To: | Pinger Technologies, Inc. (cleveland.motley@pingertechnologies.com) |
Subject: | U.S. TRADEMARK APPLICATION NO. 88315171 - REAL TIME LOCATION SYSTEM AS A - N/A |
Sent: | 5/9/2019 2:28:10 PM |
Sent As: | ECOM117@USPTO.GOV |
Attachments: | Attachment - 1 Attachment - 2 Attachment - 3 Attachment - 4 Attachment - 5 Attachment - 6 Attachment - 7 Attachment - 8 Attachment - 9 Attachment - 10 Attachment - 11 Attachment - 12 Attachment - 13 Attachment - 14 Attachment - 15 Attachment - 16 Attachment - 17 Attachment - 18 Attachment - 19 Attachment - 20 Attachment - 21 Attachment - 22 Attachment - 23 Attachment - 24 Attachment - 25 Attachment - 26 Attachment - 27 Attachment - 28 Attachment - 29 Attachment - 30 Attachment - 31 Attachment - 32 Attachment - 33 Attachment - 34 Attachment - 35 Attachment - 36 Attachment - 37 Attachment - 38 Attachment - 39 Attachment - 40 Attachment - 41 Attachment - 42 Attachment - 43 |
UNITED STATES PATENT AND TRADEMARK OFFICE (USPTO)
OFFICE ACTION (OFFICIAL LETTER) ABOUT APPLICANT’S TRADEMARK APPLICATION
U.S. APPLICATION SERIAL NO. 88315171
MARK: REAL TIME LOCATION SYSTEM AS A
|
|
CORRESPONDENT ADDRESS: |
CLICK HERE TO RESPOND TO THIS LETTER: http://www.gov.uspto.report/trademarks/teas/response_forms.jsp
|
APPLICANT: Pinger Technologies, Inc.
|
|
CORRESPONDENT’S REFERENCE/DOCKET NO: CORRESPONDENT E-MAIL ADDRESS: |
|
OFFICE ACTION
TO AVOID ABANDONMENT OF APPLICANT’S TRADEMARK APPLICATION, THE USPTO MUST RECEIVE APPLICANT’S COMPLETE RESPONSE TO THIS LETTER WITHIN 6 MONTHS OF THE ISSUE/MAILING DATE BELOW. A RESPONSE TRANSMITTED THROUGH THE TRADEMARK ELECTRONIC APPLICATION SYSTEM (TEAS) MUST BE RECEIVED BEFORE MIDNIGHT EASTERN TIME OF THE LAST DAY OF THE RESPONSE PERIOD.
ISSUE/MAILING DATE: 5/9/2019
The referenced application has been reviewed by the assigned trademark examining attorney.
SEARCH OF OFFICE’S DATABASE OF MARKS
The trademark examining attorney has searched the Office’s database of registered and pending marks and has found no conflicting marks that would bar registration under Trademark Act Section 2(d). TMEP §704.02; see 15 U.S.C. §1052(d).
However, applicant should note the following issues with this application:
(1) The identification of goods requires amendment; and
(2) A disclaimer of “REAL TIME LOCATION SYSTEM AS A SERVICE” is required.
Applicant must respond timely and completely to these two issues. 15 U.S.C. §1062(b); 37 C.F.R. §§2.62(a), 2.65(a); TMEP §§711, 718.03.
IDENTIFICATION OF GOODS REQUIRES AMENDMENT
The wording “Bluetooth” and “WiFi” in the identification of goods refers to registered marks not owned by applicant. See attached U.S. Registration Nos. 2523241 and 2525795 (WI-FI), and 2909356 and 2911905 (BLUETOOTH). Moreover, “Bluetooth Low Energy” appears to be a proprietary BLUETOOTH mark. See, e.g., Wikipedia, Bluetooth Low Energy, http://en.wikipedia.org/wiki/Bluetooth_Low_Energy. Identifications of goods should generally be comprised of generic everyday wording for the goods and exclude proprietary or potentially-proprietary wording. See TMEP §§1402.01, 1402.09. A registered mark indicates origin in one particular party and so may not be used to identify goods that originate in a party other than that registrant. TMEP §1402.09 (citing Camloc Fastener Corp. v. Grant, 119 USPQ 264, 264 n.1 (TTAB 1958)). Accordingly, applicant must amend the identification to delete “Bluetooth Low Energy” and “WiFi” and replace this wording to common commercial or generic wording. TMEP §1402.09; see 37 C.F.R. §2.32(a)(6); Camloc Fastener Corp. v. Grant, 119 USPQ at 264 n.1.
Applicant may replace such wording with the following, if appropriate:
Electronic devices for locating and tracking equipment or personnel using ultra-wideband, wireless, and cellular communications systems
Applicant’s goods may be clarified or limited, but may not be expanded beyond those originally itemized in the application. See 37 C.F.R. §2.71(a); TMEP §1402.06. Applicant may clarify or limit the identification by inserting qualifying language or deleting items to result in a more specific identification; however, applicant may not substitute different goods or add goods not found or encompassed by those in the original application. See TMEP §1402.06(a)-(b). The scope of the goods sets the outer limit for any changes to the identification and is generally determined by the ordinary meaning of the wording in the identification. TMEP §§1402.06(b), 1402.07(a)-(b). Any acceptable changes to the goods will further limit scope, and once goods are deleted, they are not permitted to be reinserted. TMEP §1402.07(e).
For assistance with identifying and classifying goods in trademark applications, please see the USPTO’s online searchable U.S. Acceptable Identification of Goods and Services Manual. See TMEP §1402.04.
Applicant offers goods “for locating and tracking equipment and personnel using Ultra Wide Band, Bluetooth Low Energy, or WiFi systems.” “A real-time location system (RTLS) is one of a number of technologies that detects the current geolocation of a target, which may be anything from a vehicle to an item in a manufacturing plant to a person. … Current real-time location systems are based on wireless technologies, such as Wi-Fi, Bluetooth, ultrawideband, RFID, and GPS.” Margaret Rouse, Real-Time Location System (RTLS), TechTarget, http://searchmobilecomputing.techtarget.com/definition/real-time-location-system-RTLS. See also Wikipedia, Real-Time Locating System, http://en.wikipedia.org/wiki/Real-time_locating_system (“Real-time locating systems (RTLS) are used to automatically identify and track the location of objects or people in real time, usually within a building or other contained area.”). Thus, the wording “REAL TIME LOCATION SYSTEM” is the generic name of the goods being offered.
The addition of the wording “AS A SERVICE” to the generic wording “REAL TIME LOCATION SYSTEM” immediately and directly conveys to consumers that the locating and tracking functions of applicant’s devices are made available to users through cloud computing and remote access. See, e.g., Technopedia, Anything as a Service (XaaS), http://www.techopedia.com/definition/14027/anything-as-a-service-xaas (“Anything as a service (XaaS) is a term that describes a broad category of services related to cloud computing and remote access.”); Wikipedia, As a Service, http://en.wikipedia.org/wiki/As_a_service.
Thus, the wording “REAL TIME LOCATION SYSTEM AS A SERVICE” is unregistrable because it is, at best, merely descriptive of characteristic or feature of applicant’s goods. See 15 U.S.C. §1052(e)(1); DuoProSS Meditech Corp. v. Inviro Med. Devices, Ltd., 695 F.3d 1247, 1251, 103 USPQ2d 1753, 1755 (Fed. Cir. 2012); TMEP §§1213, 1213.03(a).
Applicant may respond to this issue by submitting a disclaimer in the following format:
No claim is made to the exclusive right to use “REAL TIME LOCATION SYSTEM AS A SERVICE” apart from the mark as shown.
TMEP §1213.08(a)(i); see In re Owatonna Tool Co., 231 USPQ 493, 494 (Comm’r Pats. 1983).
A disclaimer of unregistrable matter does not affect the appearance of the mark; that is, a disclaimer does not physically remove the disclaimed matter from the mark. See Schwarzkopf v. John H. Breck, Inc., 340 F.2d 978, 978, 144 USPQ 433, 433 (C.C.P.A. 1965); TMEP §1213.
Applicant may not claim exclusive rights to terms that others may need to use to describe their goods in the marketplace. See Dena Corp. v. Belvedere Int’l, Inc., 950 F.2d 1555, 1560, 21 USPQ2d 1047, 1051 (Fed. Cir. 1991); In re Aug. Storck KG, 218 USPQ 823, 825 (TTAB 1983). Therefore, failure to comply with a disclaimer requirement will result in a refusal to register the entire mark. See In re Stereotaxis Inc., 429 F.3d 1039, 1040-41, 77 USPQ2d 1087, 1088-89 (Fed. Cir. 2005); TMEP §1213.01(b).
For an overview of disclaimers and instructions on how to satisfy this issue using the Trademark Electronic Application System (TEAS), see the Disclaimer webpage.
RESPONSE REQUIRED
For this application to proceed, applicant must:
(1) Amend the identification of goods; and
(2) Enter a disclaimer of “REAL TIME LOCATION SYSTEM AS A SERVICE”.
Please see “Responding to Office Actions” and the informational video “Response to Office Action” for more information and tips on responding.
/Andrew Leaser/
Trademark Examining Attorney
Law Office 117
(571) 272-1911
andrew.leaser@uspto.gov
TO RESPOND TO THIS LETTER: Informal communications will not be accepted as responses to Office actions and will not be considered; therefore, do not respond to this Office action by telephone or e-mail. Instead, go to http://www.gov.uspto.report/trademarks/teas/response_forms.jsp to file a formal response using the “Response to Examining Attorney Office Action” form. Please wait 48-72 hours from the issue/mailing date before using the Trademark Electronic Application System (TEAS), to allow for necessary system updates of the application. For technical assistance with online forms, e-mail TEAS@uspto.gov.
For questions about the Office action itself, please contact the assigned trademark examining attorney. All informal communications relevant to this application will be placed in the official application record.
WHO MUST SIGN THE RESPONSE: It must be personally signed by an individual applicant or someone with legal authority to bind an applicant (i.e., a corporate officer, a general partner, all joint applicants). If an applicant is represented by an attorney, the attorney must sign the response.
PERIODICALLY CHECK THE STATUS OF THE APPLICATION: To ensure that applicant does not miss crucial deadlines or official notices, check the status of the application every three to four months using the Trademark Status and Document Retrieval (TSDR) system at http://tsdr.gov.uspto.report/. Please keep a copy of the TSDR status screen. If the status shows no change for more than six months, contact the Trademark Assistance Center by e-mail at TrademarkAssistanceCenter@uspto.gov or call 1-800-786-9199. For more information on checking status, see http://www.gov.uspto.report/trademarks/process/status/.
TO UPDATE CORRESPONDENCE/E-MAIL ADDRESS: Use the TEAS form at http://www.gov.uspto.report/trademarks/teas/correspondence.jsp.