US20030195930A1

System and method for effecting conference calling

Claim Score by NHIP

Abstract

A system for effecting conference calling in a telecommunication network includes: (a) a plurality of subscriber units coupled with the telecommunication network; and (b) a conference control unit coupled with the telecommunication network. The conference control unit responds to a request message from a requesting subscriber unit to effect coupling of a conference-set of subscriber units in a conference calling configuration. The conference control unit controls inclusion in the conference-set by respective subscriber units. The system may provide that the conference control unit provides and controls conferencing services for the conference-set of subscriber units.

US20030195930A1, drawing sheet 1 — Sheet 1 of 4

Term

Term ended

Projected expiry passed 26 February 2025, 1.6 years ago.

20 claims: 3 independent, 17 dependent

1
A system for effecting conference calling in a telecommunication network; the system comprising:(a) a plurality of subscriber units coupled with said telecommunication network;and (b) a conference control unit coupled with said telecommunication network;said conference control unit responding to a request message from a requesting subscriber unit of said plurality of subscriber units to effect coupling of a conference-set of subscriber units of said plurality of subscriber units in a conference calling configuration;said conference control unit controlling inclusion in said conference-set by respective subscriber units of said plurality of subscriber units.
10
A method for effecting conference calling in a telecommunication network; the method comprising the steps of:(a) in no particular order: (1) providing a plurality of subscriber units coupled with said telecommunication network;and (2) providing a conference control unit coupled with said telecommunication network;and (b) operating said conference control unit in response to a request message from a requesting subscriber unit of said plurality of subscriber units to effect coupling of a conference-set of subscriber units of said plurality of subscriber units in a conference calling configuration;said conference control unit controlling inclusion in said conference calling set by respective subscriber units of said plurality of subscriber units.
19
Broadest claimClaim Score 77, broad(NHIP)An apparatus for establishing and controlling conference calling in a telecommunication network; said telecommunication network including a plurality of calling units; the apparatus being coupled with said telecommunication network; the apparatus comprising:a conferencing server unit;said server unit responding to a request message from a requesting calling unit of said plurality of calling units to effect coupling of a conference-set of calling units of said plurality of calling units in a conference calling configuration;the apparatus controlling inclusion in said conference-set by respective calling units of said plurality of calling units.

Independent claims3

30 paragraphs in 4 sections, as filed

BACKGROUND OF THE INVENTION

[0001] The present invention is directed to a system and method for effecting conference calling in a telecommunication network. In particular, the present invention provides a network-based conferencing controller, preferably embodied in a server apparatus that supports and controls conferencing services and participation among a plurality of subscriber or calling units. Representative conferencing services contemplated for control and support using the system of the present invention include text chat, file transfer, shared whiteboard, shared application or presentation, and other conferencing services.

[0002] Prior art conferencing devices or systems use significant amounts of transport bandwidth, memory and computing capacity resident at respective subscriber units, or calling units, for supporting conferencing functions involved in a given conference session. There is a need for a more efficient conferencing system that centrally supports operation of and participation in conferencing. This is especially true for subscriber units with wireless access. Such centralized control and support permits less-capable calling units (e.g., calling units having lesser memory capacity or lesser computing capacity) to participate more fully in conferencing than can be effected using presently available conferencing systems. By way of example, wireless personal digital assistant (PDA) calling units may enjoy fuller participation in conferencing when conferencing is centrally supported and controlled.

[0003] There is a need for improved efficiency in conferencing operations in order that lesser-capable calling units may participate more fully in conferencing operations. The invention advantageously reduces bandwidth utilization as compared with prior art conferencing services or systems and provides improved efficiency sufficient to permit improved participation by lesser-capable calling units over participation that has been heretofore available.

SUMMARY OF THE INVENTION

[0004] A system for effecting conference calling in a telecommunication network includes: (a) a plurality of subscriber units coupled with the telecommunication network; and (b) a conference control unit coupled with the telecommunication network. The conference control unit responds to a request message from a requesting subscriber unit to effect coupling of a conference-set of subscriber units in a conference calling configuration. The conference control unit controls inclusion in the conference-set by respective subscriber units. The conference control unit accepts data streams from multiple sources, such as subscriber units, for a particular application and generates a single data stream output to each subscriber unit. The system may provide that the conference control unit provides and controls conferencing services for the conference-set of subscriber units.

[0005] It is therefore an object of the present invention to provide a system and method for effecting conference calling that offers improved efficiency in conferencing operations.

[0006] It is a further object of the present invention to provide a system and method for effecting conference calling that permits lesser-capable calling units to participate in conferencing operations.

[0007] Further objects and features of the present invention will be apparent from the following specification and claims when considered in connection with the accompanying drawings, in which like elements are labeled using like reference numerals in the various figures, illustrating the preferred embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

P-0008[0008]FIG. 1 is a schematic drawing illustrating a prior art implementation of conference calling.

P-0009[0009]FIG. 2 is a schematic diagram illustrating implementation of conference calling according to the present invention.

P-0010[0010]FIG. 3 is a flow diagram illustrating the method of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

P-0011[0011]FIG. 1 is a schematic drawing illustrating a prior art implementation of conference calling. In FIG. 1, a conference calling system 10 includes a plurality of wireless users 20, 22, 24. Wireless users 20, 22, 24 are also designated Wireless User 1 (20), Wireless User 2 (22) and Wireless User m (24). The indicator “m” is employed to signify that there is no particular limit to the number of wireless users that may be included in conference calling system 10. Conference calling system 10 also includes a plurality of wireline users 30, 32, 34. Wireline users 30, 32, 34 are also designated Wireline User 1 (30), Wireline User 2 (32) and Wireline User n (34). The indicator “n” is employed to signify that there is no particular limit to the number of wireline users that may be included in conference calling system 10.

P-0012[0012] Wireline users 30, 32, 34 are communicatingly coupled with a telecommunication network 40 via wireline connections 60, 62, 64. Wireless users 20, 22, 24 are communicatingly coupled with telecommunication network 40 via wireless connections 50, 52, 54 with a wireless communication access tower 26. Wireless communication access tower 26 is coupled with network 40 via a wireline connection 51. Each wireless user may access the network by a different wireless communication access tower. For the sake of simplicity only one communication access tower is shown in FIG. 1. Each of wireless users 20, 22, 24 and wireline users 30, 32, 34 are equipped with a conferencing capability, generally in the form of software, and perhaps also including hardware, computing capability and memory capacity. Thus, wireless user 20 has a conferencing capability 21. Wireless user 22 has a conferencing capability 23. Wireless user 24 has a conferencing capability 25. Wireline user 30 has a conferencing capability 31. Wireline user 32 has a conferencing capability 33. Wireline user 34 has a conferencing capability 35. One of the subscribing units among wireless users 20, 22, 24 and wireline users 30, 32, 34 acts to host the conference call arrangement. In the exemplary arrangement illustrated in FIG. 1, wireless user 20 is host. However, each other subscriber unit participating in a conference calling arrangement must also have conferencing capability; it is the respective conferencing capabilities 21, 23, 25, 31, 33, 35 that carry out the conferencing function in conference calling system 10.

P-0013[0013] The host (wireless user 20 in FIG. 1) controls entry to a conference calling arrangement. A server 15 is commonly required to provide contact information for the host to add parties to the conference. Server 15 is not involved with the handling of payload in the data streams involved with a conference. Server 15 is coupled with network 40 via a wireline connection 70. Various data conferencing functions may be carried out in conference calling system 10, but they require participation by and among the various conferencing capabilities 21, 23, 25, 31, 33, 35. Such a requirement for a respective conferencing capability 21, 23, 25, 31, 33, 35 among the various subscriber units 20, 22, 24, 30, 32, 34 contributes to the cost and complexity of each subscriber unit 20, 22, 24, 30. 32, 34 because significant memory capacity and computing capacity are required to support conferencing activities. Moreover, the complexity of connection with and data transfer required among respective conferencing capabilities 21, 23, 25, 31, 33, 35 during conferencing operations contributes to a less robust connections and consequent increased susceptibility to interruption of calls, especially with respect to wireless users 20, 22, 24. The traffic load associated with various wireline users 20, 22, 24 and wireline users 30, 32, 34 during conferencing operations is indicated for each wireless connection 50, 52, 54 and wireline connection 51, 60, 62, 64. Wireline connection 70 carries zero bearer streams. That is, server 15 provides only addressing information or similar “overhead” information for establishing conferencing calls; no payload is associated with or included in traffic borne by wireline connection 51. Thus, during conferencing operations, each of wireless connections 50, 52, 54 and wireline connection 51 carries (m+n) bearer streams. A bearer stream is a stream of traffic that includes or bears information, sometimes referred to as payload, among the information in the traffic. Thus, in the exemplary prior art conference calling system 10 (FIG. 1), there are (m+n−1) data streams sent from host wireless user 20 in controlling a conference application in order that all other conference participants may receive a copy of the data. Also, there are (m+n−1) data streams received at each conference participant for any conference application that allows data to be sent from each user, such as a shared whiteboard application.

P-0014[0014] There is a need for a conferencing arrangement, preferably embodied in a network-based conferencing server apparatus, that can support voice conferencing and data conferencing operations among a plurality of subscriber or calling units that reduces the amount of memory and computing resources required of each participating subscriber unit in a conference. Such a network-based conferencing arrangement can advantageously reduce bandwidth requirements for carrying on a conference call as compared with presently available conference calling systems that require significant conferencing capability resident at each calling unit participating in a conference call, as in the case of system 10 (FIG. 1).

P-0015[0015]FIG. 2 is a schematic diagram illustrating implementation of conference calling according to the present invention. In FIG. 2, a conference calling system 110 includes a plurality of wireless users 120, 122, 124. Wireless users 120, 122, 124 are also designated Wireless User 1 (120), Wireless User 2 (122) and Wireless User m (124). The indicator “m” is employed to signify that there is no particular limit to the number of wireless users that may be included in conference calling system 110. Conference calling system 110 also includes a plurality of wireline users 130, 132, 134. Wireline users 130, 132, 134 are also designated Wireline User 1 (130), Wireline User 2 (132) and Wireline User n (134). The indicator “n” is employed to signify that there is no particular limit to the number of wireline users that may be included in conference calling system 110.

P-0016[0016] Wireline users 130, 132, 134 are communicatingly coupled with a telecommunication network 140 via wireline connections 160, 162, 164. Wireless users 120, 122, 124 are communicatingly coupled with telecommunication network 140 via wireless connections 150, 152, 154 via a wireless communication access tower 126. Wireless communication access tower 126 is coupled with network 140 via a wireline connection 151. Each wireless user may access the network by a different wireless communication access tower. For the sake of simplicity only one communication access tower is shown in FIG. 1.

P-0017[0017] A network-based data conferencing control unit, or conferencing host 150 is communicatingly coupled with network 140. Conferencing host 150 is preferably embodied in a server apparatus, but may reside in a computing apparatus such as a mainframe computer, a personal computer (PC) or another computing apparatus coupled with network 140. Conferencing host 150 is coupled with network 140 via a wireline 170 and effects and maintains conferencing arrangements and operations network-wide for all subscriber units or calling units coupled with network 140, including wireless users 120, 122, 124 and wireline users 130, 132, 134. By way of example, and not by way of limitation, wireline users may include Internet protocol (IP) telephony devices as well as Dual Tone Multiple Frequency (DTMF) phone instruments communicating via ISDN (Integrated Services Digital Network) lines, optical lines or other communication connections. Wireless users 120, 122, 124 may include, for example, time division multiple access (TDMA), code division multiple access (CDMA), wireless local area networks (LANs), UMTS (Universal Mobile Telecommunications Systems) protocol sometimes referred to as wideband CDMA, or other protocols for establishing and maintaining calls. An initiating caller (any one of subscriber units 120, 122, 124, 130, 132, 134) may connect via network 140 with conferencing host 150 to initiate a conference call arrangement. Conferencing host 150 includes a calling bridge or other configuration consistent with establishing and maintaining selected subscriber units in a conference calling arrangement.

P-0018[0018] The traffic load associated with various wireline users 120, 122, 124 and wireline users 130, 132, 134 during conferencing operations is indicated for each wireless connection 150, 152, 154 and wireline connection 151, 160, 162, 164. Wireline connection 170 carries (m+n) bearer streams. Each of wireless connections 150, 152, 154 and wireline connections 160, 162, 164 carries one bearer stream. Wireline connection 151 carries m bearer streams. A bearer stream is a stream of traffic that includes or bears information, sometimes referred to as payload, among the information in the traffic. Thus, in the exemplary prior art conference calling system 110 (FIG. 2), there is a single data stream sent from the current user in control of an application (e.g., wireless user 20) to conference control unit 150. Conference control unit 150 sends a copy of the data to all the other users. Only conference control unit 150 receives the multiple (m+n) bearer streams for any application that allows data to be sent from each user, so that only wireline connection 170 carries (m+n) bearer streams.

P-0019[0019] Admission to an ongoing conference call is preferably controlled by conference host 150. In the alternative, any subscriber unit involved in a conference call may include an additional caller in an ongoing conference call. Preferably, new callers may be added to an extant conference call only by conference host 150 in response to a request for such admission submitted to conference host 150 by a subscriber participating in the extant conference call, or by another subscriber unit (not shown in FIG. 2). In yet another alternative arrangement, conference host 150 may be programmed to include a roster of selected calling units upon initially establishing a conference call.

P-0020[0020] Thus, for example, a party desiring to establish a conference call may dial-in access to conference host 150, for example, using a common 10-digit telephone number (e.g., an E.164 number) or a URL (Universal Resource Locator) address commonly used to access a web page via the Internet. Once connection is established with conference host 150, a conference call setup may be established with conference host 150. Conference host 150 preferably keeps a list of participating calling units involved in the extant conference call and may display such a participant list on a display unit at participating caller's sites, or loci.

P-0021[0021] Alternatively, as described briefly above, a conference call participant may dial into conference host 150 (using a 10-digit phone number) or access an appropriate web page associated with conference host 150 (using a URL address) to effect adding an additional caller to an extant conference call. Once connection is established with conference host 150, then conference host 150 may present an interface display at the caller's site to effect entering required information for including an additional caller. In yet another alternate embodiment of the present invention, a prior art conferencing system (e.g., system 10; FIG. 1) may be resident at the caller seeking to add a new participant to an extant conference call. The present invention may be configured to accommodate including a caller conferenced in using a prior art conferencing capability in the network-based conference established by conference host 150.

P-0022[0022] Preferably, conference calling system 110 is configured so that any participant in an extant conference call may place a request with conference host 150 to include an additional caller. It would be preferable to initiate such contact with conference host 150 using the desired new participant's phone number or other identifier. Conference host 150 will then use the identifier information used for making a request to add a new participant to contact the proposed participant. The proposed new participant may then elect whether to participate in the extant conference call or decline to participate. If the proposed new participant opts to accept inclusion in the extant conference call, conference host 150 effects connection appropriate to include the new participate in the extant conference call.

P-0023[0023] If conference host 150 is to be programmed to include a roster of selected calling units upon initially establishing a conference call (as briefly described earlier), conference host 150 must call all predetermined participants at a predetermined time to establish the desired conference call arrangement. In such a circumstance, conference host 150 dials (or otherwise enters) an identifier, such as a phone number (e.g., a 10-digit, E.164 number) or a URL address, for each predetermined participant. As each respective participant answers the initiating call, conference host 150 establishes a conference user interface for display at the respective new participant's site. The conference user interface display may be generated locally at the respective new participant's site or may be provided by conference host 150.

P-0024[0024] Conference host 150 is preferably configured for establishing data conferencing arrangements among conference call participants. Thus, conference host 150 permits any subset of participants in a conference call to exchange text messages among themselves or to all conference call participants. A text message is preferably sent by an originating participant to conference host 150 with an address list indicating intended recipients for the message. Conference host 150 relays the text message to the indicated intended receivers. This arrangement places the need for computing capacity and communication capacity with conference host 150 for carrying out conferencing operations such as text messaging. Respective calling units 120, 122, 124, 130, 132, 134 therefore require less computing capacity and communicating capacity to participate in conference call operations than are required for participation in such operations in prior art conferencing systems, such as system 10 (FIG. 1).

P-0025[0025] Conference host 150 provides similar advantages for other data conferencing operations, such as shared whiteboard conferencing. Preferably, any party participating in a conference call may initiate a whiteboard application. Once a whiteboard application is established, participants in the conference call can take turns drawing on the whiteboard by requesting control of the whiteboard from the participant current controlling the whiteboard via conference host 150. As a user draws or writes on the whiteboard, changes on the whiteboard are transferred from the controlling participant's locus to conference host 150 in real time, or in nearly real time. Conference host 150 subsequently sends whiteboard changes to other conference participants. Changes to the whiteboard may be sent by conference host 150 in real time, in nearly real time or in a packetized signal format.

P-0026[0026] Conference host 150 may also be advantageously employed for other data conferencing operations, such as spreadsheet, word processing or presentation applications. Any of the data conferencing applications may be initiated by any participant from the initiating participant's locus. Once the data conferencing application is established, the initiating participant may opt whether or not to send a saved file associated with the data conferencing application to conference host 150 so that conference host 150 can effect display of the application file to other conference participants. Once a data application is displayed to other conference participants, various participants may take turns editing the extant version of the application file by requesting control of the application file from the currently controlling editing participant. As a respective participant edits an application file, changes effected to the file are transferred by conference host 150 to other participants. The transfer preferably is carried out in real time or in nearly real time, but may be carried out in a packetized format.

P-0027[0027] Conference host 150 may also be advantageously employed for other conferencing operations that involve data conferencing, such as packetized voice operations and streaming video operations.

P-0028[0028]FIG. 3 is a flow diagram illustrating the method of the present invention. In FIG. 3, a method 200 for effecting conference calling in a telecommunication network begins at a START locus 202. Method 200 continues, in no particular order: (1) providing a plurality of subscriber units coupled with the telecommunication network, as indicated by a block 204; and (2) providing a conference control unit coupled with the telecommunication network, as indicated by a block 206. Method 200 continues by awaiting a request for establishing a conference call arrangement, as indicated by a block 208.

P-0029[0029] As method awaits a conferencing request (block 208) a query is posed, “Has a conferencing request been received?”, as indicated by a query block 210. If no conferencing request has been received, method 20 continues from query block 210 via NO response line 212 to return to awaiting a conferencing request (block 208). If a conferencing request has been received, method 20 proceeds from query block 210 via YES response line 214 to operate a conference control unit in response to a request message from a requesting subscriber unit (the conferencing request; block 210), as indicated by a block 216 to effect coupling of a conference-set of subscriber units in a conference calling configuration. The conference calling configuration is preferably set forth in an inclusion request contained in the conferencing request. The conference control unit controls inclusion in the conference calling set by respective subscriber units as indicated by the inclusion request, as indicated by a block 218. The conference control unit further controls processing of other conferencing service requests, including for example establishing and operating text chat services, file transfer services, data conference services and other services, as indicated by a block 220. The conference control unit coordinates the requests from users to control a particular application, as indicated by a block 222.

P-0030[0030] It is to be understood that, while the detailed drawings and specific examples given describe preferred embodiments of the invention, they are for the purpose of illustration only, that the apparatus and method of the invention are not limited to the precise details and conditions disclosed and that various changes may be made therein without departing from the spirit of the invention which is defined by the following claims:

Contents4

Every citation, both ways

Citations
Document	Relation	Office	Cited during
US8488764B1	Cited by	United States of America	Applicant
US2012128140A1	Cited by	United States of America	Pre-grant
US9277021B2	Cited by	United States of America	Applicant
US8718246B2	Cited by	United States of America	Search report
US9769319B1	Cited by	United States of America	Applicant
US2011044440A1	Cited by	United States of America	Pre-grant
US8594315B1	Cited by	United States of America	Applicant
US2007180029A1	Cited by	United States of America	Pre-grant
US2002169832A1	Cites	United States of America	Pre-grant
US2002173319A1	Cites	United States of America	Pre-grant
US2002176404A1	Cites	United States of America	Pre-grant
US2003119495A1	Cites	United States of America	Pre-grant
US2003208536A9	Cites	United States of America	Pre-grant
US2004218744A1	Cites	United States of America	Pre-grant
US5375068A	Cites	United States of America	Pre-grant
US5495483A	Cites	United States of America	Pre-grant
US5521906A	Cites	United States of America	Pre-grant
US5563882A	Cites	United States of America	Pre-grant
US5594859A	Cites	United States of America	Pre-grant
US5608653A	Cites	United States of America	Pre-grant
US5608725A	Cites	United States of America	Pre-grant
US5844979A	Cites	United States of America	Pre-grant
US5916302A	Cites	United States of America	Pre-grant
US5996003A	Cites	United States of America	Pre-grant
US6020915A	Cites	United States of America	Pre-grant
US6061440A	Cites	United States of America	Pre-grant
US6105054A	Cites	United States of America	Pre-grant
US6275575B1	Cites	United States of America	Pre-grant
US6373817B1	Cites	United States of America	Pre-grant
US6373936B1	Cites	United States of America	Pre-grant
US6411988B1	Cites	United States of America	Pre-grant
US6424711B1	Cites	United States of America	Pre-grant
US6473858B1	Cites	United States of America	Pre-grant
US6519571B1	Cites	United States of America	Pre-grant
US6520646B2	Cites	United States of America	Pre-grant
US6574674B1	Cites	United States of America	Pre-grant
US6583806B2	Cites	United States of America	Pre-grant
US6584493B1	Cites	United States of America	Pre-grant
US6615166B1	Cites	United States of America	Pre-grant
US6615239B1	Cites	United States of America	Pre-grant
US6628767B1	Cites	United States of America	Pre-grant
US6697858B1	Cites	United States of America	Pre-grant
US6704769B1	Cites	United States of America	Pre-grant
US6717607B1	Cites	United States of America	Pre-grant
US6721410B1	Cites	United States of America	Pre-grant
US6754323B1	Cites	United States of America	Pre-grant
US6760750B1	Cites	United States of America	Pre-grant
US6772436B1	Cites	United States of America	Pre-grant
US6785709B1	Cites	United States of America	Pre-grant
US6795106B1	Cites	United States of America	Pre-grant
US6819752B2	Cites	United States of America	Pre-grant
US6850266B1	Cites	United States of America	Pre-grant
US6850985B1	Cites	United States of America	Pre-grant
US6851053B1	Cites	United States of America	Pre-grant
US6888803B1	Cites	United States of America	Pre-grant
US7072336B2	Cites	United States of America	Pre-grant
US7085260B2	Cites	United States of America	Pre-grant
US7260641B2	Cites	United States of America	Pre-grant
US7283519B2	Cites	United States of America	Pre-grant

2 members in 1 office; this record represents the family

This recordMember, by publication datePriority claim

Priority claims2

Priority claims
Document	Office	Kind	Date
12228202	United States of America	A	2002-04-12
US20020122282	–	–	–

Members2

Family members, oldest first
Document	Office	Kind
US2003195930A1	United States of America	A1	2003-10-16
US8392502B2	United States of America	B2	2013-03-05

175 transactions on the USPTO file

Allowed after 7 non-final rejections, 7 final rejections, 8 RCEs and 2 appeals.

Non-final rejections: 7
Final rejections: 7
RCEs: 8
Appeals: 2

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2021-04-12	Expire PatentEXP.	EXP.
2020-10-26	Maintenance Fee Reminder MailedREM.	REM.
2017-05-25	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2017-05-24	Correspondence Address ChangeC.AD	C.AD
2015-08-27	Email NotificationEML_NTR	EML_NTR
2015-08-27	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2015-08-26	Correspondence Address ChangeC.AD	C.AD
2013-03-05	Recordation of Patent Grant MailedPGM/	PGM/
2013-03-05	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2013-02-13	Issue Notification MailedAllowedWPIR	WPIR
2013-02-06	Printer Rush- No mailing	–
2013-02-06	Printer Rush- No mailing	–
2013-02-04	Pubs Case Remand to TCPUBTC	PUBTC
2013-01-28	Dispatch to FDCD1935	D1935
2013-01-28	Application Is Considered Ready for IssuePILS	PILS
2013-01-22	Issue Fee Payment VerifiedN084	N084
2013-01-22	Issue Fee Payment ReceivedIFEE	IFEE
2012-10-22	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2012-10-03	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2012-10-03	Case Docketed to Examiner in GAUDOCK	DOCK
2012-10-01	Reasons for Allowance	–
2012-10-01	Examiner's Amendment Communication	–
2012-03-07	Mail Miscellaneous Communication to ApplicantMM327	MM327
2012-03-07	Miscellaneous Communication to Applicant - No Action CountM327	M327
2012-03-05	Miscellaneous Incoming LetterLET.	LET.
2011-12-11	Date Forwarded to ExaminerFWDX	FWDX
2011-12-11	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2011-12-08	Request for Continued Examination (RCE)RCEX	RCEX
2011-12-08	Workflow - Request for RCE - BeginBRCE	BRCE
2011-09-13	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2011-08-29	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2011-08-28	Reasons for Allowance	–
2011-08-28	Examiner's Amendment Communication	–
2011-07-20	Date Forwarded to ExaminerFWDX	FWDX
2011-07-20	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2011-07-13	Request for Continued Examination (RCE)RCEX	RCEX
2011-07-13	Workflow - Request for RCE - BeginBRCE	BRCE
2011-07-01	Mail Advisory Action (PTOL - 303)MCTAV	MCTAV
2011-06-29	Advisory Action (PTOL-303)CTAV	CTAV
2011-06-29	Date Forwarded to ExaminerFWDX	FWDX
2011-06-13	Response after Final ActionA.NE	A.NE
2011-04-13	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2011-04-11	Final RejectionFinal rejectionCTFR	CTFR
2011-01-29	Date Forwarded to ExaminerFWDX	FWDX
2011-01-24	Response after Non-Final ActionA...	A...
2010-10-22	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2010-10-21	Non-Final RejectionNon-final rejectionCTNF	CTNF
2010-09-04	Date Forwarded to ExaminerFWDX	FWDX
2010-09-04	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2010-08-25	Request for Continued Examination (RCE)RCEX	RCEX
2010-08-25	Workflow - Request for RCE - BeginBRCE	BRCE
2010-08-04	Mail Advisory Action (PTOL - 303)MCTAV	MCTAV
2010-08-03	Advisory Action (PTOL-303)CTAV	CTAV
2010-08-01	Date Forwarded to ExaminerFWDX	FWDX
2010-07-26	Response after Final ActionA.NE	A.NE
2010-05-25	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2010-05-24	Final RejectionFinal rejectionCTFR	CTFR
2010-05-18	Date Forwarded to ExaminerFWDX	FWDX
2010-01-08	Mail Notice of Rescinded AbandonmentAbandonedMNRAB	MNRAB
2010-01-08	Notice of Rescinded Abandonment in TCsAbandonedNRAB	NRAB
2010-01-08	Mail-Petition to Revive Application - GrantedMPREV	MPREV
2010-01-08	Petition to Revive Application - GrantedPREV	PREV
2009-10-01	Response after Non-Final ActionA...	A...
2009-10-01	Petition EnteredPET.	PET.
2009-09-28	Mail-Petition Decision - DismissedMPTDI	MPTDI
2009-09-28	Petition Decision - DismissedPTDI	PTDI
2009-08-05	Petition EnteredPET.	PET.
2009-06-23	Mail Abandonment for Failure to Respond to Office ActionAbandonedMABN2	MABN2
2009-06-22	Aband. for Failure to Respond to O. A.AbandonedABN2	ABN2
2008-10-20	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2008-10-14	Non-Final RejectionNon-final rejectionCTNF	CTNF
2008-10-06	Case Docketed to Examiner in GAUDOCK	DOCK
2008-09-11	Date Forwarded to Examiner	–
2008-09-11	Date Forwarded to Examiner	–
2008-09-11	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2008-09-08	Request for Continued Examination (RCE)RCEX	RCEX
2008-09-08	Workflow - Request for RCE - BeginBRCE	BRCE
2008-08-21	Mail Advisory Action (PTOL - 303)MCTAV	MCTAV
2008-08-20	Advisory Action (PTOL-303)CTAV	CTAV
2008-08-16	Date Forwarded to ExaminerFWDX	FWDX
2008-08-07	Response after Final ActionA.NE	A.NE
2008-06-09	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2008-06-05	Final RejectionFinal rejectionCTFR	CTFR
2008-05-05	Date Forwarded to ExaminerFWDX	FWDX
2008-03-03	Response after Non-Final ActionA...	A...
2008-01-28	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2008-01-26	Non-Final RejectionNon-final rejectionCTNF	CTNF
2008-01-09	Date Forwarded to Examiner	–
2008-01-09	Date Forwarded to Examiner	–
2008-01-09	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2007-12-06	Request for Continued Examination (RCE)RCEX	RCEX
2007-12-06	Workflow - Request for RCE - BeginBRCE	BRCE
2007-11-19	Mail Appeals conf. Proceed to PTABMAPCP	MAPCP
2007-11-16	Pre-Appeal Conference Decision - Proceed to PTABAPCP	APCP
2007-10-24	Request for Pre-Appeal Conference FiledAP.C	AP.C
2007-10-24	Notice of Appeal FiledN/AP	N/AP
2007-10-16	Mail Advisory Action (PTOL - 303)MCTAV	MCTAV
2007-10-15	Advisory Action (PTOL-303)CTAV	CTAV
2007-10-12	Date Forwarded to ExaminerFWDX	FWDX
2007-10-09	Response after Final ActionA.NE	A.NE

Showing 100 of 175

19 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2021-05-04	Lapsed due to failure to pay maintenance feeLapsedFP	FP
2021-04-12	Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS	LAPS
2021-04-12	Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH	STCH
2020-10-26	Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2020-04-29	AssignmentAS	AS
2016-08-29	Fee paymentFPAY	FPAY
2014-09-30	AssignmentAS	AS
2014-07-25	AssignmentAS	AS
2013-11-02	Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2013-11-02	Fee payment procedurePAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2013-02-13	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2013-01-30	AssignmentAS	AS
2013-01-30	AssignmentAS	AS
2012-12-02	Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2012-12-02	Fee payment procedurePAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2011-11-22	AssignmentAS	AS
2011-11-16	AssignmentAS	AS
2002-07-05	AssignmentAS	AS
2002-07-05	AssignmentAS	AS