CN112291322A - Application management method and system based on IMS - Google Patents
Application management method and system based on IMS Download PDFInfo
- Publication number
- CN112291322A CN112291322A CN202011137964.2A CN202011137964A CN112291322A CN 112291322 A CN112291322 A CN 112291322A CN 202011137964 A CN202011137964 A CN 202011137964A CN 112291322 A CN112291322 A CN 112291322A
- Authority
- CN
- China
- Prior art keywords
- message
- module
- file
- topic
- agent
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 63
- 238000012545 processing Methods 0.000 claims abstract description 55
- 238000000034 method Methods 0.000 claims abstract description 16
- 230000005540 biological transmission Effects 0.000 claims abstract description 10
- 238000009434 installation Methods 0.000 claims abstract description 9
- 239000000872 buffer Substances 0.000 claims abstract description 4
- 239000003795 chemical substances by application Substances 0.000 claims description 54
- 230000010365 information processing Effects 0.000 claims description 14
- 238000001514 detection method Methods 0.000 claims description 7
- 230000000977 initiatory effect Effects 0.000 claims 1
- 238000004891 communication Methods 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
-
- 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/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/562—Brokering proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses an application management method and system based on an IMS (IP multimedia subsystem), belonging to the field of middleware; the method comprises the following specific steps: s1 provides message transmission channel by IMS and buffers the message; s2 executing end management operation and processing commands sent by the cloud end; s3 receives and processes the register information message of the receiving end, and sends down the installation and management command to the receiving end; the method and the system provided by the invention can realize the communication between the cloud and the end and the management of the cloud opposite end, do not depend on SSH service, and do not need the end to have a public network IP. The method breaks through the limitation brought by the traditional SSH communication mode, solves the limitation of the opposite end or cloud IP configuration, and can provide a safer and more flexible management mode.
Description
Technical Field
The invention discloses an application management method and system based on an IMS (IP multimedia subsystem), and relates to the technical field of middleware.
Background
With the rapid development of cloud computing, big data, internet of things and edge computing, more and more services need to be preprocessed on one side close to an end and return a processing result to a cloud end, so that deployment of applications needs to be performed on one side close to the end, namely an edge side or an equipment side, and application management and data acquisition can be performed on the cloud end.
The traditional management of the cloud to the edge application is managed through ssh service, the ssh service needs to be opened, and the edge or the device end needs to have an external ip address. At present, various edge and end devices do not provide ssh service and external public network IP for security and network limitation, so that the traditional centralized management console cannot manage applications in an ssh manner.
The problem that a centralized management console cannot manage applications and acquire data under the condition that edges or equipment cannot authorize SSH (secure Shell) rights or cannot provide public network IP (Internet protocol) is solved; therefore, the invention provides a general communication mode independent of ssh service and an application management mode.
Disclosure of Invention
The invention provides an application management method and system based on IMS aiming at the problems of the prior art, and the adopted technical scheme is as follows: an application management method based on IMS is characterized in that the method comprises the following specific steps:
s1 provides message transmission channel by IMS and buffers the message;
s2 executing end management operation and processing commands sent by the cloud end;
s3 receives and processes the register information message of the receiving end, and sends the installation and management command to the end.
The specific steps of the S2 execution end management operation and processing the command sent by the cloud end include:
s201, searching whether an end id file exists;
s202, when the end id file is not detected, the generated uuid is used as the end id, end node information is obtained and assembled into json format information, and the json format information is sent to agent _ common _ topic;
s212, when the terminal id file is detected, acquiring the message circularly from the agent _ receive _ topic, and processing according to the message type
When the end id file is detected in the S212, the message is obtained from the agent _ receive _ topic in a cycle, and is processed according to the message type, which includes the specific steps of:
s2121, when the message type is DZCH, completing registration and writing the end id into a file;
s2122, when the message type is DWF, after the received message is analyzed, writing the file into a specified position, generating a DWFH message according to the execution condition, and sending the DWFH message to agent _ send _ topic;
s2123, when the message type is DWH, converting the file read at the specified position into a byte stream and sending the byte stream to agent _ send _ topic;
s2124, when the message type is DWF, the message acquisition command is analyzed and executed, and the DMFH command is generated according to the execution result and sent to agent _ send _ topic.
And when the step S212 is executed, starting heartbeat counting and sending the generated heartbeat information to the agent _ common _ topic.
An application management system based on IMS specifically comprises a message module, an end management module and a cloud management module:
a message module: providing a message transmission channel by using an IMS (IP multimedia subsystem) and caching messages;
end management module: executing end management operation and processing commands sent by a cloud end;
the cloud management module: after receiving and processing the register information message of the receiving end, the receiving end sends an installation and management command to the end
The end management module specifically comprises an end detection module, an information assembly module and an information processing module:
an end detection module: searching whether an end id file exists;
an information assembly module: when the end id file is not detected, the generated uuid is used as the end id, end node information is obtained and assembled into json format information, and the json format information is sent to agent _ common _ topic;
an information processing module: when the terminal id file is detected, acquiring messages circularly from the agent _ receive _ topic, and processing according to the message type
The information processing module specifically comprises an A processing module, a B processing module, a C processing module and a D processing module:
the A processing module: when the message type is DZCH, completing registration and writing the terminal id into a file;
and a B processing module: when the message type is DWF, after the received message is analyzed, writing the file into a specified position, generating a DWFH message according to the execution condition, and sending the DWFH message to agent _ send _ topoic;
and a C processing module: when the message type is DWH, converting the file read at the specified position into a byte stream and sending the byte stream to agent _ send _ topic;
and a D processing module: and when the message type is DWF, analyzing the message acquisition command, executing, generating a DMFH command according to an execution result, and sending the DMFH command to the agent _ send _ topic.
The end management module also comprises a heartbeat module, and when the information processing module works, the heartbeat module starts heartbeat counting and sends generated heartbeat information to the agent _ common _ topic.
The invention has the beneficial effects that: the method and the system provided by the invention can realize the communication between the cloud and the end and the management of the cloud opposite end, do not depend on SSH service, and do not need the end to have a public network IP. The method breaks through the limitation brought by the traditional SSH communication mode, solves the limitation of the opposite end or cloud IP configuration, and can provide a safer and more flexible management mode.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow chart of the method of the present invention; FIG. 2 is a schematic diagram of the system of the present invention; fig. 3 is a schematic diagram of an embodiment of the present invention.
Detailed Description
The present invention is further described below in conjunction with the following figures and specific examples so that those skilled in the art may better understand the present invention and practice it, but the examples are not intended to limit the present invention.
The IMS is a high-performance message middleware in cloud and big data era, provides high-performance and high-reliability message queue service to the outside in a cloud service and cluster mode, supports the caching and transmission of mass data, meets the requirements of big data real-time processing and micro-service processing architecture, Topic is an important concept in message service, each Topic represents a type of message, the message is cached in the Topic, the message can be classified and isolated through a plurality of Topics, and the message module architecture is shown in figure 1;
messages are transmitted between topics through the SN service as well as the RS service. SN is message sending service, and sends the message in TopicA to TopicB, and the node at TopicB side must have IP or domain name address that TopicA can access; the RS serves for the message reverse sending, and also sends the message in the TopicA to the TopicB, but the node on the TopicB side can not have the IP or domain name address which the TopicA can access; SN and RS services rely on TCP/IP protocol for messaging and not on ssh. For each end, there are 3 pairs of Topic, agent _ common _ Topic and cloud _ common _ Topic, which are used for the end module to send a registration message and a heartbeat message to the cloud module; agent _ send _ topic and closed _ receive _ topic _ $ id are used for the end module to send other messages to the cloud module, for example, the result of a command issued by the cloud end, wherein the $ id is the only id of the end; the agent _ receive _ topic and the closed _ send _ topic _ $ id are used for the cloud module to send other messages to the end module, such as sending a command and related files to the end module. One for different terminals cloudcommon topic may be shared.
In order to better analyze the message content in Topic, the format of the message is agreed, and the message is in the format of a byte stream, as follows:
the format is as follows:
| MsgType | MsgContent | other messages |
The information of each field is as follows:
the message type and json format of the message are shown in the following table:
the above message defines 5 operation types, including registration operation, end file acquisition operation, end command execution operation, end file sending operation, and heartbeat operation;
with reference to the above description, two examples were chosen to illustrate embodiments of the present invention:
the first embodiment is as follows:
an application management method based on IMS, the method includes the following steps:
s1 provides message transmission channel by IMS and buffers the message;
s2 executing end management operation and processing commands sent by the cloud end;
s3 receives and processes the register information message of the receiving end, and sends down the installation and management command to the receiving end;
firstly, providing a message transmission channel between a cloud and a terminal by using an IMS according to S1, realizing based on a wave IMS message service, caching messages, then executing terminal management operation according to S2, configuring an ip domain name of the cloud, finally receiving and processing registration information of a receiving terminal according to S3, and issuing an installation and management command to the terminal;
further, the specific steps of the S2 executing the end management operation and processing the command sent by the cloud end include:
s201, searching whether an end id file exists;
s202, when the end id file is not detected, the generated uuid is used as the end id, end node information is obtained and assembled into json format information, and the json format information is sent to agent _ common _ topic;
s212, when the terminal id file is detected, acquiring a message circularly from the agent _ receive _ topic, and processing according to the message type;
when the end management step is started, whether an end id file exists is detected according to S201, if the end id file exists, the end id file indicates that the end is registered, S212 is executed, information is obtained circularly from agent _ receive _ topic, and processing is carried out according to the type of the information;
if the file is not detected, the file indicates that the file is not registered for the first time, namely the generated uuid is used as an end id according to S202, information such as an ip of an end node and a current user is obtained and assembled into json format information, and the json format information is sent to agent _ common _ topic;
further, when the end id file is detected in S212, the message is obtained from the agent _ receive _ topic in a cycle, and is processed according to the message type, which includes the specific steps of:
s2121, when the message type is DZCH, completing registration and writing the end id into a file;
s2122, when the message type is DWF, after the received message is analyzed, writing the file into a specified position, generating a DWFH message according to the execution condition, and sending the DWFH message to agent _ send _ topic;
s2123, when the message type is DWH, converting the file read at the specified position into a byte stream and sending the byte stream to agent _ send _ topic;
s2124, when the message type is DWF, analyzing the message acquisition command, executing the message acquisition command, generating a DMFH command according to an execution result, and sending the DMFH command to the agent _ send _ topic;
when the end id file is detected in S212, acquiring a message circularly from the agent _ receive _ topic, and when the acquired message is DZCH, indicating that the message is a registration reply message, namely completing registration and writing the message into the file according to S2121, if the registration is successful, writing the end id into the file, and if the registration is failed, continuing to register at intervals; when the acquired message type is DWF, a file is issued to the terminal, the received information needs to be analyzed according to S2122, the file is written into a designated position, a DWFH message is generated according to the execution condition, and the DWFH message is sent to agent _ send _ topic; when the acquired message type is DWH, the file is acquired by the user terminal, the file is read from the designated position according to S2123, converted into a byte stream and sent to agent _ send _ topic; when the acquired message type is DWF, the cloud sends a command to the terminal for execution, the message acquisition command is analyzed and executed according to S2124, a DMFH command is generated according to the execution result, and the DMFH command is sent to agent _ send _ topic;
still further, while the step S212 is executed, a heartbeat count is started to send the generated heartbeat information to the agent _ common _ topic.
Example two:
an application management system based on IMS specifically comprises a message module, an end management module and a cloud management module:
a message module: providing a message transmission channel by using an IMS (IP multimedia subsystem) and caching messages;
end management module: executing end management operation and processing commands sent by a cloud end;
the cloud management module: after receiving and processing the registration information message of the receiving end, sending an installation and management command to the end;
firstly, providing a message transmission channel between a cloud and a terminal by using an IMS (IP multimedia subsystem) through a message module, realizing based on a wave IMS message service, caching a message, then performing terminal management operation by using a terminal management module, configuring an ip domain name of a cloud terminal, finally receiving and processing registration information of a receiving terminal through the cloud management module, and issuing an installation and management command to the terminal;
further, the end management module specifically includes an end detection module, an information assembly module and an information processing module:
an end detection module: searching whether an end id file exists;
an information assembly module: when the end id file is not detected, the generated uuid is used as the end id, end node information is obtained and assembled into json format information, and the json format information is sent to agent _ common _ topic;
an information processing module: when the terminal id file is detected, acquiring a message circularly from the agent _ receive _ topic, and processing according to the message type;
when the terminal management module is started, firstly, the terminal detection module is used for detecting whether a terminal id file exists or not, if the terminal id file exists, the terminal id file indicates that the terminal is registered, the information processing module is used for acquiring messages circularly from the agent _ receive _ topic and processing the messages according to the message types;
if the file is not detected, the file indicates that the file is not registered for the first time, namely the generated uuid is used as an end id through an information assembling module, information such as an ip of an end node and a current user is obtained and assembled into json format information, and the json format information is sent to agent _ common _ topic;
further, the information processing module specifically includes a processing module a, a processing module B, a processing module C, and a processing module D:
the A processing module: when the message type is DZCH, completing registration and writing the terminal id into a file;
and a B processing module: when the message type is DWF, after the received message is analyzed, writing the file into a specified position, generating a DWFH message according to the execution condition, and sending the DWFH message to agent _ send _ topoic;
and a C processing module: when the message type is DWH, converting the file read at the specified position into a byte stream and sending the byte stream to agent _ send _ topic;
and a D processing module: and when the message type is DWF, analyzing the message acquisition command, executing, generating a DMFH command according to an execution result, and sending the DMFH command to the agent _ send _ topic.
When the information processing module detects a terminal id file, acquiring a message circularly from the agent _ receive _ topic, and when the acquired message is DZCH, indicating that the message is a registration reply message, namely completing registration and writing the message into the file through the A processing module, if the registration is successful, writing the terminal id into the file, and if the registration is failed, continuing to register at intervals; when the acquired message type is DWF, a file is issued to the terminal, the received information needs to be analyzed through the B processing module, the file is written into a designated position, a DWFH message is generated according to the execution condition, and the DWFH message is sent to agent _ send _ topic; when the acquired message type is DWH, the file is acquired by the user end, the file is read from the designated position by the C processing module, converted into a byte stream and sent to agent _ send _ topic; when the acquired message type is DWF, the cloud sends a command to the terminal for execution, the D processing module analyzes the message acquisition command and executes the message acquisition command, and a DMFH command is generated according to the execution result and is sent to agent _ send _ topic;
still further, the end management module further comprises a heartbeat module, and when the information processing module works, the heartbeat module starts heartbeat counting and sends generated heartbeat information to the agent _ common _ topic.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (8)
1. An application management method based on IMS is characterized in that the method comprises the following specific steps:
s1 provides message transmission channel by IMS and buffers the message;
s2 executing end management operation and processing commands sent by the cloud end;
s3 receives and processes the register information message of the receiving end, and sends the installation and management command to the end.
2. The method as claimed in claim 1, wherein the step of S2 executing the end management operation and processing the command sent by the cloud end comprises:
s201, searching whether an end id file exists;
s202, when the end id file is not detected, the generated uuid is used as the end id, end node information is obtained and assembled into json format information, and the json format information is sent to agent _ common _ topic;
s212, when the terminal id file is detected, acquiring the message circularly from the agent _ receive _ topic, and processing according to the message type.
3. The method as claimed in claim 2, wherein when the end id file is detected in the S212, the step of obtaining the message circularly from the agent _ receive _ topic and processing the message according to the message type includes:
s2121, when the message type is DZCH, completing registration and writing the end id into a file;
s2122, when the message type is DWF, after the received message is analyzed, writing the file into a specified position, generating a DWFH message according to the execution condition, and sending the DWFH message to agent _ send _ topic;
s2123, when the message type is DWH, converting the file read at the specified position into a byte stream and sending the byte stream to agent _ send _ topic;
s2124, when the message type is DWF, the message acquisition command is analyzed and executed, and the DMFH command is generated according to the execution result and sent to agent _ send _ topic.
4. The method as claimed in claim 3, wherein the step S212 is performed while initiating a heartbeat count to transmit the generated heartbeat information to agent _ common _ topic.
5. An application management system based on IMS is characterized in that the system specifically comprises a message module, an end management module and a cloud management module:
a message module: providing a message transmission channel by using an IMS (IP multimedia subsystem) and caching messages;
end management module: executing end management operation and processing commands sent by a cloud end;
the cloud management module: after receiving and processing the registration information message of the receiving end, the receiving end sends an installation and management command to the end.
6. The system of claim 5, wherein the peer management module specifically comprises a peer detection module, an information assembly module, and an information processing module:
an end detection module: searching whether an end id file exists;
an information assembly module: when the end id file is not detected, the generated uuid is used as the end id, end node information is obtained and assembled into json format information, and the json format information is sent to agent _ common _ topic;
an information processing module: and when the terminal id file is detected, acquiring the message circularly from the agent _ receive _ topic, and processing according to the message type.
7. The system as claimed in claim 6, wherein the information processing module specifically includes an a processing module, a B processing module, a C processing module, and a D processing module:
the A processing module: when the message type is DZCH, completing registration and writing the terminal id into a file;
and a B processing module: when the message type is DWF, after the received message is analyzed, writing the file into a specified position, generating a DWFH message according to the execution condition, and sending the DWFH message to agent _ send _ topoic;
and a C processing module: when the message type is DWH, converting the file read at the specified position into a byte stream and sending the byte stream to agent _ send _ topic;
and a D processing module: and when the message type is DWF, analyzing the message acquisition command, executing, generating a DMFH command according to an execution result, and sending the DMFH command to the agent _ send _ topic.
8. The system as claimed in claim 7, wherein the end management module further comprises a heartbeat module, and the heartbeat module starts a heartbeat count to send generated heartbeat information to the agent _ common _ topic while the information processing module is operating.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011137964.2A CN112291322A (en) | 2020-10-22 | 2020-10-22 | Application management method and system based on IMS |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011137964.2A CN112291322A (en) | 2020-10-22 | 2020-10-22 | Application management method and system based on IMS |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112291322A true CN112291322A (en) | 2021-01-29 |
Family
ID=74423631
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011137964.2A Pending CN112291322A (en) | 2020-10-22 | 2020-10-22 | Application management method and system based on IMS |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112291322A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113132477A (en) * | 2021-04-16 | 2021-07-16 | 易斌 | Real-time transmission interaction method and system for browser terminal and equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103051521A (en) * | 2013-01-09 | 2013-04-17 | 浪潮电子信息产业股份有限公司 | Retransmitting method of message in cloud environment |
| CN104156216A (en) * | 2014-08-14 | 2014-11-19 | 浪潮(北京)电子信息产业有限公司 | Heterogeneous storage management system and method oriented to cloud computing |
| CN106126349A (en) * | 2016-06-14 | 2016-11-16 | 浪潮电子信息产业股份有限公司 | A kind of remote invocation method, message-oriented middleware cluster and system |
| US20180191550A1 (en) * | 2016-12-29 | 2018-07-05 | Kodiak Networks Inc. | System and Method for Push-to-Talk (PTT) In Mobile Edge Computing (MEC) |
| US20180300124A1 (en) * | 2015-08-27 | 2018-10-18 | FogHorn Systems, Inc. | Edge Computing Platform |
| CN111416867A (en) * | 2020-03-25 | 2020-07-14 | 上海商米科技集团股份有限公司 | Method for processing messages between different devices, server and computer storage medium |
-
2020
- 2020-10-22 CN CN202011137964.2A patent/CN112291322A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103051521A (en) * | 2013-01-09 | 2013-04-17 | 浪潮电子信息产业股份有限公司 | Retransmitting method of message in cloud environment |
| CN104156216A (en) * | 2014-08-14 | 2014-11-19 | 浪潮(北京)电子信息产业有限公司 | Heterogeneous storage management system and method oriented to cloud computing |
| US20180300124A1 (en) * | 2015-08-27 | 2018-10-18 | FogHorn Systems, Inc. | Edge Computing Platform |
| CN106126349A (en) * | 2016-06-14 | 2016-11-16 | 浪潮电子信息产业股份有限公司 | A kind of remote invocation method, message-oriented middleware cluster and system |
| US20180191550A1 (en) * | 2016-12-29 | 2018-07-05 | Kodiak Networks Inc. | System and Method for Push-to-Talk (PTT) In Mobile Edge Computing (MEC) |
| CN111416867A (en) * | 2020-03-25 | 2020-07-14 | 上海商米科技集团股份有限公司 | Method for processing messages between different devices, server and computer storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113132477A (en) * | 2021-04-16 | 2021-07-16 | 易斌 | Real-time transmission interaction method and system for browser terminal and equipment |
| CN113132477B (en) * | 2021-04-16 | 2023-09-19 | 成都易明半导体有限公司 | Real-time transmission interaction method and system for browser terminal and equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Zheng et al. | Distributed QoS evaluation for real-world web services | |
| US20100115041A1 (en) | Creating a message readable by a plurality of heterogeneous recipients | |
| WO2019029320A1 (en) | Configuration management method, apparatus and device | |
| CN106936791B (en) | Method and device for intercepting malicious website access | |
| WO2010072081A1 (en) | Method and system for realizing massive terminals access of a streaming media server | |
| TW202038581A (en) | Management client, and device monitoring system and method | |
| KR20110076954A (en) | Optimized polling in low resource devices | |
| CN108712457A (en) | Back-end server dynamic load method of adjustment and device based on Nginx reverse proxys | |
| CN110943911A (en) | High-efficiency data transmission method for Internet of things based on protobuf | |
| CN110868349B (en) | Distributed high-concurrency data acquisition and processing method and system in Internet of things environment | |
| CN110677432A (en) | Network protocol internal proxy forwarding method, device, medium and terminal equipment | |
| CN112532673B (en) | Message sending method and device, computer readable storage medium and electronic equipment | |
| CN113360301B (en) | Message transmission system and method | |
| CN106789413B (en) | Method and device for detecting proxy internet surfing | |
| CN114221995B (en) | Service calling method and device and electronic equipment | |
| CN114124929A (en) | Cross-network data processing method and device | |
| WO2024060408A1 (en) | Network attack detection method and apparatus, device and storage medium | |
| CN112291322A (en) | Application management method and system based on IMS | |
| CN113760562A (en) | Link tracking method, device, system, server and storage medium | |
| CN109918215B (en) | Process communication method, system, terminal and storage medium | |
| CN115756771B (en) | Micro-servitization front-end system, workflow scheduling method and device | |
| US8200845B2 (en) | Queuing of invocations for mobile web services | |
| CN114785854A (en) | Service request processing method, device, equipment, storage medium and product | |
| JP2019040579A (en) | Message push system, client device and message push method therefor | |
| CN112152915A (en) | Message forwarding network system and message forwarding method |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210129 |