Communication method and communication apparatus

Abstract

Provided are a communication method and a communication device, which are applied to the field of communication. The communication method comprises: in the case where it is determined that a PHR abnormality occurs, the UE reports information related to the PHR abnormality to the network side, so that the network side can immediately repair the PHR abnormality, or optimizes based on the information related to the PHR abnormality reported by the UE, thereby minimizing the negative influence caused by the PHR abnormality.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Technology

[0002] Power headroom report (PHR) is the process by which user equipment (UE) reports its power headroom to the network. PHR can be used to measure uplink coverage limitations. PHR directly reflects the quality of the wireless environment in which the UE is located. However, if there are abnormalities in the PHR reporting process, such as the UE not reporting PHR for an extended period, the network will be unable to obtain the PHR, thus affecting the network's ability to perform closed-loop power control of the uplink (UL) based on the PHR, and consequently impacting resource scheduling. Summary of the Invention

[0003] In view of this, this application provides a communication method, communication device, chip system, computer-readable storage medium, computer program product, and communication system that enable network devices to be aware of PHR anomalies, so that network devices can make corresponding decisions based on the anomalies reported by the PHR.

[0004] In a first aspect, a communication method is provided, which can be executed by a user equipment (UE), a component configured in the UE (such as a circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of a terminal device. This application does not limit the scope of this method.

[0005] Specifically, the method includes: the UE determining that a Power Headroom Report (PHR) anomaly has occurred; and sending a first message to a network device, the first message being used to notify the network device of information related to the Power Headroom Report (PHR) anomaly.

[0006] Based on the above technical solution, in the event of a PHR anomaly, compared with the technical solutions in related technologies that result in a prolonged absence of PHR after an anomaly, in this embodiment of the application, the UE reports information related to the PHR anomaly to the network side so that the network side can immediately repair the PHR anomaly, or optimize the PHR configuration parameters based on the information related to the PHR anomaly reported by the UE, thereby minimizing the negative impact caused by the PHR anomaly.

[0007] This application does not specify the exact implementation method for the UE to determine that a PHR anomaly has occurred. A UE determining that a PHR anomaly has occurred can be understood as: the UE failing to report a PHR for an extended period, the network device's configured power value not meeting power requirements, and the service's evaluation quality indicators not meeting requirements.

[0008] For example, a UE determines that a PHR anomaly has occurred if the following conditions are met simultaneously: no PHR is reported within a first preset duration; the UE receives a transmit power indication from the network device that is lower than the power threshold; and the duration of the uplink bit error rate is greater than or equal to a second preset duration.

[0009] In other words, if all three conditions mentioned above are met simultaneously, it indicates that the PHR anomaly has severely impacted the user experience. The simultaneous fulfillment of these three conditions can also be defined as an abnormal event, or a PHR anomaly event.

[0010] In one possible implementation, after the UE sends a first message to the network device, the method further includes: the UE receiving a second message from the network device, the second message being used to reconfigure the PHR configuration parameters. That is, after reporting a PHR anomaly to the network device, the UE can receive optimized PHR configuration parameters from the network device, thereby enabling it to perform PHR reporting based on the optimized PHR configuration parameters. Compared to related technologies where PHR is missing for an extended period after an anomaly occurs, the UE in this embodiment can report PHR based on the reconfigured PHR configuration parameters, which helps the network device perform UL closed-loop power control based on the PHR reported by the UE, thereby enabling resource scheduling.

[0011] For example, the second message includes a path loss change threshold or the duration of a first timer (e.g., the prohibitPHR-Timer); the method further includes: the UE performing PHR reporting based on the second message. Based on the adjusted path loss change threshold or the duration of the first timer, the UE will be more likely to trigger PHR, thereby enabling rapid correction of erroneous power control parameters.

[0012] The first message mentioned above is used by the UE to notify the network device of information related to the PHR anomaly, and can be understood from different perspectives.

[0013] The first interpretation is based on the UE's (User Equipment) requirements. That is, when the UE detects a PHR (Programmable Response Time) anomaly, it immediately reports information related to the PHR anomaly to the network device via a first message, hoping the network device can quickly adjust the relevant PHR configuration parameters to rapidly resolve the fault.

[0014] For example, the first message is a first user equipment assistance information (UAI) message, which has a higher priority than the second UAI message; or, the first message is a second UAI message, which includes first information indicating that the second UAI message is an emergency UAI message.

[0015] Optionally, information related to PHR anomalies in the power headroom report includes one or more of the following: the most recent path loss change value, and the duration of the missing PHR. In other words, the UE reports information related to PHR anomalies to the network device so that the network device can adjust the corresponding configuration parameters based on the UE's recommendations.

[0016] The second interpretation is based on the needs of the network device side. Specifically, by receiving the first message sent by one or more UEs and collecting PHR anomaly information over a long period, network devices can obtain a large amount of information for statistical analysis, thereby preventing the triggering of PHR anomalies from the root cause. This helps improve the overall network performance and comprehensively optimize the user's service experience.

[0017] Optionally, before determining that a Power Headroom Report (PHR) anomaly has occurred, the method further includes: the UE receiving a first RRC message from the network device, the first RRC message being used to configure the UE to record information related to the PHR anomaly; the method further includes: recording information related to the PHR anomaly based on the first RRC message.

[0018] Therefore, after receiving the first RRC message sent by the network, the UE records the PHR anomaly so that it can be reported to the network equipment later, providing a data basis for the network equipment to perform overall optimization.

[0019] For example, as one implementation, the UE sends a first message to the network device, including: the UE sending a second RRC message to the network device, the second RRC message including indication information, the indication information being used to indicate that the UE has recorded PHR anomaly-related information. The second RRC message can be used in response to the aforementioned first RRC message. Here, the first message sent by the UE to the network device, which is the second RRC message, may include indication information to indicate to the network device that the UE has recorded PHR anomaly-related information (or available PHRF information) for the network device to use. In this way, the network device can request PHR anomaly-related information from the UE when needed.

[0020] In one possible implementation, the method further includes: the UE receiving a request message from the network device, the request message being used to request the UE to send information related to the PHR anomaly; wherein, the UE sending a first message to the network device includes: sending a request-response message to the network device according to the request message, the request-response message being the first message. Here, the first message sent by the UE to the network device is a request-response message, which provides greater flexibility in the sending method.

[0021] It should be noted that the above request messages can be sent periodically by network devices or sent on demand; there are no specific limitations on this.

[0022] Optionally, the first RRC message is also used to configure the maximum number of times; the method further includes: if the number of PHR anomalies is greater than or equal to the maximum number of times, the UE updates the recorded PHR anomaly information based on a queue method.

[0023] Optionally, after sending the first message to the network device, the method further includes: the UE deleting the reported anomaly information. Therefore, deleting the reported PHR anomaly information helps reduce the use of unnecessary storage space.

[0024] For example, the information related to PHR anomalies in the power margin report includes one or more of the following: the identifier of the serving cell where the PHR anomaly occurred, the recovery time of the PHR anomaly, the number of PHR anomalies, the signal quality measurement value of the serving cell where the PHR anomaly occurred, the identifier of the neighboring cell when the PHR anomaly occurred, the signal quality measurement value of the neighboring cell when the PHR anomaly occurred, the UE's location information when the PHR anomaly occurred, and the duration from the occurrence of the PHR anomaly to the current time. Therefore, the UE can report various PHR anomaly-related information to the network device, providing a data basis for the network device to reconfigure PHR parameters or perform overall optimization.

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

[0026] Specifically, the method includes: a network device receiving a first message from one or more user equipment (UEs) for notifying information related to power headroom report (PHR) anomalies; and determining PHR configuration parameters based on the first message.

[0027] Based on the above technical solution, compared with the related technical solutions that result in a long period of PHR absence after a PHR anomaly, in the case of a PHR anomaly, the network device in this application embodiment can immediately repair the PHR anomaly by receiving information related to the PHR anomaly reported by the UE, or optimize the PHR configuration parameters based on the information related to the PHR anomaly reported by the UE, thereby minimizing the negative impact caused by the PHR anomaly.

[0028] In one possible implementation, the method further includes: the network device sending a second message to the UE, the second message being used to reconfigure the configuration parameters of the PHR. Therefore, the network device can send the optimized PHR configuration parameters to the UE, so that the UE can perform PHR reporting based on the optimized PHR configuration parameters.

[0029] For example, the second message includes a path loss change threshold or the duration of a first timer (e.g., the prohibitPHR-Timer); the method further includes: the UE performing PHR reporting based on the second message. Based on the adjusted path loss change threshold or the duration of the first timer, the UE will be more likely to trigger PHR, thereby enabling rapid correction of erroneous power control parameters.

[0030] For a description of the first message, please refer to the description in the first aspect. For the sake of brevity, it will not be elaborated here. Optionally, the first message is a first user equipment auxiliary information (UAI) message, which has a higher priority than the second UAI message; or, the first message is a second UAI message, which includes first information used to indicate that the second UAI message is an emergency UAI message.

[0031] Optionally, information related to abnormal Power Headroom Report (PHR) includes one or more of the following: the most recent path loss change value, and the duration of the missing PHR. In other words, the network device receives information from the UE related to PHR anomalies, specifically abnormal PHR configuration parameters, and can adjust the corresponding configuration parameters based on the UE's suggestions.

[0032] In one implementation, the network device obtains the first message sent by one or more UEs and collects PHR anomaly information over a long period of time. This allows for the collection of a large amount of information for statistical analysis, thereby preventing the triggering of PHR anomalies from the root cause. This helps to improve the overall performance of the network and comprehensively optimize the user's service experience.

[0033] For example, the network device sends a first RRC message, which is used to configure the UE to record information related to PHR anomalies. That is, the network device can configure the UE to record information related to PHR anomalies so that it can obtain this information from the UE side later.

[0034] Optionally, the method further includes: the network device receiving a second RRC message from one or more UEs, the second RRC message including indication information indicating that the UE has recorded PHR anomaly-related information. Therefore, the network device can determine from the indication information in the second RRC message that the UE has recorded available PHRF information, i.e., information related to the occurrence of PHR, and can then request this information from the UE when needed to obtain a large amount of data for statistical analysis.

[0035] As one possible implementation, the network device sends a request message to one or more UEs, the request message being used to request the UEs to send information related to PHR anomalies; wherein, receiving a first message from one or more UEs includes: receiving a request response message from one or more UEs, the request response message being the first message.

[0036] It should be noted that the aforementioned request messages can be sent periodically by the network device or sent on demand; there is no specific limitation in this regard. For example, the network device periodically sends request messages to one or more UEs.

[0037] Optionally, the first RRC message is also used to configure the maximum number of times.

[0038] Optionally, the information related to the power margin report PHR anomaly includes one or more of the following: the identifier of the serving cell where the PHR anomaly occurred, the recovery time of the PHR anomaly, the number of PHR anomalies, the signal quality measurement value of the serving cell where the PHR anomaly occurred, the identifier of the neighboring cell when the PHR anomaly occurred, the signal quality measurement value of the neighboring cell when the PHR anomaly occurred, the UE's location information when the PHR anomaly occurred, and the time elapsed from the occurrence of the PHR anomaly to the current time.

[0039] Therefore, network devices can receive various information related to PHR anomalies reported by UEs, obtain more comprehensive information, and help reconfigure PHR parameters or perform overall optimization.

[0040] Thirdly, a communication apparatus is provided, comprising modules or units for performing the method in any possible implementation of the first aspect described above.

[0041] In one design, the communication device may include modules that perform the methods / operations / steps / actions described in the foregoing aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0042] In one design, the communication device is a communication chip, which may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0043] In another design, the communication device is a communication equipment, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0044] In another design, the communication device is used to perform the method in any possible implementation of the first aspect described above. The communication device may be configured in the UE, or the communication device itself may be the UE.

[0045] Fourthly, a communication apparatus is provided, comprising modules or units for performing the method in any possible implementation of the second aspect described above.

[0046] In one design, the communication device may include modules that perform the methods / operations / steps / actions described in the foregoing aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0047] In one design, the communication device is a communication chip, which may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0048] In another design, the communication device is a communication equipment, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0049] In another design, the communication device is used to perform the method in any possible implementation of the second aspect described above. The communication device may be configured in the network device described above, or the communication device itself may be a network device.

[0050] Alternatively, the network device can be an access network device (e.g., a gNB), or the network device can be a network element in the core network.

[0051] Fifthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0052] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0053] In another implementation, the communication device is a chip configured in the UE. When the communication device is a chip configured in the UE, the communication interface can be an input / output interface.

[0054] In a sixth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the second aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0055] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0056] In another implementation, the communication device is a chip configured in a network device. When the communication device is a chip configured in a network device, the communication interface can be an input / output interface.

[0057] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute a method in any possible implementation of any aspect.

[0058] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0059] Eighthly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method in any possible implementation of any of the preceding aspects.

[0060] Optionally, the processor may be one or more, and the memory may be one or more.

[0061] Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

[0062] In specific implementation, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. The embodiments of this application do not limit the type of memory or the way the memory and processor are set.

[0063] It should be understood that the relevant data interaction process, such as sending indication information, can be the process of the processor outputting indication information, and receiving capability information can be the process of the processor receiving input capability information. Specifically, the data output by the processor can be sent to the transmitter, and the input data received by the processor can come from the receiver. Here, the transmitter and receiver can be collectively referred to as a transceiver.

[0064] The processing device mentioned in the eighth aspect above can be one or more chips. The processor in the processing device can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can be integrated into the processor or located outside the processor and exist independently.

[0065] Ninthly, 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 method in any possible implementation of any of the above aspects.

[0066] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the method in any possible implementation of any of the above aspects.

[0067] Eleventhly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

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

[0069] In a twelfth aspect, a communication system is provided, including the aforementioned UE and network device.

[0070] Optionally, the communication system may also include other devices that communicate with the UE and / or network devices. Attached Figure Description

[0071] Figure 1 This is an example diagram of a communication system;

[0072] Figure 2 This is an example diagram of an access network device;

[0073] Figure 3 This is an example interaction diagram of the communication method according to an embodiment of this application;

[0074] Figure 4A This is another interactive example diagram of the communication method according to an embodiment of this application;

[0075] Figure 4B This is an example where the first message is an urgent UAI message;

[0076] Figure 5 This illustrates yet another interactive flowchart of the communication method according to an embodiment of this application;

[0077] Figure 6 This is an example of a request message in an embodiment of this application;

[0078] Figure 7 This is an example of a PHRF report message in an embodiment of this application;

[0079] Figure 8 This is another interactive example diagram of the communication method according to an embodiment of this application;

[0080] Figure 9 This is a schematic block diagram of the communication device provided in the embodiments of this application;

[0081] Figure 10 This is another schematic block diagram of the communication device provided in the embodiments of this application;

[0082] Figure 11 This is a structural example diagram of an electronic device according to an embodiment of this application. Detailed Implementation

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

[0084] In this application embodiment, "multiple" can be understood as "at least two"; "multiple items" can be understood as "at least two items".

[0085] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or the order of execution, and that the words "first" and "second" do not necessarily imply that they are different.

[0086] This application can be applied to communication systems. Mobile communication systems include, but are not limited to, the following systems: Long Term Evolution (LTE) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5th Generation (5G) systems or new radio (NR) systems and future mobile communication systems, vehicle-to-X (V2X) systems, where V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), etc., Long Term Evolution-Vehicle (LTE-V) technology for vehicle-to-everything (V2V), vehicle-to-everything (V2X), machine-type communication (MTC), Internet of Things (IoT), Long Term Evolution-Machine (LTE-M) technology for machine-to-machine (M2M), etc.

[0087] This application can also be applied to systems that integrate mobile communication systems and satellite communication systems. Satellite communication systems include, but are not limited to, non-terrestrial network (NTN) systems such as high altitude platform station (HAPS) communication, for example, the Global Navigation Satellite System (GNSS). Optionally, satellite communication systems include geostationary orbit (GEO) satellites and non-geostationary earth orbit (NGEO) satellites; or various terrestrial network (TN) systems.

[0088] Figure 1 This is a schematic diagram of the architecture of a mobile communication system 1000 applicable to embodiments of this application. For example... Figure 1 As shown, the communication system 1000 includes a wireless access network 100 and a core network 200. The wireless access network 100 may include at least one access network device (such as...). Figure 1 110a and 110b, collectively referred to as 110, may also include at least one terminal (such as...). Figure 1 Terminals 120a-120j (collectively referred to as 120) are connected wirelessly to access network devices 110a and 110b. Access network devices 110a and 110b are connected to the core network 200 wirelessly or via wired connection. The core network devices in the core network and the access network devices in the wireless access network can be different physical devices, or they can be the same physical device integrating core network logical functions and wireless access network logical functions. Terminals can connect to each other wirelessly. Access network devices can connect to each other via wired or wireless connection. Figure 1 This is just an illustration; the communication system may also include other network devices, such as wireless repeaters and / or wireless backhaul devices. Figure 1 (Not shown in the image). Communication systems may support, for example, 3GPP-related cellular systems (e.g., 5G communication systems, communication systems integrating multiple wireless technologies (e.g., communication systems integrating at least two of 2G, 3G, 4G, or 5G technologies), or future-oriented evolution systems), or wireless fidelity (WiFi) systems, or 3GPP-related cellular systems integrating other technologies, or future communication systems, etc.

[0089] In some embodiments, the network device in this application can be an access network device. Access network devices are sometimes also called access nodes. Access network devices have wireless transceiver capabilities for communicating with terminals. Access network devices include, but are not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G mobile communication systems, access network devices or modules of access network devices in Open RAN (ORAN) systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network devices can also be modules or units capable of implementing some of the functions of a base station. 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) as described below. In the ORAN system, CU can also be called O-CU, DU can also be called open (O)-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CUP-UP, and RU can also be called O-RU. The access network equipment can be a macro base station (e.g., Figure 1 110a), micro base stations or indoor stations (such as Figure 1 The access network device (110b) can be a relay node or donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, the access network device can also be a server, wearable device, or vehicle-mounted device. For example, in vehicle-to-everything (V2X) technology, the access network device 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 technology or device form used in the access network device. In this application, the access network device is referred to as a network device; unless otherwise specified, network devices refer to access network devices in this application.

[0090] In some embodiments, the network device in this application may also be a core network device. A core network device is a collective term for various functional entities used to manage users, data transmission, and network device configuration. A core network device may include one or more network elements. For example, in a 5G system, a core network device may include access and mobility management functions (AMF), user plane functions (UPF), and session management functions (SMF), etc.

[0091] The terminal in this application embodiment can also be referred to as: user equipment (UE), terminal equipment, very small aperture terminal (VSAT), station, mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc. UEs can be widely used in various communication scenarios, such as device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearables, smart transportation, or smart cities, etc. A UE can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the device form of the terminal.

[0092] As an example and not a limitation, in this embodiment, the terminal can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0093] In this embodiment, the terminal includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and main memory. The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be a terminal device, or a functional module in the terminal device that can call and execute a program.

[0094] Access network devices and / or terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network devices and terminals. Access network devices and terminal devices can be deployed in the same or different scenarios; for example, both can be deployed on land; or the access network device can be deployed on land, and the terminal device on water, etc., and so on.

[0095] In this embodiment of the application, each element in the communication system can be considered as a network element in the communication system. For example, Figure 1 The helicopter or drone 120i can be configured as a mobile access network device. For terminal devices 120j that access the wireless access network 100 via 120i, terminal device 120i is an access network device; however, for access network device 110a, 120i is a terminal device, meaning that 110a and 120i communicate via a wireless air interface protocol. Alternatively, 110a and 120i can communicate via an interface protocol between access network devices; in this case, relative to 110a, 120i is also an access network device. Therefore, both access network devices and terminal devices can be collectively referred to as communication devices. Figure 1 110a and 110b can be referred to as communication devices with access network equipment functions. Figure 1 The 120a-120j in the text can be referred to as communication devices with terminal equipment functions.

[0096] In the embodiments of this application, the communication device with access network device function can be an access network device, or a module (such as a chip, chip system, or software module) in the access network device, or a control subsystem containing access network device function. For example, a control subsystem containing access network device function can be a control center in scenarios where terminals can be applied, such as smart grids, industrial control, intelligent transportation, or smart cities.

[0097] In the embodiments of this application, the communication device with terminal functionality can be a terminal, a module within a terminal (such as a chip, chip system, modem, or software model), or a device containing terminal functionality. For ease of description, the following embodiments will use a base station or BS, and a terminal or UE as examples.

[0098] Communication between access network devices and terminal devices can follow a specific protocol layer structure. For example, this protocol layer structure may include a control plane protocol layer structure and a user plane protocol layer structure. For instance, the control plane protocol layer structure may include at least one of the following: radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, or physical (PHY) layer, etc. Similarly, the user plane protocol layer structure may include at least one of the following: service data adaptation protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer, or physical layer, etc.

[0099] like Figure 2 As shown, the access network equipment may include a CU and a DU. This design can be referred to as CU and DU separation. Multiple DUs can be centrally controlled by a single CU. As an example, the interface between the CU and DU is called the F1 interface. The control plane (CP) interface can be F1-C, and the user plane (UP) interface can be F1-U. This application does not limit the specific names of each interface. The CU and DU can be divided according to the protocol layer of the wireless network: for example, the functions of the PDCP layer and above (e.g., RRC layer and SDAP layer) are set in the CU, and the functions of the protocol layers below the PDCP layer (e.g., RLC layer, MAC layer and PHY layer) are set in the DU; or, for example, the functions of the protocol layers above the PDCP layer are set in the CU, and the functions of the protocol layers below the PDCP layer are set in the DU, without limitation.

[0100] The above division of CU and DU processing functions according to protocol layers is merely an example; other methods can also be used. For instance, CUs or DUs can be divided into those with more protocol layer functions, or they can be divided into those with partial protocol layer processing functions. For example, some functions of the RLC layer and the protocol layer functions above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of CUs or DUs can be divided according to service type or other system requirements, such as by latency. Functions that need to meet latency requirements can be placed in the DU, while functions that do not need to meet this latency requirement can be placed in the CU.

[0101] Optionally, the CU may have one or more core network functions.

[0102] Optionally, the radio unit (RU) of the DU can be remotely located. The RU has radio frequency (RF) functionality. For example, the DU and RU can be separated at the PHY layer. For instance, the DU can implement higher-level functions in the PHY layer, and the RU can implement lower-level functions. When transmitting, the PHY layer functions may include at least one of the following: adding cyclic redundancy check (CRC) bits, channel coding, rate matching, scrambling, modulation, layer mapping, precoding, resource mapping, physical antenna mapping, or RF transmission functionality. When receiving, the PHY layer functions may include at least one of the following: CRC check, channel decoding, rate matching de-scrambling, demodulation, layer mapping de-mapping, channel detection, resource demapping, physical antenna demapping, or RF reception functionality. The higher-level functions in the PHY layer may include a portion of the PHY layer's functionality, which is closer to the MAC layer; the lower-level functions in the PHY layer may include another portion of the PHY layer's functionality, for example, a portion closer to the RF functionality. For example, higher-level functions in the PHY layer may include adding CRC bits, channel coding, rate matching, scrambling, modulation, and layer mapping, while lower-level functions may include precoding, resource mapping, physical antenna mapping, and RF transmission functions; or, higher-level functions in the PHY layer may include adding CRC bits, channel coding, rate matching, scrambling, modulation, layer mapping, and precoding, while lower-level functions may include resource mapping, physical antenna mapping, and RF transmission functions. For example, higher-level functions in the PHY layer may include CRC checksum, channel decoding, rate matching de-matching, decoding, demodulation, and layer mapping de-matching, while lower-level functions may include channel detection, resource de-mapping, physical antenna de-mapping, and RF reception functions; or, higher-level functions in the PHY layer may include CRC checksum, channel decoding, rate matching de-matching, decoding, demodulation, layer mapping de-matching, and channel detection, while lower-level functions may include resource de-mapping, physical antenna de-mapping, and RF reception functions.

[0103] Optionally, the functions of the CU can be further divided, separating the control plane and the user plane and implementing them through different entities. The separated entities are the control plane CU entity (i.e., the CU-CP entity) and the user plane CU entity (i.e., the CU-UP entity). The CU-CP entity and the CU-UP entity can be connected to the DU respectively. In the embodiments of this application, an entity can be understood as a module or unit, and its form can be a hardware structure, a software module, or a hardware structure plus a software module, without limitation.

[0104] Optionally, any one of CU, CU-CP, CU-UP, DU, and RU can be a software module, a hardware structure, or a combination of software and hardware structures, without limitation. The different entities can exist in the same or different forms. For example, CU, CU-CP, CU-UP, and DU are software modules, and RU is a hardware structure. For the sake of brevity, all possible combinations are not listed here. These modules and the methods they execute are also within the protection scope of the embodiments of this application. For example, when the method of the embodiments of this application is executed by an access network device, it can be specifically executed by at least one of CU, CU-CP, CU-UP, DU, or RU.

[0105] To facilitate understanding of the embodiments of this application, the terminology used in this application will be briefly explained first. For example, the explanation of some terms can also be found in the interpretation of the 3rd Generation Partnership Project (3GPP) standard protocol.

[0106] 1. Power headroom (PH)

[0107] PH can be understood as the remaining power of the UE after completing the current transmission, that is, the power value after subtracting the current transmission power from the maximum transmission power. The maximum transmission power can be configured by the network side for the UE.

[0108] For example, PH is the difference between the maximum allowed transmission power of the UE and the currently estimated transmission power of the physical uplink shared channel (PUSCH). In other words, PH satisfies the following formula:

[0109] PH=UEAllowedMaxTransPower–PuschPower

[0110] In the above formula, UEAllowedMaxTransPower represents the maximum transmission power configured for the UE by the network side; PuschPower represents the transmission power when the UE sends PUSCH.

[0111] In other words, PH represents the transmission power that the UE can use in addition to the transmission power currently used by the PUSCH. The unit of PH is dB. Since the calculation of PH uses the transmission power of the PUSCH, the power margin is calculated in the transmission subframe of the PUSCH. The network side (e.g., the base station) calculates the number of RBs that maintain the maximum power spectral density based on the PHR reported by the UE. The value of PH can be negative or positive. If the value of PH is negative, it means that the network side has scheduled a data transmission rate for the UE that is higher than the data transmission power currently available to the UE. In the next scheduling, the network side may consider reducing the RB resources allocated to the UE. If the value of PH is positive, the network side may choose to increase the number of RBs allocated in the future. For example, the range of PH is [-23dB, +40dB].

[0112] 2. Power Headroom Report (PHR)

[0113] Power Registry (PHR) reporting refers to the process by which the UE reports its power margin to the network side (such as access network equipment). PHR provides the UE with information for power control and scheduling. In other words, PHR can be used to measure uplink coverage limitations, directly reflecting the quality of the wireless environment in which the UE is located.

[0114] As mentioned earlier, the PH value can be positive or negative. The network side can calculate the number of resource blocks (RBs) that maintain the highest power spectral density based on the PHR reported by the UE. If the PH value is positive, the network side can choose to increase the number of RBs allocated subsequently; if the PH value is negative, it means that the current PUSCH transmission power has exceeded the maximum transmission power allowed by the UE, and the network side can consider reducing the number of RBs allocated to the UE in the next scheduling.

[0115] The network side performs uplink closed-loop power control based on information such as PH, SNR or SINR measurement results reported by the UE, thereby enabling reasonable and effective resource scheduling for the UE.

[0116] The PH value is sent through the control unit of the MAC layer. The MAC CE associated with the PHR reporting process can also be called the PHR control unit. The PHR control unit occupies one byte; for example, the high 2 bits are reserved, and the low 6 bits are used to store the 64 PH level values ​​from 0 to 63. Each PH level value corresponds to an actual dB value. Table 1 shows an example of a PHR mapping table. As shown in Table 1 below:

[0117] Table 1

[0118]

[0119] In Table 1, each reported value corresponds to a range of measured values. For example, if the UE needs to report a PH value of -22dB, then the value 1 should be entered in the PHR control unit of the MAC PDU. As another example, if the network side obtains that the UE reports a PHR of POWER_HEADROOM_0, it means that the PH value reported by the UE is within the range of -23 ≤ PH < -22. It should be understood that the mapping relationship shown in Table 1 is only an exemplary description, and the embodiments of this application are not limited thereto.

[0120] 3. Method of reporting PHR

[0121] The UE can report PHR periodically, or it can report PHR when the change in path loss exceeds a path loss change threshold (e.g., denoted as dl-PathlossChange). For periodic PHR reporting, the UE reports periodically based on periodic control parameters. These periodic control parameters are executed through a MAC layer timer.

[0122] Optionally, the MAC layer timers include a disable PHR timer (which may be represented as prohibitPHR-Timer or phr-ProhibitTimer) and a report timer (which may be represented as periodicPHR-Timer).

[0123] The prohibitPHR-Timer is introduced to prevent the UE from frequently sending PHR due to frequent changes in path loss or an excessively low path loss threshold.

[0124] The periodicPHR-Timer defines the reporting period for UE to report PHR, that is, the time interval at which the UE sends PHR to the network side.

[0125] For example, the UE will trigger a PHR (or report a PHR) when any one of the following conditions (1) to (3) is met:

[0126] Condition (1): When the UE has uplink resources to transmit new data, the prohibitPHR-Timer timer has expired or has expired, and the path loss change value has exceeded dl-PathlossChange since the last PHR transmission.

[0127] Condition (2), periodicPHR-Timer timed out;

[0128] Condition (3) is when the RRC layer configures (or reconfigures) the PHR function or parameter, and the configuration (or reconfiguration) does not disable PHR.

[0129] The parameters mentioned above (prohibitPHR-Timer, periodicPHR-Timer, and dl-PathlossChange) are all configured by RRC messages (e.g., phr-Config). These parameters can also be referred to as PHR configuration parameters.

[0130] However, improper PHR configuration parameters will affect UE PHR reporting. For example, setting the `prohibitPHR-Timer` too high or the `dl-PathlossChange` setting too high may cause the UE to fail to report PHR for an extended period. Prolonged failure of UE to report PHR can be considered an abnormal PHR scenario. This prolonged lack of PHR reporting by the UE results in a persistent absence of PHR on the network side, which in turn affects the network's closed-loop power control. For instance, affecting the network's closed-loop power control manifests at least in the following way: an unreasonable transmission power control (TPC) value set on the network side leads to a high uplink (UL) block error rate (BLER), severely impacting service experience.

[0131] In view of this, this application proposes a communication method in which, when a PHR anomaly occurs, the UE reports information related to the PHR anomaly to the network side so that the network side can immediately repair the PHR anomaly, or optimize the PHR configuration parameters based on the information related to the PHR anomaly reported by the UE, thereby minimizing the negative impact caused by the PHR anomaly.

[0132] 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, network devices) as the execution entities for this interactive illustration to demonstrate the method; however, this application does not limit the execution entities for the interactive illustrations. For example, the devices (e.g., UE, network devices) in the illustrative flowcharts 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.

[0133] 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.

[0134] Figure 3 This is an example flowchart illustrating a communication method according to an embodiment of this application. Figure 3 As shown, the method includes at least the following steps:

[0135] Step 310: The UE determines that a Power Headroom Report (PHR) abnormality has occurred.

[0136] It should be noted that, in the embodiments of this application, "PHR anomaly" refers to a situation where a PHR reporting anomaly is caused by a certain fault (for example, the PHR parameters configured by the network side for the UE are unreasonable; or the network side does not configure PHR parameters, and the UE uses the default (or predefined) PHR parameters, but the default PHR parameters are unreasonable; or there is a communication failure between the UE and the network side for a period of time during the PHR parameter configuration stage, which causes the PHR parameter configuration to fail, etc.), thereby affecting the service experience.

[0137] This application does not specify the exact implementation method for the UE to determine that a PHR anomaly has occurred. A UE determining that a PHR anomaly has occurred can be understood as: the UE failing to report a PHR for an extended period, the network device's configured power value not meeting power requirements, and the service's evaluation quality indicators not meeting requirements.

[0138] The "UE has not reported a PHR for a long time" can be measured by introducing a first preset time period. For example, the UE does not report a PHR within the first preset time period.

[0139] The network device's configured power value does not meet the power requirements, possibly because the network device has not reported a PHR for an extended period, resulting in an inappropriate power value configured for the UE. Optionally, the network device's configured power value not meeting the power requirements includes: the UE receiving a transmit power indication from the network device that is lower than a power threshold.

[0140] The aforementioned "transmit power received by the UE from the network device" refers to the transmit power value sent to the UE by the network device during uplink closed-loop power control based on certain conditions during service communication. For example, the network device sends a MAC CE to the UE, which includes a TPC command (or TPC value) indicated by the network device. The power threshold value is determined by the UE itself. When the transmit power value indicated by the network device to the UE is less than the power threshold value, it may affect the uplink transmission quality, thus impacting the service experience to some extent.

[0141] It is understood that the embodiments of this application do not specifically limit the conditions referenced by the network device when performing uplink closed-loop power control; for details, please refer to the descriptions in related technologies. For example, the network device sends a TPC value to the UE based on factors such as the received network measurement results of uplink power.

[0142] The failure to meet the evaluation quality indicators of a service can be understood as follows: due to the failure to report PHR for a long time, the power value configured on the network side is inappropriate, which in turn leads to the failure to meet the evaluation quality indicators of the service, which has seriously affected the service experience (or communication quality, or communication reliability).

[0143] It should be noted that there are multiple ways to implement the quality or quantitative indicators used to evaluate services. Optionally, the quality indicators for evaluating services include, but are not limited to, one or more of the following: bit error rate (BER), block error rate (BLER), frame error rate (FER), and packet error rate (PER) (or packet loss rate). Explanations of each indicator can be found in relevant technical descriptions, and will not be elaborated upon here.

[0144] It is understood that the above only shows some of the evaluation quality indicators, and the embodiments of this application are not limited thereto. In fact, other evaluation quality indicators are also applicable to the embodiments of this application.

[0145] Optionally, the evaluation quality indicators of the service do not meet the conditions, including: the duration of the uplink bit error rate is greater than or equal to the second preset duration.

[0146] For example, a UE determines that a PHR anomaly has occurred if the following conditions are met simultaneously: no PHR is reported within a first preset duration; the UE receives a transmit power indication from the network device that is lower than a power threshold; and the duration of the uplink bit error rate is greater than or equal to a second preset duration. If all three conditions are met simultaneously, it indicates that the PHR anomaly has severely impacted the UE's service experience. The simultaneous fulfillment of these three conditions can also be defined as an abnormal event, or a PHR anomaly event.

[0147] This application does not specifically limit the relationship between the first preset duration and the second preset duration. The first preset duration is introduced to describe the situation where PHR is not reported for a long time; the second preset duration is introduced to describe the situation where the uplink bit error rate continues for a relatively long time.

[0148] It should be understood that the embodiments of this application do not specifically limit the value of the first preset duration. For example, "no PHR reported for the first preset duration" means that the UE does not report PHR within 1 day.

[0149] It should also be understood that the embodiments of this application do not specifically limit the value of the second preset duration. For example, the duration of the uplink bit error rate being greater than or equal to the second preset duration means that the duration of the uplink BLER exceeds 5 seconds.

[0150] If the UE determines that a PHR anomaly has occurred, it can report the relevant information about the PHR anomaly to the network device.

[0151] In step 320, the UE sends a first message to the network device, which is used to notify the network device of information related to the PHR anomaly. Correspondingly, the network device receives the first message from the UE.

[0152] The first message mentioned above can be sent proactively by the UE to the network device, or it can be sent by the UE based on a request from the network device; there is no specific limitation on this. Different implementation methods for the UE to send the first message to the network device will be described later.

[0153] The first message is used by the UE to notify the network device of information related to the PHR anomaly, and it can be understood from different perspectives. The first interpretation is the UE's requirement. Specifically, when the UE detects a PHR anomaly, it urgently reports information related to the PHR anomaly to the network device, hoping that the network device can quickly adjust the relevant PHR configuration parameters to quickly repair the fault.

[0154] In the first interpretation, the first message may include information related to PHR configuration parameters. Optionally, information related to PHR anomalies may include one or more of the following: the most recent road loss change value and the duration of PHR absence.

[0155] The most recent path loss change value refers to the path loss change value of the UE at the most recent time. For example, by reporting the most recent path loss change value, the UE can help the network equipment refer to the most recent path loss change value to decide whether to adjust the path loss change threshold (i.e., the dl-PathlossChange parameter).

[0156] The duration of missing PHR can be understood as the duration during which the UE does not report PHR.

[0157] The second interpretation is based on the needs of the network device side. Specifically, by receiving the first message sent by one or more UEs and collecting PHR anomaly information over a long period, network devices can obtain a large amount of information for statistical analysis, thereby preventing the triggering of PHR anomalies from the root cause. This helps improve the overall network performance and comprehensively optimize the user's service experience.

[0158] Optionally, the information related to PHR anomalies may include one or more of the following: the cell corresponding to the PHR anomaly, the recovery time of the PHR anomaly, and the number of PHR anomalies.

[0159] The cell corresponding to a PHR anomaly can be understood as the abnormal cell in which the UE was located when the PHR occurred. For example, by reporting the identifier of the abnormal cell, the UE can help network devices configure or optimize the PHR parameters of the abnormal cell.

[0160] The recovery time for a PHR anomaly can be understood as the time from when a PHR anomaly occurs until the next PHR report and the system returns to normal.

[0161] The number of PHR exceptions can be understood as the number of times the UE determines to send a PHR exception.

[0162] It should be understood that the information related to PHR anomalies in the above examples is merely illustrative, and the embodiments of this application are not limited thereto. For example, in different implementations, the specific content of the information related to PHR anomalies included in the first message may differ.

[0163] It is understandable that, regardless of which interpretation is used above, the UE can send the first message to the network device to achieve the corresponding purpose.

[0164] Step 330: The network device determines the PHR configuration parameters based on the first message.

[0165] The process by which network devices determine PHR configuration parameters based on the first message can be understood as configuring or reconfiguring PHR configuration parameters. The specific implementation methods for network devices to determine PHR configuration parameters based on the first message will be described in detail later, along with different implementation approaches.

[0166] In this embodiment, when a PHR anomaly is determined to have occurred, the UE sends a first message to the network device. This first message contains information related to the PHR anomaly. Upon receiving the first message, the network device can re-determine the PHR configuration parameters to repair or optimize the PHR anomaly caused by the configuration parameters, thereby improving the service experience.

[0167] As described in step 320 above, the UE sends the first message to the network device, which can be implemented in different ways. The following combines... Figures 4A to 8 Provide a detailed description.

[0168] Figure 4A An interactive example diagram of a communication method according to an embodiment of this application is shown. For example... Figure 4A As shown, it includes at least the following steps:

[0169] Step 410: The UE determines that a PHR anomaly has occurred.

[0170] Step 410 can be referred to the description of step 310 above, and will not be repeated here for the sake of brevity.

[0171] In step 420, the UE sends a first message to the network device. Correspondingly, the network device receives the first message.

[0172] Step 420 above can be interpreted as a first way of describing the first message in step 320, meaning that the UE can proactively send a first message to the network device when it detects a PHR anomaly. The first message is used to notify the network device of the PHR anomaly. In other words, when the UE detects a PHR anomaly, it can immediately send a first message to the network device so that the network device can quickly perform fault repair.

[0173] The embodiments of this application do not specifically limit the form of the first message.

[0174] In some embodiments, the message type of the first message is User Equipment Assistance Information (UAI).

[0175] Optionally, the first message is the first UAI message. The first UAI message can be understood as a newly defined emergency UAI message, which can be represented as emergency UAI (UE Assistance Information_urgent, or simply UAI_U). When the first message is an emergency UAI message, the priority of the emergency UAI message is higher than that of the traditional UAI message.

[0176] Since traditional UAI messages serve as reference information on the network side, network devices may ignore them upon receiving them. Therefore, if the priority of the first UAI message is higher than that of the traditional UAI message, the network device will prioritize decoding the first UAI message upon receiving it. This allows the network device to determine if the UE's PHR (Problem Response Time) is abnormal, enabling it to promptly repair fault parameters based on the UE's reported information and more easily trigger PHR reporting, thus resolving the issue of prolonged PHR omissions.

[0177] Optionally, the first message includes first information, which indicates that the first message is an emergency UAI.

[0178] The information element type of the first information in this embodiment is not specifically limited. The first information can be a sequence type or an enumeration type.

[0179] For example, the first UAI message is an enumeration type, meaning that whether it is an urgent UAI message is indicated by an enumeration value (e.g., true or false). The decoding process for UAI messages using an enumeration type is simpler. Therefore, using an enumeration type for the first UAI message can reduce air interface signaling overhead and network-side decoding time, helping to support rapid repair of PHR anomalies.

[0180] For example, the first UAI message is a sequence type. Sequence type messages can include more suggested parameters, which helps to achieve more accurate fault parameter reconfiguration. That is, the UE can include one or more parameters for reconfiguration in the first UAI message; after decoding the first UAI message, the network device can reconfigure one or more parameters based on the UE's suggestions.

[0181] For example, the first message includes at least the most recent path loss change value. For the network device, after decoding the first message, it can not only determine that the UE's PHR is abnormal, but also obtain the most recent path loss change value. If the path loss change value reported by the UE is relatively large, the network device can choose to configure a lower dl-PathlossChange parameter. After lowering the dl-PathlossChange parameter, the UE will be more likely to trigger PHR based on the lower dl-PathlossChange parameter, thereby achieving rapid correction of erroneous power control parameters.

[0182] For example, the first message includes the duration of the missing PHR. For instance, the duration of the missing PHR can be understood as the duration during which the UE did not report the PHR. For the network device, after decoding the first message, it can not only determine the UE's PHR anomaly but also the duration of the missing PHR. Based on the duration of the missing PHR, the network device can choose to configure a lower dl-PathlossChange parameter or a shorter prohibitPHR-Timer duration.

[0183] For the descriptions of the network device configuration of the dl-PathlossChange parameter or the duration of the prohibitPHR-Timer in the above examples, please refer to the explanation at step 330.

[0184] Figure 4B This shows an example where the first message is an emergency UAI message. Figure 4B As shown, the message elements of an emergency UAI message are designed as a sequence type. An emergency UAI message includes emergency elements of sequence type (e.g., Figure 4B The PHR-Assistance-urgent shown in the figure, and the emergency information cell includes the most recent road loss change value (e.g., Figure 4B The `measPathlossChange` shown in the diagram. Optionally, the emergency information element may also include the duration of PHR absence (e.g., ...). Figure 4B The TimeDuringLastPHR shown is used.

[0185] Understandable. Figure 4BThe emergency UAI message shown is merely an example, and the embodiments in this application are not limited thereto. For example, the emergency UAI message may also include other parameters or information that the UE suggests the network side should adjust.

[0186] Alternatively, the first message may be a second UAI message, which includes a first information element indicating that the second UAI message is an emergency UAI message. The second UAI message may be a traditional UAI message. That is, the first message is a modified traditional UAI message, modified by adding an emergency information element to the traditional UAI message.

[0187] It should be understood that the above description uses a UAI message as the first message as an example, and the embodiments of this application are not limited to this. In fact, the first message can also be other types of messages or newly introduced messages.

[0188] Optionally, the network device decodes the first message upon receiving it to determine whether it is an urgent UAI message. If the first message is an urgent UAI message, the network device reconfigures the PHR configuration parameters.

[0189] Taking an emergency UAI message as an example, after decoding the emergency UAI message, the network device learns that the UE's PHR is abnormal, and can then choose to adjust the PHR configuration parameters. Of course, this description uses an emergency UAI message as the first message as an example, and the embodiments in this application are not limited to this.

[0190] For example, when the first message is a traditional UAI message and the traditional UAI message has added first information, the network device can obtain the first information by decoding the traditional message and thus know that the UE's PHR is abnormal.

[0191] This application does not specifically limit the implementation method of how to adjust PHR configuration parameters on the network device side.

[0192] Optionally, the PHR configuration parameters include at least one or more of the following: prohibitPHR-Timer, periodicPHR-Timer, and path loss change threshold (denoted as dl-PathlossChange).

[0193] Optionally, after receiving the first message, the network device reconfigures the duration of the `prohibitPHR-Timer`. That is, the network device configures the duration of `prohibitPHR-Timer` to be less than its initial duration. The initial duration can be understood as the duration of `prohibitPHR-Timer` used before the UE reported the first message. The initial duration of `prohibitPHR-Timer` can be configured by the network device for the UE. For example, if the initial duration of `prohibitPHR-Timer` is 5 seconds, the reconfigured duration is 3 seconds. In this way, based on the reconfigured `prohibitPHR-Timer`, the UE is more likely to trigger a PHR report, thus enabling reasonable power control.

[0194] Optionally, after receiving the first message, the network device reconfigures the path loss change threshold. That is, the network device configures the dl-PathlossChange threshold to be less than the initial path loss change threshold. The initial path loss change threshold can be understood as the path loss change threshold value used by the UE before reporting the first message. It can also be understood that the initial path loss change threshold can be configured by the network device for the UE.

[0195] It should be noted that the UE's failure to report PHR for an extended period due to inappropriate initial PHR configuration parameters (e.g., initial path loss change threshold or duration of the prohibitPHR-Timer) on the network device ultimately leads to PHR reporting anomalies. Therefore, in this embodiment, when the UE detects a PHR anomaly, it immediately reports it to the network device, enabling the network device to promptly modify the PHR configuration parameters based on the UE's report and achieve accurate uplink power control.

[0196] Optionally, in step 430, the network device sends a second message to the UE, the second message including PHR configuration parameters. Correspondingly, the UE receives the second message.

[0197] The PHR configuration parameters included in the second message can be understood as reconfigured PHR parameters, such as the duration value of the aforementioned reconfigured prohibitPHR-Timer, or the reconfigured path loss change threshold value.

[0198] In other words, network devices can reconfigure PHR configuration parameters based on the UE's suggestion and send the reconfigured PHR parameters to the UE so that the UE can perform PHR reporting based on the reconfigured PHR parameters.

[0199] For example, the second message is an RRC reconfiguration message (RRCReconfiguration); RRCReconfiguration includes phr-Config, which is the reconfigured PHR parameter.

[0200] Optionally, after receiving the PHR configuration parameters for network device reconfiguration, the UE can execute subsequent processes based on the PHR configuration parameters, such as executing steps 440 to 460.

[0201] Step 440: The UE determines whether the PHR reporting conditions are met based on the reconfigured PHR parameters.

[0202] For the reporting requirements of PHR, please refer to the previous description. For the sake of brevity, it will not be repeated here.

[0203] Step 450: If the UE determines that the PHR reporting conditions are met, it sends a PHR to the network device. Correspondingly, the network device receives the PHR reported by the UE.

[0204] Step 460: The network device sends a Physical Downlink Control Channel (PDCCH) to the UE, which includes the TPC value. Correspondingly, the UE receives the PDCCH.

[0205] For details regarding steps 440 to 460, please refer to the descriptions in related technologies; they will not be elaborated upon here.

[0206] based on Figure 4A The illustrated process enables the UE to immediately notify the network device after recognizing a PHR anomaly. The network device then reconfigures the PHR parameters based on the UE's report, quickly correcting the PHR anomaly and achieving accurate UL power control.

[0207] The following describes another communication method according to an embodiment of this application. Similar to the foregoing... Figure 4A The difference is that, Figure 4A The implementation method is from the UE's perspective, by having the UE report an emergency UAI message, in order to achieve the goal of quickly repairing PHR anomalies in the network. Figure 5 This involves performing fault optimization for PHR anomalies from the perspective of the network device. Optionally, in Figure 5 In this scenario, the UE sends the first message to the network device based on the network device's configuration. Alternatively, the UE can also proactively send the first message to the network device. The different implementation methods will be described in detail below.

[0208] refer to Figure 5 , Figure 5 An interactive flowchart of another communication method according to an embodiment of this application is shown. Figure 5 As shown, it includes at least the following steps:

[0209] Step 510: The network device sends a first RRC message, which is used to configure the UE to record relevant information about the occurrence of a PHR anomaly. Correspondingly, the UE receives the first RRC message.

[0210] It should be noted that network devices can send RRC messages to one or more UEs to configure one or more UEs to record information related to the occurrence of PHR anomalies.

[0211] The first RRC message may include specific information or content related to the network device configuring the UE to record a PHR anomaly. For example, the first RRC message may be an RRCReconfiguration message, and the RRCReconfiguration message may include PHRF_Storge_Config, which is used to indicate information related to the UE recording an SCC configuration anomaly.

[0212] Optionally, the relevant information for the occurrence of PHR anomalies includes, but is not limited to, one or more of the following: information about the abnormal cell, the abnormal recovery time, the number of times the PHR anomaly occurred, etc.

[0213] In other words, the UE receives the first RRC message from the network device before sending the first message to the network device. The UE can then perform the operation of recording PHR anomalies based on the first RRC message.

[0214] Step 520: The UE records relevant information about the PHR anomaly based on the first RRC message.

[0215] Optionally, the UE determines that a PHR anomaly has occurred before recording information related to the PHR anomaly. For a description of determining that a PHR anomaly has occurred, please refer to the description in step 310 above; for brevity, it will not be repeated here.

[0216] Optionally, the first RRC message may also include the maximum number of anomalies. The maximum number of anomalies can be understood as: the number of times the UE can record PHR anomalies; when the number recorded by the UE is greater than or equal to the maximum number of anomalies configured by the network device, the UE updates the anomaly information based on a queue.

[0217] A queue is a linear data structure. Queuing can be considered a method of storing data. This application's embodiments do not limit the specific queue or data storage method. For example, the UE updates abnormal information, i.e., PHR abnormality-related information, based on a first-in, first-out queue.

[0218] After recording (or storing) information related to a PHR anomaly, the UE can report this information to the network device via a first message. The UE can report this information automatically or upon request from the network device; there is no specific limitation on this.

[0219] Optionally, the method further includes: step 530, the UE sends a second RRC message to the network device, the second RRC message including indication information, the indication information being used to indicate that information related to PHR anomaly (or power headroom report failure (PHRF) information) has been recorded in the UE.

[0220] For example, the second RRC message is RRCReconfigurationComplete, and the indication information can be represented as phrf_InfoAvailable. That is, the UE can use the second RRC message to indicate to the network device that the UE has available PHRF information stored in the UE, so that the network device can obtain it as needed.

[0221] Alternatively, as a possible implementation, the network device collects PHR anomaly information reported by the UE through steps 541 and 542.

[0222] Step 541: The network device sends a request message to the UE, requesting the UE to report relevant information regarding the PHR anomaly. Correspondingly, the UE receives the request message.

[0223] This application does not specifically limit the triggering method for network devices to send request messages.

[0224] Optionally, the network device can send request messages to the UE as needed.

[0225] Alternatively, the network device may periodically send request messages. For example, the network device may send request messages to the UE during off-peak hours at night (e.g., from midnight to 5 a.m.) every day or every few days.

[0226] This application does not specifically limit the form of the request message sent by the network device.

[0227] Step 542: The UE sends a request-response message to the network device, the request-response message being used to respond to the request message. Correspondingly, the network device receives the request-response message.

[0228] Step 542 above can be an implementation of the second interpretation of the first message described in step 320, that is, the UE can send a request-response message to the network device based on the request message sent by the network device. The request-response message is used to report relevant information about the PHR anomaly to the network device. In other words, when the UE receives the request message, it can send a request-response message to the network device so that the network device can collect information related to the PHR anomaly.

[0229] For example, the request message in step 541 is a UEInformationRequest message, which is used to request the UE to report its stored PHRF information. Figure 6 An example of a UEInformationRequest message is shown. Figure 6 As shown, the UEInformationRequest message can add the following information element: phrf-ReportReqIE. Furthermore, this information element is of enumeration type. The value of this information element is true.

[0230] Accordingly, by decoding the UEInformationRequest message, the UE can obtain the value of phrf-ReportReqIE as true. Then, the UE reports its recorded PHRF information through the UEInformationResponse message (or request-response message), and clears the PHRF cache after reporting the PHRF information.

[0231] Optionally, the request-response message includes a PHRF report message. The PHRF report message includes information related to the PHR anomaly.

[0232] Optionally, the PHRF report message includes one or more of the following: the cell corresponding to the PHR anomaly, the recovery time of the PHR anomaly, and the number of PHR anomalies. For an explanation of each parameter, please refer to the description in step 320 above.

[0233] Optionally, the PHRF report message may also include one or more of the following: the serving cell's measurement value when the PHR anomaly occurred, the neighboring cell's measurement value when the PHR anomaly occurred, the UE's location information when the PHR anomaly occurred, and the duration from the start of the PHR anomaly to the current time. It should be understood that this information may be requested to be reported by the UE from the network device or reported by the UE itself, without specific limitations.

[0234] Figure 7 An example of a PHRF report message is shown. Figure 7As shown, a PHRF report message (represented as PHRF-Report-r16) includes at least: failedPcellId-r16, TimeDuringFailure-r16, TimeSinceFailure-r16, LocationInfo-r16, etc.

[0235] Step 550: The UE deletes the recorded PHR abnormal information.

[0236] In other words, after reporting PHR anomaly information to the network device, the UE can delete the already reported PHR anomaly information to reduce unnecessary memory space consumption. The already reported PHR anomaly information can also be called expired anomaly information.

[0237] It should be noted that, for ease of description, Figure 5 The example described uses the interaction between a network device and a single UE, but the embodiments of this application are not limited to this. The network device can collect PHR anomaly information reported by multiple UEs (i.e., two or more UEs). For example, Figure 8 The interaction process between the network device and two UEs (UE1 and UE2) is shown.

[0238] like Figure 8 As shown, the process of network devices collecting PHR anomaly information includes at least the following steps:

[0239] Step 801-1: The network device sends an RRC message to UE1.

[0240] Step 801-2: The network device sends an RRC message to UE2.

[0241] Step 802-1: UE1 determines that a PHR anomaly has occurred.

[0242] Step 802-2, UE2 determines that a PHR anomaly has occurred.

[0243] Step 803-1: UE1 records information related to PHR anomalies.

[0244] Step 803-2: UE2 records information related to PHR anomalies.

[0245] Optionally, in step 804-1, UE1 sends PHR anomaly-related information to the network device.

[0246] Optionally, in step 804-2, UE2 sends PHR anomaly-related information to the network device.

[0247] Optionally, in step 805-1, the network device sends a first request message to UE1.

[0248] Optionally, in step 805-2, the network device sends a second request message to UE2.

[0249] Optionally, in step 806-1, UE1 sends a first request response message to the network device.

[0250] Optionally, in step 806-2, UE2 sends a second request response message to the network device.

[0251] Step 807-1: UE1 deletes the PHR exception information recorded.

[0252] Step 807-2: UE2 deletes the PHR exception information recorded.

[0253] It should be noted that the embodiments of this application do not specifically limit the execution order of the interaction process between UE1 and the network device and the interaction process between UE2 and the network device. That is, there is no sequential relationship between the two interaction processes. They can be executed simultaneously or one after the other.

[0254] It should be understood that Figure 8 Regardless of whether it's the interaction process between UE1 and the network device, or the interaction process between UE2 and the network device, the interaction flow between them can be referred to in the previous text. Figure 5 The interaction process is shown below, and related descriptions can also be found in the preceding text. Figure 5 For the sake of brevity, the detailed explanation of each step will not be elaborated here.

[0255] Step 808: The network device collects information related to the occurrence of PHR anomalies.

[0256] For network devices, after receiving information related to PHR anomalies reported by one or more UEs, the network device can perform network-side optimization actions.

[0257] For example, if the network device detects that multiple PHRF reports from UEs occur in the same cell within a certain period, it indicates that the cell (which may be called an abnormal cell) may have an unreasonable PHR parameter configuration. In this case, the network device can instruct the primary base station of the cell to perform PHR configuration parameter verification to avoid unreasonable PHR parameter configuration. The network device can be a network element in the core network, which can instruct the base station of the cell to perform PHR parameter verification or reconfiguration.

[0258] Optionally, if the abnormal cell no longer becomes abnormal after a preset time period, for example, if the network device does not receive the PHR abnormal information corresponding to the abnormal cell sent by the UE, then the network device can notify the base station of the cell to stop performing the verification of the PHR configuration parameters.

[0259] Optionally, if the aforementioned abnormal cell still becomes abnormal after a preset time period, for example, if the network device receives PHR abnormal information corresponding to the abnormal cell from the UE, then the network device determines that the verification behavior is invalid and can choose other more effective or mandatory solutions. For example, the network device can increase the penalty value for the abnormal cell or adjust the S criterion for the abnormal cell to prevent the UE from registering to the abnormal cell again to perform services.

[0260] It should be understood that the optimization process on the network side shown above is merely an example, and the embodiments of this application are not limited thereto. In fact, other optimization solutions may exist for network devices in practice.

[0261] For the purposes of this application, the network devices involved in the embodiments are, for example, those mentioned above. Figures 3 to 8 The network devices involved can be core network devices or access network devices (such as gNBs), without specific limitations. Of course, when the network device is a core network device, the interaction between the UE and the network device specifically includes: the interaction between the UE and the access network device, and the interaction between the access network device and the core network device.

[0262] It is understood that the aforementioned implementation methods can also be reasonably combined and implemented, and the embodiments of this application do not specifically limit this. For example, Figure 4A and Figure 5 This can be implemented in combination. The UE can not only report emergency UAI messages to the network device to support rapid fault repair, but also report PHR anomaly-related information based on the network device's configuration records to support the network device in analyzing large amounts of data, thereby improving the overall network performance.

[0263] To clarify, the specific implementation of "predefined" can include any of the following: protocol predefined, manufacturer-specified, defined by the communication equipment, pre-installed in the communication equipment at the time of manufacture, or agreed upon in advance by other agreed methods.

[0264] It should be understood that the various interactive processes shown above are merely exemplary descriptions, and the embodiments of this application are not limited thereto. In fact, the various embodiments described above can be implemented independently or in reasonable combinations, and the embodiments of this application do not specifically limit them in this regard.

[0265] It should also be understood that Figures 1 to 8 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... Figures 1 to 8 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0266] The above text combined Figures 1 to 8This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figures 9 to 11 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.

[0267] In the embodiments described above, the UE can execute some or all of the steps in each embodiment; the 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.

[0268] Figure 9 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 9 As shown, the communication device 1500 may include a communication module 1520. The communication module 1520 can implement corresponding communication functions, which can be internal communication functions of the communication device 1500 or communication functions between the communication device 1500 and other devices. Optionally, the communication module 1520 may also be referred to as a communication interface or transceiver module. Optionally, the communication device 1500 further includes a processing module 1510. The processing module 1510 can implement corresponding processing functions.

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

[0270] In one possible design, the communication device 1500 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 1500 may be used to perform the steps or processes performed by the UE in any of the above method embodiments.

[0271] In one possible design, the processing module 1510 is used to determine that a Power Headroom Report (PHR) anomaly has occurred; the communication module 1520 is used to send a first message to the network device, the first message being used to notify the network device of information related to the Power Headroom Report (PHR) anomaly.

[0272] Optionally, as an embodiment, the processing module 1510 is used to determine that a PHR anomaly has occurred, including: determining that a PHR anomaly has occurred when a first preset condition is met, the first preset condition including: no PHR is reported within a first preset time period, the transmit power received by the UE from the network device is less than a power threshold value, and the uplink transmission bit error rate continues for a second preset time period.

[0273] Optionally, as an embodiment, after sending the first message to the network device, the communication module 1520 is further configured to receive a second message from the network device, the second message being used to reconfigure the configuration parameters of the PHR.

[0274] Optionally, as an embodiment, the second message includes a road loss change threshold or the duration of a first timer; the processing module 1510 is further configured to perform PHR reporting based on the second message.

[0275] Optionally, as an embodiment, the first message is a first user equipment assistance information (UAI) message, and the first UAI message has a higher priority than the second UAI message; or, the first message is a second UAI message, and the second UAI message includes first information, which is used to indicate that the second UAI message is an emergency UAI message.

[0276] Optionally, as an example, the information related to the abnormality of the Power Headroom Report (PHR) includes one or more of the following: the most recent road loss change value, and the duration of the missing PHR.

[0277] Optionally, as an embodiment, before determining that a Power Headroom Report (PHR) anomaly has occurred, the communication module 1520 is further configured to receive a first RRC message from the network device, the first RRC message being configured for the UE to record information related to the PHR anomaly; the processing module 1510 is further configured to record information related to the PHR anomaly based on the first RRC message.

[0278] Optionally, as an embodiment, the communication module 1520 is further configured to send a second RRC message to the network device, the second RRC message including indication information, the indication information being used to indicate that information related to PHR anomalies has been recorded in the UE.

[0279] Optionally, as an embodiment, the communication module 1520 is further configured to: receive a request message from the network device, the request message being used to request the UE to send PHR anomaly-related information; wherein, the communication module 1520 is configured to send a first message to the network device, including: sending a request response message to the network device according to the request message, the request response message being the first message.

[0280] Optionally, as an embodiment, the first RRC message is also used to configure the maximum number of times; the processing module 1510 is also used to update the recorded PHR exception information based on a queue method when the number of PHR exceptions is greater than or equal to the maximum number of times.

[0281] Optionally, as an embodiment, after sending the first message to the network device, the processing module 1510 is further configured to delete the reported abnormal information.

[0282] Optionally, as an embodiment, the information related to the Power Headroom Report (PHR) anomaly includes one or more of the following: the identifier of the serving cell where the PHR anomaly occurred, the recovery time of the PHR anomaly, the number of PHR anomalies, the signal quality measurement value of the serving cell where the PHR anomaly occurred, the identifier of the neighboring cell when the PHR anomaly occurred, the signal quality measurement value of the neighboring cell when the PHR anomaly occurred, the UE's location information when the PHR anomaly occurred, and the duration from the occurrence of the PHR anomaly to the current time.

[0283] It should be understood that the communication device 1500 may correspond to the embodiments according to this application. Figures 3 to 8 The UE in the communication device 1500 may include functions for performing... Figures 3 to 8 The modules or units that execute the method in the UE. Furthermore, each module and the other operations and / or functions in the communication device 1500 are respectively for implementing... Figures 3 to 8 The corresponding process.

[0284] It should also be understood that when the communication device 1500 is a UE, the processing module 1510 in the communication device 1500 can be implemented by at least one processor, for example, it can correspond to Figure 10 The processor 1610 in the communication device 1600 shown herein. For example, the communication module 1520 may correspond to... Figure 10 The communication interface 1620 in the communication device 1600 shown in the figure.

[0285] It should also be understood that when the communication device 1500 is a chip or chip system configured in the UE, the processing module 1510 of the communication device 1500 can be implemented by a processor, microprocessor or integrated circuit integrated on the chip or chip system.

[0286] Alternatively, in another possible design: the communication module 1520 is used to receive a first message from one or more user equipment (UEs), the first message being used to notify information related to power headroom report (PHR) anomalies;

[0287] The processing module 1510 is used to determine the PHR configuration parameters based on the first message.

[0288] Optionally, as an embodiment, the communication module 1520 is further configured to send a second message to the UE, the second message being used to reconfigure the configuration parameters of the PHR.

[0289] Optionally, as an embodiment, the second message includes a road loss change threshold or the duration of a first timer.

[0290] Optionally, as an embodiment, the first message is a first user equipment assistance information (UAI) message, and the priority of the first UAI message is higher than the priority of the second UAI message;

[0291] Alternatively, the first message may be a second UAI message, which includes first information indicating that the second UAI message is an emergency UAI message.

[0292] Optionally, as an example, the information related to the abnormality of the Power Headroom Report (PHR) includes one or more of the following: the most recent road loss change value, and the duration of the missing PHR.

[0293] Optionally, as an embodiment, the communication module 1520 is further configured to send a first RRC message, the first RRC message being used to configure information related to the UE recording PHR anomalies.

[0294] Optionally, as an embodiment, the communication module 1520 is further configured to receive a second RRC message from one or more UEs, the second RRC message including indication information for indicating that information related to PHR anomalies has been recorded in the UE.

[0295] Optionally, as an embodiment, the communication module 1520 is further configured to send a request message, the request message being used to request the UE to send information related to the PHR anomaly; wherein, the communication module 1520 is configured to receive a first message from one or more UEs, including: receiving a request response message from one or more UEs, the request response message being the first message.

[0296] Optionally, as an example, the request message is sent periodically.

[0297] Optionally, as an example, the first RRC message is also used to configure the maximum number of times.

[0298] Optionally, as an embodiment, the information related to the Power Headroom Report (PHR) anomaly includes one or more of the following: the identifier of the serving cell where the PHR anomaly occurred, the recovery time of the PHR anomaly, the number of PHR anomalies, the signal quality measurement value of the serving cell where the PHR anomaly occurred, the identifier of the neighboring cell when the PHR anomaly occurred, the signal quality measurement value of the neighboring cell when the PHR anomaly occurred, the UE's location information when the PHR anomaly occurred, and the duration from the occurrence of the PHR anomaly to the current time.

[0299] It should be understood that the communication device 1500 may correspond to the embodiments according to this application. Figures 3 to 8 The network device in the communication device 1500 may include a device for performing network functions; Figures 3 to 8 The network device in the communication device 1500 is a module or unit that executes the method. Furthermore, each module and the other operations and / or functions described above in the communication device 1500 are respectively for implementing... Figures 3 to 8 The corresponding process.

[0300] It should also be understood that when the communication device 1500 is a network device, the processing module 1510 in the communication device 1500 can be implemented by at least one processor, for example, it can correspond to Figure 10 The processor 1610 in the communication device 1600 shown herein. For example, the communication module 1520 may correspond to... Figure 10 The communication interface 1620 in the communication device 1600 shown in the figure.

[0301] It should also be understood that when the communication device 1500 is a chip or chip system configured in the aforementioned network equipment, the processing module 1510 of the communication device 1500 can be implemented by a processor, microprocessor, or integrated circuit integrated on the chip or chip system.

[0302] Figure 10 This is another schematic block diagram of the communication device 1600 provided in the embodiments of this application. The communication device 1600 can be a UE, a network device, or a chip, chip system, or processor that supports the UE or network device in implementing the above methods. The communication device 1600 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0303] like Figure 10As shown, the communication device 1600 may include one or more processors 1610, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 1610 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 1600 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

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

[0305] In another alternative design, the communication device 1600 may include a communication interface 1620 for implementing receiving and transmitting functions. For example, the communication interface 1620 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.

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

[0307] 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.

[0308] Optionally, if the communication device 1600 includes a processor 1610, a communication interface 1620, and a memory 1630, the processor 1610, the communication interface 1620, and the memory 1630 communicate with each other through internal connection paths.

[0309] Optionally, the memory 1630 may include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. The memory 1630 may be a separate device or integrated into the processor 1610.

[0310] In one implementation, the communication device 1600 may correspond to the UE in the above method embodiments and may be used to execute various steps and / or processes performed by the UE in the above method embodiments. The processor 1610 may be used to execute instructions stored in the memory 1630, and when the processor 1610 executes the instructions stored in the memory, the processor 1610 is used to execute various steps and / or processes of the above method embodiments corresponding to the UE.

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

[0312] Optionally, the communication interface 1620 is a transceiver, which may include a transmitter and a receiver. The transceiver may further include an antenna, and the number of antennas may be one or more. The processor 1610 and memory 1630, along with the communication interface 1620, may be integrated on different chips. For example, the processor 1610 and memory 1630 may be integrated in a baseband chip, and the communication interface 1620 may be integrated in a radio frequency chip. Alternatively, the processor 1610, memory 1630, and communication interface 1620 may be integrated on the same chip. This application does not limit this.

[0313] This application also provides a processing device, including a processor and an interface; the processor is used to execute the communication method in any of the above method embodiments.

[0314] 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.

[0315] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or 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 omitted here.

[0316] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuitry in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located 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 the information in the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0317] 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.

[0318] Figure 11 A schematic diagram of the structure of a UE applicable to this application is shown.

[0319] The UE may include a processor 110, a satellite communication processor 111 (a processor with satellite communication function, or a satellite communication chip, which may also have other communication functions, such as cellular communication function), an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0320] It should be noted that, Figure 11 The structure shown does not constitute a specific limitation on the UE. In other embodiments of this application, the UE may include a... Figure 11 The components shown may include more or fewer components, or the UE may include... Figure 11 The components shown may be a combination of certain components, or the UE may include... Figure 11 Sub-components of some of the components shown. Figure 11 The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0321] Processor 110 may include one or more processing units. For example, processor 110 may include at least one of the following processing units: application processor (AP) (AP may include a satellite protocol stack), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), modem processor (also known as baseband processor, modem may include cellular protocol stack and cellular physical layer), and neural network processing unit (NPU). The different processing units may be independent devices or integrated devices.

[0322] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0323] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system. The processor 110 may be a System-on-a-Chip (SoC).

[0324] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identification card (e.g., a SIM card) interface, and / or a universal serial bus (USB) interface, etc.

[0325] Satellite communication processor 111 is communicatively connected to the AP in processor 110. When part or all of the satellite protocol stack is integrated into the AP, communication can occur between the satellite protocol stack in the AP and the satellite physical layer in satellite communication processor 111 via this connection.

[0326] The wireless communication function of a smartphone can be implemented through antenna 1, antenna 2, antenna 3, mobile communication module 150, satellite communication module 161, wireless communication module 160, access point (AP), modem, and satellite communication chip. Antennas 1, 2, and 3 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0327] The mobile communication module 150 can provide solutions for cellular communication (such as 2G / 3G / 4G / 5G) applications on smartphones.

[0328] Satellite communication module 161 can provide a solution for satellite communication applications on smartphones.

[0329] The satellite communication module 161 can be independent of the satellite communication processor 111. Alternatively, the satellite communication module 161 can be partially encapsulated within the satellite communication processor 111. For example, the RFIC in the satellite communication module 161 can be encapsulated within the satellite communication processor 111.

[0330] The wireless communication module 160 can provide solutions for wireless communication applications in smartphones, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 3, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0331] The UE can implement display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0332] The UE can achieve shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0333] Digital signal processors (DSPs) are used to process digital signals, including digital image signals and other digital signals. For example, when a UE selects a frequency, a DSP can perform Fourier transforms on the frequency energy.

[0334] In addition, an operating system runs on top of the aforementioned components. Examples include iOS, Android, and Windows. Applications can be installed and run on this operating system.

[0335] Various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. As used herein, the term "article of manufacture" encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0336] 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.

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

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

[0339] 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 performed by the UE or network device in any of the foregoing method embodiments.

[0340] 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 or network device in any of the foregoing method embodiments.

[0341] The computer-readable storage medium 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 (DR RAM).

[0342] The above-described device and method embodiments are completely corresponding, with corresponding modules or units performing corresponding steps. For example, a communication unit or communication interface performs the receiving or sending steps in the method embodiment, while other steps besides sending and receiving can be performed by a processing unit or processor.

[0343] 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.

[0344] 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 the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0345] In the above-described device embodiments, the terminal devices and network devices in the device and method embodiments completely correspond to each other. Corresponding modules or units execute corresponding steps. For example, the communication unit (transceiver) executes the receiving or sending steps in the method embodiments, while other steps besides sending and receiving can be executed by the processing unit (processor). The specific functions of each unit can be found in the corresponding method embodiments. There can be one or more processors.

[0346] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0347] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0348] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0349] 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.

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

[0351] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

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

[0353] In addition, the terms “system” and “network” are often used interchangeably in this article.

[0354] 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 by comprising: Applied to a user equipment (UE), the method includes: The power margin report (PHR) is confirmed to be abnormal. Send a first message to the network device, the first message being used to notify the network device of information related to an abnormal Power Headroom Report (PHR).

2. The method of claim 1, wherein, The determination of a PHR anomaly includes: If a PHR anomaly is determined to occur under the condition that the first preset condition is met, the first preset condition includes: no PHR is reported within a first preset time period, the transmit power received by the UE from the network device is less than the power threshold value, and the uplink transmission bit error rate continues for a second preset time period.

3. The method according to claim 1 or 2, characterized in that, After sending the first message to the network device, the method further includes: A second message is received from the network device, the second message being used to reconfigure the configuration parameters of the PHR.

4. The method according to claim 3, characterized in that, The second message includes a road loss change threshold or the duration of a first timer; the method further includes: Based on the second message, execute the PHR report.

5. The method according to any one of claims 1 to 4, characterized in that, The first message is a first user equipment assistance information (UAI) message, and the first UAI message has a higher priority than the second UAI message. Alternatively, the first message may be a second UAI message, which includes first information indicating that the second UAI message is an emergency UAI message.

6. The method according to any one of claims 1 to 5, characterized in that, The information related to the Power Headroom Report (PHR) anomaly includes one or more of the following: the most recent road loss change value, and the duration of the missing PHR.

7. The method according to any one of claims 1 to 3, characterized in that, Before determining that a Power Headroom Report (PHR) anomaly has occurred, the method further includes: receiving a first RRC message from the network device, wherein the first RRC message is used to configure the UE to record information related to the PHR anomaly; The method further includes: recording information related to the PHR anomaly based on the first RRC message.

8. The method according to claim 7, characterized in that, The method further includes: A second RRC message is sent to the network device. The second RRC message includes indication information, which is used to indicate that information related to the PHR anomaly has been recorded in the UE.

9. The method according to claim 1, 7 or 8, characterized in that, The method further includes: Receive a request message from the network device, the request message being used to request the UE to send information related to PHR anomaly; Sending the first message to the network device includes: Based on the request message, a request response message is sent to the network device, wherein the request response message is the first message.

10. The method according to any one of claims 7 to 9, characterized in that, The first RRC message is also used to configure the maximum number of times; the method further includes: If the number of PHR anomalies is greater than or equal to the maximum number, the recorded PHR anomaly information is updated based on a queue method.

11. The method according to any one of claims 7 to 10, characterized in that, After sending the first message to the network device, the method further includes: Delete the reported abnormal information.

12. The method according to any one of claims 1 to 11, characterized in that, The information related to the Power Headroom Report (PHR) anomaly includes one or more of the following: the identifier of the serving cell where the PHR anomaly occurred, the recovery time of the PHR anomaly, the number of PHR anomalies, the signal quality measurement value of the serving cell where the PHR anomaly occurred, the identifier of the neighboring cell when the PHR anomaly occurred, the signal quality measurement value of the neighboring cell when the PHR anomaly occurred, the UE's location information when the PHR anomaly occurred, and the time elapsed from the occurrence of the PHR anomaly to the current time.

13. A communication method, characterized in that, Applied to network devices, the method includes: Receive a first message from one or more user equipment (UEs), the first message being used to notify information related to power headroom report (PHR) anomalies; Based on the first message, determine the PHR configuration parameters.

14. The method according to claim 13, characterized in that, The method further includes: A second message is sent to the UE, which is used to reconfigure the configuration parameters of the PHR.

15. The method according to claim 13 or 14, characterized in that, The second message includes either the road loss change threshold or the duration of the first timer.

16. The method according to any one of claims 13 to 15, characterized in that, The first message is a first user equipment assistance information (UAI) message, and the first UAI message has a higher priority than the second UAI message. Alternatively, the first message may be a second UAI message, which includes first information indicating that the second UAI message is an emergency UAI message.

17. The method according to any one of claims 13 to 16, characterized in that, The information related to the Power Headroom Report (PHR) anomaly includes one or more of the following: the most recent road loss change value, and the duration of the missing PHR.

18. The method according to any one of claims 13 to 15, characterized in that, The method further includes: Send a first RRC message, which is used to configure the UE to record information related to PHR anomalies.

19. The method according to claim 18, characterized in that, The method further includes: Receive a second RRC message from one or more UEs, the second RRC message including indication information for indicating that information related to PHR anomalies has been recorded in the UE.

20. The method according to claim 13, 18 or 19, characterized in that, The method further includes: Send a request message, the request message being used to request the UE to send information related to the PHR anomaly; The receiving of a first message from one or more UEs includes: Receive request-response messages from one or more UEs, wherein the request-response message is the first message.

21. The method according to claim 20, characterized in that, The request messages are sent periodically.

22. The method according to any one of claims 18 to 20, characterized in that, The first RRC message is also used to configure the maximum number of times.

23. The method according to any one of claims 13 to 22, characterized in that, The information related to the Power Headroom Report (PHR) anomaly includes one or more of the following: the identifier of the serving cell where the PHR anomaly occurred, the recovery time of the PHR anomaly, the number of PHR anomalies, the signal quality measurement value of the serving cell where the PHR anomaly occurred, the identifier of the neighboring cell when the PHR anomaly occurred, the signal quality measurement value of the neighboring cell when the PHR anomaly occurred, the UE's location information when the PHR anomaly occurred, and the time elapsed from the occurrence of the PHR anomaly to the current time.

24. A communication system, characterized in that, This includes one or more user equipment (UEs) and network devices; Wherein, the UE is used to perform the method as described in any one of claims 1-12; the network device is used to perform the method as described in any one of claims 13-23.

25. A communication device, characterized in that, The device includes a processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the device to perform the method as described in any one of claims 1-12; or cause the device to perform the method as described in any one of claims 13-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, the computer performs the method as described in any one of claims 1-12; or, the computer performs the method as described in any one of claims 13-23.

27. A chip, characterized in that, include: A processor for retrieving and running a computer program from memory, causing a communication device on which the chip is mounted to perform the method as described in any one of claims 1-12; or, to perform the method as described in any one of claims 13-23.

28. A computer program product, characterized in that, It includes computer program instructions that cause the computer to perform the method as described in any one of claims 1-12, or the computer program instructions that cause the computer to perform the method as described in any one of claims 13-23.

Images