Communication methods, terminal devices and network devices

Abstract

Provided in the present application are communication methods, terminal devices and network devices. A communication method comprises: a terminal device receiving first configuration information sent by a network device, wherein the first configuration information is used for configuring a first configuration field in an RRC configuration, and the first configuration information is an RRC message or a MAC CE. In the embodiments of the present application, a network device may configure a first configuration field in an RRC configuration by means of an RRC message or a MAC CE, thereby helping improve the flexibility of RRC configuration for terminal devices.

Description

Communication methods, terminal equipment and network equipment Technical Field

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

[0002] Currently, network devices adjust the transmission and reception of wireless signals by configuring radio resource control (RRC) for terminal devices. However, traditional RRC configuration methods are relatively simple and inflexible. Summary of the Invention

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

[0004] In a first aspect, a communication method is provided, comprising: a terminal device receiving first configuration information sent by a network device, the first configuration information being used to configure a first configuration field in an RRC configuration, the first configuration information being an RRC message or a medium access control element (MAC CE).

[0005] Secondly, a communication method is provided, comprising: a network device sending first configuration information to a terminal device, the first configuration information being used to configure a first configuration field in an RRC configuration, the first configuration information being an RRC message or a MAC CE.

[0006] Thirdly, a terminal device is provided, comprising: a receiving unit, configured to receive first configuration information sent by a network device, the first configuration information being used to configure a first configuration field in an RRC configuration, the first configuration information being an RRC message or a MAC CE.

[0007] Fourthly, a network device is provided, comprising: a sending unit, configured to send first configuration information to a terminal device, the first configuration information being used to configure a first configuration field in an RRC configuration, the first configuration information being an RRC message or a MAC CE.

[0008] Fifthly, a terminal device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory, causing the terminal device to perform some or all of the steps in the method of the first aspect.

[0009] In a sixth aspect, a network device is provided, including a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the network device to perform some or all of the steps in the method of the second aspect.

[0010] Seventhly, embodiments of this application provide a communication system including the aforementioned terminal device and / or network device. In another possible design, the system may further include other devices that interact with the terminal device or network device as described in the embodiments of this application.

[0011] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device (e.g., a terminal device or a network device) to perform some or all of the steps in the methods described above.

[0012] Ninthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device (e.g., a terminal device or a network device) to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0013] In a tenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects. Attached Figure Description

[0014] Figure 1 shows the wireless communication system 100 used in an embodiment of this application.

[0015] Figure 2 is a schematic flowchart of a communication method according to an embodiment of this application.

[0016] Figure 3 is a schematic flowchart of the configuration scheme of the first configuration domain in an embodiment of this application.

[0017] Figure 4 is a schematic diagram of the scheme for determining the start time of processing delay in an embodiment of this application.

[0018] Figure 5 is a schematic diagram of a scheme for determining the start time of processing delay in another embodiment of this application.

[0019] Figure 6 is a schematic diagram of a terminal device according to an embodiment of this application.

[0020] Figure 7 is a schematic diagram of a network device according to an embodiment of this application.

[0021] Figure 8 is a schematic structural diagram of a communication device according to an embodiment of this application. Detailed Implementation

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

[0023] Figure 1 illustrates a wireless communication system 100 according to an embodiment 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 may provide communication coverage for a specific geographical area and may communicate with the terminal device 120 located within that coverage area.

[0024] Figure 1 illustrates an exemplary network device and two terminals. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include other terminal devices within its coverage area. This application embodiment does not limit this.

[0025] Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment.

[0026] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th generation (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 6th generation mobile communication systems, satellite communication systems, and so on.

[0027] 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 UE can act as a base station. For example, the UE can act as a scheduling entity, providing sidelink signals between UEs in V2X or D2D, etc. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through a base station.

[0028] The network device in this application embodiment can be a device for communicating with a terminal device. This network device can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master MeNB, auxiliary SeNB, multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0029] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0030] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

[0031] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0032] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0033] RRC configuration messages

[0034] In some scenarios, network devices can send RRC messages (also known as RRC configuration messages) to terminal devices to configure the wireless signal transmission and reception methods of the terminal devices.

[0035] In some implementations, RRC configuration messages can be carried in broadcast messages (e.g., system information block (SIB)1) or terminal-specific configuration messages (RRC reconfiguration messages).

[0036] In some implementations, the configuration fields (also known as RRC configuration fields) configured in the RRC configuration message can include mandatory fields and optional fields. Optional fields can be further subdivided into conditional optional fields (marked as CondTag) and regular optional fields (marked as NEED "code" or default) based on their storage method (e.g., need code) and their dependency on other configuration fields.

[0037] In some implementations, the mandatory field refers to the configuration field that the network device must provide when providing RRC configuration messages.

[0038] In some implementations, optional fields refer to the configuration fields that network devices can optionally provide when providing RRC configuration messages.

[0039] In some implementations, for conditionally optional fields, the configuration prerequisite for this type of configuration field is whether other configuration fields are configured.

[0040] In some implementations, for regular optional fields, this type of configuration field can include: Default field, Need S field, Need M field, Need N field, and Need R field.

[0041] In some implementations, if the default domain does not exist in the RRC configuration provided by the network device, the terminal device can use the default value specified by the protocol as the value of the default domain.

[0042] In some implementations, for the Need S field, if this configuration field does not exist in the RRC configuration provided by the network device, the protocol specifies the terminal behavior in the absence of this configuration field. For example, the Need S field is the SMTC field in the RRC Release message. Correspondingly, if the Synchronous Signal Block-Based Measurement Timing Configuration (SMTC) field does not exist, the terminal device can use the SMTC field configuration in the "measObjectNR" measurement object configuration after the connection is released.

[0043] In some implementations, for the Need M domain, the terminal device can store the domain configuration. If the domain configuration is not present in the RRC configuration provided by the network device, the terminal device uses the domain configuration that has already been configured. For example, the Need M domain is the "radioBearerConfig" configuration domain. During the first configuration process, the network device provides the configuration information for the "radioBearerConfig" configuration domain through an RRC reconfiguration message. Subsequently, during the second configuration process, if the RRC reconfiguration message provided by the network device does not include the configuration information for the "radioBearerConfig" configuration domain, the terminal device can use the configuration information for the "radioBearerConfig" configuration domain provided in the first RRC reconfiguration message.

[0044] In some implementations, the terminal device does not store the Need N domain configuration. When the network device provides the domain configuration, the terminal device performs an operation only once for that domain configuration (i.e., one-shot). If the configuration domain is not present in the RRC configuration provided by the network device, the terminal device does not perform any action. For example, if the Need N domain is the "SK-Counter" configuration domain, and the network device provides the "SK-Counter" configuration domain via an RRC reconfiguration message, the terminal device updates the key based on the domain value. If the RRC reconfiguration message does not carry the "SK-Counter" configuration domain, the terminal device does not perform any action for that "SK-Counter" configuration domain.

[0045] In some implementations, for the Need R domain, the terminal device stores the domain configuration. If the configuration field is not present in the RRC configuration provided by the network device, the terminal device deletes the domain configuration. For example, the Need R domain includes a cyclic prefix (CP) configuration field "cyclicPrefix" for the bandwidth part (BWP). During the first configuration process, the network device provides the BWP configuration field "cyclicPrefix" via an RRC reconfiguration message. Subsequently, during the second configuration process, if the RRC reconfiguration provided by the network device does not carry the configuration field "cyclicPrefix", the terminal device deletes the value of the configuration field "cyclicPrefix" stored in the first configuration.

[0046] As described above, network devices can only perform RRC configuration for terminal devices via RRC messages. This configuration method is not flexible enough. Therefore, to address this issue, embodiments of this application provide a communication method in which network devices can configure the first configuration field in RRC configuration via RRC messages or MAC CE. Compared to traditional solutions that can only perform configuration based on RRC messages, this method helps improve the flexibility of RRC configuration for terminal devices. The communication method of this application embodiment is described below with reference to Figure 2, which includes step S210.

[0047] In step S210, the network device sends first configuration information to the terminal device. The first configuration information is used to configure the first configuration field in the RRC configuration. The first configuration information is an RRC message or a MAC CE.

[0048] As mentioned earlier, RRC messages contain mandatory fields and bits for extending the compatibility of RRC messages. Therefore, even if a network device configures a 1-bit configuration field for a terminal device via an RRC message, the RRC message still needs to carry the mandatory field and the bits for compatibility extension, resulting in significant transmission overhead. Therefore, in this embodiment, the first configuration information can be carried on the MAC CE to configure the first configuration field in the RRC configuration, which helps reduce the overhead of transmitting the first configuration information.

[0049] Furthermore, because the RRC message format is relatively flexible and can carry a large amount of information, in this embodiment of the application, the first configuration information can also be carried in the RRC message to configure the first configuration field in the RRC configuration.

[0050] In some implementations, the first configuration field mentioned above can be configured via an RRC message. For example, an RRC message can be carried in broadcast signaling (e.g., SIB1). Another example is that an RRC message can be carried in terminal-specific signaling (e.g., an RRCReconfiguration message).

[0051] In some implementations, the first configuration information is MAC CE, and this first configuration information is used to configure the initial value of the first configuration domain or to update the value of the first configuration domain. That is, scenarios where the first configuration domain is configured via MAC CE can include configuring an initial value for the first configuration domain and / or updating the value of the first configuration domain.

[0052] In some implementations, the configuration domain configured based on MAC CE can be configured by the network device or based on a protocol predefined one.

[0053] In some implementations, the value of the first configuration field is a first value, and the first configuration information is used to update the first value to a second value. The second value is the value indicated by the first configuration information, or the second value is determined based on the first value and a third value, where the third value is the value indicated by the first configuration information. That is to say, the update method in this application embodiment can include two types: substitution update and combination update. A substitution update can be understood as replacing the first value with the second value indicated by the first configuration information. A combination update can be understood as combining the value indicated by the first configuration information (i.e., the third value) with the first value to obtain the updated value (i.e., the second value).

[0054] In some implementations, the first configuration information mentioned above is MAC CE, and the first value is configured based on an RRC message. That is to say, the first value configured based on an RRC message can be updated based on MAC CE, as shown in step S320 of Figure 3. For example, the first configuration information is MAC CE, the first value is configured based on an RRC message, and the second value is the value indicated by the first configuration information. In this case, the second value indicated by MAC CE is used to replace the first value configured based on an RRC message in the first configuration field.

[0055] For example, the first configuration information is MAC CE, the first value is configured based on the RRC message, and the second value is determined based on the first value and the third value. In this case, the first value in the first configuration field can be replaced with the second value, where the second value is determined based on the first value configured in the RRC message and the third value configured based on the MAC CE.

[0056] In some implementations, the first configuration information is an RRC message, and the first value is based on the MAC CE configuration. That is, the first value based on the MAC CE configuration can be updated based on the RRC message, as shown in step S330 of Figure 3. For example, the first configuration information is an RRC message, the first value is based on the MAC CE configuration, and the second value is the value indicated by the first configuration information. In this case, the second value indicated by the RRC message is used to replace the first value based on the MAC CE configuration in the first configuration field.

[0057] For example, the first configuration information is an RRC message, the first value is based on the MAC CE configuration, and the second value is determined based on the first value and the third value. In this case, the first value in the first configuration field can be replaced with the second value, where the second value is determined based on the first value configured by the MAC CE and the third value configured by the RRC message.

[0058] In this embodiment, the method of determining the second value based on the first and third values ​​is not limited. In some implementations, the third value can be understood as the adjustment amount of the first value as the original value to obtain the second value. For example, the second value can be obtained by adding the third value to the first value. Alternatively, the second value can be obtained by subtracting the third value from the first value. Another example is that the second value can be obtained by multiplying the first value by the third value. Yet another example is that the second value can be obtained by dividing the first value by the third value. Of course, in this embodiment, the second value can be obtained by inputting the first and third values ​​into a function operation, where the function operation can be represented, for example, as result = f(x, y), where x represents the first value, y represents the third value, and result represents the second value.

[0059] In addition, in the embodiments of this application, the method of determining the second value based on the first value and the third value can be predefined or configured by the network device.

[0060] It should be understood that the embodiments of this application do not limit the method of configuring the first configuration domain through the first configuration information. In some implementations, the first configuration information is used to indicate the deletion of the first value in the first configuration domain.

[0061] For ease of understanding, the configuration scheme of the first configuration field in this embodiment is described below with reference to Figure 3. Assume that the first configuration field is used to configure power control or path loss compensation related settings for the terminal device, denoted as "pathlossOffset". Furthermore, this configuration field can be configured via MAC CE or RRC messages (e.g., RRC reconfiguration messages). The method shown in Figure 3 includes steps S310 to S330.

[0062] In step S310, the network device sends an RRC reconfiguration message 1 to the terminal device. The RRC reconfiguration message 1 contains a configuration field pathlossOffset, and the value of the configuration field pathlossOffset is a first value (i.e., the initial value).

[0063] In step S320, the network device sends a MAC CE to the terminal device, which is used to update the value of the configuration field pathlossOffset from a first value to a second value.

[0064] In step S330, the network device sends an RRC reconfiguration message 2 to the terminal device. The RRC reconfiguration message 2 is used to update the value of the configuration field pathlossOffset from the second value to the third value.

[0065] The foregoing section described the scheme for configuring the first configuration field using first configuration information in the embodiments of this application. The following section describes the schemes for storing the values ​​of the first configuration field in the embodiments of this application, in conjunction with storage methods 1 to 4.

[0066] Storage Method 1: The terminal device stores a first variable (also known as a "stored variable") associated with the first configuration field. The value of the first variable is based on the RRC message and the MAC CE configuration. In other words, the terminal device can use a single stored variable to store values ​​based on both the RRC message and the MAC CE configuration, which helps reduce the complexity of storing values ​​based on these two configurations.

[0067] In some implementations, the first configuration field is associated with the first variable, which can be understood as the first variable being used to store the value corresponding to the first configuration field.

[0068] For example, suppose the first configuration field is used to configure power control or path loss compensation related settings for the terminal device, denoted as "pathlossOffset". In this case, the first configuration field can be associated with a stored variable "VarPathlossOffset". If the terminal device receives the value of the configuration field pathlossOffset from the RRC message configuration and the value of the configuration field pathlossOffset from the MAC CE configuration, the terminal device can update the value stored in the stored variable "VarPathlossOffset" based on the latest received value of the configuration field pathlossOffset.

[0069] Storage Method 2: The terminal device stores a first variable and a second variable associated with the first configuration field. The value of the first variable is based on the RRC message configuration, and the value of the second variable is based on the MAC CE configuration. In other words, the terminal device can use multiple stored variables to store values ​​configured based on RRC messages and MAC CE respectively, allowing the terminal device to flexibly choose whether to use the value configured based on RRC messages or the value configured based on MAC CE.

[0070] In some implementations, the first configuration field is associated with a first variable and a second variable, which can be understood as the first variable and the second variable being used to store the value corresponding to the first configuration field.

[0071] For example, suppose the first configuration field is used to configure power control or path loss compensation related settings for the terminal device, denoted as "pathlossOffset". In this case, the first configuration field can be associated with the storage variables "VarPathlossOffset-RRC" and "VarPathlossOffset-MAC". The storage variable "VarPathlossOffset-RRC" is used to store the value of the configuration field pathlossOffset based on the RRC message configuration, and the storage variable "VarPathlossOffset-MAC" is used to store the value of the configuration field pathlossOffset based on the MAC CE configuration.

[0072] Accordingly, if the terminal device receives the value of the configuration field pathlossOffset indicated by the RRC message, the terminal device can update the value stored in the storage variable "VarPathlossOffset-RRC" based on the value of the configuration field pathlossOffset indicated by the RRC message. If the terminal device receives the value of the configuration field pathlossOffset indicated by the MAC CE, the terminal device can update the value stored in the storage variable "VarPathlossOffset-MAC" based on the value of the configuration field pathlossOffset indicated by the MAC CE.

[0073] Storage Method 3: The terminal device stores the first variable associated with the first configuration field. The value of the first variable is configured based on the RRC message. The value of the first configuration field configured based on the MAC CE is not stored by the terminal device. That is to say, the first variable in the terminal device can only store the value of the first configuration field configured based on the RRC message.

[0074] In some implementations, the first configuration field is associated with the first variable, which can be understood as the first variable being used to store the value corresponding to the first configuration field.

[0075] For example, suppose the first configuration field is used to configure power control or path loss compensation related settings for the terminal device, denoted as "pathlossOffset". In this case, the first configuration field can be associated with a storage variable "VarPathlossOffset-RRC", where the storage variable "VarPathlossOffset-RRC" is used to store the value of the configuration field pathlossOffset based on the RRC message configuration, but not to store the value of the configuration field pathlossOffset based on the MAC CE configuration.

[0076] Accordingly, if the terminal device receives the value of the configuration field pathlossOffset indicated by the RRC message, the terminal device can update the value stored in the storage variable "VarPathlossOffset-RRC" based on the value of the configuration field pathlossOffset indicated by the RRC message. If the terminal device receives the value of the configuration field pathlossOffset indicated by the MAC CE, the terminal device does not update the value stored in the storage variable "VarPathlossOffset-RRC".

[0077] Storage Method 4: The terminal device stores a second variable associated with the first configuration field. The value of the second variable is based on the MAC CE configuration, while the value of the first configuration field, configured based on the RRC message, is not stored by the terminal device. In other words, the first variable in the terminal device can store only the value of the first configuration field configured based on the RRC message.

[0078] In some implementations, the first configuration field is associated with the second variable, which can be understood as the second variable being used to store the value corresponding to the first configuration field.

[0079] For example, suppose the first configuration field is used to configure power control or path loss compensation related settings for the terminal device, denoted as "pathlossOffset". In this case, the first configuration field can be associated with a storage variable "VarPathlossOffset-MAC", where the storage variable "VarPathlossOffset-MAC" is used to store the value of the configuration field pathlossOffset based on the MAC CE configuration, but not to store the value of the configuration field pathlossOffset based on the RRC message configuration.

[0080] Accordingly, if the terminal device receives the value of the configuration field pathlossOffset indicated by the MAC CE, the terminal device can update the value stored in the storage variable "VarPathlossOffset-MAC" based on the value of the configuration field pathlossOffset indicated by the MAC CE. If the terminal device receives the value of the configuration field pathlossOffset indicated by the RRC message, the terminal device does not update the value stored in the storage variable "VarPathlossOffset-MAC".

[0081] The foregoing section introduced the storage scheme for the first configuration field value in the embodiments of this application. The following section, in conjunction with implementation methods 1 to 6, describes the type of the first configuration field in the embodiments of this application and its corresponding usage method. It should be understood that implementation method 1 is described using the first configuration field as an optional field as an example, while implementation methods 2 to 6 are described using the first configuration field as a regular field as an example.

[0082] In implementation method 1, the type of the first configuration field is a conditional optional field, that is, the first configuration field is configured when the first condition is met.

[0083] In some implementations, the first condition mentioned above includes one or more of the following: the terminal device is configured with a second configuration field; the second configuration field has been configured via an RRC message; the initial value of the first configuration field is configured based on an RRC message.

[0084] In this application embodiment, the combination of the above-mentioned first conditions is not limited. In some implementations, the first condition includes that the terminal device is configured with a second configuration field, and that the second configuration field has been configured via an RRC message. For example, the first configuration field is Field-1, and the second configuration field is Field-2, wherein Field-1 can be configured via an RRC message or a MAC CE, and Field-2 can be configured via an RRC message or a MAC CE. In this case, the first condition includes that the terminal device is configured with Field-2, and that Field-2 has been configured via an RRC message. If the first condition is met, then Field-1 can be configured.

[0085] In some implementations, the first condition includes that the terminal device is configured with a second configuration field, and the initial value of the first configuration field is configured based on an RRC message. For example, the first configuration field is Field-1, and the second configuration field is Field-2, where Field-1 can be configured via an RRC message or a MAC CE, and Field-2 can be configured via an RRC message or a MAC CE. In this case, the first condition includes that the terminal device is configured with Field-2, and the initial value of Field-2 is configured based on an RRC message. If the first condition is met, Field-1 can be configured.

[0086] In some implementations, the first condition includes that the terminal device is configured with a second configuration field, the second configuration field has been configured via an RRC message, and the initial value of the first configuration field is based on the RRC message configuration. For example, the first configuration field is Field-1, and the second configuration field is Field-2, where Field-1 can be configured via an RRC message or a MAC CE, and Field-2 can be configured via an RRC message or a MAC CE. In this case, the first condition includes that the terminal device is configured with Field-2, Field-2 has been configured via an RRC message, and the initial value of Field-2 is based on the RRC message configuration. If the first condition is met, then Field-1 can be configured.

[0087] Of course, in this embodiment, the first condition may include the terminal device being configured with a second configuration domain. That is, if the terminal device is configured with a second configuration domain, then the first configuration domain can be configured.

[0088] Implementation method 2: The first configuration domain is the default domain.

[0089] In some implementations, the first configuration field is associated with a first rule, which includes setting the value of the first configuration field to the default value if the RRC message does not have a configured value for the first configuration field.

[0090] In some implementations, the above default values ​​can be predefined values.

[0091] For example, the first configuration field is Field-1, and the second configuration field is Field-2, where the value of Field-1 is (1, 2, 3). The protocol stipulates that when the network device does not configure Field-1 for the terminal device, the terminal device uses the default value of 1 for Field-1. Suppose that during this configuration process, the network device configures the value of Field-1 for the terminal device via MAC CE, but does not configure the value of Field-1 via RRC message. In this case, the terminal device ignores the value of Field-1 configured via MAC CE and uses the default value of 1 as the value of Field-1.

[0092] In other implementations, the first configuration field is associated with a first rule, which includes the rule that if the RRC message or MAC CE configures the value of the first configuration field to be a first value, then the value of the first configuration field is the first value. That is, if the RRC message or MAC CE configures the value of the first configuration field, then the terminal device does not use the default value of the first configuration field.

[0093] For example, the first configuration field is Field-1, and the second configuration field is Field-2, where the value of Field-1 is (1, 2, 3). The protocol specifies that when the network device does not configure Field-1 for the terminal device, the terminal device uses the default value of 1 for Field-1. If, during this configuration process, the network device configures the value of Field-1 to 1 for the terminal device via a MAC CE or RRC message, then the terminal device will no longer use the default value of 1 as the value of Field-1, but instead will use 1 as the value of Field-1.

[0094] Implementation method 3: The first configuration domain is the Need S domain.

[0095] In some implementations, a first configuration field is associated with a second rule. The second rule includes a first action performed by the terminal device if the RRC message does not configure a value for the first configuration field. The first action is the action that the terminal device needs to perform based on protocol predefined information when the first configuration field does not exist.

[0096] For example, the first configuration field is the SMTC field in the BWP configuration, which can be configured via RRC messages and MAC CE. Additionally, protocol predefined information indicates that if the first configuration field is not present, the SMTC field configuration in measObjectNR will be used. Assuming that during this configuration round, if the BWP configuration provided by the RRC message does not include a value for the SMTC field, the terminal device will use the SMTC field configuration in measObjectNR for measurement.

[0097] In some other implementations, the first configuration field is associated with a second rule, which includes that if neither the RRC message nor the MAC CE has configured a value for the first configuration field, the terminal device performs a first action. The first action is the action that the terminal device needs to perform based on protocol predefined information when the first configuration field does not exist.

[0098] For example, the first configuration field is the SMTC field in the BWP configuration, which can be configured via RRC messages and MAC CE. Additionally, protocol predefined information indicates that if the first configuration field does not exist, the SMTC field configuration in measObjectNR will be used. Assuming that during this configuration round, if neither the RRC message nor the MAC CE configures the SMTC field value, the terminal device will use the SMTC field configuration in measObjectNR for measurement.

[0099] Implementation method 4: The first configuration domain is the Need M domain.

[0100] As described above, for the Need M field, the terminal device needs to store the value of this configuration field. This application does not limit the method by which the terminal device stores this configuration field. For related information, please refer to the descriptions of storage methods 1 to 4 above.

[0101] In some implementations, the first configuration field is associated with a third rule. This third rule includes a fourth value for the first configuration field if the RRC message does not configure a value for it. This fourth value is the value that the network device last configured for the first configuration field. In other words, the third rule indicates that if the RRC message does not provide a value for the first configuration field, the terminal device can use the most recently acquired value of the first configuration field (also known as the "latest value").

[0102] For example, Field-1 can be configured via RRC messages or MAC CE, and the latest value of Field-1 is latestValue. If, during this configuration round, the network device does not configure the value of Field-1 via RRC messages, the terminal device will use latestValue as the value of Field-1.

[0103] It should be noted that, in the embodiments of this application, the above-mentioned third rule can be used in combination with the storage method 1 and storage method 2 described above.

[0104] In some implementations, the first configuration field is associated with a third rule, which includes a fifth value if the first configuration field is not configured in the RRC message. The fifth value is the value that the network device last configured for the first configuration field via an RRC message.

[0105] For example, Field-1 can be configured via RRC messages or MAC CE. The latest value of Field-1 configured via RRC messages is `latestValue-RRC`, while the latest value of Field-1 configured via MAC CE is `latestValue-MAC`. Assuming that the network device did not configure the value of Field-1 via RRC messages during this configuration round, the terminal device will use `latestValue-RRC` as the value of Field-1.

[0106] It should be noted that, in the embodiments of this application, the above-mentioned third rule can be used in combination with the storage method 1, storage method 2 and storage method 3 described above.

[0107] In some implementations, the first configuration field is associated with a third rule, which includes a sixth value for the first configuration field if the first configuration field does not exist in the RRC message. The sixth value is the value that the network device last configured for the first configuration field via MAC CE.

[0108] For example, Field-1 can be configured via RRC messages or MAC CE. The latest value of Field-1 configured via RRC messages is `latestValue-RRC`, while the latest value of Field-1 configured via MAC CE is `latestValue-MAC`. Assuming that the network device did not configure the value of Field-1 via RRC messages during this configuration round, the terminal device will use `latestValue-MAC` as the value of Field-1.

[0109] It should be noted that, in the embodiments of this application, the above-mentioned third rule can be used in combination with the storage method 1, storage method 2 and storage method 4 described above.

[0110] Implementation method 5: The first configuration domain is the Need N domain.

[0111] As explained above, for the Need N domain, the terminal device does not need to store the value of this configuration field permanently. That is, when the network device provides the value of this configuration field, the terminal device can perform an operation based on that value only once (i.e., one-shot). However, it should be noted that when the terminal device performs an operation based on the value of this configuration field, it may need to temporarily store the value. In this case, the terminal device can use storage method 3 or storage method 4 described above to store the value of the configuration field.

[0112] In some implementations, the first configuration field is associated with a fourth rule, which includes the rule that if the RRC message does not configure a value for the first configuration field, the terminal device does not perform any action.

[0113] For example, Field-1 can be configured via RRC messages or MAC CE. Assuming that the network device does not configure the value of Field-1 via RRC messages during this configuration round, the terminal device will not perform any action. It should be understood that, in this embodiment, the terminal device does not need to store the value of Field-1.

[0114] In some implementations, the first configuration field is associated with a fourth rule, which includes the rule that if the RRC message does not configure a value for the first configuration field, then the value of the first configuration field is the value that the network device last configured for the first configuration field via an RRC message.

[0115] For example, Field-1 can be configured via RRC messages or MAC CE. The value of Field-1 configured via RRC messages is Value-RRC, while the value configured via MAC CE is Value-MAC. If, during this configuration round, the network device does not configure the value of Field-1 via RRC messages, the terminal device will use Value-RRC as the value of Field-1.

[0116] It should be noted that, in the embodiments of this application, the fourth rule described above can be used in combination with the storage method 3 described above.

[0117] In some implementations, the first configuration field is associated with a fourth rule, which includes the rule that if the RRC message does not configure a value for the first configuration field, then the value of the first configuration field is the value that the network device last configured for the first configuration field via MAC CE.

[0118] For example, Field-1 can be configured via RRC messages or MAC CE. The value of Field-1 configured via RRC messages is Value-RRC, while the value configured via MAC CE is Value-MAC. If, during this configuration round, the network device does not configure the value of Field-1 via RRC messages, the terminal device will use Value-MAC as the value of Field-1.

[0119] It should be noted that, in the embodiments of this application, the fourth rule described above can be used in combination with the storage method 4 described above.

[0120] Implementation method 6: The first configuration domain is the Need R domain.

[0121] As discussed above, for the Need R domain, the terminal device may need to store the value of this configuration domain. In this case, the terminal device can use the storage method described above to store the value of this configuration domain.

[0122] In some implementations, the first configuration field is associated with a fifth rule, which includes the terminal device releasing the value of the first configuration field if the RRC message does not configure the value of the first configuration field.

[0123] For example, Field-1 can be configured via RRC messages or MAC CE. The value of Field-1 configured via RRC messages is Value-RRC, while the value configured via MAC CE is Value-MAC. If the network device does not configure the value of Field-1 via RRC messages during this configuration process, the terminal device can release the value of Field-1.

[0124] It should be noted that, in the embodiments of this application, the fifth rule described above can be used in combination with the storage methods 1 to 4 described above.

[0125] In some implementations, the first configuration field is associated with a fifth rule, which includes the terminal device releasing the value of the first configuration field configured based on the RRC message if the RRC message does not configure the value of the first configuration field. Alternatively, the terminal device may retain the value of the first configuration field configured via MAC CE.

[0126] For example, Field-1 can be configured via RRC messages or MAC CE. The value of Field-1 configured via RRC messages is Value-RRC, while the value configured via MAC CE is Value-MAC. If the network device does not configure the value of Field-1 via RRC messages during this configuration round, the terminal device can release Value-RRC. Alternatively, the terminal device can retain Value-MAC.

[0127] It should be noted that, in the embodiments of this application, the fifth rule described above can be used in combination with the storage methods 1 to 3 described above.

[0128] In some implementations, the first configuration field is associated with a fifth rule, which includes the terminal device releasing the value of the first configuration field configured based on the MAC CE if the RRC message does not configure the value of the first configuration field. Alternatively, the terminal device may retain the value of the first configuration field configured via a previous RRC message.

[0129] For example, Field-1 can be configured via RRC messages or MAC CE. The value of Field-1 configured via RRC messages is Value-RRC, while the value configured via MAC CE is Value-MAC. If the network device does not configure the value of Field-1 via RRC messages during this configuration round, the terminal device can release Value-MAC. Alternatively, the terminal device can retain Value-RRC.

[0130] It should be noted that, in the embodiments of this application, the fifth rule described above can be used in combination with the storage method 1, storage method 2 and storage method 4 described above.

[0131] The preceding text introduced the type of the first configuration domain and its corresponding usage method in the embodiments of this application. The following text describes the method for determining the processing latency when the first configuration information is MAC CE in the embodiments of this application.

[0132] In some implementations, the processing latency of the first configuration information is determined based on a first duration and / or a second duration. In the embodiments of this application, the method for determining the processing latency during MAC CE helps network devices and terminal devices reach a consensus on the understanding of processing latency, thereby unifying the timing of network devices and terminal devices for applying the configuration domain.

[0133] In some implementations, the aforementioned first duration is determined based on the network device's configuration information and / or protocol predefined information. For example, the first duration can be 10ms or 4ms.

[0134] In some implementations, the aforementioned second duration can be determined based on the first and / or second times.

[0135] In some implementations, the aforementioned first time is the time when the terminal device receives the physical downlink channel carrying the first configuration information, where the physical downlink channel is the physical downlink channel successfully decoded by the terminal device. For example, after successfully decoding the physical downlink channel, the terminal device can use the reception time of the physical downlink channel as the first time. That is, after successfully decoding the physical downlink channel, the terminal device can deduce the reception time of the physical downlink channel based on the decoding completion time and use it as the first time. Of course, in the embodiments of this application, the first time can also be the time when the terminal device successfully decodes the physical downlink channel.

[0136] It should be noted that successfully decoding the physical downlink channel can be understood as successfully decoding the first configuration information in the physical downlink channel. For example, if the first configuration information is MAC CE, then successfully decoding the physical downlink channel can mean that the terminal device successfully decodes the MAC CE. That is to say, the decoded MAC CE conforms to the encoding rules specified in the protocol.

[0137] In some implementations, the aforementioned second time is the time when the terminal device sends the feedback information corresponding to the physical downlink channel after successfully decoding the physical downlink channel.

[0138] In this application, the method for determining the second duration is not limited. In some implementations, the second duration is determined based on the absolute value of the difference between the first time and the second time. For example, the second duration is equal to the absolute value of the difference between the first time and the second time. Another example is that the second duration can be an integer multiple of the absolute value of the difference between the first time and the second time.

[0139] In this application embodiment, the method for determining the processing latency is not limited. In some implementations, the processing latency can be determined based on the minimum or maximum value of the first duration and the second duration. For example, the processing latency can be equal to the minimum value of the first duration and the second duration, as described below with reference to Example 1. Another example is that the processing latency can be equal to the maximum value of the first duration and the second duration, as described below with reference to Example 2. Yet another example is that the processing latency can be equal to the average of the first duration and the second duration. Of course, in this application embodiment, the processing latency can be equal to the second duration, as described below with reference to Example 3, or, in this application embodiment, the processing latency can be equal to the first duration.

[0140] Example 1: The first duration T1 is represented as 10ms. After the terminal device successfully decodes the physical downlink channel carrying the first configuration information, it determines the reception time of the physical downlink channel as t1, i.e., the first time is t1. After the terminal device successfully decodes the physical downlink channel, the time to send the feedback information corresponding to the physical downlink channel is t2, i.e., the second time is t2. At this time, the second duration can be represented as T2 = t2 - t1 = 9ms, i.e., T1 > T2. Therefore, the processing delay T of the MAC CE can be represented as T = T2 = 9ms.

[0141] Example 2: The first duration T1 is represented as 10ms. After the terminal device successfully decodes the physical downlink channel carrying the first configuration information, it determines the reception time of the physical downlink channel as t1. After successfully decoding the physical downlink channel, the terminal device sends the feedback information corresponding to the physical downlink channel at time t2, i.e., the second duration is t2. In this case, the second duration can be represented as T2 = t2 - t1. If T1 > T2, then the processing delay T of the MAC CE can be represented as T = T1 = 10ms.

[0142] Example 3: After the terminal device successfully decodes the physical downlink channel carrying the first configuration information, it determines the reception time of the physical downlink channel as t1, i.e., the first time is t1. After the terminal device successfully decodes the physical downlink channel, the time to send the feedback information corresponding to the physical downlink channel is t2, i.e., the second time is t2. Then, the processing delay T of the MAC CE can be expressed as T = t2 - t1.

[0143] In some implementations, the start time of the processing delay for the first configuration information can be determined based on a first time and / or a second time.

[0144] In some implementations, the first time is the time when the terminal device receives the first configuration information via the physical downlink channel, where the physical downlink channel is the physical downlink channel that the terminal device successfully decodes. For related information, please refer to the above text.

[0145] In some implementations, the second time is the time after the terminal device successfully decodes the physical downlink channel carrying the first configuration information and then feeds back the feedback information corresponding to the physical downlink channel.

[0146] In this embodiment, the method for determining the start time of the processing delay is not limited. In some implementations, the start time of the processing delay can be determined based on a first time. For example, the start time of the processing delay can be a first time, as described below with reference to Figure 4. Of course, in this embodiment, the start time of the processing delay can be obtained by taking the first time as the start time and then adjusting for time offset.

[0147] Referring to Figure 4, assume that at time t1, the terminal device receives an initial HARQ transmission, which includes a MAC CE (as an example of first configuration information) for updating the first configuration field. However, at time t1, the terminal device fails to decode the MAC CE. Then, at time t2, the terminal device receives a HARQ retransmission carrying the aforementioned MAC CE, and successfully decodes the MAC CE. At this point, the starting time for the processing delay of the MAC CE is time t2.

[0148] It should be noted that, in this embodiment, the processing latency of the MAC CE can be used to indicate the time required for the terminal device to apply the configuration information of the first configuration field carried by the MAC CE after successfully decoding the MAC CE. That is to say, in this case, the processing latency of the MAC CE may not include the time required for the terminal device to decode the MAC CE.

[0149] In some other implementations, the start time of the aforementioned processing delay can be determined based on a second time. For example, the start time of the processing delay can be a second time, as described below with reference to Figure 5. Of course, in the embodiments of this application, the start time of the processing delay can be obtained by taking the second time as the start time and then adjusting for time offset.

[0150] Referring to Figure 5, assume that at time t1, the terminal device receives an initial HARQ transmission, which includes a MAC CE (as an example of first configuration information) for updating the first configuration field. However, at time t1, the terminal device fails to decode the MAC CE. Accordingly, at time t1-1, the terminal device sends a HARQ NACK to the network device to indicate that the MAC CE was not successfully decoded. Then, at time t2, the terminal device receives a HARQ retransmission carrying the aforementioned MAC CE, and the terminal device successfully decodes the MAC CE. Accordingly, at time t2-1, the terminal device sends a HARQ ACK to the network device to indicate that the MAC CE was successfully decoded. At this time, the starting time for the processing delay of the MAC CE is time t2-1.

[0151] It should be noted that, in this embodiment, the processing latency of the MAC CE can be used to indicate the time required for the terminal device to apply the configuration information of the first configuration field carried by the MAC CE after successfully decoding the MAC CE. That is to say, in this case, the processing latency of the MAC CE may not include the time required for the terminal device to decode the MAC CE.

[0152] The method embodiments of this application have been described in detail above with reference to Figures 1 to 5. The apparatus embodiments of this application will be described in detail below with reference to Figures 6 to 8. 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.

[0153] Figure 6 is a schematic diagram of a terminal device according to an embodiment of this application. The terminal device 600 shown in Figure 6 includes a receiving unit 610.

[0154] The receiving unit 610 is configured to receive first configuration information sent by the network device. The first configuration information is used to configure the first configuration field in the RRC message. The first configuration information is either an RRC message or a MAC CE.

[0155] In some implementations, the first configuration information is MAC CE, and the first configuration information is used to configure the initial value of the first configuration domain or to update the value of the first configuration domain.

[0156] In some implementations, the value of the first configuration field is a first value, and the first configuration information is used to indicate the deletion of the first value, or the first configuration information is used to update the first value to a second value; wherein the second value is the value indicated by the first configuration information; or, the second value is determined based on the first value and a third value, wherein the third value is the value indicated by the first configuration information.

[0157] In some implementations, the first configuration information is a MAC CE, and the first value is configured based on an RRC message; or, the first configuration information is an RRC message, and the first value is configured based on a MAC CE.

[0158] In some implementations, the terminal device stores a first variable associated with the first configuration domain, the value of which is based on RRC messages and MAC CE configuration; or, the terminal device stores a first variable and a second variable associated with the first configuration domain, the value of which is based on RRC messages and the value of which is based on MAC CE configuration; or, the terminal device stores a first variable associated with the first configuration domain, the value of which is based on RRC messages, but the value of the first configuration domain based on MAC CE configuration is not stored by the terminal device; or, the terminal device stores a second variable associated with the first configuration domain, the value of which is based on MAC CE configuration, but the value of the first configuration domain based on RRC messages is not stored by the terminal device.

[0159] In some implementations, the first configuration field is configured when a first condition is met, the first condition including one or more of the following: the terminal device is configured with a second configuration field; the second configuration field has been configured via an RRC message; the initial value of the first configuration field is configured based on an RRC message.

[0160] In some implementations, the first configuration field is associated with a first rule, which includes: if the RRC message does not configure a value for the first configuration field, then the value of the first configuration field is a default value; and / or, if the RRC message or MAC CE configures the value of the first configuration field to be a first value, then the value of the first configuration field is the first value.

[0161] In some implementations, the first configuration domain is the default domain.

[0162] In some implementations, the first configuration domain is associated with a second rule, the second rule including one of the following: if the RRC message does not configure the value of the first configuration domain, the terminal device performs a first action; if neither the RRC message nor the MAC CE configures the value of the first configuration domain, the terminal device performs a first action; wherein, the first action is the action that the terminal device needs to perform based on protocol predefined information when the first configuration domain does not exist.

[0163] In some implementations, the first configuration domain is the Need S domain.

[0164] In some implementations, the first configuration domain is associated with a third rule, which includes one of the following: if the RRC message does not configure a value for the first configuration domain, then the value of the first configuration domain is a fourth value, the fourth value being the value last configured for the first configuration domain by the network device; if the RRC message does not configure a value for the first configuration domain, then the value of the first configuration domain is a fifth value, the fifth value being the value last configured for the first configuration domain by the network device via an RRC message; if the RRC message does not contain a value for the first configuration domain, then the value of the first configuration domain is a sixth value, the sixth value being the value last configured for the first configuration domain by the network device via a MAC CE.

[0165] In some implementations, the first configuration domain is the Need M domain.

[0166] In some implementations, the first configuration domain is associated with a fourth rule, which includes one of the following: if the RRC message does not configure the value of the first configuration domain, the terminal device does not perform any action; if the RRC message does not configure the value of the first configuration domain, the value of the first configuration domain is the value that the network device last configured for the first configuration domain via an RRC message; if the RRC message does not configure the value of the first configuration domain, the value of the first configuration domain is the value that the network device last configured for the first configuration domain via a MAC CE.

[0167] In some implementations, the first configuration domain is the Need N domain.

[0168] In some implementations, the first configuration domain is associated with a fifth rule, which includes one of the following: if the RRC message does not configure the value of the first configuration domain, the terminal device releases the value of the first configuration domain; if the RRC message does not configure the value of the first configuration domain, the terminal device releases the value of the first configuration domain configured based on the RRC message; if the RRC message does not configure the value of the first configuration domain, the terminal device releases the value of the first configuration domain configured based on the MAC CE.

[0169] In some implementations, the first configuration domain is the Need R domain.

[0170] In some implementations, the first configuration information is MAC CE, and the processing delay of the first configuration information is determined based on one or more of the following: a first duration, determined based on the configuration information and / or protocol predefined information of the network device; a second duration, determined based on a first time and / or a second time; wherein, the first time is the time when the terminal device receives the physical downlink channel carrying the first configuration information, the physical downlink channel is the physical downlink channel successfully decoded by the terminal device, and the second time is the time when the terminal device sends the feedback information corresponding to the physical downlink channel after successfully decoding the physical downlink channel.

[0171] In some implementations, the second duration is determined based on the absolute value of the difference between the first time and the second time.

[0172] In some implementations, the processing delay is determined based on the minimum or maximum value of the first duration and the second duration.

[0173] In some implementations, the first configuration information is MAC CE, and the start time of the processing delay of the first configuration information is determined based on one or more of the following: a first time, the first time being the time when the terminal device receives the physical downlink channel carrying the first configuration information, the physical downlink channel being the physical downlink channel successfully decoded by the terminal device; a second time, the second time being the time when the terminal device feeds back the feedback information corresponding to the physical downlink channel after successfully decoding the physical downlink channel carrying the first configuration information.

[0174] Figure 7 is a schematic diagram of a network device according to an embodiment of this application. The network device 700 shown in Figure 7 includes: a transmitting unit 710.

[0175] The sending unit 710 is used to send first configuration information to the terminal device. The first configuration information is used to configure the first configuration field in the RRC message. The first configuration information is either an RRC message or a MAC CE.

[0176] In some implementations, the first configuration information is MAC CE, and the first configuration information is used to configure the initial value of the first configuration domain or to update the value of the first configuration domain.

[0177] In some implementations, the value of the first configuration field is a first value, and the first configuration information is used to indicate the deletion of the first value, or the first configuration information is used to update the first value to a second value; wherein the second value is the value indicated by the first configuration information; or, the second value is determined based on the first value and a third value, wherein the third value is the value indicated by the first configuration information.

[0178] In some implementations, the first configuration information is a MAC CE, and the first value is configured based on an RRC message; or, the first configuration information is an RRC message, and the first value is configured based on a MAC CE.

[0179] In some implementations, the terminal device stores a first variable associated with the first configuration domain, the value of which is based on RRC messages and MAC CE configuration; or, the terminal device stores a first variable and a second variable associated with the first configuration domain, the value of which is based on RRC messages and the value of which is based on MAC CE configuration; or, the terminal device stores a first variable associated with the first configuration domain, the value of which is based on RRC messages, but the value of the first configuration domain based on MAC CE configuration is not stored by the terminal device; or, the terminal device stores a second variable associated with the first configuration domain, the value of which is based on MAC CE configuration, but the value of the first configuration domain based on RRC messages is not stored by the terminal device.

[0180] In some implementations, the first configuration field is configured when a first condition is met, the first condition including one or more of the following: the terminal device is configured with a second configuration field; the second configuration field has been configured via an RRC message; the initial value of the first configuration field is configured based on an RRC message.

[0181] In some implementations, the first configuration field is associated with a first rule, which includes: if the RRC message does not configure a value for the first configuration field, then the value of the first configuration field is a default value; and / or, if the RRC message or MAC CE configures the value of the first configuration field to be a first value, then the value of the first configuration field is the first value.

[0182] In some implementations, the first configuration domain is the default domain.

[0183] In some implementations, the first configuration domain is associated with a second rule, the second rule including one of the following: if the RRC message does not configure the value of the first configuration domain, the terminal device performs a first action; if neither the RRC message nor the MAC CE configures the value of the first configuration domain, the terminal device performs a first action; wherein, the first action is the action that the terminal device needs to perform based on protocol predefined information when the first configuration domain does not exist.

[0184] In some implementations, the first configuration domain is the Need S domain.

[0185] In some implementations, the first configuration domain is associated with a third rule, which includes one of the following: if the RRC message does not configure a value for the first configuration domain, then the value of the first configuration domain is a fourth value, the fourth value being the value last configured for the first configuration domain by the network device; if the RRC message does not configure a value for the first configuration domain, then the value of the first configuration domain is a fifth value, the fifth value being the value last configured for the first configuration domain by the network device via an RRC message; if the RRC message does not contain a value for the first configuration domain, then the value of the first configuration domain is a sixth value, the sixth value being the value last configured for the first configuration domain by the network device via a MAC CE.

[0186] In some implementations, the first configuration domain is the Need M domain.

[0187] In some implementations, the first configuration domain is associated with a fourth rule, which includes one of the following: if the RRC message does not configure the value of the first configuration domain, the terminal device does not perform any action; if the RRC message does not configure the value of the first configuration domain, the value of the first configuration domain is the value that the network device last configured for the first configuration domain via an RRC message; if the RRC message does not configure the value of the first configuration domain, the value of the first configuration domain is the value that the network device last configured for the first configuration domain via a MAC CE.

[0188] In some implementations, the first configuration domain is the Need N domain.

[0189] In some implementations, the first configuration domain is associated with a fifth rule, which includes one of the following: if the RRC message does not configure the value of the first configuration domain, the terminal device releases the value of the first configuration domain; if the RRC message does not configure the value of the first configuration domain, the terminal device releases the value of the first configuration domain configured based on the RRC message; if the RRC message does not configure the value of the first configuration domain, the terminal device releases the value of the first configuration domain configured based on the MAC CE.

[0190] In some implementations, the first configuration domain is the Need R domain.

[0191] In some implementations, the first configuration information is MAC CE, and the processing delay of the first configuration information is determined based on one or more of the following: a first duration, determined based on the configuration information and / or protocol predefined information of the network device; a second duration, determined based on a first time and / or a second time; wherein, the first time is the time when the terminal device receives the physical downlink channel carrying the first configuration information, the physical downlink channel is the physical downlink channel successfully decoded by the terminal device, and the second time is the time when the terminal device sends the feedback information corresponding to the physical downlink channel after successfully decoding the physical downlink channel.

[0192] In some implementations, the second duration is determined based on the absolute value of the difference between the first time and the second time.

[0193] In some implementations, the processing delay is determined based on the minimum or maximum value of the first duration and the second duration.

[0194] In some implementations, the first configuration information is MAC CE, and the start time of the processing delay of the first configuration information is determined based on one or more of the following: a first time, the first time being the time when the terminal device receives the physical downlink channel carrying the first configuration information, the physical downlink channel being the physical downlink channel successfully decoded by the terminal device; a second time, the second time being the time when the terminal device feeds back the feedback information corresponding to the physical downlink channel after successfully decoding the physical downlink channel carrying the first configuration information.

[0195] Figure 8 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 8 indicate that the unit or module is optional. This device 800 can be used to implement the methods described in the above method embodiments. Device 800 can be a chip, a terminal device, or a network device.

[0196] The apparatus 800 may include one or more processors 810. The processor 810 may support the apparatus 800 in implementing the methods described in the preceding method embodiments. The processor 810 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.

[0197] The apparatus 800 may further include one or more memories 820. The memories 820 store a program that can be executed by the processor 810, causing the processor 810 to perform the methods described in the preceding method embodiments. The memories 820 may be independent of the processor 810 or integrated within the processor 810.

[0198] The device 800 may also include a transceiver 830. The processor 810 can communicate with other devices or chips via the transceiver 830. For example, the processor 810 can send and receive data with other devices or chips via the transceiver 830.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0214] 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 configuration information sent by the network device. The first configuration information is used to configure the first configuration field in the RRC configuration. The first configuration information is an RRC message or a MAC CE.

2. The method according to claim 1, characterized in that, The first configuration information is MAC CE, and the first configuration information is used to configure the initial value of the first configuration domain or to update the value of the first configuration domain.

3. The method according to claim 1, characterized in that, The value of the first configuration field is a first value, and the first configuration information is used to indicate the deletion of the first value, or the first configuration information is used to update the first value to a second value; Wherein, the second value is the value indicated by the first configuration information; or, the second value is determined based on the first value and the third value, wherein the third value is the value indicated by the first configuration information.

4. The method according to claim 3, characterized in that: The first configuration information is MAC CE, and the first value is configured based on RRC messages; or, The first configuration information is an RRC message, and the first value is based on MAC CE configuration.

5. The method according to any one of claims 1 to 4, characterized in that: The terminal device stores a first variable associated with the first configuration domain, the value of which is based on RRC messages and MAC CE configuration; or, The terminal device stores a first variable and a second variable associated with the first configuration domain. The value of the first variable is configured based on an RRC message, and the value of the second variable is configured based on a MAC CE; or... The terminal device stores a first variable associated with the first configuration field. The value of the first variable is configured based on RRC messages. The value of the first configuration field configured based on MAC CE is not stored by the terminal device. or, The terminal device stores a second variable associated with the first configuration field. The value of the second variable is based on the MAC CE configuration, while the value of the first configuration field based on the RRC message configuration is not stored by the terminal device.

6. The method according to any one of claims 1 to 5, characterized in that, The first configuration domain is configured when a first condition is met, which includes one or more of the following: The terminal device is configured with a second configuration domain; The second configuration field has been configured via RRC messages; The initial value of the first configuration field is configured based on the RRC message.

7. The method according to any one of claims 1 to 6, characterized in that, The first configuration domain is associated with a first rule, which includes: If the RRC message does not configure a value for the first configuration field, then the value for the first configuration field is the default value; and / or, If the RRC message or MAC CE configures the value of the first configuration field to be the first value, then the value of the first configuration field is the first value.

8. The method according to claim 7, characterized in that, The first configuration domain is the default domain.

9. The method according to any one of claims 1 to 6, characterized in that, The first configuration domain is associated with a second rule, and the second rule includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device performs the first action; If neither the RRC message nor the MAC CE has configured the value of the first configuration field, then the terminal device performs the first action; The first action is the action that the terminal device needs to perform, determined based on protocol predefined information, when the first configuration domain does not exist.

10. The method according to claim 9, characterized in that, The first configuration domain is the Need S domain.

11. The method according to any one of claims 1 to 6, characterized in that, The first configuration domain is associated with a third rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is a fourth value, which is the value that the network device last configured for the first configuration field; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the fifth value, which is the value that the network device last configured for the first configuration field via an RRC message; If the value of the first configuration field is not present in the RRC message, then the value of the first configuration field is a sixth value, which is the value that the network device last configured for the first configuration field via MAC CE.

12. The method according to claim 11, characterized in that, The first configuration domain is the Need M domain.

13. The method according to any one of claims 1 to 6, characterized in that, The first configuration domain is associated with a fourth rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device does not perform any action; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the value that the network device last configured for the first configuration field via an RRC message; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the value that the network device last configured for the first configuration field via MAC CE.

14. The method according to claim 13, characterized in that, The first configuration domain is the Need N domain.

15. The method according to any one of claims 1 to 6, characterized in that, The first configuration domain is associated with a fifth rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field; If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field configured based on the RRC message; If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field based on the MAC CE configuration.

16. The method according to claim 15, characterized in that, The first configuration domain is the Need R domain.

17. The method according to any one of claims 1 to 16, characterized in that, The first configuration information is MAC CE, and the processing latency of the first configuration information is determined based on one or more of the following: The first duration is determined based on the configuration information and / or protocol predefined information of the network device; The second duration is determined based on the first and / or second time. Wherein, the first time is the time when the terminal device receives the physical downlink channel carrying the first configuration information, the physical downlink channel is the physical downlink channel through which the terminal device successfully decodes the first configuration information, and the second time is the time when the terminal device sends the feedback information corresponding to the physical downlink channel after successfully decoding the physical downlink channel.

18. The method according to claim 17, characterized in that, The second duration is determined based on the absolute value of the difference between the first time and the second time.

19. The method according to claim 17 or 18, characterized in that, The processing delay is determined based on the minimum or maximum value of the first duration and the second duration.

20. The method according to any one of claims 1 to 16, characterized in that, The first configuration information is MAC CE, and the start time of the processing delay of the first configuration information is determined based on one or more of the following: The first time is the time when the terminal device receives the physical downlink channel carrying the first configuration information, and the physical downlink channel is the physical downlink channel through which the terminal device successfully decodes the first configuration information. The second time is the time after the terminal device successfully decodes the physical downlink channel carrying the first configuration information and then feeds back the feedback information corresponding to the physical downlink channel.

21. A communication method, characterized in that, include: The network device sends first configuration information to the terminal device. The first configuration information is used to configure the first configuration field in the RRC configuration. The first configuration information is an RRC message or a MAC CE.

22. The method according to claim 21, characterized in that, The first configuration information is MAC CE, and the first configuration information is used to configure the initial value of the first configuration domain or to update the value of the first configuration domain.

23. The method according to claim 21, characterized in that, The value of the first configuration field is a first value, and the first configuration information is used to indicate the deletion of the first value, or the first configuration information is used to update the first value to a second value; Wherein, the second value is the value indicated by the first configuration information; or, the second value is determined based on the first value and the third value, wherein the third value is the value indicated by the first configuration information.

24. The method according to claim 23, characterized in that: The first configuration information is MAC CE, and the first value is configured based on RRC messages; or, The first configuration information is an RRC message, and the first value is based on MAC CE configuration.

25. The method according to any one of claims 21 to 24, characterized in that: The terminal device stores a first variable associated with the first configuration domain, the value of which is based on RRC messages and MAC CE configuration; or, The terminal device stores a first variable and a second variable associated with the first configuration domain. The value of the first variable is configured based on an RRC message, and the value of the second variable is configured based on a MAC CE; or... The terminal device stores a first variable associated with the first configuration field. The value of the first variable is configured based on RRC messages. The value of the first configuration field configured based on MAC CE is not stored by the terminal device. or, The terminal device stores a second variable associated with the first configuration field. The value of the second variable is based on the MAC CE configuration, while the value of the first configuration field based on the RRC message configuration is not stored by the terminal device.

26. The method according to any one of claims 21 to 25, characterized in that, The first configuration domain is configured when a first condition is met, which includes one or more of the following: The terminal device is configured with a second configuration domain; The second configuration field has been configured via RRC messages; The initial value of the first configuration field is configured based on the RRC message.

27. The method according to any one of claims 21 to 26, characterized in that, The first configuration domain is associated with a first rule, which includes: If the RRC message does not configure a value for the first configuration field, then the value for the first configuration field is the default value; and / or, If the RRC message or MAC CE configures the value of the first configuration field to be the first value, then the value of the first configuration field is the first value.

28. The method according to claim 27, characterized in that, The first configuration domain is the default domain.

29. The method according to any one of claims 21 to 26, characterized in that, The first configuration domain is associated with a second rule, and the second rule includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device performs the first action; If neither the RRC message nor the MAC CE has configured the value of the first configuration field, then the terminal device performs the first action; The first action is the action that the terminal device needs to perform, determined based on protocol predefined information, when the first configuration domain does not exist.

30. The method according to claim 29, characterized in that, The first configuration domain is the Need S domain.

31. The method according to any one of claims 21 to 26, characterized in that, The first configuration domain is associated with a third rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is a fourth value, which is the value that the network device last configured for the first configuration field; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the fifth value, which is the value that the network device last configured for the first configuration field via an RRC message; If the value of the first configuration field is not present in the RRC message, then the value of the first configuration field is a sixth value, which is the value that the network device last configured for the first configuration field via MAC CE.

32. The method according to claim 31, characterized in that, The first configuration domain is the Need M domain.

33. The method according to any one of claims 21 to 26, characterized in that, The first configuration domain is associated with a fourth rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device does not perform any action; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the value that the network device last configured for the first configuration field via an RRC message; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the value that the network device last configured for the first configuration field via MAC CE.

34. The method according to claim 33, characterized in that, The first configuration domain is the Need N domain.

35. The method according to any one of claims 21 to 26, characterized in that, The first configuration domain is associated with a fifth rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field; If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field configured based on the RRC message; If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field based on the MAC CE configuration.

36. The method according to claim 35, characterized in that, The first configuration domain is the Need R domain.

37. The method according to any one of claims 21 to 36, characterized in that, The first configuration information is MAC CE, and the processing latency of the first configuration information is determined based on one or more of the following: The first duration is determined based on the configuration information and / or protocol predefined information of the network device; The second duration is determined based on the first and / or second time. Wherein, the first time is the time when the terminal device receives the physical downlink channel carrying the first configuration information, the physical downlink channel is the physical downlink channel that the terminal device successfully decodes, and the second time is the time when the terminal device sends the feedback information corresponding to the physical downlink channel after successfully decoding the physical downlink channel.

38. The method according to claim 37, characterized in that, The second duration is determined based on the absolute value of the difference between the first time and the second time.

39. The method according to claim 37 or 38, characterized in that, The processing delay is determined based on the minimum or maximum value of the first duration and the second duration.

40. The method according to any one of claims 21 to 36, characterized in that, The first configuration information is MAC CE, and the start time of the processing delay of the first configuration information is determined based on one or more of the following: The first time is the time when the terminal device receives the physical downlink channel carrying the first configuration information, and the physical downlink channel is the physical downlink channel that the terminal device successfully decodes; The second time is the time after the terminal device successfully decodes the physical downlink channel carrying the first configuration information and then feeds back the feedback information corresponding to the physical downlink channel.

41. A terminal device, characterized in that, include: The receiving unit is configured to receive first configuration information sent by the network device. The first configuration information is used to configure a first configuration field in the RRC configuration. The first configuration information is an RRC message or a MAC CE.

42. The terminal device according to claim 41, characterized in that, The first configuration information is MAC CE, and the first configuration information is used to configure the initial value of the first configuration domain or to update the value of the first configuration domain.

43. The terminal device according to claim 41, characterized in that, The value of the first configuration field is a first value, and the first configuration information is used to indicate the deletion of the first value, or the first configuration information is used to update the first value to a second value; Wherein, the second value is the value indicated by the first configuration information; or, the second value is determined based on the first value and the third value, wherein the third value is the value indicated by the first configuration information.

44. The terminal device according to claim 43, characterized in that: The first configuration information is MAC CE, and the first value is configured based on RRC messages; or, The first configuration information is an RRC message, and the first value is based on MAC CE configuration.

45. The terminal device according to any one of claims 41 to 44, characterized in that: The terminal device stores a first variable associated with the first configuration domain, the value of which is based on RRC messages and MAC CE configuration; or, The terminal device stores a first variable and a second variable associated with the first configuration domain. The value of the first variable is configured based on an RRC message, and the value of the second variable is configured based on a MAC CE; or... The terminal device stores a first variable associated with the first configuration field. The value of the first variable is configured based on RRC messages. The value of the first configuration field configured based on MAC CE is not stored by the terminal device. or, The terminal device stores a second variable associated with the first configuration field. The value of the second variable is based on the MAC CE configuration, while the value of the first configuration field based on the RRC message configuration is not stored by the terminal device.

46. ​​The terminal device according to any one of claims 41 to 45, characterized in that, The first configuration domain is configured when a first condition is met, which includes one or more of the following: The terminal device is configured with a second configuration domain; The second configuration field has been configured via RRC messages; The initial value of the first configuration field is configured based on the RRC message.

47. The terminal device according to any one of claims 41 to 46, characterized in that, The first configuration domain is associated with a first rule, which includes: If the RRC message does not configure a value for the first configuration field, then the value for the first configuration field is the default value; and / or, If the RRC message or MAC CE configures the value of the first configuration field to be the first value, then the value of the first configuration field is the first value.

48. The terminal device according to claim 47, characterized in that, The first configuration domain is the default domain.

49. The terminal device according to any one of claims 41 to 46, characterized in that, The first configuration domain is associated with a second rule, and the second rule includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device performs the first action; If neither the RRC message nor the MAC CE has configured the value of the first configuration field, then the terminal device performs the first action; The first action is the action that the terminal device needs to perform, determined based on protocol predefined information, when the first configuration domain does not exist.

50. The terminal device according to claim 49, characterized in that, The first configuration domain is the Need S domain.

51. The terminal device according to any one of claims 41 to 46, characterized in that, The first configuration domain is associated with a third rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is a fourth value, which is the value that the network device last configured for the first configuration field; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the fifth value, which is the value that the network device last configured for the first configuration field via an RRC message; If the value of the first configuration field is not present in the RRC message, then the value of the first configuration field is a sixth value, which is the value that the network device last configured for the first configuration field via MAC CE.

52. The terminal device according to claim 51, characterized in that, The first configuration domain is the Need M domain.

53. The terminal device according to any one of claims 41 to 46, characterized in that, The first configuration domain is associated with a fourth rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device does not perform any action; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the value that the network device last configured for the first configuration field via an RRC message; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the value that the network device last configured for the first configuration field via MAC CE.

54. The terminal device according to claim 53, characterized in that, The first configuration domain is the Need N domain.

55. The terminal device according to any one of claims 41 to 46, characterized in that, The first configuration domain is associated with a fifth rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field; If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field configured based on the RRC message; If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field based on the MAC CE configuration.

56. The terminal device according to claim 55, characterized in that, The first configuration domain is the Need R domain.

57. The terminal device according to any one of claims 41 to 56, characterized in that, The first configuration information is MAC CE, and the processing latency of the first configuration information is determined based on one or more of the following: The first duration is determined based on the configuration information and / or protocol predefined information of the network device; The second duration is determined based on the first and / or second time. Wherein, the first time is the time when the terminal device receives the physical downlink channel carrying the first configuration information, the physical downlink channel is the physical downlink channel that the terminal device successfully decodes, and the second time is the time when the terminal device sends the feedback information corresponding to the physical downlink channel after successfully decoding the physical downlink channel.

58. The terminal device according to claim 57, characterized in that, The second duration is determined based on the absolute value of the difference between the first time and the second time.

59. The terminal device according to claim 57 or 58, characterized in that, The processing delay is determined based on the minimum or maximum value of the first duration and the second duration.

60. The terminal device according to any one of claims 41 to 56, characterized in that, The first configuration information is MAC CE, and the start time of the processing delay of the first configuration information is determined based on one or more of the following: The first time is the time when the terminal device receives the physical downlink channel carrying the first configuration information, and the physical downlink channel is the physical downlink channel that the terminal device successfully decodes; The second time is the time after the terminal device successfully decodes the physical downlink channel carrying the first configuration information and then feeds back the feedback information corresponding to the physical downlink channel.

61. A network device, characterized in that, include: The sending unit is used to send first configuration information to the terminal device. The first configuration information is used to configure the first configuration field in the RRC configuration. The first configuration information is an RRC message or a MAC CE.

62. The network device according to claim 61, characterized in that, The first configuration information is MAC CE, and the first configuration information is used to configure the initial value of the first configuration domain or to update the value of the first configuration domain.

63. The network device according to claim 61, characterized in that, The value of the first configuration field is a first value, and the first configuration information is used to indicate the deletion of the first value, or the first configuration information is used to update the first value to a second value; Wherein, the second value is the value indicated by the first configuration information; or, the second value is determined based on the first value and the third value, wherein the third value is the value indicated by the first configuration information.

64. The network device according to claim 63, characterized in that: The first configuration information is MAC CE, and the first value is configured based on RRC messages; or, The first configuration information is an RRC message, and the first value is based on MAC CE configuration.

65. The network device according to any one of claims 61 to 64, characterized in that: The terminal device stores a first variable associated with the first configuration domain, the value of which is based on RRC messages and MAC CE configuration; or, The terminal device stores a first variable and a second variable associated with the first configuration domain. The value of the first variable is configured based on an RRC message, and the value of the second variable is configured based on a MAC CE; or... The terminal device stores a first variable associated with the first configuration field. The value of the first variable is configured based on RRC messages. The value of the first configuration field configured based on MAC CE is not stored by the terminal device. or, The terminal device stores a second variable associated with the first configuration field. The value of the second variable is based on the MAC CE configuration, while the value of the first configuration field based on the RRC message configuration is not stored by the terminal device.

66. The network device according to any one of claims 61 to 65, characterized in that, The first configuration domain is configured when a first condition is met, which includes one or more of the following: The terminal device is configured with a second configuration domain; The second configuration field has been configured via RRC messages; The initial value of the first configuration field is configured based on the RRC message.

67. The network device according to any one of claims 61 to 66, characterized in that, The first configuration domain is associated with a first rule, which includes: If the RRC message does not configure a value for the first configuration field, then the value for the first configuration field is the default value; and / or, If the RRC message or MAC CE configures the value of the first configuration field to be the first value, then the value of the first configuration field is the first value.

68. The network device according to claim 67, characterized in that, The first configuration domain is the default domain.

69. The network device according to any one of claims 61 to 66, characterized in that, The first configuration domain is associated with a second rule, and the second rule includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device performs the first action; If neither the RRC message nor the MAC CE has configured the value of the first configuration field, then the terminal device performs the first action; The first action is the action that the terminal device needs to perform, determined based on protocol predefined information, when the first configuration domain does not exist.

70. The network device according to claim 69, characterized in that, The first configuration domain is the Need S domain.

71. The network device according to any one of claims 61 to 66, characterized in that, The first configuration domain is associated with a third rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is a fourth value, which is the value that the network device last configured for the first configuration field; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the fifth value, which is the value that the network device last configured for the first configuration field via an RRC message; If the value of the first configuration field is not present in the RRC message, then the value of the first configuration field is a sixth value, which is the value that the network device last configured for the first configuration field via MAC CE.

72. The network device according to claim 71, characterized in that, The first configuration domain is the Need M domain.

73. The network device according to any one of claims 61 to 66, characterized in that, The first configuration domain is associated with a fourth rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device does not perform any action; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the value that the network device last configured for the first configuration field via an RRC message; If the RRC message does not configure the value of the first configuration field, then the value of the first configuration field is the value that the network device last configured for the first configuration field via MAC CE.

74. The network device according to claim 73, characterized in that, The first configuration domain is the Need N domain.

75. The network device according to any one of claims 61 to 66, characterized in that, The first configuration domain is associated with a fifth rule, which includes one of the following: If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field; If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field configured based on the RRC message; If the RRC message does not configure the value of the first configuration field, the terminal device releases the value of the first configuration field based on the MAC CE configuration.

76. The network device according to claim 75, characterized in that, The first configuration domain is the Need R domain.

77. The network device according to any one of claims 61 to 76, characterized in that, The first configuration information is MAC CE, and the processing latency of the first configuration information is determined based on one or more of the following: The first duration is determined based on the configuration information and / or protocol predefined information of the network device; The second duration is determined based on the first and / or second time. Wherein, the first time is the time when the terminal device receives the physical downlink channel carrying the first configuration information, the physical downlink channel is the physical downlink channel that the terminal device successfully decodes, and the second time is the time when the terminal device sends the feedback information corresponding to the physical downlink channel after successfully decoding the physical downlink channel.

78. The network device according to claim 77, characterized in that, The second duration is determined based on the absolute value of the difference between the first time and the second time.

79. The network device according to claim 77 or 78, characterized in that, The processing delay is determined based on the minimum or maximum value of the first duration and the second duration.

80. The network device according to any one of claims 61 to 76, characterized in that, The first configuration information is MAC CE, and the start time of the processing delay of the first configuration information is determined based on one or more of the following: The first time is the time when the terminal device receives the physical downlink channel carrying the first configuration information, and the physical downlink channel is the physical downlink channel that the terminal device successfully decodes; The second time is the time after the terminal device successfully decodes the physical downlink channel carrying the first configuration information and then feeds back the feedback information corresponding to the physical downlink channel.

81. A terminal 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 send signals so that the terminal device performs the method as described in any one of claims 1-20.

82. A network 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 network device performs the method as described in any one of claims 21-40.

83. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-40.

84. 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 described in any one of claims 1-40.

85. 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-40.

86. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-40.

87. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-40.

Images