SIST EN 301 005-1:2000

• 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.1 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 but without concentration capability at VC level within the access network.

• Status: Published
• Publication Date: 30-Nov-2000
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2000
• Due Date: 01-Dec-2000
• Completion Date: 01-Dec-2000
• Ref Project: ETSI EN 301 005-1 V1.1.4 (1998-05) - V interfaces at the digital Service Node (SN); Interfaces at the VB5.1 reference point for the support of broadband or combined narrowband and broadband Access Networks (ANs); Part 1: Interface specification

SIST EN 301 005-1:2000 is the Slovenian adoption of ETSI EN 301 005-1, Part 1 of the VB5.1 series. It specifies the physical, procedural and protocol requirements for the VB5.1 reference point between an Access Network (AN) and a Service Node (SN), for broadband and combined narrowband/broadband access arrangements.

What does SIST EN 301 005-1:2000 specify?

SIST EN 301 005-1:2000 specifies how an AN and an SN interconnect at the VB5.1 reference point, including the supported access types, the ATM-based transfer model, and the management coordination needed between the two sides. The document covers provisioned connectivity only, so the AN supports flexible allocation of VPL and VCL resources but not VC-level concentration inside the access network.

The document is organized into clauses covering scope, references, definitions, the field of application, the VB5.1 concept, procedural interface requirements, connection types, non-B-ISDN access, transfer and layer management, provisioning, RTMC, performance objectives, system architecture, message formats and codes, followed by annexes.

Annex	What it covers
A	SDL process diagrams
B	UPC and NPC function location
C	Primitive interface between VB5.1 protocol FSMs and the environment
D	Added value features of VB5.1 interfaces applicable to other VBx interfaces
E	Application of the protection facility of SDH on the VB5.1 interface
F	Examples of physical interface options
G	Examples of non-ATM based non-B-ISDN accesses
H	Bibliography

What are the key requirements of SIST EN 301 005-1:2000?

Service split and management

SIST EN 301 005-1:2000 keeps user signalling and call control in the SN, while the AN multiplexes and demultiplexes traffic and does not interpret user signalling. In practice, this means the AN is not a service decision point and the SN remains responsible for the service state.

The standard separates non-real-time co-ordination, handled through Q3(AN) and Q3(SN), from Real Time Management Co-ordination (RTMC), which uses a dedicated protocol across VB5.1. That matters because some state changes must be synchronized quickly between AN and SN, not only through normal TMN management.

Physical and ATM layer behavior

Clause 6 requires the interface to use existing physical layer standards, with point-to-point physical topology, timing from the network clock, and physical-layer OAM and protection mechanisms such as SDH section protection and path trace where applicable. The document also allows multiple transmission convergence functions and notes that at least 16 can be accommodated at the SNI.

At the ATM layer, the cell header format follows the NNI specifications, CLP-marked cells may be discarded first under congestion, and the VPC carrying the RTMC protocol VCC must not carry user data or user signalling traffic. In practice, this keeps management traffic separate from service traffic.

Higher layers, connection types and identifiers

Clause 6.4 states that ATM-based user-plane traffic is transparent to the AN, while non-B-ISDN access types need AAL functions inside the AN. For RTMC, the standard uses SAAL, with AAL5, SSCOP and SSCF selections defined for assured delivery of management messages.

Clauses 7 and 8 classify broadband AN connection types as A, B and D, with point-to-point or point-to-multipoint forms where applicable. Type A is for provisioned connections, Type B for network-internal connections, and Type D for non-B-ISDN support through a virtual user port or circuit emulation. The practical point is that implementers need to choose the connection type that matches whether the access is B-ISDN, narrowband or another non-B-ISDN service.

Clause 7.3 requires unique VPCI handling for RTMC and user signalling, tied to the relevant logical user port or logical service port. That is important for provisioning and troubleshooting because the AN and SN must agree on which user flow a management message refers to.

What terms does SIST EN 301 005-1:2000 define?

• Logical service port (LSP) - The set of Virtual Paths at one VB5.1 reference point associated with one SN.
• Logical user port (LUP) - The set of Virtual Paths at the UNI or VUP associated with one VB5.1 reference point.
• Physical user port (PUP) - The physical layer functions related to one transmission convergence function at the UNI.
• Physical service port (PSP) - The physical layer functions related to one transmission convergence function at the VB5.1 reference point.
• Real Time Management Co-ordination (RTMC) - Management functions that exchange time-critical status and coordination information between AN and SN.
• Virtual User Port (VUP) - An AN internal reference point used to support non-B-ISDN access types in a way consistent with B-ISDN access types.

Who uses SIST EN 301 005-1:2000?

SIST EN 301 005-1:2000 is used by access network operators, service node operators, and equipment manufacturers that need to design or integrate VB5.1 interfaces. It is also relevant to planners and quality teams who provision VPs, coordinate RTMC behavior, manage mixed broadband/narrowband access, and check interface conformance.

Which standards are used with SIST EN 301 005-1:2000?

The main companion standards are:

• ETS 300 298-1 / ETS 300 298-2 - ATM functional characteristics and ATM layer / NNI cell header rules.
• ETS 300 299 and ETS 300 300 - Physical layer interfaces for B-ISDN cell-based and SDH-based access.
• ETS 300 301 - Traffic control and congestion control, including CLP handling.
• ETS 300 324-1 and ETS 300 347-1 - V5.1 and V5.2 access-network reference points used for narrowband integration.
• ETS 300 404 - B-ISDN OAM principles and functions.
• ETS 300 428, ETS 300 436-1, ETS 300 437-1 - AAL5, SSCOP and SSCF used by the RTMC protocol.
• ETS 300 443-1 and ETS 300 486-1 - DSS2 and meta-signalling.
• ITU-T G.902, I.321, I.371, I.432.1 to I.432.5, I.610, I.732, Z.100 and Z.120 - Access-network architecture, protocol model, traffic control, UNI characteristics, OAM, AAL concepts, SDL and MSC notation.

What does the SIST EN 301 005-1:2000 document contain?

The document contains system models, interface rules, RTMC procedures, message definitions and coding rules. It also gives SDL process diagrams, primitive interface definitions, and detailed message sequences for operations such as blocking, unblocking, reset, verification of LSP ID, and VPCI consistency checks.

Annex C is especially useful for implementation and testing because it maps primitives to messages and describes exceptional procedures. Annexes F and G give example physical interface options and example non-ATM based non-B-ISDN accesses, which help when comparing an actual design against the standard’s intended use.

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.1 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 005-1 Version 1.1.4SIST EN 301 005-1:2000en01-december-2000SIST EN 301 005-1:2000SLOVENSKI
STANDARD
EN 301 005-1 V1.1.4 (1998-05)European Standard (Telecommunications series)V interfaces at the digital Service Node (SN);Interfaces at the VB5.1 reference point for the support ofbroadband or combined narrowband and broadbandAccess Networks (ANs);Part 1: Interface specificationSIST EN 301 005-1:2000

ETSIEN 301 005-1 V1.1.4 (1998-05)2ReferenceDEN/SPS-03046-1 (9b090ieo.PDF)KeywordsV interface, PSTN, ISDN, B-ISDNETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/[e-mail]://www.etsi.frhttp://www.etsi.orgCopyright 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 1998.All rights reserved.SIST EN 301 005-1:2000

ETSIEN 301 005-1 V1.1.4 (1998-05)3ContentsIntellectual Property Rights.9Foreword.9Introduction.91Scope.112References.122.1Normative references.122.2Informative references.143Definitions and abbreviations.143.1Definitions.143.2Abbreviations.154Field of application.174.1Applications of the VB5.1 interface.174.1.1Transport network.184.2Integration of narrowband customer access types.194.3Support of other non-B-ISDN access types.204.4Support of various service node types.205Introduction to the VB5.1 reference point concept.235.1General VB5.1 design principles.235.2General reference model for the VB5.1 reference point.245.3General characteristics of individual functional groups.265.3.1User port function characteristics.265.3.2ATM connection function characteristics.265.3.3Service port function characteristics.265.4Functional modelling.275.4.1Modelling of user port function.275.4.2Modelling of service port function.275.4.3Modelling of ATM connection function.285.5AN view and SN view of physical and logical ports.295.5.1View from access network.295.5.2View from service node.306Procedural interface requirements.316.1Introduction.316.2Physical layer requirements.326.2.1General.326.2.2Basic characteristics of the VB5.1 interface.326.2.3VB5.1 interface options.336.2.4Interface requirements.336.2.4.1Interface topology and transfer capability.336.2.4.2Maximum number of transmission convergence functions.336.2.4.3Timing.346.2.4.4OAM.346.2.4.5Protection.346.2.4.6Transmission path identification.346.2.4.7Pre-assigned cell headers for use by the physical layer.346.3ATM layer requirements.346.3.1Cell header format and encoding and pre-assigned cell headers for use by the ATM layer.346.3.2Cell Loss Priority (CLP).356.3.3VPC carrying the RTMC protocol VCC.356.3.4OAM.356.4Higher layer interface requirements.356.4.1User plane.356.4.2Control plane.35SIST EN 301 005-1:2000

ETSIEN 301 005-1 V1.1.4 (1998-05)46.4.3Management plane.356.4.4Establishment of VP and VC links/connections.366.4.4.1Establishment of VP links and connections.366.4.4.2Establishment of VC links and VC connections.366.4.5ATM adaptation layer for the RTMC protocol.366.4.5.1General AAL requirements.366.4.5.2AAL5 requirements.366.4.5.3SSCOP requirements.366.4.5.4SSCF requirements.376.5Meta-signalling.376.6Interface management application.377Broadband access network connection types.377.1Introduction to connections/connection elements.377.2Multipoint requirements.387.3Broadband access network connection element identifiers.387.3.1Connection element identifiers in user-to-network signalling messages.387.3.2Connection element identifiers in RTMC messages.387.4Broadband access network connection type matrix.397.5B-ISDN type broadband access network connections.417.5.1Type A broadband access network connections.417.5.1.1Type A-VP broadband access network connection.417.5.1.1.1Application of type A-VP ptp broadband AN connection.417.5.1.2Type A-VC broadband access network connections.427.5.1.2.1Application of type A-VC ptp broadband AN connection.437.5.2Type B broadband access network connections.447.6Non-B-ISDN type broadband access network connections (type D).447.6.1Type D-VP broadband access network connection.447.6.2 Type D-VC broadband access network connection.457.6.3Application example of non-B-ISDN type broadband access network connections for the support ofnarrowband access types.458Non-B-ISDN access.468.1General considerations.468.2ATM based accesses.468.2.1General approach.468.2.2User plane.478.2.3Control plane.478.2.4Management plane.478.3Non-ATM based accesses.488.3.1General approach.488.3.1.1User plane.488.3.1.2Control plane.498.3.1.3Management plane.498.3.2Analogue and 64 kbit/s based narrowband accesses as supported by V5 interfaces.508.3.2.1Principles.508.3.2.2AAL for 2 048 kbit/s circuit emulation.508.3.2.3Connection characteristics for circuit emulation.518.3.3Other non-ATM based non-B-ISDN accesses.519Transfer and layer management functions.529.1General functional architecture.529.2Functional architecture of transfer and layer management functions.539.3Transfer functions required for individual broadband AN connection types.549.4Functions associated with the physical user port.559.5Functions associated with the logical user port.569.5.1ATM virtual path sublayer functions at the LUP.569.5.2ATM virtual channel sublayer functions on top of the LUP.569.6Functions associated with the adaptation of non-B-ISDN access types.589.6.1Functions for the support of narrowband accesses as supported by V5 interfaces.589.6.2Functions for the support of other non-B-ISDN access types.58SIST EN 301 005-1:2000

ETSIEN 301 005-1 V1.1.4 (1998-05)59.7Connection functions.589.8Functions associated with the physical service port.589.9Functions associated with the Logical Service Port (LSP).599.9.1ATM virtual path sublayer functions at the LSP.599.9.2ATM virtual channel sublayer functions on top of the LSP.5910Provisioning principles and requirements.6210.1General.6210.2Principles.6211Principles and requirements for Real Time Management Co-ordination (RTMC).6311.1Principles and requirements for real-time management co-ordination (RTMC).6311.1.1General principles for RTMC.6311.1.2RTMC requirements related to administrative actions.6411.1.2.1General.6411.1.2.2Manipulation of generic administrative state attributes.6511.1.2.3Manipulation of VB5.1 specific state attributes.6611.1.3RTMC requirements related to the occurrence of fault conditions.6611.1.4Verification of LSP ID.6711.1.5Interface reset procedure.6711.1.6VPCI consistency check.6711.1.7Activation/deactivation of B-ISDN accesses under control of the SN.6811.1.8Procedural RTMC requirements.6811.1.9Summary of RTMC functions.6812Performance design objectives.7012.1Performance design objectives for transfer functions.7012.2Performance design objectives for RTMC functions.7013VB5.1 system architecture, structure and procedures.7013.1Introduction.7013.2VB5.1 system architecture.7113.2.1System diagrams.7113.2.1.1SN and AN overview.7113.2.1.2Naming conventions.7113.2.1.3AN VB5.1 system.7213.2.1.4SN VB5.1 system.7513.2.1.5Signallists.7813.2.2Block diagrams.8713.2.2.1System management.8713.2.2.1.1AN system management.8713.2.2.1.2SN system management.8813.2.2.1.3System management internal signallists.8913.2.2.2Resource Management.9113.2.2.2.1AN Resource Management.9113.2.2.2.2SN Resource Management.9313.2.2.3RTMC protocol entity.9513.2.2.3.1AN RTMC protocol entity.9513.2.2.3.2SN RTMC protocol entity.9713.3RTMC procedures.9913.3.1General principles for the RTMC procedures.9913.3.1.1VB5.1 system external events.9913.3.1.2Single VP messages and multi VP messages.9913.3.1.3Acknowledgements.9913.3.1.4Use of transaction identifiers.9913.3.1.5General error handling.10013.3.1.5.1Handling of protocol error conditions.10013.3.1.5.2Error procedures with explicit action indication.10213.3.1.5.3Error in communication with peer network element.10213.3.1.5.4Resources unknown in peer network element.10213.3.1.5.5Requested operation rejected by peer network element.10213.3.2Co-ordination of resource status change procedures.102SIST EN 301 005-1:2000

ETSIEN 301 005-1 V1.1.4 (1998-05)613.3.2.1Block and unblock procedures.10313.3.2.1.1General.10313.3.2.1.2Procedure.10313.3.2.1.3Exceptional procedures.11113.3.2.2Shutting down of resources.11113.3.2.2.1General.11113.3.2.2.2Procedure.11113.3.2.2.3Exceptional procedures.11313.3.3VPCI consistency check procedure.11413.3.3.1General.11413.3.3.2Procedure.11413.3.3.2.1Initiating VPCI consistency check.11413.3.3.2.2Terminating VPCI consistency check.11413.3.3.3Exceptional procedures.11513.3.3.3.1Initiating VPCI consistency check.11513.3.3.3.2Terminating VPCI consistency check.11613.3.4RTMC housekeeping procedures.11613.3.4.1Start-up procedure.11613.3.4.1.1General.11613.3.4.1.2Procedure.11613.3.4.1.3Exceptional procedures.11813.3.4.2Verify logical service port Id procedure.11813.3.4.2.1General.11813.3.4.2.2Procedure.11813.3.4.2.3Exceptional procedures.11913.3.4.3Reset complete logical service port (LSP) procedure.11913.3.4.3.1General.11913.3.4.3.2Procedure.12013.3.4.3.3Exceptional procedures.12113.3.4.4Reset VPC procedure.12113.3.4.4.1General.12113.3.4.4.2Procedure.12113.3.4.4.3Exceptional procedures.12114Message format and codes.12214.1Message and information elements encoding principles.12214.1.1Encoding principles for messages.12214.1.2Encoding principles for information elements.12514.1.3Order of transmission.12614.1.4Coding of extension indicator bit.12614.1.5Coding of integers.12714.1.6Coding of spare bits.12714.1.7Compatibility instruction indicators.12714.1.7.1Regular error handling procedures.12714.1.7.2Procedures with explicit action indication.12714.1.7.2.1Unexpected or unrecognized message type.12714.1.7.2.2Information element errors.12814.2RTMC protocol messages and information elements.12814.2.1RTMC protocol messages for VB5.12814.2.1.1General.12814.2.1.2Messages for co-ordination of resource (un)available state related to service.12914.2.1.2.1BLOCK_RSC message.12914.2.1.2.2BLOCK_RSC_ACK message.12914.2.1.2.3AWAIT_CLEAR message.13014.2.1.2.4AWAIT_CLEAR_ACK message.13014.2.1.2.5AWAIT_CLEAR_COMP message.13114.2.1.2.6AWAIT_CLEAR_COMP_ACK message.13114.2.1.2.7UNBLOCK_RSC message.13114.2.1.2.8UNBLOCK_RSC_ACK message.13114.2.1.3VPCI consistency check messages.13214.2.1.3.1CONS_CHECK_REQ message.132SIST EN 301 005-1:2000

ETSIEN 301 005-1 V1.1.4 (1998-05)714.2.1.3.2CONS_CHECK_REQ_ACK message.13214.2.1.3.3CONS_CHECK_END message.13314.2.1.3.4CONS_CHECK_END_ACK message.13314.2.1.4RTMC housekeeping messages.13314.2.1.4.1LSPID message.13314.2.1.4.2REQ_LSPID message.13414.2.1.4.3RESET_RSC message.13414.2.1.4.4RESET_RSC_ACK message.13414.2.1.4.5PROTOCOL_ERROR message.13414.2.2RTMC function specific information elements.13514.2.2.1General.13514.2.2.2Blocked resource identifier.13514.2.2.3Protocol error cause.13614.2.2.4Repeat indicator.13714.2.2.5Result indicator.13714.2.2.6Resource identifier.138Annex A (normative):SDL process diagrams.140Annex B (normative):UPC and NPC function location.141B.1Introduction.141B.2Location of the UPC function.142B.2.1Location of the UPC (VP) function.142B.2.2Location of the UPC (VC) function.142B.3Location of the NPC function.143B.3.1Location of the NPC (VP) function.143B.3.2Location of the NPC (VC) function.143Annex C (normative):Primitive interface between VB5.1 protocol FSMs and environment.144C.1Introduction.144C.2General definition of the primitive interface.144C.3Primitive interface for the RTMC function.145C.3.1General description for primitives.146C.3.1.1Primitives common for access network and service node.146C.3.1.2Primitives specific for access network.146C.3.1.2.1Primitives for co-ordination of resource status changes.146C.3.1.2.2Primitives for co-ordination VPCI consistency check.147C.3.1.3Primitives specific for service node.147C.3.1.3.1Primitives for co-ordination of resource status changes.147C.3.1.3.2Primitives for co-ordination VPCI consistency check.147C.3.2Description of primitive attributes.148C.3.2.1Resource identifier attributes.148C.3.2.2Result attribute.149C.3.3Mapping between primitives and messages.150C.3.4Creation/deletion of VPC related entities across the primitive interface.151C.3.4.1Creation/deletion of VPC carrying the RTMC protocol.151C.3.4.2Creation/deletion of other VPC entities.152C.3.5Exceptional procedures at the primitive interface.154C.3.5.1General principles.154C.3.5.1.1Transmission error across VB5.1 reference point.154C.3.5.1.2"Resource(s) unknown" at peer network element.154C.3.5.1.3“Operation rejected” by peer network element.155C.3.5.1.4"Operation rejected" by local network element.155C.3.5.1.5“Operation failed” in peer network element.155C.3.5.1.6"LSPID mismatch" detected in local network element.155C.3.5.1.7"SAAL failure" in local network element.155C.3.5.1.8"Not performed" by peer network element.155SIST EN 301 005-1:2000

ETSIEN 301 005-1 V1.1.4 (1998-05)8C.3.5.2Example cases for the above general principles.155C.3.5.3Individual cases for reporting of unsuccessful operations.156C.3.5.3.1Start-up operation.156C.3.5.3.2Verify logical service port Id operation.157C.3.5.3.3Reset resource operation.158C.3.5.3.4Block/unblock resource operation.158C.3.5.3.5Await clear operation.159C.3.5.3.6VPCI consistency check operation.160Annex D (informative):Added value features of VB5.1 interfaces applicable to other VBxinterfaces.163Annex E (informative):Application of the protection facility of SDH on the VB5.1 interface.164Annex F (informative):Examples of physical interface options for the VB5.1 interface.165Annex G (informative):Examples of non-ATM based non-B-ISDN accesses.166G.1Local Area Network (LAN) accesses.
...