Browse Prior Art Database

Internet Subscriber Controlled Input (ISCI) via peripheral access

IP.com Disclosure Number: IPCOM000017911D
Original Publication Date: 2001-Oct-01
Included in the Prior Art Database: 2003-Jul-23
Document File: 3 page(s) / 237K

Publishing Venue

Siemens

Related People

Bart Reynaert: AUTHOR

Abstract

Emiel van Landeghem, B-Gent

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 42% of the total text.

Information / Kommunikation

Internet Subscriber Controlled In-put (ISCI) via peripheral access

Idee: Bart Reynaert, B-Menen;

Emiel van Landeghem, B-Gent

At the moment there are no solutions for ISCI viaperipheral  access  available.  The  X.25-concept wasoriginally only meant for demonstration purposes andcustomer tryouts, and is conceptually not suitable toestablish big performances. At the same time it is notthe suitable  platform  to  handle  normal  SubscriberControlled Input (SCI)-processing functions likecharging, traffic measurement etc.

The  at  the  based  lying  technical  problem is ex-pounded in the following:

A. Performance

A1. Restricted net access to the switch

ISCI via X.25 Classic SCI

Runtime of one SCI 4 sec. 80 msec.

Number of SCI'sper second (1 Erl.) 0,25 12,5

Number of SCI'sper minute (1 Erl.) 15 750

Number of SCI'sper minute (0,25Erl.)

3 187

Erl. = ‘Erlang’ = unit of traffic flow = number ofSCI’s per unit of time multiplied by mean hold-ing time.

‘1 Erlang’ corresponds to the usage of 100% ofthe BAPM processing time.

Figure 1

Communication: Internet client -POP

Communication: Internet client -POP

TCP/IP(Internet)

TCP/IP(Internet)

Internet

Internet

POP

POP

ISCI-Input

ISCI-Input

ISCIServer

ISCIServer

EWSD

LE

EWSD

LE

EWSD

LE

PRI

PRI

X.25

X.25

The connection  between  the  ISCI-server  and  theswitch  is  established  via  a  relatively  smallbandedX.25-interface (see Figure 1).

A2. Restricted use of Central Prozessor113 (CP113)processing capabilities

The used interface protocol is the Man Machine Lan-guage  (MML)-interface  protocol.  This  means  thatMML-commands are sent over the X.25-line. MML-commands are processed with low priority (MML:3vs.  CallP:7);  are  inherently  quite  slow  itself, andabove all, they can be processed only the Base Proc-essor (BAP) (  →   mono-processing), i.e. not on Cen-tral Processors (CAP’s) (  →   multi-processing). Com-pared to the processing of ‘classic’ Subscriber Con-trolled Input,  MML  is  about  50  times  slower  (seetable below).

As  a  consequence  of  A1  and  A2, ISCI via X.25-interface can impossibly be released for real opera-tion, due to its inefficient performance.

B. Missing major functionalities

B1. Charging

Only Automatic Message Accounting (AMA) is pos-sible, no Detailed Billing (DEB), no Meter Observa-tions (MOBS). Still, AMA for MML-commands isdifferent from AMA for classic SCI in several ways,i.e. no uniform AMA for ISCI compared to classicSCI.

B2. Personal Identification Number (PIN) functions

The PIN misuse counter, relevant for classic SCI, isnot considered. Neither are the PIN validation checksfor modifying the PIN.

B3. Lawful Interception (LI)

Not covered, since no LI is done for MML-commands.

B4. Number Portability

Not covered at all, since routing is purely done basedon Dictionary Number tables in the ISCI-server.

B5. Traffic Measurement

Not covered, since no Traffic Measurement is donefor MML-commands.

C. No standardisation perspectives

...