Communication method and device

Abstract

The invention discloses a communication method and device, which can be applied to intelligent application scenes such as a vehicle-mounted communication scene, a wireless battery management system and an intelligent home scene, and can be applied to the Internet of Vehicles, a star flash network and the like. The method may comprise: generating address allocation capability indication information (S601), and sending the address allocation capability indication information (S602) to a second node, the address allocation capability indication information being used for indicating an address allocation capability of a first node, thereby informing the second node of the address allocation capability through the address allocation capability indication information, a node with an address allocation capability does not need to be searched through a broadcast message or a multicast message, so that the wireless resource overhead can be saved. In the embodiment of the invention, the second node acquires the address allocation capability of the first node, so that the second node can determine whether to initiate the address application to the first node or not, thereby reducing unnecessary address application messages and further saving wireless resource overhead.

Description

Communication method and device Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a communication method and device. Background Art

[0002] With the continuous development of wireless communication technology, wireless battery management systems (BMS), sensor networks, and intelligent application scenarios such as smart homes, smart cockpits, smart driving, smart manufacturing, and smart transportation have emerged. Taking the smart home scenario as an example, it can include at least one communication domain, which consists of a master node and at least one slave node. Any two nodes can communicate based on the communication address.

[0003] In the communication domain, nodes typically obtain communication addresses based on the Dynamic Host Configuration Protocol (DHCP), which uses a high number of broadcast or multicast messages, increasing wireless resource overhead. Therefore, how to conserve wireless resource overhead during the process of node address acquisition is a pressing technical challenge.

[0004] Summary of the Invention

[0005] The present application provides a communication method and apparatus that can indicate the address allocation capability of a node, thereby facilitating saving wireless resource overhead.

[0006] In a first aspect, the present application provides a communication method, which is applied to a first node and can be executed by the first node or by a module in the first node, such as a chip or processor in the first node. The method may include generating address allocation capability indication information, and sending the address allocation capability indication information to a second node, where the address allocation capability indication information is used to indicate the address allocation capability of the first node.

[0007] As can be seen, the first node notifies the second node of its address allocation capability through the address allocation capability indication information, eliminating the need for the second node to search for nodes with address allocation capability through broadcast or multicast messages, thus saving radio resource overhead and time. The second node's knowledge of the first node's address allocation capability facilitates its decision to initiate an address request from the first node, reducing unnecessary address request messages and further saving radio resource overhead.

[0008] The second node is directly connected to the first node, that is, the second node and the first node are neighbor nodes. In this application, address refers to communication address, and address and communication address can be used interchangeably unless otherwise specified.

[0009] Optionally, the address allocation capability indication information is specifically used to indicate:

[0010] If the first node has the address allocation capability, then the first node can allocate a communication address to other nodes, such as the second node. Thus, upon receiving an address request message from another node, the first node can allocate a communication address to the other node, so that the other node can quickly obtain the allocated communication address.

[0011] Alternatively, if the first node has the address allocation agent capability, the first node can relay address application and address allocation for other nodes, thereby saving wireless resource overhead.

[0012] Alternatively, if the first node does not have the address allocation capability, then the first node cannot allocate communication addresses, nor can it relay address applications and address allocations for other nodes. Therefore, the first node can apply for a communication address from a node with address allocation capability to reduce unnecessary address application messages.

[0013] In one possible implementation, the address allocation capability indication information is carried in a Wireless Adjacency Protocol (WAP) message. WAP messages are transmitted during the process of establishing a neighbor relationship. Carrying the address allocation capability indication information in a WAP message during the process can save signaling overhead.

[0014] In another possible implementation, the address allocation capability indication information is carried in a Wireless Link State Protocol (WLS) message. If WLS is deployed in the communication domain to which the first node and the second node belong, carrying the address allocation capability indication information in the WLS message can save signaling overhead.

[0015] In another possible implementation, the address allocation capability indication information is carried in a non-link state routing protocol message. If a non-link state routing protocol is deployed in the communication domain to which the first node and the second node belong, the address allocation capability indication information is carried in a non-link state routing protocol message or a newly defined protocol message and can be published via broadcast or multicast. This allows information about the first node's address allocation capability to be communicated to more than just neighboring nodes.

[0016] Optionally, for the above-mentioned address allocation capability indication information used to indicate that the first node has address allocation capability, or the first node has address allocation agent capability, the above-mentioned method also includes: receiving a first message from the second node, the first message including a first address configuration message, and the first address configuration message is used to allocate or release a first communication address for the second node.

[0017] The first address configuration message may include first application information, requesting the allocation of the first communication address to the second node, i.e., requesting the allocation of a new communication address to the second node. Alternatively, the first address configuration message may include renewal information, requesting the renewal of the first communication address, i.e., requesting the renewal of an existing communication address. Alternatively, the first address configuration message may include release information, indicating the release of the first communication address, i.e., the second node proactively requesting the release of an existing communication address. Alternatively, the first address configuration message may include second application information, requesting the allocation of the first communication address to the second node when its current communication address is unavailable, i.e., requesting the allocation of a new communication address to the second node when the current communication address is unavailable. Alternatively, the first address configuration message may include confirmation information, indicating confirmation of use of the first communication address, i.e., confirmation of use of the allocated first communication address; or confirmation of release of the first communication address, i.e., upon receiving a message indicating the release of the first communication address, a first address configuration message is fed back, indicating confirmation of the release of the first communication address. By including different information in the address configuration message to indicate different requests, the overhead of the address configuration message can be reduced.

[0018] Furthermore, the first message also includes address type indication information for indicating the type of the first communication address. For example, the first address configuration message includes first application information, and the address type indication information is used to indicate the type of the first communication address requested for allocation, so that a node with address allocation capability can allocate the first communication address of that type.

[0019] The first communication address may be of a first address type or a second address type. The first address type is used for routing and forwarding within the communication domain or for identifying an application. The second address type is used to identify an application and may be an extensible address type, an IPv4 address type, or an IPv6 address type. The communication address used to identify an application may be understood as a service address.

[0020] The address length corresponding to the first address type is 2 bytes. When the type of the first communication address is the first address type, it is concise and short compared to other address types, which facilitates the transmission of more effective payloads in effective data frames and improves the payload ratio.

[0021] When the first communication address is an Internet Protocol version 4 (IPv4) address type or an Internet Protocol version 6 (IPv6) address type, it provides a basis for the deployment of IP applications in the Star Flash network. When the first communication address is an extensible address type, it is compatible with special addressing methods of special networks (such as the Internet of Things (IOT)).

[0022] When the first communication address is used to identify an application, it is specifically used to identify some or all applications on the second node, meaning that some or all applications share a service address. Alternatively, it is specifically used to identify a single application on the second node, meaning that one application can correspond to one service address. Alternatively, when the first communication address is an anycast address, it is specifically used to identify the first application on the second node and first applications on other nodes. In other words, for an anycast service address, the same application deployed on different nodes can share a single service address.

[0023] Furthermore, the above-mentioned first message also includes a message type, which is used to indicate whether the first message includes a first address configuration message, so that when the first address configuration message is included, the first node can perform address configuration-related operations, and when other messages are included, the first node performs other operations, which is beneficial to improving the execution efficiency of the first node.

[0024] In one possible implementation, the address allocation capability indication information is used to indicate that the first node has address allocation capability. After receiving the first message from the second node, the method further includes: sending a second message to the second node based on the first message, where the message type of the second message is the same as that of the first message. The second message is used to respond to the first message.

[0025] If the first address configuration message in the first message includes the first application information or the second application information, the second message may be as follows:

[0026] If the first node agrees to assign the first communication address to the second node, the second message includes the first communication address, so that the second node can learn the first communication address through the second message and then perform routing forwarding and / or identify applications on the second node based on the first communication address. Furthermore, the first node sets the status of the first communication address to allocated to manage the status of the communication address and reduce the probability of assigning the same communication address to two or more nodes. Furthermore, the second message also includes a second address configuration message, which may include consent information indicating that the first communication address has been assigned.

[0027] In the case that the first node refuses to allocate the first communication address to the second node, the second message does not include the first communication address but includes a second address configuration message. The second address configuration message may include rejection information for indicating the refusal to allocate the first communication address.

[0028] If the first address configuration message in the first message includes renewal information, the second message may be as follows:

[0029] If the first node agrees to renew the lease of the first communication address, the second message includes the lease time of the first communication address, allowing the second node to renew the lease of the first communication address without having to apply for a new communication address, thereby saving address space. Furthermore, the second message also includes a second address configuration message, which may include consent information indicating that the lease of the first communication address has been renewed.

[0030] In the case that the first node refuses to renew the lease of the first communication address, the second message includes a second address configuration message, and the second address configuration message may include rejection information for indicating that the lease renewal of the first communication address is refused.

[0031] In one possible implementation, the address allocation capability indication information is used to indicate that the first node has address allocation proxy capability. After receiving the first message from the second node, the method further includes: sending a third message to a third node based on the first message, the third message including a third address configuration message, the third address configuration message being used to allocate or release the first communication address for the second node. The message type of the third message is different from the message type of the first message.

[0032] The third node has an address allocation capability, and the third node is directly connected to the first node or not directly connected to the first node.

[0033] The third address configuration message may include first application information, requesting the allocation of the first communication address to the second node, i.e., requesting the allocation of a new communication address to the second node. Alternatively, the first address configuration message may include renewal information, requesting the renewal of the first communication address, i.e., requesting the renewal of an existing communication address. Alternatively, the third address configuration message may include release information, indicating the release of the first communication address, i.e., the second node proactively requesting the release of an existing communication address. Alternatively, the third address configuration message may include second application information, requesting the allocation of the first communication address to the second node when its current communication address is unavailable, i.e., requesting the allocation of a new communication address to the second node when the current communication address is unavailable. Alternatively, the third address configuration message may include confirmation information, indicating confirmation of use of the first communication address, i.e., confirmation of use of the allocated first communication address; or confirmation of release of the first communication address, i.e., upon receiving a message indicating the release of the first communication address, a first address configuration message is fed back, indicating confirmation of the release of the first communication address. By including different information in the address configuration message to indicate different requests, the overhead of the address configuration message can be reduced.

[0034] Furthermore, the third message also includes address type indication information for indicating the type of the first communication address. For example, the third address configuration message includes the first application information, and the address type indication information is used to indicate the type of the first communication address requested for allocation, so that the third node can allocate the first communication address of that type.

[0035] Furthermore, the third message further includes a message type, which is used to indicate whether the third message includes a third address configuration message, so that the third node can determine whether the third message includes the third address configuration message.

[0036] Furthermore, after sending the third message to the third node, the method further includes: receiving a fourth message from the third node, wherein the message type of the fourth message is the same as that of the third message, and the fourth message is used to respond to the third message.

[0037] If the third address configuration message in the third message includes the first application information or the second application information, the fourth message may be as follows:

[0038] If the third node agrees to assign the first communication address to the second node, the fourth message includes the first communication address. Furthermore, the third node sets the status of the first communication address to allocated, thereby managing the status of the communication address and reducing the probability of assigning the same communication address to two or more nodes. Furthermore, the fourth message also includes a fourth address configuration message, which may include consent information indicating that the first communication address has been assigned.

[0039] In the case that the third node refuses to allocate the first communication address to the second node, the fourth message does not include the first communication address but includes a fourth address configuration message. The fourth address configuration message may include rejection information for indicating rejection of allocation of the first communication address.

[0040] If the third address configuration message in the third message includes renewal information, the fourth message may be as follows:

[0041] If the third node agrees to renew the first communication address, the fourth message includes the lease time of the first communication address. Further, the fourth message also includes a fourth address configuration message, which may include consent information for indicating that the first communication address has been renewed.

[0042] In the case that the third node refuses to renew the lease of the first communication address, the fourth message includes a fourth address configuration message, and the fourth address configuration message may include rejection information for indicating that the lease renewal of the first communication address is refused.

[0043] Furthermore, after receiving the fourth message from the third node, the method further includes: sending a second message to the second node according to the fourth message, wherein the message type of the second message is the same as the message type of the first message and different from the message type of the fourth message.

[0044] If the fourth message includes the first communication address, then the second message includes the first communication address.

[0045] If the fourth message includes a fourth address configuration message and the fourth address configuration message includes approval information, then the second message includes a second address configuration message and the second address configuration message includes approval information. If the fourth message includes a fourth address configuration message and the fourth address configuration message includes rejection information, then the second message includes a second address configuration message and the second address configuration message includes rejection information. In other words, the content of the fourth message is the same as that of the second message.

[0046] In a second aspect, the present application provides a communication method, which is applied to a second node and can be executed by the second node or by a module in the second node, such as a chip or processor in the second node. The method may include receiving address allocation capability indication information from a first node, where the address allocation capability indication information is used to indicate the address allocation capability of the first node.

[0047] As can be seen, the second node learns the address allocation capability of the first node through the address allocation capability indication information, eliminating the need to search for nodes with address allocation capabilities through broadcast or multicast messages, thus saving radio resource overhead and time. Upon learning the address allocation capability of the first node, the second node can determine whether to initiate an address request to the first node, thereby reducing unnecessary address request messages and further saving radio resource overhead.

[0048] Optionally, the address allocation capability indication information is specifically used to indicate:

[0049] If the first node has the address allocation capability, the second node can initiate an address application to the first node to quickly obtain the allocated communication address.

[0050] Alternatively, the first node has the address allocation agent capability, and the second node can apply for a communication address from the node with the address allocation capability through the first node, so as to save wireless resource overhead.

[0051] Alternatively, if the first node does not have the address allocation capability, the second node does not apply for a communication address from the first node, nor does it apply for a communication address from a node with the address allocation capability through the first node, so as to reduce unnecessary address application messages.

[0052] In one possible implementation, the address allocation capability indication information is carried in a WAP message. The WAP message is transmitted during the process of establishing a neighbor relationship. In the process of establishing a neighbor relationship, carrying the address allocation capability indication information in the WAP message can save signaling overhead.

[0053] In another possible implementation, the address allocation capability indication information is carried in a WLS message. When WLS is deployed in the communication domain to which the first node and the second node belong, signaling overhead can be saved by carrying the address allocation capability indication information in the WLS message.

[0054] In another possible implementation, the address allocation capability indication information is carried in a non-link state routing protocol message. If a non-link state routing protocol is deployed in the communication domain to which the first node and the second node belong, the address allocation capability indication information is carried in a non-link state routing protocol message or a newly defined protocol message and can be published via broadcast or multicast. This allows information about the first node's address allocation capability to be communicated to more than just neighboring nodes.

[0055] Optionally, for the above-mentioned address allocation capability indication information being used to indicate that the first node has address allocation capability, or the first node has address allocation agent capability, the above-mentioned method also includes: sending a first message to the first node according to the above-mentioned address allocation capability indication information, the first message including a first address configuration message, and the first address configuration message being used to allocate or release a first communication address for the second node.

[0056] The first address configuration message may include first application information, requesting the allocation of the first communication address to the second node, i.e., requesting the allocation of a new communication address to the second node. Alternatively, the first address configuration message may include renewal information, requesting the renewal of the first communication address, i.e., requesting the renewal of an existing communication address. Alternatively, the first address configuration message may include release information, indicating the release of the first communication address, i.e., the second node proactively requesting the release of an existing communication address. Alternatively, the first address configuration message may include second application information, requesting the allocation of the first communication address to the second node when its current communication address is unavailable, i.e., requesting the allocation of a new communication address to the second node when the current communication address is unavailable. Alternatively, the first address configuration message may include confirmation information, indicating confirmation of use of the first communication address, i.e., confirmation of use of the allocated first communication address; or confirmation of release of the first communication address, i.e., upon receiving a message indicating the release of the first communication address, a first address configuration message is fed back, indicating confirmation of the release of the first communication address. By including different information in the address configuration message to indicate different requests, the overhead of the address configuration message can be reduced.

[0057] Furthermore, the first message also includes address type indication information for indicating the type of the first communication address. For example, the first address configuration message includes first application information, and the address type indication information is used to indicate the type of the first communication address requested for allocation, so that a node with address allocation capability can allocate the first communication address of that type.

[0058] The first communication address may be of a first address type or a second address type. The first address type is used for routing and forwarding within the communication domain or for identifying an application. The second address type is used to identify an application and may be an extensible address type, an IPv4 address type, or an IPv6 address type. The communication address used to identify an application may be understood as a service address.

[0059] The address length corresponding to the first address type is 2 bytes. When the type of the first communication address is the first address type, it is concise and short compared to other address types, which facilitates the transmission of more effective payloads in effective data frames and improves the payload ratio.

[0060] When the first communication address is an IPv4 address type or an IPv6 address type, it provides a basis for the deployment of IP applications in the Xingshan network. When the first communication address is an extensible address type, it is compatible with special addressing methods of special networks (such as IoT).

[0061] When the first communication address is used to identify an application, it is specifically used to identify some or all applications on the second node, meaning that some or all applications share a service address. Alternatively, it is specifically used to identify a single application on the second node, meaning that one application can correspond to one service address. Alternatively, when the first communication address is an anycast address, it is specifically used to identify the first application on the second node and first applications on other nodes. In other words, for an anycast service address, the same application deployed on different nodes can share a single service address.

[0062] Furthermore, the above-mentioned first message also includes a message type, which is used to indicate whether the first message includes a first address configuration message, so that when the first address configuration message is included, the first node can perform address configuration-related operations, and when other messages are included, the first node performs other operations, which is beneficial to improving the execution efficiency of the first node.

[0063] Furthermore, after sending the first message to the first node, the method further includes: receiving a second message from the first node, wherein the message type of the second message is the same as that of the first message, and the second message is used to respond to the first message.

[0064] If the first address configuration message in the first message includes the first application information or the second application information, the second message may be as follows:

[0065] If the first node agrees to assign the first communication address to the second node, the second message includes the first communication address, so that the second node can learn the first communication address through the second message and then perform routing forwarding and / or identify applications on the second node based on the first communication address. Furthermore, the first node sets the status of the first communication address to allocated to manage the status of the communication address and reduce the probability of assigning the same communication address to two or more nodes. Furthermore, the second message also includes a second address configuration message, which may include consent information indicating that the first communication address has been assigned.

[0066] In the case that the first node refuses to allocate the first communication address to the second node, the second message does not include the first communication address but includes a second address configuration message. The second address configuration message may include rejection information for indicating the refusal to allocate the first communication address.

[0067] If the first address configuration message in the first message includes renewal information, the second message may be as follows:

[0068] If the first node agrees to renew the lease of the first communication address, the second message includes the lease time of the first communication address, allowing the second node to renew the lease of the first communication address without having to apply for a new communication address, thereby saving address space. Furthermore, the second message also includes a second address configuration message, which may include consent information indicating that the lease of the first communication address has been renewed.

[0069] In the case that the first node refuses to renew the lease of the first communication address, the second message includes a second address configuration message, and the second address configuration message may include rejection information for indicating that the lease renewal of the first communication address is refused.

[0070] Optionally, for the second node having the address allocation agent capability, the above-mentioned address allocation capability indication information is used to indicate that the first node has the address allocation capability, and the above-mentioned method also includes: receiving a seventh message from the fourth node, the seventh message including a seventh address configuration message, and the seventh address configuration message is used to allocate or release the second communication address for the fourth node.

[0071] The fourth node is directly connected to the second node, and the second node can inform the fourth node through the address allocation capability indication information that the second node has the address allocation proxy capability. The seventh message is similar to the first message in the first aspect. Please refer to the detailed description of the first message in the first aspect and will not be repeated here.

[0072] Further, after receiving the seventh message, an eighth message is sent to the first node according to the seventh message. The eighth message is similar to the third message in the first aspect, and the detailed description of the first message in the first aspect can be referred to, which will not be repeated here.

[0073] Furthermore, after sending the eighth message to the first node, a ninth message is received from the first node. The ninth message is similar to the fourth message in the first aspect, and the detailed description of the fourth message in the first aspect can be referred to, which will not be repeated here.

[0074] Further, after receiving the ninth message from the first node, the tenth message is sent to the fourth node according to the ninth message. The eighth message is similar to the second message in the first aspect, and the detailed description of the second message in the first aspect can be referred to, which will not be repeated here.

[0075] Optionally, the method further includes: sending a query request message to a fifth node, the query request message including the third communication address, the third communication address being of the second address type, and the query request message being used to request a fourth communication address corresponding to the third communication address, the fourth communication address being of the first address type. The fifth node may provide a mapping query function.

[0076] In a third aspect, the present application provides a communication device, comprising a module or unit for executing the method as described in the first aspect or any one of the second aspects.

[0077] In one possible design, the communication device includes:

[0078] A processing unit, generating address allocation capability indication information;

[0079] The communication unit sends address allocation capability indication information to the second node, where the address allocation capability indication information is used to indicate the address allocation capability of the first node.

[0080] Optionally, the address allocation capability indication information is used to indicate that the first node has address allocation capability, the address allocation capability indication information is used to indicate that the first node has no address allocation capability, or the address allocation capability indication information is used to indicate that the first node has address allocation proxy capability.

[0081] Optionally, the address allocation capability indication information is carried in a wireless neighbor protocol message.

[0082] Optionally, the address allocation capability indication information is carried in a link state routing protocol message; or, the address allocation capability indication information is carried in a non-link state routing protocol message.

[0083] Optionally, the communication unit is further configured to receive a first message from the second node, where the first message includes a first address configuration message, and the first address configuration message is used to allocate or release a first communication address for the second node.

[0084] Optionally, the first address configuration message includes at least one of the following:

[0085] first application information, where the first application information is used to request allocation of a first communication address for the second node;

[0086] Renewal information, where the renewal information is used to request renewal of the first communication address;

[0087] Release information, where the release information is used to indicate the release of the first communication address;

[0088] Second application information, where the second application information is used to request allocation of a first communication address to the second node when the current communication address of the second node is unavailable;

[0089] Confirmation information, where the confirmation information is used to indicate confirmation of using the first communication address or confirmation of releasing the first communication address.

[0090] Optionally, the first message further includes address type indication information, where the address type indication information is used to indicate the type of the first communication address.

[0091] Optionally, the type of the first communication address is a first address type or a second address type, and the second address type is an extensible address type or an IPv4 address type or an IPv6 address type.

[0092] Optionally, the first address type is used for routing forwarding within the communication domain or for identifying an application, and the address length corresponding to the first address type is 2 bytes; the second address type is used to identify an application.

[0093] Optionally, when the first communication address is used to identify an application, it is specifically used to identify some or all applications on the second node, or it is specifically used to identify an application on the second node; or, when the first communication address is an anycast address, when the first communication address is used to identify an application, it is specifically used to identify the first application on the second node, as well as the first applications on other nodes.

[0094] Optionally, the first message further includes a message type, where the message type is used to indicate whether the first message includes a first address configuration message.

[0095] Optionally, the address allocation capability indication information is used to indicate that the first node has the address allocation capability; the communication unit is further used to send a second message to the second node based on the first message, and the message type of the second message is the same as the message type of the first message.

[0096] Optionally, the second message includes the first communication address.

[0097] Optionally, the processing unit is further configured to set the state of the first communication address to an allocated state.

[0098] Optionally, the second message includes a second address configuration message, and the second address configuration message includes at least one of the following:

[0099] The consent information and the allocation information are used to indicate that the first communication address has been allocated or the lease of the first communication address has been renewed;

[0100] The rejection information is used to indicate a rejection of allocating the first communication address or a rejection of renewing the lease of the first communication address.

[0101] Optionally, the address allocation capability indication information is used to indicate that the first node has address allocation agent capability; the communication unit is also used to send a third message to the third node based on the first message, the third message including a third address configuration message, and the third address configuration message is used to allocate or release the first communication address for the second node.

[0102] Optionally, the third address configuration message includes at least one of the following:

[0103] first application information, where the first application information is used to request allocation of a first communication address for the second node;

[0104] Renewal information, where the renewal information is used to request renewal of the first communication address;

[0105] Release information, where the release information is used to indicate the release of the first communication address;

[0106] Second application information, where the second application information is used to request allocation of a first communication address to the second node when the current communication address of the second node is unavailable;

[0107] Confirmation information, where the confirmation information is used to indicate confirmation of using the first communication address or confirmation of releasing the first communication address.

[0108] Optionally, the third message further includes address type indication information, where the address type indication information is used to indicate the type of the first communication address.

[0109] Optionally, the third message further includes a message type, where the message type is used to indicate whether the third message includes a third address configuration message.

[0110] Optionally, the message type of the third message is different from the message type of the first message.

[0111] Optionally, the communication unit is further configured to receive a fourth message from the third node, where the message type of the fourth message is the same as that of the third message.

[0112] Optionally, the fourth message includes the first communication address.

[0113] Optionally, the fourth message includes a fourth address configuration message, and the fourth address configuration message includes at least one of the following:

[0114] The consent information and the allocation information are used to indicate that the first communication address has been allocated or the lease of the first communication address has been renewed;

[0115] The rejection information is used to indicate a rejection of allocating the first communication address or a rejection of renewing the lease of the first communication address.

[0116] Optionally, the communication unit is further configured to send a second message to the second node based on the fourth message, where the message type of the second message is the same as that of the first message.

[0117] Optionally, the second message includes the first communication address.

[0118] Optionally, the second message includes a second address configuration message, and the second address configuration message includes at least one of the following:

[0119] The consent information and the allocation information are used to indicate that the first communication address has been allocated or the lease of the first communication address has been renewed;

[0120] The rejection information is used to indicate a rejection of allocating the first communication address or a rejection of renewing the lease of the first communication address.

[0121] Regarding the technical effects brought about by the third aspect and any possible implementation method, please refer to the introduction of the technical effects corresponding to the first aspect and the corresponding implementation method.

[0122] In another possible design, the communication device includes:

[0123] The communication unit is configured to receive address allocation capability indication information from the first node, where the address allocation capability indication information is used to indicate the address allocation capability of the first node.

[0124] Optionally, the address allocation capability indication information is used to indicate that the first node has address allocation capability, the address allocation capability indication information is used to indicate that the first node has no address allocation capability, or the address allocation capability indication information is used to indicate that the first node has address allocation proxy capability.

[0125] Optionally, the communication unit is further used to send a first message to the first node according to the address allocation capability indication information, where the first message includes a first address configuration message, and the first address configuration message is used to allocate or release a first communication address for the second node.

[0126] Optionally, the communication unit is further configured to receive a second message from the first node, where the message type of the second message is the same as that of the first message.

[0127] Optionally, the second message includes the first communication address.

[0128] Regarding the technical effects brought about by the third aspect and any possible implementation method, please refer to the introduction of the technical effects corresponding to the second aspect and the corresponding implementation method.

[0129] In a fourth aspect, embodiments of the present application provide a communication device comprising a processor. The processor is coupled to a memory and can be configured to execute instructions in the memory to implement the method of any of the first and second aspects described above and any possible implementation methods. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

[0130] In a fifth aspect, embodiments of the present application provide a communication device, comprising: a logic circuit and a communication interface. The communication interface is configured to receive or send information; the logic circuit is configured to receive or send information via the communication interface, so that the communication device executes the method of any of the first and second aspects above, and any possible implementation thereof.

[0131] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program (also referred to as code, or instructions); when the computer program runs on a computer, the method of any one of the above-mentioned first to second aspects and any possible implementation method is implemented.

[0132] In the seventh aspect, an embodiment of the present application provides a computer program product, which includes: a computer program (also referred to as code, or instructions); when the computer program is run, it enables the computer to execute any one of the above-mentioned first to second aspects and any possible implementation method.

[0133] In an eighth aspect, an embodiment of the present application provides a chip, comprising a processor configured to execute instructions. When the processor executes the instructions, the chip performs the method of any one of the first and second aspects and any possible implementation methods described above. Optionally, the chip further comprises a communication interface configured to receive or send signals.

[0134] In the ninth aspect, an embodiment of the present application provides a terminal device, which includes at least one communication device as described in the third aspect, or the communication device as described in the fourth aspect, or the communication device as described in the fifth aspect, or the chip as described in the eighth aspect.

[0135] In the tenth aspect, an embodiment of the present application provides a system, which includes a terminal device and at least one communication device as described in the third aspect, or the communication device as described in the fourth aspect, or the communication device as described in the fifth aspect, or the chip as described in the eighth aspect.

[0136] In addition, in the process of executing the method described in the first aspect and any possible embodiment, or the method described in the second aspect and any possible embodiment, the process of sending information and / or receiving information in the above method can be understood as the process of the processor outputting information, and / or the process of the processor receiving input information. When outputting information, the processor can output the information to the transceiver (or communication interface, or sending module) so that it can be transmitted by the transceiver. After the information is output by the processor, it may also need to undergo other processing before it reaches the transceiver. Similarly, when the processor receives input information, the transceiver (or communication interface, or sending module) receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, the information may need to undergo other processing before it is input into the processor.

[0137] Based on the above principles, for example, the sending of information mentioned in the above method can be understood as the processor outputting information. For another example, the receiving of information can be understood as the processor receiving input information.

[0138] Optionally, for the operations such as transmission, sending and receiving involved in the processor, if there is no special explanation, or if they do not conflict with their actual functions or internal logic in the relevant description, they can be more generally understood as processor output, reception, input and other operations.

[0139] Optionally, in the process of executing the method described in the first aspect and any possible embodiment, or the method described in the second aspect and any possible embodiment, the processor may be a processor specifically used to execute these methods, or a processor that executes these methods by executing computer instructions in a memory, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or may be separately provided on different chips. The embodiments of the present application do not limit the type of memory and the configuration of the memory and the processor.

[0140] In a possible implementation, the at least one memory is located outside the device.

[0141] In yet another possible implementation, the at least one memory is located within the device.

[0142] In another possible implementation, part of the at least one memory is located inside the device, and another part of the memory is located outside the device.

[0143] In this application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0144] In this application, a first node notifies a second node of its address allocation capability through address allocation capability indication information, eliminating the need for the second node to search for a node with address allocation capability through broadcast or multicast messages, thereby saving wireless resource overhead and time. The second node's knowledge of the first node's address allocation capability facilitates its determination of whether to initiate an address request from the first node, thereby reducing unnecessary address request messages and further saving wireless resource overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0145] FIG1 is a diagram showing several exemplary topologies of a communication domain;

[0146] Figure 2 is an example diagram of a wireless BMS scenario;

[0147] FIG3 is an example diagram of a smart home scene;

[0148] FIG4 is an example diagram of a topological structure of a mesh network provided by the present application;

[0149] FIG5 is a schematic diagram of a possible wireless communication system provided by the present application;

[0150] FIG6 is a flow chart of a communication method provided by the present application;

[0151] Figure 6-1 is an example diagram of a Node Capability TLV provided by this application;

[0152] FIG7 is a flow chart of another communication method provided by the present application;

[0153] Figure 7-1 is an example diagram of a GMP format provided by this application;

[0154] Figure 7-2 is an example diagram of the format of an address configuration message provided by this application;

[0155] Figure 7-3 is an example diagram of a TLV of an address configuration message provided by this application;

[0156] Figure 7-4 is an example diagram of address information provided by this application;

[0157] FIG8 is a flow chart of another communication method provided by the present application;

[0158] FIG9 is a flow chart of another communication method provided by the present application;

[0159] FIG10 is a flow chart of another communication method provided by the present application;

[0160] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0161] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0162] FIG13 is a schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0163] In this application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences. "And / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0164] It should be understood that, in this application, "at least one" refers to one or more, and "a plurality" refers to two or more. Furthermore, in this application, "equal to" can be used in conjunction with "greater than" or "less than." When "equal to" and "greater than" are used together, the technical solution of "greater than" is adopted; when "equal to" and "less than" are used together, the technical solution of "less than" is adopted.

[0165] The following first explains the relevant names or terms involved in this application to facilitate understanding by those skilled in the art.

[0166] 1. Node

[0167] A node is an electronic device with communication capabilities, also known as a communication node. For example, a node can include standalone devices such as handheld terminals, vehicles, on-board equipment, or network-side equipment, user equipment, access terminals, subscriber units, user stations, mobile stations, mobile stations, remote stations, remote terminals, wireless communication devices, user agents, or user devices. It can also be a component (such as a chip or integrated circuit) included in a standalone device. A node can be any possible intelligent terminal device (such as a mobile phone), intelligent transportation equipment (such as vehicles, drones, etc.), intelligent manufacturing equipment, smart home devices (such as large screens, speakers, printers, etc.), etc.

[0168] For example, when the node is an in-vehicle device, it can be a cockpit domain device or a module in the cockpit domain device, such as one or more modules such as a cockpit domain controller (CDC), a camera, a screen, a microphone, an audio system, an electronic key, a keyless entry and start system controller, etc. In a vehicle, the node can also be a wireless battery management system, or a battery management unit (BMU) or battery control unit (BCU) in a wireless battery management system.

[0169] For example, when the node is a handheld terminal, it can be a mobile phone, a wearable device, a tablet computer (pad), or a computer with data transceiver functions (such as a laptop computer, a PDA, etc.).

[0170] The nodes in this application can be applied to a variety of application scenarios, such as the following application scenarios: mobile internet (MI), industrial control, self-driving, transportation safety, Internet of Things (IoT), smart city, or smart home.

[0171] The nodes in this application can be applied to a variety of network types, such as one or more of the following network types: SparkLink, Long Term Evolution (LTE), Fifth Generation Mobile Communication Technology (5G), etc. th -generation mobile communication technology, 5G), wireless local area network (e.g., Wi-Fi), Bluetooth (BT), Zigbee, or in-vehicle short-range wireless communication network, etc.

[0172] In some application scenarios or certain network types, devices with similar communication capabilities may not be called nodes. However, for the convenience of description, in the embodiments of the present application, devices with communication capabilities are collectively referred to as nodes.

[0173] 2. Communication domain

[0174] A communication system (such as a Star Flash communication system) usually includes multiple nodes, and the nodes can communicate with each other to transmit data. Taking the in-vehicle communication system as an example, there can be multiple communication domains in the vehicle. A communication domain refers to a system composed of a group of nodes with a communication relationship and a communication connection relationship (i.e., a communication link) between the communication nodes, which is usually used to complete a specific function. For example, a communication domain may include a master node and at least one slave node, and the master and slave nodes, or the master node and the master node, or the slave node and the slave node can communicate with each other. The master node can manage the slave node, has the function of allocating resources, and is responsible for allocating resources to the slave node; the slave node obeys the scheduling of the master node, and uses the resources allocated by the master node to communicate with the master node and / or other nodes. For a communication domain, any two nodes in the communication domain can communicate based on the communication address.

[0175] In some specific implementation scenarios, the master node may also be called a grant (G) node, a G node, or a control node, and the slave node may also be called a terminal (T) or a T node. The communication link from a G node to a T node may be called a G link or a downlink, and the communication link from a T node to a G node may be called a T link or an uplink.

[0176] 3. Topology of the communication domain

[0177] For a communication domain, its topology can be a star single-hop topology, a tree three-layer multi-hop topology, or a tree multi-hop topology.

[0178] For example, see Figure 1(a) for a star-shaped single-hop topology. In Figure 1(a), communication domain 1 includes a G node and multiple T nodes (e.g., T1 node, T2 node, ..., Tn node), each of which is connected to a G node. Communication between G nodes and T nodes can be bidirectional unicast or G->T broadcast communication.

[0179] Optionally, the structure shown in Figure 1(a) can be applied to in-vehicle communication scenarios. For example, in an in-vehicle communication scenario, the G node can be a telematics box (T-BOX), and the T node can be a user terminal in the vehicle. The user terminal can be, for example, a mobile phone, headset, audio, or in-vehicle equipment. The T-BOX can also be called a remote in-vehicle terminal or an Internet of Vehicles communication terminal. For example, the T-BOX can establish a communication connection with a mobile phone to enable control of door opening and locking, window control, air conditioning, and other functions.

[0180] For example, see Figure 1(b) showing a tree-like three-layer multi-hop topology. In Figure 1(b), communication domain 2 includes G1, G2, G3, T1, T2, T3, and T4. T1 and T2 nodes are connected to G2, T3 and T4 nodes are connected to G3, and G2 and G3 nodes are connected to G1.

[0181] Node G1 can serve as the master management node, while nodes G2 and G3 can have dual identities. For example, for communication between G2 and G1, G2 can function as a T node, while G1 can function as a G node. For communication between G2 and T1, G2 can function as a G node, while T1 can function as a T node. A node with dual identities can be represented as G(T), meaning G2 can be represented as G2(T) and G3 as G3(T). In a tree-like, three-layer, multi-hop topology, communication between G and T nodes can be bidirectional unicast (for example, bidirectional unicast between G1 and T1 can be represented as G1-G2(T)-T1) or broadcast (for example, G1->G2(T)->T).

[0182] Optionally, the structure shown in (b) of Figure 1 can be applied to wireless BMS scenarios. The wireless BMS scenario can be seen in Figure 2. In Figure 2, the main control node serves as the main management node, the aggregation node is a node with dual identities, and the BMU in the BMS serves as a T node. The BCU in the BMS can serve as a G node. If the BCU is not working, the BMU continues to work, so the BCU is not shown in Figure 2. The structure shown in (b) of Figure 1 can also be applied to battery pack / cell storage scenarios, etc.

[0183] For example, see Figure 1(c) for a tree-like multi-hop topology. In Figure 1(c), communication domain 2 includes G1, G2, G3, G4, T1, T2, and T3 nodes. T1 connects to G2, T2 connects to G4, G4 connects to G2 and G3, G2 connects to G1, and G3 connects to G1. G1 serves as the master management node, while G2, G3, and G4 can be dual-identity nodes.

[0184] Optionally, the structure shown in Figure 1(c) can be applied to smart home scenarios. A smart home scenario can be seen in Figure 3. In Figure 3, the gateway / customer premises equipment (CPE) serves as the master management node, the sub-routers, large screens, mobile phones, and air conditioners serve as nodes with dual identities, and the water heater, smart curtains, speakers, microphones, printers, and smart door locks serve as T-nodes. In a smart home scenario, T-nodes may have IP addresses (e.g., the printer in Figure 3 has an IP address) or not (e.g., the water heater, smart curtains, and smart door locks in Figure 3 do not have IP addresses); G(T) nodes may have IP addresses (e.g., the sub-router in Figure 3 has an IP address) or not (e.g., the air conditioner in Figure 3 does not have an IP address). The structure shown in Figure 1(c) can also be applied to low-power large-scale sensor networks. For example, in such low-power large-scale sensor networks, the root node can serve as the master management node, the backbone nodes can serve as G(T), and the end nodes can serve as T-nodes.

[0185] The following is an introduction to the application scenarios and system architecture of this application.

[0186] Please refer to Figure 4, which is an example diagram of a mesh network topology provided in this application. The topology shown in Figure 4 includes M nodes 401, I nodes 402 to 407, and E nodes 408 to 414. Optionally, the topology also includes A nodes 415. It should be noted that the number of nodes shown in Figure 4 is for illustrative purposes only and does not constitute a limitation of this application.

[0187] Among them, I node refers to an intermediate node or an intermediate routing node, which can be understood as an address allocator or an address resolver or an address applicant, and can also be understood as a data message sender or receiver, and has the ability to forward data messages in the network. The I node can be, for example, a wireless intermediate system (WIS) node. As an address allocator, the I node has address allocation capability or address allocation agent capability. The address allocation capability refers to the ability to allocate addresses, and the address allocation agent capability refers to the inability to allocate addresses, but the ability to relay address applications and address allocations for other nodes. As an address applicant, the I node can apply for a communication address for itself. The I node can also act as an address application agent and apply for communication addresses for other nodes (such as adjacent nodes).

[0188] An E-node refers to an end node, which can be understood as an address requester or a data message sender or receiver, but does not have the ability to forward data messages within the network. For example, an E-node can be a wireless end system (WES) node. I-nodes and E-nodes are physical nodes or units, which can be understood as actual nodes or units.

[0189] M-node 401 plays the role of manager. During network initialization, it is injected with allocable address types and address spaces. M-node 401 primarily handles address allocation. To ensure the reliability of network management, one or more backup M-nodes may also exist in the network. An M-node is a functional node, functional unit, logical node, or logical unit, and can be understood as a virtual node or unit. The functions of M-node 401 can be implemented through an I-node, which means that the I-node has address allocation capabilities. The essence of an M-node is an I-node. An M-node can also be described as a manager node.

[0190] A node 415 refers to an address resolution (Address Resolver) node, which mainly provides mapping query functions, such as the mapping query function between a non-Spark Link Network Address and a Spark Link Network Address (SLNA). The two parties communicating with a non-Spark Link Network Address can query each other's Spark Link Network Address from A node 415 to build a Spark Link Network layer message based on the Spark Link Network Address, and perform addressing and forwarding through the Spark Link Network Address. A node is a functional node, functional unit, logical node or logical unit, and can be understood as a virtual node or unit. The function of A node 415 can be implemented through a certain I node, that is, the I node has a mapping query function, and the essence of A node is an I node. A node can also be described as an address resolver node.

[0191] It should be noted that a certain I node can have the function of an M node and also have the function of an A node; or, one I node has the function of an M node and another I node has the function of an A node.

[0192] It is understandable that the network shown in Figure 4 can be a communication domain, and the several topologies shown in Figure 1 can be subsets of the topology shown in Figure 4. For example, nodes G1, G2, and G3 in Figure 1(b) can be I nodes in Figure 4, and nodes T1 through T4 in Figure 1(b) can be E nodes in Figure 4. Node G1 can function as an M node. Furthermore, the master control node and aggregation node in Figure 2 can function as I nodes, and the master control node can function as an M node; the BMU can function as an E node, requesting a communication address from the master control node. The gateway / CPE, sub-routers, large screens, mobile phones, and air conditioners in Figure 3 can function as I nodes, and the gateway / CPE can function as an M node; the water heater, smart curtains, and smart door locks can function as E nodes, requesting a communication address from the gateway / CPE.

[0193] Furthermore, the embodiments of the present application can be applied to in-vehicle communication scenarios, wireless BMS scenarios (as shown in Figure 2), battery pack / cell storage scenarios, smart home scenarios (as shown in Figure 3), smart cockpits, smart driving, smart manufacturing, smart transportation and other smart application scenarios.

[0194] For example, the communicating nodes include a first node and a second node. Figure 5 is a schematic diagram of a possible wireless communication system provided by the present application, which includes a first node 501 and a second node 502. Taking a communication domain including an M node as an example, the combination of the first node 501 and the second node 502 can be any of the following:

[0195] Mode 1: The first node 501 has the function of an M-node, and the second node 502 is a directly connected node of the first node 501, which can be an I-node or an E-node. The second node 502 can apply to the first node 501 for its communication address.

[0196] Mode 2: The wireless communication system shown in FIG5 further includes a third node having M-node functionality. The third node is directly or indirectly connected to the first node 501 having address allocation agent capability. The second node 502 for applying for a communication address is directly connected to the first node 501. The first node 501 can apply for a communication address from the third node on behalf of the second node 502. The first node 501 can be an I-node, and the second node 502 can be an I-node or an E-node.

[0197] Mode 3: The wireless communication system shown in Figure 5 also includes a third node for applying for a communication address. The third node is directly connected to a second node 502 with address allocation agent capabilities. Second node 502 is directly or indirectly connected to a first node 501 with M-node functionality. Second node 502 can apply for a communication address from first node 501 on behalf of the third node. Second node 502 can be an I-node, and the third node can be an I-node or an E-node.

[0198] It should be understood that the wireless communication system may include more nodes, which are shown here as a first node and a second node for the convenience of description.

[0199] Within a communication domain, there's no clear solution for how adjacent nodes can determine each other's address allocation capabilities. Therefore, this application provides a communication method and apparatus that can indicate a node's address allocation capabilities to facilitate communication address allocation. Before introducing the communication method, we'll discuss the communication addresses provided in this application.

[0200] This application provides the following types of communication addresses:

[0201] (1) Star Flash Network Address (SLNA), used for routing and forwarding within the communication domain. That is, routing and forwarding are performed based on SLNA within the communication domain, that is, each node within the communication domain needs to be configured with SLNA, and SLNA can be considered as the default address type. SLNA can also be understood as a network-manageable address. SLNA can also be described as a Star Flash base address or base address. SLNA can also be used to identify applications, that is, as a service address. For example, the type of SLNA is called type 1 (type 1), and its byte length is 2 bytes.

[0202] (2) Extensible address, used to identify the application, i.e., as a service address. The extensible address can be understood as a user-defined address type, and its byte length is variable from 1 to 16 bytes. For example, the extensible address type is called type 2.

[0203] (3) IPv4 address, used to identify an application, i.e., as a service address. The maximum byte length of an IPv4 address is 4 bytes. For example, the type of IPv4 address is called type 4.

[0204] (4) IPv6 address, used to identify an application, i.e., as a service address. The maximum byte length of an IPv6 address is 16 bytes. For example, the type of IPv6 address is called type 6.

[0205] Among them, the identification application can describe the identification application service, etc. All four types of addresses can be used as service addresses. For ease of distinction, this application uses the type of Star Flash network address as the first address type, and the types of scalable addresses, IPv4 addresses, and IPv6 addresses as the second address type, that is, non-Star Flash network addresses.

[0206] SLNA can be divided into unicast, multicast, broadcast, and anycast types. For example, the address ranges corresponding to different types are as follows:

[0207] a. Unicast: The address range is 0.0 to 127.255, where:

[0208] 0.0: Not used as a communication address for a node, but as a default routing address in network routing addressing;

[0209] 127.1: as the local loopback address;

[0210] 127.2: The default unicast address for all M nodes (Manager Node Anycast Address).

[0211] 127.3: The default unicast address for all A nodes (Address Resolver Node Anycast Address);

[0212] 127.4 to 127.255: Reserved for future use.

[0213] b. Multicast: The address range is 128.0 to 200.255, where:

[0214] 128.0: All Manager Nodes Multicast Address (AMMA)

[0215] 128.1: The multi-hop multicast address listened to by all A nodes (All Address Resolver Nodes Multicast Address);

[0216] 128.2: All WIS Nodes Multicast Address (WIS Nodes Multicast Address)

[0217] 128.3: All WES Nodes Multicast Address (ALL WES Nodes Multicast Address)

[0218] 128.4: Link Local WIS Nodes Multicast Address (LLW Nodes Multicast Address) is a single-hop multicast address listened to by intermediate nodes within the link local range.

[0219] 128.5: Link Local WES Nodes Multicast Address (LLWES Nodes Multicast Address)

[0220] 128.6 to 128.255: Reserved for protocol extension.

[0221] c. Broadcast: The broadcast address is 255.255.

[0222] d. Reserved: The address range is 201.0 to 255.254.

[0223] A node in a communication domain can apply for a separate service address for its application, reuse the node's SLNA, or share a single service address for multiple applications. The same application deployed on different nodes can use the same service address, which is an anycast address. Applications use a publish-and-subscribe model, and multiple nodes can apply for the same multicast address.

[0224] The communication method provided by this application is introduced below.

[0225] Please refer to FIG6 , which is a flowchart of a communication method provided by the present application. The method may include but is not limited to the following steps:

[0226] S601: A first node generates address allocation capability indication information.

[0227] Among them, the address allocation capability indication information is used to indicate the address allocation capability of the first node, for example, indicating whether the first node has the address allocation capability, or whether it has the address allocation agent capability. Furthermore, the address allocation capability indication information indicates that the first node has the address allocation capability, or is used to indicate that the first node does not have the address allocation capability, or is used to indicate that the first node has the address allocation agent capability. The first node has the address allocation capability, indicating that the first node can allocate addresses for other nodes, for example, it can allocate SLNA or service addresses for other nodes. The first node has the address allocation agent capability, indicating that the first node cannot allocate addresses for other nodes, but can relay address applications and address allocation for other nodes. The first node does not have the address allocation capability, indicating that the first node can neither allocate addresses for other nodes nor relay address applications and address allocation for other nodes.

[0228] Exemplarily, the address allocation capability indication information may be indicated using a 2-bit value. For example, a value of 00 indicates that the first node has no address allocation capability; a value of 01 indicates that the first node has address allocation capability; a value of 10 indicates that the first node has address allocation proxy capability; and a value of 11 indicates that the information is reserved.

[0229] Optionally, the first node may generate address allocation capability indication information according to whether it has address allocation capability.

[0230] S602: The first node sends address allocation capability indication information to the second node. Correspondingly, the second node receives the address allocation capability indication information from the first node.

[0231] The second node is directly connected to the first node. In other words, the second node is a neighbor of the first node. The first node sends address allocation capability indication information to the second node. This information can be understood as the first node informing the second node of its address allocation capabilities through the address allocation capability indication information. Neighboring nodes use the address allocation capability indication information to inform each other of their address allocation capabilities so they can determine whether to initiate an address request.

[0232] In a first implementation, the address allocation capability indication information is carried in a wireless adjacency protocol (WAP) message. The message can also be described as a protocol data unit (PDU). That is, in the process of establishing a neighbor relationship between a first node and a second node, the first node sends a WAP PDU to the second node, and the WAP PDU carries the address allocation capability indication information. Optionally, the WAP PDU can be a hello PDU. The hello PDU includes a node capability (Node Capability) type-length-value (TLV). The definition of the Node Capability TLV can be shown in Figure 6-1.

[0233] For example, based on Figure 6-1 , the Node Capability TLV definition may include at least one of the following:

[0234] Type (1 byte in length) indicates the type of the Node Capability TLV, for example, Type 4.

[0235] Length (1 byte), used to indicate the length of the Node Capability TLV, with a value range of 0 to 255.

[0236] Node Capability Sub-TLVs (variable byte length) are used to represent an extensible set of node capabilities.

[0237] It should be noted that the Node Capability TLV appears only once in a Hello PDU. The Hello PDU sent by the first node (I-node or E-node) contains only one Node Capability TLV. If the Hello PDU received by the second node (I-node or E-node) contains more than one Node Capability TLV, the second node discards the Hello PDU.

[0238] The above-mentioned extensible node capability set may include one or more node sub-TLVs. For example, the Node General Capability Sub TLV may include address allocation capability indication information. The Node General Capability Sub TLV may indicate the Node General Capability Sub TLV of the first node. The Node General Capability Sub TLV definition may include at least one of the following:

[0239] Sub-Type: 1 byte, indicating the type of the Node General Capability Sub TLV, for example, Type 1.

[0240] Length (1 byte), indicating the length of the Node General Capability Sub TLV, ranging from 0 to 255.

[0241] The A field occupies 2 bits. The value of these 2 bits indicates the address allocation capability. For example, a value of 00 indicates no address allocation capability; a value of 01 indicates address allocation capability; a value of 10 indicates address allocation proxy capability; and a value of 11 is reserved.

[0242] It should be noted that the Node General Capability Sub TLV appears only once in the hello PDU. If the hello PDU received by the second node (I node or E node) contains more than one Node General Capability Sub TLV, the second node discards the hello PDU.

[0243] In the second implementation, the address allocation capability indication information is carried in a link state routing protocol (Wireless link state protocol, WLS) message, such as a link state message (link state PDU). That is, the first node publishes the address allocation capability indication information in its link state message. When the second node receives the link state message, it records the address allocation capability of the first node. Optionally, the link state message includes a Node Capability TLV. The definition of the Node Capability TLV can be found in Figure 6-1. For details, please refer to the description of it in the first implementation. The prerequisite for the second implementation is that the communication domain (including the first node and the second node) is deployed with WLS, that is, this implementation relies on the network routing protocol of the communication domain being WLS.

[0244] In the third implementation, the address allocation capability indication information is carried in a non-link state routing protocol message, and the non-link state routing protocol is, for example, an on-demand distance vector routing (AODV) protocol. The prerequisite for the third implementation is that the communication domain (including the first node and the second node) is deployed with a non-link state routing protocol (such as AODV, etc.), that is, the implementation depends on the network routing protocol of the communication domain being a non-link state routing protocol. For non-link state routing protocols, a new protocol PDU can be defined to publish address allocation capability indication information, for example, its publishing method can be a broadcast publishing method or a multicast publishing method, etc. This application uses the non-link state routing protocol message as an example to describe the new protocol PDU, and other names may be used to describe it in actual applications. Optionally, the non-link state routing message includes a Node Capability TLV. The definition of the Node Capability TLV can be found in Figure 6-1, and for details, please refer to the description of it in the first implementation.

[0245] The above three implementation methods are used for example only and do not constitute a limitation to the present application. In actual applications, the address allocation capability indication information may be carried in other PDUs.

[0246] In the embodiment shown in Figure 6, neighboring nodes inform each other of their address allocation capabilities through address allocation capability indication information, eliminating the need to search for nodes with address allocation capabilities through broadcast or multicast messages, thus saving radio resource overhead and time. A second node's knowledge of the first node's address allocation capability facilitates its decision to initiate an address request from the first node, reducing unnecessary address request messages and further saving radio resource overhead.

[0247] Taking a communication domain including an M node as an example, the combination of the address allocation capability of the first node and the address allocation capability of the second node can be:

[0248] In mode (1), the first node has the address allocation capability, and the second node does not have the address allocation capability. The first node may be an I-node with the function of an M-node, and the second node may be an I-node or an E-node without the address allocation capability.

[0249] In mode (2), the first node has the address allocation proxy capability, and the second node does not have the address allocation capability. The first node can be an I-node with the address allocation proxy capability, and the second node can be an I-node or an E-node without the address allocation capability. In mode (2), the communication domain also includes a third node with the address allocation capability, that is, the third node can be an I-node with the function of an M-node. The third node can be directly connected to the first node or not directly connected.

[0250] In mode (3), the first node has an address allocation capability, and the second node has an address allocation proxy capability. The first node may be an I-node with the functionality of an M-node, and the second node may be an I-node with the address allocation proxy capability. Optionally, in mode (3), the communication domain may further include a fourth node without an address allocation capability, the fourth node being directly connected to the second node. The fourth node may be an I-node or an E-node.

[0251] In mode (4), both the first node and the second node have no address allocation capability. The first node can be an I-node or an E-node, and the second node can be an I-node or an E-node.

[0252] For the above-mentioned methods (1) to (3), the communication address application process can be further executed. For method (1), the second node directly applies for a communication address from the first node, as shown in the embodiment of Figure 7. For method (2), the second node can apply for a communication address from the third node through the first node, as shown in the embodiment of Figure 8. For method (3), the fourth node can apply for a communication address from the first node through the second node, which is similar to method (2).

[0253] Please refer to Figure 7, which is a flowchart of another communication method provided by this application. In Figure 7, the first node has the function of an M node (i.e., has address allocation capability), the second node is a newly added I node or E node (not yet assigned a communication address), and the second node is directly connected to the first node. The method shown in Figure 7 may include, but is not limited to, the following steps:

[0254] S701: A first node sends address allocation capability indication information to a second node. Correspondingly, the second node receives the address allocation capability indication information from the first node, wherein the address allocation capability indication information indicates that the first node has address allocation capability.

[0255] S702: The second node sends a first message to the first node. Correspondingly, the first node receives the first message from the second node. The first message includes a first address configuration message, which is used to allocate a first communication address to the second node.

[0256] When the second node learns that the first node has the address allocation capability, the second node sends a first message to the first node. The message type of the first message may be a general message PDU (GMP). GMP is used for one-hop communication between a node and a directly connected node when there is no communication address, and is limited to one-hop communication. The prerequisite is that the two nodes using GMP communication have established a neighbor relationship. A legitimate neighbor relationship means that the security authentication has been passed. Compared with the Dynamic Host Configuration Protocol (DHCP) message, GMP can reduce wireless resource overhead. Compared with the IPv6 Neighbor Discovery Protocol message, GMP can reduce wireless resource overhead.

[0257] For example, referring to the format of a GMP shown in FIG. 7-1 , the format may include at least one of the following fields:

[0258] Network Layer Protocol Identifier, used to identify GMP;

[0259] Version: used to identify the version number of GMP, such as Version 1;

[0260] Message Type: This field indicates the type of message carried by the GMP. For example, a message type of 1 indicates that the information carried by the GMP is an Address Configuration Message.

[0261] Source System ID, which is the local system ID.

[0262] Source Interface ID, which is the air interface ID used to send the packet locally.

[0263] PDU Length: The length of the entire message, including the header.

[0264] Checksum: the checksum of the entire message;

[0265] Sequence Number, to prevent replay attacks;

[0266] Variable length fields. For example, when the Message Type is 1, the variable length fields carry the contents of the Address Configuration Message.

[0267] For example, see FIG. 7-2 for a format of an address configuration message, which may include at least one of the following fields:

[0268] Message Type, for example, 1, indicating that the message is an address configuration message;

[0269] Message Length: indicates the length of the address configuration message, which is represented by 2 bytes.

[0270] Original Requester System ID

[0271] Manager Address: The address of the M node responsible for allocating addresses. This field can be 0 when the message sent by the requesting end (the node requesting a communication address) carries an address configuration message.

[0272] Variable length fields: various TLVs in address configuration messages.

[0273] For example, referring to FIG. 7-3 , a TLV of an address configuration message may include at least one of the following fields:

[0274] Address Configuration Length

[0275] The M field occupies 1 bit. For example, when the value of this bit is 0, it indicates a unicast address; when the value of this bit is 1, it indicates a multicast address.

[0276] Address Type (also known as Address Family) indicates the type of communication address being applied for, released, or renewed. There are four types of addresses: SLNA (type 1); Scalable Address (type 2); IPv4 Address (type 4); and IPv6 Address (type 6).

[0277] A field. The value of the A field indicates the address configuration action. For example:

[0278] The value of the -A field is 0, indicating the first application information (apply), which is used by the requesting end to request allocation of a new communication address;

[0279] The value of the -A field is 1, indicating renewal information (renew lease), which is used by the requesting end to request renewal of an existing communication address;

[0280] The value of the -A field is 2, indicating the acknowledgement information (ack), which is used to indicate that the responding end agrees to allocate or renew the communication address; or used to indicate that the responding end has allocated or renewed the communication address;

[0281] The value of the -A field is 3, indicating a rejection message (nck), which is used to indicate that the responding end refuses to allocate or renew the communication address;

[0282] The value of the -A field is 4, indicating release information (release), which is used by the requesting end to instruct the release of the communication address, that is, the requesting end actively requests the release of the communication address;

[0283] The value of the -A field is 5, indicating the second application information (reapply), which is used by the requesting end to request allocation of a new communication address when the current communication address conflicts or is unavailable.

[0284] The value of the -A field is 6, indicating confirmation information (confirm), which is used to instruct the requesting end to confirm the use of the allocated communication address or to confirm the release of the communication address. (The requesting end refers to the node that requests the allocation of the communication address, which can also be described as the client, etc.; the responding end refers to the node that allocates the communication address, which can also be described as the server, etc.)

[0285] The request transaction number (Transaction Number) distinguishes different requests (for example, applying for a communication address or releasing a communication address). The response message also needs to carry the transaction number to identify the specific request being responded to.

[0286] Service Information Length: indicates the length of the next service information;

[0287] Service Information: Descriptive information about the service, such as the application ID. If this field is left blank, it indicates that the communication address is not for a specific application, but can be used for multiple purposes and is not an anycast address. If the communication address is an anycast address, the Service Information field cannot be empty.

[0288] Lease Period: The lease period for the communication address, in seconds. When applying for a communication address, the lease period must be at least 300 seconds.

[0289] Address Number: When applying for a communication address, it indicates how many communication addresses need to be applied for; when renewing a lease or not applying for a communication address, it indicates how many subsequent address information (Address Information) there are;

[0290] Address information list (Address information List), which may include one or more address information.

[0291] For example, see the address information shown in Figure 7-4, which includes address information for four address types. For example, for SLNA (address type = 1, i.e., type = 1), the address information includes the specific SLNA. For another example, for an extensible address (address type = 1, i.e., type = 1), the address information includes the address prefix length and address prefix of the extensible address.

[0292] The first message, such as the first GMP, includes a first address configuration message, which includes first application information for requesting allocation of a new communication address, such as the first communication address, for the second node. For example, based on Figure 7-3, the value of the A field in the first address configuration message is 0.

[0293] Optionally, the first message also includes address type indication information, which indicates the type of the communication address requested for allocation, i.e., the type of the first communication address. For example, based on Figure 7-3, the first address configuration message also includes an address type (Address Type). In the embodiment shown in Figure 7, the type of the first communication address is SLNA. In other words, the newly joined node applies for SLNA for the first time in order to perform routing and forwarding within the communication domain based on SLNA. Therefore, based on Figure 7-3, the address type in the first address configuration message is type1.

[0294] Optionally, the first message also includes a message type, which is used to indicate whether the first message includes the first address configuration message. For example, based on Figure 7-1, a message type of 1 indicates that the first message includes the first address configuration message; other values ​​of the message type indicate that the first message does not include the first address configuration message.

[0295] S703: The first node allocates a first communication address to the second node, and sets the state of the first communication address to an allocated state.

[0296] When the first node receives the first message, it determines whether the first communication address can be allocated to the second node. If the first communication address can be allocated to the second node, it allocates the first communication address to the second node. After the allocation, the state of the first communication address is set to the allocated state so that the first node can manage the communication addresses of each node.

[0297] Optionally, the first message also includes a lease period, indicating the duration of the application to lease the first communication address. For example, based on Figure 7-3, the first address configuration message also includes a lease period. The second node can set the available lease period for the first communication address based on the lease period. For example, if the lease period carried in the first message is 350 seconds, the second node can set the available lease period to 350 seconds or 400 seconds, depending on the specific situation.

[0298] S704: The first node sends a second message to the second node. Correspondingly, the second node receives the second message from the first node. The second message includes the first communication address.

[0299] After allocating the first communication address to the second node, the first node sends a second message to the second node, wherein the message type of the second message is the same as that of the first message, which may be GMP.

[0300] The second message includes a second address configuration message, which includes consent information indicating that the first communication address has been assigned. For example, based on Figure 7-3 , the value of the A field in the second address configuration message is 2. The second message also includes the first communication address. For example, based on Figure 7-4 , the address information list in the second address configuration message includes the SLNA of the second node.

[0301] Optionally, the second message also includes the leaseable time of the first communication address.

[0302] S705: The second node saves and validates the first communication address.

[0303] When the second node receives the second message, it obtains the first communication address from the second message and saves the first communication address. Validating the first communication address can be understood as using the first communication address for routing and / or forwarding when routing and / or forwarding is required.

[0304] S706: The second node sends a fifth message to the first node. Correspondingly, the first node receives the fifth message from the second node, wherein the fifth message includes a fifth address configuration message.

[0305] The message type of the fifth message is the same as that of the first message, which may be GMP.

[0306] The fifth message includes a fifth address configuration message, and the fifth address configuration message includes confirmation information, which is used to indicate confirmation of using the first communication address. For example, based on Figure 7-3, the value of the A field in the fifth address configuration message is 6.

[0307] S707: The first node sets the state of the first communication address to a leased state.

[0308] When the first node receives the fifth message, it sets the state of the first communication address to a leased state, so that the first node manages the communication addresses of various nodes.

[0309] In the embodiment shown in Figure 7, upon learning that the first node has address allocation capability, the second node requests the first node to allocate an SLNA for the second node. This allows the second node to dynamically obtain the SLNA, facilitating management or control of the second node by the first node. The SLNA is concise and compact, allowing more payload to be transmitted within valid data frames, improving the payload ratio.

[0310] Figure 7 uses the example of a first node agreeing to allocate a first communication address to a second node. If the first node refuses to allocate the first communication address to the second node, the second address configuration message in the second message includes rejection information, indicating the refusal to allocate the first communication address. For example, based on Figure 7-3, the value of the A field in the second address configuration message is 3. Consequently, steps S705 through S707 are not executed. Optionally, after receiving the second message, the second node may resend the first message to the first node to request a communication address.

[0311] Please refer to Figure 8, which is a flow chart of another communication method provided by the present application. In Figure 8, the third node has the function of an M node (i.e., has address allocation capability), the second node is a newly added I node or E node (not yet assigned a communication address), and the first node has address allocation agent capability; the first node is directly connected or not directly connected to the third node, and the second node is directly connected to the first node. The method shown in Figure 8 may include, but is not limited to, the following steps:

[0312] S801: A first node sends address allocation capability indication information to a second node. Correspondingly, the second node receives the address allocation capability indication information from the first node. The address allocation capability indication information indicates that the first node has address allocation agent capability.

[0313] S802: The second node sends a first message to the first node. Correspondingly, the first node receives the first message from the second node. The first message includes a first address configuration message, which is used to allocate a first communication address to the second node.

[0314] Upon learning that the first node has the address allocation proxy capability, the second node sends a first message to the first node, requesting the first node to apply for a relay address for it. The first message may be of the GMP type. The format of the GMP and the first message are described in detail in the embodiment shown in FIG7 , and are not further described here.

[0315] S803: The first node generates a third message according to the first message, wherein the third message includes a third address configuration message, and the third address configuration message is used to allocate a first communication address to the second node.

[0316] Upon receiving the first message, the first node extracts the first address configuration message from the first message (i.e., decapsulates the first message to obtain the first address configuration message) and encapsulates the first address configuration message into a third message. The third message includes the third address configuration message, and the content carried by the third address configuration message is the same as the content carried by the first address configuration message.

[0317] Among them, the message type of the third message is different from the message type of the first message, and the message type of the third message can be an address configuration protocol (ACP) message. ACP is a protocol that works on the connection-less transport protocol (CLTP) of Star Flash, adopts a client-server mode, and has an independent port number (for example, the client's port number is 5, and the server's port number is 6). ACP is defined between the address application agent and the address allocator to apply for and configure the address, that is, ACP is defined between a node with address allocation agent capability and a node with address allocation capability to apply for and configure the address (for example, address renewal).

[0318] The address application agent is responsible for encapsulation and decapsulation and does not record the address applicant's communication address. In other words, the address application agent is stateless. For the address allocator, the stateful data it records can be kept as minimal as possible to reduce the address allocator's burden. For example, it records the correspondence between the address applicant and their communication address, and optionally records the communication address status (e.g., allocated or leased).

[0319] Compared to DHCP messages, ACP messages can reduce wireless resource overhead. Compared to IPv6 Neighbor Discovery Protocol messages, ACP messages can reduce wireless resource overhead and support multi-hop wireless link access to the network.

[0320] The prerequisites for a node with address allocation capability to allocate a communication address to an indirect-connected node, that is, the prerequisites for a third node to allocate a first communication address to a second node, include:

[0321] A. After the third node establishes a neighbor relationship with the first node, the first node has been configured with SLNA;

[0322] B. The first node has learned the SLNA of the third node.

[0323] The first node can obtain the SLNA of the third node through method a or method b. In method a, the third node has a default anycast address (unicast) (Manager Node Anycast Address), for example, 127.2. This anycast address is known to all nodes with address allocation agent capabilities. In method b, when the third node does not use the default anycast address, the first node records the unicast address of the first node when applying for an SLNA for the third node.

[0324] The second node can also obtain the SLNA of the third node through the above method a.

[0325] S804: The first node sends a third message to the third node. Correspondingly, the third node receives the third message from the first node.

[0326] The third message includes a third address configuration message, which includes the first application information and is used to request allocation of a new communication address, such as the first communication address, to the second node. For example, based on Figure 7-3 , the value of the A field in the third address configuration message is 0.

[0327] Optionally, the third message also includes address type indication information, which indicates the type of the communication address requested for allocation, i.e., the type of the first communication address. For example, based on Figure 7-3, the third address configuration message also includes an address type (Address Type). In the embodiment shown in Figure 7, the type of the first communication address is SLNA. In other words, the newly joined node applies for SLNA for the first time in order to perform routing and forwarding within the communication domain based on SLNA. Therefore, based on Figure 7-3, the address type in the third address configuration message is type 1.

[0328] Optionally, the third message also includes a message type (Message type), which is used to indicate whether the third message includes a third address configuration message. For example, based on Figure 7-1, a Message type of 1 indicates that the third message includes a third address configuration message; other values ​​of Message type indicate that the third message does not include a third address configuration message.

[0329] S805: The third node allocates a first communication address to the second node and sets the state of the first communication address to allocated. For step S805, reference may be made to the detailed description of step S703 in the embodiment shown in FIG7, and will not be repeated here.

[0330] S806: The third node sends a fourth message to the first node. Correspondingly, the first node receives the fourth message from the third node, wherein the fourth message includes the first communication address.

[0331] After allocating the first communication address to the second node, the third node sends a fourth message to the first node, wherein the message type of the fourth message is the same as that of the third message, and may be an ACP message.

[0332] The fourth message includes a fourth address configuration message, which includes consent information indicating that the first communication address has been assigned. For example, based on Figure 7-3 , the value of the A field in the fourth address configuration message is 2. The fourth message also includes the first communication address. For example, based on Figure 7-4 , the address information list in the fourth address configuration message includes the SLNA of the second node.

[0333] Optionally, the fourth message also includes the leaseable time of the first communication address.

[0334] S807: The first node generates a second message according to the fourth message.

[0335] When the first node receives the fourth message, it extracts the fourth address configuration message from the fourth message and encapsulates it in the second message. The second message includes the second address configuration message, and the content carried by the second address configuration message is the same as the content carried by the fourth address configuration message.

[0336] The message type of the fourth message is different from the message type of the second message. The message type of the fourth message is an ACP message, and the message type of the second message is a GMP message.

[0337] S808: The first node sends a second message to the second node. Correspondingly, the second node receives the second message from the first node.

[0338] The second message includes a second address configuration message, which includes consent information indicating that the first communication address has been assigned. For example, based on Figure 7-3 , the value of the A field in the second address configuration message is 2. The second message also includes the first communication address. For example, based on Figure 7-4 , the address information list in the second address configuration message includes the SLNA of the second node.

[0339] Optionally, the second message also includes the leaseable time of the first communication address.

[0340] S809: The second node saves and validates the first communication address.

[0341] S810: The second node sends a fifth message to the first node. Correspondingly, the first node receives the fifth message from the second node, wherein the fifth message includes a fifth address configuration message.

[0342] For step S809 and step S810, reference may be made to the detailed description of step S705 and step S706 in the embodiment shown in FIG7 , and details thereof will not be repeated here.

[0343] S811: The first node generates a sixth message according to the fifth message.

[0344] When the first node receives the fifth message, it extracts the fifth address configuration message from the fifth message and encapsulates it in a sixth message. The sixth message includes the sixth address configuration message, and the content carried by the sixth address configuration message is the same as that carried by the fifth address configuration message.

[0345] The message type of the fifth message is different from the message type of the sixth message. The message type of the sixth message is an ACP message, and the message type of the fifth message is a GMP message.

[0346] S812: The first node sends a sixth message to the third node. Correspondingly, the third node receives the sixth message from the first node.

[0347] The sixth message includes a sixth address configuration message, and the sixth address configuration message includes confirmation information, which is used to indicate confirmation of using the first communication address. For example, based on Figure 7-3, the value of the A field in the sixth address configuration message is 6.

[0348] S813: The third node sets the state of the first communication address to a leased state.

[0349] For step S813, reference may be made to the detailed description of step S707 in the embodiment shown in FIG7 , which will not be repeated here.

[0350] In the embodiment shown in FIG8 , upon learning that the first node has address allocation proxy capability, the second node requests the first node to apply to the third node for an SLNA on the second node's behalf. This allows newly joined nodes that are not directly connected to the M node to apply for an SLNA, enabling dynamic SLNA acquisition and facilitating management or control of the second node by the first node.

[0351] Figure 8 uses the example of the third node agreeing to allocate the first communication address to the second node. If the third node refuses to allocate the first communication address to the second node, the fourth address configuration message in the fourth message includes rejection information, indicating that the allocation of the first communication address is refused. For example, based on Figure 7-3, the value of the A field in the fourth address configuration message is 3. Consequently, the second address configuration message in the second message includes rejection information. Consequently, steps S809 through S813 are not executed.

[0352] As an optional embodiment, the first node has the function of an M-node (i.e., has address allocation capability), the second node has address allocation proxy capability, and the fourth node is a newly joined I-node or E-node (not yet assigned a communication address); the first node is directly connected to the second node or indirectly connected, and the fourth node is directly connected to the second node. After the second node notifies the fourth node of its address allocation proxy capability, the following steps may be included:

[0353] S8001: The fourth node sends the seventh message to the second node. Correspondingly, the second node receives the seventh message from the fourth node.

[0354] The seventh message includes a seventh address configuration message, which is used to request allocation of a second communication address for the fourth node. The seventh message is similar to the first message in the embodiment shown in FIG8 . For details, please refer to the detailed description of the first message in the embodiment shown in FIG8 , which will not be repeated here.

[0355] S8002: The second node generates an eighth message according to the seventh message. Step S8002 is similar to step S803. The eighth message is similar to the third message in the embodiment shown in FIG8. Please refer to the detailed description of the third message in the embodiment shown in FIG8, which will not be repeated here.

[0356] S8003: The second node sends an eighth message to the first node. Correspondingly, the first node receives the eighth message from the second node.

[0357] S8004: The first node allocates a second communication address to the fourth node, and sets the state of the second communication address to an allocated state.

[0358] At S8005, the first node sends a ninth message to the second node. Correspondingly, the second node receives the ninth message from the first node. The ninth message includes the second communication address. The ninth message is similar to the fourth message in the embodiment shown in FIG8 . The detailed description of the fourth message in the embodiment shown in FIG8 is provided and will not be repeated here.

[0359] S8006: The second node generates a tenth message based on the ninth message. Step S8006 is similar to step S807. The tenth message is similar to the second message in the embodiment shown in FIG8. Please refer to the detailed description of the second message in the embodiment shown in FIG8, which will not be repeated here.

[0360] S8007: The second node sends the tenth message to the fourth node. Correspondingly, the fourth node receives the tenth message from the second node.

[0361] S8008: The fourth node saves and validates the second communication address. Step S8008 is similar to step S809.

[0362] S8009: The fourth node sends the eleventh message to the second node. Correspondingly, the second node receives the eleventh message from the fourth node.

[0363] S8010: The second node generates a twelfth message according to the eleventh message.

[0364] S8011: The second node sends a twelfth message to the first node. Correspondingly, the first node receives the twelfth message from the second node.

[0365] S8012: The first node sets the state of the second communication address to a leased state.

[0366] Steps S8008 to S8012 are similar to steps S809 to S813 in the embodiment shown in FIG8 , and reference may be made to the detailed description of the embodiment shown in FIG8 , which will not be repeated here.

[0367] Figures 7 and 8 illustrate how a newly joined second node applies for an SLNA. A node that has already learned its SLNA can learn the SLNA of node M during the SLNA acquisition process. For example, the second address configuration message in the second message includes a management address, which is the SLNA of node M. A second node that has learned its SLNA can apply for a service address from a first node with address allocation capabilities. The second node can be directly or indirectly connected to the first node.

[0368] Please refer to Figure 9, which is a flowchart of another communication method provided by this application. The method shown in Figure 9 may include but is not limited to the following steps:

[0369] S901: The second node sends a message 1 to the first node. Correspondingly, the first node receives the message 1 from the second node.

[0370] Message 1 includes address configuration message 1, which includes first application information for requesting allocation of a new communication address for the second node, such as communication address 1. For example, based on FIG7-3 , the value of the A field in the first address configuration message is 0.

[0371] Optionally, message 1 also includes address type indication information, which is used to indicate the type of the communication address requested for allocation, i.e., the type of communication address 1. For example, based on Figure 7-3, address configuration message 1 also includes an address type (Address Type). In the embodiment shown in Figure 9, the type of communication address 1 is a service address, which can be an SLNA, an extensible address, an IPv4 address, or an IPv6 address. For example, the address type in address configuration message 1 is type 2.

[0372] Communication address 1 can identify some or all applications on the second node, meaning that these applications can share a service address. Communication address 1 can also identify an application on the second node, meaning that the second node requests a service address for that application. Communication address 1 can also be an anycast address, used to identify applications, specifically the first application on the second node and first applications on other nodes. That is, for the service address of an anycast address, the same application deployed on different nodes can share a service address.

[0373] S902: The first node allocates communication address 1 to the second node, and sets the state of communication address 1 to allocated state.

[0374] S903: The first node sends message 2 to the second node. Correspondingly, the second node receives message 2 from the first node. The second message includes communication address 1.

[0375] S904: The second node saves and validates the communication address 1.

[0376] S905: The second node sends a message 5 to the first node. Correspondingly, the first node receives the message 5 from the second node. The message 5 includes an address configuration message 5.

[0377] S906: The first node sets the state of the communication address 1 to a leased state.

[0378] The implementation process of step S902 to step S906 is similar to the implementation process of step S703 to step S707, and will not be repeated here.

[0379] It should be noted that if the second node is directly connected to the first node, then messages 1, 2 and 3 are GMP messages; if the second node is not directly connected to the first node, then messages 1, 2 and 3 are ACP messages.

[0380] In the embodiment shown in FIG9 , when the second node learns the SLNA of the first node, it can directly request the service address from the first node without relaying through a node with address allocation agent capability, thus saving time and wireless resources.

[0381] The second node that has learned the SLNA may apply to the first node having the address allocation capability to renew the lease of the first communication address. The second node is directly or indirectly connected to the first node.

[0382] Please refer to Figure 10, which is a flowchart of another communication method provided by this application. The method shown in Figure 10 may include but is not limited to the following steps:

[0383] S1001: A second node sends a message 1 to a first node. Correspondingly, the first node receives the message 1 from the second node.

[0384] Message 1 includes address configuration message 1, which includes renewal information for requesting renewal of the first communication address. For example, based on FIG7-3 , the value of the A field in the first address configuration message is 1.

[0385] Optionally, message 1 further includes address type indication information, which is used to indicate the type of the first communication address for which renewal is requested. For example, based on FIG7-3 , address configuration message 1 further includes an address type (Address Type).

[0386] The second node may send message 1 to the first node when the remaining lease time of the first communication address reaches a threshold. For example, the second node may send message 1 to the first node when the remaining lease time of the first communication address is less than 40%.

[0387] S1002: The first node renews the lease of the first communication address for the second node and updates the lease.

[0388] After receiving message 1, the first node checks whether the first communication address can be renewed. If so, it renews the first communication address for the second node and updates the lease, which includes the lease time.

[0389] S1003: The first node sends a message 2 to the second node. Correspondingly, the second node receives the message 2 from the first node. The second message includes the lease time of the first communication address.

[0390] The lease time of the first communication address here refers to the lease time after the first node renews the lease, for example, extending the remaining lease time. Message 2 includes address configuration message 2, and the value of the A field in address configuration message 2 is 2.

[0391] S1004: The second node updates the lease of the first communication address.

[0392] The second node updates the lease of the first communication address according to message 2.

[0393] It should be noted that, if the second node is directly connected to the first node, then the message 1 and the message 2 are GMP messages; if the second node is not directly connected to the first node, then the message 1 and the message 2 are ACP messages.

[0394] In the embodiment shown in FIG10 , the second node may apply to the first node for renewal of the lease of the first communication address to extend the usage time.

[0395] Figure 10 uses the example of a first node agreeing to renew the first communication address for a second node. If the first node refuses to renew the first communication address for the second node, then Address Configuration Message 2 in Message 2 includes rejection information, indicating the refusal to renew the first communication address. For example, based on Figure 7-3, the value of the A field in Address Configuration Message 2 is 3. Consequently, step S1004 is not executed. Optionally, after receiving Message 2, the second node may send Message 1 to the first node again to request renewal of the communication address.

[0396] The above describes in detail the method provided in the embodiments of the present application. The following provides an apparatus for implementing any of the methods in the embodiments of the present application. For example, an apparatus is provided that includes units (or means) for implementing each step performed by the node in any of the above methods.

[0397] Please refer to FIG11 , which is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0398] As shown in Figure 11, the communication device 110 may include a communication unit 1101 and a processing unit 1102. The communication unit 1101 and the processing unit 1102 may be software, hardware, or a combination of software and hardware.

[0399] The communication unit 1101 can implement a sending function and / or a receiving function. The communication unit 1101 can also be described as a transceiver unit, an acquisition unit, or a sending unit. The communication unit 1101 can also be a unit that integrates an acquisition unit and a sending unit, wherein the acquisition unit is used to implement the receiving function and the sending unit is used to implement the sending function. Optionally, the communication unit 1101 can be used to receive information sent by other devices, and can also be used to send information to other devices.

[0400] In one possible design, the communication device 110 may correspond to the first node in the above method embodiment. For example, the communication device 110 may be the first node or a chip in the first node. The communication device 110 may include a unit for executing the operations performed by the first node in the above method embodiment, and each unit in the communication device 110 is respectively for implementing the operations performed by the first node in the above method embodiment. The description of each unit is as follows:

[0401] The processing unit 1102 generates address allocation capability indication information;

[0402] The communication unit 1101 sends address allocation capability indication information to the second node, where the address allocation capability indication information is used to indicate the address allocation capability of the first node.

[0403] Optionally, the address allocation capability indication information is used to indicate that the first node has address allocation capability, the address allocation capability indication information is used to indicate that the first node has no address allocation capability, or the address allocation capability indication information is used to indicate that the first node has address allocation proxy capability.

[0404] Optionally, the address allocation capability indication information is carried in a wireless neighbor protocol message.

[0405] Optionally, the address allocation capability indication information is carried in a link state routing protocol message; or, the address allocation capability indication information is carried in a non-link state routing protocol message.

[0406] Optionally, the communication unit 1101 is further configured to receive a first message from the second node, where the first message includes a first address configuration message, and the first address configuration message is used to allocate or release a first communication address for the second node.

[0407] Optionally, the first address configuration message includes at least one of the following:

[0408] first application information, where the first application information is used to request allocation of a first communication address for the second node;

[0409] Renewal information, where the renewal information is used to request renewal of the first communication address;

[0410] Release information, where the release information is used to indicate the release of the first communication address;

[0411] Second application information, where the second application information is used to request allocation of a first communication address to the second node when the current communication address of the second node is unavailable;

[0412] Confirmation information, where the confirmation information is used to indicate confirmation of using the first communication address or confirmation of releasing the first communication address.

[0413] Optionally, the first message further includes address type indication information, where the address type indication information is used to indicate the type of the first communication address.

[0414] Optionally, the type of the first communication address is a first address type or a second address type, and the second address type is an extensible address type or an IPv4 address type or an IPv6 address type.

[0415] Optionally, the first address type is used for routing forwarding within the communication domain or for identifying an application, and the address length corresponding to the first address type is 2 bytes; the second address type is used to identify an application.

[0416] Optionally, when the first communication address is used to identify an application, it is specifically used to identify some or all applications on the second node, or it is specifically used to identify an application on the second node; or, when the first communication address is an anycast address, when the first communication address is used to identify an application, it is specifically used to identify the first application on the second node, as well as the first applications on other nodes.

[0417] Optionally, the first message further includes a message type, where the message type is used to indicate whether the first message includes a first address configuration message.

[0418] Optionally, the address allocation capability indication information is used to indicate that the first node has the address allocation capability; the communication unit is further used to send a second message to the second node based on the first message, and the message type of the second message is the same as the message type of the first message.

[0419] Optionally, the second message includes the first communication address.

[0420] Optionally, the processing unit 1102 is further configured to set the state of the first communication address to an allocated state.

[0421] Optionally, the second message includes a second address configuration message, and the second address configuration message includes at least one of the following:

[0422] The consent information and the allocation information are used to indicate that the first communication address has been allocated or the lease of the first communication address has been renewed;

[0423] The rejection information is used to indicate a rejection of allocating the first communication address or a rejection of renewing the lease of the first communication address.

[0424] Optionally, the address allocation capability indication information is used to indicate that the first node has address allocation agent capability; the communication unit 1101 is also used to send a third message to the third node based on the first message, the third message including a third address configuration message, and the third address configuration message is used to allocate or release the first communication address for the second node.

[0425] Optionally, the third address configuration message includes at least one of the following:

[0426] first application information, where the first application information is used to request allocation of a first communication address for the second node;

[0427] Renewal information, where the renewal information is used to request renewal of the first communication address;

[0428] Release information, where the release information is used to indicate the release of the first communication address;

[0429] Second application information, where the second application information is used to request allocation of a first communication address to the second node when the current communication address of the second node is unavailable;

[0430] Confirmation information, where the confirmation information is used to indicate confirmation of using the first communication address or confirmation of releasing the first communication address.

[0431] Optionally, the third message further includes address type indication information, where the address type indication information is used to indicate the type of the first communication address.

[0432] Optionally, the third message further includes a message type, where the message type is used to indicate whether the third message includes a third address configuration message.

[0433] Optionally, the message type of the third message is different from the message type of the first message.

[0434] Optionally, the communication unit 1101 is further configured to receive a fourth message from a third node, where the message type of the fourth message is the same as that of the third message.

[0435] Optionally, the fourth message includes the first communication address.

[0436] Optionally, the fourth message includes a fourth address configuration message, and the fourth address configuration message includes at least one of the following:

[0437] The consent information and the allocation information are used to indicate that the first communication address has been allocated or the lease of the first communication address has been renewed;

[0438] The rejection information is used to indicate a rejection of allocating the first communication address or a rejection of renewing the lease of the first communication address.

[0439] Optionally, the communication unit 1101 is further configured to send a second message to the second node according to the fourth message, where the message type of the second message is the same as that of the first message.

[0440] Optionally, the second message includes the first communication address.

[0441] Optionally, the second message includes a second address configuration message, and the second address configuration message includes at least one of the following:

[0442] The consent information and the allocation information are used to indicate that the first communication address has been allocated or the lease of the first communication address has been renewed;

[0443] The rejection information is used to indicate a rejection of allocating the first communication address or a rejection of renewing the lease of the first communication address.

[0444] In another possible design, the communication device 110 may correspond to the second node in the above method embodiment. For example, the communication device 110 may be the second node or a chip in the second node. The communication device 110 may include a unit for executing the operations performed by the second node in the above method embodiment, and each unit in the communication device 110 is respectively for implementing the operations performed by the second node in the above method embodiment. The description of each unit is as follows:

[0445] The communication unit 1101 is configured to receive address allocation capability indication information from the first node, where the address allocation capability indication information is used to indicate the address allocation capability of the first node.

[0446] Optionally, the address allocation capability indication information is used to indicate that the first node has address allocation capability, the address allocation capability indication information is used to indicate that the first node has no address allocation capability, or the address allocation capability indication information is used to indicate that the first node has address allocation proxy capability.

[0447] Optionally, the address allocation capability indication information is carried in a wireless neighbor protocol message.

[0448] Optionally, the address allocation capability indication information is carried in a link state routing protocol message; or, the address allocation capability indication information is carried in a non-link state routing protocol message.

[0449] Optionally, the communication unit 1101 is further used to send a first message to the first node according to the address allocation capability indication information, where the first message includes a first address configuration message, and the first address configuration message is used to allocate or release a first communication address for the second node.

[0450] Optionally, the first address configuration message includes at least one of the following:

[0451] first application information, where the first application information is used to request allocation of a first communication address for the second node;

[0452] Renewal information, where the renewal information is used to request renewal of the first communication address;

[0453] Release information, where the release information is used to indicate the release of the first communication address;

[0454] Second application information, where the second application information is used to request allocation of a first communication address to the second node when the current communication address of the second node is unavailable;

[0455] Confirmation information, where the confirmation information is used to indicate confirmation of using the first communication address or confirmation of releasing the first communication address.

[0456] Optionally, the first message further includes address type indication information, where the address type indication information is used to indicate the type of the first communication address.

[0457] Optionally, the type of the first communication address is a first address type or a second address type, and the second address type is an extensible address type or an IPv4 address type or an IPv6 address type.

[0458] Optionally, the first address type is used for routing forwarding within the communication domain or for identifying an application, and the address length corresponding to the first address type is 2 bytes; the second address type is used to identify an application.

[0459] Optionally, when the first communication address is used to identify an application, it is specifically used to identify some or all applications on the second node, or it is specifically used to identify an application on the second node; or, when the first communication address is an anycast address, when the first communication address is used to identify an application, it is specifically used to identify the first application on the second node, as well as the first applications on other nodes.

[0460] Optionally, the first message further includes a message type, where the message type is used to indicate whether the first message includes a first address configuration message.

[0461] Optionally, the communication unit 1101 is further configured to receive a second message from the first node, where the message type of the second message is the same as that of the first message.

[0462] Optionally, the second message includes the first communication address.

[0463] Optionally, the second message includes a second address configuration message, and the second address configuration message includes at least one of the following:

[0464] The consent information and the allocation information are used to indicate that the first communication address has been allocated or the lease of the first communication address has been renewed;

[0465] The rejection information is used to indicate a rejection of allocating the first communication address or a rejection of renewing the lease of the first communication address.

[0466] Optionally, for the second node having the address allocation agent capability, the above-mentioned address allocation capability indication information is used to indicate that the first node has the address allocation capability, and the communication unit 1101 is also used to receive a seventh message from the fourth node, the seventh message including a seventh address configuration message, and the seventh address configuration message is used to allocate or release the second communication address for the fourth node.

[0467] The fourth node is directly connected to the second node, and the second node may inform the fourth node through address allocation capability indication information that the second node has the address allocation agent capability.

[0468] Optionally, the communication unit 1101 is further configured to send an eighth message to the first node according to the seventh message after receiving the seventh message.

[0469] Optionally, the communication unit 1101 is further configured to receive a ninth message from the first node after sending the eighth message to the first node.

[0470] Optionally, the communication unit 1101 is further configured to, after receiving the ninth message from the first node, send a tenth message to the fourth node according to the ninth message.

[0471] Optionally, communication unit 1101 is further configured to send a query request message to the fifth node, where the query request message includes a third communication address, where the type of the third communication address is the second address type, and the query request message is used to request a fourth communication address corresponding to the third communication address, where the type of the fourth communication address is the first address type. The fifth node may provide a mapping query function.

[0472] According to an embodiment of the present application, each unit in the device shown in Figure 11 can be separately or all merged into one or several other units to constitute, or a certain (some) unit therein can also be split into multiple smaller units in function to constitute, which can achieve the same operation without affecting the realization of the technical effect of the embodiment of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of a unit can also be realized by multiple units, or the function of multiple units is realized by one unit. In other embodiments of the present application, other units can also be included based on nodes. In practical applications, these functions can also be assisted by other units to achieve, and can be achieved by the collaboration of multiple units.

[0473] It should be noted that the implementation of each unit may also refer to the corresponding description of the method embodiments shown in the above-mentioned Figures 6, 7, 8, 9, and 10.

[0474] In the communication device 110 described in FIG11 , the first node informs the second node of its address allocation capability through address allocation capability indication information, so that the second node determines whether to initiate an address application.

[0475] Please refer to FIG12 , which is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0476] It should be understood that the communication device 120 shown in Figure 12 is only an example. The communication device of the embodiment of the present application may also include other components, or include components with similar functions to the various components in Figure 12, or not include all the components in Figure 12.

[0477] The communication device 120 includes a communication interface 1201 and at least one processor 1202 .

[0478] The communication device 120 may correspond to the first node or the second node. The communication interface 1201 is used to send and receive messages, information, or packets, and the at least one processor 1202 executes program instructions so that the communication device 120 implements the corresponding process of the method executed by the corresponding node in the above method embodiment.

[0479] In one possible design, the communication device 120 may correspond to the first node in the above method embodiment. For example, the communication device 120 may be the first node or a chip in the first node. The communication device 120 may include components for performing the operations performed by the first node in the above method embodiment. Furthermore, each component in the communication device 120 is configured to implement the operations performed by the first node in the above method embodiment, and specifically may correspond to the corresponding description of the first node in the above method embodiment.

[0480] In another possible design, the communication device 120 may correspond to the second node in the above method embodiment. For example, the communication device 120 may be the second node or a chip in the second node. The communication device 120 may include components for executing the operations performed by the second node in the above method embodiment. Furthermore, each component in the communication device 120 may specifically correspond to the description of the second node in the above method embodiment for implementing the operations performed by the second node in the above method embodiment.

[0481] For the case where the communication device may be a chip or a chip system, reference may be made to the schematic structural diagram of the chip shown in FIG13 .

[0482] As shown in Figure 13 , chip 130 includes a processor 1301 and an interface 1302. There may be one or more processors 1301, and there may be multiple interfaces 1302. It should be noted that the functions of processor 1301 and interface 1302 can be implemented through hardware design, software design, or a combination of hardware and software, without limitation.

[0483] Optionally, the chip 130 may further include a memory 1303 , which is used to store necessary program instructions and data.

[0484] In the present application, processor 1301 may be configured to call a program for implementing the communication method provided in one or more embodiments of the present application at a first node or a second node from memory 1303 and execute the instructions contained in the program. Interface 1302 may be configured to output the execution results of processor 1301. In the present application, interface 1302 may be specifically configured to output various messages, information, or messages from processor 1301.

[0485] Regarding the communication method provided by one or more embodiments of the present application, reference may be made to the embodiments shown in Figures 6, 7, 8, 9, and 10, which will not be repeated here.

[0486] The processor in the embodiments of the present application may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0487] The memory in the embodiments of the present application is used to provide storage space, in which data such as an operating system and computer programs can be stored. The memory includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0488] According to the method provided in the embodiment of the present application, the embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on one or more processors, the method shown in Figures 6, 7, 8, 9, and 10 can be implemented.

[0489] According to the method provided in the embodiment of the present application, the embodiment of the present application also provides a computer program product, which includes a computer program. When the computer program runs on a processor, it can implement the methods shown in Figures 6, 7, 8, 9, and 10.

[0490] An embodiment of the present application provides a terminal device, which includes at least one communication device 110 or communication device 120 or chip 130 as described above.

[0491] An embodiment of the present application further provides a system, which includes at least one terminal device and / or at least one communication device 110 or communication device 120 or chip 130 as described above.

[0492] An embodiment of the present application further provides a processing device, including a processor and an interface; the processor is used to execute the method in any of the above method embodiments.

[0493] It should be understood that the above-mentioned processing device can be a chip. For example, the processing device can be a field programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chip. The various methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0494] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0495] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc), or a semiconductor medium (e.g., a solid-state drive), etc.

[0496] The units in the above-mentioned various apparatus embodiments completely correspond to the electronic devices in the method embodiments, and the corresponding modules or units perform the corresponding steps. For example, the communication unit (transceiver) performs the receiving or sending steps in the method embodiments, and other steps except sending and receiving can be performed by the processing unit (processor). The functions of the specific units can be referred to the corresponding method embodiments. Among them, there can be one or more processors.

[0497] It is understood that in the embodiments of the present application, the electronic device can perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples, and the embodiments of the present application can also perform other operations or variations of various operations. In addition, the various steps can be performed in a different order than those presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application need to be performed.

[0498] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0499] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0500] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0501] The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the scope of protection of the present application.

Claims

1. A communication method, characterized in that: The method is applied to a first node, and includes: generating address allocation capability indication information; Address allocation capability indication information is sent to the second node, where the address allocation capability indication information is used to indicate the address allocation capability of the first node.

2. The method according to claim 1, characterized in that The address allocation capability indication information is used to indicate that the first node has address allocation capability, the address allocation capability indication information is used to indicate that the first node has no address allocation capability, or the address allocation capability indication information is used to indicate that the first node has address allocation proxy capability.

3. The method according to claim 1 or 2, characterized in that The address allocation capability indication information is carried in a wireless neighbor protocol message.

4. The method according to claim 1 or 2, characterized in that The address allocation capability indication information is carried in a link state routing protocol message; or, the address allocation capability indication information is carried in a non-link state routing protocol message.

5. The method according to claim 2, characterized in that The method further comprises: A first message is received from the second node, where the first message includes a first address configuration message, and the first address configuration message is used to allocate or release a first communication address for the second node.

6. The method according to claim 5, characterized in that The first address configuration message includes at least one of the following: first application information, where the first application information is used to request allocation of the first communication address to the second node; Renewal information, where the renewal information is used to request renewal of the first communication address; Release information, where the release information is used to indicate the release of the first communication address; second application information, where the second application information is used to request allocation of the first communication address to the second node when the current communication address of the second node is unavailable; Confirmation information, where the confirmation information is used to indicate confirmation of using the first communication address or confirmation of releasing the first communication address.

7. The method according to claim 5, characterized in that The first message further includes address type indication information, where the address type indication information is used to indicate the type of the first communication address.

8. The method according to claim 7, characterized in that The type of the first communication address is a first address type or a second address type, and the second address type is an extensible address type or an IPv4 address type or an IPv6 address type.

9. The method according to claim 8, characterized in that The first address type is used for routing forwarding within the communication domain or for identifying applications, and the address length corresponding to the first address type is 2 bytes; the second address type is used to identify applications.

10. The method according to claim 9, characterized in that When the first communication address is used to identify an application, it is specifically used to identify some or all applications on the second node, or is specifically used to identify an application on the second node; or, when the first communication address is an anycast address, the first communication address is specifically used to identify the first application on the second node, and the first application on other nodes.

11. The method according to claim 5, characterized in that The first message further includes a message type, where the message type is used to indicate whether the first message includes the first address configuration message.

12. The method according to claim 5, characterized in that The address allocation capability indication information is used to indicate that the first node has the address allocation capability; The method further comprises: According to the first message, a second message is sent to the second node, where the message type of the second message is the same as the message type of the first message.

13. The method according to claim 12, characterized in that The second message includes the first communication address.

14. The method according to claim 13, characterized in that The method further comprises: The state of the first communication address is set to an allocated state.

15. The method according to claim 12, characterized in that The second message includes a second address configuration message, and the second address configuration message includes at least one of the following: Approval information, wherein the allocation information is used to indicate that the first communication address has been allocated or that the lease of the first communication address has been renewed; Rejection information, where the rejection information is used to indicate a rejection of allocating the first communication address or a rejection of renewing the lease of the first communication address.

16. The method according to claim 5, characterized in that The address allocation capability indication information is used to indicate that the first node has address allocation agent capability; The method further comprises: According to the first message, a third message is sent to a third node, where the third message includes a third address configuration message, and the third address configuration message is used to allocate or release the first communication address for the second node.

17. The method according to claim 16, characterized in that The third address configuration message includes at least one of the following: first application information, where the first application information is used to request allocation of the first communication address to the second node; Renewal information, where the renewal information is used to request renewal of the first communication address; Release information, where the release information is used to indicate the release of the first communication address; second application information, where the second application information is used to request allocation of the first communication address to the second node when the current communication address of the second node is unavailable; Confirmation information, where the confirmation information is used to indicate confirmation of using the first communication address or confirmation of releasing the first communication address.

18. The method according to claim 16, characterized in that The third message also includes address type indication information, where the address type indication information is used to indicate the type of the first communication address.

19. The method according to claim 16, wherein The third message further includes a message type, where the message type is used to indicate whether the third message includes the third address configuration message.

20. The method according to claim 16, wherein The message type of the third message is different from the message type of the first message.

21. The method according to claim 16, wherein The method further comprises: A fourth message is received from the third node, where the message type of the fourth message is the same as the message type of the third message.

22. The method according to claim 21, characterized in that The fourth message includes the first communication address.

23. The method according to claim 21, characterized in that The fourth message includes a fourth address configuration message, and the fourth address configuration message includes at least one of the following: Approval information, wherein the allocation information is used to indicate that the first communication address has been allocated or that the lease of the first communication address has been renewed; Rejection information, where the rejection information is used to indicate a rejection of allocating the first communication address or a rejection of renewing the lease of the first communication address.

24. The method according to claim 21, wherein The method further comprises: According to the fourth message, a second message is sent to the second node, where the message type of the second message is the same as the message type of the first message.

25. The method according to claim 24, characterized in that The second message includes the first communication address.

26. The method according to claim 24, characterized in that The second message includes a second address configuration message, and the second address configuration message includes at least one of the following: Approval information, wherein the allocation information is used to indicate that the first communication address has been allocated or that the lease of the first communication address has been renewed; Rejection information, where the rejection information is used to indicate a rejection of allocating the first communication address or a rejection of renewing the lease of the first communication address.

27. A communication method, characterized in that: The method is applied to the second node, and the method includes: Address allocation capability indication information is received from a first node, where the address allocation capability indication information is used to indicate the address allocation capability of the first node.

28. The method according to claim 27, characterized in that The address allocation capability indication information is used to indicate that the first node has address allocation capability, the address allocation capability indication information is used to indicate that the first node has no address allocation capability, or the address allocation capability indication information is used to indicate that the first node has address allocation proxy capability.

29. The method according to claim 28, characterized in that The method further comprises: According to the address allocation capability indication information, a first message is sent to the first node, where the first message includes a first address configuration message, and the first address configuration message is used to allocate or release a first communication address for the second node.

30. The method according to claim 29, wherein The method further comprises: A second message is received from the first node, where the message type of the second message is the same as the message type of the first message.

31. The method according to claim 30, characterized in that The second message includes the first communication address.

32. A communication device, characterized in that: The communication device includes a communication unit and a processing unit; The processing unit is configured to generate address allocation capability indication information; The communication unit is configured to send address allocation capability indication information to the second node, where the address allocation capability indication information is used to indicate the address allocation capability of the first node.

33. A communication device, characterized in that: The communication device includes a communication unit; The communication unit is configured to receive address allocation capability indication information from a first node, where the address allocation capability indication information is used to indicate the address allocation capability of the first node.

34. A communication device, characterized in that: include: processor; When the processor calls the computer program or instruction in the memory, the method according to any one of claims 1 to 26 is executed, or the method according to any one of claims 27 to 31 is executed.

35. A communication device, characterized in that: include: Logic circuits and communication interfaces; The communication interface is used to receive or send information; The logic circuit is used to receive information or send information through the communication interface, so that the method according to any one of claims 1 to 26 is executed, or the method according to any one of claims 27 to 31 is executed.

36. A terminal device, characterized in that: The terminal device includes a first node and / or a second node, wherein: The first node includes the communication device according to claim 32, or the first node is a node implementing the method according to any one of claims 1 to 26; The second node includes the communication device according to claim 33, or the second node is a node implementing the method according to any one of claims 27 to 31.

37. A computer-readable storage medium, characterized in that include: The computer-readable storage medium is used to store instructions or computer programs; when the instructions or the computer program are executed, the method according to any one of claims 1 to 26 is implemented, or the method according to any one of claims 27 to 31 is implemented.

38. A computer program product, characterized in that include: instructions or computer programs; When the instructions or the computer program are executed, the method according to any one of claims 1 to 26 or the method according to any one of claims 27 to 31 is implemented.

Images