Real-time data processing method and device and electronic equipment

Abstract

The embodiment of the invention provides a real-time data processing method and device and electronic equipment, and the real-time data processing method comprises the steps: building a session with a transmitting end, and obtaining real-time text data which is transmitted by the transmitting end and is related to an operation event; determining whether the operation events comprise risk operation events or not according to the real-time text data; and when the operation event comprises a risk operation event, stopping the operation event or terminating the session.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of information technology, and in particular to a real-time data processing method, device and electronic device. Background Art

[0002] With the development of real-time communications (RTC) technology, applications such as real-time audio and video calls, video conferencing, online education, remote control, and data transmission have grown massively, and RTC is widely used in IoT solutions.

[0003] WebRTC is an open Internet standard for embedding real-time multimedia communication capabilities into web pages. WebRTC can use application programming interfaces (APIs) to equip devices with RTC capabilities without requiring users to download plug-ins. Summary of the invention

[0004] Remote control is a technology that controls external devices through a network connection. Currently, a method of remotely controlling external devices based on RTC has been proposed. When the external device is a device with high requirements on security or privacy, such as a medical device, how to avoid risks or non-compliant remote operations becomes an urgent problem to be solved.

[0005] In response to at least one of the above problems, embodiments of the present application provide a real-time data processing method, device, and electronic device.

[0006] According to one aspect of an embodiment of the present application, a real-time data processing method is provided, including:

[0007] Establishing a session with a sending end, and acquiring real-time text data related to an operation event sent by the sending end;

[0008] Determining whether the operation event includes a risk operation event according to the real-time text data;

[0009] When the operation events include risky operation events, the operation events are blocked or the session is terminated.

[0010] According to one aspect of an embodiment of the present application, a real-time data processing device is provided, including:

[0011] An acquisition unit, which establishes a session with a sending end and acquires real-time text data related to an operation event sent by the sending end;

[0012] an identification unit, which determines whether the operation event includes a risk operation event according to the real-time text data;

[0013] A management unit, which blocks the operation event or terminates the session when the identification unit determines that the operation event includes a risky operation event.

[0014] According to one aspect of an embodiment of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program enables a computer to execute the real-time data processing method described in the aforementioned aspect.

[0015] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising the real-time data processing device described in the aforementioned aspect.

[0016] With reference to the following description and accompanying drawings, the specific embodiments of the present application are disclosed in detail, indicating the way in which the principles of the present application can be adopted. It should be understood that the embodiments of the present application are not limited in scope. Within the scope of the terms of the appended claims, the embodiments of the present application include many changes, modifications and equivalents.

[0017] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other implementation methods can be obtained based on these drawings without creative work. In the drawings:

[0019] Figures 1 to 3 This is a schematic diagram of three typical network topologies of WebRTC;

[0020] Figure 4 is a schematic diagram of a real-time data processing method according to an embodiment of the present application;

[0021] Figure 5 is a schematic diagram of a graphical user interface of an embodiment of the present application;

[0022] Figure 6 is a schematic diagram of a real-time data processing device according to an embodiment of the present application;

[0023] Figure 7 is a schematic diagram of an electronic device according to an embodiment of the present application;

[0024] Figure 8It is a schematic diagram of a real-time data processing method according to an embodiment of the present application. DETAILED DESCRIPTION

[0025] With reference to the accompanying drawings, the foregoing and other features of the embodiments of the present application will become apparent through the following description. In the description and the accompanying drawings, specific embodiments of the present application are specifically disclosed, which show some embodiments in which the principles of the embodiments of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the embodiments of the present application include all modifications, variations and equivalents that fall within the scope of the attached claims.

[0026] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the title, but do not represent the spatial arrangement or time sequence of these elements, etc., and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the terms listed in association. The terms "comprise", "include", "have", etc. refer to the existence of the stated features, elements, components or components, but do not exclude the existence or addition of one or more other features, elements, components or components. In the present application, the words "connect", "connected", "coupled", etc. and the like involved in the embodiments are not limited to physical or mechanical connections, but may include electrical connections, whether directly or indirectly.

[0027] In the embodiments of the present application, the singular forms "a", "the", etc. include plural forms and should be broadly understood as "a kind" or "a type" rather than being limited to the meaning of "one"; in addition, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. In addition, the term "according to" should be understood as "at least in part according to...", and the term "based on" should be understood as "at least in part based on...", unless the context clearly indicates otherwise.

[0028] Features described and / or shown for one embodiment may be used in one or more other embodiments in the same or similar manner, combined with features in other embodiments, or replace features in other embodiments. The term "includes / comprising" when used herein refers to the presence of a feature, an entirety, a step, or a component, but does not exclude the presence or addition of one or more other features, entireties, steps, or components.

[0029] To facilitate understanding, the following describes the technologies involved in the embodiments of the present application.

[0030] Session Traversal Utilities for NAT (STUN) and Traversal Using Relays around NAT (TURN) are protocols used to solve the Network Address Translation (NAT) problem. In WebRTC applications, STUN and TURN servers are used to help participants establish peer-to-peer (P2P) connections behind NAT. STUN servers are used to detect NAT types and IP addresses. When participants are in different network environments, STUN servers can enable them to exchange IP address information and establish P2P connections, but sometimes NAT blocks the transmission of P2P messages. TURN servers can act as relay nodes between two participants in an end-to-end connection to transmit messages. STUN servers and TURN servers provide the necessary technical support for WebRTC scenarios.

[0031] WebRTC includes three typical network topologies: mesh topology, multipoint control unit (MCU) topology and selective forwarding unit (SFU) topology.

[0032] Mesh is the simplest network structure for WebRTC multi-party sessions. In this structure, each participant sends media streams to all other participants and receives media streams sent by all other participants at the same time, without the participation of a media server. Figure 1 This is a diagram of the Mesh network topology. In the Mesh network structure, each participant is connected to each other in a P2P manner, and data exchange basically does not go through a central server (in some scenarios where P2P cannot be used, it will go through a TURN server). Since each participant needs to provide independent media streams for other participants, N-1 uplinks and N-1 downlinks are required (the links are as follows Figure 1 As shown by the line segment with an arrow in the middle, it should be noted that since the participants are interconnected, for one participant, the link that sends the media stream can be regarded as an uplink, and the link that receives the media stream can be regarded as a downlink, and vice versa).

[0033] The multipoint control unit MCU (Multipoint Control Unit) is a traditional centralized network structure. Figure 2This is a schematic diagram of the MCU network topology. Each participant is only connected to the central server. The MCU central server merges the media streams of all participants to generate a media stream containing the screens of all participants. Participants only need to pull the merged screen. In this scenario, each participant only needs one uplink and one downlink (where the link where the participant sends the media stream to the central server is the uplink, and the link where the central server sends the media stream to the participant is the downlink).

[0034] The Selective Forwarding Unit (SFU) is also a centralized network structure. Figure 3 This is a schematic diagram of the SFU network topology. In the SFU network structure, there is still a central server, but the central server is only responsible for forwarding and does not perform media processing tasks that require large resource consumption, such as confluence and transcoding. Each participant sends media data to the central server and directly receives media data from each other participant from the central server. Each participant requires 1 uplink and N-1 downlinks (where the link where the participant sends the media stream to the central server is the uplink, and the link where the central server sends the media stream to the participant is the downlink).

[0035] The SFU server is considered as a WebRTC participant. It establishes a one-to-one connection with all other participants and acts as a bridge, forwarding the media data of each participant. The SFU server has the ability to replicate media data and can forward the data of one participant to multiple participants. Unlike the TURN server, the TURN server is only an auxiliary data forwarding channel provided for the WebRTC client. It performs transparent data forwarding when P2P cannot be used. The TURN server does not have the ability to replicate and forward media data.

[0036] The embodiment of the present application provides a real-time data processing method.

[0037] Figure 4 is a schematic diagram of a real-time data processing method according to an embodiment of the present application. Figure 4 As shown, the method includes:

[0038] 401, establishing a session with a sending end, and acquiring real-time text data related to an operation event sent by the sending end;

[0039] 402, determining whether the operation event includes a risk operation event according to the real-time text data;

[0040] 403: When the operation event includes a risky operation event, block the operation event or terminate the session.

[0041] In some embodiments, the real-time data communication in the present application is based on WebRTC and adopts a centralized network topology, such as the aforementioned MCU or SFU, that is, each sending end is only connected to the central server, and the functions performed by the aforementioned 401-403 can be integrated into the processor of the central server, and 401-403 are executed by the central server, or integrated into a chip connected to the processor of the central server, and 401-403 are executed under the control of the processor of the central server.

[0042] In some embodiments, the above-mentioned sending end can be one or more user devices (browsers, applications, etc.) participating in real-time communication (such as video conferencing, remote control, etc.). The user device can be a smart phone, a laptop computer, a tablet computer, a TV, etc. The central server and the sending end use the Session Description Protocol (SDP) to establish a session (including the caller or the called party). The steps of establishing a session include: the caller configures the session parameters (for example, whether the session includes media streams, media stream types, transmission protocols, media formats and other parameters), creates an initiation (Offer) signaling including the SDP description of the caller, forwards the Offer signaling to the called party via the server, the called party extracts the SDP description in the Offer signaling, and creates an answer (Answer) signaling, returns the answer signaling to the caller, and then the caller and the called party send their respective address + port number information to each other, and a session connection can be established. For the operation of establishing a session, please refer to the relevant technology and will not be repeated here.

[0043] In some embodiments, the real-time text data includes but is not limited to text data generated in the above application scenarios, such as text data generated by real-time text chat, text data generated by file transfer, or text data generated by real-time remote control.

[0044] In some embodiments, the above-mentioned real-time text data can be generated according to the operation event input by the input device of the sending end, and the input device can be at least one of a keyboard and a mouse. For example, the operation event can be input via the input device of the sending end, and the operation event includes but is not limited to the keyboard typing operation event, the mouse clicking operation event, the mouse moving / dragging operation event, etc. The above-mentioned operation event can be used to remotely control the electronic device of the receiving end, or the operation event can be used to input or send the chat content, or the operation event can be used to drag or send files, etc. The sending end (browser, application, etc.) can capture the operation event input by the input device, for example, it can capture the operation event of the mouse moving (such as the mouse coordinate position information), the mouse clicking operation event (such as which key is clicked), the keyboard typing operation event (such as which key of the keyboard is pressed), etc. At least one of the above-mentioned operation events, will generate real-time text data based on the captured operation event, and transmit it to the server side for processing through the interface. For example, the generated real-time text data (such as Json file format, etc.) can be transmitted to the server through the interface in JavaScript syntax, but the embodiment of the present application is not limited to this.

[0045] In some embodiments, the real-time text data may be plain text data, and may include an operation event name, an operation event parameter object, etc. For example, the operation event name for a mouse may include: click click, double click dblclick, mousedown, mouseup, mousemove, etc., and the parameter object may include the horizontal coordinate screenX of the mouse pointer on the screen, the vertical coordinate screenY of the mouse pointer on the screen, the horizontal coordinate clientX of the mouse pointer in the visible area of ​​the current window of the browser page, the horizontal coordinate clientY of the mouse pointer in the visible area of ​​the current window of the browser page, etc. The operation event name for a keyboard may include: press keydown, release keypress, etc., and the parameter object may include a key code (keyCode) or an input string after a combination of key codes, which will not be exemplified one by one here.

[0046] In some embodiments, after establishing a session, real-time text data can be obtained through a dedicated interface of WebRTC (e.g., RTCDataChannelAPI), which can use the stream control transport protocol (SCTP) to transmit the real-time text data. The sender can create a new data channel in the connection and invite the receiver to receive the new data channel event created by it. The receiver can learn about the data channel by monitoring, and then receive the real-time text data generated by the sender on the data channel. For details, please refer to the relevant technology, and the embodiments of the present application are not limited to this.

[0047] In some embodiments, when acquiring real-time text data, real-time media data may or may not be acquired from the sender at the same time. For example, real-time media data may be acquired through a media-specific interface (e.g., MediaStream API), which may access the sender input device (e.g., camera and / or microphone) to acquire real-time media data. The real-time media data is a real-time media stream, including at least one of an audio stream and a video stream. The format of the real-time media data includes, but is not limited to, MP3, MP4, AVI, MOV, M4V, etc., which are not exemplified one by one here. In other words, real-time text data may be sent simultaneously with real-time media data, or only real-time text data may be sent without sending real-time media data. The embodiments of the present application are not limited to this.

[0048] For example, the sender can input real-time chat data (transmit real-time text data) on the video stream graphical user interface (chat box) during a remote conference or remote control desktop (transmitting real-time video stream) (hereinafter referred to as scenario one). Alternatively, the device can be controlled in accordance with operation events (transmitting real-time text data) during remote control desktop (transmitting real-time video stream) (hereinafter referred to as scenario two). Alternatively, real-time media data may not be sent, and only file transfer (transmitting real-time text data) may be performed (hereinafter referred to as scenario three). Alternatively, real-time media data may not be sent, and only remote control (transmitting real-time text data) may be performed (hereinafter referred to as scenario four), and examples are not given one by one here.

[0049] In some embodiments, after the acquired real-time text data passes through the gateway, the real-time text data can also be stored (cached) (incremental storage) to determine whether the operation event includes a risky operation event. For example, the real-time text data can be stored (cached) by the STUN server or TURN server of the aforementioned central server, but the embodiments of the present application are not limited to this.

[0050] In some embodiments, a risk database or a lookup table (LUT) may be preset, and the database or the lookup table includes at least one of a preset risk field and a preset risk value range, and the preset risk field may include a risk operation event field, a risk parameter object field, a risk keyword, etc. The preset risk value range may include a risk parameter object value range, such as a risk mouse pointer coordinate position range, a risk key code value range, etc., as illustrated by the following example.

[0051] For example, for the above-mentioned scenarios 1 and 3, risk keywords can be preset to identify whether the real-time text data (real-time chat data or transmission files) contains the risk keyword. The risk keyword may include sensitive information, thereby avoiding the leakage of sensitive information. The sensitive information includes: at least one of personal health information and personal identification information; for example, personal health information includes disease diagnosis information, hospitalization information, medical history information, fertility information, etc., and personal identification information includes name, certificate information, etc., which are not listed one by one here. The risk keyword includes, for example, different disease diagnosis information keywords, medical history information keywords, fertility information keywords, etc.

[0052] For example, for the above-mentioned scenarios 2 and 4, at least one of the risk operation event field, the risk parameter object field and the preset risk parameter object value range can be preset to identify whether the real-time text data (operation event related to remote control) contains the risk operation event, thereby avoiding remote risk operations. The risk operation event field may include pressing the key keydown or clicking click, etc., and the risk parameter object field may include the key code of the screenshot key PrtSc on the keyboard, the key code for quick control of the opening or closing or other states of the receiving electronic device (such as F1, F2, F3, F4, F5, etc.), the key code for copying and pasting (ctrl+C or ctrl+V), etc., which are not exemplified here. The risk parameter object value range may include the value range of the key code of the preset letter key on the keyboard, the value range of the mouse horizontal coordinate screenX or clientX, and the value range of the vertical coordinate screenY or clientY. The above-mentioned preset value range (at least one of the upper limit and the lower limit) may correspond to the position of certain virtual buttons on the graphical user interface of real-time media data transmission or the remote control graphical user interface, thereby limiting the remote control of these virtual buttons.

[0053] Figure 5 is a schematic diagram of a graphical user interface of an embodiment of the present application, such as Figure 5 As shown, the interface can be a remote control interface of a medical device, and the horizontal and vertical coordinate ranges of the screenshot, start scanning, backup, and copy buttons in the interface can be pre-determined, and the above coordinate ranges can be saved as preset risk parameter object value ranges.

[0054] In some embodiments, the real-time text data can be compared with preset risk keywords. When the real-time text data includes the preset risk keywords, it is determined that the operation event includes a risk operation event. When the real-time text data does not include the preset risk keywords, it is determined that the operation event does not include a risk operation event. Wherein, the real-time text data is character matched with the preset risk keywords. When there is a matching string, it is determined that the real-time text data includes the preset risk keywords, and it is determined that the operation event includes a risk operation event. For example, if the real-time text data includes the aforementioned sensitive information, it means that the real-time chat data input by the input device of the sending end includes sensitive information, and it is determined that the input operation event includes a risk operation event.

[0055] In some embodiments, the real-time text data can be compared with a preset risk field, and when the preset risk field is included in the real-time text data, it is determined that the operation event includes a risk operation event. When the preset risk field is not included in the real-time text data, it is determined that the operation event does not include a risk operation event. Wherein, the real-time text data and the preset risk field are character matched, and when there is a matching string, it is determined that the real-time text data includes the preset risk field, and it is determined that the operation event includes a risk operation event. For example, if the real-time text data includes the aforementioned preset risk operation event field or risk parameter object field, it means that the operation event of the sending end input device includes a risk operation event.

[0056] In some embodiments, the real-time text data can be compared with a preset risk value range. When the real-time text data includes data within the preset risk value range, it is determined that the operation event includes a risk operation event. When the real-time text data does not include data within the preset risk value range, it is determined that the operation event does not include a risk operation event. For example, when the real-time text data includes the coordinates of the mouse pointer, the coordinate value of the mouse pointer is compared with the preset risk value range. If the coordinate value is within the preset risk value range, it means that the operation event of the input device at the sending end includes a risk operation event.

[0057] Each of the above embodiments can be implemented separately or in combination, and the embodiments of the present application are not limited thereto. For example, the real-time text data can be compared with a preset risk field, and the real-time text data can be compared with a preset risk value range. When the real-time text data includes the preset risk field and the real-time text data includes data within the preset risk value range, it is determined that the operation event includes a risk operation event. For example, when the real-time text data includes the coordinates of the mouse pointer, the coordinate value of the mouse pointer is compared with the preset risk value range. If the coordinate value is within the preset risk value range, it is further determined whether a single-click operation is triggered at the position of the mouse pointer, that is, whether the real-time text data corresponding to the mouse pointer coordinates also contains a single-click field (preset risk field). If the single-click field is also included, it means that the mouse pointer has not only moved to the position of the risk virtual button, but also performed a click operation, and it is determined that the operation event includes a risk operation event.

[0058] In the above example, a preset risk database or lookup table (LUT) is used to determine whether the operation event includes a risk operation event, but the present application is not limited to this. For example, a neural network model for identifying risk operation events can also be pre-trained, and the real-time text data is used as the input of the neural network model. The output results of the neural network model are 2, one is that the operation event includes a risk operation event, and the other is that the operation event does not include a risk operation event, which will not be described one by one here.

[0059] The preset risk database or lookup table (LUT) in the above embodiments, or the pre-trained neural network model can be stored in a memory in the central server, or in an independent memory connected to the central server, but the embodiments of the present application are not limited to this.

[0060] In some embodiments, in 403, when the operation event includes a risk operation event, the operation event is blocked or the session is terminated. Wherein, terminating the session includes closing the corresponding session connection and releasing resources, and stopping the transmission of real-time text data. Blocking the operation event includes maintaining the session, but not responding to the operation event, or shielding the operation event. For example, when the operation event is used to remotely control the electronic device of the receiving end, blocking the operation event means that the electronic device of the receiving end does not respond to the operation event, or does not perform the remote control corresponding to the operation event. Alternatively, when the operation event is used to input or send chat content, blocking the operation event means shielding the real-time text data (real-time chat content) input by the input device of the sending end. Alternatively, when the operation event is used to transfer files, blocking the operation event means blocking file transmission. In addition, when the operation event does not include a risk operation event, the session is maintained and subsequent real-time text data is continuously monitored.

[0061] In some embodiments, for different types of risky operation events, a processing method of blocking the operation event or terminating the session can be adopted. Alternatively, different processing methods are adopted for different types of risky operation events. For example, when the risky operation event is used to input or send chat content, or to transfer files, the operation event is blocked, and when the risky operation event is used to remotely control the electronic device of the receiving end, the session is terminated. This is only an example, and the embodiments of the present application are not limited to this.

[0062] In some embodiments, different risk levels can also be set for different risk operation events in a preset risk database or lookup table (LUT). When the risk level of the identified risk operation event is high, the session is terminated, and when the risk level of the identified risk operation event is low, the operation event is blocked. For example, when the risk operation event is pressing the keyboard F5, it means that the quick control operation is to control the medical device at the receiving end to start scanning. The risk level of this risk operation event is set to high. When the operation event includes this risk operation event, the session is terminated; when the risk operation event is pressing the keyboard PrtSc, it means that the quick control operation is to take a screenshot. The risk level of this risk operation event is set to low. When the operation event includes this risk operation event, the screenshot operation is blocked and the session does not need to be terminated. When the risk operation event is real-time text data including sensitive information, the risk level of this risk operation event is set to high. When the operation event includes this risk operation event, the session is terminated. Examples are not given one by one here.

[0063] In some embodiments, when the operation event includes a risk operation event, the operation event is blocked, and when the number of operation events blocked within a predetermined time exceeds a predetermined number, the session is terminated, thereby avoiding malicious attacks from the sender. For example, the risk operation event is pressing the keyboard PrtSc, which indicates a quick control operation screenshot. When it is determined in 402 that the operation event includes the risk operation event, the screenshot operation is blocked in 403. However, when N times of typing PrtSc are identified within a predetermined time, and then N times of screenshot operations are blocked, and N is greater than or equal to the predetermined number, the session can be terminated. The predetermined number can be determined as needed, and the embodiments of the present application are not limited thereto.

[0064] Figure 8 is a schematic diagram of a real-time data processing method according to an embodiment of the present application. Figure 8 As shown, the method includes:

[0065] 801, input operation event of input device at the sending end;

[0066] 802, generating real-time text data according to the operation event;

[0067] 803, transmitting the real-time text data through the RTCDataChannel API;

[0068] 804, identifying whether the operation event includes a risk operation event according to the real-time text data, and if so, executing 806, otherwise executing 805;

[0069] 805, maintain session;

[0070] 806, determining the processing method to be blocking the operation event or terminating the session according to the risk operation event type or risk level, and when the processing method is determined to be terminating the session, executing 807, otherwise, executing 808 to 809;

[0071] 807, terminate the session;

[0072] 808, prevent operation event;

[0073] 809, whether the operation events blocked within the predetermined time exceed the predetermined number, if so, execute 810, otherwise execute 811;

[0074] 810, terminate the session;

[0075] 811, maintain session.

[0076] The above embodiments are merely exemplary of the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0077] The embodiment of the present application also provides a real-time data processing device, which corresponds to the real-time data processing method in the above-mentioned embodiment.

[0078] Figure 6 is a schematic diagram of a real-time data processing device according to an embodiment of the present application, such as Figure 6 As shown, the real-time data processing device 600 includes:

[0079] An acquisition unit 601 establishes a session with a sending end and acquires real-time text data related to an operation event sent by the sending end;

[0080] An identification unit 602, which determines whether the operation event includes a risk operation event according to the real-time text data;

[0081] The management unit 603 blocks the operation event or terminates the session when the identification unit 602 determines that the operation event includes a risky operation event.

[0082] The implementation of the acquisition unit 601 , the identification unit 602 , and the management unit 603 may refer to 401 to 403 , which will not be repeated here.

[0083] The above embodiments are merely exemplary of the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0084] The present application also provides an electronic device, Figure 7 is a schematic diagram of an electronic device according to an embodiment of the present application. Figure 7 As shown, the electronic device 700 may include: at least one interface (not shown in the figure), a processor (eg, a central processing unit (CPU)) 701 , and a memory 702 ; the memory 702 is coupled to the processor 701 .

[0085] In some embodiments, the functions of the real-time data processing device 600 described in the above embodiments may be integrated into the processor 701. For example, the processor 701 may be configured to: establish a session with a sending end, obtain real-time text data related to an operation event sent by the sending end; determine whether the operation event includes a risk operation event according to the real-time text data; and when the operation event includes a risk operation event, block the operation event or terminate the session.

[0086] Alternatively, the real-time data processing device 600 may be configured as a chip connected to the processor 701 , and the corresponding functions may be implemented under the control of the processor 701 .

[0087] It is worth noting that the electronic device 700 may also include Figure 7 For components not shown, reference may be made to the prior art.

[0088] In the embodiment of the present application, the processor 701 is sometimes also referred to as a controller or an operation control, and may include a microprocessor or other processor devices and / or logic devices.

[0089] In some embodiments, the memory 702 can store various data; in addition, it also stores a real-time data processing program 703 and real-time data and a pre-set risk database or lookup table (LUT), or a pre-trained neural network model, and executes the program 703 under the control of the processor 701.

[0090] In some embodiments, the electronic device may be, for example, a personal computer, a server, a cloud computer, a workstation, a laptop computer, a mobile terminal, etc.; however, the embodiments of the present application are not limited thereto.

[0091] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in an electronic device, the program enables the electronic device to perform the real-time data processing method of the embodiment.

[0092] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the real-time data processing method of the embodiment.

[0093] An embodiment of the present application also provides a medical device (not shown). The medical device described herein includes but is not limited to a computed tomography (CT) device, a magnetic resonance imaging (MRI) device, a C-arm imaging device, a positron emission tomography (PET) device, a single photon emission computed tomography (SPECT) device, an ultrasound device, an X-ray imaging device, or any other suitable medical device.

[0094] For example, the medical device may include the aforementioned real-time data processing device 600 or electronic device 700. Alternatively, the medical device may be connected to the aforementioned real-time data processing device 600 or electronic device 700, and the real-time data processing method may also be independently or jointly implemented by the aforementioned medical device, a computer device connected to the medical device, and a computer device connected to the Internet cloud. The embodiments of the present application are not limited thereto.

[0095] One of the beneficial effects of the embodiments of the present application is that: determining whether the operation event includes a risky operation event based on the real-time text data, and when the operation event includes a risky operation event, blocking the operation event or terminating the session, thereby preventing risky operations based on real-time communication and enhancing the security of real-time communication.

[0096] In addition, the real-time text data is generated based on the operation events input by the input device (such as a mouse or keyboard) of the sending end, and the operation events are used to remotely control the electronic equipment of the receiving end, thereby preventing risky operations such as remote control of the mouse or keyboard by controlling medical equipment through real-time communication.

[0097] In addition, by presetting risk fields or presetting risk value ranges, risk operation events can be identified efficiently and accurately.

[0098] In addition, when the number of operation events blocked within a predetermined time exceeds a predetermined number, the session is terminated, thereby avoiding malicious attacks from the sending end.

[0099] The above devices and methods of the present application can be implemented by hardware, or by hardware combined with software. The present application relates to such a computer-readable program, which, when executed by a logic component, enables the logic component to implement the above-mentioned devices or components, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0100] The method / device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of the functional block diagrams may correspond to various software modules of the computer program flow or to various hardware modules. These software modules may correspond to the various steps shown in the figure, respectively. These hardware modules may be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0101] The software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in a memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if a device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0102] For one or more of the functional blocks described in the drawings and / or one or more combinations of functional blocks, it can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component or any appropriate combination thereof for performing the functions described in the present application. For one or more of the functional blocks described in the drawings and / or one or more combinations of functional blocks, it can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0103] The present application is described above in conjunction with specific implementation methods, but it should be clear to those skilled in the art that these descriptions are exemplary and are not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on the principles of the present application, and these modifications and variations are also within the scope of the present application.

Claims

1. A real-time data processing method, characterized in that: The method comprises: Establishing a session with a sending end, and acquiring real-time text data related to an operation event sent by the sending end; Determining whether the operation event includes a risk operation event according to the real-time text data; When the operation events include risky operation events, the operation events are blocked or the session is terminated.

2. The method according to claim 1, characterized in that The real-time text data is generated according to the operation event input by the input device of the sending end.

3. The method according to claim 2, characterized in that The input device includes at least one of a keyboard and a mouse.

4. The method according to claim 1, characterized in that: The operation event is used to remotely control the electronic device at the receiving end.

5. The method according to claim 1, characterized in that Determining whether the operation event includes a risk operation event according to the real-time text data includes: The real-time text data is compared with a preset risk field, and when the real-time text data includes the preset risk field, it is determined that the operation event includes a risk operation event.

6. The method according to claim 1, characterized in that Determining whether the operation event includes a risk operation event according to the real-time text data includes: The real-time text data is compared with a preset risk value range, and when the real-time text data includes data within the preset risk value range, it is determined that the operation event includes a risky operation event.

7. The method according to claim 1, characterized in that The method further comprises: When the number of operation events blocked within a predetermined time exceeds a predetermined number, the session is terminated.

8. A real-time data processing device, characterized in that: The device comprises: An acquisition unit, which establishes a session with a sending end and acquires real-time text data related to an operation event sent by the sending end; an identification unit, which determines whether the operation event includes a risk operation event according to the real-time text data; A management unit, which blocks the operation event or terminates the session when the identification unit determines that the operation event includes a risky operation event.

9. A storage medium storing a computer-readable program, characterized in that: The computer-readable program enables a computer to execute the real-time data processing method according to any one of claims 1 to 7.

10. An electronic device, characterized in that: The electronic device comprises the real-time data processing device according to claim 8.

Images