Eicon Networks Eicon 1550 Uživatelský manuál stáhnout pdf (Strana 8)

US

2006/0120402

A1

of

the

invention

Where

a data

packet

is

received

either

from

an

X25

application

or

from

a

TCP/IP

physical

network

interface;

and

[0019]

FIG.

5

is

a

block

diagram

showing

an

embodiment

of

the

invention

Where

a

host

running

an

X25

application

communicates

With

another

X25

application

over

a

TCP/IP

netWork.

[0020]

It

Will

be

noted

that

throughout

the

appended

draWings,

like

features

are

identi?ed

by

like

reference

numerals.

DETAILED

DESCRIPTION

OF

THE

PREFERRED

EMBODIMENT

[0021]

NoW

referring

to

FIG.

2,

there

is

shoWn

an

embodiment

Where

a

?rst

host

22

communicates

With

a

second

host

56

and

With

a

third

host

42.

[0022]

More

precisely,

the

?rst

host

22

communicates

With

the

second

host

56

via

an

alternative

data

packet

netWork

34,

a

gateWay

36

and

an

X25

netWork

54.

[0023]

The

?rst

host

22

also

communicates

With

the

third

host

42

via the

alternative

data

packet

netWork

34.

[0024]

The

alternative

data

packet

netWork

34

may com

prise

any

type

of

data

packet

netWork

such

as

a

Local

Area

NetWork

(LAN),

a

Metropolitan

Area

NetWork

(MAN),

a

Wide

Area

NetWork

(WAN)

or the

like.

The

data

packet

netWork

34

may

further

operate

using

any

type

of

commu

nication

protocol

outside

of

the

X25

protocol.

Preferably,

the

alternative

data

packet

netWork

34

is

a

Wide

Area

NetWork

operating

according

to

the

TCP/IP

communication

protocol,

such

as

the

Internet.

[0025]

More

precisely,

the

?rst

host

22

comprises

a

?rst

processing

unit

running

an

X25

application

24,

a

driver

32

and

an

alternative

data

packet

netWork

interface

30.

The

driver

32

comprises

an

X25

virtual

netWork

interface

card

26

and

an

encapsulating/decapsulating

unit

28.

[0026]

The

?rst

processing

unit

running

an

X25

applica

tion

24

may

be

any

type

of

processing

unit.

In a

preferred

embodiment,

the

?rst

processing

unit

comprises

a

Linux

based

system

running

a

X25

socket

based

application.

[0027]

The

alternative

data

packet

netWork

interface

30

may

be

any

type

of

netWork

interface

adapted

for

commu

nicating

With

the

alternative

data

packet

netWork

34.

In

a

preferred

embodiment,

the

alternative

data

packet

netWork

interface

30

comprises

an

Ethernet

interface

using

TCP/IP

protocol

stack.

[0028]

As

mentioned

earlier,

the

driver

32

comprises

an

X25

virtual

netWork

interface

card

26

(softWare

imple

mented

netWork

interface

card)

and

an

encap

sulating/decap

sulating

unit

28.

The

driver

32

is

preferably

installed

in

the

volatile

memory

of

the

?rst

host

22.

[0029]

In

fact,

the

X25

virtual

netWork

interface

card

26

of

the

driver

32

may

be

a

softWare

module

Which

is

intended

to

simulate

the

presence

of

a

X25

netWork

interface

in

the

operating

system of

the

?rst

host

22.

[0030]

The

encapsulating/decapsulating

unit

28

of

the

driver

32

may

be

a

softWare

module

Which

is

intended

to

encapsulate

data

packets

originating

from

the

X25

applica

tion

into

encapsulated

data

packets

Which

are

suitable

to

be

Jun.

8,

2006

transmitted

on

the

alternative

data

packet

netWork.

It

should

be

understood

by

the

skilled

addressee

that

the

encapsulating

comprises

performing

any

ISO

Layer

2

operations

that

are

required

for

transmitting the

data

packet

over

the

alternative

data

packet

netWork

34.

On

the

X25

virtual

netWork

inter

face

card

26

side,

the

virtual

interface

provides

support

for

X25

sockets

APIs

for

end-user

applications

to

be

able

to

make

use

of

it.

On

the

alternative

data

packet

netWork

interface

30

side,

means

are

provided

to

con?gure

destina

tion

address

and

other

parameters

(such

WindoWing)

for

a

given

connection.

It

also

comprises

proper

translation

of

X25

SVC

and

PVC

sessions

into

the

alternate

data

packet

session

format

(such

as

for

example

XOT).

[0031]

Furthermore,

the

encapsulating/decapsulating

unit

28

of

the

driver

32

is

intended

to

decapsulate

data

packets

received

from

the

alternative

data

packet

netWork

interface

30

into

data

packets

that

are

suitable

to

be

used

by

the

X25

application.

[0032]

The

gateWay

36

is

adapted

for

bridging

traf?c

betWeen

the

alternative

data

packet

netWork

34

and

the

X25

netWork

54.

In

this

embodiment

the

gateWay

36

comprises

an

alternative

data

packet

netWork

interface

38

Which

is

connected

to

the

alternative

data

packet

netWork

34

and

a

X25

netWork

gateWay

40

connected

to

the

X25

netWork

54

and

further

to

the

alternative

data

packet

netWork

interface

38.

The

skilled

addressee

Will

appreciate

that

the

gateWay

36

may

be

provided

according

to

various

parameters

such

as

bandWidth,

security

requirements

or the

like.

In a

preferred

embodiment,

the

gateWay

36

comprises

an

Eicon

1550

WAN

Router.

[0033]

The

second

host

56

comprises

a

X25

interface

58

and

a

second

processing

unit

running

an

X25

application

60.

The

second

processing

unit

running

an

X25

application

60

is

connected

to

the

X25

netWork

54

using

the

X25

interface 58.

The

skilled

addressee

Will

appreciate

that

the

X25

interface

58

may

be

selected

according

to

various

parameters

such

as

bandWidth,

security

requirements,

guar

anteed

delivery,

reliability

and

latency.

In

a

preferred

embodiment,

the

X25

interface

58

comprises

an

Eiconcard

S91.

[0034]

The

third

host

42

is

connected

to

the

alternative

data

packet

netWork

34.

[0035]

The

third

host

42

comprises

an

alternative

data

packet

netWork

interface 44,

a

driver

52

and

a

third

pro

cessing

unit

running

an

X25

application

50.

[0036]

More

precisely,

the

alternative

data

packet

netWork

interface

44

may

be

any

type

of

netWork

interface

adapted

for

communicating

With

the

alternative

data

packet

netWork

34.

In a

preferred

embodiment,

the

alternative

data

packet

netWork

interface

44

comprises

an

Ethernet

interface

using

TCP/IP

protocol

stack.

[0037]

The

driver

52

comprises

an

encapsulating/decap

sulating unit

46

and

an

X25

virtual

netWork

interface

card

48.

[0038]

Similarly

to

the

encapsulating/decapsulating

unit

28

of

the

driver

32,

the

encapsulating/decapsulating

unit

46

is

a

softWare

module

Which

is

intended

to

encapsulate

data

packets

originating

from

the

X25

application

into

encapsu

lated

data

packets

Which

are

suitable

to

be

transmitted

on

the

alternative

data

packet

netWork

34.

Again,

it

should

be

1 2 3 4 5 6 7 8 9 10

Komentáře k této Příručce

Žádné komentáře