Prosecution Insights
Last updated: April 19, 2026
Application No. 18/908,840

EVENT MANAGEMENT SYSTEM, EVENT MANAGEMENT METHOD, AND NON-TRANSITORY RECORDING MEDIUM

Non-Final OA §102§103§112
Filed
Oct 08, 2024
Examiner
VANG, MENG
Art Unit
2443
Tech Center
2400 — Computer Networks
Assignee
Ricoh Company Ltd.
OA Round
1 (Non-Final)
77%
Grant Probability
Favorable
1-2
OA Rounds
2y 11m
To Grant
99%
With Interview

Examiner Intelligence

Grants 77% — above average
77%
Career Allow Rate
226 granted / 293 resolved
+19.1% vs TC avg
Strong +28% interview lift
Without
With
+28.1%
Interview Lift
resolved cases with interview
Typical timeline
2y 11m
Avg Prosecution
28 currently pending
Career history
321
Total Applications
across all art units

Statute-Specific Performance

§101
15.4%
-24.6% vs TC avg
§103
45.8%
+5.8% vs TC avg
§102
11.8%
-28.2% vs TC avg
§112
17.1%
-22.9% vs TC avg
Black line = Tech Center average estimate • Based on career data from 293 resolved cases

Office Action

§102 §103 §112
DETAILED ACTION Claims 1-10 have been examined and are rejected. 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 . Information Disclosure Statement The information disclosure statement filed 10/08/2024 fails to comply with 37 CFR 1.98(a)(2), which requires a legible copy of each cited foreign patent document; each non-patent literature publication or that portion which caused it to be listed; and all other information or that portion which caused it to be listed. Specifically, no copy of the document “John Roach, "Mesh for Microsoft Teams aims to make collaboration in the ‘metaverse’ personal and fun" https://news.microsoft.com/source/features/innovation/mesh-for-microsoft-teams/, November 2, 2021, pages 12” (Cite No. 1 under “NON-PATENT LITERATURE DOCUMENTS”) has been filed. Therefore, the reference indicated by Cite No. 1 under “NON-PATENT LITERATURE DOCUMENTS” is not considered by the Examiner. Claim Interpretation The following is a quotation of 35 U.S.C. 112(f): (f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof. The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph: An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof. The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked. As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph: (A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function; (B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and (C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function. Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function. Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function. Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are: “event management apparatus” in line 6 of claim 1. Although claim 1 recites that the event management apparatus includes a first circuitry, the first circuitry is only configured to generate an event participation notification and transmit the notification. The first circuitry is not configured to manage information related to the predetermined event. Therefore, the limitation “event management apparatus” in line 6 of claim 1 is being interpreted under 35 U.S.C. 112(f). This claim interpretation may be overcome by amending to claim to recite “an event management apparatus includes a circuitry configured to manage information related to…” Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof. A review of the specification shows that the following appears to be the corresponding structure described in the specification for the 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph limitation: "one or more processors is included in an event management apparatus” (see page 2, lines 22-23 of the specification as filed). If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. Claim Rejections - 35 USC § 112 The following is a quotation of 35 U.S.C. 112(b): (b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention. The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph: The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention. Claims 1-10 rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention. Claims 1, 4, 5, 9 and 10 recite the limitation “the other communication terminal”, which renders the claims indefinite. There is insufficient antecedent basis for the limitation “the other communication terminal” in claims 1, 9 and 10. It is unclear what “the other communication terminal” refers to. This rejection may be overcome by replacing the limitation “the other communication terminal” with the limitation “the another communication terminal”. Dependent claims 2-8 fail to remedy the deficiency of claim 1 and are rejected. 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. Claims 1-2 and 7-10 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Chen et al. (U.S. PGPub 2024/0235870). Regarding claims 1 and 9-10, Chen teaches An event management system comprising: a first communication terminal located in a physical space and to be used for executing a predetermined event; a second communication terminal to be used for executing the predetermined event via a virtual space; and (Chen, see fig. 2; see paragraph 0041 a video conference provider 210 provides video conferencing functionality to various client devices 220-250...include two conventional computing devices 220-230, dedicated equipment for a video conference room 240...video conference provider 210 uses one or more real-time media servers 212, one or more network services servers 214, one or more video room gateways 216...provide access to and participation in one or more video conference meetings...; the examiner notes that although Chen teaches the entire limitation, the limitation following the phrase "to be used for" ("to be used for executing a predetermined event" and "to be used for executing the predetermined event via a virtual space") merely indicates intended use and therefore, no patentable weight is given to such limitations.) an event management apparatus to manage information related to the predetermined event in a case where the predetermined event is executed using the first communication terminal and the second communication terminal, (Chen, see figs. 2 and 4-6; see paragraph 0041 a video conference provider 210 provides video conferencing functionality to various client devices 220-250...include two conventional computing devices 220-230, dedicated equipment for a video conference room 240...video conference provider 210 uses one or more real-time media servers 212, one or more network services servers 214, one or more video room gateways 216...provide access to and participation in one or more video conference meetings...; see paragraphs 0100-0101 where during a virtual meeting based on an example event template is provided...include a roster 602 of video streams received from client devices joined to the virtual meeting. For example, the roster 602 may include video streams of participants 604a-604e received from the client devices 340a-340e during a virtual meeting hosted by the video conference provider 310) wherein the event management apparatus includes first circuitry configured to: generate an event participation notification after one communication terminal of the first communication terminal and the second communication terminal performs processing of participating in the predetermined event, (Chen, see figs. 6-8; see paragraph 0049 these servers 214 provide administrative functionality to enable client devices to create or participate in meetings, send meeting invitations…; see paragraph 0066 generate a meeting invitation and request the video conference provider 310 to transmit the meeting invitation to client devices on an associated invitation list...) the event participation notification being a notification prompting another communication terminal of the first communication terminal and the second communication terminal to participate in the predetermined event, the other communication terminal being a communication terminal that is scheduled to participate in and does not participate in the predetermined event yet; and (Chen, see figs. 6-8; see paragraph 0049 these servers 214 provide administrative functionality to enable client devices to create or participate in meetings, send meeting invitations…; see paragraph 0066 generate a meeting invitation and request the video conference provider 310 to transmit the meeting invitation to client devices on an associated invitation list...) transmit the generated event participation notification to the other communication terminal. (Chen, see figs. 6-8; see paragraph 0049 these servers 214 provide administrative functionality to enable client devices to create or participate in meetings, send meeting invitations…; see paragraph 0066 generate a meeting invitation and request the video conference provider 310 to transmit the meeting invitation to client devices on an associated invitation list...; see paragraph 0066 a meeting invitation may be generated and transmitting to participants on an invitation list.) Regarding claim 2, Chen teaches wherein the first circuitry generates the event participation notification, based on a participation date and time of participation of the one communication terminal of the first communication terminal and the second communication terminal in the predetermined event. (Chen, see fig. 4 date and time; see paragraph 0052 schedule a meeting, the user (anonymous or authenticated) may select an option to schedule a new meeting and may then select various meeting options, such as the date and time for the meeting...; see paragraph 0066 a meeting invitation may be generated and transmitting to participants on an invitation list.; see paragraph 0080 select a date and time for the virtual event... auto-populate based on a time slot selected by the user at the invitation) Regarding claim 7, Chen teaches wherein the first circuitry of the event management apparatus is further configured to: execute processing of participating in the predetermined event based on a request from the first communication terminal, for one of a schedule associated with the first communication terminal and a schedule associated with a user who participates in the predetermined event executed in the physical space; and (Chen, see fig. 4 display calendar; see paragraph 0073 calendar panel 400 for creating an event template…; see paragraph 0078 user may schedule an event 412 directly from the calendar 408. To schedule a new event, the user may select a desired time slot...using a cursor 422 at a desired time slot and be prompted with an option...creation of a meeting invitation...) execute processing of participating in the predetermined event based on a request from the second communication terminal, for one of a schedule associated with the second communication terminal, a schedule associated with a user who participates in the predetermined event executed in the virtual space, and (Chen, see fig. 4 display calendar; see paragraph 0073 calendar panel 400 for creating an event template…; see paragraph 0078 user may schedule an event 412 directly from the calendar 408. To schedule a new event, the user may select a desired time slot...using a cursor 422 at a desired time slot and be prompted with an option...creation of a meeting invitation...; see paragraph 0079 option 424 into which a user can input participant's names to be included on a participant invitation list. For example, a user may input a participant's name, email address, or tag.) a schedule represented by the predetermined event being executed. (Chen, see fig. 4 display calendar; see paragraph 0073 calendar panel 400 for creating an event template…; see paragraph 0078 user may schedule an event 412 directly from the calendar 408. To schedule a new event, the user may select a desired time slot...using a cursor 422 at a desired time slot and be prompted with an option...creation of a meeting invitation...) Regarding claim 8, Chen teaches wherein the predetermined event includes a conference, a meeting, a lecture, and a class conducted in the physical space and the virtual space in a same time slot. (Chen, see fig. 4 display calendar; see paragraph 0073 calendar panel 400 for creating an event template…; see paragraph 0078 user may schedule an event 412 directly from the calendar 408. To schedule a new event, the user may select a desired time slot...using a cursor 422 at a desired time slot and be prompted with an option...creation of a meeting invitation...; see paragraph 0019 an event creator that manages a band's virtual event calendar may generate an event template to be used for the band's public concerts. Since each of the public concerts will be hosted as a virtual event, having similar content (e.g., live-streaming of a concert), the event creator may generate an event template for these events) Claim Rejections - 35 USC § 103 The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claims 3 and 6 are rejected under 35 U.S.C. 103 as being unpatentable over Chen in view of Soneda et al. (U.S. PGPub 2019/0013956). Regarding claim 3, Chen teaches all of the features of claim 1. However, Chen does not explicitly teach wherein the first circuitry generates, as the event participation notification, a notification including an event name representing the predetermined event being executed and a name of a participant participating in the predetermined event. Soneda teaches wherein the first circuitry generates, as the event participation notification, a notification including an event name representing the predetermined event being executed and a name of a participant participating in the predetermined event. (Soneda, see fig. 11; see paragraph 0112 transmits, to the management system 50, a pub request including a topic name “Roster/userB” indicating messages for the user “b” and a message “Invite” for inviting the user “b” to the conference (step S61)…; see paragraph 0058 each topic name indicating a topic, a user name and right information indicating whether a user has a publication (pub) right or a subscription (sub) right for the topic.; see also paragraph 0005) It would have been obvious to one of ordinary skill in the art, at the time the invention was filed, to combine Chen and Soneda to provide the technique of generating, as the event participation notification, a notification including an event name representing the predetermined event being executed and a name of a participant participating in the predetermined event of Soneda in the system of Chen in order to authorize a second user to perform publication and subscription for a topic (Soneda, see abstract). Regarding claim 6, Chen teaches wherein the first circuitry of the event management apparatus is further configured to register user identification information and participation date and time information in association with each other, (Chen, see fig. 4 display calendar; see paragraph 0073 calendar panel 400 for creating an event template…; see paragraph 0078 user may schedule an event 412 directly from the calendar 408. To schedule a new event, the user may select a desired time slot...using a cursor 422 at a desired time slot and be prompted with an option...creation of a meeting invitation...; see paragraph 0079 option 424 into which a user can input participant's names to be included on a participant invitation list. For example, a user may input a participant's name, email address, or tag.) the request being transmitted from the first communication terminal, the participation date and time information indicating a participation date and time of participation of the first communication terminal in the predetermined event. (Chen, see figs. 6-8; see paragraph 0049 these servers 214 provide administrative functionality to enable client devices to create or participate in meetings, send meeting invitations…; see paragraph 0066 generate a meeting invitation and request the video conference provider 310 to transmit the meeting invitation to client devices on an associated invitation list...; see paragraph 0066 a meeting invitation may be generated and transmitting to participants on an invitation list.; see paragraph 0026-0027 the video conference provider 110 may prompt the user for certain information, such as a date, time, and duration for the meeting... the user may distribute the meeting information to one or more users to invite them to the meeting ) However, Chen does not explicitly teach the user identification information being included in a request to participate in the predetermined event, Soneda teaches the user identification information being included in a request to participate in the predetermined event, (Soneda, see fig. 11; see paragraph 0112 transmits, to the management system 50, a pub request including a topic name “Roster/userB” indicating messages for the user “b” and a message “Invite” for inviting the user “b” to the conference (step S61)…; see paragraph 0058 each topic name indicating a topic, a user name and right information indicating whether a user has a publication (pub) right or a subscription (sub) right for the topic.; see also paragraph 0005) It would have been obvious to one of ordinary skill in the art, at the time the invention was filed, to combine Chen and Soneda to provide the technique of the user identification information being included in a request to participate in the predetermined event of Soneda in the system of Chen in order to authorize a second user to perform publication and subscription for a topic (Soneda, see abstract). Claims 4-5 are rejected under 35 U.S.C. 103 as being unpatentable over Chen in view of Kim et al. (U.S. PGPub 2021/0194835). Regarding claim 4, Chen teaches wherein the other communication terminal, of the first communication terminal and the second communication terminal, to which the event participation notification is transmitted, (Chen, see figs. 6-8; see paragraph 0049 these servers 214 provide administrative functionality to enable client devices to create or participate in meetings, send meeting invitations…; see paragraph 0066 generate a meeting invitation and request the video conference provider 310 to transmit the meeting invitation to client devices on an associated invitation list...; see paragraph 0066 a meeting invitation may be generated and transmitting to participants on an invitation list.) However, Chen does not explicitly teach includes second circuitry configured to: receive the event participation notification transmitted from the event management apparatus; and control a display to display the received event participation notification. Kim teaches includes second circuitry configured to: receive the event participation notification transmitted from the event management apparatus; and control a display to display the received event participation notification. (Kim, see figs. 8-9 and 14; see paragraph 0135 the user may check the contents of the invitation message displayed on the display of the user terminal and then determine whether or not to participate in the group event. For example, the user may decide to accept to participate, decline to participate, or to remain undecided. In response to the user accepting the invitation message, at S1430) It would have been obvious to one of ordinary skill in the art, at the time the invention was filed, to combine Chen and Kim to provide the technique of receive the event participation notification transmitted from the event management apparatus and control a display to display the received event participation notification of Kim in the system of Chen in order to avoid wasting time unnecessarily because the user has to wait for all people to participate or try to call or broadcast again at a different time (Kim, see paragraph 0004). Regarding claim 5, Chen-Kim teaches wherein the second circuitry controls the display to display, as the event participation notification, a dialog to be operated on the other communication terminal of the first communication terminal and the second communication terminal by a user of the other communication terminal of the first communication terminal and the second communication terminal. (Chen, see fig. 4 display calendar; see paragraph 0073 calendar panel 400 for creating an event template…; see paragraph 0078 user may schedule an event 412 directly from the calendar 408. To schedule a new event, the user may select a desired time slot...using a cursor 422 at a desired time slot and be prompted with an option...creation of a meeting invitation...) Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. This includes: U.S. PGPub 2020/0358628, which describes methods related to hosting and management of virtual meetings; U.S. PGPub 2023/0138534, which describes methods and systems for a webinar backstage; and U.S. PGPub 2020/0294000, which describes live meeting information in a calendar view. Any inquiry concerning this communication or earlier communications from the examiner should be directed to MENG VANG whose telephone number is (571)270-7023. The examiner can normally be reached M-F 8AM-2PM, 3PM-5PM. 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 TAYLOR can be reached at (571) 272-3889. 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. /MENG VANG/Primary Examiner, Art Unit 2443
Read full office action

Prosecution Timeline

Oct 08, 2024
Application Filed
Feb 21, 2026
Non-Final Rejection — §102, §103, §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12602478
MALWARE MONITORING AND DETECTION
2y 5m to grant Granted Apr 14, 2026
Patent 12592834
SYSTEM AND METHOD FOR GENERATING A DIGITAL CERTIFICATE FOR A USER USING A DECENTRALIZED BLOCKCHAIN
2y 5m to grant Granted Mar 31, 2026
Patent 12592841
ACTIVE-ACTIVE REPLICATION IN BLOCKCHAIN TABLES WITH PRIMARY KEY CONSTRAINTS
2y 5m to grant Granted Mar 31, 2026
Patent 12586395
CREATING MACHINE LEARNING MODELS FOR DETECTING THE APPLICATION OF SPECIFIC DEEPFAKE TOOLS
2y 5m to grant Granted Mar 24, 2026
Patent 12587446
MANAGING NETWORK DEVICE CONFIGURATIONS BASED ON CONFIGURATION FRAGMENTS
2y 5m to grant Granted Mar 24, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

Get an AI-powered prosecution strategy using examiner precedents, rejection analysis, and claim mapping.
Powered by AI — typically takes 5-10 seconds

Prosecution Projections

1-2
Expected OA Rounds
77%
Grant Probability
99%
With Interview (+28.1%)
2y 11m
Median Time to Grant
Low
PTA Risk
Based on 293 resolved cases by this examiner. Grant probability derived from career allow rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month