CN112351109A - Accessory processing method and device - Google Patents
Accessory processing method and device Download PDFInfo
- Publication number
- CN112351109A CN112351109A CN202011362015.4A CN202011362015A CN112351109A CN 112351109 A CN112351109 A CN 112351109A CN 202011362015 A CN202011362015 A CN 202011362015A CN 112351109 A CN112351109 A CN 112351109A
- Authority
- CN
- China
- Prior art keywords
- attachment
- request
- cache server
- server
- accessory
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title abstract description 8
- 238000000034 method Methods 0.000 claims description 25
- 230000002452 interceptive effect Effects 0.000 claims description 6
- 238000012546 transfer Methods 0.000 claims description 6
- 230000005540 biological transmission Effects 0.000 description 3
- 101001094649 Homo sapiens Popeye domain-containing protein 3 Proteins 0.000 description 2
- 101000608234 Homo sapiens Pyrin domain-containing protein 5 Proteins 0.000 description 2
- 101000578693 Homo sapiens Target of rapamycin complex subunit LST8 Proteins 0.000 description 2
- 102100027802 Target of rapamycin complex subunit LST8 Human genes 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses an attachment processing method and device, wherein a server arranged in a headquarter is defined as a central server under a framework of a centralized deployment attachment storage system, and in the embodiment, corresponding cache servers are arranged at nodes of each province. The cache server firstly receives a first request sent by first user equipment, wherein the first request is used for requesting a first attachment, and the first request carries a storage address of the first attachment in a central server. After receiving the first request, the cache server determines whether the cache server includes the first attachment, and if the cache server includes the first attachment, the cache server directly obtains the first attachment from the cache server after receiving the first request which is sent by the first user equipment and carries a storage address of the first attachment in a central server, and then sends the first attachment to the first user equipment.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to an accessory processing method and apparatus.
Background
Currently, the deployment architecture of an accessory storage system is generally divided into two types, one type is distributed deployment, namely, servers for storing accessories are deployed in provincial nodes all over the country, and a user sends an accessory request to the provincial node servers; one is centralized deployment, which means that a server storing attachments is deployed in the headquarters, and users directly send requests for attachments to the headquarters server. Because centralized deployment facilitates unified operation and maintenance and centralized storage of the system, and the requirement on hardware resources is low, the deployment architecture will be a preferred scheme of future deployment architectures. However, when the system is deployed in a centralized manner, because the accessory requests of each province are all sent to the headquarters, a large amount of data transmission exists, and the link bandwidth from each province node to the headquarters node generates a large pressure, which may cause network congestion and collapse, and bring a bad experience to users.
Therefore, a solution to solve the above problems is urgently needed.
Disclosure of Invention
The technical problem to be solved by the application is to provide an attachment processing method to solve the problem that when a server is deployed in a headquarters under a current architecture for intensively deploying an attachment storage system, link bandwidth pressure from each provincial node to a headquarters node is large, network congestion is likely to collapse, and bad experience is likely to be brought to a user.
In a first aspect, an embodiment of the present application provides an attachment processing method, which is executed by a cache server, and the method includes:
receiving a first request sent by first user equipment, wherein the first request is used for requesting a first accessory, and the first request carries a storage address of the first accessory in a central server;
determining whether the first attachment is included in the cache server;
and if the cache server comprises the first attachment, acquiring the first attachment from the cache server, and sending the first attachment to the first user equipment.
Optionally, the determining whether the cache server includes the first attachment includes:
determining an identity of the first accessory;
determining whether the first attachment is included in the cache server according to the identification of the first attachment.
Optionally, the determining the identifier of the first accessory includes:
determining the identifier of the first accessory according to the corresponding relation between the locally stored storage address and the identifier of the first accessory, wherein the corresponding relation is stored after the cache server receives the identifier of the first accessory sent by the central server for the first time; alternatively, the first and second electrodes may be,
sending a second request to the central server, wherein the second request comprises the storage address, and the second request is used for requesting the identifier of the first attachment;
and receiving the identification of the first attachment sent by the central server.
Optionally, the method further includes:
if the cache server does not comprise the first attachment, sending the first request to the central server;
receiving the first attachment sent by the central server;
sending the first attachment to the first user device.
Optionally, the method further includes:
storing the first attachment.
Optionally, the method further includes:
receiving a third request sent by a second user device, wherein the third request is used for requesting the first attachment, the third request carries a storage address of the first attachment in a central server, and the time for receiving the first request by the cache server is the same as the time for receiving the third request by the cache server;
and acquiring the first attachment from the cache server, and sending the first attachment to the second user equipment.
Optionally, the first attachment is a mail attachment.
Optionally, the first request is a request based on a hypertext transfer protocol HTTP, or a request based on a third version post office protocol POP3, or a request based on an interactive mail access protocol IMAP.
Optionally, the cache server is: nginx.
In a second aspect, an embodiment of the present application provides an attachment processing apparatus, which is executed by a cache server, and includes:
a first receiving module to: receiving a first request sent by first user equipment, wherein the first request is used for requesting a first accessory, and the first request carries a storage address of the first accessory in a central server;
a determination module to: determining whether the first attachment is included in the cache server;
a first sending module configured to: and if the cache server comprises the first attachment, acquiring the first attachment from the cache server, and sending the first attachment to the first user equipment.
Optionally, the determining module is configured to:
determining an identity of the first accessory;
determining whether the first attachment is included in the cache server according to the identification of the first attachment.
Optionally, the determining module is configured to:
determining the identifier of the first accessory according to the corresponding relation between the locally stored storage address and the identifier of the first accessory, wherein the corresponding relation is stored after the cache server receives the identifier of the first accessory sent by the central server for the first time; alternatively, the first and second electrodes may be,
sending a second request to the central server, wherein the second request comprises the storage address, and the second request is used for requesting the identifier of the first attachment;
and receiving the identification of the first attachment sent by the central server.
Optionally, the apparatus further comprises:
a second sending module, configured to: if the cache server does not comprise the first attachment, sending the first request to the central server;
a second receiving module to: receiving the first attachment sent by the central server;
a third sending module, configured to: sending the first attachment to the first user device.
Optionally, the apparatus further includes a storage module configured to store the first accessory.
Optionally, the apparatus further comprises:
a third receiving module, configured to: receiving a third request sent by a second user device, wherein the third request is used for requesting the first attachment, the third request carries a storage address of the first attachment in a central server, and the time for receiving the first request by the cache server is the same as the time for receiving the third request by the cache server;
a fourth sending module, configured to: and acquiring the first attachment from the cache server, and sending the first attachment to the second user equipment.
Optionally, the first attachment is a mail attachment.
Optionally, the first request is a request based on a hypertext transfer protocol HTTP, or a request based on a third version post office protocol POP3, or a request based on an interactive mail access protocol IMAP.
Optionally, the cache server is: nginx.
Compared with the prior art, the embodiment of the application has the following advantages:
the embodiment of the application provides an attachment processing method, wherein a server arranged in a headquarter is defined as a central server under a framework of a centralized deployment attachment storage system, and in the embodiment, corresponding cache servers are arranged at nodes of each province. The cache server firstly receives a first request sent by first user equipment, wherein the first request is used for requesting a first attachment, and the first request carries a storage address of the first attachment in a central server. After receiving the first request, the cache server determines whether the cache server includes the first attachment, and if the cache server includes the first attachment, the cache server directly acquires the first attachment from the cache server without sending the first request to the central server, and sends the first attachment to the first user equipment. Therefore, if the cache server comprises the first accessory, the cache server can directly acquire the first accessory from the cache server after receiving the first request which is sent by the first user equipment and carries the storage address of the first accessory in the central server, and then send the first accessory to the first user equipment.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a schematic flow chart illustrating an attachment handling method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of an accessory handling 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 inventor of the present application finds, through research, that, currently, in a framework in which an accessory storage system is deployed in a centralized manner, because accessory requests of respective provinces are all sent to a headquarters, a large amount of data transmission exists, and link bandwidths from nodes of respective provinces to a headquarters node generate a large pressure, which may possibly cause network congestion collapse, and user experience is poor.
In order to solve the above problem, in the embodiment of the present application, a corresponding cache server is set at each provincial node. The cache server firstly receives a first request sent by first user equipment, wherein the first request is used for requesting a first attachment, and the first request carries a storage address of the first attachment in a central server. After receiving the first request, the cache server determines whether the cache server includes the first attachment, and if the cache server includes the first attachment, the cache server directly acquires the first attachment from the cache server without sending the first request to the central server, and sends the first attachment to the first user equipment. Therefore, if the cache server comprises the first accessory, the cache server can directly acquire the first accessory from the cache server after receiving the first request which is sent by the first user equipment and carries the storage address of the first accessory in the central server, and then send the first accessory to the first user equipment.
Exemplary method
Referring to fig. 1, a flowchart of an attachment processing method in an embodiment of the present application is shown. The method shown in fig. 1 is performed by a cache server.
In the present embodiment, the method shown in FIG. 1 can be implemented, for example, by the following steps S101-S103.
S101: receiving a first request sent by first user equipment, wherein the first request is used for requesting a first attachment, and the first request carries a storage address of the first attachment in a central server.
In this embodiment, the first user equipment may be, for example, a mobile terminal such as a smart phone and a tablet computer, or may be a desktop computer. The first attachment may be, for example, a mail attachment, and the first request may be, for example, a hypertext Transfer Protocol (HTTP) -based request; the first request may be a request based on Post Office Protocol 3 (POP 3) or an Interactive Mail Access Protocol (IMAP). The cache server is arranged at each provincial node, and can be a nginx server, for example.
Considering that the access amount of attachments in a province can be huge, it may be difficult to bear the access service of the attachments in the province by only setting one cache server in one province, so that the cache servers can be multiple in one province node. When a plurality of cache servers are arranged in one provincial node, in order to enable an attachment request sent by user equipment to be distributed to an idle cache server, a load balancing device can be arranged, and the load balancing device is used for distributing a mail attachment request sent by the user equipment, namely the first request to the idle cache server.
It is to be understood that, in a specific implementation, the first user device may first access the load balancing device, and the load balancing device sends the first request sent by the first user device to an idle cache server. In order to enable the first user equipment to access the load balancing equipment, the first request sent by the first user equipment may find an address of the load balancing equipment, for example, through domain name resolution. The domain name resolution process of the first request sent by the first user equipment is as follows: first, a local Domain Name Server (DNS) forwards the received first request sent by the first user equipment to an authorized DNS, where the authorized DNS is configured by a system and is used to find a local area network of a location node where the first user equipment is located and a cache Server is located according to the first request, and send an address of the DNS in the local area network to the local DNS, and for convenience of description, a DNS address in the local area network where the cache Server is located and sent to the local DNS is defined as an address of an intelligent DNS. After the authorized DNS sends the address of the intelligent DNS to the local DNS, the local DNS can access the intelligent DNS based on the address of the intelligent DNS, then the intelligent DNS can send an Internet Protocol address (Internet Protocol address, IP address) of a load balancing device in a network where the intelligent DNS is located to the local DNS, and finally, the local DNS returns the IP address of the load balancing device to the first user device, and the first user device accesses the load balancing device based on the IP address of the load balancing device.
In this embodiment, after receiving the first request sent by the first user equipment, the load balancing device may send the first request to an idle cache server connected to the load balancing device.
S102: determining whether the first attachment is included in the cache server.
In order to reduce the link bandwidth pressure from each provincial node to the headquarters node, if the cache server includes the first attachment, the cache server may directly acquire the first attachment from the cache server after receiving the first request, and the first user equipment may acquire the first attachment without downloading from the central server. Therefore, in this embodiment, after receiving the first request for requesting the first attachment sent by the first user equipment, the cache server may first determine whether the cache server includes the first attachment.
In this embodiment, it is considered that the first request received by the cache server carries an address of the first attachment in the central server, and the cache server cannot determine whether the first attachment is included in the cache server according to the address in the central server. Thus, to determine whether the first attachment is included in the cache server, an identification of the first attachment is first determined, and then a determination is made as to whether the first attachment is included in the cache server based on the identification of the first attachment.
In one example, the cache server may send a second request to the central server. Wherein the second request includes a storage address of the first attachment in the central server, and the second request is used for requesting an identifier of the first attachment.
It should be noted that, in order to ensure that the cache server has the right to access the central server, in a possible implementation manner, before sending the second request to the central server, the cache server may first send an authentication request to an authentication server, after receiving the authentication request to the cache server, the authentication server authenticates the cache server, if the cache server has the right to access the central server, the authentication server sends an authentication passing instruction to the cache server, and the cache server can continue to access the central server, otherwise, the cache server cannot access the central server. The authentication server authenticates the cache server, so that the cache server without access authority can be prevented from communicating with the central server, the link bandwidth pressure from each provincial node to the headquarter node is reduced, and network congestion is reduced.
It can be understood that, when there are too many user equipments requesting the first attachment, if the cache server requests the identifier of the first attachment from the central server each time the cache server receives a request for requesting the first attachment from the user equipment, the foregoing step of requesting the identifier of the first attachment from the central server may occupy bandwidth resources between the cache server and the central server. Thus, in one example, the cache server may store a mapping between the identity of the first attachment and a storage address of the first attachment in the central server when the cache server first receives the identity of the first attachment from the central server. In this way, when the cache server receives the request for requesting the first attachment again, the identifier of the first attachment may be determined according to the correspondence, and further, whether the first attachment is included locally may be determined according to the identifier of the first attachment. By adopting the mode, the cache server can request the identification of the first attachment from the central server only when receiving the request for the first attachment for the first time, and can determine the identification of the first attachment from the corresponding relation stored locally when receiving the request for the first attachment again subsequently, thereby reducing the bandwidth resource between the cache server and the central server occupied by the identification of the first attachment requested from the central server.
S103: and if the cache server comprises the first attachment, acquiring the first attachment from the cache server, and sending the first attachment to the first user equipment.
If the cache server comprises the first attachment, the cache server can directly acquire the first attachment from the cache server, and then send the first attachment to the first user equipment. By adopting the method, the first user equipment can receive the first attachment without downloading from the central server, so that the link bandwidth pressure from each provincial node to the headquarters node is greatly reduced, network congestion is avoided, and the user experience is improved.
In another example, if the first attachment is not included in the cache server, the cache server may forward the first request to the central server, and the central server may send the first attachment to the first user equipment after receiving the first request. And the cache server forwards the first attachment sent by the central server to the first user equipment. In other words, after sending the first request to the central server, the cache server may receive the first attachment sent by the central server, and after receiving the first attachment, the cache server may send the first attachment to the first user equipment.
In one example, when the cache server receives the first attachment, the first attachment may also be saved. In this way, when the cache server again receives the request for the first attachment, the first attachment may be obtained locally without obtaining the first attachment from the central server, thereby reducing bandwidth pressure between the cache server and the central server.
Considering that at the same time, the cache server may receive an attachment request for the first attachment from a plurality of user equipments, assuming that the third request and the first request are requests received by the cache server at the same time, wherein: the third request is a request sent by the second user equipment for requesting the first attachment. For this case, if the first attachment is not included in the cache server, the cache server may forward the first request to the central server and receive the first attachment sent by the central server. For the third request, the cache server may not forward the third request to the central server, but store the first attachment after receiving the first attachment sent from the central server based on the first request, and send the locally stored first attachment to the second user equipment. It will be appreciated that if the central server receives the third request, the first attachment will be sent to the cache server based on the third request. By the scheme of the embodiment of the application, the frequency of sending the first attachment to the cache server by the central server can be reduced, so that the bandwidth pressure between the cache server and the central server is reduced.
In addition, it should be noted that, if the number of requests for requesting the first attachment received by the cache server is greater than two, for example, a fourth request, or even a fifth request, is included in addition to the third request. In the embodiment of the application, the cache server can optionally select a request (for example, the first request) to forward to the central server, so that the central server is ensured to send the first attachment only once, and the bandwidth pressure between the cache server and the central server is effectively reduced. In one possible implementation, this function may be implemented by setting parameters of the cache server. Assuming that the cache server is a nginx server, in order to enable the nginx server to receive a plurality of requests for requesting a first attachment at the same time, the nginx server may select a request (for example, a first request) from the plurality of requests to forward to the central server, and may set a value of a parameter Proxy _ cache _ lock for rejecting a repeat request in the nginx server to be on. In addition, in order to ensure the normal operation of the function of the nginx server for storing the attachment, the value of a parameter Proxy _ cache _ path can be set, wherein the parameter Proxy _ cache _ path is used for representing the storage position of the attachment, and can be/MyCachePath, for example; the value of the parameter Max _ size, which is used to indicate the upper storage limit of nginx, may be, for example, 100 GB.
Exemplary device
Based on the method provided by the above embodiment, the embodiment of the present application further provides an apparatus, which is described below with reference to the accompanying drawings.
Referring to fig. 2, a schematic structural diagram of an accessory handling device in an embodiment of the present application is shown. The apparatus may specifically include, for example:
the first receiving module 201: the first request is used for requesting a first accessory, and the first request carries a storage address of the first accessory in a central server;
the determination module 202: means for determining whether the first attachment is included in the cache server;
the first transmission module 203: and the processing unit is configured to, if the cache server includes the first attachment, obtain the first attachment from the cache server, and send the first attachment to the first user equipment.
By the device, the first user equipment can receive the first accessory without downloading from the central server, so that the link bandwidth pressure from each provincial node to the headquarters node is reduced to a great extent, network congestion is avoided, and user experience is improved.
In one implementation, the determining module is configured to:
determining an identity of the first accessory;
determining whether the first attachment is included in the cache server according to the identification of the first attachment.
In one implementation, the determining module is configured to:
determining the identifier of the first accessory according to the corresponding relation between the locally stored storage address and the identifier of the first accessory, wherein the corresponding relation is stored after the cache server receives the identifier of the first accessory sent by the central server for the first time; alternatively, the first and second electrodes may be,
sending a second request to the central server, wherein the second request comprises the storage address, and the second request is used for requesting the identifier of the first attachment;
and receiving the identification of the first attachment sent by the central server.
In one implementation, the apparatus further comprises:
a second sending module, configured to: if the cache server does not comprise the first attachment, sending the first request to the central server;
a second receiving module to: receiving the first attachment sent by the central server;
a third sending module, configured to: sending the first attachment to the first user device.
In one implementation, the apparatus further includes a storage module to store the first accessory.
In one implementation, the apparatus further comprises:
a third receiving module, configured to: receiving a third request sent by a second user device, wherein the third request is used for requesting the first attachment, the third request carries a storage address of the first attachment in a central server, and the time for receiving the first request by the cache server is the same as the time for receiving the third request by the cache server;
a fourth sending module, configured to: and acquiring the first attachment from the cache server, and sending the first attachment to the second user equipment.
In one implementation, the first attachment is a mail attachment.
In one implementation, the first request is a hypertext transfer protocol (HTTP) based request, or a third edition post office protocol (POP 3) based request, or an Interactive Mail Access Protocol (IMAP) based request.
In one implementation, the cache server is: nginx.
Since the apparatus 200 is an apparatus corresponding to the method provided in the above method embodiment, and the specific implementation of each unit of the apparatus 200 is the same as that of the above method embodiment, for the specific implementation of each unit of the apparatus 200, reference may be made to the description part of the above method embodiment, and details are not repeated here.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice in the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the attached claims
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (18)
1. An attachment handling method, performed by a cache server, the method comprising:
receiving a first request sent by first user equipment, wherein the first request is used for requesting a first accessory, and the first request carries a storage address of the first accessory in a central server;
determining whether the first attachment is included in the cache server;
and if the cache server comprises the first attachment, acquiring the first attachment from the cache server, and sending the first attachment to the first user equipment.
2. The method of claim 1, wherein the determining whether the first attachment is included in the cache server comprises:
determining an identity of the first accessory;
determining whether the first attachment is included in the cache server according to the identification of the first attachment.
3. The method of claim 2, wherein determining the identity of the first accessory comprises:
determining the identifier of the first accessory according to the corresponding relation between the locally stored storage address and the identifier of the first accessory, wherein the corresponding relation is stored after the cache server receives the identifier of the first accessory sent by the central server for the first time; alternatively, the first and second electrodes may be,
sending a second request to the central server, wherein the second request comprises the storage address, and the second request is used for requesting the identifier of the first attachment;
and receiving the identification of the first attachment sent by the central server.
4. The method of claim 1, further comprising:
if the cache server does not comprise the first attachment, sending the first request to the central server;
receiving the first attachment sent by the central server;
sending the first attachment to the first user device.
5. The method of claim 4, further comprising:
storing the first attachment.
6. The method of claim 5, further comprising:
receiving a third request sent by a second user device, wherein the third request is used for requesting the first attachment, the third request carries a storage address of the first attachment in a central server, and the time for receiving the first request by the cache server is the same as the time for receiving the third request by the cache server;
and acquiring the first attachment from the cache server, and sending the first attachment to the second user equipment.
7. The method of any of claims 1-6, wherein the first attachment is a mail attachment.
8. The method of claim 7, wherein the first request is a hypertext transfer protocol (HTTP) based request, or a third edition post office protocol (POP 3) based request, or an Interactive Mail Access Protocol (IMAP) based request.
9. The method of any of claims 1-6, wherein the cache server is: nginx.
10. An attachment handling apparatus, executed by a cache server, the apparatus comprising:
a first receiving module to: receiving a first request sent by first user equipment, wherein the first request is used for requesting a first accessory, and the first request carries a storage address of the first accessory in a central server;
a determination module to: determining whether the first attachment is included in the cache server;
a first sending module configured to: and if the cache server comprises the first attachment, acquiring the first attachment from the cache server, and sending the first attachment to the first user equipment.
11. The apparatus of claim 10, wherein the determining module is configured to:
determining an identity of the first accessory;
determining whether the first attachment is included in the cache server according to the identification of the first attachment.
12. The apparatus of claim 11, wherein the determining module is configured to:
determining the identifier of the first accessory according to the corresponding relation between the locally stored storage address and the identifier of the first accessory, wherein the corresponding relation is stored after the cache server receives the identifier of the first accessory sent by the central server for the first time; alternatively, the first and second electrodes may be,
sending a second request to the central server, wherein the second request comprises the storage address, and the second request is used for requesting the identifier of the first attachment;
and receiving the identification of the first attachment sent by the central server.
13. The apparatus of claim 10, further comprising:
a second sending module, configured to: if the cache server does not comprise the first attachment, sending the first request to the central server;
a second receiving module to: receiving the first attachment sent by the central server;
a third sending module, configured to: sending the first attachment to the first user device.
14. The apparatus of claim 13, further comprising a storage module to store the first accessory.
15. The apparatus of claim 14, further comprising:
a third receiving module, configured to: receiving a third request sent by a second user device, wherein the third request is used for requesting the first attachment, the third request carries a storage address of the first attachment in a central server, and the time for receiving the first request by the cache server is the same as the time for receiving the third request by the cache server;
a fourth sending module, configured to: and acquiring the first attachment from the cache server, and sending the first attachment to the second user equipment.
16. The apparatus of any of claims 10-15, wherein the first attachment is a mail attachment.
17. The apparatus of claim 16, wherein the first request is a hypertext transfer protocol (HTTP) based request, or a third edition Post Office Protocol (POP) 3 based request, or an Interactive Mail Access Protocol (IMAP) based request.
18. The apparatus according to any one of claims 10-15, wherein the cache server is: nginx.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011362015.4A CN112351109A (en) | 2020-11-27 | 2020-11-27 | Accessory processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011362015.4A CN112351109A (en) | 2020-11-27 | 2020-11-27 | Accessory processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112351109A true CN112351109A (en) | 2021-02-09 |
Family
ID=74366023
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011362015.4A Pending CN112351109A (en) | 2020-11-27 | 2020-11-27 | Accessory processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112351109A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101764848A (en) * | 2010-01-12 | 2010-06-30 | 浪潮(北京)电子信息产业有限公司 | Method and device for transmitting network files |
| CN102571963A (en) * | 2012-01-13 | 2012-07-11 | 华为技术有限公司 | Content delivery method, device and access network equipment |
| CN102891807A (en) * | 2012-07-16 | 2013-01-23 | 北京东方网信科技股份有限公司 | Network flow cache method and system based on active guidance |
| CN103873562A (en) * | 2014-02-27 | 2014-06-18 | 车智互联（北京）科技有限公司 | Cache method and cache system |
| CN104427005A (en) * | 2013-08-20 | 2015-03-18 | 阿里巴巴集团控股有限公司 | Method and system for realizing accurate request scheduling on content delivery network |
| WO2017177437A1 (en) * | 2016-04-15 | 2017-10-19 | 深圳前海达闼云端智能科技有限公司 | Domain name resolution method, device, and system |
| CN109558378A (en) * | 2018-11-28 | 2019-04-02 | 泰康保险集团股份有限公司 | File management method, device, equipment and storage medium |
-
2020
- 2020-11-27 CN CN202011362015.4A patent/CN112351109A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101764848A (en) * | 2010-01-12 | 2010-06-30 | 浪潮(北京)电子信息产业有限公司 | Method and device for transmitting network files |
| CN102571963A (en) * | 2012-01-13 | 2012-07-11 | 华为技术有限公司 | Content delivery method, device and access network equipment |
| CN102891807A (en) * | 2012-07-16 | 2013-01-23 | 北京东方网信科技股份有限公司 | Network flow cache method and system based on active guidance |
| CN104427005A (en) * | 2013-08-20 | 2015-03-18 | 阿里巴巴集团控股有限公司 | Method and system for realizing accurate request scheduling on content delivery network |
| CN103873562A (en) * | 2014-02-27 | 2014-06-18 | 车智互联（北京）科技有限公司 | Cache method and cache system |
| WO2017177437A1 (en) * | 2016-04-15 | 2017-10-19 | 深圳前海达闼云端智能科技有限公司 | Domain name resolution method, device, and system |
| CN109558378A (en) * | 2018-11-28 | 2019-04-02 | 泰康保险集团股份有限公司 | File management method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110198307B (en) | Method, device and system for selecting mobile edge computing node | |
| US11178062B2 (en) | Orchestrating physical and virtual resources for delivering digital contents | |
| US20180213031A1 (en) | System and method to balance servers based on server load status | |
| RU2405261C2 (en) | System of electronic program schedule servicing, method for formation and operation of this system | |
| CN102014121B (en) | Network autodiscovery as a lever to decorrelated service activation through event driven architecture | |
| CN108737500B (en) | Target resource obtaining and providing method and device, storage medium and computer equipment | |
| CN101132373A (en) | Method of providing qos for a flow | |
| CN113596191A (en) | Data processing method, network element equipment and readable storage medium | |
| US10848586B2 (en) | Content delivery network (CDN) for uploading, caching and delivering user content | |
| CN110995873A (en) | Gateway service interface discovery method, system, electronic device and storage medium | |
| US20220312309A1 (en) | Method and Apparatus for Reporting User Plane Function Information, Storage Medium, and Electronic Apparatus | |
| WO2013000374A1 (en) | Load balance implementation method, device and set-top box | |
| CN101729491A (en) | Method, device and system for enhancing application reliability of script-based business | |
| CN110719273A (en) | Method for determining back source node, server and computer readable storage medium | |
| US20230300106A1 (en) | Data processing method, network element device and readable storage medium | |
| CN113572835A (en) | Data processing method, network element equipment and readable storage medium | |
| CN112583952A (en) | Redirection scheduling processing method, device and system, related equipment and storage medium | |
| CN112825524B (en) | Method, device and system for determining network service node | |
| CN107438098A (en) | A kind of dynamic content dispensing method and its system | |
| CN110582090A (en) | CDN scheduling method, scheduling system and MEC network element | |
| CN111262779A (en) | Method, device, server and system for acquiring data in instant messaging | |
| CN112351109A (en) | Accessory processing method and device | |
| US20230102122A1 (en) | Methods, systems, and computer readable media for identifying alternate delivery endpoints for mobile originated data and monitoring reports in a communications network | |
| CN110995890B (en) | Domain name request scheduling method and device | |
| US9219618B2 (en) | Information processing system, information processing device, management terminal device, and computer readable medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210209 |