WO2011008199A1 - Distribution de fichiers à un dispositif mobile - Google Patents

Distribution de fichiers à un dispositif mobile Download PDF

Info

Publication number
WO2011008199A1
WO2011008199A1 PCT/US2009/050568 US2009050568W WO2011008199A1 WO 2011008199 A1 WO2011008199 A1 WO 2011008199A1 US 2009050568 W US2009050568 W US 2009050568W WO 2011008199 A1 WO2011008199 A1 WO 2011008199A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile device
download
files
user
file
Prior art date
Application number
PCT/US2009/050568
Other languages
English (en)
Inventor
Gary Wallace
Adam L. Berger
Original Assignee
Penthera Partners, 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 Penthera Partners, Inc. filed Critical Penthera Partners, Inc.
Priority to PCT/US2009/050568 priority Critical patent/WO2011008199A1/fr
Priority to EP09847427.3A priority patent/EP2454675A4/fr
Publication of WO2011008199A1 publication Critical patent/WO2011008199A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/62—Establishing a time schedule for servicing the requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • account in controlling a download of one or more files from a server to a mobile device, account is taken of at least two of: a power status of the mobile device, a network connectivity status of the mobile device, an urgency of the file, and the existence of a user- indicated preference about the download.
  • the controlling includes suspending a download of a file that is occurring when a power level or network connectivity degrades during the download.
  • the suspending of the download is based on a set of rules or heuristics.
  • the suspended download is resumed when the power level or network connectivity improves during the suspension.
  • the resumed download does not include at least some of the file or files that were downloaded before the suspension.
  • the resumed download does not include one or more pieces of a file that were downloaded before the suspension.
  • download of a file from a server to a mobile device through a network is controlled by breaking the file into pieces to be sent separately, monitoring conditions of the mobile device and the network with respect to each piece, considering suspending download of a subsequent piece if the conditions deteriorate with respect to a piece.
  • Some implementations include one or more of the following features.
  • the conditions are monitored after each piece is sent and before download of the subsequent piece has begun.
  • a partial download of a file is allowed to continue under deteriorated conditions, if predetermined circumstances exist.
  • a user of a mobile device to which large files are normally downloaded automatically from a server based on the user's preferences, can initiate a download by invoking a 'sync now' option on a user interface of the mobile device.
  • a sync signal is received from a server with respect to one or more large files to be downloaded, and to the sync signal is responded to by requesting and accepting a download of the one or more large files.
  • an indication is displayed to a user of the time when a download of one or more large files to the mobile device is expected to occur.
  • an amount of bandwidth used to download one or more large files to a mobile device is adjusted based on a time of day when the download is to occur.
  • the amount of bandwidth used at a given time of the day is governed by an amount paid by a user of the mobile device.
  • a log of download activity, with respect to one or more large files that are downloaded to the mobile device is sent from a mobile device to a server.
  • a user of a mobile device can specify one or more types of files that are to be downloaded to the mobile device, and the specification of file types is stored in a server in association with an identification of the mobile device or the user.
  • a server at a server, one or more files are selected to be downloaded to a mobile device based on stored preferences of a user of the mobile device and stored information about files that were previously downloaded to the user's device.
  • a list of files that are in process of being transmitted to a client mobile device, but which have not yet been completely transmitted to the device is displayed to a user of the device Attorney Docket No. 19647-0012WO 1
  • Implementations may include one or more of the following features.
  • the displaying includes showing a percentage of at least one of the listed the files which has been transmitted.
  • the displaying can occur at the mobile device.
  • the displaying can occur on a web page.
  • Figures 1 and 2 are block diagrams of a system architecture including a server and a client.
  • Figure 3 is a user- flow diagram of a client application.
  • Figure 4 is a screen shot of a user application.
  • Figure 5 is a menu of the application.
  • Figure 6 is a screen shot of a video file.
  • Figure 7 is a screen shot of a web-based subscription portal.
  • Figure 8 is a block diagram.
  • Some of the files 10, 20 in figure 1 are large.
  • a 30-minute audio, a 10+ minute video file, and a collection of 100+ web pages may be from 1MB to 500MB or larger.
  • Delivering a file that is tens or hundreds of megabytes to a mobile device presents challenges that are absent in delivering smaller files.
  • a complete download may take tens of minutes or even hours, depending on the speed of the connection.
  • conditions may change.
  • the mobile device may be within an area with excellent wireless network coverage; but as the download progresses, the network conditions may degrade.
  • the device's battery may lose its charge to a level at which continuing the file downloading risks depleting the battery.
  • small-file applications music downloads, email, web browser
  • downloading a file that is large may entail a time delay that implicates one or more other factors in the strategy used to determine the manner and timing of the download.
  • an application 60 manages the delivery of these large files from the remote server to the mobile device in a way that is sensitive to the following considerations:
  • the mobile device has one or more network interfaces 80, e.g., GPRS/EDGE,
  • CDMA/EVDO Code Division Multiple Access
  • WiFi Wireless Fidelity
  • Bluetooth Wireless Fidelity
  • USB cable tethered to a host computer
  • This connection is the "last hop" for data traveling over the IP network from the server to the device.
  • the availability of one or more of these network resources will vary from time to time as, for example, the mobile device moves in and out of network "hotspots.” For example, at one moment, WiFi and EDGE may be available; a few minutes later, only EDGE may be available.
  • the mobile device's power status 70 varies from time to time, depending, for example, on whether the device is charging or how long it has been on battery.
  • Certain files 10 are time sensitive and may need to be delivered right away (e.g., a stock ticker update).
  • Other files 20 are relatively time insensitive, and a delay of hours in delivery may be acceptable (e.g., a movie trailer).
  • Each file stored on the remote server may be annotated Attorney Docket No. 19647-0012WO l with an "urgency" parameter 30, which may be assigned by a creator of the file (content) or determined based on some other policy.
  • the method takes into account a set of factors (two or more) in determining a sync'ing policy, by which we mean whether and how often to sync. In some implementations, there is a particular algorithm used to take into account these factors to implement a sync'ing policy.
  • an example of the technique described here includes three parts: a client, a server, and a file repository.
  • the client is a software application 273 that resides on the mobile device 275.
  • the server 200 is comprised of a set of software components including a web portal 210, a sync module 220, a log upload module 230, and a database 240.
  • the file repository 290 includes a file system storing files for subsequent delivery to devices, and an application that manages the delivery of those files over an IP network (an example of such an application is the Apache HTTP server— http://httpd.apache.org/).
  • the client may be installed by the device manufacturer (OEM) before delivery to the retail outlet which sells or delivers the device (we sometimes refer to the mobile device simply as a device) to the end-user.
  • the client may be installed by the end-user after he has acquired the device, by downloading the software application from the Internet.
  • the client behaves as follows:
  • the signal may come from the device itself, from the server 265, or from the end-user 255.
  • the application performs these steps transparently to the user. That is, the user need not take any action to cause the steps to be performed and the user need not be made aware of any of the steps occurring.
  • New files are delivered— hourly, daily, weekly— directly to the mobile device. No user action is required. This is similar to the behavior of a home Digital Video Recorder (DVR).
  • DVR Digital Video Recorder
  • the files can be stored on the device's file system.
  • the files could be stored in the "My Documents" folder.
  • the user can access them manually, using existing tools on the mobile device (e.g., a "File Manager” application on a Windows Mobile device).
  • the client may include an application (figures 3, 4) that provides a user- friendly access to a list of
  • the application 400 may enable the user to view information about the available files (410 and 500. As shown in figure 5, the application display a menu 600 containing an option 610 to manually force a sync'ing with the server. The application may also allow the user to view files that are scheduled for delivery and/or in transit 430, but not yet fully downloaded. The application may also allow for users to change some aspects of the behavior of the client application 420, and show some details about the version and copyright information of the application 450.
  • the delivered files may be of various types. For example, web pages (e.g., HTML), audio files (e.g., MP3), video files (e.g., h.264 or WMV9 or Flash), and so on.
  • the application need not itself provide rendering/playout/presentation for any or all of these file types. Instead, the application may interface with existing applications (web browser, media player, etc.) on the device through standard application programming interface (API) calls. Once the user selects a file from the list (or Attorney Docket No. 19647-0012WO 1 from the native file browser), the appropriate external application is launched to render the file (figure 6, 700).
  • API application programming interface
  • the server's behavior need not be a synchronous step-by-step process, but rather can be a set of tasks that occur asynchronously, as the server is contacted by various mobile devices 275 and web- based terminals 285.
  • the server's behavior in some implementations includes the following (with reference again to figure 2):
  • FIG. 7 A representative screen shot of the subscription portal is shown in figure 7.
  • the portal may provide 800 a menu of subscriptions or "channels" available for selection.
  • the web portal may show 810 the current subscription policy of the user, e.g., which channels the user has requested to be delivered to his device.
  • the portal may allow the user to edit this subscription policy.
  • the sync module When a mobile device 275 queries the sync module 220 about the presence of new files, the sync module performs a multi-step process to determine if any such files are present. In some
  • the sync'ing protocol includes the following features. Account for current conditions
  • the protocol also checks the device's conditions (power, network) during the download.
  • the file 900 (in Figure 8) may be split 910 into pieces 920, 930, 940, and 950 which are sent individually 952, 954, 956, and 958
  • the client 960 checks the conditions after every piece is received and then continues (or not) the download at its discretion.
  • the constituent pieces of each file are reassembled at the client as they arrive, or, alternatively, when the final piece is downloaded. Should conditions deteriorate and force the client to suspend downloading, the download will resume from the suspended point (as opposed to from the beginning of the file) when conditions are suitable.
  • the protocol also allows for the client to continue downloading for some limited period of time even if conditions have deteriorated.
  • the protocol allows for a sync (we sometimes refer to a sync'ing procedure simply as a sync) to be initiated in several ways.
  • One way is to use a timer on the client; when the timer expires, the client queries the server for the presence of new files.
  • the proposed counter starts at 300 seconds.
  • the client application must be always running on the device. This is much like a standard mobile application (e.g., a game), which is either active or closed, and when closed, does not consume any random-access memory on the device. In these
  • the client application must be auto-started when the device is booted, and it must persist while the device is on. This is analogous to a home DVR, which is always on.
  • a second way to initiate a sync is in response to a user request.
  • the client application may provide a "Sync Now” button or link, (figure 5) If user selects it, the application may:
  • a third way to initiate a sync is from the server.
  • the client may be capable of receiving asynchronous messages directly from the server.
  • a RIM Blackberry device provisioned to use a Blackberry Enterprise Server (BES) can receive signals directly from the server through an MDS component. Therefore, the client application need not continuously poll the server for new files, nor remain active. The application can, instead, be inactive until the server signal arrives and causes the device to launch the application.
  • BES Blackberry Enterprise Server
  • Urgency levels a. Urgent: File marked as time-sensitive and should be delivered as soon as possible. b. Regular: File is not time- sensitive. Battery consumption levels a. Charging: device is plugged into A/C power. b. High: Running off battery, which is at least 7/8 charged. c. Medium: Running off battery, which is between Vi and 7/8 charged. d. Low: Running off battery, which is less than Vi charged. Network connectivity levels a. Fast: Using WLAN. b. Strong: using radio-access network; strong signal. c. Medium: using radio-access network; medium signal. d. Weak: using radio-access network; poor signal. e. None: no network connectivity.
  • Voice and SMS traffic generate more revenue per bit to the owner of a mobile network than generic data traffic. Therefore, during daytime hours (e.g., 9AM-7PM), when voice and SMS traffic is high and spare capacity limited, network owners are likely to discourage network-intensive applications. On the other hand, most cellular networks are 'latent' during off-peak hours such as 9PM-6AM. During this time window, mobile network owners are likely to be more receptive to network- intensive applications.
  • bandwidth on a wireless radio-access network is a commodity whose value to the network owner varies over time.
  • the application can throttle its mobile network bandwidth usage to an acceptable level during the daytime hours by waiting a specified period of time between downloading chunks of data. For example, the application can cut by 50% its bandwidth usage by pausing for
  • the application can cut by 67% its bandwidth usage by pausing for twice this amount of time.
  • a network operator can offer a tiered level of service to its customers, in which those customers who pay for a 'premium service' are permitted higher throughput for during-the-day downloads over the mobile network.
  • the application used by premium customers would not be forced to pause (as long, or at all) between chunk downloads.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Entre autres choses, en commandant un téléchargement d'un ou de plusieurs fichiers d'un serveur vers un dispositif mobile, il est pris en compte au moins deux des éléments suivants : une urgence du fichier, l'existence d'une préférence indiquée par l'utilisateur concernant le téléchargement, un état d'alimentation du dispositif mobile et un état de connectivité au réseau du dispositif mobile.
PCT/US2009/050568 2009-07-14 2009-07-14 Distribution de fichiers à un dispositif mobile WO2011008199A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/US2009/050568 WO2011008199A1 (fr) 2009-07-14 2009-07-14 Distribution de fichiers à un dispositif mobile
EP09847427.3A EP2454675A4 (fr) 2009-07-14 2009-07-14 Distribution de fichiers à un dispositif mobile

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2009/050568 WO2011008199A1 (fr) 2009-07-14 2009-07-14 Distribution de fichiers à un dispositif mobile

Publications (1)

Publication Number Publication Date
WO2011008199A1 true WO2011008199A1 (fr) 2011-01-20

Family

ID=43449616

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2009/050568 WO2011008199A1 (fr) 2009-07-14 2009-07-14 Distribution de fichiers à un dispositif mobile

Country Status (2)

Country Link
EP (1) EP2454675A4 (fr)
WO (1) WO2011008199A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8027671B2 (en) 2008-01-14 2011-09-27 Penthera Partners, Inc. Delivering files to a mobile device
CN104268252A (zh) * 2014-09-30 2015-01-07 北京奇虎科技有限公司 一种网页中视频元素的播放方法和装置

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5625818A (en) * 1994-09-30 1997-04-29 Apple Computer, Inc. System for managing local database updates published to different online information services in different formats from a central platform
US20030023745A1 (en) * 2001-07-26 2003-01-30 Neoplanet, Inc. Method and system for adaptively downloading data from a network device
US20030212992A1 (en) * 1998-12-04 2003-11-13 Ronning Joel A. Apparatus and method for using application signatures for the identification of files
US20040123323A1 (en) * 1995-02-24 2004-06-24 James Russo Stored program pay-per-play
US20040148344A1 (en) * 2003-11-19 2004-07-29 Serenade Systems Content distribution architecture
US20050246564A1 (en) * 2004-04-29 2005-11-03 Microsoft Corporation Advanced power management in generic USB drivers
US20060031537A1 (en) * 2004-06-08 2006-02-09 International Business Machines Corporation Method, system and program product for optimized concurrent data download within a grid computing environment
US20080078871A1 (en) * 2006-08-25 2008-04-03 The Boeing Company System and method for electronically latching compartments
US20080120369A1 (en) * 2006-11-16 2008-05-22 Gustavsson Bengt Stefan Media center for picture sharing
US20080183839A1 (en) * 2007-01-26 2008-07-31 Shuqair Michel A D System For Computer To Mobile Device Place Shifting
US20090125570A1 (en) * 2007-11-13 2009-05-14 Adobe Systems Incorporated Online backup and restore

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100553082B1 (ko) * 2002-06-20 2006-02-15 엘지전자 주식회사 이동통신 단말기의 무선 데이터 다운로드 이어받기 장치및 방법
US20080285496A1 (en) * 2007-05-14 2008-11-20 Bamboo Mediacasting Ltd. Data download in wireless network
EP2034775B1 (fr) * 2007-07-27 2010-05-26 Research In Motion Limited Appareil et procédés de fonctionnement d'un serveur sans fil

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5625818A (en) * 1994-09-30 1997-04-29 Apple Computer, Inc. System for managing local database updates published to different online information services in different formats from a central platform
US20040123323A1 (en) * 1995-02-24 2004-06-24 James Russo Stored program pay-per-play
US20030212992A1 (en) * 1998-12-04 2003-11-13 Ronning Joel A. Apparatus and method for using application signatures for the identification of files
US20030023745A1 (en) * 2001-07-26 2003-01-30 Neoplanet, Inc. Method and system for adaptively downloading data from a network device
US20040148344A1 (en) * 2003-11-19 2004-07-29 Serenade Systems Content distribution architecture
US20050246564A1 (en) * 2004-04-29 2005-11-03 Microsoft Corporation Advanced power management in generic USB drivers
US20060031537A1 (en) * 2004-06-08 2006-02-09 International Business Machines Corporation Method, system and program product for optimized concurrent data download within a grid computing environment
US20080078871A1 (en) * 2006-08-25 2008-04-03 The Boeing Company System and method for electronically latching compartments
US20080120369A1 (en) * 2006-11-16 2008-05-22 Gustavsson Bengt Stefan Media center for picture sharing
US20080183839A1 (en) * 2007-01-26 2008-07-31 Shuqair Michel A D System For Computer To Mobile Device Place Shifting
US20090125570A1 (en) * 2007-11-13 2009-05-14 Adobe Systems Incorporated Online backup and restore

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2454675A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8027671B2 (en) 2008-01-14 2011-09-27 Penthera Partners, Inc. Delivering files to a mobile device
US9112838B2 (en) 2008-01-14 2015-08-18 Penthera Partners, Inc. Delivering files to a mobile device
CN104268252A (zh) * 2014-09-30 2015-01-07 北京奇虎科技有限公司 一种网页中视频元素的播放方法和装置

Also Published As

Publication number Publication date
EP2454675A4 (fr) 2016-10-26
EP2454675A1 (fr) 2012-05-23

Similar Documents

Publication Publication Date Title
US8027671B2 (en) Delivering files to a mobile device
CN100411341C (zh) 一种并行下载方法和终端
US9172622B2 (en) Methods, systems and computer products for download status notification
US8583164B2 (en) Reward-based access to media content
US8650325B2 (en) Establishing network connections
US8205006B2 (en) Systems and methods for discontinuous multi-media content transfer and handling
US20130115940A1 (en) Method and Apparatus for Downloading a File Based on WIFI
US20160269505A1 (en) Rapid Data Acquisition Over the Internet
US9619388B2 (en) Method for managing cache data of a mobile terminal, mobile terminal, and server
US9730037B2 (en) Cellular data communication for mobile devices
US20140269437A1 (en) Broadcast media content to subscriber group
KR102218648B1 (ko) 전자 장치에서 컨텍스트 데이터와 사용자 프로파일 데이터를 이용하여 저장 공간을 관리하는 방법 및 장치
CN101958901B (zh) 一种基于长期演进的多媒体点播方法、系统和移动终端
US20100240353A1 (en) Remote control system and facility side control apparatus and control program of facility apparatus and control method of facility apparatus
CN111488207A (zh) 应用进程保活方法、装置、网络设备及存储介质
CN103024724A (zh) 信息处理系统和方法、服务器、移动终端
EP2454675A1 (fr) Distribution de fichiers à un dispositif mobile
CN105721392A (zh) 一种推荐应用的方法、装置及系统
KR101522728B1 (ko) 슬라이드 검출을 기반으로 하는 데이터 전송 방법 및 기기
CN102065146B (zh) 用于优化嵌入式终端在p2p应用中的存储效率的方法与设备
CN101309211A (zh) 接收装置和接收系统
EP2645319A2 (fr) Système publicitaire, procédé publicitaire et dispositif compatible au réseau externe
KR20050058807A (ko) 이동 통신 단말기의 콘텐츠 다운로드 방법
KR20070083025A (ko) 이동단말기의 컨텐츠 다운로드 방법
KR101370323B1 (ko) 어플리케이션의 ｕｉ 이벤트 처리 방법 및 이를 위한이동통신 단말기

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2009847427

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2009847427

Country of ref document: EP