CN115378930A - File distribution method and device - Google Patents
File distribution method and device Download PDFInfo
- Publication number
- CN115378930A CN115378930A CN202110535441.1A CN202110535441A CN115378930A CN 115378930 A CN115378930 A CN 115378930A CN 202110535441 A CN202110535441 A CN 202110535441A CN 115378930 A CN115378930 A CN 115378930A
- Authority
- CN
- China
- Prior art keywords
- terminal
- file
- server
- receiving terminal
- receiving
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 63
- 230000004044 response Effects 0.000 claims abstract description 54
- 238000004891 communication Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 6
- 230000011664 signaling Effects 0.000 abstract description 11
- 238000010586 diagram Methods 0.000 description 11
- 230000000694 effects Effects 0.000 description 6
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000006467 substitution reaction 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/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a file distribution method and device. The method comprises the following steps: when the sending terminal needs to send a plurality of files to the receiving terminal, a file distribution request is generated, wherein the file distribution request comprises: the server determines a receiving terminal according to the identifier; the sending terminal sends the file distribution request to the server; and after receiving the response message returned by the server, the sending terminal sends the multiple files to the receiving terminal through the server, so that the receiving terminal stores the multiple files according to the attribute of each file in the multiple files. Compared with the mode that the file distribution request needs to be sent once for each file, the method saves the signaling overhead.
Description
Technical Field
The present invention relates to communications technologies, and in particular, to a method and an apparatus for distributing files.
Background
In the third Generation Partnership Project (3 rd Generation Partnership Project, 3GPP for short), the mission critical data (MCData) specification supports one-to-one file distribution and group file distribution. One-to-one file distribution refers to one user terminal sending a file to another user terminal, and group file distribution refers to one user terminal sending a file to all other user terminals in a group where the user terminal is located. Whether one-to-one file distribution or group file distribution is adopted, a sending terminal needs to send a file distribution request to a receiving terminal before sending a file, and the sending terminal sends the file to the receiving terminal after receiving a response message returned by the receiving terminal.
In the current MCData specification, when a sending terminal sends a plurality of files to a receiving terminal, a file distribution request needs to be sent once for each file, which causes resource waste due to high signaling overhead.
Disclosure of Invention
The application provides a file distribution method and device, which are used for solving the problem of high signaling overhead in the prior art.
In a first aspect, the present application provides a file distribution method, applied to a sending terminal, including: when the sending terminal needs to send a plurality of files to the receiving terminal, a file distribution request is generated, wherein the file distribution request comprises: the server determines a receiving terminal according to the identifier; the sending terminal sends the file distribution request to the server so that the server determines the receiving terminal according to the identification, and sends the file distribution request to the receiving terminal so that the receiving terminal returns a response message to the server after receiving the file distribution request; and after receiving the response message returned by the server, the sending terminal sends the multiple files to the receiving terminal through the server so that the receiving terminal stores the multiple files according to the attribute of each file in the multiple files.
Optionally, the number of the receiving terminals is one, and the identifier is a unique code ID of the user terminal.
Optionally, the number of the receiving terminals is at least two, and the identifier is an ID of a group in which the sending terminal and the receiving terminal are located.
Optionally, the attributes of each file include: load attributes of the file and metadata attributes of the file, the load attributes including: load code, load attribute length, load serial number and load attribute content; the metadata attributes include: metadata encoding, metadata attribute length, metadata sequence number, and metadata attribute content.
In a second aspect, the present application provides a file distribution method, applied to a server, including: the server receives a file distribution request, wherein the file distribution request comprises: the file distribution request is generated when a sending terminal needs to send a plurality of files to a receiving terminal; the server determines the receiving terminal according to the identification and sends the file distribution request to the receiving terminal, so that the receiving terminal returns a response message to the server after receiving the file distribution request; and after receiving the response message, the server sends the response message to the sending terminal, so that the sending terminal sends the multiple files to the receiving terminal through the server, and the receiving terminal stores the multiple files according to the attribute of each file in the multiple files.
Optionally, the number of the receiving terminals is one, and the identifier is a unique code ID of the user terminal; the server determines the receiving terminal according to the identifier, and the method comprises the following steps: and the server determines the user terminal corresponding to the ID as the receiving terminal.
Optionally, the number of the receiving terminals is at least two, and the identifier is an ID of a group in which the sending terminal and the receiving terminal are located; the server determines the receiving terminal according to the identifier, and the determination comprises the following steps: the server determines other user terminals except the sending terminal in the group according to the ID of the group; and the server takes other user terminals except the sending terminal in the group as the receiving terminals.
In a third aspect, the present application provides a file distribution method, applied to a receiving terminal, including: the receiving terminal receives a file distribution request, wherein the file distribution request comprises: the file distribution request is generated when a sending terminal needs to send the files to the receiving terminal; the receiving terminal sends a response message to the server so that the server sends the response message to the sending terminal, and the sending terminal sends the files to the receiving terminal through the server; and the receiving terminal stores the files according to the attribute of each file in the files.
Optionally, the sending, by the receiving terminal, a response message to the server includes: the receiving terminal displays a file receiving prompt; and when the receiving terminal receives the touch operation of confirming to receive the file by the user, the receiving terminal sends the response message to the server.
In a fourth aspect, the present application provides a transmitting terminal, including: a generating module, configured to generate a file distribution request when the sending terminal needs to send multiple files to a receiving terminal, where the file distribution request includes: the server determines a receiving terminal according to the identifier; a sending module, configured to send the file distribution request to the server, so that the server determines the receiving terminal according to the identifier, and sends the file distribution request to the receiving terminal, so that the receiving terminal returns a response message to the server after receiving the file distribution request; the receiving module is used for receiving the response message returned by the server; the sending module is further configured to send the multiple files to the receiving terminal through the server, so that the receiving terminal stores the multiple files according to the attribute of each file in the multiple files.
In a fifth aspect, the present application provides a server, comprising: a receiving module, configured to receive a file distribution request, where the file distribution request includes: the file distribution request is generated when a sending terminal needs to send a plurality of files to a receiving terminal; a sending module, configured to determine the receiving terminal according to the identifier, and send the file distribution request to the receiving terminal, so that the receiving terminal returns a response message to the server after receiving the file distribution request; the sending module is further configured to send the response message to the sending terminal after the receiving module receives the response message, so that the sending terminal sends the multiple files to the receiving terminal through the server, and the receiving terminal stores the multiple files according to the attribute of each file in the multiple files.
In a sixth aspect, the present application provides a receiving terminal, including: a receiving module, configured to receive a file distribution request, where the file distribution request includes: the file distribution request is generated when a sending terminal needs to send the files to the receiving terminal; a sending module, configured to send a response message to the server, so that the server sends the response message to the sending terminal, so that the sending terminal sends the multiple files to the receiving terminal through the server; and the storage module is used for storing the files according to the attribute of each file in the files.
In a seventh aspect, the present application provides a communication system, comprising the transmitting terminal of the fourth aspect, the server of the fifth aspect, and the receiving terminal of the sixth aspect.
In an eighth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method provided in any of the first to third aspects.
In a ninth aspect, the present application provides a chip comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to implement the method provided by any one of the first to third aspects via execution of the executable instructions.
According to the file distribution method and device, the attributes of all files to be sent by the sending terminal are added in the file distribution request, so that the receiving terminal can know that a plurality of files are sent by the sending terminal after receiving the file distribution request, and the receiving terminal can store each file according to the attributes carried in the file distribution request after receiving the plurality of files. Compared with the mode that the file distribution request needs to be sent once for each file, the method saves the signaling overhead.
Drawings
Fig. 1 is a first application scenario provided by the present application;
fig. 2 is a first flowchart under the MCData specification provided in the present application;
fig. 3 is a second application scenario provided by the present application;
fig. 4 is a second flowchart under the MCData specification provided in the present application;
fig. 5 is a schematic flowchart of a first embodiment of a file distribution method provided in the present application;
FIG. 6 is a first user interface provided herein;
FIG. 7 is a schematic diagram of the Payload attributes provided herein;
FIG. 8 is a diagram illustrating Metadata attributes provided herein;
FIG. 9 is a second user interface provided by the present application;
fig. 10 is a schematic flowchart of a second embodiment of a file distribution method provided in the present application;
FIG. 11 is a third user interface diagram provided herein;
fig. 12 is a schematic structural diagram of a transmitting terminal provided in the present application;
fig. 13 is a schematic structural diagram of a server provided in the present application;
fig. 14 is a schematic structural diagram of a receiving terminal provided in the present application;
fig. 15 is a schematic diagram of a hardware structure of a chip provided in the present application.
Detailed Description
To make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be clearly and completely described below with reference to the drawings in the present application, and it is obvious that the described embodiments are some, but not all embodiments of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.
In this application, it should be construed that the terms "" and "" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated object, indicating that there may be three relationships, for example, a and/or B, which may indicate: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "is a relation generally indicating that the former and latter associated objects are an" or ". "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a alone, b alone, c alone, a and b combination, a and c combination, b and c combination, or a, b and c combination, wherein a, b and c can be single or multiple.
Fig. 1 is a first application scenario provided in the present application. The application scenario shown in fig. 1 is a one-to-one file distribution scenario. One-to-one file distribution refers to one user terminal sending a file to another user terminal. In fig. 1, the user terminal sending the file is represented by a user terminal 1, the user terminal receiving the file is represented by a user terminal 2, and the user terminal 1 interacts with the user terminal 2 through a server. In the scenario shown in fig. 1, the user terminal 1 is also referred to as a transmitting terminal and the user terminal 2 is also referred to as a receiving terminal.
Referring to fig. 2, in the current MCData specification, when the ue 1 sends a file to the ue 2, the following steps are included:
when the file is transmitted by a Hypertext Transfer Protocol (HTTP), the user terminal 1 first uploads the file to the server, and then sends a file distribution request to the user terminal 2 through the server, where the file distribution request carries an attribute of the file, where the attribute includes a Uniform Resource Locator (URL) of the file in the server, and after receiving the file distribution request, the user terminal 2 downloads the file from the server according to the URL, and stores the file according to other contents in the attribute. Alternatively, the URL may be fed back to the user terminal 1 after the server receives the file uploaded by the user terminal 1.
When the file is transmitted in a Multimedia (MEDIA) mode, a user terminal 1 firstly sends a file distribution request to a user terminal 2 through a server, the file distribution request carries the attribute of the file, the user terminal 2 returns a response message to the user terminal 1 through the server after receiving the file distribution request, the user terminal 1 sends the file to the user terminal 2 after receiving the response message, and the user terminal 2 stores the received file according to the attribute carried in the file distribution request.
However, in both the file transferred by the HTTP method and the file transferred by the MEDIA method, when the user terminal 1 transmits a plurality of files to the user terminal 2, the user terminal 1 needs to transmit a file distribution request once for each file, and the signaling overhead is large.
Fig. 3 is a second application scenario provided by the present application. The application scenario shown in fig. 3 is a group file distribution scenario. Group file distribution refers to a user terminal sending a file to all other user terminals except the user terminal in a group where the user terminal is located. In fig. 3, the user terminal that sends the file is represented by the user terminal 1, the group in which the user terminal 1 is located is represented by the group a, the user terminals other than the user terminal 1 in the group a are represented by the user terminals 2 to N, and the user terminal 1 interacts with the user terminals 2 to N through the server. In the scenario shown in fig. 3, the user terminal 1 is also referred to as a transmitting terminal, and the user terminals 2 to N are all referred to as receiving terminals.
Referring to fig. 4, in the current MCData specification, when the ue 1 sends a file to the ues 2 to N, the following steps are included:
when the file is transmitted by a Hypertext Transfer Protocol (HTTP), the user terminal 1 uploads the file to the server, and then sends a file distribution request to the server, where the file distribution request carries an identifier of the group a and an attribute of the file, where the attribute includes a Uniform Resource Locator (URL) of the file in the server, and after receiving the file distribution request, the server parses the file distribution request from the group management server according to the identifier of the group a to obtain other user terminals in the group a except the user terminal 1, that is, the user terminals 2 to N, and sends the file distribution request to the user terminals 2 to N, and after receiving the file distribution request, the user terminals 2 to N download the file from the server according to the URL, and store the file according to other contents in the attribute. Alternatively, the URL may be fed back to the user terminal 1 after the server receives the file uploaded by the user terminal 1.
When the file is transmitted in a Multimedia (MEDIA) mode, a user terminal 1 firstly sends a file distribution request to a server, the file distribution request carries an identifier of a group A and an attribute of the file, the server receives the file distribution request, analyzes the file distribution request from a group management server according to the identifier of the group A to obtain other user terminals except the user terminal 1 in the group A, namely the user terminals 2 to N, and sends the file distribution request to the user terminals 2 to N, the user terminals 2 to N return response messages to the user terminal 1 through the server after receiving the file distribution request, and the user terminal 1 sends the file to the user terminals 2 to N after receiving the response messages. And the user terminals 2 to N store the received files according to the attributes carried in the file distribution request.
However, in both of the file transferred by the HTTP scheme and the file transferred by the MEDIA scheme, when the user terminal 1 transmits a plurality of files to the user terminals 2 to N, the user terminal 1 needs to transmit a file distribution request once for each file, and thus the signaling overhead is large.
It can be seen that, in both the one-to-one file distribution scenario and the group file distribution scenario, when the user terminal 1 needs to send multiple files, a file distribution request needs to be sent once for each file, which results in a large signaling overhead and resource waste.
The reason for the high signaling overhead is that the sending terminal needs to send a file distribution request once for each file, and an important role of the file distribution request is to inform the receiving terminal of the attributes of the file to be sent by the sending terminal. By taking the file distribution request as an entry point, the file distribution request is added to the attributes of all files to be sent by the sending terminal, so that the receiving terminal can receive a plurality of files at one time after receiving the file distribution request. Compared with the mode that each file needs to send a file distribution request once, the method saves signaling overhead.
Specific embodiments of the present application will be described in detail below with reference to specific examples. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Example one
In the scenario shown in fig. 1, fig. 5 is a schematic flowchart of a first embodiment of a file distribution method provided in the present application, and as shown in fig. 5, the file distribution method provided in the present embodiment includes:
s501, when the transmitting terminal needs to transmit a plurality of files to the receiving terminal, the transmitting terminal generates a file distribution request. The file distribution request includes: an ID of a terminal and attributes of a plurality of files are received.
Optionally, the file in this embodiment may be a picture.
In one possible implementation, the sending terminal may determine that a plurality of pictures need to be sent to the receiving terminal in the following scenarios:
referring to fig. 6, after the user makes a call to any social software on the sending terminal, a chat interface with the friend a is opened, and a click operation shown in fig. 6 is performed on the chat interface, so that the sending terminal displays a selection interface, where the selection interface includes options such as an album, shooting, and video call. When the user selects the photo album, the user terminal displays the pictures in the photo album, and after the user selects a plurality of pictures, the user clicks the sending button, so that the sending terminal can determine that the plurality of pictures need to be sent to the user terminal corresponding to the friend A. The sending terminal may further generate a file distribution request including an ID of the user terminal corresponding to the user a and attributes of the plurality of pictures selected by the user.
The following describes attributes of a plurality of files:
the file distribution request carries attributes of a plurality of files, and the attributes of each file comprise a load (Payload) attribute of the file and a Metadata (Metadata) attribute of the file.
Referring to fig. 7, the Payload attribute of the file includes: load code, load attribute length, load sequence number, and load attribute content. In the art, load coding may be represented by Payload IEI, load attribute Length may be represented by Length of Payload contents, load Sequence number may be represented by Sequence of Payload, and load attribute content may be represented by Payload contents. The load code may occupy one byte, the load attribute Length may occupy two bytes, the load sequence number may occupy one byte, and the byte number occupied by the load attribute content is related to the Length of load contents. The load attribute content includes: the type of load and the specific load content.
Referring to fig. 8, the Metadata attribute of a file includes: metadata encoding, metadata attribute length, metadata sequence number, and metadata attribute content. In the art, metadata encoding may be represented using Metadata IEI, metadata attribute Length may be represented using Length of Metadata contents, metadata Sequence number may be represented using Sequence of Metadata, and Metadata attribute content may be represented using Metadata contents. Metadata encoding can occupy one byte, metadata attribute Length can occupy two bytes, metadata sequence number can occupy one byte, and the byte number occupied by Metadata attribute content is related to Length of Metadata contents. Metadata attribute content includes: file name, file date, file description, and file size, etc.
In fig. 7 and 8, octet1 represents the first byte, octet2 the second byte, and so on, with 8 bits per byte.
S502, the sending terminal sends a file distribution request to the server.
S503, the server determines the receiving terminal according to the ID of the receiving terminal.
S504, the server sends a file distribution request to the receiving terminal.
In one possible implementation manner, the server directly takes the user terminal corresponding to the received ID as the receiving terminal, and sends the file distribution request to the user terminal.
And S505, the receiving terminal sends a response message to the server.
In a possible implementation manner, after receiving the file distribution request, the receiving terminal may first display a file receiving reminder, and after receiving the touch operation of the user for confirming to receive the file, send a response message to the server. The method combines the receiving will of the user, and the sending terminal can not send the file to the receiving terminal under the condition that the user does not want to receive the file, thereby saving network resources and simultaneously improving the use experience of the user.
In one possible implementation, the receiving terminal may display the file reception reminder by:
as shown in fig. 9, the receiving terminal may display a dialog box shown in fig. 9 to inquire whether the user agrees to receive the file, if the user clicks yes, the receiving terminal sends a response message to the server, if the user clicks no, the receiving terminal does not send the response message to the server, and since the sending terminal sends the file after receiving the response message, the sending terminal does not send the file to the receiving terminal under the condition that the user clicks no, which saves network resources.
S506, the server sends a response message to the sending terminal.
And S507, the sending terminal sends the first file to the server.
S508, the server forwards the first file to the receiving terminal.
S509, the receiving terminal stores the first file according to the attribute of the first file.
It should be noted that: similar steps are performed for the second file, the third file, \8230forthe nth file, as shown in FIG. 5. Such as: and after receiving the second file, the receiving terminal stores the second file according to the attribute of the second file.
Specifically, with reference to fig. 7 and 8, after receiving the first file, the receiving terminal searches for a load attribute with a load sequence number of 1 from the load attributes of the respective files, and uses the load attribute as the load attribute of the first file, and similarly, searches for a metadata attribute with a metadata sequence number of 1 from the metadata attributes of the respective files, and uses the metadata attribute as the metadata attribute of the first file. And storing the first file according to the load attribute content in the load attribute with the load sequence number of 1 and the metadata attribute content in the metadata attribute with the metadata sequence number of 1.
Similarly, after receiving the second file, the receiving terminal searches for the load attribute with the load serial number of 2 from the load attributes of the files, uses the load attribute as the load attribute of the second file, similarly, searches for the metadata attribute with the metadata serial number of 2 from the metadata attributes of the files, and uses the metadata attribute as the metadata attribute of the second file. And storing the second file according to the load attribute content in the load attribute with the load sequence number of 2 and the metadata attribute content in the metadata attribute with the metadata sequence number of 2. Subsequent files are analogized in the same way.
It should be noted that: the above load serial numbers using numbers such as 1, 2, etc. are only examples, and may be represented in other forms, which are not limited in the present application. In the file distribution method provided in this embodiment, in a one-to-one distribution scenario, the attributes of all files to be sent by the sending terminal are added to the file distribution request, so that after the receiving terminal receives the file distribution request, it is known that there are multiple files to be sent by the sending terminal, and after the receiving terminal receives the multiple files, each file is stored according to the attributes carried in the file distribution request. Compared with the above mode that the file distribution request needs to be sent once for each file, the method saves signaling overhead.
It should be noted that: s501 to S509 describe in detail a distribution method when a plurality of files transmitted by a transmission terminal are files transmitted by the MEDIA method. If the plurality of files sent by the sending terminal are files transmitted in an HTTP manner, the user terminal 1 may upload the plurality of files to the server, the server feeds back URLs of the plurality of files in the server to the sending terminal, the sending terminal sends a file distribution request to the receiving terminal through the server, the file distribution request carries attributes of each file, the attribute of each file includes a load (Payload) attribute of the file and a Metadata (Metadata) attribute of the file, the load (Payload) attribute includes a corresponding URL, and specifically, the URL may be carried in the content of the load attribute in fig. 7. After receiving the file distribution request, the receiving terminal downloads a first file from the server according to the URL in the load attribute content with the load serial number of 1, and stores the first file according to other information in the load attribute content with the load serial number of 1 and the metadata attribute content with the metadata serial number of 1. The subsequent files are analogized in the same way.
Example two
In the scenario shown in fig. 3, fig. 10 is a schematic flowchart of a second embodiment of the file distribution method provided in the present application, and as shown in fig. 10, the file distribution method provided in the present embodiment includes:
s1001, when the transmitting terminal needs to transmit a plurality of files to the receiving terminal, the transmitting terminal generates a file distribution request. The file distribution request includes: the ID of the group in which the transmitting terminal and the receiving terminal are located and the attributes of the plurality of files.
In one possible implementation, the sending terminal may determine that a plurality of pictures need to be sent to the receiving terminal in the following scenarios:
referring to fig. 11, after the user makes a call to any social software on the sending terminal, the chat interface of the group a is opened, and the click operation shown in fig. 11 is performed on the chat interface, so that the sending terminal displays a selection interface, where the selection interface includes options such as album, shooting, and video call. And when the user selects the photo album, the user terminal displays the pictures in the photo album, and after the user selects a plurality of pictures, the user clicks a sending button, so that the sending terminal can determine that the plurality of pictures need to be sent to the user terminals corresponding to other members in the group A. The transmitting terminal may further generate a file distribution request including the ID of the group a and the attributes of the plurality of pictures selected by the user.
S1002, the sending terminal sends a file distribution request to the server.
S1003, the server determines the receiving terminal according to the ID of the group.
In a possible implementation manner, the group management server maintains the corresponding relationship between the group ID and the user terminal, and after receiving the file distribution request, the server searches for the user terminal corresponding to the ID carried in the file distribution request from the group management server. And taking other user terminals except the sending terminal as receiving terminals in the user terminals corresponding to the ID carried by the file distribution request.
S1004, the server transmits a file distribution request to the receiving terminal.
S1005, the receiving terminal sends a response message to the server.
In a possible implementation manner, as in the foregoing embodiment, after receiving the file distribution request, the receiving terminal may first display a file receiving reminder, and after receiving the touch operation of the user confirming to receive the file, send a response message to the server. The method combines the receiving will of the user, and the sending terminal can not send the file to the receiving terminal under the condition that the user does not want to receive the file, thereby saving network resources and simultaneously improving the use experience of the user.
It should be noted that: s1006 is applicable to any one of the ue 2 to the ue N in the scenario shown in fig. 3.
S1006, the server sends a response message to the sending terminal.
And S1007, the sending terminal sends the first file to the server.
S1008, the server forwards the first file to the receiving terminal.
S1009, the receiving terminal stores the first file according to the attribute of the first file.
It should be noted that: similar steps are performed for the second file, the third file, \8230forthe nth file, as shown in FIG. 10. Such as: and after receiving the second file, the receiving terminal stores the second file according to the attribute of the second file.
For a specific storage manner, refer to the above embodiments, which are not described herein again.
In the file distribution method provided in this embodiment, in a group file distribution scenario, the attributes of all files to be sent by the sending terminal are added to the file distribution request, so that after receiving the file distribution request, a plurality of receiving terminals know that a plurality of files are to be sent by the sending terminal, and after receiving the plurality of files, each receiving terminal stores each file according to the attributes carried in the file distribution request. Compared with the mode that each file needs to send a file distribution request once, the method saves signaling overhead.
It should be noted that: in the group file distribution scenario, the above-described S1001-S1009 describes in detail a distribution method when a plurality of files transmitted by a transmission terminal are files transmitted by the MEDIA method. If the plurality of files sent by the sending terminal are files transmitted in an HTTP mode, the sending terminal can upload the plurality of files to the server, and the server feeds URLs of the plurality of files in the server back to the sending terminal. The sending terminal then sends a file distribution request to the server, where the file distribution request carries the ID of the group and the attributes of each file, and the attributes of each file include a load (Payload) attribute of the file and a Metadata (Metadata) attribute of the file, where the load (Payload) attribute includes a corresponding URL, which may be carried in the content of the load attribute in fig. 7. And after receiving the file distribution request, the server determines the receiving terminal according to the ID of the group. And then transmits a file distribution request to the receiving terminal. After receiving the file distribution request, the receiving terminal downloads a first file from the server according to the URL in the load attribute content with the load serial number of 1, and stores the first file according to other information in the load attribute content with the load serial number of 1 and the metadata attribute content with the metadata serial number of 1. The subsequent files are analogized in the same way.
Fig. 12 is a schematic structural diagram of a transmitting terminal according to the present application. As shown in fig. 12, the transmitting terminal provided by the present application includes:
a generating module 1201, configured to generate a file distribution request when the sending terminal needs to send multiple files to a receiving terminal, where the file distribution request includes: the server determines a receiving terminal according to the identifier;
a sending module 1202, configured to send the file distribution request to the server, so that the server determines the receiving terminal according to the identifier, and sends the file distribution request to the receiving terminal, so that the receiving terminal returns a response message to the server after receiving the file distribution request;
a receiving module 1203, configured to receive the response message returned by the server;
the sending module is further configured to send the plurality of files to the receiving terminal through the server, so that the receiving terminal stores the plurality of files according to the attribute of each file in the plurality of files.
Optionally, the number of the receiving terminals is one, and the identifier is a unique code ID of the user terminal.
Optionally, the number of the receiving terminals is at least two, and the identifier is an ID of a group in which the sending terminal and the receiving terminal are located.
Optionally, the attributes of each file include: load attributes of the file and metadata attributes of the file, the load attributes comprising: load codes, load attribute length, load serial number and load attribute content; the metadata attributes include: metadata encoding, metadata attribute length, metadata sequence number, and metadata attribute content.
The transmitting terminal shown in fig. 12 may be configured to perform the steps performed by the transmitting terminal in any of the above-described method embodiments. The implementation principle and the technical effect are similar, and are not described in detail herein.
Fig. 13 is a schematic structural diagram of a server provided in the present application. As shown in fig. 13, the server provided by the present application includes:
a receiving module 1301, configured to receive a file distribution request, where the file distribution request includes: the file distribution request is generated when a sending terminal needs to send a plurality of files to a receiving terminal;
a sending module 1302, configured to determine the receiving terminal according to the identifier, and send the file distribution request to the receiving terminal, so that the receiving terminal returns a response message to the server after receiving the file distribution request;
the sending module 1302 is further configured to, after receiving the response message, send the response message to the sending terminal, so that the sending terminal sends the multiple files to the receiving terminal through the server, so that the receiving terminal stores the multiple files according to the attribute of each file in the multiple files.
Optionally, the number of the receiving terminals is one, and the identifier is a unique code ID of the user terminal; the sending module 1302 is specifically configured to:
and the server determines the user terminal corresponding to the ID as the receiving terminal.
Optionally, the number of the receiving terminals is at least two, and the identifier is an ID of a group in which the sending terminal and the receiving terminal are located; the sending module 1302 is specifically configured to:
the server determines other user terminals except the sending terminal in the group according to the ID of the group; and the server takes other user terminals except the sending terminal in the group as the receiving terminals.
The sending terminal shown in fig. 13 may be configured to perform the steps performed by the server in any of the above-described method embodiments. The implementation principle and the technical effect are similar, and are not described in detail herein.
Fig. 14 is a schematic structural diagram of a receiving terminal provided in the present application. As shown in fig. 14, the receiving terminal provided by the present application includes:
a receiving module 1401, configured to receive a file distribution request, where the file distribution request includes: the file distribution request is generated when a sending terminal needs to send the files to the receiving terminal;
a sending module 1402, configured to send a response message to the server, so that the server sends the response message to the sending terminal, so that the sending terminal sends the plurality of files to the receiving terminal through the server;
a storage module 1403, configured to store the multiple files according to the attribute of each file in the multiple files.
The transmitting terminal shown in fig. 14 may be configured to perform the steps performed by the receiving terminal in any of the above-described method embodiments. The implementation principle and the technical effect are similar, and are not described in detail herein.
Fig. 15 is a schematic diagram of a hardware structure of a chip provided in the present application. As shown in fig. 15, the chip of the present embodiment may include:
memory 1501 is used to store program instructions.
A processor 1502 configured to implement the steps of sending a terminal in any of the above method embodiments, or implement the steps of a server in any of the above method embodiments, or implement the steps of receiving a terminal in any of the above method embodiments when the program instructions are executed. The implementation principle and the technical effect are similar, and are not described in detail herein.
The present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of transmitting a terminal in any of the above-described method embodiments, or performs the steps of a server in any of the above-described method embodiments, or performs the steps of receiving a terminal in any of the above-described method embodiments. The implementation principle and the technical effect are similar, and are not described in detail herein.
The present application further provides a program product, which includes a computer program stored in a readable storage medium, from which the computer program can be read by at least one processor, and the computer program is executed by the at least one processor, so that the processor implements the steps of sending a terminal in any one of the above method embodiments, or implements the steps of a server in any one of the above method embodiments, or implements the steps of receiving a terminal in any one of the above method embodiments. The implementation principle and the technical effect are similar, and are not described in detail herein.
The present application also provides a communication system including the transmitting terminal shown in fig. 12, the server shown in fig. 13, and the receiving terminal shown in fig. 14.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. 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 may be implemented in the form of hardware, or in the form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to perform some steps of the methods 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.
It should be understood that the Processor described herein may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor, or in a combination of the hardware and software modules in the processor.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit 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 or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.
Claims (15)
1. A file distribution method is applied to a sending terminal and is characterized by comprising the following steps:
when the sending terminal needs to send a plurality of files to the receiving terminal, generating a file distribution request, wherein the file distribution request comprises: the server determines a receiving terminal according to the identifier;
the sending terminal sends the file distribution request to the server so that the server determines the receiving terminal according to the identification, and sends the file distribution request to the receiving terminal so that the receiving terminal returns a response message to the server after receiving the file distribution request;
and after receiving the response message returned by the server, the sending terminal sends the multiple files to the receiving terminal through the server, so that the receiving terminal stores the multiple files according to the attribute of each file in the multiple files.
2. The method of claim 1, wherein the number of the receiving terminals is one, and the identifier is a unique code ID of the receiving terminal.
3. The method according to claim 1, wherein the number of the receiving terminals is at least two, and the identifier is an ID of a group in which the transmitting terminal and the receiving terminal are located.
4. The method according to any one of claims 1 to 3, wherein the attributes of each file include: load attributes of the file and metadata attributes of the file, the load attributes comprising: load codes, load attribute length, load serial number and load attribute content; the metadata attributes include: metadata encoding, metadata attribute length, metadata sequence number, and metadata attribute content.
5. A file distribution method is applied to a server and is characterized by comprising the following steps:
the server receives a file distribution request, wherein the file distribution request comprises: the file distribution request is generated when a sending terminal needs to send a plurality of files to a receiving terminal;
the server determines the receiving terminal according to the identification and sends the file distribution request to the receiving terminal, so that the receiving terminal returns a response message to the server after receiving the file distribution request;
and after receiving the response message, the server sends the response message to the sending terminal, so that the sending terminal sends the multiple files to the receiving terminal through the server, and the receiving terminal stores the multiple files according to the attribute of each file in the multiple files.
6. The method according to claim 5, wherein the number of the receiving terminals is one, and the identifier is a unique code ID of the receiving terminal;
the server determines the receiving terminal according to the identifier, and the method comprises the following steps:
and the server determines the user terminal corresponding to the ID as the receiving terminal.
7. The method according to claim 5, wherein the number of the receiving terminals is at least two, and the identifier is an ID of a group in which the transmitting terminal and the receiving terminal are located;
the server determines the receiving terminal according to the identifier, and the method comprises the following steps:
the server determines other user terminals except the sending terminal in the group according to the ID of the group;
and the server takes other user terminals except the sending terminal in the group as the receiving terminals.
8. A file distribution method is applied to a receiving terminal and is characterized by comprising the following steps:
the receiving terminal receives a file distribution request, wherein the file distribution request comprises: the file distribution request is generated when a sending terminal needs to send the files to the receiving terminal;
the receiving terminal sends a response message to a server so that the server sends the response message to the sending terminal, and the sending terminal sends the plurality of files to the receiving terminal through the server;
and the receiving terminal stores the files according to the attribute of each file in the files.
9. The method of claim 8, wherein the receiving terminal sends a response message to the server, comprising:
the receiving terminal displays a file receiving prompt;
and when the receiving terminal receives the touch operation of confirming to receive the file by the user, the receiving terminal sends the response message to the server.
10. A transmitting terminal, comprising:
a generating module, configured to generate a file distribution request when the sending terminal needs to send multiple files to a receiving terminal, where the file distribution request includes: the server determines a receiving terminal according to the identifier;
a sending module, configured to send the file distribution request to the server, so that the server determines the receiving terminal according to the identifier, and sends the file distribution request to the receiving terminal, so that the receiving terminal returns a response message to the server after receiving the file distribution request;
the receiving module is used for receiving the response message returned by the server;
the sending module is further configured to send the multiple files to the receiving terminal through the server, so that the receiving terminal stores the multiple files according to the attribute of each file in the multiple files.
11. A server, comprising:
a receiving module, configured to receive a file distribution request, where the file distribution request includes: the file distribution request is generated when a sending terminal needs to send a plurality of files to a receiving terminal;
a sending module, configured to determine the receiving terminal according to the identifier, and send the file distribution request to the receiving terminal, so that the receiving terminal returns a response message to the server after receiving the file distribution request;
the sending module is further configured to send the response message to the sending terminal after the receiving module receives the response message, so that the sending terminal sends the multiple files to the receiving terminal through the server, and the receiving terminal stores the multiple files according to the attribute of each file in the multiple files.
12. A receiving terminal, comprising:
a receiving module, configured to receive a file distribution request, where the file distribution request includes: the file distribution request is generated when a sending terminal needs to send the files to the receiving terminal;
a sending module, configured to send a response message to a server, so that the server sends the response message to the sending terminal, so that the sending terminal sends the multiple files to the receiving terminal through the server;
and the storage module is used for storing the files according to the attribute of each file in the files.
13. A communication system comprising the transmitting terminal of claim 10, the server of claim 11, and the receiving terminal of claim 12.
14. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method of any one of claims 1-9.
15. A chip, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to implement the method of any of claims 1-9 via execution of the executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110535441.1A CN115378930B (en) | 2021-05-17 | 2021-05-17 | File distribution method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110535441.1A CN115378930B (en) | 2021-05-17 | 2021-05-17 | File distribution method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115378930A true CN115378930A (en) | 2022-11-22 |
| CN115378930B CN115378930B (en) | 2024-08-13 |
Family
ID=84058978
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110535441.1A Active CN115378930B (en) | 2021-05-17 | 2021-05-17 | File distribution method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115378930B (en) |
Citations (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH11353247A (en) * | 1998-06-05 | 1999-12-24 | Nippon Telegr & Teleph Corp <Ntt> | Method and system for file distribution and storage medium in which file distributing program is stored |
| US6397246B1 (en) * | 1998-11-13 | 2002-05-28 | International Business Machines Corporation | Method and system for processing document requests in a network system |
| CN101860571A (en) * | 2010-06-12 | 2010-10-13 | 中兴通讯股份有限公司 | Method, system and terminal for sending dynamic content distributing service document |
| CN102148835A (en) * | 2011-04-27 | 2011-08-10 | 许式伟 | Method and system for transmitting and sharing electronic documents |
| CN102571950A (en) * | 2011-12-31 | 2012-07-11 | 华为技术有限公司 | Media content providing and acquiring methods, server and user terminal |
| KR20120110871A (en) * | 2011-03-30 | 2012-10-10 | 주식회사 케이티 | Method for determining and searching storage server in distributed file system |
| US20130073691A1 (en) * | 2011-06-17 | 2013-03-21 | Alibaba Group Holding Limited | File Processing Method, System and Server-clustered System for Cloud Storage |
| US8515904B1 (en) * | 2012-03-29 | 2013-08-20 | Emc Corporation | Providing file sytem quota support for a file system having separated data and metadata |
| WO2014161157A1 (en) * | 2013-04-02 | 2014-10-09 | 华为技术有限公司 | File uploading method in cloud storage, client, application server, and cloud storage system |
| CN104521289A (en) * | 2012-08-08 | 2015-04-15 | 三星电子株式会社 | Apparatus and method of connecting service according to user intention |
| WO2015054897A1 (en) * | 2013-10-18 | 2015-04-23 | 华为技术有限公司 | Data storage method, data storage apparatus, and storage device |
| CN105357321A (en) * | 2015-12-11 | 2016-02-24 | 北京元心科技有限公司 | File transmission method based on abstract value, terminal, and file server |
| CN105677778A (en) * | 2015-12-30 | 2016-06-15 | 深圳市鼎芯无限科技有限公司 | Small picture batch processing method, intelligent terminal and server |
| CN107070972A (en) * | 2016-12-30 | 2017-08-18 | 中国银联股份有限公司 | A kind of distributed document processing method and processing device |
| CN107872489A (en) * | 2016-09-28 | 2018-04-03 | 杭州海康威视数字技术股份有限公司 | A kind of file section method for uploading, device and cloud storage system |
| CN108093015A (en) * | 2016-11-21 | 2018-05-29 | 北京京东尚科信息技术有限公司 | Document transmission system |
| CN108280228A (en) * | 2018-02-26 | 2018-07-13 | 北京车和家信息技术有限公司 | A kind of processing method and relevant device of webpage |
| US20180232394A1 (en) * | 2017-02-15 | 2018-08-16 | Google Inc. | Systems and methods for providing access to a data file stored at a data storage system |
| CN108737482A (en) * | 2017-04-24 | 2018-11-02 | 腾讯科技（深圳）有限公司 | Document sharing method, device and system |
| CN109471844A (en) * | 2018-10-10 | 2019-03-15 | 深圳市达仁基因科技有限公司 | File sharing method, device, computer equipment and storage medium |
| CN109862098A (en) * | 2019-02-01 | 2019-06-07 | 东软医疗系统股份有限公司 | A kind of method and apparatus that medical image file uploads cloud |
| CN111478951A (en) * | 2020-03-26 | 2020-07-31 | 深圳市鸿合创新信息技术有限责任公司 | File issuing method and device |
| CN112261624A (en) * | 2019-12-31 | 2021-01-22 | 华为技术有限公司 | Method, electronic equipment and system for transmitting file in application |
-
2021
- 2021-05-17 CN CN202110535441.1A patent/CN115378930B/en active Active
Patent Citations (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH11353247A (en) * | 1998-06-05 | 1999-12-24 | Nippon Telegr & Teleph Corp <Ntt> | Method and system for file distribution and storage medium in which file distributing program is stored |
| US6397246B1 (en) * | 1998-11-13 | 2002-05-28 | International Business Machines Corporation | Method and system for processing document requests in a network system |
| CN101860571A (en) * | 2010-06-12 | 2010-10-13 | 中兴通讯股份有限公司 | Method, system and terminal for sending dynamic content distributing service document |
| KR20120110871A (en) * | 2011-03-30 | 2012-10-10 | 주식회사 케이티 | Method for determining and searching storage server in distributed file system |
| CN102148835A (en) * | 2011-04-27 | 2011-08-10 | 许式伟 | Method and system for transmitting and sharing electronic documents |
| US20130073691A1 (en) * | 2011-06-17 | 2013-03-21 | Alibaba Group Holding Limited | File Processing Method, System and Server-clustered System for Cloud Storage |
| CN102571950A (en) * | 2011-12-31 | 2012-07-11 | 华为技术有限公司 | Media content providing and acquiring methods, server and user terminal |
| US8515904B1 (en) * | 2012-03-29 | 2013-08-20 | Emc Corporation | Providing file sytem quota support for a file system having separated data and metadata |
| CN104521289A (en) * | 2012-08-08 | 2015-04-15 | 三星电子株式会社 | Apparatus and method of connecting service according to user intention |
| WO2014161157A1 (en) * | 2013-04-02 | 2014-10-09 | 华为技术有限公司 | File uploading method in cloud storage, client, application server, and cloud storage system |
| WO2015054897A1 (en) * | 2013-10-18 | 2015-04-23 | 华为技术有限公司 | Data storage method, data storage apparatus, and storage device |
| CN105357321A (en) * | 2015-12-11 | 2016-02-24 | 北京元心科技有限公司 | File transmission method based on abstract value, terminal, and file server |
| CN105677778A (en) * | 2015-12-30 | 2016-06-15 | 深圳市鼎芯无限科技有限公司 | Small picture batch processing method, intelligent terminal and server |
| CN107872489A (en) * | 2016-09-28 | 2018-04-03 | 杭州海康威视数字技术股份有限公司 | A kind of file section method for uploading, device and cloud storage system |
| CN108093015A (en) * | 2016-11-21 | 2018-05-29 | 北京京东尚科信息技术有限公司 | Document transmission system |
| CN107070972A (en) * | 2016-12-30 | 2017-08-18 | 中国银联股份有限公司 | A kind of distributed document processing method and processing device |
| US20180232394A1 (en) * | 2017-02-15 | 2018-08-16 | Google Inc. | Systems and methods for providing access to a data file stored at a data storage system |
| CN108737482A (en) * | 2017-04-24 | 2018-11-02 | 腾讯科技（深圳）有限公司 | Document sharing method, device and system |
| CN108280228A (en) * | 2018-02-26 | 2018-07-13 | 北京车和家信息技术有限公司 | A kind of processing method and relevant device of webpage |
| CN109471844A (en) * | 2018-10-10 | 2019-03-15 | 深圳市达仁基因科技有限公司 | File sharing method, device, computer equipment and storage medium |
| CN109862098A (en) * | 2019-02-01 | 2019-06-07 | 东软医疗系统股份有限公司 | A kind of method and apparatus that medical image file uploads cloud |
| CN112261624A (en) * | 2019-12-31 | 2021-01-22 | 华为技术有限公司 | Method, electronic equipment and system for transmitting file in application |
| CN111478951A (en) * | 2020-03-26 | 2020-07-31 | 深圳市鸿合创新信息技术有限责任公司 | File issuing method and device |
Non-Patent Citations (3)
| Title |
|---|
| H. SHEN, G. LIU AND L. WARD: "A Proximity-Aware Interest-Clustered P2P File Sharing System", 《IEEE TRANSACTIONS ON PARALLEL AND DISTRIBUTED SYSTEMS》, vol. 26, no. 6, 30 May 2014 (2014-05-30) * |
| 易建亮, 陈志广, 肖侬, 等: "基于代理的并行文件系统元数据优化与实现", 《计算机研究与发展》, vol. 55, no. 2, 15 May 2018 (2018-05-15) * |
| 肖芳, 周可: "基于文件相关性的云存储缓存策略", 《华中科技大学学报(自然科学版)》, vol. 47, no. 4, 12 April 2019 (2019-04-12) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115378930B (en) | 2024-08-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20170041254A1 (en) | Contextual content sharing using conversation medium | |
| US7801941B2 (en) | Apparatus and method for exchanging data between two devices | |
| CN104581374B (en) | A kind of method, node and server for obtaining section file and generating sub- m3u8 files | |
| JP2009512931A (en) | Retrieve offline instant messages | |
| US9442925B2 (en) | Regulated texting solution for mobile devices | |
| US20100318634A1 (en) | Method and system for sending, receiving and transmitting an offline image and offline image server | |
| CN111368173A (en) | File transmission method and device, electronic equipment and readable storage medium | |
| CN112055078B (en) | Data transmission method, device, computer equipment and storage medium | |
| CN110311855B (en) | User message processing method and device, electronic equipment and storage medium | |
| KR20140027465A (en) | Method, device and system for sharing microblog message | |
| US20170019484A1 (en) | System and method for aggregating communication connections | |
| KR101809365B1 (en) | Message Fragmentation Method using a MQTT Protocol in M2M/IoT Platforms | |
| CN110430126A (en) | Instant communication message processing method, device, system, equipment and storage medium | |
| CN110838969B (en) | Picture transmission method, device, equipment and medium | |
| US20090150506A1 (en) | System, method and device for implementing email notification | |
| WO2014187397A1 (en) | Multimedia message publishing method and device | |
| CN109479026B (en) | Methods, systems, and computer program products for selectively modifying and sending messaging data | |
| CN104378398B (en) | Information issuing method, information output method, device, server and system | |
| CN112714068A (en) | Method, device and system for processing coded image, storage medium and electronic device | |
| CN115378930B (en) | File distribution method and device | |
| CN107370731B (en) | Method and device for realizing communication between different applications based on natural language | |
| CN105978853B (en) | Session scheduling method, scheduling server and terminal | |
| CN111478951B (en) | File issuing method and device | |
| CN107395583B (en) | Method and device for realizing communication between different applications based on natural language | |
| CN114745367A (en) | Data transmission method and device, electronic equipment and storage 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |