Source: http://www.google.com/patents/US7221658?dq=6,263,507
Timestamp: 2015-05-06 17:49:16
Document Index: 507851263

Matched Legal Cases: ['arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 12', 'arty 13', 'arty 12', 'arty 12', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 12', 'arty 13', 'arty 12', 'arty 12', 'arty 13', 'arty 12', 'arty 12', 'arty 12', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 12', 'arty 13', 'arty 12', 'arty 13', 'arty 12', 'arty 13', 'arty 13', 'arty 13', 'arty 12', 'arty 13', 'arty 13', 'arty 13', 'arty 12', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 12', 'arty 13', 'arty 13', 'arty 13', 'arty 12', 'arty 13', 'arty 12', 'arty 13', 'arty 12', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 12', 'arty 12', 'arty 13', 'arty 12', 'arty 13', 'arty 12', 'arty 13', 'arty 12', 'arty 13', 'arty 13', 'arty 13', 'arty 13', 'arty 13']

Patent US7221658 - Independent contact spanning multiple access networks - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA personal communications portal maintains presence information about a user who may be available at one or more terminal devices on one or more access networks comprising a multiple access network. The access networks may operate in different transmission modes and may utilize different signaling formats...http://www.google.com/patents/US7221658?utm_source=gb-gplus-sharePatent US7221658 - Independent contact spanning multiple access networksAdvanced Patent SearchPublication numberUS7221658 B1Publication typeGrantApplication numberUS 09/461,119Publication dateMay 22, 2007Filing dateDec 14, 1999Priority dateDec 14, 1999Fee statusPaidPublication number09461119, 461119, US 7221658 B1, US 7221658B1, US-B1-7221658, US7221658 B1, US7221658B1InventorsSteven M. Armstrong, Eric W. Parsons, Elwyn B. Davies, Andrew Newton Harker, David Robert StringerOriginal AssigneeNortel Networks LtdExport CitationBiBTeX, EndNote, RefManPatent Citations (4), Non-Patent Citations (8), Referenced by (12), Classifications (24), Legal Events (7) External Links: USPTO, USPTO Assignment, EspacenetIndependent contact spanning multiple access networks
US 7221658 B1Abstract
FIG. 10 is a schematic diagram illustrating the use of �cooked event triggers�.
The term �multiple access network� refers to a communications network which includes two or more different types of communications networks. It may also be a network accessed using different types of terminals. A public switched telephone network (PSTN) that is connected to a wireless telephone network is an example of a multiple access network.
The term �access network� refers to a communications network, which is situated on the edge or periphery of a �core network� and through which users gain access to the core network. The term �core network� refers to a network that cannot be accessed directly by user-oriented terminal devices, but which is accessed by users indirectly through an access network.
The term �PCP� refers to an automated system for use in a multiple access network which provides a single point of presence for a watched party 13 of that multiple access network at a terminal device 80 connected to one or more of the access networks 50, 51, 52, and 76. A watched party 13 may simultaneously have access to several terminal devices 80 on one or more of access networks 50, 51, 52, and 76. The watched party 13 may also have access to a single device capable of accessing more than one of the access networks 50, 51, 52, and 76. A point of presence is a source of information about whether a watched party 13 is available for contact on a multiple access network 11, which access networks the watched party 13 is presently available on, where that watched party 13 is located on each access network, and/or by which method that watched party 13 should preferably be contacted. A PCP 10 provides a single point of presence despite the fact that a watched party 13 may have more than one terminal and/or different types of terminals for accessing the network in different modes and possibly by different access networks. A PCP 10 may also provide context information rather than just raw presence information. Raw presence information is unprocessed information about the availability, location and capability of a watched party 13 on the communications network. A PCP 10 processes raw presence information according to rules or other pre-specified criteria about watched parties 13 to provide context (e.g. status, location, etc.) information for human operators to understand and work with.
On what kind of device; By whom; At what times; Subscribing to other watched parties' 13 presence information for notification of changes (i.e., tracking the availability of certain watched parties 13); Viewing the presence information of watched parties 13 in real time (i.e., seeing in what ways a particular watched party 13 is available�if at all�at a particular time) and (optionally) receiving continuous updates of this presence information; Establishing communication with watched parties 13 via one of the currently available communication types that are included as part of the watched party's presence information. Although a variety of devices may be employed by watched parties 13 to access PCP 10, these devices can be generally classified as voice devices and data devices. Although only one PCP 10 (with its associated gateways 53-2 and 54-2) is shown in FIG. 1, in practice there could be multiple PCPs 10. A particular watched party's presence information is tracked at a particular PCP 10 which is associated with one or more of the access networks 11.
If a watching party 12 attempts to contact a watched party 13 a contact request is sent to the PCP 10 by the watching party 12. The contact request reaches the PCP 10 via a connection request input 17. These requests may be received via protocols such as ICQ (�I seek you�) or WAP� (Wireless Access Protocol). The watching party 12 may not need to know any of the watched party's direct contact details to make this request; instead, PCP 10's identifier for the watched party 13 is used.
The PCP 10 may allow watching parties 12 to send messages and communications to watched parties 13 even when those watched parties 13 are not �present� or available on the communications network. For example, when a watched party 13 is not logged onto the Internet he or she may allow the PCP 10 to forward email messages and faxes, etc.
However, since the availability information from the PCP 10 is effectively �real time,� if availability of a watched party 13 is withdrawn just after the conference call is attempted, then that watched party 13 may be excluded from the conference call.
FIG. 5 illustrates a ticket agency service 30 as a watched party 13. A watched party 13 that is a service is able to store information 14, and rules 15 in the PCP 10 and to register with the system 10 just like other watched parties 13. Watching parties 12 may send connect or notification requests to the PCP 10 regarding the ticket agency service 30. The notification requests may contain a request to be notified of a change of state in the ticket agency service 30 as well as additional information. For example, the notification request could be a request to be notified about a particular type of concert ticket. Many such notification requests by different watching parties 12 may be made of the PCP 10. Then, once tickets for the particular concert become available, the ticket agency service 30 provides information about this to the PCP 10. This information is provided to the PCP 10 by virtue of an agreement between the ticket agency service 30 provider and the PCP 10 provider. As such the event of the tickets becoming available is an example of a �cooked event trigger� as described in more detail below. The PCP 10 is then able to send notifications to each of the interested watching parties 12 to inform them that the tickets are available. Those skilled in the art will recognize that different watching parties 12 may subscribe to different changes in presence about the same watched party 13 and thus may receive different notifications (e.g., some watching parties may subscribe to receive notification that concert tickets become available on a certain date, others may request presence information about a particular seat, or a particular group, etc.).
Aggregates 40,41 differ from prior-art �buddy lists� (adjuncts to instant messaging services) in several respects. Aggregates 40, 41 are able to request actions on the aggregate's behalf whereas this is not the case for buddy lists, which merely facilitate action by the sender of a message. By creating aggregates 40,41 which have an autonomous status it is possible to enable aggregates 40,41 to be used in ways in which watched parties 13 or watching parties 12 can be used.
An aggregate 40, 41 is able to interact with the PCP 10 in the same way as either a watched party 13 or a watching party 12 as described above except that a �quorum� condition may be used. Those skilled in the art will recognize that an aggregate could allow each member, or a group of members to act for the entire aggregate and the group of members need not be a quorum. For example, when a watched party 13 is an aggregate 40, a determination must be made as to when the PCP 10 should indicate to watching parties 12 that there has been a change of state in the aggregate 40. It could be indicated, e.g., when a predetermined percentage of the members of the aggregate 40 have changed state, or when a specific number of the members of the aggregate 40 have changed state, or alternatively it might be indicated only when all members have changed state. Similarly, when a watching party 12 is an aggregate 41, a �quorum� condition may be used to determine factors relating to requests made by the watching party 12. For example, a determination of when a request should be made and what the request should be. A watched party 13 or a watching party 12 may be a member of more than one aggregate.
In yet another alternative, the PCP 10 forwards communications from the watching party 12 to a forwarding address. The watching party 12 does not gain access to the watched party's direct connection address and the PCP 10 itself does not �know� this direct address.
The capabilities of the PCP 10 are extended by using �cooked event triggers�. These may include non-communication-related events that are provided from a third party service and which occur outside the multiple access network 11 (e.g., the watched party 13 checking into a hotel or checking in for an airline flight, entering information into a calendar service, etc.). Information about these events is provided to the PCP 10 via the events gateways 53-1 in protocol 16.
FIG. 10 is a schematic diagram illustrating the use of cooked event triggers. The operator of a third-party service 902 such as a hotel registration system or an airline check-in system 902 enters into a business relationship 905 with the provider of a PCP 10. A watched party 13 subscribes to the PCP 10 in order to benefit from the PCP 10 service. When this watched party 13 checks into a hotel using the hotel registration service 902, then by virtue of the prior agreement 905 between the hotel registration service 902 and the PCP 10, information about the check-in event is provided to the PCP 10. The check-in event is referred to as a �cooked event trigger� and is provided to the PCP 10 via an event gateway 53 in an access network (not shown, but to which the system 902 is connected).
Examples of external services which may provide cooked event triggers include: security badge swipe systems, hotel registration systems, airline check-in systems, automated highway toll collection systems, calling card systems, etc. The term �cooked� is used to refer to the fact that more information is available from cooked events than just geographical location information. That is, context information is gained, associated with different types of events. For example, an airline check-in event at a particular airport generally means not only that the watched party 13 is geographically at the location of the airport but also that the watched party 13 is about to board a plane (for example). This context information is gained quickly, without the need for the PCP 10 to determine that the geographical location is in the airport (for example, from the watched party's mobile telephone location) and then infer that in the context of an airport, the likely outcome is that the watched party 13 is going to board a plane; the check-in information provides this information quickly and accurately. For example, the PCP 10, without the cooked event trigger, may have inferred wrongly that the watched party 13 was going to board a plane when in fact the watched party 13 was merely visiting the airport to collect someone.
Presence: a quality exhibited by a watched party 13 within a network such as location, availability and/or capability. Location: a form of spatial co-ordinates for a watched party 13. These may be geographical or more abstract e.g., in terms of network topology. A location may correspond to some addresses. Availability: the ability of a watched party 13 to communicate at a given time. In addition to �on-line�/�off-line� status, availability can represent a watched party's willingness to engage in communication. Capability: a measure of forms and capacity of communication a watched party 13 can engage in, e.g. due to constraints imposed by the available devices. Watched party: the subject of presence information. A watched party 13 may be a person, service, etc. Aggregate: a set of a watched parties 13 that may act as a single watched party 13. An aggregate has an exposed presence and may be the subject of a subscription. Watching party: the target for presence information. A watching party 12 may be a person, service, etc. Different watching parties may perceive a different presence for the same watched party 13. Subscribe: an action of a watching party 12 when it registers an interest in the presence of a watched party 13. Notify: an action directed at a watching party 12 relating to a change in presence of a watched party 13 that was previously the subject of a subscribe. Presence indicator: an event external to the presence system that is pertinent to a watched party's presence. Raw presence: an unprocessed collection of presence indicators (which may be related to a single watched party 13). Context Presence: an abstract state derived from a watched party's 13 raw presence according to rules defined for that a watched party 13. Not every new presence indicator results in a change to the context presence. Exposed presence: a view of a watched party's 13 context presence that is exposed to a watching party 12. It is derived according to rules defined for that a watched party 13. Note that a watched party 13 may exhibit a different exposed presence to different audiences. Audience: a class of potential watching parties 12 defined by, or in relation to, a watched party 13. An actual watching party 12 may be part of one or more audiences for a given watched party 13. Partial subscribe: a subscribe action that registers interest in part of the presence of a watched party 13. Changes to other parts of that watched party's presence will not lead to a notification. Although a watched party 13 can be composed of other watched parties 13 (see aggregate) the watched party 13 may also have components that are not a watched parties 13 but which can still be discussed in terms of their presence. Micro-subscribe: a subscribe action that is qualified by the watching party 12 to facilitate differentiation by a watched party's rules between subscriptions by the same watcher. That is, two or more different views of presence could be exposed to a watching party, regarding the same a watched party 13, related to separate micro-subscriptions. Communication: an interaction involving more than one participant in which information is transferred. A communication is characterized by the pattern of the interaction and by the media of the information transfer. Interaction pattern: a message interaction, a conversational interaction or a stream interaction, (in the context of this architecture). Message interaction: an instant message, a deferred message or an acknowledged message. Instant message: a message that is delivered to the other participant(s) without explicit action on their part. Deferred message: a message that is delivered to the other participant(s) only after explicit action on their part, e.g. e-mail and voice-mail. Acknowledged message: a message where the sender cannot engage in another action until the message is delivered to the other participant(s). Sender: the initiator of a message interaction. Conversational interaction: an (interleaved) exchange of messages, e.g. an Internet chat session. Stream interaction: an interaction involving one or more continuous data flows between the participants. Separate flows may go in opposite direction between participants. There may be several distinct flows between the same participants in the same direction. A stream interaction can be classified as simplex, half-duplex or (full) duplex. A 2-way voice call is a stream interaction at the terminal level. Caller: the initiator of a conversational interaction or a stream interaction. Media: a form of representation used for transferring information. Possible media are, files, text, audio (including speech), fax, video, etc. Mediation: the action of transforming one kind of communication into another. This may entail a media transformation and/or an interaction pattern transformation. Mediated communication: a communication that includes a mediation action. Proxy communication: a communication in which there is an intermediary between the participants. Third-party communication: a communication that is initiated by a non-participant. Service discovery: the process by which something becomes aware of the existence of a relevant service. Service description: a representation of what a service does in a form that is understood by the service provider and by the user of the service. FIG. 7 shows the PCP 10 of FIG. 3 in more detail. Watching parties 12 and watched parties 13 have access to the PCP 10 via multiple access network 11. In this example the multiple access network 11 comprises an Internet Protocol (IP) communications network 50, a wireless communications network 51, a PSTN 52, and an ISP 76. However, those skilled in the art will realize that different types and combinations of access networks could be used to form the multiple access network 11.
Inputs from the multiple access network 11 to the PCP 10 are provided in the form of event gateways 53. Also, connection requests, from watching parties 12 to the PCP 10 are accepted via connection request inputs which, for example, may be provided using the WAP protocol 61 or ICQ (�I seek you�) protocol 62. When the PCP 10 is used to establish connections between watching parties 12 and watched parties 13, a connection from the PCP 10 to the multiple access network 11 is provided in the form of connect gateways 54.
Contact addresses for that watched party 13 on each of a number of access networks or component parts of an access network. A set of the possible context presence values for the watched party 13, e.g. �at-home�, �at-work�, �travelling�, �not-able-to-contact�. �unknown�, etc. For many of these the system also holds attributes, e.g. geographical location. Minor changes to the default rules for moving from one context presence to another. The watched party's own view of what potential audiences its exposed presence has, e.g. family, friends, colleagues. Members of each potential audience may see a different projection of the watched party's presence. In application to enterprises, the administrator is able to provide audience definitions common to many entities (e.g., E-mail distribution lists). A watching party 12 authentication level for each audience to allow the watched party 13 to have safeguards that a watching party 12 really does belong to an audience. For some sorts of communication (e.g. instant messages informing of new E-mail) the watched party 13 may wish to exercise fine-grained control and insist on the watching party 12 making a micro-subscription. The attributes of such a subscription can also be subject to a watched party's rules 15 (e.g., E-mail filters) When a watched party 13 is first registered with a PCP 10 there is a substantial amount of data capture required. In order that the work-load of the watched party 13 is reduced reliance may be placed on default information and a type of �wizard� used to help the watched party 13 enter the required information quickly and easily. Later, the data can be subsequently modified by the watched party 13. These functions are carried out by the profile management system 56.
For example, in the case of a watched party 13 representing a human user (as opposed to an automated service) the interaction provided by the �wizard� data capture process can be as follows:
The watched party 13 chooses from a number of life-styles, �office-worker�, �travelling-salesman� or �executive�. Each life-style being represented by a template with default values. Each choice leads to a dialog tailored for that choice. For example, to establish the geographical location of the home and of the office. Additional locations are created if appropriate. In an embodiment, the PCP 10 is able to detect and capture details about the devices that the watched party 13 uses for communicating. Definitions of potential audiences for the watched party's presence (family, friends etc.) Finally, the watched party 13 will decide which contact information is notified to members of which audiences for what changes in context presence.
Event gateways 53-1 receive raw data from the access networks, pre-process this and pass it onto the raw presence manager 55 via event gateway 53-2. Examples of these events are keyboard activity on a terminal, movement between cells or change in Visitor Location Register (VLR) in a cellular communications network and off-hook events in a PSTN. Other events include use of the �last offered incoming call� service on a PSTN, details from calendar services and the opening of a Palm Pilot VII� lid. Event gateways 53 produce an authenticated, time ordered series of location data events that have been filtered and homogenized. That is, only information about watched party 13 being tracked by a particular PCP 10 is passed to that PCP 10's raw presence manager 55. This is achieved by using a filter in the event gateway 53. Also, events are presented to the raw presence manager 55 in a technology-neutral format (all the idiosyncrasies of different access network technology are hidden by the event gateway 53 as far as possible).
An aspect of the invention provides that the lifetime of a subscription may be controlled by the watching party 12, i.e. the watching party 12 declares when its interest in a given watched party 13 will be over. However, if the watching party 12 does not take action to declare the end of its interest then old subscriptions may eventually become useless. In the case that subscriptions are held persistently (e.g., for fault recovery) an issue of �garbage collection� arises. For example, all subscriptions that are inactive for one hour or some other prescribed time period may be deleted, etc.
In the case of Instant Message notification of an awaiting e-mail, for example, the decision on whether the watched party 13 is �on-line� to a particular e-mail notification may be a function of the sender, the message size, and possibly of keywords within the subject of the e-mail. Rather than the watching party 12 presenting this second order information at the point of sending the Instant Message, the initial subscription may capture all the information upon which the reachability decision is made. What might have been a single subscription by an e-mail notification service regarding a single watched party 13 may then be replaced by a set of fine-grained subscriptions each regarding that watched party's willingness to receive a certain e-mail notification.
The PCP 10 also comprises an exposed presence manager 58 as illustrated in FIG. 7. �Exposed presence� is a view of a watched party's presence that is exposed to a watching party 12. It is derived according to rules 15 defined for that watched party 13 and in this way, a watched party 13 exhibits different exposed presences to different audiences. The function of the exposed presence manager 58 is to �decide� what information to make available to watching parties 12 on the basis of rules 15 and other criteria 14 set by watched parties 13 or defined as defaults.
The PCP 10 also includes a connection manager 59 in some examples. When the PCP 10 forwards communication requests directly to watched parties 13, the connection manager 59 provides this forwarding facility using connect gateways 54. At least one connect gateway 54-1 is provided for each type of access network. Part of the function of the connection manager 59 is to �decide� which connect gateway 54 should be used for a particular communication request and to manage changes between connect gateways 54 according to the communication requirements. Further, the connection manager determines which access media is used for a given interaction in the event that more than one access medium is available and suitable.
The PCP 10 also includes a raw presence manager 55. The raw presence manager 55 obtains and stores information from the event gateways 53 and processes this information to form a �context presence� for each watched party 13. A variety of default contexts are defined such as �at home�. �at work desk�, �travelling� and information received from the event gateways 53 together with other watched party 13 information is used to determine which context applies for a given watched party 13 at a particular time. Rules 15 are used to aid this determination process. For example, rules 15 for mapping location indicators onto presence contexts are pre-defined. Watched parties 13 are also able to enter their own rules 15 and presence contexts for use by the raw presence manager 55.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS6247043 *Jun 11, 1998Jun 12, 2001International Business Machines CorporationApparatus, program products and methods utilizing intelligent contact managementUS6301339 *Dec 22, 1997Oct 9, 2001Data Race, Inc.System and method for providing a remote user with a virtual presence to an officeUS6301609 *Sep 8, 1999Oct 9, 2001Lucent Technologies Inc.Assignable associate priorities for user-definable instant messaging buddy groupsUS6437818 *May 5, 1998Aug 20, 2002Collaboration Properties, Inc.Video conferencing on existing UTP infrastructure* Cited by examinerNon-Patent CitationsReference112 pages downloaded from http//:www.icq.com on Aug. 11, 1999.22 pages downloaded from http://lucent.com on Apr. 6, 2000 comprising a press release date Jun. 9, 1999.33 pages downloaded from http://www.generalmagic.com on Aug. 11, 1999.44 pages downloaded from http://messenger.msn.co on Aug. 11, 1999.56 pages downloaded from http://www.wildfire.com on Aug. 11, 1999.67 pages downloaded from http://www.oz.com/pulse/ Aug. 1999.7An 11 page copy of "Nortel's Technology Perspective" Monday Oct. 19, 1998.8One page photocopy of a newspaper article. Financial Times Jun. 9, 1999.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7711849 *May 12, 2006May 4, 2010West Notifications Group, Inc.Individual XML message processing platformUS7912899 *Nov 5, 2002Mar 22, 2011Oracle International CorporationMethod for selectively sending a notification to an instant messaging deviceUS8266305 *Sep 18, 2006Sep 11, 2012Akamai Technologies, Inc.Method and system for purging content from a content delivery networkUS8655967Apr 5, 2010Feb 18, 2014West Notifications, Inc.Individual XML message processing platformUS8842157Dec 19, 2012Sep 23, 2014Huawei Device Co., Ltd.Method, apparatus, and system for implementing videoconferencing applicationUS20090097421 *Dec 21, 2007Apr 16, 2009Telefonaktiebolaget Lm Ericsson (Publ)IP-based interworking methods and apparatus for voice and data communicationsUS20130083155 *Aug 30, 2012Apr 4, 2013Cisco Technology Inc.Method, endpoint, and system for establishing a video conferenceCN101945245A *Sep 6, 2010Jan 12, 2011华为终端有限公司Realizing method, device and system of video conference applicationCN101945245BSep 6, 2010Sep 25, 2013华为终端有限公司Realizing method, device and system of video conference applicationWO2013042056A1 *Sep 19, 2012Mar 28, 2013Telefonaktiebolaget L M Ericsson (Publ)Group chat across networksWO2013048697A1 *Sep 7, 2012Apr 4, 2013Cisco Technology Inc.Method, endpoint, and system for establishing a video conferenceWO2014147637A1 *Dec 2, 2013Sep 25, 2014Bhavin TurakhiaGroup message relay* Cited by examinerClassifications U.S. Classification370/260, 709/206International ClassificationH04J1/00Cooperative ClassificationH04L67/24, H04L51/066, H04L51/36, H04L12/589, H04L12/581, H04L61/1547, H04M2207/20, H04L12/1818, H04L12/5835, H04M3/42365, H04L29/12122, H04L12/1836, H04L51/04European ClassificationH04L61/15D, H04L51/04, H04M3/42S, H04L12/58B, H04L29/08N23, H04L29/12A2D, H04L12/18D1, H04L12/58ULegal EventsDateCodeEventDescriptionFeb 9, 2015ASAssignmentOwner name: RPX CLEARINGHOUSE LLC, CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROCKSTAR CONSORTIUM US LP;ROCKSTAR CONSORTIUM LLC;BOCKSTAR TECHNOLOGIES LLC;AND OTHERS;REEL/FRAME:034924/0779Effective date: 20150128Oct 28, 2014FPAYFee paymentYear of fee payment: 8Mar 10, 2014ASAssignmentOwner name: ROCKSTAR CONSORTIUM US LP, TEXASFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ROCKSTAR BIDCO, LP;REEL/FRAME:032422/0919Effective date: 20120509Oct 28, 2011ASAssignmentOwner name: ROCKSTAR BIDCO, LP, NEW YORKFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NORTEL NETWORKS LIMITED;REEL/FRAME:027164/0356Effective date: 20110729Oct 25, 2010FPAYFee paymentYear of fee payment: 4Aug 30, 2000ASAssignmentOwner name: NORTEL NETWORKS LIMITED, CANADAFree format text: CHANGE OF NAME;ASSIGNOR:NORTEL NETWORKS CORPORATION;REEL/FRAME:011195/0706Effective date: 20000830Owner name: NORTEL NETWORKS LIMITED,CANADAFree format text: CHANGE OF NAME;ASSIGNOR:NORTEL NETWORKS CORPORATION;REEL/FRAME:11195/706Owner name: NORTEL NETWORKS LIMITED,CANADAFree format text: CHANGE OF NAME;ASSIGNOR:NORTEL NETWORKS CORPORATION;REEL/FRAME:11195/706Effective date: 20000830Owner name: NORTEL NETWORKS LIMITED,CANADAFree format text: CHANGE OF NAME;ASSIGNOR:NORTEL NETWORKS CORPORATION;REEL/FRAME:011195/0706Effective date: 20000830Mar 27, 2000ASAssignmentOwner name: NORTEL NETWORKS CORPORATION, CANADAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ARMSTRONG, STEVEN M.;PARSONS, ERIC W.;DAVIES, ELWYN B.;AND OTHERS;REEL/FRAME:010691/0895;SIGNING DATES FROM 20000203 TO 20000317RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services