Method and device for determining trigger conditions, and method and device for configuring resource partitions

Abstract

The present disclosure relates to a method and device for determining a trigger condition, and a method and device for configuring a resource partition. The method for determining the trigger condition includes the steps of determining a feature for triggering random access, selecting a random access channel RACH resource, and determining whether the selected RACH resource supports the feature, determining that the trigger condition of the feature is satisfied in response to the selected RACH resource supporting the feature, and determining that the trigger condition of the feature is not satisfied in response to the selected RACH resource not supporting the feature. According to the present disclosure, it is possible to determine whether the trigger condition of the feature is satisfied based on whether the selected RACH resource supports the feature, which is useful for determining a specific RACH resource supporting the feature from the specific RACH resource of the feature combination when a specific RACH resource of a feature combination is configured for a terminal by a network side, and further, by initiating random access by a specific RACH resource supporting the feature, the network side can determine a feature of the terminal for triggering random access as early as possible.

Description

[Technical Field]

[0001] The present disclosure relates to the field of communication technologies, and in particular to a method for determining a trigger condition, a method for configuring a resource partition, a device for determining a trigger condition, a device for configuring a resource partition, a communication device, and a computer-readable storage medium. [Background technology]

[0002] The network side can configure a specific random access resource for each feature, so that the network side can identify the corresponding feature as early as possible based on the specific random access resource used by the terminal for random access.

[0003] For example, for a feature called CE (Coverage Enhancement), the network side can configure a specific random access resource, such as a CE-specific Random Access Channel (RACH) resource, for the feature called CE. Then, when random access is triggered by the CE feature, the terminal can perform random access using the CE-specific RACH resource. Thus, the network side can determine that the corresponding feature is CE based on the CE-specific RACH resource used by the terminal for random access, and can appropriately configure the terminal according to the CE feature. Summary of the Invention [Problem to be solved by the invention]

[0004] In view of this, the embodiments of the present disclosure propose a method for determining a trigger condition, a method for configuring a resource partition, a device for determining a trigger condition, a device for configuring a resource partition, a communication device, and a computer-readable storage medium to solve the technical problems in the related art. [Means for solving the problem]

[0005] According to a first aspect of an embodiment of the present disclosure, there is proposed a method for determining a trigger condition, the method being executed by a terminal, the method including: determining a feature that triggers random access; selecting a random access channel (RACH) resource partition and determining whether the selected RACH resource supports the feature; determining that the trigger condition of the feature is met in response to the selected RACH resource supporting the feature; and determining that the trigger condition of the feature is not met in response to the selected RACH resource not supporting the feature.

[0006] According to a second aspect of an embodiment of the present disclosure, a resource partition configuration method is proposed, which is executed by a network-side device, comprising the steps of configuring a random access channel (RACH) resource partition for a terminal, thereby causing the terminal to select a RACH resource partition from configured RACH resource partitions and determine whether the selected RACH resource supports a feature that triggers random access, wherein in response to the selected RACH resource supporting the feature, the terminal determines that a trigger condition of the feature is met, and in response to the selected RACH resource not supporting the feature, the terminal determines that the trigger condition of the feature is not met.

[0007] According to a third aspect of an embodiment of the present disclosure, there is proposed a trigger condition determination device applied to a terminal, the trigger condition determination device including a processing module that determines a feature that triggers random access, selects a random access channel (RACH) resource partition, determines whether the selected RACH resource supports the feature, and determines that the trigger condition of the feature is met in response to the selected RACH resource supporting the feature, and determines that the trigger condition of the feature is not met in response to the selected RACH resource not supporting the feature.

[0008] According to a fourth aspect of an embodiment of the present disclosure, there is proposed a resource partition configuration device to be applied to a network-side device, the resource partition configuration device including: a transmission module configured to configure a random access channel (RACH) resource partition for a terminal, thereby causing the terminal to select a RACH resource partition from the configured RACH resource partitions and determine whether the selected RACH resource supports a feature that triggers random access, wherein in response to the selected RACH resource supporting the feature, the terminal determines that a trigger condition of the feature is met, and in response to the selected RACH resource not supporting the feature, the terminal determines that the trigger condition of the feature is not met.

[0009] According to a fifth aspect of an embodiment of the present disclosure, there is proposed a communication device including a processor and a memory for storing a computer program, wherein when the computer program is executed by the processor, the above-mentioned method for determining a trigger condition is realized.

[0010] According to a sixth aspect of an embodiment of the present disclosure, there is proposed a communication device including a processor and a memory for storing a computer program, wherein when the computer program is executed by the processor, the above-mentioned resource partition configuration method is realized.

[0011] According to a seventh aspect of an embodiment of the present disclosure, there is provided a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, achieves the steps of the above-described method for determining a trigger condition.

[0012] According to an eighth aspect of an embodiment of the present disclosure, there is provided a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, achieves the steps in the above-mentioned resource partition configuration method.

[0013] According to an embodiment of the present disclosure, after determining a feature for triggering random access, the terminal may select a random access channel (RACH) resource and determine whether the selected RACH resource supports the feature. If the terminal determines that the selected RACH resource supports the feature, the terminal may determine that the trigger condition of the feature is met. If the terminal determines that the selected RACH resource does not support the feature, the terminal may determine that the trigger condition of the feature is not met.

[0014] This allows determining whether the trigger condition of the feature is met based on whether the selected RACH resource supports the feature. This is useful when a specific RACH resource of a feature combination is configured for the terminal by the network side, as it can determine a specific RACH resource that supports the feature from the specific RACH resource of the feature combination. Furthermore, by initiating random access using a specific RACH resource that supports the feature, the network side can determine the feature of the terminal that triggers random access as early as possible. [Brief explanation of the drawings]

[0015] In order to more clearly describe the technical solutions in the embodiments of the present application, the drawings that need to be used in the description of the embodiments are briefly described below, but it should be clear that the drawings in the following description are only some embodiments of the present application, and those skilled in the art can obtain other drawings based on these drawings without any creative efforts. [Figure 1] 1 is a schematic flowchart of a method for determining a trigger condition according to an embodiment of the present disclosure. [Figure 2] 10 is a schematic flowchart of another method for determining a trigger condition according to an embodiment of the present disclosure. [Figure 3] 10 is a schematic flowchart of yet another method for determining a trigger condition according to an embodiment of the present disclosure. [Figure 4] 1 is a schematic flowchart of a resource partition configuration method according to an embodiment of the present disclosure; [Figure 5] 1 is a schematic block diagram of a trigger condition determination device according to an embodiment of the present disclosure; [Figure 6] 1 is a schematic block diagram of a resource partition configuration device according to an embodiment of the present disclosure. [Figure 7] FIG. 1 is a schematic block diagram of an apparatus for configuring resource partitions according to an embodiment of the present disclosure. [Figure 8] FIG. 1 is a schematic block diagram of an apparatus for determining a trigger condition according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0016] The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings of the embodiments of the present disclosure. It is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and are not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative efforts fall within the scope of protection of the present disclosure.

[0017] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It should also be understood that the term "and / or," as used herein, refers to and includes any and all possible combinations of one or more of the associated listed items.

[0018] In the embodiments of the present disclosure, terms such as first, second, and third may be used to describe various pieces of information, but it should be understood that such information should not be limited to these terms. These terms are used only to distinguish between the same types of information. For example, first information may be referred to as second information without departing from the scope of the present disclosure. Similarly, second information may be referred to as first information. Depending on the context, for example, the word "upon..." used in this specification may be interpreted as "if..." or "when..." or "depending on the decision."

[0019] For simplicity and ease of understanding, this specification uses the terms "greater than," "smaller than," "higher than," or "lower" to express magnitude relationships. However, those skilled in the art will understand that the term "greater than" also means "greater than or equal to," the term "smaller than" also means "less than or equal to," the term "higher than" also means "more than or equal to," and the term "lower" also means "less than or equal to."

[0020] 1 is a schematic flowchart of a method for determining a trigger condition according to an embodiment of the present disclosure. The method for determining a trigger condition according to this embodiment can be executed by a terminal, and the terminal includes, but is not limited to, communication devices such as mobile phones, tablet computers, wearable devices, sensors, and Internet of Things devices. The terminal can communicate with a network side device, and the network side device includes, but is not limited to, a base station, a core network, and other network side devices (also simply referred to as the network side) in communication systems such as 4G, 5G, and 6G.

[0021] As shown in FIG. 1, the method for determining the trigger condition can include the following steps S101 to S103.

[0022] In step S101, a feature that triggers random access is determined.

[0023] In step S102, select a random access channel (RACH) resource, and determine whether the selected RACH resource supports the feature.

[0024] In step S103, in response to the selected RACH resource supporting the feature, it is determined that a trigger condition of the feature is met, and in response to the selected RACH resource not supporting the feature, it is determined that the trigger condition of the feature is not met.

[0025] In addition, the resources according to all embodiments of the present disclosure may be the entire resources (e.g., one frequency band, one channel) or a resource partition (e.g., some frequency domain resources in one frequency band, some frequency domain resources in one channel).

[0026] In one embodiment, the network side can configure a unique random access resource for the terminal, and configure a corresponding unique random access resource for each feature.

[0027] For example, a CE specific RACH resource is configured for the CE feature, and a Redcap (Reduced Capability) feature is configured for the Redcap specific RACH resource. In this way, if the feature of the terminal that triggers random access is CE, the CE specific RACH resource can be directly selected to start random access. If the feature that triggers random access is Redcap, the Redcap specific RACH resource can be directly selected to start random access.

[0028] In one embodiment, the unique random access resource configured for the terminal by the network side may be a unique random access resource configured for a feature combination.

[0029] For example, the specific RACH resource configured for the terminal by the network side includes two feature combination specific RACH resources, which are a specific RACH resource of SDT (Small Data Transmission) + Redcap and a specific RACH resource of CE + Redcap. At the same time, the network side can also configure a non-specific RACH resource, such as a legacy RACH resource.

[0030] Here, the feature of the terminal that triggers random access may be a single feature or a combination of features, including any feature that requires RACH resources.

[0031] When the terminal triggers random access, if it is a non-feature random access, it can select a legacy RACH resource to start the random access. If it is a feature random access, it can determine the feature that triggers the random access, for example, feature A.

[0032] Furthermore, if a feature-specific RACH resource is not configured for the terminal by the network side, the terminal may select a legacy RACH resource to initiate random access. If a feature-specific RACH resource (a specific RACH resource of any one feature, not limited to a specific RACH resource of feature A) is configured for the terminal by the network side device, the terminal may preferentially consider the feature-specific RACH resource. If there is no selectable specific RACH resource of the feature, the terminal may select a legacy RACH resource to initiate random access.

[0033] Here, the selection of a specific RACH resource of a feature by a terminal includes, but is not limited to, the following process:

[0034] The terminal determines whether there is a specific RACH resource whose corresponding feature is included in feature A (i.e., as a subset of feature A) among the specific RACH resources of the feature configured for the terminal by the network side. If there is, the terminal can select the specific RACH resource of the feature; if there is not, the terminal selects a legacy RACH resource to initiate random access.

[0035] For example, the feature of the terminal that triggers random access is SDT, and the specific RACH resources of the feature configured for the terminal by the network side include a specific RACH resource of SDT+Redcap and a specific RACH resource of CE+Redcap. Here, since SDT+Redcap is not included in SDT and CE+Redcap is not included in SDT (i.e., SDT+Redcap or CE+Redcap are not subsets of SDT), the terminal selects a legacy RACH resource to initiate random access.

[0036] In one embodiment, the RACH resource includes a unique RACH resource of a feature combination, the feature combination including at least two features.

[0037] In one embodiment, the selected RACH resource supporting the feature comprises: The feature combination corresponding to the RACH resource includes the feature that triggers random access.

[0038] In the above case, for the specific RACH resource of SDT+Redcap, since SDT+Redcap includes SDT, the specific RACH resource of SDT+Redcap can actually support the feature SDT. After the terminal initiates random access using the specific RACH resource of SDT+Redcap, the network side can appropriately configure the terminal based on the random access resource used by the terminal (i.e., the specific RACH resource of SDT+Redcap). However, since the terminal does not initiate random access using the specific RACH resource of SDT+Redcap but instead initiates random access using the legacy RACH resource, the network side cannot determine the terminal feature that triggers random access as early as possible.

[0039] Note that if the feature of the terminal that triggers random access is a feature combination of SDT+CE+Redcap, SDT+Redcap is included in SDT+CE+Redcap, and CE+Redcap is also included in SDT+CE+Redcap (i.e., SDT+Redcap or CE+Redcap are each a subset of SDT+CE+Redcap), so the terminal can select a specific RACH resource of SDT+Redcap or a specific RACH resource of CE+Redcap. Whether to select a specific RACH resource of SDT+Redcap or a specific RACH resource of CE+Redcap can be determined based on the priority of the features. For example, the selection basis can include preferentially satisfying the selection result of a feature with a higher priority. For example, if the feature priority is Redcap > CE > SDT, the specific RACH resource of CE+Redcap can be selected.

[0040] According to an embodiment of the present disclosure, after determining a feature for triggering random access, the terminal may select a random access channel (RACH) resource and determine whether the selected RACH resource supports the feature. If the terminal determines that the selected RACH resource supports the feature, the terminal may determine that the trigger condition of the feature is met. If the terminal determines that the selected RACH resource does not support the feature, the terminal may determine that the trigger condition of the feature is not met.

[0041] This allows determining whether the trigger condition of the feature is met based on whether the selected RACH resource supports the feature. This is useful when a specific RACH resource of a feature combination is configured for the terminal by the network side, as it can determine a specific RACH resource that supports the feature from the specific RACH resource of the feature combination. Furthermore, by initiating random access using a specific RACH resource that supports the feature, the network side can determine the feature of the terminal that triggers random access as early as possible.

[0042] Additionally, when a specific RACH resource supporting the feature is determined, subsequent operations to be performed may include, but are not limited to, initiating random access using the specific RACH resource supporting the feature, and other operations may be performed, as will be described in the following embodiments.

[0043] In one embodiment, the feature is: Capacity reduction (Redcap), Coverage Extension (CE), Radio Access Network (RAN) slicing, and Small Data Transmission (SDT).

[0044] 2 is a schematic flowchart of another method for determining a trigger condition according to an embodiment of the present disclosure. As shown in FIG. 2, the method further includes step 201.

[0045] In step S201, whether the trigger condition of the feature is satisfied is indicated to an upper layer via a media access control (MAC) layer to assist the upper layer in determining whether to trigger the feature, where the feature includes at least a small data transmission (SDT).

[0046] In one embodiment, for the first feature, for example, the trigger of the first feature is determined by the MAC layer, and the terminal can directly use the selected RACH resource to initiate random access after determining that the selected RACH resource supports the first feature and that the trigger condition of the first feature is satisfied. The first feature includes, but is not limited to, Redcap, CE, and RAN slicing.

[0047] On the other hand, for the second feature, for example, the triggering of the second feature may be determined by a higher layer (e.g., a Radio Resource Control (RRC) layer), and after the terminal determines that the selected RACH resource supports the second feature and determines that the triggering condition of the second feature is met, the terminal may perform an operation of instructing the higher layer via the MAC layer whether the triggering condition of the second feature is met, to assist the higher layer in determining whether to trigger the feature. The second feature may include, but is not limited to, an SDT.

[0048] For example, if the higher layer determines, as instructed by the MAC layer, that the SDT trigger condition is met, it may take other factors into account when deciding whether to initiate random access using the selected RACH resource.

[0049] 3 is a schematic flowchart of another method for determining a trigger condition according to an embodiment of the present disclosure. As shown in FIG. 3, the method further includes the following steps:

[0050] In step S301, it is determined whether the RACH resource specific to the feature is set on the network side.

[0051] In step S302, in response to the specific RACH resource of the feature not being configured, it is determined that the trigger condition of the feature is not satisfied.

[0052] Here, the step of selecting a RACH resource and determining whether the selected RACH resource supports the feature includes step S303. In step S303, in response to the specific RACH resource of the feature being configured, select a random access channel RACH resource, and determine whether the selected RACH resource supports the feature.

[0053] In one embodiment, before selecting a random access channel (RACH) resource, the terminal may first determine whether a specific RACH resource specific to the feature is configured on the network side, where the specific RACH resource of the feature refers to a feature corresponding to the specific RACH resource and includes the feature that triggers random access.

[0054] For example, if the feature that triggers random access is SDT, and the specific RACH resource configured for the terminal by the network side includes only the specific RACH resource of SDT+Redcap, since SDT+Redcap includes SDT, it can be determined that the specific RACH resource of the feature that triggers random access is configured on the network side.

[0055] For example, if the feature that triggers random access is SDT, and the specific RACH resource configured for the terminal by the network side only includes the specific RACH resource of CE+Redcap, it can be determined that the specific RACH resource of the feature that triggers random access is not configured on the network side because CE+Redcap does not include SDT.

[0056] Here, if it is determined that a specific RACH resource for the feature is not configured on the network side, it can be determined that the trigger condition for the feature is not satisfied. In this case, no matter how the terminal selects a RACH resource, it cannot select a RACH resource that supports the feature. Therefore, it is not necessary to select a random access channel RACH resource and determine whether the selected RACH resource supports the feature, and unnecessary operations can be avoided.

[0057] On the other hand, if it is determined that a specific RACH resource for the feature has been configured by the network side device, it can determine that the trigger condition for the feature is met, and then select a random access channel RACH resource and determine whether the selected RACH resource supports the feature.

[0058] In one embodiment, the method comprises: determining, in response to the selected RACH resource supporting the feature, that a type of the ultimately initiated random access is a feature random access (feature RACH); In response to the selected RACH resource not supporting the feature, determining that the type of the ultimately initiated random access is a non-feature random access (non-feature RACH).

[0059] In the above embodiment, determining whether the trigger condition of the feature is satisfied based on whether the selected RACH resource supports the feature is merely one of the selectable determination results. Whether the selected RACH resource supports the feature can also be determined whether the type of the finally initiated random access is feature random access based on whether the selected RACH resource supports the feature.

[0060] Here, if it is determined that the selected RACH resource supports the feature that triggers random access, it may determine that the type of the finally initiated random access is feature random access.If it is determined that the selected RACH resource does not support the feature that triggers random access, it may determine that the type of the finally initiated random access is non-feature random access.

[0061] For example, if it is determined that the feature that triggers random access is SDT and the selected RACH resource supports the SDT feature, it can be determined that the type of the finally initiated random access is SDT RACH, and if it is determined that the selected RACH resource does not support the SDT feature, it can be determined that the type of the finally initiated random access is Non-SDT RACH.

[0062] For example, if it is determined that the feature that triggers random access is Redcap and that the selected RACH resource supports the Redcap feature, it can be determined that the type of random access finally initiated is msg1-based Redcap RACH, and if it is determined that the selected RACH resource does not support the Redcap feature, it can be determined that the type of random access finally initiated is Non-msg1-based Redcap RACH.

[0063] In one embodiment, the method comprises: determining whether a specific RACH resource of the feature is configured on the network side; determining, in response to the feature-specific RACH resource being configured, that the type of the ultimately initiated random access is feature random access; and determining, in response to the feature-specific RACH resource not being configured, that the type of the ultimately initiated random access is a non-feature random access.

[0064] In the above embodiment, determining whether the trigger condition of the feature is satisfied based on whether the specific RACH resource of the feature is configured is merely one of selectable determination results. Whether the specific RACH resource of the feature is configured can be determined based on whether the specific RACH resource of the feature is configured. Whether the type of the finally initiated random access is a feature random access can be determined.

[0065] Here, if it is determined that the feature-specific RACH resource is configured, it may be determined that the type of the finally initiated random access is feature random access, and if it is determined that the feature-specific RACH resource is not configured, it may be determined that the type of the finally initiated random access is non-feature random access.

[0066] For example, if it is determined that the feature that triggers random access is SDT and that an SDT-specific RACH resource is configured, it can be determined that the type of the finally initiated random access is SDT RACH. If it is determined that an SDT-specific RACH resource is not configured, it can be determined that the type of the finally initiated random access is Non-SDT RACH.

[0067] For example, if it is determined that the feature that triggers random access is Redcap and that a Redcap-specific RACH resource is configured, it can be determined that the type of the finally initiated random access is a msg1-based Redcap RACH. If it is determined that a Redcap-specific RACH resource is not configured, it can be determined that the type of the finally initiated random access is a Non-msg1-based Redcap RACH.

[0068] In one embodiment, after it is determined that the type of random access finally initiated is feature random access, no action may be performed, or an action may be performed, for example, the action performed may include, but is not limited to, an action of determining that the trigger condition of the feature is met.

[0069] In one embodiment, after it is determined that the type of random access finally initiated is a non-feature random access, no action may be performed or an action may be performed, for example, the action performed may include, but is not limited to, determining that the trigger condition of the feature is not satisfied.

[0070] 4 is a schematic flowchart of a resource partition configuration method according to an embodiment of the present disclosure. The resource partition configuration method according to this embodiment can be performed by a network-side device, and the network-side device can communicate with a terminal, including, but not limited to, a base station in a communication system, such as a 4G base station, a 5G base station, or a 6G base station. The terminal can include, but is not limited to, a communication device, such as a mobile phone, a tablet computer, a wearable device, a sensor, or an Internet of Things device.

[0071] As shown in FIG. 4, the resource partition configuration method may include step S401.

[0072] In step S401, configuring a random access channel (RACH) resource partition for a terminal, so that the terminal selects a RACH resource partition from the configured RACH resource partitions, and determines whether the selected RACH resource partition supports a feature for triggering random access; Wherein, in response to the selected RACH resource supporting the feature, the terminal determines that a trigger condition of the feature is met, and in response to the selected RACH resource not supporting the feature, the terminal determines that a trigger condition of the feature is not met.

[0073] In addition, the resources according to all embodiments of the present disclosure may be the entire resources (e.g., one frequency band, one channel) or a resource partition (e.g., some frequency domain resources in one frequency band, some frequency domain resources in one channel).

[0074] In one embodiment, the network side can configure a unique random access resource for the terminal, and configure a corresponding unique random access resource for each feature.

[0075] For example, a CE specific RACH resource is configured for the CE feature, and a Redcap (Reduced Capability) feature is configured for the Redcap specific RACH resource, so that if the feature that triggers random access is CE, the terminal can directly select the CE specific RACH resource to start random access, and if the feature that triggers random access is Redcap, the terminal can directly select the Redcap specific RACH resource to start random access.

[0076] In one embodiment, the unique random access resource configured for the terminal by the network side may be a unique random access resource configured for a feature combination.

[0077] For example, the specific RACH resource configured by the network side for the terminal includes two feature combination specific RACH resources, which are SDT (Small Data Transmission) + Redcap specific RACH resource and CE + Redcap specific RACH resource, respectively. At the same time, the network side can also configure a non-specific RACH resource, such as a legacy RACH resource, for the terminal.

[0078] Here, the feature of the terminal that triggers random access may be a single feature or a combination of features, including any feature that requires RACH resources.

[0079] When the terminal triggers random access, if it is a non-feature random access, it can select a legacy RACH resource to start the random access. If it is a feature random access, it can determine the feature that triggers the random access, for example, feature A.

[0080] Furthermore, if a feature-specific RACH resource is not configured for the terminal by the network side, the terminal may select a legacy RACH resource to initiate random access. If a feature-specific RACH resource (a specific RACH resource of any one feature, not limited to a specific RACH resource of feature A) is configured for the terminal by the network side device, the terminal may preferentially consider the feature-specific RACH resource, and if there is no selectable specific RACH resource of the feature, the terminal may select a legacy RACH resource to initiate random access.

[0081] Among these, the selection of a specific RACH resource of a feature by a terminal includes, but is not limited to, the following process:

[0082] The terminal determines whether there is a specific RACH resource whose corresponding feature is included in feature A (i.e., as a subset of feature A) among the specific RACH resources of the feature configured for the terminal by the network side. If there is, the terminal can select the specific RACH resource of the feature; if there is not, the terminal selects a legacy RACH resource to initiate random access.

[0083] For example, the feature of the terminal that triggers random access is SDT, and the specific RACH resources of the feature configured for the terminal by the network side include a specific RACH resource of SDT+Redcap and a specific RACH resource of CE+Redcap. Here, since SDT+Redcap is not included in SDT and CE+Redcap is not included in SDT (i.e., SDT+Redcap or CE+Redcap are not subsets of SDT), the terminal selects a legacy RACH resource to initiate random access.

[0084] In one embodiment, the RACH resource includes a unique RACH resource of a feature combination, the feature combination including at least two features.

[0085] In one embodiment, the selected RACH resource supporting the feature comprises: The feature combination corresponding to the RACH resource includes the feature that triggers random access.

[0086] In the above case, for the specific RACH resource of SDT+Redcap, since SDT+Redcap includes SDT, the specific RACH resource of SDT+Redcap can actually support the feature SDT. After the terminal initiates random access using the specific RACH resource of SDT+Redcap, the network side can appropriately configure the terminal based on the random access resource used by the terminal (i.e., the specific RACH resource of SDT+Redcap). However, since the terminal does not initiate random access using the specific RACH resource of SDT+Redcap but instead initiates random access using the legacy RACH resource, the network side cannot determine the terminal feature that triggers random access as early as possible.

[0087] Note that if the feature of the terminal that triggers random access is a feature combination of SDT+CE+Redcap, SDT+Redcap is included in SDT+CE+Redcap, and CE+Redcap is also included in SDT+CE+Redcap (i.e., SDT+Redcap or CE+Redcap are each a subset of SDT+CE+Redcap), so the terminal can select a specific RACH resource of SDT+Redcap or a specific RACH resource of CE+Redcap. Whether to select a specific RACH resource of SDT+Redcap or a specific RACH resource of CE+Redcap can be determined based on the priority of the features. For example, the selection basis can include preferentially satisfying the selection result of a feature with a higher priority. For example, if the feature priority is Redcap > CE > SDT, the specific RACH resource of CE+Redcap can be selected.

[0088] According to an embodiment of the present disclosure, a random access channel (RACH) resource partition is configured for a terminal by a network side device (which may be simply referred to as a network side). After the terminal determines a feature for triggering random access, the terminal selects a random access channel (RACH) resource and determines whether the selected RACH resource supports the feature. If the terminal determines that the selected RACH resource supports the feature, the terminal may determine that the trigger condition of the feature is met. If the terminal determines that the selected RACH resource does not support the feature, the terminal may determine that the trigger condition of the feature is not met.

[0089] This allows determining whether the trigger condition of the feature is met based on whether the selected RACH resource supports the feature. This is useful when a specific RACH resource of a feature combination is configured for the terminal by the network side, as it can determine a specific RACH resource that supports the feature from the specific RACH resource of the feature combination. Furthermore, by initiating random access using a specific RACH resource that supports the feature, the network side can determine the feature of the terminal that triggers random access as early as possible.

[0090] In one embodiment, the RACH resource partition configured for the terminal is further used by the terminal to determine whether a specific RACH resource of the feature is configured on the network side; Wherein, in response to a specific RACH resource of the feature not being configured, the terminal determines that a trigger condition of the feature is not satisfied, and in response to a specific RACH resource of the feature being configured, the terminal selects a RACH resource and determines whether the selected RACH resource supports the feature.

[0091] In one embodiment, before selecting a random access channel (RACH) resource, the terminal may first determine whether a specific RACH resource specific to the feature is configured on the network side, where the specific RACH resource of the feature refers to a feature corresponding to the specific RACH resource and includes the feature that triggers random access.

[0092] For example, if the feature that triggers random access is SDT, and the specific RACH resource configured for the terminal by the network side includes only the specific RACH resource of SDT+Redcap, since SDT+Redcap includes SDT, it can be determined that the specific RACH resource of the feature that triggers random access is configured on the network side.

[0093] For example, if the feature that triggers random access is SDT, and the specific RACH resource configured for the terminal by the network side only includes the specific RACH resource of CE+Redcap, it can be determined that the specific RACH resource of the feature that triggers random access is not configured on the network side because CE+Redcap does not include SDT.

[0094] Here, if it is determined that a specific RACH resource for the feature is not configured on the network side, it can be determined that the trigger condition for the feature is not satisfied. In this case, no matter how the UE selects a RACH resource, it cannot select a RACH resource that supports the feature. Therefore, it is not necessary to select a random access channel RACH resource and determine whether the selected RACH resource supports the feature, and therefore unnecessary operations can be avoided.

[0095] On the other hand, if it is determined that a specific RACH resource for the feature has been configured by the network side device, it can determine that the trigger condition for the feature is met, then select a random access channel RACH resource, and determine whether the selected RACH resource supports the feature.

[0096] In one embodiment, the RACH resource partition configured for the terminal is further used to determine the type of random access that the terminal ultimately initiates; Among these, in response to the selected RACH resource supporting the feature, the terminal determines that the type of random access finally initiated is feature random access, and in response to the selected RACH resource not supporting the feature, the terminal determines that the type of random access finally initiated is non-feature random access.

[0097] In the above embodiment, determining whether the trigger condition of the feature is satisfied based on whether the selected RACH resource supports the feature is merely one of the selectable determination results. Whether the selected RACH resource supports the feature can also be determined whether the type of the finally initiated random access is feature random access based on whether the selected RACH resource supports the feature.

[0098] Here, if it is determined that the selected RACH resource supports the feature that triggers random access, it may determine that the type of the finally initiated random access is feature random access.If it is determined that the selected RACH resource does not support the feature that triggers random access, it may determine that the type of the finally initiated random access is non-feature random access.

[0099] For example, if it is determined that the feature that triggers random access is SDT and the selected RACH resource supports the SDT feature, it can be determined that the type of the finally initiated random access is SDT RACH, and if it is determined that the selected RACH resource does not support the SDT feature, it can be determined that the type of the finally initiated random access is Non-SDT RACH.

[0100] For example, if it is determined that the feature that triggers random access is Redcap and that the selected RACH resource supports the Redcap feature, it can be determined that the type of random access finally initiated is msg1-based Redcap RACH, and if it is determined that the selected RACH resource does not support the Redcap feature, it can be determined that the type of random access finally initiated is Non-msg1-based Redcap RACH.

[0101] In one embodiment, the RACH resource partition configured for the terminal is further used by the terminal to determine whether a specific RACH resource of the feature is configured on the network side; Among these, in response to the feature-specific RACH resource being set, it is determined that the type of the finally initiated random access is feature random access, and in response to the feature-specific RACH resource not being set, it is determined that the type of the finally initiated random access is non-feature random access.

[0102] In the above embodiment, determining whether the trigger condition of the feature is satisfied based on whether the specific RACH resource of the feature is configured is merely one of the selectable determination results. Whether the specific RACH resource of the feature is configured can also be used to determine whether the type of the finally initiated random access is feature random access.

[0103] If it is determined that the feature-specific RACH resource is configured, it may be determined that the type of the finally initiated random access is feature random access.If it is determined that the feature-specific RACH resource is not configured, it may be determined that the type of the finally initiated random access is non-feature random access.

[0104] For example, if it is determined that the feature that triggers the random access is SDT and that an SDT-specific RACH resource is configured, it can be determined that the type of the finally initiated random access is SDT RACH, and if it is determined that an SDT-specific RACH resource is not configured, it can be determined that the type of the finally initiated random access is Non-SDT RACH.

[0105] For example, if it is determined that the feature that triggers the random access is Redcap and that a Redcap-specific RACH resource is configured, it can be determined that the type of the random access finally initiated is a msg1-based Redcap RACH, and if it is determined that a Redcap-specific RACH resource is not configured, it can be determined that the type of the random access finally initiated is a Non-msg1-based Redcap RACH.

[0106] Corresponding to the above-mentioned embodiments of the method for determining a trigger condition and the method for configuring a resource partition, the present disclosure further provides embodiments of an apparatus for determining a trigger condition and an apparatus for configuring a resource partition.

[0107] 5 is a schematic block diagram of a trigger condition determination device according to an embodiment of the present disclosure. The trigger condition determination device according to this embodiment is applicable to a terminal, which includes, but is not limited to, communication devices such as mobile phones, tablet computers, wearable devices, sensors, and Internet of Things devices. The terminal can communicate with a network side device, which includes, but is not limited to, a network side device (which may simply be referred to as the network side) in a communication system such as 4G, 5G, or 6G.

[0108] As shown in FIG. 5, the trigger condition determination device may include a processing module 501; The processing module 501 determines a feature that triggers random access, selects a random access channel (RACH) resource partition, and determines whether the selected RACH resource supports the feature; In response to the selected RACH resource supporting the feature, determining that a trigger condition of the feature is met, and in response to the selected RACH resource not supporting the feature, determining that a trigger condition of the feature is not met.

[0109] In one embodiment, the processing module further determines whether a specific RACH resource of the feature is configured on the network side; In response to a specific RACH resource of the feature not being configured, determine that a trigger condition of the feature is not satisfied, and in response to a specific RACH resource of the feature being configured, select a RACH resource and determine whether the selected RACH resource supports the feature.

[0110] In one embodiment, the processing module is further configured to determine that the type of the finally initiated random access is feature random access in response to the selected RACH resource supporting the feature, and to determine that the type of the finally initiated random access is non-feature random access in response to the selected RACH resource not supporting the feature.

[0111] In one embodiment, the processing module further determines whether a specific RACH resource of the feature is configured on the network side; In response to the feature-specific RACH resource being configured, the system is configured to determine that the type of the finally initiated random access is feature random access, and in response to the feature-specific RACH resource not being configured, the system is configured to determine that the type of the finally initiated random access is non-feature random access.

[0112] In one embodiment, the RACH resource includes a unique RACH resource of a feature combination, the feature combination including at least two features.

[0113] In one embodiment, the selected RACH resource supporting the feature comprises: The feature combination corresponding to the RACH resource includes the feature that triggers random access.

[0114] In one embodiment, the feature is: Capacity reduction (Redcap), Coverage Extension (CE), Radio Access Network Slicing (RAN slicing), and Small Data Transmission (SDT).

[0115] In one embodiment, the processing module is further configured to indicate to an upper layer via a media access control (MAC) layer whether a trigger condition of the feature is met, thereby assisting the upper layer in determining whether to trigger the feature.

[0116] In one embodiment, the features include at least a small data transmission SDT.

[0117] 6 is a schematic block diagram of a resource partition configuration device according to an embodiment of the present disclosure. The resource partition configuration device according to this embodiment is applicable to a network-side device, which can communicate with a terminal, including, but not limited to, a base station in a communication system, such as a 4G base station, a 5G base station, or a 6G base station. The terminal includes, but is not limited to, a communication device, such as a mobile phone, a tablet computer, a wearable device, a sensor, or an Internet of Things device.

[0118] As shown in FIG. 6, the resource partition configuration device may include: a sending module 601; The transmitting module 601 is configured to configure a random access channel (RACH) resource partition for a terminal, so that the terminal selects a RACH resource partition from the configured RACH resource partitions, and determines whether the selected RACH resource partition supports a feature for triggering random access; Wherein, in response to the selected RACH resource supporting the feature, the terminal determines that a trigger condition of the feature is met, and in response to the selected RACH resource not supporting the feature, the terminal determines that a trigger condition of the feature is not met.

[0119] In one embodiment, the RACH resource partition configured for the terminal is further used by the terminal to determine whether a specific RACH resource of the feature is configured on the network side; Wherein, in response to a specific RACH resource of the feature not being configured, the terminal determines that a trigger condition of the feature is not satisfied, and in response to a specific RACH resource of the feature being configured, the terminal selects a RACH resource and determines whether the selected RACH resource supports the feature.

[0120] In one embodiment, the RACH resource partition configured for the terminal is further used to determine the type of random access that the terminal ultimately initiates; Among these, in response to the selected RACH resource supporting the feature, the terminal determines that the type of random access finally initiated is feature random access, and in response to the selected RACH resource not supporting the feature, the terminal determines that the type of random access finally initiated is non-feature random access.

[0121] In one embodiment, the RACH resource partition configured for the terminal is further used by the terminal to determine whether a specific RACH resource of the feature is configured on the network side; Among these, in response to the feature-specific RACH resource being set, it is determined that the type of the finally initiated random access is feature random access, and in response to the feature-specific RACH resource not being set, it is determined that the type of the finally initiated random access is non-feature random access.

[0122] In one embodiment, the RACH resource includes a unique RACH resource of a feature combination, the feature combination including at least two features.

[0123] In one embodiment, the feature is: Capacity reduction (Redcap), Coverage Extension (CE), Radio Access Network Slicing (RAN slicing), and Small Data Transmission (SDT).

[0124] Regarding the apparatus in the above embodiment, the specific form of the operation performed by each module thereof has already been described in detail in the embodiment of the related method, so a detailed description thereof will be omitted here.

[0125] The device embodiment generally corresponds to the method embodiment, so for relevant parts, please refer to the description of some of the method embodiment. The device embodiment described above is merely an example, and modules described as separate components may or may not be physically separated. What is shown as a module may or may not be a physical module. That is, they may be located in the same place or distributed across multiple network modules. To achieve the purpose of the solution of this embodiment, some or all of the modules may be selected according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0126] An embodiment of the present disclosure further proposes a communication device, the communication device including a processor and a memory for storing a computer program, and when the computer program is executed by the processor, the method for determining a trigger condition described in any one of the above embodiments is realized.

[0127] An embodiment of the present disclosure further proposes a communication device, the communication device including a processor and a memory for storing a computer program, and when the computer program is executed by the processor, the resource partition configuration method described in any one of the above embodiments is realized.

[0128] An embodiment of the present disclosure further proposes a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, realizes steps in the method for determining a trigger condition described in any one of the above embodiments.

[0129] An embodiment of the present disclosure further proposes a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, realizes the steps in the resource partition configuration method described in any one of the above embodiments.

[0130] As shown in FIG. 7, FIG. 7 is a schematic block diagram of an apparatus 700 for determining a trigger condition according to an embodiment of the present disclosure. The apparatus 700 may be provided as a base station. Referring to FIG. 7, the apparatus 700 includes a processing component 722, a radio transmit / receive component 724, an antenna component 726, and a signal processing portion specific to the radio interface. The processing component 722 may further include one or more processors. One of the processors of the processing component 722 may be configured to implement the resource partition configuration method described in any one of the above embodiments.

[0131] 8 is a schematic block diagram of an apparatus 800 for configuring resource partitions according to an embodiment of the present disclosure. For example, the apparatus 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0132] Referring to FIG. 8, device 800 may include one or more of a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input / output (I / O) interface 812, a sensor component 814, and a communication component 816.

[0133] The processing component 802 controls the overall operation of the device 800, such as operations related to display, telephone calls, data communications, camera operation, and recording operations. The processing component 802 may include one or more processors 820 that execute instructions to complete all or some of the steps of the resource partition configuration method described above. The processing component 802 may also include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module that facilitates interaction between the multimedia component 808 and the processing component 802.

[0134] The memory 804 is configured to store various types of data to support operation on the device 800. Examples of this data include instructions for any applications or methods operating on the device 800, contact data, phone book data, messages, photos, videos, etc. The memory 804 can be implemented by any type of volatile and non-volatile storage device or combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks, etc.

[0135] The power supply component 806 provides power to the various components of the device 800. The power supply component 806 can include a power management system 806, one or more power sources 806, and other components associated with generating, managing, and distributing power to the device 800.

[0136] The multimedia component 808 includes a screen that provides an output interface between the device 800 and a user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). When the screen includes a touch panel, the screen may be implemented as a touch screen for receiving input signals from a user. The touch panel includes one or more touch sensors that detect touches, slides, and gestures on the touch panel. The touch sensors can detect not only the boundaries of the touch or slide motion but also the duration and pressure associated with the touch or slide motion. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a photo mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera may have a fixed optical lens system or may have a focal length and optical zoom capability.

[0137] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes one microphone (MIC), which is configured to receive external audio signals when the device 800 is in an operation mode such as a call mode, a recording mode, a voice recognition mode, etc. The received audio signals may be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, the audio component 810 further includes a speaker for outputting audio signals.

[0138] The I / O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, buttons, etc. These buttons may include, but are not limited to, a home button, volume buttons, a start button, and a lock button.

[0139] The sensor component 814 includes one or more sensors for providing status assessments of various aspects of the device 800. For example, the sensor component 814 can detect whether the device 800 is open or closed, the relative positions of components such as the display and keypad of the device 800, and changes in the position of the device 800 or a component of the device 800, whether or not the device 800 is in contact with a user, the orientation or acceleration / deceleration of the device 800, and changes in the temperature of the device 800. The sensor component 814 may also include a proximity sensor for detecting the presence of a nearby object without physical contact. The sensor component 814 may also include an optical sensor, such as a CMOS or CCD image sensor for use in imaging applications. In some embodiments, the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0140] The communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices. The device 800 can access wireless networks based on communication standards such as WiFi, 2G, 3G, 4G LTE, 5G NR, or a combination thereof. In an exemplary embodiment, the communication component 816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a near-field communication (NFC) module that facilitates short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0141] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components that perform the resource partition configuration method described above.

[0142] In an exemplary embodiment, a non-transitory computer-readable storage medium containing instructions, such as a memory 804 containing instructions, is further provided, and the above instructions are executed by the processor 820 of the device 800 to complete the above resource partition configuration method. For example, the non-transitory computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0143] Other embodiments of the present disclosure will be readily apparent to those skilled in the art from consideration of this specification and practice of the present disclosure. This disclosure is intended to cover any variations, applications, or reasonable modifications of the present disclosure, which variations, applications, or reasonable modifications follow the general principles of the present disclosure and include well-known common sense or customary technical means in the art not disclosed in the present disclosure. The specification and examples should be considered as merely illustrative, with the true scope and spirit of the present disclosure being defined by the following claims.

[0144] It should be understood that the present disclosure is not limited to the exact configuration previously described above and illustrated in the drawings, and that various modifications and changes can be made without departing from the scope of the present disclosure, which is limited only by the appended claims.

[0145] As used herein, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another and do not necessarily require or imply a relationship or order between them. The terms "comprises," "comprises," or any other variation thereof are intended to cover non-exclusive inclusions, whereby a process, method, article, or device that includes a set of elements includes not only those elements but also other elements not expressly listed, or further elements inherent in such process, method, article, or device. Without further limitation, elements defined by the phrase "comprises" do not exclude the presence of other identical elements in a process, method, article, or device that includes said elements.

[0146] The methods and devices according to the embodiments of the present disclosure have been described in detail above, and the present specification uses specific examples to explain the principles and embodiments of the present disclosure. However, the above descriptions of the embodiments are only used to help understand the method of the present disclosure and its core idea. Furthermore, those skilled in the art can modify the specific embodiments and application scope based on the idea of ​​the present disclosure. In summary, the contents of this specification should not be understood as limiting the present disclosure.

Claims

1. A method for determining a trigger condition executed by a terminal, comprising: determining a feature that triggers random access; selecting a random access channel (RACH) resource partition and determining whether the selected RACH resource supports the feature; determining, in response to the selected RACH resource supporting the feature, that a trigger condition for the feature is met; determining, in response to the selected RACH resource not supporting the feature, that a trigger condition for the feature is not met; The method for determining the trigger condition includes: and further comprising a step of instructing an upper layer via a media access control (MAC) layer whether a trigger condition of the feature is satisfied, to assist the upper layer in determining whether to trigger the feature, wherein the feature includes at least small data transmission (SDT). A method for determining a trigger condition, comprising:

2. The method for determining the trigger condition includes: determining whether a specific RACH resource for the feature is configured on the network side; determining that a trigger condition of the feature is not satisfied in response to a specific RACH resource of the feature not being configured; The step of selecting a random access channel (RACH) resource partition and determining whether the selected RACH resource partition supports the feature includes: In response to a specific RACH resource of the feature being configured, selecting a RACH resource and determining whether the selected RACH resource supports the feature.

2. The method of claim 1, wherein the trigger condition is satisfied.

3. The method for determining the trigger condition includes: determining, in response to the selected RACH resource supporting the feature, that a type of the finally initiated random access is feature random access; and determining, in response to the selected RACH resource not supporting the feature, that the type of the ultimately initiated random access is a non-feature random access.

2. The method of claim 1, wherein the trigger condition is satisfied.

4. The method for determining the trigger condition includes: determining whether a specific RACH resource for the feature is configured on the network side; determining, in response to the feature-specific RACH resource being configured, that the type of the finally initiated random access is feature random access; and determining, in response to the feature-specific RACH resource not being configured, that the type of the finally initiated random access is a non-feature random access.

2. The method of claim 1, wherein the trigger condition is satisfied.

5. The RACH resource includes a unique RACH resource of a feature combination, and the feature combination includes at least two features.

2. The method of claim 1, wherein the trigger condition is satisfied.

6. The selected RACH resource supports the feature, The feature combination corresponding to the RACH resource includes the feature that triggers random access.

6. The method of claim 5, wherein the trigger condition is satisfied.

7. The feature is Capacity reduction (Redcap), Coverage Extension (CE) and Radio Access Network Slicing (RAN slicing); and Small Data Transmission (SDT), 2. The method of claim 1, wherein the trigger condition is satisfied.

8. A resource partition configuration method executed by a network-side device, comprising: A step of configuring a random access channel (RACH) resource partition for a terminal that executes the method for determining a trigger condition according to any one of claims 1 to 7, so that the terminal selects a RACH resource partition from the configured RACH resource partitions and determines whether the selected RACH resource partition supports a feature for triggering random access, In response to the selected RACH resource supporting the feature, the terminal determining that a trigger condition for the feature is met, and in response to the selected RACH resource not supporting the feature, the terminal determining that a trigger condition for the feature is not met. A resource partition configuration method comprising:

9. The RACH resource partition configured for the terminal is further used by the terminal to determine whether a specific RACH resource for the feature is configured on the network side; In response to a specific RACH resource of the feature not being configured, the terminal determines that a trigger condition of the feature is not satisfied, and in response to a specific RACH resource of the feature being configured, the terminal selects a RACH resource and determines whether the selected RACH resource supports the feature. The resource partition configuration method according to claim 8 .

10. The RACH resource partition configured for the terminal is further used to determine the type of random access that the terminal ultimately initiates; In response to the selected RACH resource supporting the feature, the terminal determines that the type of the finally initiated random access is feature random access, and in response to the selected RACH resource not supporting the feature, the terminal determines that the type of the finally initiated random access is non-feature random access. The resource partition configuration method according to claim 8 .

11. The RACH resource partition configured for the terminal is further used by the terminal to determine whether a specific RACH resource for the feature is configured on the network side; determining that the type of the finally initiated random access is a feature random access in response to the feature-specific RACH resource being configured, and determining that the type of the finally initiated random access is a non-feature random access in response to the feature-specific RACH resource not being configured; The resource partition configuration method according to claim 8 .

12. The RACH resource includes a unique RACH resource of a feature combination, and the feature combination includes at least two features. The resource partition configuration method according to claim 8 .

13. The feature is Capacity reduction (Redcap), Coverage Extension (CE) and Radio Access Network Slicing (RAN slicing); and Small Data Transmission (SDT), The resource partition configuration method according to claim 8 .

14. 1. An apparatus for determining a trigger condition applied to a terminal, comprising: a processing module; The processing module: determining a feature that triggers random access, selecting a random access channel (RACH) resource partition, and determining whether the selected RACH resource supports the feature; configured to determine, in response to the selected RACH resource supporting the feature, that a trigger condition of the feature is met, and to determine, in response to the selected RACH resource not supporting the feature, that a trigger condition of the feature is not met; the processing module further comprising: configured to indicate to an upper layer via a media access control (MAC) layer whether a trigger condition of the feature is satisfied, thereby assisting the upper layer in determining whether to trigger the feature; The features include at least small data transmission (SDT); A trigger condition determination device characterized by:

15. A resource partition configuration device applied to a network-side device, comprising: a transmitting module; The transmitting module: The trigger condition determination device according to claim 14 is configured to configure a random access channel (RACH) resource partition for a terminal provided with the device, so that the terminal selects a RACH resource partition from the configured RACH resource partitions and determines whether the selected RACH resource partition supports a feature for triggering random access; In response to the selected RACH resource supporting the feature, the terminal determines that a trigger condition of the feature is met, and in response to the selected RACH resource not supporting the feature, the terminal determines that a trigger condition of the feature is not met. A resource partition setting device comprising:

16. A communication device, a processor; a memory for storing a computer program; When the computer program is executed by a processor, the trigger condition determination method according to any one of claims 1 to 7 or the resource partition configuration method according to any one of claims 8 to 13 is realized. A communication device comprising:

Images