(12) United States Patent
`Merritt et al.
`
`111111
`
`1111111111111111111111111111111111111111111111111111111111111
`US006421429Bl
`US 6,421,429 Bl
`Jul. 16, 2002
`
`(10) Patent No.:
`(45) Date of Patent:
`
`(54) NETWORK-BASED SYSTEM ENABLING
`IMAGE COMMUNICATIONS
`
`(75)
`
`Inventors: Andrew C. Merritt, Basking Ridge;
`Kenneth H. Rosen, Middletown, both
`of NJ (US)
`
`(73) Assignee: AT&T Corporation, New York, NY
`(US)
`
`( *) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(21) Appl. No.: 09/040,719
`
`(22) Filed:
`
`Mar. 18, 1998
`
`Related U.S. Application Data
`
`( 63) Continuation-in-part of application No. 08/636,200, filed on
`Apr. 22, 1996, now abandoned, which is a continuation of
`application No. 08/175,022, filed on Dec. 2, 1993, now
`abandoned.
`Int. Cl? ............................................... H04M ll/00
`(51)
`(52) U.S. Cl. ................................ 379/93.17; 379/93.15;
`379/100.13
`(58) Field of Search ......................... 379/93.15, 100.13,
`379/88.13, 88.14, 100.08, 100.09, 93.08;
`707/523, 526
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`5,091,931 A * 2/1992 Milewski ............... 379/100.13
`
`5,287,199 A * 2/1994 Zoccolillo .............. 379/100.13
`5,333,266 A * 7/1994 Boaz eta!. .............. 379/93.15
`5,406,557 A * 4/1995 Baudoin .................. 379/93.15
`5,459,775 A * 10/1995 Isono eta!. .............. 379/93.15
`5,524,137 A * 6/1996 Rhee ..................... 379/100.13
`5,740,231 A * 4/1998 Cohn et a!. .............. 379/93.01
`5,872,926 A * 2/1999 Levac eta!. ........... 379/100.13
`6,119,137 A * 9/2000 Smith eta!. ................ 707/523
`
`* cited by examiner
`
`Primary Examiner-Stella Woo
`(74) Attorney, Agent, or Firm-Morgan & Finnegan, L.L.P.
`
`(57)
`
`ABSTRACT
`
`A system is disclosed which enables a multitude of dissimi(cid:173)
`lar end-system devices, appliances, and platforms to inter(cid:173)
`change image information. The inventive method utilizes a
`directory database of end-user profiles, a session manager, a
`conversion manager, individual conversation processors, a
`queuing database, and a store-and-forward file-folder data(cid:173)
`base. The system accommodates pre-subscribed end-users
`as well as non-subscription users. The system handles both
`real-time and store-and-forward communications modes.
`The present invention may be practiced as either a one-node
`or a multi-node distributed architecture, scalable as required,
`and may be either network-based or premises-based, or a
`hybrid combination of these. Communications transport
`both into and out of the node(s) can range from voiceband
`telephone on analog circuits to high speed channel or
`fact-packet protocol communications modes.
`
`25 Claims, 9 Drawing Sheets
`
`IMAGE CALL ORIGINATION
`CALLING
`DEVICE(S)
`
`0
`
`30 '
`
`0 ~
`
`(N)
`
`IMAGE COMMUNICATIONS SYSTEM
`OVERALL CONFIGURATION
`
`IMAGE CALL TERMINATION
`CALLED
`DEVICE(S)
`
`0 r 40
`
`0 EJ
`
`(M)
`
`ORIGINATING
`IMAGE
`
`~ t
`
`./10
`
`r22
`IMAGE COMMUNICATIONS
`SESSION MANAGER
`
`t
`
`TERMINATING
`IMAGE
`~
`
`IMAGE
`PROFILE
`DATABASE
`
`IMAGE FORMAT
`AND
`PROTOCOL CONVERSION
`CONTROL PROCESSOR
`
`SESSION
`STORAGE
`
`AT&T - Exhibit 1004
`
`1
`
`

`

`U.S. Patent
`
`Jul. 16, 2002
`
`Sheet 1 of 9
`
`US 6,421,429 Bl
`
`FIG. 1A
`NEnNORK-BASED IMAGE PROTOCOL
`AND
`FILE FORMAT DATABASE
`
`r tB
`CALLING
`PARTY
`
`-
`
`-
`
`r 12
`NETWORK-BASED
`IMAGE
`PROCESSING
`NODE
`
`r 10
`
`-
`
`r20
`CALLED
`PARTY
`
`r 16
`NETWORK-BASED
`IMAGE
`CONVERSION
`SERVER
`
`I
`
`I
`
`I
`DATABASE INQUIRY
`FOR CALLED PARTY
`PREFERRED
`IMAGE PROTOCOL
`AND
`FILE FORMAT
`
`I
`
`F-.
`
`:::::
`DATABASE lr 14
`....._
`.....
`
`2
`
`

`

`U.S. Patent
`
`Jul. 16, 2002
`
`Sheet 2 of 9
`
`US 6,421,429 Bl
`
`FIG.
`
`tB
`
`ENTER
`
`101
`
`CALLER IN IT IA TES
`IMAGE COMMUNICATION
`
`103
`COMMUNICATION ROUTED
`TO NETWORK NODE
`
`105
`QUERY DATABASE FOR
`SUBSCRIBER INFORMATION
`
`YES
`
`NO
`
`109
`
`CONVERT IMAGE
`
`111
`COMMUNICATE IMAGE
`TO DESTINATION
`
`3
`
`

`

`FIG. 2
`IMAGE COMMUNICATIONS SYSTEM
`OVERALL CONFIGURATION
`
`IMAGE CALL ORIGINATION
`CALLING
`DEVICE(S)
`
`[ #]
`' 0 ~ I
`
`30
`
`I
`~\
`
`.
`
`(N)
`
`ORIGINATING
`IMAGE
`c:::::$=1
`I
`
`- · · - · - -
`
`_J 10
`
`r22
`IMAGE COMMUNICATIONS
`SESSION MANAGER
`
`TERMINATING
`IMAGE
`c:::::$=1
`I
`
`IMAGE CALL TERMINATION
`CALLED
`DEVICE(S)
`
`0 ( 40
`
`I
`
`I o ~
`.
`
`w ~ \
`
`~24
`
`(M)
`
`IMAGE FORMAT
`AND
`PROTOCOL CONVERSION
`CONTROL PROCESSOR
`<:
`7
`I
`
`I
`
`27t
`
`~ONVERSION
`
`ESSOR
`#1
`
`27n
`I
`CONVE~SION
`PROCESSOR
`#n
`
`- - - -
`
`272
`.--------'------.
`CONVERSION
`PROCESSOR
`#2
`- - - -
`
`d •
`\Jl
`•
`~
`~ ......
`~ = ......
`
`~
`
`~
`'"""' 0'1
`N c c
`
`~
`
`N
`
`'JJ. =(cid:173)~
`
`~
`~
`0 ......,
`'0
`
`e
`
`rJ'l
`0'1
`~
`N
`1--"
`~
`N
`\0
`~
`1--"
`
`4
`
`

`

`FIG. 3A
`IMAGE COMMUNICATIONS SYSTEM
`CASE 1: CALLING SUBSCRIBER WITH
`IMAGE FILE MATCH
`AND
`REAL-TIME COMMUNICATIONS
`
`IMAGE CALL ORIGINATION
`CALLING
`DEVICE(S)
`
`30
`
`ORIGINATING
`IMAGE
`c::$:J
`
`(N)
`
`!"-
`
`IMAGE-
`COMMUNICATIONS
`SESSION
`MANAGER
`
`I
`
`I
`
`IMAGE CALL TERMINATION
`CALLED
`DEVICE(S)
`
`TERMINATING
`IMAGE
`c::$:J
`
`40
`
`...................
`
`....... ..._..._
`
`- - - -
`(3)
`.........
`--~--
`
`__ ...,..,..,.,..,.
`
`24
`
`~---L-L..
`
`_r26
`
`28 1
`
`IMAGE FORMAT
`AND
`PROTOCOL CONVERSION
`PROCESS CONTROLLER
`
`lSESSION
`STORAGE
`
`(M)
`
`I
`
`27t
`
`~ONVERSION
`
`ESSOR
`#1
`-
`
`272
`CONVERSION
`PROCESSOR
`#2
`
`27n
`I
`CONVE~SION
`· • • · • PROCESSOR
`#n
`
`-
`
`-
`
`d •
`\Jl
`•
`~
`~ .....
`~ = .....
`
`~
`
`~
`'"""' 0'1
`N c c
`
`~
`
`N
`
`'JJ. =(cid:173)~
`
`~
`~
`0 ......,
`'0
`
`e
`
`rJ'l
`0'1
`~
`N
`1--"
`~
`N
`\0
`~
`1--"
`
`5
`
`

`

`FIG. 3B
`IMAGE COMMUNICATIONS SYSTEM
`CASE 2: CALLING SUBSCRIBER WITH
`IMAGE FILE MATCH
`AND
`STORE AND FORWARD COMMUNICATIONS
`
`IMAGE CALL ORIGINATION
`CALLING
`DEVICE(S)
`ldl
`30\l8:,
`
`ORIGINATING
`IMAGE
`c=$=1
`
`----~ I
`
`IMAGE CALL TERMINATION
`CALLED
`DEVICE(S)
`
`,
`
`'fU
`
`I
`
`Is I
`
`[ # l
`r~~£-¥8!!:.5?) ~ l~
`l '.~.r
`:
`E-MAIL (4)
`! r·------------(cid:173)
`I I
`
`.-,
`
`-- •
`
`1
`
`..L 28
`
`(U)
`
`27n
`I
`CONVE~SION
`PROCESSOR
`#n
`
`d •
`\Jl
`•
`~
`~ .....
`~ = .....
`
`~ = :-
`'"""' ~~
`N c c
`
`N
`
`'JJ. =(cid:173)~
`~ .....
`Ul
`0 ......,
`'0
`
`e
`
`rJ'l
`0'1
`~
`N
`1--"
`~
`N
`\0
`~
`1--"
`
`(N)
`
`IMAGE COMMUNICATIONS
`SESSION MANAGER
`
`IMAGE FORMAT
`AND
`PROTOCOL CONVERSION
`PROCESS CONTROLLER
`<
`7
`I
`
`I
`
`l 272
`I CONVERSION I
`PROCESSOR
`#2
`- - - -
`
`I
`
`27t
`
`U50NVERSION
`
`ESSOR
`#1
`
`6
`
`

`

`FIG. 4A
`IMAGE COMMUNICATIONS SYSTEM
`CASE 3: CALLING SUBSCRIBER WITH NO FILE MATCH
`AND
`NEAR-REAL-TIME COMMUNICATIONS
`
`d •
`\Jl
`•
`~
`~ ......
`~ = ......
`
`IMAGE CALL ORIGINATION
`CALLING
`DEVICE(S)
`
`IMAGE CALL TERMINATION
`CALLED
`DEVICE(S)
`
`30
`
`ORIGINATING
`
`c::::$::J
`IMAGE
`
`-
`
`TERMINA liNG
`IMAGE
`~
`c::::$::J
`
`40
`
`~
`
`~
`'"""' 0'1
`N c c
`
`~
`
`N
`
`(N)
`
`IMAGE-
`COMMUNICATIONS
`SESSION
`MANAGER
`
`I
`
`t--
`
`,__
`
`__L__l_
`
`I
`~-...-
`---.......
`.,.,
`__
`' (5) --- .... \
`1 .... (5)
`(3)J f(s) -f~6 .. rt~2B'
`I ~
`IMAGE FORMAT AND
`PROTOCOL CONVERSION
`SESSION
`...__ -
`PROCESS CONTROLLER
`STORAGE
`(4)
`
`I (~ I
`' . -
`
`IMAGE
`PROFILE
`DATABASE
`
`I
`
`27t
`
`~ONVERSION
`
`ESSOR
`#1
`-
`
`272
`CONVERSION
`PROCESSOR
`#2
`
`27n
`I
`CONVE~SION
`· · · · · PROCESSOR
`#n
`
`-
`
`-
`
`(M)
`
`'JJ. =(cid:173)~
`
`~
`0'1
`0 ......,
`'0
`
`e
`
`rJ'l
`0'1
`~
`N
`1--"
`~
`N
`\0
`~
`1--"
`
`7
`
`

`

`FIG. 4B
`IMAGE COMMUNICATIONS SYSTEM
`CASE 4: CALLING SUBSCRIBER WITH NO FILE MATCH
`AND
`STORE AND FORWARD COMMUNICATIONS
`
`IMAGE CALL TERMINATION
`CALLED
`DEVICE(S}
`
`~~~E-~~~J?) m
`
`I
`
`E-MAIL (6)
`~--------------
`
`l~
`
`I
`
`I
`
`'
`
`I
`
`•: 40
`I I -
`
`(
`
`IMAGE CALL ORIGINATION
`CALLING
`DEVICE(S)
`
`ORIGINATING
`IMAGE
`c=$::1
`
`(N}
`
`I•
`
`IMAGE
`COMMUNICATIONS
`SESSION
`MANAGER
`
`I
`
`I
`
`...... ___
`-- ......
`
`\
`
`\
`
`(3)
`IMAGE FORMAT AND
`PROTOCOL CONVERSION
`PROCESS CONTROLLER
`(4)
`
`(M)
`
`1
`
`27t
`
`~ONVERSION
`
`ESSOR
`#1
`
`272
`r------L----'----,
`CONVERSION
`PROCESSOR
`#2
`- - - -
`
`- - - -
`
`~-----.-.--..:..;
`
`27n
`I
`CONVE~SION
`PROCESSOR
`#n
`
`d •
`\Jl
`•
`~
`~ ......
`~ = ......
`
`~ = :-
`'"""' ~~
`N c c
`
`N
`
`'JJ. =(cid:173)~
`~ .....
`-..J
`0 ......,
`'0
`
`e
`
`rJ'l
`0'1
`~
`N
`1-"
`~
`N
`\0
`~
`1-"
`
`8
`
`

`

`FIG. 5
`IMAGE COMMUNICATIONS SYSTEM
`CASE 4: CALLING SUBSCRIBER WITH NO FILE MATCH
`AND
`STORE AND FORWARD COMMUNICATIONS
`
`d •
`\Jl
`•
`~
`~ ......
`~ = ......
`
`IMAGE CALL ORIGINATION
`CALLING
`DEVICE(S)
`
`30~\\ S
`
`I , • :
`•
`
`I
`
`I
`
`(N)
`
`IMAGE
`
`~ __________ (7l yprc~ :-MA!~ ____ .. -----·1
`(6)..!:-~AI~----------------1 j
`-t=':F-
`ORIGINATING II T
`-- -----
`~-~-----,
`I
`-
`c:::::$:J
`.I I - IMAGE
`I ', ----,\
`
`- • • - • • - • •
`
`I
`
`I
`
`r 22
`
`-
`
`I
`
`(3)
`.
`IMAGE FORMAT AND
`PROTOCOL CONVERSION
`PROCESS CONTROLLER
`(4)
`
`281
`
`~ •
`
`I ...L
`
`I
`
`COMMUNICATIONS
`SESSION
`MANAGER
`
`~
`
`~
`"""" 0'1
`N c c
`
`~
`
`N
`
`'JJ. =(cid:173)~
`
`~
`00
`0 ......,
`'0
`
`e
`
`rJ'l
`0'1
`~
`N
`1--"
`~
`N
`\0
`~
`1--"
`
`I
`
`27t
`
`~ONVERSION
`
`ESSOR
`#1
`
`272
`,.------L---..6----,
`CONVERSION
`PROCESSOR
`#2
`- - - -
`
`~-......---'-;
`
`27n
`I
`CONVE~SION
`PROCESSOR
`#n
`
`L.....--
`
`- - - -
`
`9
`
`

`

`FIG. 6
`IMAGE COMMUNICATIONS SYSTEM
`CASE 6: SUBSCRIBER CALLING A NON-SUBSCRIBER
`
`IMAGE CALL ORIGINATION
`CALLING
`DEVICE(S)
`
`IMAGE CALL TERMINATION
`CALLED
`DEVICE(S)
`
`~j6) -~OIC~:-MA)~l
`
`(5) E-MAIL
`
`I
`
`- - - - - - - - - - - - - - - , I
`
`, 1 t
`~ I
`ORIGINATING
`..!..
`IMAGE
`
`I
`
`I
`
`(N)
`
`I
`
`27t
`
`~ONVERSION
`
`ESSOR
`#1
`
`IMAGE FORMAT
`AND
`PROTOCOL CONVERSION
`PROCESS CONTROLLER
`l 272
`I CONVERSION I
`PROCESSOR
`#2
`- - - -
`
`-
`
`IMAGE COMMUNICATIONS
`SESSION MANAGER
`
`~!~E-~~!!:__(~) ~ [ ,#' J
`!
`E-MAIL (3)
`1 r·-------------
`~
`
`-
`
`~·
`
`I
`
`I
`
`~-:
`
`40
`
`(M)
`
`I
`I -.l. 28
`
`-
`
`•
`
`SESSION
`STORAGE
`
`I
`
`~-,______,
`
`27n
`I
`CONVE~SION
`PROCESSOR
`#n
`
`- - - -
`
`d •
`\Jl
`•
`~
`~ ......
`~ = ......
`
`~ = :-
`'"""' ~~
`N c c
`
`N
`
`'JJ. =(cid:173)~
`~ .....
`'0
`0 ......,
`'0
`
`e
`
`rJ'l
`0'1
`~
`N
`1--"
`~
`N
`\0
`~
`1--"
`
`10
`
`

`

`US 6,421,429 Bl
`
`1
`NETWORK-BASED SYSTEM ENABLING
`IMAGE COMMUNICATIONS
`
`This is a continuation-in-part of application Ser. No.
`08/636,200, filed Apr. 22, 1996, ABN which is a continua(cid:173)
`tion of application Ser. No. 08/175,022, filed Dec. 29, 1993,
`ABN.
`
`TECHNICAL FIELD
`
`The present invention relates generally to a method for
`image communications, and more particularly, to a method
`and system for communicating images across a network
`among users with disparate end systems running potentially
`dissimilar image protocols and formats.
`
`BACKGROUND OF THE INVENTION
`
`2
`methods, and image formats for each user. A communication
`of an originating image from a calling party to a called party
`is diverted to the network-based image processing system.
`The network-based image processing system ascertains
`5 whether the originating image file format and protocol
`matches the called party preferred file format and protocol,
`which is stored in the data base. If there is no match, the
`processing system appropriately converts the originating
`image file to the format and protocol of the called party. The
`10 image file is then communicated to the called party. A
`handshake-like exchange may be used to enable image
`communications of parties that are not subscribers and do
`not have profiles in the database. In a further embodiment,
`the network-based nodal image processing system provides
`15 for file return to the called party. The method and system of
`the present invention may be applied in systems ranging
`from local premises-based communications to wide area
`communications on either private or public networks.
`
`The problem of image file format compatibility has been
`an issue since the beginning of computer-based processing
`of even the most basic graphics. Each computer and soft- 20
`ware vendor developed a different approach to representa(cid:173)
`tion of graphics and images, often suited to a particular
`application area. For example, vendors of word processing
`systems each developed their own approach for the repre(cid:173)
`sentation of pictorial information that could be incorporated 25
`in files generated by their platforms.
`As end users began to network microcomputers, first over
`departmental local area networks, and then over wider area
`networks, the problem of file format compatibility began to
`grow. Today, with the widespread introduction of image, 30
`multimedia, and video systems, file format compatibility is
`a major issue in system development and operation.
`A number of solutions to this problem have been intro(cid:173)
`duced or proposed. At the applications level, file import and
`file export functions have been added which accommodate
`a few formats that are different from the active format of the
`application platform itself. The second solution has been the
`introduction of software which does nothing but convert one
`file format to another. A third solution is to convert all files
`to an intermediary format, which then can be used as the 40
`"universal language" among dissimilar systems, and then
`converted to a different native file format at a receiving
`end-user.
`These approaches have proved useful in and of them(cid:173)
`selves for a number of situations, but as imaging applica(cid:173)
`tions become more prevalent, image processing software
`continues to evolve, image communications becomes more
`feasible over a wider range of system applications, and
`concomitantly as the need for and use of image communi(cid:173)
`cations increases, it becomes ever more difficult and costly
`for users to maintain updated premises software. Further, the
`requirement of converting between a multitude of formats
`and protocols serves as an impediment to widespread access
`and use of image communications.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The invention will be described in greater detail below by
`way of reference to the accompanying drawings, wherein:
`FIG. 1A shows a generic configuration of an image
`communication system in accordance with practicing the
`present invention;
`FIG. 1B is an operational flow chart of an exemplary
`process for image communications, in accordance with the
`present invention;
`FIG. 2 shows a configuration of an image communication
`system in accordance with practicing the present invention;
`and
`FIG. 3A, FIG. 3B, FIG. 4A, FIG. 4B, FIG. 5, and FIG. 6
`illustrate different information flow sequences in accordance
`35 with practicing the present invention for the system depicted
`in FIG. 2.
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENT
`FIG. 1A diagrams a generic system configuration in
`accordance with practicing the present invention, and is not
`limited to any particular network, but may represent for
`example, a private/premises-based network, or a public
`network such as a public switched telecommunications
`45 network (PSTN). As shown in FIG. 1A, a network-based
`image communications processing system 10 includes an
`image processing node 12, a database 14, and an image
`conversion server 16. Preferably, the database 14 maintains
`information for image service subscribers. As understood by
`50 one skilled in the art, such a system may be implemented as
`either a one-node or a multi-node distributed architecture,
`scalable as required, and may be either network-based or
`premises-based, or a hybrid combination of these. In a
`multi-node distributed architecture, preferably a plurality of
`55 image processing nodes 12, each which supports the image
`communications protocol, would access a centralized data(cid:173)
`base 14, while a separate image conversion server 16
`preferably would be located at each node and be accessible
`to other nodes via a gateway or bridge. If the network were
`60 to represent the AT&T interexchange network, for example,
`in addition to other possible network elements that are
`known to one skilled in the art, such a node may be
`implemented in accordance with one or more of the follow(cid:173)
`ing elements: an adjunct processor (AP) (e.g., a network
`65 services complex "NSCx"), a network switch (e.g., 4ESS or
`SESS), and a service control point (SCP) (e.g., a network
`control point "NCP"). Such elements are well known in the
`
`SUMMARY OF THE INVENTION
`
`The present invention overcomes the above, and other,
`limitations by providing a system which enables a multitude
`of dissimilar end-system devices, appliances, and platforms
`to interchange image information. In an embodiment of the
`present invention, a network-based image processing system
`includes a network-based data base which holds profiles of
`the end users. The profiles typically include the capabilities
`of the end systems of the subscribing end users for storing,
`processing, and displaying images, preferably including the
`acceptable and preferred image protocols, compression
`
`11
`
`

`

`US 6,421,429 Bl
`
`3
`art, as is their adaptation for implementing functions and
`services. As understood by one skilled in the art, overall
`system requirements will affect the preferred physical imple(cid:173)
`mentation of a network-based image communications
`system, and there are many variations and adaptations
`within the purview of the present invention.
`In accordance with the present invention, FIG. 1B illus(cid:173)
`trates an operational flowchart for a method of image
`communications. In step 101, a calling party 18 initiates an
`image communication to called party 20. This communica(cid:173)
`tion arrives at the network image processing node 12 (step
`103), and the originating party's sending file format and
`protocol is compared to the preferred profile for the termi(cid:173)
`nating party through a look-up procedure in the network(cid:173)
`based database 14 (step 105). Next, in step 107, if the
`originating and terminating file formats match, then a direct 15
`communications channel (e.g., virtual circuit or direct circuit
`switched) is established between the respective parties (step
`111). If the originating and terminating image file formats do
`not match, however, then the network-based service will
`invoke and attach image converter server 16 which will 20
`perform the necessary file format and protocol conversions
`(step 109), followed by establishing a connection to the
`called party (step 111) for communicating the converted file.
`The foregoing sequence of events may occur in real-time or
`may be implemented in a "store-and-forward" 25
`communications, in which the image data to be sent to the
`called party is temporarily stored within the network, and
`forwarded to the called party at a later time. It is further
`understood that the network may determine the format and
`protocol of the calling party image either by looking up this 30
`information in the database 14 during communication setup,
`or directly from the image data transmission, using either
`in-band or out-of-band signaling.
`It is also understood that routing of the initial communi(cid:173)
`cations to the node in step 103 may occur in a variety of
`ways depending on the type of network with which the 35
`present invention is practiced, as well as the communica(cid:173)
`tions protocol. For example, if the network is the AT&T
`network and the calling device includes a modem, for
`example, then nodal access may occur via switched access
`using, for example, an 800 number or other special access 40
`code, or via a direct-network connection. On the other hand,
`if the network is a private network, then a special access
`code also may be used or the communications protocol may
`include a means for indicating that the data to be commu(cid:173)
`nicated is image data.
`The present invention may further be understood with
`reference to the embodiment shown in FIG. 2, which further
`illustrates elements of a nodal image communications
`system, and particularly a network-based image communi(cid:173)
`cations processing system 10, in accordance with practicing 50
`the present invention. Referring to FIG. 2, at a network node,
`a number of discrete servers are networked on a data link
`such as an Ethernet or FDDI (i.e., fiber distributed data
`interface) bus. As schematically depicted, more than one
`calling device 30 may access the network by any of a variety 55
`of means, including switched access or direct-network
`connection, and the network may connect to a called device
`40 by any of a similar variety of means. It is understood that
`the servers, schematically depicted in FIG. 2A, generally
`comprise one or more physical devices having hardware 60
`and/or software to accomplish the herein described func(cid:173)
`tions. In a most basic implementation, a single network node
`includes all servers; more generally, the servers may be
`distributed as determined by existing or desired system
`architecture, desired system performance, etc. Preferably, 65
`each of the servers include the following respective func-
`tions.
`
`4
`The session manager server 22 provides for input/output
`queuing of image conversion requests, and for login and
`password management of the incoming (call originating)
`party. It also stores (queues) the incoming image file(s) until
`5 processing is required (e.g., conversion), as well as the
`output file(s), which may be either held in session storage
`device 28 for future store-and-forward to the called party, or
`sent immediately after processing is completed. As an
`example of the types of hardware and software that must be
`10 supported to implement these functions, the session manager
`server 22 includes modem banks, e-mail support software,
`interfaces to voice-mail, memory storage devices, one or
`more programmable computers or workstations, program(cid:173)
`mable switches, etc.
`The profile database server 24 provides a platform for the
`Subscriber Profile Database. This database contains a multi(cid:173)
`parameter field for each subscriber, the elements of which
`describe the image file formats and protocols that can be
`accepted by this subscriber, as well as the preferred file
`format and protocol.
`As may be appreciated, and as will be more fully under(cid:173)
`stood below, from among the image file formats and/or
`protocols that can be accepted by the called party, the
`preferred file format and/or format indicated by accessing
`profile database server 24/Subscriber Profile Database (e.g.,
`step 105 ofFIG.1B) may depend on one or more of various
`parameters, including the calling party image file format and
`protocol, the type of image (e.g., medical image, black and
`white photograph, graphics, text, etc.), minimum acceptable
`quality (e.g., spatial resolution, color resolution, etc.) for a
`given image type and/or format, desired transmission time
`for a minimum acceptable quality, etc. Based on the relevant
`ones of such parameters, which may be stored in the
`Subscriber Profile Database (network-based database 14)
`and/or obtained by querying the called party, network imag(cid:173)
`ing processing system 10 determines the preferred or opti-
`mum image format and/or protocol from among the image
`file formats and/or protocols that are supported by the called
`party. Such processing to determine the preferred file format
`may be logically implemented by using one or more look-up
`tables which account for the possible combinations of these
`parameters, and may be appropriately partitioned in various
`ways between or among various elements of network image
`processing system 10, including image processing node 12
`45 and database 14 of FIG. 1A, or session manager 22, image
`profile database 24, and control processor 26 of FIG. 2.
`For instance, each profile in the Subscriber Profile Data-
`base of image profile database 24 may be structured itself as
`a look-up table logically indexed by such parameters, such
`that the preferred format and/or protocol is directly elicited
`by querying the Subscriber Profile Database (network-based
`database 14) and is dependent on such parameters as pro(cid:173)
`vided (explicitly or as a coded index) by session manager 22
`(network image processing node 12) to profile database 24
`for accessing the Subscriber Profile Database. In such an
`implementation, session manager 22 or profile database 24
`may appropriately generate from the parameters an index
`used to access the look-up table of the Subscriber profile
`database. In an alternative implementation of the partition(cid:173)
`ing between network session manager 22 (and/or control
`processor 26, or generally image processing node 12 of FIG.
`1A) and profile database server 22/Subscriber Profile Data(cid:173)
`base (or generally network-based database 14 of FIG. 1A) of
`the processing required to determine the preferred format
`and/or protocol, each profile may store information identi(cid:173)
`fying the supported formats and/or protocols and preferably
`also other user-specific parameters or preferences (e.g.,
`
`12
`
`

`

`US 6,421,429 Bl
`
`5
`
`5
`maximum transmission time for certain image types, pre(cid:173)
`ferred default format and/or protocol, etc.), and profile
`database server 24 and/or session manager 22 and/or control
`processor 26 may implement a routine (e.g., using look-up
`tables indexed by the accessed profile information) to deter(cid:173)
`mine the preferred format and/or protocol as a function of
`one or more of the above parameters (i.e., format and/or
`protocol of the originating image, image type, etc.) and the
`information accessed from the given profile of the Sub(cid:173)
`scriber Profile Database (i.e., available or acceptable image
`file formats and/or protocols supported by the called party,
`and any other user preferences, etc.).
`The image file format conversion server converts the
`calling party image file to the acceptable or preferred image
`file format of the called party, depending on the option(s)
`selected by the calling party. This server preferably includes
`conversion control processor 26 and one or more conversion
`processors 271 , 272 . . . 27n. Additional image servers may
`provide other services, such as Image Catalog, Optical
`Character Recognition, Archiving, image enhancement, face
`recognition, image transformation (e.g., special effects,
`color changes, etc.), Image Transaction Processing such as
`conversion to EDI (Electronic Data Interchange, CCITT X.
`12 Standard) or to batch data files for host entry, image
`groupware and image workflow, and bridging for image 25
`conferencing. Such applications may be provided by com(cid:173)
`mercial application programs executed by the servers, or
`special purpose application software and hardware may be
`developed as necessary. As can be appreciated by one skilled
`in the art, the nodal service permits a large library of image 30
`processing software to be maintained and shared economi(cid:173)
`cally by many users.
`In addition, the nodal image communications system may
`include other servers for providing additional functionality
`and services. For instance, an e-mail confirmation-back 35
`server may be used for sending out an e-mail message to the
`calling party regarding the disposition of the image being
`sent to the called party. Namely, that a file conversion was
`needed, was executed successfully, was forwarded to the
`calling party, and was received (file accessed) by the calling 40
`party. Also, as an adjunct or alternative to the e-mail
`confirmation-back server, a voice-mail confirmation-back
`server may inform the calling party of the same or similar
`actions, but through voice-mail messaging.
`The nodal image communications system also preferably 45
`includes a gateway/bridge for connection to other network
`nodes which also provide network-based image processing.
`Such gateways provide for load distribution and balancing,
`but also for some specialized image processing services. The
`gateways may also connect to external systems.
`In addition to the above Server functions, there are several
`access modes for the image nodal processor depicted in FIG.
`lA. A preferred implementation is access from a PC or
`workstation, utilizing a protocol such as TCP/IP
`(Transmission Control Protocol/Internet Protocol). This 55
`access could be through a router/hub interface or directly
`from the workstation utilizing software such as SLIP (Serial
`Line Interface Protocol). At the low end, access into the
`nodal server is via a FAX/modem, in CCITT (ITU) Group 3
`file format. In this case, there would preferably be provided 60
`an audio response unit which receives multifrequency tone
`(e.g., D1MF) entries from the calling party, and issues voice
`messages that elicit these tone responses. Whatever the
`access into the nodal server, these various front-end imple(cid:173)
`mentations pass files to the session manager 22.
`In accordance with the present invention, image commu(cid:173)
`nication preferably occurs in one of two modes-the real-
`
`6
`time mode or the store-and-forward mode. Real time implies
`that once the image data is transmitted from the calling
`device, there is no storage of the image data, or its
`derivatives, for transmission at a predetermined later time.
`In contrast, in the store-and-forward mode files converted at
`the node are held at the node until a predetermined later time
`at which they are sent to the designated called party.
`Designating one of these modes may be an option available
`to the caller, although the network itself may determine the
`10 mode according to factors such as traffic and/or queue
`conditions on the network, and the amount of image pro(cid:173)
`cessing required. In addition, the store-and-forward mode
`may be the default mode, or presented to the caller as an
`option, when a connection cannot be made to the called
`15 party (e.g., busy signal). Also, the mode may be designated
`as a preferred mode of reception option that is specified by
`a subscriber and stored in the image profile database.
`The present invention, and the foregoing system elements
`and their related functions, may be better understood with
`20 reference to FIGS. 3A-6 which further illustrate nodal
`image communications according to the present invention.
`FIG. 3Aillustrates the signaling which occurs when a calling
`subscriber 30 initiates an image communication with an
`image file match to the called device 40, and wherein the
`communication occurs in real time. Such a call may be
`initiated via in-band or out-of-band signaling, and is routed
`to the image nodal processor (e.g., a network node). The
`image communications session manager 22 accesses the
`image profile database 24 to ascertain whether the originat(cid:173)
`ing image format and protocol matches that used or pre(cid:173)
`ferred by the called device. In this instance, since there is a
`match, the image communications session manager 22
`establishes a connection between the calling device 30 and
`the called device 40, and the image is transmitted according
`to the predetermined transmission protocol using the origi(cid:173)
`nating image format.
`FIG. 3B illustrates the signaling which occurs when a
`calling subscriber initiates an image communication with an
`image file match to the called device, and wherein the
`communication occurs using the store-and forward mode.
`As discussed above, the store-and-forward mode may be
`selected by the calling party, or may occur as in response to
`a failed attempt in connecting to the called party. For
`instance, in response to the call arriving at the image nodal
`processor, the image communications manager 22 may
`direct an audio response unit to prompt the caller to enter the
`preferred communications mode using the touch-tone key(cid:173)
`pad on a telephone station or by entering a response from the
`keyboard of the calling device (e.g., personal computer,
`50 workstation, etc.). The sequence of events initially proceeds
`as in the case illustrated in FIG. 3A, with a match being
`indicated by the query of image profile database 24.
`However, instead of immediately establishing a connection
`to the called device, the image communications session
`manager establishes a connection from the calling device to
`the session storage device which stores the converted image
`data. The image communications session manager then
`initiates a communication, by voice-mail and/or e-mail for
`example, to the called device station using a station identi(cid:173)
`fying number (e.g., phone number) stored in the image
`profile database 24. This communication indicates that an
`image file is stored at the image nodal processor.
`Preferably, in order to retrieve images from the image
`communications system, the user accesses the image nodal
`65 processor via a special access number (e.g., an 800 number)
`or, in alternative embodiments, via an internet address. Once
`the user is connected to the image nodal processor, the user
`
`13
`
`

`

`US 6,421,429 Bl
`
`7
`may be identified by enter