CN116056157A

CN116056157A - Method and equipment for node identity negotiation, change and information interaction under multi-domain scene

Info

Publication number: CN116056157A
Application number: CN202111266499.7A
Authority: CN
Inventors: 金星; 生嘉
Original assignee: Huizhou TCL Mobile Communication Co Ltd
Current assignee: Huizhou TCL Mobile Communication Co Ltd
Priority date: 2021-10-28
Filing date: 2021-10-28
Publication date: 2023-05-02
Also published as: WO2023071989A1

Abstract

The invention provides a management node identity negotiation method, an identity changing method, an information interaction method and terminal equipment in a multi-domain scene. In the invention, the process of managing node identity negotiation in a plurality of communication domains takes into account at least one of the following factors: the multi-domain identity zone bit is configured by a user; domain priority; whether the domain management node identity is already present; terminal capability; and whether to be a scanning node in the multi-domain device discovery process, thereby optimizing the process of managing node identity negotiation. Under the condition of the determined domain management nodes and domain member nodes in a plurality of communication domains, identity change can be carried out, namely the identity of the domain management node is changed to the domain member node, and the identity of the domain member node is changed to the domain management node, so that the management flexibility under a multi-domain scene is provided. Information (e.g., air interface resource occupancy) interactions may also be performed, making resource management more efficient.

Description

Method and equipment for node identity negotiation, change and information interaction under multi-domain scene

Technical Field

The present invention relates to the field of wireless network communications technologies, and in particular, to a management node identity negotiation method, an identity change method (i.e., a method for exchanging identities of a domain management node and a domain member node) in a multi-domain scenario, an information interaction method (i.e., an information interaction method between nodes in a multi-domain scenario), and a terminal device.

Background

Currently, the 5G technology developed by The third generation partnership project (The 3rd Generation Partnership Project,3GPP) is widely enabling thousands of industries. However, the current 5G network service is difficult to reach the end node, is a key ring for opening an end-to-end connection based on short-distance communication (short-range wireless communication), is the last hundred meters of the internet of things technology, and fuses the 5G network with a wireless short-distance communication technology, so that the network coverage can be expanded, the tight fusion of different networks can be realized, the interconnection and intercommunication of network infrastructures such as an end-to-end network cloud, the data transmission and the bearing of intelligent service can be further driven, and the 5G is promoted to move to a more intelligent and open network development stage.

The development of the 5G technology promotes the generation of a large number of intelligent terminals, and brings a large number of wireless short-distance connection intelligent terminals into the market, so that more updated application scenes are derived. Such as typical short-range application scenarios in the fields of smart automobiles, smart manufacturing, smart homes, smart terminals, etc. The new wireless short-range application scene provides new requirements for the wireless short-range communication technology, and covers various aspects such as time delay, reliability, concurrency, information security and the like.

For example, the existing wireless short-range communication standard includes a star flash (SparkLink) system protocol, and the star flash 1.0 adopts an air interface technology specified in CCSA TC10 technical requirement of vehicle-mounted wireless short-range communication system to formulate a new generation wireless short-range communication system. The system designs a physical layer and a data link layer, and provides connection-oriented air interface (air interface) transmission with QoS guarantee for upper layer applications. The star flash technology can ensure the requirements of low time delay, high reliability, high precision synchronization, information security and the like, meet the requirements of various typical wireless application scenes, and promote the continuous evolution of the wireless short-distance communication technology.

In a star flash system constructed according to a star flash system protocol stack frame, nodes in the system are divided into a management node (G node) and a terminal node (T node). In a specific application scenario, a single G node manages a certain number of T nodes, and the G node and the T nodes are connected together to complete a specific communication function. The single G node and the T node connected with the single G node together form a communication domain.

For a scenario in which no other communication domain using the same time-frequency resource exists within the coverage of one communication domain, it may be called a single domain scenario. There is overlap between coverage for one communication domain and other communication domains, and these communication domains use the same time-frequency resources, these communication domains form a multi-domain scenario. Signal interference between adjacent communication domains occurs in a multi-domain scene, so that the signal to noise ratio of signals received by terminals in each communication domain is obviously reduced, and performance indexes such as capacity, coverage radius and the like of the system cannot meet the communication requirements. Therefore, when a multi-domain scene appears, the communication domains using the same time-frequency resources need to be coordinated, so that the probability of collision of air interface resources occupied by each communication domain is reduced.

Disclosure of Invention

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

The invention aims to provide a management node identity negotiation method, an identity change method, an information interaction method and terminal equipment in a multi-domain scene, so as to solve the technical problems that signal interference, air interface resource conflict and the like are easy to occur in the scene of a plurality of communication domains in the existing wireless short-distance communication (such as wireless communication in a star flash architecture).

The present invention provides, in a first aspect, a management node identity negotiation method in a multi-domain scenario, for deciding which of a plurality of communication domains is a domain management node in a management mode, the plurality of communication domains including a first communication domain and a second communication domain, the first communication domain including a first management node and at least one first terminal node connected to the first management node, the second communication domain including a second management node and at least one second terminal node connected to the second management node, the method comprising:

The first management node in the first communication domain negotiates management node identity with the second management node in the second communication domain to determine the domain management node from the first management node and the second management node, wherein the process of management node identity negotiation takes into account at least one of:

the multi-domain identity zone bit of each of the first management node and the second management node configured by a user is used;

the domain priorities of the first management node and the second management node respectively;

whether the first management node and the second management node already have domain management node identities;

terminal capabilities of the first management node and the second management node; and

which of the first management node and the second management node is a scanning node in a multi-domain device discovery process.

The second aspect of the present invention provides a method for exchanging identities of a domain management node and a domain member node in a multi-domain scenario, where the method is used for identity modification of a domain management node and a domain member node that have been determined in a plurality of communication domains, and the domain management node has a management control function for the domain member node, and the method includes:

Sending a domain management node identity change request;

receiving a domain management node identity change response; and

determining whether to change the domain management node identity according to the domain management node identity change response,

when the identity of the domain management node is decided to be changed, the identity of the domain management node is changed into a domain member node, and the identity of the domain member node is changed into the domain management node.

The third aspect of the present invention provides a method for information interaction between nodes in a multi-domain scenario, wherein a domain management node and a domain member node have been determined in the multi-domain scenario, the domain management node having a management control function for the domain member node, the method comprising:

and performing information interaction between the domain management node and one of the domain member nodes and the other of the domain management node and the domain member node, or between the domain management nodes, or between the domain member nodes, wherein the interacted information comprises at least one of the following:

the occupation condition of air interface resources;

interference information;

load ratio;

service information;

a communication domain identity class; and

and updating multi-domain information.

A fourth aspect of the present invention provides a terminal device, comprising: a memory, a processor and a program stored on the memory and executable on the processor, which when executed by the processor, implements a method as in the first aspect of the invention.

A fifth aspect of the present invention provides a terminal device, comprising: a memory, a processor and a program stored on the memory and executable on the processor, which when executed by the processor, performs a method as in the second aspect of the invention.

A sixth aspect of the present invention provides a terminal device, comprising: a memory, a processor and a program stored on the memory and executable on the processor, which when executed by the processor, implements a method as in the third aspect of the invention.

Various steps in the communication method of the present invention may be implemented by a program executable by a processor, the program may be stored in a non-transitory computer readable medium, the non-transitory computer readable medium may include at least one of the group consisting of: hard disks, CD-ROMs, optical storage devices, magnetic storage devices, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, and flash memory.

In some embodiments of the present invention, a first management node in a first communication domain negotiates management node identities with a second management node in a second communication domain to determine a domain management node from the first management node and the second management node. The above process of managing node identity negotiation takes into account at least one of the following factors: the multi-domain identity zone bit is configured by a user; domain priority; whether the domain management node identity is already present; terminal capability; and whether it is a scanning node in the multi-domain device discovery process. In some embodiments of the present invention, the determined domain management node and domain member node in the plurality of communication domains may perform an identity change, that is, the identity originally being the domain management node is changed to the domain member node, and the identity originally being the domain member node is changed to the domain management node. In some embodiments of the present invention, information interaction may be performed between one of the domain management node and the domain member node, and the other of the domain management node and the domain member node, between the domain management nodes, or between the domain member nodes, which are determined in the plurality of communication domains, so as to make resource management more efficient in response to a change in the communication environment. Therefore, the process of managing node identity negotiation is optimized, the management elasticity under the multi-domain scene is provided, the resource management efficiency under the multi-domain scene is improved, and the technical problems that signal interference, air interface resource conflict and the like are easy to occur under the scene of a plurality of communication domains are solved.

Drawings

Further details, aspects and embodiments of the invention are described below, by way of example only, with reference to the accompanying drawings. For simplicity and clarity, elements in the figures have been shown and are not necessarily drawn to scale. The same reference numerals are included in the various figures to facilitate understanding.

Fig. 1 shows a schematic diagram of a plurality of nodes in a plurality of communication domains.

Fig. 2 is a schematic diagram showing a multi-domain coordination procedure under the existing star flash protocol standard.

Fig. 3 is a schematic diagram showing a negotiation flow of a management node under the existing star flash protocol standard.

Fig. 4 shows a flowchart of a management node identity negotiation method in a multi-domain scenario according to an embodiment of the present invention.

Fig. 5 is a schematic flow chart of determining a domain management node by using a multi-domain identity flag in management node identity negotiation according to an embodiment of the present invention.

Fig. 6 is a schematic flow chart of determining a domain management node by using domain priority in management node identity negotiation according to an embodiment of the present invention.

Fig. 7 is a schematic flow chart of determining a domain management node by using a domain management node identity in the management node identity negotiation according to an embodiment of the present invention.

Fig. 8 is a schematic flow chart of determining a domain management node by using terminal capability in management node identity negotiation according to an embodiment of the present invention.

Fig. 9 is a schematic flow chart of determining a domain management node by using a scanning node in the process of whether the management node is a multi-domain device discovery in the management node identity negotiation according to the embodiment of the invention.

Fig. 10 is a schematic flow chart of determining a domain management node by using a fast domain node identity negotiation method in the management node identity negotiation according to an embodiment of the present invention.

Fig. 11 shows a flow chart of a method of exchanging identities of a domain management node and a domain member node in a multi-domain scenario according to an embodiment of the invention.

Fig. 12 is a schematic flow chart of identity change of a domain management node and a domain member node in an embodiment of the invention.

Fig. 13 is a schematic flow chart of identity change of a domain management node and a domain member node in an embodiment of the invention.

Fig. 14 is a flowchart illustrating a method for information interaction between nodes in a multi-domain scenario according to an embodiment of the present invention.

Detailed Description

In order that those skilled in the art will better understand the solution of the present invention, a technical solution of an embodiment of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiment is only a part of the embodiment of the present invention, not all of the embodiment. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.

The technical solution of the embodiment of the present invention aims to solve the technical problems related to the wireless short-range communication, and although the description of the present invention uses a star flash system communication protocol as an example, it will be apparent to those skilled in the art that the solution or concept proposed by the present invention can also be applied to other wireless short-range communication systems, and is not limited to the star flash communication system.

Some technical terms in the art are used herein, and some terms are defined as follows:

g node: and a management node in the star flash communication system, and a node for transmitting data scheduling information.

T node: a terminal node in the star flash communication system receives the data scheduling information and transmits data according to the data scheduling information;

in a specific application scenario, a single G node manages a certain number of T nodes, and the G node and the T nodes are connected together to complete a specific communication function.

Communication domain: the single G node and the T node connected with the single G node together form a communication domain.

Fig. 1 shows a schematic diagram of a plurality of nodes in a plurality of communication domains. Three communication domains are included in fig. 1, each including a management node (i.e., G node) and at least one terminal node (i.e., T node). For example, in the first communication domain, the management node G1 and the terminal nodes T11 and T12 connected to the management node G1 constitute the first communication domain; in the second communication domain, the management node G2 and the terminal node T21 connected to the management node G2 constitute a second communication domain; in the third communication domain, the management node G3 and the terminal nodes T31, T32, and T33 connected to the management node G3 constitute a third communication domain. The terminal node T41 is not connected to the management node G1, the management node G2, and the management node G3, and therefore does not belong to any of the first communication domain, the second communication domain, and the third communication domain.

In the management mode of the multi-domain scenario (the management mode is described in detail below), if the management node of the individual communication domain is still a management node in the multi-domain, the management node may be referred to as a domain management node, and if the management node of the individual communication domain is not a management node in the multi-domain, the management node may be referred to as a domain member node. For example, the first communication domain and the second communication domain perform communication management in a management mode of a multi-domain scene, if the management node G1 in the first communication domain becomes a management node in the multi-domain, the management node G1 is referred to as a domain management node, and other nodes are referred to as domain member nodes; the first communication domain, the second communication domain and the third communication domain perform communication management in a management mode of a multi-domain scene, if the management node G1 in the first communication domain becomes a management node in the multi-domain, the management node G1 is referred to as a domain management node, and other nodes are referred to as domain member nodes.

In the existing star-flash system defined by the star-flash protocol standard, information interaction between communication domains is realized through interaction between G nodes in each communication domain. According to the relation between G nodes in the multi-domain scene, two modes are defined for the multi-domain scene: a management mode and a non-management mode.

The management mode refers to that a subordinate relationship exists between G nodes of a plurality of communication domains, and the subordinate relationship bears the identities of the domain management node and the domain member nodes respectively. The domain management node has a management control function for domain member nodes, and the domain member nodes strictly obey signaling instructions of the domain management node.

The non-management mode means that a strict subordinate relationship does not exist among G nodes of a plurality of communication domains, one party is not required to strictly obey the control management of the other party, and the coordination of multi-domain information can be only carried out in a negotiation or suggestion mode.

It can be appreciated that, in coordination of multi-domain information performed in the non-management mode, there may still be a situation that time-frequency resources used by different communication domains overlap, and air interface resources cannot be effectively coordinated. And only in the management mode, the domain management node uniformly distributes the air interface resources for other domain member nodes, so that the coordination of the air interface resources among a plurality of communication domains can be really realized, and the signal interference among adjacent domains is reduced as much as possible.

Fig. 2 is a schematic diagram showing a multi-domain coordination procedure under the existing star flash protocol standard. Referring to fig. 2, the domain management node identity negotiation scheme in the existing scheme is as follows:

according to the existing star flash protocol standard, G nodes need to be converted into T nodes to discover other G nodes in a scanning mode. When the G Node triggers neighbor scanning according to a configuration period or an event, the G Node can switch to a G link common-frequency signal near the T Node identity scanning (for example, G Node 1 switches to the T Node identity and initiates scanning to G Node 2), and when the G Node switched to the T Node identity searches for a broadcast message sent by other G nodes, which means that the neighbor exists is detected, a multi-domain link establishment request is initiated to the G Node of the neighbor, and a multi-domain control link between two G nodes is established.

After the multi-domain control link is established, the two G nodes can carry out the identity negotiation of the management node in the multi-domain scene through the link. The negotiation of the domain management node negotiates selecting the management node mainly by comparing the priority in the multi-domain attribute of the G nodes of both parties, the management node willingness (i.e., the willingness degree to become the management node), and the random arbitration bit (i.e., a randomly generated value), as shown in table 1 below.

Priority level

Management node willingness

Random arbitration bits

TABLE 1

The existing star flash protocol standard compares the priority of two G nodes, the willingness value of the management node and the random arbitration bit in sequence in the process of the identity negotiation of the domain management node. The G node with higher priority acts as a domain management node. If one multi-domain G node has the same priority as another multi-domain G node, the G node compares the management node willingness value with another G node, and the G node with the higher management node willingness value acts as the management node. If the priorities of the two G nodes and the willingness of the management node are the same, the random arbitration bits are compared, and the G node with the higher random arbitration bit serves as the management node.

If the priorities of the two G nodes, the willingness of the management node and the random arbitration bit are the same, the negotiation of the domain management node fails.

After the identity negotiation of the domain management nodes, if the negotiation is successful, one G node is used as a domain management node, the other G node is used as a domain member node, and multi-domain management information interaction can be performed between the domain management node and the domain member node to mutually transmit information required by multi-domain management, and/or multi-domain measurement information interaction can also be performed between the domain management node and the domain member node to mutually transmit measurement information required by multi-domain management.

Fig. 3 is a schematic diagram showing a negotiation flow of a management node under the existing star flash protocol standard. As shown in fig. 3, the G1 node sends a management node negotiation request message to the G2 node; responding to the management node negotiation request message, and sending a management node negotiation response message to the G1 node by the G2 node; after receiving the response message of the G2 node, the G1 node sends a management node negotiation acknowledgement message to the G2 node.

The existing star-flash protocol standard does not give a specific implementation of the priority and the willingness of the management node, that is, the priority is defined as what standard is used as the priority and what parameter is used to express the willingness of the management node, and the existing star-flash protocol standard lacks clear definition. In addition, the existing star flash protocol standard does not explicitly define the management node negotiation request message, the management node negotiation response message and the management node negotiation acknowledgement message which are interacted in the management node negotiation process.

Furthermore, the following problems exist in the domain management node identity negotiation of the existing star flash protocol standard:

first, the domain management node identity negotiation is performed based on the priority, the management node wish and the random arbitration bit, if the parameters of the two G nodes are the same, the domain management node negotiation fails, and the negotiation failure probability of the domain management node identity negotiation mechanism is high. If the negotiation with the management node fails, the method can only fall back to a non-management mode, and the resource negotiation can only be carried out in a notification mode between the neighborhoods in the non-management mode, so that the probability of neighborhood interference can be greatly increased;

secondly, the mechanism of the domain management node identity negotiation cannot meet the requirement of a user for specifying the domain management node, and the applicability of the domain management node identity negotiation to certain application scenes is poor;

third, for some application scenarios where more than two communication domains exist, the domain management node identity negotiation mechanism does not consider whether the G node in the communication domain is originally used as a domain management node, and lacks the capability of effectively and reasonably performing the domain management node identity negotiation.

The invention provides a method for determining the identity of a domain management node by using a multi-domain information interaction method of management nodes between adjacent domains under a multi-domain scene and by using a known determination rule of both sides. Meanwhile, a method for changing the identity of the domain management node and information needing interaction between adjacent domains in the multi-domain coordination process are also provided. The specific technical scheme is described in detail as follows:

Fig. 4 shows a flowchart of a management node identity negotiation method in a multi-domain scenario according to an embodiment of the present invention. The management node identity negotiation method is used for negotiating the management node identity in a plurality of communication domains (such as the first and second communication domains, or the first, second and third communication domains in fig. 1). The plurality of communication domains includes a first communication domain including a first management node (e.g., G1) and at least one first terminal node (e.g., T11 and T12) connected to the first management node, and a second communication domain including a second management node (e.g., G2) and at least one second terminal node (e.g., T21) connected to the second management node. The management node identity negotiation method can determine which communication domain management node in a plurality of communication domains is used as a domain management node in a management mode.

When a first management node (such as G1) in a first communication domain is used as a domain management node, a second management node (such as G2) in a second communication domain is used as a domain member node; when the second management node in the second communication domain is the domain management node, the first management node in the first communication domain is the domain member node. The domain management node has a management control function for the domain member node.

The management node identity negotiation method comprises the following steps:

step S401: the first management node in the first communication domain negotiates management node identity with the second management node in the second communication domain to determine a domain management node from the first management node and the second management node.

For example, the management node identity negotiation performed in step S401 may be implemented in the interaction procedure of the management node identity negotiation in fig. 2. Before this, the first management node (e.g. G1) of the first communication domain may trigger the neighborhood scan according to the configuration period or the event, switch to the terminal node (i.e. T node) identity to scan for the nearby management node (the second management node, e.g. G2), or the second management node (e.g. G2) of the second communication domain may trigger the neighborhood scan according to the configuration period or the event, switch to the terminal node (i.e. T node) identity to scan for the nearby management node (the first management node, e.g. G1). Upon detecting the existence of a management node of the neighborhood, a multi-domain link establishment request is initiated to the management node of the neighborhood to establish a multi-domain control link between two management nodes (i.e., a first management node and a second management node, i.e., G1 and G2) in the two communication domains. After the multi-domain control link is established, the two management nodes can carry out the identity negotiation of the management nodes in the multi-domain scene through the link.

That is, further, before the step of performing management node identity negotiation between the first management node (e.g., G1) of the first communication domain and the second management node (e.g., G2) of the second communication domain, the method further includes:

converting one of the first management node and the second management node into a terminal node identity to scan the other of the first management node and the second management node; and

when the other of the first management node and the second management node is found after the scanning is successful, a multi-domain control link is established between the first management node and the second management node.

By the scheme, the multi-domain coordination key information of the neighborhood management nodes is compared, so that the management node identity negotiation under a multi-domain scene can be finally determined, and the probability of failure in the negotiation of the neighborhood management nodes is greatly reduced. Wherein the process of managing node identity negotiation takes into account at least one of:

the method comprises the steps that through respective multi-domain identity zone bits of a first management node and a second management node configured by a user;

Which of the first management node and the second management node is the scanning node in the multi-domain device discovery process.

In an alternative embodiment of the present invention, factors considered by the process of managing node identity negotiation include one or more of a multi-domain identity flag, a domain priority, whether a domain management node identity is already present, a terminal capability, and whether it is a scanning node in a multi-domain device discovery process. That is, the negotiation process employs one or more of the parameters described above. For example, in the negotiation process, whether the multi-domain identity flag bit is a scanning node in the multi-domain device discovery process or not is considered, and whether the multi-domain identity flag bit has the identity of the domain management node and whether the multi-domain device discovery process is a scanning node is considered at the same time.

In an alternative embodiment of the present invention, the process of managing node identity negotiation considers at least two factors among the multi-domain identity flag bit, the domain priority, whether the domain management node identity is already provided, the terminal capability, and whether it is a scanning node in the multi-domain device discovery process, and determines the domain management node according to a predetermined order of the at least two factors. That is, the negotiation process compares according to a predetermined order of at least two of the above-mentioned factors of the first management node and the second management node. For example, the predetermined sequence is a multi-domain identity flag bit and whether the multi-domain identity flag bit is a scanning node in the multi-domain device discovery process, and then in the negotiation process, the multi-domain identity flag bit is compared first, and whether the multi-domain identity flag bit is a scanning node in the multi-domain device discovery process is compared. For another example, the predetermined sequence is a multi-domain identity flag bit, whether the multi-domain identity flag bit has a domain management node identity and whether the multi-domain identity flag bit is a scanning node in the multi-domain device discovery process, and then, whether the multi-domain identity flag bit has a domain management node identity is compared in the negotiation process, and finally, whether the multi-domain identity flag bit is a scanning node in the multi-domain device discovery process is compared.

In an alternative embodiment of the present invention, the process of managing node identity negotiation determines which of the first management node and the second management node is the domain management node by sequentially comparing the multi-domain identity flag bit, the domain priority, the domain management node identity, the terminal capability, and the scanning node in the multi-domain device discovery process. That is, the predetermined sequence is a multi-domain identity flag bit, a domain priority, a domain management node identity, a terminal capability, and a scanning node in a multi-domain device discovery process, and in a negotiation process, the predetermined sequence is compared to determine which of the first management node and the second management node is the domain management node.

In an alternative embodiment of the present invention, the process of managing node identity negotiation considers at least the respective multi-domain identity flags of the first management node and the second management node configured by the user. The multi-domain identity bits may be identified by two bits. The carrying of the multi-domain identity bits may be achieved in at least two ways, in one embodiment the multi-domain identity bits are carried in a broadcast message; in another embodiment, the multi-domain identity tag is used as an attribute related to the multi-domain service, and the interaction is performed by means of multi-domain service discovery.

In particular, in determining the domain management node and domain membership node identities from the multi-domain identity flags, the user (or the user) may choose to configure the management node as to whether it is desired to be a domain management node or a domain membership node. That is, the multi-domain identity bits are configured manually by a user or at the discretion of the user.

As an illustrative example, the multi-domain identity bits may be identified by 2 bits, as shown in table 2 below:

bit position	Meaning of
		01	As a domain management node
10	As domain member node
		00	Not enabling the flag bit
11	Reserved bits

TABLE 2

Fig. 5 is a schematic flow chart of determining a domain management node by using a multi-domain identity flag in management node identity negotiation according to an embodiment of the present invention. As an exemplary example, as shown in fig. 5, the multi-domain identity flag bit of the G1 node is 01, which indicates that G1 wants to become a domain management node in the multi-domain negotiation process; the multi-domain identity flag bit of G2 is 00, which indicates that the user does not configure the expected identity of the G2 node in multi-domain coordination, so it can be determined that G1 is a domain management node.

The carrying of the multi-domain identity bit can be carried out in the following two ways:

mode one: in order to enable faster determination of the identity of the domain management node between the multi-domain management nodes, a multi-domain identity flag bit may be carried in the broadcast message of the management node, for example, identified using 2 out of 9 reserved bits in the broadcast message.

Mode two: as an attribute related to the multi-domain service, interaction is performed by means of multi-domain service discovery. The multi-domain services described herein fall under the broad concept of services and may be interactions of multi-domain services through any one or any of several suitable protocol layers in a protocol stack, thereby conveying multi-domain identity flags. For example, the multi-domain identity bits may be carried by the interaction of management node identity negotiations in fig. 2, or by a service running on the application layer. For example, a new multi-domain service is defined for a multi-domain service using two bits reserved for 12-13 in the multi-domain service capability bitmap or according to a rule defined by the service.

In an alternative embodiment of the present invention, the process of managing node identity negotiation considers at least the respective domain priorities of the first management node and the second management node, where the domain priorities are determined by parameters in the synchronization signals sent in the first communication domain and the second communication domain.

Specifically, in determining the domain management node and the domain member node identity according to the domain priority, the high-priority domain serves as the domain management node, and the general priority domain serves as the domain member node.

The star-flash access layer protocol defines two synchronization signals, wherein the synchronization signals (also called first training signals (First Train Signal, FTS)) incorporate a parameter u for distinguishing an advanced communication domain from a general communication domain in the sequence generation process, as shown in the following formula:

where u=1 for the advanced communication domain and u=40 for the general communication domain.

As an exemplary example, when the multi-domain identity bits of the management nodes participating in the multi-domain identity negotiation are identical, i.e. the domain management node cannot be determined by the multi-domain identity bits, it can be determined by the parameter u in the FTS sequence.

Fig. 6 is a schematic flow chart of determining a domain management node by using domain priority in management node identity negotiation according to an embodiment of the present invention. As an exemplary example, as shown in fig. 6, the domain priority u=1 of the G1 node is an advanced communication domain, and the domain priority u=40 of the G2 node is a general communication domain. The result of this multi-domain negotiation is that the G1 node is the domain management node and the G2 node is the domain member node.

In an alternative embodiment of the invention, the process of managing node identity negotiation takes into account at least whether the first and second management nodes already have domain management node identities. And when the first management node negotiates with a third management node in the third communication domain, determining that the first management node is a domain management node and has a domain management node identity, and if the second management node in the second communication domain does not have the domain management node identity, determining that the first management node is the domain management node after the first management node and the second management node carry out management node identity negotiation.

Specifically, in determining the identity of the domain management node and the identity of the domain member node according to whether the management node already has the identity of the domain management node, the identity of the domain management node is already in other multiple domains, and the domain management node is used in the multi-domain coordination process.

As an exemplary example, if multiple management nodes participating in the multi-domain negotiation have the same multi-domain identity flag bit and the parameter u for identifying the domain priority in the FTS is also the same, it may be further determined whether there is a unique management node that is already the identity of the domain management node in the management node participating in the multi-domain negotiation, and if so, the management node still serves as the domain management node in the multi-domain management node identity negotiation.

Fig. 7 is a schematic flow chart of determining a domain management node by using a domain management node identity in the management node identity negotiation according to an embodiment of the present invention. As an exemplary example, as shown in fig. 7, G1 and G3 are two management nodes that have completed multi-domain coordination, and G1 is a management node and G3 is a terminal node. If G2 finds G1 through the scanning process, after interacting multi-domain information with G1, it finds that G1 is already a management node identity, and in the multi-domain formed by G1 and G2, it can determine that G1 is a domain management node and G2 is a domain member node.

In an alternative embodiment of the invention, the process of managing node identity negotiation takes into account at least the terminal capabilities of the first and second management nodes. When the terminal capability of the first management node is higher than that of the second management node, the first management node serves as a domain management node, and the second management node serves as a domain member node.

Specifically, in determining the identities of the domain management node and the domain member nodes according to the terminal capability or the terminal type, the domain management node with high capability level is selected as the domain management node of the present multi-domain coordination according to the terminal capability level or the terminal type.

As an exemplary example, if multiple management nodes cannot determine the identity of the management node through one or more of the above schemes during the multi-domain negotiation, the identity of the management node may be determined according to the terminal capability level of the management node. If the management node with high terminal level (strong capability) is used as the domain management node, the management node with low terminal capability level (weak capability) is used as the domain member node.

Fig. 8 is a schematic flow chart of determining a domain management node by using terminal capability in management node identity negotiation according to an embodiment of the present invention. As an exemplary example, as shown in fig. 8, G1 and G2 are two management nodes participating in the negotiation of the management node, and three parameters including their multi-domain identities, domain priority, and whether they are domain management nodes are all the same, at this time, the domain management node identities need to be determined according to the capability levels of G1 and G2. For example, if the terminal capability class of G1 is Cat5 (i.e., category 5, the class of terminal capability belongs to class 5), the terminal capability class of G2 is Cat1 (i.e., category 1, the class of terminal capability belongs to class 1), and the terminal capability of the class Cat5 is stronger than the terminal capability of the class Cat1, it is determined that the terminal capability of G1 is stronger than G2 according to the terminal capability, so G1 serves as a domain management node and G2 serves as a domain member node.

In an alternative embodiment of the present invention, when the first management node converts the identity of the terminal node to scan for the second management node, the first management node is used as a scanning node in the multi-domain device discovery process, and the second management node is used as a scanned node in the multi-domain device discovery process. A management node in one communication domain may discover a management node in another communication domain by converting to a terminal node and scanning. When a certain management node is converted into a terminal node, the management node is used as a scanning node in the multi-domain device discovery process, and the management node in the other communication domain is used as a scanned node in the multi-domain device discovery process.

In an alternative embodiment of the present invention, the process of managing node identity negotiation takes into account at least which of the first management node and the second management node is the scanning node in the multi-domain device discovery process. When the first management node is a scanning node in the multi-domain equipment discovery process and the second management node is a scanned node in the multi-domain equipment discovery process, after the first management node and the second management node carry out management node identity negotiation, the first management node is determined to be a domain member node, and the second management node is determined to be a domain management node. Or when the first management node is a scanning node in the multi-domain equipment discovery process and the second management node is a scanned node in the multi-domain equipment discovery process, after the first management node and the second management node carry out management node identity negotiation, the second management node is determined to be a domain member node, and the first management node is a domain management node.

Specifically, in determining the domain management node and the domain member node identity according to whether the management node is a scanning node in the multi-domain device discovery process, the management node of the scanned node is used as the domain management node, and the management node of the scanning node is used as the domain member node; or, the management node of the scanned node is used as a domain management node, and the management node of the scanned node is used as a domain member node.

As an exemplary example, if multiple management nodes participating in the negotiation of the management node identity have the same communication domain attribute, the same identity and the same capability level, that is, the management node identity cannot be determined by one or more of the above schemes, then the scanning node in the multi-domain device discovery process may be used as a domain member node, and the scanned node in the multi-domain device discovery process may be used as a domain management node, because the management node as the scanned node is originally the management node, in this way, the change of the state of the management node may be reduced in some cases, and the interaction of data or the change in configuration may be reduced. Or, the scanning node in the multi-domain device discovery process is used as the management node, and the scanned node in the multi-domain device discovery process is used as the terminal node, and although the mode needs to change the state of the management node as the scanned node into the domain member node, the mode is also an alternative implementation mode.

Fig. 9 is a schematic flow chart of determining a domain management node by using a scanning node in the process of whether the management node is a multi-domain device discovery in the management node identity negotiation according to the embodiment of the invention. As an exemplary example, as shown in FIG. 9, because it is the conversion of the G1 node into the T node identity that initiates the scan to the G2 node, G1 is taken as the domain member node and G2 is taken as the domain management node.

In the multi-domain scanning process, one party is required to be used as a scanner to finish the discovery of the multi-domain equipment, so that the identity of the domain management node can be always determined through the scheme, thereby avoiding the failure of the negotiation of the management node identity and entering a non-management mode.

In an alternative embodiment of the present invention, the process of managing node identity negotiation considers only which of the first management node and the second management node is the scanning node in the multi-domain device discovery process. Which of the first management node and the second management node is the scanning node in the multi-domain device discovery process is the only consideration of the management node identity negotiation process of the first management node and the second management node.

In the embodiment of the invention, a fast domain management node identity negotiation scheme can be adopted, namely, the first management node and the second management node are the only consideration factors of the scanning node in the multi-domain equipment discovery process in the management node identity negotiation process, so that the fast domain management node identity negotiation scheme is formed. That is, without referring to other parameters (such as the above-mentioned multi-domain identity flag bit, domain priority, domain management node identity, and terminal capability), the scanned node in the multi-domain device discovery process is directly selected as a domain member node, the scanned node in the multi-domain device discovery process is selected as a domain management node, or the scanned node in the multi-domain device discovery process is selected as a management node, and the scanned node in the multi-domain device discovery process is selected as a domain member node. By the method, the processing flow and time delay of the negotiation of the domain management node can be simplified, and the efficiency is improved.

Only when both management nodes participating in the negotiation support a fast negotiation scheme, the domain management node identity may be determined by such a scheme, and whether the management node supports or enables fast domain management node identity negotiation may be determined by one of the following ways:

carrying a flag bit for supporting or enabling the fast domain management node identity negotiation in the domain management node identity negotiation message;

adding a flag bit in an extension field of the broadcast message to indicate whether the current node supports or enables the fast domain management node identity negotiation; and

a multi-domain service is defined, and whether the opposite node supports or enables the fast domain management node identity negotiation is obtained through service inquiry.

Fig. 10 is a schematic flow chart of determining a domain management node by using a fast domain node identity negotiation method in the management node identity negotiation according to an embodiment of the present invention. As an exemplary example, as shown in fig. 10, both the G1 node and the G2 node support or enable the fast domain node identity negotiation manner, and when the multi-domain device finds that the G1 node converts to the T node identity to initiate scanning to the G2 node, the G1 can be quickly determined as the domain member node, and the G2 can be quickly determined as the domain management node without referring to other parameters (such as the multi-domain identity flag bit, the domain priority, the domain management node identity, and the terminal capability described above).

Fig. 11 shows a flow chart of a method of exchanging identities of a domain management node and a domain member node in a multi-domain scenario according to an embodiment of the invention. In a multi-domain scenario, the domain management node has a management control function for domain member nodes, and the method is used for the identity change of the determined domain management node and domain member nodes in a plurality of communication domains. The identity changing method (i.e. the method of exchanging identities of the domain management node and the domain member node) comprises the steps of:

step S1101: sending a domain management node identity change request;

step S1102: receiving a domain management node identity change response; and

step S1103: and determining whether to change the identity of the domain management node according to the domain management node identity change response.

The domain management node identity change request in step S1101 includes a domain management node identity change request message, which may be issued by a domain management node (or a domain member node) in the multi-domain environment to make an identity change to the domain member node (or the domain management node). The received domain management node identity change response in step S1102 includes a domain management node identity change response message for notifying the other party of acceptance or rejection of the identity change. The domain management node identity change request message and the domain management node identity change response message can be sent as signaling or data related to the multi-domain service, and interact in a multi-domain service discovery mode.

In step S1103, when it is determined to change the identity of the domain management node, the identity of the domain management node is changed to the domain member node, and the identity of the domain member node is changed to the domain management node. When the identity of the domain management node is not changed, the domain management node maintains the identity of the domain management node, and the domain member node maintains the identity of the domain member node.

The method may further comprise the step of domain management node identity switching. In the step of domain management node identity exchange, the original domain management node and the original domain member node can send/receive necessary information when the domain management node identity is changed, for example, the original domain member node may need related information of the communication domain where the original domain management node is located, the terminal node of the communication domain or the neighborhood of the communication domain, so as to facilitate the conversion of the original domain member node into the domain management node, and make appropriate allocation for the subsequent air interface resources.

For nodes that have been determined to be domain management nodes or domain membership nodes, embodiments of the present application may support changing their identities in multiple domains through a domain management node identity change procedure.

For supporting domain management node identity change, that is, the identities of the domain management node and the domain member node can be exchanged through signaling interaction, the two multi-domain management nodes determine respective multi-domain node identities (domain management node or domain member node) after the previous multi-domain coordination, and then for some reasons, for example, the multi-domain information is changed, the two multi-domain management nodes can request to exchange domain node identities through a domain node identity change request message. The party receiving the request message decides whether to accept the identity change request and feeds back the result to the other party through the domain node identity change response message.

It should be noted that the domain node identity change request may be initiated by a domain management node or may be initiated by a domain member node. That is, in one embodiment, a domain management node identity change request is sent by a domain management node prior to an identity change; in another embodiment, the domain management node identity change request is sent by a domain member node prior to the identity change.

Fig. 12 is a schematic flow chart of identity change of a domain management node and a domain member node in an embodiment of the invention. As an exemplary example, as shown in fig. 12, as a result of the previous multi-domain coordination, the G1 node is a domain member node, the G2 is a domain management node, after which the multi-domain information of the G1 is changed, and the G1 requests the G2 to exchange the domain management node identity through a domain management node identity change request message. G2 may receive the request message:

(1) Receiving the request of G1, sending a response message for agreeing to change to G1, and then finishing identity exchange between the G1 node and the G2 node, wherein the G1 node is used as a domain management node, and the G2 node is used as a domain member node; or alternatively

(2) Refusing the request of G1, and sending a response message refusing to change to G1, and then the G1 node and the G2 node continuously maintain the respective original domain node identities.

Wherein:

the domain-management-node identity change request contains one or more of the following information:

identity change reasons, including but not limited to the change of the multi-domain negotiation parameters described above (i.e., multi-domain identity flag bit, domain priority, whether domain management node identity is already present, terminal capability, or whether it is a scanning node in the multi-domain device discovery process);

other neighborhood information, such as whether other neighbors exist, time-frequency resources used by other neighbors, and the like.

The domain management node identity change response message includes two types, namely:

(1) A response message agreeing to the domain node identity change, the message containing one or more of the following information:

other neighborhood information, such as whether other neighborhood exists, time-frequency resources used by other neighborhood, and the like;

the current domain information, such as how many terminal nodes in the management node communication domain, the time-frequency resources desired to be allocated, and the like.

(2) A response message rejecting the domain node identity change, the message comprising one or more of the following:

the reason for rejection, e.g. the requested communication domain or one or more end nodes in the communication domain, has a higher latency sensitivity;

the minimum waiting time for the next initiation of an identity change request.

In an optional embodiment of the present invention, the method for exchanging identities of a domain management node and a domain member node in the above multi-domain scenario may further include the steps of:

a domain management node change notification is sent by the domain management node to the domain member node,

after receiving the notification of the change of the domain management node, the domain member node performs the identity negotiation of the domain management node with the management node of another communication domain.

For example, in a multi-domain environment, the second management node is a domain management node, the first management node is a domain member node, and the second management node may send a domain management node change notification to the first management node to notify the first management node that the second management node will not perform a domain management node identity negotiation with a management node of another communication domain as a domain management node and/or notify the first management node, where the first management node may prepare for conversion to the management node of the communication domain where the first management node is located and/or perform a domain management node identity negotiation with the management node of the other communication domain through information transferred by the second management node.

The embodiment of the invention supports the domain management node to issue signaling for the domain member node, and indicates the domain member node to carry out multi-domain negotiation with the management node of another neighborhood. For example, in a multi-domain scenario consisting of more than two communication domains, one domain management node indicates, through a domain management node change notification message, that one domain member node connected thereto establishes multi-domain connection with other neighborhood management nodes. The scheme can be used for assisting other neighborhoods in the multi-domain environment to quickly establish a multi-domain connection when the domain management node in the original multi-domain judges that the domain management node is about to leave the multi-domain environment or when the identity of the original domain management node is changed.

Fig. 13 is a schematic flow chart of identity change of a domain management node and a domain member node in an embodiment of the invention. As an exemplary example, as shown in fig. 13, in the multi-domain environment formed by G1, G2, and G3, the domain management node G2 issues a domain management node change notification to the domain member node G1, indicating that multi-domain negotiation is performed between the domain member nodes G2 and G3; the process of G2 node and G3 node multi-domain negotiation may refer to the domain management node identity negotiation procedure described above or employ a domain management node identity negotiation procedure in the prior art standard.

The domain management node sends a domain management node change notification to the domain member node comprising one or more of the following messages:

the cause of the change;

whether the domain member node switches to the terminal node identity to scan for other nodes;

the domain member node needs to scan the information of the management node of another communication domain, such as identity, time-frequency location of broadcast message, multi-domain information, etc.

Fig. 14 is a flowchart illustrating a method for information interaction between nodes in a multi-domain scenario according to an embodiment of the present invention. The domain management node and the domain member node are determined in a plurality of communication domains, and the domain management node has a management control function for the domain member node in a multi-domain scene. The information interaction method between nodes in the multi-domain scene comprises the following steps:

Step S1401: and performing information interaction between one of the domain management node and the domain member node and the other of the domain management node and the domain member node or between the domain management nodes or between the domain member nodes, wherein the interacted information comprises at least one of the following:

the occupation condition of air interface resources;

interference information;

load ratio;

service information;

a communication domain identity class; and

and updating multi-domain information.

In step S1401, the information interaction between the domain management node and the domain member node, between the plurality of domain management nodes, or between the plurality of domain member nodes may be performed during resource allocation (e.g., the domain management node allocates resources for the domain member node), when the communication environment changes (e.g., the multi-domain information changes), or after the domain management node identity negotiation process in fig. 4 is completed and the domain management node and the domain member node are determined, or before the process of identity change between the domain management node and the domain member node in fig. 11.

After the domain management node identity negotiation, the neighborhood management node negotiates the domain management node identity and the domain member node identity, and the domain management node needs to allocate time-frequency resources for the domain member node (G node) to provide air interface resources of a communication domain formed by the domain member node (G node) and other terminal nodes connected to the domain member node (G node). On the one hand, because the service requirements in the communication domain, the number of nodes, the channel quality and the like change along with time, the requirements on the air interface time-frequency resources also change along with the time, and the domain management node needs to adjust the time-frequency resources allocated to the terminal nodes according to the requirements on the communication domain where the domain member nodes are located. On the other hand, when one domain management node and a plurality of domain member nodes (G nodes) form a multi-domain relationship, the domain management node needs to comprehensively consider the time-frequency resource requirements among the plurality of domain member nodes (G nodes) to determine a resource allocation scheme, so that the time-frequency resource conflicts among different neighborhoods are avoided. In addition, the related information of resource utilization of the interactive communication domains can be considered before the process of identity change between the domain management node and the domain member node (G node). Thus, in a multi-domain scenario, at least the following information needs to be interacted between a domain management node and a domain member node (information interaction may also be performed between multiple domain management nodes or between multiple domain member nodes), including:

The foregoing air interface resource occupation situations, for example:

time domain resources occupied by the current communication domain;

frequency domain resources occupied by the current communication domain.

The foregoing interference information, for example:

a frequency domain resource interference indication of the current communication domain;

a list of strongly interfered neighbors of the current communication domain.

The aforementioned load ratios, for example:

the guaranteed bit rate GBR (Guaranteed Bit Rate) service of the current communication domain requires a ratio of resources to available resources;

the ratio of non-guaranteed bit rate NGBR service demand resources to available resources in the current communication domain;

the total active user traffic demand resource of the current communication domain is proportional to the available resources.

The foregoing service information, for example:

the type of traffic (e.g., voice, data, time-frequency, etc.) scheduled in the current communication domain;

the bearer priority of the scheduled traffic in the current communication domain or the highest priority among all bearers (e.g., XQI, etc.).

The aforementioned communication domain identity class, for example:

indicating the grade or the air interface resource shortage of the current communication domain, and giving priority to the communication domain meeting the grade.

The foregoing multi-domain information update, for example:

other neighborhood change information detected by the current communication domain, such as newly added neighborhood, reduced neighborhood, etc. (the management node can determine the resource allocation according to the information).

The embodiment of the invention also provides a terminal device, which comprises: the system comprises a memory, a processor and a program stored in the memory and capable of running on the processor, wherein the program is executed by the processor to realize the management node identity negotiation method in the multi-domain scene in any one of the embodiments. Specific technical details of the terminal device are described above, and are not described herein.

The embodiment of the invention also provides a terminal device, which comprises: the system comprises a memory, a processor and a program stored on the memory and executable on the processor, wherein the program is executed by the processor to implement the method for exchanging identities of domain management nodes and domain member nodes in a multi-domain scenario in any of the embodiments described above. Specific technical details of the terminal device are described above, and are not described herein.

The embodiment of the invention also provides a terminal device, which comprises: the system comprises a memory, a processor and a program stored in the memory and capable of running on the processor, wherein the program is executed by the processor to realize the information interaction method between nodes in the multi-domain scene in any of the embodiments. Specific technical details of the terminal device are described above, and are not described herein.

Although not shown in detail, any device or means forming part of the network may comprise at least a processor, a storage unit and a communication interface, wherein the processor unit, the storage unit and the communication interface are configured to perform the method of any aspect of the invention.

Claims

1. A management node identity negotiation method in a multi-domain scenario for deciding which of a plurality of communication domains is a management node in a management mode, the plurality of communication domains including a first communication domain and a second communication domain, the first communication domain including a first management node and at least one first terminal node connected to the first management node, the second communication domain including a second management node and at least one second terminal node connected to the second management node, the method comprising:

2. The management node identity negotiation method as claimed in claim 1, wherein: when the first management node in the first communication domain is used as the domain management node, the second management node in the second communication domain is used as a domain member node, and the domain management node has a management control function for the domain member node.

3. The management node identity negotiation method according to claim 1, wherein before the step of performing management node identity negotiation by said first management node and said second management node, said method further comprises:

one of the first management node and the second management node converts to a terminal node identity to scan the other of the first management node and the second management node; and

Upon discovery of the other of the first management node and the second management node after successful scanning, a multi-domain control link is established between the first management node and the second management node.

4. The management node identity negotiation method as claimed in claim 1, wherein: the multi-domain identity bits are identified by two bits.

5. The management node identity negotiation method according to claim 1 or 4, wherein: the multi-domain identity bits are carried in a broadcast message.

6. The management node identity negotiation method according to claim 1 or 4, wherein: and the multi-domain identity zone bit is used as an attribute related to the multi-domain service, and interaction is performed in a multi-domain service discovery mode.

7. The management node identity negotiation method as claimed in claim 1, wherein: the domain priority is determined by parameters in synchronization signals transmitted in the first communication domain and the second communication domain.

8. The management node identity negotiation method as claimed in claim 1, wherein: and when the first management node negotiates with a third management node in a third communication domain, determining that the first management node is a domain management node and has the domain management node identity, and if the second management node in the second communication domain does not have the domain management node identity, determining that the first management node is the domain management node after the first management node and the second management node carry out management node identity negotiation.

9. The management node identity negotiation method as claimed in claim 1, wherein: when the terminal capability of the first management node is higher than that of the second management node, the first management node serves as the domain management node, and the second management node serves as a domain member node.

10. The management node identity negotiation method as claimed in claim 1, wherein: when the first management node is converted into a terminal node identity to scan the second management node, the first management node is used as the scanning node, and the second management node is used as the scanned node.

11. The management node identity negotiation method as claimed in claim 10, wherein: when the first management node is the scanning node and the second management node is the scanned node, after the first management node and the second management node carry out management node identity negotiation, the first management node is determined to be a domain member node, and the second management node is determined to be the domain management node.

12. The management node identity negotiation method as claimed in claim 10, wherein: when the first management node is the scanning node and the second management node is the scanned node, after the first management node and the second management node carry out management node identity negotiation, the second management node is determined to be a domain member node, and the first management node is the domain management node.

13. The management node identity negotiation method as claimed in claim 1, wherein: the process of managing node identity negotiation determines which of the first managing node and the second managing node is the domain managing node by sequentially comparing the multi-domain identity flag bit, the domain priority, the domain managing node identity, the terminal capability, and the scanning node.

14. The management node identity negotiation method as claimed in claim 1, wherein: which of the first management node and the second management node is the scanning node in the multi-domain device discovery process is the only consideration of the management node identity negotiation process of the first management node and the second management node.

15. The management node identity negotiation method as claimed in claim 14, wherein: the only consideration of the scanning node in the multi-domain device discovery process as the management node identity negotiation process is that the first management node and the second management node become a fast domain management node identity negotiation scheme, and whether to support or enable the fast domain management node identity negotiation is determined by one of the following ways:

Carrying a flag bit for supporting or enabling the rapid domain management node identity negotiation in a domain management node identity negotiation message;

adding a flag bit in an extension field of a broadcast message to indicate whether the current node supports or enables the fast domain management node identity negotiation; and

16. A method for exchanging identities of a domain management node and a domain member node in a multi-domain scenario, wherein the method is used for changing identities of the domain management node and the domain member node determined in a plurality of communication domains, and the domain management node has a management control function for the domain member node, and is characterized in that the method comprises:

sending a domain management node identity change request;

receiving a domain management node identity change response; and

17. The method of exchanging identities of a domain management node and a domain member node according to claim 16, wherein: the domain management node identity change request is sent by the domain management node before identity change.

18. The method of exchanging identities of a domain management node and a domain member node according to claim 16, wherein: the domain management node identity change request is sent by the domain member node before identity change.

19. The method of exchanging identities of a domain management node and a domain member node according to claim 16, wherein the domain management node identity change request comprises at least one of:

identity change reasons; and

other neighborhood information.

20. The method of exchanging identities of a domain management node and a domain member node of claim 16, wherein the domain management node identity change response message comprises a response message agreeing to a domain node identity change, the response message agreeing to a domain node identity change comprising at least one of:

other neighborhood information; and

current domain information.

21. The method of exchanging identities of a domain management node and a domain member node of claim 16, wherein the domain management node identity change response message comprises a response message rejecting a domain node identity change, the response message rejecting a domain node identity change comprising at least one of;

The reason for rejection; and

the minimum waiting time for the next initiation of an identity change request.

22. The method of exchanging identities of a domain management node and a domain member node according to claim 16, further comprising:

and after receiving the domain management node change notification, the domain member node performs domain management node identity negotiation with the management node of another communication domain.

23. The method of exchanging identities of a domain management node and a domain member node of claim 22, wherein said domain management node change notification comprises at least one of:

the cause of the change;

whether the domain member node switches to a terminal node identity to scan for other nodes; and

the domain member node needs information of the management node of another communication domain to be scanned.

24. An information interaction method between nodes in a multi-domain scene, wherein a domain management node and a domain member node are determined in the multi-domain scene, and the domain management node has a management control function for the domain member node, and the method is characterized by comprising the following steps:

the occupation condition of air interface resources;

interference information;

load ratio;

service information;

a communication domain identity class; and

and updating multi-domain information.

25. The method for information interaction between nodes in a multi-domain scenario according to claim 24, wherein the air interface resource occupation situation includes at least one of:

time domain resources occupied by the current communication domain; and

frequency domain resources occupied by the current communication domain.

26. The method for information interaction between nodes in a multi-domain scenario of claim 24, wherein the interference information comprises at least one of:

a frequency domain resource interference indication of the current communication domain; and

a list of strongly interfered neighbors of the current communication domain.

27. The method for information interaction between nodes in a multi-domain scenario of claim 24, wherein the load ratio comprises at least one of:

the ratio of guaranteed bit rate service demand resources to available resources in the current communication domain;

The ratio of non-guaranteed bit rate traffic demand resources to available resources in the current communication domain; and

28. The method for information interaction between nodes in a multi-domain scenario of claim 24, wherein the service information comprises at least one of:

the type of traffic scheduled in the current communication domain; and

the bearer priority of the scheduled traffic in the current communication domain or the highest priority of all bearers.

29. A terminal device, comprising: a memory, a processor and a program stored on the memory and executable on the processor, the program when executed by the processor to implement the method of any one of claims 1 to 15.

30. A terminal device, comprising: a memory, a processor and a program stored on the memory and executable on the processor, the program when executed by the processor to implement the method of any one of claims 16 to 23.

31. A terminal device, comprising: a memory, a processor and a program stored on the memory and executable on the processor, the program when executed by the processor to implement the method of any one of claims 24 to 28.