Communication method and communication apparatus

Abstract

The present application provides a communication method and a communication apparatus. The method comprises: a first apparatus randomly accesses a second apparatus on the basis of a first resource, wherein the first resource is in an activated state; the first apparatus determines to deactivate the first resource before the random access to the second apparatus on the basis of the first resource is completed; and the first apparatus determines that the random access to the second apparatus fails, or determines a second resource used for randomly accessing the second apparatus, or randomly accesses the second apparatus on the basis of a third resource that is not associated with any characteristic. On this basis, when a terminal device randomly accesses a network device on the basis of a random access resource that can be dynamically adjusted, the delay of the random access can be reduced.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202510390563.4, filed on March 28, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] In wireless communication systems, terminal devices can access network devices through a four-step random access (RA) procedure or a two-step random access procedure. The random access procedure enables uplink synchronization between the terminal device and the network device, and the network device can also allocate uplink resources to the terminal device during this process. However, significant random access latency can negatively impact user experience; therefore, reducing random access latency is a pressing issue that needs to be addressed in this field. Summary of the Invention

[0004] This application provides a communication method and a communication device that can reduce the latency of random access when a terminal device randomly accesses a network device based on dynamically adjustable random access resources.

[0005] Firstly, a communication method is provided, which can be executed by a first device. The first device can be a terminal device, or a component applied to the terminal device (e.g., a chip, chip system, circuit, communication module, or processor), or a logic module or software capable of implementing some or all of the functions of the terminal device; this application does not limit this. The component applied to the terminal device can be within the terminal device or can be independent of the terminal device. For ease of description, the first device will be used as an example below.

[0006] The method may include: a first device randomly accessing a second device based on a first resource, wherein the first resource is active; the first device determining to deactivate the first resource before completing the random access to the second device based on the first resource; the first device determining that the random access to the second device has failed, or determining a second resource for random access to the second device, or randomly accessing the second device based on a third resource that is not associated with any characteristics.

[0007] Based on the above technical solution, the first device randomly accesses the second device based on a dynamically adjustable first resource. Before the random access to the second device is completed, the first resource is deactivated. In this case, the first device can execute any of the following possible implementation methods.

[0008] In the first possible implementation, the first device can determine that random access to the second device has failed. After determining the failure, the first device can revert to the initial steps of random access to the second device, or in other words, the first device can retry random access to the second device. Conversely, if the first resource is deactivated and the first device still attempts to retransmit the preamble using the first resource, it will result in a longer latency. Therefore, the first possible implementation terminates the preamble retransmission process early, allowing the first device to use appropriate random access resources to randomly access the second device as soon as possible, thereby reducing the latency of random access.

[0009] In a second possible implementation, the first device can determine a second resource for random access to the second device. After the first resource is deactivated, the first device can directly return to the resource set selection step, or in other words, the first device can reselect a random access resource. Based on this, not only is the process of retransmitting the preamble terminated earlier, but the random access step before resource set selection is also saved, further reducing the latency of random access.

[0010] The third possible implementation involves the first device directly accessing the second device randomly based on a third resource that is not associated with any characteristics after the first resource is deactivated. This third resource, unassociated with any characteristics, can be understood as a random access resource that is not dynamically adjusted / activated / deactivated, or as the random access resource configured in the `rach-ConfigCommon` field (corresponding to the `RACH-ConfigCommon` information cell) of the `BWP-UplinkCommon` configuration, or as the random access resource in the system message introduced by R15. Specifically, since the third resource is not dynamically adjusted / deactivated, the first device can save the resource set selection step and directly access the second device randomly based on the third resource, thus further reducing the random access latency compared to the second possible implementation.

[0011] In conjunction with the first aspect, in certain implementations of the first aspect, determining to deactivate the first resource includes: the first device receiving first information, the first information indicating to deactivate the first resource; or, the first timer timeout, the first timer timeout indicating to deactivate the first resource.

[0012] Based on the above technical solution, the first device can flexibly determine whether to activate the first resource. For example, the first device can determine whether to activate the first resource based on an instruction from a network device or based on a timer timeout.

[0013] Secondly, a communication method is provided, which can be executed by a first device and a second device. The first device and the second device can be terminal devices, or components applied to terminal devices (e.g., chips, chip systems, circuits, communication modules, or processors), or logic modules or software capable of implementing some or all of the functions of the terminal device; this application does not limit the specifics. The components applied to the terminal device can be within the terminal device or can be independent of the terminal device. For ease of description, the first device and the second device will be used as examples below.

[0014] The method may include: a first device randomly accessing a second device based on a first resource, wherein the first resource is active; before the random access to the second device based on the first resource is completed, the second device sends a first message indicating to deactivate the first resource; the first device receives the first message; the first device determines that the random access to the second device has failed, or determines a second resource for random access to the second device, or randomly accesses the second device based on a third resource that is not associated with any characteristics.

[0015] Regarding the beneficial effects not described in detail in the second aspect, please refer to the relevant description in the first aspect, which will not be repeated here.

[0016] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the second resource is a resource in a resource set that is not associated with any characteristics, or the second resource is a resource in a resource set that can be dynamically adjusted, and the second resource is in an active state.

[0017] Based on the above technical solution, after the first resource is deactivated, the first device directly returns to the resource set selection step. In this step, the first device can select to access the second device with resources from a resource set that are not associated with any characteristics. The resource will not be dynamically adjusted / deactivated. It is relatively simple to randomly access the second device based on the resource.

[0018] Alternatively, the first device can choose to access the second device using resources from a dynamically adjustable resource set. These dynamically adjustable resources can be understood as random access resources introduced in Release 19 (specifically, configured via RACH-ConfigCommon cells), random access resources for base station energy saving, or random access resources that can be activated or deactivated. This type of resource offers greater flexibility; for example, one implementation could have a shorter period compared to resources without any associated characteristics, resulting in shorter latency when this resource is selected for random access.

[0019] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the method may further include: if a random access response is not successfully received within a first time window, the first time window being used to indicate the time for waiting for a random access response; or, if a random access response is not successfully received before a second timer expires, the second timer being used to indicate the time for waiting for random access contention resolution information.

[0020] Based on the above technical solution, after the first device fails to receive a random access response, or fails to receive random access contention resolution information, it does not use the deactivated first resource to retransmit the preamble, but instead adopts any of the first to third possible implementation methods mentioned above to reduce the latency of random access.

[0021] Thirdly, a communication method is provided, which can be executed by a first device. The first device can be a terminal device, or a component applied to the terminal device (e.g., a chip, chip system, circuit, communication module, or processor), or a logic module or software capable of implementing some or all of the functions of the terminal device; this application does not limit this. The component applied to the terminal device can be within the terminal device or can be independent of the terminal device. For ease of description, the first device will be used as an example below.

[0022] The method may include: a first device receiving second information, the second information indicating a fourth resource, the fourth resource being used for non-contention-based random access, the second information not indicating the content of a first field, the first field being used to configure non-contention-based random access; the first device receiving at least one of third information and fourth information, the third information indicating a fifth resource for random access, the fifth resource being a dynamically adjustable resource, the fourth information indicating a sixth resource for random access, the sixth resource not associated with any characteristics; the first device determining the content of the first field based on the third information or the fourth information.

[0023] Fourthly, a communication method is provided, which can be executed by a first device and a second device. The first device and the second device can be terminal devices, or components applied to terminal devices (e.g., chips, chip systems, circuits, communication modules, or processors), or logic modules or software capable of implementing some or all of the functions of the terminal device; this application does not limit the specifics. The components applied to the terminal device can be within the terminal device or can be independent of the terminal device. For ease of description, the first device and the second device will be used as examples below.

[0024] The method may include: a second device sending second information, the second information indicating a fourth resource, the fourth resource being used for non-contention-based random access, the second information not indicating the content of a first field, the first field being used to configure non-contention-based random access; the second device sending at least one of third and fourth information, the third information indicating a fifth resource for random access, the fifth resource being a dynamically adjustable resource, the fourth information indicating a sixth resource for random access, the sixth resource not associated with any characteristics; a first device receiving the second information; the first device receiving at least one of the third and fourth information; the first device determining the content of the first field based on the third or fourth information.

[0025] Based on the above technical solution, the second information used to indicate non-contention-based random access resources may not indicate the content of some fields used for configuring non-contention-based random access. The absence of a field's content in the second information could be due to the field's absence in the second information, or the field existing but without content. For fields whose content is not indicated in the second information, the first device can refer to the content of the corresponding field in the information used to configure dynamically adjustable random access resources (i.e., the fifth resource) (i.e., the third information), or the first device can refer to the content of the corresponding field in the information used to configure random access resources not associated with any characteristics (i.e., the sixth resource) (i.e., the fourth information). This avoids configuration failure of non-contention-based random access due to missing configuration parameters.

[0026] In conjunction with the third or fourth aspect, in some implementations of the third or fourth aspect, the first field includes at least one of the following: a timing field, which indicates the time-domain location of the fourth resource; or a threshold field, which indicates the signal quality threshold for receiving the synchronization signal block.

[0027] In conjunction with the third or fourth aspect, in certain implementations of the third or fourth aspect, when the fifth and sixth resources overlap, or when the fifth and sixth resources do not overlap and the state of the fifth resource is deactivated, the content of the first field is determined based on the third or fourth information, including: determining the content of the first field based on the fourth information; or, when the fifth and sixth resources do not overlap and the state of the fifth resource is active, the content of the first field is determined based on the third or fourth information, including: determining the content of the first field based on the third information.

[0028] Based on the above technical solution, if the fifth resource overlaps with the sixth resource, or if the two resources do not overlap and the fifth resource is in a deactivated state, then for fields not indicated in the second information, the first device can refer to the content of the corresponding field in the fourth information. If the two resources do not overlap and the fifth resource is in an active state, then for fields not indicated in the second information, the first device can refer to the content of the corresponding field in the third information. Based on this, the first device can determine from which information to reference the configuration in any situation, avoiding non-contentionable random access configuration failure due to missing configuration parameters.

[0029] In conjunction with the third or fourth aspect, in certain implementations of the third or fourth aspect, the second information includes a timing field, and the first field includes a threshold field. The timing field is used to indicate the temporal location of the fourth resource, and the content of the timing field is not empty. Furthermore, the third information includes a first threshold field, and the fourth information includes a second threshold field. The threshold field is used to indicate the signal quality threshold of the received synchronization signal block, and the contents of the first threshold field and the second threshold field are the same. Determining the content of the first field based on the third or fourth information includes: determining the content of the first field as the content of the first threshold field based on the first threshold field included in the third information; or, determining the content of the first field as the content of the second threshold field based on the second threshold field included in the fourth information.

[0030] Based on the above technical solution, the second information used to indicate non-contention-based random access resources contains a timing field, and the content of the timing field is not empty. Therefore, the first device does not need to refer to other information to determine the content of the timing field. Furthermore, the content of the threshold field in the fourth and fifth information is the same, so the first device can obtain a consistent threshold field content regardless of whether it refers to the fourth or fifth information. Based on this, from the perspective of restricting network-side configuration, the first device can determine the content of the first field by referring to either the fourth or fifth information, thereby avoiding configuration failure of non-contention-based random access due to lack of configuration parameters.

[0031] Fifthly, a communication method is provided, which can be executed by a first device. The first device can be a terminal device, or a component applied to the terminal device (e.g., a chip, chip system, circuit, communication module, or processor), or a logic module or software capable of implementing some or all of the functions of the terminal device; this application does not limit this. The component applied to the terminal device can be within the terminal device or can be independent of the terminal device. For ease of description, the first device will be used as an example below.

[0032] The method may include: a first device receiving fifth information, the fifth information indicating a seventh resource for random access by a first type of terminal device, the seventh resource being a dynamically adjustable resource; wherein the first type of terminal device includes a terminal device supporting at least one of the following: capability reduction; enhanced capability reduction; small packet data transmission; coverage enhancement; or, slicing; the first device performing random access based on the seventh resource.

[0033] Sixthly, a communication method is provided, which can be executed by a second device. The second device can be a terminal device, or a component applied to the terminal device (e.g., a chip, chip system, circuit, communication module, or processor), or a logic module or software capable of implementing some or all of the functions of the terminal device; this application does not limit this. The component applied to the terminal device can be within the terminal device or can be independent of the terminal device. For ease of description, the second device will be used as an example below.

[0034] The method may include: a second device sending fifth information, the fifth information indicating a seventh resource for random access by a first type of terminal device, the seventh resource being a dynamically adjustable resource; wherein the first type of terminal device includes a terminal device supporting at least one of the following: capability reduction; enhanced capability reduction; small packet data transmission; coverage enhancement; or, slicing; and the second device performing random access based on the seventh resource.

[0035] Based on the above technical solution, the seventh resource indicated by the fifth information is dedicated to random access for first-type terminal devices. Therefore, if a first device of the first type sends a preamble to a second device through the seventh resource, the second device, upon receiving the preamble, can identify the first device as a first-type terminal device (i.e., early identification) and perform corresponding processing in subsequent procedures. Furthermore, the seventh resource can be dynamically adjusted. For example, the seventh resource can be activated only when the random access load in the communication system is high, and deactivated at other times, thereby saving energy consumption in the communication system. Based on this, first-type terminal devices can be identified early by network devices during random access and can utilize dynamically adjustable random access resources to save energy.

[0036] In conjunction with the fifth or sixth aspect, in some implementations of the fifth or sixth aspect, the first type of terminal device is a terminal device with reduced support capabilities, and the fifth information includes the RACH-ConfigCommon for Redcap in R19, for example, the rach-ConfigCommonRedcap-r19 field, associated with the RACH-ConfigCommon information element, or simply referred to as R19 RACH-ConfigCommonRedcap or simply referred to as rach-ConfigCommonRedcap-r19.

[0037] In a seventh aspect, a communication method is provided, which can be executed by a first device. The first device can be a terminal device, or a component applied to the terminal device (e.g., a chip, chip system, circuit, communication module, or processor), or a logic module or software capable of implementing some or all of the functions of the terminal device; this application does not limit this. The component applied to the terminal device can be within the terminal device or can be independent of the terminal device. For ease of description, the first device will be used as an example below.

[0038] The method may include: a first device receiving sixth information, the sixth information indicating an eighth resource for random access, the eighth resource being a dynamically adjustable resource; the first device determining, based on sub-information in the sixth information, that the eighth resource is used for random access by a first type of terminal device; or, the first device receiving seventh information, the seventh information indicating a first set, the first set including a preamble for random access by a first type of terminal device; the first device sending a first preamble through the eighth resource, the first preamble belonging to the first set; wherein, the first type of terminal device includes a terminal device supporting at least one of the following: capability reduction; enhanced capability reduction; small packet data transmission; coverage enhancement; or, slicing.

[0039] Eighthly, a communication method is provided, which can be executed by a second device. The second device can be a terminal device, or a component applied to the terminal device (e.g., a chip, chip system, circuit, communication module, or processor), or a logic module or software capable of implementing some or all of the functions of the terminal device; this application does not limit this. The component applied to the terminal device can be within the terminal device or can be independent of the terminal device. For ease of description, the following description directly uses the second device as an example.

[0040] The method may include: a second device sending sixth information, the sixth information indicating an eighth resource for random access, the eighth resource being a dynamically adjustable resource; the second device sending seventh information, the seventh information indicating a first set, the first set including a preamble for random access by a first type of terminal device; the second device receiving a first preamble through the eighth resource, the first preamble belonging to the first set; wherein, the first type of terminal device includes a terminal device supporting at least one of the following: capability reduction; enhanced capability reduction; small packet data transmission; coverage enhancement; or, slicing.

[0041] Based on the above technical solution, the eighth resource indicated by the sixth information is a dynamically adjustable resource. For example, the eighth resource can be activated only when the random access load in the communication system is high, and can be deactivated at other times, thereby saving energy consumption of the communication system. Furthermore, the sub-information in the sixth information can indicate that the eighth resource is dedicated to random access for first-type terminal devices. Therefore, if a first device of the first type sends a preamble to a second device through the eighth resource, the second device, upon receiving the preamble, can identify the first device as a first-type terminal device based on the received preamble. Alternatively, the second device can configure a preamble dedicated to random access for first-type terminal devices to the first device. Thus, if a first device of the first type sends this dedicated preamble to the second device through the eighth resource, the second device, upon receiving the preamble, can identify the first device as a first-type terminal device based on the preamble. Based on this, first-type terminal devices can be identified early by network devices during random access, and can also use dynamically adjustable random access resources to save energy.

[0042] In conjunction with the seventh or eighth aspect, in some implementations of the seventh or eighth aspect, the sixth information includes R19 RACH-ConfigCommon.

[0043] In conjunction with the seventh or eighth aspect, in some implementations of the seventh or eighth aspect, the sub-information in the sixth information includes FeatureCombination.

[0044] Ninthly, a communication method is provided, which can be executed by a first device. The first device may be a terminal device, or a component applied to the terminal device (e.g., a chip, chip system, circuit, communication module, or processor), or a logic module or software capable of implementing some or all of the functions of the terminal device; this application does not limit this. The component applied to the terminal device may be within the terminal device or may be independent of the terminal device. For ease of description, the first device will be used as an example below.

[0045] The method may include: a first device receiving eighth information, the eighth information indicating a ninth resource for random access by a first type of terminal device; wherein the first type of terminal device includes a terminal device supporting at least one of the following: capability reduction; enhanced capability reduction; small packet data transmission; coverage enhancement; or, slicing; the eighth information includes a second field indicating that the ninth resource is a dynamically adjustable resource; and the first device performing random access based on the ninth resource.

[0046] In a tenth aspect, a communication method is provided, which can be executed by a second device. The second device can be a terminal device, or a component applied to the terminal device (e.g., a chip, chip system, circuit, communication module, or processor), or a logic module or software capable of implementing some or all of the functions of the terminal device; this application does not limit this. The component applied to the terminal device can be within the terminal device or can be independent of the terminal device. For ease of description, the following description directly uses the second device as an example.

[0047] The method may include: a second device sending eighth information, the eighth information indicating a ninth resource for random access by a first type of terminal device; wherein the first type of terminal device includes a terminal device supporting at least one of the following: capability reduction; enhanced capability reduction; small packet data transmission; coverage enhancement; or, slicing; the eighth information includes a second field indicating that the ninth resource is a dynamically adjustable resource; and the second device performing random access based on the ninth resource.

[0048] Based on the above technical solution, the ninth resource indicated by the eighth information is a resource dedicated to random access for first-type terminal devices. Therefore, if a first device of the first type sends a preamble to a second device through the ninth resource, the second device, upon receiving the preamble, can identify the first device as a first-type terminal device based on the received preamble. Furthermore, the eighth information includes a second field indicating that the ninth resource is a dynamically adjustable resource. For example, the eighth resource can be activated only for random access when the random access load in the communication system is high, and deactivated at other times, thereby saving energy consumption in the communication system. Based on this, first-type terminal devices can be identified early by network devices during random access, allowing for appropriate processing in subsequent procedures. Furthermore, dynamically adjustable random access resources can be used to save energy.

[0049] In conjunction with the ninth or tenth aspect, in some implementations of the ninth or tenth aspect, the eighth information includes AdditionalRACH-Config-r17.

[0050] In conjunction with the ninth or tenth aspect, in some implementations of the ninth or tenth aspect, the second field includes the RACH-ConfigCommon for NES in R19, for example, the rach-ConfigCommonNES-r19 field, associated with the RACH-ConfigCommon information element.

[0051] Eleventhly, a communication apparatus is provided for performing the method in any possible implementation of any of the first to tenth aspects described above. Specifically, the apparatus may include units and / or modules for performing the method in any possible implementation of any of the first to tenth aspects, such as processing units and / or communication units.

[0052] In one implementation, the device is a communication device (such as a terminal device or a network device). When the device is a communication device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0053] In another implementation, the device is a chip, chip system, or circuit for communication equipment (such as terminal equipment or network equipment). When the device is a chip, chip system, or circuit for communication equipment, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0054] In a twelfth aspect, a communication apparatus is provided, comprising: at least one processor for executing a computer program or instructions stored in a memory to perform a method in any possible implementation of any of the first to tenth aspects described above. Optionally, the apparatus further comprises a memory for storing the computer program or instructions; correspondingly, the at least one processor is configured to execute the computer program or instructions in the memory. Optionally, the apparatus further comprises a communication interface coupled to the processor, which can be used to input information to the processor or output information from the processor. Optionally, the processor reads the computer program or instructions from the memory through the communication interface.

[0055] In one implementation, the device is a communication device (such as a terminal device or a network device).

[0056] In another implementation, the device is a chip, chip system, or circuit for communication equipment (such as terminal equipment or network equipment).

[0057] In a thirteenth aspect, a processor is provided for performing the methods provided in any one of the first to tenth aspects described above.

[0058] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0059] In a fourteenth aspect, a computer-readable storage medium is provided, on which a computer program or instructions are stored, which, when executed on a communication device, cause the communication device to perform the method provided in any one of the first to tenth aspects.

[0060] In a fifteenth aspect, a computer program product is provided, comprising a computer program or instructions for performing the methods in any possible implementation of any of the first to tenth aspects described above. In other words, when the computer program product is run on a computer, it causes the computer to perform the methods provided in any of the first to tenth aspects described above.

[0061] In a sixteenth aspect, a chip is provided, the chip including a processor and a communication interface, wherein the processor reads instructions from a memory through the communication interface and executes the methods provided in any one of the first to tenth aspects.

[0062] Optionally, as one implementation, the chip further includes a memory storing computer programs or instructions, and a processor for executing the computer programs or instructions in the memory. When the computer programs or instructions are executed, the processor is used to perform the methods provided in any one of the first to tenth aspects described above.

[0063] In a seventeenth aspect, a communication system is provided, comprising a first device (or a first communication device) and a second device (or a second communication device). The first device is configured to execute the method provided in any implementation of the first aspect, and the second device is configured to execute the method provided in any implementation of the second aspect; or, the first device is configured to execute the method provided in any implementation of the third aspect, and the second device is configured to execute the method provided in any implementation of the fourth aspect; or, the first device is configured to execute the method provided in any implementation of the fifth aspect, and the second device is configured to execute the method provided in any implementation of the sixth aspect; or, the first device is configured to execute the method provided in any implementation of the seventh aspect, and the second device is configured to execute the method provided in any implementation of the eighth aspect; or, the first device is configured to execute the method provided in any implementation of the ninth aspect, and the second device is configured to execute the method provided in any implementation of the tenth aspect. Attached Figure Description

[0064] Figure 1 is a schematic diagram of a wireless communication system applicable to an embodiment of this application.

[0065] Figure 2 is a schematic diagram of another wireless communication system applicable to an embodiment of this application.

[0066] Figure 3 is a schematic diagram of an access network device applicable to an embodiment of this application.

[0067] Figure 4 is a flowchart of a competition-based four-step random access process applicable to embodiments of this application.

[0068] Figure 5 is a flowchart of a non-contention-based random access procedure applicable to an embodiment of this application.

[0069] Figure 6 is a flowchart of a contention-based two-step random access process applicable to an embodiment of this application.

[0070] Figure 7 is a flowchart of a non-competitive two-step random access process applicable to an embodiment of this application.

[0071] Figure 8 is a schematic diagram of a communication method 800 provided in an embodiment of this application.

[0072] Figure 9 is a schematic diagram of a communication method 900 provided in an embodiment of this application.

[0073] Figure 10 is a schematic diagram of a communication method 1000 provided in an embodiment of this application.

[0074] Figure 11 is a schematic diagram of a communication method 1100 provided in an embodiment of this application.

[0075] Figure 12 is a schematic diagram of a communication method 1200 provided in an embodiment of this application.

[0076] Figure 13 is a schematic diagram of a communication method 1300 provided in an embodiment of this application.

[0077] Figure 14 is a schematic diagram of a communication device 1400 provided in an embodiment of this application.

[0078] Figure 15 is a schematic diagram of another communication device 1500 provided in an embodiment of this application.

[0079] Figure 16 is a schematic diagram of a chip system 1600 provided in an embodiment of this application. Detailed Implementation

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

[0081] Before introducing the scheme of this application, the following points should be noted.

[0082] (1) In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, implicit instruction, etc. When describing a certain instruction information as being used to instruct A, it can be understood that the instruction information carries A, carries the identifier of A, carries B which is associated with A, carries the identifier of B which is associated with A, etc. In other words, if the receiving side of a certain instruction information can determine A based on the instruction information, it can be described as the instruction information being used to instruct A, and the specific method of determination is not limited. When it is understood that the instruction information carries A, "instruction" or "used to instruct" can be replaced with "includes". In this case, a statement similar to "sending / receiving instruction information, the instruction information being used to instruct A" can be replaced with "sending / receiving A".

[0083] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0084] (2) In this application, the expression " / " is used to indicate that the objects before and after are in an "or" relationship; for example, A / B can mean: A or B. The expression "and / or" is used to indicate that the objects before and after are in a relationship of either "and" or "or"; for example, A and / or B can mean the following: A exists alone, B exists alone, A and B exist simultaneously, where A and B can be single or multiple. "At least one of the following" or similar expressions are used to indicate any combination of the listed items; for example, at least one of A, B and / or C can mean the following: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, A and C exist simultaneously, A, B and C exist simultaneously, where A, B, and C can be single or multiple.

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

[0086] (4) In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0087] (5) In this application, "first," "second," and "#1," "#2," and "#A" are merely for descriptive convenience and are used to distinguish objects, and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that such described objects can be interchanged where appropriate in order to describe solutions other than those in the embodiments of this application.

[0088] (6) In this application, "predefined" can mean a standard protocol predefined, or it can mean a pre-agreed or pre-negotiated agreement between devices. Here, "protocol" can refer to a standard protocol in the field of communications, for example, it may include fourth-generation (4G) protocols. thGeneration 4G network, fifth generation (5G) network th This application does not limit the scope to network protocols such as 5G (generation, 5G), New Radio (NR), 5.5G, and related protocols applied in future communication networks.

[0089] (7) In this application, the configuration can be signaling configuration, such as radio resource control (RRC) messages, control information (such as downlink control information (DCI)), or medium access control (MAC) signaling (e.g., MAC control element (MAC CE / MAC-CE)). As an example, signaling configuration can be configured by signaling to the terminal device. For example, the network device configures the area identifier (or the network device configures the area identifier for the terminal device). This can be understood as the network device indicating the area identifier to the terminal device through signaling.

[0090] (8) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” and “corresponding” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0091] First, let me introduce the communication system to which this application applies.

[0092] The technical solutions provided in this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication network systems. Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems. The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems, such as inter-satellite communication systems and satellite communication systems.

[0093] As an example, a satellite communication system includes satellites, which can act as base stations or as terminal devices. When a satellite acts as a base station, it can be simply referred to as a satellite base station, which can provide communication services to terminal devices. Satellite base stations can also communicate with each other. The satellite can refer to unmanned aerial vehicles (UAVs), hot air balloons, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, high-Earth orbit (HEO) satellites, etc. A satellite can also refer to a non-terrestrial base station or non-terrestrial equipment.

[0094] As an example, V2X communication can include: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0095] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The device can also be replaced by an entity, network entity, communication equipment, communication module, node, communication node, etc. This application uses a device as an example for description.

[0096] The terminal device in this application embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal device can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal device can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer (P2P), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initiation protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drone, helicopter, multiple helicopters, four helicopters, or airplanes), ship, remote control device, smart home device, industrial equipment, transportation vehicle with wireless communication capability, communication module, or roadside unit with terminal function, all conforming to the 3rd generation partnership project (3GPP) standard. The device may be a wireless communication unit (RSU), or a device built into the aforementioned device (e.g., a communication module, modem, or chip in the aforementioned device), or other processing devices connected to the wireless modem.

[0097] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or P2P.

[0098] In this embodiment, the device for implementing the functions of a terminal device, i.e., the terminal device, can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing the functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can also be configured with program instructions for performing corresponding communication functions.

[0099] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it 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, access point, transmitting and receiving point (TRP), transmitter, master station, auxiliary station, multiple standard 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. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station 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.

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

[0101] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, or DU, or devices including CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes.

[0102] In some deployments, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or radio units (RUs). CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio equipment or radio units, such as RRUs, AAUs, or RRHs.

[0103] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a radio access network can also be an open radio access network (O-RAN or ORAN) architecture. In an O-RAN system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (open RU, O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0104] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.

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

[0106] Referring to Figure 1, as an example, Figure 1 is a schematic diagram of a wireless communication system applicable to an embodiment of this application. As shown in Figure 1, the wireless communication system includes a wireless access network 100. The wireless access network 100 may be a next-generation (e.g., future or higher version) wireless access network or a traditional (e.g., 5G, 4G, 3G, or 2G) wireless access network. One or more terminal devices (120a-120j, collectively referred to as 120) may be interconnected or connected to one or more network devices (110a, 110b, collectively referred to as 110) in the wireless access network 100. Network elements in the wireless communication system are connected through interfaces (e.g., NG, Xn) or air interfaces.

[0107] When network devices and terminal devices communicate, the network device can manage one or more cells, and a cell can include at least one terminal device. A cell can be understood as an area within the wireless signal coverage range of the network device.

[0108] Figure 1 is just a schematic diagram. The wireless communication system may also include other devices, such as core network devices, wireless relay devices and / or wireless backhaul devices, which are not shown in Figure 1.

[0109] Referring to Figure 2, as an example, Figure 2 is a schematic diagram of another wireless communication system applicable to embodiments of this application. This wireless communication system may be referred to as an ORAN system, for example. The wireless communication system may include a core network, access network equipment, and a UE. As an example, the ORAN system may also include other components besides those shown in Figure 2; specific details are not limited in this application.

[0110] Access network equipment can communicate with the core network (CN) via a backhaul link. Access network equipment can also communicate with the UE via an air interface. Specifically, the BBU in the access network equipment communicates with the core network via a backhaul link. The RU in the access network equipment communicates with at least one UE via an air interface. The BBU communicates with at least one RU via a fronthaul link; the BBU and RU may or may not be co-located. A BBU includes at least one CU and at least one DU, and the CU and DU can communicate via at least one midhaul link.

[0111] Referring to Figure 3, as an example, Figure 3 is a schematic diagram of an access network device applicable to an embodiment of this application.

[0112] Optionally, the access network equipment includes a CU. The CU is a logical node that carries the radio resource control (RRC), service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, and other control functions of the access network equipment. The CU can connect to network nodes such as the core network through interfaces, such as the E2 interface. The CU may have some core network functions. The CU (e.g., the PDCP layer and / or higher layers of the CU) connects to the DU (e.g., the radio link control (RLC) layer and lower layers of the DU) through interfaces, such as the F1 interface. Optionally, the F1 interface can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). F1AP is the application protocol of the F1 interface, defining the signaling procedures of F1 in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

[0113] As an example, a CU includes CU-CP and CU-UP. CU-CP is a logical node carrying the control plane (PDCP-C) layer, which carries the RRC layer and the Packet Data Convergence Protocol layer, and is used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function (AMF) network elements, such as the access and mobility management function (AMF) in a 5G system. The AMF network element is responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. CU-UP is a logical node carrying the user plane (PDCP-U) layer, which carries the SDAP layer and the Packet Data Convergence Protocol layer, and is used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. These network elements in the core network, such as the user plane function (UPF) in a 5G system, are responsible for data forwarding and receiving in terminal devices. The above CU and DU configurations are merely examples. In practical applications, the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or to have only some protocol layer processing functions. For example, some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements. For example, based on latency, functions that require low latency can be placed in the DU, while functions that do not require low latency can be placed in the CU.

[0114] Optionally, the access network equipment includes a DU. As shown in Figure 3, the DU is a logical node carrying the RLC layer, medium access control (MAC) layer, higher physical layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one RU. The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0115] Optionally, the access network equipment includes a Runner (RU). As shown in Figure 3, the RU is a logical node that carries lower physical layer (Lower PHY) and radio frequency (RF) processing. In some examples, the RU may be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar entities. In some examples, the Lower-PHY includes PHY processing functions such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link (such as an RF chain).

[0116] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a fronthaul link through the lower-layer split CUS-plane (LLS-CUS-Plane) (or O-RAN CUS-Plane) interface. Here, CUS-Plane represents the control plane (C-Plane), user plane (UPlane), and synchronization plane (S-Plane) (CUS-Plane). LLS-CUS may include a lower-layer split control (LLS-C) interface providing the control plane and a lower-layer split user (LLS-U) interface providing the user plane. Additionally, LLS-CUS may include a lower-layer split synchronization (LLS-S) interface providing the synchronization plane. In some examples, the control plane (or control plane) refers to the real-time control between the DU and RU. The DU and RU exchange management plane information via the lower-layer split management (LLS-M) interface of the fronthaul link. The management plane (M-Plane) refers to the non-real-time management operations between the DU and RU.

[0117] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0118] Figures 1 to 3 above are illustrative examples, and the embodiments of this application are not limited thereto.

[0119] To facilitate a better understanding of the technical solution of this application, some related technologies involved in the technical solution of this application are introduced.

[0120] 1. Random access:

[0121] In wireless communication systems, terminal devices can access network devices through either a four-step random access procedure or a two-step random access procedure. The random access procedure enables uplink synchronization between the terminal device and the network device, and the network device can also allocate uplink resources to the terminal device during the random access procedure.

[0122] As an example, events that trigger random access may include at least one of the following: initial access of an idle-state terminal device; RRC connection re-establishment; downlink or uplink data arriving at a connected-state terminal device in a state of being out of sync; uplink data arriving at a connected-state terminal device but without sending a scheduling request (SR) physical uplink control channel (PUCCH) resource; cell handover; requesting an on-demand system message; beam failure recovery, etc.

[0123] As an example, random access procedures include contention-based random access (CBRA) or contention-free random access (CFRA).

[0124] Referring to Figure 4, as an example, Figure 4 is a flowchart of a contention-based four-step random access process applicable to embodiments of this application. It may include the following steps.

[0125] S410, the terminal device sends a preamble sequence, i.e., message 1 (msg1). Correspondingly, the network device receives the preamble sequence from the terminal device. This preamble sequence can also be called the RA preamble, or a preamble code, etc.

[0126] As an example, the purpose of the preamble sent by the terminal device is to inform the network device of the terminal device's random access request and to estimate the uplink timing advance (TA) based on the reception of the preamble.

[0127] S420, the network device sends a random access response (RAR), i.e., message 2 (msg2). Correspondingly, the terminal device receives the random access response from the network device.

[0128] S430, the terminal device sends message 3 (msg3). Correspondingly, the network device receives the scheduled transmission message from the terminal device.

[0129] In step S440, the network device sends a contention resolution message, i.e., message 4 (msg4). Correspondingly, the terminal device receives the contention resolution message from the network device.

[0130] Referring to Figure 5, as an example, Figure 5 is a flowchart of a non-contention-based random access procedure applicable to embodiments of this application. It may include the following steps.

[0131] In S510, the network device assigns a preamble to the terminal device. Correspondingly, the terminal device receives the preamble assigned by the network device.

[0132] Specifically, in non-contention-based random access, the preamble can be distributed to the terminal device by the network device through a dedicated message, reducing the contention resolution process.

[0133] In S520, the terminal device sends a preamble. Correspondingly, the network device receives the preamble from the terminal device.

[0134] S530, the network device sends a random access response. Correspondingly, the terminal device receives the random access response from the network device.

[0135] As an example, 2-step random access includes contention-based 2-step random access and non-contention-based 2-step random access.

[0136] Referring to Figure 6, as an example, Figure 6 is a flowchart of a contention-based two-step random access procedure applicable to embodiments of this application. It may include the following steps.

[0137] S610, the terminal device sends message A (msgA) to the network device. Correspondingly, the network device receives msgA from the terminal device. msgA may include a preamble portion and a physical uplink shared channel (PUSCH) portion.

[0138] S620, the network device sends message B (msgB). Correspondingly, the network device receives msgB from the terminal device. Here, msgB can be a contention resolution message; for example, msgB can instruct the terminal device to fall back to the 4-step random access procedure, that is, instruct the terminal device to send msg3.

[0139] As an example, if the terminal device fails to send msgA multiple times, the random access procedure can also fall back to step 4 (RA).

[0140] Referring to Figure 7, as an example, Figure 7 is a flowchart of a non-contention-based two-step random access procedure applicable to embodiments of this application. It may include the following steps.

[0141] In S710, the network device assigns a preamble to the terminal device. Correspondingly, the terminal device receives the preamble assigned by the network device.

[0142] S720, the terminal device sends msgA to the network device. Correspondingly, the network device receives msgA from the terminal device. This msgA may include a preamble portion and a PUSCH portion.

[0143] S730: The network device sends a random access response. Correspondingly, the terminal device receives the random access response from the network device.

[0144] Specifically, in the non-contention-based two-step random access procedure, a dedicated preamble and PUSCH are allocated to the terminal device for msgA transmission, reducing the contention resolution process.

[0145] As an example, the RA resources used for RA, or the set of RA resources, can be determined by at least one of the following: RACH-ConfigGeneric, RACH-ConfigCommon, RACH-ConfigDedicated, RACH-ConfigGenericTwoStepRA, and RACH-ConfigCommonTwoStepRA information elements.

[0146] 2. RA resource partitioning (RACH partitioning):

[0147] As an example, to enable network devices to determine the type of a terminal device based on the preamble or random access channel occasion (RO) sent by the terminal device, RA resources can be further partitioned. Network devices can configure different RA resources for terminal devices based on different features or combinations of features.

[0148] The aforementioned features may include Reduced Capability (RedCap), Enhanced RedCap (eRedCap), Small Data Transmission (SDT), Coverage Enhancement (CovEnh), and Slicing.

[0149] As an example, a network device can associate a set of random access resources (RA) with one or more features. The terminal device can perform RA resource set selection after carrier selection (i.e., selection of normal uplink (NUL) or supplementary uplink (SUL)) and bandwidth part (BWP) selection, and before RA type selection (e.g., selection of 4-step RA or 2-step RA).

[0150] 3. Base station energy saving (Network Energy Saving, NES):

[0151] As an example, one goal of NES is RACH adaptation, where network devices can configure additional RA resources for end devices and dynamically adapt or activate / deactivate the configured additional RA resources. For example, network devices can use DCI to adapt / activate / deactivate the configured additional RA resources.

[0152] As one possible scenario, network devices can configure a long-term Resource Allocation (RO) for terminal devices, which remains active indefinitely. Furthermore, the aforementioned dynamically adjustable / activated / deactivated resources are dynamically activated / deactivated based on DCI (Dynamic Resource Integration), thereby achieving network energy savings.

[0153] As an example, in the RA (Rapid Access) procedure, the terminal device can first perform carrier selection (i.e., NUL / SUL selection), then BWP selection, then RA resource set selection, then RA type selection (i.e., 2-step random access or 4-step random access), and then RA parameter initialization. Then, random access is performed using the selected resource set, i.e., any one of methods 400 to 700 described above is executed. Before the random access procedure is completed, that is, before the terminal device considers the RA procedure to have successfully ended, or before the terminal device considers the RA procedure to have failed, the terminal device will not select any other RA resource set.

[0154] However, in NES scenarios, as a possible scenario, the terminal device may select a dynamically adjustable / activated / deactivated resource for random access. Before the random access process is complete, the network device may deactivate this dynamically adjustable / activated resource. If the terminal device still uses this resource for random access at this time, the network device may stop receiving / transmitting because the resource has been deactivated, leading to transmission / reception failure for the terminal device.

[0155] After a terminal device fails to send / receive, it can reselect a preamble (which can be the same as or different from the preamble sent previously) and send it to the network device. When the terminal device sends the preamble a maximum number of times, it can determine that the entire RA process has failed, or in other words, it can terminate the RA process.

[0156] As an example, if the RA procedure fails, the terminal device can go back to the steps at the beginning of the RA procedure. For example, it can start by performing carrier selection and retry random access. In the process of retrying random access, the terminal device can re-perform RA resource selection.

[0157] Therefore, the process of the terminal device constantly reselecting and sending the preamble to the network device introduces latency into random access. In view of this, this application proposes a solution to address the aforementioned problem.

[0158] The methods provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the scenarios shown in the above figures and are not limited thereto. Furthermore, the terms used below are as explained above and will not be repeated hereafter.

[0159] For ease of description, the first device and the second device will be used as examples for illustrative purposes.

[0160] As an example, the first device may be a terminal device, or it may be a component applied to the terminal device (e.g., a chip, chip system, circuit, communication module, or processor, etc.), or it may be a logic module or software capable of implementing some or all of the functions of the terminal device, etc., which is not limited in this application. The component applied to the terminal device may be within the terminal device or may be independent of the terminal device.

[0161] As an example, the second device may be a network device, or it may be a component applied to the network device (e.g., a chip, chip system, circuit, communication module, or processor, etc.), or it may be a logic module or software capable of implementing some or all of the functions of the network device, etc., which are not limited in this application. The component applied to the network device may be within the network device or may be independent of the network device.

[0162] Furthermore, the steps described below as being performed by a single execution entity can also be divided into being performed by multiple execution entities, which may be logically and / or physically separate.

[0163] Referring to Figure 8, as an example, Figure 8 is a schematic diagram of a communication method 800 provided in an embodiment of this application. The method 800 shown in Figure 8 may include the following steps.

[0164] S810, the first device randomly accesses the second device based on the first resource.

[0165] As an example, the first resource is a dynamically adjustable random access resource. "Dynamically adjustable" can be understood as parameters being dynamically adjusted, or activation / deactivation being dynamically enabled / deactivated. In other words, the first resource can be an R19 random access resource, which can be understood as a random access resource configured by the field `rach-ConfigCommon-r19`, or a field of random access resources introduced by the R19 NES project. This field can, for example, be associated with the `RACH-ConfigCommon` information element, which can also be called `R19 RACH-ConfigCommon`, or `R19 NES RACH-ConfigCommon`. In other words, the first resource can be a random access resource for NES, or a random access resource for RACH adaptation.

[0166] Based on the above description, the first resource may also be referred to as: the first random access resource, or the R19 random access resource, or the dynamic random access resource, or the random access resource that can be activated / deactivated, or the random access resource in an activated / deactivated state, or the random access resource for NES, or the random access resource for RACH adaptation, etc., and its name does not limit the scope of protection of the embodiments of this application.

[0167] The first resource is active. In other words, the first resource is activated for random access; that is, the first device randomly accesses the second device based on the active first resource.

[0168] As an example, S810 can also be replaced by any of the following: the first device randomly accesses the second device using the first resource; or, the first device randomly accesses the second device using the first resource; or, the first device sends a preamble to the second device using the first resource.

[0169] S820, before the first device completes random access to the second device based on the first resource, the first device determines to deactivate the first resource.

[0170] As an example, "before the first device completes random access to the second device based on the first resource" can be understood as: before the first device successfully accesses the second device based on the first resource, or before the first device determines that the process of random access to the second device has successfully ended; or before the first device determines that the process of random access to the second device has been completed. For example, taking a 4-step random access method: in CBRA, before the first device successfully completes contention resolution, or before the first device successfully receives msg4 and the identifier in msg4 is the same as the identifier sent by the first device in msg3. Or, in CFRA, before the first device successfully receives the random access response message, or before the first device successfully receives msg2.

[0171] As an example, the first device determining to deactivate the first resource can be replaced by the first device determining that the first resource is deactivated; or, the first device determining that the state of the first resource is deactivated. The following examples #1 and #2 illustrate two possible ways in which the first device determines to deactivate the first resource.

[0172] Example #1: The first device receives a first message. Accordingly, the second device sends the first message to the first device. The first message indicates that a first resource should be deactivated.

[0173] As an example, the first information can be DCI. In other words, the second device can instruct the first device to activate / deactivate the first resource via DCI.

[0174] As an example, Example #1 can also be understood as follows: the first device can determine to activate the first resource based on the signaling instruction; or, the second device can activate the first resource through the signaling instruction; or, the first resource can be deactivated based on the signaling instruction.

[0175] Example #2, the first timer times out.

[0176] As an example, the first timer can be a timer used to indicate the duration for which the first resource is activated. For example, the first timer can start at time #1 when the first resource is activated and expire after a certain period of time #1. The first timer can also be called a random access resource timer, a random access resource time window, or a random access resource active state timer, etc., and its name does not limit the scope of protection of the embodiments of this application.

[0177] The first timer timeout indicates the deactivation of the first resource. This can be replaced by the first device determining that the first resource is deactivated after the first timer expires; or, the first device determining that the state of the first resource changes from active to deactivated after the first timer expires.

[0178] The following describes two possible implementation scenarios.

[0179] Scenario #1: The first device fails to receive a random access response within the first time window, which is used to indicate the time for waiting for a random access response.

[0180] As an example, the first time window may begin at time #2 when the first device sends msg1 and end some time after time #2. This first time window may also be called a random access response time window, a random access response timer, or ra-ResponseWindow, etc., and its name does not limit the scope of protection of this application embodiment.

[0181] As an example, the end of the first time window indicates that the first device failed to receive msg2. This can be replaced by the first device determining that it failed to receive msg2 after the first time window ends; or, if the first time window has already started and the first device waits for the first time window to time out, then the first device determines that it failed to receive msg2; or, if the first device did not successfully receive RAR during the first time window and the first time window ends, then the first device determines that it failed to receive msg2.

[0182] Scenario #2: The first device fails to receive a random access response before the second timer expires. The second timer is used to indicate the time to wait for information on resolving the random access contention.

[0183] As an example, the second timer can start at time #3 when the first device sends msg3 and expire some time after time #3. This second timer can also be called a contention resolution timer, a contention resolution time window, or a ra-ContentionResolutionTimer, etc., and its name does not limit the scope of protection of the embodiments of this application.

[0184] As an example, the second timer timeout indicates that the first device failed to receive msg4. This can be replaced by the first device determining that it failed to receive msg4 after the second timer expires; or, if the second timer has already started and the first device waits for the second timer to expire, then the first device determines that it failed to receive msg4; or, if the first device does not successfully resolve the contention during the second timer period and the second timer expires, then the first device determines that it failed to receive msg4.

[0185] It can be understood that scenario #1 or scenario #2 can be considered as two possible scenarios in S820 before the first device completes its random access to the second device based on the first resource. That is, scenario #1 or scenario #2 can be superimposed on the condition that the first device has completed its random access to the second device based on the first resource, respectively representing: the scenario where the first device fails to receive msg2 before completing its random access to the second device based on the first resource, and the scenario where the first device fails to receive msg4 before completing its random access to the second device based on the first resource.

[0186] As an example, in scenario #1 or scenario #2 or before the first device completes random access to the second device based on the first resource, method 800 may also include S830.

[0187] S830, the first device executes step #1.

[0188] The following examples, from Example 1 to Example 3, illustrate the steps that step #1 may represent.

[0189] Example 1: The first device determines that random access to the second device has failed. In other words, the process of the first device determining that random access to the second device has failed terminates.

[0190] Specifically, after the first device determines that random access has failed, it can revert to the initial step of randomly accessing the second device, or in other words, it can retry randomly accessing the second device. Conversely, for example, in scenario #1 or scenario #2 above, if the first device still attempts to retransmit the preamble based on the first resource, it will result in a longer latency. Therefore, the implementation in Example 1 terminates the preamble retransmission process early, allowing the first device to use appropriate random access resources to randomly access the second device as soon as possible, thereby reducing the latency of random access.

[0191] Example 2: The first device determines a second resource for random access to the second device. In other words, the first device reverts to the resource set selection step, in which it selects a resource for random access to the second device based on the second resource.

[0192] Furthermore, the first device can randomly access the second device based on the second resource.

[0193] Specifically, the step of the first device returning to the resource set selection not only ends the process of retransmitting the preamble in advance, but also saves the random access step before the resource set selection, further reducing the latency of random access.

[0194] As an example, the second resource is a resource in a resource set that is not associated with any characteristics.

[0195] As an example, a resource set that is not associated with any characteristics may include one or more random access resources that are not associated with any characteristics.

[0196] As an example, a random access resource not associated with any feature can be replaced with any of the following: a public random access resource; or a resource not associated with any feature or feature combination; or a random access resource not associated with any feature or feature combination and not requiring dynamic activation / deactivation; or a random access resource not associated with any feature or feature combination and not used for NES; or a random access resource not associated with any feature or feature combination and not used for RACH adaptation.

[0197] As an example, a resource that is not associated with any characteristics can be a random access resource of R15, or a random access resource configured by R15's RACH-ConfigCommon, or a random access resource configured by the rach-ConfigCommon field (corresponding to the RACH-ConfigCommon information cell) in the BWP-UplinkCommon configuration, or a random access resource in a system message introduced by R15, or a random access resource configured by legacy RACH-ConfigCommon.

[0198] Specifically, resources in a resource set that are not associated with any characteristics will not be deactivated, and the first device can simply connect to the second device based on these resources.

[0199] As another example, the second resource is a resource in a dynamically adjustable resource set, and the second resource is in an active state.

[0200] It is understood that the description of the second resource can be referred to the relevant content of the first resource mentioned above, and will not be repeated in the embodiments of this application.

[0201] Specifically, for resources in a dynamically adjustable resource set, their period can be configured to be shorter than that of resources that are not associated with any characteristics, thus resulting in shorter latency when selecting such resources for random access.

[0202] Example 3: The first device randomly accesses the second device based on a third resource that is not associated with any characteristics. In other words, the first device reverts to the resource set selection step, in which it directly determines to randomly access the second device using the third resource.

[0203] Specifically, the third resource will not be deactivated, so the first device can save the step of resource set selection and directly access the second device randomly based on the third resource, thereby further reducing the latency of random access based on the implementation in Example 2.

[0204] The following describes another possible scenario, in which the first device randomly accesses the second device based on resources that are not associated with any characteristics, and before the random access is completed, there are dynamically adjustable random access resources activated.

[0205] Referring to Figure 9, as an example, Figure 9 is a schematic diagram of a communication method 900 provided in an embodiment of this application. The method 900 shown in Figure 9 may include the following steps.

[0206] S910, the first device randomly connects to the second device based on resource #1, where resource #1 is a resource that is not associated with any characteristics.

[0207] It is understood that the description of resources that are not associated with any characteristics, and the alternative description of the first device randomly accessing the second device based on resources, can be referred to the relevant content in the above method 800, and will not be repeated here in the embodiments of this application.

[0208] S920, before the first device completes random access to the second device based on resource #1, the first device determines to activate resource #2. Resource #2 is a dynamically adjustable random access resource.

[0209] It is understandable that the explanation of dynamically adjustable random access resources can be found in the relevant content of Method 800 above. The explanation of the first device determining to activate resource #2 can be found in the explanation of the first device determining to deactivate the first resource above. Simply replace activation with deactivation.

[0210] S930, the first device executes step #2.

[0211] The following examples, from 4 to 6, illustrate the steps that step #2 may represent.

[0212] Example 4: The first device continues to randomly access the second device based on resource #1. In other words, the first device does not change the random access resource set and completes the process of randomly accessing the second device.

[0213] Example 5: The first device determines resource #3 for random access to the second device. In other words, the first device reverts to the resource set selection step, in which it selects to randomly access the second device based on resource #3.

[0214] It is understood that the description of Example 5 can be referred to the relevant content of Example 2 above, and the embodiments of this application are not limited thereto.

[0215] Example 6: The first device randomly accesses the second device based on resource #2.

[0216] Specifically, once resource #2 is activated, it can be used for random access. The period of this resource can be configured to be shorter than that of resource #1, thus the latency of random access is also shorter when this resource is selected for random access.

[0217] The following section provides further explanation of the allocation of random access resources and introduces another possible scenario.

[0218] As an example, the previous section introduced the partitioning of RA resources, that is, network devices can partition different RA resource sets for different characteristics or combinations of characteristics. Each RA resource set (also called an RA partition) can be configured through RACH-ConfigCommon.

[0219] As an example, in the R15 standard, cell-specific random-access parameters can be configured using RACH-ConfigCommon, while dedicated random-access parameters can be configured using RACH-ConfigDedicated, for example, configuring CFRA resources for terminal devices in a handover scenario.

[0220] As an example, in the R16 standard, due to the introduction of the two-step RA, network devices can broadcast two RA resource sets, RACH-ConfigCommon and RACH-ConfigCommonTwoStepRA.

[0221] As an example, starting with the R17 standard, the random access resource partitioning (RACH partitioning) was further standardized, which introduced up to 256 AdditionalRACH-Config cells in the BWP configuration, in which RACH-ConfigCommon (for 4-step RA) and / or MsgA-ConfigCommon (for 2-step RA) can be configured.

[0222] As an example, the structure of the AdditionalRACH-Config information cell is as follows:

[0223] As an example, taking a 4-step RA approach, each feature or feature combination can be associated with a RACH-ConfigCommon information element, or multiple features or feature combinations can be associated with the same RACH-ConfigCommon. Specifically, the RACH-ConfigConfig contains one or more FeatureCombination information elements, indicating the applicable features or feature combinations.

[0224] As an example, the structure of the RACH-ConfigCommon information cell is as follows:

[0225] The true or false value can be used to indicate whether a feature is associated with RACH-ConfigCommon.

[0226] As an example, the 2-step RA is similar to the 4-step RA, except that the feature or feature combination is associated with RACH-ConfgCommonTwoStepRA instead of RACH-ConfigCommon, which will not be elaborated here.

[0227] As an example, for non-contention-based random access (e.g., handover scenarios where network devices configure CFRA resources via RACH-ConfigDedicated cells), the configuration of RACH-ConfigCommon also needs to be referenced. For instance, if the occasions configuration in the CFRA resources of RACH-ConfigDedicated is not carried, then the random access occasions (RA occasions) should be configured by referring to RACH-ConfigCommon. Furthermore, when selecting a beam in the CFRA procedure (e.g., selecting a synchronization signal block (SS / PBCH block, SSB)), an SSB with signal quality exceeding a certain threshold needs to be selected. This threshold is also configured in the rsrp-ThresholdSSB field of RACH-ConfigCommon.

[0228] Based on the preceding content, random access resources without any associated characteristics can be configured by legacy RACH-ConfigCommon, while dynamically adjustable random access resources can be configured by R19 RACH-ConfigCommon. In this case, for parameters that are absent in R19 RACH-ConfigCommon, the corresponding parameters in legacy RACH-ConfigCommon can be referenced.

[0229] However, for non-contention-based random access, such as when a network device configures CFRA resources via the RACH-ConfigDedicated information cell, the terminal device may not know how to refer to the configuration of RACH-ConfigCommon. In view of this, embodiments of this application propose a solution to address the aforementioned problem.

[0230] Referring to Figure 10, as an example, Figure 10 is a schematic diagram of a communication method 1000 provided in an embodiment of this application. The method 1000 shown in Figure 10 may include the following steps.

[0231] S1010, the first device receives the second information. Accordingly, the second device sends the second information to the first device.

[0232] The second information indicates a fourth resource used for non-contentionable random access. For example, the second information could be RACH-ConfigDedicated as described above.

[0233] The second information does not indicate the content of the first field, which is used to configure the aforementioned non-contention-based random access.

[0234] As an example, the fact that the second information does not indicate the content of the first field can be understood as either the first field not existing in the second information, or the first field existing in the second information but its content being empty.

[0235] As an example, the first field includes at least one of the following:

[0236] 1. The timing field, which indicates the temporal location of the fourth resource. For example, the timing field can be the occasions field mentioned above. In the second information, the content of this field can be empty. The first device can refer to RACH-ConfigCommon to configure the temporal location (i.e., RO) of the fourth resource. Specifically, the first device can refer to the RA occasions in the first RACH-ConfigCommon that activates the uplink portion bandwidth (active UL BWP).

[0237] 2. Threshold field: This threshold field indicates the signal quality threshold for receiving the SSB. For example, the threshold field can be the rsrp-ThresholdSSB field mentioned above. This field may not exist in the second information. The first device can refer to the RACH-ConfigCommon configuration to determine the signal quality threshold for receiving the SSB when RO is selected.

[0238] S1020, the first device receives at least one of the third and fourth information. Accordingly, the second device sends at least one of the third and fourth information to the first device.

[0239] As an example, the third information indicates a fifth resource for random access, which is a dynamically adjustable resource. For details about this resource, please refer to the relevant description above. This application embodiment will not repeat the details here.

[0240] As an example, in conjunction with the preceding content, the third piece of information may include the R19 RACH-ConfigCommon mentioned above.

[0241] As an example, the fourth information indicates a sixth resource for random access, which is not associated with any characteristics. For details about this resource, please refer to the relevant description above. This application embodiment will not repeat the details here.

[0242] As an example, in conjunction with the preceding content, the fourth piece of information may include the legacy RACH-ConfigCommon mentioned above.

[0243] S1030, the first device determines the content of the first field based on the third information or the fourth information.

[0244] The following describes three possible scenarios, namely, the first device receiving the third information, the first device receiving the fourth information, or the first device receiving both the third and fourth information, through scenarios #1 to #3.

[0245] Case #1: The first device receives the third information.

[0246] Specifically, taking R19 RACH-ConfigCommon as the third piece of information, the content of the first field can be referenced from the content of the corresponding field in R19 RACH-ConfigCommon. In other words, parameters that are not configured by the second piece of information in non-contention-based random access can be configured through R19 RACH-ConfigCommon, thereby avoiding configuration failure of non-contention-based random access due to lack of configuration parameters.

[0247] Situation #2: The first device receives the fourth message.

[0248] Specifically, taking the fourth piece of information as legacy RACH-ConfigCommon as an example, the content of the first field can refer to the content of the corresponding field in legacy RACH-ConfigCommon; in other words, parameters that are not configured by the second piece of information in non-contention random access can be configured through legacy RACH-ConfigCommon, thereby avoiding configuration failure of non-contention random access due to lack of configuration parameters.

[0249] Case #3: The first device receives the third and fourth information.

[0250] As one possible implementation, the content of the first field can be referenced from the content of the corresponding field in the fourth information.

[0251] Specifically, the fourth information indicates the random access resource of R15, which will not be deactivated. The fourth information used to configure the resource is also kept transmitted on the communication system, so it is simple to implement by referring to the content of the corresponding field in the fourth information.

[0252] As another possible implementation, case #3 can be further divided into three possible cases: case #3A to case #3C.

[0253] Case #3A: The fifth and sixth resources overlap. In other words, the fifth and sixth resources have an intersection; that is, the intersection of the fifth and sixth resources is not empty.

[0254] As an example, in case #3A, the first device determines the content of the first field based on the fourth information. Taking the fourth information as legacy RACH-ConfigCommon as an example, the content of the first field can refer to the content of the corresponding field in legacy RACH-ConfigCommon; in other words, parameters not configured by the second information in non-contentionable random access can be configured through legacy RACH-ConfigCommon, thereby avoiding configuration failure of non-contentionable random access due to lack of configuration parameters.

[0255] In case #3B, the fifth and sixth resources do not overlap. In other words, the fifth and sixth resources have no intersection, or their intersection is zero. Furthermore, the fifth resource is in a deactivated state, or in other words, the fifth resource is deactivated.

[0256] As an example, in case #3B, the first device determines the content of the first field based on the fourth information. For a detailed explanation, please refer to case #3A; the specific details will not be repeated here.

[0257] Case #3C: The fifth and sixth resources do not overlap, and the fifth resource is in an active state.

[0258] As an example, in scenario #3C, the first device determines the content of the first field based on the third information. Taking R19 RACH-ConfigCommon as an example, the content of the first field can refer to the content of the corresponding field in R19 RACH-ConfigCommon; in other words, parameters not configured by the second information in non-contentionable random access can be configured through R19 RACH-ConfigCommon, thereby avoiding configuration failure in non-contentionable random access due to lack of configuration parameters.

[0259] Based on the above explanation, the first device can determine from which information to reference the configuration under any circumstances, thus avoiding configuration failure due to lack of configuration parameters during non-contention-based random access.

[0260] The following describes a method to prevent non-contention-based random access from failing due to a lack of configuration parameters by restricting network-side configuration.

[0261] As an example, the second information includes the aforementioned timing field, the content of which is not empty. This can be understood as follows: when the second device sends the second information, the second information contains a timing field, and the content of the timing field is not empty. In other words, the first device can directly determine the temporal location of the fourth resource based on the content of the timing field, and therefore does not need to refer to other information.

[0262] As an example, the first field includes the aforementioned threshold field. That is, the first device can determine the content of the threshold field by referring to the third or fourth information; in other words, the signal quality threshold for the first device to receive the SSB in non-contention-based random access can be configured by the third or fourth information.

[0263] As one possible implementation, the third information includes a first threshold field, and the fourth information includes a second threshold field. The contents of the first threshold field and the second threshold field are identical. In other words, when the second device sends the third and fourth information, the contents of the threshold fields in the third and fourth information are the same.

[0264] Furthermore, the first device may determine the content of the threshold field included in the first field based on the first threshold field included in the third information, or based on the second threshold field included in the fourth information.

[0265] Specifically, based on the above implementation, the first device can obtain the same content of the threshold field regardless of whether it refers to the fourth or fifth information. Therefore, from the perspective of restricting network-side configuration, the first device can determine the content of the first field by referring to either the fourth or fifth information, thereby preventing non-contention-based random access from failing due to a lack of configuration parameters.

[0266] Referring to the preceding explanation, in RA resource allocation, further allocation of RA resources allows network devices to determine the type of terminal device through the preamble or RO sent by the terminal device, thereby achieving early identification. In the NES proposed in R19, network devices can configure dynamically adjustable random access resources to terminal devices, thereby achieving energy saving.

[0267] As an example, taking RedCap-enabled terminal devices as an example, in order to achieve early identification, RedCap-enabled terminal devices can perform random access through the random access resources configured in AdditionalRACH-Config, without considering RACH adaptation. In other words, even if R19 RACH-ConfigCommon is included in BWP–UplinkCommon, terminal devices can perform random access without using the random access resources configured in R19 RACH-ConfigCommon.

[0268] However, in the above example, only early identification can be achieved, and RACH adaptation to save energy cannot be implemented.

[0269] The following embodiments of this application propose methods 1100 to 1300, which can achieve both early identification and RACH adaptation by utilizing the resources of R19.

[0270] Referring to Figure 11, as an example, Figure 11 is a schematic diagram of a communication method 1100 provided in an embodiment of this application. The method 1100 shown in Figure 11 may include the following steps.

[0271] S1110, the first device receives the fifth information. Accordingly, the second device sends the fifth information to the first device.

[0272] The fifth information indicates the seventh resource used for random access by the first type of terminal equipment.

[0273] As an example, the first type of terminal device includes terminal devices that support at least one of the following: reduced capability; enhanced reduced capability; small packet data transmission; coverage enhancement; or, slicing.

[0274] It is understood that the above types are merely examples. Any characteristic that can distinguish different terminal devices can be considered a type. For example, the first type may also include whether it supports future communication systems, etc. This application does not limit the types.

[0275] Specifically, if the first device of the first type sends a preamble to the second device through the seventh resource, the second device, upon receiving the preamble, can identify the first device as a terminal device of the first type based on the reception of the preamble, thereby achieving early identification.

[0276] As an example, the seventh resource is a dynamically adjustable resource. For a detailed description of dynamically adjustable resources, please refer to the relevant content above. This application's embodiments will not be repeated here.

[0277] Specifically, for example, the seventh resource can be activated only when the random access load in the communication system is high for random access, and can be deactivated at other times, thereby saving energy consumption of the communication system.

[0278] As an example, taking the first type of terminal device as a terminal device that supports RedCap, the fifth information may include the RACH-ConfigCommon for RedCap in R19, such as the rach-ConfigCommonRedcap-r19 field, associated with the RACH-ConfigCommon information element, or simply referred to as R19 RACH-ConfigCommonRedcap or simply referred to as rach-ConfigCommonRedcap-r19.

[0279] As an example, the resources configured in R19 RACH-ConfigCommonRedcap can be dynamically adjusted, and these resources can be dedicated to end devices that support RedCap.

[0280] Specifically, BWP–UplinkCommon can include the R19 RACH-ConfigCommon and R19 RACH-ConfigCommonRedcap mentioned above. For terminal devices that support RedCap, they can perform random access based on the resources configured in R19 RACH-ConfigCommonRedcap, thereby achieving both early identification and energy saving.

[0281] It is understood that for any possible feature or combination of features, BWP-UplinkCommon can include at least one information element, which is dedicated to configuring dynamically adjustable random access resources for the terminal device of that feature or combination of features. The embodiments of this application will not be described one by one here.

[0282] S1120, the first device performs random access based on the seventh resource. In other words, the first device randomly accesses the second device based on the seventh resource. The meaning and alternative expressions can be found above, and will not be repeated here in the embodiments of this application.

[0283] Referring to Figure 12, as an example, Figure 12 is a schematic diagram of a communication method 1200 provided in an embodiment of this application. The method 1200 shown in Figure 12 may include the following steps.

[0284] S1210, the first device receives the sixth information. Accordingly, the second device sends the sixth information to the first device.

[0285] The sixth information indicates the eighth resource used for random access. The eighth resource is a dynamically adjustable resource. For a detailed description of this resource, please refer to the preceding text. The embodiments of this application will not be repeated here.

[0286] As an example, the sixth piece of information may include R19 RACH-ConfigCommon.

[0287] S1220, the first device determines the eighth resource based on the sub-information in the sixth information for random access by the aforementioned first type of terminal device.

[0288] As an example, the sub-information in the sixth information may include FeatureCombination. For an explanation of FeatureCombination, please refer to the examples above.

[0289] Specifically, BWP–UplinkCommon may include the R19 RACH-ConfigCommon mentioned above. The R19 RACH-ConfigCommon may include FeatureCombination, which can indicate the features or feature combinations associated with the resources configured by R19 RACH-ConfigCommon, thereby enabling both early identification and energy saving.

[0290] As an example, after S1210, S1231 and S1232 can also be used to achieve both early identification and energy saving.

[0291] S1231, the first device receives the seventh information. Accordingly, the second device sends the seventh information to the first device.

[0292] The seventh information indicates the first set, which includes a preamble for random access by a first type of terminal device.

[0293] S1232, the first device transmits a first preamble via the eighth resource. Correspondingly, the second device receives the first preamble from the first device via the eighth resource. This first preamble belongs to the first set.

[0294] Specifically, BWP-UplinkCommon can include the R19 RACH-ConfigCommon mentioned above. Furthermore, the second device can configure a preamble specifically for random access by the first device for the first type of terminal device. Upon receiving this preamble, the second device can identify the first device as the first type of terminal device based on it. Therefore, the first type of terminal device can be identified early by network devices during random access, and can also utilize dynamically adjustable random access resources to save energy.

[0295] Referring to Figure 13, as an example, Figure 13 is a schematic diagram of a communication method 1300 provided in an embodiment of this application. The method 1300 shown in Figure 13 may include the following steps.

[0296] S1310, the first device receives the eighth information. Accordingly, the second device sends the eighth information to the first device.

[0297] The eighth information indicates the ninth resource for random access by first-type terminal devices. In other words, the ninth resource is configured exclusively for random access by first-type terminal devices; that is, if the network device receives the preamble through the ninth resource, the network device can determine that the terminal device sending the preamble is a first-type terminal device.

[0298] As an example, the eighth information may include AdditionalRACH-Config-r17, the specific structure of which has been illustrated above and will not be repeated here in the embodiments of this application.

[0299] The eighth information includes a second field, which indicates that the ninth resource is a dynamically adjustable resource. For a detailed explanation of dynamically adjustable resources, please refer to the preceding text. This application embodiment will not repeat the details here.

[0300] As an example, the second field may include the RACH-ConfigCommon for NES in R19, such as the rach-ConfigCommonNES-r19 field, associated with the RACH-ConfigCommon information element, or simply referred to as R19 RACH-ConfigCommonNES or rach-ConfigCommonNES-r19.

[0301] As an example, the information cell structure of AdditionalRACH-Config-r17, including R19 RACH-ConfigCommonNES, is as follows:

[0302] Specifically, the ninth resource indicated by the eighth information is a resource dedicated to random access by first-type terminal devices, thereby enabling early identification. Furthermore, the eighth information includes a second field indicating that the ninth resource is a dynamically adjustable resource, allowing first-type terminal devices to utilize dynamically adjustable random access resources to save energy.

[0303] S1320, the first device performs random access based on the ninth resource. In other words, the first device randomly accesses the second device based on the ninth resource. The meaning and alternative expressions can be found above, and will not be repeated here in the embodiments of this application.

[0304] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 8 to 13. The apparatus provided by the embodiments of this application will be described in detail below with reference to Figures 14 to 16. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0305] Referring to Figure 14, which is a schematic diagram of a communication device 1400 provided in an embodiment of this application, the communication device 1400 includes a transceiver unit 1410 and a processing unit 1420. The transceiver unit 1410 can be used to implement corresponding communication functions. The transceiver unit 1410 can also be referred to as a communication interface or a communication unit. The processing unit 1420 can be used to perform processing, such as determining information bits.

[0306] Optionally, the device 1400 may further include a storage unit for storing instructions and / or data, and the processing unit 1420 may read the instructions and / or data from the storage unit to enable the device to implement the aforementioned method embodiments.

[0307] In a first possible design, the device 1400 can be the first device in the foregoing embodiments, which can implement the steps or processes corresponding to those performed by the first device in the above method embodiments. Specifically, the transceiver unit 1410 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) of the first device in the above method embodiments, and the processing unit 1420 can be used to perform processing-related operations of the first device in the above method embodiments, or operations other than transceiver (such as operations other than sending and / or receiving data or messages).

[0308] In a second possible design, the device 1400 can be the second device in the foregoing embodiments, which can implement the steps or processes corresponding to those performed by the second device in the above method embodiments. Specifically, the transceiver unit 1410 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) of the second device in the above method embodiments, and the processing unit 1420 can be used to perform processing-related operations of the second device in the above method embodiments, or operations other than transceiver (such as operations other than sending and / or receiving data or messages).

[0309] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0310] It should also be understood that the device 1400 here is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the device 1400 can be specifically the communication device in the above embodiments, and can be used to execute the various processes and / or steps corresponding to the communication device in the above method embodiments; to avoid repetition, these will not be described again here.

[0311] The apparatus 1400 of each of the above-described schemes has the function of implementing the corresponding steps performed by the communication device (such as the first device, or the second device) in the above-described methods. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (e.g., the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by processors, each performing the transceiver operations and related processing operations in the respective method embodiments.

[0312] In addition, the transceiver unit 1410 may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

[0313] It should be noted that the device in Figure 14 can be the communication device in the foregoing embodiments (such as the first device or the second device), or it can be a chip or a chip system, such as a system on a chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. No limitations are imposed here.

[0314] Referring to Figure 15, as an example, Figure 15 is a schematic diagram of another communication device 1500 provided in an embodiment of this application. The device 1500 includes a processor 1510, which is coupled to a memory 1520. The memory 1520 is used to store computer programs or instructions and / or data. The processor 1510 is used to execute the computer programs or instructions stored in the memory 1520, or to read the data stored in the memory 1520, in order to execute the methods in the above method embodiments.

[0315] Optionally, there may be one or more processors 1510.

[0316] Optionally, the memory 1520 may be one or more.

[0317] Alternatively, the memory 1520 can be integrated with the processor 1510, or it can be set separately.

[0318] Optionally, as shown in FIG15, the device 1500 further includes a transceiver 1530 for receiving and / or transmitting signals. For example, a processor 1510 is used to control the transceiver 1530 to receive and / or transmit signals.

[0319] As an example, processor 1510 may have the functions of processing unit 1420 shown in FIG14, memory 1520 may have the functions of storage unit, and transceiver 1530 may have the functions of transceiver unit 1410 shown in FIG14.

[0320] As one option, the device 1500 is used to implement the operations performed by the communication device (such as the first device, or the second device) in the various method embodiments described above.

[0321] For example, processor 1510 is used to execute computer programs or instructions stored in memory 1520 to implement the relevant operations of the communication device in the various method embodiments described above.

[0322] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or 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. A general-purpose processor can be a microprocessor or any conventional processor.

[0323] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be cache or random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0324] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0325] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0326] Referring to Figure 16, as an example, Figure 16 is a schematic diagram of a chip system 1600 provided in an embodiment of this application. The chip system 1600 (or may also be referred to as a processing system) includes logic circuitry 1610 and an input / output interface 1620.

[0327] The logic circuit 1610 can be a processing circuit in the chip system 1600. The logic circuit 1610 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 1600 to implement the methods and functions of the embodiments of this application. The input / output interface 1620 can be an input / output circuit in the chip system 1600, outputting processed information from the chip system 1600, or inputting data or signaling information to be processed into the chip system 1600 for processing.

[0328] As one approach, the chip system 1600 is used to implement operations performed by a communication device (such as the first device, or the second device) in the various method embodiments described above.

[0329] For example, logic circuit 1610 is used to implement processing-related operations performed by a communication device (such as the first device or the second device) in the above method embodiments; input / output interface 1620 is used to implement sending and / or receiving-related operations performed by a communication device (such as the first device or the second device) in the above method embodiments.

[0330] This application also provides a computer-readable storage medium storing a computer program or instructions for implementing the methods executed by a communication device (such as a first device or a second device) in the above-described method embodiments. For example, when the computer program or instructions are run on the communication device, the communication device (such as the first device or the second device) executes the above-described methods (such as any one of methods 800 to 1300).

[0331] This application also provides a computer program product comprising instructions that, when executed by a computer, implement the methods described above as performed by a communication device (such as a first device or a second device). For example, when the computer program or instructions are run on the communication device, the communication device (such as the first device or the second device) performs the methods described above (such as any one of methods 800 to 1300).

[0332] This application also provides a communication system that includes the first device and / or the second device in the embodiments described above. For example, the system includes the first device and the second device in any of the embodiments shown in Figures 8 to 13.

[0333] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0334] In the several embodiments provided in this application, it should be understood that the disclosed apparatus 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 mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0335] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as 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. For example, the computer can be a personal computer, a server, or a second device, etc. 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 accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs). For example, the aforementioned available media include, but are not limited to, USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, and other media capable of storing program code.

[0336] 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, Applied to a first device, the method includes: The second device is randomly accessed based on the first resource, where the first resource is in an active state; Before the random access to the second device based on the first resource is completed, it is determined to deactivate the first resource; The system determines that the random access to the second device has failed, or determines a second resource for random access to the second device, or randomly accesses the second device based on a third resource that is not associated with any characteristics.

2. The method according to claim 1, characterized in that, The step of determining to deactivate the first resource includes: Receive first information, which instructs you to activate the first resource; or... The first timer times out, and the first timer timeout indicates that the first resource should be activated.

3. A communication method, characterized in that, include: The first device randomly accesses the second device based on a first resource, where the first resource is in an active state; Before the second device completes the random access based on the first resource, the second device sends a first message, which instructs to activate the first resource. The first device receives the first information; The first device determines that the random access to the second device has failed, or determines a second resource for random access to the second device, or randomly accesses the second device based on a third resource that is not associated with any characteristics.

4. The method according to any one of claims 1 to 3, characterized in that, The second resource is a resource in a resource set that is not associated with any characteristics, or the second resource is a resource in a resource set that can be dynamically adjusted, and the second resource is in an active state.

5. The method according to any one of claims 1 to 4, characterized in that, Also includes: If a random access response is not successfully received within the first time window, the first time window is used to indicate the time to wait for a random access response. or, If a random access response is not successfully received before the second timer expires, the second timer is used to indicate the time to wait for information on resolving the random access contention.

6. A communication method, characterized in that, include: Receive second information, the second information indicating a fourth resource, the fourth resource being used for non-contention-based random access, the second information not indicating the content of a first field, the first field being used to configure the non-contention-based random access; Receive at least one of a third message and a fourth message, wherein the third message indicates a fifth resource for random access, the fifth resource being a dynamically adjustable resource, and the fourth message indicates a sixth resource for random access, the sixth resource being unassociated with any characteristics; The content of the first field is determined based on the third or fourth information.

7. A communication method, characterized in that, include: The second device sends a second message indicating a fourth resource for non-contention-based random access. The second message does not indicate the content of a first field, which is used to configure the non-contention-based random access. The second device sends at least one of a third message and a fourth message, wherein the third message indicates a fifth resource for random access, the fifth resource being a dynamically adjustable resource, and the fourth message indicates a sixth resource for random access, the sixth resource being unassociated with any characteristics. The first device receives the second information; The first device receives at least one of the third and fourth information; The first device determines the content of the first field based on the third information or the fourth information.

8. The method according to claim 6 or 7, characterized in that, The first field includes at least one of the following: A timing field, wherein the timing field is used to indicate the time-domain location of the fourth resource; or, A threshold field, which is used to indicate the signal quality threshold for receiving synchronization signal blocks.

9. The method according to any one of claims 6 to 8, characterized in that, When the fifth resource and the sixth resource overlap, or when the fifth resource and the sixth resource do not overlap and the fifth resource is in an inactive state, determining the content of the first field based on the third information or the fourth information includes: determining the content of the first field based on the fourth information; or, When the fifth resource and the sixth resource do not overlap, and the state of the fifth resource is active, determining the content of the first field based on the third information or the fourth information includes: determining the content of the first field based on the third information.

10. The method according to any one of claims 6 to 9, characterized in that, The second information includes a timing field, and the first field includes a threshold field. The timing field is used to indicate the temporal location of the fourth resource, and the content of the timing field is not empty; and, The third information includes a first threshold field, and the fourth information includes a second threshold field. The threshold field is used to indicate the signal quality threshold of the received synchronization signal block. The contents of the first threshold field and the second threshold field are the same. Determining the content of the first field based on the third information or the fourth information includes: Based on the first threshold field included in the third information, the content of the first field is determined to be the content of the first threshold field; or, Based on the second threshold field included in the fourth information, the content of the first field is determined to be the content of the second threshold field.

11. A communication method, characterized in that, The method includes: The system receives fifth information, which indicates a seventh resource for random access by a first type of terminal device, the seventh resource being a dynamically adjustable resource; wherein the first type of terminal device includes terminal devices supporting at least one of the following: capability reduction; enhanced capability reduction; small packet data transmission; coverage enhancement; or, slicing; Random access is performed based on the seventh resource.

12. A communication method, characterized in that, The method includes: Send a fifth message, the fifth message indicating a seventh resource for random access by a first type of terminal device, the seventh resource being a dynamically adjustable resource; wherein, the first type of terminal device includes terminal devices supporting at least one of the following: capability reduction; enhanced capability reduction; small packet data transmission; coverage enhancement; or, slicing; Random access is performed based on the seventh resource.

13. The method according to claim 11 or 12, characterized in that, The first type of terminal device is a terminal device that supports Redcap with reduced capabilities, and the fifth information includes R19's RACH-ConfigCommon for Redcap.

14. A communication method, characterized in that, The method includes: Receive sixth information, the sixth information indicating an eighth resource for random access, the eighth resource being a dynamically adjustable resource; Based on the sub-information in the sixth information, the eighth resource is determined to be used for random access by a first type of terminal device; or... Receive a seventh message, the seventh message indicating a first set, the first set including a preamble for random access by a first type of terminal device; The first preamble is sent through the eighth resource, and the first preamble belongs to the first set; The terminal device of the first type includes a terminal device that supports at least one of the following: reduced capability; enhanced reduced capability; small packet data transmission; coverage enhancement; or, slicing.

15. A communication method, characterized in that, The method includes: Send a sixth message, the sixth message indicating an eighth resource for random access, the eighth resource being a dynamically adjustable resource; Send a seventh message, the seventh message indicating a first set, the first set including a preamble for random access by a first type of terminal device; The first preamble is received through the eighth resource, the first preamble belonging to the first set; wherein, the terminal device of the first type includes a terminal device supporting at least one of the following: capability reduction; enhanced capability reduction; small packet data transmission; coverage enhancement; or, slicing.

16. The method according to claim 14 or 15, characterized in that, The sixth piece of information includes R19 RACH-ConfigCommon.

17. The method according to any one of claims 14 to 16, characterized in that, The sub-information in the sixth information includes FeatureCombination.

18. A communication method, characterized in that, The method includes: Receive eighth information, the eighth information indicating a ninth resource for random access by a first type of terminal device; wherein, the first type of terminal device includes a terminal device supporting at least one of the following: capability reduction; enhanced capability reduction; small packet data transmission; coverage enhancement; or, slicing; the eighth information includes a second field, the second field indicating that the ninth resource is a dynamically adjustable resource; Random access is performed based on the ninth resource.

19. A communication method, characterized in that, The method includes: Send an eighth message, the eighth message indicating a ninth resource for random access by a first type of terminal device; wherein the first type of terminal device includes a terminal device that supports at least one of the following: capability reduction; enhanced capability reduction; small packet data transmission; coverage enhancement; or, slicing; the eighth message includes a second field, the second field indicating that the ninth resource is a dynamically adjustable resource; Random access is performed based on the ninth resource.

20. The method according to claim 18 or 19, characterized in that, The eighth piece of information includes AdditionalRACH-Config-r17.

21. The method according to any one of claims 18 to 20, characterized in that, The second field includes R19's RACH-ConfigCommon for NES.

22. A communication device, characterized in that, Includes modules or units for performing the method according to any one of claims 1 to 21.

23. A communication device, characterized in that, Includes a processor for executing computer programs or instructions to cause the apparatus to perform the method of any one of claims 1 to 21.

24. The apparatus according to claim 23, characterized in that, The device also includes a memory and / or a communication interface. The memory, coupled to the processor, is used to store the computer program or instructions; The communication interface is coupled to the processor and is used for inputting and / or outputting information.

25. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, cause the communication device to perform the method as described in any one of claims 1 to 21.

26. A computer program product, characterized in that, The computer program product includes a computer program or instructions for performing the method as described in any one of claims 1 to 21.

Images