CN108156246B - File distribution method, system, server and client - Google Patents

File distribution method, system, server and client Download PDF

Info

Publication number
CN108156246B
CN108156246B CN201711450400.2A CN201711450400A CN108156246B CN 108156246 B CN108156246 B CN 108156246B CN 201711450400 A CN201711450400 A CN 201711450400A CN 108156246 B CN108156246 B CN 108156246B
Authority
CN
China
Prior art keywords
docker
mirror image
image
file
parent
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.)
Active
Application number
CN201711450400.2A
Other languages
Chinese (zh)
Other versions
CN108156246A (en
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.)
BEIJING WELINK Co.,Ltd.
Original Assignee
Beijing Welink Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Welink Co ltd filed Critical Beijing Welink Co ltd
Priority to CN201711450400.2A priority Critical patent/CN108156246B/en
Publication of CN108156246A publication Critical patent/CN108156246A/en
Application granted granted Critical
Publication of CN108156246B publication Critical patent/CN108156246B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application provides a file distribution method, a file distribution system, a server and a client. The method comprises the following steps: the server receives a file downloading request sent by a client, and searches whether a mapped historical Docker mirror image exists according to file information in the request; if so, sending the ID of the historical Docker mirror image to the client; otherwise, a new Docker mirror image is created based on the file information, and the ID of the new Docker mirror image is sent to the client; a client receives a Docker mirror image ID sent by a server; searching whether a corresponding historical Docker mirror image exists according to the Docker mirror image ID; if yes, extracting a file of a historical Docker mirror image; otherwise, downloading the Docker image corresponding to the Docker image ID from the server, and extracting the file of the Docker image. The method avoids repeated downloading of the file, can save system resources and improve the downloading speed.

Description

File distribution method, system, server and client
Technical Field
The present application relates to the field of network technologies, and in particular, to a method, a system, a server, and a client for distributing files based on a Docker.
Background
File distribution, such as file downloading, application updating and the like, is to send a file downloading request to a server by a client, and after receiving the file downloading request, the server finds a corresponding file according to the request and returns the file to the client.
In the prior art, each time a file downloading request of a client is received by a server, the server regards the file downloading request as a brand new file downloading request, downloads all requested files again, and then sends the requested files to the client. However, in practice, the file requested by the client may include the file already downloaded by the client, and if the server still sends the requested entire file to the client, the problem of repeated downloading of the file may occur.
For example, a client updates an application program, and downloads an application program update package of the latest version from a server, where the application program update package includes 100 files, where 80 files already exist in the application program update package of the previous version and have been downloaded by the client, in this case, after the client initiates an update request, if the server still sends 100 files in the latest update package to the client, the client receives all 100 files, and among them, 80 files are repeatedly downloaded, which not only wastes file download resources, but also results in low file download efficiency.
Disclosure of Invention
The application provides a file distribution method, a file distribution system, a server and a client, and aims to solve the problem of repeated downloading of files.
In a first aspect, the present application provides a file distribution method, including: the method comprises the steps that a server receives a file downloading request sent by a client, and file information carried in the request is obtained; searching whether a historical Docker mirror image mapped with the file information exists or not according to the file information; if a historical Docker mirror image mapped with the file information exists, sending the ID of the historical Docker mirror image to the client; otherwise, creating a new Docker mirror image based on the file information, storing the new Docker mirror image, and sending the ID of the new Docker mirror image to the client; the client receives the ID of the historical Docker image or the ID of the new Docker image sent by the server; searching whether a historical Docker mirror image corresponding to the Docker mirror image ID exists or not according to the received Docker mirror image ID, wherein the Docker mirror image ID is the ID of the historical Docker mirror image or the ID of the new Docker mirror image; if a historical Docker mirror image corresponding to the Docker mirror image ID exists, the client extracts a file in the historical Docker mirror image; otherwise, the client downloads the Docker mirror image corresponding to the Docker mirror image ID from the server, and extracts the file in the Docker mirror image corresponding to the Docker mirror image ID.
The file distribution method is based on Docker, files are stored in a Docker mirror image server in a Docker mirror image mode, when a client requests to download the files from the server, the server does not directly return the files to the client, but searches a corresponding existing historical Docker mirror image in the Docker mirror image server according to the information of the requested files, or creates a new Docker mirror image, and returns the ID of the historical Docker mirror image or the ID of the new Docker mirror image to the client. After the client receives the Docker mirror image ID returned by the server side, the Docker client in the client searches whether the Docker mirror image corresponding to the Docker mirror image ID exists or not, if the Docker mirror image exists, the Docker mirror image does not need to be downloaded from the Docker service, if the Docker mirror image does not exist, but the parent mirror image of the Docker mirror image exists, the parent mirror image does not need to be repeatedly downloaded, only the Dcker mirror image needs to be downloaded, and actually the downloaded incremental mirror image part of the Docker mirror image is mainly the incremental mirror image part of the Docker mirror image. According to the method, the repeated downloading of the Docker mirror image is avoided through the multiplexing of the Docker mirror image or the father mirror image thereof, so that the repeated downloading of the file is also avoided, system resources can be saved, and the file downloading speed is increased.
With reference to the first aspect, in a first possible implementation manner of the first aspect, the creating a new Docker image based on the file information includes: searching for alternative Docker images containing one or more files in the files corresponding to the file information, wherein the alternative Docker images do not contain other files except the one or more files in the files corresponding to the file information; selecting the largest Docker mirror image in the alternative Docker mirror images as a parent mirror image; and creating the new Docker image based on the parent image and the file not contained by the parent image, wherein the file not contained by the parent image is one or more files in the files corresponding to the file information. By adopting the inheritance parent mirror image, the method for creating the Docker mirror image based on the parent mirror image and the incremental mirror image is beneficial to the reuse of the Docker mirror image, and system resources are saved
With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the downloading, by the client, a Docker image corresponding to the Docker image ID from the server includes: judging whether the Docker mirror image corresponding to the Docker mirror image ID has a parent mirror image or not; if the Docker mirror image has a parent mirror image, searching whether the parent mirror image exists; if the parent mirror image does not exist, downloading the parent mirror image and a Docker mirror image corresponding to the Docker mirror image ID from the server; and if the Docker mirror image does not have a parent mirror image or the parent mirror image already exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the server. By adopting the implementation mode, the father mirror image can be reused, and the Docker client does not need to repeatedly download the father mirror image, so that system resources can be saved, and the downloading speed is increased.
In a second aspect, the present application provides a file distribution system, the system comprising: the file distribution unit is used for receiving the file downloading request sent by the file receiving unit and acquiring the file information carried in the request; the file synthesis unit is used for searching whether a historical Docker mirror image mapped with the file information exists in a Docker mirror image server according to the file information; if a historical Docker image mapped with the file information exists, transmitting the ID of the historical Docker image to the file distribution unit, otherwise, creating a new Docker image based on the file information, storing the new Docker image in the Docker image server, and transmitting the ID of the new Docker image to the file distribution unit; the file distribution unit is further configured to: sending the ID of the historical Docker image or the ID of the new Docker image to the file receiving unit; the Docker mirror image server is used for storing Docker mirror images; the file receiving unit is configured to receive the ID of the historical Docker image or the ID of the new Docker image sent by the file distributing unit; the Docker client is used for searching whether a historical Docker image corresponding to the Docker image ID exists according to the Docker image ID received by the file receiving unit, wherein the Docker image ID is the ID of the historical Docker image or the ID of the new Docker image; a file extraction unit, configured to extract a file in a historical Docker image if the Docker client has the historical Docker image corresponding to the Docker image ID; the Docker client is further configured to: if no historical Docker mirror image corresponding to the Docker mirror image ID exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server; the file extraction unit is further configured to: and extracting the file in the Docker image corresponding to the Docker image ID.
With reference to the second aspect, in a first possible implementation manner of the second aspect, the file synthesis module is specifically configured to: if the Docker mirror image server does not have a historical Docker mirror image mapped with the file information, searching for an alternative Docker mirror image containing one or more files in the files corresponding to the file information in the Docker mirror image server, wherein the alternative Docker mirror image does not contain other files except the one or more files; selecting the largest Docker mirror image in the alternative Docker mirror images as a parent mirror image; creating the new Docker image based on the parent image and the file not contained in the parent image, generating an ID of the new Docker image, and storing the new Docker image in the Docker image server, wherein the file not contained in the parent image is one or more files in the files corresponding to the file information.
With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the Docker client is specifically configured to: if no historical Docker mirror image corresponding to the Docker mirror image ID exists, judging whether the Docker mirror image corresponding to the Docker mirror image ID has a parent mirror image or not; if the Docker mirror image has a parent mirror image, searching whether the parent mirror image exists; if the parent mirror image does not exist, downloading the parent mirror image and the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server; and if the Docker mirror image does not have a parent mirror image or the parent mirror image already exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server.
In a third aspect, the present application provides a server, including a transceiver, a memory, a processor, and a Docker mirroring server, the transceiver being configured to: receiving a file downloading request sent by a client, and acquiring file information carried in the request; the processor is operable to: searching whether a historical Docker mirror image mapped with the file information exists in the Docker mirror image server according to the file information; if a historical Docker image mapped with the file information exists, transmitting the ID of the historical Docker image to the transceiver; otherwise, creating a new Docker mirror image based on the file information, storing the new Docker mirror image to the Docker mirror image server, and transmitting the ID of the new Docker mirror image to the transceiver; the transceiver is further configured to: and sending the ID of the historical Docker image or the ID of the new Docker image to the client.
With reference to the third aspect, in a first possible implementation manner of the third aspect, the processor is specifically configured to: if the Docker mirror image server does not have a historical Docker mirror image mapped with the file information, searching for an alternative Docker mirror image containing one or more files in the files corresponding to the file information in the Docker mirror image server, wherein the alternative Docker mirror image does not contain other files except the one or more files; selecting the largest Docker mirror image in the alternative Docker mirror images as a parent mirror image; creating the new Docker image based on the parent image and the file not contained in the parent image, generating an ID of the new Docker image, and storing the new Docker image in the Docker image server, wherein the file not contained in the parent image is one or more files in the files corresponding to the file information.
In a fourth aspect, the present application provides a client, comprising a transceiver, a memory, a processor, and a Docker client, the transceiver being configured to: receiving a Docker mirror image ID sent by a server; the Docker client is configured to: searching whether a historical Docker mirror image corresponding to the Docker mirror image ID exists or not according to the Docker mirror image ID; the processor is operable to: if a historical Docker mirror image corresponding to the Docker mirror image ID exists, extracting a file in the historical Docker mirror image; the Doker client is further used for downloading the Docker mirror image corresponding to the Docker mirror image ID from the server if the historical Docker mirror image corresponding to the Docker mirror image ID does not exist; the processor is further configured to: and extracting the file in the Docker image corresponding to the Docker image ID.
With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, if there is no historical Docker image corresponding to the Docker image ID, the Docker client determines whether the Docker image corresponding to the Docker image ID has a parent image; if the Docker mirror image has a parent mirror image, searching whether the parent mirror image exists; if the parent mirror image does not exist, downloading the parent mirror image and a Docker mirror image corresponding to the Docker mirror image ID from the server; and if the Docker mirror image does not have a parent mirror image or the parent mirror image already exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the server.
According to the file distribution scheme provided by the application, the file is stored in the Docker mirror image server in the form of the Docker mirror image, when the client requests the server to download the file, the server does not directly return the file to the client, but searches the corresponding existing historical Docker mirror image in the Docker mirror image server according to the information of the requested file, or creates a new Docker mirror image, and returns the ID of the historical Docker mirror image or the new Docker mirror image to the client. After the client receives the Docker mirror image ID returned by the server side, the Docker client searches whether the Docker mirror image corresponding to the Docker mirror image ID exists or not, if the Docker mirror image ID exists, the Docker mirror image does not need to be downloaded from the Docker mirror image server, if the Docker mirror image ID does not exist, but the parent mirror image of the Docker mirror image exists, the parent mirror image does not need to be repeatedly downloaded, and only the Dcker mirror image needs to be downloaded (actually, the downloaded Dcker mirror image is mainly the incremental mirror image part of the Docker mirror image).
Drawings
FIG. 1 is a schematic diagram of a file distribution system according to the present application;
FIG. 2 is a schematic flow chart of a file synthesis unit creating a new Docker mirror;
FIG. 3 is a schematic flow chart illustrating a process of downloading a Docker image by a Docker client;
fig. 4 is a schematic flowchart of a file distribution method provided in the present application;
FIG. 5 is a schematic diagram of a server according to the present application;
fig. 6 is a schematic structural diagram of a client according to the present application.
Detailed Description
For ease of understanding the present application, the following briefly introduces Docker and Docker mirror images. A Docker is an open-source application container engine, typically using a Client/Server (Client/Server) architecture model, and the Docker Server (or Docker mirror Server) accepts requests from Docker clients and processes the requests (e.g., creates, runs, or distributes containers). The Docker client and the Docker server may operate on the same device, and may also communicate through a socket or a RESTful (RESTful State Transfer, REST refers to a set of architectural constraints and principles, and an Application or a design that satisfies the constraints and principles is a RESTful API (Application Programming Interface), and the like. The Docker server generally runs in the background of the host and waits for receiving a message from the Docker client. The Docker client also runs on the host, which provides a series of executable commands that the user uses to realize the interaction between the Docker client and the Docker server.
The Docker image represents the file system contents of a container. One Docker image may be built on top of another Docker image, and the stacking relationship may be multi-tiered. The mirror Image of the first layer is called a Base Image (Base Image), and the other mirror images layered on the Base Image are called Parent images (Parent images). Each layer of mirror (except the topmost mirror) inherits the properties and settings of its parent mirror and adds its own configuration to the layer of mirror. The Docker image is identified by a Docker image ID.
Referring to fig. 1, a file distribution system provided for the present application includes:
the file distribution unit U101 is used for receiving the file downloading request sent by the file receiving unit and acquiring the file information carried in the request;
a file synthesis unit U102, configured to: searching whether a historical Docker mirror image mapped with the file information exists in a Docker mirror image server U103 according to the file information; if a historical Docker image mapped with the file information exists, transmitting the ID of the historical Docker image to the file distribution unit, otherwise, creating a new Docker image based on the file information, storing the new Docker image in the Docker image server, and transmitting the ID of the new Docker image to the file distribution unit;
the file distribution unit is further configured to: and sending the ID of the history Docker image or the ID of the new Docker image to the file receiving unit.
The Docker mirror image server U103 is used for storing Docker mirror images;
the file receiving unit U104 is configured to receive the ID of the historical Docker image or the ID of the new Docker image sent by the file distributing unit;
the Docker client U105 is configured to search whether a historical Docker image corresponding to the image ID exists according to the Docker image ID received by the file receiving unit;
a file extraction unit U106, configured to extract a file in a history Docker image if the history Docker image corresponding to the Docker image ID exists in the Docker client;
the Docker client is further configured to: if no historical Docker mirror image corresponding to the mirror image ID exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server;
the file extraction unit is further configured to: and extracting the file in the Docker image corresponding to the Docker image ID.
The system comprises a file distribution unit, a file synthesis unit and a Docker mirror image server, wherein the file distribution unit, the file synthesis unit and the Docker mirror image server run at one end for providing downloaded files, such as a file server of a website; the file receiving unit, the Docker client and the file extracting unit are operated at one end of the downloaded file, for example, a client such as a mobile terminal. When a client needs to download a file, a file receiving unit sends a file downloading request to a server providing the downloaded file, specifically, a file distributing unit in the server, where the request carries information of the file requested to be downloaded. After receiving the file download request, the file distribution unit parses the file download request, and obtains file information (e.g., a file name and a URL (Uniform Resource Locator) of the file) carried in the file download request.
The file synthesis unit stores a mapping table of file information and Docker mirror image IDs. One Docker image contains one file or one file set, and when the Docker image is created, the ID of the Docker image and the mapping relation between the ID of the Docker image and the information of the file contained in the ID are also generated, and the mapping relation is stored in the mapping table between the file information and the ID of the Docker image. For example, the Docker image m3 includes three files with file names of file1, file2 and file3, and the mapping table stores the mapping relationship between m3 and the set [ file1file2file3 ]. The file synthesis unit searches whether a Docker image ID mapped with the file information exists in the mapping table according to the file information obtained by the file distribution unit, for example, a client needs to download file1, file2 and file3, a file download request sent to the file distribution unit contains information of file names of file1, file2 and file3, after the file distribution unit receives the file download request, the file synthesis unit obtains information of three files contained in the file download request, for example, file names of file1, file2 and file3, and then the file synthesis unit searches whether a Docker image ID mapped with a set [ file2file2file3] exists in the mapping table according to the file names.
If the file synthesis unit finds the Docker mirror image ID mapped with the file information, the Docker mirror image indicated by the Docker mirror image ID can be found in the Docker mirror image server, namely the file synthesis unit finds the Docker mirror image mapped with the file information; or the file unit searches for a Dokcer image ID mapped with the file information according to the mapping table, and then searches whether a Docker image corresponding to the Docker image ID exists in the Docker image server according to the Docker image ID, if so, the file synthesis unit searches for the Docker image mapped with the file information, and the Docker image mapped with the file information exists. Since the Docker image server stores the created Docker image, the Docker image mapped with the file information and found by the file synthesizing unit is referred to as a history Docker image.
If the file synthesis unit finds that the historical Docker mirror image mapped with the file information exists, the file synthesis unit indicates that the file corresponding to the file information is downloaded, the file synthesis unit transmits the ID of the historical Docker mirror image to the file distribution unit, and the file distribution unit returns the ID to the file receiving unit of the client. If the file synthesizing unit does not find the historical Docker image mapped with the file information, for example, the mapping table does not have the Docker image ID mapped with the file information, or although the mapping table has the Docker image ID mapped with the file information, the Docker image server does not have the Docker image corresponding to the Docker image ID (for example, the Docker image is deleted), it indicates that the file corresponding to the file information is not downloaded or not completely downloaded, and in this case, the file synthesizing unit creates a new Docker image based on the file information.
Specifically, the flow of creating a new Docker image by the file synthesis unit is shown in fig. 2, and the steps are as follows:
step S201, the file synthesizing unit searches for a candidate Docker image including one or more files in the files corresponding to the file information in the Docker image server, and the candidate Docker image does not include other files except the one or more files in the files corresponding to the file information, for example, three files file1, file2, and file3 corresponding to the file information, the Docker image server may store a Docker image m1 including only a file1, and a Docker image m2 including a file1 and a file2, and then both m1 and m2 are candidate Docker images.
Step S202, after finding the candidate Docker images, the file synthesizing unit selects a largest Docker image as a parent image, for example, M1 is 50M, M2 is 100M, and M2 is used as the parent image.
Step S203, after determining the parent image, the file synthesis unit creates a new Docker image based on the parent image and the file not included in the parent image, where the file not included in the parent image is one or more files in the files corresponding to the file information, for example, m2 is the parent image, which only includes file1 and file2, and does not include file3, then creates a new Docker image m3, m3 inherits m2, file3 is used as an incremental image of m3, and the actual code of m3 is described as "from m 2; add file3 ". In fact, m3 contains the incremental image contained file3, file1 and file2 are not actually contained in m3, but are contained in inherited m2, but from the point of view of the Docker image and file information mapping, it can be described that m3 contains file1, file2 and file 3. The mode of inheriting the parent mirror image and creating the Docker mirror image based on the parent mirror image and the incremental mirror image is beneficial to multiplexing the Docker mirror image and saving system resources.
If the file synthesis unit does not find the alternative Docker mirror image in the Docker mirror image server, that is, the Docker mirror image server does not have any file or files containing the file or files corresponding to the file information and does not contain Docker mirror images of other files except the file or files corresponding to the file information, the file synthesis unit creates a new Docker mirror image without a parent mirror image, wherein the Docker mirror image contains all files corresponding to the file information.
And when the file synthesis unit creates a new Docker image, generating the ID of the new Docker image, and storing the created new Docker image in the Docker image server. And after the file synthesis unit creates a new Docker mirror image, the ID of the new Docker mirror image is transmitted to the file distribution unit, and the file distribution unit returns the ID to the file receiving unit of the client.
And the file receiving unit receives the Doker image ID sent by the file distributing unit and transmits the Doker image ID to the Docker client. The method includes the steps that downloaded Docker images are stored in a Docker client (for example, the Docker images stored in the Docker client are stored in a cache and can be called as historical Docker images), the Docker client firstly searches whether Docker images corresponding to Docker image IDs exist in the cache according to the Docker image IDs, if the Docker images exist, the Docker images corresponding to the Docker image IDs are directly transmitted to a file extraction unit, files contained in the Docker images are extracted by the file extraction unit, and therefore if all files to be downloaded by the client are downloaded, all the files do not need to be downloaded from a server, and repeated downloading of the files is avoided.
If the history Docker mirror image corresponding to the Docker mirror image ID received by the file receiving unit does not exist in the Docker client, the Docker client downloads the corresponding Docker mirror image from the Docker mirror image server according to the Docker mirror image ID. Specifically, as shown in fig. 3, the steps are as follows:
step S301, the Docker client judges whether a Docker mirror image corresponding to the Docker mirror image ID has a parent mirror image, specifically, the Docker client can acquire information of the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server according to the Docker mirror image ID, the information of the Docker mirror image contains parent mirror image information of the Docker mirror image, and judges whether the Dcker mirror image has the parent mirror image according to the parent mirror image information, for example, the parent mirror image information is empty, if the Dcker mirror image does not have the parent mirror image, the Dcker mirror image has the parent mirror image, otherwise, the Docker client obtains the ID of the parent; or the Docker mirror image ID comprises parent mirror image information, the Docker client analyzes the Dcker mirror image ID to obtain parent mirror image information of the Docker mirror image corresponding to the Docker mirror image ID, and whether the Docker mirror image has the parent mirror image is judged according to the parent mirror image information.
Step S302, if the Docker mirror image has a parent mirror image, searching whether the parent mirror image exists, namely judging whether the parent mirror image is downloaded;
step S303, if the parent image does not exist, that is, the parent image is not downloaded, the parent image and the Docker image corresponding to the Docker image ID are downloaded from the Docker image server.
Step S304, if the Docker mirror image does not have a parent mirror image or the parent mirror image already exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server. For example, the Docker image ID corresponds to the Docker image m3, and if m3 does not have a parent image, m3 is downloaded from the Docker image server; if m3 has a parent mirror m2, for example, the description of m3 is "from m 2; if the Add file 3' exists, m2 is downloaded from the Docker mirror image server to obtain m3, and actually, an incremental mirror image containing the file3 is downloaded, so that m2 can be reused, and a Docker client does not need to repeatedly download m2, thereby saving system resources and improving the downloading speed; if m2 does not exist, m2 and m3 are downloaded from the Docker image server, that is, both the parent image and the incremental image need to be downloaded to obtain the file contained in m3 completely. And after the Docker client finishes downloading the Docker mirror image corresponding to the Docker mirror image ID, transmitting the downloaded Docker mirror image to the file extraction unit, and extracting the file in the Docker mirror image by the file extraction unit to finish the downloading of the file.
According to the Docker-based file distribution system, files are stored in a Docker mirror image server in a Docker mirror image mode, when a client requests the server to download the files, the server does not directly return the files to the client, but searches for corresponding existing historical Docker images in the Docker mirror image server according to the information of the requested files, or creates new Docker images, and returns the IDs of the historical Docker images or the new Docker images to the client. After the client receives the Docker mirror image ID returned by the server side, the Docker client searches whether the Docker mirror image corresponding to the Docker mirror image ID exists or not, if the Docker mirror image ID exists, the Docker mirror image does not need to be downloaded from the Docker mirror image server, if the Docker mirror image ID does not exist, but the parent mirror image of the Docker mirror image exists, the parent mirror image does not need to be repeatedly downloaded, and only the Dcker mirror image needs to be downloaded (actually, the downloaded Dcker mirror image is mainly the incremental mirror image part of the Docker mirror image).
For convenience of description, the above system is described as being divided into various units by functions, and described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
Referring to fig. 4, there is also provided a file distribution method for the present application, the method comprising:
step S401, a server receives a file downloading request sent by a client;
step S402, acquiring the file information carried in the request;
step S403, searching whether a historical Docker mirror image mapped with the file information exists according to the file information;
step S404, if a history Docker mirror image mapped with the file information exists, sending the ID of the history Docker mirror image to the client;
step S405, otherwise, creating a new Docker mirror image based on the file information, saving the new Docker mirror image, and sending the ID of the new Docker mirror image to the client;
step S406, the client receives the ID of the historical Docker image or the ID of the new Docker image sent by the server;
step S407, searching whether a historical Docker image corresponding to the Docker image ID exists or not according to the received Docker image ID, wherein the Docker image ID is the ID of the historical Docker image or the ID of the new Docker image;
step S408, if a historical Docker image corresponding to the Docker image ID exists, the client extracts a file in the historical Docker image;
step S409, otherwise, the client downloads the Docker mirror image corresponding to the mirror image ID from the server, and extracts the file in the Docker mirror image corresponding to the mirror image ID.
In a possible implementation manner, the creating a new Docker image based on the file information includes:
searching for alternative Docker images containing one or more files in the files corresponding to the file information, wherein the alternative Docker images do not contain other files except the one or more files in the files corresponding to the file information;
selecting the largest Docker mirror image in the alternative Docker mirror images as a parent mirror image;
and creating the new Docker image based on the parent image and the file not contained by the parent image, wherein the file not contained by the parent image is one or more files in the files corresponding to the file information.
Specifically, the server searches for a candidate Docker image including one or more files in the files corresponding to the file information in a Docker image server, and the candidate Docker image does not include other files except the one or more files in the files corresponding to the file information. And after the alternative Docker mirror images are found, taking the largest Docker mirror image as a parent mirror image. After the parent mirror image is determined, a new Docker mirror image is created based on the parent mirror image and the file which is not contained in the parent mirror image, wherein the file which is not contained is used as the incremental mirror image of the new Docker mirror image, the mode of inheriting the parent mirror image and creating the Docker mirror image based on the parent mirror image and the incremental mirror image is beneficial to multiplexing of the Docker mirror image, and system resources are saved.
If the alternative Docker image is not found in the Docker image server, that is, there is no Docker image in the Docker image server that contains one or more of the files corresponding to the file information and does not contain other files except the one or more of the files corresponding to the file information, a new Docker image without a parent image is created, where the Docker image contains all the files corresponding to the file information.
And when a new Docker image is created, the ID of the new Docker image is generated at the same time, and the created new Docker image is stored in the Docker image server. And after the new Docker image is created, the server returns the ID of the new Docker image to the client.
In a possible implementation manner, the downloading, by the client, the Docker image corresponding to the image ID from the server includes:
judging whether the Docker mirror image has a parent mirror image or not;
if the Docker mirror image has a parent mirror image, searching whether the parent mirror image exists;
if the father mirror image does not exist, downloading the father mirror image and a Docker mirror image corresponding to the mirror image ID from the server;
and if the Docker mirror image does not have a parent mirror image or the parent mirror image already exists, downloading the Docker mirror image corresponding to the mirror image ID from the server.
Specifically, if no history Docker image corresponding to the Docker image ID received by the file receiving unit exists in the Docker client, the Docker client downloads the corresponding Docker image from the Docker image server according to the Docker image ID. Specifically, the Docker client determines whether a Docker image corresponding to the Docker image ID has a parent image, specifically, the Docker client may acquire information of the Docker image corresponding to the Docker image ID from the Docker image server according to the Docker image ID, where the information of the Docker image includes parent image information of the Docker image, and determine whether the Dcker image has the parent image according to the parent image information; or the Docker mirror image ID comprises parent mirror image information, the Docker client analyzes the Dcker mirror image ID to obtain parent mirror image information of the Docker mirror image corresponding to the Docker mirror image ID, and whether the Docker mirror image has the parent mirror image is judged according to the parent mirror image information.
If the Docker mirror image has a parent mirror image, searching whether the parent mirror image exists, namely whether the parent mirror image has been downloaded, and if the parent mirror image does not exist, namely the parent mirror image has not been downloaded, downloading the parent mirror image and the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server. If the Docker mirror image does not have a parent mirror image or the parent mirror image already exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server, so that the parent mirror image can be reused, and the Docker client does not need to repeatedly download the parent mirror image, thereby saving system resources and improving the downloading speed. And if the parent mirror image does not exist, downloading the parent mirror image and the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server, namely downloading the parent mirror image and the incremental mirror image to completely obtain all files. And after the Docker client finishes downloading the Docker mirror image corresponding to the Docker mirror image ID, extracting the file in the Docker mirror image and finishing the downloading of the file.
According to the Docker-based file distribution method, files are stored in a Docker mirror image server in a Docker mirror image mode, when a client requests the server to download the files, the server does not directly return the files to the client, but searches the corresponding existing historical Docker mirror image in the Docker mirror image server according to the information of the requested files or creates a new Docker mirror image, and the ID of the historical Docker mirror image or the ID of the new Docker mirror image is returned to the client. After the client receives the Docker mirror image ID returned by the server side, the Docker client in the client searches whether the Docker mirror image corresponding to the Docker mirror image ID exists or not, if the Docker mirror image ID exists, the Docker mirror image does not need to be downloaded from the Docker mirror image server, if the Docker mirror image does not exist, but the parent mirror image of the Docker mirror image exists, the parent mirror image does not need to be repeatedly downloaded, only the Dcker mirror image needs to be downloaded, and the incremental mirror image part of the Docker mirror image is actually downloaded. According to the method, the repeated downloading of the Docker mirror image is avoided through the multiplexing of the Docker mirror image or the father mirror image thereof, so that the repeated downloading of the file is also avoided, system resources can be saved, and the file downloading speed is increased.
The present application also provides a server, as shown in fig. 5, comprising a transceiver, a memory, a processor, and a Docker mirroring server,
the transceiver is to: receiving a file downloading request sent by a client, and acquiring file information carried in the request;
the processor is operable to:
searching whether a historical Docker mirror image mapped with the file information exists in the Docker mirror image server according to the file information;
if a historical Docker image mapped with the file information exists, transmitting the ID of the historical Docker image to the transceiver;
otherwise, creating a new Docker mirror image based on the file information, storing the new Docker mirror image to the Docker mirror image server, and transmitting the ID of the new Docker mirror image to the transceiver;
the transceiver is further configured to: and sending the ID of the historical Docker image or the ID of the new Docker image to the client.
In one possible implementation, the processor is specifically configured to:
if the Docker mirror image server does not have a historical Docker mirror image mapped with the file information, searching for alternative Docker mirror images containing one or more files in the files corresponding to the file information in the Docker mirror image server;
selecting the largest Docker mirror image in the alternative Docker mirror images as a parent mirror image;
creating the new Docker image based on the parent image and the file not contained in the parent image, generating an ID of the new Docker image, and storing the new Docker image in the Docker image server, wherein the file not contained in the parent image is one or more files in the files corresponding to the file information.
Specifically, the server searches for a candidate Docker image including one or more files in the files corresponding to the file information in a Docker image server, and the candidate Docker image does not include other files except the one or more files in the files corresponding to the file information. And after the alternative Docker mirror images are found, taking the largest Docker mirror image as a parent mirror image. After the parent mirror image is determined, a new Docker mirror image is created based on the parent mirror image and the file which is not contained in the parent mirror image, wherein the file which is not contained is used as the incremental mirror image of the new Docker mirror image, the mode of inheriting the parent mirror image and creating the Docker mirror image based on the parent mirror image and the incremental mirror image is beneficial to multiplexing of the Docker mirror image, and system resources are saved.
If the alternative Docker image is not found in the Docker image server, that is, there is no Docker image in the Docker image server that contains one or more of the files corresponding to the file information and does not contain other files except the one or more of the files corresponding to the file information, a new Docker image without a parent image is created, where the Docker image contains all the files corresponding to the file information. And when the server creates a new Docker image, the ID of the new Docker image is generated at the same time, and the created new Docker image is stored in the Docker image server. And after the new Docker image is created, the server returns the ID of the new Docker image to the client.
The present application also provides a client, as shown in fig. 6, comprising a transceiver, a memory, a processor, and a Docker client,
the transceiver is to: receiving a mirror image ID sent by a server;
the Docker client is configured to: searching whether a historical Docker mirror image corresponding to the mirror image ID exists or not according to the mirror image ID;
the processor is operable to: if a historical Docker mirror image corresponding to the mirror image ID exists, extracting a file in the historical Docker mirror image;
the Doker client is further used for downloading the Docker mirror image corresponding to the mirror image ID from the server if the historical Docker mirror image corresponding to the mirror image ID does not exist;
the processor is further configured to: and extracting the file in the Docker image corresponding to the image ID.
In a possible implementation manner, the Docker client is specifically configured to:
if no historical Docker mirror image corresponding to the mirror image ID exists, analyzing the Docker mirror image, and judging whether the Docker mirror image has a parent mirror image or not;
if the Docker mirror image has a parent mirror image, searching whether the parent mirror image exists;
if the father mirror image does not exist, downloading the father mirror image and a Docker mirror image corresponding to the mirror image ID from the server;
and if the Docker mirror image does not have a parent mirror image or the parent mirror image already exists, downloading the Docker mirror image corresponding to the mirror image ID from the server.
Specifically, if no history Docker image corresponding to the Docker image ID received by the file receiving unit exists in the Docker client, the Docker client downloads the corresponding Docker image from the Docker image server according to the Docker image ID. Specifically, the Docker client determines whether a Docker image corresponding to the Docker image ID has a parent image, specifically, the Docker client may acquire information of the Docker image corresponding to the Docker image ID from the Docker image server according to the Docker image ID, where the information of the Docker image includes parent image information of the Docker image, and determine whether the Dcker image has the parent image according to the parent image information; or the Docker mirror image ID comprises parent mirror image information, the Docker client analyzes the Dcker mirror image ID to obtain parent mirror image information of the Docker mirror image corresponding to the Docker mirror image ID, and whether the Docker mirror image has the parent mirror image is judged according to the parent mirror image information.
If the Docker mirror image has a parent mirror image, the Docker client searches whether the parent mirror image exists, namely whether the parent mirror image is downloaded, and if the parent mirror image does not exist, namely the parent mirror image is not downloaded, the Docker client downloads the parent mirror image and the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server. If the Docker mirror image does not have a parent mirror image or the parent mirror image already exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server, so that the parent mirror image can be reused, and the Docker client does not need to repeatedly download the parent mirror image, thereby saving system resources and improving the downloading speed. And if the parent mirror does not exist, the Docker client downloads the parent mirror and the Docker mirror corresponding to the Docker mirror ID from the Docker mirror server. And after the Docker client finishes downloading the Docker mirror image corresponding to the Docker mirror image ID, the processor extracts the file in the Docker mirror image and finishes downloading the file.
The client avoids repeated downloading of the Docker mirror image through multiplexing of the Docker mirror image or the father mirror image thereof, thereby avoiding repeated downloading of the file, saving system resources and improving the file downloading speed.
For convenience of description, the above devices are described as being divided into various units and modules by functions, respectively. Of course, the functionality of the units and modules may be implemented in the same one or more software and/or hardware when implementing the present application.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the method or apparatus embodiments are substantially similar to the system embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the system embodiments for related points. The above-described embodiments of the apparatus and system are merely illustrative, and the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the models can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

Claims (10)

1. A file distribution method, comprising:
the method comprises the steps that a server receives a file downloading request sent by a client, and file information carried in the request is obtained;
searching whether a historical Docker mirror image mapped with the file information exists or not according to the file information;
if a historical Docker mirror image mapped with the file information exists, sending the ID of the historical Docker mirror image to the client;
otherwise, creating a new Docker mirror image based on the file information, storing the new Docker mirror image, and sending the ID of the new Docker mirror image to the client;
the client receives the ID of the historical Docker image or the ID of the new Docker image sent by the server;
searching whether a historical Docker mirror image corresponding to the Docker mirror image ID exists or not according to the received Docker mirror image ID, wherein the Docker mirror image ID is the ID of the historical Docker mirror image or the ID of the new Docker mirror image;
if a historical Docker mirror image corresponding to the Docker mirror image ID exists, the client extracts a file in the historical Docker mirror image;
otherwise, the client downloads the Docker mirror image corresponding to the Docker mirror image ID from the server, and extracts the file in the Docker mirror image corresponding to the Docker mirror image ID.
2. The file distribution method according to claim 1, wherein the creating a new Docker image based on the file information includes:
searching for alternative Docker images containing one or more files in the files corresponding to the file information, wherein the alternative Docker images do not contain other files except the one or more files in the files corresponding to the file information;
selecting the largest Docker mirror image in the alternative Docker mirror images as a parent mirror image;
and creating the new Docker image based on the parent image and the file not contained by the parent image, wherein the file not contained by the parent image is one or more files in the files corresponding to the file information.
3. The file distribution method according to claim 1 or 2, wherein the downloading, by the client, the Docker image corresponding to the Docker image ID from the server includes:
judging whether the Docker mirror image corresponding to the Docker mirror image ID has a parent mirror image or not;
if the Docker mirror image has a parent mirror image, searching whether the parent mirror image exists;
if the parent mirror image does not exist, downloading the parent mirror image and a Docker mirror image corresponding to the Docker mirror image ID from the server;
and if the Docker mirror image does not have a parent mirror image or the parent mirror image already exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the server.
4. A file distribution system, comprising:
the file distribution unit is used for receiving the file downloading request sent by the file receiving unit and acquiring the file information carried in the request;
the file synthesis unit is used for searching whether a historical Docker mirror image mapped with the file information exists in a Docker mirror image server according to the file information;
if a historical Docker mirror image mapped with the file information exists, transmitting the ID of the historical Docker mirror image to the file distribution unit;
otherwise, creating a new Docker mirror image based on the file information, storing the new Docker mirror image in the Docker mirror image server, and transmitting the ID of the new Docker mirror image to the file distribution unit;
the file distribution unit is further configured to: sending the ID of the historical Docker image or the ID of the new Docker image to the file receiving unit;
the Docker mirror image server is used for storing Docker mirror images;
the file receiving unit is configured to receive the ID of the historical Docker image or the ID of the new Docker image sent by the file distributing unit;
the Docker client is used for searching whether a historical Docker image corresponding to the Docker image ID exists according to the Docker image ID received by the file receiving unit, wherein the Docker image ID is the ID of the historical Docker image or the ID of the new Docker image;
a file extraction unit, configured to extract a file in a historical Docker image if the Docker client has the historical Docker image corresponding to the Docker image ID;
the Docker client is further configured to: if no historical Docker mirror image corresponding to the Docker mirror image ID exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server;
the file extraction unit is further configured to: and extracting the file in the Docker image corresponding to the Docker image ID.
5. The file distribution system of claim 4, wherein the file composition module is specifically configured to:
if the Docker mirror image server does not have a historical Docker mirror image mapped with the file information, searching for an alternative Docker mirror image containing one or more files in the files corresponding to the file information in the Docker mirror image server, wherein the alternative Docker mirror image does not contain other files except the one or more files in the files corresponding to the file information;
selecting the largest Docker mirror image in the alternative Docker mirror images as a parent mirror image;
creating the new Docker image based on the parent image and the file not contained in the parent image, generating an ID of the new Docker image, and storing the new Docker image in the Docker image server, wherein the file not contained in the parent image is one or more files in the files corresponding to the file information.
6. The file distribution system of claim 4 or 5, wherein the Docker client is specifically configured to:
if no historical Docker mirror image corresponding to the Docker mirror image ID exists, judging whether the Docker mirror image corresponding to the Docker mirror image ID has a parent mirror image or not;
if the Docker mirror image has a parent mirror image, searching whether the parent mirror image exists;
if the parent mirror image does not exist, downloading the parent mirror image and the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server;
and if the Docker mirror image does not have a parent mirror image or the parent mirror image already exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the Docker mirror image server.
7. A server, comprising a transceiver, a memory, a processor, and a Docker mirror server,
the transceiver is to: receiving a file downloading request sent by a client, and acquiring file information carried in the request;
the processor is operable to:
searching whether a historical Docker mirror image mapped with the file information exists in the Docker mirror image server according to the file information;
if a historical Docker image mapped with the file information exists, transmitting the ID of the historical Docker image to the transceiver;
otherwise, creating a new Docker mirror image based on the file information, storing the new Docker mirror image to the Docker mirror image server, and transmitting the ID of the new Docker mirror image to the transceiver;
the transceiver is further configured to: and sending the ID of the historical Docker image or the ID of the new Docker image to the client.
8. The server of claim 7, wherein the processor is specifically configured to:
if the Docker mirror image server does not have a historical Docker mirror image mapped with the file information, searching for an alternative Docker mirror image containing one or more files in the files corresponding to the file information in the Docker mirror image server, wherein the alternative Docker mirror image does not contain other files except the one or more files in the files corresponding to the file information;
selecting the largest Docker mirror image in the alternative Docker mirror images as a parent mirror image;
creating the new Docker image based on the parent image and the file not contained in the parent image, generating an ID of the new Docker image, and storing the new Docker image in the Docker image server, wherein the file not contained in the parent image is one or more files in the files corresponding to the file information.
9. A client, comprising a transceiver, a memory, a processor, and a Docker client,
the transceiver is to: receiving a Docker mirror image ID sent by a server;
the Docker client is configured to: searching whether a historical Docker mirror image corresponding to the Docker mirror image ID exists or not according to the Docker mirror image ID;
the processor is operable to: if a historical Docker mirror image corresponding to the Docker mirror image ID exists, extracting a file in the historical Docker mirror image;
the Doker client is further used for downloading the Docker mirror image corresponding to the Docker mirror image ID from the server if the historical Docker mirror image corresponding to the Docker mirror image ID does not exist;
the processor is further configured to: and extracting the file in the Docker image corresponding to the Docker image ID.
10. The client of claim 9, wherein the Docker client comprises:
if no historical Docker mirror image corresponding to the Docker mirror image ID exists, judging whether the Docker mirror image corresponding to the Docker mirror image ID has a parent mirror image or not;
if the Docker mirror image has a parent mirror image, searching whether the parent mirror image exists;
if the parent mirror image does not exist, downloading the parent mirror image and a Docker mirror image corresponding to the Docker mirror image ID from the server;
and if the Docker mirror image does not have a parent mirror image or the parent mirror image already exists, downloading the Docker mirror image corresponding to the Docker mirror image ID from the server.
CN201711450400.2A 2017-12-27 2017-12-27 File distribution method, system, server and client Active CN108156246B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711450400.2A CN108156246B (en) 2017-12-27 2017-12-27 File distribution method, system, server and client

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711450400.2A CN108156246B (en) 2017-12-27 2017-12-27 File distribution method, system, server and client

Publications (2)

Publication Number Publication Date
CN108156246A CN108156246A (en) 2018-06-12
CN108156246B true CN108156246B (en) 2020-12-04

Family

ID=62462423

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711450400.2A Active CN108156246B (en) 2017-12-27 2017-12-27 File distribution method, system, server and client

Country Status (1)

Country Link
CN (1) CN108156246B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114666319B (en) * 2022-03-02 2024-03-22 北京百度网讯科技有限公司 Data downloading method, device, electronic equipment and readable storage medium
CN115348254B (en) * 2022-07-21 2023-05-30 昆仑数智科技有限责任公司 File packing and downloading method and device, electronic equipment and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105069353A (en) * 2015-08-11 2015-11-18 武汉大学 Security reinforcement method for credible container based on Docker
CN105740048A (en) * 2016-01-26 2016-07-06 华为技术有限公司 Image management method, device and system
CN105930230A (en) * 2016-04-18 2016-09-07 乐视控股（北京）有限公司 Multilayer mirror image management method
CN106487850A (en) * 2015-08-29 2017-03-08 华为技术有限公司 The methods, devices and systems of mirror image are obtained under a kind of cloud environment
CN106506587A (en) * 2016-09-23 2017-03-15 中国人民解放军国防科学技术大学 A kind of Docker image download methods based on distributed storage

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105069353A (en) * 2015-08-11 2015-11-18 武汉大学 Security reinforcement method for credible container based on Docker
CN106487850A (en) * 2015-08-29 2017-03-08 华为技术有限公司 The methods, devices and systems of mirror image are obtained under a kind of cloud environment
CN105740048A (en) * 2016-01-26 2016-07-06 华为技术有限公司 Image management method, device and system
CN105930230A (en) * 2016-04-18 2016-09-07 乐视控股（北京）有限公司 Multilayer mirror image management method
CN106506587A (en) * 2016-09-23 2017-03-15 中国人民解放军国防科学技术大学 A kind of Docker image download methods based on distributed storage

Also Published As

Publication number Publication date
CN108156246A (en) 2018-06-12

Similar Documents

Publication Publication Date Title
JP5296221B2 (en) Method for installing application in NFC-compatible device, NFC-compatible device, server node, computer-readable medium, and computer program
KR101888704B1 (en) Method and system for proximity-based, peer-initiated device configuration
CN103841134A (en) API-based method for sending and receiving information, API-based apparatus, and API-based system
CN108235763B (en) Detection system, method and related device
CN103309694A (en) Application program updating method and device
CN102081536A (en) Method for updating increment, and server
CN104820643A (en) Method and apparatus for establishing connection between user equipment and smart device
US9058182B2 (en) Management device for causing devices to update programs and computer readable media
CN104951466A (en) POI information search method, device and system and related equipment
JP2004240761A (en) Messaging system
CN104780189A (en) Software upgrading method and software upgrading device
CN101616132A (en) A kind of data capture method and device thereof and system
WO2009109980A2 (en) Method and system for transfer of application between devices
CN108156246B (en) File distribution method, system, server and client
CN110704376A (en) Log file saving method and device
CN103987064A (en) Access point (AP) upgrading method and device
CN105530323A (en) File upgrading method, related equipment and system
CN104619039A (en) Terminal equipment interconnection method and system in wireless local area network (WLAN) and terminal equipment
CN111339047B (en) Data interaction method, device and system
CN104581695A (en) Mobile terminal configuration method and system
CN102685220A (en) Method and system for data interaction based on WEB page
CN103036983A (en) Method, network node, server and system of information acquisition
CN104536777A (en) Method and device for confirming application to be started and executing corresponding operation
CN113596795B (en) Device binding method, device and computer readable storage medium
CN105045638A (en) Method and device for acquiring software package information as well as method and device for installing software package

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
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20201117

Address after: Room 4-15, 4 / F, building 10, East District, No. 10 courtyard, northwest Wangdong Road, Haidian District, Beijing 100193

Applicant after: BEIJING WELINK Co.,Ltd.

Address before: 100084 Haidian District, Haidian District, Beijing, No. four layer 4034

Applicant before: BEIJING GALAXY CLOUD INFORMATION TECHNOLOGY Co.,Ltd.

Applicant before: BEIJING GALAXY WORLD GROUP Co.,Ltd.

GR01 Patent grant
GR01 Patent grant