A communication method and terminal device, network device, communication apparatus, and medium

By introducing a status version number mechanism between terminal devices and network devices, the problem of status asynchrony caused by the loss of UE adaptability reports is solved, and timely synchronization of adaptability status and improved communication reliability are achieved.

CN121078550BActive Publication Date: 2026-03-27HONOR DEVICE CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2025-11-05
Publication Date
2026-03-27

AI Technical Summary

Technical Problem

In 5G-Advanced and later versions, the loss of UE compatibility reports makes it impossible for the base station to detect the problem, resulting in a long-term asynchrony between the UE and the base station's compatibility status. Existing 3GPP standards cannot effectively detect the problem of lost incremental compatibility reports.

Method used

A state version number mechanism is introduced, in which the terminal device sends an adaptation state version number to the network device. The network device detects adaptation loss by using the version number and triggers the terminal device to report adaptation, thereby achieving state synchronization.

Benefits of technology

Reduce signaling overhead, avoid repeated transmission of unchanged states, improve communication reliability between terminal devices and network devices, and enable timely recovery of adaptability states.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121078550B_ABST
    Figure CN121078550B_ABST
Patent Text Reader

Abstract

Embodiments of the present application provide a communication method and terminal device, network device, communication apparatus and medium, relating to the technical field of communication, aiming to trigger the terminal device to report the first adaptability when the network device does not receive the first adaptability, and realizing the adaptability state synchronization of the terminal device and the network device. The method comprises: obtaining a first state version number corresponding to a first adaptability of a terminal device; sending first information to a network device, wherein the first information is used to indicate the first state version number; receiving second information from the network device, wherein the second information is used to trigger the terminal device to report the first adaptability.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of wireless communication, and in particular to a communication method, a terminal device, a network device, a communication apparatus, and a medium. BACKGROUND

[0002] In the 5th Generation Mobile Communication Technology (5G) evolution (5G-Advanced) and subsequent versions, Artificial Intelligence (AI) / Machine Learning (ML) functions are introduced, for example, AI / ML functions can be beam management based on user equipment (UE) side models, and the Third Generation Partnership Project (3GPP) standard needs a new mechanism to manage the life cycle (LCM) of these functions.

[0003] One of the core processes in the above new mechanism is that the user equipment (UE) can send an applicability report to the base station (next-generation NodeB, gNB). However, the UE's applicability will change due to changes in the UE's local environment, and the current 3GPP meeting has concluded that if an incremental applicability report is lost, the base station cannot perceive it at all, resulting in a long asynchronous state between the UE and the base station. SUMMARY

[0004] The present application provides a communication method, a terminal device, a network device, a communication apparatus, and a medium, which aims to trigger the terminal device to report the first applicability when the network device does not receive the first applicability, so as to realize the synchronization of the applicability state of the terminal device and the network device.

[0005] In order to achieve the above-mentioned purpose, the present application provides the following technical solutions:

[0006] In a first aspect, a communication method is provided, which can be executed by a communication apparatus, or can be executed by a component (such as a circuit, a chip, or a chip system, etc.) configured in the communication apparatus, and can also be realized by a logic module or software that can realize all or part of the functions of the communication apparatus. The present application does not make any limitation in this regard. Hereinafter, the communication apparatus is taken as an example of a terminal device.

[0007] The method comprises: obtaining a first state version number corresponding to a first adaptability of a terminal device; sending first information to a network device, the first information being used for indicating the first state version number; and receiving second information from the network device, the second information being used for triggering the terminal device to report the first adaptability.

[0008] In the foregoing scheme, the terminal device indicates the first state version number in the first information sent to the network device. By introducing the state version number, the network device can detect whether the adaptability reported by the terminal device is lost by means of whether the state version number is continuous, so that the terminal device can receive the second information sent by the network device and trigger the terminal device to report the first adaptability according to the second information. In the embodiment of the application, signaling overheads can be reduced, repeated transmission of unchanged states can be avoided, and when loss is detected, the terminal device can be actively requested to report the first adaptability to restore adaptability state synchronization, thereby improving the reliability of communication between the terminal device and the network device.

[0009] In some possible implementation manners, the first information comprises: a first field used for indicating the first state version number, and the first field belongs to a packet data convergence protocol (PDCP) layer or a medium access control (MAC) layer. In the foregoing scheme, the terminal device can set the first field in a PDCP or MAC layer header, and indicate the first state version number through the first field. After receiving the first information, the network device can first parse the PDCP or MAC to obtain the first field, and determine the first state version number through the data content carried in the first field.

[0010] In some possible implementation manners, the obtaining of the first state version number corresponding to the first adaptability of the terminal device comprises: obtaining an updated first configuration item corresponding to the first adaptability of the terminal device; and updating a current state version number of the first adaptability according to the first configuration item to obtain the first state version number. In the foregoing scheme, the current state version number can be updated through the first configuration item to obtain the first state version number, so that the terminal device side can store the latest current state version number.

[0011] In some possible implementation manners, the method further comprises: updating a state of the first configuration item in a configuration item state list according to the first configuration item corresponding to the first adaptability. In the foregoing scheme, after the first configuration item corresponding to the first adaptability is updated, the state of the first configuration item in the configuration item state list can also be updated according to the first configuration item, so that the configuration item state list can store a complete state list of all current configuration items.

[0012] In some possible implementation manners, the method further includes: storing the first state version number corresponding to the first adaptability into a to-be-reported state change queue. In the foregoing scheme, in order to solve the problem that the first state version number corresponding to the first adaptability is not correctly received by the network device, the terminal device can further store a to-be-reported state change queue, which can also be referred to as a to-be-reported state change queue, and store the first state version number that is not correctly received by the network device in the to-be-reported state change queue.

[0013] In some possible implementation manners, after the second information from the network device is received, the method further includes: obtaining the first state version number and a second state version number from the to-be-reported state change queue, the second state version number being a state version number of a configuration that has been changed but not reported in the to-be-reported state change queue; and sending third information to the network device, the third information being used to indicate the first state version number and the second state version number. In the foregoing scheme, the terminal device can send the first state version number and the second state version number in the to-be-reported state change queue together, thereby improving communication efficiency.

[0014] In some possible implementation manners, the method further includes: in a case where the first information is successfully sent through a radio link control (RLC) acknowledgement, emptying the first state version number from the to-be-reported state change queue. In the foregoing scheme, in a case where the first information is successfully sent, the terminal device empties the first state version number from the to-be-reported state change queue, thereby achieving timely maintenance of the to-be-reported state change queue.

[0015] In some possible implementation manners, the first information includes at least one of the following: a first radio resource control (RRC) reconfiguration complete message, and a first user equipment (UE) assistance information. In the foregoing scheme, the terminal device can carry the first state version number through the first RRC reconfiguration complete message, or the terminal device can carry the first state version number through the first UE assistance information.

[0016] In some possible implementation manners, the method further includes: determining, according to the second information, that the terminal device performs adaptive full-amount state reporting; and sending, to the network device, fourth information, where the fourth information is used to indicate the states of all configuration items in the configuration item state list. In the foregoing solution, the network device can instruct the terminal device to perform adaptive full-amount state reporting through the second information. The terminal device stores the configuration item state list, and the configuration item state list includes the states of all configuration items of the first adaptability. Therefore, the terminal device can send the fourth information to the network device, where the fourth information is used to indicate the states of all configuration items in the configuration item state list. Therefore, the network device can obtain the full-amount states of all configuration items of the first adaptability according to the fourth information.

[0017] In a second aspect, a communication method is provided, which can be executed by a communication device, or can be executed by a component (such as a circuit, a chip, or a chip system, etc.) configured in the communication device, and can also be implemented by a logic module or software that can implement all or part of the functions of the communication device. The present application does not make any limitation in this regard. Hereinafter, the communication device is taken as an example of a network device.

[0018] The method includes: receiving first information from a terminal device, where the first information is used to indicate a first state version number corresponding to a first adaptability of the terminal device; and in a case where the first state version number is not continuous with a state version number stored by a network device, sending second information to the terminal device, where the second information is used to trigger the terminal device to report the first adaptability. In the foregoing solution, the network device can detect loss of adaptability reported by the terminal device according to whether the state version numbers are continuous, so that the terminal device can receive the second information sent by the network device, and trigger the terminal device to report the first adaptability according to the second information. In the embodiments of the present application, signaling overhead can be reduced, repeated transmission of unchanged states can be avoided, and when loss is detected, the network device can actively request the terminal device to report the first adaptability to restore adaptability state synchronization, thereby improving the reliability of communication between the terminal device and the network device.

[0019] In some possible implementation manners, the state version number stored by the network device is a last valid state version number received by the network device from the terminal device. In the foregoing solution, the network device can store the last valid state version number, and the network device can determine whether the state version numbers are continuous according to the stored state version number and the first state version number.

[0020] In some possible implementation manners, the method further includes: determining a first field from a packet data convergence protocol (PDCP) layer or a medium access control (MAC) layer of the first information, the first field being used to indicate the first state version number. In the above scheme, after the network device receives the first information, the network device can first parse the PDCP or the MAC to obtain the first field, and determine the first state version number according to data content carried in the first field.

[0021] In some possible implementation manners, the method further includes: in a case where the first state version number is continuous with a state version number stored by the network device, parsing the first information by using a radio resource control (RRC) layer. In the above scheme, the first state version of the first adaptation transmitted by the terminal device is successfully received by the network device, and the network device can achieve state synchronization with the terminal device. In this case, the network device can continue to parse the first information, so that complete data packets can be obtained from the first information. For example, the data packets can include an updated configuration of the first adaptation.

[0022] In some possible implementation manners, the method further includes: in a case where the first state version number is continuous with a state version number stored by the network device, updating an adaptation state list of the network device according to the first state version number. In the above scheme, the network device can update the adaptation state list of the network device according to the first state version number, that is, the latest state version number received can be stored in the adaptation state list, so that the latest state version number of the first adaptation transmitted by the terminal device can be stored according to the adaptation state list, and therefore the network device can perform loss detection based on the state version number.

[0023] In some possible implementation manners, the first information includes at least one of the following: a first radio resource control (RRC) reconfiguration complete message, and a first user equipment (UE) assistance information. In the above scheme, the network device can receive the first state version number by using the first RRC reconfiguration complete message, or the network device can receive the first state version number by using the first UE assistance information.

[0024] In some possible implementation manners, the second information includes: a first RRC reconfiguration message, and the first RRC reconfiguration message includes a second field, the second field being used to indicate that the terminal device reports an adaptation full state. In the above scheme, in a case where the first RRC reconfiguration message includes the second field, a position and a size of the second field in the first RRC reconfiguration message are not limited, and the second field is used to indicate that the terminal device reports the adaptation full state.

[0025] In some possible implementation manners, the communication method performed by the network device further includes: receiving, by the network device, third information from the terminal device, the third information being used to indicate the first state version number and the second state version number. In the above scheme, the terminal device can send the first state version number and the second state version number in the state change queue to be reported in a combined manner, and the network device can receive the multiple state version numbers through the third information, thereby improving communication efficiency.

[0026] In some possible implementation manners, the method further includes: receiving fourth information from the terminal device, the fourth information being used to indicate states of all configuration items in a configuration item state list of the terminal device. In the above scheme, the network device can instruct the terminal device to perform full-state reporting of adaptability through the second information, and the terminal device stores the configuration item state list, which includes states of all configuration items of the first adaptability. Therefore, the terminal device can send the fourth information to the network device, the fourth information being used to indicate states of all configuration items in the configuration item state list, so that the network device can obtain full states of all configuration items of the first adaptability according to the fourth information.

[0027] A third aspect of the present application provides a terminal device, which includes:

[0028] a processing module configured to obtain a first state version number corresponding to a first adaptability of the terminal device;

[0029] a communication module configured to send first information to a network device, the first information being used to indicate the first state version number;

[0030] the communication module is configured to receive second information from the network device, the second information being used to trigger the terminal device to report the first adaptability.

[0031] A fourth aspect of the present application provides a network device, which includes:

[0032] a communication module configured to receive first information from a terminal device, the first information being used to indicate a first state version number corresponding to a first adaptability of the terminal device;

[0033] the communication module is configured to send second information to the terminal device in a case where the first state version number is not continuous with a state version number stored by the network device, the second information being used to trigger the terminal device to report the first adaptability.

[0034] The fifth aspect of the present application provides a communication device, comprising a memory and at least one processor. The memory is configured to store programs or computer instructions, and the at least one processor is configured to execute the computer programs or computer instructions stored in the memory, so that the communication device implements the method provided by the first aspect or the second aspect of the present application.

[0035] The sixth aspect of the present application provides a computer storage medium for storing computer programs, which, when executed, are configured to implement the method provided by the first aspect or the second aspect of the present application.

[0036] The seventh aspect of the present application provides a computer program product comprising instructions which, when executed on a computer, cause the computer to perform the method provided by the first aspect or the second aspect.

[0037] The eighth aspect of the present application provides a chip system, which comprises a processor configured to support a terminal device or a network device to implement the functions involved in the above aspects, for example, to send or process the data and / or information involved in the above methods. In a possible design, the chip system further comprises a memory configured to store necessary program instructions and data of the terminal device or the network device. The chip system can be composed of a chip, or can comprise a chip and other discrete devices.

[0038] The ninth aspect of the present application provides a communication system comprising the first communication device and the second communication device as described above, for example, the first communication device is a terminal device, and the second communication device is a network device. Optionally, the communication system can further comprise other devices in communication with the terminal device and / or the network device.

[0039] The second aspect to the ninth aspect have the same or corresponding technical implementation manners as the first aspect, and the explanations, supplements and beneficial effects of the first aspect are also applicable to the second aspect to the ninth aspect, and will not be described herein. BRIEF DESCRIPTION OF DRAWINGS

[0040] Figure 1 A system architecture diagram of a communication system provided by an embodiment of the present application is shown;

[0041] Figure 2 Another system architecture diagram of a communication system provided by an embodiment of the present application is shown;

[0042] Figure 3 A flowchart of adaptability reporting and measurement configuration provided by an embodiment of the present application is shown;

[0043] Figure 4 A flowchart of interaction between a network device and a terminal device provided by an embodiment of the present application is shown;

[0044] Figure 5 A structural example diagram of a communication device provided for an embodiment of the present application is shown in FIG. 1.

[0045] Figure 6 A structural example diagram of an electronic device provided for an embodiment of the present application is shown in FIG. 2.

[0046] Figure 7 A structural example diagram of another electronic device provided for an embodiment of the present application is shown in FIG. 3. DETAILED DESCRIPTION

[0047] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. The terms used in the following embodiments are only for the purpose of describing the specific embodiments and are not intended to be limiting to the present application. As used in the specification and the appended claims of the present application, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that “one or more” as used in the embodiments of the present application means one, two, or more than two; “and / or” describes the associated objects in the association relationship, which means that there can be three kinds of relationships; for example, A and / or B can mean that A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. The character “ / ” generally represents an “or” relationship between the associated objects.

[0048] In the present specification, the reference to “one embodiment” or “some embodiments” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases “in one embodiment,” “in some embodiments,” “in other embodiments,” “in additional embodiments,” and so on, in various places in the specification are not necessarily all referring to the same embodiment, unless otherwise specifically noted. The terms “comprising,” “including,” “having,” and their variants, mean “including but not limited to,” unless otherwise specifically noted.

[0049] The plurality referred to in the embodiments of the present application means greater than or equal to two. It should be noted that in the description of the embodiments of the present application, the terms “first,” “second,” and the like are used only for the purpose of distinguishing the described objects, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying an order.

[0050] The technical solutions in the embodiments of the present application will be clearly and completely described in the present application with reference to the accompanying drawings. The terms used in the following embodiments are only for the purpose of describing the specific embodiments and are not intended to be limiting of the present application. As used in the specification and the appended claims of the present application, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “one or more,” when used in the present application, means one, two, or more than two; “and / or” describes the associated relationship of associated objects, which means that there can be three kinds of relationships; for example, A and / or B, which can represent the following three cases: A exists alone, A and B exist together, B exists alone, where A and B can be singular or plural. The character “ / ” generally represents an “or” relationship between the associated objects.

[0051] In the present specification, the phrase “one embodiment” or “some embodiments” etc. means that the specific features, structures or characteristics described in connection with the embodiment are included in one or more embodiments of the present application. Therefore, the phrases “in one embodiment,” “in some embodiments,” “in other some embodiments,” “in yet some embodiments” etc. appearing in different places in the present specification are not necessarily all referring to the same embodiment, but mean “one or more but not all embodiments,” unless otherwise specifically emphasized. The terms “include,” “contain,” “have” and their variants mean “including but not limited to,” unless otherwise specifically emphasized.

[0052] The plurality of embodiments of the present application refers to greater than or equal to two. It should be noted that in the description of the embodiments of the present application, the terms “first,” “second,” etc. are only used for the purpose of distinguishing the description and cannot be understood as indicating or implying relative importance, nor can it be understood as indicating or implying order.

[0053] The technical solutions in the embodiments of the present application will be clearly and completely described in the present application with reference to the accompanying drawings. The terms used in the following embodiments are only for the purpose of describing the specific embodiments and are not intended to be limiting of the present application. As used in the specification and the appended claims of the present application, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “one or more,” when used in the present application, means one, two, or more than two; “and / or” describes the associated relationship of associated objects, which means that there can be three kinds of relationships; for example, A and / or B, which can represent the following three cases: A exists alone, A and B exist together, B exists alone, where A and B can be singular or plural. The character “ / ” generally represents an “or” relationship between the associated objects.

[0054] The technical solutions provided in this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) systems, General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of these applications.

[0055] Figure 1 This is a schematic diagram of a communication system 100 used in an embodiment of this application. The communication system 100 may include network devices, such as... Figure 1 The network device 110 is shown. The communication system 100 may also include terminal devices, such as... Figure 1 The terminal device 120 shown. The network device 110 and the terminal device 120 can communicate via a wireless link.

[0056] Figure 1 An exemplary network device 110 and a terminal device 120 are shown. Optionally, the communication system 100 may also include multiple network devices and / or multiple terminal devices.

[0057] The network device in the present application can be a device of a network side such as an access network, a core network device, and the like. The access network device is also sometimes referred to as an access node. The access network device has a wireless transceiving function and is used to communicate with a terminal. The access network device includes, but is not limited to, a base station in the above-mentioned communication system, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5G mobile communication system, an access network device or a module of an access network device in an open RAN (ORAN) system, a satellite in an NTN communication system, a base station in a future mobile communication system, or an access node in a WiFi system, and the like. The access network device can also be a module or unit capable of realizing part of the function of a base station. The access network device can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, the access network device can also be a server, a wearable device, or a vehicle-mounted device, and the like. For example, the access network device in vehicle to everything (V2X) technology can be a road side unit (RSU). Multiple access network devices in a communication system can be the same type of base station or different types of base stations. The base station can communicate with the terminal directly or through a relay station. The terminal can communicate with multiple base stations in different access technologies. The embodiments of the present application do not limit the specific technology and specific device form of the access network device. In the present application, the access network device is referred to as a network device.

[0058] In the present application, the device for realizing the function of the network device can be a network device or a device capable of supporting the network device to realize the function, such as a processor, a circuit, a chip, or a chip system, and the like, which can be installed in the network device or used in connection with the network device. In the technical solutions provided in the present application, the device for realizing the function of the network device is taken as an example to describe the technical solutions provided in the present application.

[0059] The terminal device in the present application can be a wireless terminal device capable of receiving network device scheduling and indication information. The wireless terminal device can be a device that provides voice and / or data connectivity to a user, or a handheld device with wireless connection function, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet through a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. The terminal device can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), internet of things (IOT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, remote medical treatment, smart power grid, smart furniture, smart office, smart wear, smart transportation, smart city, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, aircraft (such as unmanned aerial vehicle, helicopter, airplane), hot air balloon, ship, robot, mechanical arm, or smart home device, etc. The embodiments of the present application do not limit the form of the terminal device.

[0060] In the present application, the device for realizing the function of the terminal device can be a terminal device, or a device capable of supporting the terminal device to realize the function, such as a processor, circuit, chip, chip system, etc., which can be installed in the terminal device or connected with the terminal device for use. In the technical solutions provided in the present application, the device for realizing the function of the terminal device is taken as an example to describe the technical solutions provided in the present application.

[0061] The access network device and / or the terminal can be fixed or mobile. The access network device and / or the terminal can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; can also be deployed on the water surface; can also be deployed on aircraft, balloons and artificial satellites in the air. The application embodiments do not limit the application scenarios of the access network device and the terminal. The access network device and the terminal device can be deployed in the same scenario or different scenarios, for example, the access network device and the terminal device are deployed on land at the same time; or the access network device is deployed on land and the terminal device is deployed on the water surface, etc., which will not be listed one by one.

[0062] In actual application, a terminal can be assisted to implement wireless access by multiple network devices, and different network devices respectively implement part of functions of a base station. For example, a network device can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and the DU can be separately arranged or can be included in a same network element, for example, a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, for example, a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0063] In different systems, the CU (or CU-CP and CU-UP), the DU, or the RU can also have different names, but a person skilled in the art can understand their meanings. For example, in an ORAN system, the CU can also be referred to as an O-CU (open CU), the DU can also be referred to as an O-DU, the CU-CP can also be referred to as an O-CU-CP, the CU-UP can also be referred to as an O-CU-UP, and the RU can also be referred to as an O-RU. Any of the CU (or CU-CP and CU-UP), the DU, and the RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module. The CU (or CU-CP and CU-UP), the DU, and the RU can implement different protocol layer functions.

[0064] For the convenience of understanding the embodiments of the present application, the terms involved in the present application will be briefly explained in subsequent embodiments. Alternatively, the explanation of some terms can also refer to the explanation in the 3rd generation partnership project (3GPP) standard protocol.

[0065] It should be understood that the technical terms in the present application are only used as examples and are not limited. For example, as the technology evolves, technical terms will also change, and in the case of the same technical meaning, other technical terms should also apply to the present application.

[0066] In 5th Generation Mobile Communication Technology (5G) evolution (5G-Advanced) and later releases, in order to introduce Artificial Intelligence (AI) / Machine Learning (ML) functionalities, for example, AI / ML functionalities can be beam management based on UE-side model, a new mechanism is needed in 3rd Generation Partnership Project (3GPP) standards to manage the Life Cycle Management (LCM) of these functionalities.

[0067] The UE can send an applicability report to the base station (next-generation NodeB, gNB), where the applicability report can also be referred to as a suitability report, and the applicability report can include applicability or inapplicability. Specifically, the UE needs to report to the base station whether the AI / ML configuration received by the UE is applicable to the local environment of the UE. For example, the AI / ML configuration can be one or more channel state information report configurations (CSI-ReportConfig) or inference-related parameter sets for inference. For example, the local environment of the UE includes: whether the model is available, whether the computing power or power of the UE is sufficient, etc.

[0068] Specifically, as shown in FIG. 1, the process of the UE sending the applicability report and the measurement configuration can include the following steps 1 to 6: Figure 2

[0069] Step 1: The base station sends a user equipment capability query (UECapabilityEnqiry) to the UE, which is used to query the capability of the UE corresponding to the radio resource management (RRM) measurement or measurement event prediction.

[0070] Step 2: The UE replies with user equipment capability information (UECapsbilityInformation), which is used for the UE to report to the base station the capability corresponding to the radio resource management (RRM) measurement or measurement event prediction.

[0071] ​Step 3: The base station sends a radio resource control (RRC) reconfiguration to the UE, for example, the RRC reconfiguration includes options A and B. Option A is RRM measurement configuration inference, which can be used for inference configuration. Option B is OtherConfig inference related parameters, which can be used for inference related parameter configuration.

[0072] Step 4: The UE reports the applicability or inapplicability of the inference to the base station through RRC reconfiguration completion (ReconfigurationComplete), or the UE reports the applicability or inapplicability of the inference related parameter configuration to the base station through RRC reconfiguration completion.

[0073] Step 5: The base station sends an RRC reconfiguration to the UE, for example, the RRC reconfiguration includes: RRM measurement configuration can be used in the inference configuration of option B.

[0074] Step 6: The UE reports the applicability or inapplicability of the inference to the base station through RRC reconfiguration completion (ReconfigurationComplete), or the UE reports the applicability or inapplicability of the inference related parameter configuration to the base station through RRC reconfiguration completion.

[0075] When the base station and the UE are in an RRC connected state, for beam management of the UE side model, the UE reports the applicability of the periodic CSI report configuration for inference and related inference parameters to the base station through two kinds of signaling. The two kinds of signaling can include the RRC ReconfigurationComplete used in the above-mentioned step 4 and the user equipment assistance information (UEAssistanceInformation, UAI) shown in the above-mentioned step 7. The RRC ReconfigurationComplete is used for initial applicability reporting, and the UEAssistanceInformation is used for subsequent state change reporting, for example, the state change can be the applicability state change of option A (periodic CSI report configuration for inference) or option B (inference related parameter set), for example, from applicable to inapplicable, or from inapplicable to applicable. For example, Figure 2 The UE can send the UAI to the base station through the UAI for subsequent state change reporting in the RRC connected state. Figure 2

[0076] ​There are two options for the adaptability / inadaptability of RRCReconfigurationComplete containing all the inference configurations:

[0077] Option one, RRCReconfigurationComplete contains the adaptability or inadaptability status of all inference configurations; only UAI contains adaptability change information.

[0078] For the option one solution, although the UE can be synchronized with the network state, the signaling overhead is large, and when the configuration quantity is large and only a small amount of changes, a large amount of redundant information that does not change is transmitted, which seriously wastes air interface resources and UE power consumption.

[0079] Option two, RRCReconfigurationComplete only contains the adaptability / inadaptability status of the inference configuration corresponding to the inference configuration issued in the last RRCReconfiguration containing inference configuration, and the adaptability change status of the inference configuration issued in the previous RRCReconfiguration and reported by the UE at least once; UAI contains adaptability change information. Among them, UAI is auxiliary information sent by the UE to the base station, and the base station does not feedback this information, so the UE cannot directly determine whether the RRC layer of the base station successfully receives and adopts the content of the UAI information. Although UAI is an RLC acknowledged mode (AM) information, the UE can only determine whether the UAI transmission is successful at the RLC layer.

[0080] For the option two solution, although the signaling overhead can be reduced, the UAI message does not have an RRC layer confirmation mechanism, and if an incremental UAI report is lost, the network device cannot perceive the incremental UAI report, resulting in a long-term state difference between the UE and the network device. For example, it will lead to the following error scenarios: the UAI containing adaptability is lost, at which time the UE knows that the UAI transmission has failed; the base station has not successfully received the UAI information, such as semantic transmission failure. Both will cause the network device and the UE to fail to re-synchronize the adaptability state, unless the network device reconfigures the same inference configuration.

[0081] The adaptability / inadaptability is described as follows: RRCReconfigurationComplete should contain the adaptability / inadaptability status of the following contents: all inference configurations contained in the immediately preceding RRCReconfiguration; all inference configurations that have been previously configured and the adaptability / inadaptability has been reported, but the adaptability status has changed since the last report. In addition, the user device needs to process the periodic CSI configuration that has been previously configured and adapted.

[0082] The agreement on adaptability / inadaptability has been reached, but it does not solve the problem that if an incremental UAI report is lost, the network device cannot perceive at all, resulting in long-term synchronization problem between the UE and the network device. Because even if the RLC layer transmission is successful, since UAI is auxiliary information, the network device side (gNB) does not define the confirmation mechanism of the RRC layer, therefore the UE still cannot judge whether the gNB correctly receives and applies the incremental state update information contained in the UAI in the high layer. This semantic loss cannot be effectively detected in the current standard.

[0083] To solve the above problem, the embodiment of the application provides a communication method. In the process of adaptively reporting the inference configuration of the beam management of the UE side model or the inference related parameter, the RRC reconfiguration completion message contains the adaptability / inadaptability state of the following contents: all inference configurations contained in the immediately preceding RRCReconfiguration; all inference configurations that have been previously configured and whose adaptability / inadaptability has been reported, but the adaptability state has changed since the last report; and the UAI includes adaptability change information.

[0084] In the embodiment of the application, the terminal device can report the state version number corresponding to the adaptability to the network device, and the state version number is used to identify the change sequence of the UE side adaptability state, so as to support incremental reporting, loss detection and state recovery.

[0085] The embodiment of the application provides a communication method, as shown in Figure 3 The communication method provided by the embodiment of the application is applied to a first communication device and a second communication device. The first communication device can be a terminal device, and the second communication device can be a network device. The implementation mode of the first communication device and the second communication device is not limited in the embodiment of the application. The interaction mode between the terminal device and the network device is not limited in the embodiment of the application. In the embodiment of the application, multiple terminal devices can interact with the network device respectively, for example, a first terminal device interacts with the network device, and a second terminal device interacts with the network device. It is not limited that the network device can also interact with three terminal devices or more terminal devices.

[0086] The first communication device in the following steps 301 to 305 can be one terminal device or multiple terminal devices. The interaction process between the first communication device and the second communication device is exemplarily described. The communication method provided by the embodiment of the application is an interaction method between the first communication device and the second communication device, and can include the following steps.

[0087] 301. The terminal device obtains a first state version number corresponding to a first adaptability of the terminal device.

[0088] The first adaptability of the terminal device can be adaptability of the terminal device to the AI / ML configuration, for example, the first adaptability of the terminal device can be whether one or more channel state information report configurations CSI-ReportConfig or inference-related parameter sets sent by the network device for inference are applicable to the local environment of the terminal device. The first adaptability of the terminal device can dynamically change according to the local environment of the terminal device, and the first state version number can be used to describe the updated state version of the first adaptability of the terminal device.

[0089] For example, the terminal device can design a version number for the first adaptability of the terminal device, define a globally monotonically increasing state version number at the terminal device side. For different states of the first adaptability, corresponding state version numbers can be used respectively, and the corresponding state version number can be updated after the state of the first adaptability is updated.

[0090] In some embodiments of the present application, step 301, the terminal device obtains a first state version number corresponding to the first adaptability of the terminal device, comprising:

[0091] A1. The terminal device obtains an updated first configuration item corresponding to the first adaptability of the terminal device.

[0092] A2. The terminal device updates the current state version number of the first adaptability according to the first configuration item to obtain the first state version number.

[0093] The terminal device can determine the update of the first adaptability according to the change of the local environment of the terminal device, for example, the local environment of the terminal device can be whether the model is available, whether the computing power of the terminal device is sufficient, and whether the power of the terminal device is sufficient. The terminal device can update the first adaptability to determine the updated first configuration item corresponding to the first adaptability. For example, the first adaptability can include a plurality of configuration items, and the terminal device can update the first configuration item in the plurality of configuration items. The terminal device can store the current state version number of the first adaptability, which is a global current state version number at the terminal device side. The global current state version number at the terminal device side has an initial value of 0 and a monotonically increasing value. The current state version number can be updated by the first configuration item, thereby obtaining the first state version number, so that the terminal device side can store the latest current state version number.

[0094] For example, the current state version number is CurrentVersion, which is a global current state version number at the terminal device side, and the initial value is 0. The terminal device maintains the CurrentVersion according to the state version number corresponding to the first adaptability.

[0095] In some embodiments of the present application, the communication method performed by the terminal device can further include the following steps:

[0096] B1. The terminal device updates the state of the first configuration item in the configuration item state list according to the first configuration item corresponding to the first adaptability.

[0097] The terminal device can further store a configuration item state list, which can include all configuration items of the first adaptability. After updating the first configuration item corresponding to the first adaptability, the terminal device can update the state of the first configuration item in the configuration item state list according to the first configuration item, so that the configuration item state list can store a complete state list of all current configuration items. For example, the configuration item state list can be ApplicabilityReportList, and the terminal device maintains the ApplicabilityReportList according to the first configuration item corresponding to the first adaptability.

[0098] In some embodiments of the present application, the communication method performed by the terminal device can further include the following steps:

[0099] C1. The terminal device stores the first state version number corresponding to the first adaptability into the pending status change queue.

[0100] To solve the problem that the first state version number corresponding to the first adaptability is not correctly received by the network device, the terminal device can further store a pending status change queue, which can also be referred to as a pending status change queue. The first state version number that is not correctly received by the network device is stored in the pending status change queue. For example, the pending status change queue can be PendingStatusChangeList, and the terminal device maintains the PendingStatusChangeList according to the state version number corresponding to the first adaptability.

[0101] 302. The terminal device sends first information to the network device, and the first information is used to indicate the first state version number. Correspondingly,

[0102] 303. The network device receives the first information from the terminal device, and the first information is used to indicate the first state version number corresponding to the first adaptability of the terminal device.

[0103] In the embodiments of the present application, after the terminal device determines the first state version number, the terminal device can send the first state version number through the first information, so that the network device receives the first information, and the network device can obtain the first state version number by analyzing the first information. The implementation of the first information is not limited.

[0104] In some embodiments of the present application, the first information includes at least one of the following: a first radio resource control reconfiguration complete message, and first user equipment assistance information.

[0105] The first information sent by the terminal device can be an RRC message. Specifically, the RRC message can be at least one of the first radio resource control reconfiguration complete message and the first user equipment assistance information. The terminal device can carry the first state version number through the first radio resource control reconfiguration complete message, and the first radio resource control reconfiguration complete message can be the RRCReconfigurationComplete in the foregoing embodiments. For example, the terminal device can carry the first state version number through the first user equipment assistance information, and the first user equipment assistance information can be the UEAssistanceInformation in the foregoing embodiments. The present application does not limit the implementation of other types of first information carrying the first state version number in the embodiments.

[0106] For example, the terminal device can receive the following three configurations from the network device: inferenceConfig-1 (configuration ID = 1); inferenceConfig-2 (configuration ID = 2); and inferenceConfig-3 (configuration ID = 3). The terminal device can first report the state when the network device replies to the RRCReconfigurationComplete: ID1 is applicable, ID2 is applicable, and ID3 is not applicable (the model is not loaded). The terminal device can additionally carry the state version number v1 in the first information reported by the terminal device, and the state of both parties is consistent at this time. Subsequently, the terminal device changes due to insufficient power and changes in the local environment: ID3 becomes applicable (low-power model is loaded), and ID2 becomes not applicable (high-power model is unloaded). The terminal device can generate the state version number v2 reported by the UAI.

[0107] In some embodiments of the present application, the first information includes a first field, the first field is used to indicate the first state version number, and the first field belongs to a packet data convergence protocol layer (PDCP) or a medium access control layer (MAC).

[0108] Correspondingly, in some embodiments of the present application, the communication method performed by the network device further includes:

[0109] The network device determines the first field from the packet data convergence protocol layer (PDCP) or the medium access control layer (MAC) of the first information, and the first field is used to indicate the first state version number.

[0110] The terminal device can configure a first field in the first information, and the position and size of the first field in the first information are not limited. Specifically, the terminal device can set the first field in a PDCP or MAC layer header, and indicate the first state version number through the first field. After receiving the first information, the network device can first parse the PDCP or MAC layer to obtain the first field, and determine the first state version number according to the data content carried by the first field.

[0111] In the embodiments of the present application, the global first state version number can be placed in a packet data convergence protocol layer (PDCP) or a medium access control layer (MAC) protocol header, so that the network device side can quickly detect the continuity of the state reporting before parsing the RRC message content.

[0112] For example, the terminal device can design and carry the state version number. First, a globally monotonically increasing state version number is defined at the terminal device side, which is embedded in the PDCP data protocol data unit header or the MAC subheader as a new field, and is sent to the base station together with the data packet carrying the RRC message (such as RRCReconfigurationComplete and UAI). For example, the state version number can be added to RRCReconfigurationComplete and UAI.

[0113] 304. In the case that the first state version number is not continuous with the state version number stored by the network device, the network device sends second information to the terminal device, and the second information is used to trigger the terminal device to report the first adaptability.

[0114] Correspondingly, 305. The terminal device receives the second information from the network device, and the second information is used to trigger the terminal device to report the first adaptability.

[0115] The network device can store a state version number, for example, the network device timely stores the latest state version number after receiving the state version number from the terminal device each time. Therefore, after receiving the first state version number in the first information, the network device can compare the first state version number with the state version number stored by the network device to determine whether the first state version number and the state version number stored by the network device are continuous, and determine whether the network device correctly receives the latest state version number from the terminal device according to whether the state version numbers are continuous. The state version numbers are continuous means that the first state version number is greater than the state version number stored by the network device, and the first state version number and the state version number stored by the network device are in a sequentially increasing relationship. For example, the interval step length of the state version number is 1, the first state version number is V1, and the state version number stored by the network device is V2. It can be determined that the first state version number and the state version number stored by the network device are continuous. For another example, the interval step length of the state version number is 2, and the state version numbers V1 and V3 are continuous. For another example, the first state version number is Va, and the state version number stored by the network device is Vb. It is determined that Va and Vb are continuous.

[0116] In the case where the first state version number and the state version number stored by the network device are not continuous, it is indicated that the first state version number of the first adaptability transmitted by the terminal device is lost, and the network device cannot achieve state synchronization with the terminal device. In this case, the network device sends second information to the terminal device, and the second information is used to trigger the terminal device to report the first adaptability.

[0117] The terminal device receives the second information, determines that the network device does not correctly receive the first state version number of the first adaptability transmitted by the terminal device according to the second information, determines that the network device cannot achieve state synchronization with the terminal device, and can trigger the terminal device to report the first adaptability according to the second information. Therefore, the terminal device can determine that the network device does not correctly receive the first state version number, and can trigger the terminal device to report the first adaptability, so that the network device can correctly receive the first adaptability. In the embodiment of the present application, the network device can detect the loss of the first information reporting and actively request full synchronization by means of the version number mechanism, which significantly improves the reliability while maintaining the compatibility with the traditional terminal device.

[0118] In some embodiments of the present application, the state version number stored by the network device is the last valid state version number received by the network device from the terminal device.

[0119] The network device can store a last valid state version number, and the network device can determine whether the state version numbers are continuous according to the stored state version number and the first state version number. For example, the state version number stored by the network device can be LastKnownVersion, which is used to record the last valid state version number received from the terminal device.

[0120] In some embodiments of the present application, the communication method performed by the network device further includes:

[0121] D1. In a case where the first state version number is continuous with the state version number stored by the network device, the network device parses the first information through a radio resource control layer (RRC).

[0122] In a case where the first state version number is continuous with the state version number stored by the network device, it indicates that the state version of the first adaptability transmitted by the terminal device is successfully received by the network device, and the network device can achieve state synchronization with the terminal device. In this case, the network device can continue to parse the first information, so that complete data packets can be obtained from the first information. For example, the data packets can include an updated configuration of the first adaptability.

[0123] In some embodiments of the present application, the communication method performed by the network device further includes:

[0124] E1. In a case where the first state version number is continuous with the state version number stored by the network device, the network device updates an adaptability state list of the network device according to the first state version number.

[0125] The network device can maintain an adaptability state list, and the last complete adaptability reported by the terminal device can be stored in the adaptability state list. In a case where the first state version number is continuous with the state version number stored by the network device, it indicates that the state version of the first adaptability transmitted by the terminal device is successfully received by the network device, and the network device can achieve state synchronization with the terminal device. In this case, the network device can update the adaptability state list of the network device according to the first state version number, that is, the latest state version number received can be stored in the adaptability state list, so that the latest state version number of the first adaptability transmitted by the terminal device can be stored according to the adaptability state list, and therefore the network device can perform loss detection based on the state version number.

[0126] The network device side can perform state version number detection and recovery mechanism as follows. The network device maintains the latest known version number and state list of the terminal device. When the network device receives a data packet, the state version number is first extracted from the underlying protocol header. If the state version number included in the underlying protocol header is not continuous with the latest state version number stored locally by the network device, it is determined that the state synchronization has been lost, and the terminal device is triggered to perform full state reporting by immediately issuing an RRC reconfiguration message carrying a full reporting request, so as to realize synchronization recovery.

[0127] In some embodiments of the present application, after the terminal device receives the second information from the network device in step 305, the communication method performed by the terminal device further includes the following steps:

[0128] F1. The terminal device obtains the first state version number and the second state version number from the to-be-reported state change queue, and the second state version number is a state version number of a changed but not reported configuration in the to-be-reported state change queue;

[0129] F2. The terminal device sends third information to the network device, and the third information is used to indicate the first state version number and the second state version number.

[0130] Correspondingly, the communication method performed by the network device further includes:

[0131] F3. The network device receives third information from the terminal device, and the third information is used to indicate the first state version number and the second state version number.

[0132] The terminal device can store the first state version number in the to-be-reported state change queue, and the to-be-reported state change queue can also store the second state version number. The second state version number is stored in the to-be-reported state change queue before the first state version number is stored. The second state version number is a state version number of a changed but not reported configuration. The to-be-reported state change queue can be used to send the configuration state corresponding to the first adaptability loss together with other configuration states whose adaptability has been changed or needs to be reported. The to-be-reported state change queue can include two types of configurations: one type is a configuration whose state has been changed but has not been reported, such as the second state version number, and the other type is a configuration of the first adaptability loss, such as the first state version number.

[0133] The terminal device determines, according to the second information, that the network device does not correctly receive the first state version number of the first adaptability transmitted by the terminal device, and determines that the network device cannot synchronize the state with the terminal device. The terminal device can send the first state version number and the second state version number in the state change queue to be reported in a merged manner. The terminal device indicates the first state version number and the second state version number through the third information. The terminal device sends the third information, and the network device receives the third information. According to the third information, the first state version number and the second state version number can be obtained. In the embodiment of the application, the terminal device can send the first state version number and the second state version number in the state change queue to be reported in a merged manner, thereby improving the communication efficiency.

[0134] For example, in the embodiment of the application, a state change queue is introduced on the terminal device side, so that even if the RLC layer transmission fails, the unconfirmed state change can be retransmitted in the subsequent reporting opportunity, thereby solving the two problems of semantic loss and transmission failure. The semantic loss refers to that the RRC layer of the network device has received the signaling, but has not correctly extracted or adopted the information contained in the signaling. The transmission failure refers to that the signaling fails to be transmitted to the RRC layer of the network device, and the transmission failure occurs at the bottom layer of the RRC layer, which can include the physical layer, the data link layer, etc.

[0135] In the embodiment of the application, the second state version number can be a newly configured initial state, and the first state version number can be an incremental update of the old configuration. The state synchronization can be realized by relying on the version number through the third information. The reporting flexibility and synchronization efficiency are improved, a plurality of state updates can be completed in a single reconfiguration, and the long-term inconsistency problem caused by the loss of the first information is avoided.

[0136] For example, the terminal device side has a state version number buffer and a merged reporting mechanism. The terminal device maintains a state change queue to be reported. When the adaptability state changes, the adaptability state change is added to the state change queue to be reported, and an incremental reporting is attempted through a UE auxiliary information (UAI) message. If the UAI message fails to be sent at the RLC layer, the change item of the adaptability state change continues to be retained in the state change queue to be reported. When the UE auxiliary information or the RRC reconfiguration completion message is sent next time, the terminal device merges and reports all unconfirmed change items in the state change queue to be reported, and only after the network side successfully receives, the state change queue to be reported is emptied.

[0137] Further, in some embodiments of the application, the communication method performed by the terminal device further includes the following steps:

[0138] G1. In a case that the first information is sent successfully through the radio link control layer (RLC) confirmation, the terminal device clears the first state version number from the pending state change queue.

[0139] In the foregoing implementation scenario of step C1, the terminal device can store the first state version number in the pending state change queue, and can determine whether the first information is sent successfully through the RLC confirmation. In a case that the first information is sent successfully, the terminal device clears the first state version number from the pending state change queue, so that the pending state change queue can be maintained in a timely manner.

[0140] For example, when the RRC reconfiguration complete message is sent, the UE can determine whether the base station successfully receives the configuration in two ways. One is to observe whether the same RRCReconfiguration signaling with the same configuration is received by the base station. The base station starts a timer when sending the RRCReconfiguration signaling. If the UE does not receive the RRCReconfigurationComplete feedback before the timer expires, the base station will resend the signaling. Therefore, when the UE receives the resending signaling, it means that the base station does not successfully receive the previous configuration. The other is to receive the ACK feedback of the underlying layer (such as the RLC layer). If the ACK is received, it means that the network device successfully receives the configuration.

[0141] For the change item reported through the UAI but not confirmed, the UE can only determine whether the transmission is successful through the RLC layer feedback, but cannot confirm whether the base station successfully receives and applies the signaling in the RRC layer. There may be a case that the RLC transmission is successful but the RRC layer is not parsed. The base station can trigger a full report request through the recovery mechanism provided in the embodiments of the present application, for example, detect the discontinuous version number, and finally realize the consistent synchronization of the reasoning configuration state of the terminal device and the network device.

[0142] In some embodiments of the present application, the second information includes: a first radio resource control reconfiguration message;

[0143] The first radio resource control reconfiguration message includes: a second field, and the second field is used to instruct the terminal device to perform the adaptive full state report.

[0144] The second information can be an RRC message, and specifically, the RRC message can be a first radio resource control reconfiguration message. The first radio resource control reconfiguration message includes a second field, and the position and size of the second field in the first radio resource control reconfiguration message are not limited. The second field is used to instruct the terminal device to perform adaptive full-state reporting. For example, full-state reporting refers to that the UE terminal device sends an adaptive state or a non-adaptive state containing all inference configurations to the network device.

[0145] In some embodiments of the present application, the communication method performed by the terminal device further includes:

[0146] H1. The terminal device determines, according to the second information, that the terminal device performs adaptive full-state reporting.

[0147] H2. The terminal device sends fourth information to the network device, where the fourth information is used to indicate the states of all configuration items in the configuration item state list.

[0148] Correspondingly, the communication method performed by the network device further includes:

[0149] H3. The network device receives fourth information from the terminal device, where the fourth information is used to indicate the states of all configuration items in the configuration item state list of the terminal device.

[0150] In the above scheme, the network device can instruct the terminal device to perform adaptive full-state reporting through the second information. The terminal device stores a configuration item state list, and the configuration item state list includes the states of all configuration items of the first adaptability. Therefore, the terminal device can send fourth information to the network device, where the fourth information is used to indicate the states of all configuration items in the configuration item state list. For example, the fourth information can be an RRC reconfiguration complete message, and the RRC reconfiguration complete message includes the states of all configuration items of the first adaptability. Therefore, the network device can obtain the full states of all configuration items of the first adaptability according to the fourth information.

[0151] As can be known from the foregoing embodiments, the terminal device sends the first information to the network device, and the first information indicates the first state version number. By introducing the state version number, the network device can detect whether the loss of adaptability reported by the terminal device occurs by means of whether the state version number is continuous. Therefore, the terminal device can receive the second information sent by the network device, and trigger the terminal device to report the first adaptability according to the second information. In the embodiments of the present application, the signaling overhead can be reduced, repeated transmission of unchanged states can be avoided, and when the loss is detected, the terminal device can be actively requested to report the first adaptability to restore the adaptability state synchronization, thereby improving the reliability of communication between the terminal device and the network device.

[0152] The main technical solutions of the embodiments of the present application are introduced in detail in combination with texts and figures in view of the problems existing in the above scenarios or for realizing the above scenarios.

[0153] In the embodiments of the present application, the terminal device is UE, and the network device is a base station.

[0154] The communication method performed by the base station side (gNB) is described.

[0155] First, the network device maintains the state, and the base station maintains the following two types of state information for each connected UE:

[0156] Last Known Version: records the last valid state version number received from the UE.

[0157] Last Known Full Status List: records the last complete adaptability status list reported by the UE.

[0158] Among them, the last complete adaptability status list includes: the periodic CSI report configuration and inference related parameters for inference issued by the base station to the UE and the corresponding adaptability information, and the base station can configure resources for the UE according to the last complete adaptability status list.

[0159] Next, the base station receiving processing and version number detection are described.

[0160] When the base station receives a data packet carrying RRC signaling (such as RRCReconfigurationComplete or UEAssistanceInformation) from the UE: parse the data packet header at the PDCP layer or MAC layer, extract the StatusVersion field therein, and obtain the received version number (ReceivedVersion).

[0161] The base station can compare the received version number (ReceivedVersion) with the locally stored last known version number (LastKnownVersion).

[0162] If ReceivedVersion == LastKnownVersion + 1, that is, the state version number is continuous, the base station can determine that the state is continuous. The base station submits the received data packet to the RRC layer for further analysis. The RRC layer applies the incremental or full status information in the message to update the local LastKnownFullStatusList. The LastKnownVersion is updated to ReceivedVersion.

[0163] If ReceivedVersion!= LastKnownVersion + 1, i.e. the state version number is not continuous, the base station can determine that the state synchronization has been lost.

[0164] Optionally, the base station in the embodiments of the present application can also discard or attempt to parse the RRC message, but not apply the state information in the LastKnownFullStatusList.

[0165] Next, it is explained that the network device can also trigger the recovery mechanism. When the version number is detected to be discontinuous, the base station requests the state synchronization recovery by issuing an RRCReconfiguration message. The message can contain an added indication field, for example, the indication field can be used to request a full applicability report (requestFullApplicabilityReport), and the indication field takes a value of true to instruct the UE to report the full state. The full state report refers to that the UE reports all the inference configuration applicability / inapplicability states in the RRCReconfigurationComplete.

[0166] The above describes the communication method of the base station side, and next, the communication method executed by the terminal device (UE) is described.

[0167] First, the UE side maintains the state. Specifically, the UE side maintains the following three states: a global current state version number (CurrentVersion), the initial value of which is 0. A complete state list of all current configuration items (ApplicabilityReportList). A state change queue to be reported (PendingStatusChangeList).

[0168] For example, there are four configurations on the UE side, and the IDs of the four configurations are 1, 2, 3 and 4 respectively. The specific state management logic is as follows: when the adaptability state of configuration 4 changes, the UE reports the change through UAI, but the transmission fails and no ACK feedback is received. At this time, the UE will store the change information of configuration 4 into PendingStatusChangeList. In addition, if there is a configuration (such as configuration 3) whose state has changed but has not been reported, the change information of configuration 3 will also be stored into PendingStatusChangeList. In the above example, the ApplicabilityReportList contains the IDs of all four configurations (1, 2, 3, 4) and their current adaptability states. The PendingStatusChangeList only contains the change information of configurations 3 and 4, that is, the PendingStatusChangeList includes the state change content to be reported.

[0169] Next, the state change on the UE side and the UAI reporting are described. When the local environment of the UE changes, causing the adaptability state of an AI configuration to change, the state of the corresponding configuration item in the ApplicabilityReportList is updated. The configuration ID corresponding to the change item and the updated state are added to the PendingStatusChangeList. The CurrentVersion is incremented by 1. The UEAssistanceInformation message is constructed, and the applicabilityReportList field of the user assistance information contains all change items in the PendingStatusChangeList. When sending the data packet corresponding to the UAI message, the StatusVersion field in the header of the PDCP or MAC layer is set to the new CurrentVersion.

[0170] The UE can hand over the UAI message to the underlying layer for transmission. The underlying layer refers to the PDCP layer, which is first passed through the PDCP layer, then the RLC layer, then the MAC layer, and finally the physical layer. The version number can be added to the header of the layer in the PDCP layer or the MAC layer.

[0171] If the RLC layer confirms that the transmission is successful, the PendingStatusChangeList is emptied. If the RLC layer indicates that the transmission fails, for example, the maximum number of retransmissions is reached, the PendingStatusChangeList remains unchanged, and waits for the next reporting opportunity.

[0172] Next, the UE side response to network request and RRCReconfigurationComplete reporting are explained. When the UE receives the RRCReconfiguration message from the base station, the UE can process the configuration update in the message and update the local ApplicabilityReportList accordingly.

[0173] For example, the UE checks whether the message contains requestFullApplicabilityReport = true. If it contains requestFullApplicabilityReport = true, it is prepared to make a full report once. The ApplicabilityReportList is used as the reporting content. If it does not contain requestFullApplicabilityReport = true, only the state changes due to this reconfiguration are added to the PendingStatusChangeList, and an incremental report is prepared. The CurrentVersion is incremented by 1.

[0174] In addition, the UE side can also reply to the network device with the RRCReconfigurationComplete message. The applicabilityReportList field of this message is determined to be a full list or an incremental list in the PendingStatusChangeList.

[0175] When sending the data packet corresponding to the RRCReconfigurationComplete message, the StatusVersion field in the underlying protocol header is set to the new CurrentVersion. If the RLC layer confirms that the sending is successful, the PendingStatusChangeList is emptied.

[0176] By introducing the version number and incremental reporting indication mechanism, both RRCReconfigurationComplete and UEAssistanceInformation signaling support incremental reporting, and the network device can detect whether reporting loss has occurred by means of the version number. This significantly reduces signaling overhead, avoids repeated transmission of unchanged states, and at the same time, when loss is detected, it can actively request a full report to restore synchronization, improving system reliability.

[0177] It should be noted that, for the foregoing method embodiments, in order to simply describe, they are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited to the action sequence described, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily necessary for the present application.

[0178] In order to better implement the above scheme of the embodiments of the present application, the related device for implementing the above scheme is also provided.

[0179] Please refer to Figure 4 The communication device 400 provided by the embodiments of the present application, for example, the communication device is specifically a first communication device, for example, the first communication device is a terminal device, the communication device can include: a processing module 401, a communication module 402, wherein,

[0180] The processing module is used for acquiring a first state version number corresponding to a first adaptability of a terminal device;

[0181] The communication module is used for sending first information to a network device, the first information being used for indicating the first state version number;

[0182] The communication module is used for receiving second information from the network device, the second information being used for triggering the terminal device to report the first adaptability.

[0183] The method performed by the component modules of the terminal device can refer to the foregoing Figure 3 The communication method performed by the terminal device shown in the foregoing

[0184] Please refer to Figure 5 The communication device 500 provided by the embodiments of the present application, for example, the communication device is specifically a second communication device, for example, the second communication device is a network device, the communication device can include: a communication module 501;

[0185] The communication module is used for receiving first information from a terminal device, the first information being used for indicating a first state version number corresponding to a first adaptability of the terminal device;

[0186] The communication module is used for sending second information to the terminal device in a case where the first state version number is not continuous with a state version number stored by the network device, the second information being used for triggering the terminal device to report the first adaptability.

[0187] The method performed by the component modules of the network device can refer to the foregoing Figure 3 The communication method performed by the network device shown in the foregoing

[0188] Figure 6 An example of an electronic device is provided for the embodiments of the present application. The electronic device can be a first device, including but not limited to a base station, a core network unit. Figure 6 A simplified block diagram of a base station is shown. The base station includes a processor 1610 part, a memory 1620 part, and a transceiver 1630 part. The processor 1610 part is mainly used for baseband processing, controlling the base station, etc.; the processor 1610 part is usually the control center of the base station, and can be referred to as a processor, which is used to control the base station to perform the processing operations of the first device side in the above method embodiments. The memory 1620 part is mainly used for storing computer program codes and data. The transceiver 1630 part is mainly used for transceiving radio frequency signals and converting radio frequency signals and baseband signals; the transceiver 1630 part can be referred to as a transceiving module, a transceiver, a transceiving circuit, or a transceiver, etc. The transceiving module of the transceiver 1630 part, which can also be referred to as a transceiver or a transceiver, includes an antenna 1633 and a radio frequency circuit (not shown in the figure), wherein the radio frequency circuit is mainly used for radio frequency processing. Optionally, the devices in the transceiver 1630 part for realizing the receiving function can be regarded as a receiver, and the devices for realizing the sending function can be regarded as a transmitter, that is, the transceiver 1630 part includes a receiver 1632 and a transmitter 1631. The receiver can also be referred to as a receiving module, a receiver, or a receiving circuit, etc., and the transmitter can be referred to as a transmitting module, a transmitter, or a transmitting circuit, etc. Figure 6 The processor 1610 part and the memory 1620 part can include one or more single boards, each of which can include one or more processors and one or more memories. The processor is used to read and execute the program in the memory to realize the baseband processing function and the control of the base station. If there are multiple single boards, the single boards can be interconnected to enhance the processing capability. As an optional implementation, multiple single boards can also share one or more processors, or multiple single boards can share one or more memories, or multiple single boards can share one or more processors at the same time.

[0189] The processor 1610 part and the memory 1620 part can include one or more single boards, each of which can include one or more processors and one or more memories. The processor is used to read and execute the program in the memory to realize the baseband processing function and the control of the base station. If there are multiple single boards, the single boards can be interconnected to enhance the processing capability. As an optional implementation, multiple single boards can also share one or more processors, or multiple single boards can share one or more memories, or multiple single boards can share one or more processors at the same time.

[0190] For example, in an implementation, the transceiving module of the transceiver 1630 part is used to execute the transceiving-related processes performed by the base station (the first device) in the foregoing method embodiments. The processor of the processor 1610 part is used to execute the processing-related processes performed by the base station in the foregoing method embodiments.

[0191] It should be understood that, Figure 6 The network device described above including the processor, the memory, and the transceiver can not depend on Figure 6 the structure shown.

[0192] Figure 7 Another example of an electronic device is provided in the embodiments of the present application. The electronic device can be a second device, which can be a terminal, including but not limited to a mobile phone, a smart wearable device (such as a smart watch), and the like. Taking a mobile phone as an example, the electronic device can include a processor 310, an external memory interface 320, an internal memory 321, a display screen 330, a camera 340, an antenna 1, an antenna 2, a mobile communication module 350, and a wireless communication module 360, and the like.

[0193] It can be understood that the structure illustrated in the embodiments does not constitute a specific limitation on the electronic device. In other embodiments, the electronic device can include more or fewer components than those illustrated, or combine certain components, or split certain components, or different arrangement of components. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0194] The processor 310 can include one or more processing units, for example: the processor 310 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units can be independent devices, or can be integrated in one or more processors.

[0195] It can be understood that the interface connection relationship between the modules illustrated in the embodiments is only illustrative and does not constitute a structural limitation on the electronic device. In other embodiments of the present application, the electronic device can also use different interface connection methods or a combination of multiple interface connection methods.

[0196] The external memory interface 320 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device. The external memory card communicates with the processor 310 through the external memory interface 320 to realize the data storage function. For example, files such as music and videos are saved in the external memory card.

[0197] The internal memory 321 can be used to store computer executable program codes, which include instructions. The processor 310 performs various function applications and data processing of the electronic device by running the instructions stored in the internal memory 321. The internal memory 321 can include a program storage area and a data storage area. The program storage area can store an operating system, application programs (such as a sound play function, an image play function, etc.) required by at least one function, etc. The data storage area can store data (such as audio data, a phone book, etc.) created during the use of the electronic device, etc. In addition, the internal memory 321 can include a high-speed random access memory, and can further include a non-volatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 310 performs various function applications and data processing of the electronic device by running the instructions stored in the internal memory 321 and / or the instructions stored in the memory disposed in the processor.

[0198] The wireless communication function of the electronic device can be implemented through the antenna 1, the antenna 2, the mobile communication module 350, the wireless communication module 360, a modem processor, and a baseband processor, etc.

[0199] The antenna 1 and the antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example, the antenna 1 can be multiplexed as a diversity antenna of a wireless local area network. In some other embodiments, the antennas can be used in combination with a tuning switch.

[0200] The mobile communication module 350 can provide a solution including 2G / 3G / 4G / 5G wireless communication applied to the electronic device. The mobile communication module 350 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 350 can receive electromagnetic waves from the antenna 1, and perform filtering, amplification, etc. on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 350 can also amplify the signals modulated by the modem processor, and convert the signals into electromagnetic waves to be radiated out through the antenna 1. In some embodiments, at least part of the function modules of the mobile communication module 350 can be disposed in the processor 310. In some embodiments, at least part of the function modules of the mobile communication module 350 and at least part of the modules of the processor 310 can be disposed in the same device.

[0201] In some embodiments, the electronic device initiates or receives a call request through the mobile communication module 350 and the antenna 1.

[0202] Furthermore, an operating system runs on top of the aforementioned components. Examples include iOS, Android, and Windows operating systems. Applications can be installed and run on this operating system. Those skilled in the art will understand that, for the sake of convenience and brevity, explanations and beneficial effects of the relevant content in any of the above-described electronic devices can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0203] This application also provides a communication system, which may include, for example, Figure 6 The first device shown (e.g., a network device such as a base station) and such as Figure 7 The second device shown is (e.g., a mobile phone or other terminal).

[0204] In this application, the terminal or network device may include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system layer may 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 may include applications such as browsers, address books, word processing software, and instant messaging software.

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

[0206] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules 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, or indirect coupling or communication connection between devices or modules, and may be electrical, mechanical, or other forms.

[0207] The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed to multiple network modules. Part or all of the modules can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0208] In addition, the functional modules in each embodiment of the present application can be integrated into one processing module, or each module can exist physically alone, or two or more modules can be integrated into one module. The integrated module can be realized in the form of hardware or in the form of a software functional module.

[0209] The integrated module, if realized in the form of a software functional module and sold or used as an independent product, can be stored in a computer readable storage medium. Based on this understanding, the essential part of the technical solutions of the present application or the whole or part of the technical solutions can be embodied in the form of a software product, which is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the processes of the methods described in each embodiment of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk, and various program code storage media.

[0210] The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that the technical solutions recorded in the foregoing embodiments can be modified, or some technical features can be replaced by equivalents; and these modifications or replacements do not make the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A communication method characterized by comprising: The method comprises: obtaining a first state version number corresponding to a first adaptability of a terminal device, the first state version number being used for the terminal device to perform incremental reporting when a state of the first adaptability changes; sending first information to a network device, the first information being used for indicating the first state version number, the first state version number being used for the network device to determine whether the first state version number is continuous with a state version number stored by the network device; receiving second information from the network device, the second information being used for triggering the terminal device to report the first adaptability.

2. The method of claim 1, wherein, The first information comprises a first field used for indicating the first state version number, and the first field belongs to a packet data convergence protocol (PDCP) layer or a medium access control (MAC) layer.

3. The method according to claim 1 or 2, characterized in that, The method further comprises: obtaining an updated first configuration item corresponding to the first adaptability of the terminal device; updating a current state version number of the first adaptability according to the first configuration item to obtain the first state version number.

4. The method of claim 3, wherein, The method further comprises: updating a state of the first configuration item in a configuration item state list according to the first configuration item corresponding to the first adaptability.

5. The method of any one of claims 1 to 2, wherein, The method further comprises: storing the first state version number corresponding to the first adaptability into a to-be-reported state change queue.

6. The method of claim 5, wherein, After the second information is received from the network device, the method further comprises: obtaining the first state version number and a second state version number from the to-be-reported state change queue, the second state version number being a state version number of a configuration that has changed but has not been reported in the to-be-reported state change queue; sending third information to the network device, the third information being used for indicating the first state version number and the second state version number.

7. The method of claim 5, wherein, The method further comprises: emptying the first state version number from the to-be-reported state change queue in a case that the first information is successfully sent through a radio link control (RLC) acknowledgement.

8. The method of claim 4, wherein, The method further comprises: determining, according to the second information, that the terminal device performs full-state reporting of adaptability; sending fourth information to the network device, the fourth information being used for indicating states of all configuration items in the configuration item state list.

9. The method of any one of claims 1 to 2, wherein, The first information comprises at least one of the following: a first radio resource control (RRC) reconfiguration complete message and first user equipment (UE) assistance information.

10. A communication method characterized by comprising: The method comprises: receiving first information from a terminal device, the first information being used for indicating a first state version number corresponding to a first adaptability of the terminal device, the first state version number being used for the terminal device to perform incremental reporting when a state of the first adaptability changes; in a case that the first state version number is not continuous with a state version number stored by a network device, sending second information to the terminal device, the second information being used for triggering the terminal device to report the first adaptability.

11. The method of claim 10, wherein, The state version number stored by the network device is a last valid state version number received by the network device from the terminal device.

12. The method according to claim 10 or 11, characterized in that, The method further comprises: determine a first field from a packet data convergence protocol (PDCP) layer or a medium access control (MAC) layer of the first information, the first field being used to indicate the first state version number.

13. The method of any one of claims 10-11, wherein, The method further comprises: in a case where the first state version number is continuous with a state version number stored by a network device, parsing the first information by a radio resource control (RRC) layer.

14. The method of any one of claims 10-11, wherein, The method further comprises: in a case where the first state version number is continuous with a state version number stored by a network device, updating an adaptation state list of the network device according to the first state version number.

15. The method of any one of claims 10-11, wherein, The first information comprises at least one of: a first radio resource control (RRC) reconfiguration complete message, and a first user equipment (UE) assistance information.

16. The method of any one of claims 10-11, wherein, The second information comprises: a first radio resource control (RRC) reconfiguration message. The first radio resource control (RRC) reconfiguration message comprises: a second field, the second field being used to indicate that the terminal device reports an adaptation full state.

17. A terminal device, comprising: The terminal device comprises: a processing module configured to obtain a first state version number corresponding to a first adaptation of a terminal device, the first state version number being used for the terminal device to perform incremental reporting when a state of the first adaptation changes; a communication module configured to send first information to a network device, the first information being used to indicate the first state version number, the first state version number being used for the network device to determine whether the first state version number is continuous with a state version number stored by the network device; the communication module is configured to receive second information from the network device, the second information being used to trigger the terminal device to report the first adaptation.

18. A network device, comprising: The network device comprises: a communication module configured to receive first information from a terminal device, the first information being used to indicate a first state version number corresponding to a first adaptation of the terminal device, the first state version number being used for the terminal device to perform incremental reporting when a state of the first adaptation changes; the communication module is configured to, in a case where the first state version number is not continuous with a state version number stored by a network device, send second information to the terminal device, the second information being used to trigger the terminal device to report the first adaptation.

19. A communications device, characterized by The communication device comprises: a memory configured to store computer programs or computer instructions; a processor configured to execute the computer programs or computer instructions stored in the memory, so that the communication device performs the method according to any one of claims 1 to 16.

20. A computer storage medium storing a computer program, characterized in that, The computer program is executed to implement the method according to any one of claims 1 to 16.

Citation Information

Patent Citations

  • Dynamic updates of applicability reporting for ai / ML models

    WO2024210809A1