CN110247951B - File transmission control method, device, equipment and storage medium - Google Patents

File transmission control method, device, equipment and storage medium Download PDF

Info

Publication number
CN110247951B
CN110247951B CN201910381352.9A CN201910381352A CN110247951B CN 110247951 B CN110247951 B CN 110247951B CN 201910381352 A CN201910381352 A CN 201910381352A CN 110247951 B CN110247951 B CN 110247951B
Authority
CN
China
Prior art keywords
file
server
intranet
uploading
user
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
CN201910381352.9A
Other languages
Chinese (zh)
Other versions
CN110247951A (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.)
Jianxin Rongtong Co ltd
Original Assignee
Jianxin Rongtong 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 Jianxin Rongtong Co ltd filed Critical Jianxin Rongtong Co ltd
Priority to CN201910381352.9A priority Critical patent/CN110247951B/en
Publication of CN110247951A publication Critical patent/CN110247951A/en
Application granted granted Critical
Publication of CN110247951B publication Critical patent/CN110247951B/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/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The embodiment of the application discloses a file transmission control method, which comprises the following steps: receiving a file transmission request, wherein the file transmission request carries a user identifier and a request type identifier; under the condition that the request type identifier is a file downloading type, if the user identifier represents that the user is an intranet user, starting an intranet local downloading scene, downloading the required file from an intranet server, and if the user identifier represents that the user is not the intranet user, starting an extranet downloading scene preferentially, and downloading the required file from an extranet server; under the condition that the request type identification is a file uploading type, if the user identification represents that the user is an intranet user, an intranet local uploading scene is started, the file is uploaded to an intranet server and is synchronized to an extranet server, if the user identification represents that the user is not the intranet user, the extranet uploading scene is preferentially started, the file is uploaded to the extranet server and is synchronized to the intranet server, and the problem that the entrance bandwidth linearly increases along with the increase of the user access amount is solved.

Description

File transmission control method, device, equipment and storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for controlling file transfer.
Background
Due to the fact that China is broad, the construction condition of network infrastructure is unbalanced, the access speed between different network service providers is not ideal, and other objective situations, users in different regions are often encountered in a traditional enterprise centralized deployment file storage system, the uploading and downloading speeds are greatly different, and the downloading is often slow. Even some users cannot smoothly complete uploading and downloading of files.
On the other hand, for a file storage system deployed in a centralized manner, uploading and downloading of external network users both need to occupy the entrance bandwidth of an enterprise, which causes the demand of the enterprise on the entrance bandwidth, and the demand linearly increases along with the amount of business of the enterprise. The expansion speed of the enterprise entrance bandwidth is slow, the cost is high, and the expansion becomes a bottleneck factor restricting the expansion of enterprise business.
Disclosure of Invention
The embodiment of the application provides a file transmission control method, a file transmission control device, file transmission control equipment and a storage medium, and the method, the device and the equipment can save the entrance bandwidth to the maximum extent on the premise of meeting the uploading and downloading requirements of internal and external network users.
In view of this, a first aspect of the present application provides a file transfer control method, including:
receiving a file transmission request, wherein the file transmission request carries a user identifier and a request type identifier;
under the condition that the request type identifier is a file downloading type, when the user identifier indicates that the user is an intranet user, starting an intranet local downloading scene, and downloading a required file from an intranet server; when the user identification represents that the user is not the intranet user, the extranet downloading scene is started preferentially, and the required file is downloaded from the extranet server;
under the condition that the request type identifier is a file uploading type, when the user identifier represents that the user is an intranet user, starting an intranet local uploading scene, uploading the file to an intranet server and synchronizing the file to an extranet server; and when the user identification represents that the user is not the intranet user, preferentially starting an extranet uploading scene, uploading the file to an extranet server and synchronizing the file to the intranet server.
A second aspect of the present application provides a file transfer control apparatus, including:
the device comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a file transmission request which carries a user identifier and a request type identifier;
the first downloading unit is used for starting an intranet local downloading scene and downloading a required file from an intranet server when the user identifier represents that the user is an intranet user under the condition that the request type identifier is a file downloading type;
the second downloading unit is used for preferentially starting an external network downloading scene and downloading the required file from the external network server when the user identifier represents that the user is not the internal network user under the condition that the request type identifier is the file downloading type;
the first uploading unit is used for starting an intranet local uploading scene when the user identifier represents that the user is an intranet user under the condition that the request type identifier is a file uploading type, uploading the file to an intranet server and synchronizing the file to an extranet server;
and the second uploading unit is used for preferentially starting an external network uploading scene when the user identifier represents that the user is not an intranet user under the condition that the request type identifier is a file uploading type, uploading the file to an external network server and synchronizing the file to the intranet server.
A third aspect of the present application provides a file transfer system, comprising:
the system comprises terminal equipment, an intranet server and an extranet server;
the terminal device executes the file transmission control method according to the first aspect by running a computer program;
the intranet server and the extranet server are used for synchronously storing files uploaded by the user through the terminal equipment and providing file downloading service for the user.
A fourth aspect of the present application provides a file transfer device, the device comprising a processor and a memory:
the memory is used for storing program codes and transmitting the program codes to the processor;
the processor is configured to execute the steps of the file transfer control method according to the first aspect, according to instructions in the program code.
A fifth aspect of the present application provides a computer-readable storage medium for storing program code for executing the file transfer control method according to the first aspect.
A sixth aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the file transfer control method of the first aspect described above.
According to the technical scheme, the embodiment of the application has the following advantages:
the embodiment of the application provides a file transmission control method, which provides corresponding file uploading and downloading services for an extranet user and an intranet user respectively, ensures that all files only pass through an entrance bandwidth once, and saves the entrance bandwidth to the maximum extent. Specifically, in the process of transmitting a file, a file transmission request is received first, and the file transmission request carries a user identifier and a request type identifier; under the condition that the request type identifier is a file downloading type, if the user identifier represents that the user is an intranet user, starting an intranet local downloading scene, downloading the required file from an intranet server, and if the user identifier represents that the user is not the intranet user, starting an extranet downloading scene preferentially, and downloading the required file from an extranet server; and if the user identification indicates that the user is not the intranet user, preferentially starting an extranet uploading scene, uploading the file to the extranet server and synchronizing the file to the intranet server. Therefore, when downloading the required file, the external network user does not need to pass through the internal network server and correspondingly does not need to occupy the entrance bandwidth, the problem that the entrance bandwidth linearly increases along with the increase of the user access amount is effectively solved, and the entrance bandwidth is saved to the maximum extent.
Drawings
Fig. 1 is a schematic view of an application scenario of a file transfer control method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a file transfer control method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a file downloading method according to an embodiment of the present application;
fig. 4 is a schematic flowchart of a file uploading method according to an embodiment of the present application;
fig. 5 is a schematic flowchart of an external network upload scenario provided in an embodiment of the present application;
fig. 6 is an interaction signaling diagram of an extranet upload scenario according to an embodiment of the present application;
fig. 7 is a schematic flowchart of an external network downloading scenario according to an embodiment of the present application;
fig. 8 is an interactive signaling diagram of an extranet download scenario according to an embodiment of the present application;
fig. 9 is a schematic flow chart of a local intranet upload scene according to an embodiment of the present application;
fig. 10 is an interactive signaling diagram of a local intranet upload scene according to an embodiment of the present application;
fig. 11 is a schematic flowchart of a local downloading scenario of an intranet according to an embodiment of the present application;
fig. 12 is an interactive signaling diagram of a local downloading scenario in an intranet according to an embodiment of the present application;
fig. 13 is a schematic structural diagram of a file transfer control apparatus according to an embodiment of the present application;
fig. 14 is a schematic structural diagram of a server according to an embodiment of the present application;
fig. 15 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In the prior art, both an external network user and an internal network user need to upload and download files through a centrally deployed file storage system; however, when uploading and downloading files, the extranet user needs to occupy the enterprise portal bandwidth, so the requirement for the enterprise portal bandwidth will increase linearly with the increase of the traffic, and is limited by the factors of low expansion speed of the enterprise portal bandwidth, high expansion cost and the like, and the expansion of the enterprise service will be trapped in the bottleneck due to the continuously increased traffic.
In view of the problems in the prior art, an embodiment of the present application provides a file transmission control method, which provides corresponding file uploading and downloading services for an extranet user and an intranet user, respectively, that is, when the extranet user uploads or downloads a file, an extranet uploading scene or an extranet downloading scene is preferentially started, and the file uploaded by the extranet user is synchronized to an intranet server in the extranet uploading scene, and when the intranet user uploads or downloads a file, an intranet local uploading scene or an intranet local downloading scene is started, and the file uploaded by the intranet user is synchronized to the extranet server in the intranet local uploading scene. Therefore, all files occupy the entrance bandwidth only when being uploaded, the external network user does not need to pass through the internal network server when downloading the files, accordingly, the entrance bandwidth of the external network user is not occupied any more, the entrance bandwidth is saved to the maximum extent, the problem that the demand for the entrance bandwidth linearly increases along with the continuous increase of the service volume is solved, and meanwhile, the expansion of the service of an enterprise is facilitated.
It should be understood that the file transmission control method provided in the embodiment of the present application may be applied to devices capable of implementing file uploading and downloading services, such as a terminal device, a server, and the like. The terminal device may be a computer, a Personal Digital Assistant (PDA), a smart phone, a tablet computer, or the like; the server may specifically be an application server or a Web server, and when the server is deployed in actual application, the server may be an independent server or a cluster server.
To facilitate understanding of the technical solution provided in the embodiment of the present application, an application scenario of the file transfer control method provided in the embodiment of the present application is described below with reference to fig. 1.
Referring to fig. 1, fig. 1 is a schematic view of an application scenario of a file transfer control method provided in an embodiment of the present application. As shown in fig. 1, the application scenario includes: an application scenario 110 for an extranet user and an application scenario 120 for an intranet user; the application scenario 110 for the extranet user includes: terminal device 111 (i.e., the computer in the application scenario for the extranet user in fig. 1), terminal device 112 (i.e., the smartphone in the application scenario for the extranet user in fig. 1), and extranet server 113, where extranet server 113 is embodied as a cloud storage server; the application scenario 120 for the intranet user includes: terminal device 121 (i.e., the computer in the application scenario facing the intranet user in fig. 1), terminal device 122 (i.e., the smartphone in the application scenario facing the intranet user in fig. 1), and intranet server 123, where intranet server 123 is embodied as an intranet disk array; the extranet server 113 and the intranet server 123 may synchronously store the file uploaded by the terminal device through a synchronization mechanism.
In practical applications, the terminal device 111, the terminal device 112, the terminal device 121, and the terminal device 122 may all execute the file transmission control method provided in the embodiment of the present application, so as to implement uploading and downloading of files in a corresponding manner. When the terminal device 111 and the terminal device 112 receive a file transmission request of a file download type initiated by a user, the terminal device 111 and the terminal device 112 may preferentially enable an extranet download scene, and download a required file from the extranet server 113; when the terminal device 111 and the terminal device 112 receive a file transmission request of a file uploading type initiated by a user, the terminal device 111 and the terminal device 112 may preferentially start an external network uploading scene, upload a file to the external network server 113, and synchronize the file to the internal network server 123; when terminal device 121 and terminal device 122 receive a file transmission request of a file download type initiated by a user, terminal device 121 and terminal device 122 may start an intranet download scene, and download a required file from intranet server 123; when terminal device 121 and terminal device 122 receive a file transmission request of a file upload type initiated by a user, terminal device 121 and terminal device 122 may start an intranet upload scene, upload a file to intranet server 123, and synchronize the file to extranet server 113.
It should be noted that, in general, a user may initiate a file transfer request through a browser or an application program on a terminal device, and after receiving the file transfer request initiated by the user, the browser or the application program automatically determines a scenario enabled for the file transfer according to a user identifier and a request type identifier in the file transfer request.
It should be understood that the application scenario shown in fig. 1 is only an example, and in practical applications, each terminal device in fig. 1 may also be a server actually, that is, the server may also execute the file transfer control method provided in the embodiment of the present application, and no limitation is made to the application scenario of the file transfer control method provided in the embodiment of the present application here.
The following describes a file transfer control method provided by the present application by way of example.
Referring to fig. 2, fig. 2 is a schematic flowchart of a file transfer control method according to an embodiment of the present application; for convenience of description, the following embodiments are described with a terminal device as an execution subject, and it should be understood that the execution subject of the file transfer control method is not limited to the terminal device, and may be a device such as a server that has file uploading and downloading capabilities. As shown in fig. 2, the file transfer control method includes the steps of:
step 201: receiving a file transmission request, wherein the file transmission request carries a user identifier and a request type identifier.
When a user needs to upload or download a file through the terminal device, the user can correspondingly initiate a file transmission request through a browser or other application programs running on the terminal device. The file transmission request carries a user identifier and a request type identifier, wherein the user identifier can represent whether the user is an intranet user or a non-intranet user (namely, an extranet user), and the request type identifier can represent whether the file transmission request initiated by the user specifically requests to download a file or upload the file.
Specifically, when a user requests to download a file through a browser or an application program, the user can correspondingly select the file required by the user, and click a file download button on an interface, at this time, the browser or the application program correspondingly generates a file transmission request, and determines that the request type of the file transmission request is identified as the file download type, and meanwhile, the browser or the application program can also obtain information which can identify whether the user is an intranet user, such as a user account name, a network name used by the user, and the like, and the information is used as a user identifier and is added to the file transmission request.
Similarly, when a user requests to upload a file through a browser or an application program, the user can correspondingly select the file to be uploaded, and click a file upload button on an interface, at this time, the browser or the application program correspondingly generates a file transmission request, and determines that the request type of the file transmission request is the file upload type, and meanwhile, the browser or the application program can also obtain information which can identify whether the user is an intranet user, such as a user account name, a network name used by the user, and the like, and the information is used as a user identifier and is added to the file transmission request.
Step 202: under the condition that the request type identifier is a file downloading type, when the user identifier indicates that the user is an intranet user, starting an intranet local downloading scene, and downloading a required file from an intranet server; and when the user identification indicates that the user is not the intranet user, the extranet downloading scene is started preferentially, and the required file is downloaded from the extranet server.
Step 203: under the condition that the request type identifier is a file uploading type, when the user identifier represents that the user is an intranet user, starting an intranet local uploading scene, uploading the file to an intranet server and synchronizing the file to an extranet server; and when the user identification represents that the user is not the intranet user, preferentially starting an extranet uploading scene, uploading the file to an extranet server and synchronizing the file to the intranet server.
After receiving a file transmission request generated by a browser or an application program running by the terminal device, the terminal device determines which file transmission scene is opened for the file transmission request according to a request type identifier and a user identifier in the file transmission request.
Specifically, the terminal device may first determine whether the request type identifier in the file transmission request is a file download type or a file upload type; if the request type identifier is a file downloading type, executing step 202, namely, continuously judging whether the user identifier is an intranet user, if so, starting an intranet local downloading scene, downloading the required file from an intranet server, and if not, preferentially starting an extranet downloading scene, and downloading the required file from an extranet server; if the request type identifier is a file uploading type, step 203 is executed, that is, whether the user identifier is an intranet user is continuously judged, if yes, an intranet local uploading scene is started, the file is uploaded to an intranet server and synchronized to an extranet server, and if not, an extranet uploading scene is started preferentially, and the file is uploaded to an extranet server and synchronized to the intranet server.
In a possible implementation manner, if the terminal device determines that the user identifier in the file transmission request is an intranet user and the request type identifier in the file transmission request is a file downloading type, at this time, the terminal device may not directly start an extranet downloading scenario, but first determine a file transmission scenario to be finally started through the following steps:
the terminal equipment judges whether the external network function of the terminal equipment is started or not; when the external network function is started, further judging whether the file to be downloaded is stored in the external network server, if the file to be downloaded is stored in the external network server, starting an external network downloading scene, and downloading the required file from the external network server; otherwise, when the function of the external network is closed or the file to be downloaded is not stored in the external network server, the terminal equipment starts the local downloading scene of the internal network and downloads the required file from the internal network server.
Namely, under the condition that the external network function of the terminal equipment is started and the file to be downloaded is stored in the external network server, the terminal equipment starts an external network downloading scene and downloads the required file from the external network server; and under the condition that the external network function of the terminal equipment is closed and/or the file to be downloaded is not stored in the external network server, the terminal equipment starts an internal network downloading scene and downloads the required file from the internal network server. Therefore, before the external network downloading scene is started, the terminal equipment determines whether the external network downloading scene is started finally according to the use state of the external network function of the terminal equipment and the storage position of the file to be downloaded, and unnecessary processing resources are prevented from being wasted due to the fact that the external network downloading scene is started directly.
In a possible implementation manner, if the terminal device determines that the user identifier in the file transmission request is the non-intranet user and the request type identifier in the file transmission request is the file uploading type, at this time, the terminal device may not directly start the extranet uploading scenario, but first determine whether the file transmission scenario needs to be started or not through the following steps:
the terminal equipment can judge whether the external network function of the terminal equipment is started or not; when the external network function is started, selecting to start an external network uploading scene, uploading the file to an external network server and synchronizing the file to an internal network server; and when the external network function is closed, selecting to start an internal network local uploading scene, uploading the file to an internal network server and synchronizing the file to the external network server.
That is, when the external network function of the terminal device itself is turned on, the terminal device starts the external network upload scene, and when the external network function of the terminal device itself is not turned on, the terminal device starts the internal network upload scene. Therefore, before the external network uploading scene is started, the terminal equipment determines whether the external network uploading scene is started finally according to the using state of the external network function of the terminal equipment, and the situation that the external network uploading scene is directly started without being supported is avoided.
It should be noted that the extranet server may be specifically a cloud Storage server, for example, an Object Storage Service (OSS) which can effectively solve the problems of slow uploading and downloading speed of extranet users and large difference of access speeds of users in different regions; the intranet server may be an intranet disk array.
It should be noted that, what is introduced in the embodiments of the present application is mainly a selection manner of a file transmission scenario, and specific implementation manners of the intranet local download scenario, the extranet download scenario, the intranet local upload scenario, and the extranet upload scenario are described in the following embodiments, and refer to relevant contents in the following embodiments in detail.
The file transmission control method provides corresponding file uploading and downloading services for the extranet user and the intranet user respectively, namely when the extranet user uploads or downloads a file, an extranet uploading scene or an extranet downloading scene is started preferentially, the file uploaded by the extranet user is synchronized to the intranet server in the extranet uploading scene, when the intranet user uploads or downloads the file, an intranet local uploading scene or an intranet local downloading scene is started, and the file uploaded by the intranet user is synchronized to the extranet server in the intranet local uploading scene. Therefore, all files occupy the entrance bandwidth only when being uploaded, the external network user does not need to pass through the internal network server when downloading the files, accordingly, the entrance bandwidth of the external network user is not occupied any more, the entrance bandwidth is saved to the maximum extent, the problem that the demand for the entrance bandwidth linearly increases along with the continuous increase of the service volume is solved, and meanwhile, the expansion of the service of an enterprise is facilitated.
To facilitate further understanding of the file transmission control method shown in fig. 2, the following describes, with reference to fig. 3 and fig. 4, an implementation manner when the request type is identified as a file download type and an implementation manner when the request type is identified as a file upload type, respectively.
Referring to fig. 3, fig. 3 is a schematic flowchart of a process that the terminal device needs to execute when the request type is identified as the file download type, that is, a schematic flowchart of the file download method.
As shown in fig. 3, when a user initiates a file transmission request with a request type identifier of a file download type, the terminal device first determines whether the user is an intranet user according to the user identifier therein, and if so, directly starts an intranet local download scene. If not, continuing to judge whether the self external network function is started; if not, directly starting the local downloading scene of the internal network, if so, continuously judging whether the file to be downloaded is stored in the external network server, if so, starting the external network downloading scene, and if not, starting the local downloading scene of the internal network.
Referring to fig. 4, fig. 4 is a schematic flowchart of a process that the terminal device needs to execute when the request type is identified as the file upload type, that is, a schematic flowchart of the file upload method.
As shown in fig. 4, when a user initiates a file transmission request with a request type identifier of a file upload type, a terminal device first determines whether the user is an intranet user according to a user identifier therein, and if so, directly starts an intranet local upload scene. If not, whether the external network function of the user is started or not is continuously judged, if not, the local uploading scene of the internal network is started, and if yes, the external network uploading scene is started.
Specific implementation manners of the external network uploading scene, the external network downloading scene, the internal network local uploading scene and the internal network downloading scene are respectively introduced below through embodiments.
Referring to fig. 5, fig. 5 is a schematic flowchart of an extranet upload scenario provided in the embodiment of the present application. For convenience of description, the following embodiments are still described with a terminal device as an execution subject, and it should be understood that the execution subject of the method for uploading a file through an external network is not limited to the terminal device, and may also be a device such as a server and the like having a file uploading function. As shown in fig. 5, the extranet upload scenario includes the following steps:
step 501: and requesting an uploading file permission parameter to an intranet server, and receiving the uploading file permission parameter returned by the intranet server.
When the terminal device determines to start the external network uploading scenario, the terminal device may first request the internal network server for uploading the file permission parameter, and in response to the request initiated by the terminal device, the internal network server correspondingly returns the uploaded file permission parameter to the terminal device.
Step 502: and splicing and generating an uploading permission Uniform Resource Locator (URL) according to the uploading file permission parameters.
After receiving the uploading file permission parameter returned by the intranet server, the terminal equipment can call a browser or an application program which needs to initiate a file transmission request, and generates an uploading permission URL according to the uploading file permission parameter in a splicing mode.
Step 503: and uploading a first target file to the extranet server based on the uploading permission URL, instructing the extranet server to establish connection with the intranet server based on a callback path specified in the uploading permission URL, and synchronizing the first target file to the intranet server based on an asynchronous task.
And the terminal equipment uploads the file to be uploaded, namely the first target file, to the extranet server according to the uploading permission URL generated by splicing, and instructs the extranet server to establish connection with the intranet server based on the callback path specified in the uploading permission URL, so that the first target file is synchronously stored, namely, the extranet server and the intranet server both store the first target file.
During specific implementation, after receiving the first target file, the extranet server firstly sends a callback request to the intranet server through a callback path indicated in the uploading permission URL; after receiving the callback request, the intranet server correspondingly creates a file number aiming at the first target file, starts an asynchronous task for synchronizing the first target file, and then sends the created file number to the extranet server; and after receiving the file number, the extranet server sends the file number to the terminal equipment so as to inform the terminal equipment that the first target file is successfully uploaded.
After the intranet server starts an asynchronous task for synchronizing the first target file, the intranet server initiates a file acquisition request to the extranet server to request to acquire the first target file uploaded by the terminal equipment, correspondingly, the extranet server sends the first target file to the intranet server, and the intranet server updates a file synchronization result into file information.
It should be noted that the extranet server and the intranet server perform file synchronization through asynchronous tasks, and the background processing has elasticity and configurability, that is, any time period such as a network idle time period can be selected to perform file synchronization, and the file transmission rate can be correspondingly adjusted.
Therefore, the terminal equipment uploads the first target file to be uploaded to the external network server through the external network uploading scene and correspondingly synchronizes the first target file to the internal network server; the subsequent user can download the first target file from the corresponding server quickly no matter through an external network download scene or an internal network download scene, and the external network user does not occupy the entrance bandwidth when downloading the first target file, so that the entrance bandwidth is saved.
In order to further understand the extranet upload scenario shown in fig. 5, the extranet upload scenario shown in fig. 5 is described below with reference to fig. 6 from the perspective of interaction between the terminal device, the intranet server, and the extranet server. Referring to fig. 6, fig. 6 is an interaction signaling diagram of an extranet upload scenario provided in the embodiment of the present application.
As shown in fig. 6, after the user clicks the file upload button of the terminal device, if the terminal device determines that the external network upload scene is enabled, the terminal device will correspondingly request the upload permission parameter from the internal network server, and after the internal network server returns the upload permission parameter to the terminal device, the terminal device splices the upload permission parameter to generate an upload permission URL; uploading the first target file to an external network server based on the uploading permission URL, and after receiving the first target file, the external network server sends a callback request to an internal network server based on the uploading permission URL; the intranet server responds to the callback request, creates a file number and a file synchronization task, sends the file number to the extranet server, and the extranet server further sends the file number to the terminal equipment so as to inform the terminal equipment that the first target file is successfully uploaded; in a file synchronization task started by the intranet server, the intranet server requests to acquire a first target file from the extranet server, the extranet server correspondingly sends the first target file to the intranet server, and then the intranet server can update a file synchronization result.
Referring to fig. 7, fig. 7 is a schematic flowchart of an extranet download scenario provided in the embodiment of the present application. For convenience of description, the following embodiments are still described with the terminal device as the execution subject, and it should be understood that the execution subject of the method for downloading the scene download file via the external network is not limited to the terminal device, and may also be a device such as a server with a file download function. As shown in fig. 7, the extranet download scenario includes the following steps:
step 701: requesting a downloading authorization URL (uniform resource locator) to an intranet server, and receiving the downloading authorization URL returned by the intranet server, wherein the downloading authorization URL indicates that a second target file can be downloaded from an extranet server.
When the terminal equipment determines to start an external network downloading scene, the terminal equipment can request an internal network server for downloading an authorized URL through a browser or an application program which initiates a file transmission request; correspondingly, the intranet server responds to the request initiated by the terminal equipment and returns the download authorization URL to the terminal equipment, and the download authorization URL can indicate that the second target file required to be downloaded by the user is downloaded from the extranet server.
In specific implementation, after the terminal device selects the second target file to be downloaded, the terminal device may request the download authorization URL corresponding to the second target file from the intranet server according to the number of the second target file.
Step 702: and downloading the second target file from the external network server based on the downloading authorization URL.
And after the terminal equipment acquires the download authorization URL returned by the intranet server, requesting the extranet server to download a second target file according to the download authorization URL, and correspondingly, returning the second target file to the terminal equipment by the extranet server.
Therefore, the terminal equipment downloads the required second target file from the external network server through the external network downloading scene, and in the file downloading process, the enterprise entrance bandwidth is not occupied, so that the entrance bandwidth is saved.
In order to further understand the extranet download scenario shown in fig. 7, the extranet download scenario shown in fig. 7 will be described below with reference to fig. 8 from the perspective of interaction between the terminal device, the intranet server, and the extranet server. Referring to fig. 8, fig. 8 is an interaction signaling diagram of an extranet download scenario provided in the embodiment of the present application.
As shown in fig. 8, after the user clicks the file download button of the terminal device, if the terminal device determines to enable the external network download scenario, the terminal device will request the download authorization URL corresponding to the second target file from the internal network server according to the file number of the second target file that the user needs to download, and the internal network server correspondingly returns the download authorization URL to the terminal device; and then, the terminal equipment requests to download the second target file from the external network server according to the download authorization URL, and the external network server correspondingly sends the second target file to the terminal equipment to realize the successful download of the second target file.
Referring to fig. 9, fig. 9 is a schematic flow diagram of an intranet local upload scene provided in the embodiment of the present application. For convenience of description, the following embodiments are still described with a terminal device as an execution subject, and it should be understood that the execution subject of the method for uploading a scene locally through an intranet is not limited to the terminal device, and may also be a device such as a server and the like having a file uploading function. As shown in fig. 9, the local uploading scenario of the intranet includes the following steps:
step 901: uploading a first target file to be uploaded to an intranet server, enabling the intranet server to receive the first target file, generating a corresponding file number, and starting an asynchronous task to synchronize the first target file to an extranet server.
When the terminal equipment determines to start an intranet local uploading scene, the terminal equipment can select a first target file to be uploaded through a browser or an application program initiating a file transmission request, and uploads the first target file to an intranet server; after receiving the first target file, the intranet server creates a corresponding file number for the first target file correspondingly, and starts an asynchronous task for synchronizing the first target file to the extranet server.
After the intranet server starts an asynchronous task for synchronizing the first target file, the intranet server sends the first target file to the extranet server, and after the extranet server successfully receives the first target file, the extranet server returns a file sending result to the intranet server to indicate that the extranet server successfully receives the first target file, and correspondingly, the intranet server updates a file synchronization result.
Step 902: and receiving a file number corresponding to the first target file.
After the intranet server generates a file number for the first target file, the file number is correspondingly returned to the terminal device, so that the terminal device is informed that the first target file is successfully uploaded.
It should be noted that the intranet server and the extranet server perform file synchronization through asynchronous tasks, and the background processing has elasticity and configurability, that is, any time period such as a network idle time period can be selected to perform file synchronization, and the file transmission rate can be correspondingly adjusted.
Therefore, the terminal equipment uploads the first target file to be uploaded to an intranet server through the local intranet uploading scene and correspondingly synchronizes the first target file to an extranet server; the subsequent user can download the first target file from the corresponding server quickly no matter through an external network download scene or an internal network download scene, and the external network user does not occupy the entrance bandwidth when downloading the first target file, so that the entrance bandwidth is saved.
In order to further understand the intranet local upload scenario shown in fig. 9, the intranet local upload scenario shown in fig. 9 is described below with reference to fig. 10 from the perspective of interaction between the terminal device, the intranet server, and the extranet server. Referring to fig. 10, fig. 10 is an interactive signaling diagram of an intranet local upload scene provided in the embodiment of the present application.
As shown in fig. 10, after a user clicks a file upload button of a terminal device, if the terminal device determines that an intranet local upload scene is enabled, the terminal device correspondingly sends a first target file to be uploaded to an intranet server, the intranet server creates a file number corresponding to the first target file for the first target file, and an asynchronous task for synchronizing the first target file to an extranet server, and the intranet server sends the file number corresponding to the first target file to the terminal device to inform the terminal device that the first target file is successfully uploaded; after the intranet server starts the asynchronous task, the intranet server sends the first target file to the extranet server, the extranet server returns a sending result to the intranet server after successfully receiving the first target file, and the intranet server correspondingly updates a file synchronization result.
Referring to fig. 11, fig. 11 is a schematic flowchart of a local downloading scenario of an intranet according to an embodiment of the present application. For convenience of description, the following embodiments are still described with a terminal device as an execution subject, and it should be understood that the execution subject of the method for downloading a scene download file locally through an intranet is not limited to the terminal device, and may also be a device such as a server with a file download function. As shown in fig. 11, the local downloading scenario of the intranet includes the following steps:
step 1101: and sending a file acquisition request to the intranet server based on the file number of the second target file to be downloaded.
When the terminal device determines to start the local downloading scene of the intranet, the terminal device may initiate a file acquisition request to the intranet server through a browser or an application program initiating a file transmission request according to a file number of a second target file to be downloaded, so as to request to acquire the second target file from the intranet server.
Step 1102: and receiving a second target file returned by the intranet server.
After receiving the file acquisition request sent by the terminal equipment, the intranet server determines a second target file to be downloaded by the terminal equipment according to the file number in the file acquisition request, and returns the second target file to the terminal equipment.
Therefore, the terminal device downloads the required second target File from the intranet server through the intranet local downloading scene, and in the File downloading process, the File can be rapidly downloaded directly based on a high-speed intranet File Transfer Protocol (FTP) Protocol, and the enterprise access bandwidth cannot be occupied.
To facilitate further understanding of the intranet local download scenario shown in fig. 11, the intranet local download scenario shown in fig. 12 will be described below with reference to fig. 12 from the perspective of interaction between the terminal device, the intranet server, and the extranet server. Referring to fig. 12, fig. 12 is an interactive signaling diagram of an intranet local download scene provided in the embodiment of the present application.
As shown in fig. 12, after the user clicks the file download button of the terminal device, if the terminal device determines to start the local intranet download scene, the terminal device requests the intranet server to obtain a second target file according to the file number of the second target file that the user needs to download; correspondingly, the intranet server responds to the file acquisition request sent by the terminal equipment, and sends the second target file to the terminal equipment, so that the successful downloading of the second target file is realized.
Aiming at the file transmission control method described above, the application also provides a corresponding file transmission control device, so that the file transmission control method can be applied and realized in practice.
Referring to fig. 13, fig. 13 is a schematic structural diagram of a file transfer control apparatus 1300 corresponding to the file transfer control method shown in fig. 2, where the file transfer control apparatus 1300 includes:
a receiving unit 1301, configured to receive a file transmission request, where the file transmission request carries a user identifier and a request type identifier;
a first downloading unit 1302, configured to, when the request type identifier is a file downloading type and the user identifier indicates that the user is an intranet user, start an intranet local downloading scene, and download the required file from an intranet server;
a second downloading unit 1303, configured to, when the request type identifier is a file downloading type and the user identifier indicates that the user is not an intranet user, preferentially start an extranet downloading scene, and download the required file from the extranet server;
a first uploading unit 1304, configured to, when the request type identifier is a file uploading type and the user identifier indicates that the user is an intranet user, start an intranet local uploading scenario, upload a file to an intranet server, and synchronize the file to an extranet server;
a second uploading unit 1305, configured to, when the request type identifier is a file uploading type and the user identifier indicates that the user is not an intranet user, preferentially enable an extranet uploading scenario, upload a file to an extranet server, and synchronize the file to the intranet server.
Optionally, the second uploading unit 1305 is further configured to:
judging whether the function of the external network is started or not;
when the function of the external network is started, starting an external network uploading scene, uploading the file to an external network server and synchronizing the file to an internal network server;
and when the function of the external network is closed, starting a local uploading scene of the internal network, uploading the file to the internal network server and synchronizing the file to the external network server.
Optionally, the second uploading unit 1305 is further configured to:
requesting an uploading file permission parameter to an intranet server, and receiving the uploading file permission parameter returned by the intranet server;
splicing and generating an uploading permission URL according to the uploading file permission parameters;
and uploading a first target file to the extranet server based on the uploading permission URL, instructing the extranet server to establish connection with the intranet server based on a callback path specified in the uploading permission URL, and synchronizing the first target file to the intranet server based on an asynchronous task.
Optionally, the second downloading unit 1303 is further configured to:
judging whether the function of the external network is started or not;
when the external network function is started, judging whether a file to be downloaded is stored in an external network server;
when a second target file to be downloaded is stored in the external network server, starting an external network downloading scene, and downloading the second target file from the external network server;
and when the function of the external network is closed or the second target file is not stored in the external network server, starting an internal network local downloading scene, and downloading the second target file from the internal network server.
Optionally, the second downloading unit 1303 is further configured to:
requesting a download authorization URL (uniform resource locator) from an intranet server, and receiving the download authorization URL returned by the intranet server, wherein the download authorization URL indicates that the second target file can be downloaded from an extranet server;
and downloading the second target file from the external network server based on the downloading authorization URL.
Optionally, the first downloading unit 1302 is configured to:
sending a file acquisition request to an intranet server based on the file number of a second target file to be downloaded;
and receiving a second target file returned by the intranet server.
Optionally, the first uploading unit 1304 is configured to:
uploading a first target file to be uploaded to an intranet server, enabling the intranet server to receive the first target file, generating a corresponding file number, and starting an asynchronous task to synchronize the first target file to an extranet server.
The file transmission control device respectively provides corresponding file uploading and downloading services for the extranet user and the intranet user, namely, when the extranet user uploads or downloads a file, an extranet uploading scene or an extranet downloading scene is preferentially started, the file uploaded by the extranet user is synchronized to the intranet server in the extranet uploading scene, when the intranet user uploads or downloads the file, an intranet local uploading scene or an intranet local downloading scene is started, and the file uploaded by the intranet user is synchronized to the extranet server in the intranet local uploading scene. Therefore, all files occupy the entrance bandwidth only when being uploaded, the external network user does not need to pass through the internal network server when downloading the files, accordingly, the entrance bandwidth of the external network user is not occupied any more, the entrance bandwidth is saved to the maximum extent, the problem that the demand for the entrance bandwidth linearly increases along with the continuous increase of the service volume is solved, and meanwhile, the expansion of the service of an enterprise is facilitated.
The present application further provides a device for controlling file transmission, where the device may specifically be a server, see fig. 14, and fig. 14 is a schematic structural diagram of a server for polling advertisement inventory according to an embodiment of the present application. The server 1400 may vary widely by configuration or performance, and may include one or more Central Processing Units (CPUs) 1422 (e.g., one or more processors) and memory 1432, one or more storage media 1430 (e.g., one or more mass storage devices) that store applications 1442 or data 1444. Memory 1432 and storage media 1430, among other things, may be transient or persistent storage. The program stored on storage medium 1430 may include one or more modules (not shown), each of which may include a sequence of instructions operating on a server. Still further, a central processor 1422 may be disposed in communication with storage medium 1430 for executing a series of instruction operations on storage medium 1430 on server 1400.
The server 1400 may also include one or more power supplies 1426, one or more wired or wireless network interfaces 1450, one or more input-output interfaces 1458, and/or one or more operating systems 1441, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
The steps performed by the server in the above embodiment may be based on the server structure shown in fig. 14.
Receiving a file transmission request, wherein the file transmission request carries a user identifier and a request type identifier;
under the condition that the request type identifier is a file downloading type, when the user identifier indicates that the user is an intranet user, starting an intranet local downloading scene, and downloading a required file from an intranet server; when the user identification represents that the user is not the intranet user, the extranet downloading scene is started preferentially, and the required file is downloaded from the extranet server;
under the condition that the request type identifier is a file uploading type, when the user identifier represents that the user is an intranet user, starting an intranet local uploading scene, uploading the file to an intranet server and synchronizing the file to an extranet server; and when the user identification represents that the user is not the intranet user, preferentially starting an extranet uploading scene, uploading the file to an extranet server and synchronizing the file to the intranet server.
Optionally, the CPU1422 may further execute the method steps of any specific implementation manner of the file transfer control method in the embodiment of the present application.
The embodiment of the application also provides another device for controlling file transmission, and the device can be specifically a terminal device. As shown in fig. 15, for convenience of explanation, only the portions related to the embodiments of the present application are shown, and details of the technology are not disclosed, please refer to the method portion of the embodiments of the present application. The terminal may be any terminal device including a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a Point of Sales (POS), a vehicle-mounted computer, and the like, taking the terminal as the mobile phone as an example:
fig. 15 is a block diagram illustrating a partial structure of a mobile phone related to a terminal provided in an embodiment of the present application. Referring to fig. 15, the cellular phone includes: radio Frequency (RF) circuit 1510, memory 1520, input unit 1530, display unit 1540, sensor 1550, audio circuit 1560, wireless fidelity (WiFi) module 1070, processor 1580, and power supply 1590; the input unit 1530 includes an input panel 1531 and other input devices 1532, the display unit 1540 includes a display panel 1541, and the audio circuit 1560 includes a speaker 1561 and a microphone 1562.
Those skilled in the art will appreciate that the handset configuration shown in fig. 15 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
In this embodiment, the processor 1580 included in the terminal has the following functions:
receiving a file transmission request, wherein the file transmission request carries a user identifier and a request type identifier;
under the condition that the request type identifier is a file downloading type, when the user identifier indicates that the user is an intranet user, starting an intranet local downloading scene, and downloading a required file from an intranet server; when the user identification represents that the user is not the intranet user, the extranet downloading scene is started preferentially, and the required file is downloaded from the extranet server;
under the condition that the request type identifier is a file uploading type, when the user identifier represents that the user is an intranet user, starting an intranet local uploading scene, uploading the file to an intranet server and synchronizing the file to an extranet server; and when the user identification represents that the user is not the intranet user, preferentially starting an extranet uploading scene, uploading the file to an extranet server and synchronizing the file to the intranet server.
Optionally, the processor 1580 may further execute method steps of any specific implementation manner of the file transfer control method in this embodiment.
The embodiment of the present application further provides a computer-readable storage medium for storing a program code, where the program code is configured to execute any one implementation manner of a file transfer control method described in the foregoing embodiments.
The present application further provides a computer program product including instructions, which when run on a computer, causes the computer to execute any one of the implementation manners of the file transfer control method described in the foregoing embodiments.
An embodiment of the present application further provides a file transfer system, including: the system comprises terminal equipment, an intranet server and an extranet server; the terminal device is used for executing the file transmission method provided by the embodiment of the application, and the intranet server and the extranet server are used for synchronously storing the files uploaded by the user through the terminal device and providing file downloading service for the user.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and 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 units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims (16)

1. A file transfer control method, comprising:
receiving a file transmission request, wherein the file transmission request carries a user identifier and a request type identifier;
under the condition that the request type identifier is a file downloading type, when the user identifier indicates that the user is an intranet user, starting an intranet local downloading scene, and downloading a required file from an intranet server; when the user identification represents that the user is not the intranet user, the extranet downloading scene is started preferentially, and the required file is downloaded from the extranet server;
under the condition that the request type identifier is a file uploading type, when the user identifier represents that the user is an intranet user, starting an intranet local uploading scene, uploading the file to an intranet server and synchronizing the file to an extranet server; when the user identification represents that the user is not the intranet user, an extranet uploading scene is started preferentially, and the file is uploaded to an extranet server and synchronized to the intranet server;
the preferentially-started external network uploading scene uploads the file to an external network server and synchronizes the file to an internal network local server, and the method comprises the following steps:
judging whether the function of the external network is started or not;
when the function of the external network is started, starting an external network uploading scene, uploading the file to an external network server and synchronizing the file to an internal network server;
and when the function of the external network is closed, starting a local uploading scene of the internal network, uploading the file to the internal network server and synchronizing the file to the external network server.
2. The method of claim 1, wherein enabling the extranet upload scenario, uploading a file to an extranet server and synchronizing to an intranet server, comprises:
requesting an uploading file permission parameter to an intranet server, and receiving the uploading file permission parameter returned by the intranet server;
splicing and generating an uploading permission URL according to the uploading file permission parameters;
and uploading a first target file to the extranet server based on the uploading permission URL, instructing the extranet server to establish connection with the intranet server based on a callback path specified in the uploading permission URL, and synchronizing the first target file to the intranet server based on an asynchronous task.
3. The method according to claim 1, wherein when the user identifier indicates that the user is not an intranet user, the external network downloading scenario is preferentially enabled, and the downloading of the required file from the external network server includes:
judging whether the function of the external network is started or not;
when the external network function is started, judging whether a file to be downloaded is stored in an external network server;
when the file to be downloaded is stored in the external network server, starting an external network downloading scene, and downloading the required file from the external network server;
and when the function of the external network is closed or the file to be downloaded is not stored in the external network server, starting the local downloading scene of the internal network, and downloading the required file from the internal network server.
4. The method of claim 1 or 3, wherein the enabling of the extranet download scenario, downloading the required file from the extranet server, comprises:
requesting a download authorization URL (uniform resource locator) from an intranet server, and receiving the download authorization URL returned by the intranet server, wherein the download authorization URL indicates that a second target file can be downloaded from an extranet server;
and downloading the second target file from the external network server based on the downloading authorization URL.
5. The method according to any one of claims 1 to 3, wherein the enabling of the intranet local download scene to download the required file from the intranet server comprises:
sending a file acquisition request to an intranet server based on the file number of a second target file to be downloaded;
and receiving a second target file returned by the intranet server.
6. The method according to any one of claims 1 to 3, wherein the enabling of the intranet local upload scene, uploading a file to an intranet server and synchronizing to an extranet server, comprises:
uploading a first target file to be uploaded to an intranet server, enabling the intranet server to receive the first target file, generating a corresponding file number, and starting an asynchronous task to synchronize the first target file to an extranet server.
7. The method of claim 1, wherein the extranet server is a cloud storage server.
8. A file transfer control apparatus, comprising:
the device comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving a file transmission request which carries a user identifier and a request type identifier;
the first downloading unit is used for starting an intranet local downloading scene and downloading a required file from an intranet server when the user identifier represents that the user is an intranet user under the condition that the request type identifier is a file downloading type;
the second downloading unit is used for preferentially starting an external network downloading scene and downloading the required file from the external network server when the user identifier represents that the user is not the internal network user under the condition that the request type identifier is the file downloading type;
the first uploading unit is used for starting an intranet local uploading scene when the user identifier represents that the user is an intranet user under the condition that the request type identifier is a file uploading type, uploading the file to an intranet server and synchronizing the file to an extranet server;
the second uploading unit is used for preferentially starting an external network uploading scene when the user identifier represents that the user is not an intranet user under the condition that the request type identifier is a file uploading type, uploading the file to an external network server and synchronizing the file to the intranet server;
the second uploading unit is further configured to:
judging whether the function of the external network is started or not;
when the function of the external network is started, starting an external network uploading scene, uploading the file to an external network server and synchronizing the file to an internal network server;
and when the function of the external network is closed, starting a local uploading scene of the internal network, uploading the file to the internal network server and synchronizing the file to the external network server.
9. The apparatus of claim 8, wherein the second uploading unit is further configured to:
requesting an uploading file permission parameter to an intranet server, and receiving the uploading file permission parameter returned by the intranet server;
splicing and generating an uploading permission URL according to the uploading file permission parameters;
and uploading a first target file to the extranet server based on the uploading permission URL, instructing the extranet server to establish connection with the intranet server based on a callback path specified in the uploading permission URL, and synchronizing the first target file to the intranet server based on an asynchronous task.
10. The apparatus of claim 8, wherein the second downloading unit is further configured to:
judging whether the function of the external network is started or not;
when the external network function is started, judging whether a file to be downloaded is stored in an external network server;
when a second target file to be downloaded is stored in the external network server, starting an external network downloading scene, and downloading the second target file from the external network server;
and when the function of the external network is closed or the second target file is not stored in the external network server, starting an internal network local downloading scene, and downloading the second target file from the internal network server.
11. The apparatus of claim 8, wherein the second downloading unit is further configured to:
requesting a download authorization URL (uniform resource locator) from an intranet server, and receiving the download authorization URL returned by the intranet server, wherein the download authorization URL indicates that a second target file can be downloaded from an extranet server;
and downloading the second target file from the external network server based on the downloading authorization URL.
12. The apparatus according to any one of claims 8 to 11, wherein the first downloading unit is configured to:
sending a file acquisition request to an intranet server based on the file number of a second target file to be downloaded;
and receiving a second target file returned by the intranet server.
13. The apparatus according to any one of claims 8 to 11, wherein the first uploading unit is configured to:
uploading a first target file to be uploaded to an intranet server, enabling the intranet server to receive the first target file, generating a corresponding file number, and starting an asynchronous task to synchronize the first target file to an extranet server.
14. A file transfer system, comprising:
the system comprises terminal equipment, an intranet server and an extranet server;
the terminal device executes the method of any one of the preceding claims 1 to 7 by running a computer program;
the intranet server and the extranet server are used for synchronously storing files uploaded by the user through the terminal equipment and providing file downloading service for the user.
15. A file transfer device, the device comprising a processor and a memory:
the memory is used for storing a computer program;
the processor is configured to execute the computer program to perform the method of any one of claims 1 to 7.
16. A computer-readable storage medium, characterized in that the computer-readable storage medium is used to store a computer program for performing the method of any of claims 1 to 7.
CN201910381352.9A 2019-05-08 2019-05-08 File transmission control method, device, equipment and storage medium Active CN110247951B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910381352.9A CN110247951B (en) 2019-05-08 2019-05-08 File transmission control method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910381352.9A CN110247951B (en) 2019-05-08 2019-05-08 File transmission control method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN110247951A CN110247951A (en) 2019-09-17
CN110247951B true CN110247951B (en) 2022-04-01

Family

ID=67883842

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910381352.9A Active CN110247951B (en) 2019-05-08 2019-05-08 File transmission control method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN110247951B (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110881062A (en) * 2019-10-18 2020-03-13 平安科技（深圳）有限公司 File transmission method, device, equipment and storage medium based on big data
CN111355791B (en) * 2020-02-25 2021-12-03 腾讯科技（深圳）有限公司 File transmission method and device, computer equipment and storage medium
CN111478943A (en) * 2020-03-06 2020-07-31 上海数据交易中心有限公司 Cross-local area network file storage method and system, storage medium and terminal
CN112165515A (en) * 2020-09-17 2021-01-01 国义招标股份有限公司 File storage method and system based on cloud server
CN112492035B (en) * 2020-11-30 2023-10-27 维沃移动通信有限公司 File transmission method and device and electronic equipment
CN113704781B (en) * 2021-07-23 2023-05-26 平安银行股份有限公司 File secure transmission method and device, electronic equipment and computer storage medium

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102347946A (en) * 2011-09-22 2012-02-08 中铁信安(北京)信息安全技术有限公司 Terminal type interactive link platform system framework and realization method thereof
CN102780779A (en) * 2012-07-23 2012-11-14 北京星网锐捷网络技术有限公司 Gateway equipment and method and device for optimization of campus network export P2P (peer-to-peer) traffic
CN104702706A (en) * 2013-12-04 2015-06-10 中国移动通信集团公司 Method and device for acquiring DNS messages
CN105635123A (en) * 2015-12-24 2016-06-01 北京恒华伟业科技股份有限公司 Method for obtaining external network resource in internal network, internal and external network servers and system
CN105898802A (en) * 2016-03-25 2016-08-24 西安电子科技大学 Cluster-based caching cooperation and sharing method in heterogeneous wireless network
CN108551476A (en) * 2018-03-27 2018-09-18 深圳市创智成科技股份有限公司 A kind of control method and system for realizing file transmission
CN109005189A (en) * 2018-08-27 2018-12-14 广东电网有限责任公司信息中心 A kind of access transmission platform suitable for double net isolation
CN109167820A (en) * 2018-08-13 2019-01-08 彩讯科技股份有限公司 A kind of method for down loading of application program, device, storage medium and terminal

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102347946A (en) * 2011-09-22 2012-02-08 中铁信安(北京)信息安全技术有限公司 Terminal type interactive link platform system framework and realization method thereof
CN102780779A (en) * 2012-07-23 2012-11-14 北京星网锐捷网络技术有限公司 Gateway equipment and method and device for optimization of campus network export P2P (peer-to-peer) traffic
CN104702706A (en) * 2013-12-04 2015-06-10 中国移动通信集团公司 Method and device for acquiring DNS messages
CN105635123A (en) * 2015-12-24 2016-06-01 北京恒华伟业科技股份有限公司 Method for obtaining external network resource in internal network, internal and external network servers and system
CN105898802A (en) * 2016-03-25 2016-08-24 西安电子科技大学 Cluster-based caching cooperation and sharing method in heterogeneous wireless network
CN108551476A (en) * 2018-03-27 2018-09-18 深圳市创智成科技股份有限公司 A kind of control method and system for realizing file transmission
CN109167820A (en) * 2018-08-13 2019-01-08 彩讯科技股份有限公司 A kind of method for down loading of application program, device, storage medium and terminal
CN109005189A (en) * 2018-08-27 2018-12-14 广东电网有限责任公司信息中心 A kind of access transmission platform suitable for double net isolation

Also Published As

Publication number Publication date
CN110247951A (en) 2019-09-17

Similar Documents

Publication Publication Date Title
CN110247951B (en) File transmission control method, device, equipment and storage medium
US20210297506A1 (en) Method, User Equipment, Server, and Apparatus for Implementing Information Sharing
AU2018220050B2 (en) Enforcing policies based on information received from external systems
CN106095458B (en) The management method and device of plug-in unit in a kind of application program
CN102819461A (en) Desktop synchronization method, device, equipment and system
CN113259161B (en) Application management method and device, electronic equipment and storage medium
CN105812435B (en) Application upgrading data packet processing method and device, electronic equipment and system
KR102441236B1 (en) Software update management method, server, terminal, device, and storage medium
CN113568884A (en) File management method and device, electronic equipment and storage medium
US12003969B2 (en) Postponed eSIM delivery to secondary mobile wireless device for cellular wireless service subscription
US20140258703A1 (en) Adaptive data synchronization
WO2019184658A1 (en) Profile switching method and apparatus, and mobile terminal
US20230217363A1 (en) Method for switching a Network slice, terminal, storage medium and electronic device
CN112969209B (en) Switching control method and device of service server, electronic equipment and storage medium
CN105389175A (en) Application program sharing method and mobile terminal
CN112969208B (en) Service server switching control method and device, electronic equipment and storage medium
WO2017166906A1 (en) Method of managing euicc subscription profile and associated apparatus
CN113596175A (en) Scene synchronization method, terminal, server and system
US10805427B1 (en) Backup and restore of customer devices
WO2018063949A1 (en) Providing network resource access based on a purpose identifier
CN108540519B (en) Balanced download control method and device
CN110049360B (en) Cross-platform content control method, device, terminal, server and storage medium
CN113825120B (en) Cellular service management for assisted mobile wireless devices
CN110661857B (en) Data synchronization method and device
WO2016188078A1 (en) Method and apparatus for networking subscriber identity module

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