EP3401782B1 - Dateiidentifizierungsverfahren und zugehörige vorrichtung - Google Patents

Dateiidentifizierungsverfahren und zugehörige vorrichtung Download PDF

Info

Publication number
EP3401782B1
EP3401782B1 EP17805842.6A EP17805842A EP3401782B1 EP 3401782 B1 EP3401782 B1 EP 3401782B1 EP 17805842 A EP17805842 A EP 17805842A EP 3401782 B1 EP3401782 B1 EP 3401782B1
Authority
EP
European Patent Office
Prior art keywords
file
directory
header identifier
identifier
indicated
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
Application number
EP17805842.6A
Other languages
English (en)
French (fr)
Other versions
EP3401782A1 (de
EP3401782A4 (de
Inventor
Hui Li
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
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 Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of EP3401782A1 publication Critical patent/EP3401782A1/de
Publication of EP3401782A4 publication Critical patent/EP3401782A4/de
Application granted granted Critical
Publication of EP3401782B1 publication Critical patent/EP3401782B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/40—Transformation of program code
    • G06F8/41—Compilation
    • G06F8/42—Syntactic analysis
    • G06F8/427—Parsing

Definitions

  • This disclosure relates to the field of electronic technology, and particularly to a method for identifying a file and related devices.
  • APK file an Android Package (i.e., APK file) of the application needs to be scanned.
  • APK file itself is a zip package
  • all files in the APK file need to be decompressed to identify a native library file and a RenderScript file stored in the APK file.
  • the native library file and the RenderScript file are traversed to achieve the scanning.
  • a lot of scan time will be consumed, resulting in increased time to boot or install applications.
  • the Wikipedia website includes a page illustrating the definition and structure of zip files, and a page relating to Android application package (APK) format, which describes how APK files can be installed on Android powered devices.
  • API Android application package
  • the disclosure provides a method for identifying a file and related devices, which can identify a file indicated by a file header identifier via scanning the file header identifier of an installation file, thereby reducing scan time of the installation file before booting or installing an application.
  • a file indicated by a file header identifier can be identified via scanning the file header identifier of an installation file and scan time of the installation file before booting a mobile terminal or installing an application can be reduced.
  • FIG. 1 is a schematic flow chart illustrating a method for identifying a file according to an embodiment of the disclosure.
  • Mobile terminals include, for example, mobile phones, tablets, laptops, palmtops, mobile internet devices (MID), wearable devices such as smart watches (for example, iwatch®), smart bracelets, pedometers and the like, and other terminal devices.
  • MID mobile internet devices
  • wearable devices such as smart watches (for example, iwatch®), smart bracelets, pedometers and the like, and other terminal devices.
  • the method begins at S100.
  • an installation file and an end tag position of a file directory of the installation file are acquired.
  • the installation file of the application needs to be acquired and a structure of the file directory in a format of the installation file needs to be extracted to achieve a partial scan.
  • the applications are indicated by various files in the file directory.
  • the file directory contains file header identifiers each for indicating a file.
  • Various files can be identified via scanning the file header identifiers. Consequently, the operation of decompressing all files in the installation file to identify a native library file and a RenderScript file can be omitted.
  • the installation file itself is a zip package, the end tag position of the file directory of the zip package can be obtained.
  • the end tag position of the file directory of the zip package can be at 0x06054b50 of the installation file in a binary format.
  • a start tag position of the file directory is determined according to the end tag position of the file directory.
  • the mobile terminal can determine the start tag position of the file directory according to the end tag position of the file directory, so as to determine a position range of the file directory in the installation file in the binary format and the start tag position of the file directory in the binary format.
  • a file header identifier in the file directory is queried for according to the start tag position of the file directory and a file indicated by the file header identifier is identified via analyzing the file header identifier.
  • all file header identifiers for indicating files are queried for in a traversal manner according to the start tag position of the file directory. After that, a file list is generated according to all the file header identifiers queried. The file indicated by the file header identifier is then identified via analyzing each file header identifier in the file list. After completing the process of analyzing the file header identifiers, the application can be initialized when booting the mobile terminal or installing the application.
  • a position of the file header identifier is at 0x04034b50 of the installation file in the binary format.
  • the installation file and the end tag position of the file directory of the installation file are acquired first. Then the start tag position of the file directory is determined according to the end tag position of the file directory. At last, the file header identifier in the file directory is queried for according to the start tag position of the file directory and the file indicated by the file header identifier is identified via analyzing the file header identifier. In this way, the process of decompressing all files in the installation file can be omitted. Therefore, scan time of the installation file before booting the mobile terminal or installing the application can be reduced, and efficiency of booting the mobile terminal or installing the application can be improved.
  • FIG. 2 is a schematic flow chart illustrating a method for identifying a file according to another embodiment of the disclosure.
  • Mobile terminals include, for example, mobile phones, tablets, laptops, palmtops, mobile internet devices (MID), wearable devices such as smart watches (for example, iwatch®), smart bracelets, pedometers and the like, and other terminal devices.
  • MID mobile internet devices
  • wearable devices such as smart watches (for example, iwatch®), smart bracelets, pedometers and the like, and other terminal devices.
  • the method begins at S200.
  • an installation file and an end tag position of a file directory of the installation file are acquired.
  • the installation file of the application needs to be acquired and a structure of the file directory in a format of the installation file need to be extracted to achieve a partial scan.
  • the applications are indicated by various files in the file directory.
  • the file directory contains file header identifiers each for indicating a file.
  • Various files can be identified via scanning the file header identifiers. Consequently, the operation of decompressing all files in the installation file to identify a native library file and a RenderScript file can be omitted.
  • the installation file itself is a zip package, the end tag position of the file directory of the zip package can be obtained.
  • the end tag position of the file directory of the zip package can be at 0x06054b50 of the installation file in a binary format.
  • a capacity of which the file directory occupies the installation file is acquired, and a distance between the file directory and a start position of the installation file (that is, a distance between the start tag position of the file directory and the start position of the installation file) is determined according to the end tag position of the file directory and the capacity of which the file directory occupies the installation file.
  • the mobile terminal can acquire the capacity (for example, the number of bytes) of which the file directory occupies the installation file. Thereafter, the distance between the file directory and the start position of the installation file is determined according to the end tag position of the file directory and the number of bytes of the file directory occupying the installation file.
  • the capacity for example, the number of bytes
  • the start tag position of the file directory is determined according to the distance between the file directory and the start position of the installation file.
  • the mobile terminal can determine the start tag position of the file directory. For example, the number of bytes of which the file directory occupies the installation file is 12, in this situation, according to the end tag position of the file directory and the occupation of 12 bytes, the offset of the file directory relative to the start position of the installation file is determined as 16 bytes. That is, the start tag position of the file directory is offset by 16 bytes relative to the start position of the installation file, and the capacity of the file directory is 12 bytes.
  • a file header identifier in the file directory is queried for according to the start tag position of the file directory and a file indicated by the file header identifier is identified via analyzing the file header identifier.
  • the application can be initialized when booting the mobile terminal or installing the application.
  • a position of the file header identifier is at 0x04034b50 of the installation file in the binary format.
  • the installation file and the end tag position of the file directory of the installation file are acquired first. Then, the start tag position of the file directory is determined according to the end tag position of the file directory. At last, the file header identifier in the file directory is queried for according to the start tag position of the file directory and the file indicated by the file header identifier is identified via analyzing the file header identifier. In this way, it is possible to omit the process of decompressing all files in the installation file. As a result, scan time of the installation file before booting the mobile terminal or installing the application can be reduced, and efficiency of booting the mobile terminal or installing the application can be improved.
  • FIG. 3 is a schematic flow chart illustrating a method for identifying a file according to yet another embodiment of the disclosure.
  • Mobile terminals include, for example, mobile phones, tablets, laptops, palmtops, mobile internet devices (MID), wearable devices such as smart watches (for example, iwatch®), smart bracelets, pedometers and the like, and other terminal devices.
  • MID mobile internet devices
  • wearable devices such as smart watches (for example, iwatch®), smart bracelets, pedometers and the like, and other terminal devices.
  • the method begins at S300.
  • an installation file and an end tag position of a file directory of the installation file are acquired.
  • the installation file of the application needs to be acquired and a structure of the file directory in a format of the installation file needs to be extracted to achieve a partial scan.
  • the applications are indicated by various files in the file directory.
  • the file directory contains file header identifiers each for indicating a file.
  • Various files can be identified via scanning the file header identifiers. Consequently, the operation of identifying a native library file and a RenderScript file by decompressing all files in the installation file can be omitted. Since the installation file itself is a zip package, the end tag position of the file directory of the zip package can be obtained.
  • the end tag position of the file directory of the zip package can be at 0x06054b50 of the installation file in a binary format.
  • a capacity of which the file directory occupies the installation file is acquired, and a distance between the file directory and a start position of the installation file is determined according to the end tag position of the file directory and the capacity of which the file directory occupies the installation file.
  • the mobile terminal can acquire the capacity (for example, the number of bytes) of which the file directory occupies the installation file. Thereafter, the distance between the file directory and the start position of the installation file is determined according to the end tag position of the file directory and the number of bytes of which the file directory occupies the installation file.
  • the capacity for example, the number of bytes
  • the start tag position of the file directory is determined according to the distance between the file directory and the start position of the installation file.
  • the mobile terminal can determine the start tag position of the file directory. For example, the number of bytes of which the file directory occupies the installation file is 12, in this situation, according to the end tag position of the file directory and the occupation of 12 bytes, the offset of the file directory relative to the start position of the installation file is determined as 16 bytes. That is, the start tag position of the file directory is offset by 16 bytes relative to the start position of the installation file, and the capacity of the file directory is 12 bytes.
  • a file header identifier in the file directory is queried for according to the start tag position of the file directory, and whether the file header identifier contains a first identifier for indicating a RenderScript file is determined.
  • all file header identifiers for indicating files are queried for in a traversal manner according to the start tag position of the file directory.
  • a file list is generated according to all the file header identifiers queried.
  • the file indicated by the file header identifier is then identified via analyzing each file header identifier in the file list. Whether the file header identifier contains the first identifier can be determined, where the first identifier can be. bc, configured to indicate the RenderScript file.
  • the mobile terminal can determine whether there is any RenderScript file by judging whether the file header identifier contains the first identifier. If the RenderScript file exists, proceed to S313; otherwise, the scan process ends.
  • the file indicated by the file header identifier can be identified as the RenderScript file. Thereafter, a system is notified that there exists the RenderScript file, and identification for the file is completed.
  • a S305 a file header identifier in the file directory is queried for according to the start tag position of the file directory, and a Lib library directory is acquired from the file directory.
  • the mobile terminal generates a file list by determining the file header identifier in the file directory and judges whether there is any Lib library directory in the file directory. If yes, the Lib library directory is acquired.
  • the file header identifier containing a second identifier is acquired from the Lib library directory, where the second identifier is configured to indicate a dynamic link library file.
  • the Lib library directory contains the file header identifier.
  • the mobile terminal can acquire the file header identifier containing the second identifier from the Lib library directory, where the second identifier can be .so (shared object), configured to indicate the dynamic link library file.
  • the mobile terminal when determining that the file header identifier contains the second identifier, the mobile terminal identifies the file indicated by the file header identifier as .so file.
  • the mobile terminal acquires the subdirectory of the Lib library directory to which the .so file belongs and determines that the subdirectory can be matched with the application binary interface, where the subdirectory can be matched with any of: arm64-v8a, armeabi-v7a, and armeabi of the application binary interface. If the subdirectory of the Lib library directory to which the .so file belongs supports any one of arm64-v8a, armeabi-v7a, and armeabi, it is determined that the subdirectory of the Lib library directory to which the .so file belongs supports the application binary interface.
  • a file header identifier in the file directory is queried for according to the start tag position of the file directory and a file indicated by the file header identifier is identified via analyzing the file header identifier.
  • operations at S309-S312 relates to identifying, querying for, and copying of the native library file.
  • the mobile terminal generates a file list by determining the file header identifier in the file directory, and identifies the file indicated by the file header identifier via analyzing the file header identifier.
  • a capacity, the most recent modification time relative to the current time, and a check value of the file indicated by the file header identifier are acquired.
  • the capacity, the most recent modification time relative to the current time, and the check value of the file indicated by the file header identifier can be acquired.
  • the capacity of the file indicated by the file header identifier can be a decompressed size of the file. For example, referring to a start position of the file header identifier, the decompressed size of the file indicated by the file header identifier can be acquired at a position which is offset by 22 bytes relative to the start position of the file header identifier, the most recent modification time relative to the current time of the file indicated by the file header identifier can be acquired at a position which is offset by 10 bytes relative to the start position of the file header identifier, and the check value of the file indicated by the file header identifier can be acquired at a position offset relative to the start position of the file header identifier by 14 bytes.
  • the check value of the file indicated by the file header identifier is a check value of cyclic redundancy check (CRC).
  • the capacity, the most recent modification time, and the check value of the file indicated by the file header identifier are compared with a capacity, the most recent modification time relative to the current time, and a check value of the dynamic link library file ( .so file) contained in the Lib library directory.
  • a capacity, the most recent modification time relative to the current time and a check value of the dynamic link library file ( .so file) contained in the Lib library directory.
  • whether the .so file contained in the Lib library directory is modified or does not exist can also be judged.
  • the file indicated by the file header identifier is not the same as the .so file contained in the Lib library directory, it is determined that the .so file contained in the Lib library directory is modified or does not exist, advance to S312; on the other hand, if the file indicated by the file header identifier is the same as the .so file contained in the Lib library directory, advance to S313 and the scan process ends.
  • the .so file in addition to the Lib library directory, can also be contained in at least one of: a directory of data, a directory of applications (app), and a directory of an application package names.
  • the file indicated by the file header identifier is depressed into the Lib library directory based on a judgment that the file indicated by the file header identifier is not the same as the dynamic link library file.
  • the mobile terminal when determining that the file indicated by the file header identifier is not the same as the .so file contained in the Lib library directory, the mobile terminal determines that the .so file contained in the Lib library directory is modified or does not exist. In this case, the file indicated by the file header identifier can be depressed and then stored in the Lib library directory.
  • the file indicated by the file header identifier can be decompressed into at least one of: the directory of the data, the directory of the applications, and the directory of the application package names.
  • operations at S303-S304 and S313, operations at S305-S308, and operations at S309-S313 may be performed in parallel.
  • the disclosure is not particularly limited.
  • the installation file and the end tag position of the file directory of the installation file are acquired first. And then, the start tag position of the file directory is determined according to the end tag position of the file directory. At last, the file header identifier in the file directory is queried for according to the start tag position of the file directory and the file indicated by the file header identifier is identified via analyzing the file header identifier. In this way, the process of decompressing all files in the installation file can be omitted. Consequently, it is possible to reduce scan time of the installation file before booting the mobile terminal or installing the application, and improve efficiency of booting the mobile terminal or installing the application.
  • FIG. 4 is a schematic structural diagram illustrating a device for identifying a file according to an embodiment of the disclosure.
  • the device illustrated in FIG. 4 can execute the methods illustrated in FIGS. 1-3 . The disclosure will not be repeated herein.
  • the device illustrated in FIG. 4 includes an acquiring module 400, a determining module 401, and an identifying module 402.
  • the acquiring module 400 is configured to acquire an installation file and an end tag position of a file directory of the installation file.
  • the determining module 401 is configured to determine a start tag position of the file directory according to the end tag position of the file directory acquired by the acquiring module 400.
  • the identifying module 402 is configured to query for a file header identifier in the file directory according to the start tag position of the file directory determined by the determining module 401 and identify a file indicated by the file header identifier via analyzing the file header identifier.
  • the installation file of the application needs to be acquired and a structure of the file directory in a format of the installation file is extracted to achieve a partial scan.
  • the applications are indicated by various files in the file directory.
  • Various files are identified via scanning the file header identifier, of the file directory, for indicating each file. Consequently, the operation of decompressing all files in the installation file to identify a native library file and a RenderScript file can be omitted.
  • the installation file itself is a zip package, the end tag position of the file directory of the zip package can be acquired.
  • the mobile terminal can determine the start tag position of the file directory according to the end tag position of the file directory, so as to determine a position range of the file directory of the installation file in the binary format and the start tag position of the file directory in the binary.
  • all the file header identifiers for indicating files are queried for in a traversal way according to the start tag position of the file directory. After that, a file list is generated according to all the file header identifiers queried. The file indicated by the file header identifier is then identified via analyzing each file header identifier in the file list. After the process of analyzing each file header identifier is completed, the application can be initialized when booting the mobile terminal or installing the application.
  • the determining module 401 includes an acquiring unit 4011 and a determining unit 4012.
  • the acquiring unit 4011 is configured to acquire a capacity of which the file directory occupies the installation file, and determine a distance between the file directory and a start position of the installation file according to the end tag position of the file directory and the capacity of which the file directory occupies the installation file.
  • the determining unit 4012 is configured to determine the start tag position of the file directory according to the distance between the file directory and the start position of the installation file.
  • the identifying module 402 includes a judging unit 4021 and a first identifying unit 4022.
  • the judging unit 4021 is configured to judge whether the file header identifier contains a first identifier for indicating a RenderScript file.
  • the first identifying unit 4022 is configured to identify the file indicated by the file header identifier as the RenderScript file based on a judgment that the judging unit 4021 judges that the file header identifier contains the first identifier.
  • the acquiring module 400 is further configured to acquire a Lib library directory from the file directory.
  • the identifying module 402 includes an acquiring unit 4023 and a second identifying unit 4024.
  • the acquiring unit 4023 is configured to acquire the file header identifier containing a second identifier from the Lib library directory, where the second identifier is configured to indicate a dynamic link library file.
  • the second identifying unit 4024 is configured to identify the file indicated by the file header identifier containing the second identifier as the dynamic link library file.
  • the determining module 401 is further configured to determine that a subdirectory of the Lib library directory to which the file indicated by the file header identifier containing the second identifier belongs supports an application binary interface.
  • the acquiring module 400 is further configured to acquire a capacity, most recent modification time, and a check value of the file indicated by the file header identifier.
  • the device further includes a judging module 403 and a decompressing module 404.
  • the judging module 403 is configured to judge whether the file indicated by the file header identifier is the same as a dynamic link library file contained in a Lib library directory according to the capacity, the most recent modification time, and the check value of the file indicated by the file header identifier.
  • the decompressing module 404 is configured to decompress the file indicated by the file header identifier into the Lib library directory based on a judgment that the judging module 403 judges that the file indicated by the file header identifier is not the same as the dynamic link library file.
  • the end tag position of the file directory of the installation file is at 0x06054b50 of the installation file in a binary format.
  • a position of the file header identifier is at 0x04034b50 of the installation file in a binary format.
  • the check value of the file indicated by the file header identifier is a check value of cyclic redundancy check (CRC).
  • the file indicated by the file header identifier is decompressed into at least one of: a directory of data, a directory of an application (app), and a directory of an application package name.
  • the installation file and the end tag position of the file directory of the installation file are acquired first. And then, the start tag position of the file directory is determined according to the end tag position of the file directory. At last, the file header identifier in the file directory is queried for according to the start tag position of the file directory and the file indicated by the file header identifier is identified via analyzing the file header identifier. In this way, the process of decompressing all files in the installation file can be omitted. Therefore, scan time of the installation file before booting the mobile terminal or installing the application can be reduced, and efficiency of booting the mobile terminal or installing the application can be improved.
  • the above modules are configured to execute related operations of the methods in FIGS. 1-3 .
  • the device is presented in the form of modules.
  • Module herein can refer to an application-specific integrated circuit (ASIC), a processor and a memory for executing one or more software or firmware programs, an integrated logic circuit, and/or other components that can achieve the above described functions.
  • ASIC application-specific integrated circuit
  • the acquiring module 400, the determining module 401, the identifying module 402, the judging module 403, and the decompressing module 404 can be implemented by the processor 601 of the mobile terminal illustrated in FIG. 6 .
  • a mobile terminal 600 can be configured by the structure illustrated in FIG .6 .
  • the mobile terminal 600 includes at least one processor 601, at least one memory 602, and at least one communication interface 603.
  • the processor 601, the memory 602, and the communication interface 603 are connected via a communication bus and achieve mutual communication.
  • the processor 601 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling execution of programs of the above schemes.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication interface 603 is configured to communicate with other devices or communication networks, such as an Ethernet, a radio access network (RAN), a wireless local area network (WLAN), and the like.
  • RAN radio access network
  • WLAN wireless local area network
  • the memory 602 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, blu-ray discs, etc.), magnetic disk storage medium, or other magnetic storage devices, or any other mediums that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer.
  • the disclosure is not limited thereto.
  • the memory can be separated from the processor and connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 602 is configured to store application program codes for executing the above schemes.
  • the processor 601 is configured to execute the application program codes stored in the memory 602.
  • the application program codes stored in the memory 602 can be configured to execute the methods in FIGS. 1-3 executed by the above mobile terminal. For instance, an installation file and an end tag position of a file directory of the installation file are acquired. A start tag position of the file directory is determined according to the end tag position of the file directory. A file header identifier in the file directory is queried for according to the start tag position of the file directory and a file indicated by the file header identifier is identified via analyzing the file header identifier.
  • Embodiments of the present disclosure also provide a computer readable storage medium.
  • the computer readable storage medium can store programs which, when executed, can implement all or part of the operations of any of the methods described in the foregoing method embodiments.
  • Embodiments of the present disclosure also provide a computer program product.
  • the computer program product includes a non-transitory computer readable storage medium that stores computer programs.
  • the computer programs are operable with a computer to implement all or part of the operations of any of the methods described in the above method embodiments.
  • the computer program product may be a software installation package.
  • the above described device embodiments are merely exemplary.
  • the units described as separate components may or may not be physically separated, the components illustrated as units may or may not be physical units, that is, they may be in the same place or may be distributed to multiple network elements. All or part of the units may be selected according to actual needs to achieve the purpose of the technical solutions of the embodiments. Those of ordinary skill in the art can understand and implement the technical solutions without creative efforts.
  • modules or units of the embodiments of the present disclosure may be implemented as a general-purpose integrated circuit (such as a central processing unit, CPU) or as an application-specific integrated circuit (ASIC).
  • a general-purpose integrated circuit such as a central processing unit, CPU
  • ASIC application-specific integrated circuit
  • the technical solutions of the present disclosure essentially, or the part of the technical solutions that contributes to the related art, or all or part of the technical solutions, may be embodied in the form of a software product which is stored in a computer readable storage medium (for example, a read-only memory (ROM), a random-access memory (RAM), Disk, compact disc (CD), or the like) and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device and so on) to perform all or part of the operations described in the various embodiments of the present disclosure.
  • a computer readable storage medium for example, a read-only memory (ROM), a random-access memory (RAM), Disk, compact disc (CD), or the like
  • a computer device which may be a personal computer, a server, or a network device and so on

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Telephone Function (AREA)

Claims (11)

  1. Verfahren zum Identifizieren einer Datei, umfassend:
    Erfassen (S100) einer Installationsdatei und einer End-Tag-Position eines Dateiverzeichnisses der Installationsdatei bei Booten eines mobilen Endgeräts oder Installieren einer Applikation in dem mobilen Endgerät;
    Bestimmen (S101) einer Start-Tag-Position des Dateiverzeichnisses gemäß der End-Tag-Position des Dateiverzeichnisses; und
    Abfragen (S102) nach einer Datei-Header-Kennung in dem Dateiverzeichnis gemäß der Start-Tag-Position des Dateiverzeichnisses;
    Erfassen (S305) eines Lib-Library-Verzeichnisses aus dem Dateiverzeichnis; und
    Identifizieren einer durch die Datei-Header-Kennung angezeigten Datei über Analysieren der Datei-Header-Kennung durch:
    Erfassen (S306) der eine zweite Kennung enthaltenden Datei-Header-Kennung aus dem Lib-Library-Verzeichnis, wobei die zweite Kennung konfiguriert ist zum Anzeigen einer Dynamic-Link-Library-Datei; und
    Identifizieren (S307) der durch die die zweite Kennung enthaltenden Datei-Header-Kennung angezeigten Datei als die Dynamic Link Library-Datei; und
    Bestimmen (S308), dass ein Unterverzeichnis des Lib-Library-Verzeichnisses, zu dem die durch die die zweite Kennung enthaltende Datei-Header-Kennung angezeigte Datei gehört, eine Binärschnittstelle unterstützt.
  2. Verfahren nach Anspruch 1, wobei das Bestimmen einer Start-Tag-Position des Dateiverzeichnisses gemäß der End-Tag-Position des Dateiverzeichnisses umfasst:
    Erfassen (S201) einer Kapazität, mit der das Dateiverzeichnis die Installationsdatei belegt, und bestimmen einer Distanz zwischen dem Dateiverzeichnis und einer Startposition der Installationsdatei gemäß der End-Tag-Position des Dateiverzeichnisses und der Kapazität, mit der das Dateiverzeichnis die Installationsdatei belegt; und
    Bestimmen (S202) der Start-Tag-Position des Dateiverzeichnisses gemäß der Distanz zwischen dem Dateiverzeichnis und der Start-Position der Installationsdatei.
  3. Verfahren nach Anspruch 1, wobei das Identifizieren einer durch die Datei-Header-Kennung angezeigten Datei über Analysieren der Datei-Header-Kennung umfasst:
    Beurteilen (S303), ob die Datei-Header-Kennung eine erste Kennung zum Anzeigen einer RenderScript-Datei enthält; und
    Identifizieren (S304) der durch die Datei-Header-Kennung als die RenderScript-Datei identifizierten Datei auf Basis einer Beurteilung, dass die Datei-Header-Kennung die erste Kennung enthält.
  4. Verfahren nach Anspruch 1, weiterhin umfassend:
    Erfassen (S310) einer Kapazität, der jüngsten Modifikationszeit relativ zu der aktuellen Zeit und eines Prüfwerts der durch die Datei-Header-Kennung angezeigten Datei;
    Beurteilen (S311), ob die durch die Datei-Header-Kennung angezeigte Datei die gleiche ist wie die in dem Lib-Library-Verzeichnis enthaltene Dynamic-Link-Library-Datei gemäß der Kapazität, der jüngsten Modifikationszeit relativ zu der aktuellen Zeit und dem Prüfwert der durch die Datei-Header-Kennung angezeigten Datei; und
    Dekomprimieren (S312) der durch die Datei-Header-Kennung angezeigten Datei in das Lib-Library-Verzeichnis auf Basis einer Beurteilung, dass die durch die Datei-Header-Kennung angezeigte Datei nicht die gleiche ist wie die Dynamic-Link-Library-Datei.
  5. Verfahren nach einem der Ansprüche 1 bis 4, wobei die End-Tag-Position des Dateiverzeichnisses der Installationsdatei bei 0x06054b50 der Installationsdatei in einem binären Format ist.
  6. Verfahren nach einem der Ansprüche 1 bis 5, wobei eine Position der Datei-Header-Kennung bei 0x04034b50 der Installationsdatei in einem binären Format ist.
  7. Verfahren nach einem der Ansprüche 1 bis 6, wobei der Prüfwert der durch die Datei-Header-Kennung angezeigten Datei ein Prüfwert einer zyklischen Redundanzprüfung (CRC) ist.
  8. Verfahren nach einem der Ansprüche 1 bis 7, wobei die durch die Datei-Header-Kennung angezeigte Datei in mindestens eines der Folgenden dekomprimiert wird: ein Verzeichnis von Daten, ein Verzeichnis von Applikationen und ein Verzeichnis von Applikationspaketnamen.
  9. Verfahren nach einem der Ansprüche 1 bis 8, wobei das Abfragen nach einer Datei-Header-Kennung in dem Dateiverzeichnis gemäß der Start-Tag-Position des Dateiverzeichnisses und Identifizieren einer durch die Datei-Header-Kennung angezeigten Datei über Analysieren der Datei-Header-Kennung umfassen:
    Bestimmen eines Positionsbereichs des Dateiverzeichnisses in der Installationsdatei in einem binären Format gemäß der Start-Tag-Position,
    Abfragen nach, innerhalb des Positionsbereichs, allen Datei-Header-Kennungen zum Anzeigen von Dateien auf traversale Weise gemäß der Start-Tag-Position;
    Generieren einer Dateiliste gemäß allen abgefragten Datei-Header-Kennungen; und
    Identifizieren von durch die Datei-Header-Kennungen angezeigten Dateien über Analysieren jeder Datei-Header-Kennung in der Dateiliste.
  10. Mobiles Endgerät, umfassend:
    einen Speicher, konfiguriert zum Speichern ausführbarer Programmcodes; und
    einen Prozessor, mit dem Speicher gekoppelt;
    wobei der Prozessor konfiguriert ist zum Aufrufen der in dem Speicher gespeicherten ausführbaren Programmcodes, um das Verfahren nach einem der Ansprüche 1 bis 9 auszuführen.
  11. Computerablagemedium, konfiguriert zum Speichern von Programmen, die bei Ausführung betreibbar sind zum Ausführen des Verfahrens nach einem der Ansprüche 1 bis 9.
EP17805842.6A 2016-05-31 2017-05-31 Dateiidentifizierungsverfahren und zugehörige vorrichtung Active EP3401782B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610380642.8A CN106055363B (zh) 2016-05-31 2016-05-31 一种识别文件的方法及移动终端
PCT/CN2017/086544 WO2017206897A1 (zh) 2016-05-31 2017-05-31 识别文件的方法及相关设备

Publications (3)

Publication Number Publication Date
EP3401782A1 EP3401782A1 (de) 2018-11-14
EP3401782A4 EP3401782A4 (de) 2019-04-10
EP3401782B1 true EP3401782B1 (de) 2020-09-02

Family

ID=57172604

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17805842.6A Active EP3401782B1 (de) 2016-05-31 2017-05-31 Dateiidentifizierungsverfahren und zugehörige vorrichtung

Country Status (4)

Country Link
US (2) US10599413B2 (de)
EP (1) EP3401782B1 (de)
CN (1) CN106055363B (de)
WO (1) WO2017206897A1 (de)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9787799B2 (en) 2014-02-27 2017-10-10 Dropbox, Inc. Systems and methods for managing content items having multiple resolutions
US10198355B2 (en) 2015-10-29 2019-02-05 Dropbox, Inc. Proving a dynamic digital content cache
CN106055363B (zh) * 2016-05-31 2017-11-14 广东欧珀移动通信有限公司 一种识别文件的方法及移动终端
CN106874776B (zh) * 2016-12-30 2020-06-09 厦门天锐科技股份有限公司 一种加密文件的解密方法
CN110413321A (zh) * 2018-04-28 2019-11-05 珠海全志科技股份有限公司 一种Android系统快速启动方法及装置
CN109408465B (zh) * 2018-10-29 2021-07-13 Oppo广东移动通信有限公司 文件归属信息记录方法、装置、存储介质及终端
US10983677B2 (en) * 2018-11-16 2021-04-20 Dropbox, Inc. Prefetching digital thumbnails from remote servers to client devices based on a dynamic determination of file display criteria
CN113626040B (zh) * 2020-05-06 2023-12-22 伊姆西Ip控股有限责任公司 用于安装应用的方法、电子设备和计算机程序产品
CN111694576B (zh) * 2020-05-22 2023-06-13 中国航空工业集团公司西安航空计算技术研究所 一种综合化航电系统软件部署控制方法

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6289512B1 (en) * 1998-12-03 2001-09-11 International Business Machines Corporation Automatic program installation
US6769115B1 (en) * 2000-05-01 2004-07-27 Emc Corporation Adaptive interface for a software development environment
US7089552B2 (en) * 2002-08-29 2006-08-08 Sun Microsystems, Inc. System and method for verifying installed software
US8805799B2 (en) * 2007-08-07 2014-08-12 International Business Machines Corporation Dynamic partial uncompression of a database table
US8024382B2 (en) * 2009-01-20 2011-09-20 Autodesk, Inc. Dynamic manipulation of archive files
US20100242037A1 (en) * 2009-03-17 2010-09-23 Microsoft Corporation Software Deployment over a Network
US8949737B2 (en) * 2009-10-28 2015-02-03 Red Hat, Inc. Centralized application package distribution
CN102902687B (zh) * 2011-07-27 2015-09-09 华为软件技术有限公司 资源文件的访问方法及装置
US8930940B2 (en) * 2011-08-19 2015-01-06 Yongyong Xu Online software execution platform
CN104252364B (zh) * 2013-06-25 2017-09-12 腾讯科技（深圳）有限公司 增量更新的方法、设备及系统
CN104573514B (zh) * 2013-10-29 2018-09-04 腾讯科技（深圳）有限公司 压缩文件的检测方法及装置
CN103646047A (zh) * 2013-11-25 2014-03-19 大连海联自动控制有限公司 Vb快速访问sql数据库的方法
CN104679534B (zh) * 2013-11-28 2019-11-19 南京中兴软件有限责任公司 系统应用安装包加载处理方法、装置及终端
CN104866504B (zh) * 2014-02-25 2018-07-06 北京娜迦信息科技发展有限公司 一种对Android软件进行功能扩展的方法及装置
CN104199673B (zh) * 2014-09-22 2018-01-26 联想(北京)有限公司 一种信息处理方法及装置
CN104572966A (zh) * 2014-12-30 2015-04-29 北京奇虎科技有限公司 一种压缩文件的解压方法和装置
CN105278989B (zh) * 2015-10-12 2018-04-06 北京顶象技术有限公司 Apk文件的快速加载方法
CN106055363B (zh) * 2016-05-31 2017-11-14 广东欧珀移动通信有限公司 一种识别文件的方法及移动终端

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
CN106055363A (zh) 2016-10-26
US10452376B2 (en) 2019-10-22
US20180364999A1 (en) 2018-12-20
EP3401782A1 (de) 2018-11-14
WO2017206897A1 (zh) 2017-12-07
EP3401782A4 (de) 2019-04-10
US20190146770A1 (en) 2019-05-16
CN106055363B (zh) 2017-11-14
US10599413B2 (en) 2020-03-24

Similar Documents

Publication Publication Date Title
EP3401782B1 (de) Dateiidentifizierungsverfahren und zugehörige vorrichtung
CN111209004B (zh) 代码转换方法及装置
CN109766099B (zh) 前端源码编译方法、装置、存储介质及计算机设备
US9742640B2 (en) Identifying compatible web service policies
US9258357B2 (en) Method for accessing plural cloud storages, electronic apparatus and non-transitory computer readable medium
CN106843842B (zh) 一种应用程序配置文件的更新方法及装置
CN108647032B (zh) 应用加载方法及装置、计算机装置和计算机可读存储介质
CN110688096B (zh) 包含插件的应用程序的构建方法、装置、介质及电子设备
CN107341106B (zh) 应用程序兼容性检测方法、开发终端及存储介质
CN113672224A (zh) 小程序页面代码生成方法、装置及计算机设备
CN113127125A (zh) 页面自动适配方法、装置、设备及存储介质
KR101117165B1 (ko) 이기종 운영체제 계층 모듈에서 동작하는 웹기반어플리케이션의 연동이 가능한 모바일 단말기용 웹 플랫폼 유닛
CN106020917B (zh) 一种软件安装方法及装置、用户终端
US20140298316A1 (en) Managing method for application program installation and electronic device
CN109190367B (zh) 利用沙箱运行应用程序安装包的方法及装置
CN110647753B (zh) 内核文件的获取方法、装置、设备及存储介质
CN107357864B (zh) 一种文件处理方法及终端
CN109002710B (zh) 一种检测方法、装置及计算机可读存储介质
CN105991729B (zh) 一种安装包下载方法及服务器
CN112887328A (zh) 一种样本检测方法、装置、设备及计算机可读存储介质
CN111984451A (zh) 表格数据的纠错方法、系统、设备及存储介质
CN110825406A (zh) 一种软件升级的方法及相关设备
CN110032501B (zh) 一种app安装包的处理方法、装置和电子设备
WO2022166410A1 (zh) 非同名符号的函数跳转方法、装置及计算机可读存储介质
CN113127054B (zh) 一种文件处理方法和相关装置

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20180809

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602017022983

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0009445000

Ipc: G06F0008610000

A4 Supplementary search report drawn up and despatched

Effective date: 20190313

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 8/61 20180101AFI20190306BHEP

Ipc: G06F 9/445 20180101ALI20190306BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LT

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20200525

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1309618

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200915

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602017022983

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201202

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201203

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201202

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200902

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1309618

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200902

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210104

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210102

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602017022983

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20210603

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210531

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210531

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210531

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210531

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230412

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200923

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20170531

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230525

Year of fee payment: 7

Ref country code: DE

Payment date: 20230524

Year of fee payment: 7

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230525

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200902