CTNF 18/833,044 CTNF 83277 Notice of Pre-AIA or AIA Status 07-03-aia AIA 15-10-aia The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA. Information Disclosure Statement The information disclosure statements (IDS) submitted on 25 th July 2024 and 25 th September 2025 are in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner. ---------- ---------- ---------- Drawings 06-22 The figures 3A, 3B and 4 are objected to because the drawings and the texts within the drawings are blurry. Corrected drawing sheets in compliance with 37 CFR 1.121(d) are required in reply to the Office action to avoid abandonment of the application. Any amended replacement drawing sheet should include all of the figures appearing on the immediate prior version of the sheet, even if only one figure is being amended. The figure or figure number of an amended drawing should not be labeled as “amended.” If a drawing figure is to be canceled, the appropriate figure must be removed from the replacement sheet, and where necessary, the remaining figures must be renumbered and appropriate changes made to the brief description of the several views of the drawings for consistency. Additional replacement sheets may be necessary to show the renumbering of the remaining figures. Each drawing sheet submitted after the filing date of an application must be labeled in the top margin as either “Replacement Sheet” or “New Sheet” pursuant to 37 CFR 1.121(d). If the changes are not accepted by the examiner, the applicant will be notified and informed of any required corrective action in the next Office action. The objection to the drawings will not be held in abeyance. ========== ========== ========== Claim Rejections - 35 USC § 102 07-07-aia AIA 07-07 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 – 07-12-aia AIA (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. 07-15-03-aia AIA Claim s 35 – 43 and 44 – 47 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Li et al (US 2024/0244711 A1) . Claim 43 (similarly Claim 35 ). Li shows a network entity (fig. 3: Multicast Session Management Network Element, hereinafter “ element ” ), comprising: one or more processors (fig. 5: processor); and one or more memories comprising computer program codes (fig. 5: memory), the one or more memories and the computer program codes being configured to, with the one or more processors, cause the network entity at least to: receive, from an application server, a message to request a temporary mobile group identity (TMGI) allocation for a multicast/broadcast service (MBS) session, including area information (fig. 3, [0188] and [0247]: the first information in S210 may be carried in an existing temporary multicast group identifier allocation request (nnef_tmgi_allocate request) message… the second service area identifier of the first multicast service may be carried in a response message of the existing temporary multicast group identifier allocation request message… after S210, to be specific, after receiving the first information described above, the network display function or the multicast/broadcast service function may perform authentication on a request of the application server), wherein the area information indicates a service area for the TMGI to be allocated ( see above ); and determine a multicast/broadcast-session management function (MB-SMF) based at least in part on the area information for the allocation of the TMGI ([0103]: a reference point between the AF/AS and the MB-SMF, and is used by the AF/AS to provide the MB-SMF with the parameter related to the multicast and broadcast, for example, the service area and the multicast/broadcast service requirement ; [0189]: S210 and S220 are performed after an existing application server receives a response message of a temporary multicast group identifier allocation request message and before the existing application server sends the service announcement message wherein the second service area identifier of the first multicast service may be carried in the existing service announcement message). Claim 36. Li shows the method of claim 35, wherein the area information is in external area format ([0103]: the NEF may properly process the parameter of the AF (for example, translate geographic location information into a cell identifier or a tracking area identifier ) and send a processed parameter to the MB-SMF), the method further comprising: translating the area information in the external area format into the area information in internal area format ( see above ). Claim 37. Li shows the method of claim 36, wherein the area information in the external area format includes geographical area information and/or civic address information ([0103]: translate geographic location information into a cell identifier or a tracking area identifier). Claim 38. Li shows the method of claim 36, wherein the area information in the internal area format includes a cell identifier (ID) list and/or a tracking area identifier (TAI) list ([0173] – [0174]: the correspondence between a cell list /a tracking area list /a base station list and a service area identifier may be stored in the multicast session management network element). Claim 39. Li shows the method of claim 35, wherein the MB-SMF is determined by the network entity by: transmitting a query for the MB-SMF to a database, wherein the query includes the area information ([0088]: performing signaling exchange with the access network device and a multicast/broadcast session management function (multicast/broadcast SMF, MB-SMF ) for MBS session management; [0249]: the network display function or the multicast/broadcast service function uses the information as an input of an NRF query , to obtain the identification information of the multicast session management network element, and then send the first information to the multicast/broadcast service function); receiving a response to the query from the database ([0249]: the network display function or the multicast/broadcast service function may obtain the identification information of the multicast session management network element in a manner of local configuration, and then send the first information to the multicast/broadcast service function), wherein the response indicates one or more MB-SMFs matching the area information ([0103]: a reference point between the NEF and the MB-SMF, and is used by the NEF to provide the MB-SMF with a parameter sent by an AF side… the NEF may properly process the parameter of the AF (for example, translate geographic location information into a cell identifier or a tracking area identifier ) and send a processed parameter to the MB-SMF ); and selecting the MB-SMF from the one or more MB-SMFs ([0088]: selecting the access network device for broadcasting; [0204]: the multicast session management network element selects an available temporary multicast group identifier from a temporary multicast group identifier resource pool preconfigured by a network, and uses the available temporary multicast group identifier as the temporary multicast group identifier of the first multicast service). Claim 40. Li shows the method of claim 39, wherein the database is a network repository function (NRF) entity ([0209]: the correspondence between a frequency/ temporary multicast group identifier of the multicast service and a service area may be stored in the multicast session management network element, or may be stored in another network element, for example, the UDM, a user data repository (UDR), a PCF, the NRF , the NEF, an MBSF-NEF, or a network element dedicated to multicast and broadcast). Claim 41. Li shows the method of claim 35, wherein the service area indicated by the area information covers one or more MBS service areas for area sessions of the MBS session for location-dependent MBS in a session management function (SMF) service area ([0095] and [0103]: MBS… MB-SMF… service area… tracking area identifier). Claim 42. Li shows the method of claim 35, wherein the network entity is a network exposure function (NEF) entity ([0103]: NEF), or a multicast/broadcast service function (MBSF) entity ([0095]: MBSF), or a combination of the NEF entity and the MBSF entity ([0094]: a function that is supported by the MBSF and that is related to an MBS includes exchanging related information at a service layer with an NEF, an MB-SMF, and a multicast/broadcast service transport function (MBSTF)). ---------- ---------- ---------- Claim 44 . Li shows a method performed by an application server (fig. 3: application server), comprising: transmitting, to a network entity (fig. 3: Multicast Session Management Network Element), a message to request a temporary mobile group identity (TMGI) allocation for a multicast/broadcast service (MBS) session including area information ([0188]: the application server requests the allocation of the temporary multicast group identifier … in an existing temporary multicast group identifier allocation request (nnef_tmgi_ allocate request ) message… the second service area identifier of the first multicast service may be carried in a response message of the existing temporary multicast group identifier allocation request message), wherein the area information indicates a service area for the TMGI to be allocated ( see above ); and receiving the allocated TMGI for the MBS session ([0189]: after an existing application server receives a response message of a temporary multicast group identifier allocation request message and before the existing application server sends the service announcement message), wherein the allocated TMGI is based on the area information ([0189]: the second service area identifier of the first multicast service may be carried in the existing service announcement message). Claim 45. Li shows the method of claim 44, wherein the area information includes one or more of : geographical area information ([0103]: translate geographic location information into a cell identifier or a tracking area identifier), civic address information ( n/a ), a cell identifier (ID) list ([0173] – [0174]: the correspondence between a cell list /a tracking area list /a base station list and a service area identifier may be stored in the multicast session management network element), and a tracking area identifier (TAI) list ( see above ; [0173] – [0174]: the multicast session management network element stores a correspondence of {SAI, cell id/TA id/RAN id}). Claim 46. Li shows the method of claim 44, wherein the service area indicated by the area information covers one or more MBS service areas for area sessions of the MBS session for location-dependent MBS in a session management function (SMF) service area ([0095] and [0103]: MBS… MB-SMF… service area… tracking area identifier). Claim 47. Li shows the method of claim 44, wherein the network entity is a network exposure function (NEF) entity ([0103]: NEF), or a multicast/broadcast service function (MBSF) entity ([0095]: MBSF), or a combination of the NEF entity and the MBSF entity ([0094]: a function that is supported by the MBSF and that is related to an MBS includes exchanging related information at a service layer with an NEF, an MB-SMF, and a multicast/broadcast service transport function (MBSTF)). ========== ========== ========== Conclusion The prior art made of record is considered pertinent to applicant’s disclosure. 1. Kim et al, US 2023/0209446 A1: a method for performing multicast-related communication, wherein the method performed by a Session Management Function (SMF) and comprising receiving, from a User Equipment (UE), a first request message for joining a multicast group; determining whether the UE is inside or outside a service area and transmitting a join reject message to the UE, based on determining that the UE is not located within the service area, wherein the join reject message includes service area information, and wherein the service area information includes a Cell ID list or Tracking Area ID (TAI) list. 2. Jeong et al, US 2022/0329983 A1: a method performed by a session management function (SMF) in a communication system, the method comprising receiving, from a terminal, a first message comprising information on a request for establishing a protocol data unit (PDU) session for a multicast broadcast service (MBS); transmitting, to an unified data management (UDM), a second message for requesting subscription information of the terminal; receiving, from the UDM, a third message comprising the subscription information of the terminal, the subscription information of the terminal including information indicating whether the terminal is authorized to use the MBS and information for identifying at least one session of the MBS allowed for the terminal; and transmitting, to the terminal, a fourth message as a response to the first message according to the subscription information of the terminal, the fourth message comprising information on a result of the establishing the PDU session. 3. Baek et al, US 2022/0279319 A1: a method performed by a session management function (SMF) entity, the method comprising transmitting, to a network repository function (NRF) entity, a first request message to discover at least one access and mobility management function (AMF) entity, based on a multicast/broadcast service (MBS) service area; receiving, from the NRF entity, a response message including information on at least one discovered AMF entity; and selecting at least one AMF based on the response message. Any inquiry concerning this communication or earlier communications from the examiner should be directed to Xavier Szewai Wong whose telephone number is 571.270.1780. The examiner can normally be reached on 11:30 am - 8:30 pm Mon to 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, Jeffrey Rutkowski can be reached on 571.270.1215. 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. /XAVIER S WONG/ Primary Examiner, Art Unit 2415 17 th May 2026 Application/Control Number: 18/833,044 Page 2 Art Unit: 2415 Application/Control Number: 18/833,044 Page 3 Art Unit: 2415 Application/Control Number: 18/833,044 Page 4 Art Unit: 2415 Application/Control Number: 18/833,044 Page 5 Art Unit: 2415 Application/Control Number: 18/833,044 Page 6 Art Unit: 2415 Application/Control Number: 18/833,044 Page 7 Art Unit: 2415 Application/Control Number: 18/833,044 Page 8 Art Unit: 2415
Prosecution Insights