CN104980520B - Notification message receiving method, device and system - Google Patents
Notification message receiving method, device and system Download PDFInfo
- Publication number
- CN104980520B CN104980520B CN201510374140.XA CN201510374140A CN104980520B CN 104980520 B CN104980520 B CN 104980520B CN 201510374140 A CN201510374140 A CN 201510374140A CN 104980520 B CN104980520 B CN 104980520B
- Authority
- CN
- China
- Prior art keywords
- client
- frequency parameter
- app
- received
- receiving frequency
- 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.)
- Active
Links
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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
- H04L67/5651—Reducing the amount or size of exchanged application data
-
- 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/14—Session management
- H04L67/141—Setup of application sessions
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method, a device and a system for receiving a notification message. The method comprises the following steps: the method comprises the steps that an AJ client routing module receives a filtering condition registered by a client APP and obtains a receiving frequency parameter in the filtering condition, wherein the receiving frequency parameter carries the maximum number of notification messages which can be received by the client APP in a detection period; and the AJ client routing module carries out periodic detection and judges whether to send the received notification message to the client APP according to the filtering condition and the receiving frequency parameter. By means of the technical scheme, the resources of the equipment where the client APP is located can be greatly saved.
Description
Technical Field
The invention relates to the field of Internet of things, in particular to a notification message receiving method, device and system.
Background
AllJoyn (AJ for short) is a collaborative open source software framework, programmers can write applications for searching nearby devices conveniently, and the system can be connected without a cloud environment regardless of the brand, the category and the system of the other party. The AllJoyn framework is very flexible, enabling the Internet of things to achieve vision. The AllJoyn adopts a "distributed software bus", which is a "medium" for the AllJoyn Application to communicate through an Application Programming Interface (API), and the Application may be firmware of a microprocessor, an Application of a mobile device (APP), or an Application program on a Personal Computer (PC). In AllJoyn, the application that issues the API is a server (service) and the consuming is a client (client), and the application can be both a service and a client, making AllJoyn a point-to-point (P2P) system. In addition, the communicated messages directly map the API of the high-level programming language implementation. Bus formation uses a self-organizing approach, based on application/service discovery, abstracting the discovery mechanism for a particular connection. The AllJoyn adopts a protocol independent of the network, and the network protocol is based on the extension of the D-Bus protocol and can run in Wi-Fi, Wi-Fi Direct, Ethernet, PLC and Bluetooth. All AllJoyn applications are clients of a Router (Router). The Client Library is an API of an AllJoyn Software Development Kit (SDK) facing developers, and has two implementations: a Standard Client (SC) targeting applications running on a High Level Operating System (HLOS), and a Thin Client (TC) targeting applications running on an embedded device.
The AllJoyn application exposes a function (object) to the outside through an API realized by the object, most applications only expose one object, hierarchical objects can be supported according to the needs of an application model, the object realizes one or more interfaces (interfaces), and the API can be discovered after service discovery and connection establishment. The interface is composed of members, and the three types of members are: method (Method), Signal (Signal), Property (Property).
Classification on Property (Property): generally, different objects represent different entities (devices), and Property in an interface generally represents the state of an entity visible to the outside. Such as the temperature of the water heater, etc. The observer (client app) as an object can thus know the state of the entity through Property. The Property can be classified into three categories according to the marking value (annotation value) of org, freedesktop, dbus, Property, emitschange signal:
when noted as True, the updating Property org, free desktop, dbus, properties, Property changed signal is sent with the new value of Property when the Property changes.
When the label value is False: a non-cacheable Property org. freedesk. dbus. properties. Property changed signal is not sent when Property changes.
When the label value is invalidates: when the Property changes, an invalid Property org, freedesktop, dbus, properties, Property changed signal is sent, not carrying the new value of the Property.
The messages are all broadcast transmission in a time domain (session), that is, apps in the same session may receive the messages. The App needs to select whether to receive the message, specifically:
how the client APP accepts the message: as shown in FIG. 1, a filter condition is registered in router by the addmatch method. When the router receives the message with the changed Property, it will determine whether it needs to send the request message for the APP according to the filtering condition. The specific messages are as follows: freedesktop.dbus.addmatch (bus _ proxy, "type ═ signal ', name ═ org.example. App ', path _ namespace ═ org/example/App ' ″), wherein the parameters of addmatch include the following: type (message type), sender (Bus name or connection unique name), interface (interface name), number (method name or signal name), path (object path), path namespace (object path namespace), destination.
After receiving the signal, the AJ client routing module (consumer AJ Router) determines whether a new value of Property needs to be sent to the client APP according to the above conditions (provided that the client APP registers a filtering condition corresponding to the Property with the Router through an addmatch method).
In the prior art, when the frequency of the Property change of the Provider (Provider) APP is particularly high and the flag value of the org.freedesktop.dbus.property.emitschange signal corresponding to the Property is set to tune or invalidates, that is, the corresponding org.freedesktop.dbus.properties.property change signal needs to be generated, the client APP subscribing to the signal may need to analyze the signal at the same frequency, which may seriously consume the resources of the device where the client APP is located, and cause the problems of overload, downtime, runaway and the like of the device.
Disclosure of Invention
In view of the problem in the prior art that provider APP sends request messages at high frequency, resulting in overload of processing of client APP, the present invention is proposed to provide a notification message receiving method, apparatus and system that overcome or at least partially solve the above problems.
The invention provides a method for receiving a notification message, which comprises the following steps: the method comprises the steps that an AJ client routing module receives a filtering condition registered by a client APP and obtains a receiving frequency parameter in the filtering condition, wherein the receiving frequency parameter carries the maximum number of notification messages which can be received by the client APP in a detection period; and the AJ client routing module carries out periodic detection and judges whether to send the received notification message to the client APP according to the filtering condition and the receiving frequency parameter.
Preferably, before the AJ client routing module receives the filter condition registered by the client APP, the application program in the client APP determines the maximum number of notification messages that can be received in unit time according to the performance and/or configuration of the device; and when the application program registers the signal processing function to the AJ core module in the client APP, sending the receiving frequency parameter to the AJ core module.
Preferably, the receiving, by the AJ client routing module, the filter condition registered by the client APP, and the obtaining of the receiving frequency parameter in the filter condition specifically includes: and the AJ client routing module receives the filter condition registered by the AJ core module and acquires a receiving frequency parameter in the filter condition.
Preferably, the step of periodically detecting by the AJ client routing module, and determining whether to send the received notification message to the client APP according to the filtering condition and the receiving frequency parameter specifically includes: and the AJ client routing module carries out periodic detection, if the received notification messages are judged to accord with the filtering conditions and the receiving frequency parameters, the notification messages are sent to the client APP, and if not, the notification messages are forbidden to be sent to the client APP.
Preferably, the step of determining that the received notification message conforms to the receiving frequency parameter specifically includes: the number of notification messages received during the detection period is calculated, and if the notification messages received during the detection period do not exceed the maximum number of reception frequency parameters, it is determined that the notification messages conform to the reception frequency parameters.
The invention also provides a notification message receiving device, which is arranged in the AJ client routing module and comprises: the device comprises an acquisition module, a detection module and a processing module, wherein the acquisition module is used for receiving a filter condition registered by a client application APP and acquiring a receiving frequency parameter in the filter condition, and the receiving frequency parameter carries the maximum number of notification messages which can be received by the client APP in a detection period; and the detection module is used for carrying out periodic detection and judging whether to send the received notification message to the client APP according to the filtering condition and the receiving frequency parameter.
Preferably, the obtaining module is specifically configured to: and receiving a filtering condition registered by an AJ core module in the client APP, and acquiring a receiving frequency parameter in the filtering condition.
Preferably, the detection module is specifically configured to: and carrying out periodic detection, if the received notification messages are judged to accord with the filtering conditions and the receiving frequency parameters, sending the notification messages to the client APP, and if not, forbidding sending the notification messages to the client APP.
Preferably, the detection module is specifically configured to: the number of notification messages received during the detection period is calculated, and if the notification messages received during the detection period do not exceed the maximum number of reception frequency parameters, it is determined that the notification messages conform to the reception frequency parameters.
The present invention also provides a notification message receiving system, including the above notification message receiving apparatus, further including: and the client application APP is used for determining the maximum number of the notification messages capable of being received in unit time according to the performance and/or configuration of the equipment, carrying the maximum number in the receiving frequency parameters, and carrying the receiving frequency parameters in the filtering conditions when the filtering conditions are registered to the AJ client routing module.
The invention has the following beneficial effects:
whether the received notification message is sent to the client side APP is judged according to the receiving frequency parameter, the problem that the client side APP is overloaded in processing due to the fact that the provider APP sends the request message at high frequency in the prior art is solved, and resources of equipment where the client side APP is located can be greatly saved.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a signaling flow diagram of a client APP receiving a notification message in the prior art;
fig. 2 is a flowchart of a notification message receiving method according to an embodiment of the present invention;
fig. 3 is a signaling flowchart of detailed processing of a notification message receiving method according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a notification message receiving apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a notification message receiving system according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
In order to solve the problem that the provider APP sends a request message at a high frequency to cause overload of processing of the client APP in the prior art, the present invention provides a notification message receiving method, apparatus and system. It should be understood that the specific embodiments described herein are merely illustrative of the invention and do not limit the invention.
Method embodiment
According to an embodiment of the present invention, there is provided a notification message receiving method, fig. 2 is a flowchart of the notification message receiving method according to the embodiment of the present invention, and as shown in fig. 2, the notification message receiving method according to the embodiment of the present invention includes the following processes:
step 201, an AJ client routing module receives a filter condition registered by a client APP, and acquires a receiving frequency parameter in the filter condition, wherein the receiving frequency parameter carries the maximum number of notification messages that can be received by the client APP in a detection period;
specifically, in the embodiment of the present invention, before the AJ client routing module receives the filter condition registered by the client APP, the application program in the client APP determines the maximum number of notification messages that can be received in unit time according to the performance and/or configuration of the device; and when the application program registers the signal processing function to the AJ core module in the client APP, sending the receiving frequency parameter to the AJ core module.
In step 201, the AJ client routing module receives the filtering condition registered by the AJ core module, and obtains a receiving frequency parameter in the filtering condition.
Step 202, the AJ client routing module performs periodic detection, and determines whether to send the received notification message to the client APP according to the filtering condition and the receiving frequency parameter.
Step 202 specifically includes: and the AJ client routing module carries out periodic detection, if the received notification messages are judged to accord with the filtering conditions and the receiving frequency parameters, the notification messages are sent to the client APP, and if not, the notification messages are forbidden to be sent to the client APP.
Wherein, the step of judging that the received notification message conforms to the receiving frequency parameter specifically comprises: the number of notification messages received during the detection period is calculated, and if the notification messages received during the detection period do not exceed the maximum number of reception frequency parameters, it is determined that the notification messages conform to the reception frequency parameters.
The above technical solutions of the embodiments of the present invention are described in detail below with reference to the accompanying drawings.
Fig. 3 is a signaling flowchart of detailed processing of a notification message receiving method according to an embodiment of the present invention, and as shown in fig. 3, the method specifically includes the following processing:
step 1, the client APP determines the frequency (the number of received messages in unit time) for receiving the notification message according to the parameters of the performance, configuration and the like of the device.
And 2, when the APP registers the signal processing function to the AJ core module, increasing a frequentresholdvalue parameter (the receiving frequency parameter). This parameter determines the number of messages the APP wishes to receive per unit of time.
Step 3, the AJ core module registers the filter condition with the AJ client routing module through the addmatch () method. The above filtering condition contains a frequethreshold parameter.
Step 4, the AJ client routing module starts cycle detection, after receiving the signal message, except for judging the conventional filtering condition (information of message type, sender, destination, object path, etc.), the number of the messages received in the detection cycle needs to be calculated additionally, if the messages received in the cycle do not exceed the threshold value, the messages are sent to the AJ core module, and a message processing function is called to process the messages. (callback function, client APP received the message). If the message received within the period exceeds the frequentreshold value, the message is discarded.
And 5, after the period is finished, continuing to monitor the next period.
In summary, with the aid of the technical solution of the embodiments of the present invention, by determining whether to send the received notification message to the client APP according to the receiving frequency parameter, a problem that the client APP is overloaded when the provider APP sends the request message at a high frequency in the prior art is solved, and resources of the device where the client APP is located can be greatly saved.
Device embodiment
According to an embodiment of the present invention, there is provided a notification message receiving apparatus, which is disposed in an AJ client routing module, and fig. 4 is a schematic structural diagram of the notification message receiving apparatus according to an embodiment of the present invention, as shown in fig. 4, the notification message receiving apparatus according to an embodiment of the present invention includes: the acquisition module 40 and the detection module 42 will be described in detail below with respect to the respective modules according to the embodiments of the present invention.
An obtaining module 40, configured to receive a filtering condition registered by a client APP, and obtain a receiving frequency parameter in the filtering condition, where the receiving frequency parameter carries a maximum number of notification messages that can be received by the client APP in a detection period; the obtaining module 40 is specifically configured to: and receiving a filtering condition registered by an AJ core module in the client APP, and acquiring a receiving frequency parameter in the filtering condition.
And the detection module 42 is configured to perform periodic detection, and determine whether to send the received notification message to the client APP according to the filtering condition and the receiving frequency parameter.
The detection module 42 is specifically configured to: and carrying out periodic detection, if the received notification messages are judged to accord with the filtering conditions and the receiving frequency parameters, sending the notification messages to the client APP, and if not, forbidding sending the notification messages to the client APP.
The detection module 42 calculates the number of notification messages received during the detection period and determines that the notification messages conform to the reception frequency parameter if the notification messages received during the detection period do not exceed the maximum number of reception frequency parameters.
The detailed processing of each module in the embodiment of the present invention may be processed with reference to the corresponding description in the method embodiment, and is not described herein again.
System embodiment
According to an embodiment of the present invention, a notification message receiving system is provided, and fig. 5 is a schematic structural diagram of the notification message receiving system according to the embodiment of the present invention, as shown in fig. 5, including the notification message receiving apparatus 50, further including: the client APP 52 is configured to determine the maximum number of notification messages that can be received in a unit time according to the performance and/or configuration of the device, carry the maximum number in the receiving frequency parameter, and carry the receiving frequency parameter in the filtering condition when registering the filtering condition with the AJ client routing module.
In conclusion, whether the received notification message is sent to the client side APP is judged according to the receiving frequency parameter, the problem that the client side APP is overloaded in processing due to the fact that the provider APP sends the request message at high frequency in the prior art is solved, and resources of equipment where the client side APP is located can be greatly saved.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the client in an embodiment may be adaptively changed and provided in one or more clients different from the embodiment. The modules of the embodiments may be combined into one module and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or client so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in a client loaded with a ranking website according to embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
Claims (6)
1. A notification message receiving method, comprising:
the method comprises the steps that an AJ client routing module receives a filtering condition registered by a client APP and obtains a receiving frequency parameter in the filtering condition, wherein the receiving frequency parameter carries the maximum number of notification messages which can be received by the client APP in a detection period;
the AJ client routing module carries out periodic detection and judges whether to send the received notification message to the client APP or not according to the filtering condition and the receiving frequency parameter;
the AJ client routing module performs periodic detection, and determining whether to send the received notification message to the client APP according to the filtering condition and the receiving frequency parameter specifically includes:
the AJ client routing module carries out periodic detection, if the received notification messages are judged to accord with the filtering conditions and the receiving frequency parameters, the notification messages are sent to the client APP, and if not, the notification messages are forbidden to be sent to the client APP;
the step of judging that the received notification message conforms to the receiving frequency parameter specifically includes:
calculating the number of received notification messages within the detection period, and determining that the notification messages conform to the reception frequency parameter if the notification messages received within the detection period do not exceed the maximum number in the reception frequency parameter.
2. The method of claim 1, wherein prior to the AJ client routing module receiving the filter criteria for client APP registration, the method further comprises:
the maximum number of notification messages which can be received in unit time is determined by an application program in the client APP according to the performance and/or configuration of the equipment;
and when the application program registers a signal processing function to an AJ core module in the client APP, sending the receiving frequency parameter to the AJ core module.
3. The method of claim 1, wherein the AJ client routing module receives a filter condition registered by the client APP, and the obtaining of the receiving frequency parameter in the filter condition specifically includes:
and the AJ client routing module receives the filter condition registered by the AJ core module and acquires a receiving frequency parameter in the filter condition.
4. A notification message receiving apparatus, provided in an AJ client routing module, the apparatus specifically includes:
an obtaining module, configured to receive a filtering condition registered by a client APP, and obtain a receiving frequency parameter in the filtering condition, where the receiving frequency parameter carries a maximum number of notification messages that can be received by the client APP in a detection period;
the detection module is used for carrying out periodic detection and judging whether to send the received notification message to the client APP or not according to the filtering condition and the receiving frequency parameter;
the detection module is specifically configured to: carrying out periodic detection, if the received notification message is judged to accord with the filtering condition and the receiving frequency parameter, sending the notification message to the client side APP, otherwise, forbidding sending the notification message to the client side APP;
the detection module is specifically configured to: calculating the number of received notification messages within the detection period, and determining that the notification messages conform to the reception frequency parameter if the notification messages received within the detection period do not exceed the maximum number in the reception frequency parameter.
5. The apparatus of claim 4, wherein the acquisition module is specifically configured to: and receiving a filtering condition registered by an AJ core module in the client APP, and acquiring a receiving frequency parameter in the filtering condition.
6. A notification message reception system comprising the notification message reception apparatus according to claim 4 or 5, further comprising:
the client application APP is used for determining the maximum number of notification messages capable of being received in unit time according to the performance and/or configuration of the equipment, carrying the maximum number in the receiving frequency parameters, and carrying the receiving frequency parameters in the filtering conditions when the filtering conditions are registered to the AJ client routing module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510374140.XA CN104980520B (en) | 2015-06-30 | 2015-06-30 | Notification message receiving method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510374140.XA CN104980520B (en) | 2015-06-30 | 2015-06-30 | Notification message receiving method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104980520A CN104980520A (en) | 2015-10-14 |
| CN104980520B true CN104980520B (en) | 2021-08-31 |
Family
ID=54276613
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510374140.XA Active CN104980520B (en) | 2015-06-30 | 2015-06-30 | Notification message receiving method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104980520B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105956038A (en) * | 2016-04-26 | 2016-09-21 | 宇龙计算机通信科技(深圳)有限公司 | Notification message management method and apparatus as well as terminal |
| CN106507294B (en) * | 2016-09-23 | 2019-11-08 | 海尔优家智能科技（北京）有限公司 | A kind of thin-client control method and control device based on AllJoyn |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1448860A (en) * | 2002-03-29 | 2003-10-15 | 欧姆龙株式会社 | Information processing device and method |
| CN104038511A (en) * | 2013-03-04 | 2014-09-10 | 联想(北京)有限公司 | Resource management method and apparatus |
| CN104137518A (en) * | 2012-02-21 | 2014-11-05 | 高通股份有限公司 | Internet protocol connectivity over a service-oriented architecture bus |
| WO2015034784A1 (en) * | 2013-09-09 | 2015-03-12 | Qualcomm Incorporated | Increasing power savings through intelligent synchronizing of data |
| CN104518890A (en) * | 2014-12-30 | 2015-04-15 | 北京海尔广科数字技术有限公司 | Network service processing method, information broadcasting and control method and device |
| CN104683193A (en) * | 2015-02-02 | 2015-06-03 | 惠州Tcl移动通信有限公司 | Application method for communication terminal and intelligent family system |
-
2015
- 2015-06-30 CN CN201510374140.XA patent/CN104980520B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1448860A (en) * | 2002-03-29 | 2003-10-15 | 欧姆龙株式会社 | Information processing device and method |
| CN104137518A (en) * | 2012-02-21 | 2014-11-05 | 高通股份有限公司 | Internet protocol connectivity over a service-oriented architecture bus |
| CN104038511A (en) * | 2013-03-04 | 2014-09-10 | 联想(北京)有限公司 | Resource management method and apparatus |
| WO2015034784A1 (en) * | 2013-09-09 | 2015-03-12 | Qualcomm Incorporated | Increasing power savings through intelligent synchronizing of data |
| CN104518890A (en) * | 2014-12-30 | 2015-04-15 | 北京海尔广科数字技术有限公司 | Network service processing method, information broadcasting and control method and device |
| CN104683193A (en) * | 2015-02-02 | 2015-06-03 | 惠州Tcl移动通信有限公司 | Application method for communication terminal and intelligent family system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104980520A (en) | 2015-10-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11997160B2 (en) | Lightweight IoT information model | |
| JP6892445B2 (en) | Cross-resource subscription for M2M service tier | |
| CN108712286B (en) | Method and device for determining network topology structure and storage medium | |
| CN106797392B (en) | Publication and discovery of M2M-IOT services | |
| CN104038908B (en) | Push message sending method and device | |
| CN111930700A (en) | Distributed log processing method, server, system and computing equipment | |
| CN112805981B (en) | Framework for dynamic proxy and management of topics and data for a service layer | |
| WO2019042186A1 (en) | Network management method and related device | |
| JP6676080B2 (en) | Method and system for installing an application version via near field communication | |
| WO2018103405A1 (en) | Method for identifying access point and hotspot, and related product | |
| KR20180019590A (en) | Methods and apparatuses for analyzing and grouping service layer subscriptions and notifications for enhanced efficiency | |
| US20160183064A1 (en) | Contextually aware dynamic group formation | |
| CN109039803A (en) | A kind of method, system and the computer equipment of processing readjustment notification message | |
| CN104980520B (en) | Notification message receiving method, device and system | |
| Silva et al. | Neighborhood-aware mobile hub: An edge gateway with leader election mechanism for internet of mobile things | |
| CN110380902B (en) | Topological relation generation method and device, electronic equipment and storage medium | |
| CN106790323B (en) | Resource discovery method and device | |
| KR101940802B1 (en) | System for calculating the number of the local triangular using the terminal resources and method thereof | |
| EP3300335B1 (en) | Device and method for data packet processing | |
| CN105072147B (en) | Processing method and device for receiving notification message | |
| US9275142B2 (en) | Method and apparatus for multi-browser web-based applications | |
| JP2014026315A (en) | Information processing device, data provision method, and data provision program | |
| CN115243291A (en) | Data processing method, device, equipment and computer storage medium | |
| CN118118883A (en) | Communication method, communication device, electronic equipment and computer readable medium | |
| CN110874299A (en) | Storage monitoring method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |