CN117693958A

CN117693958A - Communication method, device and storage medium

Info

Publication number: CN117693958A
Application number: CN202380011784.5A
Authority: CN
Inventors: 刘敏
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2023-10-19
Filing date: 2023-10-19
Publication date: 2024-03-12

Abstract

The present disclosure relates to a communication method, apparatus, and storage medium, including: and receiving first information, wherein the first information is used for configuring TDD information for each frequency domain unit in a plurality of frequency domain units, the TDD information is used for indicating the forwarding type of the repeater on different time domain units, and the forwarding type comprises at least one of uplink forwarding, downlink forwarding or flexible forwarding. The method solves the problem that the TDD information cannot be configured for each frequency domain unit of the repeater, provides a scheme for configuring the TDD information for the frequency domain units, and further improves the accuracy of the configured forwarding type of the frequency domain units by configuring the forwarding type for the time domain unit of each frequency domain unit in the plurality of frequency domain units and ensures the reliability of communication through the configured frequency domain units of the TDD information.

Description

Communication method, device and storage medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a communications method, an apparatus, and a storage medium.

Background

With the rapid development of mobile communication technology, an NCR (Network Controlled Repeater, network control repeater) may be disposed between a terminal and a network device to implement the supplement of communication coverage, so as to implement the reliability of communication between the terminal and the network device.

Disclosure of Invention

The method solves the problem that TDD (Time Division Duplex ) information cannot be configured for each frequency domain unit of the repeater, provides a scheme for configuring the TDD information for the frequency domain units, configures a forwarding type for a time domain unit of each of a plurality of frequency domain units, and provides a solution when the TDD information of the plurality of frequency domain units conflicts, so that the accuracy of the configured forwarding type of the frequency domain units is improved, and the reliability of communication through the configured frequency domain units of the TDD information is ensured.

The embodiment of the disclosure provides a communication method, a device and a storage medium.

According to a first aspect of embodiments of the present disclosure, there is provided a communication method, the method being performed by a repeater, the method comprising:

and receiving first information sent by the network equipment, wherein the first information is used for configuring TDD information for each frequency domain unit in a plurality of frequency domain units, the TDD information is used for indicating forwarding types of the repeater on different time domain units, and the forwarding types comprise at least one of uplink forwarding, downlink forwarding or flexible forwarding.

According to a second aspect of embodiments of the present disclosure, there is provided a communication method performed by a network device, the method comprising:

And sending first information to a repeater, wherein the first information is used for configuring TDD information for each frequency domain unit in a plurality of frequency domain units, the TDD information is used for indicating the forwarding type of the repeater on different time domain units, and the forwarding type comprises at least one of uplink forwarding, downlink forwarding or flexible forwarding.

According to a third aspect of embodiments of the present disclosure, there is provided a communication method, the method comprising:

the network equipment sends first information to the repeater, wherein the first information is used for configuring TDD information for each frequency domain unit in a plurality of frequency domain units, the TDD information is used for indicating the forwarding type of the repeater on different time domain units, and the forwarding type comprises at least one of uplink forwarding, downlink forwarding or flexible forwarding;

and the repeater receives the first information sent by the network equipment.

According to a fourth aspect of embodiments of the present disclosure, there is provided a communication apparatus, comprising:

the device comprises a transceiver module, a first receiving module and a second receiving module, wherein the transceiver module is used for receiving first information sent by network equipment, the first information is used for configuring TDD information for each frequency domain unit in a plurality of frequency domain units, the TDD information is used for indicating forwarding types of the repeater on different time domain units, and the forwarding types comprise at least one of uplink forwarding, downlink forwarding or flexible forwarding.

According to a fifth aspect of embodiments of the present disclosure, there is provided a communication apparatus, including:

and a transceiver module configured to send first information to a repeater, where the first information is configured to configure TDD information for each of a plurality of frequency domain units, and the TDD information is configured to indicate a forwarding type of the repeater on different time domain units, where the forwarding type includes at least one of uplink forwarding, downlink forwarding, or flexible forwarding.

According to a sixth aspect of the embodiments of the present disclosure, there is provided a communication apparatus, including:

one or more processors;

wherein the communication device is configured to perform the method of any of the first aspects.

According to a seventh aspect of the embodiments of the present disclosure, there is provided a communication apparatus, including:

one or more processors;

wherein the communication device is configured to perform the method of any of the second aspects.

According to an eighth aspect of an embodiment of the present disclosure, there is provided a communication system including:

a repeater configured to implement the communication method of the first aspect, and a network device configured to implement the communication method of the second aspect.

According to a ninth aspect of the embodiments of the present disclosure, a storage medium is presented, the storage medium storing instructions that, when run on a communication device, cause the communication device to perform the method of any one of the first or second aspects.

Drawings

The accompanying drawings, which are included to provide a further understanding of embodiments of the disclosure, illustrate and explain the exemplary embodiments of the disclosure and together with the description serve to explain the embodiments of the disclosure and do not constitute an undue limitation on the embodiments of the disclosure. In the drawings:

fig. 1 is a schematic architecture diagram of a communication system shown in accordance with an embodiment of the present disclosure;

FIG. 2 is an interactive schematic diagram of a communication method shown in accordance with an embodiment of the present disclosure;

FIG. 3A is a flow diagram illustrating a communication method according to an embodiment of the present disclosure;

FIG. 3B is a flow chart diagram of a communication method shown in accordance with an embodiment of the present disclosure;

FIG. 4 is a flow diagram of a communication method shown in accordance with an embodiment of the present disclosure;

FIG. 5 is a flow diagram of a communication method shown in accordance with an embodiment of the present disclosure;

FIG. 6 is a flow diagram of a communication method shown in accordance with an embodiment of the present disclosure;

Fig. 7A is a schematic structural diagram of a communication device according to an embodiment of the present disclosure;

fig. 7B is a schematic structural diagram of a communication device according to an embodiment of the present disclosure;

fig. 8A is a schematic structural diagram of a communication device according to an embodiment of the present disclosure;

fig. 8B is a schematic structural diagram of a chip according to an embodiment of the disclosure.

Detailed Description

The present disclosure provides a communication method, apparatus, and storage medium.

and receiving first information sent by the network equipment, wherein the first information is used for configuring Time Division Duplex (TDD) information for each frequency domain unit in a plurality of frequency domain units, the TDD information is used for indicating forwarding types of the repeater on different time domain units, and the forwarding types comprise at least one of uplink forwarding, downlink forwarding or flexible forwarding.

In the above embodiment, the problem that TDD (Time Division Duplex ) information cannot be configured for each frequency domain unit of the repeater is solved, and a scheme for configuring TDD information for a frequency domain unit is provided.

With reference to some embodiments of the first aspect, in some embodiments, the method further includes:

second information sent by the network device and/or an OAM (Operation Administration and Maintenance, operation and maintenance management) device is received, the second information being used to configure the plurality of frequency domain units.

And receiving second information sent by the network equipment or the OAM equipment, wherein the second information is used for configuring the plurality of frequency domain units.

In the above embodiment, the plurality of frequency domain units are configured through the second information, so that the accuracy of the configured frequency domain units is ensured, and the reliability of communication based on the frequency domain units is further ensured.

With reference to some embodiments of the first aspect, the second information includes at least one of:

a starting position of the frequency domain unit;

the length of the frequency domain unit.

In the above embodiment, the reliability of the configured frequency domain unit is ensured by the starting position of the configured frequency domain unit and the length of the frequency domain unit, so as to further ensure the reliability of communication based on the frequency domain unit.

the repeater does not expect the TDD information of the multiple frequency domain unit configurations to collide.

In the above embodiment, the relay does not expect TDD information collision of multiple frequency domain units, so that the relay is guaranteed to communicate by adopting non-conflicting TDD information, the problem of TDD information collision is solved, and the reliability of communication is guaranteed.

With reference to some embodiments of the first aspect, in some embodiments, the relay does not support simultaneous transceiving on different frequency bands, and the relay does not expect collision of the TDD information configured by the plurality of frequency domain units;

or alternatively, the first and second heat exchangers may be,

the repeater supports simultaneous transceiving on different frequency bands, and the repeater does not expect conflict of the TDD information configured by a plurality of frequency domain units on the same frequency band, wherein the frequency band comprises a plurality of frequency domain units.

In the above embodiment, the repeater determines whether to not expect TDD information collision of multiple frequency domain units according to whether to have simultaneous transceiving on different frequency bands, so as to solve the problem of TDD information collision, and further ensure the reliability of the repeater communication.

determining a time domain unit in which a conflict occurs between a reference frequency domain unit in the plurality of frequency domain units and other frequency domain units in the plurality of frequency domain units except the reference frequency domain unit;

Ignoring the forwarding types corresponding to the time domain units in which the conflict occurs in the other frequency domain units; or determining the forwarding type corresponding to the time domain unit with the conflict in the other frequency domain units as the forwarding type corresponding to the reference frequency domain unit.

In the above embodiment, the repeater determines how to determine the forwarding type corresponding to the time domain unit by determining the time domain unit where the conflict occurs in the plurality of frequency domain units, so as to ensure the accuracy of determining the forwarding type corresponding to the time domain unit, solve the problem of TDD information conflict, and further ensure the reliability of communication based on the frequency domain units.

With reference to some embodiments of the first aspect, in some embodiments, the relay does not expect TDD information collision for a plurality of frequency domain units, including:

the repeater does not expect that the TDD information indicated in the dynamic scheduling conflicts with the TDD information of the reference frequency domain unit.

In the above embodiment, the repeater determines the reliability of communication based on the frequency domain unit by not expecting an indication that the TDD information of the dynamic scheduling indication conflicts with the TDD information of the reference frequency domain unit, solving the problem of TDD information conflict.

With reference to some embodiments of the first aspect, in some embodiments, the relay supports semi-static configuration of TDD information.

With reference to some embodiments of the first aspect, in some embodiments, the determining a time domain unit in which the reference frequency domain unit collides with other frequency domain units includes:

and determining a time domain unit in which the reference frequency domain unit collides with the other frequency domain units indicated by the dynamic scheduling.

With reference to some embodiments of the first aspect, in some embodiments, the relay supports dynamic indication of TDD information.

The reference frequency domain unit refers to a frequency domain unit with the smallest frequency domain unit in the plurality of frequency domain units; or, the reference frequency domain unit refers to a frequency domain unit with the minimum identification on each frequency band.

With reference to some embodiments of the first aspect, in some embodiments, the repeater does not support simultaneous transceiving on different frequency bands, and the reference frequency domain unit refers to a frequency domain unit identified as the smallest among the plurality of frequency domain units; or alternatively, the first and second heat exchangers may be,

the repeater supports simultaneous transceiving on different frequency bands, and the reference frequency domain unit refers to a frequency domain unit with the minimum identifier on each frequency band.

transmitting third information to the network device, the third information being used to instruct the repeater to resolve a collision when there is the collision in the forwarding types in the plurality of frequency domain units, or,

And receiving fourth information sent by the OAM equipment, wherein the fourth information is used for indicating that the relay supports conflict resolution when the forwarding types in the frequency domain units have conflict.

In the above embodiment, the repeater reports its own support to resolve the conflict, thereby ensuring the reliability of communication using a plurality of frequency domain units.

With reference to some embodiments of the first aspect, in some embodiments, the first information is further used to indicate whether each frequency domain unit of the plurality of frequency domain units supports resolving a conflict occurring with TDD information.

In a second aspect, embodiments of the present disclosure provide a communication method performed by a network device, the method comprising:

and sending first information to a repeater, wherein the first information is used for configuring Time Division Duplex (TDD) information for each frequency domain unit in a plurality of frequency domain units, the TDD information is used for indicating the forwarding type of the repeater on different time domain units, and the forwarding type comprises at least one of uplink forwarding, downlink forwarding or flexible forwarding.

With reference to some embodiments of the second aspect, in some embodiments, the method further includes:

receiving second information sent by an OAM device, wherein the second information is used for configuring the plurality of frequency domain units;

Or alternatively, the first and second heat exchangers may be,

and sending the second information to the repeater.

With reference to some embodiments of the second aspect, in some embodiments, the second information includes at least one of:

a starting position of the frequency domain unit;

the length of the frequency domain unit.

the TDD information configured for the plurality of frequency domain units does not collide.

With reference to some embodiments of the second aspect, in some embodiments, the relay does not support simultaneous transceiving on different frequency bands, and the TDD information configured for the plurality of frequency domain units does not collide;

or alternatively, the first and second heat exchangers may be,

the repeater supports simultaneous receiving and transmitting on different frequency bands, and TDD information configured by a plurality of frequency domain units on the same frequency band does not collide.

determining a reference frequency domain unit in the plurality of frequency domain units and a time domain unit in other frequency domain units except the reference frequency domain unit in the plurality of frequency domain units, wherein the frequency band comprises a plurality of frequency domain units;

the forwarding types corresponding to the time domain units with conflicts in the other frequency domain units are ignored; or, the forwarding type corresponding to the reference frequency domain unit is determined as the forwarding type corresponding to the time domain unit where the conflict occurs in the other frequency domain units.

With reference to some embodiments of the second aspect, in some embodiments, the dynamically indicated TDD information does not conflict with TDD information of the reference frequency domain unit.

With reference to some embodiments of the second aspect, in some embodiments, the relay supports semi-static configuration of TDD information.

With reference to some embodiments of the second aspect, in some embodiments, the relay supports dynamic indication of TDD information.

With reference to some embodiments of the second aspect, in some embodiments, the reference frequency domain unit refers to a frequency domain unit that identifies a smallest among the plurality of frequency domain units; or, the reference frequency domain unit refers to a frequency domain unit with the minimum identification on each frequency band.

With reference to some embodiments of the second aspect, in some embodiments, the repeater does not support simultaneous transceiving on different frequency bands, and the reference frequency domain unit refers to a frequency domain unit identified as the smallest among the plurality of frequency domain units; or alternatively, the first and second heat exchangers may be,

And receiving third information sent by the repeater or the OAM equipment, wherein the third information is used for indicating that the repeater supports to resolve the conflict when the forwarding types in the frequency domain units have the conflict.

With reference to some embodiments of the second aspect, in some embodiments, the first information is further used to configure, for each frequency domain unit of the plurality of frequency domain units, whether resolving a conflict that occurs with TDD information is supported.

In a third aspect, embodiments of the present disclosure provide a communication method, the method including:

the network equipment sends first information to the repeater, wherein the first information is used for configuring Time Division Duplex (TDD) information for each frequency domain unit in a plurality of frequency domain units, the TDD information is used for indicating the forwarding type of the repeater on different time domain units, and the forwarding type comprises at least one of uplink forwarding, downlink forwarding or flexible forwarding;

the repeater receives first information sent by the network device.

In a fourth aspect, embodiments of the present disclosure provide a communication device including at least one of a transceiver module and a processing module; wherein the repeater is configured to perform the optional implementation manners of the first aspect and the third aspect.

In a fifth aspect, embodiments of the present disclosure provide a communication device including at least one of a transceiver module and a processing module; wherein the access network device is configured to perform the optional implementation manners of the second aspect and the third aspect.

In a sixth aspect, embodiments of the present disclosure provide a communication apparatus, including:

one or more processors;

wherein the communication device is configured to perform the method of any one of the first and third aspects.

In a seventh aspect, embodiments of the present disclosure provide a communication apparatus, including:

one or more processors;

wherein the communication device is adapted to perform the method of any one of the second and third aspects.

In an eighth aspect, an embodiment of the present disclosure provides a storage medium storing first information, which when run on a communication device, causes the communication device to perform the method according to any one of the first, second and third aspects.

In a ninth aspect, embodiments of the present disclosure propose a program product which, when executed by a communication device, causes the communication device to perform the method according to any one of the first, second and third aspects.

In a tenth aspect, the presently disclosed embodiments propose a computer program which, when run on a communication device, causes the communication device to perform the method according to any of the first, second and third aspects.

In an eleventh aspect, embodiments of the present disclosure provide a chip or chip system. The chip or chip system comprises processing circuitry configured to perform the method of any of the first, second and third aspects.

It will be appreciated that the repeater, the storage medium, the program product, the computer program, the chip or the chip system described above are all used to perform the method proposed by the embodiments of the present disclosure. Therefore, the advantages achieved by the method can be referred to as the advantages of the corresponding method, and will not be described herein.

The embodiment of the disclosure provides a communication method, a device and a storage medium. In some embodiments, terms such as a communication method and an information communication method, an indication method, and the like may be replaced with each other, terms such as a communication device and an information processing device, an indication device, and the like may be replaced with each other, and terms such as an information processing system, a communication system, and the like may be replaced with each other.

The embodiments of the present disclosure are not intended to be exhaustive, but rather are exemplary of some embodiments and are not intended to limit the scope of the disclosure. In the case of no contradiction, each step in a certain embodiment may be implemented as an independent embodiment, and the steps may be arbitrarily combined, for example, a scheme in which part of the steps are removed in a certain embodiment may also be implemented as an independent embodiment, the order of the steps in a certain embodiment may be arbitrarily exchanged, and further, alternative implementations in a certain embodiment may be arbitrarily combined; furthermore, various embodiments may be arbitrarily combined, for example, some or all steps of different embodiments may be arbitrarily combined, and an embodiment may be arbitrarily combined with alternative implementations of other embodiments.

In the various embodiments of the disclosure, terms and/or descriptions of the various embodiments are consistent throughout the various embodiments and may be referenced to each other in the absence of any particular explanation or logic conflict, and features from different embodiments may be combined to form new embodiments in accordance with their inherent logic relationships.

The terminology used in the embodiments of the disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure.

In the presently disclosed embodiments, elements that are referred to in the singular, such as "a," "an," "the," "said," etc., may mean "one and only one," or "one or more," "at least one," etc., unless otherwise indicated. For example, where an article (article) is used in translation, such as "a," "an," "the," etc., in english, a noun following the article may be understood as a singular expression or as a plural expression.

In the presently disclosed embodiments, "plurality" refers to two or more.

In some embodiments, terms such as "at least one of", "one or more of", "multiple of" and the like may be substituted for each other.

In some embodiments, "A, B at least one of", "a and/or B", "in one case a, in another case B", "in response to one case a", "in response to another case B", and the like, may include the following technical solutions according to circumstances: in some embodiments a (a is performed independently of B); b (B is performed independently of a) in some embodiments; in some embodiments, execution is selected from a and B (a and B are selectively executed); in some embodiments a and B (both a and B are performed). Similar to that described above when there are more branches such as A, B, C.

In some embodiments, the description modes such as "a or B" may include the following technical schemes according to circumstances: in some embodiments a (a is performed independently of B); b (B is performed independently of a) in some embodiments; in some embodiments execution is selected from a and B (a and B are selectively executed). Similar to that described above when there are more branches such as A, B, C.

The prefix words "first", "second", etc. in the embodiments of the present disclosure are only for distinguishing different description objects, and do not limit the location, order, priority, number, content, etc. of the description objects, and the statement of the description object refers to the claims or the description of the embodiment context, and should not constitute unnecessary limitations due to the use of the prefix words. For example, if the description object is a "field", the ordinal words before the "field" in the "first field" and the "second field" do not limit the position or the order between the "fields", and the "first" and the "second" do not limit whether the "fields" modified by the "first" and the "second" are in the same message or not. For another example, describing an object as "level", ordinal words preceding "level" in "first level" and "second level" do not limit priority between "levels". As another example, the number of descriptive objects is not limited by ordinal words, and may be one or more, taking "first device" as an example, where the number of "devices" may be one or more. Furthermore, objects modified by different prefix words may be the same or different, e.g., the description object is "a device", then "a first device" and "a second device" may be the same device or different devices, and the types may be the same or different; for another example, the description object is "information", and the "first information" and the "second information" may be the same information or different information, and the contents thereof may be the same or different.

In some embodiments, "comprising a", "containing a", "for indicating a", "carrying a", may be interpreted as carrying a directly, or as indicating a indirectly.

In some embodiments, terms such as "time/frequency", "time-frequency domain", and the like refer to the time domain and/or the frequency domain.

In some embodiments, terms "responsive to … …", "responsive to determination … …", "in the case of … …", "at … …", "when … …", "if … …", "if … …", and the like may be interchanged.

In some embodiments, terms "greater than", "greater than or equal to", "not less than", "more than or equal to", "not less than", "above" and the like may be interchanged, and terms "less than", "less than or equal to", "not greater than", "less than or equal to", "not more than", "below", "lower than or equal to", "no higher than", "below" and the like may be interchanged.

In some embodiments, the apparatuses and devices may be interpreted as entities, or may be interpreted as virtual, and the names thereof are not limited to those described in the embodiments, and may also be interpreted as "device (apparatus)", "device)", "circuit", "network element", "node", "function", "unit", "component (section)", "system", "network", "chip system", "entity", "body", and the like in some cases.

In some embodiments, a "network" may be interpreted as an apparatus comprised in the network, e.g. an access network device, a core network device, etc.

In some embodiments, the "access network device (access network device, AN device)" may also be referred to as a "radio access network device (radio access network device, RAN device)", "Base Station (BS)", "radio base station (radio base station)", "fixed station (fixed station)", and in some embodiments may also be referred to as a "node)", "access point (access point)", "transmission point (transmission point, TP)", "Reception Point (RP)", "transmission and/or reception point (transmission/reception point), TRP)", "panel", "antenna array", "cell", "macrocell", "microcell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier (component carrier)", bandwidth part (BWP), etc.

In some embodiments, a "terminal" or "terminal device" may be referred to as a "user equipment" (terminal) "," user terminal "(MS)", "mobile station (MT)", subscriber station (subscriber station), mobile unit (mobile unit), subscriber unit (subscore unit), wireless unit (wireless unit), remote unit (remote unit), mobile device (mobile device), wireless device (wireless device), wireless communication device (wireless communication device), remote device (remote device), mobile subscriber station (mobile subscriber station), access terminal (access terminal), mobile terminal (mobile terminal), wireless terminal (wireless terminal), remote terminal (mobile terminal), handheld device (handset), user agent (user), mobile client (client), client, etc.

In some embodiments, the acquisition of data, information, etc. may comply with laws and regulations of the country of locale.

In some embodiments, data, information, etc. may be obtained after user consent is obtained.

Furthermore, each element, each row, or each column in the tables of the embodiments of the present disclosure may be implemented as a separate embodiment, and any combination of elements, any rows, or any columns may also be implemented as a separate embodiment.

Fig. 1 is a schematic architecture diagram of a communication system according to an embodiment of the present disclosure, and as shown in fig. 1, a method provided by an embodiment of the present disclosure may be applied to a communication system 100, which may include a terminal 101 and a network device 102. It should be noted that, the communication system 100 may further include other devices, and the disclosure is not limited to the devices included in the communication system 100.

In some embodiments, the terminal 101 includes at least one of a mobile phone (mobile phone), a wearable device, an internet of things device, a communication enabled car, a smart car, a tablet (Pad), a wireless transceiver enabled computer, a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned (self-driving), a wireless terminal device in teleoperation (remote medical surgery), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), a wireless terminal device in smart home (smart home), for example, but is not limited thereto.

In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network, and the access network device may include at least one of an evolved NodeB (eNB), a next generation evolved NodeB (next generation eNB, ng-eNB), a next generation NodeB (next generation NodeB, gNB), a NodeB (node B, NB), a Home NodeB (HNB), a home NodeB (home evolved nodeB, heNB), a wireless backhaul device, a radio network controller (radio network controller, RNC), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a baseband unit (BBU), a mobile switching center, a base station in a 6G communication system, an Open base station (Open RAN), a Cloud base station (Cloud RAN), a base station in other communication systems, an access node in a Wi-Fi system, but is not limited thereto.

In some embodiments, the technical solutions of the present disclosure may be applied to an Open RAN architecture, where an access network device or an interface in an access network device according to the embodiments of the present disclosure may become an internal interface of the Open RAN, and flow and information interaction between these internal interfaces may be implemented by using software or a program.

In some embodiments, the access network device may be composed of a Central Unit (CU) and a Distributed Unit (DU), where the CU may also be referred to as a control unit (control unit), and the structure of the CU-DU may be used to split the protocol layers of the access network device, where functions of part of the protocol layers are centrally controlled by the CU, and functions of the rest of all the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU, but is not limited thereto.

In some embodiments, the core network device may be a device, including one or more network elements, or may be a plurality of devices or a device group, including all or part of one or more network elements. The network element may be virtual or physical. The core network comprises, for example, at least one of an evolved packet core (Evolved Packet Core, EPC), a 5G core network (5G Core Network,5GCN), a next generation core (Next Generation Core, NGC).

It may be understood that, the communication system described in the embodiments of the present disclosure is for more clearly describing the technical solutions of the embodiments of the present disclosure, and is not limited to the technical solutions provided in the embodiments of the present disclosure, and those skilled in the art can know that, with the evolution of the system architecture and the appearance of new service scenarios, the technical solutions provided in the embodiments of the present disclosure are applicable to similar technical problems.

The embodiments of the present disclosure described below may be applied to the communication system 100 shown in fig. 1, or a part of the main body, but are not limited thereto. The respective bodies shown in fig. 1 are examples, and the communication system may include all or part of the bodies in fig. 1, or may include other bodies than fig. 1, and the number and form of the respective bodies may be arbitrary, and the respective bodies may be physical or virtual, and the connection relationship between the respective bodies is examples, and the respective bodies may not be connected or may be connected, and the connection may be arbitrary, direct connection or indirect connection, or wired connection or wireless connection.

The embodiments of the present disclosure may be applied to long term evolution (Long Term Evolution, LTE), LTE-Advanced (LTE-a), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, fourth generation mobile communication system (4th generation mobile communication system,4G)), fifth generation mobile communication system (5th generation mobile communication system,5G), 5G New air (New Radio, NR), future wireless access (Future Radio Access, FRA), new wireless access technology (New-Radio Access Technology, RAT), new wireless (New Radio, NR), new wireless access (New Radio access, NX), future generation wireless access (Future generation Radio access, FX), global System for Mobile communications (GSM (registered trademark)), CDMA2000, ultra mobile broadband (Ultra Mobile Broadband, UMB), IEEE 802.11 (registered trademark), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, ultra WideBand (Ultra-wide-width, UWB), bluetooth (Bl terminal tooth (registered trademark), mobile communication network (Public Land Mobile Network, device-D, device-M, device-D, device-Device (internet of things system, device-2, device-D (internet of things system), device (internet of things), device (2-D, device-V), device (system extension, device (internet of things), etc. In addition, a plurality of system combinations (e.g., LTE or a combination of LTE-a and 5G, etc.) may be applied.

In some embodiments, a repeater is further included between the terminal 101 and the network device 102, and data is transmitted between the terminal 101 and the network device 102 through the repeater. Optionally, the repeater is an NCR, that is to say a transmission between the terminal 101 and the network device 102 via an NCR.

In some embodiments, the NCR may forward both upstream and downstream. Optionally, the uplink forwarding refers to that the terminal 101 sends uplink information to the NCR, and after the NCR receives the uplink information sent by the terminal 101, the terminal forwards the uplink information to the network device 102. Optionally, the downstream forwarding refers to that the network device 102 sends downstream information to the NCR, and after the NCR receives the downstream information sent by the network device 102, the downstream information is forwarded to the terminal 101. In some embodiments, the NCR may also be configured for flexible forwarding. The flexible forwarding refers to both uplink forwarding and downlink forwarding. Optionally, the network device indicates, by configuration, whether flexible forwarding of the NCR is upstream or downstream.

In some embodiments, the NCR includes an NCR-fwd (network controlled repeater forwarding, network control repeater forwarding) for forwarding information between the terminal and the network device and an NCR-mt (network controlled repeater mobile termination, network control repeater mobile terminal) for at least receiving instructions or configuration from the network device.

In some embodiments, the NCR may be configured with multiple frequency domain units, and each frequency domain unit may be configured with TDD information. Alternatively, the frequency domain unit may be carrier (carrier), BWP, or other frequency domain units, which are not limited by the embodiments of the present disclosure.

It should be noted that, the repeater in the embodiment of the present disclosure may also be understood as belonging to a network device, and it may be understood that the network device 102 includes a first network device and a second network device. Wherein the first network device is similar to the network device 102 in the above-described embodiments. The second network device is similar to the repeater in the above embodiment.

In some embodiments, the network device 102 further includes an OAM device configured to configure OAM information via OAM.

Optionally, the OAM information is used to carry information configuring the frequency domain unit. Alternatively, information configuring the frequency domain unit may also be carried, which is not limited by the embodiments of the present disclosure.

It should be noted that the OAM device in the embodiments of the present disclosure may also be referred to as a third network device, which is similar to the OAM device.

Fig. 2 is an interactive schematic diagram of a communication method shown in accordance with an embodiment of the present disclosure. As shown in fig. 2, an embodiment of the present disclosure relates to a communication method, the method including:

In step S2101, the repeater transmits third information to the network device.

In some embodiments, the network device receives the third information sent by the repeater. In some embodiments, the repeater transmits the third information. In some embodiments, the network device receives the third information.

In some embodiments, the third information is used to indicate that the repeater support resolves the collision when there is a collision in the forwarding type in the plurality of frequency domain units. In some embodiments, the third information is used to indicate that the repeater supports resolving the collision when there are multiple frequency domain units.

In some embodiments, the existence of a collision in the forwarding types in the multiple frequency domain units means that at least one frequency domain unit exists as uplink forwarding and at least one frequency domain unit exists as downlink forwarding. In some embodiments, the repeater support resolving conflicts when there are multiple frequency domain units refers to eliminating situations where at least one frequency domain unit is upstream and at least one frequency domain unit is downstream.

In some embodiments, the name of the third information is not limited. For example, capability information, reporting information, indication information, capability indication information, etc.

It should be noted that, in the embodiment of the present disclosure, the relay sends the third information to the network device is taken as an example to be described. In yet another embodiment, the repeater may also be configured by an OAM device.

In some embodiments, the repeater receives fourth information sent by the OAM device, the fourth information indicating that the repeater supports resolving a collision when there is a collision in the forwarding types in the plurality of frequency domain units. The fourth information is similar to the third information in the above embodiment, and will not be described here again.

It should be noted that, step S2101 is an optional step, and in another embodiment, step S2101 may not be performed.

In step S2102, the network device sends second information to the relay.

In some embodiments, the network device transmits the second information. In some embodiments, the repeater receives the second information. In some embodiments, the repeater receives second information sent by the network device.

In some embodiments, the second information is used to configure a plurality of frequency domain units. In the embodiment of the disclosure, the network device configures a plurality of frequency domain units for the repeater, and the subsequent repeater can communicate with the network device through the configured plurality of frequency domain units. Alternatively, the Frequency domain unit may be FR1 (Frequency range 1), FR2 (Frequency range 2), band (Frequency range), BWP (Carrier Bandwith Part, partial bandwidth), carrier, RB (Radio Bearer), or the like.

In some embodiments, the second information includes at least one of:

(1) The starting position of the frequency domain unit.

(2) The length of the frequency domain unit.

In some embodiments, the length of the frequency domain unit is configured by the network device.

In some embodiments, the frequency domain unit is an RB, and the starting position of the frequency domain unit is the starting RB, and the length of the frequency domain unit is the RB length.

In some embodiments, the second information multiplexes existing BWP configurations. The frequency domain unit is BWP, and the second information is used to configure a plurality of BWP. Optionally, the starting position of the frequency domain unit is the starting position of BWP. The length of the frequency domain unit is the length of BWP. In some embodiments, the second information is locationandband.

In some embodiments, the second information multiplexes an existing CC (component carrier, carrier) configuration. The frequency domain unit is a CC, and the second information is used to configure a plurality of CCs. Optionally, the starting position of the frequency domain unit is the starting position of the CC. The length of the frequency domain unit is the length of the CC.

In some embodiments, the second information may also be a newly defined band configuration. Alternatively, the initial RB in the second information may be ARFCN (absolute radio channel number). Alternatively, the starting RB may be an offset value with respect to a particular known frequency domain location. For example, the offset value with respect to a particular known frequency domain location is the smallest offset value with respect to SSB (Synchronization Signal/PBCH, synchronization signal block). Or, an offset value of the minimum RB with respect to a serving cell.

It should be noted that, the network device is different, and the signaling used is also different. In some embodiments, when the network device in the embodiments of the present disclosure is a base station, the second information is configured through air interface signaling. Optionally, the air interface signaling is RRC signaling. In some embodiments, when the network device in the embodiments of the present disclosure is an OAM device, the second information is configured by OAM.

It should be noted that, in the embodiment of the present disclosure, the network device sends the second information to the repeater is taken as an example to describe the embodiment. While in another embodiment the second information may also be sent by the OAM device.

Optionally, the OAM device sends the second information to the repeater. Correspondingly, the repeater receives the second information sent by the OAM equipment.

In some embodiments, the network device receives second information sent by the OAM device over the OAM.

In step S2103, the repeater does not expect the TDD information configured by the plurality of frequency domain units to collide.

In some embodiments, the conflict of TDD information configured by the plurality of frequency domain units means that at least one frequency domain unit is uplink forwarding and at least one frequency domain unit is downlink forwarding.

In the embodiment of the present disclosure, if TDD information configured by a plurality of frequency domain units of the repeater collides, the repeater cannot normally perform an operation, and thus the repeater does not expect the TDD information configured by the plurality of frequency domain units to collide.

In some embodiments, the relay does not expect the TDD information of the multiple frequency domain unit configuration to collide, which may also be understood as the relay does not expect the TDD information of the multiple frequency domain unit configuration to collide.

In some embodiments, the repeater does not expect the conflicting TDD information for the multiple frequency domain unit configurations, and the corresponding network device does not configure the conflicting TDD information for the multiple frequency domain units. Alternatively, it can be said that TDD information configured by the network device for a plurality of frequency domain units does not collide.

It should be noted that, based on the difference of the capabilities, there is a possibility that the repeater supports simultaneous transceiving on different frequency bands. Next, the configuration of TDD information will be described according to the relay.

In some embodiments, the repeater does not support simultaneous transceiving on different frequency bands, and the repeater does not expect the TDD information of multiple frequency domain unit configurations to collide.

In the embodiment of the present disclosure, since simultaneous transceiving on different frequency bands is not supported, if TDD information configured by a plurality of frequency bands collides, the repeater cannot normally perform operation, and thus the repeater does not expect that TDD information configured by a plurality of frequency domain units collides. Correspondingly, the network device also does not configure conflicting TDD information for multiple frequency domain units. Alternatively, it can be said that TDD information configured by the network device for a plurality of frequency domain units does not collide.

In some embodiments, the repeater supports simultaneous transceiving on different frequency bands, and the repeater does not expect the TDD information configured by multiple frequency domain units on the same frequency band to collide.

In the embodiment of the present disclosure, since simultaneous transceiving is supported on different frequency bands, TDD information between multiple frequency bands on the same frequency band collides, and the repeater cannot normally perform operation on the frequency band, so that the repeater does not expect that TDD information configured by multiple frequency domain units on the same frequency band collides. Correspondingly, the network device also does not configure conflicting TDD information for multiple frequency domain units on the same frequency band. Alternatively, it can be said that the network device does not collide with TDD information configured for a plurality of frequency domain units on the same frequency band.

In some embodiments, the repeater supports semi-static configuration of TDD information. In some embodiments, TDD information in the conflict of TDD information that the repeater in the above embodiments does not expect to configure is semi-static configuration.

In some embodiments, the repeater does not expect the dynamically indicated TDD information to collide with the TDD information of the reference frequency domain unit. In some embodiments, the TDD information in the TDD information collision that the repeater in the above embodiments does not expect configuration is a dynamic indication.

Optionally, the dynamic indication is indicated by DCI format 2-0.

It should be noted that step S2101 is an optional step, and in another embodiment, step S2101 may not be performed.

In step S2104, the network device transmits first information to the relay.

In some embodiments, the network device transmits the first information. In some embodiments, the repeater receives the first information. In some embodiments, the repeater receives first information sent by the network device.

In some embodiments, the first information is for configuring TDD information for each of a plurality of frequency domain units, the TDD information being for indicating a type of forwarding of the repeater on different time domain units, the type of forwarding including at least one of upstream forwarding, downstream forwarding, or flexible forwarding.

In some embodiments, determining a time domain unit in which a conflict occurs in a reference frequency domain unit in the plurality of frequency domain units and other frequency domain units except the reference frequency domain unit in the plurality of frequency domain units, and ignoring a forwarding type corresponding to the time domain unit in which the conflict occurs in the other frequency domain units; or determining the forwarding type corresponding to the time domain unit with the conflict in other frequency domain units as the forwarding type corresponding to the reference frequency domain unit. Optionally, the frequency band comprises a plurality of frequency domain units.

In the embodiment of the present disclosure, after the network device configures TDD information for each of multiple frequency domain units of the repeater, there may also be a conflicting frequency domain unit, where the repeater needs to determine the frequency domain unit where the conflict occurs, and then the subsequent repeater decides the forwarding type of the conflicting frequency domain unit.

In some embodiments, the repeater determines a reference frequency domain unit from the plurality of frequency domain units, determines a time domain unit that collides with the reference frequency domain unit, and ignores forwarding types corresponding to the time domain units that collide in other frequency domain units; or determining the forwarding type corresponding to the time domain unit which generates conflict in other frequency domain units as the forwarding type corresponding to the reference frequency domain unit.

In some embodiments, the reference frequency domain unit refers to the frequency domain unit that identifies the smallest of the plurality of frequency domain units; or, the reference frequency domain unit refers to a frequency domain unit with the smallest identification on each frequency band.

Optionally, if the repeater does not support simultaneous transceiving of multiple frequency domain units on the same frequency band, the reference frequency domain unit refers to a frequency domain unit with the smallest identifier among the multiple frequency domain units. Optionally, if the repeater supports simultaneous transceiving of multiple frequency domain units on the same frequency band, the reference frequency domain unit refers to a frequency domain unit with the smallest identifier on each frequency band.

Optionally, the repeater does not support simultaneous transceiving on different frequency bands, and the reference frequency domain unit refers to a frequency domain unit with the smallest identifier among the plurality of frequency domain units.

Optionally, the repeater supports simultaneous transceiving on different frequency bands, and the reference frequency domain unit refers to a frequency domain unit with the smallest identifier on each frequency band.

In some embodiments, the repeater supports semi-static configuration of TDD information. In some embodiments, the repeater supports dynamic indication of TDD information.

In some embodiments, the first information is further for configuring whether TDD collision resolution is supported for each frequency domain unit of the plurality of frequency domain units.

In the embodiment of the disclosure, for each frequency domain unit, each frequency domain unit further has a function of whether to support the conflict generated by the TDD information, that is, if the frequency domain unit does not support the conflict generated by the TDD information, the frequency domain unit does not participate in the above steps, and if the frequency domain unit supports the conflict generated by the TDD information, the frequency domain unit participates in the above steps.

It should be noted that, the embodiment of the present disclosure is described taking, as an example, whether the first information supports TDD collision resolution for each frequency domain unit configuration in the plurality of frequency domain units. In yet another embodiment, each frequency domain unit configuration of the plurality of frequency domain units may also be configured with other information as to whether the conflict occurring with TDD information is supported for resolution. Optionally, the repeater receives fifth information for configuring whether resolving a conflict occurring for the TDD information is supported for each of the plurality of frequency domain units.

In some embodiments, the names of information and the like are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "instruction", "command", "channel", "parameter", "field", "symbol", "codebook", "code word", "code point", "bit", "data", "program", "chip", and the like may be replaced with each other.

In some embodiments, terms such as "uplink," "physical uplink," and the like may be interchanged, terms such as "downlink," "physical downlink," and the like may be interchanged, terms such as "side," "side link," "side communication," "side link," "direct link," and the like may be interchanged.

In some embodiments, "acquire," "obtain," "receive," "transmit," "bi-directional transmit," "send and/or receive" may be used interchangeably and may be interpreted as receiving from other principals, acquiring from protocols, acquiring from higher layers, processing itself, autonomous implementation, etc.

In some embodiments, terms such as "send," "transmit," "report," "send," "transmit," "bi-directional," "send and/or receive," and the like may be used interchangeably.

In some embodiments, terms such as "time of day," "point of time," "time location," and the like may be interchanged, and terms such as "duration," "period," "time window," "time," and the like may be interchanged.

In some embodiments, terms such as "specific (specific)", "predetermined", "preset", "set", "indicated", "certain", "arbitrary", "first", and the like may be replaced with each other, and "specific a", "predetermined a", "preset a", "set a", "indicated a", "certain a", "arbitrary a", "first a" may be interpreted as a predetermined in a protocol or the like, may be interpreted as a obtained by setting, configuring, or indicating, or the like, may be interpreted as specific a, certain a, arbitrary a, or first a, or the like, but are not limited thereto.

The communication method according to the embodiment of the present disclosure may include at least one of step S2101 to step S2104. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, step S2104 may be implemented as an independent embodiment, step S2101 and step S2102 may be implemented as an independent embodiment, step S2103, step S2104 may be implemented as an independent embodiment, step S2101, step S2102, step S2103 may be implemented as an independent embodiment, step S2101, step S2102, step S2104 may be implemented as an independent embodiment, but is not limited thereto.

In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

In some embodiments, step S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

In some embodiments, step S2103 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

In some embodiments, step S2104 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

In some embodiments, steps S2101, S2102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

In some embodiments, steps S2101, S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

In some embodiments, steps S2102, S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

In some embodiments, steps S2101, S2102, S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

In some embodiments, reference may be made to alternative implementations described before or after the description corresponding to fig. 2.

Fig. 3A is a flow chart of a communication method according to an embodiment of the disclosure, which is applied to a repeater. As shown in fig. 3A, an embodiment of the present disclosure relates to a communication method, the method including:

In step S3101, the repeater transmits third information to the network device.

Alternative implementations of step S3101 may refer to alternative implementations of step S2101 of fig. 2, and other relevant parts of the embodiment related to fig. 2, which are not described herein.

In step S3102, the repeater does not expect TDD information collision for multiple frequency domain unit configurations.

Alternative implementations of step S3102 may refer to alternative implementations of step S2103 of fig. 2, and other relevant parts of the embodiment related to fig. 2, which are not described herein.

The communication method according to the embodiment of the present disclosure may include at least one of step S3101 to step S3102. For example, step S3101 may be implemented as a separate embodiment, step S3102 may be implemented as a separate embodiment, or at least two steps may be combined, but is not limited thereto.

In some embodiments, step S3101 is optional and step S3102 is optional, and one or more of these steps may be omitted or replaced in different embodiments. But is not limited thereto.

Fig. 3B is a flow chart of a communication method according to an embodiment of the disclosure, applied to a repeater. As shown in fig. 3B, an embodiment of the present disclosure relates to a communication method, the method including:

In step S3201, the repeater receives first information sent by the network device.

Alternative implementations of step S3201 may refer to step S2104 of fig. 2 and other relevant parts in the embodiment related to fig. 2, which are not described herein.

Fig. 4A is a flow chart of a communication method according to an embodiment of the present disclosure, which is applied to a network device, and as shown in fig. 4A, the embodiment of the present disclosure relates to a communication method, where the method includes:

in step S4101, the network device sends second information to the relay.

Alternative implementations of step S4101 may refer to step S2102 in fig. 2 and other relevant parts in the embodiment related to fig. 2, which are not described herein.

In step S4102, the network device sends first information to the relay.

Alternative implementations of step S4102 may refer to step S2104 of fig. 2 and other relevant parts in the embodiment related to fig. 2, which are not described here again.

Fig. 4B is a flow chart of a communication method according to an embodiment of the present disclosure, which is applied to a network device, and as shown in fig. 4B, the embodiment of the present disclosure relates to a communication method, where the method includes:

in step S4201, the network device sends first information to the repeater.

Alternative implementations of step S4201 may refer to step S2104 of fig. 2 and other relevant parts in the embodiment related to fig. 2, which are not described herein.

In some embodiments, the method further comprises:

or alternatively, the first and second heat exchangers may be,

and sending the second information to the repeater.

In some embodiments, the second information includes at least one of:

a starting position of the frequency domain unit;

the length of the frequency domain unit.

In some embodiments, the method further comprises:

In some embodiments, the repeater does not support simultaneous transceiving on different frequency bands, and the TDD information configured for the plurality of frequency domain units does not collide; or alternatively, the first and second heat exchangers may be,

In some embodiments, the method further comprises:

In some embodiments, the repeater supports semi-static configuration of TDD information.

In some embodiments, the dynamically indicated TDD information does not conflict with TDD information of the reference frequency domain unit.

In some embodiments, the repeater supports dynamic indication of TDD information.

In some embodiments, the reference frequency domain unit refers to a frequency domain unit that identifies a smallest frequency domain unit of the plurality of frequency domain units; or, the reference frequency domain unit refers to a frequency domain unit with the minimum identification on each frequency band.

In some embodiments, the repeater does not support simultaneous transceiving on different frequency bands, and the reference frequency domain unit refers to a frequency domain unit identified as the smallest among the plurality of frequency domain units;

or alternatively, the first and second heat exchangers may be,

In some embodiments, the method further comprises:

In some embodiments, the first information is further for configuring, for each frequency domain unit of the plurality of frequency domain units, whether resolving a conflict that occurs with TDD information is supported.

Fig. 5 is a flow chart illustrating a communication method according to an embodiment of the present disclosure, and as shown in fig. 5, the embodiment of the present disclosure relates to a communication method, where the method includes:

step S5101: the network device sends the first information to the relay.

In some embodiments, the first information is for configuring time division duplex, TDD, information for each of a plurality of frequency domain units, the TDD information being for indicating a type of forwarding of the repeater on different time domain units, the type of forwarding including at least one of uplink forwarding, downlink forwarding, or flexible forwarding.

Step S5102: the repeater receives first information sent by the network device.

Alternative implementations of step S5101 may refer to step S2104 of fig. 2, step S4102 of fig. 4A, and other relevant parts in the embodiments related to fig. 2 and 3A, which are not described herein.

Alternative implementations of step S5102 may refer to step S2104 of fig. 2, step S4102 of fig. 4A, and other relevant parts in the embodiments related to fig. 2 and 4A, which are not described herein.

In some embodiments, the method may include a method of an embodiment of the communication system side, the repeater side, the network device side, and so on, which are not described herein.

Fig. 6 is a flow chart illustrating a communication method according to an embodiment of the present disclosure, and as shown in fig. 6, the embodiment of the present disclosure relates to a communication method, which includes:

in step S6101, the base station configures a forwarding frequency domain unit for NCR.

In some embodiments, the frequency domain unit may be configured to the NCR-MT through RRC signaling.

In some embodiments, the content may be BWP, CC, configured to multiplex modes in existing protocols, such as

BWP, determination using BWP locationAndBandwidth

CC, configured with ServerCellConfigCommon/ServerCellConfigCommonSIB- > FrequencyinfoDL/FrequencyinfoUL-SIB/FrequencyinfoDL-SIB- > SCS-SpecificCarrier

In some embodiments, a new band configuration is defined, such as fwdfreq#1, fwdfreq#2 … configuration parameters including at least a start RB and an RB length, where,

the initial RB may be an absolute radio-frequency channel number (ARFCN)

Or an offset relative to a specific known frequency domain location,

o, e.g. offset of minimum RB relative to SSB

O is further e.g. offset with respect to serving cell minimum RB

In some embodiments, the base station configures TDD information for each frequency domain unit of the NCR, where uplink forwarding (e.g., U) indicates forwarding the signal of the UE to the base station, and downlink forwarding (e.g., D) indicates forwarding the signal of the base station to the UE, if not indicated, considered as flexible. The TDD configuration is semi-static, configured by RRC signaling, such as by TDD-UL-DL-ConfigCommon, TDD-UL-DL-ConfigDedicated; or the TDD configuration is dynamic, i.e. on the basis of the RRC configuration, the TDD thereof, i.e. in the uplink or downlink direction, may be indicated by dynamic signaling for a time domain unit of the flexible, e.g. symbol or slot.

In some embodiments, a method of avoiding collisions on multiple frequency domain units (if NCR only supports semi-static TDD configuration, then NCR does not forward on time domain units that do not indicate TDD)

In some embodiments, collisions are avoided at configuration time: NCR does not want the base station to be configured for TDD with different frequency domain unit configurations to collide.

-if the NCR does not have simultaneous transceiving on different frequency bands, the NCR does not want the TDD configuration of frequency domain unit #1-1 to collide with the TDD configuration of frequency domain unit # 1-2; if the NCR has simultaneous transmissions and receptions over different frequency bands, the NCR does not want the TDD configuration of frequency domain unit #1-1 and the TDD configuration of frequency domain unit #1-2 to collide over the same frequency band.

In some embodiments, if there is a conflict in configuration, when a conflict occurs, the NCR determines whether the conflicting time domain unit is uplink or downlink based on the TDD configuration of the reference frequency domain unit

-assuming that the TDD semi-static configuration of reference cells is DDDSSUUS and the TDD semi-static configuration of anothercells is ddussd; the third time domain unit collides, then the NCR behaves as follows:

o Option 1: disregarding the indication or considering the conflicting time domain unit as a flexible, where the time domain unit is not forwarded;

O Option 2: forwarding in the TDD direction by using a reference cell;

in some embodiments, a method of avoiding collisions on multiple frequency domain units (if NCR also supports dynamic TDD)

Optionally, collisions are avoided in semi-static configuration: NCR does not want the base station to be configured for TDD with a different frequency domain unit semi-static configuration to collide.

Alternatively, in the case of dynamic scheduling,

in some embodiments, the NCR does not want the dynamically indicated TDD to collide with the TDD of the reference cell; the NCR considers that the collision situation does not occur and the base station is not so configured.

In some embodiments, when a collision occurs, the NCR determines whether the colliding time domain unit is uplink or downlink based on the TDD configuration of the reference frequency domain unit

Let the TDD semi-static configuration of reference cell be DDDSSUUS, and the TDD semi-static configuration of anothercell be ddussd; at this time, the third time domain unit of the anothercell is indicated as U by dynamic scheduling, and then the NCR behaves as follows:

In some embodiments, regardless of the indication, the time domain unit is not forwarded here;

in some embodiments, the TDD direction of the reference cell is used for forwarding;

in some embodiments, the NCR determines the reference frequency domain unit according to predefined rules:

optionally, the frequency domain unit ID is the forwarding frequency domain unit with minimum index configured by the base station for NCR, or

Optionally, the frequency domain unit ID is the forwarding frequency domain unit with the smallest index on each frequency band

In some embodiments, if the NCR does not have simultaneous transceiving on a different frequency band, the reference frequency domain unit is option 1; if the NCR has simultaneous receiving and transmitting on different frequency bands, the reference frequency domain unit is option 2.

In some embodiments, the NCR performs capability reporting, where the capability indicates that the NCR supports handling the collision when the collision occurs in the forwarding direction (uplink or downlink).

In some embodiments, the base station enables TDD collision resolution for the forward frequency domain unit configuration of the NCR that is validated for a particular forward frequency domain unit.

For example, the UE reports the conflict resolution capability, the base station configures serving cell#1 for NCR, serving cell#2 for forwarding, and both cells enable the conflict resolution mechanism. When the UE has the conflict resolution capability and the conflict occurs and the conflict-occurring cell enables a conflict resolution mechanism, the NCR takes a cell index minimum cell on the frequency band as a reference cell, and the TDD semi-static configuration of the reference cell is assumed to be DDDSSS UUS, and the TDD semi-static configuration of the anothercell is assumed to be DDSSUSSD; at this time, the third time domain unit of the anothercell is indicated as U by dynamic scheduling, and the NCR disregards the indication, where the time domain unit is not forwarded.

For example, the base station configures a plurality of cells for the NCR, each cell is configured separately through TDD-UL-DL-ConfigCommon, and the NCR does not want the TDD configurations of these cells to collide, that is, the base station should avoid the situation that the collision occurs when configuring, in the embodiments of the present disclosure, some or all of the steps, and alternative implementations thereof may be combined with some or all of the steps in other embodiments, or may be combined with alternative implementations of other embodiments.

The embodiments of the present disclosure also propose an apparatus for implementing any of the above methods, for example, an apparatus comprising a unit or a module for implementing each step performed by the repeater in any of the above methods. For another example, another apparatus is also proposed, which includes a unit or module configured to implement steps performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

It should be understood that the division of each unit or module in the above apparatus is merely a division of a logic function, and may be fully or partially integrated into one physical entity or may be physically separated when actually implemented. Furthermore, units or modules in the apparatus may be implemented in the form of processor-invoked software: the device comprises, for example, a processor, the processor being connected to a memory, the memory having instructions stored therein, the processor invoking the instructions stored in the memory to perform any of the methods or to perform the functions of the units or modules of the device, wherein the processor is, for example, a general purpose processor, such as a central processing unit (Central Processing Unit, CPU) or microprocessor, and the memory is internal to the device or external to the device. Alternatively, the units or modules in the apparatus may be implemented in the form of hardware circuits, and part or all of the functions of the units or modules may be implemented by designing hardware circuits, which may be understood as one or more processors; for example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the units or modules are implemented by designing the logic relationships of elements in the circuit; for another example, in another implementation, the above hardware circuit may be implemented by a programmable logic device (programmable logic device, PLD), for example, a field programmable gate array (Field Programmable Gate Array, FPGA), which may include a large number of logic gates, and the connection relationship between the logic gates is configured by a configuration file, so as to implement the functions of some or all of the above units or modules. All units or modules of the above device may be realized in the form of invoking software by a processor, or in the form of hardware circuits, or in part in the form of invoking software by a processor, and in the rest in the form of hardware circuits.

In the disclosed embodiments, the processor is a circuit with signal processing capabilities, and in one implementation, the processor may be a circuit with instruction reading and running capabilities, such as a central processing unit (Central Processing Unit, CPU), microprocessor, graphics processor (graphics processing unit, GPU) (which may be understood as a microprocessor), or digital signal processor (digital signal processor, DSP), etc.; in another implementation, the processor may implement a function through a logical relationship of hardware circuits that are fixed or reconfigurable, e.g., a hardware circuit implemented as an application-specific integrated circuit (ASIC) or a programmable logic device (programmable logic device, PLD), such as an FPGA. In the reconfigurable hardware circuit, the processor loads the configuration document, and the process of implementing the configuration of the hardware circuit may be understood as a process of loading instructions by the processor to implement the functions of some or all of the above units or modules. Furthermore, hardware circuits designed for artificial intelligence may be used, which may be understood as ASICs, such as neural network processing units (Neural Network Processing Unit, NPU), tensor processing units (Tensor Processing Unit, TPU), deep learning processing units (Deep learning Processing Unit, DPU), etc.

Fig. 7A is a schematic structural diagram of a communication device according to an embodiment of the present disclosure. As shown in fig. 7A, the communication device 7100 may include: at least one of a transceiver module 7101, a processing module 7102, and the like. In some embodiments, the transceiver module 7101 is configured to receive first information, where the first information is configured to configure time division duplex TDD information for each of a plurality of frequency domain units, where the TDD information is configured to indicate a type of forwarding of the repeater on a different time domain unit, where the type of forwarding includes at least one of uplink forwarding, downlink forwarding, or flexible forwarding. Optionally, the transceiver module 7101 is configured to perform at least one of the communication steps (e.g., step S2101 but not limited thereto) of the transmission and/or reception performed by the repeater in any of the above methods, which is not described herein. Optionally, the processing module is configured to perform at least one of the other steps performed by the repeater in any of the above methods, which is not described herein.

Optionally, the processing module 7102 is configured to perform at least one of the communication steps such as the processing performed by the repeater in any of the above methods, which is not described herein.

Fig. 7B is a schematic structural diagram of a communication device according to an embodiment of the present disclosure. As shown in fig. 7B, the communication device 7200 may include: at least one of the transceiver module 7201, the processing module 7202, and the like. In some embodiments, the transceiver module 7201 is configured to transmit first information for configuring time division duplex, TDD, information for each of a plurality of frequency domain units, the TDD information being used to indicate a type of forwarding of the repeater on a different time domain unit, the type of forwarding including at least one of upstream forwarding, downstream forwarding, or flexible forwarding. Optionally, the transceiver module is configured to perform at least one of the communication steps (e.g., step S2102 but not limited thereto) of sending and/or receiving performed by the network device in any of the above methods, which is not described herein.

Optionally, the processing module 7202 is configured to perform at least one of the communication steps such as the processing performed by the network device in any of the above methods, which is not described herein.

In some embodiments, the transceiver module may include a transmitting module and/or a receiving module, which may be separate or integrated. Alternatively, the transceiver module may be interchangeable with a transceiver.

In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the plurality of sub-modules perform all or part of the steps required to be performed by the processing module, respectively. Alternatively, the processing module may be interchanged with the processor.

Fig. 8A is a schematic structural diagram of a communication device 8100 according to an embodiment of the present disclosure. The communication device 8100 may be a network device (e.g., an access network device, a core network device, etc.), a repeater, a chip system, a processor, etc. that supports the network device to implement any of the above methods, or a chip, a chip system, a processor, etc. that supports the repeater to implement any of the above methods. The communication device 8100 may be used to implement the method described in the above method embodiments, and reference may be made in particular to the description of the above method embodiments.

As shown in fig. 8A, communication device 8100 includes one or more processors 8101. The processor 8101 may be a general-purpose processor or a special-purpose processor, etc., and may be, for example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processor may be used to control communication devices (e.g., base stations, baseband chips, repeaters, repeater chips, DUs or CUs, etc.), execute programs, and process program data. The communication device 8100 is configured to perform any of the above methods.

In some embodiments, communication device 8100 also includes one or more memory 8102 for storing instructions. Alternatively, all or part of memory 8102 may be external to communication device 8100.

In some embodiments, communication device 8100 also includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceivers 8103 perform at least one of the communication steps (e.g., but not limited to, step S2101, step S2102, step S2103, step S2104) of transmission and/or reception in the above-described method.

In some embodiments, the transceiver may include a receiver and/or a transmitter, which may be separate or integrated. Alternatively, terms such as transceiver, transceiver unit, transceiver circuit, etc. may be replaced with each other, terms such as transmitter, transmitter circuit, etc. may be replaced with each other, and terms such as receiver, receiving unit, receiver, receiving circuit, etc. may be replaced with each other.

In some embodiments, communication device 8100 may include one or more interface circuits 8104. Optionally, an interface circuit 8104 is coupled to the memory 8102, the interface circuit 8104 being operable to receive signals from the memory 8102 or other device, and being operable to transmit signals to the memory 8102 or other device. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.

The communication device 8100 in the above embodiment description may be a network device or a repeater, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by fig. 8A. The communication device may be a stand-alone device or may be part of a larger device. For example, the communication device may be: 1) A stand-alone integrated circuit IC, or chip, or a system-on-a-chip or subsystem; (2) A set of one or more ICs, optionally including storage means for storing data, programs; (3) an ASIC, such as a Modem (Modem); (4) modules that may be embedded within other devices; (5) Receivers, repeaters, intelligent repeaters, cellular telephones, wireless devices, handsets, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.; (6) others, and so on.

Fig. 8B is a schematic structural diagram of a chip 8200 according to an embodiment of the disclosure. For the case where the communication device 8100 may be a chip or a chip system, reference may be made to a schematic structural diagram of the chip 8200 shown in fig. 8B, but is not limited thereto.

The chip 8200 includes one or more processors 8201, the chip 8200 being configured to perform any of the above methods.

In some embodiments, the chip 8200 further comprises one or more interface circuits 8202. Optionally, an interface circuit 8202 is coupled to the memory 8203, the interface circuit 8202 may be configured to receive signals from the memory 8203 or other device, and the interface circuit 8202 may be configured to transmit signals to the memory 8203 or other device. For example, the interface circuit 8202 may read instructions stored in the memory 8203 and send the instructions to the processor 8201.

In some embodiments, the interface circuit 8202 performs at least one of the sending and/or receiving communication steps of the methods described above, and the processor 8201 performs at least one of the other steps.

In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc. may be interchanged.

In some embodiments, chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memory 8203 may be external to the chip 8200.

The present disclosure also proposes a storage medium having stored thereon instructions that, when executed on a communication device 8100, cause the communication device 8100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Alternatively, the storage medium described above is a computer-readable storage medium, but is not limited thereto, and it may be a storage medium readable by other devices. Alternatively, the above-described storage medium may be a non-transitory (non-transitory) storage medium, but is not limited thereto, and it may also be a transitory storage medium.

The present disclosure also proposes a program product which, when executed by a communication device 8100, causes the communication device 8100 to perform any of the above methods. Optionally, the above-described program product is a computer program product.

The present disclosure also proposes a computer program which, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A method of communication, the method performed by a repeater, the method comprising:

2. The method according to claim 1, wherein the method further comprises:

and receiving second information sent by the network equipment and/or the operation, maintenance and management (OAM) equipment, wherein the second information is used for configuring the plurality of frequency domain units.

3. The method of claim 2, wherein the second information comprises at least one of:

a starting position of the frequency domain unit;

the length of the frequency domain unit.

4. A method according to any one of claims 1 to 3, wherein the method further comprises:

5. The method of claim 4, wherein the repeater does not support simultaneous transceiving on different frequency bands; or alternatively, the first and second heat exchangers may be,

6. A method according to any one of claims 1 to 3, wherein the method further comprises:

7. The method of claim 4, wherein the repeater does not expect TDD information collision for multiple frequency domain units, comprising:

the repeater does not expect the dynamically indicated TDD information to collide with the TDD information of the reference frequency domain unit.

8. The method according to any of claims 4 to 6, wherein the repeater supports semi-static configuration of TDD information.

9. The method according to any of claims 4 to 7, wherein the repeater supports dynamic indication of TDD information.

10. The method according to any one of claims 6 to 9, wherein the reference frequency domain unit refers to a frequency domain unit that identifies the smallest among the plurality of frequency domain units; or, the reference frequency domain unit refers to a frequency domain unit with the minimum identification on each frequency band.

11. The method of claim 10, wherein the repeater does not support simultaneous transmissions and receptions over different frequency bands, and wherein the reference frequency domain unit is a frequency domain unit that identifies a smallest among the plurality of frequency domain units; or alternatively, the first and second heat exchangers may be,

12. The method according to any one of claims 1 to 11, further comprising:

transmitting third information to the network device, the third information being used to instruct the repeater to resolve a collision when there is the collision in the forwarding types in the plurality of frequency domain units; or alternatively, the first and second heat exchangers may be,

13. The method of any of claims 1 to 12, wherein the first information is further used to indicate whether each of the plurality of frequency domain units supports resolving a conflict that occurs with TDD information.

14. A method of communication, the method performed by a network device, the method comprising:

15. The method of claim 14, wherein the method further comprises:

receiving second information sent by an OAM device, wherein the second information is used for configuring the plurality of frequency domain units; or alternatively, the first and second heat exchangers may be,

and sending the second information to the repeater.

16. The method of claim 15, wherein the second information comprises at least one of:

a starting position of the frequency domain unit;

the length of the frequency domain unit.

17. The method according to any one of claims 14 to 16, further comprising:

18. The method of claim 17, wherein the repeater does not support simultaneous transceiving on different frequency bands, and wherein the TDD information configured for the plurality of frequency domain units does not collide; or alternatively, the first and second heat exchangers may be,

19. The method according to any one of claims 14 to 16, further comprising:

20. The method of claim 17, wherein the dynamically indicated TDD information does not conflict with TDD information of a reference frequency domain element.

21. The method according to any of claims 17 to 19, wherein the repeater supports semi-static configuration of TDD information.

22. The method according to any of claims 17 to 21, wherein the repeater supports dynamic indication of TDD information.

23. The method according to any one of claims 19 to 22, wherein the reference frequency domain unit refers to a frequency domain unit that identifies the smallest of the plurality of frequency domain units; or, the reference frequency domain unit refers to a frequency domain unit with the minimum identification on each frequency band.

24. The method of claim 23, wherein the repeater does not support simultaneous transmissions and receptions over different frequency bands, and wherein the reference frequency domain unit is a frequency domain unit that identifies a smallest among the plurality of frequency domain units; or alternatively, the first and second heat exchangers may be,

25. The method according to any one of claims 14 to 24, further comprising:

26. The method of any of claims 14 to 25, wherein the first information is further used to configure whether resolving a conflict occurring with TDD information is supported for each of the plurality of frequency domain units.

27. A communication device, the communication device comprising:

and the receiving and transmitting module is used for receiving first information sent by the network equipment, the first information is used for configuring Time Division Duplex (TDD) information for each frequency domain unit in a plurality of frequency domain units, the TDD information is used for indicating the forwarding type of the repeater on different time domain units, and the forwarding type comprises at least one of uplink forwarding, downlink forwarding or flexible forwarding.

28. A communication device, the communication device comprising:

And a transceiver module configured to send first information to a repeater, where the first information is configured to configure time division duplex TDD information for each of a plurality of frequency domain units, and the TDD information is configured to indicate a forwarding type of the repeater on different time domain units, where the forwarding type includes at least one of uplink forwarding, downlink forwarding, or flexible forwarding.

29. A communication device, the communication device comprising:

one or more processors;

wherein the processor is configured to perform the communication method of any one of claims 1 to 13.

30. A communication device, the communication device comprising:

one or more processors;

wherein the processor is configured to perform the communication method of any one of claims 14 to 26.

31. A communication system comprising a repeater configured to implement the communication method of any one of claims 1 to 13 and a network device configured to implement the communication method of any one of claims 14 to 26.

32. A storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the communication method of any one of claims 1 to 13 or to perform the communication method of any one of claims 14 to 26.