Communication method, communication apparatus and communication system

Abstract

Provided in the embodiments of the present application are a communication method, a communication apparatus and a communication system. The method comprises: a second node negotiating a first mapping relationship with a first node, wherein the first mapping relationship is used for indicating a mapping relationship between states of a first capability of the second node and identifiers of the states; and the second node sending first information to the first node, wherein the first information is used for indicating an identifier of a first state in the first mapping relationship, and the identifier of the first state is used for indicating an update state of the first capability of the second node. The present application can reduce the communication overheads of capability reporting.

Description

Communication methods, communication devices and communication systems

[0001] This application claims priority to Chinese Patent Application No. 202410572872.9, filed on May 9, 2024, entitled "Communication Method, Communication Apparatus and Communication System", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] Communication nodes possess various capabilities, such as artificial intelligence (AI) capabilities, predictive capabilities, and reasoning capabilities. These communication nodes can report the capabilities they support, and nodes that configure functional policies for these communication nodes can configure control policies for them through the reported capabilities, thereby improving network performance.

[0004] A node that configures a function policy for a communication node can query the capabilities of that communication node. After receiving the query request, the communication node reports the supported capability information. The reported supported capability information includes relatively complete and detailed capability information of the communication node. However, some capabilities do not need to be reported by the communication node, resulting in a large communication overhead for the communication node in capability reporting. Summary of the Invention

[0005] This application provides a communication method, communication device, and communication system that can reduce the communication overhead of capability reporting.

[0006] In a first aspect, a communication method is provided, which can be executed by a second node, or by other devices including the functionality of the second node, or by a chip system (or chip) or other functional module capable of implementing the functionality of the second node, such as being disposed within the second node. The second node is, for example, a terminal device or a device with supporting capabilities.

[0007] The method includes: a second node negotiating a first mapping relationship with a first node, the first mapping relationship indicating the mapping relationship between the state of a first capability of the second node and the identifier of the state; and the second node sending first information to the first node, the first information indicating the identifier of a first state in the first mapping relationship, the identifier of the first state indicating the update state of the second node's first capability.

[0008] For example, the first capability in the second node can be one or more of the second node's AI capabilities, prediction capabilities, reasoning capabilities, etc.

[0009] According to the above scheme, the second node negotiates a first mapping relationship with the first node and sends a first message indicating the identifier of the first state. Upon receiving the first message, the second node can determine the updated state of its first capability indicated by the identifier of the first state through the first mapping relationship, and can update the control policy based on the updated state of the second node's first capability. This enables capability reporting by the second node, reduces the communication overhead of capability reporting, and improves the performance of capability reporting in the second node. Ultimately, this improves network performance.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the capabilities of the second node have at least two levels, the at least two levels including a first level, the capabilities of the first level including a first capability.

[0011] The capabilities of the second node can be divided into different levels, and the identifier of the first state indicated by the first information is the status identifier of the first capability in the first level.

[0012] According to the above scheme, when it is determined that the capability to be reported is the first capability in the first level, the update status of the first capability in the first level can be reported only through the first information, thereby reducing the communication overhead when the second node uploads the capability status.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the first level includes sub-levels, and the capabilities of the first level and the capabilities of the sub-levels of the first level include the first capability.

[0014] The capabilities of the second node can be divided into different levels. When there is a first level, there are corresponding capabilities under the second level. And the sub-levels under the second level also have capabilities under the sub-levels. The identifier of the first state indicated by the first information is the status identifier of the first capability in the first level and the sub-levels of the first level.

[0015] According to the above scheme, when the required reporting capability is uncertain, the capability reporting of the second node can be realized by updating the status of the first capability in the first level and the sub-level of the first level, and the communication overhead when the second node reports the capability status can be reduced.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, sending the first information to the first node includes: the second node sending the first information to the first node when the status reporting conditions are met.

[0017] According to the above scheme, when the status reporting conditions are met, sending the first information indicating the identifier of the first status in the first mapping relationship to the first node can realize the capability reporting of the second node, so that the first node can obtain the status of the capability of the second node in a timely manner and reduce the communication overhead when the second node reports the status of the capability.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the status reporting conditions include at least one of the following: the link status of the second node changes, the second node performs a switching operation, the second node performs a reconstruction operation, the status of the first capability changes, a reporting request is received from the first node, or a mapping relationship update is performed.

[0019] For example, a change in the link state of a second node can mean the second node moves from a non-linked state to a linked state. A handover operation by the second node can mean switching the link between the second node and the first node to a link with other nodes. A rebuild operation by the second node can mean restoring the RRC signaling link to the second node, reducing downtime. A change in the state of a first capability can mean the first capability changes from a supported state to a non-supported state. Receiving a reporting request from the first node means receiving information sent by the first node indicating the status of the reported capability. Performing a mapping update means updating the mapping relationship to a new mapping relationship negotiated between the first and second nodes.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the second node receiving second information from the first node, the second information being used to indicate state reporting conditions.

[0021] The second information can specifically indicate the status reporting conditions of the second node, such as at least one of the following: the second node link status changes, the second node performs a switching operation, the second node performs a reconstruction operation, the status of the first capability changes, receiving a reporting request from the first node, or performing a mapping relationship update.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the second node receiving third information from the first node, the third information being used to indicate the updated status reporting conditions.

[0023] The third information can specifically indicate the updated status reporting conditions, so that when the updated status reporting conditions are met, the second node sends the first information to the first node indicating the identifier of the first status in the first mapping relationship.

[0024] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the second node sending a fourth message to the first node, the fourth message indicating the reason for the change in the update state of the first capability.

[0025] According to the above scheme, the second node sends fourth information to the first node indicating the reason for the change in the update status of the first capability. The first node can then refer to the reason for the change and the update status of the first capability to perform the LCM process, thereby improving network performance.

[0026] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the second node renegotiating the mapping relationship with the first node.

[0027] For example, the second node sends first information indicating the identifier of the first state in the first mapping relationship to report its capabilities to the first node. It can also update the mapping relationship and renegotiate it. This renegotiated mapping relationship can be a mapping between the state of the first capability and its identifier, where the identifier corresponding to the state of the first capability in the renegotiated mapping relationship differs from the identifier corresponding to the state of the first capability in the first mapping relationship. Alternatively, the renegotiated mapping relationship can be a mapping between the state of other capabilities of the second node and their identifiers. In this way, the second node can send information indicating the state identifier of the renegotiated mapping relationship to the first node, thus completing the capability reporting from the second node to the first node.

[0028] In conjunction with the first aspect, in some implementations of the first aspect, the second node renegotiates the mapping relationship with the first node, including: the second node and the first node renegotiating the mapping relationship between the state of the second capability and the identifier of the state.

[0029] According to the above scheme, the second node negotiates a mapping relationship between the state of the second capability and its identifier with the first node. This new mapping relationship allows the second node to report the state of other capabilities of interest to the first node. This enables the reporting of capabilities within the second node, and the first node can update its control policy based on the updated state of the second node's first capabilities. This improves network performance.

[0030] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the second node switching its link with the first node to a link with the third node. The second node sends fifth information to the third node, the fifth information being used to indicate an identifier of a second state, the identifier of the second state being used to indicate the update status of the second node's capabilities, and there is a mapping relationship between the identifier of the second state and the update status of the second node's capabilities.

[0031] For example, when a second node switches to a link with a third node, and the third node manages the capabilities of the second node or performs LCM (Capability Management), the mapping relationship between the identifier of the second state and the updated capability state of the second node can be a mapping relationship negotiated between the second node and the first node. The second node continues this mapping relationship when reporting capabilities to the third node. Alternatively, the mapping relationship between the identifier of the second state and the updated capability state of the second node can also be a mapping relationship renegotiated between the third node and the second node.

[0032] The mapping relationship between the identifier of the second state and the updated state of the capabilities of the second node is a mapping relationship negotiated between the second node and the first node, or it can be a mapping relationship negotiated between the second node and the first node by the first node sending information to the third node.

[0033] According to the above scheme, the second node switches to link with the third node. The second node sends a fifth information indicator to the third node, indicating the identifier of the second state. This identifier indicates the updated status of the second node's capabilities, enabling the reporting of the second node's capabilities. A mapping relationship exists between this identifier and the updated status of the second node's capabilities. This mapping relationship can be indicated by the first node or negotiated between the second and third nodes to achieve capability reporting of the second node. The third node can perform LCM (Limited Communication Management) based on the updated status of the second node's capabilities. This enables capability reporting by the second node, reduces the communication overhead of capability reporting, and improves the performance of capability reporting in the second node. Ultimately, this improves network performance.

[0034] Secondly, a communication method is provided, which can be executed by a first node, or by other devices including the functions of the first node, or by a chip system (or chip) or other functional module capable of implementing the functions of the first node, such as being disposed in the first node. The first node is, for example, an access network device, or a CU, or a CU-CP, or a CU-CP2, or a gNB, or an O-CU-CP, etc.

[0035] The method includes a first node negotiating a second mapping relationship with a second node, the first mapping relationship indicating a mapping between the state of a first capability of the second node and an identifier of that state. The first node receives first information from the second node, the first information indicating an identifier of a first state in the first mapping relationship, the identifier of which indicates an update state of the first capability.

[0036] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: performing lifecycle management on the second node based on the update status of the first capability.

[0037] According to this scheme, the first node receives a first information indicator from the second node, which indicates the identifier of a first state in a first mapping relationship. This identifier of the first state is used to indicate the update status of a first capability. The first node obtains the update status of the first capability in the second node and performs LCM on the second node based on this update status, thereby improving network performance.

[0038] In conjunction with the second aspect, in some implementations of the second aspect, the capabilities of the second node have at least two levels, including a first level, the capabilities of which include a first capability.

[0039] In conjunction with the second aspect, in some implementations of the second aspect, the first level includes sub-levels, and the capabilities of the first level and the capabilities of the sub-levels of the first level include the first capability.

[0040] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: the first node sending second information to the second node, the second information being used to indicate the status reporting conditions for the second node to send the first information.

[0041] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: renegotiating the mapping relationship between the first node and the second node.

[0042] In conjunction with the second aspect, in some implementations of the second aspect, the renegotiation of the mapping relationship with the second node includes: the first node and the second node negotiating the mapping relationship between the state of the second capability and the identifier of the state.

[0043] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: when the first node switches to a link with the third node, the first node sends a sixth message to the third node, the sixth message being used to indicate the first mapping relationship.

[0044] For example, when the second node switches to link with the third node, the first node sends a sixth message to the third node indicating the first mapping relationship. Capability reporting between the second node and the third node can be implemented based on the first mapping relationship. For example, the second node sends a message to the third node indicating the identifier of the status of the first mapping relationship. The identifier of the status of the first mapping relationship is used to indicate the update status of the first capability in the second node.

[0045] According to this scheme, the first node sends the sixth information to the third node to indicate the first mapping relationship. The second and third nodes report capabilities based on the first mapping relationship, which can reduce the process of negotiating the mapping relationship between the second and third nodes and reduce the capability reporting time.

[0046] Thirdly, a communication method is provided, which can be executed by a third node, or by other devices including the functions of a third node, or by a chip system (or chip) or other functional module capable of implementing the functions of the third node, such as being disposed in the third node. The third node is, for example, an access network device, or a CU, or a CU-CP, or a CU-CP2, or a gNB, or an O-CU-CP, etc.

[0047] The method includes: a third node receiving fifth information from a second node, the fifth information being used to indicate an identifier of a second state, the identifier of the second state being used to indicate an update state of the capabilities of the second node, and a mapping relationship existing between the identifier of the second state and the update state of the capabilities of the second node.

[0048] The description of the mapping relationship between the identifier of the second state and the updated state of the capabilities of the second node is the same as that in the first aspect, and will not be repeated here.

[0049] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the third node performing lifecycle management on the second node based on the updated state of the second node's capabilities.

[0050] Fourthly, a communication method is provided, which can be executed by a third node, or by other devices including the functions of a third node, or by a chip system (or chip) or other functional module capable of implementing the functions of the third node, such as being disposed within the third node. The third node is, for example, an access network device, or a CU, or a CU-CP, or a CU-CP2, or a gNB, or an O-CU-CP, etc.

[0051] The method includes: a third node receiving sixth information from a first node, the sixth information indicating a first mapping relationship, the first mapping relationship indicating a mapping relationship between the state of a first capability of a second node and an identifier of that state; and the third node receiving seventh information from the second node, the seventh information indicating an identifier of a third state of the first mapping relationship, the identifier of the third state indicating an update state of the first capability.

[0052] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: the third node performing lifecycle management on the second node based on the update status of the first capability.

[0053] Fifthly, a communication device is provided. In one design, the device may include modules corresponding to the methods / operations / steps / actions described in the first aspect or any embodiment of the first aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software. In one design, the device includes: a processing unit for negotiating a first mapping relationship with a first node, the first mapping relationship indicating a mapping relationship between the state and an identifier of a first capability of a second node; and a transceiver unit for sending first information to the first node, the first information indicating an identifier of a first state in the first mapping relationship, the identifier of the first state indicating an update state of the first capability of the second node.

[0054] In a sixth aspect, a communication device is provided. In one design, the device may include modules corresponding to the methods / operations / steps / actions described in the second aspect or any embodiment of the second aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software. In one design, the device includes: a processing unit for negotiating a second mapping relationship with a second node, the first mapping relationship indicating a mapping relationship between the state of a first capability of the second node and an identifier of that state; and a transceiver unit for receiving first information from the second node, the first information indicating an identifier of a first state in the first mapping relationship, the identifier of the first state indicating an update state of the first capability.

[0055] In a seventh aspect, a communication device is provided. In one design, the device may include modules corresponding to the methods / operations / steps / actions described in the third aspect or any of the embodiments within the third aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software. In one design, the device includes a transceiver unit for receiving fifth information from a second node. This fifth information is used to indicate an identifier of a second state, which in turn indicates an update state of the second node's capabilities. A mapping relationship exists between the identifier of the second state and the update state of the second node's capabilities.

[0056] Eighthly, a communication device is provided. In one design, the device may include modules corresponding to the methods / operations / steps / actions described in the fourth aspect or any of the embodiments of the fourth aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software. In one design, the device includes: a first transceiver unit for receiving sixth information from a first node, the sixth information indicating a first mapping relationship, the first mapping relationship indicating a mapping relationship between the state of a first capability of a second node and an identifier of that state; and a second transceiver unit for receiving seventh information from the second node, the seventh information indicating an identifier of a third state of the first mapping relationship, the identifier of the third state indicating an update state of the first capability.

[0057] A ninth aspect provides a communication device, comprising a processor. The processor can implement the methods of the first to fourth aspects and any possible implementations thereof. Optionally, the communication device further includes a memory, and the processor is coupled to the memory and can be used to execute instructions in the memory to implement the methods of the first to fourth aspects and any possible implementations thereof. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface. In the embodiments of this application, the communication interface may be a transceiver, a pin, a circuit, a bus, a module, or other type of communication interface, and is not limited thereto.

[0058] In one implementation, the communication device is a communication equipment (such as a terminal device or a network device). When the communication device is a communication equipment, the communication interface can be a transceiver, or an input / output interface.

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

[0060] Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0061] A tenth aspect provides a processor, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the methods of any possible implementation of the first to fourth aspects and the first to sixth aspects described above.

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

[0063] Eleventhly, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods described in the first to fourth aspects and any possible implementation thereof.

[0064] In a twelfth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform the methods described in the first to fourth aspects and any possible implementation thereof.

[0065] In a thirteenth aspect, a communication system is provided, including at least one terminal device and at least one network device as described above. Attached Figure Description

[0066] Figure 1 is a schematic block diagram of a communication system provided in an embodiment of this application;

[0067] Figure 2 is a schematic block diagram of the network architecture provided in an embodiment of this application;

[0068] Figure 3 is a schematic block diagram of the network architecture of the development access network provided in an embodiment of this application;

[0069] Figure 4 is a schematic block diagram illustrating the application of AI in NR according to an embodiment of this application;

[0070] Figure 5 is a schematic diagram of a communication method provided in an embodiment of this application;

[0071] Figure 6 is another schematic diagram of the communication method provided in an embodiment of this application;

[0072] Figure 7 is another schematic diagram of the communication method provided in an embodiment of this application;

[0073] Figure 8 is a schematic block diagram of an example of the communication device of this application;

[0074] Figure 9 is a schematic structural diagram of an example of the second node of this application;

[0075] Figure 10 is a schematic structural diagram of an example of the first node of this application. Detailed Implementation

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

[0077] In this application embodiment, " / " can indicate that the related objects are in an "or" relationship. For example, A / B can represent A or B. "And / or" can be used to describe three relationships between related objects. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. A and B can be singular or plural. To facilitate the description of the technical solutions in this application embodiment, the terms "first" and "second" can be used for distinction. These terms do not limit the quantity or execution order, and they are not necessarily different. In this application embodiment, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary" or "for example" should not be construed as being more preferred or advantageous than other embodiments or designs. The use of "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding. In the embodiments of this application, at least one can also be described as one or more species, and more than one species can be two, three, four or more species, and this application does not impose any restrictions.

[0078] The technical solutions of this application can be applied to various communication systems, such as Long Term Evolution (LTE) systems, 5th generation (5G) communication systems, Wireless Fidelity (WiFi) systems, and the communication methods provided in this application can also be applied to 6th generation (6G) communication systems and other communication systems evolving after 5G, future communication systems, or other communication systems. This application does not limit these applications.

[0079] Figure 1 is a schematic diagram of a communication system 100 applicable to an embodiment of this application.

[0080] As shown in Figure 1, the communication system 100 may include at least one first node 110, at least one second node 120, and at least one third node 130.

[0081] First node 110 and second node 120 are linked, and first node 110 and second node 120 can communicate or transmit data. Second node 120 supports capabilities, which can be one or more of the following: AI capabilities, prediction capabilities, reasoning capabilities, etc. Second node 120 can report the status of its capabilities to first node 110. First node 110 can perform LCM (Lifecycle Management) based on the status of the capabilities reported by second node 120 to improve the performance of the communication system and network performance.

[0082] The second node 120 can switch to link with the third node 130. At this time, the second node 120 and the third node 130 can communicate or transmit data. The second node 120 can report its supported capabilities to the third node 130. The third node 130 can perform LCM (Lifecycle Management) based on the status of the capabilities reported by the second node 120 to improve the performance of the communication system and the network.

[0083] The second node 120 can be a supporting device, which can be a wireless terminal or a wired terminal. The wireless terminal can be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN). The wireless terminal can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device. These exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). A wireless terminal can also be referred to as a system, subscriber unit (SU), subscriber station (SS), mobile station (MB), mobile, remote station (RS), access point (AP), remote terminal (RT), access terminal (AT), user terminal (UT), user agent (UA), user device (UD), or user equipment (UE).

[0084] It should be understood that this application does not limit the specific form of the device of the second node 120.

[0085] The first node 110 and the third node 130 can be network devices, specifically devices capable of receiving reports from the second node 120 for LCM (Local Communication Management). In this embodiment, the network device can be a device with wireless transceiver functionality in the access network. This device includes, but is not limited to: base stations, evolved node B (eNB), radio network controllers (RNC), node B (NB), base station controllers (BSC), base transceiver stations (BTS), home base stations (e.g., home evolved node B, or home node B, HNB), baseband units (BBU), access points (APs), wireless relay nodes, wireless backhaul nodes, transmission points (TPs), or transmission and reception points (TRPs) in a Wi-Fi system. This network device can also serve as a network node constituting a Next Generation Network Baseline (gNB) or transmission point, such as a Baseband Unit (BBU) or a Distributed Unit (DU). It can also be a Centralized Unit Control Plane (CU-CP), CU-CP1, and CU-CP2. Furthermore, it can be a network node in an Open Access Network, such as an Open Access Network Centralized Unit Control Plane (O-CU-CP).

[0086] In some deployments, Figure 2 illustrates a network architecture where, in the radio access network (RAN), a gNB may include a centralized unit (CU) and a DU. The RAN may be connected to the core network (e.g., a long-term evolution (LTE) core network). The CU and DU can be understood as a logical functional division of the gNB. Physically, the CU and DU can be separate or deployed together; multiple DUs can share a single CU, and a single DU can connect to multiple CUs. CUs and DUs can be connected via interfaces, such as F1 interfaces. The division of CUs and DUs can be based on the protocol layer of the wireless network.

[0087] The gNB can also include an active antenna unit (AAU). The CU and DU implement some of the gNB's functions. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), media access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered as being sent by the DU, or by the DU+AAU. It is understandable that network devices can be devices that include one or more of the following: CU nodes, DU nodes, and AAU nodes. In addition, the CU can be classified as a network device in the RAN or as a network device in the core network (CN), and this application does not limit this.

[0088] Understandably, the above division of CU and DU processing functions according to this protocol layer is merely an example, and other methods can also be used. For instance, CUs or DUs can be divided into those with more protocol layer functions. Alternatively, CUs or DUs can be divided into those with partial protocol layer processing functions. In one design, some functions of the RLC layer and the protocol layer functions above the RLC layer are placed in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer are placed in the DU. In another design, the functions of CUs or DUs can be divided according to service type or other system requirements, such as by latency. Functions that need to meet latency requirements are placed in the DU, while functions that do not need to meet this latency requirement are placed in the CU. In yet another design, a CU can also have one or more core network functions. One or more CUs can be centrally or separately configured; for example, a CU can be placed on the network side for convenient centralized management. A DU can have multiple radio frequency functions, or the radio frequency functions can be remotely configured.

[0089] In some deployments, the functions of the CU can be implemented by a single entity or by different entities. The CU's functions can be further divided, for example, separating the control plane (CP) and user plane (UP), i.e., the CU's control plane (CU-CP) and user plane (CU-UP). For instance, CU-CP and CU-UP can be implemented by different functional entities and connected via an E1 interface. CU-CP and CU-UP can be coupled with the DU to jointly complete the base station's functions. The CU's control plane, CU-CP, also includes a further divided architecture, namely, further dividing the existing CU-CP into CU-CP1 and CU-CP2. CU-CP1 includes various radio resource management functions, while CU-CP2 only includes RRC functions and PDCP-C functions (i.e., the basic functions of control plane signaling at the PDCP layer).

[0090] In some deployments, Figure 3 shows a schematic block diagram of the open access network architecture. The Radio Intelligent Controller (RIC) achieves intelligent and automated RAN operation and maintenance by introducing the capabilities of connected second nodes. Non-real-time RICs typically handle services with long latency requirements, such as big data analysis and AI model training; real-time RICs typically handle services with short latency requirements, such as traditional RAN-side services like radio resource management and handover. O-CU-CP and O-CU-UP correspond to CU-CP and CU-UP in 5G networks, respectively, and O-DU corresponds to DU in 5G networks. O-RU corresponds to radio frequency functions and communicates with the UE through the O-RU.

[0091] A network device manages one or more cells and provides services to the managed cells. Terminal devices communicate with the network device within a cell using transmission resources (e.g., frequency domain resources, or spectrum resources) allocated by the network device. This cell can belong to a macro base station (e.g., a macro eNB or macro gNB) or to a base station corresponding to a small cell. Small cells can include metro cells, micro cells, pico cells, femto cells, etc. These small cells are characterized by small coverage areas and low transmission power, making them suitable for providing high-speed data transmission services.

[0092] In this embodiment, the device for implementing the function of the second node 120 can be a terminal device; it can also be a device capable of supporting the terminal device in implementing this function, such as a chip system. This device can be installed in the terminal device or used in conjunction with the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. In this embodiment, taking the terminal device as an example to illustrate the provided technical solution, we will describe it as such.

[0093] In this embodiment, the apparatus for implementing the functions of the first node 110 and the third node 130 can be a network device; it can also be an apparatus capable of supporting the network device in implementing the functions, such as a chip system. This apparatus can be installed in the network device or used in conjunction with the network device. In this embodiment, taking a network device as an example to illustrate the provided technical solution, we will describe it as such.

[0094] The following are definitions of technical terms that may appear in the embodiments of this application. The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application.

[0095] (1) Capabilities of the second node

[0096] In this embodiment of the application, the function of the second node 120 can be one or more of the following: AI capability, prediction capability, reasoning capability, etc.

[0097] (2) AI capabilities

[0098] The 3rd generation partnership project (3GPP) proposes that AI can be applied to new radio (NR) systems to improve network performance and user experience through intelligent data collection and analysis.

[0099] AI can reside within Operations, Administration and Maintenance (OAM), or in first or third nodes (such as gNB, CU, etc.), or in some second nodes (such as UE, etc.), or it can stand alone as a network element entity (AIC). The main function of AI in a communication system is to perform a series of AI calculations, such as model building, training approximation, and reinforcement learning, based on input data (in wireless communication systems, input data generally refers to network operation data provided by the RAN side or monitored by OAM, such as network load, channel quality, etc.).

[0100] Taking a network device in the access network as an example, the pre-trained AI model provided by the AI ​​module has the ability to predict changes in the RAN-side network, and can typically be used for load prediction, UE path prediction, etc. Furthermore, the AI ​​module can also perform policy reasoning from the perspectives of network energy saving and mobility optimization based on the predicted performance of the RAN network using the trained model, to obtain reasonable and efficient energy-saving strategies and mobility optimization strategies. When the AI ​​module is located in the OAM, its communication with the RAN-side gNB can reuse the current northbound interface; when the AI ​​module is located in the gNB or CU, it can reuse the current F1, Xn, Uu, etc. interfaces; when the AI ​​module is an independent network entity, a new communication link needs to be established to the OAM and RAN sides, such as based on a wired link or a wireless link. When the CP and UP of the CU are separated, the CP is usually responsible for receiving the AI ​​model and subsequent AI inference and policy generation functions. When CU-CP is further divided into CU-CP1 and CU-CP2, CU-CP1 is usually responsible for receiving the model and subsequent AI inference functions, and generating specific interaction signaling, which is then sent by CU-CP2.

[0101] Figure 4 illustrates a schematic diagram of AI application in NR. In Figure 4, the Data Source stores data inputs from various nodes, including the first or third node and the second node (such as gNB, CU, DU, etc.), as well as data inputs from UEs or other management entities, serving as a database for AI model training and data analysis inference. The Model Training Host analyzes the training data provided by the Data Source to provide the optimal AI model. This AI model is then deployed / updated to the Model Inference Host. Based on the inference data provided by the Data Source, the AI ​​model provides reasonable AI-based predictions for network operation, yielding outputs, or guiding network policy adjustments. These policy adjustments and outputs are uniformly planned by the Actor entities and sent to multiple network entities for execution. Simultaneously, the network's performance after applying relevant policies is fed back into the Data Source for storage. The AI ​​model's output can also serve as Model Performance Feedback to the Model Training Host for further AI model training.

[0102] 1. AI-based use cases

[0103] Currently, 3GPP has designed several basic application scenarios for AI on the RAN side through working groups such as RAN3 and RAN1. RAN3 includes energy saving, load balancing, and mobility optimization, while RAN1 includes enhanced Channel State Information Reference Signal (CSI-RS) feedback, enhanced beam scanning, and enhanced positioning. The following uses the base station as the first node and the UE as the second node as an example to briefly introduce the basic principles of several use cases.

[0104] Energy Saving: By collecting load, energy consumption, and energy efficiency information from the base station and neighboring cells, as well as UE path information and measurement results, the base station predicts its own load trends. Combined with cell usage and KPI requirements, energy-saving measures are implemented in a timely and appropriate manner without affecting network coverage or user access. The simplest energy-saving strategy includes directly deactivating the cell. Other strategies include carrier shutdown, channel shutdown, time slot shutdown, and reduced transmit power. More complex strategies involve combining these measures. When network coverage is affected or cannot meet UE access and service requirements, the current energy-saving strategy needs to be modified, or the system should be restored to normal operation. In such cases, load re-prediction or a change in the AI ​​model used for re-inference should be considered.

[0105] Load Balancing: By collecting load, energy consumption, and energy efficiency information from its own and neighboring cells, as well as UE path information and measurement results, base stations predict their own load trends. Combined with cell usage and KPI requirements, it rationally selects some UEs to hand over to neighboring cells or to receive UEs from neighboring cells, ensuring that the load levels among base stations across the entire network are similar, reducing situations where some base stations are overloaded and affecting normal services while others are idle. However, because the accuracy of prediction is not 100%, it can lead to unreasonable UE selection or handover target cells, resulting in handover failures or impact on UE services. Inaccurate load prediction can also lead to poor load balancing, or temporary abnormal load changes can render the original load balancing strategy inapplicable. In such cases, it is necessary to exit or modify the current load balancing strategy and consider re-predicting the load or changing the AI ​​model used for re-inference.

[0106] Mobility Optimization: By collecting historical path information of the UE from the base station and combining it with the UE's measurement information, the future path of the UE is predicted. Based on the predicted path, it is determined in advance whether the UE needs to handover, and the handover configuration is issued in advance, and the target cell is notified to prepare access resources, reducing the latency of the UE during the handover process and reducing the probability of handover and access failure. However, since the accuracy of path prediction is not 100%, when the predicted path is incorrect, it will lead to UE handover failure and service interruption. In this case, it is necessary to consider retraining the model and inference based on the abnormal situation, or to consider replacing the model to avoid similar abnormal situations from occurring again in the future. In Release 19, RAN2 has re-planned a new mobility optimization topic and set several use cases as research objectives. One key case is to predict the UE's measurement results, such as predicting the Reference Signal Receiving Power (RSRP) measurement results of the Synchronization Signal / Physical Broadcast Channel Block (SSB). The granularity of prediction can be cell-level or beam-level, and can be prediction based on the cell where the UE is located or prediction based on neighboring cells. In addition, two new case studies have been introduced. One is predicting the occurrence of abnormal events such as HOF / RLF (Handover Failure / Radio Link Failure), and the other is predicting measurement events such as A1 to A5. The current research direction for the latter two case studies in the standard is to consider the UE-side model, that is, the UE side reports the prediction results to the NW side (network side), and then the NW side decides what adjustments need to be made based on the prediction results.

[0107] CSI-RS Feedback Enhancement: The main process of current CSI-RS feedback enhancement is as follows:

[0108] A1. The base station and the UE first exchange a dictionary. Usually, the base station pre-trains a model based on the UE's capabilities and its own requirements, and then sends an encoder and quantizer tool to the UE.

[0109] A2. Based on the measured channel matrix results, the UE compresses and quantizes the matrix to be fed back according to the existing dictionary, and transmits the result B to the base station side;

[0110] A3. The base station recovers the original channel matrix by reverse engineering based on the dictionary and the data reported by the UE.

[0111] Beam Management Enhancement: The main process for current beam management enhancement is as follows:

[0112] B1. Generation of the initial model. By having a certain number of UEs report the results of SSB full-beam scanning, a sparse scanning matrix is ​​trained. This matrix is ​​usually unique to each cell.

[0113] B2. The base station sends the sparse model to the UE (which can be done via SIB (System Information Block) messages, etc.), and the UE performs beam scanning in the P1 stage based on this matrix;

[0114] B3. Based on the sparse scan results of the UE, the base station infers the optimal CSI-RS beam and starts P2 scanning of the UE. The UE then feeds back the optimal CSI-RS beam ID.

[0115] Positioning Accuracy Enhancements: The main process for enhancing positioning accuracy is as follows:

[0116] C1. Collect raw data using a positioning reference unit controlled by the operator;

[0117] C2.LMF (Location Management Node, non-RAN side node) and gNB train models respectively. The LMF model can infer the final positioning (latitude and longitude, etc.), and the gNB model can infer the LOS / NLOS (line-of-sight / non-line-of-sight), ToA, and time of arrival (reference signal arrival time) judgment results.

[0118] 2. Levels of AI capabilities

[0119] Specific AI capability information can be divided into multiple levels. For example, in some embodiments, it may include levels such as functionality, model, dataset, use case, and sub-use case.

[0120] The following provides an example illustrating the AI ​​capabilities in the second node.

[0121] In some embodiments, AI capabilities may include information from any of the following levels:

[0122] Level 1: Does the UE have AI capabilities?

[0123] Level 2 includes, for example, whether the UE supports AI-based CSI-RS enhancements, beam management enhancements, positioning enhancements, mobility enhancements, and whether the UE supports specific use cases.

[0124] Level 3 includes features such as whether CSI prediction, CSI compression, optimal transmit / receive top-1 / top-k beam ID / RSRP / angle prediction, direct positioning result prediction, assisted positioning prediction, cell-level reference signal L1 prediction result, cell-level reference signal L3 prediction result, beam-level reference signal L1 prediction result, beam-level reference signal L3 prediction result, HOF / RLF event prediction, measurement event prediction, path prediction, optimal handover timing / target cell prediction, and whether the UE supports specific use cases.

[0125] Level 4: Specific AI model input / output parameter formats. These can be specific input / output formats for any one or more of the above-mentioned UE capabilities. Examples include the number of historical CSI measurement results supported for CSI prediction, the time window length for predicting future CSI measurement results, the compression ratio supported for CSI compression, the k-value of the predictable optimal top-k transmit / receive beams, the accuracy of RSRP and angle, the number of supported input / output beams, the accuracy of direct positioning result prediction, the required number of historical PRS measurement results, and the input result type (e.g., Channel Impulse Response (CIR) / Power Delay Distribution). Profile (PDP), etc., assisted positioning prediction accuracy, number of required historical PRS measurement results, output result type (ToA, LOS / NLOS indicator), cell-level reference signal L1 prediction result, cell-level reference signal L3 prediction result, beam-level reference signal L1 prediction result, beam-level reference signal L3 prediction result, number of required historical measurement results, observation window length, number of predictable cells / beams / accuracy, prediction window length, number of historical measurement results required for HOF / RLF event and measurement event prediction, observation window / prediction window length, prediction accuracy value (interval), path prediction / optimal handover timing / optimal target cell observation window / prediction window length, prediction accuracy value (interval), etc.

[0126] Level 5 refers to the model ID, dataset ID, etc. of the AI ​​model supported by a certain AI capability under any of the levels from Level 1 to Level 4 mentioned above.

[0127] It is understandable that the hierarchy can be divided according to certain logic or function. The hierarchy proposed above is an example, and there can be other hierarchical divisions, which are not limited here.

[0128] (3) Capability reporting:

[0129] The second node 120 can report its capabilities to the first node 110 or the third node 130. Taking the second node as the UE and the first node as the gNB as an example, the gNB requests the UE capabilities of interest to the UE from the UE through a network-side query for terminal network supported capabilities (UE Capability Enquiry). The UE reports its actual capabilities to the gNB through UE Capability Information, or indicates its capabilities through UE Assistance Information (UAI). Subsequently, the gNB can perform relevant configurations for the UE based on its capabilities.

[0130] Taking the UE as the second node and the LMF (Location Management Function) as the first node as an example, the LMF requests the UE capabilities it is interested in from the UE through an LTE Positioning Protocol (LPP) message. The UE then reports its actual capabilities to the gNB via the LPP message. Subsequently, the LMF can configure the UE accordingly based on these capabilities.

[0131] This UE capability information can only be sent from the UE to the NW side based on a request from the NW side. As mentioned above, when the NW side is the gNB, the UE sends the capability information to the gNB based on the gNB's request. When the NW side is the LMF, the UE sends the capability information to the LMF based on the LMF's request.

[0132] It is understood that the UE Capability Enquiry information and LPP information mentioned above are exemplary, and other information may also be used, which is not limiting here.

[0133] Capability reporting can be divided into proactive reporting and reactive reporting. Proactive reporting can occur before the first node requests LCM adjustments from the second node, when the second node proactively reports the capabilities it currently supports via UAI / LPP, or the first node configures the second node to report the capabilities it currently supports via UAI / LPP (e.g., reporting periodically, or reporting when the capabilities supported by the second node change). Reactive reporting can occur after the first node requests LCM adjustments from the second node and before confirming the method of LCM adjustment. That is, after requesting the UE to configure and execute AI-related functions, the first node needs to understand the capabilities supported by the second node to confirm the specific strategy for configuring AI-related functions, and thus instructs the second node to report the capabilities it currently supports via UAI / LPP.

[0134] The following is an analysis of capability reporting.

[0135] Taking a device on the NW side (such as a gNB or LMF) as the first node and a UE as the second node as an example, the UE reports its initial capabilities based on UE Capability Information / LPP signaling. Subsequently, when the NW side needs to configure the UE to perform related functions, the UE reports its currently supported capabilities. This can be considered a Reactive reporting mode. However, when the actual capabilities supported by the UE change due to variations in the UE's local computing power, available storage resources, and power consumption, the NW side cannot know this in advance. This may result in the UE being unable to execute the configured functions, requiring the NW side to wait for the UE to actively report updated supported capabilities before reconfiguring, increasing the overall configuration time and communication overhead.

[0136] When the UE's capabilities change, it can proactively report the changes or report them in advance based on the NW's configuration before the NW needs to adjust the LCM strategy. This can be considered a proactive reporting mode. However, if the UE proactively reports relatively complete or detailed capability information every time, the NW will receive a lot of redundant information. Some of the changed capabilities may not need to be provided by the UE, which will increase communication overhead.

[0137] To address the aforementioned issues, this application proposes a mapping relationship negotiated between the UE and the NW. Specifically, the first node can negotiate a mapping relationship with the second node, which is a mapping between the identifiers of capabilities supported by the second node and their status identifiers. In this way, the second node can send information indicating the status identifier, and the first node can determine the capability corresponding to the status identifier through the mapping relationship, reducing the overhead of capability reporting. The first node can obtain the status of the second node's capabilities and perform LCM accordingly, thereby improving communication performance. Furthermore, this capability can be the capability required for the first node to perform LCM, and the second node can, when reporting capabilities, only send the status identifier of the capability required for the first node to perform LCM, further reducing communication overhead.

[0138] Figure 5 is a schematic diagram of a communication method provided in an embodiment of this application. The method 500 includes, but is not limited to, the following steps S510 and S550.

[0139] S510, the second node negotiates a first mapping relationship with the first node, which is used to indicate the mapping relationship between the status of the first capability supported by the second node and the identifier of the status.

[0140] The second node negotiates the first mapping relationship with the first node. This can be done by the second node sending a message to the first node to indicate the first mapping relationship, or by the first node sending a message to the second node to indicate the second mapping relationship.

[0141] Accordingly, the information indicating the first mapping relationship issued by the second node or the first node can be the information of the first mapping relationship itself, or it can be the information that carries the first mapping relationship in a certain field of the information, or the first node stores multiple mapping relationships, and the information indicating the first mapping relationship issued by the second node is the information to determine a specific mapping relationship among the multiple mapping relationships as the first mapping relationship. Alternatively, the second node stores multiple mapping relationships, and the information indicating the first mapping relationship issued by the first node is the information to determine a specific mapping relationship among the multiple mapping relationships as the first mapping relationship, but this application is not limited to these possibilities.

[0142] The second node negotiates with the first node a first mapping relationship indicating the mapping relationship between the state of the first capability and the identifier of the state, wherein the first capability can be the first capability indicated by the first node, or it can be the first capability selected and determined by the second node itself.

[0143] Optionally, the second node negotiates a first mapping relationship with the first node. The first node can obtain the capabilities supported by the second node. Based on the capabilities supported by the first node, a first capability can be determined. The first capability can be the capability required by the first node to perform LCM on the second node.

[0144] For example, the first node can send UE Capability Enquiry information to the second node, which can instruct the second node to report its own capability information. After receiving the instruction, the second node reports its own capability information, and the first node can then indicate its first capability to the second node through the capability information reported by the second node.

[0145] For example, if the first node stores information about the capabilities supported by the second node, it can directly indicate the first capability to the second node.

[0146] Optionally, the second node can also directly designate the first capability. For example, if the second node determines that the state of other capabilities will not change within a certain period of time, it can choose the capability that will change as the first capability. Alternatively, the second node can also instruct the first node to suggest which capabilities / which level of capabilities / which level and its sub-levels of capabilities to select as the first capability. Accordingly, the first node determines the first capability based on the instruction.

[0147] Optionally, the capabilities of the second node have at least two levels. The first node can also send information to the second node instructing the second node to report the level of the capabilities it supports. Accordingly, after receiving the instruction from the first node, the second node reports the level of the capabilities to the first node. If the first node knows the level of the capabilities required by the LCM, it can determine the first level based on the level of the capabilities. The first node indicates the first level to the second node. The capabilities of the first level include the first capability. Thus, the second node can only report the capabilities under the indicated first level.

[0148] The hierarchy of capabilities in the second node can be obtained by pre-configuring the first node, or the second node can be instructed by the first node to perform hierarchical division of the energy levels in the first node.

[0149] For example, the beam management case (hereinafter referred to as BM case) in the second node has three levels: the first level is the BM case capability; the second level is the temporal prediction capability and the spatial prediction capability under the BM case; and the third level is the 4-beam to 8-beam prediction under the temporal domain, the 4-beam to 16-beam prediction under the temporal domain, the 4-beam to 8-beam prediction under the spatial domain, and the 4-beam to 16-beam prediction under the spatial domain. The second node can indicate the third level of the BM case, and the capability under the third level is the 4-beam to 8-beam prediction under the temporal domain, the 4-beam to 16-beam prediction under the temporal domain, the 4-beam to 8-beam prediction under the temporal domain, and the 4-beam to 16-beam prediction under the spatial domain. The capability under the third level can include the first capability, and correspondingly, the first capability is the capability under the third level of the BM case.

[0150] The first capability can be in two states: supported and unsupported. Different states of the first capability can correspond to different state identifiers.

[0151] Optionally, the mapping between the state of the first capability and the identifier of the state can be implemented in any way, provided that in the first mapping relationship, each identifier of a state corresponds to a unique state of the first capability.

[0152] Optionally, a mapping between the state of a first capability and the identifier of that state can be achieved through a bitmap mapping, where one capability corresponds to one bit, and different values ​​in that bit correspond to different states of that capability.

[0153] For example, the first capability is the capability under the third level of the BM case. The third level of the BM case includes four capabilities, and each capability corresponds to one bit. Four bits can be used to represent the status of the four capabilities under the third level of the BM case. For example, a bit value of 0 indicates a non-supported state, and a value of 1 indicates a supported state. The bits of these four capabilities can be arranged in a certain order. For example, the first bit corresponds to the 4-beam (beam) prediction and 8-beam prediction in the time domain under the BM case; the second bit corresponds to the 4-beam prediction and 16-beam prediction in the time domain under the BM case; the third bit corresponds to the 4-beam prediction and 8-beam prediction in the spatial domain under the BM case; and the fourth bit corresponds to the 4-beam prediction and 16-beam prediction in the spatial domain under the BM case. The status identifier is 0000. In the first mapping relationship, the status of the first capability is that all four capabilities of the second node are in a non-supported state. The status identifier is 0001. In the first mapping relationship, the status of the first capability is that the BM... In the case of spatial domain prediction, the ability to predict 16 beams from 4 beams is a support state. The identification of other states and the mapping relationship of the first state are similar, and will not be repeated here.

[0154] For example, if the first capability is a capability at the second level of the BM case, and this second level includes two capabilities, then the status identifier of this first capability has two bits. A status identifier of 00 indicates that the status of both the temporal prediction capability and the spatial prediction capability under the BM case in the first mapping relationship is not supported. A status identifier of 01 indicates that the status of the temporal prediction capability under the BM case in the first mapping relationship is not supported, and the status of the spatial prediction capability under the BM case is supported. The identifiers of other states and the mapping relationships of the first capability states are similar and will not be elaborated here.

[0155] For example, regarding mobility enhancement-related capabilities, the capabilities of this second node under mobility enhancement-related capabilities are as follows: the required observation window length for beam-level reference signal L1 prediction results is 10 seconds; the required observation window length for beam-level reference signal L1 prediction results is 5 seconds; the required inference window for beam-level reference signal L1 prediction results is 2 seconds; the required inference window for beam-level reference signal L1 prediction results is 1 second; the maximum number of predictable beams is 4; and the maximum number of predictable beams is 2. Under the mobility enhancement level, there are a total of 6 capabilities, which can be represented by 6 bits. According to the order of the capabilities described above, the state identifier is 101010. The state of the first capability corresponding to the first mapping relationship is the state of the capability with the required observation window length for beam-level reference signal L1 prediction of 10 seconds, the capability with the required inference window for beam-level reference signal L1 prediction of 2 seconds, and the capability with the maximum number of predictable beams of 4. The state of the other 3 capabilities is the state of not supporting them.

[0156] Optionally, the mapping between the state of the first capability and the identifier of the state can be achieved through bitmap mapping. A capability under a level can correspond to a bit. For the first capability, the first capability has a corresponding bit. If the level where the first capability is located has a higher level in the level of the second node, that is, the level where the first capability is located is a sub-level of some other levels, then the capabilities under those other levels and the sub-levels of those other levels also have a corresponding number of bits.

[0157] For example, in a BM case with three levels, the first capability is the capability of the third level. The third level is a sub-level of the first and second levels. The first level has one capability (set to one bit), the second level has two capabilities (set to two bits), and the third level has four capabilities. However, since the second level exists, the third level is considered to have two capabilities: 4-beam to 8-beam prediction and 4-beam to 16-beam prediction, totaling five bits. The state identifier is 11111. In the first mapping relationship, the state of the first level's BM case capability with the first bit valued at 1 is considered to be in a supported state. The second and third bits with values ​​of 1 represent the supported states of the second level's time-domain prediction capability and spatial-domain prediction capability, respectively. The fourth and fifth bits with values ​​of 1 represent the supported states of the third level's 4-beam to 8-beam prediction and 4-beam to 16-beam prediction capabilities, respectively. Therefore, the state identifier is 10101. The state of the first capability corresponding to the first mapping relationship is BM. In the case of spatial domain prediction, the state of the 4-beam prediction capability to predict 16-beam is the support state. The identification of other states and the mapping relationship of the first capability state are similar, and will not be repeated here.

[0158] For example, in the BM case, there are 3 levels. The first capability is the capability of the second level. Then the status identifier of the first capability can have 3 bits. The status identifier is 110. The status of the first capability corresponding to the first mapping relationship is the status of the time-domain prediction capability under the BM case. The status is the support status, including 4-beam prediction, 8-beam capability and 16-beam BM case capability.

[0159] For example, mobility enhancement-related capabilities can be further divided into levels: Level 1: Mobility RRM measurement result prediction capability; Level 2: Beam-level reference signal L1 prediction capability; Level 3: Prediction window length of 10s and 5s capability; Level 4: Inference window of 2s and 1s capability; Level 5: Maximum predicted beam count of 4 and 2 capability. Again, using a bit value of 1 to represent the support status, following the above description order, the status identifier is 11111111, where the first 1 indicates Radio Resource Measurement (RRM) for mobility. The first "1" indicates that the measurement result prediction capability of the RRM is in a supported state. The second "1" indicates that the L1 prediction capability of the beam-level reference signal is in a supported state. The third and fourth "1"s indicate that the prediction window length of 10s and the prediction window length of 5s are in a supported state, respectively. The fifth and sixth "1"s indicate that the inference window length of 2s and the inference window length of 1s are in a supported state. The seventh and eighth "1"s indicate that the maximum number of predicted beams of 4 and the maximum number of predicted beams of 2 are in a supported state. The state identifier is 11011010. The states of the capabilities corresponding to the first mapping relationship are the mobility RRM measurement result prediction capability, beam-level reference signal L1 prediction capability, prediction window length of 5s capability, inference window length of 2s capability, and maximum number of predicted beams of 4 capability. The states of the other capabilities are not supported. The identifiers of other states and the mapping relationships of the capability states are similar and will not be repeated here.

[0160] For example, the five levels of mobility enhancement capabilities, with the first capability being the fifth level, can be represented by two bits. State identifier 01 in the first mapping relationship indicates that the capability with a predicted maximum beam count of 2 is in a supported state. Furthermore, when this level is determined to be a sub-level of some levels in the first mapping relationship, the capabilities of those levels are in a supported state. State identifier 01 in the first mapping relationship can also indicate that the capabilities in the first, second, third, and fourth levels are in a supported state. That is, state identifier 01 in the first mapping relationship can indicate that the capability with a predicted maximum beam count of 4 is in a supported state, and the capabilities in the first, second, third, and fourth levels are in a supported state. The identifiers for other states and the mapping relationships for capability states are similar and will not be elaborated here.

[0161] Optionally, the second node reports the capability level to the first node. If the first node cannot determine the specific level of the capability required by the LCM, it can determine the first level. There are sub-levels under the first level. The sub-levels under the first level should be the next level that is adjacent to the first level and the next level that is not adjacent. For example, in the BM case above, the sub-levels of the first level are the second level and the third level, and the sub-levels of the second level can be the third level. The capability of the first level and the capability of the sub-levels of the first level include the first capability.

[0162] Taking the three levels under the BM case as an example, the first node indicates the second level. The capabilities of the second level and its sub-levels include the first capability. That is, the capabilities of the second and third levels include the first capability. Accordingly, the first capability is the capability under the second level and the capability under the third level of the BM case.

[0163] When the first node indicates the first level, and the first capability includes the capabilities of the first level and the sub-levels of the second level, the first node may only instruct the second node to report the capability information of the first level, or it may instruct the second node to report all capability information and the capability level of the second node, such as the Functionality level, use case level, sub use case level, model ID level, DataSet level, etc.

[0164] For example, in the BM case with three levels, the first node instructs the second node to report the capabilities of the first level and the capabilities of the second level. Subsequently, the first capability negotiated between the first node and the second node is the capability of the first level, the second level, and the sub-levels of the first and second levels.

[0165] For example, regarding the five levels of mobility enhancement capabilities, if the first level indicated by the first node is the second, third, and fourth levels, then the first capability can include the capabilities of the second, third, and fourth levels and the sub-levels under these three levels. If the sub-level of the second, third, and fourth levels is the fifth level, then the first capability also includes the capability with a predicted maximum number of beams of 4 and the capability with a predicted maximum number of beams of 2, and the status of the capability of the fifth level needs to be reported.

[0166] Optionally, when the first capability is a capability under the first level and the sub-levels of the first level, after the capability of the first level is reported through the first mapping relationship, the first node and the second node can further negotiate whether to update the reported capability, such as reducing / increasing the capability of some sub-levels under the first level, or reducing / increasing the capability of some sub-levels under the first level.

[0167] S520, the second node sends first information to the first node, the first information being used to indicate the identifier of the first state in the first mapping relationship, and the identifier of the first state being used to indicate the update status of the first capability of the second node.

[0168] Accordingly, the first node receives the first information from the second node.

[0169] The first information can be an identifier of a first state. Alternatively, the first information can be a segment of information in which a certain field carries the identifier of the first state, or the first node may contain identifiers of multiple states, and the first information may be information indicating the first state among the identifiers of the multiple states.

[0170] This initial information can be transmitted to the first node via UAI / LPP.

[0171] After receiving the first information, the first node determines the identifier of the first state and obtains the updated state of the first capability through the first mapping relationship.

[0172] Optionally, if the status reporting conditions are met, the first node sends the first information to the first node.

[0173] The status reporting conditions include at least one of the following: the link status of the second node changes, the second node performs a switching operation, the second node performs a reconstruction operation, the status of the first capability changes, a reporting request is received from the first node, or a mapping relationship update is performed.

[0174] A change in the link status of a second node can mean the second node moves from a non-linked state to a linked state. A handover operation can switch the link between the second node and the first node to another node, such as switching to a link with a third node. A rebuild operation can restore the RRC signaling link for the second node, reducing downtime. A change in the status of the first AI capability can mean the first AI capability changes from supported to unsupported, or vice versa. Receiving a reporting request from the first node means receiving information sent by the first node instructing the second node to report the status of the first capability. Performing a mapping update involves negotiating a new mapping relationship between the first and second nodes.

[0175] Optionally, the status reporting condition can also be to report the capability and send the first information when the configured time is reached. The configured time can be set by configuring a timer on the second node and setting the interval to send the first information at regular intervals.

[0176] Optionally, the status reporting condition can be indicated by the first node.

[0177] The first node sends a second message to the second node, and the second node receives the second message from the first node. The second message indicates the status reporting conditions.

[0178] The second information can be a status reporting condition, or a field that carries information about status reporting conditions, or multiple pre-configured status reporting conditions in the second node. The second information indicates the status reporting condition among the multiple pre-configured status reporting conditions in the second node.

[0179] Optionally, the communication method further includes the first node sending third information to the second node, the third information being used to indicate the updated status reporting conditions.

[0180] The third piece of information can be the updated status reporting conditions. It can also be a field carrying information about the updated status reporting conditions. Alternatively, it can indicate the updated status reporting conditions among multiple pre-configured status reporting conditions in the second node. It can also be update information for status reporting conditions, such as deleting one or more conditions, adding one or more conditions, or modifying one or more conditions.

[0181] With this status reporting condition, the second node can proactively and promptly report the status of its capabilities to the first or third node. The first or third node can then promptly know about changes in the capability status of the second node, thereby adaptively adjusting LCM control and improving network performance.

[0182] Optionally, the communication method further includes the second node sending a fourth message to the first node, the fourth message indicating the reason for the change in the update state of the first capability, and correspondingly, the first node receiving the fourth message from the second node.

[0183] This fourth piece of information could be the reason for the change in update status, or the field could carry information about the reason for the change in update status.

[0184] For example, the update status of the first capability obtained by the first node through the first information is that the update status of the spatial domain prediction 4beam to 16beam capability under the BM case is not supported. The reason for the change in update status indicated by the corresponding fourth information is that the limited computing power causes the update status of the spatial domain prediction 4beam to 16beam capability under the BM case to be not supported.

[0185] Optionally, the first node and the second node can renegotiate their mapping relationship.

[0186] The renegotiated mapping relationship can be the identifier of the state that is still reported as the first capability, but the state of the first capability is adjusted to be mapped to.

[0187] The first and second nodes can renegotiate the mapping relationship and negotiate the mapping relationship between the state of the second capability and the state identifier between the second node and the first node. That is, modify the reported capability, stop reporting the first capability, report the second capability instead, and negotiate the mapping relationship between the state of the second capability and the state identifier.

[0188] The process by which the first node and the second node can renegotiate their mapping relationship can be referred to the process by which the first node and the second node can negotiate their first mapping relationship, and will not be repeated here.

[0189] The first and second nodes can renegotiate their mapping relationship. This could be because the first node determines that it doesn't need a certain capability of the second node for a certain period, and renegotiates the mapping between the second capability's state and its identifier. Alternatively, if the second stage determines that the state of a certain capability will not change for a certain period (e.g., it remains in an unsupported state), then that capability may not be included in the reported capabilities, resulting in a new mapping relationship. Or, if the identifier of the state in the first mapping relationship is incorrect, a new mapping relationship between the new state identifier and the state of the first capability can be renegotiated.

[0190] Optionally, S530 and the first node perform lifecycle management on the second node based on the update status of the first capability.

[0191] After obtaining the updated status of the first capability through the first information, the first node can perform lifecycle management through the updated status of the first capability, thereby improving network performance.

[0192] For example, if the second node reports a state of support for a capability with an observation window length of 10s in the first information it reports within a certain time period, and after a period of time, the second node reports a state of support for a capability with an observation window length of 10s, while the second node reports a state of support for a capability with an observation window length of 5s. This can be seen as the second node's capability with an observation window length of 10s changing to a capability with an observation window length of 5s. During lifecycle management, the current mobility enhancement can be exited.

[0193] Optionally, S540 and the second node can switch to linking with the third node.

[0194] Optionally, in S550, the first node sends fifth information to the third node. This fifth information is used to indicate the identifier of the second state, which is used to indicate the update status of the capabilities of the second node. There is a mapping relationship between the identifier of the second state and the update status of the capabilities of the second node.

[0195] Optionally, after the second node switches to link with the third node, the first node can send the first mapping relationship negotiated with the second node to the third node. The first node sends a sixth message to the third node, which is used to indicate the first mapping relationship. This first mapping relationship is used to indicate the mapping relationship between the state of the second node's first capability and the identifier of the state.

[0196] Optionally, after the first node and the second node renegotiate the mapping relationship, they can send all or part of the mapping relationship negotiated between the first node and the second node to the third node via a message to indicate all the mapping relationships negotiated between the first node and the second node.

[0197] After receiving all or part of the mapping relationship negotiated between the first node and the second node from the first node, the third node can continue to use the mapping relationship to report the capabilities of the second node, or it can renegotiate a new mapping relationship with the second node.

[0198] Optionally, the first node can send information to the third node, which can indicate the latest status of the second node's capabilities, and can also instruct the third node to renegotiate a new mapping relationship with the second node. This information can also indicate capability information in the first node, and the capability level in the first node, etc. The third node can use the mapping relationship negotiated between the second node and the first node, or renegotiate the mapping relationship with the second node, based on the information.

[0199] Optionally, the first node may not send any information to the third node, and the third node and the second node may negotiate the mapping relationship themselves.

[0200] The process of negotiating the mapping relationship between the third node and the second node is similar to that of negotiating the mapping relationship between the first node and the second node, and will not be described in detail here.

[0201] The first node sends a fifth message to the third node. This fifth message is used to indicate the identifier of the second state. The identifier of the second state is used to indicate the updated state of the capabilities of the second node. The mapping relationship between the identifier of the second state and the updated state of the capabilities of the second node can be a mapping relationship negotiated between the first node and the second node after the third node receives the instruction from the first node, or it can be a mapping relationship renegotiated between the third node and the second node.

[0202] The identifier of the second state, used to indicate the update status of the capabilities of the second node, can be understood as indicating the update status of certain capabilities within the second node. Accordingly, the identifier of the second state is the identifier of the status of those certain capabilities. When the third node receives the mapping relationship negotiated between the first and second nodes as indicated by the first node, such as when the third node receives the first mapping relationship indicated by the first node, those certain capabilities are the first capabilities. When the mapping relationship is renegotiated between the third and second nodes, those certain capabilities are the corresponding capabilities in the renegotiated mapping relationship between the third and second nodes.

[0203] Optionally, after receiving the updated capability status of the second node, the third node can perform lifecycle management on the second node based on the updated capability status.

[0204] In the case where the third node receives the mapping relationship negotiated between the first node and the second node as indicated by the first node, the third node receives the first mapping relationship indicated by the first node, some of which are first capabilities, and the third node receives the update status of the first capabilities. Then the third node can perform lifecycle management on the second node according to the update status of the first capabilities.

[0205] For example, the first node sends a sixth message to the third node. This sixth message indicates a first mapping relationship, which in turn indicates the mapping between the status of the second node's first capability and its identifier. After receiving this sixth message, the third node uses the first mapping relationship, allowing the second node to report its capabilities to the third node. The third node then receives a seventh message from the second node. This seventh message indicates the identifier of the third status in the first mapping relationship, which in turn indicates the update status of the first capability. The third node can then perform lifecycle management on the second node based on the update status of the first capability.

[0206] The difference between the seventh information and the first information is that the first information is information sent from the second node to the first node, while the seventh information is information sent from the second node to the third node. The identifiers of the states indicated by the seventh information and the first information both indicate the update status of the corresponding first capability in the first mapping relationship.

[0207] Optionally, when the second node sends information indicating the status to the first or third node according to the mapping relationship (such as first information, sixth information, etc.), it is implemented through UAI / LPP information.

[0208] In the embodiment shown in Figure 5 above, the first node and the second node can negotiate a mapping relationship. The capabilities corresponding to this mapping relationship are the capabilities required by the first node for LCM (Local Capability Management). The first node can report capabilities as needed, without reporting all supported capabilities. Instead, it reports the status of the required first capability through the mapping relationship. The status of this first capability determines whether the first node supports the required first capability, thereby reducing the communication overhead of capability reporting. Furthermore, when reporting capabilities subsequently, status identifier information indicating the capability determined by the mapping relationship can be reported, further reducing the communication overhead compared to directly reporting capabilities in the second node. The first node can obtain the status of the second node's capabilities and perform the LCM process accordingly, improving network performance. Moreover, after the second node switches to the third node, the first node can send the mapping relationship negotiated between the first and second nodes to the third node. This allows the third node to report capabilities based on the negotiated mapping relationship, further reducing the communication overhead of the second node reporting capabilities during the switch. Similarly, the third node can perform the LCM process based on the capabilities reported by the second node, improving network performance. Furthermore, status reporting conditions can be configured. When these conditions are met, the second node can proactively report its capabilities based on the mapping relationship with the first / third node. This avoids issues such as the first / third node being unable to promptly detect changes in the second node's capabilities when the first / third node has a need to adjust the LCM of the second node, leading to invalid LCM configurations. It also avoids the problem of the first / third node having to wait for the second node to report its updated capabilities before configuring the LCM, which increases the overall configuration time and improves configuration efficiency.

[0209] The following are examples of communication methods in two different communication systems.

[0210] Figure 6 is a schematic flowchart of a communication method 600 provided in an embodiment of this application. This method may include, but is not limited to, S610 to S650 below. It should be understood that the same content in the embodiment shown in Figure 6 as in the embodiment shown in Figure 5 can be referred to the foregoing description of the embodiment shown in Figure 5, and will not be repeated here.

[0211] In Figure 6, the first and third nodes are gNBs, and the second node is the UE. The first and third nodes can be further divided into a source gNB and a target gNB, respectively. Within the source and target gNBs, the modules that receive UE-reported capabilities and negotiate mapping relationships with the UE can be located in the gNB, CU, CU-CP, or CU-CP1. When located in CU-CP1, CU-CP2 is responsible for sending the signaling generated by CU-CP1 for interaction with the UE to the UE's RRC process.

[0212] The communication method includes:

[0213] S610, the UE and the source gNB negotiate the first mapping relationship, which is used to indicate the mapping relationship between the status of the UE's first capability and the identifier of the status.

[0214] S620, the UE sends first information to the source gNB. The first information is used to indicate the identifier of the first state in the first mapping relationship. The identifier of the first state is used to indicate the update status of the first capability of the second node.

[0215] The S620 implements the reporting of UE capabilities.

[0216] S630 and source gNB are managed for lifecycle.

[0217] S640, UE switches to target gNB.

[0218] S650, the source gNB sends the sixth information to the target gNB, which is used to indicate the first mapping relationship.

[0219] The target gNB and UE can use the first mapping relationship to report the first capability. The target gNB and UE can also agree on a new mapping relationship to report the UE capability.

[0220] In the embodiment shown in Figure 6 above, the UE and gNB can negotiate a mapping relationship. The corresponding capabilities in this mapping relationship are the capabilities required by the gNB to perform LCM. When reporting capabilities later, the UE can report the status identifier determined by the mapping relationship, thereby reducing the air interface overhead of the UE reporting capabilities. The gNB can obtain the status of the UE's capabilities and thus perform the LCM process according to the status of the UE's capabilities, thereby improving network performance.

[0221] Figure 7 is a schematic flowchart of a communication method 700 provided in an embodiment of this application. This method may include, but is not limited to, S710 to S750 below. It should be understood that the same content in the embodiment shown in Figure 7 as in the embodiment shown in Figure 5 can be referred to the foregoing description of the embodiment shown in Figure 5, and will not be repeated here.

[0222] In Figure 7, the first and third nodes represent the O-CU-CP in the developing RAN, and the second node is the UE. The UE interacts with the O-CU-CP via the O-DU, demonstrating its capability. The first and third nodes can be further divided into O-CU-CP1 and O-CU-CP2, respectively. The O-RU acts as an intermediary node for interaction between the UE and the O-CU-CP. The O-CU-CP generates the configuration to be sent to the UE and transmits it via the O-RU. Furthermore, the O-CU-CP performs LCM (Limited Module Management) to generate the decision method for the configuration to be sent to the UE, which can originate from the real-time or non-real-time RIC (Radio Interconnection Center).

[0223] S710 and O-CU-CP1 send information to the UE, which instructs the UE to report UE capability information.

[0224] S720: The UE reports its capabilities to the O-RU, and the O-RU forwards the reported UE capabilities to the O-CU-CP1.

[0225] The UE capability reported here is used as the first capability that needs to be reported in the subsequent O-CU-CP1 indication.

[0226] S730, UE, and O-CU-CP1 negotiate a first mapping relationship, which is used to indicate the mapping relationship between the state of the UE's first capability and the identifier of the state.

[0227] S740, the UE sends first information to O-CU-CP1. The first information is used to indicate the identifier of the first state in the first mapping relationship. The identifier of the first state is used to indicate the update status of the first capability of the second node.

[0228] S750 and O-CU-CP1 undergo lifecycle management.

[0229] S760 and UE switch to O-CU-CP2.

[0230] S770 and O-CU-CP1 send a sixth message to O-CU-CP2, which is used to indicate the first mapping relationship.

[0231] O-CU-CP2 and UE can use the first mapping relationship to report the first capability. O-CU-CP2 and UE can also agree on a new mapping relationship to report UE capabilities.

[0232] In the embodiment shown in Figure 7 above, the UE interacts with the O-RU and O-CU-CP to exchange UE capability information. This can be capability reporting at different levels. In this way, the UE and O-CU-CP can negotiate a mapping relationship. When reporting capabilities later, the UE can report the status identifier determined by the mapping relationship, thereby reducing the communication overhead of the UE reporting capabilities. The O-CU-CP can obtain the status of the UE's capabilities and perform the LCM process according to the status of the UE's capabilities, thereby improving network performance.

[0233] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 1 to 7. The apparatus provided by the embodiments of this application will be described in detail below with reference to Figures 8 to 10. To implement the functions of the methods provided by the embodiments of this application, each network element may include a hardware structure and / or a software module, implementing the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether a particular function is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

[0234] Figure 8 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in Figure 8, the communication device 800 may include a processing unit 810 and a transceiver unit 820.

[0235] In one possible design, the communication device 800 may correspond to the second node in the above method embodiments, or a chip configured in (or used for) the second node, or other devices, modules, circuits or units capable of implementing the method of the second node.

[0236] It should be understood that the communication device 800 may correspond to the second node in method 500 or the UE in methods 600 and 700 according to the embodiments of this application. The communication device 800 may include units for executing the method executed by the second node in method 500 of FIG. 5 and the method executed by the UE in methods 600 and 700 of FIG. 6 and 7. Furthermore, each unit in the communication device 800 and the other operations and / or functions described above are respectively for implementing the corresponding processes of methods 500, 600 and 700 in FIG. 5, 6 and 7.

[0237] It should also be understood that when the communication device 800 is a chip configured in (or used for) a second node, the transceiver unit 820 in the communication device 800 can be the chip's input / output interface or circuit, and the processing unit 810 in the communication device 800 can be the chip's processor.

[0238] Optionally, the communication device 800 may further include a processing unit 810, which can be used to process instructions or data to implement corresponding operations.

[0239] Optionally, the communication device 800 may further include a storage unit 830, which can be used to store instructions or data. The processing unit 810 can execute the instructions or data stored in the storage unit to enable the communication device to perform corresponding operations. The transceiver unit 820 in the communication device 800 may correspond to the transceiver 910 in the second node 900 shown in FIG. 9, and the storage unit 830 may correspond to the memory in the second node 900 shown in FIG. 9.

[0240] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0241] It should also be understood that when the communication device 800 is a second node, the transceiver unit 820 in the communication device 800 can be implemented through a communication interface (such as a transceiver, transceiver circuit, pin, or input / output interface), for example, it can correspond to the transceiver 910 in the terminal device 900 shown in FIG. 9. The processing unit 810 in the communication device 800 can be implemented through at least one processor, for example, it can correspond to the processor 920 in the terminal device 900 shown in FIG. 9. The processing unit 810 in the communication device 800 can be implemented through at least one logic circuit.

[0242] In another possible design, the communication device 800 may correspond to the first node / third node in the above method embodiments, for example, or a chip configured in (or used for) the first node / third node, or other device, module, circuit or unit, etc., capable of implementing the method of the first node / third node.

[0243] It should be understood that the communication device 800 may correspond to the first node / third node in method 500 according to the embodiments of this application, or the gNB in ​​method 600, or the O-CU-CP in method 700. The communication device 800 may include units for executing the methods performed by the first node / third node in method 500 of FIG. 5, the gNB in ​​method 600 of FIG. 6, and the O-CU-CP in method 700 of FIG. 7. Furthermore, each unit in the communication device 800 and the other operations and / or functions described above are respectively for implementing the corresponding processes of methods 500, 600, and 700 in FIGS. 5, 6, and 7.

[0244] It should also be understood that when the communication device 800 is a chip configured in (or used in) a first node / third node, the transceiver unit in the communication device 800 is an input / output interface or circuit in the chip, and the processing unit 810 in the communication device 800 may be a processor in the chip.

[0245] Optionally, the communication device 800 may further include a processing unit 810, which can be used to process instructions or data to implement corresponding operations.

[0246] Optionally, the communication device 800 may further include a storage unit 830, which can be used to store instructions or data. The processing unit can execute the instructions or data stored in the storage unit 830 to enable the communication device to perform corresponding operations. The storage unit 830 in the communication device 800 may correspond to the memory in the first node / third node 1000 shown in FIG10.

[0247] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0248] It should also be understood that when the communication device 800 is a first node / third node, the transceiver unit 820 in the communication device 800 can be implemented through a communication interface (such as a transceiver, transceiver circuit, pin, or input / output interface), for example, it can correspond to the transceiver 1010 in the first node / third node 1000 shown in FIG10. The processing unit 810 in the communication device 800 can be implemented through at least one processor, for example, it can correspond to the processor 1020 in the first node / third node 1000 shown in FIG10. The processing unit 810 in the communication device 800 can be implemented through at least one logic circuit.

[0249] Figure 9 is a schematic diagram of the structure of the second node 900 provided in an embodiment of this application. The first node 900 can be applied to the system shown in Figure 1 to perform the functions of the second node in the above method embodiment. As shown, the second node 900 includes a processor 920 and a transceiver 910. Optionally, the second node 900 also includes a memory. The processor 920, transceiver 910, and memory can communicate with each other through internal connection paths to transmit control and / or data signals. The memory is used to store computer programs, and the processor 920 is used to execute the computer programs in the memory to control the transceiver 910 to transmit and receive signals.

[0250] The processor 920 and the memory described above can be combined into a single processing device. The processor 920 executes the program code stored in the memory to achieve the aforementioned functions. In specific implementations, the memory can be integrated into the processor 920 or independent of the processor 920. The processor 920 can correspond to the processing unit in Figure 8.

[0251] The transceiver 910 described above can correspond to the transceiver unit in Figure 8. The transceiver 910 may include a receiver (or receiver circuit) and a transmitter (or transmitter circuit). The receiver is used to receive signals, and the transmitter is used to transmit signals.

[0252] It should be understood that the second node 900 shown in Figure 9 can implement the processes involving the second node in the method embodiments shown in Figures 5, 6, and 7. The operations and / or functions of each module in the second node 900 are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the descriptions in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0253] The processor 920 described above can be used to execute the actions implemented internally by the second node as described in the preceding method embodiments, while the transceiver 910 can be used to execute the actions described in the preceding method embodiments of sending to or receiving from the first / third node by the second node. For details, please refer to the descriptions in the preceding method embodiments; they will not be repeated here.

[0254] Optionally, the second node 900 may also include a power supply for providing power to various devices or circuits in the second node.

[0255] In addition, to make the second node more functional, the second node 900 may also include one or more of an input unit, a display unit, an audio circuit, a camera, and a sensor, and the audio circuit may also include a speaker, a microphone, etc.

[0256] Figure 10 is a structural schematic diagram of the first node provided in an embodiment of this application. It can be understood that the structural schematic diagram shown in Figure 10 can also be considered as a structural schematic diagram of the third node. Here, Figure 10 serves as a structural schematic diagram of the first node / third node 1000. The first node / third node 1000 can be applied to the system shown in Figure 1 to execute the functions of the first node / third node in the above method embodiment. For example, it can be a schematic diagram of the related structure of the first node / third node. As shown, the first node / third node 1000 includes a processor 1020 and a transceiver 1010. Optionally, the first node / third node 1000 also includes a memory. The processor 1020, transceiver 1010, and memory can communicate with each other through internal connection paths to transmit control and / or data signals. The memory is used to store computer programs, and the processor 1020 is used to execute the computer programs in the memory to control the transceiver 1010 to transmit and receive signals.

[0257] It should be understood that the first node / third node 1000 shown in Figure 10 can implement the various processes involving the first node / third node in the method embodiments shown in Figures 5, 6, and 7. The operations and / or functions of each module in the first node / third node 1000 are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the description in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0258] It should be understood that the first node / third node 1000 shown in Figure 10 can be an eNB or a gNB. Optionally, the first node / third node includes CU, DU, and AAU first / third nodes, etc. Optionally, the CU can be specifically divided into CU-CP and CU-UP. This application does not limit the specific architecture of the first node / third node.

[0259] It should be understood that the first node / third node 1000 shown in Figure 10 can be a CU node or a CU-CP node, etc.

[0260] This application also provides a processing apparatus, including a processor and a (communication) interface; the processor is used to execute the method in any of the above method embodiments.

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

[0262] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0263] According to the method provided in the application embodiments, this application embodiment also provides a computer program product, which includes: computer program code, which, when executed by one or more processors, causes a device including the processor to perform the method in the embodiments shown in FIG5, FIG6 and FIG7.

[0264] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions of the embodiments of this application are performed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a first node / third node, a user equipment, or other programmable device.

[0265] According to the method provided in the embodiments of this application, the embodiments of this application also provide a computer-readable storage medium that stores the above-mentioned computer program or instructions. When the computer program or instructions are run by one or more processors, the device including the processor performs the method in the embodiments shown in FIG5, FIG6 and FIG7.

[0266] As described above, computer programs or instructions can be stored in or transferred from one computer-readable storage medium to another. For example, a computer program or instruction can be transferred from one website, computer, server, or data center to another via wired or wireless means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be magnetic media, such as floppy disks, hard disks, and magnetic tapes; optical media, such as digital video discs; or semiconductor media, such as solid-state drives. The computer-readable storage medium can be volatile or non-volatile, or may include both volatile and non-volatile types of storage media.

[0267] According to the method provided in the embodiments of this application, the embodiments of this application also provide a communication system, including one or more of the aforementioned communication devices.

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

[0269] 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 units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

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

[0272] In the embodiments of this application, provided there is no logical contradiction, the embodiments may reference each other. For example, the methods and / or terms between method embodiments may reference each other, the functions and / or terms between device embodiments may reference each other, and the functions and / or terms between device embodiments and method embodiments may reference each other.

[0273] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Negotiate a first mapping relationship with the first node, the first mapping relationship being used to indicate the mapping relationship between the state of the first capability of the second node and the identifier of the state; Send first information to the first node, the first information being used to indicate the identifier of the first state in the first mapping relationship, and the identifier of the first state being used to indicate the update status of the first capability of the second node.

2. The method according to claim 1, characterized in that, The capabilities of the second node have at least two levels, including a first level, the capabilities of which include the first capability.

3. The method according to claim 2, characterized in that, The first level includes sub-levels, and the capabilities of the first level and the capabilities of the sub-levels of the first level include the first capability.

4. The method according to any one of claims 1 to 3, characterized in that, Sending the first information to the first node includes: If the status reporting conditions are met, send the first information to the first node.

5. The method according to claim 4, characterized in that, The status reporting conditions include at least one of the following: the second node's link status changes, the second node performs a switching operation, the second node performs a reconstruction operation, the first capability's status changes, receiving a reporting request from the first node, and performing a mapping relationship update.

6. The method according to claim 4 or 5, characterized in that, The method further includes: Receive second information from the first node, the second information being used to indicate the status reporting conditions.

7. The method according to any one of claims 4 to 6, characterized in that, The method further includes: Receive third information from the first node, the third information being used to indicate the updated status reporting conditions.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Send a fourth message to the first node, the fourth message indicating the reason for the change in the update status of the first capability.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: The mapping relationship is renegotiated with the first node.

10. The method according to claim 9, characterized in that, The renegotiation of the mapping relationship with the first node includes: Negotiate with the first node the mapping relationship between the state of the second capability and the identifier of the state.

11. The method according to any one of claims 1 to 9, characterized in that, The method further includes: Switch the link from the first node to the third node; A fifth message is sent to the third node. The fifth message is used to indicate the identifier of the second state. The identifier of the second state is used to indicate the update status of the capabilities of the second node. There is a mapping relationship between the identifier of the second state and the update status of the capabilities of the second node.

12. A communication method, characterized in that, include: Negotiate a first mapping relationship with the second node, the first mapping relationship being used to indicate the mapping relationship between the state of the second node's first capability and the identifier of the state; Receive first information from the second node, the first information being used to indicate the identifier of a first state in the first mapping relationship, the identifier of the first state being used to indicate the update status of the first capability.

13. The method according to claim 12, characterized in that, The method further includes: The second node is subject to lifecycle management based on the updated status of the first capability.

14. The method according to claim 12 or 13, characterized in that, The capabilities of the second node have at least two levels, including a first level, the capabilities of which include the first capability.

15. The method according to claim 14, characterized in that, The first level includes sub-levels, and the capabilities of the first level and the capabilities of the sub-levels of the first level include the first capability.

16. The method according to any one of claims 12 to 15, characterized in that, The method further includes: Send a second message to the second node, the second message being used to indicate the status reporting conditions for the second node to send the first message.

17. The method according to any one of claims 12 to 16, characterized in that, The method further includes: The mapping relationship is renegotiated with the second node.

18. The method according to any one of claims 17, characterized in that, The renegotiation of the mapping relationship with the second node includes: Negotiate with the second node the mapping relationship between the state of the second capability and the identifier of the state.

19. The method according to any one of claims 12 to 18, characterized in that, The method further includes: When the second node switches to a link with the third node, a sixth message is sent to the third node, the sixth message indicating the first mapping relationship.

20. A communication method, characterized in that, include: Receive fifth information from the second node, the fifth information being used to indicate the identifier of the second state, the identifier of the second state being used to indicate the update status of the capabilities of the second node, and there is a mapping relationship between the identifier of the second state and the update status of the capabilities of the second node.

21. The method according to claim 20, characterized in that, The method further includes: The lifecycle management of the second node is performed based on the updated status of its capabilities.

22. A communication method, characterized in that, include: Receive sixth information from the first node, the sixth information being used to indicate a first mapping relationship, the first mapping relationship being used to indicate the mapping relationship between the state of the first capability of the second node and the identifier of the state; Receive seventh information from the second node, the seventh information being used to indicate the identifier of the third state of the first mapping relationship, the identifier of the third state being used to indicate the update state of the first capability.

23. The method according to claim 22, characterized in that, The method further includes: The second node is subject to lifecycle management based on the updated status of the first capability.

24. A communication device, characterized in that, Used to implement the method as described in any one of claims 1 to 23.

25. A communication device, characterized in that, It includes a processor and a memory, the memory and the processor being coupled together, the processor being used to perform the method of any one of claims 1 to 23.

26. A communication device comprising a processor and a communication interface, wherein the processor uses the communication interface to perform the method of any one of claims 1 to 23.

27. A communication system, characterized in that, The communication device included in any one of claims 24 to 26.

28. A computer-readable storage medium, characterized in that, The computer stores instructions that, when executed on the computer, cause the computer to perform the method as described in any one of claims 1 to 23.

29. A computer program product, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 23.

Images