WO2025168023A1 - Communication processing method and communication apparatus - Google Patents

Abstract

Disclosed in the present application are a communication processing method and a communication apparatus. The method comprises: determining first time-domain resource allocation for a low-power signal, wherein the first time-domain resource allocation for the low-power signal is associated with second time-domain resource allocation for a synchronization signal block and third time-domain resource allocation for control resource set 0 (CORESET 0). By means of the method in the present application, the first time-domain resource allocation for the low-power signal is associated with the second time-domain resource allocation for the SSB and the third time-domain resource allocation for CORESET 0, such that the low-power signal can be transmitted on the basis of time-domain resources for the SSB and CORESET 0, and thus extra time-domain resource overheads can be reduced, thereby reducing systemic energy-saving gain loss.

Description

Communication processing method and communication device

This application claims priority to the Chinese patent application filed with the China Patent Office on February 8, 2024, with application number 202410178171.7 and application name “A Communication Processing Method and Communication Device”, the entire contents of which are incorporated by reference into this application.

Technical Field

The present application relates to the field of communication technology, and in particular to a communication processing method and a communication device.

Background Art

With the development of wireless communication technology, higher requirements are being placed on device power consumption. In addition to latency, reliability, and availability, the energy efficiency of user equipment (UE) is also crucial for 5G systems. Currently, 5G devices may need to be charged weekly or daily depending on individual usage. Typically, 5G devices tend to consume tens of milliwatts of power when in the idle or inactive radio resource control (RRC) state and hundreds of milliwatts of power when in the RRC connected state. How to extend battery life is essential for improving energy efficiency and user experience.

To improve battery life, the field has introduced an ultra-low power wake-up signal (LP-WUS) mechanism. That is, users use a separate low power wake-up receiver (LP-WUR) to receive a low power wake-up signal, and use the wake-up signal to wake up the main wireless device (Main Radio, MR) for data transmission and reception. When the UE does not detect the low power wake-up signal, the main receiver is in a deep sleep state, which further reduces the power consumption of the terminal.

Therefore, time domain resource allocation for low-power signals is one of the key focuses of 5G communications.

Summary of the Invention

The embodiments of the present application provide a communication processing method and a communication device. Based on the method described in the present application, the energy-saving gain loss of the system can be reduced.

In a first aspect, the present application provides a communication processing method, which includes: determining a first time domain resource allocation of a low power signal, wherein the first time domain resource allocation of the low power signal is associated with a second time domain resource allocation of a synchronization signal block and a third time domain resource allocation of a control resource set zero CORESET 0.

Based on the method described in the first aspect, the time domain resources of the low-power signal are associated with the time domain resources of the synchronization signal block and the time domain resources of CORESET 0, which can reduce the system energy-saving gain loss.

In one possible implementation, the method further includes: receiving indication information from a network device associated with the second time domain resource allocation of the synchronization signal block and the third time domain resource allocation of CORESET 0 to determine the first time domain resource allocation of the low power signal, wherein at least a portion of the indication information is allowed to at least partially indicate the first time domain resource allocation of the low power signal, and the frequency domain resources of the low power signal are different from the frequency domain resources of the synchronization signal block and CORESET 0.

In one possible implementation, CORESET 0 scheduling indicates a system information block having a fourth time domain resource allocation, and the set of time domain resources corresponding to the first time domain resource allocation is a subset of the set of time domain resources corresponding to the second time domain resource allocation, the time domain resources corresponding to the third time domain resource allocation, and the time domain resources corresponding to the fourth time domain resource allocation.

In a possible implementation, the set of time domain resources corresponding to the first time domain resource allocation is a subset of the set of time domain resources corresponding to the second time domain resource allocation and the set of time domain resources corresponding to the third time domain resource allocation.

In a possible implementation, the low-power signal includes a low-power synchronization signal, and a time domain resource of the low-power synchronization signal is at least the same as at least a portion of the time domain resources corresponding to the second time domain resource allocation.

In a possible implementation, the low-power signal includes a low-power synchronization signal, and a time domain resource of the low-power synchronization signal is at least the same as at least a portion of the time domain resources corresponding to the third time domain resource allocation.

In one possible implementation, the low-power signal also includes a low-power wake-up signal, the frequency domain resources of the low-power wake-up signal are the same as the frequency domain resources of the low-power synchronization signal, and the time domain resources of the low-power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation, excluding the time domain resources of the low-power synchronization signal.

In one possible implementation, the low-power signal also includes a low-power wake-up signal, the frequency domain resources of the low-power wake-up signal are different from the frequency domain resources of the low-power synchronization signal, and the time domain resources of the low-power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation.

In a possible implementation, the time domain resources of the low power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation except the time domain resources of the low power synchronization signal.

In a possible implementation, the low-power signal includes a low-power wake-up signal, and the time domain resources of the low-power wake-up signal are the same as at least part of the time domain resources corresponding to the first time domain resource allocation.

In a possible implementation, the time domain resources of the low-power wake-up signal are the same as at least part of the time domain resources corresponding to the second time domain resource allocation.

In a possible implementation, the low-power wake-up signal is associated with a user equipment group, wherein an index of the user equipment group is associated with an index of the synchronization signal block corresponding to the time domain resource of the low-power wake-up signal.

In one possible implementation, the first time domain resource allocation of the low power consumption signal is also associated with the time domain resource allocation of the tracking reference signal. The method also includes: determining that a tracking reference signal is received from a network device; and determining the first time domain resource allocation of the low power consumption signal based on the time domain resource allocation of the tracking reference signal.

In a second aspect, the present application provides a communication processing method, which includes: determining a first time domain resource allocation of a low power signal, wherein the first time domain resource allocation of the low power signal is associated with a second time domain resource allocation of a synchronization signal block and a third time domain resource allocation of a control resource set zero CORESET 0.

The beneficial effects of the possible implementation of the second aspect can be found in the beneficial effects of the possible implementation of the first aspect, and will not be repeated here.

In one possible implementation, the method further includes: conveying indication information associated with the second time domain resource allocation of the synchronization signal block and the third time domain resource allocation of CORESET 0 to the terminal device, wherein at least a portion of the indication information is allowed to at least partially indicate the first time domain resource allocation of the low power signal, and the frequency domain resources of the low power signal are different from the frequency domain resources of the synchronization signal block and CORESET 0.

In one possible implementation, CORESET 0 scheduling indicates a system information block having a fourth time domain resource allocation, and the set of time domain resources corresponding to the first time domain resource allocation is a subset of the set of time domain resources corresponding to the second time domain resource allocation, the time domain resources corresponding to the third time domain resource allocation, and the time domain resources corresponding to the fourth time domain resource allocation.

In a possible implementation, the set of time domain resources corresponding to the first time domain resource allocation is a subset of the set of time domain resources corresponding to the second time domain resource allocation and the set of time domain resources corresponding to the third time domain resource allocation.

In a possible implementation, the low-power signal includes a low-power synchronization signal, and a time domain resource of the low-power synchronization signal is at least the same as at least a portion of the time domain resources corresponding to the second time domain resource allocation.

In a possible implementation, the low-power signal includes a low-power synchronization signal, and a time domain resource of the low-power synchronization signal is at least the same as at least a portion of the time domain resources corresponding to the third time domain resource allocation.

In one possible implementation, the low-power signal also includes a low-power wake-up signal, the frequency domain resources of the low-power wake-up signal are the same as the frequency domain resources of the low-power synchronization signal, and the time domain resources of the low-power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation, excluding the time domain resources of the low-power synchronization signal.

In one possible implementation, the low-power signal also includes a low-power wake-up signal, the frequency domain resources of the low-power wake-up signal are different from the frequency domain resources of the low-power synchronization signal, and the time domain resources of the low-power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation.

In a possible implementation, the time domain resources of the low power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation except the time domain resources of the low power synchronization signal.

In a possible implementation, the low-power signal includes a low-power wake-up signal, and the time domain resources of the low-power wake-up signal are the same as at least part of the time domain resources corresponding to the first time domain resource allocation.

In a possible implementation, the time domain resources of the low-power wake-up signal are the same as at least part of the time domain resources corresponding to the second time domain resource allocation.

In a possible implementation, the low-power wake-up signal is associated with a user equipment group, wherein an index of the user equipment group is associated with an index of the synchronization signal block corresponding to the time domain resource of the low-power wake-up signal.

In one possible implementation, the first time domain resource allocation of the low power consumption signal is also associated with the time domain resource allocation of the tracking reference signal. The method also includes: sending a tracking reference signal to the terminal device so that the terminal device determines the first time domain resource allocation of the low power consumption signal based on the time domain resource allocation of the tracking reference signal.

In a third aspect, the present application provides a communication device, which may be a terminal device, a device in a terminal device, or a device that can be used in conjunction with a terminal device; wherein the communication device may also be a chip system, and the communication device may execute the method executed by the terminal device in the first aspect. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units corresponding to the above functions. The unit may be software and/or hardware. The operations and beneficial effects performed by the communication device can refer to the methods and beneficial effects described in the first aspect above, and repeated parts will not be repeated.

In a fourth aspect, the present application provides a communication device, which may be a network device, a device in a network device, or a device that can be used in conjunction with a network device; wherein the communication device may also be a chip system, and the communication device may execute the method performed by the network device in the second aspect. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units corresponding to the above functions. The unit may be software and/or hardware. The operations and beneficial effects performed by the communication device can refer to the methods and beneficial effects described in the second aspect above, and repeated parts will not be repeated.

In a fifth aspect, the present application provides a communication device comprising a processor. When the processor calls a computer program in a memory, the method executed by a terminal device or a network device in the method described in the first aspect or the second aspect is executed.

In a sixth aspect, the present application provides a communication device, which includes a processor and a memory, the memory being used to store computer-executable instructions; the processor being used to execute the computer-executable instructions stored in the memory, so that the communication device executes the method executed by the terminal device or network device in the method described in the first aspect or the second aspect.

In the seventh aspect, the present application provides a communication device, which includes a processor, a memory and a transceiver, the transceiver is used to receive or send signals; the memory is used to store a computer program; the processor is used to call the computer program from the memory to execute the method executed by the terminal device or network device in the method described in the first aspect or the second aspect.

In an eighth aspect, the present application provides a communication device comprising a processor and an interface circuit, wherein the interface circuit is configured to receive computer execution instructions and transmit them to the processor; the processor runs the computer execution instructions to execute the method executed by a terminal device or a network device in the method described in the first aspect or the second aspect.

In a ninth aspect, the present application provides a computer-readable storage medium for storing computer-executable instructions. When the computer-executable instructions are executed, the terminal device or network device executes the method described in the first aspect or the second aspect.

In a tenth aspect, the present application provides a communication device, which includes a function or unit for executing the method as described in any one of the first aspect or the second aspect.

In an eleventh aspect, the present application provides a computer program product comprising a computer program, which, when executed, enables the method executed by a terminal device or a network device in the method described in the first aspect or the second aspect to be implemented.

In the twelfth aspect, the present application provides a communication system, which includes a terminal device and a network device; wherein the terminal device is used to execute the method described in the first aspect above, and the network device is used to execute the method described in the second aspect above.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

FIG2 is an example diagram of an exemplary SSB mapping provided in an embodiment of the present application;

FIG3 is a diagram of an exemplary multiplexing mode for SSB and CORESET 0 provided in an embodiment of the present application;

FIG4 is a flow chart of a communication processing method provided in an embodiment of the present application;

FIG5 is a diagram illustrating an example of time-frequency resource allocation for a low-power signal, SSB, and CORESET 0 provided in an embodiment of the present application;

FIG6 is an example diagram of time domain resource allocation for a low-power signal provided by an embodiment of the present application;

FIG7 is an example diagram of time domain resource allocation for a low-power signal provided by an embodiment of the present application;

FIG8 is an example diagram of time domain resource allocation of a low-power wake-up signal provided by an embodiment of the present application;

FIG9 is a flow chart of a communication processing method provided in an embodiment of the present application;

FIG10 is a flow chart of a communication processing method provided in an embodiment of the present application;

FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

FIG13 is a schematic structural diagram of a chip provided in an embodiment of the present application.

DETAILED DESCRIPTION

The terms "first" and "second" and the like in the specification, claims, and drawings of this application are used to distinguish between different objects, not to describe a particular order. Furthermore, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and/or" is used to describe the corresponding relationship of associated objects, indicating that there can be three relationships. For example, "A and/or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character "/" generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

To better understand the embodiments of the present application, the following first introduces the system architecture involved in the embodiments of the present application:

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), new radio (NR), the 3rd generation partner project (3GPP) service-based architecture (SBA), and other fifth generation (5G) communication systems or sixth generation (6G) communication systems and other communication systems evolved after 5G.

Figure 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application. The communication system 100 may include a network device 110 and at least one terminal device 120. Figure 1 takes the communication system as an example, including a network device (i.e., network device 110) and one terminal device (i.e., terminal device 120). The terminal device 120 is connected to the network device 110 via a wireless method. The terminal device 120 can be fixed or movable. The network device 110 and the terminal device 120 involved in the communication system 100 in Figure 1 are described in detail below.

The network device 110 can be an evolved Node B (eNB or eNodeB) in LTE; or a base station in a 5G network, a broadband network gateway (BNG), an aggregation switch or a non-3rd generation partnership project (3GPP) access device, etc., and the embodiments of the present application do not make specific limitations on this. For example, the base stations in the embodiments of the present application may include various forms of base stations, such as: macro base stations, micro base stations (also known as small stations), relay stations, access points, next-generation base stations (gNodeB, gNB), transmitting and receiving points (TRP), transmitting points (TP), mobile switching centers, and devices that perform base station functions in device-to-device (D2D), vehicle-to-everything (V2X), machine-to-machine (M2M) communications, and Internet of Things (IoT) communications, etc. The embodiments of the present application do not specifically limit this. The network device can be called a wireless access network device, that is, an access device that enables a terminal device to access the communication system wirelessly. In the embodiments of the present application, the device for implementing the network device function can be the network device itself, or it can be a device that can support the network device to implement the function, such as a chip system or a combination of devices and components that can implement the network device function. The device can be installed in the network device. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

The terminal device 120 includes a device that provides voice and/or data connectivity to the user. For example, the terminal device 120 is a device with wireless transceiver capabilities and can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as on ships); it can also be deployed in the air (such as on airplanes, balloons, and satellites). The terminal device 120 can be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, an in-vehicle terminal, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in smart grids, a wireless terminal in transportation safety, a wireless terminal in smart cities, a wireless terminal in smart homes, a wearable terminal, etc. The embodiments of the present application do not limit the application scenarios. The terminal device 120 may sometimes also be referred to as a terminal, user equipment (UE), access terminal, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal, mobile device, UE terminal, wireless communication device, UE agent or UE device, etc. The terminal device 120 may be fixed or mobile. It will be understood that all or part of the functions of the terminal device 120 in this application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The terminal device 120 in this application may be a terminal for 5G or a terminal for 6G, and this application does not limit this. In the embodiment of the present application, the device for implementing the function of the terminal device 120 may be the terminal device 120, or it may be a device that can support the terminal device 120 to implement the function, such as a chip system or a combination device or component that can implement the function of the terminal device 120, and the device may be installed in the terminal device 120.

It should be noted that Figure 1 is only a schematic diagram of the architecture of a communication system. The communication system 100 may also include other devices, such as wireless relay devices, wireless backhaul devices, core network devices, etc., which are not shown in Figure 1. The embodiments of the present application do not limit the number of various devices included in the communication system.

The embodiments of the present application can be applied to downlink signal transmission, uplink signal transmission, and sidelink communication (such as device-to-device (D2D) signal transmission). For downlink signal transmission, the sending device is a network device, and the corresponding receiving device is a terminal device. For uplink signal transmission, the sending device is a terminal device, and the corresponding receiving device is a network device. For D2D signal transmission, the sending device is a terminal device, and the corresponding receiving device is also a terminal device. The transmission direction of the signal in the embodiments of the present application is not limited.

The network device 110 and the terminal device 120 can communicate via a licensed spectrum, an unlicensed spectrum, or both. The network device 110 and the terminal device 120 can communicate via a spectrum below 6 gigahertz (GHz), a spectrum above 6 GHz, or both. The embodiments of the present application do not limit the spectrum resources used between the network device 110 and the terminal device 120.

In the embodiments of the present application, a time-domain symbol may be an orthogonal frequency division multiplexing (OFDM) symbol or a discrete Fourier transform spread-OFDM (DFT-s-OFDM) symbol. Unless otherwise specified, symbols in the embodiments of the present application refer to time-domain symbols.

It can be understood that in the embodiments of the present application, the physical downlink shared channel (PDSCH), the physical downlink control channel (PDCCH) and the physical uplink shared channel (PUSCH) are merely examples of downlink data channels, downlink control channels and uplink data channels, respectively. In different systems and different scenarios, data channels and control channels may have different names, and the embodiments of the present application do not limit this.

In an embodiment of the present application, a low-power wake-up signal (LP-WUS) is introduced into the communication standard. The LP-WUS is received by a separate receiver, called a low-power wake-up receiver (LP-WUR) 121. The terminal device 120 needs to use a main radio (MR) 122 to properly process downlink and/or uplink data.

In one possible implementation, when the LP-WUR 121 of the terminal device 120 receives the LP-WUS and the LP-WUS indicates wake-up, the terminal device 120 turns on the MR 122 to receive and process downlink and/or uplink signals.

In one possible implementation, the LP-WUR 121 of the terminal device 120 does not receive the LP-WUS signal, or the LP-WUS indication received by the LP-WUR 121 of the terminal device 120 does not indicate wake-up, and the terminal device 120 will keep the MR 122 in a sleep state.

Optionally, LP-WUS signals can be used in radio resource control (RRC) connected, inactive, idle, and other states.

In one possible implementation, the sleep states of MR 122 may include four types: ultra-deepsleep, deep sleep, light sleep, and micro sleep.

In a communication system 100, network devices 110 are widely deployed to provide various telecommunication services, such as voice, video, data, messaging, and broadcast. To connect to the network devices 110, terminal devices 120 may need to acquire synchronization and obtain necessary system information. In wireless communication networks such as NR, the synchronization and access process may involve several signals, such as the primary synchronization signal (PSS) and the secondary synchronization signal (SSS).

PSS can allow network detection in the presence of high initial frequency errors. SSS can allow more accurate frequency adjustment and channel estimation while providing basic network information such as cell identifiers (IDs).

The physical broadcast channel (PBCH) can provide a subset of the minimum system information for random access and configuration for obtaining the remaining minimum system information. It can also provide timing information within a cell, for example, to separate the timing between beams transmitted from the cell. The amount of information suitable for the PBCH is limited to control the size. In addition, the demodulation reference signal (DMRS) can be interleaved with the PBCH resources to facilitate proper reception of the PBCH.

An SS/PBCH block, also referred to as an SSB, can include the aforementioned signals (e.g., PSS, SSS, and DMRS) and PBCH. For example, depending on the frequency range, an SSB can have a subcarrier spacing (SCS) of 15 kHz, 30 kHz, 120 kHz, or 240 kHz.

Figure 2 is an example diagram of an exemplary SSB mapping provided by an embodiment of the present application. In Figure 2, each numbered small box represents an orthogonal frequency division multiplexing (OFDM) symbol, and the black symbols represent the mapping of candidate SSB positions where SSBs can be transmitted. As shown in Figure 2, one candidate SSB position can correspond to four OFDM symbols. Figure 2 shows exemplary candidate SSB positions for 15kHz SCS, 30kHz SCS (including mode 1 and mode 2) and 120kHz SCS in their corresponding two time slots, respectively, and for 240kHz SCS in its corresponding four time slots.

In one possible implementation, an SSB burst set may be transmitted periodically according to a period configured in the system information. For example, a 20ms SSB burst set period may be assumed for initial access. By using the SSBs in the SSB burst set, the UE can determine downlink timing and/or frequency offset, etc., and obtain some basic system information from the PBCH. When the UE acquires downlink synchronization, it can know in which time slots SSB transmissions are expected. Therefore, the position of the SSB in the SSB burst set may need to be provided to the UE in order to derive subframe-level synchronization.

In addition to synchronization, some system information may also be important for the terminal device 120 to connect to the network device 110. The system information may be carried in the PDSCH scheduled by the PDCCH in the control resource set 0 (CORESET 0) configured by the PBCH in the NR. The system information may be used to indicate a bitmap of the actual transmitted SSBs.

CORESET 0 configured by PBCH may also be used for other system information, paging and/or random access response, etc. In one possible implementation, CORESET 0 configured by PBCH may include multiple resource blocks in the frequency domain and multiple OFDM symbols in the time domain.

After detecting an SSB, the UE may attempt to search for possible candidate PDCCHs based at least in part on the CORESET 0 configuration (if present in the PBCH). In one possible implementation, there may be several possible multiplexing patterns between CORESET 0 and the SSB configured by the PBCH.

FIG3 is a diagram of exemplary multiplexing modes for SSB and CORESET 0 provided in an embodiment of the present application. As shown in FIG3 , three multiplexing modes (shown as Mode 1, Mode 2, and Mode 3) can be applied to SSB and CORESET in the time domain and/or frequency domain. Among these multiplexing modes, Mode 1 can be supported in frequency bands below 6 GHz and/or above 6 GHz, while Mode 2 and Mode 3 are only supported in frequency bands above 6 GHz.

In one possible implementation, each multiplexing mode may have a set of supported parameter set combinations {SSB SCS, PDCCH SCS}. For example, a set of parameter set combinations {SSB SCS, PDCCH SCS} supported by mode 1 in sub-6 GHz bands may include {15 kHz, 15 kHz}, {15 kHz, 30 kHz}, {30 kHz, 15 kHz}, and {30 kHz, 30 kHz}, and a set of parameter set combinations {SSB SCS, PDCCH SCS} supported by mode 1 in bands above 6 GHz may include {120 kHz, 60 kHz}, {120 kHz, 120 kHz}, {240 kHz, 60 kHz}, and {240 kHz, 120 kHz}. Similarly, a set of parameter set combinations {SSB SCS, PDCCH SCS} supported by mode 2 in the frequency band above 6 GHz may include {120 kHz, 60 kHz} and {240 kHz, 120 kHz}, and a set of parameter set combinations {SSB SCS, PDCCH SCS} supported by mode 3 in the frequency band above 6 GHz may include {120 kHz, 120 kHz}.

According to some possible embodiments, the Type 0 PDCCH common search space (C-SS) may be a search space used for system information block 1 (SIB1) scheduling. The configuration of the Type 0 PDCCH C-SS is specified in Section 13 of 3GPP TS 38.213. In addition, 3GPP TS 38.213 also defines some PDCCH monitoring opportunities and related configurations (such as monitoring period, monitoring window, etc.) for Mode 1, Mode 2, and Mode 3.

FIG3 also shows the relationship between the bandwidth of a PDSCH and the bandwidth of a CORESET including a PDCCH that schedules the PDSCH.

In one possible implementation, the initial active downlink (DL) bandwidth part (BWP) can be defined as the frequency location and bandwidth of CORESET 0, along with a parameter set for system information. The PDSCH, which delivers system information, can be restricted to the initial active DL BWP. The UE can learn specific resource configurations (such as time and/or frequency domain resource allocations) from downlink control information (DCI). DCI can be used to schedule SIB1 for paging, random access, and other purposes.

In one possible implementation, the DCI size may be predefined and constant for all SSB and CORESET 0 multiplexing modes. For example, the DCI may have the same size as DCI format 1_0. The DCI carried by the PDCCH in the CORESET configured by the PBCH may include indication information about time domain resource allocation, for example, one or more bits indicating time domain resource allocation.

For different reuse modes between SSB and CORESET 0, the total number of bits indicating time domain resource allocation may be different. For reuse modes 2 and 3, if it is assumed that the PDSCH is time-aligned with the SSB, the time domain resource allocation bits may not be necessary. In addition, for different reuse modes between SSB and CORESET 0, there may be different requirements for the number of time domain resource allocation bits in the DCI. For example, for reuse modes 2 and 3, the number of time domain resource allocation bits in the DCI carried by the PDCCH in CORESET 0 may be smaller than that for reuse mode 1. On the other hand, for reuse modes 2 and 3, if the PDSCH is always scheduled to be time-aligned with the associated SSB, this may directly limit the flexibility of time domain resource allocation. Therefore, it may be necessary to introduce an effective scheme to more efficiently configure and utilize the indication information of time domain resource allocation.

In some possible embodiments, a solution is provided in which a network device may provide a terminal device with indication information of time domain resource allocation. For example, for various multiplexing modes between SSB and CORESET 0, indication information such as one or more bits may be included in a time domain resource allocation field in the DCI carried by the PDCCH in CORESET 0. For a specified multiplexing mode (e.g., multiplexing mode 2 and/or mode 3), some or all of the time domain resource allocation bits may be reused for purposes other than indicating time domain resource allocation. Optionally, at least a portion of the time domain resource allocation bits may also be used together with one or more other indicators in the DCI carried by the PDCCH in CORESET 0 (e.g., one or more reserved bits/code points, one or more bits/code points in use, etc.) to indicate other information.

In one possible implementation, in a wireless communication network such as 5G/NR, a UE-specific radio resource control (RRC) message with a bitmap may be used to indicate the SSBs actually transmitted. To determine the set of SSBs actually transmitted, the UE may need to obtain system information and/or RRC messages containing the bitmap of the SSBs actually transmitted. In addition, the UE may also need to know the SSB burst set period based on the system information and/or RRC messages.

In one possible implementation, the indication information of the time domain resource allocation in the DCI carried by the PDCCH in CORESET 0 can be reused to indicate which subsets of the candidate SSB positions have the SSBs actually transmitted. This can enable the UE to know which SSB set is actually transmitted before the UE obtains the system information and RRC message containing the bitmap of the SSBs actually transmitted. Optionally or additionally, at least a portion of the indication information about the time domain resource allocation can be used to indicate the SSB burst set period, so that when the UE cannot obtain the SSB burst set period according to the system information and RRC message within the SSB burst set period, the UE can know the duration of an SSB burst set.

In one possible implementation, the indication information of the time domain resource allocation in the DCI carried by a channel such as the PDCCH in CORESET 0 can be used to indicate the time domain resource allocation and one or more SSBs that are not transmitted. The time domain resource allocation can be applied to the PDSCH scheduled by the PDCCH in CORESET 0. According to the time domain resource allocation, the scheduled PDSCH can overlap with other CORESETs. Since the CORESETs that overlap with the PDSCH can be associated with different SSBs, the UE can assume that the SSBs associated with the overlapping CORESETs are not transmitted. Therefore, the indication information of the time domain resource allocation in the DCI (e.g., 4 time domain resource allocation bits) can also be used as an indication of one or more SSBs that are not transmitted.

It should be noted that some embodiments of the present disclosure are described with respect to 5G or NR systems, which are used as non-limiting examples of specific exemplary network configurations and system deployments. Therefore, the terms involved in and/or directly related to the description of the exemplary embodiments given herein are only used for the non-limiting examples and embodiments presented and do not limit the present application in any way. The present application can equally use any other system configuration or radio technology as long as the exemplary embodiments described herein are applicable.

Figure 4 is a flow chart of a communication processing method provided in an embodiment of the present application. The method shown in Figure 4 may be performed by the aforementioned network device. Alternatively, the method shown in Figure 4 may be performed by a chip within the network device, which is not limited in the present embodiment. Figure 4 illustrates the method using a network device as an example.

S401. Determine a first time domain resource allocation for a low power consumption signal.

Among them, the first time domain resource allocation of the low power signal is associated with the second time domain resource allocation of the synchronization signal block and the third time domain resource allocation of the control resource set zero CORESET 0.

The synchronization signal block can be a synchronization signal and physical broadcast channel block (Synchronization Signal and PBCH Block, SSB), or any suitable signal block that can facilitate the terminal device to synchronize with the network device and access the network device. This application does not limit the name.

The second time domain resource allocation for SSB and the third time domain resource allocation for CORESET 0 have been allocated based on the communication system application scenario and service requirements. In other words, the second time domain resource allocation for SSB and the third time domain resource allocation for CORESET 0 each have corresponding time domain resources.

In one possible implementation, the network device may determine the first time domain resource allocation of the low power signal based on the indication of the high-layer signaling, so that the first time domain resource allocation of the low power signal is associated with the second time domain resource allocation of the SSB and the third time domain resource allocation of the CORESET 0.

In one possible implementation, the network device can independently determine the first time domain resource allocation of the low-power signal based on the application scenario and business requirements of the communication system, so that the first time domain resource allocation of the low-power signal is associated with the second time domain resource allocation of SSB and the third time domain resource allocation of CORESET 0.

In one possible implementation, the network device may convey indication information associated with the second time domain resource allocation of SSB and the third time domain resource allocation of CORESET 0 to the terminal device, wherein at least a portion of the indication information is allowed to at least partially indicate the first time domain resource allocation of the low power signal, and the frequency domain resources of the low power signal are different from the frequency domain resources of SSB and CORESET 0.

Specifically, after the network device determines the first time domain resource allocation for the low power signal, it can convey indication information associated with the second time domain resource allocation for the SSB and the third time domain resource allocation for CORESET 0 to the terminal device to indicate the first time domain resource allocation for the low power signal to the terminal device. At least a portion of the indication information is allowed to at least partially indicate the first time domain resource allocation for the low power signal. For example, at least a portion of the existing indication information can be reused or a reserved portion in the existing indication information can be used to indicate the first time domain resource allocation for the low power signal. In addition, in order not to interfere with the SSB and CORESET 0, frequency domain resources other than the frequency domain resources of the SSB and CORESET 0 in the BWP can be used to carry the low power signal.

For example, see Figure 5, which is a diagram illustrating an example of time-frequency resource allocation for a low-power signal, SSB, and CORESET 0, provided in an embodiment of the present application. As shown in Figure 5, in the three multiplexing modes of SSB and CORESET 0, the first time-domain resource allocation for the low-power signal can be associated with the second time-domain resource allocation for SSB and the third time-domain resource allocation for CORESET 0, and the frequency-domain resources for the low-power signal are different from the frequency-domain resources for SSB and CORESET 0.

In one possible implementation, CORESET 0 scheduling indicates a system information block, the system information block has a fourth time domain resource allocation, and the set of time domain resources corresponding to the first time domain resource allocation can be a subset of the set of time domain resources corresponding to the second time domain resource allocation, the time domain resources corresponding to the third time domain resource allocation, and the time domain resources corresponding to the fourth time domain resource allocation.

Specifically, the DCI in CORESET 0 can schedule an indicator system information block, such as SIB1. Generally speaking, SIB1 is carried by PDSCH and has a fourth time domain resource allocation. The set of time domain resources corresponding to the first time domain resource allocation of the low-power signal can be a subset of the set of time domain resources corresponding to the second time domain resource allocation of the SSB, the time domain resources corresponding to the third time domain resource allocation of CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation of SIB1.

In this application, a subset of a set includes the empty set and the set itself.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation for the low-power signal may be an empty set, indicating that no time domain resources are allocated for the low-power signal. In other words, the low-power signal is not transmitted in the set of time domain resources corresponding to the second time domain resource allocation for SSB, the time domain resources corresponding to the third time domain resource allocation for CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation for SIB1.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation for the low-power signal can be the same as the set of time domain resources corresponding to the second time domain resource allocation for the SSB, the time domain resources corresponding to the third time domain resource allocation for CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation for SIB1. Referring to Figure 5 , for the three multiplexing modes of SSB and CORESET 0, the PDSCH in all three multiplexing modes can carry SIB1 indicated by the DCI scheduling in CORESET 0. The set of time domain resources allocated for the low-power signal can be the same as the set of time domain resources for the SSB, the time domain resources for CORESET 0, and the time domain resources for the PDSCH carrying SIB1. In other words, the symbol positions occupied by the low-power signal can be aligned in time resources with the symbol positions occupied by the SSB, the symbol positions occupied by CORESET 0, and the symbol positions of the PDSCH carrying SIB1. That is to say, low-power signals are transmitted on all time domain resources corresponding to the set of time domain resources corresponding to the second time domain resource allocation of SSB, the time domain resources corresponding to the third time domain resource allocation of CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation of SIB1.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation for the low-power signal may be a non-empty proper subset of the set of time domain resources corresponding to the second time domain resource allocation for the SSB, the time domain resources corresponding to the third time domain resource allocation for CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation for SIB1. That is, among the time domain resources corresponding to the set of time domain resources corresponding to the second time domain resource allocation for the SSB, the time domain resources corresponding to the third time domain resource allocation for CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation for SIB1, only some of the time domain resources are configured for transmission of the low-power signal.

In a possible implementation, the set of time domain resources corresponding to the first time domain resource allocation may be a subset of the set of time domain resources corresponding to the second time domain resource allocation and the set of time domain resources corresponding to the third time domain resource allocation.

Referring to Figure 5 , for Modes 2 and 3 of the three multiplexing modes for SSB and CORESET 0, since the PDSCH is always scheduled to be time-aligned with the associated SSB, the set of time domain resources allocated to the low-power signal can be the same as only the set of time domain resources for the SSB and CORESET 0. In other words, the symbol positions occupied by the low-power signal can be time-aligned only with the symbol positions occupied by the SSB and CORESET 0.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation for the low-power signal may be an empty set, indicating that no time domain resources are allocated for the low-power signal. In other words, the low-power signal is not transmitted in the set of time domain resources corresponding to the second time domain resource allocation for SSB and the set of time domain resources corresponding to the third time domain resource allocation for CORESET 0.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation of the low-power signal may be the same as the set of time domain resources corresponding to the second time domain resource allocation of the SSB and the set of time domain resources corresponding to the third time domain resource allocation of CORESET 0, for example, as shown in Mode 2 and Mode 3 of FIG5 . In other words, the low-power signal is transmitted on all time domain resources corresponding to the set of time domain resources corresponding to the second time domain resource allocation of the SSB and the third time domain resource allocation of CORESET 0.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation for the low-power signal may be a non-empty proper subset of the set of time domain resources corresponding to the second time domain resource allocation for the SSB, the time domain resources corresponding to the third time domain resource allocation for CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation for SIB1. That is, among the time domain resources corresponding to the set of time domain resources corresponding to the second time domain resource allocation for the SSB and the time domain resources corresponding to the third time domain resource allocation for CORESET 0, only some of the time domain resources are configured for transmission of the low-power signal.

In a possible implementation, the low power consumption signal may include a low power consumption synchronization signal, and the time domain resources of the low power consumption synchronization signal may be at least the same as at least part of the time domain resources corresponding to the second time domain resource allocation.

The low power synchronization signal (LP-SS) is at least used for the LP-WUR of the terminal device to perform coarse time synchronization and/or coarse frequency synchronization with the network device, so that the LP-WUR can receive the LP-WUS to wake up the MR. This application does not limit the name of the low power synchronization signal.

6 , the time domain resources of the LP-SS may be at least the same as at least a portion of the time domain resources corresponding to the second time domain resource allocation of the SSB.

Optionally, the time domain resources of the LP-SS may be the same as part of the time domain resources corresponding to the second time domain resource allocation of the SSB.

For example, in the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy some symbol positions of SSB, as shown in (6b) and (6f) in Figure 6 (this situation in mode 2 is not shown).

Optionally, the time domain resources of the LP-SS may be the same as the time domain resources corresponding to the second time domain resource allocation of the SSB.

For example, in the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the symbol position of SSB, as shown in (6a), (6c), and (6d) in Figure 6 (this situation in mode 3 is not shown).

Optionally, the time domain resources of the LP-SS may be at least the same as the time domain resources corresponding to the second time domain resource allocation of the SSB.

For example, in mode 2 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the symbol position of SSB as well as the symbol position of CORESET 0, as shown in (6e) in Figure 6.

In other words, in mode 1 and mode 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy at least part of the position of the SSB symbol; in mode 2, LP-SS can occupy at least part of the position of the SSB symbol and at least part of the position of the CORESET 0 symbol.

For example, the second time domain resource allocation of SSB can correspond to time domain resources of 4 symbols, and the third time domain resource allocation of CORESET 0 can correspond to time domain resources of 2 symbols. In Modes 1 and 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the time domain resources corresponding to any combination of 1 to 4 symbols of the 4 SSB symbols. In Mode 2 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the time domain resources corresponding to any combination of 1 to 6 symbols of the 4 SSB symbols and 2 CORESET 0 symbols, a total of 6 symbols (this application does not limit whether the symbols are continuous).

Furthermore, for the three multiplexing modes, LP-SS can correspond to beams one-to-one. That is, when certain SSBs are determined not to be transmitted, LP-SS is not transmitted on the corresponding time domain resources.

For multiplexing mode 1, LP-SS repetition detection can also be performed at the SIB1 location. Furthermore, the number of repetition checks and/or detection conditions can be configured. The configuration information can be pre-set or indicated by the master information block (MIB).

In a possible implementation, the low power consumption signal may include an LP-SS, and the time domain resources of the LP-SS may be at least the same as at least part of the time domain resources corresponding to the third time domain resource allocation.

7 , the time domain resources of the LP-SS may be at least the same as at least part of the time domain resources corresponding to the third time domain resource allocation of CORESET 0.

Optionally, the time domain resources of LP-SS may be the same as part of the time domain resources corresponding to the third time domain resource allocation of CORESET 0.

For example, in Mode 2 and Mode 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy some symbol positions of CORESET 0, as shown in (7c) in Figure 7 (this situation in Mode 2 is not shown).

Optionally, the time domain resources of LP-SS can be the same as the time domain resources corresponding to the third time domain resource allocation of CORESET 0.

For example, in Mode 2 and Mode 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the symbol position of CORESET 0, as shown in (7a) in Figure 7 (this situation in Mode 3 is not shown).

Optionally, the time domain resources of the LP-SS may be at least the same as the time domain resources corresponding to the third time domain resource allocation of CORESET 0.

For example, in Mode 2 and Mode 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the symbol position of SSB as well as the symbol position of CORESET 0, as shown in (7b) in Figure 7 (this case in Mode 3 is not shown).

In other words, in mode 2 and mode 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy at least part of the position of the symbol of CORESET 0 and at least part of the position of the symbol of SSB.

For example, the second time domain resource allocation for SSB can correspond to time domain resources of 4 symbols, and the third time domain resource allocation for CORESET 0 can correspond to time domain resources of 2 symbols. In Mode 2 of the three multiplexing modes for SSB and CORESET 0, LP-SS can occupy the time domain resources corresponding to any combination of 1 to 6 symbols from the total of 6 symbols, namely, 4 symbols of SSB and 2 symbols of CORESET 0. In Mode 3 of the three multiplexing modes for SSB and CORESET 0, since the symbols of CORESET 0 and SSB are aligned in the time domain, LP-SS can occupy the time domain resources corresponding to any combination of 1 to 4 symbols from the 4 symbols of SSB (this application does not limit whether the symbols are continuous).

In one possible implementation, the low-power signal also includes an LP-WUS, the frequency domain resources of the LP-WUS may be the same as the frequency domain resources of the LP-SS, and the time domain resources of the LP-WUS are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation of the low-power signal, excluding the time domain resources of the LP-SS.

LP-WUS may be other low-power signals as shown in FIG6 and FIG7. When the frequency domain resources of LP-WUS are the same as the frequency domain resources of LP-SS, as shown in (6a), (6b), (6d), (6f) in FIG6 and (7a) and (7c) in FIG7, LP-WUS and LP-SS may be configured in a time division multiplexing (TDM) manner, and LP-WUS may occupy part or all of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation of the low-power signal, excluding the time domain resources of LP-SS (this application does not limit whether the symbols are continuous).

In one possible implementation, the low-power signal also includes an LP-WUS, the frequency domain resources of the LP-WUS may be different from the frequency domain resources of the LP-SS, and the time domain resources of the LP-WUS are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation of the low-power signal, excluding the time domain resources of the LP-SS.

When the frequency domain resources of LP-WUS are different from the frequency domain resources of LP-SS (i.e., LP-WUS and LP-SS are configured in frequency division multiplexing (FDM)), LP-WUS can occupy part or all of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation of the low-power signal (this application does not limit whether the symbols are continuous).

Optionally, the time domain resources of the LP-WUS are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation of the low power signal, excluding the time domain resources of the LP-SS. That is, during the transmission of the LP-SS, the LP-WUS is not transmitted.

For mode 1 among the three multiplexing modes, the time domain resource configuration of LP-WUS also needs to meet the configuration of Type 0-PDCCH C-SS for mode 1 in 3GPP TS 38.213, so as to realize the transmission of LP-WUS under appropriate PDCCH monitoring timing and related configurations (such as monitoring period, monitoring window, etc.).

In a possible implementation, the low power consumption signal may include an LP-WUS, and the time domain resources of the LP-WUS may be the same as at least part of the time domain resources corresponding to the first time domain resource allocation.

Refer to FIG8 , which is an example diagram of time domain resource allocation of a low power consumption wake-up signal (LP-WUS) provided in an embodiment of the present application.

In the three multiplexing modes of SSB and CORESET 0, the time domain resources of the LP-WUS can be the same as at least part of the time domain resources corresponding to the first time domain resource allocation. In other words, the time domain resources of the LP-WUS can be a non-empty subset of the set of time domain resources corresponding to the first time domain resource allocation, for example, (8a) to (8f) in Figure 8. In addition, the time domain resources of the LP-WUS can be discontinuous, for example, (8b) and (8e) in Figure 8.

It is easy to understand that the set of time domain resources of LP-WUS can be the same as the set of time domain resources corresponding to the first time domain resource allocation. That is, in this case, all time domain resources corresponding to the first time domain resource allocation can be used for LP-WUS transmission.

In a possible implementation manner, the time domain resources of the LP-WUS are at least the same as at least a portion of the time domain resources corresponding to the second time domain resource allocation.

In the three multiplexing modes of SSB and CORESET 0, the time domain resources of the LP-WUS can be the same as at least part of the time domain resources corresponding to the second time domain resource allocation. In other words, the time domain resources of the LP-WUS can be a non-empty subset of the set of time domain resources corresponding to the second time domain resource allocation, for example, (8a), (8c), (8d), and (8f) in Figure 8. In addition, the time domain resources of the LP-WUS can be discontinuous, for example, (8e) in Figure 8.

It is easy to understand that when the time domain resources of the LP-WUS are a non-empty subset of the set of time domain resources corresponding to the second time domain resource allocation, the LP-WUS may correspond to the SSB.

In one possible implementation, the LP-WUS may be associated with a user equipment group (UE group), wherein the index of the user equipment group is associated with the index of the SSB corresponding to the time domain resources of the LP-WUS.

Specifically, the user equipment group may be a plurality of UEs grouped according to a specific standard.

Optionally, considering different locations of UEs, UEs with the same beam or related beams may be in one group, that is, the user equipment groups may be divided according to beams.

Optionally, UE groups may be divided according to the time slot structure type, and different parameter sets (numerologies) or services may be placed in different groups.

Optionally, UEs with different processing capabilities may be grouped according to supported bandwidth ranges.

This application does not limit the grouping method of user equipment groups.

The LP-WUS may be a paging message for a user equipment group. Since the LP-WUS may correspond to an SSB within an SSB burst set period (e.g., 20 ms), the LP-WUS may be configured for a specific user equipment group based on the SSB index. In other words, the SSB index may correspond to the user equipment group index. Based on the SSB index corresponding to the time domain resource of the LP-WUS, the LP-WUS may be configured as a paging message for the user equipment group having the corresponding user equipment group index.

In one possible implementation, one SSB may correspond to one user equipment group.

Optionally, the index of the SSB can be matched with the index of the user device group based on a hash function, and the correspondence between the index of the SSB and the index of the user device group can be updated according to the SSB burst set period (i.e., the beam scanning period), so that the user device group can traverse all beams.

Optionally, when the correspondence between the index of the SSB and the index of the user equipment group has been determined in the current beam scanning period, the correspondence between the index of the SSB in the next beam scanning period and the index of the user equipment group can be updated to Index _{_SSB} = (Index _{_UE group} + a) mod N _{_UE group} , where Index _{_SSB} is the index of the SSB, Index _{_UE group} is the index of the user equipment group in the current beam scanning period, N _{_UE group} is the number of groups of the user equipment group, and a can be any positive integer less than N _{_UE group} and coprime with N _{_UE group} , so that the user equipment group can traverse all beams.

In one possible implementation, multiple SSBs may correspond to one user equipment group.

Optionally, multiple SSBs in an SSB burst set period may correspond to one user equipment group, so that LP-WUS may be repeatedly sent to a specific user equipment group at multiple SSB time domain positions, or LP-WUS may be sent using longer time domain symbols.

In one possible implementation, an SSB burst set may be associated with a user equipment group, that is, all SSBs in an SSB burst set period may correspond to a specific user equipment group, so that within one SSB burst set period (e.g., 20 ms), the specific user equipment group may scan all beams.

Optionally, the starting position of the SSB burst set period can be the beginning of the period of connected mode discontinuous reception (CDRX) or extended/enhanced discontinuous reception (EDRX).

In one possible implementation, the first time domain resource allocation of the low power signal is also associated with the time domain resource allocation of a tracking reference signal (TRS). The method also includes: sending the TRS to the terminal device so that the terminal device determines the first time domain resource allocation of the low power signal based on the time domain resource allocation of the TRS.

Optionally, the symbol position of the LP-SS or the symbol position of the LP-WUS can be determined based on the symbol position of the TRS. For example, the symbol position of the LP-SS or the symbol position of the LP-WUS can be the same as the symbol position of the TRS, or separated by a predefined offset value.

In the method described in Figure 4, the first time domain resource allocation of the low-power signal determined by the network device is associated with the second time domain resource allocation of SSB and the third time domain resource allocation of CORESET 0. The low-power signal can be transmitted based on the time domain resources of SSB and CORESET 0, which can reduce the additional time domain resource overhead and reduce the system energy-saving gain loss.

Figure 9 is a flow chart of a communication processing method provided in an embodiment of the present application. The method shown in Figure 9 may be executed by the terminal device mentioned above. Alternatively, the method shown in Figure 9 may be executed by a chip in the terminal device, which is not limited in the present embodiment. Figure 9 illustrates the method using a terminal device as an example.

S901. Determine a first time domain resource allocation for a low power consumption signal.

Among them, the first time domain resource allocation of the low power signal is associated with the second time domain resource allocation of the synchronization signal block and the third time domain resource allocation of the control resource set zero CORESET 0.

The synchronization signal block can be a synchronization signal and physical broadcast channel block (Synchronization Signal and PBCH Block, SSB), or any suitable signal block that can facilitate the terminal device to synchronize with the network device and access the network device. This application does not limit the name.

The second time domain resource allocation for SSB and the third time domain resource allocation for CORESET 0 have been allocated based on the communication system application scenario and service requirements. In other words, the second time domain resource allocation for SSB and the third time domain resource allocation for CORESET 0 each have corresponding time domain resources.

In one possible implementation, the terminal device can determine the first time domain resource allocation of the low power signal based on the indication of the high-layer signaling, so that the first time domain resource allocation of the low power signal is associated with the second time domain resource allocation of the SSB and the third time domain resource allocation of the CORESET 0.

In one possible implementation, the terminal device can independently determine the first time domain resource allocation of the low power signal according to a predefined configuration, so that the first time domain resource allocation of the low power signal is associated with the second time domain resource allocation of SSB and the third time domain resource allocation of CORESET 0.

In one possible implementation, the terminal device may receive indication information from a network device associated with the second time domain resource allocation of SSB and the third time domain resource allocation of CORESET 0 to determine the first time domain resource allocation of the low power signal, wherein at least a portion of the indication information is allowed to at least partially indicate the first time domain resource allocation of the low power signal, and the frequency domain resources of the low power signal are different from the frequency domain resources of SSB and CORESET 0.

Specifically, after the network device determines the first time domain resource allocation for the low power signal, it can convey indication information associated with the second time domain resource allocation for the SSB and the third time domain resource allocation for CORESET 0 to the terminal device to indicate the first time domain resource allocation for the low power signal to the terminal device. The terminal device can determine the first time domain resource allocation for the low power signal based on the indication information. At least a portion of the indication information is allowed to at least partially indicate the first time domain resource allocation for the low power signal. For example, at least a portion of the existing indication information can be reused or a reserved portion in the existing indication information can be used to indicate the first time domain resource allocation for the low power signal. In addition, in order not to interfere with the SSB and CORESET 0, frequency domain resources in the BWP other than the frequency domain resources of the SSB and CORESET 0 can be used to carry the low power signal.

For example, see Figure 5, which shows an example of time-domain resource allocation for a low-power signal, SSB, and CORESET 0, provided in an embodiment of the present application. As shown in Figure 5, in the three multiplexing modes of SSB and CORESET 0, the first time-domain resource allocation for the low-power signal can be associated with the second time-domain resource allocation for SSB and the third time-domain resource allocation for CORESET 0, and the frequency-domain resources for the low-power signal are different from the frequency-domain resources for SSB and CORESET 0.

In one possible implementation, CORESET 0 scheduling indicates a system information block, the system information block has a fourth time domain resource allocation, and the set of time domain resources corresponding to the first time domain resource allocation can be a subset of the set of time domain resources corresponding to the second time domain resource allocation, the time domain resources corresponding to the third time domain resource allocation, and the time domain resources corresponding to the fourth time domain resource allocation.

Specifically, the DCI in CORESET 0 can schedule an indicator system information block, such as SIB1. Generally speaking, SIB1 is carried by PDSCH and has a fourth time domain resource allocation. The set of time domain resources corresponding to the first time domain resource allocation of the low-power signal can be a subset of the set of time domain resources corresponding to the second time domain resource allocation of the SSB, the time domain resources corresponding to the third time domain resource allocation of CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation of SIB1.

In this application, a subset of a set includes the empty set and the set itself.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation for the low-power signal may be an empty set, indicating that no time domain resources are allocated for the low-power signal. In other words, the low-power signal is not transmitted in the set of time domain resources corresponding to the second time domain resource allocation for SSB, the time domain resources corresponding to the third time domain resource allocation for CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation for SIB1.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation for the low-power signal can be the same as the set of time domain resources corresponding to the second time domain resource allocation for the SSB, the time domain resources corresponding to the third time domain resource allocation for CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation for SIB1. Referring to Figure 5 , for the three multiplexing modes of SSB and CORESET 0, the PDSCH in all three multiplexing modes can carry SIB1 indicated by the DCI scheduling in CORESET 0. The set of time domain resources allocated for the low-power signal can be the same as the set of time domain resources for the SSB, the time domain resources for CORESET 0, and the time domain resources for the PDSCH carrying SIB1. In other words, the symbol positions occupied by the low-power signal can be aligned in time resources with the symbol positions occupied by the SSB, the symbol positions occupied by CORESET 0, and the symbol positions of the PDSCH carrying SIB1. That is to say, low-power signals are transmitted on all time domain resources corresponding to the set of time domain resources corresponding to the second time domain resource allocation of SSB, the time domain resources corresponding to the third time domain resource allocation of CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation of SIB1.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation for the low-power signal may be a non-empty proper subset of the set of time domain resources corresponding to the second time domain resource allocation for the SSB, the time domain resources corresponding to the third time domain resource allocation for CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation for SIB1. That is, among the time domain resources corresponding to the set of time domain resources corresponding to the second time domain resource allocation for the SSB, the time domain resources corresponding to the third time domain resource allocation for CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation for SIB1, only some of the time domain resources are configured for transmission of the low-power signal.

In a possible implementation, the set of time domain resources corresponding to the first time domain resource allocation may be a subset of the set of time domain resources corresponding to the second time domain resource allocation and the set of time domain resources corresponding to the third time domain resource allocation.

Referring to Figure 5 , for Modes 2 and 3 of the three multiplexing modes for SSB and CORESET 0, since the PDSCH is always scheduled to be time-aligned with the associated SSB, the set of time domain resources allocated to the low-power signal can be the same as only the set of time domain resources for the SSB and CORESET 0. In other words, the symbol positions occupied by the low-power signal can be time-aligned only with the symbol positions occupied by the SSB and CORESET 0.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation for the low-power signal may be an empty set, indicating that no time domain resources are allocated for the low-power signal. In other words, the low-power signal is not transmitted in the set of time domain resources corresponding to the second time domain resource allocation for SSB and the set of time domain resources corresponding to the third time domain resource allocation for CORESET 0.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation of the low-power signal may be the same as the set of time domain resources corresponding to the second time domain resource allocation of the SSB and the set of time domain resources corresponding to the third time domain resource allocation of CORESET 0, for example, as shown in Mode 2 and Mode 3 of FIG5 . In other words, the low-power signal is transmitted on all time domain resources corresponding to the set of time domain resources corresponding to the second time domain resource allocation of the SSB and the third time domain resource allocation of CORESET 0.

Optionally, the set of time domain resources corresponding to the first time domain resource allocation for the low-power signal may be a non-empty proper subset of the set of time domain resources corresponding to the second time domain resource allocation for the SSB, the time domain resources corresponding to the third time domain resource allocation for CORESET 0, and the time domain resources corresponding to the fourth time domain resource allocation for SIB1. That is, among the time domain resources corresponding to the set of time domain resources corresponding to the second time domain resource allocation for the SSB and the time domain resources corresponding to the third time domain resource allocation for CORESET 0, only some of the time domain resources are configured for transmission of the low-power signal.

In a possible implementation, the low power consumption signal may include a low power consumption synchronization signal, and the time domain resources of the low power consumption synchronization signal may be at least the same as at least part of the time domain resources corresponding to the second time domain resource allocation.

The low power synchronization signal (LP-SS) is at least used for the LP-WUR of the terminal device to perform coarse time synchronization and/or coarse frequency synchronization with the network device, so that the LP-WUR can receive the LP-WUS to wake up the MR. This application does not limit the name of the low power synchronization signal.

6 , the time domain resources of the LP-SS may be at least the same as at least a portion of the time domain resources corresponding to the second time domain resource allocation of the SSB.

Optionally, the time domain resources of the LP-SS may be the same as part of the time domain resources corresponding to the second time domain resource allocation of the SSB.

For example, in the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy some symbol positions of SSB, as shown in (6b) and (6f) in Figure 6 (this situation in mode 2 is not shown).

Optionally, the time domain resources of the LP-SS may be the same as the time domain resources corresponding to the second time domain resource allocation of the SSB.

For example, in the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the symbol position of SSB, as shown in (6a), (6c), and (6d) in Figure 6 (this situation in mode 3 is not shown).

Optionally, the time domain resources of the LP-SS may be at least the same as the time domain resources corresponding to the second time domain resource allocation of the SSB.

For example, in mode 2 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the symbol position of SSB as well as the symbol position of CORESET 0, as shown in (6e) in Figure 6.

In other words, in mode 1 and mode 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy at least part of the position of the SSB symbol; in mode 2, LP-SS can occupy at least part of the position of the SSB symbol and at least part of the position of the CORESET 0 symbol.

For example, the second time domain resource allocation of SSB can correspond to time domain resources of 4 symbols, and the third time domain resource allocation of CORESET 0 can correspond to time domain resources of 2 symbols. In Modes 1 and 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the time domain resources corresponding to any combination of 1 to 4 symbols of the 4 SSB symbols. In Mode 2 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the time domain resources corresponding to any combination of 1 to 6 symbols of the 4 SSB symbols and 2 CORESET 0 symbols, a total of 6 symbols (this application does not limit whether the symbols are continuous).

Furthermore, for the three multiplexing modes, LP-SS can correspond to beams one-to-one. That is, when certain SSBs are determined not to be transmitted, LP-SS is not transmitted on the corresponding time domain resources.

For multiplexing mode 1, LP-SS repetition detection can also be performed at the SIB1 location. Furthermore, the number of repetition checks and/or detection conditions can be configured. The configuration information can be pre-set or indicated by the master information block (MIB).

In a possible implementation, the low power consumption signal may include an LP-SS, and the time domain resources of the LP-SS may be at least the same as at least part of the time domain resources corresponding to the third time domain resource allocation.

7 , the time domain resources of the LP-SS may be at least the same as at least part of the time domain resources corresponding to the third time domain resource allocation of CORESET 0.

Optionally, the time domain resources of LP-SS may be the same as part of the time domain resources corresponding to the third time domain resource allocation of CORESET 0.

For example, in Mode 2 and Mode 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy some symbol positions of CORESET 0, as shown in (7c) in Figure 7 (this situation in Mode 2 is not shown).

Optionally, the time domain resources of LP-SS can be the same as the time domain resources corresponding to the third time domain resource allocation of CORESET 0.

For example, in Mode 2 and Mode 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the symbol position of CORESET 0, as shown in (7a) in Figure 7 (this situation in Mode 3 is not shown).

Optionally, the time domain resources of the LP-SS may be at least the same as the time domain resources corresponding to the third time domain resource allocation of CORESET 0.

For example, in Mode 2 and Mode 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy the symbol position of SSB as well as the symbol position of CORESET 0, as shown in (7b) in Figure 7 (this case in Mode 3 is not shown).

In other words, in mode 2 and mode 3 of the three multiplexing modes of SSB and CORESET 0, LP-SS can occupy at least part of the position of the symbol of CORESET 0 and at least part of the position of the symbol of SSB.

For example, the second time domain resource allocation for SSB can correspond to time domain resources of 4 symbols, and the third time domain resource allocation for CORESET 0 can correspond to time domain resources of 2 symbols. In Mode 2 of the three multiplexing modes for SSB and CORESET 0, LP-SS can occupy the time domain resources corresponding to any combination of 1 to 6 symbols from the total of 6 symbols, namely, 4 symbols of SSB and 2 symbols of CORESET 0. In Mode 3 of the three multiplexing modes for SSB and CORESET 0, since the symbols of CORESET 0 and SSB are aligned in the time domain, LP-SS can occupy the time domain resources corresponding to any combination of 1 to 4 symbols from the 4 symbols of SSB (this application does not limit whether the symbols are continuous).

In one possible implementation, the low-power signal also includes an LP-WUS, the frequency domain resources of the LP-WUS may be the same as the frequency domain resources of the LP-SS, and the time domain resources of the LP-WUS are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation of the low-power signal, excluding the time domain resources of the LP-SS.

LP-WUS may be other low-power signals as shown in FIG6 and FIG7. When the frequency domain resources of LP-WUS are the same as the frequency domain resources of LP-SS, as shown in (6a), (6b), (6d), (6f) in FIG6 and (7a) and (7c) in FIG7, LP-WUS and LP-SS may be configured in a time division multiplexing (TDM) manner, and LP-WUS may occupy part or all of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation of the low-power signal, excluding the time domain resources of LP-SS (this application does not limit whether the symbols are continuous).

In one possible implementation, the low-power signal also includes an LP-WUS, the frequency domain resources of the LP-WUS may be different from the frequency domain resources of the LP-SS, and the time domain resources of the LP-WUS are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation of the low-power signal, excluding the time domain resources of the LP-SS.

When the frequency domain resources of LP-WUS are different from the frequency domain resources of LP-SS (i.e., LP-WUS and LP-SS are configured in frequency division multiplexing (FDM)), LP-WUS can occupy part or all of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation of the low-power signal (this application does not limit whether the symbols are continuous).

Optionally, the time domain resources of the LP-WUS are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation of the low power signal, excluding the time domain resources of the LP-SS. That is, during the transmission of the LP-SS, the LP-WUS is not transmitted.

For mode 1 among the three multiplexing modes, the time domain resource configuration of LP-WUS also needs to meet the configuration of Type 0-PDCCH C-SS for mode 1 in 3GPP TS 38.213, so as to realize the transmission of LP-WUS under appropriate PDCCH monitoring timing and related configurations (such as monitoring period, monitoring window, etc.).

In a possible implementation, the low power consumption signal may include an LP-WUS, and the time domain resources of the LP-WUS may be the same as at least part of the time domain resources corresponding to the first time domain resource allocation.

Refer to FIG8 , which is an example diagram of time domain resource allocation of a low power consumption wake-up signal (LP-WUS) provided in an embodiment of the present application.

In the three multiplexing modes of SSB and CORESET 0, the time domain resources of the LP-WUS can be the same as at least part of the time domain resources corresponding to the first time domain resource allocation. In other words, the time domain resources of the LP-WUS can be a non-empty subset of the set of time domain resources corresponding to the first time domain resource allocation, for example, (8a) to (8f) in Figure 8. In addition, the time domain resources of the LP-WUS can be discontinuous, for example, (8b) and (8e) in Figure 8.

It is easy to understand that the set of time domain resources of LP-WUS can be the same as the set of time domain resources corresponding to the first time domain resource allocation. That is, in this case, all time domain resources corresponding to the first time domain resource allocation can be used for LP-WUS transmission.

In a possible implementation manner, the time domain resources of the LP-WUS are at least the same as at least a portion of the time domain resources corresponding to the second time domain resource allocation.

In the three multiplexing modes of SSB and CORESET 0, the time domain resources of the LP-WUS can be the same as at least part of the time domain resources corresponding to the second time domain resource allocation. In other words, the time domain resources of the LP-WUS can be a non-empty subset of the set of time domain resources corresponding to the second time domain resource allocation, for example, (8a), (8c), (8d), and (8f) in Figure 8. In addition, the time domain resources of the LP-WUS can be discontinuous, for example, (8e) in Figure 8.

It is easy to understand that when the time domain resources of the LP-WUS are a non-empty subset of the set of time domain resources corresponding to the second time domain resource allocation, the LP-WUS may correspond to the SSB.

In one possible implementation, the LP-WUS may be associated with a user equipment group (UE group), wherein the index of the user equipment group is associated with the index of the SSB corresponding to the time domain resources of the LP-WUS.

Specifically, the user equipment group may be a plurality of UEs grouped according to a specific standard.

Optionally, considering different locations of UEs, UEs with the same beam or related beams may be in one group, that is, the user equipment groups may be divided according to beams.

Optionally, UE groups may be divided according to the time slot structure type, and different parameter sets (numerologies) or services may be placed in different groups.

Optionally, UEs with different processing capabilities may be grouped according to supported bandwidth ranges.

This application does not limit the grouping method of user equipment groups.

The LP-WUS may be a paging message for a user equipment group. Since the LP-WUS may correspond to an SSB within an SSB burst set period (e.g., 20 ms), the LP-WUS may be configured for a specific user equipment group based on the SSB index. In other words, the SSB index may correspond to the user equipment group index. Based on the SSB index corresponding to the time domain resource of the LP-WUS, the LP-WUS may be configured as a paging message for the user equipment group having the corresponding user equipment group index.

In one possible implementation, one SSB may correspond to one user equipment group.

Optionally, the index of the SSB can be matched with the index of the user device group based on a hash function, and the correspondence between the index of the SSB and the index of the user device group can be updated according to the SSB burst set period (i.e., the beam scanning period), so that the user device group can traverse all beams.

Optionally, when the correspondence between the index of the SSB and the index of the user equipment group has been determined in the current beam scanning period, the correspondence between the index of the SSB in the next beam scanning period and the index of the user equipment group can be updated to Index _{_SSB} = (Index _{_UE group} + a) mod N _{_UE group} , where Index _{_SSB} is the index of the SSB, Index _{_UE group} is the index of the user equipment group in the current beam scanning period, N _{_UE group} is the number of groups of the user equipment group, and a can be any positive integer less than N _{_UE group} and coprime with N _{_UE group} , so that the user equipment group can traverse all beams.

In one possible implementation, multiple SSBs may correspond to one user equipment group.

Optionally, multiple SSBs in an SSB burst set period may correspond to one user equipment group, so that LP-WUS may be repeatedly sent to a specific user equipment group at multiple SSB time domain positions, or LP-WUS may be sent using longer time domain symbols.

In one possible implementation, an SSB burst set may be associated with a user equipment group, that is, all SSBs in an SSB burst set period may correspond to a specific user equipment group, so that within one SSB burst set period (e.g., 20 ms), the specific user equipment group may scan all beams.

Optionally, the starting position of the SSB burst set period can be the beginning of the period of connected mode discontinuous reception (CDRX) or extended/enhanced discontinuous reception (EDRX).

In one possible implementation, the first time domain resource allocation of the low power signal is also associated with the time domain resource allocation of a tracking reference signal (TRS). The method also includes: determining that a TRS is received from a network device; and determining the first time domain resource allocation of the low power signal based on the time domain resource allocation of the TRS.

Optionally, the symbol position of the LP-SS or the symbol position of the LP-WUS can be determined based on the symbol position of the TRS. For example, the symbol position of the LP-SS or the symbol position of the LP-WUS can be the same as the symbol position of the TRS, or separated by a predefined offset value.

In the method described in Figure 9, the first time domain resource allocation of the low-power signal determined by the terminal device is associated with the second time domain resource allocation of SSB and the third time domain resource allocation of CORESET 0. The low-power signal can be transmitted based on the time domain resources of SSB and CORESET 0, which can reduce the additional time domain resource overhead and reduce the system energy-saving gain loss.

Figure 10 is a flow chart of a communication processing method provided in an embodiment of the present application. The method execution subject shown in Figure 10 can be the terminal device and network device mentioned above. Alternatively, the method execution subject shown in Figure 10 can be a chip in a terminal device and a chip in a network device, which is not limited in the embodiment of the present application. Figure 10 uses the terminal device and network device as the execution subject of the method as an example.

S1001. The network device transmits indication information about the first time domain resource allocation of the low power consumption signal to the terminal device. Correspondingly, the terminal device receives the indication information about the first time domain resource allocation of the low power consumption signal from the network device.

It is easy to understand that step S1001 can refer to the description of the indication information of the first time domain resource allocation of the low power signal in the above step S401 on the network device and step S901 on the terminal device, and will not be repeated here.

Figure 11 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device 1100 shown in Figure 11 can be a terminal device, or a device in a terminal device, or a device that can be used in combination with a terminal device; or the communication device shown in Figure 11 can be a network device, or a device in a network device, or a device that can be used in combination with a network device. The communication device 1100 shown in Figure 11 may include a communication unit 1101 and a processing unit 1102. Specifically, the processing unit 1102 is used to process data, which may be data received by the communication unit 1101, and the processed data may also be sent by the communication unit 1101.

Specifically, the processing unit 1102 is configured to execute the data processing function of the terminal device or network device in the aforementioned method embodiment. For other possible implementations of the communication device, reference can be made to the description of the terminal device or network device functions in the method embodiment corresponding to FIG. 4 or FIG. 9 above, which will not be repeated here.

Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1200 can be a terminal device or network device in the above method embodiment, or can also be a chip, chip system, or processor that supports the terminal device or network device to implement the above method. This communication device can be used to implement the method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

The communication device 1200 may include one or more processors 1201. The processor 1201 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit (CPU). The baseband processor may be used to process communication protocols and communication data, while the CPU may be used to control the communication device (e.g., a base station, a baseband chip, a terminal, a terminal chip, a DU or a CU), execute software programs, and process software program data.

Optionally, the communication device 1200 may include one or more memories 1202, on which instructions 1204 may be stored. The instructions may be executed on the processor 1201, causing the communication device 1200 to perform the method described in the above method embodiment. Optionally, the memory 1202 may also store data. The processor 1201 and memory 1202 may be provided separately or integrated together.

Optionally, the communication device 1200 may further include a transceiver 1205 and an antenna 1206. The transceiver 1205 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, and is configured to implement transceiver functions. The transceiver 1205 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, and is configured to implement a transmitting function. The processing unit 1102 shown in FIG11 may be the processor 1201. The communication unit 1101 may be the transceiver 1205.

In another possible design, processor 1201 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or the transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

In another possible design, processor 1201 may optionally store instructions 1203. Instructions 1203, when executed on processor 1201, may cause communication device 1200 to perform the method described in the above method embodiment. Instructions 1203 may be fixed in processor 1201. In this case, processor 1201 may be implemented by hardware.

The communication device described in the above embodiments may be a terminal device or a network device, but the scope of the communication device described in the embodiments of the present application is not limited thereto, and the structure of the communication device may not be limited to FIG12. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

(1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

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

(3) ASIC, such as modem (MSM);

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

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

(6)Others, etc.

In the case where the communication device can be a chip or a chip system, please refer to the chip structure diagram shown in Figure 13. The chip 1300 shown in Figure 13 includes a processor 1301 and an interface 1302. Optionally, it may also include a memory 1303. The number of processors 1301 can be one or more, and the number of interfaces 1302 can be multiple.

For the case where the chip is used to implement a terminal device or a network device in the embodiments of the present application:

The interface 1302 is used to receive or output signals;

The processor 1301 is configured to execute data processing operations of a terminal device or a network device.

It is understandable that some optional features in the embodiments of the present application may, in certain scenarios, be implemented independently without relying on other features, such as the solution on which they are currently based, to solve corresponding technical problems and achieve corresponding effects. They may also be combined with other features in certain scenarios as needed. Accordingly, the communication device provided in the embodiments of the present application may also implement these features or functions accordingly, which will not be described in detail here.

It should be understood that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

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

The present application also provides a computer-readable medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a communication device, the functions of any of the above method embodiments are implemented.

The present application also provides a computer program product including instructions, which enables a computer to implement the functions of any of the above method embodiments when the computer reads and executes the computer program product.

The present application provides a communication system, which includes a terminal device and a network device; wherein the terminal device is used to execute the method executed by the terminal device in the above embodiment, and the network device is used to execute the method executed by the network device in the above embodiment.

In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain operations can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

The descriptions of the various embodiments provided in this application can refer to each other. The descriptions of each embodiment have their own focus. For parts not described in detail in a particular embodiment, please refer to the relevant descriptions of other embodiments. For the convenience and brevity of description, for example, the functions and operations performed by the various devices and equipment provided in the embodiments of this application can refer to the relevant descriptions of the method embodiments of this application. The various method embodiments and the various device embodiments can also refer to, be combined with, or quote each other.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims (30)

A communication processing method, characterized in that the method comprises: Determine a first time domain resource allocation for a low power signal, wherein the first time domain resource allocation for the low power signal is associated with a second time domain resource allocation for a synchronization signal block and a third time domain resource allocation for a control resource set zero CORESET 0. The method according to claim 1, further comprising: Receiving indication information associated with the second time domain resource allocation of the synchronization signal block and the third time domain resource allocation of the CORESET 0 from a network device to determine the first time domain resource allocation of the low power consumption signal, wherein at least a portion of the indication information is allowed to at least partially indicate the first time domain resource allocation of the low power consumption signal, and the frequency domain resources of the low power consumption signal are different from the frequency domain resources of the synchronization signal block and the CORESET 0. The method according to claim 1 or 2 is characterized in that the CORESET 0 scheduling indicates a system information block, the system information block has a fourth time domain resource allocation, and the set of time domain resources corresponding to the first time domain resource allocation is a subset of the set of time domain resources corresponding to the second time domain resource allocation, the time domain resources corresponding to the third time domain resource allocation, and the time domain resources corresponding to the fourth time domain resource allocation. The method according to claim 3 is characterized in that the set of time domain resources corresponding to the first time domain resource allocation is a subset of the set of time domain resources corresponding to the second time domain resource allocation and the set of time domain resources corresponding to the third time domain resource allocation. The method according to claim 3 is characterized in that the low-power signal includes a low-power synchronization signal, and the time domain resources of the low-power synchronization signal are at least the same as at least part of the time domain resources corresponding to the second time domain resource allocation. The method according to claim 3 is characterized in that the low-power signal includes a low-power synchronization signal, and the time domain resources of the low-power synchronization signal are at least the same as at least part of the time domain resources corresponding to the third time domain resource allocation. The method according to claim 5 or 6 is characterized in that the low-power signal also includes a low-power wake-up signal, the frequency domain resources of the low-power wake-up signal are the same as the frequency domain resources of the low-power synchronization signal, and the time domain resources of the low-power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation, excluding the time domain resources of the low-power synchronization signal. The method according to claim 5 or 6 is characterized in that the low-power signal also includes a low-power wake-up signal, the frequency domain resources of the low-power wake-up signal are different from the frequency domain resources of the low-power synchronization signal, and the time domain resources of the low-power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation. The method according to claim 8 is characterized in that the time domain resources of the low-power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation, excluding the time domain resources of the low-power synchronization signal. The method according to claim 3 is characterized in that the low-power signal includes a low-power wake-up signal, and the time domain resources of the low-power wake-up signal are the same as at least part of the time domain resources corresponding to the first time domain resource allocation. The method according to claim 10, characterized in that the time domain resources of the low-power wake-up signal are the same as at least part of the time domain resources corresponding to the second time domain resource allocation. The method according to claim 11 is characterized in that the low-power wake-up signal is associated with a user equipment group, wherein the index of the user equipment group is associated with the index of the synchronization signal block corresponding to the time domain resource of the low-power wake-up signal. The method according to claim 1, wherein the first time domain resource allocation of the low-power signal is further associated with the time domain resource allocation of a tracking reference signal, and the method further comprises: determining receipt of a tracking reference signal from the network device; The first time domain resource allocation of the low power consumption signal is determined based on the time domain resource allocation of the tracking reference signal. A communication processing method, characterized in that the method comprises: Determine a first time domain resource allocation for a low power signal, wherein the first time domain resource allocation for the low power signal is associated with a second time domain resource allocation for a synchronization signal block and a third time domain resource allocation for a control resource set zero CORESET 0. The method according to claim 14, further comprising: Communicate indication information associated with the second time domain resource allocation of the synchronization signal block and the third time domain resource allocation of the CORESET 0 to a terminal device, wherein at least a portion of the indication information is allowed to at least partially indicate the first time domain resource allocation of the low power signal, and the frequency domain resources of the low power signal are different from the frequency domain resources of the synchronization signal block and the CORESET 0. The method according to claim 14 or 15 is characterized in that the CORESET 0 scheduling indicates a system information block, the system information block has a fourth time domain resource allocation, and the set of time domain resources corresponding to the first time domain resource allocation is a subset of the set of time domain resources corresponding to the second time domain resource allocation, the time domain resources corresponding to the third time domain resource allocation, and the time domain resources corresponding to the fourth time domain resource allocation. The method according to claim 16 is characterized in that the set of time domain resources corresponding to the first time domain resource allocation is a subset of the set of time domain resources corresponding to the second time domain resource allocation and the set of time domain resources corresponding to the third time domain resource allocation. The method according to claim 16 is characterized in that the low-power signal includes a low-power synchronization signal, and the time domain resources of the low-power synchronization signal are at least the same as at least part of the time domain resources corresponding to the second time domain resource allocation. The method according to claim 16 is characterized in that the low-power signal includes a low-power synchronization signal, and the time domain resources of the low-power synchronization signal are at least the same as at least part of the time domain resources corresponding to the third time domain resource allocation. The method according to claim 18 or 19 is characterized in that the low-power signal also includes a low-power wake-up signal, the frequency domain resources of the low-power wake-up signal are the same as the frequency domain resources of the low-power synchronization signal, and the time domain resources of the low-power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation, excluding the time domain resources of the low-power synchronization signal. The method according to claim 18 or 19 is characterized in that the low-power signal also includes a low-power wake-up signal, the frequency domain resources of the low-power wake-up signal are different from the frequency domain resources of the low-power synchronization signal, and the time domain resources of the low-power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation. The method according to claim 21 is characterized in that the time domain resources of the low-power wake-up signal are at least part of the time domain resources in the set of time domain resources corresponding to the first time domain resource allocation, excluding the time domain resources of the low-power synchronization signal. The method according to claim 16, wherein the low-power signal includes a low-power wake-up signal, and the time domain resources of the low-power wake-up signal are the same as at least part of the time domain resources corresponding to the first time domain resource allocation. The method according to claim 23 is characterized in that the time domain resources of the low-power wake-up signal are the same as at least part of the time domain resources corresponding to the second time domain resource allocation. The method according to claim 24 is characterized in that the low-power wake-up signal is associated with a user equipment group, wherein the index of the user equipment group is associated with the index of the synchronization signal block corresponding to the time domain resource of the low-power wake-up signal. The method according to claim 14, wherein the first time domain resource allocation of the low power consumption signal is further associated with the time domain resource allocation of a tracking reference signal, and the method further comprises: The tracking reference signal is sent to the terminal device, so that the terminal device determines the first time domain resource allocation of the low power consumption signal based on the time domain resource allocation of the tracking reference signal. A communication device, characterized by comprising a unit for executing the method according to any one of claims 1 to 13, or comprising a unit for executing the method according to any one of claims 14 to 26. A communication device, characterized in that it includes a processor and a memory, the processor and the memory are coupled, the processor is used to implement the method according to any one of claims 1-13, or the processor is used to implement the method according to any one of claims 14-26. A chip, characterized in that it includes a processor and an interface, the processor and the interface are coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions to enable the method described in any one of claims 1 to 13 to be executed, or to enable the method described in any one of claims 14 to 26 to be executed. A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are called by the computer, the computer executes the method described in any one of claims 1 to 13, or the method described in any one of claims 14 to 26.