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 .
DETAILED ACTION
1. This action is responsive to: an original application filed on 3 October 2024.
2. Claims 1-20 are currently pending and claims 1, 10 and 19 are independent claims.
Information Disclosure Statement
3. No IDS filed.
Priority
4. Priority date claimed has been noted.
Drawings
5. The drawings filed on 3 October 2024 are accepted by the examiner.
Claim Rejections - 35 USC § 103
6. 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 1-20 are rejected under 35 U.S.C §103 as being unpatentable over Wajs et al. (US Publication No. 20170228525), hereinafter Wajs and in view of Song et al. (CN Publication No. CN 112434327), hereinafter Song.
Regarding claim 1:
accessing, via a first user device, a first secure application (Wajs, ¶5-7), wherein, the method comprises the first software application interfacing with the interfacing application to thereby cause the interfacing application to access the secured software application.
receiving, via the first secure application, a data set, wherein the data set includes at least one of text data, image data, video data, or audio data (Wajs, ¶112, ¶140) an API may be used to enable the first software application 530 to effectively interface with the media player 625. The media player 625 may be configured to receive DRM-protected content with and/or without an accompanying DRM license/certificate and DRM protected contents are image, video and audio.
Wajs does not explicitly suggest, determining, via a first application server associated with the first secure application, a content element associated with the data set, wherein the content element includes sensitive information; however, in a same field of endeavor Song discloses this limitation (Song, abstract)
generating, via the first application server, media based on the sensitive information, wherein the media is encrypted to include digital rights management (“DRM”) protection (Wajs, ¶117), wherein The secured software code may be configured to generate or select content to be DRM-protected, and to encrypt the content, thereby generating the DRM-encrypted content. The content may be encrypted using a whitebox encryption module. Data associated with the DRM client (e.g. a public key or DRM client ID) may be used in encrypting the content
transmitting, to a second secure application associated with a second user device, the media (Wajs, ¶175, ¶249, ¶202), wherein sending DRM-protected content to the media player application to thereby cause the media player application to access the DRM client so as to enable rendering of the content on the computing device.
and causing to output the media via a graphical user interface (“GUI”) associated with the second user device (Wajs, ¶76, ¶58), wherein The DRM client 410 also enables the media player 420 to securely render the content (e.g. audio and video).
It would have been obvious to one of ordinary skill in the art at the time the invention was filed to include the method transmission of DRM based content of Wajs with the method protecting sensitive information disclosed in Song to ensure that the sensitive information cannot be obtained by means of screenshot or screen-recording, stated by Song at abstract.
Regarding claim 2:
further comprising accessing, via the first user device, the first secure application via a first data transmission application (Wajs, ¶8).
Regarding claim 3:
wherein the first secure application is embedded in the first data transmission application and the second secure application is embedded in a second data transmission application (Wajs, ¶3).
Regarding claim 4:
wherein receiving the data set further comprises: receiving, via a GUI associated with the first user device, a natural language prompt, wherein the natural language prompt is input by a first user as a user input; and transmitting, to the first application server, the natural language prompt (Wajs, ¶142).
Regarding claim 5:
wherein receiving the data set further comprises: accessing, via the first application server, a data storage application; requesting, via the first application server, the data set from the data storage application; and transmitting, to the first application server, the data set from the data storage application (Wajs, ¶3).
Regarding claim 6:
wherein causing to output the media via the GUI associated with the second user device further comprises: determining, via a second application server associated with the second secure application, whether an indication of digital extraction is present; and upon determining via the second application server the indication of digital extraction is not present, causing to output the media via the GUI associated with the second user device (Wajs, ¶108).
Regarding claim 7:
further comprising: determining, via a second application server associated with the second secure application, whether an indication of digital extraction is present; upon determining via the second application server the indication of digital extraction is present, modifying the media to generate a modified media, wherein the media is modified such that the sensitive information substantially not visible; and causing to output the modified media via the GUI associated with the second user device (Wajs, ¶104, ¶12).
Regarding claim 8:
further comprising: upon determining via the second application server the indication of digital extraction is present, generating a first alert via the second application server; transmitting the first alert to the first secure application; and causing to output the first alert via a GUI associated with the first secure application (Wajs, ¶180).
Regarding claim 9:
further comprising: upon determining via the second application server the indication of digital extraction is present, generating a second alert; transmitting the second alert to a DRM-protection system; and causing to output the second alert via a GUI associated with the DRM-protection system (Wajs, ¶180
Regarding claim 10:
at least one memory storing instructions (Wajs, ¶269); and at least one processor operatively connected to the memory, and configured to execute the instructions to perform operations for dynamically securing transmitted data, the operations including (Wajs, ¶269):
accessing, via a first user device, a first secure application (Wajs, ¶5-7), wherein, the method comprises the first software application interfacing with the interfacing application to thereby cause the interfacing application to access the secured software application.
receiving, via the first secure application, a data set, wherein the data set includes at least one of text data, image data, video data, or audio data (Wajs, ¶112, ¶140) an API may be used to enable the first software application 530 to effectively interface with the media player 625. The media player 625 may be configured to receive DRM-protected content with and/or without an accompanying DRM license/certificate and DRM protected contents are image, video and audio.
Wajs does not explicitly suggest, determining, via a first application server associated with the first secure application, a content element associated with the data set, wherein the content element includes sensitive information; however, in a same field of endeavor Song discloses this limitation (Song, abstract)
generating, via the first application server, media based on the sensitive information, wherein the media is encrypted to include digital rights management (“DRM”) protection (Wajs, ¶117), wherein The secured software code may be configured to generate or select content to be DRM-protected, and to encrypt the content, thereby generating the DRM-encrypted content. The content may be encrypted using a whitebox encryption module. Data associated with the DRM client (e.g. a public key or DRM client ID) may be used in encrypting the content
transmitting, to a second secure application associated with a second user device, the media (Wajs, ¶175, ¶249, ¶202), wherein sending DRM-protected content to the media player application to thereby cause the media player application to access the DRM client so as to enable rendering of the content on the computing device.
and causing to output the media via a graphical user interface (“GUI”) associated with the second user device (Wajs, ¶76, ¶58), wherein The DRM client 410 also enables the media player 420 to securely render the content (e.g. audio and video).
It would have been obvious to one of ordinary skill in the art at the time the invention was filed to include the method transmission of DRM based content of Wajs with the method protecting sensitive information disclosed in Song to ensure that the sensitive information cannot be obtained by means of screenshot or screen-recording, stated by Song at abstract.
Regarding claim 11:
wherein the operations further include accessing, via the first user device, the first secure application via a first data transmission application (Wajs, ¶8).
Regarding claim 12:
wherein the first secure application is embedded in the first data transmission application and the second secure application is embedded in a second data transmission application (Wajs, ¶3).
Regarding claim 13:
wherein receiving the data set further comprises: receiving, via a GUI associated with the first user device, a natural language prompt, wherein the natural language prompt is input by a first user as a user input; and transmitting, to the first application server, the natural language prompt (Wajs, ¶142).
Regarding claim 14:
wherein receiving the data set further comprises: accessing, via the first application server, a data storage application; requesting, via the first application server, the data set from the data storage application; and transmitting, to the first application server, the data set from the data storage application (Wajs, ¶3).
Regarding claim 15:
wherein causing to output the media via the GUI associated with the second user device further comprises: determining, via a second application server associated with the second secure application, whether an indication of digital extraction is present; and upon determining via the second application server the indication of digital extraction is not present, causing to output the media via the GUI associated with the second user device (Wajs, ¶108).
Regarding claim 16:
wherein the operations further include: determining, via a second application server associated with the second secure application, whether an indication of digital extraction is present; upon determining via the second application server the indication of digital extraction is present, modifying the media to generate a modified media, wherein the media is modified such that the sensitive information substantially not visible; and causing to output the modified media via the graphical user interface (“GUI”) associated with the second user device (Wajs, ¶12, ¶104).
Regarding claim 17:
wherein the operations further include: upon determining the indication of digital extraction is present, generating a first alert via the second application server; transmitting the first alert to the first secure application; and causing to output the first alert via a GUI associated with the first secure application (Wajs, ¶180).
Regarding claim 18:
wherein the operations further include: upon determining via the second application server the indication of digital extraction is present, generating a second alert; transmitting the second alert to a DRM-protection system; and causing to output the second alert via a GUI associated with the DRM-protection system (Wajs, ¶180).
Regarding claim 19:
accessing, via a first user device, a first secure application via a first data transmission application, wherein the first secure application is embedded in the first data transmission application (Wajs, ¶5-7), wherein, the method comprises the first software application interfacing with the interfacing application to thereby cause the interfacing application to access the secured software application.
receiving, via the first secure application, a data set, wherein the data set includes at least one of text data, image data, video data, or audio data (Wajs, ¶112, ¶140) an API may be used to enable the first software application 530 to effectively interface with the media player 625. The media player 625 may be configured to receive DRM-protected content with and/or without an accompanying DRM license/certificate and DRM protected contents are image, video and audio.
Wajs does not explicitly suggest, determining, via a first application server associated with the first secure application, a content element associated with the data set, wherein the content element includes sensitive information; however, in a same field of endeavor Song discloses this limitation (Song, abstract)
generating, via the first application server, media based on the sensitive information, wherein the media is encrypted to include digital rights management (“DRM”) protection (Wajs, ¶117), wherein The secured software code may be configured to generate or select content to be DRM-protected, and to encrypt the content, thereby generating the DRM-encrypted content. The content may be encrypted using a whitebox encryption module. Data associated with the DRM client (e.g. a public key or DRM client ID) may be used in encrypting the content
transmitting, to a second secure application associated with a second user device, the media (Wajs, ¶175, ¶249, ¶202), wherein sending DRM-protected content to the media player application to thereby cause the media player application to access the DRM client so as to enable rendering of the content on the computing device.
determining, via a second application server associated with the second secure application, whether an indication of digital extraction is present, wherein the second secure application is embedded in a second data transmission application (Wajs, ¶76, ¶218), wherein obscuration techniques include reduced contrast, colour mapping, blurring, and similar techniques to prevent the barcode from being able to be scanned by the POS terminal.
and upon determining via the second application server the indication of digital extraction is not present (Wajs, ¶109), causing to output the media via a graphical user interface (“GUI”) associated with the second user device (Wajs, ¶76, ¶58), wherein The DRM client 410 also enables the media player 420 to securely render the content (e.g. audio and video.
It would have been obvious to one of ordinary skill in the art at the time the invention was filed to include the method transmission of DRM based content of Wajs with the method protecting sensitive information disclosed in Song to ensure that the sensitive information cannot be obtained by means of screenshot or screen-recording, stated by Song at abstract.
Regarding claim 20:
further comprising: determining, via a second application server associated with the second secure application, whether an indication of digital extraction is present; upon determining via the second application server the indication of digital extraction is present, modifying the media to generate a modified media, wherein the media is modified such that the sensitive information substantially not visible; and causing to output the modified media via a GUI associated with the second user device (Wajs, ¶12, ¶104).
Conclusion
7. The prior art made of record and not relied upon is considered pertinent to applicant’s disclosure. Any inquiry concerning this communication or earlier communications from the examiner should be directed to Monjour Rahim whose telephone number is (571)270-3890.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Shewaye Gelagay can be reached on 571-272-4219. 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 CANANDA) or 571-272-1000.
/Monjur Rahim/
Patent Examiner
United States Patent and Trademark Office
Art Unit: 2436; Phone: 571.270.3890
E-mail: monjur.rahim@uspto.gov
Fax: 571.270.4890
Prosecution Insights