Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
Track | Details | Impacted Component(s) | Companies | Priority |
---|
Guilin functional enhancements | Completion of remaining Integration Tests, fixing of related bugs (across all tracks) - Service & Slice Profile related enhancements
- Interface between NSMF and NSSMF (modifyNSSI, no NSST info for allocateNSSI, etc.)
- UUI enhancements for TMF 641 API support
- coverageArea to TA list mapping
| UUI, SO, OOF, SDN-C/CCSDK, DCAE, Policy, ExtAPI | CMCC, Wipro, Tech Mahindra, TIM, Huawei, LTTS | 1 |
| Endpoint related enhancements | UUI, SO, OOF, SDN-C/CCSDK | CMCC, Wipro, Tech Mahindra, TIM, Huawei | 1 |
| 3GPP API alignment, modeling enhancements |
|
|
|
RAN Slicing | - Preparation phase, involving RAN NF instantiation and onboarding
- Configuration of RAN NFs over standard O1 - will depend on availability of info models from O-RAN
- A1 interface for Closed Loop and Intelligent Slicing
- Slice assurance use cases - this needs to be evaluated further.
- Endpoints and transport connectivity related aspects, for e.g., parameters required to be passed to TN NSSMF (how they shall be determined), MP to MP connection, etc.
- TA ↔ cell mapping
|
|
|
|
Core Slicing |
|
|
|
|
Transport Slicing | - Endpoints and transport connectivity related aspects, for e.g., parameters required to be passed to TN NSSMF (how they shall be determined), MP to MP connection, etc.
- Transport NSSI selection and reuse
|
|
|
|
Standards Alignment |
|
|
|
|
KPI Monitoring | - TMF 628 implementation
- PM-mapper/new MS with all required functionality
|
|
|
|
Closed Loop | - Closed Loop involving RAN and Core
|
|
|
|
Intelligent Slicing | - Closed Loop involving RAN and Core
- Split intelligence, with guidance coming over A1
|
|
|
|
Modeling enhancements | - Support for both options
- RAN service design enhancements
- Endpoints
- Service and Slice Profiles
|
|
|
|