CN102006245A - Date exchanging and sharing platform - Google Patents

Date exchanging and sharing platform Download PDF

Info

Publication number
CN102006245A
CN102006245A CN 201010582808 CN201010582808A CN102006245A CN 102006245 A CN102006245 A CN 102006245A CN 201010582808 CN201010582808 CN 201010582808 CN 201010582808 A CN201010582808 A CN 201010582808A CN 102006245 A CN102006245 A CN 102006245A
Authority
CN
China
Prior art keywords
message
data service
service bus
end adapter
data
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
Application number
CN 201010582808
Other languages
Chinese (zh)
Other versions
CN102006245B (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.)
Chongqing Adtech Science & Technology Co Ltd
Original Assignee
Chongqing Adtech Science & Technology 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 Chongqing Adtech Science & Technology Co Ltd filed Critical Chongqing Adtech Science & Technology Co Ltd
Priority to CN 201010582808 priority Critical patent/CN102006245B/en
Publication of CN102006245A publication Critical patent/CN102006245A/en
Application granted granted Critical
Publication of CN102006245B publication Critical patent/CN102006245B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Abstract

The invention discloses a date exchanging and sharing platform, which comprises a data service bus employing a message mechanism to achieve cooperation between a heterogeneous system and internetwork applications, wherein the data service bus comprises a message service endpoint connecting the applications through an interface to the data service bus to send and receive messages so that the data service bus is transparent to the application system, a message assembly processing the data service bus messages, a message front end adaptor connecting applications through different protocols to the data service bus so as to send and receive messages, and a message rear end adaptor enabling the data service bus to access applications of the different protocols. In the invention, for each data switching node, required data can be acquired only by interacting with the data service bus without mutual connection and access. Bottom realization and memory mechanism of the whole data sharing and exchange are transparent to each application node.

Description

A kind of exchanges data and shared platform
Technical field
The present invention relates to a kind of exchanges data and shared system.
Background technology
The data of modern enterprise are more and more, though the data between each different departments can be shared, exist following point:
The file transfer problem can shared data but can not sharing functionality, and lacks timeliness, and the asynchronous possibility of data is bigger.
The shared data bank problem can shared data but can not sharing functionality, and all are used and database is coupled, and database is a performance bottleneck.
The remote procedure call problem, energy sharing functionality and cooperation behavior are real-time but call, and be synchronous, the application coupling is too big.
Summary of the invention
The purpose of this invention is to provide a kind of to using node exchanges data and shared platform transparent, that use message mechanism.
To achieve these goals, by the following technical solutions:
A kind of exchanges data and shared platform is characterized in that: described data and shared platform comprise:
Data Service Bus (DSB): use message mechanism to finish cooperation between the application of heterogeneous system and across a network;
Described Data Service Bus comprises:
Messenger service end points: application is connected to Data Service Bus by interface sends and receive message, make Data Service Bus transparent to the application system;
Message components: data service bus message is handled;
End adapter before the message: by different agreements types of applications is connected to Data Service Bus, sends and receive message with this;
End adapter after the message: make Data Service Bus possess the ability that all kinds of different agreements of visit are used.
Described message components comprises:
Message router: message realizes the selection of passage by the routing rule of message router;
Message filter: message realizes the message selection by the filtering rule of message filter, filters out unwanted message;
Message transformer: message realizes the conversion of different data format between different system by the transformation rule of message transformer;
The message decomposer: message is decomposed into related a plurality of message to message by the message decomposer, thereby finishes the different disposal of application to the different components of message;
Message aggregator: independent and relevant message offers the application processing by message aggregator thereby form a complete message;
Message is reset device: unordered but relevant message is reset to think highly of by message and is newly reverted to correct order;
The message specification device: will be semantically the conversion of the different message of equivalence but form by message specification device performance specification form;
Message delayer: message is made delay process by the message delayer to message;
The message coupler: message can send to the major-minor passage by the message coupler, so that message is monitored or debugged;
The message flow manager: message can realize the mutual of complicated rapid message of multistep and application by workflow management by the message flow manager;
The message safety assembly: message is carried out the necessary security authentication by the message safety assembly.
End adapter comprises before the described message:
End adapter before the file: realize regularly reading file and being converted to message sending to Data Service Bus from file;
End adapter before the FTP: realize regularly reading file and being converted to message sending to Data Service Bus from ftp server;
End adapter before the mail: realize regularly reading mail and being converted to message sending to Data Service Bus from mail server.
End adapter before the HTTP: Data Service Bus is externally exposed as the HTTP service, provide application that the data service bus is made the http protocol connection request;
End adapter before the JDBC: realize regularly operating from the database server reading of data and being converted to message sending to Data Service Bus by Jdbc;
End adapter before the IBATIS: realize regularly operating from the database server reading of data and being converted to message sending to Data Service Bus by Ibatis;
End adapter before the WebService: Data Service Bus is externally exposed as the WebService service, provide application that the data service bus is made the WebService call request;
End adapter before the Caucho: Data Service Bus is externally exposed as Hessian or Burlap service, provide application that the data service bus is made service invocation request.
End adapter comprises after the described message:
End adapter behind the file: realize the message of Data Service Bus is write specified folder with document form;
End adapter behind the FTP: realize the message of Data Service Bus is write ftp server with document form;
End adapter behind the mail: realize the message of Data Service Bus is write mail server with the mail form;
End adapter behind the HTTP: the visit that the HTTP that the realization Data Service Bus provides the application system serves;
End adapter behind the JDBC: realize the visit of the database service that Data Service Bus provides the application system by JDBC;
End adapter behind the IBATIS: realize the visit of the database service that Data Service Bus provides application by IBATIS;
End adapter behind the WebService: the visit that the WebService that the realization Data Service Bus provides the application system serves;
End adapter behind the Caucho: realize the Hessian that Data Service Bus provides the application system or the visit of Burlap service.
The invention enables each data exchange node only need carry out alternately, just can not get access to needed data and do not need to interconnect visit with Data Service Bus.The bottom layer realization of whole data sharing and exchange and memory mechanism are transparent to each application node.This structure coupling is low, and is easy to expand to hierarchical structure, is configured to multistage data exchange structure, to support wider wide area scheme.
Embodiment
The present invention is described further below by specific embodiment:
If application system A and application system B and application system C are the systems of three standalone features, and each free different programming language realizes, application system A will select to call same service or the synchrodata that application system B or application system C provide according to different conditions now.
1, application system A and Data Service Bus (DSB) is mutual:
The purpose that Data Service Bus exists is exactly to realize the decoupling zero of application system A and application system B and application system C, that is to say application system A only and Data Service Bus mutual, it usefulness know the existence of application system B and application system C.End adapter just begins to have played a role before the messenger service end points of Data Service Bus and the message like this.
(1) end adapter effect before messenger service end points and the message:
If we can know the source code of application system A fully, for service call, the messenger service end points is exactly best integration mode so, by the messenger service end points, calling directly by dynamic proxy of application system A docking port is converted on the passage that message sends to DSB, and these conversions are transparent to using the A of system fully.Secondly we also can be by same service that application system B or application system C are provided by end adapter (HttpInAdapter before the message, CauchoInAdapter, WebServiceInAdapter) DSB is exposed as Http Service, Caucho Service or WebService.Application system A just is easy to DSB mutual like this.
If we can not know the source code of application system A fully, for synchrodata, end adapter (FileInAdapter) before the file in the end adapter before the message so, end adapter (FTPInAdapter) before the FTP, end adapter (MailInAdapter) provides the integration mode of file transfers form before the mail, the data of application system A are converted to message send to Data Service Bus, finally realize application system B or application system C data sync.
If application system A provides the database access authority to us, for synchrodata, application system A database data can be operated and obtain to the preceding end adapter of end adapter or IBATIS just before the JDBC so, be converted to message and send to Data Service Bus, finally realize application system B or application system C data sync.
Synchronous and asynchronous strategy:
Data Service Bus (DSB) is based on the realization of message mechanism, and the high reliability of transmitting is provided, and can provide synchronous or asynchronous calling for application system A, and asynchronous system can improve the concurrent access ability of application system A greatly.
But the assembly of Data Service Bus flexible combination:
After end adapter was converted to the passage that message sends to Data Service Bus (DSB) before the data of application system A are by message, we just can make up different assemblies according to concrete application scenarios, and various like this message components just begin to have played a role.
Message filter:
If the message that application system A sends on the passage of Data Service Bus need filter out the message that some do not satisfy condition, can select different message filters by concrete filtering rule so, as the message header filter, the type of message filter, Xpath resolves message body filter, method call filter etc.
Message router:
Because application system A will select to call same service or the synchrodata that application system B or application system C provide according to different condition, our different selection conditions that just need provide according to application system A is as routing rule so, makes the message after filtering from top message filter be sent to the different passages that are associated with the B of system or the C of system by message router.Can select different message routers by the alternative condition that concrete message is carried, as the message header router, the type of message router, Xpath resolves the message body router, the method call router, the static table router that receives dynamically receives table router etc.
Message transformer:
Because application system A and application system B and application system C are the systems of three standalone features, so after the correct channel selecting of top router realization, the data format that can not guarantee them is identical, at this moment we just need add message transformer after route exports different passages, Data Format Transform application system A becomes the required data format of application system B, and the Data Format Transform of another application system A becomes the required data format of application system C.
Can select different message transformer by the form of concrete message: the message header expander, the message body expander, object changes the XML transducer, and XML changes object transducer, XSLT message transformer, method call transducer.
If the message of application system A and application system B and application system C in equivalence semantically but form is different, so also can be finished message conversion by the message specification device.
Message chain type assembly:
As can be seen from the above, message has been passed through: message filter-message router-message transformer, because our message chain type assembly can link some linkable assemblies, and message router can only be as the connector assembly of chain, therefore we can be embodied as the chain type assembly to message filter-message router and use, number of channels can not only be saved like this, also certain efficient can be improved.
The message decomposer:
Here, if supposing the message that application system A sends on the passage of Data Service Bus is made up of different two parts, each part is handled (as the different order items on the order by application system B or application system C respectively, each different order item can be handled by different system), so just can resolve into the multiple messages that is mutually related to same message and send again by the message decomposer.Every message is by different modes and system handles.
Message aggregator:
Opposite with the effect of message decomposer, the message that is mutually related is polymerized to a full message.So just can aggregate into a results messages to the result of each bar related news of application system B above-mentioned or application system C processing again, so that subsequent treatment.
The message flow manager:
If application system A calls application system B or application system C has succession, perhaps need more complicated layout, we just can use the message flow manager, handle message on the passage that application system A sends to Data Service Bus according to workflow thought, equally can with message filter or message router, message transformer collaborative work.
Message delayer: be used for the again delivery delay function of message, can alleviate the load of Data Service Bus like this owing to network failure.
2, Data Service Bus and application system B or application system C's is mutual:
Application system B or application system C may provide different COS, and Data Service Bus is mutual with it, and at this moment, end adapter just begins to have played a role after the message.
End adapter effect after the message:
For service call, if the service that application system B or application system C expose is the HTTP mode, WebService mode or Caucho mode, we can use end adapter (HttpOutAdapter) behind the HTTP, and end adapter (CauchoOutAdapter) is mutual with it behind end adapter behind the WebService (WebServiceOutAdapter) or the Caucho.
For synchrodata, end adapter (FileOutAdapter) behind the file in the end adapter after the message so, end adapter behind the FTP (FTPOutAdapter), end adapter behind the mail (MailOutAdapter) provides the integration mode of file transfers form, the message of Data Service Bus is write file and ftp server, and mail server, to reach the different system data sharing.
If application system B or application system C provide the database access authority to us, for synchrodata, so behind the JDBC behind end adapter (JdbcInAdapter) or the IBATIS end adapter (IbatisInAdapter) just can finish to using the database manipulation of B of system or application system C, to reach the different system data sharing.
Data Service Bus message is delivered strategy again:
Because end adapter is corresponding after the message may be because the failure of faults such as network with calling of system, need to deliver again strategy and guarantee after the message that the end adapter correspondence is with the reliability of calling of system.This is quite useful under asynchronous system, so just needn't worry the unreliable of network.
The present invention is that core solves exchanges data and sharing problem with the message mechanism, and the entire process process is short and sweet, and is easy in understanding and using, and is the integration platform for heterogeneous information sources of lightweight.

Claims (4)

1. exchanges data and shared platform, it is characterized in that: described data and shared platform comprise:
Data Service Bus (DSB): use message mechanism to finish cooperation between the application of heterogeneous system and across a network;
Described Data Service Bus comprises:
Messenger service end points: application is connected to Data Service Bus by interface sends and receive message, make Data Service Bus transparent to the application system;
Message components: data service bus message is handled;
End adapter before the message: by different agreements types of applications is connected to Data Service Bus, sends and receive message with this;
End adapter after the message: make Data Service Bus possess the ability that all kinds of different agreements of visit are used.
2. exchanges data as claimed in claim 1 and shared platform is characterized in that: described message components comprises:
Message router: message realizes the selection of passage by the routing rule of message router;
Message filter: message realizes the message selection by the filtering rule of message filter, filters out unwanted message;
Message transformer: message realizes the conversion of different data format between different system by the transformation rule of message transformer;
The message decomposer: message is decomposed into related a plurality of message to message by the message decomposer, thereby finishes the different disposal of application to the different components of message;
Message aggregator: independent and relevant message offers the application processing by message aggregator thereby form a complete message;
Message is reset device: unordered but relevant message is reset to think highly of by message and is newly reverted to correct order;
The message specification device: will be semantically the conversion of the different message of equivalence but form by message specification device performance specification form;
Message delayer: message is made delay process by the message delayer to message;
The message coupler: message can send to the major-minor passage by the message coupler, so that message is monitored or debugged;
The message flow manager: message can realize the mutual of complicated rapid message of multistep and application by workflow management by the message flow manager;
The message safety assembly: message is carried out the necessary security authentication by the message safety assembly.
3. exchanges data as claimed in claim 2 and shared platform is characterized in that: end adapter comprises before the described message:
End adapter before the file: realize regularly reading file and being converted to message sending to Data Service Bus from file;
End adapter before the FTP: realize regularly reading file and being converted to message sending to Data Service Bus from ftp server;
End adapter before the mail: realize regularly reading mail and being converted to message sending to Data Service Bus from mail server;
End adapter before the HTTP: Data Service Bus is externally exposed as the HTTP service, provide application that the data service bus is made the http protocol connection request;
End adapter before the JDBC: realize regularly operating from the database server reading of data and being converted to message sending to Data Service Bus by Jdbc;
End adapter before the IBATIS: realize regularly operating from the database server reading of data and being converted to message sending to Data Service Bus by Ibatis;
End adapter before the WebService: Data Service Bus is externally exposed as the WebService service, provide application that the data service bus is made the WebService call request;
End adapter before the Caucho: Data Service Bus is externally exposed as Hessian or Burlap service, provide application that the data service bus is made service invocation request.
4. exchanges data as claimed in claim 3 and shared platform is characterized in that: end adapter comprises after the described message:
End adapter behind the file: realize the message of Data Service Bus is write specified folder with document form;
End adapter behind the FTP: realize the message of Data Service Bus is write ftp server with document form;
End adapter behind the mail: realize the message of Data Service Bus is write mail server with the mail form;
End adapter behind the HTTP: the visit that the HTTP that the realization Data Service Bus provides the application system serves;
End adapter behind the JDBC: realize the visit of the database service that Data Service Bus provides the application system by JDBC;
End adapter behind the IBATIS: realize the visit of the database service that Data Service Bus provides application by IBATIS;
End adapter behind the WebService: the visit that the WebService that the realization Data Service Bus provides the application system serves;
End adapter behind the Caucho: realize the Hessian that Data Service Bus provides the application system or the visit of Burlap service.
CN 201010582808 2010-12-10 2010-12-10 Date exchanging and sharing platform Active CN102006245B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN 201010582808 CN102006245B (en) 2010-12-10 2010-12-10 Date exchanging and sharing platform

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN 201010582808 CN102006245B (en) 2010-12-10 2010-12-10 Date exchanging and sharing platform

Publications (2)

Publication Number Publication Date
CN102006245A true CN102006245A (en) 2011-04-06
CN102006245B CN102006245B (en) 2013-01-30

Family

ID=43813331

Family Applications (1)

Application Number Title Priority Date Filing Date
CN 201010582808 Active CN102006245B (en) 2010-12-10 2010-12-10 Date exchanging and sharing platform

Country Status (1)

Country Link
CN (1) CN102006245B (en)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103763344A (en) * 2013-12-31 2014-04-30 湖南大唐先一科技有限公司 General data sharing platform based on service bus and message drive mode
CN107135198A (en) * 2017-03-28 2017-09-05 深圳市卓讯信息技术有限公司 A kind of method for interchanging data and device based on ETL technology synergy multi-communication agreements
CN107229587A (en) * 2017-06-09 2017-10-03 华东师范大学 A kind of method of work for the service bus platform for accessing polymorphic type groupware
CN107330089A (en) * 2017-07-04 2017-11-07 中国联合网络通信集团有限公司 Across a network structural data collection system
CN108462702A (en) * 2017-02-17 2018-08-28 罗伯特·博世有限公司 Method and apparatus for running the control device in bus
CN108614821A (en) * 2016-12-09 2018-10-02 中国地质调查局发展研究中心 Geologic information interconnection mutually looks into system
CN109088881A (en) * 2018-09-12 2018-12-25 杭州趣链科技有限公司 A kind of shared platform chain and method for interchanging data for realizing cross-platform data exchange
CN110086759A (en) * 2013-10-14 2019-08-02 阿里巴巴集团控股有限公司 A kind of method and apparatus for realizing message transmission between heterogeneous system
CN110995791A (en) * 2019-11-18 2020-04-10 上海联众网络信息有限公司 Interactive medical information management method and system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1411242A (en) * 2001-09-28 2003-04-16 华为技术有限公司 Broad band intelligent net access service system and its realizing method
WO2004004248A1 (en) * 2002-06-26 2004-01-08 Nokia Corporation Programmable scheduling for ip routers
CN101083592A (en) * 2006-06-01 2007-12-05 上海贝尔阿尔卡特股份有限公司 Bandwidth sharing method for base station system in chain-type topological structure and base station transceiver station
CN101335683A (en) * 2007-06-26 2008-12-31 上海岱嘉医学信息系统有限公司 Medical image data sharing method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1411242A (en) * 2001-09-28 2003-04-16 华为技术有限公司 Broad band intelligent net access service system and its realizing method
WO2004004248A1 (en) * 2002-06-26 2004-01-08 Nokia Corporation Programmable scheduling for ip routers
CN101083592A (en) * 2006-06-01 2007-12-05 上海贝尔阿尔卡特股份有限公司 Bandwidth sharing method for base station system in chain-type topological structure and base station transceiver station
CN101335683A (en) * 2007-06-26 2008-12-31 上海岱嘉医学信息系统有限公司 Medical image data sharing method

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110086759B (en) * 2013-10-14 2021-11-05 创新先进技术有限公司 Method and device for realizing message transmission between heterogeneous systems
CN110086759A (en) * 2013-10-14 2019-08-02 阿里巴巴集团控股有限公司 A kind of method and apparatus for realizing message transmission between heterogeneous system
CN103763344A (en) * 2013-12-31 2014-04-30 湖南大唐先一科技有限公司 General data sharing platform based on service bus and message drive mode
CN108614821A (en) * 2016-12-09 2018-10-02 中国地质调查局发展研究中心 Geologic information interconnection mutually looks into system
CN108614821B (en) * 2016-12-09 2020-10-13 中国地质调查局发展研究中心 Geological data interconnection and mutual-checking system
CN108462702A (en) * 2017-02-17 2018-08-28 罗伯特·博世有限公司 Method and apparatus for running the control device in bus
CN107135198A (en) * 2017-03-28 2017-09-05 深圳市卓讯信息技术有限公司 A kind of method for interchanging data and device based on ETL technology synergy multi-communication agreements
CN107229587A (en) * 2017-06-09 2017-10-03 华东师范大学 A kind of method of work for the service bus platform for accessing polymorphic type groupware
CN107330089B (en) * 2017-07-04 2020-06-23 中国联合网络通信集团有限公司 Cross-network structured data collection system
CN107330089A (en) * 2017-07-04 2017-11-07 中国联合网络通信集团有限公司 Across a network structural data collection system
CN109088881A (en) * 2018-09-12 2018-12-25 杭州趣链科技有限公司 A kind of shared platform chain and method for interchanging data for realizing cross-platform data exchange
CN109088881B (en) * 2018-09-12 2020-11-03 杭州趣链科技有限公司 Shared chain platform for realizing cross-platform data exchange and data exchange method
CN110995791A (en) * 2019-11-18 2020-04-10 上海联众网络信息有限公司 Interactive medical information management method and system
CN110995791B (en) * 2019-11-18 2023-06-06 上海联众网络信息股份有限公司 Interactive medical information management method and system

Also Published As

Publication number Publication date
CN102006245B (en) 2013-01-30

Similar Documents

Publication Publication Date Title
CN102006245B (en) Date exchanging and sharing platform
US9304836B2 (en) Bridging data distribution services domains based on discovery data
US7949704B2 (en) Administration of a broker-based publish/subscribe messaging system
CN100454905C (en) Method for passing through network address switching
US20020143644A1 (en) Connection tool for connecting analytical applications to electronic document sources
CN102025650A (en) Message processing system and message processing method of enterprise service bus
CN104243496A (en) Software defined network cross-domain security agent method and software defined network cross-domain security agent system
JP2009510811A5 (en)
CN102325186A (en) Remote service calling method and system
CN101197736A (en) Wireless net member equipment monitoring system and monitoring method thereof
CN102938770A (en) Method for realizing uniform interface for multi-protocol messages and related device and system
US7934218B2 (en) Interprocess communication management using a socket layer
CN104468299A (en) Enterprise service bus system based on user rule
CN101115010A (en) Method for extending security system, security system and security processing equipment
KR101890310B1 (en) Adapter for message queuing telemetry transport protocol interworking and data exchange system employing the same
CN111901384B (en) System, method, electronic device and readable storage medium for processing message
CN101795237A (en) Workflow integration method and device based on data exchange
CN111866157B (en) Cloud service gateway and cloud service internal and external request format conversion method
CN101860544A (en) Transmitting system and method of session initiation protocol message
US7376748B1 (en) Data delivering system
EP2252032B1 (en) Message adaptation system for system integration
CN113419843B (en) NAS-based distributed resource management system
JP2888282B2 (en) Data communication method and data communication system
KR20090000022A (en) Apparatus and method for enhancing reusability of software componentand and its method for processing using the same and record media recorded program for realizing the same
US10069762B1 (en) Group based multicast in networks

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
PE01 Entry into force of the registration of the contract for pledge of patent right

Denomination of invention: Date exchanging and sharing platform

Effective date of registration: 20131203

Granted publication date: 20130130

Pledgee: Chongqing Three Gorges bank Limited by Share Ltd South Bank branch

Pledgor: Chongqing Adtech Science & Technology Co., Ltd.

Registration number: 2013990000920

PLDC Enforcement, change and cancellation of contracts on pledge of patent right or utility model
PC01 Cancellation of the registration of the contract for pledge of patent right

Date of cancellation: 20150410

Granted publication date: 20130130

Pledgee: Chongqing Three Gorges bank Limited by Share Ltd South Bank branch

Pledgor: Chongqing Adtech Science & Technology Co., Ltd.

Registration number: 2013990000920

PLDC Enforcement, change and cancellation of contracts on pledge of patent right or utility model
PE01 Entry into force of the registration of the contract for pledge of patent right

Denomination of invention: Date exchanging and sharing platform

Effective date of registration: 20150527

Granted publication date: 20130130

Pledgee: Chongqing Sanxia bank Limited by Share Ltd New District Branch

Pledgor: Chongqing Adtech Science & Technology Co., Ltd.

Registration number: 2015990000417

PLDC Enforcement, change and cancellation of contracts on pledge of patent right or utility model
PC01 Cancellation of the registration of the contract for pledge of patent right

Date of cancellation: 20151030

Granted publication date: 20130130

Pledgee: Chongqing Sanxia bank Limited by Share Ltd New District Branch

Pledgor: Chongqing Adtech Science & Technology Co., Ltd.

Registration number: 2015990000417

PLDC Enforcement, change and cancellation of contracts on pledge of patent right or utility model