CN109150679A - A kind of perception machinery of consultation under mode bus - Google Patents
A kind of perception machinery of consultation under mode bus Download PDFInfo
- Publication number
- CN109150679A CN109150679A CN201810902037.1A CN201810902037A CN109150679A CN 109150679 A CN109150679 A CN 109150679A CN 201810902037 A CN201810902037 A CN 201810902037A CN 109150679 A CN109150679 A CN 109150679A
- Authority
- CN
- China
- Prior art keywords
- perception
- request
- prts
- headend equipment
- consultation
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40006—Architecture of a communication node
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/403—Bus networks with centralised control, e.g. polling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5038—Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5046—Resolving address allocation conflicts; Testing of addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Small-Scale Networks (AREA)
Abstract
The invention discloses the perception machineries of consultation under a kind of mode bus, it includes: that headend equipment respectively initializes the device address of oneself, device coding；Back-end system issues perception request, judges the destination address and the corresponding device address of target code and device coding in perception request are being locally created whether carry out agent registration, and carries out registration or unregistered processing；The headend equipment for receiving perception request compares destination address and whether target code equal with the device address of oneself and device coding, and according to equal or unequal interaction of holding consultation.The present invention is on the basis of Bidirectional intelligent agency service model, define in Internet of things system, under mode bus back-end system and headend equipment perception machinery of consultation, using this method, the perception that back-end system and headend equipment under mode bus can be effectively realized is negotiated, to realize Bidirectional intelligent agency service model.This method provides directive function for the intelligence of object in Internet of things system.
Description
Technical field
Perception negotiation side the present invention relates to Internet of things system intellectualized technology field, under especially a kind of mode bus
Method.
Background technique
With the rapid development of informationization technology, Internet of things system has become the trend of development.Traditional Internet of things system
In, between Internet of things system and headend equipment, often unidirectional proxy relationship, i.e. headend equipment provide clothes for Internet of things system
Business passively receives Internet of things system instruction etc., Internet of things system is not headend equipment service comprising submitting data.It is unable to structure
At the object in the Internet of things system of bi-directional service, the object of surrounding cannot be intelligently perceived, itself cannot be better achieved
Value, be unfavorable for the harmony of object in the development and Internet of things system of Internet of things system.
In Internet of things system research and manufacturing field, using ISO/IEC TR 29181-8:2017 and draft ISO WD
Future network service quality Bidirectional intelligent service broker's modelling technique of 21558-8, ISO WD 21559-8 international standard, standard
Specified in Bidirectional intelligent service broker's modelling technique, it is intended to imitate the behavior three elements that the mankind get along amiably and peacefully: perception, negotiate,
It executes, so that the object in Internet of things system has the Bidirectional intelligent service ability of class people function.
The three elements of Bidirectional intelligent agency service are perception, negotiate, execute, two most basic objects in Internet of things system
Between perception, negotiation algorithm, under mode bus, since communication channel is occupied by collective, real time full duplex Working mould cannot be used
Formula, can only use back-end system actively to initiate perception request, and headend equipment response perceives the method for request to realize Bidirectional intelligent
Agency.Under mode bus, due to the characteristic of bus, so that callee must not be with communication data be sent in intention bus, it be in fact
It now perceives, negotiate, it is necessary to using the algorithm of enhancing.This method specifies the Internet of Things in Internet of things system, under mode bus
Perception machinery of consultation between back-end system and headend equipment.
Summary of the invention
In view of the above drawbacks of the prior art, it is an object of the invention to provide the perception negotiations under a kind of mode bus
Method realizes the one-up innovation under Bidirectional intelligent agency service model, it is contemplated that the needs of mode bus anticollision use
This method, the perception that can effectively realize back-end system and headend equipment under mode bus is negotiated, to realize Bidirectional intelligent
Agency service model.This method provides directive function for the intelligence of object in Internet of things system.
It is realized the purpose of the present invention is technical solution in this way, the perception machinery of consultation under a kind of mode bus,
It includes:
S1: the first headend equipment EOD1, the second headend equipment EOD2 ..., the n-th headend equipment EODn respectively initialize oneself
Device address DAddr, device coding DMAC；
S2: back-end system EOS issues perception request PRTs, judges the destination address TargeAddr in perception request PRTs
Device address DAddr corresponding with target code TargeMAC and device coding DMAC be locally created whether carry out agency step on
Note, and carry out registration or unregistered processing；
S3: the headend equipment EOD for receiving perception request PRTs compares destination address TargeAddr and target code
Whether whether TargeMAC equal with oneself device address DAddr and device coding DMAC, and according to it is equal or unequal into
Row negotiates interaction.
Further, the step S1 further includes having:
Device address DAddr is generated at random in defined maximum range, and device coding DMAC is in defined maximum value
It is generated at random in range, device address DAddr and device coding DMAC are non-zero；
And back-end system EOS enables destination address TargeAddr=1, enables target code TargeMAC=1.
Further, the step S2 includes:
If destination address TargeAddr and the corresponding device address target code TargeMAC in perception request PRTs
Agent registration is being locally created in DAddr and device coding DMAC, then obtains communication feature code CMAC information and be attached to perception request
In PRTs；Otherwise communication feature code CMAC=0 is enabled.
Further, the step S3 further includes having:
S31: if equal, obtaining the communication feature code CMAC in perception request PRTs, if in perception request PRTs
Communication feature code CMAC is non-zero and is equal to oneself communication feature code CMAC, and explanation is registered agency, can be directly by non-total
The perception negotiation algorithm of ray mode is held consultation interaction；
S32: if the communication feature code CMAC=0 in perception request PRTs, illustrate that the agency is new perception request, not
Agent registration is established, at this point, headend equipment EOD issues perception request-reply PRTd, with perceiving the target in request-reply PRTd
Location TargeAddr=0 and target code TargeMAC=0, communication feature code CMAC=0.
Further, further include having:
S33: if back-end system EOS receives correctly perception request-reply PRTd, if it is agent registration has been established,
Then hold consultation interaction by the perception negotiation algorithm of non-bus mode；Otherwise back-end system EOS distributes a unique communication special
Levy code CMAC；
S34: establishing agent registration, and sends the first perception request PRTs_1 to the headend equipment EOD of response；Then the first sense
Know that destination address TargeAddr is equal to the device address DAddr in perception request-reply PRTd, target code in request PRTs_1
TargeMAC is equal to the device coding DMAC in perception request-reply PRTd, and communication feature code CMAC is the value of registration.
Further, further include having:
S4: device address DAddr is equal to destination address TargeAddr and device coding in the first perception request PRTs_1
The headend equipment EOD that DMAC is equal to the target code TargeMAC in the first perception request PRTs_1 is available to the first perception
PRTs_1, the communication feature code CMAC in headend equipment EOD record the first perception request PRTs_1 is requested to carry out agent registration；And
It holds consultation interaction by the perception negotiation algorithm of non-bus mode.
Further, further include having:
S5: headend equipment EOD initially enters overtime timing after step S32 issues perception request-reply PRTd；
S51: if after time-out, not receiving the first perception request PRTs_1 yet, then illustrating the communication data sent in bus
On occur colliding or communication abnormality, anomalous counts device adds 1 at this time.
Further, further include having:
S6: back-end system EOS no matter whether the secondary perception correctly establishes agency, can add target code TargeMAC
1, step S3 is repeated to step S51, is perceived next time；
S61: if target code TargeMAC reaches preset maximum value, destination address TargeAddr is added 1, is enabled
Target code TargeMAC=1 repeats step S3 to step S51, is perceived next time；
S62: back-end system EOS when agent registration reaches preset value, stops perception detection, after perception detection stops, after
The time of term of reference according to plan is carried out perception next time and detected by end system EOS.
Further, the step S6 and/or S61 includes:
Step S3 is being repeated into step S51, the headend equipment for the anomalous counts device that adds up in step S5 and step S51
EOD is no longer regarded as being communication abnormality failure after anomalous counts device reaches a certain specified value, and is considered bus data and collides
Failure, at this point, headend equipment EOD can regenerate device address DAddr and device coding DMAC, thus make oneself in next round
It may correctly be perceived in perception detection.
By adopting the above-described technical solution, the present invention has the advantage that: the present invention is different from traditional other calculations
Method, it be the Bidirectional intelligent agency service model on the basis of, it is specified that in Internet of things system, under mode bus rear end system
The perception machinery of consultation of system and headend equipment, since Bidirectional intelligent agency service model belongs to the Frontier Model in future network,
Application is not embodied at present, and the present invention realizes one-up innovation under the model.In view of the need of mode bus anticollision
It wants, using this method, the perception that can effectively realize back-end system and headend equipment under mode bus is negotiated, to realize double
To intelligent agent service model.This method provides directive function for the intelligence of object in Internet of things system.
Other advantages, target and feature of the invention will be illustrated in the following description to a certain extent, and
And to a certain extent, based on will be apparent to those skilled in the art to investigating hereafter, Huo Zheke
To be instructed from the practice of the present invention.
Detailed description of the invention
Detailed description of the invention of the invention is as follows:
Fig. 1 is that Bidirectional intelligent acts on behalf of schematic diagram.
Fig. 2 a and Fig. 2 b are the agent model schematic diagram of headend equipment and back-end system.
Fig. 3 is mode bus structural schematic diagram.
Fig. 4 is that EOS sends PRTs flow chart.
Fig. 5 is that EOS handles PRTd flow chart.
Fig. 6 is that EOD handles PRTs flow chart.
Fig. 7 is the flow diagram that non-bus formula perceives machinery of consultation.
Fig. 8 is the flow diagram that first instance object acquisition meets oneself Demand and service.
Fig. 9 is the flow diagram that second instance object acquisition meets oneself Demand and service.
In figure, parameter is defined as follows:
CMAC, Communication MAC (communication feature code)
DAddr, Device address (device address)
DAddra, Device address advise, it may be assumed that it is recommended that device address；
DMAC, Device MAC, it may be assumed that device coding；
DMACa, Device MAC advise, it may be assumed that it is recommended that device coding；
EO, Entity object, it may be assumed that entity object；
NeedS, Need Services, it may be assumed that the quantity of service of needs；
NResult, Negotiate Result, it may be assumed that negotiation result；
PRT, Perceive request, it may be assumed that perception request；
SData, Service Data, it may be assumed that service data；
SMsg, Service Massage, it may be assumed that information on services；
SMsgLst, Service Massage List, it may be assumed that information on services list；
SName, Service Name, it may be assumed that service name；
SNameLst, Service Name List, it may be assumed that service name list；
SBLen, Service Data Bytes Length, it may be assumed that service data byte length；
SDDLen, Service Data Decimal Digits, it may be assumed that service data decimal digits；
TargeAddr, Targe Address, it may be assumed that destination address；
TargeMAC, Targe MAC, it may be assumed that target code；
TS, Total Services, it may be assumed that total quantity of service of offer；
Ver, Versionnumber, it may be assumed that version number；
CurT is temporary variable.
Specific embodiment
Present invention will be further explained below with reference to the attached drawings and examples.
Embodiment 1, as shown in Figures 1 to 9；A kind of perception machinery of consultation under mode bus, it includes:
S1: the first headend equipment EOD1, the second headend equipment EOD2 ..., the n-th headend equipment EODn respectively initialize oneself
Device address DAddr, device coding DMAC；
S2: back-end system EOS issues perception request PRTs, judges the destination address TargeAddr in perception request PRTs
Device address DAddr corresponding with target code TargeMAC and device coding DMAC be locally created whether carry out agency step on
Note, and carry out registration or unregistered processing；
S3: the headend equipment EOD for receiving perception request PRTs compares destination address TargeAddr and target code
Whether whether TargeMAC equal with oneself device address DAddr and device coding DMAC, and according to it is equal or unequal into
Row negotiates interaction.
The step S1 further includes having:
Device address DAddr is generated at random in defined maximum range, and device coding DMAC is in defined maximum value
It is generated at random in range, device address DAddr and device coding DMAC are non-zero；
And back-end system EOS enables destination address TargeAddr=1, enables target code TargeMAC=1.
The step S2 includes:
If destination address TargeAddr and the corresponding device address target code TargeMAC in perception request PRTs
Agent registration is being locally created in DAddr and device coding DMAC, then obtains communication feature code CMAC information and be attached to perception request
In PRTs；Otherwise communication feature code CMAC=0 is enabled.
The step S3 further includes having:
S31: if equal, obtaining the communication feature code CMAC in perception request PRTs, if in perception request PRTs
Communication feature code CMAC is non-zero and is equal to oneself communication feature code CMAC, and explanation is registered agency, can be directly by non-total
The perception negotiation algorithm of ray mode is held consultation interaction；
S32: if the communication feature code CMAC=0 in perception request PRTs, illustrate that the agency is new perception request, not
Agent registration is established, at this point, headend equipment EOD issues perception request-reply PRTd, with perceiving the target in request-reply PRTd
Location TargeAddr=0 and target code TargeMAC=0, communication feature code CMAC=0.
Further include having:
S33: if back-end system EOS receives correctly perception request-reply PRTd, if it is agent registration has been established,
Then hold consultation interaction by the perception negotiation algorithm of non-bus mode；Otherwise back-end system EOS distributes a unique communication special
Levy code CMAC；
S34: establishing agent registration, and sends the first perception request PRTs_1 to the headend equipment EOD of response；Then the first sense
Know that destination address TargeAddr is equal to the device address DAddr in perception request-reply PRTd, target code in request PRTs_1
TargeMAC is equal to the device coding DMAC in perception request-reply PRTd, and communication feature code CMAC is the value of registration.
Further include having:
S4: device address DAddr is equal to destination address TargeAddr and device coding in the first perception request PRTs_1
The headend equipment EOD that DMAC is equal to the target code TargeMAC in the first perception request PRTs_1 is available to the first perception
PRTs_1, the communication feature code CMAC in headend equipment EOD record the first perception request PRTs_1 is requested to carry out agent registration；And
It holds consultation interaction by the perception negotiation algorithm of non-bus mode.
Further include having:
S5: headend equipment EOD initially enters overtime timing after step S32 issues perception request-reply PRTd；
S51: if after time-out, not receiving the first perception request PRTs_1 yet, then illustrating the communication data sent in bus
On occur colliding or communication abnormality, anomalous counts device adds 1 at this time.
Further include having:
S6: back-end system EOS no matter whether the secondary perception correctly establishes agency, can add target code TargeMAC
1, step S3 is repeated to step S51, is perceived next time；
S61: if target code TargeMAC reaches preset maximum value, destination address TargeAddr is added 1, is enabled
Target code TargeMAC=1 repeats step S3 to step S51, is perceived next time；
S62: back-end system EOS when agent registration reaches preset value, stops perception detection, after perception detection stops, after
The time of term of reference according to plan is carried out perception next time and detected by end system EOS.
The step S6 and/or S61 includes:
Step S3 is being repeated into step S51, the headend equipment for the anomalous counts device that adds up in step S5 and step S51
EOD is no longer regarded as being communication abnormality failure after anomalous counts device reaches a certain specified value, and is considered bus data and collides
Failure, at this point, headend equipment EOD can regenerate device address DAddr and device coding DMAC, thus make oneself in next round
It may correctly be perceived in perception detection.
As shown in figure 3, before Internet of Things back-end system EOS and the first headend equipment EOD1, the second headend equipment EOD2, third
End equipment EOD3 and the 4th headend equipment EOD4 forms Bidirectional intelligent agency service by mode bus.
First headend equipment EOD1 initializes the first device address DAddr1=1 of oneself, the first equipment condition code DMAC1
=05, the first communication feature code CMAC1=0.
Second headend equipment EOD2 initializes the second device address DAddr2=1 of oneself, the second equipment condition code DMAC2
=05, the second communication feature code CMAC2=0.
Third headend equipment EOD3 initializes the third device address DAddr3=5 of oneself, third equipment condition code DMAC3
=6A, third communication condition code CMAC3=0.
4th headend equipment EOD4 is registered equipment, the 4th device address DAddr4=9, the 4th equipment condition code
DMAC4=05, fourth communication condition code CMAC4=9CD6.
Headend equipment EOS sends perception request PRTs to perception request PRTs process by the headend equipment EOS in Fig. 4.
First headend equipment EOD1 and the second headend equipment EOD2 are due to device address DAddr and device coding DMAC phase
Together, data collision may be sent, so that the device address DAddr and device coding DMAC, the first front end that modify oneself are set
Standby EOD1 modifies the first device address DAddr1=3, the first device coding DMAC1=3C, the second headend equipment EOD2 modification the
Two device address DAddr2=5, the second device coding DMAC2=6A.
Third headend equipment EOD3 is registered by EOS automatically because timeout treatment is not present, and starts bi-directional service.
4th headend equipment EOD4 is because be registered equipment, automatically into negotiating and start bi-directional service.
First headend equipment EOD1 smoothly completes registration in next poll, into negotiating and start bi-directional service.
Second headend equipment EOD2 is in next poll, because of the second device address DAddr2 and the second device coding DMAC2
Conflict with the third device address DAddr3 of third headend equipment EOD3 and third device coding DMAC3, oneself will be modified again
The second device address DAddr2=6, the second device coding DMAC2=6A.In lower whorl poll again, registration is smoothly completed, into
Enter negotiation and starts bi-directional service.
It can be seen that the sense between the back-end system and headend equipment under mode bus can be realized automatically by this method
Know machinery of consultation, perceive the presence of other side, and by negotiating, bi-directional proxy is formed, to realize Bidirectional intelligent agent model.
Steps are as follows for the perception negotiation algorithm of non-bus mode in above-mentioned steps:
A.1, first instance object EO1, second instance object EO2 respectively initialize the device address DAddr of oneself, equipment
Encoding D MAC, and the letter such as respective total quantity of service TS, version number Ver, information on services list SMsgLst is obtained by management
Breath.
A.2, first instance object EO1 issues the first perception request PRT1, and perception solicited message is as follows:
| DAddr | DMAC | CMAC | Ver | DAddra | DMACa | TS | SMsgLst | NeedS | SNameLst | NResult |
A.3, second instance object EO2 receives the first perception request PRT1 of first instance object EO1, asks from the first perception
Seek the first device address DAddr1, the first device coding DMAC1, the first communication special that first instance object EO1 is obtained in PRT1
Levy code CMAC1, provide first total quantity of service TS1, version number Ver1, suggest the first device address DAddra1, suggest
First device coding DMACa1, the first negotiation result NResult1.Second instance object EO2 checks the first device address DAddr1
Or first device coding DMAC1 whether be locally registered.
A.3.1, such as unregistered, then explanation is new entity object, needs to hold consultation.
Enable suggest the second device address DAddra2 be equal to the first device address DAddr1, it is proposed that the second device coding
DMACa2 is equal to the first device coding DMAC1, turns A.3.4.
A.3.2, such as only one has registration record, then explanation is new entity object, is worth that matched data with registration
There is repeated conflict, needs to hold consultation.Second instance object EO2 is obtained by the method for management without repeatability conflict
Data to corresponding suggestion the second device address DAddra2 or suggestion the second device coding DMACa2 in, another does not have
The value of repeatability conflict remains into the second device address DAddra2 of corresponding suggestion or the second device coding DMACa2 of suggestion
In.Turn A.3.4.
A.3.3, such as two have registration record, then check the first communication feature code CMAC1 whether the communication special with registration
Code CMAC matching is levied, if it does, then explanation is registered entity object, is turned A.3.5；Otherwise illustrate the first device address
DAddr1 and the first device coding DMAC1 have it is repeated conflict, need to hold consultation.Second instance object EO2 passes through management
Method, obtain without repeatability conflict data to suggest the second device address DAddra2 and suggestion the second equipment volume
In code DMACa2.
A.3.4, the first device address DAddra1 of second instance object EO2 suggestion from procuratorial organ and the first equipment of suggestion are compiled
Whether code DMACa1 is non-zero, and explanation has negotiation to request if non-zero, needs to judge that the second device address DAddr2 is set with second
Standby encoding D MAC2 whether with the first device coding DMACa1 phase of the first device address DAddra1 of corresponding suggestion and suggestion
Deng unequal to need to be revised as the first device address DAddra1 of corresponding suggestion or the first device coding of suggestion
A.3.5 the value of DMACa1 turns.If being equal, illustrate address negotiation success, check the first communication feature code CMAC1 whether etc.
In the second communication feature code CMAC2, if the first communication feature code CMAC1 is not equal to the second communication feature code CMAC2, illustrate logical
Believe that channel mismatches, turns A.3.5.If the first communication feature code CMAC1 is equal to the second communication feature code CMAC2, negotiate to complete,
Enabling the second negotiation result NResult2 is to be completed, and is registered.If the first negotiation result NResult1 be it is unfinished, turn
A.3.6, otherwise perception negotiation process terminates.
A.3.5, second instance object EO2 check version number Ver1 whether with value be locally registered match, said if matching
Bright first instance object EO1 locally completes registration, turns A.3.6.If it does not match, by the first total quantity of service provided
TS1 provide quantity, obtain information on services list SMsgLst1, obtain oneself needs quantity of service NeedS2 and
A.3.7 SNameLst2 turns.
A.3.6, second instance object EO2 checks whether second edition Ver2 has update, if do not updated, perceives
Negotiating process terminates.
A.3.7, second instance object EO2 sends the second perception request PRT2 to first instance object EO1, starts to negotiate stream
Journey.
A.4, first instance object EO1 receives the second perception request PRT2 of second instance object EO2, asks from the second perception
Seek the second device address DAddr2, the second device coding DMAC2, the second communication special that second instance object EO2 is obtained in PRT2
Sign code CMAC2, it the second total quantity of service TS2 provided, second edition Ver2, the second device address DAddra2 suggested, builds
The second device coding DMACa2, the second negotiation result NResult2 of view.First instance object EO1 checks the second device address
Whether DAddr2 or the second device coding DMAC2 has been locally registered.
A.4.1, such as unregistered, then explanation is new entity object, needs to hold consultation.With enabling the first equipment suggested
Location DAddra1 be equal to the second device address DAddr2, it is proposed that the first device coding DMACa1 be equal to the second device coding
A.4.4 DMAC2 turns.
A.4.2, such as only one has registration record, then explanation is new entity object, is worth that matched data with registration
There is repeated conflict, needs to hold consultation.First instance object EO1 is obtained by the method for management without repeatability conflict
Data to corresponding suggestion the first device address DAddra1 or suggestion the first device coding DMACa1 in, another does not have
The value of repeatability conflict remains into the first device address DAddra1 of corresponding suggestion or the first device coding DMACa1 of suggestion
In.Turn A.4.4.
A.4.3, such as two have registration record, then check the second communication feature code CMAC2 whether the communication special with registration
Code CMAC matching is levied, if it does, then explanation is registered entity object, is turned A.4.5；Otherwise illustrate the second device address
DAddr2 and the second device coding DMAC2 have it is repeated conflict, need to hold consultation.First instance object EO1 passes through management
Method, obtain without repeatability conflict data to suggest the first device address DAddra1 and suggestion the first equipment volume
In code DMACa1.
A.4.4, the second device address DAddra2 of first instance object EO1 suggestion from procuratorial organ and the second equipment of suggestion are compiled
Whether code DMACa2 is non-zero, and explanation has negotiation to request if non-zero, needs to judge that the first device address DAddr1 is set with first
Standby encoding D MAC1 whether with the second device coding DMACa2 phase of the second device address DAddra2 of corresponding suggestion and suggestion
Deng unequal to need to be revised as the second device address DAddra2 of corresponding suggestion or the second device coding of suggestion
A.4.5 the value of DMACa2 turns.If being equal, illustrate address negotiation success, check the second communication feature code CMAC2 whether etc.
In the first communication feature code CMAC1, if the second communication feature code CMAC2 is not equal to the first communication feature code CMAC1, illustrate logical
Believe that channel mismatches, turns A.4.5.If the second communication feature code CMAC2 is equal to the first communication feature code CMAC1, negotiate to complete,
Enabling the first negotiation result NResult1 is to be completed, and is registered.If the second negotiation result NResult2 be it is unfinished, turn
A.4.6, otherwise perception negotiation process terminates.
A.4.5, first instance object EO1 check second edition Ver2 whether with value be locally registered match, if matched
Then illustrate that second instance object EO2 locally completes registration, turns A.4.6.If it does not match, by provide second total service
Quantity TS2 provide quantity, obtain information on services list SMsgLst2, obtain oneself needs quantity of service NeedS1 and
A.4.7 SNameLst1 turns.
A.4.6, first instance object EO1 checks whether version number Ver1 has update, if do not updated, perceives negotiation
Process terminates.
A.4.7, first instance object EO1 sends the first perception request PRT1 to second instance object EO2, starts next round
Negotiate process.
Embodiment 2, the present embodiment are preferred embodiment, as shown in Figures 1 to 9；A kind of perception association under mode bus
Quotient's method, it includes:
Under mode bus, since communication channel is occupied by collective, real time full duplex operating mode cannot be used, can only be used
Back-end system actively initiates perception request, and headend equipment response perceives the method for request to realize that Bidirectional intelligent is acted on behalf of.Perception association
Quotient's process is similar with non-bus mode, but before address foundation is negotiated in perception, needs special algorithm, defining EOS here is
Back-end system, EOD are headend equipment, and back-end system EOS is unique back-end system, and EOD has multiple, respectively the first front end
Equipment EOD1, the second headend equipment EOD2 ..., the n-th headend equipment EODn.Specific algorithm is as follows:
B.1, the first headend equipment EOD1, the second headend equipment EOD2 ..., the n-th headend equipment EODn respectively initialize from
Oneself device address DAddr, device coding DMAC；
Wherein, device address DAddr is generated at random in defined maximum range, device coding DMAC it is defined most
It is generated at random within the scope of big value, device address DAddr and device coding DMAC are non-zero.
B.2, back-end system EOS enables destination address TargeAddr=1, enables target code TargeMAC=1.
B.3, back-end system EOS issues perception request PRTs, and perception solicited message is as follows:
| DAddr | DMAC | CMAC | Ver | DAddra | DMACa | TS | SMsgLst | NeedS | SNameLst | NResult |
With,
| TargeAddr | TargeMAC |
If destination address TargeAddr and the corresponding device address target code TargeMAC in perception request PRTs
Agent registration is being locally created in DAddr and device coding DMAC, then obtains communication feature code CMAC information and be attached to perception request
In PRTs, communication feature code CMAC=0 is otherwise enabled.
B.4, the headend equipment EOD for receiving perception request PRTs compares destination address TargeAddr and target code
Whether TargeMAC is equal with oneself device address DAddr and device coding DMAC, if equal, obtains perception request PRTs
In communication feature code CMAC, if the communication feature code CMAC in perception request PRTs is non-zero and is equal to oneself communication feature
Code CMAC, explanation is registered agency, can directly be held consultation interaction by the perception negotiation algorithm of non-bus mode.If
Communication feature code CMAC=0 in perception request PRTs then illustrates that the agency is new perception request, does not set up agent registration, this
When, headend equipment EOD issue perception request-reply PRTd, perceive request-reply PRTd in destination address TargeAddr=0 and
Target code TargeMAC=0, communication feature code CMAC=0, perception solicited message are as follows:
| DAddr | DMAC | CMAC | Ver | DAddra | DMACa | TS | SMsgLst | NeedS | SNameLst | NResult |
| TargeAddr | TargeMAC |
If B.5, back-end system EOS receives correctly perception request-reply PRTd, if it is agent registration has been established,
Then hold consultation interaction by the perception negotiation algorithm of non-bus mode.Otherwise back-end system EOS distributes a unique communication special
Code CMAC is levied, agent registration is established, and sends the first perception request PRTs_1 to the headend equipment EOD of response, in the first perception
Destination address TargeAddr in PRTs_1 is requested to be equal to the device address DAddr in perception request-reply PRTd, target code
TargeMAC is equal to the device coding DMAC in perception request-reply PRTd, and communication feature code CMAC is the value of registration.
B.6, device address DAddr is equal to destination address TargeAddr and equipment volume in the first perception request PRTs_1
The headend equipment EOD that code DMAC is equal to the target code TargeMAC in the first perception request PRTs_1 is available to the first sense
Know that the communication feature code CMAC in request PRTs_1, headend equipment EOD record the first perception request PRTs_1 carries out agent registration.
Thereafter can hold consultation interaction by the perception negotiation algorithm of non-bus mode.
B.7, headend equipment EOD initially enters overtime timing after B.4 issuing perception request-reply PRTd, if overtime
Afterwards, the first perception request PRTs_1 is not received yet, then illustrates that the communication data sent collides in bus, or communication is different
Often.Anomalous counts device adds 1 at this time.
B.8, no matter whether the secondary perception correctly establishes agency to back-end system EOS, can be by target code TargeMAC
Add 1, B.7 B.3 repetition arrives walks, and is perceived next time.If target code TargeMAC reaches preset maximum value, by mesh
Mark address TargeAddr adds 1, enables target code TargeMAC=1, and B.7 B.3 repetition arrives walks, and is perceived next time.Rear end system
The modes such as system EOS stops perception and detect when agent registration reaches preset value, which can be specified by third party obtain
?.After perception detection stops, the time of term of reference according to plan is carried out perception next time and detected by back-end system EOS.
B.9, repeating B.3 into B.7 step, in the headend equipment EOD for B.7 walking cumulative anomalous counts device, in abnormal meter
It after number device reaches a certain specified value, is no longer regarded as being communication abnormality failure, and is considered that bus data collides failure, at this point, preceding
End equipment EOD can regenerate device address DAddr and device coding DMAC, so that making oneself can in next round perception detection
It can correctly be perceived.
As shown in figure 3, before Internet of Things back-end system EOS and the first headend equipment EOD1, the second headend equipment EOD2, third
End equipment EOD3 and the 4th headend equipment EOD4 forms Bidirectional intelligent agency service by mode bus.
First headend equipment EOD1 initializes the first device address DAddr1=1 of oneself, the first equipment condition code DMAC1
=05, the first communication feature code CMAC1=0.
Second headend equipment EOD2 initializes the second device address DAddr2=1 of oneself, the second equipment condition code DMAC2
=05, the second communication feature code CMAC2=0.
Third headend equipment EOD3 initializes the third device address DAddr3=5 of oneself, third equipment condition code DMAC3
=6A, third communication condition code CMAC3=0.
4th headend equipment EOD4 is registered equipment, the 4th device address DAddr4=9, the 4th equipment condition code
DMAC4=05, fourth communication condition code CMAC4=9CD6.
Headend equipment EOS sends perception request PRTs to perception request PRTs process by the headend equipment EOS in Fig. 4.
First headend equipment EOD1 and the second headend equipment EOD2 are due to device address DAddr and device coding DMAC phase
Together, data collision may be sent, so that the device address DAddr and device coding DMAC, the first front end that modify oneself are set
Standby EOD1 modifies the first device address DAddr1=3, the first device coding DMAC1=3C, the second headend equipment EOD2 modification the
Two device address DAddr2=5, the second device coding DMAC2=6A.
Third headend equipment EOD3 is registered by EOS automatically because timeout treatment is not present, and starts bi-directional service.
4th headend equipment EOD4 is because be registered equipment, automatically into negotiating and start bi-directional service.
First headend equipment EOD1 smoothly completes registration in next poll, into negotiating and start bi-directional service.
Second headend equipment EOD2 is in next poll, because of the second device address DAddr2 and the second device coding DMAC2
Conflict with the third device address DAddr3 of third headend equipment EOD3 and third device coding DMAC3, oneself will be modified again
The second device address DAddr2=6, the second device coding DMAC2=6A.In lower whorl poll again, registration is smoothly completed, into
Enter negotiation and starts bi-directional service.
It can be seen that the sense between the back-end system and headend equipment under mode bus can be realized automatically by this method
Know machinery of consultation, perceive the presence of other side, and by negotiating, bi-directional proxy is formed, to realize Bidirectional intelligent agent model.
Steps are as follows for the perception negotiation algorithm of non-bus mode in above-mentioned steps:
A.1, first instance object EO1, second instance object EO2 respectively initialize the device address DAddr of oneself, equipment
Encoding D MAC, and the letter such as respective total quantity of service TS, version number Ver, information on services list SMsgLst is obtained by management
Breath.
A.2, first instance object EO1 issues the first perception request PRT1, and perception solicited message is as follows:
| DAddr | DMAC | CMAC | Ver | DAddra | DMACa | TS | SMsgLst | NeedS | SNameLst | NResult |
A.3, second instance object EO2 receives the first perception request PRT1 of first instance object EO1, asks from the first perception
Seek the first device address DAddr1, the first device coding DMAC1, the first communication special that first instance object EO1 is obtained in PRT1
Levy code CMAC1, provide first total quantity of service TS1, version number Ver1, suggest the first device address DAddra1, suggest
First device coding DMACa1, the first negotiation result NResult1.Second instance object EO2 checks the first device address DAddr1
Or first device coding DMAC1 whether be locally registered.
A.3.1, such as unregistered, then explanation is new entity object, needs to hold consultation.
Enable suggest the second device address DAddra2 be equal to the first device address DAddr1, it is proposed that the second device coding
DMACa2 is equal to the first device coding DMAC1, turns A.3.4.
A.3.2, such as only one has registration record, then explanation is new entity object, is worth that matched data with registration
There is repeated conflict, needs to hold consultation.Second instance object EO2 is obtained by the method for management without repeatability conflict
Data to corresponding suggestion the second device address DAddra2 or suggestion the second device coding DMACa2 in, another does not have
The value of repeatability conflict remains into the second device address DAddra2 of corresponding suggestion or the second device coding DMACa2 of suggestion
In.Turn A.3.4.
A.3.3, such as two have registration record, then check the first communication feature code CMAC1 whether the communication special with registration
Code CMAC matching is levied, if it does, then explanation is registered entity object, is turned
A.3.5；Otherwise illustrate the first device address DAddr1 and the first device coding DMAC1 have it is repeated conflict, need
It holds consultation.Second instance object EO2 is obtained by the method for management without the repeated data to conflict to second suggested
In device address DAddra2 and the second device coding DMACa2 suggested.
A.3.4, the first device address DAddra1 of second instance object EO2 suggestion from procuratorial organ and the first equipment of suggestion are compiled
Whether code DMACa1 is non-zero, and explanation has negotiation to request if non-zero, needs to judge that the second device address DAddr2 is set with second
Standby encoding D MAC2 whether with the first device coding DMACa1 phase of the first device address DAddra1 of corresponding suggestion and suggestion
Deng unequal to need to be revised as the first device address DAddra1 of corresponding suggestion or the first device coding of suggestion
A.3.5 the value of DMACa1 turns.If being equal, illustrate address negotiation success, check the first communication feature code CMAC1 whether etc.
In the second communication feature code CMAC2, if the first communication feature code CMAC1 is not equal to the second communication feature code CMAC2, illustrate logical
Believe that channel mismatches, turns A.3.5.If the first communication feature code CMAC1 is equal to the second communication feature code CMAC2, negotiate to complete,
Enabling the second negotiation result NResult2 is to be completed, and is registered.If the first negotiation result NResult1 be it is unfinished, turn
A.3.6, otherwise perception negotiation process terminates.
A.3.5, second instance object EO2 check version number Ver1 whether with value be locally registered match, said if matching
Bright first instance object EO1 locally completes registration, turns A.3.6.If it does not match, by the first total quantity of service provided
TS1 provide quantity, obtain information on services list SMsgLst1, obtain oneself needs quantity of service NeedS2 and
A.3.7 SNameLst2 turns.
A.3.6, second instance object EO2 checks whether second edition Ver2 has update, if do not updated, perceives
Negotiating process terminates.
A.3.7, second instance object EO2 sends the second perception request PRT2 to first instance object EO1, starts to negotiate stream
Journey.
A.4, first instance object EO1 receives the second perception request PRT2 of second instance object EO2, asks from the second perception
Seek the second device address DAddr2, the second device coding DMAC2, the second communication special that second instance object EO2 is obtained in PRT2
Sign code CMAC2, it the second total quantity of service TS2 provided, second edition Ver2, the second device address DAddra2 suggested, builds
The second device coding DMACa2, the second negotiation result NResult2 of view.First instance object EO1 checks the second device address
Whether DAddr2 or the second device coding DMAC2 has been locally registered.
A.4.1, such as unregistered, then explanation is new entity object, needs to hold consultation.With enabling the first equipment suggested
Location DAddra1 be equal to the second device address DAddr2, it is proposed that the first device coding DMACa1 be equal to the second device coding
A.4.4 DMAC2 turns.
A.4.2, such as only one has registration record, then explanation is new entity object, is worth that matched data with registration
There is repeated conflict, needs to hold consultation.First instance object EO1 is obtained by the method for management without repeatability conflict
Data to corresponding suggestion the first device address DAddra1 or suggestion the first device coding DMACa1 in, another does not have
The value of repeatability conflict remains into the first device address DAddra1 of corresponding suggestion or the first device coding DMACa1 of suggestion
In.Turn A.4.4.
A.4.3, such as two have registration record, then check the second communication feature code CMAC2 whether the communication special with registration
Code CMAC matching is levied, if it does, then explanation is registered entity object, is turned A.4.5；Otherwise illustrate the second device address
DAddr2 and the second device coding DMAC2 have it is repeated conflict, need to hold consultation.First instance object EO1 passes through management
Method, obtain without repeatability conflict data to suggest the first device address DAddra1 and suggestion the first equipment volume
In code DMACa1.
A.4.4, the second device address DAddra2 of first instance object EO1 suggestion from procuratorial organ and the second equipment of suggestion are compiled
Whether code DMACa2 is non-zero, and explanation has negotiation to request if non-zero, needs to judge that the first device address DAddr1 is set with first
Standby encoding D MAC1 whether with the second device coding DMACa2 phase of the second device address DAddra2 of corresponding suggestion and suggestion
Deng unequal to need to be revised as the second device address DAddra2 of corresponding suggestion or the second device coding of suggestion
A.4.5 the value of DMACa2 turns.If being equal, illustrate address negotiation success, check the second communication feature code CMAC2 whether etc.
In the first communication feature code CMAC1, if the second communication feature code CMAC2 is not equal to the first communication feature code CMAC1, illustrate logical
Believe that channel mismatches, turns A.4.5.If the second communication feature code CMAC2 is equal to the first communication feature code CMAC1, negotiate to complete,
Enabling the first negotiation result NResult1 is to be completed, and is registered.If the second negotiation result NResult2 be it is unfinished, turn
A.4.6, otherwise perception negotiation process terminates.
A.4.5, first instance object EO1 check second edition Ver2 whether with value be locally registered match, if matched
Then illustrate that second instance object EO2 locally completes registration, turns A.4.6.If it does not match, by provide second total service
Quantity TS2 provide quantity, obtain information on services list SMsgLst2, obtain oneself needs quantity of service NeedS1 and
A.4.7 SNameLst1 turns.
A.4.6, first instance object EO1 checks whether version number Ver1 has update, if do not updated, perceives negotiation
Process terminates.
A.4.7, first instance object EO1 sends the first perception request PRT1 to second instance object EO2, starts next round
Negotiate process.
It should be understood that the part that this specification does not elaborate belongs to the prior art.Finally, it is stated that above
Embodiment is only used to illustrate the technical scheme of the present invention and not to limit it, although having carried out in detail referring to preferred embodiment to the present invention
Illustrate, those skilled in the art should understand that, can with modification or equivalent replacement of the technical solution of the present invention are made,
Without departing from the objective and range of the technical program, it is intended to be within the scope of the claims of the invention.
Claims (9)
1. the perception machinery of consultation under a kind of mode bus, which is characterized in that the method comprises the following steps:
S1: the first headend equipment EOD1, the second headend equipment EOD2 ..., the n-th headend equipment EODn respectively initialize setting for oneself
Standby address D Addr, device coding DMAC；
S2: back-end system EOS issues perception request PRTs, judges destination address TargeAddr and mesh in perception request PRTs
The corresponding device address DAddr and device coding DMAC of mark coding TargeMAC is being locally created whether carry out agent registration, and
Carry out registration or unregistered processing；
S3: the headend equipment EOD for receiving perception request PRTs compares destination address TargeAddr and target code TargeMAC
It is whether equal with oneself device address DAddr and device coding DMAC, and according to equal or unequal friendship of holding consultation
Mutually.
2. the perception machinery of consultation under mode bus as described in claim 1, which is characterized in that the step S1 further includes
Have:
Device address DAddr is generated at random in defined maximum range, and device coding DMAC is in defined maximum range
Interior random generation, device address DAddr and device coding DMAC are non-zero；
And back-end system EOS enables destination address TargeAddr=1, enables target code TargeMAC=1.
3. the perception machinery of consultation under mode bus as claimed in claim 2, which is characterized in that the step S2 includes:
If destination address TargeAddr and the corresponding device address target code TargeMAC in perception request PRTs
Agent registration is being locally created in DAddr and device coding DMAC, then obtains communication feature code CMAC information and be attached to perception request
In PRTs；Otherwise communication feature code CMAC=0 is enabled.
4. the perception machinery of consultation under mode bus as claimed in claim 2, which is characterized in that the step S3 further includes
Have:
S31: if equal, obtaining the communication feature code CMAC in perception request PRTs, if the communication in perception request PRTs
Condition code CMAC is non-zero and is equal to oneself communication feature code CMAC, and explanation is registered agency, can directly press non-bus mould
The perception negotiation algorithm of formula is held consultation interaction；
S32: if the communication feature code CMAC=0 in perception request PRTs, illustrate that the agency is new perception request, do not set up
Agent registration perceives the destination address in request-reply PRTd at this point, headend equipment EOD issues perception request-reply PRTd
TargeAddr=0 and target code TargeMAC=0, communication feature code CMAC=0.
5. the perception machinery of consultation under mode bus as claimed in claim 4, which is characterized in that further include having:
S33: if back-end system EOS receives correctly perception request-reply PRTd and then presses if it is agent registration has been established
The perception negotiation algorithm of non-bus mode is held consultation interaction；Otherwise back-end system EOS distributes a unique communication feature code
CMAC；
S34: establishing agent registration, and sends the first perception request PRTs_1 to the headend equipment EOD of response；Then the first perception is asked
Destination address TargeAddr in PRTs_1 is asked to be equal to the device address DAddr in perception request-reply PRTd, target code
TargeMAC is equal to the device coding DMAC in perception request-reply PRTd, and communication feature code CMAC is the value of registration.
6. the perception machinery of consultation under mode bus as claimed in claim 5, which is characterized in that further include having:
S4: device address DAddr is equal to destination address TargeAddr and device coding DMAC in the first perception request PRTs_1
It is available equal to the headend equipment EOD of the target code TargeMAC in the first perception request PRTs_1 to be requested to the first perception
Communication feature code CMAC in PRTs_1, headend equipment EOD record the first perception request PRTs_1 carries out agent registration；And by non-
The perception negotiation algorithm of mode bus is held consultation interaction.
7. the perception machinery of consultation under mode bus as claimed in claim 6, which is characterized in that further include having:
S5: headend equipment EOD initially enters overtime timing after step S32 issues perception request-reply PRTd；
S51: if after time-out, not receiving the first perception request PRTs_1 yet, then illustrating that the communication data sent goes out in bus
Now collision or communication abnormality, anomalous counts device adds 1 at this time.
8. the perception machinery of consultation under mode bus as claimed in claim 7, which is characterized in that further include having:
S6: back-end system EOS no matter whether the secondary perception correctly establishes agency, target code TargeMAC can be added to 1, weight
Multiple step S3 is perceived next time to step S51；
S61: if target code TargeMAC reaches preset maximum value, destination address TargeAddr is added 1, enables target
TargeMAC=1 is encoded, step S3 is repeated to step S51, is perceived next time；
S62: back-end system EOS when agent registration reaches preset value, stops perception detection, after perception detection stops, rear end system
The time of term of reference according to plan is carried out perception next time and detected by the EOS that unites.
9. the perception machinery of consultation under mode bus as claimed in claim 8, which is characterized in that the step S6 and/or S61
Include:
Step S3 is being repeated into step S51, the headend equipment EOD for the anomalous counts device that adds up in step S5 and step S51,
It after anomalous counts device reaches a certain specified value, is no longer regarded as being communication abnormality failure, and is considered that bus data collides failure, this
When, headend equipment EOD can regenerate device address DAddr and device coding DMAC, visit so that oneself be made to perceive in next round
It may correctly be perceived in survey.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810902037.1A CN109150679B (en) | 2018-08-09 | 2018-08-09 | Perception negotiation method under bus mode |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810902037.1A CN109150679B (en) | 2018-08-09 | 2018-08-09 | Perception negotiation method under bus mode |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109150679A true CN109150679A (en) | 2019-01-04 |
| CN109150679B CN109150679B (en) | 2021-04-02 |
Family
ID=64792488
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810902037.1A Active CN109150679B (en) | 2018-08-09 | 2018-08-09 | Perception negotiation method under bus mode |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109150679B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101035040A (en) * | 2007-02-02 | 2007-09-12 | 南京邮电大学 | Radio sensor network data collection method based on multi-agent negotiation |
| WO2013123445A1 (en) * | 2012-02-17 | 2013-08-22 | Interdigital Patent Holdings, Inc. | Smart internet of things services |
| CN104394181A (en) * | 2014-01-22 | 2015-03-04 | 上海云卡网络科技有限公司 | An object and space mutual identification system and method based on internet of things |
| EP2924573A2 (en) * | 2014-03-26 | 2015-09-30 | Rockwell Automation Technologies, Inc. | On-premise data collection and ingestion using industrial cloud agents |
| CN105431839A (en) * | 2013-03-15 | 2016-03-23 | 罗伯特·哈多克 | Intelligent internet system with adaptive user interface providing one-step access to knowledge |
| CN105743750A (en) * | 2016-03-23 | 2016-07-06 | 北京绿源普惠科技有限公司 | Adaptive sensing method for smart home |
| CN106605239A (en) * | 2014-09-23 | 2017-04-26 | 英特尔公司 | Multifactor intelligent agent control |
-
2018
- 2018-08-09 CN CN201810902037.1A patent/CN109150679B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101035040A (en) * | 2007-02-02 | 2007-09-12 | 南京邮电大学 | Radio sensor network data collection method based on multi-agent negotiation |
| WO2013123445A1 (en) * | 2012-02-17 | 2013-08-22 | Interdigital Patent Holdings, Inc. | Smart internet of things services |
| CN105431839A (en) * | 2013-03-15 | 2016-03-23 | 罗伯特·哈多克 | Intelligent internet system with adaptive user interface providing one-step access to knowledge |
| CN104394181A (en) * | 2014-01-22 | 2015-03-04 | 上海云卡网络科技有限公司 | An object and space mutual identification system and method based on internet of things |
| EP2924573A2 (en) * | 2014-03-26 | 2015-09-30 | Rockwell Automation Technologies, Inc. | On-premise data collection and ingestion using industrial cloud agents |
| CN106605239A (en) * | 2014-09-23 | 2017-04-26 | 英特尔公司 | Multifactor intelligent agent control |
| CN105743750A (en) * | 2016-03-23 | 2016-07-06 | 北京绿源普惠科技有限公司 | Adaptive sensing method for smart home |
Non-Patent Citations (2)
| Title |
|---|
| ISO: "《information technology-Future Network-Problem statement and requirements Part8:Quality of Service》", 《ISO/TR 29181-8》 * |
| 张学谦: "基于物联网的智能家居的研究与实现", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109150679B (en) | 2021-04-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| DE60225330T2 (en) | DETERMINATION OF THE ENVIRONMENTAL CONTEXT | |
| Santos et al. | A personal connected health system for the Internet of Things based on the Constrained Application Protocol | |
| DE602006000954T2 (en) | Method and system for controlling multiple home devices with a single control unit | |
| DE102010037271A1 (en) | A method of providing wireless vehicle access | |
| TWI572156B (en) | Transmission system using bluetooth low energy technique | |
| CN105578396A (en) | Emergency help method, device and system | |
| DE60101142T2 (en) | Providing services for portable information devices over an information technology network | |
| Kim et al. | Device management and data transport in IoT networks based on visible light communication | |
| Rivard et al. | Factors associated with interagency coordination in a child mental health service system demonstration | |
| Touati et al. | An experimental performance evaluation and compatibility study of the Bluetooth low energy based platform for ECG monitoring in WBANs | |
| CN109150679A (en) | A kind of perception machinery of consultation under mode bus | |
| WO2005031522A3 (en) | System and method for efficiently processing multiple credit applications | |
| DE112019002804T5 (en) | MEASURING DEVICE, INFORMATION PROCESSING DEVICE AND COMMUNICATION SYSTEM | |
| DE60212294T2 (en) | Apparatus and method for promoting the selection of electronic services by means of infrared and network address identification | |
| CN105190613A (en) | Method and apparatus for providing contextual context to a user device | |
| CN105139217A (en) | Method, apparatus and system used for acquiring user information | |
| Venturini et al. | Methodological design and comparative evaluation of a MAS providing AmI | |
| DE102020124980A1 (en) | OFFLINE APPROXIMATE CAR RIDE BOOKING | |
| CN106097218A (en) | A kind of portable medical service | |
| Lee | Dynamic data binding protocol between IoT medical device and IoT medical service for mobile healthcare | |
| CN110380760A (en) | Universal personal health equipment flag bit data transmission method based on low-power consumption bluetooth | |
| CN109245976B (en) | Non-bus type perception negotiation method | |
| KR20220103025A (en) | Method and apparatus for replacing security key in machine to machine system | |
| KR20120101806A (en) | Medical information management network and method thereof | |
| US20100280900A1 (en) | System and method for link of upper shopping mall and independent shopping mall using api method |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200508 Address after: No. 71, No. 1, No. 15, beichengtian street, Jiangbei District, Chongqing Applicant after: Chongqing Yuandun Technology Group Co., Ltd Address before: 401329 10-2, 2 Torch Hotel, 166 Keyuan Road, Kowloon Po, Chongqing. Applicant before: CHONGQING QICAIHONG DIGITAL TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |