CN104243611B - A kind of messenger service middleware system based on distribution thought - Google Patents

A kind of messenger service middleware system based on distribution thought Download PDF

Info

Publication number
CN104243611B
CN104243611B CN201410516976.4A CN201410516976A CN104243611B CN 104243611 B CN104243611 B CN 104243611B CN 201410516976 A CN201410516976 A CN 201410516976A CN 104243611 B CN104243611 B CN 104243611B
Authority
CN
China
Prior art keywords
service
message
request
messenger service
module
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
Application number
CN201410516976.4A
Other languages
Chinese (zh)
Other versions
CN104243611A (en
Inventor
马骏
邵兵
乔富龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inspur Software Co Ltd
Original Assignee
Inspur Software Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Inspur Software Co Ltd filed Critical Inspur Software Co Ltd
Priority to CN201410516976.4A priority Critical patent/CN104243611B/en
Publication of CN104243611A publication Critical patent/CN104243611A/en
Application granted granted Critical
Publication of CN104243611B publication Critical patent/CN104243611B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

The present invention provides a kind of messenger service middleware system based on distribution thought, distribution, forwarding service for various types of messages, it is intended to which reduction service end receives the pressure of message request task and improves the efficiency of the different request tasks of the multiple requesting parties for the treatment of on the basis of meeting application service.System includes:(1) messenger service subscribing module;(2) messenger service distribution module;(3) messenger service release module.Can solve the problems, such as that subscriber frequently searches the provider address of different services using the system or even can not find service provider address;The number of times that service end receives request task can be effectively reduced, reduces the probability of repeated data issue, it is effective to improve data publication efficiency;Can solve the problem that the bottleneck problem of service end high-volume request task treatment.

Description

A kind of messenger service middleware system based on distribution thought
Technical field
The present invention relates to communication technical field, in various types of messages service, when direction the opposing party's request data or service When, there is requirement higher for task treatment effeciency and data publication efficiency, the invention is intended to reduction service end and receives identical The probability of request task and the burden of reduction treatment same request, improve the treatment effeciency of request task and solve high-volume Bottleneck problem of the request task treatment in quantity and efficiency.In specifically a kind of messenger service based on distribution thought Between part system.
Background technology
In various types of messages service, efficiency, the efficiency of data publication and high-volume request task that request task is processed Reliable and stable treatment will be higher requirement, and the various resources such as the CPU of computer, internal memory and network bandwidth resources are all Limited, to meet the demand of high-volume request task application, messenger service must efficiently, stably.
Current various types of messages service is all carried out by the way of request bearing data or service provider directly transmit request, This kind of processing method causes service side frequently to receive same request task and frequently send identical data or provide what is repeated Service, under the limited service provision capacity of service side, causes service to provide the reduction of efficiency.And, when service provider exists After the collapse of a certain moment is restarted, current message service processing method cannot cause data or service requester obtain in time data or Service, and after requesting party must resubmit request task, data or service could be reacquired, increased requesting party and clothes The burden of business provider.
When requesting party needs service provider periodically to provide service, current various types of messages service processing method requirement please The side of asking periodically sends service request to service provider, causes offered load with requesting party's quantity and RQ cycle into several What multiple increases, and current various types of messages service processing method inevitably produces the treatment of batch request task and service to carry For the bottleneck problem of efficiency, therefore, unnecessary request task is reduced, it is beneficial to the lifting of integrity service efficiency.
The content of the invention
It is an object of the invention to provide a kind of messenger service middleware system.
The purpose of the present invention realizes that system includes 1) messenger service subscribing module in the following manner;2) messenger service Distribution module;3) messenger service release module, wherein:
1) messenger service subscribing module
Messenger service subscribing module, it is main to realize subscribing to the registration of request, send and subscribing to the correct return of data, disappear Breath service subscription module data flows to and is:After request task is subscribed in instantiation, messenger service subscribing module is by service request task Registered, and the solicited message with service codes and filter condition is sent to messenger service distribution module;Message After service subscription module receives return data, according to service codes and log-on message, return data are returned to and accordingly please The person of asking, the types of functionality of messenger service subscribing module is as follows:
(1) CMsgSubscribeListMgr classes:Initialization running environment simultaneously starts receiving thread, manages log-on message, And distribute return data;
(2) CMsgSubscribe classes:Message subscribing interface is defined, its subclass needs the method for realizing such definition;
(3) NewClass classes and NewClass2 classes:Message subscribing example class, inherits CMsgSubscribe classes, according to tool Body business demand realizes the interface of CMsgSubscribe classes definition;
Messenger service middleware system, in the form of service codes or referred to as message number distinguish different services, service Side to each service provide a specific service codes, subscriber to provide service codes in the way of obtain service, service codes root Carried out according to specific service needed self-defined, messenger service subscribing module is processed by the way of filter condition needs ordering for specially treated Read request;
Messenger service subscribing module supports the business that two subscribers subscribe to mutually;
2) messenger service distribution module
Messenger service distribution module, is the main body module of messenger service middleware system, and the module needs the function of realizing Including:Service profile information, message parsing, message distribution are obtained, including is subscribed to the forwarding of request and is subscribed to forwarding, the phase of data Register and unsubscribe with request treatment, special subscription treatment or filtration treatment and subscription information;
Messenger service distribution module implements flow:
(1) initialize running environment, obtain service profile information, including COS, service provider address, use Communication mode and the automatic detection cycle of service, in configuration information record to service forward table;
(2) messenger service distribution module receives message;
(3) messenger service distribution module is parsed to message, obtains type of message and messenger service code;
(4) messenger service distribution module is processed accordingly according to type of message and service codes, basic messae type bag Include:Request message, response message, message and probe message are unsubscribed, type of message is extended according to service needed;Such as The type of message that receives of fruit is that do not have the request of the type or required parameter not phase in request message, and register list Together, then corresponding service provider is forwarded messages to according to service forward table, and the subscription information is write into register list;Separately Outward, if having the request of the type, but response is not received more than certain time threshold, messenger service distribution module can be retransmitted The subscription is asked, if response message, then message is returned into corresponding subscriber according to service codes and register list;Number According to it is return when filter condition in register list select return mode, return mode is self-defined;If unsubscribe disappearing Breath, then delete the subscriber from register list, and when register list is space-time, messenger service distribution module is by the type Messenger service provider sends and unsubscribes message;If probe message, then service provider is pointed out normally to run, and according to Business demand carries out relevant treatment;
Messenger service distribution module includes service detection mechanism, when the request of certain type does not receive sound more than certain threshold value At once, messenger service distribution module will send the subscription request of the type from trend service end, and timeout threshold is according to different clothes Business demand is independently arranged;
Messenger service distribution module types of functionality is as follows:
(1) CMsgDispatchMgr classes:Initialization running environment, there is provided the total interface of service;
(2) CMsgParser classes:Message is parsed, and obtains messenger service code necessary information
(3) SMsgHead classes:Message analytic structure is defined, according to operation expanding;
(4) CMsgSubscribeMgr classes:Subscribe to request registration and forwarding, response message distribution and other kinds type disappear Breath treatment;
(5) CSubscribe classes:Define subscriber's log-on message form, including subscriber address, the necessary letter of filtration parameter Breath;
(6) CMsgReqSendFactory classes:Subscribe to the management of solicited message sending method;
(7) CMsgSubResponseHandler classes:Solicited message transmission interface is subscribed in definition, is easy to self-defined subscription to ask Seek message mode;
(8) CMsgSendHandler0 classes and CMsgSendHandler1 classes:The subscription solicited message sender of instantiation Formula;
(9) CMsgReqSendFactory classes:The return mode of response data is managed;
(10) CMsgSendHandle classes:The return mode interface of subscription response message, is easy to self-defined response message return Mode;
(11) CDetailMsgHandler0 classes and CDetailMsgHandler1 classes:The return side of response data of instantiation Formula class;
3) messenger service release module
Messenger service release module is mainly realized subscribing to the reception of request, parsing and subscribes to the return of data, and message takes Business release module workflow is as follows:
(1) messenger service release module receives message;
(2) messenger service release module is parsed to message, obtains the service codes and type of message of the request;
(3) if subscription request message, messenger service release module please according to the subscription that the service codes search this service Register list is sought, if there is the request of the type, is not processed, otherwise by subscription request registration to ordering Read request register list in, and by subscribe to request be supplied to service provider;
(4) if receiving probe message, register list is asked according to the subscription that messenger service code searches this service, such as There is the request of the type in fruit, then return to probe response message;Otherwise, probe message is parsed, is obtained and is subscribed to solicited message, And in the subscription request register list that subscription request registration is serviced to this, and it is supplied to service to provide subscription request Side;
The class function of messenger service release module is:CPubSubServer classes:Realize message sink, parsing and respond Data are return.
Described system, sets message subscribing interface, is sent according to regulation form and subscribes to request, subscribes to request form regulation It is as follows:
Heading+service codes+filtration parameter+message mark
Heading is protocol massages head, and length is specified according to the agreement for using;Service codes are according to practical business demand It is defined, length is arranged as required to;Filtration parameter is used to distinguish the subscription request that same type asks different required parameters, its Form carries out self-defined according to practical business;Message marks the message needed for for distinguishing various types of messages type and business to mark.
Described system, service is classified, different requestor's same types, the subscription request bar of same request parameter Part sends to service provider, and acquiescence transmission condition is:
(1) the subscription request without the type;
(2) subscription for having the type is asked, but required parameter is different;
(3) there is the request of the same required parameter of the type, but response message is not received more than scheduled time threshold value;
Transmission condition is extended according to actual business requirement, and scheduled time threshold value difference service is independently arranged.
Described system, messenger service distribution module uses overtime autoprobing machine system, to more than scheduled time threshold value not The service for receiving response message is detected.
Described system, the forwarding of messenger service distribution module, distribution subscribe to request and during response message, using making the right way of conduct by oneself Formula is transmitted message.
Purpose of the present invention beneficial effect is:By messenger service subscribing module, messenger service distribution module and message The cooperating of release module is serviced, the burden brought to subscriber and service provider is frequently subscribed in reduction and network is born Pressure is carried, Standard Service presentation mode, the stability and service for improving the treatment of high-volume task provides efficiency.
Brief description of the drawings
Fig. 1 is messenger service middleware system structure chart;
Fig. 2 is messenger service subscribing module illustrative view of functional configuration;
Fig. 3 is messenger service subscribing module flow chart.
Fig. 4 is messenger service distribution module illustrative view of functional configuration
Fig. 5 is messenger service release module illustrative view of functional configuration;
Specific embodiment
A kind of messenger service middleware system of the invention is described in detail below with reference to Figure of description.
The technical problems to be solved by the invention are to provide a kind of messenger service middleware system based on distribution thought, should All kinds of request tasks are subscribed in genealogical classification, and the request task of same type is simply requested once within a certain period of time, to reduce service The pressure that provider is processed request task;The data provided service side or service are using registration distribution technology so that each Data or service requester can in time obtain required data or service.
Messenger service middleware system structure is as shown in figure 1, its specific implementation is as follows:
System sets 1) messenger service subscribing module;2) messenger service distribution module;3) messenger service release module, its In:
1) messenger service subscribing module
Messenger service subscribing module is mainly realized subscribing to the registration of request, send and subscribing to the correct return of data.Disappear Breath service subscription module data flows to and is:After request task is subscribed in instantiation, subscribing module is registered service request task Registration, and the solicited message with service codes and filter condition is sent to messenger service distribution module;Messenger service is subscribed to After module receives return data, according to service codes and log-on message, return data are returned into corresponding requestor.
Messenger service subscribing module class figure is as shown in Fig. 2 all kinds of functions is as follows:
(1) CMsgSubscribeListMgr classes:Initialization running environment simultaneously starts receiving thread, manages log-on message, And distribute return data;
(2) CMsgSubscribe classes:Message subscribing interface is defined, its subclass needs the method for realizing such definition;
(3) NewClass classes and NewClass2 classes:Message subscribing example class, inherits CMsgSubscribe classes, according to tool Body business demand realizes the interface of CMsgSubscribe classes definition.
Messenger service middleware message number in the form of service codes or referred to as distinguishes different services, and service side is to every One service provides a specific service codes, subscriber to provide service codes in the way of obtain service, service codes are according to specifically Service needed carries out self-defined.Messenger service subscribing module is processed by the way of filter condition needs the subscription of specially treated to ask Ask, such as A asks the rain event of Jinan City in 2013, B to ask Qingdao City's rain event of 2014, and A and B will be using identical Service codes make requests on, but both required parameter will be distinguished in filter condition.
Messenger service subscribing module flow chart is as shown in Figure 3.
Messenger service subscribing module supports the business that two subscribers subscribe to mutually.For example, A provides the service letter of rainwater class Breath, B provides the information of grain yield class, then A subscribes to the information service of request grain class to B, and B subscribes to request rainwater class to A Information service.
2) messenger service distribution module
Messenger service distribution module is the main body module of messenger service middleware, and the function that module needs are realized includes: Obtain service profile information, message parsing, message distribution (including subscribe to request forwarding and subscribe to data forwarding), it is identical please Ask treatment, special subscription treatment (filtration treatment) and subscription information registration and unsubscribe.
Messenger service distribution module implements flow:
(1) initialize running environment, obtain service profile information, including COS, service provider address, use Communication mode and the automatic detection cycle of service, in configuration information record to service forward table;
(2) messenger service distribution module receives message;
(3) messenger service distribution module is parsed to message, obtains type of message and messenger service code;
(4) messenger service distribution module is processed accordingly according to type of message and service codes.Basic messae type bag Include:Request message, response message, message and probe message are unsubscribed, type of message is extended according to service needed.Such as The type of message that receives of fruit is that do not have the request of the type in request message, and register list, or required parameter not phase Together, then corresponding service provider is forwarded messages to according to service forward table, and the subscription information is write into register list, separately Outward, if having the request of the type, but response is not received more than certain time threshold, messenger service distribution module can be retransmitted The subscription is asked.If response message, then message is returned into corresponding subscriber according to service codes and register list;Number According to it is return when filter condition in register list select return mode, return mode is self-defined.If unsubscribe disappearing Breath, then delete the subscriber from register list, and when register list is space-time, messenger service distribution module is by the type Messenger service provider sends and unsubscribes message.If probe message, then service provider is pointed out normally to run, and according to Business demand carries out relevant treatment.
Messenger service distribution module includes service detection mechanism, when the request of certain type does not receive sound more than certain threshold value At once, messenger service distribution module will send the subscription request of the type from trend service end.Timeout threshold is according to different clothes Business demand is independently arranged.
Messenger service distribution module class figure is as shown in figure 4, types of functionality is as follows:
(1) CMsgDispatchMgr classes:Initialization running environment, there is provided the total interface of service;
(2) CMsgParser classes:Message is parsed, and obtains messenger service code necessary information
(3) SMsgHead classes:Message analytic structure is defined, according to operation expanding;
(4) CMsgSubscribeMgr classes:Subscribe to request registration and forwarding, response message distribution and other kinds type disappear Breath treatment;
(5) CSubscribe classes:Define subscriber's log-on message form, including subscriber address, the necessary letter of filtration parameter Breath
(6) CMsgReqSendFactory classes:Subscribe to the management of solicited message sending method
(7) CMsgSubResponseHandler classes:Solicited message transmission interface is subscribed in definition, is easy to self-defined subscription to ask Seek message mode
(8) CMsgSendHandler0 classes and CMsgSendHandler1 classes:The subscription solicited message sender of instantiation Formula
(9) CMsgReqSendFactory classes:The return mode of response data is managed;
(10) CMsgSendHandle classes:The return mode interface of subscription response message, is easy to self-defined response message return Mode
(11) CDetailMsgHandler0 classes and CDetailMsgHandler1 classes:The return side of response data of instantiation Formula class
3) messenger service release module
Messenger service release module is mainly realized subscribing to the reception of request, parsing and subscribes to the return of data.Message takes Business release module flow is as follows:
(1) messenger service release module receives message;
(2) messenger service release module is parsed to message, obtains the service codes and type of message of the request;
(3) if subscription request message, messenger service release module please according to the subscription that the service codes search this service Register list is sought, if there is the request of the type, is not processed, otherwise by subscription request registration to ordering Read request register list in, and by subscribe to request be supplied to service provider;
(4) if receiving probe message, register list is asked according to the subscription that messenger service code searches this service, such as There is the request of the type in fruit, then return to probe response message;Otherwise, probe message is parsed, is obtained and is subscribed to solicited message, And in the subscription request register list that subscription request registration is serviced to this, and it is supplied to service to provide subscription request Side.
Messenger service release module class figure is as shown in figure 5, types of functionality is as follows:
(1) CPubSubServer classes:Realize that message sink, parsing and response data are return.

Claims (5)

1. it is a kind of based on the messenger service middleware system for distributing thought, it is characterised in that system includes that 1) messenger service is subscribed to Module;2) messenger service distribution module;3) messenger service release module, wherein:
1) messenger service subscribing module
Messenger service subscribing module, main to realize subscribing to the registration of request, send and subscribing to the correct return of data, message clothes Business subscribing module data flow be:After request task is subscribed in instantiation, messenger service subscribing module carries out service request task Registration, and the solicited message with service codes and filter condition is sent to messenger service distribution module;Messenger service After subscribing module receives return data, according to service codes and log-on message, return data are returned into corresponding requestor, The types of functionality of messenger service subscribing module is as follows:
(1) CMsgSubscribeListMgr classes:Initialization running environment simultaneously starts receiving thread, manages log-on message, and divide Beam back and return data;
(2) CMsgSubscribe classes:Message subscribing interface is defined, its subclass needs the method for realizing such definition;
(3) NewClass classes and NewClass2 classes:Message subscribing example class, inherits CMsgSubscribe classes, according to specific industry Business demand realizes the interface of CMsgSubscribe classes definition;
Messenger service middleware system, in the form of service codes or referred to as message number distinguish different services, service side couple Each service provide a specific service codes, subscriber to provide service codes in the way of obtain service, service codes are according to tool Body service needed carry out it is self-defined, messenger service subscribing module processed by the way of filter condition need specially treated subscription please Ask;
Messenger service subscribing module supports the business that two subscribers subscribe to mutually;
2) messenger service distribution module
Messenger service distribution module, is the main body module of messenger service middleware system, and the function that module needs are realized includes: Obtain service profile information, message parsing, message distribution, including subscribe to request forwarding and subscribe to data forwarding, it is identical please Ask treatment, special subscription treatment or filtration treatment and subscription information registration and unsubscribe;
Messenger service distribution module implements flow:
(1) running environment is initialized, service profile information, including COS, service provider address, the communication of use is obtained Mode and the automatic detection cycle of service, in configuration information record to service forward table;
(2) messenger service distribution module receives message;
(3) messenger service distribution module is parsed to message, obtains type of message and messenger service code;
(4) messenger service distribution module is processed accordingly according to type of message and service codes, and basic messae type includes:Please Ask message, response message, unsubscribe message and probe message, type of message is extended according to service needed;If connect The type of message for receiving is that do not have the request of the type or required parameter to differ in request message, and register list, then Corresponding service provider is forwarded messages to according to service forward table, and the subscription information is write into register list;In addition, such as Fruit has the request of the type, but does not receive response more than certain time threshold, and messenger service distribution module can retransmit this and order Request is read, if response message, then message corresponding subscriber is returned into according to service codes and register list;Data are returned Filter condition when returning in register list selects return mode, and return mode is self-defined;If unsubscribing message, then The subscriber is deleted from register list, when register list is space-time, messenger service distribution module is by the message of the type Service provider sends and unsubscribes message;If probe message, then service provider is pointed out normally to run, and according to business Demand carries out relevant treatment;
Messenger service distribution module includes service detection mechanism, when the request of certain type does not receive response more than certain threshold value When, messenger service distribution module will send the subscription request of the type from trend service end, and timeout threshold is according to different services Demand is independently arranged;
Messenger service distribution module types of functionality is as follows:
(1) CMsgDispatchMgr classes:Initialization running environment, there is provided the total interface of service;
(2) CMsgParser classes:Message is parsed, and obtains messenger service code;
(3) SMsgHead classes:Message analytic structure is defined, is extended according to business;
(4) CMsgSubscribeMgr classes:Subscribe at request registration and forwarding, response message distribution and other kinds type message Reason;
(5) CSubscribe classes:Define subscriber's log-on message form, including subscriber address, filtration parameter;
(6) CMsgReqSendFactory classes:Subscribe to the management of solicited message sending method;
(7) CMsgSubResponseHandler classes:Solicited message transmission interface is subscribed in definition, is easy to self-defined subscription request to disappear Breath sending method;
(8) CMsgSendHandler0 classes and CMsgSendHandler1 classes:The subscription solicited message sending method of instantiation;
(9) CMsgReqSendFactory classes:The return mode of response data is managed;
(10) CMsgSendHandle classes:The return mode interface of subscription response message, is easy to the return mode of self-defined response message;
(11) CDetailMsgHandler0 classes and CDetailMsgHandler1 classes:The return mode of response data of instantiation Class;
3) messenger service release module
Messenger service release module is mainly realized subscribing to the reception of request, parsing and subscribes to the return of data, and messenger service is sent out Cloth module workflow is as follows:
(1) messenger service release module receives message;
(2) messenger service release module is parsed to message, obtains the service codes and type of message of the request;
(3) if subscription request message, messenger service release module asks note according to the subscription that the service codes search this service Volume list, if there is the request of the type, is not processed, otherwise please to subscription by subscription request registration In seeking register list, and service provider is supplied to by request is subscribed to;
(4) if receiving probe message, register list is asked according to the subscription that messenger service code searches this service, if Request through there is the type, then return to probe response message;Otherwise, probe message is parsed, is obtained and is subscribed to solicited message, and will In the subscription request register list that subscription request registration is serviced to this, and service provider is supplied to by request is subscribed to;
The class function of messenger service release module is CPubSubServer classes:Realize that message sink, parsing and response data are returned Return.
2. system according to claim 1, it is characterized in that:Message subscribing interface is set, is sent according to regulation form and subscribed to Request, subscribes to request form and provides as follows:
Heading+service codes+filtration parameter+message mark
Heading is protocol massages head, and length is specified according to the agreement for using;Service codes are carried out according to practical business demand Definition, length is arranged as required to;Filtration parameter is used to distinguish the subscription request that same type asks different required parameters, its form Carried out according to practical business self-defined;Message marks the message needed for for distinguishing various types of messages type and business to mark.
3. system according to claim 1, it is characterized in that:Service is classified, it is different requestor's same types, identical The subscription request condition of required parameter sends to service provider, and acquiescence transmission condition is:
(1) the subscription request without the type;
(2) subscription for having the type is asked, but required parameter is different;
(3) there is the request of the same required parameter of the type, but response message is not received more than scheduled time threshold value;
Transmission condition is extended according to actual business requirement, and scheduled time threshold value difference service is independently arranged.
4. system according to claim 1, it is characterized in that:Messenger service distribution module uses overtime autoprobing machine system, Service to not receiving response message more than scheduled time threshold value is detected.
5. system according to claim 1, it is characterized in that:The forwarding of messenger service distribution module, distribution are subscribed to request and are rung When answering message, message is transmitted using self-defined mode.
CN201410516976.4A 2014-09-30 2014-09-30 A kind of messenger service middleware system based on distribution thought Active CN104243611B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201410516976.4A CN104243611B (en) 2014-09-30 2014-09-30 A kind of messenger service middleware system based on distribution thought

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410516976.4A CN104243611B (en) 2014-09-30 2014-09-30 A kind of messenger service middleware system based on distribution thought

Publications (2)

Publication Number Publication Date
CN104243611A CN104243611A (en) 2014-12-24
CN104243611B true CN104243611B (en) 2017-07-07

Family

ID=52230939

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410516976.4A Active CN104243611B (en) 2014-09-30 2014-09-30 A kind of messenger service middleware system based on distribution thought

Country Status (1)

Country Link
CN (1) CN104243611B (en)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104539506A (en) * 2015-01-27 2015-04-22 浪潮集团有限公司 Network transmission service component and network transmission system
CN104636211B (en) * 2015-03-10 2018-10-16 中国农业银行股份有限公司 Information interacting method and middleware system between a kind of software systems
CN105282227A (en) * 2015-09-06 2016-01-27 浪潮软件股份有限公司 High-efficiency and high-stability page real-time data refreshing method
CN106385435A (en) * 2016-08-30 2017-02-08 乐视控股(北京)有限公司 Service treatment method and system of service system
CN107968805B (en) * 2016-10-20 2020-10-27 华为技术有限公司 Event notification method and server
CN106657349A (en) * 2016-12-29 2017-05-10 上海理想信息产业(集团)有限公司 Message subscription processing device, system and method
CN108509184B (en) * 2018-03-28 2021-11-09 武汉斗鱼网络科技有限公司 Message distribution method, computer-readable storage medium and electronic device
CN109067690B (en) * 2018-08-07 2021-03-26 腾讯科技(深圳)有限公司 Method and device for pushing offline calculation result data
CN109144639B (en) * 2018-08-07 2021-09-07 武汉斗鱼网络科技有限公司 Bullet screen message distribution method, device, equipment and storage medium
CN111245872B (en) * 2018-11-28 2023-10-13 北京亿阳信通科技有限公司 Sequential message filtering and distributing platform and method
CN112306690A (en) * 2020-11-02 2021-02-02 中国联合网络通信集团有限公司 Scheduling method and device
CN112751916B (en) * 2020-12-28 2022-03-25 中国科学院软件研究所 Data publishing-subscribing method and system for micro-service governance
CN113542217B (en) * 2021-06-07 2023-05-26 广发银行股份有限公司 Service subscription system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003065206A2 (en) * 2002-01-24 2003-08-07 Object Interactive Technologies Limited Dynamic distribution and integration of computer code objects
WO2008066876A1 (en) * 2006-12-02 2008-06-05 Andrew Macgaffey Smart jms network stack
CN102377685A (en) * 2010-08-06 2012-03-14 阿里巴巴集团控股有限公司 Subscription message sending system and subscription message sending method
CN103534988A (en) * 2013-06-03 2014-01-22 华为技术有限公司 Publish and subscribe messaging method and apparatus
CN103841206A (en) * 2014-03-17 2014-06-04 北京京东尚科信息技术有限公司 Thematic message subscripting and releasing method

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003065206A2 (en) * 2002-01-24 2003-08-07 Object Interactive Technologies Limited Dynamic distribution and integration of computer code objects
WO2008066876A1 (en) * 2006-12-02 2008-06-05 Andrew Macgaffey Smart jms network stack
CN102377685A (en) * 2010-08-06 2012-03-14 阿里巴巴集团控股有限公司 Subscription message sending system and subscription message sending method
CN103534988A (en) * 2013-06-03 2014-01-22 华为技术有限公司 Publish and subscribe messaging method and apparatus
CN103841206A (en) * 2014-03-17 2014-06-04 北京京东尚科信息技术有限公司 Thematic message subscripting and releasing method

Also Published As

Publication number Publication date
CN104243611A (en) 2014-12-24

Similar Documents

Publication Publication Date Title
CN104243611B (en) A kind of messenger service middleware system based on distribution thought
EP3734913A1 (en) Communication method and communication apparatus
CN105159781B (en) Adjust the method, apparatus and intelligent terminal of intelligent terminal application network speed
WO2018133306A1 (en) Dispatching method and device in content delivery network
CN112788074B (en) Data transmitting method, processing method, receiving method, apparatus thereof, and storage medium
US20140057606A1 (en) Method and system to enable mobile users to receive personalized notifications
CN109040326A (en) The method and apparatus of PUSH message
CN106230922A (en) A kind of news subscribing method, message production unit and message reception units
US9985925B2 (en) Apparatus and methods for bandwidth saving and on-demand data delivery for a mobile device
CN105100062A (en) Information push method, device and system
CN110851248A (en) Asynchronous task data processing method and device and computer readable storage medium
CN108124007A (en) The method and apparatus of message data real-time Transmission
CN103095684A (en) Method obtaining attention user aggregate information, device and system
CN109889558A (en) Data transmission method, middleware and the system of internet of things oriented application
KR20180105917A (en) Flexible wearable platform systems and methods for wearable data provision and intelligent wearable information services using MQTT protocols
CN104010228A (en) Apparatus and method for level-based self-adjusting peer-to-peer media streaming
CN114285906B (en) Message processing method and device, electronic equipment and storage medium
WO2016101446A1 (en) Data analysis method, apparatus, system, and terminal, and server
CN106686635B (en) Data transmission method and device based on control and configuration protocol of wireless access point
CN112967142A (en) Method and device for forwarding market information stream
EP2622499B1 (en) Techniques to support large numbers of subscribers to a real-time event
CN113204436A (en) Message processing method, device, equipment and computer readable storage medium
CN107249017B (en) A kind of method and server obtaining HLS content by CDN network
CN103533001A (en) Communication method and communication system based on HTTP multi-proxy, and intermediate proxy server
CN107872498B (en) Service data subscription method, device and system

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant