DETAILED ACTION
This office action is in response to the application filed on 9/5/2024 in which claims 1 and 4 are pending.
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 .
Priority
Receipt is acknowledged of certified copies of papers required by 37 CFR 1.55.
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 and 4 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Ferdi et al. (US20260164235A1).
As to claim 1, Ferdi teaches a User Equipment (UE) comprising: (fig. 1b)
controlling circuitry: and (fig. 1b processor 118)
transmitting and receiving circuitry, (fig. 1b transceiver 120)
wherein the UE is a UAV, ([0078] a wireless transmit and receive unit (WTRU) (e.g., an unmanned (uncrewed) aerial vehicle (UAV).)
the transmitting and receiving circuitry is configured to:
to a core network, a PDU session establishment request message including information indicating that authorization for Direct Command and Control (C2) Communication is requested, and ([0007] In examples, a first WTRU may send a first message to a network node indicating a C2 authorization request and a request for a PDU session. [0079] The authorization request may correspond with a C2 communication, such as direct or line-of-sight C2 communication. [0101] The WTRU (e.g., UAV and/or UAV-C) may indicate LOS and/or BVLOS or direct and/or network-assisted/indirect C2 communication, for example, if requesting C2 authorization (e.g., in a NAS message, in a UAS container) in a PDU Session establishment/modification request message. The WTRU may indicate its support for direct C2 communication (e.g., C2 over PC5) in the C2 authorization request.)
receive from the core network, a PDU session establishment accept message including identification information related to a UAV-controller (UAV-C), ([0079] The WTRU may receive C2authorization parameters (e.g., in an aviation container to facilitate discovery procedure with a UAV-C (e.g., UAS app user ID, discovery credentials, etc.), for example, to use as part of direct discovery (e.g., open or restricted direct discovery). The WTRU may perform (e.g., start) discovery. In examples, the WTRU may perform discovery on the condition that the WTRU receives C2 authorization information from the USS. The WTRU may use parameters from the USS to enable discovery with the UAV-C. [0102] The WTRU may obtain authorization information for direct C2 communication (e.g., parameters for peer discovery such as peer(s) CAA level ID/WTRU ID and/or credentials for direct link security, for example, in a NAS message/UAS container) in a message from an SMF (e.g., PDU Session establishment accept/command))
the controlling circuitry is configured to perform the Direct C2 Communication after the Direct C2 Communication is authorized, and ([0098] For example, a system may provide communication capabilities between the UAV and UAV-C, which may communicate through the same or different public land mobile networks (PLMNs). UAV and UAV-C may be equipped with a WTRU, for example, to enable device-to-device (D2D) communications (e.g., PC5). [0100] C2 communication authorization, such as direct C2 communication authorization, may be provided for UAVIUAV-C. C2 authorization may be enhanced to allow C2 over Uu and/or direct (e.g., PC5).)
the Direct C2 Communication is a communication using a Direct C2 link established between the UAV and the UAV-C over PC5. ([0098] For example, a system may provide communication capabilities between the UAV and UAV-C, which may communicate through the same or different public land mobile networks (PLMNs). UAV and UAV-C may be equipped with a WTRU, for example, to enable device-to-device (D2D) communications (e.g., PC5). [0100] C2 communication authorization, such as direct C2 communication authorization, may be provided for UAVIUAV-C. C2 authorization may be enhanced to allow C2 over Uu and/or direct (e.g., PC5).)
As to claim 4, Ferdi teaches a communication control method performed by a User Equipment (UE), the communication control method comprising: ([0112] FIG. 4 illustrates an example of PC5 direct communication with C2 authorization followed by discovery.)
transmitting, to a core network, a PDU session establishment request message including information indicating that authorization for Direct Command and Control (C2) Communication is requested, ([0007] In examples, a first WTRU may send a first message to a network node indicating a C2 authorization request and a request for a PDU session. [0079] The authorization request may correspond with a C2 communication, such as direct or line-of-sight C2 communication. [0101] The WTRU (e.g., UAV and/or UAV-C) may indicate LOS and/or BVLOS or direct and/or network-assisted/indirect C2 communication, for example, if requesting C2 authorization (e.g., in a NAS message, in a UAS container) in a PDU Session establishment/modification request message. The WTRU may indicate its support for direct C2 communication (e.g., C2 over PC5) in the C2 authorization request.)
receiving, from the core network, a PDU session establishment accept message including identification information related to a UAV-controller (UAV-C), and ([0079] The WTRU may receive C2authorization parameters (e.g., in an aviation container to facilitate discovery procedure with a UAV-C (e.g., UAS app user ID, discovery credentials, etc.), for example, to use as part of direct discovery (e.g., open or restricted direct discovery). The WTRU may perform (e.g., start) discovery. In examples, the WTRU may perform discovery on the condition that the WTRU receives C2 authorization information from the USS. The WTRU may use parameters from the USS to enable discovery with the UAV-C. [0102] The WTRU may obtain authorization information for direct C2 communication (e.g., parameters for peer discovery such as peer(s) CAA level ID/WTRU ID and/or credentials for direct link security, for example, in a NAS message/UAS container) in a message from an SMF (e.g., PDU Session establishment accept/command))
performing the Direct C2 Communication after the Direct C2 Communication is authorized, ([0098] For example, a system may provide communication capabilities between the UAV and UAV-C, which may communicate through the same or different public land mobile networks (PLMNs). UAV and UAV-C may be equipped with a WTRU, for example, to enable device-to-device (D2D) communications (e.g., PC5). [0100] C2 communication authorization, such as direct C2 communication authorization, may be provided for UAVIUAV-C. C2 authorization may be enhanced to allow C2 over Uu and/or direct (e.g., PC5).)
wherein the UE is a UAV, and ([0078] a wireless transmit and receive unit (WTRU) (e.g., an unmanned (uncrewed) aerial vehicle (UAV).)
the Direct C2 Communication is a communication using a Direct C2 link established between the UAV and the UAV-C over PC5. ([0098] For example, a system may provide communication capabilities between the UAV and UAV-C, which may communicate through the same or different public land mobile networks (PLMNs). UAV and UAV-C may be equipped with a WTRU, for example, to enable device-to-device (D2D) communications (e.g., PC5). [0100] C2 communication authorization, such as direct C2 communication authorization, may be provided for UAVIUAV-C. C2 authorization may be enhanced to allow C2 over Uu and/or direct (e.g., PC5).)
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ELTON S WILLIAMS whose telephone number is (571)272-9933. The examiner can normally be reached 8-4 Mon-Fri.
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, Gary Mui can be reached at (571) 270-1420. 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.
/Elton Williams/ Examiner, Art Unit 2465
Prosecution Insights