WO2017015130A1 - Fourniture d'une sécurité de police de caractères - Google Patents

Fourniture d'une sécurité de police de caractères Download PDF

Info

Publication number
WO2017015130A1
WO2017015130A1 PCT/US2016/042544 US2016042544W WO2017015130A1 WO 2017015130 A1 WO2017015130 A1 WO 2017015130A1 US 2016042544 W US2016042544 W US 2016042544W WO 2017015130 A1 WO2017015130 A1 WO 2017015130A1
Authority
WO
WIPO (PCT)
Prior art keywords
font
monitor
computing device
activities
unauthorized activity
Prior art date
Application number
PCT/US2016/042544
Other languages
English (en)
Inventor
Nathan Ford
Soaurabh Kakkar
Hemant Sharma
Mukesh Kumar
Original Assignee
Monotype Imaging Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Monotype Imaging Inc. filed Critical Monotype Imaging Inc.
Publication of WO2017015130A1 publication Critical patent/WO2017015130A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/105—Arrangements for software license management or administration, e.g. for managing licenses at corporate level
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
    • G06F11/3096—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents wherein the means or processing minimize the use of computing system or of computing system component resources, e.g. non-intrusive monitoring which minimizes the probe effect: sniffing, intercepting, indirectly deriving the monitored data from other directly available data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/604—Tools and structures for managing or administering access control systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/16—Program or content traceability, e.g. by watermarking

Definitions

  • fonts e.g., provided during temporary trial periods, subscription periods, etc., from being compromised (e.g., copied, moved, etc.) in a prohibited manner.
  • corrective action can be quickly executed upon detection of improper activities.
  • other functionality may also be provided (e.g., sending alerts, identifying wrongful actors, logging unauthorized activities, etc.) to protect the fonts.
  • font distributors can protect font distributors from violations of entered agreement with font developers and other third parties.
  • a computing device implemented method includes, at a font monitor, receiving data representing one or more activities related to providing one or more fonts to the computing device from a font service provider. The method also includes identifying at least one of the one or more activities as being associated with an unauthorized activity, and, initiating action to correct the at least one activity associated with the unauthorized activity.
  • Implementations may include one or more of the following features.
  • the font monitor may operate in an independent manner at the computing device.
  • Initiating action to correct the at least one activity associated with an unauthorized activity may include halting a usage period of one or more fonts.
  • the font monitor may employ an application programming interface.
  • the font monitor may be configured to monitor communications between the computing device and a font service provider.
  • a system in another aspect, includes a computing device that includes a memory configured to store instructions of a font monitor.
  • the system also includes a processor to execute the instructions of the font monitor to perform operations that include receiving data representing one or more activities related to providing one or more fonts to the computing device from a font service provider.
  • Operations also include identifying at least one of the one or more activities as being associated with an unauthorized activity.
  • Operations also include initiating action to correct the at least one activity associated with the unauthorized activity.
  • Implementations may include one or more of the following features.
  • the font monitor may operate in an independent manner at the computing device.
  • Initiating action to correct the at least one activity associated with an unauthorized activity may include halting a usage period of one or more fonts.
  • the font monitor may employ an application programming interface.
  • the font monitor may be configured to monitor communications between the computing device and a font service provider.
  • one or more computer readable media storing instructions that are executable by a processing device, and upon such execution cause the processing device to perform operations that include, at a font monitor, receiving data representing one or more activities related to providing one or more fonts to the computing device from a font service provider. Operations also include identifying at least one of the one or more activities as being associated with an unauthorized activity. Operations also include initiating action to correct the at least one activity associated with the unauthorized activity.
  • Implementations may include one or more of the following features.
  • the font monitor may operate in an independent manner at the computing device.
  • Initiating action to correct the at least one activity associated with an unauthorized activity may include halting a usage period of one or more fonts.
  • the font monitor may employ an application programming interface.
  • the font monitor may be configured to monitor communications between the computing device and a font service provider.
  • FIG. 1 illustrates a font distribution environment.
  • FIG. 2 illustrates fonts provided to a computing device for use during a trial, subscription, etc. period.
  • FIG. 3 illustrates monitoring for prohibited font-related activities and responding to these activities.
  • FIGs. 4, 5, 6, 6A, 6B, and 7 are flowcharts of operations for monitoring font-related activities and taking appropriate corrective action.
  • FIG. 8 illustrates an example of a computing device and a mobile computing device that can be used to implement the techniques described here.
  • an environment 100 for distributing fonts to from a font service provider 102 to multiple computing devices (e.g., computer system 104 and 106, and a mobile smartphone 108).
  • the fonts are sent via a network (e.g., the Internet 110) and one or more protocols may be employed.
  • a user e.g., designer
  • a computing device e.g., computer system 104
  • the computing device can establish a connection with the font service provider 102 and thereby allow the user to view many candidate fonts for possible selection and use.
  • one or more fonts can be provided to the user for use during a trial period. Typically such periods of time are predefined and relatively short (e.g., a few minutes, etc.) and the fonts are to be considered temporary (e.g., the fonts will be removed from the device after the trial period).
  • software being used to review and investigate these temporary fonts may provide a vehicle for improperly attaining a copy of the fonts.
  • an application executed by the computer system 104 such as an publication application (for developing electronic publications), word processor and other types of applications capable of testing a candidate font (e.g., review how certain content presents in a font) can be an unwitting accomplice in the wrongful taking of the font.
  • an application executed by the computer system 104 such as an publication application (for developing electronic publications), word processor and other types of applications capable of testing a candidate font (e.g., review how certain content presents in a font) can be an unwitting accomplice in the wrongful taking of the font.
  • an application executed by the computer system 104 such as an publication application (for developing electronic publications), word processor and other types of applications capable of testing a candidate font (e.g., review how certain content presents in a font) can be an unwitting accomplice in the wrongful taking of the font.
  • an unwitting accomplice in the wrongful taking of the font can be
  • FIG 2 components of the computer system 104 and the font service provider 102 are illustrated that assist with detecting improper font-related activities and taking corrective action.
  • a font file 202 is delivered to the computer system 104 from the font service provider 102.
  • a font manager 204 is executed by a server 206 located at the font service provider 102, in this example.
  • the font manager 204 Along with gathering the font data from sources internal (e.g., storage device 208) and/or external (e.g., remotely located storage devices, etc.) to the font service provider 102, the font manager 204 also controls, maintains, etc. the trial periods that the provided fonts can be used by the computer system. Subscription periods may also be controlled by the font manager 204. With this information determined, the font file 202 (e.g., that includes font data) is delivered to the computer system 104 from the font service provider 102.
  • the delivered font data (e.g., that represents the candidate fonts for use during the trial period) is stored at a particular location in memory 210 of the computer system 104.
  • the location is labeled a font storage folder 212 that is accessible by an operating system 214 executed by the computer system 104.
  • a local application 216 is executed by the computer system 104 to present potential candidate fonts, initiate the sending of the font request 200 to the font service provider 102, and assist the user with investigating the candidate fonts after being placed in the font storage folder 212.
  • the font application 216 may register the font(s) (provided by the received font data) at the storage location (e.g., the font storage folder 212).
  • a font monitor 218 is also executed by the computer system 104.
  • the font monitor 218 is separate from the font application 216; however, in some arrangements a portion or the entire functionality of the font monitor 218 may be incorporated into the font application 216.
  • Other architectures e.g., software, hardware, software/hardware architectures
  • the font monitor is capable of detecting one or more prohibited activities involving the temporary fonts included in the font storage folder 212. For example, unauthorized copying, moving, etc.
  • the font monitor 2118 is capable of detecting an attempt to improperly store one temporary font (or more) in a portion of the memory 210 (labeled folder 213).
  • Such illicit operations may be initiated by a user, an application being executed by the computer system 104, a combination of user and application operations, etc.
  • the probability of violating a license agreement (or potential license agreement) between the user and the font service provider, the font service provider and a developer of the temporary font, etc. may be significantly reduced.
  • a data flow 300 graphically represents techniques for detecting improper operations (represented with arrow 304) regarding one or more fonts 302 in the font storage folder 212.
  • One such improper operation could be the moving of one or more of the fonts 302 from the font storage folder 212 to another location of the computer system (e.g., folder 213).
  • Such improper operations may be initiated by various types of actors. For example, a user (e.g., designer) may initiate the operation. Applications or other types of software may also initiate unauthorized activities; for example, a publication application (e.g., electronic document development application) may include packaging functionality that can attempt to move, copy, etc. font data (e.g., embed font(s) within an application, file, etc.).
  • modifications to a folder could be considered an improper operation involving the stored fonts (e.g., trial fonts, subscription fonts, etc.).
  • modifications to permissions, immutability, etc. of a folder e.g., the font storage folder 212
  • the font monitor 218 is capable of detecting a variety of events indicative of an improper operation being attempted.
  • the font monitor 218 may monitor information (e.g., signals, data, etc.) being provided by the operating system 214 of the computer system 104.
  • some types of detectable events associated with improper operations include notifications of mounting, unmounting, etc., of storage devices internal to the computer system (e.g., hard drives), extemal to the system (e.g., pen drives (also known as flash memory sticks)), etc. Detection events may also include indications that files, folders, etc., are being created, modified, etc.
  • the font monitor 218 is aware of acceptable events that should not trigger corrective action. For example, file operations of the font application 216 may be identified as acceptable activities (e.g., creating or modifying files, folders, etc.). For activities deemed improper, corrective action(s) 308 may be initiated by the font monitor 218 as graphically illustrated with arrow 310.
  • One or more techniques may be employed by the font monitor 218 to receive information from the operating system 214 along with other possible sources.
  • application programming interfaces API's
  • routines, protocols, etc. can be utilized by the font monitor 218 to get data that represents a variety of file system events.
  • data provided by the operating system 214 to the font monitor 218 can detect if a file, folder, etc. has been created, modified, etc. in the computer system or in any attached device (e.g., external hard drive, pen drive, etc.).
  • the font monitor is typically alerted in fractions of a second by the employed techniques (e.g., a call back technique).
  • Other types of events detectable by the font monitor 218 include status indicators. For example, if the communication link between the font service provider 102 and the computer system 104 is no longer active (e.g., a user has logged out of an established connection with a service provider), action may be taken such that trial fonts, subscription fonts, etc. may be removed from the font storage folder 212. Changes to relationships may also be detected and trigger corrective action. For example, if a related account with font service provider 102 is no longer active, suspended, etc., the user may be banned from future font trial periods, subscriptions, etc. and corrective action is initiated.
  • corrective actions 308 may be initiated based upon the event(s) detected by the font monitor 218. For example, trial fonts, subscription fonts, etc. may be deleted from the font storage folder 212 to halt any further use of the fonts (e.g., the fonts are deleted due to the ending of a trial period, subscription period, etc.). If the copying, moving, etc. of fonts (from the font storage folder 212) has been detected, corrective action 308 may include the deleting of the copied versions of the fonts (in some cases, along with deleting the original versions of the fonts). In a similar manner, upon the detection of a file, folder, etc. being created, modified, etc.
  • the font monitor 218 may initiate corrective action.
  • the file, folder, etc. may be identified and included for being monitored (by the font monitor 218).
  • corrective action may be initiated (e.g., delete the copied version of the font data, delete the file, folder, etc.). So, based upon a file, folder, etc. being created, modified, moved, etc. the unauthorized new copy of can be deleted.
  • one or more techniques may be used by the font monitor 218; for example, a call back technique may be used to take such corrective action.
  • Other types of corrective action may also be employed, for example, one or more alerts may be provided.
  • a visual, audible, etc. alert may be presented by the computer system 104. Logging, report generation, etc. may also be considered as corrective action.
  • the font monitor 218 may initiate operations to identify the party associated with the unauthorized activity (e.g., identify the user, the address of the computing device, etc.), generate a report that represents the unauthorized activity (e.g., type of activity, user identity, computing device identity, etc.), and initiate the sending of the report to one or more parties (e.g., to the font service provider 102 - for example to impose a penalty, to one or more font developers, etc.).
  • the frequency of such events may decrease.
  • a flowchart 400 represents some operations of a font monitor (e.g., the font monitor 218 shown in FIG. 2) being executed by a computing device (e.g., the computer system 104).
  • Operations of the font monitor 218 are typically executed by a single computing device (e.g., the computer system 104); however, operations may be executed by multiple computing devices.
  • the execution of operations may be distributed among two or more locations.
  • a portion of the operations may be executed by an application executed by the computer system (e.g., font application 216).
  • Operations of the font monitor may also be executed at two or more locations. For example, a portion of the operations may be executed at a font service provider (e.g., by the server 206), at an intermediate computing device (e.g., located between a user device and the font service provider), with one or more computing devices, etc.
  • operations can be considered as initial operations of the font monitor.
  • operations may include initiating 402 the file monitor (e.g., font monitor 218) and determining 404 if a trial period is active or if a subscription period is active. If such a trial period or subscription period is not active, the font monitor can wait until one or more becomes active. If such a trial period or subscription period is active, operations can include providing 406 restricted access and maintain immutability of font files, font folders, etc. for trial periods, subscription periods, etc. For example, corresponding fonts stored in the font storage folder 212 may be accessible with a valid trial period or subscription period being active. Further, during such time periods changes to font files, folders, etc. is generally prohibited to maintain font integrity.
  • Operations may also include monitoring 408 for volume mounting, unmounting, etc.
  • volume mounting, unmounting, etc. For example, mounting of storage devices internal to the local computing device, external to the device, etc. may eventually be involved with illicit activities such as attempts to copy, move, etc. temporary fonts (e.g., trial fonts, subscription fonts, etc.) to a location separate from the font storage folder.
  • the font monitor can receive notification (e.g., from the operating system). Once alerted, the font monitor can identify the one or more volumes, devices, etc. (associated with the mounting, unmounting, etc.) in a list of current volumes, devices, etc. to be monitored.
  • Operations may also include monitoring 410 the operating system for event, file, folder, etc. activities.
  • the font monitor may be provided information (e.g., signals) from the operating system that indicates that a file, folder, etc. is being created, modified, etc. Monitoring may include processing received information to determine which operations may be unauthorized or allowable. For example, received information can be processed (e.g., filtered) to identify events, font files, folders, etc. associated with a link (e.g., a communication link) between the font service provider and the computer system. In some arrangements, some information from the operating system may be filtered and not acted upon. For example, file, folder, etc. operations of an application associated with providing the fonts to the computer system (e.g., font application 216) may not be considered as indicating potentially unauthorized activity.
  • information e.g., signals
  • Monitoring may include processing received information to determine which operations may be unauthorized or allowable. For example, received information can be processed (e.g., filtered) to identify events, font files, folders, etc. associated with a link (e.g., a communication link) between the font
  • a flowchart 500 represents further operations of a font monitor (e.g., the font monitor 218 shown in FIG 2) to initiate corrective action based upon a detected event associated with unauthorized font operations. For example, upon detecting 502 that a service has halted (e.g., a user trial, subscription, etc. service has become unlinked by actions of the user, an executed application, etc.) corrective action can be initiated. Operations may include removing 504 fonts (e.g., trial fonts, subscription fonts, etc.) from the computing device (e.g., computer system 104). In some arrangements, the trial period, subscription period, etc. would be ended.
  • a service halted
  • the computing device e.g., computer system 104
  • monitoring is not halted upon the service being halted; however, in some arrangements monitoring may be halted (e.g., monitoring is halted when trial, subscription services are unlinked).
  • Flowchart 510 represents other operations that may be executed by the font monitor to initiate corrective action upon detecting an event.
  • operations may include halting 514 the monitoring by the font monitor.
  • the monitoring is halted for a short period of time (e.g., a fraction of a second). While halted, a list of volumes, drives, etc.
  • Flowchart 520 represents operations that may be executed based upon detecting 522 that an application used to provide candidate fonts (e.g., the font application 216) has been halted (e.g., a user, another application, etc. has ended the execution of the application).
  • an application used to provide candidate fonts e.g., the font application 216) has been halted (e.g., a user, another application, etc. has ended the execution of the application).
  • operations may include halting 524 service, for example, a logout operation can be executed to stop services (e.g., linked to, logged into, etc.). Operations may also include removing 526 one or more fonts (e.g., trial fonts, subscription fonts, etc.) from storage on the computing device (e.g., the font storage folder 212), and, halting 528 monitoring operations (of the font monitor).
  • halting 524 service for example, a logout operation can be executed to stop services (e.g., linked to, logged into, etc.).
  • Operations may also include removing 526 one or more fonts (e.g., trial fonts, subscription fonts, etc.) from storage on the computing device (e.g., the font storage folder 212), and, halting 528 monitoring operations (of the font monitor).
  • a flowchart 600 represents operations of a font monitor (e.g., the font monitor 218 shown in FIG 2) to initiate corrective action based upon a detected event in which a file, folder, etc. is being created, modified, etc.
  • operations include detecting 602 the file/folder being created, modified, etc. (e.g., on the user computing device, on an attached external device, etc.) during a trial period, subscription period, etc. when a font application is being executed.
  • operations include stepping 604 through to determine if any font file, folders, etc. associated with a font trial, subscription, etc. are involved in the creation, modification, etc. If such a font file, folder, etc.
  • operations may include imposing 606 access restrictions (e.g., same immutability /locking, access permission, etc.) as applied to other files, folders, etc. associated with a font trial, subscription, etc. (e.g., the font storage folder 212). If such a font file, folder, etc. is being created, operations may include deleting 608 the newly created font file, folder, etc. (e.g., at the new destination).
  • access permissions to font folders, font files, etc. is controlled to secure the related font information.
  • the flowchart also monitors the creating, modifying, etc. of created files, folders, etc. for improper activities associated with the provided fonts.
  • a flowchart 700 represents some operations of a font monitor (e.g., the font monitor 218 shown in FIG. 2) being executed by a computing device (e.g., the computer system 104).
  • operations of the font monitor are typically executed by a single computing device (e.g., the computer system 104); however, operations may be executed by multiple computing devices.
  • font monitor operations may be executed at a single site (e.g., a user's location), distributed among two or more locations, etc.
  • a portion of the operations may be executed by an application that is being executed by the computer system (e.g., font application 216).
  • Operations may also be executed at multiple locations; for example, a portion of the operations may be executed at a font service provider (e.g., by the server 206), at an intermediate computing device (e.g., located between a user device and the font service provider), at one or more computing devices, etc.
  • a font service provider e.g., by the server 206
  • an intermediate computing device e.g., located between a user device and the font service provider
  • Operations may include, at a font monitor, receiving 702 data representing one or more activities related to providing one or more fonts to the computing device from a font service provider.
  • received data may represent the current status of a subscription for one or more fonts being provided by a font service provider.
  • Received data may also be provided from other types of sources, for example, data from an operating system of a computing device may be provided to the font monitor.
  • Operations may also include identifying 704 one of the one or more activities as being associated with an unauthorized activity. For example, data from the operating system may indicate that a font file is being moved, copied, etc. in an authorized manner.
  • the received data may also indicate that the subscription status with a font service provider has changed (e.g., is no longer valid), for another example.
  • Operations may also include initiating action to correct the at least one activity associated with the unauthorized activity. For example, once detected, services from a font service provider may be halted, unauthorized file operations (e.g., copying, moving, etc.) may similarly be halted and any misappropriated data (e.g., copied font files) addressed (e.g., deleted) to maintain control of fonts from the font service provider.
  • unauthorized file operations e.g., copying, moving, etc.
  • any misappropriated data e.g., copied font files addressed (e.g., deleted) to maintain control of fonts from the font service provider.
  • FIG 8 shows an example of example computing device 800 and example mobile computing device 850, which can be used to implement the techniques described herein. For example, a portion or all of the operations of font monitor 218 (shown in FIG. 2) may be executed by the computing device 800 and/or the mobile computing device 850.
  • Computing device 800 is intended to represent various forms of digital computers, including, e.g., laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers.
  • Computing device 850 is intended to represent various forms of mobile devices, including, e.g., personal digital assistants, tablet computing devices, cellular telephones, smartphones, and other similar computing devices.
  • the components shown here, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the techniques described and/or claimed in this document.
  • Computing device 800 includes processor 802, memory 804, storage device 806, high-speed interface 808 connecting to memory 804 and high-speed expansion ports 810, and low speed interface 812 connecting to low speed bus 814 and storage device 806.
  • processor 802 can process instructions for execution within computing device 800, including instructions stored in memory 804 or on storage device 806 to display graphical data for a GUI on an external input/output device, including, e.g., display 816 coupled to high speed interface 808.
  • multiple processors and/or multiple busses can be used, as appropriate, along with multiple memories and types of memory.
  • multiple computing devices 800 can be connected, with each device providing portions of the necessary operations (e.g., as a server bank, a group of blade servers, or a multi-processor system).
  • Memory 804 stores data within computing device 800.
  • memory 804 is a volatile memory unit or units.
  • memory 804 is a non-volatile memory unit or units.
  • Memory 804 also can be another form of computer- readable medium (e.g., a magnetic or optical disk. Memory 804 may be non-transitory.)
  • Storage device 806 is capable of providing mass storage for computing device 800.
  • storage device 806 can be or contain a computer-readable medium (e.g., a floppy disk device, a hard disk device, an optical disk device, or a tape device, a flash memory or other similar solid state memory device, or an array of devices, such as devices in a storage area network or other configurations.)
  • a computer program product can be tangibly embodied in a data carrier.
  • the computer program product also can contain instructions that, when executed, perform one or more methods (e.g., those described above.)
  • the data carrier is a computer- or machine-readable medium, (e.g., memory 804, storage device 806, memory on processor 802, and the like.)
  • High-speed controller 808 manages bandwidth-intensive operations for computing device 1100, while low speed controller 812 manages lower bandwidth-intensive operations. Such allocation of functions is an example only.
  • high-speed controller 808 is coupled to memory 804, display 816 (e.g., through a graphics processor or accelerator), and to high-speed expansion ports 810, which can accept various expansion cards (not shown).
  • low-speed controller 812 is coupled to storage device 806 and low-speed expansion port 814.
  • the low-speed expansion port which can include various communication ports (e.g., USB, Bluetooth®, Ethernet, wireless Ethernet), can be coupled to one or more input/output devices, (e.g., a keyboard, a pointing device, a scanner, or a networking device including a switch or router, e.g., through a network adapter.)
  • input/output devices e.g., a keyboard, a pointing device, a scanner, or a networking device including a switch or router, e.g., through a network adapter.
  • Computing device 800 can be implemented in a number of different forms, as shown in the figure. For example, it can be implemented as standard server 820, or multiple times in a group of such servers. It also can be implemented as part of rack server system 824. In addition or as an alternative, it can be implemented in a personal computer (e.g., laptop computer 822.) In some examples, components from computing device 800 can be combined with other components in a mobile device (not shown), e.g., device 850. Each of such devices can contain one or more of computing device 800, 850, and an entire system can be made up of multiple computing devices 800, 850 communicating with each other.
  • Computing device 850 includes processor 852, memory 864, an input/output device (e.g., display 854, communication interface 866, and transceiver 868) among other components.
  • Device 850 also can be provided with a storage device, (e.g., a microdrive or other device) to provide additional storage.
  • a storage device e.g., a microdrive or other device.
  • Each of components 850, 852, 864, 854, 866, and 868, are interconnected using various buses, and several of the components can be mounted on a common motherboard or in other manners as appropriate.
  • Processor 852 can execute instructions within computing device 850, including instructions stored in memory 864.
  • the processor can be implemented as a chipset of chips that include separate and multiple analog and digital processors.
  • the processor can provide, for example, for coordination of the other components of device 850, e.g., control of user interfaces, applications run by device 850, and wireless communication by device 850.
  • Processor 852 can communicate with a user through control interface 858 and display interface 856 coupled to display 854.
  • Display 854 can be, for example, a TFT LCD (Thin- Film-Transistor Liquid Crystal Display) or an OLED (Organic Light Emitting Diode) display, or other appropriate display technology.
  • Display interface 856 can comprise appropriate circuitry for driving display 854 to present graphical and other data to a user.
  • Control interface 858 can receive commands from a user and convert them for submission to processor 852.
  • external interface 862 can communicate with processor 842, so as to enable near area communication of device 850 with other devices.
  • External interface 862 can provide, for example, for wired communication in some implementations, or for wireless communication in other implementations, and multiple interfaces also can be used.
  • Memory 864 stores data within computing device 850.
  • Memory 864 can be implemented as one or more of a computer-readable medium or media, a volatile memory unit or units, or a non-volatile memory unit or units.
  • Expansion memory 874 also can be provided and connected to device 850 through expansion interface 872, which can include, for example, a SIMM (Single In Line Memory Module) card interface.
  • SIMM Single In Line Memory Module
  • expansion memory 874 can provide extra storage space for device 850, or also can store applications or other data for device 850.
  • expansion memory 874 can include instructions to carry out or supplement the processes described above, and can include secure data also.
  • expansion memory 874 can be provided as a security module for device 850, and can be programmed with instructions that permit secure use of device 850.
  • secure applications can be provided through the SIMM cards, along with additional data, (e.g., placing identifying data on the SIMM card in a non-hackable manner.)
  • the memory can include, for example, flash memory and/or NVRAM memory, as discussed below.
  • a computer program product is tangibly embodied in a data carrier.
  • the computer program product contains instructions that, when executed, perform one or more methods, e.g., those described above.
  • the data carrier is a computer- or machine-readable medium (e.g., memory 864, expansion memory 874, and/or memory on processor 852), which can be received, for example, over transceiver 868 or external interface 862.
  • Device 850 can communicate wirelessly through communication interface 866, which can include digital signal processing circuitry where necessary. Communication interface 866 can provide for communications under various modes or protocols (e.g., GSM voice calls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.) Such communication can occur, for example, through radio-frequency transceiver 868. In addition, short-range communication can occur, e.g., using a Bluetooth®, WiFi, or other such transceiver (not shown). In addition, GPS (Global Positioning System) receiver module 870 can provide additional navigation- and location-related wireless data to device 850, which can be used as appropriate by applications running on device 850. Sensors and modules such as cameras, microphones, compasses, accelerators (for orientation sensing), etc. may be included in the device.
  • GPS Global Positioning System
  • Device 850 also can communicate audibly using audio codec 860, which can receive spoken data from a user and convert it to usable digital data. Audio codec 860 can likewise generate audible sound for a user, (e.g., through a speaker in a handset of device 850.) Such sound can include sound from voice telephone calls, can include recorded sound (e.g., voice messages, music files, and the like) and also can include sound generated by applications operating on device 850.
  • Audio codec 860 can receive spoken data from a user and convert it to usable digital data. Audio codec 860 can likewise generate audible sound for a user, (e.g., through a speaker in a handset of device 850.) Such sound can include sound from voice telephone calls, can include recorded sound (e.g., voice messages, music files, and the like) and also can include sound generated by applications operating on device 850.
  • Computing device 850 can be implemented in a number of different forms, as shown in the figure. For example, it can be implemented as cellular telephone 880. It also can be implemented as part of smartphone 882, a personal digital assistant, or other similar mobile device.
  • Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor.
  • the programmable processor can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.
  • machine-readable medium and computer-readable medium refer to a computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine- readable medium that receives machine instructions.
  • PLDs Programmable Logic Devices
  • the systems and techniques described here can be implemented on a computer having a device for displaying data to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor), and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer.
  • a device for displaying data to the user e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
  • a keyboard and a pointing device e.g., a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be a form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in a form, including acoustic, speech, or tactile input.
  • the systems and techniques described here can be implemented in a computing system that includes a backend component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a frontend component (e.g., a client computer having a user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or a combination of such back end, middleware, or frontend components.
  • the components of the system can be interconnected by a form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.
  • LAN local area network
  • WAN wide area network
  • the Internet the global information network
  • the computing system can include clients and servers.
  • a client and server are generally remote from each other and typically interact through a communication network.
  • the relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
  • the engines described herein can be separated, combined or incorporated into a single or combined engine.
  • the engines depicted in the figures are not intended to limit the systems described here to the software architectures shown in the figures.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Technology Law (AREA)
  • Multimedia (AREA)
  • Quality & Reliability (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mathematical Physics (AREA)
  • Document Processing Apparatus (AREA)
  • Controls And Circuits For Display Device (AREA)

Abstract

L'invention concerne un procédé mis en œuvre par un dispositif informatique qui consiste, au niveau d'un dispositif de surveillance de police de caractères, à recevoir des données représentant une ou plusieurs activité(s) associée(s) à la fourniture d'une ou plusieurs police(s) de caractères au dispositif informatique à partir d'un fournisseur de service de police de caractères. Le procédé consiste également à identifier au moins l'une desdites activités comme étant associée à une activité non autorisée, et à initier une action pour corriger la ou les activité(s) associée(s) à l'activité non autorisée.
PCT/US2016/042544 2015-07-17 2016-07-15 Fourniture d'une sécurité de police de caractères WO2017015130A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562193974P 2015-07-17 2015-07-17
US62/193,974 2015-07-17

Publications (1)

Publication Number Publication Date
WO2017015130A1 true WO2017015130A1 (fr) 2017-01-26

Family

ID=56550415

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/042544 WO2017015130A1 (fr) 2015-07-17 2016-07-15 Fourniture d'une sécurité de police de caractères

Country Status (2)

Country Link
US (1) US20170017778A1 (fr)
WO (1) WO2017015130A1 (fr)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8615709B2 (en) 2010-04-29 2013-12-24 Monotype Imaging Inc. Initiating font subsets
US20130215126A1 (en) * 2012-02-17 2013-08-22 Monotype Imaging Inc. Managing Font Distribution
US10115215B2 (en) 2015-04-17 2018-10-30 Monotype Imaging Inc. Pairing fonts for presentation
US11537262B1 (en) 2015-07-21 2022-12-27 Monotype Imaging Inc. Using attributes for font recommendations
EP3352095A1 (fr) * 2017-01-24 2018-07-25 Fujitsu Limited Système de données hiérarchiques dynamique
US11334750B2 (en) 2017-09-07 2022-05-17 Monotype Imaging Inc. Using attributes for predicting imagery performance
US10909429B2 (en) 2017-09-27 2021-02-02 Monotype Imaging Inc. Using attributes for identifying imagery for selection
US11657602B2 (en) 2017-10-30 2023-05-23 Monotype Imaging Inc. Font identification from imagery

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050149450A1 (en) * 1994-11-23 2005-07-07 Contentguard Holdings, Inc. System, method, and device for controlling distribution and use of digital works based on a usage rights grammar
US20060005256A1 (en) * 2004-06-18 2006-01-05 Red Hat, Inc. Apparatus and method for managing digital rights with arbitration
US20110203000A1 (en) * 2010-02-16 2011-08-18 Extensis Inc. Preventing unauthorized font linking
US20150178476A1 (en) * 2013-12-24 2015-06-25 Andrew Horton System and method of monitoring font usage

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7931820B2 (en) * 2000-09-07 2011-04-26 Daikin Industries, Ltd. Dry etching gas and method for dry etching
WO2002091146A2 (fr) * 2001-05-09 2002-11-14 Ecd Systems, Inc. Systemes et procedes pour empecher l'utilisation et la manipulation non autorisees de contenu numerique
US7315944B2 (en) * 2001-11-13 2008-01-01 Ericsson Inc. Secure handling of stored-value data objects
JP4469162B2 (ja) * 2003-11-18 2010-05-26 東北リコー株式会社 印刷装置の使用済みマスタ保護システム、印刷装置の使用済みマスタ保護方法及び印刷装置
US7698732B2 (en) * 2005-02-03 2010-04-13 International Business Machines Corporation Method and apparatus for exchanging information between computer systems from different computer networks
WO2006089109A2 (fr) * 2005-02-14 2006-08-24 Extensis Corporation Format et systemes destines a l'utilisation securisee de polices de caracteres electroniques

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050149450A1 (en) * 1994-11-23 2005-07-07 Contentguard Holdings, Inc. System, method, and device for controlling distribution and use of digital works based on a usage rights grammar
US20060005256A1 (en) * 2004-06-18 2006-01-05 Red Hat, Inc. Apparatus and method for managing digital rights with arbitration
US20110203000A1 (en) * 2010-02-16 2011-08-18 Extensis Inc. Preventing unauthorized font linking
US20150178476A1 (en) * 2013-12-24 2015-06-25 Andrew Horton System and method of monitoring font usage

Also Published As

Publication number Publication date
US20170017778A1 (en) 2017-01-19

Similar Documents

Publication Publication Date Title
US20170017778A1 (en) Providing Font Security
US10614233B2 (en) Managing access to documents with a file monitor
CN107636666B (zh) 用于控制对于计算设备上的应用的准许请求的方法和***
JP6151256B2 (ja) コンピューティングデバイス、作動方法及びコンピュータプログラム
US11544383B2 (en) Method for runtime mitigation of software and firmware code weaknesses
US8935755B1 (en) Managing permissions and capabilities of web applications and browser extensions based on install location
JP6464256B2 (ja) Ａｎｄｒｏｉｄアプリケーションのライフサイクルを変更することによって、コンテナ化ワークスペース環境内でアプリケーションの実行を管理する方法
US9760359B2 (en) Healthcare as a service—downloadable enterprise application
US20170243018A1 (en) Installation and management of client extensions
US9021592B2 (en) Source code analysis of inter-related code bases
US20150113242A1 (en) Restricting access to sensitive data in system memory dumps
US9325717B1 (en) Web-store restriction of external libraries
US10936725B2 (en) Container image vulnerability reduction
AU2016422515A1 (en) Tracing objects across different parties
US20200162512A1 (en) Generating false data for suspicious users
US9477934B2 (en) Enterprise collaboration content governance framework
US9087137B2 (en) Detection of custom parameters in a request URL
US10237266B2 (en) Privileged shared account password sanitation
US9344420B2 (en) Systems and methods for deploying rich internet applications in a secure computing environment
EP3136278B1 (fr) Dispositif d'analyse de code chargé dynamiquement, procédé d'analyse de code chargé dynamiquement, et programme d'analyse de code chargé dynamiquement
US9871873B2 (en) Adapter for communication between web applications within a browser
US10970415B2 (en) Sensitive data redaction in memory dump
US10911305B2 (en) Efficient rule processing for device management data evaluation
US11809301B2 (en) Techniques for large-scale functional testing in cloud-computing environments
US20220191238A1 (en) Automated seamless recovery

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16742563

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16742563

Country of ref document: EP

Kind code of ref document: A1