WO2009149630A1 - 消息业务中文件传输的实现方法、装置和用户设备 - Google Patents
消息业务中文件传输的实现方法、装置和用户设备 Download PDFInfo
- Publication number
- WO2009149630A1 WO2009149630A1 PCT/CN2009/071237 CN2009071237W WO2009149630A1 WO 2009149630 A1 WO2009149630 A1 WO 2009149630A1 CN 2009071237 W CN2009071237 W CN 2009071237W WO 2009149630 A1 WO2009149630 A1 WO 2009149630A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- file
- user equipment
- network side
- module
- block
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1854—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with non-centralised forwarding system, e.g. chaincast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/06—Message adaptation to terminal or network requirements
- H04L51/066—Format adaptation, e.g. format conversion or compression
Definitions
- the present invention relates to the field of network communication technologies, and in particular, to a device and a user equipment for implementing file transmission in a message service.
- the content provided by the messaging service is increasingly rich.
- the messaging service can provide text, pictures, audio, video, games and the like.
- the embodiment of the present invention provides a method, a device, and a user equipment for implementing file transmission in a message service, which can reduce the data transmission processing burden of the network side device, such as an application server, and improve the file transmission speed in the message service.
- the network side device such as an application server
- a method for implementing file transmission in a message service includes:
- the network side divides the file of the message service that needs to be sent to the user equipment into at least two file blocks;
- the network side transmits the divided file blocks to the at least two user equipments, and sends the notification information of the file blocks to the user equipment, so that the user equipment obtains the unreceived information from the other user equipments.
- the file block to.
- a method for implementing a message service according to an embodiment of the present invention includes:
- the user equipment receives the notification information transmitted by the network side;
- the user equipment establishes a connection with other user equipments according to the notification information, and acquires a file block that is not received from other user equipments;
- the user equipment combines the obtained file blocks into a file of a message service.
- An apparatus for implementing file transmission in a message service includes:
- a dividing module (400), configured to divide a file of a message service that needs to be sent to the user equipment into at least two file blocks;
- a user equipment provided by an embodiment of the present invention includes:
- a second receiving module (500), configured to receive notification information transmitted by the network side;
- the obtaining module (510) is configured to establish a connection with other user equipment according to the notification information received by the second receiving module (500), and obtain, from other user equipments, the user equipment where the user equipment is located is not received from the network side.
- the combination module (520) is used to combine the file blocks obtained by the user equipment in which it is located into a file of the message service.
- the file block processing is performed on the file of the message service, the block (ie, the file block) is sent to the user equipment, and each user equipment is prompted to obtain the corresponding file block from the other user equipment.
- the data transmission processing burden; moreover, the data transmission processing burden of the network side device may not increase as the number of users receiving the message increases.
- the user equipment in the embodiment of the present invention can provide file blocks to other user equipments, so that the file transmission source ends are distributed in multiples, thereby improving the file transmission speed in the message service.
- FIG. 1 is a schematic diagram of an implementation process of file transmission in a message service according to an embodiment of the present invention
- FIG. 2 is a flowchart of an implementation process of file transmission in a message service according to an embodiment of the present invention
- FIG. 3 is a schematic diagram of a device for file transmission in a message service according to an embodiment of the present invention
- FIG. 4 is a schematic diagram of a user equipment according to an embodiment of the present invention.
- the message service referred to in the embodiment of the present invention may be a message service in the IMS domain, or may be a message service in another network domain, for example, a multimedia message service in a circuit domain or a packet domain.
- the network side in the embodiment of the present invention needs to perform block processing on a file in which a plurality of recipients have a message service.
- the message service may be initiated by the user equipment, or may be initiated by the network side, that is, the file of the message service may be sent by the user equipment, or may be provided by the network side (such as the network side. File).
- the files here can be in various forms such as text, pictures, audio, video, games, and more.
- the embodiment of the present invention does not limit the network domain to which the message service belongs, and does not limit the initiator of the message service (ie, the provider of the file that does not restrict the message service), nor does it limit the representation of the file.
- the network side can judge the file size of the message service that needs to be sent to multiple receivers, and determine that the file size is reached.
- the predetermined size value ⁇ the file is divided into blocks; for example, the network side may also judge the file type of the message service that needs to be sent to multiple receivers, and determine that the file type belongs to a predetermined type (such as video),
- the file is subjected to block processing; for example, the network side may also determine the number of recipients of the message service, and after determining that the number of recipients reaches a predetermined number, the file is processed in blocks; and, the network side may also The blocking processing indication carried in the message sent by the user equipment determines to perform block processing on the file.
- the network side may also arbitrarily combine the determination of the file size, the determination of the file type, the determination of the number of recipients, the block processing instruction carried in the message, and the like, and determine whether it is necessary according to the judgment result of the combined content.
- the file is processed in blocks. The reach described in this paragraph can also be exceeded.
- the embodiment of the present invention does not limit the specific implementation process that the network side needs to perform block processing on the file of the message service.
- the network side can divide the file into multiple file blocks, and the number of file blocks can depend on the number of recipients of the message service (ie, the number of recipient user devices) For example, the number of file blocks is equal to the number of recipients; for example, the number of file blocks is equal to the number of recipients plus one.
- the number of file blocks can also depend on other factors, such as pre-set values. and many more.
- the preset value here may be greater than the number of recipients of a certain message service, or may be smaller than the number of recipients of a message service, but the preset value for the number of file blocks should be not less than 2.
- Embodiments of the present invention may further define the number of file blocks. For example, if the number of recipients exceeds a predetermined value, the number of file blocks should be equal to a predetermined value.
- the predetermined value described in this paragraph may be the Transmission Control Protocol (TCP) maximum number of connections of the network side device, or the value set by the management according to the actual operation of the network. Embodiments of the present invention do not limit the specific implementation of setting a predetermined value.
- the network side After the network side performs the block processing on the file of the message service, it needs to send the file block and the notification information to the receiver of the message service, where the notification information is used to notify the user equipment that the device is not received from other user equipments.
- File block The file block and the notification information may be sent to the user equipment together (that is, the file block and the notification information may be sent to the user equipment through a message or a data message), or may be separately sent to the user equipment, that is, the file block and the notification information may be different.
- the message or data message is sent to the user equipment, for example, the notification information is sent first, the file block is sent again, and the like. It should be noted that the user equipment may receive only the notification information, and may receive both the file block and the notification information.
- the file block received by the user equipment may be one file block or multiple file blocks.
- these multiple file blocks can be all file blocks in the file, or they can be partial blocks in the file.
- the network side does not transmit all the file blocks in the file to all recipient user devices, that is, although some Some or some user devices can receive all the file blocks in the file, but not all recipient user devices receive all the file blocks in the file. The following examples illustrate several different situations.
- Example 1 when the number of receivers of the message service is m ⁇ , the network side divides the file of the message service into m file blocks, and sends a file block and notification information to each receiver user equipment, thereby The file blocks are sent to m receivers.
- the file block and the notification information can be sent through the same message or the same data message, or can be sent through different messages or different data messages.
- Example 2 When the number of receivers of the message service is m ⁇ , the network side divides the file of the message service into m file blocks, and sends all file blocks and notification information in the file to one of the receiver user devices. To The other recipient user equipment sends a file block and notification information. Similarly, the file block and the notification information may be sent through the same message or the same data message, or may be sent through different messages or different data messages. In addition, the network side can also send all file blocks and notification information in the file to two (this ⁇ m>2) or three (this ⁇ m>3) recipient user equipment.
- Example 3 When the number of receivers of the message service is m ⁇ , the network side divides the file of the message service into m+1 file blocks, and sends two file blocks and notification information to one of the receiver user devices, The other recipient user equipment sends a file block and notification information.
- m+l here may also be m+2 or m+3, etc., correspondingly, two or three recipient user equipments receive two file blocks and notification information.
- the example 3 here can also be simply transformed into: The network side sends all file blocks and notification information in the file to one or two (this ⁇ m> 2) or three (this ⁇ m>3) recipient user equipment.
- Example 4 When the receiver data of the message service is m ⁇ , the network side divides the file of the message service into m-1 file blocks, and sends only the notification information to one of the receiver user devices to other receivers. The user device sends a file block and notification information.
- m-1 here may also be m-2 or m-3, etc., correspondingly, two or three receiving user equipments only receive notification information.
- Example 4 here can also be simply transformed into: One or two of the network side (this ⁇ m>2) or three (this ⁇ m>3) Receiver User equipment sends all file blocks and notification information in the file.
- the embodiments of the present invention are not limited to the above-exemplified modes, and the network side only needs to ensure that all file blocks are not transmitted to all receivers. Other implementations are not mentioned here by way of example. It should be noted that the network side determines the number of file blocks divided by the file, and determines which file blocks need to be sent to which user equipments.
- the file allocation algorithm can be called a file allocation algorithm.
- the network side may perform block processing on the file of the message service and send and process the file block according to the file allocation algorithm.
- the purpose of the notification information sent by the network side to the receiver user equipment is to enable the user equipment to obtain the file block that is not received by the user equipment from the other user equipment, and the specific content of the notification information may be set according to actual needs, and the notification information
- a specific content may be: user equipment list information, the user equipment list information may include two parts of content, one part of which is the address information of the user equipment, and the other part of which is the file block information received by the user equipment.
- the user equipment list information may include all the recipient user equipments, or only all the receiver user equipments that receive the file blocks, and may only include the received The recipient user device of all file blocks of the message business file.
- the user equipment list information received by each user equipment may be the same or different. For example, for the user equipment 1, the user equipment list information received by the user equipment 1 does not include the address of the user equipment 1.
- File block information can be the byte range of the file block in the entire file
- the network side may carry the notification information in a message of the Session Description Protocol (SDP) and send the SDP message to the user equipment.
- SDP Session Description Protocol
- the network side can also use other messages.
- the embodiment of the present invention does not limit the specific expression of the message, and does not limit the specific manner in which the notification information is carried in the message.
- the user equipment After receiving the notification information transmitted by the network side, the user equipment establishes a connection with other user equipment according to the notification information, and acquires a file block of the message service from the other user equipment by using the established connection.
- the file block obtained by the user equipment from other user equipments is a file block to which the network side does not transmit. Then, the user equipment organizes the obtained file blocks into files of the message service.
- the file block obtained by the user equipment herein may include: a file block sent by the user equipment to the network side, and a file block obtained by the user equipment from the other user equipment; the file block obtained by the user equipment may also include only: the user equipment A block of files obtained from other user devices.
- the user equipment may establish a connection with another user equipment according to the notification information, thereby acquiring all file blocks that are not sent to the network side; the user equipment may also establish a connection with another plurality of user equipments, thereby Get all the file blocks that are not sent to the network side. This depends on the manner in which the network side sends the file block to the user equipment. For example, in the case that the network side sends all the file blocks of the file to the user equipment 1, the other user equipment can obtain the network side unreached by establishing a connection with the user equipment 1.
- the file block sent by the user for example, in the case that the network side divides the file into m file blocks and sends a file block to each of the m user devices, each user device establishes a connection through two or two to obtain the unreceived The remaining m - 1 file block.
- the specific situation of establishing a connection between user equipments is related to how the network side sends file blocks to the user equipment. No other case is given here.
- the embodiment of the present invention does not limit the specific implementation process of establishing a connection between user equipments, and does not limit the specific implementation process of the user equipment to organize each file block into a file of a message service.
- the user equipment may not successfully obtain the text that the network side does not send to the user equipment.
- the user equipment can then request the network side for a file block that it cannot obtain.
- the network side may send the file block to the user equipment according to the request of the user equipment.
- the reason why the user equipment cannot successfully obtain the file block that the network side does not send to the other user equipment may be: the user equipment cannot successfully establish a connection, or the connection is successfully established, but the file block transmission fails. .
- the reason why the user equipment cannot successfully establish a connection may be: user equipment offline, shutdown, and so on.
- the embodiments of the present invention do not limit the reason why the file block cannot be successfully obtained from other user equipments, nor the reasons for the connection establishment failure.
- the foregoing user equipment cannot successfully obtain a file block that is not sent to the network side from another user equipment, and then request a file block from the network side.
- the following may exemplify two cases.
- the user equipment 1 selects the user equipment 2 that receives all the file blocks of the file, and performs establishment with the user equipment 2. Connected operation. After the user equipment 1 fails to establish a connection with the user equipment 2, the user equipment 1 can select the user equipment 3 and perform an operation of establishing a connection with the user equipment 3 to acquire all file blocks that are not sent to the network side. If the user equipment 1 fails to establish a connection with the user equipment 3, the user equipment 1 can request the network side for the file block that it has not obtained. Of course, the user equipment 1 can also directly request the file block that it has not obtained after the connection with the user equipment 2 fails.
- Example 2 In the case that a different file block is sent to each user equipment on the network side, if the user equipment 1 and the user equipment 2 cannot successfully establish a connection, the user equipment 1 requests the user equipment 2 to receive from the network side. The file block to.
- the user equipment may use the request information sent by the existing message to the network side to request the network side to send a file block to the network side, or may send the request information to the network side by using the newly added message.
- embodiments of the present invention may be suitable for the expansion draft-garcia-mmusic-file- transfer-mech-01 protocol to enable transmission between point P 2p user equipment.
- the embodiment of the present invention does not limit the specific implementation process of the user equipment requesting the file block from the network side.
- the network side After receiving the information of the request file block sent by the user equipment, the network side determines the file block requested by the user equipment, and sends the file block to the user equipment. Of course, the network side can also send the file block to each user equipment. The embodiment of the present invention does not limit the protocol and message name used by the network side to send a file block to the user equipment according to the information of the requested file block.
- the network side Since the network side can resend one or some file blocks according to the request of the user equipment, the network side needs to store each file block after sending the file blocks for the first time. The network side may also store the file without storing the file block, and after receiving the request, perform the blocking processing again, and then send the requested file block to the user equipment.
- the network side can perform aging processing on the stored file blocks or files.
- the aging processing method can be any existing aging processing method, and will not be described in detail herein.
- the file block in the above description is a block.
- the embodiment of the present invention introduces a P2P technology (using P2P technology between user equipments) in a file transmission process in a message service, and performs block processing on a message service file.
- the user equipment sends the file block and the notification information, so that each user equipment obtains a file block that is not sent to the network side from the other user equipment, so that the user equipment can obtain the file block obtained from the network side and from other user equipments.
- the file block obtains the file of the complete content, which avoids the process that each user equipment needs to obtain the complete content file from the network side, thereby reducing the data transmission processing burden of the network side device such as the application server.
- the data transmission processing burden of the network side device always sends a message to the network side device.
- the data transmission processing burden, and the data transmission processing burden of the network side device does not increase at all with the increase in the number of users receiving the message. Since the user equipment in the embodiment of the present invention can obtain file blocks from other user equipments, there are multiple source devices for file transmission in the embodiments of the present invention. Since the source end of the Chinese device transmission is distributed in plurality according to the embodiment of the present invention, the embodiment of the present invention can improve the file transmission speed in the message service with respect to the source device of one file transmission.
- the user equipment UE1 sends a message to the server 1, and the recipients of the message are UE2, UE3, and UE4.
- the file of this message is transmitted by UE1 to server 1. Since UE2, UE3, and UE4 are home to server 2, server 1 transmits the received file to server 2. After receiving the file, Server 2 uses Me ssage Session Relay
- MSRP Message Session Propagation Protocol
- the server 2 transmits the file block 1 to the UE 2, and transmits the file block 2 to the UE 3 and transmits the file block 3 to the UE 4.
- the server 2 sends notification information to UE2, UE3, and UE4, respectively, to help establish a connection between UE2, UE3, and UE4.
- a line extension is as follows:
- the address of one of the user equipments is msrp://atlantal.example.com:7654/jshA7we;tcp, the byte range of the file block received by the user equipment in the file is: 1-2048, 2049-4096 .
- the address of another user device is msrp://atlanta2.example.com:6666/jshA7we;tcp, and the byte range of the file block received by the user device in the file is: 6145-8192.
- the UE2, the UE3, and the UE4 After receiving the file block and the notification information, the UE2, the UE3, and the UE4 establish a connection between the UE2 and the UE3, a connection between the UE2 and the UE4, and a connection between the UE3 and the UE4, so that the UE2 obtains the file from the UE3.
- Block 2 obtaining file block 3 from UE4, UE3 acquiring file block 1 from UE2, acquiring file block 3 from UE4, U E4 acquiring file block 1 from UE2, and obtaining file block 2 from UE3.
- UE2, UE3, and UE4 respectively organize the file blocks obtained by the combination, and finally obtain the completion file of the message service.
- the data transmission processing amount of the server 2 is the data transmission processing amount of one file. Although the number of the receiving user equipment is 3, the data transmission processing amount of the server 2 is not three files. The amount of data sent processing.
- step 1.1 the application server AS2 sends a SIP to UE2.
- INVITE invitation
- server information such as server address information, file information such as file name information.
- Step 1.2 AS2 sends SIP to UE3
- INVITE tells UE4 the server information and file information of AS2 through the SDP message.
- steps 1.1, 1.2 and 1.3 can be performed simultaneously, and the order of execution can be adjusted.
- Step 2.1 After receiving the SIP INVITE, UE2 replies to SIP2 with SIP 200.
- UE2's own information is the address information of UE2.
- Step 2.2 After receiving the SIP INVITE, UE3 replies to SIP2 with SIP 200.
- Step 2.3 After receiving the SIP INVITE, UE4 replies to SIP2 with SIP 200.
- Step 3.1 After receiving the SIP 200 OK returned by UE2, AS2 replies with an ACK response to UE2.
- Step 3.2 After receiving the SIP 200 OK returned by UE3, AS2 replies with an ACK response to UE3.
- Step 3.3 After receiving the SIP 200 OK returned by UE4, AS2 replies with an ACK response to UE4.
- Step 4.1 AS2 sends the user list information to the UE through the extended SDP message (such as RE-INVITE)
- Step 4.2 AS2 sends the user list information to the UE through the extended SDP message (such as RE-INVITE).
- the extended SDP message such as RE-INVITE
- Step 4.3 AS2 sends the user list information to the UE through an extended SDP message (such as RE-INVITE).
- an extended SDP message such as RE-INVITE
- Extended a line: a user-selector: ⁇ 3 ⁇ 4 address and file block>, its specific meaning is as follows:
- the listening address of UE2 is: msrp://atlantal.example.com:7654/jshA7we;tcp
- the file block owned by UE2 is: byte-range:" 1-2048,2049-4096,4097-6145"
- the listening address of UE3 is: msrp: ⁇ atlanta2.example.com:6666/jshAlhe;tcp
- the file block owned by UE3 is: byte-range: "6146-8192,8193-10240,10241-12288"
- the listening address of UE4 is: msrp: ⁇ atlanta3.example.com:8888/jshA2his;tcp
- the file block owned by UE4 is: byte-range: "12289-14336, 14337-16384, 16385-18432" [97]
- the above listening address is the address information of UE2, and the above-mentioned file block is the user equipment from the network side. Received file block information.
- Step 5.1 After receiving the RE-INVITE, UE2 replies to AS2 with a SIP 200 OK response.
- Step 5.2 After receiving the RE-INVITE, UE3 replies to AS2 with a SIP 200 OK response.
- Step 5.3 After receiving the RE-INVITE, UE4 replies to the SIP 200 OK response to AS2.
- Step 6.1 After receiving the SIP 200 OK returned by UE2, AS2 replies with an ACK response to UE2.
- Step 6.2 After receiving the SIP 200 OK returned by the UE3, the AS2 replies with an ACK response to the UE3.
- Step 6.3 After receiving the SIP 200 OK returned by UE4, AS2 replies with an ACK response to UE4.
- AS2 and each UE establish a TCP connection with each other, and AS2 can send a file block to each U E through MSRP.
- Step 7.1 AS2 sends a file block of byte-range: 1-2048, byte-range: 2049-4096, byte-range: 4097-6145 to UE2 through MSRP.
- Step 7.2 AS2 sends byte-range to 6 through MSRP: 6146-8192, byte-range: 8193-102 40, byte-range: File blocks of 10241-12288.
- Step 7.3 AS2 sends a byte-range to the UE4 through MSRP: 12289-14336, byte-range: 14337-
- Step 8.1 After receiving the file block, UE2 replies to AS2 with an MSRP 200 OK response.
- Step 8.2 After receiving the file block, UE3 replies to AS2 with an MSRP 200 OK response.
- Step 9.1 UE2 and UE3 exchange the received file blocks with each other according to the received user list information.
- Step 9.2 UE2 and UE4 exchange the received file blocks with each other according to the received user list information.
- Step 9.3 The UE3 and the UE4 exchange the received file blocks with each other according to the received user list information.
- Step 10.1 After UE2 and UE3 exchange file blocks, they send MSRP 200 OK responses to each other.
- Step 10.2 After UE2 and UE4 exchange file blocks, they send MSRP 200 OK responses to each other.
- the file block is successfully obtained (such as UE2)
- other UEs such as UE3, UE4
- the UE can use the existing draft-garcia-mmusic-file-transfer-mech-01 protocol to implement the process of requesting a file block from AS2.
- the number of receiving user equipments in FIG. 2 is described by taking 3 as an example.
- a connection may be established with a part of the UE, and then the UE is notified to establish a connection, so that the file block can be transmitted between the UEs.
- FIG. 3 An apparatus for implementing file transmission in a message service according to an embodiment of the present invention is shown in FIG. 3.
- the device is disposed in the network side device, and can be set in the application server.
- the device in FIG. 3 includes: a dividing module 400 and a sending module 410.
- the device may also optionally include: a first receiving module 420 and a determining module 430.
- the dividing module 400 in the network side device divides the file of the message service into at least two file blocks.
- the message service here may be a message service in the IMS domain, or may be a message service in another network domain, and the message service may be initiated by the user equipment or initiated by the network side.
- the files here can be in various forms such as text, pictures, audio, video, games, and so on.
- the dividing module 400 may determine whether the file of the message service is subjected to blocking processing, and the dividing module 400 may determine the number of file blocks divided by the file according to the file allocation algorithm. Specifically, it is as described in the above method embodiment.
- the partitioning module 400 can include a determined number of sub-modules 401, an assignment sub-module 403, and a partitioning sub-module 402.
- the determined quantity sub-module 401 determines the number m of recipient user devices in the local area of the message service, and outputs m, which is greater than one.
- the determined quantity sub-module 401 can also output m by other means, for example, the output m is the number of receivers plus 1, and for example, the number quantum module 401 outputs a preset value. Specifically, the description of the above method embodiments.
- the dividing sub-module 402 performs block processing on the file of the message service according to the m output by the determined number of sub-modules 401.
- the value outputted by the quantity sub-module 401 may be checked by the evaluation sub-module 403. For example, the evaluation sub-module 403 determines that the output of the determined quantity sub-module 401 exceeds a predetermined value, and assigns m to a predetermined value. And transmitting the modified m to the dividing sub-module 402.
- the predetermined value here may be the maximum number of transmission control protocol connections of the network side device, or may be a value set by the management party according to the actual operation of the network, as described in the foregoing method implementation manner.
- the sending module 410 transmits the at least two file blocks divided by the dividing module 400 to the at least two user equipments.
- the sending module 410 needs to send, to the user equipment, notification information for acquiring a file block from the user equipment, where the notification information is used to notify the user equipment to obtain a file block that is not received from other user equipment.
- the sending module 410 sends the file block and the notification information to the user equipment in various manners.
- the file block and the notification information may be sent to the user equipment through a message or a data message, and the file block and the notification information may pass different messages.
- the data packet is sent to the user equipment, such as sending a notification message to the user equipment, then sending a file block, and the like.
- the sending module 410 may send the notification information to only one user equipment, and may send the file block and the notification information to the user equipment, and the file block sent to a user equipment may be a file block. It can also be multiple file blocks.
- the sending module 410 can determine which file blocks need to be sent to which user equipment according to the file allocation algorithm. Specifically, it is as described in the above method embodiment.
- the first receiving module 420 receives the information of the request file block sent by the user equipment, and the determining module 430 determines the file block requested by the user equipment according to the information received by the first receiving module 420, and notifies the sending module 41 0 to send the user.
- the file block requested by the device may notify the sending module 410 to send a file block to a certain user equipment, and may also notify the sending module 410 to send a file block to multiple user equipments, such as sending a requested file block to each user equipment, etc., as described in the foregoing method implementation manner. Description in .
- the storage module in the device needs to store each file block sent, and the storage module in the device may not store the file block.
- the determining module 430 notifies the dividing module 400 to perform the blocking processing again, and then the determining module 430 notifies the sending module 410 to send a request to some or some user equipments.
- File block The device may include an aging processing module to perform aging processing on the file blocks or files stored in the storage module.
- the aging processing module may perform aging processing by using various existing aging processing methods, and details are not described herein.
- the user equipment provided by the embodiment of the present invention is as shown in FIG.
- the user equipment in FIG. 4 includes: a second receiving module 500, an obtaining module 510, and a combining module 520.
- the user equipment may also optionally include a request module 530.
- the second receiving module 500 receives the information transmitted by the network side, and the information may be notification information, or may be File blocks and notifications, of course, can also be all file blocks.
- the obtaining module 510 establishes a connection with other user equipments according to the notification information received by the second receiving module 500, and acquires, from other user equipments, the file blocks that the second receiving module 500 does not receive from the network side.
- the obtaining module 510 can establish a connection with another user equipment according to the notification information, so as to obtain all the file blocks that the network side does not send to the user equipment where the network side is located; the obtaining module 510 can also establish a connection with another multiple user equipment according to the notification information to obtain All file blocks that the network side did not send to its user device. This depends on the algorithm by which the network side sends file blocks to the user equipment, as described in the above method embodiments.
- the combining module 520 combines the file blocks obtained by the user equipment in which it is located into a file of the message service.
- the file block obtained by the user equipment of the combination module 520 may be only all the file blocks sent by the network side received by the second receiving module 500, or may be the file block and the network block sent by the second receiving module 500.
- the file blocks obtained by the module 510 from other user devices may also be only all file blocks acquired by the module 510 from other user devices.
- the requesting module 530 determines that the obtaining module 510 cannot successfully obtain the file block from the other user equipment, and requests the network side to the file block that cannot be successfully acquired. There are various reasons why the obtaining module 510 cannot successfully obtain file blocks that are not sent to the network side from other user equipments, as described in the foregoing method embodiments.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
公开了消息业务中文件传输的实现方法、装置和用户设备。属于消息传输技术领域。其中,消息业务中文件传输的实现方法包括:网络侧将需要发送至用户设备的消息业务的文件划分成至少两个文件块;网络侧将所述划分后的文件块分别向至少两个用户设备传输,并向用户设备下发获取文件块的通知信息,以使所述用户设备从其它用户设备处获取其未接收到的文件块。上述技术方案在用户设备间采用了P2P技术,减轻了网络侧设备如应用服务器的数据发送处理负担,提高了消息业务中的文件传输速度。
Description
说明书 消息业务中文件传输的实现方法、 装置和用户设备
[I] 本申请要求于 2008年 6月 12日提交中国专利局、 申请号为 200810110650.6、 发明 名称为 "消息业务中文件传输的实现方法、 装置和用户设备"的中国专利申请的优 先权, 其全部内容通过引用结合在本申请中。
[2] 技术领域
[3] 本发明涉及网络通讯技术领域, 具体涉及一种消息业务中文件传输的实现方法 装置和用户设备。
[4] 发明背景
[5] 目前, 消息业务提供的内容日益丰富, 例如, 消息业务能够提供文字、 图片、 音频、 视频、 游戏等内容。
[6] 在服务器需要向多个用户发送同一内容的文件吋, 多个用户均需要从服务器处 获取完整内容的文件。 服务器需要向多个用户发送的同一内容的文件可以是用 户设备提供的, 也可以是服务器提供的。
[7] 发明人发现目前的消息业务中文件传输的过程至少存在如下问题: 由于服务器 需要向多个用户设备发送完整内容的文件, 因此, 服务器的数据发送处理负担 重, 而且, 服务器的数据发送处理负担会随着接收消息的用户数量的增多而增 加。
[8] 发明内容
[9] 本发明实施方式提供一种消息业务中文件传输的实现方法、 装置和用户设备, 可减轻网络侧设备如应用服务器的数据发送处理负担, 提高了消息业务中的文 件传输速度。
[10] 本发明实施方式提供的一种消息业务中文件传输的实现方法, 包括:
[I I] 网络侧将需要发送至用户设备的消息业务的文件划分成至少两个文件块;
[12] 网络侧将所述划分后的文件块分别向至少两个用户设备传输, 并向用户设备下 发获取文件块的通知信息, 以使所述用户设备从其它用户设备处获取其未接收 到的文件块。
[13] 本发明实施方式提供的一种消息业务实现方法, 包括:
[14] 用户设备接收网络侧传输来的通知信息;
[15] 所述用户设备根据所述通知信息与其它用户设备建立连接, 并从其它用户设备 处获取其未接收到的文件块;
[16] 所述用户设备将获得的文件块组合为消息业务的文件。
[17] 本发明实施方式提供的一种消息业务中文件传输的实现装置, 包括:
[18] 划分模块 (400) , 用于将需要发送至用户设备的消息业务的文件划分成至少 两个文件块;
[19] 发送模块 (410) , 用于将所述划分模块 (400) 划分成的文件块分别向至少两 个用户设备传输, 并向用户设备下发获取文件块的通知信息, 以使所述用户设 备从其它用户设备处获取其未接收到的文件块。
[20] 本发明实施方式提供的一种用户设备, 包括:
[21] 第二接收模块 (500) , 用于接收网络侧传输来的通知信息;
[22] 获取模块 (510) , 用于根据所述第二接收模块 (500) 接收到的通知信息与其 它用户设备建立连接, 并从其它用户设备处获取其所在用户设备未从网络侧接 收到的文件块;
[23] 组合模块 (520) , 用于将其所在用户设备获得的文件块组合为消息业务的文 件。
[24] 通过上述技术方案的描述可知, 通过对消息业务的文件进行划分文件块处理、 向用户设备发送块 (即文件块) , 并促使各用户设备从其它用户设备处获取相 应的文件块, 使用户设备能够利用从其它用户设备处获取的文件块获得消息业 务的完整内容的文件, 避免了各用户设备均需要从网络侧获取完整内容的文件 的过程, 从而减轻了网络侧设备如应用服务器的数据发送处理负担; 而且, 网 络侧设备的数据发送处理负担可以不随着接收消息的用户数量的增多而增加。 另外, 由于本发明实施方式中的用户设备可以向其它用户设备提供文件块, 使 文件传输源端分布为多个, 从而提高了消息业务中的文件传输速度。
[25] 附图简要说明
[26] 图 1是本发明实施方式的消息业务中文件传输的实现过程示意图;
[27] 图 2是本发明实施方式的消息业务中文件传输的实现过程流程图;
[28] 图 3是本发明实施方式的消息业务中文件传输的装置示意图;
[29] 图 4是本发明实施方式的用户设备示意图。
[30] 实施本发明的方式
[31] 本发明实施方式中所称的消息业务可以是 IMS域中的消息业务, 也可以是其它 网络域中的消息业务, 例如, 电路域或分组域中的多媒体消息业务等。 本发明 实施方式中的网络侧需要对存在多个接收方的消息业务的文件进行分块处理。 这里的消息业务可以是用户设备发起的, 也可以是网络侧主动发起的, 也就是 说, 该消息业务的文件可以是用户设备发送来的, 也可以是网络侧主动提供的 (如网络侧发布文件) 。 这里的文件可以为文本、 图片、 音频、 视频、 游戏等 多种形式。 本发明实施方式不限制消息业务所属的网络域, 不限制消息业务的 发起方 (即不限制消息业务的文件的提供方) , 也不限制文件的表现形式。
[32] 是否对消息业务的文件进行分块处理可以由网络侧根据判断结果来确定, 例如 , 网络侧可以对需要发送至多个接收方的消息业务的文件大小进行判断, 在确 定出文件大小达到预定大小值吋, 对文件进行分块处理; 再例如, 网络侧也可 以对需要发送至多个接收方的消息业务的文件类型进行判断, 在确定出文件类 型属于预定类型 (如视频) 吋, 对文件进行分块处理; 再例如, 网络侧也可以 对消息业务的接收方数量进行判断, 在确定出接收方数量达到预定数量值吋, 对文件进行分块处理; 还有, 网络侧也可以根据用户设备发送来的消息中携带 的分块处理指示来确定对文件进行分块处理。 而且, 网络侧也可以将上述文件 大小的判断、 文件类型的判断、 接收方数量的判断、 消息中携带的分块处理指 示等任意组合, 并根据组合后的内容的判断结果来确定是否需要对文件进行分 块处理。 本段中描述的达到也可以为超过。 本发明实施方式不限制网络侧确定 出需要对消息业务的文件进行分块处理的具体实现过程。
[33] 在网络侧对消息业务的文件进行分块处理过程中, 网络侧可以将文件分成多个 文件块, 文件块的数量可以取决于消息业务的接收方数量 (即接收方用户设备 数量) , 例如, 文件块的数量等于接收方数量; 再例如, 文件块的数量等于接 收方数量加 1等。 文件块的数量也可以取决于其它因素, 例如, 预先设定的数值
等等。 这里的预先设定的数值可以大于某消息业务的接收方数量, 也可以小于 某消息业务的接收方数量, 但是为文件块的数量预先设定的数值应该不小于 2。
[34] 在文件块的数量取决于消息业务的接收方数量的情况下, 考虑到接收方数量可 能会过大或存在其它因素的限制条件 (如文件块的大小不应小于预定大小等) , 本发明实施方式可以对文件块的数量进行进一步的限定, 例如, 在接收方数 量超过预定值吋, 文件块的数量应该等于预定值。 本段中描述的预定值可以为 网络侧设备的传输控制协议 (TCP) 最大连接数, 也可以是管理方根据网络的实 际运行情况设定的数值。 本发明实施方式不限制设定预定值的具体实现方式。
[35] 网络侧在将消息业务的文件进行分块处理后, 需要向该消息业务的接收方发送 文件块和通知信息, 该通知信息用于通知用户设备从其它用户设备处获取其未 接收到的文件块。 文件块和通知信息可以一起发送至用户设备 (即文件块和通 知信息可以通过一条消息或一个数据报文发送至用户设备) , 也可以分别发送 至用户设备, 即文件块和通知信息可以通过不同的消息或数据报文发送至用户 设备, 例如, 先发送通知信息、 再发送文件块等。 需要说明的是, 用户设备可 以仅接收到通知信息, 也可以既接收到文件块又接收到通知信息, 而且, 用户 设备接收到的文件块可以为一个文件块、 也可以为多个文件块。 当用户设备接 收到多个文件块吋, 这多个文件块可以是文件中的所有文件块, 也可以是文件 中的部分块。 当某个或某些用户设备接收到的多个文件块是文件中的所有文件 块吋, 网络侧不会向所有的接收方用户设备均传输文件中的所有文件块, 也就 是说, 虽然某个或某些用户设备可以接收到文件中的所有文件块, 但是并不是 所有的接收方用户设备均接收到文件中的所有文件块。 下面例举几种不同的情 况。
[36] 例 1, 当消息业务的接收方数量为 m吋, 网络侧将该消息业务的文件分成 m个文 件块, 并向每个接收方用户设备发送一个文件块和通知信息, 从而将 m个文件块 分别发送到 m个接收方。 此吋, 文件块和通知信息可以通过同一个消息或同一个 数据报文发送, 也可以通过不同的消息或不同的数据报文发送。
[37] 例 2, 当消息业务的接收方数量为 m吋, 网络侧将该消息业务的文件分成 m个文 件块, 并向其中一个接收方用户设备发送文件中的所有文件块和通知信息, 向
其它接收方用户设备发送一个文件块和通知信息。 同样的, 文件块和通知信息 可以通过同一消息或同一个数据报文发送, 也可以通过不同的消息或不同的数 据报文发送。 另外, 网络侧也可以向其中两个 (此吋 m>2) 或三个 (此吋 m>3) 接收方用户设备发送文件中的所有文件块和通知信息。
[38] 例 3、 当消息业务的接收方数量为 m吋, 网络侧将该消息业务的文件分成 m+ l 个文件块, 并向其中一个接收方用户设备发送两个文件块和通知信息, 向其它 接收方用户设备发送一个文件块和通知信息。 另外, 这里的 m+ l也可以为 m + 2 或 m + 3等, 相应的, 其中两个或三个接收方用户设备接收到两个文件块和通知 信息。 这里的例 3也可以简单变换为: 网络侧向其中一个或两个 (此吋 m>2) 或 三个 (此吋 m>3) 接收方用户设备发送文件中的所有文件块和通知信息。
[39] 例 4、 当消息业务的接收方数据为 m吋, 网络侧将该消息业务的文件分成 m— 1 个文件块, 并向其中一个接收方用户设备仅发送通知信息, 向其它接收方用户 设备发送一个文件块和通知信息。 另外, 这里的 m— 1也可以为 m— 2或 m— 3等, 相应的, 其中两个或三个接收方用户设备仅接收到通知信息。 这里的例 4也可以 简单变换为: 网络侧向其中一个或两个 (此吋 m>2) 或三个 (此吋 m>3) 接收方 用户设备发送文件中的所有文件块和通知信息。
[40] 本发明实施方式不限于上述例举的方式, 网络侧只需要保证没有向所有的接收 方发送所有的文件块即可。 其它实现方式在此不再逐一例举。 需要说明的是, 上述网络侧确定文件划分的文件块数、 以及确定需要向哪些用户设备发送怎样 的文件块可以称为文件分配算法, 文件分配算法的表现形式是多种多样的, 也 就是说, 网络侧可以根据文件分配算法来对消息业务的文件进行分块处理、 以 及文件块的发送处理。
[41] 网络侧向接收方用户设备发送的通知信息的目的是使用户设备从其它用户设备 处获取其未接收到的文件块, 该通知信息的具体内容可以根据实际需要来设定 , 通知信息的一种具体内容可以为: 用户设备列表信息, 用户设备列表信息可 以包括两部分内容, 一部分内容为用户设备的地址信息, 另一部分内容为用户 设备接收到的文件块信息。 用户设备列表信息中可以包括所有的接收方用户设 备, 也可以仅包括所有接收到文件块的接收方用户设备, 还可以仅包括接收到
消息业务文件的所有文件块的接收方用户设备。 另外, 每个接收方用户设备接 收到的用户设备列表信息可以相同, 也可以不相同, 例如, 针对用户设备 1而言 , 用户设备 1接收到的用户设备列表信息中不包括用户设备 1的地址信息和用户 设备 1接收到的文件块信息。 文件块信息可以为文件块在整个文件中的字节范围
, 也可以为文件块编号标识等等。
[42] 网络侧可以将通知信息携带在会话描述协议 (SDP) 的消息中, 并向用户设备 发送该 SDP消息。 当然, 网络侧也可以釆用其它消息, 本发明实施方式不限制消 息的具体表现形式, 也不限制通知信息在消息中具体携带方式。
[43] 用户设备在接收到网络侧传输来的通知信息后, 根据该通知信息与其它用户设 备建立连接, 并利用建立好的连接从其它用户设备处获取消息业务的文件块。 该用户设备从其它用户设备处获取到的文件块是网络侧未向其传输的文件块。 然后, 用户设备将获得的各文件块整理组合为消息业务的文件。 这里的用户设 备获得的文件块可以包括: 用户设备接收的网络侧向其发送的文件块、 以及用 户设备从其它用户设备处获取的文件块; 用户设备获得的文件块也可以仅包括 : 用户设备从其它用户设备处获取的文件块。 而且, 在上述描述中, 用户设备 根据通知信息可以与另外一个用户设备建立连接, 从而获取到网络侧未向其发 送的所有文件块; 用户设备也可以通过与另外多个用户设备建立连接, 从而获 取到网络侧未向其发送的所有文件块。 这取决于网络侧向用户设备发送文件块 的方式, 例如, 在网络侧向用户设备 1发送文件的所有文件块的情况下, 其它用 户设备可以通过与用户设备 1建立连接来获取网络侧未向其发送的文件块; 再例 如, 在网络侧将文件划分为 m文件块, 并向 m个用户设备均发送一个文件块的情 况下, 各用户设备通过两两间建立连接, 以获取其未接收到的其余 m - 1个文件 块。 用户设备间建立连接的具体情况与网络侧如何向用户设备发送文件块相关 , 在此不再对各种不同的情况进行一一例举。 本发明实施方式不限制用户设备 间建立连接的具体实现过程, 也不限制用户设备将各文件块整理组合为消息业 务的文件的具体实现过程。
[44] 在用户设备从其它用户设备处获取网络侧未向其发送的文件块的过程中, 可能 会存在该用户设备不能够成功的从其它用户设备处获取网络侧未向其发送的文
件块的情况, 在这种情况下, 用户设备可以再向网络侧请求其不能够获得的文 件块。 网络侧可以根据用户设备的请求向用户设备发送该文件块。
[45] 用户设备不能够成功的从其它用户设备处获取网络侧未向其发送的文件块的原 因可以为: 用户设备间不能够成功建立连接, 或者虽然连接成功建立, 但是文 件块传输失败等。 用户设备间不能够成功建立连接的原因可以为: 用户设备下 线、 关机等。 本发明实施方式不限制不能够成功从其它用户设备处获取文件块 的原因, 也不限制连接建立失败的原因等。
[46] 上述用户设备不能够成功的从其它用户设备处获取网络侧未向其发送的文件块 、 之后向网络侧请求文件块的情况可以为多种, 下面简单例举两种情况。
[47] 例 1, 在网络侧向用户设备 2、 用户设备 3发送文件的所有文件块的情况下, 用 户设备 1选择接收到文件的所有文件块的用户设备 2, 并执行与用户设备 2建立连 接的操作。 在用户设备 1与用户设备 2建立连接失败后, 用户设备 1可以选择用户 设备 3, 并执行与用户设备 3建立连接的操作, 以获取网络侧未向其发送的所有 文件块。 如果用户设备 1与用户设备 3建立连接也失败, 则用户设备 1可以向网络 侧请求其未获得的文件块。 当然, 用户设备 1也可以在与用户设备 2建立连接失 败后, 直接向网络侧请求其未获得的文件块。
[48] 例 2、 在网络侧向每个用户设备均发送一个不同文件块的情况下, 如果用户设 备 1与用户设备 2不能够成功建立连接, 则用户设备 1向网络侧请求用户设备 2接 收到的文件块。
[49] 用户设备可以利用现有的消息向网络侧发送的请求信息, 以请求网络侧向其发 送某文件块, 也可以利用新增加的消息向网络侧发送请求信息。 例如, 本发明 实施方式可以对 draft-garcia-mmusic-file-transfer-mech-01协议进行适当的扩充, 以实现用户设备间的点到点 P2p传输。 本发明实施方式不限制用户设备向网络侧 请求文件块的具体实现过程。
[50] 网络侧在接收到用户设备发送来的请求文件块的信息后, 确定该用户设备请求 的文件块, 并向该用户设备发送文件块。 当然, 网络侧也可以向各用户设备均 发送该文件块。 本发明实施方式不限制网络侧根据请求文件块的信息向用户设 备发送文件块所釆用的协议及消息名称。
[51] 由于网络侧可以根据用户设备的请求再次发送某个或某些文件块, 因此, 网络 侧在第一次发送了各文件块后, 需要存储各文件块。 网络侧也可以不存储文件 块而存储文件, 在接收到请求后, 再次进行分块处理, 然后再向用户设备发送 请求的文件块。 网络侧可以对存储的文件块或文件进行老化处理, 老化处理的 方法可以为现有的多种老化处理方法, 在此不再详细说明。 上述描述中的文件 块即块。
[52] 通过上述描述可知, 本发明实施方式在消息业务中的文件传输过程中引入了 P2 P技术 (在用户设备之间釆用 P2P技术) , 通过对消息业务的文件进行分块处理 、 向用户设备发送文件块和通知信息, 促使各用户设备从其它用户设备处获取 网络侧未向其发送的文件块, 从而使用户设备能够根据从网络侧获取的文件块 、 以及从其它用户设备处获取的文件块获得完整内容的文件, 避免了各用户设 备均需要从网络侧获取完整内容文件的过程, 从而减轻了网络侧设备如应用服 务器的数据发送处理负担。 在网络侧向各用户设备均发送一个不同的文件块、 且用户设备能够从其它用户设备处成功获取其它文件块的情况下, 网络侧设备 的数据发送处理负担始终为网络侧设备发送一个消息的数据发送处理负担, 且 网络侧设备的数据发送处理负担完全不随着接收消息的用户数量的增多而增加 。 由于本发明实施方式中的用户设备可以从其它用户设备处获取文件块, 因此 , 本发明实施方式中存在多个文件传输的源端设备。 由于本发明实施方式中文 件传输的源端分布为多个, 因此, 相对于一个文件传输的源端设备来说, 本发 明实施方式能够提高消息业务中的文件传输速度。
[53] 下面结合附图对本发明实施方式提供的消息业务实现方法进行说明。
[54] 消息业务实现过程如附图 1所示。
[55] 图 1中, 用户设备 UE1向服务器 1发送消息, 该消息的接收方为 UE2、 UE3和 UE 4。 该消息的文件由 UE1传输至服务器 1。 由于 UE2、 UE3和 UE4归属服务器 2, 因 此, 服务器 1将接收到的文件发送至服务器 2。 服务器 2接收到该文件后, 利用 Me ssage Session Relay
Protocol (消息会话传播协议, MSRP) 协议将文件分成 3个文件块一文件块 1
、 文件块 2和文件块 3 (本实施例中以每个文件块均为三分之一文件为例) 。 月艮
务器 2向 UE2发送文件块 1、 向 UE3发送文件块 2、 向 UE4发送文件块 3。 同吋, 月艮 务器 2分别向 UE2、 UE3和 UE4发送通知信息, 以帮助 UE2、 UE3和 UE4之间建立 连接。
[56] 服务器 2可以对 SDP信息进行扩展, 以发送文件块和通知信息, 例如扩展 a行, 使&=^^-^1^¾)1":<地址和文件块 >, 其中的地址为用户设备地址, 文件块为该用 户设备接收到的文件块信息。 一个具体的 a行扩展例子如下所示:
[57] a=user-selector:path:"msrp://atlantal.example.com:7654/jshA7we;tcp"
[58] byte-range:" 1-2048,2049-4096"
[59] a=user-selector:path:"msrp://atlanta2.example.com:6666/jshA7we;tcp"
[60] byte-range:"6145-8192"
[61] 其中一个用户设备的地址为 msrp://atlantal.example.com:7654/jshA7we;tcp, 该用 户设备接收到的文件块在文件中的字节范围为: 1-2048, 2049-4096。 另一个用 户设备的地址为 msrp://atlanta2.example.com:6666/jshA7we;tcp, 该用户设备接收 到的文件块在文件中的字节范围为: 6145-8192。
[62] UE2、 UE3和 UE4在接收到文件块和通知信息后, 建立 UE2与 UE3之间的连接、 UE2与 UE4之间的连接、 UE3与 UE4之间的连接, 从而 UE2从 UE3处获取文件块 2 、 从 UE4处获取文件块 3, UE3从 UE2处获取文件块 1、 从 UE4处获取文件块 3, U E4从 UE2处获取文件块 1、 从 UE3处获取文件块 2。 UE2、 UE3和 UE4分别整理组 合其获得的文件块, 最终得到消息业务的完成文件。
[63] 从该图的描述中可知, 服务器 2的数据发送处理量为一个文件的数据发送处理 量, 虽然接收方用户设备数量为 3, 但是服务器 2的数据发送处理量并不是 3个文 件的数据发送处理量。
[64] 本发明实施方式的消息业务具体实现过程如附图 2所示。
[65] 图 2中, 在步骤 1.1、 应用服务器 AS2向 UE2发送 SIP
INVITE (邀请) , 并将 AS2的服务器信息和文件信息通过 SDP消息告诉 UE2。 服 务器信息例如服务器地址信息, 文件信息例如文件名信息。
[66] 步骤 1.2、 AS2向 UE3发送 SIP
INVITE, 并将 AS2的服务器信息和文件信息通过 SDP消息告诉 UE3。
步骤 1.3、 AS2向 UE4发送 SIP
INVITE, 并将 AS2的服务器信息和文件信息通过 SDP消息告诉 UE4。
需要说明的是, 上述步骤 1.1、 1.2和 1.3可以同吋执行, 也可以调整执行的先后 顺序。
[69] 步骤 2.1、 UE2接收到 SIP INVITE后, 向 AS2回复 SIP 200
OK, 以将自己的信息告诉 AS2。 UE2自己的信息如 UE2的地址信息。
[70] 步骤 2.2、 UE3接收到 SIP INVITE后, 向 AS2回复 SIP 200
OK, 以将自己的信息告诉 AS2。
[71] 步骤 2.3、 UE4接收到 SIP INVITE后, 向 AS2回复 SIP 200
OK, 以将自己的信息告诉 AS2。
[72] 步骤 3.1、 AS2在接收到 UE2返回的 SIP 200 OK后, 向 UE2回复 ACK应答。
[73] 步骤 3.2、 AS2在接收到 UE3返回的 SIP 200 OK后, 向 UE3回复 ACK应答。
[74] 步骤 3.3、 AS2在接收到 UE4返回的 SIP 200 OK后, 向 UE4回复 ACK应答。
[75] 步骤 4.1、 AS2将用户列表信息通过扩展的 SDP消息 (如 RE-INVITE) 发送给 UE
2。
步骤 4.2、 AS2将用户列表信息通过扩展的 SDP消息 (如 RE-INVITE) 发送给 UE
3。
步骤 4.3、 AS2将用户列表信息通过扩展的 SDP消息 (如 RE-INVITE) 发送给 UE
4。
扩展了 a行的 SDP消息的具体格式如:
v=0
o=altanta 2890844526 2890844526 IN IP4 altantapc.example.com
s=
c=IN IP4 alicepc.example.com
t=0 0
m=message 7654 TCP/MSRP *
a=accept- types: image/jpeg
a=file-selector:hash:SHA:72245FE8653DDAF371362F86D471913EE4A2CE2E
[87] a=user-selector:path:"msrp://atlantal.example.com:7654/jshA7we;tcp" byte-range:" l-2048,2049-4096,4097-6145"
[88] a=user-selector:path:"msrp://atlanta2.example.com:6666/jshAlhe;tcp"
byte-range: "6146-8192,8193- 10240, 10241- 12288"
[89] a=user-selector:path:"msrp://atlanta3.example.com:8888/jshA2his;tcp"
byte-range:" 12289-14336,14337-16384, 16385-18432"
[90] 其中: 扩展的 a行: a= user-selector:<¾址和文件块 >, 其具体意义如下:
[91] UE2的监听地址是: msrp://atlantal.example.com:7654/jshA7we;tcp
[92] UE2拥有的文件块是: byte-range:" 1-2048,2049-4096,4097-6145"
[93] UE3的监听地址是: msrp:〃 atlanta2.example.com:6666/jshAlhe;tcp
[94] UE3拥有的文件块是: byte-range:"6146-8192,8193-10240,10241-12288"
[95] UE4的监听地址是: msrp:〃 atlanta3.example.com:8888/jshA2his;tcp
[96] UE4拥有的文件块是: byte-range:" 12289-14336,14337-16384, 16385-18432" [97] 上述监听地址即 UE2的地址信息, 上述拥有的文件块即用户设备从网络侧接收 到的文件块信息。
[98] 需要说明的是, 上述步骤 4.1、 4.2和 4.3可以同吋执行, 也可以调整执行的先后 顺序。
[99] 步骤 5.1、 UE2接收到 RE-INVITE后, 向 AS2回复 SIP 200 OK应答。
[100] 步骤 5.2、 UE3接收到 RE-INVITE后, 向 AS2回复 SIP 200 OK应答。
[101] 步骤 5.3、 UE4接收到 RE-INVITE后, 向 AS2回复 SIP 200 OK应答。
[102] 步骤 6.1、 AS2在接收到 UE2返回的 SIP 200 OK后, 向 UE2回复 ACK应答。
[103] 步骤 6.2、 AS2在接收到 UE3返回的 SIP 200 OK后, 向 UE3回复 ACK应答。
[104] 步骤 6.3、 AS2在接收到 UE4返回的 SIP 200 OK后, 向 UE4回复 ACK应答。
[105] 至此, AS2和各个 UE之间均互相建立了 TCP连接、 且 AS2可以通过 MSRP向各 U E发送文件块。
[106] 步骤 7.1、 AS2通过 MSRP向 UE2发送 byte-range: 1-2048、 byte-range:2049-4096、 byte-range:4097-6145的文件块。
[107] 步骤 7.2、 AS2通过 MSRP向 UE3发送 byte-range:6146-8192、 byte-range:8193-102
40、 byte-range:10241-12288的文件块。
[108] 步骤 7.3、 AS2通过 MSRP向 UE4发送 byte-range:12289-14336、 byte-range: 14337-
16384、 byte-range: 16385-18432的文件块。
[109] 需要说明的是, 上述步骤 7.1、 7.2和 7.3可以同吋执行, 也可以调整执行的先后 顺序。
[110] 步骤 8.1、 UE2在接收到文件块后, 向 AS2回复 MSRP 200 OK应答。
[111] 步骤 8.2、 UE3在接收到文件块后, 向 AS2回复 MSRP 200 OK应答。
[112] 步骤 8.3、 UE4在接收到文件块后, 向 AS2回复 MSRP 200 OK应答。
[113] 步骤 9.1、 UE2和 UE3之间根据接收到的用户列表信息, 互相交换各自接收到的 文件块。
[114] 步骤 9.2、 UE2和 UE4之间根据接收到的用户列表信息, 互相交换各自接收到的 文件块。
[115] 步骤 9.3、 UE3和 UE4之间根据接收到的用户列表信息, 互相交换各自接收到的 文件块。
[116] 步骤 10.1、 UE2和 UE3交换文件块之后, 相互发送 MSRP 200 OK应答。
[117] 步骤 10.2、 UE2和 UE4交换文件块之后, 相互发送 MSRP 200 OK应答。
[118] 步骤 10.3、 UE3和 UE4交换文件块之后, 相互发送 MSRP 200 OK应答。
[119] 在上述图 2的描述中, 如果某个 UE (如 UE2) 关机导致其它 UE不能够从该 UE
(如 UE2) 处成功获得文件块, 则其它 UE (如 UE3、 UE4) 可以向 AS2再次发起 缺失文件块的请求 (如向 AS2请求 byte-range: 1-2048、 byte-range:2049-4096、 byte -range:4097-6145的文件块) 。 UE可以利用现有的 draft-garcia-mmusic-file-transfer -mech-01协议来实现向 AS2请求文件块的过程。 另外, 上述图 2中的接收方用户 设备数量是以 3为例进行说明的, 如果需要连接的 UE (即接收方用户设备数量) 超过了 AS2能够支持的 TCP最大连接数, 贝 l」AS2甚至可以与部分 UE建立连接, 然 后, 通知 UE之间建立连接, 使 UE之间进行文件块的传输即可。
[120] 需要特别说明的是, 上述针对图的描述是以 IMS域为例来说明本发明实施方式 的, 这并不表示本发明实施方式提供的消息业务中文件传输的实现方法只能应 用于 IMS域中。 当应用于其它网络域中吋, 其实现过程与上述实施例描述的过程
基本相同, 其区别可能包括: 扩展的消息名称的变化, 网络实体的名称的变化 , 以及消息流向的变化等。 但是, 其实质都是釆用了网络侧将文件分块传输、 用户设备间釆用 P2P技术获取相应文件块, 而且, 都可以充分利用现有的消息流 程。 在其它网络域的实现过程在此不再重复说明。
[121] 下面对本发明实施方式提供的消息业务中文件传输的实现装置进行说明。
[122] 本发明实施方式提供的消息业务中文件传输的实现装置如附图 3所示。 该装置 设置于网络侧设备中, 如可以设置于应用服务器中。
[123] 图 3中的装置包括: 划分模块 400和发送模块 410, 该装置还可以可选的包括: 第一接收模块 420和确定模块 430。
[124] 在网络侧设备需要将消息业务文件发送至多个接收方用户设备吋, 网络侧设备 中的划分模块 400将该消息业务的文件分成至少两个文件块。 这里的消息业务可 以是 IMS域中的消息业务, 也可以是其它网络域中的消息业务, 而且消息业务可 以是用户设备发起的, 也可以是网络侧主动发起的。 这里的文件可以为文本、 图片、 音频、 视频、 游戏等多种形式。 另外, 划分模块 400可以对消息业务的文 件是否进行分块处理进行判断, 划分模块 400可以根据文件分配算法来确定文件 划分的文件块数。 具体如上述方法实施方式中的描述。
[125] 划分模块 400可以包括确定数量子模块 401、 赋值子模块 403和划分子模块 402。
[126] 在需要将文件划分为多文件块吋, 确定数量子模块 401确定消息业务的本区域 内接收方用户设备数量 m, 并输出 m, 该 m大于 1。 当然, 确定数量子模块 401也 可以釆用其它方式来输出 m, 例如输出的 m为接收方数量加 1, 再例如, 确定数 量子模块 401输出预先设定的数值等。 具体如上述方法实施方式的描述。
[127] 划分子模块 402根据确定数量子模块 401输出的 m将消息业务的文件进行分块处 理。
[128] 确定数量子模块 401输出的数值可以先经过赋值子模块 403的检査, 例如, 赋值 子模块 403在确定出确定数量子模块 401输出的 m超过预定值吋, 将 m赋值为预定 值, 并将修改后的 m发送至划分子模块 402。 这里的预定值可以为网络侧设备的 传输控制协议最大连接数, 也可以是管理方根据网络的实际运行情况设定的数 值, 具体如上述方法实施方式的描述。
[129] 在划分模块 400对文件进行分块处理后, 发送模块 410将划分模块 400分成的至 少两个文件块分别向至少两个用户设备传输。
[130] 发送模块 410需要向用户设备下发从用户设备处获取文件块的通知信息, 该通 知信息用于通知用户设备从其它用户设备处获取其未接收到的文件块。 发送模 块 410向用户设备下发文件块和通知信息的方式有多种, 例如, 文件块和通知信 息可以通过一条消息或一个数据报文发送至用户设备, 文件块和通知信息可以 通过不同的消息或数据报文发送至用户设备, 如先向用户设备发送通知信息, 再发送文件块等。 而且, 发送模块 410可以向某个用户设备仅下发通知信息, 也 可以向用户设备既下发文件块又下发通知信息, 而且, 向某个用户设备下发的 文件块可以为一个文件块、 也可以为多个文件块。 发送模块 410可以根据文件分 配算法确定需要向哪些用户设备发送怎样的文件块。 具体如上述方法实施方式 中的描述。
[131] 第一接收模块 420接收用户设备发送来的请求文件块的信息, 确定模块 430根据 第一接收模块 420接收到的信息确定用户设备请求的文件块, 并通知发送模块 41 0发送该用户设备请求的文件块。 确定模块 430可以通知发送模块 410向某个用户 设备发送文件块, 也可以通知发送模块 410向多个用户设备发送文件块如向各个 用户设备均发送请求的文件块等, 具体如上述方法实施方式中的描述。
[132] 由于该装置可以根据用户设备的请求再次发送某个或某些文件块, 因此, 该装 置中的存储模块需要存储发送的各文件块, 该装置中的存储模块可以不存储文 件块而存储文件, 此吋, 在第一接收模块 420接收到请求后, 确定模块 430通知 划分模块 400再次进行分块处理, 然后, 确定模块 430再通知发送模块 410向某个 或某些用户设备发送请求的文件块。 该装置可以包括老化处理模块, 以对存储 模块中存储的文件块或文件进行老化处理, 老化处理模块可以釆用现有的多种 老化处理方法进行老化处理, 在此不再详细说明。
[133] 本发明实施方式提供的用户设备如附图 4所示。
[134] 图 4中的用户设备包括: 第二接收模块 500、 获取模块 510和组合模块 520。 用户 设备还可以可选的包括请求模块 530。
[135] 第二接收模块 500接收网络侧传输来信息, 该信息可以是通知信息, 也可以是
文件块和通知信息, 当然, 也可以是所有的文件块。
[136] 获取模块 510根据第二接收模块 500接收到的通知信息与其它用户设备建立连接 , 并从其它用户设备处获取第二接收模块 500未从网络侧接收到的文件块。 获取 模块 510可以根据通知信息与另外一个用户设备建立连接, 以获取网络侧未向其 所在用户设备发送的所有文件块; 获取模块 510也可以根据通知信息与另外多个 用户设备建立连接, 以获取网络侧未向其所在用户设备发送的所有文件块。 这 取决于网络侧向用户设备发送文件块的算法, 具体如上述方法实施方式中的描 述。
[137] 组合模块 520将其所在用户设备获得的文件块整理组合为消息业务的文件。 组 合模块 520所在用户设备获得的文件块可以仅为第二接收模块 500接收到的网络 侧发送来的所有文件块, 也可以为第二接收模块 500接收到的网络侧发送来的文 件块和获取模块 510从其它用户设备处获取的文件块, 还可以仅为获取模块 510 从其它用户设备处获取的所有文件块。
[138] 请求模块 530在确定出获取模块 510不能够从其它用户设备处成功获取文件块吋 , 向网络侧请求所述不能够成功获取的文件块。 获取模块 510不能够成功的从其 它用户设备处获取网络侧未向其发送的文件块的原因有多种, 具体如上述方法 实施方式中的描述。
[139] 通过以上的实施方式的描述, 本领域的技术人员可以清楚地了解到本发明可借 助软件加必需的硬件平台的方式来实现, 当然也可以全部通过硬件来实施, 但 很多情况下前者是更佳的实施方式。 基于这样的理解, 本发明的技术方案对背 景技术做出贡献的全部或者部分可以以软件产品的形式体现出来, 该计算机软 件产品可以存储在存储介质中, 如 ROM/RAM、 磁碟、 光盘等, 包括若干指令用 以使得计算机设备 (可以是个人计算机, 服务器, 或者网络设备等) 执行本发 明各个实施例或者实施例的某些部分所述的方法。
[140] 虽然通过实施例描绘了本发明, 本领域普通技术人员知道, 本发明有许多变形 和变化而不脱离本发明的精神, 本发明的申请文件的权利要求包括这些变形和 变化。
Claims
[1] 一种消息业务中文件传输的实现方法, 其特征在于, 包括:
网络侧将需要发送至用户设备的消息业务的文件划分成至少两个文件块; 网络侧将所述划分后的文件块分别向至少两个用户设备传输, 并向用户设 备下发获取文件块的通知信息, 以使所述用户设备从其它用户设备处获取 其未接收到的文件块。
[2] 如权利要求 1所述的方法, 其特征在于, 所述网络侧将需要发送至用户设备 的消息业务的文件划分成至少两个文件块包括:
网络侧确定所述消息业务的接收方用户设备数量 m, 并将所述文件划分为 m 个文件块, 所述 m为大于 1的自然数。
[3] 如权利要求 2所述的方法, 其特征在于, 所述将所述文件划分为 m个文件块 之前还包括:
网络侧在确定出所述 m超过预定值吋, 将 m赋值为预定值。
[4] 如权利要求 3所述的方法, 其特征在于, 所述预定值包括: 网络侧的传输控 制协议 TCP最大连接数。
[5] 如权利要求 2所述的方法, 其特征在于, 所述网络侧将所述至少两个文件块 分别向至少两个用户设备传输包括:
网络侧将所述 m个文件块分别向 m个用户设备传输, 使一个用户设备接收到 一个文件块。
[6] 如权利要求 1所述的方法, 其特征在于, 所述向用户设备下发获取文件块的 通知信息包括:
网络侧将用户设备的地址信息和用户设备接收到的文件块信息发送至各用 户设备。
[7] 如权利要求 1所述的方法, 其特征在于, 所述向用户设备下发获取文件块的 通知信息包括:
网络侧将所述通知信息携带在会话描述协议 SDP的消息中, 并向用户设备 发送。
[8] 如权利要求 1至 7中任一权利要求所述的方法, 其特征在于, 所述方法还包
括:
网络侧接收用户设备发送来的请求文件块的信息;
网络侧确定用户设备请求的文件块, 并发送所述用户设备请求的文件块。
[9] 一种消息业务实现方法, 其特征在于, 包括:
用户设备接收网络侧传输来的通知信息;
所述用户设备根据所述通知信息与其它用户设备建立连接, 并从其它用户 设备处获取其未接收到的文件块;
所述用户设备将获得的文件块组合为消息业务的文件。
[10] 如权利要求 9所述的方法, 其特征在于, 所述方法还包括:
用户设备在确定出不能够从其它用户设备处成功获取文件块吋, 向网络侧 请求所述不能够成功获取的文件块。
[11] 一种消息业务中文件传输的实现装置, 其特征在于, 包括:
划分模块 (400) , 用于将需要发送至用户设备的消息业务的文件划分成至 少两个文件块;
发送模块 (410) , 用于将所述划分模块 (400) 划分成的文件块分别向至 少两个用户设备传输, 并向用户设备下发获取文件块的通知信息, 以使所 述用户设备从其它用户设备处获取其未接收到的文件块。
[12] 如权利要求 11所述的装置, 其特征在于, 所述划分模块 (400) 包括: 确定数量子模块 (401) , 用于确定所述消息业务的接收方用户设备数量 m , 所述 m为大于 1的自然数;
划分子模块 (402) , 用于根据所述 m将所述文件划分为 m个文件块。
[13] 如权利要求 12所述的装置, 其特征在于, 所述划分模块 (400) 还包括: 赋值子模块 (403) , 用于在确定出所述确定数量子模块 (401) 输出的 m 超过预定值吋, 将 m赋值为预定值, 并发送至划分子模块 (402) 。
[14] 如权利要求 11或 12或 13所述的装置, 其特征在于, 所述装置还包括:
第一接收模块 (420) , 用于接收用户设备发送来的请求文件块的信息; 确定模块 (430) , 用于根据第一接收模块 (420) 接收到的信息确定用户 设备请求的文件块, 并通知发送模块 (410) 发送所述用户设备请求的文件
块。
[15] 一种用户设备, 其特征在于, 包括:
第二接收模块 (500) , 用于接收网络侧传输来的通知信息; 获取模块 (510) , 用于根据所述第二接收模块 (500) 接收到的通知信息 与其它用户设备建立连接, 并从其它用户设备处获取其所在用户设备未从 网络侧接收到的文件块;
组合模块 (520) , 用于将其所在用户设备获得的文件块组合为消息业务的 文件。
[16] 如权利要求 15所述的用户设备, 其特征在于, 所述用户设备还包括:
请求模块 (530) , 用于在确定出获取模块 (510) 不能够从其它用户设备 处成功获取文件块吋, 向网络侧请求所述不能够成功获取的文件块。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP09761255.0A EP2282460B1 (en) | 2008-06-12 | 2009-04-10 | Document transmission realizing method, apparatus and user device for message business |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200810110650.6 | 2008-06-12 | ||
CN2008101106506A CN101291300B (zh) | 2008-06-12 | 2008-06-12 | 消息业务中文件传输的实现方法、装置和用户设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009149630A1 true WO2009149630A1 (zh) | 2009-12-17 |
Family
ID=40035383
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/071237 WO2009149630A1 (zh) | 2008-06-12 | 2009-04-10 | 消息业务中文件传输的实现方法、装置和用户设备 |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP2282460B1 (zh) |
CN (1) | CN101291300B (zh) |
WO (1) | WO2009149630A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107707521A (zh) * | 2017-08-08 | 2018-02-16 | 山东中创软件商用中间件股份有限公司 | 一种文件传输方法及系统 |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101291300B (zh) * | 2008-06-12 | 2011-04-20 | 华为技术有限公司 | 消息业务中文件传输的实现方法、装置和用户设备 |
CN101771960A (zh) * | 2009-01-04 | 2010-07-07 | 中国移动通信集团公司 | 移动网络的业务调用方法、业务网关、业务平台和系统 |
CN103457643A (zh) * | 2012-05-29 | 2013-12-18 | 宏碁股份有限公司 | 近场通信设备的文件分享系统及其方法 |
CN102904934A (zh) * | 2012-09-25 | 2013-01-30 | 东莞宇龙通信科技有限公司 | 终端数据传输的方法及其系统 |
CN104978661A (zh) * | 2014-04-01 | 2015-10-14 | 深圳市赛格导航科技股份有限公司 | 一种基于车载定位的电子商务服务方法及其系统 |
CN105553832A (zh) * | 2015-12-25 | 2016-05-04 | 北京奇虎科技有限公司 | 消息发送、接收方法及装置 |
CN106341240A (zh) * | 2016-04-11 | 2017-01-18 | 上海建朗信息科技有限公司 | 会议文件定向群发系统 |
CN108270556B (zh) * | 2016-12-30 | 2021-06-22 | 北京国双科技有限公司 | 终端的登录方法和装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1897588A (zh) * | 2006-06-21 | 2007-01-17 | 北京北大方正电子有限公司 | 一种混合模式的网络文件传输方法及系统 |
CN101043345A (zh) * | 2006-03-20 | 2007-09-26 | 腾讯科技(深圳)有限公司 | 一种基于点对点技术的图片共享系统和方法 |
WO2008030494A2 (en) * | 2006-09-05 | 2008-03-13 | Donnelli Robert M | Managing client-to-server or peer-to-peer relationships in a private or virtual network |
CN101291300A (zh) * | 2008-06-12 | 2008-10-22 | 华为技术有限公司 | 消息业务中文件传输的实现方法、装置和用户设备 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU2002239617A1 (en) * | 2000-10-30 | 2002-05-21 | The Trend Fund Corp. | Method and system for providing messaging to multiple clients |
TWI265697B (en) * | 2002-06-06 | 2006-11-01 | Ibm | Digital contents distribution system, digital contents distribution method, computer readable recording medium storing the program therein, and server and client therefor |
US7593333B2 (en) * | 2004-07-07 | 2009-09-22 | Microsoft Corporation | Efficient one-to-many content distribution in a peer-to-peer computer network |
JP4704252B2 (ja) * | 2006-03-14 | 2011-06-15 | 富士通株式会社 | ネットワークシステムのブロードキャスト処理方法及びネットワークシステム |
US20080133767A1 (en) * | 2006-11-22 | 2008-06-05 | Metis Enterprise Technologies Llc | Real-time multicast peer-to-peer video streaming platform |
-
2008
- 2008-06-12 CN CN2008101106506A patent/CN101291300B/zh active Active
-
2009
- 2009-04-10 WO PCT/CN2009/071237 patent/WO2009149630A1/zh active Application Filing
- 2009-04-10 EP EP09761255.0A patent/EP2282460B1/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101043345A (zh) * | 2006-03-20 | 2007-09-26 | 腾讯科技(深圳)有限公司 | 一种基于点对点技术的图片共享系统和方法 |
CN1897588A (zh) * | 2006-06-21 | 2007-01-17 | 北京北大方正电子有限公司 | 一种混合模式的网络文件传输方法及系统 |
WO2008030494A2 (en) * | 2006-09-05 | 2008-03-13 | Donnelli Robert M | Managing client-to-server or peer-to-peer relationships in a private or virtual network |
CN101291300A (zh) * | 2008-06-12 | 2008-10-22 | 华为技术有限公司 | 消息业务中文件传输的实现方法、装置和用户设备 |
Non-Patent Citations (2)
Title |
---|
CHEN RONG: "TRAFFIC CONTROL SOLUTION FOR SCHOOL NETWORK", JOURNAL OF SICHUAN UNIVERSITY OF SCIENCE & ENGINEERING(NATURAL SCIENCE EDITION), vol. 20, no. 6, 31 December 2007 (2007-12-31), pages 60 - 62, XP008147206 * |
See also references of EP2282460A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107707521A (zh) * | 2017-08-08 | 2018-02-16 | 山东中创软件商用中间件股份有限公司 | 一种文件传输方法及系统 |
Also Published As
Publication number | Publication date |
---|---|
CN101291300A (zh) | 2008-10-22 |
EP2282460A1 (en) | 2011-02-09 |
EP2282460B1 (en) | 2014-12-03 |
CN101291300B (zh) | 2011-04-20 |
EP2282460A4 (en) | 2011-06-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2009149630A1 (zh) | 消息业务中文件传输的实现方法、装置和用户设备 | |
JP4901878B2 (ja) | ユニキャスト・セッションとマルチキャスト・セッションとの間で変換を行うための方法 | |
JP2015029327A (ja) | コンテンツダウンロード及びコンテンツアップロード用ポリシー | |
WO2007041937A1 (fr) | Methode d'envoi et de reception de message hors ligne, appareil client, serveur et systeme | |
WO2016176094A1 (en) | Instant message and electronic mail portability | |
US8516081B2 (en) | Delivery server, content delivery method in delivery server and multicast server, content delivery method in multicast server | |
WO2007068209A1 (fr) | Procede, systeme et dispositif d'envoi de messages instantanes ims | |
WO2009018755A1 (fr) | Procédé de session multi-terminal, système de communication et dispositifs associés | |
US10498791B2 (en) | Negotiation of message chunk size for message session relay protocol session | |
CN106559396B (zh) | 基于Web实时通信的媒体多播方法和系统 | |
CN110875914B (zh) | 一种基于共享会话链路传输消息的方法及装置 | |
WO2015127813A1 (zh) | 一种录音控制方法及sip服务器和录音服务器 | |
US20130097265A1 (en) | Method for transferring and storing cpm service message and service thereof | |
US20150043421A1 (en) | Wireless relay apparatus, communication system, and communication method | |
US7899058B2 (en) | Using a hash value as a pointer to an application class in a communications device | |
WO2012013094A1 (zh) | 基于对话关联标识的会话建立方法及系统 | |
WO2018133542A1 (zh) | 文件传输方法及系统、装置、电子设备、计算机存储介质 | |
US8493936B2 (en) | Method and device for handover between UEs in process of sending message | |
CN108833063A (zh) | 一种报文重传方法及装置 | |
JP2011515980A (ja) | 通信システムにおけるピアツーピアマルチメディア接続の状態を問い合わせるシステムおよび方法 | |
CN109120578A (zh) | 一种实现链路连接处理的方法及装置 | |
WO2009030171A1 (fr) | Procédé d'implémentation de service média, système de communication et dispositifs associés | |
WO2009043280A1 (fr) | Procédé, équipement et système pour identifier un type de service et établir un service selon l'identifiant | |
CN104811579A (zh) | 一种传真业务处理系统、方法及设备 | |
WO2008151572A1 (fr) | Procédé, passerelle d'interconnexion et client de transfert de fichier |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09761255 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009761255 Country of ref document: EP |