Presentation rnc
Download as PPT, PDF1 like332 views
The document describes the internal diagram for RNC connectivity in an MSC network. It explains that path IDs must be the same on the RNC and MSC sides to correlate the route. Each voice channel requires a unique path ID. Virtual paths divide bandwidth into fixed allocated portions, while virtual channels dynamically share bandwidth within a virtual path using a virtual channel identifier. An incident was created to modify the bandwidth and path ID between two nodes due to a mismatch in the path ID.
Presentation rnc
- 2. MSC Internal Diagram for RNC Connectivity.
- 3. The Path ID must be the same as on the RNC side so must be given by CSE. Each VCHAN for traffic needs a different Path ID. Path ID can be correlated as Route Virtual Path: The bandwidth of the transmission path is logically divided into separate virtual paths. Each virtual path is allocated a fixed amount of bandwidth. Virtual paths do not dynamically vary their bandwidths beyond what has been allocated. Virtual Channel The bandwidth of a virtual path is logically divided into separate virtual channels using a virtual channel identifier. Unlike virtual paths, virtual channels share the bandwidth within a virtual path dynamically. R N C M S C Path ID 2 PAthID 3 Path ID 2 Path ID 3
- 4. Path ID 2 Path ID 3 Path ID 2 Path ID 3 R N C M S C R N C M S C Path ID 2 Path ID 3 Path ID 2 Path ID 1 VPI-211 VCI-36 WO- 2394098 has been created to change the Bandwidth from 14KCPS to 9KCPS and to Modify the Path ID from 3 to 1 between 91GABNBU and TSTR22TCW VPI-211 VCI-36 BW-14kcps BW-9kcps As their was mismatch in Path ID which is basically representing Route Created incident