WO2008106890A1 - Procédé, système et appareil d'utilisation d'un tampon multimédia - Google Patents

Procédé, système et appareil d'utilisation d'un tampon multimédia Download PDF

Info

Publication number
WO2008106890A1
WO2008106890A1 PCT/CN2008/070408 CN2008070408W WO2008106890A1 WO 2008106890 A1 WO2008106890 A1 WO 2008106890A1 CN 2008070408 W CN2008070408 W CN 2008070408W WO 2008106890 A1 WO2008106890 A1 WO 2008106890A1
Authority
WO
WIPO (PCT)
Prior art keywords
media
media buffer
content
buffer
information
Prior art date
Application number
PCT/CN2008/070408
Other languages
English (en)
Chinese (zh)
Inventor
Xiangyang Wu
Jun Yan
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008106890A1 publication Critical patent/WO2008106890A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/722—Admission control; Resource allocation using reservation actions during connection setup at the destination endpoint, e.g. reservation of terminal resources or buffer space
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/801—Real time traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/806—Broadcast or multicast traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/824—Applicable to portable or mobile terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]

Definitions

  • the present invention relates to the field of network communications, and in particular, to a method, system, and two media caching devices for using a media cache. Background of the invention
  • FIG. 1 is a structure of the existing media buffer.
  • the IP network 102 transparently connects the client 101 and the server 103.
  • the media buffer 104 can cache part or all of the content of the server 103. The physical location may be close to the client.
  • the media buffer The 104 can provide the stored data to the client 101, thereby improving the average access time and reducing the network transmission delay. At the same time, the bandwidth consumption of the core transmission network can be effectively saved.
  • the client 101 initially configures the information of the media buffer 104, and explicitly configures the address of the media buffer 104 on the client. 101.
  • the service request is first sent to the media buffer 104 according to the configuration information. If the media buffer 104 has the cached media content, the media buffer 104 directly provides the content to the client 101. If the media buffer 104 does not have corresponding content, the media buffer 104 can request content from the server 103 and then forward the content to the client 101 for use.
  • the second method is: the client 101 directly requests the media content from the server 103, and the server 103 directs the client 101 to the media by using a HTTP/RTSP redirection mechanism according to a policy such as load sharing and nearby content providing.
  • Buffer 104 enabling customers
  • the terminal 101 first requests the media buffer 104 to provide content. If the media buffer 104 has cached media content, the media buffer 104 directly provides content to the client 101; if the media buffer 104 does not have corresponding content, the media buffer 104 The content can be requested from the server 103 and then forwarded to the client 101 for use.
  • the current two methods treat the IP network between the client and the server as transparent.
  • the media buffer can be introduced to the client.
  • next generation network is taken as an example, and its structure is shown in Figure 2.
  • the user equipment 201 is configured to initiate a service request to the application server 202 by using an IMS core network 203;
  • the application server 202 is configured to receive the service request sent by the user equipment 201 through the IMS core network 203, and provide various service logic control functions to the IMS core network 203.
  • the IMS core network 203 is configured to control functions such as user registration, session control, routing, service triggering, and media resource control, and send a bearer control request to a Resource and Admission Control Subsystem (RACS) 204;
  • RATS Resource and Admission Control Subsystem
  • the RACS 204 is configured to complete control of the bearer network according to the requirements of the IMS core network 203.
  • the transport function entity 205 is configured to provide access, aggregation, and core network border gateway functions of the user equipment 201 under the bearer control of the RACS 204.
  • the IMS core network 203 is introduced between the user equipment 201 and the application server 202 providing various service logic control functions as the session control layer of the NGN network
  • the RACS 205 is also introduced as the bearer control layer of the NGN network, thereby realizing the separation of control and bearer.
  • the user equipment or the application server cannot directly obtain the address of the network entity used to carry the transmission, that is, the network between the user equipment and the application server cannot be regarded as transparent, and the media buffer is directly obtained.
  • the address, the media buffer is introduced into the NGN network, so with the current method, the media cache cannot be used.
  • an embodiment of the present invention provides a method for using a media cache, which can implement media caching in an IMS network environment.
  • Embodiments of the present invention provide a method for using a media cache, which is capable of implementing media caching in an IMS network environment.
  • Embodiments of the present invention provide a method for using a media cache, which is capable of implementing media caching in an IMS network environment.
  • Embodiments of the present invention provide a system using a media cache, which is capable of implementing media caching in an IMS network environment.
  • Embodiments of the present invention provide a system using a media cache, which is capable of implementing media caching in an IMS network environment.
  • Embodiments of the present invention provide a system using a media cache, which is capable of implementing media caching in an IMS network environment.
  • Embodiments of the present invention provide a media caching apparatus capable of implementing media caching in an IMS network environment.
  • Embodiments of the present invention provide a media caching apparatus capable of implementing media caching in an IMS network environment.
  • a method of using a media cache comprising:
  • the IP multimedia subsystem acquires the media buffer information, and adds the media buffer information to the service request, where the service request is a service request sent by the client that is routed or forwarded by the IMS to the application server;
  • the media server requests the media buffer to provide content according to the media buffer information in the service request.
  • a method of using a media cache comprising:
  • the media server obtains the media buffer information by using the media buffer information registration entity, where the media buffer information is the media buffer registered to the media buffer information registration entity.
  • the media server requests the media buffer to provide content according to the media buffer information.
  • a method of using a media cache comprising:
  • the IMS obtains the media buffer address information, and replaces the client address and the media server address in the message with the media buffer address information, where the message is an interaction message between the client and the application server that is routed or forwarded by the IMS;
  • the client uses the media buffer as a proxy between the client and the media server to request the media buffer to provide content.
  • a system using a media cache comprising: an IMS, a media server and a media buffer;
  • the IMS obtains the media buffer information, and adds the media buffer information to the service request, where the service request is a service request sent by the client that is routed or forwarded by the IMS to the application server;
  • the media server requests the media buffer to provide content according to the media buffer information in the service request.
  • a system using a media cache comprising: a media buffer information registration entity, Media server and media buffer;
  • the media buffer is configured to register self information into the media buffer information registration entity
  • the media server is configured to obtain media buffer information by using the media buffer information registration entity, and request the media buffer to provide content according to the media buffer information.
  • a system for using a media cache comprising: an IMS and a media buffer; the IMS, acquiring media buffer address information, replacing the client address or the media server address in the message with the media buffer address information,
  • the message is an interaction message between the client and the application server that is routed or forwarded by the IMS;
  • the media buffer is configured to provide the requested content to the client as a proxy between the client and the media server according to the content request sent by the client.
  • a media cache device comprising: a cache module, an address output module, and an execution module;
  • the cache module is configured to store media content
  • the address output module is configured to output information of a package cache address when the RACS query or the media cache device is running;
  • the execution module is configured to: when the cache module does not have the requested content, forward the content of the MRF input to the client, and when the cache module caches the requested content, read the cached request content in the cache module, and the requested content Enter it into the client.
  • a media buffering device comprising: a cache module, an address allocation module, and an execution module;
  • the cache module is configured to store media content
  • the address allocation module is configured to allocate a media buffer network side and an access side address when the RACS requests the media buffer device to act as an RTSP protocol proxy, and input information including a media buffer address network side and an access side address.
  • the execution module is configured to send a content request to the MRF when the cache module does not have the requested content, and forward the request content of the MRF input to the client, and when the content of the request is cached in the cache module, the cache in the cache module is read. Request content, input the requested content to the client.
  • the three methods and systems for using the media cache and the two media caching devices are provided by the embodiment of the present invention, and the information including the media buffer address is obtained by using the IMS, and the information exchanges between the client and the IMS, the MRF, and the IMS is performed.
  • the media buffer is introduced into the IMS network environment, so that the media cache is used in the IMS network environment, so that the media providing mechanism in the IMS network environment can be optimized, the bandwidth resource of the core transmission network can be saved, the media providing time can be saved, and the user can be effectively improved.
  • the business experience in turn, can better provide multimedia services. BRIEF DESCRIPTION OF THE DRAWINGS
  • 1 is a structural schematic diagram of an existing media buffer
  • FIG. 2 is a schematic diagram of an NGN structure based on an IMS network environment
  • FIG. 3 is a schematic structural diagram of a system according to a first embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a service request process according to a first embodiment of the present invention.
  • FIG. 5 is a flow chart showing the execution of the first process in the first embodiment of the present invention
  • Figure 6 is a flow chart showing the execution of the second process in the first embodiment of the present invention
  • Figure 7 is a first embodiment of the present invention
  • FIG. 8 is a schematic flowchart of a second embodiment of the present invention
  • FIG. 9 is a schematic structural diagram of a system according to a third embodiment of the present invention.
  • FIG. 10 is a schematic flow chart of a third embodiment of the present invention.
  • FIG. 11 is a schematic flow chart of a fourth embodiment of the present invention.
  • FIG. 12 is a schematic diagram of a first structure of a media cache device according to an embodiment of the present invention
  • FIG. 13 is a schematic diagram of a second structure of a media cache device according to an embodiment of the present invention. Mode for carrying out the invention
  • the method for using the media cache is: setting a media buffer; the client sends a service request to the media server MRF through the IP multimedia subsystem IMS; the MRF obtains the information including the media buffer address, and The client sends a service request response carrying the MRF address; the client sends a content request to the MRF according to the received MRF address; after receiving the content request sent by the client, the MRF provides the request to the client by using the obtained media buffer address.
  • the method for using the media cache is: setting a media buffer; the client sends a service request to the media server MRF through the IP multimedia subsystem IMS; the MRF obtains the information including the media buffer address, and The client sends a service request response carrying the MRF address; the client sends a content request to the MRF according to the received MRF address; after receiving the content request sent by the client, the MRF provides the request to the client by using the obtained media buffer address.
  • Content is: setting a media buffer; the client sends a service request to the media server M
  • FIG. 3 is a schematic structural diagram of a system according to a first embodiment of the present invention.
  • the system in this embodiment includes a UE (User Equipment) 310, an MRF 320 that provides media resources, and a network edge node 330 that sets the media buffer 331.
  • UE User Equipment
  • MRF Mobile Radio Access
  • a media buffer 331 is disposed in the network edge node 330;
  • the UE 310 sends a service request to the MRF 320 through the IMS, and sends a content request to the MRF 320 according to the MRF320 service request response carrying the MRF address sent by the IMS; for example, performing a playback control operation such as fast forward, fast rewind, play, pause, etc., where the interface 13 It is an interface between the MRF 320 and the UE 310, which can use RTSP or a protocol with similar functions.
  • the MRF320 obtains the information including the media buffer address, and sends a service request response carrying the MRF address to the UE 310 through the IMS, and provides the requested content by using the obtained information including the media buffer address according to the content request sent by the UE 310. UE310.
  • the system of this embodiment further includes a first control module 351 in the RACS 350 and a second control module 341 in the IMS 340;
  • the second control module in the IMS in this embodiment is a proxy call session control function.
  • P-CSCF Proxy-Call Session Control Function
  • the request sent by the P-CSCF 341 in the received IMS queries the media buffer 331 through an interface preset with the media buffer 331 to obtain information including the media buffer address, and sends a service request carrying the information to the P-CSCF 341. , forwarded by the P-CSCF341 to the MRF320.
  • the first control module 351 in the RACS corresponds to the network edge node 330 set by the media buffer 331.
  • the first control module 351 in the shell's RACS is an SPDF, and is queried through the 12 interface.
  • the media buffer 331 obtains the information including the media buffer address, and sends the obtained information to the IMS 340.
  • the 12 interface is an interface between the RACS 350 and the media buffer 331, and the interface can use a protocol such as H.248.
  • the media buffer 331 is a new function entity. Accordingly, the interface 11 between the MRF 320 and the media buffer 331, the interface 12 between the RACS 350 and the media buffer 331 and the interface 13 between the MRF 320 and the UE 310 are new interfaces.
  • the media buffer 331 is disposed in the network edge node 330, and the network edge node 330 can be embodied as an entity such as GGSN, DSLAM, BGF, BRAS.
  • the following uses the structure shown in FIG. 3 as an example to specifically describe the flow of using the media cache.
  • This process can be broken down into business request processes and content flow processes.
  • the content process can be divided into two situations:
  • the first process if the necessary content is not cached in the media buffer, the first process is executed.
  • the second case If the necessary content is cached in the media buffer, the second process is executed.
  • a UE sends a service request to an AS via an IMS.
  • the P-CSCF passes.
  • the RACS queries the cache support capability of the network edge node.
  • the information such as the media cache address is added to the service request.
  • the service request is further forwarded to the AS through the IMS, and the AS makes a content request to the MRF according to the user request.
  • the MRF is requested to provide media content to the user; the MRF queries the media buffer for the cache information of the media content requested by the user according to the obtained description information of the cache support capability.
  • the process specifically includes the following steps:
  • Step 401 The UE sends a service request to the IMS.
  • the information of the content identifier CID is carried in the service request sent by the UE to the IMS.
  • Step 402 The P-CSCF in the IMS queries the RACS for the cache support capability information of the network edge node.
  • the P-CSCF queries the RACS for the cache support capability information of the network edge node.
  • Step 403 The RACS responds to the cache support capability query of the network edge node sent by the P-CSCF.
  • the RACS will describe the capability information cacheCap of the network edge node supporting the cache to be returned to the P-CSCF in the IMS. If the network edge node supports the caching capability, the information also includes the address information of the media buffer.
  • Step 404 The IMS forwards the service request to the AS.
  • the IMS further forwards the service request to the AS, where the content identifier CID and the cache support capability information cacheCap are carried.
  • Step 405 The AS forwards the service request to the MRF.
  • the AS transmits the service request of the user to the MRF, and requests the media resource from the MRF, where the AS carries the content identifier CID and the cache support capability information cacheCap.
  • Step 406 The MRF checks the cache support capability information of the network edge node carried in the request.
  • the MRF check request carries the network edge node cache support capability information. If the cache support capability is not available, the MRF provides the service according to the non-cache condition, and the subsequent process is performed, which is not detailed here; If the capability is met, step 407 is performed.
  • Step 407 The MRF queries the media buffer for the cache information of the requested content.
  • the MRF determines that the network edge node has the media buffer support capability. If the MRF confirms that the network edge node has the media buffer support capability, the MRF locates the entity where the media buffer is located, that is, the network edge that is combined with the media buffer, according to the content identifier CID and the cache support capability cacheCap description information. After the node locates the entity, the MRF queries the media buffer for the cached information of the requested content, including cache information such as cache and cache amount.
  • Step 408 The media buffer queries the cache information of the MRF response content.
  • Step 409 The MRF selects to perform a subsequent process according to the media buffer response result.
  • the MRF performs the subsequent process of the first process according to the result of the media buffer response, if there is no cache content on the media buffer; otherwise, the subsequent process of the second process is performed.
  • FIG. 5 is a schematic flowchart of performing the first process in the first embodiment of the present invention.
  • the MRF may negotiate with the UE to determine the media sending parameter according to a general procedure.
  • the MRF provides the content to the UE.
  • the MRF sends media transmission parameters, such as the content identifier CID, the encoding mode, the sending address/port, and the encapsulation mode to the media buffer.
  • the media buffer determines whether the media stream is in accordance with the local policy.
  • the content of the media stream is saved through the media buffer to optimize the subsequent business process; the aging of the media buffer content is determined by the local policy, and no dynamic notification to the MRF is required.
  • the first process specifically includes the following steps:
  • Step 501 The MRF sends the media transmission parameter and the content description parameter to the media buffer.
  • the MRF sends a media transmission parameter media_trans_param and a content description parameter contentInfo to the media buffer, where media-trans-param It is a description of the media transmission parameters of the media content sent by the MRF, such as the MRF IP address mrf_ip, the port number mrf_port, etc.; the contentInfo is a description of the media content, such as the content identifier CID, the packet length packetLen, etc.; Save this information, according to these two pieces of information, the media buffer can receive the specific media according to the local strategy.
  • the RTP payload type parameter RTP payloadType may indicate The encoding format information, so the encoding format parameter codec does not need to be explicitly passed; for the message-level media buffer, the matching parameter needs to increase the RTP encapsulation length to prevent confusion caused by caching different package length contents.
  • Step 502 The MRF returns the media transmission parameter and the control point address information to the AS.
  • the MRF returns the media transmission parameter media_trans_param and the control point address parameter MRF_cache_control to the AS, where the MRF_cache_control is used to designate the media control point as the MRF, that is, the media control address information provided therein is the address information of the MRF.
  • Step 503 The AS forwards the media transmission parameter and the control point address information to the P-CSCF.
  • Step 504 The P-CSCF forwards the media transmission parameter and the control point address information to the UE.
  • step 503 and step 504 mainly complete the AS, and the media transmission address information and control point information returned by the MRF are carried in the response and returned to the UE, where the response is
  • P-CSCF is passed to the UE
  • Step 505 The UE sends a play request to the MRF.
  • the UE sends a play request to the media play control point MRF returned by the AS, where the request carries the content identifier CID and the content time range range information;
  • Step 506 The MRF sends the content to the media buffer.
  • the MRF sends content according to the playback request of the UE, and the content passes through the media buffer.
  • Step 507 The media buffer caches the content according to the local policy.
  • the media buffer caches the content according to the local policy. If the content needs to be cached, the media stream is matched and cached according to the information obtained in step 501. For different services, the media buffer performs matching and content caching. The parameters required are also different. For example, for a live television (LTV) service in an Internet Protocol (IPTV) service, the media buffer can match a message quintuple parameter according to a time range to obtain a specific content identifier. The content contained in the CID, therefore, the parameters required for the LTV-type business are shown in Table 2:
  • the MRF can indicate the broadcast time of a certain content in an absolute time range, such as 2006-11-07 15:23:40-2006- 11 -07 16:23:40, supplemented by the initial sum during the time period. End time stamp and serial number;
  • the media buffer uses the quintuple to match the corresponding real-time service flow, and then detects the RTP time stamp and serial number, and divides the content according to the description of the MRF; if the real-time program does not need to press the content For the division, if only the program of a certain time period needs to be recorded, the MRF can only inform the media buffer of the quintuple information of the specific channel, and the media buffer can record the absolute time range synchronously when recording the content.
  • VOD video on demand
  • a quintuple only corresponds to one content identifier CID; therefore, the media buffer can only obtain the content included in the specific content identifier CID according to the packet quintuple parameter matching, that is, the MRF only informs the media buffer quintuple information.
  • the MRF only informs the media buffer quintuple information.
  • Step 508 The media buffer continues to forward the content to the UE.
  • step 508 since the media buffer may cache the content, when the request for the same content is received again, the MRF may use the content cached in the media buffer, as follows: A description of the second process.
  • FIG. 6 is a schematic flowchart of executing the second process in the first embodiment of the present invention.
  • the MRF interacts with the media buffer to determine media transmission parameters; the parameters are carried to the UE through a media negotiation process of a Session Description Protocol (SDP); wherein the MRF is specified as a media playback control point, and the media buffer provides a point for the media; After the control command is played, the media buffer is notified to send the corresponding content to the UE.
  • SDP Session Description Protocol
  • the media buffer requests the missing content from the MRF and sends the content to the UE as needed, which specifically includes the following steps:
  • Step 601 The MRF sends the media transmission parameter and the content description parameter to the media buffer.
  • the MRF sends the media_trans_param and contentInfo parameters to the media buffer, where the media_trans_param describes the media transmission parameters of the media content sent by the MRF, such as the MRF IP address mrf_ip, the port number mrf_port, and the like; the contentInfo performs the media content.
  • Description such as content identifier CID, packet length packetLen, etc.
  • Step 602 The media buffer returns a media transmission parameter to the MRF.
  • the Bay ij MRF obtains the media transmission parameter media_trans_param from the media buffer, and describes the media transmission parameter of the media content sent by the media buffer, for example, The media buffer cache IP address, port number cache_port and other information.
  • the MRF returns the media transmission parameter and the control point address information to the AS.
  • the MRF returns media_trans_param and MRF_media buffer-control parameter information to the AS, where the media_trans-param media transmission parameter includes information such as the IP address cache_ip of the media buffer, the port number cache_port, and the like.
  • the cache serves as a point of supply for media content.
  • Step 604 The AS forwards the media transmission parameter and the control point address information to the P-CSCF.
  • Step 605 The P-CSCF forwards the media transmission parameter and the control point address information to the UE.
  • Step 606 The UE sends a play request to the MRF.
  • Step 607 The MRF sends the request information to the media buffer.
  • the MRF converts the playback control request into request information between the MRF and the media buffer, requesting playback of the specified content.
  • Step 608 The media buffer sends a request to the MRF response.
  • steps 609 to 611 are optional steps, after the media buffer determines that the requested partial content is cached, and before the media buffer provides the content to the client, only part of the content is cached in the media buffer. A special treatment of time.
  • Step 609 The media buffer requests the missing content from the MRF in advance according to the local policy.
  • the media buffer according to the processing and prediction of the content requested by the user, the media buffer requests the missing content in advance according to the local policy.
  • Step 610 The MRF sends the request content.
  • the MRF sends the content requested by the media buffer to the media buffer.
  • Step 611 The media buffer buffers the media content for subsequent transmission to the user.
  • Step 612 The media buffer sends the media content to the UE.
  • the media buffer sends the media content to the UE under the MRF request, and the content may be cached by the media buffer, or may be obtained by the media buffer after the MRF instant request; the media buffer is sending the media content.
  • the RTP message sequence number is required, The metrics are consistent.
  • the parameters used to match the media stream are not in the media buffer in the second process.
  • the parameters used to match the media stream are the same. Specifically, when locating the content of the cached media stream on the media buffer, the required parameters are as shown in Table 3:
  • the content identifier CID, the encoding format codec, and the playing time range can generally be determined during playback control, and the information can be directly matched in the above table; for the packet-level media buffer In other words, considering the possibility of the difference in RTP encapsulation length, the media buffer can use this parameter as a condition for splicing each segment of the content.
  • the above content identification CID can be a live TV festival.
  • the destination channel information, the specific content is determined by the playing time range; or may be specific content indicating a specific channel.
  • the information including the media buffer address is obtained by querying the media buffer.
  • the information including the media buffer address may be obtained according to the registration information of the media buffer.
  • the media buffer performs a specific media buffer information registration entity. Registering/registering, and an interface exists between the media buffer information registration entity and the MRF, through which the MRF queries the media buffer information registration entity to obtain media buffer information, and accesses network information according to the user IP address.
  • the media buffer registers with the media buffer information entity, such as X-function (XDPF, X Device Profile Function) registration, that is, the system further includes xDPF, and the xDPF can be preset through the media buffer.
  • the interface receives the registration information including the media buffer address sent by the media buffer, and sends the information to the MRF when the MRF queries through the preset interface with the MRF.
  • the process of implementing the service request in the media cache by this method is as shown in FIG. 7. Specific steps are as follows:
  • Step 701 The media buffer registers and status notification to the xDPF.
  • the media buffer registers with the xDPF and performs status notification.
  • the media buffer registers with the media buffer; during the registration process, the media buffer needs to provide the xDPF with the device identifier of the device running by itself, including the media buffer address, the media buffer space size, the media buffer space usage, the load status, and the like;
  • the media buffer needs to notify the xDPF of the running status.
  • the xDPF can also actively query the running status of the media buffer after it is registered.
  • Step 702 The UE sends a service request to the AS through the IMS.
  • the UE sends a service request to the AS, where the request carries the content identifier CID, and is transmitted to the AS through the P-CSCF; the P-CSCF in the IMS further adds the user location information loc in the service request; Step 703: The AS forwards the service request to the MRF.
  • the AS transmits the service request of the user to the MRF, and requests the MRF to provide the media resource, where the user location information loc and the content identifier CID are carried.
  • Step 704 The MRF queries the media buffer information.
  • the MRF queries the xDPF according to the user location information loc to determine whether there is a media buffer in the UE access network or the network edge node close to the UE; if the MRF does not query the appropriate media buffer, the MRF uses no media.
  • the business process in the case of a cache is a user service and will not be described here. If yes, step 705 is performed;
  • Step 705 The xDPF returns the media buffer information.
  • Step 706 The MRF queries the media buffer for the cache information of the specified content.
  • the MRF queries the media buffer for the cache information of the specified content according to the media buffer information returned by the xDPF, including, for example, whether the cache, the cache amount, and the like.
  • Step 707 The media buffer responds to the specified content cache query.
  • Step 708 The MRF selects to perform the subsequent process according to the query result.
  • the subsequent process is performed according to the first process shown in FIG. 5; otherwise, the second process shown in FIG. 6 is performed.
  • This embodiment provides an example of a time-shifted television on demand (TsTV) application for implementing LTV content in a multicast manner.
  • the media buffer buffers the RTP packets in the multicast packet, that is, the cache.
  • the content includes the RTP header.
  • a media buffer is set on a network edge node digital user access multiplexer (DSLAM), and the MRF is used as a playback control point.
  • DSLAM network edge node digital user access multiplexer
  • the system structure diagram of this embodiment is similar to that of FIG. 3, except that the network edge node that is combined with the media buffer is a DSLAM, and the network for verifying is added.
  • Body UPSF here is not - repeat.
  • FIG. 8 is a schematic flowchart of a second embodiment of the present invention.
  • media buffer content is provided in a multicast manner from a DSLAM to a UE, whether the media buffer has content, and whether a media buffer is used by the MRF.
  • the MRF locates the media buffer, at which time the media buffer can have content/no content/or partial content; if there is no media buffer, the MRF can provide content by itself; if there is a media buffer, However, the media buffer has no content, the MRF can provide content by itself, or instruct the media buffer to perform a buffer operation; if there is part or complete content on the media buffer, the media buffer is used to provide content; since the media buffer is located on the DSLAM, The multicast mode provides content.
  • the media buffer provides the content, the media source address does not need to be allocated, and the original multicast address and port are used; when the content is incomplete, the media buffer requests the MRF delivery at an appropriate timing.
  • Step 801 The MRF sends a multicast service flow to the media buffer.
  • the user selects to watch a specific program, and the MRF sends a multicast service flow according to the user selection, and the multicast stream passes through the media buffer in the DSLAM;
  • Step 802 The media buffer selects a cached multicast stream according to a local policy.
  • the media buffer in the DSLAM caches the multicast stream according to a local policy, or may not cache.
  • Step 803 The media buffer forwards the multicast stream to the UE.
  • the multicast stream arrives at the UE on the terminal side, and is decoded and displayed by the UE.
  • Step 804 The UE sends a service request to the AS through the IMS.
  • the service request carries a channel identifier ChID, and requests for play control.
  • the P-CSCF in the IMS may request the RACS to provide media buffer capability support information, thereby supporting the DSLAM media buffer.
  • the capability information cacheCap is added in the business request.
  • Step 805 The AS verifies the service request to the UPSF.
  • the request is routed or forwarded to the AS for processing, and the AS may need to verify the request to the UPSF.
  • Step 806 The AS sends a media resource request to the MRF.
  • the AS sends a media resource request to the MRF to request to provide the media content.
  • Step 807 The MRF queries whether there is specified content on the media buffer.
  • the MRF determines the media buffer according to the information such as the cacheCap; the MRF queries the media buffer for the specified content; if no content is specified, the subsequent process may be performed without using the media buffer process, which is not detailed herein; , go to step 808.
  • Step 808 The media buffer responds to the MRF response with a specified content.
  • a query for specifying content to the MRF response returns a response result to the MRF query, including a description of the specified content.
  • Step 809 The MRF returns the media transmission parameter and the control point address information to the AS.
  • the MRF allocates a play control parameter to make the play control point itself
  • the media transmission parameter provided by the MRF is the address parameter of the media buffer; the above parameters are carried in the response and returned to the AS.
  • Step 810 The AS forwards the media transmission parameter and the control point address information to the UE.
  • the AS forwards the media transmission parameter and the control point address information to the IMS.
  • Step 811 The UE leaves the corresponding program multicast group.
  • the UE after receiving the response information, uses the IGMP leave message to leave the corresponding program multicast group.
  • Step 812 The UE sends a play control command to the MRF.
  • the UE sends a play control command to the play control address specified in the response.
  • the UE sends a play control command to the MRF.
  • Step 813 The MRF sends a play request to the media buffer.
  • the MRF converts the received playback control command into an interface message between the MRF and the media buffer, and requests the media buffer to play the specified content.
  • Steps 814 through 816 are optional steps that occur only under certain conditions:
  • Step 814 The media buffer pre-requests the missing content to the MRF according to the local policy.
  • the media buffer requests the remaining content from the MRF according to the cache policy.
  • Step 815 The MRF sends the request content.
  • the content requested by the media buffer is sent by the MRF to the media buffer.
  • Step 816 The media buffer caches the media content for subsequent transmission to the user.
  • Step 817 The media buffer sends the content to the UE in a multicast manner.
  • Step 818 The UE decodes and displays the received content.
  • the embodiment implements the TsTV service in the multicast+unicast mode, where the multicast is used to play the LTV content, and the unicast is used to send the content to the user.
  • the content of the VCR control is not limited to
  • the RTP packet in the multicast packet is buffered in the media buffer, that is, the cache content includes the RTP header.
  • the playback control signaling When the user performs VCR operation, the playback control signaling will directly or indirectly affect the media buffer, and its control instruction indicates the point in time at which the initial playback is required; MRF and media buffer Interaction, the media buffer is responsible for allocating the address and port for providing unicast content; the parameters that need to be carried for the playback control signaling and the parameters required to match the content on the media buffer have been described above, and are no longer here. Narration.
  • the media buffer After the user obtains the unicast address and port, the media buffer encapsulates the content requested by the user and sends it to the user according to the assigned address and port. For missing content, the media buffer is based on a local policy/algorithm, requesting content from the MRF in unicast and storing the requested content locally.
  • the BGF provides content to the UE in a unicast manner.
  • the UE needs to be aware of the change in the source address of the media content, and thus can perform unicast address/port renegotiation. Therefore, in this case, the process of using the media buffer should increase the media buffer allocation unicast before step 808.
  • the step of transmitting parameters for media content delivery to the UE, and step 817 should send the media content to the UE in a unicast manner for the media buffer.
  • the embodiment can be regarded as the unicast playback stage in the TsTV service: the content of the media buffer is other users.
  • the VOD media source address is the address and port of the media buffer, and the media buffer unicasts and encapsulates the cached content to the UE.
  • the media buffer performs content to the MRF according to the local caching algorithm/policy.
  • the request is, and the requested content is re-encapsulated, and is uniformly processed and sent to the UE.
  • the flow of using the media buffer in this embodiment does not include steps 801 - 803, and the other steps are the same as the above-described process of providing content to the UE in a unicast manner.
  • FIG. 9 is a block diagram showing the structure of a system according to a third embodiment of the present invention. Included in this embodiment as A client of the User Equipment (UE) 910, an MRF 920, and a media buffer 931 disposed in the network edge node 930.
  • UE User Equipment
  • the main difference between this embodiment and FIG. 3 is that the MRF 920 provides the access side address of the media buffer 931 to the UE 910 through the IMS, and the interface between the media server execution module 921 and the media buffer 931 in the MRF 920.
  • the interface 15 between the first control module 951 and the media buffer 931 in the RACS 950 and the interface 16 between the media buffer 931 and the UE 910 have new functional descriptions. The functional characteristics of these three interfaces are specifically described below.
  • the interface 14 is an interface between the MRF 920 and the media buffer 931.
  • the media buffer 931 forwards the content request of the UE 910 to the MRF 920 through the interface 14, such as a media play control request.
  • the media buffer 931 can also request the MRF 920 to provide content through the interface 14 for the content. Cache.
  • the interface 15 is an interface between the first control module 951 and the media buffer 931 in the RACS 950.
  • the first control module 951 requests the use of the media buffer 931 through the interface 15; the interface 15 can use a similar protocol such as H.248.
  • the interface 16 is an interface between the UE 910 and the media buffer 931.
  • the UE 910 sends a content request to the media buffer 931 by using the interface 16, for example, a playback control operation such as fast forward, fast rewind, play, pause, etc., and the interface 16 can use RTSP or have A protocol similar to the function.
  • FIG. 9 is a schematic flowchart of a third embodiment of the present invention.
  • a client sends a service request to an MRF through an IMS.
  • the IMS requests the RACS to obtain a media buffer address, and the RACS passes the advance.
  • the set interface requests the media buffer as the RTSP protocol proxy, and the media buffer allocates the network side and the access side address according to the RTSP protocol proxy request, and sends the allocated media buffer network side and the access side address to the IMS through the RACS, IMS.
  • the client address information in the service request is replaced by the media side address information of the media buffer, and sent to the MRF, and the MRF parses the received service request, and obtains the network including the media buffer. Side address information.
  • the MRF sends a service request response carrying its own address information to the IMS; the IMS replaces the address information of the MRF in the service request response with the media buffer access side address information, and replaces the media cache in the service request response with the saved client address information.
  • the network side address information of the device is sent to the client.
  • the embodiment specifically includes the following steps:
  • Step 1001 The UE sends a service request to the IMS.
  • the service identifier sent by the UE to the IMS carries the content identifier CID client RTSP&RTP parameter c_RTSP&RTP_param information for requesting specific media content.
  • Step 1002 The P-CSCF in the IMS requests to use the media buffer through the RACS.
  • the P-CSCF in the IMS requests to use the media buffer through the RACS, and the RACS supports the media buffer control capability and the network edge node has the cache.
  • the RACS requests the media buffer to serve the UE as an RTSP Proxy.
  • Step 1003 The media buffer responds to the P-CSCF by using a media buffer request through the RACS.
  • the media buffer when the media buffer responds to the RACS, it carries the network-side RTSP&RTP parameter net_RTSp&RTP_param allocated by the media buffer and the access side RTSP&RTP parameter a_RTSP&RTP_Param.
  • the RACS returns a response to the P-CSCF, the two parameters are also carried.
  • Step 1004 The IMS forwards the service request to the AS.
  • the P-CSCF sends a service request to the AS, where c_RTSP&RTP_param is replaced by the network side RTSP&RTP parameter net_RTSP&RTP_param; in addition, the P-CSCF adds the UE location information loc information in the request;
  • Step 1005 The AS forwards the service request to the MRF.
  • the AS transmits the service request of the user to the MRF, and requests the media from the MRF.
  • the physical resource which carries the UE location information Loc, the content identifier CID, and the network side RTSP&RTP parameter net_RTSP&RTP_paramtext
  • Step 1006 The MRF sends a service request response to the AS.
  • the MRF responds to the service request with the MRF, and carries the information such as the RTSP&RTP parameter mrf_RTSP&RTP_param of the MRF.
  • Step 1007 The AS forwards the service request response to the P-CSCF.
  • the AS forwards the MRF service request response to the UE through the P-CSCF, and carries the information such as the content identifier CID and the MRF RTSP&RTP parameter mrf_RTSP&RTP_param.
  • Step 1008 The P-CSCF sends the RTSP&RTP parameter information of the MRF to the media buffer through the RACS.
  • the P-CSCF sends parameters such as mrf_RTSP&RTP_param to the RACS, and the RACS passes the parameter to the media buffer entity for later use;
  • Step 1009 The P-CSCF sends a service request response to the UE.
  • the P-CSCF sends a service request response to the UE, where the RTSP&RTP parameter mrf_RTSP&RTP_Param of the MRF in the received response is replaced by the access side RTSP&RTP parameter a_RTSP&RTP_Param allocated by the media buffer; in addition, for the client to be normal
  • the inverse replacement of step 1004 is also required, that is, the network side RTSP & RTP parameter net_RTSP & RTP_param is replaced by c_RTSP &RTP_param; the response sent to the UE carries information such as the content identifier CID and the access side RTSP & RTP parameters a_RTSP & RTP_Param.
  • the RTSP&RTP parameters obtained by the UE are related parameters of the media buffer, and the user RTSP&RTP parameters obtained by the MRF are directed to the media buffer, thereby introducing the media buffer into the service transmission path.
  • Step 1010 The UE sends a media play request to the media buffer.
  • the UE sends a media play request to the media buffer, where the information carries the content identifier CID and the content time range range.
  • steps 1011 - 1012 are performed.
  • Step 1011 The media buffer sends an RTSP protocol proxy request to the MRF.
  • the media buffer if there is no content requested by the user on the media buffer, the media buffer sends an RTSP protocol proxy request to the MRF to request to send the content.
  • Step 1012 The MRF sends the requested content to the media buffer.
  • the MRF sends the requested content to the media buffer, and the media buffer locally caches the media content as needed.
  • Step 1013 The media buffer sends the specified content to the user.
  • the media buffer sends the specified streaming media content to the user, and the streaming media may be locally cached, or may be requested from the MRF immediately.
  • an application example of playing TsTV for LTV content in a multicast manner is provided.
  • the RTP message in the multicast packet is buffered in the media buffer, that is, the cache content includes the RTP header.
  • a media cache is set in the DSLAM, and the MRF is a playback control point.
  • the system structure is similar to that of Figure 9. The only difference is that the network edge node that is connected with the media buffer is BGF, which is not described here.
  • FIG. 11 is a schematic flowchart of a fourth embodiment of the present invention. In this embodiment, the following steps are specifically included:
  • Step 1101 The MRF sends a multicast service flow to the media buffer.
  • the user selects to watch a specific program, and the MRF broadcasts a multicast service stream, and the multicast stream passes through the media buffer in the BGF.
  • Step 1102 The media buffer selects a cached multicast stream according to a local policy.
  • the media buffer caches the multicast stream according to a local policy, or may not cache.
  • Step 1103 The media buffer forwards the multicast stream to the UE.
  • the multicast stream arrives at the UE on the terminal side, and is decoded and displayed by the UE.
  • the playback control command is converted into a service request, and the following steps are performed:
  • Step 1104 The UE sends a service request to the IMS.
  • the service request carries the channel identifier ChID and the UE location information loc to request playback control.
  • the request further carries the RTP&RTSP parameter of the terminal side, etc.;
  • the P-CSCF in the IMS requests the RACS to perform media buffer support, and requests the media buffer entity to provide RTP&RTSP parameters.
  • Step 1106 The RACS acquires transmission parameters used by the network side.
  • the RACS interacts with the BGF to determine the transmission parameters used by the BGF on the network side, that is, the network side address N_Addr and the network side port N_port information, and the terminal side RTP&RTSP parameters are transmitted to the BGF;
  • Step 1107 The RACS sends a response to the P-CSCF request using the media buffer.
  • the RACS responds to the P-CSCF in the IMS, and carries the acquired transmission parameters used by the network side, that is, the network side address N_Addr and the network side port N_port;
  • Step 1108 The P-CSCF forwards the service request to the MRF through the AS.
  • the P-CSCF carries the channel identifier ChID, the network side address N_Addr, and the network side port N_port information in the service request and sends the information to the AS, that is, the terminal side in the original service request is replaced by the network side parameter.
  • RTP & RTSP parameters; AS in turn carries these parameters to request MRF to provide media content.
  • Step 1109 The MRF saves the network side transmission parameters.
  • the MRF saves the network side address N_Addr and the network side port N_port information. Used for subsequent delivery of content to the media buffer;
  • Step 1110 The MRF sends a service request response to the AS.
  • the MRF allocates transmission parameters for transmitting the media content, including the unicast address U_addr and the unicast port U_port information, and returns the parameter to the AS.
  • Step 1111 The AS forwards the service request response to the IMS.
  • the AS returns the unicast address U_addr and the unicast port U_port information to step 1112:
  • the P-CSCF sends a request to use the media buffer to the RACS.
  • the P-CSCF in the IMS requests the RACS to perform media buffer support, and requests the media buffer entity to provide RTP and RTSP parameters.
  • Step 1113 The RACS obtains the transmission parameters used by the access side.
  • the RACS interacts with the BGF to determine the transmission parameters that the BGF will use on the access side, that is, the access side address a_Addr and the access side port a_port, and the unicast address assigned by the MRF 11_&(1( ⁇ and unicast)
  • the port U_port information is transmitted to the BGF for use by the BGF to accept media content.
  • Step 1114 The RACS sends a response to the P-CSCF using the media buffer.
  • the RACS response to the P-CSCF in the IMS includes an access side address _ (1 ( ⁇ and access side port a_port and other parameters.
  • Step 1115 The P-CSCF sends a service request response to the UE.
  • the P-CSCF replaces parameters such as the unicast address U_addr and the unicast port U_port in the AS response with parameters such as the access side address a_Addr and the access port a_port; in addition, the inverse transform described in step 1108 is performed. , that is, the network side RTP&RTSP parameter in the service response is replaced by the client RTP & RTSP parameter, and the result is sent to the UE.
  • Step 1116 The UE leaves the corresponding program multicast group.
  • the UE after receiving the response information, uses the IGMP leave message to leave the corresponding Program multicast group.
  • Step 1117 The UE sends a play control command to the BGF.
  • the UE sends a play control command to the play control address of the BGF.
  • Step 1118 to Step - Step 1120 is an optional step that occurs only under certain conditions:
  • Step 1119 The MRF sends the request content.
  • the content requested by the media buffer is sent by the MRF to the media buffer.
  • Step 1120 The media buffer caches the media content for subsequent transmission to the user.
  • Step 1121 The media buffer sends the content to the UE in a unicast manner.
  • Step 1122 The UE decodes and displays the received content.
  • the core network used may be a core network such as a streaming media core network or a PSDN emulation subsystem in addition to the IMS.
  • the media buffer can be combined with the DSLAM, and can also be associated with a Border Gateway Function (BGF), a GPRS Gateway Support Node (GGSN), and a Resource Control Executive Function Entity (RCEF, Resource). Control Enforcement Function ) and other network entities are combined to implement media caching.
  • BGF Border Gateway Function
  • GGSN GPRS Gateway Support Node
  • RCEF Resource Control Executive Function Entity
  • FIG. 12 is a schematic diagram of a first structure of a media cache device according to an embodiment of the present invention.
  • the device includes a query module 1201, an execution module 1202, a cache module 1203, and an address output module 1204.
  • a cache module 1203, configured to store media content
  • the query module 1201 responds to the query of whether the MRF caches the content requested by the client, and queries whether the content requested by the client is cached in the cache module 1203, and the results of the query are respectively Input to execution module 1202 and MRF;
  • the address output module 1204 outputs information including a media cache address when the RACS query or the media cache device is running;
  • the execution module 1202 forwards the content of the MRF input to the client when there is no requested content in the cache module 1203 according to the query result input by the query module 1201, and reads the cache module 1203 when the cached module 1203 caches the requested content.
  • the cached request content, the requested content is input to the client.
  • FIG. 13 is a schematic diagram of a second structure of a media cache device according to an embodiment of the present invention.
  • the device includes a determining module 1301, a cache module 1303, an executing module 1302, and an address assigning module 1304.
  • a cache module 1303, configured to store media content
  • the determining module 1301 determines whether the content of the request is cached in the cache module 1303 according to the content request sent by the client, and inputs the result of the determination to the executing module 1302;
  • the address allocation module 1304 when the RACS requests the media buffer device to act as the RTSP protocol agent, allocates the media buffer network side and the access side address, and inputs information including the media buffer address network side and the access side address into the RACS;
  • the execution module 1302 sends a content request to the MRF when the cache module 1303 does not have the requested content, and forwards the requested content of the MRF input to the client, and caches the requested content in the cache module 1303. At this time, the requested content cached in the cache module 1303 is read, and the requested content is input to the client.
  • the three methods and systems for using the media cache and the two media caching devices are provided by the embodiment of the present invention, and the information including the media buffer address is obtained by using the IMS, and the information exchanges between the client and the IMS, the MRF, and the IMS is performed.
  • the media providing mechanism in the environment can save the bandwidth resources of the core transmission network, save the media providing time, effectively improve the user's business experience, and thus better provide multimedia services.

Abstract

L'invention concerne un procédé d'utilisation d'un tampon multimédia dans lequel un sous-système multimédia IP (IMS) obtient des informations de la mémoire tampon multimédia, ajoute les informations de la mémoire tampon multimédia à une demande de service, et la demande de service est envoyée à un serveur d'application via la route IMS ou le client recevant la transmission. Un serveur multimédia demande à la mémoire tampon multimédia de fournir un contenu en fonction des informations de la mémoire tampon multimédia de la demande de service. L'invention concerne également deux procédés et un système correspondant, ainsi que deux dispositifs tampons multimédia. Le tampon multimédia peut être mis en oeuvre dans un environnement de réseau IMS par application de l'invention.
PCT/CN2008/070408 2007-03-05 2008-03-04 Procédé, système et appareil d'utilisation d'un tampon multimédia WO2008106890A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710079411.4 2007-03-05
CN2007100794114A CN101262413B (zh) 2007-03-05 2007-03-05 实现媒体缓存的方法、系统和装置

Publications (1)

Publication Number Publication Date
WO2008106890A1 true WO2008106890A1 (fr) 2008-09-12

Family

ID=39737803

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070408 WO2008106890A1 (fr) 2007-03-05 2008-03-04 Procédé, système et appareil d'utilisation d'un tampon multimédia

Country Status (2)

Country Link
CN (1) CN101262413B (fr)
WO (1) WO2008106890A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103118049B (zh) * 2011-11-17 2018-02-16 广州中海电信有限公司 一种通过网络缓存下载文件的方法和系统
CN102625076A (zh) * 2012-04-06 2012-08-01 高剑平 一种基于流媒体的电视交互式视频应答方法及系统
CN103716343B (zh) * 2012-09-29 2016-11-09 重庆新媒农信科技有限公司 基于数据缓存同步的分布式业务请求处理方法及系统
CN103888487A (zh) * 2012-12-19 2014-06-25 中国电信股份有限公司 媒体流控制方法和系统
CN108370372B (zh) * 2016-02-22 2021-07-09 华为技术有限公司 一种数据包的传输方法、网络侧设备以及用户设备
EP3606005B1 (fr) * 2017-04-26 2022-04-13 Huawei Technologies Co., Ltd. Procédé de redirection, élément de réseau de plan de commande, élément de réseau de plan utilisateur d'agrégation, serveur de contenu et dispositif terminal

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1454426A (zh) * 2000-06-01 2003-11-05 奥罗卡斯特.Com公司 基于qos的内容分配网络
US20040107143A1 (en) * 2002-11-29 2004-06-03 Aki Niemi Method for authorizing indirect content download
CN1787476A (zh) * 2004-12-06 2006-06-14 北京三星通信技术研究有限公司 宽带实时多媒体业务集成服务系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1454426A (zh) * 2000-06-01 2003-11-05 奥罗卡斯特.Com公司 基于qos的内容分配网络
US20040107143A1 (en) * 2002-11-29 2004-06-03 Aki Niemi Method for authorizing indirect content download
CN1787476A (zh) * 2004-12-06 2006-06-14 北京三星通信技术研究有限公司 宽带实时多媒体业务集成服务系统

Also Published As

Publication number Publication date
CN101262413A (zh) 2008-09-10
CN101262413B (zh) 2011-01-05

Similar Documents

Publication Publication Date Title
US9118738B2 (en) Systems and methods for controlling access to a media stream
JP5612105B2 (ja) データ・サービスに対するスケーラブルなビデオ制御帯域幅の割り当て
US9485299B2 (en) Progressive download gateway
US9215483B2 (en) Policies for content downloading and content uploading
JP5442766B2 (ja) サービス・レイヤにより支援する、マルチメディア・ストリーム・アクセス配信の変更
US8307049B2 (en) Method and device for obtaining media description information of IPTV services
US9414124B2 (en) Audiovisual session switchover from a first access network to a second access network
RU2480936C2 (ru) Способ, устройство и система для распространения информации на основе ip-телевидения
US20150288530A1 (en) Methods for switching between a mbms download and an http-based delivery of dash formatted content over an ims network
KR101757771B1 (ko) 상호 계층 최적화를 이용한 멀티미디어 데이터 패킷을 송신하는 방법 및 장치
Thomas et al. Enhancing MPEG DASH performance via server and network assistance
US8228945B2 (en) Streaming communication system
KR20120138319A (ko) 멀티미디어 데이터 특징 정보를 이용하여 멀티미디어 서비스 데이터 패킷을 송신하는 방법 및 장치
TW201603546A (zh) 單一播放適應性位元率串流
WO2008037218A1 (fr) Procédé, système et serveur multimédia permettant une commutation rapide d'un canal de télévision sur internet (iptv)
US20110099595A1 (en) Method and a User Equipment for Reserving Bandwidth
KR20120028857A (ko) 적절한 서비스 레벨을 제공하는 방법 및 장치
WO2007093124A1 (fr) Procédé et système d'ordonnancement de ressources multimédia
WO2008106890A1 (fr) Procédé, système et appareil d'utilisation d'un tampon multimédia
WO2008110122A1 (fr) Procédé, système et entité tampon de commutation de chaînes de téléréseau
EP2448260B1 (fr) Procédé de téléchargement de contenu vers l'amont et entité de fonction de livraison de contenu
WO2011144176A1 (fr) Procédé, appareil et système adaptés pour contrôler une livraison de contenu d'un réseau de livraison de contenu
WO2009092248A1 (fr) Dispositif et système de distribution de contenu, procédé pour contenu à la demande et architecture de réseau
TW201204037A (en) Use of picture-in-picture stream for internet protocol television fast channel change
US8239909B2 (en) Method of securing resources in a video and audio streaming delivery system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08715144

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08715144

Country of ref document: EP

Kind code of ref document: A1