DETAILED ACTION
Notice of Pre-AIA or AIA Status
1. The instant application No. 18/766,825 has claims 1-5 are pending.
2 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 § 112
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 1-5 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention.
Claims 1 and 4 recites the following limitation: “transmitting a Handover Request message to a target base station for handover of a mobile terminal, the Handover Request message including information on an authorization status of the mobile terminal for Vehicle-to-Everything (V2X) services.” Specification discloses the source eNB 130S (or the RSU 220) determines to perform a handover of the UE 100 based on the measurement report and sends a handover request that contains V2X indication to the target eNB 130T (or the RSU 221). The V2X indication indicates at least one of: the UE 100 is interested in the V2X service; the UE 100 is allowed to utilize the V2X service; the UE 100 has already been authenticated for the V2X service; and the UE 100 has already been approved for the V2X service (See ¶0053). There is nothing in the specification for authorization status of the mobile terminal. Further, it’s a single service being authenticated not a plurality of service. The limitation has no support in the original specification.
Claims 2 and 5 recites the following limitation: “the Handover Request Acknowledge message includes a V2X configuration indicating the V2X services or area information of the V2X services.” Applicant specifications paragraph 0054-0055 state the acknowledgment contains The V2X configuration may include information about the V2X service provided in the target cell or information about the V2X service area that the target cell contains (or the V2X service area in which the target cell is contained) (e.g., V2X SA Index (ID)). Nothing in specification state the acknowledgement is v2x services. The limitation has no support in the original specification.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
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 and 4 are rejected under 35 U.S.C. 102(a)(2)as being anticipated by Xu et al. (Pub. No. US 2018/0199194 A1; hereinafter Xu).
Regarding claim 1, Xu discloses a method of a source base station comprising: transmitting a Handover Request message to a target base station for handover of a mobile terminal, the Handover Request message including information on an authorization status of the mobile terminal for Vehicle-to-Everything (V2X) services; (See 0060, the authorization information for at least one of vehicle UE or RSU UE may be transmitted during mobility procedure. For X2 handover procedure, the authorization information for at least one of vehicle UE or RSU UE may be transmitted from the source eNB to the target eNB via the handover request message; See 0057, The authorization information for the vehicle UE may be “Vehicle UE Authorized” information element (IE), which may be included in an existing message or a new message. The authorization information for the vehicle UE (or “Vehicle UE Authorized” IE) provides information on the authorization status of the vehicle UE for V2X services.) receiving a Handover Request Acknowledge message from the target base station. (See 0073, If “Vehicle UE Authorized” IE or “RSU UE Authorized” IE is contained in the handover request message, and it contains one or more IEs set to “authorized”, the target eNB may, if supported, consider that the corresponding UE is authorized for the relevant V2X services. In step S401, the eNB2 transmits a handover request acknowledge message to the eNB1.)
Regarding claim 4, Xu disclose a method of a target base station comprising: receiving a Handover Request message from a source base station for handover of a mobile terminal, the Handover Request message including information on an authorization status of the mobile terminal for Vehicle-to-Everything (V2X) services; (See 0060, the authorization information for at least one of vehicle UE or RSU UE may be transmitted during mobility procedure. For X2 handover procedure, the authorization information for at least one of vehicle UE or RSU UE may be transmitted from the source eNB to the target eNB via the handover request message; See 0057, The authorization information for the vehicle UE may be “Vehicle UE Authorized” information element (IE), which may be included in an existing message or a new message. The authorization information for the vehicle UE (or “Vehicle UE Authorized” IE) provides information on the authorization status of the vehicle UE for V2X services.) transmitting a Handover Request Acknowledge message from the target base station. (See 0073, If “Vehicle UE Authorized” IE or “RSU UE Authorized” IE is contained in the handover request message, and it contains one or more IEs set to “authorized”, the target eNB may, if supported, consider that the corresponding UE is authorized for the relevant V2X services. In step S401, the eNB2 transmits a handover request acknowledge message to the eNB1.)
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Dinan et al. (Pub. No. US 20180049224 A1)-See 0292, during the handover process, eNB may consider the information on whether the target eNB supports V2X service in the handover decision process. For example, an eNB may prioritize handover to a target eNB that supports V2X services, over another target eNB that does not support V2X service. eNBs may transmit/receive message to/from eNBs indicating whether the eNB supports V2X services. An eNB may transmit handover request to one or more target eNBs and receive handover ack from the one or more target eNB. In an example, handover request may request V2X services, and handover ack may include information about whether the eNB supports V2X services.
Park et al. (Pub. No. US 2018/0124648 A1)-See ¶0181, if the Expected UE Behavior IE is provided in the HANDOVER REQUEST message, the target eNB may, if supported, store this information and may use it to determine the RRC connection time. If the ProSe Authorized IE is contained in the HANDOVER REQUEST message and it contains one or more IEs set to “authorized”, the eNB may, if supported, consider that the UE is authorized for the relevant ProSe service(s). If the V2X Services Authorized IE is contained in the HANDOVER REQUEST message and it contains one IE set to “authorized”, the eNB may, if supported, consider that the UE is authorized for the relevant service(s). If the UE Context Reference at the SeNB IE is contained in the HANDOVER REQUEST message the target eNB may use it. In this case, the source eNB may expect the target eNB to include the UE Context Kept Indicator IE set to “True” in the HANDOVER REQUEST ACKNOWLEDGE message, which may use this information. If the Bearer Type IE is included in the HANDOVER REQUEST message and is set to “non IP”, the target eNB may not perform header compression for the concerned E-RAB.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to TEJIS DAYA whose telephone number is (571)270-7817. The examiner can normally be reached 6:30-4:30.
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, Nicholas Jensen can be reached at 571-270-5443. 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.
/Tejis Daya/Primary Examiner, Art Unit 2472
Prosecution Insights