WO2018068361A1 - 应用程序的流量管理方法、系统及具有该系统的终端设备 - Google Patents

应用程序的流量管理方法、系统及具有该系统的终端设备 Download PDF

Info

Publication number
WO2018068361A1
WO2018068361A1 PCT/CN2016/106054 CN2016106054W WO2018068361A1 WO 2018068361 A1 WO2018068361 A1 WO 2018068361A1 CN 2016106054 W CN2016106054 W CN 2016106054W WO 2018068361 A1 WO2018068361 A1 WO 2018068361A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
data packet
identifier
package name
tool
Prior art date
Application number
PCT/CN2016/106054
Other languages
English (en)
French (fr)
Inventor
范自道
胡海龙
Original Assignee
网宿科技股份有限公司
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 网宿科技股份有限公司 filed Critical 网宿科技股份有限公司
Priority to EP16918622.8A priority Critical patent/EP3445010B1/en
Priority to US16/092,906 priority patent/US10680962B2/en
Publication of WO2018068361A1 publication Critical patent/WO2018068361A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2475—Traffic characterised by specific attributes, e.g. priority or QoS for supporting traffic characterised by the type of applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Definitions

  • the invention belongs to the technical field of terminal devices, and relates to a management method and system, in particular to a method and system for managing traffic of an application and a terminal device having the same.
  • a mobile intelligent terminal refers to a program that is provided by a third-party service provider such as a personal computer, and can be installed by a user, such as a software, a game, and the like, by which the user can continuously expand the function of the terminal and can move through the mobile terminal.
  • a portable device that implements wireless network access through a communication network.
  • Common mobile smart terminals include smartphones and tablets. Thanks to its high portability, mobile smart terminals are becoming the most frequently used terminal devices.
  • the existing mobile intelligent terminal device covers a plurality of applications, and needs to perform differential management on different application traffic to enhance the access experience of the mobile intelligent terminal.
  • One is to convert the packet information into the owner attribute
  • the second is to manage the traffic of different owners.
  • traffic management is more common on routers and remote servers, and is generally based on ip as the minimum management granularity.
  • an object of the present invention is to provide a method and system for managing traffic of an application, and a terminal device having the same, which is used to solve the problem that the prior art cannot distinguish and manage different APP traffic. .
  • an aspect of the present invention provides a traffic management method for an application, and a traffic management method for the application, where the traffic management method of the application includes the following steps: reading a sent by the application The attribute information of the data packet for indicating the source thereof; determining, according to the attribute information of the data packet, whether the application that sends the data packet is a designated play tool, and the data packet originating from the specified play tool and the non-source designated play The tool's data packets are managed differently.
  • the determining whether the application that sends the data packet is a designated playing tool is The step of differentially managing the data packet originating from the specified playing tool and the data packet not originating from the specified playing tool includes: converting the attribute information of the data packet into an identifier corresponding to the application that sends the data packet; determining the Whether the identifier corresponding to the application is an identifier of the specified playing tool; if yes, the application is a specified playing tool, and the foreground process is queried, and the package name of the data packet is mapped to the package name of the foreground process. If not, the identifier of the application is converted to the package name of the application.
  • the data packet is used to indicate that the attribute information of the source includes source port information of the data packet; and the attribute information of the data packet is converted into an application corresponding to the application that sends the data packet.
  • the step of identifying is to map an identifier matching the source port information of the transmitted data packet in a first lookup table for recording a TCP connection status based on source port information of the data packet.
  • the step of converting the identifier of the application into the application package name includes: An identifier corresponding to the application, searching for a package name of an application matching the identifier in a second lookup table for recording a package name of an application that sends the data packet; or according to The lookup interface of the package name of the application, looking up the package name of the application; converting the identifier of the application into the application package name.
  • the designated play tool is a MediaServer component of the Android system.
  • Another aspect of the present invention provides a traffic management system for an application, where the traffic management system of the application includes: a reading module, configured to read attribute information of a data packet sent by the application for indicating its source a management module, configured to determine, according to the attribute information of the data packet, whether the application that sends the data packet is a designated play tool, to distinguish between a data packet originating from the specified play tool and a data packet not derived from the specified play tool; management.
  • a reading module configured to read attribute information of a data packet sent by the application for indicating its source
  • a management module configured to determine, according to the attribute information of the data packet, whether the application that sends the data packet is a designated play tool, to distinguish between a data packet originating from the specified play tool and a data packet not derived from the specified play tool; management.
  • the management module includes: a conversion unit, configured to convert attribute information of the data packet into an identifier corresponding to an application that sends the data packet; and a processing unit, configured to determine the Whether the identifier corresponding to the application is an identifier of the specified playing tool; if yes, the application is a specified playing tool, and the foreground process is queried, and the package name of the data packet is mapped to the package name of the foreground process.
  • the data packet is used to indicate that source attribute information includes source port information of the data packet; and the converting unit is configured to record TCP according to source port information of the data packet.
  • the first lookup table of the connection status maps an identifier that matches the source port information of the transmitted data packet.
  • the processing unit when the processing unit determines that the identifier corresponding to the application is not the identifier of the specified play tool, the processing unit is configured to record and send the data packet according to the identifier corresponding to the application program.
  • the second query table of the package name of the application finds the package name of the application matching the identifier; or finds the package of the application according to the lookup interface for finding the package name of the application that sends the data packet Name; convert the identifier of the application into the Application package name.
  • Another aspect of the present invention provides a terminal device, where the terminal device includes: the traffic management system of the application.
  • the traffic management method and system of the application of the present invention and the terminal device having the same have the following beneficial effects:
  • the traffic management method and system of the application according to the present invention and the terminal device having the same implement precise management of traffic of different applications, and do not require intervention of the APP, and do not need to modify the system architecture of the terminal device.
  • FIG. 1 is a schematic diagram showing the structure of a terminal device system according to the present invention.
  • FIG. 2 is a schematic flowchart showing a flow management method of an application of the present invention in an embodiment.
  • FIG. 3 is a schematic diagram showing the flow of step S5 in the traffic management method of the application of the present invention.
  • FIG. 4 is a schematic diagram showing the principle structure of a traffic management system of an application of the present invention in an embodiment.
  • FIG. 5 is a schematic diagram showing the principle structure of a management module in a traffic management system of an application program of the present invention.
  • FIG. 6 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
  • the association between the status of the App and the MediaPlayer to play the video and the traffic are implemented in the application layer.
  • the App traffic identification is based on the UID (User Identification) attribute of the App (application), that is, the correspondence between the packet information and the UID, and the UID is the App.
  • UID User Identification
  • the unique identifier in the system so it can be determined by the packet information that the packet belongs to an App, thereby realizing the management of the specified player traffic and other traffic for different App traffic.
  • the embodiment provides a traffic management method for an application, and the traffic management method of the application includes the following steps:
  • Reading attribute information of the data packet indicating its source
  • the application that sends the data packet is a designated playing tool, and the data packet originating from the specified playing tool and the data packet not derived from the specified playing tool are separately managed. .
  • the traffic management method of the application described in this embodiment will be described in detail below with reference to the drawings.
  • the traffic management method of the application described in this embodiment is applied to a terminal device.
  • the actual implementation manner of the terminal device includes a smart phone, a tablet computer, a set top box, or an IPAD.
  • FIG. 1 a schematic diagram of a three-dimensional structure of a terminal device according to an embodiment of the present invention is shown.
  • the terminal device is described by taking a smart phone as an example.
  • the smart phone is, for example, a smart phone that installs an Android operating system or an iOS operating system, or an operating system such as Palm OS, Symbian, or Blackberry OS 6.0 or Windows Phone 8.
  • the touch screen is used to output a display application icon user interface.
  • the application icon user interface includes a plurality of application icons.
  • the traffic management method of the application is completed by configuring an APP, a MediaServer, a traffic management platform, and a Netfilter at the IP layer, both of which are in the application layer, in the terminal device.
  • FIG. 1 shows a schematic structural diagram of a terminal device system.
  • FIG. 2 a flow diagram of an application flow management method in an embodiment is shown.
  • the traffic including mediaPlayer traffic and non-mediaPlayer traffic.
  • the traffic management method of the application specifically includes the following steps:
  • the S2 Receive a request for traffic access, and know that the request for receiving the traffic access is a data packet directly sent by an application (APP), or a data packet accessed by an application (APP) through a media server (MediaServer).
  • APP application
  • MediaServer media server
  • the App actually sends a video play request to the MediaServer through the client of the MediaPlayer, and the video play request is sent by the MediaServer.
  • the data packet used to request to play the video includes a data packet originating from a specified playing tool and a data packet not derived from the specified playing tool.
  • step S2 further includes: in the process of sending the data packet originating from the specified play tool and the data packet not originating from the specified play tool to the proxy server or the source station, the traffic management platform intercepts The data packet sent by the application intercepts the data packet originating from the specified playback tool and the data packet not derived from the specified playback tool.
  • the terminal device is always waiting for the interception of the data packet before intercepting the data packet sent by the application.
  • the network firewall is used to redirect the data packet originating from the specified play tool and the non-source designation.
  • the package of the playback tool is used to redirect the data packet originating from the specified play tool and the non-source designation.
  • the iptable syntax is: iptable[-t table]command[chain][match][-j target]
  • the traffic management platform reads the data packet originating from the specified play tool and the attribute information of the data packet not derived from the specified play tool for indicating its source.
  • the data packet is used to indicate that the attribute information of the source includes the source port information of the data packet, that is, the source port information of the data packet originating from the specified playback tool and the data not derived from the specified playback tool. Source port information for the package.
  • the traffic management platform determines, according to the attribute information of the data packet, whether the application that sends the data packet is a designated play tool to distinguish between a data packet originating from the specified play tool and a data packet not derived from the specified play tool. Traffic management.
  • the specified playing tool is a Media Player (media player). Because many existing applications use VideoPlayer to play video.
  • FIG. 3 which is shown as a schematic diagram of the process of step S5. As shown in FIG. 3, the step S5 specifically includes the following steps:
  • S51 Convert the attribute information of the data packet, that is, the source port information of the data packet originating from the specified playing tool and the source port information of the data packet not derived from the specified playing tool, into sending the data packet originating from the specified playing tool.
  • An identifier for an application that is not derived from the packet of the specified playback tool is searched in a first lookup table for recording a TCP connection status.
  • the first lookup table is /proc/net/tcp(udp); the identifier is a UID.
  • the identifier corresponding to the application is an identifier of the specified play tool; if yes, indicating that the application is a designated play tool (MediaPlayer), performing step S53; if not, indicating the application For the non-designated play tool (MediaPlayer), step S54 is performed.
  • the identifier of the foreground process is 1013.
  • the system uniformly assigns a UID to the APP, wherein the UID of the APP of the data packet sent by the specified playback tool is fixed to 1013.
  • S53 Determine that the application is a specified play tool (MediaPlayer), query the foreground process, and map the package name of the data packet originating from the specified play tool to the package name of the foreground process.
  • the application APP calls the MediaPlayerr traffic access
  • the data packet from the specified playback tool with the UID of 1013 is triggered by the foreground process, and therefore, the package name mapping of the data packet originating from the specified playback tool is triggered.
  • S54 Determine that the application is a non-designated play tool, and convert the identifier of the application into a package name of the application. Specifically, the identifier of the application that accesses the traffic according to the non-designated playback tool (MediaPlayer) acquires the package name of the application and records it. In this embodiment, according to the identifier corresponding to the application, in the second query table for recording the package name of the application that sends the data packet, that is, in the /data/system/package.xml table in this embodiment.
  • the management of traffic sent by different applications includes guiding traffic, traffic statistics, and the like.
  • the traffic management method of the application program in this embodiment implements accurate management of traffic of different applications, and does not require intervention of the APP, and does not require modification of the terminal device system architecture.
  • the embodiment provides a traffic management system 2 for an application, and the system 2 is applied to the terminal device 1.
  • a schematic structural diagram of a traffic management system of an application is shown in an embodiment.
  • the traffic management system 2 of the application includes an initialization module 21, a receiving module 22, a redirection module 23, a reading module 24, and a management module 25.
  • the initialization module 21 is configured to initialize the terminal device.
  • the receiving module 22 connected to the initialization module 21 is configured to receive a request for traffic access, and know whether the request for receiving the traffic access is a data packet directly sent by the APP, or a data packet sent by the APP through the media server (MediaServer).
  • MediaServer media server
  • the App actually sends a video play request to the MediaServer through the client of the MediaPlayer, and the video play request is performed at this time. Issued by MediaServer.
  • the data packet for requesting to play the video includes a data packet originating from a specified playing tool and being forwarded by the media server located in the terminal device, and a non-originating designated playing device that is not forwarded by the media server. Packet.
  • the data packet originating from the specified play tool and the data packet not derived from the specified play tool are sent to Netfilter.
  • the receiving module 22 is further configured to: when the data packet sent by the application is sent to the remote server or the source station, the traffic management platform intercepts the data packet originating from the specified playing tool and the non-originating specified playing tool Packet.
  • the terminal device is always waiting for the data packet to be intercepted before intercepting the data packet originating from the specified play tool and the data packet not originating from the specified play tool.
  • the redirection module 23 connected to the receiving module 22 is configured to use the network firewall after the data packet originating from the specified playing tool and the data packet not derived from the specified playing tool enters the Netfilter built in the redirection module 23 Redirecting the data packet originating from the specified playback tool and the data packet not derived from the specified playback tool.
  • the iptable is used to redirect the data packet originating from the specified playback tool.
  • the reading module 24 connected to the receiving module 22 and the redirection module 23 is configured to read the data packets originating from the specified playing tool and the attribute information indicating the source thereof from the data packets not derived from the specified playing tool.
  • the data packet is used to indicate that the attribute information of the source includes the source port information of the data packet, that is, the source port information of the data packet originating from the specified playback tool and the data not derived from the specified playback tool. Source port information for the package.
  • the management module 25 connected to the reading module 24 is configured to determine, according to the attribute information of the data packet, whether the application that sends the data packet is an application that calls a specified playback tool to play a video to manage traffic of different applications.
  • FIG. 5 is a schematic diagram showing the principle structure of the management module. As shown in FIG. 5, the management module 25 specifically includes a conversion unit 251, a processing unit 252, and a traffic management unit 253.
  • the converting unit 251 is configured to use the attribute information of the data packet, that is, the source end of the data packet originating from the specified playing tool.
  • the port information and the source port information of the data packet not derived from the specified playback tool are converted into an identifier corresponding to the application that sends the data packet originating from the specified playback tool and the data packet not derived from the specified playback tool.
  • an identifier matching the source port information of the sent data packet is searched in a first lookup table for recording a TCP connection status.
  • the first lookup table is /proc/net/tcp(udp); the identifier is a UID.
  • the processing unit 252 connected to the conversion unit 251 is configured to determine an identifier corresponding to the specified play tool; if yes, the application is a specified play tool (MediaPlayer), and the foreground process is queried, and the data packet originating from the specified play tool is used.
  • the package name is mapped to the package name of the foreground process; if not, it indicates that the application is a non-designated play tool (MediaPlayer), and the identifier of the application is converted into the package name of the application.
  • the second query table for recording the package name of the application that sends the data packet that is, in the /data/system/package.xml table in this embodiment.
  • the identifier of the foreground process is 1013.
  • the system uniformly assigns a UID to the APP, wherein the UID of the APP that specifies the data packet of the playback tool is fixed to 1013.
  • the processing unit 262 determines that the application is a non-designated play tool
  • the identifier of the application is converted into a package name of the application.
  • the identifier of the application that accesses the traffic according to the non-designated playback tool (MediaPlayer) acquires the package name of the application and records it.
  • the identifier corresponding to the application in the second query table for recording the package name of the application that sends the data packet, that is, in the /data/system/package.xml table in this embodiment.
  • the traffic management unit 253 connected to the processing unit 252 is configured to manage the sound/flow generated by the application of the foreground process set by the package name and the package name of the application of the non-foreground process.
  • the management of traffic sent by different applications includes guiding traffic, traffic statistics, and the like.
  • the present embodiment further provides a terminal device 1.
  • a terminal device 1 Referring to FIG. 7, a schematic structural diagram of the terminal device in an embodiment is shown. As shown in FIG. 7, the terminal device 1 includes the traffic management system 2 of the above-described application.
  • the terminal device is any one of a set top box, a tablet computer, and a mobile phone.
  • the present invention effectively overcomes various shortcomings in the prior art and has high industrial utilization value.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供一种应用程序的流量管理方法、系统及具有该系统的终端设备，所述应用程序的流量管理方法包括以下步骤：读取所述应用程序发送的数据包的用于表示其来源的属性信息；根据该数据包的属性信息，判断发送该数据包的应用程序是否为指定播放工具，以对来源于指定播放工具的数据包和非来源于指定播放工具的数据包进行区别管理。本发明所述的应用程序的流量管理方法、系统及具有该系统的终端设备实现了对不同应用程序的流量进行精确管理，并且不需要APP的干预，不需要对终端设备系统架构进行改动。

Description

应用程序的流量管理方法、系统及具有该系统的终端设备 技术领域
本发明属于终端设备技术领域，涉及一种管理方法及系统，特别是涉及一种应用程序的流量管理方法、系统及具有该系统的终端设备。
背景技术
移动智能终端是指像个人电脑一样，具有独立的操作系统，可以由用户自行安装软件、游戏等第三方服务商提供的程序，通过此类程序来不断对终端的功能进行扩充，并可以通过移动通讯网络来实现无线网络接入的便携式设备。常见的移动智能终端包括智能手机和平板电脑。得益于其高度的便携性，移动智能终端正在成为人们使用频率最高的终端设备。
现有的移动智能终端设备涵盖多种应用，需要对不同应用流量进行区别管理，以增强移动智能终端的访问体验。
然而，现有的流量的管理一般分为两个步骤：
一是将数据包信息转化为拥有者属性；
二是对不同拥有者的流量进行管理，目前流量管理多见于路由器、远程服务器上，并且一般是以ip作为最小管理粒度。
而现有对流量管理的技术无法对不同APP流量进行区分管理。
因此，如何提供一种应用程序的流量管理方法、系统及具有该系统的终端设备，以解决现有技术无法对不同APP流量进区分管理的缺陷，实已成为本领域从业者亟待解决的技术问题。
发明内容
鉴于以上所述现有技术的缺点，本发明的目的在于提供一种应用程序的流量管理方法、系统及具有该系统的终端设备，用于解决现有技术无法对不同APP流量进行区分管理的问题。
为实现上述目的及其他相关目的，本发明一方面提供一种应用程序的流量管理方法，用程序的流量管理方法，所述应用程序的流量管理方法包括以下步骤：读取所述应用程序发送的数据包的用于表示其来源的属性信息；根据该数据包的属性信息，判断发送该数据包的应用程序是否为指定播放工具，以对来源于指定播放工具的数据包和非来源于指定播放工具的数据包进行区别管理。
于本发明的一实施例中，所述判断发送该数据包的应用程序是否为指定播放工具，以对 来源于指定播放工具的数据包和非来源于指定播放工具的数据包进行区别管理的步骤包括：将所述数据包的属性信息转换为发送该数据包的应用程序对应的标识符；判断所述应用程序对应的标识符是否为所述指定播放工具的标识符；若是，则表示该应用程序为指定播放工具，查询前台进程，将所述数据包的包名映射成所述前台进程的包名；若否，将所述应用程序的标识符转化成所述应用程序的包名。
于本发明的一实施例中，所述数据包用于表示其来源的属性信息包括数据包的源端口信息；所述将所述数据包的属性信息转换为发送该数据包的应用程序对应的标识符的步骤为根据所述数据包的源端口信息，在用于记录TCP连接状况的第一查询表中映射查找与所述发送数据包的源端口信息匹配的标识符。
于本发明的一实施例中，在判断所述应用程序对应的标识符不为指定播放工具的标识符时，将所述应用程序的标识符转化成所述应用程序包名的步骤包括：根据所述应用程序对应的标识符，在用于记录发送数据包的应用程序的包名的第二查询表中查找与所述标识符匹配的应用程序的包名；或根据用于查找发送数据包的应用程序的包名的查找接口，查找该应用程序的包名；将所述应用程序的标识符转化成所述应用程序包名。
于本发明的一实施例中，所述指定播放工具为安卓系统的MediaServer组件。
本发明另一方面提供一种应用程序的流量管理系统，所述应用程序的流量管理系统包括：读取模块，用于读取所述应用程序发送的数据包的用于表示其来源的属性信息；管理模块，用于根据该数据包的属性信息，判断发送该数据包的应用程序是否为指定播放工具，以对来源于指定播放工具的数据包和非来源于指定播放工具的数据包进行区别管理。
于本发明的一实施例中，所述管理模块包括：转换单元，用于将所述数据包的属性信息转换为发送该数据包的应用程序对应的标识符；处理单元，用于判断所述应用程序对应的标识符是否为所述指定播放工具的标识符；若是，则表示该应用程序为指定播放工具，查询前台进程，将所述数据包的包名映射成所述前台进程的包名。
于本发明的一实施例中，所述数据包用于表示其来源的属性信息包括数据包的源端口信息；所述转换单元用于根据所述数据包的源端口信息，在用于记录TCP连接状况的第一查询表中映射查找与所述发送数据包的源端口信息匹配的标识符。
于本发明的一实施例中，所述处理单元在判断所述应用程序对应的标识符不为指定播放工具的标识符时，根据所述应用程序对应的标识符，在用于记录发送数据包的应用程序的包名的第二查询表中查找与所述标识符匹配的应用程序的包名；或根据用于查找发送数据包的应用程序的包名的查找接口，查找该应用程序的包名；将所述应用程序的标识符转化成所述 应用程序包名。
本发明又一方面提供一种终端设备，所述终端设备包括：所述的应用程序的流量管理系统。
如上所述，本发明的应用程序的流量管理方法、系统及具有该系统的终端设备，具有以下有益效果：
本发明所述的应用程序的流量管理方法、系统及具有该系统的终端设备实现了对不同应用程序的流量进行精确管理，并且不需要APP的干预，不需要对终端设备系统架构进行改动。
附图说明
图1显示为本发明的终端设备系统配置结构示意图。
图2显示为本发明的应用程序的流量管理方法于一实施例中的流程示意图。
图3显示为本发明的应用程序的流量管理方法中步骤S5的流程示意图。
图4显示为本发明的应用程序的流量管理系统于一实施例中的原理结构示意图。
图5显示为本发明的应用程序的流量管理系统中管理模块的原理结构示意图。
图6显示为本发明的终端设备于一实施例中的原理结构示意图。
元件标号说明
1        终端设备
2        应用程序的流量管理系统
21       初始化模块
22       接收模块
23       重定向模块
24       读取模块
25       管理模块
251      转换单元
252      处理单元
253      流量管理单元
S1～S6   步骤
S51～S54 步骤
具体实施方式
以下通过特定的具体实例说明本发明的实施方式，本领域技术人员可由本说明书所揭露的内容轻易地了解本发明的其他优点与功效。本发明还可以通过另外不同的具体实施方式加以实施或应用，本说明书中的各项细节也可以基于不同观点与应用，在没有背离本发明的精神下进行各种修饰或改变。需说明的是，在不冲突的情况下，以下实施例及实施例中的特征可以相互组合。
需要说明的是，以下实施例中所提供的图示仅以示意方式说明本发明的基本构想，遂图式中仅显示与本发明中有关的组件而非按照实际实施时的组件数目、形状及尺寸绘制，其实际实施时各组件的型态、数量及比例可为一种随意的改变，且其组件布局型态也可能更为复杂。
本发明所述的应用程序的流量管理方法和系统的技术原理为：
将App调用mediaPlayer播放视频的状态与流量关联起来均在应用层实现，App流量识别是基于App(应用程序)的UID(User Identification)属性，即数据包信息与UID存在对应关系，UID又是App在系统中的唯一标识，因此可通过数据包信息确定该数据包属于某个App发出，从而实现对不同App流量，即实现了对指定播放器流量和其他流量进行管理。
实施例一
本实施例提供一种应用程序的流量管理方法，所述应用程序的流量管理方法包括以下步骤：
拦截应用程序发送的数据包；
读取所述数据包的用于表示其来源的属性信息；
根据该数据包的属性信息，判断发送该数据包的应用程序是否为指定播放工具，以对来源于指定播放工具的数据包和非来源于指定播放工具的数据包进行区别管理。。
以下将结合图示对本实施例所述的应用程序的流量管理方法进行详细描述。本实施例所述的应用程序的流量管理方法应用于终端设备。所述终端设备于实际的实现方式中包括智能手机、平板电脑，机顶盒，或IPAD等中。请参阅图1，显示为本发明的终端设备于一实施例中的立体结构示意图。
在本实施例中，所述终端设备以智能手机为例进行说明。所述智能手机例如为安装Android操作系统或者iOS操作系统，或者Palm OS、Symbian(塞班)、或者Black Berry(黑莓)OS 6.0、Windows Phone 8等操作系统的智能手机。在本实施例中，所述触摸屏用于输出显示应用程序图标用户界面。所述应用程序图标用户界面包括多个应用程序图标。
在本实施例中，通过在所述终端设备中配置均处于应用层的APP，MediaServer，流量管理平台，和处于IP层的Netfilter来完成应用程序的流量管理方法。请参阅图1，显示为终端设备系统配置结构示意图。
请参阅图2，显示为应用程序的流量管理方法于一实施例中的流程示意图。在本实施例中，仅提供流量的管理，所述流量包括mediaPlayer流量和非mediaPlayer流量。如图2所示，所述应用程序的流量管理方法具体包括以下几个步骤：
S1，初始化所述终端设备。
S2，接收流量访问的请求，并获知接收到流量访问的请求是应用程序(APP)直接发送的数据包，还是应用程序(APP)通过媒体服务器(MediaServer)发送的流量访问的数据包。例如，当APP调用MediaPlayer播放视频时，由于MediaPlayer的架构是C/S(客户机/服务器)结构，App实际通过MediaPlayer的客户端向MediaServer发送视频播放请求的，此时视频播放请求由MediaServer发出。在本实施例中，所述用以请求播放视频的数据包包括来源于指定播放工具的数据包和非来源于指定播放工具的数据包。所述来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包发送至Netfilter。在本实施例中，所述指定播放工具为安卓系统的MediaServer组件。在本实施例中，步骤S2还包括在所述来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包发送至代理服务器或源站的过程中，所述流量管理平台拦截应用程序发送的数据包，即拦截所述来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包。在本实施例中，在拦截应用程序发送的的数据包之前，所述终端设备一直处于等待拦截所述数据包的等候状态。
S3，所述来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包进入Netfilter后，利用网络防火墙重定向所述来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包。
其中，iptable语法为：iptable[-t table]command[chain][match][-j target]
注释：iptable[-t表名]-命令[链接][匹配][-j动作/目标]。
S4，所述流量管理平台读取所述来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包的用于表示其来源的属性信息。在本实施例中，所述数据包用于表示其来源的属性信息包括数据包的源端口信息，即读取来源于指定播放工具的数据包的源端口信息和非来源于指定播放工具的数据包的源端口信息。
S5，所述流量管理平台根据该数据包的属性信息，判断发送该数据包的应用程序是否为指定播放工具以对来源于指定播放工具的数据包和非来源于指定播放工具的数据包进行区别 流量管理。在本实施例中，所述指定播放工具为MediaPlayer(媒体播放器)。因为，现有很多应用程序均是通过调用MediaPlayer来播放视频的。请参阅图3，显示为步骤S5的流程示意图。如图3所示，所述步骤S5具体包括以下几个步骤：
S51，将所述数据包的属性信息，即将来源于指定播放工具的数据包的源端口信息和非来源于指定播放工具的数据包的源端口信息转换为发送来源于指定播放工具的数据包和非来源于指定播放工具的数据包的应用程序对应的标识符。具体地，根据所述数据包的源端口信息，在用于记录TCP连接状况的第一查询表中映射查找与所述发送数据包的源端口信息匹配的标识符。在本实施例中，所述第一查询表为/proc/net/tcp(udp)；所述标识符为UID。
S52，判断所述应用程序对应的标识符是否为与所述指定播放工具的标识符；若是，则表示该应用程序为指定播放工具(MediaPlayer)，执行步骤S53；若否，则表示该应用程序为非指定播放工具(MediaPlayer)，执行步骤S54。在本实施例中，前台进程的标识符为1013。在终端设备中，安装APP和媒体服务器时，系统会给APP统一分配一UID，其中通过指定播放工具发出的数据包的APP的UID固定为1013。
S53，判定该应用程序为指定播放工具(MediaPlayer)，查询前台进程，将来源于指定播放工具的数据包的包名映射成所述前台进程的包名。在本实例中，当应用程序APP调用MediaPlayerr流量访问时，UID为1013的来源于指定播放工具的数据包是由前台进程触发的，因此，将触发来源于指定播放工具的数据包的包名映射成为前台进程的包名。
S54，判定该应用程序为非指定播放工具，将所述应用程序的标识符转化成所述应用程序的包名。具体地，根据非指定播放工具(MediaPlayer)进行流量访问的应用程序的标识符，获取该应用程序的包名，并记录下来。在本实施例中，根据所述应用程序对应的标识符，在用于记录发送数据包的应用程序的包名的第二查询表，即本实施例中/data/system/package.xml表中查找与所述标识符匹配的应用程序的包名；或根据用于查找发送数据包的应用程序的包名的查找接口，即本实施例中的SDK接口getPackagesForUid，查找该应用程序的包名，并根据查找到的包名，记录下来；并将所述应用程序的标识符转换成所述应用程序的包名。
S6，根据包名设置为的前台进程的应用程序和非前台进程的应用程序的包名发出的流量进行管理。在本实施例中，对不同应用程序发出的流量进行管理包括对流量做引导、流量统计等。
本实施例所述的应用程序的流量管理方法实现了对不同应用程序的流量进行精确管理，并且不需要APP的干预，不需要对终端设备系统架构进行改动。
实施例二
本实施例提供一种应用程序的流量管理系统2，该系统2应用于终端设备1。请参阅图4，显示为应用程序的流量管理系统于一实施例中的原理结构示意图。如图4所示，所述应用程序的流量管理系统2包括：初始化模块21、接收模块22、重定向模块23、读取模块24、及管理模块25。
初始化模块21用于初始化所述终端设备。
与初始化模块21连接的接收模块22用于接收流量访问的请求，并获知接收到流量访问的请求是APP直接发送的数据包，还是APP通过媒体服务器(MediaServer)发送的数据包。在本实施例中，当APP调用MediaPlayer播放视频时，由于MediaPlayer的架构是C/S(客户机/服务器)结构，App实际通过MediaPlayer的客户端向MediaServer发送视频播放请求的，此时视频播放请求由MediaServer发出。在本实施例中，所述用以请求播放视频的数据包包括通过位于终端设备内的媒体服务器转发的来源于指定播放工具的数据包和未通过所述媒体服务器转发的非来源于指定播放工具的数据包。所述来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包发送至Netfilter。且所述接收模块22还用于在应用程序发送的数据包发送至远程服务器或源站的过程中，所述流量管理平台拦截来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包。在本实施例中，在拦截来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包之前，所述终端设备一直处于等待拦截所述数据包的等候状态。
与接收模块22连接的重定向模块23用于在所述来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包进入内置于重定向模块23中的Netfilter后，利用网络防火墙重定向所述来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包。例如，利用iptable重定向所述来源于指定播放工具的数据包。
与接收模块22和重定向模块23连接的读取模块24用于读取来源于指定播放工具的数据包和所述非来源于指定播放工具的数据包的用于表示其来源的属性信息。在本实施例中，所述数据包用于表示其来源的属性信息包括数据包的源端口信息，即读取来源于指定播放工具的数据包的源端口信息和非来源于指定播放工具的数据包的源端口信息。
与所述读取模块24连接的管理模块25用于根据该数据包的属性信息，判断发送该数据包的应用程序是否为调用指定播放工具播放视频的应用程序以管理不同应用程序的流量。请参阅图5，显示为管理模块的原理结构示意图。如图5所示，所述管理模块25具体包括：转换单元251、处理单元252、流量管理单元253。
转换单元251用于将所述数据包的属性信息，即将来源于指定播放工具的数据包的源端 口信息和非来源于指定播放工具的数据包的源端口信息转换为发送来源于指定播放工具的数据包和非来源于指定播放工具的数据包的应用程序对应的标识符。具体地，根据所述数据包的源端口信息，在用于记录TCP连接状况的第一查询表中映射查找与所述发送数据包的源端口信息匹配的标识符。在本实施例中，所述第一查询表为/proc/net/tcp(udp)；所述标识符为UID。
与转换单元251连接的处理单元252用于判断所述指定播放工具对应的标识符；若是，则表示该应用程序为指定播放工具(MediaPlayer)，查询前台进程，将来源于指定播放工具的数据包的包名映射成所述前台进程的包名；若否，则表示该应用程序为非指定播放工具(MediaPlayer)，将所述应用程序的标识符转换成所述应用程序的包名。在本实施例中，根据所述应用程序对应的标识符，在用于记录发送数据包的应用程序的包名的第二查询表，即本实施例中/data/system/package.xml表中查找与所述标识符匹配的应用程序的包名；或根据用于查找发送数据包的应用程序的包名的查找接口，即本实施例中的SDK接口getPackagesForUid，查找该应用程序的包名，并根据查找到的包名来记录，并将所述应用程序的标识符转换成该应用程序的包名。在本实施例中，前台进程的标识符为1013。在终端设备中，安装APP和媒体服务器时，系统会给APP统一分配一UID，其中指定播放工具的数据包的APP的UID固定为1013。在本实施例中，所述处理单元262判定该应用程序为非指定播放工具时，将所述应用程序的标识符转化成所述应用程序的包名。具体地，根据非指定播放工具(MediaPlayer)进行流量访问的应用程序的标识符，获取该应用程序的包名，并记录下来。在本实施例中，根据所述应用程序对应的标识符，在用于记录发送数据包的应用程序的包名的第二查询表，即本实施例中/data/system/package.xml表中查找与所述标识符匹配的应用程序的包名；或根据用于查找发送数据包的应用程序的包名的查找接口，即本实施例中的SDK接口getPackagesForUid，查找该应用程序的包名，并根据查找到的包名，记录下来；并将所述应用程序的标识符转换成所述应用程序的包名。
与处理单元252连接的流量管理单元253用于根据包名设置为的前台进程的应用程序和非前台进程的应用程序的包名发出的音/流量进行管理。在本实施例中，对不同应用程序发出的流量进行管理包括对流量做引导、流量统计等。
本实施例还提供终端设备1，请参阅图7，显示为终端设备于一实施例中的原理结构示意图。如图7所示，所述终端设备1包括上述的应用程序的流量管理系统2。所述终端设备为机顶盒、平板电脑、手机中的任意一种。
综上所述，本发明所述的应用程序的流量管理方法、系统及具有该系统的终端设备实现 了对不同应用程序的流量进行精确管理，并且不需要APP的干预，不需要对终端设备系统架构进行改动。所以，本发明有效克服了现有技术中的种种缺点而具高度产业利用价值。
上述实施例仅例示性说明本发明的原理及其功效，而非用于限制本发明。任何熟悉此技术的人士皆可在不违背本发明的精神及范畴下，对上述实施例进行修饰或改变。因此，举凡所属技术领域中具有通常知识者在未脱离本发明所揭示的精神与技术思想下所完成的一切等效修饰或改变，仍应由本发明的权利要求所涵盖。

Claims (10)

  1. 一种应用程序的流量管理方法，其特征在于，所述应用程序的流量管理方法包括以下步骤：
    读取所述应用程序发送的数据包的用于表示其来源的属性信息；
    根据该数据包的属性信息，判断发送该数据包的应用程序是否为指定播放工具，以对来源于指定播放工具的数据包和非来源于指定播放工具的数据包进行区别管理。
  2. 根据权利要求1所述的应用程序的流量管理方法，其特征在于：所述判断发送该数据包的应用程序是否为指定播放工具，以对来源于指定播放工具的数据包和非来源于指定播放工具的数据包进行区别管理的步骤包括：
    将所述数据包的属性信息转换为发送该数据包的应用程序对应的标识符；
    判断所述应用程序对应的标识符是否为所述指定播放工具的标识符；若是，则表示该应用程序为指定播放工具，查询前台进程，将所述数据包的包名映射成所述前台进程的包名；
    若否，将所述应用程序的标识符转化成所述应用程序的包名。
  3. 根据权利要求2所述的应用程序的流量管理方法，其特征在于：所述数据包用于表示其来源的属性信息包括数据包的源端口信息；所述将所述数据包的属性信息转换为发送该数据包的应用程序对应的标识符的步骤为根据所述数据包的源端口信息，在用于记录TCP连接状况的第一查询表中映射查找与所述发送数据包的源端口信息匹配的标识符。
  4. 根据权利要求2所述的应用程序的流量管理方法，其特征在于：在判断所述应用程序对应的标识符不为指定播放工具的标识符时，将所述应用程序的标识符转化成所述应用程序包名的步骤包括：
    根据所述应用程序对应的标识符，在用于记录发送数据包的应用程序的包名的第二查询表中查找与所述标识符匹配的应用程序的包名；或
    根据用于查找发送数据包的应用程序的包名的查找接口，查找该应用程序的包名；
    将所述应用程序的标识符转化成所述应用程序包名。
  5. 根据权利要求1所述的应用程序的流量管理方法，其特征在于：
    所述指定播放工具为安卓系统的MediaServer组件。
  6. 一种应用程序的流量管理系统，其特征在于，所述应用程序的流量管理系统包括：
    读取模块，用于读取所述应用程序发送的数据包的用于表示其来源的属性信息；
    管理模块，用于根据该数据包的属性信息，判断发送该数据包的应用程序是否为指定播放工具，以对来源于指定播放工具的数据包和非来源于指定播放工具的数据包进行区别管理。
  7. 根据权利要求6所述的应用程序的流量管理系统，其特征在于：所述管理模块包括：
    转换单元，用于将所述数据包的属性信息转换为发送该数据包的应用程序对应的标识符；
    处理单元，用于判断所述应用程序对应的标识符是否为所述指定播放工具的标识符；若是，则表示该应用程序为指定播放工具，查询前台进程，将所述数据包的包名映射成所述前台进程的包名。
  8. 根据权利要求7所述的应用程序的流量管理系统，其特征在于：所述数据包用于表示其来源的属性信息包括数据包的源端口信息；所述转换单元用于根据所述数据包的源端口信息，在用于记录TCP连接状况的第一查询表中映射查找与所述发送数据包的源端口信息匹配的标识符。
  9. 根据权利要求7所述的应用程序的流量管理系统，其特征在于：所述处理单元在判断所述应用程序对应的标识符不为指定播放工具的标识符时，根据所述应用程序对应的标识符，在用于记录发送数据包的应用程序的包名的第二查询表中查找与所述标识符匹配的应用程序的包名；或根据用于查找发送数据包的应用程序的包名的查找接口，查找该应用程序的包名；将所述应用程序的标识符转化成所述应用程序包名。
  10. 一种终端设备，其特征在于，所述终端设备包括：如权利要求6-9中任一项所述的应用程序的流量管理系统。
PCT/CN2016/106054 2016-10-10 2016-11-16 应用程序的流量管理方法、系统及具有该系统的终端设备 WO2018068361A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16918622.8A EP3445010B1 (en) 2016-10-10 2016-11-16 Application program traffic management method, system and terminal device having the system
US16/092,906 US10680962B2 (en) 2016-10-10 2016-11-16 Method and system for managing traffic of application programs, and terminal device containing the system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610882916.3A CN106533974B (zh) 2016-10-10 2016-10-10 应用程序的流量管理方法、系统及具有该系统的终端设备
CN201610882916.3 2016-10-10

Publications (1)

Publication Number Publication Date
WO2018068361A1 true WO2018068361A1 (zh) 2018-04-19

Family

ID=58331266

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/106054 WO2018068361A1 (zh) 2016-10-10 2016-11-16 应用程序的流量管理方法、系统及具有该系统的终端设备

Country Status (4)

Country Link
US (1) US10680962B2 (zh)
EP (1) EP3445010B1 (zh)
CN (1) CN106533974B (zh)
WO (1) WO2018068361A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107124370B (zh) * 2017-05-05 2020-01-03 网宿科技股份有限公司 机顶盒及其流量管控方法和业务请求流量管控系统
CN107483593B (zh) * 2017-08-22 2019-12-31 网宿科技股份有限公司 双向透明代理方法及系统
CN112804251B (zh) * 2021-02-01 2022-04-15 哈尔滨工业大学 一种基于userId的Android应用流量过滤方法与系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101902484A (zh) * 2009-05-25 2010-12-01 北京启明星辰信息技术股份有限公司 局域网http应用业务分类方法及系统
CN103036803A (zh) * 2012-12-21 2013-04-10 南京邮电大学 一种基于应用层检测的流量控制方法
CN103582512A (zh) * 2013-02-04 2014-02-12 华为技术有限公司 特征提取装置、网络流量识别方法、装置和系统
US20150215219A1 (en) * 2014-01-30 2015-07-30 Telefonaktiebolaget L M Ericsson (Publ) Service Specific Traffic Handling

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8151323B2 (en) * 2006-04-12 2012-04-03 Citrix Systems, Inc. Systems and methods for providing levels of access and action control via an SSL VPN appliance
BR112012006280B1 (pt) * 2009-09-22 2020-12-01 Telefonaktiebolaget Lm Ericsson método para apresentar uma notificação de televisão de protocolo de internet para equipamento de usuário e equipamento de usuário
US8270420B2 (en) * 2009-12-15 2012-09-18 Hewlett-Packard Development Company, L.P. iSCSI to FCoE gateway
US8155625B2 (en) * 2009-12-22 2012-04-10 Motorola Mobility, Inc. Methods and apparatus for conserving energy used by a mobile device
US20120324568A1 (en) * 2011-06-14 2012-12-20 Lookout, Inc., A California Corporation Mobile web protection
KR101380966B1 (ko) * 2011-08-24 2014-05-02 주식회사 팬택 휴대 단말 시스템에서의 보안 장치
US8918881B2 (en) * 2012-02-24 2014-12-23 Appthority, Inc. Off-device anti-malware protection for mobile devices
US8819844B2 (en) * 2012-03-30 2014-08-26 Aeris Communications, Inc. Method and system for data implant in set up message
US9473355B2 (en) * 2013-03-14 2016-10-18 Amazon Technologies, Inc. Inferring application inventory
CN104283873B (zh) * 2014-09-28 2017-06-23 深圳市九洲电器有限公司 基于多网卡设备下数字媒体服务器的实现方法及系统
CN105553955B (zh) * 2015-12-09 2020-04-03 上海安吉星信息服务有限公司 一种数据处理方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101902484A (zh) * 2009-05-25 2010-12-01 北京启明星辰信息技术股份有限公司 局域网http应用业务分类方法及系统
CN103036803A (zh) * 2012-12-21 2013-04-10 南京邮电大学 一种基于应用层检测的流量控制方法
CN103582512A (zh) * 2013-02-04 2014-02-12 华为技术有限公司 特征提取装置、网络流量识别方法、装置和系统
US20150215219A1 (en) * 2014-01-30 2015-07-30 Telefonaktiebolaget L M Ericsson (Publ) Service Specific Traffic Handling

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP3445010A4 (en) 2019-05-08
EP3445010B1 (en) 2020-09-23
CN106533974A (zh) 2017-03-22
US20190173799A1 (en) 2019-06-06
EP3445010A1 (en) 2019-02-20
US10680962B2 (en) 2020-06-09
CN106533974B (zh) 2020-04-07

Similar Documents

Publication Publication Date Title
WO2017114206A1 (zh) 短链接处理方法、装置及短链接服务器
US20140304381A1 (en) Method and apparatus for communicating with smart objects
CN114025021B (zh) 一种跨Kubernetes集群的通信方法、系统、介质和电子设备
CN107222326B (zh) 用于设备间服务的访问方法、配置方法及装置
CN104754003B (zh) 传输数据的方法及系统
CN103346972A (zh) 基于用户终端的流量控制装置和方法
TWI528182B (zh) 處理程序間通訊的方法及裝置
CN114338594B (zh) 在Kubernetes环境下的ARP代答方法、装置、设备及存储介质
TWI674780B (zh) 網路服務系統及網路服務方法
WO2018068361A1 (zh) 应用程序的流量管理方法、系统及具有该系统的终端设备
WO2016041322A1 (zh) 移动智能终端下转发应用内流量的方法
CN107182053B (zh) 一种用于连接隐藏无线接入点的方法与设备
US11611620B2 (en) Method and system for triggering an online interaction in connection with a physical product
US20220286495A1 (en) Domain Name Query Method and Related Device
CN109905380A (zh) 一种分布式系统中的节点控制方法和相关装置
WO2020125074A1 (zh) 消息到达率确定方法、装置、数据统计服务器及存储介质
US10374946B2 (en) Centralized wireless network management system
CN108536617A (zh) 缓存管理方法、介质、系统和电子设备
CN112445700A (zh) 测试方法和装置
KR101899970B1 (ko) 모바일 클라우드 환경에 적용되는 모바일 단말과 클라우드 서버 및 이를 이용한 모바일 클라우드 컴퓨팅 방법
CN103414713A (zh) 一种访问云端媒体资源的方法、装置和dlna设备
TWI814877B (zh) 將重定向的生物辨識裝置隔離到遠程會話
CN112787947B (zh) 网络业务的处理方法、系统和网关设备
WO2015192497A1 (zh) 通信链路的发送方法、装置及终端
US20200104787A1 (en) Method and system for triggering an online interaction in connection with a physical product

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2016918622

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016918622

Country of ref document: EP

Effective date: 20181116

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

Ref document number: 16918622

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE