Information transmission method and apparatus, storage medium, and program product

Abstract

Embodiments of the present invention relate to the technical field of communications, and provide an information transmission method and apparatus, a storage medium, and a program product, which can guarantee the communication quality between nodes in a communication network to the greatest extent possible. The method comprises: receiving first information, wherein the first information is used for querying capability information of a first node; and sending second information, wherein the second information comprises first capability information and / or second capability information, for example, the first capability information is used for indicating capability information of the first node related to layer 1- or layer 2-triggered mobility (LTM) switching, and the second capability information is used for indicating capability information of the first node related to an extended reality (XR) service.

Description

Information transmission methods, devices, storage media and program products

[0001] This disclosure claims priority to Chinese patent application No. 202510475248.1, filed on April 16, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of communication technology, and in particular to information transmission methods, devices, storage media and program products. Background Technology

[0003] In wireless communication systems, the exchange of capability information between network devices and terminals is crucial for achieving efficient resource allocation and protocol compatibility. However, currently, terminals are unable to report certain capability information to network devices. This prevents network devices from distinguishing between situations where a terminal does not support a capability and situations where a terminal is unable to report data related to a capability due to communication anomalies, thus affecting the communication quality between network devices and terminals. Summary of the Invention

[0004] This disclosure provides an information transmission method, apparatus, storage medium, and program product that can maximize the communication quality between nodes in a communication network.

[0005] On the one hand, an information transmission method is provided, including: receiving first information, the first information being used to query the capability information of a first node;

[0006] Send a second message, which includes first capability information and / or second capability information. For example, the first capability information is used to indicate capability information related to mobility LTM handover triggered by layer 1 or layer 2 of the first node, and the second capability information is used to indicate capability information related to extended reality XR services of the first node.

[0007] On the other hand, an information transmission method is provided, including: sending first information, the first information being used to query the capability information of a first node;

[0008] Receive second information, which includes first capability information and / or second capability information. For example, the first capability information is used to indicate capability information related to mobility LTM handover triggered by layer 1 or layer 2 of the first node, and the second capability information is used to indicate capability information related to extended reality XR services of the first node.

[0009] In another aspect, an information transmission device is provided, comprising: a communication unit and a processing unit; the processing unit is configured to instruct the communication unit to receive first information, the first information being used to query the capability information of a first node;

[0010] The processing unit is also configured to instruct the communication unit to send second information, the second information including first capability information and / or second capability information. For example, the first capability information is used to indicate capability information related to mobility LTM handover triggered by layer 1 or layer 2 of the first node, and the second capability information is used to indicate capability information related to extended reality XR services of the first node.

[0011] In another aspect, an information transmission device is provided, comprising: a processing unit for instructing a communication unit to send first information, the first information being used to query capability information of a first node;

[0012] The processing unit is also configured to instruct the communication unit to receive second information, the second information including first capability information and / or second capability information. For example, the first capability information is used to indicate capability information related to mobility LTM handover triggered by Layer 1 or Layer 2 of the first node, and the second capability information is used to indicate capability information related to extended reality XR services of the first node.

[0013] In another aspect, a communication device is provided, comprising: a memory and a processor; the memory and the processor are coupled; the memory is used to store a computer program; and the processor, when executing the computer program, implements the information transmission method of any of the above embodiments.

[0014] In another aspect, a computer-readable storage medium is provided, on which computer program instructions are stored, which, when executed by a processor, implement the information transmission method of any of the above embodiments; the computer-readable medium includes a non-transitory computer-readable medium.

[0015] In another aspect, a computer program product is provided, which includes computer program instructions that, when executed by a processor, implement the information transmission method of any of the above embodiments.

[0016] This disclosure discloses that a first node and / or a third node can, in response to first information used to query the capabilities of the first node, report information about LTM handover capabilities and / or XR service capabilities (i.e., second information) to a second node. This allows the second node to distinguish between situations where the first node does not support the capability (e.g., LTM handover capability, XR service capability, etc.) and situations where the first node is unable to report data related to the capability due to communication anomalies. This enables the second node to adaptively optimize communication between the first node and other nodes in the communication network, thereby maximizing the communication quality between nodes in the communication network. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in this disclosure, the accompanying drawings used in some embodiments of this disclosure will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings.

[0018] Figure 1 is a communication system architecture diagram according to an embodiment of the present disclosure;

[0019] Figure 2 is a flowchart illustrating an information transmission method according to an embodiment of the present disclosure;

[0020] Figure 3 is a flowchart illustrating another information transmission method according to an embodiment of the present disclosure;

[0021] Figure 4 is a flowchart illustrating another information transmission method according to an embodiment of the present disclosure;

[0022] Figure 5 is a flowchart illustrating another information transmission method according to an embodiment of the present disclosure;

[0023] Figure 6 is a flowchart illustrating another information transmission method according to an embodiment of the present disclosure;

[0024] Figure 7 is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0025] Figure 8 is a schematic diagram of the structure of another communication device according to an embodiment of the present disclosure. Detailed Implementation

[0026] The technical solutions of this disclosure will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0027] Unless the context otherwise requires, throughout the specification and claims, the term "comprise" and its other forms, such as the third-person singular "comprises" and the present participle "comprising," are interpreted as open-ended and encompassing, meaning "including, but not limited to." In the description of the specification, terms such as "one embodiment," "some embodiments," "exemplary embodiments," "example," "specific example," or "some examples," etc., are intended to indicate that a particular feature, structure, material, or characteristic associated with that embodiment or example is included in at least one embodiment or example of this disclosure. The illustrative representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, a particular feature, structure, material, or characteristic may be included in any suitable manner in any one or more embodiments or examples.

[0028] It should be noted that, in this disclosure, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in this disclosure should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0029] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0030] In the description of this disclosure, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "more than one" means two or more.

[0031] In this disclosure, suffixes such as "module," "part," or "unit" used to represent elements are used only for the purpose of illustrative purposes and have no inherent meaning. Therefore, "module," "part," or "unit" can be used interchangeably.

[0032] In long-term evolution (LTE) systems, self-organizing networks (SON) reduce network deployment and maintenance costs through self-configuration and self-optimization. However, with the introduction of 5G New Radio (NR) systems, traditional SON functions face challenges in dynamic mobility management and high-reliability service support. The 3rd Generation Partnership Project (3GPP) release 16 first proposed combining SON with minimum path test (MDT), and subsequent releases 17 and 18 introduced implementations that further enhanced the data collection capabilities of SON / MDT.

[0033] Furthermore, the SON / MDT function can be combined with at least one of the following functions to further enhance the SON / MDT function: mobility robustness optimization (MRO) function based on L1 / 2-triggered mobility (LTM) mechanism, conditional handover (CHO) function involving candidate secondary cell group (SCG), conditional PSCell Addition or Change (CPAC) function, mobility handover function in non-terrestrial network (NTN), network slicing function, or extended reality (XR) service.

[0034] However, currently, terminals are unable to report some of their capabilities to network devices, making it impossible for network devices to distinguish between situations where the terminal does not support the capability and situations where the terminal cannot report data related to the capability, thus affecting the communication quality between network devices and terminals.

[0035] For example, if a terminal is unable to report LTM handover capability information to the network device, the network device cannot clearly distinguish whether the terminal supports LTM handover. In this case, the network device may assume that the terminal supports LTM handover and then send an LTM handover command to the terminal.

[0036] If the terminal does not actually support LTM handover capabilities, it will not report an LTM handover failure to the network device. However, if there is a communication failure between the terminal and the network device, the terminal will also be unable to report an LTM handover failure to the network device.

[0037] Consequently, network devices cannot distinguish between a terminal's failure to report an LTM handover failure due to the terminal's lack of LTM handover capability and a terminal's inability to report an LTM handover failure due to abnormal communication between the terminal and the network device. This affects the efficiency of communication optimization between the network device and the terminal, and consequently, the quality of communication between the network device and the terminal.

[0038] For example, if a terminal is unable to report XR service capability information to the network device, the network device may be unable to distinguish between the terminal's failure to report XR service data due to its lack of support for XR services and the terminal's failure to report XR service data due to communication abnormalities between the terminal and the network device. This will affect the efficiency of XR service measurement and optimization between the network device and the terminal, and consequently affect the communication quality between the network device and the terminal.

[0039] In response to this, embodiments of the present disclosure provide an information transmission method in which a first node and / or a third node may, in response to first information used to query the capabilities of the first node, report information about LTM handover capabilities and / or XR service capabilities (i.e., second information) to a second node. This allows the second node to distinguish between situations where the first node does not support the capability (e.g., LTM handover capability, XR service capability, etc.) and situations where the first node is unable to report data related to the capability due to communication anomalies. This enables the second node to adaptively optimize communication between the first node and other nodes in the communication network, thereby maximizing the communication quality between nodes in the communication network.

[0040] The information transmission method provided in this disclosure can be applied to systems with various communication standards. For example, the information transmission method provided in this disclosure is applicable to systems including, but not limited to, Long Term Evolution (LTE) systems, various versions based on LTE evolution, 5G systems, future mobile communication networks, or multiple converged communication systems. Furthermore, the information transmission method provided in this disclosure can also be applied to future-oriented communication systems.

[0041] For example, the above information transmission method can be applied to the communication system shown in Figure 1. As shown in Figure 1, the communication system includes: a first node 101, a second node 102, and a third node 103.

[0042] For example, the second node 102 can communicate with both the first node 101 and the third node 103. The first node 101 can be referred to as user equipment (UE), terminal-side equipment, user-side equipment, etc. The second node 102 can also be referred to as base station-side equipment, network-side equipment, etc. The third node 103 can be referred to as core network element, core network-side equipment, etc.

[0043] In some embodiments, the first node 101 or the third node 103 receives first information from the second node 102, which is used to query the capability information of the first node. Then, the second node 102 sends second information to the first node 101 or the third node 103. This second information includes first capability information and / or second capability information. For example, the first capability information indicates capability information related to LTM handover for the first node, and the second capability information indicates capability information related to XR services for the first node. This allows the second node 102 to distinguish between situations where the first node 101 does not support certain capabilities (e.g., LTM handover capabilities, XR service capabilities, etc.) and situations where the first node 101 cannot report capability-related data normally due to communication anomalies. This enables the second node 102 to adaptively optimize communication between the first node 101 and other nodes in the communication system (e.g., the second node 102), thereby maximizing the communication quality between nodes in the communication network.

[0044] It should be noted that Figure 1 is only an exemplary framework diagram. The number of communication devices included in Figure 1 and the names of each communication device are not limited. In addition to the communication devices shown in Figure 1, the communication system may also include other communication devices, such as relay nodes.

[0045] The application scenarios of the embodiments disclosed herein are not limited. The system architecture and business scenarios described in the embodiments of this disclosure are for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and do not constitute a limitation on the technical solutions provided by the embodiments of this disclosure. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of this disclosure are also applicable to similar technical problems.

[0046] The information transmission method provided by the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0047] The information transmission method provided in this embodiment can be applied to the first node 101 in the communication system shown in FIG1. ​​FIG2 shows a schematic flowchart of an information transmission method, which includes the following steps S201 and S202.

[0048] S201, Receive the first message.

[0049] For example, the first information is used to query the capability information of the first node.

[0050] S202, Send the second message.

[0051] For example, the second information includes first capability information and / or second capability information. For instance, the first capability information is used to indicate capability information related to LTM handover of the first node, and the second capability information is used to indicate capability information related to XR services of the first node.

[0052] In addition, in some embodiments, the second information may also include other capability information, such as augmented reality (AR) services, which is not limited in this application embodiment.

[0053] In this application, the first node and / or the third node may, in response to the first information used to query the capabilities of the first node, report information about LTM handover capabilities and / or XR service capabilities (i.e., the second information) to the second node. This allows the second node to distinguish between situations where the first node does not support the capability (e.g., LTM handover capability, XR service capability, etc.) and situations where the first node is unable to report the capability-related data normally due to communication anomalies. This enables the second node to adaptively optimize the communication between the first node and other nodes in the communication network, thereby ensuring the communication quality between nodes in the communication network as much as possible.

[0054] The following provides a detailed explanation of the primary capability information.

[0055] In some embodiments, the first capability information includes at least one of the following: whether the first node supports reporting radio link failure (RLF) reports triggered by LTM handover failure, whether the first node supports LTM handover, whether the first node supports reporting successful handover history (SHR) reports triggered by LTM handover success, and whether the first node supports reporting reports triggered by LTM handover.

[0056] For example, the first capability information can be as follows:

[0057] The above describes the capability information related to the LTM handover of the first node. However, assuming the first node fails to perform an LTM handover, the first node can attempt to re-establish the connection with PCell1 before entering the connected state (or during the operation of the started T311 timer), and the attempt to re-establish the connection with PCell1 fails (referred to as Scenario 1); or, the first node can attempt to re-perform one or more consecutive LTM handovers before entering the connected state, but all one or more consecutive LTM handovers fail (referred to as Scenario 2). For example, the first node performs an LTM handover before entering the connected state to attempt to switch to PCell2, and if the handover to PCell2 fails, it performs another LTM handover to attempt to switch to PCell3, but the handover to PCell3 fails. In both of these scenarios, the first node will be triggered to report an RLF report. The following describes an embodiment of the first node reporting an RLF report.

[0058] In some embodiments, referring to FIG2 and as shown in FIG3, after S202 above, the method provided by this disclosure embodiment further includes:

[0059] S301, Send RLF report.

[0060] In some embodiments, the implementation process of S301 described above can be: the first node sends an RLF report to the second node. The above description takes the example of the first node reporting an RLF report to the second node. The first node can also send an RLF report to other nodes. For example, the first node reports an RLF report to a fourth node. The fourth node can act as a relay node between the first node and the second node. For example, the fourth node can be another terminal in the communication system other than the first node. This application embodiment does not limit this.

[0061] For example, the RLF report includes: a fault report of the last LTM handover failure that occurred before the first node entered the connected state; or,

[0062] The first node reports an LTM handover failure for the first time before entering the connected state; or,

[0063] The fault report of the last LTM handover failure before the first node enters the connected state, and the fault report of the first LTM handover failure before the first node enters the connected state; or,

[0064] The first node reports an LTM handover failure each time it enters the connected state.

[0065] Furthermore, taking the example of the first node's last LTM handover failure report before entering the connected state included in the RLF report: the first node can record the last LTM handover failure report before entering the connected state in the RLF report by deleting and then recording the fault report. Specifically, the first node can record the first LTM handover failure report in the RLF report. If another LTM handover failure occurs, the recorded first LTM handover failure report is deleted from the RLF report, and the second LTM handover failure report is recorded.

[0066] Alternatively, the first node can record the last LTM handover failure report in the RLF report before entering the connected state by overwriting the fault report. Specifically, the first node can record the first LTM handover failure report in the RLF report. If another LTM handover failure occurs, the fault report of the second LTM handover failure will overwrite the fault report of the first LTM handover failure in the RLF report.

[0067] Furthermore, taking the fault report in the RLF report, which includes the last LTM handover failure report of the first node before entering the connected state and the first LTM handover failure report of the first node before entering the connected state, as an example: the first node defines two fields in the RLF report. The above two fields are used to carry the fault report of the last LTM handover failure of the first node before entering the connected state and the fault report of the first LTM handover failure of the first node before entering the connected state, respectively.

[0068] Alternatively, the first node may define a list in the RLF report that includes at least two entries. Any two of these entries may correspond to the fault report of the first node's last LTM handover failure before entering the connected state, and the fault report of the first node's first LTM handover failure before entering the connected state. For example, the first entry of these at least two entries may correspond to the fault report of the first node's last LTM handover failure before entering the connected state, and the second entry of these at least two entries may correspond to the fault report of the first node's first LTM handover failure before entering the connected state.

[0069] The implementation process of recording the last LTM handover failure report of the first node before entering the connected state in the defined fields or lists can be understood by referring to the above implementation process of recording the last LTM handover failure report of the first node before entering the connected state in the RLF report, and will not be repeated here.

[0070] In some embodiments, the RLF report also includes the cause of the RLF failure, which includes at least one of the following: layer 1 beam failure, channel state information reference signal (CSI RS) measurement failure, media access control (MAC) scheduling conflict, hybrid automatic repeat request (HARQ) retransmission limit overrun, listen before talk (LBT) channel failure (LBT railure-r16), and synchronization failure.

[0071] Furthermore, in some embodiments, layer 1 beam failure can refer to layer 1 beam alignment failure, or it can refer to layer 1 beam recovery time exceeding the mobility requirements of layer 1 or layer 2.

[0072] CSI-RS measurement failure refers to the failure of CSI-RS measurement results to be updated in a timely manner, resulting in Layer 1 beam failure or cell selection error.

[0073] MAC layer scheduling conflict refers to the failure of Layer 2 dynamic scheduling to reserve sufficient resources for low-latency handover, such as the pre-allocated physical uplink control channel (PUCCH) resources or physical uplink shared channel (PUSCH) resources being preempted.

[0074] HARQ retransmission failure refers to the failure to retransmit data packets in a timely manner during the HARQ process under the Layer 2 fast retransmission mechanism. Furthermore, this HARQ retransmission failure occurs at the MAC layer, not the radio link control (RLC) layer.

[0075] LBT channel failure: In the unlicensed spectrum (NR-U), L1 channel preemption fails, for example, the clear channel assessment (CCA) used to detect whether the channel is idle is continuously busy.

[0076] Synchronization failure refers to the failure of the Layer 1 or Layer 2 synchronization signal (e.g., the synchronization signal block (SSB)) to complete alignment during LTM handover, resulting in synchronization timeout.

[0077] In some embodiments, the cause of an RLF failure is carried in the RLF failure cause field of the RLF report; or, the cause of an RLF failure is carried in the LTM handover failure cause field of the RLF report, thus providing two embodiments for reporting the cause of an RLF failure.

[0078] The following provides a detailed explanation of the second ability information.

[0079] In some embodiments, the information of the second capability includes at least one of the following: whether the first node supports measuring the quality of XR services, whether the first node supports XR services, and whether the first node supports adjusting the radio resources of XR services.

[0080] The above describes the capability information related to XR services reported by the first node. However, when the first node supports XR services, measurements (e.g., SON / MDT, quality of experience (QoE)) can be used to measure the XR services supported by the first node to evaluate their performance. Existing measurement methods are usually random or fixed-area triggering methods, which cannot perform targeted measurements of XR services. This easily leads to measurements of a large number of non-XR service hotspot areas (e.g., industrial areas), resulting in the collection of a large amount of redundant data and wasting storage and processing resources. To achieve targeted measurement of XR services, the following describes an embodiment of measurement configuration for XR services.

[0081] In some embodiments, referring to FIG2 and as shown in FIG4, after S202 described above, the method provided by this disclosure further includes:

[0082] S401, Receive third information.

[0083] For example, the third piece of information is used to indicate the area where the first node is located when it is triggered to measure the quality of the XR service.

[0084] In some embodiments, the third information includes the identifier of the geographic raster where the first node is located when the first node is triggered to measure the quality of the XR service.

[0085] In some embodiments, the geographic raster division method described in this application can be reused as the geographic raster division method of MDT measurement configuration or other geographic raster division methods, and the embodiments of this application do not limit this.

[0086] Furthermore, the third information is also used to indicate the measurement priority of the XR service. In this embodiment, the third information can directly include the measurement priority of the XR service corresponding to the geographic raster where the first node is located. Different geographic rasters can correspond to different XR service measurement priorities. For example, the measurement priority of the XR service corresponding to the office building raster is set to low, and the measurement priority of the XR service corresponding to the stadium raster is set to high. In addition, the measurement priority of the XR service can also be represented by a numerical value; the higher the value, the higher the measurement priority of the corresponding XR service.

[0087] In other embodiments, the third information includes the tracking area identity (TAI) of the first node when it is triggered to measure the quality of the XR service.

[0088] As described above regarding the third information, the third information is also used to indicate the measurement priority of XR services. In this embodiment, the third information can implicitly indicate the measurement priority of the XR service corresponding to the tracking area where the first node is located. For example, the measurement priority of XR services can be configured in batches according to the TAI list, that is, the tracking areas where the first node is located are arranged in order of XR service measurement priority from low to high or from high to low.

[0089] Furthermore, this embodiment is generally applicable to wide-area XR service scenarios (e.g., in-vehicle AR navigation), but it can also be applied to other scenarios, and this application embodiment does not limit this.

[0090] In some embodiments, the third information includes the identifier of the cell where the first node is located when the first node is triggered to measure the quality of the XR service.

[0091] As described above regarding the third information, the third information is also used to indicate the measurement priority of XR services. In this embodiment, the third information can implicitly indicate the measurement priority of the XR service corresponding to the cell where the first node is located. For example, the cells where the first node is located can be arranged in order of XR service measurement priority from low to high or from high to low.

[0092] Furthermore, when the first node is triggered to measure the quality of the XR service, the cell where the first node is located is usually a cell with a high load (or load) determined based on historical data statistics. It can also be a cell with other characteristics (e.g., poor signal quality). This application embodiment does not limit this.

[0093] In some embodiments, prior to S401, the third node may also reuse the relevant signaling for MDT configuration or the dedicated signaling for measuring XR service configuration to send third information to the second node. The third information sent by the second node to the first node may be carried in existing measurement configuration information (e.g., SON / MDT configuration information, QoE configuration information). Furthermore, when the first node indicates in the radio resource control (RRC) message obtained from the second node that the current service type of the first node is XR service, it initiates XR service measurement.

[0094] As described above regarding RLF reports, these reports can include fault reports of LTM handover failures. Besides LTM handovers, RLF reports can also include CHO-related information. Currently, when the cell involved in the current handover involves a primary cell (PCell) and the handover type is CHO, existing protocols specify that the last handover (lastHO) type is set to CHO. In other words, existing protocols specify how CHO-related information involving the master cell group (MCG) should be carried in the RLF report. However, existing protocols do not specify how CHO-related information involving the SCG (e.g., lastHO-type, SCG addition indication information, SCG modification indication information, etc.) should be carried in the RLF report.

[0095] For example, the information related to the CHO involving SCG includes at least one of the following: expanding the enumeration value in lastHO-type, predefining the lastHO-type SCG field, reusing the CHO in lastHO-type and supplementing the CHO with auxiliary fields to define the CHO.

[0096] For example, the extended enumeration values ​​in lastHO-type include at least one of the following: conditional switching involving MCG is set to CHO MCG or CHO, and conditional switching involving SCG is set to CHO SCG. If the last executed RRC reconfiguration message including synchronous reconfiguration includes information related to CHO involving MCG, then lastHO-type is set to CHO or CHO MCG; if the last executed RRC reconfiguration message including synchronous reconfiguration includes information related to CHO involving SCG, then lastHO-type is set to CHO SCG.

[0097] For example, lastHO-type can be as follows:

[0098] The predefined `lastHO-type` SCG field includes information about the most recent CHO execution by the node residing in the SCG. For example, the information about the most recent CHO execution by the node residing in the SCG is set to at least one of the following: CHOs involving the SCG are set to CHO, LTM handovers involving the SCG are set to LTM, and dual active protocol stack (DAPS) handovers involving the SCG are set to DAPS. If the last executed RRC reconfiguration message, including synchronous reconfiguration, includes information related to a CHO involving the SCG, then `lastHO-type` is set to CHO.

[0099] For example, if the last executed RRC reconfiguration message, which includes synchronous reconfiguration, contains information related to the CHO involving the SCG, then the lastHO-type can also be as follows:

[0100] The auxiliary fields include last cell group information defined by the last CHO execution. For example, the last CHO execution cell group information includes any one of the following: MCG, or SCG, or both MCG and SCG. The condition for the existence of last CHO execution cell group information is that the lastHO-type is set to CHO and / or LTM and / or DAPS. Specifically, the condition for the existence of last CHO execution cell group information is that the last executed RRC reconfiguration message, including synchronization reconfiguration, includes CHO-related information.

[0101] If the last executed RRC reconfiguration message, including the synchronization reconfiguration, includes CHO-related information involving the MCG, then the cell group information for the last executed CHO is set to include the MCG; if the last executed RRC reconfiguration message, including the synchronization reconfiguration, includes CHO-related information involving the SCG, then the cell group information for the last executed CHO is set to include the SCG.

[0102] For example, the last cell group information for the CHO execution can be as follows:

[0103] lastCellGroupinfo ENUMERATED{mcg,scg,both,spare1}OPTIONAL,

[0104] In some embodiments, the last part of the description used in this application can be replaced with the latest, most recent or other relevant descriptions, and this application does not limit this.

[0105] The information transmission method provided in this disclosure can be applied to the second node 102 in the communication system shown in FIG1. ​​FIG5 shows a schematic flowchart of another information transmission method, which includes the following steps S501 and S502.

[0106] S501, Send the first message.

[0107] For example, the first information is used to query the capability information of the first node.

[0108] S502, Receive the second information.

[0109] For example, the second information includes first capability information and / or second capability information. For instance, the first capability information is used to indicate capability information related to LTM handover of the first node, and the second capability information is used to indicate capability information related to XR services of the first node.

[0110] One example is a communication between a second node and a first node, illustrating the information transmission method: the second node sends first information to the first node and receives second information from the first node.

[0111] Furthermore, in this example, the first information can be carried in a UE capability query message, and the second information can be carried in a UE capability message. The above are examples of messages in which the first and second information are carried. The first and second information can also be carried in other messages, such as the second information being carried in a random access procedure message (MSG) 3 or uplink control information (UCI). This application embodiment does not limit this.

[0112] Another example illustrates the information transmission method using communication between a second node and a third node: the second node sends first information to the third node and receives second information from the third node.

[0113] Furthermore, in this example, the first information can be carried in the initial UE message, and the second information can be carried in the initial context setup request message. In addition, the second information can specifically be carried in the UE radio capability field of the initial context setup request message, and it can also be carried in other fields of the initial context setup request message (e.g., dedicated fields, UE differentiation information fields), which is not limited in this embodiment. The above are examples of messages in which the first and second information are carried. The first and second information can also be carried in other messages, for example, the second information can be carried in an NG setup response or a handover request acknowledge message, which is not limited in this embodiment.

[0114] It should be noted that the descriptions of the first information, LTM switching, second information, XR services, and related effects can be found in the description on the first node side, and will not be repeated here in the embodiments disclosed herein.

[0115] The information transmission method provided in this disclosure can be applied to the third node 103 in the communication system shown in FIG1. ​​FIG6 shows a schematic flowchart of another information transmission method, which includes the following steps S601 and S602.

[0116] S601, Receive the first message.

[0117] For example, the first information is used to query the capability information of the first node.

[0118] S602, Send the second message.

[0119] For example, the second information includes first capability information and / or second capability information. For instance, the first capability information is used to indicate capability information related to LTM handover of the first node, and the second capability information is used to indicate capability information related to XR services of the first node.

[0120] It should be noted that the descriptions of the first information, LTM switching, second information, XR services, and related effects are not repeated here in the embodiments disclosed herein.

[0121] To achieve the aforementioned functions, the information transmission device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art will readily recognize that, based on the algorithmic steps of the examples described in conjunction with the embodiments of this disclosure, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware 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 disclosure.

[0122] This disclosure embodiment can divide the information transmission device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one functional module. The integrated module can be implemented in hardware or software. It should be noted that the module division in this disclosure embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the example of dividing each functional module according to each function.

[0123] Figure 7 is a schematic diagram of a communication device according to an embodiment of the present disclosure. The communication device can execute the information transmission method provided in the above-described method embodiments. As shown in Figure 7, the communication device includes a communication unit 701 and a processing unit 702.

[0124] When the structural diagram shown in Figure 7 is used to represent the structure of the first node:

[0125] The processing unit is used to instruct the communication unit to receive first information, which is used to query the capability information of the first node;

[0126] The processing unit is further configured to instruct the communication unit to receive and send second information, the second information including first capability information and / or second capability information. For example, the first capability information is used to indicate capability information related to mobility LTM handover triggered by Layer 1 or Layer 2 of the first node, and the second capability information is used to indicate capability information related to extended reality XR services of the first node.

[0127] In some embodiments, the first capability information includes at least one of the following: whether the first node supports reporting a Radio Link Failure (RLF) report triggered by an LTM handover failure, whether the first node supports LTM handover, whether the first node supports reporting a Handover Success History (SHR) report triggered by a successful LTM handover, and whether the first node supports reporting a report triggered by an LTM handover.

[0128] In some embodiments, the processing unit is further configured to instruct the communication unit to receive and send an RLF report; the RLF report includes a fault report of the first node's last LTM handover failure before entering the connected state; or, a fault report of the first node's first LTM handover failure before entering the connected state; or, a fault report of the first node's last LTM handover failure before entering the connected state and a fault report of the first node's first LTM handover failure before entering the connected state; or, a fault report of each LTM handover failure before entering the connected state.

[0129] In some embodiments, the RLF report may also include the cause of the RLF failure, which may include at least one of the following: Layer 1 beam failure, Channel State Information Reference Signal (CSI) RS measurement failure, Media Access Control (MAC) scheduling conflict, Hybrid Automatic Repeat Request (HARQ) retransmission exceeding limit, Radio Pre-Transmission Listen Channel (LBT) failure, and synchronization failure.

[0130] In some embodiments, the cause of an RLF failure is carried in the RLF failure cause field of the RLF report; or, the cause of an RLF failure is carried in the LTM handover failure cause field of the RLF report.

[0131] In some embodiments, the information of the second capability includes at least one of the following: whether the first node supports measuring the quality of XR services, whether the first node supports XR services, and whether the first node supports adjusting the radio resources of XR services.

[0132] In some embodiments, the processing unit is further configured to instruct the communication unit to receive third information, the third information being used to indicate the area where the first node is located when the first node is triggered to measure the quality of the XR service.

[0133] In some embodiments, the third information includes the identifier of the geographic raster where the first node is located when the first node is triggered to measure the quality of the XR service; or the identifier of the tracking area where the first node is located when the first node is triggered to measure the quality of the XR service; or the identifier of the cell where the first node is located when the first node is triggered to measure the quality of the XR service.

[0134] In some embodiments, the third information is also used to indicate the measurement priority of the XR service.

[0135] When the structural diagram shown in Figure 7 is used to represent the structure of the second node:

[0136] The processing unit is used to instruct the communication unit to send first information, which is used to query the capability information of the first node.

[0137] The processing unit is also configured to instruct the communication unit to receive second information, the second information including first capability information and / or second capability information. For example, the first capability information is used to indicate capability information related to mobility LTM handover triggered by Layer 1 or Layer 2 of the first node, and the second capability information is used to indicate capability information related to extended reality XR services of the first node.

[0138] In some embodiments, the first capability information includes at least one of the following: whether the first node supports reporting a Radio Link Failure (RLF) report triggered by an LTM handover failure, whether the first node supports LTM handover, whether the first node supports reporting a Handover Success History (SHR) report triggered by a successful LTM handover, and whether the first node supports reporting a report triggered by an LTM handover.

[0139] In some embodiments, the processing unit is further configured to instruct the communication unit to receive an RLF report; the RLF report includes a fault report of the first node's last LTM handover failure before entering the connected state; or, a fault report of the first node's first LTM handover failure before entering the connected state; or, a fault report of the first node's last LTM handover failure before entering the connected state and a fault report of the first LTM handover failure within the period before entering the connected state; or, a fault report of each LTM handover failure of the first node before entering the connected state.

[0140] In some embodiments, the RLF report may also include the cause of the RLF failure, which may include at least one of the following: Layer 1 beam failure, Channel State Information Reference Signal (CSI) RS measurement failure, Media Access Control (MAC) scheduling conflict, Hybrid Automatic Repeat Request (HARQ) retransmission exceeding limit, Radio Pre-Transmission Listen Channel (LBT) failure, and synchronization failure.

[0141] In some embodiments, the cause of an RLF failure is carried in the RLF failure cause field of the RLF report; or, the cause of an RLF failure is carried in the LTM handover failure cause field of the RLF report.

[0142] In some embodiments, the information of the second capability includes at least one of the following: whether the first node supports measuring the quality of XR services, whether the first node supports XR services, and whether the first node supports adjusting the radio resources of XR services.

[0143] In some embodiments, the processing unit is further configured to instruct the communication unit to send third information, the third information being used to indicate the area where the first node is located when the first node is triggered to measure the quality of the XR service.

[0144] In some embodiments, the third information includes the identifier of the geographic raster where the first node is located when the first node is triggered to measure the quality of the XR service; or the identifier of the tracking area where the first node is located when the first node is triggered to measure the quality of the XR service; or the identifier of the cell where the first node is located when the first node is triggered to measure the quality of the XR service.

[0145] In some embodiments, the third information is also used to indicate the measurement priority of the XR service.

[0146] When the structural diagram shown in Figure 7 is used to represent the structure of the third node:

[0147] The processing unit is used to instruct the communication unit to receive first information, which is used to query the capability information of the first node;

[0148] The processing unit is also configured to instruct the communication unit to send second information, the second information including first capability information and / or second capability information. For example, the first capability information is used to indicate capability information related to mobility LTM handover triggered by layer 1 or layer 2 of the first node, and the second capability information is used to indicate capability information related to extended reality XR services of the first node.

[0149] In some embodiments, the first capability information includes at least one of the following: whether the first node supports reporting a Radio Link Failure (RLF) report triggered by an LTM handover failure, whether the first node supports LTM handover, whether the first node supports reporting a Handover Success History (SHR) report triggered by a successful LTM handover, and whether the first node supports reporting a report triggered by an LTM handover.

[0150] In some embodiments, the information of the second capability includes at least one of the following: whether the first node supports measuring the quality of XR services, whether the first node supports XR services, and whether the first node supports adjusting the resources of XR services.

[0151] In the case of implementing the functions of the integrated modules described above in hardware, this disclosure provides another possible structure for the communication device involved in the above embodiments. As shown in FIG8, the communication device 80 includes: a processor 802 and a bus 804. Optionally, the communication device may further include a memory 801; optionally, the communication device may further include a communication interface 803.

[0152] Processor 802 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 802 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 802 may also be a combination of functions implementing computational capabilities, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0153] The communication interface 803 is used to connect to other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0154] The memory 801 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage medium or other magnetic storage device, or 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.

[0155] In some embodiments, the memory 801 may exist independently of the processor 802. The memory 801 may be connected to the processor 802 via a bus 804 and may be used to store instructions or program code. When the processor 802 calls and executes the instructions or program code stored in the memory 801, it can implement the information transmission method provided in the embodiments of this disclosure.

[0156] In other embodiments, the memory 801 may also be integrated with the processor 802.

[0157] Bus 804 can be an extended industry standard architecture (EISA) bus, etc. Bus 804 can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in Figure 8, but this does not mean that there is only one bus or one type of bus.

[0158] Some embodiments of this disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) storing computer program instructions that, when executed on a computer, cause the computer to perform an information transmission method as described in any of the above embodiments.

[0159] Exemplary examples show that the aforementioned computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described in this disclosure may represent one or more devices for storing information and / or other machine-readable storage media. The term "machine-readable storage media" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0160] This disclosure provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the information transmission method of any of the above embodiments. The above are merely specific embodiments of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions within the technical scope disclosed in this disclosure should be covered within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. An information transmission method, wherein, Applied to the first node, the method includes: Receive first information, which is used to query the capability information of the first node; Send a second message, the second message including first capability information and / or second capability information, wherein the first capability information is used to indicate capability information related to mobility LTM handover triggered by the first node at layer 1 or layer 2, and the second capability information is used to indicate capability information related to extended reality XR services of the first node.

2. The method according to claim 1, wherein, The first capability information includes at least one of the following: whether the first node supports reporting a Radio Link Failure (RLF) report triggered by the LTM handover failure; whether the first node supports the LTM handover; whether the first node supports reporting a Handover Success History Record (SHR) report triggered by the LTM handover success; and whether the first node supports reporting a report triggered by the LTM handover.

3. The method according to claim 1 or 2, wherein, The method further includes: Send an RLF report; the RLF report includes a fault report of the last LTM handover failure that occurred before the first node entered the connected state; or, The first node reports an LTM handover failure for the first time before entering the connected state; or, The fault report of the first node's last LTM handover failure before entering the connected state, and the fault report of the first node's first LTM handover failure before entering the connected state; or, The first node reports a failure of LTM handover each time it enters the connected state.

4. The method according to claim 3, wherein, The RLF report also includes the cause of the RLF failure, which includes at least one of the following: Layer 1 beam failure, Channel State Information Reference Signal (CSI) RS measurement failure, Media Access Control (MAC) scheduling conflict, Hybrid Automatic Repeat Request (HARQ) retransmission exceeding limit, Radio Pre-Transmission Listen (LBT) channel failure, and synchronization failure.

5. The method according to claim 4, wherein, The cause of the RLF failure is contained in the RLF failure cause field of the RLF report; or... The cause of the RLF failure is contained in the LTM handover failure reason field of the RLF report.

6. The method according to claim 1, wherein, The information of the second capability includes at least one of the following: whether the first node supports measuring the quality of the XR service, whether the first node supports the XR service, and whether the first node supports adjusting the radio resources of the XR service.

7. The method according to claim 1 or 6, wherein, The method further includes: Receive third information, which is used to indicate the area where the first node is located when the first node is triggered to measure the quality of the XR service.

8. The method according to claim 7, wherein, The third information includes the identifier of the geographic raster where the first node is located when the first node is triggered to measure the quality of the XR service; or... When the first node is triggered to measure the quality of the XR service, the identifier of the tracking area where the first node is located; or... The identifier of the cell where the first node is located when the first node is triggered to measure the quality of the XR service.

9. The method according to claim 7, wherein, The third piece of information is also used to indicate the measurement priority of the XR service.

10. An information transmission method, wherein, Applied to the second node, the method includes: Send the first message, which is used to query the capability information of the first node; Receive second information, the second information including first capability information and / or second capability information, wherein the first capability information is used to indicate capability information related to mobility LTM handover triggered by the first node at layer 1 or layer 2, and the second capability information is used to indicate capability information related to extended reality XR services of the first node.

11. The method according to claim 10, wherein, The first capability information includes at least one of the following: whether the first node supports reporting a Radio Link Failure (RLF) report triggered by the LTM handover failure; whether the first node supports the LTM handover; whether the first node supports reporting a Handover Success History Record (SHR) report triggered by the LTM handover success; and whether the first node supports reporting a report triggered by the LTM handover.

12. The method according to claim 10 or 11, wherein, The method further includes: Receive an RLF report; the RLF report includes a fault report of the last LTM handover failure that occurred before the first node entered the connected state; or, The first node reports an LTM handover failure for the first time before entering the connected state; or, The fault report of the first node's last LTM handover failure before entering the connected state, and the fault report of the first node's first LTM handover failure before entering the connected state; or, The first node reports a failure of LTM handover each time it enters the connected state.

13. The method according to claim 12, wherein, The RLF report also includes the cause of the RLF failure, which includes at least one of the following: Layer 1 beam failure, Channel State Information Reference Signal (CSI) RS measurement failure, Media Access Control (MAC) scheduling conflict, Hybrid Automatic Repeat Request (HARQ) retransmission exceeding limit, Radio Pre-Transmission Listen (LBT) channel failure, and synchronization failure.

14. The method according to claim 13, wherein, The cause of the RLF failure is contained in the RLF failure cause field of the RLF report; or... The cause of the RLF failure is contained in the LTM handover failure reason field of the RLF report.

15. The method according to claim 10, wherein, The information of the second capability includes at least one of the following: whether the first node supports measuring the quality of the XR service, whether the first node supports the XR service, and whether the first node supports adjusting the radio resources of the XR service.

16. The method according to claim 10 or 15, wherein, The method further includes: Send a third message, which indicates the area where the first node is located when the first node is triggered to measure the quality of the XR service.

17. The method according to claim 16, wherein, The third information includes the identifier of the geographic raster where the first node is located when the first node is triggered to measure the quality of the XR service; or... When the first node is triggered to measure the quality of the XR service, the identifier of the tracking area where the first node is located; or... The identifier of the cell where the first node is located when the first node is triggered to measure the quality of the XR service.

18. The method according to claim 16, wherein, The third piece of information is also used to indicate the measurement priority of the XR service.

19. An information transmission method, wherein, Applied to a third node, the method includes: Receive first information, which is used to query the capability information of the first node; Send a second message, the second message including first capability information and / or second capability information, wherein the first capability information is used to indicate capability information related to mobility LTM handover triggered by the first node at layer 1 or layer 2, and the second capability information is used to indicate capability information related to extended reality XR services of the first node.

20. The method according to claim 19, wherein, The first capability information includes at least one of the following: whether the first node supports reporting a Radio Link Failure (RLF) report triggered by the LTM handover failure; whether the first node supports the LTM handover; whether the first node supports reporting a Handover Success History Record (SHR) report triggered by the LTM handover success; and whether the first node supports reporting a report triggered by the LTM handover.

21. The method according to claim 19, wherein, The information of the second capability includes at least one of the following: whether the first node supports measuring the quality of the XR service, whether the first node supports the XR service, and whether the first node supports adjusting the resources of the XR service.

22. A communication device, wherein, include: Memory and processor; Memory and processor are coupled; The memory is used to store instructions that can be executed by the processor; When the processor executes the instructions, it performs the method as described in any one of claims 1-21.

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

24. A computer program product, wherein, The computer program product includes computing technology program instructions, which, when executed by a processor, implement the method as described in any one of claims 1-21.

Images