Source: http://www.google.com/patents/US7194073?dq=6,891,551
Timestamp: 2017-04-29 03:12:58
Document Index: 642192131

Matched Legal Cases: ['art 200', 'art 300', 'arts 200', 'art 200', 'art 300', 'art 300', 'art 400', 'art 500', 'art 400', 'art 500', 'art 500', 'arts 200']

Patent US7194073 - Method for automatically replenishing pre-paid calling units within a ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsIn a system including a telematics unit and a data center, a method for automatically replenishing pre-paid calling units within the telematics is based on an occurrence of a trigger event as detected by the telematics units. Upon being notified of the trigger event, the data center automatically uploads...http://www.google.com/patents/US7194073?utm_source=gb-gplus-sharePatent US7194073 - Method for automatically replenishing pre-paid calling units within a telematic unitAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS7194073 B2Publication typeGrantApplication numberUS 10/706,658Publication dateMar 20, 2007Filing dateNov 12, 2003Priority dateNov 12, 2003Fee statusPaidAlso published asUS20050100148Publication number10706658, 706658, US 7194073 B2, US 7194073B2, US-B2-7194073, US7194073 B2, US7194073B2InventorsGary A. Watkins, Christopher L. OesterlingOriginal AssigneeGeneral Motors CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (8), Referenced by (8), Classifications (17), Legal Events (12) External Links: USPTO, USPTO Assignment, EspacenetMethod for automatically replenishing pre-paid calling units within a telematic unit
US 7194073 B2Abstract
1. In a system including a telematics unit and a data center, a method for automatically replenishing calling units within the telematics unit, the method comprising:
operating the telematics unit to automatically detect an occurrence of a trigger event to the data center; and
operating the data center to communicate a replenishment package to the telematics unit subsequent to the detection of the trigger event, wherein the replenishment package includes a first set of calling units.
2. The method of claim 1, wherein the operation of the telematics unit to automatically report the occurrence of a trigger event to the data center includes:
operating the telematics unit to monitor a calendar to thereby facilitate a detection of an end of a current billing cycle; and
operating the telematic unit to communicate the occurrence of the trigger event to the data center upon the detection of the end of the current billing cycle.
operating the data center to identify the replenishment package based on an association of the telematics unit and a customer account in response to the communication of the occurrence of the trigger event by the telematics unit.
operating the data center to communicate a trigger event reset to the telematics unit subsequent to the telematics unit replenishing itself with the first set of calling units; and
operating the telematics unit to reset the trigger event to the end of the next billing cycle in response to a reception of the trigger event reset.
5. The method of claim 1, wherein an operation of the telematics unit to automatically detect and communicate an occurrence of a trigger event to the data center includes:
operating the telematics unit to monitor a consumption of a second set of calling units by the telematics unit to thereby facilitate a detection of a depletion of the second set of calling units; and
operating the telematics unit to communicate the occurrence of the trigger event to the data center upon the detection of the depletion of the second set of calling units.
operating the data center to identify and deliver at least one replenishment package to the telematics unit in response to the communication of the detected depletion of the second set of calling units;
operating the telematics unit to select the replenishment package from the offered at least one replenishment package, wherein the data center automatically communicates the replenishment package in response to the selection of the replenishment package by the telematics unit.
wherein the data center identifies the at least one replenishment package as a function of a consumption rate of calling units by the telematics unit.
operating the telematics unit to automatically replenish itself with the first set of calling units in response to a reception of the replenishment package.
a telematics unit operable to automatically detect an occurrence of a trigger event to said data center; and
a data center operable to communicate a replenishment package to said telematics unit subsequent to the occurrence of the trigger event,
wherein the replenishment package includes a first set of calling units, and
wherein said telematics unit is further operable to automatically replenish itself with the first set of calling units in response to a reception of the replenishment package.
10. The system of claim 9, wherein said telematics units includes:
means for monitoring a calendar to thereby facilitate a detection of an end of a current billing cycle; and
means for communicating the occurrence of the trigger event to said data center upon the detection of the end of the current billing cycle.
11. The system of claim 10, wherein said data center includes
means for identifying the replenishment package based on an association of said telematics unit and a customer account.
wherein said data center is further operable to communicate a trigger event reset to said telematics unit subsequent to said telematics unit replenishing itself with the first set of calling units; and
wherein said telematics unit is further operable to reset the trigger event to the end of the next billing cycle in response to a reception of the trigger event reset.
13. The system of claim 9, wherein said telematics unit includes:
means for monitoring a consumption of a second set of calling units by said telematics unit to thereby facilitate a detection of a depletion of the second set of calling units; and
means for communicating the occurrence of the trigger event to said data center upon the detection of the depletion of the second set of calling units.
wherein said data center is further operable to identify and offer at least one replenishment package to said telematics unit in response to the communication of the detected depletion of the second set of calling units;
wherein said telematics unit is further operable to select the replenishment package from the offered at least one replenishment package; and
wherein said data center automatically communicates the replenishment package in response to the selection of the replenishment package by said telematics unit.
15. The system of claim 11, wherein said data center identifies the at least one replenishment package as a function of a consumption rate of calling units by said telematics unit.
16. A telematics unit, comprising:
means for automatically detecting and communicating an occurrence of a trigger event to a data center; and
means for automatically replenishing itself with a first set of calling units in response to a reception of a replenishment package from the data center,
wherein the reception of the replenishment package from the data center corresponds to the communicated occurrence of the trigger event.
17. The telematics unit of claim 16,
wherein the occurence of the trigger event is an end of a billing cycle.
18. The telematics unit of claim 16,
wherein the occurrence of the trigger event is a depletion of a second set of calling units by said telematics unit during a current billing cycle.
19. The telematics unit of claim 16,
wherein the replenishment package is associated with a customer account corresponding to said telematics unit.
20. The telematics unit of claim 16,
wherein the replenishment package is based on a consumption rate of calling units by said telematics unit.
21. The telematics unit of claim 16,
wherein said telematics unit selected the replenishment package from among at least one replenishment package offered by the data center.
In general, the invention relates to mobile application services in telematics units. More specifically, the invention relates to a method for automatically replenishing calling units within a mobile communication unit.
A mobile application service provider provides information and services to the vehicles of subscribers from a data center through a vehicle installed wireless telecommunication apparatus. Examples of types of services provided are emergency response assistance, roadside service assistance, location-based services such as turn-by-turn directions, prepaid personal calling, phone number directory lookup assistance, and points of interest lookup. These services may be offered on pre-paid or non-prepaid arrangements.
One way of offering prepaid personal calling is by offering packages of pre-paid usage. Usage for example, can be measured in units, in terms of the number of minutes of operator assistance or amount of data transfer. When the pre-paid units are completely consumed, they must be replenished for the service to continue. This will require the subscriber to contact the service provider to purchase more units of service. Although service replenishment may be performed using the vehicle installed wireless telecommunication apparatus to connect to the data center, it requires the subscriber to interact with an automated voice system or a service representative to purchase the desired pre-paid service package.
Thus, there is a significant need for a method and system for automatically replenishing mobile application services in a vehicle so that the subscriber services remain uninterrupted.
One embodiment of the invention provides a method including the steps of operating the telematics unit to automatically report an occurrence of a trigger event to the data center and operating the data center to communicate a replenishment package to the telematics unit subsequent to the occurrence of the trigger event, wherein the replenishment package includes a first set of calling units. The method further includes operating the telematics unit to automatically replenish itself with the first set of calling units in response to a reception of the replenishment package.
Another aspect of the invention provides a system including a telematics unit operable to automatically report an occurrence of a trigger event to said data center; and a data center operable to communicate a replenishment package to said telematics unit subsequent to the occurrence of the trigger event, wherein the replenishment package includes a first set of calling units, wherein said telematics unit is further operable to automatically replenish itself with the first set of calling units in response to a reception of the replenishment package.
Yet another aspect of the invention describes a telematics unit including means for automatically reporting and communicating an occurrence of a trigger event to a data center; and means for automatically replenishing itself with a first set of calling units in response to a reception of a replenishment package from the data center, wherein the reception of the replenishment package from the data center corresponds to the communicated occurrence of the trigger event.
FIG. 1 illustrates one embodiment of a system for communicating from a telematics unit to a data center in accordance with the present invention;
FIG. 2 illustrates a flowchart representative of one embodiment in accordance with the present invention of a method for automatically replenishing pre-paid calling units within a telematics unit at the end of a billing cycle; and
FIG. 3 illustrates a flowchart representative of one embodiment in accordance with the present invention of a method for automatically replenishing pre-paid calling units within a telematics unit upon a complete consumption of the calling units.
In one embodiment, telematics unit 120 is a vehicle communications unit that includes a digital signal processor (DSP) 122 connected to a wireless modem 124, a global positioning system (GPS) unit 126, an in-vehicle memory 128, such as, for example, a non-volatile flash memory, a microphone 130, one or more speakers 132, an embedded or in-vehicle mobile phone 134, and a wireless access point node 136. DSP 122 is also referred to as a micro-controller, controller, ASIC, host processor, or vehicle communications processor. GPS unit 126 provides longitude and latitude coordinates of the vehicle, as well as a time stamp. In-vehicle mobile telephone system 134 is a cellular-type phone, such as, for example an analog, digital, dual-mode, dual-band, multi-mode or multi-band cellular phone. In another example, the mobile telephone system is an analog mobile telephone system operating over a prescribed band nominally at 800 MHz. In another example, the mobile telephone system is a digital mobile telephone system operating over a prescribed band nominally at 800 MHz, 900 MHz, 1900 MHz, or any suitable band capable of carrying digital cellular communications.
In one example, modem 124 includes a Prepaid Personal Calling (“PPC”) loading module 115 capable of communication with at least one call center 170. In one embodiment of the invention, PPC loading module 115 is an embedded component of the modem 124 capable of providing a wireless communication link between the telematics unit 120 and call center 170. In another embodiment, the PPC loading module 115 is external to the modem 124, and in communication with the telematics unit 120. PPC loading module 115 is configured to perform at least the methods disclosed herein. In one embodiment, PPC loading module 115 is pre-programmed with an initial, predetermined number of PPC units. In a second embodiment, PPC loading module 115 secures an initial number of PPC units from call center 170. A replenishment package is a package of PPC units. In one embodiment, a replenishment package is a predetermined number of units. For example, a replenishment package may increase the number of PPC units by 150 units. In another embodiment, replenishment package increases an existing number of units to a predetermined number of units. In another example, a replenishment package may increase the number of PPC units to 150 units.
DSP 122 executes various computer programs and communication control and protocol algorithms that control communication, programming and operational modes of electronic and mechanical systems within vehicle 110. In one embodiment, DSP 122 is an embedded system controller. In another embodiment, DSP 122 controls communications between telematics unit 120, wireless carrier system 140, and call center 170. In another embodiment, DSP 122 controls communications between the wireless access point node 134 and nodes of a mobile ad hoc network. In one embodiment, a speech-recognition application is installed in DSP 122 to translate human voice input through microphone 130 into digital signals. DSP 122 generates and accepts digital signals transmitted between telematics unit 120 and a vehicle communication bus 112 that is connected to various electronic modules in the vehicle 110. In one embodiment, the digital signals activate a programming mode and operation modes, as well as provide for data transfers. In another embodiment, a vehicle data upload (VDU) utility program facilitates the transfer of instructions and data requests to vehicle 110.
Vehicle 110, via a vehicle communication bus 112, sends signals to various units of equipment and systems within the vehicle 110 to perform various functions such as monitoring the operational state of vehicle systems, collecting and storing data from the vehicle systems, providing instructions, data and programs to various vehicle systems and calling from telematics unit 120. In facilitating interactions among the various communication and electronic modules, vehicle communication bus 112 utilizes bus interfaces such as controller-area network (CAN), J1850, International Organization for Standardization (ISO) Standard 9141, ISO Standard 11898 for high-speed applications, and ISO Standard 11519 for lower speed applications.
Vehicle 110, via telematics unit 120, sends and receives radio transmissions from wireless carrier system 140. Wireless carrier system 140 is implemented as any suitable system for transmitting a signal from mobile vehicle 110 to communication network 142. Wireless carrier system 140 incorporates any type of telecommunications in which electromagnetic waves carry signal over part of or the entire communication path. In one embodiment, wireless carrier system 140 transmits analog audio, digital audio (including, but not limited to, CDMA, TDMA, FDMA, GSM) and/or video signals. In an example, wireless carrier system 140 transmits analog audio and/or video signals such as those sent from AM and FM radio stations and transmitters, or digital audio signals in the S band (approved for use in the U.S.) and L band (used in Europe and Canada). In one embodiment, wireless carrier system 140 is a satellite broadcast system broadcasting over a spectrum in the “S” band (2.3 GHz) that has been allocated by the U.S. Federal Communications Commission (FCC) for nationwide broadcasting of satellite-based Digital Audio Radio Service (DARS).
Switch 172 of call center 170 connects to land network 144. Switch 172 transmits voice or data transmissions from call center 170, and receives voice or data transmissions from telematics unit 120 in mobile vehicle 110 through wireless carrier system 140 and/or wireless access point node 136, communication network 142, and land network 144. Switch 172 receives data transmissions from, and sends data transmissions to, one or more web-hosting portals 160. Switch 172 receives data transmissions from, or sends data transmissions to, one or more communication services managers 174 via one or more networks 180.
Communication services manager 174 is any suitable hardware and software capable of providing communication services to telematics unit 120 in mobile vehicle 110. Communication services manager 174 sends to or receives data transmissions from one or more communication services databases 176 via networks 180. Communication services manager 174 sends to or receives data transmissions from one or more communication services advisors 178 via networks 180. Communication services database 176 sends to or receives data transmissions from communication services advisor 178 via networks 180. Communication services advisor 178 receives from or sends to switch 172 voice or data transmissions.
Vehicle 110 initiates service requests to call center 170 by sending a voice or digital-signal command to telematics unit 120 which in turn, sends an instructional signal or a voice call through wireless modem 124, wireless carrier system 140, communication network 142, and land network 144 to call center 170. In another embodiment, the service request is for a vehicle data upload (VDU) that initiates a data transfer between vehicle 110 and service center 170 or web hosting portal 160. In another embodiment, the mobile vehicle 110 receives a request from call center 170 to send various vehicle data from mobile vehicle 110 through telematics unit 120 through wireless modem 124, wireless access point node 136, wireless carrier system 140, communication network 142, and land network 144 to call center 170.
FIG. 2 illustrates a flowchart 200 and a flowchart 300 that are executed by PPC loading module 115 and data center 170, respectively, in implementing an automated monthly PPC unit replenishment method of the present invention. While in practice telematics unit 120 can have any PPC billing cycle, flowcharts 200 and 300 will be described herein as if telematics unit 120 has a PPC billing cycle that occurs the 1st of every month.
In operation, during a stage S202 of flowchart 200, PPC loading module 115 monitors a calendar to thereby detect an occurrence of an end of a PPC billing cycle for telematics unit 120. PPC loading module 115 proceeds from stage S202 to a stage S204 upon detecting an end of the current billing cycle for telematics unit 120 (e.g., January 1st). During stage S204, telematics unit 120 conventionally connects with data center 170 to communicate the end of the PPC billing cycle as a PPC trigger event to data center 170. A PPC trigger event indicates one of various events (e.g., end-of-billing-cycle and interim unit replenishing). Thus, in response thereto, data center 170 determines during a stage S302 of flowchart 300 if the PPC trigger event indicates an event of a billing cycle for telematics unit 120, and if so, call center 170 automatically proceeds to a stage S304 to identify and communicate an appropriate PPC unit package to PPC loading module 115. In one embodiment of stage S304, call center 170 identifies the PPC unit package from a customer account associated with telematics unit 120 and automatically uploads the PPC unit package to PPC loading module 115. For example, the automatically uploaded PPC unit package may be a first replenishment package after the first detection of a trigger event, or the PPC unit package may be a second replenishment package after the second detection of a trigger event. Subsequent packages (third, fourth fifth, etc.) are also included herein. The replenishment packages (first, second, etc.) may be either a fixed number of PPC units, e.g. 150, or the replenishment packages may be a variable number of PPC units sufficient to increase the existing PPC units to a certain number, e.g. 150. Thus, for example, if a telematics unit currently has 14 PPC units, the first (second, etc.) replenishment package may add 150 PPC units (making the total 164 units in the telematics unit), or the replenishment package may increase the existing units to 150 by adding 136 PPC units.
Upon receipt of the PPC unit package by PPC loading module 115, telematics unit 120 replenishes its PPC units and PPC loading module 115 communicates the replenishment of the PPC units to call center 170 during a stage S206. During a stage S306, call center 170 acknowledges the replenishment of the PPC units by telematics unit 120 and communicates an PPC trigger reset to PPC loading module 115, which resets the PPC trigger to the end of the next billing cycle (e.g., February 1st) during a stage S208. PPC loading module 115 thereafter returns to stage S202 to monitor the calendar, while call center 170 terminates flowchart 300 until call center 170 receives another PPC trigger event from PPC loading module 115.
FIG. 3 illustrates a flowchart 400 and a flowchart 500 that are executed by PPC loading module 115 and call center 170, respectively, in implementing an automated interim PPC unit replenishment method of the present invention. The purpose of this method is to replenish the PPC units of telematics unit 120, if necessary, during a PPC billing cycle.
In operation, during a stage S402 of flowchart 400, PPC loading module 115 monitors a consumption of PPC units by telematics unit 120 to thereby detect an occurrence of a depletion of the PPC units of telematics unit 120. PPC loading module 115 proceeds from stage S402 to a stage S404 upon a detection of a depletion of the PPC units. During stage S404, PPC loading module 115 conventionally connects to data center 115 to report and communicate the depletion of the PPC units as a PPC trigger event to call center 170. In response thereto, call center 170 determines during a stage S502 of flowchart 500 if the PPC trigger event indicates a depletion of the PPC units for telematics unit 120, and if so, automatically proceeds to a stage S504 to identify and deliver one or more PPC unit packages to telematics unit 120. In selecting which PPC unit package(s) to offer, call center 170 considers (1) the size of the depleted PPC unit package, (2) the date the depleted PPC unit package was first utilized by telematics unit 120, and (3) the current date. In one embodiment, call center 170 calculates a baseline PPC unit package as a function of a product of (1) an average of the minutes per day used by telematics unit 120 during a consumption of the depleted PPC unit package, and (2) the number of days remaining before the end of the current billing cycle. In selecting the PPC unit packages to offer to telematics unit 120, call center 170 uses (1) the baseline number of PPC units, and/or (2) rounds up the baseline number of PPC units by “x” units (e.g., 10 or 25).
Upon receipt of the offered PPC unit package(s) during a stage S406, a user of PPC loading module 115 can either (1) select an offered PPC unit package or (2) request a different PPC unit package that has more or less PPC units than the current offered PPC unit package(s). PPC loading module 115 eventually communicates a final selection of an offered PPC unit package to call center 170, which communicates the selected PPC unit package to PPC loading module 115 during a stage S506. In one embodiment of stage S304, call center 170 automatically uploads the selected PPC unit package to PPC loading module 115.
Upon receipt of the selected PPC unit package, telematics unit 120 replenishes its PPC units and PPC loading module 115 communicates the replenishment of the PPC units to call center 170 during a stage S408. PPC loading module 115 thereafter returns to stage S402 to monitor a consumption of the PPC units by telematics unit 120, while call center 170 terminates flowchart 500 until such time call center 170 receives another PPC trigger event from PPC loading module 115.
From the preceding descriptions herein of flowcharts 200–300 as illustrated in FIGS. 2 and 3, those having ordinary skill in the art will appreciate various advantages of the present invention, such as, for example, an elimination of a need for a customer to have to call a data center or the like to purchase more PPC units at the end of a billing cycle or upon a depletion of PPC units during a billing cycle. Furthermore, those having ordinary skill in the art will appreciate that, in practice, the automated monthly PPC replenishment method and the automated interim PPC replenishment method of the present invention can be individually executed as described and illustrated herein, or merged into single PPC replenishment method.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5749052 *May 24, 1995May 5, 1998Tele Digital Development, Inc.Cellular telephone management systemUS6430406 *Feb 17, 2000Aug 6, 2002Nokia Mobile Phones Ltd.Credit information in a mobile phoneUS6526273 *Dec 22, 1999Feb 25, 2003Bellsouth Intellectual Property CorporationSystem and method for automated pre-paid wireless replenishment with notificationUS6735290 *Sep 28, 2001May 11, 2004Bellsouth Intellectual Property CorporationMethod and system for pre-setting long distance call chargesUS6934529 *Feb 20, 2001Aug 23, 2005Sevket Ilhan BagorenReplenishment of pre-paid wireless telephone accounts using short message service (SMS)US20030027549 *Jul 30, 2001Feb 6, 2003Msafe Inc.Prepaid communication system and methodUS20030157925 *Feb 21, 2002Aug 21, 2003Sorber Russell E.Communication unit and method for facilitating prepaid communication servicesUS20050061872 *May 17, 2004Mar 24, 2005Miles PaschiniSystem and method for electronic prepaid account replenishment* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7382873 *Jun 27, 2003Jun 3, 2008General Motors CorporationMethod and system for automatic calling unit replenishmentUS7796972May 30, 2008Sep 14, 2010General Motors LlcMethod and system for automatic calling unit replenishmentUS7996235 *Aug 10, 2005Aug 9, 2011General Motors LlcTelematics marketing information acquisition triggering method and systemUS8131255Jul 29, 2009Mar 6, 2012General Motors LlcSystem for facilitating use of a single telecommunication device by multiple usersUS20040266392 *Jun 27, 2003Dec 30, 2004General Motors CorporationMethod and system for automatic calling unit replenishmentUS20070038510 *Aug 10, 2005Feb 15, 2007General Motors CorporationTelematics marketing information acquistion triggering method and systemUS20080287097 *May 30, 2008Nov 20, 2008General Motors CorporationMethod and system for automatic calling unit replenishmentUS20110028123 *Jul 29, 2009Feb 3, 2011General Motors CompanySystem for facilitating use of a single telecommunication device by multiple users* Cited by examinerClassifications U.S. Classification379/114.2, 455/407, 379/114.16International ClassificationH04M15/00, H04M17/02Cooperative ClassificationH04M15/00, H04M2017/22, H04M17/20, H04M17/201, H04M2017/225, H04M2017/222, H04M2215/32, H04M17/02European ClassificationH04M17/20A, H04M17/20, H04M15/00, H04M17/02Legal EventsDateCodeEventDescriptionNov 12, 2003ASAssignmentOwner name: GENERAL MOTORS CORPORATION, MICHIGANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WATKINS, GARY A.;OESTERLING, CHRISTOPHER L.;REEL/FRAME:014701/0598Effective date: 20031110Feb 3, 2009ASAssignmentOwner name: UNITED STATES DEPARTMENT OF THE TREASURY, DISTRICTFree format text: SECURITY AGREEMENT;ASSIGNOR:GENERAL MOTORS CORPORATION;REEL/FRAME:022191/0254Effective date: 20081231Owner name: UNITED STATES DEPARTMENT OF THE TREASURY,DISTRICTFree format text: SECURITY AGREEMENT;ASSIGNOR:GENERAL MOTORS CORPORATION;REEL/FRAME:022191/0254Effective date: 20081231Apr 16, 2009ASAssignmentOwner name: CITICORP USA, INC. AS AGENT FOR BANK PRIORITY SECUFree format text: SECURITY AGREEMENT;ASSIGNOR:GENERAL MOTORS CORPORATION;REEL/FRAME:022552/0006Effective date: 20090409Owner name: CITICORP USA, INC. AS AGENT FOR HEDGE PRIORITY SECFree format text: SECURITY AGREEMENT;ASSIGNOR:GENERAL MOTORS CORPORATION;REEL/FRAME:022552/0006Effective date: 20090409Aug 20, 2009ASAssignmentOwner name: MOTORS LIQUIDATION COMPANY (F/K/A GENERAL MOTORS CFree format text: RELEASE BY SECURED PARTY;ASSIGNOR:UNITED STATES DEPARTMENT OF THE TREASURY;REEL/FRAME:023119/0491Effective date: 20090709Aug 21, 2009ASAssignmentOwner name: MOTORS LIQUIDATION COMPANY (F/K/A GENERAL MOTORS CFree format text: RELEASE BY SECURED PARTY;ASSIGNORS:CITICORP USA, INC. AS AGENT FOR BANK PRIORITY SECURED PARTIES;CITICORP USA, INC. AS AGENT FOR HEDGE PRIORITY SECURED PARTIES;REEL/FRAME:023119/0817Effective date: 20090709Owner name: MOTORS LIQUIDATION COMPANY, MICHIGANFree format text: CHANGE OF NAME;ASSIGNOR:GENERAL MOTORS CORPORATION;REEL/FRAME:023129/0236Effective date: 20090709Owner name: MOTORS LIQUIDATION COMPANY,MICHIGANFree format text: CHANGE OF NAME;ASSIGNOR:GENERAL MOTORS CORPORATION;REEL/FRAME:023129/0236Effective date: 20090709Aug 27, 2009ASAssignmentOwner name: GENERAL MOTORS COMPANY, MICHIGANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOTORS LIQUIDATION COMPANY;REEL/FRAME:023148/0248Effective date: 20090710Owner name: UNITED STATES DEPARTMENT OF THE TREASURY, DISTRICTFree format text: SECURITY AGREEMENT;ASSIGNOR:GENERAL MOTORS COMPANY;REEL/FRAME:023155/0814Effective date: 20090710Owner name: UAW RETIREE MEDICAL BENEFITS TRUST, MICHIGANFree format text: SECURITY AGREEMENT;ASSIGNOR:GENERAL MOTORS COMPANY;REEL/FRAME:023155/0849Effective date: 20090710Owner name: GENERAL MOTORS COMPANY,MICHIGANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOTORS LIQUIDATION COMPANY;REEL/FRAME:023148/0248Effective date: 20090710Owner name: UNITED STATES DEPARTMENT OF THE TREASURY,DISTRICTFree format text: SECURITY AGREEMENT;ASSIGNOR:GENERAL MOTORS COMPANY;REEL/FRAME:023155/0814Effective date: 20090710Owner name: UAW RETIREE MEDICAL BENEFITS TRUST,MICHIGANFree format text: SECURITY AGREEMENT;ASSIGNOR:GENERAL MOTORS COMPANY;REEL/FRAME:023155/0849Effective date: 20090710Nov 12, 2009ASAssignmentOwner name: GENERAL MOTORS LLC, MICHIGANFree format text: CHANGE OF NAME;ASSIGNOR:GENERAL MOTORS COMPANY;REEL/FRAME:023504/0691Effective date: 20091016Owner name: GENERAL MOTORS LLC,MICHIGANFree format text: CHANGE OF NAME;ASSIGNOR:GENERAL MOTORS COMPANY;REEL/FRAME:023504/0691Effective date: 20091016Aug 18, 2010FPAYFee paymentYear of fee payment: 4Nov 4, 2010ASAssignmentOwner name: GM GLOBAL TECHNOLOGY OPERATIONS, INC., MICHIGANFree format text: RELEASE BY SECURED PARTY;ASSIGNOR:UNITED STATES DEPARTMENT OF THE TREASURY;REEL/FRAME:025245/0347Effective date: 20100420Owner name: GM GLOBAL TECHNOLOGY OPERATIONS, INC., MICHIGANFree format text: RELEASE BY SECURED PARTY;ASSIGNOR:UAW RETIREE MEDICAL BENEFITS TRUST;REEL/FRAME:025311/0725Effective date: 20101026Nov 8, 2010ASAssignmentOwner name: WILMINGTON TRUST COMPANY, DELAWAREFree format text: SECURITY AGREEMENT;ASSIGNOR:GENERAL MOTORS LLC;REEL/FRAME:025327/0196Effective date: 20101027Aug 20, 2014FPAYFee paymentYear of fee payment: 8Nov 7, 2014ASAssignmentOwner name: GENERAL MOTORS LLC, MICHIGANFree format text: RELEASE BY SECURED PARTY;ASSIGNOR:WILMINGTON TRUST COMPANY;REEL/FRAME:034183/0436Effective date: 20141017RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services