TWI487340B - Method and device for realizing stand-alone software communication - Google Patents

Method and device for realizing stand-alone software communication Download PDF

Info

Publication number
TWI487340B
TWI487340B TW099113499A TW99113499A TWI487340B TW I487340 B TWI487340 B TW I487340B TW 099113499 A TW099113499 A TW 099113499A TW 99113499 A TW99113499 A TW 99113499A TW I487340 B TWI487340 B TW I487340B
Authority
TW
Taiwan
Prior art keywords
user equipment
single
software
a1
communication
Prior art date
Application number
TW099113499A
Other languages
Chinese (zh)
Other versions
TW201138394A (en
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 TW099113499A priority Critical patent/TWI487340B/en
Publication of TW201138394A publication Critical patent/TW201138394A/en
Application granted granted Critical
Publication of TWI487340B publication Critical patent/TWI487340B/en

Links

Description

Method and device for realizing single-machine software communication

The present application belongs to the field of computer application technologies, and in particular, to a method and device for implementing single-machine software communication.

With the development of network technology, users' demand for various application software is not limited to single-machine functions. More and more users want software to have certain network functions, so that the basic functions of software-based and remote users can be used. Interact.

The increase in user demand for software features has also increased the difficulty of software development. Especially for software that was originally only for stand-alone software, to implement network functions, the corresponding communication function module must be added to the software. Compared with the implementation of the stand-alone function, the implementation of the network function puts higher requirements on the developer and the development environment. If you want to implement more complex network functions, you may need to set up a server. Therefore, implementing network functions on a single-machine software will significantly increase the development difficulty and development cost, which also limits the developers to some extent. In addition, because different developers use different network environments during development or testing, users will inevitably encounter compatibility problems when actually using the software network function, and often require users to differentize for different software. The network connection configuration brings operational troubles.

The embodiment of the present application provides a method and a device for implementing a single-machine software communication, which solves the problems of high difficulty, high cost, and poor compatibility in implementing a network function in a single-machine software. The technical solution is as follows: The method for implementing the single-machine software communication includes: establishing, by the first user equipment, an instant communication connection with the second user equipment; the single-machine software A1 in the first user equipment uses the instant communication connection to communicate with the single-machine software A2 in the second user equipment The first user equipment and the second user equipment are mutually peer devices, and the instant communication connection between the first user equipment and the second user equipment is performed by the instant communication user terminal B1 and the first user equipment. The instant messaging client B2 in the second user equipment is established; the single-machine software A1 in the first user equipment and the single-machine software A2 in the second user equipment are the same software.

The embodiment of the present application further provides an apparatus for implementing single-machine software communication, which is located in a local user equipment and a peer user equipment, and the apparatus includes a connection establishing unit, a request sending unit, a request receiving unit, and a single-machine software starting unit; the connection establishing unit, For establishing an instant communication connection between the local user equipment and the peer user equipment; on the local user equipment side: the single-machine software startup unit is used to start the local single-machine software A1; the request sending unit is configured to send to the opposite user equipment The single-machine software communication request, the single-machine software communication request carries the identifier of the single-machine software A1; on the opposite-end user equipment side: the request receiving unit is configured to receive the single-machine software communication request; the single-machine software startup unit is configured to The single-machine software identifier carried in the single-machine software communication request starts the local single-machine software A2; the single-machine software A1 communicates with the stand-alone software A2 using the instant communication connection established by the connection establishment unit.

In the technical solution provided by the embodiment of the present application, the single-machine software communicates using the network connection established by the instant communication system, so that the single-machine software itself does not need the communication function module, thereby effectively reducing the difficulty in realizing the network function in the single-machine software. And development costs. In addition, since each single-machine software uniformly uses the network connection established by the instant messaging system, normal communication of a plurality of single-machine software can be realized in a one-time configuration, which simplifies user operations.

First, a method for implementing single-machine software communication provided by the embodiment of the present application is described, including: establishing, by the first user equipment, an instant communication connection with the second user equipment; the single-machine software A1 in the first user equipment uses the instant communication connection, and The single-user software A2 in the second user equipment communicates with each other; wherein the first user equipment and the second user equipment are mutually peer devices, and the instant communication connection between the first user equipment and the second user equipment is performed by the first The instant messaging client B1 in the user equipment is established with the instant messaging client B2 in the second user equipment; the single-machine software A1 in the first user equipment and the single-machine software A2 in the second user equipment are the same software.

In the above technical solution, the single-machine software communicates using the network connection established by the instant communication system, so that the single-machine software itself is not required to have the communication function module. From the developer's point of view, you can focus on the implementation of the basic functions of the stand-alone software. For the implementation of the network function, you only need to leave an interface that can interact with the local instant messaging client, even a relatively complex network. The road function can also be realized by the instant communication server, which effectively reduces the development difficulty and development cost of implementing the network function in the single machine software.

On the other hand, in the prior art, because different developers use different network environments during development or testing, users often encounter compatibility problems when actually using the software network function. Applying the technical solution provided by the present application, multiple single-machine software can uniformly use the network connection established by the same instant messaging system, so communication configuration is not required for each specific single-machine software, which simplifies user operations.

On the other hand, in the prior art, due to limitations in development and development costs, many network functions implemented in a stand-alone software do not take into account communication security, fault handling, etc., and instant messaging systems generally It has a relatively complete communication security and fault handling mechanism. Therefore, by applying the technical solution of the present application, the reliability of the single-machine software communication can be effectively improved.

The technical solutions in the embodiments of the present application are clearly and completely described in the following, in which the technical solutions in the embodiments of the present application are clearly and completely described. The embodiments are only a part of the embodiments of the present application, and not all of them. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope shall fall within the scope of the application.

Embodiment 1:

In the embodiment of the present application, the communication entity involved includes the first user equipment and the second user equipment. In the communication process, the first user equipment and the second user equipment are mutually peer devices. There are two parts involved on the first user equipment side: a single-machine software A1 and an instant communication user B1; on the second user equipment side, two parts are also involved: a stand-alone software A2 and an instant communication user B2; wherein, B1 and B2 Belong to the same instant messaging system, A1 and A2 are the same software. A1 and A2 communicate via an instant messaging connection established by B1 and B2. FIG. 1 is a flowchart of a method for implementing the embodiment, including the following steps: S101, A1 sends a communication request to B1; in the embodiment of the present application, although the stand-alone software still has a communication module logically, the module It does not actually interact directly with the network side. When the stand-alone software has communication requirements, it will first send a communication request to the instant messaging client B1 in the local user equipment.

In order to ensure that the stand-alone software can correctly communicate using the instant messaging connection, the stand-alone software and the instant messaging software should have a certain correspondence. For the instant messaging client, in addition to the basic instant messaging function, it is also necessary to pre-define a dedicated local communication interface to implement internal message interaction between the instant communication software trip and the stand-alone software trip. When implementing the network function of the stand-alone software, the local communication interface between the stand-alone software and the instant messaging software can be implemented only according to the local communication interface defined by the instant messaging software, and no interaction with the network is involved. Understandably, a single-machine software can choose to use a variety of instant messaging software to communicate, and an instant messaging software can also support communication of multiple stand-alone software at the same time.

Assume that stand-alone software A1 is a game software, local users want to play games with other users through the network, select the corresponding network function, such as requesting online games with someone, or looking for online opponents, etc., A1 will be to local user devices. The corresponding instant messaging client B1 sends a communication request. Of course, the foregoing situation is that the preset B1 is currently running in the local user equipment. In a specific implementation, before sending the communication request, the A1 may first detect whether the corresponding instant communication client is currently running in the local user equipment. If not, the corresponding instant messaging client can be automatically started, or a prompt message can be sent to the user to prompt the user to manually start the corresponding instant messaging client.

S102: After receiving the communication request sent by A1, B1 verifies A1. For the purpose of secure communication, after receiving the communication request sent by A1, B1 may further confirm whether A1 is allowed to communicate using the instant communication connection. The verification may include multiple implementation manners, for example, prompting the user for relevant information and requesting the user to further confirm; or, B1 requires the corresponding verification information provided by A1 to determine the identity of the current user, and the verification information may also be used with the instant chat account. A consistent username or password. A1 may also directly carry the corresponding verification information in the communication request sent in S101.

It can be understood that this step can also be used for the inspection of compatibility. In S101, when A1 sends a communication request to B1, it actually determines that the network function can be implemented through B1. In this step, B1 can further confirm whether to support communication of A1, specifically by checking the version number, Send specific test data and other means to achieve. This step is combined with S101, which is equivalent to realizing the bidirectional compatibility check of A1 and B1, thereby ensuring that A1 can correctly communicate using the instant communication connection established by B1.

S103, B1 sends a communication request response to A1; this step is an optional step. If A1 passes the verification of B1, B1 may notify A1 that the verification is successful in the response message, and continue to perform the subsequent steps. If A1 does not pass the verification of B1, B1 will reject the communication request of A1, and send a response message to notify A1. In the response message, the reason value of the rejection may be further carried, for example, the user identity is illegal, the software version is incompatible, and the like. .

S104: The B1 detects whether an instant communication connection exists with the peer user equipment.

After A1 is verified, B1 can allow A1 to communicate using an instant messaging connection, but in the specific implementation, it is divided into the following cases:

1) The local user wishes to communicate with the specified user, and there is currently an instant communication connection between the local user device and the designated user device (eg, both parties are chatting). In this case, A1 can directly communicate with the peer user equipment using the current instant messaging connection. Correspondingly, the same stand-alone software should also be started in the peer user equipment, hereinafter referred to as A2. That is, A1 and A2 communicate with each other through the local instant messaging client B1 and the peer instant messaging client (hereinafter referred to as B2) even if the communication connection is established. It can be understood that, on the peer user equipment side, A2 and B2 can also perform a verification operation similar to S102, which will not be described in detail herein.

2) The local user wishes to communicate with the specified user, and there is currently no instant communication connection between the local user device and the designated user device.

3) The local user wants to randomly search for a communication object, for example, randomly searching for an online opponent when playing a game. In this case, the randomly sought communication object and the local user equipment currently have no instant communication connection.

In actual implementation, A1 needs to provide B1 with the identity of the communication object device, which may be an identifier indicating a specific communication object (for example, an instant messaging account), or an identifier indicating that the communication object is randomly searched for. The identifier can also be directly carried in the communication request sent by A1 to B1. B1 detects the current instant messaging connection status based on the identity, and if it is case 1), allows A1 and A2 to communicate using the current instant messaging connection, and if it is case 2) or 3), then proceeds to S105.

S105. The B1 establishes an instant communication connection with the peer device.

For the cases 2) and 3) in S104, B1 needs to establish an instant communication connection with the corresponding peer device according to the identifier of the communication object device provided by A1 for use by A1.

The instant messaging system is mainly based on two protocols: TCP (Transfer Control Protocol) and UDP (User Datagram Protocol). Among them, the characteristic of UDP is that it does not need to establish a connection, and the network overhead is small, but the data transmission reliability is poor. TCP is a connection-oriented protocol with high transmission reliability. In the solution provided by the present application, the communication of the stand-alone software has higher requirements on data reliability, so it is necessary to establish a reliable TCP connection between the instant communication users.

B1 first sends the identity of the peer device to the instant messaging server, and the instant messaging server will return corresponding information to B1 according to the specific type of the identifier:

Corresponding to the above situation 2), the instant messaging server will directly return to B1 the information such as the IP address and TCP nickname of the user equipment corresponding to the identifier; here, it should be noted that the peer user equipment must currently be in the instant messaging system. Online status, otherwise an instant communication connection cannot be achieved.

Corresponding to the above situation 3), the instant messaging server will randomly return to B1 the IP address, TCP nickname and other information of the user equipment corresponding to an online user, or return relevant information of multiple online user equipments to B1, and then Local users choose their own communication objects.

B1 starts to establish an instant communication connection with B2 of the peer user equipment according to the information about the peer user equipment returned by the server.

S106, B1 returns a connection establishment success response message to A1.

After the connection is successfully established, B1 returns a connection establishment success response message to A1, which is an optional step. Subsequent A1 and A2 can communicate using the instant messaging connection established by B1 and B2. In this embodiment, the communication may be performed in a peer-to-peer manner, or the communication may be performed through an instant messaging server, which is not limited in this embodiment.

Embodiment 2:

The method provided in the first embodiment is the entire communication process initiated by the stand-alone software. In practical applications, a more common situation is that the user is currently using the instant messaging system for chatting (ie, B1 and B2 have been established). In the instant communication connection, the local user wants to run a certain stand-alone software and interact with the peer user, that is, the initiator of the communication process is the instant communication user B1 of the local end. For this specific case, this embodiment provides another A method for implementing single-machine software communication, the flow chart is as shown in FIG. 2, and includes the following steps: S201, B1 and B2 establish an instant communication connection; in this implementation, before starting the single-machine software, the local user equipment has been established with the peer user equipment. An instant messaging connection.

S202, B1 starts the stand-alone software A1 in the local user equipment; when the local user wants to run a certain stand-alone software A1, A1 is directly started by B1. Equivalent to the local instant messaging client directly allows A1 to use instant messaging connection, so the verification and other steps can be omitted.

In the prior art, there are two ways to start the software in the instant messaging client: 1) separately opening a window independent of the chat window, running the software in the independent window; 2) expanding the chat window and embedding the software in the chat window run. Among them, the disadvantage of the mode 1) is that the software has poor combination with the chat window, lacks integrity, and cannot implement the soft-attached chat window movement, so that the user often cannot associate the software function with the chat window. The shortcoming of mode 2) is that the interface size cannot be changed at any time during the use of the software, and the flexibility is poor.

In response to the above problem, the embodiment provides a method for starting the software in the instant messaging client: B1 creates an extension window of the chat window based on the current instant messaging chat window, and starts A1 in the extended window, so that The benefits are as follows:

1) During the operation of A1, when it is necessary to change its size due to the function interface switching, a request can be made to the extended window managed by B1. After receiving the size change request from A1, the extended window adjusts its size to adapt to the functional interface change of A1. The adaptive size change of the extended window is unlimited and frequency, and can be performed at any time according to the request of A1.

2) In the same extended window, multiple softwares can be loaded at the same time, which can include software with network function requirements, and can also include ordinary stand-alone software. Each software works in parallel and does not affect each other. For example, if there is already an A1 running in the extended window, if the user starts another software A11 based on the extended window, A11 can run concurrently with A1, and the user can switch the functions of the two softwares through the switching device on the extended window. The operation interface, during the switching process, the extended window can always be adjusted to adapt to the software interface size change currently being used by the user.

It can be understood that the instant messaging client can also activate a plurality of single-machine software in the local user equipment in different extended windows, which is not limited in this embodiment.

3) The extended window can be moved as a whole with the chat window or independently. In the case where the software is already running in the extended window, if the user drags the chat window position, the extended window can be attached to change the position along with the chat window, and the relative position between the extended window and the chat window does not change. If the user drags the extended window away from the chat window, then the change of the position of the chat window and the change of the extended window position are independent of each other and do not affect each other. Users can drag the extended window to any position on the screen.

S203: B1 sends a single-machine software communication request to B2.

After B1 starts A1, it sends a single-machine software communication request to B2 of the peer user equipment. In the request, it needs to carry the identifier of the single-machine software A1, so that B2 can start the same software as A1.

This step can be triggered by the user or automatically by B1. In the case of automatic execution of B1, since the software activated by B1 may be a software with network function requirements, or may be an ordinary single-machine software, B1 may first detect whether A1 requires users to interact through the network. If yes, send a separate software communication request to B2.

S204. The B2 receives the single-machine software communication request, and starts the single-machine software A2 in the local user equipment according to the single-machine software identifier carried in the single-machine software communication request. The operation of starting the A2 may be performed automatically by the B2 or by the B2 direction. The user sends a prompt message, and the user confirms whether to start. B2 can start A2 in the same way as B1 starts A1.

In this step, if B2 does not detect the corresponding software in the machine, the user may be prompted to download, and of course, the software communication request sent by B1 may be rejected.

S205. After B2 starts A2, it sends a single-machine software communication request response to B1.

At this point, A1 and A2 can communicate using the instant messaging connection established by B1 and B2.

In this embodiment, the actual communication process is initiated by the instant communication user terminal, and the verification process can be omitted without losing communication reliability. And some local interactive flow step processes. On the other hand, the embodiment also provides a method for starting the software in the extended window to achieve a better user experience.

Embodiment 3:

Corresponding to the above method embodiment 1, the present application further provides a device for implementing single-machine software communication, which is located in a local user equipment and a peer user equipment. Referring to FIG. 3, the apparatus includes: a connection establishing unit 310, configured to establish An instant communication connection established between the local user equipment and the peer user equipment; the request receiving unit 320 is configured to receive a communication request sent by the single-machine software A1 in the local user equipment; and the verification communication unit 330 is configured to verify the A1, if the verification is passed The A1 and the single-machine software A2 in the peer user equipment are allowed to communicate using the instant communication connection; wherein the single-machine software A1 and the single-machine software A2 are the same software.

Embodiment 4:

Corresponding to the foregoing method embodiment 2, the present application further provides another apparatus for implementing single-machine software communication, which is located in a local user equipment and a peer user equipment. Referring to FIG. 4, the apparatus includes: a connection establishing unit 410, and a stand-alone software. The initiating unit 420, the request sending unit 430, and the request receiving unit 440; the connection establishing unit 410 is configured to establish an instant communication connection between the local user equipment and the peer user equipment; on the local user equipment side: the single-machine software starting unit 420, The local device software A1 is activated. The request sending unit 430 is configured to send a single-machine software communication request to the peer user equipment. The single-machine software communication request carries the identifier of the single-machine software A1. On the opposite user equipment side: The request receiving unit 440 is configured to receive the single-machine software communication request. The single-machine software startup unit 420 is configured to start the local single-machine software A2 according to the single-machine software identifier carried in the single-machine software communication request; the single-machine software A1 and the stand-alone software A2 communicates using the instant messaging connection established by the connection establishment unit.

The single-machine software starting unit 420 may specifically include: an extended window creating sub-unit for creating an extended window of the instant messaging chat window; and activating sub-unit for starting the stand-alone software in the extended window.

For the convenience of description, the above devices are described separately by function into various units. Of course, the functions of each unit can be implemented in the same software or software and/or hardware in the implementation of the present application.

As can be seen from the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of a software plus a necessary universal hardware platform. Based on such understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in the form of a software product, which can be stored in a storage medium such as a ROM/RAM, a disk, A disc or the like includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application or portions of the embodiments.

The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment. The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

This application can be used in a variety of general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, small computers, large Computer, decentralized computing environment including any of the above systems or devices, and so on.

The application can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, a program module includes routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. The present application can also be practiced in a distributed computing environment where tasks are performed by remote processing devices that are connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

The above description is only a specific embodiment of the present application, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present application. It should be considered as the scope of protection of this application.

310. . . Connection establishment unit

320. . . Request receiving unit

330. . . Verify communication unit

410. . . Connection establishment unit

420. . . Stand-alone software starter unit

430. . . Request sending unit

440. . . Request receiving unit

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only Some of the embodiments described in the application can be used to obtain other drawings based on these drawings without departing from the prior art.

1 is a flowchart of a method for implementing single-machine software communication according to Embodiment 1 of the present application;

2 is a flowchart of a method for implementing single-machine software communication according to Embodiment 2 of the present application;

3 is a schematic structural diagram of a single-machine software communication device according to Embodiment 3 of the present application;

FIG. 4 is a schematic structural diagram of a device for implementing a single-machine software communication according to Embodiment 4 of the present application.

Claims (10)

  1. A method for implementing single-machine software communication, comprising: establishing, by the instant communication user B1 in the first user equipment and the instant communication user B2 in the second user equipment, the first user equipment and the second user equipment An instant communication connection between the first user equipment and the second user equipment as a peer device; implementing a two-way connection between the single-machine software A1 in the first user equipment and the instant communication user B1 in the first user equipment a compatibility check, the determining, by determining the identity of the current user, whether the single-machine software A1 in the first user equipment is verified to use the instant communication client B1 in the first user equipment, And determining whether the single-machine software A1 in the first user equipment is compatible with the instant communication user B1 in the first user equipment, so as to correctly use the instant communication established by the instant communication user B1 in the first user equipment. Connecting to communicate with the stand-alone software A2 in the second user equipment; allowing the stand-alone software A1 in the first user equipment to use the instant communication connection, and The single-machine software A2 in the second user equipment communicates with the single-machine software A1 in the first user equipment, and the single-machine software A2 in the second user equipment is the same software.
  2. According to the method of claim 1, the method further comprises: B1 receiving a communication request sent by A1.
  3. The method of claim 2, wherein the communication request carries an identifier of the second user equipment, wherein A1 is allowed to be used. The instant messaging connection communicates with the A2, including: detecting, according to the identifier of the second user equipment, whether there is an instant communication connection between B1 and B2; if yes, allowing A1 and A2 to communicate using the current instant messaging connection; No, B1 establishes an instant communication connection with B2 according to the identity of the second user equipment, and allows A1 and A2 to communicate using the established instant messaging connection.
  4. The method of claim 1, wherein A1 is allowed to communicate with A2 using the instant messaging connection, including: B1 establishes an instant communication connection with B2; B1 activates the stand-alone software A1 in the local user equipment; and sends to the B2 The single-machine software communication request, the single-machine software communication request carries the identifier of the single-machine software A1; the B2 receives the single-machine software communication request; and starts the single-machine software A2 in the local user equipment according to the single-machine software identifier carried in the single-machine software communication request And A1 and A2 communicate using the instant messaging connection established by B1 and B2.
  5. The method of claim 4, wherein the instant messaging client activates the stand-alone software in the local user equipment, and the specific implementation is: the instant messaging user creates an extended window of the instant messaging chat window, and the extended window is displayed in the extended window. Start the stand-alone software.
  6. The method of claim 5, wherein the instant messaging client starts the stand-alone software in the extended window, comprising: the instant messaging client launching the plurality of stand-alone software in the local user device in the same extended window; Or the instant messaging client starts multiple stand-alone software in the local user equipment in different extended windows.
  7. According to the method of claim 4, 5 or 6, wherein before B1 sends a single-machine software communication request to B2, the method further includes: B1 detecting whether A1 needs to be used by the user through network interaction, and if yes, sending to B2 Single machine software communication request.
  8. An apparatus for implementing a single-machine software communication, which is located in a local user equipment and a peer user equipment, wherein the apparatus comprises: a connection establishing unit, configured to establish an instant communication connection established between the local user equipment and the opposite user equipment; requesting to receive a unit, configured to receive a communication request sent by the single-machine software A1 in the local user equipment; and a verification communication unit, configured to implement a two-way connection compatibility check between the stand-alone software A1 and the instant communication user B1 in the local user equipment The two-way connection compatibility check includes determining whether the A1 is verified to use B1 by determining the identity of the current user, and determining whether A1 is compatible with B1, so as to correctly use the instant communication connection established by B1 to the opposite end. The single-machine software A2 in the user equipment communicates; wherein the single-machine software A1 and the stand-alone software A2 are the same software.
  9. A device for implementing single-machine software communication, located in a local user equipment And the peer user equipment, wherein the apparatus comprises a connection establishing unit, a verification communication unit, a request sending unit, a request receiving unit, and a stand-alone software starting unit; the connection establishing unit is configured to establish a local user equipment and a peer user An instant communication connection of the device; a verification communication unit, configured to implement a two-way connection compatibility check between the stand-alone software A1 and the instant communication user B1 in the local user equipment, the two-way connection compatibility check includes: The user's identity to determine whether A1 is verified to use B1, and to determine whether A1 is compatible with B1, to correctly use the instant messaging connection established by B1 to communicate with the stand-alone software A2 in the peer user equipment; The device side: the single-machine software startup unit is configured to start the local single-machine software A1; the request sending unit is configured to send a single-machine software communication request to the peer user equipment, where the single-machine software communication request carries the identifier of the single-machine software A1 On the peer user equipment side: the request receiving unit is configured to receive the single-machine software communication request The stand-alone software starting unit, based on the stand-alone software for communication request identifier carried in the stand-alone software, start a local stand-alone software A2; A1 is connected to the stand-alone software used to communicate with a standalone software A2 the connection establishment unit establishes the IM.
  10. The device of claim 9, wherein the The single-machine software startup unit includes: an extended window creation sub-unit for creating an extended window of the instant messaging chat window; and a startup sub-unit for starting the stand-alone software in the extended window.
TW099113499A 2010-04-28 2010-04-28 Method and device for realizing stand-alone software communication TWI487340B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
TW099113499A TWI487340B (en) 2010-04-28 2010-04-28 Method and device for realizing stand-alone software communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
TW099113499A TWI487340B (en) 2010-04-28 2010-04-28 Method and device for realizing stand-alone software communication

Publications (2)

Publication Number Publication Date
TW201138394A TW201138394A (en) 2011-11-01
TWI487340B true TWI487340B (en) 2015-06-01

Family

ID=46759842

Family Applications (1)

Application Number Title Priority Date Filing Date
TW099113499A TWI487340B (en) 2010-04-28 2010-04-28 Method and device for realizing stand-alone software communication

Country Status (1)

Country Link
TW (1) TWI487340B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050086309A1 (en) * 2003-10-06 2005-04-21 Galli Marcio Dos S. System and method for seamlessly bringing external services into instant messaging session
US20060036692A1 (en) * 2004-08-10 2006-02-16 Microsoft Corporation Method and system of integrating instant messaging with other computer programs
TW200838227A (en) * 2007-03-02 2008-09-16 Asustek Comp Inc Method and system for monitoring and controlling voice instant messaging

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050086309A1 (en) * 2003-10-06 2005-04-21 Galli Marcio Dos S. System and method for seamlessly bringing external services into instant messaging session
US20060036692A1 (en) * 2004-08-10 2006-02-16 Microsoft Corporation Method and system of integrating instant messaging with other computer programs
TW200838227A (en) * 2007-03-02 2008-09-16 Asustek Comp Inc Method and system for monitoring and controlling voice instant messaging

Also Published As

Publication number Publication date
TW201138394A (en) 2011-11-01

Similar Documents

Publication Publication Date Title
US8171145B2 (en) System and method for two way communication and controlling content in a game
US8910239B2 (en) Providing virtualized private network tunnels
US8914845B2 (en) Providing virtualized private network tunnels
CA2771785C (en) A system and method for pervasive computing
EP2056195A1 (en) Implementation method for updating the terminals in batches
JP2014532208A (en) Method and computing system for proximity services
EP2428022B1 (en) Method and apparatus for proximity based pairing of mobile devices
CN103718161B (en) Web Application Architecture
EP2815320B1 (en) Remote debugging as a service
US9231904B2 (en) Deploying and managing networked devices
US9027112B2 (en) Mobile device management
US20170272316A1 (en) Managing network connected devices
CN104969231A (en) Security challenge assisted password proxy
CN102802071A (en) Intelligent television, mobile terminal, multi-screen interaction system and wireless communication method
EP2963933A1 (en) Remote control processing method, apparatus and system
CN103891246B (en) Page real-time communication apparatus and method for transferring a call
CN102710534B (en) Application of a cross-network communication method and apparatus
US20100197293A1 (en) Remote computer access authentication using a mobile device
CN103400067B (en) Rights management method, system and server
JP5485382B2 (en) Method and system for payment through a mobile device
KR101951133B1 (en) Video studio creating method and service device
US20160112262A1 (en) Installation and configuration of connected devices
CN103118032B (en) A terminal login account synchronization method, the terminal server
TWI496008B (en) Link equipment
CN103763327A (en) Account number logging-in method and system