Communication method and device

Abstract

A communication method and apparatus, the method comprising: a network device sending a first RRC message to a terminal device, the first RRC message being used for configuring a first RRC connection, and the terminal device sending a second RRC message comprising a first capability parameter set in response to the first RRC message. Wherein the terminal device sends the second RRC message in the form of segments, for example, the terminal device sends a plurality of segments included in the second RRC message. In the embodiment of the invention, the network device receives any segment in the second RRC message and considers that the first RRC connection configuration is successfully completed, and compared with the situation that the first RRC connection configuration is successfully completed only when all contents of the second RRC message are received, it can be determined that the terminal device successfully completes the first RRC connection configuration in advance, so that the service is transmitted as early as possible, and the service transmission delay is reduced.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] Different terminal devices may have different capabilities. Network devices configure and schedule terminal devices based on their actual capabilities to ensure proper communication between them. Typically, after initial registration, a terminal device responds to a network device's capability query message by reporting its capabilities, such as its frequency band combination capabilities. In addition to the capabilities listed in the capability information, some terminal devices also report certain capabilities through radio resource control (RRC) reconfiguration completion messages. For example, the network device sends an RRC reconfiguration message to the terminal device, and the terminal device sends an RRC reconfiguration completion message to the network device, which carries some of the terminal device's capabilities.

[0003] As capabilities increase, the number of capability parameters carried in the RRC reconfiguration completion message may also increase, which will increase the RRC reconfiguration completion latency. Summary of the Invention

[0004] This application provides a communication method and apparatus for reducing RRC connection completion delay, so as to start service transmission as early as possible, thereby reducing service transmission delay.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, this application provides a communication method applied to a terminal side. For example, the method may be applied to a terminal device or a component within the terminal device (e.g., a circuit, chip, or chip system), or it may be applied to a larger device including the terminal device. For ease of description, the following example illustrates the method applied to a terminal device.

[0007] The communication method includes: a terminal device receiving a first RRC message from a first network device and sending a second RRC message. The first RRC message is used to configure a first RRC connection. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message. The second RRC message includes a first segment and a second segment. Sending the second RRC message by the terminal device includes: the terminal device sending the first segment, which indicates successful completion of the first RRC connection configuration.

[0008] Accordingly, in a second aspect, this application provides a communication method applied to a network side. For example, the method may be applied to a network device or a component within the network device (e.g., a circuit, chip, or chip system), or it may be applied to a larger device including the network device. For ease of description, the following example illustrates the method applied to a first network device.

[0009] The communication method includes: a first network device sending a first RRC message and receiving a first segment from a second RRC message. The first RRC message is used to configure a first RRC connection. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message. The second RRC message includes a first segment and a second segment, whereby the first segment indicates successful completion of the first RRC connection configuration.

[0010] In the solutions provided in the first or second aspect, the second RRC message is sent in segments, so that the first network device can consider the first RRC connection configuration to be successfully completed upon receiving any segment of the second RRC message. This is equivalent to the terminal device informing the first network device in advance, through the segments of the second RRC message, that the terminal device has successfully completed the first RRC connection configuration. Compared to the first network device needing to receive the entire second RRC message to consider the first RRC connection configuration successful, the first network device's advance knowledge of the terminal device's successful completion allows for earlier service transmission, reducing service transmission latency.

[0011] Thirdly, this application provides a communication method applied to a terminal side. For example, the method may be applied to a terminal device or a component within the terminal device (e.g., a circuit, chip, or chip system), or it may be applied to a larger device including the terminal device. For ease of description, the following example illustrates the method applied to a terminal device.

[0012] The communication method includes: a terminal device receiving a first RRC message from a first network device, sending a third RRC message, and sending a second RRC message. The first RRC message is used to configure a first RRC connection. The third RRC message is used to indicate successful completion of the first RRC connection configuration. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message.

[0013] Accordingly, in a fourth aspect, this application provides a communication method applied to a network side. For example, the method may be applied to a network device or a component within the network device (e.g., a circuit, chip, or chip system), or it may be applied to a larger device including the network device. For ease of description, the following example illustrates the method applied to a first network device.

[0014] The communication method includes: a first network device sending a first RRC message, receiving a third RRC message, and receiving a second RRC message. The first RRC message is used to configure a first RRC connection. The third RRC message is used to indicate successful completion of the first RRC connection configuration. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message.

[0015] In the solutions provided in the third or fourth aspect, after receiving the first RRC message, the terminal device informs the first network device in advance via a third RRC message that the terminal device has successfully completed the first RRC connection configuration. The first network device considers the successful completion of the first RRC connection configuration upon receiving the third RRC message. Compared to the first network device only considering the successful completion of the first RRC connection configuration upon receiving the entire second RRC message, the earlier notification of the successful completion of the first RRC connection configuration by the terminal device allows for earlier service transmission and reduces service transmission latency.

[0016] In a possible implementation of the third or fourth aspect, the third RRC message includes first indication information for indicating receipt of the second RRC message.

[0017] In this scheme, the terminal device uses the first indication information to make the first network device realize that after the third RRC message, there is a second RRC message to be received, so as to avoid the first network device treating the third RRC message as the only response message to the first RRC message and missing the second RRC message.

[0018] Fifthly, this application provides a communication method applied to a terminal side. For example, the method may be applied to a terminal device or a component within the terminal device (e.g., a circuit, chip, or chip system), or it may be applied to a larger device including the terminal device. For ease of description, the following example illustrates the method applied to a terminal device.

[0019] The communication method includes: a terminal device receiving a capability query message from a first network device, the capability query message being used to query the capabilities of the terminal device. The capability query message includes second indication information, the second indication information being used to indicate that the terminal device is allowed to report its capabilities according to an RRC configuration message.

[0020] Accordingly, in a sixth aspect, this application provides a communication method applied to a network side. For example, the method may be applied to a network device or a component within the network device (e.g., a circuit, chip, or chip system), or it may be applied to a larger device including the network device. For ease of description, the following example illustrates the method applied to a first network device.

[0021] The communication method includes: a first network device sending a capability query message to a terminal device, the capability query message being used to query the capabilities of the terminal device. The capability query message includes second indication information, the second indication information being used to indicate that the terminal device is allowed to report its capabilities according to an RRC configuration message.

[0022] In the solutions provided in the fifth or sixth aspect, the first network device informs the terminal device via a capability query message, allowing the terminal device to report its capabilities according to the RRC configuration message. This allows the terminal device to determine whether to report its capabilities based on the first network device's instruction. For example, when the first network device allows the terminal device to report its capabilities according to the RRC configuration message, the terminal device reports its capabilities accordingly, saving the overhead of reporting capabilities via capability information. When the first network device does not allow the terminal device to report its capabilities according to the RRC configuration message, the terminal device will not report its capabilities to avoid unnecessary capability reporting and signaling waste.

[0023] In a possible implementation of the fifth aspect, the method further includes: a terminal device sending capability information, the capability information including a second set of capability parameters, the second set of capability parameters indicating at least one capability supported by the terminal device. Correspondingly, in a possible implementation of the sixth aspect, the method further includes: a first network device receiving capability information, the capability information including a second set of capability parameters, the second set of capability parameters indicating at least one capability parameter supported by the terminal device.

[0024] In a possible implementation of the fifth or sixth aspect, the capability information includes one or more of the first, second, or third information. The first information indicates whether the terminal device supports reporting capability information in response to an RRC configuration message. The second information indicates whether the terminal device supports reporting capability information for a first frequency band combination in response to an RRC configuration message. The third information indicates whether the terminal device supports reporting capability information for a first capability in response to an RRC configuration message.

[0025] In this scheme, the terminal device can inform the network device via capability information whether it supports reporting capability information in response to RRC configuration messages, or whether it supports reporting capability information for a first frequency band combination in response to RRC configuration messages, or whether it supports reporting capability information for a first capability in response to RRC configuration messages. This scheme can assist the first network device in determining whether to request the terminal device to report one or more capabilities based on RRC configuration messages. For example, if the terminal device does not support reporting capability information for a first frequency band combination in response to RRC configuration messages, then the first network device does not need to request the terminal device to report capabilities for the first frequency band combination based on RRC configuration messages, thus avoiding unnecessary signaling waste.

[0026] In a possible implementation of the fifth or sixth aspect, the second capability parameter indicates that the capabilities supported by the terminal device include a first capability, which corresponds to a first capability parameter value, which is predefined.

[0027] In this scheme, the first capability can be characterized by a predefined first capability parameter value. In this case, when the terminal device reports the second capability parameter, it does not need to indicate the first capability parameter value; the first network device can determine the first capability of the terminal device.

[0028] In a possible implementation of the fifth or sixth aspect, the first RRC message further includes third indication information, which is used to request the terminal device to report a first capability parameter set; or, the third indication information is used to request the terminal device to report a first capability parameter set related to the first capability.

[0029] In this scheme, the first network device can request specific capabilities from the terminal device through the third indication information, such as requesting the terminal device to report a set of first capability parameters or a set of first capability parameters related to the first capability, thereby meeting the actual needs of the first network device.

[0030] In a possible implementation of the fifth or sixth aspect, the first RRC message includes information about the first capability, and the second RRC message also includes the second capability parameter value corresponding to the first capability.

[0031] In this scheme, when the first RRC message includes information about the first capability, it can be assumed that the first network device wants to reacquire the first capability. In this case, the terminal device can report the second capability parameter value corresponding to the first capability through the second RRC message. The first network device determines the first capability based on the second capability parameter value, rather than defaulting to the capability indicated by the predefined first capability parameter value.

[0032] In a possible implementation of the fifth or sixth aspect, the first capability in the first RRC message is less than or equal to the first capability in the second RRC message.

[0033] Seventhly, this application provides a communication method applied to a terminal side. For example, the method may be applied to a terminal device or a component within the terminal device (e.g., a circuit, chip, or chip system), or it may be applied to a larger device including the terminal device. For ease of description, the following example illustrates the method applied to a terminal device.

[0034] The communication method includes: a terminal device receiving a first RRC message from a first network device, sending a second RRC message, and communicating with the first network device using a first set of capability parameters. The first RRC message is used to configure a first RRC connection. The second RRC message includes the first set of capability parameters, which is determined based on the first RRC message.

[0035] Accordingly, in an eighth aspect, this application provides a communication method applied to a network side. For example, the method may be applied to a network device or a component within the network device (e.g., a circuit, chip, or chip system), or the method may be applied to a larger device including the network device. For ease of description, the following example illustrates the method applied to a first network device.

[0036] The communication method includes: a first network device sending a first RRC message, receiving a second RRC message, and communicating with a terminal device using a first set of capability parameters. The first RRC message is used to configure a first RRC connection. The second RRC message includes the first set of capability parameters, which is determined based on the first RRC message.

[0037] In the solution provided in the seventh or eighth aspect, the terminal device and the first network device communicate by default using the first capability parameter set reported by the terminal device through the second RRC message. The first network device schedules the terminal device according to the first capability parameter set, and the terminal device communicates with the network device according to the first capability parameter set. This avoids inconsistencies in the understanding of the terminal device's capabilities between the first network device and the terminal device, thereby reducing communication anomalies between them.

[0038] In a possible implementation of the seventh aspect, the method further includes: before communicating with the first network device using the first set of capability parameters, the terminal device receives an acknowledgment message for the second RRC message, the acknowledgment message indicating that the first network device has successfully received the second RRC message. Correspondingly, in a possible implementation of the eighth aspect, the method further includes: before communicating with the terminal device using the first set of capability parameters, the first network device sends an acknowledgment message for the second RRC message, the acknowledgment message indicating that the first network device has successfully received the second RRC message.

[0039] In this scheme, the first network device can notify the terminal device that it has successfully received the second RRC message via an acknowledgment message. The acknowledgment message implicitly indicates that the first network device will use the first set of capability parameters to communicate with the terminal device.

[0040] In a possible implementation of the seventh aspect, the method further includes: the terminal device receiving fourth indication information, which instructs the first network device to confirm or refuse to communicate with the terminal device using the first capability parameter set; wherein, if the fourth indication information instructs the first network device to refuse to communicate with the terminal device using the first capability parameter set, a second capability parameter set is applied to communicate with the first network device, the second capability parameter set being included in the capability information of the terminal device. Correspondingly, in a possible implementation of the eighth aspect, the method further includes: the first network device sending fourth indication information, which instructs the first network device to confirm or refuse to communicate with the terminal device using the first capability parameter set; wherein, if the fourth indication information instructs the first network device to refuse to communicate with the terminal device using the first capability parameter set, a second capability parameter set is applied to communicate with the terminal device, the second capability parameter set being included in the capability information of the terminal device.

[0041] In this scheme, the first network device can explicitly inform the terminal device via a fourth indication message whether it will use a first set of capability parameters to communicate with the terminal device. If the fourth indication message indicates that the first network device will not use the first set of capability parameters to communicate with the terminal device, then by default, the first network device will use a second set of capability parameters to communicate with the terminal device. This scheme allows the terminal device to clearly understand whether the first network device is using the first or second set of capability parameters, thereby reducing communication anomalies between the terminal device and the network device.

[0042] Ninthly, embodiments of this application provide a communication method, which can be executed by a first communication device and a second communication device. The first communication device has the function of implementing the behavior in the method examples of the first aspect described above. For example, the first communication device includes corresponding means, modules, or units for executing the method of the first aspect, which can be implemented by software and / or hardware. The second communication device has the function of implementing the behavior in the method examples of the fifth aspect described above. For example, the second communication device includes corresponding means, modules, or units for executing the method of the fifth aspect, which can be implemented by software and / or hardware. The first communication device is used as a terminal device, and the second communication device is used as a first network device as an example below.

[0043] The communication method includes: a first network device sending a first RRC message to a terminal device, the first RRC message being used to configure a first RRC connection; the terminal device sending a second RRC message to the first network device, the second RRC message including a first set of capability parameters, the first set of capability parameters being determined based on the first RRC message. The second RRC message includes a first segment and a second segment, the first segment being used to indicate successful completion of the first RRC connection configuration. Specifically, the terminal device sending the second RRC message to the first network device includes the terminal device sending the first segment to the first network device.

[0044] Tenthly, embodiments of this application provide a communication method that can be executed by a first communication device and a second communication device. The first communication device has the function of implementing the behavior in the method example of the first aspect described above. For example, the first communication device includes corresponding means, modules, or units for executing the method of the first aspect, which can be implemented by software and / or hardware. The second communication device has the function of implementing the behavior in the method example of the fifth aspect described above. For example, the second communication device includes corresponding means, modules, or units for executing the method of the fifth aspect, which can be implemented by software and / or hardware. The first communication device is used as a terminal device, and the second communication device is used as a first network device as an example below.

[0045] The communication method includes: a first network device sending a first RRC message to a terminal device, the first RRC message being used to configure a first RRC connection; the terminal device sending a third RRC message to the first network device, the third RRC message being used to indicate successful completion of the first RRC connection configuration; and the terminal device sending a second RRC message to the first network device, the second RRC message including a first set of capability parameters, the first set of capability parameters being determined based on the first RRC message.

[0046] Eleventhly, embodiments of this application provide a communication method that can be executed by a first communication device and a second communication device. The first communication device has the function of implementing the behavior in the method example of the first aspect described above. For example, the first communication device includes corresponding means, modules, or units for executing the method of the first aspect, which can be implemented by software and / or hardware. The second communication device has the function of implementing the behavior in the method example of the fifth aspect described above. For example, the second communication device includes corresponding means, modules, or units for executing the method of the fifth aspect, which can be implemented by software and / or hardware. The first communication device is used as a terminal device, and the second communication device is used as a first network device as an example below.

[0047] The communication method includes: a first network device sending a first RRC message to a terminal device, the first RRC message being used to configure a first RRC connection; the terminal device sending a second RRC message to the first network device, the second RRC message including a first set of capability parameters, the first set of capability parameters being determined based on the first RRC message; and the terminal device and the network device communicating using the first set of capability parameters.

[0048] In a twelfth aspect, embodiments of this application provide a communication device that has the functionality to implement the behaviors described in any of the method examples of the first to eighth aspects. The beneficial effects can be found in the relevant descriptions of the first to eighth aspects and will not be repeated here. For example, the communication device can be a terminal device as described in any of the first, third, fifth, and seventh aspects; or, the communication device can be a device capable of supporting the terminal device to implement the functions required by the methods provided in any of the first, third, fifth, and seventh aspects. For example, the communication device can be a chip or chip system in the terminal device. As another example, the communication device can be a network device as described in any of the second, fourth, sixth, and eighth aspects; or, the communication device can be a device capable of supporting the network device to implement the functions required by the methods provided in any of the second, fourth, sixth, and eighth aspects. For example, the communication device can be a chip or chip system in the network device.

[0049] In one possible design, the communication device includes a baseband device and a radio frequency device.

[0050] In one possible design, the communication device includes corresponding means or modules for performing the methods of any of the first to eighth aspects. For example, the communication device includes a processing unit (sometimes also called a processing module or processor) and / or a transceiver unit (sometimes also called a transceiver module or transceiver). The transceiver unit is capable of both transmitting and receiving functions. When the transceiver unit performs the transmitting function, it may be called a transmitting unit (sometimes also called a transmitting module), and when it performs the receiving function, it may be called a receiving unit (sometimes also called a receiving module). The transmitting unit and the receiving unit may be the same functional unit, referred to as the transceiver unit, which performs both transmitting and receiving functions; or, the transmitting unit and the receiving unit may be different functional units, with "transceiver unit" being a collective term for these functional units. These units (modules) can perform the corresponding functions in the method examples of any of the first to eighth aspects described above, as detailed in the method examples, and will not be repeated here.

[0051] In a thirteenth aspect, embodiments of this application provide a communication device, which may be the communication device described in the twelfth aspect of the above embodiments, or a chip or chip system disposed in the communication device described in the twelfth aspect. The communication device includes a communication interface and a processor, and optionally, a memory. The memory stores computer programs, instructions, or data, and the processor is coupled to the memory and the communication interface. When the processor reads the computer program, instructions, or data, it causes the communication device to execute the method performed by the terminal device in the above method embodiments. For example, the communication device may be a terminal device or a functional module within a terminal device, such as a baseband chip and a radio frequency chip. Alternatively, when the processor reads the computer program, instructions, or data, it causes the communication device to execute the method performed by the network device in the above method embodiments. For example, the communication device may be a network device or a functional module within a network device, such as a baseband chip and a radio frequency chip.

[0052] In a fourteenth aspect, embodiments of this application provide a chip system including a processor and a communication interface for implementing the methods described in any of the first to eighth aspects. Optionally, the chip system further includes a memory. The memory stores a computer program (also referred to as code or instructions). The processor retrieves and executes the computer program from the memory, causing a device equipped with the chip system to perform the methods of any of the first to eighth aspects and any implementation thereof. The chip system may be composed of chips or may include chips and other discrete devices.

[0053] In a fifteenth aspect, embodiments of this application provide a communication device including an input / output interface and logic circuitry. The input / output interface is used for inputting and / or outputting information. The input / output interface may be an interface circuit, an output circuit, an input circuit, a pin, or related circuitry, etc. The logic circuitry is used to execute the methods described in any of the first to eighth aspects.

[0054] In practical implementation, the aforementioned communication device can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the logic circuit can be a transistor, gate circuit, flip-flop, and various other logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the input / output interface and the logic circuit.

[0055] In one implementation, when the communication device is a wireless communication device, it can be a terminal device such as a mobile phone, or a network device such as a base station. The interface circuit can be a radio frequency processing chip in the wireless communication device, and the processing circuit can be a baseband processing chip in the wireless communication device.

[0056] In a sixteenth aspect, embodiments of this application provide a communication system comprising a terminal device and a network device, wherein the terminal device is configured to implement the function of the method described in the first aspect, and the network device is configured to implement the function of the method described in the second aspect; or, the terminal device is configured to implement the function of the method described in the third aspect, and the network device is configured to implement the function of the method described in the fourth aspect; or, the terminal device is configured to implement the function of the method described in the fifth aspect, and the network device is configured to implement the function of the method described in the sixth aspect; or, the terminal device is configured to implement the function of the method described in the seventh aspect, and the network device is configured to implement the function of the method described in the eighth aspect.

[0057] In a seventeenth aspect, embodiments of this application provide a computer-readable storage medium for storing a computer program or instructions that, when executed, cause the methods described in any of the first to eighth aspects and any implementation thereof to be implemented.

[0058] In an eighteenth aspect, embodiments of this application also provide a computer program product containing instructions that, when run on a computer, cause the methods described in any of the first to eighth aspects and any implementation thereof to be implemented.

[0059] The beneficial effects of the aforementioned aspects nine through eighteen and their implementation methods can be referenced to the beneficial effects of any aspect one through eight and any implementation method therein. Attached Figure Description

[0060] Figure 1 A schematic diagram of the communication system provided in the embodiments of this application;

[0061] Figure 2 Schematic diagrams of two typical protocol stacks for a base station provided in the embodiments of this application;

[0062] Figure 3 A flowchart illustrating the terminal device reporting capability provided in this application embodiment;

[0063] Figure 4 A flowchart illustrating the communication method 400 provided in an embodiment of this application;

[0064] Figure 5 A flowchart illustrating the communication method 500 provided in an embodiment of this application;

[0065] Figure 6 A flowchart illustrating the communication method 600 provided in an embodiment of this application;

[0066] Figure 7 A flowchart illustrating the communication method 700 provided in an embodiment of this application;

[0067] Figure 8 A flowchart illustrating the communication method 800 provided in an embodiment of this application;

[0068] Figure 9 A schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0069] Figure 10 This is another schematic diagram of the communication device provided in the embodiments of this application. Detailed Implementation

[0070] The technical solutions provided in the embodiments of this application can be applied to communication systems related to the 3rd Generation Partnership Project (3GPP), such as Long Term Evolution (LTE) communication systems, 5th Generation (5G) mobile communication systems, or other next-generation mobile communication systems, such as 6th Generation (6G) communication systems, or other similar communication systems. Other similar communication systems may include Wireless Fidelity (WIFI), Vehicle-to-Everything (V2X), Internet of Things (IoT) systems, Narrow Band Internet of Things (NB-IoT) systems, and so on.

[0071] Please see Figure 1 This illustration shows a communication system applicable to embodiments of this application. The communication system includes a wireless access network 100 and a core network 200. Optionally, the communication system may also include the Internet. Figure 1 (Using this as an example).

[0072] The wireless access network 100 may include at least one network device and at least one terminal device. For example, the wireless access network 100 includes two network devices, 110a and 110b, and terminal devices, such as 120a to 120j. Figure 1The network architecture shown is merely illustrative; the number of terminal devices and / or network devices may be fewer or more. The communication system described in the embodiments of this application is intended to more clearly illustrate the technical solutions of the embodiments of this application and does not constitute a limitation on the communication system to which the embodiments of this application apply. For example, the communication system may also include other devices, such as wireless relay devices and wireless backhaul devices, etc. Figure 1 Not shown in the diagram. Those skilled in the art will recognize that, with the evolution of network architecture, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. When applying the technical solutions of the embodiments of this application to other communication systems, the devices, components, modules, etc., in the embodiments can be replaced with corresponding devices, components, modules in other communication systems, without limitation.

[0073] In this embodiment, the network device refers to a radio access network (RAN) device. The RAN can be a 3GPP-related cellular system, such as a 5G / new radio (NR) mobile communication system, or a future-oriented evolution system (e.g., a 6G mobile communication system). The RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a virtualized RAN (vRAN), etc. The RAN can also be a communication system that integrates two or more of the above systems. The RAN device can also be referred to as a RAN node, RAN entity, or access node, etc.

[0074] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a 6G mobile communication system, or a base station in a future mobile communication system. A RAN node can also be a macro base station, a micro base station, an indoor station, a relay node, a donor / host node, or a radio controller. RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in V2X technology, a RAN node can be a roadside unit (RSU).

[0075] In another possible scenario, a RAN node can be a module or unit that performs some of the functions of a base station; or multiple RAN nodes can collaborate to assist terminal devices in achieving wireless access, with different RAN nodes performing some of the functions of a base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). The function of a CU can be implemented by a single entity or by different entities. For example, the function of a CU can be further divided, that is, the control plane and the user plane can be separated and implemented by different entities, namely the control plane CU entity (i.e., CU-control plane (CP) entity) and the user plane CU entity (i.e., CU-user plane (UP) entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the function of the RAN node. The CU and DU can be set up separately or included in the same network element, such as in the baseband unit (BBU). Any of the units among the CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented by software modules, hardware modules, or a combination of software modules and hardware modules.

[0076] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples.

[0077] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement: for example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and above (such as the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer); the DU can be configured to implement the functions of protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and / or the Physical (PHY) layer). For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications or the technical specifications of other applicable communication protocols.

[0078] For example, see Figure 2 The following are schematic diagrams of two typical protocol stacks of a base station provided in the embodiments of this application. In base station (1), the base station is divided into CU and DU. CU is configured to implement the functions of protocol layers above PDCP (e.g., RRC layer and / or SDAP layer, etc.); DU is configured to implement the functions of protocol layers below PDCP (e.g., RLC layer, MAC layer, and / or PHY layer, etc.). CU and DU communicate with each other based on the F1 interface. In base station (2), the base station is divided into CU and DU. CU includes CU-CP and CU-UP. CU-CP is used to implement the control plane functions of CU, and CU-UP is used to implement the user plane functions of CU. CU-CP and CU-UP can communicate based on the E1 interface. CU-CP and DU communicate based on the F1 interface (also called F1-C) that supports the control plane. CU-UP and DU communicate based on the F1 interface (also called F1-U) that supports the user plane. CU-CP is configured to implement the control plane and RRC layer functions of the PDCP layer, and CU-UP is configured to implement the user plane and SDAP layer functions of the PDCP layer. DU is configured to implement the functions of protocol layers below the PDCP layer (such as RLC, MAC, and / or PHY layers).

[0079] The above division of the processing functions of CU and DU according to protocol layers is merely an example; other division methods are also possible, and this application does not limit this. For example, in one design, CU or DU can be further divided into processing functions with protocol layers. In one design, some functions of the RLC layer and the functions of the protocol layer above the RLC layer are located in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are located in the DU.

[0080] In another possible design, the DU and RU collaborate to implement the PHY layer functionality, or, more specifically, a portion of the PHY layer functionality of the DU can be moved to the RU. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways depending on the design. For example, the DU may be configured to implement baseband functions, and the RU may be configured to implement mid-RF functions. Alternatively, the DU may be configured to implement higher-level functions in the PHY layer, and the RU may be configured to implement lower-level functions in the PHY layer, or both lower-level and RF functions. Higher-level functions in the physical layer may include a portion of the physical layer's functionality closer to the MAC layer, and lower-level functions may include another portion of the physical layer's functionality closer to the mid-RF side. This application does not limit the specific functions of the DU and RU. The interface between the DU and RU can be called a fronthaul interface. In one design, the CU may not have a PDCP layer; for example, the CU may only include an RRC layer. The CU-CP may not have PDCP-C. The CU-UP may not have PDCP-U, or may not have a CU-UP. In one design, the DU may not have an RLC layer; for example, the DU may only have a MAC and a higher PHY layer.

[0081] When the RAN is O-RAN, it can also have artificial intelligence (AI) capabilities. For example, O-RAN includes an intelligent controller. The intelligent controller can be a non-real-time RAN intelligent controller (RIC / non-RT RIC / NRTRIC) or a near-real-time RAN intelligent controller (RIC / nRT RIC / nRT RIC). A non-real-time RIC can be used to implement non-real-time intelligent management of RAN functions, enabling workflows including model training and updates, and guiding applications / functions in the nRT RIC based on policies. A near-real-time RIC can be used to implement near-real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, near-real-time control and optimization of O-RAN modules and resources are achieved.

[0082] In the embodiments of this application, the means for implementing the functions of the network device can be the network device itself, or it can be a means that supports the network device in implementing the functions, such as a chip system or a combination of devices or components that can implement the functions of the network device. This means can be installed in the network device. The embodiments of this application do not limit the specific technology or specific device form used in the network device.

[0083] In this application embodiment, anything capable of data communication with a base station can be considered a terminal device. Terminal devices are also called terminals, terminal equipment, user equipment (UE), mobile stations, or mobile terminals, etc. Terminal devices can be widely used in various scenarios. For example, terminal devices can be: mobile phones, computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, stations (STA), robotic arms, cameras, robots, vehicles, drones, helicopters, airplanes, ships, or smart home devices (such as televisions, air conditioners, robot vacuums, speakers, set-top boxes), relays, customer premises equipment (CPE), etc.

[0084] Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system, such as a water meter or electricity meter. IoT is an important component of future information technology development. Its main technical characteristic is connecting objects to networks through communication technology, thereby realizing an intelligent network that enables human-machine interconnection and object-to-object interconnection.

[0085] When the terminal device is applied to V2X, it can also be called a V2X device, such as a smart car, digital car, unmanned car, driverless car, pilotless car, autonomous car, pure electric vehicle, hybrid electric vehicle (HEV), range-extended electric vehicle (REEV), plug-in hybrid electric vehicle (PHEV), new energy vehicle, and roadside unit (RSU).

[0086] The various terminal devices described above, if located on a vehicle (e.g., placed / installed inside the vehicle), can all be considered in-vehicle terminal devices. In-vehicle terminal devices can be built into a vehicle's in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit as one or more components or units. The vehicle can implement the methods of this application through the built-in in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit. In-vehicle terminal devices can be vehicle equipment, in-vehicle modules, vehicles, on-board units (OBU), roadside units (RSU), in-vehicle systems (or in-vehicle transmitting units) (telematics boxes, T-boxes), chips, or systems on chips (SOCs), etc. These chips or SOCs can be installed in the vehicle, OBU, RSU, or T-box.

[0087] In the embodiments of this application, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing the functions, such as a chip system or a combination of devices or components that can implement the functions of the terminal device. This device can be installed in the terminal device. The embodiments of this application do not limit the specific technology or device form used in the terminal device.

[0088] Taking a network device as a base station and a terminal device as a UE as an example, the base station and UE can be fixed or mobile. The base station and UE can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed on airplanes, balloons, and artificial satellites. The embodiments of this application do not limit the application scenarios of the base station and UE.

[0089] The roles of the base station and the UE can be relative, for example, Figure 1 The helicopter or drone 120i can be configured as a mobile base station. For UEs 120j accessing the wireless access network 100 via 120i, UE 120i is a base station; however, for base station 110a, 120i is a UE, meaning that 110a and 120i communicate via a radio interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol; in this case, 120i is also a base station relative to 110a. Therefore, both the base station and the UE can be collectively referred to as a communication device. Figure 1 The 110a and 110b in the text can be referred to as communication devices with base station functions. Figure 1 The 120a-120j in the text can be referred to as communication devices with UE functionality.

[0090] The communication system applicable to the embodiments of this application has been described above. The following describes some contents involved in the embodiments of this application, such as the capabilities of the terminal device and the process of the terminal device reporting capabilities.

[0091] 1) Carrier aggregation

[0092] Carrier aggregation refers to providing services to terminal devices simultaneously using multiple carriers. By aggregating multiple component carriers (CCs) to provide services to terminal devices at the same time, communication bandwidth and peak data rates can be increased. Each carrier can have at least one serving cell component carrier operating for the terminal device. In carrier aggregation technology, typically one carrier is the primary carrier (primary CC, PCC) or primary cell (primary cell, PCell), and the other carriers are secondary carriers (secondary CCs, SCCs) or secondary cells (secondary cells, Scells). Scells can be activated or deactivated during use. For example, if there is no data transmission for a period of time, the network can deactivate the Scell, and then reactivate it when data transmission resumes.

[0093] Carrier aggregation is divided into intra-band carrier aggregation and multi-band (or band combination) carrier aggregation. Intra-band carrier aggregation refers to the aggregation of multiple carriers on a single band (also called a frequency band), while multi-band carrier aggregation refers to the aggregation of multiple carriers on multiple frequency bands. Taking a band combination including band A, band B, and band C as an example, band A has one carrier, band B has two carriers, and band C has two carriers. The carrier aggregation of the band combination can be performed by aggregating one carrier on band A, two carriers on band B, and two carriers on band C.

[0094] 2) Capabilities of terminal equipment

[0095] The capabilities of a terminal device include, but are not limited to, one or more of the following: supported frequency bands, supported carrier blocks (BCs), supported secondary cells (SCells), supported number of carrier blocks (CCs), maximum supported multiple-input multiple-output (MIMO) layers, and measurement interval capabilities. Frequency band combinations can be used to express the CA combinations and dual connectivity (DC) capabilities supported by the UE. A frequency band can also be called a frequency range, and each frequency band corresponds to a frequency range. Each frequency band in each frequency band combination can include one or more continuous or non-contiguous carriers. In the embodiments of this application, a frequency band can also be a frequency / frequency point.

[0096] 3) Levels of terminal device capabilities

[0097] The capabilities of terminal devices can be divided into several levels, including but not limited to: terminal device level capabilities, frequency band level capabilities, and frequency band combination level capabilities.

[0098] 3-1) Terminal device level capabilities (also known as per UE capabilities), such as the protocol versions supported by the terminal device, PDCP layer capabilities, MAC layer capabilities, etc.

[0099] 3-2) Band-level capabilities (also known as per-band capabilities) are frequency-band related capabilities, typically associated with the radio frequency capabilities of the terminal device. The capabilities of a terminal device include a supported band list, which includes an identifier for each supported band and the corresponding band-level capabilities.

[0100] 3-3) Band Combination Level Capabilities (also known as BC-level capabilities or per-BC capabilities) are BC-related capabilities, primarily used for carrier aggregation and dual connectivity. The BCs supported by a terminal device are typically related to its RF and baseband capabilities. The terminal device's capabilities include a list of BCs it supports. For a given BC, the terminal device needs to indicate information about the frequency bands it includes, such as the identifiers of each frequency band included in the BC.

[0101] It's important to note that even if a terminal device only supports one band, it reports this information via a Broadband Controller (BC), which in this case contains only one band. A single band can support multiple consecutive carriers or only a single carrier.

[0102] 3-4) Per-band per-band capability (also known as per-band per-BC capability) refers to the capability of a specific band within a frequency band (BC), and is usually related to the RF capabilities of the terminal device. Each BC corresponds to a feature set combination (FSC). The FSC contains the feature set (FS) corresponding to each frequency band within that BC, which is the per-band per-BC capability of each frequency band, also known as per-FS capability.

[0103] Both per-band per BC level capabilities and per-band capabilities are band-specific capabilities. The difference lies in that per-band per BC level capabilities target a specific band within a given BC, while per-band capabilities are general capabilities for that band. For example, if a terminal device reports support for capability A in the per-band level capabilities of band A, then capability A should be supported on band A in all BCs composed of band A (e.g., band A + band B or band A + band C). However, for per-band per BC level capabilities, if a terminal device reports support for capability B on band A in a band A + band B combination, then band A in a band A + band C combination may report support for capability B. In essence, capability A belongs to the per-band level capabilities, and capability B belongs to the per-band per BC level capabilities.

[0104] 3-5) Carrier-level capability (also known as per CC capability) refers to the capability of component carriers within a frequency band combination. In per CC capability information, each component carrier is associated with a per-component carrier feature set (FSPC) to indicate the capability of the corresponding component carrier; therefore, per CC capability is also called FeatureSetPerCC capability. Each FSPC includes FeatureSetDownlinkPerCC cells for reporting downlink transmission capability and FeatureSetUplinkPerCC cells for reporting uplink transmission capability, indicating the uplink and downlink transmission capabilities of the terminal device, respectively.

[0105] 4) The process of terminal device reporting capabilities

[0106] Different terminal devices may have different capabilities. Network devices will configure and schedule terminal devices according to their actual capabilities so that they can communicate normally with network devices.

[0107] For example, see Figure 3 This is a schematic diagram illustrating the reporting capability of a terminal device provided in an embodiment of this application. Figure 3 As shown, after initial registration and network access, the terminal device reports its capabilities in response to the network device's capability query message. For example, in response to the network device's capability query message, the terminal device sends capability information (UEcapability information) to the network device. This capability information includes capability parameters or characteristic parameters of one or more capabilities supported by the terminal device. After receiving this capability information, the network device forwards it to the core network, where the core network stores the terminal device's capability information. When the terminal device switches to RRC idle state, the network device deletes the terminal device's capability information; when the terminal device transitions from RRC idle state to RRC connected state, the network device can obtain the terminal device's capabilities from the core network. In addition to the capabilities in the capability information, the terminal device also reports some capabilities through RRC reconfiguration. For example, the terminal device can report capabilities related to measurement gaps and capabilities related to the location of DC component transmission through RRC reconfiguration.

[0108] For ease of distinction, the capability reporting capability information can be called a basic capability / static capability, and the capability reporting RRC reconfiguration completion messages can be called a dynamic capability. Correspondingly, the method of reporting capabilities based on capability information is called a static reporting method, and the method of reporting capabilities based on RRC reconfiguration completion messages is called a dynamic reporting method. It should be noted that the dynamic reporting method is relative to the capability reporting through capability information. In this embodiment, the dynamic reporting method is not limited to the capability reporting capability based on RRC reconfiguration completion messages. Any method that reports configuration capabilities based on the current RRC connection, or in other words, the capability reporting configuration capabilities based on the RRC connection state after transitioning from an RRC disconnected state to an RRC connected state, can be considered a dynamic reporting method. For example, the method of reporting capabilities based on RRC recovery completion messages or RRC connection completion messages is also a dynamic reporting method.

[0109] Furthermore, the capabilities supported by terminal devices vary depending on the CA combination. When the RRC reconfiguration message sent by the network device to the terminal device includes a CA combination, the terminal device, upon receiving the RRC reconfiguration message, can also report the capabilities matching that CA combination, without needing to report the capabilities corresponding to other CA combinations, thereby reducing the signaling overhead of reporting capabilities.

[0110] 5) In the embodiments of this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0111] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0112] In the embodiments of this application, "when," "if," and "if" all refer to the device taking corresponding actions under certain objective circumstances, and are not time-limited, nor do they require the device to perform a judgment action, nor do they imply any other limitations. Unless otherwise specified, "if" and "if" can be substituted, and "when" and "in the case of" can be substituted. "When" and "if" / "if" can be substituted.

[0113] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0114] In this application's embodiments, ordinal numbers such as "first" and "second" are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, the first set of capability parameters and the second set of capability parameters refer to two different sets of capability parameters, and do not indicate a difference in the priority or importance of these two sets of capability parameters.

[0115] Figure 3 The illustrated process, while supporting message reporting capabilities via RRC reconfiguration for terminal devices, only a limited number of capabilities are supported. For example, currently, only specific capabilities such as measurement gap-related capabilities, DC component location transmission capabilities, and BC capabilities are supported for message reporting via RRC reconfiguration. As the number of capability parameters increases, terminal devices will need to adapt accordingly. Figure 3 The reported process shows that the overhead of capability information is also increasing.

[0116] Additionally, network devices can configure CA combinations for terminal devices via RRC reconfiguration messages, and terminal devices can also report BC capabilities via RRC reconfiguration. However, network devices do not explicitly indicate which frequency bands(s) are used to configure the CA combination for the terminal device; in other words, network devices do not explicitly indicate which frequency band combination is used for capability configuration in the RRC reconfiguration message. When a terminal device reports capabilities to a network device based on an RRC reconfiguration message, it will blindly guess the frequency band combination selected by the network device. For example, the terminal device will iterate through the capabilities reported based on capability information and match them with the configuration sent by the network device, blindly guessing the frequency band combination selected by the network device based on the matching results. For instance, the BC capabilities reported by the terminal device based on capability information include bandA+bandB+bandC (referred to as BC capability 1) and bandA+bandB+bandD (referred to as BC capability 2), and the CA combination in the RRC reconfiguration message sent by the network device is a CA combination consisting of carrier 1 on bandA and carrier 2 on bandB. The terminal device iterates through all parameters under the reported BC capabilities (such as bandwidth and subcarrier spacing on each carrier) and matches them with the parameters under the CA combination configured by the network device (such as bandwidth and subcarrier spacing on each carrier) to determine which BC capability the network device used to send the RRC reconfiguration message. If the terminal device finds that at least two BCs satisfy the network device's configuration based on the matching results, the terminal device will blindly select one of these two BCs as the BC on which the network device configuration is based.

[0117] Because there are numerous parameters under BC capabilities, matching all parameters under all reported BC capabilities with the RRC reconfiguration messages sent by the network device is highly complex. Furthermore, if the BC selected by the terminal device is not the BC referenced by the network device during configuration (i.e., the terminal device and network device are not aligned on their BC capabilities), communication between them will fail. As the number of BC capability parameters increases, the complexity of the terminal device blindly guessing the BC selected by the network device increases, the probability of BC capability misalignment between the terminal device and network device increases, and the probability of communication failure between them also increases.

[0118] To address the aforementioned technical problems, this application provides a solution based on its embodiments. In these embodiments, terminal devices are allowed to report capabilities other than the aforementioned specific capabilities (e.g., gap measurement capabilities, DC component location transmission capabilities, BC capabilities, etc.) via RRC messages. For example, based on the RRC configuration sent by the network device, the terminal device autonomously selects the capability parameters to be applied under the current network configuration and then informs the network device. This avoids the misalignment problem between the network device and the terminal device caused by blind matching by the terminal device, reducing the compatibility risk between the terminal device and the network device. For example, the BC capabilities reported by the terminal device include bandA+bandB+bandC (referred to as BC capability 1) and bandA+bandB+bandD (referred to as BC capability 2). The RRC configuration sent by the network device includes a CA combination, which is a CA combination consisting of carrier 1 on bandA and carrier 2 on bandB. The terminal device can autonomously select the capability parameters to be applied under the CA combination of the current network configuration and then inform the network device via an RRC message. Compared to the network device instructing the terminal device on the configuration and then the terminal device traversing the BC capability to determine which BC matches the network configuration, this method avoids the problem of misalignment between the network and the terminal device caused by blind matching by the terminal device.

[0119] In the following description, the communication method provided in the embodiments of this application is applied to... Figure 1 Taking the network architecture shown as an example, the communication method provided in this application embodiment can be executed by a first communication device and a second communication device. The steps executed by the first communication device can be implemented by the first communication device itself, by components within the first communication device (such as a baseband chip, or other processing units or processor modules), or by a device including the first communication device. The steps executed by the second communication device can be implemented by the second communication device itself, by components within the second communication device (such as a baseband chip, or other processing units or processor modules), or by a device including the second communication device. The specific form of the first and second communication devices is not limited; for example, the first communication device can be a chip, and the second communication device can be a device; or both the first and second communication devices can be chips or devices. In possible scenarios, the first communication device can be... Figure 1 The terminal device 120a shown, or it could be Figure 1 The chip (system) in the terminal device 120a; the second communication device can be Figure 1 The network device 110a in the middle, or it could be Figure 1 The chip (system) in the network device 110a.

[0120] Please see Figure 4, Figure 4 This is a flowchart illustrating the communication method 400 provided in an embodiment of this application. Figure 4 Taking a terminal device as the first communication device and a first network device as the second communication device as an example, this method is introduced from the perspective of the interaction between the terminal device and the first network device. It should be understood that the communication method can also be implemented by other devices, such as chips or communication devices with communication functions.

[0121] S401. The first network device sends a capability query message to the terminal device, which is used to query the capabilities of the terminal device.

[0122] Accordingly, the terminal device receives a capability query message from the first network device.

[0123] S402. The terminal device sends capability information to the first network device, the capability information including a second set of capability parameters, the second set of capability parameters indicating at least one capability of the terminal device.

[0124] The terminal device receives a capability query message and sends capability information to the first network device. Correspondingly, the first network device receives the capability information from the terminal device. This capability information includes a second set of capability parameters, which includes at least one capability parameter indicating at least one capability of the terminal device.

[0125] S403. The first network device sends a first RRC message to the terminal device, which is used to configure the first RRC connection.

[0126] Accordingly, the terminal device receives a first RRC message from the first network device. The first RRC message can be an RRC reconfiguration message or an RRC recovery message. The first RRC message includes parameter information for configuring the first RRC connection. The first RRC message includes radio bearer configuration, measurement configuration, CA combination configuration, etc., for the first RRC connection. The content of the first RRC message can be determined based on the capability information reported by the terminal device; in other words, the configuration indicated by the first RRC message can be determined based on the second set of capability parameters. For example, the CA combination configuration included in the first RRC message can be determined based on the BC capabilities reported by the terminal device through the capability information. It can be understood that the aforementioned CA combination configuration can be understood as the configuration of one or more cells or cell groups.

[0127] S404. The terminal device sends a second RRC message to the first network device. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message.

[0128] Accordingly, the first network device receives the second RRC message from the terminal device. This second RRC message can be a response to the first RRC message. For example, the first RRC message may be an RRC reconfiguration message, and the second RRC message may be an RRC reconfiguration completion message; or, for example, the first RRC message may be an RRC recovery message, and the second RRC message may be an RRC recovery completion message.

[0129] In this embodiment, the second RRC message may include a first capability parameter set, used to indicate at least one capability of the terminal device. It is understood that the first capability parameter set includes at least one capability parameter. Compared to the second capability parameter set, the capability indicated by the first capability parameter set is a dynamic capability. Alternatively, compared to the terminal device reporting capabilities through capability information, the terminal device reporting capabilities through the second RRC message can be considered as dynamically reporting capabilities. Considering that currently only a few specific capabilities are supported for message reporting via RRC reconfiguration, as the number of capabilities increases, the number of capabilities reported through capability information also increases, resulting in significant overhead for capability information. In this embodiment, the terminal device is allowed to report capabilities other than the aforementioned specific capabilities through the second RRC message. As the number of capabilities increases, newly added capabilities can be reported through the second RRC message to minimize the overhead of capability information. For example, the terminal device is allowed to report capabilities other than the aforementioned specific capabilities through the second RRC message, or the first capability parameter set may include one or more capability parameters other than the aforementioned specific capabilities. The first capability parameter set is determined based on the first RRC message. How the terminal device determines the first set of capability parameters based on the first RRC message will be described below and will not be discussed here.

[0130] The protocol may specify or stipulate that terminal devices are allowed to report capabilities via RRC messages, or that terminal devices are allowed to report capabilities in RRC connection state. Compared to reporting capabilities via capability information, terminal devices reporting capabilities via RRC messages is a dynamic reporting of capabilities. From this perspective, it can also be specified or stipulated that terminal devices are allowed to report dynamic capabilities, or that terminal devices are allowed to report capabilities in a dynamic reporting manner. In this case, the terminal device can report capabilities via RRC messages.

[0131] Different network devices may have varying capabilities. For example, some network devices support terminal devices reporting their capabilities based on RRC configuration messages, while others, due to capability limitations, are insufficient to support this. If terminal devices default to allowing every network device to report its capabilities via RRC messages, it would obviously result in unnecessary overhead from RRC messages. To avoid this wasted overhead, the first network device can use a capability query message to indicate to the terminal device whether it is allowed to report its capabilities based on RRC configuration messages.

[0132] For example, a capability query message may include second indication information, which indicates that the terminal device is allowed to report its capabilities according to the RRC configuration message, or that the terminal device is allowed to report dynamic capabilities, or that the terminal device is allowed to report capabilities dynamically, or that the terminal device is allowed to report capabilities in RRC connected state; or that the terminal device is allowed to report capabilities in an RRC message. If the first network device allows the terminal device to report its capabilities according to the RRC configuration message, then the first network device supports the terminal device reporting its capabilities according to the RRC configuration message. From this perspective, the second indication information may indicate: the first network device supports the terminal device reporting its capabilities according to the RRC configuration message, or the second indication information indicates that the first network device supports the terminal device reporting dynamic capabilities, or the second indication information indicates that the first network device supports the terminal device reporting capabilities dynamically, or the second indication information indicates that the first network device supports the terminal device reporting capabilities in RRC connected state; or the second indication information indicates that the first network device supports the terminal device reporting capabilities in an RRC message.

[0133] Optionally, if the capability query message includes second indication information, it may implicitly indicate that the terminal device is allowed to report more capabilities based on the RRC configuration message, or it may implicitly indicate that the capabilities allowed to be reported by the terminal device based on the RRC configuration message are not limited to the currently supported capabilities based on the RRC reconfiguration completion message reporting.

[0134] In possible implementations, the first network device may also instruct the terminal device to report dynamic capabilities via a first RRC message. For example, the first RRC message may include third indication information, which is used to request the terminal device to report a first set of capability parameters. When the terminal device is allowed to report its capabilities according to the RRC configuration message, the first network device may request the terminal device to report the desired capabilities via the first RRC message. For example, the first RRC message may include third indication information, which is used to request the terminal device to report a first set of capability parameters for the first capability. This first capability is the capability that the first network device wants the terminal device to report, such as sounding reference signal (SRS) carrier round-robin capability, SRS transmit switching capability, uplink transmit switching capability, uplink transmit power level, measurement capability, supported AI / machine learning (ML) models and AI / ML parameters, etc. It should be noted that whether the first RRC message includes third indication information is independent of whether the capability query message includes second indication information. For example, when the capability query message includes second indication information, the first RRC message may or may not include the third indication information. Alternatively, when the first RRC message includes the third indication information, the capability query message may include the second indication information, or it may include the second indication information.

[0135] Depending on the capabilities of the terminal device, the dynamic capabilities that the terminal device supports reporting may vary, or the capability parameters that the terminal device supports reporting may also differ. If the terminal device does not support reporting the capabilities / capability parameters requested by the first network device based on RRC messages, then the third indication information in the first RRC message is unnecessary. To avoid the first network device sending unnecessary third indication information, the terminal device can inform the first network device of the capabilities / capability parameters that it supports reporting via RRC messages.

[0136] For example, the capability information may include first information indicating whether the terminal device supports reporting capability information in response to an RRC configuration message. If the first information indicates that the terminal device supports reporting capability information in response to an RRC configuration message, the first RRC message may include third indication information, which may indicate that the requesting terminal device should report a first set of capability parameters. If the first information indicates that the terminal device does not support reporting capability information in response to an RRC configuration message, the first RRC message does not include the third indication information.

[0137] Furthermore, the terminal device can also inform the first network device whether it supports reporting capability information for a certain feature / capability. For example, the capability information may include second information, which indicates whether the terminal device supports reporting capability information for the first frequency band combination in response to the RRC configuration message. If the second information indicates that the terminal device supports reporting capability information for the first frequency band combination in response to the RRC configuration message, the first RRC message may include third indication information, which instructs the terminal device to report capability information / capability parameters corresponding to the first frequency band combination. If the second information indicates that the terminal device does not support reporting capability information for the first frequency band combination in response to the RRC configuration message, the first RRC message does not include the third indication information.

[0138] For example, capability information may include third information, which indicates whether the terminal device supports reporting capability information for a first capability in response to an RRC configuration message. If the third information indicates that the terminal device supports reporting capability information for a first capability in response to an RRC configuration message, the first RRC message may include third indication information, which may indicate that the terminal device reports capability information / capability parameters corresponding to the first capability. If the first information indicates that the terminal device does not support reporting capability information for a first capability in response to an RRC configuration message, the first RRC message does not include the third indication information. Here, capability can also be understood as feature, or capability having corresponding features. From this perspective, the third information used to indicate whether the terminal device supports reporting capability information for a first capability in response to an RRC configuration message can also be replaced by the third information used to indicate whether the terminal device supports reporting capability information for a first feature in response to an RRC configuration message. The first feature may include one or more of the following: "sidelink enhancement" or "mobility enhancement", SRS carrier round-robin capability, SRS transmit handover capability, uplink transmit handover (UplinkTxSwitching) capability, uplink transmit power level, measurement capability, supported AI / ML models and AI / ML parameters, etc.

[0139] The first, second, and third information described above are merely examples; capability information may also include other capability parameters / information used to indicate support for reporting in response to RRC configuration messages. Optionally, capability information may include one or more of the first, second, or third information.

[0140] A certain capability / feature can be characterized by the corresponding capability parameter value. For example, a terminal device has an uplink transmission handover capability, which can be characterized by the handover time of the uplink transmission handover. It is understood that different handover times correspond to different uplink transmission handover capabilities. In possible implementations, for a certain capability, a default parameter value can be predefined to represent the initial capability of that capability. For example, if the handover time of the uplink transmission handover when the terminal device supports uplink transmission handover is predefined as a first value (e.g., 210µs), then the uplink transmission handover capability is the first value. In this case, the terminal device does not need to separately indicate the actual uplink transmission handover time it supports in the capability information to determine the uplink transmission handover capability supported by the terminal device. For example, for a first capability, a first capability parameter value can be predefined. When the capability indicated by the second capability parameter set reported by the terminal device includes the first capability, it may not include the first capability parameter value. However, since the first capability parameter value is predefined, the first network device can determine the first capability based on the predefined first capability parameter value.

[0141] For example, assuming the capability information indicates that the terminal device supports uplink transmission handover between band A and band B, this capability information may not include one or more capability parameter values, such as the handover time, handover mode (switchUL or dualUL for uplink), and downlink bands affected by the uplink handover. Default values ​​for these capability parameter values ​​can be predefined; for example, the default value for the handover time supported by the terminal device between band A and band B is a first value (e.g., 210µs). With the above capability parameter values ​​defaulted, the first network device can determine the handover time supported by the terminal device between band A and band B based on the capability information and the default first value.

[0142] The second RRC message can also indicate a second value for the handover time (e.g., 35µs). Generally, the default capability parameter value represents a weaker capability. If the actual capability of the terminal device is higher than the capability represented by the default capability parameter value, the first network device can inform the terminal device through the second RRC message. Continuing the example above, if the terminal device supports a handover time of the second value (e.g., 35µs) between band A and band B, the second RRC message sent by the terminal device to the first network device can include a second parameter to indicate that the terminal device supports a handover time of the second value between band A and band B. Typically, the capability represented by the capability parameter value reported through the second RRC message is stronger, or in other words, the capability reported in the second RRC message is higher than the capability reported in the capability information.

[0143] In one possible implementation, if the first network device wants to obtain the actual size of the first capability, the first RRC message may include information about the first capability. Accordingly, in response to the first RRC message, the terminal device may report the capability parameter value corresponding to the first capability in a second RRC message. For example, if the first capability corresponds to a predefined first capability parameter value, the second RRC message may include the second capability parameter value corresponding to the first capability.

[0144] As mentioned above, the terminal device receives a first RRC message, determines a first set of capability parameters based on the first RRC message, and sends a second RRC message including the first set of capability parameters to the first network device. The capabilities indicated by the first set of capability parameters include, but are not limited to, a few specific capabilities currently only supported. That is, in this embodiment, the terminal device is allowed to report capabilities, including but not limited to, a few specific capabilities currently only supported, in response to the RRC configuration message. Thus, the terminal device does not need to traverse and match the capabilities reported through capability information with the first RRC message, blindly guessing the configuration selected by the first network device, which reduces processing complexity. For example, the BC capabilities reported by the terminal device include bandA+bandB+bandC (referred to as BC capability 1) and bandA+bandB+bandD (referred to as BC capability 2). The first RRC message includes a CA combination, which is a CA combination consisting of carrier 1 on bandA and carrier 2 on bandB. The terminal device can determine the application's capabilities based on the CA combination configured by the network and inform the network device through the second RRC message. Compared to the previous method where the network device instructs the terminal device on the configuration and the terminal device then traverses the capabilities of the Common Base (BC) to determine which BC matches the network configuration, this solution allows the terminal device to autonomously select the capability parameters to be applied under the CA combination of the current network configuration and then inform the network device. This avoids the problem of misalignment between the network and the terminal device caused by blind matching by the terminal device, and reduces the compatibility risk between the terminal device and the network device.

[0145] It is understandable that allowing terminal devices to respond to RRC configuration message reporting capabilities includes, but is not limited to, a few specific capabilities currently only supported. The second RRC message may contain a lot of content, which would prolong the completion of RRC connection configuration. Therefore, embodiments of this application provide communication method 500 and communication method 600. Both communication method 500 and communication method 600 can reduce the latency of RRC connection configuration completion.

[0146] Please see Figure 5 , Figure 5 This is a flowchart illustrating the communication method 500 provided in an embodiment of this application. Figure 5Taking a terminal device as the first communication device and a first network device as the second communication device as an example, this method is introduced from the perspective of the interaction between the terminal device and the first network device. It should be understood that the communication method can also be implemented by other devices, such as chips or communication devices with communication functions.

[0147] like Figure 5 As shown, the communication method 500 provided in this application embodiment includes the following steps.

[0148] S501, The first network device sends a first RRC message to the terminal device, which is used to configure the first RRC connection.

[0149] For details on the specific implementation of S501, please refer to the relevant content of S403 mentioned above, which will not be repeated here.

[0150] S502, The terminal device sends a second RRC message to the first network device. The second RRC message includes a first set of capability parameters. The first RRC message includes a first segment and a second segment. The first segment is used to indicate that the first RRC connection configuration has been successfully completed.

[0151] Upon receiving the first RRC message, the terminal device can send a second RRC message to the first network device. The content of the second RRC message is determined based on the first RRC message. For details regarding the content of the second RRC message, please refer to the relevant content in S404 above, which will not be repeated here.

[0152] Considering the large amount of content in the second RRC message, the completion delay of the RRC connection configuration feedback is relatively long, which in turn prevents timely commencement of service transmission, affecting system performance and network key performance indicators (KPIs). In this embodiment, the second RRC message can be sent in segments. For example, the second RRC message includes multiple segments. When the terminal device sends the second RRC message, it is actually sending these multiple segments. The first network device can parse each segment independently, without needing to receive all segments before parsing. Upon receiving any segment, the first network device can assume successful completion of the first RRC connection configuration and can schedule service data to the terminal device. In other words, any segment included in the second RRC message can indicate successful completion of the first RRC connection configuration. For example, if the first RRC message includes a first segment and a second segment, both the first and second segments can indicate successful completion of the first RRC connection configuration. Compared to the first network device only considering the first RRC connection configuration successful after receiving the second RRC message, indicating the successful completion of the first RRC connection configuration in segments will reduce the completion latency of the RRC connection configuration.

[0153] For example, the first RRC message includes a first segment and a second segment, and the terminal device sending the second RRC message includes sending both the first and second segments. The first network device receives the first segment and considers the first RRC connection configuration successfully completed. The first network device receives the second segment and considers the first RRC connection configuration successfully completed. Since the first network device considers the first RRC connection configuration successfully completed, it can schedule service transmission based on the first RRC message and the capabilities reported by the terminal device through the second RRC message. In other words, the first network device considers the first RRC connection configuration successfully completed in advance and schedules service transmission ahead of time, which reduces service transmission latency compared to the first network device waiting to receive the entire content of the second RRC message before scheduling service transmission.

[0154] Please see Figure 6 , Figure 6 This is a flowchart illustrating the communication method 600 provided in an embodiment of this application. Figure 6 Taking a terminal device as the first communication device and a first network device as the second communication device as an example, this method is introduced from the perspective of the interaction between the terminal device and the first network device. It should be understood that the communication method can also be implemented by other devices, such as chips or communication devices with communication functions.

[0155] like Figure 6 As shown, the communication method 600 provided in this application embodiment includes the following steps.

[0156] S601. The first network device sends a first RRC message to the terminal device. The first RRC message is used to configure the first RRC connection.

[0157] For details on the specific implementation of S601, please refer to the relevant content of S403 mentioned above, which will not be repeated here.

[0158] S602. The terminal device sends a third RRC message to the first network device. The third RRC message is used to indicate that the first RRC connection configuration has been successfully completed.

[0159] Upon receiving the first RRC message, the terminal device can send a third RRC message to the first network device in response. This third message can be used to indicate successful completion of the first RRC connection configuration, which is equivalent to the terminal device indicating in advance that the first RRC connection configuration has been successfully completed. Therefore, the first network device does not need to wait for the second RRC message from the terminal device to schedule service transmission.

[0160] S603. The terminal device sends a second RRC message to the first network device. The second RRC message includes a first set of capability parameters, which are determined based on the first RRC message.

[0161] The terminal device receives the first RRC message, determines the second RRC message based on the first RRC message, and sends the second RRC message to the first network device. For a detailed implementation of S603, please refer to the relevant content of S404 above; it will not be repeated here.

[0162] It should be noted that S602 and S603 can be sent together, or S602 can be sent before S603, or S602 can be sent after S603. The first network device, upon receiving the third RRC message but before receiving the second RRC message, will also consider the first RRC connection configuration successfully completed.

[0163] Optionally, the third RRC message also includes first indication information, which indicates the reception of the second RRC message. The first network device receives the third RRC message and, based on the first indication information, determines that a second RRC message needs to be received. This can also be understood as the first indication information indicating whether the terminal device will send a second RRC message after the third RRC message. Through the first indication information, the network device can anticipate whether a second RRC message will subsequently be sent to indicate the first capability parameter set. When the first indication information indicates that the terminal device will subsequently send a second RRC message, the first network device can wait to receive the second RRC message and then reconfigure and schedule the terminal device according to the first capability parameter set indicated by the second RRC message; when the first indication information indicates that the terminal device will not subsequently send a second RRC message, the first network device does not need to wait to receive the second RRC message and can schedule the terminal device according to the configuration in the first RRC message.

[0164] In one possible implementation, the first indication information is 1 bit. If the third RRC message carries this 1 bit, or if the third RRC message carries this 1 bit and the value of this 1 bit is "1", then the terminal device is instructed to send a second RRC message after the third RRC message. If the third RRC message does not carry this 1 bit, or if the third RRC message carries this 1 bit and the value of this 1 bit is "0", then the terminal device is instructed not to send a second RRC message after the third RRC message.

[0165] In communication method 600, a first capability parameter set is reported via a second RRC message, and a third RRC message is used to separately inform the first network device of the successful completion of RRC connection configuration. Compared to using a second RRC message to both indicate successful completion of RRC connection configuration and report the first capability parameter set, this avoids the problem of excessive delay in RRC connection configuration completion and inability to start service transmission in a timely manner due to the excessive length of the second RRC message. For example, the terminal device first informs the first network device of the successful completion of the first RRC connection configuration via the third RRC message. Upon receiving the third RRC message, the first network device can schedule service transmission without waiting to receive the second RRC message, thereby reducing the delay in RRC connection configuration completion and the delay in service transmission.

[0166] Optionally, after receiving the third RRC message, the first network device can confirm that the terminal device has completed the first RRC connection configuration and can schedule the terminal device to perform service transmission according to the configuration parameters in the first RRC message.

[0167] Considering that in addition to reporting its capabilities to the network device via capability information, a terminal device can also report some of its capabilities to the network device via RRC messages, if the terminal device and the network device have inconsistent understandings of the terminal device's capabilities, normal communication between them will be impossible. Therefore, this application provides a communication method 700. Through communication method 700, the terminal device can clearly determine which capabilities the network device is scheduling based on, thereby ensuring normal communication between the terminal device and the first network device as much as possible.

[0168] Please see Figure 7 , Figure 7 This is a flowchart illustrating the communication method 700 provided in an embodiment of this application. Figure 7 Taking a terminal device as the first communication device and a first network device as the second communication device as an example, this method is introduced from the perspective of the interaction between the terminal device and the first network device. It should be understood that the communication method can also be implemented by other devices, such as chips or communication devices with communication functions.

[0169] like Figure 7 As shown, the communication method 700 provided in this application embodiment includes the following steps.

[0170] S701. The first network device sends a first RRC message to the terminal device. The first RRC message is used to configure the first RRC connection.

[0171] For details on the specific implementation of S701, please refer to the relevant content of S403 mentioned above, which will not be repeated here.

[0172] S702. The terminal device sends a second RRC message to the first network device. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message.

[0173] For details on the specific implementation of S702, please refer to the relevant content of S404 or S502 mentioned above, which will not be repeated here.

[0174] S703, The terminal device uses the first set of capability parameters to communicate with the first network device.

[0175] It is understandable that before the first network device sends the first RRC message to the terminal device, the terminal device will report a second set of capability parameters to the first network device using capability information. Subsequently, the terminal device reports the first set of capability parameters to the first network device via a second RRC message. Therefore, the terminal device sends both a first set of capability parameters and a second set of capability parameters to the first network device. The parameter values ​​corresponding to the same capability in the first set of capability parameters may differ from those in the second set. If the terminal device and the first network device have inconsistent understandings of the terminal device's capabilities, they will be unable to communicate normally. To ensure that the terminal device and the first network device have consistent understandings of the terminal device's capability parameters, it can be agreed that when the terminal device reports both a first set of capability parameters and a second set of capability parameters, the first network device will, by default, schedule the terminal device based on the first set of capability parameters and communicate with the terminal device using the first set of capability parameters.

[0176] Alternatively, the first network device may notify the terminal device of the set of capability parameters used by the first network device. For example, this includes, but is not limited to, the following two methods.

[0177] Method 1: The first network device uses the first set of capability parameters by receiving the confirmation instruction of the second RRC message.

[0178] For example, a first network device receives a second RRC message and sends an acknowledgment of the second RRC message to a terminal device. This acknowledgment indicates that the first network device has successfully received the second RRC message. Upon receiving this acknowledgment, the terminal device considers that the first network device has successfully received the second RRC message and will then use the first capability parameter set. This acknowledgment can be a low-layer data packet acknowledgment (ACK), such as a hybrid automatic repeat request (HARQ) ACK or an automatic repeat request (ARQ) ARQ ACK. This ACK feedback can be transmitted by the physical layer, MAC layer, RLC layer, or other low-layer protocol stack entities in future access technologies.

[0179] Method 2: The first network device explicitly indicates whether to use the first capability parameter set through the fourth indication information.

[0180] For example, after receiving the second RRC message, the first network device may send a fourth indication message to the terminal device. This fourth indication message is used to instruct the first network device to confirm or refuse to use the first capability parameter set to communicate with the terminal device, or to instruct the first network device to accept or refuse to use the first capability parameter set to configure or schedule the terminal device. If the fourth indication message instructs the first network device to confirm using the first capability parameter set to communicate with the terminal device, then the terminal device uses the first capability parameter set to communicate with the first network device. If the fourth indication message instructs the first network device to refuse using the first capability parameter set to communicate with the terminal device, then the terminal device uses the second capability parameter set to communicate with the first network device.

[0181] It is understandable that before communicating with the first network device using the first capability parameter set, the terminal device receives an acknowledgment message from the first network device regarding the second RRC message, or receives a fourth indication message, which instructs the first network device to confirm the application of the first capability parameter set for communication with the terminal device. However, it can be agreed that the terminal device and the first network device communicate based on the first capability parameter set. Therefore, receiving an acknowledgment message from the first network device regarding the second RRC message or receiving the fourth indication message before communicating with the first network device using the first capability parameter set is not a mandatory step. Figure 7 The image is indicated by a dashed line.

[0182] Communication method 700 provides capability parameters for various terminal devices and the first network device to be used in alignment, thereby ensuring normal communication between the terminal devices and the first network device as much as possible.

[0183] One or more of the communication methods 400, 500, and 700 described above can be combined. For example, communication methods 400 and 500 can be combined, as can communication methods 400 and 700, or communication methods 400, 500, and 700. Similarly, one or more of the communication methods 400, 600, and 700 described above can be combined. For example, communication methods 400 and 600 can be combined, as can communication methods 400 and 700, or communication methods 400, 600, and 700.

[0184] For example, see Figure 8 This is a schematic flowchart of the communication method 800 provided in an embodiment of this application. Communication method 800 can be viewed as a combination of communication method 400, communication method 500, and communication method 700. Figure 8 As shown, the communication method 800 includes the following steps.

[0185] S801. The first network device sends a capability query message to the terminal device. This capability query message is used to query the capabilities of the terminal device.

[0186] Accordingly, the terminal device receives a capability query message from the first network device. The specific implementation of S801 can be found in the relevant content of the aforementioned communication method 400, and will not be repeated here. For example, the capability query message may include second indication information, which indicates that the terminal device is allowed to report its capabilities according to the RRC configuration message, or the second indication information indicates that the first network device allows the terminal device to report its capabilities according to the RRC configuration message.

[0187] S802, The terminal device sends capability information to the first network device, the capability information including a second set of capability parameters, the second set of capability parameters indicating at least one capability of the terminal device.

[0188] The terminal device receives a capability query message and sends capability information to the first network device. Correspondingly, the first network device receives the capability information from the terminal device. This capability information includes a second parameter capability set, the details of which can be found in the relevant content of the aforementioned communication method 400, and will not be repeated here. For example, the capability information may include one or more of the aforementioned first, second, or third information.

[0189] S803. The first network device sends a first RRC message to the terminal device. The first RRC message is used to configure the first RRC connection.

[0190] Accordingly, the terminal device receives a first RRC message from the first network device. The specific implementation of the first RRC message can be found in the relevant content of the aforementioned communication method 400, and will not be repeated here. For example, the first RRC message may include third indication information, which is used to request the terminal device to report a first set of capability parameters, or the third indication information is used to request the terminal device to report a first set of capability parameters for a first capability / first characteristic. As another example, the first RRC message may include information about a first capability to request the terminal device to report the capability parameter value corresponding to the first capability.

[0191] S804. The terminal device sends a second RRC message to the first network device. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message.

[0192] Accordingly, the first network device receives a second RRC message from the terminal device. The content of the second RRC message can be found in the relevant content of the aforementioned communication method 400, and will not be repeated here.

[0193] Optionally, the second RRC message may include multiple segments, which the terminal device may send to the first network device. The first network device considers the first RRC connection configuration to be successfully completed upon receiving any one of the segments. For details, please refer to the relevant content in S502 of the aforementioned communication method 500, which will not be repeated here.

[0194] S805, the first network device sends a fourth indication message to the terminal device, the fourth indication message being used to instruct the first network device to confirm or refuse to use the first capability parameter set to communicate with the terminal device.

[0195] Accordingly, the terminal device receives a fourth indication message from the first network device. If the fourth indication message indicates that the first network device confirms communication with the terminal device using the first set of capability parameters, then the terminal device communicates with the first network device using the first set of capability parameters. If the fourth indication message indicates that the first network device refuses to communicate with the terminal device using the first set of capability parameters, then the terminal device communicates with the first network device using the second set of capability parameters.

[0196] Understandably, S805 is not a mandatory step, therefore, in Figure 8 The image is indicated by a dashed line.

[0197] S806. The first network device sends a fourth RRC message to the terminal device. This fourth RRC message is used to configure the second RRC connection.

[0198] Accordingly, the terminal device receives a fourth RRC message from the first network device, which may be determined by the first network device based on the second RRC message. That is, upon receiving the second RRC message, the first network device can reconfigure the terminal device according to the first set of capability parameters. For example, if the first set of capability parameters affects the previous configuration of the first network device (e.g., the configuration in the first RRC message), then the first network device may send a fourth RRC message.

[0199] It should be noted that the second RRC connection and the first RRC connection in S803 can be the same RRC connection; however, the configuration corresponding to the second RRC connection is different from that of the first RRC connection. The execution of S806 depends on whether the first network device reconfigures the terminal device. Even if the first capability parameter set includes capabilities that affect the previous configuration of the first network device, the first network device may not need to reconfigure the terminal device. Therefore, S806 is not a mandatory step. Figure 8 The image is indicated by a dashed line.

[0200] Additionally, it should be noted that, Figure 8 In steps S801 and S802, the first network device can be replaced by a second network device, which can store the second capability parameter set of the terminal device in the core network device. When the first network device needs to obtain the second capability parameter set of the terminal device, it can obtain the second capability parameter set from the core network device.

[0201] Figure 8 Taking the combination of communication methods 400, 500, and 700 as an example. It can be understood that when communication methods 400, 600, and 700 are combined, S807 can be executed before S804, that is, the terminal device sends a third RRC message to the first network device. For details, please refer to the relevant content in the aforementioned communication method 600, which will not be repeated here.

[0202] In the embodiments provided above, the methods provided by the embodiments of this application are described using a terminal device and a first network device as examples. In this application, each embodiment can be implemented independently or in combination based on certain inherent connections; in each embodiment, different implementation methods can be implemented in combination or independently. To achieve the functions in the methods provided by the embodiments of this application above, the steps executed by the terminal device can be implemented by different functional entities constituting the terminal device. The steps executed by the network device can be implemented by different functional entities constituting the network device. For example, the first network device can be a CU-DU architecture, where the CU can generate a first RRC message and the DU can send the first RRC message. To achieve the functions in the methods provided by the embodiments of this application above, the terminal device and the network device can include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. Whether a particular function is executed in the form of hardware structures, software modules, or hardware structures plus software modules depends on the specific application and design constraints of the technical solution.

[0203] Based on the same concept as the method embodiments, this application provides a communication device. The communication device used to implement the above method in the embodiments of this application is described below with reference to the accompanying drawings. The content above can be used in subsequent embodiments, and repeated content will not be repeated.

[0204] Figure 9 This is a schematic block diagram of a communication device 900 provided in an embodiment of this application. The communication device 900 can be a terminal device or a first network device as described in the above embodiments. For example, the communication device 900 can be... Figure 1 The communication device 900 can be a terminal device; or, the communication device 900 can be a chip (system) in the terminal device; or, the communication device 900 can be a software module of the terminal device. The communication device 900 can correspondingly implement the functions or steps implemented by the terminal device in the various method embodiments described above. For example, the communication device 900 can be... Figure 1The communication device 900 can be a network device; or, the communication device 900 can be a chip (system) within the network device; or, the communication device 900 can be a software module of the network device. The communication device 900 can correspondingly implement the functions or steps implemented by the network device in the various method embodiments described above. The communication device 900 may include a processing module 910 and a transceiver module 920. Optionally, it may also include a storage module, which can be used to store instructions (code or program) and / or data. The storage module may be, for example, a memory. The processing module 910 and the transceiver module 920 may be coupled to the storage module. For example, the processing module 910 can read instructions (code or program) and / or data from the storage module to implement the corresponding method. When the communication device 900 is a chip in a terminal device or network device, the storage module may be a storage module within the chip, such as a register or cache. For example, the storage module can also be an external storage module located within the terminal device or network device, such as read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, random access memory (RAM), etc. The aforementioned units can be configured independently, or partially or completely integrated.

[0205] Processing module 910 may be a processor or controller, such as a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing unit (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc. Transceiver module 920 is a transceiver, interface circuit, bus, pin, or other possible communication interface for receiving signals from other devices. For example, when the device is implemented as a chip, transceiver module 920 is an interface circuit for the chip to receive signals from other chips or devices, or an interface circuit for the chip to send signals to other chips or devices.

[0206] In one implementation, the communication device 900 can correspondingly implement the behavior and functions of the terminal device in the above method embodiments. The communication device 900 can be the terminal device, a component (e.g., a chip or circuit) applied in the terminal device, a part of a chip or chipset in the terminal device used to execute related method functions, or a software module capable of implementing the methods executed by the terminal device in the above communication method; there are no limitations. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0207] For example, transceiver module 920 is used to receive a first RRC message from a first network device and send a second RRC message. The first RRC message is used to configure a first RRC connection. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message. The second RRC message includes a first segment and a second segment. Processing module 910 is used to generate the second RRC message. The transceiver module 920's sending of the second RRC message includes sending a first segment indicating successful completion of the first RRC connection configuration.

[0208] For example, transceiver module 920 is used to receive a first RRC message from a first network device, send a third RRC message, and send a second RRC message. The first RRC message is used to configure a first RRC connection. The third RRC message is used to indicate successful completion of the first RRC connection configuration. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message. Processing module 910 is used to generate the third RRC message. Processing module 910 is also used to generate the second RRC message.

[0209] As an optional implementation, the third RRC message includes first indication information, which is used to indicate the receipt of the second RRC message.

[0210] For example, the transceiver module 920 is used to receive a capability query message from the first network device, which queries the capabilities of the communication device 900. The capability query message includes second indication information, which instructs the communication device 900 to report its capabilities according to the RRC configuration message.

[0211] As an optional implementation, the transceiver module 920 is also used to transmit capability information, which includes a second set of capability parameters indicating at least one capability supported by the communication device 900.

[0212] As an optional implementation, the capability information includes one or more of the following: first information, second information, or third information. The first information indicates whether the communication device 900 supports reporting capability information in response to an RRC configuration message. The second information indicates whether the communication device 900 supports reporting capability information for a first frequency band combination in response to an RRC configuration message. The third information indicates whether the communication device 900 supports reporting capability information for a first capability in response to an RRC configuration message.

[0213] As an optional implementation, the second capability parameter set indicates that the capabilities supported by the communication device 900 include a first capability, which corresponds to a first capability parameter value, which is predefined.

[0214] As an optional implementation, the first RRC message also includes third indication information, which is used to request the communication device 900 to report the first capability parameter set; or, the third indication information is used to request the communication device 900 to report the first capability parameter set related to the first capability.

[0215] As an optional implementation, the first RRC message includes information about the first capability, and the second RRC message also includes the second capability parameter value corresponding to the first capability.

[0216] As an optional implementation, the first capability in the first RRC message is less than or equal to the first capability in the second RRC message.

[0217] For example, transceiver module 920 is used to receive a first RRC message from a first network device, send a second RRC message, and communicate with the first network device using a first set of capability parameters. The first RRC message is used to configure a first RRC connection. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message. Processing module 910 is used to generate the second RRC message.

[0218] As an optional implementation, the transceiver module 920 is also used to receive an acknowledgment message for the second RRC message before communicating with the first network device using the first capability parameter set. The acknowledgment message indicates that the first network device has successfully received the second RRC message.

[0219] As an optional implementation, the transceiver module 920 is also used to receive a fourth indication message, which is used to instruct the first network device to confirm or refuse to use the first capability parameter set to communicate with the terminal device; wherein, when the fourth indication message instructs the first network device to refuse to use the first capability parameter set to communicate with the terminal device, the transceiver module 920 uses a second capability parameter set to communicate with the first network device, which is included in the capability information of the communication device 900.

[0220] In another implementation, the communication device 900 can correspondingly implement the behavior and functions of the first network device in the above method embodiments. The communication device 900 can be a network device, a component (e.g., a chip or circuit) within a network device, a part of a chip or chipset in a network device used to execute the relevant method functions, or a software module in a network device capable of implementing the above communication method; there are no limitations. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0221] For example, transceiver module 920 is used to send a first RRC message and receive a first segment from a second RRC message. The first RRC message is used to configure a first RRC connection. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message. The second RRC message includes a first segment and a second segment, where the first segment indicates successful completion of the first RRC connection configuration. Processing module 910 is used to generate the first segment.

[0222] For example, the transceiver module 920 is used to send a first RRC message, receive a third RRC message, and receive a second RRC message. The first RRC message is used to configure a first RRC connection. The third RRC message is used to indicate successful completion of the first RRC connection configuration. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message. The processing module 910 is used to generate the first RRC message.

[0223] As an optional implementation, the third RRC message includes first indication information, which is used to indicate the receipt of the second RRC message.

[0224] For example, the transceiver module 920 is used to send a capability query message to the terminal device, which queries the capabilities of the terminal device. This capability query message includes second indication information, which instructs the terminal device to report its capabilities according to the RRC configuration message.

[0225] As an optional implementation, the transceiver module 920 is also used to receive capability information, which includes a second set of capability parameters indicating at least one capability parameter supported by the terminal device.

[0226] As an optional implementation, the capability information includes one or more of the following: first information, second information, or third information. The first information indicates whether the terminal device supports reporting capability information in response to an RRC configuration message. The second information indicates whether the terminal device supports reporting capability information for a first frequency band combination in response to an RRC configuration message. The third information indicates whether the terminal device supports reporting capability information for a first capability in response to an RRC configuration message.

[0227] As an optional implementation, the second capability parameter indicates that the capabilities supported by the terminal device include the first capability, which corresponds to the first capability parameter value, which is predefined.

[0228] As an optional implementation, the first RRC message may further include third indication information, which is used to request the terminal device to report the first capability parameter set; or, the third indication information is used to request the terminal device to report the first capability parameter set related to the first capability.

[0229] As an optional implementation, the first RRC message includes information about the first capability, and the second RRC message also includes the second capability parameter value corresponding to the first capability.

[0230] As an optional implementation, the first capability in the first RRC message is less than or equal to the first capability in the second RRC message.

[0231] For example, the transceiver module 920 is used to send a first RRC message, receive a second RRC message, and communicate with the terminal device using a first set of capability parameters. The first RRC message is used to configure a first RRC connection. The second RRC message includes the first set of capability parameters, which is determined based on the first RRC message. The processing module 910 is also used to generate the first RRC message.

[0232] As an optional implementation, before the first network device communicates with the terminal device using the first set of capability parameters, the transceiver module 920 is also used to send an acknowledgment message for the second RRC message, which indicates that the first network device has successfully received the second RRC message.

[0233] As an optional implementation, the transceiver module 920 is also used to send a fourth indication message, which is used to instruct the communication device 900 to confirm or refuse to use the first capability parameter set to communicate with the terminal device; wherein, if the fourth indication message instructs the communication device 900 to refuse to use the first capability parameter set to communicate with the terminal device, the second capability parameter set is used to communicate with the terminal device, and the second capability parameter set is included in the capability information of the terminal device.

[0234] When the communication device 900 is a chip-based device or circuit, the transceiver module can be an input / output circuit and / or a communication interface; the processing module is an integrated processor, microprocessor, or integrated circuit.

[0235] Figure 10 This is a schematic block diagram of a communication device 1000 provided in an embodiment of this application. The communication device 1000 can be a terminal device or a network device (e.g., a first network device or a second network device) as described in the above embodiments. For example, the communication device 1000 can be... Figure 1 The terminal device or the chip (system) within the terminal device. In the embodiments of this application, the chip system may be composed of chips or may include chips and other discrete devices. Specific functions can be found in the descriptions of the above method embodiments. For example, the communication device 1000 may be... Figure 1 The network device or the chip (system) within the network device. In the embodiments of this application, the chip system may be composed of a chip, or it may include chips and other discrete devices. For specific functions, please refer to the description in the above method embodiments.

[0236] The communication device 1000 includes one or more processors 1001, used to implement or support the communication device 1000 in implementing the functions of the terminal device or the first network device in the methods provided in the embodiments of this application. For details, please refer to the detailed description in the method examples, which will not be repeated here. The processor 1001 can also be called a processing unit or processing module, and can implement certain control functions. The processor 1001 can be a general-purpose processor or a dedicated processor, etc. For example, it includes: a baseband processor, a central processing unit, an application processor, a modem processor, a graphics processor, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and / or a neural network processor, etc. The baseband processor can be used to process communication protocols and communication data. The central processing unit can be used to control the communication device 1000 (e.g., a network device or a terminal device), execute software programs and / or process data. Different processors can be independent devices or integrated into one or more processors, for example, integrated on one or more application-specific integrated circuits.

[0237] In one design, processor 1001 may include program 1003 (sometimes also referred to as code or instructions), which can be executed on processor 1001 to cause communication device 1000 to perform the methods described in the embodiments below. In yet another possible design, communication device 1000 includes circuitry (…). Figure 10 (Not shown), the circuit is used to implement the functions of the terminal device or network device in the above embodiments.

[0238] In one design, the communication device 1000 may include one or more memories 1002 storing a program 1004 (sometimes referred to as code or instructions), which can be run on the processor 1001 to cause the communication device 1000 to perform the methods described in the above method embodiments.

[0239] In one design, the processor 1001 and / or memory 1002 may include an artificial intelligence (AI) module 1007 and an AI module 1008, which are used to implement AI-related functions. The AI ​​modules can be implemented through software, hardware, or a combination of both. For example, the AI ​​module may include a RAN intelligent controller (RIC) module. For example, the AI ​​module may be a near real-time RIC or a non-real-time RIC.

[0240] In one possible design, the processor 1001 and / or memory 1002 may also store data. The processor and memory may be configured separately or integrated together.

[0241] In one possible design, the communication device 1000 may further include a transceiver 1005 and / or an antenna 1006. The processor 1001, sometimes referred to as a processing unit, controls the communication device 1000. The transceiver 1005, sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to realize the transmission and reception functions of the communication device 1000 through the antenna 1006.

[0242] In one possible design, the communication device 1000 may further include one or more of the following components: a wireless communication module, an audio module, an external memory interface, internal memory, a universal serial bus (USB) interface, a power management module, an antenna, a speaker, a microphone, an input / output module, a sensor module, a motor, a camera, or a display screen, etc. It is understood that in some embodiments, the communication device 1000 may include more or fewer components, or some components may be integrated, or some components may be separated. These components may be implemented in hardware, software, or a combination of software and hardware.

[0243] The communication device in the above embodiments can be a terminal device, a circuit, a chip applied in a terminal device, or other combined devices or components having the aforementioned terminal device. Alternatively, the communication device in the above embodiments can be a network device, a circuit, a chip applied in a network device, or other combined devices or components having the aforementioned network device. When the communication device is a terminal device or a network device, the transceiver module can be a transceiver, which may include an antenna and radio frequency circuits, etc., and the processing module can be a processor, such as a CPU. When the communication device is a chip system, the communication device can be an FPGA, a dedicated ASIC, a system-on-chip (SoC), a CPU, a network processor (NP), a DSP, a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips. The processing module can be the processor of the chip system. The transceiver module or communication interface can be the input / output interface or interface circuit of the chip system. For example, the interface circuit can be a code / data read / write interface circuit. The interface circuit can be used to receive code instructions (the code instructions are stored in memory and can be read directly from memory or through other devices) and transmit them to the processor; the processor can then execute the code instructions to perform the methods described in the above method embodiments. Alternatively, the interface circuit can also be a signal transmission interface circuit between a communication processor and a transceiver.

[0244] This application also provides a communication system, which includes at least one terminal device and at least one network device. The terminal device is used to implement one or more related functions of the above-described communication methods 400, 500, and 700, and the network device is used to implement one or more related functions of the above-described communication methods 400, 500, and 700. Alternatively, the terminal device is used to implement one or more related functions of the above-described communication methods 400, 600, and 700, and the network device is used to implement one or more related functions of the above-described communication methods 400, 600, and 700.

[0245] This application also provides a computer-readable storage medium including instructions that, when run on a computer, cause the computer to execute the method performed by the terminal device or network device (e.g., a first network device or a second network device) in the above-described communication method.

[0246] This application also provides a computer program product, including computer program code, which, when executed, causes a computer to perform the method executed by the terminal device or network device (e.g., a first network device or a second network device) in the above-described communication method.

[0247] This application provides a chip system including a processor and potentially a memory, for implementing the functions of a terminal device or network device (e.g., a first network device or a second network device) in the aforementioned communication method. The chip system can be composed of chips or may include chips and other discrete components.

[0248] To achieve the above Figures 9-10 In addition to the functions of the communication device, this application also provides a chip, including a processor, for supporting the communication device in implementing the functions involved in the terminal device or network device (e.g., a first network device or a second network device) in the above method embodiments. In one possible design, the chip is connected to a memory or the chip includes a memory for storing the computer programs or instructions and data necessary for the communication device.

[0249] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

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

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

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

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

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

[0255] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, include: Receive a first Radio Resource Control (RRC) message from a first network device, the first RRC message being used to configure a first RRC connection; Send a second RRC message, the second RRC message including a first set of capability parameters, the first set of capability parameters being determined based on the first RRC message; The second RRC message includes a first segment and a second segment. Sending the second RRC message includes sending the first segment, wherein the first segment indicates that the first RRC connection configuration has been successfully completed.

2. A communication method, characterized in that, include: Receive a first Radio Resource Control (RRC) message from a first network device, the first RRC message being used to configure a first RRC connection; Send a third RRC message, which indicates that the first RRC connection configuration was successfully completed; Send a second RRC message, the second RRC message including a first set of capability parameters, the first set of capability parameters being determined based on the first RRC message.

3. The method as described in claim 2, characterized in that, The third RRC message includes first indication information, which is used to indicate that the second RRC message is received.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: The system receives a capability query message from the first network device. The capability query message is used to query the capabilities of the terminal device. The capability query message includes second indication information, which is used to indicate that the terminal device is allowed to report its capabilities according to the RRC configuration message.

5. The method as described in claim 4, characterized in that, The method further includes: Send capability information, the capability information including a second capability parameter set, the second capability parameter set indicating at least one capability supported by the terminal device.

6. The method as described in claim 5, characterized in that, The capability information includes one or more of the following: The first piece of information is used to indicate whether the terminal device supports reporting capability information in response to the RRC configuration message; The second information is used to indicate whether the terminal device supports reporting capability information for the first frequency band combination in response to the RRC configuration message; The third piece of information is used to indicate whether the terminal device supports reporting capability information for the first capability in response to the RRC configuration message.

7. The method as described in claim 5 or 6, characterized in that, The second set of capability parameters indicates that the capabilities supported by the terminal device include a first capability, the first capability corresponding to a first capability parameter value, and the first capability parameter value is predefined.

8. The method as described in claim 7, characterized in that, The first RRC message also includes: The third instruction information is used to request the terminal device to report the first capability parameter set; or, the third instruction information is used to request the terminal device to report the first capability parameter set related to the first capability.

9. The method as described in claim 8, characterized in that, The first RRC message includes information about the first capability, and the second RRC message also includes a second capability parameter value corresponding to the first capability.

10. The method as described in claim 9, characterized in that, The first capability in the first RRC message is less than or equal to the first capability in the second RRC message.

11. The method according to any one of claims 5-10, characterized in that, The method further includes: Use the first set of capability parameters to communicate with the first network device.

12. The method as described in claim 11, characterized in that, Before communicating with the first network device using the first set of capability parameters, the method further includes: A confirmation message is received for the second RRC message, indicating that the first network device has successfully received the second RRC message.

13. The method according to any one of claims 5-10, characterized in that, The method further includes: A fourth indication message is received, which is used to instruct the first network device to confirm or refuse to use the first capability parameter set to communicate with the terminal device; wherein, if the fourth indication message instructs the first network device to refuse to use the first capability parameter set to communicate with the terminal device, the second capability parameter set is used to communicate with the first network device.

14. A communication method, characterized in that, include: Send a first Radio Resource Control (RRC) message, the first RRC message being used to configure a first RRC connection; Upon receiving the first segment of the second RRC message, it is determined that the first RRC connection configuration has been successfully completed. The second RRC message includes a first set of capability parameters, which is determined based on the first RRC message. The second RRC message includes the first segment and a second segment, and the first segment indicates that the first RRC connection configuration has been successfully completed.

15. A communication method, characterized in that, include: Send a first Radio Resource Control (RRC) message, the first RRC message being used to configure a first RRC connection; Receive a third RRC message, which indicates that the first RRC connection configuration was successfully completed; Receive a second RRC message, the second RRC message including a first set of capability parameters, the first set of capability parameters being determined based on the first RRC message.

16. The method as described in claim 15, characterized in that, The third RRC message includes first indication information, which is used to indicate that the second RRC message is received.

17. The method according to any one of claims 14-16, characterized in that, The method further includes: Send a capability query message, which is used to query the capabilities of the terminal device. The capability query message includes second indication information, which is used to indicate that the terminal device is allowed to report its capabilities according to the RRC configuration message.

18. The method as described in claim 17, characterized in that, The method further includes: The terminal device receives capability information, which includes a second set of capability parameters indicating at least one capability parameter supported by the terminal device.

19. The method as described in claim 18, characterized in that, The capability information includes one or more of the following: The first piece of information is used to indicate whether the terminal device supports reporting capability information in response to the RRC configuration message; The second information is used to indicate whether the terminal device supports reporting capability information for the first frequency band combination in response to the RRC configuration message; The third piece of information is used to indicate whether the terminal device supports reporting capability information for the first capability in response to the RRC configuration message.

20. The method as described in claim 18 or 19, characterized in that, The second capability parameter indicates that the terminal device supports capabilities including a first capability, the first capability corresponding to a first capability parameter value, and the first capability parameter value is predefined.

21. The method as described in claim 20, characterized in that, The first RRC message also includes: The third instruction information is used to request the terminal device to report the first capability parameter set, or the third instruction information is used to request the terminal device to report the first capability parameter set related to the first capability.

22. The method as described in claim 21, characterized in that, The second RRC message includes information about the first capability, and also includes a second capability parameter value corresponding to the first capability.

23. The method as described in claim 22, characterized in that, The first capability in the first RRC message is less than or equal to the first capability in the second RRC message.

24. The method according to any one of claims 14-23, characterized in that, The method further includes: The first set of capability parameters is used to communicate with the terminal device.

25. The method as described in claim 24, characterized in that, Before communicating with the terminal device using the first set of capability parameters, the method further includes: Send an acknowledgment message for the second RRC message, the acknowledgment message indicating that the second RRC message was successfully received.

26. The method according to any one of claims 14-23, characterized in that, The method further includes: A fourth indication message is sent, which is used to indicate whether to confirm or refuse to use the first capability parameter set to communicate with the terminal device; wherein, if the fourth indication message indicates that the first capability parameter set is refused to be used to communicate with the terminal device, the second capability parameter set is used to communicate with the terminal device.

27. A communication device, characterized in that, The communication device includes a processor and a memory, the memory for storing a computer program, and the processor for executing the computer program stored in the memory, causing the communication device to perform the method as described in any one of claims 1 and 4 to 13, or causing the communication device to perform the method as described in any one of claims 2 to 13, or causing the communication device to perform the method as described in any one of claims 14 and 17 to 26, or causing the communication device to perform the method as described in any one of claims 15 to 26.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 and 4 to 13, or causes the computer to perform the method as described in any one of claims 2 to 13, or causes the communication device to perform the method as described in any one of claims 14 and 17 to 26, or causes the communication device to perform the method as described in any one of claims 15 to 26.

29. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 and 4 to 13, or causes the computer to perform the method as described in any one of claims 2 to 13, or causes the computer to perform the method as described in any one of claims 14 and 17 to 26, or causes the communication device to perform the method as described in any one of claims 15 to 26.

30. A chip system, characterized in that, The chip system includes: A processor and an interface, the processor being configured to call and execute instructions from the interface, wherein, when the processor executes the instructions, it implements the method as described in any one of claims 1 and 4 to 13, or implements the method as described in any one of claims 2 to 13, or implements the method as described in any one of claims 14 and 17 to 26, or causes the communication device to perform the method as described in any one of claims 15 to 26.

Images