WO2009021464A1 - Method, device and system for realizing multicast service - Google Patents

Method, device and system for realizing multicast service Download PDF

Info

Publication number
WO2009021464A1
WO2009021464A1 PCT/CN2008/072006 CN2008072006W WO2009021464A1 WO 2009021464 A1 WO2009021464 A1 WO 2009021464A1 CN 2008072006 W CN2008072006 W CN 2008072006W WO 2009021464 A1 WO2009021464 A1 WO 2009021464A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
multicast address
address
bearer network
identifier
Prior art date
Application number
PCT/CN2008/072006
Other languages
English (en)
French (fr)
Inventor
Min Zha
Yong Huang
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.
Priority to EP08783997.3A priority Critical patent/EP2139158B1/en
Publication of WO2009021464A1 publication Critical patent/WO2009021464A1/zh
Priority to US12/704,579 priority patent/US8488603B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/16—Multipoint routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2521—Translation architectures other than single NAT servers
    • H04L61/2535—Multiple local networks, e.g. resolving potential IP address conflicts
    • 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

Definitions

  • the embodiments of the present invention relate to a multicast technology in the communication field, and in particular, to a method, an apparatus, and a system for implementing a multicast service. Background technique
  • IP Internet Protocol
  • the basic idea of IP is that the source host sends only one piece of data.
  • the destination address in this data is the multicast group address. All receivers in the multicast group are The same data copy can be received, and only the host (target host) in the multicast group can receive the data, and other hosts in the network cannot receive it.
  • the IP address space is divided into four categories: A, B, C, and D.
  • the class D address is reserved for use as a multicast address.
  • IPv4 IP protocol
  • all IP addresses from 224.0.0.0 to 239.255.255.255 belong to the class D address.
  • the address range of 224.0.0.0 to 224.0.0.255 is reserved, and the address range of 224.0.1.0 to 238.255.255.255 is used as the user multicast address, which is valid in the whole network.
  • the address range from 239.0.0.0 to 239.255.255.255 is the local management group. Broadcast address, valid only for a specific local range.
  • IPv4 multicast network except for some well-known and reserved multicast addresses, other addresses do not explicitly specify how to use them, so there is a danger of address conflicts.
  • IPTV Internet Protocol Television
  • the user equipment obtains the multicast address of the channel from the EPG (Electronic Program Guide) menu provided by the IPTV operator, and performs a multicast request according to the multicast address.
  • EPG Electronic Program Guide
  • the multicast addresses provided by different IPTV operators may be the same, and the multicast paths of most programs of an IPTV operator are the same, conflicts may occur.
  • each IPTV operator's channel can be assigned a different multicast address to solve.
  • the bearer network needs to maintain a large number of multicast paths, and the workload is very large.
  • the prior art provides a technology for uniformly managing a multicast address by a network provider.
  • the network provider allocates a multicast address to a channel of the IPTV operator, and the EPG menu is uniformly provided by the network provider to ensure multicast entering the bearer network.
  • the addresses do not conflict. This solution solves the problem that the multicast addresses caused by multiple IPTV operators sharing one bearer network may conflict to some extent.
  • the multicast address of the channel of the IPTV operator is allocated by the network provider, when the IPTV operator needs to connect with multiple bearer networks, the multicast address of the channel of the IPTV operator is difficult to be consistent; Multicast path.
  • the embodiments of the present invention provide a method, an apparatus, and a system for implementing a multicast service, so as to reduce the number of multicast paths that need to be maintained by the bearer network.
  • the embodiment of the invention provides a method for implementing a multicast service, including:
  • the ingress node converts the received multicast service data address from the original multicast address identifier into the bearer network internal multicast address identifier according to the mapping relationship information, and sends the outgoing address; the egress node according to the mapping relationship information And converting the received address of the multicast service data from the internal multicast address identifier of the bearer network to the original multicast address identifier, and sending the address.
  • the embodiment of the invention further provides a resource management system, where the system includes a multicast address
  • the management entity, the multicast address management entity includes:
  • the multicast address mapping module is configured to establish a mapping relationship between the original multicast address identifier of the multicast service data and the internal multicast address identifier of the bearer network.
  • the multicast address mapping relationship sending module is configured to send information indicating a mapping relationship between the original multicast address identifier and the internal multicast address identifier of the bearer network to the ingress node device and the egress node device of the multicast path.
  • the embodiment of the present invention further provides a data transmission device, including: an external interface module and an internal interface module, which are used for performing multicast service data interaction with devices externally and internally of the bearer network, and further includes:
  • the multicast address mapping relationship receiving module is configured to receive the multicast address mapping relationship information, where the mapping relationship information is mapping information between the original multicast address identifier of the multicast service data and the bearer address identifier of the bearer network;
  • a multicast address mapping module configured to convert, according to the mapping relationship information, an original multicast address identifier of the multicast service data into a bearer network internal address identifier, and send the multicast service data to the internal interface And converting the internal address identifier of the bearer network of the multicast service data into an original multicast address identifier, and sending the multicast service data to the external interface module.
  • the embodiment of the present invention further provides a multicast service implementation system, including a multicast address management entity, and at least two data transmission devices;
  • the multicast address management entity is configured to establish a mapping relationship between the original multicast address identifier of the multicast service data and the internal multicast address identifier of the bearer network, and send information indicating the mapping relationship to the multicast path entry And the data transmission device of the egress; the data transmission device located at the ingress of the multicast path, configured to convert the received original multicast address identifier of the multicast service data into a bearer network according to the mapping relationship information
  • the internal multicast address is identified and sent out;
  • the data transmission device located at the exit of the multicast path is configured to convert the internal multicast address identifier of the bearer network of the received multicast service data into the original group of the multicast service data according to the mapping relationship information. Broadcast the address ID and send it out.
  • the embodiment of the invention further provides a computer storable medium, which stores a read/write program Order, causes the computer to perform the following methods:
  • the ingress node converts the received multicast service data address from the original multicast address identifier into the bearer network internal multicast address identifier according to the mapping relationship information, and sends the outgoing address; the egress node according to the mapping relationship information And converting the received address of the multicast service data from the internal multicast address identifier of the bearer network to the original multicast address identifier, and sending the address.
  • the original multicast address identifier of the multicast service data is mapped to the multicast address identifier of the bearer network, and is sent to the ingress node and the egress node of the multicast path, so that the multicast service data is transmitted.
  • the multicast address identifier inside the bearer network is used when transmitting in the bearer network
  • the original multicast address identifier of the multicast service data is used when the bearer network is outside, so that the bearer network is used.
  • the internal multicast addresses do not conflict, and a reasonable address mapping relationship can be used to reduce the number of multicast paths that need to be maintained inside the bearer network.
  • FIG. 1 is a schematic diagram of a plurality of bearer networks shared by multiple IPTV operators in the prior art
  • FIG. 2 is a schematic flowchart of a multicast address control process according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a flow of a multicast service flow according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a multicast service signaling according to an embodiment of the present invention
  • FIG. 6 is a schematic structural diagram of a resource management system according to an embodiment of the present invention
  • FIG. 7 is a schematic structural diagram of a data transmission device according to an embodiment of the present invention.
  • the control and data flow of the UE and the IPTV provider are not used.
  • the network control and the bearer layer convert the control and the multicast address in the data stream.
  • the multicast address allocated by the IPTV provider is still used outside the multicast service bearer network, and the network control is used inside the multicast service bearer network.
  • the internal multicast address of the bearer network allocated by the bearer layer is used for multicast service transmission, so as to avoid conflicts between multicast addresses in the bearer network.
  • FIG. 2 A schematic diagram of a multicast address control process in the embodiment of the present invention is shown in FIG. 2.
  • the user equipment passes the AF (Application Function) to the multicast address information (such as the multicast address pair ⁇ 8>, where G is the multicast address) through the normal process of requesting the service.
  • S is the multicast source address
  • RACS Resource and Admission Control Subsystem
  • the RACS maps the multicast address pair to the multicast address pair ⁇ G, managed by the RACS. S,>, and the mapping relationship of the multicast address pair is sent to the ingress node and the egress node of the multicast path of the multicast service.
  • the specific steps include:
  • Step 201 The user equipment requests the multicast service by using high layer signaling.
  • Step 202 The service control layer obtains, according to the request, a corresponding multicast service address identifier pair ⁇ G, S>, where the multicast address pair is allocated by the IPTV operator.
  • the service control layer sends the multicast address pair ⁇ G, S> to the bearer control layer, and the bearer control layer controls the multicast path and resources.
  • Step 203 The RACS carrying the control layer establishes a multicast path for the multicast service, or adds the user equipment to the multicast path (if the multicast path of the multicast service already exists), and the multicast address provided by the IPTV operator Mapping ⁇ G, S> to the multicast address pair ⁇ G', S, > managed by the network provider, and sending the mapping relationship of the multicast address pair ⁇ 8> and ⁇ 0', 8'> to The ingress node and the egress node of the multicast path established by the multicast service.
  • the ingress and egress nodes of the multicast path are located at the edge of the multicast service bearer network.
  • the ingress node receives the multicast stream sent by the multicast source, and the multicast stream is routed to the egress node along the multicast path, and is sent by the egress node to the user equipment.
  • the control function of the RACS carrying the control layer mainly includes: implementing admission control based on the saved policy, accepting or rejecting the request for the multicast service. If accepting multicast from user equipment
  • the service request reserves resources for transmitting the multicast service data, establishes a multicast path for transmitting the multicast stream, and performs multicast address pair mapping.
  • Step 204 The bearer control layer responds to the service control layer with the setting completion information.
  • Step 205 The service control layer notifies the user equipment that the multicast service request is successful, and sends the multicast address pair ⁇ G, S> of the multicast service requested by the user equipment to the user equipment.
  • the user equipment further performs step 206, that is, sends a multicast join request according to the obtained multicast address pair ⁇ 8>.
  • the multicast address pair carried in the request is ⁇ G, S>.
  • the multicast address information can be identified by using only the multicast address G.
  • the embodiment of the present invention provides a mapping manner of several multicast addresses:
  • the multicast address G and the multicast source address S of ⁇ G, S> ⁇ can be mapped to the bearer network respectively.
  • the multicast address G of the commerce management and the multicast source address S, that is, ⁇ 8> are mapped to ⁇ G,, S,>;
  • the multicast address information provided by the IPTV operator is a multicast address pair ⁇ G,S>, the multicast address and multicast source address of ⁇ G,S> ⁇ can be mapped to the multicast address managed by the bearer network provider, that is, ⁇ *> is mapped to ⁇ G',* >;
  • the multicast address information provided by the IPTV operator is the multicast address ⁇ G>
  • the multicast address ⁇ G> is mapped to the multicast address ⁇ G,> managed by the bearer network provider, ie, ⁇ G >Map to ⁇ G'>;
  • the multicast address information provided by the IPTV operator is the multicast address ⁇ G>
  • the multicast address ⁇ G> is mapped to the multicast address G managed by the bearer network provider
  • the multicast service data is The multicast source address S, the multicast address G, and the multicast source address S' of the bearer network are allocated to the multicast address pair ⁇ G', S, > within the bearer network, that is, ⁇ G> is mapped to ⁇ G,,S,>.
  • Mapping the multicast address information provided by the IPTV operator to the multicast address information managed by the bearer network provider in the bearer network, establishing a multicast address mapping relationship, and delivering the multicast node to the ingress node and the egress node may be performed by using the user equipment to request the multicast service, or the multicast address mapping relationship information may be configured by the RACS or directly configured to the ingress node of the multicast path according to the networking situation or the network plan. Export node.
  • FIG. 3 shows an example of the transmission process of a multicast service flow.
  • the edge nodes of the multicast service bearer network include a, b, c, d, e, and f, where node f is the ingress node of the multicast path, and node a is the egress node of the multicast path.
  • the multicast stream with the multicast address pair ⁇ G, S> reaches the ingress node f from the multicast source, and enters the bearer network from the ingress node f.
  • the ingress node f pairs the multicast address of the multicast stream according to the multicast address mapping relationship.
  • G, S> is converted to ⁇ G,, S,>.
  • the multicast address pair is ⁇ G,,S, and the multicast stream is routed along the multicast path to the egress node a of the bearer network.
  • the egress node a multicasts the multicast address pair to the ⁇ G according to the multicast address mapping relationship.
  • , , S, > is converted to ⁇ G, S>, and the multicast stream is sent to the user equipment.
  • the ingress node f maps the relationship according to the multicast address that is sent to it (the inbound multicast group in the table is ⁇ G, S>, and the outgoing multicast group is ⁇ G, , S, > ), maps the incoming multicast group address ⁇ 8> to the outgoing multicast group address ⁇ G', S, >, and converts the multicast address information originally provided by the IPTV operator into a group within the bearer network.
  • the egress node a is based on the multicast address mapping table sent to it (the inbound multicast group in the table is ⁇ G, S, >, and the outgoing multicast group is ⁇ G, S>).
  • the multicast group address ⁇ 0, 8, and > is mapped to the multicast group address ⁇ G, S>, and the multicast address information in the bearer network is converted into the multicast address information originally provided by the IPTV operator.
  • the address information of the multicast service data is still provided by the IPTV operator, and the multicast service data is used by the bearer network when transmitting in the bearer network. Broadcast address information. Therefore, when IPTV is shipped When the business needs to be connected to multiple bearer networks, the multicast address of the multicast service can be consistent. The address mapping ensures that the address of the multicast service does not conflict within the bearer network. Since the address information of the multicast service data is still provided by the IPTV operator, the IPTV operator can be easily added with new services and menu management is facilitated.
  • the multicast service can be implemented according to the foregoing procedure.
  • the embodiment of the present invention also provides a multicast service. Implementation.
  • the principle of the multicast service packet is: dividing the BTV (Broadcast TV) program into different BTV service packets according to the authentication attribute and the charging attribute, and when the user equipment switches between the channel programs in the same BTV service package, There is no need to perform authentication and billing work on a per-request basis.
  • the user equipment requests a multicast service packet, the user equipment needs to request the multicast group corresponding to a group of multicast service flows in the multicast service packet, and the multicast paths of the multicast service flows are consistent. , but the multicast address is different. If the bearer network maintains the multicast path separately based on the multicast address, the maintenance workload is large.
  • the multicast address pair of a group of multicast service flows of the same multicast service packet is ⁇ G1, S1>, ⁇ G2, S2>, ⁇ G3, S3>... ⁇ Gn ,Sn>, mapped to a group of multicast address pairs with the same multicast address according to the networking situation or network plan ⁇ G,,S1,>, ⁇ G,,S2,>, ⁇ G,,S3,>.. . ⁇ G,,Sn,>, the bearer network only maintains the multicast path of the multicast service packet according to the multicast address G, including the use of ⁇ 0', *> to implement unified maintenance of the internal multicast path of the bearer network, and uniformly allocate resources. , to achieve unified and simplified control of this group of multicast service flows within the bearer network.
  • FIG. 4 and FIG. 5 show an example of implementing a multicast service for a multicast service packet according to an embodiment of the present invention.
  • the access aggregation network provides an multicast flow entry by an EN (Edge Node).
  • EN Edge Node
  • the switch is located inside the bearer network and can process multicast requests.
  • AN1 and AN2 are two multicast egress nodes.
  • the user equipment requests the multicast service and has been accepted.
  • the multicast address mapping relationship has been established in the process of requesting the multicast service, and has been delivered to the corresponding ingress node and egress node (the specific process is the same as the process shown in Figure 2).
  • the multicast service requested by the user equipment is a BTV service packet
  • the BTV service packet includes two multicast streams whose multicast address pairs are ⁇ 81 ⁇ 1> and ⁇ 82, 82>, and the address mapping relationship is: ⁇ gl , sl> corresponds
  • the address pair of the network is ⁇ g,,sl,>, ⁇ g2, s2> corresponding to the address pair ⁇ g,, s2,> of the network.
  • the process of the user equipment requesting to join the multicast service includes the following steps:
  • Step 401 The AN1 receives the multicast join request sent by the user equipment, and requests to join the multicast stream whose multicast address pair is ⁇ gl, s 1 >.
  • Step 402 The AN1 converts the multicast address pair ⁇ 1, 81> to ⁇ g', sl'> according to the pre-obtained multicast address mapping relationship.
  • Step 403 The AN1 sends an IGMP (Internet Group Management Protocol) request, and requests to add a multicast stream whose multicast address pair is ⁇ 8, 81, >, and the request is sent to the switch inside the bearer network.
  • IGMP Internet Group Management Protocol
  • Step 404 The switch sends an IGMP request to the EN at the edge of the network, and adds the user equipment to the multicast stream of the multicast address pair ⁇ g, , s 1 ' >.
  • Step 405 The AN2 receives the multicast join request sent by the user equipment, and requests to join the multicast stream whose multicast address pair is ⁇ 82 ⁇ 2>.
  • Step 406 The AN2 converts the multicast address pair ⁇ 2, 82> to ⁇ g', s2'> according to the pre-obtained multicast address mapping relationship.
  • Step 407 The AN2 sends an IGMP request to request to join the multicast stream with the multicast address pair being ⁇ 8, 82,>.
  • the request is sent to the switch inside the bearer network, and the switch receives the request to establish a multicast replication table. item. Since AN1 has requested the multicast stream corresponding to the multicast address ⁇ 8,,*>, the multicast request will not be sent to the EN.
  • FIG. 5 shows an example of a transport flow for a multicast service flow.
  • the edge nodes of the multicast service bearer network include a, b, c, d, e, and f, where node f is the ingress node of the multicast path (corresponding to EN in Figure 4), node a and node.
  • b is the egress node of the multicast path (corresponding to AN1 and AN2 in Figure 4, respectively).
  • a group of multicast streams belonging to a multicast service packet, whose corresponding set of multicast address pairs is ⁇ G1, S1> ⁇ G2,S2> ⁇ G3,S3>.. ⁇ Gn,Sn> (The multicast address For the IPTV operator, from the multicast source to the ingress node f, from the ingress node f to the bearer network, the entrance Node f pairs the multicast address of the multicast stream according to the multicast address mapping relationship.
  • ⁇ G1,S1>, ⁇ G2,S2>, ⁇ G3,S3>... ⁇ Gn,Sn ⁇ is replaced by the multicast address pair ⁇ G,,Sr>, ⁇ G,,S2,> within the bearer network.
  • the multicast stream with the multicast address pair ⁇ G', S1, >, ⁇ G, , S2, >, ⁇ G, , S3, > ... ⁇ G,, Sn,> is routed along the multicast path to the multicast path.
  • egress node and a network egress node of the carrier, b, egress node and the egress node a b are inside the bearer network according to the multicast group of the multicast stream to the multicast address, address mapping ⁇ G,, S1,> ⁇ G, , S2'> ⁇ G , , S3 , >.. ⁇ G',Sn'> ⁇ ;
  • the multicast address pair provided by the IPTV operator is ⁇ 01,81>, ⁇ 02,82>, ⁇ 03,83>. .. ⁇ Gn,Sn>, and send the set of multicast streams to the user equipment.
  • the ingress node f maps the relationship according to the multicast address that is sent to it (the inbound multicast group in the table is ⁇ G1, S1> ⁇ G2,S2> ⁇ G3, S3 >.. ⁇ Gn,Sn>, the outgoing multicast group is ⁇ G,,Sr>, ⁇ G,,S2,>, ⁇ G,,S3,>... ⁇ G,,Sn,> ), will enter
  • the multicast group address is mapped to the corresponding outgoing multicast group address, and the multicast address information originally provided by the IPTV operator is converted into the multicast address information of the bearer network; the egress nodes a and b are according to the group sent to it.
  • Broadcast address mapping relationship table (in the multicast group in the table is ⁇ G , , S1 , > ⁇ G , , S2'> ⁇ G , , S3 , >.. ⁇ G', Sn'>, and the outgoing multicast group is ⁇ G1,S1> ⁇ G2,S2> ⁇ G3,S3>.. ⁇ Gn,Sn> ), maps the incoming multicast group address to the corresponding outgoing multicast group address, and implements the multicast address information inside the network. Convert to the multicast address information originally provided by the IPTV operator.
  • the above process describes that when a multicast service packet has multiple multicast streams with the same multicast path, the multicast address pairs of different multicast streams with the same multicast path are converted into the same multicast.
  • the multicast address pair of the address (the multicast source address distinguishes different multicast groups), so that the bearer network can maintain only the multicast path corresponding to the multicast address and reduce the number of multicast path maintenance.
  • the multicast addresses of the multicast streams of different multicast paths can be mapped to the same multicast address to reduce the number of multicast path maintenance.
  • the embodiment of the present invention further provides a resource management system.
  • FIG. 6 it is a schematic structural diagram of a resource management system according to an embodiment of the present invention, where the system includes a multicast address tube.
  • the entity 6 includes a multicast address mapping module 61 and a multicast address mapping relationship sending module 62.
  • the multicast address mapping module 61 is configured to map the original multicast address identifier of the multicast service data (that is, the multicast address information provided by the IPTV operator) to the internal multicast address identifier of the bearer network, and establish the original multicast service data.
  • the broadcast address mapping relationship sending module 62 is configured to send the mapping relationship between the original multicast address identifier and the bearer network internal multicast address identifier to the ingress node device and the egress node device of the multicast path, so that the ingress node device and the egress node device can
  • the multicast address identifier conversion of the multicast service data is performed according to the mapping relationship.
  • the specific processing procedure of the multicast address mapping module 61 is as follows:
  • the multicast address mapping module 61 maps the original multicast address to a multicast address within the bearer network; or maps the original multicast address to a multicast address inside the bearer network and allocates The multicast source address of the bearer network, and the mapped multicast address and the assigned multicast source address form a multicast address pair within the network; if the original multicast address identifier is a multicast address pair, the multicast address mapping module The mapping of the multicast address in the original multicast address pair to the multicast address in the bearer network; or mapping the multicast address and the multicast source address in the original multicast address pair to the multicast address inside the bearer network. The multicast address and multicast source address of the pair;
  • the multicast address mapping module 61 may also map the original multicast address pairs of the multiple multicast service data to the internal multicast address pairs of the bearer network, if the multicast addresses in the internal multicast address pairs of the bearer networks are the same, especially for one When a group of multicast service flows in a multicast service packet have the same multicast path, the multicast address mapping module can map the multicast address pairs of the multicast service flows to the multicast with the same multicast address in the bearer network. Address pair.
  • the multicast address management entity can be located in the resource admission control function RACS, and can also be used as a function module in the router (especially the central router), the resource manager, the policy manager, and the broadband access server.
  • the embodiment of the invention further provides a data transmission device, as shown in FIG.
  • the internal interface module 72 further includes a multicast address mapping relationship receiving module 73 and a first multicast address mapping module 74.
  • the external interface module 71 and the internal interface module 72 are respectively configured to perform multicast service data interaction with devices external to and inside the bearer network, and the multicast service data may be a multicast stream or related signaling.
  • the multicast address mapping relationship receiving module 73 is configured to receive a multicast address mapping relationship, where the mapping relationship includes a mapping relationship between the original multicast address identifier of the multicast service data and the internal address identifier of the bearer network, where the original multicast address identifier is The internal multicast address identifier of the bearer network provided by the IPTV operator is allocated by the provider of the multicast service bearer network.
  • the first multicast address mapping module 74 is configured to convert the original multicast address identifier of the multicast service data into a bearer network internal address identifier according to the mapping relationship, and send the multicast service data to the internal interface module; or The internal address identifier of the bearer network of the multicast service data is converted into the original multicast address identifier, and the multicast service data is sent to the external interface module.
  • the mapping relationship information received by the multicast address mapping relationship receiving module 73 indicates that the original multicast address identifier is mapped to the internal multicast address identifier of the bearer network; the first multicast address mapping module According to the mapping relationship, the original multicast address identifier of the multicast stream received by the external interface module 71 from the multicast source is mapped/converted to the internal multicast address identifier of the bearer network, and the multicast stream is sent to the internal interface module.
  • the multicast stream is sent by the internal interface module 72 to other data transmission devices in the bearer network.
  • the mapping relationship information received by the multicast address mapping relationship receiving module 73 indicates that the internal multicast address identifier of the bearer network is mapped to the original multicast address identifier; the first multicast address mapping module According to the mapping relationship, the multicast address identifier in the bearer network of the multicast stream received by the internal interface module 72 is mapped/converted into the original multicast address identifier of the multicast stream, and the multicast stream is sent to the external interface.
  • the module 71 is sent by the external interface module 71 to the multicast stream receiver.
  • the device can also include a second multicast address mapping module 75.
  • the second multicast address mapping module is when the data transmission device is located at the exit of the multicast path
  • the original multicast address identifier of the multicast service related signaling (such as the request for joining the multicast service) received by the external interface module 71 is mapped/converted into the bearer internal multicast address identifier, and the signaling is performed. It is sent to the internal interface module 72, which is sent by the internal interface module 72 to the data transmission device in the bearer network.
  • the second multicast address mapping module 75 receives the multicast service related signaling (such as the request for joining the multicast service) received by the internal interface module 72 according to the mapping relationship.
  • the internal multicast address identifier is mapped to the original multicast address identifier of the multicast service, and the signaling is sent to the external interface module 71.
  • the embodiment of the invention further provides a multicast service implementation system.
  • the system includes a multicast address management entity and data transmission devices located at the entrance and exit of the multicast path, respectively.
  • the multicast address management entity is configured to establish a mapping relationship between the original multicast address identifier of the multicast service data and the internal multicast address identifier of the bearer network, and send information indicating the mapping relationship to the entry and exit of the multicast path respectively.
  • a data transmission device wherein the original multicast address identifier is provided by the IPTV operator, and the internal multicast address identifier of the bearer network is allocated by the provider of the multicast service bearer network;
  • the data transmission device at the ingress of the multicast path is configured to map/convert the original multicast address identifier of the multicast service data received from the multicast source to the internal multicast address identifier of the bearer network according to the mapping relationship of the multicast address. And transmitting the multicast service data to the data transmission device located at the exit of the multicast path;
  • the data transmission device at the exit of the multicast path is configured to map/convert the internal multicast address identifier of the bearer network of the multicast service data to the original multicast address identifier of the multicast service data according to the mapping relationship of the multicast address, and
  • the multicast service data is sent to the receiver of the multicast service data.
  • the control and data flow of the user equipment and the IPTV provider do not change, and the network control and the bearer layer convert the control and the multicast address in the data stream, so that the external address is not Change, internal to internal multicast address, no collision within the bearer network; in the process of converting addresses, different multicast groups with the same multicast path can be converted to have the same multicast address (by group Address area of the broadcast source).
  • the multicast network can be configured to maintain the multicast path corresponding to the multicast address, which reduces the number of multicast path maintenance.
  • the present invention can be implemented by hardware or by software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present invention can be embodied in the form of a software product that can be stored in a non-volatile storage medium.
  • a computer device (may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

组播业务的实现方法及其装置和系统 技术领域
本发明实施例涉及通信领域的组播技术，尤其涉及一种组播业务 的实现方法及其装置和系统。 背景技术
在 Internet上， 多媒体业务诸如： 流媒体， 视频会议和视频点播 等， 正在成为信息传送的重要组成部分。 点对点传输的单播方式不能 适应这一类业务传输特性 -单点发送多点接收， 在这种情况下组播应 运而生，它的出现解决了一个主机向特定的多个接收者发送消息的方 法， 成为新一代网络的不可缺少的关键技术。
IP ( Internet Protocol, 网络之间互连的协议 )组播的基本思想是， 源主机只发送一份数据， 这份数据中的目的地址为组播组地址； 组播 组中的所有接收者都可接收到同样的数据拷贝，并且只有组播组内的 主机（目标主机）可以接收该数据， 网络中其他主机不能收到。
IP地址空间被划分为 A、 B、 C、 D四类， 其中 D类地址被保留 用做组播地址。 在第四版的 IP 协议 （IPv4 ) 中， 从 224.0.0.0 到 239.255.255.255间的所有 IP地址都属于 D类地址。 其中， 224.0.0.0 到 224.0.0.255 地址范围被预留， 224.0.1.0到 238.255.255.255 地址 范围作为用户组播地址， 在全网范围内有效， 239.0.0.0 到 239.255.255.255地址范围为本地管理组播地址，仅在特定的本地范围 内有效。 在 IPv4组播网络中， 除了一些熟知的和保留的组播地址以 夕卜，其他地址并没有明确规定该如何使用，因此存在地址冲突的危险。
IPTV ( Internet Protocol Television, IP电视）业务大多运用组播 技术开展业务， 而在现在的 IPTV运营中， 要求多个 IPTV运营商可 以共用一个承载网络，如图 1所示。在该场景中，用户设备是从 IPTV 运营商提供的 EPG ( Electronic Program Guide, 电视节目菜单） 菜单 中， 获得频道的组播地址， 并根据该组播地址进行组播请求。 考虑到不同的 IPTV运营商提供的组播地址可能相同， 而且一个 IPTV运营商的大多数节目的组播路径也相同， 因此可能造成冲突。 为了解决该冲突， 可以为每个 IPTV运营商的频道分配不同的组播地 址来解决。 但如果每个频道都要有一个 IP组播地址， 承载网络需要 维护大量的组播路径， 工作量非常大。
现有技术提供一种由网络提供商统一管理组播地址的技术，由网 络提供商对 IPTV运营商的频道分配组播地址， EPG菜单由网络提供 商统一提供， 以保证进入承载网络的组播地址不冲突。 该方案从一定 程度上解决了多个 IPTV运营商共用一个承载网络造成的组播地址可 能冲突的问题。
在实现本发明创造的过程中，发明人发现现有技术至少存在以下 缺点：
若 IPTV运营商的频道的组播地址由网络提供商分配，则当 IPTV 运营商需要与多个承载网络连接时， IPTV运营商的频道的组播地址 很难保持一致； 承载网络仍需要维护大量组播路径。 发明内容
本发明实施例提供一种组播业务的实现方法及其装置和系统，以 减小承载网络所需维护的组播路径的数量。
本发明实施例提供一种组播业务实现方法， 包括：
在组播路径的入口节点和出口节点上建立组播业务数据的原组 播地址标识和承载网络内部的组播地址标识的映射关系信息；
所述入口节点根据所述映射关系信息将接收到的组播业务数据 的地址由原组播地址标识转换为承载网络内部组播地址标识 ,并发送 出去； 所述出口节点根据所述映射关系信息， 将接收到的所述组播业 务数据的地址由承载网络内部组播地址标识转换为原组播地址标识 , 并发送出去。
本发明实施例还提供一种资源管理系统，所述系统包括组播地址 管理实体， 所述组播地址管理实体包括：
组播地址映射模块，用于建立组播业务数据的原组播地址标识与 承载网络内部组播地址标识的映射关系；
组播地址映射关系发送模块，用于将表示原组播地址标识和所述 承载网络内部组播地址标识的映射关系的信息发送到组播路径的入 口节点设备和出口节点设备。
本发明实施例还提供一种数据传输设备， 包括： 外部接口模块和 内部接口模块，分别用于与承载网络外部和内部的设备进行组播业务 数据交互， 还包括：
组播地址映射关系接收模块， 用于接收组播地址映射关系信息， 所述映射关系信息为组播业务数据的原组播地址标识和承载网络内 部地址标识的映射关系信息；
组播地址映射模块， 用于根据所述映射关系信息， 将所述组播业 务数据的原组播地址标识转换为承载网络内部地址标识，并将所述组 播业务数据发送到所述内部接口模块；或将所述组播业务数据的承载 网络内部地址标识转换为原组播地址标识，并将所述组播业务数据发 送到所述外部接口模块。
本发明实施例还提供一种组播业务实现系统，包括组播地址管理 实体， 以及至少两个数据传输设备；
所述组播地址管理实体，用于建立组播业务数据的原组播地址标 识和承载网络内部组播地址标识的映射关系，并分别将表示所述映射 关系的信息发送到位于组播路径入口和出口的所述数据传输设备； 位于组播路径入口的所述数据传输设备，用于根据所述映射关系 信息，将接收到的所述组播业务数据的原组播地址标识转换为承载网 络内部组播地址标识， 并发送出去；
位于组播路径出口的所述数据传输设备，用于根据所述映射关系 信息，将所接收到的组播业务数据的承载网络内部组播地址标识转换 射为所述组播业务数据的原组播地址标识， 并发送出去。
本发明实施例还提供一种计算机可存储介质， 存储有可读写程 序， 使得计算机执行以下方法：
在组播路径的入口节点和出口节点上建立组播业务数据的原组 播地址标识和承载网络内部的组播地址标识的映射关系信息；
所述入口节点根据所述映射关系信息将接收到的组播业务数据 的地址由原组播地址标识转换为承载网络内部组播地址标识 ,并发送 出去； 所述出口节点根据所述映射关系信息， 将接收到的所述组播业 务数据的地址由承载网络内部组播地址标识转换为原组播地址标识 , 并发送出去。
本发明实施例通过将组播业务数据的原组播地址标识映射为承 载网络内部的组播地址标识，并发送到组播路径的入口节点和出口节 点， 使组播业务数据在传输过程中， 通过入口节点和出口节点的地址 映射， 在承载网络内部传输时釆用承载网络内部的组播地址标识， 在 承载网络之外时釆用该组播业务数据的原组播地址标识 ,使承载网络 内部的组播地址不会发生冲突，并可釆用合理的地址映射关系减少承 载网络内部需要维护的组播路径数量。 附图说明
图 1 为现有技术中多个 IPTV运营商共用一个承载网络的示意 图；
图 2为本发明实施例的组播地址控制流程示意图；
图 3为本发明实施例的组播业务流的传输流程示意图； 图 4为本发明实施例的组播业务信令的实现流程示意图； 图 5为本发明实施例的组播业务数据流的实现流程示意图； 图 6为本发明实施例提供的资源管理系统的结构示意图； 图 7为本发明实施例提供的数据传输设备结构示意图。 具体实施方式
在本发明实施例中， UE和 IPTV提供商的控制、 数据流程不用 变动， 由网络控制和承载层对控制和数据流中的组播地址进行转换， 在组播业务承载网络外部依然使用 IPTV提供商分配的组播地址， 在 组播业务承载网络内部使用网络控制和承载层分配的承载网络内部 组播地址进行组播业务传输，从而避免组播地址在承载网络内部发生 冲突。
下面结合附图对本发明实施例进行详细描述。
本发明实施例的组播地址控制流程示意图， 如图 2所示。 在图 2 所示的流程中， 用户设备通过正常的请求业务的流程， 通过 AF ( Application Function, 应用功能体）将组播地址信息 （如组播地址 对< 8>, 其中 G为组播地址， S为组播源地址） 下发给承载控制层 的 RACS ( Resource and Admission Control Subsystem, 资源接纳控制 功能）， RACS 将该组播地址对映射为由 RACS 管理的组播地址对 <G，,S，>, 并将该组播地址对的映射关系下发到该组播业务的组播路 径的入口节点和出口节点。 具体步骤包括：
步骤 201、 用户设备通过高层信令请求组播业务。
步骤 202、 业务控制层根据该请求， 获取到对应的组播业务地址 标识对 <G,S>, 该组播地址对是 IPTV运营商分配的。 业务控制层将 该组播地址对 <G,S>发给承载控制层， 由承载控制层进行组播路径和 资源的控制。
步骤 203、 承载控制层的 RACS为该组播业务建立组播路径， 或 将该用户设备加入组播路径 （若该组播业务的组播路径已经存在）， 将由 IPTV运营商提供的组播地址对 <G,S>映射成由网络提供商管理 的组播地址对 <G',S，>,并将组播地址对< 8>和<0',8'>的映射关系下 发到为该组播业务建立的组播路径的入口节点和出口节点。组播路径 的入口节点和出口节点位于组播业务承载网络的边缘。 其中， 入口节 点接收组播源发送的组播流， 该组播流沿组播路径路由到出口节点， 由出口节点发送到用户设备。
承载控制层的 RACS的控制功能主要包括：基于保存的策略实现 接纳控制，接受或拒绝对组播业务的请求。 如果接受用户设备的组播 业务请求， 则为传输该组播业务数据预留资源， 建立传输该组播流的 组播路径， 并进行组播地址对映射。
步骤 204、 承载控制层向业务控制层回应设置完毕信息。
步骤 205、 业务控制层向用户设备通知组播业务请求成功， 并将 用户设备所请求的组播业务的组播地址对 <G,S>发送到用户设备。
在上述流程中， 如果步骤 203中， 承载控制层为用户设备所请求 的组播业务进行资源预留，而没有为用户设备所请求的组播业务建立 组播路径 （或没有将用户设备加入组播路径）， 则步骤 205中， 用户 设备在收到业务控制层发送的组播业务请求成功的通知后 ,还执行步 骤 206, 即， 根据得到的组播地址对< 8>发送组播加入请求， 请求 中携带组播地址对为 <G,S>。 该请求到达组播路径出口节点时， 组播 加入请求中的组播地址对< 8>被映射为<0，,8，>,按照常规流程对组 播加入请求进行处理。
组播地址信息除了可以用组播地址对标识以外，还可以仅用组播 地址 G进行标识， 本发明实施例给出了几种组播地址的映射方式：
( 1 )若 IPTV运营商提供的组播地址信息为组播地址对 <G,S>, 则可将 <G,S>†的组播地址 G和组播源地址 S分别映射为承载网络提 供商管理的组播地址 G，和组播源地址 S，，即，将< 8>映射为 <G，,S，>； ( 2 )若 IPTV运营商提供的组播地址信息为组播地址对 <G,S>, 则可将 <G,S>†的组播地址和组播源地址， 映射为承载网络提供商管 理的组播地址， 即， 将< *>映射为 <G',*>;
( 3 )若 IPTV运营商提供的组播地址信息为组播地址 <G>, 则将 组播地址 <G>映射为承载网络提供商管理的组播地址 <G，>, 即， 将 <G>映射为 <G'>;
( 4 )若 IPTV运营商提供的组播地址信息为组播地址 <G>, 则将 组播地址 <G>映射为承载网络提供商管理的组播地址 G，，并为该组播 业务数据分配承载网络内部的组播源地址 S，， 组播地址 G，和组播源 地址 S'组成承载网络内部的组播地址对 <G',S，>, 即， 将 <G>映射为 <G，,S，>。 在将 IPTV运营商提供的组播地址信息映射为承载网络内部由承 载网络提供商管理的组播地址信息，建立组播地址映射关系并下发到 组播路径的入口节点和出口节点的具体实现上，可通过上述基于用户 设备请求组播业务进行，也可以根据组网情况或网络规划将组播地址 映射关系信息以静态信息配置的方式，通过 RACS或直接配置到组播 路径的入口节点和出口节点。
在通过组播业务承载网络传输组播流时 ,组播业务承载网络的入 口节点和出口节点分别根据组播地址信息的映射关系进行组播地址 信息转换，使在承载网络内部使用承载网络提供商分配的组播地址信 息。 图 3给出了一个组播业务流的传输流程实例。
如图 3所示， 组播业务承载网络的边缘节点包括 a、 b、 c、 d、 e、 f ,其中节点 f为组播路径的入口节点，节点 a为组播路径的出口节点。 组播地址对为 <G,S>的组播流从组播源到达入口节点 f, 从入口节点 f 进入承载网络， 入口节点 f根据组播地址映射关系将组播流的组播地 址对 <G,S>转换为 <G，,S，>。该组播地址对为 <G，,S， 々组播流沿组播路 径路由到承载网络的出口节点 a, 在出口节点 a根据组播地址映射关 系将组播流的组播地址对 <G，,S，>转换为 <G,S>, 并将组播流发送到用 户设备。
如图 3所示， 在具体实现过程中， 入口节点 f根据下发给它的组 播地址映射关系表（表中的入组播组为 <G,S>、 出组播组为 <G，,S，> ), 将入组播组地址< 8>映射为出组播组地址 <G',S，>, 实现将原来由 IPTV运营商提供的组播地址信息转换为承载网络内部的组播地址信 息； 出口节点 a根据下发给它的组播地址映射关系表（表中的入组播 组为 <G，,S，>、 出组播组为 <G,S> ), 将入组播组地址<0，,8，>映射为出 组播组地址 <G,S>, 实现将承载网络内部的组播地址信息转换为原来 由 IPTV运营商提供的组播地址信息。
由此可见， 针对组播源和组播业务数据的接收方用户设备， 组播 业务数据的地址信息仍由 IPTV运营商提供， 组播业务数据在承载网 络内部传输时釆用承载网络提供的组播地址信息。 因此， 当 IPTV运 营商需要与多个承载网络连接时，其组播业务的组播地址可以保持一 致，通过地址映射方式保证在组播业务的地址在承载网络内部不会冲 突。 由于组播业务数据的地址信息仍由 IPTV运营商提供， 则可以便 于 IPTV运营商增加新的业务， 以及便于进行菜单管理。
对于组播业务对应一个组播地址对的情况可以按照上述流程实 现组播业务， 对于组播业务包对应一组组播地址对的情况， 本发明实 施例也给出了一种组播业务的实现方法。
组播业务包的原理是： 将 BTV ( Broadcast TV, 广播电视）节目 根据鉴权属性和计费属性分成不同的 BTV业务包， 用户设备在同一 个 BTV业务包中的频道节目之间切换时， 不需要基于每一个请求执 行鉴权和计费工作。 这要求用户设备在请求一个组播业务包的时候， 需要将该组播业务包中的一组组播业务流对应的组播组请求下来，而 这些组播业务流的组播路径都是一致的， 但组播地址不同。 如果承载 网根据组播地址单独维护组播路径， 则维护工作量很大。
本发明实施例针对这种情况，将同一个组播业务包的一组组播业 务流的组播地址对 <G1,S1>,<G2,S2>,<G3,S3>...<Gn,Sn>,根据组网情 况或网络规划映射成组播地址都相同的一组组播地址对 <G，,S1，>,<G，,S2，>,<G，,S3，>...<G，,Sn，>,承载网络只根据组播地址 G， 维护该组播业务包的组播路径， 包括利用 <0',*>实现承载网络内部组 播路径统一维护， 统一分配资源， 实现在承载网络内部对这一组组播 业务流的统一简化控制。图 4和图 5给出了本发明实施例针对组播业 务包实现组播业务的实例。
如图 4所示， 接入汇聚网由一个 EN ( Edge Node, 边缘节点 )提 供组播流入口，交换机位于承载网络内部可处理组播请求， AN1、 AN2 分别为两个组播出口节点。 用户设备请求组播业务并已被接受。 在请 求组播业务的过程中已经建立了组播地址映射关系，并已下发到相应 的入口节点和出口节点 （具体过程同图 2所示的流程）。 用户设备所 请求的组播业务为一个 BTV业务包，该 BTV业务包包含有两个组播 地址对为<81^1>和<82,82>的组播流， 地址映射关系为： <gl,sl>对应 载网络的地址对 <g，,sl，>,<g2,s2>对应 载网络的地址对 <g，,s2，>。 用户设备请求加入组播业务的过程， 包括以下步骤：
步骤 401、 AN1收到用户设备发送的组播加入请求， 请求加入组 播地址对为 <gl ,s 1 >的组播流。
步骤 402、 AN1根据预先得到的组播地址映射关系， 将组播地址 对< 1,81>转换为 <g',sl'>。
步骤 403、 AN1发送 IGMP ( Internet组管理协议 )请求， 请求加 入组播地址对为<8，,81，>的组播流， 该请求被发送到承载网络内部的 交换机。
步骤 404、 交换机发送 IGMP请求到网络边缘的 EN, 将用户设 备加入组播地址对 <g， ,s 1 ' >的组播流。
步骤 405、 AN2收到用户设备发送的组播加入请求， 请求加入组 播地址对为 <82^2>的组播流。
步骤 406、 AN2根据预先得到的组播地址映射关系， 将组播地址 对< 2,82>转换为 <g',s2'>。
步骤 407、 AN2发送 IGMP请求，请求加入组播地址对为<8，,82，> 的组播流， 该请求被发送到承载网络内部的交换机， 交换机收到该请 求， 建立组播复制的表项。 由于 AN1 已经请求过该组播地址<8，,*> 对应的组播流， 所以该组播的请求不会再向 EN发送。
在通过组播业务承载网络传输组播流时 ,组播业务承载网络的入 口节点和出口节点分别根据组播地址对的映射关系进行组播地址转 换， 使在承载网络内部使用承载网络提供商分配的组播地址。 图 5给 出了一个组播业务流的传输流程实例。
如图 5所示， 组播业务承载网络的边缘节点包括 a、 b、 c、 d、 e、 f, 其中节点 f为组播路径的入口节点 （对应图 4中的 EN ), 节点 a 和节点 b为组播路径的出口节点 （分别对应图 4中的 AN1和 AN2 )。 属于一个组播业务包的一组组播流， 其对应的一组组播地址对为 <G1,S1> <G2,S2> <G3,S3>.. <Gn,Sn> (该组播地址对由 IPTV运营商 提供）， 从组播源到达入口节点 f, 从入口节点 f进入承载网络， 入口 节点 f 根据组播地址映射关系将该组组播流的组播地址对
<G1,S1>,<G2,S2>,<G3,S3>...<Gn,Sn^ 换为承载网络内部的组播地 址对 <G，,Sr>,<G，,S2，>,<G，,S3，>...<G，,Sn，>。 该组组播地址对为 <G',S1，>,<G， ,S2，>,<G， ,S3，> ... <G，,Sn，>的组播流沿组播路径路由到 承载网络的出口节点 a和出口节点 b, 出口节点 a和出口节点 b分别 根据组播地址映射关系将该组组播流的承载网络内部的组播地址对 <G,,S1,> <G,,S2'> <G,,S3,>.. <G',Sn'> ^^； IPTV运营商提供的组 播地址对<01,81>,<02,82>,<03,83>...<Gn,Sn>,并将该组组播流发送 到用户设备。
如图 5所示， 在具体实现过程中， 入口节点 f根据下发给它的组 播 地 址 映 射 关 系 表 （ 表 中 的 入 组 播 组 为 <G1,S1> <G2,S2> <G3,S3>.. <Gn,Sn> 、 出 组 播 组 为 <G，,Sr>,<G，,S2，>,<G，,S3，>...<G，,Sn，> ), 将入组播组地址映射为对 应的出组播组地址， 实现将原来由 IPTV运营商提供的组播地址信息 转换为承载网络内部的组播地址信息； 出口节点 a和 b根据下发给它 的 组 播 地 址 映 射 关 系 表 （ 表 中 的 入 组 播 组 为 <G,,S1,> <G,,S2'> <G,,S3,>.. <G',Sn'> 、 出 组 播 组 为 <G1,S1> <G2,S2> <G3,S3>.. <Gn,Sn> ), 将入组播组地址映射为对应 的出组播组地址，实现将承载网络内部的组播地址信息转换为原来由 IPTV运营商提供的组播地址信息。
上述流程描述了针对一个组播业务包对应有多个组播路径相同 的组播流的情况下，将具有相同组播路径的不同的组播流的组播地址 对， 转换成具有相同组播地址（由组播源的地址区分不同的组播组） 的组播地址对， 这样承载网可以只维护该组播地址对应的组播路径， 减少组播路径维护数量。 在具体应用中， 也可以将不同组播路径的组 播流的组播地址映射为相同的组播地址，以达到减小组播路径维护数 的目的。
本发明实施例还提供了一种资源管理系统， 如图 6所示， 为本发 明实施例提供的资源管理系统的结构示意图，该系统包括组播地址管 理实体 6, 该实体 6包括组播地址映射模块 61和组播地址映射关系 发送模块 62。
组播地址映射模块 61 , 用于将组播业务数据的原组播地址标识 (即由 IPTV运营商提供的组播地址信息）映射为承载网络内部组播 地址标识 ,建立组播业务数据的原组播地址标识和承载网络内部组播 地址标识的映射关系；其中，原组播地址标识为 IPTV运营商提供的， 承载网络内部组播地址标识为组播业务承载网络的提供商分配的； 组播地址映射关系发送模块 62, 用于将原组播地址标识和承载 网络内部组播地址标识的映射关系发送到组播路径的入口节点设备 和出口节点设备，使得入口节点设备和出口节点设备能够根据该映射 关系进行组播业务数据的组播地址标识转换。
组播地址映射模块 61的具体处理过程为：
若原组播地址标识为组播地址， 则组播地址映射模块 61将原组 播地址映射为承载网络内部的组播地址； 或者， 将原组播地址映射为 承载网络内部的组播地址并分配承载网络内部的组播源地址，将映射 后的组播地址和分配的组播源地址组成 载网络内部的组播地址对； 若原组播地址标识为组播地址对， 则组播地址映射模块 61将原 组播地址对中的组播地址映射为承载网络内部的组播地址； 或者， 分 别将原组播地址对中的组播地址和组播源地址映射为承载网络内部 的组播地址对中的组播地址和组播源地址；
组播地址映射模块 61还可将多个组播业务数据的原组播地址对 映射为承载网络内部组播地址对，若这些承载网络内部组播地址对中 的组播地址相同，尤其对于一个组播业务包中的一组组播业务流具有 相同的组播路径时，组播地址映射模块可将这些组播业务流的组播地 址对映射为承载网络内部具有相同组播地址的组播地址对。
组播地址管理实体可以在资源接纳控制功能 RACS中，还可以作 为一个功能模块位于路由器 （特别是中心路由器）， 资源管理器、 策 略管理器、 以及宽带接入服务器中。
本发明实施例还提供了一种数据传输设备， 如图 7所示， 为本发 明实施例提供的数据传输设备结构示意图，该设备包括外部接口模块
71和内部接口模块 72,还包括组播地址映射关系接收模块 73和第一 组播地址映射模块 74。
外部接口模块 71和内部接口模块 72, 分别用于与承载网络外部 和内部的设备进行组播业务数据交互，组播业务数据可以是组播流或 相关信令。
组播地址映射关系接收模块 73 , 用于接收组播地址映射关系， 该映射关系包括组播业务数据的原组播地址标识和承载网络内部地 址标识的映射关系； 其中， 原组播地址标识为 IPTV运营商提供的， 承载网络内部组播地址标识为组播业务承载网络的提供商分配的。
第一组播地址映射模块 74 , 用于根据映射关系， 将组播业务数 据的原组播地址标识转换为承载网络内部地址标识，并将该组播业务 数据发送到内部接口模块；或将该组播业务数据的承载网络内部地址 标识转换为原组播地址标识，并将该组播业务数据发送到所述外部接 口模块。
当数据传输设备位于组播路径的入口时，组播地址映射关系接收 模块 73接收到的映射关系信息表示将原组播地址标识映射为承载网 络内部组播地址标识； 第一组播地址映射模块 74根据该映射关系， 将外部接口模块 71从组播源接收到的组播流的原组播地址标识映射 / 转换为承载网络内部组播地址标识， 并将组播流发送到内部接口模 块， 由内部接口模块 72将组播流发送到承载网络中的其他数据传输 设备。
当数据传输设备位于组播路径的出口时，组播地址映射关系接收 模块 73接收到的映射关系信息表示将承载网络内部组播地址标识映 射为原组播地址标识； 第一组播地址映射模块 74根据该映射关系， 将内部接口模块 72接收到的组播流的承载网络内部的组播地址标识 映射 /转换为该组播流的原组播地址标识， 并将组播流发送到外部接 口模块 71 , 由外部接口模块 71发送到组播流接收方。
该设备还可以包括第二组播地址映射模块 75。 当数据传输设备位于组播路径的出口时，第二组播地址映射模块
75根据映射关系，将外部接口模块 71接收到的组播业务相关信令 (如 加入组播业务的请求） 的原组播地址标识映射 /转换为承载网络内部 组播地址标识， 并将信令发送到内部接口模块 72 , 由内部接口模块 72发送到承载网络中的数据传输设备。
当数据传输设备位于组播路径的入口时，第二组播地址映射模块 75根据映射关系，将内部接口模块 72接收到的组播业务相关信令 (如 加入组播业务的请求）的承载网络内部组播地址标识映射为该组播业 务的原组播地址标识， 并将信令发送到外部接口模块 71。
本发明实施例还提供了一种组播业务实现系统。该系统包括组播 地址管理实体和分别位于组播路径入口和出口的数据传输设备。
组播地址管理实体，用于建立组播业务数据的原组播地址标识和 承载网络内部组播地址标识的映射关系，并分别将表示该映射关系的 信息发送到位于组播路径入口和出口的数据传输设备； 其中， 原组播 地址标识为 IPTV运营商提供的， 承载网络内部组播地址标识为组播 业务承载网络的提供商分配的；
位于组播路径入口的数据传输设备，用于根据组播地址的映射关 系， 将从组播源接收到的组播业务数据的原组播地址标识映射 /转换 为承载网络内部组播地址标识，并将组播业务数据发送到位于组播路 径出口的数据传输设备；
位于组播路径出口的数据传输设备，用于根据组播地址的映射关 系， 将组播业务数据的承载网络内部组播地址标识映射 /转换为该组 播业务数据的原组播地址标识，并将组播业务数据发送到组播业务数 据的接收方。
综上所述， 本发明的上述实施例中， 用户设备和 IPTV提供商的 控制、数据流程不用变动， 由网络控制和承载层对控制和数据流中的 组播地址进行转换， 使其对外不做变动， 对内转换成内部组播地址， 承载网络内部不发生冲突； 在转换地址的过程中， 可以将有相同组播 路径的不同的组播组转换成具有相同的组播地址（由组播源的地址区 分不同的组播组）， 这样承载网可以只维护该组播地址对应的组播路 径， 减少了组播路径维护数量。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解 到本发明， 可以通过硬件实现， 也可以借助软件加必要的通用硬件平 台的方式来实现。基于这样的理解， 本发明的技术方案可以以软件产 品的形式体现出来， 该软件产品可以存储在一个非易失性存储介质
(可以是 CD-ROM, U盘， 移动硬盘等） 中， 包括若干指令用以使 得一台计算机设备（可以是个人计算机， 服务器， 或者网络设备等） 执行本发明各个实施例所述的方法。
总之， 以上所述仅为本发明的较佳实施例而已， 并非用于限定本 发明的保护范围。 凡在本发明的精神和原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权利要求
1、 一种组播业务实现方法， 其特征在于， 包括：
在组播路径的入口节点和出口节点上建立组播业务数据的原组 播地址标识和承载网络内部的组播地址标识的映射关系信息；
所述入口节点根据所述映射关系信息将接收到的组播业务数据 的地址由原组播地址标识转换为承载网络内部组播地址标识 ,并发送 出去； 所述出口节点根据所述映射关系信息， 将接收到的所述组播业 务数据的地址由承载网络内部组播地址标识转换为原组播地址标识 , 并发送出去。
2、 如权利要求 1所述的方法， 其特征在于， 所述在组播路径的 入口节点和出口节点建立组播业务数据的原组播地址标识和承载网 络内部的组播地址标识的映射关系信息， 包括：
将所述映射关系信息通过静态信息配置的方式配置到所述组播 路径的入口节点和出口节点；
或者， 当接收到组播业务数据请求时， 承载控制实体建立所述组 播业务数据的原组播地址标识与承载网络内部的组播地址标识的映 射关系信息，并将该映射关系信息发送到所述组播路径的入口节点和 出口节点。
3、 如权利要求 1所述的方法， 其特征在于， 所述组播地址标识 为组播地址， 或为由组播地址和组播源地址组成的组播地址对。
4、 如权利要求 1或 3所述的方法， 其特征在于， 所述建立组播 业务数据的原组播地址标识和承载网络内部的组播地址标识的映射 关系信息， 包括：
若所述原组播地址标识为组播地址，
则将所述组播地址映射为承载网络内部的组播地址，建立原组播 地址与所述承载网络内部组播地址的映射关系； 或者， 将所述组播 地址映射为 载网络内部的组播地址并分配 载网络内部的组播源 地址 ,将映射后的组播地址和分配的承载网络内部的组播源地址组成 承载网络内部的组播地址对，建立原组播地址与所述承载网络内部组 播地址对的映射关系；
若所述原组播地址标识为组播地址对，
则将原组播地址对中的组播地址映射为承载网络内部的组播地 址， 建立原组播地址对与所述承载网络内部组播地址的映射关系； 或 者，分别将原组播地址对中的组播地址和组播源地址映射为承载网络 内部的组播地址对中的组播地址和组播源地址 ,建立原组播地址对与 所述承载网络内部组播地址对的映射关系。
5、 如权利要求 1所述的方法， 其特征在于， 所述建立组播业务 数据的原组播地址标识和承载网络内部的组播地址标识的映射关系 信息， 包括：
当多个组播地址对对应于同一个组播业务包时，分别将所述多个 组播地址对映射为承载网络内部的组播地址对，所述承载网络内部的 组播地址对中的组播地址都相同。
6、 如权利要求 1所述的方法， 其特征在于， 还包括：
入口节点根据所述映射关系信息将接收到的组播业务相关信令 中的地址由原组播地址标识转换为承载网络内部组播地址标识，并发 送出去； 所述出口节点根据所述映射关系信息， 将接收到的组播业务 相关信令中的地址由承载网络内部组播地址标识转换为原组播地址 标识， 并发送出去。
7、 一种资源管理设备， 所述系统包括组播地址管理实体， 其特 征在于， 所述组播地址管理实体包括：
组播地址映射模块，用于建立组播业务数据的原组播地址标识与 承载网络内部组播地址标识的映射关系；
组播地址映射关系发送模块，用于将表示原组播地址标识和所述 承载网络内部组播地址标识的映射关系的信息发送到组播路径的入 口节点设备和出口节点设备。
8、 如权利要求 7所述的资源管理设备， 其特征在于， 若所述原 组播地址标识为组播地址，则所述组播地址映射模块将所述组播地址 映射为承载网络内部的组播地址； 或者， 将所述组播地址映射为承载 网络内部的组播地址并分配承载网络内部的组播源地址 ,将映射后的 组播地址和分配的组播源地址组成 7 载网络内部的组播地址对； 若所述原组播地址标识为组播地址对，则所述组播地址映射模块 将原组播地址对中的组播地址映射为承载网络内部的组播地址； 或 者，分别将原组播地址对中的组播地址和组播源地址映射为承载网络 内部的组播地址对中的组播地址和组播源地址。
9、 如权利要求 7所述的资源管理设备， 其特征在于， 所述组播 地址映射模块， 还用于当多个组播地址对对应于同一个组播业务包 时， 分别将所述多个组播地址对映射为承载网络内部组播地址对， 所 述承载网络内部组播地址对中的组播地址相同。
10、 一种数据传输设备， 包括外部接口模块和内部接口模块， 分 别用于与承载网络外部和内部的设备进行组播业务数据交互，其特征 在于， 还包括：
组播地址映射关系接收模块， 用于接收组播地址映射关系信息， 所述映射关系信息为组播业务数据的原组播地址标识和承载网络内 部地址标识的映射关系信息；
第一组播地址映射模块， 用于根据所述映射关系信息， 将所接收 到的组播业务数据的入组播地址标识转换为出组播地址标识，并将所 述组播业务数据发送出去。
11、 如权利要求 10所述的数据传输设备， 其特征在于， 当所述 数据传输设备位于组播路径入口时，所述组播地址映射关系接收模块 接收到的所述映射关系信息表示将所述原组播地址标识映射为所述 承载网络内部组播地址标识 ,所述第一组播地址映射模块根据所述映 射关系信息 ,将所述外部接口模块接收到的组播业务数据的原组播地 址标识转换为承载网络内部组播地址标识；
当所述数据传输设备位于组播路径出口时，所述组播地址映射关 系接收模块接收到的所述映射关系信息表示将所述承载网络内部组 播地址标识映射为所述原组播地址标识；所述第一组播地址映射模块 根据所述映射关系信息，将所述内部接口模块接收到的组播业务数据 的承载网络内部组播地址标识转换为所述组播业务数据的原组播地 址标识。
12、 如权利要求 10所述的数据传输设备， 其特征在于， 还包括： 第二组播地址映射模块，用于根据所述映射关系信息将所述组播 业务的信令的原组播地址标识转换为承载网络内部地址标识，并将所 述组播业务的信令发送到所述内部接口模块；或将所述组播业务的信 令的承载网络内部地址标识转换为原组播地址标识 ,并将所述组播业 务的信令发送到所述外部接口模块。
13、 如权利要求 12所述的数据传输设备， 其特征在于， 当所述 数据传输设备位于组播路径出口时，所述第二组播地址映射模块将所 述外部接口模块接收到的组播业务信令的原组播地址标识映射为承 载网络内部组播地址标识 ,并将所述组播业务信令发送到所述内部接 口模块； 当所述数据传输设备位于组播路径入口时， 所述第二组播地 址映射模块将所述内部接口模块接收到的组播业务信令的承载网络 内部组播地址标识映射为原组播地址标识，并将所述组播业务信令发 送到所述外部接口模块。
14、 一种组播业务实现系统， 其特征在于， 包括组播地址管理实 体， 以及至少两个数据传输设备；
所述组播地址管理实体，用于建立组播业务数据的原组播地址标 识和承载网络内部组播地址标识的映射关系，并分别将表示所述映射 关系的信息发送到位于组播路径入口和出口的所述数据传输设备； 位于组播路径入口的所述数据传输设备，用于根据所述映射关系 信息，将接收到的所述组播业务数据的原组播地址标识转换为承载网 络内部组播地址标识， 并发送出去；
位于组播路径出口的所述数据传输设备，用于根据所述映射关系 信息，将所接收到的组播业务数据的承载网络内部组播地址标识转换 射为所述组播业务数据的原组播地址标识， 并发送出去。
15、一种计算机可读存储介质，其特征在于，存储有可读写程序， 使得计算机执行以下方法：
在组播路径的入口节点和出口节点上建立组播业务数据的原组 播地址标识和承载网络内部的组播地址标识的映射关系信息；
所述入口节点根据所述映射关系信息将接收到的组播业务数据 的地址由原组播地址标识转换为承载网络内部组播地址标识，并发送 出去； 所述出口节点根据所述映射关系信息， 将接收到的所述组播业 务数据的地址由承载网络内部组播地址标识转换为原组播地址标识， 并发送出去。
PCT/CN2008/072006 2007-08-15 2008-08-15 Method, device and system for realizing multicast service WO2009021464A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP08783997.3A EP2139158B1 (en) 2007-08-15 2008-08-15 Method, device and system for realizing multicast service
US12/704,579 US8488603B2 (en) 2007-08-15 2010-02-12 Method, apparatus, and system for implementing multicast services

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007101405804A CN101369907B (zh) 2007-08-15 2007-08-15 组播业务的实现方法及其装置和系统
CN200710140580.4 2007-08-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/704,579 Continuation US8488603B2 (en) 2007-08-15 2010-02-12 Method, apparatus, and system for implementing multicast services

Publications (1)

Publication Number Publication Date
WO2009021464A1 true WO2009021464A1 (en) 2009-02-19

Family

ID=40350401

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/072006 WO2009021464A1 (en) 2007-08-15 2008-08-15 Method, device and system for realizing multicast service

Country Status (4)

Country Link
US (1) US8488603B2 (zh)
EP (1) EP2139158B1 (zh)
CN (1) CN101369907B (zh)
WO (1) WO2009021464A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024175458A1 (en) * 2023-02-20 2024-08-29 Nchain Licensing Ag Sending and receiving blockchain data

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8295200B2 (en) * 2009-03-31 2012-10-23 Motorola Mobility Llc Discovering multicast routing capability of an access network
US9118934B2 (en) * 2010-01-18 2015-08-25 Sprint Communications Company L.P. Integration of remote electronic device with media local area network
US9794647B1 (en) 2010-02-02 2017-10-17 Sprint Communications Company L.P. Centralized program guide
US8358640B1 (en) 2010-06-01 2013-01-22 Sprint Communications Company L.P. Femtocell bridging in media local area networks
US9319362B1 (en) * 2012-01-25 2016-04-19 Solace Systems, Inc. Messaging system with distributed filtering modules which register interests, remove any messages that do not match the registered interest, and forward any matched messages for delivery
US9294886B2 (en) * 2012-08-31 2016-03-22 Qualcomm Incorporated Evolved multimedia broadcast/multicast services (eMBMS) geo-location based group call
US9300483B2 (en) 2013-03-15 2016-03-29 International Business Machines Corporation Self-routing multicast in a software defined network fabric
US9485801B1 (en) 2014-04-04 2016-11-01 Sprint Communications Company L.P. Mobile communication device connected to home digital network
US20150381377A1 (en) * 2014-06-26 2015-12-31 Qualcomm Technologies International, Ltd. Method and apparatus for managing addresses and connectivity arrangements for transporting multicast data in a wireless network
CN105681255A (zh) * 2014-11-18 2016-06-15 中兴通讯股份有限公司 网元间媒体流数据发送、接收方法及发送、接收装置
US10673742B2 (en) * 2015-09-10 2020-06-02 Telefonaktiebolaget Lm Ericsson (Publ) Multicast state reduction via tunneling in a routed system
US10164907B2 (en) 2015-11-25 2018-12-25 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for completing loosely specified MDTs
US9848317B2 (en) 2015-11-25 2017-12-19 Viasat, Inc. Multicast handover for mobile communications
US9954765B2 (en) 2016-01-08 2018-04-24 Telefonaktiebolaget Lm Ericsson (Publ) Graph construction for computed spring multicast
CN109075984B (zh) 2016-03-28 2021-06-01 瑞典爱立信有限公司 计算的spring组播的多点到多点树
US10542057B2 (en) * 2016-12-30 2020-01-21 Akamai Technologies, Inc. Multicast overlay network for delivery of real-time video
US10904136B2 (en) 2018-08-06 2021-01-26 Telefonaktiebolaget Lm Ericsson (Publ) Multicast distribution tree versioning for minimizing multicast group traffic disruption
US11811509B2 (en) 2021-01-29 2023-11-07 Juniper Networks, Inc. Upstream multicast hop (UMH) extensions for anycast deployments
CN117411738B (zh) * 2023-12-15 2024-03-08 格创通信(浙江)有限公司 组播复制方法、装置、电子设备和存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1713611A (zh) * 2004-06-24 2005-12-28 信息产业部电信研究院 Ip电信网系统中实现组播的方法
CN1744574A (zh) * 2005-09-02 2006-03-08 杭州华为三康技术有限公司 组播报文穿越非组播网络的方法及其应用的网络系统
CN1968183A (zh) * 2005-11-17 2007-05-23 华为技术有限公司 一种在MAC in MAC网络中实现组播的方法

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US618697A (en) * 1899-01-31 Wilhelm loebinger
US6181697B1 (en) * 1998-03-31 2001-01-30 At&T Corp. Method for a unicast endpoint client to access a multicast internet protocol (IP) session and to serve as a redistributor of such session
US6611872B1 (en) * 1999-01-11 2003-08-26 Fastforward Networks, Inc. Performing multicast communication in computer networks by using overlay routing
JP3667586B2 (ja) * 2000-02-28 2005-07-06 日本電気株式会社 マルチキャストパケット転送装置、マルチキャストパケット転送システム及び記憶媒体
US6831917B1 (en) * 2000-05-10 2004-12-14 Cisco Technology, Inc. Network address translation for multicast virtual sourcing
US6870841B1 (en) * 2000-09-18 2005-03-22 At&T Corp. Controlled transmission across packet network
US7447203B2 (en) * 2003-07-29 2008-11-04 At&T Intellectual Property I, L.P. Broadband access for virtual private networks
JP4382528B2 (ja) * 2004-02-27 2009-12-16 富士通株式会社 マルチキャストネットワーク装置，マルチキャストネットワークシステムおよびマルチキャスト方法
JP4464766B2 (ja) * 2004-03-03 2010-05-19 株式会社日立製作所 マルチキャスト配信制御装置
WO2005107161A1 (fr) * 2004-04-28 2005-11-10 Beijing Jiaxun Feihong Electrical Co., Ltd. Systeme et procede de communications d'un reseau de telecommunications ip et leur application
US7519010B1 (en) * 2004-08-30 2009-04-14 Juniper Networks, Inc. Inter-autonomous system (AS) multicast virtual private networks
KR100738524B1 (ko) * 2004-11-24 2007-07-11 삼성전자주식회사 멀티캐스팅을 위한 터널링 방법 및 장치
JP4486902B2 (ja) * 2005-03-01 2010-06-23 富士通株式会社 ネットワークシステム及びゲートウェイ装置
US8471903B2 (en) * 2006-08-21 2013-06-25 At&T Intellectual Property I, L.P. Locally originated IPTV programming

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1713611A (zh) * 2004-06-24 2005-12-28 信息产业部电信研究院 Ip电信网系统中实现组播的方法
CN1744574A (zh) * 2005-09-02 2006-03-08 杭州华为三康技术有限公司 组播报文穿越非组播网络的方法及其应用的网络系统
CN1968183A (zh) * 2005-11-17 2007-05-23 华为技术有限公司 一种在MAC in MAC网络中实现组播的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2139158A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024175458A1 (en) * 2023-02-20 2024-08-29 Nchain Licensing Ag Sending and receiving blockchain data

Also Published As

Publication number Publication date
EP2139158A1 (en) 2009-12-30
CN101369907A (zh) 2009-02-18
EP2139158A4 (en) 2010-07-07
US20100142530A1 (en) 2010-06-10
EP2139158B1 (en) 2015-06-10
CN101369907B (zh) 2011-09-28
US8488603B2 (en) 2013-07-16

Similar Documents

Publication Publication Date Title
WO2009021464A1 (en) Method, device and system for realizing multicast service
US8930451B2 (en) Multicast/unicast admission control method, device and system
US9407495B2 (en) Combining locally addressed devices and wide area network (WAN) addressed devices on a single network
EP2124385B1 (en) Method, device and system for multicast service authorization controlling
US8638788B2 (en) Replication management for remote multicast replication network
US20110064077A1 (en) Method and apparatus for sending and receiving multicast packets
US8619777B2 (en) Admission control for receiving traffic at hosts
WO2008131651A1 (fr) Procédé, système et dispositif de commande de ressource multidiffusion
JP5548696B2 (ja) マルチキャストサービス品質モジュールおよび方法
WO2009021460A1 (fr) Procédé de rapport d&#39;un résultat de mise en œuvre de politique, système de communication par réseau et équipement
WO2007025461A1 (fr) Procede et systeme de gestion de la qos d&#39;un ensemble de flux speciaux
JP4787376B2 (ja) マルチキャストベアラリソースを制御するための方法、装置、およびシステム
WO2008017226A1 (fr) Système et procédé de commande de multidiffusion
WO2009024096A1 (fr) Appareil de gestion de ressources, procédé et système
JP5167295B2 (ja) マルチキャスト中継装置、マルチキャスト中継方法、及びマルチキャスト中継プログラム
KR100662257B1 (ko) 인터넷 프로토콜 티브이 서비스를 위한 홈게이트웨이 장치및 그를 이용한 서비스 우선순위 재조정 방법
WO2009026846A1 (fr) Procédé, dispositif et système de transmission de messages permettant la mise en oeuvre de services de multidiffusion
WO2021143214A1 (zh) 一种数据传输方法及相关的设备和系统

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: 08783997

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2008783997

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE