Communication methods and communication devices

Abstract

Provided are communication methods and communication devices. A method comprises: a terminal device receiving first information sent by a network device, the first information being used for configuring a group of data radio bearers, and the group of data radio bearers being used for transmitting one or more types of control information, wherein the group of data radio bearers comprises one or more data radio bearers.

Description

Communication methods and communication equipment Technical Field

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

[0002] In communication systems, to complete certain data transmission tasks, it is often necessary to transmit control information (such as radio resource control messages) via the signaling radio bearer (SRB). On the one hand, when the amount of control information to be transmitted is large, it may cause SRB congestion. On the other hand, the serial transmission characteristic of control information may lead to queuing delays. How to alleviate SRB congestion and reduce the queuing delays of control information to be transmitted are technical problems that need to be solved. Summary of the Invention

[0003] This application provides a communication method and a communication device. The various aspects covered by this application are described below.

[0004] In a first aspect, a communication method is provided, the method comprising: a terminal device receiving first information sent by a network device, the first information being used to configure a set of data radio bearers (DRBs), the set of DRBs being used to transmit one or more control information; wherein the set of DRBs includes one or more DRBs.

[0005] In a second aspect, a communication method is provided, the method comprising: a network device sending first information to a terminal device, the first information being used to configure a set of DRBs, the set of DRBs being used to transmit one or more control information; wherein the set of DRBs includes one or more DRBs.

[0006] Thirdly, a communication device is provided, which is a terminal device. The communication device includes: a receiving unit, configured to receive first information sent by a network device, the first information being configured to configure a set of DRBs, the set of DRBs being configured to transmit one or more control information; wherein the set of DRBs includes one or more DRBs.

[0007] Fourthly, a communication device is provided, which is a network device. The communication device includes: a transmitting unit, configured to transmit first information to a terminal device, the first information being configured to configure a set of DRBs, the set of DRBs being configured to transmit one or more control information; wherein the set of DRBs includes one or more DRBs.

[0008] Fifthly, a communication device is provided, including a transceiver, a memory, and a processor, wherein the memory is used to store a program, the processor is used to invoke the program in the memory, and to control the transceiver to receive or transmit signals so that the communication device performs the method as described in the first or second aspect.

[0009] A sixth aspect provides an apparatus including a processor for calling a program from a memory to cause the apparatus to perform the method as described in the first or second aspect.

[0010] In a seventh aspect, a chip is provided, including a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in the first or second aspect.

[0011] Eighthly, a computer-readable storage medium is provided having a program stored thereon that causes a computer to perform the method as described in the first or second aspect.

[0012] A ninth aspect provides a computer program product, characterized in that it includes a program that causes a computer to perform the method as described in the first or second aspect.

[0013] In a tenth aspect, a computer program is provided that causes a computer to perform the method as described in the first or second aspect.

[0014] In this embodiment, by establishing an association between a set of DRBs and one or more control information, the transmission of one or more control information using a set of DRBs is achieved. DRBs can also serve as a data transmission channel for control information. On the one hand, when the amount of control information to be transmitted is large, it can alleviate or avoid SRB congestion. On the other hand, it can reduce the queuing delay of the control information to be transmitted. Attached Figure Description

[0015] Figure 1 is a schematic diagram of the communication system used in the embodiments of this application.

[0016] Figure 2 is a schematic flowchart of the communication method provided in an embodiment of this application.

[0017] Figure 3 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0018] Figure 4 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0019] Figure 5 is a schematic diagram of the structure of the communication device provided in the embodiment of this application. Detailed Implementation

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

[0021] Communication system

[0022] Figure 1 is a system architecture example diagram of a wireless communication system 100 applicable to embodiments of this application. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 can provide network coverage for a specific geographical area and can communicate with the terminal device 120 located within that coverage area. The terminal device 120 can access a network (such as a wireless network) through the network device 110. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity; this embodiment of the application does not limit this.

[0023] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as 5G systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as sixth-generation mobile communication systems, satellite communication systems, and so on.

[0024] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes, etc. Optionally, the terminal device can act as a base station. For example, the terminal device can act as a scheduling entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) systems. For instance, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0025] The network device in this application embodiment can be a device for communicating with terminal devices. This network device can be, for example, an access network device or a core network device. The access network device can be any of the following: next generation Node B (gNB), centralized unit (CU), distributed unit (DU), centralized unit-control plane (CU-CP), or centralized unit-user plane (CU-UP). The core network equipment can be any of the following: location management function (LMF) network elements, network slice selection function (NSSF) network elements, authentication server function (AUSF) network elements, unified data management (UDM) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, user plane function (UPF) network elements, sensing function (SF) network elements, network data analytics function (NWDAF) network elements, and artificial intelligence (AI) function management entities.

[0026] Types of wireless bearers

[0027] In related technologies, the communication system standards developed by the 3rd Generation Partnership Project (3GPP) divide radio bearers into two categories: SRBs and DRBs. SRBs can be used to transmit radio resource control (RRC) messages. Each RRC message can carry a maximum of 9KB of data. Furthermore, RRC messages use serial transmission technology. For example, a new RRC message transmission is not allowed until all segments of an RRC message have been successfully transmitted. DRBs, on the other hand, are generally established by access network devices in response to requests from core network devices, primarily for application layer service transmissions. In other words, DRBs are typically used to perform application layer data transmission tasks.

[0028] For newly generated data transmission services within a communication system (e.g., model iteration training tasks, model training dataset transmission tasks, measurement result collection tasks, model transmission tasks, model parameter transmission tasks, etc.), the start and end points of these data transmission services are highly flexible. These data transmission services can originate from the access stratum (AS) of the terminal equipment to the access network equipment, or from the access stratum of the terminal equipment to the core network equipment, or from the access network equipment to the access stratum of the terminal equipment, etc. Since much of the collected data primarily involves access stratum functions, this collected data may be formatted using RRC messages. Generally, data defined using RRC messages can be transmitted as control information. On the one hand, because data transmission tasks such as model training datasets may involve large amounts of data (typically reaching tens of megabytes to several gigabytes), this can easily cause SRB congestion. On the other hand, even if the transmitted RRC message segments are few, the serial transmission mode of RRC messages may still lead to queuing delays for control information. Therefore, how to avoid or mitigate SRB congestion and how to reduce queuing delays for control information are technical problems that need to be solved.

[0029] To address the aforementioned issues, this application provides a communication method. Using this method, an association can be established between a set of DRBs and one or more control information types, enabling the transmission of one or more control information types using a set of DRBs. DRBs can also serve as a data transmission channel for control information. On one hand, when the amount of control information to be transmitted is large, it can alleviate or avoid SRB congestion. On the other hand, it can reduce the queuing delay of control information to be transmitted. Furthermore, in scenarios involving changing serving cells, transmitting control information via DRBs can achieve lossless data transmission, whereas related technologies do not support lossless data transmission in mobility scenarios.

[0030] The communication method provided in the embodiments of this application will be described in detail below with reference to Figure 2.

[0031] Figure 2 is a schematic flowchart of a communication method provided in an embodiment of this application. The method in Figure 2 is described from the perspective of a terminal device. The terminal device in Figure 2 can be the terminal device 120 mentioned above. This terminal device can be used to communicate with network devices. The terminal device can be, for example, a UE.

[0032] Referring to Figure 2, the communication method provided in this application embodiment may include the following step S210.

[0033] In step S210, the terminal device receives the first information sent by the network device; correspondingly, the network device sends the first information to the terminal device.

[0034] The first information here can be used to configure a set of DRBs. This can also be understood as the first information being used to configure a set of user plane bearers or a set of data plane bearers. User plane bearers or data plane bearers can be DRBs or other radio bearers (RBs) with similar functions to DRBs. This application embodiment uses the example of the first information being used to configure a set of DRBs for illustration. It should be understood that the descriptions related to DRBs can also be replaced with user plane bearers or data plane bearers, and this application embodiment does not limit this. A set of DRBs can contain one DRB. Alternatively, a set of DRBs can contain multiple DRBs. In some scenarios, a set of DRBs can be used to transmit one type of control information (corresponding to Scenario 1 below). In other scenarios, a set of DRBs can be used to transmit one or more types of control information (corresponding to Scenario 2 below).

[0035] Optionally, in some embodiments, a DRB can be used to transmit control information.

[0036] Alternatively, in other embodiments, a DRB can be used to transmit one or more control information.

[0037] Alternatively, in other embodiments, multiple DRBs can be used to transmit control information.

[0038] Alternatively, in other embodiments, multiple DRBs can be used to transmit one or more types of control information.

[0039] In some cases (corresponding to Case 1 below), the control information can be an RRC message. In other cases (corresponding to Case 2 below), the control information can be a dedicated message for transmitting access stratum related data. "Dedicated message for transmitting access stratum related data" can include or be replaced by: a message specifically designed for transmitting access stratum related data.

[0040] RRC messages can be either downlink or uplink. A downlink RRC message can be understood as an RRC message sent from a network device to a terminal device. An uplink RRC message can be understood as an RRC message sent from a terminal device to a network device.

[0041] Optionally, in some embodiments, the dedicated message for transmitting access layer related data may include one or more of the following data types: model training dataset; measurement related data. Optionally, in other embodiments, the dedicated message for transmitting access layer related data may include one or more of the following data types: model class data; model parameter class data; terminal device capability related data.

[0042] Control messages can have a specific format. The format of control messages can be determined based on predefined protocol information. In other words, the format of control messages can be determined based on protocol defaults. That is, regardless of whether the control message is an RRC message or a dedicated message for transmitting access layer related data, the format of each type of control message can be predefined in the protocol. For RRC messages, the format of each RRC message can be predefined by the protocol. That is, the format of each RRC message can be fixed. For messages specifically used to transmit access layer related data, the format of each message specifically used to transmit access layer related data can be predefined by the protocol. That is, the format of each message specifically used to transmit AS layer related data can be fixed.

[0043] As described in step S210, this embodiment establishes an association between a set of DRBs and one or more control information, enabling the transmission of one or more control information using a set of DRBs. On one hand, this method provides different data transmission channels for control information transmission. Thus, when SRB signaling transmission congestion occurs, it can switch to another data transmission channel (i.e., DRB) to complete the control information transmission, alleviating the situation where SRB signaling transmission congestion leads to untimely control information transmission. On the other hand, it can avoid SRB congestion when the amount of data contained in the control information is too large. In related technologies, control information uses serial transmission technology. For example, a new RRC message transmission is not allowed before each segment of an RRC message is successfully transmitted. Therefore, if there is a large amount of RRC content to be transmitted, it will result in too many RRC message segments to be transmitted, and these excessive RRC message segments will block subsequent RRC message transmissions before successful transmission. Transmitting larger RRC messages (i.e., control information) through DRBs can effectively avoid SRB congestion.

[0044] Step S210 mentions that in some cases (corresponding to Case 1 below), the control information can be an RRC message. In other cases (corresponding to Case 2 below), the control information can be a dedicated message used to transmit access layer related data. Case 1 and Case 2 will be described in detail below.

[0045] In scenario one, the control information can be an RRC message.

[0046] RRC messages can be either downlink RRC messages or uplink RRC messages.

[0047] A downlink RRC message can be understood as an RRC message sent by a network device to a terminal device. Below is a specific example of a downlink RRC message:

[0048] An uplink RRC message can be understood as an RRC message sent by a terminal device to a network device. Below is a specific example of an uplink RRC message:

[0049] Regardless of whether it is a downlink RRC message or an uplink RRC message, the type of RRC message received can be determined by the dedicated control channel (DCCH) header (the value of the DCCH header associated with the RRC message transmitted in this round is confirmed by the selection function mentioned above), and then the RRC message can be decoded according to the definition of that RRC message.

[0050] In scenario two, the control information can be a dedicated message used to transmit access layer related data.

[0051] Messages specifically used for transmitting access layer data differ from RRC messages. For example, a message specifically used for transmitting access layer data could be a message defined specifically for a new control protocol layer. Logically, this new control protocol layer can be parallel to or above the RRC protocol layer. "The new control protocol layer is parallel to the RRC protocol layer" can be understood as: the lower protocol layer directly connected to this new control protocol layer is also a Packet Data Convergence Protocol (PDCP) protocol layer (the control information generated by the new control protocol layer is directly passed down to the PDCP protocol layer for further processing). "The new control protocol layer is above the RRC protocol layer" can be understood as: the control information generated by the new control protocol layer is not directly passed down to the PDCP protocol layer for further processing, but is first processed by the RRC protocol layer before being passed down to the PDCP protocol layer for further processing.

[0052] Optionally, in some embodiments, access layer related data may include one or more of the following data types: model training dataset; measurement related data.

[0053] In some cases, access layer data may include model training datasets. In other cases, access layer data may include measurement-related data. In still other cases, access layer data may include both model training datasets and measurement-related data.

[0054] Model training datasets can be used to train artificial intelligence (AI) models. For example, a model training dataset could be beam measurement results over a period of time, which can be used to train an AI model for beam management functions. As a concrete example, in a beam management scenario, a terminal device can collect beam-related measurement results over a period of time (the beam-related measurement results may include one or more of the following: cell identification information, beam identification information, and beam measurement results). In this scenario, a message specifically used to transmit access layer related data can be understood as a first dedicated message. The protocol can define the format of the first dedicated message, which may include parameters used to carry the model training dataset.

[0055] Measurement-related data typically refers to measurement data acquired by terminal devices during measurements performed using measurement reference signals configured on network devices. Common types of measurement reference signals include: synchronization signal block (SSB), channel state information reference signal (CSI-RS), positioning reference signal (PRS), sensing reference signals, and reference signals for ambient internet of things (ambient IoT) devices. Measurement-related data can include one or more of the following: cell-level measurement-related data and beam-level measurement-related data. Cell-level measurement-related data can include one or more of the following: cell identification information and cell measurement results. Beam-level measurement-related data can include one or more of the following: cell identification information, beam identification information, and beam measurement results. In this scenario, messages specifically used to transmit access layer-related data can be understood as second-specific messages. The protocol can define the format of second-specific messages, which can include parameters used to carry measurement-related data.

[0056] The measurement quantities corresponding to the above measurement results may include one or more of the following: reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), received signal strength indication (RSSI), and channel impulse response (CIR).

[0057] Transmitting model training datasets via DRB offers several advantages. First, model training datasets typically record raw sample data, whose characteristics more closely resemble the actual communication environments experienced by terminal devices. Therefore, transmitting model training datasets allows terminal devices to train AI models that more closely reflect reality using raw sample data, making it easier for the model's performance to meet the demands of real-world communication environments. Second, most data types involved in model training datasets (such as reference signal received power (RSRP) measurements) do not have high privacy protection requirements (except for information like the terminal device's location). Directly transmitting model training datasets reduces the risk of leaking the sender's trade secrets.

[0058] Transmitting measurement-related data via DRB has the following advantages. Firstly, the measurement data obtained by a single device (e.g., a terminal device or network device) through the measurement process is very limited, but the optimization of measurement-related algorithms or the training of measurement-related AI models generally requires a large amount of measurement data. Transmitting measurement-related data via DRB enables measurement data sharing among multiple devices, improving the efficiency of a single device in acquiring measurement-related data. Secondly, because the data source is relatively random, the generalization ability of measurement-related data is better (or the quality of measurement-related data is higher), making it easier to obtain high-quality optimization algorithms or high-performance AI models using such data.

[0059] Optionally, in other embodiments, the access layer related data may include one or more of the following data types: model data; model parameter data; and terminal device capability-related data.

[0060] In some cases, access layer related data may include model-type data. In others, it may include model parameter-type data. Still others, it may include terminal device capability-related data. In still still others, it may include both model-type data and model parameter-type data. In yet another instance, it may include both model-type data and terminal device capability-related data. In yet another instance, it may include model parameter-type data and terminal device capability-related data. In still another instance, it may include model-type data, model parameter-type data, and terminal device capability-related data.

[0061] Model-type data can be understood as the data contained in an AI model. Generally speaking, different functional characteristics can be implemented through different AI models. For example, for beam management functions, an AI model can be trained specifically to perform beam management; for radio resource management (RRM) measurement functions, an AI model can be trained specifically to perform RRM measurement. In this scenario, messages specifically used to transmit access layer related data can be understood as third-party dedicated messages. The format of third-party dedicated messages can be defined in the protocol. These third-party dedicated messages can include parameters used to carry model-type data.

[0062] Model parameter data can be understood as a part of model class data. Generally speaking, model class data can include model structure data and model parameter data. Given that the model structure is known, transmitting only model parameter data is more efficient because it contains a much smaller amount of data compared to the complete model class data. In this scenario, messages specifically used to transmit access layer related data can be understood as fourth-specific messages. The format of fourth-specific messages can be defined in the protocol. These fourth-specific messages can include parameters used to carry model parameter data.

[0063] The capability-related data of a terminal device may include one or more of the following: non-access stratum (NAS) related capability data, access stratum related capability data. In some cases, the capability-related data of a terminal device may include NAS related capability data. In other cases, the capability-related data of a terminal device may include both NAS and access stratum related capability data. Different functional characteristics can be indicated by one or more capability information. In this scenario, a message specifically used to transmit access stratum related data can be understood as a fifth dedicated message. The format of the fifth dedicated message can be defined in the protocol. This fifth dedicated message may include parameters used to carry the capability-related data of the terminal device.

[0064] Transmitting model-type data via DRB has the following advantages: If the data recipient uses the received model to perform model training tasks, transmitting model-type data via DRB allows the model trainer to train the required AI model more quickly. If the data recipient uses the received model to perform specific communication functions, it saves the data recipient the work of training that type of AI model itself. Especially for terminal devices with limited computing power, obtaining AI models from network devices is more in line with business realities than training AI models themselves.

[0065] Transmitting model parameter data via DRB has the following effects: If the recipient of the model parameter data uses the received model parameters to perform a model training task, transmitting model parameter data via DRB allows the model trainer to train the required AI model more quickly. If the recipient of the model parameter data uses the received model parameters to replace existing model parameters, transmitting model parameter data via DRB allows the recipient to quickly update its deployed AI model, thereby regaining communication gains through the AI ​​model in a shorter time.

[0066] Transmitting terminal device capability-related data via DRB has the following advantages: It can prevent SRB congestion when the amount of data related to the terminal device's capabilities is large.

[0067] The aforementioned first, second, third, fourth, and fifth dedicated messages can be the same dedicated message or different dedicated messages. If the aforementioned first, second, third, fourth, and fifth dedicated messages are the same dedicated message, then different types of access layer related data (one or more of the following: model training dataset, measurement related data, model class data, model parameter class data, and terminal device capability related data) can be carried separately through different parameters contained in the same dedicated message.

[0068] Step S210 also mentions that in some scenarios, a set of DRBs can be used to transmit one type of control information (corresponding to Scenario 1 below). In other scenarios, a set of DRBs can be used to transmit one or more types of control information (corresponding to Scenario 2 below). To establish the association between a set of DRBs and one or more types of control information, this application provides three implementation methods for Scenario 1 and five implementation methods for Scenario 2. In these eight implementation methods, the association between a set of DRBs and one or more types of control information is established explicitly or implicitly, thereby realizing the function of transmitting one or more types of control information using a set of DRBs.

[0069] Since a set of DRBs can be directly associated with one or more control information messages, and these control information messages can be either RRC messages or dedicated messages used to transmit access layer related data, the types of control information that a DRB can transmit are not limited to RRC messages; non-RRC messages can also be transmitted via DRBs. It should be understood that using the method provided in the embodiments of this application, the types of control information that a DRB can transmit are diverse and have good scalability. Non-RRC messages can be understood as messages predefined in standard protocols (i.e., the format of the data contained in the message is predefined in the protocol). Alternatively, non-RRC messages can also be understood as messages defined in proprietary protocols (proprietary protocols are different from standardized protocols; proprietary protocols can be understood as protocols implemented by at least two vendors through agreement). Transmitting messages defined by proprietary protocols via DRBs allows related technologies to be commercialized earlier, which greatly alleviates the problem of slow technological updates caused by slow progress in standard protocol discussions, and can improve industry flexibility and user experience.

[0070] The following sections will provide detailed explanations of the three implementation methods for Scenario 1 and the five implementation methods for Scenario 2, using specific examples.

[0071] In the following description, the terms "bearer identifier" and "bearer identifier information" are used. It should be understood that in the embodiments of this application, "bearer identifier" and "bearer identifier information" can be used interchangeably. In the following description, the terms "bearer group identifier" and "bearer group identifier information" are also used. It should be understood that in the embodiments of this application, "bearer group identifier" and "bearer group identifier information" can be used interchangeably.

[0072] Scenario 1: A group of DRBs is used to transmit a type of control information.

[0073] In scenario one, a set of DRBs can be used to transmit control information.

[0074] Optionally, in some embodiments, the relationship between control information and DRBs can be one-to-one. In this case, a set of DRBs contains one DRB, and control information can be transmitted through a DRB associated with that control information.

[0075] Alternatively, in other embodiments, the relationship between control information and DRBs can be one-to-many. In this case, a set of DRBs can contain at least two DRBs, and a type of control information can be transmitted through at least two DRBs associated with that control information.

[0076] In Scenario 1, there are multiple ways to configure the association between control information and a set of DRBs. This application provides three possible implementation methods. The following sections will describe these three possible implementation methods in detail with specific examples.

[0077] The first implementation method of scenario one

[0078] In the first implementation of Scenario 1, the first information may include the bearer identifier corresponding to the DRB, and the first indication information associated with the DRB. The first indication information may be used to indicate a type of control information.

[0079] Here, a DRB can be understood as: among the m (m is a positive integer) DRBs configured by the network device for the terminal device, one DRB is associated with a type of control information. For ease of description, a DRB associated with one type of control information can be called a first-type DRB. In addition to the first-type DRBs, the m DRBs configured by the network device for the terminal device may also include second-type DRBs. Second-type DRBs can be understood as DRBs that are not associated with any control information.

[0080] Each first-class DRB can be associated with a first indication information. The first indication information associated with a DRB can be used to indicate a type of control information associated with that DRB. The DRB associated with the first indication information can be used to transmit the control information indicated by that first indication information. Through the first indication information associated with a DRB, the association relationship between a type of control information and one or more DRBs can be determined.

[0081] There are multiple ways to implement the first instruction information. This application provides the following three possible implementation methods.

[0082] In some implementations, the first indication information can be an identification information (e.g., ID information). This identification information can be the same as or different from the message type identifier corresponding to the control information defined in the protocol. Different values ​​of the identification information can correspond to different types of control information. The protocol can stipulate the association between different values ​​of the identification information and different types of control information. For example, a value of '000' for the first indication information corresponds to an RRC reconfiguration message, a value of '001' corresponds to an RRC capability information reporting message, and a value of '010' corresponds to an RRC data collection reporting message, etc.

[0083] In some implementations, the initial instruction can be implemented using the `choice{}` function. Each value of the `choice{}` function corresponds to a type of control information. Different values ​​of the `choice{}` function can correspond to different types of control information.

[0084] In other implementations, the initial indication information can be implemented using an enumeration parameter. Each element of the enumeration parameter can correspond to a type of control information. Different elements of the enumeration parameter can correspond to different types of control information.

[0085] A DRB can correspond to a bearer group identifier. A DRB can contain one or more DRBs. The bearer group identifier is used to associate a group of DRBs together. That is, one or more DRBs associated with the same bearer group identifier can be referred to as the same DRB group. Generally speaking, one or more DRBs belonging to the same DRB group can be used to perform the same data transmission task. In some cases, the bearer group identifier may also be called a session identifier, task identifier, or index identifier. Bearer group identifiers, session identifiers, task identifiers, and index identifiers can all be used to associate a group of DRBs together. The explanation of the bearer group identifier here applies to the entire text and will not be repeated elsewhere.

[0086] In the first implementation of Scenario 1, the first information may include the bearer group identifier corresponding to the DRB. Alternatively, the first information may not include the bearer group identifier corresponding to the DRB.

[0087] Optionally, in some embodiments, the first information may not include the bearer group identifier corresponding to the DRB. In this case, the network device may configure one or more DRBs for a certain type of control information to be transmitted. If multiple DRBs are configured to transmit the same type of control information, the control information type indicated by the first indication information associated with these multiple DRBs is the same.

[0088] Optionally, in some embodiments, the first information may include the bearer group identifier corresponding to the DRB. In this case, the value of the bearer group identifier can be used to determine which DRBs belong to the same group. The first indication information associated with DRBs belonging to the same group indicates the same type of control information.

[0089] To facilitate understanding, the following explanation is provided in conjunction with Table 1. Table 1 shows an example of the first implementation method for Scenario 1.

[0090] Table 1. Examples of the first implementation method for Scenario 1

[0091] In Table 1, the network device configures m (m is a positive integer) DRBs for the terminal device. Some DRBs are associated with a type of control information. For ease of description, DRBs associated with a type of control information are called Type 1 DRBs, and DRBs not associated with any control information are called Type 2 DRBs. When configuring any Type 1 DRB, the configuration parameters related to the DRB include the bearer identification information corresponding to the DRB, the first indication information, and other configuration parameters related to the DRB. Alternatively, the configuration parameters related to the DRB include the bearer identification information corresponding to the DRB, the first indication information, the bearer group identification information, and other configuration parameters related to the DRB. The first indication information is used to indicate the type of control information associated with the DRB associated with the first indication information. When configuring any Type 2 DRB, the configuration parameters related to the DRB include the bearer identification information corresponding to the DRB and other configuration parameters related to the DRB. Alternatively, the configuration parameters related to the DRB include the bearer identification information corresponding to the DRB, the bearer group identification information, and other configuration parameters related to the DRB. The bearer group identification information corresponding to the DRB is used to associate a group of DRBs together. In other words, one or more DRBs associated with the same bearer group identifier are referred to as the same DRB group. Other configuration parameters related to DRBs include the protocol layer configuration for implementing the DRB.

[0092] The protocol layer configuration for implementing DRB can include PDCP layer configuration information and / or other protocol layer configuration information. Other protocol layer configurations can include Service Data Adaptation Protocol (SDAP) layer configuration information. Of course, if the functionality of the PDCP protocol layer is merged with the functionality of the Radio Link Control (RLC) protocol layer to define a new protocol layer (hereinafter referred to as the first protocol layer), then the protocol layer configuration for implementing DRB can include the first protocol layer configuration information and / or other protocol layer configuration information. This explanation of the protocol layer configuration for implementing DRB applies throughout the entire text and will not be repeated elsewhere.

[0093] In the first implementation of Scenario 1, the association between a control message and one or more DRBs is determined by the first indication information associated with the DRB, so that the terminal device can clearly know which DRB(s) a control message can be transmitted through.

[0094] In the first implementation of Scenario 1, the association between a control information and one or more DRBs is determined by a small number of parameters (first indication information), which is simple to implement.

[0095] The second implementation method of scenario one

[0096] In the second implementation of Scenario 1, the first information may include one or more sets of DRB-related configuration parameters, as well as first indication information associated with the first target DRB group. Here, the first target DRB group can be understood as any one of the one or more DRB groups.

[0097] The group or multiple DRBs can be understood as a group or multiple DRBs configured by the network device for the terminal device. Each DRB in the group or multiple DRBs can be associated with a first indication information. The first indication information can be used to indicate a type of control information. The first indication information associated with a group of DRBs can be used to indicate the type of control information associated with that group of DRBs. That is, the first indication information can be used to indicate the type of control information associated with the group of DRBs associated with the first indication information. Based on this, the group of DRBs associated with the first indication information can be used to transmit the control information indicated by the first indication information.

[0098] The configuration parameters related to DRB can include the bearer identifier corresponding to the DRB, as well as the protocol layer configuration for implementing the DRB.

[0099] In the second implementation of Scenario 1, the first indication information can be implemented in multiple ways. This application provides three possible implementations, which can be found in the description of the relevant parts of the first implementation of Scenario 1. Further details are omitted here.

[0100] In the second implementation of Scenario 1, the association between a set of DRBs and a type of control information is determined by the first indication information associated with a set of DRBs.

[0101] To facilitate understanding, Table 2 is used as a reference below. Table 2 shows an example of the second implementation method for Scenario 1.

[0102] Table 2. Examples of the second implementation method for Scenario 1

[0103] In Table 2, the network device configures k (k is a positive integer) DRBs for the terminal device, and each DRB is associated with a first indication information. The first indication information is used to indicate the type of control information associated with the DRB associated with the first indication information. The three implementation methods of the first indication information are described in the corresponding section of Table 1, and will not be repeated here. Each DRB group contains one or more DRBs. The configuration parameters related to the DRB include the bearer identification information corresponding to the DRB, as well as other configuration parameters related to the DRB. Among them, the other configuration parameters related to the DRB include the protocol layer configuration for implementing the DRB.

[0104] The configuration in Table 2 clearly shows which type of control information a set of DRBs is associated with (the association between the two is determined by the first indication information associated with a set of DRBs).

[0105] In the second implementation of Scenario 1, the association between a control information and a set of DRBs is determined by the first indication information associated with a set of DRBs, so that the terminal device can clearly know which control information can be transmitted through which DRBs.

[0106] In the second implementation of Scenario 1, on the one hand, the association between a control message and a group of DRBs is determined with a small number of parameters (first indication information), making it simple to implement. On the other hand, configuring DRBs by group saves more configuration overhead.

[0107] The first and second implementation methods of Scenario 1 have been described in detail above. As can be seen from the above description, in both the first and second implementation methods of Scenario 1, the first information may include first instruction information. In some cases, in the first and second implementation methods of Scenario 1, the first information may include not only the first instruction information but also second and / or third instruction information.

[0108] The second indication information here can be used to indicate whether the control information indicated by the first indication information is uplink control information or downlink control information. Uplink control information can be understood as control information sent by the terminal device to the network device. Downlink control information can be understood as control information sent by the network device to the terminal device. The second indication information can be configured at the DRB granularity or at the DRB group granularity. That is, the second indication information can be included in a single DRB-related configuration parameter (refer to the example in Table 1) or in a group of DRB-related configuration parameters (refer to the example in Table 2), which is similar to the configuration method of the first indication information.

[0109] The third indication information here can be used to indicate the protocol layer associated with the control information indicated by the first indication information. The third indication information can be configured at the DRB granularity or at the DRB group granularity. That is, the third indication information can be included in a single DRB-related configuration parameter (see the example in Table 1) or in a group of DRB-related configuration parameters (see the example in Table 2), which is similar to the configuration method of the first indication information.

[0110] Of course, if the first information itself already contains the meaning of the second and third indication information, then there is no need to separately configure the second and / or third indication information in the first information. For example, if the value of the first indication information is '000', corresponding to an RRC reconfiguration message, since the protocol has clearly defined that the RRC reconfiguration message is a downlink control message and the protocol layer associated with this message is the RRC protocol layer, then the first indication information itself contains the meaning of the second and third indication information. Therefore, there is no need to repeat the same meaning through the second and / or third indication information.

[0111] Optionally, in some embodiments, the first information may further include second indication information. If the first indication information only indicates the logical number of the control information, but the logical number alone cannot confirm whether the control information indicated by the first indication information is uplink control information or downlink control information, then the first information may further include second indication information. The second indication information can be used to indicate whether the control information indicated by the first indication information is uplink control information or downlink control information. For example, if the value of the first indication information is '000', since '000' can refer to both the message with logical number '000' in the uplink control information and the message with logical number '000' in the downlink control information, the second indication information is needed to further distinguish whether the control information indicated by the first indication information is uplink control information or downlink control information. When the first information includes second indication information, if the control information type involved in this application is associated with only one protocol layer, such as the RRC protocol layer, then the first information may not include third indication information. When the first information includes second indication information, if the control information type involved in this application is associated with more than one protocol layer, then the first information may further include third indication information.

[0112] Optionally, in other embodiments, the first information may further include third indication information. If the control information type involved in this application is associated with more than one protocol layer, for example, if the protocol layers associated with the control information type include the RRC protocol layer and a second protocol layer, wherein the message specifically used for transmitting access layer related data is generated by the second protocol layer, and the first indication information cannot provide the protocol layer information associated with the control information type, then the first information may further include third indication information. When the first information includes third indication information, if it cannot be determined whether the control information indicated by the first indication information is uplink control information or downlink control information through the first indication information, then the first information may not include second indication information. When the first information includes third indication information, if it can be determined whether the control information indicated by the first indication information is uplink control information or downlink control information through the first indication information, then the first information may not include second indication information.

[0113] Optionally, in other embodiments, the first information may further include second and third indication information. If the control information indicated by the first indication information cannot be determined through the first indication information as either uplink or downlink control information, and the control information type involved in this application is associated with more than one protocol layer, then the second and third indication information can be configured separately in the first information.

[0114] The third implementation method of scenario one

[0115] In the third implementation of scenario one, the first information may include one or more first parameters.

[0116] The first parameter can be used to indicate a set of DRB-related configuration parameters; that is, the first parameter can be used to configure a set of DRBs. A network device can configure k (k is a positive integer) DRBs for a terminal device. These k DRBs can be configured sequentially using k first parameters.

[0117] The configuration parameters related to DRB can include the bearer identifier corresponding to the DRB, as well as the protocol layer configuration for implementing the DRB.

[0118] The first parameter can be associated with a type of control information. Different first parameters can be associated with different types of control information. A set of DRBs indicated by the first parameter (or a set of DRBs configured by the first parameter) can be used to transmit a type of control information associated with the first parameter. The type of control information associated with the first parameter can be determined based on protocol predefined information (or, through protocol defaults). Protocol predefined information may include: the predefined location of the first parameter in the protocol. That is, the predefined location of the first parameter in the protocol can determine which type of control information the set of DRBs configured by that first parameter is used to transmit. For example, the protocol stipulates that parameter one is associated with RRC reconfiguration messages, that is: the set of DRBs configured by parameter one is used to transmit RRC reconfiguration messages; the protocol stipulates that parameter two is associated with RRC capability information reporting messages, that is: the set of DRBs configured by parameter two is used to transmit RRC capability information reporting messages; the protocol stipulates that parameter k is associated with RRC data collection reporting messages, that is: the set of DRBs configured by parameter k is used to transmit RRC data collection reporting messages.

[0119] To facilitate understanding, Table 3 is used as a reference below. Table 3 shows an example of the third implementation method for Scenario 1.

[0120] Table 3 shows an example of the third implementation method for Scenario 1.

[0121] In Table 3, the network device configures k (k is a positive integer) DRBs for the terminal device. Each DRB group contains one or more DRBs. The k DRBs are configured sequentially through parameters one through k. The target DRB in the k DRB groups is used to transmit a type of control information, and the target DRB can be any one of the k DRB groups. Parameter k includes the configuration parameters related to the k-th DRB. The DRB-related configuration parameters include the bearer identifier corresponding to the DRB and the protocol layer configuration for implementing the DRB.

[0122] In the third implementation of Scenario 1, a control method that determines a set of DRB associations through predefined protocol information can save on configuration overhead.

[0123] The above describes the three implementation methods for Scenario 1. The following describes the five implementation methods for Scenario 2.

[0124] Scenario 2: A group of DRBs is used to transmit one or more control information.

[0125] In Scenario 2, a set of DRBs can be used to transmit one or more types of control information. In Scenario 2, the association between control information and DRBs can be any of the following: one-to-one association, one-to-many association, many-to-one association, or many-to-many association.

[0126] Optionally, in some embodiments, the relationship between control information and DRB can be one-to-one. In this case, a group of DRBs may contain one DRB, and control information can be transmitted through a DRB associated with that control information.

[0127] Alternatively, in other embodiments, the relationship between control information and DRBs can be one-to-many. In this case, a group of DRBs can contain at least two DRBs, and a type of control information can be transmitted through at least two DRBs associated with that control information.

[0128] Alternatively, in other embodiments, the relationship between control information and DRBs can be many-to-one. In this case, a group of DRBs may contain one DRB, and at least two types of control information can be transmitted through a DRB associated with those at least two types of control information.

[0129] Alternatively, in other embodiments, the relationship between control information and DRBs can be many-to-many. In this case, a group of DRBs can contain at least two DRBs, and at least two types of control information can be transmitted through at least two DRBs associated with the at least two types of control information.

[0130] In Scenario 2, there are multiple configuration methods to establish the association between one or more control information items and a set of DRBs. This application provides five possible implementation methods. The following sections will detail these five possible implementation methods with specific examples.

[0131] The first implementation method of scenario two

[0132] In the first implementation of Scenario 2, the first information may include the bearer identifier corresponding to the DRB, and one or more fourth indication information associated with the DRB. The fourth indication information may be used to indicate a type of control information.

[0133] Here, a DRB can be understood as: among the m (m is a positive integer) DRBs configured by the network device for the terminal device, the DRB associated with one or more types of control information. For ease of description, a DRB associated with one or more types of control information can be called a first-class DRB. Each first-class DRB can be associated with one or more types of control information. Different DRBs belonging to the first-class DRB can be associated with the same type of one or more types of control information. Alternatively, different DRBs belonging to the first-class DRB can be associated with different types of one or more types of control information. In addition to the first-class DRBs, the m DRBs configured by the network device for the terminal device may also include second-class DRBs. Second-class DRBs can be understood as DRBs that are not associated with any control information.

[0134] Each DRB belonging to the first type of DRB can be associated with one or more fourth indication messages. Each of these one or more fourth indication messages can be used to indicate a type of control information associated with a DRB associated with the one or more fourth indication messages. Therefore, one or more types of control information associated with the DRB can be indicated through the one or more fourth indication messages. The DRB associated with one or more fourth indication messages can be used to transmit one or more types of control information indicated by the one or more fourth indication messages.

[0135] There are multiple ways to implement the fourth instruction information. This application provides the following three possible implementation methods.

[0136] In some implementations, the fourth indication information can be an identification information (e.g., ID information). This identification information can be the same as or different from the message type identifier corresponding to the control information defined in the protocol. Different values ​​of the identification information can correspond to different types of control information. The protocol can stipulate the association between different values ​​of the identification information and different types of control information. For example, a value of '000' for the fourth indication information corresponds to an RRC reconfiguration message, a value of '001' corresponds to an RRC capability information reporting message, and a value of '010' corresponds to an RRC data collection reporting message, etc.

[0137] In some implementations, the fourth instruction information can be implemented using the `choice{}` function. Each value of the `choice{}` function corresponds to a type of control information. Different values ​​of the `choice{}` function can correspond to different types of control information.

[0138] In some implementations, the fourth indication information can be implemented using enumeration parameters. Each element of the enumeration parameter can correspond to a type of control information. Different elements of the enumeration parameter can correspond to different types of control information.

[0139] A DRB can correspond to a bearer group identifier. A DRB can contain one or more DRBs. The bearer group identifier is used to associate a group of DRBs together. That is, one or more DRBs associated with the same bearer group identifier can be referred to as the same DRB group. Generally speaking, one or more DRBs belonging to the same DRB group can be used to perform the same data transmission task.

[0140] In the first implementation of Scenario 2, the first information may include the bearer group identifier corresponding to the DRB. Alternatively, the first information may not include the bearer group identifier corresponding to the DRB.

[0141] Optionally, in some embodiments, the first information may further include the bearer group identifier corresponding to the DRB. In this case, the network device may configure one or more DRBs to transmit one or more types of control information. If multiple DRBs are configured to transmit the same type of control information, or if multiple DRBs are configured to transmit the same multiple types of control information, then the control information types indicated by one or more fourth indication information associated with the multiple DRBs are the same.

[0142] Optionally, in some embodiments, the first information may not include the bearer group identifier corresponding to the DRB. In this case, the values ​​of one or more fourth indication information associated with the DRB can determine which DRBs belong to the same group, and the control information types indicated by one or more fourth indication information associated with DRBs belonging to the same group are the same.

[0143] In the first implementation of Scenario 2, the association between one or more control information and a set of DRBs can be determined through one or more fourth indication information associated with the DRB.

[0144] To facilitate understanding, the following explanation is provided in conjunction with Table 4. Table 4 shows an example of the first implementation method for Scenario 2.

[0145] Table 4. Example of the first implementation method for Scenario 2.

[0146] In Table 4, the network device configures m (m is a positive integer) DRBs for the terminal device. Some DRBs are associated with one or more control information types. For ease of description, DRBs associated with one or more control information types are called Type I DRBs, and DRBs not associated with any control information types are called Type II DRBs. When configuring any Type I DRB, the configuration parameters related to the DRB include the bearer identification information corresponding to the DRB, one or more fourth indication information types, and other configuration parameters related to the DRB. Alternatively, the configuration parameters related to the DRB include the bearer identification information corresponding to the DRB, one or more fourth indication information types, bearer group identification information, and other configuration parameters related to the DRB. A fourth indication information type is used to indicate the type of control information associated with the associated DRB. When configuring any Type II DRB, the configuration parameters related to the DRB include the bearer identification information corresponding to the DRB and other configuration parameters related to the DRB. Alternatively, the configuration parameters related to the DRB include the bearer identification information corresponding to the DRB, bearer group identification information, and other configuration parameters related to the DRB. The bearer group identifier information corresponding to a DRB is used to associate a group of DRBs together; that is, one or more DRBs associated with the same bearer group identifier are referred to as the same group of DRBs. Other configuration parameters related to DRBs include the protocol layer configuration for implementing DRBs.

[0147] The configuration in Table 4 clearly shows which type or types of control information each DRB belonging to the first type of DRB is associated with (the association between the two is determined by one or more fourth indication information associated with the DRB).

[0148] In the first implementation of Scenario 1, the association between one or more control information and one or more DRBs is determined by one or more fourth indication information associated with the DRB, so that the terminal device can clearly know which DRBs one or more control information can be transmitted through.

[0149] In the first implementation of Scenario 2, the association between one or more control information and one or more DRBs is determined by a small number of parameters (one or more fourth indication information), which is simple to implement.

[0150] The second implementation method of scenario two

[0151] In the second implementation of Scenario 2, the first information may include one or more sets of DRB-related configuration parameters, as well as one or more fourth indication information associated with the second target DRB group. Here, the second target DRB group can be understood as any one of the one or more DRB groups.

[0152] The set or multiple DRBs can be understood as a set or multiple DRBs configured by the network device for the terminal device. Each DRB in the set or multiple DRBs can be associated with one or more fourth indication information. The fourth indication information can be used to indicate a type of control information. Based on this, the one or more fourth indication information associated with a set of DRBs can be used to transmit one or more types of control information indicated by the one or more fourth indication information. That is, a set of DRBs associated with one or more fourth indication information can be used to transmit one or more types of control information indicated by the one or more fourth indication information.

[0153] The configuration parameters related to DRB can include the bearer identifier corresponding to the DRB, as well as the protocol layer configuration for implementing the DRB.

[0154] In the second implementation of Scenario 2, there are multiple ways to implement the fourth indication information. This application provides three possible implementations, which can be found in the description of the relevant parts of the first implementation of Scenario 2. Further details are omitted here.

[0155] In the second implementation of Scenario 2, the association between a set of DRBs and one or more fourth indication information can be determined through a set of DRBs associated with one or more fourth indication information.

[0156] To facilitate understanding, the following explanation is provided in conjunction with Table 5. Table 5 shows an example of the second implementation method for Scenario 2.

[0157] Table 5. Example of the second implementation method for Scenario 2.

[0158] In Table 5, the network device configures k (k is a positive integer) DRBs for the terminal device. Each DRB group is associated with one or more fourth indication information. The fourth indication information is used to indicate a type of control information associated with the associated DRB group. The three implementation methods of the fourth indication information are described in the corresponding section of Table 4 and will not be repeated here. Each DRB group contains one or more DRBs. The configuration parameters related to the DRB include the bearer identification information corresponding to the DRB and other configuration parameters related to that DRB. Among them, the other configuration parameters related to the DRB include the protocol layer configuration for implementing the DRB.

[0159] The configuration in Table 5 clearly shows which type or types of control information a group of DRBs is associated with (the association between the two is determined by one or more fourth indication information associated with a group of DRBs).

[0160] In the second implementation of Scenario 2, the association between one or more control information and a set of DRBs is determined by one or more fourth indication information associated with a set of DRBs. The terminal device can then clearly know which type or types of control information can be transmitted through which DRBs.

[0161] In the second implementation of Scenario 2, on the one hand, the association between one or more control information and a group of DRBs is determined by a small number of parameters (one or more fourth indication information), making it simple to implement. On the other hand, configuring DRBs by group saves more configuration overhead.

[0162] The third implementation method of scenario two

[0163] In the third implementation of scenario two, the first information may include one or more second parameters.

[0164] The second parameter can be used to indicate a set of DRB-related configuration parameters; that is, the second parameter can be used to configure a set of DRBs. A network device can configure k (k is a positive integer) DRBs for a terminal device. These k DRBs can be configured sequentially using k second parameters.

[0165] The configuration parameters related to DRB can include the bearer identifier corresponding to the DRB, as well as the protocol layer configuration for implementing the DRB.

[0166] The second parameter can be associated with one or more control information types. Different second parameters can be associated with different control information types. A set of DRBs indicated by the second parameter can be used to transmit one or more control information types associated with the second parameter. The control information type associated with the second parameter can be determined based on protocol predefined information (or, in other words, through protocol defaults). Protocol predefined information may include: the predefined location of the second parameter in the protocol. That is, the predefined location of the second parameter in the protocol can determine which type or types of control information the set of DRBs configured for that second parameter is used to transmit. For example, the protocol stipulates that parameter one is associated with RRC reconfiguration messages, that is: the set of DRBs configured with parameter one is used to transmit RRC reconfiguration messages; the protocol stipulates that parameter two is associated with RRC capability information reporting messages, that is: the set of DRBs configured with parameter two is used to transmit RRC capability information reporting messages; the protocol stipulates that parameter k is associated with RRC data collection reporting messages, that is: the set of DRBs configured with parameter k is used to transmit RRC data collection reporting messages.

[0167] To facilitate understanding, Table 6 is used as a reference below. Table 6 shows an example of the third implementation method for Scenario 2.

[0168] Table 6 shows an example of the third implementation method for scenario two.

[0169] In Table 6, the network device configures k (k is a positive integer) DRBs for the terminal device. Each DRB group contains one or more DRBs. The k DRBs are configured sequentially through parameters one through k. The target DRB in the k DRB groups is used to transmit one or more control information, and the target DRB can be any one of the k DRB groups. Parameter k includes the configuration parameters related to the k-th DRB. The configuration parameters related to the DRB include the bearer identifier corresponding to the DRB and the protocol layer configuration for implementing the DRB.

[0170] In the third implementation of Scenario 2, determining one or more controls associated with a set of DRBs through predefined protocol information can save on configuration overhead.

[0171] The fourth implementation method of scenario two

[0172] The fourth implementation in Scenario 2 can include two scenarios. In the first scenario, the first information can include the bearer identifier corresponding to the DRB and the first bit string information associated with that DRB. In the second scenario, the first information can include one or more sets of configuration parameters related to the DRB and the first bit string information associated with the third target group DRB. These two scenarios will be described in detail below with reference to Tables 7A and 7B.

[0173] In the first case, the first information may include the bearer identifier corresponding to the DRB, and the first bit string information associated with the DRB. This first bit string information may be used to indicate one or more types of control information associated with the DRB.

[0174] Here, a DRB can be understood as: among the m (m is a positive integer) DRBs configured by the network device for the terminal device, the DRB associated with one or more types of control information. For ease of description, a DRB associated with one or more types of control information can be called a first-type DRB. Each DRB belonging to the first-type DRB can be associated with one or more types of control information. The types of one or more types of control information associated with each DRB belonging to the first-type DRB can be the same. Alternatively, the types of one or more types of control information associated with each DRB belonging to the first-type DRB can also be different. Among the m DRBs configured by the network device for the terminal device, in addition to the first-type DRBs, a second-type DRB may also be included. The second-type DRB can be understood as a DRB that is not associated with any control information.

[0175] Each DRB belonging to the first type of DRB can be associated with a first bit string. The target bit in the first bit string can be associated with a type of control information. Here, the target bit can be understood as any bit in the first bit string. The first bit string can contain one or more target bits. For example, the first bit string may contain 4 bits: the first bit is associated with an RRC reconfiguration message, the second bit with an RRC capability information reporting message, the third bit with a Record Quality of Experience (QoE) message, and the fourth bit with an RRC data collection reporting message.

[0176] If the target bit in the first bit string information has a first value, then a DRB associated with the first bit string information can be used to transmit the control information associated with that target bit. For example, if the target bit in the first bit string information has a value of '1', then the DRB associated with the first bit string information can be used to transmit the control information associated with that target bit.

[0177] The association between target bits and control information types can be determined based on protocol predefined information. Alternatively, the association between target bits and control information types can be determined based on protocol defaults.

[0178] For the first case of the fourth implementation method in scenario two, optionally, in some embodiments, the first information may also include the bearer group identifier corresponding to the DRB.

[0179] A DRB can correspond to a bearer group identifier. A DRB can contain one or more DRBs. The bearer group identifier is used to associate a group of DRBs together. That is, one or more DRBs associated with the same bearer group identifier can be referred to as the same DRB group. Generally speaking, one or more DRBs belonging to the same DRB group can be used to perform the same data transmission task.

[0180] In the first case of the fourth implementation method in Scenario 2, the association between a DRB and one or more control information can be determined through the first bit string information associated with a DRB.

[0181] For ease of understanding, the following explanation is provided in conjunction with Table 7A. Table 7A shows an example of the fourth implementation method for Scenario 2 (corresponding to the first case of the fourth implementation method for Scenario 2).

[0182] Example 1 of the fourth implementation method in Scenario 2 of Table 7A

[0183] In Table 7A, the network device configures m (m is a positive integer) DRBs for the terminal device. Some DRBs are associated with one or more control information. For ease of description, DRBs associated with one or more control information are called Type I DRBs, and DRBs not associated with any control information are called Type II DRBs. When configuring any Type I DRB, the configuration parameters related to the DRB include the bearer identifier information corresponding to the DRB, the first bit string, and other configuration parameters related to the DRB. Alternatively, the configuration parameters related to the DRB include the bearer identifier information corresponding to the DRB, the first bit string, the bearer group identifier information, and other configuration parameters related to the DRB. Each bit in the first bit string is associated with one type of control information. This association is determined by protocol agreement. For example, the first bit string consists of 4 bits. The protocol stipulates that the first bit in the first bit string is associated with an RRC reconfiguration message, the second bit is associated with an RRC capability information reporting message, the third bit is associated with a QoE message, and the fourth bit is associated with an RRC data collection reporting message. If the target bit is a first value (e.g., '1'), then the DRB associated with the first bit string information is considered to be used to transmit control information associated with that target bit, where the target bit is any bit in the first bit string information. When configuring any DRB belonging to the second type of DRB, the DRB-related configuration parameters include the bearer identifier information corresponding to the DRB and other configuration parameters related to the DRB. Alternatively, the DRB-related configuration parameters include the bearer identifier information corresponding to the DRB, the bearer group identifier information, and other configuration parameters related to the DRB. The bearer group identifier information corresponding to the DRB is used to associate a group of DRBs together; that is, one or more DRBs associated with the same bearer group identifier are referred to as the same group of DRBs. Other DRB-related configuration parameters include the protocol layer configuration for implementing the DRB.

[0184] The first scenario of the fourth implementation method for scenario two has been introduced above with reference to Table 7A. The second scenario of the fourth implementation method for scenario two has been introduced below with reference to Table 7B.

[0185] In the second scenario, the first information may include one or more sets of configuration parameters related to the DRB, as well as the first bit string information associated with the third target DRB. The third target DRB can be understood as any one of the one or more DRBs.

[0186] The group or multiple DRBs here can be understood as k (k is a positive integer) DRBs configured by the network device for the terminal device, each associated with one or more control information. For ease of description, the DRBs in the k (k is a positive integer) DRBs configured by the network device for the terminal device, each associated with one or more control information, can be called the first type of DRB. Each DRB belonging to the first type of DRB can be associated with one or more control information. In addition to the first type of DRBs, the k groups of DRBs configured by the network device for the terminal device may also include second type of DRBs. The second type of DRB can be understood as DRBs that are not associated with any control information.

[0187] DRB-related configuration parameters can include the bearer identifier corresponding to the DRB. DRB-related configuration parameters can also include the protocol layer configuration for implementing the DRB.

[0188] Each group of first-class DRBs (i.e., third-target DRBs) can be associated with a first bit string. The target bits in the first bit string can be associated with a type of control information. Here, the target bit can be understood as any single bit in the first bit string. The first bit string can contain one or more target bits. The first bit string can be used to indicate the type of one or more control information associated with the group of DRBs associated with it. For example, the first bit string may consist of four bits: the first bit is associated with an RRC reconfiguration message, the second bit with an RRC capability information reporting message, the third bit with a QoE message, and the fourth bit with an RRC data collection reporting message.

[0189] If the target bit in the first bit string information has a first value, then a set of DRBs associated with the first bit string information can be used to transmit the control information associated with the target bit. For example, if the target bit in the first bit string information has a value of '1', then a set of DRBs associated with the first bit string information can be used to transmit the control information associated with the target bit.

[0190] The association between target bits and control information types can be determined based on protocol predefined information. Alternatively, the association between target bits and control information types can be determined based on protocol defaults.

[0191] In the second case of the fourth implementation method in Scenario 2, the association between a set of DRBs and one or more control information can be determined through the first bit string information associated with a set of DRBs.

[0192] For ease of understanding, the following explanation is provided in conjunction with Table 7B. Table 7B shows an example of the fourth implementation method for Scenario 2 (corresponding to the second case of the fourth implementation method for Scenario 2).

[0193] Example 1 of the fourth implementation method in Scenario 2 of Table 7B

[0194] In Table 7B, the network device configures k (k is a positive integer) groups of DRBs for the terminal device. Some DRBs are associated with one or more control information. For ease of description, DRBs associated with one or more control information are called Type I DRBs, and DRBs not associated with any control information are called Type II DRBs. When configuring any group of DRBs belonging to Type I DRBs, the configuration includes the configuration parameters related to that group of DRBs and the first bit string information. The configuration parameters related to the DRB include the bearer identifier information corresponding to the DRB and other configuration parameters related to the DRB. Each bit in the first bit string information is associated with a type of control information, and this association is determined by protocol agreement. For example, the first bit string information includes 4 bits. According to the protocol, the first bit in the first bit string information is associated with the RRC reconfiguration message, the second bit in the first bit string information is associated with the RRC capability information reporting message, the third bit in the first bit string information is associated with the QoE message, and the fourth bit in the first bit string information is associated with the RRC data collection reporting message. If the target bit is a first value (e.g., '1'), then the DRB associated with the first bit string information is considered to be used to transmit control information associated with that target bit, where the target bit is any bit in the first bit string information. When configuring any DRB belonging to the second type of DRB, the DRB-related configuration parameters include the bearer identifier information corresponding to the DRB and other configuration parameters related to the DRB. These other configuration parameters include the protocol layer configuration for implementing the DRB.

[0195] By using the configuration in Table 7A or Table 7B, it can be clearly determined which type or types of control information a group of DRBs is associated with (the association between the two is determined by the first bit string information associated with one or a group of DRBs).

[0196] In the fourth implementation of Scenario 2, the association between one or more control information and one or more DRBs is determined by the first bit string information associated with one or a group of DRBs. The terminal device can then clearly know which one or more control information can be transmitted through which DRBs.

[0197] Since the number of target bits contained in the first bit string information associated with each DRB belonging to the first type of DRB can be one or more, the association between one or more control information and one or a group of DRBs can be indicated by one or more target bits.

[0198] The fourth implementation method in Scenario 2 balances the flexibility of configuration with the size of the overhead.

[0199] The fifth implementation method of scenario two

[0200] The fifth implementation method in Scenario 2 can include two scenarios. In the first scenario, the first information can include the bearer identifier corresponding to the DRB, and one or more fifth indication information associated with the DRB. In the second scenario, the first information can include one or more sets of DRB-related configuration parameters, and one or more fifth indication information associated with the fourth target group DRB. These two scenarios will be described in detail below with reference to Tables 8A and 8B.

[0201] In the first scenario, the first information may include the bearer identifier corresponding to the DRB, and one or more fifth indication information associated with the DRB. The fifth indication information may be associated with a control information type.

[0202] Here, a DRB can be understood as: among the m (m is a positive integer) DRBs configured by the network device for the terminal device, the DRB associated with one or more types of control information. For ease of description, a DRB associated with one or more types of control information can be called a first-type DRB. Each first-type DRB can be associated with one or more types of control information. Each DRB belonging to the first-type DRB can be associated with the same type of one or more types of control information. Alternatively, each DRB belonging to the first-type DRB can be associated with different types of one or more types of control information. In addition to the first-type DRBs, the m DRBs configured by the network device for the terminal device may also include second-type DRBs. Second-type DRBs can be understood as DRBs that are not associated with any control information.

[0203] Each Category 1 DRB can be associated with one or more fifth indication messages. Any one of these fifth indication messages can be associated with a control information type. For example, a DRB may be associated with four fifth indication messages: the first associated with an RRC reconfiguration message, the second with an RRC capability information reporting message, the third with a QoE message, and the fourth with an RRC data collection reporting message.

[0204] In one or more fifth indication messages associated with a DRB, if any fifth indication message takes the value of a second value, it indicates that the DRB is used to transmit control information associated with that fifth indication message. For example, in one or more fifth indication messages associated with a DRB, if any fifth indication message takes the value of 'true', it indicates that the DRB is used to transmit control information associated with that fifth indication message.

[0205] The association between the fifth instruction information and the control information type can be determined based on predefined information in the protocol. Alternatively, the association between the fifth instruction information and the control information type can be determined based on the protocol's default method.

[0206] For the first case of the fifth implementation of scenario two, optionally, in some embodiments, the first information may also include the bearer group identifier corresponding to the DRB.

[0207] A DRB can correspond to a bearer group identifier. A DRB can contain one or more DRBs. The bearer group identifier is used to associate a group of DRBs together. That is, one or more DRBs associated with the same bearer group identifier can be referred to as the same DRB group. Generally speaking, one or more DRBs belonging to the same DRB group can be used to perform the same data transmission task.

[0208] In the first case of the fifth implementation method in Scenario 2, the association between a DRB and one or more control information can be determined by one or more fifth indication information associated with a DRB.

[0209] For ease of understanding, the following explanation is provided in conjunction with Table 8A. Table 8A shows an example of the fifth implementation method for Scenario 2 (corresponding to the first case of the fifth implementation method for Scenario 2).

[0210] Example 1 of the fifth implementation method in Scenario 2 of Table 8A

[0211] In Table 8A, the network device configures m (m is a positive integer) DRBs for the terminal device. Some DRBs are associated with one or more control information. For ease of description, DRBs associated with one or more control information are called Type I DRBs, and DRBs not associated with any control information are called Type II DRBs. When configuring any Type I DRB, the configuration parameters related to the DRB include the bearer identification information corresponding to the DRB, one or more fifth indication information, and other configuration parameters related to the DRB. Alternatively, the configuration parameters related to the DRB include the bearer identification information corresponding to the DRB, one or more fifth indication information, bearer group identification information, and other configuration parameters related to the DRB. Each fifth indication information is associated with one type of control information, and this association is determined by protocol agreement. For example, if a DRB is associated with four fifth indication information, the protocol stipulates that the first fifth indication information is associated with an RRC reconfiguration message, the second fifth indication information is associated with an RRC capability information reporting message, the third fifth indication information is associated with a QoE message, and the fourth fifth indication information is associated with an RRC data collection reporting message. If the value corresponding to the fifth indication information is the second value (e.g., 'true'), then the DRB associated with the fifth indication information is considered to be used to transmit the control information associated with the fifth indication information. When configuring any DRB belonging to the second type of DRB, the DRB-related configuration parameters include the bearer identification information corresponding to the DRB and other configuration parameters related to the DRB. Alternatively, the DRB-related configuration parameters include the bearer identification information corresponding to the DRB, the bearer group identification information, and other configuration parameters related to the DRB. Among these, the other configuration parameters related to the DRB include at least the protocol layer configuration for implementing the DRB.

[0212] The first scenario of the fifth implementation method for scenario two has been introduced above with reference to Table 8A. The second scenario of the fifth implementation method for scenario two will be introduced below with reference to Table 8B.

[0213] In the second scenario, the first information may include one or more sets of DRB-related configuration parameters, as well as one or more fifth indication information associated with the fourth target group DRB. The fourth target group DRB can be understood as any one of the one or more DRB sets.

[0214] The group or multiple DRBs can be understood as k (k is a positive integer) DRBs configured by the network device for the terminal device, each associated with one or more control information. For ease of description, the DRBs in the k (k is a positive integer) DRBs configured by the network device for the terminal device, each associated with one or more control information, can be called the first type of DRB. Each first type of DRB can be associated with one or more control information. In addition to the first type of DRBs, the k groups of DRBs configured by the network device for the terminal device may also include a second type of DRB. The second type of DRB can be understood as a DRB that is not associated with any control information.

[0215] DRB-related configuration parameters can include the bearer identifier corresponding to the DRB. DRB-related configuration parameters can also include the protocol layer configuration for implementing the DRB.

[0216] Each group of Category 1 DRBs (i.e., the fourth target group DRBs) can be associated with one or more fifth indication messages. Any one of these fifth indication messages can be associated with a control information type. For example, a group of DRBs may be associated with four fifth indication messages: the first is associated with an RRC reconfiguration message, the second with an RRC capability information reporting message, the third with a QoE message, and the fourth with an RRC data collection reporting message.

[0217] In a set of DRBs associated with one or more fifth indication messages, if any one of the fifth indication messages takes the value of a second value, it can indicate that the set of DRBs is used to transmit the control information associated with that fifth indication message. For example, in a set of DRBs associated with one or more fifth indication messages, if any one of the fifth indication messages takes the value of 'true', it indicates that the set of DRBs is used to transmit the control information associated with that fifth indication message.

[0218] The association between the fifth instruction information and the control information type can be determined based on predefined information in the protocol. Alternatively, the association between the fifth instruction information and the control information type can be determined based on the protocol's default method.

[0219] In the second case of the fifth implementation method in Scenario 2, the association between a set of DRBs and one or more control information can be determined through one or more fifth indication information associated with a set of DRBs.

[0220] For ease of understanding, the following explanation is based on Table 8B. Table 8B shows an example of the fifth implementation method for Scenario 2 (corresponding to the second case of the fifth implementation method for Scenario 2).

[0221] Example 2 of the fifth implementation method in Scenario 2 of Table 8B

[0222] In Table 8B, the network device configures k (k is a positive integer) groups of DRBs for the terminal device. Some DRBs are associated with one or more control information. For ease of description, DRBs associated with one or more control information are called Class I DRBs, and DRBs not associated with any control information are called Class II DRBs. When configuring any group of DRBs belonging to Class I DRBs, the configuration includes configuration parameters related to that group of DRBs and one or more fifth indication information. The configuration parameters related to the DRB include the bearer identification information corresponding to the DRB and other configuration parameters related to the DRB. Each fifth indication information is associated with a type of control information, and this association is determined by protocol agreement. For example, if a DRB is associated with four fifth indication information, the protocol stipulates that the first fifth indication information is associated with an RRC reconfiguration message, the second fifth indication information is associated with an RRC capability information reporting message, the third fifth indication information is associated with a QoE message, and the fourth fifth indication information is associated with an RRC data collection reporting message. If the value of the corresponding fifth indication information is the second value (e.g., 'true'), then the DRB associated with that fifth indication information is considered to be used to transmit the control information associated with that fifth indication information. When configuring any DRB belonging to the second type of DRB, the DRB-related configuration parameters include the bearer identification information corresponding to the DRB and other configuration parameters related to the DRB. Among them, the other configuration parameters related to the DRB include the protocol layer configuration for implementing the DRB.

[0223] The configuration in Table 8A or Table 8B can be used to determine which type or types of control information a set of DRBs is associated with (the association between the two is determined by one or more fifth indication information associated with a set of DRBs).

[0224] In the fifth implementation of Scenario 2, since each or each group of DRBs belonging to the first type of DRB can be associated with one or more fifth indication information, the association between one or more control information and one or a group of DRBs can be indicated by one or more fifth indication information.

[0225] In the fifth implementation method of Scenario 2, the overhead of configuration can be saved.

[0226] The above provides a detailed description of the three implementation methods for scenario one and the five implementation methods for scenario two provided in the embodiments of this application, using specific examples.

[0227] As can be seen from the above description, the embodiments of this application establish an association between a set of DRBs and one or more control information, thereby enabling the transmission of one or more control information using a set of DRBs. On the one hand, this method can provide different data transmission channels for the transmission of control information. In this way, when SRB signaling transmission congestion occurs, it can switch to another data transmission channel (i.e., DRB) to complete the control information transmission, alleviating the situation where SRB signaling transmission congestion leads to untimely control information transmission. On the other hand, it can avoid SRB congestion when the amount of data contained in the control information is too large. In related technologies, control information uses serial transmission technology. For example, a new RRC message transmission is not allowed before each segment of an RRC message is completely and successfully transmitted. Therefore, if there is a large amount of RRC content to be transmitted, it will result in too many RRC message segments to be transmitted, and too many RRC message segments will block subsequent RRC message transmissions before successful transmission. If larger RRC messages (i.e., control information) are transmitted through DRBs, SRB congestion can be effectively avoided.

[0228] The method embodiments of this application have been described in detail above with reference to Figure 2 and Tables 1 to 8. The apparatus embodiments of this application will now be described in detail below with reference to Figures 3 to 5. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0229] Figure 3 is a schematic diagram of the structure of a communication device 300 provided in an embodiment of this application. The communication device 300 shown in Figure 3 is a terminal device. The communication device 300 includes a receiving unit 310. The receiving unit 310 is used to receive first information sent by a network device, the first information being used to configure a set of DRBs, the set of DRBs being used to transmit one or more control information; wherein, the set of DRBs includes one or more DRBs.

[0230] In some implementations, the control information is a Radio Resource Control (RRC) message; or, the control information is a dedicated message for transmitting access layer (AS) related data.

[0231] In some implementations, the RRC message is a downlink RRC message or an uplink RRC message; wherein, the downlink RRC message is an RRC message sent by the network device to the terminal device, and the uplink RRC message is an RRC message sent by the terminal device to the network device.

[0232] In some implementations, the AS-related data includes one or more of the following data types: model training dataset; measurement-related data.

[0233] In some implementations, the AS-related data includes one or more of the following data types: model class data; model parameter class data; and terminal device capability-related data.

[0234] In some implementations, the format of the control information is determined based on protocol predefined information.

[0235] In some implementations, the set of DRBs is used to transmit control information.

[0236] In some implementations, the first information includes the bearer identifier corresponding to the DRB and first indication information associated with the DRB, wherein the first indication information is used to indicate a type of control information.

[0237] In some implementations, the DRB associated with the first indication information is used to transmit control information indicated by the first indication information.

[0238] In some implementations, the first information may also include the bearer group identifier corresponding to the DRB.

[0239] In some implementations, the first information includes one or more sets of DRB-related configuration parameters and a first indication information associated with a first target DRB. The first indication information is used to indicate a type of control information. The DRB-related configuration parameters include the bearer identifier corresponding to the DRB and the protocol layer configuration for implementing the DRB. The first target DRB is any one of the one or more sets of DRBs.

[0240] In some implementations, a set of DRBs associated with the first indication information is used to transmit control information indicated by the first indication information.

[0241] In some implementations, the first information further includes second indication information and / or third indication information, wherein: the second indication information is used to indicate whether the control information indicated by the first indication information is uplink control information or downlink control information, the uplink control information is control information sent by the terminal device to the network device, and the downlink control information is control information sent by the network device to the terminal device; the third indication information is used to indicate the protocol layer associated with the control information indicated by the first indication information.

[0242] In some implementations, the first information includes one or more first parameters, which are used to indicate a set of DRB-related configuration parameters, including the bearer identifier corresponding to the DRB and the protocol layer configuration for implementing the DRB.

[0243] In some implementations, the first parameter is associated with a type of control information, which is determined based on protocol predefined information.

[0244] In some implementations, a set of DRBs indicated by the first parameter is used to transmit a type of control information associated with the first parameter.

[0245] In some implementations, the set of DRBs is used to transmit one or more types of control information.

[0246] In some implementations, the first information includes a bearer identifier corresponding to the DRB and one or more fourth indication information associated with the DRB, the fourth indication information being used to indicate a type of control information.

[0247] In some implementations, the DRB associated with the one or more fourth indication messages is used to transmit one or more control information indicated by the one or more fourth indication messages.

[0248] In some implementations, the first information may also include the bearer group identifier corresponding to the DRB.

[0249] In some implementations, the first information includes one or more sets of DRB-related configuration parameters and one or more fourth indication information associated with the second target DRB. The fourth indication information is used to indicate a control information type. The DRB-related configuration parameters include the bearer identifier corresponding to the DRB and the protocol layer configuration for implementing the DRB. The second target DRB is any one of the one or more sets of DRBs.

[0250] In some implementations, a set of DRBs associated with the one or more fourth indication messages are used to transmit one or more control information indicated by the one or more fourth indication messages.

[0251] In some implementations, the first information includes one or more second parameters, which are used to indicate a set of DRB-related configuration parameters, including the bearer identifier corresponding to the DRB and the protocol layer configuration for implementing the DRB.

[0252] In some implementations, the second parameter is associated with one or more control information types, which are determined based on protocol predefined information.

[0253] In some implementations, the set of DRBs indicated by the second parameter is used to transmit one or more control information associated with the second parameter.

[0254] In some implementations, the first information includes a bearer identifier corresponding to the DRB and a first bit string information associated with the DRB, wherein the first bit string information is used to indicate one or more control information types associated with the DRB.

[0255] In some implementations, if the target bit takes the first value, the DRB associated with the first bit string information is indicated to be used to transmit the control information associated with the target bit; wherein the target bit is any bit in the first bit string information.

[0256] In some implementations, the association between the target bit and the control information type is determined based on protocol predefined information.

[0257] In some implementations, the first information may also include the bearer group identifier corresponding to the DRB.

[0258] In some implementations, the first information includes one or more sets of DRB-related configuration parameters and a first bit string information associated with a third target DRB; wherein, the DRB-related configuration parameters include a bearer identifier corresponding to the DRB, the first bit string information is used to indicate one or more control information types associated with a set of DRBs associated with the first bit string information, and the third target DRB is any one of the one or more sets of DRBs.

[0259] In some implementations, if the target bit takes the first value, then a set of DRBs associated with the first bit string information is indicated to be used to transmit control information associated with the target bit; wherein, the target bit is any bit in the first bit string information.

[0260] In some implementations, the association between the target bit and the control information type is determined based on protocol predefined information.

[0261] In some implementations, the first information includes a bearer identifier corresponding to the DRB and one or more fifth indication information associated with the DRB, the fifth indication information being associated with a control information type.

[0262] In some implementations, if the value of the fifth indication information is a second value, then the DRB associated with the fifth indication information is indicated to be used to transmit the control information associated with the fifth indication information; wherein, the fifth indication information is any one of the one or more fifth indication information.

[0263] In some implementations, the association between the fifth indication information and the control information type is determined based on protocol predefined information.

[0264] In some implementations, the first information may also include the bearer group identifier corresponding to the DRB.

[0265] In some implementations, the first information includes one or more sets of DRB-related configuration parameters and one or more fifth indication information associated with the fourth target DRB; wherein, the DRB-related configuration parameters include the bearer identifier corresponding to the DRB, the fifth indication information is associated with a control information type, and the fourth target DRB is any one of the one or more sets of DRBs.

[0266] In some implementations, if the value of the fifth indication information is a second value, then the DRB associated with the fifth indication information is indicated to be used to transmit the control information associated with the fifth indication information; wherein, the fifth indication information is any one of the one or more fifth indication information.

[0267] In some implementations, the association between the fifth indication information and the control information type is determined based on protocol predefined information.

[0268] Figure 4 is a schematic diagram of the structure of a communication device 400 provided in an embodiment of this application. The communication device 400 shown in Figure 4 is a network device. The communication device 400 includes a transmitting unit 410. The transmitting unit 410 is used to send first information to a terminal device, the first information being used to configure a set of DRBs, the set of DRBs being used to transmit one or more control information; wherein, the set of DRBs includes one or more DRBs.

[0269] In some implementations, the control information is a Radio Resource Control (RRC) message; or, the control information is a dedicated message for transmitting access layer (AS) related data.

[0270] In some implementations, the RRC message is a downlink RRC message or an uplink RRC message; wherein, the downlink RRC message is an RRC message sent by the network device to the terminal device, and the uplink RRC message is an RRC message sent by the terminal device to the network device.

[0271] In some implementations, the AS-related data includes one or more of the following data types: model training dataset; measurement-related data.

[0272] In some implementations, the AS-related data includes one or more of the following data types: model class data; model parameter class data; and terminal device capability-related data.

[0273] In some implementations, the format of the control information is determined based on protocol predefined information.

[0274] In some implementations, the set of DRBs is used to transmit control information.

[0275] In some implementations, the first information includes the bearer identifier corresponding to the DRB and first indication information associated with the DRB, wherein the first indication information is used to indicate a type of control information.

[0276] In some implementations, the DRB associated with the first indication information is used to transmit control information indicated by the first indication information.

[0277] In some implementations, the first information may also include the bearer group identifier corresponding to the DRB.

[0278] In some implementations, the first information includes one or more sets of DRB-related configuration parameters and a first indication information associated with a first target DRB. The first indication information is used to indicate a type of control information. The DRB-related configuration parameters include the bearer identifier corresponding to the DRB and the protocol layer configuration for implementing the DRB. The first target DRB is any one of the one or more sets of DRBs.

[0279] In some implementations, a set of DRBs associated with the first indication information is used to transmit control information indicated by the first indication information.

[0280] In some implementations, the first information further includes second indication information and / or third indication information, wherein: the second indication information is used to indicate whether the control information indicated by the first indication information is uplink control information or downlink control information, the uplink control information is control information sent by the terminal device to the network device, and the downlink control information is control information sent by the network device to the terminal device; the third indication information is used to indicate the protocol layer associated with the control information indicated by the first indication information.

[0281] In some implementations, the first information includes one or more first parameters, which are used to indicate a set of DRB-related configuration parameters, including the bearer identifier corresponding to the DRB and the protocol layer configuration for implementing the DRB.

[0282] In some implementations, the first parameter is associated with a type of control information, which is determined based on protocol predefined information.

[0283] In some implementations, a set of DRBs indicated by the first parameter is used to transmit a type of control information associated with the first parameter.

[0284] In some implementations, the set of DRBs is used to transmit one or more types of control information.

[0285] In some implementations, the first information includes a bearer identifier corresponding to the DRB and one or more fourth indication information associated with the DRB, the fourth indication information being used to indicate a type of control information.

[0286] In some implementations, the DRB associated with the one or more fourth indication messages is used to transmit one or more control information indicated by the one or more fourth indication messages.

[0287] In some implementations, the first information may also include the bearer group identifier corresponding to the DRB.

[0288] In some implementations, the first information includes one or more sets of DRB-related configuration parameters and one or more fourth indication information associated with the second target DRB. The fourth indication information is used to indicate a control information type. The DRB-related configuration parameters include the bearer identifier corresponding to the DRB and the protocol layer configuration for implementing the DRB. The second target DRB is any one of the one or more sets of DRBs.

[0289] In some implementations, a set of DRBs associated with the one or more fourth indication messages are used to transmit one or more control information indicated by the one or more fourth indication messages.

[0290] In some implementations, the first information includes one or more second parameters, which are used to indicate a set of DRB-related configuration parameters, including the bearer identifier corresponding to the DRB and the protocol layer configuration for implementing the DRB.

[0291] In some implementations, the second parameter is associated with one or more control information types, which are determined based on protocol predefined information.

[0292] In some implementations, the set of DRBs indicated by the second parameter is used to transmit one or more control information associated with the first parameter.

[0293] In some implementations, the first information includes a bearer identifier corresponding to the DRB and a first bit string information associated with the DRB, wherein the first bit string information is used to indicate one or more control information types associated with the DRB.

[0294] In some implementations, if the target bit takes the first value, the DRB associated with the first bit string information is indicated to be used to transmit the control information associated with the target bit; wherein the target bit is any bit in the first bit string information.

[0295] In some implementations, the association between the target bit and the control information type is determined based on protocol predefined information.

[0296] In some implementations, the first information may also include the bearer group identifier corresponding to the DRB.

[0297] In some implementations, the first information includes one or more sets of DRB-related configuration parameters and a first bit string information associated with a third target DRB; wherein, the DRB-related configuration parameters include a bearer identifier corresponding to the DRB, the first bit string information is used to indicate one or more control information types associated with a set of DRBs associated with the first bit string information, and the third target DRB is any one of the one or more sets of DRBs.

[0298] In some implementations, if the target bit takes the first value, then a set of DRBs associated with the first bit string information is indicated to be used to transmit control information associated with the target bit; wherein, the target bit is any bit in the first bit string information.

[0299] In some implementations, the association between the target bit and the control information type is determined based on protocol predefined information.

[0300] In some implementations, the first information includes a bearer identifier corresponding to the DRB and one or more fifth indication information associated with the DRB, the fifth indication information being associated with a control information type.

[0301] In some implementations, if the value of the fifth indication information is a second value, then the DRB associated with the fifth indication information is indicated to be used to transmit the control information associated with the fifth indication information; wherein, the fifth indication information is any one of the one or more fifth indication information.

[0302] In some implementations, the association between the fifth indication information and the control information type is determined based on protocol predefined information.

[0303] In some implementations, the first information may also include the bearer group identifier corresponding to the DRB.

[0304] In some implementations, the first information includes one or more sets of DRB-related configuration parameters and one or more fifth indication information associated with the fourth target DRB; wherein, the DRB-related configuration parameters include the bearer identifier corresponding to the DRB, the fifth indication information is associated with a control information type, and the fourth target DRB is any one of the one or more sets of DRBs.

[0305] In some implementations, if the value of the fifth indication information is a second value, then the DRB associated with the fifth indication information is indicated to be used to transmit the control information associated with the fifth indication information; wherein, the fifth indication information is any one of the one or more fifth indication information.

[0306] In some implementations, the association between the fifth indication information and the control information type is determined based on protocol predefined information.

[0307] Figure 5 is a schematic diagram of the structure of a communication device applicable to embodiments of this application. The dashed lines in Figure 5 indicate that the unit or module is optional. This device 500 can be used to implement the methods described in the above method embodiments. Device 500 can be a chip, a terminal device, or a network device.

[0308] The apparatus 500 may include one or more processors 510. The processor 510 may support the apparatus 500 in implementing the methods described in the preceding method embodiments. The processor 510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0309] The apparatus 500 may also include one or more memories 520. The memories 520 store a program that can be executed by the processor 510, causing the processor 510 to perform the methods described in the preceding method embodiments. The memories 520 may be independent of the processor 510 or integrated within the processor 510.

[0310] The device 500 may also include a transceiver 530. The processor 510 can communicate with other devices or chips via the transceiver 530. For example, the processor 510 can send and receive data with other devices or chips via the transceiver 530.

[0311] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to the communication device provided in this application, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0312] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in this application embodiment, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0313] This application also provides a computer program. This computer program can be applied to the communication device provided in this application, and causes the computer to execute the methods performed by the communication device in various embodiments of this application.

[0314] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0315] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0316] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0317] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0318] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0319] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0320] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0321] 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.

[0322] 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.

[0323] 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.

[0324] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0325] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

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

Claims

1. A communication method, characterized in that, include: The terminal device receives first information sent by the network device, the first information being used to configure a set of data radio bearers, the set of data radio bearers being used to transmit one or more control information; The set of data radio bearers includes one or more data radio bearers.

2. The method according to claim 1, characterized in that: The control information is a Radio Resource Control (RRC) message; or... The control information is a dedicated message used to transmit access layer related data.

3. The method according to claim 2, characterized in that, The RRC message can be a downlink RRC message or an uplink RRC message; The downlink RRC message is an RRC message sent by the network device to the terminal device, and the uplink RRC message is an RRC message sent by the terminal device to the network device.

4. The method according to claim 2, characterized in that, The access layer related data includes one or more of the following data types: Model training dataset; Measure relevant data.

5. The method according to claim 2, characterized in that, The access layer related data includes one or more of the following data types: Model class data; Model parameter data; Data related to the capabilities of terminal devices.

6. The method according to any one of claims 1 to 5, characterized in that, The format of the control information is determined based on protocol predefined information.

7. The method according to any one of claims 1 to 6, characterized in that, The set of data wireless bearers is used to transmit control information.

8. The method according to claim 7, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and first indication information associated with the data radio bearer, wherein the first indication information is used to indicate a type of control information.

9. The method according to claim 8, characterized in that, The data wireless bearer associated with the first indication information is used to transmit a type of control information indicated by the first indication information.

10. The method according to claim 8 or 9, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

11. The method according to claim 7, characterized in that: The first information includes one or more sets of configuration parameters related to data radio bearers and a first indication information associated with a first target group of data radio bearers. The first indication information is used to indicate a type of control information. The configuration parameters related to the data radio bearers include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer. The first target group of data radio bearers is any one of the one or more sets of data radio bearers.

12. The method according to claim 11, characterized in that, A set of data wireless bearers associated with the first indication information is used to transmit a type of control information indicated by the first indication information.

13. The method according to any one of claims 8 to 12, characterized in that: The first information also includes second indication information and / or third indication information, wherein: The second indication information is used to indicate whether the control information indicated by the first indication information is uplink control information or downlink control information. The uplink control information is the control information sent by the terminal device to the network device, and the downlink control information is the control information sent by the network device to the terminal device. The third indication information is used to indicate the protocol layer associated with the control information indicated by the first indication information.

14. The method according to claim 7, characterized in that, The first information includes one or more first parameters, which are used to indicate a set of configuration parameters related to the data radio bearer. The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer.

15. The method according to claim 14, characterized in that, The first parameter is associated with a type of control information, which is determined based on protocol predefined information.

16. The method according to claim 14 or 15, characterized in that, The first parameter indicates a set of data wireless bearers used to transmit control information associated with the first parameter.

17. The method according to any one of claims 1 to 6, characterized in that, The set of data wireless bearers is used to transmit one or more control information.

18. The method according to claim 17, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and one or more fourth indication information associated with the data radio bearer, wherein the fourth indication information is used to indicate a type of control information.

19. The method according to claim 18, characterized in that, The data radio bearer associated with the one or more fourth indications is used to transmit one or more control information indicated by the one or more fourth indications.

20. The method according to claim 18 or 19, characterized in that: The first information also includes the bearer group identifier corresponding to the data radio bearer.

21. The method according to claim 17, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and one or more fourth indication information associated with the second target group of data radio bearers. The fourth indication information is used to indicate a type of control information. The configuration parameters related to the data radio bearers include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer. The second target group of data radio bearers is any one of the one or more sets of data radio bearers.

22. The method according to claim 21, characterized in that, A set of data wireless bearers associated with the one or more fourth indication information is used to transmit one or more control information indicated by the one or more fourth indication information.

23. The method according to claim 17, characterized in that, The first information includes one or more second parameters, which are used to indicate a set of configuration parameters related to the data radio bearer. The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer.

24. The method according to claim 23, characterized in that, The second parameter is associated with one or more control information types, which are determined based on protocol predefined information.

25. The method according to claim 23 or 24, characterized in that, The second parameter indicates a set of data wireless bearers used to transmit one or more control information associated with the second parameter.

26. The method according to claim 17, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and a first bit string information associated with the data radio bearer, wherein the first bit string information is used to indicate one or more control information types associated with the data radio bearer.

27. The method according to claim 26, characterized in that, If the target bit takes the first value, then the data radio bearer associated with the first bit string information is used to transmit the control information associated with the target bit; The target bit is any one bit in the first bit string information.

28. The method according to claim 27, characterized in that, The association between the target bit and the control information type is determined based on protocol predefined information.

29. The method according to any one of claims 26 to 28, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

30. The method according to claim 17, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and the first bit string information associated with the third target group of data radio bearers; The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer, the first bit string information is used to indicate one or more control information types associated with a group of data radio bearers associated with the first bit string information, and the third target group of data radio bearers is any one of the group or multiple groups of data radio bearers.

31. The method according to claim 30, characterized in that, If the target bit takes the first value, then a set of data wireless bearers associated with the first bit string information is used to transmit the control information associated with the target bit; The target bit is any one bit in the first bit string information.

32. The method according to claim 31, characterized in that, The association between the target bit and the control information type is determined based on protocol predefined information.

33. The method according to claim 17, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and one or more fifth indication information associated with the data radio bearer, the fifth indication information being associated with a control information type.

34. The method according to claim 33, characterized in that, If the value of the fifth indication information is the second value, then the data wireless bearer associated with the fifth indication information is used to transmit the control information associated with the fifth indication information; The fifth indication information is any one of the one or more fifth indication information.

35. The method according to claim 33 or 34, characterized in that, The association between the fifth indication information and the control information type is determined based on protocol predefined information.

36. The method according to any one of claims 33 to 35, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

37. The method according to claim 17, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and one or more fifth indication information associated with the fourth target group of data radio bearers; The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer, the fifth indication information is associated with a control information type, and the fourth target group data radio bearer is any one of the one or more groups of data radio bearers.

38. The method according to claim 37, characterized in that, If the value of the fifth indication information is the second value, then the data wireless bearer associated with the fifth indication information is used to transmit the control information associated with the fifth indication information; The fifth indication information is any one of the one or more fifth indication information.

39. The method according to claim 37 or 38, characterized in that, The association between the fifth indication information and the control information type is determined based on protocol predefined information.

40. A communication method, characterized in that, include: The network device sends first information to the terminal device, the first information being used to configure a set of data radio bearers, the set of data radio bearers being used to transmit one or more control information; The set of data radio bearers includes one or more data radio bearers.

41. The method according to claim 40, characterized in that: The control information is a Radio Resource Control (RRC) message; or... The control information is a dedicated message used to transmit access layer related data.

42. The method according to claim 41, characterized in that, The RRC message can be a downlink RRC message or an uplink RRC message; The downlink RRC message is an RRC message sent by the network device to the terminal device, and the uplink RRC message is an RRC message sent by the terminal device to the network device.

43. The method according to claim 41, characterized in that, The access layer related data includes one or more of the following data types: Model training dataset; Measure relevant data.

44. The method according to claim 41, characterized in that, The access layer related data includes one or more of the following data types: Model class data; Model parameter data; Data related to the capabilities of terminal devices.

45. The method according to any one of claims 40 to 44, characterized in that, The format of the control information is determined based on protocol predefined information.

46. ​​The method according to any one of claims 40 to 45, characterized in that, The set of data wireless bearers is used to transmit control information.

47. The method according to claim 46, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and first indication information associated with the data radio bearer, wherein the first indication information is used to indicate a type of control information.

48. The method according to claim 47, characterized in that, The data wireless bearer associated with the first indication information is used to transmit a type of control information indicated by the first indication information.

49. The method according to claim 47 or 48, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

50. The method according to claim 46, characterized in that: The first information includes one or more sets of configuration parameters related to data radio bearers and a first indication information associated with a first target group of data radio bearers. The first indication information is used to indicate a type of control information. The configuration parameters related to the data radio bearers include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer. The first target group of data radio bearers is any one of the one or more sets of data radio bearers.

51. The method according to claim 50, characterized in that, A set of data wireless bearers associated with the first indication information is used to transmit a type of control information indicated by the first indication information.

52. The method according to any one of claims 47 to 51, characterized in that: The first information also includes second indication information and / or third indication information, wherein: The second indication information is used to indicate whether the control information indicated by the first indication information is uplink control information or downlink control information. The uplink control information is the control information sent by the terminal device to the network device, and the downlink control information is the control information sent by the network device to the terminal device. The third indication information is used to indicate the protocol layer associated with the control information indicated by the first indication information.

53. The method according to claim 46, characterized in that, The first information includes one or more first parameters, which are used to indicate a set of configuration parameters related to the data radio bearer. The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer.

54. The method according to claim 53, characterized in that, The first parameter is associated with a type of control information, which is determined based on protocol predefined information.

55. The method according to claim 53 or 54, characterized in that, The first parameter indicates a set of data wireless bearers used to transmit control information associated with the first parameter.

56. The method according to any one of claims 40 to 55, characterized in that, The set of data wireless bearers is used to transmit one or more control information.

57. The method according to claim 56, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and one or more fourth indication information associated with the data radio bearer, wherein the fourth indication information is used to indicate a type of control information.

58. The method according to claim 57, characterized in that, The data radio bearer associated with the one or more fourth indications is used to transmit one or more control information indicated by the one or more fourth indications.

59. The method according to claim 57 or 58, characterized in that: The first information also includes the bearer group identifier corresponding to the data radio bearer.

60. The method according to claim 56, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and one or more fourth indication information associated with the second target group of data radio bearers. The fourth indication information is used to indicate a type of control information. The configuration parameters related to the data radio bearers include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer. The second target group of data radio bearers is any one of the one or more sets of data radio bearers.

61. The method according to claim 60, characterized in that, A set of data wireless bearers associated with the one or more fourth indication information is used to transmit one or more control information indicated by the one or more fourth indication information.

62. The method according to claim 56, characterized in that, The first information includes one or more second parameters, which are used to indicate a set of configuration parameters related to the data radio bearer. The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer.

63. The method according to claim 62, characterized in that, The second parameter is associated with one or more control information types, which are determined based on protocol predefined information.

64. The method according to claim 62 or 63, characterized in that, The second parameter indicates a set of data wireless bearers used to transmit one or more control information associated with the first parameter.

65. The method according to claim 56, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and a first bit string information associated with the data radio bearer, wherein the first bit string information is used to indicate one or more control information types associated with the data radio bearer.

66. The method according to claim 65, characterized in that, If the target bit takes the first value, then the data radio bearer associated with the first bit string information is used to transmit the control information associated with the target bit; The target bit is any one bit in the first bit string information.

67. The method according to claim 66, characterized in that, The association between the target bit and the control information type is determined based on protocol predefined information.

68. The method according to any one of claims 65 to 67, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

69. The method according to claim 56, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and the first bit string information associated with the third target group of data radio bearers; The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer, the first bit string information is used to indicate one or more control information types associated with a group of data radio bearers associated with the first bit string information, and the third target group of data radio bearers is any one of the group or multiple groups of data radio bearers.

70. The method according to claim 69, characterized in that, If the target bit takes the first value, then a set of data wireless bearers associated with the first bit string information is used to transmit the control information associated with the target bit; The target bit is any one bit in the first bit string information.

71. The method according to claim 70, characterized in that, The association between the target bit and the control information type is determined based on protocol predefined information.

72. The method according to claim 56, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and one or more fifth indication information associated with the data radio bearer, the fifth indication information being associated with a control information type.

73. The method according to claim 72, characterized in that, If the value of the fifth indication information is the second value, then the data wireless bearer associated with the fifth indication information is used to transmit the control information associated with the fifth indication information; The fifth indication information is any one of the one or more fifth indication information.

74. The method according to claim 72 or 73, characterized in that, The association between the fifth indication information and the control information type is determined based on protocol predefined information.

75. The method according to any one of claims 72 to 74, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

76. The method according to claim 56, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and one or more fifth indication information associated with the fourth target group of data radio bearers; The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer, the fifth indication information is associated with a control information type, and the fourth target group data radio bearer is any one of the one or more groups of data radio bearers.

77. The method according to claim 76, characterized in that, If the value of the fifth indication information is the second value, then the data wireless bearer associated with the fifth indication information is used to transmit the control information associated with the fifth indication information; The fifth indication information is any one of the one or more fifth indication information.

78. The method according to claim 76 or 77, characterized in that, The association between the fifth indication information and the control information type is determined based on protocol predefined information.

79. A communication device, characterized in that, The communication device is a terminal device, and the communication device includes: A receiving unit is configured to receive first information sent by a network device, wherein the first information is used to configure a set of data radio bearers, and the set of data radio bearers is used to transmit one or more control information. The set of data radio bearers includes one or more data radio bearers.

80. The device according to claim 79, characterized in that: The control information is a Radio Resource Control (RRC) message; or... The control information is a dedicated message used to transmit access layer related data.

81. The device according to claim 80, characterized in that, The RRC message can be a downlink RRC message or an uplink RRC message; The downlink RRC message is an RRC message sent by the network device to the terminal device, and the uplink RRC message is an RRC message sent by the terminal device to the network device.

82. The device according to claim 80, characterized in that, The access layer related data includes one or more of the following data types: Model training dataset; Measure relevant data.

83. The device according to claim 80, characterized in that, The access layer related data includes one or more of the following data types: Model class data; Model parameter data; Data related to the capabilities of terminal devices.

84. The device according to any one of claims 79 to 83, characterized in that, The format of the control information is determined based on protocol predefined information.

85. The device according to any one of claims 79 to 84, characterized in that, The set of data wireless bearers is used to transmit control information.

86. The device according to claim 85, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and first indication information associated with the data radio bearer, wherein the first indication information is used to indicate a type of control information.

87. The device according to claim 86, characterized in that, The data wireless bearer associated with the first indication information is used to transmit a type of control information indicated by the first indication information.

88. The device according to claim 86 or 87, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

89. The device according to claim 85, characterized in that: The first information includes one or more sets of configuration parameters related to data radio bearers and a first indication information associated with a first target group of data radio bearers. The first indication information is used to indicate a type of control information. The configuration parameters related to the data radio bearers include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer. The first target group of data radio bearers is any one of the one or more sets of data radio bearers.

90. The device according to claim 89, characterized in that, A set of data wireless bearers associated with the first indication information is used to transmit a type of control information indicated by the first indication information.

91. The device according to any one of claims 86 to 90, characterized in that: The first information also includes second indication information and / or third indication information, wherein: The second indication information is used to indicate whether the control information indicated by the first indication information is uplink control information or downlink control information. The uplink control information is the control information sent by the terminal device to the network device, and the downlink control information is the control information sent by the network device to the terminal device. The third indication information is used to indicate the protocol layer associated with the control information indicated by the first indication information.

92. The device according to claim 85, characterized in that, The first information includes one or more first parameters, which are used to indicate a set of configuration parameters related to the data radio bearer. The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer.

93. The device according to claim 92, characterized in that, The first parameter is associated with a type of control information, which is determined based on protocol predefined information.

94. The device according to claim 92 or 93, characterized in that, The first parameter indicates a set of data wireless bearers used to transmit control information associated with the first parameter.

95. The device according to any one of claims 79 to 84, characterized in that, The set of data wireless bearers is used to transmit one or more control information.

96. The device according to claim 95, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and one or more fourth indication information associated with the data radio bearer, wherein the fourth indication information is used to indicate a type of control information.

97. The device according to claim 96, characterized in that, The data radio bearer associated with the one or more fourth indications is used to transmit one or more control information indicated by the one or more fourth indications.

98. The device according to claim 96 or 97, characterized in that: The first information also includes the bearer group identifier corresponding to the data radio bearer.

99. The device according to claim 95, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and one or more fourth indication information associated with the second target group of data radio bearers. The fourth indication information is used to indicate a type of control information. The configuration parameters related to the data radio bearers include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer. The second target group of data radio bearers is any one of the one or more sets of data radio bearers.

100. The device according to claim 99, characterized in that, A set of data wireless bearers associated with the one or more fourth indication information is used to transmit one or more control information indicated by the one or more fourth indication information.

101. The device according to claim 95, characterized in that, The first information includes one or more second parameters, which are used to indicate a set of configuration parameters related to the data radio bearer. The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer.

102. The device according to claim 101, characterized in that, The second parameter is associated with one or more control information types, which are determined based on protocol predefined information.

103. The device according to claim 101 or 102, characterized in that, The second parameter indicates a set of data wireless bearers used to transmit one or more control information associated with the second parameter.

104. The device according to claim 95, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and a first bit string information associated with the data radio bearer, wherein the first bit string information is used to indicate one or more control information types associated with the data radio bearer.

105. The device according to claim 104, characterized in that, If the target bit takes the first value, then the data radio bearer associated with the first bit string information is used to transmit the control information associated with the target bit; The target bit is any one bit in the first bit string information.

106. The device according to claim 105, characterized in that, The association between the target bit and the control information type is determined based on protocol predefined information.

107. The device according to any one of claims 104 to 106, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

108. The device according to claim 95, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and the first bit string information associated with the third target group of data radio bearers; The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer, the first bit string information is used to indicate one or more control information types associated with a group of data radio bearers associated with the first bit string information, and the third target group of data radio bearers is any one of the group or multiple groups of data radio bearers.

109. The device according to claim 108, characterized in that, If the target bit takes the first value, then a set of data wireless bearers associated with the first bit string information is used to transmit the control information associated with the target bit; The target bit is any one bit in the first bit string information.

110. The device according to claim 109, characterized in that, The association between the target bit and the control information type is determined based on protocol predefined information.

111. The device according to claim 95, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and one or more fifth indication information associated with the data radio bearer, the fifth indication information being associated with a control information type.

112. The device according to claim 111, characterized in that, If the value of the fifth indication information is the second value, then the data wireless bearer associated with the fifth indication information is used to transmit the control information associated with the fifth indication information; The fifth indication information is any one of the one or more fifth indication information.

113. The device according to claim 111 or 112, characterized in that, The association between the fifth indication information and the control information type is determined based on protocol predefined information.

114. The device according to any one of claims 111 to 113, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

115. The device according to claim 95, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and one or more fifth indication information associated with the fourth target group of data radio bearers; The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer, the fifth indication information is associated with a control information type, and the fourth target group data radio bearer is any one of the one or more groups of data radio bearers.

116. The device according to claim 115, characterized in that, If the value of the fifth indication information is the second value, then the data wireless bearer associated with the fifth indication information is used to transmit the control information associated with the fifth indication information; The fifth indication information is any one of the one or more fifth indication information.

117. The device according to claim 115 or 116, characterized in that, The association between the fifth indication information and the control information type is determined based on protocol predefined information.

118. A communication device, characterized in that, The communication device is a network device, and the communication device includes: A transmitting unit is configured to send first information to a terminal device, wherein the first information is configured to configure a set of data radio bearers, and the set of data radio bearers is configured to transmit one or more control information. The set of data radio bearers includes one or more data radio bearers.

119. The device according to claim 118, characterized in that: The control information is a Radio Resource Control (RRC) message; or... The control information is a dedicated message used to transmit access layer related data.

120. The device according to claim 119, characterized in that, The RRC message can be a downlink RRC message or an uplink RRC message; The downlink RRC message is an RRC message sent by the network device to the terminal device, and the uplink RRC message is an RRC message sent by the terminal device to the network device.

121. The device according to claim 119, characterized in that, The access layer related data includes one or more of the following data types: Model training dataset; Measure relevant data.

122. The device according to claim 119, characterized in that, The access layer related data includes one or more of the following data types: Model class data; Model parameter data; Data related to the capabilities of terminal devices.

123. The device according to any one of claims 118 to 122, characterized in that, The format of the control information is determined based on protocol predefined information.

124. The device according to any one of claims 118 to 123, characterized in that, The set of data wireless bearers is used to transmit control information.

125. The device according to claim 124, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and first indication information associated with the data radio bearer, wherein the first indication information is used to indicate a type of control information.

126. The device according to claim 125, characterized in that, The data wireless bearer associated with the first indication information is used to transmit a type of control information indicated by the first indication information.

127. The device according to claim 125 or 126, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

128. The device according to claim 124, characterized in that: The first information includes one or more sets of configuration parameters related to data radio bearers and a first indication information associated with a first target group of data radio bearers. The first indication information is used to indicate a type of control information. The configuration parameters related to the data radio bearers include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer. The first target group of data radio bearers is any one of the one or more sets of data radio bearers.

129. The device according to claim 128, characterized in that, A set of data wireless bearers associated with the first indication information is used to transmit a type of control information indicated by the first indication information.

130. The device according to any one of claims 125 to 129, characterized in that: The first information also includes second indication information and / or third indication information, wherein: The second indication information is used to indicate whether the control information indicated by the first indication information is uplink control information or downlink control information. The uplink control information is the control information sent by the terminal device to the network device, and the downlink control information is the control information sent by the network device to the terminal device. The third indication information is used to indicate the protocol layer associated with the control information indicated by the first indication information.

131. The device according to claim 124, characterized in that, The first information includes one or more first parameters, which are used to indicate a set of configuration parameters related to the data radio bearer. The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer.

132. The device according to claim 131, characterized in that, The first parameter is associated with a type of control information, which is determined based on protocol predefined information.

133. The device according to claim 131 or 132, characterized in that, The first parameter indicates a set of data wireless bearers used to transmit control information associated with the first parameter.

134. The device according to any one of claims 118 to 123, characterized in that, The set of data wireless bearers is used to transmit one or more control information.

135. The device according to claim 134, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and one or more fourth indication information associated with the data radio bearer, wherein the fourth indication information is used to indicate a type of control information.

136. The device according to claim 135, characterized in that, The data radio bearer associated with the one or more fourth indications is used to transmit one or more control information indicated by the one or more fourth indications.

137. The device according to claim 135 or 136, characterized in that: The first information also includes the bearer group identifier corresponding to the data radio bearer.

138. The device according to claim 134, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and one or more fourth indication information associated with the second target group of data radio bearers. The fourth indication information is used to indicate a type of control information. The configuration parameters related to the data radio bearers include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer. The second target group of data radio bearers is any one of the one or more sets of data radio bearers.

139. The device according to claim 138, characterized in that, A set of data wireless bearers associated with the one or more fourth indication information is used to transmit one or more control information indicated by the one or more fourth indication information.

140. The device according to claim 134, characterized in that, The first information includes one or more second parameters, which are used to indicate a set of configuration parameters related to the data radio bearer. The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer and the protocol layer configuration for implementing the data radio bearer.

141. The device according to claim 140, characterized in that, The second parameter is associated with one or more control information types, which are determined based on protocol predefined information.

142. The device according to claim 140 or 141, characterized in that, The second parameter indicates a set of data wireless bearers used to transmit one or more control information associated with the first parameter.

143. The device according to claim 134, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and a first bit string information associated with the data radio bearer, wherein the first bit string information is used to indicate one or more control information types associated with the data radio bearer.

144. The device according to claim 143, characterized in that, If the target bit takes the first value, then the data radio bearer associated with the first bit string information is used to transmit the control information associated with the target bit; The target bit is any one bit in the first bit string information.

145. The device according to claim 144, characterized in that, The association between the target bit and the control information type is determined based on protocol predefined information.

146. The device according to any one of claims 143 to 145, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

147. The device according to claim 134, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and the first bit string information associated with the third target group of data radio bearers; The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer, the first bit string information is used to indicate one or more control information types associated with a group of data radio bearers associated with the first bit string information, and the third target group of data radio bearers is any one of the group or multiple groups of data radio bearers.

148. The device according to claim 147, characterized in that, If the target bit takes the first value, then a set of data wireless bearers associated with the first bit string information is used to transmit the control information associated with the target bit; The target bit is any one bit in the first bit string information.

149. The device according to claim 148, characterized in that, The association between the target bit and the control information type is determined based on protocol predefined information.

150. The device according to claim 134, characterized in that, The first information includes a bearer identifier corresponding to the data radio bearer and one or more fifth indication information associated with the data radio bearer, the fifth indication information being associated with a control information type.

151. The device according to claim 150, characterized in that, If the value of the fifth indication information is the second value, then the data wireless bearer associated with the fifth indication information is used to transmit the control information associated with the fifth indication information; The fifth indication information is any one of the one or more fifth indication information.

152. The device according to claim 150 or 151, characterized in that, The association between the fifth indication information and the control information type is determined based on protocol predefined information.

153. The device according to any one of claims 150 to 152, characterized in that, The first information also includes the bearer group identifier corresponding to the data radio bearer.

154. The device according to claim 134, characterized in that, The first information includes one or more sets of configuration parameters related to data radio bearers and one or more fifth indication information associated with the fourth target group of data radio bearers; The configuration parameters related to the data radio bearer include the bearer identifier corresponding to the data radio bearer, the fifth indication information is associated with a control information type, and the fourth target group data radio bearer is any one of the one or more groups of data radio bearers.

155. The device according to claim 154, characterized in that, If the value of the fifth indication information is the second value, then the data wireless bearer associated with the fifth indication information is used to transmit the control information associated with the fifth indication information; The fifth indication information is any one of the one or more fifth indication information.

156. The device according to claim 154 or 155, characterized in that, The association between the fifth indication information and the control information type is determined based on protocol predefined information.

157. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the communication device performs the method as described in any one of claims 1 to 39 or the method as described in any one of claims 40 to 78.

158. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform the method as claimed in any one of claims 1 to 39 or the method as claimed in any one of claims 40 to 78.

159. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as claimed in any one of claims 1 to 39 or the method as claimed in any one of claims 40 to 78.

160. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1 to 39 or the method as described in any one of claims 40 to 78.

161. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as claimed in any one of claims 1 to 39 or the method as claimed in any one of claims 40 to 78.

162. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1 to 39 or the method as described in any one of claims 40 to 78.

Images