US10321099B2 - Software, systems, and methods for video recording of a transaction involving protected data - Google Patents
Software, systems, and methods for video recording of a transaction involving protected data Download PDFInfo
- Publication number
- US10321099B2 US10321099B2 US15/889,671 US201815889671A US10321099B2 US 10321099 B2 US10321099 B2 US 10321099B2 US 201815889671 A US201815889671 A US 201815889671A US 10321099 B2 US10321099 B2 US 10321099B2
- Authority
- US
- United States
- Prior art keywords
- video
- scene
- video camera
- recording
- data storage
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/18—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
- H04N7/181—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast for receiving images from a plurality of remote sources
Definitions
- video capture systems may ultimately serve several purposes, including the capture of transactions and other events for video analysis related to the operation of the business, the identification of perpetrators of crimes committed at the place of business, and the deterrence of potential criminal activities on the premises.
- the types of business locations employing such video capture systems include, but are not limited to, grocery stores, department stores, and automated teller machines (ATMs).
- Embodiments disclosed herein provide software, systems, and methods for recording a scene encompassing a transaction.
- the scene is recorded to a data storage system using a first video camera capable of capturing protected data associated with the transaction. While recording the scene using the first video camera, in response to a first timing trigger, the recording of the scene is continued using a second video camera not capable of capturing the protected data. While then recording the scene using the second video camera, and in response to receiving a second timing trigger, the recording of the scene is continued using the first video camera.
- the first and second timing triggers are initiated based on at least one event associated with the transaction.
- FIG. 1 illustrates a video capture system according to an embodiment of the invention
- FIG. 2 illustrates a method of operating a video capture system according to an embodiment of the invention
- FIG. 3 illustrates a data storage system according to an embodiment of the invention
- FIG. 4A illustrates a video file stored in video data storage in the data storage system of FIG. 3 according to an embodiment of the invention.
- FIG. 4B illustrates video files stored in video data storage in the data storage system of FIG. 3 according to another embodiment of the invention.
- FIG. 1 illustrates a video capture system 100 according to one embodiment.
- the video capture system 100 includes at least a first video camera 106 A and a second video camera 106 B, each of which provide video data to a data storage system 108 . While the cameras 106 A, 106 B and the data storage system 108 are depicted as three separate components, other arrangements involving greater or fewer components may be employed in other implementations of the video capture system 100 while retaining the characteristics and functionality of the video capture system 100 described below.
- the video cameras 106 A, 108 A are oriented to capture a scene 102 generally occurring within a predetermined location or area at which one or more transactions 104 make occur.
- the scene 102 may be an area employed for point-of-sale (POS) transactions, such as a cash register or self-service product purchase scanning terminal.
- POS point-of-sale
- ATM automated teller machine
- Other examples of scenes 102 in which a transaction 104 may occur may be employed in other implementations.
- the execution of the transaction 104 may involve the exposure or other indication of “protected data” that a party to the transaction 104 may desire to protect from public disclosure.
- protected data may include, but are not limited to, credit card numbers, license driver numbers, Social Security numbers, personal identification numbers (PINs), home addresses, phone numbers, birthdates, signatures, images of family members, and other personal information, including combinations thereof.
- PINs personal identification numbers
- protected data may be easily captured as video data. For example, a video camera capturing a transaction may provide enough resolution to capture data residing on a credit card, driver's license, or personal check.
- such a camera may also clearly record keypad entries by a customer or employee, such as PINs and other codes.
- Storage and/or transmission of various forms of protected data may not only be counter to the wishes of the customer or business owner, but may be prohibited or limited by applicable laws.
- the video cameras 106 A, 106 B do not provide the same level or type of coverage of the scene 100 .
- the first video camera 106 A may be configured to capture at least one item of protected data during the transaction 104
- the second video camera 106 B may be configured to provide at least some viewing coverage of the scene 102 without capturing the protected data of the transaction 104 .
- the first video camera 106 A may provide an overhead view of a POS area, whereby at least some aspect of the transaction 104 involving protected data may be captured, whereas the second video camera 106 B may be positioned to capture the same scene 102 , but from a different angle not capable of capturing protected data involved in the transaction 104 .
- the two cameras 106 A, 106 B may provide similar viewing angles of the scene 102 , but only the first camera 106 A may provide the zoom and/or resolution capability to capture protected data.
- the first video camera 106 A may be a high-definition camera
- the second video camera 106 B may be a standard-definition camera.
- Other differences between the configurations of the first video camera 106 A and the second video camera 106 B may be employed to result in the differing data capturing abilities between the two cameras 106 A, 106 B.
- more than two such cameras 106 A, 106 B may be employed to provide multiple views of the scene 102 , with at least one of the cameras being arranged such that capture of protected data is not possible.
- each of cameras 106 A, 106 B comprise digital video compression or encoding circuitry and software.
- a compression or encoding technique, of second video camera 106 B could preclude capturing protected data involved in the transaction 104 due to increased noise or video artifacts of the compression technique as compared to a compression or encoding technique of first video camera 106 A.
- a method 200 of operating a video capture system such as the video capture system 100 of FIG. 1 , is presented in FIG. 2 .
- the scene 102 is recorded using the first video camera 106 A capable of capturing protected data associated with the transaction 104 (operation 202 ). While the scene 102 is being recorded using the first video camera 106 A, and in response to a first timing trigger, the recording is continued using the second video camera 106 B incapable of capturing the protected data (operation 204 ). Thereafter, while the scene 102 is being recorded using the second video camera 106 B, the recording is continued using the first video camera 106 A in response to a second timing trigger (operation 206 ).
- the first and second timing triggers are initiated based on at least one event associated with the transaction 104 .
- video data captured by the first video camera 106 A during at least one time period of the transaction 104 may contain a view of protected data involved in the transaction 104 .
- Such video is effectively replaced or substituted by video data captured via the second video camera 106 B.
- replacement or substitution may occur while the video data from the cameras 106 A, 106 B are being recorded in the data storage system 108 , or while the video data are being transferred from the data storage system 108 to another destination.
- the first and second timing triggers are based on at least one event or activity associated with the transaction 104 .
- the first timing trigger may occur in response to an action by a customer or employee, such as the swiping of a credit card in a card reader.
- the first timing trigger may be generated in response to a customer approaching or entering a predefined area of the scene 102 , such as an area surrounding the card reader.
- audio or speech detection may be employed to determine whether protected data is about to be presented. For example, an employee requesting a particular action of a customer, such as asking the customer to present a credit card, or to type a PIN into a keypad, that signals the forthcoming protected data may cause initiation of the first timing trigger. In another instance, an employee requesting personal information, such as an address or phone number, may initiate the first timing trigger. Other actions or events involving the transaction 104 may be employed to generate the first timing trigger in other implementations.
- the second timing trigger may be generated by any single event, or combination of events, involving the transaction 104 .
- the customer involved in the transaction 104 leaving a particular area such as the area in front of a card reader, may initiate the second timing trigger.
- the completion of the transaction 104 such as the generation or printing of a receipt, or completion of an authorization to charge a bank or credit account, may be employed as the initiating event for the second timing trigger.
- audio or speech processing may be employed to detect parting comments by either the employee or customer that are typically associated with the completion of the transaction 104 , thus initiating the second timing trigger.
- Other actions by either employee or customer may be utilized in other implementations to generate one or both of the timing triggers.
- the second timing trigger may be generated based upon a timing delay after the first timing trigger.
- a delay may be a set period of time after which the initiation of the transaction 104 , such as a credit card swipe through a card reader, may initiate a delay of a predetermined period of time, such as thirty seconds or one minute, before generating the second timing trigger.
- Other initiating events, as well as other timing delays, may be employed in other embodiments.
- transaction 104 is processed through or payment made by a mobile device, tablet, or smart phone of a customer, such as in a near-field communication (NFC) transaction.
- the first or second timing triggers may be responsive to operation of the mobile device, such as responsive to initiation and termination of the near-field communications, or from a signal generated by the scanning device or wireless point-of-sale device of the store.
- FIG. 3 depicts a data storage system 300 as a possible example of the data storage system 108 of FIG. 1 , although the data storage system 100 may utilize alternative configurations.
- the data storage system 300 of FIG. 3 includes a communication interface 301 , a user interface 302 , a processing system 303 , and video data storage 307 .
- the processing system 303 is linked to the communication interface 301 and the user interface 302 .
- the processing system 403 includes control circuitry 304 and at least one memory device 305 that stores operating software 306 .
- the communication interface 301 includes one or more components that communicate over communication links, such as network cards, ports, radio frequency (RF) transceivers, processing circuitry and software, or some other communication devices.
- the communication interface 301 may be configured to communicate over metallic, wireless, or optical links.
- the communication interface 301 may be configured to use time-division multiplexing (TDM), Internet Protocol (IP), Ethernet, optical networking, wireless protocols, communication signaling, or some other communication format, including combinations thereof.
- TDM time-division multiplexing
- IP Internet Protocol
- Ethernet optical networking
- wireless protocols communication signaling
- communication signaling or some other communication format, including combinations thereof.
- the communication interface 301 is configured to receive video data from a plurality of video cameras, as well as to transfer the received video data to a destination system, such as a financial establishment or law enforcement agency.
- the communication interface 301 may also receive event information, such as proximity information, data related to a credit card swipe or authorization, or other information related to the transaction to generate the timing triggers noted above.
- the user interface 302 includes components that interact with a user.
- the user interface 302 may include a keyboard, display screen, mouse, touch pad, or some other user input/output apparatus.
- the user interface 302 may be omitted from the data storage system 300 in some examples.
- the video data storage 307 may be any type of volatile or nonvolatile data storage component or system, including, but not limited to, a magnetic or optical disk drive, static or dynamic random access memory (RAM), solid state memory, or flash memory.
- video data storage 307 comprises a computer-readable, non-transitory memory.
- the control circuitry 304 includes, for example, a microprocessor and/or other circuitry that retrieves and executes operating software 306 from the memory device 305 .
- the memory device 305 includes a disk drive, flash drive, data storage circuitry, solid state memory, or some other computer-readable, non-transitory memory apparatus.
- the operating software 306 contains computer programs, firmware, or some other form of machine-readable processing instructions.
- the operating software 306 may include an operating system, utilities, drivers, network interfaces, applications, or some other type of software. When executed by the control circuitry 304 , the operating software 306 directs the processing system 303 to operate the data storage system 300 as described herein.
- the operating software 306 directs the processing system 303 in one embodiment to provide a video recording in which protected data associated with a transaction is not captured or represented in the recording, as described above in relation to the method 200 of FIG. 2 .
- FIG. 4A presents an example of such a recording, embodied as a video file 401 stored within the video data storage 307 of the data storage system 300 depicted in FIG. 3 .
- the video file 401 contains video data which does not capture or otherwise indicate protected data. More specifically, in the video file 401 , a portion of first camera data 404 A of the video file 401 received from the first video camera 106 A is replaced with second camera data 404 B received from the second video camera 106 B. As described above, the beginning and ending points of the portion of the first camera data 404 A substituted by the second camera data 404 B may be indicated by way of the first and second timing triggers discussed above.
- the processing system 303 of the data storage system 300 may store the first camera data 404 A being received from the first video camera 106 A into the video file 401 until the processing system 303 generates or detects the first timing trigger based upon one or more events associated with the transaction 104 . In response to the first timing trigger, the processing system 303 then continues writing to the video file 401 using the second camera data 404 B currently being received from the second video camera 106 B, thus ceasing or suspending the transfer of the first camera data 404 A to the file 401 A.
- the generation or reception of the second timing trigger in the processing system 303 then causes the processing system 303 to cease or suspend transferring the second camera data 404 B being received from the second video camera 104 B, and to resume recording of the first camera data 404 A currently being received from the first video camera 10 B to the video file 401 .
- the processing system 303 is capable of generating the video file 401 free from the inclusion of any protected data “on-the-fly” as the first camera data 404 A and the second camera data 404 B are being streamed to the data storage system 300 from the cameras 406 A, 106 B.
- Such an implementation may preclude the storage of any protected data, although separate recording of the portion of the first camera data 404 A substituted by the second camera data 404 B into another video file (not shown in FIG. 4A ) is possible in other embodiments.
- FIG. 4B provides another example of the video data storage 307 in which two separate video files 401 A, 401 B are recorded: one file 401 A for the first camera data 404 A received from the first video camera 106 A, and another file 401 B to store the second camera data 404 B received from the second video camera 106 B.
- all of the video data from both cameras 106 A, 106 B, including video data representing or revealing protected data captured by the first video camera 106 A are stored in the video data storage 307 .
- a first timing trigger value 402 A for the first timing trigger and a second timing trigger value 402 B for the second timing trigger.
- the trigger values 402 A, 402 B represent time values, such as timestamps embedded within the first camera data 404 A and the second camera data 404 B, that indicate the starting time and ending time of a portion of the first camera data 404 A which is to be substituted with the corresponding portion of the second camera data 404 B.
- a video file (such as the video file 401 of FIG.
- the resulting mixed video file may be stored in the video data storage 307 for subsequent transfer and/or analysis.
- both the first camera data 404 A and the second camera data 404 B may be accessed for future reference.
- Such an implementation may be useful, for example, in situations in which a federal agency interested in the financial aspects of the transaction 104 may desire access to the protected data captured in the first camera data 404 A, while other parties, such as local law enforcement, may request access to a view of the scene 102 without unnecessarily viewing any protected data.
- both edited and unedited versions of a video file containing the first camera data 404 A may be stored in the video data storage 307 .
- the processing system 303 may process such a video file to prevent unauthorized access to that video data, such as by way of encoding or encrypting the video files carrying the protected data.
- the resulting encoded or encrypted video file may then be stored safely over the long term in the data storage system 300 , or transmitted therefrom to other destination systems.
- processing system 303 may transfer a first portion of video file 401 A until indicated by the first timing trigger value.
- processing system 303 may suspend transfer of the first portion of video file 401 A and transfer a first portion of video file 401 B until indicated by the second timing trigger value.
- the first portion of video file 401 B would be transferred in the place of portions of video file 401 A.
- processing system 303 may then transfer a second portion of video file 401 A and ceasing transfer of video file 401 B.
- the portions of the various video files could be determined by the first and second timing trigger values, such as timestamps, frame numbers, or other values.
Abstract
Description
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/889,671 US10321099B2 (en) | 2010-11-18 | 2018-02-06 | Software, systems, and methods for video recording of a transaction involving protected data |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US41534010P | 2010-11-18 | 2010-11-18 | |
US13/293,782 US9930295B2 (en) | 2010-11-18 | 2011-11-10 | Software, systems, and methods for video recording of a transaction involving protected data |
US15/889,671 US10321099B2 (en) | 2010-11-18 | 2018-02-06 | Software, systems, and methods for video recording of a transaction involving protected data |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/293,782 Continuation US9930295B2 (en) | 2010-11-18 | 2011-11-10 | Software, systems, and methods for video recording of a transaction involving protected data |
Publications (2)
Publication Number | Publication Date |
---|---|
US20180234666A1 US20180234666A1 (en) | 2018-08-16 |
US10321099B2 true US10321099B2 (en) | 2019-06-11 |
Family
ID=46064026
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/293,782 Active 2035-01-16 US9930295B2 (en) | 2010-11-18 | 2011-11-10 | Software, systems, and methods for video recording of a transaction involving protected data |
US15/889,671 Active US10321099B2 (en) | 2010-11-18 | 2018-02-06 | Software, systems, and methods for video recording of a transaction involving protected data |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/293,782 Active 2035-01-16 US9930295B2 (en) | 2010-11-18 | 2011-11-10 | Software, systems, and methods for video recording of a transaction involving protected data |
Country Status (2)
Country | Link |
---|---|
US (2) | US9930295B2 (en) |
CN (1) | CN102780867A (en) |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
NZ563215A (en) * | 2007-11-06 | 2009-03-31 | Zenith Asset Man Ltd | A method of monitoring product identification and apparatus therefor |
WO2014144882A1 (en) * | 2013-03-15 | 2014-09-18 | E-Connect | Visual analysis of transactions |
US9645860B2 (en) * | 2013-09-06 | 2017-05-09 | Microsoft Technology Licensing, Llc | Verification that particular information is transferred by an application |
US9432627B2 (en) | 2013-09-06 | 2016-08-30 | Microsoft Technology Licensing, Llc | Restricting information requested by an application |
US9438868B2 (en) * | 2014-02-13 | 2016-09-06 | Semiconductor Components Industries, Llc | Adaptive image sensor systems and methods |
CN104239145B (en) * | 2014-09-28 | 2017-10-27 | 北京奇艺世纪科技有限公司 | A kind of data consistency control method and device based on case mechanism |
US10409621B2 (en) | 2014-10-20 | 2019-09-10 | Taser International, Inc. | Systems and methods for distributed control |
US10192277B2 (en) | 2015-07-14 | 2019-01-29 | Axon Enterprise, Inc. | Systems and methods for generating an audit trail for auditable devices |
CN106131471A (en) * | 2016-07-18 | 2016-11-16 | 四川君逸易视科技有限公司 | Financing monitor based on intelligent video technology |
CN110032882A (en) * | 2018-12-29 | 2019-07-19 | 阿里巴巴集团控股有限公司 | Card method and apparatus are deposited based on block chain |
CN111428080B (en) * | 2019-04-25 | 2024-02-27 | 杭州海康威视数字技术股份有限公司 | Video file storage method, video file search method and video file storage device |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030048202A1 (en) | 2001-09-10 | 2003-03-13 | Michael Francois | Cockpit image recording system |
US20040135885A1 (en) | 2002-10-16 | 2004-07-15 | George Hage | Non-intrusive sensor and method |
US20050128314A1 (en) | 2003-12-10 | 2005-06-16 | Canon Kabushiki Kaisha | Image-taking apparatus and image-taking system |
US20070107029A1 (en) | 2000-11-17 | 2007-05-10 | E-Watch Inc. | Multiple Video Display Configurations & Bandwidth Conservation Scheme for Transmitting Video Over a Network |
-
2011
- 2011-11-10 US US13/293,782 patent/US9930295B2/en active Active
- 2011-11-18 CN CN2011103836187A patent/CN102780867A/en active Pending
-
2018
- 2018-02-06 US US15/889,671 patent/US10321099B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070107029A1 (en) | 2000-11-17 | 2007-05-10 | E-Watch Inc. | Multiple Video Display Configurations & Bandwidth Conservation Scheme for Transmitting Video Over a Network |
US20030048202A1 (en) | 2001-09-10 | 2003-03-13 | Michael Francois | Cockpit image recording system |
US20040135885A1 (en) | 2002-10-16 | 2004-07-15 | George Hage | Non-intrusive sensor and method |
US20050128314A1 (en) | 2003-12-10 | 2005-06-16 | Canon Kabushiki Kaisha | Image-taking apparatus and image-taking system |
Non-Patent Citations (1)
Title |
---|
"Bang Preceded Tower Crash," Mutual Press Clipping Service Inc., Apr. 7, 1991, 1 page. |
Also Published As
Publication number | Publication date |
---|---|
US9930295B2 (en) | 2018-03-27 |
CN102780867A (en) | 2012-11-14 |
US20120127315A1 (en) | 2012-05-24 |
US20180234666A1 (en) | 2018-08-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10321099B2 (en) | Software, systems, and methods for video recording of a transaction involving protected data | |
US11669819B2 (en) | Automatic storage of electronic receipts across merchants and transaction cards | |
US10032170B2 (en) | Multi factor authentication rule-based intelligent bank cards | |
US10185961B2 (en) | Geotagged image for checking validity of purchase transaction | |
US20040024709A1 (en) | System and method for determining the identity of a party associated with a transaction | |
US20040177046A1 (en) | Credit card protection system | |
CN104574052B (en) | The method of payment and system of authentication are carried out based on 3D line holographic projections | |
JP5865550B1 (en) | Card verification system, card unauthorized use detection method, and card unauthorized use detection program | |
US10706477B1 (en) | Augmented reality account statement | |
US10475014B1 (en) | Payment device security | |
US20140025577A1 (en) | System and method for secure transactions utilizing passive near-field communications devices | |
WO2017032056A1 (en) | Point-of-sale-based cash-out determining method and apparatus | |
US11823536B1 (en) | Gesture flagging for advanced security | |
US20070168295A1 (en) | Verification method for personal credit purchases | |
US9846982B2 (en) | Document geometric deformation watermarking and tracking | |
EP3879478A1 (en) | A method, computer program and apparatus | |
KR20160087946A (en) | Mobile terminal and method for processing record data interworked with bill counting apparatus | |
CN113570448A (en) | Data processing method, equipment and medium in electronic warehouse elementary substance escort pledge | |
KR101115608B1 (en) | Financial settlement admission service apparatus and method for preventing and controlling credit card selling of fraud franchisee | |
KR20210066219A (en) | Method for processing dutch pay transaction using face recognition and server thereof | |
JP7116610B2 (en) | Transaction management system and transaction management method | |
US20180089689A1 (en) | Dedicated payment terminal for mitigating instances of card holder fraud using image capture and method | |
US7930390B2 (en) | Identification method | |
KR100877014B1 (en) | Automatic teller machine | |
US10748132B2 (en) | Security tool |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: VERINT AMERICAS INC., GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VERINT SYSTEMS INC.;REEL/FRAME:047362/0434 Effective date: 20160129 Owner name: VERINT SYSTEMS INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HEIER, KURT;WACHMAN, ERAN;SIGNING DATES FROM 20120127 TO 20120131;REEL/FRAME:047361/0932 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:VERINT AMERICAS INC.;REEL/FRAME:050612/0972 Effective date: 20190929 |
|
AS | Assignment |
Owner name: COGNYTE SOFTWARE LTD., ISRAEL Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VERINT AMERICAS INC.;REEL/FRAME:057569/0475 Effective date: 20210201 |
|
AS | Assignment |
Owner name: COGNYTE TECHNOLOGIES ISRAEL LTD, ISRAEL Free format text: CHANGE OF NAME;ASSIGNOR:VERINT SYSTEMS LTD.;REEL/FRAME:060751/0532 Effective date: 20201116 |
|
AS | Assignment |
Owner name: COGNYTE TECHNOLOGIES ISRAEL LTD, ISRAEL Free format text: CHANGE OF NAME;ASSIGNOR:VERINT SYSTEMS LTD.;REEL/FRAME:059710/0742 Effective date: 20201116 |
|
AS | Assignment |
Owner name: COGNYTE SOFTWARE LTD. (AS SUCCESSOR-IN-INTEREST TO VERINT AMERICAS INC.), ISRAEL Free format text: NOTICE OF PARTIAL TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:061686/0755 Effective date: 20221014 |
|
AS | Assignment |
Owner name: COGNYTE TECHNOLOGIES ISRAEL LTD, ISRAEL Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:COGNYTE SOFTWARE LTD.;REEL/FRAME:061675/0724 Effective date: 20221026 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |