ESN LLC v. Cisco Systems, Inc. et al

Filing 94

NOTICE OF FILING OF OFFICIAL TRANSCRIPT of Proceedings held on June 10, 2009, Tutorial, 48 pages, before The Honorable Chief Judge David Folsom. Court Reporter: Libby Crawford, CSR, Telephone number: 903.794.4067 Ext 237 or [e-mail]. NOTICE RE REDACTION OF TRANSCRIPTS: The parties have seven (7) business days to file with the Court a Notice of Intent to Request Redaction of this transcript. If no such Notice is filed, the transcript will be made remotely electronically available to the public without redaction after 90 calendar days. The policy is located on our website at www.txed.uscourts.gov Transcript may be viewed at the court public terminal or purchased through the Court Reporter/Transcriber before the deadline for Release of Transcript Restriction. After that date, it may be purchased from the Court Reporter or PACER. Redaction Request due 7/16/2009. Redacted Transcript Deadline set for 7/27/2009. Release of Transcript Restriction set for 9/23/2009. (aec, )

ESN LLC v. Cisco Systems, Inc. et al

Doc. 94

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 APPEARANCES: FOR PLAINTIFF ESN, L.L.C.: ESN, L.L.C. VS.

IN THE UNITED STATES DISTRICT COURT FOR THE EASTERN DISTRICT OF TEXAS TEXARKANA DIVISION . . . . CIVIL ACTION NO. 5:08CV20 TEXARKANA, TEXAS JUNE 10, 2009 1:56 P.M.

CISCO SYSTEMS, INC., ET AL.

TUTORIAL BEFORE THE HONORABLE CHIEF JUDGE DAVID FOLSOM, UNITED STATES DISTRICT JUDGE.

MR. GERALD C. WILLIS, JR. MR. PETER J. MCANDREWS MCANDREWS HELD & MALLOY 500 W. MADISON STREET SUITE 3400 CHICAGO, IL. 60661 MR. THOMAS JOHN WARD, JR. WARD & SMITH LAW FIRM P.O. BOX 1231 LONGVIEW, TX. 75606-1231

FOR DEFENDANT CISCO SYSTEMS, INC.:

MR. CHARLES K. VERHOEVEN QUINN EMANUEL URQUHART OLIVER & HEDGES, L.L.P. SAN FRANCISCO 50 CALIFORNIA STREET 22ND FLOOR SAN FRANCISCO, CA. 94111 MR. MICHAEL EDWIN JONES POTTER MINTON, P.C. 110 N. COLLEGE SUITE 500 P.O. BOX 359

Dockets.Justia.com

-21 2 3 4 5 COURT REPORTER: 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 PROCEEDINGS RECORDED BY STENOMASK VERBATIM REPORTING, TRANSCRIPT PRODUCED BY CAT SYSTEM. MS. LIBBY CRAWFORD, CSR OFFICIAL COURT REPORTER 500 STATE LINE AVENUE TEXARKANA, TEXAS 75501 903/794-4067 TYLER, TX. 75710-0359 MS. SAYURI K. SHARPER QUINN EMANUEL URQUHART OLIVER & HEDGES - REDWOOD 555 TWIN DOLPHIN DR. SUITE 560 REDWOOD SHORES, CA. 94065

-31 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 INDEX THE COURT.................................................. PLAINTIFF'S TUTORIAL BY MR. MCANDREWS...................... 4 4

DEFENDANT'S TUTORIAL BY MS. SHARPER........................ 25 THE COURT.................................................. 46 REPORTER'S CERTIFICATION................................... 48

-41 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 (OPEN COURT) THE COURT: PLEASE BE SEATED. ARE HERE FOR A TUTORIAL. MINUTES. GOOD AFTERNOON. WE PROCEEDINGS TEXARKANA, TEXAS JUNE 10, 2009

I HAVE GIVEN EACH SIDE UP TO 45

ARE THE PARTIES READY TO GO FORWARD? MR. MCANDREWS: WE ARE, YOUR HONOR. MR. JONES: WE ARE, YOUR HONOR. THE COURT: THEN PLAINTIFF MAY GO FORWARD. MR. MCANDREWS: GOOD MORNING, YOUR HONOR. MY NAME IS

PETER MCANDREWS.

I REPRESENT ESN, THE PLAINTIFF IN THE CASE.

I AM GOING TO PROVIDE WHAT I HOPE TO BE A BRIEF TUTORIAL ON THE SOLE PATENT-IN-SUIT, U.S. PATENT NUMBER 7,283,519, WHICH I WILL REFER TO AS THE `519 PATENT. I AM HOPING TO KEEP THIS

BRIEF, AND IF YOU BELIEVE THAT FROM A PATENT ATTORNEY, THEN I HAVE A GOOD AUTOMOBILE DEALERSHIP I HAVE TO SELL YOU DOWN THE ROAD HERE. BUT I'LL KEEP IT AS BRIEF AS POSSIBLE. AND I

THINK I CAN DO THAT BECAUSE THE UNDERLYING TECHNOLOGIES IN THIS CASE ARE REALLY NOT THAT COMPLEX TO UNDERSTAND AT THE LEVEL NECESSARY FOR OUR PURPOSES OVER THE NEXT TWO DAYS. THE PARTIES ARE ALSO LARGELY IN AGREEMENT ON THE UNDERLYING TECHNOLOGIES. OF COURSE THERE ARE DISPUTES ABOUT

THE PRECISE DEFINITIONS OF CERTAIN TERMS AND PHRASES, BUT THOSE WILL BE ADDRESSED IN THE CLAIM CONSTRUCTION HEARING

-51 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 TOMORROW. THE `519 PATENT IS ENTITLED: DISTRIBUTED EDGE SWITCHING SYSTEM FOR VOICE-OVER-PACKET MULTISERVICE NETWORK. FILED IN APRIL OF 2002. IT WAS

IT ISSUED OCTOBER 16, 2007, AND THE

SOLE INVENTOR IS GREGORY D. GIRARD OF MASSACHUSETTS. THE TITLE OF THE PATENT IS ACTUALLY A GOOD PLACE TO START WITH THE TUTORIAL BECAUSE IT INTRODUCES SOME OF THE MOST BASIC CONCEPTS DEALT WITH BY THE `519 PATENT. ONE OF THE CONCEPTS

IS FOUND IN THE TERM VOICE-OVER-PACKET MULTISERVICE NETWORK. THIS TERM REFERS TO THE FACT THAT THE `519 PATENT IS DIRECTED TO A SYSTEM FOR PROVIDING VOICE COMMUNICATIONS OVER A NETWORK THAT TRANSMITS VOICE DATA IN BUNDLES REFERRED TO AS PACKETS. THE TERM MULTISERVICE REFERS TO THE FACT THAT THE VOICE DATA PACKETS ARE TRANSMITTED OVER A NETWORK THAT IS ALSO USED TO COMMUNICATE OTHER TYPES OF DATA PACKETS SUCH AS EMAIL AND SO ON. A UNIVERSALLY RECOGNIZED EXAMPLE OF SUCH A NETWORK IS THE INTERNET. VOICE COMMUNICATIONS OVER THE INTERNET IS COMMONLY

REFERRED TO AS VOICE OVER INTERNET PROTOCOL, OR VOIP, V-O-I-P. ANOTHER BASIC CONCEPT INTRODUCED BY THREE WORDS OF THE TITLE, THE FIRST THREE WORDS, IS DISTRIBUTED EDGE SWITCHING. THIS

PHRASE REFERS TO THE FACT THAT THE PATENT DISCLOSES A SYSTEM IN WHICH DEVICES ARE DISTRIBUTED ABOUT THE EDGE OF A NETWORK, FOR EXAMPLE, THE INTERNET. FUNCTION. THESE DEVICES PROVIDE A SWITCHING

SWITCHING GENERALLY REFERS TO THE PROCESS OF

-61 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 PSTN. SETTING UP AND CONTROLLING A PHONE CALL BETWEEN TWO ENDPOINTS. THIS IS IN CONTRAST TO A SYSTEM SUCH AS THE PUBLIC TELEPHONE SYSTEM THAT I'LL DISCUSS IN A LITTLE MORE DETAIL IN A MINUTE AS BACKGROUND. THE PUBLIC TELEPHONE SYSTEM RELIES ON A SYSTEM

OF CENTRALLY LOCATED SWITCHES TO PROVIDE TELEPHONE SERVICE. NOW, IN THE BACKGROUND DISCUSSION OF THE PATENT, A FIGURE IS PROVIDED THAT DISCLOSES THE PUBLIC PHONE SYSTEM. CALLED THE PUBLIC SWITCHED TELEPHONE NETWORK OR PSTN. IT'S I'LL BE

USING THAT ABBREVIATION, PSTN, THROUGHOUT THE NEXT SEVERAL MINUTES TO REFER TO THE TELEPHONE SYSTEM THAT MOST OF US HAVE KNOWN DURING MOST OF OUR LIVES, AND IT INCLUDES TO BE THE DOMINANT PHONE SYSTEM IN THE WORLD TODAY. FIGURE 1 ILLUSTRATES SOME OF THE BASIC COMPONENTS OF THE THERE ARE OF COURSE TELEPHONES AND THOSE ARE THE PHONES

THAT YOU WOULD HAVE IN YOUR OFFICE, HERE IN THE COURTHOUSE, OR AT YOUR HOME. THE PHONES ARE CONNECTED TO SWITCHES. THESE

SWITCHES AGAIN ARE THE SWITCHES THAT ARE GOING TO CONNECT ENDPOINTS, THE PHONES, TO EACH OTHER. THE SWITCHES ARE

CONNECTED TO A SIGNALING NETWORK THAT ALLOWS THE SWITCHES TO COMMUNICATE INFORMATION TO EACH OTHER FOR THE PURPOSE OF ALLOWING ONE SWITCH TO CONNECT A CALL THROUGH TO ANOTHER SWITCH. AND FINALLY THERE IS A TRANSPORT NETWORK THROUGH

WHICH A CIRCUIT IS MADE FOR COMMUNICATING VOICE SIGNALS BETWEEN A PHONE CONNECTED TO ONE SWITCH AND A PHONE CONNECTED TO ANOTHER SWITCH.

-71 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 NOW, THE PSTN RELIES ON WHAT IS CALLED CIRCUIT SWITCHING. FOR PURPOSES OF THIS DISCUSSION IT IS MOST USEFUL TO UNDERSTAND CIRCUIT SWITCHING AS A CONTRAST WITH PACKET SWITCHING. NEWTON'S TELECOM DICTIONARY PROVIDES SUCH A

DISCUSSION OF CIRCUIT SWITCHING IN ITS DEFINITION OF PACKET SWITCHING. AND IT SAYS: HERE IS ANOTHER WAY OF EXPLAINING THERE ARE TWO BASIC WAYS OF MAKING A CALL.

PACKET SWITCHING:

FIRST, THE ONE EVERYONE'S FAMILIAR WITH ­- THE COMMON PHONE CALL. YOU DIAL. THE LOCAL SWITCH FINDS AN UNUSED PATH TO THE WHILE YOU ARE SPEAKING, THE IT'S DEDICATED TO THE CIRCUIT

PERSON YOU CALLED AND JOINS YOU. CIRCUIT IS 100 PERCENT ALL YOURS. CONVERSATION.

THIS IS CALLED CIRCUIT SWITCHED.

SWITCHING IS THE WAY THE WORLDWIDE PHONE SYSTEM WORKS, ALSO CALLED THE PSTN. SO, CIRCUIT SWITCHING CREATES A CONNECTION

OR CIRCUIT BETWEEN TWO PARTIES TO A TELEPHONE CALL WHERE THE CIRCUIT IS DEDICATED SOLELY TO THAT TELEPHONE CALL. IN OTHER

WORDS, THE CIRCUIT IS NOT SHARED WITH ANY OTHER PHONE CALLS OR OTHER TYPES OF DATA. THE PARTIES ARE IN GENERAL AGREEMENT ON THIS PART OF THE BACKGROUND AS IT RELATES TO CIRCUIT SWITCHING IN THE PSTN. CISCO'S EXPERT WITNESS, DR. BURGER, STATES: THE PSTN IS A CIRCUIT-SWITCHED NETWORK, WHICH MEANS THAT WHEN A TELEPHONE CALL IS CONNECTED, A CIRCUIT BETWEEN THE TWO TELEPHONES IS ESTABLISHED THAT IS DEDICATED SOLELY TO THE CALL. CIRCUIT IS NOT SHARED WITH OTHER DATA. THAT

-81 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 NOW THE CIRCUIT SWITCHING IN A PSTN IS PERFORMED BY A SYSTEM OF CENTRALLY DEPLOYED SWITCHES. IN FACT, THE SWITCHES

DEPICTED IN FIGURE 1 ARE REFERRED TO AS CENTRAL OFFICE SWITCHES. THEY ARE DEPLOYED IN WHAT IS COMMONLY REFERRED TO MOST TOWNS AND CITIES WILL HAVE ONE OR THESE

AS THE CENTRAL OFFICE.

MORE CENTRAL OFFICES THAT HOUSE THESE SWITCHES.

FACILITIES ARE TYPICALLY OWNED AND OPERATED BY A LOCAL OR REGIONAL TELEPHONE COMPANY. IN FACT, OFTENTIMES THESE ARE THE

VERY SAME BUILDINGS IN WHICH OPERATORS OF PHONE SYSTEMS PAST ACTUALLY RAN AROUND AND PULLED AND PUSHED PLUGS TO MAKE CONNECTIONS. SO IT'S USUALLY THE SAME CONCRETE BUNKER

BUILDING, ONLY NOW THE WINDOWS ARE BLACKED OUT BECAUSE ALL YOU HAVE IN THERE IS A BUNCH OF COMPUTER HARDWARE. IN THE PSTN THE ONLY EQUIPMENT THAT IS LOCATED ON A CUSTOMER PREMISE IS THE PHONE. THESE PHONES DO NOT HAVE TO

INCLUDE ANY INTELLIGENCE BECAUSE THEY RELY ON A CENTRAL OFFICE SWITCH TO MAKE CONNECTIONS FOR THEM. THE PHONES ARE LITERALLY

REFERRED TO AS PLAIN OLD TELEPHONE SERVICE TELEPHONES OR P-O-T-S, POTS PHONES. AND YOU WILL HEAR POTS PHONES REFERRED THE TELEPHONES ARE

TO THROUGHOUT THE NEXT DAY OR TWO.

CONNECTED OVER A WIRE, SUCH AS A COPPER TELEPHONE WIRE, TO THE REMOTE CENTRAL OFFICE SWITCH. THE BASIC POTS TELEPHONE HAS A SPEAKER, A MICROPHONE, AND BUTTONS THAT GENERATE TONES WHEN THEY ARE PRESSED. THE TONES,

SUCH AS THE TONES REPRESENTING A DIALED DIGIT OF A TELEPHONE

-91 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 NUMBER OR THE POUND SIGN OR AN ASTERISK, ARE COMMUNICATED OVER THE PHONE WIRES TO THE CENTRAL OFFICE SWITCH WHERE THE SWITCH TRANSLATES THOSE TONES INTO A PHONE NUMBER TO ALLOW IT TO SET UP CALLS BETWEEN PHONES LOCATED ON DIFFERENT CUSTOMER PREMISES. THE OPERATION OF A POTS TELEPHONE IS SO BASIC THAT

EVEN THE DIAL TONE IS PRODUCED BY THE CENTRAL OFFICE SWITCH. USUALLY, PHONES IN THE SAME GEOGRAPHIC REGION, LIKE IN THE SAME TOWN, ARE CONNECTED TO THE SAME CENTRAL OFFICE SWITCH SO CALLS BETWEEN THOSE PHONES ARE SET UP AND CONTROLLED BY JUST A SINGLE SWITCH. AND IN THE FIGURE HERE, YOU CAN IMAGINE

MULTIPLE PHONES ON THE RIGHT-HAND SIDE CONNECTED TO THE SAME SWITCH. HOWEVER, IF A CALL IS BEING MADE TO A PHONE CONNECTED

TO A DIFFERENT CENTRAL OFFICE SWITCH, ADDITIONAL LAYERS OF SWITCHING ARE REQUIRED TO CONNECT ONE CENTRAL OFFICE SWITCH TO ANOTHER. AND THIS PASSAGE FROM THE `519 PATENT AT COLUMN 2,

LINES 28 TO 37, EXPLAINS THE GENERAL OPERATION OF A CENTRAL OFFICE SWITCH. AND IN THE THIRD SENTENCE THERE IT SAYS: THE

SIGNALING MODULE INTERFACES WITH THE SS7 -- SS#7 TRANSPORT NETWORK FOR THE PURPOSE OF SETTING UP A BEARER CHANNEL BETWEEN THE CALLING AND CALLED CENTRAL OFFICE SWITCHES. SO THE SS7

TRANSPORT NETWORK IS AN ADDITIONAL LAYER OF SIGNALING THAT ALLOWS SWITCHES TO MAKE CONNECTIONS BETWEEN SWITCHES FOR THE PURPOSE OF CONNECTING DISTANT PHONES TO EACH OTHER. THE NEXT ITEM IN THE BACKGROUND THAT IS IMPORTANT TO UNDERSTAND IS PACKET SWITCHING. AND AS I DESCRIBED, PACKET

- 10 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 SWITCHING IS IN CONTRAST TO CIRCUIT SWITCHING. PACKET

SWITCHING NETWORKS DEVELOPED IN PARALLEL TO THE PSTN AND THEY WERE MEANT FOR GENERAL DATA TRANSMISSION. WE KNOW TODAY. THAT'S THE INTERNET

THE NEWTON'S TELECOM DICTIONARY, IN THE SAME

DISCUSSION THAT I HAD EARLIER, THAT I PROVIDED EARLIER, ALTHOUGH IT WAS TRUNCATED TO LEAVE OUT THE PORTION DISCUSSING PACKET SWITCHING, STATES THAT: PACKET SWITCHING IS DIFFERENT. IN PACKET SWITCHING, THE CONVERSATION (WHICH MAY BE VOICE, VIDEO, IMAGES, DATA, ETCETERA) IS SLICED INTO SMALL PACKETS OF INFORMATION. EACH PACKET IS GIVEN A UNIQUE IDENTIFICATION AND

EACH PACKET CARRIES ITS OWN DESTINATION ADDRESS ­- I.E., WHERE IT'S GOING. EACH PACKET MAY GO BY A DIFFERENT ROUTE. THE

PACKETS MAY ALSO ARRIVE IN A DIFFERENT ORDER THAN HOW THEY WERE SHIPPED. THE IDENTIFICATION AND SEQUENCING INFORMATION

ON EACH PACKET LETS THE DATA BE REASSEMBLED IN THE PROPER SEQUENCE. PACKET SWITCHING IS THE WAY THE INTERNET WORKS.

NOW THE IDEA THAT DATA PACKETS MAY TRAVEL TO THEIR DESTINATION BY DIFFERENT ROUTES, ARRIVE OUT OF ORDER, AND EXPERIENCE DELAYS DUE TO OTHER DATA TRAFFIC IN THE SAME NETWORK LED SOME TO BELIEVE THAT PACKET SWITCHING WAS NOT A GOOD WAY TO COMMUNICATE LIVE OR REALTIME VOICE CONVERSATIONS SUCH AS WOULD TAKE PLACE DURING A TELEPHONE CALL. YOU CAN

IMAGINE HOW FRUSTRATING IT MIGHT BE WHEN YOU SAY HELLO TO SOMEONE AND YOU DON'T GET THE HELLO COMING BACK TO YOU UNTIL LATER IN THE CALL AT SOME TIME.

- 11 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 HOWEVER, IMPROVEMENTS IN THE SPEED AND RELIABILITY OF THE INTERNET AND THE DEVELOPMENT OF EFFICIENT VOICE AND CODING TECHNIQUES EVENTUALLY LED TO THE INTRODUCTION OF VOICE OR VOICE OVER IP IN THE 1990S. THE NEWTON'S DICTIONARY COMMENTS

ON THESE DEVELOPMENTS: RECENT DEVELOPMENTS OF CERTAIN SOFTWARE AND MAKING USE OF COMPLEX COMPRESSION ALGORITHMS, HOWEVER, HAS INTRODUCED PACKETIZED VOICE AND VIDEO TO THE CORPORATE INTRANETS AND THE INTERNET, WHICH WAS THE FIRST PACKETSWITCHED NETWORK AND REMAINS BY FAR THE MOST HEAVILY USED TODAY. AND AS A QUICK ASIDE, THIS MENTIONS COMPRESSION ALGORITHMS. TECHNIQUES. WHAT THAT IS REFERRING TO IS VOICE ENCODING AND WHAT A VOICE ENCODING SYSTEM DOES IS IT TURNS

VOICE SIGNALS INTO DIGITAL DATA REPRESENTING, FOR EXAMPLE, THE FREQUENCY, VOLUME, AND OTHER PARAMETERS OF A VOICE AND THEN COMPRESSING THAT DATA SO THAT IT CAN BE EFFICIENTLY TRANSMITTED. THAT PARTICULAR IDEA IS NOT ALL THAT IMPORTANT

FOR THE OVERALL CLAIM CONSTRUCTION ARGUMENT BUT IT'S A USEFUL PIECE OF INFORMATION TO HAVE. NOW, NEWTON'S ­- THE NEWTON'S DICTIONARY DEFINITION THAT I HAVE BEEN REFERENCING WAS PUBLISHED IN 2000 AND YET IT RECOGNIZES THAT VOIP IS ONLY A RECENT DEVELOPMENT EVEN AT THAT TIME. EVEN TODAY, THE MAJORITY OF PHONE SERVICE CONTINUES TO THIS IS DUE IN PART TO THE

BE OVER THE CIRCUIT SWITCHED PSTN.

FACT THAT VOIP WAS ORIGINALLY SOMEWHAT OF A NOVELTY AND

- 12 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 SYSTEMS HAD NOT YET BEEN DEVELOPED TO ALLOW VOIP TO MIMIC ALL OF THE FEATURES OF THE PSTN THAT THE PUBLIC HAD COME TO EXPECT. IN THE MID TO LATE 1990S VARIOUS TELECOMMUNICATIONS STANDARD SETTING BODIES BEGAN WORKING ON SUCH SYSTEMS THAT WOULD ALLOW THE MIMICKING OF A PSTN. THESE SYSTEMS WERE

GENERALLY REFERRED TO AS NEXT GENERATION NETWORK OR NGN. WHILE A HUGE NUMBER OF IDEAS WERE EXPLORED, FIGURE 2 OF THE `519 PATENT ILLUSTRATES SOME OF THE COMPONENTS OF SOME OF THE MOST PROMINENT IDEAS FOR THE NGN. THE NGN, AGAIN, STILL

INCLUDED TELEPHONES AND, IN FACT, IT WAS ENVISIONED THAT THE PHONES WOULD STILL BE THE SAME POTS TELEPHONES THAT INDIVIDUALS HAD IN THEIR HOMES AND BUSINESSES. THE INDUSTRY

RECOGNIZED THAT IF THE NGN WAS GOING TO BE WIDELY ACCEPTED, IT NEEDED TO ACCOMMODATE THE PHONES CUSTOMERS ALREADY HAD ON THEIR PREMISES. TO ACCOMMODATE THESE PHONES, THOUGH, AN ADDITIONAL DEVICE CALLED A RESIDENTIAL OR MEDIA GATEWAY WAS DEPLOYED AT THE CUSTOMER PREMISES. THESE DEVICES INCLUDED THE VOICE ENCODERS

AND DECODERS THAT I MENTIONED BEFORE REFERRED TO AS A KODAK CODER DECODER OF VOICES, OF A VOICE, AND MAKING THE VOICE PACKET SUITABLE FOR TRANSMISSION OVER THE INTERNET. HOWEVER,

CONSISTENT WITH THE MODEL OF THE PSTN, THE RESIDENTIAL GATEWAY STILL RELIED ON CENTRALIZED NETWORK COMPONENTS TO SET UP AND CONTROL TELEPHONE CALLS.

- 13 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 AS THE `519 PATENT EXPLAINS IN ITS BACKGROUND SECTION, RESIDENTIAL GATEWAYS ARE UNINTELLIGENT IN THE SENSE THAT THEY REQUIRE THE MEDIA GATEWAY CONTROLLER, AND I'LL SHOW YOU WHERE THAT IS IN THE NETWORK IN JUST A MOMENT, TO MEDIATE ALL NETWORK SIGNALING FUNCTIONS ON THEIR BEHALF. THEY CANNOT

DETERMINE THE BROADER NETWORK SIGNALING CONTEXT OF THE CALLING OPERATIONS IN WHICH THEY PARTICIPATE. THEY ARE INCAPABLE OF

INDEPENDENTLY EXECUTING SERVICE LOGIC THAT INVOLVES NETWORK SIGNALING OPERATIONS, FOR EXAMPLE, CALL REDIRECTION, MULTIPOINT CALL CONTROL, CALL SUPERVISION, MULTIPLE LINE APPEARANCES, ETCETERA, WITHOUT CENTRALIZED PARTICIPATION BY SOMETHING CALLED A MEDIA GATEWAY CONTROLLER. THESE FACTORS

IMPOSE SUBSTANTIAL CONSTRAINTS ON THE VARIETY OF NETWORK SERVICES THE NGN CAN DELIVER BECAUSE EACH NEW SERVICE MUST BE TIGHTLY INTEGRATED WITH THE MEDIA GATEWAY CONTROLLER IN ORDER TO PERFORM CALL CONTROL OPERATIONS. AS ILLUSTRATED IN FIGURE 2, THESE MEDIA GATEWAY CONTROLLERS WERE DEPLOYED CENTRALLY. FOR EXAMPLE, THESE

CONTROLLERS WOULD BE DEPLOYED IN THE SAME CENTRAL OFFICE THAT THE PSTN CENTRAL OFFICE SWITCH WAS DEPLOYED IN, OR AT YOUR INTERNET SERVICE PROVIDER. IN THE EARLY PART OF THE DECADE,

THAT WAS LIKELY TO BE SOMEWHERE IN VIRGINIA AT AOL'S HEADQUARTERS. SO, THE CONTROL WAS VERY MUCH LEFT OUTSIDE THE IN ANY EVENT, THE THEME OF

CONTROL OF THOSE ON THE PREMISES.

CENTRALIZED CONTROL OF TELEPHONE CALLS WAS CARRIED FORWARD

- 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 FROM THE PSTN TO THE NGN. NOW, A NUMBER OF DIFFERENT SIGNALING PROTOCOLS HAVE BEEN PROPOSED FOR THE NGN. A SIGNALING PROTOCOL ESSENTIALLY

DEFINES THE VARIOUS ELEMENTS OF THE NETWORK AND THE LANGUAGE THAT THOSE ELEMENTS SPEAK TO EACH OTHER TO SET UP AND CONTROL PHONE CALLS. THE PRIMARY PROTOCOLS THAT HAD BEEN PROPOSED BY

THE END OF THE `90S INCLUDED SOMETHING CALLED MGCP, WHICH IS MEDIA GATEWAY CONTROL PROTOCOL, H.323, AND SIP, SESSION INITIATION PROTOCOL, AMONG OTHERS. SIP, SESSION INITIATION

PROTOCOL, I AM GOING TO SPEND A LITTLE MORE TIME IN A MOMENT ON BECAUSE THAT IS THE PRIMARY PROTOCOL RELIED ON BY THE INVENTION IN THE `519 PATENT. WHILE EACH OF THESE PROPOSED PROTOCOLS HAD THEIR OWN PERCEIVED SET OF ADVANTAGES, THEY ALL SHARED A THEME THAT WAS COMMON TO THE PSTN. THE CRITICAL SYSTEMS NECESSARY TO SET UP

AND CONTROL TELEPHONE CALLS, THE NETWORK INTELLIGENCE, REMAINED CENTRALLY DEPLOYED IN THE NETWORK. BECAUSE THE NGN

WAS A NATURAL EVOLUTION FROM THE PSTN, IT WAS CONCEIVED AT THE OUTSET TO REALIZE SIMILAR ECONOMIES OF SCALE, LARGE SCALE UNIFORMITY OF SERVICE, AND A SIMILAR DEGREE OF CENTRALIZED MANAGEMENT CAPABILITY. THESE THREE PROTOCOLS INCLUDED ROUGHLY ANALOGOUS GATEWAY DEVICES INTENDED FOR DEPLOYMENT AT A CUSTOMER'S PREMISE AND CENTRALIZED CONTROL ELEMENTS. MGCP, FOR EXAMPLE, HAD A MEDIA

GATEWAY ON A CUSTOMER PREMISE AND IN THE CENTRAL OFFICE WAS

- 15 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 DEPLOYED A MEDIA GATEWAY CONTROLLER. IN H.323, THERE WAS A

GATEWAY ON THE PREMISE AND A GATEKEEPER IN THE CENTRAL OFFICE. IN SIP WE HAVE AN ENTITY CALLED THE SIP USER AGENT THAT REPRESENTS THE ENDPOINT AND WOULD BE DEPLOYED IN ONE OF THE GATEWAYS ON THE PREMISE. HAVE A SIP PROXY SERVER. NOW, SIP IS AN ACRONYM FOR SESSION INITIATION PROTOCOL. AND AS THE NAME SUGGESTS, IT'S A PROTOCOL MEANT TO INITIATE SESSIONS. A SESSION, FOR EXAMPLE, IS A TELEPHONE CALL. RFC SIP AND IN THE CENTRAL OFFICE WE WOULD

WAS INTRODUCED IN 1999 IN A DOCUMENT CALLED AN RFC. LITERALLY MEANS REQUEST FOR COMMENT.

IN RFC 2543 SESSION

INITIATION PROTOCOL IS DESCRIBED AS AN APPLICATION LAYER CONTROL OR SIGNALING PROTOCOL FOR CREATING, MODIFYING, AND TERMINATING SESSIONS WITH ONE OR MORE PARTICIPANTS. THESE

SESSIONS INCLUDE INTERNET MULTIMEDIA CONFERENCES, INTERNET TELEPHONE CALLS, AND MULTIMEDIA DISTRIBUTION. THE FIRST DRAFT SIP STANDARD WAS PUBLISHED AS RFC 2543 IN MARCH OF 1999. AN UPDATED VERSION OF THAT DRAFT SIP STANDARD

WAS PUBLISHED IN RFC 3261 IN JUNE OF 2002 SHORTLY AFTER THE `519 PATENT WAS FILED. NOW AS I MENTIONED, THE NAME LITERALLY STANDS FOR REQUEST FOR COMMENTS. THE PURPOSE OF AN RFC IS TO SOLICIT COMMENTARY

BY INDUSTRY EXPERTS SO THAT THE PROPOSED SIP PROTOCOL CAN BE IMPROVED AND ULTIMATELY BECOME A STANDARD. RFC 2543 STATES

THAT THIS DOCUMENT SPECIFIES AN INTERNET STANDARDS TRACK

- 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 PROTOCOL, SO IT'S NOT A STANDARD YET. TRACK AND IT'S IN DRAFT FORM STILL. IT'S ON A STANDARD IT'S A STANDARDS TRACK

PROTOCOL FOR THE INTERNET COMMUNITY AND REQUESTS DISCUSSION AND SUGGESTION FOR IMPROVEMENT. SO IT WAS ANTICIPATED, INDEED

EXPECTED, THAT IMPLEMENTORS OF THE DRAFT STANDARD WOULD DEVIATE IN CERTAIN WAYS FROM THE DRAFT TO ALLOW EXPERIMENTATION WITH POSSIBLE IMPROVEMENTS. NOW WE ARE GOING TO DISCUSS THESE DRAFT SIP STANDARDS IN A LITTLE MORE DETAIL TOMORROW, BUT I WANTED TO JUST SHOW YOU BRIEFLY GENERALLY WHAT A SIP STANDARD LOOKS LIKE. LITERALLY THE FACE OF THE DOCUMENT. THIS IS

ON THE FACE IT'S REFERRED THIS IS ADDRESSING

TO AS REQUEST FOR COMMENTS, NUMBER 2543.

SIP, SESSION INITIATION PROTOCOL PUBLISHED IN MARCH OF `99. THE RFC THAT REPLACED IT IS RFC 3261 PUBLISHED IN JUNE OF 2002. NOW I AM GOING TO COVER SOME OF THE FUNDAMENTAL BUILDING BLOCKS OF THE SIP PROTOCOL. AGENT. THE FIRST ONE IS A SIP USER

A SIP USER AGENT, AS ITS NAME IMPLIES, IS THE ELEMENT

OF A SIP NETWORK THAT IS INTENDED TO OPERATE ON BEHALF OF A USER, LIKE THE USER OF A TELEPHONE. IT'S THE ENDPOINT OF A

SIP NETWORK THAT REPRESENTS NON-SIP THINGS AND HUMANS AND PHONES THAT EXIST OUTSIDE OF THE SIP NETWORK. NETWORK ­- I AM SORRY. BUT THE SIP

THE SIP USER AGENT IS ESSENTIALLY THE

ENDPOINT OF THE SIP NETWORK. NOW A SIP USER AGENT, THESE ARE SOME OF THE THINGS THAT

- 17 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 COME OUT OF THE DRAFT SIP STANDARD. A SIP USER AGENT, OR UA

IN SOME CASES IT'S REFERRED TO, IS AN APPLICATION WHICH CONTAINS BOTH A USER AGENT CLIENT AND A USER AGENT SERVER. AND I AM GOING TO PROVIDE AN EXAMPLE IN A SECOND SO WE CAN UNDERSTAND A LITTLE BETTER WHAT THE DIFFERENCE BETWEEN THOSE TWO ELEMENTS IS. WHEN THE SIP USER AGENT IS THE CALLING USER AGENT, IT IMPLEMENTS THE USER AGENT CLIENT WHICH IS A CLIENT APPLICATION THAT INITIATES THE SIP REQUEST SUCH AS AN INVITATION TO ANOTHER USER AGENT TO INITIATE A TELEPHONE SESSION. SO WHEN

IT IS STARTING THE TELEPHONE CALL, IT ACTS AS A USER AGENT CLIENT. WHEN A SIP USER AGENT IS THE CALLED USER AGENT, IT

IMPLEMENTS A USER AGENT SERVER WHICH IS A SERVER APPLICATION THAT CONTAINS ­- I AM SORRY ­- THAT CONTACTS THE USER WHEN A SIP REQUEST IS RECEIVED. IN OTHER WORDS, IT CONTACTS THE

USER, FOR EXAMPLE, BY MAKING A TELEPHONE RING, AND THAT RETURNS A RESPONSE ON BEHALF OF THE USER. IN OTHER WORDS, AN

INDICATION THAT, YES, NOW MY PHONE IS RINGING, YOU CAN GO AHEAD AND MAKE THAT RINGING SOUND IN THE PHONE SO YOU KNOW THAT THE PHONE IS RINGING AS OPPOSED TO BUSY, FOR EXAMPLE. THE RESPONSE THAT'S PROVIDED BY THE USER AGENT CLIENT WILL ACCEPT, REJECT, OR REDIRECT THE REQUEST. AND HERE IS A BRIEF EXAMPLE, VERY MUCH SIMPLIFIED BUT IT SHOWS SOME OF THE BASIC SIGNALING THAT GOES ON TO SET UP A PHONE CALL. IN THIS EXAMPLE, WE HAVE SIP USER AGENT A ON THE

- 18 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 LEFT HAND AT THE TOP THERE. ANALOG TELEPHONE. SIP USER AGENT A REPRESENTS AL'S

AND BETWEEN AL'S ANALOG TELEPHONE AND USER

AGENT A, THERE IS NON-SIP DEVICE LEVEL SIGNALING, FOR EXAMPLE, THE THINGS WE MENTIONED EARLIER THAT A POTS PHONE CAN DO. IT

CAN SEND OUT TONES THAT REPRESENT NUMBERS WHEN YOU PRESS THE BUTTONS OR IT CAN INDICATE THAT THE HANDSET HAS BEEN PICKED UP. ALL OF THAT INFORMATION IS WHAT IS REFERRED TO AS DEVICE

LEVEL SIGNALING AND IT LETS THE USER AGENT KNOW WHAT IS GOING ON WITH THE POTS TELEPHONE. SO, FOR EXAMPLE, WHEN AL PICKS UP HIS HANDSET AND DIALS BOB'S PHONE NUMBER, AND NOW BOB'S PHONE, I'VE ACTUALLY REPRESENTED BOB'S PHONE AS A NATIVE SIP PHONE. IN THIS CASE

BOB'S PHONE ACTUALLY HAS A SIP USER AGENT BUILT INTO IT. SOMEBODY, YOU KNOW, PEOPLE HAVE MANUFACTURED PHONES TO INCLUDE THE SIP USER AGENT ENDPOINT RIGHT IN THE PHONE ITSELF. SO IN

THIS CASE, AL PICKS UP HIS HANDSET AND DIALS BOB'S ­- HE DIALS BOB'S PHONE NUMBER. SIP USER AGENT A ATTEMPTS TO INITIATE A AND

SESSION BY SENDING AN INVITE MESSAGE TO USER AGENT B. THAT'S INDICATED AS NUMBER 1.

AN INVITE IS SENT AND IT'S

LITERALLY A MESSAGE THAT WILL INCLUDE THE TERM INVITE IN IT THAT IS SENT TO USER AGENT B. IN THIS CASE, BECAUSE USER AGENT A IS THE CALLING USER AGENT, IT'S IMPLEMENTING THE USER AGENT CLIENT. AND BECAUSE

USER AGENT B IS THE CALLED USER AGENT, IT IS IMPLEMENTING THE USER AGENT SERVER. SO USER AGENT B PROCESSES THE INVITE

- 19 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 MESSAGE, CAUSES BOB'S PHONE TO RING, AND THEN SENDS A RINGING MESSAGE TO USER AGENT A TO INDICATE THAT BOB'S TELEPHONE IS RINGING. SO THAT RINGING MESSAGE GOES BACK TO USER AGENT A

AND USER AGENT A SENDS A SIGNAL TO AL'S ANALOG TELEPHONE AND SAYS, RING. IF BOB PICKS UP HIS HANDSET TO ANSWER, USER AGENT

B WOULD SEND AN OKAY MESSAGE INDICATING THAT I HAVE PICKED UP THE PHONE, I AM HERE, I AM AVAILABLE TO ENGAGE IN A TELEPHONE SESSION. WHEN USER AGENT A RECEIVES THAT OKAY MESSAGE, IT

WILL ACKNOWLEDGE RECEIPT OF THE OKAY MESSAGE AND SEND AN ACKNOWLEDGMENT OR AN ACK MESSAGE BACK TO USER AGENT B. THEREAFTER, A MEDIA SESSION, WHICH IS THE EXCHANGE OF THE DIGITIZED VOICE DATA, HAS BEEN SET UP AND IT WILL CONTINUE UNTIL ONE PARTY TERMINATES THE CALL BY HANGING UP. NOW, IT'S NOT CRITICALLY IMPORTANT TO UNDERSTAND THIS POINT BUT OFTENTIMES THAT MEDIA SESSION, THE PASSAGE OF DIGITAL DATA ACROSS THAT MEDIA SESSION MAY IN SOME CASES FOLLOW A DIFFERENT PATH THAN THE SETUP MESSAGES. IT'S NOT

IMPORTANT THAT THEY ARE PASSED THROUGH THE SAME ROUTERS AND SWITCHES. NOT. OFTENTIMES THAT MAY BE THE CASE. SOMETIMES IT'S

THE FLEXIBILITY OF THE PROTOCOL ALLOWS YOU TO SET UP A

PHONE CALL USING ONE DATA PATH BUT THEN COMMUNICATE THE DATA USING A DIFFERENT DATA PATH. IN THIS CASE, AS I MENTIONED BEFORE, THE SIP ENDPOINT IS USER AGENT A. THE ENDPOINT IS NOT AL'S ANALOG TELEPHONE AND AS

BECAUSE IT'S INCAPABLE OF COMMUNICATING SIP MESSAGES.

- 20 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 THE PATENT EXPLAINS, SIP USER AGENTS ARE CREATED TO OPERATE ON BEHALF OF TELEPHONE STATIONS, FOR EXAMPLE, NON-SIP TELEPHONES THAT ARE BY THEMSELVES INCAPABLE OF PERFORMING SIP NETWORK SIGNALING OPERATIONS. SO THE USER AGENT IS A SIP ENDPOINT.

THE `519 PATENT AND THE DRAFT SIP STANDARD REFER TO SIP USER AGENTS AS THE ENDPOINTS. RFC 3261 SAYS THAT THE SESSION

INITIATION SIP PROTOCOL WORKS IN CONCERT WITH THESE PROTOCOLS AND THAT THESE, THE DISCUSSION HERE WAS A REFERENCE TO OTHER PROTOCOLS SUCH AS PROTOCOLS NECESSARY TO DIGITIZE AND COMPRESS VOICE DATA, BUT IN ANY EVENT, IT SAYS IT WORKS IN CONCERT WITH THESE PROTOCOLS BY ENABLING INTERNET ENDPOINTS CALLED USER AGENTS TO DISCOVER ONE ANOTHER AND TO AGREE ON A CHARACTERIZATION OF A SESSION THEY WOULD LIKE TO SHARE. THE

CHARACTERIZATION OF A SESSION WOULD BE, FOR EXAMPLE, WE ARE GOING TO USE THIS TYPE OF VOICE COMPRESSION TECHNIQUE SO THAT EACH END OF THE CALL KNOWS ESSENTIALLY THE DIGITIZED VOICE LANGUAGE THAT EACH ENDPOINT WILL BE SPEAKING. NOW ANOTHER FUNDAMENTAL BUILDING BLOCK OF THE SIP PROTOCOL IS A SIP PROXY SERVER, AND I MENTIONED THAT EARLIER AS THE CENTRALIZED ELEMENT. IN THE `519 PATENT YOU WILL FIND AND THE

THE DEFINITION TAKEN FROM RFC 2543 EXACTLY.

DEFINITION OF A SIP PROXY SERVER AS FOUND IN RFC 2543 IS AN INTERMEDIARY PROGRAM THAT ACTS AS BOTH A SERVER AND A CLIENT FOR THE PURPOSE OF MAKING REQUESTS ON BEHALF OF OTHER CLIENTS. REQUESTS ARE SERVICED INTERNALLY OR BY PASSING THEM ON

- 21 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 POSSIBLY AFTER TRANSLATION TO OTHER SERVERS. A PROXY

INTERPRETS, AND, IF NECESSARY, REWRITES A REQUEST MESSAGE BEFORE FORWARDING IT. NOW HERE IS A BRIEF ILLUSTRATION. MUCH LIKE THE EARLIER

ILLUSTRATION, WE HAVE THE ENDPOINTS, USER AGENT A AND USER AGENT B, BUT IN THIS INSTANCE WE HAVE INSERTED A SIP PROXY SERVER AS AN INTERMEDIARY IN THE SIP COMMUNICATION. NOW THE

SIP PROXY SERVER ACTS ESSENTIALLY AS A USER AGENT SERVER WHEN IT RECEIVES THE INVITE MESSAGE. THE FIRST INVITE MESSAGE THERE LABELED NUMBER 1 WOULD BE ANALOGOUS TO THE INVITE MESSAGE WE SAW IN THE EARLIER ILLUSTRATION WHERE THERE WERE JUST TWO SIP ENDPOINTS. SO WHEN

THE USER AGENT CLIENT PORTION OF USER AGENT A SENDS A MESSAGE, IT NEEDS A SERVER TO RECEIVE THAT. SO A USER AGENT SERVER

PORTION OF THE SIP PROXY SERVER WILL RECEIVE THAT MESSAGE, BUT THEN THE SIP PROXY SERVER HAS TO TURN AROUND AND OUT THE OTHER SIDE ACT AS A SIP USER AGENT CLIENT. SO THE SIP PROXY

SERVER, IN ITS ROLE AS ACTING AS AN INTERMEDIARY, ACTS AS BOTH A SERVER AND A CLIENT BUT IT'S ACTING AS A SERVER ON ONE SIDE OF THE CALL AND IT'S ACTING AS A CLIENT ON THE OTHER SIDE OF THE CALL. AND IT ACTS AS A CLIENT FOR PURPOSES OF PASSING ON

THAT INVITE MESSAGE, WHICH IS THE MESSAGE NUMBER 3 THERE. SO, IN THIS FASHION, SIP MESSAGES ARE RELAYED THROUGH THE INTERMEDIARY TO THE FAR END ENDPOINT, AND, BY THE WAY, THERE CAN BE MULTIPLE HOPS IN BETWEEN. THERE CAN BE MULTIPLE PROXY

- 22 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 SERVERS AS YOU GET CLOSER TO THE OTHER ENDPOINT. BUT THE

POINT IS, THIS SIMPLE ILLUSTRATION SHOWS THAT THE SIP PROXY SERVER IS ACTING AS AN INTERMEDIARY. ULTIMATELY WE SEE THAT THERE IS AN ACKNOWLEDGMENT MESSAGE IN THIS PARTICULAR ILLUSTRATION. IT'S SHOWING THE

ACKNOWLEDGMENT MESSAGE SENT ALL THE WAY FROM ONE END TO THE OTHER. THAT WOULD BE IN A SITUATION WHERE THE ROUTING OF THE

MEDIA PACKETS ARE GOING TO FOLLOW A DIFFERENT PATH THAN THE SETUP MESSAGES. THE MEDIA STREAM. SO YOU MIGHT LEAVE THE PROXY SERVER OUT OF IN SOME INSTANCES YOU MIGHT INCLUDE

WHATEVER PIECE OF HARDWARE THE PROXY SERVER IS RUNNING ON, YOU MIGHT INCLUDE IT IN THE MEDIA STREAM. AND IN THAT CASE, YOU

WOULDN'T SEE THAT ACKNOWLEDGMENT MESSAGE SKIPPING A STEP AND YOU WOULD SEE THE MEDIA SESSION PASSING FIRST THROUGH THE PROXY SERVER AND THEN TO THE FAR END. NOW WITH THE TIME I HAVE LEFT HERE I AM GOING TO BRIEFLY GO THROUGH AN OVERVIEW OF THE TWO CLAIMS OF THE PATENT-IN-SUIT TO INTRODUCE YOU TO THE PROBLEMS THAT ARE SOLVED BY THE INVENTION. SO CLAIM 9 PROVIDES AN OVERVIEW. WE HAVE A

NETWORK DEVICE, AND IN THE PATENT THAT NETWORK DEVICE IS REFERRED TO AS AN EDGE SWITCH. BROADBAND NETWORK INTERFACE. THE EDGE SWITCH HAS A THE BROADBAND NETWORK INTERFACE

WILL BE ESSENTIALLY A MODEM THAT WILL CONNECT YOU TO THE BROADBAND ACCESS NETWORK. MODEM. IN SOME HOMES YOU MAY HAVE A DSL BUT THE

IN SOME HOMES YOU MAY HAVE A CABLE MODEM.

- 23 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 IDEA IS IT IS THE CONNECTION BETWEEN YOU AND THE BROADBAND ACCESS NETWORK THAT WILL ULTIMATELY GIVE YOU ACCESS TO THE INTERNET. THERE ARE A PLURALITY OF INTERFACES, INCLUDING A TELEPHONE LINE INTERFACE AND A COMPUTER DATA INTERFACE. THE

TELEPHONE LINE INTERFACE WOULD BE, FOR EXAMPLE, THE INTERFACE THAT YOU PLUG YOUR POTS PHONE INTO SO THAT THE NETWORK DEVICE CAN PROVIDE AN INSTANCE OF A SIP USER AGENT TO REPRESENT THAT POTS PHONE. THERE IS A PROCESSOR AND THEN THERE IS A MACHINE-

READABLE STORAGE MEDIUM THAT STORES PROCESSOR-EXECUTABLE INSTRUCTIONS, IN OTHER WORDS, SOFTWARE INSTRUCTIONS, TO PROVIDE SIP AGENTS THE INSTRUCTIONS CAUSING THE NETWORK DEVICE TO DO TWO THINGS. THE FIRST THING THAT IT DOES IS IT PROVIDES

A SIP USER AGENT TO REPRESENT A NON-SIP TELEPHONE THAT USES THE TELEPHONE LINE INTERFACE. SO, FOR EXAMPLE, THERE IS A

USER AGENT PROVIDED BY THIS NETWORK DEVICE FOR THE POTS PHONE THAT GETS PLUGGED INTO IT. IN ADDITION, THIS NETWORK DEVICE, UNLIKE THE GATEWAYS OF THE PRIOR ART, INCLUDES A SIP PROXY SERVER THAT MEDIATES ALL SIP COMMUNICATIONS OVER THE BROADBAND NETWORK INTERFACE INVOLVING THE NON-SIP TELEPHONE. RUNS RIGHT ON THE NETWORK DEVICE. THUS THE INVENTION OF CLAIM 9 PROVIDES BOTH A SIP USER AGENT AND A SIP PROXY SERVER IN THE SAME NETWORK DEVICE WHICH IS DEPLOYED ON THE SAME CUSTOMER PREMISE. THIS CAN BE SEEN IN AND THAT SIP PROXY SERVER

- 24 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 FIGURE 11 OF THE `519 PATENT WHERE EACH PREMISE HAS A NETWORK DEVICE WITH A SIP USER AGENT AND A SIP PROXY SERVER. THIS

ALLOWS THE NETWORK DEVICES TO SET UP AND CONTROL TELEPHONE CALLS WITHOUT THE NEED FOR CENTRAL NETWORK ELEMENTS. THE MESH

OF LIGHT GRAY DOTTED LINES REPRESENTS THE SIP SIGNALING PATHS THAT GO DIRECTLY FROM ONE PREMISE-BASED NETWORK DEVICE TO ANOTHER. THIS SYSTEM WAS CONSIDERED REVOLUTIONARY AT THE TIME

BECAUSE IT WAS CONTRARY TO THE STANDARD MODEL OF CENTRALIZED CONTROL CARRIED FORWARD FROM THE PSTN. WITH THIS SYSTEM,

CUSTOMERS AND BUSINESSES WOULD BE ABLE TO HAVE TELEPHONE SERVICE WITH ALL THE BENEFITS AND FEATURES OF THE PSTN WITHOUT CEDING CONTROL TO A TELEPHONE CARRIER AND WITHOUT HAVING TO PAY FOR ANYTHING OTHER THAN INTERNET ACCESS. NOW WITH THE LEVEL OF AUTONOMY PROVIDED BY THE INVENTION OF CLAIM 9, THE INVENTOR ALSO RECOGNIZED THAT THERE WAS STILL A NEED FOR SOME LEVEL OF CENTRALIZED MONITORING OF THE PHONE CALLS BEING MADE. FOR EXAMPLE, IF A BUSINESS WANTED TO KEEP

TRACK OF THE TIME, DATE, AND LENGTH OF PHONE CALLS FOR THE PURPOSE OF MONITORING ITS EMPLOYEES OR EVEN CHARGING CUSTOMERS, THERE WAS SOME LEVEL OF CENTRALIZED OVERSIGHT THAT MIGHT BE DESIRED. SO CLAIM 16 PROVIDES A METHOD OF COLLECTING CLAIM 16 IS A

CALL LOG DATA FROM THE VARIOUS NETWORK DEVICES. METHOD.

CLAIM 16 WILL INCORPORATE IN LARGE PART THE DEVICE BUT IN ANY EVENT, THIS IS A

THAT WAS INTRODUCED IN CLAIM 9.

METHOD CLAIM AND IT CALLS FOR LOCATING A SYSTEM MANAGEMENT

- 25 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 PLATFORM IN A SHARED PACKET NETWORK. THE SYSTEM MANAGEMENT

PLATFORM COLLECTING CALL LOG DATA FROM A PLURALITY OF NETWORK DEVICES. SO THE SYSTEM MANAGEMENT PLATFORM WOULD BE CENTRALLY AND THEN IN

LOCATED, FOR EXAMPLE, IN A CENTRAL OFFICE.

ADDITION, A NUMBER OF NETWORK DEVICES WILL BE DISTRIBUTED ABOUT THAT NETWORK. NETWORK DEVICE. AND FIGURE 4 SHOWS THREE INSTANCES OF A

THESE NETWORK DEVICES ARE CAPABLE OF ROUTING

CALLS IN A PEER-TO-PEER FASHION, WHICH IS ANOTHER WAY OF SAYING THAT THEY CAN ROUTE CALLS FROM ONE PREMISE TO ANOTHER WITHOUT THE NEED FOR CENTRALIZED CONTROL. AND FINALLY, CLAIM

16 ADDS THE REQUIREMENT OF A PROXY SERVER IN EACH OF THESE NETWORK DEVICES. THAT'S ALL I HAVE, YOUR HONOR. WHY DON'T WE TAKE A FIVE

THE COURT: THANK YOU.

MINUTE RECESS FOR THE DEFENDANT TO SET UP, AND THEN WE WILL HAVE THE TUTORIAL FROM CISCO. MINUTES. (RECESS AT 2:31 P.M., UNTIL 2:37 P.M., OPEN COURT) THE COURT: PLEASE BE SEATED. BEHALF OF CISCO. MS. SHARPER: YES, I AM. GOOD AFTERNOON. MY NAME IS READY TO GO FORWARD ON WE WILL BE IN RECESS FIVE

SAYURI SHARPER AND I REPRESENT THE DEFENDANTS, CISCO SYSTEMS AND CISCO-LINKSYS. HERE IS THE OUTLINE OF WHAT I AM GOING TO COVER TODAY. WE ARE GOING TO START WITH THE BACKGROUND TECHNOLOGY, HOW THE VOICE NETWORK HAS EVOLVED FROM PSTN TO VOICE OVER IP. AND WE

- 26 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 ARE GOING TO FOCUS FOR VOICE OVER IP TWO ALTERNATIVE ARCHITECTURES. THERE IS A TELECOM-CENTRIC ARCHITECTURE AND

THE INTERNET-CENTRIC ARCHITECTURE. AFTER THE BACKGROUND SECTION, WE WILL FOCUS ON SIP. IS SESSION INITIATION PROTOCOL. SIP

AND THERE ARE SIP BUILDING

BLOCKS THAT ARE DEFINED BY THE SPECIFICATION TO EXPLAIN HOW YOU WOULD BUILD A VOICE OVER IP NETWORK USING SIP. WE WILL

TAKE A LOOK AT THAT, TAKE A LOOK AT HOW SIP MESSAGES WORK, AND HOW THESE MESSAGES ARE USED BY THESE BUILDING BLOCKS TO INVOKE SIP OPERATIONS. AND THEN WE WILL TAKE A LOOK AT THE `519 PATENT, REVIEW A LITTLE BIT OF THE PRIOR ART THAT IS MENTIONED IN THE PATENT AND FOCUS ON HOW SIP IS USED IN THE PATENT ITSELF. SO THIS IS A PICTURE OF A TRADITIONAL PUBLIC SWITCH TELEPHONE NETWORK, VERY SIMILAR TO WHAT MR. MCANDREWS WENT THROUGH IN HIS TUTORIAL SESSION. THE TRADITIONAL PUBLIC I

SWITCH TELEPHONE NETWORK USED CIRCUIT-SWITCHED SYSTEMS.

WON'T GO OVER THAT AGAIN BECAUSE THAT WAS PRETTY WELL COVERED. THE ONE THING I WOULD LIKE TO POINT OUT IS THE CLASS 5 SWITCH OR THE SWITCH IN THE CENTRAL OFFICE. THE POINT HERE IS THAT

WITHOUT A SWITCH IN THE NETWORK, A TELEPHONE IN A HOUSE CAN'T TALK TO ANOTHER TELEPHONE. IT'S REQUIRED TO MAKE A CALL

CONNECTION BETWEEN THE TWO TELEPHONES FOR YOU TO HAVE A CONNECTION BETWEEN THEM. SO PRIMARILY THE NETWORK THAT IS OUT IN THE PUBLIC WAS

- 27 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 THIS PSTN, BUT PSTN IS REALLY NOT SUITED TO TRANSPORTING DATA. IN THE 1990S INTERNET BECAME VERY POPULAR. AND IN ORDER TO

TRANSPORT DATA, WHAT YOU NEED IS A PACKET-SWITCHED NETWORK. SO PEOPLE STARTED BUILDING PACKET-SWITCHED NETWORK INFRASTRUCTURE SO THAT THEY CAN ROUTE THIS DATA TRAFFIC. AGAIN, THE TERMS OF THE BASIC TECHNOLOGY OF PACKET-SWITCHED NETWORK THAT HAS BEEN COVERED BY MR. MCANDREWS, SO I WON'T GO OVER THAT HERE. SUFFICE IT TO SAY THAT A LOT OF INVESTMENT

WAS PUT IN PLACE TO BUILD THIS SECOND NETWORK TO TRANSPORT DATA IN ADDITION TO VOICE. SO SOME OF THESE SERVICE PROVIDERS WHO WERE OFFERING DATA SERVICE STARTED TO WONDER, HEY, CAN WE GET VOICE INTO OUR NETWORK ALSO FOR ADDITIONAL REVENUE? CAN WE SELL THIS NETWORK AND THAT'S THE

SERVICE FOR PEOPLE TO ROUTE THEIR VOICE DATA? START OF VOICE OVER IP.

SO IN ORDER TO ACCOMMODATE THAT, WHAT YOU NEEDED TO DO IS TO CHANGE THIS CONTINUOUS STREAM OF VOICE TRAFFIC AND PUT THAT INTO INDIVIDUAL DATA PACKET CHUNKS. SO MAKE VOICE LOOK MORE

LIKE DATA AND THEN YOU CAN ROUTE THAT IN THE INTERNET OR ANY PACKET-SWITCHED NETWORK JUST AS IF YOU ROUTE DATA. SO THAT

WAY A PHONE THAT IS CONNECTED TO AN INTERNET CAN TALK TO ANOTHER PHONE CONNECTED TO THE INTERNET. THAT SERVICE, HOWEVER, WASN'T TOO APPEALING BECAUSE A LOT OF PEOPLE WERE STILL SERVED OUT OF THE PUBLIC SWITCH TELEPHONE NETWORK. SO IF I CAN ONLY CALL MY NEIGHBOR WHO IS ON THE SAME

- 28 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 NETWORK AS ME, THERE IS ONLY SO MUCH VALUE. IN ORDER TO

ACCOMMODATE MY ABILITY TO CALL ANYBODY, WHAT I NEEDED WAS A GATEWAY THAT COULD CROSS BETWEEN THESE DIFFERENT TYPE OF NETWORKS. SO THAT'S THE REASON OF HAVING THIS PSTN GATEWAY WHAT IT DOES, IT

WHICH IS IN THE CENTER OF THE DIAGRAM.

CONVERTS PACKET DATA ­- PACKET VOICE USING VOICE OVER IP INTO THE FORMAT THAT'S COMPATIBLE WITH A STANDARD TELEPHONE NETWORK. SO HERE IS A TIMELINE OF HOW VOICE OVER IP EVOLVED. THE

FIRST COMMERCIALLY AVAILABLE PRODUCT THAT SUPPORTS VOICE OVER IP CALLED INTERNET PHONE WAS INTRODUCED TO THE MARKET IN FEBRUARY OF 1995. VOCALTEC. AND THIS IS A PRODUCT THAT WAS OFFERED BY

SO USING THE INTERNET PHONE YOU CAN CALL PEOPLE SO

THAT WAS ATTACHED TO INTERNET WHO ALSO HAVE THAT SOFTWARE. THIS WAS GREAT.

IT ENABLED PEOPLE THAT WAS OFFERING INTERNET

SERVICE TO PROVIDE VOICE CAPABILITY AS WELL. THE VOCALTEC PRODUCT, HOWEVER, WAS PROPRIETARY. IT USES

ITS OWN PROTOCOL WHICH MEANT THAT ALL THE EQUIPMENT HAD TO BE ACQUIRED FROM VOCALTEC. SO THAT LIMITED THE APPEAL OF THE

PRODUCT BECAUSE IF YOU WANT TO DESIGN A LARGE NETWORK, WHAT YOU WANT IS TO BE ABLE TO BUY EQUIPMENT FROM MULTIPLE VENDORS. SO STANDARDS SETTING ORGANIZATIONS STARTED WORKING ON VOICE OVER IP. THERE ARE TWO DIFFERENT STANDARD SETTING ONE IS ITU-T AND THE

ORGANIZATIONS THAT WAS WORKING ON THIS. OTHER IS IETF.

SO THE FIRST SET OF STANDARDS WAS PUBLISHED BY

- 29 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 ITU-T IN NOVEMBER OF 1996 AND THIS IS KNOWN AS THE H.323 RECOMMENDATIONS. THE IETF PUBLISHED A DIFFERENT PROTOCOL ITU-T PUBLISHED

CALLED SIP AS RFC 2543 IN MARCH OF 1999.

ANOTHER PROTOCOL KNOWN AS MEGACO, OR H.248 IN JUNE OF 2000. SO BY THE END OF 2000, THERE WERE TWO COMPETING VOICE OVER IP ARCHITECTURES ON THE MARKET. ONE WAS BASED ON THE SET

OF STANDARDS FROM ITU-T, SO THESE ARE THE H.323 AND THE H.248 OR MEGACO STANDARDS. CENTRIC SIP PROTOCOL. SO WHAT ARE THESE STANDARDS ORGANIZATIONS? JUST TO GO OVER THEM BRIEFLY, ITU-T IS AN ORGANIZATION WITHIN THE INTERNATIONAL TELECOMMUNICATIONS UNION WHICH IS PART OF THE UNITED NATIONS. AND ITS PURPOSE IS TO COORDINATE STANDARDS SO THE KEY HERE IS TO UNDERSTAND THAT AND THE OTHER ONE WAS THE INTERNET-

FOR TELECOMMUNICATIONS.

THE HERITAGE OF ITU-T IS FROM THE TELECOMMUNICATIONS INDUSTRY. SO IT'S A MEMBERSHIP DRIVEN ORGANIZATION. IN ORDER FOR YOU TO

CONTRIBUTE OR PUT ­- HAVE COMMENTS ON THEM, YOU HAVE TO BE A MEMBER. AND THE MEMBERSHIP CONSISTS OF 191 COUNTRIES AND SO AGAIN, THE FOCUS HERE IS TO MAKE SURE

ABOUT 700 COMPANIES.

THAT THE TELECOMMUNICATIONS NETWORK AROUND THE WORLD INTEROPERATES. ITU-T STANDARDS ARE KNOWN AS RECOMMENDATIONS. RECOMMENDATIONS ARE DEVELOPED IN STUDY GROUPS. THEY GO

THROUGH A REVIEW PROCESS WHERE ANY MEMBER CAN SUBMIT THEIR COMMENTS. ONCE THOSE ARE RESOLVED, THEN IT'S PUBLISHED AS A

- 30 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 RECOMMENDATION. STANDARDS, HOWEVER, EVOLVED. THERE IS NO SO HOW ITU-T

STANDARD THAT'S STABLE BECAUSE THINGS CHANGE.

ACCOMMODATE THAT IS THAT THEY REVISE THE STANDARD WITH NEW VERSIONS. SO, FOR EXAMPLE, H.323 WE SAW THE FIRST VERSION OF THE LATEST VERSION,

THE SPECIFICATION WAS PUBLISHED IN 1996.

WHICH IS VERSION 6, WAS PUBLISHED IN 2006, SO THAT YOU CAN MODIFY THE STANDARD AS YOU LEARN NEW THINGS AND AS A REQUIREMENT CHANGES. THIS IS IN CONTRAST TO IETF WHICH IS THE INTERNET ENGINEERING TASK FORCE. THE FOCUS OF THIS GROUP IS IN THE AND RATHER THAN

INTERNET AS OPPOSED TO TELECOMMUNICATIONS.

BEING A MEMBERSHIP DRIVEN ORGANIZATION, THIS IS AN OPEN ORGANIZATION WHICH MEANS THAT ANYBODY CAN ATTEND THEIR MEETINGS AND ANYBODY CAN MAKE COMMENTS. IN ANY WAY TO JUST THE MEMBERS. IT'S NOT RESTRICTED

EVEN THOUGH IT SOUNDS LIKE

THIS IS A MORE INFORMAL ORGANIZATION, IETF ACTUALLY FOLLOWS A VERY RIGOROUS STANDARDIZATION PROCESS. SO ALL STANDARDS OR ACTUALLY ALL SPECIFICATIONS THAT ARE BEING PROPOSED AS STANDARD HAS TO BE SUBMITTED TO IETF FIRST AS AN INTERNET-DRAFT. THE INTERNET-DRAFT THEN IS ­- BECOMES

PUBLICLY AVAILABLE AND WILL BE OPEN FOR REVIEW AND COMMENTS BY ANY INTERESTED PARTY. IN ORDER TO RESOLVE DIFFERENCES OF

OPINIONS ABOUT THE SPECIFICATION, THIS WORK IS HANDLED WITHIN A WORKING GROUP. THIS IS SIMILAR TO THE STUDY GROUP IN ITU-T.

SO THE WORKING GROUP GETS TOGETHER, THEY REVISE THE

- 31 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 SPECIFICATION, AND KEEP ON WORKING AT IT UNTIL THERE IS CONSENSUS ON THE SPECIFICATION ITSELF. ONCE THERE IS

CONSENSUS, THEN THE DRAFT SPECIFICATION IS SUBMITTED TO THE INTERNET ENGINEERING STEERING GROUP FOR APPROVAL. THERE IS A SPECIFIC CRITERIA THAT NEEDS TO BE MET BEFORE ANY DRAFT SPECIFICATION CAN BE APPROVED AS A STANDARD. THE

FIRST ONE IS THAT THE SPECIFICATION HAS TO BE WELL UNDERSTOOD. THAT MEANS THE SPECIFICATION HAS TO BE CLEAR TO SOMEONE WHO READS IT. REVIEW. APPROVED. IT HAS TO HAVE RECEIVED SIGNIFICANT COMMUNITY SO WITHOUT THE REVIEW PROCESS IT WILL NOT BE AND IT HAS TO ENJOY ENOUGH COMMUNITY INTEREST TO BE THESE ARE PROTOCOLS THAT WILL BE USED ON

CONSIDERED VALUABLE. THE INTERNET. SUBMIT. INTERNET.

AND THEY JUST DON'T APPROVE ANYTHING YOU

IT HAS TO BE OF VALUE TO THE OPERATION OF THE SO ONCE IT'S SUBMITTED AND APPROVED, THEN THE

SPECIFICATION IS PUBLISHED WITH AN OFFICIAL RFC NUMBER. UNLIKE THE ITU-T, THE STANDARDS DOCUMENT WITHIN IETF DOES NOT HAVE REVISION NUMBERS. THAT DOCUMENT NEVER CHANGES. SO IF YOU HAVE AN RFC PUBLISHED, HOWEVER, AS WE SAID, STANDARDS

EVOLVE SO THEY HAVE TO HAVE A MECHANISM TO ACCOMMODATE THAT. SO WITHIN IETF WHEN THERE IS A REVISION TO A STANDARD, IT'S PUBLISHED WITH A NEW RFC NUMBER. SO WHAT DOES RFC MEAN? I

THINK WE'VE HEARD COMMENTS THAT REQUEST FOR COMMENTS ARE NOT FINAL DOCUMENTS BECAUSE IT STANDS FOR REQUEST FOR COMMENTS, SO OBVIOUSLY IT'S NOT FINAL. BUT THAT REALLY IS NOT HOW THE

- 32 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 TERMINOLOGY IS USED WITHIN IETF. WITHIN IETF THE NOMENCLATURE

FOR REQUEST FOR COMMENTS IS REALLY AN OFFICIAL IETF PUBLICATION. SO ANYTHING THAT IETF PUBLISHES HAS AN RFC NUMBER. AND

THERE ARE FOUR CATEGORIES OF RFCS, SO NOT ALL RFC ARE STANDARD DOCUMENTS. THEY ARE ­- THE CATEGORIES ARE: INFORMATIONAL, IF YOU GET AN

EXPERIMENTAL, STANDARDS TRACK, AND HISTORIC.

RFC ON EACH ­- ON THE FIRST PAGE OF EACH DOCUMENT THE CATEGORY OF THE DOCUMENT IS CLEARLY MARKED. IT WILL SAY INFORMATIONAL, AND ONLY STANDARD

EXPERIMENTAL, STANDARDS TRACK, OR HISTORIC.

TRACK DOCUMENTS ARE CONSIDERED IETF STANDARDS. AND THERE ARE THREE LEVELS OF STANDARDS. THESE ARE NOT

ON THE FACE OF THE RFC BUT THERE IS A WEBSITE WHERE YOU CAN GO TO LOOK UP THE STATUS. THEY ARE: PROPOSED STANDARD, DRAFT SO HOW DO YOU ELEVATE

STANDARD, AND INTERNET STANDARD.

STANDARDS FROM PROPOSED STANDARD, TO THE NEXT LEVEL, TO FINALLY THE INTERNET STANDARD? WELL, THE PROCESS IS PRETTY WHAT WE KNOW IS

COMPLICATED AND NOT OBVIOUS A LOT OF TIMES.

THAT A MAJORITY OF THE COMMONLY USED INTERNET STANDARDS, ABOUT 90 PERCENT OF THE STANDARDS AVAILABLE TODAY ARE A PROPOSED STANDARD. LEVEL. SIP, WHICH IS THE PROTOCOL WE ARE TALKING ABOUT, HAS BEEN BROADLY DEPLOYED IN THE LAST TEN YEARS AND THAT IS STILL A PROPOSED STANDARD. SOMETHING THAT WE PROBABLY USE EVERY DAY VARIOUS REASONS WHY THEY DON'T MOVE TO THE NEXT

- 33 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 WHICH IS HTTP, THIS IS THE PROTOCOL THAT IS USED BETWEEN WEB BROWSERS AND WEBSITE. WHEN YOU ACCESS A WEBSITE, THAT IS A DRAFT STANDARD. EVEN PROTOCOL THAT ARE INTERNET STANDARDS CAN BE MODIFIED. SO, FOR EXAMPLE, THIS IS ANOTHER PROTOCOL THAT WE THE TWO THEY WERE

PROBABLY USE ALL THE TIME WHICH IS TO DO EMAIL. STANDARDS REQUIRED FOR THAT IS MAIL AND SMTP. ORIGINALLY RFC 821 AND 822. INTERNET STANDARD STATUS.

AND THESE DOCUMENTS REACHED BUT NETWORK CHANGE AND THINGS

EVOLVE SO THEY BECAME OBSOLETED BY RFC 5321 AND 5322, WHICH WHEN IT WAS PUBLISHED ORIGINALLY WAS PUBLISHED AS PROPOSED STANDARD AND CURRENTLY ARE DRAFT STANDARD. SO, DOES IT MEAN THAT PROPOSED STANDARDS ARE NOT STANDARDS? NO. IN FACT, IF YOU PICK UP AN RFC DOCUMENT AS A

CATEGORY. THE ONLY THING YOU SEE IS THAT IT'S A STANDARDS TRACK DOCUMENT. IT DOESN'T MEAN THAT THEY ­- THE STANDARD

DOCUMENT IS NOT A SOLID JUST BECAUSE THEY HAVE DIFFERENT LEVELS OF MATURITY. GOING BACK TO THESE TWO ORGANIZATIONS AS WE TALKED ABOUT, ITU-T IS FOCUSED IN THE TELECOMMUNICATIONS INDUSTRY AND THE ARCHITECTURE HERE IS MUCH MORE TELECOM-CENTRIC. HERE WE HAVE

THE MEDIA GATEWAY CONTROLLER, THUS THE BLUE BOX ON THE TOP. IT'S ALSO COMMONLY CALLED IN THE INDUSTRY AS A SOFTSWITCH. WHAT YOU SEE IN THIS ARCHITECTURE IS THAT THIS BOX PLAYS THE SAME ROLE AS A CLASSIFIED SWITCH.

- 34 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 THE COURT: AS A WHAT? MS. SHARPER: CLASSIFIED SWITCH. THAT'S THE SWITCH SO

IN THE CENTRAL OFFICE IN THE TRADITIONAL PSTN NETWORK.

WHAT THAT MEANS IS THAT YOU CAN HAVE THE TELEPHONES CONNECT TO EACH OTHER WITHOUT THE MEDIA GATEWAY CONTROLLER. SO IT

ACCOMPLISHED THAT BY USING THIS MEGACO PROTOCOL, WHICH IS KNOWN AS A MASTER-SLAVE PROTOCOL. WHAT DOES THAT MEAN? THAT

MEANS THAT THE RESIDENTIAL GATEWAY WHICH ACTUALLY HAS A TELEPHONE ATTACHED TO IT DOESN'T DO ANYTHING UNLESS IT'S TOLD TO DO SO BY THE SOFTSWITCH USING THE MEGACO. COMMAND AND IT SENDS A RESPONSE. SO IT GETS A

SO THAT IS THE TYPE OF

ARCHITECTURE THAT IS PROMOTED BY MEGACO USING THE ITU-T STANDARD. HERE WHAT YOU SEE EVEN THOUGH IT'S USING IP FOR TRANSPORT, THE NETWORK ARCHITECTURE IS PRETTY MUCH THE SAME AS PSTN NETWORK, WHERE THE SMARTS ARE IN THE NETWORK, THE INTELLIGENCE AND CONTROL, ARE ALL IN THE GATEWAY CONTROLLER WITHIN THE NETWORK ITSELF. AND THE DEVICES ARE PRETTY DUMB. THEY JUST DO WHAT THEY ARE TOLD TO DO. THIS IS VERY DIFFERENT FROM INTERNET-CENTRIC ARCHITECTURE THAT WAS BEING PROMOTED BY SIP. HERE YOU SEE TWO CIRCLES

REPRESENTING CUSTOMER PREMISES, OR IN THIS CASE ON THE RIGHT IS A SMALL OFFICE. AND WHAT YOU SEE IS THAT THESE NETWORKS YOU DON'T SEE SOMETHING

CAN TALK TO EACH OTHER USING SIP.

THAT IS AN EQUIVALENT OF A CLASSIFIED SWITCH IN THE NETWORK.

- 35 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 THIS IS POSSIBLE BECAUSE THE DEVICES TALK TO EACH OTHER USING SIP WHICH IS A PEER-TO-PEER PROTOCOL AS OPPOSED TO A MASTERSLAVE PROTOCOL. SO, YOU DON'T NEED A CENTRALIZED SERVER ANYWHERE WITHIN THE NETWORK FOR THESE DEVICES TO TALK TO EACH OTHER. WHAT YOU

SEE HERE IF YOU CAN THINK OF IT'S MORE LIKE HOW EMAIL WORKS. SO THE ARCHITECTURE HERE IS INTERNET-CENTRIC VERSUS HOW A TELEPHONE SYSTEM WILL WORK. ALTHOUGH THERE COULD BE OPTIONAL

NETWORK-BASED SERVICES THAT CAN BE MADE AVAILABLE TO THE SIP DEVICES, THEY ARE NOT NECESSARY. SO WHAT PEOPLE TALK ABOUT IN

THE INTERNET ENVIRONMENT IS THAT THE SMARTS ARE IN THE ENDUSER DEVICES AND THE NETWORK JUST SERVE AS A TRANSPORT. IT'S

JUST A WIRE, EXCEPT A LITTLE BIT MORE COMPLICATED THAN JUST A POINT-TO-POINT WIRE THAT CONNECTS THE DEVICES TO EACH OTHER. HERE IS A TIMELINE FOR SIP DEVELOPMENT. I WON'T GO SUFFICE IT TO

THROUGH A LOT OF DETAILS THAT IS IN THIS SLIDE.

SAY THAT THE ORIGINAL SPECIFICATION THAT WERE INTERNET DRAFTS WERE PROPOSED IN FEBRUARY OF 1996. AND OFFICIAL INTERNET

DRAFTS WAS SUBMITTED TO IETF LATER THAT YEAR, AND IT WENT THROUGH OVER TWO YEARS OF DEVELOPMENT WITHIN THE WORKING GROUP BEFORE EVERYBODY WAS SATISFIED WITH THE PROTOCOL, AND IT WAS FINALLY SUBMITTED TO THE ENGINEERING STEERING GROUP FOR APPROVAL. AND THE OFFICIAL APPROVAL FOR THE PROTOCOL WAS

RECEIVED IN 1999. AFTER THAT APPROVAL, THE INDUSTRY WORKED HARD AT

- 36 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 DEVELOPING PRODUCTS THAT WERE INTEROPERABLE. MULTIPLE INTEROPERABILITY EVENTS. THERE WERE

AND BY 2001, THESE EVENTS

WERE ATTENDED BY MORE THAN 50 COMPANIES TRYING TO MAKE THEIR EQUIPMENT WORK TOGETHER. AND IN 2001, THE FIRST VOICE OVER IP SO BY THEN THE SIP-

SERVICE USING SIP WAS LAUNCHED BY VONAGE. BASED NETWORK ARCHITECTURE WAS IN PLACE.

THESE ARE SOME OF THE COMMENTS THAT PEOPLE MADE ABOUT SIP IN THAT TIME FRAME. HENRY SINNREICH, WHO WAS ASSOCIATED WITH

WORLDCOM, MADE THE COMMENT THAT SIP IS THE PURE INTERNET PLAY AS OPPOSED TO THE TRADITIONAL TELECOM NETWORK. AN INTERNET APPLICATION LOOKS LIKE. SAID: THIS IS WHAT

MATT JOHNSON FROM LEVEL 3

BY PUSHING INTELLIGENCE OUT TO THE NETWORK ENDPOINTS,

SIP CAN SIMPLIFY THE SYSTEMS REQUIRED IN THE NETWORK, AGAIN ACKNOWLEDGING THE DIFFERENCE OF SIP FROM OTHER PROPOSED PROTOCOLS. AND VINT CERF, WHO IS OFTEN CALLED THE FATHER OF

THE INTERNET, SAID: SIP IS PROBABLY THE THIRD GREAT PROTOCOL OF THE INTERNET, AFTER TCP/IP AND HTTP. SO, OKAY, WHAT IS SIP? AND THIS WAS IN 2001.

AS SPECIFIED BY RFC 2543, IT'S A

SIGNALING PROTOCOL FOR CREATING, MODIFYING, AND TERMINATING VOICE OVER IP CALLS. OVER IP NETWORK? SO HOW DO YOU USE SIP TO BUILD A VOICE

IN ORDER TO EXPLAIN HOW YOU USE SIP TO BUILD

A VOICE OVER IP NETWORK, RFC 2543 DEFINES A SET OF BUILDING BLOCKS AND THE BEHAVIOR AND THE PROTOCOL OF THESE BUILDING BLOCKS IN A VOICE OVER IP NETWORK. THERE ARE FIVE DIFFERENT THEY

TYPES OF BUILDING BLOCKS THAT ARE SPECIFIED IN RFC 2543.

- 37 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 ARE: USER AGENT, PROXY SERVER, REDIRECT SERVER, LOCATION SERVER, AND REGISTRAR. THE `519 PATENT ONLY TALKS ABOUT USER AGENT AND PROXY SERVER SO THAT'S WHAT WE WILL FOCUS IN THE TUTORIAL TODAY. EACH OF THESE BUILDING BLOCKS COMMUNICATE WITH EACH OTHER USING SIP MESSAGES. THERE ARE TWO TYPES OF MESSAGES: REQUEST AND WE WILL TAKE A LOOK AT RFC 2543 IS

MESSAGES AND RESPONSE MESSAGES.

THIS A LITTLE BIT LATER IN THE TUTORIAL AS WELL. CONCERNED WITH INTEROPERABILITY. YOU USE THESE BUILDING BLOCKS.

IT'S NOT CONCERNED ABOUT HOW AT THE END OF THE DAY, THESE SO HOW YOU USE

BUILDING BLOCKS ARE JUST SOFTWARE MODULES.

THEM TO PUT A PRODUCT TOGETHER IS NOT OF CONCERN IN THE SPECIFICATION. IT'S MORE THE PROTOCOLS AND HOW THESE BUILDING THAT'S WHAT IS SPECIFIED IN

BLOCKS INTERACT WITH EACH OTHER. THE RFC ITSELF.

OKAY, HERE IS A PICTORIAL REPRESENTATION OF A SIP USER AGENT. THE DEFINITION FOR USER AGENT SAYS: IT'S A PROGRAM

THAT CONTAINS BOTH A USER AGENT CLIENT AND A USER AGENT SERVER. OKAY, SO WHAT DOES THAT MEAN? IT THEN DEFINES USER

AGENT CLIENT AS A PROGRAM THAT INITIATES THE SIP REQUEST, AND A USER AGENT SERVER AS A PROGRAM THAT CONTACTS A USER WHEN THE SIP REQUEST IS RECEIVED AND RETURNS THE RESPONSE ON BEHALF OF THE USER. REQUEST. THE DEFINITION ITSELF IS REALLY NOT SUFFICIENT FOR ONE OF THE RESPONSE ACCEPTS, REJECTS, OR REDIRECTS THE

- 38 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 SKILL IN THE ART TO FIGURE OUT HOW YOU BUILD A SIP USER AGENT. IN ORDER FOR YOU TO KNOW HOW TO DO THAT, YOU'D NEED TO KNOW WHAT THESE SIP REQUEST AND RESPONSE MESSAGES ARE AND HOW THE SIP USER AGENT ACTUALLY USES THEM. DIFFERENT SECTIONS OF THE RFC. SO THESE ARE COVERED IN

THE PROTOCOLS, THE MESSAGE

FORMAT ARE SPECIFIED IN SECTIONS 2 THROUGH 7 OF THE DOCUMENT. AND THE RULES ASSOCIATED WITH HOW A SIP USER AGENT SENDS AND RECEIVES THESE MESSAGES ARE COVERED IN SECTION 11. TAKE A CLOSER LOOK AT HOW THIS IS DONE IN A MINUTE. HERE IS A PICTORIAL REPRESENTATION OF A SIP PROXY SERVER. ACCORDING TO THE DEFINITION, IT'S AN INTERMEDIARY PROGRAM THAT ACTS AS BOTH A SERVER AND A CLIENT FOR THE PURPOSE OF MAKING REQUESTS ON BEHALF OF OTHER CLIENTS. SO WHAT DOES THIS MEAN? WE WILL

IN THE TERMINOLOGY OF RFC 2543, A SERVER IS NOT A COMPUTER WHICH IS WHAT WE WOULD NORMALLY THINK OF. A SERVER IS A

SOFTWARE PROGRAM THAT ACCEPTS SIP REQUESTS AND SENDS A RESPONSE TO IT. SO THAT'S A SERVER. AND THAT'S SHOWN IN THE

PICTURE ON THE LEFT.

SO, SIP PROXY SERVER ACCEPTS A RESPONSE

AND SENDS A REQUEST BACK. THE OTHER HALF OF A SIP PROXY SERVER IS A CLIENT. AND

THE DEFINITION OF A CLIENT WITHIN THE SPEC IS IT'S ANYTHING THAT SENDS SIP REQUESTS. THAT'S A CLIENT. SO WE HAVE TO READ REQUESTS ARE

A LITTLE BIT MORE TO SEE WHAT THIS THING DOES.

SERVICED INTERNALLY OR BY PASSING THEM ON, POSSIBLY AFTER TRANSLATION, TO OTHER SERVERS. SO A SIP PROXY SERVER NORMALLY

- 39 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 IS ASKED TO FIND A LOCATION OF A SIP USER AGENT. IN ORDER TO

DO THAT, A SIP PROXY SERVER MAY CONSULT A LOCATION SERVER WHICH HAS THE CALLED PARTY'S LOCATION INFORMATION. IN THAT

CASE, IT CAN RESOLVE THE ADDRESS AND SENDS A SIP REQUEST ONTO THIS USER AGENT. SOMETIMES IT CONSULTS ITS LOCAL LOCATION IN THAT CASE, THE

SERVER AND IT DOESN'T HAVE THE ADDRESS. REQUEST IS FORWARDED TO ANOTHER SERVER.

AGAIN, HOW THIS IS DONE IS NOT IN THE DEFINITION.

THE

RULES ASSOCIATED WITH HOW YOU IMPLEMENT THE PROXY SERVER IS FOUND IN SECTION 12.3 OF THE DOCUMENT. BUILDING A SIP USER

AGENT AND SIP PROXY SERVER REQUIRES YOU TO USE SIP REQUEST MESSAGES. AND THIS IS SOMETHING THAT IS IN SECTION 4 OF THE LET'S REVIEW WHAT ARE THE SIP REQUEST MESSAGES THEY ARE: INVITE, WHICH IS USED TO INVITE

SPECIFICATION.

THAT ARE AVAILABLE.

A USER TO A COMMUNICATION SESSION; ACK, WHICH ACKNOWLEDGES THE FINAL RESPONSE TO AN INVITE REQUEST; OPTIONS, WHICH IS USED TO QUERY A SERVER ABOUT ITS ABILITIES; BYE, TO TERMINATE A CALL SESSION; CANCEL, TO CANCEL A PENDING REQUEST; AND REGISTER, TO REGISTER AN ADDRESS WITH A SIP REGISTRAR. THE DETAIL OF THE SYNTAX OF THESE MESSAGES ARE IN SECTION 4 TO 6, BUT LET'S AT LEAST TAKE A LOOK AT ONE EXAMPLE OF AN INVITE REQUEST MESSAGE. SO WHAT YOU SEE IN THE FIRST LINE IS

THAT THE MESSAGE STARTS WITH A KEY WORD, IN THIS CASE THE WORD INVITE. THE SECOND FIELD IN THIS FIRST LINE IS THE ADDRESS OF THIS LOOKS KIND OF SIMILAR TO AN EMAIL

THE CALLED PARTY.

- 40 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 ADDRESS BECAUSE, AS I SAY, A SIP IS PRETTY CLOSE TO HOW EMAIL WORKS. SO HERE YOU HAVE THE ADDRESS AS SIP:[e-mail].

SO THAT WOULD BE THE FIELD THAT TELLS A SERVER WHO TO INVITE. AND THAT'S FOLLOWED BY THE VERSION NUMBER OF SIP. IT SAYS IT'S VERSION 2.0. HERE

I WON'T GO INTO EVERY LINE OF THIS

REQUEST MESSAGE, BUT I WOULD LIKE TO NOTE THAT EVERY REQUEST MESSAGE HAS TO HAVE THE FROM, TO, AND CALL-ID HEADERS. ARE IMPORTANT BECAUSE THEY ARE NECESSARY TO IDENTIFY A SPECIFIC CALL SESSION. SO THIS IS A PACKET NETWORK AND YOU THESE

NEED TO KNOW WHICH MESSAGE IS ASSOCIATED WITH WHICH CALL, SO THESE FIELDS ARE USED FOR THAT PURPOSE. THERE ARE ALSO SIX DIFFERENT TYPES OF SIP RESPONSE MESSAGES AND THAT'S SHOWN HERE. SIP RESPONSE MESSAGES HAS A RATHER THAN ONE

DIFFERENT FORMAT THAN WHAT WE PREVIOUSLY SAW.

KEY WORD, IT ACTUALLY STARTS WITH A THREE-DIGIT STATUS CODE. AND THAT STATUS CODE IS THEN FOLLOWED BY A REASON PHRASE, AN ENGLISH EXPLANATION OF WHAT THE MESSAGE MEANS. SO THE FIRST

TYPE OF STATUS CODE STARTS WITH THE DIGIT 1 THAT'S SHOWN ON THE TABLE IN THE RIGHT. RINGING. SO IT'S, FOR EXAMPLE, 180 WHICH MEANS

THIS TYPE OF CODE IS USED TO PROVIDE INFORMATION.

SO THE REQUEST HAS BEEN RECEIVED AND IT'S PROCESSING THE REQUEST, AND IN THE MEANTIME, IT TELLS THE OTHER PARTY SOME INFORMATION ABOUT THE CALL. THE SECOND TYPE ARE KNOWN AS SUCCESS-TYPE MESSAGES WHICH MEANS THAT THE ACTION WAS SUCCESSFULLY RECEIVED AND ACCEPTED.

- 41 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 THE THIRD TYPE OF MESSAGES ARE REDIRECTION MESSAGES WHICH SAYS THAT A FURTHER ACTION NEEDS TO BE TAKEN IN ORDER TO COMPLETE THE REQUEST. MESSAGES. THEN THERE ARE DIFFERENT TYPES OF ERROR

IF THE ERROR WAS CAUSED BY A CLIENT, IT STARTS WITH

STATUS CODE OF 4; SERVER ERROR 5; GLOBAL ERROR 6. HERE IS WHAT A RESPONSE MESSAGE LOOKS LIKE. SO THE FIRST

LINE STARTS WITH A SIP PROTOCOL VERSION RATHER THAN INVITE OR KEY WORD, FOLLOWED BY THE STATUS CODE AND THE REASON PHRASE. IN THIS CASE IT SAYS: 180 RINGING. WHAT YOU SEE IS THAT THE

FORMAT FOLLOWING THE FIRST LINE IS VERY SIMILAR TO REQUEST MESSAGES. AND THE IMPORTANT THING TO NOTE HERE IS THAT AGAIN

THE FIELD FROM, TO, CALL-ID ARE MANDATORY BECAUSE THEY ARE NECESSARY TO IDENTIFY A SPECIFIC CALL SESSION. SO HOW ARE THESE MESSAGES USED BY THESE BUILDING BLOCKS? WE SAW THIS DIAGRAM OR SOMETHING SIMILAR A LITTLE WHILE AGO. BUT HERE WHAT WE ARE SHOWING IS COMMUNICATION HAPPENING DIRECTLY BETWEEN ONE USER AGENT TO ANOTHER USER AGENT. USER

AGENT ON THE LEFT IS INITIATING THE CALL SESSION BY SENDING AN INVITE. THE USER AGENT ON THE RIGHT SENDS AN INFORMATIONAL WHEN THE USER ACTUALLY ANSWERS

RESPONSE SAYING 180 RINGING.

THE PHONE, IT SENDS 200 OK SAYING THAT NOW WE CAN START THE COMMUNICATION. THE USER AGENT RESPONDS WITH AN ACK. THAT

MEANS THAT IT RECEIVED A RESPONSE AND COMMUNICATION CAN HAPPEN BETWEEN THE TWO. AND WHEN SOMEBODY HANGS UP THE PHONE, THE

USER AGENT SENDS THE BYE MESSAGE.

- 42 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 THIS IS WHAT HAPPENS WHEN THE ORIGINATING USER AGENT KNOWS THE LOCATION OF THE RECEIVING USER AGENT ON THE RIGHT. SOMETIMES, THOUGH, A USER AGENT MAY WANT TO CONTACT SOMEONE EVEN THOUGH IT DOESN'T KNOW THE LOCATION OF THAT PERSON. THAT'S THE CASE WHEN A PROXY SERVER GETS INVOLVED. SO

HERE, THE

SIP USER AGENT IS SENDING AN INVITE MESSAGE BUT DOESN'T REALLY KNOW WHERE THE USER AGENT THAT IT WANTS TO REACH IS LOCATED. SO RATHER THAN SENDING IT DIRECTLY, IT SENDS TO A SIP PROXY SERVER. NORMALLY, A SIP USER AGENT GETS CONFIGURED WITH A DEFAULT PROXY SERVER SO IT WILL SEND THAT MESSAGE OVER THERE. THE SIP

PROXY SERVER SENDS A MESSAGE BACK SAYING, OKAY, IT'S GOING TO TRY TO FIND THIS PERSON. AND IF IT FINDS IT, THEN IT FORWARDS AND FROM THERE

THE REQUEST ON TO THE DESTINATION USER AGENT.

ON, IT SERVES AS INTERMEDIARY OR A RELAY POINT BETWEEN THESE MESSAGES. SO THE MESSAGES GOES BACK AND FORTH THROUGH THIS SO SOMETIMES THIS PROXY SERVER DOESN'T HAVE THE IT CAN SEND IT TO ANOTHER PROXY

PROXY SERVER.

ADDRESS, SO WHAT DOES IT DO? SERVER.

THIS IS AN EXAMPLE WHERE TWO PROXY SERVERS ARE

INVOLVED IN THE PASS FROM SIP USER AGENT ON THE LEFT TO THE RIGHT. SO LET'S TAKE A CLOSER LOOK AT WHAT'S ACTUALLY HAPPENING. THIS IS THE INVITE MESSAGE FROM USER AGENT THAT IS BEING SENT ORIGINALLY. THIS IS THE SAME MESSAGE THAT WE SAW BEFORE. SO THIS MESSAGE IS SENT

IT'S TRYING TO REACH [e-mail].

- 43 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 TO THE SIP PROXY SERVER. HERE IS THE INVITE MESSAGE FROM THE

SIP PROXY SERVER GENERATED BY THE FIRST SIP PROXY SERVER. WHAT I'VE DONE IS HIGHLIGHTED IN RED THE TWO ADDITIONAL LINES THAT IS INSERTED. YOU SEE IT'S PRETTY MUCH A COPY OF WHAT IT

RECEIVED, EXCEPT WHAT IT DOES IS THAT IT ADDS SOME ROUTING INFORMATION, WHICH IS THE ADDRESS INFORMATION OF THE PROXY SERVER ITSELF SO THE MESSAGE CAN FIND ITS WAY BACK TO IT. THE CALL SESSION IDENTIFICATION INFORMATION IN THIS CASE REMAINS THE SAME BECAUSE IT'S THE SAME CALL. HERE IS WHAT THE

SIP PROXY SERVER, THE SECOND ONE, WHAT THE INVITE MESSAGES LOOKS LIKE. AQUA BLUE. THE TWO ADDITIONAL LINES THAT ARE INSERTED IS IN WHAT YOU SEE AGAIN IS THAT IT'S REALLY JUST ADDING AND THE CALL SESSION IDENTIFICATION

THE ROUTING INFORMATION. REMAINS THE SAME.

AGAIN, THIS ROUTING INFORMATION IS

NECESSARY BECAUSE THE MESSAGE AS IT FINDS ITS WAY BACK HAS TO GO THROUGH BOTH OF THESE PROXY SERVERS TO REACH THE ORIGINATING SIP USER AGENT. OKAY, SO THAT'S KIND OF A TUTORIAL ON SIP, AND LET'S TAKE A LOOK AT THE `519 PATENT. THIS IS JUST A NOTE THAT THESE

PATENTS WERE FILED AFTER 2000 WHEN ALL THE STANDARDS WERE ALREADY IN PLACE. HERE IS THE FIRST FIGURE IN THE PATENT LABELED PRIOR ART, AND THIS IS DEPICTING THE TRADITIONAL PSTN NETWORK. AND MR.

MCANDREWS COVERED THIS PRETTY WELL, SO I WILL SKIP THIS. FIGURE 2 IS WHAT IS CALLED WITHIN THE PATENT THE NEXT

- 44 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 GENERATION NETWORK. IT'S BASED ON THE MEDIA GATEWAY

CONTROLLER USING MEGACO PROTOCOL TO CONTROL THE RESIDENTIAL GATEWAYS TO SET UP CALL CONNECTION. THIS, HOPEFULLY, LOOKS

FAMILIAR TO YOU BECAUSE IT'S REALLY THE SAME NETWORK ARCHITECTURE AS WHAT WE REVIEWED WHEN WE TALKED ABOUT THE ITU-T PROTOCOL-BASED ARCHITECTURE. THAT PICTURE IS SHOWN AGAIN HERE, AND WHAT YOU SEE IS THAT THEY BOTH HAVE THE MEDIA GATEWAY CONTROLLER, THE RESIDENTIAL GATEWAYS, THE PSTN GATEWAY, AND THEY USE THIS MASTER-SLAVE MEGACO PROTOCOL TO COMMUNICATE BETWEEN THEM. HERE IS FIGURE 3 OF THE PATENT AND IT'S CALLED THE EDGE SWITCH NETWORK ARCHITECTURE. WHAT THE PATENT SAYS IS THAT

THERE ARE THREE CONNECTIVITY ELEMENTS IN THIS ARCHITECTURE: THE EDGE SWITCHES, WHICH ARE THE SWITCHES ON THE CUSTOMER PREMISES, THE APPLICATION SERVER, AND THE PSTN GATEWAY. APPLICATION SERVER ON TOP LEFT AND PSTN GATEWAY KIND OF IN THE MIDDLE OF THE DIAGRAM. AND ALL THESE CONNECTIVITY ELEMENTS

USE SIP FOR COMMUNICATION AND THEY COULD OPTIONALLY CONNECT TO NETWORK-BASED SIP PROXY SERVERS. HERE YOU SEE THE SMARTS, AND

THE NETWORK IS AT THE EDGE AND THE NETWORK ITSELF IS JUST A DUMB TRANSPORT NETWORK. AGAIN, THIS IS PRETTY SIMILAR TO WHAT WE'VE SEEN BEFORE IN TERMS OF THE ARCHITECTURE USING SIP. HERE ARE THE SIP EDGE

DEVICES WHICH ARE INTELLIGENT DEVICES THAT CAN USE SIP TO COMMUNICATE. HERE IS THE PSTN GATEWAY AND THE APPLICATION

- 45 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 SERVER, AND SIP USED BETWEEN THESE. LET'S TAKE A CLOSER LOOK AT HOW THESE BUILDING BLOCK ELEMENTS ARE IMPLEMENTED WITHIN THE `519 PATENT. HERE IS

FIGURE 7 OF THE PATENT WHICH DEPICTS THE SOFTWARE ARCHITECTURE OF THIS DEVICE. WHAT THE EDGE SWITCH DOES IS IT CONNECTS TWO ONE IS KNOWN AS THE SIP PHONE. THESE

TYPES OF TELEPHONES.

ARE PHONES A AND C, AND THE OTHER ONE IS A NON-SIP PHONE, PHONE B. THERE ARE SIP USER AGENTS OUTSIDE OF THIS BOX THAT'S

NOT IN THE DIAGRAM, SO I'VE JUST PUT THAT IN THIS PICTURE TO ILLUSTRATE THAT THEY ARE THERE SO THAT THEY KNOW HOW TO SEND AND RECEIVE SIP MESSAGES. SO LET'S TAKE A LOOK AT WHAT THE EDGE SWITCH DOES FOR A SIP-BASED PHONE. HERE WHAT YOU SEE IS THAT IT REALLY JUST THE USER AGENT IN PHONE A SENDS

SERVES AS A SIP PROXY SERVER.

A SIP REQUEST TO THE SIP PROXY SERVER WHICH IS INSIDE THE EDGE SWITCH. THE SIP PROXY SERVER THEN FORWARDS IT ON TO A SIP SO THAT'S THE

USER AGENT THAT REPRESENTS PHONE C.

FUNCTIONALITY THAT IS PROVIDED BY THE EDGE SWITCH. FOR NON-SIP PHONES, THE EDGE SWITCH PROVIDES ONE ADDITIONAL FUNCTION WHICH IS A TELEPHONE GATEWAY FUNCTIONALITY. THIS IS SHOWN IN THE BLUE BOX. SO WHAT IT

DOES IS THAT WHEN YOU PICK UP A TELEPHONE, THE SOFTWARE WITHIN THE BOX DETECTS THAT THERE WAS AN OFF-HOOK SIGNAL. AND IT

SENDS A DIAL-TONE DOWN SO THE PHONE ­- YOU WILL KNOW THAT YOU ARE CONNECTED. IT THEN USES THE SIP USER AGENT SOFTWARE THERE

- 46 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 TO CONVERT THESE EVENTS TO SIP MESSAGES. SO THE SIP USER

AGENT WHEN THERE IS AN OFF-HOOK WILL START AN INVITE MESSAGE. THAT INVITE MESSAGE THEN IS SENT TO A SIP PROXY SERVER WHICH HAPPENS TO BE IN THE SAME BOX. THESE ARE SOFTWARE

BUILDING BLOCKS, SO YOU JUST LOAD TWO SOFTWARE MODULE INTO THIS SAME MACHINE. AND SIP PROXY SERVER TAKES A LOOK AT THIS

AND FORWARDS IT TO THE SIP USER AGENT, AS WE TALKED ABOUT BEFORE. SO THIS IS HOW THE `519 EDGE SWITCH USES SIP BUILDING SO THAT IS THE END OF MY TUTORIAL.

BLOCKS IN ITS PRODUCT.

THE COURT: THANK YOU. MS. SHARPER: THANK YOU. THE COURT: YOUR COMMENTS HAVE BEEN MOST HELPFUL. WILL START CLAIM CONSTRUCTION, TRY TO, PROMPTLY AT 9. HAVE ANY COMMENTS? MR. VERHOEVEN: YOUR HONOR, WE AGREED ON A MANNER OF PRESENTATION. NOT. THE COURT: I WAS GOING TO TAKE UP IF I HAD ADDRESSED THAT IN MY SCHEDULING ORDER, WHICH I HAVE STARTED TRYING TO DO IN RECENT CASES. HOW DO THE PARTIES ANTICIPATE GOING FORWARD? I DON'T KNOW IF YOU WANT TO HEAR THE DETAILS OR WE

DO YOU

MR. VERHOEVEN: WELL, WE THINK THAT IF WE GO TERM BY TERM FOR EVERY TERM THAT WE WILL HAVE TROUBLE BECAUSE THERE'S SO MANY TERMS, AND IT MAY BE MORE EFFICIENT TO GROUP THE TERMS INTO THREE TRANCHES. AND THE PLAINTIFF WILL GO AND COVER THE

FIRST TRANCHE, AND THEN I'LL GO AND THEN ­-

- 47 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 THE COURT: REPLY. MR. VERHOEVEN: EXACTLY. AND WE'