wireless-pr

Signed-off-by: Jason.Ning <njh1195@outlook.com>

wg-wireless/KubeEdge Wireless Working Group Charter.md

+# WG Wireless Charter
+
+
+
+This charter adheres to the conventions described in [KubeEdge Open Governance](https://github.com/kubeedge/community/blob/master/GOVERNANCE.md) and uses the Roles and Organization Management outlined in the governance doc.
+
+## Stakeholder SIG
+
+- SIG MEC
+
+## **Scope**
+
+KubeEdge-Wireless Working group is responsible to simplify, develop, and optimize the wireless communication issues under kubeEdge.
+
+### **In scope**
+
+#### **Areas of Focus**
+
+​	Wireless  technology, Communication mesh technical, multi-access protocol, Invoke the schema on the communication computing topology
+
+- Cloud or edge service quality problems caused by user movement
+- Random off-line issues present new challenges to kubeEdge management in wireless communication. 
+- Optimize the quality of communication under the scenario of side collaboration
+- Proactive changes in communication intensity require decentralized cloud management capabilities.
+
+#### Out of scope
+
+- Do not invent communication protocol.
+
+## **Roles and Organization Management**
+
+This Special working group follows and adheres to the Roles and Organization Management outlined in KubeEdge Open Governance and opts-in to updates and modifications to KubeEdge Open Governance.
+
+## Participate in organization and personnel
+
+- PengCheng Lab,(Tingting Yang, Jiahong Ning)
+- DLMU(Dalian Maritime University, Hailong Feng, Zhengqi Cui)
+- ShanghaiTech University (Yang Yang, LianTao Wu, Dapeng Lan)；
+- Universitetet i Oslo(DaPeng Lan); 
+- SEU(Southeast University, Chengzhuo Han); 
+- SJTU(ShangHai JiaoTong university, Xudong Wang,Jiawei Zhang), 
+- CUCC(China Union Communication Corporation，Gao Chen）

wg-wireless/README.md

+### KubeEdge-Wireless Working Group 
+
+KubeEdge-Wireless Working group is responsible to simplify, develop, and optimize the communication issues under wireless scenario in kubeEdge.
+
+## Stakeholder SIG
+
+- SIG MEC
+
+### **Meeting**
+
+- SIG MEC biweekly meeting: [Fridays at 10:00 GMT+8](https://zoom.us/my/kubeedge) (bi-weekly starts on Friday September 18th, 2020) [Convert to your timezone](https://www.thetimezoneconverter.com/?t=10%3A00 am&tz=GMT%2B8&).
+  - [Meeting notes and Agenda](https://docs.google.com/document/d/1Bg6vnT2anDd8lxX4s05m6--NFzFlQIkpETAljas7MJI/edit#)
+  - [Meeting Calendar](https://calendar.google.com/calendar/u/0?cid=Y19nODluOXAwOG05MzFiYWM3NmZsajgwZzEwOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t) | [Subscribe](https://calendar.google.com/calendar?cid=OHJqazhvNTE2dmZ0ZTIxcWlidmxhZTNsajRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ)
+
+## Contact
+
+- Slack: [#sig-mec](https://kubeedge.slack.com/archives/C0120QT37PD)
+- [Mailing list](https://groups.google.com/forum/#!forum/kubeedge)
+
+This working group currently sponsored by sig-mec with a focus on improving ability of management and developing of kubeedge in wireless scenario.

wg-wireless/whitepapers/Working Group Proposal.md

+KubeEdge-Wireless Working Group Proposal
+
+Author: Jiahong Ning
+
+## **Target:** 
+
+- Our goal is to make an open platform to enable **Wireless**-Edge computing, extending native containerized application orchestration capabilities to hosts at **Wireless**-Edge, which built upon kubernetes and provides fundamental infrastructure support for **Wireless**-network, app deployment and meta-data synchronization between cloud and **Wireless**-Edge.
+- **Extend** KubeEdge to support **wireless mobile scenarios**.
+
+## Overview:
+
+-  With the development of computing and communication technologies, powerful computing equipments constitutes multi-agent systems. The agents have both computing and communication capacities and interact with each others. Therefore, the problem of wireless agents interaction between multiple agents and system management is the main scenario discussed here. 
+- The communication relationship between different Kubeedge nodes can not be easily seen as connect or disconnect,  it should be more fine-grain communication management.
+
+This proposal is about to carry out the wireless network issues under kubeedge management. 
+
+## In scope：
+
+### Areas of Focus
+
+- Cloud or edge service quality problems caused by user movement
+- Random off-line issues present new challenges to kubeEdge management in wireless communication. 
+- Optimize the quality of communication under the scenario of side collaboration
+- Proactive changes in communication intensity require decentralized cloud management capabilities.
+
+### Out of scope
+
+- Do not invent communication protocol.
+
+## Scenario：
+
+**Scenario_1: Vehicle Network/Vessel Network/UAV Network:**
+
+<img src="https://snz04pap002files.storage.live.com/y4m9TFrXL6j2ajyTvHbGHvTWUo5w6kT7SMZ2DZq1t1ivm9Trt4Lo7wt4-azpzI5O746g8fXqBkMz0iweMjyNQdBS4WaXnv5HLtyxU_kHOFNGrEpgfrbocPHwC1Jb6TnskFPTfWwvQUzkhgsz-AoRc1VffTLSUX8klBth8EMHG_KmYO5zoKt_Vpk8XVRDn2UO_-J?width=640&height=397&cropmode=none" width="640" height="397" style="zoom: 67%;" />
+
+**Key differences** between wireless and wire:  
+
+- Communication mode may need to change from TCP, IP mode to multi-cast or broadcast mode.
+- Network for dynamics scenarios.  
+
+**Description**:  In the mobile scenario, multiple vehicles support similar services, and vehicles wireless connected with each other as KubeEdge nodes. 
+
+- Off-line autonomy and node management: Five cars form an mesh network, which can transfer information processing between each other in off-line conditions.
+- Leader selection: Choose a node as a cluster head, to do the overall management of other equipments.
+- KubeEdge-wireless should monitor the whole or partly network status, to aid in networking decisions.
+- According to the Service Level Agreement, KubeEdge can make decisions on the networking modes and limit the network scope.
+- Inspired by 3GPP 36.885 standards.
+
+**Scenario_2: Air/Sea rescue Collaboration：**
+
+<img src="https://snz04pap002files.storage.live.com/y4mJdEgovz7T_GDsALgDPEWrN4MhF1P7MudfdjqUTnhIxMSo5vkqrUdk8NpCFe6ypykfj-c0tXva_S67FrJP0G03ntfE6hptIxSc0d296PTI-WVFY-Sg8BYNN2JO0JuoqMVCSY-ytW43_0gp3FUGYZhaOMPInDR_1gc80DlY7s7vlbVV1dEC4YBnlYYCr3euiTW?width=657&height=362&cropmode=none" width="657" height="362" style="zoom:67%;" />
+
+
+- The environmental complexity of the sea and sky makes communication more difficult.
+- The lack of base station support in this scenario necessitates a change in the communication mode.
+- The search target area is enlarged, but the individual energy is limited, and cluster head is needed for management.
+- It is necessary to study the dynamic network topology to cope with the constantly changing environment of airspace and sea area.
+
+## Proposal:
+
+- KubeEdge has the ability to manager the complex wireless networking status without sensing by service.
+  - Allow users to be compatible with different network connection mode, under plug-in management
+  - With the change of networking modes, the traditional communication modes of KubeEdge need to be extended, such as including broadcast and multi-cast.
+- Optimize the quality of communication under the scenario of side collaboration
+  - Topologies will constantly changing, and the scheduling of communication capabilities will become a critical issue.
+  - Consider the situation of poor network channel quality.
+  - Actively consider the network instability caused by mobility, especial for users joint and exit suddenly.
+  - Active feedback to adjust the network, active networking.
+- Edge nodes have partial cloud capabilities
+
+  - Enable the edge devices to self-organize network and partial autonomy when off-line or discontinuous network. 
+
+  - In most cases, multiple edge devices may spontaneously form a small group, and the outside nodes can join or quit the group.
+
+## Involving technology：
+
+​	Wireless  technology, Communication mesh technical, multi-access protocol, Invoke the schema on the communication computing topology
+
+
+
+
+
+
+
+ 

wg-wireless/whitepapers/scenario.md

+Kubeedge wireless scenario
+
+#### Scenario：
+
+##### 	Vehicle Network/Vessel network/UAV network:
+
+<img src="https://snz04pap002files.storage.live.com/y4m9TFrXL6j2ajyTvHbGHvTWUo5w6kT7SMZ2DZq1t1ivm9Trt4Lo7wt4-azpzI5O746g8fXqBkMz0iweMjyNQdBS4WaXnv5HLtyxU_kHOFNGrEpgfrbocPHwC1Jb6TnskFPTfWwvQUzkhgsz-AoRc1VffTLSUX8klBth8EMHG_KmYO5zoKt_Vpk8XVRDn2UO_-J?width=640&height=397&cropmode=none" width="640" height="397" />
+
+**Key differences** between wireless and wire:  
+
+- Communication mode may need to change from TCP, IP mode to multi-cast or broadcast mode.
+- Network for dynamics scenarios.  
+
+With the development of computing, powerful computing equipment could be seen as multi-agent. Therefore, the  problem of wireless interaction between multiple agents is the main scenario discussed here. 
+
+**Description**:  In the mobile scenario, multiple vehicles support similar service, and each vehicles wireless connected with each other as a KubeEdge node. (e.g. NIO ET7 with NVIDIA Orin * 4 , which has computing power of 1016 TOPS)
+
+- Off-line autonomy and node management: Five cars form an mesh network, which can trans information processing between each other in off-line conditions.
+- Leader Selection: Choose a Kube as cluster head, to do the overall management of other equipments.
+- KubeEdge-wireless should monitor the whole or partly state of network, to aid in networking decisions.
+- According to the Service Level Agreement, KubeEdge makes decisions on the networking mode and limits the networking scope.
+- Inspired by 3GPP 36.885 standards.
+
+
+
+##### **Air/Sea rescue Collaboration：**
+
+<img src="https://snz04pap002files.storage.live.com/y4mJdEgovz7T_GDsALgDPEWrN4MhF1P7MudfdjqUTnhIxMSo5vkqrUdk8NpCFe6ypykfj-c0tXva_S67FrJP0G03ntfE6hptIxSc0d296PTI-WVFY-Sg8BYNN2JO0JuoqMVCSY-ytW43_0gp3FUGYZhaOMPInDR_1gc80DlY7s7vlbVV1dEC4YBnlYYCr3euiTW?width=657&height=362&cropmode=none" width="657" height="362" />
+
+- The environmental complexity of the sea and sky makes communication more difficult
+- The lack of base station support in this scenario necessitates a change in the communication mode.
+- The search area is enlarged, but the individual energy is limited, and cluster head is needed for management.
+- It is necessary to study the dynamic network structure topology to cope with the constantly changing environment of airspace and sea area.
+
+