United States Patent (19)
`Onweller
`
`USOO5764756A
`Patent Number:
`11
`45 Date of Patent:
`
`5,764,756
`Jun. 9, 1998
`
`54) NETWORKED TELEPHONY CENTRAL
`OFFICES
`75) Inventor: Arthur E. Onweller, Evergreen, Colo.
`73 Assignee: US West, Inc., Englewood, Colo.
`
`"Flexible Routing and Addressing For a Next Generation
`IP” Francs, P. et al., Computer Communications Review,
`vol. 24. No. 4, 1 Oct., 1994, pp. 116-125.
`“An Overview of UNP." Peterson, L. L., Computer Com
`munications Review, vol. 19. No. 2. 1 Apr. 1989, pp. 21-31.
`
`21 Appl. No.: 585,347
`22 Filed:
`Jan. 11, 1996
`51) int. Clar. H04M 3700; HO4M 1/24:
`HO4M 3/08: HO4M 3/22
`52 U.S. C. .......................... 379/242: 370/352; 370/401;
`370/405; 370/410; 379/1: 379/12: 379/15
`58) Field of Search ............................... 3791, 6, 10, 12.
`379,22, 26, 27, 30, 32.33, 242, 15: 370/54,
`60, 85.6, 85.13, 85.14, 94.1, 352, 370,
`399, 40, 402, 405, 407, 408,409, 410.
`349, 522, 431
`
`56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`4,700,340 10/1987 Beranek et al. ........................ 370/28
`5,307,437 4/1994 Perlman et al. ..
`... 370/40
`5,317,568 5/1994 Bixby et al. ............................ 3704O1
`5,331,634 7/1994 Fischer ..............
`... 30405
`5,396.543 3/1995 Beeson, Jr. et al.
`... 379/59
`5,406,557 4/1995 Baudoin ............
`... 370.407
`5,410,590 4/1995 Blood et al. ..
`... 379,147
`5,414,754 5/1995 Pugh et al.....
`... 379/67
`5.425,026 6/1995 Mori..........
`370410
`5,450,468 9/1995 Bushnell ...
`379/27 X
`5,485,455
`1/1996 Dobbins et al. ........................ 370,255
`5,502,723 3/1996 Sanders .................................., 370/352
`5,530.703 6/1996 Liu et al. ................................ 370/255
`OTHER PUBLICATIONS
`"Internetworking with TCP/IP" (Document XP002031754).
`Douglas E. Comer, 1991. Prentice Hall. New Jersey, Chap
`ters 1 and 20.
`"Efficient, Real-TimeAddress Resolution in Backbone Net
`works of General Topology.” DBM Technology Disclosure
`Bulletin, vol. 36, No. 3. 1 Mar. 1993, pp. 133-139.
`
`Primary Examiner-Harry S. Hong
`Attorney Agent, or Firm-Holme. Roberts & Owen
`57
`ABSTRACT
`A communications networking system is disclosed for con
`trolling and monitoring devices within a telephony central
`office. The networking system includes a high bandwidth
`local area network (LAN) within the central office for
`transferring substantially all communications between each
`central office network element and remote telephony opera
`tional support systems (OSSs) that control and monitor
`network element performance. The LAN simplifies commu
`nications within the central office: (a) by substantially elimi
`nating direct connections, between central office network
`elements and remote OSSs, and (b) by utilizing at least one
`standardized communication protocol such as TCP/IP, UDP/
`IP, or OSI when transferring communications over the LAN.
`The networking system includes a mediation device(s) for
`translating between network element specific protocols and
`a standardized protocol used on the LAN. The networking
`system further includes redundant routers, each acting as an
`interface between a wide area network (WAN) connecting to
`the central office and the central office local area network,
`wherein the WAN provides substantially all of the commu
`nications between the central office and the OSSs. One of the
`routers is used in securing the central office against unde
`sirable access by agents dialing into the central office via the
`public telephone lines. This router obtains an ID and pass
`word from a dial-in agent, and communicates with a remote
`security center to determine what central office process
`interfaces the agent may access. The router also prohibits
`dial-in users from accessing the WAN and thereby accessing
`other telephony service control sites.
`
`57 Claims, 17 Drawing Sheets
`
`-es
`-
`
`ASPRA PSSARD
`PASSWORD
`-------n ASSIGNMENT
`
`
`
`&
`
`224
`
`J.
`|-
`
`PULTELEPHONE NEWORKORO.
`CENTER is
`
`ETORMANAGEMENT
`AN-U8--- OSS
`
`3.
`
`ACESS
`SECURITY
`
`AESS
`PESSNS
`DAAASE
`
`
`
`
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 1 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 1 of 17
`
`5,764,756
`
`
`
`JLRIV RHOIRICH [ '0IH
`
`
`
`
`
`1008 W300W
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 2 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`5,764,756
`
`VZ * OIH
`
`U.S. Patent
`
`
`
`
`
`
`
`
`
`
`
`
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 3 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 3 of 17
`
`5,764,756
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 4 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 4 of 17
`
`5,764,756
`
`FIG 3A
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`LET EACHELEMENT OF AN ARRAY
`COI), I=1,2,...,NBR COS, REPRESENT A
`CENTRAL OFFICE 120;
`
`304
`
`ADRSABLE INTERFACES - THE LIST OF PROCESS
`INTERFACES AT COI) WHEREIN FOREACHSUCH
`INTERFACE: (a) IT IS ABLE TO RECOGNIZE AN
`ADDRESS ASSIGNED TO IT; (b) IT IS DESIRABLE TO
`SEND OR RECEIVE COMMUNICATIONS USING AN
`ADDRESS ASSEGNED TO THE PROCESS INTERFACE
`
`
`
`
`
`320
`
`INTERFACE -- FIRST (NEXT) PROCESS
`INTERFACE IN "ADRSABLE INTERFACES"
`
`
`
`DOES "INTERFACE" COMMUNICATE WITH THE LAN 196
`OR WITH A ROUTER (e.g., ROUTERS 204, 192) WHEREIN:
`(a) THE COMMUNICATION IS THROUGH ASECOND
`INTERFACE IN "ADRSABLE INTERFACES", (b) THE
`SECOND INTERFACE PROVIDES A SOCKET THROUGH
`WHICH THE COMMUNICATIONSTRAVERSE, AND (c) THE
`SOCKET IS A GATEWAY BETWEEN 'INTERFACE" AND
`THE LAN 96 OR A ROUTER
`
`INSERT "INTERFACE" ON THE
`LIST, COI).IPADRSABLE LIST
`
`INSERT "INTERFACE" ON THE LIST,
`COI). SOCKET ADRSABLE LIST
`
`IS THERE ANOTHER PROCESS INTERFACE IN
`"ADRSABLE INTERFACES" NOT YET PROVIDED
`ON A LIST IN EITHER STEP 324 OR 328?
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 5 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 5 of 17
`
`5,764,756
`
`332
`
`H -- 1
`
`i
`
`|-
`
`NO {O | > NBR COS'
`336
`YES
`
`340
`
`FIG 3B
`
`NBR OSS -- THE NUMBER OF DATA CENTERS 130 AND
`CONTROL LOCATIONS SUCH AS CONTROL CENTER 128 AND
`SECURITY CENTER 140 TO BE INCLUDED IN THE SERVICE
`CONTROL WIDE AREA NETWORK 124
`
`344
`
`NTWKNODES -- NBR COS+ NBR OSS
`
`348
`
`NBR LAN HOST IDS -- THE MAXIMUM VALUE OF THE THIRD
`STANDARD DEVIATION FROM THE MEAN NUMBER OF IP
`ADDRESSABLE PROCESS INTERFACES PER CENTRAL OFFICE 120
`
`DETERMINE AN IP-ADDRESSING SCHEME WHEREIN:
`(a) EACH PROCESS INTERFACE PUT ON A LIST,
`COI).IP ADRSABLE LIST, I=1,2,...,NBR COS, HAS A DIFFERENT
`IP-ADDRESS;
`(b) "NTWK NODES" IS LESS THAN THE NUMBER OF NETWORK
`IDS IN THE NETWORKID PORTION OF THE IP-ADDRESSES FOR
`THE IP-ADDRESSING SCHEME;
`(c) FOREACH CENTRAL OFFICE, COI), I=1,2,...,NBR COS, THE
`PROCESS INTERFACES ON COI).IP ADRSABLE LIST HAVE
`IDENTICAL NETWORK ID PORTIONS FOR THEIR IP-ADDRESSES;
`(d) THE ADDRESSING SCHEME ALLOCATES TWO ORMORE BITS
`FOR THE LAN/ROUTER ID OF THE LOCAL ID PORTION OF EACH
`P-ADDRESS SO THAT AT LEAST TWO LAN HUBS 96 INA
`CENTRAL OFFICE 120 CAN BE DISTINGUISHED BY THE
`IP-ADDRESSES: AND
`(e) THE NUMBER OF DISTINCT BINARY VALUES OBTAINABLE IN
`THE HOST ID PORTION OF THE LOCAL ID OF THE IP-ADDRESSES
`IS GREATER THAN OR EQUAL TO NBR LAN HOST IDS
`
`IP ADRS MASK -- THE NUMBER OF BITS REQUIRED TO
`REPRESENT THE HOST ID PORTION OF AN IP-ADDRESS
`FOR THE DETERMINED IP-ADDRESSING SCHEME
`
`352
`
`END
`
`356
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 6 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 6 of 17
`
`5,764,756
`
`FIG. 4A
`
`404
`
`Hl
`
`-
`
`---
`
`408
`
`NTWK ID - THE FIRST (NEXT) NETWORK ID
`OF AN IP-ADDRESS FOR THE NETWORK
`ADDRESING SCHEME (DETERMINED IN FIGS. 3)
`WHEREN THE NETWORK ID IS NOT USED INA
`CENTRAL OFFICE, COJ), J NOT EQUAL TO I
`
`CO LAN - THE FIRST (NEXT). ENTRY IN A LIST
`OF REPRESENTATIONS OF LAN(S) 196 AND
`ROUTER(S) 204 OF COI);
`
`LAN ID -- THE FIRST (NEXT) LAN/ROUTER
`ID OF THE LOCAL D PORTION OF AN IP
`ADDRESS FOR THE NETWORKADDRESSING
`SCHEME WHEREN THE LAN/ROUTER HD IS
`NOT ASSIGNED TO ANOTHERLAN 196 OR
`ROUTER 204 IN COI)
`
`420
`
`
`
`
`
`HOST H A REPRESENTATION OF THE
`FIRST (NEXT) PROCESS INTERFACE OF
`COI).IP ADRSABLE LIST THAT ALSO
`COMMUNICATES VIA CO LAN
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 7 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 7 of 17
`
`5,764,756
`
`AAA
`
`
`
`424
`
`HOST ID -- THE FIRST (NEXT) PROCESS HOST
`ID OF THE LOCAL ID PORTION OF AN IP
`ADDRESS FOR THE NETWORKADDRESSING
`SCHEME WHEREIN THE HOST ID IS NOT
`CURRENTLY BEING USED TO ADDRESS A
`PROCESS INTERFACE OF
`COI).IP ADRSABLE LIST THAT ALSO
`COMMUNICATES VIA CO LAN
`
`T
`428
`
`ASSIGN THE IP-ADDRESS,
`NTWK IDLAN/ROUTER ID.HOST ID, TO THE
`PROCESS INTERFACE FOR THE IDENTIFIER HOST
`
`IS THERE ANOTHER
`PROCESS INTERFACE OF
`COI).IP ADRSABLE LIST
`THAT COMMUNICATES
`WITH CO LAN AND THAT
`HAS NOT BEEN ASSIGNED
`AN IP-ADDRESS
`
`IS THERE ANOTHER LAN 196
`OR ROUTER 204 IN COI?
`
`YES
`
`432
`
`YES
`
`436
`
`NO
`
`K --
`
`440
`
`YES
`
`I > NBR COS'?
`
`444
`
`NO
`
`END
`
`FIG 4B
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 8 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 8 of 17
`
`5,764,756
`
`FIG 5A
`
`START
`
`LET THE ARRAY, COI), I=1,2,...,NBR COS,
`REPRESENT THE CENTRAL OFFICES 120
`
`I -- 1
`
`508
`
`CONVERTER IP ADRS LIST -- THE LIST OF
`IP-ADDRESSES FOR CONVERTERS IN THE
`CENTRAL OFFICE 120 REPRESENTED BY COI)
`
`
`
`
`
`CONVERTER IP ADRS -- THE FIRST
`(NEXT) IP-ADDRESS IN
`CONVERTER IP ADRS LIST
`
`CONVERTER H THE RECORD
`REPRESENTING THE HARDWARE
`COMPONENT OF COI HAVING
`"CONVERTER IP ADRS"AS ITS
`IP-ADDRESS
`
`504
`
`512
`
`516
`
`520
`
`NBR ASYNC CARDS -- THE NUMBER OF
`ASYNCHRONOUS PROTOCOL CONVERTER CARDS
`IN THE HARDWARE COMPONENT REPRESENTED
`BY "CONVERTER"
`
`524
`
`528
`
`ASSUMING ALL ASYNCHRONOUS PROTOCOL CONVERTER
`CARDS IN THE HARDWARE COMPONENT REPRESENTED BY
`"CONVERTER" ARE IN THE FIRST PHYSICALLY CONSECUTIVE
`SLOTS OF THE COMPONENT, LET THE ARRAY, ASYNCARDJ),
`J=1,2,...,NBR ASYNC CARDS, BE SUCH THAT EACH ARRAY
`ENTRY, ASYNCARDJ), REPRESENTS ONE OF THE
`ASYNCHRONOUS PROTOCOL CONVERTER CARDS, AND THE
`ARRAY ENTRIES ARE IN THE SAME ORDER AS THE
`ASYNCHJRONOUS CARDS ARE IN THE SLOTS OF THE
`COMPONENT REPRESENTED BY "CONVERTER"
`
`:
`1
`
`:
`
`
`
`
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 9 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 9 of 17
`
`5,764,756
`
`A
`
`532
`
`FIG 5B
`
`
`
`
`
`
`
`
`
`NBR SOCKETS -- THE NUMBER
`OF SOCKETS SUPPORTED BY THE
`CARD FOR ASYNCARDJ)
`
`536
`
`LET THE ARRAY, SOCKETK, K=1,
`2,...,NBR SOCKETS, REPRESENT THE PHYSICAL
`SOCKET PORTS ON THE ASYNCHRONOUS CARD
`REPRESENTED BY ASYNCARDJWHEREIN THE
`ENTRIES IN THE ARRAY ARE IN THE SAME ORDER
`AS THE PHYSICAL SOCKET PORTS ARE ON THE
`CARD FOR ASYNCARDJ)
`
`540
`
`SOCKETADRS - 10,000 + (J*100)+K
`
`548
`
`ASSIGN AN IP-ADDRESS EXTENDED BY A SOCKET
`ADDRESS TO THE PROCESS INTERFACE OF
`COI). SOCKET ADRSABLE LIST COMMUNICATING
`WITH THE SOCKET FORSOCKETK); SPECIFICALLY,
`ASSIGN THE ADDRESS OBTAINED FROM
`CONCATENATING CONVERTER IP ADRS WITH
`SOCKET ADRS
`
`552
`
`NO CKNBR sockets
`
`560
`
`YES
`
`J - J--
`
`562
`
`NO g) J>NBR ASYNC CARDS?
`564
`YES
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 10 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 10 of 17
`
`5,764,756
`
`
`
`IS THERE A NEXT IP-ADDRESS IN
`"CONVERTER IP ADRS LIST"?
`
`
`
`572
`
`C DNBR COS'
`YES
`
`
`
`FIG. 5C
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 11 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 11 of 17
`
`5,764,756
`
`FG 6A
`
`START
`
`LET THE ARRAY, COI), I=1,2,...,NBR COS,
`REPRESENT THE CENTRAL OFFICES 120;
`
`608
`
`-- 1
`
`604
`
`62
`
`CONVERTER IP ADRS LIST -- THE LIST OF
`IP-ADDRESSES FOR PROTOCOL CONVERTERS IN COI
`
`CONVERTER IP ADRS -- THE FIRST (NEXT)
`IP-ADDRESS IN CONVERTER IP ADRS LIST
`
`616
`
`CONVERTER - RECORD REPRESENTING THE
`HARDWARE COMPONENT OF COI HAVING
`"CONVERTER IP ADRS"AS ITS IP-ADDRESS
`
`620
`
`624
`
`NBR SYNC CARDS -- THE NUMBER OF SYNCHRONOUS
`PROTOCOL CONVERTER CARDS IN "CONVERTER"
`
`
`
`ASSUMING ALL SYNCHRONOUS PROTOCOL CONVERTER
`CARDS IN THE HARDWARE COMPONENT REPRESENTED BY
`"CONVERTER" PHYSICALLY FOLLOW, IN CONSECUTIVE
`SLOTS, THE (ANY) ASYNCHRONOUS PROTOCOL
`CONVERTER CARDS ALSO IN THE COMPONENT, LET THE
`ARRAY, SYNCARDJ), J=1,...,NBR SYNC CARDS, BE SUCH
`THAT EACH ARRAY ENTRY, SYNCJ), REPRESENTS ONE OF
`THE SYNCHRONOUS PROTOCOL CONVERTER CARDS, AND
`THE ARRAY ENTRIES ARE IN THE SAME ORDER AS THE
`SYNCHRONOUS CARDS ARE IN THE SLOTS OF THE
`COMPONENT REPRESENTED BY "CONVERTER"
`
`628
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 12 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 12 of 17
`
`5,764,756
`
`632
`
`NBR SOCKETS -- THE NUMBER OF
`SOCKETS SUPPORTED BY SYNCARDJ)
`
`636
`
`640
`
`LET THE ARRAY, SOCKETK), K=1,2,...,NBR SOCKETS,
`REPRESENT THE PHYSICAL SOCKET PORTS ON THE
`SYNCHRONOUS CARD REPRESENTED BY
`SYNCARDJ) WHEREIN THE ENTRIES IN THE ARRAY
`ARE IN THE SAME ORDER AS THE PHYSICAL SOCKET
`PORTS ARE ON THE CARD FOR SYNCARDJ)
`
`:
`
`K -H 1
`
`644
`
`warm-www.m-r-ram-mar-
`
`648
`
`NBR LOGICAL CHANNELS -- THE NUMBER OF
`LOGICAL CHANNELS SUPPORTING ASYNCHRONOUS
`PROCESS INTERFACE ON SOCKETK), EACH PROCESS
`INTERFACE BEING IN COI). SOCKET ADRSABLE LIST
`
`LCN --
`
`652
`
`LOGICAL CHANNEL ADRS -- 11,000 + (J-1)*2000) +
`K* 100 + LCN
`
`656
`
`
`
`ASSIGN TO THE PROCESS INTERFACE COMMUNICATING
`VLA SOCKETKON THE LOGICAL CHANNEL HAVING
`CHANNEL NUMBER, LCN, AN EXTENDED IP-ADDRESS;
`SPECIFICALLY, ASSIGN THE ADDRESS OBTAINED FROM
`CONCATENATING CONVERTER IP ADRS WITH
`LOGICAL CHANNEL ADRS
`
`660
`
`FIG. 6B
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 13 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 13 of 17
`
`5,764,756
`
`t
`
`LCN -- LCN + 1
`
`664
`
`K > N B R S O CKE T S 9
`
`680
`
`> NBR SYNC CARDS?
`
`
`
`—
`
`IS THERE A NEXT IP-ADDRESS IN
`"CONVERTER IP ADRS LIST"
`
`F.G. 6C
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 14 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 14 of 17
`
`5,764,756
`
`FIG 7A
`
`START
`
`
`
`
`
`
`
`AN OFFSITE AGENT PLACES A CALL TO THE DIAL ACCESS
`COMMUNICATION UNIT 208
`
`ROUTER 204 ANSWERS THE CALL AND PROMPTS FOR
`AGENT'S LOG-IN IDENTIFICATION AND THE
`PERIODICALLY CHANGING PASSWORD PROVIDED BY THE
`TRANSPORTABLE PASSWORD ASSIGNMENT UNIT 224
`
`704
`
`708
`
`ROUTER 204 ENCAPSULATES AGENT LOG-IN IDENTIFICATION
`AND RECEIVED PASSWORD IN A TCP/IP PACKET AND SENDS
`THE PACKET, VIA COMMUNICATION LINES 184 AND WAN 124,
`TO THE CENTRALIZED SECURITY CENTER 132
`
`712
`AFTER THE LOG-IN IDENTIFICATION AND PASSWORD
`HAVE BEEN ROUTED TO THE ACCESS SECURITY
`SERVER 168, THIS SERVER DETERMINES WHETHER
`THE AGENT CAN BE AUTHENTICATED BY THE ACCESS
`SECURITY SERVER 168?
`
`716
`
`NO
`
`YES
`
`728
`
`
`
`720
`
`USING THE AGENT'S LOG-IN
`IDENTIFICATION, THE ACCESS
`SECURITY SERVER 168
`RETRIEVES THE AGENT'S
`ACCESS PERMISSIONS FROM
`THE ACCESS PERMISSIONS
`DATA BASE 76 AND SENDS
`THESE PERMISSIONS ALONG
`WITH ACCESS APPROVAL TO
`THE ROUTER 204 VIA
`COMMUNICATION LINES 84
`AND WAN 124
`
`ACCESS DENIAL CODE IS
`RETURNED TO THE
`ROUTER 204, VIA
`COMMUNICATION LINES
`184 AND WAN 124;
`ROUTER 204 THEN DENIES
`ACCESS TO THE AGENT
`
`THE AGENT'S CALL IS
`TERMINATED
`
`END
`
`724
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 15 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 15 of 17
`
`5,764,756
`
`ACCESS SECURITY SERVER 168 LOGS THE AGENT'S ACCESS
`REQUEST AND A TIMESTAMP OF THE REQUEST
`
`732
`
`THE ROUTER 204 RECEIVES ACCESS APPROVAL FROM ACCESS
`SECURITY SERVER 168, LOADS THE RECEIVED ACCESS
`PERMISSIONS INTO A PERMISSIONS STORAGE AREA, AND
`ISSUES AN ACCESS APPROVED MESSAGE TO THE AGENT
`
`736
`
`
`
`
`
`
`
`
`
`
`
`THE AGENT SELECTS THE COMMUNICATION PROTOCOLTO
`BE USED AND REQUESTS ACCESS TO A PROCESS
`INTERFACE OF A COMMUNICATION PORT USING THE
`TELEPHONY PROVIDERENTERPRISE-WIDE IP-ADDRESSING
`SCHEME FOR PROCESS INTERFACES
`
`
`
`
`
`
`
`ROUTER 204 USES THE AGENTS
`STORED PERMISSIONS TO DETERMINE
`WHETHER THE AGENT IS PERMITTED
`744
`TO ACCESS THE REQUESTED IP-
`ADDRESSED PROCESS INTERFACE,
`{OS
`
`ACCESS NOT PERMITTED
`
`
`
`
`
`
`
`ACCESS
`PERMITTED
`
`IS THE REQUESTED
`PROCESS INTERFACE
`CONNECTED TO A
`TERMINAL EMULATION
`PORT 214 ON THE ROUTER
`204?
`
`754
`
`
`
`748
`
`YES
`
`
`
`
`
`740
`IS THIS THE
`THIRD
`CONSECUTIVE
`ATTEMPT BY
`AGENT TO
`ACCESSA
`PROCESS
`INTERFACE TO
`WHICH
`PERMISSION IS
`NOT GRANTED
`NO
`
`FIG. 7B
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 16 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 16 of 17
`
`5,764,756
`
`
`
`ROUTER 204
`BROADCASTS TOITS
`TERMINAL
`EMULATION PORTS
`214 THE IP-ADDRESS
`OF THE REQUESTED
`PROCESS INTERFACE
`
`ROUTER 204 SENDS A TCP/IP
`PACKET TO THE LAN HUB 196 FOR
`BROADCASTING ON THE CENTRAL
`OFFICE 120 LAN REQUESTING
`COMMUNICATION BE ESTABLISHED
`BETWEEN THE AGENT AND THE
`REQUESTED PROCESS INTERFACE
`
`ROUTER 204 OUTPUTS
`A BANNER MESSAGE
`TO THE AGENT
`INDICATING ACCESS
`TO THE REQUESTED
`PROCESS INTERFACE
`IS BEING GRANTED
`
`UPON RECEIVING THE
`BROADCASTED TOP/IP PACKET,
`THE COMMUNICATION PORT
`HAVING THE AGENT SPECIFIED IP
`ADDRESS RESPONDS, VIA LAN HUB
`196, TO THE INITIAL TCP/IP PACKET
`FROM ROUTER 204 BY SENDING A
`RESPONSIVE TCP/IP PACKET
`INDICATING COMMUNICATIONS
`WITH THE REQUESTED PROCESS
`INTERFACE CAN BE ESTABLISHED,
`PLUS A BANNER MESSAGE FOR THE
`AGENT
`
`THE TERMINAL EMULATION ROUTERPORT
`CORRESPONDING TO THE IP-ADDRESS
`INITIALIZES THE ASYNCHRONOUS LINE 216 TO
`THE NETWORKELEMENT PROCESS
`INTERFACE CONSOLE PORTALSO
`CORRESPONDING TO THE IP-ADDRESS.
`
`ASSUMING THE CONSOLE PORT RESPONDS, THE
`CONSOLE PORT OUTPUTSA BANNER MESSAGE FOR
`THE AGENT AND COMMUNICATIONS BETWEEN THE
`AGENT AND THE CONSOLE PORT ARE ESTABLISHED
`
`FIG. 7C
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 17 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`U.S. Patent
`
`Jun. 9, 1998
`
`Sheet 17 of 17
`
`5,764,756
`
`
`
`
`
`ROUTER 204 PROMPTS FOR A
`NEW PROCESS INTERFACE
`FROM THE AGENT
`
`ROUTER 204 RESETS THE
`PREVIOUSLY REQUESTED
`PROCESS INTERFACE
`
`796
`
`788
`
`ROUTER 204 MANTAINS A
`COMMUNICATIONS
`ROUTE BETWEEN THE
`AGENT AND THE
`REQUESTED PROCESS
`INTERFACE
`
`THE AGENT AND THE REQUESTED PROCESS
`INTERFACE COMMUNICATE WITH ONE ANOTHER
`
`772
`
`776
`
`
`
`THE AGENT TERMINATES THE COMUNICATION WITH
`THE REQUESTED PROCESS INTERFACE BY: (a) A
`SOFTWARE LOG-OFF, OR (b) HANGING UP THE PHONE
`
`792
`
`YES
`
`
`
`
`
`ROUTER 204 TERMINATES
`THE AGENT'S CALL
`
`IS AGENT STILL ON-LINE
`WITH THE ROUTER 204?
`
`
`
`750
`
`NO
`
`THE ROUTER 204 DISCARDS THE AGENT'S STORED
`PERMISSIONS AND RESETS ANY PROCESS
`INTERFACE ACCESSED FOR A NEXT ACCESS
`
`752
`
`END
`
`FIG. 7D
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 18 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`5,764,756
`
`1.
`NETWORKED TELEPHONY CENTRAL
`OFFICES
`
`FIELD OF THE INVENTION
`The present invention relates to a communications net
`working system for controlling and monitoring performance
`of and access to a telephony central office. In particular, the
`networking system provides enhancements in restricting
`undesirable access to central office facilities and in simpli
`fying central office communications by providing a local
`area network in the central office.
`
`2
`24 maybe utilized for communicating in anyone of a
`number of telephony network management application
`protocols, for example:
`(i) CMIP/CMIS, an application protocol for managing
`telephony network elements. In particular, CMIP/
`CMIS is used for communicating with network ele
`ment communication ports, that utilize OSInetwork
`ing standards as provided by the International
`organization for Standardization (ISO), ISO-8073,
`Ot,
`(ii) SNMP (Simple Network Monitoring Protocol), a
`standardized internet network management protocol
`for monitoring network elements having communi
`cation ports utilizing the IP
`(1.2) The public telephone network 28 for allowing cen
`tral office off-site technicians dial access to a central
`office 20 for monitoring and/or correcting network
`element 48 malfunctions;
`(1.3) An asynchronous proprietary network 52 for estab
`lishing communications between network element 48
`data ports and “UNDX" based host systems at OSSs 10
`of the data center 14, wherein a proprietary network
`protocol such as "URP” by Datakit is used. Note that a
`terminal/host computational paradigm may be used
`between a network element and OSSs when commu
`nicating using the network 52. That is, the network
`element, or more precisely, one of its data ports,
`behaves like a terminal in that it is controlled by a
`single host OSS 10 computational device and therefore
`the data port is dependent on this host for instructing it
`as to when it should communicate with the host:
`(1.4) One or more private point-to-point lines 56 between
`a central office 20 and a data center 14, wherein
`transmissions on these dedicated lines may use any
`number of protocols. However, it may be likely that
`such transmissions do not use any protocol whatsoever
`since such point-to-point lines often are viewed as an
`extension of the network elements 48 so that the
`operating systems of the network elements are acces
`sible from a remote location such as data center 14:
`(1.5) A X.25 network 54 for communicating using the
`X.25 communication protocol, wherein information is
`encapsulated in (or converted to) X.25 packets for
`transmission. Note that a packet assembler/
`disassembler 56 must be provided at each terminating
`node of this network to decode and encode X.25
`packets from and to the network 54, respectively.
`Further note that a protocol translator 58 may be
`connected between packet assembler/disassembler 56
`and the network elements 48 for translating the proto
`col of the disassembled X.25 information into one or
`more specialized network element 48 protocols such as:
`(i) E2A: a telephony protocol developed by AT&T for
`transmitting state changes and alarm notices between
`legacy network elements and associated OSSs.
`(ii) Synder: a synchronous protocol developed by
`AT&T for use in controlling digital access to tele
`phony cross connect equipment,
`(iii) TBOS: a protocol developed by AT&T for use in
`providing network element alarms to an OSS. This
`protocol is based on a structured block of 512 bits.
`BX.25: a protocol defined by AT&T Bell Laboratories
`for use in providing multiple communication ses
`sions or connections over a single communication
`channel. This protocol is used only on AT&T manu
`factured equipment.
`(1,6) One or more synchronous networks 60 for support
`ing primarily IBM host applications of OSSs 10 that
`
`BACKGROUND OF THE INVENTION
`The incremental deployment of progressively newer tech
`nologies by telephony service providers has created, in
`many cases, a wide range of telecommunications equipment
`and operations that must be integrated to provide reliable
`service to subscribers. For example, a telephony provider
`may have network elements and operational support systems
`(OSSs) that have been in place for years (known in the art
`as legacy systems) as well as newer network elements and
`their associated OSSs that allow more efficient and/or more
`comprehensive operational support. Thus, there have been.
`in some cases, substantial duplications of the same func
`tionality using different technologies within service sites for
`telephony service providers.
`The above statements are particularly true for telephony
`provider central offices and the OSSs to which the central
`offices connect. In particular, referring to prior art FIG. 1,
`note that although certain OSSs 10 may be physically
`coalesced in a single data center 14 as shown, there may be
`a substantial number of different communication technolo
`gies used to monitor and control central offices 20 from such
`remote locations as data center 14. FIG. 1 illustrates six
`communication technologies typically used in externally
`communicating with and controlling devices within central
`offices 20 from remote locations. They are:
`(1.1) ATCP/IP wide area network 24 for high bandwidth
`communications using the well known standardized
`TCP/IP protocol. Note that the term wide area network
`(WAN) is hereinafter intended to refer to any physical
`network technology that spans larger geographical dis
`tances (e.g., from tens to thousands of miles). Further
`note that TCP/IP is an abbreviation for Transmission
`Control Protocol/Internet Protocol wherein the Internet
`Protocol is known as a "network layer" protocol and
`the Transmission Control Protocol is known as a "trans
`port layer" protocol that is constructed on top of the
`Internet Protocol. Thus, the Internet Protocol (IP) is
`responsible for establishing, maintaining, and terminat
`ing a network connection between two communicating
`network nodes. The IP is also responsible for transfer
`ring information along an established connection. The
`TCP, on the other hand, is responsible for providing
`information between communicating network nodes
`wherein there is an agreed upon level of communica
`tion quality. In particular, TCP transmits data as full
`duplex data streams across a particular networkpath or
`"connection" that has been determined between the
`communicating network nodes. Further TCP/IP is
`widely used as a foundation upon which higher level or
`"application layer” protocols depend. More precisely,
`TCP/IP is a fourth layer protocol, wherein the higher
`layers are denoted: the session layer (5"), presentation
`layer (6") and the application layer (7"). Thus, (as one
`skilled in the art will understand) the TCP/IP network
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`45
`
`SO
`
`55
`
`65
`
`Hewlett Packard Enterprise Co. Ex. 1024, Page 19 of 34
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01378
`
`

`

`5,764,756
`
`5
`
`25
`
`35
`
`3
`require communications with various legacy devices
`(i.e. technologically outdated devices) such as devices
`using 3270 terminal emulation software. Note that in
`some cases communications on these networks use a
`bisynchronous polled protocol wherein the absence of
`constant polling by an OSS 10 renders the legacy
`devices and printers 64 attached to synchronous cluster
`controller 66 useless.
`Given the lack of integration between external commu
`nication connections to a central office 20 as FIG. 1
`10
`illustrates, it is not surprising that it is very difficult to
`provide a uniform or consistent management of the external
`communications on these connections. Moreover, note that
`although FIG. 1 shows only a single communication line 80
`between various communication ports on network elements
`48 and other central office devices communicating with the
`central office external connections, it is important to note
`that the thick lines within central office 20 represent a
`plurality of distinct communication lines having, potentially,
`a distinct communication line per network element 48. Thus,
`there is potentially a large number of communication lines
`80 internal to each central office 20 to be managed.
`However, since the communication lines 80 have no device
`in common, it is substantially not possible to uniformly
`manage the communication in such a center office.
`Further note that due substantially to the lack of uniform
`management of both external and internal communications
`of a central office 20, there are minimal security features to
`prohibit unauthorized access to a central office 20 as well as
`potentially other telephony provider sites via one of the
`external connections once access to a central office 20 is
`obtained. In particular, there may be substantial risk that
`hackers gain access to, for example, network elements 48 in
`a central office 20 via an off-site processing unit 72 (e.g., a
`combination of a personal computer and a modem) and the
`public telephone network 28. Further, there is a risk that if
`a hacker gains access to a central office 20, then he/she may
`be able to also gain access to other central offices 20 or a data
`center 14 by navigating central office external connections.
`Thus, it would be advantageous to have a central office
`architecture that allows better management and increased
`security for both internal and external communications of a
`central office. In particular, it would be advantageous to have
`a central office architecture wherein the internal communi
`cations are routed through one or more common devices
`allowing both better access permissions checking and reduc
`ing the number of distinct communication lines between
`central office devices. Further, it would be advantageous to
`have a central office architecture wherein communications
`between telephony provider service sites are provided sub
`50
`stantially by a single wide area network wherein security
`measures may be applied straightforwardly and uniformly.
`SUMMARY OF THE INVENTON
`The present invention is a system and method for
`remotely controlling a telephony central office wherein a
`local area network (LAN) for the central office is used for
`communication with substantially every network element at
`the central office. In a preferred embodiment, the system and
`method of the present invention provides a central office
`local area network architecture wherein substantially all
`external communications with the central office are routed
`through the local area network. Thus, external communica
`tions between a telephony centralized control center or
`operational support system (OSS) and communication ports
`of network elements at a central office utilizing the present
`invention must use the local area network.
`
`4
`Additionally, in providing a local area network for a
`central office utilizing the present invention, it is an aspect
`of the LAN to be ethernet based as defined in, for instance.
`IEEE standard 802.3 which may be obtained from the
`Institute of Electrical and Electronic Engineers and which is
`hereby incorporated by reference. Thus, such a LAN pro
`vides a cost effective, high data rate (e.g., 10 megabytes per
`second) capability for communicating with substantially all
`telephony components at the central office. Moreover, it is a
`further aspect that the LAN include a LAN hub through
`which all LAN communications are routed. Thus, for
`example, central office cabling becomes substantially more
`understandable and less complex.
`Note that in funnelling external communications with the
`central office through such a local area network, an address
`ing scheme is necessary for uniquely identifying each com
`munication port of each network element at a central office.
`Further note that since the present invention is contemplated
`for utilization at a plurality of central offices of a telephony
`provider, wherein the central offices are connected to the
`same wide area network (WAN) for allowing a centralized
`control center to control the network elements at the central
`offices, it is an aspect of the present invention that such an
`addressing scheme must uniquely identify each network
`element communication port across the plurality of such
`central offices. In particular, it is preferred that the commu
`nication port addresses of the addressing scheme be Internet
`Protocol (IP) addresses of 32 bits that are extended with
`additional information in a manner wherein various fields
`within each such extended address provide information
`regarding both the location and type of the communication
`port to which the address is assigned. Thus, for example, it
`is preferred that each such extended IP-address