WO2013022686A1 - Procédé et dispositif pour cataloguer les métadonnées fournies par de multiples fournisseurs de contenu dans un système multimédia - Google Patents

Procédé et dispositif pour cataloguer les métadonnées fournies par de multiples fournisseurs de contenu dans un système multimédia Download PDF

Info

Publication number
WO2013022686A1
WO2013022686A1 PCT/US2012/049268 US2012049268W WO2013022686A1 WO 2013022686 A1 WO2013022686 A1 WO 2013022686A1 US 2012049268 W US2012049268 W US 2012049268W WO 2013022686 A1 WO2013022686 A1 WO 2013022686A1
Authority
WO
WIPO (PCT)
Prior art keywords
metadata
content
data
contents
content providers
Prior art date
Application number
PCT/US2012/049268
Other languages
English (en)
Inventor
Samir Ahmed
Original Assignee
Technicolor Usa, 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 Technicolor Usa, Inc. filed Critical Technicolor Usa, Inc.
Publication of WO2013022686A1 publication Critical patent/WO2013022686A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/266—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
    • H04N21/2665—Gathering content from different sources, e.g. Internet and satellite
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
    • G06F16/48—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/84—Generation or processing of descriptive data, e.g. content descriptors
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/85—Assembly of content; Generation of multimedia applications
    • H04N21/854—Content authoring
    • H04N21/8543—Content authoring using a description language, e.g. Multimedia and Hypermedia information coding Expert Group [MHEG], eXtensible Markup Language [XML]

Definitions

  • the present application discloses a method and an apparatus for cataloging the metadata supplied from multiple content providers in various data formats. More specifically, a disclosed embodiment creates a mapping table using a plurality of metadata supplied from the multiple content providers and generates an individual Technicolor id for each one of the multimedia contents.
  • a method comprising importing a plurality of metadata files associated with respective ones of plurality of contents on a first plurality of data format from multiple content providers, extracting metadata from the plurality of metadata files, mapping the metadata based upon at least one key data field for gathering all metadata relevant to one of the plurality of contents, generating a unique Id for said one of the plurality of contents, merging the gathered metadata in a predetermined manner, and exporting the merged metadata on a second plurality of data format.
  • an apparatus comprising first means, such as an input point, for importing a plurality of metadata files associated with respective ones of plurality of contents on a first plurality of data format from multiple content providers and second means, including a processor, coupled to the first means for processing the plurality of imported metadata files, wherein the second means extracts metadata from the plurality of imported metadata files, the second means maps said metadata based upon at least one key data field for gathering all metadata relevant to one of the plurality of contents, the second means generates a unique Id for the one of the plurality of contents, and the second means merges the gathered metadata in a predetermined manner for exporting the merged metadata on a second plurality of data format.
  • first means such as an input point
  • second means including a processor, coupled to the first means for processing the plurality of imported metadata files, wherein the second means extracts metadata from the plurality of imported metadata files, the second means maps said metadata based upon at least one key data field for gathering all metadata relevant to one of the plurality of contents, the second means generates a
  • the apparatus comprises an interface coupled to multiple content providers operative to import a plurality of metadata files associated with respective ones of plurality of contents on a first plurality of data format from multiple content providers, a merging processor coupled to the input point operative to extract metadata from the plurality of metadata files, the processor operative to map the metadata based upon at least one key data field for gathering all metadata relevant to one of the plurality of contents, the processor operative to generate a unique Id for the one of the plurality of contents, the processor operative to merge the gathered metadata in a predetermined manner, and the processor operative to export the merged metadata on a second plurality of data format.
  • Fig. 1 depicts a conceptual block diagram illustrating an exemplary embodiment of the Technicolor Data Ingest (TDI) system along with its external environment in accordance with the present disclosure
  • Fig, 2 depicts a flowchart of an exemplary embodiment of the TDI signal processing steps in accordance with the present disclosure
  • Fig, 3 depicts a detailed view of a part of the conceptual block diagram of Fig. 1 , which illustrates an exemplary embodiment of the TDI system along with its exemplary eternal environment in accordance with the present disclosure;
  • Fig. 4 depicts an exemplary embodiment of a metadata mapping table for the TDI system in accordance with the present disclosure
  • Fig. 5 depicts an exemplary embodiment illustrating a delta partition process of the TDI system in accordance with the present disclosure
  • Fig. 6 depicts a conceptual block diagram illustrating an exemplary embodiment of the data processing system subsequent to the TDI system in accordance with the present disclosure.
  • a preferred embodiment disclosed herein matches various metadata, supplied from multiple content providers on different data formats, so that a metadata mapping table with respect to common media contents may be created, More specifically, these various metadata are cataloged with respect to a particular common content, such as the same movie content.
  • a rich set of aggregated relevant metadata may be created by selectively combining preferable fields of the metadata provided by the multiple content providers with respect to the common content.
  • the attributes of metadata are called as "fields,” which may include, but are not limited to, the data on the titles of movies, the names of the directors of movies, the release years of movies, etc.
  • the disclosed embodiment which may be used with MapReduce and NoSQL technologies, reduces the data processing time for the creation of a metadata mapping table.
  • the TDI system makes it possible to scale easily by utilizing existing hardware available.
  • the TDI system is a highly scalable solution for merging incoming rows of metadata, also known as "records," from multiple content providers into a collection of enhanced records for distribution to users. Because different content providers may provide the same fields of metadata over the same contents and because the merging rules of the metadata may be user specific, the TDI system takes into account the ongoing maintenance of changing providers and merging rules. Furthermore, the TDI system is designed and implemented with fault tolerance and robustness in mind. In addition, the TDI system can be hardware agnostic and is executable in public cloud environments (like Amazon EC2), where compute instances can be ephemeral, as well as in house environments.
  • public cloud environments like Amazon EC2
  • the TDI system allows several metadata on various data formats to be imported and matched seamlessly together. This advantage is derived from a particular way how both structured and unstructured metadata are being matched in the TDI system. That is, the matching operation is carried out by simply defining one or a plurality of key matching field(s), such as key fields including the title, the name of director, the names of actors, the release year, the genre(s), and the name of the producer of a particular content.
  • key matching field(s) such as key fields including the title, the name of director, the names of actors, the release year, the genre(s), and the name of the producer of a particular content.
  • TDI system 110 a conceptual block diagram illustrating an exemplary embodiment of TDI system 110 along with exemplary external environment 120, 130, 140, 150, 160 and 170, with which TDI system 1 10 communicates, is described.
  • Multiple content providers provide multiple contents 120 for TDI system 1 10.
  • Such content providers include, for example, TMS, IVA, Set J am, Baseline, and other network service providers (NSPs).
  • TDI system 1 10 has a bi-directional communication with each one of the providers. For example, TDI system 1 10 not only periodically receives contents along with their metadata from the providers but also sends requests to the providers, for particular information including metadata, as illustrated with arrows 122, 123 from the TDI system 1 10 to the content providers.
  • Arrow 121 illustrates headend/configuration data for TV contents.
  • Arrows 124, 125, 126, 127 and 128 illustrate the metadata provided by multiple content providers— SetJam, TMS, Baseline, NSP and SiteManager. These metadata are generated and formatted in various different manners, depending upon providers.
  • Arrows 131 , 141 , 151 , 161 and 171 represent various output of TDI system 1 10.
  • One form of exported metadata 131 is provided for Search and Recommendation engine 130.
  • Merged offers 141 includes the metadata concerning the price information of the contents.
  • Merged metadata 151 is provided for data cache 150 for fast access.
  • Transfer images 161 represents the passed-through content output for contend distribution network (CDN) 160.
  • CDN contend distribution network
  • OpenCase export 171 represents another form of exported data suitable for the OpenCase application.
  • TDI system 1 10 imports media contents, including the metadata thereof, from multiple content providers.
  • TDI system 1 10 extracts the metadata from the media contents.
  • TDI 1 10 maps the metadata, using the information for one or plurality of key fields, That is, TDI 1 10 maps (i.e., relates) a plurality of metadata for the same contents provided by the multiple content proviers as illustrated in Fig. 4.
  • TDI 1 10 provides an Id (called "Technicolor Id" herein) for each one of the various media contents for easy identification. For example, once the key field information, such as the titles of media contents, has been matched, TDI system 1 10 generates an individual Technicolor Id for each one of the records, in other words, an individual Technicolor Id is now available for identifying a group of various fields of metadata, supplied from multiple content providers, associated with a particular single media content. In step 220, a group of selected fields of metadata associated with the same content, which are identified by a single Technicolor Id, are merged in a predetermined manner. In step 240, the merged metadata are formatted in a predetermined manner for exported. Thanks to Technicolor Ids, other systems in the downstream may easily access the merged metadata for any media contents available through TDI system 1 10,
  • TDI system 1 10 in Fig. 1 is described.
  • Multiple content providers 301 (Studios), 302 (TMS), 304 (Baseline), 306 (SetJam), 308 (IVA), 309 (Rotten Tomatoes provide TDI system 1 10 with various metadata on their native data representaiton formats, such as XML, CVS, Regex, etc.
  • TDI system 1 10 reads metadata from imported files, respectively, and load the metadata into a data source (not shown in Fig. 3). Each extract operation automatically creates a new partition in the data source as shown in Fig. 5.
  • TDI system 1 10 receives metadata feeds 183, 125, 185, 124, 187, 189 from respective ones of multiple providers 301 , 302, 304, 306, 308, 309 on a regular basis, and such data feeds may include the data on new elements, updated elements and missing elements.
  • a partition is created with an individual partition Id along with the date of import as shown in Fig. 5.
  • partition 510 is created with the partition Id of "771-2264-FAE" along with the data importation date and time of July 10, 2012 at 22:08:47 on data source 550.
  • partition 520 is created with the partition Id of "121-44654-CDE" along with the data importation date and time of July 1 1 , 2012 at 08:40:23 on data source 550.
  • TDI system 1 10 creates a delta difference between the two partitions. That is, TDI system 3 10 creates delta partition 515 for the first and second metadata feeds and provides delta partition Id of "D-452-1634-EEC" for such delta partition data. This allows TDI system 1 10 to export only the delta data in order to avoid sending redundant information to the downstream systems,
  • the metadata for the movie contents provided by content provider 302 includes “tmsjd,” which identify the movie contents provided by content provider 302 (TMS).
  • the metadata for the movie contents provided by content provider 304 includes “bl spanmovie_id,” which identifies the movie contents provided by content provider 304 (Baseline).
  • content provider 304 (Baseline) provides the metadata "bLpersonJd,” which identifies the names of the people featuring the movie contents provided by content provider 304 (Baseline).
  • content provider 302 (TMS) does not provide the metadata that identifies the names of the people featuring the movie contents provided by content provider 302 (TMS).
  • some providers provide particular fields of metadata while other providers do not. This is because the metadata fields are not standardized among content providers.
  • TDI system 1 10 The metadata mapping and merging operation of TDI system 1 10 are now described in detail. It is possible for multiple content providers to provide the metadata relevant to a common media content, such as the same movie. However, since providers use different forms of Ids to identify the same media content, TDI system 1 10 needs to identify the relationship of the various forms of metadata provided by multiple content providers— e.g., whether or not the various forms of metadata may be relevant to the same media content.
  • the key field analysis mentioned above, is used to determine the relationships among the various metadata. In other words, one or a plurality of selected key field(s)— e.g., a metadata field describing the title of movie— may be analyzed to determine whether or not the same movie is involved.
  • Id mapping table 400 is described.
  • the various metadata on the common media content Movie 1 are provided by six different content providers Providers A - F.
  • each one of the six providers uses a different form of Id to identify its metadata relevant to Movie 1.
  • Provide A uses "MV2121 12" while Providers B - F use "254544,” “S31 13131 ,” “ 1544454,” “c54wser544" and "D54wer45,” respectively.
  • TDI system 1 10 determines that all of these six different Ids in fact identify a single common media content (i.e.. Movie 1), an independent Technicolor Id of "T12121" is generated.
  • mapping and merging operation 312 the extracted metadata are processed for cataloging, merging, and exporting in accordance with Technicolor Ids, as described above, in one embodiment.
  • extracted metadata may be reformatted and exported directly to the downstream users, without being merged into the metadata supplied from other providers, as shown by arrow 315.
  • TDI system 1 10 defines the data to be included in the export along with a data format thereof. More specifically, TDI system 1 10 may select one of the metadata out of a plurality of metadata in the same field for export when the plurality of metadata in the same field are available. For example, if a plurality of titles describing the same movie are available, TDI system 1 10 may be able to select one of the title descriptions for export. TDI system 1 10 may be able to export the data in a predetermined data format suitable for a downstream user. For example, such data formats for export may include (but are not limited to) the XML and JSON formats.
  • TDI system 1 10 the data sources are represented as Virtual Tables giving the ability to query the data seamlessly. Although the data can be queried using HQL (like in a traditional relation database), the data is not stored online. This architecture makes it possible to store a huge amount of past partition information, without affecting the query performance of daily runs. This is advantageous over the conventional Relational DataBase Management System (RDBMS), which typically suffers in performance as the size of the data grows.
  • RDBMS Relational DataBase Management System
  • TDI system 1 10 can export delta partitions for all the metadata to be exported, in addition to full dataset export.
  • a delta export is done by performing a left outer join between the current partition and the delta partition. Records are compared using a custom JSON comparison on each record. When a record is equivalent in both partitions, the delta partition is not exported. Otherwise (i.e., when two metadata partitions are different, or a new data has been added to the latest metadata partition), TDI system 1 10 runs the delta partition exporting operation.
  • New data sets can easily be integrated by simply modifying a configuration file that identifies the fields that need to be matched. Adding and supporting new categories of output formats are also done easily simply by creating exporting rules and selecting any of the fields from the different data providers.
  • TDI system 1 10 may utilize, as described above, a plethora of well-known techniques, including (but not limited to) soundex and fuzzy matches, to match the different metadata provided by multiple content providers. After indexing, storing and merging the matched metadata, TDI can then be configured to export the metadata on different data formats, using any combinations of the metadata provided by multiple content providers on various data formats.
  • TDI system 1 10 makes it possible to scale up the number of machines in the grid in order to decrease the overall data processing time. As a result, the global data processing time is advantageously reduced from several days to several hours.
  • TDi system 1 10 In job analysis 610, job dependencies are analyzed and potentially executed, based on data freshness. Then in core process 620, TDi system 1 10 generates HQL 216 (Hive SQL) with current partition information embedded in the query. Code is also distributed using the underlying Hadoop Distributed Cache, which is different from the local TDI distributed cache using Redis, The optional stream instructions are also embedded in the generated SQL. This then generates Hadoop code in Java and runs the jar on the mappers and reducers in the cluster. Finally, an optional post processing step is executed, which can optionally put files together as a single file, insert a prefix and suffix to the data, concatenate a collection of files and create a final compressed version.
  • HQL 216 Hive SQL
  • code is also distributed using the underlying Hadoop Distributed Cache, which is different from the local TDI distributed cache using Redis.
  • the optional stream instructions are also embedded in the generated SQL. This then generates Hadoop code in Java and runs the jar
  • TDI system 110 is operative to function in combination with a Map Reduce engine (Hadoop-Java), a relational querying language HQL (Hive- Java), a Distributed Cache (Redis), and to utilize a transformation streaming technique known as Hadoop streaming as shown in Fig. 6.
  • Map Reduce engine Hadoop-Java
  • HQL relational querying language
  • Redis Distributed Cache
  • the tool uses a custom DSL (Domain Specific Language) built in Ruby so thai the underlying execution details are mostly abstracted away from developers. This provides a clean and cohesive experience when developing data processing rules using TDI system 1 10. Without such a language, one would have to manually interact with the underlying subsystems, mixing the business logic with the subsystem integration, creating a convoluted and difficult to maintain implementation.
  • the DSL also allows one to make generic optimizations to the platform without disturbing the business logic implemented using the DSL.
  • Figs. 1 6 may be implemented in various forms of hardware, software or combinations thereof. Preferably, these elements are implemented in a combination of hardware and software on one or more appropriately programmed general-purpose devices, which may include a processor, memory and input/output interfaces.
  • any flow charts, flow diagrams, state transition diagrams, pseudocode, and the like represent various processes that can be substantially represented in computer readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
  • the computer readable media and code written on can be implemented in a transitory state (signal) and a non-transitory state (e.g., on a tangible medium such as CD-ROM, DVD, Blu-Ray. Hard Drive, flash card, or other type of tangible storage medium).
  • processors capable of executing software in association with appropriate software.
  • the functions of such a processor may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared.
  • explicit use of the term "processor” or “controller” should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor ("DSP") hardware, read only memory (“ROM”) for storing software, random access memory (“RAM”), and nonvolatile storage.
  • DSP digital signal processor
  • ROM read only memory
  • RAM random access memory
  • any switches shown in the figures are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the implementer as more specifically understood from the context.

Abstract

L'invention concerne un procédé/dispositif (200;110) de traitement de métadonnées, qui permet d'importer (212) une pluralité de fichiers de métadonnées associés à des contenus respectifs d'une pluralité de contenus, dans une première pluralité de formats de données, provenant de multiples fournisseurs de contenu (301, 302, 304, 306, 308, 309); d'extraire (214) des métadonnées provenant de la pluralité des fichiers de métadonnées; de mapper (216) les métadonnées extraites sur la base d'au moins un champ de données de clé pour rassembler toutes les métadonnées pertinentes à un contenu de la pluralité des contenus; de produire (218) un Id unique pour le contenu de la pluralité des contenus; de fusionner les métadonnées rassemblées d'une manière prédéterminée; et d'exporter (240) les métadonnées fusionnées dans une deuxième pluralité de formats de données (340, 342, 344, 346, 348).
PCT/US2012/049268 2011-08-05 2012-08-02 Procédé et dispositif pour cataloguer les métadonnées fournies par de multiples fournisseurs de contenu dans un système multimédia WO2013022686A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201161574612P 2011-08-05 2011-08-05
US61/574,612 2011-08-05

Publications (1)

Publication Number Publication Date
WO2013022686A1 true WO2013022686A1 (fr) 2013-02-14

Family

ID=46640788

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2012/049268 WO2013022686A1 (fr) 2011-08-05 2012-08-02 Procédé et dispositif pour cataloguer les métadonnées fournies par de multiples fournisseurs de contenu dans un système multimédia

Country Status (1)

Country Link
WO (1) WO2013022686A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112784068A (zh) * 2021-01-28 2021-05-11 新华智云科技有限公司 一种媒资自定义编目的管理方法及其系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040003403A1 (en) * 2002-06-19 2004-01-01 Marsh David J. Methods and systems for reducing information in electronic program guide and program recommendation systems
US20070255741A1 (en) * 2006-04-28 2007-11-01 Business Objects, S.A. Apparatus and method for merging metadata within a repository
US20080046929A1 (en) * 2006-08-01 2008-02-21 Microsoft Corporation Media content catalog service
US20090259633A1 (en) * 2008-04-15 2009-10-15 Novafora, Inc. Universal Lookup of Video-Related Data

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040003403A1 (en) * 2002-06-19 2004-01-01 Marsh David J. Methods and systems for reducing information in electronic program guide and program recommendation systems
US20070255741A1 (en) * 2006-04-28 2007-11-01 Business Objects, S.A. Apparatus and method for merging metadata within a repository
US20080046929A1 (en) * 2006-08-01 2008-02-21 Microsoft Corporation Media content catalog service
US20090259633A1 (en) * 2008-04-15 2009-10-15 Novafora, Inc. Universal Lookup of Video-Related Data

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112784068A (zh) * 2021-01-28 2021-05-11 新华智云科技有限公司 一种媒资自定义编目的管理方法及其系统

Similar Documents

Publication Publication Date Title
US10769248B2 (en) Satellite and central asset registry systems and methods and rights management systems
US7711729B2 (en) Searching a document based on a customer defined metadata schemata
US7890547B2 (en) Content delivery server
US10452714B2 (en) Central asset registry system and method
US20120221498A1 (en) Aggregating and normalizing entertainment media
US20130297557A1 (en) Column based data transfer in extract, transform and load (etl) systems
US9300986B2 (en) Media system with canonical architecture for integrating media productions from different content providers
US10949440B2 (en) Metadata-driven data management platform
CN106462632B (zh) 具有内容规范层的媒体商店
KR20130142161A (ko) 효과적인 검색을 가능하게 하기 위해 서버 기반 및 lan 기반 매체 컨텐츠 및 정보를 결합하는 방법 및 장치
US20090024596A1 (en) System and apparatus to represent, store, manipulate, and process metadata information
Alexiou et al. OpenAIRE LOD services: scholarly communication data as linked data
EP3042316B1 (fr) Identification de musique
EP3577587B1 (fr) Systèmes et procédés de registres de ressources satellites et de registre central et systèmes de gestion de droits
US11868445B2 (en) Systems and methods for federated searches of assets in disparate dam repositories
WO2014201402A1 (fr) Systèmes et procédés pour rechercher des structures chimiques
US10776357B2 (en) System and method of data join and metadata configuration
WO2013022686A1 (fr) Procédé et dispositif pour cataloguer les métadonnées fournies par de multiples fournisseurs de contenu dans un système multimédia
US20170323015A1 (en) Automated metadata cleanup and distribution platform
WO2022031293A1 (fr) Systèmes et procédés de recherches fédérées d'actifs dans des référentiels de dam disparates
US9747368B1 (en) Batch reconciliation of music collections
KR102588238B1 (ko) 컨텐츠 제작 어플리케이션 및 상기 컨텐츠 제작 어플리케이션 구동 방법
CN110704421A (zh) 数据处理方法、装置、设备和计算机可读存储介质
US20240160701A1 (en) Systems and methods for federated searches of assets in disparate dam repositories
Jain et al. Analysis of Bill Of Material Data using Kafka and Spark

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: 12745759

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: 12745759

Country of ref document: EP

Kind code of ref document: A1