Transfer device and transmission method thereof, network equipment, and communication system

Abstract

In some embodiments of the present invention, a forwarder and a transmission method thereof, a network device, and a communication system are provided, which include: a forwarder receiving control information from a network device over a control link, the forwarder supporting uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and the forwarder performing forwarding on a backhaul link and / or an access link based on the control information.

Description

[Technical Field]

[0001] The present invention relates to the field of communications. [Background technology]

[0002] Compared with traditional 3G and 4G systems, 5G systems can provide larger bandwidth and higher data rates, and can support more types of devices and vertical businesses (services / businesses). Therefore, the deployment frequency of 5G systems is usually much higher than that of 3G and 4G systems. For example, 5G systems can be deployed in the millimeter wave band.

[0003] However, the higher the carrier frequency, the more severe the fading that the signal experiences during transmission. Therefore, in the practical deployment of 5G systems, how to better enhance cell coverage has become a problem to be solved, especially in the millimeter wave band.

[0004] It should be noted that the introduction of the above background art is intended to clearly and completely explain the technical solutions of the present invention and to facilitate understanding by those skilled in the art, and these technical solutions described in the background art of the present invention should not be construed as being known to those skilled in the art. Summary of the Invention [Problem to be solved by the invention]

[0005] In order to better solve the coverage problem of cellular mobile communication systems in actual deployments, adopting an RF relay / repeater to amplify and forward communication signals between terminal equipment and network equipment is a commonly used deployment method. RF relays are widely applied in the actual deployment of 3G and 4G systems. Generally speaking, an RF relay is a device that amplifies and forwards round-trip signals between network equipment and terminal equipment in the RF domain (range).

[0006] The inventors have discovered that adopting RF forwarders to enhance coverage is one viable solution to the coverage issues faced by 5G systems during deployment. However, conventional forwarders lack the ability to communicate with network devices. Therefore, while such forwarders can help enhance signal strength when installed in 5G systems, they are not flexible enough to adapt to complex environmental changes and cannot achieve the same benefits as deploying similar RF forwarders in 3G or 4G systems.

[0007] In view of at least one of the above problems, embodiments of the present invention provide a forwarder and a transmission method thereof, a network device, and a communication system, in which the forwarder has the ability to communicate with the network device, and can better enhance signal coverage under the configuration of the network and adapt to environmental changes, thereby improving the transmission efficiency of the entire network. [Means for solving the problem]

[0008] According to one aspect of an embodiment of the present invention, there is provided a transmission method for a forwarder, the method comprising: a forwarder receiving control information from a network device over a control link, the forwarder supporting uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and The forwarder may perform forwarding on a backhaul link and / or an access link based on the control information.

[0009] According to another aspect of an embodiment of the present invention, there is provided a forwarder, comprising: a communication unit that receives control information from a network device over a control link, the forwarder supporting uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and The control information includes a forwarding unit that performs forwarding on a backhaul link and / or an access link based on the control information.

[0010] According to another aspect of an embodiment of the present invention, there is provided a method for controlling a forwarder, the method comprising: The network equipment transmits control information over a control link to a forwarder, the forwarder supporting uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and The network device receives or transmits a transport signal on a backhaul link.

[0011] According to yet another aspect of an embodiment of the present invention, there is provided a network device, comprising: a communication unit that transmits control information over a control link to a forwarder, the forwarder supporting uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and It includes a transceiver unit that receives or transmits transport signals over a backhaul link.

[0012] According to another aspect of an embodiment of the present invention, there is provided a communication system, comprising: a network device that transmits control information to the forwarder over a control link; and and a forwarder that receives the control information from the network device, the forwarder supporting uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing waveform, and forwarding on a backhaul link and / or an access link based on the control information. [Effects of the Invention]

[0013] The advantageous effects of the embodiment of the present invention at least include the following: a forwarder receives control information from a network device through a control link, and the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform, so that the network device can configure the forwarding of the forwarder based on the network conditions, thereby better enhancing signal coverage and adapting to changes in the environment and main business (services / traffic) within the cell, thereby improving the transmission efficiency of the entire network.

[0014] The following description and reference to the drawings disclose in detail particular embodiments of the present invention, illustrating ways in which the principles of the present invention may be employed, but the scope of the present invention is not limited thereto, and various changes, modifications, and alternatives may be included within the scope of the appended claims.

[0015] Additionally, features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, may be combined with features in the other embodiments, or may be substituted for features in the other embodiments.

[0016] It should be noted that when used in this specification, terms such as "comprise / have" refer to the presence of a feature, element, step, or assembly, but do not exclude the presence or addition of one or more other features, elements, steps, or assemblies. [Brief explanation of the drawings]

[0017] Elements and features described in one drawing or one embodiment of an embodiment of the invention may be combined with elements and features shown in one or more other drawings or embodiments, and in the drawings, like reference numerals are used to indicate corresponding parts in several drawings and to indicate corresponding parts used in several embodiments.

[0018] The included drawings are used to provide a further understanding of the embodiments of the present invention, and these drawings constitute a part of this specification, illustrate embodiments of the present invention, and together with the written description, serve to explain the principles of the present invention. Also, it is apparent that the drawings described below are only for illustrating some embodiments of the present invention, and those skilled in the art can derive other drawings based on these drawings without any creative effort. [Figure 1] FIG. 1 illustrates an application scenario according to an embodiment of the present invention. [Figure 2] FIG. 1 is a diagram showing NCR in an embodiment of the present invention. [Figure 3] FIG. 10 is a diagram illustrating a transmission method of a forwarder in an embodiment of the present invention. [Figure 4] FIG. 2 illustrates a forwarder in accordance with an embodiment of the present invention. [Figure 5] FIG. 10 is a diagram illustrating a method for controlling a transfer device in an embodiment of the present invention. [Figure 6] FIG. 1 illustrates a network device according to an embodiment of the present invention. [Figure 7] 1 is a diagram illustrating an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0019] The foregoing and other features of the present invention will become more apparent from a consideration of the accompanying drawings and the following description. While the specification and drawings disclose particular embodiments of the present invention, they illustrate only some of the embodiments which may employ the principles of the present invention, and it is to be understood that the present invention is not limited to the described embodiments, but rather includes all modifications, variations, and alternatives which fall within the scope of the appended claims.

[0020] In embodiments of the present invention, the term "communication network" or "wireless communication network" may refer to a network conforming to any communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.

[0021] Additionally, communications between devices in a communications system may be performed according to any level of communications protocol, including, but not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, New Radio (NR), and / or other conventional or future-developed communications protocols.

[0022] In an embodiment of the present invention, the term "network equipment" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services to the terminal device. The network equipment may include, but is not limited to, a "node" and / or a "donor" in the IAB architecture, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a network gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0023] The base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a 5G base station (gNB), etc., and may further include a Remote Radio Head (RRH), a Remote Radio Unit (RRU), a relay, or a low-power node (e.g., femto, pico, etc.). The term "base station" may include some or all of these functions, and each base station can provide communication coverage for a specific geographical area. For example, a 5G base station gNB may include one gNB CU and one or more gNB DUs, where a CU / DU is a logical node of the gNB that has some of the functions of the gNB. The term "cell" may refer to a base station and / or the area it covers, depending on the context in which the term is used.

[0024] In the embodiments of the present invention, the term "user equipment" (UE) or "terminal equipment" (TE) refers to a device that accesses a communication network and receives services from the network, for example, via network equipment. The user equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc. For example, it is a terminal equipment served by an IAB node or an IAB donor under the IAB architecture.

[0025] Among these, user equipment may include, but is not limited to, cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, mobile devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, etc.

[0026] Furthermore, for example, in a scenario such as the Internet of Things (IoT), the user equipment may also be a monitoring or measuring device or apparatus, for example, including but not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, etc.

[0027] Furthermore, the term "network side" or "network equipment side" refers to the network side, or may be a base station, and may include one or more network equipment as described above. The term "user side" or "terminal side" or "terminal equipment side" refers to the user or terminal side, or may be a UE, and may include one or more terminal equipment as described above.

[0028] To enhance coverage, 3GPP Rel-17 research introduces an RF repeater to forward transmissions between terminal equipment (UE) and network equipment (base station). As for the network equipment and terminal equipment, the RF repeater introduced in Rel-17 is transparent, i.e., the network equipment and terminal equipment are unaware of the existence of the RF repeater.

[0029] 1 is a diagram illustrating an application scenario according to an embodiment of the present invention. As shown in FIG. 1, for convenience of explanation, one network device (e.g., a 5G base station gNB) 101, one repeater 102, and one terminal device (e.g., a UE) 103 are used as an example, but the present invention is not limited thereto.

[0030] As shown in Fig. 1, a terminal device 103 establishes a connection with and communicates with a network device 101. In order to improve communication quality, channels / signals transmitted between the terminal device 103 and the network device 101 are forwarded via a forwarder 102. The interaction of channels / signals between the network device 101, the terminal device 103 and the forwarder 102 adopts a beam-based transmission / reception method.

[0031] As shown in FIG. 1, the network equipment 101 may have a cell / carrier, and the network equipment 101, the forwarder 102 and the terminal equipment 103 can forward / communicate in the cell, but the present invention is not limited thereto, for example, the network equipment 101 may further have other cells / carriers.

[0032] In an embodiment of the present invention, existing or future services may be transmitted between a network device and a terminal device, including, but not limited to, eMBB, mMTC, URLLC, and V2X communication.

[0033] Since the conventional forwarder does not have the ability to communicate with the network equipment, the conventional forwarder can help strengthen the signal strength, but is not flexible enough to respond to complex environmental changes, so the overall network throughput will be reduced. In order to make the forwarding of the forwarder more flexible and adapt to the characteristics of the 5G network, the network equipment needs to be able to support the forwarder and set the forwarding of the forwarder based on the network situation.

[0034] To enhance NR coverage, 3GPP Rel-18 proposes a network-controlled repeater (NCR) scheme to forward signals between network equipment and terminal equipment. The NCR can directly communicate with network equipment via a control link to support NCR forwarding operations.

[0035] 2 is a diagram illustrating an NCR in an embodiment of the present invention. As shown in FIG. 2, the NCR 202 is configured between a network device 201 and a terminal device 203. The NCR 202 may include two modules / components: a forwarder mobile terminal (NCR-MT) and a forwarder forwarding module (NCR-Fwd). The NCR-Fwd may also be referred to as the NCR routing unit (NCR-RU). The NCR-MT is used to communicate with the network device, and the NCR-Fwd is used to forward signals back and forth between the network device and the terminal device.

[0036] As shown in Figure 2, the NCR in this embodiment may have three links: a control link (C-link), a backhaul link (BH link) for forwarding, and an access link (AC link). The C-link is used for communication between the NCR and the network equipment. The BH link is used by the forwarder to receive forwarding signals from the network equipment or forward signals from the terminal equipment to the network equipment. The AC link is used by the forwarder to forward signals from the network equipment to the terminal equipment or receive forwarding signals from the terminal equipment.

[0037] Therefore, although the NCR-MT in the embodiment of the present invention directly communicates with the network device via the control link, there is still no solution for the terminal capabilities and characteristics that the NCR-MT should have in order to communicate with the network device. In order for the NCR to receive control information from the network device and forward communications between the terminal device and the network device based on the control information, basic user features, terminal capabilities, and required settings must be supported by the NCR-MT.

[0038] Various implementations of the embodiments of the present invention will be described below in conjunction with the drawings, which are merely examples and are not intended to limit the present invention.

[0039] In an embodiment of the present invention, a forwarder can communicate with a network device, receive a communication channel / signal transmitted by the network device, and demodulate / decode the channel / signal, thereby obtaining information transmitted by the network device to the forwarder. Hereinafter, this signal processing process is referred to as "communication." The forwarder can also forward a channel / signal transmitted between the network device and a terminal device, and the forwarder does not demodulate / decode the channel / signal, but may perform processing such as amplification. Hereinafter, this signal processing process is referred to as "forwarding." "Communication" and "forwarding" are collectively referred to as "transmission." Note that these terms are used for convenience of explanation only and do not limit the present invention.

[0040] For convenience, a channel / signal for direct communication between a network device and a forwarder or between a third device (e.g., a terminal device) and a forwarder may be referred to as a communication signal, and when transmitting a communication signal, the forwarder needs to perform encoding and / or modulation, and when receiving a communication signal, the forwarder needs to perform decoding and / or demodulation. Also, a channel / signal forwarded via a forwarder may be referred to as a transport signal, and the forwarder may perform signal processing such as amplification on the transport signal, but does not perform decoding and / or demodulation.

[0041] In an embodiment of the present invention, the forwarder may further be referred to as a live broadcast station, an RF forwarder, a repeater, an RF repeater, or a live broadcast station node, a forwarder node, a repeater node, or an intelligent live broadcast station, an intelligent forwarder, an intelligent repeater, an intelligent live broadcast step node, an intelligent forwarder node, an intelligent repeater node, etc., but the present invention is not limited thereto.

[0042] In an embodiment of the present invention, the network equipment may be an equipment of a serving cell of a terminal equipment, an equipment of a cell in which a forwarder is located, an equipment of a serving cell of a forwarder, or a parent node of a forwarder, but the present invention does not limit the name of the forwarder, and all equipment that can realize the above-mentioned functions is included in the scope of the forwarder of the present invention.

[0043] The following describes in more detail the embodiments of the present invention.

[0044] <Example of the first aspect> In the embodiment of the present invention, a transmission method of a forwarder is provided, and the description is given from the forwarder side.

[0045] FIG. 3 is a diagram illustrating a transmission method of a forwarder in an embodiment of the present invention. As shown in FIG. 3, the method includes the following steps: 301: A forwarder receives control information from a network device via a control link, wherein the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and 302: The forwarder performs forwarding on a backhaul link and / or an access link based on the control information.

[0046] Note that, although the above-mentioned FIG. 3 is used to exemplify an embodiment of the present invention, the present invention is not limited thereto. For example, the execution order of each step (operation) can be appropriately adjusted, or some operations can be added or removed. Those skilled in the art can make appropriate modifications based on the above content without being limited to the description of the above-mentioned FIG. 3.

[0047] In the following description, "supporting" a certain characteristic means that the characteristic is mandatorily supported by NCR-MT.

[0048] For example, the degree to which the feature is supported may be determined based on the capabilities of the NCR, e.g., the NCR may report its capabilities to the network device, and the network device may determine the degree to which the feature is mandatorily supported by the NCR-MT based on the capabilities reported by the NCR.

[0049] Also, for example, it may not be required that the NCR report the capability, but may instead fully mandate support for the feature.

[0050] In the following description, "not being mandatorily supported" for a certain feature means that the feature is not mandatorily supported by the NCR, and may be referred to as optional. For example, a certain feature may be selectively supported or not supported. For example, a device manufacturer may choose whether or not the NCR has a certain feature.

[0051] In the embodiment of the present invention, the NCR-MT is used by the NCR-Fwd to forward signals between the terminal equipment and the network equipment. In view of this, most of the NR features and settings for enhancement are not necessary for the NCR-MT, since its location can be fixed and its function can be simplified as much as possible.

[0052] To ensure communication between the NCR-MT and network equipment, basic terminal capabilities must be supported by the NCR-MT. The following describes NR-related features and capabilities that are supported or not mandatorily supported by the NCR-MT, including, for example, NCR-MT waveforms and modulation, initial access and mobility management, MIMO, uplink and downlink control channels, scheduling / HARQ operation, etc.

[0053] First, the waveform and modulation characteristics of NCR will be explained below.

[0054] In some embodiments, the forwarder supports uplink and downlink transmission of CP-OFDM waveforms.

[0055] In some embodiments, the transmitter is not mandatorily configured to support uplink transmission of Discrete Fourier Transform-Spread Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveforms.

[0056] In some embodiments, the forwarder supports an uplink modulation scheme.

[0057] In some embodiments, the forwarder supports a downlink modulation scheme.

[0058] It should be noted that each of the above NCR waveforms and modulation characteristics may be supported alone, or one or more of them may be supported together, e.g., a transmitter may support any combination of the above.

[0059] The initial access and mobility management features of NCR are further described below.

[0060] In some embodiments, the forwarder supports initial access capabilities, including supporting a random access channel (RACH) preamble format, and / or mandating no support for synchronization signal block (SSB) based radio resource management (RRM) measurements, and / or supporting reception of broadcast system information blocks (SIBs), and / or mandating no support for paging.

[0061] For example, in the case of RACH (Random Access Channel) preamble format: one preamble format is supported.

[0062] Also, for example, regarding broadcast SIB reception, MIB reception is supported, SIB1 (RMSI) reception is supported, and OSI (other SIBs) is supported or not forcibly supported.

[0063] In some embodiments, the forwarder supports mobility management capabilities, including supporting SSB based radio link management (RLM) and / or mandatorily not supporting channel state information reference signal (CSI-RS) based radio link management (RLM).

[0064] It should be noted that the above-mentioned NCR initial access and mobility management features may be supported individually, or one or more of them may be supported together; for example, a forwarder may support any combination of the above.

[0065] The MIMO properties of NCR are further explained below.

[0066] In some embodiments, the transmitter supports multiple-input multiple-output (MIMO) features, which include at least one of the following: supporting physical downlink shared channel (PDSCH) reception, supporting PDSCH beam switching, supporting the number of PDSCH MIMO layers, supporting a transmission configuration indication (TCI) state for PDSCH, not mandating support for an active TCI state for PDCCH, supporting downlink DMRS, not mandating support for downlink semi-static physical resource block binding, supporting physical uplink shared channel (PUSCH) transmission, supporting uplink DMRS, supporting beam management capabilities, supporting CSI-RS-related capabilities, supporting downlink phase tracking reference signal (PTRS), supporting uplink PTRS, supporting time / frequency tracking reference signal (TRS)-related capabilities, supporting sounding reference signal (SRS)-related capabilities, and supporting spatial domain-related related capabilities.

[0067] In some embodiments, the forwarder supports basic PDSCH reception characteristics.

[0068] For example, in the case of mapping between data and resource elements (RE): Supported.

[0069] Also, for example, in the case of single layer transmission: Supported.

[0070] Also, for example, in the case of one transmission configuration indication (TCI) state: Supported.

[0071] In some embodiments, the forwarder supports beam switching for PDSCH.

[0072] For example, for duration: supported under FR2.

[0073] In some embodiments, the forwarder supports a maximum number of MIMO layers for the PDSCH.

[0074] For example, in a single-carrier standalone scenario, if four transmission channels are required to support at least four MIMO layers within a specified frequency band, then at least two MIMO layers are supported under FR2.

[0075] In some embodiments, the transporter supports the TCI state of the PDSCH.

[0076] For example, the number of supported active TCI states may be: {1, 2, 4, 8}, or the number of supported active TCI states may be 1 and / or 2 and / or 4 and / or 8 (ie, any combination of 1, 2, 4, 8).

[0077] Also, for example, in the case of the maximum number of configurable TCI states: {4, 8, 16, 32, 64, 128} is supported, or the maximum number of configurable TCI states supported is 4 and / or 8 and / or 16 and / or 32 and / or 64 and / or 128 (i.e., any combination of 4, 8, 16, 32, 64, 128).

[0078] In some embodiments, the forwarder does not enforce support for additional active TCI states for the PDCCH.

[0079] For example, in addition to the number of active TCI states for the PDSCH, one additional active TCI state for the control channel is supported, and this feature is supported only when the maximum number of active TCIs for the PDSCH is one.

[0080] In some embodiments, the forwarder supports basic downlink DMRS.

[0081] For example, for Type A DMRS: For at least one port, if the prefix DMRS of one symbol does not have any additional DMRS symbols: supported; For at least one port, if one symbol prefix DMRS has one additional DMRS symbol: supported or not mandatory supported; For at least one port, if prefix DMRS of one symbol has two additional DMRS symbols: supported or mandatory not supported.

[0082] Also, for example, for Type B DMRS: For at least one port, if the prefix DMRS of one symbol does not have any additional DMRS symbols: supported; For at least one port, if prefix DMRS of one symbol has one additional DMRS symbol: supported or mandatory not supported.

[0083] Also, for example, to support 1+2 DMRS: For multiple ports, if one prefix DMRS symbol uses two additional DMRS symbols: Force not supported.

[0084] It also supports DMRS types, e.g.: For type 1: Supported; For type 2: Force no support.

[0085] In some embodiments, the forwarder is not mandatorily supporting the downlink semi-static physical resource block binding capability.

[0086] In some embodiments, the forwarder supports basic PUSCH transmission characteristics.

[0087] For example, in the case of mapping between data and RE: Supported.

[0088] Also, for example, in the case of single layer transmission (single Tx): Supported.

[0089] Also, for example, single-port single-resource SRS transmission (the use of the SRS set is set as "codebook"): supported.

[0090] In some embodiments, the forwarder supports basic uplink DMRS.

[0091] For example, for Type A DMRS: For prefix DMRS of one symbol, if there are no additional DMRS symbols: supported; For one symbol prefix DMRS, if there is one additional DMRS symbol: supported or not mandatory supported; For one symbol prefix DMRS, if there are two additional DMRS symbols: supported or mandatorily not supported.

[0092] Also, for example, for Type B DMRS: For prefix DMRS of one symbol, if there are no additional DMRS symbols: supported; For one symbol prefix DMRS, if there is one additional DMRS symbol: supported or not mandatory supported.

[0093] Also, for example, to support 1+2 DMRS: For multiple ports, if prefix DMRS of one symbol has two additional DMRS symbols: Mandatory not supported.

[0094] Also, for example, to support DMRS types: For type 1: Supported; For type 2: Supported.

[0095] Also, for example, in the case of two-symbol uplink prefix DMRS: not supported compulsorily.

[0096] Also, for example, in the case of two-symbol uplink prefix DMRS and one additional two-symbol DMRS: Forced not to support.

[0097] In some embodiments, the forwarder supports Beam management related capabilities.

[0098] For example, beam correspondence: supported.

[0099] Also, for example, periodic beam reports and aperiodic beam reports: supported.

[0100] Also, for example, in the case of beam measurement based on SSB or CSI-RS: not mandatory support.

[0101] Also, for example, in the case of Beam reporting time: Supported.

[0102] Also, for example, when selecting a receiving beam using repetition "on" of CSI-RS resources: supported or forcibly not supported.

[0103] Also, for example, in the case of Beam switching: Force not to support.

[0104] Also, for example, in the case of non-group beam reporting: supported or not forcibly supported.

[0105] Also, for example, in the case of uplink beam management: supported or not forcibly supported.

[0106] Also, for example, in the case of Beam revocation (failure) recovery: not forcefully supported.

[0107] In some embodiments, the forwarder supports CSI-RS related capabilities.

[0108] For example, for CSI feedback: Support.

[0109] Also, for example, in the case of CSI feedback received by CSI-RS and CSI-IM: Supported.

[0110] Also, for example, in the case of RE mapping mode of PDSCH: Supported.

[0111] Also, for example, in the case of semi-persistent CSI-RS: Supported.

[0112] Also, for example, in the case of CSI reporting structure: Support.

[0113] Also, for example, in the case of Type I single panel codebook: Not forcibly supported.

[0114] In some embodiments, the forwarder supports basic downlink and uplink PTRS.

[0115] For example, supporting a downlink PTRS for the port and / or supporting an uplink PTRS for the port.

[0116] In some embodiments, the transporter supports TRS-related capabilities.

[0117] For example, for basic TRS: Supported.

[0118] Also, for example, in the case of TRS (CSI-RS for tracking): supported or not forcibly supported.

[0119] In some embodiments, the forwarder supports SRS-related capabilities.

[0120] For example, for basic SRS: Supported.

[0121] Also, for example, in the case of SRS resources: supported or not forcibly supported.

[0122] Also, for example, in the case of SRS transmission switching: supported or forcibly not supported.

[0123] In some embodiments, the forwarder supports uplink spatial domain related association capabilities.

[0124] For example, for spatial domain relationships to be set: supported or forced not supported.

[0125] Also, for example, in the case of active spatial domain relations: supported or forced not supported.

[0126] Also, for example, in the case of additional active spatial domain relationships for PUCCH: not forcibly supported.

[0127] It should be noted that each of the above MIMO characteristics of NCR may be supported alone, or one or more of them may be supported, for example, a forwarder may support any combination of the above.

[0128] The uplink and downlink control channel and process related characteristics of NCR are further described below.

[0129] In some embodiments, the forwarder supports downlink control channel and process features.

[0130] For example, for basic downlink control channel characteristics: Supported.

[0131] Also, for example, if each scheduling CC processes one unicast DCI scheduling DL and two unicast DCI scheduling UL per slot under TDD: not forcibly supported.

[0132] Also, for example, type 1 CSS and type 3 CSS configured by dedicated RRC, SS with 6RB bitmap and 3 OFDM symbols dedicated to UE under FR2, CORESET resource allocation: supported or not forcibly supported.

[0133] Also, for example, if there is more than one CORESET setting per BWP other than CORESET 0: supported or not mandatorily supported under FR2.

[0134] Also, for example, if more than one TCI state setting is allowed in each CORESET: supported or not forcibly supported.

[0135] In some embodiments, the forwarder supports uplink control channel and process features.

[0136] For example, for basic uplink control channel characteristics: Supported.

[0137] Also, for example, in the case of PUCCH format 2, which is effective for frequency hopping over 1 to 2 OFDM symbols per slot: supported or not supported compulsorily.

[0138] Also, for example, in the case of PUCCH format 3, which is effective for frequency hopping over 4 to 14 OFDM symbols per slot: supported or not supported compulsorily.

[0139] Also, for example, in the case of non-frequency hopping PUCCH formats 0 and 2 with frequency hopping disabled: not supported forcibly.

[0140] Also, for example, in the case of non-frequency hopping PUCCH formats 1, 3 and 4 with frequency hopping disabled: not supported forcibly.

[0141] Also, for example, in the case of a dynamic HARQ-ACK codebook: supported or not supported by force.

[0142] Also, for example, in the case of a semi-static HARQ-ACK codebook: support or not support is forced.

[0143] Also, for example, in the case of HARQ-ACK spatial domain bundling of PUSCH for each PUCCH or PUCCH: not forcibly supported.

[0144] Also, for example, when SR / HARQ-ACK / CSI is transmitted using the same starting symbol in one slot in a PUCCH resource, the case where SR / HARQ-ACK / CSI is multiplexed once with one PUCCH (or HARQ-ACK / CSI attached to a PUSCH) per slot: not forcibly supported.

[0145] Also, for example, in the case of UCI code group segmentation: Forced not to support.

[0146] Also, for example, repetition of PUCCH formats 1, 3, and 4 with K=2, 4, 8 in multiple slots: not supported compulsorily.

[0147] Also, for example, when PUCCH-spatial relation info is indicated by MAC CE for each PUCCH resource: supported or not forcibly supported.

[0148] Also, for example, in the case of HARQ-ACK with the starting FDM symbol of a different PUCCH / PUSCH multiplexed with PUSCH: supported or not supported compulsorily.

[0149] It should be noted that the above-mentioned NCR uplink / downlink control channel and process-related characteristics may be supported individually, or one or more of them may be supported, for example, the forwarder may support any combination of the above.

[0150] The NCR scheduling or HARQ operation will be further described below.

[0151] In some embodiments, the forwarder supports scheduling or hybrid automatic repeat request (HARQ) operation.

[0152] For example, for basic scheduling or HARQ operation: Supported.

[0153] Also, for example, in the case of frequency hopping within a slot of a PUSCH scheduled by Type 1 CSS before an RRC connection: not forcibly supported.

[0154] Also, for example, in the case of PDSCH mapping type A with fewer than seven OFDM symbols: not supported forcibly.

[0155] Also, for example, in the case of PDSCH mapping type B: not forcibly supported.

[0156] Also, for example, in the case of frequency hopping within a slot of a PUCCH other than a PUSCH scheduled by Type 1 CSS before RRC connection: this is forcibly not supported.

[0157] Also, for example, in the case of PUSCH overlapping in multiple slots, this is forcibly not supported.

[0158] Also, for example, in the case of semi-static and dynamic rate matching resource sets configured for DL: Not forcibly supported.

[0159] Also, for example, in the case of rate matching surrounding LTE CRS: not forcibly supported.

[0160] Also, for example, when DL scheduling of PDSCH type A has a slot offset greater than 0, it is forcibly not supported.

[0161] Also, for example, when DL scheduling of PDSCH type B has a slot offset greater than 0, it is forcibly not supported.

[0162] Also, for example, in the case of a UL scheduling slot offset greater than 12: Forced not to support.

[0163] The channel coding properties of NCR are further explained below.

[0164] In some embodiments, the forwarder supports channel coding.

[0165] The uplink transmit power control characteristics of NCR will be further explained below.

[0166] In some embodiments, the forwarder supports uplink transmit power control (TPC).

[0167] For example, for LTE-NR DC dynamic power balancing: Force not to support.

[0168] Also, for example, in the case of operation A in single UL Tx case 1: not supported forcibly.

[0169] Also, for example, for basic power control operations: Supported.

[0170] Also, for example, in the case of two PUSCH closed-loop uplink power control: not forcibly supported.

[0171] Also, for example, in the case of two PUCCH closed-loop downlink power controls: not forcibly supported.

[0172] It should be noted that the above-mentioned NCR scheduling or HARQ operation related features may be supported independently, or one or more of them may be supported together, e.g., the forwarder may support any combination of the above.

[0173] The following further describes the NCR characteristics that are not mandatorily supported.

[0174] In some embodiments, the forwarder is not mandated to support or does not support at least one of the following features or capabilities: two-step random access, unlicensing, eMIMO, carrier aggregation (CA), multi-radio dual connectivity (MR-DC), and integrated access and backhaul (IAB) related capabilities.

[0175] In some embodiments, the forwarder is not mandated to support or does not support at least one of the following features or capabilities: non-terrestrial network (NTN), NR from 52.6 GHz to 71 GHz, and downlink 1024QAM related features of FR1.

[0176] In some embodiments, the forwarder is not mandated to support or does not support at least one of the following features or capabilities: Crosslink Interference (CLI), Remote Interference Management (RIM), and Multicast Broadcast Service (MBS) related features.

[0177] It should be noted that the above-mentioned NCR characteristics that are not compulsorily supported may be one or more of them, for example, the forwarder may not be compulsorily required to support any combination of the above.

[0178] Although the above examples are used to exemplify the capability characteristics of NCR-MT, the present invention is not limited thereto. Furthermore, the above-mentioned characteristics can be arbitrarily combined to form a capability characteristic table supported or compulsorily supported by NCR-MT. The following further describes the capability groups that are compulsorily required by NCR-MT through Table 1. Unless otherwise specified, other capability groups or component parts of the capability groups and specific capabilities can be selected by NCR-MT.

[0179] Table 1: Layer-1 mandatory features for NCR-MT.

[0180] [Table 1] TIFF2025526610000003.tif220170TIFF2025526610000004.tif204170TIFF2025526610 000005.tif192170TIFF2025526610000006.tif231170TIFF2025526610000007.tif20417 0TIFF2025526610000008.tif231170TIFF2025526610000009.tif129170TIFF2025526610 000010.tif235170TIFF2025526610000011.tif225170TIFF2025526610000012.tif78170 Although Table 1 shows an example of capability characteristics that are forcibly supported by NCR-MT, the present invention is not limited to this. For example, a new capability characteristic table may be created by deleting some of the content in Table 1, or another capability characteristic table may be created by adding more content. Based on the above content, the present invention allows various combinations of NCR-MT capability characteristics.

[0181] The above-described embodiments are provided to exemplify the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0182] According to an embodiment of the present invention, a forwarder receives control information from a network device through a control link, and the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform, so that the forwarder can communicate with the network device, and the network device can configure the forwarding of the forwarder based on the network conditions, thereby further enhancing signal coverage and adapting to changes in the environment and main tasks within the cell, thereby improving the transmission efficiency of the entire network.

[0183] <Example of the second aspect> In an embodiment of the present invention, a forwarder is provided, which may be, for example, a network device or a terminal device, or may be one or more components or assemblies disposed in the network device or the terminal device.

[0184] 4 is a diagram illustrating a transmitter according to an embodiment of the present invention. The principle by which the transmitter solves the problem is the same as the method according to the embodiment of the first aspect, so that specific implementations can refer to the embodiment of the first aspect, and redundant explanations of the same content will be omitted here.

[0185] As shown in FIG. 4, a forwarder 400 in an embodiment of the present invention includes: A communication unit 401: receiving control information from a network device via a control link, wherein the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and A forwarding unit 402 performs forwarding via a backhaul link and / or an access link based on the control information.

[0186] 4 shows only the configuration of the forwarder 400, but the present invention is not limited to this. For example, the communication unit 401 may be called an NCR-MT or may be a certain module or assembly of the NCR-MT, and the forwarding unit 402 may be called an NCR-Fwd or may be a certain module or assembly of the NCR-Fwd.

[0187] In some embodiments, the forwarder is not mandatorily configured to support uplink transmission of DFT-s-OFDM waveforms.

[0188] In some embodiments, the forwarder supports an uplink modulation scheme.

[0189] In some embodiments, the forwarder supports a downlink modulation scheme.

[0190] In some embodiments, the forwarder supports an early access capability.

[0191] In some embodiments, the forwarder supporting initial access capabilities includes supporting a random access channel (RACH) preamble format, and / or not mandating support for synchronization signal block (SSB) based radio resource management (RRM) measurements, and / or supporting reception of broadcast system information blocks (SIBs), and / or not mandating support for paging.

[0192] In some embodiments, the forwarder supports mobility management capabilities.

[0193] In some embodiments, the forwarder supporting mobility management capabilities includes supporting SSB based Radio Link Management (RLM) and / or mandatorily not supporting Channel State Information Reference Signal (CSI-RS) based Radio Link Management (RLM).

[0194] In some embodiments, the forwarder supports multiple input multiple output (MIMO) features.

[0195] In some embodiments, the transmitter's support of multiple-input multiple-output (MIMO) features includes at least one of the following: supporting physical downlink shared channel (PDSCH) reception, supporting PDSCH beam switching, supporting the number of PDSCH MIMO layers, supporting a transmission configuration indication (TCI) state for PDSCH, not mandating support for an active TCI state for PDCCH, supporting downlink DMRS, not mandating support for downlink semi-static physical resource block binding, supporting physical uplink shared channel (PUSCH) transmission, supporting uplink DMRS, supporting beam management capabilities, supporting CSI-RS-related capabilities, supporting downlink phase tracking reference signal (PTRS), supporting uplink PTRS, supporting time / frequency tracking reference signal (TRS)-related capabilities, supporting sounding reference signal (SRS)-related capabilities, and supporting spatial domain-related related capabilities.

[0196] In some embodiments, the forwarder supports downlink control channel and procedure features.

[0197] In some embodiments, the forwarder supports uplink control channel and process features.

[0198] In some embodiments, the forwarder supports scheduling or hybrid automatic repeat request (HARQ) operation.

[0199] In some embodiments, the forwarder supports channel coding.

[0200] In some embodiments, the forwarder supports uplink transmit power control (TPC).

[0201] In some embodiments, the forwarder is not mandated to support or does not support at least one of the following features or capabilities: two-step random access, unlicensed, eMIMO, carrier aggregation (CA), multi-radio dual connectivity (MR-DC), and integrated access and backhaul (IAB) related capabilities.

[0202] In some embodiments, the forwarder is not mandated to support or does not support at least one of the following features or capabilities: non-terrestrial network (NTN), NR from 52.6 GHz to 71 GHz, and downlink 1024QAM related features of FR1.

[0203] In some embodiments, the forwarder is not mandated to support or does not support at least one of the following features or capabilities: Crosslink Interference (CLI), Remote Interference Management (RIM), and Multicast Broadcast Service (MBS) related features.

[0204] 4 shows only the connection relationships or signal directions between each component or module for convenience, but various related technologies such as bus connection may be adopted as would be understood by a person skilled in the art. Each of the components or modules described above may be realized by hardware such as a processor, a memory, a transmitter (device), or a receiver (device), but the implementation of the present invention is not limited thereto.

[0205] The above-described embodiments are provided to exemplify the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0206] According to an embodiment of the present invention, a forwarder receives control information from a network device through a control link, and the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform, so that the forwarder can communicate with the network device, and the network device can configure the forwarding of the forwarder based on the network conditions, thereby further enhancing signal coverage and adapting to changes in the environment and main tasks within the cell, thereby improving the transmission efficiency of the entire network.

[0207] <Example of the third aspect> In the embodiment of the present invention, a control method for a forwarder is provided, and will be described from the perspective of a network device. Note that the description of the same content as in the embodiment of the first aspect will be omitted.

[0208] FIG. 5 illustrates a control method for a transmitter in an embodiment of the present invention. As shown in FIG. 5, the method includes the following steps: 501: A network device sends control information to a forwarder via a control link, where the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and 502: The network device receives or transmits a transmission signal on a backhaul link.

[0209] Note that while the above-mentioned FIG. 5 is used to exemplify an embodiment of the present invention, the present invention is not limited thereto. For example, the execution order of each step (operation) can be adjusted, or some operations can be added or removed. Those skilled in the art can make appropriate modifications based on the above content without being limited to the description of FIG. 5.

[0210] In some embodiments, a network device may send a forwarding signal (e.g., a signal whose destination is a terminal device and is forwarded by the forwarder) and / or a communication signal (e.g., a signal whose destination is the forwarder) to a forwarder, or the network device may also receive a forwarding signal (e.g., a signal generated and transmitted by a terminal device and forwarded by the forwarder) and / or a communication signal (e.g., a signal generated and transmitted by the forwarder) from a forwarder.

[0211] Although the steps or processes related to the present invention have been described above, the present invention is not limited thereto. The method in the embodiments of the present invention may further include other steps or processes, and the specific contents of these steps or processes can be found in the related art.

[0212] The above-described embodiments are provided to exemplify the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0213] In accordance with an embodiment of the present invention, a network device transmits control information to a forwarder through a control link, and the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform, so that the forwarder can communicate with the network device, and the network device can configure the forwarding of the forwarder based on the network conditions, thereby further enhancing signal coverage and adapting to changes in the environment and main tasks within the cell, thereby improving the transmission efficiency of the entire network.

[0214] <Example of the fourth aspect> An embodiment of the present invention provides a network device.

[0215] 6 is a diagram illustrating a network device according to an embodiment of the present invention. The principle by which the network device solves the problem is the same as the method according to the third embodiment, so that specific implementations can refer to the third embodiment, and redundant explanations of the same content will be omitted here.

[0216] As shown in FIG. 6, a network device 600 in an embodiment of the present invention includes: A communication unit 601: transmitting control information to a forwarder via a control link, wherein the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and Transmitter / receiver 602: Receives or transmits a transport signal through a backhaul link.

[0217] In some embodiments, the network equipment may transmit forwarding signals (e.g., destination is a terminal equipment and forwarded by the forwarder) and / or communication signals (e.g., destination is the forwarder) to the forwarder, or the network equipment may also receive forwarding signals (e.g., generated and transmitted by a terminal equipment and forwarded by the forwarder) and / or communication signals (e.g., generated and transmitted by the forwarder) from the forwarder.

[0218] Although only the components or modules related to the present invention have been described above, the present invention is not limited thereto. The network device 600 in the embodiment of the present invention may further include other components or modules, and reference can be made to the related art for specific details of these components or modules.

[0219] 6 only shows the connection relationships or signal directions between each component or module for convenience, but as will be understood by those skilled in the art, various related technologies such as bus connection may be adopted. Each of the above-described components or modules may be realized by hardware such as a processor, memory, transmitter, or receiver, but the implementation of the present invention is not limited thereto.

[0220] The above-described embodiments are provided to exemplify the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0221] In accordance with an embodiment of the present invention, a network device transmits control information to a forwarder through a control link, and the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform, so that the forwarder can communicate with the network device, and the network device can configure the forwarding of the forwarder based on the network conditions, thereby further enhancing signal coverage and adapting to changes in the environment and main tasks within the cell, thereby improving the transmission efficiency of the entire network.

[0222] <Example of the fifth aspect> In an embodiment of the present invention, a communication system is provided, and Fig. 1 is a diagram illustrating the communication system in the embodiment of the present invention. As shown in Fig. 1, the communication system 100 includes a network device 101, a forwarder 102, and a terminal device 103. For convenience, Fig. 1 illustrates only one network device, one forwarder, and one terminal device, but the embodiment of the present invention is not limited thereto.

[0223] In an embodiment of the present invention, existing or future services may be transmitted between the network device 101 and the terminal device 103. For example, these services may include, but are not limited to, eMBB, mMTC, URLLC, V2X communication, etc. The forwarder 102 is configured to execute the transmission method described in the embodiment of the first aspect, and the network device 101 is configured to execute the control method described in the embodiment of the third aspect, the contents of which are incorporated herein and will not be described in detail again.

[0224] An embodiment of the present invention further provides an electronic device, which may be, for example, a transporter or a network device.

[0225] 7 is a block diagram of an electronic device according to an embodiment of the present invention. As shown in FIG. 7, the electronic device 700 may include a processor 710 (e.g., a central processing unit (CPU)) and a memory 720, which is connected to the processor 710. The memory 720 can store various data and can also store a program 730 for information processing, and can execute the program 730 under the control of the processor 710.

[0226] For example, the processor 710 may be configured to execute a program to implement the transmission method described in the embodiments of the first aspect. For example, the processor 710 may be configured to perform the following controls: receive control information from a network device over a control link, in which the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and perform transmission over a backhaul link and / or an access link based on the control information.

[0227] For example, the processor 710 may be configured to execute a program to implement the control method described in the embodiments of the third aspect. For example, the processor 710 may be configured to perform the following controls: send control information to a forwarder over a control link, where the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and receive or send a transport signal over a backhaul link.

[0228] 7, the electronic device 700 may further include a transceiver 740, an antenna 750, etc., among which the functions of the above-mentioned components are the same as those of the prior art, and therefore detailed description thereof will be omitted here. Note that the electronic device 700 does not need to include all the components shown in FIG. 7. The electronic device 700 may further include components not shown in FIG. 7, and for this, reference can be made to the prior art.

[0229] An embodiment of the present invention further provides a computer-readable program, which, when executed by a transmitter, causes a computer to perform the transmission method according to the embodiment of the first aspect at the transmitter.

[0230] An embodiment of the present invention further provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer to perform the transmission method according to the embodiment of the first aspect in a transmitter.

[0231] An embodiment of the present invention further provides a computer-readable program, which, when executed by a network device, causes a computer to execute the control method described in the embodiment of the third aspect on the network device.

[0232] An embodiment of the present invention further provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer to execute the control method described in the embodiment of the third aspect in a network device.

[0233] The above-described devices and methods may be realized by software or hardware, or by a combination of hardware and software. The present invention further relates to a computer-readable program as described below, which, when executed by a logic component, causes the logic component to realize the above-described devices or components, or to perform each of the above-described methods or steps. The logic component may be, for example, an FPGA (Field Programmable Gate Array), a microprocessor, or a processing unit used in a computer. The present invention also relates to a storage medium, such as a hard disk, magnetic disk, optical hard disk, DVD, or flash memory, that stores the above-described program.

[0234] Furthermore, one or more combinations of the functional blocks illustrated in the figures and / or one or more combinations of the functional blocks may be implemented as 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 component, a discrete gate or transistor logic component, a discrete hardware assembly, or any other suitable combination for performing the functions described herein. Also, one or more combinations of the functional blocks illustrated in the figures and / or one or more combinations of the functional blocks may be further implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors communicatively coupled with a DSP, or any other configuration.

[0235] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and any modifications to the present invention that do not depart from the spirit of the present invention fall within the technical scope of the present invention.

[0236] Furthermore, the following additional notes are disclosed regarding the above-mentioned embodiments.

[0237] (Appendix 1) A transmission method for a forwarder, comprising: a forwarder receiving control information from a network device over a control link, wherein the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and The forwarder performs forwarding on a backhaul link and / or an access link based on the control information.

[0238] (Appendix 2) 2. The method of claim 1, comprising: The transmitter is not mandatorily configured to support uplink transmission of Discrete Fourier Transform Splayed Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveforms.

[0239] (Appendix 3) 10. The method according to claim 1 or 2, The forwarder supports an uplink modulation scheme and / or a downlink modulation scheme.

[0240] (Appendix 4) 4. The method of any one of claims 1 to 3, comprising: The forwarder supports initial access and / or mobility management capabilities.

[0241] (Appendix 5) 5. The method of claim 4, The forwarder's support of initial access capabilities includes the following: supporting a random access channel (RACH) preamble format, and / or not mandatorily supporting synchronization signal block (SSB) based radio resource management (RRM) measurements, and / or supporting reception of broadcast system information blocks (SIBs), and / or not mandatorily supporting paging.

[0242] (Appendix 6) 5. The method of claim 4, The forwarder's support of mobility management capabilities includes the following: supporting SSB-based radio link management (RLM) and / or not mandatorily supporting channel state information reference signal (CSI-RS)-based radio link management (RLM).

[0243] (Appendix 7) 7. The method of any one of claims 1 to 6, comprising: The transmitter supports multiple-input multiple-output (MIMO) characteristics.

[0244] (Appendix 8) 8. The method of claim 7, The transmitter's support of multiple-input multiple-output (MIMO) characteristics includes at least one of the following: supporting physical downlink shared channel (PDSCH) reception, supporting PDSCH beam switching, supporting the number of PDSCH MIMO layers, supporting the PDSCH transmission configuration indication (TCI) state, not mandating support for the PDCCH active TCI state, supporting downlink DMRS, not mandating support for downlink semi-static physical resource block binding, supporting physical uplink shared channel (PUSCH) transmission, supporting uplink DMRS, supporting beam management capabilities, supporting CSI-RS related capabilities, supporting downlink phase tracking reference signal (PTRS), supporting uplink PTRS, supporting time / frequency tracking reference signal (TRS) related capabilities, supporting sounding reference signal (SRS) related capabilities, and supporting spatial domain related related capabilities.

[0245] (Appendix 9) 9. The method of any one of claims 1 to 8, comprising: The forwarder supports downlink control channel and process characteristics, and / or the forwarder supports uplink control channel and process characteristics.

[0246] (Appendix 10) 10. The method of any one of claims 1 to 9, comprising: The forwarder supports scheduling or hybrid automatic repeat request (HARQ) operation, and / or the forwarder supports channel coding, and / or the forwarder supports uplink transmit power control (TPC).

[0247] (Appendix 11) 11. The method of any one of claims 1 to 10, comprising: The forwarder is not mandatorily supported or does not support at least one of the following features or capabilities: two-step random access, unlicensed, eMIMO, carrier aggregation (CA), multi-radio dual connectivity (MR-DC), and integrated access and backhaul (IAB) related capabilities.

[0248] (Appendix 12) 12. The method of any one of claims 1 to 11, comprising: The transmitter is not mandatorily supported or does not support at least one of the following characteristics or capabilities: non-terrestrial network (NTN), NR from 52.6 GHz to 71 GHz, and downlink 1024QAM related characteristics of FR1.

[0249] (Appendix 13) 13. The method of any one of claims 1 to 12, comprising: The forwarder is not mandatorily supported or does not support at least one of the following features or capabilities: Crosslink Interference (CLI), Remote Interference Management (RIM), and Multicast Broadcast Service (MBS) related features.

[0250] (Appendix 14) A method for controlling a transfer device, comprising: The network device sends control information to a forwarder over a control link, wherein the forwarder supports uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform; and The network device receiving or transmitting a transport signal over a backhaul link.

[0251] (Appendix 15) a transporter, a memory and a processor; The memory stores a computer program, and the processor is configured to execute the computer program to implement the transfer device communication method described in any one of Supplementary Notes 1 to 13.

[0252] (Appendix 16) A network device, a memory and a processor; The memory stores a computer program, and the processor is configured to execute the computer program to implement the method for controlling a transfer device described in Appendix 14.

Claims

1. a transporter, a communication unit for receiving control information from a network device over a control link, the forwarder supporting uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing waveform; and a forwarding unit that performs forwarding on a backhaul link and / or an access link based on the control information;

2. 2. The transfer device of claim 1, The transmitter does not mandatorily support uplink transmission of Discrete Fourier Transform Splayed Orthogonal Frequency Division Multiplexing waveforms.

3. 2. The transfer device of claim 1, The forwarder supports an uplink modulation scheme.

4. 2. The transfer device of claim 1, The forwarder supports a downlink modulation scheme.

5. 2. The transfer device of claim 1, The forwarder supports initial access capabilities.

6. 6. The transfer device of claim 5, The forwarder's support of early access capabilities includes: A forwarder that supports a random access channel preamble format and / or does not mandatorily support radio resource management measurements based on synchronization signal blocks and / or supports reception of broadcast system information blocks and / or does not mandatorily support paging.

7. 2. The transfer device of claim 1, The forwarder supports mobility management capabilities.

8. 8. The transfer device of claim 7, The forwarder's support of mobility management capabilities includes: A forwarder that supports radio link management based on synchronization signal blocks and / or does not mandatorily support radio link management based on channel state information reference signals.

9. 2. The transfer device of claim 1, The forwarder supports multiple input and multiple output characteristics.

10. 10. The transfer device of claim 9, The forwarder supporting multiple input and multiple output characteristics includes at least one of the following: A transmitter that supports physical downlink shared channel reception, supports physical downlink shared channel beam switching, supports physical downlink shared channel MIMO layer number, supports physical downlink shared channel transmission configuration indication state, does not mandatorily support physical downlink control channel active transmission configuration indication state, supports downlink demodulation reference signal, does not mandatorily support downlink semi-static physical resource block binding, supports physical uplink shared channel transmission, supports uplink demodulation reference signal, supports beam management capability, supports channel state information reference signal related capability, supports downlink phase tracking reference signal, supports uplink phase tracking reference signal, supports time / frequency tracking reference signal related capability, supports sounding reference signal related capability, and supports spatial domain relationship related capability.

11. 2. The transfer device of claim 1, The forwarder supports downlink control channel and process characteristics.

12. 2. The transfer device of claim 1, The forwarder supports uplink control channel and process characteristics.

13. 2. The transfer device of claim 1, The forwarder supports scheduled or hybrid automatic retransmission request operations.

14. 2. The transfer device of claim 1, The forwarder supports channel coding.

15. 2. The transfer device of claim 1, The forwarder supports uplink transmit power control.

16. 2. The transfer device of claim 1, The forwarder is not mandatorily able to support or support at least one of the following characteristics or capabilities: The forwarder supports two-step random access, permissionless, eMIMO, carrier aggregation, multi-radio dual connectivity, and integrated access and backhaul related capabilities.

17. 2. The transfer device of claim 1, The forwarder is not mandatorily able to support or support at least one of the following characteristics or capabilities: Non-terrestrial network, NR from 52.6 GHz to 71 GHz, and FR1 downlink 1024QAM related characteristics, transmitter.

18. 2. The transfer device of claim 1, The forwarder is not mandatorily able to support or support at least one of the following characteristics or capabilities: Crosslink interference, remote interference management and multicast broadcasting related features, forwarder.

19. A network device, a communication unit that transmits control information over a control link to a forwarder, the forwarder supporting uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing waveform; and Network equipment including a transceiver that receives or transmits transport signals over a backhaul link.

20. 1. A communication system comprising: a network device that transmits control information to the forwarder over a control link; and a forwarder that receives the control information from the network device, the forwarder supporting uplink and downlink transmission of a cyclic prefix orthogonal frequency division multiplexing waveform, and forwarding on a backhaul link and / or an access link based on the control information.

Images