NGN Signalling requirement to support QoS

Size: px

Start display at page:

Download "NGN Signalling requirement to support QoS"

Victoria Mathews
5 years ago
Views:

Internatinal Telecmmunicatin Unin NGN Signalling requirement t supprt QS Tina Tsu (tena@huawei.cm) RACF functinal architecture defined in Rec. Y.

1 Internatinal Telecmmunicatin Unin NGN Signalling requirement t supprt QS Tina Tsu (tena@huawei.cm) RACF functinal architecture defined in Rec. Y.2111 The relevant functinal entities are: the Service Cntrl Functins; the Netwrk Attachment Cntrl Functins; the Plicy Decisin Functinal Entity (PD-FE) within the Resurce and Admissin Cntrl Functins (RACF); the Transprt Resurce Cntrl Functinal Entity TRC-FE within the RACF; the Transprt Functins, which cntain -- the Plicy Enfrcement Functinal Entity (PE-PE); -- the Transprt Resurce Enfrcement Functinal Entity (TRE-FE) (fr further study); -- ther functins. 2 1

2 Principles f mapping The realizatin presented in Q.3300 (Intrductin t the Q.330x series f Recmmendatins) accepts the cnsideratins f scalability and dmain independence that mtivated the develpment f the functinal architecture. As a result, it maps each functinal entity f the functinal architecture t a separate type f physical entity. Furthermre, each reference pint is assumed t map t a separate prtcl interface. Because this latter mapping is ne-t-ne, each interface is named after the reference pint t which it crrespnds (e.g. Rs interface crrespnding t the Rs reference pint). Depending n the technlgy invlved, it may well be that sme f the physical entities identified in this Recmmendatin are cmbined. In such a case, each cmbined entity will supprt the cmbined set f interfaces f its cmpnent elements, except that interfaces that wuld lie between the cmpnent elements if they were separate are absrbed int the interir f the cmbined entity. 3 Implementatins f functinal entities Mapping frm functinal t physical entities cncerned with resurce admissin and cntrl Functinal Entity Abbrev. Physical Entity Abbrev. Service Cntrl Functins SCF Service Cntrl Entity (e.g. implementatin f P-CSCF) SCE Netwrk Attachment Cntrl Functins NACF Netwrk Attachment Cntrl Entity NACE Plicy Decisin Functinal Entity PD-FE Plicy Decisin Physical Entity PD-PE Transprt Resurce Cntrl Functinal Entity TRC-FE Transprt Resurce Cntrl Physical Entity TRC-PE Transprt Resurce Enfrcement Functinal Entity TRE-FE Transprt Resurce Enfrcement Physical Entity TRE-PE Transprt Functins ther than the PE-PE and TRE-FE TF Transprt Physical Entity T-PE Plicy Enfrcement Functinal Entity PE-PE Plicy Enfrcement Physical Entity PE-PE 4 2

Example physical realizatin f the RACF architecture An example cnfiguratin f the physical entities identified in the table f previus slide and the interfaces between them.

3 Example physical realizatin f the RACF architecture An example cnfiguratin f the physical entities identified in the table f previus slide and the interfaces between them. The figure shws a number f pssible intercnnectin arrangements. These may vary accrding t the needs f the netwrk peratrs cncerned. 5 Nrthbund Interface Singalling Requirements(1) 1) Request fr resurces t supprt the service SCE initiates a QS request t the RAC-PE, with main parameters as fllws: Cnnectin ID: The unique ID fr each request. It is a requirement t have a "cnnectin ID" t allw the sender and receiver t match a request with fllwing respnses, related mdificatins and cancellatins. It is left fr prtcl design t determine which side generates that cnnectin ID. Stream infrmatin: infrmatin t identify an IP data stream. QS parameters: A descriptin f the service quality requirements f a stream. 2) Mdificatin f resurces t supprt service With respect t sme services, it may be necessary t mdify the QS requirements at anytime during the time the service is running. Accrding t SCE requirements, RAC-PE mdifies the bandwidth that was applied fr use the previus time. Multi-time mdificatin is supprted. Main parameters: Cnnectin ID: The unique ID fr each request. Stream infrmatin: infrmatin t identify an IP data stream. QS parameters: A descriptin f the service quality requirements f a stream. 3) Acceptance f resurces t supprt service Upn cmpleting QS resurce allcatin, RAC-PE respnds t the SCE by sending elements f success infrmatin. Main Cnnectin ID. Accepted QS parameters: Amng multi-ptinal QS capabilities, the accepted QS capability is selected. 6 3

4 Nrthbund Interface Singalling Requirements(2) 4) Rejectin f resurces t supprt service In the case that the RAC-PE cannt meet the QS request f the SCE, it will send a rejectin fr resurces t supprt service t the SCE. Main parameters: Cnnectin ID. Rejectin cause. 5) Reprt abut resurces t supprt service In the case f any change in the allcated bandwidth infrmatin (the resurce seized by the cnnectin is n lnger available, etc.; fr example), the RAC-PE shuld reprt it t the SCE. Main parameters: Cnnectin ID. Current status. 6) Release f resurces t supprt service When a service is terminated, the SCE shuld initiate a request t RAC-PE fr releasing the resurce that it has been requested t allcate. Accrding t the SCE requirement, the RAC-PE takes the bandwidth back. Main parameters: Cnnectin ID. Release cause. 7) Respnse t release f resurces The cancellatin f resurces shuld be cnfirmed t the sessin. Main Cnnectin ID. Executin Results. 7 Hrizntal Interface Singalling Requirements(1) 1. Request fr resurces t supprt service The current RAC-PE initiates a QS request t the next hp RAC-PE fr an interface, with the fllwing main - Cnnectin ID: The unique ID fr each request. Each cnnectin may cntain multiple streams. It is a requirement t have a cnnectin ID t allw the sender and receiver t match a request with fllwing respnses, related mdificatins and cancellatins. It is left fr prtcl design t determine which side generates that cnnectin ID. - Stream infrmatin: infrmatin t identify an IP data stream - QS parameters: A descriptin f the service quality requirements f a stream. Many internatinal standards are available fr reference in this respect, hence n further descriptin here. - Path infrmatin selected in the lcal dmain and the previus dmains (fr the MPLS case: By means f cnsultatin, data stream bearer path LSP sets are distributed between the RAC-PEs, s cnditins f LSP paths selected in the lcal dmain and the previus dmains shuld be prvided fr each ther amng RAC-PEs, s that a peer RAC-PE can crrectly select a transit path LSP. Fr a bidirectinal path, bth frward path and backward path are available, such as MPLS label stack. ) - Address infrmatin f the inter-dmain interface: The address f the egress interface in the lcal dmain (fr the nn-mpls case.) 2. Mdificatin f resurces t supprt service In respect with sme services, it may be necessary t mdify the QS requirements at any time during the service running. Accrding t the request by the upstream RAC-PE, a RAC-PE mdifies the bandwidth that was applied fr use at the previus time. Multi-time mdificatin is supprted. Main - Cnnectin ID: The unique ID fr each request. Each cnnectin may cntain multiple streams. - Stream infrmatin: infrmatin t identify an IP data stream. - QS parameters: A descriptin f the service quality requirements f a stream. Many internatinal standards are available fr reference in this respect, hence n further descriptin here. 8 4

5 Hrizntal Interface Singalling Requirements(2) 4. Rejectin f request fr resurces t supprt service When the RAC-PE finds ut that the QS request f the upstream RAC-PE cannt be satisfied, it will send a rejectin respnse t the upstream RAC-PE. Main - Cnnectin ID - Rejectin cause 5. Reprt abut resurces t supprt service In case f any change with the allcated bandwidth infrmatin (the resurce seized by the cnnectin is n lnger available, etc.; fr example), RAC-PE shuld reprt it t the upstream RAC-PE. Main parameters: - Cnnectin ID - Current status 6. Release f resurces t supprt service The upstream RAC-PE requests the dwnstream RAC-PE fr releasing the resurce that has been requested fr allcatin. Main - Cnnectin ID - Release cause. 7. Respnse fr release fr resurces The cancellatin f resurces shuld be cnfirmed t the upstream RAC-PE. Main - Cnnectin ID - Executin results. 9 Suthbund Interface Singalling Requirements(1) 1) QS cnfiguratin infrmatin delivery Accrding t the request f the sessin/call layer, r an adjacent RAC-PEE, the RAC-PEE determines a service rute and delivers the final strategy t the crrespnding PE-PE. Main Cnnectin ID. Stream infrmatin: infrmatin t identify an IP data stream. QS parameters. Other technlgy-specific infrmatin (e.g., selected infrmatin f the entire path, and delivered-is-cmplete path infrmatin that has been allcated fr the MPLS case). 2) QS cnfiguratin infrmatin mdificatin With respect t sme services, it may be necessary t mdify the QS requirements at any time during the service running. Accrding t the request by the sessin/call layer, r an adjacent RAC-PEE, a RAC-PEE mdifies the bandwidth that was applied fr use the previus time. The RAC-PEE determines a service rute, and delivers the mdified strategy t the crrespnding PE-PE. RAC-PEE and PE-PE supprt multi-time mdificatin. Main Cnnectin ID. Stream infrmatin: infrmatin t identify an IP data stream; QS parameters. Other technlgy-specific infrmatin (e.g., selected infrmatin f the entire path, and delivered is cmplete path infrmatin that has been allcated fr the MPLS case). 10 5

6 Suthbund Interface Singalling Requirements(1) 3) QS cnfiguratin respnse The PE-PE sets QS cnfiguratin infrmatin, and returns a success/failure indicatin. Main Cnnectin ID. Executin results. 4) Resurce status reprt This message is sent in the event f changes in the PE-PE resurce infrmatin (e.g., PE-PE fault, LSP is nt available, etc.); the RAC-PEE will maintain the related bandwidth infrmatin. Main Resurce identifier (i.e., the LSP identifier, in the MPLS case). Current status. 5) QS cnfiguratin cancellatin When a cnnectin is finished, the cnfiguratin infrmatin delivered n the cnnectin shuld be cancelled. Main parameters are: Cnnectin ID. Cause cde. 11 Interfaces and prtcls Interface Supprting Entities Prtcl Base (Nte) Rec. N. Rs SC-PE, PD-PE Diameter Q Rp Between TRC-PE RCIP Q Rw PD-PE, PE-PE Intrductin COPS-PR Q Q H.248 Q Diameter Q Rc TRC-PE, T-PE and PE-PE COPS-PR Q SNMP Q Rt Rd PD-PE, TRC-PE PD-PE t PD-PE (intra-dmain) Diameter T be determined Q Q Ri PD-PE t PD-PE (inter-dmain) T be determined Q Rn TRC-PE, TRE-PE Fr further study -- NOTES: Diameter: RFC 3588 COPS-PR: Cmmn Open Plicy Service Plicy Prvisining (RFCs 2748, 3084) SNMP: Simple Netwrk Management Prtcl (RFC 3410 and many thers) RCIP: Resurce Cnnectin Initiatin Prtcl, p. cit. 12 6

Resource and Admission Control for NGN

Resource and Admission Control for NGN Internatinal Telecmmunicatin Unin Resurce and Admissin Cntrl fr NGN Hui-Lan Lu, Ph.D. Q.4/13 Rapprteur Bell Labs, Lucent Technlgies Geneva, 14-16 June 2006 802.xx Access xdsl Dmain 1 IntServ Why? N G N