Page History

...

• OEM Device or SoC reference device should boot with Kernel & all required drivers should load & we should be in a position to login to shell

Roles & Responsibilities of each team to deliver EasyMesh AP solution to ISP's

• ISP's
  • Define RFP with all requirements to SoC and OEM's
• SoC Vendor
  • Deliver Base Kernel & Drivers to OEM
• OEM
  • Integrate SoC Kernel & drivers
  • Customization of drivers if required
  • OSS component Integration
  • Onewifi integration
  • EasyMesh Agent integration
  • IEEE1905 Integration
  • Developer testing 
  • Deliver working EasyMesh AP profile to ISP 
    • Agent device should onboard to gateway as Star
    • Agent device should onboard to Agent device in Daisy chain
    • There need to be a single EasyMesh Agent in Gateway as well as Agent profile
    • CAPI integration
    • EasyMesh Precertification
    • Easymesh R6 certification 
• ISP's
  • Principal engineer reviews test results and code base (Kernel,Drivers,HAL,EasyMesh,Onewifi,rdk-wifi-hal,hostap,etc)shared by OEM
    • Build the code
    • Validate the code and make sure all fundamental use cases work
    • Deliver the standard image with Dev testing team
  • Dev test team do end to end validation of image and share feedback with principal engineer
  • Principal engineer review feature with wifi architect & Product architect.
    • Compare with product requirement
    • Compare with architecture requirements
    • Discuss and security related items
    • Review against RFP requirements.
  • Share feedback with OEM if any.
  • Share additional requirements with OEM if they want to implement any ISP specific features
  • Core wifi team need to handle ISP specific changes on easymesh repo and maintain a local patch or if its enhancement as per spec,contribute back to RDK
• System Integrators
  • Get in sync with ISP/OEM/SoC
• App vendors
  • Closely work with ISP and their associated SoC and OEM

How does it serve community

...