CN101634955A - Method for processing event in radio frequency identification system and reader management terminal (RMT) - Google Patents
Method for processing event in radio frequency identification system and reader management terminal (RMT) Download PDFInfo
- Publication number
- CN101634955A CN101634955A CN200910168824A CN200910168824A CN101634955A CN 101634955 A CN101634955 A CN 101634955A CN 200910168824 A CN200910168824 A CN 200910168824A CN 200910168824 A CN200910168824 A CN 200910168824A CN 101634955 A CN101634955 A CN 101634955A
- Authority
- CN
- China
- Prior art keywords
- incident
- resource
- event
- pond
- lock
- 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
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention relates to the field of radio frequency identification technologies, in particular to a method for processing events in a radio frequency identification system and a reader management terminal (RMT). Through the cooperative work of an event filtering thread and an event processing thread and the unified management of an event manager to events, the invention enables the RMT to process resource-unconstrained events and various resource-constrained events simultaneously. The invention also introduces the concept of a resource lock to enable the RMT to sufficiently utilize limited resources to quickly process various resource-constrained events as many as possible, thereby improving the integral performance of the RMT in the radio frequency identification system.
Description
Technical field
The present invention relates to the REID field, relate in particular to the method and the Remote client of event handling in a kind of radio-frequency recognition system.
Background technology
RFID (Radio Frequency Identification, radio-frequency (RF) identification) is a kind of contactless automatic identification technology, and by the automatic recognition objective object of radiofrequency signal and obtain related data, identification work need not manual intervention, can work in rugged surroundings.RMT in the rfid system (Remoting Maintenance Teminal, Remote client terminal) is the responsible terminal that the reader of networking is managed and safeguards, adopts the b/s structure.RMT can manage the variety classes of networking, the reader of different model simultaneously, also supports multi-client to visit simultaneously simultaneously.It is hundreds and thousands of that the quantity of networking reader can reach.
The handled incident relevant with reader operation of RMT is divided into resource-constrained incident and the not limited incident of resource.Resource-constrained incident is subdivided into dissimilar resource-constrained incidents according to the restriction of suffered dissimilar resources again.Here said resource is meant RMT server CPU processing power and network environment etc.Resource-constrained incident is meant the incident that influenced by various resource performance.For example, when a plurality of readers carry out the version down operation simultaneously, owing to be subjected to the such resource limit of processing power of the network bandwidth and RMT server CUP, and speed of download is slow, and user's ease for use is made a very bad impression.If but be the quantity that simple restriction can be carried out the reader of version download simultaneously, can bring disagreeableness sensation to the user again.
The problem that prior art exists is that RMT can not handle the resource-constrained incident of not limited incident of resource and number of different types simultaneously, and when handling resource-constrained incident, the problem that treatment effeciency is lower.Therefore, RMT need provide a kind of reliable, effective and efficient manner to carry out the concurrent processing of dissimilar incidents and scheduling, the high concurrency environment when the networking reader being managed to adapt to RMT, thus provide a close friend, easy-to-use office terminal for the user.
Summary of the invention
Fundamental purpose of the present invention is to provide the system and method for event handling in a kind of rfid system, be used to realize that RMT handles the not limited incident of resource and polytype resource-constrained incident simultaneously, and make full use of Limited resources and handle resource-constrained incident as much as possible as far as possible fast, promote the bulk treatment ability of RMT.
To achieve these goals, the invention provides the method for event handling in a kind of radio-frequency recognition system, it is characterized in that, comprise the steps:
A, reader send to reader management terminal (RMT) with the operational order that the user initiates from the page; Reader management terminal (RMT) is that each reader is created an incident separately according to described operational order, and described event type comprises that resource is not limited and resource-constrained;
B, task manager are judged the type of described incident, if the not limited incident of resource, then put into pending incident pond, change state-event into armed state, while wake events processing threads also forwards step D to, if resource-constrained incident is then put into pre-incident pond, start the event filtering thread simultaneously;
C, event filtering thread are the resource-constrained incident Resources allocation lock in the pre-incident pond, and task manager will be assigned to the resource-constrained incident of resource lock and put into pending incident pond, start the event handling thread simultaneously;
D, event handling thread taking-up incident from pending incident pond is handled, and task manager adds described incident in the processing events pond, and this state-event changes to treatment state;
E, reader management terminal (RMT) send message to reader.
Further, among the described step C, also comprise step: whether the whole pre-incident of event filtering thread cycle criterion pond has incident, then is its application resource lock if having.
Further, among the described step C, also comprise step: whether the available resources lock is arranged in the event filtering thread cycle criterion resource lock, lock if any available resources, then event filter successfully is that described resource-constrained incident application is to resource lock, as no available resources lock, then event filtering thread block.
Further, after the described step e, also comprise step: the reader return messages are given reader management terminal (RMT), task manager is according to the event number in the reader return messages, finding corresponding event in the processing events pond, making described incident carry out the operation of return messages, judging whether described incident occupies resource lock, have then to discharge this resource lock and it is removed from the incident pond, do not have and then directly remove.
Further, after the described step e, also comprise step: start timer, when the time-out time of timer setting arrives, task manager judges whether described incident occupies resource lock, has then to discharge this resource lock and it is removed from the incident pond, does not have then directly to remove.
The present invention also provides a kind of reader management terminal (RMT), comprising: be used to deposit the pre-incident pond of resource-constrained incident, be used to the incident pond of depositing the resource lock pond of resource lock and being used to the incident of depositing; Also comprise event filtering thread, event handling thread and the task manager that is used to plan as a whole scheduling events; Wherein,
Reader management terminal (RMT) is that each reader is created an incident separately, and described event type comprises that resource is not limited and resource-constrained; Task manager is judged the type of described incident, if the not limited incident of resource is then put into pending incident pond, change state-event into armed state, the wake events processing threads if resource-constrained incident is then put into pre-incident pond, starts the event filtering thread simultaneously simultaneously; The event filtering thread is the resource-constrained incident Resources allocation lock in the pre-incident pond; Task manager will be assigned to the resource-constrained incident of resource lock and put into pending incident pond, start the event handling thread simultaneously; Event handling thread taking-up incident from pending incident pond is handled, and task manager adds described incident in the processing events pond, and this state-event changes to treatment state; Reader management terminal (RMT) sends message to reader.
Wherein, whether the event filtering thread also is used for the whole pre-incident of cycle criterion pond incident, then is its application resource lock if having.
Wherein, whether the event filtering thread also is used for the cycle criterion resource lock the available resources lock, and if any the available resources lock, then event filter successfully is that described resource-constrained incident application is to resource lock, as no available resources lock, then event filtering thread block.
Wherein, reader management terminal (RMT) send message to reader after the reader return messages to reader management terminal (RMT), task manager also is used for the event number according to the reader return messages, finding corresponding event in the processing events pond, make described incident carry out the operation of return messages, judge whether described incident occupies resource lock, have then to discharge this resource lock and it is removed not have and then directly remove from the incident pond.
Further, also comprise: timer, the time-out time that is used for when the timer setting arrives, and task manager judges whether described incident occupies resource lock, has then to discharge this resource lock and it is removed from the incident pond, does not have then directly to remove.
As from the foregoing, collaborative work by event filtering thread and event scheduling thread makes RMT not only can handle the resource-constrained incident of unrestricted quantity, and can make each resource-constrained incident when operation, obtain sufficient resources, thereby realize handling efficiently.Solve RMT because the treatment effeciency that the restriction of resource brings hangs down inferior problem, improved the high concurrent processing ability of RMT.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is a model synoptic diagram of the present invention;
Fig. 2 is the process flow diagram of a specific embodiment of the present invention.
Embodiment
Describe the present invention in detail with embodiment below with reference to the accompanying drawings.
The present invention is by the collaborative work of event filtering thread and these two threads of event handling thread, and task manager is to the unified management of incident, make RMT can handle the not limited incident of resource and various types of resource-constrained incident simultaneously, introduce the notion of " resource lock " simultaneously, make RMT can utilize Limited resources to handle dissimilar resource-constrained incident as much as possible apace fully." incident " of the present invention is abstract to the single job of a reader that RMT initiates.Incident has attribute such as event number, state-event, result and sends message to reader, handles the reader return messages, and functions such as time-out time and overtime task are set.Resource lock of the present invention is used for resource-constrained incident is controlled.
As shown in Figure 1, the pre-incident pond that is arranged at the RMT service end only is used to deposit the resource-constrained incident that all do not obtain resource lock, and the resource-constrained incident that can deposit in the pre-incident pond does not have restricted number.Pre-incident pond is actually an event queue, and the incident of wherein depositing has sequencing, adopts to arrive first and deposits the mechanism of getting earlier earlier.
After resource-constrained incident was added in the pre-incident pond, the event filtering thread was responsible for taking out resource-constrained incident from pre-incident pond, apply for the resource lock of respective type and distribute to this incident for it to the resource lock pond then.
The resource lock pond also is arranged on the RMT service end, and various types of resource locks can be deposited in the inside, to meet the different needs.The type of resource lock is classified according to limited resource, can be divided into the cpu resource lock, Internet resources lock, CPU Internet resources lock or the like.The type of every kind of resource lock is the resource-constrained incident of corresponding respective type all.The resource lock number of lock in the pond is limited, takes the mode of First come first served to obtain, resource lock quantity size setting according to resource is set.Resource lock has two states, is respectively idle condition and occupied state.The resource lock of idle condition can use, and the resource lock of occupied state can not use.
After resource-constrained incident has obtained the resource lock of respective type, be responsible for this incident is put into the incident pond by task manager.But incident all is defaulted as processing events in the incident pond, is responsible for taking-up incident from the incident pond by the event handling thread, incident is finished send a message to the operation of reader.When the reader return messages, incident will discharge resource lock, is about to the resource lock state and is made as the free time; Under the perhaps overtime situation, incident also will discharge resource lock.The essence in incident pond also is event queue, and its access mechanism is with pre-incident pond.
Be arranged in the incident pond of RMT service end and can deposit various types of incidents, comprise the not limited incident of resource-constrained incident or resource.Deposit the restriction of incident incalculability in the incident pond.Inside, incident pond is divided into two types pond, subevent again, is respectively pending incident pond and processing events pond.According to the different conditions of incident, deposit the incident of different conditions.What deposit in the wherein pending incident pond is the incident that is in armed state, and what deposited in the processing events pond is the incident of present state.About the state of incident, will describe in detail below.
Incident has 5 kinds of different states, is respectively init state, armed state, present state, treatment state and timeout mode.According to different state-events, task manager carries out different operational administratives to incident.When incident initially was created, its state was set to init state; When incident was put into pending incident pond by task manager, its state was set as armed state; When incident during by the event handling thread process, its state just is set as at treatment state, and when the reader return messages, incident is set as treatment state; If in official hour, reader is return messages not, and then incident is set as timeout mode.
As shown in Figure 2, the method realization flow figure that provides for one embodiment of the invention.This process flow diagram may further comprise the steps:
Step 201: the user initiates once operation to reader from the page.Operation this time both can be the operation of only a reader being carried out, and can be again the operation that a plurality of readers are carried out simultaneously;
Step 201:RMT service end is according to user's operation, the corresponding events corresponding that generates, by task manager resource-constrained incident is put into pre-incident pond, the not limited incident of resource is put into the incident pond, the quantity of the quantity of generation incident and user-selected reader is consistent, and promptly the RMT server is that each reader generates an incident separately;
Step 203: the event filtering thread starts, and this thread mainly is responsible for the incident of obtaining and is its Resources allocation lock from pre-task pool;
Step 204: whether the whole pre-incident of cycle criterion pond has incident, if then execution in step 205 is arranged; If there is not then execution in step 206;
Step 205: after resource-constrained incident was added in the pre-incident pond, wake events filtered thread;
Step 206: when not having incident in the pre-incident pond, the event filtering thread block is waken up when incident is added in the pre-incident pond;
Step 207: after the event filtering thread is waken up, go to take out in the pre-incident pond resource-constrained incident;
Step 208: judge in the pre-incident pond whether have resource-constrained incident, have then execution in step 209, do not have then execution in step 206;
Step 209: have resource-constrained incident in the pre-task pool, the event filtering thread removes resource lock pond application resource lock for it;
Step 210: judge the idling-resource lock that whether has respective type in the resource lock pond, if there is not then execution in step 211, if there is then execution in step 212;
Step 211: event filtering thread block and wake-up waiting, event filtering thread block when not having the idling-resource lock of respective type in the resource lock pond, and when respective type idling-resource lock is arranged in the resource lock pond, be waken up;
Step 212: task manager will obtain the incident of resource lock and put in the pending incident pond, start the event handling thread simultaneously;
Step 213: event handling thread block and wake-up waiting, when remaining processing events in the incident pond, the event handling thread is waken up, otherwise still blocks;
Step 214: the event handling thread obtains pending incident from pending incident pond.
Step 215: judge in the pending incident pond whether have pending incident, if exist, then execution in step 216, if there is not then execution in step 213;
Step 216: task manager removes this incident from pending incident pond, adds to simultaneously in the processing events pond, makes incident carry out the task of sending a message to reader then, and starts timer;
Step 217: reader return messages, reader return messages are asynchronous;
Step 218: task manager is finding events corresponding in the processing events pond according to the event number in the return messages, and makes incident carry out the operation of return messages;
Step 219: discharge the resource lock that this incident is occupied, execution in step 211 then;
Step 220: when the time-out time that is provided with arrives, timer begins to carry out task of timer;
Step 221: judging whether this incident occupies resource lock, is execution in step 219 then, otherwise execution in step 222;
Step 222: task manager is from the processing events pond deleting this incident.
The present invention proposes the unified method of handling of the resource-constrained incident of not limited incident of a kind of resource and polytype, be used to realize and guarantee the purpose that the high concurrency of all types of incidents makes all types of incidents efficiently be handled again, and then improved the overall performance of RMT in the radio-frequency recognition system.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have multiple change and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1, the method for event handling in a kind of radio-frequency recognition system is characterized in that, comprises the steps:
A, reader send to reader management terminal (RMT) with the operational order that the user initiates from the page; Reader management terminal (RMT) is that each reader is created an incident separately according to described operational order, and described event type comprises that resource is not limited and resource-constrained;
B, task manager are judged the type of described incident, if the not limited incident of resource, then put into pending incident pond, change state-event into armed state, while wake events processing threads also forwards step D to, if resource-constrained incident is then put into pre-incident pond, start the event filtering thread simultaneously;
C, event filtering thread are the resource-constrained incident Resources allocation lock in the pre-incident pond, and task manager will be assigned to the resource-constrained incident of resource lock and put into pending incident pond, start the event handling thread simultaneously;
D, event handling thread taking-up incident from pending incident pond is handled, and task manager adds described incident in the processing events pond, and this state-event changes to treatment state;
E, reader management terminal (RMT) send message to reader.
2, the method for event handling in the radio-frequency recognition system as claimed in claim 1 is characterized in that, among the described step C, also comprises step: whether the whole pre-incident of event filtering thread cycle criterion pond has incident, then is its application resource lock if having.
3, the method for event handling in the radio-frequency recognition system as claimed in claim 1, it is characterized in that, among the described step C, also comprise step: whether the available resources lock is arranged in the event filtering thread cycle criterion resource lock, lock if any available resources, then event filter successfully is that described resource-constrained incident application is to resource lock, as no available resources lock, then event filtering thread block.
4, the method for event handling in the radio-frequency recognition system as claimed in claim 1, it is characterized in that, after the described step e, also comprise step: the reader return messages are given reader management terminal (RMT), and task manager is finding corresponding event in the processing events pond according to the event number in the reader return messages, make described incident carry out the operation of return messages, judge whether described incident occupies resource lock, have then to discharge this resource lock and it is removed not have and then directly remove from the incident pond.
5, the method for event handling in the radio-frequency recognition system as claimed in claim 1, it is characterized in that, after the described step e, also comprise step: start timer, when the time-out time of timer setting arrives, task manager judges whether described incident occupies resource lock, has then to discharge this resource lock and it is removed from the incident pond, does not have then directly to remove.
6, a kind of reader management terminal (RMT) is characterized in that, comprising: be used to deposit the pre-incident pond of resource-constrained incident, be used to the incident pond of depositing the resource lock pond of resource lock and being used to the incident of depositing; Also comprise event filtering thread, event handling thread and the task manager that is used to plan as a whole scheduling events; Wherein,
Reader management terminal (RMT) is that each reader is created an incident separately, and described event type comprises that resource is not limited and resource-constrained; Task manager is judged the type of described incident, if the not limited incident of resource is then put into pending incident pond, change state-event into armed state, the wake events processing threads if resource-constrained incident is then put into pre-incident pond, starts the event filtering thread simultaneously simultaneously; The event filtering thread is the resource-constrained incident Resources allocation lock in the pre-incident pond; Task manager will be assigned to the resource-constrained incident of resource lock and put into pending incident pond, start the event handling thread simultaneously; Event handling thread taking-up incident from pending incident pond is handled, and task manager adds described incident in the processing events pond, and this state-event changes to treatment state; Reader management terminal (RMT) sends message to reader.
7, terminal according to claim 6 is characterized in that, whether the event filtering thread also is used for the whole pre-incident of cycle criterion pond incident, then is its application resource lock if having.
8, terminal according to claim 6, it is characterized in that, whether the event filtering thread also is used for the cycle criterion resource lock the available resources lock, lock if any available resources, then event filter successfully is that described resource-constrained incident application is to resource lock, as do not have available resources and lock then event filtering thread block.
9, terminal according to claim 6, it is characterized in that, reader management terminal (RMT) send message to reader after the reader return messages to reader management terminal (RMT), task manager also is used for the event number according to the reader return messages, finding corresponding event in the processing events pond, making described incident carry out the operation of return messages, judging whether described incident occupies resource lock, have then to discharge this resource lock and it is removed from the incident pond, do not have and then directly remove.
10, terminal according to claim 6 is characterized in that, also comprises: timer, be used for arriving when the time-out time of timer setting, task manager judges whether described incident occupies resource lock, has then to discharge this resource lock and it is removed from the incident pond, does not have then directly to remove.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200910168824 CN101634955B (en) | 2009-08-21 | 2009-08-21 | Method for processing event in radio frequency identification system and reader management terminal (RMT) |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200910168824 CN101634955B (en) | 2009-08-21 | 2009-08-21 | Method for processing event in radio frequency identification system and reader management terminal (RMT) |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101634955A true CN101634955A (en) | 2010-01-27 |
| CN101634955B CN101634955B (en) | 2013-01-09 |
Family
ID=41594152
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200910168824 Active CN101634955B (en) | 2009-08-21 | 2009-08-21 | Method for processing event in radio frequency identification system and reader management terminal (RMT) |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101634955B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102135907A (en) * | 2011-03-22 | 2011-07-27 | 曙光信息产业股份有限公司 | Alarm processing method of super-large scale cluster |
| CN104808913A (en) * | 2014-01-23 | 2015-07-29 | 腾讯科技（深圳）有限公司 | Event responding method and device |
| CN106547609A (en) * | 2015-09-18 | 2017-03-29 | 阿里巴巴集团控股有限公司 | A kind of event-handling method and equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080061943A1 (en) * | 2006-08-11 | 2008-03-13 | Ke-Li Wu | RFID systems and methods of operating the same in power-saving modes |
-
2009
- 2009-08-21 CN CN 200910168824 patent/CN101634955B/en active Active
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102135907A (en) * | 2011-03-22 | 2011-07-27 | 曙光信息产业股份有限公司 | Alarm processing method of super-large scale cluster |
| CN102135907B (en) * | 2011-03-22 | 2013-01-16 | 曙光信息产业股份有限公司 | Alarm processing method of super-large scale cluster |
| CN104808913A (en) * | 2014-01-23 | 2015-07-29 | 腾讯科技（深圳）有限公司 | Event responding method and device |
| CN104808913B (en) * | 2014-01-23 | 2019-08-06 | 腾讯科技（深圳）有限公司 | Event response method and device |
| CN106547609A (en) * | 2015-09-18 | 2017-03-29 | 阿里巴巴集团控股有限公司 | A kind of event-handling method and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101634955B (en) | 2013-01-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104639374B (en) | A kind of application deployment management system | |
| CN108287751B (en) | Task execution method and device and distributed system | |
| CN102761454A (en) | Method and system for monitoring internet of things | |
| CN111290917A (en) | YARN-based resource monitoring method and device and terminal equipment | |
| CN101207522A (en) | Method and apparatus for implementation of collocation task scheduling | |
| CN102999384B (en) | Managing processes within suspend states and execution states | |
| CN1784656A (en) | Monitoring operational data in data processing systems | |
| CN101621400A (en) | History performance data collection method and performance data collecting system | |
| CN103188101A (en) | Distributed type collection scheduling method and device | |
| CN111026602A (en) | Health inspection scheduling management method and device of cloud platform and electronic equipment | |
| CN101634955B (en) | Method for processing event in radio frequency identification system and reader management terminal (RMT) | |
| CN103595566A (en) | Method and device for detecting idle IP addresses | |
| CN103441999A (en) | Control method for socket connection pool | |
| CN113656209A (en) | Resource processing method, device, equipment and storage medium | |
| CN107015855A (en) | A kind of asynchronous service centralized dispatching method and device for supporting time parameter method | |
| CN104683460B (en) | A kind of communication means of Internet of Things, device and server | |
| CN109388501A (en) | Communication matching process, device, equipment and medium based on recognition of face request | |
| CN103312623B (en) | Task cooperation device and method | |
| CN105446812A (en) | Multitask scheduling configuration method | |
| CN110445700A (en) | Slave communication system, method and terminal device | |
| CN111309457A (en) | Method, terminal, collection node and system for collecting meal ordering shop information | |
| Ouyang et al. | An intelligent RFID reader and its application in airport baggage handling system | |
| CN1328925C (en) | Method for timed monitoring of memory database in mobile communication equipment | |
| CN202385116U (en) | Distributed operation and maintenance data acquisition device | |
| CN115712572A (en) | Task testing method and device, storage medium and electronic device |
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 | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20161011 Address after: 300308 Tianjin Airport Economic Zone, Binhai New Area seven East Road No. 2 Zhongxing Industrial Base Patentee after: ZTE INTELLIGENT IOT TECHNOLOGY Co.,Ltd. Address before: 518057 Nanshan District science and Technology Park, Guangdong, South Road, ZTE building, science and Technology Park Patentee before: ZTE Corp. |
|
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: Room 401, building 12, east area, airport business park, No. 80, Huanhe North Road, free trade zone (Airport Economic Zone), Binhai New Area, Tianjin 300000 Patentee after: Gaoxing Zhilian Technology Co.,Ltd. Address before: 300308, Zhongxing Industrial base, 2 East seven, Airport Economic Zone, Tianjin Binhai New Area Patentee before: ZTE INTELLIGENT IOT TECHNOLOGY Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: Room 401, building 12, East Airport Business Park, 80 Huanhe North Road, Tianjin Binhai New Area pilot free trade zone (Airport Economic Zone) Patentee after: Zte Intelligent Iot Technology Co.,Ltd. Address before: Room 401, building 12, East Airport Business Park, 80 Huanhe North Road, Tianjin Binhai New Area pilot free trade zone (Airport Economic Zone) Patentee before: Gaoxing Zhilian Technology Co.,Ltd. |