Communications Architecture Between Devices

download Communications Architecture Between Devices

of 13

Transcript of Communications Architecture Between Devices

  • 7/25/2019 Communications Architecture Between Devices

    1/13

    Communications Architecture between devices -

    At the high level, the TheTable reservation management system is composed of 6 systems that

    are interconnected by a communication network that is rooted in the 7 layers of the OSI model

    The 6 systems that comprise the ecosystem are !

    " TheTable mobile application

    # TheTable watch

    $, TheTable appserver

    %TheTable core databases

    & TheTable restaurant back!end web portal management app

    6 TheTable restaurant web portal

  • 7/25/2019 Communications Architecture Between Devices

    2/13

    A high level depiction of the components and the communication network that connects them is

    attached here as the Communication Architecture High Level Diagram'

  • 7/25/2019 Communications Architecture Between Devices

    3/13

    The diagram above denotes 6 interfaces that will be discussed in the ne(t section

    10 layer model breakdown of architecture

  • 7/25/2019 Communications Architecture Between Devices

    4/13

    The communications architecture can be decomposed using the ") layer model of information

    systems *evel $ represents the communication network services that are re+uired to interconnect

    the different hardware processing and storage platforms that are at level %- of the system *evel

    # represents the physical mediums of connectivity to form a basis for the *evel $ connectivity

    services A description of the communication architecture will also re+uire a description of the

    framework services and common software and enterprise services that are part of the overall

    information system

    Interface 1 and ! "etween the #he#able watch and the i$% a&&lication 'Interface 1( and

    the Android a&&lication 'interface () #his interface has the following com&onents -

    *evel #! .luetooth /0 operating at the #&123 fre+uency

    *evel $ ' .luetooth Architecture using the .luetooth Stack

    *evel &46 ' The watch utili3es a proprietary developed processing framework to populate packets

    formatted according to theI555 )#"&" .luetooth 8A9 specifications The packets are

    interpreted via the Android platform:s .luetooth A8I framework and the iOS platform:s ;ore

    .luetooth framework to yield information that can be used by the application

    that is present in the watch and the mobile

  • 7/25/2019 Communications Architecture Between Devices

    5/13

    application OS

    The .luetooth architecture can be summari3ed within conte(t of the 7 layer OSI model as

    follows *iu- !

  • 7/25/2019 Communications Architecture Between Devices

    6/13

    The portion representing the .luetooth and is the common portion that sets the

    *evel $ and *evel # restrictions on the application frameworks and middleware *evels & and 6-

    residing on the watch and mobile application operating systems

    Interface * ! "etween the #he#able mobile a&&lication and the #he#able a&&lication

    server)

    *evel #! Internet connectivity via wifi between the mobile devices and the app server ifi is

    rooted in the I555 )#"" standards and uses the #% 123 ?20 /adio band

    *evel $ ' This is composed of internet connectivity services using the 7 layer OSI model with

    the following decomposition '

    *ayer 9ame OSI 8rotocols

    7 Application 2TT8

    6 8resentation @851

    & Session /8;

    % Transport T;8

    $ 9etwork Ip v%

    #

  • 7/25/2019 Communications Architecture Between Devices

    7/13

  • 7/25/2019 Communications Architecture Between Devices

    8/13

    download the S

  • 7/25/2019 Communications Architecture Between Devices

    9/13

    web services hosted on the app server and the restaurant management portal to directly access

    the database and run SE* +ueries on it would leave the entire system e(tremely prone to hackers

    who might e(ploit security vulnerabilities to carry out a SE* inBection attack In order to protect

    the system and speed up +uerying4retrieval and ensure that the databases are themselves kept up

    to date it is preferable to use a

  • 7/25/2019 Communications Architecture Between Devices

    10/13

    Image from Oracle-

  • 7/25/2019 Communications Architecture Between Devices

    11/13

    side and hence it:s operation is very similar to Interface % between the appserver on the user:s

    side and the core database-

    *evel # ' Internet connectivity for which the medium would be wired optical fiber that links the

    servers hosting the applications in regional data centers with the core data center A ") 1igabit

    optical fiber *# connection would be classified under I555 )#$ae

    *evel $ 'This is composed of internet connectivity services using the 7 layer OSI model with the

    following decomposition '

    *ayer 9ame OSI 8rotocols

    7 Application 2TT86 8resentation @851

    & Session /8;

    % Transport T;8

    $ 9etwork Ip v%

    #

  • 7/25/2019 Communications Architecture Between Devices

    12/13

    *evel $ ' This is composed of internet connectivity services using the 7 layer OSI model with

    the following decomposition '

    *ayer 9ame OSI 8rotocols

    7 Application 2TT8

    6 8resentation @851

    & Session /8;

    % Transport T;8

    $ 9etwork Ip v%

    #

  • 7/25/2019 Communications Architecture Between Devices

    13/13

    /eferences !

    httpF44docsoraclecom4cd45#"76%G)"4web""""4e"$7$&4dbwshtmHS/8A#

    httpF44progtutorialstripodcom4.luetoothGTechnologyhtm

    http://docs.oracle.com/cd/E21764_01/web.1111/e13735/dbws.htm#WSRPA289http://docs.oracle.com/cd/E21764_01/web.1111/e13735/dbws.htm#WSRPA289