WO2013078811A1 - 用户注册方法、交互方法及相关设备 - Google Patents

用户注册方法、交互方法及相关设备 Download PDF

Info

Publication number
WO2013078811A1
WO2013078811A1 PCT/CN2012/073779 CN2012073779W WO2013078811A1 WO 2013078811 A1 WO2013078811 A1 WO 2013078811A1 CN 2012073779 W CN2012073779 W CN 2012073779W WO 2013078811 A1 WO2013078811 A1 WO 2013078811A1
Authority
WO
WIPO (PCT)
Prior art keywords
registered user
temporary account
user
gateway
account
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/CN2012/073779
Other languages
English (en)
French (fr)
Inventor
王鹏
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 EP12738009.5A priority Critical patent/EP2621141A4/en
Publication of WO2013078811A1 publication Critical patent/WO2013078811A1/zh
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
    • 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/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
    • 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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a user registration method, an interaction method, and related devices. Background technique
  • the RCS Rich Communication Suite solution is a comprehensive communication and information sharing platform across communications networks and the Internet. Users can use the real mobile phone number as the login account, and can communicate with contacts via the RCS solution PC (Personal Computer) client, Web (Web) client or mobile client (IM: Instant Messaging) Communication, you can also upload, download, share pictures, music, video, text and more.
  • the RCS solution not only expands the user's social network, but also provides users with a diverse lifestyle.
  • the RCS solution is the same as the normal IM interaction tool. If two users need to interact with the same type of client (such as IM interaction, file interaction, etc.), the two users must be registered users of the system corresponding to the client. For example, if User A and User B need to interact through the RCS client, then User A and User B must both be registered users of the RCS system. This results in a registered user of a system (IM system, RCS system, etc.) not being able to interact with registered users who are not the system.
  • the embodiments of the present invention provide a user registration method, an interaction method, and related devices, which enable a registered user of a system to interact with a registered user who is not the system.
  • An embodiment of the present invention provides a user registration method, including:
  • Another embodiment of the present invention provides an interaction method, including:
  • Another embodiment of the present invention provides an interaction method, including:
  • the first system client used by the system registration user is forwarded to the interaction message.
  • Another embodiment of the present invention provides a system gateway, including:
  • a receiving unit configured to receive an invitation request sent by the system registration user by using the first system client, where the invitation request includes an identifier of the non-system registered user;
  • An obtaining unit configured to acquire a temporary account that is valid for the non-system registered user and is valid in the system
  • a sending unit configured to send, according to the identifier of the non-system registered user, the temporary account to a terminal used by the non-system registered user.
  • Another embodiment of the present invention provides a terminal, including:
  • a receiving unit configured to receive a temporary account from a system gateway, where the temporary account is allocated for a non-system registered user and is valid in the system;
  • a sending unit configured to send a login request to the system gateway, where the login request includes a temporary account that is received by the receiving unit;
  • the receiving unit is further configured to receive, by the system gateway, information that invites a system registered user of the non-system registered user;
  • the sending unit is further configured to send, to the system gateway, an interaction message that needs to be sent to the registered user of the system, where the interaction message carries the temporary account, so that the system gateway authenticates the temporary account.
  • the interaction message is forwarded to the first system client used by the system registration user.
  • Another embodiment of the present invention provides a system gateway, including:
  • a receiving unit configured to receive a login request sent by the second system client, where the login request carries a temporary account that is valid for the non-system registered user and is valid in the system;
  • An authentication unit configured to authenticate a temporary account carried by the login request
  • a sending unit configured to send, to the second system client, information for inviting a system registered user of the non-system registered user after the authentication unit passes the authentication of the temporary account carried by the login request;
  • the receiving unit is further configured to receive an interaction message from the second system client that needs to be sent to the registered user of the system, where the interaction message carries a temporary account;
  • the authentication unit is further configured to perform authentication on the temporary account carried by the interaction message
  • the sending unit is further configured to: after the authentication unit passes the authentication of the temporary account carried by the interaction message, And forwarding, by the first system client used by the system registration user, the interaction message.
  • the system gateway can allocate a temporary account to the non-system registered user when the system registration user requests the non-system registered user to interact, and send the temporary account.
  • Registering users with non-systems so that non-system registered users can use the temporary account to interact with system registered users, so that registered users of one system can interact with registered users who are not the system, so that system registered users can have better
  • the business experience can also increase the willingness of non-system registered users to register as system registered users.
  • FIG. 1 is a flowchart of a user registration method according to an embodiment of the present invention
  • FIG. 2 is a signaling flowchart of a user registration method according to another embodiment of the present invention
  • FIG. 3 is a flowchart of an interaction method according to an embodiment of the present invention
  • FIG. 5 is a signaling flowchart of an interaction method according to another embodiment of the present invention.
  • FIG. 6 is a structural diagram of a system gateway according to an embodiment of the present invention.
  • FIG. 7 is a structural diagram of a system gateway according to another embodiment of the present invention.
  • FIG. 8 is a structural diagram of a system gateway according to another embodiment of the present invention.
  • FIG. 9 is a structural diagram of a system gateway according to another embodiment of the present invention.
  • FIG. 10 is a structural diagram of a terminal according to an embodiment of the present invention.
  • FIG. 11 is a structural diagram of a system gateway according to another embodiment of the present invention.
  • FIG. 12 is a structural diagram of a system gateway according to another embodiment of the present invention.
  • FIG. 13 is a structural diagram of a terminal according to another embodiment of the present invention.
  • FIG. 1 is a flowchart of a user registration method according to an embodiment of the present invention.
  • the embodiment describes a process flow of a system gateway, where the system gateway is different according to the system. There are differences. For example, when the system is an RCS system, the system gateway is an RCS gateway; when the system is an IM system, the system gateway is an IM gateway.
  • This embodiment includes:
  • the invitation request received by the system gateway is based on an intra-system interaction protocol.
  • the invitation request is transmitted through the core network of the Internet Multimedia Subsystem (IMS), and the RCS gateway can specifically receive from the rest interface.
  • An invitation request where the invitation request can be in the Hyper Text Transport Protocol (HTTP) or an internal custom protocol; within the IM system, the invitation request is based on the internal protocol used by the IM system.
  • the first system client refers to a client used by a system registered user. The first system client obtains the identifier process of the non-system registered user, and may be selected by the system registration user from the address book of the operated terminal, or may be obtained by receiving the input of the registered user of the system.
  • the first system client may first query the registered user information center of the system for the identifier of the user, if not obtained from the registered user information center.
  • the user's identity can be determined that the user is not registered with the system, so that the invitation request is sent to the system gateway when it is determined that the user is not registered with the system.
  • the registered user information center of the system may be different according to different systems. For example, in the RCS system, it may be an RCS User Center (RCS UP Center); in an IM system, it may be an IM Server.
  • the identifier of the non-system registered user carried in the invitation request may be an e-mail (E-mail) address, a terminal number, or the like of the non-system registered user.
  • E-mail e-mail
  • the system gateway may allocate a temporary account to the non-system registered user. Specifically, the system gateway may directly use the identifier of the non-system registered user as a temporary account, or may assign the system serial number as a temporary account, or may allocate the temporary by other means. The embodiment of the present invention does not limit the specific form of the temporary account, nor does it limit the allocation mode of the temporary account. It only needs to ensure that the assigned temporary account is unique in the system.
  • the system gateway may also send the identifier of the non-system registered user to the registered user information center of the system. After the registered user information center of the system allocates the temporary account to the non-system registered user, the temporary account is sent to the system gateway.
  • the login password used when the temporary account is used to log in to the system may be further allocated.
  • the system gateway can send temporary accounts to non-system registered users through different channels. It can be understood that the channel for sending the temporary account by the system gateway is different from the channel for receiving the invitation request, and the receiving invitation request is generally adopted. The channel in the system, but the channel for sending the temporary account is different according to the type of the identifier of the non-system registered user. Depending on the channel, the system gateway can send the invitation request in different ways.
  • the identity of a non-system registered user is
  • the system gateway can send a temporary account to the E-mail address by means of E-mail;
  • the ID of the non-system registered user is the terminal number, the method of SMS or multimedia message is used.
  • the terminal corresponding to the terminal number sends a temporary account.
  • the login password corresponding to the temporary account is assigned, when the terminal used by the non-system registered user sends the temporary account, the login password is further sent to the terminal used by the non-system registered user.
  • the temporary account or the temporary account and the login password may be set in the invitation link, and then the invitation link is sent to the terminal used by the non-system registered user; the non-system registered user receives the invitation link. After the invitation link, you can directly click the invitation link to log in to the system, which reduces the cumbersome operation of non-system registered users.
  • the system gateway can allocate a temporary account to the non-system registered user when the system registration user requests the non-system registered user to interact, and send the temporary account to the non-system registered user, so that the non-system registered user can
  • the temporary account is used to interact with the registered user of the system, so that a registered user of a system can interact with a registered user who is not the system, so that the registered user of the system can have a better business experience, and can also increase the registration of the non-system registered user.
  • the invitation request received by the system gateway may further carry the account of the system registered user that initiated the invitation request; at this time, in order to improve the security of the system, the system gateway allocates the non-system registered user. After the temporary account, the account of the system registration user who initiated the invitation request can be further saved with the temporary account, so that in the subsequent interaction process, only the temporary account and the account of the system registered user having the invitation relationship with the temporary account are allowed to perform. Interaction.
  • the system gateway may determine, according to the account of the system registered user, whether the registered user of the system has the right to send an invitation request; and only when determining the system When a registered user has the right to send an invitation request, the temporary account assigned to the non-system registered user is obtained, thereby preventing the system registered user without the permission to send the invitation request, thereby improving the security and stability of the system.
  • what kind of permission can be sent can be set by the system operator, for example, as long as the system registration user can send an invitation request, or only allow valid system registration users to send invitation requests, or only allow a certain level And a valid system registered user sends an invitation request, etc.; wherein, a valid system registered user Refers to the system registered user who can use the system function normally. For example, if the account of a system registered user is in the loss status, the registered user of the system is not a valid system registered user.
  • the invitation request received by the system gateway further carries an interaction type that the system registration user invites the non-system registered user to interact; at this time, the system gateway acquires the system assigned to the non-system registered user.
  • the temporary account can be further registered in the interactive server corresponding to the interaction type.
  • the system gateway can register the temporary account on the IM server; when the system registration user invites the non-system registered user to interact with each other as a file interaction, The system gateway can register the temporary account on the file server.
  • the non-system registered user can subsequently authenticate with the interactive server when using the temporary account to interact with the system registered user. It can be understood that when the temporary account is allocated by the registered user information center of the system, the system gateway may not need to register the temporary account with the interactive server corresponding to the interaction type.
  • the system is an RCS system
  • the RCS gateway obtains a temporary account that is valid for the non-system registered user
  • the Internet Protocol Multimedia Subsystem IMS: IP multimedia) Subsystem
  • FIG. 2 is a signaling flow of a user registration method according to another embodiment of the present invention.
  • the embodiment specifically describes a process for registering a user when an RCS registered user invites a non-RCS registered user to perform an IM interaction in an RCS system.
  • This embodiment includes:
  • the first system client After receiving the instruction that the user A initiates the IM interaction with the user B, the first system client sends a query request to the RCS UP Center to query whether the user B is an RCS registered user, and the query request carries the user B. logo.
  • User A is an RCS registered user, and the first system client is an RCS standard client. After logging in to the first system client, user A can select from the contact list of the first system client or the address book of the terminal. User B's identity, or User A's identity may be entered by User A.
  • the RCS UP Center queries, according to the identifier of the user B, whether the user B is an RCS registered user.
  • the query result is carried in the query response and returned to the first system client.
  • the first system client After receiving the query response, the first system client obtains the query result. If the query result is that the user B is the RCS registered user, the normal RCS interaction process is started, and the normal RCS interaction process is not described in the embodiment of the present invention; If the query result is that the user B is a non-RCS registered user, the first system client sends an invitation request to the RCS gateway, where the invitation request carries the user A's identity verification information and the user B's identity, where the user A's identity verification information includes User A's account number and login password and other information.
  • the user ID of the user B is an E-mail address, and the E-mail is specifically b@cc.com.
  • the invitation request provided by an embodiment of the present invention may be as follows:
  • the authentication information of user A is stored in the Authorization header field, and the content of the Authorization header field is a string obtained by AAA64 encryption of the authentication information of A.
  • the RCS gateway After receiving the invitation request, the RCS gateway verifies whether the user A has the right to send an invitation request by using the authentication information of the user A carried in the invitation request, and allocates a temporary account and login to the user B when determining that the user A has the right to send the invitation request. password.
  • the account in the RCS system may be a Session Initiation Protocol Uniform Resource Identifier (SIP URI).
  • SIP URI Session Initiation Protocol Uniform Resource Identifier
  • the RCS gateway uses the E-mail address to generate a temporary account, and the generated temporary account is SIP: B@cc.com.
  • the RCS gateway may add the temporary account information allocated to the user B in the temporary account table. Specifically, the temporary account table may save the identifier of the user B as the user. B temporary account and login password. In this case, before the temporary account is assigned to the user B, the RCS gateway can first determine whether the temporary account has been assigned to the user B in the temporary account table. If the temporary account has been assigned, the RCS gateway can directly use the record in the temporary account table. Temporary account assigned to User B.
  • the RCS gateway may further record the invitation relationship between the user A and the user B in the invitation relationship table, where the account of the user A and the user B may be recorded in the invitation relationship table.
  • the temporary account wherein the saved user A's account may be at least one of user A's user identity (UID: User Identity) and user A's SIP URI.
  • the time for assigning the temporary account and the validity period of the temporary account may be further recorded in the invitation relationship table; wherein, the validity period is the default validity period.
  • the RCS gateway After receiving the invitation request sent by the first system client, the RCS gateway returns an invitation request response (not shown) to the first system client.
  • the RCS gateway sends a first registration request to the IMS core network, to request the IMS core network element to register the temporary account allocated to the user B, where the first registration request carries the temporary account assigned by the user B.
  • the IMS core network sends a first registration response to the RCS gateway, where the first registration response carries information about whether the temporary account allocated by the user B is successfully registered. This embodiment only considers the case of successful registration.
  • the RCS gateway sends a second registration request to the IM server, to request the IM server to register the temporary account allocated for the user B, where the second registration request carries the temporary account assigned to the user B.
  • the IM server sends a second registration response to the RCS gateway, where the second registration response carries information about whether the temporary account allocated by the user B is successfully registered. This embodiment only considers the case of successful registration.
  • the RCS gateway sets the temporary account and the login password assigned to the user B in the invitation link, and sends an E-mail to the E-mail address of the user B, where the E-mail includes the invitation link; wherein, to the user B
  • the E-mail address is sent to the E-mail, specifically to send an E-mail to the E-mail server where the E-mail address is located, and then the E-mail server sends the E-mail to the terminal used by the user B.
  • the invitation link provided by one embodiment of the present invention is as follows:
  • the RCS gateway can also add some introduction information about the invitation link to the sent E-mail.
  • the RCS gateway can register with the RCS to request non-RCS registration.
  • the non-RCS registered user is assigned a temporary account, and the temporary account is sent to the non-RCS registered user, so that the non-RCS registered user can use the temporary account to interact with the RCS registered user, so that the RCS registered user can have better.
  • the business experience can also increase the willingness of non-RCS registered users to register as RCS registered users, and accelerate the popularity of RCS.
  • FIG. 3 illustrates a flow of an interaction method provided by an embodiment of the present invention.
  • the embodiment describes a process flow of a terminal, specifically a terminal used by a non-system registered user. Examples include:
  • the terminal may receive an E-mail, a short message, or a multimedia message sent by the system gateway.
  • the temporary account can be carried in the invitation link.
  • the login password is further included in the E-mail, SMS or MMS.
  • the login password can also be carried in the invitation link.
  • the second system client When the non-system registered user obtains the temporary account, or the temporary account and the login password, the second system client can be started, the temporary account is input, or the temporary account and the login password are input, and the second system client sends the password to the system gateway.
  • a login request, the login request includes a temporary account, or a temporary account and a login password, so that the system gateway can authenticate according to the temporary account, or the temporary account and the login password.
  • the non-system registered user When the temporary account, or the temporary account and the login password are carried in the invitation link, the non-system registered user only needs to click the invitation link to start the second system client, and the second system client can automatically send the login after starting. Requests, which can reduce the operations that non-system registered users need to do, and increase the willingness of non-system registered users.
  • the second system client may be a separate client preset in the terminal, and the independent client may have some additional functional missing compared with the first system client used by the system registered user, but the present
  • the system function is the same as the first system client; the second system client may also be a web client, and the basic system function of the web client is the same as the first system client. The same.
  • the temporary account, or the temporary account and the login password are carried in the invitation link, the non-system registered user only needs to click the invitation link, and the terminal will automatically start the independent client or the web client; wherein, the basic system function is based on the system.
  • the difference may be different.
  • basic system functions may include an RCS session, etc.
  • basic system functions may include an IM session, etc.
  • the second system client can implement the basic System functions can be customized by the system operator as needed.
  • the system gateway After receiving the login request, the system gateway performs authentication according to the temporary account, or the temporary account and the login password carried in the login request. Specifically, the system gateway can match the temporary account carried in the login request to the temporary account table saved by itself. , or temporary account and login password. After the authentication is passed, the system gateway can find the information of the system registered user who invites the non-system registered user from the invitation relationship table saved by itself.
  • the system gateway receives, by the system gateway, information about a system registered user that invites a non-system registered user. Since the non-system registered user does not have a corresponding contact list in the system, after the second system client logs in to the system, it receives the information returned by the system gateway to invite the non-system registered user to interact with the system registration user. Therefore, the non-system registered user can interact with the system registered user who invites the non-system registered user, and the non-RCS registered user can only interact with the RCS registered user who invites him, and cannot interact with other RCS registered users arbitrarily.
  • the information of the registered user of the system may be different according to different systems.
  • the information of the registered user of the system may be the IM account of the registered user of the system; in the RCS system, the information of the registered user of the system may be Is the UID of the registered user of the system, or the registered user of the system.
  • the terminal After receiving the information of the system registration user who invites the non-system registered user, the terminal displays the information of the registered user of the system on the interface of the second system client, so that the non-system registered user can open the second system client.
  • the system registers the user's interactive window to interact with the system's registered users.
  • the interactive message carries the interaction information of the non-system registered user and the registered user of the system.
  • it can also carry a temporary account, or a temporary account and a login password, so that the system gateway can authenticate according to the temporary account, or the temporary account and the login password, thereby registering the first system used by the user after the authentication is passed.
  • the client forwards the interactive message.
  • the system gateway can forward the interactive message to the first system client through the interaction server corresponding to the current interaction type. It can be understood that if the system gateway allocates the temporary account to the non-system registered user, the system gateway does not The temporary account is registered with the interactive server, and the system gateway needs to register the temporary account at the interactive server at least before forwarding the interactive message to the first system client through the interactive server.
  • the user's interaction message further includes: sending a detection request to the system gateway to detect the online status of the registered user of the system; receiving the online status of the system registered user returned by the system gateway; if the online status of the registered user of the system is online, the system gateway is Send an interactive message that needs to be sent to the registered user of the system.
  • the terminal used by the non-system registered user in this embodiment can log in to the system using the temporary account assigned by the system gateway, and interact with the system registered user who invites the non-system registered user, thereby enabling a registered user of a system to Interact with registered users who are not the system, so that the system registered users can have a better business experience, and can also increase the willingness of non-system registered users to register as system registered users.
  • the second system client used by the non-system registered user or the first system client used by the system registration user may log in to the system when the login is cancelled.
  • the gateway sends a logout request, so that the system gateway deletes the temporary account and the invitation relationship between the temporary account and the account of the registered user of the system, or deletes the invitation relationship between the temporary account and the account of the registered user of the system.
  • FIG. 4 is a flowchart of the interaction method provided by another embodiment of the present invention.
  • the embodiment describes the processing flow of the system gateway.
  • the embodiment includes:
  • the login request received by the system gateway may further carry the login password when the system gateway assigns a login password to the temporary account. 402. After the authentication of the temporary account carried in the login request is passed, send information to the second system client to invite the system registered user of the non-system registered user.
  • the system gateway can match the temporary account number, or the temporary account number and the login password carried in the login request to the temporary account table saved by the system. After the matching is passed, the system gateway can find the invitation to the non-system registered user from the invitation relationship table saved by itself. The system registers the user's information.
  • the first system client used by the system registration user forwards the interaction message.
  • the authentication of the temporary account carried in the interactive message may include: determining, according to the invitation relationship between the saved temporary account and the account of the registered user of the system, whether the temporary account carried in the interactive message has an invitation relationship with the account of the system registered user; If the temporary account carried in the message has an invitation relationship with the account of the registered user of the system, the authentication is passed.
  • the system gateway only needs to authenticate the temporary account to implement the login of the second system client and the interaction with the first system client, so that the registered users of one system can
  • the registered users of the system interact to enable the system registered users to have a better business experience, and also increase the willingness of non-system registered users to register as system registered users.
  • the process of forwarding the interactive message by the system gateway to the first system client used by the system registration user may be different according to the system.
  • the system gateway may forward the interaction message to the first system client through the interaction server.
  • the system gateway can forward the interactive message to the IM server, and the IM server forwards the interactive message to the first system client.
  • the interaction type is IM interaction
  • the system gateway can forward the interaction message to the IM server of the RCS system through the IMS core network, and then the IM server forwards the interaction message to the first system client.
  • the forwarding of the interactive message by the first system client may include: converting the format of the message from the format of the first protocol that the second system client interacts with the system gateway to the format of the second protocol used by the internal interaction of the system; System client forwarding is converted to the format of the second protocol Interactive message.
  • the internal interaction of the system includes the interaction between the network elements in the system, and the interaction between the network element in the system and the first system client used by the registered user of the system.
  • system gateway may further include: before forwarding the interaction message to the first system client used by the system registration user:
  • the non-system registered user in order to achieve the purpose that the non-system registered user invited by the system registration user can interact with the registered user of the system only when the system is registered with the user online, uses the second
  • the system client may send a detection request to the system gateway to detect the online status of the registered user of the system; therefore, the system gateway receives the detection request from the second system client requesting the online status of the registered user of the registered system; therefore, the system gateway can detect the system Register the online status of the user and carry the online status of the registered user of the system in the detection response and return it to the second system client.
  • the second system client used by user B can send a status message to the RCS gateway to request the RCS gateway to detect user A.
  • the status message sent by the second system client can be as follows:
  • Authorization is a string that uses User B's temporary account and login password to be encrypted by BASE64.
  • the RCS gateway After receiving the status message, the RCS gateway authenticates user B according to Authorization. After the authentication is passed, it verifies that user B has the right to query the online status of user A according to the saved relationship table. If user B has the right to query the online status of user A, the RCS gateway converts the status message into a SIP OPTIONS message and sends it to the IMS core network. After receiving the online status of user A returned by the IMS core network, the online status of user A is returned to The second client used by user B.
  • the second system client can periodically send a status message to the system gateway, so that the system gateway periodically detects the online status of the registered user of the system; of course, the second system client can also send only to the system gateway. With a status message, the system gateway automatically and periodically detects the online status of the registered user of the system. It should be noted that although the system gateway periodically detects the online status of the registered user of the system, as long as the detected online status of the registered user of the system is returned to the previous time. The online status of the second system client does not change, and the system gateway does not need to return the online status of the system registered user to the second system client again.
  • Non-system registered users and system registered users who interact with each other may go offline during the interaction process or after the interaction is completed. If the non-system registered user goes offline, the second system client used by the non-system registered user will go to the system gateway. Sending a logout request, requesting to log off the login; If the system registered user goes offline, the first system client used by the system registration user also sends a logout request to the system gateway, requesting to logout.
  • the system gateway receives a logout request from the first system client used by the system registered user or the second system client used by the non-system registered user; at this time, the system gateway can delete The temporary account and the invitation relationship between the temporary account and the account of the registered user of the system, or the invitation relationship between the temporary account and the account of the registered user of the system.
  • the system gateway may delete the invitation relationship between the temporary account and the account of the system registered user from the invitation relationship table saved by itself, and delete the temporary account assigned to the non-system registered user from the temporary account table; Or, if the temporary account assigned by the system gateway to the same non-system registered user is the same at different times, the system gateway may only delete the invitation relationship between the temporary account in the invitation relationship table and the account of the system registered user, if there is a system registration again. The user invites the non-system registered user to interact, and the system gateway can directly obtain the temporary account assigned to the non-system registered user in the temporary account list.
  • FIG. 5 is a signaling flowchart of an interaction method provided by another embodiment of the present invention.
  • the embodiment specifically describes a process for performing an IM interaction between an RCS registered user and a non-RCS registered user in an RCS system, where the embodiment includes :
  • the second system client After user B starts the second system client, the second system client sends a login request to the RCS gateway, where the login request carries a temporary account.
  • User B is a non-RCS registered user, and the temporary account is assigned by the RCS gateway to user B.
  • the RCS gateway authenticates the temporary account.
  • the RCS gateway can match the temporary account carried in the login request to the temporary account table. If the temporary account number is matched in the temporary account table, the authentication is passed, and vice versa, the authentication fails.
  • the RCS gateway converts the login request into a SIP login request.
  • the protocol used by the RCS gateway to receive the login request may be the Restfol protocol, or In the case of the Hypertext Transport Protocol (HTTP): Extensible Makeup Language (XML) protocol; specifically, when the second system client is a standalone client, the protocol used for the login request can be It is the Restfol protocol; when the second system client is a web client, the protocol used for the login request may be the HTTP+XML protocol or the Restful protocol.
  • HTTP Hypertext Transport Protocol
  • XML Extensible Makeup Language
  • the RCS gateway initiates a SIP authentication process by using a login request of the SIP protocol, so that the IMS core network and the IM server authenticate the login request of the SIP protocol.
  • the IMS core network and the IM server can authenticate the login request through the SIP protocol.
  • the RCS gateway After receiving the response indicating that the authentication is passed by the IMS core network and the IM server, the RCS gateway obtains information about the registered user of the system that has an invitation relationship with the temporary account from the invitation relationship table, and obtains the information of the registered user of the system. The information carried is returned to the second system client in the login response.
  • This embodiment assumes that the acquired information of the system registered user includes the information of the user A.
  • the second system client After receiving the login response, the second system client sends a status message to the RCS gateway to request the RCS gateway to detect the online status of user A.
  • the RCS gateway converts the status message into a SIP OPTIONS message, initiates a SIP OPTIONS message flow by using the SIP OPTIONS message, and obtains the online status of the user A from the IM server through the IMS core network.
  • the RCS gateway After receiving the online status of user A returned by the IMS core network, the RCS gateway carries the online status of user A in the status response and returns it to the second system client.
  • user B may choose to send the first IM message to user A, so the second system client sends the first IM message to the RCS gateway.
  • the first IM message sent to the RCS gateway is as follows. :
  • the first IM message may be based on the Restf l protocol or the HTTP+XML protocol.
  • the RCS gateway After receiving the message, the RCS gateway authenticates user B.
  • the specific authentication includes the authentication of the temporary account of user B, and whether user B and the user
  • A has an authentication of the invitation relationship.
  • the RCS gateway converts the first IM message into a SIP INVITE message, and sends the SIP INVITE message to the IM server through the IMS core network through the MSRP channel.
  • the SIP INVITE message can be directly sent to the IMS core network to initiate a SIP INVITE process to establish an MSRP channel.
  • the IM server forwards the SIP INVITE message to the first system client used by user A.
  • the MSRP channel between the first system client and the RCS gateway is established, and the interaction between the subsequent RCS gateway and the first system client can be directly performed through the MSRP channel. .
  • User A replies to the user B, and the first system client sends the second IM message to the RCS gateway through the MSRP channel.
  • the RCS gateway After converting the second IM message to the Restf l protocol or the HTTP+XML protocol, the RCS gateway sends the second IM message converted to the Restf l protocol or the HTTP+XML protocol to the second system client.
  • User B selects to end the interaction, and the second system client sends a logout request to the RCS gateway.
  • the RCS gateway converts the logout request into a SIP protocol format, sends a logout request converted to a SIP protocol format to the IM server through the IMS core network, initiates a SIP BYE process by using a logout request in a SIP protocol format, and removes the MSRP channel.
  • the RCS gateway performs logout processing.
  • the logout process includes deleting the invitation relationship between the temporary account of the user B and the account of the user A in the invitation relationship table, and further deleting the temporary of the user B in the temporary account table. account number.
  • the RCS gateway sends a logout response to the second system client.
  • the RCS gateway only needs to authenticate the temporary account to implement login of the second system client, and interaction with the first system client, so that the non-RCS registered user can use the temporary account. Interact with RCS registered users, so that RCS registered users can have a better business experience, and can increase the willingness of non-RCS registered users to register as RCS registered users, and accelerate the popularization of RCS.
  • FIG. 6 is a schematic diagram of a system gateway provided by an embodiment of the present invention, including:
  • the receiving unit 601 is configured to receive an invitation request sent by the system registration user by using the first system client, where the invitation request includes an identifier of the non-system registered user.
  • the obtaining unit 602 is configured to obtain, after the receiving unit 601 receives the invitation request, a temporary account that is valid for the non-system registered user and is valid in the system.
  • the sending unit 603 is configured to send, according to the identifier of the non-system registered user, the temporary account acquired by the obtaining unit 602 to the terminal used by the non-system registered user.
  • the system gateway can allocate a temporary account to the non-system registered user when the system registration user requests the non-system registered user to interact, and send the temporary account to the non-system registered user, so that the non-system registered user can
  • the temporary account is used to interact with the registered user of the system, so that a registered user of a system can interact with a registered user who is not the system, so that the registered user of the system can have a better business experience, and can also increase the registration of the non-system registered user.
  • FIG. 7 illustrates a structure of a system gateway according to another embodiment of the present invention, including: a receiving unit 601, configured to receive an invitation request sent by a system registration user through a first system client, where the invitation request includes an identifier of a non-system registered user. ; The invitation request also includes system registered users Account number.
  • the obtaining unit 602 is configured to obtain, after the receiving unit 601 receives the invitation request, a temporary account that is valid for the non-system registered user and is valid in the system.
  • the sending unit 603 is configured to send, according to the identifier of the non-system registered user, the temporary account acquired by the obtaining unit 602 to the terminal used by the non-system registered user.
  • the saving unit 704 is configured to save an invitation relationship between the temporary account acquired by the obtaining unit 602 and the account of the system registered user received by the receiving unit 601.
  • the system gateway provided by another embodiment of the present invention may further include a determining unit 805, configured to determine, according to the account of the system registration user received by the receiving unit 601, whether the registered user of the system has the right to send an invitation request;
  • the obtaining unit 602 is only used to obtain the temporary number assigned to the non-system registered user when the determining unit 805 determines that the system registered user has the right to send the invitation request.
  • the invitation request received by the receiving unit 601 included in the system gateway provided by another embodiment of the present invention may further include an interaction type in which the system registration user invites a non-system registered user to interact;
  • the gateway may further include a first registration unit 906 for registering the temporary account acquired by the acquisition unit 602 by the interaction server corresponding to the interaction type received by the receiving unit 601.
  • the system gateway provided by another embodiment of the present invention may be applied to an RCS system, specifically used as an RCS gateway in an RCS system; when the system gateway is applied to an RCS system, may further include a second registration unit, which is used in the IMS core network.
  • Figure 8 is a diagram showing the structure of a system gateway provided by another embodiment of the present invention, including:
  • the receiving unit 1001 is configured to receive a login request sent by the second system client, where the login request carries a temporary account that is valid for the non-system registered user and is valid in the system.
  • the authentication unit 1002 is configured to authenticate the temporary account carried by the login request received by the receiving unit 1001.
  • the sending unit 1003 is configured to send, after the authentication unit 1002 authenticates the temporary account carried by the login request, the information of the system registered user who invites the non-system registered user to the second system client.
  • the receiving unit 1001 is further configured to receive a request from the second system client to send to the system registration User interaction message, which carries a temporary account.
  • the authentication unit 1002 is further configured to authenticate the temporary account carried by the interaction message received by the receiving unit 1001.
  • the authentication unit 1002 is specifically configured to determine, according to the invitation relationship between the saved temporary account and the account of the registered user of the system, whether the temporary account carried in the interactive message has an invitation relationship with the account of the system registered user. If the temporary account carried in the interactive message has an invitation relationship with the account of the registered user of the system, the authentication is determined to pass.
  • the sending unit 1003 is further configured to: after the authentication unit 1002 passes the authentication of the temporary account carried by the interactive message, forward the interactive message to the first system client used by the system registration user.
  • the sending unit 1003 may be specifically configured to convert a format of the interaction message from a format of the first protocol that the second system client interacts with the system gateway to a second protocol used for internal interaction of the system. Format; then forward the interactive message to the first system client in the format converted to the second protocol.
  • the system gateway only needs to authenticate the temporary account to implement the login of the second system client and the interaction with the first system client, so that the registered users of one system can
  • the registered users of the system interact to enable the system registered users to have a better business experience, and also increase the willingness of non-system registered users to register as system registered users.
  • FIG. 9 is a schematic diagram of a system gateway according to another embodiment of the present invention, including: a receiving unit 1001, configured to receive a login request sent by a second system client, where the login request is carried in a system that is allocated by a non-system registered user. A valid temporary account.
  • the authentication unit 1002 is configured to authenticate the temporary account carried by the login request received by the receiving unit 1001.
  • the sending unit 1003 is configured to send, after the authentication unit 1002 authenticates the temporary account carried by the login request, the information of the system registered user who invites the non-system registered user to the second system client.
  • the receiving unit 1001 is further configured to receive a detection request from the second system client to request the online status of the registered user of the system.
  • the detecting unit 1104 is configured to detect, after the receiving unit 1001 receives the detection request, the online status of the registered user of the system.
  • the sending unit 1003 is further configured to register the user of the system detected by the detecting unit 1104.
  • the state is returned to the second system client.
  • the receiving unit 1001 is further configured to receive an interaction message from the second system client that needs to be sent to the system registration user, where the interaction message carries the temporary account.
  • the authentication unit 1002 is further configured to authenticate the temporary account carried by the interaction message received by the receiving unit 1001.
  • the sending unit 1003 is further configured to: after the authentication unit 1002 passes the authentication of the temporary account carried by the interactive message, forward the interactive message to the first system client used by the system registration user.
  • the receiving unit 1001 is further configured to receive a logout request from the first system client or the second system client.
  • the system gateway provided by the embodiment
  • the deleting unit 1205, as shown in FIG. 9, may be configured to delete the temporary account and the invitation relationship between the temporary account and the account of the system registered user, or delete the temporary account and the registered user of the system after the receiving unit 1001 receives the logout request.
  • the invitation relationship of the account may be configured to delete the temporary account and the invitation relationship between the temporary account and the account of the system registered user, or delete the temporary account and the registered user of the system after the receiving unit 1001 receives the logout request. The invitation relationship of the account.
  • FIG. 10 is a diagram showing the structure of a terminal according to an embodiment of the present invention, including:
  • the receiving unit 1301 is configured to receive a temporary account from the system gateway, where the temporary account is allocated for the non-system registered user and is valid in the system.
  • the sending unit 1302 is configured to send a login request to the system gateway, where the login request includes a temporary account received by the receiving unit 1301.
  • the receiving unit 1301 is further configured to receive information about a system registered user that invites a non-system registered user returned by the system gateway.
  • the sending unit 1302 is further configured to send, to the system gateway, an interaction message that needs to be sent to the registered user, where the interaction message carries the temporary account, so that the system gateway authenticates the temporary account and then registers the first system client used by the user with the system.
  • the terminal forwards the interactive message.
  • the terminal used by the non-system registered user in this embodiment can log in to the system using the temporary account assigned by the system gateway, and interact with the system registered user who invites the non-system registered user, thereby enabling a registered user of a system to Interact with registered users who are not the system, so that the system registered users can have a better business experience, and can also increase the willingness of non-system registered users to register as system registered users.
  • a sending unit included in a terminal provided by an embodiment of the present invention is provided. 1302.
  • the sending unit 1301 is further configured to send a detection request to the system gateway to detect an online status of the registered user of the system.
  • the receiving unit 1301 is further configured to receive an online status of the system registered user returned by the system gateway, where the sending unit 1302 is configured to be in the system.
  • the system gateway sends an interactive message to the system registered user.
  • a sending unit included in a terminal provided by an embodiment of the present invention is provided.
  • the method may further be configured to send a logout request to the system gateway, so that the system gateway deletes the temporary account and the invitation relationship between the temporary account and the account of the registered user of the system, or deletes the invitation relationship between the temporary account and the account of the registered user of the system.
  • FIG. 11 illustrates a structure of a system gateway according to another embodiment of the present invention, including at least one processor 1402 (eg, a CPU), at least one network interface 1405 or other communication interface, a memory 1406, and at least one communication bus 1403 for Achieve connection communication between these devices.
  • the processor 1402 is operative to execute executable modules, such as computer programs, stored in the memory 1406.
  • the memory 1406 may include a high speed random access memory (RAM: Random Access Memory) and may also include a non-volatile memory such as at least one disk memory.
  • the communication connection between the system gateway and at least one other network element is implemented by at least one network interface 1405 (which may be wired or wireless), and may use an Internet, a wide area network, a local area network, a metropolitan area network, or the like.
  • the memory 1406 stores a program 14061, and the program 14061 can be executed by the processor 1402.
  • the program includes: receiving an invitation request sent by the system registration user through the first system client, the invitation request including the non-system registered user Identification; Obtain a temporary account that is valid for the non-system registered user in the system; send a temporary account to the terminal used by the non-system registered user according to the identifier of the non-system registered user.
  • FIG. 12 illustrates a structure of a system gateway according to another embodiment of the present invention, including at least one processor 1502 (eg, a CPU), at least one network interface 1505 or other communication interface, a memory 1506, and at least one communication bus 1503 for Achieve connection communication between these devices.
  • the processor 1502 is configured to execute executable modules, such as computer programs, stored in the memory 1506.
  • the memory 1506 may include a high speed random access memory (RAM: Random Access Memory), and may also include a non-volatile memory such as at least one disk memory.
  • RAM Random Access Memory
  • Implementing the system gateway with at least one network interface 1505 (which may be wired or wireless)
  • the communication connection between at least one other network element may use the Internet, a wide area network, a local network, a metropolitan area network, and the like.
  • the memory 1506 stores a program 15061, and the program 15061 can be executed by the processor 1502.
  • the program includes: receiving a login request sent by the second system client, the login request carrying the system assigned to the non-system registered user a valid temporary account; after the authentication of the temporary account carried in the login request is passed, the second system client sends the information of the system registered user who invites the non-system registered user; and the request from the second system client is sent to the system.
  • An interactive message of the registered user the interactive message carries a temporary account; after the authentication of the temporary account carried in the interactive message is passed, the first system client used by the system registration user forwards the interactive message.
  • FIG. 13 illustrates a structure of a terminal according to another embodiment of the present invention, including at least one processor 1602 (eg, a CPU), at least one network interface 1605 or other communication interface, a memory 1606, and at least one communication bus 1603 for implementing The connection between these devices is communicated.
  • the processor 1602 is configured to execute an executable module, such as a computer program, stored in the memory 1606.
  • the terminal optionally includes a user interface 1604, including but not limited to a display, a keyboard and a pointing device (eg, a mouse, a trackball, a touchpad, or a touch sensitive display.
  • the memory 1606 may include a high speed random access memory (RAM: Random) Access Memory ) may also include non-volatile memory, such as at least one disk saver.
  • RAM Random
  • the system gateway and at least one other network may be implemented by at least one network interface 1505 (which may be wired or wireless)
  • the communication connection between the yuan can use the Internet, the wide area network, the local network, the metropolitan area network, and the like.
  • the memory 1606 stores a program 16061, which can be executed by the processor 1602.
  • the program includes: receiving a temporary account from the system gateway, and using a temporary account to send a login request to the system gateway, the temporary account is The non-system registered user is allocated and valid in the system; receiving the information of the system registered user that invites the non-system registered user returned by the system gateway; sending an interaction message to the system gateway that needs to be sent to the system registered user, and the interactive message carries the temporary account, In order for the system gateway to authenticate the temporary account, the first system client used by the system registration user forwards the interactive message.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM: Read Random Memory), or a random access memory (RAM).

Landscapes

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

Abstract

本发明涉及通信技术领域，公开了用户注册方法、交互方法及相关设备。其中用户注册方法，包括：接收系统注册用户通过第一系统客户端发送的邀请请求，所述邀请请求包括非系统注册用户的标识；获取为所述非系统注册用户分配的在所述系统内有效的临时账号；根据所述非系统注册用户的标识，向所述非系统注册用户所使用的终端发送所述临时账号。使用本发明，可以使一个系统的注册用户能够与非该系统的注册用户进行交互。

Description

用户注册方法、 交互方法及相关设备
本申请要求于 2011 年 11 月 28 日提交中国专利局、 申请号为 201110384980.6, 发明名称为"用户注册方法、 交互方法及相关设备 "的中国专 利申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，具体涉及用户注册方法、交互方法及相关设备。 背景技术
融合通信套件 ( RCS: Rich Communication Suite )解决方案是一个跨通信 网、互联网的综合通信及信息共享平台。用户可以使用真实的手机号码作为登 录帐号， 可以通过 RCS解决方案的个人电脑 （PC: Personal Computer )客户 端、 万维网 （Web )客户端或手机客户端与联系人进行即时通讯（IM: Instant Messaging )通信， 也可以上传、 下载、 共享图片、 音乐、 视频、 文本等内容。 RCS 解决方案不但能够扩大用户的社交网络， 也能够为用户提供多元化的生 活形态。
但是 RCS解决方案和普通的 IM交互工具一样，如果两个用户需要使用相 同类型的客户端进行交互（如 IM交互、 文件交互等）， 这两个用户必须是该 客户端对应的系统的注册用户； 例如， 用户 A和用户 B如果需要通过 RCS客 户端进行交互， 那么用户 A和用户 B必须都是 RCS系统的注册用户才可以。 这就导致一个系统（IM系统、 RCS系统等） 的注册用户不能够与非该系统的 注册用户进行交互。
发明内容
本发明实施例提供了用户注册方法、 交互方法及相关设备， 可以使一个系 统的注册用户能够与非该系统的注册用户进行交互。
本发明一个实施例提供了一种用户注册方法， 包括：
接收系统注册用户通过第一系统客户端发送的邀请请求 ,所述邀请请求包 括非系统注册用户的标识；
获取为所述非系统注册用户分配的在所述系统内有效的临时账号； 根据所述非系统注册用户的标识，向所述非系统注册用户所使用的终端发 送所述临时账号。 本发明另一个实施例提供了一种交互方法， 包括：
接收来自系统网关的临时账号，使用所述临时账号向所述系统网关发送登 录请求， 所述临时账号是为非系统注册用户分配且在所述系统内有效；
接收所述系统网关返回的邀请所述非系统注册用户的系统注册用户的信 息；
向所述系统网关发送需要发送至所述系统注册用户的交互消息，所述交互 消息携带所述临时账号，以使所述系统网关对所述临时账号鉴权通过后向所述 系统注册用户所使用的第一系统客户端转发所述交互消息。
本发明另一个实施例提供了一种交互方法， 包括：
接收第二系统客户端发送的登录请求，所述登录请求携带为所述非系统注 册用户分配的在所述系统内有效的临时账号；
在对所述登录请求携带的临时账号的鉴权通过后 ,向所述第二系统客户端 发送邀请所述非系统注册用户的系统注册用户的信息；
接收来自所述第二系统客户端的需要发送给所述系统注册用户的交互消 息， 该交互消息携带临时账号；
在对所述交互消息携带的临时账号的鉴权通过后，向所述系统注册用户使 用的第一系统客户端转发所述交互消息。
本发明另一个实施例提供了一种系统网关， 包括：
接收单元， 用于接收系统注册用户通过第一系统客户端发送的邀请请求， 所述邀请请求包括非系统注册用户的标识；
获取单元，用于获取为所述非系统注册用户分配的在所述系统内有效的临 时账号；
发送单元， 用于根据所述非系统注册用户的标识， 向所述非系统注册用户 所使用的终端发送所述临时账号。
本发明另一个实施例提供了一种终端， 包括：
接收单元， 用于接收来自系统网关的临时账号， 所述临时账号是为非系统 注册用户分配且在所述系统内有效；
发送单元， 用于向所述系统网关发送登录请求， 所述登录请求包括所述接 收单元接收的临时账号； 所述接收单元，还用于接收所述系统网关返回的邀请所述非系统注册用户 的系统注册用户的信息；
所述发送单元，还用于向所述系统网关发送需要发送至所述系统注册用户 的交互消息， 所述交互消息携带所述临时账号， 以使所述系统网关对所述临时 账号鉴权通过后向所述系统注册用户所使用的第一系统客户端转发所述交互 消息。
本发明另一个实施例提供了一种系统网关， 包括：
接收单元， 用于接收第二系统客户端发送的登录请求， 所述登录请求携带 为所述非系统注册用户分配的在所述系统内有效的临时账号；
鉴权单元， 用于对所述登录请求携带的临时账号进行鉴权；
发送单元，用于在所述鉴权单元对所述登录请求携带的临时账号的鉴权通 过后 ,向所述第二系统客户端发送邀请所述非系统注册用户的系统注册用户的 信息；
所述接收单元，还用于接收来自所述第二系统客户端的需要发送给所述系 统注册用户的交互消息， 该交互消息携带临时账号；
所述鉴权单元， 还用于对所述交互消息携带的临时账号进行鉴权； 所述发送单元，还用于在所述鉴权单元对所述交互消息携带的临时账号的 鉴权通过后， 向所述系统注册用户使用的第一系统客户端转发所述交互消息。
从本发明实施例提供的以上技术方案可以看出，由于本发明实施例中系统 网关可以在系统注册用户要求非系统注册用户进行交互时，为非系统注册用户 分配临时账号， 并将临时账号发送给非系统注册用户，使非系统注册用户可以 使用该临时账号与系统注册用户进行交互，从而使一个系统的注册用户能够与 非该系统的注册用户进行交互，使系统注册用户可以有更好的业务体验，也能 够增加非系统注册用户注册成系统注册用户的意愿。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所 需要使用的附图作简单地介绍，显而易见地， 下面描述中的附图仅仅是本发明 的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提 下， 还可以根据这些附图获得其他的附图。 图 1为本发明一个实施例提供的用户注册方法的流程图；
图 2为本发明另一个实施例提供的用户注册方法的信令流程图； 图 3为本发明一个实施例提供的交互方法的流程图；
图 4为本发明另一个实施例提供的交互方法的流程图；
图 5为本发明另一个实施例提供的交互方法的信令流程图；
图 6为本发明一个实施例提供的系统网关的结构图；
图 7为本发明另一个实施例提供的系统网关的结构图；
图 8为本发明另一个实施例提供的系统网关的结构图；
图 9为本发明另一个实施例提供的系统网关的结构图；
图 10为本发明一个实施例提供的终端的结构图；
图 11为本发明另一个实施例提供的系统网关的结构图；
图 12为本发明另一个实施例提供的系统网关的结构图；
图 13为本发明另一个实施例提供的终端的结构图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清 楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而不是 全部的实施例。基于本发明中的实施例， 本领域普通技术人员在没有作出创造 性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
先介绍本发明实施例提供的用户注册方法，图 1描述了本发明一个实施例 提供的用户注册方法的流程， 该实施例描述的是系统网关的处理流程， 其中， 系统网关根据系统的不同会有不同，例如系统为 RCS系统时，系统网关为 RCS 网关； 系统为 IM系统时， 系统网关为 IM网关。 该实施例包括：
101、 接收系统注册用户通过第一系统客户端发送的邀请请求， 该邀请请 求携带非系统注册用户的标识。
系统网关接收的邀请请求是基于系统内交互协议的， 例如， 在 RCS系统 内， 邀请请求是通过网际协议多媒体子系统（IMS: IP multimedia subsystem ) 核心网传输的， RCS网关具体可以从 rest接口接收邀请请求，其中邀请请求可 以 于超文本传输协议 ( HTTP: Hyper Text Transport Protocol )或内部自定 义协议的； 在 IM系统内， 邀请请求则是基于该 IM系统所使用的内部协议。 其中， 第一系统客户端是指由系统注册用户使用的客户端。 其中， 第一系统客 户端获取非系统注册用户的标识过程，具体可以通过系统注册用户从操作的终 端的通讯录中选择获取， 也可以通过接收系统注册用户的输入获取。
在本发明的一个实施例中，第一系统客户端在获取了邀请请求中的用户的 标识后， 可以先到系统的注册用户信息中心查询该用户的标识，如果没有从注 册用户信息中心查询到该用户的标识， 就可以确定该用户没有在系统注册，从 而在确定该用户没有在系统注册时， 才向系统网关发送邀请请求。 其中， 系统 的注册用户信息中心根据不同的系统会有不同， 例如在 RCS系统中， 可以是 RCS用户中心 （ RCS UP Center ); 在 IM系统中， 可以是 IM Server。
其中，邀请请求携带的非系统注册用户的标识可以是非系统注册用户的电 子邮件（E-mail )地址、 终端号码等。
102、 获取为非系统注册用户分配的在系统内有效的临时账号。
其中， 可以由系统网关为非系统注册用户分配临时账号， 具体地， 系统网 关可以直接以非系统注册用户的标识作为临时账号，也可以分配系统流水号作 为临时账号，也可以采用其他方式分配临时账号； 本发明实施例不限定临时账 号的具体形式，也不限定临时账号的分配方式， 只需要保证分配的临时账号在 系统中唯一即可。也可以由系统网关将非系统注册用户的标识发送至系统的注 册用户信息中心，由系统的注册用户信息中心为非系统注册用户分配临时账号 后， 将临时账号发送给系统网关。
其中， 在本发明的另一个实施例中， 为了提高系统的安全性， 在为非系统 注册用户分配临时账号时，可以进一步分配使用该临时账号登录系统时使用的 登录密码。
103、 根据非系统注册用户的标识， 向非系统注册用户所使用的终端发送 临时 号。
根据非系统注册用户的标识不同，系统网关可以通过不同的通道向非系统 注册用户发送临时账号， 可以理解的是， 系统网关发送临时账号的通道与接收 邀请请求的通道不同，接收邀请请求一般采用系统内通道，但是发送临时账号 的通道根据非系统注册用户的标识的类型的不同有不同，根据通道的不同， 系 统网关可以采用不同的方式发送邀请请求。例如，在非系统注册用户的标识为 非系统注册用户的 E-mail地址时， 系统网关可以通过 E-mail的方式向 E-mail 地址发送临时账号； 在非系统注册用户的标识为终端号码时， 则通过短信或多 媒体短信的方式向终端号码对应的终端发送临时账号。
其中，如果分配了与临时账号对应的登录密码， 则向非系统注册用户所使 用的终端发送临时账号时，进一步向非系统注册用户所使用的终端发送登录密 码。
具体地， 为了方便非系统注册用户的操作， 可以将临时账号或临时账号和 登录密码设置在邀请链接中，再向非系统注册用户所使用的终端发送该邀请链 接；非系统注册用户在收到了邀请链接后，可以直接点击该邀请链接登录系统， 降低了非系统注册用户的操作繁瑣度。
从上可知 ,本实施例中系统网关可以在系统注册用户要求非系统注册用户 进行交互时， 为非系统注册用户分配临时账号， 并将临时账号发送给非系统注 册用户，使非系统注册用户可以使用该临时账号与系统注册用户进行交互，从 而使一个系统的注册用户能够与非该系统的注册用户进行交互 ,使系统注册用 户可以有更好的业务体验，也能够增加非系统注册用户注册成系统注册用户的 意愿。
在本发明的另一个实施例中，系统网关接收的邀请请求还可以携带发起该 邀请请求的系统注册用户的账号； 此时， 为了提高系统的安全性， 系统网关在 为非系统注册用户分配了临时账号后，可以进一步保存发起邀请请求的系统注 册用户的账号与该临时账号的邀请关系，从而在后续的交互过程中，仅允许临 时账号与该临时账号具有邀请关系的系统注册用户的账号进行交互。
进一步，在系统网关接收的邀请请求携带了发起该邀请请求的系统注册用 户的账号时，系统网关可以根据系统注册用户的账号判断该系统注册用户是否 有权限发送邀请请求；并且只有在判断得到系统注册用户有权限发送邀请请求 时， 才获取为非系统注册用户分配的临时账号，从而避免没有权限的系统注册 用户发送邀请请求， 提高系统的安全性和稳定性。 其中， 具有什么样的权限可 以发送邀请请求可以由系统运营商设定， 例如， 只要是系统注册用户都可以发 送邀请请求， 或只允许有效的系统注册用户发送邀请请求， 或只允许具有一定 级别， 并且有效的系统注册用户发送邀请请求等； 其中， 有效的系统注册用户 是指的可以正常使用系统功能的系统注册用户，例如，如果一个系统注册用户 的账号处于挂失状态， 则该系统注册用户就不是有效的系统注册用户。
在本发明的另一个实施例中，系统网关接收的邀请请求还携带了系统注册 用户邀请非系统注册用户进行交互的交互类型； 此时， 系统网关在获取了为非 系统注册用户分配的在系统内有效的临时账号后，可以进一步在交互类型对应 的交互服务器注册临时账号。例如， 系统注册用户邀请非系统注册用户进行交 互的交互类型为 IM交互时，系统网关可以将临时账号在 IM服务器进行注册； 系统注册用户邀请非系统注册用户进行交互的交互类型为文件交互时，系统网 关可以将临时账号在文件服务器进行注册。这样， 非系统注册用户后续在使用 临时账号与系统注册用户进行交互时， 可以通过交互服务器的验证。可以理解 的是，在临时账号是由系统的注册用户信息中心分配时， 系统网关可以不需要 在交互类型对应的交互服务器注册临时账号。
在本发明的另一个实施例中， 系统为 RCS系统， 则 RCS网关在获取了为 非系统注册用户分配的在系统内有效的临时账号后，可以进一步在网际协议多 媒体子系统（ IMS： IP multimedia subsystem )核心网中注册该临时账号。 由于 RCS系统中的交互信息会通过 IMS核心网进行传输， 因此在 IMS核心网中注 册临时账号， 可以确保非系统注册用户可以使用临时账号在 IMS核心网传输 交互信息。
图 2描述了本发明另一个实施例提供的用户注册方法的信令流程，该实施 例具体描述的是在 RCS系统中， RCS注册用户邀请非 RCS注册用户进行 IM 交互时的用户注册的流程， 该实施例包括：
201、 第一系统客户端在接收到用户 A发起的与用户 B进行 IM交互的指 令后， 向 RCS UP Center发送查询请求， 用于查询用户 B是否为 RCS注册用 户， 该查询请求携带用户 B的标识。
其中， 用户 A是 RCS注册用户， 第一系统客户端是 RCS标准客户端， 用 户 A在登录了第一系统客户端后， 可以从第一系统客户端的联系人列表、 或 者终端的通讯录中选择用户 B的标识， 或者也可以由用户 A输入用户 B的标 识。
202、 RCS UP Center根据用户 B的标识查询用户 B是否为 RCS注册用户， 并将查询结果携带在查询响应中返回给第一系统客户端。
203、 第一系统客户端在接收到查询响应后， 获取查询结果； 如果查询结 果为用户 B为 RCS注册用户时， 开始正常的 RCS交互流程， 本发明实施例不 对正常的 RCS交互流程进行描述；如果查询结果为用户 B为非 RCS注册用户， 则第一系统客户端向 RCS网关发送邀请请求， 该邀请请求携带用户 A的身份 验证信息以及用户 B的标识， 其中， 用户 A的身份验证信息包括用户 A的账 号及登录密码等信息。
4叚设用户 B的用户标识是 E-mail地址， 该 E-mail具体为 b@cc.com, 则 本发明一个实施例提供的邀请请求可以如下所示：
POST http://host:port/rcsgw/invitee/user HTTP/ 1.1
Authorization: Basic QUNS01NFQ 1 VSSVRZVE9LRU4=
Content Type: application/json; charset=UTF-8
{ "email"： "b@cc.com" }
其中， 用户 A的身份验证信息保存在 Authorization头域， Authorization 头域的内容是由 A的身份验证信息经过 BASE64加密获得的字符串。
204、 RCS网关接收到邀请请求后， 使用邀请请求携带的用户 A的身份验 证信息验证用户 A是否有权限发送邀请请求， 在确定用户 A有权限发送邀请 请求时， 为用户 B分配临时账号和登录密码。
RCS系统中的账号可以为会话发起协议统一资源标识（SIP URI: Session Initiation Protocol Uniform Resource Identifier ), 本实施例 4叚设 RCS网关使用 E-mail地址生成临时账号， 则生成的临时账号为 SIP:b@cc.com。
其中， RCS网关在为用户 B分配了临时账号和登录密码后， 可以在临时 账号表中增加为用户 B分配的临时账号的信息， 具体地， 临时账号表中可以 保存用户 B的标识， 为用户 B分配的临时账号及登录密码。 在这种情况下， RCS网关在为用户 B分配临时账号之前， 可以先到临时账号表中确定是否已 经为用户 B分配了临时账号， 如果已经分配了临时账号则可以直接使用临时 账号表中记录的为用户 B分配的临时账号。
进一步， RCS网关还可以进一步在邀请关系表中记录用户 A与用户 B的 邀请关系， 其中， 可以在邀请关系表中记录用户 A的账号以及为用户 B分配 的临时账号，其中，保存的用户 A的账号可以是用户 A的用户身份标识（UID: User Identity )和用户 A的 SIP URI中的至少一个。 在本发明的另一个实施例 中， 为用户 B分配的临时账号是有有效期的， 则可以进一步在邀请关系表中 记录分配临时账号的时间以及临时账号的有效期； 其中，在有效期为默认的有 效期时， 可以仅在邀请关系表中记录分配临时账号的时间。
其中， RCS 网关在接收到第一系统客户端发送的邀请请求后， 会向第一 系统客户端返回邀请请求响应 （图中未示出）。
205、 RCS网关向 IMS核心网发送第一注册请求， 用于请求 IMS核心网 网元对为用户 B分配的临时账号进行注册， 该第一注册请求携带为用户 B分 配的临时账号。
206、 IMS核心网向 RCS网关发送第一注册响应， 该第一注册响应携带为 用户 B分配的临时账号是否成功注册的信息。 本实施例仅考虑成功注册的情 况。
207、 RCS网关向 IM服务器发送第二注册请求，用于请求 IM服务器对为 用户 B分配的临时账号进行注册， 该第二注册请求携带为用户 B分配的临时 账号。
208、 IM服务器向 RCS网关发送第二注册响应， 该第二注册响应携带为 用户 B分配的临时账号是否成功注册的信息。 本实施例仅考虑成功注册的情 况。
209、RCS网关将为用户 B分配的临时账号和登录密码设置在邀请链接中， 并向用户 B的 E-mail地址发送 E-mail, 该 E-mail包括该邀请链接； 其中， 向 用户 B的 E-mail地址发送 E-mail, 具体是向该 E-mail地址所在的 E-mail服务 器发送 E-mail , 后续由该 E-mail服务器将 E-mail发送给用户 B使用的终端。
假设临时账号 sip:b@cc.com对应的登录密码为 12345,则本发明一个实施 例提供的邀请链接如下所示：
http:// host:port/rcsgw/invitee/session/sip:b@cc.com?passwd= 12345
其中， 为了使用户 B在收到 E-mail能够清楚地知道该链接的作用， RCS 网关还可以在发送的 E-mail中增加一些关于该邀请链接的介绍信息。
从上可知， 本实施例中 RCS网关可以在 RCS注册用户要求非 RCS注册 用户进行交互时， 为非 RCS注册用户分配临时账号， 并将临时账号发送给非 RCS注册用户，使非 RCS注册用户可以使用该临时账号与 RCS注册用户进行 交互， 使 RCS注册用户可以有更好的业务体验， 也能够增加非 RCS注册用户 注册成 RCS注册用户的意愿， 加快 RCS的普及。
如下再介绍本发明实施例提供的交互方法，图 3描述了本发明一个实施例 提供的交互方法的流程， 该实施例描述的是终端， 具体是非系统注册用户使用 的终端的处理流程， 该实施例包括：
301、 接收来自系统网关的临时账号， 该临时账号是为非系统注册用户分 配且在系统内有效。
具体地， 终端可以在接收系统网关发送的 E-mail、 短信或彩信等后， 从
E-mail、 短信或彩信中获取临时账号。 其中， 该临时账号可以承载在邀请链接 中。
进一步， 在临时账号有对应的登录密码时， E-mail、 短信或彩信中会进一 步包括该登录密码。 相应地， 在临时账号承载在邀请链接中时， 该登录密码也 可以承载在该邀请链接中。
302、 使用临时账号向系统网关发送登录请求。
非系统注册用户在获取了临时账号、或者临时账号与登录密码时， 可以启 动第二系统客户端， 再输入临时账号、 或者输入临时账号与登录密码， 第二系 统客户端就会向系统网关发送登录请求， 该登录请求包括临时账号、或者临时 账号与登录密码， 以使系统网关能够根据临时账号、或者临时账号与登录密码 进行鉴权。
在临时账号、或者临时账号与登录密码承载在邀请链接中时， 非系统注册 用户只需要点击该邀请链接， 就可以启动第二系统客户端， 第二系统客户端启 动后就可以自动的发送登录请求，从而可以减少非系统注册用户需要进行的操 作， 提高非系统注册用户的使用意愿。
其中， 第二系统客户端可以是预先设置在终端的独立客户端， 该独立客户 端与系统注册用户所使用的第一系统客户端相比，可能会有一些附加功能上的 缺失，但 本的系统功能与第一系统客户端是相同的； 第二系统客户端也可 能是一个 Web客户端， 该 Web客户端基本的系统功能与第一系统客户端是相 同的。 在临时账号、 或者临时账号与登录密码承载在邀请链接中时， 非系统注 册用户只需要点击邀请链接，终端就会自动的启动独立客户端或 Web客户端； 其中， 基本的系统功能根据系统的不同会有不同， 例如对于 RCS系统， 基本 的系统功能可以包括 RCS会话等； 对于 IM系统， 基本的系统功能可以包括 IM会话等； 可以理解的是， 第二系统客户端所能够实现的基本的系统功能可 以由系统运营商根据需要进行定制。
其中， 系统网关在接收到登录请求后， 根据登录请求携带的临时账号、 或 者临时账号与登录密码进行鉴权， 具体地， 系统网关可以到自身保存的临时账 号表中匹配登录请求携带的临时账号、或者临时账号与登录密码。在鉴权通过 后，系统网关就可以从自身保存的邀请关系表中查找到邀请该非系统注册用户 的系统注册用户的信息。
303、 接收系统网关返回的邀请非系统注册用户的系统注册用户的信息。 由于非系统注册用户在系统中没有对应的联系人列表，因此在第二系统客 户端登陆了系统之后，就会接收到系统网关返回的邀请该非系统注册用户进行 交互的系统注册用户的信息，从而使非系统注册用户可以与邀请该非系统注册 用户的系统注册用户进行交互， 并且该非 RCS注册用户只能与邀请他的 RCS 注册用户进行交互， 不能任意与其他 RCS注册用户交互。
可以理解的是，系统注册用户的信息根据不同的系统会有不同，例如在 IM 系统中， 系统注册用户的信息可以是系统注册用户的 IM账号等；在 RCS系统 中， 系统注册用户的信息可以是系统注册用户的 UID, 或者是系统注册用户的
SIP URI等。
304、 向系统网关发送需要发送至系统注册用户的交互消息， 该交互消息 携带临时账号，以使系统网关对临时账号鉴权通过后向系统注册用户所使用的 第一系统客户端转发该交互消息。
终端在接收了邀请非系统注册用户的系统注册用户的信息后，就会在第二 系统客户端的界面上显示该系统注册用户的信息，使非系统注册用户可以通过 第二系统客户端打开与该系统注册用户的交互窗口，从而与系统注册用户进行 交互。
交互消息除了携带非系统注册用户与系统注册用户进行交互的交互信息 夕卜， 还可携带临时账号、 或者临时账号与登录密码， 使系统网关可以根据临时 账号、或者临时账号与登录密码进行鉴权，从而在鉴权通过后向系统注册用户 所使用的第一系统客户端转发交互消息， 具体地， 系统网关可以通过当前交互 类型对应的交互服务器向第一系统客户端转发交互消息； 可以理解的是，如果 系统网关在为非系统注册用户分配临时账号时没有将该临时账号在交互服务 器注册，则系统网关至少需要在通过交互服务器向第一系统客户端转发交互消 息之前， 将该临时账号在该交互服务器注册。
其中， 为了提高系统的安全性， 可以要求仅在系统注册用户在线时， 该系 统注册用户邀请的非系统注册用户才能够与该系统注册用户进行交互 ,因此在 向系统网关发送需要发送至系统注册用户的交互消息前进一步包括：向系统网 关发送请求检测系统注册用户的在线状态的检测请求；接收系统网关返回的系 统注册用户的在线状态； 如果系统注册用户的在线状态为在线， 才向系统网关 发送需要发送至系统注册用户的交互消息。
从上可知，本实施例中非系统注册用户使用的终端可以使用系统网关分配 的临时账号登录到系统，并且与邀请该非系统注册用户的系统注册用户进行交 互，从而使一个系统的注册用户能够与非该系统的注册用户进行交互，使系统 注册用户可以有更好的业务体验，也能够增加非系统注册用户注册成系统注册 用户的意愿。
进一步， 在本发明的另一个实施例中， 为了进一步提高系统的安全性， 非 系统注册用户使用的第二系统客户端或系统注册用户使用的第一系统客户端 在注销登录时，会向系统网关发送一个注销请求， 以使系统网关删除临时账号 以及临时账号与系统注册用户的账号的邀请关系、或删除临时账号与系统注册 用户的账号的邀请关系。
图 4描述了本发明另一个实施例提供的交互方法的流程，该实施例描述的 是系统网关的处理流程， 该实施例包括：
401、 接收第二系统客户端发送的登录请求， 该登录请求携带为非系统注 册用户分配的在系统内有效的临时账号。
其中，在系统网关为临时账号分配了登录密码时， 系统网关接收的登录请 求还可以进一步携带该登录密码。 402、 在对登录请求携带的临时账号的鉴权通过后， 向第二系统客户端发 送邀请非系统注册用户的系统注册用户的信息。
系统网关可以到自身保存的临时账号表中匹配登录请求携带的临时账号、 或者临时账号与登录密码，在匹配通过后， 系统网关可以从自身保存的邀请关 系表中查找到邀请该非系统注册用户的系统注册用户的信息。
403、 接收来自第二系统客户端的需要发送给系统注册用户的交互消息， 该交互消息携带临时账号。
404、 在对交互消息携带的临时账号的鉴权通过后， 向系统注册用户所使 用的第一系统客户端转发交互消息。
其中，对交互消息携带的临时账号的鉴权可以包括： 根据保存的临时账号 与系统注册用户的账号的邀请关系，判断交互消息携带的临时账号是否与系统 注册用户的账号存在邀请关系；如果交互消息携带的临时账号与系统注册用户 的账号存在邀请关系， 则鉴权通过。
从上可知，本实施例中系统网关只需要对临时账号进行鉴权就可以实现第 二系统客户端的登录， 以及与第一系统客户端之间的交互，从而使一个系统的 注册用户能够与非该系统的注册用户进行交互，使系统注册用户可以有更好的 业务体验， 也能够增加非系统注册用户注册成系统注册用户的意愿。
其中，根据系统的不同， 系统网关向系统注册用户所使用的第一系统客户 端转发交互消息的流程可能会有不同， 一般情况下， 系统网关可以通过交互服 务器向第一系统客户端转发交互消息。 例如在 IM系统中， 系统网关可以将交 互消息转发给 IM服务器，由 IM服务器将该交互消息转发至第一系统客户端。 在 RCS系统中， 交互类型为 IM交互时， 系统网关可以通过 IMS核心网将交 互消息转发至 RCS系统的 IM服务器，再由该 IM服务器将交互消息转发至第 一系统客户端。
在非系统注册用户使用的第二系统客户端与系统网关的交互使用第一协 议， 且系统内部交互使用第二协议， 且第一协议与第二协议不同时， 系统网关 向系统注册用户使用的第一系统客户端转发交互消息具体可以包括：将消息的 格式从第二系统客户端与系统网关交互的第一协议的格式，转换为系统内部交 互所使用的第二协议的格式；向第一系统客户端转发转换为第二协议的格式的 交互消息。 其中， 系统内部交互包括系统内网元之间的交互， 以及系统内网元 与系统注册用户使用的第一系统客户端的交互等。
在本发明的另一个实施例中， 为了提高系统交互的安全性， 系统网关向系 统注册用户所使用的第一系统客户端转发交互消息前可以进一步包括：
在本发明的另一个实施例中， 为了达到仅在系统注册用户在线时，该系统 注册用户邀请的非系统注册用户才能够与该系统注册用户进行交互的目的，非 系统注册用户使用的第二系统客户端可以向系统网关发送检测系统注册用户 的在线状态的检测请求； 因此， 系统网关会接收到来自第二系统客户端的请求 检测系统注册用户的在线状态的检测请求；因此系统网关可以检测系统注册用 户的在线状态，并将系统注册用户的在线状态携带在检测响应中返回给第二系 统客户端。
以系统为 RCS系统为例， 4叚设 RCS注册用户为用户 A, 非 RCS注册用 户为用户 B, 则用户 B使用的第二系统客户端可以向 RCS网关发送 status消 息来请求 RCS 网关检测用户 A 的在线状态， 假设用户 A 的 SIP URI 为 sip:a@cc.com, 则第二系统客户端发送的 status消息可以如下所示：
GET http:// host:port/rcsgw/invitee/status/sip:a@cc.com HTTP/1.1
Authorization: Basic QUNS01NFQ 1 VSSVRZVE9LRU4=
其中， Authorization为使用用户 B 的临时账号及登录密码经过 BASE64 加密后的字符串。
RCS网关收到 status消息后， 根据 Authorization对用户 B进行鉴权， 鉴 权通过后， 根据自身保存的邀请关系表验证用户 B是否有权限查询用户 A的 在线状态。 如果用户 B有权限查询用户 A的在线状态， RCS网关将 status消 息转换为 SIP OPTIONS消息发送给 IMS核心网，收到 IMS核心网返回的用户 A的在线状态后， 将用户 A的在线状态返回给用户 B使用的第二客户端。
可以理解的是，第二系统客户端可以周期性地向系统网关发送 status消息， 以使系统网关周期性地检测系统注册用户的在线状态； 当然， 第二系统客户端 也可以只向系统网关发送一次 status消息， 系统网关自动的周期性地检测系统 注册用户的在线状态。 需要说明的是， 系统网关虽然周期性地检测系统注册用 户的在线状态，但是只要检测到的系统注册用户的在线状态与上一次返回给第 二系统客户端的在线状态相比没有改变，系统网关就不需要再次向第二系统客 户端返回系统注册用户的在线状态。
进行交互的非系统注册用户和系统注册用户都有可能在交互的过程中，或 交互完成后下线，如果是非系统注册用户下线， 非系统注册用户使用的第二系 统客户端会向系统网关发送注销请求，请求注销登录； 如果是系统注册用户下 线， 系统注册用户使用的第一系统客户端也会向系统网关发送注销请求，请求 注销登录。 因此在本发明的另一个实施例中， 系统网关会接收到来自系统注册 用户使用的第一系统客户端、或非系统注册用户使用的第二系统客户端的注销 请求； 此时， 系统网关可以删除临时账号以及临时账号与系统注册用户的账号 的邀请关系、 或删除临时账号与系统注册用户的账号的邀请关系。 即， 系统网 关在接收到注销请求后，可以从自身保存的邀请关系表中删除临时账号与系统 注册用户的账号的邀请关系，以及从临时账号表中删除为非系统注册用户分配 的临时账号； 或者，如果系统网关在不同时间为同一个非系统注册用户分配的 临时账号是相同的，那么系统网关可以只删除邀请关系表中临时账号与系统注 册用户的账号的邀请关系，如果再有系统注册用户邀请该非系统注册用户进行 交互，系统网关可以直接到临时账号表中获取为该非系统注册用户分配的临时 账号。
图 5描述了本发明另一个实施例提供的交互方法的信令流程图， 该实 施例具体描述的是在 RCS系统中， RCS注册用户与非 RCS注册用户进行 IM 交互的流程， 该实施例包括：
501、用户 B启动第二系统客户端后，第二系统客户端向 RCS网关发送登 录请求， 该登录请求携带临时账号。
其中，用户 B为非 RCS注册用户，临时账号是 RCS网关为用户 B分配的。
502、 RCS网关对临时账号进行鉴权。
RCS 网关可以将登录请求携带的临时账号到临时账号表中进行匹配， 如 果在临时账号表中匹配到对应的临时账号则鉴权通过， 反之， 鉴权不通过。
503、 RCS网关在对临时账号的鉴权通过后， 将登录请求转换成 SIP协议 的登录请求。
其中， RCS网关接收的登录请求所采用的协议可以是 Restfol协议， 也可 以是超文本传输协议 ( HTTP: Hyper Text Transport Protocol ) +可扩展标记语 言（XML: Extensive Makeup Language )协议； 具体地， 在第二系统客户端是 独立客户端时， 登录请求所采用的协议可以是 Restfol协议； 在第二系统客户 端是 Web客户端时，登录请求所采用的协议可以是 HTTP+XML协议或 Restful 协议。
504、 RCS网关使用 SIP协议的登录请求发起 SIP鉴权流程， 以使 IMS核 心网和 IM服务器对 SIP协议的登录请求进行鉴权。
由于 RCS网关在为非 RCS注册用户分配临时账号后，已经在 IMS核心网 和 IM服务器注册了该临时账号， 因此 IMS核心网和 IM服务器能够通过 SIP 协议的登录请求的鉴权。
505、 RCS网关在收到 IMS核心网和 IM服务器返回的表示鉴权通过的响 应后，从邀请关系表中获取与上述临时账号具有邀请关系的系统注册用户的信 息， 将获取的系统注册用户的信息携带在登录响应中返回给第二系统客户端。
本实施例假设获取的系统注册用户的信息包括用户 A的信息。
506、第二系统客户端在接收到登录响应后，向 RCS网关发送 status消息， 用于请求 RCS网关检测用户 A的在线状态。
507、 RCS 网关在对用户 B 的鉴权通过后， 将 status 消息转换为 SIP OPTIONS消息， 使用 SIP OPTIONS消息发起 SIP OPTIONS消息流程， 通过 IMS核心网从 IM服务器获取用户 A的在线状态。
508、 RCS网关在收到 IMS核心网返回的用户 A的在线状态后，将用户 A 的在线状态携带在 status响应中返回给第二系统客户端。
509、在用户 A的在线状态为在线时，用户 B可以选择向用户 A发送第一 IM消息， 因此第二系统客户端向 RCS网关发送第一 IM消息。
假设用户 A的 SIP URI是 SIP:a@cc.com,用户 B向用户 A发送的第一 IM 消息的内容为 abcdefg, 本发明一个实施例提供的向 RCS网关发送的第一 IM 消息如下所示：
POST http:// host:port/rcsgw/invitee/message HTTP/ 1.1
Authorization: Basic QUNS01NFQ 1 VSSVRZVE9LRU4=
{ "to"： "sip :a@cc. com", "message"： "abcdefg" } 其中， Authorization 后的内容是用户 B 的临时账号和登录密码经过 BASE64加密后的字符串。
其中， 第一 IM消息可以基于 Restf l协议或 HTTP+XML协议。
510、 RCS网关收到消息后， 对用户 B进行鉴权。
具体的鉴权包括对用户 B的临时账号的鉴权， 以及用户 B是否与用户
A存在邀请关系的鉴权。
511、 鉴权通过后， RCS网关将第一 IM消息转换成 SIP INVITE消息， 通过 MSRP通道将 SIP INVITE消息经由 IMS核心网发送至 IM服务器。
其中， 在第一系统客户端与第二系统客户端之间尚未建立 MSRP通道 时， 则可以直接将 SIP INVITE消息发送至 IMS核心网发起 SIP INVITE流 程从而建立 MSRP通道。
512、 IM服务器将 SIP INVITE消息转发给用户 A使用的第一系统客户 端。
在第一系统客户端接收到 SIP INVITE消息后，就会建立第一系统客户 端与 RCS网关之间的 MSRP通道， 则后续 RCS网关和第一系统客户端之 间的交互可以直接通过 MSRP通道进行。
513、 用户 A向用户 B回复消息， 第一系统客户端通过 MSRP通道将 第二 IM消息发送至 RCS网关。
514、 RCS网关将第二 IM消息转换成 Restf l协议或 HTTP+XML协议 后，将转换成 Restf l协议或 HTTP+XML协议的第二 IM消息发送给第二系统 客户端。
515、 用户 B选择结束交互， 第二系统客户端向 RCS网关发送注销请 求。
516、 RCS网关将注销请求转换成 SIP协议格式， 通过 IMS核心网向 IM服务器发送转换成 SIP协议格式的注销请求， 使用 SIP协议格式的注销 请求发起 SIP BYE流程， 拆除 MSRP通道。
517、 RCS网关进行注销处理。
具体地， 注销处理包括删除邀请关系表中用户 B的临时账号与用户 A 的账号之间的邀请关系， 进一步， 还可以删除临时账号表中用户 B的临时 账号。
518、 RCS网关在注销处理完成后， 向第二系统客户端发送注销响应。 从上可知， 本实施例中 RCS网关只需要对临时账号进行鉴权就可以实现 第二系统客户端的登录， 以及与第一系统客户端之间的交互， 使非 RCS注册 用户可以使用该临时账号与 RCS注册用户进行交互， 使 RCS注册用户可以有 更好的业务体验， 也能够增加非 RCS注册用户注册成 RCS注册用户的意愿， 加快 RCS的普及。
需要说明的是， 对于前述的各方法实施例， 为了简单描述， 故将其都 表述为一系列的动作组合， 但是本领域技术人员应该知悉， 本发明并不受 所描述的动作顺序的限制， 因为依据本发明， 某些步骤可以采用其他顺序 或者同时进行。 其次， 本领域技术人员也应该知悉， 说明书中所描述的实 施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
如下介绍本发明实施例提供的装置， 先介绍本发明实施例提供的系统网 关， 图 6描述了本发明一个实施例提供的系统网关的结构， 包括：
接收单元 601 , 用于接收系统注册用户通过第一系统客户端发送的邀请请 求， 该邀请请求包括非系统注册用户的标识。
获取单元 602, 用于在接收单元 601接收了邀请请求后， 获取为非系统注 册用户分配的在系统内有效的临时账号。
发送单元 603 , 用于根据非系统注册用户的标识， 向非系统注册用户所使 用的终端发送获取单元 602获取的临时账号。
从上可知 ,本实施例中系统网关可以在系统注册用户要求非系统注册用户 进行交互时， 为非系统注册用户分配临时账号， 并将临时账号发送给非系统注 册用户，使非系统注册用户可以使用该临时账号与系统注册用户进行交互，从 而使一个系统的注册用户能够与非该系统的注册用户进行交互 ,使系统注册用 户可以有更好的业务体验，也能够增加非系统注册用户注册成系统注册用户的 意愿。
图 7描述了本发明另一个实施例提供的系统网关的结构， 包括： 接收单元 601 , 用于接收系统注册用户通过第一系统客户端发送的邀请请 求， 该邀请请求包括非系统注册用户的标识； 该邀请请求还包括系统注册用户 的账号。
获取单元 602, 用于在接收单元 601接收了邀请请求后， 获取为非系统注 册用户分配的在系统内有效的临时账号。
发送单元 603 , 用于根据非系统注册用户的标识， 向非系统注册用户所使 用的终端发送获取单元 602获取的临时账号。
保存单元 704, 用于保存获取单元 602获取的临时账号与接收单元 601接 收的系统注册用户的账号的邀请关系。
如图 7 所示， 本发明另一个实施例提供的系统网关还可以包括判断单元 805 , 用于根据接收单元 601接收的系统注册用户的账号， 判断该系统注册用 户是否有权限发送邀请请求； 此时， 获取单元 602, 仅用于在判断单元 805判 断得到系统注册用户有权限发送邀请请求时 ,才获取为非系统注册用户分配的 临时 号。
如图 7 所示， 本发明另一个实施例提供的系统网关包括的接收单元 601 接收的邀请请求，还可以包括系统注册用户邀请非系统注册用户进行交互的交 互类型； 则该实施例提供的系统网关还可以包括第一注册单元 906, 用于在接 收单元 601接收的交互类型对应的交互服务器注册获取单元 602获取的临时账 号。
本发明另一个实施例提供的系统网关可以应用于 RCS系统， 具体是作为 RCS系统中的 RCS网关使用； 当系统网关应用于 RCS系统时， 还可以包括第 二注册单元， 用于在 IMS核心网中注册分配单元 602分配的临时账号， 其中 第二注册单元未在图中示出。
图 8描述了本发明另一个实施例提供的系统网关的结构， 包括：
接收单元 1001 , 用于接收第二系统客户端发送的登录请求， 该登录请求 携带为非系统注册用户分配的在系统内有效的临时账号。
鉴权单元 1002, 用于对接收单元 1001接收的登录请求携带的临时账号进 行鉴权。
发送单元 1003 , 用于在鉴权单元 1002对登录请求携带的临时账号的鉴权 通过后， 向第二系统客户端发送邀请非系统注册用户的系统注册用户的信息。
接收单元 1001 , 还用于接收来自第二系统客户端的需要发送给系统注册 用户的交互消息， 该交互消息携带临时账号。
鉴权单元 1002, 还用于对接收单元 1001接收的交互消息携带的临时账号 进行鉴权。
在本发明的一个实施例中， 鉴权单元 1002, 具体可以用于根据保存的临 时账号与系统注册用户的账号的邀请关系，判断交互消息携带的临时账号是否 与系统注册用户的账号存在邀请关系；如果交互消息携带的临时账号与系统注 册用户的账号存在邀请关系， 确定鉴权通过。
发送单元 1003 , 还用于在鉴权单元 1002对交互消息携带的临时账号的鉴 权通过后， 向系统注册用户使用的第一系统客户端转发交互消息。
在本发明的一个实施例中， 发送单元 1003 , 具体可以用于将交互消息的 格式从第二系统客户端与系统网关交互的第一协议的格式，转换为系统内部交 互所使用的第二协议的格式；再向第一系统客户端转发转换为第二协议的格式 的交互消息。
从上可知，本实施例中系统网关只需要对临时账号进行鉴权就可以实现第 二系统客户端的登录， 以及与第一系统客户端之间的交互，从而使一个系统的 注册用户能够与非该系统的注册用户进行交互，使系统注册用户可以有更好的 业务体验， 也能够增加非系统注册用户注册成系统注册用户的意愿。
图 9描述了本发明另一个实施例提供的系统网关的结构， 包括： 接收单元 1001 , 用于接收第二系统客户端发送的登录请求， 该登录请求 携带为非系统注册用户分配的在系统内有效的临时账号。
鉴权单元 1002, 用于对接收单元 1001接收的登录请求携带的临时账号进 行鉴权。
发送单元 1003 , 用于在鉴权单元 1002对登录请求携带的临时账号的鉴权 通过后， 向第二系统客户端发送邀请非系统注册用户的系统注册用户的信息。
接收单元 1001 , 还用于接收来自第二系统客户端的请求检测系统注册用 户的在线状态的检测请求。
检测单元 1104, 用于在接收单元 1001接收了检测请求后， 检测系统注册 用户的在线状态。
发送单元 1003 , 还用于将检测单元 1104检测到的系统注册用户的在线状 态返回给第二系统客户端。
接收单元 1001 , 还用于接收来自第二系统客户端的需要发送给系统注册 用户的交互消息， 该交互消息携带临时账号。
鉴权单元 1002, 还用于对接收单元 1001接收的交互消息携带的临时账号 进行鉴权。
发送单元 1003 , 还用于在鉴权单元 1002对交互消息携带的临时账号的鉴 权通过后， 向系统注册用户使用的第一系统客户端转发交互消息。
如图 9所示， 在本发明的另一个实施例中， 接收单元 1001 , 还可以用于 接收来自第一系统客户端或第二系统客户端的注销请求； 此时， 该实施例提供 的系统网关还可以包括如图 9所示的删除单元 1205 , 用于在接收单元 1001接 收了注销请求后，删除临时账号以及临时账号与系统注册用户的账号的邀请关 系、 或删除临时账号与系统注册用户的账号的邀请关系。
再介绍本发明实施例提供的终端， 图 10描述了本发明一个实施例提供的 终端的结构， 包括：
接收单元 1301 , 用于接收来自系统网关的临时账号， 该临时账号是为非 系统注册用户分配且在系统内有效。
发送单元 1302, 用于向系统网关发送登录请求， 该登录请求包括接收单 元 1301接收的临时账号。
接收单元 1301 , 还用于接收系统网关返回的邀请非系统注册用户的系统 注册用户的信息。
发送单元 1302, 还用于向系统网关发送需要发送至统注册用户的交互消 息， 该交互消息携带临时账号， 以使系统网关对临时账号鉴权通过后向系统注 册用户所使用的第一系统客户端转发交互消息。
从上可知，本实施例中非系统注册用户使用的终端可以使用系统网关分配 的临时账号登录到系统，并且与邀请该非系统注册用户的系统注册用户进行交 互，从而使一个系统的注册用户能够与非该系统的注册用户进行交互，使系统 注册用户可以有更好的业务体验，也能够增加非系统注册用户注册成系统注册 用户的意愿。
在本发明的另一个实施例中 ,本发明实施例提供的终端所包括的发送单元 1302,还可以用于向系统网关发送请求检测系统注册用户的在线状态的检测请 求； 接收单元 1301 , 还可以用于接收系统网关返回的系统注册用户的在线状 态； 发送单元 1302, 用于在系统注册用户的在线状态为在线时， 才向系统网 关发送需要发送至系统注册用户的交互消息。
在本发明的另一个实施例中，本发明实施例提供的终端所包括的发送单元
1302,还可以用于向系统网关发送注销请求， 以使系统网关删除临时账号以及 临时账号与系统注册用户的账号的邀请关系、或删除临时账号与系统注册用户 的账号的邀请关系。
图 11描述了本发明另一个实施例提供的系统网关的结构， 包括至少一个 处理器 1402 (例如 CPU ), 至少一个网络接口 1405或者其他通信接口， 存储 器 1406, 和至少一个通信总线 1403 , 用于实现这些装置之间的连接通信。 处 理器 1402用于执行存储器 1406中存储的可执行模块， 例如计算机程序。存储 器 1406可能包含高速随机存取存储器（ RAM: Random Access Memory ), 也 可能还包括非不稳定的存储器（non-volatile memory ), 例如至少一个磁盘存储 器。 通过至少一个网络接口 1405 (可以是有线或者无线） 实现该系统网关与 至少一个其他网元之间的通信连接， 可以使用互联网， 广域网， 本地网， 城域 网等。
在一些实施方式中， 存储器 1406存储了程序 14061 , 程序 14061可以被 处理器 1402执行， 这个程序包括： 接收系统注册用户通过第一系统客户端发 送的邀请请求， 该邀请请求包括非系统注册用户的标识； 获取为非系统注册用 户分配的在系统内有效的临时账号；根据非系统注册用户的标识， 向非系统注 册用户所使用的终端发送临时账号。
图 12描述了本发明另一个实施例提供的系统网关的结构， 包括至少一个 处理器 1502 (例如 CPU ), 至少一个网络接口 1505或者其他通信接口， 存储 器 1506, 和至少一个通信总线 1503 , 用于实现这些装置之间的连接通信。 处 理器 1502用于执行存储器 1506中存储的可执行模块， 例如计算机程序。存储 器 1506可能包含高速随机存取存储器（RAM: Random Access Memory ), 也 可能还包括非不稳定的存储器（non-volatile memory ), 例如至少一个磁盘存储 器。 通过至少一个网络接口 1505 (可以是有线或者无线） 实现该系统网关与 至少一个其他网元之间的通信连接， 可以使用互联网， 广域网， 本地网， 城域 网等。
在一些实施方式中， 存储器 1506存储了程序 15061 , 程序 15061可以被 处理器 1502执行， 这个程序包括： 接收第二系统客户端发送的登录请求， 该 登录请求携带为非系统注册用户分配的在系统内有效的临时账号；在对登录请 求携带的临时账号的鉴权通过后，向第二系统客户端发送邀请非系统注册用户 的系统注册用户的信息；接收来自第二系统客户端的需要发送给系统注册用户 的交互消息， 该交互消息携带临时账号； 在对交互消息携带的临时账号的鉴权 通过后， 向系统注册用户使用的第一系统客户端转发交互消息。
图 13描述了本发明另一个实施例提供的终端的结构， 包括至少一个处理 器 1602(例如 CPU ),至少一个网络接口 1605或者其他通信接口，存储器 1606, 和至少一个通信总线 1603 , 用于实现这些装置之间的连接通信。 处理器 1602 用于执行存储器 1606中存储的可执行模块， 例如计算机程序。 终端可选的包 含用户接口 1604, 包括但不限于显示器， 键盘和点击设备（例如， 鼠标， 轨 迹球（ trackball ), 触感板或者触感显示屏。 存储器 1606可能包含高速随机存 取存储器（RAM: Random Access Memory ), 也可能还包括非不稳定的存储器 ( non- volatile memory ), 例如至少一个磁盘存者器。 通过至少一个网络接口 1505 (可以是有线或者无线）实现该系统网关与至少一个其他网元之间的通信 连接， 可以使用互联网， 广域网， 本地网， 城域网等。
在一些实施方式中， 存储器 1606存储了程序 16061 , 程序 16061可以被 处理器 1602执行， 这个程序包括： 接收来自到系统网关的临时账号， 使用临 时账号向系统网关发送登录请求，该临时账号是为非系统注册用户分配且在系 统内有效； 接收系统网关返回的邀请非系统注册用户的系统注册用户的信息； 向系统网关发送需要发送至系统注册用户的交互消息，交互消息携带所述临时 账号，以使系统网关对临时账号鉴权通过后向系统注册用户所使用的第一系统 客户端转发交互消息。
上述装置和系统内的各模块之间的信息交互、执行过程等内容， 由于与本 发明方法实施例基于同一构思， 具体内容可参见本发明方法实施例中的叙述， 此处不再赘述。 本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程， 是可以通过计算机程序来指令相关的硬件来完成，上述的程序可存储于一计算 机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。 其中， 上述的存储介质可为磁碟、 光盘、 只读存储记忆体（ROM: Read-Only Memory )或随机存储记忆体 ( RAM: Random Access Memory )等。 例的说明只是用于帮助理解本发明的方法及其思想； 同时，对于本领域的一般 技术人员 ,依据本发明的思想 ,在具体实施方式及应用范围上均会有改变之处 , 综上所述， 本说明书内容不应理解为对本发明的限制。

Claims

权 利 要 求
1、 一种用户注册方法， 其特征在于， 包括：
接收系统注册用户通过第一系统客户端发送的邀请请求，所述邀请请求包 括非系统注册用户的标识；
获取为所述非系统注册用户分配的在所述系统内有效的临时账号； 根据所述非系统注册用户的标识，向所述非系统注册用户所使用的终端发 送所述临时账号。
2、 如权利要求 1所述的用户注册方法， 其特征在于， 所述邀请请求还包 括所述系统注册用户的账号； 所述方法还包括：
保存所述临时账号与所述系统注册用户的账号的邀请关系。
3、 如权利要求 2所述的用户注册方法， 其特征在于， 获取为所述非系统 注册用户分配的临时账号前进一步包括：
根据所述系统注册用户的账号判断所述系统注册用户是否有权限发送邀 请请求；
如果判断得到所述系统注册用户有权限发送邀请请求，才获取为所述非系 统注册用户分配的临时账号。
4、 如权利要求 1至 3任一所述的用户注册方法， 其特征在于， 所述邀请 请求还包括所述系统注册用户邀请所述非系统注册用户进行交互的交互类型； 所述获取为所述非系统注册用户分配的在所述系统内有效的临时账号后 进一步包括：
在所述交互类型对应的交互服务器注册所述临时账号。
5、 如权利要求 1至 4任一所述的用户注册方法， 其特征在于， 所述系统 为融合通信套件系统；所述获取为所述非系统注册用户分配的在所述系统内有 效的临时账号后进一步包括：
在网际协议多媒体子系统核心网中注册所述临时账号。
6、 如权利要求 1至 5任一所述的用户注册方法， 其特征在于， 获取为所 述非系统注册用户分配的在所述系统内有效的临时账号时，进一步获取所述临 时账号登录所述系统的登录密码；
向所述非系统注册用户所使用的终端发送所述临时账号时，进一步向所述 非系统注册用户所使用的终端发送所述登录密码。
7、 如权利要求 1至 6任一所述的用户注册方法， 其特征在于， 所述根据 括： 、 、 。 、 、 - 将所述临时账号设置在邀请链接中，根据所述非系统注册用户的标识向所 述非系统注册用户所使用的终端发送所述邀请链接。
8、 如权利要求 1至 7任一所述的用户注册方法， 其特征在于， 所述非系 统注册用户的标识是所述非系统注册用户的电子邮件地址；
所述向所述非系统注册用户所使用的终端发送所述临时账号包括：通过电 子邮件的方式向所述电子邮件地址发送所述临时账号；
或
所述非系统注册用户的标识是所述非系统注册用户的终端号码； 所述向所述非系统注册用户所使用的终端发送所述临时账号包括：通过短 信或多媒体短信的方式向所述终端号码对应的终端发送所述临时账号。
9、 如权利要求 8所述的用户注册方法， 其特征在于， 所述临时账号是所 述电子邮件地址、 或根据所述电子邮件地址生成、 或所述终端号码、 或根据所 述终端号码生成。
10、 一种交互方法， 其特征在于， 包括：
接收来自系统网关的临时账号，使用所述临时账号向所述系统网关发送登 录请求， 所述临时账号是为非系统注册用户分配且在所述系统内有效；
接收所述系统网关返回的邀请所述非系统注册用户的系统注册用户的信 自 ·
向所述系统网关发送需要发送至所述系统注册用户的交互消息，所述交互 消息携带所述临时账号，以使所述系统网关对所述临时账号鉴权通过后向所述 系统注册用户所使用的第一系统客户端转发所述交互消息。
11、 如权利要求 10所述的交互方法， 其特征在于， 所述向所述系统网关 发送需要发送至所述系统注册用户的交互消息前进一步包括：
向所述系统网关发送请求检测所述系统注册用户的在线状态的检测请求； 接收所述系统网关返回的所述系统注册用户的在线状态； 如果所述系统注册用户的在线状态为在线，才向所述系统网关发送需要发 送至所述系统注册用户的交互消息。
12、 如权利要求 10或 11所述的交互方法， 其特征在于， 所述方法进一步 包括：
向所述系统网关发送注销请求，以使所述系统网关删除所述临时账号以及 所述临时账号与所述系统注册用户的账号的邀请关系、或删除所述临时账号与 所述系统注册用户的账号的邀请关系。
13、 一种交互方法， 其特征在于， 包括：
接收第二系统客户端发送的登录请求 ,所述登录请求携带为所述非系统注 册用户分配的在所述系统内有效的临时账号；
在对所述登录请求携带的临时账号的鉴权通过后 ,向所述第二系统客户端 发送邀请所述非系统注册用户的系统注册用户的信息；
接收来自所述第二系统客户端的需要发送给所述系统注册用户的交互消 息， 该交互消息携带临时账号；
在对所述交互消息携带的临时账号的鉴权通过后，向所述系统注册用户使 用的第一系统客户端转发所述交互消息。
14、 如权利要求 13所述的交互方法， 其特征在于， 所述对所述交互消息 携带的临时账号的鉴权包括：
根据保存的临时账号与系统注册用户的账号的邀请关系，判断所述交互消 息携带的临时账号是否与所述系统注册用户的账号存在邀请关系；
如果所述交互消息携带的临时账号与所述系统注册用户的账号存在邀请 关系， 鉴权通过。
15、 如权利要求 13或 14所述的交互方法， 其特征在于， 所述向所述系统 注册用户转发所述交互消息包括：
将所述交互消息的格式从所述第二系统客户端与所述系统网关交互的第 一协议的格式， 转换为所述系统内部交互所使用的第二协议的格式；
向所述第一系统客户端转发转换为所述第二协议的格式的交互消息。
16、 如权利要求 13至 15任一所述的交互方法， 其特征在于， 所述方法还 包括： 接收来自所述第二系统客户端的请求检测所述系统注册用户的在线状态 的检测请求；
检测所述系统注册用户的在线状态；
将所述系统注册用户的在线状态返回给所述第二系统客户端。
17、 如权利要求 13至 16任一所述的交互方法， 其特征在于， 所述方法还 包括：
接收来自所述第一系统客户端或第二系统客户端的注销请求；
删除所述临时账号以及所述临时账号与所述系统注册用户的账号的邀请 关系、 或删除所述临时账号与所述系统注册用户的账号的邀请关系。
18、 一种系统网关， 其特征在于， 包括：
接收单元， 用于接收系统注册用户通过第一系统客户端发送的邀请请求， 所述邀请请求包括非系统注册用户的标识；
获取单元，用于获取为所述非系统注册用户分配的在所述系统内有效的临 时账号；
发送单元， 用于根据所述非系统注册用户的标识， 向所述非系统注册用户 所使用的终端发送所述临时账号。
19、 如权利要求 18所述的系统网关， 其特征在于， 所述邀请请求还包括 所述系统注册用户的账号； 所述系统网关还包括：
保存单元， 用于保存所述临时账号与所述系统注册用户的账号的邀请关 系。
20、 如权利要求 19所述的系统网关， 其特征在于， 还包括：
判断单元，用于根据所述系统注册用户的账号判断所述系统注册用户是否 有权限发送邀请请求；
所述获取单元，用于在所述判断单元判断得到所述系统注册用户有权限发 送邀请请求时， 才获取为所述非系统注册用户分配的临时账号。
21、 如权利要求 18至 20任一所述的系统网关， 其特征在于， 所述邀请请 求还包括所述系统注册用户邀请所述非系统注册用户进行交互的交互类型；所 述系统网关还包括：
第一注册单元， 用于在所述交互类型对应的交互服务器注册所述临时账 号。
22、 如权利要求 18至 21任一所述的系统网关， 其特征在于， 所述系统为 融合通信套件系统； 所述系统网关还包括：
第二注册单元， 用于在网际协议多媒体子系统核心网中注册所述临时账 号。
23、 一种终端， 其特征在于， 包括：
接收单元， 用于接收来自系统网关的临时账号， 所述临时账号是为非系统 注册用户分配且在所述系统内有效；
发送单元， 用于向所述系统网关发送登录请求， 所述登录请求包括所述接 收单元接收的临时账号；
所述接收单元，还用于接收所述系统网关返回的邀请所述非系统注册用户 的系统注册用户的信息；
所述发送单元，还用于向所述系统网关发送需要发送至所述系统注册用户 的交互消息， 所述交互消息携带所述临时账号， 以使所述系统网关对所述临时 账号鉴权通过后向所述系统注册用户所使用的第一系统客户端转发所述交互 消息。
24、 如权利要求 23所述的终端， 其特征在于， 所述发送单元， 还用于向 所述系统网关发送请求检测所述系统注册用户的在线状态的检测请求；
所述接收单元，还用于接收所述系统网关返回的所述系统注册用户的在线 状态；
所述发送单元， 用于在所述系统注册用户的在线状态为在线时， 才向所述 系统网关发送需要发送至所述系统注册用户的交互消息。
25、 如权利要求 23或 24所述的终端， 其特征在于， 所述发送单元， 还用 于向所述系统网关发送注销请求，以使所述系统网关删除所述临时账号以及所 述临时账号与所述系统注册用户的账号的邀请关系、或删除所述临时账号与所 述系统注册用户的账号的邀请关系。
26、 一种系统网关， 其特征在于， 包括：
接收单元， 用于接收第二系统客户端发送的登录请求， 所述登录请求携带 为所述非系统注册用户分配的在所述系统内有效的临时账号； 鉴权单元， 用于对所述登录请求携带的临时账号进行鉴权；
发送单元，用于在所述鉴权单元对所述登录请求携带的临时账号的鉴权通 过后 ,向所述第二系统客户端发送邀请所述非系统注册用户的系统注册用户的 信息；
所述接收单元，还用于接收来自所述第二系统客户端的需要发送给所述系 统注册用户的交互消息， 该交互消息携带临时账号；
所述鉴权单元， 还用于对所述交互消息携带的临时账号进行鉴权； 所述发送单元，还用于在所述鉴权单元对所述交互消息携带的临时账号的 鉴权通过后， 向所述系统注册用户使用的第一系统客户端转发所述交互消息。
27、 如权利要求 26所述的系统网关， 其特征在于， 所述鉴权单元， 具体 用于根据保存的临时账号与系统注册用户的账号的邀请关系，判断所述交互消 息携带的临时账号是否与所述系统注册用户的账号存在邀请关系；如果所述交 互消息携带的临时账号与所述系统注册用户的账号存在邀请关系 ,确定鉴权通 过。
28、 如权利要求 26或 27所述的系统网关， 其特征在于， 所述发送单元， 具体用于将所述交互消息的格式从所述第二系统客户端与所述系统网关交互 的第一协议的格式， 转换为所述系统内部交互所使用的第二协议的格式； 向所 述第一系统客户端转发转换为所述第二协议的格式的交互消息。
29、 如权利要求 26至 28任一所述的系统网关， 其特征在于， 所述系统网 关还包括检测单元；
所述接收单元，还用于接收来自所述第二系统客户端的请求检测所述系统 注册用户的在线状态的检测请求；
所述检测单元， 用于在所述接收单元接收了所述检测请求后，检测所述系 统注册用户的在线状态；
所述发送单元，还用于将所述系统注册用户的在线状态返回给所述第二系 统客户端。
30、 如权利要求 26至 29任一所述的系统网关， 其特征在于， 所述系统网 关还包括删除单元；
所述接收单元，还用于接收来自所述第一系统客户端或第二系统客户端的 注销请求；
所述删除单元， 用于在所述接收单元接收了所述注销请求后，删除所述临 时账号以及所述临时账号与所述系统注册用户的账号的邀请关系、或删除所述 临时账号与所述系统注册用户的账号的邀请关系。
PCT/CN2012/073779 2011-11-28 2012-04-11 用户注册方法、交互方法及相关设备 Ceased WO2013078811A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP12738009.5A EP2621141A4 (en) 2011-11-28 2012-04-11 PARTICIPATION METHOD, INTERACTION PROCEDURE AND ASSOCIATED DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110384980.6 2011-11-28
CN201110384980.6A CN102420819B (zh) 2011-11-28 2011-11-28 用户注册方法、交互方法及相关设备

Publications (1)

Publication Number Publication Date
WO2013078811A1 true WO2013078811A1 (zh) 2013-06-06

Family

ID=45945054

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/073779 Ceased WO2013078811A1 (zh) 2011-11-28 2012-04-11 用户注册方法、交互方法及相关设备

Country Status (4)

Country Link
US (1) US9059958B2 (zh)
EP (1) EP2621141A4 (zh)
CN (1) CN102420819B (zh)
WO (1) WO2013078811A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112738105A (zh) * 2017-04-14 2021-04-30 创新先进技术有限公司 邀请注册方法及装置

Families Citing this family (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103516675A (zh) * 2012-06-21 2014-01-15 华为软件技术有限公司 资源标识共享方法、终端和管理平台
CN102843357B (zh) * 2012-07-30 2016-11-16 北京网蜜在线网络有限公司 访问网络的方法、应用服务器及系统
CN103595699B (zh) * 2012-08-17 2018-02-27 腾讯科技（深圳）有限公司 一种管理账号的方法、系统及装置
CN103634416B (zh) * 2012-08-23 2017-12-22 中国移动通信集团公司 一种设备号码管理方法和平台
CN103685173A (zh) * 2012-09-10 2014-03-26 盛趣信息技术（上海）有限公司 网络应用的体验系统、使用方法、客户端及用户设备
CN103973656A (zh) * 2013-02-04 2014-08-06 中兴通讯股份有限公司 终端状态判断的方法和系统、RCS-e服务器
US20140298395A1 (en) * 2013-03-27 2014-10-02 Tencent Technology (Shenzhen) Company Limited Methods and systems for playing video on multiple terminals
CN104168176B (zh) * 2013-05-16 2018-08-24 深圳中兴网信科技有限公司 一种即时通讯方法、客户端、服务器及系统
CN104219257B (zh) * 2013-05-29 2018-05-11 华为终端（东莞）有限公司 一种网页实时通信方法、系统及服务器和客户端
CN104378330B (zh) * 2013-08-13 2019-02-12 北京奇虎科技有限公司 一种账户注册的方法及相应的装置和服务器
CN104378395B (zh) 2013-08-14 2019-02-05 华为技术有限公司 访问ott应用、服务器推送消息的方法及装置
CN103618717B (zh) * 2013-11-28 2017-12-05 北京奇虎科技有限公司 多账户客户信息的动态认证方法、装置和系统
EP2892186A1 (en) * 2014-01-02 2015-07-08 Alcatel Lucent Method and server enabling a first user to automatically discover the social network identifiers of a second user and the respective statuses of this second user in these social networks
KR102133514B1 (ko) * 2014-01-13 2020-07-13 삼성전자주식회사 전자 장치의 상태 메시지 서비스 제공 방법 및 그 전자 장치
US9754091B2 (en) * 2014-05-21 2017-09-05 Google Inc. Restricted accounts on a mobile platform
JP6027069B2 (ja) * 2014-09-18 2016-11-16 富士フイルム株式会社 Ｖｐｎアクセス制御システム、その作動方法及びプログラム、並びにｖｐｎルータ及びサーバ
CN105516935A (zh) * 2014-09-25 2016-04-20 深圳市中兴微电子技术有限公司 Rcs与传统信息业务平台化综合决策方法、装置及终端
US20160269381A1 (en) * 2015-03-10 2016-09-15 Synchronoss Technologies, Inc. Apparatus, system and method of dynamically controlling access to a cloud service
CN106411981B (zh) * 2015-07-31 2019-12-10 腾讯科技（深圳）有限公司 帐号分配方法及装置
CN106612265A (zh) * 2015-10-27 2017-05-03 阿里巴巴集团控股有限公司 即时通信方法及服务器
KR102436509B1 (ko) * 2015-12-07 2022-08-25 삼성전자주식회사 임시 계정 정보를 제공하는 방법, 장치 및 시스템
CN105956926A (zh) * 2016-04-26 2016-09-21 福州微猪信息科技有限公司 猪场数据开放平台
FR3058023B1 (fr) * 2016-10-24 2019-11-08 Sagemcom Broadband Sas Procede d'appairage aupres d'une passerelle
CN106341431B (zh) * 2016-11-30 2019-07-12 北京恒华伟业科技股份有限公司 一种登录方法、平台及系统
US10476822B2 (en) 2016-12-08 2019-11-12 T-Mobile Usa, Inc. MSRP/HTTP file transfer
CN106686011B (zh) * 2017-03-10 2020-02-21 安康鸿天科技开发有限公司 一种基于ims通信的多视场交互方法及装置
KR102266879B1 (ko) * 2017-04-14 2021-06-22 삼성전자주식회사 대화형 콘텐츠 제공 시스템
CN108228303B (zh) * 2018-01-31 2022-04-12 阿里巴巴（中国）有限公司 关联账户的更新方法及装置
US10264413B1 (en) * 2018-05-01 2019-04-16 Verizon Patent And Licensing Inc. Integrated rich communications services (RCS) messaging
CN108696538B (zh) * 2018-07-10 2020-12-22 安康鸿天科技开发有限公司 一种基于密钥文件的ims系统的安全通信方法
CN113313600B (zh) * 2020-02-26 2024-05-17 京东科技控股股份有限公司 消息的处理方法、装置及系统、存储介质、电子装置
CN112291223B (zh) * 2020-10-23 2023-03-24 摩森特(北京)科技有限公司 一种手机终端不支持5g消息的解决方法
CN112667589B (zh) * 2020-12-30 2023-09-01 北京明朝万达科技股份有限公司 一种日志管理方法、装置及系统
CN113783869B (zh) * 2021-09-08 2023-07-21 上海达龙信息科技有限公司 基于分享链接的云应用分享方法、装置、存储介质及设备
CN113840245B (zh) * 2021-11-16 2023-03-31 中国电信股份有限公司 用于rcs消息的通信方法和通信系统
CN115037725B (zh) * 2022-05-20 2024-01-05 深圳市欢太科技有限公司 账号分配方法、装置、存储介质及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005004505A2 (en) * 2003-06-27 2005-01-13 Oracle International Corporation Roaming across different access mechanisms and network technologies
CN101127625A (zh) * 2006-08-18 2008-02-20 华为技术有限公司 一种对访问请求授权的系统及方法
CN101277476A (zh) * 2007-03-30 2008-10-01 富士通株式会社 网络系统、终端定制方法以及定制服务方法
CN101369893A (zh) * 2008-10-06 2009-02-18 中国移动通信集团设计院有限公司 一种对临时用户进行局域网络接入认证的方法

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7835943B2 (en) * 1999-05-28 2010-11-16 Yahoo! Inc. System and method for providing place and price protection in a search result list generated by a computer network search engine
US7136915B2 (en) * 2000-03-14 2006-11-14 Rieger Iii Charles J System for communicating through maps
US7797241B2 (en) * 2000-09-13 2010-09-14 Ip.Com, Inc. Global information network product publication system
US7742996B1 (en) * 2000-09-27 2010-06-22 Khai Hee Kwan Computer program, system and method for on-line issuing and verifying a representation of economic value interchangeable for money having identification data and password protection over a computer network
US20030233278A1 (en) * 2000-11-27 2003-12-18 Marshall T. Thaddeus Method and system for tracking and providing incentives for tasks and activities and other behavioral influences related to money, individuals, technology and other assets
US20020157090A1 (en) * 2001-04-20 2002-10-24 Anton, Jr. Francis M. Automated updating of access points in a distributed network
US20070067297A1 (en) * 2004-04-30 2007-03-22 Kublickis Peter J System and methods for a micropayment-enabled marketplace with permission-based, self-service, precision-targeted delivery of advertising, entertainment and informational content and relationship marketing to anonymous internet users
JP4168972B2 (ja) * 2004-05-10 2008-10-22 株式会社セガ 会員登録されたユーザを起点に会員未登録の他のユーザに会員サービスを提供するシステム、サーバ、サービス提供方法およびプログラム
US7509272B2 (en) * 2004-06-16 2009-03-24 American Express Travel Related Services Company, Inc. Calendar auction method and computer program product
EP1884067B1 (en) * 2005-04-30 2015-02-25 Samsung Electronics Co., Ltd. Method for requesting an unregistered UE to perform registration in the IMS
CN100388685C (zh) * 2005-08-30 2008-05-14 华为技术有限公司 Ip多媒体子系统中ims注册触发实现方法
EP1775902A1 (en) * 2005-10-11 2007-04-18 Siemens Aktiengesellschaft S-CSCF assignment and user profile download for unregistered IMS subscribers for originating services
US20070118801A1 (en) * 2005-11-23 2007-05-24 Vizzme, Inc. Generation and playback of multimedia presentations
US7698171B2 (en) * 2006-07-28 2010-04-13 Trialpay, Inc. Methods and system for facilitating bids for placement of offers in an alternative payment platform
US20090177541A1 (en) * 2007-06-19 2009-07-09 Lead Llc Method and apparatus for point-based rewards system using interactive devices and software
US20090150237A1 (en) * 2007-12-10 2009-06-11 American Express Travel Related Services Company, Inc. Points based online auction
US20100011073A1 (en) * 2008-06-10 2010-01-14 True Commerce, Inc. User-deployable data transformation and exchange platform including on-demand item synchronization and user-deployable order management system
CN101986674A (zh) * 2010-09-17 2011-03-16 中兴通讯股份有限公司 一种通过移动通信终端邀请社交网站好友的方法及装置
US9723463B2 (en) * 2010-10-25 2017-08-01 Nokia Technologies Oy Method and apparatus for a device identifier based solution for user identification

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005004505A2 (en) * 2003-06-27 2005-01-13 Oracle International Corporation Roaming across different access mechanisms and network technologies
CN101127625A (zh) * 2006-08-18 2008-02-20 华为技术有限公司 一种对访问请求授权的系统及方法
CN101277476A (zh) * 2007-03-30 2008-10-01 富士通株式会社 网络系统、终端定制方法以及定制服务方法
CN101369893A (zh) * 2008-10-06 2009-02-18 中国移动通信集团设计院有限公司 一种对临时用户进行局域网络接入认证的方法

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112738105A (zh) * 2017-04-14 2021-04-30 创新先进技术有限公司 邀请注册方法及装置
CN112738105B (zh) * 2017-04-14 2024-03-15 创新先进技术有限公司 邀请注册方法及装置

Also Published As

Publication number Publication date
EP2621141A4 (en) 2013-10-23
CN102420819A (zh) 2012-04-18
US20130198382A1 (en) 2013-08-01
EP2621141A1 (en) 2013-07-31
CN102420819B (zh) 2014-11-05
US9059958B2 (en) 2015-06-16

Similar Documents

Publication Publication Date Title
CN102420819B (zh) 用户注册方法、交互方法及相关设备
US12069043B2 (en) Authenticated session management across multiple electronic devices using a virtual session manager
US11700137B2 (en) Collaborative access to virtual desktops
CN101517963B (zh) 分布式、可缩放、可插入的会议体系结构
KR101635244B1 (ko) 실시간 통신을 위한 사용자-기반 인증
CN104753877B (zh) 一种群组通信方法及装置
US20090094531A1 (en) Telephone call as rendezvous mechanism for data sharing between users
CN101919225B (zh) 认证系统及方法
US20160323235A1 (en) Instant Message and Electronic Mail Portability
US20090319611A1 (en) Method and System for Facilitating Exchange of A Data Between Applications Using a Communication Platform
CN106415519B (zh) 安全的统一云存储
US20070100944A1 (en) Uniform resource identifier decoration to enable connectivity for instant messaging providers serving non-authoritative namespaces
WO2014206199A1 (zh) 账号登陆的方法、设备及系统
WO2014201931A1 (zh) 资源处理方法和站点服务器
CN102082775A (zh) 一种用户身份管理方法、装置和系统
US12003512B2 (en) Limiting discovery of a protected resource in a zero trust access model
US20230388383A1 (en) Systems and methods for routing remote application data
CN102045166A (zh) 单点登录的方法及系统
CN103856454A (zh) Ip 多媒体子系统与互联网业务互通的方法及业务互通网关
CN102143091B (zh) 跨域操作的实现方法、系统、服务器和浏览器
CN105721274A (zh) 一种多种即时通讯的融合方法及装置
CN114979043A (zh) 一种富媒体的群聊服务方法、服务器及消息即平台
US9742776B2 (en) Contact identification validation via social invitation
CN103621039A (zh) 用于在计算机网络中访问服务器的服务器、系统、方法、计算机程序和计算机程序产品
WO2015021842A1 (zh) 访问ott应用、服务器推送消息的方法及装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2012738009

Country of ref document: EP

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

Ref document number: 12738009

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE