CN114615096A - Telecommunication charging method, system and related equipment based on event-driven architecture - Google Patents
Telecommunication charging method, system and related equipment based on event-driven architecture Download PDFInfo
- Publication number
- CN114615096A CN114615096A CN202111399815.8A CN202111399815A CN114615096A CN 114615096 A CN114615096 A CN 114615096A CN 202111399815 A CN202111399815 A CN 202111399815A CN 114615096 A CN114615096 A CN 114615096A
- Authority
- CN
- China
- Prior art keywords
- event
- service
- submitting
- service request
- computing architecture
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000003860 storage Methods 0.000 claims abstract description 78
- 238000012545 processing Methods 0.000 claims abstract description 48
- 238000011217 control strategy Methods 0.000 claims abstract description 35
- 230000008569 process Effects 0.000 claims abstract description 18
- 238000006243 chemical reaction Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 6
- 238000011161 development Methods 0.000 abstract description 10
- 238000012423 maintenance Methods 0.000 abstract description 6
- 238000007726 management method Methods 0.000 description 47
- 238000004891 communication Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 8
- 230000015654 memory Effects 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 5
- 238000004364 calculation method Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 230000010354 integration Effects 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000005034 decoration Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000036541 health Effects 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000005291 magnetic effect Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000011144 upstream manufacturing Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000013070 change management Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000008602 contraction Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000005070 sampling Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
- H04L12/1407—Policy-and-charging control [PCC] architecture
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
A telecommunication charging method, system and related equipment based on event-driven architecture comprises: acquiring application list data and event message definition list data of an event-driven computing architecture, submitting an event management platform to process and generate a control strategy and/or a routing rule, and issuing the control strategy and/or the routing rule to an event grid for execution; receiving a service request issued by the micro-service of any event-driven computing architecture, and submitting the service request to an event grid for storage; receiving one or more subscription requests generated by the micro-service of the event-driven computing architecture, submitting the event grid to call the storage service according to a control strategy and/or a routing rule, and distributing the storage service to the micro-service of the event-driven computing architecture issuing the subscription request to execute the service. By adopting the technical scheme, the real-time and efficient processing of telecommunication charging service events is realized, the rapid iterative development of services is supported, and the problem that the system cannot process timely is solved; meanwhile, the maintenance cost of the system is reduced.
Description
[ technical field ] A method for producing a semiconductor device
The present invention relates to the field of computer network technologies, and in particular, to a method, a system, and a related device for telecommunication charging based on an event-driven architecture.
[ background of the invention ]
With the commercial landing and continuous development of 5G technology, a great deal of services between the Internet of things and man-machine interaction emerge at the same time, and in addition, the rapid development of directional videos and the network characteristics of 'always online' of users, the continuous abundance of service types brings huge impact to a billing support system of a telecommunication operator, and the service type comprises a series of changes such as the large increase of data volume, the diversification of services, the complication of package types and the like, and flexible, uninterrupted, batch and real-time service is the biggest challenge faced by a telecommunication billing system.
The existing telecommunication industry charging system has high requirements on system throughput and performance due to large charging service data volume and complex service calculation rules, and is based on a distributed flow calculation microservice architecture; the charging service application is composed of producer service/consumer service, a consumer registers in a registration center, the producer discovers the consumer from the registration center and sends a task to the consumer for processing, message interaction is carried out between the producer and the consumer through RPC communication based on an SDL protocol, and data circulation is carried out between applications through a shared storage or a distributed storage as a medium to realize flow calculation.
However, the existing telecommunication billing system architecture includes the following problems: (1) the coupling is high, the service is remotely called through the SDL interface, and the service consumer is influenced by the fault or upgrade of the service provider; newly adding a charging downstream service requires that an upstream charging service newly outputs a file, and the code of the upstream service needs to be adjusted, so that the service agility is influenced; (2) agility treatment capacity is insufficient, a dehaps operation and maintenance mode and gray level treatment capacity are not supported, online is required to be planned according to a large version, and online efficiency has a large promotion space; (3) the service framework is bound by languages, the service framework is provided for service application in an SDK mode, service frameworks SDKs of different languages need to be provided, and the maintenance cost is high.
[ summary of the invention ]
Aiming at the defects in the prior art, the application aims to provide a telecommunication charging method, a telecommunication charging system and related equipment based on an event-driven architecture, so that the telecommunication charging service event is efficiently processed in real time, the rapid iterative development of services is supported, and the problem that the system cannot process timely is solved; meanwhile, the maintenance cost of the system is reduced.
In order to achieve the purpose, the invention provides the following technical scheme:
in a first aspect, a telecommunication charging method based on an event-driven architecture is provided, which includes:
acquiring application list data and event message definition list data of an event-driven computing architecture, submitting an event management platform to process and generate a control strategy and/or a routing rule, and issuing the control strategy and/or the routing rule to an event grid for execution;
receiving a service request issued by the micro-service of any event-driven computing architecture, and submitting the service request to the event grid for storage;
receiving one or more subscription requests generated by the micro-service of the event-driven computing architecture, submitting the event grid to call the storage service according to a control strategy and/or a routing rule, and distributing the storage service to the micro-service of the event-driven computing architecture issuing the subscription request to execute the service.
The invention is further configured to: the submitting event management platform processes and generates a control strategy and/or a routing rule, and the specific steps comprise:
acquiring application list data and event message definition list data, submitting the application list data and the event message definition list data to an event stream arranging module for corresponding binding processing to generate event stream topology information, and storing the generated event stream topology information to an event resource warehouse;
and issuing the strategy and/or the routing rule generated by the event flow topology information to a control plane.
The invention is further configured to: the receiving of the service request issued by the micro-service of any event-driven computing architecture and the submitting to the event grid storage specifically comprises the following steps:
receiving a service request issued by the micro-service of any event-driven computing architecture, submitting the service request to a corresponding sidecar agent, and forwarding the service request by the sidecar agent according to a control strategy and/or a routing rule provided by a control plane;
and acquiring the service request forwarded by the sidecar agent, and importing the service request into a storage plane for storage.
The invention is further configured to: the method comprises the following steps of receiving one or more subscription requests generated by the microservices of the event-driven computing architecture, submitting the event grid to invoke storage services according to a control strategy and/or a routing rule, and distributing the storage services to the microservices of the event-driven computing architecture issuing the subscription requests for service execution, wherein the method specifically comprises the following steps:
receiving one or more subscription requests generated by the micro-service of the event-driven computing architecture, and submitting the one or more subscription requests to corresponding side car agents, wherein the side car agents forward the subscription requests according to a control strategy and/or a routing rule provided by a control plane;
obtaining the subscription request forwarded by the sidecar agent, submitting the subscription request to a storage plane for inquiring and calling a corresponding service request, and sending the service request back to the sidecar agent for forwarding;
and acquiring the service request forwarded by the sidecar agency, and distributing the service request to one or more micro-services of the event-driven computing architecture generating a subscription request to execute the service.
The invention is further configured to: the event-driven computing architecture comprises an event processing engine supporting EventLoop, Commander and EventCaller operation modes.
The invention is further configured to: the operation mode of the event processing engine adopts an asynchronous thread pool mode.
The invention is further configured to: the method for receiving the service request issued by the micro-service of any event-driven computing architecture specifically comprises the following steps:
acquiring a service request issued by an external application, submitting the service request to an event gateway for data conversion, accessing the converted service request to a sidecar agent corresponding to the event gateway by the event gateway, and forwarding the service request to a storage plane by the sidecar agent according to a control strategy and/or a routing rule;
acquiring data of an external storage medium, submitting the data to a source connector for data conversion, forwarding a converted service request through the sidecar agent deployed on the source connector, and submitting the converted service request to the storage plane;
and acquiring a service request generated by the timing trigger of the user-defined event source, forwarding the service request through the sidecar agent deployed in the user-defined event source, and submitting the service request to the storage plane.
The invention is further configured to: the event-driven computing architecture comprises a Sink connector used for acquiring data from the event grid, and the Sink connector exports the data to different external storage media through a data conversion rule.
The invention is further configured to: before the microservice distributed to the event-driven computing architecture issuing the subscription request is used for executing the service, the event management platform performs real-time management on the event grid, and specifically includes:
and acquiring the flow data of the event grid, submitting the flow data to the event management platform for management, and realizing service statistics.
In a second aspect, there is provided a telecommunications charging distributed computing system based on an event driven architecture, comprising:
the strategy acquisition module is used for acquiring application list data and event message definition list data of the event-driven computing architecture, submitting the application list data and the event message definition list data to an event management platform for processing and generating a control strategy and/or a routing rule, and issuing the control strategy and/or the routing rule to an event grid for execution;
the request issuing module is used for receiving a service request issued by the micro-service of any event-driven computing architecture and submitting the service request to the event grid for storage;
the request acquisition module is used for receiving one or more subscription requests generated by the micro-service of the event-driven computing architecture, submitting the event grid to call the storage service according to a control strategy and/or a routing rule, and distributing the storage service to the micro-service of the event-driven computing architecture issuing the subscription request to execute the service.
In a third aspect, a computer-readable storage medium is provided, on which a computer program is stored, which program, when being executed by a processor, carries out the steps of the telecommunication charging method according to any of the preceding claims.
In a fourth aspect, a terminal is provided, which includes:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the steps of the telecommunications billing method of any of the preceding claims.
Compared with the prior art, the invention has the following advantages:
1. the event grid is used as a middleware among the micro-services of the event-driven computing architecture, and a communication transmission function among the micro-services of the event-driven computing architecture is received, so that the micro-services of the event-driven computing architecture are concentrated on business logic, the communication logic is stripped from the business logic, the decoupling between the business logic and a service framework is realized, the problem that the logic of a producer needs to be modified when a consumer is newly added in the existing charging system is solved, the quick iterative development of the business is supported, and the business agility of an operator client is improved;
2. the data plane comprises a plurality of side car agents which are communicated with each other, the side car agents and the micro-services of the event-driven computing architecture are in pairwise occurrence and correspond to each other, a service grid is constructed among the micro-services of the event-driven computing architecture, the service grid is used for processing communication among the services, and flexible, reliable and rapid event distribution routing capacity is provided, so that the event-driven computing architecture is concentrated in being responsible for service processing, decoupling between service logic and a service framework is realized, the problem that the logic of a producer needs to be modified when a consumer is newly added in the existing charging system is solved, rapid iterative development of services is supported, and the business agility of an operator client is improved; meanwhile, in a side car mode, the system pushes the event notification in an event producer active pushing mode, instead of acquiring update information based on a pulling mode by a consumer, so that the problem that the system cannot process timely is solved;
3. the storage plane is formed by different message queue clusters, the data plane is used as a middleware between the microservice of the event-driven computing architecture and the storage plane, and the charging event is circulated through the message queues, so that the problem that a file is required to be circulated among multiple links of the conventional charging system is solved, and the overall processing efficiency of the system is improved;
4. the event-driven computing architecture is based on the CloudEvent specification, supports multiple application types such as service code, micro service, webapp and the like to be rapidly accessed into an event grid through characteristics such as an event gateway, a source connector and the like, supports an operator charging system to rapidly integrate a third-party platform, and constructs an industry ecology;
5. event request backlog quantity and sampling record are carried out on a storage plane in the process of counting and outputting through an event monitoring module, and an event transmission path is uploaded, so that the counting of computing services is realized, and the visual management of an event grid is realized;
6. the event management platform is a front-end interactive management platform of the system and is used for managing the resource condition of an event grid and providing a corresponding management interface for automatically controlling resources by a charging peripheral system;
7. through the construction of a Service Mesh, event access is independent of the flow description of a calculation method of a specific programming language and an operation environment, the whole logic architecture is flexible and variable, and different technical architectures can be used for realizing the technical model, so that the system performance is reliable, and meanwhile, the system portability and expandability are enhanced; meanwhile, the method can quickly respond to the change of business requirements and the technical change, and supports and establishes a high-concurrency, high-response and dense data transmission computing system;
8. the system is an architecture mode focusing on asynchronous communication based on generation/consumption, compared with synchronous communication, when asynchronous communication sends characters, time slots among the sent characters can be random, the system is suitable for the rapid development of directional videos and the network characteristics of 'always on' of users, can quickly respond to the change of service requirements and the technical change, and supports and establishes a high-concurrency, high-response and dense data transmission computing system.
[ description of the drawings ]
FIG. 1 is a flowchart illustrating the steps of the present embodiment;
FIG. 2 is a logic diagram of the event bus service of the present embodiment;
FIG. 3 is a diagram illustrating an EventLoop mode according to the present embodiment;
FIG. 4 is a diagram illustrating the Commander schema of the present embodiment;
FIG. 5 is a schematic diagram of EventCaller mode in the present embodiment;
FIG. 6 is a logic diagram of an event grid according to the present embodiment;
fig. 7 is a schematic structural view of the sidecar mode of the present embodiment.
[ detailed description ] embodiments
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are illustrative only and should not be construed as limiting the invention.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
As will be understood by those skilled in the art, a "terminal" as used herein includes both devices having a wireless signal receiver, which are only devices having a wireless signal receiver without transmit capability, and devices having receive and transmit hardware, which are devices having receive and transmit hardware capable of two-way communication over a two-way communication link. Such a device may include: a cellular or other communication device having a single line display or a multi-line display or a cellular or other communication device without a multi-line display; PCS (PerSonal CommunicationS Service), which may combine voice, data processing, facsimile and/or data communication capabilities; a PDA (PerSonal Digital ASSiStant), which may include a radio frequency receiver, a pager, internet/intranet access, web browser, notepad, calendar and/or GPS (Global PoSitioning SyStem) receiver; a conventional laptop and/or palmtop computer or other device having and/or including a radio frequency receiver. As used herein, a "terminal" or "terminal device" can be portable, transportable, installed in a vehicle (aeronautical, maritime, and/or land-based), or situated and/or configured to operate locally and/or in a distributed fashion at any other location(s) on earth and/or in space. As used herein, a "terminal Device" may also be a communication terminal, a web terminal, a music/video playing terminal, such as a PDA, an MID (Mobile Internet Device) and/or a Mobile phone with music/video playing function, or a smart tv, a set-top box, etc.
As shown in fig. 1 and fig. 2, a method for charging a telecommunication service based on an event-driven architecture disclosed in the present invention includes:
s1, acquiring application list data and event message definition list data of the event-driven computing architecture, submitting the application list data and the event message definition list data to an event management platform for processing and generating a control strategy and/or a routing rule, and issuing the control strategy and/or the routing rule to an event grid for execution;
s2, receiving a service request issued by the micro-service of any event-driven computing architecture, and submitting the service request to an event grid for storage;
s3, receiving one or more subscription requests generated by the micro-service of the event-driven computing architecture, submitting the event grid to call the storage service according to the control strategy and/or the routing rule, and distributing the storage service to the micro-service of the event-driven computing architecture issuing the subscription request to execute the service.
Optionally, in S1, the submitting event management platform processes and generates the control policy and/or the routing rule, and the specific steps include:
acquiring application list data and event message definition list data, submitting the application list data and the event message definition list data to an event stream arranging module for corresponding binding processing to generate event stream topology information, and storing the generated event stream topology information to an event resource warehouse;
and issuing the strategy and/or the routing rule generated by the event stream topology information to a control plane.
Specifically, the Event stream topology information includes a service request and a subscription request that a microservice of the Event-driven computing architecture needs to publish, and Event association Topic, for example, in fig. 2, application a needs to publish Event1, and Event1 is associated with Topic 1.
And storing the generated event stream topology information to an event resource warehouse through an application management module and an event management module, wherein the microservice of the event-driven computing architecture for issuing the subscription request is registered in an event management platform.
Optionally, in S2, receiving a service request issued by a microservice of any event-driven computing architecture, and submitting the service request to an event grid storage, the specific steps include:
receiving a service request issued by the micro-service of any event-driven computing architecture, submitting the service request to a corresponding side car agent, wherein the side car agent provides a standard interface to receive the submitted service request, and forwards the service request according to a control strategy and/or a routing rule provided by a control plane;
and acquiring the service request forwarded by the sidecar agent, and importing the service request into a storage plane for storage.
Optionally, in S2, a service request issued by a microservice of any event-driven computing architecture is received, and the specific method includes:
the method comprises the steps that a service request issued by an external application is obtained and submitted to an event gateway for data conversion, the event gateway has protocol conversion capacity, various protocols used by the external application are converted into standard protocols required by a charging system through protocol conversion so as to be convenient for identification and analysis of modules in the charging system, the event gateway accesses the converted service request to a sidecar agent corresponding to the event gateway, the sidecar agent provides a standard interface to receive the service request accessed by the event gateway, and the sidecar agent forwards the service request to a storage plane according to a control strategy and/or a routing rule;
acquiring data of an external storage medium, submitting the data to a source connector for data conversion, forwarding a converted service request through the sidecar agent deployed on the source connector, and submitting the converted service request to a storage plane;
and acquiring a service request generated by the timing trigger of the user-defined event source, forwarding the service request through a sidecar agent deployed in the user-defined event source, and submitting the service request to a storage plane.
In addition, the event-driven computing architecture comprises a Sink connector used for acquiring data from the event grid, the Sink connector exports the data to different external storage media through a data conversion rule, the Sink connector has a protocol conversion capability, and a protocol used by a standard interface is converted into a private protocol required by the external storage media through the protocol conversion, so that the external storage media can conveniently identify and analyze the data.
Optionally, in S3, receiving one or more subscription requests generated by the microservice of the event-driven computing architecture, submitting the event grid to invoke the storage service according to the control policy and/or the routing rule, and distributing the storage service to the microservice of the event-driven computing architecture issuing the subscription request for service execution, where the specific steps include:
receiving one or more subscription requests generated by the micro-service of the event-driven computing architecture, submitting the one or more subscription requests to a corresponding sidecar agent, wherein the sidecar agent provides a standard interface to receive the subscription requests submitted by the micro-service of the event-driven computing architecture, and forwards the subscription requests according to a control strategy and/or a routing rule provided by a control plane;
the method comprises the steps of obtaining a subscription request forwarded by a sidecar agent, submitting the subscription request to a storage plane for inquiring and calling a corresponding service request, and returning the service request to the sidecar agent for forwarding;
and acquiring the service request forwarded by the sidecar agent, and distributing the service request to one or more event-driven computing architecture microservices generating the subscription request to execute the service.
Illustratively, when a user completes a voice call through an application a, an event management platform acquires the application a and a voice call event, binds messages such as an address, the application a and the voice call event through an event stream arrangement module to generate integrated event stream topology information, and generates a control strategy and/or a routing rule according to the event stream topology information.
Meanwhile, the application A outputs the voice call event, the voice call event is output to the sidecar agent A deployed in the application A to be forwarded, and due to the fact that a plurality of sidecar agents form a service grid through networking, mutual communication among all the sidecar agents is achieved.
Then, the sidecar agent A stores the voice call event to a corresponding message queue according to the control strategy and/or the routing rule.
As the micro-service of the event-driven computing architecture for issuing the subscription request is registered on the event management platform, the event management platform drives the corresponding micro-service B to start, the micro-service B can be selected from one of a comprehensive acquisition system, a new version charging system, an online charging system, a settlement system and a charging and payment system, the micro-service B issues the subscription request to the corresponding sidecar agent B for forwarding, and the sidecar agent B determines a forwarded target message queue according to a control strategy and/or a routing rule and sends the subscription request to the target message queue to acquire the voice call event.
The target message queue distributes the voice call event to the side car agent B, the side car agent B sends the voice call event to the micro-service B, and the micro-service B responds after acquiring the voice call event, executes a charging program and charges the voice call event.
The start of the micro service B is realized through a life cycle management module; for the subscription operation, if the event name sent by the microservice B to the sidecar agent is the event name, topology information is required; if the sent topic is not required to be subjected to topology information, and the corresponding event topic can be found in the storage plane according to the topic.
Optionally, in the step of distributing the event-driven microservice to the event-driven computing architecture issuing the subscription request for performing service execution, the event management platform performs real-time management on the event grid, and specifically includes:
and acquiring the flow data of the event grid, submitting the flow data to an event management platform for management, and realizing service statistics. The charging system introduces an event management platform to track and record the event grid and the event-driven computing architecture and perform service statistics, so that the health degree and the service index of the charging system are monitored, and the accurate grasp of the system operation condition is ensured.
The event-driven computing architecture comprises an event processing engine supporting EventLoop, Commander and EventCaller operation modes, and the operation mode of the event processing engine is an asynchronous thread pool mode.
The event processing engine is used for receiving and issuing an event based on an EventClient provided by an event grid and is divided into an event basic capability layer, an event scene enabling layer and a business service capability layer; the event basic capability layer provides basic capabilities such as an event subscription request, a service publishing request, operation management and the like; the event scene enabling layer provides a high-level event operation interface aiming at a plurality of event operation scenes; the service capability layer provides service execution and service calling clients respectively aiming at a local mode and a remote mode of the service processor, and provides insight capability for recording engine processing indexes and calling information.
The EventLoop, Commander and EventCaller operation modes supported by the event processing engine comprise:
as shown in fig. 3, the EventLoop mode is a basic mode of event processing, and most event applications use the EventLoop operating mode as an initial link of event processing. The run mode logic can be described as: (1) receiving a service request distributed by an event grid by a Subscriber; (2) the Subscriber imports the Service request into Service Exec & Call to execute Service or Call Service; (3) acquiring a Service execution or calling result in Service Exec & Call, and submitting the result to publish; (4) publishing the processing result to an event grid by the Publisher; (5) and the task of accepting the next event repeats the steps.
As shown in fig. 4, the Commander schema is an application developed based on an event-driven computing architecture, and most of the application can generate a Commander-type event message at any link of business logic; the generated Commander Event message sends an Event to a specified Event topic of the storage plane by the Event Commander of the Event processing engine.
As shown in fig. 5, the EventCaller model is an application developed based on an event-driven computing architecture, and event-based service calls can be made at any link of business logic; event-based service calls are classified into synchronous call modes and asynchronous call modes. The synchronous calling mode is supported by an EventSyncCaller component, a Request/Reply theme is created in an event grid for caching a service Request and a corresponding message during calling, a micro-service of an event-driven computing architecture is in a blocking state when synchronous calling is initiated, and a certain timeout time can be set during calling; the asynchronous calling mode is supported by an EventASyncCaller component, a Request/Reply theme is created in an event grid for caching requests and corresponding messages during calling, the micro-service of the event-driven computing architecture can continue to perform other logic processing after initiating the asynchronous calling, the EventASyncCaller informs the micro-service of the event-driven computing architecture of the calling result in a callback mode, and the asynchronous calling mode can also set timeout time.
In another aspect, as shown in fig. 2 and fig. 6, there is provided a telecommunication charging distributed computing system based on an event driven architecture, including:
the strategy acquisition module is used for acquiring application list data and event message definition list data of the event-driven computing architecture, submitting the application list data and the event message definition list data to an event management platform for processing and generating a control strategy and/or a routing rule, and issuing the control strategy and/or the routing rule to an event grid for execution;
the request issuing module is used for receiving a service request issued by the micro-service of any event-driven computing architecture and submitting the service request to the event grid for storage;
the request acquisition module is used for receiving one or more subscription requests generated by the micro-service of the event-driven computing architecture, submitting the event grid to call the storage service according to a control strategy and/or a routing rule, and distributing the storage service to the micro-service of the event-driven computing architecture issuing the subscription request to execute the service.
The system comprises a policy acquisition module, a request issuing module and a request acquisition module, wherein the policy acquisition module, the request issuing module and the request acquisition module are based on an event driven architecture, and specifically comprise event bus services, the event bus services are connected with business events and applications by a standardized CloudEvents protocol and provide centralized event management and driving capability, and the event bus services comprise an event grid, an event driven computing architecture and an event management platform; the event grid is the basis for constructing event bus service, and comprises a data plane, a storage plane and a control plane; the event-driven computing architecture is used for issuing or receiving events to the event grid, integrating business applications and concentrating on development of business logic; the event management platform is used for managing the event-driven computing architecture and the event grid.
Specifically, as shown in fig. 6 and 7, the data plane includes a plurality of communicating sidecar agents, the plurality of sidecar agents are networked to form a service grid, the sidecar agents and the microservices of the event-driven computing architecture appear in pairs and correspond to each other, the data plane is used as an intermediate between the microservices of the event-driven computing architecture and the storage plane, and the microservices of the event-driven computing architecture perform event message interaction with different storage planes through the data plane; the storage plane is formed by a plurality of cross-domain message queue clusters and is used for storing the event messages forwarded by the sidecar agent; the control plane is used to provide policies and/or routing rules for the data plane. The event bus service based on the event-driven architecture is independent of the flow description of a computing method of a specific programming language and an operating environment for event access, the whole logic architecture is flexible and variable, and different technical architectures can be used for realizing the technical model, so that the system performance is reliable, and meanwhile, the portability and the expandability of the system are enhanced.
Furthermore, a plurality of side car agents communicating with each other are constructed into a Mesh structure, namely, the side car agents are constructed into a Service Mesh (Service Mesh), a side car mode (Sidecar) is adopted, the side car mode (Sidecar) means that the side car agents are deployed along with the processes of the Service application, each Service application process is configured with one bound side car agent (Sidecar), and the side car agents (Sidecar) only need to load and set routing rule configuration facing single application. The deployment has the advantages that any sidecar agent has a fault, only a single application process is influenced, other application processes cannot be influenced, and the fault influence plane is controlled in a smaller range.
The event-driven computing architecture is a hybrid microservice computing architecture constructed based on a Servicemesh mechanism and an EDA mechanism, and comprises an event processing engine, wherein the event processing engine has event driving capability and can support service-oriented treatment capability. The event driven computing architecture further comprises:
the event gateway is used for converting data of the event generated by the external application and sending the event to the event grid;
the source connector is used for acquiring data from different external storage media, converting the data and then sending the converted data to the event grid;
and customizing an event source, and generating an event accessed to the event grid according to different condition triggering modes.
And the Sink connector is used for acquiring data from the event grid and exporting the data to different external storage media through a data conversion rule.
The event-driven computing architecture comprises an event processing engine and a business processor, wherein the event processing engine is used after being unpacked, the event processing engine provides calls in a plug-in mode when executing services, and the call integration mode comprises the following steps:
local integration, wherein an event processing engine and a service processor are configured in the same working process, and the service processor and the event processing engine are bound on languages; the business processor may be in single threaded synchronous mode or asynchronous thread pool mode, when in asynchronous thread pool mode, the event processing engine obtains bulk event consumption, i.e., transaction management capability.
And remote integration, wherein the event processing engine and the service processor realize the control of network communication through a sidecar agent. The service processor and the event processing engine are in different working processes, the event processing engine executes services in a service calling mode, the service calling is realized based on the ServiceMesh, the realization language of the remote service processing server can not be bound with the event processing engine, the service server can provide convenience for public services or topology arranged according to certain configuration with the event processing engine, and the remote integration provides convenience in the aspects of multi-language extension, service multiplexing, micro-service processing flow arrangement, multi-level load balancing, service routing and the like of the service services.
The micro services used for executing the services in the event-driven computing architecture are related to a plurality of types, for example, new version charging systems, OCS, hotwalling, charging and payment systems, comprehensive acquisition systems, comprehensive settlement systems, network management and other service type network elements, such as Billing-HSS, ABM, intelligent switching platform and other data type network elements. The comprehensive acquisition system is responsible for completing the acquisition of the telecommunication use records of the user and the format standardization; VC & payment is used for realizing the functions of realizing the recharging of the affiliated telecommunication products and completing the related electronic payment by using the rechargeable card and using voice and network media by customers; the comprehensive settlement system is used for realizing the expense allocation and settlement of using telecommunication services under roaming scenes with other operators; HotBill is used for realizing the charging of the telecommunication service of the post-paid user; the OCS is used to implement charging for prepaid subscriber telecommunication service usage.
The event management platform is a front-end interactive management platform of the event-driven architecture system, abstracts each service of telecommunication charging into an event, is used for managing an event grid and an event-driven computing architecture, provides a corresponding management interface, is convenient for an external system to automatically control resources, and completes the configuration and management related to the event. The event management platform comprises:
the event monitoring module is used for monitoring the resource condition of the event grid;
the event arranging module is used for arranging the binding relationship between the events and the application to generate event stream topology information, generating a strategy and/or a routing rule according to the event stream topology information, and issuing the strategy and/or the routing rule to the control plane;
the event resource warehouse is used for storing the event information generated by the event arranging module;
the interface development module is used for providing management interfaces for the outside, such as interfaces for event list query and the like;
the application management module is used for managing the events which need to be subscribed and received by the micro-service, and is different from the event stream arranging module in that the application management module binds the events to a single application and the event stream arranging module arranges the relations of a plurality of applications and the events;
the event management module is responsible for the index, creation, change management and other functional points of the event;
the Schema management module is responsible for defining an event structure, and can be associated with the Schema management module to describe the specific data structure definition of the event during event definition;
the event theme management module is used for adding, deleting and enumerating event themes, binding the event themes and event clusters, and managing logic themes and subtopic rules;
the event agent management module is used for managing the life cycle of the side car agent, including configuration, starting, stopping and the like;
the event cluster management module is used for configuring a release cluster and performing start-stop management and high availability of the cluster; and displaying the event theme, and inquiring the display cluster, the example linked list and the health state.
An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of any one of the above-mentioned telecommunication charging methods. The storage medium includes, but is not limited to, any type of disk including floppy disks, hard disks, optical disks, CD-ROMs, and magneto-optical disks, ROMs (Read-Only memories), RAMs (Random AcceSS memories), EPROMs (EraSable Programmable Read-Only memories), EEPROMs (Electrically EraSable Programmable Read-Only memories), flash memories, magnetic cards, or optical cards. That is, a storage medium includes any medium that stores or transmits information in a form readable by a device (e.g., a computer). Which may be a read-only memory, magnetic or optical disk, or the like.
An embodiment of the present invention further provides a terminal, where the terminal includes:
one or more processors;
a storage device for storing one or more programs,
when executed by one or more processors, cause the one or more processors to implement the steps of the telecommunications billing method of any of the above.
In summary, the event-driven architecture-based telecommunication charging method, system and related devices provided by the present application have the following beneficial effects:
the event grid is used as a middleware among the micro-services of the event-driven computing architecture, and a communication transmission function among the micro-services of the event-driven computing architecture is received, so that the micro-services of the event-driven computing architecture are concentrated on business logic, the communication logic is stripped from the business logic, the decoupling between the business logic and a service framework is realized, the problem that the logic of a producer needs to be modified when a consumer is newly added in the existing charging system is solved, the quick iterative development of the business is supported, and the business agility of an operator client is improved; meanwhile, in a side car mode, the system pushes the event notification in an event producer active pushing mode, instead of acquiring the update information based on a pulling mode by a consumer, and the problem that the system cannot process timely is solved.
Compared with the existing charging system, the event-driven architecture-based telecommunication charging method can support charging service agility and improve the service online efficiency by more than 70%; the characteristics of event-driven service and real-time event response of the method can improve the timeliness of business processing by over 60 percent; under the requirement of high performance, the method has the advantages that the degree of detachability of the highly loose coupling supporting business microservice is improved by more than 50%; the method can improve the automation of the operator charging service system and reduce the operation and maintenance cost by more than 40 percent.
The method can continuously guarantee the high availability and the elastic expansion and contraction capacity of the service system, and improve the automatic operation and maintenance capacity; the method can help the client architecture to be expandable, servitization, observability and cloud primary sustainable evolution; the method can help the customer to improve the customer perception of the service, and simultaneously can save the cost of storage resources; the method can provide the unified access and consumption processing capability of the Internet of things and the edge computing event of the client; the method can provide a client uniform event and support the acquisition and processing capacity of the BOM domain monitoring event; the method can provide the capabilities of analyzing the client data and uniformly acquiring and processing the AI events.
It will be understood by those within the art that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. Those skilled in the art will appreciate that the computer program instructions may be implemented by a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, implement the features specified in the block or blocks of the block diagrams and/or flowchart illustrations of the present disclosure.
Those of skill in the art will appreciate that various operations, methods, steps in the processes, acts, or solutions discussed in the present application may be alternated, modified, combined, or deleted. Further, various operations, methods, steps in the flows, which have been discussed in the present application, may be interchanged, modified, rearranged, decomposed, combined, or eliminated. Further, steps, measures, schemes in the various operations, methods, procedures disclosed in the prior art and the present invention can also be alternated, changed, rearranged, decomposed, combined, or deleted.
The foregoing is only a partial embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (12)
1. A telecommunication charging method based on an event-driven architecture is characterized by comprising the following steps:
acquiring application list data and event message definition list data of an event-driven computing architecture, submitting an event management platform to process and generate a control strategy and/or a routing rule, and issuing the control strategy and/or the routing rule to an event grid for execution;
receiving a service request issued by the micro-service of any event-driven computing architecture, and submitting the service request to the event grid for storage;
receiving one or more subscription requests generated by the micro-service of the event-driven computing architecture, submitting the event grid to call the storage service according to a control strategy and/or a routing rule, and distributing the storage service to the micro-service of the event-driven computing architecture issuing the subscription request to execute the service.
2. The telecommunication charging method according to claim 1, wherein said submitting event management platform processes and generates control policy and/or routing rule, the specific steps comprising:
acquiring application list data and event message definition list data, submitting the application list data and the event message definition list data to an event stream arranging module for corresponding binding processing to generate event stream topology information, and storing the generated event stream topology information to an event resource warehouse;
and issuing the strategy and/or the routing rule generated by the event stream topology information to a control plane.
3. The telecommunication charging method according to claim 1, wherein said receiving a service request issued by a microservice of any of said event-driven computing architectures, and submitting the service request to said event grid storage, comprises the specific steps of:
receiving a service request issued by the micro-service of any event-driven computing architecture, submitting the service request to a corresponding sidecar agent, and forwarding the service request by the sidecar agent according to a control strategy and/or a routing rule provided by a control plane;
and acquiring the service request forwarded by the sidecar agent, and importing the service request into a storage plane for storage.
4. The telecommunication charging method according to claim 1, wherein the receiving one or more subscription requests generated by the microservice of the event-driven computing architecture, submitting the event grid to invoke the storage service according to the control policy and/or the routing rule, and distributing the storage service to the microservice of the event-driven computing architecture issuing the subscription request for service execution, specifically includes:
receiving one or more subscription requests generated by the micro-service of the event-driven computing architecture, and submitting the one or more subscription requests to corresponding side car agents, wherein the side car agents forward the subscription requests according to a control strategy and/or a routing rule provided by a control plane;
obtaining the subscription request forwarded by the sidecar agent, submitting the subscription request to a storage plane for inquiring and calling a corresponding service request, and sending the service request back to the sidecar agent for forwarding;
and acquiring the service request forwarded by the sidecar agency, and distributing the service request to one or more event-driven computing architecture microservices generating subscription requests to execute services.
5. The telecommunications charging method of claim 1, wherein the event-driven computing architecture includes an event processing engine that supports EventLoop, Commander and eventcaler modes of operation.
6. The telecommunications billing method of claim 5, wherein the event processing engine operates in asynchronous thread pool mode.
7. The telecommunication charging method according to claim 1, wherein said receiving a service request issued by a microservice of any of said event-driven computing architectures specifically comprises:
acquiring a service request issued by an external application, submitting the service request to an event gateway for data conversion, accessing the converted service request to a sidecar agent corresponding to the event gateway by the event gateway, and forwarding the service request to a storage plane by the sidecar agent according to a control strategy and/or a routing rule;
acquiring data of an external storage medium, submitting the data to a source connector for data conversion, forwarding a converted service request through the sidecar agent deployed on the source connector, and submitting the converted service request to the storage plane;
and acquiring a service request generated by the timing trigger of the user-defined event source, forwarding the service request through the sidecar agent deployed in the user-defined event source, and submitting the service request to the storage plane.
8. The telecommunication charging method according to claim 1, wherein the event-driven computing architecture comprises a Sink connector for obtaining data from the event grid, and the Sink connector exports data to different external storage media through a data conversion rule.
9. The telecommunication charging method according to claim 1, wherein before the microservice distributed to the event-driven computing architecture issuing the subscription request for service execution, the event management platform manages the event grid in real time, specifically including:
and acquiring the flow data of the event grid, submitting the flow data to the event management platform for management, and realizing service statistics.
10. A telecommunications charging distributed computing system based on an event driven architecture, comprising:
the strategy acquisition module is used for acquiring application list data and event message definition list data of the event-driven computing architecture, submitting the application list data and the event message definition list data to an event management platform for processing and generating a control strategy and/or a routing rule, and issuing the control strategy and/or the routing rule to an event grid for execution;
the request issuing module is used for receiving a service request issued by the micro-service of any event-driven computing architecture and submitting the service request to the event grid for storage;
the request acquisition module is used for receiving one or more subscription requests generated by the micro-service of the event-driven computing architecture, submitting the event grid to call the storage service according to a control strategy and/or a routing rule, and distributing the storage service to the micro-service of the event-driven computing architecture issuing the subscription request to execute the service.
11. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, carries out the steps of a telecommunication charging method according to any one of claims 1 to 9.
12. A terminal, characterized in that the terminal comprises:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the steps of a telecommunications billing method according to any of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111399815.8A CN114615096B (en) | 2021-11-19 | 2021-11-19 | Event-driven architecture-based telecommunication charging method, system and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111399815.8A CN114615096B (en) | 2021-11-19 | 2021-11-19 | Event-driven architecture-based telecommunication charging method, system and related equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114615096A true CN114615096A (en) | 2022-06-10 |
| CN114615096B CN114615096B (en) | 2024-03-08 |
Family
ID=81857772
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111399815.8A Active CN114615096B (en) | 2021-11-19 | 2021-11-19 | Event-driven architecture-based telecommunication charging method, system and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114615096B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115412383A (en) * | 2022-08-25 | 2022-11-29 | 中国工商银行股份有限公司 | Charging method, device, node, system and medium for containerized cloud computing resources |
| CN116155686A (en) * | 2023-01-30 | 2023-05-23 | 浪潮云信息技术股份公司 | Method for judging node faults in cloud environment |
| CN116319951A (en) * | 2022-08-31 | 2023-06-23 | 京东科技信息技术有限公司 | Data processing method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040255025A1 (en) * | 2003-06-13 | 2004-12-16 | Giuseppe Ricagni | Event based charging in a communications system |
| US20120275300A1 (en) * | 2009-11-13 | 2012-11-01 | Telefonaktiebolaget L M Ericsson (Publ) | Service event trigger |
| US20170163431A1 (en) * | 2014-06-06 | 2017-06-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Notification of Network Events Relevant for Policy and Charging Decisions |
| CN107819590A (en) * | 2016-09-14 | 2018-03-20 | 华为技术有限公司 | A kind of methods, devices and systems of charging |
| CN109951301A (en) * | 2017-12-21 | 2019-06-28 | 电信科学技术研究院 | A kind of tactful and billing control method and equipment |
| CN110943971A (en) * | 2019-10-17 | 2020-03-31 | 亚信科技（中国）有限公司 | Event service processing method and system |
-
2021
- 2021-11-19 CN CN202111399815.8A patent/CN114615096B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040255025A1 (en) * | 2003-06-13 | 2004-12-16 | Giuseppe Ricagni | Event based charging in a communications system |
| US20120275300A1 (en) * | 2009-11-13 | 2012-11-01 | Telefonaktiebolaget L M Ericsson (Publ) | Service event trigger |
| US20170163431A1 (en) * | 2014-06-06 | 2017-06-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Notification of Network Events Relevant for Policy and Charging Decisions |
| CN107819590A (en) * | 2016-09-14 | 2018-03-20 | 华为技术有限公司 | A kind of methods, devices and systems of charging |
| CN109951301A (en) * | 2017-12-21 | 2019-06-28 | 电信科学技术研究院 | A kind of tactful and billing control method and equipment |
| CN110943971A (en) * | 2019-10-17 | 2020-03-31 | 亚信科技（中国）有限公司 | Event service processing method and system |
Non-Patent Citations (1)
| Title |
|---|
| 史鹏利;李明生;刘亚玲;: "基于信令消息的移动分组业务计费策略研究与应用", 电信技术, no. 10, 25 October 2018 (2018-10-25) * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115412383A (en) * | 2022-08-25 | 2022-11-29 | 中国工商银行股份有限公司 | Charging method, device, node, system and medium for containerized cloud computing resources |
| CN116319951A (en) * | 2022-08-31 | 2023-06-23 | 京东科技信息技术有限公司 | Data processing method and device |
| CN116155686A (en) * | 2023-01-30 | 2023-05-23 | 浪潮云信息技术股份公司 | Method for judging node faults in cloud environment |
| CN116155686B (en) * | 2023-01-30 | 2024-05-31 | 浪潮云信息技术股份公司 | Method for judging node faults in cloud environment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114615096B (en) | 2024-03-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114615096B (en) | Event-driven architecture-based telecommunication charging method, system and related equipment | |
| CN109889551B (en) | Method for accessing intelligent hardware to Internet of things cloud platform | |
| Albano et al. | Message-oriented middleware for smart grids | |
| CN112968943B (en) | Electric power is platform in coordination | |
| CN110716744A (en) | Data stream processing method, system and computer readable storage medium | |
| CN112511218B (en) | Satellite ground station monitoring system based on microservice | |
| CN110795486A (en) | Micro-service platform | |
| CN101808051B (en) | Application integration gateway and control method thereof | |
| CN103023857B (en) | A kind of method and system of information resources remote deployment | |
| CN105577446B (en) | Lightweight embedded network management system and method | |
| CN111885439B (en) | Optical network integrated management and duty management system | |
| CN102271162A (en) | Platform as a service (PAAS)-cloud-based telecommunication comprehensive service platform system and using method | |
| CN102903046A (en) | Real-time car pooling system for mobile terminal | |
| CN104980525A (en) | Pervasive mobile computing frame based on state middleware | |
| CN110287266A (en) | A kind of distributed system and data processing method | |
| CN114189274A (en) | Satellite ground station monitoring system based on microservice | |
| CN108900314A (en) | A kind of the number of request charging method and device of network acceleration service | |
| CN116755799A (en) | Service arrangement system and method | |
| CN102904739A (en) | Method for realizing event transmission and common information model (CIM) server | |
| CN101557382A (en) | Professional ability resource management system and professional ability resource access management method | |
| CN104462235A (en) | Internet of Things general event service mechanism based on Restful Web Service | |
| CN112416980A (en) | Data service processing method, device and equipment | |
| Dangi et al. | A novel hybrid deep learning approach for 5G network traffic control and forecasting | |
| Li et al. | Online Service Request Duplicating for Vehicular Applications | |
| Tang et al. | An adaptive model of service composition based on policy driven and multi-agent negotiation |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |