WO2016019714A1 - 外部设备与路由器之间连接情况的通知方法及装置 - Google Patents

外部设备与路由器之间连接情况的通知方法及装置 Download PDF

Info

Publication number
WO2016019714A1
WO2016019714A1 PCT/CN2015/072032 CN2015072032W WO2016019714A1 WO 2016019714 A1 WO2016019714 A1 WO 2016019714A1 CN 2015072032 W CN2015072032 W CN 2015072032W WO 2016019714 A1 WO2016019714 A1 WO 2016019714A1
Authority
WO
WIPO (PCT)
Prior art keywords
port
plug
router
plugin
notification
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2015/072032
Other languages
English (en)
French (fr)
Inventor
刘铁俊
程亮
李政
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Xiaomi Inc
Original Assignee
Xiaomi 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 Xiaomi Inc filed Critical Xiaomi Inc
Priority to KR1020157014271A priority Critical patent/KR101776445B1/ko
Priority to JP2016539414A priority patent/JP2016534653A/ja
Priority to MX2015006163A priority patent/MX360570B/es
Priority to BR112015012468A priority patent/BR112015012468A2/pt
Priority to RU2015120927A priority patent/RU2632395C2/ru
Priority to US14/715,887 priority patent/US20160041854A1/en
Publication of WO2016019714A1 publication Critical patent/WO2016019714A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324—Display of status information
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H04L41/0809—Plug-and-play configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity

Definitions

  • the present disclosure relates to the field of plug-in platform navigation technologies for routers, and more particularly to a method and apparatus for notifying a connection between an external device and a router.
  • the router developer adds the function of the plug-in platform to the router, and the third-party developer can develop the plug-in according to the document published by the router developer and the SDK (Software Development Kit).
  • the plugin can run on the plugin platform.
  • the router cannot connect the external device with The connection information between the routers is notified to the plug-in, and the plug-in cannot obtain the connection between the external device and the router, and the plug-in function is not convenient.
  • the embodiments of the present disclosure provide a method and a device for notifying a connection between an external device and a router, and notify a plug-in of the router between the connection between the external device and the router, so as to facilitate the function of the plug-in. Play.
  • a notification method for a connection between an external device and a router includes:
  • the preset behavior including that an external device is connected to the router, or the external device is disconnected from the router;
  • the monitoring whether a preset behavior occurs may include:
  • determining a registration port of the plugin of the router in a port of the plugin management center may include:
  • the method may further include:
  • the one-to-one correspondence is stored.
  • the first notification is sent to the plugin by using a registration port of the plugin, where the first notification is used to indicate that the preset behavior occurs, which may include:
  • the first notification being sent by the lightweight server to the plugin via a registration port of the plugin.
  • a notification device for a connection between an external device and a router comprising:
  • a monitoring module configured to monitor whether a preset behavior occurs, where the preset behavior includes that an external device is connected to the router, or the external device releases the connection with the router;
  • a determining module configured to: when the monitoring module detects that the preset behavior occurs, determine, in a port of the plug-in management center, a registration port of the plug-in of the router;
  • a notification module configured to send, by using the registration port of the plug-in determined by the determining module, a first notification to the plug-in, where the first notification is used to indicate that the preset behavior occurs.
  • the monitoring module can include:
  • a monitoring unit configured to monitor whether a second notification is received, where the second notification is used to indicate that the preset behavior occurs.
  • the determining module may include:
  • a determining unit configured to: when the monitoring module detects that the preset behavior occurs, according to a one-to-one correspondence between the pre-stored port of the plug-in management center and the plug-in of the router, in the plug-in management center In the port, determine the registered port of the plugin.
  • the apparatus may further include:
  • An obtaining module configured to obtain a port registration request sent by the plugin
  • a storage module configured to store the one-to-one correspondence.
  • the notification module can include:
  • a boot unit a lightweight web server for launching the plugin
  • a notification unit configured to connect to the lightweight web server by SOCKET communication, and send, by the lightweight server, the first notification to the plugin through a registration port of the plugin.
  • a notification apparatus for connecting a connection between an external device and a router includes:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the preset behavior including that an external device is connected to the router, or the external device is disconnected from the router;
  • the PluginCenter of the router notifies the plug-in of the router of the occurrence of the behavior.
  • the plug-in of the router is informed of the connection between the external device and the router, so that the plug-in of the router can fully utilize the function of the plug-in by using the external device, thereby improving the user experience of the plug-in.
  • FIG. 1 is a flowchart of a method for notifying a connection between an external device and a router according to an exemplary embodiment.
  • FIG. 2 is a flowchart of a method for notifying a connection between another external device and a router according to an exemplary embodiment.
  • FIG. 3 is a block diagram of a notification device for a connection between an external device and a router, according to an exemplary embodiment.
  • FIG. 4 is a block diagram of a notification device of another connection situation between an external device and a router, according to an exemplary embodiment.
  • FIG. 5 is a block diagram of a notification module, according to an exemplary embodiment.
  • FIG. 1 is a schematic diagram of a method for notifying a connection between an external device and a router according to an embodiment of the present disclosure.
  • the method is used for a PluginCenter of a router, and the PluginCenter may be a background program initiated by a router, such as As shown in FIG. 1, the method includes the following steps S101-S103:
  • step S101 it is monitored whether a preset behavior occurs, and the preset behavior may be that an external device is connected to the router (that is, an external device is inserted into the router), or the external device is disconnected from the router (ie, the external device is disconnected from the router) Remove).
  • the preset behavior may be that an external device is connected to the router (that is, an external device is inserted into the router), or the external device is disconnected from the router (ie, the external device is disconnected from the router) Remove).
  • step S101 may be implemented to monitor whether a second notification is received, and the second notification is used to indicate that a preset behavior has occurred.
  • the monitoring device in the router monitors whether a preset behavior has occurred, and when it occurs, the monitoring device sends a second notification to the plug-in management center.
  • the external interface is configured on the router, and the external interface is used to connect the external device.
  • the external interface may be a wired interface or a wireless interface, that is, the router and the external device may be wired or wireless.
  • the external interface accesses the external interface, or the external device is removed from the external interface, the external interface sends a second notification to the plugin management module of the router.
  • step S102 when the preset behavior occurs, in the port of the PluginCenter, the registration port of the plugin of the router is determined.
  • step S102 may be implemented as: when a preset behavior occurs, determining a registration port of the plugin in the port of the PluginCenter according to a one-to-one correspondence between the pre-stored PluginCenter port and the plugin of the router.
  • the one-to-one correspondence may be stored in a configuration file, and in addition to recording the one-to-one correspondence, the configuration file may also declare the capability possessed by the plug-in.
  • a configuration file is stored in the PluginCenter, and the format of the record is a key-value type, and the configuration file includes three parameters: appid, port, and capability. Where appid is the ID of the plugin, port is the registered port number of the plugin, and capability indicates the capabilities of the plugin.
  • a configuration file includes the following:
  • the plug-in with ID is 2919291939
  • its registration port is port 10001 of PluginCenter, which can know that a USB device is connected to the router, or the USB device is disconnected from the router.
  • step S103 a first notification is sent to the plugin through the registration port of the plugin, and the first notification is used to indicate that the preset behavior occurs.
  • step S103 can be implemented as: launching a plug-in lightweight web server thrift server; connecting to the plug-in thrift server through a socket SOCKET communication, and sending the above to the plug-in through the plug-in registration port of the plug-in thrift server First notice.
  • the PluginCenter of the router notifies the plug-in of the router to the occurrence of the behavior.
  • the plug-in of the router learns the connection between the external device and the router, so that the plug-in of the router can fully utilize the function of the plug-in by using the external device, thereby improving the user experience of the plug-in.
  • the foregoing method may further include: establishing the one-to-one correspondence, and causing the PluginCenter to store the one-to-one correspondence, the process comprising the following steps A1-A3:
  • Step A1 Obtain a port registration request sent by the plugin.
  • Step A2 Query the idle port in the port of the plug-in management center, register the plug-in to the free port, and establish a one-to-one correspondence between the registered port of the plug-in and the plug-in.
  • step A3 a one-to-one correspondence is stored.
  • the process of querying and registering can be performed by a preset program.
  • the above steps A A1-A3 can be performed as follows: obtaining a request for calling a preset program interface sent by the plug-in; and starting the above-mentioned preset program, by the above preset
  • the program queries the free port in the port of the PluginCenter, registers the plug-in to the free port, and establishes a one-to-one correspondence between the registered port of the plug-in and the plug-in by the preset program; receiving the above-mentioned one sent by the preset program A correspondence relationship and storing the one-to-one correspondence described above.
  • the above preset program may be an SDK (Software Development Kit, Software Development Kit Application) or other types of applications.
  • the external device is a USB device
  • the router starts the background program PluginCenter after the startup. As shown in FIG. 2, the embodiment includes the following steps:
  • step S201 the plugin X of the router invokes the SDK API opened by the plugin platform.
  • step S202 the SDK API starts incrementing the port number from a preset port number (such as 10000) on the PluginCenter and determines whether the registered port of the incremented port number is an idle port.
  • a preset port number such as 10000
  • step S203 when the USB device is plugged into the USB port of the router, the monitoring device in the router will detect that this behavior occurs.
  • step S204 the monitoring device in the router invokes a script program that sends a notification message to the PluginCenter, which is used to indicate that a USB device is connected to the router.
  • step S205 after receiving the notification message, the PluginCenter scans the configuration file, finds the registration port number of the plug-in X, and starts the thrift server of the plug-in X.
  • step S206 the PluginCenter is connected to the thrift server of the plug-in X through the SOCKET communication.
  • step S207 the thrift server of the plug-in X sends a notification message to the plug-in X through the registration port of the plug-in X, the notification message is used to indicate that a USB device is connected to the router.
  • the PluginCenter of the router notifies the plugin of the router of the occurrence of the behavior, so that the plugin of the router is known.
  • the connection between the USB device and the router enables the plug-in of the router to fully utilize the functions of the plug-in by using the USB device, thereby improving the user experience of the plug-in.
  • FIG. 3 is a device for notifying a connection between an external device and a router according to an embodiment of the present disclosure, which may be used in a plug-in management center of a router or a router, including:
  • the monitoring module 31 is configured to monitor whether a preset behavior occurs, and the preset behavior includes that an external device is connected to the router, or the external device is disconnected from the router;
  • a determining module 32 configured to: when the monitoring module 31 detects that a preset behavior occurs, determine, in a port of the plug-in management center, a registration port of the plug-in of the router;
  • the notification module 33 is configured to send a first notification to the plug-in by using the registration port of the plug-in determined by the determining module 32, where the first notification is used to indicate that the preset behavior occurs.
  • the monitoring module may include:
  • the monitoring unit is configured to monitor whether the second notification is received, and the second notification is used to indicate that the preset behavior has occurred.
  • the determining module may include:
  • a determining unit configured to determine, according to a one-to-one correspondence between a port of the pre-stored plug-in management center and a plug-in of the router, when the monitoring module detects the preset behavior, determine the registration end of the plug-in in the port of the plug-in management center mouth.
  • the foregoing apparatus may further include:
  • the obtaining module 41 is configured to obtain a port registration request sent by the plug-in;
  • the establishing module 42 is configured to query the idle port in the port of the plug-in management center, register the plug-in to the free port, and establish a one-to-one correspondence between the registered port of the plug-in and the plug-in;
  • the storage module 43 is configured to store a one-to-one correspondence.
  • the foregoing notification module 33 may include:
  • a startup unit 51 a lightweight web server for starting the plugin
  • the notification unit 52 is configured to connect to the lightweight web server through the SOCKET communication, and send the first notification to the plug-in by the lightweight server through the registration port of the plug-in.
  • a notification device for connecting between an external device and a router which can be used for a plug-in management center of a router or a router, including:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the first notification is sent to the plugin through the registration port of the plugin, and the first notification is used to indicate that the preset behavior occurs.
  • the processor is also configured to:
  • the processor is also configured to:
  • the processor is also configured to:
  • the one-to-one correspondence is stored.
  • the processor is also configured to:
  • the first notification being sent by the lightweight server to the plugin via a registration port of the plugin.
  • the foregoing apparatus notifies the plug-in of the router to the router plug-in through the PluginCenter of the router when an external device is connected to the router or the external device releases the connection with the router.
  • the plug-in of the router learns the connection between the external device and the router, so that the plug-in of the router can fully utilize the function of the plug-in by using the external device, thereby improving the user experience of the plug-in.
  • a non-transitory computer readable storage medium when instructions in the storage medium are executed by a processor of a client, enabling a client to perform a notification method of a connection between an external device and a router, the method comprising :
  • the first notification is sent to the plugin through the registration port of the plugin, and the first notification is used to indicate that the preset behavior occurs.
  • whether the foregoing monitoring has a preset behavior may include:
  • determining the registration port of the plug-in of the router in the port of the plug-in management center may include:
  • the registered port of the plug-in is determined in the port of the plug-in management center.
  • the above method may further include:
  • the one-to-one correspondence is stored.
  • the first notification is sent to the plugin by using the registration port of the plugin, where the first notification is used to indicate that the preset behavior occurs, which may include:
  • the first notification is sent by the lightweight server to the plugin via the registration port of the plugin.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Computing Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Computer And Data Communications (AREA)

Abstract

本公开是关于外部设备与路由器之间连接情况的通知方法及装置，用以将外部设备与路由器之间的连接情况通知给路由器的插件，便于插件功能的发挥。方法包括：监测是否发生预设行为，所述预设行为包括有外部设备连接到了路由器上、或者所述外部设备解除了与所述路由器的连接；当发生所述预设行为时，在所述插件管理中心的端口中，确定所述路由器的插件的注册端口；通过所述插件的注册端口，向所述插件发送第一通知，所述第一通知用于表明发生所述预设行为。该技术方案能够将外部设备与路由器之间的连接情况通知给路由器的插件，便于插件功能的发挥。

Description

外部设备与路由器之间连接情况的通知方法及装置
相关申请的交叉引用
本申请基于申请号为201410389817.2、申请日为2014/8/8的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及路由器的插件平台导航技术领域，尤其涉及外部设备与路由器之间连接情况的通知方法及装置。
背景技术
相关技术中，路由器开发者在路由器上加入了插件平台的功能，第三方开发者只要根据路由器开发者公布的文档和SDK(Software Development Kit，软件开发工具包)就能进行插件的开发，开发出来的插件能在插件平台上运行。
但是，当路由器上有外部设备连接到路由器上(即由外部设备插入路由器)、或者当外部设备解除了与路由器的连接(即外部设备从路由器上移除)时，路由器并不能将外部设备与路由器之间的连接情况信息通知给插件，插件不能获取外部设备与路由器之间的连接情况，不便于插件功能的发挥。
发明内容
为克服相关技术中存在的问题，本公开实施例提供外部设备与路由器之间连接情况的通知方法及装置，用以将外部设备与路由器之间的连接情况通知给路由器的插件，便于插件功能的发挥。
根据本公开实施例的第一方面，提供一种外部设备与路由器之间连接情况的通知方法，用于所述路由器的插件管理中心PluginCenter，包括：
监测是否发生预设行为，所述预设行为包括有外部设备连接到了路由器上、或者所述外部设备解除了与所述路由器的连接；
当发生所述预设行为时，在所述插件管理中心的端口中，确定所述路由器的插件的注册端口；
通过所述插件的注册端口，向所述插件发送第一通知，所述第一通知用于表明发生所述预设行为。
在一个实施例中，所述监测是否发生了预设行为，可包括：
监测是否接收到第二通知，所述第二通知用于表明发生了所述预设行为。
在一个实施例中，所述当发生所述预设行为时，在所述插件管理中心的端口中，确定所述路由器的插件的注册端口，可包括：
当发生所述预设行为时，根据预存的所述插件管理中心的端口与所述路由器的插件之间的一一对应关系，在所述插件管理中心的端口中，确定所述插件的注册端口。
在一个实施例中，所述方法还可包括：
获取所述插件发送来的端口注册请求；
查询所述插件管理中心的端口中的空闲端口，将所述插件注册到所述空闲端口上，并建立所述插件的注册端口与所述插件之间的一一对应关系；
存储所述一一对应关系。
在一个实施例中，所述通过所述插件的注册端口，向所述插件发送第一通知，所述第一通知用于表明发生所述预设行为，可包括：
启动所述插件的轻量级网络服务器；
通过套接字SOCKET通信连接到所述轻量级网络服务器，由所述轻量级服务器通过所述插件的注册端口向所述插件发送所述第一通知。
根据本公开实施例的第二方面，提供一种外部设备与路由器之间连接情况的通知装置，包括：
监测模块，用于监测是否发生预设行为，所述预设行为包括有外部设备连接到了路由器上、或者所述外部设备解除了与所述路由器的连接；
确定模块，用于当所述监测模块监测到发生所述预设行为时，在所述插件管理中心的端口中，确定所述路由器的插件的注册端口；
通知模块，用于通过所述确定模块确定的所述插件的注册端口，向所述插件发送第一通知，所述第一通知用于表明发生所述预设行为。
在一个实施例中，所述监测模块可包括：
监测单元，用于监测是否接收到第二通知，所述第二通知用于表明发生了所述预设行为。
在一个实施例中，所述确定模块可包括：
确定单元，用于当所述监测模块监测到发生所述预设行为时，根据预存的所述插件管理中心的端口与所述路由器的插件之间的一一对应关系，在所述插件管理中心的端口中，确定所述插件的注册端口。
在一个实施例中，所述装置还可包括：
获取模块，用于获取所述插件发送来的端口注册请求；
建立模块，用于查询所述插件管理中心的端口中的空闲端口，将所述插件注册到所述空 闲端口上，并建立所述插件的注册端口与所述插件之间的一一对应关系；
存储模块，用于存储所述一一对应关系。
在一个实施例中，所述通知模块可包括：
启动单元，用于启动所述插件的轻量级网络服务器；
通知单元，用于通过SOCKET通信连接到所述轻量级网络服务器，由所述轻量级服务器通过所述插件的注册端口向所述插件发送所述第一通知。
根据本公开实施例的第三方面，提供一种外部设备与路由器之间连接情况的通知装置，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
监测是否发生预设行为，所述预设行为包括有外部设备连接到了路由器上、或者所述外部设备解除了与所述路由器的连接；
当发生所述预设行为时，在所述插件管理中心的端口中，确定所述路由器的插件的注册端口；
通过所述插件的注册端口，向所述插件发送第一通知，所述第一通知用于表明发生所述预设行为。
本公开的实施例提供的技术方案可以包括以下有益效果：
本公开实施例提供的上述技术方案，当有外部设备连接到了路由器上、或者外部设备解除了与路由器的连接这些行为发生时，通过路由器的PluginCenter，将这些行为的发生情况通知给路由器的插件，使路由器的插件获知外部设备与路由器之间的连接情况，使路由器的插件能利用外部设备充分发挥插件的功能，提高插件的用户使用体验。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
图1是根据一示例性实施例示出的一种外部设备与路由器之间连接情况的通知方法的流程图。
图2是根据一示例性实施例示出的另一种外部设备与路由器之间连接情况的通知方法的流程图。
图3是根据一示例性实施例示出的一种外部设备与路由器之间连接情况的通知装置的框图。
图4是根据一示例性实施例示出的另一种外部设备与路由器之间连接情况的通知装置的框图。
图5是根据一示例性实施例示出的通知模块的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
图1所示为本公开实施例提供的一种外部设备与路由器之间连接情况的通知方法，该方法用于路由器的PluginCenter(插件管理中心)，该PluginCenter可以是路由器启动的一个后台程序，如图1所示，该方法包括如下步骤S101-S103：
在步骤S101中，监测是否发生预设行为，预设行为可以是有外部设备连接到了路由器上(即有外部设备插入了路由器)、或者外部设备解除了与路由器的连接(即外部设备从路由器上移除)。
在一个实施例中，步骤S101可实施为：监测是否接收到第二通知，第二通知用于表明发生了预设行为。比如路由器中的监测装置监测是否发生了预设行为，当发生时，该监测装置将第二通知发送给插件管理中心。
其中，路由器上设置有外部接口，外部接口用于连接所述外部设备，外部接口可以为有线接口也可以是无线接口，也就是说路由器与外部设备可以使有线连接，也可以是无线连接。当外部设备接入到所述外部接口，或外部设备从所述外部接口移除时，外部接口向路由器的插件管理模块发送第二通知。
在步骤S102中，当发生预设行为时，在PluginCenter的端口中，确定路由器的插件的注册端口。
在一个实施例中，步骤S102可实施为：当发生预设行为时，根据预存的PluginCenter的端口与路由器的插件之间的一一对应关系，在PluginCenter的端口中，确定插件的注册端口。其中，上述一一对应关系可存储于一配置文件中，该配置文件中除了记录上述一一对应关系外，还可以申明插件拥有的能力。例如，PluginCenter中存储一个配置文件，记录的格式为key-value类型，该配置文件中包括三个参数appid、port和capability， 其中，appid表示插件的ID，port表示插件的注册端口号，capability表示插件拥有的能力，比如一个配置文件中包括以下内容：
appid＝2919291939,port＝10001,capability＝USBDISK
以上内容表示：ID为2919291939的插件，其注册端口为PluginCenter的10001号端口，其能够获知有USB设备连接到了路由器上、或者USB设备解除了与路由器的连接。
在步骤S103中，通过插件的注册端口，向插件发送第一通知，第一通知用于表明发生预设行为。
在一个实施例中，步骤S103可实施为：启动插件的轻量级网络服务器thrift server；通过套接字SOCKET通信连接到插件的thrift server，由插件的thrift server通过插件的注册端口向插件发送上述第一通知。
本公开实施例提供的上述方法，当有外部设备连接到了路由器上、或者外部设备解除了与路由器的连接这些行为发生时，通过路由器的PluginCenter，将这些行为的发生情况通知给路由器的插件，使路由器的插件获知外部设备与路由器之间的连接情况，使路由器的插件能利用外部设备充分发挥插件的功能，提高插件的用户使用体验。
在一个实施例中，上述方法还可以包括建立上述一一对应关系，使PluginCenter存储上述一一对应关系，该过程包括如下步骤A1-A3：
步骤A1，获取插件发送来的端口注册请求。
步骤A2，查询插件管理中心的端口中的空闲端口，将插件注册到空闲端口上，并建立插件的注册端口与插件之间的一一对应关系。
步骤A3，存储一一对应关系。
其中，查询和注册的过程可以由一个预设程序来执行，比如上述步骤A A1-A3可执行为：获取插件发送来的调用预设程序接口的请求；启动上述预设程序，由上述预设程序查询PluginCenter的端口中的空闲端口，将插件注册到该空闲端口上，并由上述预设程序建立插件的注册端口与插件之间的一一对应关系；接收上述预设程序发送来的上述一一对应关系，并存储上述一一对应关系。其中，上述预设程序可以是SDK(Software Development Kit,软件开发工具包应用程序)或者其它类型的应用程序。
下面以一具体实施例来说明本公开实施例提供的上述方法。
本实施例中，以外部设备为USB设备为例，路由器在启动后启动后台程序PluginCenter，如图2所示，本实施例包括如下步骤：
在步骤S201中，路由器的插件X调用插件平台开放出去的SDK API。
在步骤S202中，SDK API从PluginCenter上预设的一个端口号(如10000)开始递增端口号并判断递增后的端口号的注册端口是否为空闲端口，当发现递增后的端口号的注册端口已经被占用时，继续递增，直到找到空闲端口时，将插件X注册到该空闲端口上，将插件X的注册端口号、插件X的ID、插件X的capability对应记录到PluginCenter存储的配置文件中(假设appid＝2919291939，port＝10001，capability＝USBDISK)。
在步骤S203中，当USB设备插入到路由器的USB端口中，此时，路由器中的监测装置会监测到这一行为发生。
在步骤S204中，路由器中的监测装置调用一个脚本程序，该脚本程序将一通知消息发送给了PluginCenter，该通知消息用于表明有USB设备连接到了路由器上。
在步骤S205中，PluginCenter接收到上述通知消息之后，扫描上述配置文件，从中找到插件X的注册端口号，启动插件X的thrift server。
在步骤S206中，PluginCenter通过SOCKET通信连接到插件X的thrift server。
在步骤S207中，插件X的thrift server通过插件X的注册端口向插件X发送一通知消息，该通知消息用于表明有USB设备连接到了路由器上。
本实施例中，当有USB设备连接到了路由器上、或者USB设备解除了与路由器的连接这些行为发生时，通过路由器的PluginCenter，将这些行为的发生情况通知给路由器的插件，使路由器的插件获知USB设备与路由器之间的连接情况，使路由器的插件能利用USB设备充分发挥插件的功能，提高插件的用户使用体验。
图3为本公开实施例提供的一种外部设备与路由器之间连接情况的通知装置，可用于路由器或者路由器的插件管理中心，包括：
监测模块31，用于监测是否发生预设行为，预设行为包括有外部设备连接到了路由器上、或者外部设备解除了与路由器的连接；
确定模块32，用于当监测模块31监测到发生预设行为时，在插件管理中心的端口中，确定路由器的插件的注册端口；
通知模块33，用于通过确定模块32确定的插件的注册端口，向插件发送第一通知，第一通知用于表明发生预设行为。
在一个实施例中，上述监测模块可包括：
监测单元，用于监测是否接收到第二通知，第二通知用于表明发生了预设行为。
在一个实施例中，上述确定模块可包括：
确定单元，用于当监测模块监测到发生预设行为时，根据预存的插件管理中心的端口与路由器的插件之间的一一对应关系，在插件管理中心的端口中，确定插件的注册端 口。
在一个实施例中，如图4所示，上述装置还可包括：
获取模块41，用于获取插件发送来的端口注册请求；
建立模块42，用于查询插件管理中心的端口中的空闲端口，将插件注册到空闲端口上，并建立插件的注册端口与插件之间的一一对应关系；
存储模块43，用于存储一一对应关系。
在一个实施例中，如图5所示，上述通知模块33可包括：
启动单元51，用于启动插件的轻量级网络服务器；
通知单元52，用于通过SOCKET通信连接到轻量级网络服务器，由轻量级服务器通过插件的注册端口向插件发送第一通知。
一种外部设备与路由器之间连接情况的通知装置，可用于路由器或者路由器的插件管理中心，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，处理器被配置为：
监测是否发生预设行为，预设行为包括有外部设备连接到了路由器上、或者外部设备解除了与路由器的连接；
当发生预设行为时，在插件管理中心的端口中，确定路由器的插件的注册端口；
通过插件的注册端口，向插件发送第一通知，第一通知用于表明发生预设行为。
所述处理器还被配置为：
监测是否接收到第二通知，所述第二通知用于表明发生了所述预设行为。
所述处理器还被配置为：
当发生所述预设行为时，根据预存的所述插件管理中心的端口与所述路由器的插件之间的一一对应关系，在所述插件管理中心的端口中，确定所述插件的注册端口。
所述处理器还被配置为：
获取所述插件发送来的端口注册请求；
查询所述插件管理中心的端口中的空闲端口，将所述插件注册到所述空闲端口上，并建立所述插件的注册端口与所述插件之间的一一对应关系；
存储所述一一对应关系。
所述处理器还被配置为：
启动所述插件的轻量级网络服务器；
通过套接字SOCKET通信连接到所述轻量级网络服务器，由所述轻量级服务器通过所述插件的注册端口向所述插件发送所述第一通知。
本公开实施例提供的上述装置，当有外部设备连接到了路由器上、或者外部设备解除了与路由器的连接这些行为发生时，通过路由器的PluginCenter，将这些行为的发生情况通知给路由器的插件，使路由器的插件获知外部设备与路由器之间的连接情况，使路由器的插件能利用外部设备充分发挥插件的功能，提高插件的用户使用体验。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
一种非临时性计算机可读存储介质，当所述存储介质中的指令由客户端的处理器执行时，使得客户端能够执行一种外部设备与路由器之间连接情况的通知方法，所述方法包括：
监测是否发生预设行为，预设行为包括有外部设备连接到了路由器上、或者外部设备解除了与路由器的连接；
当发生预设行为时，在插件管理中心的端口中，确定路由器的插件的注册端口；
通过插件的注册端口，向插件发送第一通知，第一通知用于表明发生预设行为。
在一个实施例中，上述监测是否发生了预设行为，可包括：
监测是否接收到第二通知，第二通知用于表明发生了预设行为。
在一个实施例中，上述当发生预设行为时，在插件管理中心的端口中，确定路由器的插件的注册端口，可包括：
当发生预设行为时，根据预存的插件管理中心的端口与路由器的插件之间的一一对应关系，在插件管理中心的端口中，确定与插件的注册端口。
在一个实施例中，上述方法还可包括：
获取插件发送来的端口注册请求；
查询所述插件管理中心的端口中的空闲端口，将所述插件注册到所述空闲端口上，并建立所述插件的注册端口与所述插件之间的一一对应关系；
存储所述一一对应关系。
在一个实施例中，上述通过与插件的注册端口，向插件发送第一通知，第一通知用于表明发生预设行为，可包括：
启动插件的轻量级网络服务器；
通过套接字SOCKET通信连接到轻量级网络服务器，由轻量级服务器通过与插件的注册端口向插件发送第一通知。
本领域技术人员在考虑说明书及实践这里公开的公开后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (11)

  1. 一种外部设备与路由器之间连接情况的通知方法，用于所述路由器，其特征在于，所述方法包括：
    监测是否发生预设行为，所述预设行为包括有外部设备连接到了路由器上、或者所述外部设备解除了与所述路由器的连接；
    当发生所述预设行为时，在所述插件管理中心的端口中，确定所述路由器的插件的注册端口；
    通过所述插件的注册端口，向所述插件发送第一通知，所述第一通知用于表明发生所述预设行为。
  2. 如权利要求1所述的方法，其特征在于，所述监测是否发生了预设行为，包括：
    监测是否接收到外部接口发送的第二通知，所述第二通知用于表明发生了所述预设行为，所述路由器上设置有所述外部接口，所述外部接口用于连接所述外部设备。
  3. 如权利要求1所述的方法，其特征在于，所述当发生所述预设行为时，在所述插件管理中心的端口中，确定所述路由器的插件的注册端口，包括：
    当发生所述预设行为时，根据预存的所述插件管理中心的端口与所述路由器的插件之间的一一对应关系，在所述插件管理中心的端口中，确定所述插件的注册端口。
  4. 如权利要求3所述的方法，其特征在于，所述方法还包括：
    获取所述插件发送来的端口注册请求；
    查询所述插件管理中心的端口中的空闲端口，将所述插件注册到所述空闲端口上，并建立所述插件的注册端口与所述插件之间的一一对应关系；
    存储所述一一对应关系。
  5. 如权利要求1所述的方法，其特征在于，所述通过所述插件的注册端口，向所述插件发送第一通知，所述第一通知用于表明发生所述预设行为，包括：
    启动所述插件的轻量级网络服务器；
    通过套接字SOCKET通信连接到所述轻量级网络服务器，由所述轻量级服务器通过所述插件的注册端口向所述插件发送所述第一通知。
  6. 一种外部设备与路由器之间连接情况的通知装置，其特征在于，包括：
    监测模块，用于监测是否发生预设行为，所述预设行为包括有外部设备连接到了路由器上、或者所述外部设备解除了与所述路由器的连接；
    确定模块，用于当所述监测模块监测到发生所述预设行为时，在所述插件管理中心的端口中，确定所述路由器的插件的注册端口；
    通知模块，用于通过所述确定模块确定的所述插件的注册端口，向所述插件发送第一通知，所述第一通知用于表明发生所述预设行为。
  7. 如权利要求6所述的装置，其特征在于，所述监测模块包括：
    监测单元，用于监测是否接收到外部接口发送的第二通知，所述第二通知用于表明发生了所述预设行为，所述路由器上设置有所述外部接口，所述外部接口用于连接所述外部设备。
  8. 如权利要求6所述的装置，其特征在于，所述确定模块包括：
    确定单元，用于当所述监测模块监测到发生所述预设行为时，根据预存的所述插件管理中心的端口与所述路由器的插件之间的一一对应关系，在所述插件管理中心的端口中，确定所述插件的注册端口。
  9. 如权利要求8所述的装置，其特征在于，所述装置还包括：
    获取模块，用于获取所述插件发送来的端口注册请求；
    建立模块，用于查询所述插件管理中心的端口中的空闲端口，将所述插件注册到所述空闲端口上，并建立所述插件的注册端口与所述插件之间的一一对应关系；
    存储模块，用于存储所述一一对应关系。
  10. 如权利要求6所述的装置，其特征在于，所述通知模块包括：
    启动单元，用于启动所述插件的轻量级网络服务器；
    通知单元，用于通过SOCKET通信连接到所述轻量级网络服务器，由所述轻量级服务器通过所述插件的注册端口向所述插件发送所述第一通知。
  11. 一种外部设备与路由器之间连接情况的通知装置，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    监测是否发生预设行为，所述预设行为包括有外部设备连接到了路由器上、或者所述外部设备解除了与所述路由器的连接；
    当发生所述预设行为时，在所述插件管理中心的端口中，确定所述路由器的插件的注册端口；
    通过所述插件的注册端口，向所述插件发送第一通知，所述第一通知用于表明发生所述预设行为。
PCT/CN2015/072032 2014-08-08 2015-01-30 外部设备与路由器之间连接情况的通知方法及装置 Ceased WO2016019714A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
KR1020157014271A KR101776445B1 (ko) 2014-08-08 2015-01-30 외부 장치 및 라우터 사이의 연결 상태를 알리기 위한 방법 및 장치
JP2016539414A JP2016534653A (ja) 2014-08-08 2015-01-30 外部装置とルータとの接続状態を通知する方法及び装置
MX2015006163A MX360570B (es) 2014-08-08 2015-01-30 Método y aparato para informar una condición de conexión entre un dispositivo externo y un enrutador.
BR112015012468A BR112015012468A2 (pt) 2014-08-08 2015-01-30 método e aparelho para informar uma condição de conexão entre um dispositivo externo e um roteador
RU2015120927A RU2632395C2 (ru) 2014-08-08 2015-03-19 Способ и устройство для сообщения о состоянии соединения между внешним устройством и маршрутизатором
US14/715,887 US20160041854A1 (en) 2014-08-08 2015-05-19 Method and apparatus for informing connection condition between external device and router

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410389817.2 2014-08-08
CN201410389817.2A CN104168136B (zh) 2014-08-08 2014-08-08 外部设备与路由器之间连接情况的通知方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/715,887 Continuation US20160041854A1 (en) 2014-08-08 2015-05-19 Method and apparatus for informing connection condition between external device and router

Publications (1)

Publication Number Publication Date
WO2016019714A1 true WO2016019714A1 (zh) 2016-02-11

Family

ID=51911783

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/072032 Ceased WO2016019714A1 (zh) 2014-08-08 2015-01-30 外部设备与路由器之间连接情况的通知方法及装置

Country Status (9)

Country Link
US (1) US20160041854A1 (zh)
EP (1) EP2983085B1 (zh)
JP (1) JP2016534653A (zh)
KR (1) KR101776445B1 (zh)
CN (1) CN104168136B (zh)
BR (1) BR112015012468A2 (zh)
MX (1) MX360570B (zh)
RU (1) RU2632395C2 (zh)
WO (1) WO2016019714A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104168136B (zh) * 2014-08-08 2018-04-06 小米科技有限责任公司 外部设备与路由器之间连接情况的通知方法及装置
FR3100951B1 (fr) * 2019-09-12 2022-06-17 Remi Garot Dispositif de communication mobile

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102724356A (zh) * 2012-05-25 2012-10-10 中兴通讯股份有限公司 接入设备的信息同步方法及装置
CN103475592A (zh) * 2013-08-27 2013-12-25 上海斐讯数据通信技术有限公司 一种3g上网卡热插拔支持系统及方法
CN103873488A (zh) * 2014-04-08 2014-06-18 北京极科极客科技有限公司 基于路由器插件的上网控制方法
CN104038536A (zh) * 2014-05-23 2014-09-10 小米科技有限责任公司 插件通信方法和装置
CN104168136A (zh) * 2014-08-08 2014-11-26 小米科技有限责任公司 外部设备与路由器之间连接情况的通知方法及装置

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6574695B1 (en) * 2000-01-06 2003-06-03 Sun Microsystems, Inc. System and method for providing hot swap capability using existing circuits and drivers with minimal changes
US7082598B1 (en) * 2002-07-17 2006-07-25 Vmware, Inc. Dynamic driver substitution
JP4110977B2 (ja) * 2003-01-21 2008-07-02 松下電器産業株式会社 サーバ
DE112005000173B4 (de) * 2004-01-09 2010-07-22 Panasonic Corp., Kadoma IP-Vorrichtung und Management-Server
EP1555772A3 (en) * 2004-01-15 2013-07-17 Yamaha Corporation Remote control method of external devices
JP4480559B2 (ja) * 2004-12-01 2010-06-16 Ｎｅｃアクセステクニカ株式会社 ブロードバンドルータおよびそのポートマッピング情報更新方法
US20070233928A1 (en) * 2006-03-31 2007-10-04 Robert Gough Mechanism and apparatus for dynamically providing required resources for a hot-added PCI express endpoint or hierarchy
US7877368B2 (en) * 2007-11-02 2011-01-25 Paglo Labs, Inc. Hosted searching of private local area network information with support for add-on applications
CN102253840B (zh) * 2011-08-04 2013-11-13 深圳芯智汇科技有限公司 插件管理方法及插件管理器
US20130297281A1 (en) * 2011-10-11 2013-11-07 Invodo, Inc. Methods and systems of providing items to customers via a network
US8880994B1 (en) * 2013-04-19 2014-11-04 E-Z Brief Llc System and method for annotating and manipulating electronic documents
CN103279375B (zh) * 2013-06-19 2016-08-10 百度在线网络技术（北京）有限公司 在浏览器中运行应用程序的方法和装置
CN203446037U (zh) * 2013-09-27 2014-02-19 广东九联科技股份有限公司 一种带usb接口的无线路由器
US20150304187A1 (en) * 2014-04-17 2015-10-22 Invent.ly LLC Bandwidth Management in Local Premise Networks

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102724356A (zh) * 2012-05-25 2012-10-10 中兴通讯股份有限公司 接入设备的信息同步方法及装置
CN103475592A (zh) * 2013-08-27 2013-12-25 上海斐讯数据通信技术有限公司 一种3g上网卡热插拔支持系统及方法
CN103873488A (zh) * 2014-04-08 2014-06-18 北京极科极客科技有限公司 基于路由器插件的上网控制方法
CN104038536A (zh) * 2014-05-23 2014-09-10 小米科技有限责任公司 插件通信方法和装置
CN104168136A (zh) * 2014-08-08 2014-11-26 小米科技有限责任公司 外部设备与路由器之间连接情况的通知方法及装置

Also Published As

Publication number Publication date
EP2983085A1 (en) 2016-02-10
CN104168136A (zh) 2014-11-26
RU2632395C2 (ru) 2017-10-04
CN104168136B (zh) 2018-04-06
BR112015012468A2 (pt) 2017-07-11
EP2983085B1 (en) 2018-10-10
MX360570B (es) 2018-11-08
KR101776445B1 (ko) 2017-09-19
KR20160030872A (ko) 2016-03-21
JP2016534653A (ja) 2016-11-04
MX2015006163A (es) 2016-03-15
US20160041854A1 (en) 2016-02-11
RU2015120927A (ru) 2016-12-27

Similar Documents

Publication Publication Date Title
US9054299B2 (en) Registering a common information model provider to a common information model object manager
RU2009132388A (ru) Согласование загрузки между несколькими способными к загрузке устройствами
CN108769124A (zh) PaaS平台的应用部署方法、装置、服务器及存储介质
WO2014043876A1 (zh) 窃听行为侦测方法及终端设备
KR20130108613A (ko) 프로세스 간 통신을 위한 방법, 장치 및 컴퓨터 기록 매체
US20170280410A1 (en) Method, device and system for implementing information self-registration, and computer storage medium
WO2016197737A1 (zh) 自检处理方法、装置及系统
CN106716924A (zh) 蜂窝网络中wlan警报通知的方法及装置
CN105573777B (zh) 应用中服务的控制方法及装置
US10499311B2 (en) Method and apparatus for implementing network sharing
WO2013123815A1 (zh) 一种开机时间的获取方法及装置
WO2016019714A1 (zh) 外部设备与路由器之间连接情况的通知方法及装置
WO2014015743A1 (zh) 下载应用程序的方法、用户设备和应用服务器
CN104572105B (zh) 数据更新方法及装置
US8854962B2 (en) Methods for coupling information handling systems through a communications stack
US20140297719A1 (en) Receiving a communication event
CN106416133B (zh) 最优心跳周期的确定方法、装置和设备
CN104570967B (zh) 基于Android系统的远程控制方法及系统
CN105208574A (zh) 终端无线模块的性能检测方法及装置
CN102821302A (zh) 视频下载方法、网关设备及网络视频监控系统
CN104572418A (zh) 移动终端的诊断方法、装置和系统
CN102752365A (zh) 信息处理的方法与装置
US9860683B2 (en) Communication apparatus, method for controlling communication apparatus, and storage medium
US11233929B2 (en) Image capturing apparatus, system, control method for image capturing apparatus, and non-transitory computer-readable storage medium that controls processing to communicate with a client based on received setting value
JP2014123172A (ja) 計算機システム、及びシステム管理方法

Legal Events

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

Ref document number: MX/A/2015/006163

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 20157014271

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2015120927

Country of ref document: RU

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2016539414

Country of ref document: JP

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112015012468

Country of ref document: BR

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

Ref document number: 15829642

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112015012468

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20150528

122 Ep: pct application non-entry in european phase

Ref document number: 15829642

Country of ref document: EP

Kind code of ref document: A1