Processing

Please wait...

Settings

Settings

Goto Application

1. WO1997024851 - GENERIC OPERATOR SERVICES SESSION LAYER PROTOCOL

Publication Number WO/1997/024851
Publication Date 10.07.1997
International Application No. PCT/US1996/020274
International Filing Date 30.12.1996
Chapter 2 Demand Filed 25.07.1997
IPC
H04L 29/06 2006.01
HELECTRICITY
04ELECTRIC COMMUNICATION TECHNIQUE
LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
29Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/-H04L27/136
02Communication control; Communication processing
06characterised by a protocol
H04L 29/08 2006.01
HELECTRICITY
04ELECTRIC COMMUNICATION TECHNIQUE
LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
29Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/-H04L27/136
02Communication control; Communication processing
06characterised by a protocol
08Transmission control procedure, e.g. data link level control procedure
CPC
H04L 29/06
HELECTRICITY
04ELECTRIC COMMUNICATION TECHNIQUE
LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
29Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00
02Communication control
06characterised by a protocol
H04L 67/14
HELECTRICITY
04ELECTRIC COMMUNICATION TECHNIQUE
LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
67Network-specific arrangements or communication protocols supporting networked applications
14for session management
H04L 67/16
HELECTRICITY
04ELECTRIC COMMUNICATION TECHNIQUE
LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
67Network-specific arrangements or communication protocols supporting networked applications
16Service discovery or service management, e.g. service location protocol [SLP] or Web services
H04L 67/42
HELECTRICITY
04ELECTRIC COMMUNICATION TECHNIQUE
LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
67Network-specific arrangements or communication protocols supporting networked applications
42Protocols for client-server architectures
H04L 69/12
HELECTRICITY
04ELECTRIC COMMUNICATION TECHNIQUE
LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
69Application independent communication protocol aspects or techniques in packet data networks
12Protocol engines, e.g. VLSIs or transputers
H04L 69/32
HELECTRICITY
04ELECTRIC COMMUNICATION TECHNIQUE
LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
69Application independent communication protocol aspects or techniques in packet data networks
30Definitions, standards or architectural aspects of layered protocol stacks
32High level architectural aspects of 7-layer open systems interconnection [OSI] type protocol stacks
Applicants
  • MCI COMMUNICATIONS CORPORATION [US]/[US]
Inventors
  • KIRCHNER, Michael, C.
  • KRISHNASWAMY, Sridhar
  • KULT, George
  • SACKETT, Jeffrey, R.
  • YOUNG, Greg
Agents
  • KESSLER, Edward, J.
Priority Data
08/581,74429.12.1995US
Publication Language English (EN)
Filing Language English (EN)
Designated States
Title
(EN) GENERIC OPERATOR SERVICES SESSION LAYER PROTOCOL
(FR) PROTOCOLE GENERIQUE DE COUCHE SESSION POUR SERVICES POUR OPERATEURS
Abstract
(EN)
The invention provides a generic session layer protocol that enables many generic complex transactions and exchanges between a client and a service/server. The generic session layer transactions and exchanges are available via a set of programming language functions. The functions reside in the Network Information Distribution Service (NIDS) Application Program Interface (API) of an operator services network. To introduce a new service on an operator services network, only the functions are needed to be used. Accordingly, each time a new service is created, new functions calls, new protocols and a new session layer do not need to be created.
(FR)
La présente invention concerne un protocole générique de couche session qui permet de nombreuses transactions, et de nombreux échanges, génériques complexes entre un client et un service ou serveur. Ces transactions et échanges sont disponibles par l'intermédiaire d'un ensemble de fonctions de langages de programmation. Ces fonctions résident dans l'interface de programme d'application (API) d'un service de distribution d'informations sur un réseau (NIDS) d'un réseau de services pour opérateurs. Pour introduire un service nouveau dans un réseau de ce genre, il n'est nécessaire d'utiliser que les fonctions. En conséquence, chaque fois qu'un service nouveau est créé, il n'est pas nécessaire de créer de nouveaux appels de fonctions, de nouveaux protocoles ni une nouvelle couche session.
Latest bibliographic data on file with the International Bureau