WO2026000147A1 - Communication method, communication system, and storage medium - Google Patents

Abstract

The present disclosure provides a communication method, a device, and a storage medium. The method is executed by a terminal and comprises: receiving first information sent by a network device, the first information being used for indicating that the terminal needs to perform a target operation, and the target operation being related to a conflict during uplink and downlink transmissions of the terminal; and determining a first timing advance (TA) for performing the target operation. A TA for performing the target operation can be determined, thereby preventing inconsistency between TA information used by the terminal and a TA used by a base station, and avoiding the conflict problem during uplink and downlink transmissions of the terminal.

Description

A communication method, a communication system, and a storage medium Technical Field

This disclosure relates to the field of communication technology, and in particular to a communication method, a communication system, and a storage medium.

Background Technology

In satellite communication systems, terminals with reduced capacity (Redcap) that operate in half-duplex-frequency division duplex (HD-FDD) can access non-terrestrial networks (NTNs). However, there are conflicts in uplink and downlink transmissions for Redcap terminals operating in HD-FDD.

Summary of the Invention

This disclosure proposes a communication method, a communication device, a communication system, and a storage medium.

According to a first aspect of the present disclosure, a communication method is proposed, executed by a terminal, the method comprising: receiving first information sent by a network device, the first information indicating that the terminal needs to perform a target operation, the target operation being related to a conflict in the uplink and downlink transmission process of the terminal; and determining a first timing advance (TA) for performing the target operation.

In the above method, by determining the first timing advance (TA) to determine the time to execute the target operation, conflicts between the terminal during uplink and downlink transmission can be avoided.

According to a second aspect of the present disclosure, a communication method is proposed, which is executed by a network device. The method includes: sending first information to a terminal, the first information being used to instruct the terminal to perform a target operation, the target operation being related to a conflict in the uplink and downlink transmission process of the terminal.

In the above method, the terminal can be instructed to perform the target operation through the first information, thereby avoiding conflicts between the terminal during uplink and downlink transmission.

According to a third aspect of the present disclosure, a terminal is provided, including a transceiver module for receiving first information sent by a network device, the first information indicating that the terminal needs to perform a target operation, the target operation being related to a conflict during uplink and downlink transmission of the terminal; and a processing module for determining a first timing advance (TA) for performing the target operation.

According to a fourth aspect of the present disclosure, a network device is provided, including a transceiver module for sending first information to a terminal, the first information being used to instruct the terminal to perform a target operation, the target operation being related to a conflict in the uplink and downlink transmission process of the terminal.

According to a fifth aspect of the present disclosure, a communication device is provided, comprising: one or more processors; wherein the one or more processors are configured to invoke instructions to cause the communication device to perform a method as described in any of the first aspects of the present disclosure, or to perform a method as described in any of the second aspects of the present disclosure.

According to a sixth aspect of the present disclosure, a communication system is proposed, including a network device and a terminal, wherein the terminal is configured to implement the method of the first aspect, and the network device is configured to implement the method of the second aspect.

According to a seventh aspect of the present disclosure, a storage medium is provided that stores instructions which, when executed on a communication device, cause the communication device to perform a method as described in either the first or second aspect.

Attached Figure Description

The above and/or additional aspects and advantages of this disclosure will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, in which:

Figure 1 is a schematic diagram of the architecture of some communication systems provided in the embodiments of this disclosure;

Figure 2 is an interactive schematic diagram of a communication method provided in an embodiment of this disclosure;

Figures 3a-3c are schematic flowcharts of some communication methods provided in the embodiments of this disclosure;

Figures 4a-4c are schematic flowcharts of some other communication methods provided in the embodiments of this disclosure;

Figure 5 is a flowchart illustrating some other communication methods provided in the embodiments of this disclosure;

Figure 6a is a schematic diagram of the structure of a terminal provided in an embodiment of this disclosure;

Figure 6b is a schematic diagram of the structure of a network device provided in an embodiment of this disclosure;

Figure 7a is a schematic diagram of the structure of a communication device provided in an embodiment of this disclosure;

Figure 7b is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure.

Detailed Implementation

This disclosure provides a communication method, communication device, communication system, and storage medium.

In a first aspect, embodiments of this disclosure propose a communication method executed by a terminal, the method comprising: receiving first information sent by a network device, the first information being used to indicate that the terminal needs to perform a target operation, the target operation being related to a conflict between the terminal and the uplink/downlink transmission process, and determining a first timing advance (TA) for performing the target operation.

In the above embodiments, by determining the first timing advance (TA) to determine the time for executing the target operation, conflicts between the terminal during uplink and downlink transmission can be avoided.

In conjunction with some embodiments of the first aspect, in some embodiments, the collisions of the terminal during uplink and downlink transmission include at least one of the following: collisions between dynamically scheduled transmission and semi-static pre-configured transmission in the same time unit; collisions between dynamically scheduled transmission/reception and dynamically scheduled reception/transmission in the same time unit; collisions between semi-static pre-configured transmission/reception and semi-static pre-configured reception/transmission in the same time unit; collisions between Synchronous Broadcast Block (SSB) and uplink transmission in the same time unit, wherein uplink transmission includes at least one of semi-static pre-configured uplink transmission and dynamically scheduled uplink transmission; and collisions between valid random access opportunity (RO) or Msg.A PUSCH and downlink reception in the same time unit, wherein downlink reception includes at least one of semi-static pre-configured downlink reception and dynamically scheduled downlink reception.

In the above embodiments, the type of collision during uplink and downlink transmission of the terminal can be determined.

In conjunction with some embodiments of the first aspect, in some embodiments, the target operation includes at least one of the following: a first operation for determining available time units in dynamic scheduling and/or semi-static scheduling; a second operation for determining unavailable time domain symbol positions; and a third operation for determining time unit information for uplink transmission or downlink reception.

In the above embodiments, the target operation can be determined, which helps to avoid conflicts between the terminal in uplink and downlink transmission.

In conjunction with some embodiments of the first aspect, in some embodiments, determining the first timing advance (TA) for performing the target operation includes: determining the first TA based on predefined rules.

In the above embodiments, the first timing advance TA can be determined, which facilitates the determination of the TA for the target operation and helps to avoid conflicts between the terminal in uplink and downlink transmission.

In conjunction with some embodiments of the first aspect, in some embodiments, determining the first TA based on predefined rules includes at least one of the following: determining the TA last reported by the terminal to the network device as the first TA; determining the terminal's TA based on the configuration information sent by the network device and the terminal's location information, and determining it as the first TA; determining the TA based on the ephemeris information broadcast by the network device, and determining it as the first TA; determining the TA based on the timing offset Koffset value broadcast by the network device, and determining it as the first TA; determining the TA based on the target timing parameters broadcast by the network device, and determining it as the first TA.

In the above embodiments, the first timing advance TA can be determined, which facilitates the determination of the TA for the target operation and helps to avoid conflicts between the terminal in uplink and downlink transmission.

In conjunction with some embodiments of the first aspect, in some embodiments, determining the first timing advance (TA) for performing the target operation includes: receiving a second TA sent by the network device via a scheduling instruction or higher-layer signaling; and determining the first TA based on the second TA.

In the above embodiments, the first TA can be determined according to the instructions of the network device, which facilitates the determination of the TA for the target operation and helps to avoid conflicts between the terminal in uplink and downlink transmission.

In conjunction with some embodiments of the first aspect, in some embodiments, determining the first TA based on the second TA sent by the network device includes at least one of the following: determining the second TA as the first TA; adjusting the TA determined by the terminal based on the second TA, and determining the adjusted TA as the first TA.

In the above embodiments, the first TA can be determined according to the instructions of the network device, which facilitates the determination of the TA for the target operation and helps to avoid conflicts between the terminal in uplink and downlink transmission.

In some embodiments, in conjunction with the first aspect, the method further includes: determining that the terminal supports the TA reporting function; and sending a first TA to the network device.

In the above embodiments, when the terminal supports TA reporting, it reports the TA to the network device, which makes it easier for the network device to determine the terminal's TA, so as to achieve consistency between the TA of the terminal and the network device, and to avoid conflicts between the terminal in uplink and downlink transmission.

In conjunction with some embodiments of the first aspect, in some embodiments, the second TA is a TA determined by the network device, or a TA obtained by the network device after adjusting the TA reported by the terminal.

In the above embodiments, the terminal can report the TA (Transmission Aspect Ratio), which allows the network device to adjust the TA based on the reported TA, thereby ensuring that the TA of the terminal and the network device are consistent and avoiding conflicts between the terminal in uplink and downlink transmissions.

Secondly, embodiments of this disclosure propose a communication method executed by a network device, the method comprising: sending first information to a terminal, the first information being used to instruct the terminal to perform a target operation, the target operation being related to a conflict in the uplink and downlink transmission process of the terminal.

In the above embodiments, the terminal can be instructed to perform the target operation through the first information, thereby avoiding conflicts between the terminal during uplink and downlink transmission.

In conjunction with some embodiments of the second aspect, in some embodiments, the collisions of the terminal during uplink and downlink transmission include at least one of the following: collisions between dynamically scheduled transmission and semi-static pre-configured transmission in the same time unit; collisions between dynamically scheduled transmission/reception and dynamically scheduled reception/transmission in the same time unit; collisions between semi-static pre-configured transmission/reception and semi-static pre-configured reception/transmission in the same time unit; collisions between Synchronous Broadcast Block (SSB) and uplink transmission in the same time unit, wherein uplink transmission includes at least one of semi-static pre-configured uplink transmission and dynamically scheduled uplink transmission; and collisions between valid random access opportunity (RO) or Msg.A PUSCH and downlink reception in the same time unit, wherein downlink reception includes at least one of semi-static pre-configured downlink reception and dynamically scheduled downlink reception.

In the above embodiments, the type of collision during uplink and downlink transmission of the terminal can be determined.

In conjunction with some embodiments of the second aspect, in some embodiments, the target operation includes at least one of the following: a first operation for determining available time units in dynamic scheduling and/or semi-static scheduling; a second operation for determining unavailable time domain symbol positions; and a third operation for determining time unit information for uplink transmission or downlink reception.

In the above embodiments, the target operation can be determined, which helps to avoid conflicts between the terminal in uplink and downlink transmission.

In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes at least one of the following: sending configuration information to the terminal, the configuration information being used by the terminal to determine a first timing action (TA) for performing the target operation; broadcasting ephemeris information, the ephemeris information being used by the terminal to determine the first TA for performing the target operation; broadcasting a timing offset (Koffset) value, the Koffset value being used by the terminal to determine the first TA for performing the target operation; broadcasting target timing parameters, the target timing parameters being used by the terminal to determine the first TA for performing the target operation; and sending a second TA to the terminal via a scheduling instruction or higher-layer signaling, the second TA being used by the terminal to determine the first TA for performing the target operation.

In the above embodiments, the network device can send configuration information to the terminal to assist the terminal in determining the first TA, so as to facilitate the determination of the TA of the target operation and avoid conflicts between the terminal in uplink and downlink transmission.

In conjunction with some embodiments of the second aspect, in some embodiments, the second TA is a TA determined by the network device, or a TA obtained by the network device after adjusting the TA reported by the terminal.

In the above embodiments, the network device can adjust the TA according to the TA reported by the terminal to make the TA of the terminal and the network device consistent, so as to avoid conflicts between the terminal in uplink and downlink transmission.

In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: receiving a first TA (Target Action) sent by a terminal to perform the target operation, wherein the terminal supports TA reporting functionality.

In the above embodiments, when the terminal supports TA reporting, the network device can receive the TA reported by the terminal.

Thirdly, embodiments of this disclosure propose a terminal, including a transceiver module for receiving first information sent by a network device, the first information indicating that the terminal needs to perform a target operation, the target operation being related to a conflict during uplink and downlink transmission; and a processing module for determining a first timing advance (TA) for performing the target operation.

Fourthly, embodiments of this disclosure propose a network device including a transceiver module for sending first information to a terminal. The first information is used to instruct the terminal to perform a target operation, which is related to a conflict during uplink and downlink transmission.

Fifthly, embodiments of this disclosure provide a communication device, which includes: one or more processors; wherein the one or more processors are configured to invoke instructions to cause the communication device to perform the method of any one of the first aspects, or the method of any one of the second aspects.

In a sixth aspect, embodiments of this disclosure provide a communication system comprising: a terminal and a network device; wherein the terminal is configured to perform the method described in the first aspect and optional implementations thereof, and the network device is configured to perform the method described in the second aspect and optional implementations thereof.

In a seventh aspect, embodiments of this disclosure provide a storage medium storing computer-executable instructions; after being executed by a processor, the computer-executable instructions are capable of performing the methods described in the first aspect, the optional implementation of the first aspect, the second aspect, and the optional implementation of the second aspect.

It is understood that the aforementioned terminals, network devices, communication devices, communication systems, and storage media are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

This disclosure provides communication methods, communication devices, communication systems, and storage media. In some embodiments, the terms "communication method" and "information processing method" can be used interchangeably, as can the terms "terminal," "network device," and "communication apparatus," and the terms "information processing system" and "communication system."

This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and/or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

In the embodiments disclosed herein, "multiple" refers to two or more.

In some embodiments, the terms “at least one of”, “at least one of”, “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

The descriptions in this disclosure, such as "at least one of A, B, C..." or "A and/or B and/or C...", include the case where any one of A, B, C... exists alone, as well as the case where any combination of any of A, B, C... exists alone. Each case can exist alone. For example, "at least one of A, B, C" includes the cases of A alone, B alone, C alone, A and B combination, A and C combination, B and C combination, and A and B and C combination. For example, A and/or B includes the cases of A alone, B alone, and A and B combination.

In some embodiments, the notation "in one case A, in another case B" or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: A is executed regardless of B, i.e., A is executed in some embodiments; B is executed regardless of A, i.e., B is executed in some embodiments; A and B are selectively executed, i.e., A and B are selected for execution in some embodiments; A and B are both executed, i.e., A and B are executed in some embodiments. The same applies when there are more branches such as A, B, and C.

The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

In some embodiments, the terms “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 used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. The terms “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

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

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 communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures that replace communication between access network devices, core network devices, or network devices and terminals with communication between multiple terminals (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, uplink link, downlink link, etc., can be replaced with sidelink link.

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, core network device, or network device may also be configured to have all or some of the functions of the terminal.

In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

In some embodiments, the terms “downlink control information (DCI)”, “downlink (DL) assignment”, “DL DCI”, “uplink (UL) grant”, and “UL DCI” can be used interchangeably.

In some embodiments, the terms "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can the terms "physical uplink shared channel (PUSCH)" and "UL data".

In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

In some embodiments, terms such as "moment,""point in time,""time," and "time location" can be used interchangeably, as can "duration,""segment," and "time period." The terms "interval window,""window," and "time" can be used interchangeably.

In some embodiments, “get,” “obtain,” “get,” “receive,” “transmit,” “bidirectional transmission,” and “send and/or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, processing and obtaining on their own, or autonomously implementing, among other meanings.

In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and/or receive” can be used interchangeably.

In some embodiments, "pre-defined" or "pre-set" can be interpreted as pre-specified in an agreement or the like, or as a device or the like performing a pre-set action.

In some embodiments, determining can be interpreted as judging, deciding, judging, calculating, computing, processing, deriving, investigating, searching, looking up, searching, querying, ascertaining, receiving, transmitting, inputting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, considering, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but is not limited to these.

In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values (e.g., a comparison with a predetermined value), but is not limited thereto.

In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and/or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

In some embodiments, data, information, etc., may be obtained after obtaining user consent. To address the above-mentioned problems, this disclosure proposes an information indication method, a communication device, a communication system, and a storage medium.

Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 may include a terminal 101 and a network device 102.

In some embodiments, the terminal includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, in a 5G communication system, an evolved Node B (eNB), a next-generation evolved Node B (ng-eNB), a next-generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), and a base station controller. The base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in 6th generation mobile networks (6G), open RAN, cloud RAN, base station in other communication systems, and access node in wireless fidelity (WiFi) system are at least one of the following, but not limited to:

In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

In some embodiments, the access network device may consist of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layers of the access network device to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or all protocol layer functions are distributed in the DU and centrally controlled by the CU. Controlling DU, but not limited to this.

In some embodiments, a core network device may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), or a Next Generation Core (NGC).

In some embodiments, the aforementioned one or more network elements may include, for example, AMF, UPF, MME, etc., and may also include other network elements, such as Policy Control Function (PCF), Application Function (AF), Network Application Function (NAF), Authentication and Key Management for Applications Anchor Function (AAnF), Bootstrapping Server Functionality (BSF), Session Management Function (SMF), etc.

It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. The number and form of each main body are arbitrary. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), and Future Generation Radio Access (F). X), 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)), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems extended from them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

The emergence of new-generation Internet applications such as Augmented Reality (AR)/Virtual Reality (VR) and vehicle-to-vehicle communication has placed higher demands on wireless communication technologies, driving their continuous evolution to meet application needs. Currently, cellular mobile communication technology is in the next generation of technological evolution. A key characteristic of this next-generation technology is the need for flexible configuration to support multiple service types. Different service types have different requirements for wireless communication technologies. For example, enhanced mobile broadband (eMBB) primarily requires high bandwidth and high speed; ultra-reliable low-latency communication (URLLC) primarily requires high reliability and low latency; and massive machine-type communication (mMTC) primarily requires a large number of connections. Therefore, next-generation wireless communication systems need flexible and configurable designs to support the transmission of multiple service types.

In the research of wireless communication technology, satellite communication is considered an important aspect of the future development of wireless communication technology. Satellite communication refers to communication conducted by terrestrial radio communication equipment using satellites as relays. A satellite communication system consists of a satellite component and a ground component. The characteristics of satellite communication are: large communication range; communication can be conducted between any two points within the coverage area of the satellite's emitted radio waves; and it is less affected by land-based disasters (high reliability). As a supplement to the current terrestrial cellular communication system, satellite communication has the following advantages:

1. Extended coverage: For areas that cannot be covered by current cellular communication systems or where the cost of coverage is too high, such as oceans, deserts, and remote mountainous areas, satellite communication can be used to solve the communication problem.

2. Emergency communication: In extreme situations such as disasters like earthquakes that render cellular communication infrastructure unavailable, satellite communication can be used to quickly establish communication connections.

3. Providing industry applications: For example, for latency-sensitive services requiring long-distance transmission, satellite communication can reduce the transmission cost. Time delay.

It is foreseeable that in future wireless communication systems, satellite communication systems and terrestrial cellular communication systems will gradually achieve deep integration, truly realizing the Internet of Everything.

In satellite communication systems, terminal types supporting HD-FDD Redcap access the NTN network. For example, uplink and downlink transmission conflicts in HD-FDD Redcap can be resolved through predefined rules or based on either the base station or the terminal.

Based on the scheduling type and the type of information transmitted, collisions can be categorized into the following five types:

1. Collisions between dynamically scheduled transmissions and semi-static pre-configured transmissions within the same time unit;

2. Collisions between dynamically scheduled transmit/receive operations and dynamically scheduled receive/transmit operations within the same time unit;

3. Semi-static pre-configured transmission/reception and semi-static pre-configured reception/transmission within the same time unit;

4. Collisions between synchronization signal blocks (SSBs) and uplink transmissions (including semi-static pre-configured uplink transmissions and dynamically scheduled uplink transmissions) in the same time unit;

5. Collisions between valid random access opportunities (RACH Occasion, RO)/Msg.A PUSCH and downlink reception (including semi-static pre-configured downlink reception and dynamically scheduled downlink reception) within the same time unit.

The dynamic scheduling transmissions described in the above collision types refer to scheduling based on Downlink Control Information (DCI) indications. Uplink transmissions include the transmission of PUSCH, Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH), or Sounding Reference Signal (SRS) indicated by the DCI. Downlink transmissions include the transmission of PDSCH or Channel State Information Reference Signal (CSI-RS) indicated by the DCI. Semi-static pre-configured transmissions refer to the transmission of information within preset time-frequency resources pre-configured by Radio Resource Control (RRC) signaling. Downlink transmissions include pre-configured PDCCH (type 0/0A/1/2CSS), PDSCH, CSI-RS, or DL PRS, while uplink transmissions include pre-configured PUSCH, PUCCH, and SRS.

The relevant technologies address the above-mentioned species collisions as follows:

1. Collisions between dynamically scheduled send/receive and dynamically scheduled receive/transmit.

The dynamic scheduling strategy is determined by the network, which typically performs dynamic scheduling based on the terminal's capabilities. For HD-FDD terminals that cannot transmit and receive simultaneously, the network will not schedule the terminal to transmit and receive at the same time. Therefore, this type of collision can be resolved through network scheduling. On the terminal side, however, the terminal does not expect the received PDCCH to indicate that transmission and reception should occur in the same time unit.

2. Semi-static pre-configured transmit/receive and semi-static pre-configured receive/transmit

Similar to the collision between dynamically scheduled transmit/receive and dynamically scheduled receive/transmit, since the semi-static transmission configuration is determined by the network, the network will not pre-configure simultaneous HD-FDD transmission and reception. Therefore, on the terminal side, the terminal does not expect pre-configured information to be configured for transmission and reception in the same time unit.

3. Collisions between dynamic scheduling transmission and semi-static pre-configured transmission

Since this type of collision already exists in the Rel-15NR TDD system, HD-FDD reuses the processing method from the Rel-15TDD system.

When the pre-configured transmission is downlink reception and the dynamic scheduling is uplink transmission, if any of the scheduled uplink transmission symbols is the same as the downlink reception symbol, the current pre-configured downlink reception is abandoned.

When the pre-configured transmission is uplink sending while the dynamic scheduling is downlink receiving, it is necessary to first determine the transmission timing and then determine whether to cancel the policy based on the timing.

Assume the time corresponding to the last symbol of the CORESET to which the DCI belongs, detected by the terminal, is k. If the first symbol of the pre-configured uplink PUSCH/PUCCH falls within the time interval k and k+T _proc,2 , then the terminal will not cancel the pre-configured PUSCH/PUCCH transmission. Otherwise, the terminal will cancel the PUSCH/PUCCH transmission within the pre-configured time unit, or the actual duplicate transmission of PUSCH or PRACH transmission.

Assume the time corresponding to the last symbol of the CORESET to which the DCI belongs, detected by the terminal, is k. If the first symbol of the pre-configured SRS falls within the time interval k and k+T _proc,2 , then the terminal will not cancel the transmission from the first symbol of the SRS to the time interval k+T _proc,2 . Instead, it will cancel the transmission of the SRS after k+T _proc,2 .

This refers to the PUSCH preparation time under terminal capability 1. Specifically, it assumes that the SCS corresponding to the PDCCH used for scheduling PUCCH, PUSCH, or SRS is the minimum value between the SCS or _{u_r} corresponding to the scheduled PUCCH, PUSCH, or SRS information. Specifically, when the subcarrier spacing of PRACH is not less than 15kHz, _{u_r} is equal to the SCS corresponding to PRACH; otherwise, _{u_r} = 0.

4. Collisions between SSB and uplink transmissions (including semi-static pre-configured uplink transmissions and dynamically scheduled uplink transmissions).

This type of collision also exists in NR TDD systems, and the conclusions drawn from the handling methods in NR TDD can be considered for reuse. That is, prioritize SSB transmission and abandon pre-configured uplink transmissions. Regarding SSB and dynamically scheduled uplink transmissions, when an uplink transmission collides with an SSB, abandon the uplink transmission and prioritize SSB reception.

5. Collisions between valid RO/Msg.A PUSCH and downlink reception (including semi-statically pre-configured downlink reception and dynamically scheduled downlink reception, SSB).

Valid ROs include PRACH resources in 4-step RACH and Msg.A PRACH resources in 2-step RACH. Terminals do not always need to perform random access; often, random access is initiated only when triggered by a certain event. Therefore, establishing a fixed rule to constrain transmission would actually hinder transmission flexibility. Thus, this type of collision can be left to the terminal implementation to handle.

In the NTN scenario, the terminal's TA (Transmission Address) changes rapidly due to the satellite's fast movement. This can cause a mismatch between the TA information used by the terminal and the TA information obtained by the base station, which can affect uplink and downlink transmission collisions for terminals supporting HD-FDD.

To address the aforementioned issues, this disclosure proposes a communication method that effectively resolves uplink and downlink collisions when the TA information used by the terminal may not match the TA information obtained by the base station, thus ensuring the effectiveness of data transmission. The specific details of this method are as follows.

Figure 2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2, this embodiment of the present disclosure relates to a communication method for a communication system 100, which may include a terminal 101 and a network device 102. The method includes:

Step 2101: The network device sends configuration information to the terminal.

In some embodiments, the network device may send configuration information to the terminal, the configuration information being used by the terminal to determine the first TA to perform the target operation.

In some embodiments, for example, the network device may also configure auxiliary information for the terminal, wherein the auxiliary information may be broadcast ephemeris information, which is used by the terminal to determine the first TA for performing the target operation; or it may be broadcast timing offset Koffset value, which is used by the terminal to determine the first TA for performing the target operation; or it may be broadcast target timing parameters, which are used by the terminal to determine the first TA for performing the target operation.

In other words, network devices can configure information for terminals, and this configuration information can be used to assist the terminal in determining the first TA to perform the target operation.

Specifically, auxiliary information can be a type of configuration information, which can be included in the configuration information and sent to the terminal by the network device; or, the network device can broadcast auxiliary information, such as ephemeris information, timing offset Koffset value information, target timing parameters, etc. The terminal can obtain auxiliary information by listening to the broadcast. This disclosure does not restrict the method of obtaining auxiliary information.

In some embodiments, this step is optional. When the terminal can determine the first TA according to predefined rules, the network device may not send configuration information to the terminal, and this step can be omitted.

Step 2102: The network device sends the first information to the terminal.

In some embodiments, the first information can be used to instruct the terminal to perform a target operation, which is related to a conflict during uplink and downlink transmission. In other words, the network device can instruct the terminal to perform the target operation through the first information.

In some embodiments, conflicts between the terminal during uplink and downlink transmissions include at least one of the following:

Collision between dynamic scheduling transmission and semi-static pre-configured transmission on the same time unit;

Collisions between dynamically scheduled transmit/receive and dynamically scheduled receive/transmit within the same time unit;

Collisions between semi-static pre-configured transmit/receive and semi-static pre-configured receive/transmit within the same time unit;

Collisions between the Synchronous Broadcast Block (SSB) and uplink transmissions in the same time unit, wherein the uplink transmissions include at least one of semi-static pre-configured uplink transmissions and dynamically scheduled uplink transmissions;

The collision between a valid random access opportunity (RO) or Msg.A PUSCH and a downlink reception in the same time unit, wherein the downlink reception includes at least one of semi-static pre-configured downlink reception and dynamically scheduled downlink reception.

In some embodiments, the target operation includes at least one of the following:

The first operation is used to determine the available time units in dynamic scheduling and/or semi-static scheduling, i.e., slot counting;

The second operation is used to determine the location of unavailable time-domain symbols, i.e., invalid symbols.

The third operation is used to determine the time unit information for uplink transmission or downlink reception.

In some embodiments, this step is optional. When the terminal does not need to perform the target operation, the network device may not send the first information to the terminal, and this step may be omitted.

Step 2103: The network device sends the second TA to the terminal.

In some embodiments, the network device may send a second TA to the terminal via a scheduling instruction or higher-layer signaling. The second TA is used by the terminal to determine the first TA to perform the target operation.

In some embodiments, for example, the second TA is a TA determined by the network device.

In other words, network devices can send a target TA to a terminal, which can help the terminal determine the TA to perform the target operation based on the TA. For example, the terminal can adjust its TA based on the received TA to obtain the first TA to perform the target operation.

In some embodiments, for example, the second TA may be the TA obtained by adjusting the network device based on the TA reported by the terminal.

In other words, a network device can receive a first TA reported by a terminal and determine a second TA based on the first TA. For example, a network device can adjust the TA based on the received first TA to obtain a second TA.

In some embodiments, this step is optional, and when the terminal can determine the first TA for performing the target operation without based on the second TA, the network device may not send the second TA to the terminal.

Step 2104: The terminal determines the first timing advance TA.

In some embodiments, the terminal may determine a first timing advance TA, and the method by which the terminal determines the first TA may include at least one of the following.

Method 1

In some embodiments, determining the first timing advance (TA) for performing the target operation includes: determining the first TA based on predefined rules.

In some embodiments, the first TA is determined based on predefined rules, including at least one of the following:

The TA last reported by the terminal to the network device is determined as the first TA;

The terminal's TA is determined based on the configuration information sent by the network device and the terminal's location information, and is designated as the first TA;

The TA determined based on ephemeris information broadcast by network devices is designated as the first TA;

The timing offset Koffset value determined based on the network device broadcast is designated as the first timing offset;

The timing parameter (TA) determined based on the target timing parameters broadcast by the network device is designated as the first TA.

Optionally, the terminal can determine the most recently reported TA value and continue to use that TA as the first TA for performing the target operation.

Optionally, the terminal can determine the current TA value. For example, the terminal can determine the current TA value based on the network device configuration information and the terminal's own location information, and use this TA as the first TA to perform the target operation.

Optionally, the terminal can determine the current TA value. For example, the terminal can determine the TA based on ephemeris information broadcast by the network device and use that TA as the first TA to perform the target operation.

Optionally, the terminal can determine the current TA value. For example, the terminal can determine the TA based on the timing offset Koffset value broadcast by the network device and use that TA as the first TA for performing the target operation.

Optionally, the terminal can determine the current TA value. For example, the terminal can determine the TA based on the target timing parameters broadcast by the network device and use that TA as the first TA to perform the target operation.

Method 2

In some embodiments, determining a first timing advance (TA) for performing a target operation includes: receiving a second TA sent by a network device via a scheduling instruction or higher-layer signaling; and determining the first TA based on the second TA.

In some embodiments, determining the first TA based on the second TA sent by the network device includes at least one of the following: determining the second TA as the first TA; adjusting the TA determined by the terminal based on the second TA, and determining the adjusted TA as the first TA.

Optionally, the terminal can use the second TA sent by the network device as the TA for performing the target operation, that is, the network device can directly instruct the terminal to perform the target operation via TA.

Optionally, the terminal may receive a second TA sent by the network device, and adjust the TA calculated by the terminal according to the second TA, and determine the adjusted TA as the TA for performing the target operation, i.e., the first TA.

The TA calculated by the terminal can be obtained based on the network device's configuration information and the terminal's location information; or it can be calculated based on the ephemeris information broadcast by the network device; or it can be calculated based on the timing offset Koffset value broadcast by the network device; or it can be calculated based on the target timing parameters broadcast by the network device, etc.

Step 2105: The terminal sends the first advance timing TA to the network device.

In some embodiments, when it is determined that the terminal supports the TA reporting function, the terminal may send a first TA to the network device.

In some embodiments, when the terminal supports the TA reporting function, the terminal can report a first TA to keep it consistent with the TA of the network device. For example, after the terminal reports the first TA, the network device can adjust the TA according to the first TA reported by the terminal.

In some embodiments, when the terminal supports the TA reporting function, the terminal can trigger the terminal to report TA based on the base station's configuration information, or the terminal can decide whether to report TA and when to report it.

In some embodiments, this step is optional. When the terminal does not have TA reporting function, this step can be omitted; or when the terminal has TA reporting capability but does not report TA, this step can be omitted.

The method involved in the embodiments of this disclosure may include at least one of steps 2101 to 2105. For example, steps 2101+2102+2104, 2105, 2101+2102+2103+2104+2105, and 2101+2102+2103+2104+2105 may be implemented as independent embodiments, and steps 2101+2102+2103+2104 may be implemented as independent embodiments, but are not limited thereto.

In some embodiments, the execution order of step 2103 is not fixed. For example, when the terminal determines the first TA to perform the target operation based on the second TA, step 2103 needs to be executed before step 2104. In this case, the execution order of step 2103 can be interchanged with that of steps 2101 and 2102.

In some embodiments, the execution order of step 2103 is not fixed. For example, when the second TA is obtained by the network device by adjusting the first TA reported by the terminal, step 2103 can be executed after step 2105 above. That is, the terminal can report the determined first TA to the network device without determining the first TA based on the second TA. The network device can then adjust the first TA based on the received first TA to obtain the second TA.

In some embodiments, the execution order of steps 2101 and 2102 can be interchanged, or they can be executed simultaneously.

Figure 3a is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3a, the present disclosure relates to a communication method for a terminal, the method including:

Step 3101: Receive configuration information.

The optional implementation of step 3101 can be found in the optional implementation of step 2101 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

In some embodiments, the terminal receives configuration information sent by a network device, but is not limited thereto; it may also receive configuration information sent by other entities.

In some embodiments, the terminal obtains configuration information defined by the protocol.

In some embodiments, the terminal obtains configuration information from the upper layer(s).

In some embodiments, the terminal processes the information to obtain configuration information.

Step 3102: Receive the first information.

The optional implementation of step 3102 can be found in the optional implementation of step 2102 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

In some embodiments, the terminal receives first information sent by a network device, but is not limited thereto; it may also receive first information sent by other entities.

In some embodiments, the terminal obtains first information as defined by the protocol.

In some embodiments, the terminal obtains first information from the upper layer(s).

In some embodiments, the terminal processes the information to obtain the first information.

Step 3103: Receive the second TA.

The optional implementation of step 3103 can be found in the optional implementation of step 2103 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

In some embodiments, the terminal receives a second TA sent by a network device, but is not limited thereto; it may also receive a second TA sent by other entities.

In some embodiments, the terminal obtains a second TA as defined by the protocol.

In some embodiments, the terminal obtains the second TA from the upper layer(s).

In some embodiments, the terminal performs processing to obtain a second TA.

Step 3104: The terminal determines the first TA.

The optional implementation of step 3104 can be found in the optional implementation of step 2104 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

Step 3105: Send the first TA.

The optional implementation of step 3105 can be found in the optional implementation of step 2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

In some embodiments, the network device may receive a first TA.

In some embodiments, the terminal may send a first TA to a network device, but is not limited thereto; the terminal may also send a first TA to other entities.

Figure 3b is a flowchart illustrating a method according to an embodiment of the present disclosure. As shown in Figure 3b, the present disclosure relates to a communication method for a terminal, the method comprising:

Step 3201: Receive configuration information.

The optional implementation of step 3201 can be found in step 2101 of Figure 2, the optional implementation of step 3101 of Figure 3a, and other related parts in the embodiments involved in Figures 2 and 3a, which will not be repeated here.

Step 3202: Receive the first information.

The optional implementation of step 3202 can be found in step 2102 of Figure 2, the optional implementation of step 3102 of Figure 3a, and other related parts in the embodiments involved in Figures 2 and 3a, which will not be repeated here.

Step 3203: The terminal determines the first TA.

The optional implementation of step 3203 can be found in step 2104 of Figure 2, the optional implementation of step 3104 of Figure 3a, and other related parts in the embodiments involved in Figures 2 and 3a, which will not be repeated here.

Figure 3c is a flowchart illustrating a method according to an embodiment of the present disclosure. As shown in Figure 3c, the present disclosure relates to a communication method for a terminal, the method comprising:

Step 3301: Receive the first information.

The optional implementation of step 3301 can be found in the optional implementations of step 2102 in Figure 2, step 3102 in Figure 3a, step 3202 in Figure 3b, and other related parts in the embodiments involved in Figures 2, 3a, and 3b, which will not be repeated here.

Step 3302: The terminal determines the first TA.

The optional implementation of step 3302 can be found in the optional implementation of step 2104 in Figure 2, step 3104 in Figure 3a, step 3203 in Figure 3b, and other related parts in the embodiments involved in Figures 2, 3a, and 3b, which will not be repeated here.

Figure 4a is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4a, the present disclosure relates to a communication method for a network device, the method comprising:

Step 4101: Send configuration information.

The optional implementations of step 4101 can be found in the optional implementations of step 2101 in Figure 2, step 3101 in Figure 3a, step 3201 in Figure 3b, and other related parts in the embodiments involved in Figures 2, 3a, and 3b, which will not be repeated here.

In some embodiments, the terminal may receive configuration information.

In some embodiments, the network device may send configuration information to the terminal, but it is not limited to this; the network device may also send configuration information to other entities.

Step 4102: Send the first message.

The optional implementation of step 4102 can be found in the optional implementations of step 2102 in Figure 2, step 3102 in Figure 3a, step 3202 in Figure 3b, and other related parts in the embodiments involved in Figures 2, 3a, and 3b, which will not be repeated here.

In some embodiments, the terminal may receive first information.

In some embodiments, the network device may send first information to the terminal, but is not limited thereto; the network device may also send first information to other entities.

Step 4103: Send the second TA.

The optional implementation of step 4103 can be found in step 2103 of Figure 2, the optional implementation of step 3103 of Figure 3a, and other related parts in the embodiments involved in Figures 2 and 3a, which will not be repeated here.

In some embodiments, the terminal may receive a second TA.

In some embodiments, the network device may send a second TA to the terminal, but is not limited thereto; the network device may also send TAs to other entities. Second TA.

Step 4104: Receive the first TA.

The optional implementation of step 4104 can be found in the optional implementations of step 2105 in Figure 2, step 3105 in Figure 3a, step 3204 in Figure 3b, and other related parts in the embodiments involved in Figures 2, 3a, and 3b, which will not be repeated here.

In some embodiments, the network device receives a first TA sent by a terminal, but is not limited thereto; it may also receive a first TA sent by other entities.

In some embodiments, the network device obtains a first TA as defined by the protocol.

In some embodiments, the network device processes data to obtain a first TA.

Figure 4b is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4b, the present disclosure relates to a communication method for a terminal, the method comprising:

Step 4201: Send configuration information.

The optional implementations of step 4201 can be found in step 2101 of Figure 2, step 3101 of Figure 3a, step 3201 of Figure 3b, optional implementations of step 4101 of Figure 4a, and other related parts in the embodiments involved in Figures 2, 3a, 3b, and 4a, which will not be repeated here.

Step 4202: Send the first message.

Optional implementations of step 4202 can be found in step 2102 of Figure 2, step 3102 of Figure 3a, step 3202 of Figure 3b, optional implementations of step 4102 of Figure 4a, and other related parts in the embodiments involved in Figures 2, 3a, 3b, and 4a, which will not be repeated here.

Figure 4c is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 4c, the present disclosure relates to a communication method for a terminal, the method comprising:

Step 4301: Send the first message.

The optional implementation of step 4301 can be found in step 2102 of Figure 2, step 3102 of Figure 3a, step 3202 of Figure 3b, step 4102 of Figure 4a, step 4202 of Figure 4b, and other related parts in the embodiments involved in Figures 2, 3a, 3b, 4a, and 4b, which will not be repeated here.

Figure 5 is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 5, the present disclosure relates to a communication method for a communication system, which includes a network device and a terminal. The method includes:

Step 5101: The network device sends the first information to the terminal.

The optional implementation of step 5101 can be found in step 2102 of Figure 2, step 3102 of Figure 3a, step 3202 of Figure 3b, step 4102 of Figure 4a, step 4202 of Figure 4b, step 4301 of Figure 4c, and other related parts in the embodiments involved in Figures 2, 3a, 3b, 4a, 4b, and 4c, which will not be repeated here.

Step 5102: The terminal determines the first timing advance TA.

The optional implementations of step 5102 can be found in step 2104 of Figure 2, step 3104 of Figure 3a, step 3203 of Figure 3b, step 3302 of Figure 3c, and other related parts in the embodiments involved in Figures 2, 3a, 3b, and 3c, which will not be repeated here.

The following is an exemplary description of the above method.

The method illustrated in this disclosure relates to a method for NTN collision avoidance, in which a terminal can determine the TA value used by the terminal during data transmission based on a predefined method or by receiving base station signaling.

The method will be explained and illustrated below through specific examples.

Example 1: Predefined timing advance value.

In this approach, the terminal determines the TA value used to execute the target operation based on predefined rules. The target operation can be an operation that involves counting the number of available slots or determining the location of an invalid symbol.

In one implementation, when a terminal is configured to support TA reporting, the terminal can trigger TA reporting based on the base station's configuration information or decide independently whether to perform TA reporting.

The terminal determines the most recently reported TA value.

The terminal determines its current TA value based on the auxiliary information configured by the base station and its own location information.

Once the terminal determines that it needs to perform a target operation, such as slot counting or invalid symbol determination, based on the configuration information received from the base station, it determines the TA value to use when performing the target operation. For example, the predefined rule could be that the terminal uses the most recently reported TA value as the TA value to perform the target operation.

In another implementation, when the terminal is not configured with the TA reporting function, the terminal receives the base station's configuration information to determine the timing advance value set by the base station.

In one implementation, the terminal can determine the set TA value based on the ephemeris information broadcast by the base station.

In another implementation, the terminal can calculate the set TA value based on the cell-specific Koffset value broadcast by the base station.

The terminal determines the current TA value.

The terminal determines that it needs to perform a target operation, such as slot counting or invalid symbol determination, based on the configuration information received from the base station. The terminal then determines the TA value to use when performing the target operation based on predefined rules. For example, the predefined rules could be timing advance values determined by the terminal.

Example 2: The timing advance value used by the terminal based on scheduling instructions or higher-level signaling configuration.

The terminal determines that it supports the target operation, which can be either available slot counting or invalid symbol determination. Whether the terminal supports the target operation can be determined by the configuration of the receiving base station.

The terminal receives the scheduling instructions from the base station and determines the timing advance value to be used to execute the target operation.

When the terminal determines that the available slot counting or invalid symbol determination configuration is enabled, it determines the timing advance value for performing the target operation based on the TA value notified by the base station.

In summary, the above embodiments of this solution provide a method for resolving uplink and downlink transmission collisions in HD-FDD terminals of satellite communication systems. This method can effectively address the issue of uplink and downlink collisions when the TA information used by the terminal may not match the TA information of the terminal obtained by the base station, thus ensuring the effectiveness of data transmission.

The method is as follows: Figure 6a is a schematic diagram of the structure of the terminal 101 proposed in this embodiment. As shown in Figure 6a, the terminal 101 includes: a transceiver module 6101, used to receive first information sent by a network device, the first information being used to indicate that the terminal needs to perform a target operation, the target operation being related to the conflict in the uplink and downlink transmission process of the terminal; optionally, the transceiver module is used to perform at least one of the transmission-reception related steps (e.g., steps 2101, 2102, 2103, 2105, etc., but not limited thereto) performed by the terminal 101 in any of the above methods, which will not be described in detail here.

In some embodiments, terminal 101 further includes: processing module 6102, configured to determine a first timing advance TA for performing the target operation; optionally, the processing module is configured to perform at least one of the processing-related steps (e.g., step 2104, but not limited thereto) performed by terminal 101 in any of the above methods, which will not be described in detail here.

In some embodiments, the transceiver module can also be used to receive configuration information.

In some embodiments, the transceiver module can also be used to receive a second TA.

In some embodiments, the transceiver module can also be used to send a first TA.

Figure 6b is a schematic diagram of the structure of the network device 102 proposed in this embodiment. As shown in Figure 6b, the network device 102 includes: a transceiver module 6201, used to send first information to a terminal, the first information being used to instruct the terminal to perform a target operation, the target operation being related to a conflict in the uplink and downlink transmission process of the terminal; optionally, the transceiver module is used to perform at least one of the transceiver steps (e.g., steps 2101, 2102, 2103, 2105, etc., but not limited thereto) performed by the network device 102 in any of the above methods, which will not be described in detail here.

In some embodiments, the transceiver module can also be used to send configuration information.

In some embodiments, the transceiver module can also be used to send a second TA.

In some embodiments, the transceiver module can also be used to receive a first TA.

As shown in Figure 7a, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. The processor 7101 is used to invoke instructions to cause the communication device 7100 to execute any of the above methods.

In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may also be located outside the communication device 7100.

In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the communication steps such as sending and receiving in the above method are performed by the transceivers 7103, and other steps are performed by the processor 7101.

In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.

Optionally, the communication device 7100 further includes one or more interface circuits 7104, which are connected to the memory 7102. The interface circuits 7104 can be used to receive signals from the memory 7102 or other devices, and can be used to send signals to the memory 7102 or other devices. For example, the interface circuits 7104 can read instructions stored in the memory 7102 and send the instructions to the processor 7101.

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 this disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7a. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

Figure 7b is a schematic diagram of the structure of the chip 7200 proposed in an embodiment of this disclosure. For cases where the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the chip 7200 shown in Figure 7b, but it is not limited thereto.

Chip 7200 includes one or more processors 7201, which are used to invoke instructions to cause chip 7200 to perform any of the above methods.

In some embodiments, chip 7200 further includes one or more interface circuits 7202 connected to memory 7203. Interface circuits 7202 can be used to receive signals from memory 7203 or other devices, and can also be used to send signals to memory 7203 or other devices. For example, interface circuit 7202 can read instructions stored in memory 7203 and send those instructions to processor 7201. Optionally, terms such as interface circuit, interface, transceiver pin, and transceiver can be used interchangeably.

In some embodiments, chip 7200 further includes one or more memories 7203 for storing instructions. Optionally, all or part of the memories 7203 may be located outside of chip 7200.

This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 7100, cause the communication device 7100 to perform 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 not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

This disclosure also provides a program product that, when executed by the communication device 7100, causes the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

The correspondences shown in the tables of this disclosure can be configured or predefined. The values of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headers of the above tables can also use other names that the communication device can understand, and the values or representations of the parameters can also be other values or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

The predefined terms in this disclosure can be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

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

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

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

Claims (21)

A communication method, characterized in that the method is executed by a terminal, the method comprising: The terminal receives first information sent by a network device, the first information being used to instruct the terminal to perform a target operation, the target operation being related to a conflict during the uplink and downlink transmission process; Determine the first timing advance (TA) for performing the target operation. According to the method of claim 1, the collisions of the terminal during uplink and downlink transmission include at least one of the following: Collision between dynamic scheduling transmission and semi-static pre-configured transmission on the same time unit; Collisions between dynamically scheduled transmit/receive and dynamically scheduled receive/transmit within the same time unit; Collisions between semi-static pre-configured transmit/receive and semi-static pre-configured receive/transmit on the same time unit; Collisions between Synchronous Broadcast Block (SSB) and uplink transmissions in the same time unit, wherein the uplink transmissions include at least one of semi-static pre-configured uplink transmissions and dynamically scheduled uplink transmissions; The collision between a valid random access opportunity (RO) or Msg.A PUSCH and a downlink reception in the same time unit, wherein the downlink reception includes at least one of semi-static pre-configured downlink reception and dynamically scheduled downlink reception. The method according to claim 1 or 2, wherein the target operation includes at least one of the following: The first operation is used to determine the available time units in dynamic scheduling and/or semi-static scheduling; The second operation is used to determine the location of unavailable time-domain symbols; The third operation is used to determine the time unit information for uplink transmission or downlink reception. The method according to any one of claims 1 to 3, characterized in that determining the first timing advance (TA) for performing the target operation includes: The first TA is determined based on predefined rules. The method according to claim 4, wherein determining the first TA based on predefined rules includes at least one of the following: The TA last reported by the terminal to the network device is determined as the first TA; The TA of the terminal is determined based on the configuration information sent by the network device and the location information of the terminal, and is identified as the first TA; The TA determined based on the ephemeris information broadcast by the network device is designated as the first TA; The TA determined based on the timing offset Koffset value broadcast by the network device is determined as the first TA; The timing parameter (TA) determined based on the target timing parameters broadcast by the network device is designated as the first TA. The method according to any one of claims 1 to 5, characterized in that determining the first timing advance (TA) for performing the target operation includes: Receive the second TA sent by the network device via scheduling instructions or higher-layer signaling; The first TA is determined based on the second TA. According to the method of claim 6, the step of determining the first TA based on the second TA sent by the network device includes at least one of the following: The second TA is determined to be the first TA; Based on the second TA, the TA determined by the terminal is adjusted, and the adjusted TA is determined as the first TA. The method according to any one of claims 1 to 7, characterized in that the method further comprises: It is confirmed that the terminal supports the TA reporting function; Send the first TA to the network device. The method according to any one of claims 6 to 8 is characterized in that the second TA is a TA determined by the network device, or a TA obtained by the network device after adjusting the TA reported by the terminal. A communication method, characterized in that the method is executed by a network device, the method comprising: Send a first message to the terminal, the first message being used to instruct the terminal to perform a target operation, the target operation being related to a conflict in the uplink and downlink transmission process of the terminal. According to the method of claim 10, the collisions of the terminal during uplink and downlink transmission include at least the following: One item: Collision between dynamic scheduling transmission and semi-static pre-configured transmission on the same time unit; Collisions between dynamically scheduled transmit/receive and dynamically scheduled receive/transmit within the same time unit; Collisions between semi-static pre-configured transmit/receive and semi-static pre-configured receive/transmit within the same time unit; Collisions between Synchronous Broadcast Block (SSB) and uplink transmissions in the same time unit, wherein the uplink transmissions include at least one of semi-static pre-configured uplink transmissions and dynamically scheduled uplink transmissions; The collision between a valid random access opportunity (RO) or Msg.A PUSCH and a downlink reception in the same time unit, wherein the downlink reception includes at least one of semi-static pre-configured downlink reception and dynamically scheduled downlink reception. The method according to claim 10 or 11, wherein the target operation comprises at least one of the following: The first operation is used to determine the available time units in dynamic scheduling and/or semi-static scheduling; The second operation is used to determine the location of unavailable time-domain symbols; The third operation is used to determine the time unit information for uplink transmission or downlink reception. The method according to any one of claims 10 to 12, characterized in that the method further comprises at least one of the following: The terminal sends configuration information, which is used by the terminal to determine the first TA to perform the target operation; Broadcast ephemeris information, which is used by the terminal to determine the first TA to perform the target operation; The broadcast timing offset Koffset value is used by the terminal to determine the first TA for performing the target operation; Broadcast target timing parameters, which are used by the terminal to determine the first timing action (TA) for performing the target operation; A second TA is sent to the terminal via a scheduling instruction or higher-level signaling. The second TA is used by the terminal to determine the first TA to perform the target operation. According to the method of claim 13, the second TA is a TA determined by the network device, or a TA obtained by the network device after adjusting the TA reported by the terminal. The method according to any one of claims 10 to 14, characterized in that the method further comprises: The terminal receives a first TA (Transaction Transfer) sent by the terminal to execute the target operation, and the terminal supports TA reporting functionality. A terminal, characterized in that it comprises: The transceiver module is used to receive first information sent by the network device. The first information is used to instruct the terminal to perform a target operation, which is related to the conflict of the terminal in the uplink and downlink transmission process. The processing module is used to determine the first timing advance (TA) for performing the target operation. A network device, characterized in that it comprises: The transceiver module is used to send first information to the terminal, the first information being used to instruct the terminal to perform a target operation, the target operation being related to a conflict in the uplink and downlink transmission process of the terminal. A communication system, characterized in that it comprises: A terminal for performing the method as described in any one of claims 1 to 9; A network device for performing the method as described in any one of claims 10 to 15. The method according to claim 18 is characterized in that the terminal is a Redcap terminal with reduced capability supporting half-duplex frequency division multiplexing (HD-FDD), and/or the network device is a network device for non-terrestrial networks. A communication device includes: a transceiver; a memory; and a processor connected to the transceiver and the memory, respectively, configured to control the transmission and reception of wireless signals of the transceiver by executing computer-executable instructions on the memory, and capable of implementing the method of any one of claims 1-15. A computer storage medium, wherein the computer storage medium stores computer-executable instructions; the computer-executable instructions, when executed by a processor, are capable of implementing the method of any one of claims 1-15.