| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 30269.303-2018 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Information technology -- Sensor networks -- Part 303: Communication and information exchange: Network layer specification for wireless sensor networks based on IP protocol
| Valid |
GB/T 30269.303-2018
|
PDF similar to GB/T 30269.303-2018
Basic data | Standard ID | GB/T 30269.303-2018 (GB/T30269.303-2018) | | Description (Translated English) | Information technology -- Sensor networks -- Part 303: Communication and information exchange: Network layer specification for wireless sensor networks based on IP protocol | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L79 | | Classification of International Standard | 35.110 | | Word Count Estimation | 139,168 | | Date of Issue | 2018-06-07 | | Date of Implementation | 2019-01-01 | | Regulation (derived from) | National Standard Announcement No. 9 of 2018 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 30269.303-2018: Information technology -- Sensor networks -- Part 303: Communication and information exchange: Network layer specification for wireless sensor networks based on IP protocol
---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Information technology--Sensor networks--Part 303. Communication and information exchange. Network layer specification for wireless sensor networks based on IP protocol
ICS 35.110
L79
National Standards of People's Republic of China
Information technology sensor network
Part 303. Communication and information exchange.
IP-based wireless sensor network network layer specification
Informationtechnology-Sensornetworks-Part 303.Communicationand
Published on.2018-06-07
2019-01-01 implementation
State market supervision and administration
China National Standardization Administration issued
Content
Foreword III
1 Scope 1
2 Normative references 1
3 Terms and Definitions 1
4 Abbreviations 3
5 Overall description 4
5.1 Overview 4
5.2 Protocol Stack Structure 5
6 adaptation layer 6
6.1 Overview 6
6.2 Frame Format 6
6.3 Constant 12
6.4 Functional Description 12
7 network layer 24
7.1 Overview 24
7.2 Service Specification 24
7.3 Frame Format 62
7.4 Command Frame 68
7.5 Constants and NIB Attributes 107
7.6 Functional Description 112
References 136
Foreword
GB/T 30269 "Information Technology Sensor Network" is divided into the following parts.
--- Part 1. Reference architecture and general technical requirements;
--- Part 2. Terminology;
--- Part 301. Communication and information exchange. low-speed wireless sensor network network layer and application support sub-layer specification;
--- Part 302. Communication and information exchange. High-reliability wireless sensor network media access control and physical layer specifications;
--- Part 303. Communication and information exchange. IP-based wireless sensor network network layer specification;
--- Part 401. Collaborative Information Processing. Services and interfaces supporting collaborative information processing;
--- Part 501. Identification. Sensing node identifier preparation rules;
--- Section 502. Identification. Sensing node identifier resolution;
--- Section 503. Identification. Sensing node identifier registration procedures;
--- Part 504. Identification. Sensor node identifier management specification;
--- Part 601. Information Security. General Technical Specifications;
--- Part 602. Information Security. Low-rate wireless sensor network network layer and application support sub-layer security specifications;
--- Part 603. Information Security. Network Transmission Security Specification;
--- Part 701. Sensor interface. signal interface;
--- Part 702. Sensor interface. data interface;
--- Part 801. Testing. General requirements;
--- Part 802. Testing. Low-speed wireless sensor network media access control and physical layer;
--- Part 803. Testing. Low-speed wireless sensor network network layer and application support sub-layer;
--- Part 804. Testing. Sensor Interface Test Specification;
--- Section 805. Testing. Sensor Gateway Test Specification;
--- Part 806. Test. Sensing node identifier resolution conformance test specification;
--- Part 807. Testing. Low-rate wireless sensor network network layer and application support sub-layer security assessment specifications;
--- Part 901. Gateway. General technical requirements;
--- Part 902. Gateway. Remote management technical requirements;
--- Section 903. Gateway. Logic Function Interface Technical Specification;
--- Part 1001. Middleware. Sensor network node interface.
This part is part 303 of GB/T 30269.
This part is drafted in accordance with the rules given in GB/T 1.1-2009.
Please note that some of the contents of this document may involve patents. The issuing organization of this document is not responsible for identifying these patents.
This part is proposed and managed by the National Information Technology Standardization Technical Committee (SAC/TC28).
This section was drafted. Chongqing University of Posts and Telecommunications, China Electronics Technology Standardization Institute, Shenzhen HiSilicon Semiconductor Co., Ltd., Shenzhen Competition
West Information Technology Co., Ltd., China Electric Power Research Institute, Anhui University.
The main drafters of this section. Wei Wei, Wang Heng, Zhuo Lan, Liu Pei, Su Jingru, Jiang Wei, Tong Jie, Zhao Bo, Wang Ping, Wang Hao, Yu Hui, Hu Yanjun.
Information technology sensor network
Part 303. Communication and information exchange.
IP-based wireless sensor network network layer specification
1 Scope
This part of GB/T 30269 defines the network topology, protocol stack structure, network layer of wireless sensor networks based on IP protocol.
Its adaptation layer protocols and services.
This section applies to the design and development of wireless sensor networks based on IP technology.
2 Normative references
The following documents are indispensable for the application of this document. For dated references, only dated versions apply to this article.
Pieces. For undated references, the latest edition (including all amendments) applies to this document.
GB 15629.11-2003 Information technology systems - Telecommunications and information exchange - Particular requirements for local and metropolitan area networks
Part 11. Wireless LAN Media Access Control and Physical Layer Specifications
GB/T 15629.15-2010 Information technology systems - Telecommunications and information exchange - Particular requirements for local and metropolitan area networks
Part 15. Low-speed wireless personal area network (WPAN) media access control and physical layer specifications
GB/T 30269.301-2014 Information technology sensor networks - Part 301. Communication and information exchange. Low-speed wireless sensing
Network layer and application support sublayer specification
RFC791 IPv4 network protocol specification (Internetprotocol, DARPAinternetprogramprotocolspecifica-
Tion)
RFC3232 assigned value. RFC1700 is replaced by online database (Assignednumbers. RFC1700isreplacedby
Anon-linedatabase)
Transmission of RFC4944 IPv6 Messages over IEEE 802.15.4 Networks. Overview, Presuppositions, Problem Statements, Objectives
(TransmissionofIPv6packetsoverIEEE802.15.4networks.Overview, assumptions, problemstate-
Ment,andgoals)
RFC6550 RPL. IPv6 Low Power Lossful Network Routing Protocol (RPL. IPv6routingprotocolforlow-powerand
Lossynetworks)
RFC6551 Routing Metrics for Low Power Lossy Network Path Calculations (Routingmetricsusedforpathcalculation
Inlow-powerandlossynetworks)
RFC6552 Objective function for low power lossy network routing protocol (RPL) (Objectivefunctionzerofortherou-
Tingprotocolforlow-powerandlossynetworks(RPL))
RFC8200 Internet Protocol, Version 6 (IPv6) Specification [Internetprotocol, version6 (IPv6) specification]
3 Terms and definitions
The following terms and definitions apply to this document.
3.1
Security level securitylevel
An indication of the protection application is provided in the information transmission.
3.2
Packet
A set of bits that are sent in a format through physical media at the same time.
3.3
Disconnect disconnection
A service used to cancel a connection.
3.4
Degree degree
The number of neighbor nodes in the range of one hop around the node.
3.5
Service data unit servicedataunit
A unit of information transmitted through a service access point.
3.6
Personal network coordinator personalnetworkcoordinator
A coordinator that serves as the primary control in the personal area network.
Note. In a short-range wireless network, there should generally be one domain network coordinator.
3.7
Encryption encryption
Convert information into another form of expression and require privileged information to restore the original expression.
3.8
Confidentiality
Guarantee information is only disclosed to target customers.
3.9
Connection connection
A service used to create member affiliations in a wireless personal area network.
3.10
Key key
Privilege information used to restrict unauthorized users from accessing information content.
Note. Keys are generally used to protect information from exposure and/or tampering.
3.11
Full-featured device fulfunctiondevice
A device that can be used as a central coordinator.
3.12
Device device
An entity that can perform short-range wireless network access control and as a physical layer wireless interface.
Note. The device can be a simplified function device (RFD) or a full-featured device (FFD).
3.13
Protocol data unit protocoldataunit
A unit of data exchanged between two layers of entities.
3.14
Neighbors found neighbordiscovery
Nodes used on the same link discover each other's existence, determine each other's MAC layer address, discover routers, and maintain access to
The reachability information of the path of the live neighbor.
3.15
Mesh network meshnetwork
A network topology in which any device node can act as both an AP and a router, and each node in the network can send and
Receiving signals, each node can communicate directly with one or more peer nodes.
4 Abbreviations
The following abbreviations apply to this document.
ADL. Adaptation Layer (AdaptationLayer)
AP. Access Control Point (AccessPoint)
APDU. Application Support Sublayer Protocol Data Unit (ApplicationSupportSublayerProtocolDataUnit)
APL. Application Layer (ApplicationLayer)
APS. Application Support Sublayer (ApplicationSupportSublayer)
APSME-SAP. Application Support Sublayer Management Entity - Service Access Point (ApplicationSupportSublayerManagement
Entity-ServiceAccessPoint)
CID. text identifier (ContextIdentifier)
DAC. Duplicate Address Confirmation (DuplicateAddressConfirmation)
DAD. Duplicate Address Detection (DuplicateAddressDetection)
DAG. directed acyclic graph (DirectedAcyclicGraph)
DAO. Destination Advertisement Object (DestinationAdvertisementObject)
DAR. Duplicate Address Request Message Message (DuplicateAddressRequest)
DTSN. Destination Advertisement Broadcast Series (DestinationAdvertisementTriggerSequenceNumber)
DHCP. Dynamic Host Configuration Protocol (DynamicHostConfigurationProtocol)
DODAG. Destination-OrientedDirectedAcyclicGraph
DISDODAG. Request Information (DODAGInformationSolicitation)
DIODODAG. Information Object (DODAGInformationObject)
EPID. Extended Personal Area Network Identifier (ExtendPANID)
EUI. Extended Unique Identifier (ExtendedUniqueIdentifier)
HC_UDP. Header Compression Datagram Protocol (HeaderCompression_UserDatagramProtocol)
ICMP. Internet Control Message Protocol (InternetControlMessageProtocol)
IEEE. Institute of Electrical and Electronics Engineers (Institute of Electric Europe Engineers)
IP. Internet Protocol (InternetProtocol)
IPHC. IP-based Sensor Network Header Compression Technology (IPoverWirelessSensorNetworkHeaderCompress)
IPv6. Internet Protocol 6th Edition (InternetProtocolversion6)
MAC. Media Access Control (MediumAccessControl)
MCPS-SAP. MAC Common Part Sublayer - Service Access Point (MediumAccessControlCommonPartSublayer-
ServiceAccessPoint)
MLDE-SAP. MAC Sublayer Data Entity - Service Access Point (Medium AccessControlSublayerDataEntity-
ServiceAccessPoint)
MLME-SAP. MAC sublayer management entity - service access point (Medium AccessControlSublayerManagement
Entity-ServiceAccessPoint)
FFD. Full-featured device (FulFunctionDevice)
MPDU. MAC layer protocol data unit (MACProtocolDataUnit)
NA. NeighborAdvertisement
ND. Neighbor Discovery (NeighborDiscovery)
NFB. Negative Feedback (NegativeFeedback)
NHC. Next Head Compression (NextHeaderCompress)
NIB. Network Layer Information Base (Network-LayerInformationBase)
NLDE. Network Layer Data Entity (Network-LayerDataEntity)
NLDE-SAP. Network Layer Data Entity - Service Access Point (Network-LayerDataEntity-ServiceAccessPoint)
NLME. Network-Layer Management Entity
NLME-SAP. Network Layer Management Entity - Service Access Point (Network-LayerManagementEntity-ServiceAccess)
Point)
NPDU. Network Layer Protocol Data Unit (Network-LayerProtocolDataUnit)
NS. Neighbor Solicitation
NSDU. Network Service Data Unit (NetworkServiceDataUnit)
NUD. Neighbor Unreachable Detection (NeighborUnreachableDetection)
NWKIB. Network Layer Information Base (NetworkLayerInformationBase)
NWL. Network Layer (NetworkLayer)
OSI. Open System Interconnection
PAN. Personal Area Network (PersonalAreaNetwork)
PHY. Physical Layer (PhysicalLayer)
PIB. PAN Information Base (PANInformationBase)
PLME-SAP. Physical Layer Management Entity - Service Access Point (PhysicalLayerManagementEntity-ServiceAccess
Point)
RA. Router Advertisement (RouterAdvertisement)
RFD. Reduced Function Device (ReducedFunctionDevice)
RPL. IPv6-based routing protocol for low-power wireless networks (IPv6RoutingProtocolforLow-Power
andLossyNetworks)
RS. Router Request (RouterSolicitation)
RSSI. Received Signal Strength Indication (ReceivedSignalStrengthIndication)
SAP. Service Access Point (ServiceAccessPoint)
SCH. Scheduling Header (SchedulingHeader)
UDP. User Datagram Protocol (UserDatagramProtocol)
5 general description
5.1 Overview
5.1 specifies the support provided by the wireless sensor network to form the network topology, and describes the mesh network and the tree network group in detail.
a hybrid network in which wireless sensor networks are divided into two peer subnets according to different support protocols. IPv4/IPv6 wireless sensors
The internet. Each subnet can be a distributed hybrid network structure. In the network operation, each routing node has a message packet forwarding function.
can. After the node completes the information collection, it forwards the gateway through the router and accesses the IPv4/IPv6 backbone network through the gateway. Wireless based on IP protocol
The network topology of the sensor network is shown in Figure 1.
Figure 1 Schematic diagram of IP-based wireless sensor network topology
Figure 1 defines the following four types of logical function devices.
a) Gateway. responsible for protocol conversion and data mapping between the wireless sensor network and the IPv4/IPv6 backbone network;
b) Coordinator. The manager of the network organization, a network has only one coordinator, responsible for managing other nodes in its network (routing)
And child nodes);
c) routing node. implement data transfer;
d) End node. A terminal node is a device that connects a sensor or actuator to a wireless sensor network.
Note. A node refers to a routing node and a terminal node. The client, the client, refers to a program that corresponds to the server and provides local services to the client.
The IPv4/IPv6 backbone network can be Ethernet, a network defined by GB 15629.11-2003, or a network defined by other standards.
The IPv4/IPv6 backbone network and clients are outside the scope of this standard.
The protocol stack structure of the wireless sensor network is based on the OSI model. Each layer provides a series of specifics for the adjacent upper layer
Services (such as. the physical layer provides services for the media access control layer), mainly including data entities providing data transmission services and management entities to provide
Various services other than data transmission. Each service entity provides an interface to the upper layer of its neighbor through SAP, each
SAP supports different service primitives to achieve different functional requirements.
The adaptation layer defines functions such as stateless address autoconfiguration, fragment reassembly, header compression, and deterministic support. Network layer defines routing
Mechanisms and algorithms, neighbor discovery services and network and device maintenance.
5.2 Protocol stack structure
The wireless sensor network protocol stack consists of layers and their modules, as shown in Figure 2.
Figure 2 Protocol stack structure
The physical layer and MAC layer of the wireless sensor network shall comply with the requirements of GB/T 15629.15-2010.
The adaptation layer of the wireless sensor network is an intermediate layer defined in the network layer, and provides the MAC layer access to the IP protocol upward.
It is mainly responsible for stateless address autoconfiguration, fragment reassembly, and network layer header compression and deterministic support.
The network layer of the wireless sensor network supports route discovery and maintenance at the network layer between nodes, neighbor discovery and related neighbor information.
Save, inter-node data transfer mechanism, and network management and device maintenance.
6 adaptation layer
6.1 Overview
The adaptation layer provides services for the MAC layer of the wireless sensor network oriented to the IPv6 protocol, and is an intermediate layer defined in the network layer.
It provides upward access support of the MAC layer to the IPv6 protocol, and implements control network construction, topology, fragment reassembly, header compression, and determination.
Sexual support, etc. The adaptation layer frame format is mainly described for the IPv6 protocol.
6.2 Frame format
6.2.1 General frame format
The adaptation layer frame is the payload portion of the MPDU, and each adaptation layer frame is composed of two basic parts. a frame header and a payload. Adaptation layer header package
In the form of a stack, the stack consists of headers with different header types and header fields, according to different functional requirements.
The adaptation layer general frame format includes a frame header stack of the adaptation layer encapsulation and an adaptation layer payload. Wherein, the adaptation layer frame header includes a frame header
Type field and corresponding frame header field. The frame header stack of the adaptation layer encapsulation is described as a specific order field, in a certain order, according to
The second is the Mesh header, the broadcast header, the slice header, and the dispatch header. As shown in Figure 3.
Octet. 1 8/2 1 1 1 3/4 1 2
Mesh head
Frame header type field
Mesh head
Broadcast head
Frame header type field
Broadcast head
Fragment header
Frame header type field
Fragment header
Dispatch header
Frame header type field
Dispatch header
Figure 3 Universal Adaptation Layer Frame Format
6.2.2 Frame Head Type
The adaptation layer header type field is 8 bits, and each frame header type is determined by the corresponding type field. As shown in Table 1.
Table 1 Frame header type table
Type field (8 bits) Frame header type field meaning description
00xxxxxx NALP
Non-sensor net frame. The following bit is not part of the sensor network package, any message message value
The sensor network node that is 00xxxxxx will discard this packet. Other Hope and Sensor Network Festival
The non-sensor network protocol co-located should immediately follow the head of GB/T 15629.15-2010
Department, including an octet that matches the type field
01000001 The IPv6 subsequent header is an uncompressed IPv6 header, see 6.2.7.2
01000010 HC1 The subsequent header is the IPv6 header with HC1 compression. See 6.2.7.3 for HC1 compression.
01010000 BC0 The subsequent header is the BC0 header that supports Mesh broadcast/multicast. See 6.2.4 for the head of BC0.
01111111 ESC
The subsequent header is an additional message message field, a single 8-bit field of the message message value.
It allows message message values greater than 127
10xxxxxx Mesh The subsequent header is the Mesh mesh header, see 6.2.3
11000xxx FRAG1 The subsequent header is the first fragment header, see 6.2.7.5 or 6.2.7.9
11100xxx FRAGN The subsequent header is the subsequent fragment header, see 6.2.7.5 or 6.2.7.9
01000000~01111111 IPHC IPv6 compression header
11100000~11110111 NHC Next Compression
01000011 SCH Dispatch header type description value
6.2.3 Mesh Head
The adaptation layer Mesh header consists of a Mesh type field and a corresponding Mesh header field. Mesh type field is divided by the highest two points
Do not set to 1 and 0 to decide. The structure of the adaptation layer Mesh header frame is shown in Figure 4.
Bit. 0~1 2 3 4~7 Octet. 8/2 8/2
10 VF remaining hop source address destination address
Figure 4 Adaptation layer Mesh header frame structure
The adaptation layer Mesh header frame structure includes a V field, an F field, a remaining hop count field, a source address field, and a destination address field in sequence.
The corresponding meaning of each field is shown in Table 2.
Table 2 Mesh header fields
Field Type Field Value Field Meaning
(1 person)
0 The initiator address is a 64-bit IEEE extended address (EUI-64 address)
1 The initiator address is a 16-bit short address.
(1 person)
0 Destination address is 64-bit IEEE extended address (EUI-64 address)
1 destination address is 16-bit short address
Remaining hops
(4)
0 no longer forwards the package
Non-zero every time, minus 1
Table 2 (continued)
Field Type Field Value Field Meaning
source address
The link layer address of the initiator. Can be 64-bit IEEE extended address (EUI-64 address) or 16-bit short
site. Determined by the value of the V field
Destination address
The link layer address of the destination. Can be 64-bit IEEE extended address (EUI-64 address) or 16-bit short
site. Determined by the value of the F field
6.2.4 Broadcast Header (BC0 Header)
The adaptation layer broadcast header follows the Mesh header and consists of a broadcast (BC0) type field and a corresponding broadcast (BC0) header field. BC0
The type field is determined by setting the highest two bits to 0 and 1. The adaptation layer broadcast header frame structure is shown in FIG. 5.
Bit. 0~1 2~7 8~15
01 BC0 BC0 serial number
Figure 5 Adaptation layer broadcast header (BC0) frame structure
The BC0 header field is the LBC0 sequence number. The BC0 serial number is incremented by 1 each time a new Mesh broadcast or multicast packet is sent.
Duplicate packets are detected and suppressed.
6.2.5 Fragment reorganization
Fragmentation reorganization includes.
a) fragment retransmission request header
The fragment retransmission request header is used for the fragment receiving direction to send information to the fragment sender to feed back the lost fragment. Fragment retransmission request header format
Figure 6 shows. The header type identifier bit "11001" of the slice retransmission request header is set according to the allocation of the original header dispatch value. Minute
The slice retransmission request header has two formats. When the number of lost fragments does not exceed 15, the fragment retransmission request header format should be as shown in Figure 6a).
Show. When the number of lost fragments exceeds 15, the fragment retransmission request header format should be as shown in Figure 6b).
b) fragment retransmission response header format
The slice retransmission response header is used to retransmit lost fragments. The fragment retransmission response header format is shown in Figure 7.
The header type identifier of the slice retransmission request header is set to "11101" according to the allocation of the original header dispatch value.
6.2.6 Dispatch header
The scheduling header type description value and the scheduling header are as shown in FIG. 8.
The frame format of the scheduling header is shown in Figure 9.
Bits. 5 11 16 4 5 5 Variable 5
Identifier. 11001 Packet Length Fragment Label MFSUM MFNUM MFNUM MFNUM
a)
Bits. 5 11 16 4 4 5 5 Variable 5
Identifier. 11001 Packet Length Fragment Label 1111 MFSUM-15 MFNUM MFNUM MFNUM
b)
Description.
Packet Length--- Indicates the length of the original packet (in octets).
Fragment label --- indicates the label of the fragment.
MFSUM --- indicates the number of lost fragments. The value of this field ranges from 0 to 15. It can indicate that there are 15 fragments lost. The value of this field is "0" and
"30" is not used to indicate the number of lost fragments, but is used to indicate the success of the reorganization and the abandonment of the reorganization. When 0 and 30 appear in the domain
When you do not follow any missing fragment number fields.
MFNUM --- indicates the number of the lost fragment. When there are multiple shards lost, the order of the missing shard numbers is arranged from small to large. In order to distribute
The sender retransmits in the order in which the fragments are sent. When all the missing shards are completely filled, if the data is fragmented
The length of the request header is not aligned with the boundary of the integer octet, and "0" is padded at the end to make the header length an integer octet.
Figure 6 fragment retransmission request header format
Bit. 5 11 16 8 Variable
Identifier. 11001 Packet Length Fragment Label Offset Payload
Description.
Packet Length--- Indicates the length of the original packet (in octets).
Fragment label --- indicates the label of the frag...
|