Communication method and device

Abstract

The invention discloses a communication method and device, and the method comprises the steps: determining a pattern of a time domain resource occupied by an uplink channel and a downlink channel corresponding to a terminal through agreement based on a protocol or first information; wherein the first information is sent by a network device, and the uplink channel and the downlink channel are located in a time division duplex (TDD) frame; according to the invention, the terminal can determine a new time division duplex (TDD) frame structure, the system communication efficiency is effectively improved, the compatibility of the scheme is improved, and the channel performance is ensured.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0002] With the continuous development of communication technology, non-terrestrial network (NTN) has gradually become one of the research hotspots. NTN can build wireless communication systems using non-terrestrial infrastructure such as aerial platforms or satellites in orbit. It can effectively enhance the coverage of the network and can also be used for emergency communications. In addition, NTN can also play a role in the development of the Internet of Things (IoT) and has scalability. Summary of the invention

[0003] The embodiments of the present disclosure provide a communication method and device.

[0004] A first aspect of the present disclosure provides a communication method, which is executed by a terminal and includes:

[0005] Determine, based on the agreement of the protocol or the first information, a pattern of time domain resources occupied by an uplink channel and a downlink channel corresponding to the terminal;

[0006] The first information is sent by a network device, and the uplink channel and the downlink channel are located in a time division duplex TDD frame.

[0007] A second aspect of the present disclosure provides a communication method, which is performed by a network device and includes:

[0008] Sending first information to a terminal, where the first information is used by the terminal to determine a pattern of time domain resources occupied by corresponding uplink channels and downlink channels;

[0009] The uplink channel and the downlink channel are located in a time division duplex (TDD) frame.

[0010] A third aspect of the present disclosure provides a terminal, the terminal comprising:

[0011] A processing module, configured to determine a pattern of time domain resources occupied by an uplink channel and a downlink channel corresponding to the terminal based on a protocol agreement or the first information;

[0012] The first information is sent by a network device, and the uplink channel and the downlink channel are located in a time division duplex TDD frame.

[0013] A fourth aspect of the present disclosure provides a network device, the network device comprising:

[0014] A transceiver module, configured to send first information to a terminal, wherein the first information is used by the terminal to determine a pattern of time domain resources occupied by corresponding uplink channels and downlink channels;

[0015] The uplink channel and the downlink channel are located in a time division duplex (TDD) frame.

[0016] The solution proposed in the embodiment of the present disclosure determines the pattern of time domain resources occupied by the uplink channel and the downlink channel corresponding to the terminal through a protocol-based agreement or first information; wherein the first information is sent by a network device, and the uplink channel and the downlink channel are located in a time division duplex TDD frame; so that the terminal can determine a new time division duplex TDD frame structure, effectively improving the system communication efficiency, improving the compatibility of the solution, and ensuring channel performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0018] Figure 1A is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0019] Figure 2A is an interactive schematic diagram of a communication method provided by an embodiment of the present disclosure;

[0020] Figure 2B-2K is a schematic diagram of a TDD frame structure provided by an embodiment of the present disclosure;

[0021] Figure 3A-3B It is a flowchart of a communication method provided by an embodiment of the present disclosure;

[0022] Figure 4A It is a flowchart of a communication method provided by an embodiment of the present disclosure;

[0023] Figure 5 It is a flow chart of a communication method provided by an embodiment of the present disclosure;

[0024] Fig. 6A is a schematic diagram of the structure of a terminal provided by an embodiment of the present disclosure;

[0025] Figure 6B is a structural diagram of a network device provided by an embodiment of the present disclosure;

[0026] Fig. 7A is a structural diagram of a communication device provided by an embodiment of the present disclosure;

[0027] Figure 7B It is a schematic diagram of the structure of a chip provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0028] The embodiments of the present disclosure provide a communication method and device.

[0029] In a first aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0030] Determine, based on the agreement of the protocol or the first information, a pattern of time domain resources occupied by the uplink channel and the downlink channel corresponding to the terminal;

[0031] The first information is sent by a network device, and the uplink channel and the downlink channel are located in a time division duplex (TDD) frame.

[0032] In the above embodiment, the terminal is enabled to determine a new time division duplex TDD frame structure, which effectively improves the system communication efficiency, improves the compatibility of the solution, and ensures the channel performance.

[0033] In combination with some embodiments of the first aspect, in some embodiments, the first information is used to indicate a pattern of at least one predefined time domain resource.

[0034] In the above embodiment, at least one pattern agreed upon by the indication protocol can be configured through the signaling sent by the network device, which effectively improves the flexibility of the solution.

[0035] In combination with some embodiments of the first aspect, in some embodiments, the first information includes a first parameter set and / or a second parameter set.

[0036] In the above embodiment, the network device can configure parameters so that the terminal determines the corresponding pattern based on the parameters and then determines the TDD frame structure, which can effectively improve the flexibility of configuration while ensuring channel performance, avoiding data conflicts, and reasonably allocating resources.

[0037] In combination with some embodiments of the first aspect, in some embodiments, the above-mentioned first parameter set includes at least one of the following parameters: the period of the pattern of the above-mentioned time domain resources; the starting position of the time domain resources occupied by the above-mentioned downlink channel; the starting position of the time domain resources occupied by the above-mentioned uplink channel; the length of the time domain resources occupied by the above-mentioned downlink channel; the length of the time domain resources occupied by the above-mentioned uplink channel.

[0038] In the above embodiment, the terminal can determine the corresponding pattern based on the parameters, which can effectively improve the flexibility of configuration, while ensuring channel performance, avoiding data conflicts, reasonably allocating resources, and ensuring complete transmission of the channel.

[0039] In combination with some embodiments of the first aspect, in some embodiments, the second parameter set includes at least one of the following parameters: the period of the pattern of the time domain resources; the starting position of the time domain resources occupied by the downlink channel or the uplink channel; information related to the protection period; the length of the time domain resources occupied by the downlink channel; the length of the time domain resources occupied by the uplink channel.

[0040] In the above embodiment, the terminal can determine the corresponding pattern based on the parameters, which can effectively improve the flexibility of configuration, while ensuring channel performance, avoiding data conflicts, reasonably allocating resources, and ensuring complete transmission of the channel.

[0041] In combination with some embodiments of the first aspect, in some embodiments, a period of the above-mentioned time domain resource pattern includes at least one time domain resource segment of a downlink channel or an uplink channel, wherein the above-mentioned downlink channel resources or uplink channel resources in each of the above-mentioned time domain resource segments are continuous.

[0042] In combination with some embodiments of the first aspect, in some embodiments, each parameter in the above-mentioned first parameter set has at least one configuration value, wherein each configuration value is used to determine the time domain resources occupied by a downlink channel or an uplink channel in one of the above-mentioned time domain resource segments in the above-mentioned time domain resource pattern.

[0043] In combination with some embodiments of the first aspect, in some embodiments, each parameter in the above-mentioned second parameter set has at least one configuration value, wherein each configuration value is used to determine the time domain resources occupied by a downlink channel or an uplink channel in one of the above-mentioned time domain resource segments in the above-mentioned time domain resource pattern.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is used to determine a pattern of multiple time domain resources, and the method further includes:

[0045] The pattern of the target time domain resource of the terminal is determined to be a combination of the patterns of the multiple time domain resources.

[0046] In the above embodiments, the flexibility of the solution can be improved and the diversity of pattern configuration is increased.

[0047] In combination with some embodiments of the first aspect, in some embodiments, the first information is system information, or the first information is radio control resource RRC signaling dedicated to the terminal.

[0048] In the above embodiment, for the terminals in the cell, the frame structure configuration may be shared or configured separately, which can effectively improve the communication efficiency of the system, increase the flexibility of the solution, and ensure the communication performance of the system.

[0049] In a second aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0050] Sending first information to a terminal, where the first information is used by the terminal to determine a pattern of time domain resources occupied by corresponding uplink channels and downlink channels;

[0051] The uplink channel and the downlink channel are located in a time division duplex (TDD) frame.

[0052] In the above embodiment, the terminal is enabled to determine a new time division duplex TDD frame structure, which effectively improves the system communication efficiency, improves the compatibility of the solution, and ensures the channel performance.

[0053] In combination with some embodiments of the second aspect, in some embodiments, the first information is used to indicate a pattern of at least one predefined time domain resource.

[0054] In combination with some embodiments of the second aspect, in some embodiments, the above-mentioned first information includes a first parameter set and / or a second parameter set.

[0055] In combination with some embodiments of the second aspect, in some embodiments, the above-mentioned first parameter set includes at least one of the following parameters: the period of the pattern of the above-mentioned time domain resources; the starting position of the time domain resources occupied by the above-mentioned downlink channel; the starting position of the time domain resources occupied by the above-mentioned uplink channel; the length of the time domain resources occupied by the above-mentioned downlink channel; the length of the time domain resources occupied by the above-mentioned uplink channel.

[0056] In combination with some embodiments of the second aspect, in some embodiments, the above-mentioned second parameter set includes at least one of the following parameters: the period of the pattern of the above-mentioned time domain resources; the starting position of the time domain resources occupied by the above-mentioned downlink channel or the above-mentioned uplink channel; information related to the protection period; the length of the time domain resources occupied by the above-mentioned downlink channel; the length of the time domain resources occupied by the above-mentioned uplink channel.

[0057] In combination with some embodiments of the second aspect, in some embodiments, a period of the above-mentioned time domain resource pattern includes at least one time domain resource segment of a downlink channel or an uplink channel, wherein the above-mentioned downlink channel resources or uplink channel resources in each of the above-mentioned time domain resource segments are continuous.

[0058] In combination with some embodiments of the second aspect, in some embodiments, each parameter in the above-mentioned first parameter set has at least one configuration value, wherein each configuration value is used to determine the time domain resources occupied by a downlink channel or an uplink channel in one of the above-mentioned time domain resource segments in the above-mentioned time domain resource pattern.

[0059] In combination with some embodiments of the second aspect, in some embodiments, each parameter in the above-mentioned second parameter set has at least one configuration value, wherein each configuration value is used to determine the time domain resources occupied by a downlink channel or an uplink channel in one of the above-mentioned time domain resource segments in the above-mentioned time domain resource pattern.

[0060] In combination with some embodiments of the second aspect, in some embodiments, the first information is used to determine patterns of multiple time domain resources, and the pattern of the target time domain resources of the terminal is a combination of the patterns of the multiple time domain resources.

[0061] In combination with some embodiments of the second aspect, in some embodiments, the first information is system information, or the first information is radio control resource RRC signaling dedicated to the terminal.

[0062] In a third aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0063] The terminal determines, based on the agreement of the protocol or the first information, a pattern of time domain resources occupied by an uplink channel and a downlink channel corresponding to the terminal;

[0064] The first information is sent by a network device, and the uplink channel and the downlink channel are located in a time division duplex (TDD) frame.

[0065] In the above embodiment, the terminal is enabled to determine a new time division duplex TDD frame structure, which effectively improves the system communication efficiency, improves the compatibility of the solution, and ensures the channel performance.

[0066] In a fourth aspect, an embodiment of the present disclosure proposes a terminal, which includes a transceiver module and a processing module; wherein the terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0067] In a fifth aspect, an embodiment of the present disclosure proposes a network device, which includes a transceiver module and a processing module; wherein the network device is used to execute the second aspect and the optional implementation method of the second aspect.

[0068] In a sixth aspect, an embodiment of the present disclosure proposes a communication device, which includes: at least one processor and an interface circuit; wherein the communication device is used to execute the first aspect and the optional implementation method of the first aspect.

[0069] In a seventh aspect, an embodiment of the present disclosure proposes a communication device, comprising: at least one processor and an interface circuit; wherein the communication device is used to execute the second aspect and the optional implementation method of the second aspect.

[0070] In an eighth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and a network device; wherein the terminal is configured to execute the method described in the first aspect and the optional implementation of the first aspect, and the network device is configured to execute the method described in the second aspect and the optional implementation of the second aspect.

[0071] In the ninth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect and the optional implementation method of the first aspect, the second aspect and the optional implementation method of the second aspect.

[0072] In a tenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0073] In an eleventh aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0074] In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system. The chip or chip system includes a processing circuit configured to execute the method described in accordance with the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0075] It is understandable that the above-mentioned terminals, access network devices, core network devices, communication systems, storage media, program products, computer programs, chips or chip systems are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods, which will not be repeated here.

[0076] In some embodiments, the terms communication method and information processing method can be used interchangeably.

[0077] The embodiments of the present disclosure are not exhaustive, but are only illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, the 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. In addition, 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. In each embodiment of the present disclosure, if there is no special explanation and logical conflict, the terms and / or descriptions between the embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0078] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0079] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "a", "an", "the", "above", "said", "aforementioned", "this", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun after the article may be understood as a singular expression or a plural expression.

[0080] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0081] In some embodiments, the terms “at least one of A or B, at least one of A and B,” “one or more,” “a plurality of,” “multiple,” etc. may be used interchangeably.

[0082] In some embodiments, "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 regardless of whether there is a B branch); in some embodiments, B (B is executed regardless of whether there is an A branch); 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.

[0083] In some embodiments, the "A or B" and other recording methods may include the following technical solutions according to the situation: in some embodiments, A (A is executed regardless of whether there is a B branch); in some embodiments, B (B is executed regardless of whether there is an A branch); in some embodiments, execution is selected from A and B (A and B are selectively executed). When there are more branches such as A, B, C, etc., the above is also similar.

[0084] The 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. For example, if 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", and 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". For another example, if 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". For another example, 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. In addition, 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.

[0085] In some embodiments, “including A”, “comprising A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0086] In some embodiments, terms such as "time / frequency", "time / frequency domain", etc. refer to the time domain and / or the frequency domain.

[0087] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at...", "when...", "if...", "if...", etc. can be used interchangeably. These descriptions all mean that the device will make corresponding processing under certain objective circumstances. It is not necessary to limit the time, nor is it required that the device must have a judgment action when implementing it, nor does it mean that there must be other limitations.

[0088] In some embodiments, 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.

[0089] In some embodiments, devices and the like may be interpreted as physical or virtual, and their names are not limited to the names described in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "network function", "network device", "function", "node", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" may be used interchangeably.

[0090] In some embodiments, "network" may be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0091] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station (radio base station)", "fixed station (fixed station)", "node (node)", "access point (access point)", "transmission point (TP)", "reception point (reception point, RP)", "transmission and / or reception point (transmission / reception point, TRP)", "panel (panel)", "antenna panel (antenna panel)", "antenna array (antenna array)", "cell (cell)", "macro cell (macro cell)", "small cell (small cell)", "femto cell (femto cell)", "pico cell (pico cell)", "sector (sector)", "cell group (cell)", "serving cell (serving cell)", "carrier (carrier)", "component carrier (component carrier)", "bandwidth part (bandwidth part, BWP)" and the like can be used interchangeably.

[0092] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "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 and the like can be used interchangeably.

[0093] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the access network device, the core network device, or the network device and the communication between the terminals is replaced by the communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it can also be set as a structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0094] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may also be configured to have a structure that has all or part of the functions of the terminal.

[0095] In some embodiments, acquisition of data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0096] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0097] Figure 1A It is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0098] like Figure 1A As shown, the communication system 100 includes a terminal 101 and a network device 102 .

[0099] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a Narrow Band-Internet of Things device (NB-IoT), a satellite communication 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, a wireless terminal device in a smart home, and at least one of a reduced capability (RedCap) terminal, but is not limited to these.

[0100] In some embodiments, the network device 102 is, for example, a node or device that accesses a terminal to a wireless network. The network device may include nodes such as satellites or drones in non-terrestrial communication networks, evolved NodeB (eNB) in 5G communication systems, next generation evolved NodeB (ng-eNB), next generation NodeB (gNB), next generation RAN node (NG-RAN node), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul equipment, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in 6G communication system, open base station (Open RAN), cloud base station (Cloud RAN), base station in other communication systems, and at least one of access nodes in Wi-Fi systems, but is not limited to these.

[0101] In some embodiments, the technical solution of the present disclosure may be applicable to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure may become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.

[0102] In some embodiments, 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 referred to as 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.

[0103] It can be understood that 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.

[0104] The following embodiments of the present disclosure can be applied to Figure 1A The communication system 100, or a portion thereof, is shown but is not limited thereto. Figure 1A The various entities shown are examples, and the communication system may include Figure 1A All or part of the subject, and may also include Figure 1A The number and form of other entities are arbitrary, each entity can be physical or virtual, the connection relationship between the entities is illustrative, the entities can be connected or disconnected, the connection can be in any way, it can be direct or indirect, and it can be wired or wireless.

[0105] The embodiments of the present disclosure may be applied to non-terrestrial networks (NTN), Internet of Things (IoT) systems, narrowband Internet of Things (NB-IoT) systems, long term evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, fourth generation mobile communication systems (4G), fifth generation mobile communication systems (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine-to-Machine (M2M) system, Vehicle-to-Everything (V2X), systems using other communication methods, next-generation systems based on them, etc. In addition, multiple systems can also be combined (for example, a combination of LTE or LTE-A and 5G, etc.) for application.

[0106] In some embodiments, non-terrestrial networks (NTN) have gradually become one of the research hotspots. NTN can build wireless communication systems using non-terrestrial infrastructure such as aerial platforms or satellites in orbit. It can effectively enhance the coverage of the network and can also be used for emergency communications. In addition, NTN can also play a role in the development of the Internet of Things (IoT) and has scalability.

[0107] In some embodiments, only frequency division duplexing (FDD) operation is supported for the IoT-NTN system.

[0108] In some embodiments, it is contemplated that time division duplexing (TDD) operation may be supported on a dedicated spectrum (1616-1626.5 MHz) allocated to satellite systems, which spectrum is currently used by the Iridium private communications system.

[0109] In some embodiments, it is also possible to consider introducing a certain period in the TDD band to achieve the purpose of saving power consumption, for example, defining a period of 90 ms.

[0110] Furthermore, Iridium is pushing to use one DL time unit (8.28ms) and one UL time unit (8.28ms) in its 90ms period for the 3GPP TDD mode, and the remaining resources are used to maintain the operation of its original private system, that is, to achieve compatibility between the 3GPP IoT-NTN TDD mode and the Iridium private system.

[0111] Since the current IoT-NTN system only supports FDD operation, the frame structure of the TDD mode needs to be considered and redesigned.

[0112] Furthermore, in each embodiment of the present application, the following effects may also need to be comprehensively considered during TDD design:

[0113] 1. Considering the coexistence with Iridium's TDD private system, x DL time units (8.28ms) in the 90ms period are selected for DL ​​transmission in TDD mode, and x UL time units (8.28ms) in the 90ms period are selected for UL transmission in TDD mode.

[0114] 2. Resource mapping in IoT-NTN TDD mode needs to refer to the mapping method of NarrowBand Primary Synchronization Signal (NPSS), NarrowBand Secondary Synchronization Signal (NSSS), NarrowBand Physical Broadcast Channel (NPBCH) and NarrowBand Physical Random Access Channel (NPRACH) in FDD mode. In order to achieve resource consistency with FDD in TDD mode, it is necessary to ensure that the resource locations of NPSS, NSSS and NPBCH are not covered or omitted.

[0115] 3. For Low Earth Orbit (LEO) satellite systems, the round trip time (RTT) varies according to the satellite altitude:

[0116] For example, LEO 600km: RTT is about 25.77ms; LEO 1200km: RTT is about 41.77ms.

[0117] Based on the above analysis, in the design of the TDD frame structure of each embodiment of the present application, it is necessary to consider the reasonable allocation of DL and UL time units to ensure that the operating space of the Iridium system is retained while meeting the IoT-NTN TDD requirements. When designing the TDD frame structure, the time when these channels appear in the TDD frame should be matched as much as possible with the time when they appear in the FDD system to keep the channel performance unaffected. This will help ensure the complete transmission of synchronization and broadcast channels and meet the signaling requirements of IoT-NTN. In addition, it is necessary to reserve appropriate guard time slots (guard period) to ensure that there is enough delay between uplink and downlink switching to avoid signal overlap. A guard time slot of reasonable length is introduced each time DL and UL are switched. The specific length can depend on the satellite altitude to ensure smooth DL and UL switching of the IoT-NTN system and avoid data conflicts.

[0118] The communication method and device provided by the present disclosure are described in detail below with reference to the accompanying drawings.

[0119] Figure 2A FIG. 1 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. Figure 2A As shown, the embodiment of the present disclosure relates to a communication method, and the method includes:

[0120] Step S2101, the network device 102 sends first information.

[0121] In some embodiments, the first information is used by the terminal 101 to determine a pattern of time domain resources occupied by corresponding uplink channels and downlink channels.

[0122] In various embodiments of the present application, the above-mentioned pattern of time domain resources is a pattern under the time division duplex TDD mode.

[0123] In some embodiments, the uplink channel and the downlink channel are located in a TDD frame.

[0124] In some embodiments, the first information is used to indicate a pattern of at least one predefined time domain resource.

[0125] In some embodiments, the first information includes a first parameter set and / or a second parameter set.

[0126] In some embodiments, the above-mentioned first parameter set (for example, can be recorded as set#1) includes at least one of the following parameters: the period (period) of the pattern of the time domain resources; the starting position of the time domain resources occupied by the downlink channel; the starting position of the time domain resources occupied by the uplink channel; the length (duration) of the time domain resources occupied by the downlink channel; the length of the time domain resources occupied by the uplink channel.

[0127] Optionally, the unit of the "period of the pattern of time domain resources" may be a radio frame or millisecond (ms), which refers to the time period of repetition of the pattern.

[0128] Furthermore, the position of the first radio frame in each cycle may be determined by the following formula: SFN mod N = 0, where SFN is the system frame number (SFN), mod means modulus, and N is the position of the first radio frame.

[0129] Optionally, the unit of the “starting position of the time domain resources occupied by the downlink channel (simply denoted as D)” may be a time slot, or a subframe, or a millisecond (ms), etc.

[0130] Optionally, the parameter of "starting position of D" is used to indicate an offset of the starting position relative to a starting position / ending position of a UL time domain unit within a period.

[0131] Optionally, the parameter of "starting position of D" is used to indicate the offset of the starting position relative to a time domain reference point within a period. Optionally, the time domain reference point may be, for example, subframe#0 of the first system frame within a specific period N, that is, the starting position of D is the offset relative to subframe#0 of the first system frame in the current period; or, the time domain reference point may also be the Mth slot within a TDD pattern period, etc., where M is a protocol agreement or a high-level configuration.

[0132] Optionally, the unit of the “starting position of the time domain resources occupied by the uplink channel (simply denoted as U)” may be a time slot, or a subframe, or a millisecond (ms), etc.

[0133] Optionally, the parameter of "starting position of U" is used to indicate the offset of the starting position relative to a time domain reference point within a period. Optionally, the time domain reference point may be, for example, subframe#0 of the first system frame within a specific period N, that is, the starting position of U is the offset relative to subframe#0 of the first system frame within the current period; or, the time domain reference point may also be the Mth slot within a TDD pattern period, etc., where M is a protocol agreement or a high-level configuration.

[0134] Optionally, the parameter of "starting position of U" is used to indicate the offset of the starting position relative to the starting position / ending position of D.

[0135] Optionally, the unit of the "time domain resource length occupied by the downlink channel" can be time slot, subframe, millisecond ms, etc.; it refers to the total duration of DL transmission in TDD mode, and controls the resource distribution of the downlink time slot.

[0136] Optionally, the unit of the "time domain resource length occupied by the uplink channel" can be time slot, subframe, millisecond ms, etc.; it refers to the total duration of UL transmission in TDD mode, and controls the resource distribution of the uplink time slot.

[0137] Optionally, the number of continuous D or U time domain unit windows (also called time domain resource segments) within the above-mentioned one cycle may be one or more.

[0138] In the case where the first information includes the first parameter set, the corresponding guard period is the symbol between the end position of D and the start position of U, or the symbol between the end position of U and the start position of D.

[0139] In some embodiments, the second parameter set (for example, can be recorded as set#2) includes at least one of the following parameters: the period (period) of the pattern of the time domain resources; the starting position of the time domain resources occupied by the downlink channel or the uplink channel; information related to the guard period (guard period); the length (duration) of the time domain resources occupied by the downlink channel; the length of the time domain resources occupied by the uplink channel.

[0140] Optionally, the unit of the "period of the pattern of time domain resources" may be a radio frame or millisecond (ms), which refers to the time period of repetition of the pattern.

[0141] Furthermore, the position of the first radio frame in each cycle may be determined by the following formula: SFN mod N = 0, where SFN is the system frame number, mod represents modulus, and N is the position of the first radio frame.

[0142] Optionally, in the above-mentioned second parameter set, only one of the starting positions of the time domain resources occupied by the downlink channel or the uplink channel may be included. That is, the second parameter set includes the starting position of the time domain resources occupied by the downlink channel, but does not include the starting position of the time domain resources occupied by the uplink channel; or the second parameter set includes the starting position of the time domain resources occupied by the uplink channel, but does not include the starting position of the time domain resources occupied by the downlink channel.

[0143] Optionally, the unit of the “starting position of the time domain resources (simply denoted as D or U) occupied by the downlink channel or the uplink channel” may be a time slot, or a subframe, or millisecond (ms), etc.

[0144] Optionally, the parameter of "starting position of D or U" is used to indicate the offset of the starting position relative to the starting position / ending position of the UL time domain unit within a period; or the offset relative to the starting position or ending position of the guard period, which can be left or right.

[0145] Optionally, the parameter of "starting position of D or U" is used to indicate the offset of the starting position relative to a time domain reference point in a period. Optionally, the time domain reference point may be, for example, subframe#0 of the first system frame in a specific period N, that is, the starting position of D is the offset relative to subframe#0 of the first system frame in the current period; or, the time domain reference point may also be the Mth slot in a TDD pattern period, etc., where M is a protocol agreement or a high-level configuration.

[0146] Optionally, the “protection period related information” may include: at least one of a duration of the protection period and a starting position of the protection period.

[0147] Optionally, the duration of the protection period refers to the total duration of the transmission of the protection period in the TDD mode, and the unit may be a time slot, a subframe, a millisecond ms, etc.

[0148] Optionally, the starting position of the protection period may be preset by the protocol or indicated by the network device 102 .

[0149] For example, the protocol preset method can be: the protocol can preset the starting position of the guard period to be defined as one time domain symbol after the end position of U, or as one symbol after the end position of D. Alternatively, it can also be defined as the starting position of U minus the duration of the guard period, or it can also be defined as the starting position of D minus the duration of the guard period. The network device 102 indicates a value, which is used to indicate the offset of the starting position of the guard period relative to a time domain reference point within a period.

[0150] Optionally, the unit of the "time domain resource length occupied by the downlink channel" can be time slot, subframe, millisecond ms, etc.; it refers to the total duration of DL transmission in TDD mode, and controls the resource distribution of the downlink time slot.

[0151] Optionally, the unit of the "time domain resource length occupied by the uplink channel" can be time slot, subframe, millisecond ms, etc.; it refers to the total duration of UL transmission in TDD mode, and controls the resource distribution of the uplink time slot.

[0152] Optionally, the number of continuous D or U time domain unit windows (also called time domain resource segments) within the above-mentioned one cycle may be one or more.

[0153] In the case where the first information includes the second parameter set, the starting position of U / D may be defined by the starting position of D / U and the guard period.

[0154] For example, it is known that D and guard period are determined based on the indication of the network device 102, D is used to indicate the offset of the starting position of D relative to the first subframe in the period, and the starting position of the guard period is the next time domain symbol of the end position of D. Then, the uplink starting position (in units of slot, subframe, or ms, etc.) can be an offset relative to the starting position of the guard period.

[0155] Or, for example, it is known that D and guard period are determined based on the indication of network device 102, wherein the starting position of guardperiod is an offset relative to the starting time of the period, and the time domain position of guard period is determined based on guard period duration, and D is an offset relative to the end position of guard period, for example, the starting position of D is the next symbol of guard period, and the location of D can be determined based on the duration of D. Furthermore, the end position of U can also be defined as the previous time domain symbol of the starting position of guard period, and the location of U can be determined based on the duration of U, thereby determining the time domain resource locations of all D and U within a TDD period. In this way, the parameters indicated by network device 102 include: duration of D and U, guard period duration, and start point of guard period.

[0156] In some embodiments, the name of the above-mentioned first information is not limited, and it may be, for example, "system information", "broadcast message", "Radio Resource Control (RRC) signaling", "dedicated signaling", "ephemeris information", "type information", "configuration information", "communication configuration", etc.

[0157] Step S2102: Terminal 101 determines a pattern of time domain resources occupied by uplink channels and downlink channels.

[0158] In some embodiments, the terminal 101 may determine the pattern of time domain resources corresponding to the uplink channel and the downlink channel based on the agreement of the protocol.

[0159] Optionally, the protocol may stipulate a pattern of one or more time domain resources.

[0160] Optionally, the protocol may preset a fixed TDD pattern, and different systems / cases / scenarios all adopt this fixed pattern.

[0161] Optionally, the above-mentioned preset fixed pattern can refer to the pattern example in any embodiment of the present application.

[0162] In some embodiments, the protocol may preset multiple patterns, and the terminal 101 may further determine one of the patterns in an implicit manner (for example, one of the patterns is implicitly determined based on the ephemeris information broadcast by the System Information Block (SIB) message, or information such as the satellite type).

[0163] Furthermore, the terminal 101 can repeatedly transmit in the time domain to form a complete TDD frame structure based on the determined time domain resource pattern, thereby determining the uplink resources and downlink resources that the terminal 101 can use.

[0164] In some embodiments, the terminal 101 may determine a pattern of time domain resources corresponding to the uplink channel and the downlink channel based on the first information.

[0165] In some embodiments, the first information is used to indicate a pattern of time domain resources corresponding to the terminal 101, and the terminal 101 determines the pattern of the time domain resources based on the indication of the first information.

[0166] In some embodiments, the first information includes a first parameter set and / or a second parameter set, and the terminal 101 determines a pattern of time domain resources corresponding to the uplink channel and the downlink channel based on the first parameter set and / or the second parameter set.

[0167] In some embodiments, a period of a time domain resource pattern includes at least one time domain resource segment of a downlink channel or an uplink channel, wherein the downlink channel resources or uplink channel resources in each time domain resource segment are continuous.

[0168] In some embodiments, the corresponding time domain resource pattern can be determined by combining the configuration of the network device 102 with the protocol preset. Multiple parameters required for determining the time domain resource pattern, some of which are determined based on the configuration or indication of the network device 102, and some of which are protocol preset values ​​or determined based on preset rules.

[0169] Optionally, the definition of the candidate value (candidate value) of each parameter in the first parameter set or the second parameter set may adopt at least one of the following methods, wherein the definition methods of the candidate values ​​of different parameters may be different:

[0170] Integer indication, for example, the candidate value is defined as Integer(1…X), or inter(0…X);

[0171] Enumerated values, for example, candidate values ​​are defined as Emumerated(a,b,c…);

[0172] Bitmap.

[0173] In some embodiments, there may be multiple D / U time domain resource segments in a time domain period of the TDD pattern (wherein the D / U resources in each time domain resource segment are continuous), and the first parameter set and / or the second parameter set may adopt at least one of the following configuration methods:

[0174] Optionally, there is at least one configuration value for each of the following parameters in the first parameter set, wherein each configuration value is used to determine the time domain resources occupied by a downlink channel or an uplink channel within a time domain resource segment in a time domain resource pattern: the starting position of D, the starting position of U, the duration of D, and the duration of U.

[0175] Optionally, there is at least one configuration value for each of the following parameters in the second parameter set, wherein each configuration value is used to determine the time domain resources occupied by a downlink channel or an uplink channel in a time domain resource segment in a time domain resource pattern: the starting position of D / U, the guard period (including duration and / or starting position), the duration of D, the duration of U (wherein the duration of D / U can be the number of continuous resources in a time domain resource segment).

[0176] Optionally, multiple TDD patterns can be determined by configuration or indication of the first parameter set and / or the second parameter set, and parameters preset by the protocol. That is, the time domain period, guard period, location of D, and location of U of each of the multiple patterns determined by the terminal 101 can be different. Optionally, D and / or U is only a continuous time domain resource segment.

[0177] A possible embodiment is (taking the configuration of two patterns as an example for explanation), the terminal 101 completes the specific transmission resource configuration of UL and DL in time period 1 according to the corresponding UL and DL parameter definitions in time period 1 indicated by pattern#1, and completes the specific transmission resource configuration of UL and DL in time period 2 according to the corresponding UL and DL parameter definitions in time period 2 indicated by pattern#2. The target pattern is determined based on pattern#1 and pattern#2. One possible way is that the final target pattern is based on a combination of pattern#1 and pattern#2 to form a longer period (time period=time period 1+time period 2), and a complete TDD frame structure is formed through repeated transmission of the time period.

[0178] In some embodiments, when the terminal 101 determines the target pattern based on multiple patterns, there are two ways to splice the previous and next patterns (pattern #1 / 2 / …):

[0179] Method 1: The terminal 101 determines the starting position of the time period of each pattern through the indication / protocol preset of the network device 102. The terminal determines the longer period of the target pattern based on the starting position of the time period of each pattern and the duration of the time period. For example, the starting radio frame of pattern#1 is SFN#1, the duration is 1 radio frame, the starting radio frame of pattern#2 is SFN#4, the duration is 2 radio frames, then the current time period of the target pattern is: SFN#1~SFN#5, and the starting position of the target pattern is the first time domain symbol position of SFN#1.

[0180] Method 2: The wireless frame indicates that the pattern list is {pattern#1, pattern#2, ...}, and the starting position of each pattern is determined based on the ending position of the previous pattern (for example, the starting time domain position of pattern#2 is determined based on the ending position of pattern#1). For example, the starting time domain position of pattern#2 is the next time domain symbol of the ending time domain position of pattern#1. Based on this, the determination of the time domain period of the target pattern can be determined only through the configuration of the network device 102 or the protocol preset: each pattern (such as pattern#1 and pattern#2, etc.) has an independent time domain duration, and the starting position of pattern#1. Another possible way is that each pattern (such as pattern#1 and pattern#2, etc.) has the same time period, then a common time period can be determined based on the protocol preset or the configuration of the network device 102, and further only the starting time domain position of pattern#1 and the time domain resource location of U and / or D within each pattern need to be determined through the configuration of the network device or the protocol preset.

[0181] It should also be noted that, in the above embodiments, it is not excluded that a time domain period of one pattern contains only downlink resources, while a time domain period of another pattern contains only uplink resources.

[0182] In some embodiments, the first information may also indicate a number or index of a TDD pattern.

[0183] Optionally, there may be multiple TDD patterns, which are preset by the protocol.

[0184] As an example, the TDD uplink and downlink common configuration (tdd-UL-DL-ConfigurationCommon) provides a subcarrier spacing configuration (determining the frequency domain configuration) and a TDD pattern number configuration (used to determine the specific selection of the TDD pattern) defined by a reference subcarrier spacing (referenceSubcarrierSpacing). The corresponding TDD pattern can be found based on the TDD pattern number (that is, the number or index of the TDD pattern), and a complete TDD frame structure is formed according to the repeated transmission of the pattern. The terminal 101 finds the pattern to indicate the TDD frame structure through the relevant TDD pattern number parameter index indication provided by tdd-UL-DL-ConfigurationCommon.

[0185] In some embodiments, the network device 102 may not configure the relevant parameters of the TDD pattern, so the terminal 101 can determine the default TDD pattern based on the preset method and / or preset value of the protocol.

[0186] In some embodiments, the first information is included in the system information. For example, it can be configured through a narrowband system information block (SIBx-NB), and the TDD pattern can be a cell-specific configuration, that is, all terminals in the cell share the same frame structure.

[0187] As an example, the network device 102 can generate a SIBx-NB message containing TDD pattern configuration information and broadcast it in the cell. SIBx-NB contains relevant parameters of the TDD pattern, such as a pattern number (TDD pattern number) or specific pattern parameters (such as time period, DL / UL starting position, duration, etc.). All terminals 101 that receive the SIBx-NB parse the TDD pattern parameters and set the uplink and downlink transmission time slots in their respective TDD frames according to the parameters. Based on the repetition of the TDD pattern period, the terminal 101 generates a complete TDD frame structure, thereby achieving consistent DL / UL time slot configuration within the cell.

[0188] In some embodiments, the network device 102 can also be configured through terminal-dedicated (UE dedicated) signaling, then the TDD pattern can be a terminal-specific (UE-specific) configuration, that is, each terminal can have a separate IoT-NTN TDD frame structure, and the TDD frame structures corresponding to different terminals may be different.

[0189] As an example, the network device 102 can generate a dedicated RRC signaling for a specific terminal, including a specific TDD pattern parameter set, and send it directly to the terminal. The RRC signaling can specify the TDD pattern number, or provide detailed pattern parameters, such as downlink / uplink starting position, duration, guard period, etc. The terminal that receives the RRC signaling parses the pattern parameters and generates its own TDD frame structure. Based on the pattern period, the terminal dynamically switches the DL / UL time slot during transmission to meet specific business needs.

[0190] As an example, in each embodiment of the present application, the following factors may be considered in the design of the TDD pattern:

[0191] 1. Considering the coexistence with Iridium's TDD private system, one DL time unit (8.28ms) and one UL time unit (8.28ms) in the 90ms period are selected.

[0192] 2. Map resources according to the NPSS / NSSS / NPBCH / NPRACH mapping method under the FDD system to ensure the integrity of its location structure.

[0193] 3. The maximum gaurd period between DL and UL is 41.77ms.

[0194] As an example, a TDD pattern might be Figure 2B shown.

[0195] The period of the pattern of the time domain resources is 180 ms, the period of the PRACH may be 40 / 80, the time domain offset of the PRACH relative to the subframe#0 of the first system frame in the current period is timeoffset=32, and the number of repetitions of the PRACH is repetition=1.

[0196] Specifically, the time domain offset of PRACH relative to subframe#0 of the first system frame in the current cycle is timeoffset=32, that is, the starting position of PRACH is located at subframe#2 of the fourth radio frame in the first 90ms.

[0197] Pattern 1: Within the first 90 ms, the second UL slot (in the 4th radio frame) of the Iridium system is used for UL transmission in TDD mode, and the second DL slot (in the 7th radio frame) is used for DL ​​transmission in TDD mode.

[0198] Specifically, the starting position of PRACH is located on subframe#2 of the 4th radio frame within the 90ms, NPSS is located on subframe#5 of the 7th radio frame, and NPBCH is located on subframe#0 of the 8th radio frame.

[0199] Pattern 2: In the second 90ms, the first UL slot (in the third radio frame) of the Iridium system is used for UL transmission in TDD mode, and the second DL slot (in the seventh radio frame) is used for DL ​​transmission in TDD mode.

[0200] Specifically, the starting position of PRACH is located on subframe#2 of the 3rd wireless frame within the 90ms, NPSS is located on subframe#5 of the 7th wireless frame, NSSS is located on subframe#9 of the 7th wireless frame, and NPBCH is located on subframe#0 of the 8th wireless frame.

[0201] As an example, a TDD pattern might be Figure 2C shown.

[0202] The period of the pattern of the time domain resources is 180 ms, the period of the PRACH may be 40 / 80, the time domain offset of the PRACH relative to the subframe#0 of the first system frame in the current period is timeoffset=32, and the number of repetitions of the PRACH is repetition=1.

[0203] Specifically, the time domain offset of PRACH relative to subframe#0 of the first system frame in the current cycle is timeoffset=32, that is, the starting position of PRACH is located at subframe#2 of the fourth radio frame in the first 90ms.

[0204] Pattern 1: Within the first 90 ms, the second UL slot (in the 4th radio frame) of the Iridium system is used for UL transmission in TDD mode, and the third DL slot (in the 8th radio frame) is used for DL ​​transmission in TDD mode.

[0205] Specifically, the starting position of PRACH is located on subframe#2 of the 4th radio frame within the 90ms, NPSS is located on subframe#5 of the 8th radio frame, and NPBCH is located on subframe#0 of the 9th radio frame.

[0206] Pattern 2: In the second 90ms, the first UL slot (in the third radio frame) of the Iridium system is used for UL transmission in TDD mode, and the third DL slot (in the eighth radio frame) is used for DL ​​transmission in TDD mode.

[0207] Specifically, the starting position of PRACH is located on subframe#2 of the 3rd wireless frame within the 90ms, NPSS is located on subframe#5 of the 8th wireless frame, NSSS is located on subframe#9 of the 8th wireless frame, and NPBCH is located on subframe#0 of the 9th wireless frame.

[0208] As an example, a TDD pattern might be Figure 2D shown.

[0209] The period of the pattern of the time domain resources is 180 ms, the period of the PRACH may be 40, the time domain offset of the PRACH relative to the subframe#0 of the first system frame in the current period is timeoffset=8, and the number of repetitions of the PRACH is repetition=1.

[0210] Specifically, the time domain offset of PRACH relative to subframe#0 of the first system frame in the current period is timeoffset=8, and the period of PRACH is 40, that is, the starting position of PRACH in the actual pattern is located at subframe#8 of the 5th wireless frame in the first 90ms.

[0211] Pattern 1: In the first 90 ms, the fourth UL slot (in the fifth radio frame) of the Iridium system is used for UL transmission in TDD mode, and the second DL slot (in the seventh radio frame) is used for DL ​​transmission in TDD mode.

[0212] Specifically, the starting position of PRACH is located on subframe #8 of the 5th radio frame within the 90 ms, NPSS is located on subframe #5 of the 7th radio frame, and NPBCH is located on subframe #0 of the 8th radio frame.

[0213] Pattern 2: In the second 90ms, the third UL slot (in the 4th radio frame) of the Iridium system is used for UL transmission in TDD mode, and the second DL slot (in the 7th radio frame) is used for DL ​​transmission in TDD mode.

[0214] Specifically, the starting position of PRACH is located on subframe#8 of the 4th wireless frame within the 90ms, NPSS is located on subframe#5 of the 7th wireless frame, NSSS is located on subframe#9 of the 7th wireless frame, and NPBCH is located on subframe#0 of the 8th wireless frame.

[0215] It is understandable that, in the above pattern, PRACH resources outside the UL slot of the Iridium system cannot be used.

[0216] As an example, a TDD pattern might be Figure 2E shown.

[0217] The period of the pattern of the time domain resources is 180 ms, the period of the PRACH may be 40, the time domain offset of the PRACH relative to the subframe#0 of the first system frame in the current period is timeoffset=8, and the number of repetitions of the PRACH is repetition=1.

[0218] Specifically, the time domain offset of PRACH relative to subframe#0 of the first system frame in the current period is timeoffset=8, and the period of PRACH is 40, that is, the starting position of PRACH in the actual pattern is located at subframe#8 of the 5th wireless frame in the first 90ms.

[0219] Pattern 1: In the first 90 ms, the fourth UL slot (in the fifth radio frame) of the Iridium system is used for UL transmission in TDD mode, and the third DL slot (in the eighth radio frame) is used for DL ​​transmission in TDD mode.

[0220] Specifically, the starting position of PRACH is located on subframe #8 of the 5th radio frame within the 90 ms, NPSS is located on subframe #5 of the 8th radio frame, and NPBCH is located on subframe #0 of the 9th radio frame.

[0221] Pattern 2: In the second 90ms, the third UL slot (in the 4th radio frame) of the Iridium system is used for UL transmission in TDD mode, and the third DL slot (in the 8th radio frame) is used for DL ​​transmission in TDD mode.

[0222] Specifically, the starting position of PRACH is located on subframe#8 of the 4th wireless frame within the 90ms, NPSS is located on subframe#5 of the 8th wireless frame, NSSS is located on subframe#9 of the 9th wireless frame, and NPBCH is located on subframe#0 of the 9th wireless frame.

[0223] As an example, a TDD pattern might be Figure 2F shown.

[0224] The period of the pattern of the time domain resources is 180 ms, the period of the PRACH may be 40 / 80, the time domain offset of the PRACH relative to the subframe#0 of the first system frame in the current period is timeoffset=32, and the number of repetitions of the PRACH is repetition=2.

[0225] Specifically, the time domain offset of PRACH relative to subframe#0 of the first system frame in the current cycle is timeoffset=32, that is, the starting position of PRACH is located at subframe#2 of the fourth radio frame in the first 90ms.

[0226] Pattern 1: Within the first 90ms, the second and third UL slots (in the 4th and 5th radio frames) of the Iridium system are used for UL transmission in TDD mode, and the first and second DL slots (in the 6th and 7th radio frames) are used for DL ​​transmission in TDD mode.

[0227] Specifically, the starting position of PRACH is located on subframe#2 of the 4th wireless frame within the 90ms, NPSS is located on subframe#5 of the 7th wireless frame, NSSS is located on subframe#9 of the 7th wireless frame, and NPBCH is located on subframe#0 of the 7th wireless frame and subframe#0 of the 8th wireless frame.

[0228] Pattern 2: In the second 90ms, the first and second UL slots (in the third radio frame) of the Iridium system are used for UL transmission in TDD mode, and the first and second DL slots (in the eighth radio frame) are used for DL ​​transmission in TDD mode.

[0229] Specifically, the starting position of PRACH is located on subframe#2 of the 3rd wireless frame within the 90ms, NPSS is located on subframe#5 of the 7th wireless frame, NSSS is located on subframe#9 of the 7th wireless frame, and NPBCH is located on subframe#0 of the 7th wireless frame and subframe#0 of the 8th wireless frame.

[0230] As an example, a TDD pattern might be Figure 2G The network device 102 may indicate the following first parameter set #a: N=18 (radio frame), D=8, U=8.

[0231] Define the period of DL within 90ms as: dl-Periodicity=20;

[0232] The start time of DL is defined as the offset of subframe#0 of the first system frame in a specific period as: dl-StartTime{15,18,19};

[0233] All possible starting point positions of DL within 90ms are Enumrated{15,18,19,35,38,39,55,58,59,75,78,79};

[0234] The UL period within 90ms is defined as: ul-Periodicity{40,80};

[0235] The offset of the UL start time relative to the subframe#0 of the first system frame in a specific period is defined as: ul-StartTime{8,16,32,64};

[0236] All possible starting point positions of UL within 90ms are Enumrated{8,16,32,48,56,64,72,88}.

[0237] Considering two cases of RTT = 25.77 ms (LEO 600 km) and 41.77 ms (LEO 1200 km), ensure that the guard period from DL to UL is greater than the RTT value.

[0238] Consider a case where RTT = 41.77ms, DL start position is 18, UL start position is 8, and cycle is 40 / 80. Figure 2G shown.

[0239] Specifically, within the first 90ms, the starting position of PRACH is located at subframe #8 of the first radio frame, NPSS is located at subframe #5 of the third radio frame, and NPBCH is located at subframe #9 of the second radio frame. Within the second 90ms, the starting position of PRACH is located at subframe #8 of the eighth radio frame, NPSS is located at subframe #5 of the third radio frame, NSSS is located at subframe #8 of the second radio frame, and NPBCH is located at subframe #9 of the second radio frame.

[0240] As an example, the network device 102 may indicate the following first parameter set: N=9, D=20, U=20.

[0241] a.RTT=25.77ms(LEO 600km):

[0242] 1)DL first, UL second:

[0243] DL: dl-StartTime{0,...,23};

[0244] UL: subframe offset {26,...,50} relative to DL;

[0245] All possible starting point positions of UL within 90ms are Integer{46,...,69}.

[0246] 2) UL in front, DL in the back:

[0247] DL: dl-StartTime{20,...,69};

[0248] UL: forward subframe offset {20,...,44} relative to DL;

[0249] All possible starting positions of UL within 90ms are Integer{0,...,26}.

[0250] b.RTT = 41.77ms (LEO 1200km):

[0251] 1)DL first, UL second:

[0252] DL: dl-StartTime{0,...,7};

[0253] UL: subframe offset {42,...,50} relative to DL;

[0254] All possible starting positions of UL within 90ms are Integer{62,...,69}.

[0255] 2) UL in front, DL in the back:

[0256] DL: dl-StartTime{20,...,69};

[0257] UL: forward subframe offset {20,...,28} relative to DL;

[0258] All possible starting positions of UL within 90ms are Integer{0,...,42}.

[0259] A TDD pattern in a TDD configuration in a.2) and b.2) can be as follows Figure 2H As shown, the PRACH cycle is 40 / 80, the time domain offset of the PRACH relative to the subframe#0 of the first system frame in the current cycle is timeoffset=8, and the number of repetitions of the PRACH is repetition=2.

[0260] Specifically, within the first 90ms, the starting position of PRACH is located at subframe#8 of the first radio frame, NPSS is located at subframe#5 of the third radio frame and subframe#5 of the fourth radio frame, NSSS is located at subframe#9 of the fourth radio frame, and NPBCH is located at subframe#0 of the third radio frame and subframe#0 of the fourth radio frame. Within the second 90ms, the starting position of PRACH is located at subframe#0 of the first radio frame, NPSS is located at subframe#5 of the third radio frame and subframe#5 of the fourth radio frame, NSSS is located at subframe#9 of the fourth radio frame, and NPBCH is located at subframe#0 of the third radio frame and subframe#0 of the fourth radio frame.

[0261] As an example, the network device 102 may indicate the following first parameter set: N=9, D=20, U=30.

[0262] a.RTT=25.77ms(LEO 600km):

[0263] 1)DL first, UL second:

[0264] DL: dl-StartTime{0,...,13};

[0265] UL: subframe offset {26,...,40} relative to DL;

[0266] All possible starting positions of UL within 90ms are Integer{46,...,59}.

[0267] 2) UL in front, DL in the back:

[0268] DL: dl-StartTime{30,...,69};

[0269] UL: forward subframe offset {30,...,44} relative to DL;

[0270] All possible starting positions of UL within 90ms are Integer{0,...,26}.

[0271] b.RTT = 41.77ms (LEO 1200km):

[0272] 1)DL first, UL second:

[0273] DL: dl-StartTime = 0;

[0274] UL: subframe offset relative to DL = 40.

[0275] 2) UL in front, DL in the back:

[0276] DL: dl-StartTime = 30;

[0277] UL: forward subframe offset relative to DL = 30.

[0278] A TDD pattern for a TDD configuration in a.1) can be as follows Fig.2I As shown, the PRACH cycle is 40, the time domain offset of PRACH relative to subframe#0 of the first system frame in the current cycle is timeoffset=8, and the number of repetitions of PRACH is repetition=2.

[0279] Specifically, in the first 90ms, NPSS is located at subframe#5 of the first radio frame and subframe#5 of the second radio frame, NSSS is located at subframe#9 of the second radio frame, NPBCH is located at subframe#0 of the first radio frame and subframe#0 of the second radio frame, and the starting position of PRACH is located at subframe#8 of the fifth radio frame. In the second 90ms, NPSS is located at subframe#5 of the first radio frame and subframe#5 of the second radio frame, NSSS is located at subframe#9 of the second radio frame, NPBCH is located at subframe#0 of the first radio frame and subframe#0 of the second radio frame, and the starting position of PRACH is located at subframe#8 of the fourth radio frame.

[0280] As an example, the network device 102 may indicate the following second parameter set: N=9, D=30, U=20.

[0281] a.RTT=25.77ms(LEO 600km):

[0282] 1)DL first, UL second:

[0283] DL: dl-StartTime{0,...,13};

[0284] Guard period: {26,...,40};

[0285] UL: Subframe offset relative to the end of the guard period = 1;

[0286] All possible starting positions of UL within 90ms are Integer{56,...,59}.

[0287] 2) UL in front, DL in the back:

[0288] DL: dl-StartTime{20,...,59};

[0289] Guard period: {20,...,44};

[0290] UL: Subframe offset relative to the end of the guard period = 1;

[0291] All possible starting point positions of UL within 90ms are Inter{0,...,26}.

[0292] b.RTT = 41.77ms (LEO 1200km):

[0293] 1)DL first, UL second:

[0294] DL: dl-StartTime = 0;

[0295] Guard period: 40;

[0296] UL: Subframe offset relative to the end position of the guard period = 1.

[0297] 2) UL in front, DL in the back:

[0298] DL: dl-StartTime = 20;

[0299] Guard period: 40;

[0300] UL: Subframe offset relative to the end position of the guard period = 1.

[0301] A TDD pattern in a TDD configuration in b.2) and a.2) can be as follows Figure 2J As shown, the PRACH cycle is 40 / 80, the time domain offset of the PRACH relative to the subframe#0 of the first system frame in the current cycle is timeoffset=8, and the number of repetitions of the PRACH is repetition=2.

[0302] Specifically, within the first 90ms, the starting position of PRACH is located at subframe#8 of the first radio frame, NPSS is located at subframe#5 of the third radio frame, subframe#5 of the fourth radio frame, and subframe#5 of the fifth radio frame, NSSS is located at subframe#9 of the fourth radio frame, and NPBCH is located at subframe#0 of the third radio frame, subframe#0 of the fourth radio frame, and subframe#0 of the fifth radio frame. Within the second 90ms, the starting position of PRACH is located at subframe#0 of the first radio frame, NPSS is located at subframe#5 of the third radio frame, subframe#5 of the fourth radio frame, and subframe#5 of the fifth radio frame, NSSS is located at subframe#9 of the fourth radio frame, and NPBCH is located at subframe#0 of the third radio frame, subframe#0 of the fourth radio frame, and subframe#0 of the fifth radio frame.

[0303] As an example, the network device 102 may indicate the following second parameter set: N=9, D=30, U=30.

[0304] Consider the case of RTT = 25.77ms (LEO 600km):

[0305] 1)DL first, UL second:

[0306] DL: dl-StartTime{0,...,3};

[0307] Guard period: {26,...,30};

[0308] UL: Subframe offset relative to the end of the guard period = 1;

[0309] All possible starting positions of UL within 90ms are Integer{56,...,69}.

[0310] 2) UL in front, DL in the back:

[0311] DL: dl-StartTime{30,...,69};

[0312] Guard period: {26,...,30};

[0313] UL: Subframe offset relative to the end of the guard period = 1;

[0314] All possible starting point positions of UL within 90ms are Inter{0,...,26}.

[0315] A TDD pattern in a TDD configuration in 2) can be as follows Figure 2K As shown, the PRACH cycle is 40 / 80, the time domain offset of the PRACH relative to the subframe#0 of the first system frame in the current cycle is timeoffset=8, and the number of repetitions of the PRACH is repetition=5.

[0316] Specifically, within the first 90ms, the starting position of PRACH is located at subframe#8 of the first radio frame, NPSS is located at subframe#5 of the fourth radio frame, subframe#5 of the fifth radio frame, and subframe#5 of the sixth radio frame, NSSS is located at subframe#9 of the fourth radio frame, and NPBCH is located at subframe#0 of the fourth radio frame, subframe#0 of the fifth radio frame, and subframe#0 of the sixth radio frame. Within the second 90ms, the starting position of PRACH is located at subframe#0 of the first radio frame, NPSS is located at subframe#5 of the fourth radio frame, subframe#5 of the fifth radio frame, and subframe#5 of the sixth radio frame, NSSS is located at subframe#9 of the fourth radio frame, and NPBCH is located at subframe#0 of the fourth radio frame, subframe#0 of the fifth radio frame, and subframe#0 of the sixth radio frame.

[0317] In each embodiment of the present application, uplink resources may be used for transmission of a PRACH, or may be used for transmission of a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH).

[0318] In some embodiments, terms such as "eNB", "gNB", "base station", "NG-RAN node", etc. can be used interchangeably.

[0319] In some embodiments, the terms "carrier", "band", "frequency" and the like can be used interchangeably.

[0320] In some embodiments, 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.

[0321] In some embodiments, 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.

[0322] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

[0323] In some embodiments, terms such as "physical downlink shared channel (PDSCH)", "DL data" and the like can be interchangeable, and terms such as "physical uplink shared channel (PUSCH)", "UL data" and the like can be interchangeable.

[0324] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0325] In some embodiments, 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.

[0326] In some embodiments, the terms "component carrier (CC)", "cell", "frequency carrier", "carrier frequency" and the like may be used interchangeably.

[0327] In some embodiments, terms such as "resource block (RB)", "physical resource block (PRB)", "sub-carrier group (SCG)", "resource element group (REG)", "PRB pair", "RB pair", "resource element (RE)", and "sub-carrier" can be used interchangeably.

[0328] In some embodiments, the terms "frame", "radio frame", "subframe", "slot", "sub-slot", "mini-slot", "symbol", "symbol", "transmission time interval (TTI)" and so on may be used interchangeably.

[0329] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, which can be interpreted as receiving from other entities, obtaining from protocols, obtaining from high layers, obtaining by self-processing, autonomous implementation, etc. The protocol includes, for example, at least one of the 3GPP protocol, Wi-Fi protocol, audio and / or video protocol.

[0330] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0331] In some embodiments, 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.

[0332] The communication method involved in the embodiment of the present disclosure may include at least one of step S2101 to step S2102. For example, step 2101 may be implemented as an independent embodiment, step 2102 may be implemented as an independent embodiment, step 2101+2102 may be implemented as an independent embodiment, etc., but is not limited thereto.

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

[0334] In some embodiments, see Figure 2A Other optional implementations recorded before or after the corresponding description.

[0335] Figure 3A FIG. 1 is a flow chart of a communication method according to an embodiment of the present disclosure. Figure 3A As shown, the embodiment of the present disclosure relates to a communication method, which is executed by a terminal 101 and includes:

[0336] Step S3101, receiving the first information sent by the network device 102.

[0337] The optional implementation of step S3101 can be found in Figure 2A Optional implementations of step S2101, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0338] Step S3102: determine the pattern of time domain resources occupied by the uplink channel and the downlink channel.

[0339] The optional implementation of step S3102 can be found in Figure 2A Optional implementations of step S2102, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0340] The communication method involved in the embodiment of the present disclosure may include at least one of step S3101 to step S3102. For example, step 3101 may be implemented as an independent embodiment, step 3102 may be implemented as an independent embodiment, step 3101+3102 may be implemented as an independent embodiment, etc., but is not limited thereto.

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

[0342] Figure 3B FIG. 1 is a flow chart of a communication method according to an embodiment of the present disclosure. Figure 3B As shown, the embodiment of the present disclosure relates to a communication method, which is executed by a terminal 101 and includes:

[0343] Step S3201: determine the pattern of time domain resources occupied by uplink channels and downlink channels.

[0344] The optional implementation of step S3201 can be found in Figure 2A Step S2102, Figure 3A Optional implementation of step S3102, and Figure 2A , Figure 3A Other related parts in the embodiments involved will not be described in detail here.

[0345] Figure 4A FIG. 1 is a flow chart of a communication method according to an embodiment of the present disclosure. Figure 4A As shown, the embodiment of the present disclosure relates to a communication method, which is performed by a network device 102 and includes:

[0346] Step S4101, sending first information to terminal 101.

[0347] The optional implementation of step S4101 can be found in Figure 2A Optional implementations of step S2101, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0348] Optionally, the first information is used by the terminal 101 to determine a pattern of time domain resources occupied by an uplink channel and a downlink channel. The optional implementation method thereof can be found in Figure 2A Optional implementations of step S2102, and Figure 2A Other related parts in the embodiments involved will not be described in detail here.

[0349] Figure 5 FIG. 1 is a flow chart of a communication method according to an embodiment of the present disclosure. Figure 5As shown, the method involved in the embodiment of the present disclosure is used in a communication system 100, and the method includes:

[0350] Step S5101, the terminal 101 determines a pattern of time domain resources occupied by an uplink channel and a downlink channel corresponding to the terminal based on a protocol agreement or first information; wherein the uplink channel and the downlink channel are located in a time division duplex TDD frame.

[0351] The optional implementation of step S5101 can refer to the above Figure 2A , Figure 3A-3B , Figure 4A Any one or more steps in the embodiments, and Figure 2A , Figure 3A-3B , Figure 4A Other related parts in the embodiments involved.

[0352] In some embodiments, the above method may include the above method of embodiments of the communication system side, terminal side, network device side, etc., which will not be repeated here.

[0353] In this implementation mode or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementation modes or other examples.

[0354] The following is an exemplary introduction to the methods described in the above embodiments.

[0355] In some embodiments, the TDD pattern can be determined based on protocol presets (described from the perspective of eNB / terminal). The protocol can predefine the TDD pattern and implement basic uplink and downlink transmission based on the preset pattern. Specifically, there are two different ways:

[0356] Direction 1: The protocol presets a fixed pattern, and different systems / cases / scenarios all adopt this fixed pattern. The candidate pattern preset by the protocol is at least one of the following embodiments: embodiments #1, 2, ..., #10.

[0357] Implementation: The pattern is repeated in a fixed periodic structure in the time domain to form a complete TDD frame structure. By presetting a unified pattern in the protocol, the eNB and UE obtain the TDD frame structure through the pattern and determine their uplink and downlink resources accordingly.

[0358] Direction 2: The protocol presets multiple patterns, and one of the patterns is determined based on an implicit method (for example, based on the ephemeris information broadcast by the SIB message, or the satellite type, etc.). The candidate pattern preset by the protocol is as follows: Figure 2B-2K At least one of the embodiments shown.

[0359] Implementation: The TDD frame structure is constructed based on the repeated transmission of the pattern. When the UE accesses, it determines the currently used pattern based on implicit information, and then constructs a complete TDD frame structure according to the repeated transmission of the pattern, and determines its uplink and downlink resources accordingly.

[0360] In some embodiments, the TDD pattern can be determined based on the configuration / indication signaling of the eNB. The eNB can directly configure the TDD pattern by means of signaling instructions. This method has strong flexibility and can adjust the uplink and downlink time slot configuration in real time to adapt to complex or highly variable business needs. The specific solution is as follows:

[0361] Indication parameters

[0362] Solution #1: The eNB configuration / indication signaling indicates at least one parameter in at least one of the following parameter sets to define the TDD Pattern:

[0363] Set #1 (the first parameter set in the above embodiments): time period, starting position of D, starting position of U, duration of D and U.

[0364] time period: defines the period N of the TDD pattern (unit: radio frame or ms), that is, the time period of pattern repetition. The position of the first radio frame in each period is determined by the following formula: SFN mod N = 0.

[0365] D start position: Downlink start position (in slot, subframe, or ms), specified in the following two ways:

[0366] Opt.1: The starting position of D is an offset relative to the starting position / ending position of the UL time domain unit within one cycle;

[0367] Opt.2: The starting position of D is an offset relative to a time domain reference point within a period. For example, the time domain reference point is subframe#0 of the first system frame within a specific period N, that is, the starting position of D shown is an offset relative to subframe#0 of the first system frame in the current period; or, the time domain reference point is the Mth slot within a TDD pattern period.

[0368] U start position: Uplink start position (in slots, subframes, or ms and so on), specified in the following two ways:

[0369] Opt.1: The starting position of U is an offset relative to subframe#0 of the first system frame in the current cycle, or an offset relative to a time reference point in a cycle;

[0370] Opt.2: The starting position of U is an offset relative to the starting / ending position of D.

[0371] D / U duration: the total duration of DL / UL transmission in TDD mode (unit: slot, subframe, orms), which controls the resource distribution of uplink and downlink time slots. The number of consecutive D or U time domain unit windows (segments) within one cycle can be one or more (the number of time slot segments / subframe segments is multiple, which is similar to embodiment #2 in TDD pattern)

[0372] Note: In this method, the guard period is the symbol between the end position of D and the start position of U, or the symbol between the end position of U and the start position of D.

[0373] As an example, some configuration examples of set#1 and examples of specific TDD patterns under this parameter configuration can be found in Figure 2G-2I The embodiment shown.

[0374] Set #2 (the second parameter set in the above embodiments): time period, starting position of D or starting position of U (only one of them is defined), guard period, duration of D, duration of U. Among them,

[0375] time period: defines the period N of the TDD pattern (unit: radio frame or ms), that is, the time period of pattern repetition. The position of the first radio frame in each period is determined by the following formula: SFN mod N = 0.

[0376] The starting position of D or the starting position of U: the starting position of a continuous downlink resource or uplink resource within a period (unit: slot, subframe, or ms), which can be specified in the following two ways:

[0377] Opt.1: The starting position of D or U is an offset relative to the starting position / ending position of the UL time domain unit within a period; or an offset relative to the starting position or ending position of the guard period, which can be left or right;

[0378] Opt.2: The starting position of the D or U is an offset relative to a time domain reference point within a period. For example, the time domain reference point is subframe#0 of the first system frame within a specific period N, that is, the starting position of D shown is an offset relative to subframe#0 of the first system frame within a specific period; or, the time domain reference point is the Mth slot within a TDD pattern period.

[0379] guard period: The duration of the guard period is the total duration of the guard period transmission in TDD mode, in slot, subframe, or ms; the starting position of the guard period can be preset by the protocol or indicated by the eNB. For example, the protocol preset method can be that the starting position of the guard period can be defined as the end position of U + 1 symbol, or the end position of D + 1 symbol, or the starting position of U - guard period duration, or the starting position of D - guard period duration. The eNB indication is to indicate a value, and the value is an offset relative to the time domain reference point within a period.

[0380] D / U duration: the total duration of DL / UL transmission in TDD mode (unit: slot, subframe or ms), which controls the resource distribution of uplink and downlink time slots.

[0381] Note: In this method, the starting position of U / D can be defined by the starting position of D / U and the guard period. For example, it is known that D and guard period are determined based on gNB indication, D is an offset based on the first subframe in the period, and the starting position of the guard period is the next time domain symbol of the end position of D. Then the uplink starting position (in slot, subframe, or ms) can be an offset relative to the starting position of the guard period. Alternatively, it is known that D and guardperiod are determined based on gNB indication, where the starting position of the guard period is an offset relative to the starting time of the period, and the time domain position of the guard period is determined based on the guard period duration, and D is an offset relative to the end position of the guardperiod. For example, the starting position of D is the next symbol of the guard period, and the location of D can be determined based on the duration of D. Furthermore, the end position of U can be defined as the time domain symbol before the start position of the guard period. At the same time, based on the duration of U, the location of U can be determined. Thus, the time domain resource locations of all D and U within a TDD cycle are determined. In this way, the parameters indicated by the eNB include: the duration of D and U, the guard period duration, and the start point of the guard period.

[0382] As an example, some configuration examples of set#2 and examples of specific TDD patterns under this parameter configuration can be found in Figures 2J-2K The embodiment shown.

[0383] In some embodiments, the TDD pattern is determined based on eNB configuration or indication + protocol preset mode. It can be that some parameters are determined based on eNB configuration or indication, and some parameters are determined based on protocol preset values ​​or preset rules.

[0384] In some embodiments, the candidate value of each parameter in set#1 or set#2 is defined in at least one of the following ways, and the candidate value definition methods of different parameters may be different:

[0385] Integer indication, such as the value of Integer (1 ... X), or inter (0 ... X), an example can be as follows Figures 2H-2K As shown in the embodiment;

[0386] Enumerated value, Emumerated(a,b,c…), an example can be Figure 2G As shown in the embodiment;

[0387] Bitmap.

[0388] Parameter configuration method

[0389] In addition, optionally, based on at least one of the following configurations, a TDD pattern having multiple D / U time domain resource segments in a time domain period (wherein the D / U resources in each time domain resource segment are continuous) can be implemented. An example can be as follows: Figure 2C As shown in the embodiment.

[0390] Solution 1: Based on set#1, for at least one of the following parameters, multiple parameter values ​​can be configured, where each parameter value corresponds to a D / U time domain resource segment within a period: the starting position of D, the starting position of U, the duration of D, and the duration of U.

[0391] Solution 2: Based on set#2, for at least one of the following parameters, multiple corresponding parameter values ​​can be configured: the starting position of D / U, guard period (duration and / or start point), duration of D, duration of U (the duration of D / U is the number of continuous resources in a time domain resource segment).

[0392] Solution three: Determine multiple TDD patterns through the configuration or indication / protocol preset parameters of set#1 and / or set#2. That is, in this way, the time domain period, guard period, location of D and location of U of each pattern in the multiple patterns are determined, wherein, optionally, D and / or U is only a continuous time domain resource segment. A possible embodiment is (taking the configuration of two patterns as an example for explanation), the UE completes the specific transmission resource configuration of UL and DL in time period 1 according to the corresponding UL and DL parameter definitions in time period 1 indicated by pattern1, and completes the specific transmission resource configuration of UL and DL in time period 2 according to the corresponding UL and DL parameter definitions in time period 2 indicated by pattern2. Determine the target pattern based on pattern1 and pattern2. A possible way is that the target pattern is based on a combination of pattern1 and pattern2 to form a longer period (time period = time period 1 + time period 2), and the TDD frame Strucure is formed by repeated transmission of the time period.

[0393] In this mode, for the concatenation of several patterns: pattern#1 / 2 / …, there are two specific modes:

[0394] Method 1: The UE determines the starting position of the time period of each pattern through the indication / protocol preset of the eNB. The terminal determines the longer period of the target pattern based on the starting position of the time period of each pattern and the duration of the time period. For example, the starting radio frame of pattern#1 is SFN#1, the duration is 1 radio frame, the starting radio frame of pattern#2 is SFN#4, the duration is 2 radio frames, then the current time period of the target pattern is: SFN#1~SFN#5, and the starting position of the target pattern is the first time domain symbol position of SFN#1.

[0395] Method 2: eNB indicates that the pattern list is {pattern#1, pattern#2}, and the starting time domain position of pattern#2 is determined based on the ending time domain position of pattern#1. For example, the starting time domain position of pattern#2 is the next time domain symbol of the ending time domain position of pattern#2. Based on this, the determination of the time domain period of the target pattern only needs to be determined through the configuration of the eNB or the protocol preset: the independent time domain duration of pattern#1 and pattern#2, and the starting position of pattern#1. Another possible method is that pattern#1 and pattern#2 have the same time period, then a common time period can be determined based on the protocol preset or the configuration of the eNB, and further only the starting time domain position of pattern#1 and the time domain resource location of U and / D within pattern#1 and pattern#2 need to be determined through the configuration of the eNB or the protocol preset.

[0396] It should also be noted that, in this manner, it is not excluded that only Downlink resources are used in the time domain period of one pattern, while only Uplink resources are used in the time domain period of another pattern.

[0397] Solution #2: The configuration / indication signaling of the eNB indicates the number or index of a TDD pattern. There can be multiple TDD patterns, which are preset by the protocol.

[0398] As an example, the candidate pattern determined by the configuration / indication signaling of the eNB is as follows: Figure 2B-2K At least one of the embodiments shown.

[0399] Implementation scheme: tdd-UL-DL-ConfigurationCommon provides the subcarrier spacing configuration (determines the frequency domain configuration) and TDD patternnumber configuration (determines the specific selection of the TDD pattern) defined by referenceSubcarrierSpacing, and finds the corresponding TDD pattern through the TDD pattern number (the number or index of the TDD pattern), and constructs the TDD frame structure according to the repeated transmission of the pattern. At the UE, the pattern is found through the relevant TDD pattern number parameter index provided by tdd-UL-DL-ConfigurationCommon to indicate the TDD frame structure.

[0400] The default value of the configuration parameter is:

[0401] If the eNB does not configure the relevant parameters of the TDD pattern, the terminal determines the default TDD pattern based on the protocol preset method / value.

[0402] Configuration / indication signaling:

[0403] The configuration signaling may be SIBx-NB or UE dedicated RRC signaling.

[0404] In some embodiments, the TDD pattern may be configured via SIBx-NB, so that all terminals in the cell share the same frame structure.

[0405] Implementation: The eNB generates a SIBx-NB message containing TDD pattern configuration information and broadcasts it in the cell. The SIBx-NB contains relevant parameters of the TDD pattern, such as the pattern number (TDD pattern number) or specific pattern parameters (such as time period, DL / UL starting position, duration, etc.). All UEs that receive the SIBx-NB parse the TDD pattern parameters and set the uplink and downlink transmission time slots in their respective TDD frames according to the parameters. Based on the repetition of the TDD pattern period, the UE generates a complete TDD frame structure, thereby achieving consistent DL / UL time slot configuration within the cell.

[0406] In some embodiments, the TDD pattern may be configured via UE dedicated signaling, so that each terminal may have a separate IOT-NTN TDD frame structure.

[0407] Implementation: eNB generates dedicated RRC signaling for a specific UE, including a specific TDD pattern parameter set, and sends it directly to the UE. RRC signaling can specify the TDD pattern number, or provide detailed pattern parameters, such as downlink / uplink starting position, duration, guard period, etc. The UE that receives the RRC signaling parses the pattern parameters and generates its own TDD frame structure. Based on the pattern period, the UE dynamically switches the DL / UL time slot during transmission to meet specific service requirements.

[0408] The embodiments of the present disclosure also propose a device (also referred to as a communication device, etc.) for implementing any of the above methods. For example, a device is proposed, and the above device includes a unit or module for implementing each step performed by the terminal in any of the above methods. For another example, another 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.

[0409] It should be understood that 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. In addition, 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. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above hardware circuits can be understood as one or more processors; for example, in one implementation, the above 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 in the circuit; for example, in another implementation, the above hardware circuit can be realized by a programmable logic device (PLD), taking a field programmable gate array (FPGA) as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to realize the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of a processor calling software, or in the form of a hardware circuit, or in part by a processor calling software, and the rest by a hardware circuit.

[0410] In the disclosed embodiment, the processor is a circuit with signal processing capability. In one implementation, 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), etc.; in another implementation, the processor may realize certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and realizing the configuration of the hardware circuit may be understood as the process of the processor loading instructions to realize the functions of some or all of the above units or modules. In addition, it may also be a hardware circuit designed for artificial intelligence, which may be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0411] Fig. 6A is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. The terminal 6100 is used to execute any of the above methods. In some embodiments, Fig. 6A As shown, the terminal 6100 may include: at least one of a transceiver module 6101, a processing module 6102, etc. In some embodiments, the processing module 6102 is used to determine the time domain resource pattern occupied by the uplink channel and the downlink channel corresponding to the terminal based on the agreement of the protocol or the first information; wherein the first information is sent by the network device, and the uplink channel and the downlink channel are located in a time division duplex TDD frame. Optionally, the transceiver module is used to execute at least one of the communication steps such as sending and / or receiving executed by the terminal 101 in any of the above methods (for example, step S2101, step S3101, but not limited to this), which will not be repeated here. Optionally, the processing module is used to execute at least one of the other steps (for example, step S2102, step S3102, step S3201, but not limited to this) executed by the terminal 101 in any of the above methods, which will not be repeated here.

[0412] Figure 6B 6200 is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure. The network device 6200 is used to execute any of the above methods. In some embodiments, Figure 6B As shown, the network device 6200 may include: at least one of a transceiver module 6201, a processing module 6202, etc. In some embodiments, the transceiver module 6201 is used to send first information to the terminal, and the first information is used by the terminal to determine the time domain resource pattern occupied by the corresponding uplink channel and downlink channel; wherein the uplink channel and the downlink channel are located in a time division duplex TDD frame. Optionally, the transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S2101, step S4101, but not limited to this) executed by the network device 102 in any of the above methods, which will not be repeated here. Optionally, the processing module is used to execute at least one of the other steps executed by the network device 102 in any of the above methods, which will not be repeated here.

[0413] In some embodiments, 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. Optionally, the transceiver module may be interchangeable with the transceiver.

[0414] In some embodiments, the processing module may be a single module or may include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module.

[0415] In some embodiments, the processing module may be interchangeable with the processor, and the transceiver module may be interchangeable with the transceiver.

[0416] Fig. 7A 7100 is a schematic diagram of the structure of the communication device 7100 proposed in the embodiment of the present disclosure. The communication device 7100 can be a network device (such as an access network device, a core network device, etc.), or a terminal (such as a user device, etc.), or a chip, a chip system, or a processor that supports the network device to implement any of the above methods, or a chip, a chip system, or a processor that supports the terminal to implement any of the above methods. The communication device 7100 can be used to implement the method described in the above method embodiment, and the details can be referred to the description in the above method embodiment.

[0417] like Fig. 7AAs shown, the communication device 7100 is used to perform any of the above methods. In some embodiments, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, for example, it can be a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute the program, and process the data of the program. Optionally, the communication device 7100 is used to perform any of the above methods. Optionally, one or more processors 7101 are used to call instructions so that the communication device 7100 performs any of the above methods.

[0418] In some embodiments, the communication device 7100 further includes one or more transceivers 7102. When the communication device 7100 includes one or more transceivers 7102, the transceiver 7102 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S3101, step S4101, but not limited thereto), and the processor 7101 performs at least one of the other steps (for example, step S2102, step S3102, step S3201, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and the transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc. may be replaced with each other; the terms transmitter, transmission unit, transmitter, transmission circuit, etc. may be replaced with each other; the terms receiver, receiving unit, receiver, receiving circuit, etc. may be replaced with each other.

[0419] In some embodiments, the communication device 7100 also includes one or more memories 7103 for storing data and / or instructions. Optionally, one or more processors 7101 are used to call the instructions stored in the memory 7103 so that the communication device 7100 performs any of the above methods. Optionally, all or part of the memory 7103 may also be outside the communication device 7100. In an optional embodiment, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuit 7104 is connected to the memory 7102, and the interface circuit 7104 can be used to receive data and / or instructions from the memory 7102 or other devices, and can be used to send data and / or instructions to the memory 7102 or other devices. For example, the interface circuit 7104 can read the data and / or instructions stored in the memory 7102, and send the data and / or instructions to the processor 7101.

[0420] The communication device 7100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited thereto. Fig. 7A The communication device may be an independent device or may be part of a larger device. For example, 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, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, 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.

[0421] Figure 7B 7200 is a schematic diagram of the structure of the chip 7200 proposed in the embodiment of the present disclosure. For the case where the communication device 7100 can be a chip or a chip system, please refer to Figure 7B The structure diagram of the chip 7200 is shown, but is not limited to this.

[0422] The chip 7200 includes one or more processors 7201. The chip 7200 is configured to execute any of the above methods.

[0423] In some embodiments, the chip 7200 further includes one or more interface circuits 7202. Optionally, the terms such as interface circuit, interface, transceiver pin, etc. can be interchangeable. In some embodiments, the chip 7200 further includes one or more memories 7203 for storing data and / or instructions. Optionally, all or part of the memory 7203 can be outside the chip 7200. Optionally, the interface circuit 7202 is connected to the memory 7203, and the interface circuit 7202 can be used to receive data and / or instructions from the memory 7203 or other devices, and the interface circuit 7202 can be used to send data and / or instructions to the memory 7203 or other devices. For example, the interface circuit 7202 can read the data and / or instructions stored in the memory 7203, and send the data and / or instructions to the processor 7201.

[0424] In some embodiments, the interface circuit 7202 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S3101, step S4101, but not limited thereto). The interface circuit 7202 performs the communication steps such as sending and / or receiving in the above method, for example, means that the interface circuit 7202 performs data and / or instruction interaction between the processor 7201, the chip 7200, the memory 7203 or the transceiver device. In some embodiments, the processor 7201 performs at least one of the other steps (for example, step S2102, step S3102, step S3201, but not limited thereto).

[0425] The modules and / or devices described in the embodiments such as virtual devices, physical devices, chips, etc. can be combined or separated as needed. Optionally, some or all steps can also be performed by multiple modules and / or devices in collaboration, which is not limited here.

[0426] The present disclosure also proposes a storage medium, on which instructions are stored, and when the instructions are executed on a communication device, the communication device executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto, and it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and it may also be a temporary storage medium.

[0427] The present disclosure also proposes a program product, including a program and / or an instruction, which, when executed by a communication device, causes the communication device to execute any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0428] 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.

Claims

1. A communication method, characterized in that: The method is executed by a terminal, and includes: Determine, based on the agreement of the protocol or the first information, a pattern of time domain resources occupied by an uplink channel and a downlink channel corresponding to the terminal; The first information is sent by a network device, and the uplink channel and the downlink channel are located in a time division duplex TDD frame.

2. The method according to claim 1, characterized in that The first information is used to indicate a pattern of at least one predefined time domain resource.

3. The method according to claim 1 or 2, characterized in that: The first information includes at least one of a first parameter set and a second parameter set; The first parameter set includes at least one of the following parameters: a period of the pattern of the time domain resources; The starting position of the time domain resources occupied by the downlink channel; The starting position of the time domain resources occupied by the uplink channel; The length of the time domain resources occupied by the downlink channel; The length of the time domain resources occupied by the uplink channel; The second parameter set includes at least one of the following parameters: a period of the pattern of the time domain resources; At least one of a starting position of the time domain resources occupied by the downlink channel and a starting position of the time domain resources occupied by the uplink channel; The length of a protection period, wherein the protection period is used to indicate a minimum interval between the downlink channel and the uplink channel; The starting position of the protection period; The length of the time domain resources occupied by the downlink channel; The length of the time domain resources occupied by the uplink channel.

4. The method according to claim 3, characterized in that A period of the time domain resource pattern includes at least one time domain resource segment of a downlink channel or an uplink channel, wherein the downlink channel resources or uplink channel resources in each time domain resource segment are continuous.

5. The method according to claim 4, characterized in that Each parameter in the first parameter set has at least one configuration value, wherein each configuration value is used to determine the time domain resources occupied by a downlink channel or an uplink channel in one of the time domain resource segments in the pattern of the time domain resources; and / or, Each parameter in the second parameter set has at least one configuration value, wherein each configuration value is used to determine the time domain resources occupied by a downlink channel or an uplink channel in one of the time domain resource segments in the pattern of the time domain resources.

6. The method according to any one of claims 1 to 5, characterized in that: The first information is used to determine a pattern of multiple time domain resources, and the method further includes: The pattern of the target time domain resource of the terminal is determined to be a combination of the patterns of the multiple time domain resources.

7. The method according to any one of claims 1 to 6, characterized in that: The first information is system information, or the first information is radio control resource RRC signaling dedicated to the terminal.

8. A communication method, characterized in that: The method is performed by a network device, and the method includes: Sending first information to a terminal, where the first information is used by the terminal to determine a pattern of time domain resources occupied by corresponding uplink channels and downlink channels; The uplink channel and the downlink channel are located in a time division duplex (TDD) frame.

9. The method according to claim 8, characterized in that The first information is used to indicate a pattern of at least one predefined time domain resource.

10. The method according to claim 8 or 9, characterized in that: The first information includes at least one of a first parameter set and a second parameter set; The first parameter set includes at least one of the following parameters: a period of the pattern of the time domain resources; The starting position of the time domain resources occupied by the downlink channel; The starting position of the time domain resources occupied by the uplink channel; The length of the time domain resources occupied by the downlink channel; The length of the time domain resources occupied by the uplink channel; The second parameter set includes at least one of the following parameters: a period of the pattern of the time domain resources; At least one of a starting position of the time domain resources occupied by the downlink channel and a starting position of the time domain resources occupied by the uplink channel; The length of a protection period, wherein the protection period is used to indicate a minimum interval between the downlink channel and the uplink channel; The starting position of the protection period; The length of the time domain resources occupied by the downlink channel; The length of the time domain resources occupied by the uplink channel.

11. The method according to claim 10, characterized in that A period of the time domain resource pattern includes at least one time domain resource segment of a downlink channel or an uplink channel, wherein the downlink channel resources or uplink channel resources in each time domain resource segment are continuous.

12. The method according to claim 11, characterized in that Each parameter in the first parameter set has at least one configuration value, wherein each configuration value is used to determine the time domain resources occupied by a downlink channel or an uplink channel in one of the time domain resource segments in the pattern of the time domain resources; and / or, Each parameter in the second parameter set has at least one configuration value, wherein each configuration value is used to determine the time domain resources occupied by a downlink channel or an uplink channel in one of the time domain resource segments in the pattern of the time domain resources.

13. The method according to any one of claims 8 to 12, characterized in that: The first information is used to determine patterns of multiple time domain resources, and the pattern of the target time domain resource of the terminal is a combination of the patterns of the multiple time domain resources.

14. The method according to any one of claims 8 to 13, characterized in that: The first information is system information, or the first information is radio control resource RRC signaling dedicated to the terminal.

15. A communication method, characterized in that: The method comprises: The terminal determines, based on the agreement of the protocol or the first information, a pattern of time domain resources occupied by an uplink channel and a downlink channel corresponding to the terminal; The first information is sent by a network device, and the uplink channel and the downlink channel are located in a time division duplex TDD frame.

16. A communication device, characterized in that: The communication device is used to execute the communication method according to any one of claims 1-7 and 8-14.

17. A communication system, characterized in that: The invention comprises a terminal and a network device, wherein the terminal is configured to implement the communication method according to any one of claims 1 to 7, and the network device is configured to implement the communication method according to any one of claims 8 to 14.

18. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the communication method according to any one of claims 1 to 7 and 8 to 14.

19. A program product, comprising at least one of a program and an instruction, characterized in that: When at least one of the program and the instruction is executed by the communication device, the communication method described in any one of claims 1-7 and 8-14 is implemented.

Images