Communication method and apparatus

Abstract

Provided in the present application are a communication method and apparatus. The method comprises: a terminal device receiving configuration information, wherein the configuration information comprises a first period of a downlink transmission gap, the first period is equal to k*90, or the first period is equal to the sum of a second period and a third period, the second period represents a downlink transmission gap period configured by an existing protocol, a start position of the first period is located on a first downlink time unit, and the downlink transmission gap within the first period is used by the terminal device and a network device to stop downlink transmission. On the basis that the start position of the first period is located on the first downlink time unit, by configuring the first period to be equal to k*90 or the first period to be equal to the sum of the second period and the third period, sufficient downlink time units within the first period can be used for downlink transmission, and the number of instances the downlink transmission is interrupted by the downlink transmission gap can be effectively reduced, thereby realizing normal downlink transmission.

Description

A communication method and apparatus

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510366235.0, filed on March 25, 2025, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] In narrowband Internet of Things (NB-IoT) scenarios supported by non-terrestrial network (NTN) communication systems, network devices may transmit data to a particular terminal device multiple times on the downlink (DL), resulting in a longer downlink transmission time for that terminal device. This can lead to time-domain conflicts between the downlink transmissions of that terminal device and those of other terminal devices. To address this, the 3rd generation partnership project (3GPP) proposed the downlink transmission gap (DL gap). By configuring the DL gap, downlink transmissions from different terminal devices can be made to minimize time-domain conflicts.

[0005] How to properly configure downlink transmission gaps to ensure normal downlink transmission remains to be solved. Summary of the Invention

[0006] This application provides a communication method and apparatus for enabling normal downlink transmission.

[0007] Firstly, this application provides a communication method that can be executed by a terminal device or a module within the terminal device (e.g., a communication module, a circuit or chip responsible for communication functions (e.g., a modem chip, a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), a chip system, or a processor, etc.). Optionally, the method can also be implemented by a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. The following example illustrates the execution of the communication method by a terminal device. The method may include the following steps: The terminal device receives configuration information, wherein the configuration information may include a first period of a downlink transmission gap, the first period may be equal to k*90, where k is an integer greater than or equal to 1, or the first period may be equal to the sum of a second period and a third period, the second period representing the period configured or defined by an existing protocol for the downlink transmission gap, the starting position of the first period being located on a first downlink time unit, the downlink transmission gap within the first period being used for the terminal device and network device to stop downlink transmission, and the downlink time units within the first period other than the downlink transmission gap being used for the terminal device and network device to perform downlink transmission.

[0008] In this method, since the starting position of the first cycle is located in the first downlink time unit, by configuring the first cycle to be equal to k*90 or equal to the sum of the second and third cycles, there can be enough downlink time units in the first cycle for downlink transmission (for example, there are enough downlink time units in the first cycle except for downlink transmission gaps for downlink transmission between network devices and terminal devices). This makes the period configuration of the downlink transmission gap more reasonable (or appropriate), which can effectively reduce the number of times downlink transmission is interrupted (or interrupted) by downlink transmission gaps (which can be understood as downlink transmission (such as narrowband physical downlink shared channel (NPDSCH) transmission) will not be frequently interrupted by downlink transmission gaps), which helps to meet the downlink transmission needs of network devices and terminal devices, thereby enabling the normal operation of downlink transmission.

[0009] Secondly, this application provides a communication method that can be executed by a network device or a module within the network device (e.g., a communication module, a circuit or chip responsible for communication functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.). Optionally, the method can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the network device. The following example illustrates the execution of the communication method by a network device. The method may include the following steps: the network device determines configuration information, and then the network device can send the configuration information. The configuration information may include a first period of downlink transmission gaps, where the first period may be equal to k*90, where k is an integer greater than or equal to 1, or the first period may be equal to the sum of a second period and a third period. The second period represents the period configured or defined by an existing protocol for downlink transmission gaps. The starting position of the first period is located on a first downlink time unit. The downlink transmission gaps within the first period are used for the terminal device and the network device to stop downlink transmission, and the downlink time units within the first period other than the downlink transmission gaps are used for downlink transmission between the terminal device and the network device.

[0010] The technical effects achievable in the second aspect are similar to those achievable in the first aspect, and will not be elaborated upon here.

[0011] Based on the first or second aspect, in one possible implementation, the sum of the second period and the third period equals k*90.

[0012] In the above implementation, by setting the sum of the second and third cycles to k*90, the starting position of the downlink transmission gap in the first cycle can also be located on a downlink time unit (such as a DL subframe), which makes it easier for other terminal devices to monitor and perform downlink transmission at this point, and further enables each downlink transmission gap to be used normally for downlink transmission of other terminal devices.

[0013] Based on the first or second aspect, in one possible implementation, the number of downlink time units included in the downlink transmission gap is equal to the product of the first period and the first coefficient.

[0014] The above implementation ensures that the duration or downlink time units used for downlink transmission within the downlink transmission gap in the first cycle are sufficient to meet the needs of network devices for downlink transmission with other terminal devices. In contrast, traditional configurations often result in no downlink time units (e.g., DL subframes) within the downlink transmission gap, only uplink time units (e.g., DL subframes) and / or guard interval time units (e.g., GP subframes), making downlink transmission impossible or resulting in very few downlink time units within the gap, insufficient to meet the downlink transmission needs of network devices with other terminal devices. The above implementation ensures a certain number of downlink time units within the downlink transmission gap in the first cycle.

[0015] Based on the first or second aspect, in one possible implementation, the starting position of the downlink transmission gap is determined according to a first period and a first offset, wherein the first offset represents the offset between the time-domain starting position of the time-division duplex pattern and the time-domain starting position of the narrowband Internet of Things.

[0016] The above implementation provides a different way of determining the starting position of the downlink transmission gap than the traditional method. By comprehensively considering the impact of the offset between the time domain starting position of the time division duplex pattern and the time domain starting position of the narrowband Internet of Things on the starting position of the downlink transmission gap, the starting position of the downlink transmission gap can be located on the downlink time unit, which helps to ensure that the downlink transmission gap can be correctly configured and applied.

[0017] Based on the first or second aspect, in one possible implementation, the starting position of the downlink transmission gap can satisfy the following relationship: (1024n) h +10n f +floor(n s / 2))mod N=3

[0018] Where, n h n f and n s Indicates the starting position of the downlink transmission gap, n h n represents the index of the first superframe. f n represents the index of the first radio frame included in the first superframe. s This indicates the index of the first subframe included in the first wireless frame, floor() represents the floor operation, mod represents the modulo operation, the first offset is 3, and N represents the first period.

[0019] The above implementation takes into account the offset between the time-domain start position of the time-division duplex pattern and the time-domain start position of narrowband IoT, as well as the impact of superframes on the start position of the downlink transmission gap. This can ensure that the start position of the downlink transmission gap is located on the downlink time unit, which helps to ensure that the downlink transmission gap can be correctly configured and applied.

[0020] Based on the first or second aspect, in one possible implementation, one or more time units located after the downlink transmission gap in the time domain are downlink time units.

[0021] The above implementation method can ensure that when a network device needs to perform multiple downlink transmissions with a certain terminal device, the network device can immediately resume downlink transmission with that terminal device after the downlink transmission interval ends.

[0022] Thirdly, this application provides a communication device that implements the functions described in the first and second aspects above. For example, the communication device includes modules, units, or means corresponding to the operations described in the first and second aspects above. These functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software. For instance, in some examples, the communication device can be a terminal device or a module within a terminal device, and it implements the functions described in the first aspect. In other examples, the communication device can be a network device or a module within a network device, and it implements the functions described in the second aspect.

[0023] In one possible implementation, the communication device may include a transceiver unit. Optionally, the communication device may further include a processing unit. The transceiver unit can be used to transmit and receive signals to enable communication between the communication device and other devices; for example, the transceiver unit can be used to send data to other communication devices. The processing unit can be used to perform some internal operations of the communication device. The functions performed by the transceiver unit and the processing unit may correspond to the operations involved in the first and second aspects described above.

[0024] In one possible implementation, the communication device includes at least one processor, which can be coupled to a memory. The memory can store necessary computer programs or instructions for implementing the functions described in the first to second aspects above. The processor can execute the computer programs or instructions stored in the memory, causing the communication device to implement the methods in any possible implementation of any of the first to second aspects above when the computer programs or instructions are executed.

[0025] In one possible implementation, the communication device includes at least one processor and a memory, the memory of which may store necessary computer programs or instructions for implementing the functions involved in the first to second aspects described above. The at least one processor may execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible implementation of any of the first to second aspects described above.

[0026] In one possible implementation, the communication device includes at least one processor and an interface circuit (or communication interface), wherein the at least one processor is configured to communicate with other devices via the interface circuit and execute the methods in any of the possible implementations of the first to second aspects described above. The interface circuit is used to enable communication between the communication device and other communication devices, for example, to receive signals from other communication devices and transmit them to the at least one processor, or to send signals from the at least one processor of the communication device to other communication devices, such as the transmission or reception of data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0027] It is understood that, in the third aspect mentioned above, the processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. Furthermore, there can be one or more processors, and one or more memories. The memory can be integrated with the processor or separated from it. In specific implementations, the memory can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0028] Fourthly, this application provides a possible communication system, which may include the terminal equipment, network equipment, etc., mentioned in the first or second aspect above. The implementation of the relevant functions of the terminal equipment or network equipment can be found in the descriptions mentioned in the first or second aspect above, and will not be repeated here.

[0029] For example, the number of terminal devices or network devices can be one or more.

[0030] Fifthly, this application provides a computer program product comprising a computer program or instructions that, when executed on a communication device (or computer), cause the communication device (or computer) to perform the method in any possible implementation of any of the first to second aspects described above.

[0031] In a sixth aspect, this application provides a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device (or computer), cause the communication device (or computer) to perform the method in any possible implementation of any of the first to second aspects described above.

[0032] In a seventh aspect, this application provides a chip that may include at least one processor and may also include a memory (or the chip may be coupled to the memory), wherein the at least one processor executes program instructions in the memory to cause the chip to perform the methods in any possible implementation of any of the first to second aspects described above. Here, "coupling" refers to two components being directly or indirectly connected to each other, such as coupling referring to an electrical connection between two components.

[0033] Eighthly, this application also provides a chip system including at least one processor for supporting a computer device in implementing any possible implementation of the methods in any of the first to second aspects described above. In one possible implementation, the chip system further includes a memory for storing programs and data necessary for the computer device. The chip system may be composed of chips or may include chips and other discrete devices.

[0034] Based on the implementation methods provided in the above aspects, this application can be further combined to provide more implementation methods. Attached Figure Description

[0035] Figure 1 illustrates an exemplary architectural diagram of a ground-based communication system provided in an embodiment of this application;

[0036] Figure 2 illustrates a possible satellite communication system architecture provided in an embodiment of this application.

[0037] Figure 3 illustrates a schematic diagram of subframe distribution in a TDD cycle according to an embodiment of this application.

[0038] Figure 4 illustrates a flowchart of a communication method provided in an embodiment of this application;

[0039] Figure 5 illustrates a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0040] Figure 6 illustrates a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0041] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0042] The following describes the communication system architecture to which the communication method provided in this application is applicable. It should be noted that this description is for the convenience of those skilled in the art and does not constitute a limitation on the scope of protection claimed in this application.

[0043] The communication scheme provided in this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink (SL) communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th Generation (5G) mobile communication systems or new radio access technology (NR), satellite communication systems, etc. Among them, the 5G mobile communication system can include non-standalone (NSA) and / or standalone (SA) networking. The technical solution provided in this application can also be applied to future evolution communication systems. The satellite communication system can be a satellite communication system integrated with the 4th generation (4G), 5G mobile communication systems, or future communication systems, such as NTN. NTN communication systems can be, for example, satellite communication systems, or include unmanned aerial vehicles, high altitude platform stations (HAPS), and other aerial access network equipment; this application does not limit the scope of such systems.

[0044] In a communication system, one network element can send signals to or receive signals from another network element. These signals can include information, signaling, or data. The term "network element" can also be replaced with entities, network entities, devices, communication equipment, communication modules, nodes, communication nodes, etc.

[0045] For example, a terrestrial communication system may include at least one terminal device and at least one network device. The network device may send downlink signals to the terminal device, and / or the terminal device may send uplink signals to the network device. Furthermore, it is understood that if the communication system includes multiple terminal devices, the multiple terminal devices may also exchange signals with each other; that is, both the signal transmitting network element and the signal receiving network element may be terminal devices.

[0046] Figure 1 illustrates an exemplary architecture diagram of a terrestrial communication system applicable to an embodiment of this application. The communication system 100 may include network device 110 and terminal devices 101 to 106. It should be understood that the communication system 100 may include more or fewer network devices or terminal devices. Network devices or terminal devices may be hardware, functionally defined software, or a combination of both. Furthermore, terminal devices 104 to 106 may also form a communication system; for example, terminal device 105 may send downlink data to terminal device 104 or terminal device 106. Communication between network devices and terminal devices can occur through other devices or network elements. Network device 110 may send downlink data to terminal devices 101 to 106 and may also receive uplink data sent by terminal devices 101 to 106. Of course, terminal devices 101 to 106 may also send uplink data to network device 110 and may also receive downlink data sent by network device 110.

[0047] Network device 110 is a node in the radio access network (RAN), also known as a base station, RAN node (or device), RAN entity, access network device, or access node, etc. Currently, some examples of access network devices include: evolved NodeB (eNodeB), access point (AP), access point (AP) in wireless fidelity (WIFI) systems, wireless relay node, wireless backhaul node, transmission point (TP), next generation node B (gNB) in 5G networks, transmitting point (TP), transmission reception point (TRP), home base station (e.g., home evolved NodeB, or home Node B, HNB), macro base station, micro base station (also called small station), relay station, satellite station, base band unit (BBU), and other network devices in communication systems evolving after 5G. Network device 110 can also be other devices with network device functions, such as gNB, TRP, or TP in a 5G system, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system. Furthermore, network device 110 can also be a device that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), Internet of Things (IoT), machine-to-machine (M2M) communication, or other communication systems. It can also include network devices in centralized units (CU) and distributed units (DU) of cloud radio access networks (C-RAN) systems, and network devices in NTN communication systems, and can be deployed on high-altitude platforms or satellites. This application embodiment does not specifically limit this. For example, in a satellite communication system, the network device can be a satellite, or a base station device mounted on a satellite.

[0048] For example, in some possible network architectures, network devices can be CUs, DUs, CUs (control plane, CP), CUs (user plane, UP), or radio units (RUs), etc. CUs and DUs can be configured separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). In this network architecture, signaling generated by the CU can be sent to the terminal device via the DU, or signaling generated by the terminal device can be sent to the CU via the DU. The DU can directly pass the signaling through protocol layer encapsulation without parsing it to the terminal device or CU. In this network architecture, the CU is classified as a network device on the radio access network side; alternatively, the CU can also be classified as a network device on the core network side, and this application does not impose any limitations on this. For example, the functions of the Packet Data Convergence Protocol (PDCP) layer and above are located in the CU, while the functions of protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer and the Media Access Control (MAC) layer) are located in the DU. It is understood that the above division of the processing functions of the CU and DU according to protocol layers is merely an example, and other methods can also be used. For instance, the functions of protocol layers above the RLC layer are located in the CU, and the functions of protocol layers below the RLC layer are located in the DU. Alternatively, the CU or DU can be divided into those with functions of more protocol layers, or even those with partial processing functions of protocol layers.

[0049] It is understood that CU (or CU-CP and CU-UP), DU, or RU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0050] Optionally, if the network equipment adopts a CU-DU separation architecture, this CU-DU separation architecture can also be called a distributed deployment architecture, or it can adopt a CU-DU-RU separation architecture. For example, the network equipment can logically include one CU and one or more DUs. Each DU can be connected to the CU through an F1 interface, and information exchange between different DUs can be completed based on the forwarding of the CU. The CU and DU can be physically set together or physically separated, without limitation. The CU can support the functions of the Radio Resource Control (RRC) layer protocol, PDCP protocol, and Service Data Adaptation Protocol (SDAP) protocol; the DU can support the RLC layer protocol, MAC layer protocol, and some or all of the physical (PHY) layer functions. For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications. As another example, the access network equipment can logically include CU, DU, and RU. The CU and DU can be physically set together or physically separated, without limitation. The CU (Core Unit) supports RRC, PDCP, and SDAP layer protocols; the DU (Distributed Unit) supports RLC and MAC layer protocols, and some PHY layer protocols; the RU (Remote Root Unit) supports some or all PHY layer protocols. For example, the DU is primarily responsible for higher-level protocol functions such as data encryption and integrity protection, while the RU is primarily responsible for transmitting and receiving radio frequency signals. In this CU-DU-RU separation architecture, the interface between the DU and RU can be called fronthaul, the interface between the CU and DU can be called midhaul, and the interface between the CU and the core network can be called backhaul.

[0051] Terminal devices 101 to 106 are devices that provide voice or data connectivity to users. They can also be Internet of Things (IoT) devices, and are also referred to as terminals, user equipment (UE), access terminal equipment, vehicle-mounted terminals, industrial control terminals, UE units, UE stations, mobile stations, mobile stations (MS), mobile terminals (MT), remote stations, remote terminal equipment, mobile devices, UE terminal equipment, terminal equipment, wireless communication equipment, UE agents, or UE devices, etc. For example, terminal devices 101 to 106 include handheld devices and vehicle-mounted devices with wireless connectivity.Currently, terminal devices 101 to 106 can be: mobile phones, tablets, customer-premises equipment (CPE), subscriber units, satellite phones, cellular phones, smartphones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, wireless data cards, personal digital assistant (PDA) computers, wireless modems, handsets, laptop computers, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, head-mounted displays (HMDs), wireless terminals in industrial control, mobile internet devices (MIDs), vehicle-mounted terminal devices (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), and self-driving cars. Wireless terminals in various fields, including driving, remote medical care, smart grids, transportation safety, smart cities, smart homes, wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), vehicles, drones, helicopters, airplanes, factory machinery / equipment, machine-type communication (MTC) terminals, ships, and robots. Terminal devices 101 to 106 can also be other devices with terminal functions; for example, terminal devices 101 to 106 can also function as terminals in D2D communication.

[0052] Based on the description of the terrestrial communication system architecture shown in Figure 1, this application embodiment illustrates the application of a non-terrestrial network (NTN) communication system. NTN includes nodes such as satellite networks, high-altitude platforms, and unmanned aerial vehicles (UAVs), and boasts significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and freedom from geographical limitations. It has been widely applied in various fields including maritime communication, positioning and navigation, disaster relief, scientific experiments, video broadcasting, and Earth observation. Terrestrial communication systems and NTN communication systems such as satellite networks integrate, complementing each other's strengths and weaknesses, to jointly form a globally seamless, integrated sea, land, air, space, and ground communication network, meeting the ubiquitous and diverse service needs of users. In this application embodiment, NTN communication is exemplified by satellite communication, or more specifically, the NTN communication system is exemplified by a satellite communication system. Figure 2 is a schematic diagram of a possible satellite communication system architecture applicable to this application embodiment. As shown in Figure 2, this satellite communication system architecture may include at least one terminal device (e.g., terminal device 1, terminal device 2, etc.), at least one satellite (e.g., satellite 1, satellite 2, etc.) (or a base station deployed on the satellite, such as a 5G base station), a ground station, a core network (CN) (e.g., a 5G core network), and a data network (DN). The terminal device and the satellite (or the base station deployed on the satellite) can communicate via an air interface (which can be of various types, such as 5G New Radio). For example, terminal device 1 can access satellite 1 via a 5G New Radio interface. Wireless links (e.g., the Xn interface) exist between satellites (or base stations deployed on the satellite), which can be used for signaling interaction and user data transmission between base stations. For example, satellites (or base stations deployed on the satellite) can communicate via the Xn interface. The satellite and the ground station can communicate via the NG interface. The ground station can connect to the core network via the NG interface, which can be wired or wireless. The core network and the data network can communicate via the N6 interface. Satellites can typically form multiple beams, each beam similar to a cell / sector in a terrestrial mobile communication system (such as LTE / NR).

[0053] The following is a brief introduction to the equipment and interfaces included in the satellite communication system architecture.

[0054] (1) Base station: It is mainly used to provide wireless access services, schedule wireless resources to access terminal equipment, and provide reliable wireless transmission protocols and data encryption protocols. For example, a base station can be regarded as a network device 110 included in the communication system 100, or a device (such as a chip or chip system) used to implement the functions of the network device 110.

[0055] (2) Core Network: Primarily used to provide functions such as user access control, mobility management, session management, user security authentication, and billing. The core network consists of multiple functional units, which can be divided into control plane network elements (or control plane functional units) and user plane network elements (or user plane processing units). User plane network elements are responsible for the transmission of service data; for example, user plane network elements may include, but are not limited to, user plane function (UPF) network elements. Control plane network elements are responsible for the management of the mobile network; for example, control plane network elements may include, but are not limited to, access and mobility management function (AMF) network elements and session management function (SMF) network elements. AMF network elements are responsible for user access management, security authentication, and mobility management. SMF network elements are responsible for terminal device session management (including session establishment, modification, and release), UPF network element selection and reselection, terminal device Internet Protocol (IP) address allocation, Quality of Service (QoS) control, and selection of UPF network elements providing packet forwarding functions. UPF is used to manage user plane data transmission, traffic statistics, and other functions.

[0056] (3) Data Network: A data network that provides business services (such as data and / or voice services) to users. Generally, the client is located on the terminal device, and the server is located on the data network. The data network can be a private network, such as a local area network, or an external network not controlled by the operator, such as the Internet, or a dedicated network jointly deployed by the operator, such as a network that provides IP multimedia core network subsystem (IMS) services.

[0057] (4) Ground station: mainly responsible for forwarding signaling and service data between satellite and core network.

[0058] (5) 5G New Radio: refers to the wireless link between the terminal device and the satellite.

[0059] (6) Xn interface: This refers to the interface between satellites (or base stations deployed on satellites), mainly used for signaling interaction such as handover.

[0060] (7) NG interface: This refers to the interface between the satellite and the core network. It mainly exchanges non-access stratum (NAS) signaling of the core network and user service data.

[0061] In this application embodiment, network devices in a terrestrial communication system and satellites in an NTN communication system can be uniformly considered as network devices. The apparatus for implementing the functions of a network device can be a network device itself; it can also be an apparatus capable of supporting the network device in implementing that function, such as a chip system, which can be installed within the network device. The following description of the technical solutions provided in this application embodiment uses a satellite as an example to illustrate the technical solutions provided in this application embodiment. It is understood that when the method provided in this application embodiment is applied to a terrestrial communication system, the actions performed by the satellite can be applied to the base station or network device for execution.

[0062] In this application embodiment, the device for implementing the functions of the terminal device can be the terminal device itself; it can also be a device capable of supporting the terminal device in implementing the functions, such as a chip system, hardware circuit, software module, or hardware circuit plus software module. This device can be installed in the terminal device or used in conjunction with the terminal device. In this application embodiment, the chip system can be composed of chips or can include chips and other discrete devices. The technical solutions provided in this application embodiment are described using the example of a terminal device as the device for implementing the functions of the terminal device.

[0063] It should be noted that the communication system and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0064] The following is an explanation of the relevant terms used in the embodiments of this application. Unless otherwise specified, these explanations are provided to support the meaning of the relevant terms and to make the embodiments of this application easier to understand, and should not be regarded as a strict limitation of the relevant terms within the scope of protection claimed by this application.

[0065] (1) TDD cycle:

[0066] The NTN system supports two frame structures: Frequency Division Duplex (FDD) and TDD. The TDD frame structure, as shown in Table 1, consists of 10 subframes, each 1ms long, and comprises 10 radio frames. These subframes are further divided into special and ordinary subframes. Special subframes, also known as GP subframes, are divided into three time slots: downlink (or downlink pilot slot, DLPTS), guard period (GP), and uplink (or uplink pilot slot, UpPTS). Ordinary subframes are further divided into uplink (UL) subframes and downlink (DL) subframes. Uplink subframes transmit uplink control signaling and service data, while downlink subframes transmit downlink control signaling and service data. In Table 1, D represents a downlink subframe, U represents an uplink subframe, and S represents a special subframe.

[0067] Table 1

[0068] Optionally, if the number of downlink subframes in a radio frame's 10 subframes is greater than 5, the radio frame can be understood as a downlink radio frame. In special cases, all 10 subframes in a downlink radio frame are downlink subframes. Correspondingly, if the number of uplink subframes in a radio frame's 10 subframes is greater than 5, the radio frame can be understood as an uplink radio frame. In special cases, all 10 subframes in an uplink radio frame are uplink subframes.

[0069] In one possible implementation, a TDD cycle in IoT-NTN includes 9 radio frames, and the duration of a TDD cycle is 90ms. The radio frames in a TDD cycle are divided into downlink radio frames (or DL ​​frames), guard interval frames (GP frames), or uplink radio frames (UL frames). For example, a TDD cycle may include 1 DL frame, 7 GP frames, and 1 UL frame. Another example is that a TDD cycle may include 3 DL frames, 3 GP frames, and 3 UL frames. Furthermore, the number of DL frames, GP frames, and UL frames in a TDD cycle can also be (4, 3, 2), (5, 3, 1), or other values; this application embodiment does not limit this. In one possible implementation, a DL frame in a TDD cycle includes 8 DL subframes and 2 GP subframes, a UL frame in a TDD cycle includes 8 UL subframes and 2 GP subframes, and a GP frame in a TDD cycle includes 10 GP subframes.

[0070] In another possible implementation, one TDD cycle in IoT-NTN corresponds to 90ms, and one subframe corresponds to 1ms. That is, one TDD cycle includes 90 subframes, namely DL subframes, GP subframes, and UL subframes. Every 10 consecutive subframes within a TDD cycle constitute a radio frame, and one radio frame corresponds to 10ms. Therefore, a TDD cycle includes 9 radio frames. For example, as shown in Figure 3, one TDD cycle may include 8 DL subframes, 74 GP subframes, and 8 UL subframes. It is understood that the arrangement of DL frames, GP frames, and UL frames shown in Figure 3 is merely an example for illustrating the technical solution of this application and does not constitute a limitation on the arrangement of DL frames, GP frames, and UL frames.

[0071] (2) Time Unit: This can refer to one or more subframes, one or more time slots, one or more symbols, or one or more radio frames. Optionally, a time unit can also consist of one or more symbols. In this application, a time unit is taken as a time slot. A portion of a time slot can refer to symbols used for uplink transmission within that time slot. For example, symbols from one uplink / downlink switching point to the time slot boundary, or symbols used for uplink transmission from one uplink / downlink switching point to the next. For downlink transmission, a portion of a time slot can be symbols used for downlink transmission from a time slot boundary to an uplink / downlink switching point, or symbols used for downlink transmission from one uplink / downlink switching point to the time slot boundary, or symbols used for downlink transmission from one uplink / downlink switching point to the next. In this application, unless otherwise specified, all symbols refer to time-domain symbols. These time-domain symbols can be orthogonal frequency division multiplexing (OFDM) symbols or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols.

[0072] Currently, when a 90ms TDD mode is introduced in NB-IoT scenarios, only 8 subframes are used for downlink transmission within 90ms. Therefore, according to the traditional downlink transmission gap configuration, a downlink transmission gap is set up for each subframe used for downlink transmission (e.g., 8 DL subframes). This means that the actual downlink transmission only occurs for a few DL subframes before stopping, resulting in frequent interruptions to downlink transmission due to downlink gaps. Furthermore, since the duration of the downlink transmission gap is determined by the period and duration coefficient of the downlink L transmission gap, the traditional downlink transmission gap configuration may result in the absence of DL subframes within the downlink transmission gap. This causes terminal devices that need to perform DL transmission during the downlink transmission gap to be unable to perform downlink transmission normally.

[0073] In view of this, this application provides a communication method to make the periodic configuration of downlink transmission gaps more reasonable, which can effectively reduce the number of times downlink transmission is interrupted by downlink transmission gaps, thereby enabling normal downlink transmission.

[0074] The specific implementation of the communication method in the embodiments of this application will be described in detail below with reference to the accompanying drawings. It is understood that this application uses network devices and terminal devices as examples of the execution subjects in the interactive illustration, but this application does not limit the execution subjects in the interactive illustration. For example, the method executed by the network device in this application can also be executed by a module applied to the network device (e.g., a communication module, a circuit or chip responsible for communication functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or by a logical node, logical module, or software capable of implementing all or part of the functions of the network device, or it can also be implemented through a combination of hardware and software. Similarly, the method executed by the terminal device in this application can also be executed by a module applied to the terminal device (e.g., a communication module, a circuit or chip responsible for communication functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or by a logical node, logical module, or software capable of implementing all or part of the functions of the terminal device, or it can also be implemented through a combination of hardware and software. For example, the network device can be network device 110 as shown in Figure 1, and the terminal device can be one of the terminal devices shown in Figure 1 (such as terminal device 101). Alternatively, the network device can be one of the satellites shown in Figure 2 (such as satellite 1), and the terminal device can be one of the terminal devices shown in Figure 2 (such as terminal device 1).

[0075] Figure 4 illustrates a flowchart of a communication method provided in an embodiment of this application. This method is applicable to the communication system architecture shown in Figure 1 or Figure 2. As shown in Figure 4, the method includes:

[0076] Step 401: Determine the configuration information for the network device.

[0077] Step 402: The network device sends configuration information. Accordingly, the terminal device receives the configuration information from the network device.

[0078] The configuration information may include the first period of the downlink transmission gap (or downlink transmission interval, or downlink transmission interval). Optionally, the first period of the downlink transmission gap can be represented by dl-GapPeriodicity.

[0079] For example, the first period may include one or more of DL subframes, UL subframes, or GP subframes. The number of DL subframes, UL subframes, and GP subframes may be one or more.

[0080] The first cycle is described below through several possible implementation methods.

[0081] Method a1: The first period equals k * 90. Where k is an integer greater than or equal to 1.

[0082] It is understandable that, when the first period equals k*90, the starting position of the first period can be located on the first downlink time unit (e.g., the first DL subframe). This allows the starting position of the downlink transmission gap within the first period to be located on a downlink time unit (e.g., a DL subframe), facilitating normal monitoring and downlink transmission by other terminal devices at this point. Furthermore, it allows the downlink transmission gap within the first period to be used normally for downlink transmission by other terminal devices.

[0083] In one possible implementation, the network device can carry a period value k*90 in the configuration information. Optionally, the unit of k*90 is milliseconds (ms). Here, 90ms can refer to the TDD period.

[0084] For example, consider k values ​​of 8, 16, 32, 64, and 128. When k = 8, k * 90 = 8 * 90 = 720. When k = 16, k * 90 = 16 * 90 = 1440. When k = 32, k * 90 = 32 * 90 = 2880. When k = 64, k * 90 = 64 * 90 = 5760. When k = 128, k * 90 = 128 * 90 = 11520. It's understandable that k can also be any other positive integer value.

[0085] Optionally, when k is 8, 16, 32, 64, and 128, the network device may carry one of {720, 1440, 2880, 5760, 11520} as the period of the downlink transmission gap in the configuration information.

[0086] The first period of the downlink transmission gap is represented by dl-GapPeriodicity. For example, k is 8, 16, 32, 64 and 128. The period form of the downlink transmission gap included in the configuration information can be seen in Example b1 and Example b2.

[0087] Example b1: dl-GapPeriodicity-r19 ENUMERATED{sf720,sf1440,sf2880,sf5760}.

[0088] Example b2: dl-GapPeriodicity-r19 ENUMERATED{sf720,sf1440,sf2880,sf5760,sf11520}.

[0089] It is understandable that "sf" in examples b1 and b2 represents a sub-frame.

[0090] Method a2: The first cycle equals the sum of the second and third cycles.

[0091] The second period can represent the period configured or defined by an existing protocol for downlink transmission gaps. The third period can represent a period extended from the second period. For example, the third period can be represented by dl-GapPeriodicityExtention. For instance, the second period can be one of {sf64, sf128, sf256, sf512}.

[0092] In one possible implementation, the network device can carry a second period and a third period in the configuration information. In this way, the terminal device receiving the configuration information can obtain the second and third periods from the configuration information. Then, the terminal device can determine the first period based on the second and third periods; that is, the first period is equal to the sum of the second and third periods.

[0093] In another possible implementation, the network device can carry the sum of the second and third cycles in the configuration information.

[0094] Optionally, the sum of the second and third cycles can be equal to k*90. In this way, by setting the sum of the second and third cycles to k*90, the starting position of the downlink transmission gap in the first cycle in method a2 can also be located on a downlink time unit (such as a DL subframe), which makes it easier for other terminal devices to monitor and perform downlink transmission at this point, and further enables each downlink transmission gap to be used normally for downlink transmission of other terminal devices.

[0095] Optionally, the downlink transmission gap may include one or more downlink time units. In one possible implementation, the number of downlink time units included in the downlink transmission gap within the first period can be equal to the product of the first period and a first coefficient. This ensures that the duration or downlink time units used for downlink transmission within the downlink transmission gap within the first period are sufficient to meet the needs of network devices for downlink transmission with other terminal devices. Compared to traditional configuration schemes that result in no downlink time units (e.g., DL subframes) within the downlink transmission gap, only uplink time units (e.g., DL subframes) and / or guard interval time units (e.g., GP subframes), making downlink transmission impossible or having very few downlink time units within the downlink transmission gap, insufficient to meet the downlink transmission needs of network devices with other terminal devices, this scheme ensures a certain number of downlink time units within the downlink transmission gap within the first period.

[0096] In one example, the first coefficient can be predefined by the protocol. After receiving the configuration information, the terminal device can obtain the first period from the configuration information. Then, the terminal device can determine the number of downlink time units included in the downlink transmission gap within the first period, or the duration of the downlink transmission gap within the first period, based on the first period and the first coefficient defined by the protocol. For example, the first coefficient can be represented by dl-GapDurationCoeff. For instance, the value of the first coefficient can be one of {1 / 8, 1 / 4, 3 / 8, 1 / 2}.

[0097] In another example, the first coefficient can be carried in the configuration information. After receiving the configuration information, the terminal device can obtain the first period and the first coefficient from the configuration information. Then, the terminal device can determine the number of downlink time units included in the downlink transmission gap within the first period, or determine the duration of the downlink transmission gap within the first period, based on the first period and the first coefficient.

[0098] The following examples illustrate the downlink transmission gaps within the first cycle.

[0099] Example c1: When a terminal device is scheduled by the network device to perform downlink transmission before receiving configuration information, the downlink transmission gap within the first cycle can be used for the terminal device to stop downlink transmission with the network device. The downlink time units within the first cycle, excluding the downlink transmission gap, are used for downlink transmission between the terminal device and the network device. It should be understood that the downlink transmission gap within the first cycle may include uplink time units and / or guard interval time units in addition to downlink time units.

[0100] In example c1, other terminal devices besides the aforementioned terminal devices may be scheduled by the network device to perform downlink transmissions during the downlink transmission gaps within the first cycle. For example, consider two terminal devices (e.g., terminal device 101 and terminal device 102). Terminal device 101 is scheduled by the network device to perform downlink transmissions before receiving configuration information. Thus, terminal device 101 can stop downlink transmissions with the network device during the downlink transmission gaps within the first cycle. That is, it can be understood that terminal device 101 stops receiving control signaling or service data from the network device during the downlink transmission gaps within the first cycle. Terminal device 101 can perform downlink transmissions with the network device on multiple downlink time units within the first cycle, excluding the downlink transmission gaps. That is, it can be understood that terminal device 101 receives control signaling or service data from the network device on multiple downlink time units within the first cycle, excluding the downlink transmission gaps.

[0101] When the network device needs to schedule the terminal device 102 during the downlink transmission gap in the first cycle, the terminal device 102 can perform downlink transmission with the network device during the downlink transmission gap in the first cycle. That is, it can be understood that the terminal device 102 receives control signaling or service data from the network device during one or more downlink time units included in the downlink transmission gap in the first cycle. It can also be understood that the terminal device 102 will not perform downlink transmission with the network device during multiple downlink time units in the first cycle other than the downlink transmission gap. That is, it can be understood that the terminal device 102 will not receive control signaling or service data from the network device during multiple downlink time units in the first cycle other than the downlink transmission gap.

[0102] Example c2: When a terminal device is not scheduled for downlink transmission by the network device before receiving configuration information, downlink time units within the first cycle, excluding downlink transmission gaps, are not used for downlink transmission between the terminal device and the network device. Downlink transmission gaps within the first cycle may be used for downlink transmission between the terminal device and the network device.

[0103] In example c2, other terminal devices besides the aforementioned terminal devices may be scheduled by the network device to perform downlink transmission on multiple downlink time units within the first cycle, excluding downlink transmission gaps. For specific implementation examples, please refer to the example description in example c1 above, which will not be repeated here.

[0104] In one possible implementation, one or more time units following the downlink transmission gap in the time domain can be considered downlink time units. This ensures that if a network device needs to perform multiple downlink transmissions with a particular terminal device, the network device can immediately resume downlink transmissions with that terminal device after the downlink transmission gap ends.

[0105] For example, when setting downlink transmission gaps, if the time unit after the end of the downlink transmission gap is a non-downlink time unit (such as an uplink time unit or a guard interval time unit), the downlink transmission gap can be extended to include the downlink time unit after the end of the downlink transmission gap.

[0106] The starting position of the downlink transmission gap in the first cycle is described below.

[0107] The starting position of the downlink transmission gap defined by existing protocols is based on formula (10n) f +floor(n s / 2))mod N=0 In the NB-IoT scenario with the introduction of a 90ms TDD mode, the starting position (or initial position) of the downlink transmission gap may not be located on the downlink time unit. It is necessary to consider the impact of the offset between the time-domain starting position of the time division duplex pattern and the time-domain starting position of narrowband IoT on the starting position of the downlink transmission gap. This can ensure that the starting position of the downlink transmission gap is located on the downlink time unit, thus guaranteeing that the downlink transmission gap can be correctly configured and applied to meet the needs of network devices for downlink transmission with other terminal devices. Wherein, the above n f and n s This indicates the starting position of the downlink transmission gap as defined by the existing protocol.

[0108] In one possible implementation, the starting position of the downlink transmission gap within the first cycle can be determined based on the first cycle and a first offset. The first offset can represent the offset between the time-domain start position of the time-division duplex pattern and the time-domain start position of the narrowband IoT (e.g., the timing start position or the radio frame start position of the narrowband IoT). For example, the first offset can be 3. For example, the period of the time-division duplex pattern is 90 ms.

[0109] For example, the starting position of the downlink transmission gap can satisfy the following relationship: (1024n) h +10n f +floor(n s / 2))mod N=3

[0110] Where, n h n f and n s This indicates the starting position of the downlink transmission gap within the first cycle. h Indicates the index of the first superframe. n f This represents the index of the first radio frame included in the first superframe. s This represents the index of the first subframe included in the first radio frame. `floor()` indicates floor operation. `mod` indicates modulo operation. `N` represents the first period. The first offset is 3.

[0111] The following example illustrates the implementation of network devices sending configuration information.

[0112] In one example, a network device can send configuration information to one or more terminal devices via unicast.

[0113] In another example, a network device can send configuration information to one or more terminal devices via broadcast.

[0114] As can be seen from S401 to S402 above, since the starting position of the first cycle is located in the first downlink time unit, by configuring the first cycle to be equal to k*90 or the first cycle to be equal to the sum of the second and third cycles, there can be enough downlink time units in the first cycle for downlink transmission (for example, there are enough downlink time units in the first cycle except for downlink transmission gaps for downlink transmission between network devices and terminal devices). In this way, the period configuration of the downlink transmission gap is more reasonable (or appropriate), which can effectively reduce the number of times downlink transmission is interrupted by downlink transmission gaps, and help meet the downlink transmission needs of network devices and terminal devices, thereby enabling the normal operation of downlink transmission.

[0115] It is understood that, in order to achieve the functions in the above embodiments, the network device and terminal device include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware, computer software, or a combination of both. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0116] Figures 5 and 6 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of network devices or terminal devices in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. The communication device can be a network device or a terminal device, or it can be a module in a network device or a terminal device (e.g., a communication module, a circuit or chip responsible for communication functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or it can be a logical node, logical module, or software that can implement all or part of the functions of a network device or a terminal device.

[0117] The communication device 500 shown in Figure 5 includes a transceiver unit 510 (or a communication module, transceiver module, or communication unit, used for sending and receiving data). Optionally, the communication device 500 shown in Figure 5 may further include a processing unit 520 (or a processing module). The communication device 500 can be used to implement the functions of the network device or terminal device in the method embodiment shown in Figure 4 above. For example, the transceiver unit 510 can perform the receiving and sending actions performed by the network device or terminal device in the method embodiment above. The processing unit 520 can perform other actions besides the sending and receiving actions performed by the network device or terminal device in the method embodiment above.

[0118] When the communication device 500 is used to implement the functions of the terminal device in the method embodiment shown in Figure 4: the transceiver unit 510 is used to receive configuration information. The configuration information includes a first period of downlink transmission gaps. The first period is equal to k*90, where k is an integer greater than or equal to 1. Alternatively, the first period is equal to the sum of the second and third periods, where the second period represents the period configured or defined by the existing protocol for downlink transmission gaps. The starting position of the first period is located on the first downlink time unit. The downlink transmission gap within the first period is used for the terminal device and network device to stop downlink transmission. The downlink time units within the first period other than the downlink transmission gap are used for downlink transmission between the terminal device and network device. The processing unit 520 is used to perform corresponding processing operations, such as calling the transceiver unit 510 to execute the transmission and reception actions required by the terminal device in the method embodiment shown in Figure 4, or determining the starting position of the downlink transmission gap, etc.

[0119] When the communication device 500 is used to implement the functions of the network device in the method embodiment shown in Figure 4 above: Processing unit 520 is used to determine configuration information. Transceiver unit 510 is used to send the configuration information. The configuration information includes a first period of downlink transmission gaps. The first period is equal to k*90, where k is an integer greater than or equal to 1. Alternatively, the first period is equal to the sum of the second period and the third period, where the second period represents the period configured or defined by the existing protocol for downlink transmission gaps. The starting position of the first period is located on the first downlink time unit. The downlink transmission gaps within the first period are used for the terminal device and the network device to stop downlink transmission. The downlink time units within the first period other than the downlink transmission gaps are used for the terminal device and the network device to perform downlink transmission.

[0120] For a more detailed description of the processing unit 520 and the transceiver unit 510, please refer to the relevant description in the method embodiment shown in Figure 4 above, which will not be repeated here.

[0121] It should be understood that the transceiver unit 510 in the embodiments of this application can be implemented by an interface circuit or interface circuit-related circuit components, and the processing unit 520 can be implemented by a processor or processor-related circuit components.

[0122] It should be noted that the module division in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical entities, or have two or more units integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0123] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, or a server, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0124] The communication device 600 shown in Figure 6 includes at least one processor 620 and interface circuitry 610. The at least one processor 620 and interface circuitry 610 may be coupled to each other. It is understood that interface circuitry 610 may be a transceiver or an input / output interface. Exemplarily, the communication device 600 may also include a memory 630. Memory 630 is used to store instructions executed by at least one processor 620, or to store input data required for at least one processor 620 to execute instructions, or to store data generated after at least one processor 620 executes instructions.

[0125] When the communication device 600 is used to implement the method embodiment shown in FIG4 above, at least one processor 620 is used to implement the function of the processing unit 520 above, and the interface circuit 610 is used to implement the function of the transceiver unit 510 above.

[0126] For example, taking a network device as a base station and a terminal device as a UE, when the aforementioned communication device is a chip applied to the UE, the UE chip implements the functions corresponding to the UE in the above method embodiments. For example, when the UE chip receives information from the base station, it can be understood that the information is first received by other modules in the UE (such as an RF module or antenna), and then sent to the UE chip by these modules. When the UE chip sends information to the base station, it can be understood that the information is first sent to other modules in the UE (such as an RF module or antenna), and then sent to the base station by these modules.

[0127] When the aforementioned communication device is a chip applied to a base station, the base station chip implements the functions corresponding to the base station in the above method embodiments. For example, when the base station chip receives information from the UE, it can be understood that the information is first received by other modules in the base station (such as an RF module or antenna), and then sent to the base station chip by these modules. When the base station chip sends information to the UE, it can be understood that the information is sent down to other modules in the base station (such as an RF module or antenna), and then sent to the UE by these modules.

[0128] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be terminal devices or network devices, or modules within those devices. Information transmission and reception can be between a terminal device and a network device, such as between a UE and a base station. Information transmission and reception can also be between two base stations, such as between a CU and a DU. Furthermore, information transmission and reception can be between different modules within a single device, such as between a UE chip and other UE modules, or between a base station chip and other modules within that base station.

[0129] Based on the same concept, this application also provides a possible communication system. This communication system may include a terminal device and a network device. The terminal device can be used to implement the technical solutions related to the terminal device in the above embodiments. The network device can be used to implement the technical solutions related to the network device in the above embodiments.

[0130] Based on the same concept, this application also provides a computer program product, which includes a computer program or instructions that, when run on a communication device (or computer), cause the communication device (or computer) to perform the methods provided in the above embodiments.

[0131] Based on the same concept, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device (or computer), cause the communication device (or computer) to perform the methods provided in the above embodiments.

[0132] The storage medium can be any available medium that a computer can access. For example, but not limited to, a computer-readable medium can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0133] Based on the same concept, embodiments of this application also provide a chip, which may include a processor and a memory (or the chip may be coupled to the memory). The processor executes program instructions in the memory to cause the chip to perform the methods provided in the above embodiments. Here, "coupling" means that two components are directly or indirectly connected to each other, such as coupling can refer to an electrical connection between two components.

[0134] Based on the same concept, embodiments of this application also provide a chip system, which includes a processor for supporting a computer device in implementing the functions involved in the terminal device or network device in the above embodiments. In one possible implementation, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete components.

[0135] It is understood that the processor in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0136] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a communication device. Of course, the processor and storage medium can also exist as discrete components in the communication device.

[0137] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. A computer program is a set of instructions that directs each step of an action of an electronic computer or other device with message processing capabilities. It is typically written in a programming language and runs on a target architecture. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless 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 integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be volatile or non-volatile, or it can include both types of storage media.

[0138] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0139] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects.

[0140] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method characterized by comprising: The method, which applies to a terminal device or a chip in the terminal device, includes: Receive configuration information; The configuration information includes a first period of downlink transmission gap, where the first period is equal to k*90, where k is an integer greater than or equal to 1, or the first period is equal to the sum of the second period and the third period. The second period represents the period configured or defined by the existing protocol for the downlink transmission gap. The starting position of the first period is located on the first downlink time unit. The downlink transmission gap within the first period is used for the terminal device and the network device to stop downlink transmission. The downlink time units within the first period other than the downlink transmission gap are used for the terminal device and the network device to perform downlink transmission.

2. A communication method characterized by comprising: The method, applied to a network device or a chip in the network device, includes: Determine the configuration information; Send the configuration information; The configuration information includes a first period of downlink transmission gap, where the first period is equal to k*90, where k is an integer greater than or equal to 1, or the first period is equal to the sum of the second period and the third period. The second period represents the period configured or defined by the existing protocol for the downlink transmission gap. The starting position of the first period is located on the first downlink time unit. The downlink transmission gap within the first period is used for the terminal device and the network device to stop downlink transmission. The downlink time units within the first period other than the downlink transmission gap are used for the terminal device and the network device to perform downlink transmission.

3. The method of claim 1 or 2, wherein, The sum of the second period and the third period equals k*90.

4. The method according to any one of claims 1 to 3, characterized in that, The number of downlink time units included in the downlink transmission gap is equal to the product of the first period and the first coefficient.

5. The method according to any one of claims 1 to 4, wherein The starting position of the downlink transmission gap is determined based on the first period and the first offset, whereby the first offset represents the offset between the time-domain starting position of the time-division duplex pattern and the time-domain starting position of the narrowband Internet of Things.

6. The method of claim 5, wherein, The start position of the downlink transmission gap satisfies the following relationship: (1024n h + 10n f + floor(n s / 2)) mod N = 3 wherein n h , n f , and n s represent the starting position of the downlink transmission gap, n h represents the index of the first superframe, n f represents the index of the first radio frame included in the first superframe, n s represents the index of the first subframe included in the first radio frame, floor() represents the down-rounding operation, mod represents the remainder operation, the first offset is 3, and N represents the first period.

7. A communication device, characterized by The communication device is a terminal device or a chip in the terminal device, and the communication device includes a transceiver module; The transceiver module is used to receive configuration information; The configuration information includes a first period of downlink transmission gap, where the first period is equal to k*90, where k is an integer greater than or equal to 1, or the first period is equal to the sum of the second period and the third period. The second period represents the period configured or defined by the existing protocol for the downlink transmission gap. The starting position of the first period is located on the first downlink time unit. The downlink transmission gap within the first period is used for the terminal device and the network device to stop downlink transmission. The downlink time units within the first period other than the downlink transmission gap are used for the terminal device and the network device to perform downlink transmission.

8. A communication device, characterized by The communication device is a network device or a chip in the network device, and the communication device includes a processing module and a transceiver module; The processing module is used to determine configuration information; The transceiver module is used to send the configuration information; The configuration information includes a first period of downlink transmission gap, where the first period is equal to k*90, where k is an integer greater than or equal to 1, or the first period is equal to the sum of the second period and the third period. The second period represents the period configured or defined by the existing protocol for the downlink transmission gap. The starting position of the first period is located on the first downlink time unit. The downlink transmission gap within the first period is used for the terminal device and the network device to stop downlink transmission. The downlink time units within the first period other than the downlink transmission gap are used for the terminal device and the network device to perform downlink transmission.

9. The apparatus of claim 7 or 8, wherein, The sum of the second period and the third period equals k*90.

10. The device of any one of claims 7-9, wherein, The number of downlink time units included in the downlink transmission gap is equal to the product of the first period and the first coefficient.

11. The device of any one of claims 7-10, wherein, The starting position of the downlink transmission gap is determined based on the first period and the first offset, whereby the first offset represents the offset between the time-domain starting position of the time-division duplex pattern and the time-domain starting position of the narrowband Internet of Things.

12. The apparatus of claim 11, wherein, The start position of the downlink transmission gap satisfies the following relationship: (1024n h + 10n f + floor(n s / 2)) mod N = 3 wherein n h , n f , and n s represent the starting position of the downlink transmission gap, n h represents the index of the first superframe, n f represents the index of the first radio frame included in the first superframe, n s represents the index of the first subframe included in the first radio frame, floor() represents a down-rounding operation, mod represents a remainder operation, the first offset is 3, and N represents the first period.

13. A communications device, characterized by Includes at least one processor and interface circuitry; The interface circuit is used to receive signals from other communication devices and transmit them to the at least one processor, or to send signals from the at least one processor to other communication devices. The at least one processor is configured to implement the method as described in any one of claims 1-6 via logic circuits or execution code instructions.

14. A communication system, characterized by This includes terminal equipment and network equipment; The terminal device is used to perform the method as described in any one of claims 1, 3-6, and the network device is used to perform the method as described in any one of claims 2-6.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed by a communication device, cause the method as described in any one of claims 1-6 to be implemented.

16. A computer program product, characterised in that, The computer program product includes a computer program or instructions that, when executed on a communication device, cause the method as described in any one of claims 1-6 to be implemented.

Images