WO2016124115A1 - 多账号登录、通讯方法、装置和移动终端 - Google Patents

多账号登录、通讯方法、装置和移动终端 Download PDF

Info

Publication number
WO2016124115A1
WO2016124115A1 PCT/CN2016/072778 CN2016072778W WO2016124115A1 WO 2016124115 A1 WO2016124115 A1 WO 2016124115A1 CN 2016072778 W CN2016072778 W CN 2016072778W WO 2016124115 A1 WO2016124115 A1 WO 2016124115A1
Authority
WO
WIPO (PCT)
Prior art keywords
component
service
account
service component
binding
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/CN2016/072778
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.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding 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 Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to JP2017541013A priority Critical patent/JP6685313B2/ja
Publication of WO2016124115A1 publication Critical patent/WO2016124115A1/zh
Priority to US15/669,752 priority patent/US20170331912A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/41—User authentication where a single sign-on provides access to a plurality of computers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H04L51/046—Interoperability with other network applications or services
    • 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
    • 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/18—Network architectures or network communication protocols for network security using different networks or channels, e.g. using out of band channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements

Definitions

  • the present invention relates to the field of communications, and specifically discloses a multi-account login, communication method, device, and mobile terminal.
  • IM instant messaging
  • the core communication layer of IM products is generally fixed, which is difficult to change after implementation, and the work of changing the communication layer is generally complicated, and the labor cost is high.
  • the reconstruction of the communication layer is also facing reconstruction. Unknown risks such as functional failures, it is difficult to achieve the rapid development of the project.
  • the object of the present invention is to provide a multi-account login, communication method, device and mobile terminal, which conveniently realizes that multiple accounts are logged in or communicated in the same instant messaging client.
  • an embodiment of the present invention discloses a multi-account login method, including:
  • Multiple activity components respectively receive account information that needs to be online at the same time
  • the activity component respectively transmits the account information to a corresponding service component in a different process by using a binding instance
  • the service component separately logs in according to the account information.
  • the embodiment of the invention also discloses a multi-account communication method, including:
  • the active component invokes the service component to perform a communication operation through the binding instance.
  • the embodiment of the invention further discloses a multi-account login device, comprising:
  • a receiving module configured to implement, by multiple active components, account information that needs to be online at the same time
  • a calling module configured to: implement, by the binding component, the account component to transmit the account information to a corresponding service component in a different process
  • the login module is configured to implement, respectively, that the service component logs in according to the account information.
  • the embodiment of the invention further discloses a multi-account communication device, comprising:
  • a communication operation module configured to enable the active component to invoke the service component to perform a communication operation by using the binding instance.
  • an embodiment of the present invention further provides a mobile terminal, which has the foregoing apparatus.
  • the active component respectively invokes the corresponding service component in different processes to log in through the binding instance.
  • each account can be bound to the corresponding service process through the binding mechanism, and the independence between the processes can be utilized to realize simultaneous login and communication of multiple accounts.
  • the embodiment of the present invention can implement the function of upgrading an existing single-account instant messaging client to a multi-account simultaneous online login or communication based on the existing IM solution or the socket communication framework, and the implementation is relatively simple, and the development cycle is also very Short, the risk is relatively small, and can well meet the needs of multiple accounts at the same time online.
  • FIG. 1 is a schematic flowchart of a multiple account login method according to an embodiment of the present invention
  • FIG. 2 is a flowchart of configuring an instant messaging client in a multiple account login method according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a multi-account communication method provided by an embodiment of the present invention.
  • FIG. 4 is a flowchart of a multi-account communication method for logging out of a server according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of the multi-account login device according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of another multi-account login device according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a multi-account login device according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a multi-account login device according to an embodiment of the present invention.
  • the “active component” used refers to the Activity component, which is one of the components commonly used in the Android component.
  • the Activity component is an application component that provides an interactive area on the screen that users can use to interact with a task or implement a function.
  • Service component refers to the Service component, which is also one of the commonly used components in the Android component. It can be used to process some time-consuming logic in the background, or to perform certain tasks that require long-term operation. When necessary, the Service component can continue to run in the background even when the program exits.
  • Binding refers to Binder.
  • each application contains some Activity component and Service component. These Activity component and Service component may run in the same process, or may run in different processes. For components running in different processes, the Android system can use the Binder mechanism for interprocess communication. For example, Binder can implement communication between the Activity component running in the main process and the service process running in the service process.
  • FIG. 1 is a schematic flowchart of a multiple account login method according to an embodiment of the present invention.
  • the embodiment shown in FIG. 1 includes steps S101-S103.
  • step S101 the plurality of active components respectively receive account information that needs to be online at the same time.
  • step S102 the active component respectively transmits account information to the service components in different processes through the binding instance.
  • the service component separately logs in according to the account information, and implements multiple accounts.
  • the number is also logged in online for the purpose.
  • the activity component is configured to provide an interaction interface corresponding to the account information, where the user can input account information, such as a user name, a password, and the like, that need to be online at the same time.
  • An instant messaging client can have multiple active components that are loosely bound to each other. Each active component can launch another active component in order to perform different actions.
  • the fallback stack follows the basic "last in, first out" queue mechanism, so when the user completes the work with the current active component and switches the interactive interface, the previous activity will pop up from the fallback stack and return to the previous state.
  • the user interface for receiving account information may be respectively set on different pages (the page may also be provided by the active component), or may be integrated on the same page.
  • the interactive interface for receiving account information has a one-to-one correspondence with the active components. Therefore, when the user inputs the account information to the interactive interface, the activity component can obtain the account information input by the user.
  • three interactive components are required to provide three interactive interfaces for login.
  • the three interactive interfaces can be configured on different pages or on one page.
  • the activity component obtains the account information input by the user from the corresponding interaction interface.
  • each service component can maintain a long connection to the server through a socket connection.
  • Each socket connection has a locally unique socket number, so an instant messaging client can use multiple socket connections to enable multiple account logins or communications. In this way, multiple service components can log in to the server through the corresponding socket long connection to implement multiple accounts to log in at the same time.
  • the active component receives the account information through the corresponding interactive interface, the account information is transmitted to the corresponding service component through the binding instance.
  • the service component sends the account information to the server for login through the established socket long connection.
  • FIG. 2 is a flowchart of configuring an instant messaging client in a multiple account login method according to an embodiment of the present invention.
  • the configuration process includes steps S201-S203.
  • the corresponding active component and the corresponding service component are configured according to the number of accounts that need to be online at the same time. For example, according to the number of accounts that need to be online at the same time, the corresponding active components are configured, and each active component provides an interactive interface for inputting account information.
  • the number of service components and their subclasses is selected based on the number of accounts that need to be online at the same time. For example, if three accounts are required to be online at the same time, it is necessary to implement a service component S 0 and two subclasses of the service component S 0 : the service component S 1 and the service component S 2 , and the subclass inherits the service component S 0 Empty class.
  • the number of simultaneous online accounts is less than or equal to the number of configured service components.
  • the number of simultaneously registered accounts may be one, two, or three.
  • the number of simultaneous online accounts can be selected according to actual needs, and may not be completely the same as the number of service components.
  • Step S202 configuring a plurality of the service components in different service processes.
  • the service component S 0 is configured into the service process
  • the service component S 1 is configured into the service1 process
  • the service component S 2 is configured to the service2 process. in.
  • step S203 the process in which the active component is located is bound to the service process of the corresponding service component, and the corresponding binding instance (Binder) is obtained.
  • the service component When the active component is bound to the service component, if the service component has not established a socket connection with the server, the service component first establishes a socket connection with the server. If the active component receives the account information, the active component passes the account information to the service component through the binding instance, and the service component logs in to the server through the socket connection.
  • the processes in which the active components are located are respectively bound to the service processes in which the corresponding service components are located.
  • the service component feeds back the corresponding binding instance (ie, Binder) to the active component.
  • the active component can call the service component to log in to the server through the binding instance.
  • three account accounts are required to log in at the same time, and three interactive interfaces provided by the active component A 0 , the active component A 1 , and the active component A 2 respectively receive user input account information.
  • the process in which the active component A 0 ie, the Activity component
  • is located is bound to the Service process in which the service component S 0 is located through the Binder mechanism.
  • the process in which the active component A 1 is located is bound to the Service1 process in which the service component S 1 is located, and the process in which the active component A 2 is located is also bound to the Service2 process in which the service component S 2 is located.
  • the movable assembly A 0 which is bound to the service process through which the Service component S 0 corresponding to the acquired process instance binding B 0; A 1 in which the active component is bound to a service process in which the component S 1 the acquired corresponding service process Service1 binding instance B 1; a 2 in which the movable assembly process is bound to S Service2 service process service component 2 is located to the corresponding binding instance acquired B 2.
  • the Service process, the Service1 process, and the Service2 process are different service processes.
  • the active component A 0 , the active component A 1 , and the active component A 2 can call the corresponding service component S 0 , the service component S 1 , and the service through the binding instance B 0 , the binding instance B 1 , and the binding instance B 2 respectively .
  • Component S 2 uses a different account to log in. For example, if the user needs to log in three accounts at the same time: the first account, the second account, and the third account, the active component A 0 receives the first account through the corresponding interaction interface, and invokes the corresponding service by binding the instance B 0 .
  • the component S 0 is logged in to the first account; after the activity component A 1 receives the second account through the corresponding interaction interface, the corresponding service component S 1 is invoked by the binding instance B 1 to log in to the second account; the active component A 2 passes the corresponding interaction. after receiving the third interface account, by binding the component invokes the service example B 2 S 2 corresponding to the account to log in the third, thereby enabling three login account simultaneously.
  • the service component S 0 , the service component S 1 , and the service component S 2 are running in different processes, and one process has a Socket connection, the function of simultaneously logging in multiple accounts can be realized.
  • a 0 active components can bind the call log Example B (Login) Method 0 0
  • Example B binding component invokes the service corresponding to S 0 login operation to log in the corresponding account to the server.
  • B 0 may also bind instance, the registration result is returned to the active component via a callback function A 0 A 0 a movable assembly disposed.
  • the active component A 1 and the active component A 1 can also log in to the corresponding account by calling the corresponding login instance B 1 or the binding instance B 2 login method to implement multiple account login.
  • the embodiment of the invention also discloses a multi-account communication method.
  • the method includes the step of logging in (step S301) by using the login method provided by the embodiment shown in FIG.
  • step S302 the active component performs a communication operation through the corresponding binding instance.
  • the active component receives a new message to receive the listener through the binding instance. This way, if the service component receives a message from the server, it can notify the active component through the binding instance. Similarly, if the service component receives a send message request initiated by the active component, the service component sends a message to the server over the socket connection.
  • the foregoing “communication operation” includes, but is not limited to, the active component sends a message to the server by calling the service component through the binding instance, and the service component feeds back the received message to the active component through the binding instance, and the active component passes the The binding instance calls the service component to log out of the server.
  • the active component invokes the sendMessage method of the binding instance, and the calling service component triggers a send message operation to deliver the message to the server.
  • the service component After the message is successfully sent, the service component returns the result of the sent message to the active component by using the callback set by the active component through the binding instance.
  • the service component may receive a message sent by another person, and may change the message content by binding the callback set by the instance and the active component. Pass through to the active component.
  • FIG. 4 is a flowchart of a multi-account communication method for logging out of a server according to an embodiment of the present invention.
  • the embodiment shown in Figure 4 includes steps S401-S403. After the login is performed in the embodiment shown in FIG. 1 in step S401, the process proceeds to steps S402 and S403.
  • step S402 the active component can call the service component to log out of the server through the binding instance. Then, in step S403, the binding of the active component to the service component is released. For example, on the fly At the end of the communication scenario, the active component can call the login instance's logout method (logout), and the binding instance invokes the service component's logout operation to log out of the server. After the logout is successful, the binding instance can return the logout result to the active component through the callback set by the active component. The last active component is unbound from the service component.
  • logout logout method
  • the binding instance invokes the service component's logout operation to log out of the server.
  • the binding instance can return the logout result to the active component through the callback set by the active component. The last active component is unbound from the service component.
  • the instant messaging client may have packaged basic logic such as login, messaging, socket long connection retention, etc. in the service component.
  • basic logic such as login, messaging, socket long connection retention, etc.
  • the binding properties of a service component determine that these existing solutions are cross-process. Therefore, the function of supporting multiple accounts and simultaneous login can be realized by binding the service in which the service component is located to the active component.
  • the instruction code can be stored in any type of computer-accessible memory (eg, permanent or modifiable, volatile or non-volatile, solid state Or non-solid, fixed or replaceable media, etc.).
  • the memory may be, for example, Programmable Array Logic ("PAL"), Random Access Memory (RAM), or Programmable Read Only Memory (PROM). "), Read-Only Memory (“ROM”), Electrically Erasable Programmable ROM (“EEPROM”), Disk, CD, Digital Versatile Disc , referred to as "DVD”) and so on.
  • PAL Programmable Array Logic
  • RAM Random Access Memory
  • PROM Programmable Read Only Memory
  • ROM Read-Only Memory
  • EEPROM Electrically Erasable Programmable ROM
  • Disk CD
  • DVD Digital Versatile Disc
  • FIG. 5 is a schematic structural diagram of a multi-account login device provided by an embodiment of the present application.
  • the multi-account login device 10 includes a receiving module 11, a calling module 12, and a login module 13.
  • the receiving module 11 is configured to implement that multiple active components respectively receive account information that needs to be online at the same time.
  • the calling module 12 is configured to implement the activity component to pass the account information to the corresponding service component in different processes through the binding instance.
  • the login module 13 is configured to implement that the service component separately logs in according to the account information.
  • FIG. 6 is a schematic structural diagram of another multi-account login device according to an embodiment of the present invention.
  • the multi-account login device 10 includes the receiving module 11, the calling module 12, and the login module 13 in the embodiment shown in FIG. 5, and further includes a first configuration module 14, a second configuration module 15, and a third configuration.
  • Module 16 is a schematic structural diagram of another multi-account login device according to an embodiment of the present invention.
  • the multi-account login device 10 includes the receiving module 11, the calling module 12, and the login module 13 in the embodiment shown in FIG. 5, and further includes a first configuration module 14, a second configuration module 15, and a third configuration. Module 16.
  • the first configuration module 15 is configured to configure a service component and a subclass of multiple service components according to the number of account information that needs to be online at the same time, wherein the subclass inherits the empty class of the service component.
  • the second configuration module 16 is configured to implement configuring multiple service components in different service processes in a configuration file of the Android system.
  • the third configuration module 17 includes a binding module 171 and a binding feedback module 172.
  • the binding module 171 is configured to respectively bind the process in which the active component is located with the service process in which the corresponding service component is located.
  • the binding feedback module 172 is configured to implement the service component to feed back the corresponding binding instance to the active component.
  • the above embodiment is an apparatus embodiment corresponding to the login method embodiment, and the present embodiment can be implemented in cooperation with the embodiment of the login method.
  • the related technical details mentioned in the embodiment of the login method are still valid in the present embodiment, and are not described herein again in order to reduce the repetition. Accordingly, the related technical details mentioned in the present embodiment can also be applied to the login method implementation.
  • FIG. 7 is a schematic structural diagram of a multi-account login device provided by the embodiment.
  • the multi-account communication device includes the multi-account login device 10 and the communication operation module 20 according to the embodiment shown in FIG. 6.
  • the communication operation module 20 is configured to implement the communication operation by the active component by calling the service component through the corresponding binding instance.
  • the communication operation module 20 includes, but is not limited to, a sending submodule 21 for implementing an activity component to send a message to the server by calling the service component through the binding instance, and a method for implementing the service component to feed back the received message to the active component through the binding instance.
  • the receiving submodule 22 is configured to implement the logout submodule 23 for the active component to log out of the server by calling the service component through the binding instance.
  • the communication device further includes a result feedback module, configured to enable the service component to feed back the result of the communication operation to the active component through the binding instance.
  • the communication operation module 20 includes a logout submodule 24 and a debinding submodule 25.
  • the logout submodule 24 is configured to implement the active component to log out of the server by calling the service component through the binding instance.
  • the unbinding sub-module 25 is used to implement binding of the active component to the service component.
  • the embodiment shown in Fig. 4 is a method embodiment corresponding to the present embodiment, and the present embodiment can be implemented in cooperation with the embodiment shown in Fig. 4.
  • the related technical details mentioned in the embodiment shown in FIG. 4 are still effective in the present embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related technical details mentioned in the present embodiment can also be applied to the embodiment shown in FIG.
  • the application relates to a mobile terminal having the apparatus of any of the embodiments illustrated in Figures 5-8.
  • each unit mentioned in the embodiments of the present invention is a logical unit.
  • a logical unit may be a physical unit, a part of a physical unit, or multiple physical entities.
  • the combined implementation of the elements, the physical implementation of these logical units themselves is not the most important, the combination of the functions implemented by these logical units is the key to solving the technical problems raised by the present invention.
  • the above-mentioned various device embodiments of the present invention do not introduce a unit that is not closely related to solving the technical problem proposed by the present invention, which does not indicate that the above device implementation does not have other unit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明涉及通信领域，公开了一种多账号登录和通讯方法、装置和移动终端，该登录方法包括：多个活动组件分别接收需要同时在线的账号信息；所述活动组件通过绑定实例分别向对应的处于不同进程中的服务组件传递所述账号信息；所述服务组件根据所述账号信息分别进行登录。本发明实施例通过将服务组件配置在不同的服务进程中，利用绑定机制将服务进程与对应的活动组件所在的进程进行绑定。这样，将每个账号通过绑定机制绑定到相应的服务进程中，利用进程的独立性，来实现多账号同时登录。

Description

多账号登录、通讯方法、装置和移动终端 技术领域
本发明涉及通讯领域，具体公开了一种多账号登录、通讯方法、装置和移动终端。
背景技术
随着IM(即时通讯)产品的发展，用户的需求也越来越多，例如希望IM产品可以支持多个账号同时在线来收发消息。但是目前IM产品大都只支持单账号登陆，登陆其他账号需要先将当前账号登出。如何快速的将单账号支持版本升级到多账号支持版本，成为了众多IM开发工程师需要解决的问题。
如果需要实现多个账号同时在线来满足不同使用场景下的沟通需要，开发者有三种实现方式：
1、放弃现有IM解决方案或者现成的socket通信框架，自己编写IM逻辑。
2、推动当前IM解决方案的提供方或者socket通信框架的提供方来提供多账号支持。
3、如果IM解决方案是自己实现的，则需要重构通信层来增加多账号支持。
对于第一种方式，由于IM底层socket层通信逻辑编写较为复杂，而目前大部分IM产品开发均采用现有的IM解决方案(如环信，亲加通信云)或者现成的socket层通信解决框架(如mina)，改写IM逻辑比较困难。尽管也有一些IM产品使用自身的IM底层功能，但这种方式成本太高。对于第二种方式，同时要求当前IM解决方案的提供方或者socket通信框架的提供方 来提供多账号支持需要大量时间，在对多账号支持的需求迫切的情况下不太适用，很可能错过推广的时机而失去大量用户。对于第三种实现方式，IM产品的核心通信层一般都较固定，实现后较难变更，而且一般更改通信层的工作较为复杂，人力成本较高；同时，通信层的重构也面临重构后的功能故障等未知风险，难以实现项目的快速开发的需求。
发明内容
本发明的目的在于提供一种多账号登录、通讯方法、装置和移动终端，便捷地实现多个账号在同一个即时通讯客户端中登录或通讯。
为解决上述技术问题，本发明的实施方式公开了一种多账号登录方法，包括：
多个活动组件分别接收需要同时在线的账号信息；
所述活动组件通过绑定实例分别向对应的处于不同进程中的服务组件传递所述账号信息；
所述服务组件根据所述账号信息分别进行登录。
本发明的实施方式还公开了一种多账号通讯方法，包括：
上述的多账号登录方法的步骤；以及
所述活动组件通过所述绑定实例调用所述服务组件进行通讯操作。
本发明的实施方式又公开了一种多账号登录装置，包括：
接收模块，用于实现多个活动组件分别接收需要同时在线的账号信息；
调用模块，用于实现所述活动组件通过绑定实例向对应的处于不同进程中的服务组件传递所述账号信息；
登录模块，用于实现所述服务组件根据所述账号信息分别进行登录。
本发明的实施方式又公开了一种多账号通讯装置，包括：
上述的多账号登录装置；以及
通讯操作模块，用于实现所述活动组件通过所述绑定实例调用所述服务组件进行通讯操作。
另外，本发明实施例又提供了一种移动终端，具有上述的装置。
本发明实施方式与现有技术相比，主要区别及其效果在于：本发明实施例中，活动组件分别通过绑定实例调用对应的处于不同进程中的服务组件进行登录。这样，可以实现将每个账号通过绑定机制绑定到相应的服务进程中，利用进程之间的独立性来实现多账号同时登录和通讯。
本发明实施方式可以基于现有的IM解决方案或者socket通信框架，实现将现有的单账号即时通讯客户端升级到具备多账号同时在线登录或通讯的功能，实现较为简单，开发的周期也非常短，风险也是相对较少，可以很好的满足多账号同时在线的需求。
附图说明
图1是本发明实施方式提供的多账号登录方法的流程示意图；
图2是本发明实施方式提供的多账号登录方法中对即时通讯客户端进行配置的流程图；
图3是本发明实施方式提供的多账号通讯方法的流程示意图；
图4是本发明实施方式提供的多账号通讯方法登出服务器的流程图；
图5是本发明实施方式提供的该多账号登录装置的结构示意图；
图6是本发明实施方式提供的另一种多账号登录装置的结构示意图；
图7是本发明实施方式提供的多账号登录装置的结构示意图；
图8是本发明实施方式提供的多账号登录装置的结构示意图。
具体实施方式
在以下的叙述中，为了使读者更好地理解本申请而提出了许多技术细节。但是，本领域的普通技术人员可以理解，即使没有这些技术细节和基于以下各实施方式的种种变化和修改，也可以实现本申请各权利要求所要求保护的技术方案。
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明的实施方式作进一步地详细描述。
在本发明涉及的实施方式中，使用的“活动组件”是指Activity组件，其是安卓(Android)组件中常用的组件之一。Activity组件是一个应用程序组件，在屏幕上提供一个交互区域，用户可以用来交互完成某项任务或实现某项功能。“服务组件”是指Service组件，其也是Android组件中常用的组件之一，它可以用于在后台处理一些耗时的逻辑，或者执行某些需要长期运行的任务。必要的时候，甚至在程序退出的情况下，Service组件也还可以在后台继续保持运行状态。“绑定”是指Binder。在Android系统中，每一个应用程序都包含一些Activity组件和Service组件，这些Activity组件和Service组件有可能运行在同一个进程中，也有可能运行在不同的进程中。对于运行在不同的进程中的组件，Android系统可以采用Binder机制来进行进程间通信。例如Binder可以实现运行在主进程的Activity组件与运行在服务进程中的服务进程之间的通讯。
参见图1，图1是本发明实施方式提供的一种多账号登录方法的流程示意图，图1示出的实施方式包括步骤S101-S103。
在步骤S101中，多个活动组件分别接收需要同时在线的账号信息。
此后进入步骤S102，活动组件通过绑定实例分别向处于不同进程中的服务组件传递账号信息。
此后进入步骤S103，服务组件根据账号信息分别进行登录，实现多账 号同时登录在线的目的。
具体而言，活动组件用于提供与账号信息对应的交互界面，用户可以在该交互界面中输入需要同时在线的账号信息，例如用户名、密码等。即时通讯客户端可以有多个活动组件，这些活动组件彼此松散的绑定在一起。每个活动组件为了执行不同的行为，能够启动另一个活动组件。当启动一个新的活动组件，前一个活动组件会被停止，但安卓系统把这个活动组件保留到一个堆栈中(回退堆栈)的顶部，其对应的交互界面失去用户焦点。回退堆栈遵循基本的“后进先出”队列机制，因此当用户用当前的活动组件完成工作后，并切换交互界面时，前一个活动会从该回退堆栈中弹出，并回复之前的状态。
在一些实施方式中，用户接收账户信息的交互界面可以分别设于不同的页面(该页面也可以是活动组件提供的)上，也可以集成在同一个页面上。用于接收账户信息的交互界面与活动组件是一一对应的。因此，当用户向交互界面输入账户信息后，活动组件可以得到用户输入的账户信息。
例如，如果需要三个账号登录，则需要由三个活动组件提供三个用于登录的交互界面。这三个交互界面可以分别配置在不同的页面上，也可以配置在一个页面上。活动组件从对应的交互界面获取用户输入的账号信息。
另外一方面，每个服务组件可以通过一个socket连接与服务器保持长连接。每个socket连接具有本地唯一的socket号，因此，即时通讯客户端可以使用多个socket连接实现多账号的登录或通讯。这样，多个服务组件可以分别通过对应的socket长连接来登录服务器实现多账号同时登录。
如果活动组件经对应的交互界面接收到账号信息，则通过绑定实例将账号信息传递给对应的服务组件。服务组件通过建立的socket长连接将账户信息发送到服务器进行登录。
为了实现多账号登录，需要在使用前对即时通讯客户端进行配置。参 见图2，图2是本发明实施方式提供的多账号登录方法中对即时通讯客户端进行配置的流程图。所述的配置过程包括步骤S201-S203。
在步骤S201中，根据需要同时在线的账号数量，配置对应活动组件和对应的服务组件。例如，根据需要同时在线的账号数量，配置对应的活动组件，每个活动组件提供一个用于输入账户信息的交互界面。此外，根据需要同时在线的账号的数量，选择服务组件及其子类的数量。例如，如果需要三个账号同时在线，则需要实现一个服务组件S0，以及两个该服务组件S0的子类：服务组件S1与服务组件S2，子类继承了服务组件S0的空类。这样，可以实现三个活动组件：服务组件S0、服务组件S1、服务组件S2，满足需要三账号同时在线的需求。在登录过程中，同时在线的账号数量小于或等于配置的服务组件的数量，例如在配置了三个服务组件的实施方式中，同时登录的账号数量可以是1个、2个或3个。用户在使用过程中可以依据实际需要选择同时在线的账号数量，并不一定完全与服务组件的数量相同。
步骤S202，将多个所述服务组件配置在不同的服务进程中。
具体实现过程中，例如可以在安卓系统中的AndroidManifest配置文件中，将上述的服务组件S0配置到service进程中，将服务组件S1配置到service1进程中，将服务组件S2配置到service2进程中。
步骤S203，分别将活动组件所处的进程与对应的服务组件的所处的服务进程绑定，获取对应的绑定实例(Binder)。当活动组件与服务组件绑定时，如果服务组件尚未与服务器建立socket连接，则服务组件首先与服务器建立socket连接。如果活动组件接收到账号信息，活动组件通过绑定实例将账号信息传递给服务组件，服务组件通过该socket连接登录到服务器。
具体而言，将活动组件所处的进程分别分别与对应的服务组件所处的服务进程进行绑定。完成绑定后，服务组件向活动组件反馈对应的绑定实例(即Binder)。这样，活动组件分别可以通过绑定实例调用服务组件登录服 务器。例如，在一些实施方式中，需要三个账号同时登录，由活动组件A0、活动组件A1、活动组件A2提供三个交互界面分别接收用户输入账户信息。活动组件A0(即Activity组件)所处的进程通过Binder机制绑定到了服务组件S0所处的Service进程。同时，活动组件A1所处的进程绑定到了服务组件S1所处的Service1进程，活动组件A2所处的进程还绑定到了服务组件S2所处的Service2进程。这样，活动组件A0所处的进程通过绑定到服务组件S0所处的Service进程获取到对应的绑定实例B0；活动组件A1所处的进程绑定到服务组件S1所处的Service1服务进程获取到对应绑定实例B1；活动组件A2所处的进程绑定到服务组件S2所处的Service2服务进程获取到对应的绑定实例B2。其中，Service进程、Service1进程和Service2进程分别为不同的服务进程。
因此，活动组件A0、活动组件A1、活动组件A2可以分别通过绑定实例B0、绑定实例B1、绑定实例B2调用对应的服务组件S0、服务组件S1、服务组件S2来使用不同的账号进行登录。例如，假如用户需要同时登录三个账号：第一账号、第二账号和第三账号，则活动组件A0通过对应的交互界面接收到第一账号后，通过绑定实例B0调用对应的服务组件S0登录第一账号；活动组件A1通过对应的交互界面接收到第二账号后，通过绑定实例B1调用对应的服务组件S1登录第二账号；活动组件A2通过对应的交互界面接收到第三账号后，通过绑定实例B2调用对应的服务组件S2登录第三账号，从而可以实现三个账号同时登录。
因为服务组件S0、服务组件S1、服务组件S2运行在不同进程之中，而一个进程具有一条Socket连接，从而可以实现多账号同时登录在线的功能。在图1示出的实施方式中，在调用对应的绑定实例B0时，活动组件A0可以调用绑定实例B0的登录(login)方法，绑定实例B0调用对应的服务组件S0的登录操作来登录对应的账号到服务器。登录成功后，绑定实例B0还可以通过活动组件A0设置的回调函数，将登录结果返回给活动组件A0。同样，活动组 件A1和活动组件A1也可以对应调用对应的绑定实例B1或绑定实例B2的登录(login)方法来登录相应的账号，实现多账号登录。
此外，本发明实施例还公开了一种多账号通讯方法。请参阅图3，该方法包括利用图1示出的实施方式提供的登录方法登录(步骤S301)后，还包括步骤S302。
在步骤S302中，活动组件通过对应的绑定实例进行通讯操作。在服务组件建立socket连接后，活动组件通过绑定实例注册新消息接收监听。这样，如果服务组件收到来自服务器的消息即可通过绑定实例通知给活动组件。同样，如果服务组件收到活动组件发起的发送消息请求时，服务组件通过socket连接将消息发送到服务器。
在一些实施方式中，上述的“通讯操作”包括但不限于：活动组件通过绑定实例调用服务组件向服务器发送消息、服务组件通过绑定实例将接受到的消息反馈至活动组件、活动组件通过绑定实例调用服务组件登出服务器。例如，在活动组件通过绑定实例调用服务组件向服务器发送消息的实施方式中，活动组件调用绑定实例的sendMessage方法，调用服务组件触发发送消息操作，将消息传递给服务器。消息发送成功后，服务组件通过绑定实例利用活动组件设置的回调，将发送消息结果返回给活动组件。又如，在服务组件通过绑定实例将接受到的消息反馈至活动组件的实施方式中，服务组件可能会收到别人发送的消息，可以通过绑定实例与活动组件设置的回调，将消息内容透传到活动组件。
在另外一些实施方式中，参见图4，图4是本发明实施提供的多账号通讯方法登出服务器的流程图。在图4示出的实施方式包括步骤S401-S403。步骤S401中利用图1示出的实施方式进行登录后，进入步骤S402和S403。
在步骤S402中，活动组件可以通过绑定实例调用服务组件登出服务器。然后，在步骤S403中，解除活动组件与服务组件的绑定。例如，在即 时通讯的场景结束的时候，活动组件可以调用绑定实例的登出方法(logout)，绑定实例调用服务组件的登出操作来登出服务器。登出成功后，绑定实例可通过活动组件设置的回调，将登出结果返回给活动组件。最后活动组件与服务组件解除绑定。
在另外一些现有的实施方式中，即时通讯客户端可能已经将基本逻辑如登录、消息收发、socket长连接保持等封装在服务组件中。通常服务组件的绑定属性决定了这些现有的解决方案都是跨进程的。因此，将服务组件所处的服务进行绑定到活动组件即可实现支持多账号同时登录的功能。
本申请的各方法实施方式均可以以软件、硬件、固件等方式实现。不管本申请是以软件、硬件、还是固件方式实现，指令代码都可以存储在任何类型的计算机可访问的存储器中(例如永久的或者可修改的，易失性的或者非易失性的，固态的或者非固态的，固定的或者可更换的介质等等)。同样，存储器可以例如是可编程阵列逻辑(Programmable Array Logic，简称“PAL”)、随机存取存储器(Random Access Memory，简称“RAM”)、可编程只读存储器(Programmable Read Only Memory，简称“PROM”)、只读存储器(Read-Only Memory，简称“ROM”)、电可擦除可编程只读存储器(Electrically Erasable Programmable ROM，简称“EEPROM”)、磁盘、光盘、数字通用光盘(Digital Versatile Disc，简称“DVD”)等等。
本申请的实施方式还涉及一种多账号登录装置。图5是本申请实施方式提供的多账号登录装置的结构示意图。具体地说，该多账号登录装置10包括接收模块11、调用模块12和登录模块13。
其中，接收模块11用于实现多个活动组件分别接收需要同时在线的账号信息。调用模块12用于实现活动组件通过绑定实例向对应的处于不同进程中的服务组件传递账号信息。登录模块13用于实现服务组件根据账号信息分别进行登录。
参见图6，图6是本发明实施例提供的另一种多账号登录装置的结构示意图。具体地说，该多账号登录装置10包括图5示出的实施方式中的接收模块11、调用模块12和登录模块13外，还包括第一配置模块14、第二配置模块15和第三配置模块16。
其中，第一配置模块15用于根据需要同时在线的账号信息的数量，配置服务组件及多个服务组件的子类，其中，子类继承该服务组件的空类。第二配置模块16用于在安卓系统的配置文件中实现将多个服务组件配置在不同的服务进程中。第三配置模块17包括绑定模块171和绑定反馈模块172。绑定模块171用于将活动组件所处的进程与对应的服务组件所处的服务进程分别进行绑定。绑定反馈模块172用于实现服务组件向活动组件反馈对应的绑定实例。
上述实施方式是与登录方法实施方式相对应的装置实施方式，本实施方式可与登录方法的实施方式互相配合实施。该登录方法实施方式中提到的相关技术细节在本实施方式中依然有效，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在登录方法实施方式中。
本申请实施方式还涉及一种多账号通讯装置。图7是该实施方式提供的多账号登录装置的结构示意图。具体地说，该多账号通讯装置包括图6示出的实施方式涉及的多账号登录装置10和通讯操作模块20。其中，通讯操作模块20用于实现活动组件通过对应的绑定实例调用服务组件进行通讯操作。通讯操作模块20包括但不限于：用于实现活动组件通过绑定实例调用服务组件向服务器发送消息的发送子模块21、用于实现服务组件通过绑定实例将接受到的消息反馈至活动组件的接收子模块22、用于实现活动组件通过绑定实例调用服务组件登出服务器的登出子模块23。在一些实施方式中，该通讯装置还包括结果反馈模块，用于实现服务组件通过绑定实例将通讯操作的结果反馈给活动组件。
在另外一些实施方式中，参见图8，通讯操作模块20包括登出子模块24、解除绑定子模块25。其中，登出子模块24用于实现活动组件通过绑定实例调用服务组件登出服务器。解除绑定子模块25用于实现活动组件解除与服务组件的绑定。
图4示出的实施方式是与本实施方式相对应的方法实施方式，本实施方式可与图4示出的实施方式互相配合实施。图4示出的实施方式中提到的相关技术细节在本实施方式中依然有效，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在图4示出的实施方式中。
此外，本申请还涉及一种移动终端，其具有图5-图8示出的任一实施方式的装置。
需要说明的是，本发明各设备实施方式中提到的各单元都是逻辑单元，在物理上，一个逻辑单元可以是一个物理单元，也可以是一个物理单元的一部分，还可以以多个物理单元的组合实现，这些逻辑单元本身的物理实现方式并不是最重要的，这些逻辑单元所实现的功能的组合才是解决本发明所提出的技术问题的关键。此外，为了突出本发明的创新部分，本发明上述各设备实施方式并没有将与解决本发明所提出的技术问题关系不太密切的单元引入，这并不表明上述设备实施方式并不存在其它的单元。
需要说明的是，在本专利的权利要求和说明书中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个”限定的要素，并不排除在包括所述要素的过程、方法、物品或 者设备中还存在另外的相同要素。
虽然通过参照本发明的某些优选实施方式，已经对本发明进行了图示和描述，但本领域的普通技术人员应该明白，可以在形式上和细节上对其作各种改变，而不偏离本发明的精神和范围。

Claims (17)

  1. 一种多账号登录方法，其特征在于，包括：
    多个活动组件分别接收需要同时在线的账号信息；
    所述活动组件通过绑定实例分别向对应的处于不同进程中的服务组件传递所述账号信息；
    所述服务组件根据所述账号信息分别进行登录。
  2. 如权利要求1所述的多账号登录方法，其特征在于，所述“所述活动组件通过绑定实例分别向对应的处于不同进程中的服务组件传递所述账号信息”的步骤之前，还包括：
    根据需要同时在线的账号信息的数量，配置所述服务组件及多个所述服务组件的子类，所述子类继承所述服务组件的空类。
  3. 如权利要求1所述的多账号登录方法，其特征在于，所述“所述活动组件通过绑定实例分别向对应的处于不同进程中的服务组件传递所述账号信息”的步骤之前，还包括：
    将活动组件所处的进程与所述服务组件所处的服务进程分别进行绑定；
    所述服务组件向所述活动组件反馈对应的绑定实例。
  4. 如权利要求1所述的多账号登录方法，其特征在于，所述“所述活动组件通过绑定实例分别向对应的处于不同进程中的服务组件传递所述账号信息”的步骤之前，还包括：
    在安卓系统的配置文件中实现将所述服务组件配置在不同的服务进程中。
  5. 一种多账号通讯方法，其特征在于，包括：
    如权利要求1-4任一项所述的多账号登录方法的步骤；以及
    所述活动组件通过所述绑定实例调用所述服务组件进行通讯操作。
  6. 如权利要求5所述的多账号通讯方法，其特征在于，所述通讯操作包括：所述活动组件通过所述绑定实例调用所述服务组件向服务器发送消息、所述服务组件通过所述绑定实例将接受到的消息反馈至所述活动组件、所述活动组件通过所述绑定实例调用所述服务组件登出服务器中的一种或多种。
  7. 如权利要求5所述的多账号通讯方法，其特征在于，所述“所述活动组件通过所述绑定实例调用所述服务组件进行通讯操作”的步骤后，还包括：
    所述服务组件通过所述绑定实例将通讯操作的结果反馈给所述活动组件。
  8. 如权利要求5所述的多账号通讯方法，其特征在于，所述“所述活动组件通过所述绑定实例调用所述服务组件进行通讯操作”的步骤包括：
    所述活动组件通过所述绑定实例调用所述服务组件登出服务器；
    所述活动组件解除与所述服务组件的绑定。
  9. 一种多账号登录装置，其特征在于，包括：
    接收模块，用于实现多个活动组件分别接收需要同时在线的账号信息；
    调用模块，用于实现所述活动组件通过绑定实例分别向对应的处于不同进程中的服务组件传递所述账号信息；
    登录模块，用于实现所述服务组件根据所述账号信息分别进行登录。
  10. 如权利要求9所述的多账号登录装置，其特征在于，还包括：
    第一配置模块，用于根据需要同时在线的账号信息的数量，配置所述服 务组件及多个所述服务组件的子类，所述子类继承所述服务组件的空类。
  11. 如权利要求9所述的多账号登录装置，其特征在于，还包括第二配置模块，用于在安卓系统的配置文件中实现将所述服务组件配置在不同的服务进程中。
  12. 如权利要求9所述的多账号登录装置，其特征在于，还包括第三配置模块，所述第三配置模块包括：
    绑定模块，用于将所述活动组件所处的进程与所述服务组件所处的服务进程分别进行绑定；
    绑定反馈模块，用于实现所述服务组件向所述活动组件反馈对应的绑定实例。
  13. 一种多账号通讯装置，其特征在于，包括：
    如权利要求9-12任一项所述的多账号登录装置；以及
    通讯操作模块，用于实现所述活动组件通过所述绑定实例调用所述服务组件进行通讯操作。
  14. 如权利要求13所述的多账号通讯装置，其特征在于，所述通讯操作模块包括：用于实现所述活动组件通过所述绑定实例调用所述服务组件向服务器发送消息的发送子模块、用于实现所述服务组件通过所述绑定实例将接受到的消息反馈至所述活动组件的接收子模块、用于实现所述活动组件通过所述绑定实例调用所述服务组件登出服务器的登出子模块中的一种或多种。
  15. 如权利要求13所述的多账号通讯装置，其特征在于，还包括：
    结果反馈模块，用于实现所述服务组件通过所述绑定实例将通讯操作的结果反馈给所述活动组件。
  16. 如权利要求13所述的多账号通讯装置，其特征在于，所述通讯操 作模块包括：
    登出子模块，用于实现所述活动组件通过所述绑定实例调用所述服务组件登出服务器；
    解除绑定子模块，用于实现所述活动组件解除与所述服务组件的绑定。
  17. 一种移动终端，其特征在于，具有如权利要求9-16任一项所述的装置。
PCT/CN2016/072778 2015-02-05 2016-01-29 多账号登录、通讯方法、装置和移动终端 Ceased WO2016124115A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2017541013A JP6685313B2 (ja) 2015-02-05 2016-01-29 マルチアカウントのログイン及び通信方法、装置、ならびにモバイル端末
US15/669,752 US20170331912A1 (en) 2015-02-05 2017-08-04 Multi-account login and communication

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510062182.XA CN105991402A (zh) 2015-02-05 2015-02-05 多账号登录、通讯方法、装置和移动终端
CN201510062182.X 2015-02-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/669,752 Continuation US20170331912A1 (en) 2015-02-05 2017-08-04 Multi-account login and communication

Publications (1)

Publication Number Publication Date
WO2016124115A1 true WO2016124115A1 (zh) 2016-08-11

Family

ID=56563458

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/072778 Ceased WO2016124115A1 (zh) 2015-02-05 2016-01-29 多账号登录、通讯方法、装置和移动终端

Country Status (4)

Country Link
US (1) US20170331912A1 (zh)
JP (1) JP6685313B2 (zh)
CN (1) CN105991402A (zh)
WO (1) WO2016124115A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110519258A (zh) * 2019-08-22 2019-11-29 深圳市丰润达科技有限公司 设备接入账户控制方法、控制装置和可读存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106484481B (zh) * 2016-10-10 2020-01-14 Oppo广东移动通信有限公司 一种多开应用的配置方法、装置及终端
CN107645441A (zh) * 2017-09-16 2018-01-30 宁波亿拍客网络科技有限公司 一种可以同时登录超过一个帐号的即时通讯工具
CN114338581B (zh) * 2022-01-10 2023-09-29 土巴兔集团股份有限公司 多账号的通讯管理方法及相关装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004027562A2 (en) * 2002-09-17 2004-04-01 Bellsouth Intellectual Property Corporation Server-based message protocol translation
CN102082775A (zh) * 2009-11-27 2011-06-01 中国移动通信集团公司 一种用户身份管理方法、装置和系统
CN102801656A (zh) * 2012-08-29 2012-11-28 腾讯科技（深圳）有限公司 实现即时通信应用的状态控制、修改方法、设备及系统
CN103634195A (zh) * 2012-08-22 2014-03-12 中兴通讯股份有限公司 通讯方法及装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4049327B2 (ja) * 2004-10-29 2008-02-20 インターナショナル・ビジネス・マシーンズ・コーポレーション 複数のインスタント・メッセージング・ログイン・セッションのための方法、システムおよびコンピュータ・プログラム
CN101252548A (zh) * 2008-01-28 2008-08-27 北京亿企通信息技术有限公司 一种在即时通信工具中多点登录的方法
CN101924681A (zh) * 2009-06-15 2010-12-22 北京华智大为科技有限公司 一种网页即时通讯的数据分流方法及装置
CN102081617A (zh) * 2009-11-26 2011-06-01 英业达股份有限公司 在线咨询方法与系统
KR101536785B1 (ko) * 2010-10-29 2015-07-17 네이버 주식회사 멀티 로그인을 이용한 통합 커뮤니케이션 시스템 및 방법 그리고 통합 커뮤니케이션 툴의 동작을 제어하는 단말기 및 단말기에서의 커뮤니케이션 방법
WO2012111058A1 (ja) * 2011-02-15 2012-08-23 Ｎｅｃカシオモバイルコミュニケーションズ株式会社 携帯端末装置およびその画面表示方法
CN103259770A (zh) * 2012-02-17 2013-08-21 腾讯科技（深圳）有限公司 登录方法及登录服务器

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004027562A2 (en) * 2002-09-17 2004-04-01 Bellsouth Intellectual Property Corporation Server-based message protocol translation
CN102082775A (zh) * 2009-11-27 2011-06-01 中国移动通信集团公司 一种用户身份管理方法、装置和系统
CN103634195A (zh) * 2012-08-22 2014-03-12 中兴通讯股份有限公司 通讯方法及装置
CN102801656A (zh) * 2012-08-29 2012-11-28 腾讯科技（深圳）有限公司 实现即时通信应用的状态控制、修改方法、设备及系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110519258A (zh) * 2019-08-22 2019-11-29 深圳市丰润达科技有限公司 设备接入账户控制方法、控制装置和可读存储介质

Also Published As

Publication number Publication date
CN105991402A (zh) 2016-10-05
JP2018514829A (ja) 2018-06-07
JP6685313B2 (ja) 2020-04-22
US20170331912A1 (en) 2017-11-16

Similar Documents

Publication Publication Date Title
US9854045B2 (en) Generic cloud enabling of stateful applications
US9674123B2 (en) System and method for message dispatching and communication
EP3913859B1 (en) Vnf life cycle management method and apparatus
CN111324412A (zh) 服务部署方法、设备及存储介质
CN107580083A (zh) 一种容器ip地址分配的方法和系统
US9456017B2 (en) System and method for a connector being able to adapt to newer features introduced to a messaging provider with only configuration changes
CN107203419A (zh) 应用程序中的模块间调用方法、装置及系统
CN102339234A (zh) 一种协议栈运行装置和方法
CN102591724A (zh) 消息交互方法及装置
WO2016124115A1 (zh) 多账号登录、通讯方法、装置和移动终端
CN111142910B (zh) 一种面向多界面的资源调配处理方法及系统
CN105183674A (zh) Usb虚拟化网络映射方法、装置以及usb集线器
CN113312168A (zh) 页面访问方法与电子设备
CN110740057A (zh) 一种业务部署方法以及区块链平台
CN118394548B (zh) 一种微前端跨应用信息共享方法与微前端架构系统
CN115412329A (zh) 一种用于物联网的信息处理方法及相关装置
US20150220348A1 (en) Computing system initiation
WO2023092316A1 (zh) 一种第三方服务登录方法、装置、终端设备及存储介质
CN104090792A (zh) 一种宽带接入网中逻辑文件的动态加载方法
CN103220235B (zh) 分布式虚拟交换机的管理方法和相关装置及系统
US20220303261A1 (en) Methods and apparatus for lightweight machine to machine communication
CN109962788B (zh) 多控制器调度方法、装置和系统及计算机可读存储介质
CN108605222A (zh) 用于在电信网络与电信终端设备之间传输参数数据且用于在电信终端设备上激活和/或改变和/或停用通过参数数据限定或表示的通信配置文件的方法、用于传输参数数据的系统、用于传输参数数据的电信终端设备、计算机程序以及计算机程序产品
CN106487849A (zh) 一种基于重定向的信息传输方法及装置
CN119095023A (zh) eSIM的配置文件下载方法、系统、电子设备及存储介质

Legal Events

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

Ref document number: 16746110

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017541013

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16746110

Country of ref document: EP

Kind code of ref document: A1