CN107426047A - Network flow monitoring method and its terminal based on the mono- kernel multisystems of Android - Google Patents
Network flow monitoring method and its terminal based on the mono- kernel multisystems of Android Download PDFInfo
- Publication number
- CN107426047A CN107426047A CN201710318539.5A CN201710318539A CN107426047A CN 107426047 A CN107426047 A CN 107426047A CN 201710318539 A CN201710318539 A CN 201710318539A CN 107426047 A CN107426047 A CN 107426047A
- Authority
- CN
- China
- Prior art keywords
- data structure
- network
- internet protocol
- namespace
- protocol data
- 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.)
- Pending
Links
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/16—Flow control; Congestion control in connection oriented networks, e.g. frame relay
-
- 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/0876—Network utilisation, e.g. volume of load or congestion level
-
- 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/20—Traffic policing
-
- 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/03—Protocol definition or specification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
Abstract
The present invention discloses a kind of network flow monitoring method based on the mono- kernel multisystems of Android, and it includes registered network agreement data structure;When creating or calling any network namespace, established a connection between the network namespace and the Internet protocol data structure, traffic monitoring data structure is created on the network namespace to monitor the data on flows of the network namespace;When nullifying the network namespace, the Internet protocol data structure is called to disconnect the annexation between the network namespace and the Internet protocol data structure.The present invention on any system can with and can only see the network interface of oneself system and every App traffic statistics, for the situation of single kernel multisystem scheme, the independent operation of traffic statistics between multisystem is realized, enhances the isolation and security of network flow statistic.
Description
Technical field
The present invention relates to the Network Traffic Flow Technology field of android system, more particularly to one kind to be based on the mono- kernels of Android
The network flow monitoring method and its terminal of multisystem.
Background technology
With Android development, the multisystem scheme based on container is proposed out on Android, wherein
Realize process isolation, file system isolation, Network Isolation etc..Android container schemes are provided based on linux kernel
Namespace is (i.e.:NameSpace) and Cgroups technologies, multiple Virtual Spaces are isolated on single kernel.Android
The data traffic service condition in the range of monitoring whole system is supported, flow prompting and flow are prompted by Notifications
Using limitation, quota is specified to turn off mobile data when flow exceedes.System can track each App flow service condition, use
Family can see each App historical traffic service condition at Setting app interfaces.Android passes through in linux kernel
Network interface records flow status.The network equipment being each active in driving by realizing Dev_get_stats
The equipment is returned on Rx_Bytes and Tx_Bytes statistics, and the numerical value is only disregarded comprising the information with the interaction of Ip layers
The flow informations such as Arp are calculated, also do not calculate header during encapsulation.Android collects stream using NetworkStateTracker
Statistical information is measured, NetworkStateTracker can identify each network interface and interface type and different identity.
In order to correctly count, all route datas are all taken into account by NetworkStateTracker.Mobile operator may be wished
The data flux statistics information for hoping a network equipment total does not include specific type, such as MMS. mobile radio interfaces to each
The APN of activation has independent Linux network interfaces, therefore Android can distinguish different APN data traffic.USB、BT
Network share mechanism, Wifi network hotspots forward rule that data forwarding is gone out using Iptables, and android system passes through note
The network information between any pair of interface is recorded to count these flow informations.Each App traffic statistics monitoring and tracking work(
Kernel Xt_qtaguid can be depended on (i.e.:Traffic monitoring data structure) module.The work(to be labelled to different Socket
Can in System/core/libcutils/qtaguid.c, the program rely on Xt_qtaguid modules derived from user interface/
Proc/Net/Xt_qtaguid/ctrl.Quota2Netfilter modules set name quota restrictions, when specified limit reaches
After notify client layer, each App uses independent UID, and Qtaguid Netfilter modules are every in Socket interface the HTM methods
Individual App Internet Use.In an App, it is possible to specify the label in addition to UID of network data is by the App's
Data are divided into several different subtypes, can thus distinguish downloading flow, the flow use state of Media Stream etc..
In Android single kernel multisystem scheme, Xt_qtaguid does not support the flow of multisystem to control, and herein, causes us
Single traffic statistics can not be made for each system so that the Xt_qtaguid in the mono- kernel multisystem schemes of Android is not
The problem of supporting the control of multisystem flow.
Therefore, need badly it is a kind of for every Net NameSpace (i.e.:Network namespace) support single traffic statistics letter
The mode of breath, to support each system individually to count the net based on the mono- kernel multisystems of Android of the function of oneself data on flows
Network flux monitoring method and its terminal.
The content of the invention
It is an object of the invention to provide a kind of network flow monitoring method based on the mono- kernel multisystems of Android and its
Terminal.
To achieve the above object, the invention provides a kind of network flow monitoring based on the mono- kernel multisystems of Android
Method, it includes:
Registered network agreement data structure;
When creating or calling any network namespace, in the network namespace and the Internet protocol data structure
Between establish a connection, it is empty to monitor the network naming that traffic monitoring data structure is created on the network namespace
Between data on flows;
When nullifying the network namespace, the Internet protocol data structure is called to disconnect the network namespace
Annexation between the Internet protocol data structure.
Compared with prior art, the present invention is when creating or calling any network namespace, in the network namespace
Established a connection between the Internet protocol data structure, traffic monitoring data knot is created on the network namespace
Structure, afterwards when nullifying the network namespace, disconnect the network namespace and the Internet protocol data structure it
Between annexation so that on any system can with and can only see the network interface of oneself system and every App stream
Measure statistical information, it is impossible to see the traffic statistics of other systems, for the situation of single kernel multisystem scheme, realize more
The independent operation of traffic statistics between system, enhance the isolation and security of network flow statistic.Wherein, described
Establishing a connection as man-to-man annexation between network namespace and the Internet protocol data structure.
It is preferred that described create traffic monitoring data structure to monitor the network naming on the network namespace
Also include after the data on flows in space:
Initialize the Internet protocol data structure, the network namespace and the traffic monitoring data structure.
It is preferred that described call the Internet protocol data structure to disconnect the network namespace and network association
Also include after annexation between view data structure:
Delete the corresponding traffic monitoring data structure of the network namespace.
It is preferred that the Internet protocol data structure is registered when starting the kernel.
It is preferred that when requiring to look up the traffic monitoring data of any network namespace, on the network namespace
Call and obtain the information of the traffic monitoring data structure.
It is preferred that the Internet protocol data structure includes into incoming interface and exits interface.
It is preferred that the establishment or when calling any network namespace, in the network namespace and the network
Establish a connection and specifically include between agreement data structure:
When creating or calling any network namespace, call the Internet protocol data structure it is described enter incoming interface connect
Mouthful to establish the annexation between the network namespace and the Internet protocol data structure.
It is preferred that during the cancellation network namespace, it is described to disconnect to call the Internet protocol data structure
Annexation between network namespace and the Internet protocol data structure specifically includes:
When nullifying the network namespace, the described of the Internet protocol data structure is called to exit interface to disconnect
State the annexation between network namespace and the Internet protocol data structure.
Accordingly, present invention also offers a kind of network flow monitoring terminal based on the mono- kernel multisystems of Android, its
Including:
Processor, it is adapted for carrying out instructions;And
Storage device, suitable for storing instructions, the instruction is suitable to be loaded and performed by processor:
Registered network agreement data structure;
When creating or calling any network namespace, in the network namespace and the Internet protocol data structure
Between establish a connection, it is empty to monitor the network naming that traffic monitoring data structure is created on the network namespace
Between data on flows;
When nullifying the network namespace, the Internet protocol data structure is called to disconnect the network namespace
Annexation between the Internet protocol data structure.
It is preferred that traffic monitoring data structure is created to monitor on the network namespace described in computing device
State the instruction of the data on flows of network namespace also includes afterwards:
Initialize the network namespace, the Internet protocol data structure and the traffic monitoring data structure.
It is preferred that the Internet protocol data structure is called described in computing device with disconnect the network namespace and
Also include after the instruction of annexation between the Internet protocol data structure:
Delete the corresponding traffic monitoring data structure of the network namespace.
It is preferred that the Internet protocol data structure is registered when starting the kernel.
It is preferred that when requiring to look up the traffic monitoring data of any network namespace, computing device is in the network
Called on NameSpace and obtain the instruction of the information of its traffic monitoring data structure.
It is preferred that the Internet protocol data structure includes into incoming interface and exits interface.
It is preferred that when being created described in computing device or calling any network namespace, in the network namespace
The instruction to be established a connection between the Internet protocol data structure specifically includes:
When creating or calling any network namespace, call the Internet protocol data structure it is described enter incoming interface with
The annexation established between the network namespace and the Internet protocol data structure.
It is preferred that when nullifying the network namespace described in computing device, the Internet protocol data structure is called
Specifically included with disconnecting the instruction of the annexation between the network namespace and the Internet protocol data structure:
When nullifying the network namespace, the described of the Internet protocol data structure is called to exit interface to disconnect
State the annexation between network namespace and the Internet protocol data structure.
It will be become more fully apparent by following description and with reference to accompanying drawing, the present invention, these accompanying drawings are used to explain the present invention
Embodiment.
Brief description of the drawings
Fig. 1 is the flow chart of the network flow monitoring method based on the mono- kernel multisystems of Android of the present invention.
Fig. 2 is the step S1021 of present invention particular flow sheet.
Fig. 3 is the step S1041 of present invention particular flow sheet.
Fig. 4 is the structured flowchart of the network flow monitoring terminal based on the mono- kernel multisystems of Android of the present invention.
Embodiment
Embodiments of the invention are described with reference now to accompanying drawing, similar element numbers represent similar element in accompanying drawing.
Fig. 1 is refer to, the network flow monitoring method of the invention based on the mono- kernel multisystems of Android includes:
S101, registered network agreement data structure is (i.e.:Pernet_Operations).Specifically, when starting the kernel
The Internet protocol data structure is registered, the Internet protocol data structure includes into incoming interface and exits interface.Need to illustrate
, the present embodiment is that the Internet protocol data structure is just registered when starting the kernel, can be with during practical operation
According to the actual requirements, the net is registered according to safe traffic monitor command caused by the specific instruction of input or other operations
Network agreement data structure, therefore herein not to be limited.
S102, create or call any network namespace (i.e.:Net Namespace) when, it is empty in the network naming
Between established a connection between the Internet protocol data structure, on the network namespace create traffic monitoring data
Structure is (i.e.:Xt_Qtaguid) to monitor the data on flows of the network namespace.Wherein, in the mono- kernel polyphylys of Android
In system, the primary Xt_Qtaguid for only having Root Namespace uniformly to see whole system flow information, and system
Acquiescence general/Proc/Net/Xt_Qtaguid/ is mounted on Root Namespace, so there was only Root Net Namespace
It can be seen that Xt_Qtaguid flow information.Specifically, in order that each system it can be seen that the flow information of itself,
Pernet_Operations is registered during kernel starts, kernel and Net are established by the Pernet_Operations
Namespace annexation.After annexation of the kernel with Net Namespace is established, appoint in each establishment or calling
During one Net Namespace, Xt_Qtaguid is created on the Net Namespace, by the Xt_Qtaguid to monitor
The data on flows of the Net Namespace.
S103, initialize the Internet protocol data structure, the network namespace and the traffic monitoring data knot
Structure.The Internet protocol data structure, the network namespace and the traffic monitoring number are initialized by initialization command
According to structure, the Internet protocol data structure, the network namespace and the traffic monitoring data are may further ensure that
Independence, integrality and the real-time of the data of structure.
S104, when nullifying the network namespace, call the Internet protocol data structure and ordered with disconnecting the network
Annexation between the name space and the Internet protocol data structure.Specifically, disconnected by the Pernet_Operations
The annexation of kernel and Net Namespace.Disconnect kernel and after Net Namespace annexation, kernel can not be adjusted
With the Xt_Qtaguid to check the data on flows of the NetNamespace.
S105, delete the corresponding traffic monitoring data structure of the network namespace.Specifically, one is nullified
, it is necessary to the Xt_Qtaguid related data structures in the Net Namespace be deleted, further to protect during Net Namespace
Protect the security of network flow statistic.
As shown in Fig. 2 step S102 is specifically included:S1021, when creating or calling any network namespace, call institute
State the Internet protocol data structure it is described enter incoming interface to establish the network namespace and the Internet protocol data structure
Between annexation.
Preferably, when require to look up it is any need obtain traffic monitoring data corresponding network namespace when, in institute
State the information that its traffic monitoring data structure is called and obtained on network namespace.Specifically ,/Proc/Net/ is checked
During Xt_Qtaguid, first finding needs the Net Namespace for checking Xt_Qtaguid, then in the Net Namespace
Xt_Qtaguid corresponding to lookup.
As shown in figure 3, step S104 is specifically included:S1041, when nullifying the network namespace, call the network
The described of agreement data structure exits interface to disconnect between the network namespace and the Internet protocol data structure
Annexation.
It should be noted that Pernet_Operations, network naming corresponding to the Internet protocol data structure of the present invention
Net Namespace corresponding to space, Xt_Qtaguid corresponding to traffic monitoring data structure are those skilled in the art's table
The conventional replacement of the Chinese, English of common technology noun is stated, it is of the invention in order to keep the continuity of description language and program language,
Such common technology noun can be used alternatingly in the description.
Fig. 4 is refer to, correspondingly, present invention also offers a kind of network traffics based on the mono- kernel multisystems of Android
Monitor terminal 100, including processor 1 and storage device 2, the processor 1 are adapted for carrying out instructions;The storage device 2
Suitable for storing instructions.The instruction is suitable to be loaded and performed by processor 1, and the instruction includes:Registered network agreement number
According to structure;When creating or calling any network namespace, in the network namespace and the Internet protocol data structure
Between establish a connection, it is empty to monitor the network naming that traffic monitoring data structure is created on the network namespace
Between data on flows;When nullifying the network namespace, call the Internet protocol data structure and ordered with disconnecting the network
Annexation between the name space and the Internet protocol data structure.
Preferably, processor 1 perform the establishment traffic monitoring data structure on the network namespace to monitor
Also include after the instruction of the data on flows of the network namespace:Initialize the Internet protocol data structure, the net
Network NameSpace and the traffic monitoring data structure.
Preferably, processor 1 perform the calling the Internet protocol data structure to disconnect the network namespace
Also include after the instruction of annexation between the Internet protocol data structure:Delete pair of the network namespace
The traffic monitoring data structure answered.
Preferably, the Internet protocol data structure is registered when starting the kernel.
, it is necessary to when searching the traffic monitoring data of any network namespace, processor 1 performs in the network preferably
Called on NameSpace and obtain the instruction of the information of the traffic monitoring data structure.
Preferably, the Internet protocol data structure include into incoming interface and exit interface.
Preferably, when processor 1 performs the establishment or calls any network namespace, in the network namespace
The instruction to be established a connection between the Internet protocol data structure specifically includes:
When creating or calling any network namespace, call the Internet protocol data structure it is described enter incoming interface with
The annexation established between the network namespace and the Internet protocol data structure.
Preferably, when processor 1 performs the cancellation network namespace, call the Internet protocol data structure
Specifically included with disconnecting the instruction of the annexation between the network namespace and the Internet protocol data structure:
When nullifying the network namespace, the described of the Internet protocol data structure is called to exit interface to disconnect
State the annexation between network namespace and the Internet protocol data structure.
The above disclosed right for being only the preferred embodiments of the present invention, the present invention can not being limited with this certainly
Scope, therefore the equivalent variations made according to scope of the present invention patent, still belong to the scope that the present invention is covered.
Claims (16)
- A kind of 1. network flow monitoring method based on the mono- kernel multisystems of Android, it is characterised in that including:Registered network agreement data structure;When creating or calling any network namespace, between the network namespace and the Internet protocol data structure Establish a connection, traffic monitoring data structure is created on the network namespace to monitor the network namespace Data on flows;When nullifying the network namespace, the Internet protocol data structure is called to disconnect the network namespace and institute State the annexation between the Internet protocol data structure.
- 2. the network flow monitoring method as claimed in claim 1 based on the mono- kernel multisystems of Android, it is characterised in that It is described that traffic monitoring data structure is created on the network namespace to monitor the data on flows of the network namespace Also include afterwards:Initialize the Internet protocol data structure, the network namespace and the traffic monitoring data structure.
- 3. the network flow monitoring method as claimed in claim 1 based on the mono- kernel multisystems of Android, it is characterised in that It is described to call the Internet protocol data structure to disconnect between the network namespace and the Internet protocol data structure Annexation after also include:Delete the corresponding traffic monitoring data structure of the network namespace.
- 4. the network flow monitoring method as claimed in claim 1 based on the mono- kernel multisystems of Android, it is characterised in that The Internet protocol data structure is registered when starting the kernel.
- 5. the network flow monitoring method as claimed in claim 1 based on the mono- kernel multisystems of Android, it is characterised in that When requiring to look up the traffic monitoring data of any network namespace, called on the network namespace and obtain the stream Measure the information of monitoring data structure.
- 6. the network flow monitoring method as claimed in claim 1 based on the mono- kernel multisystems of Android, it is characterised in that The Internet protocol data structure includes into incoming interface and exits interface.
- 7. the network flow monitoring method as claimed in claim 6 based on the mono- kernel multisystems of Android, it is characterised in that The establishment or when calling any network namespace, between the network namespace and the Internet protocol data structure Establish a connection and specifically include:When creating or calling any network namespace, call the Internet protocol data structure it is described enter incoming interface to establish Annexation between the network namespace and the Internet protocol data structure.
- 8. the network flow monitoring method as claimed in claim 6 based on the mono- kernel multisystems of Android, it is characterised in that During the cancellation network namespace, the Internet protocol data structure is called to disconnect the network namespace and institute The annexation stated between the Internet protocol data structure specifically includes:When nullifying the network namespace, the described of the Internet protocol data structure is called to exit interface to disconnect the net Annexation between network NameSpace and the Internet protocol data structure.
- A kind of 9. network flow monitoring terminal based on the mono- kernel multisystems of Android, it is characterised in that including:Processor, it is adapted for carrying out instructions;AndStorage device, suitable for storing instructions, the instruction is suitable to be loaded and performed by processor:Registered network agreement data structure;When creating or calling any network namespace, between the network namespace and the Internet protocol data structure Establish a connection, traffic monitoring data structure is created on the network namespace to monitor the network namespace Data on flows;When nullifying the network namespace, the Internet protocol data structure is called to disconnect the network namespace and institute State the annexation between the Internet protocol data structure.
- 10. the network flow monitoring terminal as claimed in claim 9 based on the mono- kernel multisystems of Android, it is characterised in that Traffic monitoring data structure is created to monitor the network naming on the network namespace described in the computing device Also include after the instruction of the data on flows in space:Initialize the network namespace, the Internet protocol data structure and the traffic monitoring data structure.
- 11. the network flow monitoring terminal as claimed in claim 9 based on the mono- kernel multisystems of Android, it is characterised in that The Internet protocol data structure is called to be assisted to disconnect the network namespace and the network described in the computing device Also include after the instruction of annexation between view data structure:Delete the corresponding traffic monitoring data structure of the network namespace.
- 12. the network flow monitoring terminal as claimed in claim 9 based on the mono- kernel multisystems of Android, it is characterised in that The Internet protocol data structure is registered when starting the kernel.
- 13. the network flow monitoring terminal as claimed in claim 9 based on the mono- kernel multisystems of Android, it is characterised in that When requiring to look up the traffic monitoring data of any network namespace, called on the network namespace and obtain the stream Measure the information of monitoring data structure.
- 14. the network flow monitoring terminal as claimed in claim 9 based on the mono- kernel multisystems of Android, it is characterised in that The Internet protocol data structure includes into incoming interface and exits interface.
- 15. the network flow monitoring terminal as claimed in claim 14 based on the mono- kernel multisystems of Android, its feature exist In when performing the establishment or calling any network namespace, in the network namespace and the Internet protocol data The instruction to be established a connection between structure specifically includes:When creating or calling any network namespace, call the Internet protocol data structure it is described enter incoming interface to establish Annexation between the network namespace and the Internet protocol data structure.
- 16. the network flow monitoring terminal as claimed in claim 14 based on the mono- kernel multisystems of Android, its feature exist In, perform it is described cancellation the network namespace when, call the Internet protocol data structure to disconnect the network naming The instruction of annexation between space and the Internet protocol data structure specifically includes:When nullifying the network namespace, the described of the Internet protocol data structure is called to exit interface to disconnect the net Annexation between network NameSpace and the Internet protocol data structure.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710318539.5A CN107426047A (en) | 2017-05-08 | 2017-05-08 | Network flow monitoring method and its terminal based on the mono- kernel multisystems of Android |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710318539.5A CN107426047A (en) | 2017-05-08 | 2017-05-08 | Network flow monitoring method and its terminal based on the mono- kernel multisystems of Android |
Publications (1)
Publication Number | Publication Date |
---|---|
CN107426047A true CN107426047A (en) | 2017-12-01 |
Family
ID=60424504
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201710318539.5A Pending CN107426047A (en) | 2017-05-08 | 2017-05-08 | Network flow monitoring method and its terminal based on the mono- kernel multisystems of Android |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN107426047A (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108390810A (en) * | 2018-01-05 | 2018-08-10 | 郑州信大捷安信息技术股份有限公司 | One kind is based on the more android system network virtualization methods of single linux kernel |
CN111355818A (en) * | 2018-12-24 | 2020-06-30 | 中国电信股份有限公司 | Address resolution scheduling method and device and address resolution system |
CN113660248A (en) * | 2021-08-11 | 2021-11-16 | 杭州安恒信息技术股份有限公司 | Service flow isolation method, system, readable storage medium and device |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7463726B2 (en) * | 2003-02-03 | 2008-12-09 | Sparktech Corporation | Remotely selecting an economical communications transmission medium |
US20120102314A1 (en) * | 2010-04-01 | 2012-04-26 | Huizhou TCL Mobile Communications Co., Ltd. | Smart phone system and booting method thereof |
US8423634B2 (en) * | 2004-05-24 | 2013-04-16 | Neustar, Inc. | System and method for determining cost of website performance |
CN104717368A (en) * | 2015-04-08 | 2015-06-17 | 宇龙计算机通信科技(深圳)有限公司 | Flow-data updating method, flow-data updating system and terminal |
CN104780079A (en) * | 2015-04-08 | 2015-07-15 | 宇龙计算机通信科技(深圳)有限公司 | Flow monitoring method and device for multiple system terminals |
CN105786480A (en) * | 2015-12-29 | 2016-07-20 | 上海闻泰电子科技有限公司 | Application processing system and processing method |
-
2017
- 2017-05-08 CN CN201710318539.5A patent/CN107426047A/en active Pending
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7463726B2 (en) * | 2003-02-03 | 2008-12-09 | Sparktech Corporation | Remotely selecting an economical communications transmission medium |
US8423634B2 (en) * | 2004-05-24 | 2013-04-16 | Neustar, Inc. | System and method for determining cost of website performance |
US20120102314A1 (en) * | 2010-04-01 | 2012-04-26 | Huizhou TCL Mobile Communications Co., Ltd. | Smart phone system and booting method thereof |
CN104717368A (en) * | 2015-04-08 | 2015-06-17 | 宇龙计算机通信科技(深圳)有限公司 | Flow-data updating method, flow-data updating system and terminal |
CN104780079A (en) * | 2015-04-08 | 2015-07-15 | 宇龙计算机通信科技(深圳)有限公司 | Flow monitoring method and device for multiple system terminals |
CN105786480A (en) * | 2015-12-29 | 2016-07-20 | 上海闻泰电子科技有限公司 | Application processing system and processing method |
Non-Patent Citations (1)
Title |
---|
希尔瓦娜丝女神: "Android网络流量监听开源项目-ConnectionClass源码分析", 《博客园,WWW.CNBLOGS.COM/PUNKISNTDEAD/P/4780351.HTML》 * |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108390810A (en) * | 2018-01-05 | 2018-08-10 | 郑州信大捷安信息技术股份有限公司 | One kind is based on the more android system network virtualization methods of single linux kernel |
CN108390810B (en) * | 2018-01-05 | 2021-07-30 | 郑州信大捷安信息技术股份有限公司 | Single Linux kernel based multi-Android system network virtualization method |
CN111355818A (en) * | 2018-12-24 | 2020-06-30 | 中国电信股份有限公司 | Address resolution scheduling method and device and address resolution system |
CN113660248A (en) * | 2021-08-11 | 2021-11-16 | 杭州安恒信息技术股份有限公司 | Service flow isolation method, system, readable storage medium and device |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6786558B2 (en) | Application state change notification program and its method | |
US10505762B2 (en) | Network function virtualization requirements to service a long term evolution (LTE) network | |
CN109257827A (en) | Communication means, device, system, terminal and access network equipment | |
EP2448304B1 (en) | Multiple access method and multiple access system of terminals in evolved packet system (eps) | |
US9247059B1 (en) | Priority token-based interactive voice response server | |
WO2019075848A1 (en) | Coordination of terminal slicing function and network slicing function | |
WO2019074407A1 (en) | Methods for establishing connection for packet data transfer of a wireless communication device | |
US11765791B2 (en) | Systems and methods for providing low latency services via an evolved packet core network | |
US20170250952A1 (en) | Method and Apparatuses for Enabling Routing of Data Packets Between a Wireless Device and a Service Provider Based in the Local Service Cloud | |
US9706351B1 (en) | Emergency call over a data network | |
US10299183B2 (en) | Communication apparatus, communication method, communication system, and program | |
CN107426047A (en) | Network flow monitoring method and its terminal based on the mono- kernel multisystems of Android | |
CN110072297A (en) | A kind of network architecture, information interacting method and device | |
EP3131276B1 (en) | Incoming call forwarding method and user equipment | |
JP7026085B2 (en) | Network connection system and its method | |
US9497606B1 (en) | Native dialer fall-back | |
US20230156828A1 (en) | Session establishment method and apparatus, system, and computer storage medium | |
EP2050289B1 (en) | Call identification mechanism for multi-protocol telephones | |
US20180013888A1 (en) | Call Collision Processing Method for Terminal Device, and Terminal Device | |
US10404858B1 (en) | Short message service (SMS) with geographic data for user equipment (UE) | |
EP3641248B1 (en) | Traffic optimization device, communication system, traffic optimization method, and program | |
CN108471633B (en) | Communication method and communication system | |
JP2022016935A (en) | Device, method and program for data processing | |
KR20220166275A (en) | Session processing method, device and storage medium | |
US10003657B2 (en) | Data transmission processing method and apparatus |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
AD01 | Patent right deemed abandoned | ||
AD01 | Patent right deemed abandoned |
Effective date of abandoning: 20210511 |