WO1999003286A2 - Systeme cellulaire utilisant un courtier de demande d'objet - Google Patents

Systeme cellulaire utilisant un courtier de demande d'objet Download PDF

Info

Publication number
WO1999003286A2
WO1999003286A2 PCT/US1998/014456 US9814456W WO9903286A2 WO 1999003286 A2 WO1999003286 A2 WO 1999003286A2 US 9814456 W US9814456 W US 9814456W WO 9903286 A2 WO9903286 A2 WO 9903286A2
Authority
WO
WIPO (PCT)
Prior art keywords
orb
processor
server
protocol
entity
Prior art date
Application number
PCT/US1998/014456
Other languages
English (en)
Other versions
WO1999003286A3 (fr
Inventor
Praveen Kumar
Scott Larribeau
Stewart Y. Kuan
Sanjay Kapoor
Original Assignee
Northern Telecom Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Northern Telecom Limited filed Critical Northern Telecom Limited
Priority to AU83982/98A priority Critical patent/AU8398298A/en
Priority to CA002295833A priority patent/CA2295833A1/fr
Priority to EP98934471A priority patent/EP0995325A2/fr
Publication of WO1999003286A2 publication Critical patent/WO1999003286A2/fr
Publication of WO1999003286A3 publication Critical patent/WO1999003286A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/16—WPBX [Wireless Private Branch Exchange]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/42—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker
    • H04Q3/54—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker in which the logic circuitry controlling the exchange is centralised
    • H04Q3/545—Circuit arrangements for indirect selecting controlled by common circuits, e.g. register controller, marker in which the logic circuitry controlling the exchange is centralised using a stored programme
    • H04Q3/54575—Software application
    • H04Q3/54583—Software development, e.g. procedural, object oriented, software generation, software testing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13034—A/D conversion, code compression/expansion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/1305—Software aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13057—Object-oriented software
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13098—Mobile subscriber
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13104—Central control, computer control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13107—Control equipment for a part of the connection, distributed control, co-processing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13204—Protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/1322—PBX
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/1338—Inter-exchange connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13396—Signaling in general, in-band signalling

Definitions

  • the present invention relates to a microcellular telephone system.
  • the present invention relates to a microcellular telephone system employing an object request broker to facilitate communication among components.
  • MSC mobile switching centers
  • base stations base station transceivers
  • transcoders transcoders
  • PBX wireless public broadcast exchange
  • Protocols provide standards that ensure compatibility between elements, such as portable terminals and the particular service platform on which they depend. Examples of the currently-implemented protocols include the GSM standard (Europe), the PHS standard (Japan), and the AMPS/TDMA and CDMA protocols (North America).
  • the present invention provides a mobility architecture that distributes functions across several peripheral processors within a microcellular communication environment.
  • the system and method of the present invention provides a transport mechanism that permits objects to effectively communicate with non-object oriented platforms.
  • the present invention allows existing systems to be integrated with newly designed call processing applications.
  • a call processing method comprises the steps of transmitting an object request message from the first processor to an object request broker (ORB); identifying an interface wrapper using the object request message, the interface wrapper serving as a proxy for a non-object residing on the at least one peripheral processor; receiving, at the identified interface wrapper, the object request message from the ORB; converting the object request message to a data request by inserting an identifier reference; retrieving a non-object entity using the data request; returning the non-object entity to a call application program via the ORB, the non-object entity corresponding to the object requested by the ORB; and executing the call application program using the returned non-object entity.
  • ORB object request broker
  • a method for facilitating communication between an ORB platform processor and a non-ORB platform processor comprising: receiving, at an object adapter client, a registration request message from at least one non-object entity, the adapter client and the at least one non-object entity residing on the non-ORB platform processor; forwarding the registration request message from the object adapter client to an object adapter server, the object adapter server residing on the ORB platform processor; and generating an interface wrapper to serve as a proxy for the at least one non- object entity.
  • a microcellular telephone system including a core processing unit and a wireless private branch exchange (PBX) switch for distributing communication signals to a plurality of portable terminals
  • the PBX switch comprises a mobility controller, the mobility controller includes an object request broker for communicating object request messages from the core processing unit; and at least one transcoder card, coupled to the mobility controller, for performing protocol dependent processing functions.
  • PBX wireless private branch exchange
  • a telephone switch comprises a call services layer for providing call processing services that are common to both wireline and wireless services; a mobility layer, coupled to the call processing layer, for providing mobility control for a plurality of portable terminals; a protocol interface layer for providing a protocol specific communication link to the plurality of portable terminals; and a platform layer for providing a protocol independent operating environment.
  • FIG. 1 illustrates a cellular system consistent with the invention
  • FIG. 2 illustrates one embodiment of the layered software architecture consistent with the invention
  • FIG. 3 is a block diagram of the mobility controller and transcoder shown in Fig. i;
  • FIG. 4 illustrates the registration of a non-object residing on a transcoder card for access by an ORB object;
  • FIG. 5 illustrates the message sequence occurring during a non-object to object binding procedure in accordance with the one embodiment of invention
  • FIG. 6 is a flow diagram showing a message sequence 600 occurring during a object to non-object binding procedure in accordance with one embodiment of the invention.
  • FIG. 7 illustrates a message sequence occurring when an ORB object residing on a ORB platform processor calls upon a non-object residing on a peripheral non-ORB platform processor, in accordance with the invention.
  • a cellular system consistent with the invention employs a telephone switch having a layered, distributed architecture, where modules for protocol dependent functions are separated from modules for non-protocol dependent functions. In this way, the protocol under which the system operates can be changed with minimum disruption to modules for non-protocol dependent functions.
  • the switch also may employ a mechanism to enhance the object request broker that controls and facilitates communication between cards operating on object-oriented and non-object-oriented platforms. In this way, components operating under an object- oriented platform can be used in conjunction with components operating under a non- object-oriented platform.
  • FIG. 1 is a block diagram of a cellular communication system 100 consistent with the invention.
  • System 100 includes a public branch exchange (PBX) switch 110, a series of telephone terminals 102 and 104, at least one micro base station 150, a group of distributed antenna 160 and 161, and a series of portable, or cellular, telephone units 170 and 171.
  • PBX public branch exchange
  • system 100 could include a plurality of PBX switches, in which case each of the PBX switches would cover a different zone.
  • System 100 preferably operates within a single facility, or group of related facilities, the size of which dictates the number of components that system 100 accommodates.
  • system 100 is preferably connected to a public switching network 180 through standard communication link 182 and to a macro cellular network 190 through communication link 192.
  • Telephone terminals 102 and 104 are connected to PBX 110 switch by a conventional communication link 105 capable of transmitting both voice and data communication signals.
  • PBX 110 is also coupled to micro base station 150, which in turn is coupled to distributed antenna 160 and 161.
  • Antenna 160 and 161 communicates with portable units 170 and 171 through wireless link 165.
  • system 110 interfaces with at least one network server terminal (not shown) responsible for, among other things, network administration and maintenance functions.
  • Telephone terminals 102 and 104 are standard telephones capable of receiving and transmitting call signals to and from PBX switch 110 using conventional methods and equipment.
  • Micro base station 150 preferably comprises programmed processing hardware executing signal transceiver software for routing communication signals from PBX switch 110 to the portable units 170 and 171 via antennae 160 and 161, respectively.
  • Portable units 170 and 171 are preferably conventional cellular telephones, and alternatively could also comprise pagers, personal digital assistants (PDA) or any other wireless device capable of receiving and transmitting a radio or microwave frequency communication signal.
  • PDA personal digital assistants
  • portable units 170 and 171 comply with communication protocol IS-136 and are capable of following the registration requirements of IS-41.
  • PBX switch 110 preferably comprises programmed processing hardware executing software for performing call processing and mobility routing functions for system 100.
  • Northern Telecom Ltd.'s Meridian Ml is an example of a PBX switch suitable for the present invention.
  • PBX switch 110 receives internal call processing and routing requests from the telephone terminals 102 and 104 and the portable units 170 and 171, as well as external call routing requests from PSTN 180 and macro cellular network 190 via communication links 182 and 192, respectively.
  • PBX switch 110 contains a core network central processing unit (CPU) 120, a mobility controller 130, and a transcoder card 140.
  • Core network CPU 120 is a standard call processing and switching device that handles non-mobile related call processing requests received at PBX switch 110 from external or internal sources.
  • core network CPU 120 routes the call according to conventional switching techniques to telephone terminals 102 or 104.
  • PBX switch 110 also contains mobility controller 130 and transcoder card 140 for routing communication signals to portable units 170 and 171 via micro base station 150 and antenna 160 and 161. Both mobility controller 130 and transcoder card 140 have processors and associated components to perform their various call routing and processing duties. Consistent with the invention, mobility controller 130 performs general call mobility functions such as (1) providing call handover to maintain a continuous wireless communication link when portables move between zones, (2) allowing portables of different configurations access system 110, and (3) tracking the portable's location as a user moves within the serviced facility and outside the coverage area of system 100. Mobility controller 130 receives mobility routing requests from core network CPU 120 via a standard communication connection, such as an Ethernet-type bus connection.
  • a standard communication connection such as an Ethernet-type bus connection.
  • Transcoder card 140 is preferably coupled to mobility controller 130 via a connection such as an HDLC communication link and micro base station 150.
  • Transcoder card 140 provides protocol specific mobility call processing functions such as call signal compression and decompression, encoding, echo cancellation and physical access to the portable terminal.
  • transcoder card 140 provides functions that are specific to the protocol standard employed by the particular portable terminal.
  • transcoder card 140 which is preferably physically isolated and separate from mobility controller 130, contains software modules for protocol dependent functions and operates under the same platform as mobility controller 130.
  • the protocol under which system 100 operates can be modified by replacing, or modifying, transcoder card 140 and the protocol related software modules located on mobility controller 130.
  • protocols include GSM, AMPS/TDMA, CDMA and PHS, as well as other protocols.
  • transcoder card 140 may also operate on a different platform than mobility controller 130. As discussed in greater detail below, the invention provides an interface to allow communication between mobility controller 130 and transcoder card 140.
  • FIG. 2 shows one embodiment of a layered software architecture structure 200 representing a distribution of functions among the processors in system 100. This layered distribution isolates protocol dependent functions from non-protocol dependent functions, minimizing the need to replace the modules for non-protocol dependent functions when the protocol under which the system operates is changed.
  • structure 200 includes a platform layer 210, a protocol layer 220, a network mobility layer 230, and a call services layer 240. These layers represent groups of functions performed by PBX 110 that may be distributed between core network CPU 120, mobility controller 130 and transcoder card 140.
  • mobility controller 130 and transcoder card 140 performs the functions associated with protocol layer 220.
  • Core network CPU 120 performs functions associated with call services layer 240 and network layer 230.
  • Platform layer 210 contains the general operating system environment for the underlying hardware of PBX 110. This includes development platforms for the various software modules residing on PBX 110 individual processor cards and the software needed to communicate with a system server apparatus interfaced to PBX 110.
  • core network CPU 120, mobility controller 130 and transcoder card 140 each have functionality relating to platform layer 210.
  • Protocol layer 220 encodes requests and data transfers to a specified protocol standard.
  • the layer preferably contains protocol standards to allow communication in at least one known protocol standard, such as AMPS/TDMA, GSM, PHS, and CDMA.
  • Mobility layer 230 provides mobility call processing function such as (1) providing call handover to maintain a continuous wireless communication link when portables move between zones, (2) allowing portables of different protocol configurations access to system 110, and (3) tracking the portable's locations as a user moves within the serviced facility and outside the coverage area of system 100.
  • the functions relating to this layer are performed on both core network CPU 120 and mobility controller 130.
  • Call services layer 240 interfaces mobility controller 130 with core network CPU 120 and allows communication of call processing and call routing requests between the mobility application and the standard wireline processing modules.
  • FIG. 3 is a block diagram illustrating components of mobility controller 130 and transcoder card 140.
  • transcoder card 140 includes adapter client 325 and non-object 330.
  • Mobility controller 130 includes object request broker (ORB) 305, wrapper object 310, ORB object 315, and adapter server 320. These components allow mobility controller 130, which is an object-oriented platform, to communication with transcoder card 140, a non-object oriented platform.
  • ORB object request broker
  • wrapper object 310 wrapper object 310
  • ORB object 315 ORB object 315
  • adapter server 320 adapter server 320.
  • These components allow mobility controller 130, which is an object-oriented platform, to communication with transcoder card 140, a non-object oriented platform.
  • a non- object may also be referred to as a non-ORB or an OOMT object.
  • ORB 305 comprises a software module that permits objects on a processor, or machine, operating under an object-oriented platform to access objects on another processor, or machine, also operating under an object-oriented platform. ORB 305 allows these platform-compatible machines to send object request messages from one machine to another and return object messages or data corresponding to the request messages.
  • ORBs create virtual objects, or "stubs," which represent remotely- located objects on other machines. Objects residing on the same machine as the stubs treat the stubs as if they were actual objects by passing information and submitting requests, which the stubs forward to the corresponding remotely-located objects.
  • ORBs and interface stubs are conventionally known in fields other than cellular call processing.
  • core network CPU 120 and mobility controller 130 operate under an object-oriented platform and communicate through ORB 305. Unless otherwise stated, the specification refers to "ORB platforms” and “object-oriented platforms” interchangeably. Similarly, “non-ORB platforms” and “non-object-oriented platforms” are used interchangeably.
  • Wrapper object 310 serves as a proxy for an object or a non-object residing on a remote non-ORB platform machine. It converts messages received from ORB 305 to a compatible message format that is understood by a non-object residing on a non-ORB platform. For example, if ORB object 315 requests a non-object residing on transcoder card 140, wrapper object 310 is called and converts the request into a format understandable by transcoder card 140.
  • wrapper object 310 is mapped to an integer value that serves as a identifier reference corresponding to and identifying the non- object it represents.
  • object 315 When an object request message is sent from ORB object 315 to non- object 330, object 315 sends the message thru ORB 305 by invoking a "stub" that represents wrapper object 310.
  • the stub and ORB 305 work together to deliver the message to wrapper obj ect 310, wrapper obj ect 310 translates the request so that it may be understood by adapter server 320 and adapter client 325.
  • wrapper object 310 is created either when a new non-object becomes available or a new object is created that wants to use an existing non-object.
  • ORB object 315 comprises an object, such as an application program, that accesses other objects.
  • ORB object 315 is a call processing program using remotely-located objects or sub-process programs to complete its assigned task.
  • Adapter server 320 and adapter client 325 communicate to pass data and requests to, for example, permit ORB object 315 to utilize data or functions residing in non-object 330.
  • Adapter server 320 and adapter client 325 use a standard TCP/IP communication link, or a similar common or proprietary link, as their underlying transport mechanism.
  • Adapter server 320 and adapter client 325 preferably comprise a programmed processor executing software to perform the associated functions described herein.
  • Non-object 330 may be data or sub-processing program residing on transcoder card 140, or any non-ORB platform machine. While non-object 330 is characterized as non-object, it may also be an object residing on non-ORB platform transcoder card 140.
  • wrapper object 310 serves two basic functions. First, wrapper object 310 operates as a translator, or interface, for messages transmitted from non-object 330 to ORB object 315. Second, wrapper object 310 operates as a translator, or interface, for message transmitted from ORB object 315 to non-object 330.
  • wrapper object 310 acts as a "reader thread" that permits data and messages contained in non-object 330 to be transmitted to ORB object 315 without disturbing the normal operation of ORB 305 and ORB object 315. That is, wrapper object 310 supplies data and messages from non-object 330 in a format understandable to ORB object 315 and at a time in which ORB object 315 expects to receive the data and message (i.e., ORB object 315 may be event-driven). Thus eliminating the need for ORB object 315 to poll for messages from non-object 330. Alternatively, several wrapper objects could rely on a single reader thread to receive messages from non-objects.
  • wrapper object 310 acts as a virtual object that represents non-object 330 residing on the non-obj ect platform transcoder card 140. Wrapper obj ect 310 remains transparent to ORB object 315 and ORB 305 and receives any received data and messages to non-object 330 in a manner and format understandable to non-object 330.
  • Wrapper object 310 is assigned an OOMT reference identifier that adapter client 325 uses to call non-object 330.
  • the reference identifier is preferably unique to ensure that adapter client 325 and adapter server 320 call for the correct non-object 330.
  • This identifier reference or "OOMTobjectReference,” includes information about the non-ORB platform on which the register non-object resides and is stored at both wrapper object 310 and the non-object 330. The OOMTobjectReference is subsequently used in all messages when a reference to the non-object is required.
  • an ORB object 315 sends a message to a non-object 330
  • the message is delivered through the ORB 305 to the wrapper object 310.
  • Wrapper object 310 receives the message and adds the identifier reference to the message before forwarding it to adapter server 320.
  • Adapter server 320 uses the identifier reference to determine the appropriate adapter client 325 to send the message and adapter client 325 uses the identifier reference to determine the appropriate non- object.
  • FIG. 4 shows a flow diagram for a registration process 400 consistent with the present invention.
  • a registration message is forwarded to adapter client 325, which also resides on transcoder card 140 (step 410).
  • adapter client 325 transmits a registration request message to adapter server 320 (step 420).
  • adapter server 320 creates wrapper object 310 (step 430).
  • wrapper object 310 serves as a proxy device that translates requests transmitted between ORB 305 and adapter server 320.
  • Adapter server 320 transmits a registration confirmation signal to adapter client 325 (step 440).
  • adapter client 325 transmits a registration confirmation signal to non- object 330 (step 450).
  • FIG. 5 is a flow diagram showing a message sequence 500 occurring during a non-object to object binding procedure in accordance with one embodiment of the invention.
  • non-object 330 sends a bind request message to adapter client 325 (step 510).
  • the bind request message includes the name of the ORB object 315 with which non-object 330 seeks to bind and a corresponding host name containing ORB object 315.
  • the host name refers to the core network CPU 120.
  • Adapter client 325 forwards the bind request message to adapter server 320 (step 520).
  • Adapter server 320 sends the bind request message to wrapper object 310 (step 530). Wrapper object 310 then sends an ORB_bind command message to ORB 305 (step 540).
  • the bind message contains the host and object name for ORB object 315.
  • ORB 305 Upon receiving the ORB_bind command, ORB 305 creates an stub 335 to serve as an interface between ORB 305 located on mobility controller 130 and ORB object 315 on core network CPU (step 550).
  • adapter server 320 and adapter client 325 assign an OOMT object identifier, or "ORBobjectReference,” that is similar to the "OOMTobjectReference,” describe above.
  • wrapper object 310 sends a bind confirmation message to adapter server 320 (step 560).
  • adapter server 320 sends a bind confirmation message to adapter client 325 (step 570), which, in turn, forwards the bind confirmation message to non-object 330 (step 580).
  • the bind confirmation message contains an OOMT object identifier reference that identifies stub 335.
  • the OOMT object identifier reference allows wrapper object 310 and adapter server 320 to identify stub 335 and associated ORB object 315 by using the stub identifier as a key in a translation table contained in adapter server 320.
  • Adapter server 320 and adapter client 325 use this integer identifier to recognize when a particular stub is called.
  • ORB object 315 also preferably binds to non-object 330.
  • ORB object 315 sends an ORB_bind command to ORB 305 (step 610).
  • ORB 305 creates an ORB stub 340 to serve as an interface for wrapper object 310 (step 620).
  • stub 340 is used when ORB object 315 wants to send a message to non-object 330.
  • FIG. 7 is a flow diagram showing a message sequence 700 occurring when an ORB object, or call application program residing on an ORB platform processor, calls upon a non-object residing on a peripheral non-ORB platform processor.
  • ORB object 315 transmits a object request message to stub 340 (step 705).
  • the object requested is non-object 330 residing on transcoder card 140.
  • Stub 340 forwards the request to ORB 305 (step 710) and ORB 305, recognizing that wrapper object 310 is the requested object, forwards the request message to wrapper object 310 (step 715).
  • the object request message is in a standard ORB message format.
  • Wrapper object 310 then converts the ORB message object request message to a message format that adapter server 320 and adapter client 325 can recognize. This converted message is then sent to adapter server 320 (step 720), which sends the message to adapter client 325 (step 725).
  • the converted object request message contains the non-object's 330 identifier reference.
  • adapter client 325 Upon receipt of the object request message and the object identifier reference, adapter client 325 forwards the message to called non-object 330 (step 730).
  • non-object 330 sends, for example, data or a message to adapter client 325 (step 735), and adapter client 325 forwards the non-object data to adapter server 320 (step 740).
  • the non-object data or message is a data byte stream and contains data information, a second parameter identifying the length of the data byte stream, and the identifier reference for wrapper object 310. This data byte stream is in accordance with the underlying communication transport that adapter server 320 and adapter client 325 use to communicate.
  • adapter server 320 forwards the ORB data message to wrapper object 310 (step 745).
  • Wrapper object 310 then converts the data byte stream to an ORB formatted message and forwards the ORB data message to stub 335 (step 750). Finally, stub 335 returns the data message to ORB 305 (step 755) and ORB object 315 receives the requested data message (step 760). Upon the completion of message sequence 600, ORB object 315 is able to complete its task using the retrieved object or data message.
  • Mobility controller 130 implemented on a ORB platform would serve as a communication intermediary between the two non-ORB transcoder cards regardless of their particular platform characteristics.
  • the message flow sequences would be similar to those described in conjunction with communicating between the ORB and non-ORB platform cards.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
  • Exchange Systems With Centralized Control (AREA)

Abstract

Un système cellulaire utilise un commutateur téléphonique ayant une architecture en couches et répartie, les modules pour les fonctions dépendant du protocole étant séparés des fonctions dépendant du non protocole. Le commutateur utilise également un courtier de demande d'objet qui commande et facilite la commande la communication entre les cartes exploitées sur des plates-formes orientées objet et non-objet.
PCT/US1998/014456 1997-07-11 1998-07-10 Systeme cellulaire utilisant un courtier de demande d'objet WO1999003286A2 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU83982/98A AU8398298A (en) 1997-07-11 1998-07-10 Cellular system employing an object request broker
CA002295833A CA2295833A1 (fr) 1997-07-11 1998-07-10 Systeme cellulaire utilisant un courtier de demande d'objet
EP98934471A EP0995325A2 (fr) 1997-07-11 1998-07-10 Systeme cellulaire utilisant un courtier de demande d'objet

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US89376297A 1997-07-11 1997-07-11
US08/893,762 1997-07-11

Publications (2)

Publication Number Publication Date
WO1999003286A2 true WO1999003286A2 (fr) 1999-01-21
WO1999003286A3 WO1999003286A3 (fr) 1999-04-01

Family

ID=25402048

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1998/014456 WO1999003286A2 (fr) 1997-07-11 1998-07-10 Systeme cellulaire utilisant un courtier de demande d'objet

Country Status (4)

Country Link
EP (1) EP0995325A2 (fr)
AU (1) AU8398298A (fr)
CA (1) CA2295833A1 (fr)
WO (1) WO1999003286A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001010139A2 (fr) * 1999-07-29 2001-02-08 Telefonaktiebolaget Lm Ericsson (Publ) Courtier de demandes d'objets a capacite de traitement d'objets multiples associes
WO2001041398A1 (fr) * 1999-11-30 2001-06-07 Telefonaktiebolaget Lm Ericsson (Publ) Acces ad hoc a des dispositifs bluetooth a partir d'une application java

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0405829A2 (fr) * 1989-06-30 1991-01-02 AT&T Corp. Architecture de système de logiciel orientée vers l'objet

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0405829A2 (fr) * 1989-06-30 1991-01-02 AT&T Corp. Architecture de système de logiciel orientée vers l'objet

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"CORBA: INTEGRATING DIVERSE APPLICATIONS WITHIN DISTRIBUTED HETEROGENEOUS ENVIRONMENTS" IEEE COMMUNICATIONS MAGAZINE, vol. 35, no. 2, February 1997, pages 46-55, XP000683401 *
GOKHALE A ET AL: "THE PERFORMANCE OF THE CORBA DYNAMIC INVOCATION INTERFACE AND DYNAMIC SKELETON INTERFACE OVER HIGH-SPEED ATM NETWORKS" COMMUNICATIONS: THE KEY TO GLOBAL PROSPERITY. GLOBECOM 1996, LONDON, NOV. 18 - 22, 1996, vol. 1, 18 November 1996, pages 50-56, XP000742125 INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS *
KATSUMI MARUYAMA ET AL: "A CONCURRENT OBJECT-ORIENTED SWITCHING PROGRAM IN CHILL" IEEE COMMUNICATIONS MAGAZINE, vol. 29, no. 1, 1 January 1991, pages 60-68, XP000203322 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001010139A2 (fr) * 1999-07-29 2001-02-08 Telefonaktiebolaget Lm Ericsson (Publ) Courtier de demandes d'objets a capacite de traitement d'objets multiples associes
WO2001010139A3 (fr) * 1999-07-29 2001-12-06 Ericsson Telefon Ab L M Courtier de demandes d'objets a capacite de traitement d'objets multiples associes
WO2001041398A1 (fr) * 1999-11-30 2001-06-07 Telefonaktiebolaget Lm Ericsson (Publ) Acces ad hoc a des dispositifs bluetooth a partir d'une application java

Also Published As

Publication number Publication date
EP0995325A2 (fr) 2000-04-26
WO1999003286A3 (fr) 1999-04-01
CA2295833A1 (fr) 1999-01-21
AU8398298A (en) 1999-02-08

Similar Documents

Publication Publication Date Title
US5845203A (en) Remote access application messaging wireless method
US6094578A (en) Gateway unit
RU2153237C2 (ru) Операционная система связи и способ ее осуществления
CA2241902C (fr) Procede et appareil de conversion de protocole
US7212543B1 (en) Method, system and device for establishing communication between different communication networks
US5842138A (en) Configuration-independent methods and apparatus for software communication in a cellular network
WO1999016227A2 (fr) Systeme generique de telecommunications sans fil
KR20000069257A (ko) 통화 셋업 프로세스
CN100461946C (zh) 一种系统间切换方法
WO1998002011A1 (fr) Unite passerelle
RU2283544C2 (ru) Способ обеспечения обслуживания коротких сообщений через мобильную интеллектуальную сеть
WO1999003286A2 (fr) Systeme cellulaire utilisant un courtier de demande d'objet
JPH11317771A (ja) サ―ビス制御点と信号網との間のインテリジェントゲ―トウェイ
JP2000125332A (ja) サービス登録方式
JP3310205B2 (ja) 移動通信システム
US5864761A (en) SS7 map provider system
AU6126196A (en) Ground-station system, ground station, device, method
EP1127439B1 (fr) Procede, systeme et dispositif pour etablir des communications entre differents reseaux de communication
US20030008640A1 (en) Data transmission method and data transmission arrangement
USH1898H (en) Signaling data processing
JPH11275634A (ja) ネットワーク番号管理システム及び交換機
US7376108B2 (en) Data transmission method and data transmission arrangement
AU717297B2 (en) Configuration-independent methods and apparatus for software communication in a cellular network
KR100299165B1 (ko) 교환기의 무선데이터서비스시스템 및 그 제어방법
US6963584B2 (en) Enhanced private parameter capability in IS-41 messages

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM HR HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

AK Designated states

Kind code of ref document: A3

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM HR HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
ENP Entry into the national phase in:

Ref country code: CA

Ref document number: 2295833

Kind code of ref document: A

Format of ref document f/p: F

Ref document number: 2295833

Country of ref document: CA

NENP Non-entry into the national phase in:

Ref country code: KR

WWE Wipo information: entry into national phase

Ref document number: 1998934471

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 1998934471

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWW Wipo information: withdrawn in national office

Ref document number: 1998934471

Country of ref document: EP