CN114666098A - Mobile terminal non-intrusive event monitoring universal uplink mechanism - Google Patents
Mobile terminal non-intrusive event monitoring universal uplink mechanism Download PDFInfo
- Publication number
- CN114666098A CN114666098A CN202210185559.0A CN202210185559A CN114666098A CN 114666098 A CN114666098 A CN 114666098A CN 202210185559 A CN202210185559 A CN 202210185559A CN 114666098 A CN114666098 A CN 114666098A
- Authority
- CN
- China
- Prior art keywords
- api
- node
- sdk
- data
- uplink
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
-
- 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
Abstract
The invention relates to the technical field of internet, and particularly discloses a mobile terminal non-intrusive event monitoring universal uplink mechanism, which comprises the following steps: step S001: adding an event monitoring mechanism beside the original system, and calling an SDK in the event monitoring mechanism to monitor the original system Api; step S002: the original system can inquire the block chain content through the SDK; step S003: the invention calls the uplink preposition service of the block chain through the SDK, and aims to solve the problem that the original system is more invasive due to the addition of a new block chain when the coupling of the original system is higher.
Description
Technical Field
The application relates to the technical field of internet, and particularly discloses a mobile terminal non-intrusive event monitoring universal uplink mechanism.
Background
With the development of mobile internet, a great number of applications (applications) emerge, and a good operation strategy is the most important aspect of mobile Application marketing promotion. Data operations have long played an important role as the basis for mobile Application marketing operations. The collection, storage and application of user behavior data are basic support of data operation, and the accuracy, completeness and timeliness of the user behavior data collection directly determine the quality of data operation.
Currently, event monitoring is basically implemented through an access block chain, and there are mainly 2 ways: 1. self-research or introduction of a bottom platform facility of a block chain manufacturer, and chaining data through privatized deployment; 2. adopt the SDK of block chain producer, carry out the cochain with corresponding data, above-mentioned two kinds of modes all have some problems: 1. the block chain development cost is high, and the access cost is high; 2. reintroducing blockchains into a developed system is time and labor consuming; 3. when the system coupling is high, the content is added to make the original system more invasive. In view of the above, the present invention provides a mechanism for mobile-side non-intrusive event monitoring for a universal uplink.
Disclosure of Invention
The invention aims to solve the problem that when the coupling of the original system is higher, the addition of a new block chain can cause larger invasion to the original system.
In order to achieve the above object, the present invention provides the following basic solutions:
a mobile-side non-intrusive event monitoring universal uplink mechanism includes the following steps:
step S001: adding an event monitoring mechanism beside the original system, and calling an SDK in the event monitoring mechanism to monitor the original system Api;
step S002: the original system can inquire the block chain content through the SDK;
step S003: the blockchain uplink preamble service is invoked by the SDK.
The principle and effect of this basic scheme lie in:
1. compared with the prior art, the block chain development cost is higher, and the access cost can be reduced by the block chain development method.
2. Compared with the prior art, when the system is used in a developed system, the original system does not need to be modified, the system is not invasive, and the modification and adjustment required when the system is accessed are reduced.
3. Compared with the prior art, the plug-and-play system enables developers to use the plug-and-play system in a plug-in mode, and the plug-and-play system can be conveniently and quickly used on the project.
Further, in step S001, after the original system is accessed to the SDK and turned on, the related data is monitored and acquired through the optimization processing of the Api turned on for the recording, video recording and screen recording events provided by the systems of different mobile devices.
Further, in step 003, the uplink data in the uplink preamble service of the blockchain is queried through the mobile terminal device or the data large screen, and the audio/video data after uplink is played.
Further, the step of monitoring the original system Api by the SDK is as follows:
step S004: checking whether an initial Api is configured, if not, skipping, and if so, accessing the initial Api;
step S005: checking whether historical scanning information exists or not, if not, skipping, and if so, acquiring historical scanning node information;
step S006: acquiring a scanning protocol of a current block chain, taking out a scanning port and a scanning result defined in the scanning protocol, and sequentially sending detection data to an Api port to be scanned, wherein if no response exists, the Api is invalid; if so, determining whether the response conforms to the block chain protocol, if so, determining the response to be a valid Api node, and if not, determining the response to be an invalid node;
step S007: after the effective Api node is obtained, the connection between the SDK and the Api is realized, and the monitoring of the SDK and the Api is completed.
Further, the uplink data is encrypted and then broadcast to each node in the block chain, such as node a, node B, node C and node D, so that after the block chain passes the data consensus, the information after the data encryption is persisted, and the persisted uplink data is displayed through mobile terminal equipment or a data large screen.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments will be briefly introduced below. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.
Fig. 1 is a flowchart illustrating a mechanism for mobile-side non-intrusive event monitoring for a universal uplink.
Detailed Description
The embodiment example is shown in figure 1:
a mobile node-side mechanism for monitoring a universal uplink for non-intrusive event monitoring comprises the following steps:
step S001: adding an event monitoring mechanism beside the original system, and calling an SDK in the event monitoring mechanism to monitor the original system Api;
step S002: the original system can inquire the block chain content through the SDK;
step S003: the blockchain uplink preamble service is invoked by the SDK.
In step S001, after the original system is accessed to the SDK and turned on, the Api turned on for the recording, video recording and screen recording events provided by the systems of different mobile devices is optimized to monitor and obtain related data;
specifically, the method comprises the following steps:
the SDK monitors the original system Api in the following steps:
step S004: checking whether an initial Api is configured, if not, skipping, and if so, accessing the initial Api;
step S005: checking whether historical scanning information exists or not, if not, skipping, and if so, acquiring historical scanning node information;
step S006: acquiring a scanning protocol of a current block chain, taking out a scanning port and a scanning result defined in the scanning protocol, and sequentially sending detection data to an Api port to be scanned, wherein if no response exists, the Api is invalid; if so, determining whether the response conforms to the block chain protocol, if so, determining the response to be a valid Api node, and if not, determining the response to be an invalid node;
step S007: after the effective Api node is obtained, the connection between the SDK and the Api is realized, and the monitoring of the SDK and the Api is finished;
in step 003, uplink data in the block chain uplink pre-service is queried through the mobile terminal device or the data large screen, and audio and video data after uplink is played;
and encrypting the uplink data and broadcasting the encrypted uplink data to each node in the block chain, such as a node A, a node B, a node C and a node D, so that the block chain can pass the data consensus, the information after the data encryption is persisted, and the persisted uplink data is displayed through mobile terminal equipment or a data large screen.
The design does not need to change the original service system: the original mobile terminal App service system does not need to change any service, and if the recording, video recording and screen recording related functions exist, the SDK can be used for real-time chain connection of the recording, video recording and screen recording data through the chain connection system.
Event monitoring is carried out on the original service system:
after an original system is accessed to an SDK and started, the related data is monitored and obtained through optimization processing of an Api for starting recording, video recording and screen recording events provided by systems of different mobile devices, taking an iOS system video recording function of an apple device as an example, a system captureOutput method called by system video is monitored by using a KVO mechanism of the iOS system, the most original data of the obtained video is encoded and then is pushed to a service end for uplink in real time, the uplink can be successfully carried out after the video is finished, and the customized processing (including no processing) of the original system service can be carried out in a callback method provided by the SDK after the uplink is successfully carried out.
And (3) data uploading:
the mobile terminal equipment acquires original audio and video data in real time through a camera and a microphone of the equipment, namely monitors the data, acquires original yuv data and original pcm data of audio of the equipment in real time, respectively carries out real-time hard coding of aac and h264 on the audio and video through hard coding provided by an equipment system, and uploads the data to a server in real time through rtmp protocol, and the server synthesizes the coded audio and video into flv format video or wav format audio and carries out corresponding audio and video format processing, namely the successful real-time uplink is realized.
Data usage:
the mobile terminal equipment or the data large screen inquires the uplink data through the uplink prepositive service of the block chain, and plays the audio and video data after uplink and the like.
To sum up:
1. compared with the prior art, the block chain development cost is higher, and the access cost can be reduced by the block chain development method.
2. Compared with the prior art, when the system is used in a developed system, the original system does not need to be modified, the system is not invasive, and the modification and adjustment required when the system is accessed are reduced.
3. Compared with the prior art, the plug-in system enables developers to plug and play, is similar to a plug-in form, and can be conveniently and quickly used on own projects.
The mechanism solves the problem that when the coupling of the original system is high, the original system is more invasive due to the addition of a new block chain.
While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts. In accordance with one or more embodiments, some acts may occur in different orders and/or concurrently with other acts from that shown and described herein or not shown and described herein but understood by those of ordinary skill in the art. To further enable those of skill in the art, the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention. The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software as a computer program product, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk (disk) and disc (disc), as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks (disks) usually reproduce data magnetically, while discs (discs) reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
Claims (5)
1. A mobile-side mechanism for non-intrusive event listening to a universal uplink, comprising: the method comprises the following steps:
step S001: adding an event monitoring mechanism beside the original system, and calling an SDK in the event monitoring mechanism to monitor the original system Api;
step S002: the original system can inquire the block chain content through the SDK;
step S003: the blockchain uplink preamble service is invoked by the SDK.
2. The mechanism of claim 1, wherein in step S001, after an original system accesses and turns on the SDK, the Api for turning on the recording, video recording and screen recording events provided by different mobile devices is optimized to monitor and obtain related data.
3. The mechanism as claimed in claim 1, wherein in step 003, the uplink data in the uplink block chain pre-service is queried and played back after uplink through the mobile device or the data large screen.
4. The mechanism of claim 2 wherein the step of the SDK monitoring the legacy system Api comprises:
step S004: checking whether an initial Api is configured, if not, skipping, and if so, accessing the initial Api;
step S005: checking whether historical scanning information exists or not, if not, skipping, and if so, acquiring historical scanning node information;
step S006: acquiring a scanning protocol of a current block chain, taking out a scanning port and a scanning result defined in the scanning protocol, and sequentially sending detection data to an Api port to be scanned, wherein if no response exists, the Api is invalid; if so, determining whether the response conforms to the block chain protocol, if so, determining the response to be a valid Api node, and if not, determining the response to be an invalid node;
step S007: after the effective Api node is obtained, the connection between the SDK and the Api is realized, and the monitoring of the SDK and the Api is finished.
5. The mechanism as claimed in claim 3, wherein the encrypted uplink data is broadcasted to each node in the blockchain, such as node a, node B, node C and node D, so that the blockchain can pass the common identification of the data, and then the encrypted data information is persisted, and the persisted uplink data is displayed through the mobile device or the data large screen.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210185559.0A CN114666098A (en) | 2022-02-28 | 2022-02-28 | Mobile terminal non-intrusive event monitoring universal uplink mechanism |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210185559.0A CN114666098A (en) | 2022-02-28 | 2022-02-28 | Mobile terminal non-intrusive event monitoring universal uplink mechanism |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114666098A true CN114666098A (en) | 2022-06-24 |
Family
ID=82027741
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210185559.0A Pending CN114666098A (en) | 2022-02-28 | 2022-02-28 | Mobile terminal non-intrusive event monitoring universal uplink mechanism |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114666098A (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN204542095U (en) * | 2015-03-30 | 2015-08-12 | 深圳市天蓝海科技有限公司 | Blood pressure non-invasive monitoring intelligent watch and system |
| CN108769757A (en) * | 2018-05-25 | 2018-11-06 | 数字乾元科技有限公司 | video statistics and transaction system and method |
| WO2020098844A2 (en) * | 2019-11-08 | 2020-05-22 | Alipay (Hangzhou) Information Technology Co., Ltd. | System and method for implementing a blockchain-based decentralized application |
| CN111444512A (en) * | 2019-01-17 | 2020-07-24 | 杨税令 | Mobile terminal blocking method and system for block chain |
| CN111488344A (en) * | 2020-04-08 | 2020-08-04 | 北京瑞策科技有限公司 | User operation data uplink method and system based on service data block chain |
| CN111756736A (en) * | 2020-06-24 | 2020-10-09 | 深圳市网心科技有限公司 | Cross-link method and system between heterogeneous block chains, electronic equipment and storage medium |
| CN112000563A (en) * | 2020-08-26 | 2020-11-27 | 支付宝(杭州)信息技术有限公司 | User behavior recording method, device and equipment |
| WO2020253688A1 (en) * | 2019-06-20 | 2020-12-24 | 深圳前海微众银行股份有限公司 | Blockchain-based cross-chain communication method, device, and transaction system |
| CN112800130A (en) * | 2020-12-30 | 2021-05-14 | 杭州趣链科技有限公司 | Data uplink method, system, device, equipment and storage medium |
| WO2021136251A1 (en) * | 2019-12-30 | 2021-07-08 | 北京金山云网络技术有限公司 | Cross-blockchain communication method and apparatus, cross-chain service system and cross-chain transaction system |
| CN113315832A (en) * | 2021-05-26 | 2021-08-27 | 杭州云象网络技术有限公司 | Cross-chain information synchronization method, system and device based on cloud cross-chain transfer protocol |
| US20210389932A1 (en) * | 2020-06-10 | 2021-12-16 | Snap Inc. | Software development kit engagement monitor |
-
2022
- 2022-02-28 CN CN202210185559.0A patent/CN114666098A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN204542095U (en) * | 2015-03-30 | 2015-08-12 | 深圳市天蓝海科技有限公司 | Blood pressure non-invasive monitoring intelligent watch and system |
| CN108769757A (en) * | 2018-05-25 | 2018-11-06 | 数字乾元科技有限公司 | video statistics and transaction system and method |
| CN111444512A (en) * | 2019-01-17 | 2020-07-24 | 杨税令 | Mobile terminal blocking method and system for block chain |
| WO2020253688A1 (en) * | 2019-06-20 | 2020-12-24 | 深圳前海微众银行股份有限公司 | Blockchain-based cross-chain communication method, device, and transaction system |
| WO2020098844A2 (en) * | 2019-11-08 | 2020-05-22 | Alipay (Hangzhou) Information Technology Co., Ltd. | System and method for implementing a blockchain-based decentralized application |
| WO2021136251A1 (en) * | 2019-12-30 | 2021-07-08 | 北京金山云网络技术有限公司 | Cross-blockchain communication method and apparatus, cross-chain service system and cross-chain transaction system |
| CN111488344A (en) * | 2020-04-08 | 2020-08-04 | 北京瑞策科技有限公司 | User operation data uplink method and system based on service data block chain |
| US20210389932A1 (en) * | 2020-06-10 | 2021-12-16 | Snap Inc. | Software development kit engagement monitor |
| CN111756736A (en) * | 2020-06-24 | 2020-10-09 | 深圳市网心科技有限公司 | Cross-link method and system between heterogeneous block chains, electronic equipment and storage medium |
| CN112000563A (en) * | 2020-08-26 | 2020-11-27 | 支付宝(杭州)信息技术有限公司 | User behavior recording method, device and equipment |
| CN112800130A (en) * | 2020-12-30 | 2021-05-14 | 杭州趣链科技有限公司 | Data uplink method, system, device, equipment and storage medium |
| CN113315832A (en) * | 2021-05-26 | 2021-08-27 | 杭州云象网络技术有限公司 | Cross-chain information synchronization method, system and device based on cloud cross-chain transfer protocol |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10484806B2 (en) | Managing audio output through an intermediary | |
| US9154185B2 (en) | Managing audio output through an intermediary | |
| US7752202B2 (en) | Information processing and, content distribution apparatus method, and program with conversion identification information | |
| US20080059567A1 (en) | System and method for configuring a client electronic device | |
| KR20080064176A (en) | Methods and apparatus for metering portable media players | |
| CN104253999A (en) | Method and apparatus for transmitting content, method and apparatus for receiving content, method and apparatus for encoding content, method and apparatus for decoding content | |
| CN108108595A (en) | The method and system authorized to the software in electronic equipment | |
| US20050008326A1 (en) | Video recording apparatus and method of programming the video recording apparatus to perform timer recording | |
| WO2008071083A1 (en) | A method and apparatus for processing flow media service anomaly | |
| CN114666098A (en) | Mobile terminal non-intrusive event monitoring universal uplink mechanism | |
| KR20020026263A (en) | Audio player | |
| JP2001358799A (en) | Data transmission system, data transmitter used in the data transmission system, data reproducing device and data transmitter method | |
| CN114758661A (en) | Bluetooth audio processing method and device and storage medium | |
| JP5301462B2 (en) | Apparatus for providing an encoded data signal and method for encoding a data signal | |
| KR100315328B1 (en) | Digital Portable Mobile Telephone and Methods for Inputting/Outputting and Storing/Retrieving Voice Data Therefor | |
| KR20060098734A (en) | Improved copyright information managing method and mobile terminal which has copyright information managing function in multimedia messaging system data | |
| KR100803661B1 (en) | Recording service method using mobile communication and internet | |
| JP2009033649A (en) | Content data transmitting/receiving system, content data transmitting device, content data receiving device, content data transmission method, content data reception processing method | |
| JP2009239848A (en) | Receiving apparatus and processing method, recording apparatus and processing method, program, recording medium, and network system | |
| KR100659460B1 (en) | Background music service method and system | |
| KR100650648B1 (en) | An apparatus for playing multimedia contents supplied by network in the mobile communication system and the method thereof | |
| KR101836220B1 (en) | Apparatus and method for media sharing | |
| KR100367582B1 (en) | Upload preventing method for data transmission system | |
| KR100442060B1 (en) | Method for recording sound and image using a wire and wireless telecommunication network and system therefor | |
| CN113963722B (en) | Method and device for controlling multiple devices to play different audios simultaneously and terminal device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |