[go: up one dir, main page]

WO2025081433A1 - Procédé et appareil de communication, et support de stockage - Google Patents

Procédé et appareil de communication, et support de stockage Download PDF

Info

Publication number
WO2025081433A1
WO2025081433A1 PCT/CN2023/125497 CN2023125497W WO2025081433A1 WO 2025081433 A1 WO2025081433 A1 WO 2025081433A1 CN 2023125497 W CN2023125497 W CN 2023125497W WO 2025081433 A1 WO2025081433 A1 WO 2025081433A1
Authority
WO
WIPO (PCT)
Prior art keywords
frequency domain
information
repeater
domain unit
forwarding
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/125497
Other languages
English (en)
Chinese (zh)
Inventor
刘敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to CN202380011784.5A priority Critical patent/CN117693958A/zh
Priority to PCT/CN2023/125497 priority patent/WO2025081433A1/fr
Publication of WO2025081433A1 publication Critical patent/WO2025081433A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a communication method, device and storage medium.
  • NCR Network Controlled Repeater
  • NCR Network Controlled Repeater
  • NCR can be set between the terminal and the network equipment to supplement the communication coverage and realize the reliability of communication between the terminal and the network equipment.
  • NCR can be configured with multiple frequency domain units, so that NCR can realize more flexible communication in the frequency domain.
  • the present invention solves the problem that TDD (Time Division Duplex) information cannot be configured for each frequency domain unit of a repeater, and provides a solution for configuring TDD information for frequency domain units.
  • TDD Time Division Duplex
  • the forwarding type for the time domain unit of each frequency domain unit in multiple frequency domain units, and providing a solution when the TDD information of multiple frequency domain units conflicts, the accuracy of the forwarding type of the configured frequency domain units is improved, and the reliability of communication through the frequency domain units that have been configured with TDD information is ensured.
  • the embodiments of the present disclosure provide a communication method, a device, and a storage medium.
  • a communication method is provided, the method being performed by a repeater, the method comprising:
  • Receive first information sent by a network device where the first information is used to configure TDD information for each frequency domain unit in a plurality of frequency domain units, where the TDD information is used 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.
  • a communication method is provided, the method being executed by a network device, the method comprising:
  • Send first information to the repeater wherein the first information is used to configure TDD information for each frequency domain unit in multiple frequency domain units, and the TDD information is used to indicate the forwarding type of the repeater on different time domain units, and the forwarding type includes at least one of uplink forwarding, downlink forwarding or flexible forwarding.
  • a communication method comprising:
  • the network device sends first information to the repeater, where the first information is used to configure TDD information for each frequency domain unit in the multiple frequency domain units, where the TDD information is used 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;
  • the repeater receives the first information sent by the network device.
  • a communication device including:
  • a transceiver module is used to receive first information sent by a network device, wherein the first information is used to configure TDD information for each frequency domain unit in a plurality of frequency domain units, and the TDD information is used to indicate the forwarding type of the repeater on different time domain units, wherein the forwarding type includes at least one of uplink forwarding, downlink forwarding or flexible forwarding.
  • a communication device including:
  • a transceiver module is used to send first information to a repeater, wherein the first information is used to configure TDD information for each frequency domain unit in a plurality of frequency domain units, wherein the TDD information is used to indicate a forwarding type of the repeater on different time domain units, wherein the forwarding type includes at least one of uplink forwarding, downlink forwarding or flexible forwarding.
  • a communication device including:
  • processors one or more processors
  • the communication device is used to execute any method described in the first aspect.
  • a communication device including:
  • processors one or more processors
  • the communication device is used to execute any method described in the second aspect.
  • a communication system including:
  • a repeater and a network device wherein the repeater is configured to implement the communication method described in the first aspect, and the network device is configured to implement the communication method described in the second aspect.
  • a storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes a method as described in any one of the first aspect or the second aspect.
  • FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
  • FIG2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure
  • FIG3A is a flow chart of a communication method according to an embodiment of the present disclosure.
  • FIG3B is a flow chart of a communication method according to an embodiment of the present disclosure.
  • FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure.
  • FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure.
  • FIG6 is a flow chart of a communication method according to an embodiment of the present disclosure.
  • FIG7A is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure.
  • FIG7B is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure.
  • FIG8A is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure.
  • FIG8B is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure.
  • the present disclosure provides a communication method, an apparatus and a storage medium.
  • a communication method is provided, the method being performed by a repeater, the method comprising:
  • Receive first information sent by a network device where the first information is used to configure time division duplex (TDD) information for each frequency domain unit in a plurality of frequency domain units, where the TDD information is used 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.
  • TDD time division duplex
  • the problem of being unable to configure TDD (Time Division Duplex) information for each frequency domain unit of the repeater is solved, and a solution for configuring TDD information for the frequency domain units is provided.
  • TDD Time Division Duplex
  • the method further includes:
  • OAM Operaation Administration and Maintenance
  • Second information sent by a network device or an OAM device is received, where the second information is used to configure the multiple frequency domain units.
  • multiple frequency domain units are configured through the second information to ensure the accuracy of the configured frequency domain units, thereby ensuring the reliability of communication based on the frequency domain units.
  • the second information includes at least one of the following:
  • the length of the frequency domain unit is the length of the frequency domain unit.
  • the reliability of the configured frequency domain unit is ensured by configuring the starting position of the frequency domain unit and the length of the frequency domain unit, thereby ensuring the reliability of communication based on the frequency domain unit.
  • the method further includes:
  • the repeater does not expect the TDD information configured by multiple frequency domain units to conflict.
  • the repeater does not expect TDD information conflicts among multiple frequency domain units, ensuring that the repeater uses non-conflicting TDD information for communication, solving the problem of TDD information conflicts and ensuring the reliability of communication.
  • the repeater does not support simultaneous transmission and reception on different frequency bands, and the repeater does not expect the TDD information configured by the multiple frequency domain units to conflict;
  • the repeater supports simultaneous transmission and reception on different frequency bands.
  • the repeater does not expect the TDD information configured by multiple frequency domain units on the same frequency band to conflict.
  • the frequency band includes multiple frequency domain units.
  • the repeater determines whether TDD information conflict of multiple frequency domain units is not expected according to whether there is simultaneous transmission and reception in different frequency bands, thereby solving the problem of TDD information conflict and ensuring the reliability of repeater communication.
  • the method further includes:
  • the repeater determines the time domain unit in which the conflict occurs among multiple frequency domain units, and then determines how to determine the forwarding type corresponding to the time domain unit, thereby ensuring the accuracy of determining the forwarding type corresponding to the time domain unit, solving the problem of TDD information conflict, and thus ensuring the reliability of communication based on the frequency domain unit.
  • the repeater does not expect TDD information conflicts of multiple frequency domain units, including:
  • the relay does not expect that the TDD information indicated by the dynamic scheduling conflicts with the TDD information of the reference frequency domain unit.
  • the repeater solves the problem of TDD information conflict by not expecting an indication that the TDD information indicated by the dynamic scheduling conflicts with the TDD information of the reference frequency domain unit, thereby determining the reliability of communication based on the frequency domain unit.
  • the repeater supports semi-static configuration of TDD information.
  • determining the time domain unit that conflicts between the reference frequency domain unit and other frequency domain units includes:
  • the repeater supports dynamic indication of TDD information.
  • the reference frequency domain unit refers to a frequency domain unit with a smallest identifier among the multiple frequency domain units; or, the reference frequency domain unit refers to a frequency domain unit with a smallest identifier on each frequency band.
  • the repeater does not support simultaneous transmission and reception on different frequency bands
  • the reference frequency domain unit refers to a frequency domain unit with a smallest identifier among the multiple frequency domain units
  • the repeater supports simultaneous transmission and reception on different frequency bands, and the reference frequency domain unit refers to the frequency domain unit with the smallest identifier on each frequency band.
  • the method further includes:
  • the third information being used to indicate that the repeater supports resolving the conflict when there is a conflict in the forwarding types in the multiple frequency domain units, or,
  • Fourth information sent by the OAM device is received, where the fourth information is used to indicate that the repeater supports resolving conflicts when conflicts exist in forwarding types in the multiple frequency domain units.
  • the repeater reports that it supports conflict resolution, thereby ensuring the reliability of communication using multiple frequency domain units.
  • the first information is further used to indicate whether each frequency domain unit in the multiple frequency domain units supports resolving conflicts occurring in TDD information.
  • an embodiment of the present disclosure provides a communication method, the method being executed by a network device, the method comprising:
  • the first information is used to configure time division duplex (TDD) information for each frequency domain unit in a plurality of frequency domain units, wherein the TDD information is used to indicate a forwarding type of the repeater on different time domain units, wherein the forwarding type includes at least one of uplink forwarding, downlink forwarding or flexible forwarding.
  • TDD time division duplex
  • the method further includes:
  • the second information is sent to the repeater.
  • the second information includes at least one of the following:
  • the length of the frequency domain unit is the length of the frequency domain unit.
  • the method further includes:
  • the TDD information configured for the multiple frequency domain units does not conflict.
  • the repeater does not support simultaneous transmission and reception on different frequency bands, and the TDD information configured for the multiple frequency domain units does not conflict;
  • the repeater supports simultaneous transmission and reception on different frequency bands, and TDD information configured by multiple frequency domain units on the same frequency band does not conflict.
  • the method further includes:
  • the forwarding type corresponding to the conflicting time domain unit in the other frequency domain units is ignored; or, the forwarding type corresponding to the reference frequency domain unit is determined as the forwarding type corresponding to the conflicting time domain unit in the other frequency domain units.
  • the dynamically indicated TDD information does not conflict with the TDD information of the reference frequency domain unit.
  • the repeater supports semi-static configuration of TDD information.
  • the repeater supports dynamic indication of TDD information.
  • the reference frequency domain unit refers to the frequency domain unit with the smallest identifier among the multiple frequency domain units; or, the reference frequency domain unit refers to the frequency domain unit with the smallest identifier on each frequency band.
  • the repeater does not support simultaneous transmission and reception on different frequency bands
  • the reference frequency domain unit refers to the frequency domain unit with the smallest identifier among the multiple frequency domain units
  • the repeater supports simultaneous transmission and reception on different frequency bands, and the reference frequency domain unit refers to the frequency domain unit with the smallest identifier on each frequency band.
  • the method further includes:
  • the first information is also used to configure, for each of the multiple frequency domain units, whether to support resolving conflicts occurring in TDD information.
  • an embodiment of the present disclosure provides a communication method, the method comprising:
  • the network device sends first information to the repeater, where the first information is used to configure time division duplex (TDD) information for each frequency domain unit in the multiple frequency domain units, where the TDD information is used 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;
  • TDD time division duplex
  • the repeater receives first information sent by the network device.
  • an embodiment of the present disclosure provides a communication device, wherein the communication device includes at least one of a transceiver module and a processing module. wherein the above-mentioned repeater is used to execute the optional implementation method of the first aspect and the third aspect.
  • an embodiment of the present disclosure provides a communication device, which includes at least one of a transceiver module and a processing module; wherein the access network device is used to execute the optional implementation methods of the second and third aspects.
  • an embodiment of the present disclosure provides a communication device, including:
  • processors one or more processors
  • the communication device is used to execute the method described in any one of the first aspect and the third aspect.
  • an embodiment of the present disclosure provides a communication device, including:
  • processors one or more processors
  • the communication device is used to execute the method described in any one of the second aspect and the third aspect.
  • an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores first information, and when the first information is run on a communication device, the communication device executes a method as described in any one of the first aspect, the second aspect, and the third aspect.
  • an embodiment of the present disclosure proposes a program product.
  • the communication device executes any one of the methods described in the first aspect, the second aspect and the third aspect.
  • an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or the chip system comprises a processing circuit configured to execute any one of the methods described in the first aspect, the second aspect, and the third aspect.
  • the embodiments of the present disclosure provide a communication method, a device, and a storage medium.
  • the terms communication method, information communication method, indication method, etc. can be replaced with each other
  • the terms communication device, information processing device, indication device, etc. can be replaced with each other
  • the terms information processing system, communication system, etc. can be replaced with each other.
  • each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined.
  • a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged.
  • the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined, for example, some or all of the steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
  • elements expressed in the singular form can mean “one and only one", or “one or more”, “at least one”, etc.
  • the noun after the article can be understood as a singular expression. It can also be understood as a plural expression.
  • plurality refers to two or more.
  • the terms "at least one of”, “one or more”, “a plurality of”, “multiple”, etc. can be used interchangeably.
  • "at least one of A and B", “A and/or B", “A in one case, B in another case”, “in response to one case A, in response to another case B”, etc. may include the following technical solutions according to the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); 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 executed). When there are more branches such as A, B, C, etc., the above is also similar.
  • the recording method of "A or B” may include the following technical solutions according to the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed).
  • A A is executed independently of B
  • B B is executed independently of A
  • execution is selected from A and B (A and B are selectively executed).
  • prefixes such as “first” and “second” in the embodiments of the present disclosure are only used to distinguish different description objects, and do not constitute restrictions on the position, order, priority, quantity or content of the description objects.
  • the statement of the description object refers to the description in the context of the claims or embodiments, and should not constitute unnecessary restrictions due to the use of prefixes.
  • the description object is a "field”
  • the ordinal number before the "field” in the "first field” and the "second field” does not limit the position or order between the "fields”
  • the "first” and “second” do not limit whether the "fields” they modify are in the same message, nor do they limit the order of the "first field” and the "second field”.
  • the description object is a "level”
  • the ordinal number before the "level” in the “first level” and the “second level” does not limit the priority between the "levels”.
  • the number of description objects is not limited by the ordinal number, and can be one or more. Taking the "first device” as an example, the number of "devices” can be one or more.
  • the objects modified by different prefixes may be the same or different. For example, if the description object is "device”, then the “first device” and the “second device” may be the same device or different devices, and their types may be the same or different. For another example, if the description object is "information”, then the "first information” and the “second information” may be the same information or different information, and their contents may be the same or different.
  • “including A”, “comprising A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
  • time/frequency refers to the time domain and/or the frequency domain.
  • terms such as “greater than”, “greater than or equal to”, “not less than”, “more than”, “more than or equal to”, “not less than”, “higher than”, “higher than or equal to”, “not lower than”, and “above” can be replaced with each other, and terms such as “less than”, “less than or equal to”, “not greater than”, “less than”, “less than or equal to”, “no more than”, “lower than”, “lower than or equal to”, “not higher than”, and “below” can be replaced with each other.
  • devices and equipment may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as “equipment”, “device”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, “subject”, etc.
  • network can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.
  • an “access network device (AN device)” may also be referred to as a “radio access network device”.
  • the terms “radio access network device, RAN device”, “base station, BS”, “radio base station”, “fixed station”, in some embodiments, may also be understood as “node”, “access point”, “transmission point, TP”, “reception point, RP”, “transmission and/or reception point, TRP”, “panel”, “antenna panel”, “antenna array”, “cell”, “macro cell”, “small cell”, “femto cell”, “pico cell”, “sector”, “cell group”, “serving cell”, “carrier”, “component carrier”, “bandwidth part, BWP”, etc.
  • terminal or “terminal device” may be referred to as "user equipment (terminal)", “user terminal (user terminal)”, “mobile station (MS)”, “mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.
  • acquisition of data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
  • data, information, etc. may be obtained with the user's consent.
  • each element, each row, or each column in the table of the embodiments of the present disclosure may be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns may also be implemented as an independent embodiment.
  • FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , the method provided in the embodiment of the present disclosure can be applied to a communication system 100, and the communication system may include a terminal 101 and a network device 102. It should be noted that the communication system 100 may also include other devices, and the present disclosure does not limit the devices included in the communication system 100.
  • the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited to these.
  • a mobile phone a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device
  • the network device 102 may include at least one of an access network device and a core network device.
  • the access network device is, for example, a node or device that accesses a terminal to a wireless network.
  • the access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), and a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.
  • eNB evolved NodeB
  • ng-eNB next generation evolved NodeB
  • gNB next generation NodeB
  • NB no
  • the technical solution of the present disclosure may be applicable to the Open RAN architecture.
  • the interfaces between access network devices or within access network devices involved in the embodiments of the present disclosure may become internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.
  • the access network device may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU), wherein the CU may also be called a control unit (control unit).
  • the CU-DU structure may be used to split the protocol layer of the access network device, with some functions of the protocol layer being centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer being distributed in the DU, and the DU being centrally controlled by the CU, but not limited to this.
  • the core network device may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements.
  • the network element may be virtual or physical.
  • the core network may include, for example, at least one of the Evolved Packet Core (EPC), the 5G Core Network (5GCN), and the Next Generation Core (NGC).
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure.
  • a person of ordinary skill in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.
  • the following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or part of the subject, but are not limited thereto.
  • the subjects shown in FIG1 are examples, and the communication system may include all or part of the subjects in FIG1 , or may include other subjects other than FIG1 , and the number and form of the subjects are arbitrary, and the subjects may be physical or virtual, and the connection relationship between the subjects is an example, and the subjects may be connected or disconnected, and the connection may be in any manner, and may be a direct connection or an indirect connection, and may be a wired connection or a wireless connection.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-B LTE-Beyond
  • SUPER 3G IMT-Advanced
  • 4G the fourth generation mobile communication system
  • 5G 5G new radio
  • FAA Future Radio Access
  • RAT New Radio
  • NR New Radio
  • NX New radio access
  • the present invention relates to wireless communication systems such as LTE, Wi-Fi (Registered Trademark), GSM (Registered Trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (Registered Trademark)), IEEE 802.16 (WiMAX (Registered Trademark)), IEEE 802.20, Ultra-Wide Band (UWB), Bluetooth (Registered Trademark), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine-to-Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), systems using other communication methods, and next-generation systems expanded therefrom.
  • PLMN Public Land Mobile Network
  • D2D Device-to-Device
  • M2M Machine-to-Machine
  • IoT Internet of Things
  • V2X Vehicle-to-Everything
  • systems using other communication methods and next-generation systems expanded therefrom.
  • next-generation systems expanded therefrom
  • 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 via the repeater.
  • the repeater is an NCR, that is, data is transmitted between the terminal 101 and the network device 102 via the NCR.
  • the NCR can perform uplink forwarding and downlink forwarding.
  • the uplink forwarding refers to the terminal 101 sending uplink information to the NCR, and after the NCR receives the uplink information sent by the terminal 101, the uplink information is forwarded to the network device 102.
  • the downlink forwarding refers to the network device 102 sending downlink information to the NCR, and after the NCR receives the downlink information sent by the network device 102, the downlink information is forwarded to the terminal 101.
  • the NCR can also be set to flexible forwarding. Among them, the flexible forwarding means that both uplink forwarding and downlink forwarding can be performed.
  • the network device indicates through configuration whether the flexible forwarding of the NCR is uplink forwarding or downlink forwarding.
  • the NCR includes NCR-fwd (network controlled repeater forwarding) and NCR-mt (network controlled repeater mobile termination), wherein the NCR-fwd is used to forward information between the terminal and the network device, and the NCR-mt is at least used to receive instructions or configurations from the network device.
  • NCR-fwd network controlled repeater forwarding
  • NCR-mt network controlled repeater mobile termination
  • the NCR may be configured with multiple frequency domain units, and each frequency domain unit may be configured with TDD information.
  • the frequency domain unit may be a carrier, a BWP or other frequency domain units, which is not limited in the embodiments of the present disclosure.
  • the repeater in the embodiment of the present disclosure can also be understood as belonging to a network device, and it can be understood that the above network device 102 includes a first network device and a second network device. Among them, the first network device is similar to the network device 102 in the above embodiment. The second network device is similar to the repeater in the above embodiment.
  • the network device 102 further includes an OAM device, and the OAM device is used to configure OAM information through OAM.
  • the OAM information is used to carry information for configuring the frequency domain unit.
  • the OAM information may also carry information for configuring the frequency domain unit, which is not limited in the embodiment of the present disclosure.
  • the OAM device in the embodiment of the present disclosure may also be referred to as a third network device, which is similar to the OAM device.
  • FIG2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2 , the embodiment of the present disclosure relates to a communication method, and the method includes:
  • Step S2101 The repeater sends third information to the network device.
  • the network device receives the third information sent by the repeater. In some embodiments, the repeater sends the third information. In some embodiments, the network device receives the third information.
  • the third information is used to indicate that the repeater supports resolving conflicts when conflicts exist in forwarding types in multiple frequency domain units. In some embodiments, the third information is used to indicate that the repeater supports resolving conflicts when conflicts exist in multiple frequency domain units.
  • the conflict in forwarding types among multiple frequency domain units means that at least one frequency domain unit is for uplink forwarding and at least one frequency domain unit is for downlink forwarding.
  • the repeater supports conflict resolution when conflicts exist among multiple frequency domain units, which means eliminating the situation where at least one frequency domain unit is for uplink forwarding and at least one frequency domain unit is for downlink forwarding.
  • the name of the third information is not limited, and it can be, for example, capability information, reporting information, indication information, capability indication information, etc.
  • the embodiment of the present disclosure is described by taking the example of a repeater sending the third information to a network device.
  • the repeater may also be configured by an OAM device.
  • the repeater receives fourth information sent by the OAM device, and the fourth information is used to indicate that the repeater supports resolving the conflict when there is a conflict in the forwarding types in the multiple frequency domain units.
  • the fourth information is similar to the third information in the above embodiment and will not be repeated here.
  • step S2101 is an optional step. In another embodiment, step S2101 may not be performed.
  • Step S2102 The network device sends second information to the repeater.
  • the network device sends the second information. In some embodiments, the repeater receives the second information. In some embodiments, the repeater receives the second information sent by the network device.
  • the second information is used to configure multiple frequency domain units.
  • the network device configures multiple frequency domain units for the repeater, and the subsequent repeater can communicate with the network device through the configured multiple frequency domain units.
  • the frequency domain unit can be FR1 (Frequency range 1), FR2 (Frequency range 2), band, BWP (Carrier Bandwith Part), carrier, RB (Radio Bearer), etc.
  • the second information includes at least one of the following:
  • the length of the frequency domain unit is configured by a network device.
  • the frequency domain unit is an RB, and it can be understood that the starting position of the frequency domain unit is the starting RB, and the length of the frequency domain unit is the RB length.
  • the second information reuses the existing BWP configuration mode. If the frequency domain unit is a BWP, the second information is used to configure multiple BWPs.
  • the starting position of the frequency domain unit is the starting position of the BWP.
  • the length of the frequency domain unit is the length of the BWP.
  • the second information is locationAndBandwidth.
  • the second information reuses an existing CC (component carrier) configuration method. If the frequency domain unit is a CC, the second information is used to configure multiple CCs.
  • 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.
  • the second information may also be a newly defined frequency band configuration.
  • the starting RB in the second information may be an ARFCN (absolute radio-frequency channel number).
  • the starting RB may be an offset value relative to a specific known frequency domain position.
  • the offset value relative to a specific known frequency domain position is the minimum offset value relative to the SSB (Synchronization Signal/PBCH).
  • it may be an offset value relative to the minimum RB of the serving cell.
  • the signaling used is different for different network devices.
  • the second information is configured through air interface signaling.
  • the air interface signaling is RRC signaling.
  • the network device in the embodiment of the present disclosure is an OAM device, the second information is configured through OAM.
  • the embodiment of the present disclosure is described by taking the example of a network device sending the second information to a repeater.
  • the second information may also be sent by an OAM device.
  • the OAM device sends the second information to the repeater.
  • the repeater receives the second information sent by the OAM device.
  • the network device receives second information sent by the OAM device through OAM.
  • Step S2103 The repeater does not expect that TDD information configured by multiple frequency domain units will conflict.
  • the conflict of TDD information configured by the multiple frequency domain units means that at least one frequency domain unit is for uplink forwarding and at least one frequency domain unit is for downlink forwarding.
  • the repeater cannot operate normally, so the repeater does not expect the TDD information configured by multiple frequency domain units to conflict.
  • the repeater does not expect that TDD information configured by multiple frequency domain units will conflict with each other, which can also be understood as the repeater does not expect that TDD information configured by multiple frequency domain units will conflict with each other.
  • the repeater does not expect the TDD information configured by multiple frequency domain units to conflict, and correspondingly, the network device does not configure conflicting TDD information for multiple frequency domain units. Alternatively, it can be said that the TDD information configured by the network device for multiple frequency domain units does not conflict.
  • the repeater may support simultaneous transmission and reception on different frequency bands based on different capabilities.
  • the following describes the configuration of TDD information according to different repeaters.
  • the repeater does not support simultaneous transmission and reception on different frequency bands, and the repeater does not expect TDD information configured by multiple frequency domain units to conflict.
  • the repeater since it does not support simultaneous transmission and reception on different frequency bands, if the TDD information configured by multiple frequency bands conflicts, the repeater cannot perform operations normally, so the repeater does not expect the TDD information configured by multiple frequency domain units to conflict.
  • the network device does not configure conflicting TDD information for multiple frequency domain units.
  • the TDD information configured by the network device for multiple frequency domain units does not conflict.
  • the repeater supports simultaneous transmission and reception on different frequency bands, and the repeater does not expect TDD information configured by multiple frequency domain units on the same frequency band to conflict.
  • the repeater since it supports simultaneous transmission and reception on different frequency bands, if the TDD information between multiple frequency bands on the same frequency band conflicts, the repeater cannot perform normal operations on the frequency band, so the repeater does not expect the TDD information configured by multiple frequency domain units on the same frequency band to conflict.
  • the network device does not configure conflicting TDD information for multiple frequency domain units on the same frequency band. In other words, the TDD information configured by the network device for multiple frequency domain units on the same frequency band does not conflict.
  • the repeater supports semi-static configuration of TDD information. In some embodiments, the repeater in the above embodiments does not expect that the configured TDD information will conflict, and the TDD information in the configuration is all semi-statically configured.
  • the repeater does not expect the dynamically indicated TDD information to conflict with the TDD information of the reference frequency domain unit. In some embodiments, the repeater in the above embodiments does not expect that all TDD information in the configured TDD information conflict is dynamically indicated.
  • dynamic indication is indicated using DCI format 2-0.
  • step S2101 is an optional step. In another embodiment, step S2101 may not be performed.
  • Step S2104 The network device sends first information to the repeater.
  • the network device sends the first information. In some embodiments, the repeater receives the first information. In the embodiment, the repeater receives the first information sent by the network device.
  • the first information is used to configure TDD information for each frequency domain unit in multiple frequency domain units, and the TDD information is used to indicate the forwarding type of the repeater on different time domain units, and the forwarding type includes at least one of uplink forwarding, downlink forwarding or flexible forwarding.
  • a reference frequency domain unit among multiple frequency domain units is determined to conflict with a time domain unit among other frequency domain units except the reference frequency domain unit among the multiple frequency domain units, and the forwarding type corresponding to the conflicting time domain unit among other frequency domain units is ignored; or, the forwarding type corresponding to the conflicting time domain unit among other frequency domain units is determined to be the forwarding type corresponding to the reference frequency domain unit.
  • the frequency band includes multiple frequency domain units.
  • conflicting frequency domain units may also exist.
  • the repeater needs to determine the conflicting frequency domain unit, and then the repeater decides the forwarding type of the conflicting frequency domain unit.
  • the repeater first determines a reference frequency domain unit from multiple frequency domain units, then determines a time domain unit that conflicts with the reference frequency domain unit, and then ignores the forwarding type corresponding to the time domain unit that conflicts with other frequency domain units; or, awards the forwarding type corresponding to the time domain unit that conflicts with other frequency domain units as the forwarding type corresponding to the reference frequency domain unit.
  • the reference frequency domain unit refers to a frequency domain unit with the smallest identifier among multiple frequency domain units; or, the reference frequency domain unit refers to a frequency domain unit with the smallest identifier on each frequency band.
  • the reference frequency domain unit refers to the frequency domain unit with the smallest identifier among the multiple frequency domain units.
  • the reference frequency domain unit refers to the frequency domain unit with the smallest identifier on each frequency band.
  • the repeater does not support simultaneous transmission and reception on different frequency bands
  • the reference frequency domain unit refers to a frequency domain unit with a smallest identifier among multiple frequency domain units.
  • the repeater supports simultaneous transmission and reception on different frequency bands
  • the reference frequency domain unit refers to a frequency domain unit with a minimum identifier on each frequency band.
  • the repeater supports semi-static configuration of TDD information. In some embodiments, the repeater supports dynamic indication of TDD information.
  • the first information is further used to configure whether to support TDD conflict resolution for each frequency domain unit in the plurality of frequency domain units.
  • each frequency domain unit also has a function of whether to support resolving conflicts occurring in TDD information. That is to say, if the frequency domain unit does not support resolving conflicts occurring in TDD information, the frequency domain unit does not participate in the above steps. If the frequency domain unit supports resolving conflicts occurring in TDD information, the frequency domain unit participates in the above steps.
  • the embodiment of the present disclosure is described by taking the first information as an example of whether each frequency domain unit in a plurality of frequency domain units is configured to support TDD conflict resolution.
  • other information may also be used to configure whether each frequency domain unit in a plurality of frequency domain units is configured to support resolution of conflicts occurring in TDD information.
  • the repeater receives fifth information, which is used to configure whether each frequency domain unit in a plurality of frequency domain units is configured to support resolution of conflicts occurring in TDD information.
  • the names of information, etc. are not limited to the names recorded in the embodiments, and terms such as “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”, “domain”, “field”, “symbol”, “symbol”, “code element”, “codebook”, “codeword”, “codepoint”, “bit”, “data”, “program”, and “chip” can be used interchangeably.
  • terms such as “uplink”, “uplink”, “physical uplink” can be interchangeable, and terms such as “downlink”, “downlink”, “physical downlink” can be interchangeable, and terms such as “side”, “sidelink”, “side communication”, “sidelink communication”, “direct connection”, “direct link”, “direct communication”, “direct link communication” can be interchangeable.
  • obtain can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from high levels, obtaining by self-processing, autonomous implementation, etc.
  • terms such as “moment”, “time point”, “time”, and “time position” can be interchangeable, and terms such as “duration”, “period”, “time window”, “window”, and “time” can be interchangeable.
  • terms such as “certain”, “preset”, “preset”, “set”, “indicated”, “some”, “any”, and “first” can be interchangeable, and "specific A”, “preset A”, “preset A”, “set A”, “indicated A”, “some A”, “any A”, and “first A” can be interpreted as A pre-defined in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., and can also be interpreted as specific A, some A, any A, or first A, etc., but is not limited to this.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2104.
  • 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 independent embodiments
  • step S2103 and step S2104 may be implemented as independent embodiments
  • step S2101, step S2102, and step S2103 may be implemented as independent embodiments
  • step S2101, step S2102, and step S2104 may be implemented as independent embodiments, but are not limited thereto.
  • step S2101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2103 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2104 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2101 and step S2102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2101 and step S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2102 and step S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S2101, step S2102, and step S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • FIG3A is a flow chart of a communication method according to an embodiment of the present disclosure, which is applied to a repeater. As shown in FIG3A , an embodiment of the present disclosure relates to a communication method, and the method includes:
  • Step S3101 The repeater sends third information to the network device.
  • step S3101 can refer to the optional implementation of step S2101 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • Step S3102 The repeater does not expect TDD information configured by multiple frequency domain units to conflict.
  • step S3102 can refer to the optional implementation of step S2103 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the communication method involved in the embodiment of the present disclosure may include at least one of step S3101 to step S3102.
  • step S3101 may be implemented as an independent embodiment
  • step S3102 may be implemented as an independent embodiment, or at least two steps may be combined, but not limited thereto.
  • step S3101 is optional
  • step S3102 is optional
  • one or more of these steps may be omitted or replaced in different embodiments, but the present invention is not limited thereto.
  • FIG3B is a flow chart of a communication method according to an embodiment of the present disclosure, which is applied to a repeater. As shown in FIG3B , an embodiment of the present disclosure relates to a communication method, and the method includes:
  • Step S3201 The repeater receives first information sent by a network device.
  • step S3201 can refer to step S2104 of FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.
  • FIG4A is a flow chart of a communication method according to an embodiment of the present disclosure, which is applied to a network device. As shown in FIG4A , an embodiment of the present disclosure relates to a communication method, and the method includes:
  • Step S4101 The network device sends second information to the repeater.
  • step S4101 can refer to step S2102 of FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.
  • Step S4102 The network device sends first information to the repeater.
  • step S4102 can refer to step S2104 of FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.
  • FIG4B is a flow chart of a communication method according to an embodiment of the present disclosure, which is applied to a network device. As shown in FIG4B , an embodiment of the present disclosure relates to a communication method, and the method includes:
  • Step S4201 The network device sends first information to the repeater.
  • step S4201 can refer to step S2104 of FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the method further comprises:
  • the second information is sent to the repeater.
  • the second information includes at least one of the following:
  • the length of the frequency domain unit is the length of the frequency domain unit.
  • the method further comprises:
  • the TDD information configured for the multiple frequency domain units does not conflict.
  • the repeater does not support simultaneous transmission and reception on different frequency bands, and the TDD information configured for the multiple frequency domain units does not conflict; or,
  • the repeater supports simultaneous transmission and reception on different frequency bands, and TDD information configured by multiple frequency domain units on the same frequency band does not conflict.
  • the method further comprises:
  • the forwarding type corresponding to the conflicting time domain unit in the other frequency domain units is ignored; or, the forwarding type corresponding to the reference frequency domain unit is determined as the forwarding type corresponding to the conflicting time domain unit in the other frequency domain units.
  • the repeater supports semi-static configuration of TDD information.
  • the dynamically indicated TDD information does not conflict with the TDD information of the reference frequency domain unit.
  • the repeater supports dynamic indication of TDD information.
  • the reference frequency domain unit refers to a frequency domain unit with a smallest identifier among the multiple frequency domain units; or, the reference frequency domain unit refers to a frequency domain unit with a smallest identifier on each frequency band.
  • the repeater does not support simultaneous transmission and reception on different frequency bands, and the reference frequency domain unit refers to the frequency domain unit with the smallest identifier among the multiple frequency domain units;
  • the repeater supports simultaneous transmission and reception on different frequency bands, and the reference frequency domain unit refers to the frequency domain unit with the smallest identifier on each frequency band.
  • the method further comprises:
  • the first information is further used to configure, for each of the multiple frequency domain units, whether to support resolving conflicts occurring in TDD information.
  • FIG5 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure relates to a communication method, and the method includes:
  • Step S5101 The network device sends first information to the repeater.
  • the first information is used to configure time division duplex TDD information for each frequency domain unit in multiple frequency domain units, and the TDD information is used to indicate the forwarding type of the repeater on different time domain units, and the forwarding type includes at least one of uplink forwarding, downlink forwarding or flexible forwarding.
  • Step S5102 The repeater receives the first information sent by the network device.
  • step S5101 can refer to step S2104 in FIG. 2 , step S4102 in FIG. 4A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.
  • step S5102 can refer to step S2104 of FIG. 2 , step S4102 of FIG. 4A , and other related parts of the embodiments involved in FIG. 2 and FIG. 4A , which will not be described in detail here.
  • the above method may include the method of the above-mentioned communication system side, repeater side, network device side, etc., which will not be repeated here.
  • FIG6 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG6 , the embodiment of the present disclosure relates to a communication method, and the method includes:
  • Step S6101 The base station configures a forwarding frequency domain unit for the NCR.
  • the frequency domain unit may be configured to the NCR-MT via RRC signaling.
  • the content may be BWP, CC, and the configuration method may reuse the method in the existing protocol, such as
  • a new frequency band configuration is defined, such as FwdFreq#1, FwdFreq#2, etc.
  • the configuration parameters include at least the starting RB and RB length, where:
  • the starting RB can be absolute radio-frequency channel number (ARFCN)
  • ⁇ Another example is the offset relative to the minimum RB of the serving cell
  • the base station configures TDD information for each frequency domain unit of the NCR, wherein uplink forwarding (such as U) indicates that The UE's signal is forwarded to the base station.
  • Downlink forwarding (such as D) means forwarding the base station's signal to the UE. If not indicated, it is considered flexible.
  • the TDD configuration is semi-static and configured through RRC signaling, such as TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated; or the TDD configuration is dynamic, that is, based on the RRC configuration, for flexible time domain units, such as symbol or slot, its TDD, that is, uplink or downlink direction, can be indicated through dynamic signaling.
  • a method for avoiding conflicts on multiple frequency domain units (if the NCR only supports semi-static TDD configuration, the NCR does not forward on time domain units that do not indicate TDD)
  • conflicts are avoided during configuration: the NCR does not want conflicts to occur between TDDs configured for different frequency domain units in the base station.
  • the NCR does not want the TDD configuration of the frequency domain unit #1-1 to conflict with the TDD configuration of the frequency domain unit #1-2; if the NCR has the capability to transmit and receive simultaneously on different frequency bands, the NCR does not want the TDD configuration of the frequency domain unit #1-1 to conflict with the TDD configuration of the frequency domain unit #1-2 on the same frequency band.
  • the NCR determines whether the conflicting time domain unit is forwarded uplink or downlink according to the TDD configuration of the reference frequency domain unit.
  • the behavior of the NCR is as follows:
  • ⁇ Option 1 Ignore the instruction or consider the domain unit to be flexible during the conflict, and do not forward the message at this time;
  • ⁇ Option 2 Use the TDD direction of the reference cell for forwarding
  • a method for avoiding conflicts on multiple frequency domain units (if NCR also supports dynamic TDD)
  • NCR does not want conflicts to occur when the base station is configured as TDD with semi-static configuration in different frequency domain units.
  • the NCR does not want the TDD configuration of the frequency domain unit #1-1 to conflict with the TDD configuration of the frequency domain unit #1-2; if the NCR has the capability to transmit and receive simultaneously on different frequency bands, the NCR does not want the TDD configuration of the frequency domain unit #1-1 to conflict with the TDD configuration of the frequency domain unit #1-2 on the same frequency band.
  • the NCR does not want the dynamically indicated TDD to conflict with the TDD of the reference cell; in this case, the NCR believes that the conflict will not occur and the base station will not be configured in this way.
  • the NCR determines whether the conflicting time domain unit is an uplink forwarding or a downlink forwarding according to the TDD configuration of the reference frequency domain unit.
  • the behavior of NCR is as follows:
  • the indication is ignored and the domain unit does not forward at this time
  • forwarding is performed using the TDD direction of the reference cell
  • the NCR determines the reference frequency domain unit according to a predefined rule:
  • the frequency domain unit ID is the forwarding frequency domain unit with the smallest index configured by the base station for the NCR, or
  • the frequency domain unit ID is the forwarding frequency domain unit with the smallest index on each frequency band.
  • the reference frequency domain unit is option 1; if the NCR has the capability to transmit and receive simultaneously on different frequency bands, the reference frequency domain unit is option 2.
  • the NCR reports a capability, where the capability indicates that the NCR supports handling conflicts when conflicts occur in a forwarding direction (uplink or downlink).
  • the base station configures whether to enable TDD conflict resolution for the forwarding frequency domain unit of the NCR, and the configuration is effective for a specific forwarding frequency domain unit.
  • the UE reports the conflict resolution capability
  • the base station configures serving cell #1 and serving cell #2 for NCR for forwarding, and both cells enable the conflict resolution mechanism.
  • the NCR uses the cell with the smallest cell index on the frequency band as the reference cell. Assume that the TDD semi-static configuration of the reference cell is DDDSSUUS, and the TDD semi-static configuration of another cell is DDSSUSSD; at this time, the third time domain unit of the other cell indicated by dynamic scheduling is U, then the NCR ignores the indication and does not forward the time domain unit at this time.
  • the base station configures multiple cells for the NCR, and each cell is configured separately through TDD-UL-DL-ConfigCommon.
  • the NCR does not want the TDD configurations of these cells to conflict, that is, the base station should avoid conflicts during configuration.
  • some or all of the steps and their optional implementation methods can be arbitrarily combined with some or all of the steps in other embodiments, and can also be arbitrarily combined with the optional implementation methods of other embodiments.
  • the embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a device is proposed, the above device includes a unit or module for implementing each step performed by the repeater in any of the above methods.
  • a device is also proposed, including a unit or module for implementing each step performed by a network device (such as an access network device, a core network function node, a core network device, etc.) in any of the above methods.
  • a network device such as an access network device, a core network function node, a core network device, etc.
  • the division of the units or modules in the above device is only a division of logical functions, and in actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated.
  • the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory.
  • the processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory inside the device or a memory outside the device.
  • CPU central processing unit
  • microprocessor a microprocessor
  • the units or modules in the device may be implemented in the form of hardware circuits, and the functions of some or all of the units or modules may be realized by designing the hardware circuits.
  • the hardware circuits may be understood as one or more processors.
  • the hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are realized by designing the logical relationship of the components within the circuit.
  • the hardware circuit may be implemented by a programmable logic device (PLD).
  • PLD programmable logic device
  • FPGA field programmable gate array
  • it may include a large number of logic gate circuits, and the connection relationship between the logic gate circuits may be configured by a configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices may be implemented entirely by the processor calling software, or entirely by hardware circuits, or partially by The processor calls the software, and the rest is implemented in the form of hardware circuits.
  • the processor is a circuit with signal processing capability.
  • the processor may be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which may be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the above hardware circuit may be fixed or reconfigurable, such as a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the process of the processor loading a configuration document to implement the hardware circuit configuration may be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules.
  • it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as Neural Network Processing Unit (NPU), Tensor Processing Unit (TPU), Deep Learning Processing Unit (DPU), etc.
  • ASIC Neural Network Processing Unit
  • NPU Neural Network Processing Unit
  • TPU Tensor Processing Unit
  • DPU Deep Learning Processing Unit
  • FIG7A is a schematic diagram of the structure of a communication device proposed in an embodiment of the present disclosure.
  • the communication device 7100 may include: at least one of a transceiver module 7101, a processing module 7102, etc.
  • the transceiver module 7101 is used to receive a first information
  • the first information is used to configure time division duplex TDD information for each frequency domain unit in a plurality of frequency domain units
  • the TDD information is used to indicate the forwarding type of the repeater on different time domain units
  • the forwarding type includes at least one of uplink forwarding, downlink forwarding or flexible forwarding.
  • the transceiver module 7101 is used to execute at least one of the communication steps such as sending and/or receiving performed by the repeater in any of the above methods (such as step S2101 but not limited thereto), which will not be repeated here.
  • the processing module is used to execute at least one of the other steps performed by the repeater in any of the above methods, which will not be repeated here.
  • the processing module 7102 is used to execute at least one of the communication steps such as processing performed by the repeater in any of the above methods, which will not be repeated here.
  • FIG7B is a schematic diagram of the structure of the communication device proposed in an embodiment of the present disclosure.
  • the communication device 7200 may include: at least one of a transceiver module 7201, a processing module 7202, etc.
  • the transceiver module 7201 is used to send a first information
  • the first information is used to configure time division duplex TDD information for each frequency domain unit in a plurality of frequency domain units
  • the TDD information is used to indicate the forwarding type of the repeater on different time domain units, and the forwarding type includes at least one of uplink forwarding, downlink forwarding or flexible forwarding.
  • the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and/or receiving (such as step S2102 but not limited thereto) performed by the network device in any of the above methods, which will not be repeated here.
  • the processing module 7202 is used to execute at least one of the communication steps such as processing performed by the network device in any of the above methods, which will not be repeated here.
  • the transceiver module may include a sending module and/or a receiving module, and the sending module and the receiving module may be separate or integrated.
  • the transceiver module may be interchangeable with the transceiver.
  • the processing module can be a module or include multiple submodules.
  • the multiple submodules respectively execute all or part of the steps required to be executed by the processing module.
  • the processing module can be replaced with the processor.
  • FIG8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure.
  • the communication device 8100 may be a network device (such as an access network device, a core network device, etc.), or a repeater, or a chip that supports the network device to implement any of the above methods.
  • the chip system, or processor, etc. may also be a chip, chip system, or processor 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 embodiment, and the details may refer to the description in the above method embodiment.
  • the communication device 8100 further includes one or more memories 8102 for storing instructions.
  • the memory 8102 may also be outside the communication device 8100.
  • the communication device 8100 further includes one or more transceivers 8103.
  • the transceiver 8103 performs at least one of the communication steps such as sending and/or receiving in the above method (for example, step S2101, step S2102, step S2103, step S2104, but not limited thereto).
  • the transceiver may include a receiver and/or a transmitter, and the receiver and the transmitter may be separate or integrated.
  • the terms such as transceiver, transceiver unit, transceiver, transceiver circuit, etc. may be replaced with each other, the terms such as transmitter, transmission unit, transmitter, transmission circuit, etc. may be replaced with each other, and the terms such as receiver, receiving unit, receiver, receiving circuit, etc. may be replaced with each other.
  • the communication device 8100 may include one or more interface circuits 8104.
  • the interface circuit 8104 is connected to the memory 8102, and the interface circuit 8104 may be used to receive signals from the memory 8102 or other devices, and may be used to send signals to the memory 8102 or other devices.
  • the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.
  • the communication device 8100 described in the above embodiments 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 an independent device or may be part of a larger device.
  • the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a repeater, an intelligent repeater, a cellular phone, a wireless device, a handheld device, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.
  • FIG. 8B is a schematic diagram of the structure of a chip 8200 provided in an embodiment of the present disclosure.
  • the communication device 8100 may be a chip or a chip system
  • the chip 8200 includes one or more processors 8201, and the chip 8200 is used to execute any of the above methods.
  • the chip 8200 further includes one or more interface circuits 8202.
  • the interface circuit 8202 is connected to the memory 8203.
  • the interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and the interface circuit 8202 can be used to send signals to the memory 8203 or other devices.
  • the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the processor 8201.
  • the interface circuit 8202 performs at least one of the communication steps of sending and/or receiving in the above method.
  • Processor 8201 performs at least one of the other steps.
  • interface circuit interface circuit
  • transceiver pin transceiver
  • the chip 8200 further includes one or more memories 8203 for storing instructions.
  • the memory 8203 may be outside the chip 8200.
  • the present disclosure also proposes a storage medium, on which instructions are stored, and when the instructions are executed on the communication device 8100, the communication device 8100 executes any of the above methods.
  • the storage medium is an electronic storage medium.
  • the storage medium is a computer-readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices.
  • the storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a temporary storage medium.
  • the present disclosure also proposes a program product, which, when executed by the communication device 8100, enables the communication device 8100 to execute any of the above methods.
  • the program product is a computer program product.
  • the present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to execute any one of the above methods.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande se rapporte à un procédé et à un appareil de communication, ainsi qu'à un support de stockage. Le procédé consiste : à recevoir des premières informations, les premières informations étant utilisées pour configurer des informations TDD pour chaque unité de domaine fréquentiel parmi une pluralité d'unités de domaine fréquentiel, les informations TDD étant utilisées pour indiquer un type de transfert d'un répéteur sur une unité de domaine temporel différente, et le type de transfert comprenant un transfert de liaison montante et/ou un transfert de liaison descendante et/ou un transfert flexible. La présente demande résout le problème selon lequel il est impossible de configurer des informations TDD pour chaque unité de domaine fréquentiel d'un répéteur, et fournit une solution pour configurer des informations TDD pour des unités de domaine fréquentiel ; par la configuration d'un type de transfert pour une unité de domaine temporel de chaque unité de domaine fréquentiel parmi une pluralité d'unités de domaine fréquentiel, la précision du type de transfert configuré de l'unité de domaine fréquentiel est améliorée, et la fiabilité de communication par des unités de domaine fréquentiel pour lesquelles des informations TDD ont été configurées est assurée.
PCT/CN2023/125497 2023-10-19 2023-10-19 Procédé et appareil de communication, et support de stockage Pending WO2025081433A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202380011784.5A CN117693958A (zh) 2023-10-19 2023-10-19 通信方法、装置以及存储介质
PCT/CN2023/125497 WO2025081433A1 (fr) 2023-10-19 2023-10-19 Procédé et appareil de communication, et support de stockage

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/125497 WO2025081433A1 (fr) 2023-10-19 2023-10-19 Procédé et appareil de communication, et support de stockage

Publications (1)

Publication Number Publication Date
WO2025081433A1 true WO2025081433A1 (fr) 2025-04-24

Family

ID=90130586

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/125497 Pending WO2025081433A1 (fr) 2023-10-19 2023-10-19 Procédé et appareil de communication, et support de stockage

Country Status (2)

Country Link
CN (1) CN117693958A (fr)
WO (1) WO2025081433A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116636157A (zh) * 2020-12-04 2023-08-22 高通股份有限公司 用于在无线通信中将中继器与多个上游节点一起使用的技术
US20230268982A1 (en) * 2022-04-29 2023-08-24 Intel Corporation Network controlled repeater
CN116711388A (zh) * 2020-12-28 2023-09-05 华为技术有限公司 一种中继通信方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116636157A (zh) * 2020-12-04 2023-08-22 高通股份有限公司 用于在无线通信中将中继器与多个上游节点一起使用的技术
CN116711388A (zh) * 2020-12-28 2023-09-05 华为技术有限公司 一种中继通信方法及装置
US20230268982A1 (en) * 2022-04-29 2023-08-24 Intel Corporation Network controlled repeater

Also Published As

Publication number Publication date
CN117693958A (zh) 2024-03-12

Similar Documents

Publication Publication Date Title
WO2025000303A1 (fr) Procédé d'indication d'informations, terminal, dispositif de réseau, système de communication et support de stockage
WO2025086179A1 (fr) Procédé de transmission d'informations, appareil, dispositif de communication, système de communication et support de stockage
WO2025059954A1 (fr) Procédé de communication, terminal, dispositif réseau et système de communication
CN117337607A (zh) 频段切换方法、终端、网络设备以及存储介质
WO2025059951A1 (fr) Procédé de communication, terminal, dispositif de réseau et support de stockage
WO2025000565A1 (fr) Procédé de demande de rapport, dispositif de communication et support de stockage
WO2025065642A1 (fr) Procédés de communication de relais, dispositifs de relais, terminaux, système de communication et support de stockage
WO2025050326A1 (fr) Procédé de commutation de communication, terminal, dispositif de réseau et support de stockage
WO2025035323A1 (fr) Procédé de mesure de positionnement, terminal et dispositif de réseau
WO2025081433A1 (fr) Procédé et appareil de communication, et support de stockage
WO2025020085A1 (fr) Procédé de communication, répéteur, dispositif de réseau et support de stockage
WO2025020083A1 (fr) Procédé de détermination de faisceau, répéteur, dispositif de réseau et support de stockage
WO2025091418A1 (fr) Procédé de récupération d'occupation de canal, terminal et support de stockage
WO2025081460A1 (fr) Procédé d'indication, terminal, dispositif de réseau et support de stockage
WO2025145400A1 (fr) Procédé et appareil de communication, et support de stockage
WO2025000306A1 (fr) Procédé d'indication d'informations, terminal, dispositif de réseau, système de communication et support de stockage
WO2025118248A1 (fr) Procédé de traitement, appareil et support de stockage
WO2025111759A1 (fr) Procédés et appareils d'indication, et support de stockage
WO2025102326A1 (fr) Procédé d'envoi de signal, procédé de réception de signal, terminal, système de communication et support de stockage
WO2025166739A1 (fr) Procédé et appareil de détermination de nombre de répétitions et support de stockage
WO2025111947A1 (fr) Procédés de gestion de cycle de vie, procédé d'envoi d'indication, terminaux et dispositifs de réseau
WO2025025026A1 (fr) Procédé de traitement d'informations, dispositif de réseau, terminal, système de communication, et support de stockage
WO2025091408A1 (fr) Procédé d'accès à un canal, procédé de communication, terminal et support de stockage
WO2025111805A1 (fr) Procédé d'envoi de signal de référence périodique de liaison latérale, terminal et support de stockage
WO2025123366A1 (fr) Procédé et appareil de communication, et support de stockage

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23955759

Country of ref document: EP

Kind code of ref document: A1