MEF
The MEF is a major industry body with 210+ members of which 130+ are service providers from around the globe. MEF's membership has developed the Carrier Ethernet market from zero in 2001 to an $80Bn market (Source: IHS Markit) today.
Opportunities for Students and Graduates
The MEF is offering unique opportunities to students and graduates to participate in ongoing software and modelling projects that will have profound and immediate impact on the connectivity and cloud services industry. These projects involve many of the MEF's member companies including major global service providers and technology providers, and touch on the latest in standards work including LSO, SDN and NFV.
Interested students, graduates and academic institutions should contact Daniel Bar-Lev.
Click on graphic to enlarge
Projects for Students
These projects can be integrated into one semester university projects for undergraduates with the backing of the student's university or similar academic institution.
JIRA is used to scope out the project for development work in agile methodology (e.g. sprints) and to track the achievements of individual students in such a way that supervisors can assess their success.
All contributions of code by students are under Apache 2.0 licensing (see Code Contribution Agreement)
Current Development Opportunities
- Rules engine development (i.e., MEF 10.3; MEF 26.1; MEF 45) for service decomposition.
- Path computation and path selection using graph theory applied to development of Topology Engine.
- Data science/engineering applied to Inventory Engine and data analytics for SLAs, etc.
- Pub/Sub pattern applied towards fault and performance management.
- Develop micro-services on the LSO Innovation Platform for functional blocks within SOF.
Typical Requirements for Software Developers
The following highlight the backgrounds required and preferred to participate in the projects listed below. Note that some requirements relate only to specific projects.- Studying Information or Computer Science, Telematics, Networking, Internet or Web Engineering
- Practical experience in developing sofware in Java 8
- Prior knowledge of tools like Spring Boot and implementation approaches like Micro-Services
- At least basic knowledge of networking (e.g. Carrier Ethernet, IP, MPLS etc.)
- UML and/or YANG modeling experience
- HCI or User Interface design experience
- Preferred: Familiarity with MEF terminology and specs
- Preferred: Experience working with Open Source projects (e.g. OpenStack, OpenDaylight, OPNFV, ON.Lab)
- Preferred: Experience using OpenStack solutions
Key Topics
- Path computation and path selection using graph theory applied to development of Topology Engine.
- Data science/engineering applied to Inventory Engine and data analytics for SLAs, etc.
Introduction
- Hadoop
- Kafka
- Node.js (Orchestrator)
- GraphDB
SOF Blocks
- Service Orchestration Functionality (SOF) receives a MEF Service Activation request from BSS/OSS (LSO Legato client).
- SOF decomposes the service and passes the service graph to the Path Computation functional block.
- Path Computation functional block determines the underlying network graph that will meet the service connectivity request.
- Included in the Path Computation functional block is a Path Selection sub-component.
- The network graph is passed to Design & Assign functional block which is responsible for determination of each LSO Presto invocation necessary to stitch the network path.
- ICM functional block is responsible for determination of Domain Controller responsible for each LSO Presto ConnectivityService segment.
- LSO Presto Client invokes the one or more activation requests over the LSO Presto interface.
Additional Projects
Inter-Carrier Serviceability
Developers will write code in sprints defined and led by MEF member companies that will implement business requirements and processes defined by Service Provider MEF members for checking serviceability of wholesale services (e.g. E-Access and E-Transit) in an M2M environment across open APIs defined by the MEF at LSO Sonata and LSO Interlude.
Inter-Carrier Product Ordering
Developers will write code in sprints defined and led by MEF member companies that will implement business requirements and processes defined by Service Provider MEF members for ordering of wholesale services (e.g. E-Access and E-Transit) in an M2M environment across open APIs defined by the MEF at LSO Sonata and LSO Interlude.
Inter-Carrier Product Activation and Configuration
Developers will write code in sprints defined and led by MEF member companies that will implement business requirements and processes defined by Service Provider MEF members for activation and configuration of wholesale services (e.g. E-Access and E-Transit) in an M2M environment across open APIs defined by the MEF at LSO Sonata and LSO Interlude .
Inter-Carrier Invoicing
Developers will write code in sprints defined and led by MEF member companies that will implement business requirements and processes defined by Service Provider MEF members for invoicing (including billing) of wholesale services (e.g. E-Access and E-Transit) in an M2M environment across open APIs defined by the MEF at LSO Sonata and LSO Interlude.
Inter-Carrier Assurance
Developers will write code in sprints defined and led by MEF member companies that will implement business requirements and processes defined by Service Provider MEF members for all aspects of service assurance (e.g. trouble ticketing) of wholesale services (e.g. E-Access and E-Transit) in an M2M environment across open APIs defined by the MEF at LSO Sonata and LSO Interlude.
Inter-Carrier Security
Developers will write code in sprints defined and led by MEF member companies that will test the vulnerability of open APIs defined by the MEF at the M2M interfaces between Carriers.
Intra-Carrier Network Data Collection
Developers will write code in sprints defined and led by MEF member companies to collect data from networks based on different technology domains (e.g. CORD, Packet WAN, Optical Transport, 5G, SD WAN) for use in assessing the performance of the network as defined in MEF specifications (e.g. MEF 30.1, MEF 35.1)
Inter-Carrier Network Data Collection
Developers will write code in sprints defined and led by MEF member companies to collect data from wholesale Operators for use in assessing the performance of the wholesale service as defined in MEF specifications (e.g. MEF 30.1 , MEF 35.1)
LSO Orchestratable SDN Controllers
Developers will write code in sprints defined and led by MEF member companies to enable SDN Controllers (e.g. OpenDaylight, ONOS, OpenContrail) to be orchestrated via open APIs at LSO Presto (i.e. develop LSO Presto plugins for Open Source controllers)
LSO Orchestratable NFV Orchestrators
Developers will write code in sprints defined and led by MEF member companies to enable NFVOs to be LSO orchestrated (e.g. OPNFV MANO, ETSI MANO)
User Portal
Developers will write code in sprints defined and led by MEF member companies to be used in sample user portals to manage MEF-defined services via open APIs the fulfillment and control phases of a service lifecycle.
DRAFT