[go: up one dir, main page]

WO2008131627A1 - A method, system for processing session and message - Google Patents

A method, system for processing session and message Download PDF

Info

Publication number
WO2008131627A1
WO2008131627A1 PCT/CN2007/071316 CN2007071316W WO2008131627A1 WO 2008131627 A1 WO2008131627 A1 WO 2008131627A1 CN 2007071316 W CN2007071316 W CN 2007071316W WO 2008131627 A1 WO2008131627 A1 WO 2008131627A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
receiver
message
service server
initiator
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2007/071316
Other languages
English (en)
French (fr)
Inventor
Guojun Xu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
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
Priority to EP07846142A priority Critical patent/EP2093946A4/en
Publication of WO2008131627A1 publication Critical patent/WO2008131627A1/zh
Priority to US12/508,301 priority patent/US20090305733A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • 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/21—Monitoring or handling of messages
    • H04L51/214—Monitoring or handling of messages using selective forwarding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/4061—Push-to services, e.g. push-to-talk or push-to-video
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the present invention relates to a network session technology, and in particular, to a method and system for processing a session and a message when a recipient is offline.
  • the session refers to two or more participants transmitting messages or continuous media information by establishing a session connection.
  • the session processing method in the prior art when the originating party of the session initiates the session invitation, if the receiving party is not online, the receiving party often cannot obtain the content of the session invitation.
  • the currently used push-to-talk over-network (PoC) service can provide a voice mailbox (PoC Box) function when the receiver is not online.
  • the receiver service server triggers the PoC box to participate in the session instead of the receiver and records the session content.
  • the session content of the session can be obtained from the PoC box, and according to the acquired session content. Know the originator information of the session invitation.
  • the initiator initiates a session request to the receiving service server, and knows that if the receiving party is not online, if the initiator does not When the session content is provided to the PoC Box, the PoC Box does not record any session information. In this way, the recipient cannot know the information of the invitation of this session.
  • related information such as an initiator identifier, a session initiation time, and the like may be included.
  • the session request can be learned only through the session content saved in the PoC Box when the receiver is online.
  • the initiating direction sends a discrete message to the receiving party
  • the offline message is often saved as an offline message by the offline function entity, and when the receiving party goes online, the offline message is sent to the offline message.
  • the receiver is not online, it cannot be known. A discrete message sent to the receiver in the originating direction.
  • the embodiment of the present invention provides a method and system for processing a session and a message, so that the receiver can learn the session invitation information when the party is offline, even if the initiator does not provide the session content.
  • the embodiment of the invention provides a method for session processing, the method comprising:
  • the receiving service server receives the session request sent by the initiator
  • the session invitation information is generated according to the received session request, and the session invitation information is provided to the recipient.
  • the embodiment of the invention further provides a system for session processing, the system comprising: an initiator, a receiver service server, and a receiver;
  • An initiator configured to send a session request to a receiver service server
  • the receiving service server is configured to receive a session request sent by the initiator, and when detecting that the receiver is offline, generate session invitation information according to the received session request, and provide the session invitation information to the receiver;
  • the receiver is configured to obtain session invitation information provided by the receiver service server.
  • the embodiment of the invention further provides a method for processing a session and a message, the method comprising: receiving, by the receiver service server, a session request or a discrete message sent by the initiator;
  • the session request or the discrete message is sent to the interconnection function entity according to the user setting or the operator policy;
  • the interconnect function entity uses the message service that the receiver is using to send the session request or discrete message to the recipient or accept the session request or the discrete message instead of the recipient.
  • Another method for processing a session and a message includes: receiving, by a receiver service server, a session request or a discrete message sent by an initiator;
  • the session request or the discrete message is forwarded to the authorized user through the online authorized user service server according to the authorized user information set by the receiver.
  • An embodiment of the present invention provides a session and message processing system, where the system includes: a receiver service server, and an interconnection function entity;
  • a receiver service server configured to receive a session request or a discrete message sent by the sender, and if it is detected that the receiver is not online, send the session request or the discrete message to the interconnected functional entity according to a user setting or an operator policy;
  • the interconnection function entity receives a session request or a discrete message sent by the receiver service server, and uses the message service that the receiver is using to send the session request or the discrete message to the receiver or replace the receiver to accept the session request or the discrete message. Message.
  • the embodiment of the invention provides a session and message processing system, a receiver service server, and a service server of an authorized user;
  • the receiving service server is configured to receive the session request or the discrete message sent by the initiator. If the receiving party is not online, the session request or the discrete message is sent to the service server of the authorized user according to the authorized user information set by the receiver. ;
  • the service server of the authorized user is configured to forward the session request or the discrete message sent by the receiver service server to the authorized user.
  • the session processing method and system provided by the embodiment of the present invention, when the receiver service server detects that the receiver service server is offline, generates session invitation information according to the received session request and provides the session invitation information to the receiver.
  • the receiver can obtain the session invitation information when the party is not online even if the initiator does not provide the session content, unlike the prior art, if the initiator does not perform the voice message, the receiver cannot know whether the message is received or not. Conversation invitations received while online.
  • the interworking function entity sends the session request or the discrete message to the receiving party by using the message service that the receiving party is using, so that the receiving party even if the initiator does not provide the session content, the receiving party also It is possible to know the session request or the discrete message sent by the originating party when not online.
  • a method and a system for processing a session and a message are provided by the embodiment of the present invention. If the receiving party is not online, the session request or the discrete message sent by the initiator is sent to the online authorized user according to the authorized user information set by the receiver. . The receiving party is caused to initiate a session request sent by the receiving party when the authorized user is informed that the offline user is offline.
  • FIG. 1 is a system structural diagram of a first session processing according to an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a service server according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for notifying a receiver to implement session processing by using a circuit switched (CS) domain message according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a session processing method for saving session invitation information according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a method for replacing a receiver session according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a method for processing a message service session being used by a receiver according to an embodiment of the present invention
  • FIG. 7 is a flowchart of another method for processing a message service processing session by a receiving party according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of a method for processing a discrete message when a receiver is offline, according to an embodiment of the present disclosure
  • FIG. 9 is a flowchart of a method for forwarding a session request to an authorized user according to an embodiment of the present invention
  • FIG. 10 is a schematic structural diagram of a second session processing system according to an embodiment of the present disclosure
  • FIG. 11 is a system structural diagram of a third session processing according to an embodiment of the present invention.
  • FIG. 12 is a structural structural diagram of a first message processing according to an embodiment of the present invention.
  • FIG. 13 is a structural diagram of a second message processing system according to an embodiment of the present invention. detailed description
  • the embodiment of the present invention is mainly based on a Session Initiation Protocol (SIP) system, where the originating party sends a session request to the service server, and the receiver service server detects that the receiver is offline, and generates a session according to the received session request. Invite the information and provide the session invitation information to the recipient.
  • SIP Session Initiation Protocol
  • FIG. 1 is a structural diagram of a first session processing system according to an embodiment of the present invention. As shown in FIG. 1, the system mainly includes: an initiator 101, a receiver service server 102, and a receiver 103.
  • the initiator 101 sends a session request to the recipient service server 102;
  • the receiver service server 102 receives the session request sent by the initiator 101, and detects that the receiver 103 is not online, generates session invitation information according to the received session request, and provides the session invitation information to the receiver 103;
  • the receiver 103 obtains session invitation information provided by the recipient service server 102.
  • the session request may include an identifier of the initiator and an identifier of the receiver.
  • the identity of the originator may include the originator's uniform resource identifier, name, and the like.
  • the session invitation information includes information such as an initiator identifier, a session initiation time, and a receiver identifier.
  • the system can also include: an Interworking Function (IWF) entity 104, and a message center 105;
  • IWF Interworking Function
  • the IWF entity 104 is configured to receive the session invitation information sent by the receiver service server 102, generate a message carrying the session invitation information according to the received session invitation information, and send the message carrying the session invitation information to the message center 105;
  • the message center 105 receives the message carrying the session invitation information sent by the IW entity 104, and sends a message carrying the session invitation information to the receiver 103.
  • the message carrying the session invitation information may be a short message, a multimedia message, or the like.
  • the message center 105 can be a short message center, a multimedia message (MMS) center (MMS center), a wireless application protocol (Wireless Application Protocol) gateway. Wait.
  • MMS multimedia message
  • MMS center multimedia message center
  • wireless application protocol Wireless Application Protocol
  • the message center can also be replaced with a WAP gateway (Wireless Application Protocol Gateway), and the WAP gateway receives the message carrying the session invitation information sent by the IWF entity 104, and pushes the message carrying the session invitation information with WAP PUSH (wireless application protocol push) ) is provided to the recipient.
  • WAP gateway Wireless Application Protocol Gateway
  • WAP PUSH wireless application protocol push
  • the session invitation information generated by the receiver service server 102 may include an activation identifier.
  • the IW entity 104 when the message format is a short message format or a message carried by the PUSH, the IW entity 104 generates the session invitation information.
  • the message includes a header field that activates the receiver client; when the message format is a multimedia message format, the content type field of the message carrying the session invitation information generated by the IW entity 104 includes a parameter indication of activating the receiver client;
  • the party 103 automatically goes online to establish a session connection with the initiator 101, or does not go online.
  • the receiving service server 102 is further configured to: when sending the session invitation information including the activation identifier, send a ringing response to the initiator 101; if it is detected that the receiving party 103 is not online during the set time of the ringing period, The initiator 101 sends back a timeout response; if it detects that the receiver 103 is online during the ringing, the session request is sent to the receiver 103;
  • the sender 1 01 is further configured to wait for the receiving party 103 to go online after receiving the ringing response, and end the session request after receiving the timeout response;
  • the receiver 1 03 establishes a session connection with the initiator 101 after receiving the session request.
  • the system may further include: an offline function entity 106, configured to receive and save the session invitation information sent by the receiver service server 102, and when the online notification sent by the receiver service server 102 is received, the saved session invitation information is provided. To the recipient service server 103;
  • the service server 102 is further configured to: when the receiver 103 is online, send an online notification to the offline function entity 106; obtain the session invitation information saved by the offline function entity, and provide the session invitation information to the receiver.
  • the offline function entity 106 can be a standalone device or can be placed in the recipient service server 102.
  • the system can also include a unified storage entity 107 for receiving the recipient service server 102
  • the session connection is established with the initiator 101, and the session content sent by the initiator 101 is saved.
  • the saved session content is provided to the receiver service server 102. If the end session notification of the recipient service server 102 is received, the session connection with the initiator is terminated, and after receiving the session continuation notification, the session content sent by the initiator is continuously recorded;
  • the receiving service server 102 is further configured to: when the receiving party is offline, send the offline notification to the unified storage entity 107; when detecting that the receiving party goes online, provide the session content sent by the unified storage entity 107 to the receiving party. And sending an online notification to the unified storage entity 107, detecting whether the session established by the unified storage entity and the initiator ends when the receiver goes online, and if not yet, sending a connection notification to the receiver 1300; detecting the receiver and the initiator After the session is established, an end session notification or a session continuation notification is sent to the unified storage entity 107.
  • the receiving party 103 is further configured to obtain the session content provided by the receiver service server 102 after being online, and establish a session connection with the initiator 101 after receiving the establishment session notification sent by the receiver service server 102.
  • the unified storage entity 107 may be configured as an independent device or in the receiver service server 102.
  • FIG. 2 is a structural diagram of a service server according to an embodiment of the present invention.
  • the service server mainly includes: a transceiver unit 111, a detecting unit 112, and a session invitation information generating unit 11 3;
  • the transceiver unit 111 after receiving the session request, sends the session request to the detecting unit 112, and after receiving the session invitation information sent by the session invitation information generating unit 113, the session invitation information is sent;
  • the detecting unit 112 after receiving the session request sent by the transceiver unit, detects whether the receiver is online according to the receiver identifier in the session request, and detects that the receiver is not online, and sends the session request to the session invitation information generating unit 113. ;
  • the session invitation information generating unit 11 3 receives the session request sent by the detecting unit 112, and then roots The session invitation information is generated according to the session request, and is provided to the transceiver unit 111.
  • the service server may further include: an offline function unit 114, configured to receive and save the session invitation information generated by the session invitation information generating unit 113, and send the saved session invitation information to the transceiver unit when receiving the online notification sent by the detecting unit 112. 111 ;
  • the detecting unit 112 is further configured to send an online notification to the offline function unit 114 when the receiving party goes online;
  • the transceiver unit 111 sends the session invitation information after receiving the session invitation information provided by the offline function unit.
  • the service server may further include: a unified storage unit 115, when receiving the offline notification sent by the detecting unit 112, establishing a session connection with the initiator, and saving the session content sent by the initiator, after receiving the online notification sent by the detecting unit 112 , the saved session content is provided to the transceiver unit 111;
  • the detecting unit 112 is further configured to: when detecting that the receiving party is offline, send an offline notification to the unified storage unit 115, and when detecting that the receiving party goes online, send an online notification to the unified storage unit 115; the transceiver unit 111 further And configured to receive the session content sent by the unified storage unit 115, and send the session content.
  • the service server may further include: a notification unit 116, configured to provide the unified storage unit 115 with a notification that the receiver establishes a session connection with the initiator to the transceiver unit 111;
  • the transceiver unit 111 is further configured to send the notification provided by the notification unit 116 to the initiator.
  • the transceiving unit 111 also transmits the notification to the recipient via the interworking function entity or the offline function unit 114.
  • the detecting unit 112 is further configured to: when detecting that the receiving party is online, further detecting whether the session connection established by the unified storage unit 115 and the initiator is ended, and if not yet, sending a connection notification to the transceiver unit 111; detecting receiving After establishing a session with the initiator, the party sends an end session notification or a session continuation notification to the unified storage unit 115;
  • the transceiver unit 111 is further configured to: after receiving the connection notification sent by the detecting unit 112, send the connection notification;
  • the unified storage unit 115 is further configured to: after receiving the end session notification sent by the detecting unit 112, end the session established with the initiator, and after receiving the session continuation notification sent by the detecting unit 112, continue to record the session sent by the initiator 101. content. description.
  • Figure 3 is a flow chart of a method for notifying a receiver to implement session processing by using a Circuit Switch (CS) domain message.
  • CS Circuit Switch
  • PS Packet Switching
  • Step 201 The initiator sends a session request to the receiver service server through a SIP/IP core (Core).
  • Core SIP/IP core
  • the initiator first initiates a session request to the SIP/IP Core, and the SIP/IP Core finds the corresponding service server of the receiver according to the service information and the receiver information in the session request, and sends the session request to the receiver service server.
  • the session request can use the following example:
  • INVITE sip bobSbiloxi. example, com SIP/2.0
  • the session request may include information such as an initiator identifier, a receiver identifier, and a service type.
  • Step 202 When the receiver service server detects that the receiver is offline, generates session invitation information according to the received session request.
  • the generated session invitation information can be in the following format:
  • the generated session invitation information includes an initiator identifier, a sending time, and receiver information.
  • the receiver service server After the receiver service server detects that the receiver is offline, it will send a SIP signaling response to the initiator through the SIP/IP CORE, notifying the initiator that the receiver is unreachable.
  • the returned SIP signaling response can be in the following format:
  • the SIP/IP Core sends a reject session response to the initiator, and the initiator ends the session request.
  • Step 203 The receiver service server sends the generated session invitation information to the IWF entity.
  • Step 204 The IWF entity generates a message carrying the session invitation information according to the received session invitation information.
  • the IWF entity can perform format conversion according to the protocol used by the receiver to generate a message carrying the session invitation information. For example, a short message carrying session invitation information or carrying session invitation information may be generated. The multimedia message or the short message carried by the Ray PUSH carrying the session invitation information.
  • the message carrying the session invitation information also includes the initiator identifier, the sending time, and the recipient information.
  • Step 205 IWF entity of the session invitation message carrying the information to the short message service center (SMSC) 0
  • the IWF entity sends the multimedia message carrying the session invitation information to the multimedia center (MMS center); if the IW entity generates the bearer PUSH carrying the session invitation information The short message, the IWF entity sends the short message carried by the WAP PUSH carrying the session invitation information to the wireless application protocol gateway.
  • multimedia center multimedia center
  • the IWF entity sends the short message carried by the WAP PUSH carrying the session invitation information to the wireless application protocol gateway.
  • Step 206 The SMSC sends the message carrying the session invitation information to the receiver according to the receiver information in the converted session invitation information.
  • the session invitation information is sent to the receiver by using the CS domain, and the related information of the invited session can also be obtained when the receiver user is offline.
  • step 202 when the receiver service server detects that the receiver is offline, the session invitation information with the activation identifier may be generated, and then the IWF entity sends the session invitation information. Converting to a short message format or a message format carried by the WAP PUSH, the generated message carrying the session invitation information includes a header field that activates the recipient client; and the IW entity converts the session invitation information into a multimedia message. In the format, the generated content type field of the message carrying the session invitation information includes a parameter indication of activating the recipient client.
  • the receiver When the receiver obtains the converted message carrying the session invitation information indicating the parameter of the active receiver client header field, the receiver automatically activates the client of the receiver, and the receiver automatically goes online to establish a session connection with the initiator. You can also choose whether to go online.
  • the receiving service server sends the session invitation information including the activation identifier
  • the ringback response is sent back to the initiator, and the initiator waits for the receiver to go online; if the receiver does not go online within the set time during the ringing, the receiver The server sends a timeout response to the initiator through the SIP/IP Core, and the initiator ends the session request.
  • the session invitation information with the activation identifier may be implemented by using the following header field format based on the format in step 202:
  • the receiver service server sends a ringback response to the initiator, informing the initiator to wait for the receiver to respond, and the ringing response can be in the following format:
  • the IWF After the IWF receives the session invitation information with the activation identifier, it converts to the message format.
  • the following example can be used:
  • FIG. 4 is a flow chart of the session processing method for saving session invitation information. As shown in Figure 4, the method mainly includes the following steps:
  • Step 301 The initiator sends a session request to the receiver service server through the SIP/IP Core.
  • Step 302 When the receiver service server detects that the receiver is offline, the session invitation information is generated according to the session request of the initiator.
  • the SIP/IP Core sends a reject session response to the initiator, and the initiator ends the session request.
  • Step 301 The implementation method of step 302 is the same as the implementation method of steps 201 and 202, respectively.
  • the receiver service server After the receiver service server detects that the receiver is offline, it sends a response to the sender through the SIP/IP Core, notifying the initiator that the receiver is not online.
  • Step 303 The receiver service server sends the generated session invitation information to the offline function entity.
  • the offline function entity is separately set, in addition to the offline function entity. It can also be set in the receiving service server, and the function of generating and saving the session invitation information is completed by the service server.
  • Step 304 The offline function entity saves the received session invitation information.
  • the offline function entity can save the session invitation information as an offline message.
  • Step 305 After the receiver service server detects that the receiver is online, the session invitation information is obtained from the offline function entity.
  • Step 306 The receiving service server provides session invitation information to the receiver in a push (PUSH) or pull (PULL) manner.
  • PUSH push
  • PULL pull
  • FIG. 5 is a flowchart of a method for replacing a receiver session according to an embodiment of the present invention. As shown in FIG. 5, the method includes the following steps:
  • Step 401 The initiator sends a session request to the receiver service server through the S IP/IP Core.
  • Step 402 When the receiver service server detects that the receiver is offline, generates session invitation information according to the received session request.
  • Step 403 The service of the receiver sends the generated session invitation information to the offline function entity.
  • Step 404 The offline function entity saves the session invitation information in an offline message manner.
  • Step 405 The receiver service server notifies the unified storage entity to participate in the session.
  • the receiving service server detects that the receiving party is not online, if the receiving party customizes the service instead of the session, the unified storage entity is notified to participate in the session instead of the receiving party.
  • the steps 403 and 405 have no fixed sequence, and may also be performed simultaneously.
  • the unified storage entity sends a SIP 200 ok to the recipient service server.
  • the receiving service server sends back a response of the SIP 200 ok to the initiator through the CIP/IP Core, thereby notifying the initiator that the unified storage entity can replace the recipient to participate in the session.
  • Step 406 The unified storage entity establishes a session with the initiator through the receiver service server, and records the session content.
  • Step 407 After the receiver service server detects that the receiver is online, the session invitation information is obtained from the offline function entity.
  • Step 408 The receiver obtains the session invitation information by means of PULL or PUSH.
  • Step 409 The receiver service server acquires the session content from the unified storage entity.
  • steps 407 and 409 have no fixed sequence, and may also be performed simultaneously.
  • Step 410 The receiver service server provides the session content to the receiver in a PULL or PUSH manner, and notifies the receiver to continue the session.
  • Step 411 The receiver establishes a session channel with the initiator, and performs session connection.
  • Step 412 The receiver service server notifies the unified storage entity to end the session established with the initiator.
  • the receiving party may select whether to perform the session connection according to the received session invitation information. If the receiving party does not perform the session connection, the unified storage entity always replaces the receiving party to perform the session and records the session content.
  • the receiving party service server The session record is obtained from the unified storage entity, and the session record is provided to the receiver in a PULL or PUSH manner.
  • the receiver service server does not notify the receiver to continue the session, and steps 411 and 412 are not performed.
  • the receiver service server may send a session continuation notification to the unified storage entity, and the unified storage entity continues to receive and record the session content sent by the initiator.
  • the unified storage entity replaces the receiver to participate in the session, and may also notify the sender of the unified storage entity by using the SIP message to replace the receiver to participate in the session, and at the same time, the session invitation information and the I may be unified through the CS domain. A notification that the storage entity replaces the recipient's participation in the session is provided to the recipient.
  • the methods provided in the above embodiments may exist alone or in combination of the methods described in the above embodiments.
  • the unified storage entity may be used instead of the receiver to participate in the session, and the session invitation information may be provided by using the CS domain in the embodiment of FIG.
  • Receiving party Further, after receiving the session invitation information with the activation identifier, the receiver can automatically activate the online connection and perform session connection with the initiator.
  • FIG. 6 is a flowchart of a method for processing a message service session being used by the receiver according to an embodiment of the present invention. As shown in FIG. Includes the following steps:
  • Step 501 The initiator sends a session request to the receiver service server.
  • Step 502 The receiver service server detects that the receiver is offline, and detects that the receiver is using the fixed S service, and sends the received session request to the IWF entity.
  • the receiving service server may obtain the MN S service information that the receiver is using from the recipient's home subscriber server (HSS), and provide the service information to the IW entity.
  • the receiver may also obtain the receiver from using the HSS of the receiver.
  • Other messaging services may be used.
  • Step 503 After receiving the session request, the IW entity converts the session request into an MMS that includes the session request information and sends the message to the multimedia message center (MMSC) of the receiver.
  • MMSC multimedia message center
  • Step 504 The receiving MMSC sends the received MMS containing the session request information to the receiver.
  • Step 505 After receiving the solid S containing the session request information, the receiver may select to go online or not. If the receiver is online, the receiver service server can connect the session to the receiver, and the initiator establishes a session connection with the receiver. If the receiver does not go online, proceed to step 506.
  • Step 506 The IWF negotiates a session channel with the initiator through the receiver service server.
  • the IWF can directly accept the session request by the IWF when the receiver receives the session request of the initiator according to the user's settings or the operator policy, and establish a meeting between the receiver and the IWF.
  • the voice channel through which the receiver and the initiator exchange messages through the IWF is a prior art, and details are not described herein again.
  • Step 507 After the session channel negotiation is completed, a session channel is established, and the session content of the initiator is received by using the session channel, and the content of the session is converted into a solid S format, and sent to the receiver by the fixed SC of the receiver, or the receiving receiver is received.
  • the MMS sent by the receiving MMSC, and the MMS message is converted into a SIP (Session Description Protocol) domain message, and sent to the initiator through the established session channel.
  • SIP Session Description Protocol
  • the receiver service server detects that the receiver is offline, it can directly send the session request to the IWF entity.
  • the IWF entity obtains the solid S service information that the receiver is using from the HSS, and will receive the message.
  • the session request is sent to the IWF entity.
  • the message service that the receiver is using can also be an SMS (short message) message, an email message, or other message service.
  • FIG. 7 is a flowchart of another method for a message service processing session being used by a receiver according to an embodiment of the present invention.
  • the IFW may pass some services and receivers in addition to establishing a session channel with the initiator.
  • Establishing a session channel as shown in FIG. 7, the method may include the following steps: Step 601: The initiator sends a session request to the receiver service server.
  • Step 602 The receiver service server detects that the receiver is offline, and detects that the receiver is using the instant messaging (IMPS) message service, and sends the received session request to the IWF entity.
  • IWF instant messaging
  • the receiver service server can obtain the service information that the receiver is using from the receiver's HSS.
  • Step 603 After receiving the session request, the IW entity converts the session request into an IMPS message containing the session request information, and sends the message to the instant messaging center (IMPSC).
  • IMPSC instant messaging center
  • Step 604 The IMPS sends an IMPS message containing the session request information to the receiver.
  • Step 605 The IWF entity negotiates the session channel with the initiator through the receiver service server, and negotiates the session channel with the receiver through the IMPSC.
  • Step 606 The IWF entity establishes a session channel with the initiator and establishes a session channel with the receiver.
  • Step 607 The IWF entity receives the session sent by the initiator through the session channel established with the initiator. Content, and converting the content of the session into an IMPS message form to be sent to the receiver through a channel established with the receiver; or receiving a message in the form of an IMPS sent by the receiver through a session channel established with the receiver, and the IMPS message is The message converted into a SIP domain is sent to the initiator through a session channel established with the initiator.
  • the receiver service server detects that the receiver is offline, it can also directly send the session request to the IWF entity.
  • the IWF entity detects that the receiver is using the IMPS message service, it will receive the session. The request is sent to the IW entity.
  • FIG. 8 is a flowchart of a method for processing a discrete message when a receiver is offline, according to an embodiment of the present invention. As shown in FIG. 8, the method may include the following steps:
  • Step 701 The receiver service server receives the SIP discrete message sent by the initiator.
  • Step 702 The receiver service server detects that the receiver is offline, and detects that the receiver is using the fixed S service, and sends the received SIP discrete message to the IWF entity.
  • Step 703 After receiving the SIP discrete message, the IWF entity converts the SIP discrete message into a solid S containing the content of the discrete message, and sends the fixed S to the MMSC.
  • Step 704 The solid SC sends the solid S sent by the IWF entity to the receiver.
  • the receiver responds to the IWF entity by the MMSC to receive the response of the fixed S, and the IWF entity also responds to the initiator by the message server to receive the response of the message.
  • FIG. 9 is a flowchart of a method for forwarding a session request to an authorized user according to an embodiment of the present invention.
  • a description is performed by sending a session request to a receiver in a sending direction, when the sending direction sends a discrete message to the receiver.
  • the process provided by this embodiment can also be used.
  • the method may include the following steps: Step 801: The receiver service server receives the session request sent by the initiator.
  • Step 802 The receiver service server detects that the receiver is offline, and obtains the authorized user information set by the receiver.
  • the receiving service server when the receiving service server detects that the receiving party is offline, it can obtain whether the receiving party sets an authorized user from the HSS of the receiving party, and if the authorized user is set, further obtain the authorized user information.
  • Step 803 The receiver service server forwards the session request to the service server of the authorized user according to the setting of the receiver.
  • Step 804 The service server of the authorized user sends the received session request to the authorized user.
  • Step 805 After receiving the session request, the authorized user establishes a session channel with the initiator, instead of completing the session with the initiator.
  • the receiver service server may also use the message service that the receiver is using by the IWF entity to send a notification that the authorized user performs the session instead of the receiver to the receiver, and the method for sending the notification may use the map. 8
  • the process shown is complete.
  • the notification can also be saved by the offline functional entity, and the notification is obtained when the recipient goes online.
  • the content of the session between the initiator and the authorized user can be saved through the unified storage entity.
  • the receiving service server may also send a notification of the authorized user agent receiving party to the initiator through the S IP domain.
  • the receiving service server can also record the content of the session between the initiator and the authorized user, so that the receiver can find the content of the session.
  • FIG. 10 is a system structure diagram of a second session processing according to an embodiment of the present invention. As shown in FIG. 10, the system includes: a receiver service server 91 0, and an IWF entity 920.
  • the receiver service server 91 0 is configured to receive a session request sent by the sender, and if the receiver is detected to be offline, send the session request to the IWF entity 920.
  • the IWF entity 920 receives the session request sent by the receiver service server 910, and uses the message service that the receiver is using, sends the session request to the receiver or accepts the session instead of the receiver. Request.
  • the system may further include: HSS 940, configured to store message service information that the recipient is using.
  • the receiver service server 910 is further configured to obtain, from the HSS 940, message service information that the receiver is using;
  • the IWF entity 920 is configured to obtain, from the HSS 940 or the receiver service server 910, message service information that is used by the receiver, and perform, by using the message service information that the receiver is using, to send the session request to the receiver or accept the receiver instead. The operation of the session request.
  • the IWF entity 920 may include: a receiving unit 921, a message converting unit 922, and a sending unit 923;
  • the receiving unit 921 is configured to receive a session request sent by the receiving service server 910; the message converting unit 922 is configured to convert the session request received by the receiving unit 921 into a message of the message service that the receiving party is using;
  • the sending unit 923 is configured to send the message converted by the message converting unit 922 to the receiver.
  • the IWF entity 920 may further include: a message obtaining unit 924, configured to obtain the message service information that the receiver is using from the HSS 940 or the receiver service server 910, and send the obtained message service information to the message conversion unit 922;
  • the message conversion unit 922 is further configured to receive the message service information sent by the message obtaining unit 924, and perform an operation of converting the session request received by the receiving unit 921 into a message of the message service being used by the receiver by using the message service information.
  • the IWF entity 920 may further include: a session channel establishing unit 925, configured to establish a session channel with the initiator;
  • the receiving unit 921 is further configured to receive the session content sent by the initiator by using the session channel established by the session channel establishing unit 925;
  • the message conversion unit 922 is further configured to convert the session content received by the receiving unit 921 into a message of a message service that the receiver is using.
  • the session channel establishing unit 925 is further configured to establish a session channel with the receiver.
  • the sending unit 923 is further configured to send the message converted by the message converting unit 922 to the receiving party through the session channel established by the session channel establishing unit 925.
  • FIG. 11 is a system structure diagram of a third session processing according to an embodiment of the present invention.
  • the system includes: a receiver service server 1010 and a service server 1020 of an authorized user; and a receiver service server 1010, configured to Receiving a session request sent by the initiator, if it is detected that the receiver is not online, according to the authorized user information set by the receiver, the session request is sent to the service of the authorized user 1020;
  • the service server 1020 of the authorized user is configured to forward the session request sent by the receiver service server 1010 to the authorized user.
  • the system can also include:
  • the authorized user 1030 after receiving the session request sent by the authorized user's service server 1020, establishes a session channel with the initiator, instead of the receiver and the initiator.
  • the system may further include: an IWF entity 1 040 or an offline functional entity 1 050;
  • the receiver service server 1010 is further configured to send the notification of the authorized user to the IWF entity 1040 or the offline function entity 1050 instead of the notification of the receiver and the initiator;
  • the IWF entity 1040 is configured to receive the notification sent by the receiver service server 1010, and send the notification to the receiver by using the service message that the receiver is using or by using the CS domain;
  • the offline function entity 1050 is configured to receive the notification sent by the receiver service server 1010, and send the notification to the receiver as an offline message.
  • the receiver service server 1010 is further configured to send an authorized user to the initiator in place of the notification that the receiver and the initiator perform the session.
  • the system may further include: a receiver unified storage entity, configured to save session content between the initiator and the authorized user.
  • the system may further include: HSS 1060, configured to store authorized user information set by the receiver;
  • the receiver service server 1010 is further configured to obtain, from the HSS 1060, authorized user information set by the receiver.
  • the receiving service server 1010 may include: a receiving unit 1011, a detecting unit 1012, an authorized user information acquiring unit 1013, and a sending unit 1014.
  • the receiving unit 1011 is configured to receive a session request sent by the initiator 1010.
  • the detecting unit 1012 is configured to detect whether the receiver is online;
  • the authorized user information obtaining unit 1013 is configured to obtain authorized user information set by the receiving party when the detecting unit 1012 detects that the receiving party is not online;
  • the sending unit 1014 is configured to send the session request received by the receiving unit 1011 to the authorized user according to the authorized user information acquired by the authorized user information acquiring unit 1013.
  • the receiving service server 1010 further includes: a notification unit 1015, configured to generate a notification that the authorized user performs a session with the initiator in the authorized party;
  • the sending unit 1014 is configured to send the notification generated by the notification unit 1015 to the receiver through the IWF entity, or the offline function entity, or by using the message service that the receiver is using; and/or send the notification generated by the notification unit 1015 To the initiator.
  • FIG. 12 is a schematic structural diagram of a first type of message processing according to an embodiment of the present invention. As shown in FIG. 12, the system includes: a receiver service server 1110 and an IWF entity 1140;
  • the receiving service server 1110 is configured to receive the discrete message sent by the initiator, and if it is detected that the receiver is not online, and detects that the receiving party is using other message service, the discrete message is sent to the IWF entity 1140;
  • the IWF entity 1140 is configured to receive the discrete message sent by the receiver service server 1110, and convert the discrete message into other messages being used by the receiver, and send the message to the receiver.
  • the system may further include an HSS 1130, configured to store service information that the receiver is using; the receiver service server 1110 is further configured to obtain, from the HSS 1130, service information that the receiver is using, and detect, according to the service information, that the receiver is in use.
  • Other messaging services may further include an IWF entity 1140, configured to receive the discrete message sent by the receiver service server 1110, and convert the discrete message into a message of other message service being used by the receiver, and corresponding to the message service being used by the receiver.
  • the message center sends the converted message to the recipient.
  • the IWF entity 1140 includes: a receiving unit 1141, a message converting unit 1142, and a sending unit 1143;
  • the receiving unit 1141 is configured to receive the discrete message sent by the receiving service server 1110.
  • the message converting unit 1142 is configured to convert the discrete message received by the receiving unit 1141 into a message of the message service being used by the receiver.
  • the sending unit 1143 is configured to send the message converted by the message converting unit 1142 to the receiver.
  • the IWF entity 1140 further includes: a message obtaining unit 1144, configured to obtain the message service information that the receiver is using from the HSS 1130 or the receiver service server 1110, and send the obtained message service information to the message conversion unit 1142;
  • the message conversion unit 1142 is further configured to receive the message service information sent by the message obtaining unit 1144, and perform an operation of converting the discrete message received by the receiving unit 1141 into a message of the message service being used by the receiver by using the message service information.
  • the system shown in Figure 12 can be used to implement the method flow shown in Figure 8.
  • FIG. 13 is a structural diagram of a second message processing system according to an embodiment of the present invention.
  • the system includes: a receiver service server 1210, and a service server 1220 of an authorized user.
  • the receiving service server 1210 is configured to receive the discrete message sent by the initiator, and if it is detected that the receiver is not online, forward the discrete message to the service server 1220 of the authorized user according to the authorized user information set by the receiver;
  • the service server 1220 of the authorized user is configured to send the discrete message sent by the receiver service server 1210 to the authorized user.
  • the system can also include: an IW entity 1240 or an offline functional entity 1250;
  • the receiver service server 1210 is further configured to receive the discrete message by the authorized user instead of the receiver.
  • the notification is sent to the IWF entity 1240 or the offline functional entity 1250;
  • the IWF entity 1240 is configured to receive the notification sent by the receiver service server 1210, and send the notification to the receiver by using the service message that the receiver is using or by using the CS domain;
  • the offline function entity 1250 is configured to receive the notification sent by the receiver service server 1210, and send the notification to the receiver as an offline message.
  • the receiver service server 1210 is further configured to send, to the initiator, a notification that the authorized user receives the discrete message instead of the receiver.
  • the receiving service server 1210 includes: a receiving unit 1211, a detecting unit 1212, an authorized user information acquiring unit 1213, and a sending unit 1214;
  • the receiving unit 1211 is configured to receive a discrete message sent by the initiator.
  • the detecting unit 1212 is configured to detect whether the receiver is online;
  • the authorized user information obtaining unit 1213 is configured to obtain authorized user information set by the receiving party when the detecting unit 1212 detects that the receiving party is not online;
  • the sending unit 1214 is configured to send the discrete message received by the receiving unit 1211 to the authorized user according to the authorized user information acquired by the authorized user information acquiring unit 1213.
  • the receiver service server may further include: a notification unit 1215, configured to generate a notification that the authorized user receives the discrete message instead of the receiver;
  • the sending unit 1214 is further configured to send the notification generated by the notification unit 1215 to the receiver through the IWF entity 1240, or the offline function entity 1250, or by using the message service that the receiver is using; and/or the notification generated by the notification unit 1215 Sent to the initiator.
  • the system shown in Figure 13 can be used to implement the method flow shown in Figure 9.
  • the session processing method, system, and service server provided by the embodiment of the present invention, when the receiver service server detects that the receiver service server is offline, generates session invitation information according to the received session request and provides the message to the receiver.
  • the party enables the receiver to know the session invitation information when the party is offline, even if the initiator does not provide the session content, unlike the prior art, if the initiator does not perform the voice message, the receiver cannot When you are not online Invited session invitation.
  • the receiving party can receive the session invitation information in a timely state without being online, and the receiving party can also automatically activate the online meeting by receiving the session invitation information, and establish a session with the initiator in time.
  • the method may save the session invitation information by using the offline function entity to implement the offline message, and when the receiving party goes online, provide the session invitation information to the receiver, so that the receiver is notified of the session invitation received when the party is offline, and
  • the receiver can obtain the recorded session content, and, when the session has not ended, can choose to connect with the initiator. This enriches the user's business experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Telephonic Communication Services (AREA)

Description

会话和消息的处理方法、 系统
技术领域
本发明涉及网络会话技术， 特别涉及一种接收方不在线时的会话和消息 的处理方法、 系统。
背景技术
随着网络技术的不断发展， 利用网络建立会话已经成为用户间进行联系 和沟通的常用方法。 其中， 所述会话指的是两个或多个参与者通过建立会话 连接来传递消息或者连续媒体信息。 但是， 在现有技术中的会话处理方法中， 会话的发起方向接收方发起会话邀请时， 如果接收方不在线， 则接收方往往 不能获得会话邀请的内容。
为了解决上述问题， 目前釆用的无线一键通（PoC , Push to ta lk over Ce l lular )业务可以在接收方不在线时， 提供语音信箱 （PoC Box ) 的功能。 当发起方发起会话请求时， 接收方业务服务器触发 PoC Box代替接收方参加 会话并记录会话内容， 接收方上线后， 可以从 PoC Box 中获取该会话的会话 内容， 并根据所获取的会话内容得知会话邀请的发起方信息。
在实现本发明的过程中， 发明人发现在现有技术中存在如下问题： 在上述方法中， 发起方在向接收方业务服务器发起会话请求， 并得知接 收方不在线时， 如果发起方没有将会话内容提供给 PoC Box , 则 PoC Box不会 记录任何的会话信息。 这样， 接收方则不能获知本次会话邀请的信息。 在该 会话邀请的信息中， 可以包括发起方标识、 会话发起时间等相关信息。 另外， 在上述方法中， 也只有在接收方上线时， 才能通过 PoC Box 中保存的会话内 容获知被发起会话请求。
另外， 在现有技术中， 当发起方向接收方发送离散消息时， 如果接收方 不在线， 往往通过离线功能实体将该离散消息保存为离线消息， 当接收方上 线后， 将该离线消息发送给接收方。 但是， 如果接收方不上线， 则不能获知 到发起方向接收方发送的离散消息。
所以， 现有技术中没有一种会话处理的方法， 即使在发起方没有提供会 话内容的情况下， 接收方也能够获知不在线时的会话邀请信息。 也没有一种 消息处理的方法， 即使在接收方不在线的情况下， 接收方也能够获知发起方 向接收方发送的离散消息。
发明内容
有鉴于此， 本发明实施例提供了一种会话和消息的处理方法、 系统， 以 便于即使在发起方没有提供会话内容的情况下， 接收方也能够获知不在线时 的会话邀请信息。
本发明实施例提供了一种会话处理的方法， 该方法包括：
接收方业务服务器接收发起方发送的会话请求；
如果检测到接收方不在线， 根据接收到的会话请求生成会话邀请信息， 并将所述会话邀请信息提供给接收方。
本发明实施例还提供了一种会话处理的系统， 该系统包括： 发起方、 接 收方业务服务器、 以及接收方；
发起方， 用于向接收方业务服务器发送会话请求；
接收方业务服务器， 用于接收发起方发送的会话请求， 检测到接收方不 在线时， 根据接收到的会话请求生成会话邀请信息， 并将所述会话邀请信息 提供给接收方；
接收方， 用于获取接收方业务服务器提供的会话邀请信息。
本发明实施例还提供了一种会话和消息的处理方法， 该方法包括： 接收方业务服务器接收发起方发送的会话请求或离散消息；
如果检测到接收方不在线， 则根据用户设置或运营商策略， 将所述会话 请求或离散消息发送给互联功能实体；
所述互联功能实体利用接收方正在使用的消息业务， 将所述会话请求或 离散消息发送给接收方或代替接收方接受该会话请求或离散消息。 本发明实施例提供的另外一种会话和消息的处理方法， 该方法包括： 接收方业务服务器接收发起方发送的会话请求或离散消息；
如果检测到接收方不在线， 根据所述接收方设置的授权用户信息， 将所 述会话请求或离散消息通过在线的授权用户的业务服务器转发给授权用户。
本发明实施例提供了一种会话和消息的处理系统， 该系统包括： 接收方 业务服务器、 以及互联功能实体；
接收方业务服务器， 用于接收发送方发送的会话请求或离散消息， 如果 检测到接收方不在线， 则根据用户设置或运营商策略将所述会话请求或离散 消息发送给所述互联功能实体；
互联功能实体， 接收所述接收方业务服务器发送的会话请求或离散消息， 利用接收方正在使用的消息业务， 将所述会话请求或离散消息发送给接收方 或代替接收方接受该会话请求或离散消息。
本发明实施例提供了一种会话和消息的处理系统， 接收方业务服务器、 和授权用户的业务服务器；
接收方业务服务器， 用于接收发起方发送的会话请求或离散消息， 如果 检测到接收方不在线， 根据接收方设置的授权用户信息， 将所述会话请求或 离散消息发送给授权用户的业务服务器；
授权用户的业务服务器， 用于将所述接收方业务服务器发送的会话请求 或离散消息转发给授权用户。
由以上技术方案可以看出， 本发明实施例提供的会话处理方法、 系统， 通过接收方业务服务器检测到接收方业务服务器不在线时， 根据接收到的会 话请求生成会话邀请信息提供给接收方， 使得接收方即使在发起方没有提供 会话内容的情况下， 接收方也能够获知不在线时的会话邀请信息， 而不像现 有技术中， 如果发起方不进行语音留言， 接收方则不能获知不在线时受到的 会话邀请。
本发明实施例提供的一种会话和消息处理的方法、 系统， 如果检测到接 收方不在线， 则通过互联功能实体利用接收方正在使用的消息业务， 将所述 会话请求或离散消息发送给接收方， 使得接收方即使在发起方没有提供会话 内容的情况下， 接收方也能够获知不在线时的发起方向接收方发送的会话请 求或离散消息。
本发明实施例提供的一种会话和消息处理的方法、 系统， 如果检测到接 收方不在线， 根据接收方设置的授权用户信息， 将发起方发送的会话请求或 离散消息发送给在线的授权用户。 使得接收方通过设置的授权用户获知不在 线时发起方向接收方发送的会话请求。
附图说明
图 1为本发明实施例提供的第一种会话处理的系统结构图；
图 2为本发明实施例提供的业务服务器的结构示意图；
图 3 为本发明实施例提供的利用电路交换（CS )域消息通知接收方实现 会话处理的方法流程图；
图 4为本发明实施例提供的保存会话邀请信息的会话处理方法流程图； 图 5为本发明实施例提供的代替接收方会话的方法流程图；
图 6 为本发明实施例提供的通过接收方正在使用的消息业务处理会话的 方法流程图；
图 7 为本发明实施例提供的通过接收方正在使用的消息业务处理会话的 另一方法流程图；
图 8 为本发明实施例提供的接收方不在线时， 处理离散消息的方法流程 图；
图 9为本发明实施例提供的将会话请求转发到授权用户的方法流程图； 图 10为本发明实施例提供的第二种会话处理的系统结构图；
图 11为本发明实施例提供的第三种会话处理的系统结构图；
图 12为本发明实施例提供的第一种消息处理的系统结构图；
图 1 3为本发明实施例提供的第二种消息处理系统结构图。 具体实施方式
为了使上述技术方案、 目的和优点更加清楚， 下面结合具体实施例对本 发明进行详细地描述。
本发明实施例主要基于初始会话协议 ( SIP, Session Initiation Protocol ) 系统， 发起方向接收方业务服务器发送会话请求， 所述接收方业 务服务器检测到接收方不在线时， 根据接收到的会话请求生成会话邀请信息， 并将所述会话邀请信息提供给接收方。
图 1为本发明实施例提供的第一种会话处理的系统的结构图， 如图 1所 示， 该系统主要包括： 发起方 101、 接收方业务服务器 102、 以及接收方 103。
发起方 101, 向接收方业务服务器 102发送会话请求；
接收方业务服务器 102,接收发起方 101发送的会话请求，检测到接收方 103不在线时，根据接收到的会话请求生成会话邀请信息， 并将所述会话邀请 信息提供给接收方 103;
接收方 103, 获取接收方业务服务器 102提供的会话邀请信息。
其中， 所述会话请求中可以包含发起方的标识、 以及接收方的标识。 发 起方的标识可以包括发起方的统一资源标识、 姓名等。
所述会话邀请信息包括发起方标识、 会话发起时间、 接收方标识等信息。 该系统还可以包括： 互联功能 （ IWF) 实体 104、 以及消息中心 105;
IWF实体 104, 用于接收接收方业务服务器 102发送的会话邀请信息， 根 据接收到的会话邀请信息生成携带会话邀请信息的消息， 并将所述携带会话 邀请信息的消息发送给消息中心 105;
消息中心 105,接收 IW实体 104发送的携带会话邀请信息的消息， 将携 带会话邀请信息的消息发送给接收方 103。
所述携带会话邀请信息的消息可以为短消息， 或者多媒体消息等。
相应地， 所述消息中心 105可以是短消息中心、 多媒体消息（MMS) 中心 (彩信中心）、 无线应用协议 ( 醫, Wireless Application Protocol ) 网关 等。
另外， 消息中心也可以替换成 WAP网关 （无线应用协议网关）， 所述 WAP 网关接收 IWF实体 104发送的携带会话邀请信息的消息， 并将携带会话邀请 信息的消息以 WAP PUSH (无线应用协议推） 的方式提供给接收方。
所述接收方业务服务器 102 生成的会话邀请信息中可以包含激活标识； 此时， 当所述消息格式是短消息格式或 ΨΑΡ PUSH承载的消息时， 所述 I W实 体 104生成的携带会话邀请信息的消息中包含激活接收方客户端的头域； 当所述消息格式是多媒体消息格式时， 所述 IW实体 104生成的携带会 话邀请信息的消息的内容类型字段中包含激活接收方客户端的参数指示； 接 收方 103 获取到所述包含激活接收方客户端头域的、 携带会话邀请信息的消 息时， 自动上线与发起方 101建立会话连接， 或者不上线。
所述接收方业务服务器 102 , 还用于发送包含激活标识的会话邀请信息 时， 向发起方 101 回送振铃响应； 如果在振铃期间的设定时间内检测到接收 方 103没有上线， 则向发起方 101 回送超时响应； 如果在振铃期间检测到接 收方 103上线， 则将所述会话请求发送给接收方 103 ;
所述发送方 1 01 , 还用于接收到振铃响应后， 等待接收方 103上线， 接收 到超时响应后， 结束会话请求；
所述接收方 1 03 , 接收到会话请求后， 与发起方 101建立会话连接。
该系统还可以包括： 离线功能实体 106 , 用于接收并保存接收方业务服务 器 102发送的会话邀请信息， 当接收到所述接收方业务服务器 102发送的上 线通知时， 将保存的会话邀请信息提供给接收方业务服务器 103;
所述业务服务器 102还用于检测到接收方 103上线时， 向离线功能实体 106发送上线通知；获取离线功能实体保存的会话邀请信息，并提供给接收方。
所述离线功能实体 106 可以为独立的设备， 也可以设置在接收方业务服 务器 102中。
该系统还可以包括统一存储实体 107 , 用于接收到接收方业务服务器 102 发送的不在线通知时， 与发起方 101建立会话连接， 并保存发起方 101发送 的会话内容， 接收到接收方业务服务器 102发送的上线通知后， 将保存的会 话内容提供给接收方业务服务器 102 , 如果接收到所述接收方业务服务器 102 的结束会话通知时， 则结束与发起方的会话连接， 接收到会话继续通知后， 继续纪录发起方发送的会话内容；
所述接收方业务服务器 102 ,还用于检测到接收方不在线时， 向统一存储 实体 107发送不在线通知； 检测到接收方上线时， 将统一存储实体 107发送 的会话内容提供给接收方， 并向统一存储实体 107发送上线通知， 检测接收 方上线时统一存储实体与发起方建立的会话是否结束， 如果尚未结束， 则向 所述接收方 1 03发送接续通知； 检测到接收方与发起方建立会话后， 向所述 统一存储实体 107发送结束会话通知或会话继续通知。
接收方 103 ,还用于上线后，获取接收方业务服务器 1 02提供的会话内容； 接收到接收方业务服务器 102发送的建立会话通知后， 建立与发起方 101 的 会话连接。
其中， 所述统一存储实体 107 可以设置为独立的设备， 也可以设置在接 收方业务服务器 102中。
下面对本发明实施例提供的业务服务器进行详细地描述。 图 2 为本发明 实施例提供的业务服务器的结构图， 如图 1 所示， 该业务服务器主要包括： 收发单元 111、 检测单元 112、 以及会话邀请信息生成单元 11 3;
收发单元 111 ,接收到会话请求后，将所述会话请求发送给检测单元 112 , 接收到会话邀请信息生成单元 11 3发送的会话邀请信息后， 发送所述会话邀 请信息；
检测单元 112 ,接收到收发单元发送的会话请求后，根据会话请求中的接 收方标识检测接收方是否在线， 检测到接收方不在线时， 将所述会话请求发 送给会话邀请信息生成单元 11 3;
会话邀请信息生成单元 11 3 ,接收到检测单元 112发送的会话请求后，根 据所述会话请求生成会话邀请信息， 提供给收发单元 111。
该业务服务器还可以包括： 离线功能单元 114 , 用于接收并保存会话邀请 信息生成单元 113生成的会话邀请信息， 接收到检测单元 112发送的上线通 知时， 将保存的会话邀请信息发送给收发单元 111 ;
所述检测单元 112 , 还用于检测到接收方上线时， 向离线功能单元 114发 送上线通知；
所述收发单元 111 ,接收到离线功能单元提供的会话邀请信息后，发送所 述会话邀请信息。
该业务服务器还可以包括： 统一存储单元 115 ,接收到检测单元 112发送 的不在线通知时， 与发起方建立会话连接， 并保存发起方发送的会话内容， 接收到检测单元 112发送的上线通知后， 将保存的会话内容提供给收发单元 111 ;
所述检测单元 112 , 还用于检测到接收方不在线时， 向统一存储单元 115 发送不在线通知， 检测到接收方上线时， 向统一存储单元 115发送上线通知； 所述收发单元 111 , 还用于接收统一存储单元 115发送的会话内容， 并发 送所述会话内容。
该业务服务器还可以包括： 通知单元 116 , 用于将所述统一存储单元 115 代替接收方与发起方建立会话连接的通知提供给收发单元 111 ;
所述收发单元 111 ,还用于将所述通知单元 116提供的所述通知发送给发 起方；
所述收发单元 111 还将所述通知通过互联功能实体或离线功能单元 114 发送给接收方。
另外， 所述检测单元 112 , 还用于检测到接收方上线时， 进一步检测统一 存储单元 115 与发起方建立的会话连接是否结束， 如果尚未结束， 则向收发 单元 111 发送接续通知； 检测到接收方与发起方建立会话后， 向统一存储单 元 115发送结束会话通知或会话继续通知； 所述收发单元 111, 还用于收到检测单元 112发送的接续通知后，发送所 述接续通知；
所述统一存储单元 115,还用于接收到检测单元 112发送的结束会话通知 后， 结束与发起方建立的会话， 接收到检测单元 112发送的会话继续通知后， 继续纪录发起方 101发送的会话内容。 描述。 图 3 为利用电路交换（CS, Circuit Switch)域消息通知接收方实现 会话处理的方法流程图。 发起方向接收方发起的会话请求、 以及接收方业务 服务器检测接收方是否在线都是在分组交换（PS, Packet Switch)域中进行 的。 在图 3所示的会话处理方法中， 检测到接收方不在线时， 利用 CS域的消 息业务通知接收方。 如图 3所示， 该方法包括以下步骤：
步骤 201: 发起方通过 SIP/IP核 （Core) 向接收方业务服务器发送会话 请求。
本步骤中， 发起方首先向 SIP/IP Core发起会话请求， SIP/IP Core根据 会话请求中的业务信息以及接收方信息找到接收方相应的业务服务器， 并将 会话请求发送给接收方业务服务器。
假设发起方为 Alice, 接收方为 Bob, 该会话请求可以釆用如下例子：
INVITE sip: bobSbiloxi. example, com SIP/2.0
Via: SIP/2.0/TCP client, at lanta. example, com: 5060; branch=z9hG4bK74bf 9
Max-Forwards: 70
From: Alice <sip: aliceSatlanta. example. com>; tag=9f xced76s 1
To: Bob <sip: bobSbiloxi. example. com>
Call-ID: 384827629822018851 lo)at lanta. example, com
CSeq: 1 INVITE Contact: <s ip: aliceSclient. atlanta. example, com; transpor t=tcp> Content-Type: application/ sdp
Content-Length: 151 v=0
o=alice 2890844526 2890844526 IN IP4 client, atlanta. example, com s=—
c=IN IP4 192.0.2.101
t=0 0
m=audio 49172 RTP/AVP 0
a=rtpmap: 0 PCMU/8000
其中， 所述会话请求中可以包含发起方标识、 接收方标识、 业务类型等 信息。
步骤 202: 接收方业务服务器检测到接收方不在线时， 根据接收到的会话 请求生成会话邀请信息。
例如： 在 Bob不在线时， 生成的会话邀请信息可以釆用如下格式：
MESSAGE sip: aliceSlexample. com SIP/2.0
From: Alice <im: al iceSexam le. com>
To: Bob <im: bobSexample. com>
Content-type: message/ imdn+xml
Content-Dispos i t ion: not if i cat ion
Content-length: ...
<imdn>
<Sender>Bob</mes sage-id> <datetime>2006-04-04T12: 16: 49-05: 00</datet ime> <reci ient-ur i>bobo)exam le. com</ recipient-ur i>
<note lang="en" >0ne session invitation has been recevied</ note>
</ imdn>
其中， 所述生成的会话邀请信息包含发起方标识， 发送时间， 以及接收 方信息等。
在本步骤中， 接收方业务服务器检测到接收方不在线后， 会通过 SIP/IP CORE向发起方回送 SIP信令应答， 通知发起方接收方不可达。 回送的 SIP信 令应答可以釆用如下格式：
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/TCP client, at lanta. example, com: 5060; branch=z9hG4bK74b43
； received=192.0.2.101
From: Alice <sip: aliceSatlanta. example. com>; tag=9f xced76s 1 To: Bob <sip: bobSbiloxi. example. com>; tag=3f lall2sf
Call-ID: 384827629822018851 lSat lanta. example, com
CSeq: 1 INVITE
Content-Length: 0
另外， 在本步骤中， 接收方业务服务器检测到接收方不在线后， 通过 SIP/IP Core向发起方回送拒绝会话响应， 发起方结束会话请求。
步骤 203: 接收方业务服务器将生成的会话邀请信息发送给 IWF实体。 步骤 204: IWF实体根据接收到的会话邀请信息生成携带会话邀请信息的 消息。
IWF实体可以根据接收方使用的协议进行格式转换，生成携带会话邀请信 息的消息。 例如， 可以生成携带会话邀请信息的短消息或携带会话邀请信息 的多媒体消息或携带会话邀请信息的雷 PUSH承载的短消息。
携带会话邀请信息的消息中同样包含发起方标识， 发送时间， 以及接收 方信息等。
步骤 205 : IWF 实体将所述携带会话邀请信息的消息发送给短消息中心 ( SMSC )0
如果在步骤 204 中， IWF 实体生成携带会话邀请信息的多媒体消息， 则 IWF 实体将携带会话邀请信息的多媒体消息发送给多媒体中心 （彩信中心）； 若 IW实体生成携带会话邀请信息的雷 PUSH承载的短消息， 则 IWF实体将 携带会话邀请信息的 WAP PUSH承载的短消息发送给无线应用协议网关。
步骤 206: SMSC根据转换后的会话邀请信息中的接收方信息， 将所述携 带会话邀请信息的消息发送给接收方。
通过上述方法， 利用 CS域将所述会话邀请信息发送给接收方， 使接收方 用户不在线时也可以获知被邀请会话的相关信息。
另外， 在上述流程的基础上， 在步骤 202 中， 接收方业务服务器检测到 接收方不在线时， 可以生成带有激活标识的会话邀请信息， 然后， 所述 IWF 实体如果将所述会话邀请信息转换为短消息格式或 WAP PUSH 承载的消息格 式， 则使得所述生成的携带会话邀请信息的消息中包含激活接收方客户端的 头域； 所述 IW 实体如果将所述会话邀请信息转换为多媒体消息格式时， 则 使得生成的携带会话邀请信息的消息的内容类型字段中包含激活接收方客户 端的参数指示。 接收方获取到转换后的、 包含激活接收方客户端头域的参数 指示的、 携带会话邀请信息的消息时， 会自动激活接收方的客户端， 接收方 自动上线， 与发起方建立会话连接； 也可以选择是否上线。 其中， 接收方业 务服务器发送包含激活标识的会话邀请信息时， 向发起方回送振铃响应， 发 起方等待接收方上线； 如果在振铃其间的设定时间内接收方没有上线， 则接 收方的服务器会通过 SIP/ IP Core 向发起方发送超时响应， 发起方结束会话 请求；。 所述带有激活标识的会话邀请信息可以是在步骤 202 中的格式基础上利 用如下头域格式实现：
MESSAGE sip: aliceSlexample. com SIP/2.0
From: Alice <IM: al iceSexample. com>
To: Bob <IM: bobSexample. com>
Content-type: application
Content-Disposition: IM Client Login
Content-length: ...
此时， 接收方业务服务器会向发起方回送振铃响应， 通知发起方等待接 收方应答， 该振铃响应可以釆用如下格式：
SIP/2.0 180 Ringing
From: Alice <sip: aliceSatlanta. example. com>; tag=9f xced76s 1
To: Bob <sip: bobSbiloxi. example. com>; tag=314159
Call-ID: 384827629822018851 lSatlanta. example, com
Contact: <s ip: bobScl ient. bi loxi. example, com; transpor t=tcp>
CSeq: 2 INVITE
Content-Length: 0
IWF根据接收到的带有激活标识的会话邀请信息后， 转换为消息格式， 可 以釆用如下例子：
ContentType = application/IM Client
Date = 2007-04-20 02: 25: 28
Del iveryRepor t = false
DeliveryTime = 2007-04-20 02: 25: 28 (绝对时间)
Expiry = 2007-04-21 02: 25: 28 (绝对时间)
From = bobSexample. com
MessageClass = 0x80 MessageType = 0x80
MmsVers ion = 0x90
Priority = 0x80
ReadReply = false
SenderVisibility = true
Subject = This is a test
To = [139XXXXXXXX]
Transact ionld = {auto}
Content: 接收方上线后与发起方建立会话通道的过程为现有技术， 在此不再赘述。 另外， 业务服务器生成的会话邀请信息可以不通过 CS域立即提供给接收 方， 可以釆用离线功能实体为接收方保存该会话邀请信息， 接收方上线后， 获取该会话邀请信息。 图 4 为保存会话邀请信息的会话处理方法流程图。 如 图 4所示， 该方法主要包括以下步骤：
步骤 301: 发起方通过 SIP/IP Core向接收方业务服务器发送会话请求。 步骤 302: 接收方业务服务器检测到接收方不在线时， 根据发起方的会话 请求生成会话邀请信息。
另外， 在本步骤中， 接收方业务服务器检测到接收方不在线后， 通过
SIP/IP Core向发起方回送拒绝会话响应， 发起方结束会话请求。
步骤 301、 步骤 302的实现方法分别与步骤 201、 202的实现方法相同。 在接收方业务服务器检测到接收方不在线后， 会通过 SIP/IP Core 向发 起方发送应答， 通知发起方所述接收方不在线。
步骤 303: 接收方业务服务器将生成的会话邀请信息发送给离线功能实 体。
该实施例中为离线功能实体单独设置的情况， 除此之外， 离线功能实体 也可以设置在接收方业务服务器中， 由业务服务器统一完成生成和保存会话 邀请信息的功能。
步骤 304 : 离线功能实体保存接收到的会话邀请信息。
该步骤中， 离线功能实体可以将会话邀请信息以离线消息的方式进行保 存。
步骤 305 : 接收方业务服务器检测到接收方上线后，从离线功能实体中获 取会话邀请信息。
步骤 306 : 接收方业务服务器以推送（PUSH )或拉（PULL )的方式向接收 方提供会话邀请信息。
该步骤中， 接收方上线后， 与接收方业务服务器建立会话通道， 从而获 取会话邀请信息。
另外， 在图 4 所示流程的基础上， 可以釆用一个统一存储实体代替接收 方进行会话并记录会话内容， 接收方上线后， 接收到离线功能实体发送的会 话邀请信息获知被邀请会话， 如果会话尚未结束， 接收方可以与发起方建立 会话通道， 接续该会话， 统一存储实体停止会话。 图 5 为本发明实施例提供 的代替接收方会话的方法流程图， 如图 5所示， 该方法包括以下步骤：
步骤 401 : 发起方通过 S IP/ IP Core向接收方业务服务器发送会话请求。 步骤 402 : 接收方业务服务器检测到接收方不在线时， 根据接收到的会话 请求生成会话邀请信息。
步骤 403: 接收方的业务将生成的会话邀请信息发送给离线功能实体。 步骤 404 : 离线功能实体以离线消息的方式对会话邀请信息进行保存。 步骤 405 : 接收方业务服务器通知统一存储实体参与会话。
接收方业务服务器在检测到接收方不在线时， 如果接收方定制了代替会 话的业务， 则通知统一存储实体代替接收方参与会话。
所述步骤 403与 405没有固定的先后顺序， 也可以同时进行。
在步骤 405之后， 统一存储实体会向接收方业务服务器发送 S IP 200 ok 的响应， 接收方业务服务器再通过 CIP/ IP Core向发起方回送 S IP 200 ok的 响应， 以此通知发起方可以由统一存储实体代替接收方参与会话。
步骤 406 : 统一存储实体通过接收方业务服务器与发起方建立会话， 并记 录会话内容。
步骤 407 : 接收方业务服务器检测到接收方上线后，从离线功能实体中获 取会话邀请信息。
步骤 408 : 接收方以 PULL或 PUSH的方式获取会话邀请信息。
步骤 409 : 接收方业务服务器从统一存储实体获取会话内容。
上述步骤 407与步骤 409没有固定的先后顺序， 也可以同时进行。
步骤 410:接收方业务服务器以 PULL或 PUSH的方式向接收方提供会话内 容， 并且通知接收方接续会话。
步骤 411 : 接收方与发起方建立会话通道， 进行会话接续。
步骤 412 : 接收方业务服务器通知统一存储实体结束与发起方建立的会 话。
另外， 接收方可以根据接收到的会话邀请信息选择是否进行会话接续， 如果接收方不进行会话接续， 则统一存储实体一直代替接收方进行会话并记 录会话内容， 接收方上线后， 接收方业务服务器从统一存储实体中获取会话 记录， 并将会话记录以 PULL或 PUSH的方式提供给接收方， 即步骤 410中， 接收方业务服务器不通知接收方接续会话， 且不执行步骤 411和 412。 另外， 接收方上线后， 接收方业务服务器向接收方发送接续通知时， 也可以向统一 存储实体发送会话继续通知， 所述统一存储实体继续接收并记录发起方发送 的会话内容。
在图 5 所示实施例中， 统一存储实体代替接收方参与会话， 还可以通过 S IP 消息通知发送方统一存储实体代替接收方参与会话， 同时， 可以通过 CS 域将会话邀请信息和 I或统一存储实体代替接收方参与会话的通知提供给接 收方。 以上实施例所提供的方法可以单独存在， 也可以是以上实施例所述方法 的组合。 例如， 在图 5 所示的实施例中， 根据预先的设置， 也可以为统一存 储实体代替接收方参与会话， 同时， 利用图 3实施例中的通过 CS域的方式， 将会话邀请信息提供给接收方； 更进一步地， 接收方接收到带有激活标识的 会话邀请信息后， 可以自动激活上线， 与发起方进行会话接续。
除了上述实施例所提供的方法外， 当接收方业务服务器检测到接收方不 在线时， 如果同时检测到接收方正在使用其它消息业务， 则可以根据用户的 设置或运营商的策略， 通过接收方正在使用的消息业务将对接收方的会话请 求发送给接收方， 图 6 为本发明实施例提供的通过接收方正在使用的消息业 务处理会话的方法流程图， 如图 6所示， 该方法可以包括以下步骤：
步骤 501 : 发起方向接收方业务服务器发送会话请求。
步骤 502 : 接收方业务服务器检测到接收方不在线， 并检测到接收方正在 使用固 S业务， 则将接收到的会话请求发送给 IWF实体。
接收方业务服务器可以从接收方的归属用户服务器（HSS ) 中获取接收方 正在使用的丽 S业务信息， 并将该业务信息提供给 IW实体； 也可以从接收 方的 HSS中获取接收方正在使用的其它消息业务。
步骤 503: IW实体接收到会话请求后， 将会话请求转换为包含会话请求 信息的 MMS发送给接收方的多媒体消息中心 （MMSC )。
步骤 504 : 接收方的 MMSC将接收到的包含会话请求信息的 MMS发送给接 收方。
步骤 505 : 接收方接收到包含会话请求信息的固 S后， 可以选择上线或不 上线。 如果接收方上线， 则接收方业务服务器可以将该会话接续到接收方， 发起方与接收方建立会话连接； 如果接收方不上线， 则继续执行步骤 506。
步骤 506 : IWF通过接收方业务服务器与发起方协商会话通道。
本例中， IWF可以根据用户的设置， 或运营商策略， 当接收方接收到发起 方的会话请求时， 由 IWF直接接受该会话请求， 建立接收方和 IWF之间的会 话通道， 通过该通道， 接收方和发起方通过 IWF的转换互通消息。 本步骤中协商会话通道的过程为现有技术， 在此不再赘述。
步骤 507: 会话通道协商完成后， 建立会话通道， 利用该会话通道接收发 起方的会话内容， 并将该会话内容转换为固 S形式通过接收方的固 SC发送给 接收方， 或者， 接收接收方通过接收方的 MMSC发送的 MMS , 并将该 MMS的消 息转换为 SIP (会话描述协议）域的消息， 并通过建立的会话通道发送给发起 方。
在图 6 所示流程中， 接收方业务服务器检测到接收方不在线后， 还可以 直接将会话请求发送给 IWF 实体， IWF 实体从 HSS 中获取接收方正在使用的 固 S业务信息， 将接收到的会话请求发送给 IWF实体。 另外， 接收方正在使用 的消息业务还可以为 SMS (短消息） 消息、 电子邮件消息或其它消息业务。
图 7 为本发明实施例提供的通过接收方正在使用的消息业务处理会话的 另一方法流程图， 在该流程中， IFW除了和发起方建立会话通道外， 还可以通 过某些业务与接收方建立会话通道， 如图 7所示， 该方法可以包括以下步骤： 步骤 601 : 发起方向接收方业务服务器发送会话请求。
步骤 602: 接收方业务服务器检测到接收方不在线， 并检测到接收方正在 使用即时通信（IMPS ) 消息业务， 则将接收到的会话请求发送给 IWF实体。
接收方业务服务器可以从接收方的 HSS 中获取接收方正在使用的业务信 息。
步骤 603: IW实体接收到会话请求后， 将会话请求转换为包含会话请求 信息的 IMPS消息， 发送给即时通信消息中心 （IMPSC )。
步骤 604: IMPS将包含会话请求信息的 IMPS消息发送给接收方。
步骤 605: IWF实体通过接收方业务服务器与发起方协商会话通道， 并通 过 IMPSC与接收方协商会话通道。
步骤 606: IWF实体与发起方建立会话通道，并且与接收方建立会话通道。 步骤 607: IWF实体通过与发起方建立的会话通道接收发起方发送的会话 内容， 并将该会话内容转换为 IMPS消息形式通过与接收方建立的通道发送给 接收方； 或者， 通过与接收方建立的会话通道接收接收方发送的 IMPS形式的 消息， 并将该 IMPS消息的内容转换为 SIP域的消息， 通过与发起方建立的会 话通道发送给发起方。
在图 7 所示的流程中， 接收方业务服务器检测到接收方不在线后， 还可 以直接将会话请求发送给 IWF实体， IWF实体检测到接收方正在使用 IMPS消 息业务时， 将接收到的会话请求发送给 IW实体。
以上所述实施例均是发送方向接收方发送会话请求时的处理流程， 当发 送方向接收方发送离散消息， 而不是会话请求时， 如果接收方不在线， 则同 样可以通过接收方正在使用的其它消息业务， 将该离散消息的内容发送给接 收方。 图 8 为本发明实施例提供的接收方不在线时， 处理离散消息的方法流 程图， 如图 8所示， 该方法可以包括以下步骤：
步骤 701 : 接收方业务服务器接收到发起方发送的 SIP离散消息。
步骤 702: 接收方业务服务器检测到接收方不在线， 并检测到接收方正在 使用固 S业务， 则将接收到的 SIP离散消息发送给 IWF实体。
步骤 703: IWF实体接收到 SIP离散消息后， 将 SIP离散消息转换为包含 该离散消息内容的固 S, 并将该固 S发送给 MMSC。
步骤 704: 固 SC将 IWF实体发送的固 S发送给接收方。
本步骤之后，接收方通过 MMSC向 IWF实体回复接收到该固 S的响应， IWF 实体也通过消息服务器向发起方回复接收方接收到丽 S消息的响应。
如果发送方向接收方发送会话请求和离散消息， 如果接收方不在线， 还 可以根据接收方的设置， 将该会话请求或离散消息发送给接收方授权的其它 在线用户。 图 9 为本发明实施例提供的将会话请求转发到授权用户的方法流 程图， 在该实施例中是以发送方向接收方发送会话请求为例进行的描述， 当 发送方向接收方发送离散消息时， 同样可以釆用该实施例所提供的流程。 如 图 9所示， 该方法可以包括以下步骤： 步骤 801 : 接收方业务服务器接收到发起方发送的会话请求。 步骤 802 : 接收方业务服务器检测到接收方不在线， 并获取到接收方设置 的授权用户信息。
本步骤中， 接收方业务服务器检测到接收方不在线时， 可以从接收方的 HSS中获取到接收方是否设置授权用户， 如果设置授权用户， 进一步获取授权 用户信息。
步骤 803: 接收方业务服务器根据接收方的设置， 将该会话请求转发给授 权用户的业务服务器。
步骤 804： 授权用户的业务服务器将接收到的会话请求发送给授权用户。 步骤 805 : 授权用户接收到会话请求后， 与发起方建立会话通道， 代替接 收方与发起方完成会话。
在图 9所示的流程中， 接收方业务服务器还可以通过 IWF实体利用接收 方正在使用的消息业务， 将授权用户代替接收方进行会话的通知发送给接收 方， 发送通知的方法可以釆用图 8 所示流程来完成。 也可以将该通知通过离 线功能实体对该通知进行保存， 接收方上线时获取该通知。 另外， 还可以通 过统一存储实体保存发起方与授权用户之间的会话内容。
接收方业务服务器还可以通过 S IP域将授权用户代理接收方进行会话的 通知发送给发起方。
另外， 图 9 所示的流程中， 接收方业务服务器还可以记录发起方和授权 用户之间进行的会话内容， 以便接收方对会话内容进行查找。
图 10为本发明实施例提供的第二种会话处理的系统结构图， 如图 10所 示， 该系统包括： 接收方业务服务器 91 0、 和 IWF实体 920。
接收方业务服务器 91 0 , 用于接收发送方发送的会话请求， 如果检测到接 收方不在线， 则将该会话请求发送给 IWF实体 920。
IWF实体 920 , 接收接收方业务服务器 910发送的会话请求， 利用接收方 正在使用的消息业务， 将该会话请求发送给接收方或代替接收方接受该会话 请求。
该系统还可以包括： HSS 940 , 用于保存接收方正在使用的消息业务信 息。
接收方业务服务器 910, 还用于从 HSS 940中获取接收方正在使用的消息 业务信息；
IWF实体 920, 用于从 HSS 940或接收方业务服务器 910中获取接收方正 在使用的消息业务信息， 并利用接收方正在使用的消息业务信息执行将该会 话请求发送给接收方或代替接收方接受该会话请求的操作。
其中， IWF实体 920可以包括： 接收单元 921、 消息转换单元 922和发送 单元 923;
接收单元 921 , 用于接收接收方业务服务器 910发送的会话请求； 消息转换单元 922 ,用于将接收单元 921接收到的会话请求转换为接收方 正在使用的消息业务的消息；
发送单元 923 , 用于将消息转换单元 922转换后的消息发送给接收方。 该 IWF实体 920还可以包括： 消息获取单元 924 , 用于从 HSS 940或接收 方业务服务器 910 中获取接收方正在使用的消息业务信息， 并将获取的该消 息业务信息发送给消息转换单元 922;
消息转换单元 922 ,还用于接收消息获取单元 924发送的所述消息业务信 息， 利用该消息业务信息执行将接收单元 921 接收到的会话请求转换为接收 方正在使用的消息业务的消息的操作。
该 IWF实体 920还可以包括： 会话通道建立单元 925 , 用于与发起方建立 会话通道；
接收单元 921 ,还用于通过会话通道建立单元 925建立的会话通道接收发 起方发送的会话内容；
消息转换单元 922 ,还用于将接收单元 921接收到的会话内容转换为接收 方正在使用的消息业务的消息。 会话通道建立单元 925 , 还用于与接收方建立会话通道；
发送单元 923 ,还用于将消息转换单元 922转换后的消息通过会话通道建 立单元 925建立的会话通道发送给接收方。
图 10所示的系统可以用于实现图 6和图 7所示的方法流程。
图 11为本发明实施例提供的第三种会话处理的系统结构图， 如图 11所 示， 该系统包括： 接收方业务服务器 1010和授权用户的业务服务器 1020; 接收方业务服务器 1010 , 用于接收发起方发送的会话请求， 如果检测到 接收方不在线， 根据接收方设置的授权用户信息， 将该会话请求发送给授权 用户的业务 ^良务器 1020;
授权用户的业务服务器 1020 ,用于将接收方业务服务器 1010发送的会话 请求转发给授权用户。
该系统还可以包括：
授权用户 1030 , 接收到授权用户的业务服务器 1020发送的会话请求后， 与发起方建立会话通道， 代替接收方与发起方进行会话。
该系统还可以包括： IWF实体 1 040或离线功能实体 1 050;
接收方业务服务器 1010 , 还用于将授权用户代替接收方与发起方进行会 话的通知发送给 IWF实体 1040或离线功能实体 1050;
IWF实体 1040 , 用于接收接收方业务服务器 1010发送的通知， 并将该通 知通过接收方正在使用的业务消息或通过 CS域发送给接收方；
离线功能实体 1050 , 用于接收接收方业务服务器 1010发送的通知， 并将 该通知以离线消息的方式发送给接收方。
接收方业务服务器 1010 , 还用于将授权用户代替接收方与发起方进行会 话的通知发送给发起方。
该系统还可以包括： 接收方统一存储实体， 用于保存发起方与授权用户 之间的会话内容。
该系统还可以包括： HSS 1060 , 用于存储接收方设置的授权用户信息； 接收方业务服务器 1010, 还用于从 HSS 1060中获取接收方设置的授权用 户信息。
其中，接收方业务服务器 1010可以包括：接收单元 1011 ,检测单元 1012 , 授权用户信息获取单元 1013 , 发送单元 1014;
接收单元 1011 , 用于接收发起方 1010发送的会话请求；
检测单元 1012 , 用于检测接收方是否在线；
授权用户信息获取单元 1013 ,用于在检测单元 1012检测到接收方不在线 时， 获取接收方设置的授权用户信息；
发送单元 1014 ,用于根据授权用户信息获取单元 1013获取的授权用户信 息， 将接收单元 1011接收的会话请求发送给授权用户。
该接收方业务服务器 1010还包括： 通知单元 1015 , 用于生成授权用户代 替接收方与发起方进行会话的通知；
发送单元 1014 , 用于将通知单元 1015生成的通知通过 IWF实体、或离线 功能实体， 或利用接收方正在使用的消息业务发送给接收方； 和 /或， 将所述 通知单元 1015生成的通知发送给发起方。
图 11所示的系统可以用于实现图 9所示的方法流程。
图 12为本发明实施例提供的第一种消息处理的系统结构图， 如图 12所 示， 该系统包括： 接收方业务服务器 1110和 IWF实体 1140;
接收方业务服务器 1110 , 用于接收发起方发送的离散消息， 如果检测到 接收方不在线， 并检测到接收方正在使用其它消息业务， 则将该离散消息发 送给 IWF实体 1140;
IWF实体 1140 , 用于接收接收方业务服务器 1110发送的离散消息， 并将 该离散消息转换为接收方正在使用的其它消息， 发送给接收方。
该系统还可以包括 HSS 1130 , 用于存储接收方正在使用的业务信息； 接收方业务服务器 1110, 还用于从 HSS 1130中获取接收方正在使用的业 务信息， 根据该业务信息检测接收方正在使用的其它消息业务。 该系统还可以包括 IWF实体 1140 ,用于接收接收方业务服务器 1110发送 的离散消息， 并将该离散消息转换为接收方正在使用的其它消息业务的消息， 并通过接收方正在使用的消息业务对应的消息中心将转换后的消息发送给接 收方。
其中， IWF实体 1140包括： 接收单元 1141、 消息转换单元 1142和发送 单元 1143;
接收单元 1141 , 用于接收接收方业务服务器 1110发送的离散消息； 消息转换单元 1142 ,用于将接收单元 1141接收到的离散消息转换为接收 方正在使用的消息业务的消息；
发送单元 1143 , 用于将消息转换单元 1142转换后的消息发送给接收方。 该 IWF实体 1140还包括： 消息获取单元 1144 , 用于从 HSS 1130或接收 方业务服务器 1110中获取接收方正在使用的消息业务信息， 并将获取的该消 息业务信息发送给消息转换单元 1142;
消息转换单元 1142 ,还用于接收消息获取单元 1144发送的消息业务信息， 利用该消息业务信息执行将接收单元 1141接收到的离散消息转换为接收方正 在使用的消息业务的消息的操作。
图 12所示的系统可以用于实现图 8所示的方法流程。
图 13为本发明实施例提供的第二种消息处理系统结构图， 其特征在于， 该系统包括： 接收方业务服务器 1210、 授权用户的业务服务器 1220;
接收方业务服务器 1210 , 用于接收发起方发送的离散消息， 如果检测到 接收方不在线， 根据接收方设置的授权用户信息， 将所述离散消息转发给授 权用户的业务服务器 1220;
授权用户的业务服务器 1220 ,用于将接收方业务服务器 1210发送的离散 消息发送给授权用户。
该系统还可以包括： IW实体 1240或离线功能实体 1250;
接收方业务服务器 1210 , 还用于将授权用户代替接收方接收离散消息的 通知发送给 IWF实体 1240或离线功能实体 1250;
IWF实体 1240 , 用于接收接收方业务服务器 1210发送的通知， 并将该通 知通过接收方正在使用的业务消息或通过 CS域发送给接收方；
离线功能实体 1250 , 用于接收接收方业务服务器 1210发送的通知， 并将 该通知以离线消息的方式发送给接收方。
接收方业务服务器 1210 , 还用于将授权用户代替接收方接收离散消息的 通知发送给所述发起方。
其中， 接收方业务服务器 1210包括： 接收单元 1211 , 检测单元 1212 , 授权用户信息获取单元 1213 , 发送单元 1214;
接收单元 1211 , 用于接收发起方发送的离散消息；
检测单元 1212 , 用于检测接收方是否在线；
授权用户信息获取单元 1213 ,用于在检测单元 1212检测到接收方不在线 时， 获取接收方设置的授权用户信息；
发送单元 1214 ,用于根据授权用户信息获取单元 1213获取的授权用户信 息， 将接收单元 1211接收的离散消息发送给授权用户。
该接收方业务服务器还可以包括： 通知单元 1215 , 用于生成授权用户代 替接收方接收离散消息的通知；
发送单元 1214 , 还用于将通知单元 1215生成的通知通过 IWF实体 1240、 或离线功能实体 1250 , 或利用接收方正在使用的消息业务发送给接收方； 和 / 或， 将通知单元 1215生成的通知发送给发起方。
图 13所示的系统可以用于实现图 9所示的方法流程。
由以上描述可以看出， 本发明实施例提供的会话处理方法、 系统和业务 服务器， 通过接收方业务服务器检测到接收方业务服务器不在线时， 根据接 收到的会话请求生成会话邀请信息提供给接收方， 使得接收方即使在发起方 没有提供会话内容的情况下，接收方也能够获知不在线时的会话邀请信息， 而 不像现有技术中， 如果发起方不进行语音留言， 接收方则不能获知不在线时 受到的会话邀请。
更进一步地， 接收方可以在不在线的状态下及时接收到会话邀请信息， 并且， 接收方还可以通过接收会话邀请信息自动激活上线， 及时与发起方建 立会话。
更进一步地， 该方法可以通过离线功能实体以离线消息的实行保存会话 邀请信息， 待接收方上线时， 向接收方提供会话邀请信息， 使接收方获知不 在线时受到的会话邀请， 并且， 可以通过设置统一存储实体代替接收方参与 会话， 并记录会话内容， 在接收方收到会话邀请信息后， 可以获取记录的会 话内容， 并且， 在会话尚未结束时， 可以选择与发起方进行会话接续。 从而 丰富了用户的业务体验。
以上所述仅为本发明的较佳实施例而已， 并不用以限制本发明， 凡在本 发明的精神和原则之内， 所做的任何修改、 等同替换、 改进等， 均应包含在 本发明保护的范围之内。

Claims

权 利 要求 书
1、 一种会话处理的方法， 其特征在于， 该方法包括：
接收方业务服务器接收发起方发送的会话请求；
如果检测到接收方不在线， 根据接收到的会话请求生成会话邀请信息， 并 将所述会话邀请信息提供给接收方。
2、 根据权利要求 1所述的会话处理的方法， 其特征在于， 所述会话请求包 括发起方的标识、 以及接收方标识；
所述根据接收到的会话请求生成会话邀请信息包括： 根据包含发起方标识 和接收方标识的会话请求以及会话发起时间， 生成包含发起方标识、 接收方标 识、 以及会话发起时间中的一个或多个的会话邀请信息。
3、 根据权利要求 1所述的会话处理的方法， 其特征在于， 所述将会话邀请 信息提供给接收方的步骤包括：
接收方业务服务器将所述会话邀请信息发送给互联功能实体， 所述互联功 能实体根据接收到的会话邀请信息生成携带会话邀请信息的消息， 并将所述携 带会话邀请信息的消息发送给消息中心， 所述消息中心将所述转换后的会话邀 请信息发送给接收方。
4、 根据权利要求 3所述的会话处理的方法， 其特征在于， 所述携带会话邀 请信息的消息为短消息， 所述消息中心为短消息中心； 或者，
所述携带会话邀请信息的消息为多媒体消息， 所述消息中心为彩信中心。
5、 根据权利要求 3所述的会话处理的方法， 其特征在于， 所述接收方业务 服务器生成的会话邀请信息中包含激活标识；
当所述携带会话邀请信息的消息为短消息时， 所述互联功能实体生成的携 带会话邀请信息的消息中包含激活接收方客户端的头域；
当所述携带会话邀请信息的消息是多媒体消息时， 所述互联功能实体生成 的携带会话邀请信息的消息的内容类型字段中包含激活接收方客户端的参数指 示；
该方法还包括： 接收方获取到转换后的、 包含激活接收方客户端头域的参 数指示的、 携带会话邀请信息的消息时， 自动上线与发起方建立会话连接， 或 者不上线。
6、 根据权利要求 1所述的会话处理的方法， 其特征在于， 所述将会话邀请 信息提供给接收方的步骤包括：
接收方业务服务器将生成的会话邀请信息发送给离线功能实体， 离线功能 实体以离线消息的方式保存所述会话邀请信息； 接收方业务服务器检测到接收 方上线后， 从离线功能实体中获取保存的会话邀请信息， 将所述会话邀请信息 提供给接收方。
7、 根据权利要求 5所述的会话处理的方法， 其特征在于， 该方法还包括： 接收方业务服务器发送包含激活标识的会话邀请信息时， 向发起方回送振铃响 应， 发起方等待接收方上线； 如果在振铃期间的设定时间内接收方没有上线， 则接收方的服务器向发起方回送超时响应， 发起方结束会话请求； 如果在振铃 期间接收方上线， 则接收方业务服务器将会话请求发送给接收方， 接收方与发 起方建立会话。
8、 根据权利要求 3所述的会话处理的方法， 其特征在于， 该方法还包括： 接收方业务服务器检测到接收方不在线后， 触发统一存储实体代替接收方与发 起方进行会话， 并记录会话内容； 接收方业务服务器检测到接收方上线后， 从 统一存储实体中获取会话内容， 并将所述会话内容提供给接收方； 在所述触发统一存储实体代替接收方与发起方进行会话之后还包括： 接收 方业务服务器将统一存储实体代替接收方与发起方进行会话的通知发送给发起 方； 和 /或，
接收方业务服务器将统一存储实体代替接收方与发起方进行会话的通知通 过 IW实体或离线功能实体发送给接收方。
9、 根据权利要求 8所述的会话处理的方法， 其特征在于， 该方法还包括： 接收方上线后， 接收方业务服务器检测到统一存储实体与发起方进行的会话尚 未结束时， 则通知接收方与发起方建立会话连接。
10、 一种会话处理的系统， 其特征在于， 该系统包括： 发起方、 接收方业 务服务器、 以及接收方；
发起方， 用于向接收方业务服务器发送会话请求；
接收方业务服务器， 用于接收发起方发送的会话请求， 检测到接收方不在 线时， 根据接收到的会话请求生成会话邀请信息， 并将所述会话邀请信息提供 给接收方；
接收方， 用于获取接收方业务服务器提供的会话邀请信息。
11、根据权利要求 10所述的会话处理的系统， 其特征在于， 该系统还包括： 互联功能实体和消息中心；
互联功能实体， 用于接收所述接收方业务服务器发送的会话邀请信息， 根 据接收到的会话邀请信息生成携带会话邀请信息的消息， 并将所述携带会话邀 请信息的消息发送给消息中心；
消息中心， 用于接收互联功能实体发送的所述携带会话邀请信息的消息， 并将所述携带会话邀请信息的消息发送给接收方。
12、根据权利要求 10所述的会话处理的系统， 其特征在于， 该系统还包括： 互联功能实体和无线应用协议网关；
互联功能实体， 用于接收所述接收方业务服务器发送的会话邀请信息， 根 据接收到的会话邀请信息生成携带会话邀请信息的消息， 并将所述携带会话邀 请信息的消息发送给无线应用协议网关；
所述无线应用协议网关， 用于接收互联功能实体发送的所述携带会话邀请 信息的消息， 并将所述携带会话邀请信息的消息以无线应用协议推的方式提供 给接收方。
13、 根据权利要求 11或 12所述的会话处理的系统， 其特征在于， 所述接 收方业务服务器生成的会话邀请信息中包含激活标识；
所述互联功能实体生成的携带会话邀请信息的消息中包含激活接收方客户 端的头域；
所述接收方， 接收到包含激活接收方客户端的头域的、 携带会话邀请信息 的消息时， 自动上线与发起方建立会话连接， 或者不上线。
14、根据权利要求 10所述的会话处理的系统， 其特征在于， 该系统还包括： 离线功能实体， 用于接收并保存所述接收方业务服务器发送的会话邀请信息， 当接收到所述接收方业务服务器发送的上线通知时， 将保存的会话邀请信息提 供给所述接收方业务服务器；
所述接收方业务服务器， 还用于检测到接收方上线时， 向所述离线功能实 体发送上线通知， 获取离线功能实体保存的会话邀请信息， 并提供给所述接收 方。
15、 根据权利要求 11或 12所述的会话处理的系统， 其特征在于， 该系统 还包括： 统一存储实体， 用于接收到所述接收方业务服务器发送的不在线通知 时， 与发起方建立会话连接， 并保存发起方发送的会话内容； 接收到所述接收 方业务服务器发送的上线通知后， 将保存的会话内容提供给所述接收方业务服 务器；
所述接收方业务服务器， 还用于检测到接收方不在线时， 向统一存储实体 发送不在线通知， 检测到接收方上线时， 向所述统一存储实体发送上线通知， 将所述统一存储实体发送的会话内容提供给接收方；
所述接收方， 还用于接收所述接收方业务服务器提供的所述会话内容。
16、 一种会话和消息的处理方法， 其特征在于， 该方法包括：
接收方业务服务器接收发起方发送的会话请求或离散消息；
如果检测到接收方不在线， 则根据用户设置或运营商策略， 将所述会话请 求或离散消息发送给互联功能实体；
所述互联功能实体利用接收方正在使用的消息业务， 将所述会话请求或离 散消息发送给接收方或代替接收方接受该会话请求或离散消息。
17、 根据权利要求 16所述的会话和消息的处理方法， 其特征在于， 该方法 还包括： 接收方业务服务器从归属用户服务器中获取接收方正在使用的消息业 务信息， 并将该消息业务信息发送给所述互联功能实体； 或者， 互联功能实体 从归属用户服务器中获取接收方正在使用的消息业务信息；
所述互联功能实体利用获取到的所述消息业务信息执行所述利用接收方正 在使用的消息业务， 将所述会话请求或离散消息发送给接收方或代替接收方用
18、 根据权利要求 16所述的会话和消息的处理方法， 其特征在于， 所述利 用接收方正在使用的消息业务， 将所述会话请求或离散消息发送给接收方包括： 将所述会话请求或离散消息转换为接收方正在使用的消息业务类型的消息， 并 将该转换后的消息发送给接收方。
19、 根据权利要求 16所述的会话和消息的处理方法， 其特征在于， 在所述 互联功能实体代替接收方接受该会话请求之后还包括： 所述互联功能实体与发 起方建立会话通道， 利用所述会话通道接收发起方的会话内容， 并将该会话内 容转换为接收方正在使用的消息业务类型的消息， 并将该转换后的消息发送给 接收方； 或者， 接收所述接收方发送来的消息， 将所述接收方发送来的消息转 换为会话描述协议域的消息， 通过建立的会话通道发送给发起方。
20、 一种会话和消息处理方法， 其特征在于， 该方法包括：
接收方业务服务器接收发起方发送的会话请求或离散消息；
如果检测到接收方不在线， 根据所述接收方设置的授权用户信息， 将所述 会话请求或离散消息通过在线的授权用户的业务服务器转发给授权用户。
21、 根据权利要求 20所述的方法 其特征在于， 该方法还包括：
授权用户接收到所述会话请求后， 与发起方建立会话通道， 代替接收方与 发起方进行会话。
22、 根据权利要求 21所述的方法， 其特征在于， 该方法还包括： 接收方业 务服务器将授权用户代替接收方与发起方进行会话的或接收消息的通知通过互 联功能实体利用接收方正在使用的消息业务发送给接收方， 或通过离线功能实 体对所述通知进行保存， 接收方上线时获取所述通知； 和 /或， 接收方统一存储 实体保存发起方与所述授权用户之间的会话内容。
23、 一种会话和消息处理系统， 其特征在于， 该系统包括： 接收方业务服 务器、 以及互联功能实体；
接收方业务服务器， 用于接收发送方发送的会话请求或离散消息， 如果检 测到接收方不在线， 则根据用户设置或运营商策略将所述会话请求或离散消息 发送给所述互联功能实体；
互联功能实体， 接收所述接收方业务服务器发送的会话请求或离散消息， 利用接收方正在使用的消息业务， 将所述会话请求或离散消息发送给接收方或 代替接收方接受该会话请求或离散消息。
24、 根据权利要求 23所述的会话和消息处理系统， 其特征在于， 该系统还 包括： 归属用户服务器， 用于保存所述接收方正在使用的消息业务信息；
所述接收方业务服务器， 还用于从所述归属用户服务器中获取所述接收方 正在使用的消息业务信息；
所述互联功能实体， 还用于从所述归属用户服务器或接收方业务服务器中 获取所述接收方正在使用的消息业务信息， 并利用所述接收方正在使用的消息 业务信息执行将所述会话请求发送给接收方或代替接收方接受该会话请求的操 作。
25、 一种会话和消息处理系统， 其特征在于， 该系统包括： 接收方业务服 务器、 和授权用户的业务服务器；
接收方业务服务器， 用于接收发起方发送的会话请求或离散消息， 如果检 测到接收方不在线， 根据接收方设置的授权用户信息， 将所述会话请求或离散 消息发送给授权用户的业务服务器；
授权用户的业务服务器， 用于将所述接收方业务服务器发送的会话请求或 离散消息转发给授权用户。
26、 根据权利要求 25所述的系统， 其特征在于， 该系统还包括： 互联功能 实体或离线功能实体；
所述接收方业务服务器， 还用于将授权用户代替接收方与发起方进行会话 的通知发送给所述互联功能实体或离线功能实体；
所述互联功能实体， 用于接收所述接收方业务服务器发送的通知， 并将所 述通知通过接收方正在使用的业务消息或通过电路交换 CS域发送给接收方； 所述离线功能实体， 用于接收所述接收方业务服务器发送的通知， 并将所 述通知以离线消息的方式发送给接收方。
27、 根据权利要求 25所述的系统， 其特征在于， 该系统还包括： 接收方统 一存储实体， 用于保存发起方与所述授权用户之间的会话内容。
归属用户服务器， 用于存储接收方设置的授权用户信息。
PCT/CN2007/071316 2007-04-30 2007-12-24 A method, system for processing session and message Ceased WO2008131627A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP07846142A EP2093946A4 (en) 2007-04-30 2007-12-24 METHOD, SESSION AND MESSAGE PROCESSING SYSTEM
US12/508,301 US20090305733A1 (en) 2007-04-30 2009-07-23 Method and system for processing sessions and messages

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200710107161.0 2007-04-30
CN200710107161 2007-04-30
CN200710149583.4 2007-09-12
CN2007101495834A CN101299785B (zh) 2007-04-30 2007-09-12 一种会话处理的方法、系统以及业务服务器

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/508,301 Continuation US20090305733A1 (en) 2007-04-30 2009-07-23 Method and system for processing sessions and messages

Publications (1)

Publication Number Publication Date
WO2008131627A1 true WO2008131627A1 (en) 2008-11-06

Family

ID=39925185

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/071316 Ceased WO2008131627A1 (en) 2007-04-30 2007-12-24 A method, system for processing session and message

Country Status (4)

Country Link
US (1) US20090305733A1 (zh)
EP (1) EP2093946A4 (zh)
CN (1) CN101299785B (zh)
WO (1) WO2008131627A1 (zh)

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101400021A (zh) * 2008-10-15 2009-04-01 中兴通讯股份有限公司 PoC回呼请求处理方法、发送/接收装置、移动终端
US9397862B2 (en) 2008-12-12 2016-07-19 At&T Intellectual Property I, L.P. Method and apparatus for completing a circuit switched service call in an internet protocol network
CN102158466B (zh) * 2010-02-11 2013-10-09 华为终端有限公司 用户设备间媒体转移方法和应用服务器
KR101701832B1 (ko) * 2010-05-31 2017-02-02 엘지전자 주식회사 이동 단말기 및 이것의 그룹 대화 제어 방법
CN102457815A (zh) * 2010-10-18 2012-05-16 中国移动通信集团北京有限公司 一种PoC业务回呼请求处理方法、装置及系统
CN102075531B (zh) * 2010-12-27 2013-01-30 北京像素软件科技股份有限公司 一种为客户端传输数据的方法
US9819700B2 (en) * 2011-05-30 2017-11-14 Telefonaktiebolaget Lm Ericsson (Publ) System and method for passive communication services
GB201210596D0 (en) 2012-06-14 2012-08-01 Microsoft Corp Notification of communication events
CN103338192B (zh) * 2012-06-14 2017-07-18 微软技术许可有限责任公司 用于在呼叫者与被呼叫者之间建立呼叫的网络节点和方法
GB201210598D0 (en) 2012-06-14 2012-08-01 Microsoft Corp Notification of communication events
GB201210600D0 (en) 2012-06-14 2012-08-01 Microsoft Corp Call invites
CN103856644A (zh) * 2012-11-30 2014-06-11 上海鱼游网络科技有限公司 一种网络电话的提示方法及系统
US9811808B2 (en) 2013-02-12 2017-11-07 International Business Machines Corporation Meeting notifications for offline invitees
CN107689939A (zh) * 2016-08-05 2018-02-13 阿里巴巴集团控股有限公司 消息交互方法和装置
CN109151235B (zh) * 2018-10-22 2021-03-30 奇酷互联网络科技（深圳）有限公司 远程通信群组的协同操控方法、服务器和存储装置
CN110266582B (zh) * 2019-05-29 2022-08-26 深圳市梦网科技发展有限公司 一种消息推送方法、系统、服务器及通信终端
CN111028837B (zh) * 2019-12-16 2022-10-04 深圳云之家网络有限公司 语音会话方法、语音识别系统及计算机存储介质
CN113098920A (zh) 2020-01-09 2021-07-09 京东方科技集团股份有限公司 会话建立方法、装置及其相关设备
CN114554427B (zh) * 2020-11-24 2023-10-17 中国移动通信集团有限公司 一种5g消息处理方法、装置、设备及计算机存储介质
CN113673963A (zh) * 2021-09-01 2021-11-19 武汉悦学帮网络技术有限公司 一种账号激活方法、装置、计算机设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1777155A (zh) * 2005-12-08 2006-05-24 中国科学院计算技术研究所 基于会话启动协议的即时通讯系统中的即时消息过滤方法
CN1838643A (zh) * 2005-03-25 2006-09-27 华为技术有限公司 一种即时消息的接收方法
WO2006105813A1 (en) * 2005-04-04 2006-10-12 Telefonaktiebolaget Lm Ericsson (Publ) Answer modes in push-to-talk mobile communication services

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6564261B1 (en) * 1999-05-10 2003-05-13 Telefonaktiebolaget Lm Ericsson (Publ) Distributed system to intelligently establish sessions between anonymous users over various networks
US20070047523A1 (en) * 2001-08-16 2007-03-01 Roamware, Inc. Method and system for call-setup triggered push content
FR2845235A1 (fr) * 2002-10-01 2004-04-02 Cegetel Procede de messagerie vocale instantanee et dispositif de mise en oeuvre d'un tel procede
US20040176128A1 (en) * 2003-01-30 2004-09-09 3Com Corporation System, mobile communications unit, and softswitch method and apparatus for establishing an Internet Protocol communication link
US20060168037A1 (en) * 2004-12-21 2006-07-27 Alcatel Systems and methods for handling presence messages
US20060252435A1 (en) * 2005-03-18 2006-11-09 Yahoo! Inc. Enabling application wakeup on a mobile device with a hybrid client
CN1859380B (zh) * 2005-07-28 2011-12-07 华为技术有限公司 一种离线消息获取方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1838643A (zh) * 2005-03-25 2006-09-27 华为技术有限公司 一种即时消息的接收方法
WO2006105813A1 (en) * 2005-04-04 2006-10-12 Telefonaktiebolaget Lm Ericsson (Publ) Answer modes in push-to-talk mobile communication services
CN1777155A (zh) * 2005-12-08 2006-05-24 中国科学院计算技术研究所 基于会话启动协议的即时通讯系统中的即时消息过滤方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2093946A4 *

Also Published As

Publication number Publication date
CN101299785B (zh) 2013-06-05
CN101299785A (zh) 2008-11-05
EP2093946A4 (en) 2010-04-21
US20090305733A1 (en) 2009-12-10
EP2093946A1 (en) 2009-08-26

Similar Documents

Publication Publication Date Title
WO2008131627A1 (en) A method, system for processing session and message
WO2009070989A1 (en) A method, system and device for performing a storing process and inquiring on sessions history records
WO2009079954A1 (en) Method, system and message service interworking module for implementing message service interworking
CN101656921B (zh) 即时消息传递状态通知方法、网元设备及网络系统
CN101222521B (zh) 基于会话发起协议的文件传输方法
US8014775B2 (en) Method and system for implementing messaging services and a message application server
CN101112071A (zh) 基于图像的一键通用户接口的图像交换
JP2013507678A (ja) コンバージドｉｐメッセージング（ｃｐｍ）とショートメッセージサービス（ｓｍｓ）との間のインターワーキングサービスを提供するための方法及びインターネットプロトコルショートメッセージゲートウェイ（ｉｐ−ｓｍ−ｇｗ）
ES2408679T3 (es) Método, dispositivo de cliente, servidor y sistema para el envío/recepción de un mensaje fuera de línea
WO2007009369A1 (en) Method and system by which instant message user can use instant message system chat room to which user unbelongs
CN101355533B (zh) 一种通信互连方法和设备
CN101204059A (zh) 一种即时通信阻塞信息通知的方法和系统
CN101426184B (zh) 富媒体通信业务的处理方法及终端设备和通信系统
CN102340456B (zh) 互通网关系统的通信方法及互通网关系统
CN103368821A (zh) 发送语音消息的方法及系统、融合消息服务器及客户端
CN101389059A (zh) 实现会话模式切换的方法、系统及设备
CN103379017B (zh) 语音留言方法及系统、融合消息服务器及客户端
CN101207577B (zh) 消息系统间的互连方法及消息互连网关
WO2012013094A1 (zh) 基于对话关联标识的会话建立方法及系统
WO2011032390A1 (zh) 一种融合ip消息的发送方法及系统
CN101400022B (zh) 标识业务类型及根据标识建立业务的方法、装置及系统
CN100442789C (zh) 一种多方通信的实现方法及系统
CN101753326A (zh) 业务互连与建立会话通道的方法互连选择功能模块和装置
WO2009006830A1 (en) Method, device and system for implementing communication between the user terminals
CN1878171B (zh) 一种聊天室中阻塞信息通知的方法

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2007846142

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE