WO2023051253A1

WO2023051253A1 - End-to-end communication method, and electronic device and computer-readable storage medium

Info

Publication number: WO2023051253A1
Application number: PCT/CN2022/118775
Authority: WO
Inventors: 曾强辉; 生嘉
Original assignee: 惠州Tcl移动通信有限公司
Priority date: 2021-09-28
Filing date: 2022-09-14
Publication date: 2023-04-06
Also published as: CN115884135A

Abstract

Disclosed in the present application is an end-to-end communication method. The end-to-end communication method is applied to a first managed node. The end-to-end communication method comprises: sending a service request message to a management node, wherein the service request message is used for requesting the provision of a first service; receiving a service request response from the management node; on the basis of the service request response, determining a second managed node, which provides the first service; and performing end-to-end data interaction with the second managed node. Further disclosed in the present application are an electronic device and a computer-readable storage medium. In this way, the present application makes it possible to realize end-to-end communication between managed nodes.

Description

Peer-to-peer communication method, electronic device and computer-readable storage medium

technical field

The present application relates to the technical field of communication, and in particular, to an end-to-end communication method, electronic equipment, and a computer-readable storage medium.

Background technique

With the advent of the Internet of Everything era, more and more smart devices have appeared in people's lives, bringing a lot of convenience to human life. But corresponding to the rapid development of technology, people have higher and higher requirements for short-distance communication. In many fields such as smart cars, smart terminals, smart homes, and smart manufacturing, technologies such as VR/casting real-time games, high-reliability and low-latency real-time calls, interconnection between wearable devices and smartphones, and vehicle-mounted noise reduction technologies are available. Business features such as low latency, ultra-high reliability, high-precision synchronization, and multiple concurrency. However, the existing short-distance communication technology cannot meet the requirements of the above-mentioned technologies. In order to meet the needs of users and achieve higher performance, Starlight short-distance communication technology emerged as the times require.

Starlight wireless short-distance communication technology (hereinafter referred to as Starlight technology or Starlight) develops a new generation of wireless short-distance communication system. The existing protocol architecture of Starlight technology, its basic architecture is divided into three layers: access layer, basic service layer and basic application layer. The Starlight access layer provides the Starlight underlying interface. According to the requirements of different business scenarios, the current Starlight access layer provides two communication interfaces, SLB and SLE, for the upper layer of Starlight. The basic service layer provides service functions such as device discovery, service discovery, connection establishment/maintenance and release, QoS management, status monitoring, and information security for upper-layer business data. The basic application layer implements various application functions, and can define general application service frameworks such as basic communication, basic audio and video, and 5G integration.

In the network architecture of Starlight Technology, the nodes in the system include management nodes (also called G nodes) and managed nodes (also called T nodes). In a specific application scenario, a single management node manages a certain number of managed nodes, and the management node connects with these managed nodes to complete specific communication functions. A single management node and its connected managed nodes form a communication domain.

From the perspective of the current Starlight technology architecture, only the communication link between the management node and the managed node is defined, and the air interface interaction between the management node and the managed node is realized at the Starlight access layer. Based on the number of management nodes and the limited services provided, when all the management nodes within the communication range of the managed node cannot provide the service required by the managed node, but there are other managed nodes that can provide the service or there are other managed nodes When a node can better provide this service, it needs to consider the end-to-end communication service between the managed nodes.

Contents of the invention

The main purpose of this application is to provide an end-to-end communication method and electronic equipment, which can solve the problem that there is no end-to-end communication service between managed nodes in the existing starlight technology.

In order to solve the above technical problems, the first technical solution adopted by this application is to provide an end-to-end communication method, which is applied to the first managed node, and the method includes: sending a service request message to the management node, and the service request message is used for Provide the first service based on the request; receive the service request response from the management node; determine the second managed node providing the first service based on the service request response; and perform end-to-end data interaction with the second managed node.

In order to solve the above technical problems, the second technical solution adopted by this application is: provide an end-to-end communication method, which is applied to the management node, and the method includes: receiving a service request message from the first managed node, and the service request The message is used to request to provide the first service; if the management node cannot provide the first service, obtain the capability information of whether other managed nodes in the communication domain can provide the first service; determine that there is a candidate that can provide the first service based on the capability information The management node and/or the second managed node; sending a service request response to the first managed node, where the service request response carries at least one of the following: an indication of the existence of the second managed node, information about the candidate managed node, and the second managed node Information about the management node; assisting the first managed node to perform end-to-end data interaction with the second managed node.

In order to solve the above technical problems, the third technical solution adopted by this application is: provide an end-to-end communication method, which is applied to the managed node, the method includes: receiving a capability query message from the management node, and the capability query message is used for Query whether the first service is supported; report capability information to the management node, and the capability information is used to indicate whether the first service can be provided.

In order to solve the above technical problems, the fourth technical solution adopted by this application is to provide an electronic device, the electronic device includes a memory and a processor, the memory is used to store program data, and the program data can be executed by the processor to realize the following: The method described in the first or third technical solution.

In order to solve the above technical problems, the fifth technical solution adopted by the present application is to provide an electronic device, the electronic device includes a memory and a processor, the memory is used to store program data, and the program data can be executed by the processor to realize the following: The method described in the second technical solution.

In order to solve the above technical problems, the sixth technical solution adopted by this application is to provide a computer-readable storage medium, which stores program instructions, and when the program instructions are executed, the first to third technical solutions are implemented. method described in the protocol.

The beneficial effect of the present application is that: by sending the service request response to the management node, the first managed node determines whether there is a second managed node that meets the required service requirements in the communication domain of the management node through the service request response. The management node, and further can determine the relevant information of the second managed node, so as to realize the end-to-end direct connection data interaction between the first managed node and the second managed node through the time-frequency resource allocation of the management node, Or the end-to-end data interaction between the first managed node and the second managed node is implemented by forwarding data through the management node.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort.

[Corrected 12.10.2022 under Rule 91]
FIG. 1 is a schematic flow diagram of the first embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 2 is a schematic flow diagram of the second embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 3 is a schematic flowchart of the third embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 4 is a schematic flowchart of the fourth embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 5 is a schematic flowchart of the fifth embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 6 is a schematic flowchart of the sixth embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 7 is a schematic flowchart of the seventh embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 8 is a schematic flowchart of the eighth embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 9 is a schematic flowchart of the ninth embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 10 is a schematic flowchart of the tenth embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 11 is a schematic flowchart of the eleventh embodiment of the end-to-end communication method of this application;

[Corrected 12.10.2022 under Rule 91]
FIG. 12 is a schematic flowchart of the twelfth embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 13 is a schematic flowchart of the thirteenth embodiment of the end-to-end communication method of this application;

[Corrected 12.10.2022 under Rule 91]
FIG. 14 is a schematic flowchart of the fourteenth embodiment of the end-to-end communication method of this application;

[Corrected 12.10.2022 under Rule 91]
FIG. 15 is a schematic flowchart of the fifteenth embodiment of the end-to-end communication method of this application;

[Corrected 12.10.2022 under Rule 91]
FIG. 16 is a schematic sequence diagram of the sixteenth embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 17 is a schematic sequence diagram of the seventeenth embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 18 is a schematic sequence diagram of the eighteenth embodiment of the end-to-end communication method of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 19 is a schematic sequence diagram of the nineteenth embodiment of the end-to-end communication method of this application;

[Corrected 12.10.2022 under Rule 91]
FIG. 20 is a schematic structural diagram of the first embodiment of the electronic device of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 21 is a schematic structural diagram of the second embodiment of the electronic device of the present application;

[Corrected 12.10.2022 under Rule 91]
FIG. 22 is a schematic structural diagram of the first embodiment of a computer-readable storage medium of the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

The terms "first", "second", etc. in this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "include" and "have", as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes unlisted steps or units, or optionally further includes For other steps or units inherent in these processes, methods, products or apparatuses.

Reference herein to an "embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The occurrences of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is understood explicitly and implicitly by those skilled in the art that the embodiments described herein can be combined with other embodiments.

As shown in FIG. 1 , FIG. 1 is a schematic flowchart of the first embodiment of the end-to-end communication method of the present application. The method is applied to the first managed node, which includes the following steps:

S11: Send a service request message to the management node.

The first managed node is a terminal node that initiates a service request. The first managed node discovers the management node through a device discovery process. After discovering the management node, the first managed node sends a service request message to the management node. The service request message is used to request to provide the first service.

S12: Receive a service request response from the management node.

A service request response based on the sent service request message from the management node is received. After receiving the service request message sent by the managed node, the management node finds the second managed node that can provide the first service through query or broadcast, and then passes the identity or address information of the second managed node through the service request The response informs the first managed node. The service request response is carried by a system message. If the management node itself has the service requested by the service request message, it does not need to find other managed nodes, and directly responds to the service request, or if the management node can provide the requested service, the management node does not find a better one. Other managed nodes of the service, and then respond to the service request, which is a typical short-distance communication technology between the management node and the managed node, which is not within the scope of this application. If the service request response of the management node indicates that it is not capable of providing the service, the process ends, and the first managed node sends service request information to other management nodes.

S13: Determine a second managed node that provides the first service based on the service request response.

In the case that the service request response from the management node indicates that it has the ability to provide services, the first managed node, after receiving the service request response, determines the information about the second managed node contained in the service request response in the following manner: . The second managed node is a terminal node that can provide services.

Optionally, the first managed node directly reads the information of the second managed node from the service request response.

Optionally, the first managed node reads the indication that the second managed node exists from the service request response. The management node determines whether other managed nodes in its communication domain support the service required by the first managed node by broadcasting or inquiring. If other managed nodes support the service, they will respond to the management node's service request through public channel resources. Otherwise, no service request response is performed. When receiving service request responses from other managed nodes, the management node sends a service request response including an indication that the second managed node exists to the first managed node.

Optionally, the first managed node reads information of candidate managed nodes capable of providing the first service from the service request response, selects a second managed node from the candidate managed nodes, and sends the second managed node to the management node. Information about managed nodes. The management node determines whether other managed nodes in its communication domain support the services required by the first managed node by broadcasting or inquiring. The information of multiple other managed nodes supporting the service of the first managed node is sent to the first managed node through the service request response, as the candidate managed node information.

Wherein, the information of the managed node may be the identity information of the managed node in the communication domain, such as an IP address, a MAC address, or a global starlight unique identifier, and the like.

S14: Perform end-to-end data interaction with the second managed node.

After the first managed node determines the information of the second managed node, end-to-end data interaction can be performed in the following manner.

Optionally, after the existing Starlight SLB access layer is enhanced, after the management node allocates time-frequency resources for the managed nodes, a direct data link can be established between the managed nodes. A direct data link is established between the first managed node and the second managed node to realize end-to-end data interaction.

Wherein, if a data link needs to be established between the managed node and the management node, the managed node needs to support the dual connection function, otherwise it does not need it.

Optionally, the first managed node and the second managed node perform data forwarding through the management node, so as to realize end-to-end data interaction.

As shown in FIG. 2 , FIG. 2 is a schematic flowchart of a second embodiment of the end-to-end communication method of the present application. The method is applied to the first managed node, which includes the following steps:

S21: Send a service request message to the management node.

The first managed node is a terminal node that initiates a service request. The first managed node discovers the management node through the device discovery process, and the management node allocates public resources for the service request to it. Referring to the concept in TS23.303modeB, after discovering the management node, the first managed node sends a service request message by using the public resources allocated by the management node without establishing a communication link with the management node. The service request message is used to request to provide the first service.

S22: Receive a service request response from the management node.

S23: Determine a second managed node that provides the first service based on the service request response.

Wherein, the information of the managed node may include the identity information of the managed node in the communication domain, such as an IP address, a MAC address, or a global starlight unique identifier, and the like.

S24: Establish a communication link with the management node.

After the first managed node determines the information of the second managed node, the first managed node initiates a communication link establishment request to the management node, and establishes a communication link with the management node. The communication link may be an XRC link.

S25: Perform end-to-end data interaction with the second managed node.

As shown in FIG. 3 , FIG. 3 is a schematic flowchart of a third embodiment of the end-to-end communication method of the present application. The method is applied to the first managed node, which includes the following steps:

S31: Establish a communication link with the management node.

The first managed node is a terminal node that initiates a service request. The first managed node discovers the management node through a device discovery process. The first managed node sends a communication link establishment request to the management node, and establishes a communication link with the management node. The communication link may be an XRC link.

S32: Send a service request message to the management node.

After the communication link is established, the first managed node sends a service request message to the management node. The service request message is used to request to provide the first service.

S33: Receive a service request response from the management node.

A service request response based on the sent service request message from the management node is received. After receiving the service request message sent by the managed node, the management node finds the second managed node that can provide the first service through query or broadcast, and then passes the identity or address information of the second managed node through the service request The response informs the first managed node. The service request response is carried by a system message. If the management node itself has the service requested by the service request message, it does not need to find other managed nodes, and directly responds to the service request, or if the management node can provide the requested service, the management node does not find a better one. Other managed nodes of the service, and then respond to the service request, which is a typical short-distance communication technology between the management node and the managed node, which is not within the scope of this application. If the service request response of the management node shows that it does not have the ability to provide services, the process ends, the first managed node releases the communication link with the management node, establishes communication link connections with other management nodes, and sends data to other management nodes. Send a service request message.

S34: Determine a second managed node that provides the first service based on the service request response.

Optionally, the first managed node reads the indication that the second managed node exists from the service request response. The management node determines whether other managed nodes in its communication domain support the service required by the first managed node by broadcasting or inquiring. If other managed nodes support the service, they will respond to the service request to the management node through public channel resources. Otherwise, no service request response is performed. When receiving service request responses from other managed nodes, the management node sends a service request response including an indication that the second managed node exists to the first managed node.

Optionally, the first managed node reads information of candidate managed nodes capable of providing the first service from the service request response, selects a second managed node from the candidate managed nodes, and sends the second managed node to the management node. Information about managed nodes. The management node determines whether other managed nodes in its communication domain support the service required by the first managed node by broadcasting or inquiring. The information of multiple other managed nodes supporting the service of the first managed node is sent to the first managed node through the service request response, as the candidate managed node information.

S35: Perform end-to-end data interaction with the second managed node.

As shown in FIG. 4 , FIG. 4 is a schematic flowchart of a fourth embodiment of the end-to-end communication method of the present application. It is a further extension of steps S14, S25, and S35. The method is applied to the first managed node, which includes the following steps:

S41: Receive information about directly connected resources allocated by the management node.

Directly connected resources include the following types of resource information.

Optionally, the directly connected resources include scheduling time-frequency resources of the second managed node.

Optionally, the directly connected resource is a resource pool uniformly allocated by the management node to the first managed node and the second managed node.

Optionally, the directly connected resources include scheduling time-frequency resources of the second managed node and a resource pool uniformly allocated by the management node to the first managed node and the second managed node. The first managed node selects the information of which directly connected resource to use for end-to-end data interaction.

S42: Perform directly connected end-to-end data interaction with the second managed node by using the directly connected resource.

Direct end-to-end data interaction can be realized in the following two ways.

Optionally, when the directly connected resources include time-frequency resources for scheduling the second managed node, the management node will also send time-frequency resources for scheduling the first managed node to the second managed node. The time-frequency resource is allocated and designated by the management node for the first managed node and the second managed node. This enables the first managed node and the second managed node to respectively receive data messages from each other on corresponding time-frequency resources, thereby realizing an end-to-end direct data link between the first managed node and the second managed node.

Optionally, the directly connected resource is a resource pool allocated by the management node to the first managed node and the second managed node. The first managed node and the second managed node occupy physical resources in the allocated resource pool by means of LBT to send data. When receiving data, the receiver can obtain the time-frequency resource of the sender's physical resource carried in the resource block through blind detection of fixed resource blocks in the frame structure, such as SCI, in the pre-allocated resource pool. Thus, an end-to-end direct data link between the first managed node and the second managed node is established.

As shown in FIG. 5 , FIG. 5 is a schematic flowchart of a fifth embodiment of the end-to-end communication method of the present application. It is a further extension of steps S14, S25, and S35. The method is applied to the first managed node, which includes the following steps:

S51: Use the management node as a forwarding node to perform forwarding-based end-to-end data interaction with the second managed node.

After determining the relevant information of the second managed node, the first managed node and the management node continue to establish a data link on the basis of establishing a control link, so as to send relevant data information to the management node. The management node is used as a forwarding node to realize end-to-end data interaction between the first managed node and the second managed node.

Optionally, a control link and a data link are established between the management node and the first managed node and between the management node and the second managed node. On the control plane, the management node schedules the first managed node and the second managed node through the control link. On the data level, the management node acts as a relay node to implement service interaction between the first managed node and the second managed node.

Optionally, a control link and a data link are established between the management node and the first managed node, and the first managed node sends relevant data information to the management node through the data link. When the relevant data information is a one-way extremely small amount of data transmission, such as printing instructions, switching instructions, etc., these instructions can be maintained in the service mapping type table of the QoS management module in consideration of compatibility. Then the management node sends relevant data information to the second managed node by broadcasting, thereby realizing data transmission between the first managed node and the second managed node.

As shown in FIG. 6 , FIG. 6 is a schematic flowchart of a sixth embodiment of the end-to-end communication method of the present application. The method is applied to a management node and includes the following steps:

S61: Receive a service request message from the first managed node.

The first managed node is a terminal node that initiates a service request. The first managed node discovers the management node through a device discovery process. After discovering the management node, the first managed node sends a service request message to the management node. The management node receives the service request information of the first managed node. The service request message is used to request to provide the first service.

S62: Obtain capability information about whether other managed nodes in the communication domain can provide the first service.

After receiving the service request message sent by the managed node, the management node can determine whether other managed nodes in the communication domain can provide the services required by the first managed node in the following ways.

Optionally, read stored capability information. Query the capability information of the managed node that has been obtained in the management node to determine whether it supports the service.

Optionally, a capability query message is sent to other managed nodes in the communication domain, where the capability query message is used to query whether the first service is supported. Receive capability information reported by other managed nodes in the communication domain.

Optionally, the management node sends the capability query information in a broadcast manner. If other managed nodes support the service, they will respond to the management node's service request through public channel resources. Otherwise, no service request response is performed.

If the management node itself has the service requested by the service request message, it does not need to find other managed nodes, and directly responds to the service request, or if the management node can provide the requested service, the management node does not find a better one. Other managed nodes of the service, and then respond to the service request, which is a typical short-distance communication technology between the management node and the managed node, which is not within the scope of this application. If other managed nodes in the communication domain do not have the ability to provide services, the service request response sent to the first managed node indicates that they do not have the ability to provide services, so that the first managed node can end the process.

S63: Determine that there is a candidate managed node and/or a second managed node capable of providing the first service based on the capability information.

If there are other managed nodes that can support the service required by the first managed node in the communication domain, when there is only one managed node supporting the service in the communication domain, the managed node is selected as the second managed node.

When there are multiple managed nodes supporting services in the communication domain, all of them are regarded as candidate managed nodes. Further, the management node may select the second managed node from among the managed nodes according to information such as RSRP and SINR reported by the managed nodes.

S64: Send a service request response to the first managed node.

In the case that the service request response indicates that it has the ability to provide the service, the service request response carries at least one of the following: an indication of the existence of the second managed node, information of candidate managed nodes, and information of the second managed node.

Optionally, the service request response carries an indication that the second managed node exists. The management node determines whether other managed nodes in its communication domain support the service required by the first managed node by broadcasting or inquiring. If other managed nodes support the service, they will respond to the service request to the management node through public channel resources. Otherwise, no service request response is performed. When receiving service request responses from other managed nodes, the management node sends a service request response including an indication that the second managed node exists to the first managed node. When the data information to be transmitted by the first managed node is subsequently received, the data information may be transmitted to the second managed node in the form of broadcast.

Optionally, the management node sends the information of multiple candidate managed nodes to the first managed node through a service request response for selection by the first managed node.

Optionally, the management node sends the information of the second managed node to the first managed node through a service request response.

S65: Assist the first managed node to perform end-to-end data interaction with the second managed node.

Optionally, after enhancing the existing Starlight SLB access layer, the management node allocates time-frequency resources for the managed nodes, and direct data links can be established between the managed nodes. A direct data link is established between the first managed node and the second managed node to realize end-to-end data interaction.

As shown in FIG. 7 , FIG. 7 is a schematic flowchart of a seventh embodiment of the end-to-end communication method of the present application. The method is applied to a management node and includes the following steps:

S71: Receive a service request message from the first managed node.

The first managed node is a terminal node that initiates a service request. The first managed node discovers the management node through the device discovery process, and the management node allocates public resources for the service request to it. Referring to the concept in TS23.303modeB, after discovering the management node, the first managed node sends a service request message to the management node without establishing a communication link with the management node. The management node receives the service request information of the first managed node. The service request message is used to request to provide the first service.

S72: Obtain capability information about whether other managed nodes in the communication domain can provide the first service.

If other managed nodes in the communication domain do not have the ability to provide services, the service request response sent to the first managed node indicates that they do not have the ability to provide services, so that the first managed node can end the process.

S73: Determine that there is a candidate managed node and/or a second managed node capable of providing the first service based on the capability information.

S74: Send a service request response to the first managed node.

Optionally, the service request response carries an indication that the second managed node exists. The management node determines whether other managed nodes in its communication domain support the service required by the first managed node by broadcasting or inquiring. If other managed nodes support the service, they will respond to the management node's service request through public channel resources. Otherwise, no service request response is performed. When receiving service request responses from other managed nodes, the management node sends a service request response including an indication that the second managed node exists to the first managed node. When the data information to be transmitted by the first managed node is subsequently received, the data information may be transmitted to the second managed node in the form of broadcast.

S75: Establish a communication link with the first managed node.

After the first managed node determines the information of the second managed node, the first managed node initiates a communication link establishment request to the management node, and the management node establishes a communication link with the first managed node. The communication link may be an XRC link.

S76: Assist the first managed node to perform end-to-end data interaction with the second managed node.

As shown in FIG. 8 , FIG. 8 is a schematic flowchart of an eighth embodiment of the end-to-end communication method of the present application. The method is applied to a management node and includes the following steps:

S81: Establish a communication link with the first managed node.

The first managed node is a terminal node that initiates a service request. The first managed node discovers the management node through a device discovery process. The first managed node sends a communication link establishment request to the management node, and the management node establishes a communication link with the first managed node. The communication link may be an XRC link.

S82: Receive a service request message from the first managed node.

The first managed node sends a service request message to the management node through the communication link. The service request message is used to request to provide the first service.

S83: Obtain capability information about whether other managed nodes in the communication domain can provide the first service.

If other managed nodes in the communication domain do not have the ability to provide services, the service request response sent to the first managed node indicates that they do not have the ability to provide services, so that the first managed node can end the process and release the communication link.

S84: Determine that there is a candidate managed node and/or a second managed node capable of providing the first service based on the capability information.

S85: Send a service request response to the first managed node.

S86: Assist the first managed node to perform end-to-end data interaction with the second managed node.

As shown in FIG. 9 , FIG. 9 is a schematic flowchart of a ninth embodiment of the end-to-end communication method of the present application. It is a further extension of steps S63, S73, and S83. The method is applied to a management node and includes the following steps:

S91: Select at least part of the managed nodes capable of providing the first service as candidate management nodes based on the capability information.

When there are multiple managed nodes supporting the first service in the communication domain, the management node regards them all as candidate managed nodes.

S92: Select a second managed node from candidate management nodes.

The management node may select a second managed node from the candidate managed nodes according to information such as RSRP and SINR reported by the candidate managed nodes, so as to provide better services for the first managed node.

As shown in FIG. 10 , FIG. 10 is a schematic flowchart of a tenth embodiment of the end-to-end communication method of the present application. It is a further extension of steps S65 and S86. The method is applied to a management node and includes the following steps:

S101: Allocate direct connection resources for the first managed node and the second managed node.

Optionally, the directly connected resources include scheduling time-frequency resources of the second managed node and scheduling time-frequency resources of the first managed node.

Optionally, the directly connected resources include time-frequency resources for scheduling the second managed node and the first managed node, and a resource pool uniformly allocated by the management node for the first managed node and the second managed node. The first managed node selects the information of which directly connected resource to use for end-to-end data interaction.

S102: Send information about directly connected resources to the first managed node and the second managed node.

Optionally, the management node sends the time-frequency resource for scheduling the second managed node to the first managed node, and sends the time-frequency resource for scheduling the first managed node to the second managed node.

Optionally, the management node sends information about the resource pool to the first managed node and the second managed node.

Optionally, the management node sends time-frequency resources for scheduling the second managed node to the first managed node, sends time-frequency resources for scheduling the first managed node to the second managed node, and sends the time-frequency resource for scheduling the first managed node to the first managed node The resource pool information is sent with the second managed node. The first managed node selects the information of which directly connected resource to use for end-to-end data interaction.

As shown in FIG. 11 , FIG. 11 is a schematic flowchart of an eleventh embodiment of the end-to-end communication method of the present application. It is a further extension of steps S65 and S86. The method is applied to a management node and includes the following steps:

S111: Forward end-to-end data between the first managed node and the second managed node.

After the first managed node determines the relevant information of the second managed node, the first managed node and the management node continue to establish a data link on the basis of establishing a control link to send relevant data information to the management node . The management node is used as a forwarding node to realize end-to-end data interaction between the first managed node and the second managed node.

Optionally, a control link and a data link are established between the management node and the original managed node, and the first managed node sends relevant data information to the management node through the data link. When the relevant data information is a one-way extremely small amount of data transmission, such as printing instructions, switching instructions, etc., these instructions can be maintained in the service mapping type table of the QoS management module in consideration of compatibility. Then the management node sends relevant data information to the second managed node by broadcasting, thereby realizing data transmission between the first managed node and the second managed node.

As shown in FIG. 12 , FIG. 12 is a schematic flowchart of a twelfth embodiment of the end-to-end communication method of the present application. The method is applied to a managed node, and it includes the following steps:

S121: Receive a capability query message from the management node.

The capability query message is used to query whether the first service is supported. The capability query message may be received from the management node alone, or may be sent and received by the management node in a broadcast manner.

S122: Report capability information to the management node.

After inquiring whether the services it can provide include the first service, it sends a service request response to the management node and reports capability information. The capability information is used to indicate whether the first service can be provided. Or, if it cannot provide the first service itself, it does not respond to the service request and does not report the capability information.

As shown in FIG. 13 , FIG. 13 is a schematic flowchart of a thirteenth embodiment of the end-to-end communication method of the present application. The method is applied to a managed node, and it includes the following steps:

S131: Receive a capability query message from the management node.

S132: Report capability information to the management node.

S133: Receive information about directly connected resources allocated by the management node.

Optionally, the directly connected resources include time-frequency resources for scheduling the first managed node.

Optionally, the directly connected resources include scheduling time-frequency resources of the first managed node and a resource pool uniformly allocated by the management node to the first managed node and the second managed node. The first managed node selects the information of which directly connected resource to use for end-to-end data interaction.

S134: Perform directly connected end-to-end data interaction with the first managed node requesting the first service by using the directly connected resources.

Direct end-to-end data interaction can be realized in the following two ways.

Optionally, when the directly connected resource includes the time-frequency resource of the source second managed node, the management node will also send the time-frequency resource for scheduling the second managed node to the first managed node. The time-frequency resource is allocated and designated by the management node for the first managed node and the second managed node. This enables the first managed node and the second managed node to respectively receive data messages from each other on corresponding time-frequency resources, thereby realizing an end-to-end direct data link between the first managed node and the second managed node.

As shown in FIG. 14 , FIG. 14 is a schematic flowchart of a fourteenth embodiment of the end-to-end communication method of the present application. It is a further extension of step S134. The method is applied to a managed node, and it includes the following steps:

S141: Use the management node as a forwarding node to perform forwarding-based end-to-end data interaction with the first managed node requesting the first service.

As shown in FIG. 15 , FIG. 15 is a schematic flowchart of a fifteenth embodiment of the end-to-end communication method of the present application. The method is applied to a managed node, and it includes the following steps:

S151: Receive a capability query message from the management node.

S152: Report capability information to the management node.

S153: Receive service data sent by the management node in a broadcast manner.

The service data comes from the first managed node requesting the first service. After the first managed node determines the relevant information of the second managed node, a control link and a data link are established between the management node and the first managed node, and the first managed node communicates with the management node through the data link. Send relevant data information. When the relevant data information is a one-way extremely small amount of data transmission, such as printing instructions, switching instructions, etc., these instructions can be maintained in the service mapping type table of the QoS management module in consideration of compatibility. Then the management node sends relevant data information to the second managed node by broadcasting, thereby realizing data transmission between the first managed node and the second managed node.

As shown in FIG. 16 , FIG. 16 is a schematic sequence diagram of a sixteenth embodiment of the end-to-end communication method of the present application. The method includes the following steps:

S161: The first managed node and the management node perform device discovery.

S162: The first managed node establishes a communication link with the management node.

S163: The first managed node sends a service request to the management node.

S164: The management node queries the managed node for services of the managed node.

S165: The managed node reports the service.

S166: The management node determines the second managed node.

S167: The management node sends a service request response to the first managed node.

S168: The management node allocates time-frequency resources for the first managed node.

S169: The management node allocates time-frequency resources for the second managed node.

S170: The management node sends time-frequency resource information for scheduling the second managed node to the first managed node.

S171: The management node sends time-frequency resource information for scheduling the first managed node to the second managed node.

S172: The first managed node establishes an end-to-end data link with the managed node.

In this embodiment, the management node queries other managed nodes in the communication domain, and receives the service report information of the managed nodes. When only one managed node meets the required service reporting information, the management node determines that it is the second managed node; when it receives multiple managed nodes that meet the required reporting information, the management node regards all of them as candidates The managed node further determines the most suitable managed node that can provide the best service through information such as RSRP and SINR reported by the candidate managed node as the second managed node. After determining the second managed node, the management node sends a service request response to the first managed node based on the information of the second managed node. For ease of description, only the selected second managed node is shown in the figure, but actually there may be more other managed nodes in the communication domain of the management node. For the same or similar steps in this embodiment, refer to the foregoing embodiments, and details are not repeated here.

As shown in FIG. 17 , FIG. 17 is a schematic sequence diagram of a seventeenth embodiment of the end-to-end communication method of the present application. The method includes the following steps:

S181: The first managed node performs device discovery.

S182: The first managed node sends a service request to the management node.

S183: The management node queries the managed node for services of the managed node.

S184: The managed node reports the service.

S185: The management node determines the second managed node.

S186: The management node sends a service request response to the first managed node.

S187: The first managed node establishes a communication link with the management node.

S188: The management node allocates time-frequency resources for the first managed node.

S189: The management node allocates time-frequency resources for the second managed node.

S190: The management node sends time-frequency resource information for scheduling the second managed node to the first managed node.

S191: The management node sends time-frequency resource information for scheduling the first managed node to the second managed node.

S192: The first managed node establishes an end-to-end data link with the managed node.

As shown in FIG. 18 , FIG. 18 is a schematic sequence diagram of an eighteenth embodiment of the end-to-end communication method of the present application. The method includes the following steps:

S201: The first managed node and the management node perform device discovery.

S202: The first managed node establishes a communication link with the management node.

S203: The first managed node sends a service request to the management node.

S204: The management node queries the managed node for services of the managed node.

S205: The managed node reports the service.

S206: The management node determines the second managed node.

S207: The management node sends a service request response to the first managed node.

S208: The management node executes data forwarding.

As shown in FIG. 19 , FIG. 19 is a schematic sequence diagram of a nineteenth embodiment of the end-to-end communication method of the present application. The method includes the following steps:

S211: The first managed node and the management node perform device discovery.

S212: The first managed node establishes a communication link with the management node.

S213: The first managed node sends a service request to the management node.

S214: The management node performs broadcast polling (service request) to the managed node.

S215: The managed node sends a service request response to the management node.

S216: The management node sends a service request response to the first managed node.

S217: The first managed node sends related data to the management node.

S218: The management node broadcasts and transmits relevant data to the managed node.

In this embodiment, the management node broadcasts a service request to the managed node, receives a service request response from the managed node that meets the service requirement, and based on this, sends a message indicating that there is a managed node that meets the service requirement in the communication domain to the first managed node. Node's service request response. For ease of description, only the selected second managed node is shown in the figure, but actually there may be more other managed nodes in the communication domain of the management node. For the same or similar steps in this embodiment, refer to the foregoing embodiments, and details are not repeated here.

As shown in FIG. 20 , FIG. 20 is a schematic structural diagram of the first embodiment of the electronic device of the present application. The electronic device includes: a processor 110 and a memory 120 .

The processor 110 controls operations of the communication device, and the processor 110 may also be called a CPU (Central Processing Unit, central processing unit). The processor 110 may be an integrated circuit chip, capable of processing signal sequences. The processor 210 can also be a general-purpose processor, a digital signal sequence processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

The memory 120 stores instructions and data required for the processor 110 to work.

The processor 110 is configured to execute instructions to implement the methods described in any one of the first embodiment to the fifth embodiment, the twelfth embodiment to the fifteenth embodiment of the service discovery method of this application, that is, a possible combined method.

As shown in FIG. 21 , FIG. 21 is a schematic structural diagram of a second embodiment of the electronic device of the present application. The electronic device includes: a processor 210 and a memory 220 .

The processor 210 controls the operation of the communication device, and the processor 210 may also be called a CPU (Central Processing Unit, central processing unit). The processor 210 may be an integrated circuit chip, capable of processing signal sequences. The processor 210 can also be a general-purpose processor, a digital signal sequence processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

The memory 220 stores instructions and data required for the processor 210 to work.

The processor 210 is configured to execute instructions to implement the method described in any one of the sixth embodiment to the eleventh embodiment of the service discovery method of this application, that is, a possible combined method.

As shown in FIG. 22 , FIG. 22 is a schematic structural diagram of a first embodiment of a computer-readable storage medium of the present application. The computer-readable storage medium includes a memory 310, and the memory 310 stores program data. When the program data is executed, the method provided by any embodiment and possible combination of the measurement method of the present application is implemented.

The memory 310 may include a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a flash memory (Flash Memory), a hard disk, an optical disk, and the like.

To sum up, by sending the service request response to the management node, the first managed node determines whether there is a second managed node that meets the required service requirements in the communication domain of the management node through the service request response. , and further can determine the relevant information of the second managed node, so as to realize the end-to-end direct data interaction between the first managed node and the second managed node through the time-frequency resource allocation of the management node, or through The end-to-end data interaction between the first managed node and the second managed node is realized by the management node forwarding the data.

In the several implementation manners provided in this application, it should be understood that the disclosed methods and devices may be implemented in other ways. For example, the device implementation described above is only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be Incorporation may either be integrated into another system, or some features may be omitted, or not implemented.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated units in the above other embodiments are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the methods described in various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc., which can store program codes. .

[Corrected 12.10.2022 under Rule 91]
The above is only an embodiment of the application, and does not limit the patent scope of the application. Any equivalent structure or equivalent process conversion made by using the specification and drawings of this application, or directly or indirectly used in other related technologies fields, are all included in the scope of patent protection of this application in the same way.

Claims

An end-to-end communication method applied to a first managed node, characterized in that the method includes:

sending a service request message to the management node, where the service request message is used to request provision of the first service;

receiving a service request response from the management node;

determining a second managed node providing the first service based on the service request response;

Perform end-to-end data interaction with the second managed node.
The method according to claim 1, characterized in that,

Before sending the service request message to the management node, it further includes:

Establish a communication link with the management node.
The method according to claim 1, characterized in that,

The sending the service request message to the management node includes:

sending the service request message by using the public resource allocated by the management node.
The method according to claim 3, characterized in that,

The service request response is carried by a system message.
The method according to claim 3, characterized in that,

After determining the second managed node providing the first service based on the service request response, the step further includes:

Establish a communication link with the management node.
The method according to any one of claims 1-5, characterized in that,

The determining the second managed node providing the first service based on the service request response includes:

reading the information of the second managed node from the service request response; or

reading an indication of the presence of the second managed node from the service request response; or

reading information of candidate managed nodes capable of providing the first service from the service request response;

selecting the second managed node from among the candidate managed nodes;

sending the information of the second managed node to the management node.
The method according to any one of claims 1-5, characterized in that,

The end-to-end data interaction with the second managed node includes:

receiving information about directly connected resources allocated by the management node;

Perform direct-connected end-to-end data interaction with the second managed node by using the directly-connected resources.
The method according to claim 7, characterized in that,

The directly connected resources include time-frequency resources for scheduling the second managed node, and/or a resource pool uniformly allocated for the first managed node and the second managed node.
The method according to any one of claims 1-5, characterized in that,

The end-to-end data interaction with the second managed node includes:

Using the management node as a forwarding node to perform forwarding-based end-to-end data interaction with the second managed node.
An end-to-end communication method applied to a management node, characterized in that the method comprises:

receiving a service request message from a first managed node, where the service request message is used to request provision of a first service;

If the management node cannot provide the first service, obtain capability information about whether other managed nodes in the communication domain can provide the first service;

determining that there is a candidate managed node and/or a second managed node capable of providing the first service based on the capability information;

Sending a service request response to the first managed node, where the service request response carries at least one of the following: an indication that the second managed node exists, information about the candidate managed node, and the second managed node Node information;

assisting the first managed node to perform end-to-end data interaction with the second managed node.
The method according to claim 10, characterized in that,

Before receiving the service request message from the first managed node, it further includes:

Establish a communication link with the first managed node.
The method according to claim 10, characterized in that,

Before receiving the service request message from the first managed node, it further includes:

Allocating public resources for sending the service request message to the first managed node.
The method according to claim 12, characterized in that,

The service request response is carried by a system message.
The method according to claim 12, characterized in that,

The service request response sent to the first managed node further includes:

Establish a communication link with the first managed node.
The method according to any one of claims 10-14, characterized in that,

The obtaining capability information of whether other managed nodes in the communication domain can provide the first service includes:

read the stored capability information; or

sending a capability query message to other managed nodes in the communication domain, where the capability query message is used to query whether the first service is supported;

and receiving the capability information reported by other managed nodes in the communication domain.
The method according to claim 15, characterized in that,

The sending a capability query message to other managed nodes in the communication domain includes:

The capability query message is sent in a broadcast manner.
The method according to claim 16, characterized in that,

The assisting the first managed node to perform end-to-end data interaction with the second managed node includes:

receiving service data from the first managed node;

The service data is sent in a broadcast manner.
The method according to any one of claims 10-14, characterized in that,

The determining based on the capability information that there are candidate managed nodes and/or second managed nodes capable of providing the first service includes:

Selecting at least some managed nodes capable of providing the first service as the candidate management nodes based on the capability information.
The method of claim 18, wherein,

After selecting at least part of the managed nodes capable of providing the first service based on the capability information as the candidate management nodes, the step further includes:

Selecting the second managed node from the candidate management nodes.
The method according to any one of claims 10-14, characterized in that,

The assisting the first managed node to perform end-to-end data interaction with the second managed node includes:

Allocating direct connection resources for the first managed node and the second managed node;

sending the information of the directly connected resources to the first managed node and the second managed node.
The method of claim 20, wherein

The direct connection resources include time-frequency resources for scheduling the first managed node and the second managed node, and sending the direct connection to the first managed node and the second managed node Resource information includes:

Sending the time-frequency resource for scheduling the second managed node to the first managed node, and sending the time-frequency resource for scheduling the first managed node to the second managed node.
The method of claim 20, wherein

The direct connection resource includes a resource pool uniformly allocated for the first managed node and the second managed node, and sending the direct connection to the first managed node and the second managed node Linked resource information includes:

sending the information of the resource pool to the first managed node and the second managed node.
The method according to any one of claims 10-14, characterized in that,

The assisting the first managed node to perform end-to-end data interaction with the second managed node includes:

Forwarding end-to-end data between the first managed node and the second managed node.
An end-to-end communication method applied to a managed node, characterized in that the method includes:

receiving a capability query message from the management node, where the capability query message is used to query whether the first service is supported;

reporting capability information to the management node, where the capability information is used to indicate whether the first service can be provided.
The method of claim 24, further comprising:

receiving information about directly connected resources allocated by the management node;

Perform direct-connected end-to-end data interaction with the first managed node requesting the first service by using the direct-connection resources.
The method of claim 25, wherein,

The directly connected resources include time-frequency resources for scheduling the first managed node, and/or a resource pool uniformly allocated for the first managed node and the managed node.
The method of claim 24, further comprising:

Using the management node as a forwarding node to perform forwarding-based end-to-end data interaction with the first managed node requesting the first service.
The method of claim 24, wherein,

Said receiving the capability query message from the management node includes:

Receive the capability query message sent by the management node in a broadcast manner.
The method of claim 28, further comprising:

receiving service data sent by the management node in a broadcast manner, where the service data comes from the first managed node requesting the first service.
An electronic device, characterized in that it includes a memory and a processor, the memory is used to store program data, and the program data can be executed by the processor, so as to implement any of claims 1-9 or 24-29 one of the methods described.
An electronic device, characterized by comprising a memory and a processor, the memory is used to store program data, and the program data can be executed by the processor, so as to implement any one of claims 10-23 Methods.
A computer-readable storage medium, wherein the storage medium stores program instructions, and when the program instructions are executed, the method according to any one of claims 1-29 is realized.