Method for relay network duplex coordination and relay node device

Abstract

Embodiments of the present application provide a method for duplex coordination of a relay network and a relay node device. The relay node device can receive a message sent by its parent node device according to a dynamically configured first time domain resource, and send a message to its child node device according to a dynamically configured second time domain resource, thereby meeting the requirements of 5G NR for backhaul link communication. The method comprises: a first node device receiving a first message sent by a second node device on a first time domain resource and sending a second message to a third node device on a second time domain resource according to configuration information, wherein the configuration information indicates the first time domain resource and / or the second time domain resource, the second node device is a parent node of the first node device, and the third node device is a child node of the first node device.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a method for duplex coordination in a relay network and a relay node device. Background Technology

[0002] In Release 10, the duplex coordination and scheduling of uplink and downlink between fixed node devices (donor Evolutionary Node B, donor eNB) and relay node devices (relay eNB) only performs backhaul link communication on some pre-configured fixed subframes (time domain resources), which cannot meet the backhaul link communication requirements of 5G New Radio (5G NR). Summary of the Invention

[0003] This application provides a method for duplex coordination in a relay network and a relay node device. The relay node device can receive messages sent by its parent node device according to a dynamically configured first time domain resource, and send messages to its child node device according to a dynamically configured second time domain resource, thereby meeting the requirements of 5G NR for backhaul link communication.

[0004] In a first aspect, embodiments of this application provide a method for duplex coordination in a relay network, including:

[0005] According to the configuration information, the first node device receives a first message sent by the second node device on the first time domain resource, and sends a second message to the third node device on the second time domain resource.

[0006] The configuration information indicates the first time domain resource and / or the second time domain resource, the second node device is the parent node of the first node device, and the third node device is the child node of the first node device.

[0007] Therefore, in the relay network duplex coordination method of this application embodiment, the first node device can receive messages sent by its parent node device on the first time domain resource and send messages to its child node device on the second time domain resource according to the dynamic configuration information, thereby meeting the 5G NR requirements for backhaul link communication.

[0008] Optionally, in one implementation of the first aspect, the first time domain resource and / or the second time domain resource are downlink time domain resources.

[0009] Optionally, in one implementation of the first aspect, the first time-domain resource and / or the second time-domain resource includes flexible time-slot resources.

[0010] Optionally, in one implementation of the first aspect, the first time-domain resource and the second time-domain resource do not overlap.

[0011] Optionally, in one implementation of the first aspect, the second time-domain resource is part or all of the third time-domain resource, wherein the third time-domain resource is a downlink time-domain resource other than the first time-domain resource.

[0012] Therefore, the first time domain resource can be non-overlapping with the second time domain resource, so that the first node device can simultaneously receive messages sent by its parent node device on the first time domain resource and send messages to its child node device on the second time domain resource.

[0013] Optionally, in one implementation of the first aspect, the first time-domain resource partially or completely overlaps with the second time-domain resource.

[0014] Optionally, in one implementation of the first aspect, the first node device receives a first message sent by the second node device on a first time domain resource according to configuration information, and sends a second message to the third node device on a second time domain resource, including:

[0015] The first node device preferentially receives the first message sent by the second node device on the first time domain resource.

[0016] Therefore, the first time domain resource can partially or completely overlap with the second time domain resource. In this case, the first node device will preferentially receive messages sent by its parent node device on the first time domain resource, thereby allowing the first node device to prioritize the scheduling of resources for message reception.

[0017] Optionally, in one implementation of the first aspect, the first node device receives a first message sent by the second node device on a first time domain resource according to configuration information, and sends a second message to the third node device on a second time domain resource, including:

[0018] The first node device prioritizes sending the second message to the third node device in the non-overlapping region of the second time domain resource.

[0019] Therefore, the first time domain resource may partially or completely overlap with the second time domain resource. In this case, the first node device prioritizes sending messages to its child node devices in the non-overlapping area of ​​the second time domain resource. Thus, the first node device can prioritize scheduling downlink time domain resources in the non-overlapping area for message sending.

[0020] Optionally, in one implementation of the first aspect, the first node device receives a first message sent by the second node device on a first time domain resource according to configuration information, and sends a second message to the third node device on a second time domain resource, including:

[0021] If the Discontinuous Reception (DRX) configuration information indicates that the first message sent by the second node device does not need to be received on the first time domain resource, the first node device sends the second message to the third node device on the second time domain resource. The DRX configuration information indicates that the first node device receives messages during the inactive timer runtime or the continuous timer runtime, and refuses to receive messages after the inactive timer expires or the continuous timer expires.

[0022] Optionally, in one implementation of the first aspect, the configuration information includes first configuration information and second configuration information, wherein the first configuration information indicates the first time domain resource and the second configuration information indicates the second time domain resource.

[0023] Optionally, in one implementation of the first aspect, if the first message and / or the second message are downlink reference signals or system messages,

[0024] According to the configuration information, the first node device receives a first message sent by the second node device on the first time domain resource, and sends a second message to the third node device on the second time domain resource, including:

[0025] The first node device receives the first message sent by the second node device in the non-overlapping area of ​​the first time domain resource and the second time domain resource, and / or sends the second message to the third node device in the non-overlapping area of ​​the second time domain resource and the first time domain resource.

[0026] Therefore, the first node device receives downlink reference signals or system messages sent by its parent node device in the non-overlapping area of ​​the first time domain resource and the second time domain resource, and sends downlink reference signals or system messages to its child node device in the non-overlapping area of ​​the second time domain resource and the first time domain resource, thereby ensuring reliable transmission of downlink reference signals or system messages.

[0027] Optionally, in one implementation of the first aspect, the method further includes:

[0028] The first node device sends the first time domain resource, and / or the second time domain resource, and / or the overlapping area of ​​the first time domain resource and the second time domain resource, and / or the non-overlapping area of ​​the first time domain resource and the second time domain resource to the third node device.

[0029] Therefore, the first node device sends time-domain resources to its child node devices, thereby enabling the child node devices to determine the time-domain resources for receiving messages sent by the first node device, thus ensuring reliable transmission.

[0030] Optionally, in one implementation of the first aspect, the first node device receives a first message sent by the second node device on a first time domain resource according to configuration information, and sends a second message to the third node device on a second time domain resource, including:

[0031] The first node device, based on configuration information and DRX configuration information, receives the first message sent by the second node device on the first time domain resource, and sends the second message to the third node device on the second time domain resource, wherein...

[0032] The first node device ignores the DRX configuration information that instructs the first node device to receive the first message on downlink time domain resources other than the first time domain resource, and refuses to receive the first message;

[0033] The DRX configuration information instructs the first node device to receive messages during the inactive timer's runtime or the continuous timer's runtime, and to refuse to receive messages after the inactive timer expires or the continuous timer expires.

[0034] Therefore, when the first node device receives a message, it prioritizes the time-domain resources indicated by the configuration information and then considers the DRX configuration information. In this way, when the configuration information and the DRX configuration information conflict, the conflict can be resolved.

[0035] Optionally, in one implementation of the first aspect, before the first node device receives the first message sent by the second node device on the first time domain resource according to the configuration information, and before sending the second message to the third node device on the second time domain resource, the method further includes:

[0036] The first node device receives the configuration information sent by the fourth node device, which is either the second node device, an anchor node device, an access network device, or a core network device.

[0037] Optionally, in one implementation of the first aspect, the first node device receives the configuration information sent by the fourth node device, including:

[0038] The first node device receives the configuration information sent by the fourth node device via Radio Resource Control (RRC), Media Access Control Control Element (MAC CE), or Downlink Control Information (DCI).

[0039] Optionally, in one implementation of the first aspect, the method further includes:

[0040] The first node device communicates with the fifth node device in the fifth time domain resource via device-to-device (D2D) communication.

[0041] The fifth time domain resource is configured for the sixth node device, which is either the second node device, the anchor node device, the access network device, or the core network device.

[0042] Secondly, embodiments of this application provide a method for duplex coordination in a relay network, including:

[0043] The first node device receives time-domain resource information sent by the second node device, wherein the second node device is the parent node of the first node device;

[0044] The first node device receives the message sent by the second node device based on the time domain resource information.

[0045] Therefore, in the relay network duplex coordination method of this application embodiment, the first node device receives time domain resource information sent by its parent node device, thereby the first node device can determine the time domain resources for receiving the message sent by its parent node device, and thus ensure reliable transmission.

[0046] Optionally, in one implementation of the second aspect, the time-domain resource information includes a first time-domain resource, and / or a second time-domain resource, and / or the overlapping region of the first time-domain resource and the second time-domain resource, and / or the non-overlapping region of the first time-domain resource and the second time-domain resource, wherein...

[0047] The second node device receives messages sent by the third node device through the first time domain resource, and sends messages to the first node device through the second time domain resource. The third node device is the parent node of the second node device.

[0048] Optionally, in one implementation of the second aspect, if the time-domain resource information includes the first time-domain resource,

[0049] The first node device receives messages sent by the second node device based on the time-domain resource information, including:

[0050] The first node device receives messages sent by the second node device on time domain resources other than the first time domain resource.

[0051] Optionally, in one implementation of the second aspect, if the time-domain resource information includes the first time-domain resource, and / or the second time-domain resource,

[0052] The first node device receives messages sent by the second node device based on the time-domain resource information, including:

[0053] The first node device receives messages sent by the second node device on the second time domain resource.

[0054] Optionally, in one implementation of the second aspect, if the time-domain resource information includes the first time-domain resource, and / or the second time-domain resource, and / or the overlapping area of ​​the first time-domain resource and the second time-domain resource,

[0055] The first node device receives messages sent by the second node device based on the time-domain resource information, including:

[0056] The first node device preferentially receives messages sent by the second node device on the third time domain resource, wherein the third time domain resource is the time domain resource in the second time domain resource excluding the overlapping area between the first time domain resource and the second time domain resource.

[0057] Optionally, in one implementation of the second aspect, if the time-domain resource information includes the first time-domain resource, and / or the second time-domain resource, and / or the overlapping area of ​​the first time-domain resource and the second time-domain resource, and / or the non-overlapping area of ​​the first time-domain resource and the second time-domain resource,

[0058] The first node device receives messages sent by the second node device based on the time-domain resource information, including:

[0059] The first node device preferentially receives messages sent by the second node device in the non-overlapping area of ​​the first time domain resource and the second time domain resource.

[0060] Thirdly, embodiments of this application provide a relay node device that can execute the method in the first aspect or any optional implementation of the first aspect, which is a module or unit.

[0061] Fourthly, embodiments of this application provide a relay node device that can execute the methods in the second aspect or any optional implementation of the second aspect, as a module or unit.

[0062] Fifthly, a relay node device is provided, comprising a processor, a memory, and a communication interface. The processor is connected to the memory and the communication interface. The memory stores instructions, the processor executes the instructions, and the communication interface communicates with other network elements under the control of the processor. When the processor executes the instructions stored in the memory, the execution causes the processor to perform the methods of the first aspect or any possible implementation thereof.

[0063] Sixthly, a relay node device is provided, comprising a processor, a memory, and a communication interface. The processor is connected to the memory and the communication interface. The memory is used to store instructions, the processor is used to execute the instructions, and the communication interface is used to communicate with other network elements under the control of the processor. When the processor executes the instructions stored in the memory, the execution causes the processor to perform the methods of the second aspect or any possible implementation thereof.

[0064] In a seventh aspect, a computer storage medium is provided, wherein program code is stored therein, the program code being used to instruct a computer to execute instructions of the methods described in the above aspects.

[0065] Eighthly, a computer program product including instructions is provided, which, when run on a computer, causes the computer to perform the methods described in the above aspects. Attached Figure Description

[0066] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of this application.

[0067] Figure 2 This is a schematic flowchart of a method for coordinating duplex in a relay network according to an embodiment of this application.

[0068] Figure 3 This is a schematic diagram showing that the two time-domain resources do not overlap in the embodiments of this application.

[0069] Figure 4 This is a schematic diagram showing the overlap of two time-domain resources in an embodiment of this application.

[0070] Figure 5 This is a schematic flowchart of a method for relay network duplex coordination according to another embodiment of this application.

[0071] Figure 6 This is a schematic block diagram of a relay node device according to an embodiment of this application.

[0072] Figure 7 This is a schematic block diagram of another relay node device according to an embodiment of this application.

[0073] Figure 8 This is a schematic structural diagram of a system chip according to an embodiment of this application.

[0074] Figure 9 A schematic block diagram of a relay network duplex coordination device provided in an embodiment of this application is shown. Detailed Implementation

[0075] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0076] The technical solutions of this application embodiment can be applied to 5G NR communication systems.

[0077] Figure 1 This is a schematic diagram illustrating an application scenario of an embodiment of the present invention.

[0078] like Figure 1 As shown, the communication system 100 may include a core network device 110, anchor node devices 120, relay node devices 130-170, and terminal devices 180-190. A topology network centered on the core network device 110 can be established in this communication system 100. The core network device 110 can establish communication connections with the terminal device 180 through anchor node devices 120, relay node devices 130, 140, and 150, and the core network device 110 can establish communication connections with the terminal device 190 through anchor node devices 120, 160, and 170.

[0079] It should be understood that the embodiments of this application are only illustrated by way of example, using the communication system 100, but the embodiments of this application are not limited thereto. That is to say, the number of relay node devices and the number of terminal devices in the embodiments of this application can be determined according to actual needs.

[0080] Among them, the core network equipment 110 can be a 5G core network (5G Core, 5GC) equipment, such as the Access and Mobility Management Function (AMF), the Session Management Function (SMF), or the User Plane Function (UPF).

[0081] The anchor node device 120 can be a base station or access network device that communicates directly with the core network device 110 via wired connection. The anchor node device 120 can provide communication coverage for a specific geographical area and can communicate with relay node devices or terminal devices (e.g., UEs) located within that coverage area. Optionally, the anchor node device 120 can be a base station (gNB) in a New Radio (NR) system, a radio controller in a Cloud Radio Access Network (CRAN), or a relay station, access point, vehicle-mounted device, wearable device, or network equipment in a future Public Land Mobile Network (PLMN).

[0082] Relay node devices (130-170) can forward data or signaling between anchor node devices and terminal devices. For example, relay node device 130 connects anchor node device 120 and relay node device 140, and is used to forward data or signaling between anchor node device 120 and relay node device 140 (terminal device 180). Relay node devices can provide communication coverage for a specific geographical area and can communicate with other relay node devices or terminal devices located within that coverage area. Optionally, the relay node device can be a base station (gNB) in an NR system, or a relay station, access point, vehicle-mounted equipment, wearable device, or network equipment in a future PLMN evolution, etc.

[0083] Optionally, the communication connection between the relay node device and the anchor node device 120 can be represented by the number of hops. For example, the number of hops between the relay node device 130 and the anchor node device 120 is 1, and the number of hops between the relay node device 150 and the anchor node device 120 is 3.

[0084] Optionally, the upstream device of a relay node device is its parent node, and the next hop is its child node. For example, the parent node of relay node device 140 is relay node device 130, and the child node of relay node device 140 is relay node device 150.

[0085] Optionally, the fewer the hops between a relay node device 120 and the anchor node device 120, the higher its priority. For example, the priority of relay node device 130 is higher than that of relay node device 140. Alternatively, the priority of relay node device 130 may be the same as that of relay node device 160.

[0086] Terminal equipment (180-190) can be mobile or fixed. Optionally, terminal equipment can refer to access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device. Access terminal can be cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal equipment in a 5G NR network, or terminal equipment in a future PLMN evolution, etc.

[0087] Figure 1 An exemplary embodiment shows a core network device, an anchor node device, five relay node devices, and two terminal devices. Optionally, the wireless communication system 100 may include multiple anchor node devices and other numbers of relay node devices, and each relay node device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0088] Optionally, the wireless communication system 100 may also include other network entities such as Session Management Function (SMF), Unified Data Management (UDM), and Authentication Server Function (AUSF), which are not limited in this application embodiment.

[0089] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0090] Figure 2 This is a schematic flowchart of a relay network duplex coordination method 200 according to an embodiment of this application. Method 200 can optionally be applied to... Figure 1 The system shown is not limited to this. Method 200 includes at least some of the following.

[0091] 210. According to the configuration information, the first node device receives a first message sent by the second node device on the first time domain resource, and sends a second message to the third node device on the second time domain resource. The configuration information indicates the first time domain resource and / or the second time domain resource, the second node device is the parent node of the first node device, and the third node device is the child node of the first node device.

[0092] Specifically, the first message can be downlink data, a paging message, a system message, a downlink reference signal, or some control signaling messages. This application embodiment does not limit this.

[0093] Specifically, the second message can be downlink data, a paging message, a system message, a downlink reference signal, or some control signaling messages. This application embodiment does not limit this.

[0094] The first node device can simultaneously receive the first message sent by the second node device on the first time domain resource, and send the second message to the third node device on the second time domain resource.

[0095] The first time domain resource and / or the second time domain resource are downlink time domain resources.

[0096] Optionally, the first time-domain resource and / or the second time-domain resource may include flexible slot resources.

[0097] Optionally, the first time-domain resource and the second time-domain resource do not overlap.

[0098] Optionally, the second time domain resource is part or all of the third time domain resource, wherein the third time domain resource is a downlink time domain resource other than the first time domain resource.

[0099] For example, such as Figure 3 As shown, the first time domain resources and the second time domain resources do not overlap. The second time domain resources are part of the third time domain resources. The first time domain resources and the third time domain resources constitute all the downlink time domain resources.

[0100] Therefore, the first time domain resource can be non-overlapping with the second time domain resource, so that the first node device can simultaneously receive messages sent by its parent node device on the first time domain resource and send messages to its child node device on the second time domain resource.

[0101] Optionally, the first time-domain resource may partially or completely overlap with the second time-domain resource.

[0102] For example, such as Figure 4As shown, the first time-domain resource partially overlaps with the second time-domain resource.

[0103] Specifically, when the first time domain resource and the second time domain resource partially or completely overlap, the first node device preferentially receives the first message sent by the second node device on the first time domain resource.

[0104] Therefore, the first time domain resource can partially or completely overlap with the second time domain resource. In this case, the first node device will preferentially receive messages sent by its parent node device on the first time domain resource, thereby allowing the first node device to prioritize the scheduling of resources for message reception.

[0105] Optionally, while the first node device receives the first message sent by the second node device on the first time domain resource, the third node device may be in a receiving state, for example, the third node device may receive messages sent by a parent node other than the first node device.

[0106] Specifically, when the first time domain resource partially or completely overlaps with the second time domain resource, the first node device prioritizes sending the second message to the third node device in the non-overlapping area of ​​the second time domain resource with the first time domain resource.

[0107] Therefore, the first time domain resource may partially or completely overlap with the second time domain resource. In this case, the first node device prioritizes sending messages to its child node devices in the non-overlapping area of ​​the second time domain resource. Thus, the first node device can prioritize scheduling downlink time domain resources in the non-overlapping area for message sending.

[0108] Optionally, if the DRX configuration information indicates that the first message sent by the second node device is not required to be received on the first time domain resource, the first node device sends the second message to the third node device on the second time domain resource.

[0109] Optionally, when the first time-domain resource and the second time-domain resource partially or completely overlap, the configuration information includes first configuration information and second configuration information, wherein the first configuration information indicates the first time-domain resource and the second configuration information indicates the second time-domain resource.

[0110] Optionally, the first time domain resource and the second time domain resource partially or completely overlap. If the first message and / or the second message is a downlink reference signal or a system message, the first node device receives the first message sent by the second node device in the non-overlapping area of ​​the first time domain resource and the second time domain resource, and / or sends the second message to the third node device in the non-overlapping area of ​​the second time domain resource and the first time domain resource.

[0111] Therefore, the first node device receives downlink reference signals or system messages sent by its parent node device in the non-overlapping area of ​​the first time domain resource and the second time domain resource, and sends downlink reference signals or system messages to its child node device in the non-overlapping area of ​​the second time domain resource and the first time domain resource, thereby ensuring reliable transmission of downlink reference signals or system messages.

[0112] Optionally, the first node device sends the first time domain resource, and / or the second time domain resource, and / or the overlapping area of ​​the first time domain resource and the second time domain resource, and / or the non-overlapping area of ​​the first time domain resource and the second time domain resource to the third node device.

[0113] If the first node device sends the first time domain resource to the third node device, the third node device receives the message sent by the first node device on a time domain resource other than the first time domain resource.

[0114] If the first node device sends the first time domain resource to the third node device, and / or the second time domain resource, the third node device receives the message sent by the first node device on the second time domain resource.

[0115] If the first node device sends the first time domain resource, and / or the second time domain resource, and / or the overlapping area of ​​the first time domain resource and the second time domain resource to the third node device, the third node device shall preferentially receive the message sent by the first node device on the third time domain resource, wherein the third time domain resource is the time domain resource of the second time domain resource excluding the overlapping area of ​​the first time domain resource and the second time domain resource.

[0116] If the first node device sends the first time domain resource, and / or the second time domain resource, and / or the overlapping area of ​​the first time domain resource and the second time domain resource, and / or the non-overlapping area of ​​the first time domain resource and the second time domain resource to the third node device, the third node device shall preferentially receive the message sent by the first node device in the non-overlapping area of ​​the second time domain resource and the first time domain resource.

[0117] Therefore, the first node device sends time-domain resources to its child node devices, thereby enabling the child node devices to determine the time-domain resources for receiving messages sent by the first node device, thus ensuring reliable transmission.

[0118] Optionally, the first node device receives the first message sent by the second node device on the first time domain resource according to the configuration information and DRX configuration information, and sends the second message to the third node device on the second time domain resource.

[0119] The first node device ignores the DRX configuration information that instructs the first node device to receive the first message on downlink time domain resources other than the first time domain resource, and refuses to receive the first message.

[0120] The DRX configuration information instructs the first node device to receive messages during the inactivity timer or the onduration timer, and to refuse to receive messages after the inactivity timer or the onduration timer expires.

[0121] Specifically, if the first node device determines, based on the DRX configuration information, that it needs to receive the first message from the second node device on the first time domain resource, and the configuration information indicates that there is no time domain resource for the first message, the first node device refuses to receive the first message.

[0122] Optionally, this configuration information has a higher priority than the DRX configuration information.

[0123] Therefore, when the first node device receives a message, it prioritizes the time-domain resources indicated by the configuration information and then considers the DRX configuration information. In this way, when the configuration information and the DRX configuration information conflict, the conflict can be resolved.

[0124] Optionally, the first node device receives the configuration information sent by the fourth node device, which is the second node device, or an anchor node device, or an access network device, or a core network device.

[0125] Optionally, the first node device receives the configuration information sent by the fourth node device via RRC, MAC CE, or DCI.

[0126] Optionally, the method 200 further includes:

[0127] The first node device performs D2D communication with the fifth node device on the fifth time domain resource, wherein the fifth time domain resource is configured for the sixth node device, which is the second node device, or an anchor node device, or an access network device, or a core network device.

[0128] The first node device and the fifth node device are node devices of the same priority.

[0129] Optionally, the fifth time-domain resource can be a side-row time-domain resource.

[0130] Therefore, in the relay network duplex coordination method of this application embodiment, the first node device can receive messages sent by its parent node device on the first time domain resource and send messages to its child node device on the second time domain resource according to the dynamic configuration information, thereby meeting the 5G NR requirements for backhaul link communication.

[0131] Figure 5 This is a schematic flowchart of a relay network duplex coordination method 300 according to an embodiment of this application. Method 300 can optionally be applied to... Figure 1 The system shown is not limited to this. Method 300 includes at least some of the following.

[0132] 310, the first node device receives time-domain resource information sent by the second node device, wherein...

[0133] The second node device is the parent node of the first node device.

[0134] 320. The first node device receives the message sent by the second node device based on the time domain resource information.

[0135] Optionally, the time-domain resource information includes a first time-domain resource, and / or a second time-domain resource, and / or the overlapping area of ​​the first time-domain resource and the second time-domain resource, and / or the non-overlapping area of ​​the first time-domain resource and the second time-domain resource, wherein,

[0136] The second node device receives messages sent by the third node device through the first time domain resource, and sends messages to the first node device through the second time domain resource. The third node device is the parent node of the second node device.

[0137] Optionally, if the time-domain resource information includes the first time-domain resource,

[0138] The first node device receives messages sent by the second node device based on the time-domain resource information, including:

[0139] The first node device receives messages sent by the second node device on time domain resources other than the first time domain resource.

[0140] Optionally, if the time-domain resource information includes the first time-domain resource, and / or the second time-domain resource,

[0141] The first node device receives messages sent by the second node device based on the time-domain resource information, including:

[0142] The first node device receives messages sent by the second node device on the second time domain resource.

[0143] Optionally, if the time-domain resource information includes the first time-domain resource, and / or the second time-domain resource, and / or the overlapping area of ​​the first time-domain resource and the second time-domain resource,

[0144] The first node device receives messages sent by the second node device based on the time-domain resource information, including:

[0145] The first node device preferentially receives messages sent by the second node device on the third time domain resource, wherein the third time domain resource is the time domain resource in the second time domain resource excluding the overlapping area between the first time domain resource and the second time domain resource.

[0146] Optionally, if the time-domain resource information includes the first time-domain resource, and / or the second time-domain resource, and / or the overlapping area of ​​the first time-domain resource and the second time-domain resource, and / or the non-overlapping area of ​​the first time-domain resource and the second time-domain resource,

[0147] The first node device receives messages sent by the second node device based on the time-domain resource information, including:

[0148] The first node device preferentially receives messages sent by the second node device in the non-overlapping area of ​​the first time domain resource and the second time domain resource.

[0149] It should be understood that the steps in the relay network duplex coordination method 300 can be referred to the relevant descriptions of the corresponding steps in the relay network duplex coordination method 200. For the sake of brevity, they will not be repeated here.

[0150] Therefore, in the relay network duplex coordination method of this application embodiment, the first node device receives time domain resource information sent by its parent node device, thereby the first node device can determine the time domain resources for receiving the message sent by its parent node device, and thus ensure reliable transmission.

[0151] Figure 6 This is a schematic block diagram of a relay node device 400 according to an embodiment of this application. Figure 6 As shown, the relay node device 400 includes a communication unit 410; wherein, the communication unit 410 is used to receive a first message sent by a second node device on a first time domain resource, and to send a second message to a third node device on a second time domain resource, according to configuration information, wherein the configuration information indicates the first time domain resource and / or the second time domain resource, the second node device is the parent node of the relay node device, and the third node device is the child node of the relay node device.

[0152] It should be understood that the relay node device 400 can correspond to the first node device in method 200 and can implement the corresponding operations implemented by the first node device in method 200. For the sake of brevity, it will not be described in detail here.

[0153] Figure 7 This is a schematic block diagram of a relay node device 500 according to an embodiment of this application. Figure 7 As shown, the relay node device 500 includes a communication unit 510; wherein, the communication unit 510 is used to receive time-domain resource information sent by a second node device, wherein the second node device is the parent node of the relay node device; the communication unit 510 is also used to receive messages sent by the second node device according to the time-domain resource information.

[0154] It should be understood that the relay node device 500 can correspond to the first node device in method 300 and can implement the corresponding operations implemented by the first node device in method 300. For the sake of brevity, it will not be described in detail here.

[0155] Figure 8 This is a schematic structural diagram of a system chip 600 according to an embodiment of this application. Figure 8 The system chip 600 includes an input interface 601, an output interface 602, a processor 603, and a memory 604, which are connected by an internal communication connection line. The processor 603 is used to execute the code in the memory 604.

[0156] Optionally, when the code is executed, the processor 603 implements the method executed by the first node device in method 200. For the sake of brevity, further details are omitted here.

[0157] Optionally, when the code is executed, the processor 603 implements the method executed by the first node device in method 300. For the sake of brevity, further details are omitted here.

[0158] Figure 9 This is a schematic block diagram of a communication device 700 according to an embodiment of this application. Figure 9 As shown, the communication device 700 includes a processor 710 and a memory 720. The memory 720 can store program code, and the processor 710 can execute the program code stored in the memory 720.

[0159] Optionally, such as Figure 9 As shown, the communication device 700 may include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with the outside world.

[0160] Optionally, the processor 710 can call the program code stored in the memory 720 to execute the corresponding operation of the first node device in method 200. For the sake of brevity, it will not be described in detail here.

[0161] Optionally, the processor 710 can call the program code stored in the memory 720 to execute the corresponding operation of the first node device in method 300. For the sake of brevity, this will not be described in detail here.

[0162] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0163] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

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

[0165] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0166] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0167] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0168] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0169] If the aforementioned functions are implemented as software functional 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 this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0170] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for duplex coordination in a relay network, characterized in that, include: According to the configuration information, the first node device receives a first message sent by the second node device on the first time domain resource, and sends a second message to the third node device on the second time domain resource. The configuration information indicates the first time domain resource and the second time domain resource, the second node device is the parent node of the first node device, and the third node device is the child node of the first node device; The first time-domain resource and the second time-domain resource partially or completely overlap, and the first time-domain resource and / or the second time-domain resource include flexible time-slot resources; The first node device, according to configuration information, receives a first message sent by the second node device on a first time domain resource, and sends a second message to the third node device on a second time domain resource, including: The first node device sends the second message to the third node device in a non-overlapping region of the second time domain resource.

2. The method according to claim 1, characterized in that, The first time-domain resource and / or the second time-domain resource are downlink time-domain resources.

3. The method according to claim 1, characterized in that, The first node device, according to configuration information, receives a first message sent by the second node device on a first time domain resource, and sends a second message to the third node device on a second time domain resource, including: If the non-continuous reception DRX configuration information indicates that it is not necessary to receive the first message sent by the second node device on the first time domain resource, the first node device sends the second message to the third node device on the second time domain resource. The DRX configuration information indicates that the first node device receives the message during the inactive timer runtime or the continuous timer runtime, and refuses to receive the message after the inactive timer expires or the continuous timer expires.

4. The method according to any one of claims 1 to 3, characterized in that, The configuration information includes first configuration information and second configuration information, wherein the first configuration information indicates the first time-domain resource and the second configuration information indicates the second time-domain resource.

5. The method according to any one of claims 1 to 3, characterized in that, If the first message and / or the second message are downlink reference signals or system messages The first node device, according to configuration information, receives a first message sent by the second node device on a first time domain resource, and sends a second message to the third node device on a second time domain resource, including: The first node device receives the first message sent by the second node device in a non-overlapping region of the first time domain resource and the second time domain resource.

6. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first node device sends the first time domain resource, and / or the second time domain resource, and / or the overlapping area of ​​the first time domain resource and the second time domain resource, and / or the non-overlapping area of ​​the first time domain resource and the second time domain resource to the third node device.

7. The method according to any one of claims 1 to 3, characterized in that, The first node device, according to configuration information, receives a first message sent by the second node device on a first time domain resource, and sends a second message to the third node device on a second time domain resource, including: The first node device, based on the configuration information and DRX configuration information, receives the first message sent by the second node device on the first time domain resource, and sends the second message to the third node device on the second time domain resource, wherein... The first node device ignores the DRX configuration information that instructs the first node device to receive the first message on downlink time domain resources other than the first time domain resource, and refuses to receive the first message; The DRX configuration information instructs the first node device to receive messages during the inactive timer's runtime or the continuous timer's runtime, and to refuse to receive messages after the inactive timer expires or the continuous timer expires.

8. The method according to any one of claims 1 to 3, characterized in that, Before the first node device receives the first message sent by the second node device on the first time domain resource according to the configuration information, and before sending the second message to the third node device on the second time domain resource, the method further includes: The first node device receives the configuration information sent by the fourth node device, which is either the second node device, an anchor node device, an access network device, or a core network device.

9. The method according to claim 8, characterized in that, The first node device receives the configuration information sent by the fourth node device, including: The first node device receives the configuration information sent by the fourth node device through Radio Resource Control (RRC), Media Access Control (MAC) CE, or Downlink Control Information (DCI).

10. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first node device performs end-to-end D2D communication with the fifth node device on the fifth time domain resources, wherein, The fifth time domain resource is configured for the sixth node device, which is either the second node device, an anchor node device, an access network device, or a core network device.

11. A method for duplex coordination in a relay network, characterized in that, include: The first node device receives time-domain resource information sent by the second node device, wherein the second node device is the parent node of the first node device; The first node device receives the message sent by the second node device based on the time-domain resource information; The time-domain resource information includes a first time-domain resource and a second time-domain resource, and / or, the overlapping region of the first time-domain resource and the second time-domain resource, and / or, the non-overlapping region of the first time-domain resource and the second time-domain resource. The second node device receives messages sent by the third node device through the first time domain resource, and sends messages to the first node device through the second time domain resource, wherein the third node device is the parent node of the second node device; The first node device receives a message sent by the second node device based on the time-domain resource information, including: The first node device receives the message sent by the second node device in the non-overlapping region of the first time domain resource and the second time domain resource in the second time domain resource.

12. A relay node device, characterized in that, include: The communication unit is configured to receive a first message sent by a second node device on a first time domain resource, and to send a second message to a third node device on a second time domain resource, according to configuration information. The configuration information indicates the first time domain resource and the second time domain resource, the second node device is the parent node of the relay node device, and the third node device is the child node of the relay node device; The first time-domain resource and the second time-domain resource partially or completely overlap, and the first time-domain resource and / or the second time-domain resource include flexible time-slot resources; The communication unit is specifically used for: The second message is sent to the third node device in the non-overlapping region of the second time domain resource with the first time domain resource.

13. The relay node device according to claim 12, characterized in that, The first time-domain resource and / or the second time-domain resource are downlink time-domain resources.

14. The relay node device according to claim 12, characterized in that, The communication unit is specifically used for: If the non-continuous reception DRX configuration information indicates that it is not necessary to receive the first message sent by the second node device on the first time domain resource, the relay node device sends the second message to the third node device on the second time domain resource. The DRX configuration information indicates that the relay node device receives messages during the inactive timer runtime or the continuous timer runtime, and refuses to receive messages after the inactive timer expires or the continuous timer expires.

15. The relay node device according to any one of claims 12 to 14, characterized in that, The configuration information includes first configuration information and second configuration information, wherein the first configuration information indicates the first time-domain resource and the second configuration information indicates the second time-domain resource.

16. The relay node device according to any one of claims 12 to 14, characterized in that, If the first message and / or the second message are downlink reference signals or system messages The communication unit is specifically used for: The first message sent by the second node device is received in a non-overlapping region of the first time domain resource and the second time domain resource.

17. The relay node device according to any one of claims 12 to 14, characterized in that, The communication unit is further configured to send the first time-domain resource, and / or the second time-domain resource, and / or the overlapping area of ​​the first time-domain resource and the second time-domain resource, and / or the non-overlapping area of ​​the first time-domain resource and the second time-domain resource to the third node device.

18. The relay node device according to any one of claims 12 to 14, characterized in that, The communication unit is specifically used for: Based on the configuration information and DRX configuration information, the system receives the first message sent by the second node device on the first time domain resource, and sends the second message to the third node device on the second time domain resource, wherein... The relay node device ignores the DRX configuration information that instructs the relay node device to receive the first message on downlink time domain resources other than the first time domain resource, and refuses to receive the first message; The DRX configuration information instructs the relay node device to receive messages during the inactive timer's runtime or the continuous timer's runtime, and to refuse to receive messages after the inactive timer expires or the continuous timer expires.

19. The relay node device according to any one of claims 12 to 14, characterized in that, Before the communication unit receives the first message sent by the second node device on the first time domain resource according to the configuration information, and sends the second message to the third node device on the second time domain resource, the communication unit is further configured to: The configuration information is received from a fourth node device, which is either the second node device, an anchor node device, an access network device, or a core network device.

20. The relay node device according to claim 19, characterized in that, The communication unit is specifically used for: The configuration information is received by the fourth node device via Radio Resource Control (RRC), Media Access Control (MAC) CE, or Downlink Control Information (DCI).

21. The relay node device according to any one of claims 12 to 14, characterized in that, The communication unit is also used for end-to-end D2D communication with the fifth node device on the fifth time domain resources, wherein... The fifth time domain resource is configured for the sixth node device, which is either the second node device, an anchor node device, an access network device, or a core network device.

22. A relay node device, characterized in that, include: A communication unit is used to receive time-domain resource information sent by a second node device, wherein the second node device is the parent node of the relay node device; The communication unit is further configured to receive messages sent by the second node device based on the time-domain resource information; The time-domain resource information includes a first time-domain resource and a second time-domain resource, and / or, the overlapping region of the first time-domain resource and the second time-domain resource, and / or, the non-overlapping region of the first time-domain resource and the second time-domain resource. The second node device receives messages sent by the third node device through the first time domain resource, and sends messages to the relay node device through the second time domain resource, wherein the third node device is the parent node of the second node device; Specifically, the communication unit is used for: The message sent by the second node device is received in the non-overlapping area of ​​the first time domain resource and the second time domain resource in the second time domain resource.

23. A relay node device, comprising: processor; Memory is used to store programs that can be executed by the processor; When the processor executes the program, it performs the method according to any one of claims 1 to 10.

24. A relay node device, comprising: processor; Memory is used to store programs that can be executed by the processor; When the processor executes the program, it performs the method according to claim 11.

25. A computer storage medium having stored thereon computer-executable instructions which, when executed by a processor, implement the steps of the method according to any one of claims 1 to 10, or the steps of the method according to claim 11.

Images