SIST EN 301 217-1:2001
(Main)V interfaces at the digital Service Node (SN); Interfaces at the VB5.2 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 1: Interface specification
- Abstract
This part of a set of ETSs on VB5 reference points specifies the physical, procedural and protocol requirements for the interfaces at the VB5.2 reference point between a broadband or combined narrowband & broadband access network and a service node. The access network shall support flexible (provisioned) VPC and VCC allocation and flexible VCC allocation on a connection by connection basis which provides flexible concentration capability at VC level within the access network and accross the VB5.2 reference point.
- Status
- Published
- Publication Date
- 31-Aug-2001
- Technical Committee
- SPS - Signalling protocols and switching
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Sep-2001
- Due Date
- 01-Sep-2001
- Completion Date
- 01-Sep-2001
SIST EN 301 217-1:2001 is the Slovenian adoption of ETSI EN 301 217-1 V1.2.2, published by SIST. It specifies the physical, procedural, and protocol requirements for the VB5.2 reference point between an Access Network (AN) and a Service Node (SN) in broadband or combined narrowband and broadband access networks. In practice, it defines how the AN and SN work together for provisioned connectivity and for on-demand virtual channel (VC) allocation under SN control.
What does SIST EN 301 217-1:2001 specify?
SIST EN 301 217-1:2001 specifies the interface at the VB5.2 reference point, not the internal design of the AN or the SN. It covers how broadband access, narrowband migration cases, and other non-B-ISDN access types are handled at the interface, while leaving equipment implementation choices open.
The document is organized into clauses on scope, references, definitions, application field, the VB5.2 concept, procedural interface requirements, connection types, non-B-ISDN handling, management functions, provisioning, real-time co-ordination, performance objectives, detailed procedures, and message formats. It also includes annexes for SDL diagrams, ATM Forum UNI support, DSS2 interworking, clipping-sensitive services, RTMC/B-BCC relationships, and an optimization study for switched broadcast services.
| Annex | What it covers |
|---|---|
| Annex A | SDL process diagrams |
| Annex B | Support of terminal equipment using ATM Forum ATM UNI signalling version 4.0 |
| Annex C | Interworking between B-BCC and DSS2 |
| Annex D | Support of services with susceptibility to clipping |
| Annex E | RTMC and B-BCC system relationship |
| Annex F | Potential optimization of the B-BCC protocol for switched broadcast services |
What are the key requirements of SIST EN 301 217-1:2001?
SIST EN 301 217-1:2001 makes the VB5.2 reference point a superset of VB5.1 by adding on-demand VC link allocation in the access network under SN control. That matters because it lets the SN dynamically allocate access-network resources per connection instead of relying only on provisioning.
VB5.2 control model
Clause 5 says the AN multiplexes and demultiplexes traffic, but it does not interpret user signalling. The SN keeps call control and associated connection control, so the access network stays service-independent and does not choose the service provider based on user signalling.
Management and signalling split
Clause 6 separates management-plane coordination from control-plane signalling. Real Time Management Co-ordination (RTMC) handles time-critical coordination across the VB5.2 reference point, while Broadband Bearer Connection Control (B-BCC) lets the SN request VC establishment, modification, and release with negotiated traffic descriptors and QoS parameters.
ATM and protocol handling
Clause 6 requires the ATM layer cell header format and encoding to follow the NNI specifications, and it applies Cell Loss Priority (CLP) handling and F4/F5 OAM flows. The B-BCC protocol uses the Signalling ATM Adaptation Layer (SAAL), including AAL5, SSCOP, and SSCF selections suited to assured message transfer.
Connection types and identifiers
Clause 7 defines connection types A to E. Types C and E are the VB5.2-specific on-demand cases, while type D covers non-B-ISDN connections; point-to-multipoint support is unidirectional from SN to UNI. The clause also requires unique VPCI and VCI use within the relevant logical user port or logical service port, so both ends can map signalling identifiers to the actual ATM cell headers.
Non-B-ISDN support
Clause 8 allows ATM-based and non-ATM-based access types to be hidden behind Access Adaptation Functions (AAFs). Where needed, Virtual User Ports (VUPs) keep access-specific details from changing the VB5.2 interface, which helps when broadband and narrowband access coexist.
RTMC, B-BCC, and procedures
Clauses 11 to 14 specify the detailed coordination, connection establishment, release, branch handling, congestion control, and reset/restart procedures, together with message names and information elements. For implementation and testing, this is where the practical state machines and protocol exchanges are defined.
What terms does SIST EN 301 217-1:2001 define?
- B-BCC function - The set of connection-control functions that lets the SN establish, modify, and release the access-network part of VCCs.
- B-BCC protocol - The layer 3 protocol between SN and AN that carries B-BCC signalling.
- RTMC function - Real Time Management Co-ordination, which coordinates time-critical management-plane actions between AN and SN.
- Logical User Port (LUP) - The logical access point used to identify the user side within a VB5.2 reference point.
- Logical Service Port (LSP) - The logical access point used to identify the service side within a VB5.2 reference point.
- Virtual User Port (VUP) - A virtual access boundary used to support certain implementations without exposing access-specific details at the interface.
- Access Network (AN) - The network between customer access and the service node that multiplexes traffic and supports the VB5.2 functions.
- Service Node (SN) - The node that keeps call control and controls on-demand bearer connection actions.
Who uses SIST EN 301 217-1:2001?
SIST EN 301 217-1:2001 is used by telecom network designers, access-network vendors, and service-node manufacturers who need a common interface model for broadband or mixed broadband/narrowband access. It is also relevant to operations and management teams that configure Q3-managed functions, provisioning engineers who allocate VPs and VCs, and test teams validating RTMC and B-BCC behaviour.
Which standards are used with SIST EN 301 217-1:2001?
- EN 301 005-1 - Provides the VB5.1 reference point model, several shared definitions, and related functional clauses reused here.
- EN 301 005-2 - Gives the PICS proforma for the VB5.1/VB5.2 family.
- EN 301 271 - Covers management interfaces associated with VB5.1 and is used for the management context.
- ETS 300 298-1/2 and EN 300 301 - Provide ATM functional characteristics, ATM layer specification, and traffic/congestion control background.
- ETS 300 404, ETS 300 428, ETS 300 436-1, ETS 300 437-1, ETS 300 486-1 - Cover OAM, AAL5, SSCOP, SSCF, and meta-signalling.
- ITU-T G.902, I.321, I.361, I.432.1 to I.432.5, Q.2931, Q.2971, Q.2110, Q.2120, Q.2130, Q.2962, Q.2963.1 to Q.2963.3, X.800 - Provide the architecture, ATM, physical-layer, signalling, negotiation, and security references used by the standard.
What does the SIST EN 301 217-1:2001 document contain?
SIST EN 301 217-1:2001 contains the interface model, connection-type classifications, and the detailed RTMC and B-BCC procedure descriptions needed to implement the VB5.2 reference point. It also includes message formats and information elements for allocation, release, modification, branch handling, reset, pre-synchronization, and fault handling.
Annex A gives SDL process diagrams, which are useful for implementation logic and conformance testing. Annex B adds support for ATM Forum UNI signalling version 4.0, Annex C shows DSS2 interworking, and Annex F explores a possible protocol optimization for switched broadcast services.
Get Certified
Connect with accredited certification bodies for this standard
BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.
NYCE
Mexican standards and certification body.
Sponsored listings
Frequently Asked Questions
SIST EN 301 217-1:2001 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "V interfaces at the digital Service Node (SN); Interfaces at the VB5.2 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 1: Interface specification". This standard covers: This part of a set of ETSs on VB5 reference points specifies the physical, procedural and protocol requirements for the interfaces at the VB5.2 reference point between a broadband or combined narrowband & broadband access network and a service node. The access network shall support flexible (provisioned) VPC and VCC allocation and flexible VCC allocation on a connection by connection basis which provides flexible concentration capability at VC level within the access network and accross the VB5.2 reference point.
This part of a set of ETSs on VB5 reference points specifies the physical, procedural and protocol requirements for the interfaces at the VB5.2 reference point between a broadband or combined narrowband & broadband access network and a service node. The access network shall support flexible (provisioned) VPC and VCC allocation and flexible VCC allocation on a connection by connection basis which provides flexible concentration capability at VC level within the access network and accross the VB5.2 reference point.
SIST EN 301 217-1:2001 is classified under the following ICS (International Classification for Standards) categories: 35.200 - Interface and interconnection equipment. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 301 217-1:2001 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.PHVQLNDV interfaces at the digital Service Node (SN); Interfaces at the VB5.2 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 1: Interface specification35.200Vmesniška in povezovalna opremaInterface and interconnection equipmentICS:Ta slovenski standard je istoveten z:EN 301 217-1 Version 1.2.2SIST EN 301 217-1:2001en01-september-2001SIST EN 301 217-1:2001SLOVENSKI
STANDARD
ETSIETSI EN 301 217-1 V1.2.2 (1999-09)2ReferenceDEN/SPS-09047-1 (b9o90ipc.PDF)KeywordsAN, SN, VB5 interface, V5 interface, broadbandETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: editor@etsi.frCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1999.All rights reserved.SIST EN 301 217-1:2001
ETSIETSI EN 301 217-1 V1.2.2 (1999-09)3ContentsIntellectual Property Rights.10Foreword.10Introduction.101Scope.122References.133Definitions and abbreviations.163.1Definitions.163.2Abbreviations.174Field of application.185Introduction to the VB5.2 reference point concept.195.1General VB5.2 design principles.195.2General reference model for the VB5.2 reference point.205.3General characteristics of individual functional groups.205.3.1User port function characteristics.205.3.2ATM connection function characteristics.205.3.3Service port function characteristics.205.4Functional modelling.215.4.1Modelling of user port function.215.4.2Modelling of service port function.215.4.3Modelling of ATM connection function.215.5AN view and SN view of physical and logical ports.216Procedural interface requirements.226.1Introduction.226.2Physical layer requirements.236.3ATM layer requirements.236.3.1Cell header format and encoding and pre-assigned cell headers for use by the ATM layer.236.3.2Cell Loss Priority (CLP).236.3.3VPC carrying RTMC and B-BCC protocol VCCs.236.3.4OAM.236.4Higher layer interface requirements.236.4.1User plane.236.4.2Control plane.236.4.3Management plane.246.4.4Establishment of VP and VC links/connections.246.4.4.1Establishment of VP links and connections.246.4.4.2Establishment of VC links and VC connections.246.4.5ATM adaptation layer for the RTMC protocol.256.4.6ATM adaptation layer for the B-BCC protocol.256.4.6.1General AAL requirements.256.4.6.2AAL5 requirements.256.4.6.3SSCOP requirements.256.4.6.4SSCF requirements.266.5Meta-signalling.266.6Interface Management Application.266.7Usage information transfer.267Broadband access network connection types.267.1Introduction to connections/connection elements.267.2Multipoint requirements.277.3Broadband access network connection element identifiers.277.3.1Connection element identifiers in user-to-network signalling messages.277.3.2Connection element identifiers in RTMC messages.27SIST EN 301 217-1:2001
ETSIETSI EN 301 217-1 V1.2.2 (1999-09)47.3.3Connection element identifiers in B-BCC messages.277.4Overview of broadband access network connection types.287.5B-ISDN type broadband access network connections.287.5.1Type A broadband access network connections.287.5.2Type B broadband access network connections.287.5.3Type C broadband access network connections.287.5.3.1Type C-VC broadband access network connections.287.5.3.1.1Application of type C-VC PP broadband AN connection.297.6Non-B-ISDN type broadband access network connections.317.6.1Type D broadband access network connections.317.6.2Type E broadband access network connections.317.6.2.1Type E-VC broadband access network connection.318Handling of non-B-ISDN access types.318.1General considerations.318.2ATM based accesses.328.2.1General approach.328.2.2User plane.328.2.3Control plane.338.2.4Management plane.338.3Non-ATM based accesses.338.3.1General approach.338.3.1.1User plane.348.3.1.2Control plane.358.3.1.3Management plane.358.3.2Analogue and 64 kbit/s based narrowband accesses as supported by V5 interfaces.358.3.3Other non-ATM based non-B-ISDN accesses.359Transfer and layer management functions.359.1General functional architecture.369.2Functional architecture of transfer and layer management functions.389.3Transfer functions required for individual broadband AN connection types.399.4Functions associated with logical and physical ports.3910Provisioning principles and requirements.4010.1General.4010.2Provisioning principles common for the VB5.1 and VB5.2 reference point concept.4010.3Provisioning principles specific for the VB5.2 reference point concept.4011Requirements for real-time co-ordination between AN and SN.4211.1Principles and requirements for real-time management co-ordination (RTMC).4211.2Principles and requirements for broadband bearer connection control (B-BCC).4211.2.1General principles for B-BCC.4211.2.2Establishment of bearer connections.4311.2.2.1Selection of VPCI and VCI at the service port.4311.2.2.2Selection of VPCI and VCI at the user port.4411.2.2.3Bearer connection parameters.4511.2.2.4Negotiation of connection characteristics.4511.2.2.5Branches of point-to-multipoint connections.4511.2.3Release of bearer connections.4511.2.4Modification of traffic parameters of established bearer connections.4611.2.5B-BCC reset.4611.2.6Automatic congestion control.4611.2.7B-BCC start-up and B-BCC restart requirements.4711.2.7.1B-BCC start-up.4711.2.7.2B-BCC restart.4711.2.7.3Indirect initiation of a B-BCC start-up or restart at the AN.4811.2.8Procedural requirements.4812Performance design objectives.4912.1Performance design objectives for transfer functions.4912.2Performance design objectives for RTMC and B-BCC functions.49SIST EN 301 217-1:2001
ETSIETSI EN 301 217-1 V1.2.2 (1999-09)513VB5.2 system architecture, structure and procedures.5013.1Introduction and overview.5013.2RTMC system architecture.5113.3RTMC procedures.5113.4B-BCC system architecture.5113.4.1System diagrams.5113.4.1.1Overview of B-BCC system.5113.4.1.2Classification of B-BCC primitives.5313.4.1.3B-BCC system (AN side).5313.4.1.4B-BCC system (SN side).5513.4.1.5Primitive interface between B-BCC system and the VB5.2 application functions.5813.4.1.5.1Primitives common for the AN and SN.5813.4.1.5.2Primitives specific for the SN.5813.4.1.5.3Primitives specific for the AN.6013.4.1.6Primitive interface between B-BCC protocol system and ATM adaptation layer.6213.4.1.7Description of VB5 B-BCC messages and parameters.6213.4.2Block diagrams.6313.4.2.1B-BCC management entities.6313.4.2.2B-BCC connection management entities.6413.4.2.3B-BCC protocol entities.6613.5VB5.2 connection control functions.6713.5.1General.6713.5.2Interworking with user signalling.6813.5.2.1Interworking with DSS2 based signalling systems.6813.5.2.2Support of user-to-network signalling systems other than DSS2.6913.5.3Selection of VPCI and VCI for service port and user port.6913.5.3.1VPCI/VCI selection procedure for the service port.6913.5.3.1.1VPCI/VCI selection procedure start at the SN.6913.5.3.1.2VPCI/VCI selection procedure at the AN.7013.5.3.1.3Selection procedure termination at the SN.7113.5.3.2VPCI/VCI selection procedure for the user port.7113.5.4Connection establishment and connection characteristics negotiation.7213.5.4.1Connection establishment start in the SN.7213.5.4.2Connection establishment start in the AN.7313.5.4.3Connection characteristics negotiation in the AN.7413.5.4.4Connection establishment continuation in the SN.7513.5.4.5Connection establishment termination in the AN.7513.5.4.6Connection establishment termination in the SN.7613.5.5Release of connections.7613.5.5.1Connection release start in the SN.7613.5.5.2Connection release in the AN.7713.5.5.3Connection release termination in the SN.7713.5.5.4Use of en bloc de-allocation.7713.5.6Modification of traffic parameters.7813.5.6.1Modification start in the SN.7813.5.6.2Modification start in the AN.7813.5.6.3Progressing modification in the SN.7813.5.6.4Modify completion in the AN.7913.5.6.5Modify terminated at the SN.8013.5.7Establishment of branches of point-to-multipoint connections.8013.5.7.1Branch establishment start in the SN.8013.5.7.2Branch establishment start in the AN.8113.5.7.3Branch establishment continuation/completion in the SN.8113.5.7.4Branch establishment termination in the AN.8213.5.7.5Branch establishment termination in the SN.8313.5.8Release of branches.8313.5.8.1Branch release start in the SN.8313.5.8.2Branch release in the AN.8413.5.8.3Branch release termination in the SN.8413.5.8.4Use of en bloc drop branch.84SIST EN 301 217-1:2001
ETSIETSI EN 301 217-1 V1.2.2 (1999-09)613.5.9Interworking with ANs not supporting point to multipoint connections.8513.5.10AN fault procedure.8513.5.11B-BCC Reset.8513.5.11.1B-BCC reset start at the SN.8613.5.11.2B-BCC reset at the AN.8613.5.11.3B-BCC reset termination in the SN.8613.5.11.4Functionality in the AN to report abnormal conditions.8713.5.12B-BCC automatic congestion control functions.8713.5.12.1Actions taken during overload in the AN.8713.5.12.2Receipt of primitives by the SN connection control function containing an automatic congestionlevel parameter.8813.5.13Establishment of (semi-)permanent VCCs via the B-BCC protocol.8813.6B-BCC communication procedures.8813.6.1General principles for the B-BCC procedures.8813.6.1.1Overview of B-BCC communication mechanism.8813.6.1.2Acknowledgements.8913.6.1.3Use of transaction identifiers.8913.6.1.4Use of connection reference numbers and branch identifiers.8913.6.1.5General error handling.9013.6.1.5.1Handling of protocol syntax error conditions.9013.6.1.5.2Error procedures with explicit action indication.9013.6.1.5.3Transmission error in communication with peer network element.9013.6.1.5.4Procedural B-BCC errors.9013.6.1.5.5Requested operation rejected by peer network element.9013.6.1.6Timers used in B-BCC procedures.9013.6.1.7Segmentation of requests into individual transactions.9113.6.2Procedures for establishment and release of bearer connections.9113.6.2.1Bearer connection establishment procedure.9113.6.2.1.1General.9113.6.2.1.2Procedure.9113.6.2.1.3Exceptional procedures.9213.6.2.2Bearer connection release procedure.9313.6.2.2.1General.9313.6.2.2.2Procedure.9413.6.2.2.3Exceptional procedures.9413.6.2.3Bearer connection modification procedure.9413.6.2.3.1General.9413.6.2.3.2Procedure.9413.6.2.3.3Exceptional procedures.9513.6.3Procedures specific for point-to-multipoint connections.9713.6.3.1Branch establishment procedure.9713.6.3.1.1General.9713.6.3.1.2Procedure.9713.6.3.1.3Exceptional procedures.9713.6.3.2Branch release procedure.9813.6.3.2.1General.9813.6.3.2.2Procedure.9813.6.3.2.3Exceptional procedures.9913.6.4B-BCC housekeeping procedures.9913.6.4.1B-BCC reset procedure.9913.6.4.1.1General.9913.6.4.1.2Procedure.9913.6.4.1.3Exceptional procedures.10013.6.4.2AN fault procedure.10013.6.4.2.1General.10013.6.4.2.2Procedure.10013.6.4.2.3Exceptional procedures.10013.6.4.3B-BCC pre-synchronization procedure.10113.6.4.3.1General.10113.6.4.3.2Procedure.101SIST EN 301 217-1:2001
ETSIETSI EN 301 217-1 V1.2.2 (1999-09)713.6.4.3.3Exceptional procedures.10113.6.4.4SAAL establishment procedure.10113.6.4.4.1General.10113.6.4.4.2Procedure.10113.6.4.4.3Exceptional procedure.10213.6.4.5B-BCC start-up procedure.10213.6.4.5.1General.10213.6.4.5.2Procedure.10213.6.4.5.3Exceptional procedures.10213.6.4.6B-BCC restart procedure.10313.6.4.6.1General.10313.6.4.6.2Procedure.10313.6.4.6.3Exceptional procedures.10414Message format and codes.10414.1Message and information element encoding principles.10514.2RTMC protocol messages and information elements.10514.3B-BCC protocol messages and information elements.10514.3.1Overview of B-BCC protocol messages.10514.3.2B-BCC messages for the support of basic B-BCC procedures.10814.3.2.1ALLOC message.10814.3.2.2ALLOC_ACC message.10814.3.2.3ALLOC_REJ message.10914.3.2.4ALLOC_COMP message.10914.3.2.5ALLOC_COMP_ACC message.10914.3.2.6ALLOC_COMP_REJ message.11014.3.2.7DEALLOC message.11014.3.2.8DEALLOC_ACC.11014.3.3B-BCC messages for the support of B-BCC housekeeping procedures.11014.3.3.1BBCC_RESET message.11014.3.3.2BBCC_RESET_ACC message.11114.3.3.3BBCC_RESET_REJ message.11114.3.3.4BBCC_PRESYNC message.11114.3.3.5BBCC_PRESYNC_ACC message.11114.3.3.6BBCC_PRESYNC_REJ message.11114.3.3.7AN_FAULT message.11214.3.3.8AN_FAULT_ACC message.11214.3.3.9PROTOCOL_ERROR message.11214.3.4Additional B-BCC messages for the support of traffic parameter modification.11214.3.4.1MODIFY message.11314.3.4.2MODIFY_ACC message.11314.3.4.3MODIFY_REJ message.11314.3.4.4MODIFY_COMP message.11314.3.4.5MODIFY_COMP_ACC message.11314.3.4.6MODIFY_COMP_REJ message.11414.3.4.7MODIFY_ABORT message.11414.3.4.8MODIFY_ABORT_ACC message.11414.3.4.9MODIFY_ABORT_REJ message.11414.3.5Additional B-BCC messages for the support of point-to-multipoint connections.11414.3.5.1ADD_BRANCH message.11414.3.5.2ADD_BRANCH_ACC message.11514.3.5.3ADD_BRANCH_REJ message.11514.3.5.4UPDATE_BRANCH message.11514.3.5.5UPDATE_BRANCH_ACC message.11514.3.5.6UPDATE_BRANCH_REJ message.11514.3.5.7DROP_BRANCH message.11614.3.5.8DROP_BRANCH_ACC message.11614.3.5.9DROP_BRANCH_REJ message.11614.3.6B-BCC function specific information elements.11714.3.6.1Overview.11714.3.6.2Connection reference number.118SIST EN 301 217-1:2001
ETSIETSI EN 301 217-1 V1.2.2 (1999-09)814.3.6.3Connection reference number list.11814.3.6.4User port connection identifier.11814.3.6.5Service port connection identifier.12014.3.6.6Alternative user port VPCI.12114.3.6.7Alternative service port VPCI.12114.3.6.8Automatic congestion level.12114.3.6.9Reject cause.
...