Upload
marko-palola
View
1.048
Download
3
Tags:
Embed Size (px)
DESCRIPTION
The CORE trial environment provides functions such as obtaining knowledge, making decisions and adjustments on the system under cognitive control. The trial environment provides a cognitive engine for decision making, a WWW browser user interface and CORE tools for collecting knowledge and making adjustments. See http://core.willab.fi for more information
Citation preview
Cognitive Trial Environment
CORE Workshop 15.1.2013Marko PalolaVTT Technical Research Centre of Finland
221/03/2013
15.1.2013 Marko Palola, VTT
2
CORE project 2011-2014
Develop and deploy future CR business ecosystem techniques
Develop a cognitive trial system for carrying out experiments
Make proof of concept trials and measurements
VTT, Centria, CWCNSN, EXFO Nethawk, EB, Pehutek,
PPO, Renesas, Finnish Defence Forces
TEKES Trial [email protected]
321/03/2013
15.1.2013 Marko Palola, VTT
3
Cognitive Radio Systems
“A radio system employing technology that allows the system to obtain knowledge of its operational and geographical environment, established policies and its internal state; to dynamically and
autonomously adjust its operational parameters and protocols according to its obtained knowledge in order to achieve predefined
objectives; and to learn from the results obtained.”
REPORT ITU-R SM.2152
421/03/2013
15.1.2013 Marko Palola, VTT
4
Cognitive Radio Systems
Enabler for next generation, dynamic spectrum access networks
Use or share the spectrum in an opportunistic manner
Power consumptionBest connection
Load balancing
Networkoptimisation
Networkreconfiguration
Resource sharing
521/03/2013
15.1.2013 Marko Palola, VTT
5
Cognitive Cycle realisation in the CORE project 1/2
Collection of network information,
user QoS, userlocation, and radio
resource data.
General approach for
decisionmaking based
on data
Resource loadbalansing
adjustments.
Internal stateis specified bythe collected
data
Generalizedimplementation
621/03/2013
15.1.2013 Marko Palola, VTT
6
Cognitive Cycle realisation in the CORE project 2/2Obtaining knowledge & Adjustments
CORE Client toolsCORE Cognitive APICORE Cognitive Manager
Decision makingData cache & historyCognitive EngineDecision algorithm
Trial AccessCORE Trial Environment UserInterface
721/03/2013
15.1.2013 Marko Palola, VTT
7
Trialing with CORE
CORE trial environment allows integrating an external system undercognitive engine control.
Requires installing/development of Core Client tools for informationcollection and making adjustmentsDuring trial Trial customer is able to
make decision rules based on collected data that change the behaviour of the external systemUse and measure the external system
821/03/2013
15.1.2013 Marko Palola, VTT
8
Obtaining Knowledge & Making changes
Core Clients interface the externalsystem, which may consist of
Computer, terminal, sensorServer, router, base station, switchSimulator, measurement or monitoringtoolDatabase, file, socketService platformAny equipment that can be monitored
921/03/2013
15.1.2013 Marko Palola, VTT
9
Obtaining Knowledge & Making changes
Core Clients monitor / receive information fromexternal system
Produce data for decision making using CORE data format
Data delivery as soon as information is changedPeriodical status (refresh current state)
Core Clients are information collectors
1021/03/2013
15.1.2013 Marko Palola, VTT
10
CORE data formatCORE uses the following data presentation format
component.parameter = value;
Examples:
basestation.load = high;basestation.load=88;network.available=wlan1;network.current=centria_lte;
Names and values can be freely selected.
Cognitive engine follows values and changes related to user, terminal, network, server, service, and basestation components.
1121/03/2013
15.1.2013 Marko Palola, VTT
11
Event message
Core clients deliver collected information to their associated CE for decisionmaking using an event message specified by Cognitive API.
Who/wherecollected
information
Related to what?
How long data is usable? Data
component.parameter = value;
References: 4Ward, Univerself, Future Internet, Mercone…
1221/03/2013
15.1.2013 Marko Palola, VTT
12
Obtaining Knowledge & Making changes
Core clients implement routine that makechanges to external system.
Core clients inform the cognitive engine whatthey can do
A core client’s capabilityactivated by the cognitive engine
CORE project have developed capabilities for Handover capability
Offloading, load balansingWARP radio network channel management
channel occupancy information
Core Clients configure the external system
1321/03/2013
15.1.2013 Marko Palola, VTT
13
Decision making in CORE
Cognitive engineRule-based decision making (if .. then ..)Decision rules
Decisions are based on Data on incoming event messageEarlier received data (cache)
Decision rules can be defined by the Trial customer.
1421/03/2013
15.1.2013 Marko Palola, VTT
14
Decision algorithm
A bunch of decision rules, each rule hasRequirement(s) Capability action
Requirement is tested each time new data event arrives on the decision engine
Capability action is defined by a core client
If requirements are all true the capability action is activated ->an event is sent to the associated core clients
1521/03/2013
15.1.2013 Marko Palola, VTT
15
Decision Rule: Requirements
Requirement is a conditional clause formatted as followscomponent.parameter<operator>value;
Component is a text containinguser, terminal, network, service, basestation or free text
Parameter is a text such as
name, location, id, user, terminal, network, delay, throughput, ..
Operator is !=, ==, >, < , inc, not
Value is a number or text
Example: network.downlink>21.5; network.downlink=low;
1621/03/2013
15.1.2013 Marko Palola, VTT
16
Decision Rule: Capability action
Capability can be defined by1) Event component.action(value);2) Event/value;component.action(value);3) Event component.parameter=value;
In 1) and 3) the capability action is sent as it is declared to the interestedparties.In 2) the cognitive engine will seek for value from the data cache and set the value inside the ().
For example: HandoverEvent/network.available;handover.to(network.available);May result the following (depending on the network.available known by CE)
HandoverEvent handover.to(wlan1);
1721/03/2013
Cognitive API – event formats
• Data and other control information
• Information routing
• Control who access what
• Animation purposes
References: 4Ward, Univerself, Future Internet 1-2, …
1821/03/2013
15.1.2013 Marko Palola, VTT
18
CORE general architecture
1921/03/2013
15.1.2013 Marko Palola, VTT
19
Examples of Core Clients developed in CORE project
Handover / Data offloadingHandoverCoreClientNetshCoreClient
QoS measurement data collectionQosmetCoreClient
User location in LTE networkLteCoreClient
WARP radio resource managementWarpCoreClient
2021/03/2013
15.1.2013 Marko Palola, VTT
20
HandoverCoreClient
External systemBirdstep SafeMoveapplicationVTT’s Mobile IP serviceSeamless handover
HandoverCoreClientCurrent networkAvailable networkHandover capability
3G/4G-WLAN-LANLeave network
2121/03/2013
15.1.2013 Marko Palola, VTT
21
HandoverCoreClient
External systemnetshipconfig
Core ClientCurrent networkAvailable networkHandover capability
WLAN-WLAN4G/3G-WLAN-LANLeave network
Example information and capability definitions for handover core clients:
NetworkFoundEvent network.current=LocalAreaConnection;NetworkFoundEvent network.available=panoulu;
HandoverEvent/network.available;handover.to(network.available);HandoverEvent handover.to(wlan1);HandoverEvent handover.away(panoulu);
2221/03/2013
15.1.2013 Marko Palola, VTT
22
QoS information collection for decision making
External system:Qosmet QoS measurement systemhttp://www.cnl.fi/qosmet.html
QoS measured for both directions between the measurement points for selected data flow.
QoS reported every second
QosmetCoreClient:
• Monitors measured QoS data for changes-> send message for decision making
• Configurable limits for QoS data values-> send message for decision making
2321/03/2013
15.1.2013 Marko Palola, VTT
23
QoS information collection for decision making
measurement durationtimestampuplink packet lossuplink packet loss totaldownlink packet loss downlink packet loss totaluplink packet delay downlink packet delay uplink packet jitter downlink packet jitter throughput downlink
QosmetCoreClient receives the following QoS parameters(typically in 1 seconds interval):
offered load uplinkbytes receivedpackets receivedbytes sentpackets sentdownlink calculated MOSuplink calculated MOS
Example decision data delivered by QosmetCoreClient• throughput.speed=low;• throughput.value=345.22;
2421/03/2013
15.1.2013 Marko Palola, VTT
24
LTECoreClient – user LTE cell location
LteCoreClient receives various information from EAST tool:
• CREATE_ACK – an LTE device has attached to the network• HO_EVENT – an LTE device has made handover• DESTROY_ACK – an LTE device is disconnected• ENB_ASSO_INFO – an LTE base station has been started• STARTUP – the network is restarting
Delivers user cell location and number of clients in a cell to decision making• UE2.location = 65311;• UE3.network=lte;• basestation.cellid=25601;basestation.clients=1;
External system:
• Centria LTE test network• NetHawk East LTE tool
http://www.exfo.com
2521/03/2013
15.1.2013 Marko Palola, VTT
25
WarpCoreClient – WARP radio NW resource management
External system:
• CWC’s WARP radio network• WARP database
WarpCoreClient brings WLAN channel availability information into WARP radio network
• Sets free / occupied WLAN channels
WARPs avoid reserved WLAN channels
2621/03/2013
15.1.2013 Marko Palola, VTT
26
Summary of CORE Trial Environment features
CORE Client-side toolsWindows 7-based network detection, handover
MIP network detection, seamless handovers
Qosmet 2-way network QoS information collector – delay, delay jitter, packet loss, throughput, General QoE (1-5)
LTE user location monitoring – Cell id, IMSI, IP address
MIH Network Information data source (on development)
Networks, basestations, basestation status
WARP Cognitive radio network resource management (on development)
WLAN channel management over network
LTE network resource management (2013)
CORE Cognitive engineIntegrate & control new systems easily
Stand-alone and distributed decision making
Cognitive API for data collection
Browser-based user interfaceDecision rule editorMonitor collected dataVisualisation of data Configuration of client-side tools, policies, access, data types (on development)
Cognitive Engine hosting at VTT CNL
http://core.willab.fi http://www.cnl.fi
2721/03/2013
15.1.2013 Marko Palola, VTT
27
VTT - 70 years oftechnology for business
and society
2821/03/2013
15.1.2013 Marko Palola, VTT
28
DEMONSTRATIONS
2921/03/2013
15.1.2013 Marko Palola, VTT
29
CORE Trial Environment Demo WLAN/LTE offloading
3021/03/2013
15.1.2013 Marko Palola, VTT
30
CORE Trial Environment Demo Centria IPTV priority (LTE-WLAN offloading)
Kaisaniemi
Ratakatu
Puuhkala
S1+X2
S1+X2S1+X2
PPO
iPro
M5 AnalyzerBTS Site Manager
AlavieskaS1+X2
YlivieskaS1+X2
CENTRIA
Wi-Fi1
Wi-Fi2LTECoreClient
Trial users
VTTCORE Trial Environment
Cognitive API
Cognitive Engine
Cognitive Manager
WWWEAST visualization
UI
EXFO EASTLTEMME-SGW-SimulatorLTECoreScript
QosmetQosmetCoreClient
HandoverCoreClientMIP Client
QosmetQosmetCoreClient
HandoverCoreClientMIP Client
QosmetQosmetCoreClient
HandoverCoreClientMIP Client
Cognitive EngineVisualization
3121/03/2013
15.1.2013 Marko Palola, VTT
31