Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 1-20 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Li et al. (US 2024/0397472).
Regarding claim 1, Li discloses a method of a first device (Li, paragraph [0006], receiving, by a user device, from a network device), comprising:
receiving configuration of one or more first sidelink resource pools for at least sidelink data transmission and configuration of one or more second sidelink resource pools dedicated for sidelink reference signal transmission (Li, Fig. 7; paragraph [0006], receiving, by a user device, from a network device, SL-PRS resource configuration; paragraph [0070], DCI allocates resources for SL-data transmission on PSSCH 712 and 714, and SL-PRS transmission 722 and 724);
receiving a Downlink Control Information (DCI) for scheduling sidelink data transmission or sidelink reference signal transmission (Li, Fig. 7; paragraph [0006], receiving, by a user device, from a network device, SL-PRS resource configuration; paragraph [0070], DCI allocates resources for SL-data transmission on PSSCH 712 and 714, and SL-PRS transmission 722 and 724), wherein a cyclic redundancy check (CRC) of the DCI is scrambled by a Radio Network Temporary Identifier (RNTI) (Li, paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration);
determining whether the DCI is for scheduling sidelink data transmission or for sidelink reference signal transmission based on the RNTI (Li, paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration);
acquiring or determining fields or information in the DCI based on a result of the determining whether the DCI is for scheduling sidelink data transmission or for sidelink reference signal transmission, wherein the DCI comprises a field of resource pool index corresponding to one sidelink resource pool (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index), and wherein:
when the DCI is determined for scheduling sidelink data transmission, the one sidelink resource pool is a first sidelink resource pool among the one or more first sidelink resource pools for at least sidelink data transmission (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index), or
when the DCI is determined for scheduling sidelink reference signal transmission, the one sidelink resource pool is a second sidelink resource pool among the one or more second sidelink resource pools dedicated for sidelink reference signal transmission (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index);
determining a sidelink resource in the one sidelink resource pool based on the acquired or determined fields, or the information in the DCI (Li, paragraph [0085], SL-PRS resource assignment; paragraph [0090], fields in the following table for the new DCI format: SL-PRS resource assignment); and
performing a sidelink transmission on the sidelink resource in the one sidelink resource pool (Li, Fig. 7; paragraph [0070], DCI allocates resources for SL-data transmission on PSSCH 712 and 714, and SL-PRS transmission 722 and 724).
Regarding claim 2, Li discloses the method of claim 1, wherein:
when the one sidelink resource pool is configured for at least sidelink data transmission, the first device acquires or determines fields or information, in the DCI, according to sidelink data transmission-related fields (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
when the one sidelink resource pool is configured for at least sidelink data transmission, the first device determines fields, in the DCI, as sidelink data transmission-related fields (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
when the one sidelink resource pool is configured for at least sidelink data transmission, the first device determines presence of sidelink data transmission-related fields and/or absence of sidelink reference signal-related fields in the DCI (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
when the DCI is determined for scheduling sidelink data transmission, the first device acquires or determines fields or information, in the DCI, according to sidelink data transmission-related fields (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
when the DCI is determined for scheduling sidelink data transmission, the first device determines presence of sidelink data transmission-related fields and/or absence of sidelink reference signal-related fields in the DCI (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
the first sidelink resource pool is configured for sidelink data transmission and with sidelink reference signal transmission (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index).
Regarding claim 3, Li discloses the method of claim 2, wherein:
the sidelink data transmission-related fields comprise or mean Physical Sidelink Shared Channel (PSSCH)-related fields (Li, Fig. 7; paragraph [0006], receiving, by a user device, from a network device, SL-PRS resource configuration; paragraph [0070], DCI allocates resources for SL-data transmission on PSSCH 712 and 714, and SL-PRS transmission 722 and 724); and/or
there is at least one first field in the sidelink data transmission-related fields and/or not in the sidelink reference signal-related fields (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0085], existing fields in DCI format; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
the at least one first field comprises any one or any combination of a Hybrid Automatic Repeat Request (HARQ) process number field, a new data indicator field, a frequency resource assignment for sub-channel, a Physical Sidelink Feedback Channel (PSFCH)-to-HARQ feedback timing indicator field, or a Physical Uplink Control Channel (PUCCH) resource indicator field (Li,; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, HARQ process number, frequency resource assignment, feedback timing indicator, PUCCH resource indicator).
Regarding claim 4, Li discloses the method of claim 1, wherein:
when the one sidelink resource pool is configured for sidelink reference signal transmission, the first device acquires or determines fields or information, in the DCI, according to sidelink reference signal-related fields (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
when the one sidelink resource pool is configured for sidelink reference signal transmission, the first device determines fields, in the DCI, as sidelink reference signal-related fields (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
when the one sidelink resource pool is configured for sidelink reference signal transmission, the first device determines presence of sidelink reference signal-related fields and/or absence of sidelink data transmission-related fields in the DCI (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
when the DCI is determined for scheduling sidelink reference signal transmission, the first device acquires or determines fields or information, in the DCI, according to sidelink reference signal-related fields (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
when the DCI is determined for scheduling sidelink reference signal transmission, the first device determines presence of sidelink reference signal-related fields and/or absence of sidelink data transmission-related fields in the DCI (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
the second sidelink resource pool is configured for sidelink reference signal transmission (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index).
Regarding claim 5, Li discloses the method of claim 4, wherein:
the sidelink reference signal-related fields comprise or mean Sidelink (SL)-Positioning Reference Signal-(PRS)-related fields (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, SL-PRS resource pool index); and/or
there is at least one second field in the SL-PRS-related fields and/or not in the sidelink data transmission-related fields (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, SL-PRS resource pool index); and/or
the at least one second field comprises at least one SL-PRS resource Identity or Index field (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, SL-PRS resource pool index).
Regarding claim 6, Li discloses the method of claim 1, wherein:
determining whether the DCI is for scheduling sidelink data transmission or for scheduling sidelink reference signal transmission based on the RNTI being associated with sidelink data transmission or sidelink reference signal transmission (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0085], SL-RNTI or SL-CS-RNTI or SL-PRS-RNTI or SL-PRS-CS-RNTI; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, SL-PRS resource pool index); and/or
when the RNTI is associated with sidelink data transmission, the first device determines the DCI is for scheduling sidelink data transmission (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0085], SL-RNTI or SL-CS-RNTI or SL-PRS-RNTI or SL-PRS-CS-RNTI; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, SL-PRS resource pool index); and/or
when the RNTI is associated with sidelink reference signal transmission, the first device determines the DCI is for scheduling sidelink reference signal transmission (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0085], SL-RNTI or SL-CS-RNTI or SL-PRS-RNTI or SL-PRS-CS-RNTI; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, SL-PRS resource pool index).
Regarding claim 7, Li discloses the method of claim 1, wherein:
a bit size of the DCI used for scheduling sidelink data transmission is same as a bit size of the DCI used for scheduling sidelink reference signal transmission (Li, paragraph [0086], the size of the new DCI format can be the same or different from the existing format; information bits for the new DCI format); and/or
a total bit number of sidelink data transmission-related fields, including padding bits, if any, in the DCI used for scheduling sidelink data transmission is same as a total bit number of sidelink reference signal-related fields, including padding bits, if any, in the DCI used for scheduling sidelink reference signal transmission (Li, paragraph [0086], the size of the new DCI format can be the same or different from the existing format; information bits for the new DCI format; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, SL-PRS resource pool index, padding bits).
Regarding claim 8, Li discloses the method of claim 6, wherein:
the RNTI associated with sidelink data transmission is SL-RNTI or SL-Configured Scheduling (CS)-RNTI (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0085], SL-RNTI or SL-CS-RNTI or SL-PRS-RNTI or SL-PRS-CS-RNTI; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, SL-PRS resource pool index); and/or
the RNTI associated with sidelink reference signal transmission is SL-Positioning Reference Signal (PRS)-RNTI or SL-PRS-CS-RNTI (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0085], SL-RNTI or SL-CS-RNTI or SL-PRS-RNTI or SL-PRS-CS-RNTI; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, SL-PRS resource pool index); and/or
when the CRC of the DCI is scrambled by a SL-RNTI or a SL-CS-RNTI, the first device determines the DCI is for scheduling sidelink data transmission (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0085], SL-RNTI or SL-CS-RNTI or SL-PRS-RNTI or SL-PRS-CS-RNTI; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, SL-PRS resource pool index); and/or
when the CRC of the DCI is scrambled by a SL- PRS-RNTI or a SL-PRS-CS-RNTI, the first device determines the DCI is for scheduling sidelink reference signal transmission (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0085], SL-RNTI or SL-CS-RNTI or SL-PRS-RNTI or SL-PRS-CS-RNTI; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, SL-PRS resource pool index).
Regarding claim 9, Li discloses the method of claim 1, wherein:
the first device determines the one sidelink resource pool based on the field of resource pool index and the RNTI (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
when the DCI is determined for scheduling sidelink data transmission, the field of resource pool index indicates a first resource pool identity or index associated with the first sidelink resource pool (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
when the DCI is determined for scheduling sidelink reference signal transmission, the field of resource pool index indicates a second resource pool identity or index associated with the second sidelink resource pool (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index); and/or
the first resource pool identity or index is the same as or different from the second resource pool identity or index (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index).
Regarding claim 10, Li discloses the method of claim 1, wherein: the one or more first sidelink resource pools and the one or more second sidelink resource pools are configured in a same carrier, or a same cell, or a same SL Bandwidth Part (BWP) (Li, Fig. 1, single/same cell).
Regarding claim 11, Li discloses a method of a network node (Li, paragraph [0006], receiving, by a user device, from a network device), comprising:
transmitting, to a first device, configuration of one or more first sidelink resource pools for at least sidelink data transmission and configuration of one or more second sidelink resource pools dedicated for sidelink reference signal transmission (Li, Fig. 7; paragraph [0006], receiving, by a user device, from a network device, SL-PRS resource configuration; paragraph [0070], DCI allocates resources for SL-data transmission on PSSCH 712 and 714, and SL-PRS transmission 722 and 724);
determining a sidelink resource associated with one sidelink resource type in one sidelink resource pool, wherein the one sidelink resource type is for sidelink data transmission or for sidelink reference signal transmission (Li, paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration), and wherein:
when the one sidelink resource type is for sidelink data transmission, the one sidelink resource pool is a first sidelink resource pool among the one or more first sidelink resource pools for at least sidelink data transmission (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index), or
when the one sidelink resource type is for sidelink reference signal transmission, the one sidelink resource pool is a second sidelink resource pool among the one or more second sidelink resource pools dedicated for sidelink reference signal transmission (Li, paragraph [0065], fields of the DCI format; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index);
generating a Downlink Control information (DCI), wherein the DCI indicates the sidelink resource and comprises a field of resource pool index corresponding to the one sidelink resource pool (Li, Fig. 7; paragraph [0006], receiving, by a user device, from a network device, SL-PRS resource configuration; paragraph [0065], fields of the DCI format; paragraph [0070], DCI allocates resources for SL-data transmission on PSSCH 712 and 714, and SL-PRS transmission 722 and 724; paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration; paragraph [0090], fields in the following table for the new DCI format: SL-PRS Transmission indication: 0 for SL-PRS or 1 for SL data and SL-PRS, resource pool index);
scrambling a cyclic redundancy check (CRC) of the DCI by a Radio Network Temporary Identifier (RNTI), wherein the RNTI is determined based on the one sidelink resource type (Li, paragraph [0084], new DCI format is CRC scrambled by SL-PRS-RNTI to indicate SL-PRS resource configuration); and
transmitting the DCI to the first device (Li, Fig. 7; paragraph [0070], DCI allocates resources for SL-data transmission on PSSCH 712 and 714, and SL-PRS transmission 722 and 724).
Claims 12-16 are rejected under substantially the same rationale as claims 2-5 and 7, respectively.
Claim 17 is rejected under substantially the same rationale as claims 6 and 8.
Claims 18-19 are rejected under substantially the same rationale as claims 9-10, respectively.
Claim 20 is rejected under substantially the same rationale as claim 1. Li additionally discloses a memory; and a processor operatively coupled to the memory, wherein the processor is configured to execute a program code (Li, Fig. 14; paragraphs [0175]-[0177], memory, processor, processor-executable instructions).
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ALAN LOUIS LINDENBAUM whose telephone number is (571)270-3858. The examiner can normally be reached Monday through Friday 9:00 AM to 5:00 PM EST.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Nishant Divecha can be reached at (571) 270-3125. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/ALAN L LINDENBAUM/ Examiner, Art Unit 2419
/Nishant Divecha/ Supervisory Patent Examiner, Art Unit 2419