WO2015000142A1 - Method, system and equipment for transmitting service data - Google Patents

Abstract

The embodiment of the present application relates to the technical field of wireless communications, and in particular to a method, system and equipment for transmitting service data, aiming at solving the problem in the prior art that the stability of DASH (Dynamic Adaptive Streaming over HTTP) services are greatly affected by the occurrence of vertical handoff. The method in the present application comprises: a DASH proxy server determining a code rate corresponding to user equipment performing vertical handoff during the transmission of DASH service data, and transmitting the DASH service data to the user equipment according to the determined code rate. In the embodiment of the present application, the DASH service data is transmitted, through the code rate determined by the DASH proxy server, to the user equipment performing vertical handoff during the transmission of the DASH service data, thus the impact on the stability of the DASH services after vertical handoff is reduced.

Description

 Method, system and device for transmitting service data

 The present invention relates to the field of wireless communication technologies, and in particular, to a method, system and device for transmitting service data. Background technique

 3GP-DASH, 3 GPP (3rd Generation Partnership Project) DASH (Dynamic Adaptive Streaming over HTTP; HTTP, Hyper Text Transport Protocol, Hypertext Transfer Protocol) A media file consists of two parts: a Media Presentation Description (MPD) and a media stream file.

 The DASH server first generates multiple representations of multiple bitrates for the same media stream file. Each Representation includes multiple segments. In general, each segment lasts for a few seconds or ten seconds. The UE (User Equipment) can select Segment fragments of different Representations according to the transmission status of the current network. The "representation" and "sharding" of the media stream are described in the MPD file. After obtaining the MPD file, the UE can select a Representation of the media stream according to the current network condition, and obtain a media stream corresponding to a segment by request. The process of acquiring the media stream file based on the DASH technology is shown in FIG. 1A. As can be seen from FIG. 1A, the DASH server selects a 250 kbps slice in the slice 1 according to the current network transmission condition, and selects a 500 kbps score in the slice 2. Slice, select 1 Mbps slice in slices 3 and 4.

 The 3GPP organization has proposed a normative integration standard for Non-3GPP access methods and 3GPP access methods. Under this framework, mobile terminals can switch between different networks according to the standard process. Since the bandwidth of the wireless network will change greatly after the vertical switchover, this will have a great impact on the application service of the upper layer.

Currently due to the characteristics of its adaptive network bandwidth, and different commercial versions of the algorithm are different The characteristics of the DASH service will be greatly affected after the completion of the handover due to the change of the wireless bandwidth after the vertical handover occurs. For example, for video services, after the handover is completed, since the rate requested by the UE does not match the wireless bandwidth after handover, there will be a video jitter period of more than half a minute, and the Buffer will experience many underflows, some of which have a long underflow time. , video playback is often stuck.

 In summary, the current vertical handover has a relatively large impact on the stability of the DASH service. Summary of the invention

 The invention provides a method, a system and a device for transmitting service data, which are used to solve the problem that the stability of the DASH service is greatly affected after the vertical handover occurs in the prior art.

 In a first aspect, a method for transmitting service data is provided, including:

 The DASH proxy server determines a code rate corresponding to the user equipment that performs vertical switching when performing DASH service data transmission;

 The DASH proxy server sends DASH service data to the user equipment according to the determined code rate.

 With reference to the first aspect, in a first possible implementation, the DASH proxy server determines, before the code rate corresponding to the user equipment that performs the vertical handover when performing DASH service data transmission, the method further includes:

 The DASH proxy server receives a handover complete indication message of the user equipment.

 With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, the handover completion indication message is carried by a Hypertext Transfer Protocol HTTP message.

 With reference to the first aspect or the first or second possible implementation manner of the first aspect, in a third possible implementation manner, the DASH proxy server determines a user equipment that performs vertical handover when performing DASH service data transmission. The corresponding code rate, including:

The DASH proxy server determines a code rate of the DASH service data that needs to be sent to the user equipment according to the bandwidth of the user equipment in the switched network. With reference to the first aspect, or the first possible implementation of the first aspect, to any one of the third possible implementation manners, in a fourth possible implementation manner, the DASH proxy server is determined according to the determining Rate, sending DASH service data to the user equipment, including:

 And the DASH proxy server transmits the DASH service data and the determined code rate according to the received request of the user equipment, and sends the DASH service data to the user equipment.

 With reference to the fourth possible implementation manner of the foregoing aspect, in a fifth possible implementation manner, the information that is requested to transmit the DASH service data is carried by using an HTTP message.

 With reference to the first aspect, or the first possible implementation of the first aspect, to any one of the third possible implementation manners, in a sixth possible implementation manner, the DASH proxy server is determined according to the determining Rate, sending DASH service data to the user equipment, including:

 After determining that the code rate requested by the user equipment is different from the code rate determined by the DASH proxy server, the DASH proxy server sends the DASH service data to the user equipment according to the determined code rate.

 In conjunction with the sixth possible implementation of the first aspect, in a seventh possible implementation, the method further includes:

 After determining that the code rate requested by the user equipment is the same as the code rate determined by the DASH proxy server, the DASH proxy server sends DASH service data to the user equipment according to a code rate requested by the user equipment.

 With reference to the first aspect, or the first possible implementation of the first aspect, to any one of the seventh possible implementation manners, in an eighth possible implementation manner, the method further includes:

 Sending, by the DASH proxy server, the received message of the user equipment requesting the MPD file to the DASH server, and sending the response message of the requesting MPD file returned by the DASH server to the DASH server before the user equipment performs the vertical handover. User equipment

 The DASH proxy server sends DASH service data to the UE according to a code rate requested by the user equipment.

In a second aspect, a method for transmitting service data is provided, including: The user equipment stops receiving DASH service data of the DASH proxy server when performing vertical handover;

 After the vertical handover is completed, the user equipment continues to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server.

 With reference to the second aspect, in a first possible implementation manner, after the vertical handover is completed, the user equipment continues to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server, and further Includes:

 The user equipment sends a handover complete indication message to the DASH proxy server.

 With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner, the handover completion indication message is carried by using an HTTP message.

 With the second aspect or the first or second possible implementation manner of the second aspect, in a third possible implementation manner, after the vertical handover is completed, the user equipment continues to receive the DASH proxy server according to the Before the DASH service data sent by the DASH proxy server determines the code rate, the method further includes:

 The user equipment sends information requesting to transmit DASH service data to the DASH proxy server.

 With reference to the third possible implementation manner of the second aspect, in a fourth possible implementation manner, the user equipment is configured to determine information for requesting to transmit DASH service data according to the following manner:

 The user equipment determines a processing manner of the completed transmission part in the fragment that is not completed when the vertical handover is performed, and determines information for requesting transmission of the DASH service data according to the determined processing manner.

 With reference to the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner, the user equipment determines a manner of processing the DASH service data that is not completed, the method includes: the user equipment determining, Whether the amount of data in the part of the fragment that has been transferred is greater than the threshold;

If so, the portion of the fragment that has completed the transmission is retained; otherwise, the portion of the fragment that has completed the transmission is deleted. In a third aspect, a method for transmitting service data is provided, including:

 The DASH proxy server determines a code rate corresponding to the user equipment that performs vertical switching when performing DASH service data transmission;

 The DASH proxy server updates the code rate in the MPD file according to the determined code rate, and returns the updated MPD file to the user equipment;

 The DASH proxy server sends DASH service data to the user equipment according to a code rate selected by the user equipment from the MPD file.

 With reference to the third aspect, in a first possible implementation, before the DASH proxy server determines the code rate of the DASH service data that needs to be sent to the user equipment, the method further includes:

 The DASH proxy server receives a handover complete indication message of the user equipment.

 With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner, the handover completion indication message is carried by a Hypertext Transfer Protocol HTTP message.

 With reference to the third aspect, or the first or the second possible implementation manner of the third aspect, in a third possible implementation manner, the DASH proxy server determines a code rate of DASH service data that needs to be sent to the user equipment, Includes:

 The DASH proxy server determines the code rate of the DASH service data that needs to be sent to the user equipment according to the bandwidth of the user equipment in the switched network.

 With reference to the third aspect, or the first possible implementation manner of the third aspect, to any one of the third possible implementation manners, in a fourth possible implementation manner, the DASH proxy server is configured according to the determined code rate , update the bit rate in the MPD file, including:

 The DASH proxy server updates the code rate in the MPD file, wherein the code rate in the updated MPD file is not greater than the determined code rate.

 With reference to the third aspect, or the first possible implementation manner of the third aspect, to any one of the fourth possible implementation manners, in a fifth possible implementation manner, the DASH proxy server determines that the user needs to send to the user Before the bit rate of the DASH service data of the device, it also includes:

The DASH proxy server sends the received message that the user equipment requests the MPD file to the DASH server, and returns a response message of the requested MPD file returned by the DASH server. Sent to the user equipment;

 The DASH proxy server sends DASH service data to the UE according to a code rate requested by the user equipment.

 In a fourth aspect, a method for transmitting service data is provided, including:

 The user equipment stops receiving DASH service data of the DASH proxy server when performing vertical handover;

 After the vertical handover is completed, the user equipment selects a code rate from the MPD file sent by the DASH proxy server and sends the code to the DASH proxy server, where the MPD file is the DASH proxy server according to the DASH proxy server. The determined code rate is obtained after the update; the user equipment receives the DASH service data sent by the DASH proxy server according to the received code rate.

 With reference to the fourth aspect, in a first possible implementation manner, after the vertical handover is completed, the user equipment selects a code rate from the MPD file sent by the DASH proxy server, and sends the code rate to the DASH proxy service. Includes:

 The user equipment sends a handover complete indication message to the DASH proxy server.

 With reference to the first possible implementation manner of the fourth aspect, in a second possible implementation manner, the handover completion indication message is carried by using an HTTP message.

 With reference to the fourth aspect, or the first or the second possible implementation manner of the fourth aspect, in a third possible implementation manner, after the vertical handover is completed, the user equipment continues to receive the DASH proxy server according to the receiving Before the DASH service data sent by the code rate, it also includes:

 The user equipment sends information requesting to transmit DASH service data to the DASH proxy server.

 With reference to the third possible implementation manner of the fourth aspect, in a fourth possible implementation manner, the user equipment determines information for requesting to transmit DASH service data according to the following manner:

The user equipment determines a processing manner of the completed transmission part in the fragment that has not completed the transmission when performing the vertical handover, and determines information requesting to transmit the DASH service data according to the determined processing manner. With reference to the fourth possible implementation manner of the fourth aspect, in a fifth possible implementation manner, the user equipment determines, by the user equipment, the method for processing the DASH service data that is not completed. Whether the amount of data in the part of the fragment that has been transferred is greater than the threshold;

 If so, the portion of the slice that has completed the transfer is retained; otherwise, the portion of the slice that has completed the transfer is deleted.

 The fifth aspect provides a DASH proxy server for transmitting service data, including: a determining module, configured to determine a code rate corresponding to a user equipment that performs vertical handover when performing DASH service data transmission;

 And a sending module, configured to send DASH service data to the user equipment according to the determined code rate.

 With reference to the fifth aspect, in a first possible implementation manner, the determining module is further configured to: after receiving the handover complete indication message of the user equipment, determine, to perform user equipment that performs vertical handover when performing DASH service data transmission Corresponding code rate.

 With reference to the fifth aspect, or the first possible implementation manner of the fifth aspect, in a second possible implementation manner, the handover completion indication message is carried by a Hypertext Transfer Protocol HTTP message.

 With reference to the fifth aspect or the first or the second possible implementation manner of the fifth aspect, in a third possible implementation manner, the determining module is specifically configured to:

 Determining, according to the bandwidth of the user equipment in the switched network, a code rate of DASH service data that needs to be sent to the user equipment.

 With reference to the fifth aspect, or the first possible implementation manner of the fifth aspect, to any one of the third possible implementation manners, in a fourth possible implementation manner, the sending module is specifically configured to: The request of the user equipment to transmit the information of the DASH service data and the determined code rate, and send the DASH service data to the user equipment.

 With reference to the fourth possible implementation manner of the fifth aspect, in a fifth possible implementation manner, the information that is requested to transmit the DASH service data is carried by using an HTTP message.

Combining the fifth aspect or the first possible implementation of the fifth aspect to the third possible implementation In a sixth possible implementation, in a sixth possible implementation, the sending module is specifically configured to: after determining that a code rate requested by the user equipment is different from a code rate determined by the DASH proxy server, Sending the DASH service data to the user equipment by the determined code rate.

 With reference to the sixth possible implementation of the fifth aspect, in a seventh possible implementation, the determining module is further configured to:

 After determining that the code rate requested by the user equipment is the same as the code rate determined by the DASH proxy server, the DASH service data is sent to the user equipment according to the code rate requested by the user equipment.

 With reference to the fifth aspect, or the first possible implementation manner of the fifth aspect, to any one of the seventh possible implementation manners, in the eighth possible implementation manner, the determining module is further configured to: Before the user equipment performs the vertical switching, the received message of the user equipment requesting the MPD file is sent to the DASH server, and the response message of the requesting MPD file returned by the DASH server is sent to the user equipment; The code rate requested by the user equipment, and the DASH service data is sent to the UE.

 A sixth aspect provides a user equipment for transmitting service data, including:

 a receiving module, configured to receive DASH service data of the DASH proxy server;

 a processing module, configured to: when the vertical handover is performed, control the receiving module to stop receiving DASH service data of the DASH proxy server, and after the vertical handover is completed, control the receiving module to continue to receive the DASH proxy server according to the DASH proxy The DASH service data sent by the server at the determined bit rate.

 With reference to the sixth aspect, in a first possible implementation, the processing module is further configured to: after the vertical handover is completed, control the receiving module to continue to receive the code determined by the DASH proxy server according to the DASH proxy server Before the DASH service data is sent, the handover completion indication message is sent to the DASH proxy server.

 With reference to the first possible implementation manner of the sixth aspect, in a second possible implementation manner, the handover completion indication message is carried by using an HTTP message.

With reference to the sixth aspect, or the first or the second possible implementation manner of the sixth aspect, in a third possible implementation, the processing module is further configured to: After the vertical handover is completed, the receiving module continues to receive the DASH proxy server to send information requesting to transmit DASH service data to the DASH proxy server before receiving the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server.

 In conjunction with the third possible implementation of the sixth aspect, in a fourth possible implementation, the processing module is further configured to:

 The information requesting transmission of the DASH service data is determined according to the following manner: Determining the processing manner of the completed transmission portion in the fragment that has not completed the transmission when performing the vertical handover, and determining the information requesting to transmit the DASH service data according to the determined processing manner.

 With reference to the fourth possible implementation manner of the sixth aspect, in a fifth possible implementation, the processing module is specifically configured to:

 Determining whether the amount of data of the portion of the fragment that has completed the transmission is greater than a threshold; if so, retaining the portion of the fragment that has completed the transmission; otherwise, deleting the portion of the fragment that has completed the transmission.

 The seventh aspect provides a DASH proxy server for transmitting service data, including: a determining module, configured to determine a code rate corresponding to a user equipment that performs vertical handover when performing DASH service data transmission;

 a sending module, configured to update a code rate in the MPD file according to the determined code rate, and return the updated MPD file to the user equipment; according to a code rate selected by the user equipment from the MPD file, The user equipment sends DASH service data.

 With reference to the seventh aspect, in a first possible implementation, the determining module is further configured to: after receiving the handover complete indication message of the user equipment, determine a code rate of DASH service data that needs to be sent to the user equipment.

 With reference to the first possible implementation manner of the seventh aspect, in a second possible implementation manner, the handover completion indication message is carried by a Hypertext Transfer Protocol HTTP message.

 In combination with the seventh aspect or the first or second possible implementation manner of the seventh aspect, the determining module is specifically configured to:

The code rate of the DASH service data that needs to be sent to the user equipment is determined according to the bandwidth of the user equipment in the switched network. With reference to the seventh aspect, or the first possible implementation manner of the seventh aspect, to any one of the third possible implementation manners, in the fourth possible implementation manner, the sending module is specifically configured to: update the MPD The code rate in the file, wherein the code rate in the updated MPD file is not greater than the determined code rate.

 With reference to the seventh aspect, or the first possible implementation manner of the seventh aspect, to any one of the fourth possible implementation manners, in a fifth possible implementation manner, the sending module is further configured to: determine a requirement Before receiving the code rate of the DASH service data of the user equipment, the received message of the user equipment requesting the MPD file is sent to the DASH server, and the response message of the requesting MPD file returned by the DASH server is sent to the user. The device sends DASH service data to the UE according to the code rate requested by the user equipment.

 The eighth aspect provides a user equipment for transmitting service data, including:

 a receiving module, configured to receive DASH service data of the DASH proxy server;

 a processing module, configured to: when the vertical switching is performed, control the receiving module to stop receiving DASH service data of the DASH proxy server, and after the vertical switching is completed, select a code rate from the MPD file sent by the DASH proxy server to send to the a DASH proxy server, wherein the MPD file is obtained after the DASH proxy server is updated according to a code rate determined by the DASH proxy server; and controlling the receiving module to receive the DASH proxy server to send according to a received code rate. DASH business data.

 With reference to the eighth aspect, in a first possible implementation, the processing module is further configured to: after the vertical handover is completed, select a code rate from the MPD file sent by the DASH proxy server, and send the code rate to the DASH proxy. Before the service, a handover complete indication message is sent to the DASH proxy server.

 With reference to the first possible implementation manner of the eighth aspect, in a second possible implementation manner, the handover completion indication message is carried by using an HTTP message.

 With reference to the eighth aspect, or the first or the second possible implementation manner of the eighth aspect, in a third possible implementation, the processing module is further configured to:

After the vertical handover is completed, continue to receive the DASH proxy server according to the received code rate Before transmitting the DASH service data, sending information requesting transmission of DASH service data to the DASH proxy server.

 In conjunction with the third possible implementation of the eighth aspect, in a fourth possible implementation, the processing module is further configured to:

 The information requesting transmission of the DASH service data is determined according to the following manner: Determining the processing manner of the completed transmission portion in the fragment that has not completed the transmission when performing the vertical handover, and determining the information requesting to transmit the DASH service data according to the determined processing manner.

 With reference to the fourth possible implementation of the eighth aspect, in a fifth possible implementation, the processing module is specifically configured to:

 Determining whether the amount of data of the portion of the fragment that has completed the transmission is greater than a threshold; if so, retaining the portion of the fragment that has completed the transmission; otherwise, deleting the portion of the fragment that has completed the transmission.

 In conjunction with the ninth aspect, a system for transmitting service data includes:

 a DASH proxy server, configured to determine a code rate corresponding to the user equipment that performs vertical switching when performing DASH service data transmission, and send DASH service data to the user equipment according to the determined code rate;

 The user equipment is configured to stop receiving the DASH service data of the DASH proxy server during the vertical handover, and after receiving the vertical handover, continue to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server.

 In conjunction with the tenth aspect, a system for transmitting service data includes:

 a DASH proxy server, configured to determine a code rate corresponding to the user equipment that performs vertical switching when performing DASH service data transmission, update a code rate in the MPD file according to the determined code rate, and return the updated MPD file to the user equipment. Transmitting DASH service data to the user equipment according to a code rate selected by the user equipment from the MPD file;

The user equipment is configured to stop receiving DASH service data of the DASH proxy server when performing vertical handover, and select a code rate from the MPD file sent by the DASH proxy server to send to the DASH proxy server after the vertical handover is completed, The MPD file is obtained after the DASH proxy server is updated according to the code rate determined by the DASH proxy server, and is connected. Receiving DASH service data sent by the DASH proxy server according to the received code rate. In an eleventh aspect, a DASH proxy server for transmitting service data is provided, including: a processor, configured to determine a code rate corresponding to a user equipment that performs vertical handover when performing DASH service data transmission;

 And a transmitter, configured to send DASH service data to the user equipment according to the determined code rate.

 With reference to the eleventh aspect, in a first possible implementation manner, the processor is further configured to: after receiving the handover complete indication message of the user equipment, determine, to perform a vertical handover when performing DASH service data transmission The code rate corresponding to the device.

 With reference to the eleventh aspect or the first possible implementation manner of the eleventh aspect, in a second possible implementation manner, the handover completion indication message is carried by a Hypertext Transfer Protocol HTTP message.

 With reference to the eleventh aspect or the first or second possible implementation manner of the eleventh aspect, in a third possible implementation manner, the processor is specifically configured to:

 Determining, according to the bandwidth of the user equipment in the switched network, a code rate of DASH service data that needs to be sent to the user equipment.

 With reference to the eleventh aspect or the first possible implementation manner of the eleventh aspect to any one of the third possible implementation manners, in a fourth possible implementation manner, the transmitter is specifically configured to:

 Transmitting the DASH service data information and the determined code rate according to the received request of the user equipment, and transmitting the DASH service data to the user equipment.

 With reference to the fourth possible implementation manner of the eleventh aspect, in a fifth possible implementation manner, the information that is requested to transmit the DASH service data is carried by using an HTTP message.

 With reference to the eleventh aspect, or the first possible implementation manner of the eleventh aspect, to any one of the third possible implementation manners, in a sixth possible implementation manner, the transmitter is specifically configured to:

Determining that the code rate requested by the user equipment is not determined by the code rate determined by the DASH proxy server Then, the DASH service data is sent to the user equipment according to the determined code rate. In conjunction with the sixth possible implementation of the eleventh aspect, in a seventh possible implementation, the processor is further configured to:

 After determining that the code rate requested by the user equipment is the same as the code rate determined by the DASH proxy server, the DASH service data is sent to the user equipment according to the code rate requested by the user equipment.

 With reference to the eleventh aspect, or the first possible implementation manner of the eleventh aspect, to any one of the seventh possible implementation manners, in an eighth possible implementation manner, the processor is further configured to: Sending, by the user equipment, a message requesting the MPD file to the DASH server, and transmitting a response message of the requested MPD file returned by the DASH server to the user equipment, according to the user equipment performing the vertical switching; The code rate requested by the user equipment, to the

The UE sends DASH service data.

 A twelfth aspect provides a user equipment for transmitting service data, including:

 a receiver, configured to receive DASH service data of the DASH proxy server;

 a processor, configured to: when the vertical handover is performed, control the receiver to stop receiving DASH service data of the DASH proxy server, and after the vertical handover is completed, control the receiver to continue to receive the DASH proxy server according to the DASH proxy server. The DASH service data sent at the determined bit rate.

 With reference to the twelfth aspect, in a first possible implementation, the processor is further configured to: after the vertical handover is completed, control, by the receiver, to continue to receive, by the DASH proxy server, according to the DASH proxy server Before the DASH service data sent by the code rate,

The DASH proxy server sends a handover complete indication message.

 With reference to the first possible implementation manner of the twelfth aspect, in a second possible implementation manner, the handover completion indication message is carried by using an HTTP message.

 In conjunction with the twelfth aspect or the first or second possible implementation of the twelfth aspect, in a third possible implementation, the processor is further configured to:

After the vertical handover is completed, controlling the receiver to continue to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server, to the The DASH proxy server sends information requesting to transmit DASH service data.

 In conjunction with the third possible implementation of the twelfth aspect, in a fourth possible implementation, the processor is further configured to:

 The information requesting transmission of the DASH service data is determined according to the following manner: Determining the processing manner of the completed transmission portion in the fragment that has not completed the transmission when performing the vertical handover, and determining the information requesting to transmit the DASH service data according to the determined processing manner.

 In conjunction with the fourth possible implementation of the twelfth aspect, in a fifth possible implementation, the processor is specifically configured to:

 Determining whether the amount of data of the portion of the fragment that has completed the transmission is greater than a threshold; if so, retaining the portion of the fragment that has completed the transmission; otherwise, deleting the portion of the fragment that has completed the transmission.

 According to a thirteenth aspect, a DASH proxy server for transmitting service data is provided, including: a processor, configured to determine a code rate corresponding to a user equipment that performs vertical handover when performing DASH service data transmission;

 a transmitter, configured to update a code rate in the MPD file according to the determined code rate, and return the updated MPD file to the user equipment; according to a code rate selected by the user equipment from the MPD file, The user equipment sends DASH service data.

 With reference to the thirteenth aspect, in a first possible implementation, the processor is further configured to: after receiving the handover complete indication message of the user equipment, determine a code rate of DASH service data that needs to be sent to the user equipment. .

 With reference to the first possible implementation manner of the thirteenth aspect, in a second possible implementation manner, the handover completion indication message is carried by a Hypertext Transfer Protocol HTTP message.

 In conjunction with the thirteenth aspect or the first or second possible implementation of the thirteenth aspect, the processor is specifically configured to:

 The code rate of the DASH service data that needs to be sent to the user equipment is determined according to the bandwidth of the user equipment in the switched network.

With reference to the thirteenth aspect or the first possible implementation manner of the thirteenth aspect to any one of the third possible implementation manners, in the fourth possible implementation manner, the transmitter is specifically used In:

 The code rate in the MPD file is updated, wherein the code rate in the updated MPD file is not greater than the determined code rate.

 With reference to the thirteenth aspect, or the first possible implementation manner of the thirteenth aspect, to any one of the fourth possible implementation manners, in a fifth possible implementation manner, the transmitter is further configured to: Before determining the code rate of the DASH service data that needs to be sent to the user equipment, sending the received message of the user equipment requesting the MPD file to the DASH server, and sending the response message of the requesting MPD file returned by the DASH server to the Describe the user equipment; and send DASH service data to the UE according to the code rate requested by the user equipment.

 In a fourteenth aspect, a user equipment for transmitting service data is provided, including:

 a receiver, configured to receive DASH service data of the DASH proxy server;

 a processor, configured to: when the vertical handover is performed, control the receiver to stop receiving DASH service data of the DASH proxy server, and after the vertical handover is completed, select a code rate from the MPD file sent by the DASH proxy server to send to the a DASH proxy server, wherein the MPD file is obtained after the DASH proxy server is updated according to a code rate determined by the DASH proxy server; and controlling the receiver to continue receiving the DASH proxy server according to a received code rate. The DASH service data sent.

 With reference to the fourteenth aspect, in a first possible implementation, the processor is further configured to: after the vertical handover is completed, select a code rate from the MPD file sent by the DASH proxy server, and send the code to the DASH. Before the proxy service, a handover complete indication message is sent to the DASH proxy server.

 With reference to the first possible implementation manner of the fourteenth aspect, in a second possible implementation manner, the handover completion indication message is carried by using an HTTP message.

 In conjunction with the fourteenth aspect or the first or second possible implementation of the fourteenth aspect, in a third possible implementation, the processor is further configured to:

After the vertical handover is completed, continuing to receive the DASH service data sent by the DASH proxy server according to the received code rate, sending a request to the DASH proxy server to transmit the DASH service. Information about the data.

 In conjunction with the third possible implementation of the fourteenth aspect, in a fourth possible implementation, the processor is further configured to:

 The information requesting transmission of the DASH service data is determined according to the following manner: Determining the processing manner of the completed transmission portion in the fragment that has not completed the transmission when performing the vertical handover, and determining the information requesting to transmit the DASH service data according to the determined processing manner.

 In conjunction with the fourth possible implementation of the fourteenth aspect, in a fifth possible implementation, the processor is specifically configured to:

 Determining whether the amount of data of the portion of the fragment that has completed the transmission is greater than a threshold; if so, retaining the portion of the fragment that has completed the transmission; otherwise, deleting the portion of the fragment that has completed the transmission.

 In the embodiment of the present invention, the DASH service data is sent to the user equipment that performs vertical handover when performing DASH service data transmission by using the code rate determined by the DASH proxy server, or the code rate in the MPD file is updated according to the determined code rate, and according to the ongoing The user equipment that performs vertical handover during the DASH service data transmission sends the DASH service data to the user equipment from the code rate selected by the updated MPD file, thereby reducing the impact on the stability of the DASH service after the vertical handover occurs.

 Further, the user equipment can be adapted to the bandwidth of the new network more quickly after changing from the huge wireless bandwidth resources, requesting a suitable video bit rate, and allowing the process to be smoothly excessive, and preventing the client from overflowing. The occurrence of the situation eliminates video jitter and jams. The user's video experience is increased; the difference caused by the adaptive algorithms of different clients is shielded, no matter what adaptive algorithm is used by the client, it can help the client to determine the bit rate and improve the video experience. DRAWINGS

1A is a schematic diagram of a process of acquiring a media stream file based on DASH technology in the background; FIG. 1B is a schematic diagram of a location of a DASH proxy server in a network according to an embodiment of the present invention; FIG. 2A is a schematic diagram of an interaction process between a DASH proxy server and a user equipment according to an embodiment of the present invention; ; 2B is a schematic flowchart of a method for selecting a DASH proxy server by a P-GW according to an embodiment of the present invention; FIG. 3A is a schematic flowchart of a method for transmitting service data by a first DASH proxy server according to an embodiment of the present invention;

 3B is a schematic flow chart of a method for receiving bandwidth information by a DASH proxy server according to an embodiment of the present invention;

 4 is a schematic flowchart of a method for transmitting service data by a user equipment according to an embodiment of the present invention; FIG. 5 is a schematic flowchart of a method for transmitting service data by a DASH proxy server and a user equipment according to an embodiment of the present invention;

 6A is a schematic diagram of marking a first DASH proxy server according to an embodiment of the present invention; FIG. 6B is a schematic diagram of marking a second DASH proxy server according to an embodiment of the present invention; FIG. 7 is a flow chart of rate control of a DASH proxy server according to an embodiment of the present invention; FIG. 8 is a schematic flowchart of a method for performing fragmentation processing by a user equipment according to an embodiment of the present invention; FIG. 9 is a schematic flowchart of a method for performing service transmission after a user equipment switches from WLAN to LTE according to an embodiment of the present invention;

 10 is a schematic flowchart of a method for transmitting service data by a second DASH proxy server according to an embodiment of the present invention;

 11 is a schematic flowchart of a method for transmitting service data by a second user equipment according to an embodiment of the present invention; FIG. 12 is a schematic flowchart of a method for transmitting service data by a second DASH proxy server and a user equipment according to an embodiment of the present invention;

 13 is a schematic flowchart of a method for performing service transmission after a second user equipment switches from WLAN to LTE according to an embodiment of the present invention;

 14 is a schematic diagram of a system for transmitting service data according to an embodiment of the present invention;

 FIG. 15 is a schematic diagram of a second system for transmitting service data according to an embodiment of the present invention; FIG.

 16 is a schematic diagram of a first DASH proxy server according to an embodiment of the present invention;

 FIG. 17 is a schematic diagram of a first user equipment according to an embodiment of the present invention;

 18 is a schematic diagram of a second DASH proxy server according to an embodiment of the present invention;

FIG. 19 is a schematic diagram of a second user equipment according to an embodiment of the present invention; 20 is a schematic diagram of a third DASH proxy server according to an embodiment of the present invention;

 21 is a schematic diagram of a third user equipment according to an embodiment of the present invention;

 FIG. 22 is a schematic diagram of a fourth DASH proxy server according to an embodiment of the present invention; FIG.

 FIG. 23 is a schematic diagram of a fourth user equipment according to an embodiment of the present invention. Detailed ways

 In the embodiment of the present invention, the DASH service data is sent to the user equipment that performs vertical handover when performing DASH service data transmission by using the code rate determined by the DASH proxy server, or the code rate in the MPD file is updated according to the determined code rate, and according to the ongoing The user equipment that performs vertical handover during the DASH service data transmission sends the DASH service data to the user equipment from the code rate selected by the updated MPD file, thereby reducing the impact on the stability of the DASH service after the vertical handover occurs.

 Among them, in a heterogeneous wireless network, switching between different access networks is called vertical handover. The solution of the embodiments of the present invention is applicable to vertical switching between any networks.

 Preferably, the solution of the embodiment of the present invention is suitable for a better effect when switching from a high bandwidth vertical to a low bandwidth scenario. For example, a WLAN (Wireless Local Area Network) is vertically switched to a 3GPP network, such as an LTE (Long Term Evolution) network.

 Currently, the DASH server is located on the public network and cannot be controlled and adjusted by the operator. For this reason, the embodiment of the present invention adds a DASH Proxy server as a proxy buffer between the P-GW (PDN GW, packet data gateway) and the DASH server, as shown in FIG. 1B. The request sent by the user equipment to the network side is sent to the DASH proxy server. If the resource is cached in the DASH proxy server, the DASH proxy server directly returns the resource to the user equipment. If the resource is not cached in the DASH proxy server, the DASH proxy server sends a request to the DASH server and downloads the resource, and then returns it to the user device.

 The DASH proxy server determines the resources that the user equipment needs to download according to the content contained in the received information of the user equipment.

In the implementation, the DASH proxy server will get the information requested by the user equipment, and from the information The resources requested by the user equipment are known.

 The DASH proxy server detects the DASH event and interacts with the PCRF (Policy and Charging Rules Function) to exchange DASH session messages. It can also operate on MPD files. HTTP messages are transmitted between the P-GW and the DASH Server.

 After the vertical switching of the user equipment, the DASH proxy server makes a rate decision to help the user equipment correctly estimate the bandwidth and fully adapt to the new wireless network.

 As shown in FIG. 2A, in the schematic diagram of the interaction flow between the DASH proxy server and the user equipment in the embodiment of the present invention, the following steps are included:

 Step 201: The user equipment establishes a default EPS (Evolved Packet System) bearer between the P-GW (PDN GW, packet data gateway).

 Step 202: The user equipment requests an MPD file from the DASH server through the P-GW.

 Step 203: After receiving the requested MPD file, the DASH selects a suitable DASH proxy server by the P-GW and sends the request MPD file to the DASH proxy server. The process of selecting the DASH proxy server by the P-GW can be seen in FIG. 2B.

 Step 204: After the DASH proxy server receives the request MPD file, the DASH proxy server detects the DASH event, and the DASH proxy server forwards the request MPD file to the DASH server.

 Step 205: The DASH server returns the response information including the MPD file to the DASH proxy server.

 Step 206: The DASH proxy server returns response information including the MPD file to the user equipment. Step 207: The user equipment requests the fragment 1 of the IMpbs according to the obtained MPD file. Step 208: The P-GW forwards the request of the user equipment.

 Step 209: The DASH proxy server queries the PCRF for the request.

Step 210: The PCRF returns a recommended result to the DASH proxy server after granting the request. Generally, the PCRF will judge whether it is permitted according to the deployment of the operator. The returned result is generally the result of quality assurance, such as QoS quality or maximum support rate. Step 211A: If the DASH proxy server caches the requested resource, directly return the resource to the user equipment; or

 Step 211B: If the DASH proxy server does not cache the requested resource, request the resource from the DASH server and return the resource to the user equipment.

 As shown in FIG. 2B, the method for selecting a DASH proxy server by the P-GW in the embodiment of the present invention includes the following steps:

 Step 221: After receiving the request MPD file from the user equipment, the P-GW determines that there is a DASH event, and forwards the DNS resolution request to the DNS (Domain Name Server).

 Step 222: The DNS obtains the IP address of the DASH proxy server according to the received DNS resolution request, and returns it to the P-GW.

 In the implementation, after obtaining the IP address of the DASH proxy server, the P-GW can also forward the IP address of the DASH proxy server to the user equipment.

 As shown in FIG. 3A, the method for transmitting service data by the first DASH proxy server according to the embodiment of the present invention includes the following steps:

 Step 301: The DASH proxy server determines a code rate of the DASH service data that needs to be sent to the user equipment, where the user equipment is a user equipment that performs vertical handover when performing DASH service data transmission;

 Step 302: The DASH proxy server sends DASH service data to the user equipment according to the determined code rate.

 Preferably, in step 301, after receiving the handover completion indication message of the user equipment, the DASH proxy server determines that the user equipment has completed the handover, and then determines the code rate of the DASH service data that needs to be sent to the user equipment.

 In an implementation, the handover complete indication message may be carried by an HTTP message.

 Preferably, the DASH proxy server determines the code rate of the DASH service data that needs to be sent to the user equipment according to the bandwidth of the user equipment in the switched network.

The DASH proxy server needs to determine the user equipment before determining the code rate of the DASH service data that needs to be sent to the user equipment according to the bandwidth of the user equipment in the switched network. Bandwidth in the switched network.

 In the embodiment of the present invention, the DASH proxy server determines the bandwidth of the user equipment in the switched network. The following is an example of the user equipment switching to the LTE network.

 Mode 1: Due to the actual deployment of the LTE, the operator generally guarantees a basic wireless bandwidth of the user equipment in the LTE cell, and then a static pre-configuration can be performed on the supportable range of the LTE wireless rate in the DASH proxy server. The value, such as the supportable code rate range is 300~900kbit/s;

 Mode 2: The DASH proxy server estimates the bandwidth of the newly added user equipment according to different scheduling algorithms used by the eNodeB (Evolved Base Station) of the LTE. After the user equipment is switched to the LTE network, the CQI (Channel Quality Indicator) is reported. The eNodeB can estimate the channel quality of the user equipment according to the CQI of the UE, and implement the user equipment according to its own scheduling algorithm. Estimation of bandwidth. The specific method is as follows:

 1. The eNodeB uses RR (Round-Robin, round robin) polling scheduling. In this case, the radio resources of LTE are equally allocated, that is, each user equipment obtains equal radio resources. At this time, the number of RBs (resource blocks) to which each user equipment is allocated is the total number of RBs of the eNodeB divided by the total number of user equipments. The eNodeB obtains the SINR according to the CQI and the SINR (Signal Interference Noise Ratio) corresponding table, and obtains the transmission rate of each RB by using a table corresponding to the SINR and the radio rate. The estimated wireless bandwidth value can be obtained by multiplying the number of RBs obtained by the user equipment. The corresponding SINR and rate table are as follows:

2 -3.40 QPSK 0.2344 42.20

3 -1.70 QPSK 0.3770 67.86

4 -0.19 QPSK 0.6016 108.28

5 1.34 QPSK 0.8770 157.86

6 2.64 QPSK 1.1758 211.64

16QAM

 ( Quadrature

 7 5.16 Amplitude 1.4766 265.79

 Modulation

 Intersection amplitude modulation)

8 6.71 16QAM 1.9141 344.54

9 8.18 16QAM 2.4063 433.13

10 10.43 64QAM 2.7305 491.49

11 11.84 64QAM 3.3223 598.01

12 13.32 64QAM 3.9023 702.14

13 15.53 64QAM 4.5234 814.21

14 16.20 64QAM 5.1152 920.74

15 22.38 64QAM 5.5547 999.85

2. The eNodeB uses the PF scheduling algorithm. In the scheduling algorithm, each user is assigned a priority, and the user with the highest priority in the cell at any time receives the service. The priority parameter is:

Where 3⁄4 (represents the time t, the average download rate of user k.) represents the time t, The speed at which the i-th RB can carry on user K. The scheduling algorithm decides which UE to assign the RB to based on the calculated priority metric.

 3. According to the percentage of the total download rate occupied by each UE, the bandwidth of the user equipment in the switched network can be calculated.

 After determining the bandwidth of the user equipment in the switched network, it is necessary to determine the code rate according to the bandwidth. There are many ways to determine the bitrate based on bandwidth:

 For example, the correspondence between the bandwidth range and the code rate may be preset, and then the code rate corresponding to the bandwidth range in which the determined bandwidth is located is taken as the determined code rate.

 For example: Determine the highest supported code rate of the user equipment without Buffer underflow as the determined code rate.

 For the specific user equipment, the maximum supported code rate that does not appear Buffer underflow can be determined by the following methods:

 1. Determine the bit rate level of the DASH service requested by the user equipment requestBit (request bit). 2. Determine the size of the data that needs to be downloaded before the user equipment switches D = requestBit* segmentDuration. requestBit indicates the bit rate level of the DASH service requested by the user equipment; segmentDuration indicates the length of the fragment requested by the user equipment.

 3. Determine T = D/R, where T is the estimated time required for the UE to download the part of the data; R is the bandwidth of the user equipment in the switched network.

 4. Determine L = buffer-minBuffer, where L is the longest download time allowed for the estimated user equipment. Buffer indicates the length of data buffered by the user device; minBuffer indicates the reserved value for ensuring smooth playback of the DASH service.

 5. Determine if the result of step 3 is not less than the result of step 4, ie! ^ If it is established, it indicates that the bit rate level is too high, downgrade the bit rate level of the DASH service requested by the user equipment, and then re-determine T.

 6. Repeat step 5, until T<L, the bit rate level of the DASH service requested by the user equipment that was last lowered is used as the determined code rate.

In the foregoing mode 2, the base station needs to send the user equipment to the DASH proxy server after the handover. The bandwidth in the network is shown in Figure 3B:

 Step 311: The eNodeB performs a network switching process.

 Step 312: The DASH proxy server receives a message that the user equipment completes the handover.

 Step 313: The eNodeB estimates a bandwidth change of the user equipment.

 Step 314: The DASH proxy server sends a message to the eNodeB to query bandwidth information of the user equipment.

 Step 315: The eNodeB returns bandwidth information of the user equipment to the DASH proxy server.

 The DASH proxy server sends the DASH service data to the user equipment according to the determined code rate, including:

 The DASH proxy server transmits the DASH service data and the determined code rate according to the received request of the user equipment, and sends the DASH service data to the user equipment.

 Specifically, the DASH proxy server determines the DASH service data that needs to be transmitted for the user equipment according to the received information of the DASH service data transmitted by the user equipment;

 Then, the DASH proxy server selects DASH service data that is not greater than the determined code rate and needs to be transmitted by the user equipment from the DASH service data that is required to be transmitted by the user equipment corresponding to the multiple code rates, and sends the data to the user equipment.

 In an implementation, the information requesting to transmit DASH service data may be carried by an HTTP message. After the user equipment performs vertical handover, the application layer of the user equipment cannot correctly perceive the huge change of the bandwidth of the wireless network resource, and therefore cannot request an appropriate code rate, so the DASH proxy server is required to determine the code rate, if the user equipment can already With the correct perceived bandwidth, the DASH proxy server does not need to determine the bit rate.

 Specifically, after receiving the information of the DASH service data requested by the user equipment, the DASH proxy server compares the code rate in the information (that is, the code rate requested by the user equipment) with the code rate determined by the DASH proxy server, if not The same, determining that the user equipment cannot correctly sense the bandwidth, and then sending the DASH service data to the user equipment according to the determined code rate;

If the same, it is determined that the user equipment can correctly sense the bandwidth, and the number of DASH services can be sent to the user equipment according to the code rate in the information or the code rate determined by the DASH proxy server. According to. After receiving the information that the user equipment requests to transmit the DASH service data, the DASH service data is directly sent to the user equipment according to the code rate in the information.

 Before performing DASH service data transmission, the user equipment needs to obtain the MPD file corresponding to the DASH service. Specifically, after receiving the message that the user equipment requests the MPD file, the DASH proxy server sends the received message that the user equipment requests the MPD file to the DASH server, and returns a response message of the requested MPD file returned by the DASH server. Sending to the user equipment; the DASH proxy server sends DASH service data to the UE according to a code rate requested by the user equipment.

 As shown in FIG. 4, the method for transmitting service data by the first user equipment in the embodiment of the present invention includes the following steps:

 Step 401: The user equipment stops receiving DASH service data of the DASH proxy server when performing vertical handover.

 Step 402: After the vertical handover is completed, the user equipment continues to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server.

 Preferably, in step 402, the user equipment continues to receive the

Before the DASH proxy server sends the DASH service data according to the code rate determined by the DASH proxy server, the method further includes:

 The user equipment sends a handover complete indication message to the DASH proxy server.

 In an implementation, the handover complete indication message may be carried by an HTTP message.

 Preferably, in step 402, the user equipment continues to receive the

Before the DASH proxy server sends the DASH service data according to the code rate determined by the DASH proxy server, the method further includes:

 The user equipment sends information requesting to transmit DASH service data to the DASH proxy server.

The user equipment determines the information for requesting to transmit the DASH service data according to the following manner: the user equipment determines a processing manner of the completed transmission part in the fragment that is not completed when performing the vertical handover, and according to the determined processing manner, Determining the request to transmit DASH service data Information.

 Preferably, the manner in which the user equipment determines the DASH service data that is not completed is processed, including:

 Determining, by the user equipment, whether the amount of data of the part of the fragment that has completed the transmission is greater than a threshold;

 If so, the portion of the slice that has completed the transfer is retained; otherwise, the portion of the slice that has completed the transfer is deleted.

 As shown in FIG. 5, the method for transmitting service data by the first DASH proxy server and user equipment according to the embodiment of the present invention includes the following steps:

 Step 501: The user equipment performs a vertical handover process of the network.

 The vertical handover process of the user equipment includes registration authentication in the LTE network, and establishment of a tunnel and a bearer. For details, refer to 3GPP TS23.402, and details are not described herein again.

 After the process is completed, it indicates that the user equipment has been connected to the new network, and a wireless bearer connection is established, so that the uplink and downlink communication can be performed in the new network.

 If the user equipment has DASH service data that has not been transmitted before the vertical handover, the transmission will stop when the vertical handover is performed.

 Step 502: The user equipment sends a vertical handover completion indication message (ie, a notification message of the HO) to the DASH proxy server, to notify the DASH proxy server that the vertical handover has been completed.

 Preferably, the vertical handover completion indication message includes a mobility even indication, that is, prompting the DASH proxy server that the UE has completed the network handover.

 In an implementation, the message communication of the application layer between the user equipment and the DASH proxy server in the embodiment of the present invention can be implemented by extending a URL (Uniform Resource Locator) of the HTTP request. For example, the vertical handover completion indication message can be carried by an HTTP message.

 Specifically, the corresponding parameter information is added to the URL to indicate the status of the user equipment, such as the vertical handover indication in this embodiment.

The specific implementation is as follows: Htt :// sever. example . com /media_A.mp4? Event=HO_event

 If the user equipment contains unsuccessful fragments at this time, since the user equipment has previously stopped transmitting, it is necessary to process the undownloaded fragments. The user device may choose to discard or retain the downloaded portion of the score that has not been downloaded. The specific process can be seen in Figure 7.

 If the UE does not have a downloaded slice at this time, no fragmentation processing is performed.

 Step 503: After receiving the vertical handover completion indication message, the DASH proxy server stops transmitting the un-downloaded fragment of the DASH to the user equipment, and marks the state of the user equipment as a handover state, and marks the state of the user as requiring a code. Rate control.

 Step 504: The user equipment sends information requesting to transmit DASH service data to the network side. This information includes the buffer remaining time and the current requested bit rate.

 If the request information of the user equipment is not recorded on the network side, the identifier of the DASH service that needs to be requested may also be included.

 In an implementation, the message communication of the application layer between the user equipment and the DASH proxy server in the embodiment of the present invention can be implemented by extending the URL of the HTTP request. For example, information requesting to transmit DASH service data is carried by an HTTP message.

 The parameter information in the information requesting to transmit the DASH service data may be expressed by using a WebAPI (Internet Application Programming Interface) description language (such as WADL: Web Application Description Language, Internet Application Description Language), and the network entity can be parsed normally. .

 In fact, under the mouth: htt : // sever. example . com /media— A.mp4 ? Buffer=b, RequestBit=r, LastRequest=l

 The Buffer carries the remaining time of the buffer, RequestBit is the code rate requested by the user equipment, and LastRequest is the code rate of the last request.

 Preferably, the video jitter can be reduced by the UE video stability algorithm according to the code rate of the last request.

Step 505: After receiving the information requesting to transmit the DASH service data, the DASH proxy server marks that the state of the user equipment cannot be adapted to the network bandwidth after the handover, and after the state is required to perform the rate control, according to the user equipment after the handover. Bandwidth in the network, determined to be sent to The code rate of the DASH service data of the user equipment returns a response message requesting to transmit the DASH service data to the user equipment.

 Preferably, the response message requesting to transmit DASH service data may include a code rate determined by the DASH proxy server.

 In an implementation, the message communication of the application layer between the user equipment and the DASH proxy server in the embodiment of the present invention can be implemented by extending the URL of the HTTP request. For example, a response message requesting transmission of DASH service data is carried by an HTTP message.

 The DASH proxy server, in the HTTP reply message, carries the URL information inserted into the network parameter through the Content-Location header field, and is used to notify the user equipment of the code rate determined by the DASH proxy server, thereby assisting the user equipment to adapt. Switched network.

 Specific implementation ^: Content-Location: htt :// sever. example . com /media- A.mp4? SuggestBit=B

 Among them, SuggestBit (Proposed Bit) is the code rate that the Proxy determines for the client.

 Step 506: The DASH proxy server sends the DASH service data to the user equipment according to the determined code rate.

 After the user equipment performs vertical handover, the application layer of the user equipment cannot correctly perceive the huge change of the bandwidth of the wireless network resource, and therefore cannot request an appropriate code rate, so the DASH proxy server needs to make a decision on the code rate.

 If the user equipment has been able to correctly sense the bandwidth, then the DASH proxy server can modify its own state to release the rate control and exit the control.

 Since the state of itself is the release rate control, the state of the user equipment is modified to adapt to the network bandwidth.

 Specifically, when the code rate requested by the user equipment is the same as the code rate determined by the DASH proxy server, the DASH proxy server considers that the user equipment can correctly sense the bandwidth, reach a steady state, and exit control.

When the DASH proxy server needs to send the DASH service data to the user equipment, the DASH service data is sent to the user equipment according to the code rate requested by the user equipment. In the implementation, since the bandwidth changes greatly after the handover, the user equipment cannot adapt to the condition of the new network at this time, and the DASH proxy server needs to make decisions and changes to the requested code rate.

 The status of the user equipment can be defined according to the following table. For specific status changes, see Figure 6A:

The status of the DASH proxy server can be defined according to the following table. The specific status changes can be seen in Figure 6B:

As shown in FIG. 7, the DAST proxy server performing rate control according to the embodiment of the present invention includes the following steps:

 Step 701: The DASH proxy server starts a code rate control process.

 Step 702: The DASH proxy server receives the code rate requested by the user equipment.

Step 703: The DASH proxy server determines whether the code rate requested by the user equipment is the same as the code rate determined by the DASH proxy server; if yes, step 704 is performed; otherwise, step 705 is performed. Step 704: The DASH proxy server exits the rate control process.

 Step 705: The DASH proxy server sends the DASH service data to the user equipment according to the code rate determined by the DASH proxy server, and returns to step 702.

 As shown in FIG. 8, the method for performing fragmentation processing by the user equipment according to the embodiment of the present invention includes the following steps: Step 801: After completing the vertical handover, the user equipment sends a vertical handover completion indication message to the DASH proxy server.

 Step 802: The user equipment determines whether there is DASH service data that has not been transmitted. If yes, step 803 is performed; otherwise, the process ends.

 Step 803: The user equipment determines whether there is a fragment that does not complete the transmission when the vertical handover is performed. If yes, step 804 is performed; otherwise, step 807 is performed.

 Step 804: The user equipment determines whether the amount of data of the completed transmission part in the fragment that has not completed the transmission when performing the vertical handover is greater than the threshold; if yes, step 805 is performed; otherwise, step 806 is performed.

 Step 805: The user equipment reserves the part of the fragment that has completed the transmission, immediately uses the bit stream based switching, and performs step 807.

 The procedure for using bit stream based handover can be seen in the procedure for using bit stream-based handover as specified in the 3GPP protocol.

 Step 806: The user equipment deletes the part of the fragment that has completed the transmission, and determines that the video fragment needs to be requested again, and performs step 807.

 Step 807: The user equipment sends information requesting to transmit DASH service data to the DASH proxy server.

 Step 808: The user equipment receives the DASH service data sent by the DASH proxy server. As shown in FIG. 9, the method for performing service transmission after the first user equipment switches from WLAN to LTE according to the embodiment of the present invention includes: The process can refer to FIG. 2A.

Step 902: The user equipment prepares for handover. For the specific preparation process, refer to the provisions in the 3GPP protocol. The user equipment is ready to switch.

 Step 903: The user equipment sends an Attach message to the E-UTRAN. If it is a network side controlled handover procedure, then steps 902 and 903 are not performed.

 Step 904: The user equipment performs a handover process from WLAN to LTE.

 Step 905: The user equipment sends a Handover message to the Dash proxy server, where the message includes the handover indication information.

 Step 906: The user equipment processes the undownloaded fragments. If there are no undownloaded fragments, skip the step.

 Step 907: After receiving the Handover message, the Dash proxy server stops sending data, and determines a code rate corresponding to the user equipment.

 Step 908: The user equipment sends a request message carrying information requesting to transmit DASH service data to the Dash proxy server.

 The information requesting to transmit the DASH service data includes: a buffer remaining time and a current requested code rate. If the network side does not record the request message before the user equipment, it also needs to send the information of the last request. The device for recording the request message before the user equipment herein may be a Dash proxy server, or other device capable of obtaining a request message from the Dash proxy server.

 Preferably, the request message may further include an identifier of the user equipment requesting to transmit the DASH service data. For example, which fragment is specifically transmitted or which part of the data is transmitted.

 Step 909: The Dash proxy server returns a request response message to the user equipment.

 Preferably, the request response message includes a code rate requested by the network side device.

 Step 910: The Dash proxy server performs DASH transmission with the user equipment.

 Specifically, after determining that the rate control is required, the Dash proxy server compares the code rate requested by the user equipment with the code rate of the user equipment determined by the Dash proxy server;

 If they are the same, the DASH service data is sent to the user equipment according to the code rate requested by the user equipment or the code rate of the user equipment determined by the Dash proxy server.

If not, the number of DASH services is sent to the user equipment according to the code rate of the user equipment determined by the Dash proxy server. After determining that the rate control is not required, the Dash proxy server sends the DASH service data to the user equipment according to the code rate requested by the user equipment.

 The above describes the return of DASH service data according to the code rate determined by the Dash proxy server. In addition to the above manner, the embodiment of the present invention can also be implemented by updating an MPD file. By updating the MPD file, it is not necessary to enter the continuous control state compared to the above method. Due to the reduction of the network bandwidth after the handover, the Dash proxy server can determine the highest code rate that the new network can support. The Dash Proxy Server will remove the option in the MPD file for a higher bitrate than the estimated value. Then the new MPD file is updated between the user equipment and the Dash proxy server, the user equipment sends an MPD file request to the Dash proxy server, and the Dash proxy server returns the updated MPD file. The user equipment uses its own adaptive algorithm to make the code rate decision, but at this time, the inappropriate code rate range has been removed by the MPD file, so the requested code rate range has been updated, and the code requested by the user equipment can be guaranteed. The rate matches the switched network, enabling the user equipment to adapt to the new network more quickly.

 As shown in FIG. 10, the method for transmitting service data by the second DASH proxy server in the embodiment of the present invention includes the following steps:

 Step 1010: The DASH proxy server determines a code rate corresponding to the user equipment that performs vertical handover when performing DASH service data transmission.

 Step 1020: The DASH proxy server updates the code rate in the MPD file according to the determined code rate, and returns the updated MPD file to the user equipment.

 Step 1030: The DASH proxy server sends DASH service data to the user equipment according to a code rate selected by the user equipment from the MPD file.

 Preferably, in step 1010, the DASH proxy server determines that the user equipment has completed the handover after receiving the handover completion indication message of the user equipment, and then determines the code rate of the DASH service data that needs to be sent to the user equipment.

 In an implementation, the handover complete indication message may be carried by an HTTP message.

 Preferably, the DASH proxy server determines the code rate of the DASH service data that needs to be sent to the user equipment according to the bandwidth of the user equipment in the switched network.

The DASH proxy server determines the bandwidth of the user equipment in the switched network. Before the bit rate of the DASH service data to be sent to the user equipment needs to be determined, the bandwidth of the user equipment in the switched network needs to be determined.

 The manner in which the DASH proxy server determines the bandwidth of the user equipment in the switched network is the same as the manner in which the DASH proxy server determines the bandwidth of the user equipment in the switched network in FIG. 3, and details are not described herein again.

 After determining the bandwidth of the user equipment in the switched network, it is necessary to determine the code rate according to the bandwidth. The manner in which the DASH proxy server determines the code rate according to the bandwidth in FIG. 10 is the same as the manner in which the DASH proxy server determines the code rate according to the bandwidth in FIG. 3, and details are not described herein again.

 For the specific process of the base station transmitting the bandwidth of the user equipment in the switched network to the DASH proxy server, refer to FIG. 3B.

 The DASH proxy server updates the code rate in the MPD file according to the determined code rate, including:

 The DASH proxy server updates the code rate in the MPD file, wherein the code rate in the updated MPD file is not greater than the determined code rate.

 Before performing DASH service data transmission, the user equipment needs to obtain the MPD file corresponding to the DASH service. Specifically, after receiving the message that the user equipment requests the MPD file, the DASH proxy server sends the received message that the user equipment requests the MPD file to the DASH server, and returns a response message of the requested MPD file returned by the DASH server. Sending to the user equipment; the DASH proxy server sends DASH service data to the UE according to a code rate requested by the user equipment.

 As shown in FIG. 11, the method for transmitting service data by the second user equipment in the embodiment of the present invention includes the following steps:

 Step 1110: The user equipment stops receiving DASH service data of the DASH proxy server when performing vertical handover.

Step 1120: After the vertical handover is completed, the user equipment selects a code rate from the MPD file sent by the DASH proxy server to send to the DASH proxy server, where the MPD file is the DASH proxy server according to the DASH proxy. After the server determines the code rate update owned;

 Step 1130: The user equipment receives DASH service data that is sent by the DASH proxy server according to the received code rate.

 Preferably, in step 1120, the user equipment continues to receive the macro after the vertical handover is completed.

Before the DASH proxy server sends the DASH service data according to the code rate determined by the DASH proxy server, the method further includes:

 The user equipment sends a handover complete indication message to the DASH proxy server.

 In an implementation, the handover complete indication message may be carried by an HTTP message.

 Preferably, in step 1120, the user equipment continues to receive the macro after the vertical handover is completed.

Before the DASH proxy server sends the DASH service data according to the code rate determined by the DASH proxy server, the method further includes:

 The user equipment sends information requesting to transmit DASH service data to the DASH proxy server.

 The user equipment determines the information for requesting to transmit the DASH service data according to the following manner: the user equipment determines a processing manner of the completed transmission part in the fragment that is not completed when performing the vertical handover, and according to the determined processing manner, Determine the information requesting to transmit DASH service data.

 Preferably, the manner in which the user equipment determines the DASH service data that is not completed is processed, including:

 Determining, by the user equipment, whether the amount of data of the part of the fragment that has completed the transmission is greater than a threshold;

 If so, the portion of the slice that has completed the transfer is retained; otherwise, the portion of the slice that has completed the transfer is deleted.

 For the method for the user equipment to perform the fragmentation processing, refer to FIG. 8.

 As shown in FIG. 12, a method for transmitting service data by a second DASH proxy server and user equipment according to an embodiment of the present invention includes the following steps:

Step 1201: The user equipment performs a vertical handover process of the network. The vertical handover process of the user equipment includes a registration authentication in the LTE network, and a process of establishing a tunnel and a bearer. For details, refer to 3GPP TS 23.402, and details are not described herein again.

 After the process is completed, it indicates that the user equipment has been connected to the new network, and a wireless bearer connection is established, so that the uplink and downlink communication can be performed in the new network.

 If the user equipment has DASH service data that has not been transmitted before the vertical handover, the transmission will stop when the vertical handover is performed.

 Step 1202: The user equipment sends a vertical handover complete indication message (ie, a notification message of the HO) to the DASH proxy server, to notify the DASH proxy server that the vertical handover has been completed.

 Preferably, the vertical handover completion indication message includes handover indication information.

 In an implementation, the message communication of the application layer between the user equipment and the DASH proxy server in the embodiment of the present invention can be implemented by extending the URL of the HTTP request. For example, the vertical handover completion indication message can be carried by an HTTP message.

 Specifically, the corresponding parameter information is added to the URL to indicate the status of the user equipment, such as the vertical handover indication in this embodiment.

 The specific implementation is as follows:

 Htt :// sever. example . com /media_A.mp4? Event=HO_event

 If the user equipment contains unsuccessful fragments at this time, since the user equipment has previously stopped transmitting, it is necessary to process the undownloaded fragments. The user device may choose to discard or retain the downloaded portion of the score that has not been downloaded. The specific process can be seen in Figure 7.

 If the UE does not have a downloaded slice at this time, no fragmentation processing is performed.

 Step 1203: After receiving the vertical handover completion indication message, the DASH proxy server stops transmitting the fragment that has not been downloaded by the DASH to the user equipment.

 Step 1204: The DASH proxy server determines, according to the bandwidth of the user equipment in the switched network, a code rate of the DASH service data that the user equipment can support at the current network, and updates the MPD file according to the determined code rate, and the MPD file is exceeded. Determine the bit rate removal.

 Step 1205: The user equipment requests an MPD file from the DASH proxy server.

Step 1206: The DASH proxy server returns the updated MPD file to the user equipment. Step 1207: The user equipment sends information requesting to transmit DASH service data to the network side. Step 1208: The DASH proxy server returns a response message requesting to transmit DASH service data to the user equipment.

 This information includes the remaining time of the buffer and the selected code rate in the MPD file.

 If the request information of the user equipment is not recorded on the network side, the identifier of the DASH service that needs to be requested may also be included.

 In an implementation, the message communication of the application layer between the user equipment and the DASH proxy server in the embodiment of the present invention can be implemented by extending the URL of the HTTP request. For example, information requesting to transmit DASH service data is carried by an HTTP message.

 The parameter information in the information requesting to transmit the DASH service data may be a Web API.

4 The language is expressed in (WADL: Web Application Description Language), which can be used for network entities to parse normally.

 In fact, under the mouth: htt : // sever. example . com /media— A.mp4 ? Buffer=b, RequestBit=r, LastRequest=l

 The Buffer carries the remaining time of the buffer, RequestBit is the code rate requested by the user equipment, and LastRequest is the code rate of the last request.

 Preferably, the video jitter can be reduced by the UE video stability algorithm according to the code rate of the last request.

 Step 1208: The DASH proxy server sends the DASH service data to the user equipment according to the received code rate.

 Step 1204 may be performed after the DASH proxy server receives the requested MPD file. Preferably, after receiving the information requesting to transmit the DASH service data, the DASH proxy server may return a response message requesting to transmit the DASH service data to the user equipment.

 In an implementation, the message communication of the application layer between the user equipment and the DASH proxy server in the embodiment of the present invention can be implemented by extending the URL of the HTTP request. For example, a response message requesting transmission of DASH service data is carried by an HTTP message.

Among them, the DASH proxy server in the HTTP reply message, through the Content-Location header The domain carries the URL information inserted into the network parameter, and is used to notify the user equipment of the code rate determined by the DASH proxy server.

 As shown in FIG. 13, the method for performing service transmission after the second user equipment switches from WLAN to LTE according to the embodiment of the present invention includes the following steps: The process can be seen in FIG. 2A.

 Step 1302: The user equipment is ready to switch. For the specific preparation process, refer to the process of preparing the handover of the user equipment specified in the 3GPP protocol.

 Step 1303: The user equipment sends an Attach message to the E-UTRAN. If it is the switching process of the network side control, then steps 902 and 903 are not performed.

 Step 1304: The user equipment performs a handover process from WLAN to LTE.

 Step 1305: The user equipment sends a Handover message to the Dash proxy server, where the message includes the handover indication information.

 Step 1306: The user equipment processes the undownloaded fragments. If there are no unsuccessful fragments, skip the step.

 Step 1307: After receiving the Handover message, the Dash proxy server stops sending data, and determines the code rate of the DASH service data that the user equipment can support at the current network according to the bandwidth of the user equipment in the switched network, and according to the determined The code rate updates the MPD file and removes the determined code rate from the MPD file.

 Step 1308: The user equipment requests a message of the MPD file from the DASH proxy server.

 Step 1309: The DASH proxy server returns a response message including the MPD file to the user equipment. Step 1310: The user equipment transmits DASH service data according to the received MPD file and the DASH proxy server.

 As shown in FIG. 14, the system for transmitting service data in the first embodiment of the present invention includes:

The DASH proxy server 141 is configured to determine a code rate corresponding to the user equipment that performs vertical handover when performing DASH service data transmission, and send DASH service data to the user equipment according to the determined code rate; The user equipment 142 is configured to stop receiving the DASH service data of the DASH proxy server when performing the vertical handover, and continue to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server after the vertical handover is completed. .

 As shown in FIG. 15, a second system for transmitting service data according to an embodiment of the present invention includes:

 The DASH proxy server 151 is configured to determine a code rate corresponding to the user equipment that performs vertical handover when performing DASH service data transmission, update a code rate in the MPD file according to the determined code rate, and return the updated MPD file to the user. The device sends DASH service data to the user equipment according to a code rate selected by the user equipment from the MPD file;

 The user equipment 152 is configured to stop receiving DASH service data of the DASH proxy server when performing vertical handover, and select a code rate from the MPD file sent by the DASH proxy server to send to the DASH proxy server after the vertical handover is completed. The MPD file is obtained after the DASH proxy server updates according to the code rate determined by the DASH proxy server, and receives the DASH service data sent by the DASH proxy server according to the received code rate.

 As shown in FIG. 16, the first DASH proxy server in the embodiment of the present invention includes:

 a determining module 161, configured to determine a code rate corresponding to the user equipment that performs vertical switching when performing DASH service data transmission;

 The sending module 162 is configured to send DASH service data to the user equipment according to the determined code rate.

 Preferably, the determining module 161 is further configured to:

 After receiving the handover complete indication message of the user equipment, determining a code rate corresponding to the user equipment that performs vertical handover when performing DASH service data transmission.

 Preferably, the handover completion indication message is carried by a Hypertext Transfer Protocol HTTP message. Preferably, the determining module 161 is specifically configured to:

 Determining, according to the bandwidth of the user equipment in the switched network, a code rate of DASH service data that needs to be sent to the user equipment.

 Preferably, the sending module 162 is specifically configured to:

Transmitting the information of the DASH service data according to the received request of the user equipment, and the Determining a code rate, and transmitting the DASH service data to the user equipment.

 Preferably, the information requesting to transmit the DASH service data is carried by an HTTP message. Preferably, the sending module 162 is specifically configured to:

 After determining that the code rate requested by the user equipment is different from the code rate determined by the DASH proxy server, sending the DASH service data to the user equipment according to the determined code rate.

 Preferably, the determining module 161 is further configured to:

 After determining that the code rate requested by the user equipment is the same as the code rate determined by the DASH proxy server, the DASH service data is sent to the user equipment according to the code rate requested by the user equipment.

 Preferably, the determining module 161 is further configured to:

 Sending, by the user equipment, a message requesting the MPD file to the DASH server, and transmitting a response message of the requested MPD file returned by the DASH server to the user equipment, according to the user equipment performing the vertical switching; The code rate requested by the user equipment sends DASH service data to the UE.

 As shown in FIG. 17, the first user equipment of the embodiment of the present invention includes:

 The receiving module 171 is configured to receive DASH service data of the DASH proxy server, and the processing module 172 is configured to: when receiving the vertical switch, control the receiving module 171 to stop receiving the DASH service data of the DASH proxy server; and after the vertical handover is completed, control receiving The module 171 continues to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server.

 Preferably, the processing module 172 is further configured to:

 After the vertical handover is completed, the control receiving module 171 continues to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server, and sends a handover complete indication message to the DASH proxy server.

 Preferably, the handover completion indication message is carried by an HTTP message.

 Preferably, the processing module 172 is further configured to:

After the vertical handover is completed, the control receiving module 171 continues to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server, to the The DASH proxy server sends information requesting to transmit DASH service data.

 Preferably, the processing module 172 is further configured to:

 The information requesting transmission of the DASH service data is determined according to the following manner: Determining the processing manner of the completed transmission portion in the fragment that has not completed the transmission when performing the vertical handover, and determining the information requesting to transmit the DASH service data according to the determined processing manner.

 Preferably, the processing module 172 is specifically configured to:

 Determining whether the amount of data of the portion of the fragment that has completed the transmission is greater than a threshold; if so, retaining the portion of the fragment that has completed the transmission; otherwise, deleting the portion of the fragment that has completed the transmission.

 As shown in FIG. 18, a second DASH proxy server according to an embodiment of the present invention includes:

 a determining module 181, configured to determine a code rate corresponding to the user equipment that performs vertical switching when performing DASH service data transmission;

 The sending module 182 is configured to update a code rate in the MPD file according to the determined code rate, and return the updated MPD file to the user equipment; according to the code rate selected by the user equipment from the MPD file, The user equipment sends DASH service data.

 Preferably, the determining module 181 is further configured to:

 After receiving the handover complete indication message of the user equipment, determine the code rate of the DASH service data that needs to be sent to the user equipment.

 Preferably, the handover completion indication message is carried by a Hypertext Transfer Protocol HTTP message. Preferably, the determining module 181 is specifically configured to:

 The code rate of the DASH service data that needs to be sent to the user equipment is determined according to the bandwidth of the user equipment in the switched network.

 Preferably, the sending module 182 is specifically configured to:

 The code rate in the MPD file is updated, wherein the code rate in the updated MPD file is not greater than the determined code rate.

 Preferably, the sending module 182 is further configured to:

Before determining the code rate of the DASH service data that needs to be sent to the user equipment, sending the received message of the user equipment requesting the MPD file to the DASH server, and sending the DASH service The response message of the requested MPD file returned by the device is sent to the user equipment; and the DASH service data is sent to the UE according to the code rate requested by the user equipment.

 As shown in FIG. 19, the second user equipment in this embodiment of the present invention includes:

 The receiving module 191 is configured to receive DASH service data of the DASH proxy server, and the processing module is configured to: when receiving the vertical switch, control the receiving module 191 to stop receiving the DASH service data of the DASH proxy server, and after the vertical handover is completed, from the Selecting a code rate from the MPD file sent by the DASH proxy server to the DASH proxy server, where the MPD file is obtained after the DASH proxy server is updated according to the code rate determined by the DASH proxy server; and controlling the receiving module 191 continues to receive DASH service data sent by the DASH proxy server according to the received code rate.

 Preferably, the processing module 192 is further configured to:

 After the vertical handover is completed, a handover completion indication message is sent to the DASH proxy server before selecting a code rate from the MPD file sent by the DASH proxy server to be sent to the DASH proxy service.

 Preferably, the handover completion indication message is carried by an HTTP message.

 Preferably, the processing module 192 is further configured to:

 After the vertical handover is completed, before receiving the DASH service data sent by the DASH proxy server according to the received code rate, the DASH proxy server is sent a message requesting to transmit the DASH service data.

 Preferably, the processing module 192 is further configured to:

 The information requesting transmission of the DASH service data is determined according to the following manner: Determining the processing manner of the completed transmission portion in the fragment that has not completed the transmission when performing the vertical handover, and determining the information requesting to transmit the DASH service data according to the determined processing manner.

 Preferably, the processing module 192 is specifically configured to:

 Determining whether the amount of data of the portion of the fragment that has completed the transmission is greater than a threshold; if so, retaining the portion of the fragment that has completed the transmission; otherwise, deleting the portion of the fragment that has completed the transmission.

As shown in FIG. 20, the third DASH proxy server in the embodiment of the present invention includes: The processor 2001 is configured to determine a code rate corresponding to the user equipment that performs vertical handover when performing DASH service data transmission;

 The transmitter 2002 is configured to send DASH service data to the user equipment according to the determined code rate.

 Preferably, the processor 2001 is further configured to:

 After receiving the handover complete indication message of the user equipment, determining a code rate corresponding to the user equipment that performs vertical handover when performing DASH service data transmission.

 Preferably, the handover completion indication message is carried by a Hypertext Transfer Protocol HTTP message. Preferably, the processor 2001 is specifically configured to:

 Determining, according to the bandwidth of the user equipment in the switched network, a code rate of DASH service data that needs to be sent to the user equipment.

 Preferably, the transmitter 2002 is specifically configured to:

 Transmitting the DASH service data information and the determined code rate according to the received request of the user equipment, and transmitting the DASH service data to the user equipment.

 Preferably, the information requesting to transmit the DASH service data is carried by an HTTP message. Preferably, the transmitter 2002 is specifically configured to:

 After determining that the code rate requested by the user equipment is different from the code rate determined by the DASH proxy server, sending the DASH service data to the user equipment according to the determined code rate.

 Preferably, the processor 2001 is further configured to:

 After determining that the code rate requested by the user equipment is the same as the code rate determined by the DASH proxy server, the DASH service data is sent to the user equipment according to the code rate requested by the user equipment.

 Preferably, the processor 2001 is further configured to:

 Sending, by the user equipment, a message requesting the MPD file to the DASH server, and transmitting a response message of the requested MPD file returned by the DASH server to the user equipment, according to the user equipment performing the vertical switching; The code rate requested by the user equipment sends DASH service data to the UE.

As shown in FIG. 21, the third user equipment of the embodiment of the present invention includes: The receiver 2101 is configured to receive DASH service data of the DASH proxy server, and the processor 2102 is configured to: when receiving the vertical switch, control the receiver 2101 to stop receiving the DASH service data of the DASH proxy server; and after the vertical handover is completed, control receiving The device 2101 continues to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server.

 Preferably, the processor 2102 is further configured to:

 After the vertical handover is completed, the control receiver 2101 continues to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server, and sends a handover complete indication message to the DASH proxy server.

 Preferably, the handover completion indication message is carried by an HTTP message.

 Preferably, the processor 2102 is further configured to:

 After the vertical handover is completed, the control receiver 2101 continues to receive the DASH proxy server to send the information requesting the transmission of the DASH service data to the DASH proxy server before receiving the DASH service data sent according to the code rate determined by the DASH proxy server.

 Preferably, the processor 2102 is further configured to:

 The information requesting transmission of the DASH service data is determined according to the following manner: Determining the processing manner of the completed transmission portion in the fragment that has not completed the transmission when performing the vertical handover, and determining the information requesting to transmit the DASH service data according to the determined processing manner.

 Preferably, the processor 2102 is specifically configured to:

 Determining whether the amount of data of the portion of the fragment that has completed the transmission is greater than a threshold; if so, retaining the portion of the fragment that has completed the transmission; otherwise, deleting the portion of the fragment that has completed the transmission.

 As shown in FIG. 22, a fourth DASH proxy server according to an embodiment of the present invention includes:

 The processor 2201 is configured to determine a code rate corresponding to the user equipment that performs vertical switching when performing DASH service data transmission;

a transmitter 2202, configured to update a code rate in the MPD file according to the determined code rate, and return the updated MPD file to the user equipment; according to the code rate selected by the user equipment from the MPD file, The user equipment sends DASH service data. Preferably, the processor 2201 is further configured to:

 After receiving the handover complete indication message of the user equipment, determine the code rate of the DASH service data that needs to be sent to the user equipment.

 Preferably, the handover completion indication message is carried by a Hypertext Transfer Protocol HTTP message. Preferably, the processor 2201 is specifically configured to:

 The code rate of the DASH service data that needs to be sent to the user equipment is determined according to the bandwidth of the user equipment in the switched network.

 Preferably, the transmitter 2202 is specifically configured to:

 The code rate in the MPD file is updated, wherein the code rate in the updated MPD file is not greater than the determined code rate.

 Preferably, the transmitter 2202 is further configured to:

 Before determining the code rate of the DASH service data that needs to be sent to the user equipment, sending the received message of the user equipment requesting the MPD file to the DASH server, and sending the response message of the requesting MPD file returned by the DASH server to the Describe the user equipment; and send DASH service data to the UE according to the code rate requested by the user equipment.

 As shown in FIG. 23, the fourth user equipment of the embodiment of the present invention includes:

 The receiver 2301 is configured to receive DASH service data of the DASH proxy server.

 The processor 2302 is configured to: when the vertical handover is performed, control the receiver 2301 to stop receiving the DASH service data of the DASH proxy server; and after the vertical handover is completed, select a code rate from the MPD file sent by the DASH proxy server to send to the The DASH proxy server, wherein the MPD file is obtained after the DASH proxy server is updated according to a code rate determined by the DASH proxy server; and the control receiver 2301 continues to receive the DASH proxy server according to the received code rate. The DASH service data sent.

 Preferably, the processor is further configured to:

After the vertical handover is completed, a handover completion indication message is sent to the DASH proxy server before selecting a code rate from the MPD file sent by the DASH proxy server to be sent to the DASH proxy service. Preferably, the handover completion indication message is carried by an HTTP message.

 Preferably, the processor 2302 is further configured to:

 After the vertical handover is completed, before receiving the DASH service data sent by the DASH proxy server according to the received code rate, the DASH proxy server is sent a message requesting to transmit the DASH service data.

 Preferably, the processor 2302 is further configured to:

 The information requesting transmission of the DASH service data is determined according to the following manner: Determining the processing manner of the completed transmission portion in the fragment that has not completed the transmission when performing the vertical handover, and determining the information requesting to transmit the DASH service data according to the determined processing manner.

 Preferably, the processor 2302 is specifically configured to:

 Determining whether the amount of data of the portion of the fragment that has completed the transmission is greater than a threshold; if so, retaining the portion of the fragment that has completed the transmission; otherwise, deleting the portion of the fragment that has completed the transmission.

 Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can be embodied in the form of one or more computer program products embodied on a computer-usable storage medium (including but not limited to disk storage, CD-ROM, optical storage, etc.) in which computer usable program code is embodied.

 The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowcharts and/or block diagrams, and combinations of flow and/or blocks in the flowcharts and/or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the computer readable memory is stored in the computer readable memory. The instructions in the production result include an article of manufacture of an instruction device that implements the functions specified in a block or blocks of a flow or a flow and/or a block diagram of the flowchart.

 These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

 Although the preferred embodiment of the invention has been described, it will be apparent to those skilled in the < Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and modifications The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Rights request

1. A method of transmitting business data, characterized in that the method includes:

The dynamic adaptive hypertext transfer protocol streaming DASH proxy server determines the bit rate corresponding to the user equipment that performs vertical switching when transmitting DASH business data;

The DASH proxy server sends DASH service data to the user equipment according to the determined code rate.

2. The method according to claim 1, characterized in that, before the DASH proxy server determines the code rate corresponding to the user equipment that performs vertical switching when transmitting DASH service data, it also includes:

The DASH proxy server receives the handover completion indication message of the user equipment.

3. The method of claim 2, wherein the switching completion indication message is carried through a Hypertext Transfer Protocol (HTTP) message.

4. The method according to any one of claims 1 to 3, characterized in that the DASH proxy server determines the code rate corresponding to the user equipment that performs vertical switching when transmitting DASH service data, including:

The DASH proxy server determines the code rate of the DASH service data that needs to be sent to the user equipment according to the bandwidth of the user equipment in the network after switching.

5. The method according to any one of claims 1 to 4, characterized in that the DASH proxy server sends DASH service data to the user equipment according to the determined code rate, including:

The DASH proxy server transmits the DASH service data information and the determined code rate according to the received request from the user equipment, and sends the DASH service data to the user equipment.

6. The method of claim 5, wherein the information requesting transmission of the DASH service data is carried through an HTTP message.

7. The method according to any one of claims 1 to 4, characterized in that the DASH proxy server sends DASH service data to the user equipment according to the determined code rate, including: After determining that the code rate requested by the user equipment is different from the code rate determined by the DASH proxy server, the DASH proxy server sends the DASH service data to the user equipment according to the determined code rate.

8. The method of claim 7, wherein the method further includes:

After determining that the code rate requested by the user equipment is the same as the code rate determined by the DASH proxy server, the DASH proxy server sends DASH service data to the user equipment according to the code rate requested by the user equipment.

9. The method according to any one of claims 1 to 8, characterized in that the method further includes:

Before the user equipment performs vertical switching, the DASH proxy server sends the received message requesting the MPD file from the user equipment to the DASH server, and sends the response message requesting the MPD file returned by the DASH server to the DASH server. The user equipment described above;

The DASH proxy server sends DASH service data to the UE according to the code rate requested by the user equipment.

10. A method of transmitting business data, characterized in that the method includes:

When the user equipment performs vertical handover, it stops receiving DASH service data from the DASH proxy server;

After the vertical handover is completed, the user equipment continues to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server.

11. The method of claim 10, wherein after the vertical handover is completed, the user equipment continues to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server. include:

The user equipment sends a handover completion indication message to the DASH proxy server.

12. The method of claim 11, wherein the switching completion indication message is carried through an HTTP message.

13. The method according to any one of claims 10 to 12, characterized in that, after the vertical handover is completed, the user equipment continues to receive the DASH proxy server according to the DASH proxy service. Before sending the DASH service data at the code rate determined by the processor, it also includes:

The user equipment sends information requesting transmission of DASH service data to the DASH proxy server.

14. The method of claim 13, wherein the user equipment determines the information requesting transmission of DASH service data according to the following method:

The user equipment determines a processing method for the completed transmission part of the fragments that have not been completed during vertical handover, and determines information requesting transmission of DASH service data based on the determined processing method.

15. The method of claim 14, wherein the user equipment determines a method for processing the untransmitted DASH service data, including:

The user equipment determines whether the data amount of the transmitted part in the fragment is greater than a threshold;

If so, retain the completed transmission part of the fragment; otherwise, delete the completed transmission part of the fragment.

16. A method of transmitting business data, characterized in that the method includes:

The DASH proxy server determines the bit rate corresponding to the user equipment that performs vertical switching when transmitting DASH service data;

The DASH proxy server updates the code rate in the MPD file according to the determined code rate, and returns the updated MPD file to the user device;

The DASH proxy server sends DASH service data to the user equipment according to the code rate selected by the user equipment from the MPD file.

17. The method of claim 16, wherein before the DASH proxy server determines the code rate of the DASH service data that needs to be sent to the user equipment, it further includes:

The DASH proxy server receives the handover completion indication message of the user equipment.

18. The method of claim 17, wherein the switching completion indication message is carried through an HTTP message.

19. The method according to any one of claims 16 to 18, characterized in that, the DASH agent The server determines the code rate of the DASH service data that needs to be sent to the user equipment, including: the DASH proxy server determines the code rate of the DASH service data that needs to be sent to the user equipment based on the bandwidth of the user equipment in the network after switching.

20. The method according to any one of claims 16 to 19, characterized in that the DASH proxy server updates the code rate in the MPD file according to the determined code rate, including:

The DASH proxy server updates the code rate in the MPD file, where the code rate in the updated MPD file is not greater than the determined code rate.

21. The method according to any one of claims 16 to 20, characterized in that, before the DASH proxy server determines the code rate of the DASH service data that needs to be sent to the user equipment, it further includes: the DASH proxy server will receive Send the message requesting the MPD file from the user equipment to the DASH server, and send the response message requesting the MPD file returned by the DASH server to the user equipment;

The DASH proxy server sends DASH service data to the UE according to the code rate requested by the user equipment.

22. A method for transmitting business data, characterized in that the method includes:

When the user equipment performs vertical handover, it stops receiving DASH service data from the DASH proxy server;

After the vertical handover is completed, the user equipment selects a code rate from the MPD file sent by the DASH proxy server and sends it to the DASH proxy server, where the MPD file is the code generated by the DASH proxy server according to the DASH proxy server. Obtained after the determined code rate is updated; The user equipment receives the DASH service data sent by the DASH proxy server according to the received code rate.

23. The method of claim 22, wherein after the vertical handover is completed, the user equipment selects a code rate from the MPD file sent by the DASH proxy server and before sending it to the DASH proxy service, include:

The user equipment sends a handover completion indication message to the DASH proxy server.

24. The method of claim 23, wherein the handover completion indication message communicates Contained via HTTP message.

25. The method according to any one of claims 22 to 24, wherein after the vertical handover is completed, the user equipment continues to receive the DASH service data sent by the DASH proxy server according to the received code rate. include:

The user equipment sends information requesting transmission of DASH service data to the DASH proxy server.

26. The method of claim 25, wherein the user equipment determines the information requesting transmission of DASH service data according to the following method:

The user equipment determines a processing method for the completed transmission part of the fragments that have not been completed during vertical handover, and determines information requesting transmission of DASH service data based on the determined processing method.

27. The method of claim 26, wherein the user equipment determines a method for processing the uncompleted transmission of DASH service data, including:

The user equipment determines whether the data amount of the transmitted part in the fragment is greater than a threshold;

If so, retain the completed transmission part of the fragment; otherwise, delete the completed transmission part of the fragment.

28. A dynamic adaptive Hypertext Transfer Protocol streaming media DASH proxy server for transmitting business data, characterized in that the DASH proxy server includes:

Determination module, used to determine the code rate corresponding to the user equipment that performs vertical switching when transmitting DASH service data;

A sending module, configured to send DASH service data to the user equipment according to the determined code rate.

29. The DASH proxy server according to claim 28, characterized in that the determination module is also used to:

After receiving the handover completion indication message of the user equipment, the code rate corresponding to the user equipment that performs vertical handover during DASH service data transmission is determined.

30. The DASH proxy server according to claim 29, wherein the switching completion indication message is carried through a Hypertext Transfer Protocol HTTP message.

31. The DASH proxy server according to any one of claims 28 to 30, characterized in that the determination module is specifically used for:

According to the bandwidth of the user equipment in the network after switching, the code rate of the DASH service data that needs to be sent to the user equipment is determined.

32. The DASH proxy server according to any one of claims 28 to 31, characterized in that the sending module is specifically used for:

According to the received request from the user equipment to transmit the information of the DASH service data and the determined code rate, the DASH service data is sent to the user equipment.

33. The DASH proxy server according to claim 32, wherein the information requesting transmission of the DASH service data is carried through an HTTP message.

34. The DASH proxy server according to any one of claims 28 to 31, characterized in that the sending module is specifically used for:

After it is determined that the code rate requested by the user equipment is different from the code rate determined by the DASH proxy server, the DASH service data is sent to the user equipment according to the determined code rate.

35. The DASH proxy server according to claim 34, characterized in that the determination module is also used to:

After it is determined that the code rate requested by the user equipment is the same as the code rate determined by the DASH proxy server, DASH service data is sent to the user equipment according to the code rate requested by the user equipment.

36. The DASH proxy server according to any one of claims 28 to 35, characterized in that the determination module is also used to:

Before the user equipment performs vertical switching, send the received message requesting the MPD file from the user equipment to the DASH server, and send the response message requesting the MPD file returned by the DASH server to the user equipment; according to The code rate requested by the user equipment is used to send DASH service data to the UE.

37. A user equipment for transmitting service data, characterized in that the user equipment includes: The receiving module is used to receive the DASH business data of the DASH proxy server; the processing module is used to control the receiving module to stop receiving the DASH business data of the DASH proxy server when vertical switching is performed, and after the vertical switching is completed, control the The receiving module continues to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server.

38. The user equipment according to claim 37, characterized in that, the processing module is further configured to: after the vertical handover is completed, control the receiving module to continue to receive the data determined by the DASH proxy server according to the DASH proxy server. Before sending the DASH service data at the code rate, a switching completion indication message is sent to the DASH proxy server.

39. The user equipment according to claim 38, characterized in that the handover completion indication message is carried through an HTTP message.

40. The user equipment according to any one of claims 37 to 39, characterized in that the processing module is also used to:

After the vertical switching is completed, the receiving module is controlled to send a message requesting transmission of DASH service data to the DASH proxy server before continuing to receive the DASH service data sent by the DASH proxy server according to the code rate determined by the DASH proxy server.

41. The user equipment according to claim 40, wherein the processing module is further configured to: determine the information requesting transmission of DASH service data according to the following method: determine the fragments that have not completed transmission during vertical handover. The processing method of the transmission part has been completed, and based on the determined processing method, the information requesting the transmission of DASH business data is determined.

42. The user equipment according to claim 41, characterized in that the processing module is specifically used to:

Determine whether the data amount of the completed transmission part in the fragment is greater than the threshold; if so, retain the completed transmission part of the fragment; otherwise, delete the completed transmission part of the fragment.

43. A DASH proxy server for transmitting business data, characterized in that the DASH proxy server includes:

Determination module, used to determine users who perform vertical switching during DASH service data transmission The code rate corresponding to the device;

A sending module, configured to update the code rate in the MPD file according to the determined code rate, and return the updated MPD file to the user equipment; according to the code rate selected by the user equipment from the MPD file, to the The user equipment sends DASH service data.

44. The DASH proxy server according to claim 43, characterized in that the determination module is also used to:

After receiving the handover completion indication message of the user equipment, the code rate of the DASH service data that needs to be sent to the user equipment is determined.

45. The DASH proxy server according to claim 44, wherein the switching completion indication message is carried through an HTTP message.

46. The DASH proxy server according to any one of claims 43 to 45, characterized in that the determination module is specifically used for:

According to the bandwidth of the user equipment in the network after switching, the code rate of the DASH service data that needs to be sent to the user equipment is determined.

47. The DASH proxy server according to any one of claims 43 to 45, characterized in that the sending module is specifically used for:

Update the code rate in the MPD file, where the code rate in the updated MPD file is not greater than the determined code rate.

48. The DASH proxy server according to any one of claims 43 to 47, characterized in that the sending module is also used to:

Before determining the code rate of the DASH service data that needs to be sent to the user equipment, send the received message requesting the MPD file from the user equipment to the DASH server, and send the response message requesting the MPD file returned by the DASH server to the DASH server. The user equipment: sends DASH service data to the UE according to the code rate requested by the user equipment.

49. A user equipment for transmitting service data, characterized in that the user equipment includes: a receiving module for receiving DASH service data from a DASH proxy server;

Processing module, used to control the receiving module to stop receiving DASH when performing vertical switching The DASH service data of the proxy server, after the vertical switching is completed, selects a code rate from the MPD file sent by the DASH proxy server and sends it to the DASH proxy server, where the MPD file is the DASH proxy server according to the Obtained after updating the code rate determined by the DASH proxy server; and controlling the receiving module to continue receiving the DASH service data sent by the DASH proxy server according to the received code rate.

50. The user equipment according to claim 49, wherein the processing module is further configured to: after the vertical switching is completed, select a code rate from the MPD file sent by the DASH proxy server and send it to the DASH Before providing the proxy service, a switching completion indication message is sent to the DASH proxy server.

51. The user equipment according to claim 50, characterized in that the handover completion indication message is carried through an HTTP message.

52. The user equipment according to any one of claims 49 to 51, characterized in that the processing module is also used to:

After the vertical switching is completed, before continuing to receive the DASH service data sent by the DASH proxy server according to the received code rate, a message requesting transmission of the DASH service data is sent to the DASH proxy server.

53. The user equipment according to claim 52, characterized in that the processing module is further configured to: determine information requesting transmission of DASH service data according to the following method: determine the fragments that have not completed transmission during vertical handover. The processing method of the transmission part has been completed, and based on the determined processing method, the information requesting the transmission of DASH business data is determined.

54. The user equipment according to claim 53, characterized in that the processing module is specifically used to:

Determine whether the data amount of the completed transmission part in the fragment is greater than the threshold; if so, retain the completed transmission part of the fragment; otherwise, delete the completed transmission part of the fragment.

55. A system for transmitting business data, characterized in that the system includes:

Dynamic adaptive hypertext transfer protocol streaming media DASH proxy server is used to determine the code rate corresponding to the user equipment that performs vertical switching during DASH service data transmission, and determines according to the Send DASH service data to the user equipment at a certain code rate;

The user equipment is configured to stop receiving DASH service data from the DASH proxy server when vertical switching is performed, and after the vertical switching is completed, continue to receive the DASH proxy server according to the

DASH service data sent at the code rate determined by the DASH proxy server.

56. A system for transmitting business data, characterized in that the system includes:

The DASH proxy server is used to determine the code rate corresponding to the user equipment that performs vertical switching during DASH service data transmission, update the code rate in the MPD file based on the determined code rate, and return the updated MPD file to the user equipment , send DASH service data to the user equipment according to the code rate selected by the user equipment from the MPD file;

The user equipment is configured to stop receiving DASH service data from the DASH proxy server when vertical switching is performed, and after the vertical switching is completed, select a code rate from the MPD file sent by the DASH proxy server and send it to the DASH proxy server, The MPD file is obtained by updating the DASH proxy server according to the code rate determined by the DASH proxy server, and receives the DASH service data sent by the DASH proxy server according to the received code rate.