DETAILED ACTION
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
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)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claim(s) 21-34 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Bernt et al. (hereinafter “Bernt”, Bernt Mattsson et al., Information flows and procedures involving multiple systems for the ad hoc data session in MCData, 3GPP, SA WG6, 27 April 2023, XP052307361) .
As per claim 21, Bernt disclosed a method performed (see at least section 7.17.3.K.3, Ad hoc data communication setup) , by a mission critical data (MCData) server of a primary (see at least Fig. 7.17.3.K.3-1, MCData server 1) MCData system in a wireless communication system, the method comprising receiving, from an MCData client (see Fig. 7.17.3.K.3-1, MCData client 1), a data transfer request message for identifying a target MCData user for ad hoc group standalone short data service SDS (see at least Fig. 7.17.3.K.3-1, step 1); transmitting, to an MCData server of a partner MCData system (see at least Fig. 7.17.3.K.3-1, MCDATA server 2 (partner), a get user list request message including criteria for identifying a list of at least one target MCData user, if the criteria is included in the data transfer request message (see at least Fig. 7.17.3.K.3-1, step 5); receiving, from the MCData server of the partner MCData system, a get user list response message including the list of at least one target MCData user associated with the criteria (see at least Fig. 7.17.3.K.3-1, step 6); generating an ad hoc group based on the list of at least one MCData user (see at least Fig. 7.17.3.K.3-1, step 7); and transmitting, to the MCData client, a data transfer response message including information for the ad hoc group in response to the data transfer request message (see at least Fig. 7.17.3.K.3-1, steps 14).
As per claims 22 and 29, Bernt disclosed identifying whether the criteria for identifying the list of at least one MCData user or the list of at least one MCData user is included in the data transfer request message, wherein, if the criteria is included in the data transfer request message, the list of at least one MCData user for the ad hoc group SDS is identified within the primary MCData system (see throughout the reference, wherein the reference disclosed description of how the information flow Ad hoc group data session release notification from one MCData server to another MCData server. his notification is to provide the list of MCData IDs meeting the criteria specified in the ad hoc group data session get user list request from one MCData server to another MCData server).
As per claims 23 and 30, Bernt disclosed generating the ad hoc group further comprises
identifying a pre-configured MCData group to be used for configuration of the ad hoc group and an MCData ad hoc group identifier (ID) for the ad hoc group (see at least section 7.17.3.K.1, Figure 7.17.3.K.1-1 illustrates the procedure for ad hoc group data communication setup procedure, Pre-conditions: steps 1-5).
As per claims 24 and 31, Bernt disclosed the information for the ad hoc group included in the data transfer response message includes at least one of the ad hoc group ID, a pre-configured MCData group ID of the identified pre-configured MCData group, or a result of a data transfer request (see at least section 7.17.3.K.1, Figure 7.17.3.K.1-1 illustrates the procedure for ad hoc group data communication setup procedure, Pre-conditions: steps 1-5). .
As per claims 25 and 32, Bernt disclosed receiving, from the MCData client, an ad hoc group data request message including an ad hoc group identifier (ID); and transmitting, to at least one target MCData user, an ad hoc group data request message (see at least section 7. 17.3.K.3 and figure 7.17.3.K.3-1; section 7.17.3.K.4 and figure 7.17.3.K.4.1).
As per claims 26 and 33, Bernt disclosed the ad hoc group data request message further
includes information for at least one of an ID of the at least one target MCData user, a conversation ID, a transaction ID, an emergency indicator, a location, an application ID, or SDS content (see at least figure 7.17.4.M.2-1, description of SDS data throughout the reference).
As per claims 27 and 34, Bernt disclosed wherein, if SDS content of ad hoc group data is for MCData user consumption, a notification of the ad hoc group data is provided to the at least one target MCData user (see at least section 7.17.3.K.3, The MCData server 1 may notify the initiating MCData user of all MCData users who acknowledged the ad hoc group data session request and joined the ad hoc group data communication The MCData server 1 more than once during the data communication may send this notification to the initiating MCData user whenever an MCData user joins or leaves the MCData ad hoc group data communication. If the authorized users (not shown in figure) are configured to receive the participants information of ad hoc group data communication, the MCData server provides ad hoc group data session notify about all MCData users who acknowledged the ad hoc group data session request and joined the ad hoc group data communication, and when MCData users joins or leaves the MCData ad hoc group data communication).
As per claim 28, see rejection above in claim 21, Bernt further disclosed at least one processor (inherently) and at least one memory (inherently).
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Pablo Tran whose telephone number is (571)272-7898. The examiner normal hours are 9:30 -5:00 (Monday-Friday). If attempts to reach the examiner by telephone are unsuccessful, the examiner's supervisor, Jinsong Hu, can be reached at (571)272-3965. The fax phone number for the organization where this application or proceeding is assigned is (571)273-8300.
Information regarding the status of an application may be obtained from the
Patent Application Information Retrieval (PAIR) System. Status information for
Published applications may be obtained from either Private PAIR or Public PAIR.
Status information for unpublished applications is available through Private PAIR only.
For more information about the PAIR system, see httpr//pair-directauspto.gov. Should
You have questions on access to the Private PAIR system, contact the Electronic
Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (in USA or CANADA) or 571-272-1000.
August 12, 2026
/PABLO N TRAN/Primary Examiner, Art Unit 2643
Prosecution Insights