Overview | Features | Aricent Deliverables | FAQ

Q1. What is VB5 ?
Q2. What is VB5 reference configuration ?
Q3. Why is VB5 required ?
Q4. What are the VB5 specifications available from standards body ?
Q5. What are the advantages of VB5 interface ?
Q6. What are the key features of VB5 ?
Q7. What are the typical VB5 applications ?
Q8. Show me where and how VB5 fits in the network ?
Q9. What is the VB5 target segment ?
Q10. I have got V5 on my system. Does VB5 support V5 services ?

Q11. What are the Aricent VB5 products ?
Q12. What are the Aricent related products ?
Q13. What are the deliverables with each product ?
Q14. What are the advantages of Aricent VB5 solution ?
Q15. What are the Aricent differentiators ?
Q16. What are the features of Aricent VB5 product family ?
Q17. Show me a typical connection establishment scenario after VB5 is inducted in the network ?
Q18. What is the testing strategy followed for Aricent VB5 stack product ?
Q19. What is testing for functionality not covered by the ATS ?

Ans: VB5 Interface specifies the physical, procedural and protocol requirements for interfaces at the reference point between Access Network (AN) and Service Node (SN). The VB5 specification is split into two types.

VB5.1 provides for VPC's and VCC's provisioned in the Access Network via the Q3 management interface by using Real Time Management Coordination (RTMC) protocol. RTMC protocol is used to communicate management information about resources in real time across VB5 interface between Access Network (AN) and Service Node (SN).

VB5.2 adds to VB5.1 the ability of the associated Service Node to allocate AN resources on demand via a Broadband Bearer Channel Connection (B-BCC) protocol. B-BCC protocol is used for dynamic allocation of resources in AN under the control of SN.

-Top-

Ans: VB5 reference configuration (from ITU-T G.982) to position SNI interface in Broadband Network is shown in the figure below.

Ans: The evolution of VB5 standards indicates the natural progression in the broadband network design, just like the narrow-band case wherein the user interface terminates on an AN (Access Network) instead of a LE (Local Exchange) directly. With the definition of the VB5 interface, UNIs will now terminate on the AN instead of directly terminating on the SN (Service Node).

-Top-

Ans: VB5 interface is a recommended standard by ITU-T, ETSI, FSAN, MSF and DAVIC bodies as a standard broadband network interface between Access Network and Service Node.

• ITU specs - G967.1 -- V-Interfaces at the Service Node (SN) - VB5.1 Reference Point Specification
• ETSI specs - EN 301 005 -- V-Interface at the VB5.1 reference point for the support of broadband or combined narrowband & broadband Access Networks (AN)
• ITU specs - G967.2 -- V-Interfaces at the Service Node (SN) - VB5.2 Reference Point Specification
• ETSI specs - EN 301 217 -- V-Interface at the VB5.2 reference point for the support of broadband or combined narrowband & broadband Access Networks (AN)
• ITU specs - Q.832.1 -- VB5.1 Management
• ITU specs - Q.832.2 -- VB5.2 Management and Broadband Access Coordination

Ans: Advantages of VB5 interface are:

• Allow the AN to multiplex/de-multiplex user signalling and data streams from several UNIs in a cost effective manner.
• Allow network management of Access Network via Q3 interface
• Administration of resources in access network
• Maintenance of resources in access network
• Allow user selection of the Service Node
• Allow dynamic allocation of bandwidth on demand
• Effective usage of bandwidth available

-Top-

Q.6 What are the key features of VB5 ?

Ans: Key features of VB5 are:

• ATM based
• Transmission Layer independent
• SN is aware of AN resource un-availability at run-time
• AN is transparent to user signalling
• Enables user access to multiple SN's on a single UNI
• Provides standardized method of carrying integrated narrowband traffic at the SNI.
• Supports B-ISDN Services, Non B-ISDN ATM based services and narrowband services via V5.1/V5.2.
• Enables concentration at the UNI and SNI on a connection by connection basis (on demand) making efficient use of AN resources. (only for VB5.2)

Ans: The typical applications of VB5 are:

• IP Router
• ATM VC switch
• Fiber To The Home (FTTH) / Fiber To The Curb (FTTC) / Fiber To The Building (FTTB)
• Video on Demand (VOD)
• Switched Video Broadcasting (SVB)
• VP leased line

-Top-

Q.8 Show me where and how VB5 fits in the network ?

VB5.2 Interface Diagram

-Top-

Q.9 What is the VB5 target segment ?

Ans:

• Small and Medium OEMs for FTTx, Switched Video Broadcasting (SVB), Video On Demand (VOD)
• Large OEMs for their access products
• T & M (Test and Measurement) OEMs with products in telecom segment
• Private operators in new markets

Ans: At present, the narrowband services such as PSTN, ISDN-BA and ISDN-PRA are the predominant service offerings by the telecommunications operators. The services to be supported across the VB5 reference point include all those supported by V5.2 with the addition of symmetrical and assymetric broadband services, broadcast services, and a LAN interconnect function.

Narrowband services should be carried over a VB5 reference point using the V5.1 and/or V5.2 formatted structures based on 2Mbit/s links. Narrowband services should be provided in 2Mbit/s blocks corresponding to the V5 transmission link data rate using AAL1 as the method of transferring this CBR across an ATM system.

-Top-

Ans: The following products are already available:

• VB5.1 Protocol Stack for Access Network
• VB5.2 Protocol Stack for Access Network
• VB5 Abstract Test Suites for AN for VB5.1 & VB5.2: ETSI TSS & TP 301 105 - 3 is a subset of this. It includes test specifications for redundancy, statistics, provisioning and for VB5.2 protocol stack also.
• VB5.1 Protocol Stack for Service Node
• VB5.2 Protocol Stack for Service Node
• VB5 Abstract Test Suites for SN for VB5.1 & VB5.2
• VB5-AN Application
• Equipment Manager
• Resource Manager
• The following products are on-going:
• VB5-SN Application
• Equipment Manager
• Resource Manager

The following products are planned and are in Aricent roadmap:

• VB5-Q3: It shall provide the complete VB5 solution including VB5 Manager, Agent, Application and protocol stack
• VB5 Test and Measurement : Aricent shall work with Test and Measurement manufacturers to provide the VB5.2 monitor, VB5.2 emulator and VB5.2 simulator functionality

-Top-

Q.12 What are the Aricent related products ?

Ans:

• Signaling ATM Adaptation Layer
• V5.2 Protocol Stack (AN & LE)
• UNI Signaling Protocol Stack ( ITU - Q.2931 / ATM forum UNI 4.0)

Ans: Each product is available with the following deliverables:

• Source Code in C language for RTMC System Management, RTMC Resource Management, RTMC protocol entity, B-BCC Management, B-BCC Connection Management and B-BCC Protocol entity (In case of VB5.1, only RTMC System Management, RTMC Resource Management, and RTMC protocol entity) for VB5 Protocol Stack product
• Protocol Implementation Conformance Statement (Specifications)
• Application Programmer's Interface (API)
• User manual with illustrative examples

-Top-

Q.14 What are the advantages of Aricent VB5 solution ?

Ans: Aricent VB5.2 stack ensures performance and conformance right from the very beginning. It brings

• Reduction of lead time by at least 50%
• Availability of VB5 experts for training or consultancy
• Complete VB5 solution including Q3 management support
• Availability of Aricent infrastructure for integration and testing

Ans:

• Complete VB5.2 Offering
• On-site consultancy and turnkey development models
• Expertise in all aspects of telecom and datacom
• Lower Cost
• Flexible Payment Terms

-Top-

Q.16 What are the features of Aricent VB5 product family ?

Ans: The key functionalities can be briefly listed as follows:

• The stack (and each constituent entity) provides the functionality for handling one or more than one VB5.x interfaces
• The complete VB5.2 protocol stack is capable of execution on a multi-processor target environment by distributing various entities across various subsystems
• Each stack entity is capable of execution in a multi-tasking or single thread of control operating environment
• The message processing is done under entity's own thread of control. There is a minimal real-time overhead on the calling application's thread of control
• There is single entry point for
  
  • Message delivery from the call control application or the peer VB5 entity
  • VB5 Core Engine, which parses and processes the message and updates the finite state machine (FSM), whenever required
    
• Communication between a stack entity and the system is through the invocation of clearly defined Application Programmer's Interface (API). It is possible to port the APIs to a message based or function based interface
• Porting on a new platform requires changes to a few, clearly identified modules.
• The stack and each of its constituent entity can be ported on platforms with redundancy for the processor cards

-Top-

Q.17 Show me a typical connection establishment scenario after VB5 is inducted in the network ?

Ans: The following figure shows a successful connection establishment scenario where user connected to AN is originating a call.

-Top-

Q.18 What is the testing strategy followed for Aricent VB5 stack product ?

Ans: One of the key elements of the Protocol Development Framework is the four-step testing strategy to ensure delivery of reliable, error-free code which functions as per the specified standards. The four steps involved in testing are

• Code Unit Testing
• Conformance Testing using the standards specified Abstract Test Suite
• Enhanced testing for functionality not covered by the ATS
• Sample port on few targets and run-time optimisation

-Top-

Q.19 What is testing for functionality not covered by the ATS ?

Ans: There are several aspects of the VB5 product, which can not be tested just by executing the ATS. In this testing step, the stack is ported on a system, available in-house in the lab and tested for the following functions

• OS failure and error handling
• Stack initialisation and provisioning failure
• Testing for Statistics and Trace functionality
• Integration and testing of the support for redundancy
• Multiple VB5 interfaces
• Graceful recovery
• Testing of a full connection establishment scenario

-Top-

Last updated : March 9, 2006