Information transmission method, communication device, and storage medium

Abstract

The present application discloses an information transmission method, a communication device, and a storage medium, which relate to the field of communications. The method includes: a terminal receiving capability query signaling from a network device; and the terminal transmitting capability information of the terminal to the network device, the capability information including a first capability item and dual-active protocol stack (DAPS) capability information supported by the terminal corresponding to the first capability item, and / or a second capability item and carrier aggregation (CA) capability information supported by the terminal corresponding to the second capability item. In the method, the DAPS capability information supported by the terminal is reported to the network device using the first capability item, and / or the CA capability information supported by the terminal is reported to the network device using the second capability item, so that the DAPS capability information and the CA capability information supported by the terminal can be reported separately, and therefore, when the DAPS capability information is the same as or different from the CA capability information, both the CA capability information and the DAPS capability information can be reported to the network device.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of communication technologies, and in particular, to information transmission methods, communication devices, and storage media.

Background Art

[0002] The concept of dual active protocol stack (DAPS) handover has been introduced in the 5th-generation (5G) mobile communication standard R16. DAPS handover means that in the process of handover from a source cell to a target cell, a user equipment (UE) maintains connections to both the source cell and the target cell to which the UE should be handed over, and does not release the link to the source cell until the link to the target cell is successfully established. By means of DAPS handover, the interruption time caused by the UE handover process can be shortened, and the reliability of the UE handover can be improved.

[0003] Before initiating a DAPS handover, network devices (e.g., a source base station corresponding to a source cell) need to obtain DAPS capability information supported by the UE. Currently, the main direction of the 3rd generation partnership project (3GPP®) standards is to report DAPS capability information supported by the UE by reusing the band combination structure included in the UE's radio frequency parameters (RF-Parameters) when the UE's capability information is reported. For example, parameter information for source and target cells in a DAPS handover may be reported by using the Band Combination->feature Set Combination ID corresponding to the feature Set Combination, and parameter information when the UE establishes connectivity to both the source and target cells may be reported by using Band Combination->caParametersNR and Band Combination->bandlist->band.

[0004] In the aforementioned method of reporting DAPS capability information by reusing the band combination structure, the band combination structure is originally intended for reporting carrier aggregation (CA) capability information. When DAPS capability information is reported by reusing the band combination structure, the DAPS capability information to be reported must be the same as the CA capability information. However, in practice, DAPS capability information may differ from CA capability information, and DAPS capability information that differs from CA capability information cannot be reported using the method of reporting DAPS capability information by reusing the band combination structure. [Overview of the project] [Means for solving the problem]

[0005] Embodiments of this application provide an information transmission method, a communication device, and a storage medium that can satisfy the requirements for reporting DAPS capability information when DAPS capability information differs from CA capability information.

[0006] According to a first aspect, one embodiment of the present application provides an information transmission method. The method includes the steps of: a terminal receiving capability inquiry signaling from a network device; and the terminal transmitting terminal capability information to the network device. The capability information includes a first capability item and dual active protocol stack (DAPS) capability information corresponding to the first capability item, supported by the terminal, and / or a second capability item and carrier aggregation (CA) capability information corresponding to the second capability item, supported by the terminal.

[0007] In this information transmission method, the capability information of a terminal that is transmitted to a network device by the terminal after receiving capability inquiry signaling from the network device includes a first capability item and dual-active protocol stack (DAPS) capability information corresponding to the first capability item that is supported by the terminal, as well as a second capability item and carrier aggregation (CA) capability information corresponding to the second capability item that is supported by the terminal. Therefore, the DAPS capability information and CA capability information supported by the terminal can be reported separately. Compared to current technology, the decoupling of the DAPS capability information and CA capability information supported by the terminal is implemented, so that both the CA capability information and the DAPS capability information can be reported to the network device if the DAPS capability information is the same as or different from the CA capability information.

[0008] In one possible design, capability information includes specific parameters for each band in multiple band combinations and is supported by the terminal. The DAPS capability information corresponding to a first capability item is specific parameters for each band in one of the multiple band combinations and / or is supported by the terminal. The CA capability information corresponding to a second capability item is specific parameters for each band in one of the multiple band combinations.

[0009] In one possible design, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters for each band in different band combinations.

[0010] In this design, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item can correspond to specific parameters of each band in different band combinations, respectively, in order to report the DAPS capability information and CA capability information.

[0011] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters for each band in the same band combination.

[0012] In this design, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item can correspond to specific parameters of each band in the same band combination in order to report the DAPS capability information and the CA capability information.

[0013] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first and second capability items may also correspond to specific parameters for each band in different band combinations.

[0014] In one possible design, the DAPS capability information corresponding to a first capability item supported by the terminal includes at least one of the following: uplink DAPS capability and downlink DAPS capability at a per-bandwidth granularity, or uplink DAPS capability and downlink DAPS capability at a per-carrier granularity.

[0015] This design allows for the addition of several DAPS-specific capability enhancements.

[0016] According to a second aspect, one embodiment of the present application provides a communication device that can be applied to a terminal. The device has a function to carry out the method according to the first aspect described above. The function may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more units or modules corresponding to the function of the method according to the first aspect described above.

[0017] For example, the communication device may include a receiving module configured to receive capability inquiry signaling from a network device, and a transmitting module configured to transmit terminal capability information to the network device. The capability information includes a first capability item and dual active protocol stack (DAPS) capability information corresponding to the first capability item, supported by the terminal, and / or a second capability item and carrier aggregation (CA) capability information corresponding to the second capability item, supported by the terminal.

[0018] In one possible design, capability information includes specific parameters for each band in multiple band combinations and is supported by the terminal. The DAPS capability information corresponding to a first capability item is specific parameters for each band in one of the multiple band combinations and / or is supported by the terminal. The CA capability information corresponding to a second capability item is specific parameters for each band in one of the multiple band combinations.

[0019] In one possible design, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters for each band in different band combinations.

[0020] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters for each band in the same band combination.

[0021] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first and second capability items may also correspond to specific parameters for each band in different band combinations.

[0022] In one possible design, the DAPS capability information corresponding to a first capability item supported by the terminal includes at least one of the following: uplink DAPS capability and downlink DAPS capability at a per-bandwidth granularity, or uplink DAPS capability and downlink DAPS capability at a per-carrier granularity.

[0023] According to a third aspect, an embodiment of the present application further provides a communication device including a processor configured to execute computer instructions stored in a memory. When the computer instructions are executed, the device is enabled to perform the method according to any one of the first aspect or possible designs of the first aspect.

[0024] According to a fourth aspect, an embodiment of the present application further provides a communication device including a processor and an interface circuit. The processor communicates with another device via the interface circuit and is configured to perform the method according to any one of the first aspect or possible designs of the first aspect.

[0025] The communication device in the second aspect to the fourth aspect can be applied to a terminal.

[0026] According to a fifth aspect, an embodiment of the present application further provides a computer-readable storage medium including computer software instructions. When the computer software instructions operate in a terminal or a chip built in the terminal, the terminal is enabled to perform the method according to the first aspect.

[0027] Regarding the beneficial effects achievable in the second aspect to the fifth aspect, it will be understood that reference may be made to the beneficial effects in any one of the first aspect and possible designs of the first aspect. Details are not described again here.

[0028] According to a sixth aspect, an embodiment of the present application provides an information transmission method. The method includes a step in which a network device transmits capability query signaling to a terminal, and a step in which the network device receives capability information from the terminal device. The capability information includes a first capability item and dual active protocol stack (DAPS) capability information corresponding to the first capability item supported by the terminal, and / or a second capability item and carrier aggregation (CA) capability information corresponding to the second capability item supported by the terminal.

[0029] In this information transmission method, after receiving the capability query signaling from the network device, the capability information of the terminal transmitted by the terminal to the network device includes the first capability item, and the dual active protocol stack (DAPS) capability information corresponding to the first capability item supported by the terminal, as well as the second capability item, and the carrier aggregation (CA) capability information corresponding to the second capability item supported by the terminal. Therefore, the DAPS capability information and the CA capability information supported by the terminal can be reported separately. Compared with the current technology, since the separation between the DAPS capability information and the CA capability information supported by the terminal is implemented, when the DAPS capability information is the same as or different from the CA capability information, both the CA capability information and the DAPS capability information can be reported to the network device.

[0030] In one possible design, the capability information includes the specific parameters of each band in a plurality of band combinations. The DAPS capability information corresponding to the first capability item supported by the terminal is the specific parameters of each band in one of the plurality of band combinations, and / or the CA capability information corresponding to the second capability item supported by the terminal is the specific parameters of each band in one of the plurality of band combinations.

[0031] In one possible design, when the DAPS capability information supported by the terminal is different from the CA capability information supported by the terminal, the first capability item and the second capability item correspond to the specific parameters of each band in different band combinations.

[0032] In this design, when the DAPS capability information supported by the terminal is different from the CA capability information supported by the terminal, the first capability item and the second capability item can respectively correspond to the specific parameters of each band in different band combinations for reporting the DAPS capability information and the CA capability information.

[0033] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters for each band in the same band combination.

[0034] In this design, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item can correspond to specific parameters of each band in the same band combination in order to report the DAPS capability information and the CA capability information.

[0035] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first and second capability items may also correspond to specific parameters for each band in different band combinations.

[0036] In one possible design, the DAPS capability information corresponding to a first capability item supported by the terminal includes at least one of the following: uplink DAPS capability and downlink DAPS capability at a per-bandwidth granularity, or uplink DAPS capability and downlink DAPS capability at a per-carrier granularity.

[0037] This design allows for the addition of several DAPS-specific capability enhancements.

[0038] According to a seventh aspect, one embodiment of the present application provides a communication device that can be applied to a network device. The device has a function to carry out the method according to the sixth aspect described above. The function may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more units or modules corresponding to the function of the method according to the sixth aspect described above.

[0039] For example, the communication device may include a transmitting module configured to send capability inquiry signaling to a terminal and a receiving module configured to receive capability information from the terminal. The capability information includes a first capability item and dual active protocol stack (DAPS) capability information corresponding to the first capability item, which is supported by the terminal, and / or a second capability item and CA capability information corresponding to the second capability item, which is supported by the terminal.

[0040] In one possible design, capability information includes specific parameters for each band in multiple band combinations and is supported by the terminal. The DAPS capability information corresponding to a first capability item is specific parameters for each band in one of the multiple band combinations and / or is supported by the terminal. The CA capability information corresponding to a second capability item is specific parameters for each band in one of the multiple band combinations.

[0041] In one possible design, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters for each band in different band combinations.

[0042] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters for each band in the same band combination.

[0043] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first and second capability items may also correspond to specific parameters for each band in different band combinations.

[0044] In one possible design, the DAPS capability information corresponding to a first capability item supported by the terminal includes at least one of the following: uplink DAPS capability and downlink DAPS capability at a per-bandwidth granularity, or uplink DAPS capability and downlink DAPS capability at a per-carrier granularity.

[0045] According to the eighth aspect, one embodiment of the present application further provides a communication device including a processor configured to execute computer instructions stored in memory. When the computer instructions are executed, the device is enabled to perform a method according to the sixth aspect or any one of a possible design of the sixth aspect.

[0046] According to the ninth aspect, one embodiment of the present application further provides a communication device including a processor and an interface circuit. The processor is configured to communicate with another device via the interface circuit and to perform a method according to the sixth aspect or any one of a possible design of the sixth aspect.

[0047] The communication devices in the seventh to ninth embodiments may be applied to network devices, such as source base stations.

[0048] According to a tenth aspect, one embodiment of the present application further provides a computer-readable storage medium containing computer software instructions. When the computer software instructions operate in a network device or a chip embedded in a network device, the network device is enabled to perform the method according to the sixth aspect.

[0049] For beneficial effects that can be achieved in the seventh through tenth embodiments, it will be understood that we should refer to the beneficial effects in the sixth embodiment and any one of the possible designs of the sixth embodiment. Further details will not be provided here.

[0050] According to the eleventh aspect, one embodiment of the present application provides an information transmission method. The method includes the steps of: a terminal maintaining link communication with a first cell and successfully accessing a second cell; the terminal receiving a first reconfiguration message from a network device in the second cell; and the terminal releasing its configuration in the first cell based on the first reconfiguration message.

[0051] In this information transmission method, during the DAPS handover process, the terminal maintains link communication with the first cell, and after successfully accessing the second cell, it releases the configuration in the first cell when it receives the first reconfiguration message sent by the network device of the second cell. Therefore, the terminal only needs to retain two sets of configurations: the configuration in the second cell and the configuration in the reconfiguration message sent by the network device of the second cell; it does not need to retain three sets of configurations. In this way, the terminal does not need to allocate memory space for three sets of configurations during the DAPS handover, thereby significantly reducing the complexity of the terminal implementation.

[0052] In one possible design, the first reconfiguration message is the first reconfiguration message received by the terminal from the network device of the second cell after the terminal has successfully accessed the second cell.

[0053] In one possible design, the first reconfiguration message may or may not include a source cell configuration release instruction.

[0054] If the first reconfiguration message includes a source cell configuration release instruction, the terminal may release the configuration in the first cell based on the source cell configuration release instruction. If the first reconfiguration message does not include a source cell configuration release instruction, the terminal may automatically release the configuration in the first cell.

[0055] In another possible design, the first reconfiguration message does not include a source cell configuration release instruction, and the method further includes the step of the terminal leaving the existing configuration in the second cell unchanged and / or sending a reconfiguration error message to the network device in the second cell.

[0056] In one possible design, the step of a terminal maintaining link communication with a first cell and successfully accessing a second cell includes, in the DAPS handover process, the step of the terminal receiving a handover command from a network device in the first cell, and the step of the terminal maintaining link communication with the first cell and successfully accessing a second cell based on the handover command.

[0057] In one possible design, the step of the terminal successfully accessing the second cell includes the step of the terminal synchronizing with the second cell and sending a reconfiguration complete message to the network device of the second cell.

[0058] According to a twelfth aspect, one embodiment of the present application provides a communication device that can be applied to a terminal. The device has a function to carry out the method according to the eleventh aspect described above. The function may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more units or modules corresponding to the function of the method according to the eleventh aspect described above.

[0059] For example, the communication device may include an access module configured to maintain link communication between a terminal and a first cell and to access a second cell successfully; a receive module configured to receive a first reconfiguration message from a network device in the second cell; and a release module configured to release the terminal configuration in the first cell based on the first reconfiguration message.

[0060] In one possible design, the first reconfiguration message is the first reconfiguration message received by the receiving module from the network device of the second cell after the terminal has successfully accessed the second cell.

[0061] In one possible design, the first reconfiguration message may or may not include a source cell configuration release instruction.

[0062] In another possible design, the first reconfiguration message does not include a source cell configuration release instruction, and the access module is further configured to leave the existing configuration in the second cell unchanged and / or to send a reconfiguration error message to the network device in the second cell.

[0063] In one possible design, during the DAPS handover process, the receiving module is further configured to receive handover commands from the network device of the first cell, and the access module is configured to maintain link communication between the terminal and the first cell based on the handover commands and to successfully access the second cell.

[0064] In one possible design, the access module is configured to control the terminal to synchronize with the second cell and send a reconfiguration complete message to the network device of the second cell.

[0065] According to a thirteenth aspect, one embodiment of the present application further provides a communication device including a processor configured to execute computer instructions stored in memory. When the computer instructions are executed, the device is enabled to perform a method according to the eleventh aspect or any one of a possible design thereof.

[0066] According to a fourteenth aspect, one embodiment of the present application further provides a communication device including a processor and an interface circuit. The processor is configured to communicate with another device via the interface circuit and to perform a method according to the eleventh aspect or any one of a possible design of the eleventh aspect.

[0067] The communication devices in the 12th to 14th embodiments may be applied to terminals.

[0068] According to a 15th aspect, one embodiment of the present application further provides a computer-readable storage medium containing computer software instructions. When the computer software instructions operate in a terminal or a chip embedded in a terminal, the terminal is enabled to perform the method according to the 11th aspect.

[0069] For beneficial effects that can be achieved in the twelfth through fifteenth embodiments, it will be understood that we should refer to the beneficial effects in the eleventh embodiment and any one of the possible designs of the eleventh embodiment. Further details will not be provided here.

[0070] According to the sixteenth aspect, one embodiment of the present application provides an information transmission method. The method includes the step of a network device in a second cell sending a first reconfiguration message to a terminal after the terminal has successfully accessed the second cell. The first reconfiguration message includes a source cell configuration release instruction, which is used to command the terminal to release the configuration in the first cell, the first cell being the cell with which the terminal maintains link communication.

[0071] In this information transmission method, during the DAPS handover process, when a terminal maintains link communication with the first cell and successfully accesses the second cell, and then receives the first reconfiguration message sent by the network device of the second cell, the terminal releases the configuration in the first cell based on the source cell configuration release instruction. Therefore, the terminal only needs to retain two sets of configurations: the configuration in the second cell and the configuration in the reconfiguration message sent by the network device of the second cell; it does not need to retain three sets of configurations. In this way, the terminal does not need to allocate memory space for three sets of configurations during the DAPS handover, thereby significantly reducing the complexity of the terminal implementation.

[0072] In one possible design, the first reconfiguration message is the first reconfiguration message that the terminal successfully sent to the second cell after the second cell's network device sent it to the terminal.

[0073] In one possible design, before the network device of the second cell sends the first reconfiguration message to the terminal, the method further includes the step of the network device of the second cell receiving a reconfiguration complete message from the terminal.

[0074] In one possible design, the network device of the second cell sends the first reconfiguration message to the terminal, The step of the second cell's network device sending a first reconfiguration message to the terminal when it sends a handover success instruction to the first cell's network device, or The steps include: the network device of the second cell sends a handover success instruction to the network device of the first cell and then sends a first reconfiguration message to the terminal; The second cell's network device sends a first reconfiguration message to the terminal after receiving an SN status transfer instruction from the first cell's network device, or The second cell's network device sends a first reconfiguration message to the terminal after completing the data transfer, or The second cell's network device sends a first reconfiguration message to the terminal before sending a path switching request message, or The second cell's network device sends a first reconfiguration message to the terminal when it sends a path switching request message, or The second cell's network device sends a first reconfiguration message to the terminal after sending a path switching request message, or The second cell's network device sends a first reconfiguration message to the terminal after receiving an end marker, or The second cell's network device sends a first reconfiguration message to the terminal after receiving a path switching request acknowledgment message, or The process includes the step of the network device of the second cell sending a first reconfiguration message to the terminal before the network device of the first cell sends a terminal context release message.

[0075] This design provides multiple opportunities for the network device in the second cell to send the first reconfiguration message to the terminal.

[0076] According to the 17th aspect, one embodiment of the present application provides a communication device. The device has a function to carry out the method according to the 16th aspect described above. The function may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more units or modules corresponding to the function of the method according to the 16th aspect described above.

[0077] For example, the communication device may include a transmitting module configured to send a first reconfiguration message to a terminal after the terminal has successfully accessed a second cell. The first reconfiguration message includes a source cell configuration release instruction, which is used to instruct the terminal to release the configuration in the first cell, the first cell being the cell with which the terminal maintains link communication.

[0078] In one possible design, the first reconfiguration message is the first reconfiguration message that the terminal successfully sent to the second cell after the transmission module.

[0079] In one possible design, the device further includes a receiving module configured to receive a reconfiguration complete message from the terminal.

[0080] In one possible design, the transmitting module specifically sends a first reconfiguration message to the terminal when it sends a handover success instruction to the network device of the first cell, or After sending a handover success instruction to the network device of the first cell, send a first reconfiguration message to the terminal, or After receiving an SN status transfer instruction from the network device of the first cell, send a first reconfiguration message to the terminal, or After completing the data transfer, send a first reconfiguration message to the terminal, or Send a first reconfiguration message to the terminal before sending a path switching request message, or Send a first reconfiguration message to the terminal when sending a path switching request message, or After sending a path switching request message, send a first reconfiguration message to the terminal, or After receiving the end marker, send a first reconfiguration message to the terminal, or After receiving a path switching request acknowledgment message, send a first reconfiguration message to the terminal, or The system is configured to send a first reconfiguration message to the terminal before sending a terminal context release message to the network device of the first cell.

[0081] According to the 18th aspect, one embodiment of the present application further provides a communication device including a processor configured to execute computer instructions stored in memory. When the computer instructions are executed, the device is enabled to perform a method according to the 16th aspect or any one of a possible design of the 16th aspect.

[0082] According to the 19th aspect, one embodiment of the present application further provides a communication device including a processor and an interface circuit. The processor is configured to communicate with another device via the interface circuit and to perform a method according to the 16th aspect or any one of a possible design of the 16th aspect.

[0083] The communication devices in the 17th to 19th embodiments may be applied to network devices, such as target base stations.

[0084] According to the 20th aspect, one embodiment of the present application further provides a computer-readable storage medium containing computer software instructions. When the computer software instructions operate in a network device or a chip embedded in a network device, the network device is enabled to perform the method according to the 16th aspect.

[0085] For beneficial effects that can be achieved in the 17th through 20th embodiments, it will be understood that we should refer to the beneficial effects in the 16th embodiment and any one of the possible designs of the 16th embodiment. Further details will not be provided here.

[0086] According to the 21st aspect, one embodiment of the present application provides an information transmission method. The method includes the steps of: a terminal maintaining link communication with a first cell and successfully accessing a second cell; the terminal receiving a reconfiguration message from a network device of the first cell; and the terminal deciding to leave the configuration in the first cell unchanged or not to perform a reconfiguration based on the reconfiguration message.

[0087] In this information transmission method, during the DAPS handover process, when a terminal maintains link communication with the first cell and successfully accesses the second cell, and then receives a reconfiguration message sent by the network device of the first cell, the terminal decides not to perform reconfiguration based on the reconfiguration message, i.e., ignores the reconfiguration message. Therefore, the terminal only needs to maintain two sets of configurations: the configuration in the first cell and the configuration in the second cell; it does not need to maintain three sets of configurations. In this way, the terminal does not need to allocate memory space for three sets of configurations during DAPS handover, thereby significantly reducing the complexity of the terminal implementation.

[0088] In one possible design, the method further includes the step of the terminal sending a reconfiguration error message to the network device of the first cell.

[0089] In one possible design, the step of a terminal maintaining link communication with a first cell and successfully accessing a second cell includes, in the DAPS handover process, the step of the terminal receiving a handover command from a network device in the first cell, and the step of the terminal maintaining link communication with the first cell and successfully accessing a second cell based on the handover command.

[0090] In one possible design, the step of the terminal successfully accessing the second cell includes the step of the terminal synchronizing with the second cell and sending a reconfiguration complete message to the network device of the second cell.

[0091] According to a 22nd aspect, one embodiment of the present application provides a communication device that can be applied to a terminal. The device has a function to carry out the method according to the 21st aspect described above. The function may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more units or modules corresponding to the function of the method according to the 21st aspect described above.

[0092] For example, the communication device may include an access module configured to maintain link communication between a terminal and a first cell and to access a second cell successfully; a receiving module configured to receive a first reconfiguration message from a network device in the first cell; and an access module further configured to decide whether to leave the configuration of the terminal in the first cell unchanged or not to perform a reconfiguration based on the reconfiguration message.

[0093] In one possible design, the device further includes a transmit module configured to send reconfiguration error messages to the network device of the first cell.

[0094] In one possible design, during the DAPS handover process, the receiving module is further configured to receive handover commands from the network device of the first cell, and the access module is configured to maintain link communication between the terminal and the first cell based on the handover commands and to successfully access the second cell.

[0095] In one possible design, the access module is configured to control the terminal to synchronize with the second cell and send a reconfiguration complete message to the network device of the second cell.

[0096] According to a 23rd aspect, one embodiment of the present application further provides a communication device including a processor configured to execute computer instructions stored in memory. When the computer instructions are executed, the device is enabled to perform a method according to the 21st aspect or any one of a possible design of the 21st aspect.

[0097] According to the 24th aspect, one embodiment of the present application further provides a communication device including a processor and an interface circuit. The processor is configured to communicate with another device via the interface circuit and to perform a method according to the 21st aspect or any one of a possible design of the 21st aspect.

[0098] The communication devices in the 22nd to 24th embodiments may be applied to terminals.

[0099] According to a 25th aspect, one embodiment of the present application further provides a computer-readable storage medium containing computer software instructions. When the computer software instructions operate in a terminal or a chip embedded in a terminal, the terminal is enabled to perform the method according to the 21st aspect.

[0100] For beneficial effects that can be achieved in the 22nd through 25th embodiments, it will be understood that we should refer to the beneficial effects in the 21st embodiment and any one of the possible designs of the 21st embodiment. Further details will not be provided here.

[0101] According to the 26th aspect, one embodiment of the present application provides an information transmission method. The method includes the step of sending a source cell configuration release message to a terminal when the network device of the second cell sends a handover success instruction to the network device of the first cell after the terminal has successfully accessed the second cell, wherein the first cell is a cell with which the terminal maintains link communication, or The second cell's network device sends a source cell configuration release message to the terminal after sending a handover success instruction to the first cell's network device, or The second cell's network device sends a source cell configuration release message to the terminal after receiving an SN status transfer instruction from the first cell's network device, or The second cell's network device sends a source cell configuration release message to the terminal after completing the data transfer, or The second cell's network device sends a source cell configuration release message to the terminal before sending a path switching request message, or The second cell's network device sends a source cell configuration release message to the terminal when it sends a path switching request message, or The second cell's network device sends a source cell configuration release message to the terminal after sending a path switching request message, or The second cell's network device sends a source cell configuration release message to the terminal after receiving the end marker, or The second cell's network device sends a source cell configuration release message to the terminal after receiving a path switching request acknowledgment message, or The process includes the step of the network device of the second cell sending a source cell configuration release message to the terminal before the network device of the first cell sends a terminal context release message.

[0102] The source cell configuration release message is used to instruct the terminal to release the configuration in the first cell.

[0103] The method provides the second cell's network device with multiple earlier opportunities to send a source cell configuration release message to the terminal, allowing subsequent reconfiguration messages (either sent by the first cell's network device or by the second cell's network device) to be sent more flexibly and reducing the complexity of the terminal implementation.

[0104] According to the 27th aspect, one embodiment of the present application provides a communication device that can be applied to a network device. The device has a function to carry out the method according to the 26th aspect described above. The function may be implemented by hardware, or by hardware running corresponding software. The hardware or software includes one or more units or modules corresponding to the function of the method according to the 26th aspect described above.

[0105] For example, when a communication device sends a handover success instruction to the network device of the first cell after the terminal has successfully accessed the second cell, it sends a source cell configuration release message to the terminal, and the first cell is the cell that the terminal maintains link communication with, or After sending a handover success instruction to the network device of the first cell, send a source cell configuration release message to the terminal, or After receiving an SN status transfer instruction from the network device of the first cell, send a source cell configuration release message to the terminal, or After completing the data transfer, send a source cell configuration release message to the terminal, or Send a source cell configuration release message to the terminal before sending a path switching request message, or When sending a path switching request message, send a source cell configuration release message to the terminal, or After sending a path switching request message, send a source cell configuration release message to the terminal, or After receiving the end marker, send a source cell configuration release message to the terminal, or After receiving a path switching request acknowledgment message, send a source cell configuration release message to the terminal, or The system may include a send module configured to send a source cell configuration release message to the terminal before sending a terminal context release message to the network device of the first cell.

[0106] The source cell configuration release message is used to instruct the terminal to release the configuration in the first cell.

[0107] According to the 28th aspect, one embodiment of the present application further provides a communication device including a processor configured to execute computer instructions stored in memory. When the computer instructions are executed, the device is enabled to perform a method according to the 26th aspect or any one of a possible design of the 26th aspect.

[0108] According to the 29th aspect, one embodiment of the present application further provides a communication device including a processor and an interface circuit. The processor is configured to communicate with another device via the interface circuit and to perform a method according to the 26th aspect or any one of a possible design of the 26th aspect.

[0109] The communication devices in the 27th to 29th embodiments may be applied to network devices.

[0110] According to the 30th aspect, one embodiment of the present application further provides a computer-readable storage medium containing computer software instructions. When the computer software instructions operate in a network device or a chip embedded in a network device, the network device is enabled to perform the method according to the 26th aspect.

[0111] For beneficial effects that can be achieved in the 27th through 30th embodiments, it will be understood that we should refer to the beneficial effects in the 26th embodiment and any one of the possible designs of the 26th embodiment. Further details will not be provided here.

[0112] According to the 31st aspect, one embodiment of the present application further provides a communication device including a transceiver unit and a processing unit. The transceiver unit may be configured to transmit and receive information or to communicate with another network element. The processing unit may be configured to process data. For example, the device may, via the transceiver unit and the processing unit, implement a method according to any one of the first, sixth, eleventh, sixteenth, twentieth, or twenty-sixth aspects.

[0113] According to the 32nd aspect, one embodiment of the present application further provides a computer program product. When executed, the computer program product may implement a method according to any one of the first, sixth, eleventh, sixteenth, twentieth, or twenty-sixth aspects.

[0114] According to the 33rd aspect, one embodiment of the present application further provides a chip system. The chip system is applied to a terminal and comprises one or more interface circuits and one or more processors, the interface circuits and processors being interconnected via lines, and the processors receiving and executing computer instructions from the memory of an electronic device via the interface circuits in order to carry out a method according to any one of the first, 11th, or 21st aspects.

[0115] According to the 34th aspect, one embodiment of the present application further provides a chip system. The chip system is applied to a network device and comprises one or more interface circuits and one or more processors, the interface circuits and processors being interconnected via lines, and the processors receiving and executing computer instructions from the memory of an electronic device via the interface circuits in order to carry out a method according to any one of the sixth, sixteenth, or twenty-sixth aspects.

[0116] For beneficial effects that can be achieved in the 31st to 34th embodiments, it will be understood that we should refer to the beneficial effects in the 1st, 6th, 11th, 16th, 21st, or 26th embodiments. Further details will not be provided here.

[0117] According to the 35th aspect, one embodiment of the present application further provides a communication system including a network device and a terminal. The terminal performs the method according to the first aspect, and the network device performs the method according to the sixth aspect.

[0118] According to the 36th aspect, one embodiment of the present application further provides a communication system including a network device and a terminal. The terminal operates according to the method of the 11th aspect, and the network device operates according to the method of the 16th aspect. Alternatively, the terminal operates according to the method of the 21st aspect.

[0119] For beneficial effects that can be achieved in the 35th embodiment, refer to the beneficial effects in the 1st and 6th embodiments, and for beneficial effects that can be achieved in the 36th embodiment, refer to the beneficial effects in the 11th, 16th, and 21st embodiments. Further details will not be explained again here. [Brief explanation of the drawing]

[0120] [Figure 1] This is a schematic diagram of DAPS handover. [Figure 2] This is a schematic flowchart of the UE capability inquiry process. [Figure 3] This is a schematic diagram of a communication system according to one embodiment of the present application. [Figure 4] This is a schematic diagram of a network device according to one embodiment of this application. [Figure 5] This is a schematic flowchart of an information transmission method according to one embodiment of this application. [Figure 5A] This is a schematic diagram of capability information according to one embodiment of the present application. [Figure 6] This is a schematic flowchart of an existing DAPS handover. [Figure 7] This is another schematic flowchart of an information transmission method according to one embodiment of this application. [Figure 8] This is yet another schematic flowchart of an information transmission method according to one embodiment of this application. [Figure 9] This is yet another schematic flowchart of an information transmission method according to one embodiment of this application. [Figure 10] This is yet another schematic flowchart of an information transmission method according to one embodiment of this application. [Figure 11] This is yet another schematic flowchart of an information transmission method according to one embodiment of this application. [Figure 12] This is yet another schematic flowchart of an information transmission method according to one embodiment of this application. [Figure 13] This is yet another schematic flowchart of an information transmission method according to one embodiment of this application. [Figure 14] This is yet another schematic flowchart of an information transmission method according to one embodiment of this application. [Figure 15] This is yet another schematic flowchart of an information transmission method according to one embodiment of this application. [Figure 16] This is a schematic diagram of the structure of a communication device according to one embodiment of this application. [Figure 17] This is a schematic diagram of another structure of a communication device according to one embodiment of this application. [Figure 18] This is a schematic diagram of yet another structure of a communication device according to one embodiment of this application. [Figure 19] This is a schematic diagram of yet another structure of a communication device according to one embodiment of this application. [Figure 20] This is a schematic diagram of yet another structure of a communication device according to one embodiment of this application. [Figure 21] This is a schematic diagram of yet another structure of a communication device according to one embodiment of this application. [Figure 22] This is a schematic diagram of yet another structure of a communication device according to one embodiment of this application. [Modes for carrying out the invention]

[0121] The concept of dual active protocol stack (DAPS) handover has been introduced in the 5th-generation (5G) mobile communication standard R16. DAPS handover means that, during the handover process from a source cell to a target cell, user equipment (UE) maintains connectivity to both the source cell and the target cell to which the user equipment is to be handed over, and does not release the link to the source cell until the link with the target cell is successfully established.

[0122] For example, Figure 1 is a schematic diagram of a DAPS handover.

[0123] As shown in Figure 1, there is link communication between the UE and the source cell before the DAPS handover takes place. During the DAPS handover process, the UE maintains connections to both the source cell and the target cell. That is, during the process of accessing the target cell, the UE maintains link communication with the source cell. After the UE has successfully accessed the target cell and established a link with it, i.e., after the DAPS handover is complete, the UE releases the link with the source cell.

[0124] DAPS handover can reduce the downtime caused by the UE handover process and improve the reliability of UE handover.

[0125] Before initiating a DAPS handover, a network device (e.g., a source base station corresponding to a source cell) needs to know whether the UE supports DAPS capabilities and the DAPS specification parameters supported by the UE. The network device will only initiate a DAPS handover if it determines that the UE supports DAPS capabilities. In other words, before initiating a DAPS handover, the network device must first obtain information on the DAPS capabilities supported by the UE. For example, the network device may obtain the DAPS capabilities supported by the UE by using the UE capability query procedure.

[0126] The following describes the UE capability query procedure and the process by which network devices obtain DAPS capabilities supported by the UE by using the UE capability query procedure in current technology.

[0127] A UE capability query means that after the UE establishes an initial connection to the network device, the network device sends a capability query signaling signal to the UE. Upon receiving the capability query signaling signaling signal, the UE returns to the network device the capabilities supported by the UE.

[0128] For example, Figure 2 is a schematic flowchart of the UE capability inquiry process.

[0129] As shown in Figure 2, the UE capability inquiry procedure may include S201 and S202.

[0130] S201: The network device sends a capability inquiry signaling to the UE.

[0131] In one possible design, capability inquiry signaling could be "UECapabilityEnquiry".

[0132] In response, the UE receives capability inquiry signaling from the network device.

[0133] S202:UE transmits capability information to network devices.

[0134] In one possible design, the UE could send capability information to network devices by using the signaling "UECapabilityInformation".

[0135] Optionally, in the aforementioned UE capability inquiry process, a network device may request the UE to demonstrate capability in multiple standards by using the signaling "UECapabilityEnquiry". In response, the UE may return the capability corresponding to the standards requested by the network device to the network device by using the signaling "UECapabilityInformation".

[0136] For example, the signaling "UECapabilityEnquiry" sent to the UE by a network device may include a "reqRatList" field. If the "reqRatList" field requests 5G standard capabilities, for example, if the "reqRatList" field includes an "Nr-rat" field, then the capability information reported by the UE to the network device must include the 5G standard capabilities supported by the UE. For example, to report the 5G standard capabilities supported by the UE, a "UE-NR-Capability" field may be added to the signaling "UECapabilityInformation".

[0137] Alternatively, if the capability of a 4G-5G hybrid networking standard is required in the "reqRatList" field, for example, if the "reqRatList" field includes the "Eutra-Nr-rat" field, then the capability information reported by the UE to the network device must include the capability of a 4G-5G hybrid networking standard supported by the UE. For example, to report the capability of a 4G-5G hybrid networking standard supported by the UE, the "UE-MRDC-Capability" field may be added to the signaling "UECapabilityInformation".

[0138] Alternatively, if 4G standard capabilities are required in the "reqRatList" field, for example, if the "reqRatList" field includes the "Eutra-rat" field, the capability information reported by the UE to the network device must include the capabilities of the 4G standard supported by the UE. For example, to report the capabilities of the 4G standard supported by the UE, the "UE-EUTRA-Capability" field may be added to the signaling "UECapabilityInformation".

[0139] By using an example where capability information includes the capabilities of 5G standards supported by the UE, the "UE-NR-Capability" field primarily includes fields such as "Phy-Parameters", "RF-Parameters", "PDCP-Parameters", "RLC-Parameters", "MAC-Parameters", and "featureSetCombinations".

[0140] The "Phy-Parameters" field contains the UE's physical parameters, the "RF-Parameters" field contains the UE's radio frequency (RF) parameters, the "PDCP-Parameters" field contains the UE's packet data convergence protocol (PDCP) parameters, the "RLC-Parameters" field contains the UE's radio link control (RLC) parameters, and the "MAC-Parameters" field contains the UE's medium access control (MAC) parameters.

[0141] The "featureSetCombinations" field contains multiple "featureSetCombinations" fields. Each "featureSetCombinations" field corresponds to one or more band combinations, and different "featureSetCombinations" fields correspond to different band combinations.

[0142] The RF parameters of the UE included in the "RF-Parameters" field may include a support band combination list supported by the UE, and the fields of the list may be represented as "supportBandCombinationList". The band combination list may include multiple band combinations, and the fields of multiple band combinations may be represented as "BandCombination1", "BandCombination2", "BandCombination3", etc. The fields of each band combination may include fields such as "bandlist", "caParametersNR", and "featureSetCombinationID". The "bandList" field represents information about each band that makes up the band combination, such as the band ID and the bandwidth class. The "caParametersNR" field represents the capability parameters related to carrier aggregation of NR Bands. The "featureSetCombinationID" field corresponds to the "featureSetCombination" field that corresponds to the band combination.

[0143] The "featureSetCombination" field contains specific parameters for each band in the corresponding band combination. For example, specific parameters for band 1 may be represented using the "FeatureSetPerBand(Band_1)" field, and specific parameters for band 2 may be represented using the "FeatureSetPerBand(Band_2)" field.

[0144] Each "FeatureSetPerBand" field may further contain "FeatureSetDownLink" and "FeatureSetUpLink" fields. For example, the "FeatureSetPerBand->FeatureSetDownLink" field indicates the downlink parameter of the bandwidth, and the "FeatureSetPerBand->FeatureSetUpLink" field indicates the uplink parameter of the bandwidth.

[0145] Each "FeatureSetDownLink" field may further contain a "FeatureSetListPerDownLinkCC" field. For example, the "FeatureSetDownLink->FeatureSetListPerDownLinkCC" field shows the downlink parameters for each downlink carrier (CC) in the bandwidth. Each "FeatureSetUpLink" field may further contain a "FeatureSetListPerUpLinkCC" field. For example, the "FeatureSetUpLink->FeatureSetListPerUpLinkCC" field shows the uplink parameters for each uplink carrier in the bandwidth.

[0146] Currently, the main direction of the 3rd generation partnership project (3GPP) standards is to report DAPS capability information supported by the UE by reusing the structure of the "BandCombination" field in the aforementioned UE capability inquiry procedure.

[0147] For example, DAPS capability information primarily includes parameter information for source and target cells, and parameter information for when the UE establishes connections to both source and target cells. Parameter information for source and target cells is reported using the "BandCombination->featureSetCombinationID" field and the corresponding "featureSetCombination" field. Parameter information for when the UE establishes connections to both source and target cells is reported using the "BandCombination->caParametersNR" field and the "BandCombination->bandlist->band" field.

[0148] In the aforementioned method of reporting DAPS capability information by reusing the structure of the "BandCombination" field, it can be seen that the structure of the "BandCombination" field was originally intended for reporting CA capability information. Therefore, when DAPS capability information is reported by reusing the structure of the "BandCombination" field, the DAPS capability information to be reported must be the same as the CA capability information. However, in reality, DAPS capability information may differ from CA capability information, and DAPS capability information that differs from CA capability information cannot be reported using the method of reporting DAPS capability information by reusing the structure of the "BandCombination" field.

[0149] For example, in one possible scheme, DAPS capability information differing from CA capability information could mean that the terminal supports DAPS handover between band A and band B, but does not support carrier aggregation between band A and band B. Alternatively, in another possible scheme, DAPS capability information differing from CA capability information could also mean that under carrier aggregation between band A and band B, the number of uplink multiple-input multiple-output (MIMO) layers for carrier CC1 in band A and carrier CC2 in band B is 1+1. However, during DAPS handover, the number of uplink MIMO layers for carrier CC1 in band A and carrier CC2 in band B is 2+2.

[0150] Please understand that the aforementioned explanation that DAPS competency information differs from CA competency information is merely one example for illustrative purposes.

[0151] Based on this, embodiments of the present application provide an information transmission method. When a terminal (or UE) transmits terminal capability information to a network device after receiving capability inquiry signaling from the network device, the terminal may report DAPS capability information and CA capability information by using two different capability items. For example, the capability information may include a first capability item and a second capability item, the first capability item corresponding to DAPS capability information supported by the terminal and the second capability item corresponding to CA capability information supported by the terminal.

[0152] The second capability item may be the aforementioned "featureSetCombinationID" field. The first capability item may be the "featureSetCombinationDAPS" field, similar to the aforementioned "featureSetCombinationID" field.

[0153] In this information transmission method, DAPS capability information and CA capability information are reported separately using the first capability item and the second capability item. Therefore, DAPS capability information and CA capability information supported by a terminal can be reported separately. Consequently, if the DAPS capability information is the same as or different from the CA capability information, both the CA capability information and the DAPS capability information can be reported to the network device.

[0154] The following describes an example of an information transmission method provided in the embodiment of this application, with reference to the attached drawings.

[0155] In the description of this application, terms such as “first” and “second” are used merely for distinction and descriptive purposes and are not used to specifically limit the features. In the description of embodiments of this application, the term “and / or” describes a relationship between related subjects and indicates that three relationships may exist. For example, A and / or B may indicate three cases: A only exists, both A and B exist, or B only exists. The symbol “ / ” usually indicates an “or” relationship between related subjects. In this application, “at least one” means one or more, and “multiple” means two or more.

[0156] The application scenario for the information transmission method provided in the embodiments of this application may be a communication system. Figure 3 is a schematic diagram of a communication system according to one embodiment of this application.

[0157] As shown in Figure 3, the communication system may include a terminal 310 and a plurality of network devices 320 (for example, network device 1 to network device n).

[0158] Network devices may also be called wireless access network devices or next-generation wireless access network devices. Terminal 310 can communicate with network device 320. Network device 320 may provide functional services such as wireless resource management, quality of service management, and data encryption and compression for terminal 310. Different network devices 320 can communicate with each other via the Xn interface.

[0159] Terminal 320 is located within the coverage of one or more cells (carriers) provided by network device 320, and may have one or more cells serving it. If there are multiple cells serving the terminal, the terminal may operate in a CA, dual connectivity (DC), or cooperative multipoint transmission manner.

[0160] Optionally, the communication system may further include a core network device (not shown) which can communicate with the network device 320 via a next-generation (NG) interface.

[0161] Optionally, the communication system may be a universal mobile telecommunications system (UMTS), a code division multiple access (CDMA) system, a wireless local area network (WLAN) system, a wideband code division multiple access (WCDMA®) system, a long-term evolution (LTE) system, an LTE frequency division duplex (FDD) system, a universal mobile telecommunications system (UMTS), a fifth-generation (5G) communication system, or another wireless communication system using orthogonal frequency division multiplexing (OFDM) technology. This application does not limit the specific type of communication system.

[0162] Optionally, terminal 310 in the communication system may also be called UE, mobile station (MS), mobile terminal (MT), etc. Terminal 310 may be a device that provides voice or data connectivity to a user. For example, terminals include mobile phones ("cellular" phones), cell phones, computers, cordless phones, Session Initiation Protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), laptop computers, handheld communication devices, handheld computing devices, satellite radio devices, wireless modem cards, TV set-top boxes (STBs), customer premise equipment (CPE), wearable devices (e.g., smartwatches, smart bracelets, pedometers), in-vehicle devices (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed rail), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (e.g., refrigerators, televisions, air conditioners, electric meters), intelligent robots, workshop devices, wireless terminals in self-driving, and remote medical surgery. This may include wireless terminals in surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, flying devices (e.g., intelligent robots, hot air balloons, unmanned aerial vehicles, aircraft), and other devices configured to communicate using wireless systems. The application does not limit the specific representation of terminal 310.

[0163] In some embodiments, the network device 320 may be a next-generation node B (gNB), an evolved Node B (eNB), a next-generation evolved node B (ng-eNB), a transmission reception point (TRP), a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved Node B or home Node B, HNB), a base band unit (BBU), a wireless fidelity (Wi-Fi) access point (AP), a central unit (CU), a distributed unit (DU), a central unit-control plane (CU-CP), a central unit-user plane (CU-UP), and the like.

[0164] The gNB provides the terminal 310 with the protocols and functions of the new radio (NR) control plane and / or user plane, and can access the 5G core network (5th generation core, 5GC).

[0165] ng-eNB provides terminal 310 with protocols and functions for an evolved universal terrestrial radio access (E-UTRA) control plane and / or user plane, and can access 5GC.

[0166] CU primarily consists of the RRC layer, Service Data Adaptation Protocol (SDAP) layer, and Packet Data Convergence Protocol (PDCP) layer of gNB, or the RRC and PDCP layers of ng-eNB.

[0167] DU primarily includes the radio link control (RLC) layer, medium access control (MAC) layer, and physical layer protocols of gNB or ng-eNB.

[0168] CU-CP primarily consists of the RRC layer within the gNB-CU or ng-eNB-CU and the control plane in the PDCP layer.

[0169] CU-UP primarily consists of the SDAP layer within the gNB-CU or ng-eNB-CU and the user plane in the PDCP layer.

[0170] The aforementioned communication system shown in Figure 3 is intended solely to more clearly illustrate the technical solution in the embodiments of this application and is not intended to constitute a limitation on the technical solution provided in the embodiments of this application. For example, the communication system may further include another device, such as a network control device. The network control device may be an operation administration and maintenance (OAM) system, also known as a network management system. The network control device may manage the aforementioned network device 320.

[0171] Furthermore, those skilled in the art will understand that the technical solutions provided in the embodiments of this application will also be applicable to similar technical problems as network architectures evolve and new service scenarios emerge.

[0172] Figure 4 is a schematic diagram of a network device according to one embodiment of the present application. The network device may be the network device 320 in the aforementioned communication system shown in Figure 3. As shown in Figure 4, the network device may include at least one processor 41, memory 42, communication interface 43, and bus 44.

[0173] The following describes each component of the network device in detail, referring to Figure 4.

[0174] The processor 41 is the control center of the network device and may be a single processor or a collective term for multiple processing elements. For example, the processor 41 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that implement this embodiment of the present application, such as one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs).

[0175] The processor 41 can operate or execute software programs stored in memory 42 and retrieve data stored in memory 42 to perform various functions of the network device.

[0176] In one embodiment, the processor 41 may include one or more CPUs, for example, CPU0 and CPU1 shown in Figure 4.

[0177] In a specific embodiment, the network device may include a plurality of processors, for example, processors 41 and 45 shown in Figure 4. Each of the processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). In this specification, a processor may be one or more devices, circuits, and / or processing cores configured to process data (e.g., computer program instructions).

[0178] Memory 42 is configured to store a software program for executing method steps performed by a network device in the solution of this application, and the processor 41 controls its execution. Memory 42 may be read-only memory (ROM) or another type of static storage device capable of storing static information and instructions, or random access memory (RAM) or another type of dynamic storage device capable of storing information and instructions. Alternatively, memory 42 may be, but is not limited to, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or another compact disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital multipurpose discs, Blu-ray optical discs, etc.), magnetic disk storage media or another magnetic storage device, or any other medium accessible by a computer that can be used to carry or store program code expected in the form of instructions or data structures.

[0179] Memory 42 may exist independently and be connected to processor 41 via bus 44. Memory 42 may, but is not limited to, be integrated into processor 41.

[0180] The communication interface 43 communicates with another device or communication network using any device such as a transceiver. The communication interface 43 may be an Ethernet interface, a radio access network (RAN) interface, a wireless local area network (WLAN), etc. The communication interface 43 may include a receiving unit for implementing receiving functions and a transmitting unit for implementing transmitting functions.

[0181] Bus 44 can be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, etc. Buses can be classified into address buses, data buses, control buses, etc. For ease of representation, buses are represented in Figure 4 using only one thick line. However, this does not indicate that there is only one bus or one type of bus.

[0182] While bus 44 is used in Figure 4, it should be understood that the bus can be replaced with a different form of connection and is not limited to the bus itself.

[0183] Optionally, the structure of the terminal 310 in the aforementioned communication system shown in Figure 3 may also include several structures similar to those of the network device shown in Figure 4, such as a processor, memory, communication interface, and bus, in order to realize various functions of the terminal 310. Further details are not described here.

[0184] The following describes an information transmission method provided in one embodiment of this application with reference to Figure 5. Figure 5 is a schematic flowchart of the information transmission method according to one embodiment of this application.

[0185] As shown in Figure 5, the information transmission method may include S501 to S502.

[0186] S501: The network device sends a capability inquiry signal to the terminal.

[0187] The network device is the network device in the aforementioned communication system shown in Figure 3, and may be, for example, a gNB, eNB, or ng-eNB.

[0188] For example, a network device may send a first RRC message to a terminal, and the first RRC message may include capability inquiry signaling.

[0189] In one possible design, capability inquiry signaling could be "UECapabilityEnquiry".

[0190] In response, the terminal receives capability inquiry signaling from the network device.

[0191] After receiving capability inquiry signaling from a network device, the terminal may return capability information supported by the terminal to the network device. For example, S502 may occur.

[0192] S502: The terminal transmits terminal capability information to a network device, the capability information including a first capability item and DAPS capability information corresponding to the first capability item that is supported by the terminal, and a second capability item and CA capability information corresponding to the second capability item that is supported by the terminal.

[0193] In response, the network device receives capability information from the terminal.

[0194] For example, a terminal may send a second RRC message to a network device, the second RRC message may include terminal capability information signaling, and the terminal capability information signaling includes capability information supported by the terminal.

[0195] In one possible design, terminal capability information signaling could be "UECapabilityInformation".

[0196] The following specifically describes capability information sent by a terminal to a network device, using an example where the terminal capability information signaling is "UECapabilityInformation".

[0197] The signaling "UECapabilityInformation" may include fields such as "Phy-Parameters", "RF-Parameters", "PDCP-Parameters", "RLC-Parameters", "MAC-Parameters", and "featureSetCombinations".

[0198] The "Phy-Parameters" field, "RF-Parameters" field, "PDCP-Parameters" field, "RLC-Parameters" field, "MAC-Parameters" field, and "featureSetCombinations" field are the same as the related descriptions above and will not be explained in detail again here.

[0199] For example, as explained above, the "featureSetCombinations" field contains multiple "featureSetCombinations" fields. Each "featureSetCombinations" field corresponds to one band combination, and different "featureSetCombinations" fields correspond to different band combinations.

[0200] Each "featureSetCombination" field contains specific parameters for each band in the corresponding band combination. For example, specific parameters may be represented using the "FeatureSetPerBand" field.

[0201] Each "FeatureSetPerBand" field may further contain "FeatureSetDownLink" and "FeatureSetUpLink" fields. For example, the "FeatureSetPerBand->FeatureSetDownLink" field indicates the downlink parameter of the bandwidth, and the "FeatureSetPerBand->FeatureSetUpLink" field indicates the uplink parameter of the bandwidth.

[0202] Each "FeatureSetDownLink" field may further contain a "FeatureSetListPerDownLinkCC" field. For example, the "FeatureSetDownLink->FeatureSetListPerDownLinkCC" field shows the downlink parameters for each downlink carrier in the bandwidth. Each "FeatureSetUpLink" field may further contain a "FeatureSetListPerUpLinkCC" field. For example, the "FeatureSetUpLink->FeatureSetListPerUpLinkCC" field shows the uplink parameters for each uplink carrier in the bandwidth.

[0203] The difference is that, in this embodiment of the present application, in addition to fields such as the "bandlist" field, "caParametersNR" field and "featureSetCombinationID" field, the "BandCombination" field for each band combination further includes the "featureSetCombinationDAPS" field.

[0204] For example, the following is an example of modifying an abstract syntax notification (ASN) to add a "featureSetCombinationDAPS" field to the "BandCombination" field for each band combination. BandCombination-v16xy::= SEQUENCE{ featureSetCombinationDAPS featureSetCombinationID OPTIONAL }

[0205] ASN is a protocol language widely used in various standard protocols, defining various syntax types and corresponding encoding and decoding rules. According to the 3GPP specification, all standard interfaces at a base station use the ASN protocol for message encoding and decoding. That is, messages tracked in standard interface tracking are all messages obtained after ASN encoding at the base station / core network / terminal. During standard message tracking, a DLL corresponding to a specific interface is called to decode and parse the message.

[0206] The "featureSetCombinationDAPS" field may also be called the first capability item and can correspond to the "featureSetCombination" field contained within the "featureSetCombinations" field. It is used to report DAPS capability information supported by the terminal to network devices. For example, parameter information for source and target cells supported by the terminal may be reported to network devices using the first capability item ("featureSetCombinationDAPS" field) and the corresponding "featureSetCombination" field.

[0207] The "featureSetCombinationID" field may also be called the second capability item and can correspond to the "featureSetCombination" field, which is also included in the "featureSetCombinations" field, and is used to report CA capability information supported by the terminal to network devices. For example, CA capability information supported by the terminal may be reported to network devices by using the second capability item ("featureSetCombinationID" field) and the "featureSetCombination" field corresponding to the second capability item.

[0208] In other words, the DAPS capability information corresponding to the first capability item mentioned above, supported by the terminal, is understood to be one of the "featureSetCombination" fields among the multiple "featureSetCombination" fields contained in the "featureSetCombinations" field, that is, a specific parameter for each band in one of the multiple band combinations. The CA capability information corresponding to the second capability item mentioned above, supported by the terminal, is also one of the "featureSetCombination" fields among the multiple "featureSetCombination" fields contained in the "featureSetCombinations" field, that is, a specific parameter for each band in one of the multiple band combinations.

[0209] Figure 5A is a schematic diagram of capability information according to one embodiment of this application.

[0210] Referring to Figure 5A, featureSetCombinationID is used as an example of the second capability item.

[0211] The second capability item, featureSetCombinationID, is used to identify the specific parameters for each band in a band combination (FeatureSetCombination). For each FeatureSetCombination, the second capability item corresponds to the specific parameters for each band in a band combination (FeatureSetCombination) in a featureSetCombination list or featureSetCombination. Its English description may be as follows: The IE FeatureSetCombinationId identifies a FeatureSetCombination. The FeatureSetCombinationID of a FeatureSetCombination is the position of the FeatureSetCombination in the featureSetCombinations list (in UE-NR-Capability or UE-MRDC-Capability). The FeatureSetCombinationId=0 refers to the first entry in the featureSetCombinations list (in UE-NR-Capability or UE-MRDC-Capability).

[0212] For the first capability item, featureSetCombinationDAPS is used as an example.

[0213] The first capability item, featureSetCombinationDAPS, is used to identify the specific parameters for each band in a band combination (FeatureSetCombination). For each FeatureSetCombination, the first capability item corresponds to the specific parameters for each band in a band combination (FeatureSetCombination) in a multi-band combination (featureSetCombination list or featureSetCombination). Its English description may be as follows: The IE featureSetCombinationDAPS identifies a FeatureSetCombination. The featureSetCombinationDAPS of a FeatureSetCombination is the position of the FeatureSetCombination in the featureSetCombinations list. The featureSetCombinationDAPS=0 refers to the first entry in the featureSetCombinations list.

[0214] Optionally, DAPS capability information corresponding to the first capability item (featureSetCombinationDAPS) supported by the terminal may be present in UE-NR-Capability or UE-MRDC-Capability.

[0215] The DAPS capability information corresponding to the first capability item supported by the terminal is either a specific parameter for each band in one of several band combinations, or the CA capability information corresponding to the second capability item supported by the terminal is a specific parameter for each band in one of several band combinations.

[0216] Specifically, "a specific parameter for each band in one of several band combinations" refers to a FeatureSetCombination, and "multiple band combinations" can refer to a featureSetCombination. The "featureSetCombinations" field contains multiple "featureSetCombination" fields. Each "featureSetCombination" field corresponds to one or more band combinations, and different "featureSetCombination" fields correspond to different band combinations.

[0217] In this invention, featureSetCombinations is synonymous with featureSetCombination list.

[0218] For example, the first capability item includes the first capability item 1 (featureSetCombinationDAPS_1), the first capability item 2 (featureSetCombinationDAPS_2), and the first capability item 3 (featureSetCombinationDAPS_3). The "Specific parameters for each band in the band combination" (FeatureSetCombination) corresponding to the first capability item 1 (featureSetCombinationDAPS_1) corresponds to the "Specific parameters for each band in the band combination" (FeatureSetCombination) in the featureSetCombination list (in position of).

[0219] Alternatively, the first capability item includes the first capability item 1 (featureSetCombinationDAPS_1), the first capability item 2 (featureSetCombinationDAPS_2), and the first capability item 3 (featureSetCombinationDAPS_3). The "Specific parameters for each band in the band combination" (FeatureSetCombination) corresponding to the first capability item 1 (featureSetCombinationDAPS_1) corresponds to the "Specific parameters for each band in the band combination" (FeatureSetCombination) within featureSetCombinations (in position of).

[0220] Optionally, parameter information when the terminal establishes a connection to both the source and target cells can also be reported using the "BandCombination->caParametersNR" field and the "BandCombination->bandlist->band" field.

[0221] In one possible design, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first and second capability items correspond to specific parameters for each band in different band combinations. If the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first and second capability items correspond to specific parameters for each band in the same band combination.

[0222] Alternatively, in another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first and second capability items may also correspond to specific parameters of each band in different band combinations. The first and second capability items correspond to specific parameters of each band in different band combinations, but the specific parameters of each band in the band combinations corresponding to the first and second capability items may be the same. That is, the “featureSetCombinations” field may contain two “featureSetCombination” fields having the same content, and the first and second capability items correspond separately to one of the two fields. This is not limited to the present application.

[0223] As described above, in the information transmission method provided in this embodiment of the present application, the terminal capability information transmitted by the terminal to the network device after receiving capability inquiry signaling from the network device includes a first capability item and dual-active protocol stack (DAPS) capability information supported by the terminal corresponding to the first capability item, and a second capability item and carrier aggregation (CA) capability information supported by the terminal corresponding to the second capability item, so that the DAPS capability information and CA capability information supported by the terminal can be reported separately. Compared to current technology, the decoupling between the DAPS capability information and CA capability information supported by the terminal is implemented so that both the CA capability information and the DAPS capability information can be reported to the network device if the DAPS capability information is the same as or different from the CA capability information.

[0224] In one possible design, considering that DAPS may require some dedicated per-band granularity capabilities and per-carrier granularity capabilities, several DAPS-specific capability extensions may be added to the "FeatureSetDownLink" and "FeatureSetUpLink" fields within each "FeatureSetPerBand" field, as well as the "FeatureSetListPerDownLinkCC" and "FeatureSetListPerUpLinkCC" fields.

[0225] For example, the ASN can be modified according to the following example. FeatureSetDownLink-v16xy::= SEQUENCE{ dapsDownLinkParam DapsDownLinkParam OPTIONAL featureSetListPerDownlinkCCDAPS SEQUENCE(SIZE(1..maxNrofServingCells))OF featureSetPerCCDAPS OPTIONAL } FeatureSetUpLink-v16xy::= SEQUENCE{ dapsUpLinkParam DapsUpLinkParam OPTIONAL featureSetListPerUplinkCCDAPS SEQUENCE(SIZE(1..maxNrofServingCells))OF featureSetPerCCDAPS OPTIONAL }

[0226] In other words, in the structure of FeatureSetDownLink-v16xy, the new capability item dapsDownLinkParam may be extended to report downlink DAPS capability at PerBand granularity, and the new capability item featureSetListPerDownlinkCCDAPS may be extended to report downlink DAPS capability at PerCC granularity. In the structure of FeatureSetUpLink-v16xy, the new capability item dapsUpLinkParam is extended to report uplink DAPS capability at PerBand granularity, and the new capability item featureSetListPerUplinkCCDAPS is extended to report uplink DAPS capability at PerCC granularity.

[0227] In response to this, the capability information transmitted by the terminal to the network device includes, as supported by the terminal, DAPS capability information corresponding to the first capability item, including uplink DAPS capability and downlink DAPS capability at a bandwidth-level granularity, as well as uplink DAPS capability and downlink DAPS capability at a carrier-level granularity.

[0228] "Uplink DAPS capability at the granularity per bandwidth" can also be called "uplink DAPS capability per bandwidth," and specifically refers to uplink DAPS capability based on perband granularity, or uplink DAPS capability based on perband.

[0229] "Downlink DAPS capability at the granularity per bandwidth" can also be called "downlink DAPS capability per bandwidth," and specifically refers to downlink DAPS capability based on per-band granularity, or downlink DAPS capability based on per-band.

[0230] "Uplink DAPS capability at the carrier-specific granularity" can also be called "uplink DAPS capability per carrier," and specifically refers to uplink DAPS capability based on carrier-specific granularity, uplink DAPS capability based on each carrier, or uplink DAPS capability based on per CC.

[0231] "Downlink DAPS capability at the carrier-specific granularity" can also be called "downlink DAPS capability at the carrier-specific granularity," and specifically, carrier Each Downlink DAPS capability based on granularity, carrier each This refers to downlink DAPS capability based on or based on per CC.

[0232] As described above, after obtaining the terminal's DAPS capability information, the network device may initiate a DAPS handover of the terminal.

[0233] The following briefly describes the procedure for a terminal to perform a DAPS handover using current technology, with reference to Figure 6. Figure 6 is a schematic flowchart of an existing DAPS handover.

[0234] As shown in Figure 6, the existing DAPS handover procedure may include steps S601 through S614.

[0235] S601: The terminal measures the target cell and sends a report to the source base station.

[0236] The reports transmitted by the terminal to the source base station include events such as the current serving source cell's signal strength being below a threshold and the target cell's signal strength being above a threshold, as well as other events.

[0237] In response, the source base station receives the report from the terminal.

[0238] S602: The source base station decides to perform a terminal handover based on the report.

[0239] S603: The source base station sends a handover request message to the target base station.

[0240] The target base station is the base station corresponding to the aforementioned target cell.

[0241] S604: The target base station decides to grant access to the terminal.

[0242] For example, the target base station may decide whether to grant access to the terminal based on factors such as the number of connections to the target base station, and if access is granted to the terminal, it may send a handover acknowledgment message to the source base station.

[0243] S605: The target base station sends a handover request acknowledge message to the source base station.

[0244] In response, the source base station receives a handover request acknowledgment message from the target base station.

[0245] S606: The source base station sends a handover command to the terminal.

[0246] In response to this, Terminal devices The device receives a handover command. The handover command may include relevant information about the target cell and relevant configuration parameters necessary for the device to access the target cell.

[0247] S607: The terminal maintains link communication with the source cell based on the handover command and synchronizes with the target cell.

[0248] For example, a terminal may initiate random access to a target base station in order to complete configuration in the target cell.

[0249] S608: The terminal sends an RRC reconfiguration complete message to the target base station.

[0250] In response, the target base station receives an RRC reconfiguration completion message from the terminal.

[0251] S609: The target base station sends a handover success instruction to the source base station.

[0252] In response, the source base station receives a handover success instruction transmitted by the target base station.

[0253] S610: The source base station sends an SN status transfer instruction to the target base station.

[0254] In response, the target base station receives an SN status transfer instruction.

[0255] The target base station may transfer user data from the terminal based on the SN status transfer instruction.

[0256] S611: The target base station sends a path switch request message to the access and mobility management function (AMF).

[0257] In response, the AMF receives a path switching request message.

[0258] S612:AMF performs path switching using the user plane function (UPF).

[0259] S613: The AMF sends a path switch request acknowledge message to the target base station.

[0260] Correspondingly, the target base station receives a path switching request confirmation response message.

[0261] S614: The target base station sends a UE context release message to the source base station.

[0262] Correspondingly, the source base station receives the UE context release message and releases the UE context information.

[0263] According to the foregoing content, the terminal completes the handover by performing the foregoing steps, and the target base station also implements the path switching procedure for the terminal handover on the core network side, so that the terminal data is sent from the gateway to the terminal via the target base station.

[0264] After S614 is completed, the terminal may basically be considered to have completed the handover. In this case, the terminal does not need to remember the configuration of the source cell (also referred to as the configuration used by the terminal in the source cell), and there is no need to maintain the link between the terminal and the source cell. Therefore, step S615: The target base station sends a source cell configuration release message to the terminal, may exist.

[0265] The source cell configuration release message is used to instruct the terminal to release the configuration in the source cell.

[0266] Correspondingly, the terminal receives the source cell configuration release message and releases the source configuration in the source cell.

[0267] In the aforementioned DAPS handover procedure, during the period (generally several seconds or milliseconds) after the terminal has successfully accessed the target cell but has not received a source cell configuration release message (e.g., a release message) sent by the target base station, i.e., within the period from after S608 to before S615 as shown in Figure 6, the terminal may receive a reconfiguration message sent by the source base station or the target base station.

[0268] If the terminal receives a reconfiguration message transmitted by the source base station within this period, the terminal retains three sets of configurations: the configuration in the source cell, the configuration in the target cell, and the configuration in the reconfiguration message transmitted by the source base station. If the terminal receives a reconfiguration message transmitted by the target base station within this period, the terminal also retains three sets of configurations: the configuration in the source cell, the configuration in the target cell, and the configuration in the reconfiguration message transmitted by the target base station.

[0269] In the aforementioned case where the terminal maintains three sets of configurations, the terminal now needs to reserve memory space for the three sets of configurations during a DAPS handover. However, this significantly increases the complexity of the terminal implementation and imposes relatively high requirements on the terminal implementation.

[0270] Based on this, in a scenario in which a terminal can receive a reconfiguration message sent by a target base station during the period after the terminal has successfully accessed a target cell but has not received a source cell configuration release message sent by the target base station, one embodiment of the present application provides an information transmission method that can simplify the complexity of the terminal implementation.

[0271] The following describes the information transmission method using an example in which the source cell is the first cell, the source base station is the network device of the first cell, the target cell is the second cell, and the target base station is the network device of the second cell.

[0272] In one possible design, the method includes the following: during the DAPS handover process, when the terminal maintains link communication with the first cell and successfully accesses the second cell, the network device of the second cell sends a reconfiguration message to the terminal, the first reconfiguration message may include a source cell configuration release instruction. The terminal may release the configuration in the first cell based on the source cell configuration release instruction.

[0273] For example, Figure 7 is another schematic flowchart of an information transmission method according to one embodiment of this application.

[0274] As shown in Figure 7, in this design, the information transmission method may include the following steps.

[0275] S701: The network device in the first cell sends a handover command to the terminal.

[0276] In response, the terminal receives a handover command from the network device of the first cell. The handover command includes relevant parameter information for the second cell.

[0277] S702: The terminal maintains link communication with the first cell and synchronizes with the second cell based on the handover command.

[0278] For example, in order to complete the configuration in the second cell, the terminal may initiate random access to the network devices of the second cell based on a handover command, for example, based on relevant parameter information of the second cell included in the handover command.

[0279] Specifically, the handover command includes a configuration to be used by the terminal in the second cell, and the terminal accesses the second cell based on the terminal's configuration in the second cell within the handover command.

[0280] S703: The terminal sends a reconfiguration complete message to the network device of the second cell.

[0281] In response, the network device in the second cell receives a reconfiguration complete message.

[0282] Through S701 to S703, the terminal maintains link communication with the first cell and successfully accesses the second cell.

[0283] S704: The network device of the second cell sends a first reconfiguration message to the terminal, the first reconfiguration message includes a source cell configuration release instruction (daps-SourceRelease), and the first reconfiguration message is the first reconfiguration message.

[0284] In other words, the first reconfiguration message sent to the terminal by the network device of the second cell includes a source cell configuration release instruction.

[0285] Specifically, a source cell configuration release instruction may be used to command a terminal to stop DAPS processing in the source cell, to command the terminal to release its DAPS configuration in the source cell, or to command the terminal to release the link between the terminal and the source cell. Alternatively, a source cell configuration release instruction may be used to command a terminal to stop DAPS processing in the source cell and to release the terminal's DAPS configuration in the source cell (indicates to UE that the source cell part of DAPS operation is to be stopped and the source cell part of DAPS configuration is to be released).

[0286] Correspondingly, the terminal receives a first reconfiguration message from the network device of the second cell. The first reconfiguration message can be used to instruct the terminal to reconfigure the configuration in the second cell.

[0287] After receiving the first reconfiguration message, the terminal may release the configuration of the terminal in the first cell based on the source cell configuration release instruction included in the first reconfiguration message. After receiving the first reconfiguration message, based on the source cell configuration release instruction included in the first reconfiguration message, the terminal may stop the DAPS process in the source cell, or release the DAPS configuration of the terminal in the source cell, or release the link between the terminal and the source cell, or stop the DAPS process in the source cell and release the DAPS configuration of the terminal in the source cell (Indicates to UE that the source cell part of DAPS operation is to be stopped and the source cell part of DAPS configuration is to be released).

[0288] For example, S705 may be performed.

[0289] S705: The terminal releases the configuration in the first cell based on the source cell configuration release instruction included in the first reconfiguration message.

[0290] Specifically, based on the source cell configuration release instruction contained in the first reconfiguration message, the terminal may release its configuration in the first cell, or the terminal may stop DAPS processing in the source cell, or the terminal may release its DAPS configuration in the source cell, or the terminal may release the link between the terminal and the source cell, or the terminal may stop DAPS processing in the source cell and release its DAPS configuration in the source cell (indicates to UE that the source cell part of DAPS operation is to be stopped and the source cell part of DAPS configuration is to be released).

[0291] Optionally, after S704, the network device of the second cell may send a second reconfiguration message to the terminal, the second reconfiguration message being a reconfiguration message following the first reconfiguration message (first reconfiguration message).

[0292] Alternatively, in another possible design, the method includes the following: in the DAPS handover process, when the terminal maintains link communication with the first cell and successfully accesses the second cell, the network device of the second cell sends a reconfiguration message to the terminal, the first reconfiguration message may not include a source cell configuration release instruction. Upon receiving the first reconfiguration message, the terminal may automatically release its configuration in the first cell.

[0293] For example, Figure 8 is yet another schematic flowchart of an information transmission method according to one embodiment of this application.

[0294] As shown in Figure 8, in this design, the information transmission method may include the following steps.

[0295] S801: The network device in the first cell sends a handover command to the terminal.

[0296] In response, the terminal receives a handover command from the network device of the first cell.

[0297] S802: The terminal maintains link communication with the first cell and synchronizes with the second cell based on the handover command.

[0298] For example, a terminal may initiate random access to the network devices of the second cell based on a handover command in order to complete the configuration in the second cell.

[0299] S803: The terminal sends a reconfiguration complete message to the network device of the second cell.

[0300] In response, the network device in the second cell receives a reconfiguration complete message.

[0301] S801 to S803 allow the terminal to maintain link communication with the first cell and access the second cell successfully.

[0302] S804: The network device in the second cell sends the first reconfiguration message to the terminal.

[0303] In response, the terminal receives a first reconfiguration message from the network device of the second cell. The first reconfiguration message can be used to instruct the terminal to reconfigure the configuration in the second cell.

[0304] After receiving the first reconfiguration message, the terminal may automatically release its configuration in the first cell. For example, S805 may be performed.

[0305] S805: The terminal releases the configuration in the first cell.

[0306] Optionally, after S804, the network device of the second cell may send a second reconfiguration message to the terminal, the second reconfiguration message being a reconfiguration message following the first reconfiguration message (first reconfiguration message).

[0307] It can be seen that the main difference between the embodiment shown in Figure 8 and the embodiment shown in Figure 7 is that, in the embodiment shown in Figure 7, the first reconfiguration message sent to the terminal by the network device of the second cell includes a source cell configuration release instruction, and the terminal can release the configuration in the first cell based on the source cell configuration release instruction, whereas in the embodiment shown in Figure 8, the first reconfiguration message sent to the terminal by the network device of the second cell does not include a source cell configuration release instruction, and the terminal can automatically release the configuration in the first cell after receiving the first reconfiguration message.

[0308] In the information transmission method shown in Figure 7 or Figure 8, during the DAPS handover process, the terminal maintains link communication with the first cell and, after successfully accessing the second cell, releases the configuration in the first cell when it receives the first reconfiguration message sent by the network device of the second cell. Therefore, the terminal only needs to retain two sets of configurations: the configuration in the second cell and the configuration in the reconfiguration message sent by the network device of the second cell; it does not need to retain three sets of configurations. In this way, the terminal does not need to allocate memory space for three sets of configurations during the DAPS handover, thereby significantly reducing the complexity of the terminal implementation.

[0309] In addition, it should be noted that the embodiments shown in Figures 7 and 8 begin with the step in the DAPS handover process where the network device of the first cell (e.g., the source base station) sends a handover command to the terminal. However, as with the embodiment shown in Figure 6, it should be understood that the DAPS handover process includes many other steps, which will not be described again in detail here.

[0310] Optionally, in the embodiments shown in Figures 7 and 8, both the messages between the terminal and the network device of the first cell and the messages between the terminal and the network device of the second cell may be RRC messages. For example, the first cell's network device sending a handover command to the terminal may be done by the first cell's network device sending a handover command to the terminal using RRC messages. The first reconfiguration message sent to the terminal by the second cell's network device may be a first RRC reconfiguration message, etc.

[0311] Figure 9 is another schematic flowchart of an information transmission method according to one embodiment of this application.

[0312] Optionally, as shown in Figure 9, if the first reconstruction message does not include a source cell configuration release instruction based on Figure 8, the information transmission method may further include S901.

[0313] S901: The terminal sends a reconfiguration error message to the network device of the second cell.

[0314] Please note that Figure 9 is merely an example for illustrative purposes, and the order of S901 and S805 is not limited in this application.

[0315] Optionally, if the first reconfiguration message does not include a source cell configuration release instruction, the terminal may also ignore the first reconfiguration message and maintain the configuration in the second cell (leaving the existing configuration in the second cell unchanged). The terminal's configuration in the second cell is the configuration of the second cell included in the handover command from the network device of the first cell when the terminal accesses the second cell. The configuration of the second cell is the configuration used by the terminal in the second cell.

[0316] Alternatively, if the first reconfiguration message does not include a source cell configuration release instruction, the terminal ignores the first reconfiguration message and maintains the configuration in the second cell, and also sends a reconfiguration error message to the network device in the second cell.

[0317] That is, if the first reconfiguration message does not include a source cell configuration release instruction, the terminal may maintain the configuration established in the second cell when the terminal accesses the second cell and / or send a reconfiguration error message to the network device of the second cell. This is not limited to the present application.

[0318] From the embodiments shown in Figures 7 to 9, it can be seen that in the aforementioned solution, which simplifies the complexity of the terminal implementation provided in the embodiments of this application, the terminal does not expect to receive a reconfiguration message that does not include a source cell configuration release instruction.

[0319] In addition, in a scenario in which a terminal can receive a reconfiguration message sent by a source base station during a period after the terminal has successfully accessed a target cell but has not yet received a source cell configuration release message sent by the target base station, one embodiment of the present application further provides an information transmission method that can simplify the complexity of the terminal implementation.

[0320] Similarly, using an example where the source cell is the first cell, the source base station is the network device of the first cell, the target cell is the second cell, and the target base station is the network device of the second cell, the method includes the step in which, in the DAPS handover process, the terminal maintains link communication with the first cell and, after successfully accessing the second cell, the network device of the first cell sends a reconfiguration message to the terminal, and the terminal decides not to perform a reconfiguration based on the reconfiguration message, i.e., the terminal ignores the reconfiguration message sent by the network device of the first cell.

[0321] For example, Figure 10 is yet another schematic flowchart of an information transmission method according to one embodiment of this application.

[0322] As shown in Figure 10, the information transmission method may include the following steps.

[0323] S1001: The network device of the first cell sends a handover command to the terminal.

[0324] In response, the terminal receives a handover command from the network device of the first cell.

[0325] S1002: The terminal maintains link communication with the first cell based on the handover command and synchronizes with the second cell.

[0326] For example, a terminal may initiate random access to the network devices of the second cell in order to complete the configuration in the second cell.

[0327] S1003: The terminal sends a reconfiguration complete message to the network device of the second cell.

[0328] In response, the network device in the second cell receives a reconfiguration complete message.

[0329] From S1001 to S1003, the terminal maintains link communication with the first cell and successfully accesses the second cell.

[0330] S1004: The network device of the first cell sends a reconfiguration message to the terminal.

[0331] In response, the terminal receives a reconfiguration message from the network device of the first cell. The reconfiguration message can be used to instruct the terminal to reconfigure the configuration in the first cell.

[0332] S1005: The terminal decides not to perform a reconfiguration based on the reconfiguration message.

[0333] Alternatively, S1005 may be that the terminal remains unchanged in its configuration within the first cell.

[0334] In this information transmission method, during the DAPS handover process, when a terminal maintains link communication with the first cell and successfully accesses the second cell, and then receives a reconfiguration message sent by the network device of the first cell, the terminal decides not to perform reconfiguration based on the reconfiguration message, i.e., ignores the reconfiguration message. Therefore, the terminal only needs to maintain two sets of configurations: the configuration in the first cell and the configuration in the second cell; it does not need to maintain three sets of configurations. In this way, the terminal does not need to allocate memory space for three sets of configurations during DAPS handover, thereby significantly reducing the complexity of the terminal implementation.

[0335] Figure 11 is another schematic flowchart of an information transmission method according to one embodiment of this application.

[0336] As shown in Figure 11, in one possible design, the information transmission method may further include S1101.

[0337] S1101: The terminal sends a reconfiguration error message to the network device of the first cell.

[0338] Please note that Figure 11 is merely an example for illustrative purposes, and the order of S1005 and S1101 is not limited in this application.

[0339] In addition, it should be noted that the embodiments shown in Figures 10 and 11 begin with the step in the DAPS handover process where the network device of the first cell (e.g., the source base station) sends a handover command to the terminal. As with the embodiment shown in Figure 6, it should be understood that the DAPS handover process also includes many other steps, which are not described again in detail here.

[0340] Optionally, in the embodiments shown in Figures 10 and 11, both the messages between the terminal and the network device of the first cell and the messages between the terminal and the network device of the second cell may also be RRC messages. Further details are not described here.

[0341] Optionally, one embodiment of the present application further provides an information transmission method. In this method, in the DAPS handover process, after the terminal maintains link communication with the first cell and successfully accesses the second cell, the network device of the second cell may send a source cell configuration release message to the terminal at any earlier opportunity within the aforementioned period from after S608 to S614 as shown in Figure 6. This allows subsequent reconfiguration messages (reconfiguration messages sent by the network device of the first cell or by the network device of the second cell) to be sent more flexibly, and also reduces the complexity of the terminal implementation.

[0342] Referring to the attached diagrams, the following also describes, step by step, possible design schemes for the information transmission method, starting from the step in which the network device of the first cell (e.g., the source base station) sends a handover command to the terminal in the DAPS handover process. It should be understood that, as with the embodiment shown in Figure 6, the DAPS handover process may also include many other steps, which will not be described again in detail here.

[0343] Figure 12 is yet another schematic flowchart of an information transmission method according to one embodiment of the present application. As shown in Figure 12, in one possible design, the information transmission method may include S1201 to S1210.

[0344] S1201: The network device in the first cell sends a handover command to the terminal.

[0345] In response, the terminal receives a handover command from the network device of the first cell.

[0346] S1202: The terminal maintains link communication with the first cell and synchronizes with the second cell based on the handover command.

[0347] For example, a terminal may initiate random access to the network devices of the second cell in order to complete the configuration in the second cell.

[0348] S1203: The terminal sends a reconfiguration complete message to the network device of the second cell.

[0349] In response, the network device in the second cell receives a reconfiguration complete message.

[0350] S1204: The network device in the second cell sends a handover success instruction to the network device in the first cell.

[0351] In response, the network device in the first cell receives a handover success instruction.

[0352] S1205: The network device of the second cell sends a source cell configuration release message to the terminal.

[0353] In one embodiment, S1204 may be executed before S1205. That is, the network device of the second cell sends a handover success instruction to the network device of the first cell and then sends a source cell configuration release message to the terminal.

[0354] In another embodiment, S1204 and S1205 may occur simultaneously. That is, the network device of the second cell sends a source cell configuration release message to the terminal when it sends a handover success instruction to the network device of the first cell.

[0355] In response, the terminal receives a source cell configuration release message. Based on the source cell configuration release message, the terminal may release the configuration in the first cell.

[0356] S1206: The network device in the first cell sends an SN status forwarding instruction to the network device in the second cell.

[0357] An SN status transfer instruction may also be called an SN status transfer message. An SN status transfer message or SN status transfer instruction is used to indicate the status information of the SN (sequence numbers) of the DRB where the DAPS handover is taking place. SN is the sequential data packet number of each DRB at the DPCP layer.

[0358] In response, the network device in the second cell receives an SN status forwarding instruction.

[0359] The network device in the second cell may transfer terminal user data based on an SN status transfer instruction.

[0360] S1207: The network device in the second cell sends a path switching request message to the AMF.

[0361] In response, the AMF receives a path switching request message.

[0362] S1208: AMF performs path switching via UPF.

[0363] S1209: The AMF sends a path switching request acknowledgment message to the network device in the second cell.

[0364] In response, the network device in the second cell receives a path switching request acknowledgment message.

[0365] S1210: The network device in the second cell sends a terminal context release message to the network device in the first cell.

[0366] In response, the source base station receives a terminal context release message and releases the terminal context information.

[0367] Figure 13 is another schematic flowchart of an information transmission method according to one embodiment of the present application. As shown in Figure 13, in another possible design, the information transmission method may include S1301 to S1310.

[0368] S1301: The network device in the first cell sends a handover command to the terminal.

[0369] In response, the terminal receives a handover command from the network device of the first cell.

[0370] S1302: The terminal maintains link communication with the first cell and synchronizes with the second cell based on the handover command.

[0371] For example, a terminal may initiate random access to the network devices of the second cell in order to complete the configuration in the second cell.

[0372] S1303: The terminal sends a reconfiguration complete message to the network device of the second cell.

[0373] In response, the network device in the second cell receives a reconfiguration complete message.

[0374] S1304: The network device in the second cell sends a handover success instruction to the network device in the first cell.

[0375] In response, the network device in the first cell receives a handover success instruction.

[0376] S1305: The network device in the first cell sends an SN status transfer instruction to the network device in the second cell.

[0377] In response, the network device in the second cell receives an SN status transfer instruction. Based on the SN status transfer instruction, the network device in the second cell may transfer terminal user data.

[0378] S1306: The network device of the second cell sends a source cell configuration release message to the terminal.

[0379] In one embodiment, S1306 may be executed after the network device of the second cell has completed the data transfer. That is, the network device of the second cell sends a source cell configuration release message to the terminal after completing the data transfer.

[0380] In another embodiment, S1306 may be performed after S1305, but before the network device of the second cell completes the data transfer. That is, the network device of the second cell sends a source cell configuration release message to the terminal after receiving an SN status transfer instruction from the network device of the first cell.

[0381] In yet another embodiment, S1306 may occur after the network device of the second cell has completed the data transfer, but before S1307. That is, the network device of the second cell sends a source cell configuration release message to the terminal before sending a path switching request message.

[0382] In response, the terminal receives a source cell configuration release message. Based on the source cell configuration release message, the terminal may release the configuration in the first cell.

[0383] S1307: The network device in the second cell sends a path switching request message to the AMF.

[0384] In response, the AMF receives a path switching request message.

[0385] S1308: AMF performs path switching via UPF.

[0386] S1309: The AMF sends a path switching request acknowledgment message to the network device in the second cell.

[0387] In response, the network device in the second cell receives a path switching request acknowledgment message.

[0388] S1310: The network device in the second cell sends a terminal context release message to the network device in the first cell.

[0389] In response, the source base station receives a terminal context release message and releases the terminal context information.

[0390] Figure 14 is a schematic flowchart of yet another information transmission method according to one embodiment of the present application. As shown in Figure 14, in yet another possible design, the information transmission method may include S1401 to S1410.

[0391] S1401: The network device in the first cell sends a handover command to the terminal.

[0392] In response, the terminal receives a handover command from the network device of the first cell.

[0393] S1402: The terminal maintains link communication with the first cell and synchronizes with the second cell based on the handover command.

[0394] For example, a terminal may initiate random access to the network devices of the second cell in order to complete the configuration in the second cell.

[0395] S1403: The terminal sends a reconfiguration complete message to the network device of the second cell.

[0396] In response, the network device in the second cell receives a reconfiguration complete message.

[0397] S1404: The network device in the second cell sends a handover success instruction to the network device in the first cell.

[0398] In response, the network device in the first cell receives a handover success instruction.

[0399] S1405: The network device in the first cell sends an SN status forwarding instruction to the network device in the second cell.

[0400] In response, the network device in the second cell receives an SN status transfer instruction. Based on the SN status transfer instruction, the network device in the second cell may transfer terminal user data.

[0401] An SN status transfer instruction may also be called an SN status transfer message. An SN status transfer message or SN status transfer instruction is used to indicate the status information of the SN (sequence numbers) of the DRB where the DAPS handover is taking place. SN is the sequential data packet number of each DRB at the DPCP layer.

[0402] S1406: The network device in the second cell sends a path switching request message to the AMF.

[0403] In response, the AMF receives a path switching request message.

[0404] S1407: The network device of the second cell sends a source cell configuration release message to the terminal.

[0405] In one embodiment, S1406 may be executed before S1407. That is, the network device of the second cell sends a source cell configuration release message to the terminal after sending a path switching request message.

[0406] In another implementation, S1406 and S1407 may be executed simultaneously. That is, the network device of the second cell sends a source cell configuration release message to the terminal when it sends a handover success instruction to the network device of the first cell.

[0407] In response, the terminal receives a source cell configuration release message. Based on the source cell configuration release message, the terminal may release the configuration in the first cell.

[0408] S1408: AMF performs path switching via UPF.

[0409] S1409: The AMF sends a path switching request acknowledgment message to the network device in the second cell.

[0410] In response, the network device in the second cell receives a path switching request acknowledgment message.

[0411] S1410: The network device in the second cell sends a terminal context release message to the network device in the first cell.

[0412] In response, the source base station receives a terminal context release message and releases the terminal context information.

[0413] Figure 15 is a schematic flowchart of yet another information transmission method according to one embodiment of the present application. As shown in Figure 15, in yet another possible design, the information transmission method may include S1501 to S1510.

[0414] S1501: The network device in the first cell sends a handover command to the terminal.

[0415] In response, the terminal receives a handover command from the network device of the first cell.

[0416] S1502: The terminal maintains link communication with the first cell and synchronizes with the second cell based on the handover command.

[0417] For example, a terminal may initiate random access to the network devices of the second cell in order to complete the configuration in the second cell.

[0418] S1503: The terminal sends a reconfiguration complete message to the network device of the second cell.

[0419] In response, the network device in the second cell receives a reconfiguration complete message.

[0420] S1504: The network device in the second cell sends a handover success instruction to the network device in the first cell.

[0421] In response, the network device in the first cell receives a handover success instruction.

[0422] S1505: The network device in the first cell sends an SN status forwarding instruction to the network device in the second cell.

[0423] In response, the network device in the second cell receives an SN status transfer instruction. Based on the SN status transfer instruction, the network device in the second cell may transfer terminal user data.

[0424] S1506: The network device in the second cell sends a path switching request message to the AMF.

[0425] In response, the AMF receives a path switching request message.

[0426] S1507: AMF performs path switching via UPF.

[0427] S1508: The AMF sends a path switching request acknowledgment message to the network device in the second cell.

[0428] In response, the network device in the second cell receives a path switching request acknowledgment message.

[0429] S1509: The network device of the second cell sends a source cell configuration release message to the terminal.

[0430] In other words, the network device of the second cell sends a source cell configuration release message to the terminal after receiving a path switching request acknowledgment message, or before sending a terminal context release message to the network device of the first cell.

[0431] For example, assuming that the period from S1509 to S1510 is divided into three consecutive periods T1, T2, and T3, the network device of the second cell may send a source cell configuration release message to the terminal within T1 after receiving the path switching request acknowledgment message. Alternatively, the network device of the second cell may send a source cell configuration release message to the terminal within T3 before sending a terminal context release message to the network device of the first cell. Alternatively, the network device of the second cell may send a source cell configuration release message to the terminal within T2.

[0432] In response, the terminal receives a source cell configuration release message. Based on the source cell configuration release message, the terminal may release the configuration in the first cell.

[0433] S1510: The network device in the second cell sends a terminal context release message to the network device in the first cell.

[0434] In response, the source base station receives a terminal context release message and releases the terminal context information.

[0435] In the DAPS handover process, the network device of the second cell receives the end marker within the period between the time the AMF performs a path switch via the UPF and the time the AMF sends a path switch request acknowledgment message to the network device of the second cell. In yet another possible design, in this information transmission method, the network device of the second cell may send a source cell configuration release message to the terminal after receiving the end marker. This is not limited to the present application.

[0436] During the path switching process, the UPF sends data to the network device of the first cell (source base station), and the network device of the first cell (source base station) forwards the data to the network device of the second cell. After the data transfer is complete, the UPF continues to send end marker data packets to indicate the end of the data flow.

[0437] Optionally, the solutions in the embodiments shown in Figures 12 to 15 may also be used as a subordinate solution to the solution in the embodiment shown in Figure 7. That is, in the embodiments shown in Figures 12 to 15, in the DAPS handover process, after the terminal maintains link communication with the first cell and successfully accesses the second cell, the selected opportunity for the network device of the second cell to send a source cell configuration release message to the terminal during the aforementioned period from after S608 to S614 shown in Figure 6 may be the opportunity for the network device of the second cell to send a first reconfiguration message to the terminal, which includes a source cell configuration release instruction, in the embodiment shown in Figure 8.

[0438] In other words, in the solutions of the embodiments shown in Figures 12 to 15, in the DAPS handover process, after the terminal maintains link communication with the first cell and successfully accesses the second cell, the source cell configuration release message sent to the terminal by the network device of the second cell may be a first reconfiguration message that includes a source cell configuration release instruction sent to the terminal by the network device of the second cell in the embodiment shown in Figure 8.

[0439] The above primarily describes the solutions provided in the embodiments of this application from the perspective of interaction between network elements. To realize the aforementioned functions, it will be understood that network elements such as terminals and network devices include corresponding hardware structures and / or software modules for performing those functions.

[0440] For example, one embodiment of this application may further provide a communication device that can be applied to a terminal. Figure 16 is a schematic diagram of the structure of a communication device according to one embodiment of this application.

[0441] As shown in Figure 16, the communication device may include a receiving module 1601 configured to receive capability inquiry signaling from a network device, and a transmitting module 1602 configured to transmit terminal capability information to the network device. The capability information includes a first capability item and dual active protocol stack (DAPS) capability information corresponding to the first capability item, supported by the terminal, and / or a second capability item and carrier aggregation (CA) capability information corresponding to the second capability item, supported by the terminal.

[0442] In one possible design, capability information includes specific parameters for each band in multiple band combinations and is supported by the terminal. The DAPS capability information corresponding to a first capability item is specific parameters for each band in one of the multiple band combinations and / or is supported by the terminal. The CA capability information corresponding to a second capability item is specific parameters for each band in one of the multiple band combinations.

[0443] In one possible design, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters for each band in different band combinations.

[0444] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters for each band in the same band combination.

[0445] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first and second capability items may also correspond to specific parameters for each band in different band combinations.

[0446] In one possible design, the DAPS capability information corresponding to a first capability item supported by the terminal includes at least one of the following: uplink DAPS capability and downlink DAPS capability at a per-bandwidth granularity, or uplink DAPS capability and downlink DAPS capability at a per-carrier granularity.

[0447] In response to this, one embodiment of the present application may further provide a communication device that can be applied to a network device. Figure 17 is a schematic diagram of another structure of a communication device according to one embodiment of the present application.

[0448] As shown in Figure 17, the communication device may include a transmitting module 1701 configured to send capability inquiry signaling to a terminal, and a receiving module 1702 configured to receive capability information from the terminal. The capability information includes a first capability item and dual-active protocol stack (DAPS) capability information corresponding to the first capability item, which is supported by the terminal, and / or a second capability item and CA capability information corresponding to the second capability item, which is supported by the terminal.

[0449] In one possible design, capability information includes specific parameters for each band in multiple band combinations and is supported by the terminal. The DAPS capability information corresponding to a first capability item is specific parameters for each band in one of the multiple band combinations and / or is supported by the terminal. The CA capability information corresponding to a second capability item is specific parameters for each band in one of the multiple band combinations.

[0450] In one possible design, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters for each band in different band combinations.

[0451] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters for each band in the same band combination.

[0452] In another possible design, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first and second capability items may also correspond to specific parameters for each band in different band combinations.

[0453] In one possible design, the DAPS capability information corresponding to a first capability item supported by the terminal includes at least one of the following: uplink DAPS capability and downlink DAPS capability at a per-bandwidth granularity, or uplink DAPS capability and downlink DAPS capability at a per-carrier granularity.

[0454] Optionally, one embodiment of this application may further provide a communication device that can be applied to a terminal. Figure 18 is a schematic diagram of yet another structure of a communication device according to one embodiment of this application.

[0455] As shown in Figure 18, the communication device may include an access module 1801 configured to maintain link communication between the terminal and the first cell and to access the second cell normally, a receive module 1802 configured to receive a first reconfiguration message from the network device of the second cell, and a release module 1803 configured to release the terminal configuration in the first cell based on the first reconfiguration message.

[0456] In one possible design, the first reconfiguration message is the first reconfiguration message received by the receiving module 1802 from the network device of the second cell after the terminal has successfully accessed the second cell.

[0457] In one possible design, the first reconfiguration message may or may not include a source cell configuration release instruction.

[0458] In another possible design, the first reconfiguration message does not include a source cell configuration release instruction, and the access module 1801 is further configured to leave the existing configuration in the second cell unchanged and / or to send a reconfiguration error message to the network device in the second cell.

[0459] In one possible design, during the DAPS handover process, the receiving module 1802 is further configured to receive a handover command from a network device in the first cell, and the access module 1801 is specifically configured to maintain link communication between the terminal and the first cell based on the handover command and to successfully access the second cell.

[0460] In one possible design, the access module 1801 is configured to control the terminal to synchronize with the second cell and send a reconfiguration complete message to the network device of the second cell.

[0461] In response to this, one embodiment of the present application may further provide a communication device that can be applied to a network device. Figure 19 is a schematic diagram of yet another structure of a communication device according to one embodiment of the present application.

[0462] As shown in Figure 19, the communication device may include a transmitting module 1901 configured to send a first reconfiguration message to a terminal after the terminal has successfully accessed a second cell. The first reconfiguration message includes a source cell configuration release instruction, which is used to command the terminal to release the configuration in the first cell, the cell in which the terminal maintains link communication.

[0463] In one possible design, the first reconfiguration message is the first reconfiguration message that the terminal successfully sent to the second cell after the transmission module 1901.

[0464] In one possible design, the device further includes a receiving module 1902 configured to receive a reconfiguration complete message from a terminal.

[0465] In one possible design, the transmitting module 1901 specifically sends a first reconfiguration message to the terminal when it sends a handover success instruction to the network device of the first cell, or After sending a handover success instruction to the network device of the first cell, send a first reconfiguration message to the terminal, or After receiving an SN status transfer instruction from the network device of the first cell, send a first reconfiguration message to the terminal, or After completing the data transfer, send a first reconfiguration message to the terminal, or Send a first reconfiguration message to the terminal before sending a path switching request message, or Send a first reconfiguration message to the terminal when sending a path switching request message, or After sending a path switching request message, send a first reconfiguration message to the terminal, or After receiving the end marker, send a first reconfiguration message to the terminal, or After receiving a path switching request acknowledgment message, send a first reconfiguration message to the terminal, or The system is configured to send a first reconfiguration message to the terminal before sending a terminal context release message to the network device of the first cell.

[0466] Optionally, one embodiment of this application may further provide a communication device that can be applied to a terminal. Figure 20 is a schematic diagram of yet another structure of a communication device according to one embodiment of this application.

[0467] As shown in Figure 20, the communication device may include an access module 2001 configured to maintain link communication between a terminal and a first cell and to access a second cell successfully; a receiving module 2002 configured to receive a first reconfiguration message from a network device in the first cell; and an access module 2001 further configured to decide whether to leave the configuration of the terminal in the first cell unchanged or not to perform a reconfiguration based on the reconfiguration message.

[0468] In one possible design, the device further includes a transmit module 2003 configured to send reconfiguration error messages to the network device of the first cell.

[0469] In one possible design, during the DAPS handover process, the receiving module 2002 is further configured to receive a handover command from a network device in the first cell, and the access module 2001 is specifically configured to maintain link communication between the terminal and the first cell based on the handover command and to successfully access the second cell.

[0470] In one possible design, the access module 2001 is configured to control the terminal to synchronize with the second cell and send a reconfiguration complete message to the network device of the second cell.

[0471] Optionally, one embodiment of this application may further provide a communication device that can be applied to a network device. Figure 21 is a schematic diagram of yet another structure of a communication device according to one embodiment of this application.

[0472] As shown in Figure 21, the communication device may include a transmitting module 2101 and a processing module 2102. The processing module 2102 may be configured to control the terminal to access a second cell, process terminal data, etc. After the terminal has successfully accessed the second cell, the transmitting module 2101 sends a source cell configuration release message to the terminal when it sends a handover success instruction to the network device of the first cell, and the first cell is the cell that the terminal will maintain link communication with, or After sending a handover success instruction to the network device of the first cell, send a source cell configuration release message to the terminal, or After receiving an SN status transfer instruction from the network device of the first cell, send a source cell configuration release message to the terminal, or After completing the data transfer, send a source cell configuration release message to the terminal, or Send a source cell configuration release message to the terminal before sending a path switching request message, or When sending a path switching request message, send a source cell configuration release message to the terminal, or After sending a path switching request message, send a source cell configuration release message to the terminal, or After receiving the end marker, send a source cell configuration release message to the terminal, or After receiving a path switching request acknowledgment message, send a source cell configuration release message to the terminal, or The system is configured to send a source cell configuration release message to the terminal before sending a terminal context release message to the network device of the first cell.

[0473] The source cell configuration release message is used to instruct the terminal to release the configuration in the first cell.

[0474] Optionally, one embodiment of this application further provides a communication device. The communication device may be applied to the aforementioned network device or terminal. Figure 22 is a schematic diagram of yet another structure of a communication device according to one embodiment of this application.

[0475] As shown in Figure 22, the communication device may include a transceiver unit 2201 and a processing unit 2202. The transceiver unit 2201 may be configured to transmit and receive information, or to communicate with another network element. The processing unit 2202 may be configured to process data.

[0476] When the communication device is applied to a terminal, the transceiver unit 2201 and the processing unit 2202 may be used to carry out the method performed by the terminal in the above-described embodiment.

[0477] When the communication device is applied to a network device, the transceiver unit 2201 and the processing unit 2202 may be used to carry out the methods performed by the network device in the embodiments described above.

[0478] It should be understood that the division of modules or units within a device is merely a logical functional division. In actual implementation, all or part of the modules or units may be integrated into a single physical entity, or the modules or units may be physically separated. In addition, all units within a device may be implemented using software invoked by processing elements, or using hardware, or some units may be implemented using software invoked by processing elements, and some units may be implemented using hardware.

[0479] For example, each unit may be a separately located processing element or may be integrated into a chip of the device for implementation. In addition, each unit may be stored in memory in the form of a program, and the processing element of the device invokes and executes the functions of the units. In addition, all or part of the units may be integrated or implemented independently. The processing element as used herein may be called a processor, or it may be an integrated circuit having signal processing capabilities. In implementation, the steps in the above-described method or the units may be implemented by using hardware integrated logic circuits within the processor element, or they may be implemented in the form of software invoked by the processing element.

[0480] In one example, any one of the aforementioned units in the device may be one or more integrated circuits configured to carry out the aforementioned method, such as one or more ASICs, one or more DSPs, one or more FPGAs, or a combination of at least two of these integrated circuit forms.

[0481] As another example, if a unit within a device is implemented in the form of a program called by a processing element, the processing element could be a general-purpose processor, such as a CPU, or another processor capable of calling the program. As yet another example, these units may be integrated and implemented in the form of a system-on-a-chip (SOC).

[0482] The aforementioned receiving unit is an interface circuit or input circuit of the device and is configured to receive signals from another device. For example, if the device is implemented using a chip, the receiving unit is an interface circuit or input circuit used by the chip to receive signals from another chip or device. If the communication device includes a transmitting unit, the transmitting unit is an interface circuit or output circuit of the device and is configured to transmit signals to another device. For example, if the device is implemented using a chip, the transmitting unit is an interface circuit or output circuit used by the chip to transmit signals to another chip or device.

[0483] For example, one embodiment of the present application may further provide a communication device that can be applied to the network device or terminal described above. The communication device may include a processor and an interface circuit. There may be one or more processors. When the communication device is applied to a network device, the processor is configured to communicate with another device via the interface circuit and to perform the steps performed by the network device in the method described above. When the communication device is applied to a terminal, the processor is configured to communicate with another device via the interface circuit and to perform the steps performed by the terminal in the method described above.

[0484] In one embodiment, a unit used by a network device or terminal to separately perform the corresponding steps in the method described above may be implemented in a manner in which a processing element schedules a program. For example, a device applied to a network device or terminal may include a processing element and a storage element. The processing element invokes a program stored in the storage element to perform the method performed by the corresponding network device or terminal in the embodiment described above. The storage element may be a storage element located on the same chip as the processing element, i.e., an on-chip storage element.

[0485] In another embodiment, the program used to perform the method performed by the network device or terminal in the method described above may reside in a storage element located on a different chip from the processing element's chip, i.e., an off-chip storage element. In this case, the processing element calls the program from the off-chip storage element or loads it into an on-chip storage element to call the method performed by the corresponding network device or terminal in the method embodiment described above.

[0486] For example, one embodiment of this application may further provide a communication device. The communication device may include a processor configured to execute computer instructions stored in memory. When the computer instructions are executed, the device is enabled to perform the aforementioned methods performed by a network device or terminal. The memory may be located inside or outside the communication device. One or more processors are present.

[0487] In one embodiment, the unit used by a network device or terminal to carry out the steps in the method described above may consist of one or more processing elements, the processing elements may be located on the corresponding network device or terminal, and the processing elements herein may be integrated circuits, for example, one or more ASICs, one or more DSPs, one or more FPGAs, or a combination of these types of integrated circuits. The integrated circuits may be integrated to form a chip.

[0488] The unit used by a network device or terminal to perform the steps in the method described above may be integrated and implemented in the form of a System of Central (SOC). The SOC chip is configured to perform the corresponding method. At least one processing element and a storage element may be integrated into the chip, and the processing element performs the corresponding method by calling a program stored in the storage element. Alternatively, at least one integrated circuit may be integrated into the chip to perform the corresponding method. Alternatively, with reference to the method described above, some functions of the unit may be implemented by the processing element calling a program, and some functions of the unit may be implemented by an integrated circuit.

[0489] As described above, the processing element in this specification may be a general-purpose processor, such as a CPU, or one or more integrated circuits configured to carry out the method described above, such as one or more ASICs, one or more DSPs, one or more FPGAs, or a combination of at least two of these types of integrated circuits.

[0490] A memory element may refer to a single memory or to a collective term for multiple memory elements.

[0491] For example, one embodiment of the present application further provides a chip system which may be applied to the aforementioned network device or terminal. The chip system includes one or more interface circuits and one or more processors, the interface circuits and processors being interconnected via lines, and the processors receiving and executing computer instructions from the memory of an electronic device via the interface circuits to carry out the method performed by the corresponding network device or terminal in the aforementioned method embodiment.

[0492] From the description of the embodiments described above, those skilled in the art will clearly understand that the division of the functional modules described above is used only as an example for illustrative purposes, for the sake of simplicity. In actual applications, the functions described above may be assigned to different functional modules and completed by different functional modules according to requirements. That is, the internal structure of the device is divided into different functional modules to complete all or some of the functions described above.

[0493] It should be understood that in some embodiments provided in this application, the disclosed apparatus and methods may be implemented in other ways. For example, the described apparatus embodiments are merely illustrative. For example, the division into modules or units is merely a logical functional division, and other divisions may be used in actual implementation. For example, multiple units or components may be combined, integrated into another apparatus, or some features may be ignored or omitted. In addition, the mutual coupling, direct coupling, or communication connection indicated or considered may be implemented through some interfaces. Indirect coupling or communication connection between apparatuses or units may be implemented in an electrical, mechanical, or other form.

[0494] Units described as separate parts may or may not be physically separated, and a part shown as a unit may be one or more physical units, that is, they may be located in one place or distributed across multiple different locations. Some or all of the units may be selected based on the actual requirements in order to achieve the objectives of the solution of the embodiment.

[0495] In addition, the functional units in the embodiments of this application may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit. The integrated unit may be implemented in hardware form or in the form of a software functional unit.

[0496] If the integrated unit is implemented in the form of a software functional unit and sold or used independently as a product, the integrated unit may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of this application may be implemented essentially, or in part with respect to the prior art, or all or part of the technical solutions may be implemented in the form of a software product, for example, a program. The software product is a program product, for example, stored in a computer-readable storage medium, and includes several instructions for instructing a device (which may be a single-chip microcomputer, a chip, etc.) or processor to perform all or part of the steps of the method described in the embodiments of this application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, ROM, RAM, a magnetic disk, or an optical disk.

[0497] For example, one embodiment of this application may further provide a computer-readable storage medium containing computer software instructions. When the computer software instructions operate in a network device or a chip embedded in a network device, the network device is enabled to perform the methods performed by the network device in the embodiments described above.

[0498] Alternatively, when computer software instructions operate on a terminal or a chip embedded in the terminal, the terminal is enabled to perform the actions performed by the terminal in the embodiments described above.

[0499] The above description represents only specific embodiments of this application and is not intended to limit the scope of protection of this application. Any modifications or substitutions within the technical scope disclosed herein shall fall within the scope of protection of this application. Accordingly, the scope of protection of this application shall be subject to the scope of protection of the claims. [Explanation of Symbols]

[0500] 41 processors 42 memory 43 Communication Interface 44 bus 45 processors 310 terminals 320 network devices 1601 Receiver Module 1602 Transmitter Module 1701 Transmitter Module 1702 Receiver Module 1801 Access Module 1802 Receiver Module 1803 Release Module 1901 Transmitter Module 1902 Receiver Module 2001 Access Module 2002 Receiver Module 2003 Transmitter Module 2101 Transmitter Module 2102 Processing Module 2201 Transceiver Unit 2202 Processing Unit

Claims

1. An information transmission method, wherein the method is applied to a terminal, and the method is The steps include receiving capability inquiry signaling from a network device, A step of transmitting capability information of the terminal to the network device, wherein the capability information includes a first capability item and dual active protocol stack (DAPS) capability information for each band in the bandwidth combination corresponding to the first capability item, which is supported by the terminal, and a second capability item and carrier aggregation (CA) capability information for each band in the bandwidth combination corresponding to the second capability item, which is supported by the terminal, and the DAPS capability information for each band in the bandwidth combination corresponding to the first capability item, which is supported by the terminal, includes uplink DAPS capability and downlink DAPS capability. Information transmission methods including

2. The method according to claim 1, wherein, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters of each band in different band combinations.

3. The method according to claim 1 or 2, wherein, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters of each band in the same band combination.

4. An information transmission method, wherein the method is applied to a network device, and the method is The steps include sending a capability inquiry signaling to the terminal, A step of receiving capability information from the terminal, wherein the capability information includes a first capability item and dual active protocol stack (DAPS) capability information for each band in the bandwidth combination corresponding to the first capability item, which is supported by the terminal, and a second capability item and carrier aggregation (CA) capability information for each band in the bandwidth combination corresponding to the second capability item, which is supported by the terminal, and the DAPS capability information for each band in the bandwidth combination corresponding to the first capability item, which is supported by the terminal, includes uplink DAPS capability and downlink DAPS capability. Information transmission methods including

5. The method according to claim 4, wherein, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters of each band in different band combinations.

6. The method according to claim 4 or 5, wherein, if the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters of each band in the same band combination.

7. An information transmission device applied to a terminal, wherein the device is A receiving module configured to receive capability inquiry signaling from a network device, A transmitting module configured to transmit capability information of the terminal to the network device, wherein the capability information includes a first capability item and dual active protocol stack (DAPS) capability information for each band in a bandwidth combination corresponding to the first capability item, which is supported by the terminal, and a second capability item and carrier aggregation (CA) capability information for each band in a bandwidth combination corresponding to the second capability item, which is supported by the terminal, and the DAPS capability information for each band in the bandwidth combination corresponding to the first capability item, which is supported by the terminal, includes uplink DAPS capability and downlink DAPS capability, and An information transmission device equipped with the following features.

8. The apparatus according to claim 7, wherein, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters of each band in different band combinations.

9. The apparatus according to claim 7 or 8, wherein the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, and the first capability item and the second capability item correspond to specific parameters of each band in the same band combination.

10. An information transmission device applied to a network device, wherein the device A transmitting module configured to send capability inquiry signaling to a terminal, A receiving module configured to receive capability information from the terminal, wherein the capability information includes a first capability item and dual active protocol stack (DAPS) capability information for each band in a band combination corresponding to the first capability item, supported by the terminal, and a second capability item and carrier aggregation (CA) capability information for each band in a band combination corresponding to the second capability item, supported by the terminal, and the DAPS capability information for each band in the band combination corresponding to the first capability item, supported by the terminal, includes uplink DAPS capability and downlink DAPS capability, and An information transmission device equipped with the following features.

11. The apparatus according to claim 10, wherein, if the DAPS capability information supported by the terminal differs from the CA capability information supported by the terminal, the first capability item and the second capability item correspond to specific parameters of each band in different band combinations.

12. The apparatus according to claim 10 or 11, wherein the DAPS capability information supported by the terminal is the same as the CA capability information supported by the terminal, and the first capability item and the second capability item correspond to specific parameters of each band in the same band combination.

13. A communication device, A communication device comprising a processor configured to execute computer instructions stored in memory, wherein when the computer instructions are executed, the device enables the device to perform the method according to any one of claims 1 to 3.

14. A communication device, A communication device comprising a processor configured to execute computer instructions stored in memory, wherein when the computer instructions are executed, the device enables the device to perform the method according to any one of claims 4 to 6.

15. A communication device comprising a processor and an interface circuit, wherein the processor is configured to communicate with another device via the interface circuit and to perform the method according to any one of claims 1 to 3.

16. A communication device comprising a processor and an interface circuit, wherein the processor is configured to communicate with another device via the interface circuit and to perform the method according to any one of claims 4 to 6.

17. A computer-readable storage medium containing computer software instructions, A computer-readable storage medium that enables the terminal to perform the method according to any one of claims 1 to 3 when the computer software instruction is performed on a terminal or a chip embedded in the terminal.

18. A computer-readable storage medium containing computer software instructions, A computer-readable storage medium that enables the network device to perform the method according to any one of claims 4 to 6 when the computer software instruction is operated on a network device or a chip embedded in a network device.

19. A communication system comprising network devices and terminals, The terminal performs the method described in any one of claims 1 to 3, The network device is a communication system that performs the method according to any one of claims 4 to 6.

Images