CN107172060B - Login method of client container - Google Patents
Login method of client container Download PDFInfo
- Publication number
- CN107172060B CN107172060B CN201710419899.4A CN201710419899A CN107172060B CN 107172060 B CN107172060 B CN 107172060B CN 201710419899 A CN201710419899 A CN 201710419899A CN 107172060 B CN107172060 B CN 107172060B
- Authority
- CN
- China
- Prior art keywords
- client
- connection
- starting
- login
- executing
- 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.)
- Expired - Fee Related
Links
Images
Classifications
-
- 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/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- 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/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- 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/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a login method of a client container, which comprises the following steps: s1, copying a dynamic library file in the operating environment library pointed by the source directory into the target directory according to the source directory and the target directory in the configuration file, and executing the instantiation method of the starting class of the current client; s2, displaying the starting animation after the instantiation of the starting class is completed; s3, executing an instantiation method and an initialization method for updating the detection object, starting a socket connection service of the current client to establish socket connection with the server, and starting a client disconnection reconnection mechanism; s4, after the startup class is started, acquiring a user name and a password from a login interface to log in; and S5, after login is successful, obtaining the user information from the server and storing the user information in the cache of the current client. The invention has the beneficial effects that: the technical scheme ensures the communication safety, and realizes a whole set of realization method of intelligent upgrade of the client, cache of the client, a network reconnection mechanism of the client and user authentication.
Description
Technical Field
The invention relates to the field of Internet, in particular to a login method of a client container.
Background
With the rapid development of internet technology, more and more application clients appear in the lives of people, and users can obtain services from the internet by logging in the application clients. However, the existing login method cannot guarantee communication security, and also does not provide functions such as client upgrade, client cache, connection service from the client to the server, a client network reconnection mechanism and the like.
Disclosure of Invention
The invention provides a login method of a client container, which solves the technical problem in the prior art.
The technical scheme for solving the technical problems is as follows: a login method of a client container comprises the following steps:
s1, copying a dynamic library file in the operating environment library pointed by the source directory into the target directory according to the source directory and the target directory in the configuration file, and executing the instantiation method of the starting class of the current client by taking a locally stored server address list and an encrypted communication file as parameters;
s2, displaying the starting animation after the instantiation of the starting class is completed;
s3, executing an instantiation method and an initialization method for updating the detection object, judging whether the version of the client needs to be updated, if so, closing the starting animation, quitting the execution, if not, executing the initialization method and the starting method of the starting class, simultaneously starting the socket connection service of the current client to establish socket connection with the server, and starting a disconnection reconnection mechanism of the client;
s4, after the startup class is started, displaying a login interface, and acquiring a user name and a password from the login interface to log in;
and S5, after login is successful, obtaining user information from the server and storing the user information in the cache of the current client.
The invention has the beneficial effects that: the technical scheme provides a UI container implementation method based on a client architecture, which ensures communication safety, and realizes a whole set of implementation methods of client intelligent upgrade, client cache, client-to-server connection service, a client network reconnection mechanism and user authentication. The starting speed of the client is improved, the access mechanism of the client is optimized, and a new thought is provided for the design of the client.
On the basis of the technical scheme, the invention can be further improved as follows.
Preferably, step S3 includes:
s31, executing the instantiation method of the update detection object, and acquiring the root directory, the update configuration file and the version information of the current application program;
s32, executing the initialization method of the update detection object, if the root directory, the update configuration file and the version information are not empty, connecting a version update management server to obtain the latest version information;
s33, if the version information is different from the latest version information, generating and pushing a message for inquiring whether the user needs to update the client version, judging whether the client version needs to be updated according to the feedback information, if so, closing the starting animation, updating the value of the registry base item and the local program file, otherwise, executing the initialization method and the starting method of the starting class.
Preferably, in step S3, the executing the initialization method and the startup method for the startup class specifically includes:
and executing an initialization method of the base class of the starting class, acquiring the server address list, loading all local audio files, and executing an instantiation method and a starting method of the base class by taking the server address list as a parameter.
Preferably, the method for executing the initialization of the base class specifically includes:
generating a new log file, the log file comprising: the method comprises the steps of executing an initialization method of an interface manager class by taking a client type as a parameter, setting the client type as the client type of the interface manager, creating a window according to the client type of the interface manager, and setting the title, the minimum width and the minimum height of the window.
Preferably, the method for executing the instantiation of the base class specifically includes:
and taking the server address list, the encrypted communication file and a locally stored interface display mode as parameters, executing the instantiation method of the base class, adding a base class object obtained by instantiation into a client cache object list, processing the server name in the server address list, loading the encrypted communication file to obtain an encryption key, setting the encryption key as the encryption key of the current application program, starting the interface manager, creating a resource manager, and creating and initializing a thread pool.
Preferably, the method for executing the start of the base class specifically includes:
storing a client object in the client cache object list, registering an idle overtime monitoring thread, setting a client socket connection monitor, forcibly interrupting a session event and a client authorization limit event by a registration server, subscribing a popup event and a notification event, setting a socket connection monitor, acquiring a connection attribute value list, and creating a socket connection service according to the connection attribute value list, a socket service type, the server address list and a message processor.
Preferably, step S4 specifically includes:
after the starting class is started, acquiring the starting state of the socket connection service, issuing an event that a client tries to log in, displaying a login interface, judging whether the current connection state is the connected state if the socket connection service is in the started state, trying to establish socket connection with the server if the current connection state is the unconnected state, displaying second error prompt information on the login interface if the connection is overtime, issuing a login ending event, and executing the login method of the base class if the connection state is the connected state.
Preferably, the method for executing the login of the base class specifically includes:
obtaining a user name and a password from the login interface, displaying a login progress control bar, sending a connection message including a connection ID, the client type, user encryption information, a client IP address, an MAC address, a current client version, a domain name, a port and a registration parameter of a connection server, and whether to kill login of a session to the server, if the login is successful, obtaining a login message result, storing the message result in a context session object in a cache of the client, and if the login is failed, displaying third error prompt information on the login interface.
Preferably, in step S5, the method for starting the client disconnection reconnection mechanism specifically includes:
a1, taking the base class as a monitor for monitoring socket connection establishment events and socket connection disconnection events;
a2, when the socket connection disconnection event is monitored, issuing a network disconnection event, setting the connection object of the client application program object and the connection object of the client request repeater to be null when the connection is disconnected, setting the connection flag bit to be false, and starting a reconnection thread if the disconnection reconnection is set to be true in the configuration file;
a3, when the socket connection establishment event is monitored, setting the connection object of the client application program object and the connection object of the client request repeater as new socket connection objects, setting the connection flag bit as true, stopping the network disconnection timer, and issuing a network connection success event.
Preferably, in step a2, the method for starting the reconnecting thread specifically includes:
judging whether the connection flag bit is true or false, if the connection flag bit is false, the reconnection thread is in a waiting state, if the connection flag bit is true, reconnection is carried out at preset time intervals within preset reconnection time, registration reconnection is carried out by taking the connection ID, the client type, the domain name and the port number of the connection server and the session context object and the registration parameters as parameters, data are synchronized with the server, and a client connection success event is issued.
Drawings
Fig. 1 is a schematic flowchart of a login method for a client container according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating a login method of a client container according to another embodiment of the present invention;
fig. 3 is a flowchart illustrating a login method of a client container according to another embodiment of the present invention.
Detailed Description
The principles and features of this invention are described below in conjunction with the following drawings, which are set forth by way of illustration only and are not intended to limit the scope of the invention.
As shown in fig. 1, a login method for a client container includes:
s1, copying a dynamic library file in the operating environment library pointed by the source directory into the target directory according to the source directory and the target directory in the configuration file, and executing the instantiation method of the starting class of the current client by taking the locally stored server address list and the encrypted communication file as parameters;
s2, displaying the starting animation after the instantiation of the starting class is completed;
s3, executing an instantiation method and an initialization method for updating the detection object, judging whether the version of the client needs to be updated, if so, closing the starting animation, quitting the execution, if not, executing the initialization method and the starting method of the starting class, simultaneously starting the socket connection service of the current client to establish socket connection with the server, and starting a disconnection reconnection mechanism of the client;
s4, after the startup class is started, displaying a login interface, and acquiring a user name and a password from the login interface to log in;
and S5, after login is successful, obtaining the user information from the server and storing the user information in the cache of the current client.
Setting a source directory and a target directory in the configuration file, wherein the source directory points to a dynamic library file in the runtime environment library, such as a dll file, copying the dll file into the target directory, and instantiating a client starting class. And after the start class is instantiated, displaying a start animation of the client to prompt a user that the client is starting. Before starting, whether the current client version is the latest version or not needs to be judged, if not, a user is prompted to update, if the user selects to update, the user directly quits from starting to update the client version, if the user selects not to update, the starting is continued, the starting class is started, meanwhile, the client socket connection service is started, the socket connection is established with the server, and the client disconnection reconnection mechanism is started.
Specifically, as shown in fig. 2, step S3 includes:
s31, executing the instantiation method of the update detection object, and acquiring the root directory, the update configuration file and the version information of the current application program;
s32, executing an initialization method for updating the detection object, if the root directory, the update configuration file and the version information are not empty, connecting the version update management server to obtain the latest version information;
and S33, if the version information is different from the latest version information, generating and pushing a message for inquiring whether the user needs to update the client version, judging whether the client version needs to be updated according to the feedback information, if so, closing the starting animation, updating the value of the base item of the registry and the local program file, and otherwise, executing the initialization method and the starting method of the starting class.
Specifically, an update detection object is instantiated, a root directory, an update configuration file and version information of a current application program are obtained, if the root directory, the update configuration file and the version information are not empty, whether the current version is the latest version is judged, if not, a dialog box is popped up to inquire whether a user needs to update, if the user clicks a 'yes' button, a starting animation is closed, updating is carried out, and if the user clicks a 'no' button, a starting class is continuously started. Of course, if any one of the three is empty, an exception is thrown, and an error prompt box is popped up.
Specifically, in step S3, the executing of the initialization method and the starting method of the starting class specifically includes:
the method comprises the steps of executing an initialization method of a base class of a starting class, obtaining a server address list, loading all local audio files, and executing an instantiation method and a starting method of the base class by taking the server address list as a parameter.
Specifically, the method for initializing the execution base class specifically includes:
generating a new log file, the log file comprising: the method comprises the steps of executing an initialization method of an interface manager class by taking a client type as a parameter, setting the client type as the client type of the interface manager, creating a window according to the client type of the interface manager, and setting the title, the minimum width and the minimum height of the window.
Specifically, the instantiation method of the execution base class specifically includes:
the method comprises the steps of taking a server address list, an encrypted communication file and a locally stored interface display mode as parameters, executing an instantiation method of a base class, adding a base class object obtained by instantiation into a client cache object list, processing a server name in the server address list, loading the encrypted communication file to obtain an encryption key, setting the encryption key as the encryption key of a current application program, starting an interface manager, creating a resource manager, and creating and initializing a thread pool.
Specifically, the starting method for executing the base class specifically includes:
storing a client object in a client cache object list, registering an idle overtime monitoring thread, setting a client socket connection monitor, forcibly interrupting a session event and a client authorization limit event by a registration server, subscribing a popup event and a notification event, setting a socket connection monitor, acquiring a connection attribute value list, and creating a socket connection service according to the connection attribute value list, a socket service type, a server address list and a message processor.
Specifically, step S4 specifically includes:
after the start of the start class is finished, acquiring the starting state of the socket connection service, issuing an event that the client tries to log in, displaying a login interface, if the socket connection service is in the starting state, judging whether the current connection state is in the connected state, if the current connection state is in the unconnected state, trying to establish socket connection with the server, if the connection is overtime, displaying second error prompt information on the login interface, issuing a login end event, and if the connection state is in the connected state, executing the login method of the base class.
Specifically, the method for executing the login of the base class specifically includes:
the method comprises the steps of obtaining a user name and a password from a login interface, displaying a login progress control bar, sending a connection message including a connection ID, a client type, user encryption information, a client IP address, an MAC address, a current client version, a domain name, a port and a registration parameter of a connection server, and whether login of a session is killed to the server, obtaining a login message result if the login is successful, storing the message result in a context session object in a cache of the client, and displaying second error prompt information on the login interface if the login is failed.
Specifically, as shown in fig. 3, in step S3, the method for starting the client disconnection reconnection mechanism specifically includes:
a1, taking the base class as a monitor for monitoring socket connection establishment events and socket connection disconnection events;
a2, when a socket connection disconnection event is monitored, issuing a network disconnection event, setting a connection object of a client application program object and a connection object of a client request repeater to be null when the connection is disconnected, setting a connection flag bit to be false, and starting a reconnection thread if disconnection reconnection is set to be true in a configuration file;
a3, when a socket connection establishment event is monitored, setting a connection object of a client application program object and a connection object of a client request repeater as new socket connection objects, setting a connection flag bit as true, stopping a network disconnection timer, and issuing a network connection success event.
It should be understood that true and false of the connection flag bit represent connected and unconnected states, respectively. If the disconnection reconnection is set to be true in the configuration file, namely, as long as the disconnection is monitored, the reconnection thread is directly started.
Specifically, in step a2, the method for starting the reconnecting thread specifically includes:
judging whether the connection flag bit is true or false, if the connection flag bit is false, the reconnection thread is in a waiting state, if the connection flag bit is true, reconnection is carried out at preset time intervals within preset reconnection time, registration reconnection is carried out by taking a connection ID, a client type, a domain name, a port number and a session context object of a connection server and a registration parameter as parameters, data is synchronized with the server, and a client connection success event is issued.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (8)
1. A method for logging on a client container, comprising:
s1, copying a dynamic library file in the operating environment library pointed by the source directory into the target directory according to the source directory and the target directory in the configuration file, and executing the instantiation method of the starting class of the current client by taking a locally stored server address list and an encrypted communication file as parameters;
s2, displaying the starting animation after the instantiation of the starting class is completed;
s3, executing an instantiation method and an initialization method for updating the detection object, judging whether the version of the client needs to be updated, if so, closing the starting animation, quitting the execution, if not, executing the initialization method and the starting method of the starting class, simultaneously starting the socket connection service of the current client to establish socket connection with the server, and starting a disconnection reconnection mechanism of the client;
s4, after the startup class is started, displaying a login interface, and acquiring a user name and a password from the login interface to log in;
s5, after login is successful, obtaining user information from the server and storing the user information in the cache of the current client;
in step S3, the executing of the initialization method and the startup method of the startup class specifically includes:
executing an initialization method of a base class of the starting class, acquiring the server address list, loading all local audio files, and executing an instantiation method and a starting method of the base class by taking the server address list as a parameter;
in step S3, the method for starting the client disconnection reconnection mechanism specifically includes:
a1, taking the base class as a monitor for monitoring socket connection establishment events and socket connection disconnection events;
a2, when the socket connection disconnection event is monitored, issuing a network disconnection event, setting the connection object of the client application program object and the connection object of the client request repeater to be null when the connection is disconnected, setting the connection flag bit to be false, and starting a reconnection thread if the disconnection reconnection is set to be true in the configuration file;
a3, when the socket connection establishment event is monitored, setting the connection object of the client application program object and the connection object of the client request repeater as new socket connection objects, setting the connection flag bit as true, stopping the network disconnection timer, and issuing a network connection success event.
2. The login method for the client container according to claim 1, wherein step S3 comprises:
s31, executing the instantiation method of the update detection object, and acquiring the root directory, the update configuration file and the version information of the current application program;
s32, executing the initialization method of the update detection object, if the root directory, the update configuration file and the version information are not empty, connecting a version update management server to obtain the latest version information;
s33, if the version information is different from the latest version information, generating and pushing a message for inquiring whether the user needs to update the client version, judging whether the client version needs to be updated according to the feedback information, if so, closing the starting animation, updating the value of the registry base item and the local program file, otherwise, executing the initialization method and the starting method of the starting class.
3. The method of claim 2, wherein the step of performing the initialization of the base class specifically comprises:
generating a new log file, the log file comprising: the method comprises the steps of executing an initialization method of an interface manager class by taking a client type as a parameter, setting the client type as the client type of the interface manager, creating a window according to the client type of the interface manager, and setting the title, the minimum width and the minimum height of the window.
4. The login method for the client container according to claim 3, wherein executing the instantiation method for the base class specifically comprises:
and taking the server address list, the encrypted communication file and a locally stored interface display mode as parameters, executing the instantiation method of the base class, adding a base class object obtained by instantiation into a client cache object list, processing the server name in the server address list, loading the encrypted communication file to obtain an encryption key, setting the encryption key as the encryption key of the current application program, starting the interface manager, creating a resource manager, and creating and initializing a thread pool.
5. The method of claim 4, wherein executing the method for starting the base class specifically comprises:
storing a client object in the client cache object list, registering an idle overtime monitoring thread, setting a client socket connection monitor, forcibly interrupting a session event and a client authorization limit event by a registration server, subscribing a popup event and a notification event, setting a socket connection monitor, acquiring a connection attribute value list, and creating a socket connection service according to the connection attribute value list, a socket service type, the server address list and a message processor.
6. The login method for the client container according to claim 5, wherein step S4 specifically includes:
after the starting class is started, acquiring the starting state of the socket connection service, issuing an event that a client tries to log in, displaying a login interface, judging whether the current connection state is the connected state if the socket connection service is in the started state, trying to establish socket connection with the server if the current connection state is the unconnected state, displaying first error prompt information on the login interface if the connection is overtime, issuing a login ending event, and executing the login method of the base class if the connection state is the connected state.
7. The method of claim 6, wherein the performing the login method of the base class specifically comprises:
acquiring a user name and a password from the login interface, displaying a login progress control bar, sending a connection message including a connection ID, the client type, user encryption information, a client IP address, an MAC address, a current client version, a domain name, a port and a registration parameter of a connection server, and whether to kill login of a session to the server, if the login is successful, acquiring a login message result, storing the message result in a context session object in a cache of the current client, and if the login is failed, displaying second error prompt information on the login interface.
8. The login method for the client container according to claim 7, wherein in step a2, the method for starting the reconnect thread specifically includes:
judging whether the connection flag bit is true or false, if the connection flag bit is false, the reconnection thread is in a waiting state, if the connection flag bit is true, reconnection is carried out at preset time intervals within preset reconnection time, registration reconnection is carried out by taking the connection ID, the client type, the domain name and the port number of the connection server and the session context object and the registration parameters as parameters, data are synchronized with the server, and a client connection success event is issued.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710419899.4A CN107172060B (en) | 2017-06-06 | 2017-06-06 | Login method of client container |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710419899.4A CN107172060B (en) | 2017-06-06 | 2017-06-06 | Login method of client container |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107172060A CN107172060A (en) | 2017-09-15 |
| CN107172060B true CN107172060B (en) | 2020-03-17 |
Family
ID=59824520
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710419899.4A Expired - Fee Related CN107172060B (en) | 2017-06-06 | 2017-06-06 | Login method of client container |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107172060B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108229136A (en) * | 2017-12-14 | 2018-06-29 | 宁波升维信息技术有限公司 | A kind of login encryption method |
| CN108616914B (en) * | 2018-03-30 | 2021-09-07 | 武汉斗鱼网络科技有限公司 | Method and device for reconnection of broken line |
| CN110381113A (en) * | 2019-06-12 | 2019-10-25 | 深圳市奥克多普科技有限公司 | A kind of method for service selection and system |
| CN111328155B (en) * | 2020-02-27 | 2022-01-07 | Oppo广东移动通信有限公司 | Data transmission method, device, storage medium and electronic equipment |
| CN112351094B (en) * | 2020-11-02 | 2023-10-03 | 深圳市安软科技股份有限公司 | Webpage pushing method and device, electronic equipment and storage medium |
| CN112799682B (en) * | 2021-04-13 | 2021-06-29 | 杭州太美星程医药科技有限公司 | Data acquisition and processing system and method for operating multi-version application thereof |
| CN114979151B (en) * | 2022-07-27 | 2022-11-11 | 江苏中创供应链服务有限公司 | Method for dynamically adjusting signing service for cross-border e-commerce |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101158906A (en) * | 2007-08-10 | 2008-04-09 | 林明辉 | Customer terminals program automatic update method |
| CN101179424A (en) * | 2006-11-29 | 2008-05-14 | 腾讯科技（深圳）有限公司 | Method and system for updating network client terminal |
| US9356804B1 (en) * | 2012-06-12 | 2016-05-31 | Amazon Technologies, Inc. | Policy-based network connection resource selection |
| CN106454766A (en) * | 2016-09-27 | 2017-02-22 | 盐城工学院 | Real-time cooperation data sharing system based on Android system and Wi-Fi Direct |
-
2017
- 2017-06-06 CN CN201710419899.4A patent/CN107172060B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101179424A (en) * | 2006-11-29 | 2008-05-14 | 腾讯科技（深圳）有限公司 | Method and system for updating network client terminal |
| CN101158906A (en) * | 2007-08-10 | 2008-04-09 | 林明辉 | Customer terminals program automatic update method |
| US9356804B1 (en) * | 2012-06-12 | 2016-05-31 | Amazon Technologies, Inc. | Policy-based network connection resource selection |
| CN106454766A (en) * | 2016-09-27 | 2017-02-22 | 盐城工学院 | Real-time cooperation data sharing system based on Android system and Wi-Fi Direct |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107172060A (en) | 2017-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107172060B (en) | Login method of client container | |
| US11501057B2 (en) | Enabling file attachments in calendar events | |
| US9549057B2 (en) | Method and apparatus of providing messaging service and callback feature to mobile stations | |
| EP2425614B1 (en) | Remotely locating and commanding a mobile device | |
| US8666367B2 (en) | Remotely locating and commanding a mobile device | |
| US7673021B2 (en) | Automated provisioning of phones in packet voice networks | |
| US8965958B2 (en) | File fetch from a remote client device | |
| WO2015188771A1 (en) | Method and apparatus for processing application notification message, and terminal device | |
| US8463758B2 (en) | Network registry and file cleaner | |
| CN110855666B (en) | Gateway equipment activation method, device, equipment and medium based on end cloud cooperation | |
| KR101692733B1 (en) | Method for managing virtual machine and device therefor | |
| AU2019337572B2 (en) | System for providing a service based upon authorization token and virtual assistant and related methods | |
| US9716623B2 (en) | Automatic and secure activation of a universal plug and play device management device | |
| US20220050699A1 (en) | Workspace resiliency with multi-feed status resource caching | |
| CN113170283A (en) | Triggering event notifications based on messages to application users | |
| KR20140033318A (en) | Method for registering and providing notice of a trap event, and terminal using same | |
| WO2015139493A1 (en) | Desktop sharing method and sharing device | |
| WO2023207175A1 (en) | Scanning detection method, apparatus and system in hybrid cloud environment, and device and medium | |
| CN113364979A (en) | Method and system for remote control of devices, server, client device, and medium | |
| JP4506637B2 (en) | Information processing apparatus, information processing method, and computer program | |
| US11425172B2 (en) | Application security for service provider networks | |
| JP2003316738A (en) | Life cycle managing method of object having user authentication and service use restriction corresponding to web service | |
| CN115883153A (en) | Website access control method, device, equipment and storage medium | |
| JP2022536479A (en) | Desktop virtualization with power management linked to client devices | |
| FR2977103A1 (en) | Method for accessing remote server to access medical data, involves connecting universal serial bus key to computer, and copying main application from memory of universal serial bus key to memory e.g. RAM, of computer |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20200317 Termination date: 20210606 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |