A communication method, apparatus, and system

Abstract

The application discloses a communication method, device and system, relates to the technical field of communication, and can enable a UE to determine whether to perform PDCCH monitoring based on a target mode, reduce UE response delay, and thereby improve communication efficiency. The communication method comprises the following steps: a UE receives at least one mode configured by an access network device, different modes are used to specify different conflict processing modes when PDCCH skipping occurs in a waiting period corresponding to a UE IRI. Different modes are suitable for different state information. The waiting period corresponding to the UE IRI comprises a period from sending the UE IRI to waiting for DCI sent by the access network device. The UE acquires state information of the UE, and in response to detecting that it is necessary to trigger CSI reporting, sends, based on configuration information and the state information, a first UE IRI to the access network device, wherein the first UE IRI is used to indicate a target mode corresponding to the state information of the UE.

Description

Technical Field

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

[0002] In the context of the 3rd Generation Partnership Project (3GPP) for fifth-generation mobile communications, rd In the 3GPP 5G standard, regarding scenarios where a Physical Downlink Control Channel (PDCCH) skips during the waiting period corresponding to a UE Initiated Report Indicator (UEIRI), on the one hand, during the waiting period corresponding to the UEIRI, the user equipment (UE) needs to wait for the network to send downlink control information (DCI) and perform PDCCH monitoring. On the other hand, if a PDCCH skip also occurs during the waiting period corresponding to the UEIRI, the PDCCH skip may instruct the UE not to perform PDCCH monitoring during that waiting period. This can cause a conflict regarding whether the UE should perform PDCCH monitoring.

[0003] In this situation, there is no clear regulation on how the UE should effectively respond to the aforementioned conflict. This can lead to a delay in the UE's response, potentially preventing it from capturing the DCI and thus from reporting channel state information (CSI), thereby affecting communication efficiency. Summary of the Invention

[0004] This application provides a communication method, apparatus, and system. The UE can determine a target mode among at least one mode based on acquired status information and at least one mode pre-configured by the access network device, thereby determining whether to perform PDCCH monitoring, reducing UE response latency, and thus improving communication efficiency. The access network device can also determine whether to send DCI to the UE based on the target mode determined by the UE, saving signaling overhead and power consumption, thereby improving communication efficiency.

[0005] Firstly, a communication method is provided, which can be executed by a UE, or by a component configured in the UE (such as a circuit, chip, or chip system), or by a logic module or software capable of implementing all or part of the UE's functions. This application does not limit this. The following description uses a UE as an example.

[0006] The method includes: receiving configuration information sent by an access network device for configuring at least one mode, wherein different modes are used to specify different conflict handling methods when a PDCCH skip occurs during the waiting period corresponding to a UEIRI; acquiring UE status information; and in response to detecting a report that needs to trigger CSI, sending a report for triggering CSI and a first UEIRI indicating a target mode to the access network device based on the configuration information and status information, wherein the target mode is one of the at least one modes corresponding to the UE status information.

[0007] Different modes apply to different status information. UEIRI is used to indicate that the UE needs to trigger CSI reporting. The waiting period corresponding to UEIRI includes the period from sending UEIRI to waiting for the access network device to send DCI.

[0008] In this application, the mode can also be described as a conflict handling mode, or a UEERI and PDCCH skip coexistence mode, etc.

[0009] The aforementioned communication method is applied to the UE. The access network device can pre-configure a conflict handling method for PDCCH skipping during the waiting period corresponding to the UEIRI. This allows the UE to determine a target mode corresponding to the state information based on the acquired state information and at least one mode configured by the access network device, and then send the target mode and the first UEIRI to the access network device. In this way, on the one hand, the access network device can determine whether to send DCI to the UE based on the target mode, avoiding blindly sending DCI to the UE, saving signaling overhead and power consumption, thereby improving communication efficiency. On the other hand, the UE can also determine whether to perform PDCCH monitoring based on the target mode, reducing UE response latency and avoiding the inability to capture DCI, thus preventing the inability to complete CSI reporting, thereby improving communication efficiency.

[0010] In one possible implementation of the first aspect, the status information includes at least one of the following: device type, service type, power consumption status, blind detection capability constraints, mobility status, link change status, or beam reporting requirements.

[0011] This implementation provides multi-dimensional state information, which can improve the accuracy of determining the target pattern.

[0012] In one possible implementation of the first aspect, at least one mode includes at least one of the following: a first mode; the first mode specifies that PDCCH skipping is fully performed during the waiting period corresponding to the UEERI; a second mode; the second mode specifies that a first number of PDCCH skips are allowed to be performed during the waiting period corresponding to the UEERI; a third mode; the third mode specifies that a second number of PDCCH skips are allowed to be performed during the waiting period corresponding to the UEERI, wherein the second number is less than the first number; and a fourth mode; the fourth mode specifies that PDCCH skipping is not performed during the waiting period corresponding to the UEERI.

[0013] This implementation offers multiple modes, improving the flexibility and diversity of decision-making. It also allows for adaptation to different situations, selecting the appropriate target mode based on varying state information, thereby achieving a balance between power consumption and reliability.

[0014] In one possible implementation of the first aspect, the configuration information is also used to configure the mode parameters corresponding to each mode.

[0015] This implementation extends the functionality of configuration information. By pre-configuring the mode parameters corresponding to each mode through configuration information, the UE can skip or not skip PDCCH monitoring based on the target mode and the corresponding mode parameters, thus saving signaling overhead.

[0016] In one possible implementation of the first aspect, the mode parameters include at least one of the following: a first threshold related to the effective number of PDCCH monitoring; a second threshold related to the number of consecutive unserviceable PDCCH monitoring; the maximum duration of UEIRI transmission; the maximum number of UEIRI transmissions; a preset duration after the maximum number of UEIRI transmissions is reached; or, the minimum transmission interval between two adjacent UEIRI transmissions.

[0017] In this implementation, the mode parameters are characterized by multi-dimensional performance indicators, allowing for flexible and diverse designs.

[0018] In one possible implementation of the first aspect, the method further includes: during the waiting period corresponding to the first UEIRI, if the UE is in a PDCCH skipping state, skipping or not skipping PDCCH monitoring based on the target mode.

[0019] This implementation achieves a balance between power consumption and reliability. It also reduces UE response latency, preventing the inability to capture DCI and thus the inability to report CSI, thereby improving communication efficiency.

[0020] In one possible implementation of the first aspect, skipping or not skipping PDCCH monitoring based on a target mode includes: if the target mode is a first mode, skipping PDCCH monitoring and not performing PDCCH monitoring associated with the first UEERI; or, if the target mode is a second mode, skipping a first number of PDCCH monitoring and partially performing PDCCH monitoring associated with the first UEERI; or, if the target mode is a third mode, skipping a second number of PDCCH monitoring and partially performing PDCCH monitoring associated with the first UEERI; or, if the target mode is a fourth mode, not skipping PDCCH monitoring and fully performing PDCCH monitoring associated with the first UEERI.

[0021] In this implementation, different target modes execute different PDCCH monitoring, achieving a balance between power consumption and reliability. It also reduces UE response latency, avoids the inability to capture DCI, and consequently prevents the inability to report CSI, thereby improving communication efficiency.

[0022] In one possible implementation of the first aspect, if the target mode is a second mode, a third mode, or a fourth mode, the method further includes receiving a DCI sent by the access network device before skipping or not skipping PDCCH monitoring based on the target mode.

[0023] In this implementation, the access network device can determine whether to send DCI to the UE based on the target mode, avoiding blindly sending DCI to the UE or not sending DCI to the UE, saving signaling overhead and power consumption, thereby improving communication efficiency.

[0024] In one possible implementation of the first aspect, the method further includes: obtaining the number of valid monitoring sessions for PDCCH monitoring; and determining that the PDCCH monitoring associated with the first UEIRI has failed if no DCI is detected during the time period from the start of PDCCH monitoring until the number of valid monitoring sessions is greater than the threshold for the first time.

[0025] In this implementation, the maximum number of effective PDCCH monitoring sessions can be limited to avoid unrestrained PDCCH monitoring and the occasional failure of PDCCH monitoring associated with a single UEIRI, thereby improving the accuracy of the judgment.

[0026] In one possible implementation of the first aspect, the method further includes: obtaining the number of consecutive unserviceable times monitored by the PDCCH; and determining that the PDCCH monitoring associated with the first UEIRI has failed in response to the number of consecutive unserviceable times being greater than a second threshold.

[0027] In this implementation, the maximum number of consecutive unserviceable events monitored by PDCCH can be limited, thereby avoiding the sporadic failure of PDCCH monitoring associated with a single UEIRI and improving the accuracy of the judgment.

[0028] In one possible implementation of the first aspect, the method further includes: in response to sending a first UEIRI, starting a first timer; in response to the runtime of the first timer being greater than a maximum duration, determining that the PDCCH monitoring associated with the first UEIRI has failed.

[0029] In this implementation method, the accuracy of judgment can be improved by limiting the effective duration of PDCCH monitoring, avoiding prolonged PDCCH monitoring and the occasional failure of PDCCH monitoring associated with a single UEIRI.

[0030] In one possible implementation of the first aspect, if the PDCCH monitoring associated with the first UEIRI fails, the method further includes: retransmitting the first UEIRI if the number of times the first UEIRI is sent is less than the maximum number of times it is sent; or, if the number of times the first UEIRI is sent is greater than or equal to the maximum number of times it is sent, the UE exits the reporting of the triggered CSI after a preset time.

[0031] In this implementation, sending the UEIRI multiple times avoids the sporadic failure of PDCCH monitoring associated with the UEIRI, improving the accuracy of the judgment. Furthermore, when the number of UEIRI transmissions exceeds or equals the maximum transmission count, a fallback strategy is executed, causing the UE to exit and trigger CSI reporting. This avoids repeatedly retransmitting the UEIRI, entering an endless loop, wasting power, and thus reducing communication efficiency.

[0032] In one possible implementation of the first aspect, retransmitting the first UEIRI includes: starting a second timer in response to a PDCCH monitoring failure associated with the first UEIRI; retransmitting the first UEIRI after the second timer has finished running; the running length of the second timer is the minimum transmission interval between two consecutive transmissions of the UEIRI.

[0033] This implementation method can minimize latency and improve communication efficiency within the time limit of resources.

[0034] In one possible implementation of the first aspect, when the first UEIRI is being transmitted for the first time, the method further includes: initializing mode parameters in response to transmitting the first UEIRI.

[0035] In this implementation, historical data can be cleared, avoiding coupling with historical data and improving communication efficiency.

[0036] In one possible implementation of the first aspect, the method further includes: incrementing the number of times the first UEIRI has been transmitted by 1 each time the first UEIRI is successfully transmitted; and setting the number of times the first UEIRI has been transmitted to 0 if the PDCCH monitoring is successful.

[0037] In this implementation, by counting the number of times the first UEIRI has been sent and resetting the number of times the first UEIRI has been sent when the DCCH monitoring is successful, the accuracy can be improved and the correct reset of the number of times the first UEIRI has been sent can be guaranteed.

[0038] In one possible implementation of the first aspect, not skipping PDCCH monitoring includes: not skipping PDCCH monitoring on the serving cell associated with the first UEIRI; and performing PDCCH skipping on cells other than the serving cell associated with the first UEIRI in the UE's target serving cells.

[0039] This implementation method enables real-time and efficient scheduling, saving UE power consumption.

[0040] Secondly, a communication method is provided, which can be executed by an access network device, or by a component (such as a circuit, chip, or chip system) configured in the access network device, or by a logic module or software capable of implementing all or part of the functions of the access network device. This application does not limit this approach. The following description uses an access network device as an example.

[0041] The method includes: sending configuration information for at least one mode to the UE; different modes are used to configure different conflict handling methods when a PDCCH skip occurs during the waiting period corresponding to a UEIRI. The method also includes receiving a report from the UE to trigger CSI and a first UEIRI indicating a target mode corresponding to the UE's state information in at least one mode. The target mode is determined by the UE in response to detecting a report requiring CSI triggering, based on the configuration information and the state information obtained by the UE.

[0042] Different modes apply to different status information. UEIRI is used to indicate that the UE needs to trigger CSI reporting. The waiting period corresponding to UEIRI includes the period from sending UEIRI to waiting for the access network device to send DCI.

[0043] The aforementioned communication method is applied to access network equipment. The access network equipment can pre-configure a conflict handling method for PDCCH skipping during the waiting period corresponding to the UEIRI. This allows the UE to determine a target mode corresponding to the state information based on the acquired state information and at least one mode configured by the access network equipment, and then send the target mode and the first UEIRI to the access network equipment. In this way, on the one hand, the access network equipment can determine whether to send DCI to the UE based on the target mode, avoiding blindly sending DCI to the UE, saving signaling overhead and power consumption, thereby improving communication efficiency. On the other hand, the UE can also determine whether to perform PDCCH monitoring based on the target mode, reducing UE response latency and avoiding the inability to capture DCI, thus preventing the inability to complete CSI reporting, thereby improving communication efficiency.

[0044] In one possible implementation of the second aspect, the status information includes at least one of the following: device type, service type, power consumption status, blind detection capability constraints, mobility status, link change status, or beam reporting requirements.

[0045] In one possible implementation of the second aspect, at least one mode includes at least one of the following: a first mode; the first mode specifies that PDCCH skipping is fully performed during the waiting period corresponding to the UEERI; a second mode; the second mode specifies that a first number of PDCCH skips are allowed to be performed during the waiting period corresponding to the UEERI; a third mode; the third mode specifies that a second number of PDCCH skips are allowed to be performed during the waiting period corresponding to the UEERI, wherein the second number is less than the first number; and a fourth mode; the fourth mode specifies that PDCCH skipping is not performed during the waiting period corresponding to the UEERI.

[0046] In one possible implementation of the second aspect, the method further includes: determining whether to send DCI to the UE based on the target mode.

[0047] In one possible implementation of the second aspect, determining whether to send DCI to the UE based on the target mode includes: not sending DCI to the UE when the target mode is the first mode; and sending DCI to the UE when the target mode is the second, third, or fourth mode.

[0048] In one possible implementation of the second aspect, the configuration information is also used to configure the mode parameters corresponding to each mode.

[0049] In one possible implementation of the second aspect, the mode parameters include at least one of the following: a first threshold related to the effective number of PDCCH monitoring; a second threshold related to the number of consecutive unserviceable PDCCH monitoring; the maximum duration of UEIRI transmission; the maximum number of UEIRI transmissions; a preset duration after the maximum number of UEIRI transmissions is reached; or, the minimum transmission interval between two adjacent UEIRI transmissions.

[0050] The second aspect is the implementation on the access network equipment side, which corresponds to the first aspect. The explanations, supplements, and descriptions of the beneficial effects of the first aspect also apply to the second aspect, and will not be repeated here.

[0051] Thirdly, a communication device is provided, the communication device including at least one processor coupled to a memory storing a program or instructions; the processor is configured to execute the program or instructions such that the communication device is configured to perform a communication method as described in the first aspect and any embodiment thereof, or to perform a communication method as described in the second aspect and any embodiment thereof.

[0052] The third aspect is the implementation on the device side, which corresponds to the first and second aspects. The explanations, supplements, and descriptions of the beneficial effects of the first and second aspects also apply to the third aspect, and will not be repeated here.

[0053] Fourthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform a communication method as described in the first aspect and any embodiment thereof, or to perform a communication method as described in the second aspect and any embodiment thereof.

[0054] Fifthly, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform a communication method as described in the first aspect and any embodiment thereof, or to perform a communication method as described in the second aspect and any embodiment thereof.

[0055] In a sixth aspect, a communication system is provided, including the communication device as described in the third aspect.

[0056] In a seventh aspect, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, such that a communication method as described in the first aspect and any embodiment thereof, or a communication method as described in the second aspect and any embodiment thereof, is executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0057] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0058] The technical effects of the design methods in the third, fourth, fifth, sixth, and seventh aspects can be found in the technical effects of the different design methods in the first or second aspects, and will not be repeated here. Attached Figure Description

[0059] Figure 1 This application provides a schematic diagram of the architecture of a wireless communication system. Figure 2 This application provides a schematic diagram of the structure of a terminal device and an access network device according to an embodiment of the present application. Figure 3 A flowchart illustrating a communication method provided in an embodiment of this application; Figure 4 A flowchart illustrating another communication method provided in an embodiment of this application; Figure 5 A schematic diagram of a communication device provided in an embodiment of this application; Figure 6 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0060] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0061] First, some concepts involved in this application will be described.

[0062] The terms "first" and "second" used in the embodiments of this application are only used to distinguish features of the same type and should not be construed as indicating relative importance, quantity, order, etc.

[0063] The terms "exemplary" or "for example" used in the embodiments of this application are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0064] The technical solutions provided in this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, new radio access technology (NR), future communication systems, 5G Advanced communication systems, 6th generation (6G) mobile communication systems, or 6th generation radio access technology (6GR). Among these, 5G or 6G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of these applications. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technologies can be used in the systems and radio technologies mentioned above, as well as in other systems and radio technologies.

[0065] Appendix Figure 1 This is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application. The wireless communication system 100 may include an access network device, such as an appendix. Figure 1 At least one access network device 110 is shown. The wireless communication system 100 may also include a UE, such as an attached… Figure 1 The UE 120 shown is an example. Access network device 110 and UE 120 can communicate via a wireless link. Optionally, the wireless communication system 100 may further include multiple access network devices 110 and multiple UEs 120.

[0066] The access network equipment in this application is sometimes also referred to as an access node. Access network equipment has wireless transceiver capabilities for communicating with terminals. Access network equipment includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules of access network equipment in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units capable of implementing some of the functions of a base station. Access network equipment can be a macro base station, micro base station, indoor station, relay node, donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, access network equipment can also be a server, wearable device, or vehicle-mounted equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network devices in a communication system can be base stations of the same type or different types. Base stations can communicate with terminals directly or via relay stations. Terminals can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network devices. In this application, access network devices are referred to simply as network devices.

[0067] In this application, the apparatus for implementing the functions of the access network device can be the access network device itself, or it can be any apparatus capable of supporting the access network device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the access network device. In the technical solution provided in this application, the use of the access network device as an example to illustrate the technical solution provided in this application is described.

[0068] The UE in this application can be a wireless UE capable of receiving scheduling and instruction information from access network equipment. A wireless UE can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, a UE can communicate with one or more core networks or the Internet via a radio access network (RAN). A UE can also be referred to as a terminal, user equipment, mobile station, mobile terminal, etc. UEs can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the UE.

[0069] In this application, the device for implementing the UE's functions can be the UE itself, or any device capable of supporting the UE in implementing those functions, such as a processor, circuit, chip, or chip system. This device can be installed in the UE or connected to and used with the UE. In the technical solution provided in this application, the UE is used as an example to illustrate the technical solution provided in this application.

[0070] Access network devices and UEs can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on airplanes, balloons, and satellites. This application does not limit the application scenarios of the access network devices and UEs. Access network devices and UEs can be deployed in the same or different scenarios. For example, access network devices and UEs can be deployed simultaneously on land; or, access network devices can be deployed on land and UEs can be deployed on water, etc., and so on.

[0071] In practical applications, multiple access network devices can collaborate to assist the UE in achieving wireless access, with each device implementing a portion of the base station's functions. For example, access network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0072] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.

[0073] Figure 2 This is a schematic diagram of the structure of a UE and an access network device provided in an embodiment of this application. The UE 120 includes a first processor 121, a first memory 122, and a first transceiver 123.

[0074] The first processor 121 may include one or more processing units, such as: a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a microcontroller unit (MCU), a programmable logic device (PLD), an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0075] The first memory 122 can be volatile memory or non-volatile memory, or it can include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM).

[0076] The first memory 122 can exist independently and be connected to the first processor 121 via a bus. Alternatively, the first memory 122 can be integrated with the first processor 121. The first memory 122 stores application code that executes the scheme of this application, and its execution is controlled by the first processor 121. The first processor 121 executes the computer program instructions stored in the first memory 122, thereby performing various functional applications and data processing of the UE, such as implementing the sensing method described in the embodiments of this application.

[0077] The first processor 121 and the first transceiver 123 are connected via a bus. The first transceiver 123 can be any transceiver-like device used for communication with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. The first transceiver 123 includes a transmitter Tx and a receiver Rx.

[0078] Optionally, in this embodiment, the first transceiver 123 may include the RF link corresponding to SCell and the RF link corresponding to SpCell.

[0079] The access network device 110 includes a second processor 111, a second memory 112, and a second transceiver 113. The second processor 111 executes computer program instructions stored in the second memory 112, thereby performing various functional applications and data processing of the access network device 110, such as implementing the communication method described in the embodiments of this application. The functions of the second processor 111 are described with reference to the first processor 121, the functions of the second memory 112 are described with reference to the first memory 122, and the functions of the second transceiver 113 are described with reference to the first transceiver 123, and will not be repeated here.

[0080] To facilitate understanding of the embodiments of this application, the terminology used in this application is first briefly explained. Optionally, the explanation of some terms can also refer to the explanations in the 3rd Generation Partnership Project (3GPP) standard protocol. It should be understood that the technical terms in this application are only examples and not limitations. For example, as technology evolves, technical terms may also change; where the technical meaning remains the same, other technical terms should also apply to this application.

[0081] 1. UEIRI The UE information reporting indication (UEIRI) is used by the UE to report scheduling requests (SRs) or other related information to the network.

[0082] For example, for beam reporting initiated by the UE in mode A, when the UE detects the need to report channel state information (CSI), it sends a UEIRI (also described as a positive UEIRI) to the network via the physical uplink control channel (PUCCH). The UEIRI indicates that the UE needs to trigger beam reporting / CSI, and the positive UEIRI indicates that the UE actually needs to trigger beam reporting / CSI. After receiving the UEIRI from the UE, the network sends downlink control information (DCI) carrying the CSI request to the UE via the physical downlink control channel (PDCCH), such as a DCI in format 0_1 ​​(also described as DCI format 0_1) or DCI in format 0_2 (also described as DCI format 0_2), to trigger the UE to send CSI / beam reporting on the physical uplink shared channel (PUSCH).

[0083] 2. Waiting period corresponding to UEIRI The waiting period corresponding to UEIRI refers to the period from sending UEIRI to waiting for the DCI sent by the network side.

[0084] 3. PDCCH skipped PDCCH skipping (also described as PDCCH monitoring skipping or PDCCH skipping) is used to make the UE skip PDCCH monitoring occasions (also described as PDCCH monitoring occasions) for a specific duration or for a specific search space group. In other words, it makes the UE stop monitoring PDCCH for a specific duration or for a specific search space group, thereby saving power by reducing unnecessary monitoring.

[0085] 4. DCI DCI refers to a series of commands issued by the network to the UE. For example, the network generates a DCI command and sends it to the UE. After receiving the DCI command, the UE executes the corresponding operation indicated by the DCI command.

[0086] 5. UCI Uplink control information (UCI) refers to control signals sent by the UE to the network side. Examples include hybrid automatic repeat request acknowledgment (HARQ-ACK), CSI, or scheduling request (SR).

[0087] In the 3GPP 5G standard, if a PDCCH skips during the waiting period corresponding to the UE's IRI, it will cause a conflict regarding whether the UE should perform PDCCH monitoring. In this case, there is no clear specification on how the UE should effectively respond to this conflict. This can lead to a delayed UE response, potentially preventing the UE from capturing the DCI and thus failing to report the CSI, thereby affecting communication efficiency.

[0088] In view of this, this application provides a communication method, apparatus, and system. The access network device can pre-configure at least one conflict handling method when a PDCCH skip occurs during the waiting period corresponding to the UEIRI. Each conflict handling method corresponds to a mode, enabling the UE to determine a target mode corresponding to the state information based on acquired state information and at least one mode configured by the access network device, and then send the target mode and a first UEIRI to the access network device. Thus, on the one hand, the access network device can determine whether to send a DCI to the UE based on the target mode, avoiding blindly sending DCIs to the UE, saving signaling overhead and power consumption, thereby improving communication efficiency. On the other hand, the UE can also determine whether to perform PDCCH monitoring based on the target mode, reducing UE response latency and avoiding the inability to capture DCIs, thus preventing the inability to complete CSI reporting, thereby improving communication efficiency.

[0089] The following detailed explanation of the solution provided in this application, in conjunction with the corresponding flowcharts, illustrates the method. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., UE, access network equipment) as examples of the execution entities for this interactive illustration, but this application does not limit the execution entities of the interactive illustrations. For example, the devices in the illustrative flowcharts (e.g., UE, access network equipment) can also be chips, chip systems, or processors that support the implementation of this method on the device, or logical modules or software capable of implementing all or part of the device's functions.

[0090] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0091] Appendix Figure 3This is a flowchart illustrating a communication method provided in an embodiment of this application. It can be understood that the UE involved in this communication method may be an attached device. Figure 1 The UE in this context can also refer to the device within the UE (such as a processor, chip, or chip system). The access network equipment involved in this communication method can be an auxiliary device. Figure 1 Access network equipment can also refer to devices within access network equipment (such as processors, chips, or chip systems). For example, see attached... Figure 3 As shown, the communication method 300 includes the following steps S301-S305: S301. The access network device sends configuration information to the UE.

[0092] Accordingly, the UE receives configuration information sent by the access network device.

[0093] In this application, the configuration information may also be described as conflict handling configuration information, UEERI and PDCCH skipping coexistence configuration information, or UEERI-skipping conflict handling configuration information, etc., without limitation.

[0094] The configuration information is used to configure at least one mode, which can also be described as a conflict handling mode, a UEIRI and PDCCH skipping coexistence mode, or a UEIRI-skipping conflict handling mode, etc. Different modes specify / define different conflict handling methods (also described as UEIRI-skipping conflict handling methods) when a PDCCH skip occurs during the waiting period corresponding to the UEIRI. Different modes are applicable to different status information. The UEIRI is used to indicate that the UE needs to trigger CSI reporting. The waiting period corresponding to the UEIRI includes the period from sending the UEIRI to waiting for the DCI sent by the access network equipment. The UEIRI and its corresponding waiting period can refer to existing technologies, which will not be elaborated here.

[0095] Optionally, at least one mode includes at least one of the following: First mode: can also be described as forced PDCCH skip mode or forced skipping mode or forced skipping mode, etc., where the first mode is used to specify that PDCCH skipping is fully performed during the waiting period corresponding to UEIRI.

[0096] Second mode: can also be described as a relaxed PDCCH skipping mode or a relaxed skipping mode or a relaxed skipping mode, etc. The second mode is used to specify that a first number of PDCCH skips are allowed during the waiting period corresponding to UEERI.

[0097] The third mode, also described as strict PDCCH skipping mode, strict skipping mode, or strict skipping mode, specifies that a second number of PDCCH skips are allowed during the corresponding wait period in the UEIRI. The second number is less than the first number.

[0098] Fourth mode: can also be described as forced PDCCH monitoring mode or forced monitoring mode, etc. The fourth mode is used to specify that PDCCH skipping will not be performed during the waiting period corresponding to UEIRI.

[0099] Optionally, the first mode has a lower priority than the second mode. The second mode has a lower priority than the third mode. The third mode has a lower priority than the fourth mode.

[0100] Understandably, in the first mode, the UE completely skips PDCCH and does not perform PDCCH monitoring at all. In the second mode, the UE skips a large number of PDCCHs, meaning it skips most of them and performs some PDCCH monitoring, which avoids premature failure of PDCCH monitoring. In the third mode, the UE skips a small number of PDCCHs, meaning it skips a few and performs some PDCCH monitoring, which allows for faster exit from reporting trigger CSI or retransmitting the first UEIRI. In the fourth mode, the UE does not skip PDCCHs at all and performs PDCCH monitoring completely. This avoids the UE being unable to effectively respond to conflicts that occur during the waiting period corresponding to the UEIRI, thus improving communication efficiency.

[0101] In one possible implementation, at least one pattern can be indicated by an indicator field or by an identifier. This application embodiment does not limit the method of indicating at least one pattern. In this application embodiment, at least one pattern is indicated by a first indicator field.

[0102] In one possible implementation, the length (also described as bit width) of the first indicator field can be 2 bits (or 3 bits or 4 bits), and the length of the first indicator field is not limited in this embodiment. In this embodiment, the length of the first indicator field is 2 bits.

[0103] Optionally, the value of the first indicator field can indicate a first mode, a second mode, a third mode, or a fourth mode. It is understood that if the first indicator field is set to the first value, the mode is the first mode. If the first indicator field is set to the second value, the mode is the second mode. If the first indicator field is set to the third value, the mode is the third mode. If the first indicator field is set to the fourth value, the mode is the fourth mode.

[0104] For example, taking a first indicator field with a length of 2 bits as an example, the first, second, third, and fourth values ​​can be any one of 00, 01, 10, and 11, with each value corresponding to a different pattern. In the embodiments of this application, the first value is 00, the second value is 01, the third value is 10, and the fourth value is 11.

[0105] For example, the values ​​of the first indicator field, the corresponding patterns, the meanings of the patterns, and the effects are shown in Table 1 below: Table 1: Values ​​of the first indicator field and their corresponding modes, meanings, and effects.

[0106] Optionally, the configuration information is also used to configure the mode parameters corresponding to each mode.

[0107] Optionally, the mode parameters include at least one of the following: a first threshold related to the effective number of PDCCH monitoring (which can also be described as the maximum number of PDCCH monitoring, the maximum number of monitoring, or the maximum number of effective monitoring, etc.), a second threshold related to the number of consecutive unserviceable PDCCH monitoring (which can also be described as the maximum number of PDCCH skips, the maximum number of skips, the maximum number of skipping, or the maximum number of consecutive unserviceable PDCCH monitoring, etc.), the maximum duration of UEIRI transmission, the maximum number of UEIRI transmissions (which can also be described as the maximum number of UEIRI transmissions, etc.), the preset duration after the maximum number of UEIRI transmissions is reached (which can also be described as the cooling duration after the maximum number of transmissions is reached, or the minimum transmission interval between two UEIRI transmissions, etc.

[0108] The first-time threshold is the threshold for the number of valid PDCCH monitoring sessions, which can be set according to actual needs. For example, the average, median, minimum, or maximum value obtained from multiple valid PDCCH monitoring sessions can be used as the first-time threshold; it can also be set based on empirical values, such as 0, 3, or 5.

[0109] The second threshold is the threshold for the number of consecutive unserviceable times monitored by PDCCH, and it can be set according to actual needs. For example, the average, median, minimum, or maximum value obtained from multiple consecutive unserviceable times monitored by PDCCH can be used as the second threshold; it can also be set according to empirical values, such as 0, 1, or 8.

[0110] The maximum duration is a threshold related to the duration of UEIRI transmission and can be set according to actual needs. For example, the average, median, minimum, or maximum value obtained from multiple durations of UEIRI transmission can be used as the maximum duration; it can also be set based on empirical values, such as 8 time slots (also described as slots), 16 time slots, or 40 time slots.

[0111] The maximum number of transmissions is a threshold related to the number of times UEIRI is transmitted, and can be set according to actual needs. For example, the average, median, minimum, or maximum value obtained from multiple transmissions of UEIRI can be used as the maximum number of transmissions; it can also be set based on empirical values, such as 2 or 3.

[0112] The preset duration is the time elapsed after the maximum number of UEIRI transmissions has been reached, and can be set according to actual needs. For example, the average, median, minimum, or maximum value obtained from multiple durations after the maximum number of UEIRI transmissions has been reached can be used as the preset duration; it can also be set based on empirical values, such as 40 time slots, 80 time slots, or 160 time slots.

[0113] The minimum transmission interval is the interval between two consecutive UEIRI transmissions, and can be set according to actual needs. For example, the minimum transmission interval can be set by statistically analyzing multiple transmission intervals between two consecutive UEIRI transmissions, and using the average, median, minimum, or maximum value of these intervals; alternatively, it can be set based on empirical values, such as 8 time slots, 12 time slots, or 80 time slots.

[0114] Optionally, the mode parameter may also include the number of times the UEIRI has been sent. The number of times the UEIRI has been sent is the number of times the UEIRI has been sent. Optionally, during initial configuration, the number of times the UEIRI has been sent is 0, that is, if the configuration information is initial, the number of times the UEIRI has been sent carried in the configuration information is 0.

[0115] In this application, the values ​​of the same mode parameter corresponding to different modes can be the same or different. For example, each mode and its corresponding mode parameter value are shown in Table 2 below: Table 2: Each mode and its corresponding mode parameters

[0116] It is understandable that configuring at least one mode and the corresponding mode parameters for each mode can reduce signaling overhead and reconfiguration latency, and improve resource utilization efficiency.

[0117] It is understandable that the access network device sends configuration information to the UE to pre-configure the conflict handling method when a PDCCH skip occurs during the waiting period corresponding to the UEIRI. This reduces signaling overhead and transmission latency.

[0118] S302, UE obtains status information.

[0119] Optionally, the status information includes at least one of the following: device type, service type, power consumption status, blind detection capability constraints, mobility status, link change status, and beam reporting requirements.

[0120] In this context, UE obtaining status information can be understood as the UE obtaining its current status information. UE obtaining status information may include at least one of the following: The UE obtains its own device type from the factory settings; The UE obtains the service type of the service currently to be transmitted; The UE collects battery information and determines the power consumption status based on the battery information; The UE determines its blind detection capability constraints based on the network-side configuration, or based on its own capabilities. For details, please refer to existing technologies; further explanation is omitted here. The UE compares its own speed with the speed threshold and determines its mobility status based on the comparison result; specifically, the speed threshold and the determination method are as described in Method 1.5 below.

[0121] The UE compares its own channel quality (such as reference signal received power (RSRP)) with the quality threshold and determines the link change status based on the comparison result; specifically, the quality threshold and the determination method are as described in Method 1.6 below.

[0122] The UE compares the signal quality of its serving beam downgraded by n orders with the quality threshold, and determines the beam reporting requirement based on the comparison result, where n is an integer greater than or equal to 1. Specifically, the quality threshold and its determination method are described in Method 1.7 below.

[0123] Optionally, the configuration information is also used to configure status information that adapts to each mode.

[0124] In one possible implementation, status information can be indicated by an indicator field or by an identifier; this application embodiment does not limit the method of indicating status information. In this application embodiment, status information is indicated by a second indicator field.

[0125] In one possible implementation, the length of the second indicator field can be 2 bits, 3 bits, or 4 bits; however, this application embodiment does not limit the length of the second indicator field. In this application embodiment, the length of the second indicator field is 3 bits.

[0126] Optionally, the second indicator field is also used to indicate the active conditions. The active conditions indicate which information in the status information participates in the mode determination. The value of the second indicator field can refer to the first indicator field or existing technology, and will not be elaborated further here.

[0127] Optionally, device type, service type, power consumption status, blind detection capability constraints, mobility status, link change status, beam reporting requirements, and activity conditions can also be indicated by indicator fields. The content of the indicator fields corresponding to each status information item will be described in detail later and will not be repeated here.

[0128] For example, the field name, field length, encoding, and function corresponding to each status information item are shown in Table 3 below (where CPE stands for Customer Premises Equipment, XR stands for Extended Reality, and UAV stands for Unmanned Aerial Vehicle): Table 3: Indicator information, field name, code, and function for each status information item

[0129] Optionally, the configuration information can also be used to configure the applicable conditions for the status information.

[0130] Optionally, the conditions for applying status information may include any of the following: Method 1.1, Applicable conditions for equipment type.

[0131] Optionally, the device type includes at least one of the following: mobile phone, tablet, CPE, IoT, XR, wearable UE, vehicle UE, UAV, robot, etc.

[0132] The contents of the device type or devClass field can be found in the first indicator field or in existing technology, and will not be repeated here.

[0133] In this embodiment, the device type or devClass field has a length of 2 bits. A value of 00 indicates a mobile phone / tablet. A value of 01 indicates a CPE / IoT. A value of 10 indicates an XR / wearable UE. A value of 11 indicates a vehicle-mounted UE / UAV / robot.

[0134] Optional, the applicable conditions for the device type include: modified parameters.

[0135] Optionally, the correction parameters include at least one of the following: the highest mode allowed by the device type (also described as modeCap_dev), the lowest protection mode recommended by the device type (also described as modeFloor_dev), and whether the device type is allowed to trigger the lowest protection mode (also described as devOverrideEnable). These correction parameters characterize how different device types of UEs correct for different modes.

[0136] It is understandable that, since the priority of the first mode is lower than that of the second mode, the priority of the second mode is lower than that of the third mode, and the priority of the third mode is lower than that of the fourth mode, the highest mode allowed by the device type actually refers to the highest priority mode that the target mode can select. For example, if the highest mode allowed by the device type is the third mode (10), then the target mode can be any one of the first mode (00), the second mode (01), and the third mode (10). The lowest protection mode recommended by the device type actually refers to the lowest priority mode that the target mode can select. For example, if the lowest protection mode recommended by the device type is the second mode (01), then the target mode can be any one of the second mode (01), the third mode (10), and the fourth mode (11).

[0137] In one possible implementation, the correction parameter can be a set of correction parameters or a list of correction parameters; the embodiments of this application do not limit the manner in which the correction parameter is modified. In the embodiments of this application, the correction parameter is a set of correction parameters.

[0138] In other words, the equipment type meets the applicable conditions, including: the equipment type meets the set of correction parameters.

[0139] In one possible implementation, the correction parameters can be indicated through an indicator field or an identifier; the method of indicating the correction parameters is not limited in this embodiment. In this embodiment, the indicator field indicates the highest allowed mode for the device type, the lowest recommended protection mode for the device type, and whether the device type is allowed to trigger the lowest protection mode. The content of the indicator field for the correction parameters can refer to the first indicator field or existing technology, and will not be repeated here.

[0140] For example, the modified parameters and their corresponding field names, lengths, meanings, and encodings are shown in Table 4 below: Table 4: Correction parameters and their corresponding field names, lengths, meanings, and encodings.

[0141] In one possible implementation, the correction parameters for different device types may be the same or different for different modes. This application does not limit the content of the correction parameters for different device types for different modes.

[0142] For example, the device types, their corresponding codes, correction parameters, and meanings are shown in Table 5 below: Table 5: Equipment Types and Corresponding Codes, Correction Parameters, and Meanings

[0143] Understandably, after obtaining the device type, the UE searches in Table 5 to obtain the highest allowed mode type, the recommended minimum protection mode, and whether the device type is allowed to trigger the minimum protection mode. For example, if the UE obtains the device type as mobile phone / tablet, it searches for a device of type mobile phone / tablet in Table 5 and obtains that the highest allowed mode type is the fourth mode, the recommended minimum protection mode is the first mode, and the device type is allowed to trigger the minimum protection mode. That is, the device type corresponding to mobile phone / tablet allows the device type to trigger the minimum protection mode, and the highest allowed target mode can only be the fourth mode (11), and the lowest can only be the first mode (00), for example, any one of the first mode (00), second mode (01), third mode (10), and fourth mode (11).

[0144] Method 1.2, Applicable conditions for business types.

[0145] Optionally, the business types include at least one of the following: background synchronization, cached video, file upload / download, non-real-time log / sensing data retransmission, voice, video conferencing, real-time uplink video, cloud gaming, XR interaction, industrial control, vehicle-road cooperative sensing, and emergency alarm.

[0146] The content of the business type or svcTypeId field can be found in the first indicator field or in existing technologies, and will not be repeated here.

[0147] In this embodiment, the length of the business type or svcTypeId field is 4 bits. A value of 0x0 indicates background synchronization. A value of 0x1 indicates cached video. A value of 0x2 indicates file upload / download. A value of 0x3 indicates non-real-time log / sensory data retransmission. A value of 0x4 indicates voice. A value of 0x5 indicates video conferencing. A value of 0x6 indicates real-time uplink video. A value of 0x7 indicates cloud gaming. A value of 0x8 indicates XR interaction. A value of 0x9 for the business type or svcTypeId field indicates industrial control. A value of 0xA indicates vehicle-road cooperative perception. A value of 0xB indicates emergency alarm.

[0148] Optional, the applicable conditions for the service type include: latency-insensitive beam reporting service.

[0149] In one possible implementation, the delay-insensitive beam reporting service can be a set of delay-insensitive beam reporting services or a list of delay-insensitive beam reporting services. This application embodiment does not limit the manner in which the delay-insensitive beam reporting service is provided. In this application embodiment, the delay-insensitive beam reporting service is a set of delay-insensitive beam reporting services.

[0150] In other words, the applicable conditions for a service type include: whether the service type belongs to the latency-insensitive beam reporting service set. In other words, whether the service type is within the latency-insensitive beam reporting service set.

[0151] For example, the service type, its corresponding encoding, sensitivity score S, and whether it is in the latency-insensitive beam reporting service set are shown in Table 6 below: Table 6: Service type and corresponding code, sensitivity score S, and whether it is in the delay-insensitive beam reporting service set

[0152] Understandably, after obtaining the service type, the UE looks up the corresponding service type in Table 6 and further determines whether the service type is in the latency-insensitive beam reporting service set, thus determining the sensitivity score S. For example, if the UE obtains that the service type is cached video, it looks up the service type for cached video in Table 6, determines that cached video is in the latency-insensitive beam reporting service set, and determines that the sensitivity score S is 0.

[0153] Method 1.3, Applicable conditions for power consumption states.

[0154] Optionally, the power consumption state includes at least one of the following: power saving, energy saving, balanced, unconstrained, etc.

[0155] The contents of the power consumption status or pwrState field can be found in the first indicator field or in existing technologies, and will not be repeated here.

[0156] In this embodiment, the power consumption status or pwrState field has a length of 2 bits. A value of 00 indicates power saving. A value of 01 indicates energy saving. A value of 10 indicates balanced power consumption. A value of 11 indicates unconstrained power consumption.

[0157] Optionally, the applicable conditions for the power state include: mode upper limit. That is, the power state meets the applicable conditions, including: the upper limit of the modes allowed by the power state.

[0158] It is understandable that the upper limit of the mode actually refers to the highest priority mode that the target mode can select. For example, if the upper limit of the mode is the third mode (10), then the target mode can be any one of the first mode (00), the second mode (01), and the third mode (10).

[0159] For example, the power consumption states and their corresponding codes, meanings, and mode limits are shown in Table 7 below: Table 7: Power Consumption Status and Corresponding Encoding, Meaning, and Mode Upper Limit

[0160] It is understandable that after obtaining the power consumption status, the UE looks up the corresponding mode upper limit in Table 7. For example, after the UE obtains the power consumption status as energy saving, it looks up the mode upper limit in Table 7 as the third mode (10). That is to say, the power consumption status corresponding to energy saving can only be determined as the third mode (10) at most, for example, any one of the first mode (00), the second mode (01), and the third mode (10).

[0161] Method 1.4, Applicable conditions for blind inspection capability constraints.

[0162] Optionally, the blind detection capability constraint includes at least one of the following: low blind detection capability, medium blind detection capability, high blind detection capability, and very high blind detection capability. Among them, very high is greater than high.

[0163] The content of the blind detection capability constraint or capClass field can be found in the first indicator field or in existing technology, and will not be repeated here.

[0164] In this embodiment, the length of the blind detection capability constraint or capClass field is 2 bits. A value of 00 indicates low blind detection capability. A value of 01 indicates medium blind detection capability. A value of 10 indicates high blind detection capability. A value of 11 indicates very high blind detection capability.

[0165] Optionally, the applicable conditions for blind detection capability constraints include: mode upper limit. In other words, the blind detection capability constraints must meet the applicable conditions, including: the upper limit of modes allowed by the blind detection capability constraints.

[0166] For example, the blind detection capability constraints, their corresponding codes, meanings, and mode limits are shown in Table 8 below: Table 8: Blind Detection Capability Constraints and Corresponding Codes, Meanings, and Mode Upper Limits

[0167] It is understandable that after obtaining the blind detection capability constraint, the UE looks up the corresponding mode upper limit in Table 8. For example, after obtaining the blind detection capability constraint as high blind detection capability, the UE looks up the mode upper limit in Table 8 as the fourth mode. That is to say, the blind detection capability constraint corresponding to high blind detection capability allows the target mode to be determined at most the fourth mode (11), for example, any one of the first mode (00), the second mode (01), the third mode (10), and the fourth mode (11).

[0168] Method 1.5, Applicable conditions for mobility status.

[0169] Optionally, the applicable conditions for the mobility state include at least one of the following: a first threshold (also described as a first speed threshold or speedTh1), a second threshold (also described as a second speed threshold or speedTh2), a third threshold (also described as a third speed threshold or speedTh3), a fourth threshold (also described as a first-order beam switching frequency threshold or beamSwitchRateTh1), a fifth threshold (also described as a second-order beam switching frequency threshold or beamSwitchRateTh2), a sixth threshold (also described as a switching frequency threshold or hoRateTh), or a seventh threshold (also described as a Doppler class threshold or dopplerClassTh).

[0170] Among them, the first threshold is less than or equal to the second threshold, the second threshold is less than or equal to the third threshold, and the fourth threshold is less than or equal to the fifth threshold.

[0171] The first threshold is the threshold for low-speed UE operation, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple speeds of the UE at low speeds, such as the average, median, minimum, or maximum value of multiple speeds at low speeds; it can also be set based on empirical values, such as 126 km / h.

[0172] The second threshold is the threshold for high-speed UE operation, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple speeds of the UE at high speeds, such as the average, median, minimum, or maximum value of multiple speeds at high speeds; it can also be set based on empirical values, such as 254 km / h.

[0173] The third threshold is the threshold for UE speeds at ultra-high speeds, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple speeds of the UE at ultra-high speeds, such as the average, median, minimum, or maximum value of multiple speeds at ultra-high speeds; it can also be set based on empirical values, such as 510 km / h.

[0174] The fourth threshold is the threshold for the first-order beam switching frequency, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple first-order beam switching frequencies, such as the mean, median, minimum, or maximum value of multiple first-order beam switching frequencies; it can also be set based on empirical values, such as 7 times / second.

[0175] The fifth threshold is the threshold for the second-order beam switching frequency, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple frequencies of second-order beam switching, such as the mean, median, minimum, or maximum value of multiple frequencies of second-order beam switching; it can also be set based on empirical values, such as 15 times / second.

[0176] The sixth threshold is the threshold for beam switching frequency, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple beam switching frequencies, such as the mean, median, minimum, or maximum value of multiple beam switching frequencies; it can also be set based on empirical values, such as 7 times / minute.

[0177] The seventh threshold is the threshold for Doppler levels, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple Doppler levels, such as the mean, median, minimum, or maximum value of multiple Doppler levels; it can also be set based on empirical values, such as "extremely high".

[0178] For example, the applicable conditions for link change status, as well as their corresponding meanings and functions, are shown in Table 9 below: Table 9: Applicable conditions for mobility status and their corresponding meanings and functions

[0179] In one possible implementation, the applicable conditions of the mobility state can be indicated by an indicator field or by an identifier. This application embodiment does not limit the method of indicating the applicable conditions of the mobility state. In this application embodiment, the applicable conditions of the mobility state are indicated by an indicator field.

[0180] For example, the applicable conditions for mobility status and the field names, lengths, encoding rules, and example values ​​of the corresponding indication fields are shown in Table 10 below (where LSB is the least significant bit; 2km / h / LSB is used to characterize the speed value change to 2km / h for every 1 LSB change or the speed change to 2km / h for every 1 LSB change): Table 10: Applicable conditions for mobility status and corresponding indicator fields, including field names, lengths, encoding rules, and example values.

[0181] The contents of the first threshold field or speedTh1 field, the second threshold field or speedTh2 field, the third threshold field or speedTh3 field, the fourth threshold field or beamSwitchRateTh1 field, the fifth threshold field or beamSwitchRateTh2 field, the sixth threshold field or hoRateTh field, or the seventh threshold field or dopplerClassTh field can be referred to the first indicator field or existing technology, and will not be repeated here.

[0182] Optionally, the mobility status meets the applicable conditions, including at least one of the following: The UE's speed is less than the first threshold and the beam switching frequency is less than the fourth threshold, so the mobility status is stationary / low speed. The UE’s speed is greater than or equal to the first threshold and less than the second threshold, or the beam switching frequency is greater than or equal to the fourth threshold, and the mobility state is medium speed. The mobility state is high-speed if the UE's speed is greater than or equal to the second threshold and less than the third threshold, or if the beam switching frequency is greater than or equal to the fifth threshold. The UE's speed is greater than or equal to the third threshold, or the beam switching frequency is greater than or equal to the sixth threshold, or the Doppler level is high or very high, and the mobility state is ultra-high speed.

[0183] The contents of the mobility state or mobState field can be found in the first indicator field or in existing technology, and will not be described again here.

[0184] In this embodiment, the length of the mobility state or mobState field is 2 bits. A value of 00 indicates a stationary / low-speed mobility state. A value of 01 indicates a medium-speed mobility state. A value of 10 indicates a high-speed mobility state. A value of 11 indicates an ultra-high-speed mobility state.

[0185] For example, the mobility status, its corresponding code, applicable conditions, and mobility score M are shown in Table 11 below: Table 11: Mobility Status and Corresponding Codes, Applicable Conditions, and Mobility Score M

[0186] Understandably, after obtaining the UE's speed, and / or beam switching frequency, and / or Doppler level, the UE looks up information in Table 11 to determine the specific mobility state, and further determines the mobility score M corresponding to that mobility state. For example, after obtaining the UE's speed, if the UE looks up information in Table 11 and finds that the UE's speed is greater than or equal to the first threshold and less than the second threshold, the mobility state is determined to be medium speed, and the mobility score M is 1.

[0187] Method 1.6, Applicable conditions for link change status.

[0188] Optionally, the applicable conditions for link change states include at least one of the following: the eighth threshold (which can also be described as the first-order drop threshold of reference signal received power or the first-order drop threshold of RSRP or rsrpDropTh1), the ninth threshold (which can also be described as the second-order drop threshold of RSRP or rsrpDropTh2), the tenth threshold (which can also be described as the first-order drop threshold of reference signal received quality (RSRQ) or the first-order drop threshold of RSRQ or rsrqDropTh1), the eleventh threshold (which can also be described as the second-order drop threshold of RSRQ or rsrqDropTh2), the twelfth threshold (which can also be described as the absolute threshold of RSRP or absRsrpCrit), the thirteenth threshold (which can also be described as the absolute threshold of RSRQ or absRsrqCrit), the measurement period (which can also be described as the measurement period index or measPeriodIdx), or the moving average window (which can also be described as the smoothed average window or avgWin).

[0189] Among them, the eighth threshold is less than or equal to the ninth threshold. The tenth threshold is less than or equal to the eleventh threshold.

[0190] The eighth threshold is the threshold for the first-order descent of RSRP, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple RSRP values ​​that show the first-order descent, such as the mean, median, minimum, or maximum value of these values; it can also be set based on empirical values, such as 3dB.

[0191] The ninth threshold is the threshold for the second-order descent of RSRP, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple RSRP values ​​that show a second-order descent, such as the mean, median, minimum, or maximum value of these values; it can also be set based on empirical values, such as 6 dB.

[0192] The tenth threshold is the threshold for the first-order descent of RSRQ, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple RSRQ values ​​for the first-order descent, such as the mean, median, minimum, or maximum of multiple RSRQ values ​​for the first-order descent; it can also be set based on empirical values, such as 2dB.

[0193] The eleventh threshold is the threshold for the second-order descent of RSRQ, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple RSRQ values ​​for the second-order descent of RSRQ, such as the mean, median, minimum, or maximum value of multiple RSRQ values ​​for the second-order descent of RSRQ; it can also be set based on empirical values, such as 4dB.

[0194] The twelfth threshold is the threshold for the absolute value of RSRP, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple absolute values ​​of RSRP, such as the mean, median, minimum, or maximum value of multiple absolute values ​​of RSRP; it can also be set based on empirical values, such as -110dB.

[0195] The thirteenth threshold is the threshold for the absolute value of RSRQ, which can be set according to actual needs. For example, it can be obtained by counting multiple absolute values ​​of RSRQ, such as the mean, median, minimum, or maximum value of multiple absolute values ​​of RSRQ; it can also be set based on empirical values, such as -15dB.

[0196] The measurement period is the period for measuring link change status, and it can be set according to actual needs. For example, it can be obtained by statistically analyzing the periods of multiple link change status measurements, such as the average, median, minimum, or maximum of the periods of multiple link change status measurements; it can also be set based on empirical values, such as 40ms.

[0197] The moving average window represents the average value over a historical measurement period and can be set according to actual needs. For example, it can be obtained by calculating the average value of multiple historical measurement periods, such as the average, median, minimum, or maximum value of multiple historical measurement periods; it can also be set based on empirical values, such as 4.

[0198] For example, the applicable conditions for link change status, as well as their corresponding meanings and functions, are shown in Table 12 below: Table 12: Applicable conditions for link change status, and their corresponding meanings and effects

[0199] In one possible implementation, the applicable conditions for the link change state can be indicated by an indicator field or by an identifier. This application embodiment does not limit the method of indicating the applicable conditions for the link change state. In this application embodiment, the applicable conditions for the link change state are indicated by an indicator field.

[0200] For example, the applicable conditions for link change status and the corresponding field names, lengths, encoding rules, and example values ​​of the indication fields are shown in Table 13 below (where LSB is the least significant bit (LSB); 1dB / LSB is used to characterize the change in decibel value by 1dB for each change of 1 LSB or the change of 1dB for each change of 1 LSB; the relative value (also described as offset) is the difference relative to a certain reference point (such as the base value, the previous value, or the center point); the encoded value (also described as enc); and the actual threshold (also described as threshold)): Table 13: Applicable conditions for link change status and corresponding indicator field names, lengths, encoding rules, and example values.

[0201] Optionally, the link change status meets the applicable conditions, including at least one of the following: If ΔRSRP (which can also be described as the difference between RSRP and RSRP) is less than the eighth threshold and ΔRSRQ (which can also be described as the difference between RSRQ and RSRQ) is less than the tenth threshold, the link change state is stable. If ΔRSRP is greater than or equal to the eighth threshold and less than the ninth threshold, and ΔRSRQ is greater than or equal to the tenth threshold and less than the eleventh threshold, the link change state is a slightly degraded state. If ΔRSRP is greater than or equal to the ninth threshold, or if ΔRSRQ is greater than or equal to the eleventh threshold, the link change state is a rapid degradation state. If RSRP is less than or equal to the twelfth threshold, or RSRQ is less than or equal to the thirteenth threshold, the link change status is an emergency state.

[0202] The content of the link change status or linkDeltaState field can be found in the first indicator field or in existing technologies, and will not be repeated here.

[0203] Among them, ΔRSRP and ΔRSRQ are related to the actual value and the moving average of the moving average window avgWin measurement periods. Specifically, ΔRSRP and ΔRSRQ, along with the actual value and the moving average of the moving average window avgWin measurement periods, satisfy the following formulas (1)-(2): ΔRSRP= Formula (1); ΔRSRQ= Formula (2); in, The moving average of RSRP is calculated for a moving average window of avgWin measurement periods. The moving average of RSRQ for a moving average window of avgWin measurement periods. This is the actual value of RSRP. ΔRSRP is the actual value of RSRQ. ΔRSRP is the difference between the moving average of RSRP over avgWin measurement periods and the actual value of RSRP. ΔRSRQ is the difference between the moving average of RSRQ over avgWin measurement periods and the actual value of RSRQ.

[0204] It is understandable that the UE can obtain the RSRP and RSRQ of the current serving beam, and calculate ΔRSRP and ΔRSRQ based on the obtained RSRP, RSRQ and formulas (1)-(2).

[0205] In this embodiment, the link change state or linkDeltaState field has a length of 2 bits. A value of 00 indicates a stable mobility state. A value of 01 indicates a slightly degraded mobility state. A value of 10 indicates a rapidly degraded mobility state. A value of 11 indicates an emergency mobility state.

[0206] For example, the link change status, the corresponding encoding, the applicable conditions, and the link change status score L are shown in Table 14 below: Table 14: Link Change Status and Corresponding Codes, Applicable Conditions, and Link Change Status Scores L

[0207] Understandably, after obtaining RSRP and RSRQ, the UE calculates ΔRSRP and ΔRSRQ, looks up the applicable conditions in Table 14, determines the specific link change state, and assigns a link change state score L. For example, after obtaining RSRP and RSRQ, the UE calculates ΔRSRP and ΔRSRQ, looks up the applicable conditions in Table 14, and determines that ΔRSRP is greater than or equal to the ninth threshold, or ΔRSRQ is greater than or equal to the eleventh threshold. In this case, the link change state is determined to be a rapid degradation state, and the link change state score L is determined to be 2.

[0208] Method 1.7, Applicable conditions for beam reporting requirements.

[0209] Optionally, the applicable conditions for beam reporting requirements include at least one of the following: the fourteenth threshold (which can also be described as the first-order descent threshold of the serving beam or the first-order descent threshold of servBeam or servBeamDropTh1), the fifteenth threshold (which can also be described as the second-order descent threshold of the serving beam or the second-order descent threshold of servBeam or servBeamDropTh2), the sixteenth threshold (which can also be described as the threshold for candidate beams to be better than the current serving beam or candBeamBetterTh), the seventeenth threshold (which can also be described as the first-order aging threshold of the serving beam or the first-order aging threshold of beam report or beamReportAgeTh1), the eighteenth threshold (which can also be described as the second-order aging threshold of the serving beam or the second-order aging threshold of beam report or beamReportAgeTh2), the nineteenth threshold (which can also be described as the beam failure risk threshold or beamFailRiskTh), or the twentieth threshold (which can also be described as the threshold for the number of candidate available beams or minCandidateBeamNum).

[0210] Among them, the fourteenth threshold is less than or equal to the fifteenth threshold. The seventeenth threshold is less than or equal to the eighteenth threshold.

[0211] The fourteenth threshold is the threshold for the RSRP value of the first-order descent of the serving beam, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple RSRP values ​​of the first-order descent of the serving beam, such as the mean, median, minimum, or maximum value of multiple RSRP values ​​of the first-order descent of the serving beam; it can also be set based on empirical values, such as 3dB.

[0212] The fifteenth threshold is the threshold for the RSRP value of the second-order descent of the serving beam, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple RSRP values ​​of the second-order descent of the serving beam, such as the mean, median, minimum, or maximum value of multiple RSRP values ​​of the second-order descent of the serving beam; it can also be set based on empirical values, such as 6dB.

[0213] The sixteenth threshold is the threshold for the RSRP value of a candidate beam that is better than the current serving beam, and it can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple RSRP values ​​of candidate beams that are better than the current serving beam, such as the mean, median, minimum, or maximum value of multiple RSRP values ​​of candidate beams that are better than the current serving beam; it can also be set based on empirical values, such as 3dB.

[0214] The seventeenth threshold is the threshold for the first-order aging duration of the serving beam, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple first-order aging durations of the serving beam, such as the average, median, minimum, or maximum value of multiple first-order aging durations of the serving beam; it can also be set based on empirical values, such as 16 time slots.

[0215] The eighteenth threshold is the threshold for the duration of second-order aging of the serving beam, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple durations of second-order aging of the serving beam, such as the average, median, minimum, or maximum value of multiple durations of second-order aging of the serving beam; it can also be set based on empirical values, such as 64 time slots.

[0216] The nineteenth threshold is the threshold for the level of beam failure risk, which can be set according to actual needs. For example, it can be obtained by statistically analyzing multiple levels of beam failure risk, such as the mean, median, minimum, or maximum value of multiple levels of beam failure risk; it can also be set based on empirical values, such as a high level.

[0217] The twentieth threshold is the threshold for the number of candidate available beams, which can be set according to actual needs. For example, it can be obtained by counting multiple candidate available beams, such as the mean, median, minimum, or maximum of multiple candidate available beams; it can also be set based on empirical values, such as 1 or 2.

[0218] For example, the applicable conditions, corresponding meanings, and functions of beam reporting requirements are shown in Table 15 below: Table 15: Applicable Conditions for Beam Reporting Requests, and Their Corresponding Meanings and Functions

[0219] In one possible implementation, the applicable conditions for beam reporting requirements can be indicated through an indicator field or an identifier. This application embodiment does not limit the method of indicating the applicable conditions for beam reporting requirements. In this application embodiment, the applicable conditions for beam reporting requirements are indicated through an indicator field.

[0220] For example, the applicable conditions for beam reporting requirements and the field names, lengths, encoding rules, and example values ​​of the corresponding indicator fields are shown in Table 16 below (where LSB is the least significant bit; 1dB / LSB is used to characterize the change in decibel value by 1dB for each change of 1 LSB or the change in decibel value by 1dB for each change of 1 LSB): Table 16: Applicable conditions for beam reporting requirements and corresponding indicator field names, lengths, encoding rules, and example values.

[0221] Optionally, the beam reporting requirement must meet the applicable conditions, including at least one of the following: (This can also be described as the gain of the current serving beam or the RSRP gain of the current serving beam or RSRP gain) being less than the sixteenth threshold, and (This can also be described as the duration or time slot of beam aging) If it is less than the seventeenth threshold, the beam reporting requirement is low. ΔRSRP is greater than or equal to the fourteenth threshold, or, If the value is greater than or equal to the seventeenth threshold, the beam reporting requirement is medium. ΔRSRP is greater than or equal to the fifteenth threshold, or, Greater than or equal to the sixteenth threshold, or, If the value is greater than or equal to the 18th threshold, the beam reporting requirement is high. The beam failure risk level is greater than the nineteenth threshold, or the link change status is an emergency state coded as 11, or the number of candidate available beams is less than the twentieth threshold and ΔRSRP is less than the fifteenth threshold, and the beam reporting requirement is extremely high.

[0222] The content of the beam reporting requirement or beamNeedIdx field can be found in the first indicator field or existing technology, and will not be repeated here.

[0223] in, , It is related to the actual value of the RSRP of the currently serving beam, the actual value of the RSRP of the current best candidate beam, the time slot in which the UE currently reports the beam, and the time slot in which the UE last reported the beam. Specifically, , The actual value of the RSRP of the current serving beam, the actual value of the RSRP of the current best candidate beam, the time slot reported by the UE for the current beam, and the time slot reported by the UE for the last beam satisfy the following formulas (3)-(4): = Formula (3); = Formula (4); in, This is the actual value of RSRP for the current best candidate beam. This is the actual value of the RSRP for the currently serving beam. This is the difference between the actual RSRP of the current best candidate beam and the actual RSRP of the currently serving beam. This refers to the time slot reported by the UE's current beam. This refers to the time slot of the UE's last beam report.

[0224] Understandably, the UE can obtain the RSRP of the current serving beam, the RSRP of the current best candidate beam, the timeslot of the current beam reporting, and the timeslot of the last beam reporting. Based on the obtained RSRP of the current serving beam, RSRP of the current best candidate beam, timeslot of the current beam reporting, timeslot of the last beam reporting, and formulas (2)-(5), it can calculate ΔRSRP. , .

[0225] In this embodiment, the beam reporting requirement or beamNeedIdx field has a length of 2 bits. A value of 00 indicates a low beam reporting requirement. A value of 01 indicates a medium beam reporting requirement. A value of 10 indicates a high beam reporting requirement. A value of 11 indicates an extremely high beam reporting requirement.

[0226] For example, the beam reporting requirements, their corresponding codes, applicable conditions, and requirement score B are shown in Table 17 below: Table 17: Beam reporting requirements and corresponding codes, applicable conditions, and requirement score B

[0227] Understandably, after obtaining the RSRP of the current serving beam, the RSRP of the current best candidate beam, the timeslot of the current beam reporting, and the timeslot of the last beam reporting, the UE calculates ΔRSRP. , The applicable conditions are found in Table 17 to determine the specific beam reporting requirement, and the corresponding requirement score B is obtained. For example, after obtaining the RSRP of the current serving beam, the RSRP of the current best candidate beam, the current beam reporting time slot, and the time slot of the last beam reporting, the UE calculates ΔRSRP. , The applicable conditions found in Table 17 are: ΔRSRP is greater than or equal to the fourteenth threshold, or... If the value is greater than or equal to the seventeenth threshold, the beam reporting requirement is determined to be medium, and further, the requirement score B is determined to be 1.

[0228] It is understandable that the UE obtains the status information in order to determine the mode corresponding to the conflict handling method when the UE skips the PDCCH during the waiting period corresponding to the UEIRI, that is, to determine the target mode.

[0229] S303, the UE determines the target mode based on configuration information and status information.

[0230] After obtaining the status information, the UE can determine the target mode based on the obtained status information and the aforementioned configuration information. The target mode is at least one mode that corresponds to the UE's status information.

[0231] In one possible implementation, the UE can first obtain each status information, then determine the target status information for judging the target mode based on the active conditions in the configuration information, and determine the target mode based on the UE's current target status information. Alternatively, the UE can first determine the target status information for judging the target mode based on the active conditions in the configuration information, then obtain the UE's current target status information, and determine the target mode based on the UE's current target status information. The embodiments of this application do not limit the order of obtaining status information and determining status information based on the active conditions in the configuration information.

[0232] Since the service type determines the sensitivity score S, the mobility status determines the mobility score M, the link change status determines the link change status score L, and the beam reporting requirement determines the requirement score B, it means that the service type, mobility status, link change status, and beam reporting requirement are all related to the scores. Optionally, the urgency score U can be obtained based on the sensitivity score S corresponding to the service type, the mobility score M corresponding to the mobility status, the link change status score L corresponding to the link change status, and the requirement score B corresponding to the beam reporting requirement.

[0233] Optionally, the urgency score U and the sensitivity score S corresponding to the service type, the mobility score M corresponding to the mobility status, the link change status score L corresponding to the link change status, and the demand score B corresponding to the beam reporting demand satisfy the following formula (5): U = α × S + β × L + γ × M + δ × B Formula (5); Where U is the urgency score. S is the sensitivity score corresponding to the service type. M is the mobility score corresponding to the mobility status. L is the link change status score corresponding to the link change status. B is the requirement score corresponding to the beam reporting requirement. α, β, γ, and δ are the coefficients of S, L, M, and B, respectively.

[0234] Optionally, α can be 4. β can be 3. γ can be 2. δ can be 3.

[0235] It is understandable that after obtaining the service type, mobility status, link change status, and beam reporting requirement, the UE can query Tables 6, 11, 14, and 17 to obtain the sensitivity score S corresponding to the service type, the mobility score M corresponding to the mobility status, the link change status score L corresponding to the link change status, and the requirement score B corresponding to the beam reporting requirement. Based on the above formula (5), the urgency score U can be calculated.

[0236] Optionally, the urgency rating U can be compared with the initial mode. Related. Specifically, the urgency score U and the initial mode. Satisfy the following formula (6): Formula (6); Where 00 is the code for the first mode, used to represent the first mode. 01 is the code for the second mode, used to represent the second mode. 10 is the code for the third mode, used to represent the third mode. 11 is the code for the fourth mode, used to represent the fourth mode. U represents the urgency score. This is the initial mode.

[0237] It is understandable that after calculating the urgency score U, the UE can calculate the initial mode based on the above formula (6). .

[0238] Optionally, the UE can determine the final mode based on the remaining state information: device type, power consumption state, and blind detection capability constraints. Specifically, The constraints of device type, power consumption status, and blind detection capability satisfy the following formula (7): Formula (7); Optionally, if the device type is not allowed to trigger the minimum protection mode, that is, the device type does not trigger the minimum protection mode or is not configured with the minimum protection mode, then The constraints of device type, power consumption status, and blind detection capability satisfy the following formula (8): Formula (8); in, The minimum protection mode recommended for this device type. The highest mode allowed for this device type. This represents the upper limit of the power state modes; in other words, the highest mode that the power state is allowed to operate in. This represents the upper limit of the blind detection capability constraint, that is, the highest mode allowed by the blind detection capability constraint. This is the initial mode. This is the final model.

[0239] It is understandable that after obtaining the device type, power consumption status, and blind detection capability constraints, the UE can consult Tables 5, 7, and 8 to obtain the highest allowed mode for the device type, whether the device type is allowed to trigger the minimum protection mode, the minimum protection mode recommended for the device type, the highest allowed mode for the power consumption status, and the highest allowed mode for the blind detection capability constraints. Thus, based on the initial mode calculated using the above formulas (5) to (6), the UE can determine the highest allowed mode for the device type. Based on the above formula (7) or formula (8), the final pattern is calculated. .

[0240] In the method described in formulas (5)-(8) above for the UE to determine the mode based on configuration information and acquired status information, the urgency score U is used to reflect the intensity of the real-time demand for target DCI capture by the UEIRI trigger event, while the device type, power consumption status, and blind detection capability constraints are used to limit the range of modes that the UE can actually execute when a conflict occurs during the waiting period corresponding to the UEIRI, i.e., mode constraints. In this way, the urgency of the event and the mode constraints executed by the UE can be separated.

[0241] Understandably, when a UE obtains status information, it can query at least one of the following tables (Tables 5-8, 11, 14, and 17) in the configuration information based on the obtained status information, and obtain at least one of the following: the corresponding score, the minimum protection mode recommended for the device type, the maximum allowed mode, and whether the device type is allowed to trigger the minimum protection mode, and calculate the final mode. .

[0242] For example, the UE obtains that the current service type is cached video, the link change state is stable, and the power consumption state is power saving. Looking up the table in the configuration information, it finds that cached video, in the latency-insensitive beam report service set, has a sensitivity score S of 0. The link change state score L corresponding to the stable state is found to be 0. The upper limit of the power saving mode is found to be the second mode (01). The UE calculates the urgency score U to be 0, corresponding to the initial mode. The first mode is (00). The final mode is then calculated. The first mode is (00), therefore, the target mode is the first mode (00).

[0243] For example, the UE obtains that the current service type is video conferencing, the link change status is slightly degraded, and the power consumption status is balanced. Looking up the table in the configuration information, it finds that video conferencing is not in the latency-insensitive beam reporting service set, and the corresponding sensitivity score S is 2. The link change status score L corresponding to the slightly degraded status is found to be 1. The upper limit of the balanced mode is found to be the fourth mode (11). The UE calculates the urgency score U to be 11, corresponding to the initial mode. This is the second mode (01). The final mode is then calculated. The target mode is the second mode (01).

[0244] For example, the UE obtains that the current device type is vehicle-mounted UE, the service type is real-time uplink video or cloud gaming, and the link change status is rapid degradation. Looking up the configuration information, the highest allowed mode for the vehicle-mounted UE is the fourth mode (11), and the recommended lowest protection mode is the third mode (10). It is found that real-time uplink video or cloud gaming is not in the latency-insensitive beam report service set, and the corresponding sensitivity score S is 2. The link change status score L corresponding to the rapid degradation status is 2. The UE calculates the urgency score U as 14, corresponding to the initial mode. This is the second mode (01). The final mode is then calculated. Therefore, the target mode is the third mode (10).

[0245] For example, the UE obtains that the current service type is XR interaction or industrial control, the power consumption status is unconstrained, the blind detection capability is high or extremely high, the link change status is an emergency state, and the beam reporting requirement is extremely high. Looking up the table in the configuration information, it is found that XR interaction or industrial control is not in the latency-insensitive beam reporting service set, and the corresponding sensitivity score S is 3. The upper limit of the mode corresponding to unconstrained is found to be the fourth mode (11). The upper limit of the mode corresponding to high or extremely high blind detection capability is found to be the fourth mode (11). The link change status score L corresponding to the emergency state is found to be 3. The requirement score B corresponding to the extremely high beam reporting requirement is found to be 3. The UE calculates the urgency score U to be 30, corresponding to the initial mode. This is the fourth mode (11). The final mode is then calculated. Therefore, the target mode is the fourth mode (11).

[0246] S304. In response to the detection of a report that requires triggering CSI, the UE sends the first UEIRI to the access network device.

[0247] Accordingly, the access network device receives the first UEIRI sent by the UE.

[0248] In one possible implementation, the first UEIRI may or may not indicate the target mode. This application embodiment does not limit whether the first UEIRI indicates the target mode.

[0249] When the first UEIRI indicates the target mode, the first UEIRI not only indicates that the UE needs to trigger CSI reporting, but also indicates the target mode. In this way, by reusing the first UEIRI to indicate the target mode, signaling overhead can be saved.

[0250] Optionally, if the first UEIRI indicates the target mode, it can be indicated by resources associated with the first UEIRI. For example, the first resource indicates the first mode, the second resource indicates the second mode, the third resource indicates the third mode, and the fourth resource indicates the fourth mode.

[0251] Optionally, the first resource can be a PUCCH resource with an offset of 0, the second resource can be a PUCCH resource with an offset of 1, the third resource can be a PUCCH resource with an offset of 2, and the fourth resource can be a PUCCH resource with an offset of 3.

[0252] If the first UEIRI does not indicate a target mode, it only indicates that the UE needs to trigger CSI reporting. Optionally, the target mode can be indicated by the UCI associated with the first UEIRI. An example is shown in the attached figure. Figure 3 As shown, the communication method 300 may further include step S305: S305, the UE sends a UCI to the access network equipment.

[0253] Accordingly, the access network equipment receives the UCI sent by the UE.

[0254] Among them, UCI is associated with the first UEIRI and is used to indicate the target mode.

[0255] In other words, if the first UEIRI does not indicate the target mode, it only indicates that the UE needs to trigger CSI reporting. The UCI associated with the first UEIRI is used to indicate the target mode. In this way, by using the first UEIRI and the UCI associated with it to indicate whether the UE needs to trigger CSI reporting and the target mode, resource conflicts can be avoided, scalability is good, and communication reliability is improved.

[0256] The communication method 300 described in steps S301-S305 above allows the access network device to pre-configure at least one mode for when a PDCCH skip occurs during the waiting period corresponding to the UEIRI. This enables the UE to determine a target mode corresponding to the status information based on the acquired status information and the at least one mode configured by the access network device, and then send the target mode and the first UEIRI to the access network device. In this way, on the one hand, the access network device can determine whether to send a DCI to the UE based on the target mode, avoiding blindly sending DCIs to the UE, saving signaling overhead and power consumption, thereby improving communication efficiency. On the other hand, the UE can also determine whether to perform PDCCH monitoring based on the target mode, reducing UE response latency and avoiding the inability to capture DCIs, thus preventing the inability to report CSIs, thereby improving communication efficiency.

[0257] Furthermore, after receiving the target mode indicated by the UE, the access network device can determine whether to send DCI to the UE based on the target mode. In addition, after determining the target mode, the UE can also skip or not skip PDCCH monitoring, etc., based on the target mode. The following section combines... Figure 4 The following further process is described: Appendix Figure 4 This is a flowchart illustrating another communication method provided in an embodiment of this application. It can be understood that the UE involved in this communication method may be an attached... Figure 1 The UE in this context can also refer to the device within the UE (such as a processor, chip, or chip system). The access network equipment involved in this communication method can be an auxiliary device. Figure 1 Access network equipment can also refer to devices within access network equipment (such as processors, chips, or chip systems). For example, see attached... Figure 4 As shown, the communication method 300 may further include the following steps S306-S320: S306. Access network equipment determines whether the target mode is the first mode.

[0258] After receiving the target mode sent by the UE, the access network device can determine whether the target mode is the first mode. It is understandable that the access network device determines whether the target mode is the first mode in order to decide whether to send DCI to the UE.

[0259] If the target mode is the first mode, proceed to step S307. If the target mode is the second, third, or fourth mode, proceed to step S308.

[0260] S307. Access network equipment does not send DCI to UE.

[0261] When the target mode is the first mode, the UE skips PDCCH monitoring and does not perform PDCCH monitoring associated with the first UEIRI. Therefore, the access network device may not send DCI to the UE.

[0262] It should be understood that when an access network device does not send a DCI to a UE, it means that it will not send a DCI specific to that UE. In other words, it will no longer send a DCI to schedule the CSI reporting of that UE. This does not affect the access network device's ability to send DCIs to other UEs.

[0263] S308. The access network equipment sends DCI to the UE.

[0264] Accordingly, the UE can receive DCI sent by the access network device.

[0265] DCI is used to instruct / schedule the UE to send CSI to the access network equipment.

[0266] When the target mode is the second, third or fourth mode, the UE does not completely skip PDCCH monitoring and performs PDCCH monitoring associated with the first UEIRI. Therefore, the access network device can send DCI to the UE accordingly.

[0267] S309, UE determines whether the target mode is the first mode.

[0268] In one possible implementation, step S308 can be performed before, after, or simultaneously with step S309. The embodiments of this application do not limit the execution order of steps S308 and S309.

[0269] After determining the target mode and sending the first UEIRI to the access network equipment, the UE can determine whether the target mode is the first mode during the waiting period corresponding to the first UEIRI. It can be understood that the UE determines whether the target mode is the first mode in order to determine whether to skip PDCCH monitoring and not perform PDCCH monitoring associated with the first UEIRI.

[0270] When the target mode is mode one, the UE skips PDCCH monitoring and does not perform PDCCH monitoring associated with the first UEIRI. When the target mode is mode two, three, or four, the UE does not skip or partially skips PDCCH monitoring and performs PDCCH monitoring associated with the first UEIRI. Therefore, to save signaling overhead and power consumption, the UE can determine whether to skip PDCCH monitoring based on the target mode.

[0271] If the target mode is the first mode, proceed to step S310. If the target mode is the second, third, or fourth mode, proceed to step S311.

[0272] S310, UE skips PDCCH monitoring and does not perform PDCCH monitoring associated with the first UEIRI.

[0273] When the target mode is the first mode, the UE can skip PDCCH monitoring and not perform PDCCH monitoring associated with the first UEIRI, thereby reducing UE response latency, avoiding the inability to capture DCI, and thus the inability to complete CSI reporting, and improving communication efficiency.

[0274] S311. The UE does not skip PDCCH monitoring and performs PDCCH monitoring associated with the first UEIRI.

[0275] When the target mode is mode two, three, or four, the UE can perform PDCCH monitoring associated with the first UEIRI without skipping PDCCH monitoring. Specifically, in mode two, the UE skips a first number of PDCCH monitoring sessions and partially performs PDCCH monitoring associated with the first UEIRI. In mode three, the UE skips a second number of PDCCH monitoring sessions and partially performs PDCCH monitoring associated with the first UEIRI. In mode four, the UE does not skip PDCCH monitoring and fully performs PDCCH monitoring associated with the first UEIRI. This reduces UE response latency, avoids the inability to capture DCI, and thus prevents the reporting of CSI, thereby improving communication efficiency.

[0276] Optionally, not skipping PDCCH monitoring includes: not skipping PDCCH monitoring on the serving cell associated with the first UEIRI; and performing PDCCH skipping on cells other than the serving cell associated with the first UEIRI among the UE's target serving cells.

[0277] S312. In response to sending the first UEIRI, the UE initializes the mode parameters.

[0278] After sending the first UEIRI, the UE can initialize the mode parameters in response to sending the first UEIRI.

[0279] Optionally, the UE initialization mode parameters may include at least one of the following: defining mode parameters, setting specific values ​​for mode parameters, and setting an initial value for the number of UEIRI transmissions (e.g., setting it to 0). For example, the UE can set the value of each mode parameter in each mode as shown in Table 2.

[0280] S313. The UE determines whether it has successfully received the DCI.

[0281] After the access network device sends the DCI, the UE can determine whether it has successfully received the DCI. It's understandable that the UE's determination of whether it has successfully received the DCI is also to determine whether to send the CSI to the access network device.

[0282] If the UE successfully receives the DCI, proceed to step S314. If the UE fails to receive the DCI, proceed to step S315.

[0283] S314. The UE sends a CSI to the access network equipment.

[0284] Accordingly, the access network equipment receives the CSI sent by the UE.

[0285] If the UE successfully receives the DCI, the UE can send the CSI to the access network equipment.

[0286] Optionally, the UE can clear mode parameters after successfully receiving the DCI. These parameters may include, for example, the first transmission threshold, the second transmission threshold, the maximum duration, the maximum number of transmissions, the preset duration, and the minimum transmission interval.

[0287] S315, UE determines whether the preset conditions are met.

[0288] If the UE fails to receive the DCI, it can determine whether preset conditions are met. Understandably, the UE checks whether the preset conditions are met to determine if the transmission of the first UEIRI failed.

[0289] If the UE meets the preset conditions, proceed to step S312. If the UE does not meet the preset conditions, proceed to step S316.

[0290] If the UE meets the preset conditions, the UE can initialize the mode parameters. That is to say, if the first UEIRI transmission has not failed, it can continue to try PDCCH monitoring.

[0291] Optionally, the UE meeting the preset conditions may include at least one of the following methods: Method 2.1: The number of valid monitoring times for PDCCH monitoring is less than or equal to the threshold of the first time.

[0292] Understandably, before determining whether the effective number of PDCCH monitoring is less than or equal to the first threshold, the UE can first obtain the effective number of PDCCH monitoring.

[0293] In other words, the UE obtains the effective number of PDCCH monitoring. If the UE does not detect DCI within the time period from the start of PDCCH monitoring to the effective number of monitoring being less than or equal to the threshold of the first count, the UE returns to step S312 to initialize the mode parameters.

[0294] Method 2.2: The number of consecutive unserviceable times monitored by PDCCH is less than or equal to the second threshold.

[0295] Understandably, before determining whether the number of consecutive unservice instances monitored by PDCCH is less than or equal to the second threshold, the UE can first obtain the number of consecutive unservice instances monitored by PDCCH.

[0296] In other words, the UE obtains the number of consecutive unservice occurrences monitored by the PDCCH. If the number of consecutive unservice occurrences is less than or equal to the second threshold and no DCI is detected, the UE returns to step S312 to initialize the mode parameters.

[0297] Method 2.3: The duration of the first UEERI is less than or equal to the maximum duration.

[0298] Understandably, before determining whether the duration of the first UEIRI is less than or equal to the maximum duration, the UE may first respond by sending the first UEIRI, start the first timer, and determine whether the duration of the first UEIRI is less than or equal to the maximum duration by comparing the running time of the first timer with the maximum duration.

[0299] In other words, in response to sending the first UEIRI, the UE starts the first timer. If the duration of the first timer is less than or equal to the maximum duration and no DCI is detected, the UE returns to step S312 to initialize the mode parameters.

[0300] Understandably, the threshold values ​​for the first count, the second count, and the maximum duration differ depending on the target mode. Referring to Table 2 above, if the target mode is mode two, the threshold value for the first count is 3, the threshold value for the second count is 8, and the maximum duration is 40 time slots. If the target mode is mode three, the threshold value for the first count is 3, the threshold value for the second count is 1, and the maximum duration is 16 time slots. If the target mode is mode four, the threshold value for the first count is 5, the threshold value for the second count is 0, and the maximum duration is 8 time slots.

[0301] S316, The UE determines that the PDCCH monitoring associated with the first UEIRI has failed.

[0302] If the UE does not meet the preset conditions, the UE can determine that the PDCCH monitoring associated with the first UEIRI has failed, that is, the transmission of the first UEIRI fails in a single attempt.

[0303] Correspondingly, optionally, the UE not meeting the preset conditions may include at least one of the following methods: Method 3.1: The number of effective monitoring times of PDCCH monitoring is greater than the threshold of the first time.

[0304] In other words, the UE obtains the number of valid PDCCH monitoring attempts. If the UE does not detect DCI within the time period from the start of PDCCH monitoring until the number of valid monitoring attempts exceeds the threshold for the first attempt, the UE determines that the PDCCH monitoring associated with the first UEIRI has failed.

[0305] Method 3.2: The number of consecutive unservice failures monitored by PDCCH exceeds the threshold of the second count.

[0306] In other words, the UE obtains the number of consecutive unservice occurrences monitored by the PDCCH. If the number of consecutive unservice occurrences exceeds the second threshold and no DCI is detected, the UE determines that the PDCCH monitoring associated with the first UEIRI has failed.

[0307] Method 3.3: The duration of the first UEERI is less than or equal to the maximum duration.

[0308] In other words, the UE starts a first timer in response to sending the first UEIRI. If the runtime of the first timer exceeds the maximum duration and no DCI is detected, the UE determines that the PDCCH monitoring associated with the first UEIRI has failed.

[0309] Optionally, after determining that the PDCCH monitoring associated with the first UEIRI has failed, the UE can clear the mode parameters related to this first UEIRI. For example, the first count threshold, the second count threshold, the maximum duration, the minimum transmission interval, etc.

[0310] S317. The UE determines whether the number of times it sends the first UEIRI is less than the maximum number of times it can send.

[0311] After the UE determines that the PDCCH associated with the first UEIRI has failed to be monitored, it can determine whether the number of times the first UEIRI has been sent is less than the maximum number of times it can be sent. In other words, it can determine whether multiple attempts to send the first UEIRI have failed.

[0312] Understandably, the maximum number of transmissions varies depending on the target mode. Referring to Table 2 above, the maximum number of transmissions is 2 for the second target mode, 2 for the third target mode, and 3 for the fourth target mode.

[0313] If the number of times the UE transmits the first UEIRI is less than the maximum number of transmissions, proceed to step S319. If the number of times the UE transmits the first UEIRI is greater than or equal to the maximum number of transmissions, proceed to step S318.

[0314] S318. After a preset time, the UE exits and triggers the CSI report.

[0315] If the number of times the UE sends the first UEIRI is greater than or equal to the maximum number of times it can send, it means that the UE has tried to send the first UEIRI multiple times but still has not successfully received the DCI. In this case, the UE can exit the reporting of triggered CSI after a preset time, that is, give up sending CSI to the access network equipment.

[0316] Understandably, the preset duration varies depending on the target mode. Referring to Table 2 above, the preset duration is 160 time slots for the second target mode, 80 time slots for the third target mode, and 40 time slots for the fourth target mode.

[0317] S319, UE starts the second timer.

[0318] The runtime of the second timer is the minimum transmission interval between two consecutive transmissions of UEIRI.

[0319] Understandably, different target modes have different preset durations. Referring to Table 2 above, if the target mode is mode two, the minimum transmission interval is 80 time slots. If the target mode is mode three, the minimum transmission interval is 12 time slots. If the target mode is mode four, the minimum transmission interval is 8 time slots.

[0320] If the number of times the UE sends the first UEIRI is less than the maximum number of times it can send the first UEIRI indicates that the number of times the UE sends the first UEIRI has not yet reached the maximum number of times it can send the first UEIRI. In other words, if the number of times it sends the first UEIRI is greater than or equal to the maximum number of times it can send the first UEIRI again, the UE can start the second timer.

[0321] S320. In response to the end of the second timer, the UE retransmits the first UEIRI to the access network device.

[0322] After the second timer starts, the UE can retransmit the first UEIRI to the access network device in response to the end of the second timer.

[0323] Optionally, the transmission count of the first UEIRI is incremented by 1 each time it is successfully transmitted. If PDCCH monitoring is successful, the transmission count of the first UEIRI is reset to 0.

[0324] Understandably, after retransmitting the first UEIRI to the access network device, the UE can return to step S306 and execute steps S306-S320 again until the number of times the UE sends the first UEIRI is greater than or equal to the maximum number of transmissions, or the UE successfully receives the DCI. It should be noted that before retransmitting the first UEIRI to the access network device, the UE can reconfirm its current status information, update the target mode based on the reconfirmed status information, and indicate the newly confirmed target mode to the access network device when retransmitting the first UEIRI.

[0325] The communication method 300 described in steps S306-S320 above allows the access network device to determine whether to send DCI to the UE based on the target mode, avoiding blindly sending DCI to the UE, saving signaling overhead and power consumption, thereby improving communication efficiency. On the other hand, the UE can also determine whether to perform PDCCH monitoring based on the target mode, reducing UE response latency and avoiding the inability to capture DCI, thus preventing the inability to report CSI, thereby improving communication efficiency.

[0326] The communication method 300 described in steps S301-S320 above allows the access network device to pre-configure at least one mode for when a PDCCH skip occurs during the waiting period corresponding to the UEIRI. This enables the UE to determine a target mode corresponding to the status information based on the acquired status information and the at least one mode configured by the access network device, and then send the target mode and the first UEIRI to the access network device. In this way, on the one hand, the access network device can determine whether to send a DCI to the UE based on the target mode, avoiding blindly sending DCIs to the UE, saving signaling overhead and power consumption, thereby improving communication efficiency. On the other hand, the UE can also determine whether to perform PDCCH monitoring based on the target mode, reducing UE response latency and avoiding the inability to capture DCIs, thus preventing the inability to report CSIs, thereby improving communication efficiency.

[0327] It should be understood that, attached Figure 1 To be continued Figure 4 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on the accompanying drawings. Figure 1 To be continued Figure 5 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0328] The above text, combined with the appendix Figure 1 To be continued Figure 4 The present application describes in detail the communication method provided in its embodiments. The following will refer to the appendix... Figure 5 To be continued Figure 6 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0329] In the embodiments described above, the UE can execute some or all of the steps in each embodiment; the access network device can execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application can also perform other operations or variations of various operations. Furthermore, the steps can be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0330] Appendix Figure 5 This is a schematic block diagram of a communication device provided in an embodiment of this application. (See attached diagram) Figure 5 As shown, the communication device 500 may include a communication module 510. The communication module 510 can implement corresponding communication functions, which can be internal communication functions of the communication device 500 or communication functions between the communication device 500 and other devices. Optionally, the communication module 510 may also be referred to as a communication interface or transceiver module. Optionally, the communication device 500 further includes a processing module 520. The processing module 520 can implement corresponding processing functions.

[0331] Optionally, the communication device 500 further includes a storage module 530, which can be used to store instructions and / or data; the processing module 520 can read the instructions and / or data in the storage module 530 so that the communication device 500 can implement the aforementioned method embodiments.

[0332] In one possible design, the communication device 500 may correspond to the UE in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the UE. The communication device 500 can be used to execute the steps or processes performed by the UE in any of the above method embodiments.

[0333] For example, the communication module 510 is used to execute configuration information sent by the access network device for configuring at least one mode for handling conflicts when a PDCCH skip occurs during the waiting period corresponding to the UEIRI. In response to detecting a report requiring CSI triggering, based on the configuration information and status information, a communication method is used to send a report for triggering CSI and a first UEIRI indicating a target mode corresponding to the UE's status information in at least one mode to the access network device. Different modes are applicable to different status information. The UEIRI is used to indicate that the UE needs to trigger CSI. The waiting period corresponding to the UEIRI includes the period from sending the UEIRI to waiting for the access network device to send a DCI.

[0334] The processing module 520 is used to execute the communication method for obtaining the status information of the UE.

[0335] Optionally, the processing module 520 may also be connected to the functional module to perform some or all of the steps in the various embodiments.

[0336] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0337] In one possible design, the communication device 500 may correspond to the access network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the access network device. The communication device 500 can be used to perform the steps or processes performed by the access network device in any of the above method embodiments.

[0338] For example, communication module 510 is used to perform a communication method that sends configuration information to the UE for configuring at least one mode for handling conflicts when a PDCCH skip occurs during the waiting period corresponding to the UEIRI. It also receives a report from the UE to trigger CSI and a first UEIRI indicating a target mode corresponding to the UE's state information in at least one mode. The target mode is determined by the UE in response to detecting a report requiring CSI triggering, based on the configuration information and the state information obtained by the UE. Different modes are applicable to different state information. The UEIRI is used to indicate that the UE needs to trigger CSI. The waiting period corresponding to the UEIRI includes the period from sending the UEIRI to waiting for the DCI sent by the access network device.

[0339] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0340] Appendix Figure 6 This is another schematic block diagram of the communication device 600 provided in the embodiments of this application. The communication device 600 may be a chip, chip system, or processor, etc., in an access network device or core network device that implements the above-described methods. The communication device 600 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0341] As attached Figure 6 As shown, the communication device 600 may include one or more processors 610, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 610 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 600 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0342] In an alternative design, the processor 610 may also store instructions and / or data that can be executed by the processor 610 to cause the communication device 600 to perform the methods described in the above method embodiments.

[0343] In another alternative design, the communication device 600 may include a communication interface 630 for implementing receiving and transmitting functions. For example, the communication interface 630 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0344] Optionally, the communication device 600 may include one or more memories 620, which may store instructions that can be executed on the processor 610, causing the communication device 600 to perform the methods described in the above method embodiments. Optionally, the memories 620 may also store data. Optionally, the processor 610 may also store instructions and / or data. The processor 610 and the memories 620 may be provided separately or integrated together.

[0345] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0346] In one implementation, the communication device 600 may correspond to the UE in the above method embodiments and may be used to execute the various steps and / or processes executed by the UE in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 620, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the UE.

[0347] In another implementation, the communication device 600 may correspond to the access network device in the above method embodiments, and may be used to execute the various steps and / or processes executed by the access network device in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 620, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the access network device.

[0348] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

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

[0350] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0351] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0352] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned UE and access network device.

[0353] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the UE and access network device in any of the foregoing method embodiments.

[0354] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes performed by the UE and access network device in any of the foregoing method embodiments.

[0355] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0356] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0357] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

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

[0359] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0360] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, Applied to a terminal device (UE); the method includes: The system receives configuration information sent by the access network device. This configuration information is used to configure at least one mode. Different modes are used to specify different conflict handling methods when a Physical Downlink Control Channel (PDCCH) skips during the waiting period corresponding to the UEIRI (UE Information Request Indication). Different modes are applicable to different state information. The UEIRI is used to indicate that the UE needs to trigger the reporting of Channel State Information (CSI). The waiting period corresponding to the UEIRI includes the period from sending the UEIRI to waiting for the downlink control information (DCI) sent by the access network device. Obtain the status information of the UE; In response to detecting a report that requires triggering CSI, a first UEIRI is sent to the access network device based on the configuration information and the status information; the first UEIRI is used to trigger the CSI report and to indicate a target mode; the target mode is one of the at least one modes that corresponds to the status information of the UE.

2. The communication method according to claim 1, characterized in that, The status information includes at least one of the following: Device type, service type, power consumption status, blind detection capability constraints, mobility status, link change status, or beam reporting requirements.

3. The communication method according to claim 1 or 2, characterized in that, The at least one mode includes at least one of the following: First mode; the first mode is used to specify that PDCCH skipping is fully performed during the waiting period corresponding to the UEIRI; Second mode; the second mode is used to specify that a first number of PDCCH skips are allowed during the waiting period corresponding to the UEIRI; A third mode; the third mode is used to specify that a second number of execution PDCCH skips are allowed during the waiting period corresponding to the UEIRI; the second number is less than the first number; Fourth mode; the fourth mode is used to specify that PDCCH skipping is not performed during the waiting period corresponding to the UEERI.

4. The communication method according to claim 3, characterized in that, The configuration information is also used to configure the mode parameters corresponding to each mode.

5. The communication method according to claim 4, characterized in that, The mode parameters include at least one of the following: The first count threshold related to the effective number of monitoring sessions in PDCCH monitoring; The second threshold related to the number of consecutive unserviceable occurrences monitored by PDCCH; Maximum duration for sending UEIRI; The maximum number of times UEIRI can be sent; The preset time after UEIRI has reached the maximum number of transmissions; or, The minimum transmission interval between two consecutive UEIRI transmissions.

6. The communication method according to claim 5, characterized in that, The method further includes: During the waiting period corresponding to the first UEIRI, if the UE is in the PDCCH skipping state, the PDCCH monitoring is skipped or not skipped based on the target mode.

7. The communication method according to claim 6, characterized in that, The decision to skip or not skip PDCCH monitoring based on the target pattern includes: If the target mode is the first mode, skip the PDCCH monitoring and do not perform the PDCCH monitoring associated with the first UEERI; or, When the target mode is the second mode, skip the first number of PDCCH monitoring sessions and partially perform the PDCCH monitoring associated with the first UEIRI; or, If the target mode is the third mode, skip the second number of PDCCH monitoring sessions and partially perform the PDCCH monitoring associated with the first UEIRI; or, When the target mode is the fourth mode, the PDCCH monitoring is not skipped, and the PDCCH monitoring associated with the first UEERI is fully executed.

8. The communication method according to claim 7, characterized in that, When the target mode is the second mode, the third mode, or the fourth mode, before deciding whether to skip PDCCH monitoring based on the target mode, the method further includes: Receive DCI sent by the access network device.

9. The communication method according to claim 8, characterized in that, The method further includes: Obtain the effective monitoring count of the PDCCH; If no DCI is detected within the time period from the start of PDCCH monitoring to the number of valid monitoring sessions exceeding the first threshold, it is determined that the PDCCH monitoring associated with the first UEIRI has failed.

10. The communication method according to claim 9, characterized in that, The method further includes: Obtain the number of consecutive service outages monitored by the PDCCH; In response to the number of consecutive unserviceable events exceeding the second threshold, it is determined that the PDCCH monitoring associated with the first UEIRI has failed.

11. The communication method according to claim 10, characterized in that, The method further includes: In response to sending the first UEIRI, start the first timer; In response to the first timer's runtime being greater than the maximum duration, it is determined that the PDCCH monitoring associated with the first UEERI has failed.

12. The communication method according to claim 11, characterized in that, In the event that the PDCCH monitoring associated with the first UEIRI fails, the method further includes: If the number of times the first UEIRI is sent is less than the maximum number of times, retransmit the first UEIRI; or, If the number of times the first UEIRI is sent is greater than or equal to the maximum number of times it can be sent, the UE will exit after the preset time period, triggering the reporting of the CSI.

13. The communication method according to claim 12, characterized in that, The retransmission of the first UEIRI includes: In response to the failure of PDCCH monitoring associated with the first UEIRI, a second timer is started; After the second timer finishes running, the first UEIRI is retransmitted; the running time of the second timer is the minimum transmission interval between two consecutive transmissions of UEIRI.

14. The communication method according to claim 13, characterized in that, When the first UEIRI is being transmitted for the first time, the method further includes: In response to sending the first UEIRI, the mode parameters are initialized.

15. The communication method according to claim 14, characterized in that, The method further includes: Each time the first UEIRI is successfully transmitted, the number of times the first UEIRI has been transmitted is incremented by 1. If the PDCCH monitoring is successful, the number of times the first UEIRI has been sent is set to 0.

16. The communication method according to any one of claims 6-15, characterized in that, The non-skipping of PDCCH monitoring includes: On the serving cell associated with the first UEIRI, PDCCH monitoring is not skipped; PDCCH skipping is performed on cells other than the serving cell associated with the first UEIRI in the target serving cell of the UE.

17. A communication method, characterized in that, Applied to access network equipment; the method includes: Configuration information is sent to the terminal device (UE); the configuration information is used to configure at least one mode; different modes are used to specify different conflict handling methods when the UE is in a physical downlink control channel (PDCCH) skipping during the waiting period corresponding to the UEIRI reporting request; different modes are applicable to different state information; the UEIRI is used to indicate that the UE needs to trigger the reporting of channel state information (CSI); the waiting period corresponding to the UEIRI includes the period from sending the UEIRI to waiting for the downlink control information (DCI) sent by the access network device; The system receives a first UEIRI sent by the UE; the first UEIRI is used to trigger the reporting of CSI and to indicate a target mode; the target mode is determined by the UE in response to detecting a report that requires triggering CSI, based on the configuration information and the status information obtained by the UE; the target mode is one of the at least one modes that corresponds to the status information of the UE.

18. The communication method according to claim 17, characterized in that, The status information includes at least one of the following: The UE's device type, service type, power consumption status, blind detection capability constraints, mobility status, link change status, or beam reporting requirements.

19. The communication method according to claim 17 or 18, characterized in that, The at least one mode includes one of the following: First mode; the first mode is used to specify that PDCCH skipping is fully performed during the waiting period corresponding to the UEIRI; Second mode; the second mode is used to specify that a first number of PDCCH skips are allowed during the waiting period corresponding to the UEIRI; A third mode; the third mode is used to specify that a second number of execution PDCCH skips are allowed during the waiting period corresponding to the UEIRI; the second number is less than the first number; Fourth mode; the fourth mode is used to specify that PDCCH skipping is not performed during the waiting period corresponding to the UEERI.

20. The communication method according to claim 19, characterized in that, The method further includes: Based on the target mode, determine whether to send DCI to the UE.

21. The communication method according to claim 20, characterized in that, The step of determining whether to send DCI to the UE based on the target mode includes: If the target mode is the first mode, DCI is not sent to the UE; When the target mode is the second mode, the third mode, or the fourth mode, DCI is sent to the UE.

22. The communication method according to any one of claims 17-18 and 20-21, characterized in that, The configuration information is also used to configure the mode parameters corresponding to each mode.

23. The communication method according to claim 22, characterized in that, The mode parameters include at least one of the following: The first count threshold related to the effective number of monitoring sessions in PDCCH monitoring; The second threshold related to the number of consecutive unserviceable occurrences monitored by PDCCH; Maximum duration for sending UEIRI; The maximum number of times UEIRI can be sent; The preset time after UEIRI has reached the maximum number of transmissions; or, The minimum transmission interval between two consecutive UEIRI transmissions.

24. A communication device, characterized in that, The device includes a processor and a memory, wherein the memory stores instructions, and when the processor executes the instructions, the communication device performs the communication method as described in any one of claims 1-16, or the communication method as described in any one of claims 17-23.

25. A computer program product, characterized in that, include: A computer program, when the computer program is run, causes a computer to perform the communication method as described in any one of claims 1-16, or the communication method as described in any one of claims 17-23.

26. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the communication method as described in any one of claims 1-16, or the communication method as described in any one of claims 17-23.

27. A communication system, characterized in that, Includes the communication device as described in claim 24.

28. A chip system, characterized in that, The chip system includes one or more processors, which are configured to retrieve and execute instructions stored in memory, such that the communication method as described in any one of claims 1-16, or the communication method as described in any one of claims 17-23, is executed.

Images