CN101330396B - Method for establishing multicast route and entity equipment - Google Patents
Method for establishing multicast route and entity equipment Download PDFInfo
- Publication number
- CN101330396B CN101330396B CN200710127603A CN200710127603A CN101330396B CN 101330396 B CN101330396 B CN 101330396B CN 200710127603 A CN200710127603 A CN 200710127603A CN 200710127603 A CN200710127603 A CN 200710127603A CN 101330396 B CN101330396 B CN 101330396B
- Authority
- CN
- China
- Prior art keywords
- multicast
- entity
- bearing bed
- multicast path
- path
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to the communication field and discloses a method and an entity device for establishing a multicast path. In the invention, a bearing control layer entity sets a multicast path for a bearing layer entity so as to shorten the time for establishing the multicast path. For a bearing layer entity in the multicast path can not be controlled by the bearing control layer entity, other adjacent and controllable bearing layer entities in the multicast path can be indicated to establish a multicast path through bearing signaling information, therefore, in the network, where the bearing control layer entity can only control part bearing layer entity, a multicast path can be established comparatively quickly.
Description
Technical field
The present invention relates to the communications field, particularly multicast path is set up technology.
Background technology
That Internet Protocol Television (IPTV) business is based on is that broadband Internet protocol (Internet Protocol abbreviates " IP " as) network is carried out, be main business with the Streaming Media.V compares with traditional T, and it is abundant more professional flexibly that IPTV can provide.IPTV mainly provides live/broadcast television service (being called for short " LTV "/" BTV "), VOD service (Video on Demand is called for short " VOD ") etc.Wherein, VOD service uses point-to-point communication mode; Live/broadcast television service then need send to a plurality of destination nodes with the data that a source node produces, and uses the communication mode of point-to-multipoint.Be multicasting technology to the most effective solution of point-to-multipoint delivery at present, it can effectively utilize the network bandwidth, avoids the bandwidth resources waste.
Multicasting technology is to send professional technology with Class D IP address, and the sender sends the identical services content to a plurality of recipients simultaneously, and identical content only need send a getting final product to the designated multicast address.
Obtain multicast content; Content recipient (user) need come the multicast router of requirement adjacency to send corresponding business tine to oneself through adding corresponding multicast group; This process can use Internet Group Management Protocol (Internet Group Management Protocol is called for short " IGMP ") to realize; Then pass through multicast routing protocol between the router; Like Protocol Independent Multicast-sparse mode (Protocol IndependentMulticast Sparse Mode; Be called for short " PIM-SM ") agreement etc.; With other router alternately to set up multicast path, the multicast service content just can pass to content recipient along multicast path from multicast source like this.
That is to say that in existing network, the process of setting up of multicast path divides two sections to carry out.First section for the user with in abutting connection with the process of setting up in path between the multicast router: the user through the IGMP agreement to concerning in abutting connection with multicast router report multicast member; The information such as multicast group that add or withdraw from comprising the user; If have two-layer switching equipment in abutting connection with between the multicast router user and its; Like LAN switch (LanSwitch)/digital subscriber line access multiplex (DSL Access Multiplexer; Abbreviate " DSLAM " as) etc., then this two-layer switching equipment can be realized the distribution of duplicating to multicast data flow through IGMP SNOOPING (IGMP snooping) agreement.Second section is user's the process of setting up in abutting connection with path between multicast router and the multicast source, in this process, uses multicast routing protocol (for example PIM-SM agreement etc.) to set up the multicast path tree usually.
Down in the face of being used for earlier the closely business and agreement (the Telecommunications and Internet converged Services and Protocols forAdvanced Networking of the fusion of the telecommunications of network and internet; Being called for short " TISPAN ") a multicast path under the framework sets up instance and describe, and is as shown in Figure 1.
TISPAN is with next generation network (Next Generation Network; Abbreviation " NGN ") framework is divided into operation layer and bearing bed; Bearer control layer is divided into Network Attachment Subsystem (NetworkAttachment Subsystem again; Be called for short " NASS ") subsystem and resource and admission control subsystem (Resource and Admission Control Subsystem is called for short " RACS "), as shown in Figure 2.Mainly comprise among the RACS and insert side resource and admission control function (Access-Resource andAdmission Control Function; Abbreviation " Access-Resource and Admission Control Function "), resources of core network and admission control function (Core-Resource and Admission Control Function; Be called for short " C-RACF "), based on the strategy decisive function functional entitys such as (Service-based Policy Decision Function are called for short " SPDF ") of business.
DSLAM_1 among Fig. 1 and DSLAM_2 can be corresponding to the access nodes in the TISPAN framework (Access Node is called for short " AN "); Router Router_1 and Router_2 are the nearest router of distance B SLAM, can be corresponding to IP Edge (IP fringe node), and the position of Router_3 is corresponding to Core Border Node (core boundary node).
Multicast path as shown in Figure 1 is set up process and is mainly comprised following step:
Step 101: subscriber equipment (User Equipment is called for short " UE ") 1 is at first initiated an adding (*, IGMP request G); During this request process DSLAM_1; DSLAM_1 equipment carries out IGMP Snooping, intercepts the IGMP message, record multicast group address and this user's corresponding port; Avoid follow-up multicast data flow is transmitted to the not user in multicast group, like the UE2 among Fig. 1.
Wherein (* G) represents one to be the multicast data flow of multicast group address with G, or one is multicast group address and the multicast data flow that limits one or more multicast source address with G.
Step 102:LanSwitch_1 receives that (* after IGMP request G), carries out IGMP Snooping equally, and continues to transmit and should ask to next node in this adding.
Step 103:Router_1 receives that (* after IGMP request G), judges whether to exist this (* in this adding; G) state if do not exist, then shows the shared tree of not setting up this multicast as yet; Router_1 is that the Ethernet interface that is connected to LanSwitch_1 is set up (a *; G) state, expression is from (*, multicast packet G) will send from this Ethernet interface.And to next node transmission PIM-SM message, multicast path is set up in request.
After step 104:Router_3 receives that this PIM-SM sets up multicast path message; Judge whether equally to exist (*, G) state is not if exist; Then show the shared tree of not setting up this multicast as yet; Router_3 sets up (*, a G) state, and send the PIM-SM request message to the next multicast router towards multicast source for the interface that is connected to downstream receiving terminal (Router_1).
Step 105 to step 107:PIM-SM message finally arrives multicast source (Multicast Source) through Router_4 and Router_5; Wherein Router_4, Router_5 and Multicast Source all are required to be the corresponding interface and set up (*; G) state is so far finished by the multicast forwarding path foundation of multicast source transmitting terminal to receiving terminal UE1.
Inventor of the present invention finds, the existing method of setting up multicast path through the bearing bed signaling message possibly cause problems such as the path setup delay is long.Specifically, in the above-mentioned process of setting up multicast forwarding path, relate to a plurality of bearing bed nodes, when not setting up the shared tree of this multicast as yet; Need through transmitting the bearing bed signaling, one by one at receiving terminal to all the bearing bed nodes between the transmitting terminal, like router and LanSwitch, on set up multicast path information (i.e. (*; G) state), this process efficiency is lower, makes that the path setup delay is longer; If be used in the LTV/BTV business, can cause the response time long, influence user experience.In addition, because this method needs all bearing bed routers all to support multicast routing protocols such as PIM-SM, implementation complexity is higher.
Summary of the invention
The technical problem underlying that embodiment of the present invention will solve provides a kind of method for building up and entity device of multicast path, has shortened the time that multicast path is set up.
For solving the problems of the technologies described above, execution mode of the present invention provides a kind of method for building up of multicast path, may further comprise the steps:
Each bearing bed entity that the bearer control layer entity should pass through to multicast path respectively issues multicast path information is set;
The bearing bed entity is provided with information according to multicast path and sets up multicast path.
Execution mode of the present invention also provides a kind of bearer control layer entity, comprising:
Information generating unit is set, is used to bearing bed entity generation multicast path information is set;
Transmitting element is used for that the multicast path that the information generating unit generation is set is provided with information and issues to each bearing bed entity that multicast path should pass through respectively.
Execution mode of the present invention also provides a kind of bearing bed entity, comprising:
Receiving element, the multicast path that is used to receive from above-mentioned bearer control layer entity is provided with information;
The unit is set up in the path, is used for according to the multicast path that receiving element is received information being set and sets up multicast path.
Embodiment of the present invention compared with prior art, the main distinction and effect thereof are: to the bearing bed entity multicast path is set by the bearer control layer entity, has shortened the time that multicast path is set up, thereby support the quick response to multicast service request.Because the bearer control layer entity is known the Distribution status of network topology structure and multicast data flow; So can calculate each bearing bed entity that multicast path should pass through soon; As long as it is just passable to these bearing bed entities transmission multicast paths information to be set; Each bearing bed entity is almost synchronously set up multicast path, and with respect to the mode that triggers step by step through the bearing bed signaling message fully in the prior art, the time that multicast path is set up has shortened greatly.
Description of drawings
Fig. 1 is a sketch map of setting up multicast path in the prior art;
Fig. 2 is a RACS framework sketch map in the prior art;
Fig. 3 is the method for building up flow chart according to the multicast path of first embodiment of the invention;
Fig. 4 is the method for building up flow chart according to the multicast path of second embodiment of the invention;
Fig. 5 is the method for building up flow chart according to the multicast path of third embodiment of the invention;
Fig. 6 is the bearer control layer entity structure diagram according to four embodiment of the invention;
Fig. 7 is the bearing bed entity structure diagram according to fifth embodiment of the invention.
Embodiment
For making the object of the invention, technical scheme and advantage clearer, will combine accompanying drawing that execution mode of the present invention is done to describe in detail further below.
First embodiment of the invention relates to a kind of method for building up of multicast path.In this execution mode, bearer control layer entity each bearing bed entity on multicast path issues multicast path information is set; Corresponding bearing bed entity is provided with information according to this multicast path and sets up multicast path.Through to the bearing bed entity multicast path being set, having shortened the time that multicast path is set up, thereby supported quick response multicast service request by the bearer control layer entity.
Still be example with network topology structure shown in Figure 1 below, multicast path set up flow process specify, as shown in Figure 3.
In step 301, UE1 adds multicast service (*, IGMP request G) to initiating one with its two-layer switching equipment DSLAM_1 that directly links to each other.
In step 302; DSLAM_1 receives the adding (* from UE1; G) after the request,, in this request, carry the IP address of UE1 and the multicast group address G (or multicast group address G and multicast source address) of expectation adding to the request that Access-Resource and Admission Control Function sends the application multicast load-bearing resource.
In step 303; Bearer control layer entity A-RACF carries out multicast resource access control and resource reservation to the request of this application multicast load-bearing resource; And issue multicast path according to the Distribution status decision needs of Access Network topological structure and this multicast data flow to which node (bearing bed entity) information is set, promptly confirm to form the node of Access Network multicast path.In this execution mode, suppose that UE1 is that interior first of Access Network that Router1 serves adds the subscriber equipment of multicast group G, Access-Resource and Admission Control Function confirms that need issue multicast path to DSLAM_1, LanSwitch_1 and Router1 is provided with information.Because bearer control layer entity A-RACF knows the Distribution status of network topology structure and multicast data flow; So can calculate each bearing bed entity that multicast path should pass through soon; As long as it is just passable to these bearing bed entities transmission multicast paths information to be set; With respect to the mode that triggers step by step through the bearing bed signaling message fully in the prior art, the time that multicast path is set up has shortened greatly.
In step 304 to step 306, Access-Resource and Admission Control Function issues multicast path to bearing bed entity DSLAM_1, LanSwitch_1 and Router1 respectively information is set.This broadcasts the corresponding relation that the path is provided with the interface that can comprise this multicast group address and bearing bed entity in the information, perhaps, and the corresponding relation of the interface of multicast group address and multicast source address and bearing bed entity.
Corresponding bearing bed entity (DSLAM_1, LanSwitch_1 or Router1) is when receiving multicast message; If the multicast group address of this multicast message and this multicast path are provided with the multicast group address coupling in the information; Perhaps (multicast group address and the multicast source address) of this multicast message and this multicast path are provided with (multicast group address and the multicast source address) coupling in the information, and the interface that then to this multicast path bearing bed entity corresponding with this address in the information is set duplicates this multicast message of forwarding.
In step 307, Access-Resource and Admission Control Function sends the message of request core net multicast load-bearing resource to C-RACF.
Need to prove there is not fixing precedence relationship between step 304 to the step 307, can be that executed in parallel is perhaps carried out with any sequencing.
In step 308; After bearer control layer entity C-RACF receives the message from the request core net multicast load-bearing resource of Access-Resource and Admission Control Function; Multicast resource access control and resource reservation are carried out in this request, and which node to issue multicast path according to the Distribution status decision needs of core net topological structure and this multicast data flow to information is set.
In this execution mode, do not set up as yet in the hypothesis core net (*, path G), thus C-RACF confirms that need issue multicast path to Router_3, Router_4, Router_5 and multicast source (MulticastSource) is provided with information in this step.
Equally; Because bearer control layer entity C-RACF knows the Distribution status of network topology structure and multicast data flow; So can calculate each bearing bed entity that multicast path should pass through soon; As long as it is just passable to these bearing bed entities transmission multicast paths information to be set, with respect to the mode that triggers step by step through the bearing bed signaling message fully in the prior art, the time that multicast path is set up has shortened greatly.
In step 309 to step 311, C-RACF issues multicast path to router Router_3, Router_4 and Router_5 respectively information is set.This is broadcast the path corresponding relation that can comprise the interface of this multicast group address and bearing bed entity in the information equally is set; Perhaps, the corresponding relation that comprises the interface of multicast group address and multicast source address and bearing bed entity.
Corresponding bearing bed entity (Router_3, Router_4 or Router_5) is when receiving multicast message; If the multicast group address of this multicast message and this multicast path are provided with the multicast group address coupling in the information; Perhaps (multicast group address and the multicast source address) of this multicast message and this multicast path are provided with (multicast group address and the multicast source address) coupling in the information, and the interface that then to this multicast path bearing bed entity corresponding with this address in the information is set duplicates this multicast message of forwarding.
In step 312, C-RACF issues multicast path to multicast source information is set, if this multicast source does not begin to send multicast message as yet, then indicates this multicast source to start simultaneously and sends multicast data flow.
Equally, not having fixing precedence relationship between step 309 to the step 312, can be that executed in parallel is perhaps carried out with any sequencing.
So far all accomplished the setting of multicast path on each bearing bed node, multicast data flow can begin to be sent to UE1 by multicast source.
Second embodiment of the invention relates to a kind of method for building up of multicast path equally.This execution mode and first execution mode are similar, and its difference is: in the first embodiment, through by UE to its access node that directly links to each other (being DSLAM_1) initiation adding multicast service (*; G) request; Trigger multicast path and set up flow process, and in this execution mode, through by UE to application function (Application Function; Be called for short " AF ") initiate the request of setting up multicast service, trigger multicast path and set up flow process; In first execution mode, the bearer control layer entity that relates to comprises Access-Resource and Admission Control Function and C-RACF, and in this execution mode, the bearer control layer entity that relates to also comprises SPDF.
Idiographic flow is as shown in Figure 4.In step 401, UE3 initiates one to AF and sets up multicast service (*, conversation initialized protocol G) (Session Initiation Protocol is called for short " SIP ") request.
In step 402; AF receives this and sets up multicast service (*; G) after the SIP request, the SPDF in RACS sends the request of application multicast load-bearing resource, in this request, carries the IP address and the multicast group address G (or multicast group address G and multicast source address) that hopes to add of UE3.
After SPDF among the RACS receives the request of this application multicast load-bearing resource, get into step 403 and step 408 respectively.In step 403, SPDF sends the request of application Access Network multicast load-bearing resource to Access-Resource and Admission Control Function.In step 408, SPDF sends the request of application core net multicast load-bearing resource to C-RACF.There is not fixing precedence relationship between step 403 and the step 408, can executed in parallel or carry out with any sequencing.
After step 403; Get into step 404; After Access-Resource and Admission Control Function is received the bearing resource request from SPDF; Multicast resource access control and resource reservation are carried out in this request, and issue multicast path according to the Distribution status decision needs of Access Network topological structure and this multicast data flow to which node (being the bearing bed entity) information is set.
In this execution mode, suppose that UE3 is that interior first of Access Network that Router2 serves adds the user of multicast group G, thereby Access-Resource and Admission Control Function confirms that need issue multicast path to DSLAM_2, LanSwitch_2 and Router_2 is provided with information.Because the bearer control layer entity is known the Distribution status of network topology structure and multicast data flow; So can calculate each bearing bed entity that multicast path should pass through soon; As long as it is just passable to these bearing bed entities transmission multicast paths information to be set; With respect to the mode that triggers step by step through the bearing bed signaling message fully in the prior art, the time that multicast path is set up has shortened greatly.
In step 405 to step 407, Access-Resource and Admission Control Function issues multicast path to DSLAM_2, LanSwitch_2 and Router_2 respectively information is set.Not having fixing precedence relationship between step 405 to the step 407, can be that executed in parallel is perhaps carried out with any sequencing.That is sent broadcasts the corresponding relation that the path is provided with the interface that can comprise this multicast group address and bearing bed entity in the information; Perhaps, the corresponding relation that comprises the interface of multicast group address and multicast source address and bearing bed entity.
Corresponding bearing bed entity (DSLAM_2, LanSwitch_2 or Router_2) is when receiving multicast message; If the multicast group address of this multicast message and this multicast path are provided with the multicast group address coupling in the information; Perhaps (multicast group address and the multicast source address) of this multicast message and this multicast path are provided with (multicast group address and the multicast source address) coupling in the information, and the interface that then to this multicast path bearing bed entity corresponding with this address in the information is set duplicates this multicast message of forwarding.
In step 408, SPDF sends the request of application core net multicast load-bearing resource to C-RACF.Step 408 and step 403 do not have fixing precedence relationship, after step 408, get into step 409.
In step 409; After C-RACF receives the request from the application core net multicast load-bearing resource of SPDF; Multicast resource access control and resource reservation are carried out in this request, and which node to issue multicast path according to the Distribution status decision needs of core net topological structure and this multicast data flow to information is set.Hypothesis Router_3 adds at UE1 to the multicast path of multicast source that (* was provided with in the time of G), thereby C-RACF only needs to issue multicast path to Router_3 information is set in this step in this execution mode.
In step 410, C-RACF issues multicast path to Router_3 and information is set and indicates Router_3 to begin to duplicate this multicast data flow of distribution to Router_2.
So far UE3 has set up to the multicast path of multicast source and has finished, and multicast data flow can begin to be sent to UE3 by Router_3.
Third embodiment of the invention relates to a kind of method for building up of multicast path, and is similar with first or second execution mode, and its difference is, in first or second execution mode, does not have the uncontrollable bearing bed entity of bearer control layer entity on the multicast path; And in this execution mode; There is the uncontrollable bearing bed entity of bearer control layer entity on the multicast path; In the case; Find the bearing bed entity contiguous each bearing bed entity that this bearer control layer entity need can be controlled with this uncontrollable bearing bed entity from multicast path; The bearing bed entity of indicating this vicinity triggers this uncontrollable bearing bed entity through the bearing bed signaling message and sets up multicast path, thereby in the bearer control layer entity can only the network of control section bearing bed entity, also can set up multicast path comparatively apace.
Be that example specifies below with Fig. 5; The uncontrollable bearing bed entity of bearer control layer entity A-RACF LanSwitch_2 among Fig. 5; Step 501 to step 503 is identical with step 401 to step 403 among Fig. 5; In step 504; Access-Resource and Admission Control Function carries out multicast resource access control and resource reservation to this request after receiving the bearing resource request from SPDF, and issues multicast path according to the Distribution status decision needs of Access Network topological structure and this multicast data flow to which node (being the bearing bed entity) information is set.
In this execution mode; Same hypothesis UE3 is that interior first of Access Network that Router2 serves adds the user of multicast group G; So Access-Resource and Admission Control Function confirms that need issue multicast path to DSLAM_2, LanSwitch_2 and Router_2 is provided with information; Yet; Because Access-Resource and Admission Control Function can't control LanSwitch_2, so the Access-Resource and Admission Control Function decision only sends multicast path to DSLAM_2 and Router_2 information is set, and the bearing bed entity DSLAM_2 of indication and LanSwitch_2 vicinity sets up multicast path through bearing bed signaling message triggering LanSwitch_2.
In step 505 and step 506, Access-Resource and Admission Control Function issues multicast path to DSLAM_2 and Router_2 respectively information is set.Step 505 and step 506 be fixing precedence relationship not.
In step 507, after DSLAM_2 receives that the multicast path from Access-Resource and Admission Control Function is provided with information, send to LanSwitch_2 and to add multicast service (*, IGMP request G) is used for LanSwitch_2 is provided with multicast path information.
In step 508, LanSwitch_2 receives this adding multicast service, and (* is after IGMP request G); Carry out IGMP Snooping; Intercept the IGMP message, record multicast group address and the interface that links to each other with DSLAM_2, and to Router_2 forwarding adding multicast service (*; G) IGMP request, this request terminates at the Router_2 place.Thus it is clear that, in the bearer control layer entity can only the network of control section bearing bed entity, also can set up multicast path comparatively apace.
Step 509 to step 511 is identical with step 408 to step 410.
Need to prove that each execution mode of the present invention is mainly with the UE initiation request, triggering the process of setting up multicast path is that example specifies; When concrete the application; Can be initiated the foundation of multicast path by network side equally, its key step and thought are similar, repeat no more at this.
In addition; Each execution mode of the present invention is an example with the TISPAN framework, the process of the foundation of multicast path has been carried out bright specifically, under this scene; The bearer control layer entity comprises Access-Resource and Admission Control Function, C-RACF and SPDF, and the bearing bed entity comprises DSLAM, LanSwitch and Router; Yet; Each execution mode of the present invention is not limited in TISPAN; Go for the network architecture that other carrying and control are separated equally, the bearer control layer entity also is not limited only to Access-Resource and Admission Control Function, C-RACF and SPDF, can also be third generation partner program (3rd Generation Partnership Project; Abbreviation " 3GPP ") policy control and charging rule functions (Policy Control and Charging Rules Function in; Be called for short " PCRF "), perhaps, (the International TelecommunicationUnion-Telecommunication Standardization Sector of ITU-T; Abbreviation " ITU-T ") the bearing resource controlled function entity in (Transport Resource Control-Functional Entity is called for short " TRC-FE ") etc.; The bearing bed entity is not limited to DSLAM, LanSwitch_2 and Router equally; Can be other any access node, IP fringe node, core boundary node, BAS Broadband Access Server (Broadband Remote Access Server is called for short " BRAS "), Ethernet switch, ip router etc. equally.The concrete message of transmitting between different bearer control layer entities and the bearing bed entity maybe be different, but its principle is identical, can reach effect of the present invention equally.
Four embodiment of the invention relates to a kind of bearer control layer entity, and is as shown in Figure 6, comprising: information generating unit is set, is used to bearing bed entity generation multicast path information is set; Transmitting element is used for that this multicast path that information generating unit generation is set is provided with information at least one bearing bed entity on multicast path and issues.To the bearing bed entity multicast path is set by the bearer control layer entity, has shortened the time that multicast path is set up, thereby supported quick response multicast service request.
This bearer control layer entity can also comprise: first selected cell is used for confirming that according to the Distribution status of network topology structure and multicast data flow needs issue this bearing bed entity that multicast path is provided with information; This is provided with information generating unit and for determined each the bearing bed entity of this first selected cell generates multicast path information is set; This transmitting element sends multicast path to determined each the bearing bed entity of this first selected cell information is set.Because the bearer control layer entity is known the Distribution status of network topology structure and multicast data flow; So can calculate each bearing bed entity that multicast path should pass through soon; As long as it is just passable to these bearing bed entities transmission multicast paths information to be set; With respect to the mode that triggers step by step through the bearing bed signaling message fully in the prior art, the time that multicast path is set up has shortened greatly.
This bearer control layer entity can also comprise: judging unit is used to judge whether have the uncontrollable first bearing bed entity of this bearer control layer entity on this multicast path; Second selected cell; Be used for judging under the situation that has this first bearing bed entity, select the second bearing bed entity contiguous each bearing bed entity that this bearer control layer entity can be controlled from this multicast path with this first bearing bed entity at this judging unit; Indicating member is used to indicate the selected second bearing bed entity of this second selected cell to trigger this first bearing bed entity through the bearing bed signaling message and sets up multicast path.Thereby in the bearer control layer entity can only the network of control section bearing bed entity, also can set up multicast path comparatively apace.
Bearer control layer entity in this execution mode can comprise one of following or its combination in any: the PCRF among the Access-Resource and Admission Control Function among the TISPAN, C-RACF, SPDF, the 3GPP, the TRC-FE among the ITU-T etc.
Fifth embodiment of the invention relates to a kind of bearing bed entity, and is as shown in Figure 7, comprising: receiving element, and the multicast path that is used to receive from the bearer control layer entity is provided with information; The unit is set up in the path, is used for according to the multicast path that this receiving element is received information being set and sets up multicast path.
This multicast path is provided with the corresponding relation that information comprises the interface of multicast group address and bearing bed entity, perhaps, comprises the corresponding relation of the interface of multicast group address and multicast source address and bearing bed entity.
This path is set up the unit and may further include storing sub-units is set, and is used to store the multicast path that this receiving element receives information is set.
This bearing bed entity can further include with lower unit:
The medium receiving element is used for the receiving group message;
Address comparing unit, whether mate the address of the multicast message that is used for judging that this medium receiving element is received and the address that multicast path is provided with information;
The medium retransmission unit is used for when the result of determination of this address comparing unit is coupling, and the interface that bearing bed entity corresponding with this address in the information is set to this multicast path duplicates this multicast message of forwarding.
Wherein, this address comparing unit and medium retransmission unit are provided with storing sub-units from this and obtain multicast path information is set.
Bearing bed entity in this execution mode comprises one of following or its combination in any: access node, IP fringe node, core boundary node, DSLAM, BRAS, Ethernet switch, ip router.
In sum, in embodiments of the present invention, to the bearing bed entity multicast path is set, has shortened the time that multicast path is set up, thereby supported quick response multicast service request by the bearer control layer entity.
Because the bearer control layer entity is known the Distribution status of network topology structure and multicast data flow; So can calculate each bearing bed entity that multicast path should pass through soon; As long as it is just passable to these bearing bed entities transmission multicast paths information to be set; With respect to the mode that triggers step by step through the bearing bed signaling message fully in the prior art, the time that multicast path is set up has shortened greatly.
For the uncontrollable bearing bed entity of bearer control layer entity on the multicast path, can indicate on the multicast path contiguous and controllable other bearing bed entity to trigger and set up multicast path through the bearing bed signaling message.Thereby in the bearer control layer entity can only the network of control section bearing bed entity, also can set up multicast path comparatively apace.
Though through reference some preferred implementation of the present invention; The present invention is illustrated and describes; But those of ordinary skill in the art should be understood that and can do various changes to it in form with on the details, and without departing from the spirit and scope of the present invention.
Claims (9)
1. the method for building up of a multicast path is characterized in that, may further comprise the steps:
Each bearing bed entity that the bearer control layer entity should pass through to multicast path respectively issues multicast path information is set;
Said bearing bed entity is provided with information according to said multicast path and sets up multicast path.
2. the method for building up of multicast path according to claim 1 is characterized in that, also comprises following steps:
If there is the uncontrollable first bearing bed entity of said bearer control layer entity on the said multicast path; Find the second bearing bed entity contiguous each bearing bed entity that then this bearer control layer entity can be controlled from said multicast path, indicate this second bearing bed entity to trigger this first bearing bed entity and set up multicast path through the bearing bed signaling message with this first bearing bed entity.
3. the method for building up of multicast path according to claim 1 is characterized in that, said bearer control layer entity confirms that according to the Distribution status of network topology structure and multicast data flow needs issue the said bearing bed entity that said multicast path is provided with information.
4. according to the method for building up of each described multicast path in the claim 1 to 3; It is characterized in that; Said multicast path is provided with information and comprises: the corresponding relation of the interface of multicast group address and bearing bed entity; Perhaps, the corresponding relation of the interface of multicast group address and multicast source address and bearing bed entity.
5. according to the method for building up of each described multicast path in the claim 1 to 3, it is characterized in that said bearer control layer entity comprises one of following or its combination in any:
Insert side resource and admission control function, core-network side resource and admission control function, strategy decisive function, policy control and charging rule functions, bearing resource controlled function entity based on business;
Said bearing bed entity comprises one of following or its combination in any:
Access node, IP fringe node, core boundary node, digital subscriber line access multiplex, BAS Broadband Access Server, Ethernet switch, ip router.
6. a bearer control layer entity is characterized in that, comprising:
Information generating unit is set, is used to bearing bed entity generation multicast path information is set;
Transmitting element is used for that the said multicast path that the information generating unit generation is set is provided with information and issues to each bearing bed entity that multicast path should pass through respectively.
7. bearer control layer entity according to claim 6 is characterized in that, also comprises:
First selected cell is used for confirming that according to the Distribution status of network topology structure and multicast data flow needs issue the said bearing bed entity that said multicast path is provided with information;
The said information generating unit that is provided with is that determined each the bearing bed entity generation multicast path of said first selected cell is provided with information;
Said transmitting element sends multicast path to determined each the bearing bed entity of said first selected cell information is set.
8. bearer control layer entity according to claim 6 is characterized in that, also comprises:
Judging unit is used to judge whether have the uncontrollable first bearing bed entity of said bearer control layer entity on the said multicast path;
Second selected cell; Be used for existing under the situation of the said first bearing bed entity, from each bearing bed entity that the above bearer control layer entity of said multicast path can be controlled, select the second bearing bed entity contiguous with this first bearing bed entity in said judging unit judgement;
Indicating member is used to indicate the selected second bearing bed entity of said second selected cell to trigger the said first bearing bed entity through the bearing bed signaling message and sets up multicast path.
9. according to each described bearer control layer entity in the claim 6 to 8, it is characterized in that said bearer control layer entity comprises one of following or its combination in any:
Insert side resource and admission control function, core-network side resource and admission control function, strategy decisive function, policy control and charging rule functions, bearing resource controlled function entity based on business.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710127603A CN101330396B (en) | 2007-06-18 | 2007-06-18 | Method for establishing multicast route and entity equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710127603A CN101330396B (en) | 2007-06-18 | 2007-06-18 | Method for establishing multicast route and entity equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101330396A CN101330396A (en) | 2008-12-24 |
| CN101330396B true CN101330396B (en) | 2012-10-03 |
Family
ID=40206005
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200710127603A Expired - Fee Related CN101330396B (en) | 2007-06-18 | 2007-06-18 | Method for establishing multicast route and entity equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101330396B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1463103A (en) * | 2002-04-09 | 2003-12-24 | 三星电子株式会社 | Appts. and method for transmitting control information of multimedia broadcasting/combined broadcasting affairs |
| CN1607779A (en) * | 2003-10-14 | 2005-04-20 | 华为技术有限公司 | A method for implementing resource distribution |
| CN1889581A (en) * | 2005-06-30 | 2007-01-03 | 华为技术有限公司 | Inter-carrying control hierarchy equipment dynamic route realizing method |
| CN1956408A (en) * | 2006-07-17 | 2007-05-02 | 华为技术有限公司 | Method and device for ensuring service QoS at different bearing layer network communicating |
-
2007
- 2007-06-18 CN CN200710127603A patent/CN101330396B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1463103A (en) * | 2002-04-09 | 2003-12-24 | 三星电子株式会社 | Appts. and method for transmitting control information of multimedia broadcasting/combined broadcasting affairs |
| CN1607779A (en) * | 2003-10-14 | 2005-04-20 | 华为技术有限公司 | A method for implementing resource distribution |
| CN1889581A (en) * | 2005-06-30 | 2007-01-03 | 华为技术有限公司 | Inter-carrying control hierarchy equipment dynamic route realizing method |
| CN1956408A (en) * | 2006-07-17 | 2007-05-02 | 华为技术有限公司 | Method and device for ensuring service QoS at different bearing layer network communicating |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101330396A (en) | 2008-12-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP3942033B2 (en) | Multicast method in a network for point-to-point packet switching | |
| US6728777B1 (en) | Method for engineering paths for multicast traffic | |
| CA2721472C (en) | Method and apparatus for multicast tree management in multi-hop relay communication system | |
| EP2012461A1 (en) | Multicast network system | |
| CN101299825B (en) | Method, system and apparatus for implementing multicast load-bearing resource control | |
| CN101572650B (en) | Method and system of IPTV resource allocation | |
| KR20120076444A (en) | System for chatting service using embms and control method for user equipment, ebm-sc and service provider server of the system for chatting service using embms | |
| JP4654278B2 (en) | Multicast tree assignment method and apparatus | |
| CA2376032A1 (en) | Method for engineering paths for multicast traffic | |
| CN101325500B (en) | Method, system and apparatus for implementing multicast load-bearing resource | |
| CN101483639A (en) | Method for resource management in network | |
| WO2009103192A1 (en) | A resource allocation method and a resource release method | |
| WO2010069174A1 (en) | A data transmission method, system and equipment | |
| WO2013037319A1 (en) | Bandwidth resource management method, device and system for label switched path | |
| CN101330396B (en) | Method for establishing multicast route and entity equipment | |
| CN101291242B (en) | Method, system and apparatus for PIM DM to support bandwidth reservation and establishing multicast list | |
| CN101789897A (en) | Method and router for resource reservation in protocol-independent multicast | |
| Chandrasekar et al. | Performance of Video Conferencing using Protocol Independent Multicast Routing with Core failure | |
| WO2008025267A1 (en) | Method, system, resource and admission control unit for realizing the multicast service | |
| Al-Misbahi et al. | The overlay multicast protocol (OMP): A proposed solution to improving scalability of multicasting in MPLS networks | |
| Bettahar et al. | A simple resource reservation protocol for multicast communications | |
| Cho et al. | A Bandwidth Reservation Method for Multicast Streaming Service | |
| Di Crescenzo et al. | MULTICAST-AWARE QOS IN NEXT GENERATION NETWORKS | |
| Nadeau et al. | NXG03-2: Any Source Implicit Multicast (ASIMcast) | |
| Kim et al. | A Scalable Hybrid Overlay Multicast Adopting Host Group Model for Subnet-Dense Receivers |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20121003 Termination date: 20140618 |
|
| EXPY | Termination of patent right or utility model |