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 § 101
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claim 18 is rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter.
Claim 18 is directed to a “system” which is referring to software or database. Thus, system in claim 18 is limited to is directed to software per se, therefore, it not based on the following statutory categories: e.g., process, machine, etc.
In order to overcome the 35 USC 101 rejection, set forth above in claim 18, applicant is suggested to include recitation of a “storage” and a “processor” into the claim limitation.
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.
Claim(s) 1-19 is/are rejected under 35 U.S.C. 102 as being anticipated by Moy US 20240330608
1. A method for servicing a communication from an originating entity, the method comprising the actions of:
receiving a communication initiation at a telecommunications network component, the communication initiation being sent from an originating entity and comprising a unique identifier, which is associated with the originating entity, and a destination entity identifier (Moy: fig. 3, 37-38 [0086, 0411-0432] - For example, user 1 3801 may place an outbound call to a phone number on the platform 3800 or is called by the platform 3800 to its device phone number 3804, and establish a call with user 3 3812 which get called on its Viber social application running on the device 3815, with real-time interpreting of their speech Language C. Devices may have video between them);
parsing the communication initiation at the telecommunications network component (Moy: fig. 3, 30-31, 37-38 [0086, 0411-0432] - For example, associating a language to the user's device phone number, social application profile ID, application login ID, or SIP (*) user name);
detecting the unique identifier in the communication initiation at the telecommunications network component (Moy: fig. 3, 37-38 [0086-0099, 0370, 0411-0432] - For example, to detect the language from the speech recognition transcripts, [0372] By associating a language to a specific recognized voice using voice recognition/voice biometrics, [0373] By associating a language to the user's device phone number, social application profile ID, application login ID, or SIP (*) user name);
the telecommunications network component providing the communication initiation, based at least in part on the unique identifier, to a communications platform (Moy: fig. 3, 37-38 [0086-0099, 0411-0432] - A [312] call leg is established between that telephony 311 device and the conference 302, with [313] audio in to that telephony device 311 and [314] audio out from that telephony device 311. [315] Audio from user 1 is forwarded to user 2);
the communication platform identifying the source of the communication initiation and the destination entity of the communication (Moy: fig. 3, 37-38 [0086-0099, 0411-0432] - A [312] call leg is established between that telephony 311 device and the conference 302, with [313] audio in to that telephony device 311 and [314] audio out from that telephony device 311. [315] Audio from user 1 is forwarded to user 2…);
the communication platform establishing a communication channel between the originating entity and the destination entity (Moy: fig. 3, 37-38 [0086-0099, 0411-0432] - Audio from user 1 is also forwarded to [318] WebSocket 1. WebSocket 1 transmits only the audio from user 1 and not from any other audio source);
subsequently to establishing the communication channel: in response to receiving a communication transmission from the originating entity for the destination entity, the communication platform performing any conversion necessary for the destination entity to understand the communication transmission from the originating entity (Moy: fig. 3, 37-38 [0086-0100, 0411-0432] - The connector and translation modules forward to the orchestration application 300 a [323] transcript of user 1 speech in language A, a [324] transcript of user 2 speech in language B, a [325] translation of user 1 speech into language B, and a [326] translation of user 2 speech into language A);
in response to receiving a communication transmission from the destination entity to the originating entity, the communication platform performing any conversion necessary for the originating entity to understand the communication transmission from the destination entity (Moy: fig. 3, 37-38 [0086-0100, 0411-0432] - The connector and translation modules forward to the orchestration application 300 a [323] transcript of user 1 speech in language A, a [324] transcript of user 2 speech in language B, a [325] translation of user 1 speech into language B, and a [326] translation of user 2 speech into language A); and
the communication platform routing the translated communication transmissions between the originating entity and the destination entity (Moy: fig. 3, 37-38 [0086-0105, 0411-0432] - The resulting Text-to-Speech audio translation in language B is played to both [339] user 2 and [340] user 1. The resulting Text-to-Speech audio translation in language A is played to both [341] user 1 and [342] user 2).
2. The method of claim 1, wherein parsing the communication at the telecommunications network component comprises recognizing by the telecommunications network component that the unique identifier is one that is serviced by the communications platform (Moy: fig. 3, fig. 30-31, 37-38 [0086, 0359-0364, 0411-0432] - For example, associating a language to the user's device phone number, social application profile ID, application login ID, or SIP (*) user name).
3. The method of claim 1, wherein the telecommunications network component is included within the communications platform and the action of providing the communication initiation to the communications platform comprises passing the communications initiation to the communications platform (Moy: fig. 3, 37-38 [0411-0432] - The voice core platform 3700 is handling calls to/from a proxy number [3720] which is dedicated to user 1 3702. The automated real-time speech components 3701 are connected [3718] to the voice platform 3700).
4. The method of claim 3, wherein the action of the communication platform establishing a communication channel between the originating entity and the destination entity comprises establishing a first leg of the communication channel between the communication platform and the destination entity and establishing a second leg of the communication channel between the communication platform and the originating entity (Moy: fig. 3, 37-38 [0095-0096] - establishment of [306] [312] call legs with both users).
5. The method of claim 4, wherein the action of establishing the first leg of the communication channel between the communication platform and the destination entity comprises using a telecommunications technology compatible with the destination entity (Moy: fig. 3, 37-38 [0095-0096] - establishment of [306] [312] call legs with both users).
6. The method of claim 4, wherein the action establishing the second leg of the communication channel between the communication platform and the destination entity comprises using a telecommunications technology compatible with the originating entity (Moy: fig. 3, 37-38 [0095-0096] - establishment of [306] [312] call legs with both users).
7. The method of claim 4, further comprising the communication platform entering the communication transmission into an archive for a user associated with the originating entity (Moy: fig. 30-31 [0359-0364] - Known Languages Selection).
8. The method of claim 1, wherein the telecommunications network component is communicatively coupled to the telecommunications network component over a telecommunications network and the action of providing the communication initiation to the communications platform comprises transmitting the communications initiation to the communications platform (Moy: fig. 3, 37-38).
9. The method of claim 8, wherein the action of the communication platform establishing a communication channel between the originating entity and the destination entity comprises establishing a first leg of the communication channel between the communication platform and the destination entity and establishing a second leg of the communication channel between the communication platform and the originating entity (Moy: fig. 3, 37-38 [0095-0096] - establishment of [306] [312] call legs with both users).
10. The method of claim 9, wherein the action of establishing the first leg of the communication channel between the communication platform and the destination entity comprises using a telecommunications technology compatible with the destination entity (Moy: fig. 3, 37-38 [0095-0096] - establishment of [306] [312] call legs with both users).
11. The method of claim 10, wherein the action establishing the second leg of the communication channel between the communication platform and the destination comprises using a telecommunications technology compatible with the originating entity (Moy: fig. 3, 37-38 [0095-0096] - establishment of [306] [312] call legs with both users).
12. The method of claim 8, further comprising the communication platform entering the communication transmission into an archive for a user associated with the originating entity (Moy: fig. 30-31 [0359-0364] - Known Languages Selection).
13. The method of claim 1, wherein the originating entity can be any of a variety of end user devices (EUDs) (Moy: fig. 37-38, unit 3705, 3729).
14. The method of claim 1, wherein the destination entity can be any of a variety of end user devices (EUDs) (Moy: fig. 37-38, units 3709m 3713).
15. The method of claim 1, wherein the destination entity and the originating entity can be any of a variety of end user devices (EUDs) and the action of the communication platform establishing a communication channel between the originating entity and the destination entity comprises establishing a communication path to the destination entity EUD that is technically compatible with the destination entity EUD and a communication path to the originating entity EUD that is technically compatible with the originating entity EUD (Moy: fig. 37-38, units 3709m 3713).
16. The method of claim 15, wherein at least one of the destination entity EUD and the originating entity EUD is a video conferencing application and the action of establishing the communication path includes establishing a communication path that can carry video and audio to/from the destination entity EUD and/or the originating entity EUD (Moy: fig. 37-38, units 3709m 3713).
17. The method of claim 15, wherein at least one of the destination entity EUD and the originating entity EUD is a messaging application and the action of establishing the communication path includes establishing a communication path that can carry text messages to/from the destination entity EUD and/or the originating entity EUD (Moy: fig. 37-38, units 3709-3713 “SMS” TTS).
19. The system of claim 18, wherein the plurality of interfaces comprises two or more interfaces selected from a group of interfaces comprising: an application program interface to a messaging service; an interface to a social messaging platform; an interface to a Customer Relationship Management (CRM) system; an interface to an enterprise collaboration system; and an interface to a private branch exchange system (Moy: fig. 37-38, [0424-0425] units 3709-3713 device 3803 running an application which can support either or a combination of: [0425] Phone number as phone number 1 3804, [0426] Social app user ID 1 3805, examples of social user ID are Viber number, Whatsapp number, Facebook ID, [0427] SIP user name 3806, when using SIP phones, SIP applications such as softphones, [0428] Login profile 1 3807, application defined, when for example using a WebRTC based native mobile application, web application, or desktop application).
Claim Rejections - 35 USC § 103
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 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.
Claim(s) 20 is/are rejected under 35 U.S.C. 103 as being unpatentable over Moy US 20240330608 in view of Onusko US 20210160208
20. The system of claim 19, wherein the plurality of interfaces comprises an interface to an archival system and the communications platform is configured to store a history of the translated communication transmissions from and to the originating entity (Moy: fig. 37-38, units 3709-3713 “SMS” TTS).
Moy merely discloses the term “to store history”
Onusko further teaches the term communications platform is configured to store a history of the translated communication transmissions from and to the originating entity (Onusko: fig. 1-3 [0078, 0171] unified context-aware content archive 112 may be managed by storage management module 210 - cloud computing system)
Thus, it would have been obvious to one skill in the art before the effective filing date of the claim invention to include the above recited limitation into Moy’s invention in order to allow users to review communications stored in unified context-aware content archive, as taught by Onusko.
Regarding claims 18), the independent claim and each dependent claim are related to the same limitation set for hereinabove in claims 1, where the difference used is a “system” and the wordings of the claims were interchanged within the claim itself or some of the claims were presented as a combination of two or more previously presented limitations. This change does not affect the limitation of the above treated claims. Adding these phrases to the claims and interchanging the wording did not introduce new limitations to these claims. Therefore, these claims were rejected for similar reasons as stated above.
Remark:
The examiner stresses that the claims are too broad and require detail or specialization of the steps as recited in the claims. Alone and as claimed, the limitations are too open.
Examiner has cited particular portions of the references as applied to each claim limitation for the convenience of the applicant. Although the specified citations are representative of the teachings of the art and are applied to the specific limitations within the individual claim, other passages and figures may apply as well. It is respectfully requested from the applicant in preparing responses, to fully consider the references in entirety as potentially teaching all or part of the claimed invention, as well as the context of the passage as taught by the prior art or disclosed by the Examiner.
In addition, an interview could expedite the prosecution.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Sulaiman Nooristany whose telephone number is (571) 270-1929. The examiner can normally be reached on M-F from 9 to 5. 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. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free).
/SULAIMAN NOORISTANY/Primary Examiner, Art Unit 2415
Prosecution Insights