Communication method, communication apparatus and storage medium

Abstract

Disclosed in the embodiments of the present application are a communication method, a communication apparatus and a storage medium, which can be used for enabling a network device to perform flexible scheduling of NB-IoT in an NTN. The method in the embodiments of the present application comprises: receiving downlink control information, wherein the downlink control information is used for indicating first information, the first information comprises the period of a first time-domain resource, the first information is used for determining a first time-domain unit, and the first time-domain unit is located within the first time-domain resource; and receiving downlink information starting from the first time-domain unit, or sending uplink information starting from the first time-domain unit. The period of a first time-domain resource is indicated, such that a network device can adapt to a TDD mode to perform uplink scheduling or downlink scheduling, thereby enhancing the flexibility of uplink scheduling and downlink scheduling. Since the time-domain length of the first time-domain resource is 90 ms, the scheduling manners for uplink information and downlink information can be adapted to the 90 ms time-domain resource, thereby realizing flexible scheduling.

Description

Communication methods, communication devices and storage media

[0001] This application claims priority to Chinese Patent Application No. 202510134187.2, filed on February 6, 2025, entitled "Communication Method, Communication Device and Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication technology, and in particular to a communication method, communication device, and storage medium. Background Technology

[0003] Narrowband Internet of Things (NB-IoT) is a low-power wide-area network technology based on cellular networks, specifically designed for large-scale Internet of Things (IoT) devices.

[0004] The narrow-band physical downlink control channel (NPDCCH) is the physical channel used in NB-IoT for transmitting downlink control information. It primarily carries downlink control information (DCI), which guides user equipment on how to receive downlink data or send uplink data.

[0005] However, the current scheduling method may result in the inability to schedule downlink or uplink data onto available subframes. Summary of the Invention

[0006] This application provides a communication method, communication device, and storage medium for enabling network devices to flexibly schedule NB-IoT within an NTN.

[0007] The first aspect of this application provides a communication method. Optionally, the executing entity of this method may be a first device, which may be a terminal device, a component or device applied to the terminal device (e.g., a module, a communication module, a circuit or chip responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), or a logic module or software capable of implementing all or part of the terminal device's functions). The first device receives downlink control information (DCI), wherein the DCI is carried on a narrow-band physical downlink control channel (NPDCCH). The DCI is used to indicate first information, which includes the period of a first time-domain resource. This first time-domain resource is a time-division duplex time-division multiplexing (TDM) of a new narrowband Internet of Things (NB-IoT) non-terrestrial networks (NTN). The duplex (TDD) mode requires a period of N radio frames, where N is a base value of 9. First information is used to determine a first time-domain unit, which is located within a first time-domain resource. The first device begins receiving downlink information from the first time-domain unit, or begins transmitting uplink information from the first time-domain unit.

[0008] Based on the first aspect of this application, by indicating the period of the first time domain resource, the network device is able to adapt to the TDD mode for uplink or downlink scheduling, thereby enhancing the flexibility of uplink and downlink scheduling.

[0009] A second aspect of this application provides a communication method. Optionally, the execution subject of this method may be a second device, which may be a network device, a component or device applied to the network device (e.g., a module, communication module, circuit or chip responsible for communication functions (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor), or a logic module or software (e.g., a CU, DU, or RU) capable of implementing all or part of the network device's functions. The method includes the second device determining a Direct Current Interface (DCI), whereby the DCI indicates first information, including the period of a first time-domain resource and the end time-domain unit of a narrowband physical downlink control channel. The first information is used to determine a first time-domain unit located within the first time-domain resource. The second device sends the DCI to the first device, enabling the first device to determine the first time-domain unit based on the DCI, thereby receiving downlink information or sending uplink information.

[0010] Based on the first or second aspect of this application, in some possible implementations, the time domain length of the first time domain resource is 90ms. The first time domain resource includes 8ms of uplink time domain resource and 8ms of downlink time domain resource. The first time domain unit is located within the uplink time domain resource, or the first time domain unit is located within the downlink time domain resource. That is, a TDD frame structure with a length of 90ms can be configured in the system. This 90ms frame structure repeats periodically in the time domain. Each 90ms frame structure contains 8ms of uplink time domain resource and 8ms of downlink time domain resource. The first time domain resource can be understood as one of these 90ms frame structures.

[0011] Based on the first or second aspect of this application, in some possible implementations, downlink information is carried on a narrow-band physical downlink shared channel (NPDSCH), and uplink information is carried on a narrow-band physical uplink shared channel (NPUSCH).

[0012] Since the time domain length of the first time domain resource is 90ms, and the first time domain unit is located in the uplink or downlink time domain resource, the scheduling methods of uplink and downlink information can be adapted to the 90ms first time domain resource, thereby achieving flexible scheduling.

[0013] Based on the first or second aspect of this application, in some possible implementations, the first time domain unit is located within the downlink time domain resources, and the first information further includes a first parameter, which is used to indicate the number of repetitions of the period in which the first time domain unit is located, and the first parameter is determined according to the scheduling delay domain in the downlink control information.

[0014] By indicating the first parameter, the network device can determine the different time-domain positions of the first time-domain unit by the number of repetitions of the cycle, thereby enabling the first time-domain unit to have multiple implementation methods and thus achieving flexible scheduling.

[0015] Based on the first or second aspect of this application, in some possible implementations, the first time-domain unit n0 satisfies: n0=n+k1*T;

[0016] Alternatively, the first time-domain unit n0 satisfies: n0 = n + k1 * T - offset;

[0017] Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, k1 is the first parameter, T is the period of the first time domain resource, and offset is the first offset value. The first offset value is used to indicate the offset value between the end domain unit of the narrowband physical downlink control channel and the start domain unit of the downlink time domain resource within a downlink time domain resource.

[0018] The time domain position of the first time domain unit is determined by the first offset value, so that the first time domain unit can be in the starting time domain unit of the downlink time domain resources, thus avoiding scheduling restrictions.

[0019] Based on the first or second aspect of this application, in some possible implementations, the first time domain unit is located within the downlink time domain resource, and the first information further includes a first offset value. The first offset value is used to indicate the offset value between the end time domain unit of the narrowband physical downlink control channel and the start time domain unit of the downlink time domain resource within a downlink time domain resource, and the downlink control information is carried in the narrowband physical downlink control channel.

[0020] The time domain position of the first time domain unit is determined by the first offset value, so that the terminal device receives downlink information at a time domain position 90ms later, thereby avoiding scheduling restrictions.

[0021] Based on the first or second aspect of this application, in some possible implementations, the first time-domain unit n0 satisfies: n0 = n + T - offset;

[0022] Where n is the end domain unit of the narrowband physical downlink control channel, downlink control information is carried in the narrowband physical downlink control channel, T is the period of the first time domain resource, and offset is the first offset value.

[0023] The time domain position of the first time domain unit is determined by the first offset value, so that the terminal device receives downlink information at a time domain position 90ms later, thereby avoiding scheduling restrictions.

[0024] Based on the first or second aspect of this application, in some possible implementations, if the first time domain unit is located within the uplink time domain resources, then the first information also includes a second offset value, which is a parameter configured by the network device.

[0025] Because there is a large time delay between network devices and terminal devices in NTN scenarios, determining the first time domain unit by using the second offset value ensures that the time domain position of the first time domain unit is within the uplink time domain resources, thereby enabling normal transmission of uplink information.

[0026] Based on the first or second aspect of this application, in some possible implementations, the first time-domain unit n0 satisfies: n0 = n + K offset +T;

[0027] Where n is the end domain element of the narrowband physical downlink control channel, and downlink control information is carried in the narrowband physical downlink control channel, K offset The second offset value is T, where T is the period of the first time-domain resource.

[0028] Because there is a large time delay between network devices and terminal devices in NTN scenarios, determining the first time domain unit by using the second offset value ensures that the time domain position of the first time domain unit is within the uplink time domain resources, thereby enabling normal transmission of uplink information.

[0029] Based on the first or second aspect of this application, in some possible implementations, the first information further includes a first parameter, which is used to indicate the number of repetitions of the period in which the first time domain unit is located, and the first parameter is determined according to the scheduling delay domain in the downlink control information.

[0030] The first time domain unit is determined by the first parameter, which enables the first time domain unit to be flexibly scheduled in uplink time domain resources of different periods.

[0031] Based on the first or second aspect of this application, in some possible implementations, the first time-domain unit n0 satisfies: n0 = n + K offset +k1*T;

[0032] Where n is the end domain element of the narrowband physical downlink control channel, and downlink control information is carried in the narrowband physical downlink control channel, K offset The second offset value is k1, the first parameter is k1, and the period of the first time domain resource is T.

[0033] The first time domain unit is determined by the first parameter, which enables the first time domain unit to be flexibly scheduled in uplink time domain resources of different periods.

[0034] Based on the first or second aspect of this application, in some possible implementations, the first information further includes a second parameter, which is used to indicate the number of time-domain units of the delay, and the second parameter is determined based on the scheduling delay domain in the downlink control information.

[0035] A third aspect of this application provides a communication device, comprising:

[0036] The interface module is used to receive downlink control information, which is used to indicate first information, including the period of the first time domain resource, and to determine the first time domain unit, which is located within the first time domain resource.

[0037] The processing module is used to determine the first time-domain unit;

[0038] The interface module is also used to receive downlink information starting from the first time domain unit, or to send uplink information starting from the first time domain unit.

[0039] In some possible implementations, the time domain length of the first time domain resource is 90ms, the first time domain resource includes 8ms of uplink time domain resource and 8ms of downlink time domain resource, the first time domain unit is located within the uplink time domain resource, or the first time domain unit is located within the downlink time domain resource;

[0040] Downlink information is carried on a narrowband physical downlink shared channel, and uplink information is carried on a narrowband physical uplink shared channel.

[0041] In some possible implementations, the first time domain unit is located within the downlink time domain resources, and the first information also includes a first parameter, which is used to indicate the number of repetitions of the period in which the first time domain unit is located. The first parameter is determined based on the scheduling delay domain in the downlink control information.

[0042] In some possible implementations, the first time-domain unit n0 satisfies: n0 = n + k1 * T;

[0043] Alternatively, the first time-domain unit n0 satisfies: n0 = n + k1 * T - offset;

[0044] Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, k1 is the first parameter, T is the period of the first time domain resource, and offset is the first offset value. The first offset value is used to indicate the offset value between the end domain unit of the narrowband physical downlink control channel and the start domain unit of the downlink time domain resource within a downlink time domain resource.

[0045] In some possible implementations, the first time domain unit is located within the downlink time domain resource, and the first information also includes a first offset value, which is used to indicate the offset value between the end time domain unit of the narrowband physical downlink control channel and the start time domain unit of the downlink time domain resource within a downlink time domain resource, and the downlink control information is carried in the narrowband physical downlink control channel.

[0046] In some possible implementations, the first time-domain unit n0 satisfies: n0 = n + T - offset;

[0047] Where n is the end domain unit of the narrowband physical downlink control channel, downlink control information is carried in the narrowband physical downlink control channel, T is the period of the first time domain resource, and offset is the first offset value.

[0048] In some possible implementations, if the first time domain unit is located within the uplink time domain resources, the first information may also include a second offset value, which is a parameter configured by the network device.

[0049] In some possible implementations, the first time-domain unit n0 satisfies: n0 = n + K offset +T;

[0050] Where n is the end domain element of the narrowband physical downlink control channel, and downlink control information is carried in the narrowband physical downlink control channel, K offset The second offset value is T, where T is the period of the first time-domain resource.

[0051] In some possible implementations, the first information may further include a first parameter, which indicates the number of repetitions of the period in which the first time-domain unit is located, and the first parameter is determined based on the scheduling delay domain in the downlink control information.

[0052] In some possible implementations, the first time-domain unit n0 satisfies: n0 = n + K offset +k1*T;

[0053] Where n is the end domain element of the narrowband physical downlink control channel, and downlink control information is carried in the narrowband physical downlink control channel, K offset The second offset value is k1, the first parameter is k1, and the period of the first time domain resource is T.

[0054] In some possible implementations, the first information also includes a second parameter, which indicates the number of time-domain units of the delay, and is determined based on the scheduling delay domain in the downlink control information.

[0055] A fourth aspect of this application provides a communication device, comprising:

[0056] The processing module is used to determine downlink control information, which is used to indicate first information, including the period of the first time domain resource, and to determine the first time domain unit, which is located within the first time domain resource.

[0057] The interface module is used to send downlink control information.

[0058] In some possible implementations, the time domain length of the first time domain resource is 90ms, the first time domain resource includes 8ms of uplink time domain resource and 8ms of downlink time domain resource, the first time domain unit is located within the uplink time domain resource, or the first time domain unit is located within the downlink time domain resource;

[0059] Downlink information is carried on a narrowband physical downlink shared channel, and uplink information is carried on a narrowband physical uplink shared channel.

[0060] In some possible implementations, the first time domain unit is located within the downlink time domain resources, and the first information also includes a first parameter, which is used to indicate the number of repetitions of the period in which the first time domain unit is located. The first parameter is determined based on the scheduling delay domain in the downlink control information.

[0061] In some possible implementations, the first time-domain unit n0 satisfies: n0 = n + k1 * T;

[0062] Alternatively, the first time-domain unit n0 satisfies: n0 = n + k1 * T - offset;

[0063] Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, k1 is the first parameter, T is the period of the first time domain resource, and offset is the first offset value. The first offset value is used to indicate the offset value between the end domain unit of the narrowband physical downlink control channel and the start domain unit of the downlink time domain resource within a downlink time domain resource.

[0064] In some possible implementations, if the first time domain unit is located within the downlink time domain resource, the first information also includes a first offset value, which indicates the offset between the end time domain unit of the narrowband physical downlink control channel and the start time domain unit of the downlink time domain resource within a downlink time domain resource, wherein the downlink control information is carried in the narrowband physical downlink control channel.

[0065] In some possible implementations, the first time-domain unit n0 satisfies: n0 = n + T - offset;

[0066] Where n is the end domain unit of the narrowband physical downlink control channel, downlink control information is carried in the narrowband physical downlink control channel, T is the period of the first time domain resource, and offset is the first offset value.

[0067] In some possible implementations, the first time domain unit is located within downlink time domain resources, and the first information also includes a second offset value, which is a parameter configured by the network device.

[0068] In some possible implementations, the first time-domain unit n0 satisfies: n0 = n + K offset +T;

[0069] Where n is the end domain element of the narrowband physical downlink control channel, and downlink control information is carried in the narrowband physical downlink control channel, K offset The second offset value is T, where T is the period of the first time-domain resource.

[0070] In some possible implementations, the first information may further include a first parameter, which indicates the number of repetitions of the period in which the first time-domain unit is located, and the first parameter is determined based on the scheduling delay domain in the downlink control information.

[0071] In some possible implementations, the first time-domain unit n0 satisfies: n0 = n + K offset +k1*T;

[0072] Where n is the end domain element of the narrowband physical downlink control channel, and downlink control information is carried in the narrowband physical downlink control channel, K offset The second offset value is k1, the first parameter is k1, and the period of the first time domain resource is T.

[0073] In some possible implementations, the first information also includes a second parameter, which indicates the number of time-domain units of the delay, and is determined based on the scheduling delay domain in the downlink control information.

[0074] A fifth aspect of this application provides a communication device, which may be a first device or a second device, or a component applied to the first device or the second device (e.g., a module, a communication module, a circuit or chip responsible for communication functions (e.g., a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core or a system-in-package (SIP) chip), or a logic module or software (e.g., a CU, DU, or RU) capable of implementing all or part of the functions of the first device or the second device). The communication device includes:

[0075] A processor for executing a program that causes the communication device to perform the method as described in the first or second aspect and any possible implementation thereof.

[0076] Optionally, the communication device further includes a memory, and the processor is coupled to the memory; the memory is used to store programs.

[0077] The sixth aspect of this application provides a chip or chip system including at least one processor and a communication interface, the communication interface and at least one processor being interconnected via a line, the at least one processor being used to run computer programs or instructions to perform the communication method described in any of the possible implementations of the first or second aspect.

[0078] The communication interface in the chip can be an input / output interface, pins, or circuits.

[0079] In one possible implementation, the chip or chip system described above in this application further includes at least one memory storing instructions. The memory can be an internal storage unit of the chip, such as a register or cache, or it can be a storage unit of the chip itself, such as a read-only memory or random access memory.

[0080] The seventh aspect of this application provides a communication system, including a communication device that performs the first aspect and any possible implementation thereof, and a communication device that performs the second aspect and any possible implementation thereof.

[0081] An eighth aspect of this application provides a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the method described in the first aspect above, or cause the computer to perform the method described in the second aspect above.

[0082] The ninth aspect of this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the method described in the first aspect above, or cause the computer to perform the method described in the second aspect above. Attached Figure Description

[0083] Figure 1a is a schematic diagram of an embodiment of the ground network architecture in this application;

[0084] Figure 1b is a schematic diagram of an embodiment of the non-terrestrial network architecture in this application;

[0085] Figure 2 is a schematic diagram of an embodiment of the 90ms frame structure in this application;

[0086] Figure 3 is a schematic diagram of an embodiment of NB-IoT DL scheduling in FDD mode in this application;

[0087] Figure 4 is a schematic diagram of an embodiment of UL scheduling of NB-IoT in FDD mode in this application;

[0088] Figure 5 is a schematic diagram of an embodiment of NB-IoT UL scheduling applied to a 90ms frame structure in this application;

[0089] Figure 6 is a schematic diagram of an embodiment of the communication method in this application;

[0090] Figure 7 is a schematic diagram of an embodiment of downlink scheduling in this application;

[0091] Figure 8 is a schematic diagram of another embodiment of downlink scheduling in this application;

[0092] Figure 9 is a schematic diagram of another embodiment of downlink scheduling in this application;

[0093] Figure 10 is a schematic diagram of an embodiment of uplink scheduling in this application;

[0094] Figure 11 is a schematic diagram of another embodiment of uplink scheduling in this application;

[0095] Figure 12 is a schematic diagram of an embodiment of the communication device in this application;

[0096] Figure 13 is a schematic diagram of another embodiment of the communication device in this application;

[0097] Figure 14 is a schematic diagram of another embodiment of the communication device in this application;

[0098] Figure 15 is a schematic diagram of another embodiment of the communication device in this application. Detailed Implementation

[0099] First, a brief description of the terrestrial network architecture on which the communication method in the embodiments of this application is based:

[0100] Please refer to Figure 1a, which is a possible, non-limiting system schematic diagram. As shown in Figure 1a, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (110a and 110b in Figure 1a, collectively referred to as 110) and at least one terminal (120a-120j in Figure 1a, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (not shown in Figure 1a). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0101] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G, or future mobile communication systems. RAN 100 can also be an open-radio access network (ORAN), cloud-radio access network (CRAN), or wireless fidelity (Wi-Fi) system. RAN 100 can also be a communication system integrating two or more of the above systems. RAN 100 can also be a non-terrestrial network (NTN) communication system, or a scenario where NTN and terrestrial network (TN) are integrated. The NTN system can be an NTN system integrated with 4G, 5G, and any future generation of communication systems, such as NR NTN, IoT NTN, etc. 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.

[0102] RAN node 110, sometimes referred to as network equipment, RAN entity, or access node, constitutes part of the communication system and assists terminals in achieving wireless access. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 1a can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 1a can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0103] In one possible scenario, network devices can be devices within a wireless network. For example, a network device can be a RAN node (or device) that connects terminal devices to the wireless network, also known as a base station. Currently, some examples of RAN devices include: evolved Node B (eNodeB), radio network controller (RNC), Node B (NB), base station (BS), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B (HNB), baseband unit (BBU), access point (AP) in a Wi-Fi system, macro base station, micro base station, wireless relay node, donor node, radio controller in a CRAN scenario, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP), etc. They can also be network devices in 5G mobile communication systems. For example, a next-generation NodeB (gNB), TRP, or TP in a new radio (NR) system; or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G mobile communication system; or, network equipment can also be network nodes constituting a gNB or transmission point. Examples include centralized units (CU), distributed units (DU), centralized unit control planes (CU-CP), centralized unit user planes (CU-UP), or radio units (RU). CUs and DUs can be separate or included in the same network element, such as a BBU. RUs can be included in radio equipment or radio units, such as in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).Alternatively, network equipment can also be a satellite (or satellite base station) or a high altitude platform station (HAPS), or base station equipment mounted on a satellite / HAPS. The satellite can include at least one of the following: a geostationary earth orbit (GEO) satellite (or geosynchronous orbit satellite) or a non-geostationary earth orbit (NGEO) satellite. A non-geostationary earth orbit satellite can include at least one of the following: a medium earth orbit (MEO) satellite or a low earth orbit (LEO) satellite. There are no limitations here. Network equipment can also be a gateway station (or ground station, earth station, signaling station, gateway, or gateway station). Network equipment can also be a server, wearable device, vehicle, or vehicle-mounted equipment. For example, network equipment in V2X technology can be a roadside unit (RSU). It should be understood that the aforementioned TRP can be a device or module located on the network side of the aforementioned communication system and possessing corresponding communication functions. The TRP typically contains communication modules, circuits, or chips that perform the corresponding communication functions. The TRP can also be configured with program instructions for corresponding communication functions.

[0104] It should be noted 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 open radio access network (ORAN) system, CU can also be called an open centralized unit (O-CU) or an open CU, DU can also be called an open-distributed unit (O-DU), CU-CP can also be called an open-centralized unit control plane (O-CU-CP), CU-UP can also be called an open-centralized unit user plane (O-CU-UP), and RU can also be called an open radio unit (O-RU). This application does not limit the specific names. Any of the units CU, CU-CP, CU-UP, DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0105] Optionally, for network elements in the ORAN system, each network element can implement the protocol layer functions shown in Table 1 below.

[0106] Table 1

[0107] It should be noted that in the ORAN system, the network device in this application can be one or more network elements listed in Table 1 above.

[0108] The architecture of the CU and DU of a network device is described below. A network device includes at least one CU and at least one DU. Optionally, the network device may also include at least one RU.

[0109] The following example uses a network device consisting of a CU and a DU. The CU has some core network functions and can include CU-CP and CU-UP. The CU and DU can be configured according to the protocol layer functions of the wireless network they implement. For example, the CU may be configured to implement the Packet Data Convergence Protocol (PDCP) layer and above (e.g., RRC and / or SDAP layers). The DU may be configured to implement protocol layers below the PDCP layer (e.g., RLC, MAC, and / or physical (PHY) layers). Alternatively, the CU may be configured to implement protocol layers above the PDCP layer (e.g., RRC and / or SDAP layers), and the DU may be configured to implement protocol layers below the PDCP layer (e.g., RLC, MAC, and / or PHY layers).

[0110] When a CU includes CU-CP and CU-UP, CU-CP is used to implement the control plane functions of the CU, and CU-UP is used to implement the user plane functions of the CU. For example, when a CU is configured to implement the functions of the PDCP layer, RRC layer, and SDAP layer, CU-CP is used to implement the RRC layer functions and the control plane functions of the PDCP layer, and CU-UP is used to implement the SDAP layer functions and the user plane functions of the PDCP layer.

[0111] The CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements can be access and mobility function (AMF) network elements, such as the AMF in a 5G system. The AMF is responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover.

[0112] CU-UP can interact with network elements in the core network used to implement user plane functions. These network elements, such as the user plane function (UPF) in a 5G system, are responsible for forwarding and receiving data in terminal devices.

[0113] The above CU and DU configurations are merely examples; the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or only some protocol layer processing functions. For example, some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements. For example, based on latency, functions that require low latency can be placed in the DU, while functions that do not require low latency can be placed in the CU.

[0114] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0115] It should be noted that network devices can be devices or apparatuses with chips, devices or apparatuses with integrated circuits, or chips, chip systems, modules, or control units in the aforementioned devices or apparatuses; this application does not impose any specific limitations. It should also be noted that in this application, the term "network device" can refer to the network device itself, or to chips, functional modules, or integrated circuits within the network device that implement the methods provided in this application; this application does not impose any specific limitations.

[0116] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node performing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-CPs, CU-UPs, or radio units (RUs). 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).

[0117] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, 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 and hardware modules.

[0118] A terminal is a device or module that connects to the aforementioned communication system and possesses corresponding communication functions. Terminals can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as NTN, device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart homes, smart offices, smart wearables, intelligent transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, transportation vehicles with wireless communication capabilities, communication modules, etc. The terminal can also be a communication module, satellite phone, or a component thereof with satellite communication capabilities, or a satellite communication terminal, such as a very small aperture terminal (VSAT) (commonly referred to as a VSAT terminal), portable station, fixed station, vehicle-mounted or airborne satellite communication terminal, etc. It should be understood that the satellite communication terminal can serve as a micro base station to further provide a data interface to the accessing user equipment. The embodiments of this application do not limit the device form of the terminal. The terminal typically contains a communication module, circuit, or chip that performs the corresponding communication function. The terminal can also be configured with program instructions for performing the corresponding communication function. The terminal device can also be a mobile terminal device, such as a mobile phone (or "cellular" phone), computer, and data card. For example, it can be a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device that exchanges voice and / or data with the wireless access network. Examples include personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), tablets, and computers with wireless transceiver capabilities.Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station (MS), remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, subscriber station (SS), customer premises equipment (CPE), etc.

[0119] Please refer to Figure 1b. The following is a brief description of the non-terrestrial network architecture on which the communication method in this embodiment is based:

[0120] Ground mobile terminals access the network via a new air interface. Network equipment is deployed on satellites and connected to the ground core network via wireless links. Simultaneously, wireless links exist between satellites to facilitate signaling interaction and user data transmission between network devices. The network elements in Figure 1b and their interfaces are described below:

[0121] Terminal: Mobile devices that support the New Radio interface, typically such as mobile phones and tablets. They can access satellite networks via the air interface and initiate services such as making calls and accessing the internet.

[0122] Network equipment primarily provides wireless access services, allocates wireless resources to access terminals, and provides reliable wireless transmission protocols and data encryption protocols. Network equipment deployed on satellites is referred to as NTN nodes.

[0123] Core Network: Handles user access control, mobility management, session management, user security authentication, billing, and other services. It consists of multiple functional units, which can be divided into control plane and data plane functional entities. The Access and Mobility Management Unit (AMF) is responsible for user access management, security authentication, and mobility management. The User Plane Unit (UPF) is responsible for managing user plane data transmission, traffic statistics, and other functions.

[0124] Ground station: Responsible for forwarding signaling and service data between satellite base stations and the core network. A ground station is a network device deployed on the ground. Ground stations used for distributing and collecting satellite communication service data, or for exchanging data within the satellite communication network and routing data to external networks, are called gateway stations. A gateway station can be a network device, a component of a network device (such as a processor, chip, or chip system), or a logic module or software that implements all or part of the functions of the network device.

[0125] New Radio: The wireless link between a terminal and a base station.

[0126] Xn interface: The interface between base stations, mainly used for signaling interaction such as handover.

[0127] NG interface: The interface between the base station and the CN, mainly used for exchanging non-access stratum (NAS) signaling of the core network and user service data.

[0128] The terminal device in Figure 1b can be located within the beam or cell coverage area of ​​the network device. The terminal device can communicate with the network device via the uplink (UL) or downlink (DL). For example, in the UL direction, the terminal device can send uplink data to the network device via the physical uplink shared channel (PUSCH); in the DL direction, the network device can send downlink data to the terminal device via the physical downlink shared channel (PDSCH). The terminal device can be a terminal device supporting the new radio interface, which can access the network device via the air interface and initiate services such as calls and internet access. For example, the network device can be a RAN device mounted on a flight platform. When the RAN device is mounted on the flight platform, the RAN device moves synchronously with the flight platform. The RAN device and the flight platform can be considered as a single unit. In this case, the flight platform can be regarded as the RAN device, or it can be described as the flight platform operating in regenerative mode, meaning the flight platform possesses the functions of the RAN device. Additionally, the communication link between the flight platform and the terminal equipment can be referred to as a service link. When the communication system includes multiple flight platforms, the flight platforms can communicate with each other through the Xn interface. In practical applications, the network equipment can also be RAN equipment distributed on the flight platform based on DU, or it can directly serve as the flight platform; the specifics are not limited here.

[0129] The aforementioned flight platform can be a satellite, drone, or other aircraft. For example, the flight platform may include geostationary earth orbit (GEO) satellites, non-geostationary orbit satellites, low-earth orbit (LEO) satellites, medium-earth orbit (MEO) satellites, geosynchronous orbit satellites, unmanned aerial vehicle (UAV) system platforms, high altitude platform stations (HAPS), hot air balloons, or high-orbit satellites, etc., and is not specifically limited here. This application uses a satellite as the flight platform for illustration.

[0130] Low-Earth orbit (LEO) and medium-Earth orbit (MEO) satellites can have their own orbital paths, and multiple satellites typically work together to provide communication over a fixed area. High-Earth orbit (GEO) satellites are generally stationary, and one or a few high-Earth orbit satellites provide communication over a fixed area.

[0131] Furthermore, the embodiments of this application can also be applied to other future communication technologies. The network architecture and service scenarios described in this application are for the purpose of more clearly illustrating the technical solutions of this application, and do not constitute a limitation on the technical solutions provided in this application. As those skilled in the art will understand, with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided in this application are also applicable to similar technical problems.

[0132] The following is a brief introduction to the concepts that may be involved in this application.

[0133] 1) Time-domain unit:

[0134] The unit of time-domain resources can be called a time-domain unit. In the embodiments of this application, a time-domain unit can be any one of the following: symbol, orthogonal frequency division multiplexing (OFDM) symbol, slot, sensing slot, mini-slot, partial slot, and sub-frame.

[0135] 2) 90ms frame structure:

[0136] The 105th 3GPP plenary meeting adopted a new work item description (WID): It proposes a new time division duplex (TDD) mode for narrowband internet of things (NB-IoT) non-terrestrial networks (NTN), allowing the configuration of radio resource usage within frequency bands allocated by the target mobile satellite service (MSS). Specifically, it defines a periodic subset of uplink (UL) and downlink (DL) subframes over N radio frames. The periodic mode should consist of a non-overlapping set of available consecutive UL subframes, a set of available consecutive DL subframes, and a guard period (GP). This TDD mode requires a period of N radio frames, with a base value of 9 for N. Blind detection is not assumed at the UE end. The value of N and the configuration of the periodic mode are fixed and inflexible configurations within each frequency band. The latest RAN1 meeting concluded that it is feasible to have 8 consecutive downlink subframes and 8 consecutive uplink subframes within a 90-millisecond (ms) TDD period. Figure 2 illustrates one possible implementation of the 90ms frame structure.

[0137] 3) Uplink / downlink scheduling of NB-IoT:

[0138] Figure 3 illustrates a schematic diagram of DL scheduling in NB-IoT under Frequency Division Duplex (FDD) mode. Network devices send downlink control information (DCI) to terminal devices via the narrow-band physical downlink control channel (NPDCCH), instructing the terminal devices to begin receiving downlink information from downlink subframe n0. This downlink information is carried on the narrow-band physical downlink shared channel (NPDSCH). As shown in Figure 3, time unit n represents the end subframe position of the NPDCCH. Since the terminal device requires a 5ms processing delay, downlink information reception begins after a delay of k0 subframes starting from subframe n+5.

[0139] k0 refers to the number of NB-IoT downlink subframes from FDD downlink subframe n+5 to downlink subframe n0, where k0 is determined by the scheduling delay field (I) in DCI format N1. DelayFor DCI format N2, k0 = 0. Table 2 shows the values ​​of k0 for DCI format N1 in downlink scheduling.

[0140] Table 2: Values ​​of k0 corresponding to DCI format N1 in downlink scheduling

[0141] Among them, R max Used to indicate the aggregation and repetition levels of the search space.

[0142] Figure 4 illustrates a schematic diagram of UL scheduling in FDD mode for NB-IoT. The network device sends a DCI to the terminal device via NPDCCH, instructing the terminal device to send uplink information starting from subframe n0. This uplink information is carried on the narrow-band physical uplink shared channel (NPDSCH). Wherein, K... offset The configuration is carried by the SIB31-NB, and its value ranges from 0 to 1023ms. Subframe n+K offset The first uplink slot after +k0 is designated as n0, and uplink information is transmitted at position n0 of subframe. Table 3 shows the values ​​of k0 corresponding to N0 in DCI format during uplink scheduling.

[0143] Table 3: Values ​​of k0 corresponding to DCI format N0 in uplink scheduling

[0144] However, if downlink or uplink scheduling is performed in the above manner within a 90ms frame structure, it may result in the inability to schedule downlink or uplink data to available subframes. Taking uplink scheduling as an example, as shown in Figure 5, when k0 is 8, 16, and 32, the uplink information is transmitted in the UL subframe of the first period; when k0 is 64, the uplink information is transmitted in the UL subframe of the second period. Therefore, in practical applications, the available scheduling positions are limited, and it is impossible to select a resource position to start transmission within 8ms of the DL or UL subframe, thus restricting scheduling.

[0145] Based on this, this application provides a method. Referring to Figure 6, a communication method in this application includes:

[0146] 601. The network device sends downlink control information to the terminal device. Correspondingly, the terminal device receives the downlink control information from the network device.

[0147] The network device sends the DCI to the terminal device via the NPDCCH, and the terminal device decodes it to obtain the DCI. The DCI is used to indicate first information, which includes the period of the first time domain resource. The first information is used to determine the first time domain unit, which is located within the first time domain resource.

[0148] The first time-domain resource has a time-domain length of 90ms, comprising 8ms of uplink time-domain resources and 8ms of downlink time-domain resources. Any one of the first time-domain resource, uplink time-domain resource, and downlink time-domain resource can include one or more time-domain units. That is, the system can be configured with a 90ms TDD frame structure, which repeats periodically in the time domain. Each 90ms frame structure contains 8ms of uplink time-domain resources and 8ms of downlink time-domain resources. The first time-domain resource can be understood as one of these 90ms frame structures. For example, a 90ms frame (or radio frame) may have a first time-domain resource, comprising 8ms of uplink subframes and 8ms of downlink subframes. See Figure 2 for details, which will not be elaborated here. The first time-domain unit is located in the uplink time-domain resource, or the first time-domain unit is located in the downlink time-domain resource. Specifically, when the first time domain unit is located in the downlink time domain resource, step 602a is executed; when the first time domain unit is located in the uplink time domain resource, step 602b is executed. This embodiment uses a 90ms frame as an example, including an 8ms uplink subframe and an 8ms downlink subframe. In practical applications, the first time domain resource can also be other time domain units, such as a set of multiple subframes or a set of multiple time slots; the specific type is not limited here.

[0149] 602a. The terminal device begins receiving downlink information from the first time domain unit.

[0150] Specifically, downlink information is carried on the NPDSCH. The terminal device receiving downlink information from the first time domain unit can be understood as the terminal device receiving the signal on the NPDSCH used to carry downlink information from the first time domain unit.

[0151] 602b. The terminal device starts sending uplink information from the first time domain unit.

[0152] Specifically, uplink information is carried on the NPUSCH. The terminal device sending uplink information starting from the first time domain unit can be understood as the terminal device sending signals to carry uplink information on the NPUSCH starting from the first time domain unit.

[0153] In this embodiment, since the first time domain unit is determined according to the period of the first time domain resource, the terminal device can receive downlink information on downlink subframes of different periods, or send uplink information on uplink subframes of different periods, thereby achieving flexible scheduling.

[0154] The following sections describe the content of the first information and the method for determining the first time domain unit for downlink scheduling and uplink scheduling, respectively.

[0155] I. Downlink Scheduling.

[0156] In downlink scheduling, the terminal device receives downlink information starting from the first time domain unit, and the downlink information is carried in the NPDSCH. The DCI is used to indicate the first information, which includes, in addition to the period of the first time domain resource, at least one of a first parameter, a first offset value, and a second parameter. The second parameter is k0, used to indicate the number of time domain units with delay. In this embodiment, the time domain unit can be any one of a symbol, an orthogonal frequency division multiplexing (OFDM) symbol, a slot, a sensing slot, a mini-slot, a partial slot, or a sub-frame. The following description uses a sub-frame as an example to illustrate how the first time domain unit (or first sub-frame) is determined.

[0157] For DCI format N1, DCI includes a scheduling delay field (I Delay ). Among them, I Delay Corresponding to the first parameter k1 and / or the second parameter k0, the first parameter k1 is used to indicate the number of repetitions in the period in which the first time domain unit is located.

[0158] In one possible implementation, the terminal device can determine the first time-domain unit based on the end subframe of the NPDCCH and the first parameter k1. For example, the first time-domain unit n0 satisfies: n0 = n + k1 * T. Where n is the end subframe of the NPDCCH, and T is the period of the first time-domain resource (i.e., 90 ms). Table 4 below shows I... Delay One possible implementation of the correspondence between the parameter and the first parameter k1.

[0159] Table 4: I Delay Correspondence with the first parameter k1

[0160] As shown in Table 4, when k1 is 1, the first time domain unit n0 is n+T; when k1 is 2, the first time domain unit is n+2T; when k1 is 3, the first time domain unit is n+3T; and when k1 is 4, the first time domain unit is n+4T. Figure 7 is a possible schematic diagram of the first time domain unit. The terminal device determines the first time domain unit based on the DCI, and then starts receiving downlink information from the first time domain unit.

[0161] As shown in Figure 7, since the first time-domain unit can be located on downlink subframes of different periods, the network device can indicate multiple scheduling positions to the terminal device through DCI, thereby achieving flexible scheduling.

[0162] Optionally, to ensure that the first time-domain unit is located at the beginning of the downlink subframe, the first information may further include a first offset value. For example, as shown in Figure 8, the first parameter k1 is 1, meaning the first time-domain unit is within the downlink subframe of the first repetition period. The first time-domain unit n0 satisfies: n0 = n + k1 * T - offset, where offset is the first offset value, used to indicate the offset between the end time-domain unit n of the NPDCCH and the beginning time-domain unit of the downlink subframe within the first period of the downlink subframe.

[0163] It should be noted that the offset between the end time domain unit n of the NPDCCH and the start time domain unit of the downlink subframe can be understood as the offset between the end subframe n of the NPDCCH and the start subframe of the downlink subframe.

[0164] Optionally, the terminal device can also determine the first time-domain unit based on the second parameter k0. For example, the first time-domain unit n0 satisfies: n0 = n + k1*T + k0. By determining the second parameter k0, the network device can indicate multiple scheduling positions within the same downlink subframe, thereby achieving flexible scheduling.

[0165] For example, as shown in Figure 9, the first parameter k1 is 1, meaning the first time-domain unit is within the downlink subframe of the first repetition period. When k0 is 0, the first time-domain unit is at the beginning position of the downlink subframe; when k0 is greater than 0 and less than 8, all first time-domain units are within the downlink subframe. The network device can indicate the specific position of the first time-domain unit in the downlink subframe by indicating the value of k0. The value of the second parameter k0 is determined by the delay scheduling field in the DCI. Table 5 below shows I Delay One possible implementation of the correspondence between the second parameter k0 and the second parameter k0.

[0166] Table 5: I Delay Correspondence with the second parameter k0

[0167] As shown in Table 5, combined with the value of the first parameter k1 shown in Table 4 above, the position of the first time domain unit can be indicated in multiple ways, thereby achieving flexible scheduling.

[0168] It should be noted that when the first parameter k1 is 0, the second parameter k0 is set to 5 to ensure a minimum delay of 5ms. Table 6 below shows I Delay One possible implementation of the correspondence between the first parameter k1 and the second parameter k0.

[0169] Table 6: I Delay The correspondence between the first parameter k1 and the second parameter k0

[0170] As shown in Table 6 above, when different delay scheduling fields indicate the same first parameter k1, different second parameters k0 can be used to indicate different time-domain positions (as shown in Figure 9). When different delay scheduling fields indicate the same second parameter k0, different first parameters k1 can be used to indicate different periods. Based on this, the network device can indicate multiple possible time-domain positions of the first time-domain unit to the terminal device, thereby adapting the downlink information on the NPDSCH scheduled by the DCI to the 90ms frame structure, and thus achieving flexible scheduling.

[0171] In another possible implementation, for DCI format N2, the second parameter k0 is 0. Therefore, the first time domain unit n0 satisfies: n0 = n + T - offset, so that the terminal device receives downlink information through NPDSCH at the starting position of downlink resources in the next cycle.

[0172] In this embodiment of the application, by adapting the downlink information scheduled by DCI format N2 based on a 90ms frame structure, the downlink information sent on NPDSCH can be normally received by the terminal device.

[0173] The above describes how the first time domain unit is determined when a network device performs downlink scheduling via DCI. The following describes how the first time domain unit is determined when a network device performs uplink scheduling via DCI.

[0174] II. Uplink scheduling.

[0175] In uplink scheduling, the terminal device begins sending uplink information from the first time domain unit, and this uplink information is carried on the NPUSCH. Since network devices in NTNs are typically deployed on in-flight platforms, there is a significant time delay between the network devices and the terminal devices. Therefore, the network devices can use K... offset (i.e., the second offset value) is used to indicate the latency between network devices and terminal devices.

[0176] DCI is used to indicate first information, which includes, in addition to the period of the first time domain resource and the second offset value, at least one of the first parameter, the first offset value and the second parameter.

[0177] For DCI format N1, DCI includes a scheduling delay field (I Delay ). Among them, I Delay Corresponding to the first parameter k1 and / or the second parameter k0, the first parameter k1 is used to indicate the number of repetitions in the period in which the first time domain unit is located.

[0178] In one possible implementation, the terminal device can determine the first time-domain unit based on the end subframe of the NPDCCH and the first parameter k1. For example, the first time-domain unit n0 satisfies: n0 = n + K offset +k1*T. Where n is the ending subframe of NPDCCH, and T is the period of the first temporal resource (i.e., 90ms). Table 7 below shows I Delay One possible implementation of the correspondence between the parameter and the first parameter k1.

[0179] Table 7: I Delay Correspondence with the first parameter k1

[0180] As shown in Table 7, when k1 is 0, the first time-domain unit n0 is n+K. offset When k1 is 1, the first time-domain unit is n+K. offset +T; When k1 is 2, the first time-domain unit is n+K. offset +2T; When k1 is 3, the first time-domain unit is n+K. offset +3T. Figure 10 is a possible schematic diagram of the first time domain unit. The terminal device determines the first time domain unit based on the DCI, and then starts sending uplink information from the first time domain unit.

[0181] It should be noted that the second offset value K shown in Figure 10 offset The value of is configured by the network device to ensure that subframe n+K offset At the beginning of the uplink subframe. In another possible implementation, the second offset value K offset The value of k1 is the same as the length of the GP frame. As shown in Figure 11, the first time-domain unit is determined based on the first parameter k1 and the second parameter k0. The value of the second parameter k0 is determined by the delay scheduling field in the DCI. Table 8 below shows I Delay One possible implementation of the correspondence between the second parameter k0 and the second parameter k0.

[0182] Table 8: I Delay Correspondence with the second parameter k0

[0183] As shown in Table 8, by combining the values ​​of the first parameter k1 shown in Table 7 above, the position of the first time domain unit can be indicated in multiple ways, thereby achieving flexible scheduling.

[0184] It should be noted that the second parameter k0 indicated by different delay scheduling fields can be the same. For example, see Table 9 below:

[0185] Table 9: I Delay The correspondence between the first parameter k1 and the second parameter k0

[0186] Based on this, network devices can indicate multiple possible time-domain positions of the first time-domain unit to terminal devices, thereby adapting the uplink information on the NPUSCH scheduled by DCI to the 90ms frame structure and thus achieving flexible scheduling.

[0187] In this embodiment of the application, by indicating the value of the second parameter k0, the uplink information is sent from the beginning position of the uplink subframe, thereby avoiding scheduling restrictions.

[0188] The communication method in the embodiments of this application has been described above. The communication device in the embodiments of this application is described below. Please refer to FIG12. The communication device 1200 can be used to execute the process executed by the terminal device in the embodiment shown in FIG6. For details, please refer to the relevant description in the foregoing method embodiments. The communication device 1200 can be a terminal device, or a component or device applied to the terminal device (e.g., a module, a communication module, a circuit or chip responsible for communication functions (e.g., a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core), or a logic module or software that can implement all or part of the functions of the terminal device.

[0189] The communication device 1200 includes an interface module 1201 and a processing module 1202.

[0190] The processing module 1202 is used for data processing. The interface module 1201 can implement corresponding communication functions. The interface module 1201 can also be called a communication interface or a communication module.

[0191] Optionally, the communication device 1200 may further include a storage module, which can be used to store program code, program instructions and / or data. The processing module 1202 can read the instructions and / or data in the storage module so that the communication device 1200 can implement the aforementioned method embodiments.

[0192] The communication device 1200 can be used to perform the actions performed by the terminal device in the above method embodiments. For example, it can be a terminal device, a communication module within a terminal device, or a circuit or chip within a terminal device responsible for communication functions. The communication device 1200 can be a terminal device or a component configurable on a terminal device. The processing module 1202 is used to perform processing-related operations on the terminal device side in the above method embodiments. The interface module 1201 is used to perform reception-related operations on the terminal device side in the above method embodiments.

[0193] Optionally, the interface module 1201 may include a sending module and a receiving module. The sending module is used to perform the sending operation in the above method embodiments. The receiving module is used to perform the receiving operation in the above method embodiments.

[0194] It should be noted that the communication device 1200 may include a transmitting module but not a receiving module. Alternatively, the communication device 1200 may include a receiving module but not a transmitting module. Specifically, it depends on whether the above-described scheme executed by the communication device 1200 includes both transmitting and receiving actions. For example, the communication device 1200 is used to execute the actions performed by the terminal device in the embodiment shown in FIG. 6. For details, please refer to the relevant description in the embodiment shown in FIG. 6; it will not be elaborated upon here.

[0195] For example, the communication device 1200 is used to execute the following scheme:

[0196] Interface module 1201 is used to receive downlink control information, which is used to indicate first information, including the period of the first time domain resource, and is used to determine the first time domain unit, which is located within the first time domain resource;

[0197] Processing module 1202 is used to determine the first time domain unit;

[0198] Interface module 1201 is also used to receive downlink information starting from the first time domain unit, or to send uplink information starting from the first time domain unit.

[0199] The descriptions of downlink control information, first time domain resources, and first time domain units can be found in the aforementioned embodiments, and will not be repeated here.

[0200] It should be understood that the specific procedures for each module to perform the above-mentioned corresponding processes have been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0201] Optionally, when the communication device 1200 is a terminal device or a communication module within a terminal device, the processing module 1202 in the above embodiments can be implemented by at least one processor or processor-related circuitry. Specifically, the processor may include a modem chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip. The interface module 1201 can be implemented by a transceiver or transceiver-related circuitry. The interface module 1201 may also be referred to as a communication module or communication interface. The storage module can be implemented by at least one memory.

[0202] Optionally, when the communication device 1200 is a circuit or chip in a terminal device responsible for communication functions, such as a modem chip or a SoC chip or SIP chip containing a modem core, the function of the processing module 1202 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processing cores. The function of the interface module 1201 can be implemented by the interface circuit or data transceiver circuit on the aforementioned chip.

[0203] The following is another structural schematic diagram of the communication device according to an embodiment of this application. Referring to FIG13, the communication device can be used to execute the process performed by the network device in the embodiment shown in FIG6. For details, please refer to the relevant description in the foregoing method embodiments. The communication device 1300 can be a network device, or a component or device applied to a network device (e.g., a module, communication module, circuit or chip responsible for communication function (such as a modem chip, or a SoC chip or SIP chip containing a modem core), chip system or processor), or a logic module or software that can implement all or part of the functions of the network device.

[0204] The communication device 1300 includes an interface module 1301. Optionally, a processing module 1302.

[0205] The processing module 1302 is used for data processing. The interface module 1301 can implement corresponding communication functions. The interface module 1301 can also be called a communication interface or a communication module.

[0206] Optionally, the communication device 1300 may further include a storage module, which can be used to store program code, program instructions and / or data. The processing module 1302 can read the instructions and / or data in the storage module so that the communication device 1300 can implement the aforementioned method embodiments.

[0207] The communication device 1300 can be used to perform the actions performed by the network device in the above method embodiments. For example, it can be a network device or a communication module within a network device, or a circuit or chip within a network device responsible for communication functions. The communication device 1300 can be a network device or a component configurable within a network device. The processing module 1302 is used to perform processing-related operations on the network device side in the above method embodiments. The interface module 1301 is used to perform reception-related operations on the network device side in the above method embodiments.

[0208] Optionally, interface module 1301 may include a sending module and a receiving module. The sending module is used to perform the sending operation in the above method embodiments. The receiving module is used to perform the receiving operation in the above method embodiments.

[0209] It should be noted that the communication device 1300 may include a transmitting module but not a receiving module. Alternatively, the communication device 1300 may include a receiving module but not a transmitting module. Specifically, it depends on whether the above-described scheme performed by the communication device 1300 includes both transmitting and receiving actions. For example, the communication device 1300 is used to perform the actions performed by the network device in the embodiment shown in FIG. 6. For details, please refer to the relevant description in the embodiment shown in FIG. 6; it will not be elaborated upon here.

[0210] For example, the communication device 1300 is used to execute the following scheme:

[0211] Processing module 1302 is used to determine downlink control information, which is used to indicate first information, including the period of the first time domain resource, and to determine the first time domain unit, which is located within the first time domain resource;

[0212] Interface module 1301 is used to send downlink control information.

[0213] The descriptions of downlink control information, first time domain resources, and first time domain units can be found in the aforementioned embodiments, and will not be repeated here.

[0214] It should be understood that the specific procedures for each module to perform the above-mentioned corresponding processes have been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0215] The processing module 1302 in the above embodiments can be implemented by at least one processor or processor-related circuitry. The interface module 1301 can be implemented by a transceiver or transceiver-related circuitry. The interface module 1301 can also be referred to as a communication module or communication interface. The storage module can be implemented by at least one memory.

[0216] The following describes a communication device provided in an embodiment of this application. Please refer to Figure 14, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device can be a terminal device or a network device as described in the above method embodiments, or it can be a chip, chip system, or processor that supports the terminal device or network device in implementing the above methods. This communication device can be used to implement the methods described in the above method embodiments, and for details, please refer to the description in the above method embodiments.

[0217] The communication device may include one or more processors 1401, which are connected to a memory 1402, an input / output unit 1403, and a bus 1404. The processor 1401 may 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 the communication device (e.g., base station, baseband chip, terminal, terminal chip, DU or CU, etc.), execute software programs, and process data from the software programs.

[0218] Optionally, the communication device may include one or more memories 1402, which may store instructions that can be executed on the processor 1401, causing the communication device to perform the methods described in the above method embodiments. Optionally, the memories 1402 may also store data. The processor 1401 and the memories 1402 may be configured separately or integrated together.

[0219] Optionally, the communication device may also include a transceiver and an antenna. A transceiver, also called a transceiver unit, transceiver, or transceiver circuit, is used to implement transmission and reception functions. A transceiver may include a receiver and a transmitter; the receiver, also called a receiver circuit, is used to implement the receiving function; the transmitter, also called a transmitter or transmitting circuit, is used to implement the transmitting function.

[0220] In another possible design, the processor 1401 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or for transmitting or relaying signals.

[0221] In another possible design, the processor 1401 may optionally store instructions that, when executed, cause the communication device to perform the methods described in the above method embodiments. The instructions may be stored in the processor 1401; in this case, the processor 1401 may be implemented in hardware.

[0222] In another possible design, the communication device may include a circuit that can perform the sending or receiving or communication functions of the terminal device or network device in the aforementioned method embodiments. The processor and transceiver described in this application embodiment can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-type metal-oxide-semiconductor (NMOS), p-type metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0223] The communication device described in the above embodiments can be a terminal device or a network device, but the scope of the communication device described in the embodiments of this application is not limited thereto, and the structure of the communication device is not limited to FIG14. The communication device can be a standalone device or part of a larger device. For example, the communication device can be:

[0224] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0225] (2) A collection of one or more ICs, optionally including a storage component for storing data and instructions;

[0226] (3) ASIC, such as modem;

[0227] (4) Modules that can be embedded in other devices;

[0228] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.

[0229] (6) Others, etc.

[0230] For communication devices that can be chips or chip systems, please refer to the structural diagram of the chip shown in Figure 15. The chip 1500 shown in Figure 15 includes a processor 1501 and an interface 1502. Optionally, it may also include a memory 1503. The number of processors 1501 can be one or more, and the number of interfaces 1502 can be multiple.

[0231] For cases where the chip is used to implement the functions of the network device or terminal device in the embodiments of this application:

[0232] The interface 1502 is used to receive or output signals;

[0233] The processor 1501 is used to perform data processing operations on network devices or terminal devices.

[0234] It should also be understood that the above naming is defined solely for the purpose of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other names in 5G networks and other future networks. For example, in future communication networks, some or all of the above-mentioned network elements may retain the names used in 5G, or they may adopt other names, etc.

[0235] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the communication device given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0236] It should be understood that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0237] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAK are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0238] This application also provides a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the methods described in the foregoing embodiments. The computer-readable storage medium may be a non-volatile storage medium.

[0239] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods described in the foregoing embodiments.

[0240] Those skilled in the art will clearly 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.

[0241] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0242] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0243] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0244] 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, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0245] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted 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)).

[0246] The embodiments described in this application are merely some, not all, of the embodiments described herein. All other embodiments obtained by those skilled in the art based on the embodiments described herein without inventive effort are within the scope of protection of this application.

[0247] References to "one embodiment" or "some embodiments" as described in this application mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0248] In the description of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. "And / or" in this document is merely a description of 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, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, and c can be single or multiple.

Claims

1. A communication method, characterized in that, The method includes: Receive downlink control information, the downlink control information being used to indicate first information, the first information including the period of a first time domain resource, the first information being used to determine a first time domain unit, the first time domain unit being located within the first time domain resource; Receive downlink information starting from the first time domain unit, or send uplink information starting from the first time domain unit.

2. A communication method, characterized in that, The method includes: Determine downlink control information, the downlink control information being used to indicate first information, the first information including the period of a first time domain resource and the end time domain unit of the narrowband physical downlink control channel, the first information being used to determine the first time domain unit, the first time domain unit being located within the first time domain resource; Send the downlink control information.

3. The method according to claim 1 or 2, characterized in that, The time domain length of the first time domain resource is 90ms. The first time domain resource includes 8ms of uplink time domain resource and 8ms of downlink time domain resource. The first time domain unit is located within the uplink time domain resource, or the first time domain unit is located within the downlink time domain resource. The downlink information is carried on a narrowband physical downlink shared channel, and the uplink information is carried on a narrowband physical uplink shared channel.

4. The method according to claim 3, characterized in that, The first time domain unit is located within the downlink time domain resource. The first information also includes a first parameter, which is used to indicate the number of repetitions of the period in which the first time domain unit is located. The first parameter is determined based on the scheduling delay domain in the downlink control information.

5. The method according to claim 4, characterized in that, The first time-domain unit n0 satisfies: n0 = n + k1 * T; Alternatively, the first time-domain unit n0 satisfies: n0 = n + k1 * T - offset; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, k1 is the first parameter, T is the period of the first time domain resource, and offset is the first offset value. The first offset value is used to indicate the offset value between the end domain unit of the narrowband physical downlink control channel and the start time domain unit of the downlink time domain resource within a downlink time domain resource.

6. The method according to any one of claims 3 to 5, characterized in that, The first time domain unit is located within the downlink time domain resource. The first information also includes a first offset value, which is used to indicate the offset value between the end time domain unit of the narrowband physical downlink control channel and the start time domain unit of the downlink time domain resource within the downlink time domain resource. The downlink control information is carried in the narrowband physical downlink control channel.

7. The method according to claim 6, characterized in that, The first time-domain unit n0 satisfies: n0 = n + T - offset; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, T is the period of the first time domain resource, and offset is the first offset value.

8. The method according to any one of claims 3 to 7, characterized in that, The first time domain unit is located within the uplink time domain resource, and the first information also includes a second offset value, which is a parameter configured by the network device.

9. The method according to claim 8, characterized in that, The first time-domain unit n0 satisfies: n0 = n + K offset +T; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, and K offset The second offset value is given, where T is the period of the first time-domain resource.

10. The method according to claim 8 or 9, characterized in that, The first information also includes a first parameter, which indicates the number of repetitions in the period in which the first time domain unit is located. The first parameter is determined based on the scheduling delay domain in the downlink control information.

11. The method according to claim 10, characterized in that, The first time-domain unit n0 satisfies: n0 = n + K offset +k1*T; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, and K offset The second offset value is given, k1 is the first parameter, and T is the period of the first time-domain resource.

12. The method according to any one of claims 1 to 11, characterized in that, The first information also includes a second parameter, which indicates the number of time-domain units of the delay, and the second parameter is determined based on the scheduling delay domain in the downlink control information.

13. A communication device, characterized in that, include: An interface module is used to receive downlink control information, which is used to indicate first information, the first information including the period of a first time domain resource, and the first information is used to determine a first time domain unit, which is located within the first time domain resource; The processing module is used to determine the first time-domain unit; The interface module is also configured to receive downlink information from the first time domain unit, or to send uplink information from the first time domain unit.

14. The apparatus according to claim 13, characterized in that, The time domain length of the first time domain resource is 90ms. The first time domain resource includes 8ms of uplink time domain resource and 8ms of downlink time domain resource. The first time domain unit is located within the uplink time domain resource, or the first time domain unit is located within the downlink time domain resource. The downlink information is carried on a narrowband physical downlink shared channel, and the uplink information is carried on a narrowband physical uplink shared channel.

15. The apparatus according to claim 14, characterized in that, The first time domain unit is located within the downlink time domain resource. The first information also includes a first parameter, which is used to indicate the number of repetitions of the period in which the first time domain unit is located. The first parameter is determined based on the scheduling delay domain in the downlink control information.

16. The apparatus according to claim 15, characterized in that, The first time-domain unit n0 satisfies: n0 = n + k1 * T; Alternatively, the first time-domain unit n0 satisfies: n0 = n + k1 * T - offset; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, k1 is the first parameter, T is the period of the first time domain resource, and offset is the first offset value. The first offset value is used to indicate the offset value between the end domain unit of the narrowband physical downlink control channel and the start time domain unit of the downlink time domain resource within a downlink time domain resource.

17. The apparatus according to any one of claims 14 to 16, characterized in that, The first time domain unit is located within the downlink time domain resource. The first information also includes a first offset value, which is used to indicate the offset value between the end time domain unit of the narrowband physical downlink control channel and the start time domain unit of the downlink time domain resource within the downlink time domain resource. The downlink control information is carried in the narrowband physical downlink control channel.

18. The apparatus according to claim 17, characterized in that, The first time-domain unit n0 satisfies: n0 = n + T - offset; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, T is the period of the first time domain resource, and offset is the first offset value.

19. The apparatus according to any one of claims 14 to 18, characterized in that, The first time domain unit is located within the uplink time domain resource, and the first information also includes a second offset value, which is a parameter configured by the network device.

20. The apparatus according to claim 19, characterized in that, The first time-domain unit n0 satisfies: n0 = n + K offset +T; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, and K offset The second offset value is given, where T is the period of the first time-domain resource.

21. The apparatus according to claim 19 or 20, characterized in that, The first information also includes a first parameter, which indicates the number of repetitions in the period in which the first time domain unit is located. The first parameter is determined based on the scheduling delay domain in the downlink control information.

22. The apparatus according to claim 21, characterized in that, The first time-domain unit n0 satisfies: n0 = n + K offset +k1*T; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, and K offset The second offset value is given, k1 is the first parameter, and T is the period of the first time-domain resource.

23. The apparatus according to any one of claims 13 to 22, characterized in that, The first information also includes a second parameter, which indicates the number of time-domain units of the delay, and the second parameter is determined based on the scheduling delay domain in the downlink control information.

24. A communication device, characterized in that, include: The processing module is used to determine downlink control information, which is used to indicate first information, the first information including the period of a first time domain resource, and the first information is used to determine a first time domain unit, which is located within the first time domain resource; The interface module is used to send the downlink control information.

25. The apparatus according to claim 24, characterized in that, The time domain length of the first time domain resource is 90ms. The first time domain resource includes 8ms of uplink time domain resource and 8ms of downlink time domain resource. The first time domain unit is located within the uplink time domain resource, or the first time domain unit is located within the downlink time domain resource. The downlink information is carried on a narrowband physical downlink shared channel, and the uplink information is carried on a narrowband physical uplink shared channel.

26. The apparatus according to claim 25, characterized in that, The first time domain unit is located within the downlink time domain resource. The first information also includes a first parameter, which is used to indicate the number of repetitions of the period in which the first time domain unit is located. The first parameter is determined based on the scheduling delay domain in the downlink control information.

27. The apparatus according to claim 26, characterized in that, The first time-domain unit n0 satisfies: n0 = n + k1 * T; Alternatively, the first time-domain unit n0 satisfies: n0 = n + k1 * T - offset; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, k1 is the first parameter, T is the period of the first time domain resource, and offset is the first offset value. The first offset value is used to indicate the offset value between the end domain unit of the narrowband physical downlink control channel and the start time domain unit of the downlink time domain resource within a downlink time domain resource.

28. The apparatus according to any one of claims 25 to 27, characterized in that, The first time domain unit is located within the downlink time domain resource. The first information also includes a first offset value, which is used to indicate the offset value between the end time domain unit of the narrowband physical downlink control channel and the start time domain unit of the downlink time domain resource within the downlink time domain resource. The downlink control information is carried in the narrowband physical downlink control channel.

29. The apparatus according to claim 28, characterized in that, The first time-domain unit n0 satisfies: n0 = n + T - offset; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, T is the period of the first time domain resource, and offset is the first offset value.

30. The apparatus according to any one of claims 25 to 29, characterized in that, The first time domain unit is located within the downlink time domain resource, and the first information also includes a second offset value, which is a parameter configured by the network device.

31. The apparatus according to claim 30, characterized in that, The first time-domain unit n0 satisfies: n0 = n + K offset +T; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, and K offset The second offset value is given, where T is the period of the first time-domain resource.

32. The apparatus according to claim 30 or 31, characterized in that, The first information also includes a first parameter, which indicates the number of repetitions in the period in which the first time domain unit is located. The first parameter is determined based on the scheduling delay domain in the downlink control information.

33. The apparatus according to claim 32, characterized in that, The first time-domain unit n0 satisfies: n0 = n + K offset +k1*T; Wherein, n is the end domain unit of the narrowband physical downlink control channel, the downlink control information is carried in the narrowband physical downlink control channel, and K offset The second offset value is given, k1 is the first parameter, and T is the period of the first time-domain resource.

34. The apparatus according to any one of claims 24 to 33, characterized in that, The first information also includes a second parameter, which indicates the number of time-domain units of the delay, and the second parameter is determined based on the scheduling delay domain in the downlink control information.

35. A communication device, characterized in that, include: A processor for executing a program that causes the communication device to perform the method as described in any one of claims 1 to 12.

36. A computer-readable storage medium, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 12.

37. A computer program product containing instructions, characterized in that, When it is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 12.

Images