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 .
Response to Amendment
This Action is in response to Applicant’s Amendment filed on March 3, 2026. Claims 1-4 are still pending in the present application. This Action is made Non-FINAL.
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-4 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Shrivastava et al (US Pat. Pub. No. 2024/0214988).
Regarding claim 1, Shrivastava et al discloses a communication control method performed by a user equipment in a mobile communication system for providing Multicast/Broadcast Services (MBS) to the user equipment, the communication control method comprising: receiving, from a network node, a Radio Resource Control (RRC) reconfiguration message for establishing a multicast MBS bearer for the user equipment in an RRC connected state (see at least paragraph 100 discloses in connected state, terminal receiving RRC reconfiguration message which includes MBS radio bearer (BRB)), wherein the RRC reconfiguration message comprises an MBS session identifier indicating a multicast MBS session associated with the multicast MBS bearer (see at least paragraph 100 discloses RRC reconfiguration message carries activation of MBS session; further on paragraph 106-107 discloses MBS session ID).
Regarding claim 2, Shrivastava et al discloses notifying, by an RRC entity in the user equipment, an entity in a higher layer than the RRC entity of the MBS session identifier comprised in the RRC reconfiguration message (see at least paragraph 52 discloses notifying to higher layer).
Regarding claim 3, Shrivastava et al discloses a user equipment that receives Multicast/Broadcast Services (MBS) from network, the user equipment comprising: a receiver configured to receive from a network node, a Radio Resource Control (RRC) reconfiguration message for establishing a multicast MBS bearer for the user equipment in an RRC connected state (see at least paragraph 100 discloses in connected state, terminal receiving RRC reconfiguration message which includes MBS radio bearer (BRB)), wherein the RRC reconfiguration message comprises an MBS session identifier indicating a multicast MBS session associated with the multicast MBS bearer (see at least paragraph 100 discloses RRC reconfiguration message carries activation of MBS session; further on paragraph 106-107 discloses MBS session ID).
Regarding claim 4, Shrivastava et al discloses a network node configured to provide Multicast/Broadcast Services (MBS), the network node comprising: a transmitter configured to transmit to a user equipment in an RRC connected state, a Radio Resource Control (RRC) reconfiguration message for establishing a multicast MBS bearer for the user equipment (see at least paragraph 100 discloses in connected state, terminal receiving RRC reconfiguration message which includes MBS radio bearer (BRB)), wherein the RRC reconfiguration message comprises an MBS session identifier indicating a multicast MBS session associated with the multicast MBS bearer (see at least paragraph 100 discloses RRC reconfiguration message carries activation of MBS session; further on paragraph 106-107 discloses MBS session ID).
Response to Arguments
Applicant's arguments, filed on March 3, 2026, with respect to claims 1, 3 and 4 have been considered and are persuasive. Therefore, the rejection has been withdrawn. However, upon further consideration, a new ground(s) of rejection is made in view of Shrivastava et al.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to LITON MIAH whose telephone number is (571)270-3124. The examiner can normally be reached on Mon - Fri 7:30am -5:00pm.
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, Rafael Perez-Gutierrez can be reached on 571-272-7915. 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 http://pair-direct.uspto.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.
/LITON MIAH/Primary Examiner, Art Unit 2642
Prosecution Insights