Use Case Contacts Info in Guilin release
Lead contacts for each contributing organization
Company | Name | |
---|---|---|
CMCC | @LIN MENG | |
Wipro | @Swaminathan Seetharaman | |
Huawei | @Henry Yu @wangyaoguang | |
TIM | @Alessandro D'Alessandro | |
Tech Mahindra | @Milind Jalwadi (Unlicensed) | |
Amdocs | @Borislav Glozman | |
IBM | @Sandeep Shah | |
LTTS | @Sudarshan KS |
Track Leads
Track | Name(s) | |
---|---|---|
Frankfurt Improvements | @Zhang Min @Swaminathan Seetharaman | |
RAN Slicing | @Swaminathan Seetharaman @Shankaranarayanan Puzhavakath Narayanan @wangyaoguang (External RAN NSSMF) | |
Core Slicing | Milind Jalwadi | |
Transport Slicing | @Henry Yu @LIN MENG | |
Standardization of external interfaces | @Swaminathan Seetharaman | |
KPI Monitoring | @LUKAI | |
Closed Loop | @Swaminathan Seetharaman @LIN MENG | |
Intelligent Slicing | @LIN MENG @Swaminathan Seetharaman | |
Modeling | @guochuyi |
Use case team members and contacts (functional requirements)
Note: For team members contributing to the non-functional requirements, please refer Non-functional requirements contribution in Guilin.
Bold indicates main module responsibles.
Name | Organization | Track(s) | Component(s) | Location | Remarks | |
---|---|---|---|---|---|---|
@Zhang Min | CMCC | Frankfurt improvements, Common NSMF | SO | Beijing, China | Also NSSMF adaptor common part | |
@HeTengjiao | CMCC | Frankfurt improvements, Common NSMF | SO | Beijing, China | Also NSSMF adaptor common part | |
@xu ran | CMCC | Frankfurt improvements, KPI Monitoring | U-UI | Beijing, China | ||
@Keguang He | CMCC | Frankfurt improvements | SDC, | Beijing, China | ||
@Keguang He | CMCC | KPI Monitoring | U-UI | Beijing, China | ||
@guochuyi | CMCC | All | Modeling | Beijing, China | ||
@LUKAI | CMCC | KPI Monitoring | DCAE | Beijing, China | PM Mapper MS, DES MS | |
@Ahila P | Wipro | RAN Slicing, Closed Loop, Intelligent Slicing | CCSDK/SDN-R | Chennai, India | Including Config DB | |
@dhebeha mj | Wipro | Frankfurt Improvements, RAN Slicing | OOF | Chennai, India | ||
@dhebeha mj | Wipro | Closed Loop | DCAE | Chennai, India | Slice Analysis MS | |
@krishna moorthy | Wipro | Frankfurt Improvements, RAN Slicing | OOF | Chennai, India | ||
@krishna moorthy | Wipro | Closed Loop Control, Intelligent Slicing | Policy | Chennai, India | Control Loop related updates | |
@Priyadharshini B | Wipro | Frankfurt Improvements, RAN Slicing, Closed Loop & Intelligent Slicing | SO | Bangalore, India | Common NSSMF, RAN NSSMF, NSMF improvements | |
@Priyadharshini B | Wipro | Standard Interfaces | ExtAPI | Bangalore, India | TMF 641 enhancements | |
@Reshmasree c | Wipro | Frankfurt Improvements, RAN Slicing, Closed Loop & Intelligent Slicing | SO | Bangalore, India | Common NSSMF, RAN NSSMF, NSMF improvements | |
@Reshmasree c | Wipro | Closed Loop, Intelligent Slicing | DCAE | Bangalore, India | Slice Analysis MS | |
Henry Yu | Huawei | Transport Slicing | SO | Ottawa, Canada | TN NSSMF | |
Henry Yu | Huawei | Transport Slicing | AAI | Ottawa, Canada | TN NSSI (TSCi) model Transport End point model | |
@Hesam Rahimi | Huawei | Transport Slicing | CCSDK/SDN-C | Ottawa, Canada | CCVPN/ACTN implementation/ realization of Transport Slicing on SDNC | |
@Sithara Nambiar | Huawei | Frankfurt improvements | OOF | Bangalore, India | NST Selection | |
@wangyaoguang | Huawei | RAN Slicing: (External) RAN NSSMF interaction | SO | Beijing, China | ||
@Enbo Wang | Huawei | RAN Slicing: (External) RAN NSSMF interaction | SO | Beijing, China | ||
@Borislav Glozman | Amdocs | All | Modeling | Israel | ||
@Aleem Raja | Tech Mahindra | Core Slicing | SO | Pune, India | Core NSSMF | |
Alexander Borovitsky | TIM | Core Slicing | SO | Israel | NSSMF, NSMF, Adapter for 5G Core | |
@Former user (Deleted) | TIM | Core Slicing | CDS | Torino, Italy (UTC + 2) | ||
@Alessandro D'Alessandro | TIM | All | Modeling | Torino, Italy (UTC + 2) | ||
@Sandeep Shah | IBM | RAN Slicing, Closed Loop | CCSDK/SDN-R | CT | Including Config DB | |
@praveen v | LTTS | Core Slicing, Closed Loop | Core NF Simulator | Bangalore, India | ||
@Naveen S Sankad | LTTS | Tracking and following in this release | SO | Bangalore, India |
|