My Wiki!

Table of Contents

2015-12-17

new things in 5G

til the end of project:

  • 1,2 IPRs event NFV, SDN not necessarily mobility management.
  • implementation

HW review 2015-11

  • deliverable, slide, discussion,
  • 5 papers & 1 patent
  • Reactive to proactive: showing performance b/w the 2 cases
  • proactive with multicast (candidate cluster)

Pattern

  • 2 slides why doing this
  • few what are the inventions?
  • all in all 10-13

Split ipr idea to 2 patents: 1) extension of OF for measurements (good reason), 2) the algorithm why the rule is there (learning),

Discuss Mcast solution: what happen with packets when MH is not attached? need to justify this.

ipr: there is work around? connecting AP with SW! so drop the patent idea. Focus on create new interface.

new Zoran ipr idea:

The OpenFlow channel is the interface that connects each OpenFlow Logical Switch to an OpenFlow controller. Through this interface, the controller configures and manages the switch, receives events from the switch, and sends packets out the switch. The Control Channel of the switch may support a single OpenFlow channel with a single controller, or multiple OpenFlow channels enabling multiple controllers to share management of the switch. –

> opposite to this.

idea: outport aggregation.

idea: multicast

idea: Zoran, implement SW to SW flow modification –

> good paper, OF extension. target SIGCOM

idea: Thuy, handover table

—

> these 3 ideas to paper or patent, implement and evaluate the solutions.

–

> Implement multicast

—

> demo, papers, patent. For next year.

HW MoM

Discuss IPR

Z: what we should do? high level comment, should not talk about internal of KME, CCE. Focus on something new, does not exist. 2 options for invention. 1) how to get information from SDN devices to the controller, e.g., X2 interface. How to get information without interfering handover. Specify protocol to communicate, update status data beyond Openflow. E.g, extend OF, look for new fields 2) We use OF to proactive send flow to devices, as method invention. How we use the context information to calculate flow. This need much details.

Z: Slide 15 starting point to work towards OF extension. Specify how the communication is possible, what extension is needed (new).

CM: If KME, CCe are in control plane, co-located with SDN Controller, specify their communication. Using OF and extension of OF.

M: take aways: look into extension of OF, details all communication with OF.

Z: One possibility. Store rules on neighbouring switch, when the node moves, the rules are sent to previous node to change data flow. Using Ap-AP communication, to forward flows to future mobile node.

Experiment discussion.

MK: we put the experiment as living document so we both can work together on the experiment.

Survey

CM: will update the document next week.


Trace: • ndn • paper_idea • f2f_10062016 • sdn_nfv • cafe_berlin • microservices • mount_lvm • dtn2_src_walk • 0_proposal_forming • mom

Navigation
Toolbox