Communication method and related apparatus

Abstract

The present application provides a communication method and a related apparatus, which are applied to the technical field of communications. In embodiments of the present application, for a scenario in which a moving speed of a terminal changes dynamically, the terminal carries a plurality of TDM modes when reporting auxiliary information, so that a network device can configure an adapted TDM mode for the terminal on the basis of the TDM modes recommended by the terminal when the terminal is in different moving states. The embodiments of the present application can effectively enhance the flexibility of an IDC information reporting process.

Description

Communication method and related apparatus

[0001] The present application claims priority to the Chinese patent application No. 202411815786.2, filed on December 10, 2024, entitled “Communication method and related apparatus”, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, in particular to a communication method and related apparatus. BACKGROUND

[0003] Currently, the same terminal can support 3GPP and non-3GPP functions at the same time, but when the above functions work at the same time in the terminal, In-Device Co-existence (IDC) problems may be caused due to adjacent channel interference (ACI), intermodulation distortion (IMD), etc., and the IDC problems will cause interference on multiple subframes or time slots in the time domain.

[0004] Some solutions use time division multiplexing (TDM) mode to solve IDC problems, thereby reasonably arranging resource scheduling. On the one hand, the solution of solving IDC problems by using the existing TDM mode makes the delay of IDC information reporting process too long, resulting in insufficient flexibility of updating; on the other hand, for the discontinuous reception (DRX) mechanism in the current TDM mode, when the terminal performs Non-Terrestrial networks (NTN) service, only the uplink power leakage will interfere with the reception of global navigation satellite system (GNSS) information, and the downlink will not affect the reception of GNSS. But the current DRX mechanism stops both uplink and downlink services of NTN in the sleep period, that is, the downlink service which is not affected cannot be performed, resulting in low efficiency of NTN service scheduling.

[0005] Therefore, how to effectively enhance the flexibility of IDC information reporting process, reduce the delay of IDC reporting process and improve the efficiency of NTN scheduling on the basis of solving IDC problems is a hot spot for researchers in the field. SUMMARY

[0006] The application provides a communication method and related device, which can effectively enhance the flexibility of IDC information reporting process, reduce the time delay of IDC reporting process, and improve the scheduling efficiency of NTN.

[0007] In a first aspect, the application provides a communication method, which can be applied to a first communication device, such as a terminal or a module in the terminal (wherein the module in the terminal includes a communication module and a computing module), or a circuit or chip responsible for communication function in the terminal (such as a modem chip, also known as a baseband chip, or a system on chip (SoC) chip or a system in package (SIP) chip containing a modem core). The method comprises:

[0008] sending in-device coexistence (IDC) resource information to a second communication device, wherein the IDC resource information carries a plurality of time division multiplexing (TDM) modes;

[0009] sending first reference information to the second communication device, wherein the first reference information is used to indicate a configuration of a first TDM mode, and the first TDM mode belongs to one of the plurality of TDM modes;

[0010] receiving first indication information from the second communication device, wherein the first indication information is used to indicate communication according to the first TDM mode.

[0011] communicating according to the first TDM mode.

[0012] Optionally, the plurality of TDM modes correspond to a plurality of mobile states of the first communication device respectively.

[0013] In the application, the first communication device is taken as a terminal, and the second communication device is taken as a network device. In the case that the moving speed of the terminal is dynamically changing, the TDM mode needs to be frequently updated. In the current scheme, generally, each time the TDM mode is updated, the network device needs to be re-reported with auxiliary information, and then the network device reconfigures the RRC to issue a newly configured DRX cycle to the terminal. This scheme not only wastes the network device side resources but also is not flexible. In the application, in the scenario that the moving speed of the terminal is dynamically changing, the terminal carries a plurality of TDM modes when reporting auxiliary information, so that the network device can configure an adaptive TDM mode for the terminal according to the TDM mode suggested by the terminal in different mobile states. This scheme can effectively enhance the flexibility of IDC information reporting process.

[0014] In a possible implementation, the IDC resource information further carries identifiers corresponding to the plurality of TDM modes respectively, the first reference information carries an identifier corresponding to the first TDM mode, and the first reference information is specifically used to indicate the identifier corresponding to the first TDM mode, and the first indication information is specifically used to indicate that communication is performed according to the first TDM mode by using the identifier corresponding to the first TDM mode.

[0015] In the above implementation, the first communication device is taken as a terminal, and the second communication device is taken as a network device, and the terminal can further report an identifier corresponding to a TDM mode in the process of reporting IDC information. According to the scheme, when the network device configures an adaptive TDM mode for the terminal according to the TDM mode recommended by the terminal in different mobile states of the terminal, the network device does not need to indicate a complete TDM mode configured for the terminal, but only needs to indicate the identifier corresponding to the TDM mode, thereby effectively reducing the time delay of the IDC reporting process and saving the resources of the network device.

[0016] In another possible implementation, the receiving the first indication information from the second communication device includes:

[0017] The first indication information is carried in a medium access control-control element (MAC-CE) from the second communication device.

[0018] In the above implementation, the first communication device is taken as a terminal, and the second communication device is taken as a network device. Because in the existing scheme, the terminal needs to re-report auxiliary information to the network device every time the TDM mode is updated, and then the network device reconfigures the RRC, and the network device only issues a newly configured DRX cycle to the terminal after the reconfiguration, which causes a long time delay of the IDC reporting process. The scheme can effectively reduce the time delay of the IDC reporting process and save the resources of the network device by using MAC-CE to process information.

[0019] In another possible implementation, the communication according to the first TDM mode includes:

[0020] Monitoring a physical downlink control channel (PDCCH) in an inactive period of a discontinuous reception (DRX) cycle, and the PDCCH is only used to schedule downlink data.

[0021] In the above implementation, NTN only interferes with GNSS reception due to uplink power leakage, while downlink is unaffected. However, the existing DRX mechanism stops both uplink and downlink services of NTN during the sleep period, meaning that unaffected downlink services cannot operate normally, resulting in low NTN scheduling efficiency. To address this scenario, based on the existing DRX mechanism, the first communication device can stop scheduling uplink data during the inactive period of the DRX cycle (e.g., the sleep period) while maintaining normal monitoring of the PDCCH channel to ensure normal scheduling of downlink data, thereby effectively improving NTN scheduling efficiency.

[0022] In yet another possible implementation, prior to communicating according to the first TDM mode, the method further includes:

[0023] Receive second indication information, wherein the second indication information is used to indicate monitoring PDCCH during the inactive period of the DRX cycle, wherein the PDCCH is only used for scheduling downlink data.

[0024] In the above implementation, NTN only interferes with GNSS reception due to uplink power leakage, while downlink is unaffected. However, the existing DRX mechanism suspends both uplink and downlink services during the dormant period, meaning that unaffected downlink services cannot operate normally, resulting in low NTN scheduling efficiency. To address this scenario, this solution can instruct the terminal to schedule downlink data by sending indication information from other devices (e.g., a second communication device). For example, based on the existing DRX mechanism, during the inactive period of the DRX cycle (e.g., the dormant period), only uplink data scheduling is stopped, while the PDCCH channel is monitored normally to enable the first communication device to schedule downlink data normally, thereby effectively improving NTN scheduling efficiency.

[0025] In yet another possible implementation, the first communication device is configured to monitor the PDCCH during the inactive period of the DRX cycle.

[0026] In the above implementation, NTN only interferes with GNSS reception due to uplink power leakage, while downlink is unaffected. However, the existing DRX mechanism suspends both uplink and downlink services during the sleep period, meaning that unaffected downlink services cannot function normally, resulting in low NTN scheduling efficiency. To address this scenario, this solution, based on the existing DRX mechanism, allows the terminal to be configured via protocol to only stop scheduling uplink data during the inactive period of the DRX cycle (e.g., the sleep period), while maintaining normal monitoring of the PDCCH channel. This enables the first communication device to schedule downlink data normally, thereby effectively improving NTN scheduling efficiency.

[0027] In yet another possible implementation, the method further includes:

[0028] If the first condition is met, second reference information is sent to the second communication device, wherein the second reference information is used to indicate the configuration of a second TDM mode, and the second TDM mode belongs to one of the plurality of TDM modes other than the first TDM mode.

[0029] Receive third indication information from the second communication device, wherein the third indication information is used to indicate communication according to the second TDM mode. Communicate according to the second TDM mode.

[0030] In the above embodiment, taking the first communication device as the terminal and the second communication device as the network device as an example, when the first condition is met (e.g., the terminal's mobility status changes dynamically), the terminal needs to request an update to the TDM mode from the network device. For example, the terminal can report a suggested TDM mode, which the network device then uses to configure an adapted TDM mode for the terminal. Since the network device has already obtained multiple TDM modes reported by the terminal, it can flexibly allocate TDM modes even if the terminal's mobility status changes dynamically, effectively reducing the latency of the IDC reporting process and saving network device resources.

[0031] In yet another possible implementation, the first condition includes any one of the following:

[0032] The first communication device switches its movement state from a first speed to a second speed; or,

[0033] The movement state of the first communication device changes from the second speed to a stationary state; or,

[0034] The first communication device switches its movement state from the first speed to a stationary state, wherein the first speed is greater than the second speed.

[0035] In the above embodiments, taking the first communication device as the terminal and the second communication device as the network device as an example, since the environment in which the terminal is located and its own mobility state are prone to change, events that are likely to affect the accurate application of the TDM mode (such as the first condition) can be used as triggering conditions for sending the second TDM mode to the second communication device. The second TDM mode is sent to the second communication device only when the triggering condition is met, which can ensure that the TDM mode is targeted while saving the resource consumption of the network device.

[0036] Secondly, embodiments of this application provide a communication method applied to a second communication device. The second communication device may be, for example, a network device or a communication module within a network device, or a circuit or chip within the network device 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). The method includes:

[0037] Receive in-device coexisting IDC resource information from the first communication device, wherein the IDC resource information carries multiple time division multiplexing (TDM) modes;

[0038] Receive first reference information from the first communication device, wherein the first reference information is used to indicate the configuration of a first TDM mode, the first TDM mode belonging to one of the plurality of TDM modes;

[0039] Send a first instruction message to the first communication device, wherein the first instruction message is used to instruct communication to be performed according to the first TDM mode.

[0040] Optionally, the multiple TDM modes correspond to various mobile states of the first communication device.

[0041] In one possible implementation, the IDC resource information also carries identifiers corresponding to the plurality of TDM modes respectively, the first reference information carries the identifier corresponding to the first TDM mode, the first reference information is specifically used to indicate the configuration of the identifier corresponding to the first TDM mode, and the first indication information is specifically used to indicate communication according to the first TDM mode through the identifier corresponding to the first TDM mode.

[0042] In yet another possible implementation, sending the first indication information to the first communication device includes:

[0043] The first instruction information is sent to the first communication device via the Media Access Control-Control Element (MAC-CE).

[0044] In yet another possible implementation, the method further includes:

[0045] Send a second indication message to the first communication device, wherein the second indication message is used to indicate monitoring the PDCCH during the inactive period of the discontinuous reception DRX cycle, and the PDCCH is used only for scheduling downlink data.

[0046] In yet another possible implementation, the method further includes:

[0047] Receive second reference information, wherein the second reference information is used to indicate the configuration of a second TDM mode, the second TDM mode being a TDM mode other than the first TDM mode among the plurality of TDM modes;

[0048] Send a third instruction message to the first communication device, wherein the third instruction message is used to instruct communication to be performed according to the second TDM mode.

[0049] Thirdly, embodiments of this application provide a communication device that can be used in the first communication device of the first aspect. The communication device can be a terminal, a device in the terminal (e.g., a chip, a chip system, or a circuit), or a device that can be matched with the terminal. It can also be a logic module or software that can realize all or part of the terminal functions.

[0050] In one possible implementation, the communication device may include modules or units that perform the methods / operations / steps / actions described in the first aspect. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0051] Fourthly, embodiments of this application provide a communication device that can be used in the second communication device of the second aspect. The communication device can be a network device, a device in a network device (e.g., a chip, a chip system, or a circuit), or a device that can be matched with a network device, or a logic module or software that can implement all or part of the functions of a network device.

[0052] In one possible implementation, the communication device may include modules or units that perform the methods / operations / steps / actions described in the second aspect one by one. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0053] Fifthly, embodiments of this application provide a communication device, which includes at least one processor and a communication interface; the communication interface is used for inputting and / or outputting information, and the at least one processor is used to call a computer program stored in at least one memory to implement the method described in any of the embodiments of the first or second aspect.

[0054] In one possible implementation, the communication device further includes at least one of the aforementioned memories. Optionally, the memory and processor are integrated together.

[0055] In a sixth aspect, embodiments of this application provide a communication device, which includes a logic circuit and an interface, the logic circuit and the interface being coupled; the interface is used to input and / or output information, and the logic circuit is used to implement the method described in any of the embodiments of the first to second aspects.

[0056] In one possible implementation of the sixth aspect, the communication device is a chip or chip system.

[0057] In a seventh aspect, embodiments of this application provide a communication system, which includes a first communication device and a second communication device, and the first communication device and the second communication device are communicatively connected. The first communication device is used to implement the method of any embodiment of the first aspect, and the second communication device is used to implement the method of any embodiment of the second aspect.

[0058] Eighthly, embodiments of this application provide a computer-readable storage medium for storing instructions or computer programs; when the instructions or computer programs are executed, they implement the method of any one of the embodiments of the first to second aspects.

[0059] Ninthly, this application provides a computer program product including computer instructions that, when executed on at least one processor, can implement the methods described in any of the first to second aspects or any possible implementations thereof. Exemplarily, the computer program product can be a software installation package, which can be downloaded and executed on a computing device when the aforementioned methods are required.

[0060] The beneficial effects of the technical solutions provided in the second to ninth aspects of this application can be referred to the beneficial effects of the technical solutions in the first aspect, and will not be repeated here. Attached Figure Description

[0061] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0062] Figure 2 is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0063] Figure 3 is a schematic diagram of an O-RAN system provided in an embodiment of this application;

[0064] Figure 4 is a diagram showing the network element function division and protocol layer structure of an O-RAN system provided in an embodiment of this application;

[0065] Figure 5 is a schematic diagram illustrating an IDC problem provided in an embodiment of this application;

[0066] Figure 6 is a schematic diagram of satellite communication in an NTN provided in an embodiment of this application;

[0067] Figure 7 is a schematic diagram of an NR-NTN UL power leakage interference GNSS receiver provided in an embodiment of this application;

[0068] Figure 8 is a schematic diagram of an auxiliary information reporting method provided in an embodiment of this application;

[0069] Figure 9 is a schematic diagram of an FDM scheme provided in an embodiment of this application;

[0070] Figure 10 is a schematic diagram of the principle of a DRX mechanism provided in an embodiment of this application;

[0071] Figure 11 is a schematic diagram of a TDM solution provided in an embodiment of this application;

[0072] Figure 12 is a schematic diagram of the dynamic change of the DRX cycle provided in an embodiment of this application;

[0073] Figure 13 is a schematic diagram of an uplink / downlink scheduling process provided in an embodiment of this application;

[0074] Figure 14 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0075] Figure 15 is a schematic diagram of multiple TDM modes corresponding to various mobile states of a first communication device according to an embodiment of this application;

[0076] Figure 16 is a schematic diagram showing the corresponding identifiers for multiple TDM modes provided in an embodiment of this application;

[0077] Figure 17 is a schematic diagram of a DRX cycle configuration method provided in an embodiment of this application;

[0078] Figure 18a is a schematic flowchart of a transmission TDM mode provided in an embodiment of this application;

[0079] Figure 18b is a flowchart illustrating another TDM transmission mode provided in an embodiment of this application;

[0080] Figure 18c is a flowchart illustrating another TDM transmission mode provided in an embodiment of this application;

[0081] Figure 19 is a schematic diagram of the structure of a communication device 190 provided in an embodiment of this application;

[0082] Figure 20 is a schematic diagram of another communication device 200 provided in an embodiment of this application;

[0083] Figure 21 is a structural schematic diagram of another communication device 210 provided in an embodiment of this application. Detailed Implementation

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

[0085] The system architecture used in the embodiments of this application is described below. It should be noted that the system architecture and business 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 know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this application are also applicable to similar technical problems.

[0086] Please refer to Figure 1, which is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 1(a), the communication system includes a first communication device 101 and a second communication device 102. Optionally, the communication system further includes a third communication device 103.

[0087] Optionally, the first communication device 101, the second communication device 102, and the third communication device 103 can be of the same type or different types. For example, as shown in Figure 1(b), the first communication device 101 is a terminal, the second communication device 102 is a network device, and the third communication device 103 is a terminal. As shown in Figure 1(c), the first communication device 101 is a terminal, the second communication device 102 is a terminal, and the third communication device 103 is a network device. The architecture of the communication system will now be described in detail, taking the first communication device 101 as a terminal and the second communication device 102 as a network device as an example.

[0088] It is understood that when the communication system only includes the first communication device 101 and the second communication device 102, the communication system only shows one terminal and one network device. In actual use, an architecture of at least one terminal and / or at least one network device can be adopted as needed (e.g., the architecture shown in Figure 1(a)). For example, the communication system shown in Figure 2 includes one network device and multiple terminals, or multiple network devices and one terminal. A single terminal can send IDC resource information to a single network device, and a single network device can send first indication information to a single terminal.

[0089] It is understood that when the communication system includes a first communication device 101, a second communication device 102, and a third communication device 103, such as the architecture shown in Figure 1(b), the communication system shows one network device and two terminals. In actual use, an architecture with at least one terminal and / or at least one network device can be adopted as needed. For example, a single terminal (e.g., represented as terminal 1) can send IDC resource information A to a single network device (e.g., represented as network device 1), a single terminal (e.g., represented as terminal 2) can send IDC resource information B to network device 1, network device 1 can send instruction information A to terminal 1, and network device 2 can also send instruction information B to terminal 2.

[0090] In this embodiment, the terminal involved may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities. The terminal 220 shown in Figure 2 may also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., or a device used to provide voice or data connectivity to users, or an Internet of Things (IoT) device. For example, the terminal includes handheld devices and vehicle-mounted devices with wireless connectivity. Currently, terminals can include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, smart glasses, etc.), in-vehicle equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), satellite terminals, virtual reality (VR) devices, augmented reality (AR) devices, point-of-sale (POS) machines, customer-premises equipment (CPE), light user equipment (UE), reduced capability user equipment (REDCAP UE), wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. The terminal can also be a vehicle device, such as a vehicle unit, vehicle module, vehicle chip, on-board unit (OBU), or telematics box (T-BOX). The terminal can also be other devices with terminal functions. For example, the terminal can also be a device that plays the role of a terminal in D2D communication.

[0091] Typically, network device 210 can be a node in a radio access network (RAN), such as a wireless relay device and / or a wireless backhaul device (not shown in Figure 2). Network device 210 may also be referred to as an access network device or a RAN node (or device), forming part of a communication system to help terminals achieve wireless access. Network device 210 can also be a 3rd generation partnership project (3GPP) related cellular system, such as a 4th generation (4G) mobile communication system, a 5th generation (5G) mobile communication system, an NTN (non-terrestrial network) system, or a future-oriented evolution system (such as a 6th generation (6G) mobile communication system). Network device 210 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WIFI) system, or a communication system integrating two or more of the above systems.

[0092] In the communication system 2000, multiple network devices 210 can be nodes of the same type or different types. In some scenarios, the roles of network devices 210 and terminals 220 are relative. For example, in Figure 2, network element 220i can be a helicopter or drone, which can be configured as a mobile base station. For terminals 220j accessing the RAN 200 through network element 220i, network element 220i is a base station; however, for base station 210a, network element 220i is a terminal. Network devices 210 and terminals 220 are sometimes referred to as communication devices. For example, in Figure 2, network elements 210a and 210b can be understood as communication devices with base station functions, and network elements 220a-220j can be understood as communication devices with terminal functions. Terminal 220 connects to network device 210 wirelessly. Network device 210 connects to the core network wirelessly or via a wired connection. The core network equipment and network equipment 210 in the core network can be different physical devices, or they can be the same physical device that integrates core network logical functions and wireless access network logical functions.

[0093] In one possible scenario, network equipment can be a base station, an evolved NodeB (eNodeB), a transmitting and receiving point (TRP), a transmitting point (TP), a next-generation NodeB (gNB), a base station in a future mobile communication system, a satellite, or an access point (AP) in a Wi-Fi system, an integrated access and backhaul (IAB) node, or a network device in a mobile switching center non-terrestrial network (NTN) communication system, i.e., it can be deployed on a high-altitude platform or satellite, etc. Network equipment can be a macro base station (as shown in Figure 2, 210a), a micro base station or indoor station (as shown in Figure 2, 210b), a relay node or donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Network equipment can also function as a base station in device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, drone communication, and machine-to-machine (M2M) communication. Alternatively, network equipment can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU).

[0094] In another possible scenario, multiple network devices collaborate to assist terminals in achieving wireless access, with each device performing a portion of the base station's functions. For example, these network devices could be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be configured separately or included in the same network element, such as the baseband unit (BBU). The CU and DU nodes separate the gNB's protocol layers; some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed across the DU, which is centrally controlled by the CU. As one implementation, the CU deploys the Radio Resource Control (RRC) layer, PDCP layer, and Service Data Adaptation Protocol (SDAP) layer in the protocol stack; the DU deploys the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical Layer (PHY) in the protocol stack. Thus, the CU has the processing capabilities of RRC, PDCP, and SDAP. The DU has the processing capabilities of RLC, MAC, and PHY. It is understood that the above functional division is merely an example and does not constitute a limitation on the CU and DU. The RU can be included in radio equipment or radio units, such as in a remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH). It is understood that the network device can be a CU node, a DU node, or a device including both CU and DU nodes. Furthermore, the CU can be classified as a network device in the access network RAN ​​or as a network device in the core network CN; there is no restriction on this.

[0095] In this application, the core network equipment refers to equipment in the core network (CN) that provides service support to the terminal. Examples of core network equipment include: access and mobility management function (AMF) entities, session management function (SMF) entities, user plane function (UPF) entities, etc., which are not listed here. The AMF entity is responsible for terminal access management and mobility management; the SMF entity is responsible for session management, such as user session establishment; and the UPF entity can be a user plane functional entity, primarily responsible for connecting to external networks. It should be noted that in this application, entities can also be referred to as network elements or functional entities. For example, an AMF entity can also be called an AMF network element or an AMF functional entity, and an SMF entity can also be called an SMF network element or an SMF functional entity, etc.

[0096] Optionally, the method provided in this application embodiment can also be applied to an O-RAN system. Please refer to Figure 3, which is a schematic diagram of an O-RAN system provided in this application embodiment. The O-RAN system may also include other components besides those shown in Figure 3, and this application does not limit this. Optionally, the network device shown in Figure 3 can be an access network device, such as an eNB, gNB, or next-generation access network device. The access network device communicates with the core network (CN) via a backhaul link and with the terminal via an air interface.

[0097] The BBU in the access network equipment communicates with the core network via a backhaul link, and the RU in the access network equipment communicates with at least one terminal via an air interface. The BBU communicates with at least one RU via a fronthaul link. The BBU and RU may or may not be co-located. The BBU includes at least one control unit (CU) and at least one distributed unit (DU), which can communicate via at least one midhaul link.

[0098] Further optionally, please refer to Figure 4, which is a diagram illustrating the network element functional division and protocol layer structure of an open radio access network (O-RAN) system provided in an embodiment of this application. As shown in Figure 4, in some examples, the CU is a logical node carrying the RRC layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU is connected to network nodes such as the core network through some interfaces, which may be interfaces such as E2 interfaces. Optionally, the CU may have some functions of the core network, such as the PDCP layer and higher layers. The CU is connected to the DU (e.g., RLC layer and lower layers) through some interfaces, which may be interfaces such as F1 interfaces. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). F1AP is the application protocol of the F1 interface, and in some examples, the signaling procedures of F1 are defined. The F1 interface supports the control plane F1-C and the user plane F1-U.

[0099] In some examples, the CU can be split into CU-CP (control unit-control plane) and CU-UP (control unit-user plane). CU-CP is a logical node carrying the RRC layer and PDCP-C (control plane part of PDCP) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function (AMF) network elements, such as the access and mobility management function (AMF) in a 5G mobile communication system. AMF network elements are responsible for mobility management in the mobile network, such as terminal location updates, terminal registration with the network, and terminal handover. CU-UP is a logical node carrying the SDAP layer and the PDCP-U (user plane part of PDCP) layer for user plane data, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. These network elements in the core network, such as the UPF (user plane function) in a 5G system, are responsible for data forwarding and receiving in the terminal. It should be understood that the above configurations of CU and DU are merely examples, and the functions of CU and DU can be configured as needed. This application does not impose excessive limitations on this. For example, CU or DU can be configured to have more protocol layer functions, or CU or DU can be configured to have some protocol layer processing functions. Another example is to place some functions of the RLC layer and the protocol layer functions above the RLC layer in the CU, and place the remaining functions of the RLC layer and the protocol layer functions below the RLC layer in the DU. Yet another example is that the functions of CU or DU can be divided according to service type or other system requirements, such as by latency, placing functions that need to meet low latency requirements in the DU, and functions that do not need to meet this latency requirement in the CU.

[0100] In some examples, a DU is a logical node that carries the radio link control (RLC) layer, medium access control (MAC) layer, higher physical layer (PHY) layer, and other functions. In some examples, a DU can control at least one RU. The DU connects to the RU through interfaces, which can be fronthaul interfaces.

[0101] In some examples, the CU may not have a PDCP layer, i.e., it only includes the RRC layer. CU-CP does not have PDCP-C. CU-UP may not have PDCP-U, or may not have CU-UP at all. In some examples, the DU may not have an RLC layer, only a MAC and a higher PHY layer. Furthermore, in some examples, it may not have a CU and may only include the DU.

[0102] In some examples, the higher PHY layer includes parts of the PHY layer that handle processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0103] In some examples, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency chain (RF chain) processing. In some examples, the RU can be a 3GPPTRP, a remote radio head (RRH), or other similar functionalities. In some examples, the Low-PHY includes PHY processing functions such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more terminals via a wireless link.

[0104] Optionally, the DU and RU may or may not be co-located. The DU and RU exchange control plane information via a fronthaul link through a lower-layer split-control, user plane information (LLS-CUS) and synchronization interface. The LLS-CUS may include LLS-C and LLS-U interfaces that respectively provide the control plane (C-Plane) and user plane (U-Plane). In some examples, the control plane (C-Plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0105] Optionally, the 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 the DU and RU can be configured in various ways depending on the design. For example, the DU can be configured to implement baseband functions, and the RU can be configured to implement mid-RF functions. Alternatively, the DU can be configured to implement higher-level functions in the PHY layer, and the 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 may include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer may include another portion of the physical layer's functions that are closer to the mid-RF side.

[0106] 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. The network device deployment methods listed here are only examples; as standard technologies evolve, network devices may have other deployment forms.

[0107] Currently, a single terminal can simultaneously support both 3GPP and non-3GPP functions. 3GPP functions include Long Term Evolution (LTE) and New Radio (NR), while non-3GPP functions include Global Navigation Satellite System (GNSS), Wireless Local Area Network (WLAN), and Bluetooth. However, when multiple functions operate simultaneously within a terminal, IDC (Independent Data Conversion) issues may arise due to ACI (Automatic Communication Interface) and IMD (Independent Data Distributed) problems. These IDC issues can then lead to interference in multiple subframes or time slots in the time domain. Please refer to Figure 5, which is a schematic diagram illustrating an IDC problem according to an embodiment of this application. As shown in Figure 5, the transmission signal from the NR radio module interferes with the reception of GNSS information, and the transmission from the WIFI radio module may in turn interfere with the signal reception of the NR receiver.

[0108] Under cellular network deployment, terrestrial 5G technology cannot achieve network coverage in remote areas. Therefore, 3GPP introduced NTN technology to expand 5G coverage scenarios. NTN includes satellite communication networks, high-altitude platform systems, and air-to-ground networks. By enhancing the 5G air interface protocol to adapt to satellite scenarios, it is an important direction for the evolution of integrated space-ground communication, with broad application prospects and is currently a research hotspot. Please refer to Figure 6, which is a schematic diagram of satellite communication in NTN provided by an embodiment of this application. As shown in Figure 6, the terminal is connected to the ground station via satellite, and data is transmitted between the ground station and the data center.

[0109] GNSS refers to all satellite navigation systems, which are widely used in many fields, including but not limited to transportation, military, resources and environment, disaster prevention and mitigation, power and telecommunications, urban management, and location services.

[0110] Currently, terminals support simultaneous operation of GNSS and NR-NTN. GNSS provides accurate location coordinates and time information for the terminal to perform NTN services. However, when the operating frequency bands of GNSS and NR-NTN are close, it may cause IDC (Internet Data Center) problems and interference, especially for n254 and n255. Please refer to Figure 7, which is a schematic diagram of NR-NTN UL power leakage interfering with GNSS reception according to an embodiment of this application. As shown in Figure 7, taking n254 as an example, if the GNSS receiver operates in a high-frequency band (1575.42MHz), the operating frequency band of NTN UL is 1610~1626.5MHz. The power leakage of NTN UL will interfere with GNSS reception.

[0111] If the NTN UL service interferes with the reception of the GNSS system during the execution of NR NTN communication services, it may affect the demodulation of GNSS information and prevent the terminal from obtaining accurate positioning information. This is especially true for NTN services, which have a much longer propagation time than terrestrial communication, and when the terminal is in motion, the inaccurate positioning information used will cause the NTN service to fail to function properly.

[0112] In some solutions, when a terminal detects an IDC (Internet Data Center) problem, it can report relevant information about the IDC problem to the network device, such as the time of the IDC interference, the affected system, and the type of interference, in order to resolve the IDC problem. Specifically, please refer to Figure 8, which is a schematic diagram of UE assistance information reporting provided in an embodiment of this application. As shown in Figure 8, during the RRC (Redirect Reconfiguration Control) reconfiguration process, the network device sends an RRC reconfiguration message to the terminal, and the terminal sends assistance information to the network device, wherein the assistance information carries the reported IDC information.

[0113] When network devices receive information about IDC problems reported by terminals, frequency division multiplexing (FDM) or TDM can be used to resolve IDC interference.

[0114] For example, please refer to Figure 9, which is a schematic diagram of an FDM scheme provided in an embodiment of this application. As shown in Figure 9, the FDM method includes: the network device configuring a candidate service frequency list for the terminal. When the terminal detects an IDC problem, it reports the affected frequency range in the auxiliary information sent by the terminal, including the center frequency and the affected bandwidth around the center frequency. Finally, the network device switches the terminal to an unaffected candidate service carrier frequency to resolve the IDC interference.

[0115] Please refer to Figure 10, which is a schematic diagram of a DRX mechanism provided in an embodiment of this application. As shown in Figure 10, the terminal stops non-3GPP transmission during the 3GPP scheduled period (the active period shown in Figure 10) and performs non-3GPP transmission during the non-3GPP unscheduled period (the sleep period shown in Figure 10). This is actually a DRX mechanism, and one DRX cycle is equal to the sum of the active period and the sleep period. Please refer to Figure 11, which is a schematic diagram of a TDM scheme provided in an embodiment of this application. As shown in Figure 11, if an IDC problem occurs, the terminal can send a suggested TDM mode to the network device during the RRC reconfiguration process. The network device configures a suitable DRX cycle for the terminal based on the terminal's suggested TDM mode and the resource scheduling situation.

[0116] Generally speaking, network devices will enable TDM on the basis of FDM according to the terminal capabilities. Combining the two solutions can better solve the IDC problem and make reasonable resource scheduling.

[0117] Regarding the IDC (Internet Data Center) issue between NTN and GNSS, in the TDM (Telecommunications Management) scheme, the terminal performs NTN services during the active period (on duration), using the location coordinates and time information provided by GNSS. During the dormant period, NTN services are stopped, and GNSS information is received and processed to update the GNSS information for the next active period of NTN services. The speed of terminal location changes will affect the validity period of GNSS information. That is, if the terminal remains stationary and its location remains unchanged for a long time, the GNSS information is valid for a long time; however, if the terminal moves at high speed and its location changes rapidly, the validity period of each received GNSS information is very short. Therefore, the DRX cycle may be dynamic and change with the GNSS validity period. Please refer to Figure 12, which is a schematic diagram of the dynamic change of the DRX cycle provided by an embodiment of this application. As shown in Figure 12, the following situations may exist:

[0118] (1) For terminals in a stationary or uniformly moving state, the GNSS positioning results are always valid and the DRX cycle remains unchanged.

[0119] (2) For terminals in slow-moving states, the GNSS validity period changes slowly and can continue for a period of time before updating the DRX cycle.

[0120] (3) For terminals in a fast-moving state, the validity period of GNSS changes frequently, and the DRX cycle needs to be updated in a timely manner.

[0121] Therefore, in order to configure the network with the appropriate TDM mode, the terminal needs to adaptively report the suggested TDM mode to the network device based on its own mobility speed, supported GNSS functions, the period of interference, and ongoing NTN services. When the terminal's operating status changes, the TDM mode needs to be updated accordingly. Each update of the TDM mode requires re-reporting auxiliary information and reconfiguring via RRC before the network device will issue the newly configured DRX cycle.

[0122] The IDC information reporting process in this solution is not flexible enough and does not consider scenarios where the terminal's mobility status changes dynamically. For example, consider a large number of terminals dynamically moving within cell A. Assuming there are 2000 terminals in the cell and their movement speed changes rapidly, and the GNSS validity period is 5 minutes, each terminal needs an RRC reset every 5 minutes to update its GNSS information. For network equipment, updating the DRX mode requires an RRC reconfiguration every 150ms, consuming significant network resources. Furthermore, in the existing DRX mechanism, if data transmission is not completed within the activation period, the activation period is extended. However, the GNSS may have expired during the extended period, causing location-sensitive NTN services to malfunction.

[0123] The existing DRX mechanism distinguishes between the activation and dormancy periods by whether or not the physical downlink control channel (PDCCH) is monitored. Specifically, during the activation period, the terminal turns on the receiver and continuously monitors the downlink PDCCH channel; during the dormancy period, the terminal turns off the receiver and does not monitor the PDCCH channel. Furthermore, both uplink and downlink scheduling of the terminal depend on the PDCCH channel. Please refer to Figure 13, which is a schematic diagram of an uplink / downlink scheduling process provided in an embodiment of this application. As shown in Figure 13(a), the uplink scheduling process includes: when uplink data needs to be transmitted, the terminal sends a scheduling request (SR) to the network device on the PUCCH or PRACH channel to request uplink authorization. After receiving the SR, the network device responds to the SR and sends downlink control information (DCI) to the terminal via the PDCCH.

[0124] As shown in Figure 13(b), the downlink scheduling process includes: the network device allocates downlink time-frequency resources to the terminal based on the channel status reported by the terminal and information such as terminal capabilities, and sends scheduling information (DCI) to the terminal via PDCCH. The network device transmits data on the PDSCH resources allocated to the terminal, and the terminal demodulates the data based on the scheduling information received from the PDCCH channel. Since not monitoring the PDCCH channel will cause uplink and downlink scheduling anomalies for the terminal, NTN uplink and downlink services are usually suspended during the DRX sleep period.

[0125] In the existing DRX mechanism, only uplink power leakage interferes with GNSS reception; downlink reception remains unaffected. However, the existing DRX mechanism halts both uplink and downlink services in the NTN during the dormant period, meaning unaffected downlink services cannot proceed, resulting in low NTN scheduling efficiency.

[0126] In view of this, this application provides a communication method and related apparatus. Taking a first communication device as the terminal and a second communication device as a network device as an example, when the terminal's movement speed is dynamically changing, the TDM mode needs to be updated frequently. In current solutions, each TDM mode update typically requires re-reporting auxiliary information to the network device, which then reconfigures the network device via RRC before sending the newly configured DRX cycle to the terminal. This approach not only wastes network device resources but is also inflexible. This application addresses scenarios where the terminal's movement speed is dynamically changing by having the terminal carry multiple TDM modes when reporting auxiliary information. This allows the network device to configure an appropriate TDM mode for the terminal based on the terminal's suggested TDM mode, regardless of the terminal's movement state. This solution not only reduces the resource configuration burden on network devices but also enhances the flexibility of the IDC information reporting process.

[0127] In the communication method described below (as shown in Figure 14), the specific descriptions of the first and second communication devices can be found in Figures 1 to 4, and will not be detailed here. For ease of description, specific examples in the embodiments of this application may be illustrated using terminals and network devices, but this should not be construed as a limitation on the embodiments of this application.

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

[0129] Please refer to Figure 14, which is a flowchart illustrating a communication method provided in an embodiment of this application. This flowchart describes the interaction between a first communication device and a second communication device as executing entities. The first communication device can be a terminal as an independent device, a communication module within a terminal, or a circuit or chip within a terminal responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip). The second communication device can be a network device as a device, or a component within an independent device, such as a processor, chip, or chip system of a network device, or a logic module or software capable of implementing all or part of the functions of a network device. Optionally, this method can be applied to a communication system, such as the communication systems shown in Figures 1 to 4.

[0130] The method shown in Figure 14 may include multiple steps in steps S1401-S1404. It should be understood that this application describes the steps in the order of S1401-S1404 for ease of description, and is not intended to limit the execution to this specific order. This application's embodiments do not limit the order of execution, the execution time, or the number of executions of one or more of the above steps. Steps S1401-S1404 are as follows:

[0131] Step S1401: The first communication device sends information about coexisting IDC resources within the device to the second communication device.

[0132] Accordingly, the second communication device receives the IDC resource information.

[0133] Optionally, when the first communication device encounters an IDC problem, it can report relevant information about the IDC problem (such as the time of the IDC interference, the system affected by the interference, the type of interference, etc.) and IDC resource information through UE assistance information.

[0134] The IDC resource information carries multiple Time Division Multiplexing (TDM) modes, which correspond to various mobile states of the first communication device.

[0135] For example, please refer to Figure 15. Figure 15 is a schematic diagram of multiple TDM modes corresponding to various movement states of a first communication device according to an embodiment of this application. As shown in Figure 15, the multiple TDM modes include TDM mode A, TDM mode B, and TDM mode C. TDM mode A corresponds to a first speed for the movement state of the first communication device (e.g., moving quickly at a speed of 3 m / ms or moving at a constant speed of 3 m / ms), TDM mode B corresponds to a second speed for the movement state of the first communication device (e.g., moving slowly at a speed of 1 m / ms), and TDM mode C corresponds to a stationary movement state for the first communication device (e.g., stopping moving at a speed of 0 m / ms). For TDM mode A, since the movement speed of the first communication device is changing rapidly, the GNSS validity period changes frequently (e.g., a GNSS validity period is 10 seconds). Therefore, the TDM mode needs to be frequently updated to adapt to subsequent services. The time of one DRX cycle can be configured to 4 ms. For TDM mode B, since the speed of the first communication device changes slowly and the GNSS validity period changes slowly (e.g., a GNSS validity period of 60 seconds), the TDM mode does not need to be updated too frequently and can continue updating for a period of time. The duration of one DRX cycle can be configured to 6ms. For TDM mode C, since the speed of the first communication device is stationary and the GNSS positioning result is always valid (e.g., a GNSS validity period of infinity), the TDM mode does not need to be updated. Therefore, one DRX cycle can be configured to 2560ms.

[0136] Step S1402: The first communication device sends first reference information to the second communication device.

[0137] Accordingly, the second communication device receives the first reference information.

[0138] The first reference information is used to indicate the configuration of the first TDM mode, which is one of multiple TDM modes.

[0139] Optionally, in the process of the terminal reporting IDC information in this application embodiment, the identifier corresponding to the TDM mode can also be reported.

[0140] As one possible implementation, the IDC resource information also carries identifiers corresponding to multiple TDM modes respectively. The first reference information carries the identifier corresponding to the first TDM mode. The first reference information is specifically used to indicate the configuration of the identifier corresponding to the first TDM mode. The first indication information is specifically used to indicate communication according to the first TDM mode through the identifier corresponding to the first TDM mode.

[0141] For example, please refer to Figure 16. Figure 16 is a schematic diagram of multiple TDM modes corresponding to identifiers provided in an embodiment of this application. As shown in Figure 16, taking 2 bytes as an example, assuming that the IDC information includes 16 bits, corresponding to 2 bytes, the following are two exemplary cases of indicating the identifiers corresponding to multiple TDM modes through an index of P bits:

[0142] In the first scenario, for example, if P = 2, multiple TDM modes can be identified using two bits. For instance, as shown in Figure 16(a), if P bits are all 00, TDM mode A can be indicated by the identifier 00. Similarly, if P bits are all 01, TDM mode B can be indicated by the identifier 01. And if P bits are all 10, TDM mode C can be indicated by the identifier 10.

[0143] Optionally, different speed levels in the first speed can be mapped to different TDM modes in TDM mode A, with different identifiers for each speed level. For example, if the first speed ranges from 1 m / ms to 1.6 m / ms, it can be divided into four speed levels: 1 m / ms, 1.2 m / ms, 1.4 m / ms, and 1.6 m / ms. Correspondingly, TDM mode A also has four TDM modes: TDM mode A1, TDM mode A2, TDM mode A3, and TDM mode A4, which can be mapped to these four TDM modes using identifiers 001, 002, 003, and 004, respectively.

[0144] Scenario 2: For example, if P = 4, multiple TDM modes can be identified using 4 bits. For instance, as shown in Figure 16(b), if the value of P bits is 0000, TDM mode A can be indicated by the identifier 0000. Similarly, if the value of P bits is 0100, TDM mode B can be indicated by the identifier 0100. And if the value of P bits is 1000, TDM mode C can be indicated by the identifier 1000.

[0145] It should be understood that the above are merely two exemplary possible scenarios shown for ease of description and are not intended to limit the specific numerical values ​​of the identifiers in the embodiments of this application.

[0146] This solution enables subsequent network devices to configure an adapted TDM mode for a terminal when the terminal is in different mobile states, based on the terminal's suggested TDM mode. Instead of indicating the complete TDM mode, it only needs to indicate the corresponding identifier of the TDM mode, thereby effectively saving network device resources and reducing the latency of the IDC reporting process.

[0147] Step S1403: The second communication device sends the first instruction information to the first communication device.

[0148] Accordingly, the first communication device receives the first instruction information.

[0149] The first indication information is used to indicate communication according to the first TDM mode.

[0150] Optionally, after the first communication device sends a suggested TDM mode to the second communication device, the second communication device can directly instruct the first communication device to communicate according to the TDM mode suggested by the first communication device by sending a first instruction message to the first communication device. For example, if the TDM mode suggested by the first communication device is TDM mode A, the second communication device instructs the first communication device to communicate according to TDM mode A by sending the first instruction message.

[0151] Optionally, after the first communication device sends a suggested TDM mode to the second communication device, the second communication device can first evaluate the TDM mode based on the suggested TDM mode and resource scheduling information, and then determine one TDM mode from multiple TDM modes. For example, the TDM mode suggested by the first communication device is TDM mode A, and the TDM mode finally determined by the second communication device is TDM mode B. The second communication device instructs the first communication device to communicate according to TDM mode B through the first indication information.

[0152] Currently, each time the first communication device updates the TDM mode, it needs to re-report auxiliary information to the second communication device. Then, after the second communication device reconfigures via RRC, it will send the newly configured DRX cycle to the first communication device, resulting in excessive delay in the IDC reporting process. Therefore, this application can process information through MAC-CE, which can effectively reduce the delay in the IDC reporting process and save network equipment resources.

[0153] In one possible implementation, the second communication device sends a first instruction message to the first communication device via a Media Access Control-Control Element (MAC-CE).

[0154] Optionally, the first indication information is carried by the MAC-CE of the second communication device.

[0155] Accordingly, the first communication device receives the first indication information carried by the MAC-CE from the second communication device.

[0156] Optionally, the first indication information sent by the second communication device to the first communication device is first transmitted to the first communication device by the RRC layer of the second communication device, and then processed by the MAC-CE of the second communication device.

[0157] In existing solutions, NTN only interferes with GNSS reception due to uplink power leakage, while downlink remains unaffected. However, the existing DRX mechanism suspends both uplink and downlink services of NTN during the dormant period, meaning that even unaffected downlink services cannot function properly, resulting in low NTN scheduling efficiency. To address this scenario, two possible implementation methods for adjusting the downlink scheduling of the first communication device are described below:

[0158] In the first implementation method, an instruction message is sent by another device to instruct the first communication device to schedule downlink data.

[0159] Optionally, the second communication device may send a second instruction message to the first communication device.

[0160] Accordingly, the first communication device receives the second instruction information before communicating according to the first TDM mode.

[0161] For example, please refer to Figure 17, which is a schematic diagram of a DRX cycle configuration method provided in an embodiment of this application. As shown in Figure 17, the second indication information is used to instruct the first communication device to monitor the PDCCH during the inactive period of the DRX cycle. The PDCCH is only used to schedule downlink data.

[0162] Optionally, the second indication information is used to instruct the first communication device to monitor the PDCCH during the inactive period (e.g., the dormant period) of the DRX cycle to perform 3GPP services, such as NTN downlink services.

[0163] In the second implementation method, the first communication device is configured via protocol to only stop scheduling uplink data during the inactive period (e.g., the sleep period) of the DRX cycle. Specifically, referring to Figure 17, the first communication device is configured to monitor the PDCCH during the inactive period of the DRX cycle, and the PDCCH is used only for scheduling downlink data.

[0164] Optionally, since the PDCCH carries hybrid automatic repeat request (HARQ) information to acknowledge or request retransmission of data packets, and NTN supports disabling the HARQ feedback function, the HARQ feedback function can be disabled during the inactive period to ensure that downlink services can proceed normally during the inactive period of the DRX cycle.

[0165] Based on the existing DRX mechanism, this scheme performs uplink and downlink scheduling normally during the active period of the DRX cycle, and stops scheduling uplink data during the dormant period of the DRX cycle, while monitoring the PDCCH channel normally to enable the first communication device to schedule downlink data normally, thereby effectively improving the scheduling efficiency of NTN.

[0166] Step S1404: The first communication device communicates according to the first TDM mode.

[0167] For example, the first communication device can communicate according to a first TDM mode, which allows it to handle NTN services during the active and inactive (e.g., sleep) periods of the DRX cycle according to the first TDM mode. For instance, during the active period, the first communication device performs NTN services using location coordinates and time information provided by GNSS. During the sleep period, it stops NTN services, receives and processes GNSS information, and updates the GNSS information for NTN services in the next active period.

[0168] In one possible implementation, the first communication device sends second reference information to the second communication device when the first condition is met, receives third instruction information from the second communication device, and communicates according to the second TDM mode.

[0169] Optionally, the first condition may be a change in the movement state of the first communication device.

[0170] For example, the first condition includes, but is not limited to, any one of the following:

[0171] (1) The movement state of the first communication device is switched from a first speed to a second speed. Optionally, the first speed is greater than the second speed. For example, the first speed is a fast movement at 3 m / ms or a constant movement at 3 m / ms, and the second speed is a slow movement at 1 m / ms, and the movement state of the first communication device is switched from 3 m / ms to 1 m / ms.

[0172] (2) The movement state of the first communication device is switched from the second speed to a stationary state. Optionally, the second speed is greater than the stationary speed. For example, the second speed is either a rapid movement at 1 m / ms or a constant movement at 1 m / ms, and the stationary speed is 0 m / ms. The movement state of the first communication device is switched from 1 m / ms to 0 m / ms.

[0173] (3) The movement state of the first communication device is switched from the first speed to a stationary state. Optionally, the first speed is greater than the stationary speed. For example, the first speed is either moving rapidly at a speed of 3 m / ms or moving at a constant speed of 3 m / ms, and the stationary speed is 0 m / ms. The movement state of the first communication device is switched from 3 m / ms to 0 m / ms.

[0174] It should be understood that the above are only three exemplary possible situations shown for ease of description, and are not intended to limit the specific numerical value of the movement state of the first communication device in the embodiments of this application.

[0175] The second reference information is used to indicate the configuration of the second TDM mode, which is one of the multiple TDM modes other than the first TDM mode. The third indication information is used to indicate communication according to the second TDM mode.

[0176] Optionally, the first communication device can directly send a suggested TDM mode to the second communication device, and the second communication device can directly instruct the first communication device to communicate according to the suggested TDM mode. For example, if the suggested TDM mode by the first communication device is TDM mode A, the second communication device can instruct the first communication device to communicate according to TDM mode A through a third instruction message.

[0177] Optionally, the first communication device can directly send a suggested TDM mode to the second communication device. The second communication device evaluates the suggested TDM mode and resource scheduling information based on the suggested TDM mode and determines one TDM mode from multiple TDM modes. For example, the suggested TDM mode is TDM mode A, and the final TDM mode determined by the second communication device is TDM mode B. The second communication device instructs the first communication device to communicate according to TDM mode B through third indication information.

[0178] Optionally, the first communication device receives third indication information from the second communication device, which may be third indication information from the MAC-CE of the second communication device.

[0179] In this scheme, when a first condition is met (e.g., the mobility state of the first communication device changes dynamically), the first communication device needs to request an update to the TDM mode from the second communication device. For example, the first communication device can report a suggested TDM mode, which is then used by the second communication device to configure an adapted TDM mode for the terminal. Since the second communication device has already acquired multiple TDM modes reported by the first communication device, even if the mobility state of the first communication device changes dynamically, the allocation of TDM modes can be flexibly implemented, effectively saving network device resources and reducing the latency of the IDC reporting process.

[0180] In this application, taking the first communication device as the terminal and the second communication device as the network device as an example, when the terminal's movement speed is dynamically changing, the TDM mode needs to be updated frequently. In current solutions, each TDM mode update typically requires re-reporting auxiliary information to the network device, which then reconfigures the network device via RRC before sending the newly configured DRX cycle to the terminal. This approach is not only wasteful of network device resources but also inflexible. This application addresses scenarios where the terminal's movement speed is dynamically changing by having the terminal carry multiple TDM modes when reporting auxiliary information. This allows the network device to configure an appropriate TDM mode for the terminal based on the terminal's suggested TDM mode, regardless of the terminal's movement state. This solution effectively enhances the flexibility of the IDC information reporting process.

[0181] The embodiment shown in Figure 14 provides a detailed explanation of the main interaction principle between the first communication device and the second communication device. For ease of understanding, specific examples of three transmission TDM modes are given below with reference to Figures 18a-18c.

[0182] Please refer to Figure 18a. Figure 18a is a schematic flowchart of a TDM transmission mode provided in an embodiment of this application. It should be understood that, for ease of description, this application describes the process in the order of steps 11-17, and does not intend to limit the execution to the above order. This application embodiment does not limit the order of execution, execution time, or number of executions of one or more of the above steps. As shown in Figure 18a, the specific steps of Case 1 are as follows:

[0183] Step 11: The second communication device sends an RRC reconfiguration message to the first communication device.

[0184] Accordingly, the first communication device receives the RRC reconfiguration message.

[0185] The RRC reconfiguration message is used to modify the RRC connection, including establishing SRB and DRB bearers, and configuring measurement, radio resources, and security information. The second communication device sends RRC reconfiguration signaling, containing information such as measurement configuration, reporting configuration, and dedicated radio resource configuration. Upon receiving this, the first communication device performs the corresponding configuration and responds with a reconfiguration success message. This process is primarily used to adjust the mobility and quality of service of the first communication device in the network.

[0186] Step 12: The first communication device sends information about coexisting IDC resources within the device to the second communication device.

[0187] Accordingly, the second communication device receives the IDC resource information.

[0188] The IDC resource information carries multiple Time Division Multiplexing (TDM) modes, which correspond to various mobile states of the first communication device.

[0189] Step 13: The second communication device transmits the received IDC resource information to the MAC CE layer via the RRC processing layer.

[0190] Step 14: The first communication device sends the first reference information to the second communication device.

[0191] Accordingly, the second communication device receives the first reference information.

[0192] The first reference information is used to indicate the configuration of the first TDM mode, which is one of multiple TDM modes.

[0193] Step 15: The second communication device sends the identifier corresponding to the TDM mode to the first communication device.

[0194] The identifier corresponding to the TDM mode sent by the second communication device to the first communication device is carried through the MAC-CE layer.

[0195] The TDM mode sent to the first communication device is obtained based on the first TDM mode, and the identifier corresponding to the TDM mode is used to indicate communication according to the configured TDM mode.

[0196] For example, if the MAC-CE layer of the second communication device directly configures the TDM mode of the first communication device as the first TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the first TDM mode; if the MAC-CE layer of the second communication device configures the TDM mode of the first communication device as another suitable TDM mode according to the first TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the other TDM mode.

[0197] Step 16: When the movement state of the first communication device changes, the first communication device sends the identifier corresponding to the second TDM mode to the second communication device.

[0198] Accordingly, the second communication device receives the identifier corresponding to the second TDM mode.

[0199] Step 17: The second communication device sends the identifier corresponding to the TDM mode to the first communication device.

[0200] The identifier corresponding to the TDM mode sent by the second communication device to the first communication device is carried through the MAC-CE layer.

[0201] The TDM mode sent to the first communication device is obtained based on the second TDM mode, and the identifier corresponding to the TDM mode is used to indicate communication according to the configured TDM mode.

[0202] For example, if the MAC-CE layer of the second communication device directly configures the TDM mode of the first communication device as the second TDM mode according to the second TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the second TDM mode; if the MAC-CE layer of the second communication device configures the TDM mode of the first communication device as another suitable TDM mode according to the second TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the other TDM mode.

[0203] It should be noted that in this scheme, the first communication device is not allowed to send uplink scheduling requests during the inactive period, and the second communication device is not allowed to initiate uplink scheduling.

[0204] In this application, taking the first communication device as the terminal and the second communication device as the network device as an example, on the one hand, when the terminal's movement speed is dynamically changing, the TDM mode needs to be updated frequently. In current solutions, each TDM mode update typically requires re-reporting auxiliary information to the network device, and then the network device reconfigures via RRC before sending the newly configured DRX cycle to the terminal. This solution not only wastes network device resources but is also inflexible. This application addresses the scenario where the terminal's movement speed is dynamically changing by having the terminal carry multiple TDM modes when reporting auxiliary information. This allows the network device to configure an appropriate TDM mode for the terminal based on the terminal's suggested TDM mode, regardless of the terminal's movement state.

[0205] On the other hand, in the existing solution, the terminal needs to re-report auxiliary information to the network device every time it updates the TDM mode. Then, the network device will reconfigure the terminal through RRC before sending the newly configured DRX cycle to the terminal. This results in an excessively long delay in the IDC reporting process. This solution uses MAC-CE for information processing, which can effectively reduce the delay in the IDC reporting process and save network device resources.

[0206] In summary, this solution not only effectively enhances the flexibility of the IDC information reporting process, but also reduces the latency of the IDC reporting process and saves network equipment resources.

[0207] It should be noted that detailed explanations of steps 11-17 above can be found in the embodiment shown in Figure 14, and will not be repeated here.

[0208] Please refer to Figure 18b, which is a flowchart illustrating another TDM transmission mode provided in this application embodiment. It should be understood that, for ease of description, this application describes the process in the order of steps 21-26, and does not intend to limit the execution to this specific order. This application embodiment does not limit the order of execution, execution time, or number of executions of one or more of the above steps. As shown in Figure 18b, the specific steps of Case Two are as follows:

[0209] Step 21: The second communication device sends an RRC reconfiguration message to the first communication device.

[0210] Accordingly, the first communication device receives the RRC reconfiguration message.

[0211] The RRC reconfiguration message is used to modify the RRC connection, including establishing SRB and DRB bearers, and configuring measurement, radio resources, and security information. The second communication device sends RRC reconfiguration signaling, containing information such as measurement configuration, reporting configuration, and dedicated radio resource configuration. Upon receiving this, the first communication device performs the corresponding configuration and responds with a reconfiguration success message. This process is primarily used to adjust the mobility and quality of service of the first communication device in the network.

[0212] Step 22: The first communication device sends information about coexisting IDC resources within the device to the second communication device.

[0213] Accordingly, the second communication device receives the IDC resource information.

[0214] The IDC resource information carries multiple Time Division Multiplexing (TDM) modes, which correspond to various mobile states of the first communication device.

[0215] Step 23: The first communication device sends the first reference information to the second communication device.

[0216] Accordingly, the second communication device receives the first reference information.

[0217] The first reference information is used to indicate the configuration of the first TDM mode, which is one of multiple TDM modes.

[0218] Step 24: The second communication device sends the identifier corresponding to the TDM mode to the first communication device.

[0219] The identifier corresponding to the TDM mode sent by the second communication device to the first communication device is carried through the RRC layer.

[0220] The TDM mode sent to the first communication device is obtained based on the first TDM mode, and the identifier corresponding to the TDM mode is used to indicate communication according to the configured TDM mode.

[0221] For example, if the RRC layer of the second communication device directly configures the TDM mode of the first communication device as the first TDM mode according to the first TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the first TDM mode; if the RRC layer of the second communication device configures the TDM mode of the first communication device as another suitable TDM mode according to the first TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the other TDM mode.

[0222] Step 25: When the movement state of the first communication device changes, the first communication device sends the identifier corresponding to the second TDM mode to the second communication device.

[0223] Accordingly, the second communication device receives the identifier corresponding to the second TDM mode.

[0224] Step 26: The second communication device sends the identifier corresponding to the TDM mode to the first communication device.

[0225] The identifier corresponding to the TDM mode sent by the second communication device to the first communication device is carried through the RRC layer.

[0226] The TDM mode sent to the first communication device is obtained based on the second TDM mode, and the identifier corresponding to the TDM mode is used to indicate communication according to the configured TDM mode.

[0227] For example, if the RRC layer of the second communication device directly configures the TDM mode of the first communication device as the second TDM mode according to the second TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the second TDM mode; if the RRC layer of the second communication device configures the TDM mode of the first communication device as another suitable TDM mode according to the second TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the other TDM mode.

[0228] It should be noted that in this scheme, the first communication device is configured to monitor the PDCCH during the inactive period of the DRX cycle, and the PDCCH is only used for scheduling downlink data.

[0229] In this application, NTN only interferes with GNSS reception due to uplink power leakage, while downlink is unaffected. However, the existing DRX mechanism stops both uplink and downlink services of NTN during the dormant period, meaning that unaffected downlink services cannot operate normally, resulting in low NTN scheduling efficiency. To address this scenario, based on the existing DRX mechanism, the first communication device can stop scheduling uplink data during the inactive period of the DRX cycle (e.g., the dormant period) while maintaining normal monitoring of the PDCCH channel to ensure normal scheduling of downlink data, thereby effectively improving NTN scheduling efficiency.

[0230] It should be noted that detailed explanations of steps 21-26 above can be found in the embodiment shown in Figure 14, and will not be repeated here.

[0231] Please refer to Figure 18c, which is a flowchart illustrating another TDM transmission mode provided in this application embodiment. It should be understood that, for ease of description, this application describes the process in the order of steps 31-37, and does not intend to limit the execution to this specific order. This application embodiment does not limit the order of execution, execution time, or number of executions of one or more of the above steps. As shown in Figure 18c, the specific steps of Case 3 are as follows:

[0232] Step 31: The second communication device sends an RRC reconfiguration message to the first communication device.

[0233] Accordingly, the first communication device receives the RRC reconfiguration message.

[0234] The RRC reconfiguration message is used to modify the RRC connection, including establishing SRB and DRB bearers, and configuring measurement, radio resources, and security information. The second communication device sends RRC reconfiguration signaling, containing information such as measurement configuration, reporting configuration, and dedicated radio resource configuration. Upon receiving this, the first communication device performs the corresponding configuration and responds with a reconfiguration success message. This process is primarily used to adjust the mobility and quality of service of the first communication device in the network.

[0235] Step 32: The first communication device sends information about coexisting IDC resources within the device to the second communication device.

[0236] Accordingly, the second communication device receives the IDC resource information.

[0237] The IDC resource information carries multiple Time Division Multiplexing (TDM) modes, which correspond to various mobile states of the first communication device.

[0238] Step 33: The second communication device transmits the received IDC resource information to the MAC CE layer via the RRC processing layer.

[0239] Step 34: The first communication device sends the first reference information to the second communication device.

[0240] Accordingly, the second communication device receives the first reference information.

[0241] The first reference information is used to indicate the configuration of the first TDM mode, which is one of multiple TDM modes.

[0242] Step 35: The second communication device sends the identifier corresponding to the TDM mode to the first communication device.

[0243] The identifier corresponding to the TDM mode sent by the second communication device to the first communication device is carried through the MAC-CE layer.

[0244] The TDM mode sent to the first communication device is obtained based on the first TDM mode, and the identifier corresponding to the TDM mode is used to indicate communication according to the configured TDM mode.

[0245] For example, if the MAC-CE layer of the second communication device directly configures the TDM mode of the first communication device as the first TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the first TDM mode; if the MAC-CE layer of the second communication device configures the TDM mode of the first communication device as another suitable TDM mode according to the first TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the other TDM mode.

[0246] Step 36: When the movement state of the first communication device changes, the first communication device sends the identifier corresponding to the second TDM mode to the second communication device.

[0247] Accordingly, the second communication device receives the identifier corresponding to the second TDM mode.

[0248] Step 37: The second communication device sends the identifier corresponding to the TDM mode to the first communication device.

[0249] The identifier corresponding to the TDM mode sent by the second communication device to the first communication device is carried through the MAC-CE layer.

[0250] The TDM mode sent to the first communication device is obtained based on the second TDM mode, and the identifier corresponding to the TDM mode is used to indicate communication according to the configured TDM mode.

[0251] For example, if the MAC-CE layer of the second communication device directly configures the TDM mode of the first communication device as the second TDM mode according to the second TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the second TDM mode; if the MAC-CE layer of the second communication device configures the TDM mode of the first communication device as another suitable TDM mode according to the second TDM mode, then the identifier sent to the first communication device is the identifier corresponding to the other TDM mode.

[0252] It should be noted that steps 31-37 are the same as steps 11-17, but in this scheme, the first communication device is configured to monitor the PDCCH during the inactive period of the DRX cycle. The PDCCH is only used for scheduling downlink data. Therefore, Case 3 is a combination of steps 11-17 and the constraint "the first communication device is configured to monitor the PDCCH during the dormant period of the DRX cycle. The PDCCH is only used for scheduling downlink data".

[0253] In this application, taking the first communication device as the terminal and the second communication device as the network device as an example, on the one hand, when the terminal's movement speed is dynamically changing, the TDM mode needs to be updated frequently. In current solutions, each TDM mode update typically requires re-reporting auxiliary information to the network device, and then the network device reconfigures via RRC before sending the newly configured DRX cycle to the terminal. This solution not only wastes network device resources but is also inflexible. This application addresses the scenario where the terminal's movement speed is dynamically changing by having the terminal carry multiple TDM modes when reporting auxiliary information. This allows the network device to configure an appropriate TDM mode for the terminal based on the terminal's suggested TDM mode, regardless of the terminal's movement state.

[0254] On the other hand, in the existing solution, the terminal needs to re-report auxiliary information to the network device every time it updates the TDM mode. Then, the network device will reconfigure the terminal through RRC before sending the newly configured DRX cycle to the terminal. This results in an excessively long delay in the IDC reporting process. This solution uses MAC-CE for information processing, which can effectively reduce the delay in the IDC reporting process and save network device resources.

[0255] On the other hand, while NTN's uplink power leakage does interfere with GNSS reception, downlink remains unaffected. However, the existing DRX mechanism halts both uplink and downlink services during the sleep period, meaning even unaffected downlink services cannot function properly, resulting in low NTN scheduling efficiency. To address this scenario, based on the existing DRX mechanism, during the inactive period of the DRX cycle (e.g., the sleep period), the terminal can stop scheduling uplink data while maintaining normal monitoring of the PDCCH channel to ensure normal downlink data scheduling, thereby effectively improving NTN scheduling efficiency.

[0256] In summary, this solution not only effectively enhances the flexibility of the IDC information reporting process, but also reduces the latency of the IDC reporting process, saves network equipment resources, and improves NTN scheduling efficiency.

[0257] It should be noted that detailed explanations of steps 31-37 above can be found in the embodiment shown in Figure 14, and will not be repeated here.

[0258] The methods of the embodiments of this application have been described in detail above. The apparatus of the embodiments of this application is provided below.

[0259] It should be understood that the division of units in the apparatus provided in this application embodiment is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units in the apparatus can be implemented by a processor calling software. For example, the apparatus includes a processor connected to a memory, which stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of each unit of the apparatus. The processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is either internal or external to the apparatus.

[0260] Alternatively, the units in the device can be implemented as hardware circuits. The functionality of some or all of the units can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the above units is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the above units.

[0261] In the embodiments of this application, each unit in the device may be one or more processors (or processing circuits) configured to implement the above methods, such as: CPU, graphics processing unit (GPU), neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), microprocessor unit (MPU), digital signal processor (DSP), ASIC, FPGA, or a combination of at least two of these processor forms.

[0262] Furthermore, the units in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units are integrated together as a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or for implementing the functions of the units in the device. The at least one processor can be of different types, such as including a CPU and an FPGA, or including a CPU and an AI processor, or including a CPU and a GPU, etc. Several possible devices are listed below.

[0263] Please refer to Figure 19, which is a schematic diagram of the structure of a communication device 190 provided in an embodiment of this application. Optionally, the communication device 190 can be a first communication device or a component within the first communication device, such as a chip or integrated circuit. The communication device 190 is used to implement the aforementioned communication method, such as the communication method shown in Figure 14.

[0264] In one possible design, the communication device 190 includes a communication unit 1901 and a processing unit 1902. The communication device 190 is used to implement the aforementioned communication method, such as the communication method shown in FIG. 14. Exemplarily, the communication device is used, for example, to execute the method executed by the first communication device.

[0265] In one possible implementation, the communication unit 1901 is used to send coexisting IDC resource information within the device to the second communication device, wherein the IDC resource information carries multiple time-division multiplexing (TDM) modes.

[0266] The communication unit 1901 is further configured to send first reference information to the second communication device, wherein the first reference information is configured to indicate the configuration of a first TDM mode, and the first TDM mode belongs to one of the plurality of TDM modes.

[0267] The communication unit 1901 is further configured to receive first indication information from the second communication device, wherein the first indication information is configured to indicate communication according to the first TDM mode;

[0268] The communication unit 1901 is also used for communication according to the first TDM mode;

[0269] The processing unit 1902 is used to process the transmitted and received data.

[0270] In another possible implementation, the IDC resource information also carries the identifiers corresponding to the plurality of TDM modes respectively, the first reference information carries the identifiers corresponding to the first TDM mode, the first reference information is specifically used to indicate the configuration of the identifiers corresponding to the first TDM mode, and the first indication information is specifically used to indicate communication according to the first TDM mode through the identifiers corresponding to the first TDM mode.

[0271] In yet another possible implementation, in relation to receiving the first indication information from the second communication device, the communication unit 1901 is specifically configured to:

[0272] Receive first indication information carried by the Media Access Control-Control Element (MAC-CE) from the second communication device.

[0273] In another possible implementation, in terms of communicating according to the first TDM mode, the communication unit 1901 is specifically used to: monitor the physical downlink control channel PDCCH during the inactive period of a discontinuous reception DRX cycle, wherein the PDCCH is used only for scheduling downlink data.

[0274] In another possible implementation, the communication unit 1901 is further configured to receive second indication information, wherein the second indication information is configured to indicate monitoring of the PDCCH during the inactive period of the DRX cycle.

[0275] In yet another possible implementation, the first communication device is configured to monitor the PDCCH during the inactive period of the DRX cycle.

[0276] In another possible implementation, the communication unit 1901 is further configured to send second reference information to the second communication device when the first condition is met, wherein the second reference information is used to indicate the configuration of a second TDM mode, the second TDM mode being one of the plurality of TDM modes other than the first TDM mode.

[0277] The communication unit 1901 is further configured to receive third indication information from the second communication device, wherein the third indication information is configured to indicate communication according to the second TDM mode;

[0278] The communication unit 1901 is also used to communicate according to the second TDM mode.

[0279] In yet another possible implementation, the first condition includes any one of the following:

[0280] The first communication device switches its movement state from a first speed to a second speed; or,

[0281] The movement state of the first communication device changes from the second speed to a stationary state; or,

[0282] The first communication device switches its movement state from the first speed to a stationary state, wherein the first speed is greater than the second speed.

[0283] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0284] Please refer to Figure 20, which is a schematic diagram of another communication device 200 provided in an embodiment of this application. Optionally, the communication device 200 can be a second communication device, or a component within a second communication device, such as a chip or integrated circuit. The communication device 200 is used to implement the aforementioned communication method, such as the communication method shown in Figure 14.

[0285] In one possible design, the communication device 200 includes a communication unit 2001 and a processing unit 2002. The communication device 200 is used to implement the aforementioned communication method, such as the communication method shown in FIG. 14. Exemplarily, the communication device is used, for example, to execute the method executed by the second communication device.

[0286] In one possible implementation, the communication unit 2001 is used to receive in-device coexisting IDC resource information from the first communication device, wherein the IDC resource information carries multiple time division multiplexing (TDM) modes.

[0287] The communication unit 2001 is further configured to receive first reference information from the first communication device, wherein the first reference information is configured to indicate the configuration of a first TDM mode, and the first TDM mode belongs to one of the plurality of TDM modes.

[0288] The communication unit 2001 is further configured to send first indication information to the first communication device, wherein the first indication information is configured to indicate communication according to the first TDM mode;

[0289] The processing unit 2002 is used to process the transmitted and received data.

[0290] In another possible implementation, the IDC resource information also carries the identifiers corresponding to the plurality of TDM modes respectively, the first reference information carries the identifiers corresponding to the first TDM mode, the first reference information is specifically used to indicate the configuration of the identifiers corresponding to the first TDM mode, and the first indication information is specifically used to indicate communication according to the first TDM mode through the identifiers corresponding to the first TDM mode.

[0291] In yet another possible implementation, in terms of sending the first instruction information to the first communication device, the communication unit 2001 is specifically configured to: send the first instruction information to the first communication device via a Media Access Control-Control Element (MAC-CE).

[0292] In another possible implementation, the communication unit 2001 is further configured to send a second indication message to the first communication device, wherein the second indication message is configured to indicate monitoring of the PDCCH during the inactive period of the discontinuous reception DRX cycle, the PDCCH being used only for scheduling downlink data.

[0293] In another possible implementation, the communication unit 2001 is further configured to receive second reference information, wherein the second reference information is configured to indicate the configuration of a second TDM mode, the second TDM mode being one of the plurality of TDM modes other than the first TDM mode.

[0294] The communication unit 2001 is further configured to send third indication information to the first communication device, wherein the third indication information is used to indicate communication according to the second TDM mode;

[0295] The communication unit 2001 is also used to transmit second data.

[0296] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0297] Please refer to Figure 21, which is a schematic diagram of another communication device 210 provided in an embodiment of this application. The communication device 210 can be a standalone device, such as a first communication device or a second communication device, or it can be a component included in a standalone device, such as a chip, software module, or integrated circuit. The communication device 210 may include at least one processor 2101 and a communication interface 2102. Optionally, it may also include at least one memory 2103. Further optionally, it may also include a connection line 2104, wherein the processor 2101, the communication interface 2102, and / or the memory 2103 are connected through the connection line 2104, and / or communicate with each other through the connection line 2104 to transmit control signals and / or data signals.

[0298] Wherein: processor 2101 is a module that performs arithmetic and / or logical operations, and may specifically include one or more of the following modules: filter, modem, power amplifier, low noise amplifier (LNA), baseband processor, radio frequency processor, radio frequency circuit, CPU, AP, microcontroller unit (MCU), electronic control unit (ECU), GPU, MPU, ASIC, image signal processor (ISP), DSP, FPGA, complex programmable logic device (CPLD), or coprocessor, etc.

[0299] The communication interface 2102 can be used to provide information input or output to at least one processor, or to receive signals sent externally and / or send signals to externally.

[0300] For example, the communication interface 2102 may include interface circuitry, such as input / output interfaces, chip pins, etc.

[0301] For example, the communication interface 2102 may include a wired link interface such as an Ethernet cable, or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission, vehicle short-range communication technology and other short-range wireless communication technologies, etc.).

[0302] Optionally, the communication interface 2102 may also include a radio frequency transmitter, an antenna, etc. When the communication interface 2102 includes an antenna, the number of antennas can be one or more.

[0303] As one possible design, if the communication device 210 is a standalone device, the communication interface 2102 may include a receiver and a transmitter. The receiver and transmitter may be the same component or different components. When the receiver and transmitter are the same component, this component may be referred to as a transceiver.

[0304] As another possible design, if the communication device 210 is a chip or circuit, the communication interface 2102 may include an input interface and an output interface. The input interface and the output interface may be the same interface or they may be different interfaces.

[0305] Alternatively, the functions of the communication interface 2102 can be implemented by a transceiver circuit or a dedicated transceiver chip.

[0306] The memory 2103 provides storage space, in which data such as the operating system and computer programs can be stored. The memory 2103 can be one or a combination of several of the following: cache, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), compact disc read-only memory (CD-ROM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD), solid-state drive (SSD), etc. Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store computer programs or instructions, and / or data.

[0307] The functions and actions of each module or unit in the communication device 210 listed above are merely illustrative examples.

[0308] Each functional unit in the communication device 210 can be used to implement the aforementioned communication method, such as the communication method shown in FIG14, for example, to execute the method executed by the first communication device, or to execute the method executed by the second communication device.

[0309] Optionally, processor 2101 may be a processor specifically designed to execute the aforementioned methods (for ease of distinction, referred to as a dedicated processor), or a processor that executes the aforementioned methods by calling a computer program (for ease of distinction, referred to as a dedicated processor). Optionally, at least one processor may include both dedicated processors and general-purpose processors.

[0310] Optionally, if the communication device 210 includes at least one memory 2103, and the processor 2101 implements the aforementioned communication method by calling a computer program, the computer program can be stored in the memory 2103.

[0311] This application also provides a chip, which includes logic circuitry and a communication interface. The communication interface is used to receive or transmit signals; the logic circuitry is used to receive or transmit signals through the communication interface. The chip is used to implement the aforementioned communication method, such as the communication method shown in FIG14, for example, to execute a method executed by a first communication device, or to execute a method executed by a second communication device.

[0312] This application also provides a computer-readable storage medium storing instructions that, when executed on at least one processor (or communication device), implement the aforementioned communication method, such as the communication method shown in FIG14, for example, a method executed by a first communication device, or a method executed by a second communication device.

[0313] This application also provides a computer program product, which includes computer instructions for implementing the aforementioned communication method, such as the communication method shown in FIG14, for example, for executing a method executed by a first communication device, or for executing a method executed by a second communication device.

[0314] It should be noted that, in the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplarily" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0315] In the embodiments of this application, "at least one" refers to one or more items, and "more than one" refers to two or more items. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items.

[0316] For example, at least one of a, b, or c can be represented as: 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. "AND / OR" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects have an "OR" relationship.

[0317] Furthermore, unless otherwise stated, the use of ordinal numbers such as "first" and "second" in the embodiments of this application is for distinguishing multiple objects and is not for limiting the order, sequence, priority, or importance of multiple objects. Similarly, terms like "first node" and "second node" are merely for convenience in describing new parameters in different implementations and do not indicate differences in their execution operations, importance, structure, etc.

[0318] In the above embodiments, the term "when..." can be interpreted, depending on the context, as meaning "if...", "before...", "determined...", or "detected...". The above descriptions are merely optional embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the concept and principles of this application should be included within the protection scope of this application.

[0319] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

Claims

1. A communication method, characterized in that, Applied to a first communication device, the method includes: Send coexisting IDC resource information within the device to the second communication device, wherein the IDC resource information carries multiple time-division multiplexing (TDM) modes; Send first reference information to the second communication device, wherein the first reference information is used to indicate the configuration of a first TDM mode, and the first TDM mode belongs to one of the plurality of TDM modes; Receive first indication information from the second communication device, wherein the first indication information is used to indicate communication according to the first TDM mode; Communication is performed according to the first TDM mode.

2. The method according to claim 1, characterized in that, The IDC resource information also carries the identifiers corresponding to the multiple TDM modes respectively. The first reference information carries the identifier corresponding to the first TDM mode. The first reference information is specifically used to indicate the configuration of the identifier corresponding to the first TDM mode. The first indication information is specifically used to indicate communication according to the first TDM mode through the identifier corresponding to the first TDM mode.

3. The method according to claim 1 or 2, characterized in that, The receipt of the first indication information from the second communication device includes: Receive first indication information carried by the Media Access Control-Control Element (MAC-CE) from the second communication device.

4. The method according to any one of claims 1-3, characterized in that, The communication according to the first TDM mode includes: During the inactive period of the discontinuous reception DRX cycle, the physical downlink control channel (PDCCH) is monitored, wherein the PDCCH is used only for scheduling downlink data.

5. The method according to any one of claims 1-4, characterized in that, Before communicating according to the first TDM mode, the method further includes: Receive a second indication message, wherein the second indication message is used to indicate that the PDCCH is monitored during the inactive period of the DRX cycle, and the PDCCH is used only for scheduling downlink data.

6. The method according to any one of claims 1-4, characterized in that, The first communication device is configured to monitor the PDCCH during the inactive period of the DRX cycle.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: If the first condition is met, second reference information is sent to the second communication device, wherein the second reference information is used to indicate the configuration of a second TDM mode, and the second TDM mode belongs to one of the plurality of TDM modes other than the first TDM mode; Receive third indication information from the second communication device, wherein the third indication information is used to indicate communication according to the second TDM mode; Communication is performed according to the second TDM mode.

8. The method according to claim 7, characterized in that, The first condition includes any one of the following: The first communication device switches its movement state from a first speed to a second speed; or, The movement state of the first communication device changes from the second speed to a stationary state; or, The first communication device switches its movement state from the first speed to a stationary state, wherein the first speed is greater than the second speed.

9. A communication method, characterized in that, Applied to a second communication device, the method includes: Receive in-device coexisting IDC resource information from the first communication device, wherein the IDC resource information carries multiple time division multiplexing (TDM) modes; Receive first reference information from the first communication device, wherein the first reference information is used to indicate the configuration of a first TDM mode, the first TDM mode belonging to one of the plurality of TDM modes; Send a first instruction message to the first communication device, wherein the first instruction message is used to instruct communication to be performed according to the first TDM mode.

10. The method according to claim 9, characterized in that, The IDC resource information also carries the identifiers corresponding to the multiple TDM modes respectively. The first reference information carries the identifier corresponding to the first TDM mode. The first reference information is specifically used to indicate the configuration of the identifier corresponding to the first TDM mode. The first indication information is specifically used to indicate communication according to the first TDM mode through the identifier corresponding to the first TDM mode.

11. The method according to claim 9 or 10, characterized in that, Sending the first instruction information to the first communication device includes: The first instruction information is sent to the first communication device via the Media Access Control-Control Element (MAC-CE).

12. The method according to any one of claims 9-11, characterized in that, The method further includes: Send a second indication message to the first communication device, wherein the second indication message is used to indicate monitoring the PDCCH during the inactive period of the discontinuous reception DRX cycle, and the PDCCH is used only for scheduling downlink data.

13. The method according to any one of claims 9-12, characterized in that, The method further includes: Receive second reference information, wherein the second reference information is used to indicate the configuration of a second TDM mode, the second TDM mode being a TDM mode other than the first TDM mode among the plurality of TDM modes; Send a third instruction message to the first communication device, wherein the third instruction message is used to instruct communication to be performed according to the second TDM mode.

14. A communication device, characterized in that, The communication device includes a communication unit and a processing unit, the communication unit and the processing unit being used to perform the method as described in any one of claims 1-8.

15. A communication device, characterized in that, The communication device includes a communication unit and a processing unit, the communication unit and the processing unit being used to perform the method as described in any one of claims 9-13.

16. A communication device, characterized in that, The communication device includes a processor; when the processor invokes a computer program or instructions in memory, it causes the communication device to implement the method as described in any one of claims 1-8.

17. A communication device, characterized in that, The communication device includes a processor; when the processor invokes a computer program or instructions in memory, it causes the communication device to implement the method as described in any one of claims 9-13.

18. A communication device, characterized in that, It includes logic circuits and interfaces, wherein the logic circuits and the interfaces are coupled; The interface is used for inputting and / or outputting information, and the logic circuit is used to enable the communication device to implement the method as described in any one of claims 1-13.

19. The apparatus according to claim 18, characterized in that, The communication device is a chip or chip system.

20. A communication system, characterized in that, The communication system includes the communication device as described in claim 14 and the communication device as described in claim 15; or The communication system includes the communication device as described in claim 16 and the communication device as described in claim 17.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store instructions or computer programs; When the instructions or the computer program are executed, the method described in any one of claims 1-13 is implemented.

22. A computer program product, characterized in that, include: Instructions or computer programs; When the instructions or the computer program are executed, the method described in any one of claims 1-13 is implemented.

Images