Trigger condition judging, resource partitioning configuration method and apparatus

Abstract

The present disclosure relates to a triggering condition judging method, a resource partition configuration method and device, wherein the triggering condition judging method comprises: determining a characteristic of triggering random access; selecting a random access channel (RACH) resource, judging whether the selected RACH resource supports the characteristic; in response to the selected RACH resource supporting the characteristic, determining a triggering condition meeting the characteristic; in response to the selected RACH resource not supporting the characteristic, determining a triggering condition not meeting the characteristic. According to the present disclosure, whether the triggering condition meets the characteristic can be judged according to whether the selected RACH resource supports the characteristic, which is beneficial to determining, when the network side configures a specific RACH resource with a characteristic combination for a terminal, a specific RACH resource supporting the characteristic in the specific RACH resource with the characteristic combination, and then initiating random access through the specific RACH resource supporting the characteristic, so that the network side can determine the characteristic of the terminal triggering random access as early as possible.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to a trigger condition judgment method, a resource partitioning configuration method, a trigger condition judgment device, a resource partitioning configuration device, a communication device, and a computer-readable storage medium. Background Technology

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

[0003] For example, for a feature like Coverage Enhancement (CE), the network side can configure dedicated random access resources for this feature, such as a CE-specific RACH (Random Access Channel) resource. When a terminal triggers random access due to the CE feature, it can use the CE-specific RACH resource for random access. The network side can then determine the corresponding feature as CE based on the CE-specific RACH resource used by the terminal for random access, and thus configure the terminal appropriately based on the CE feature. Summary of the Invention

[0004] In view of the above, embodiments of this disclosure provide a trigger condition determination method, a resource partitioning configuration method, a trigger condition determination device, a resource partitioning configuration device, a communication device, and a computer-readable storage medium to solve the technical problems in the related art.

[0005] According to a first aspect of the present disclosure, a trigger condition determination method is proposed, executed by a terminal, the method 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; in response to the selected RACH resource supporting the feature, determining a trigger condition that satisfies the feature; and in response to the selected RACH resource not supporting the feature, determining a trigger condition that does not satisfy the feature.

[0006] According to a second aspect of the present disclosure, a resource partitioning configuration method is proposed, executed by a network-side device. The method includes: configuring a Random Access Channel (RACH) resource partition for a terminal, so that the terminal can select a RACH resource partition from the configured RACH resource partitions, and determining whether the selected RACH resource supports the feature of triggering random access; wherein, in response to the selected RACH resource supporting the feature, the terminal determines that the triggering condition of the feature is met; in response to the selected RACH resource not supporting the feature, the terminal determines that the triggering condition of the feature is not met.

[0007] According to a third aspect of the present disclosure, a triggering condition determination apparatus is provided, applicable to a terminal. The apparatus includes: a processing module configured to determine a feature that triggers random access; select a random access channel (RACH) resource partition and determine whether the selected RACH resource supports the feature; in response to the selected RACH resource supporting the feature, determine a triggering condition that satisfies the feature; and in response to the selected RACH resource not supporting the feature, determine a triggering condition that does not satisfy the feature.

[0008] According to a fourth aspect of the present disclosure, a resource partitioning configuration apparatus is provided, applicable to network-side devices. The apparatus includes: a transmitting module configured to configure a Random Access Channel (RACH) resource partition for a terminal, wherein the terminal selects a RACH resource partition from the configured RACH resource partitions and determines whether the selected RACH resource supports the feature of triggering random access; wherein, in response to the selected RACH resource supporting the feature, the terminal determines that the triggering condition of the feature is met; in response to the selected RACH resource not supporting the feature, the terminal determines that the triggering condition of the feature is not met.

[0009] According to a fifth aspect of the present disclosure, a communication device is provided, comprising: a processor; a memory for storing a computer program; wherein, when the computer program is executed by the processor, the above-described trigger condition determination method is implemented.

[0010] According to a sixth aspect of the present disclosure, a communication device is provided, comprising: a processor; a memory for storing a computer program; wherein, when the computer program is executed by the processor, the above-described resource partitioning configuration method is implemented.

[0011] According to a seventh aspect of the present disclosure, a computer-readable storage medium is provided for storing a computer program that, when executed by a processor, implements the steps in the above-described trigger condition determination method.

[0012] According to an eighth aspect of the present disclosure, a computer-readable storage medium is provided for storing a computer program that, when executed by a processor, implements the steps in the resource partitioning configuration method described above.

[0013] According to embodiments of this disclosure, after determining the feature that triggers random access, the terminal selects a Random Access Channel (RACH) resource and can determine whether the selected RACH resource supports the feature. If the selected RACH resource supports the feature, the triggering condition for the feature is determined to be met; otherwise, if the selected RACH resource does not support the feature, the triggering condition for the feature is determined not to be met.

[0014] Accordingly, it is possible to determine whether the triggering conditions of the feature are met based on whether the selected RACH resource supports the feature. This is beneficial when the network side configures a specific RACH resource with a feature combination for the terminal, and identifies the specific RACH resource that supports the feature among the specific RACH resources of the feature combination. Then, random access can be initiated through the specific RACH resource that supports the feature, so that the network side can determine the feature that triggers random access for the terminal as early as possible. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 This is a schematic flowchart illustrating a trigger condition determination method according to an embodiment of the present disclosure.

[0017] Figure 2 This is a schematic flowchart illustrating another trigger condition determination method according to an embodiment of the present disclosure.

[0018] Figure 3 This is a schematic flowchart illustrating another trigger condition determination method according to an embodiment of the present disclosure.

[0019] Figure 4 This is a schematic flowchart illustrating a resource partitioning configuration method according to an embodiment of the present disclosure.

[0020] Figure 5 This is a schematic block diagram of a trigger condition determination device according to an embodiment of the present disclosure.

[0021] Figure 6This is a schematic block diagram illustrating a resource partitioning configuration apparatus according to an embodiment of the present disclosure.

[0022] Figure 7 This is a schematic block diagram illustrating an apparatus for resource partitioning configuration according to embodiments of the present disclosure.

[0023] Figure 8 This is a schematic block diagram illustrating an apparatus for triggering condition determination according to an embodiment of the present disclosure. Detailed Implementation

[0024] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0025] The terminology used in this disclosure is for the purpose of describing specific embodiments only and is not intended to be limiting of the present disclosure. The singular forms “a” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates 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.

[0026] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of embodiments of this disclosure, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0027] For the sake of brevity and ease of understanding, this document uses the terms "greater than" or "less than", "higher than" or "lower than" to describe size relationships. However, it will be understood by those skilled in the art that the term "greater than" also includes the meaning of "greater than or equal to", and "less than" also includes the meaning of "less than or equal to"; the term "higher than" also includes the meaning of "higher than or equal to", and "lower than" also includes the meaning of "lower than or equal to".

[0028] Figure 1This is a schematic flowchart illustrating a trigger condition determination method according to an embodiment of the present disclosure. The trigger condition determination method shown in this embodiment can be executed by a terminal, which includes, but is not limited to, communication devices such as mobile phones, tablets, wearable devices, sensors, and IoT devices. The terminal can communicate with network-side devices, which include, but are not limited to, network-side devices in 4G, 5G, and 6G communication systems (which can be simply referred to as network-side devices), such as base stations and core networks.

[0029] like Figure 1 As shown, the trigger condition determination method may include the following steps:

[0030] In step S101, the characteristics that trigger random access are determined;

[0031] In step S102, a random access channel (RACH) resource is selected, and it is determined whether the selected RACH resource supports the aforementioned feature.

[0032] In step S103, in response to the selected RACH resource supporting the feature, a triggering condition for satisfying the feature is determined; in response to the selected RACH resource not supporting the feature, a triggering condition for not satisfying the feature is determined.

[0033] It should be noted that the resources involved in all embodiments of this disclosure can be a whole resource (e.g., a frequency band, a channel) or a resource partition (e.g., a portion of the frequency domain resources in a frequency band, a portion of the frequency domain resources in a channel).

[0034] In one embodiment, the dedicated random access resources configured for the terminal on the network side can be configured separately for each feature.

[0035] For example, configure CE-specific RACH resources for CE characteristics; configure Redcap-specific RACH resources for Redcap (ReducedCap) characteristics. Then, when the terminal triggers random access using the CE characteristic, it can directly select CE-specific RACH resources to initiate random access; when the triggering characteristic is Redcap, it can directly select Redcap-specific RACH resources to initiate random access.

[0036] In one embodiment, the dedicated random access resources configured by the network side for the terminal can also be dedicated random access resources configured for feature combinations.

[0037] For example, the network side configures specific RACH resources for terminals, including two feature combination-specific RACH resources: one for SDT (Small Data Transmission) + Redcap, and the other for CE + Redcap. Simultaneously, the network side can also configure non-specific RACH resources, such as traditional legacy RACH resources.

[0038] The feature that triggers random access for a terminal can be a single feature or a combination of features. Features that trigger random access include any feature that requires RACH resources.

[0039] When a terminal triggers random access, if it is a non-featured random access, it can choose the legacyRACH resource to initiate random access. If it is a feature-based random access, the feature that triggered the random access can be determined, for example, referred to as feature A.

[0040] Furthermore, if the network side does not configure a specific RACH resource for the terminal, the terminal can choose the legacy RACH resource to initiate random access; if the network side device configures a specific RACH resource for the terminal (a specific RACH resource for any feature, not limited to the specific RACH resource for feature A), the terminal can first consider the specific RACH resource for the feature. If there is no specific RACH resource for the feature that can be selected, the terminal can choose the legacy RACH resource to initiate random access.

[0041] The selection of specific RACH resources for a given characteristic by the terminal includes, but is not limited to, the following processes:

[0042] The terminal determines whether there exists a specific RACH resource configured for the terminal by the network side that corresponds to a feature included in feature A (i.e., a subset of feature A). If so, the terminal can select the specific RACH resource for that feature; otherwise, it will select the legacy RACH resource to initiate random access.

[0043] For example, if the feature that triggers random access for a terminal is SDT, the specific RACH resources configured for the terminal by the network side include specific RACH resources for SDT+Redcap and specific RACH resources for CE+Redcap. SDT+Redcap is not included in SDT, nor is CE+Redcap (that is, SDT+Redcap or CE+Redcap is not a subset of SDT). Therefore, the terminal will choose the legacy RACH resource to initiate random access.

[0044] In one embodiment, the RACH resource includes a feature-specific RACH resource, wherein the feature combination includes at least two features.

[0045] In one embodiment, the selected RACH resource supports the following features:

[0046] The characteristic combination corresponding to the RACH resource includes the characteristic that triggers random access.

[0047] In the above situation, regarding the specific RACH resources of SDT+Redcap, since SDT+Redcap includes SDT, the specific RACH resources of SDT+Redcap can actually support the SDT feature. After the terminal initiates random access using the specific RACH resources of SDT+Redcap, the network side can configure the terminal appropriately based on the random access resources used by the terminal (i.e., the specific RACH resources of SDT+Redcap). However, the terminal did not initiate random access through the specific RACH resources of SDT+Redcap, but instead initiated random access through the legacy RACH resources, causing the network side to fail to determine the feature of the terminal triggering random access in a timely manner.

[0048] It should be noted that if the terminal triggers random access using the combination of SDT+CE+Redcap, since SDT+Redcap is included within SDT+CE+Redcap, and CE+Redcap is also included within SDT+CE+Redcap (i.e., SDT+Redcap or CE+Redcap are subsets of SDT+CE+Redcap respectively), the terminal can choose either the specific RACH resource of SDT+Redcap or the specific RACH resource of CE+Redcap. The specific choice between SDT+Redcap and CE+Redcap can be determined based on the feature priority. For example, the selection criterion could include prioritizing higher-priority features. For instance, if the feature priority is Redcap > CE > SDT, then the specific RACH resource of CE+Redcap can be selected.

[0049] According to embodiments of this disclosure, after determining the feature that triggers random access, the terminal selects a Random Access Channel (RACH) resource and can determine whether the selected RACH resource supports the feature. If the selected RACH resource supports the feature, the terminal determines that the triggering condition for the feature is met; otherwise, if the selected RACH resource does not support the feature, the terminal determines that the triggering condition for the feature is not met.

[0050] Accordingly, it is possible to determine whether the triggering conditions of the feature are met based on whether the selected RACH resource supports the feature. This is beneficial when the network side configures a specific RACH resource with a feature combination for the terminal, and identifies the specific RACH resource that supports the feature among the specific RACH resources of the feature combination. Then, random access can be initiated through the specific RACH resource that supports the feature, so that the network side can determine the feature that triggers random access for the terminal as early as possible.

[0051] It should be noted that, after identifying a specific RACH resource that supports the aforementioned feature, the subsequent actions performed include, but are not limited to, initiating random access through the specific RACH resource that supports the aforementioned feature, and may also include other actions, which will be described in subsequent embodiments.

[0052] In one embodiment, the feature includes at least one of the following:

[0053] Capability reduction of Redcap holdings;

[0054] Enhanced CE coverage;

[0055] Radio Access Network (RAN) slicing;

[0056] Small Data Transmission Technology (SDT)

[0057] Figure 2 This is a schematic flowchart illustrating another trigger condition determination method according to embodiments of the present disclosure. Figure 2 As shown, the method further includes:

[0058] In step S201, the Media Access Control (MAC) layer instructs the higher layer whether the triggering conditions of the feature are met, assisting the higher layer in determining whether to trigger the feature. The feature includes at least Small Data Transmission (SDT).

[0059] In one embodiment, for the first feature, such as its triggering being determined by the MAC layer, the terminal can directly initiate random access through the selected RACH resource after determining that the selected RACH resource supports the first feature and that the triggering conditions of the first feature are met. The first feature includes, but is not limited to, Redcap, CE, and RAN slicing.

[0060] Regarding the second feature, its triggering is determined by a higher layer (e.g., the Radio Resource Control (RRC) layer). After determining that the selected RACH resource supports the second feature and that the triggering conditions for the second feature are met, the terminal can perform an action by instructing the higher layer through the MAC layer whether the triggering conditions for the second feature are met, thus assisting the higher layer in determining whether to trigger the feature. The second feature includes, but is not limited to, SDT.

[0061] For example, when the higher layer determines that the SDT triggering conditions are met according to the instructions of the MAC layer, other factors can also be considered to determine whether to initiate random access through the selected RACH resource.

[0062] Figure 3 This is a schematic flowchart illustrating another trigger condition determination method according to embodiments of the present disclosure. Figure 3 As shown, the method further includes:

[0063] In step S301, it is determined whether the network side has configured the dedicated RACH resource for the aforementioned feature;

[0064] In step S302, in response to a dedicated RACH resource that has not been configured with the feature, it is determined that the triggering condition of the feature is not met;

[0065] The step of selecting a RACH resource and determining whether the selected RACH resource supports the feature includes:

[0066] In step S303, in response to a dedicated RACH resource configured with the aforementioned feature, a random access channel RACH resource is selected, and it is determined whether the selected RACH resource supports the aforementioned feature.

[0067] In one embodiment, before selecting a random access channel (RACH) resource, the terminal may first determine whether the network side has configured a specific RACH resource for the aforementioned feature. The specific RACH resource refers to the feature corresponding to the specific RACH resource, including the feature that triggers random access.

[0068] For example, if the feature that triggers random access is SDT, and the specific RACH resources configured by the network side for the terminal only include the specific RACH resources of SDT+Redcap, since SDT+Redcap includes SDT, then it can be determined that the network side has configured the specific RACH resources that trigger the feature that triggers random access.

[0069] For example, if the feature that triggers random access is SDT, and the specific RACH resources configured by the network side for the terminal only include the specific RACH resources of CE+Redcap, since CE+Redcap does not include SDT, then it can be determined that the network side has not configured the specific RACH resources for the feature that triggers random access.

[0070] Specifically, if it is determined that the network side does not have a dedicated RACH resource configured with the aforementioned feature, it can be determined that the triggering condition of the aforementioned feature is not met. Therefore, no matter how the terminal selects a RACH resource, it cannot select a RACH resource that supports the aforementioned feature. Thus, it is not necessary to select a random access channel RACH resource and determine whether the selected RACH resource supports the aforementioned feature, thereby avoiding unnecessary operations.

[0071] When it is determined that the network-side device has configured a dedicated RACH resource with the aforementioned feature, the triggering conditions of the aforementioned feature can be determined before selecting the random access channel RACH resource, and it can be determined whether the selected RACH resource supports the aforementioned feature.

[0072] In one embodiment, the method further includes:

[0073] In response to the selected RACH resource supporting the feature, the type of the final initiated random access is determined to be feature random access (feature RACH).

[0074] In response to the selected RACH resource not supporting the feature, the type of random access finally initiated is determined to be non-feature random access (non-feature RACH).

[0075] In the above embodiments, determining whether the triggering condition of the feature is met based on whether the selected RACH resource supports the feature is only one of the possible determination results. Based on whether the selected RACH resource supports the feature, it can also be determined whether the type of the ultimately initiated random access is a feature-based random access.

[0076] Specifically, when it is determined that the selected RACH resource supports the feature that triggers random access, the type of the final initiated random access can be determined to be feature-based random access; when it is determined that the selected RACH resource does not support the feature that triggers random access, the type of the final initiated random access can be determined to be non-feature-based random access.

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

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

[0079] In one embodiment, the method further includes:

[0080] Determine whether the network side has configured dedicated RACH resources for the aforementioned features;

[0081] In response to a dedicated RACH resource configured with the aforementioned characteristics, the type of the ultimately initiated random access is determined to be characteristic random access;

[0082] In response to a dedicated RACH resource that is not configured with the aforementioned feature, the type of the ultimately initiated random access is determined to be non-feature random access.

[0083] In the above embodiments, determining whether the triggering condition of the feature is met based on whether a dedicated RACH resource for the feature is configured is only one of the optional determination results based on whether a dedicated RACH resource for the feature is configured. Based on whether a dedicated RACH resource for the feature is configured, it can also be determined whether the type of the ultimately initiated random access is feature-based random access.

[0084] Specifically, when a dedicated RACH resource configured with the aforementioned feature is identified, the type of random access initiated can be determined to be feature-based random access; when a dedicated RACH resource not configured with the aforementioned feature is identified, the type of random access initiated can be determined to be non-feature-based random access.

[0085] For example, if the feature that triggers random access is SDT, when it is determined that a dedicated RACH resource configured with SDT is available, the type of random access initiated can be determined to be SDT RACH. When it is determined that a dedicated RACH resource not configured with SDT is available, the type of random access initiated can be determined to be Non-SDT RACH.

[0086] For example, if the characteristic that triggers random access is Redcap, when it is determined that a dedicated RACH resource configured with Redcap is available, the type of random access initiated can be determined to be msg1-based Redcap RACH. When it is determined that a dedicated RACH resource not configured with Redcap is available, the type of random access initiated can be determined to be Non-msg1-based Redcap RACH.

[0087] In one embodiment, after determining that the type of the final initiated random access is feature-based random access, no action may be performed, or an action may be performed, such as determining the triggering conditions that satisfy the feature.

[0088] In one embodiment, after determining that the type of the final initiated random access is non-feature random access, no action may be performed, or an action may be performed. For example, the actions performed include, but are not limited to, determining that the triggering conditions of the feature are not met.

[0089] Figure 4 This is a schematic flowchart illustrating a resource partitioning configuration method according to an embodiment of the present disclosure. The resource partitioning configuration method shown in this embodiment can be executed by a network-side device, which can communicate with a terminal. The network-side device includes, but is not limited to, base stations in communication systems such as 4G base stations, 5G base stations, and 6G base stations. The terminal includes, but is not limited to, communication devices such as mobile phones, tablets, wearable devices, sensors, and IoT devices.

[0090] like Figure 4As shown, the resource partitioning configuration method may include the following steps:

[0091] In step S401, a random access channel (RACH) resource partition is configured for the terminal so that the terminal can select a RACH resource partition from the configured RACH resource partitions and determine whether the selected RACH resource supports the feature of triggering random access.

[0092] Wherein, in response to the selected RACH resource supporting the feature, the terminal determines that the triggering condition of the feature is met; in response to the selected RACH resource not supporting the feature, the terminal determines that the triggering condition of the feature is not met.

[0093] It should be noted that the resources involved in all embodiments of this disclosure can be a whole resource (e.g., a frequency band, a channel) or a resource partition (e.g., a portion of the frequency domain resources in a frequency band, a portion of the frequency domain resources in a channel).

[0094] In one embodiment, the dedicated random access resources configured for the terminal on the network side can be configured separately for each feature.

[0095] For example, configure CE-specific RACH resources for CE characteristics; configure Redcap-specific RACH resources for Redcap (ReducedCap) characteristics. Then, when the terminal triggers random access using the CE characteristic, it can directly select CE-specific RACH resources to initiate random access; when the triggering characteristic is Redcap, it can directly select Redcap-specific RACH resources to initiate random access.

[0096] In one embodiment, the dedicated random access resources configured by the network side for the terminal can also be configured for the corresponding dedicated random access resources for feature combinations.

[0097] For example, the network side configures specific RACH resources for terminals, including two feature combination-specific RACH resources: SDT (Small Data Transmission) + Redcap specific RACH resources, and CE + Redcap specific RACH resources. Simultaneously, the network side can also configure non-specific RACH resources for terminals, such as traditional legacy RACH resources.

[0098] The feature that triggers random access for a terminal can be a single feature or a combination of features. Features that trigger random access include any feature that requires RACH resources.

[0099] When a terminal triggers random access, if it is a non-featured random access, it can choose the legacyRACH resource to initiate random access. If it is a feature-based random access, the feature that triggered the random access can be determined, for example, referred to as feature A.

[0100] Furthermore, if the network side does not configure a specific RACH resource for the terminal, the terminal can choose the legacy RACH resource to initiate random access; if the network side device configures a specific RACH resource for the terminal (a specific RACH resource for any feature, not limited to the specific RACH resource for feature A), the terminal can first consider the specific RACH resource for the feature. If there is no specific RACH resource for the feature that can be selected, the terminal can choose the legacy RACH resource to initiate random access.

[0101] The selection of specific RACH resources for a given characteristic by the terminal includes, but is not limited to, the following processes:

[0102] The terminal determines whether there exists a specific RACH resource configured for the terminal by the network side that corresponds to a feature included in feature A (i.e., a subset of feature A). If so, the terminal can select the specific RACH resource for that feature; otherwise, it will select the legacy RACH resource to initiate random access.

[0103] For example, if the feature that triggers random access for a terminal is SDT, the specific RACH resources configured for the terminal by the network side include the specific RACH resources of SDT+Redcap and the specific RACH resources of CE+Redcap. SDT+Redcap is not included in SDT (that is, SDT+Redcap or CE+Redcap is not a subset of SDT), and CE+Redcap is not included in SDT. Therefore, the terminal will choose the legacy RACH resource to initiate random access.

[0104] In one embodiment, the RACH resource includes a feature-specific RACH resource, wherein the feature combination includes at least two features.

[0105] In one embodiment, the selected RACH resource supports the following features:

[0106] The characteristic combination corresponding to the RACH resource includes the characteristic that triggers random access.

[0107] In the above situation, regarding the specific RACH resources of SDT+Redcap, since SDT+Redcap includes SDT, the specific RACH resources of SDT+Redcap can actually support the SDT feature. After the terminal initiates random access using the specific RACH resources of SDT+Redcap, the network side can configure the terminal appropriately based on the random access resources used by the terminal (i.e., the specific RACH resources of SDT+Redcap). However, the terminal did not initiate random access through the specific RACH resources of SDT+Redcap, but instead initiated random access through the legacy RACH resources, causing the network side to fail to determine the feature of the terminal triggering random access in a timely manner.

[0108] It should be noted that if the terminal triggers random access using the combination of SDT+CE+Redcap, since SDT+Redcap is included within SDT+CE+Redcap, and CE+Redcap is also included within SDT+CE+Redcap (i.e., SDT+Redcap or CE+Redcap are subsets of SDT+CE+Redcap respectively), the terminal can choose either the specific RACH resource of SDT+Redcap or the specific RACH resource of CE+Redcap. The specific choice between SDT+Redcap and CE+Redcap can be determined based on the feature priority. For example, the selection criterion could include prioritizing higher-priority features. For instance, if the feature priority is Redcap > CE > SDT, then the specific RACH resource of CE+Redcap can be selected.

[0109] According to embodiments of this disclosure, a network-side device (hereinafter referred to as the network side) configures a Random Access Channel (RACH) resource partition for a terminal. After determining the feature that triggers random access, the terminal selects a RACH resource and can determine whether the selected RACH resource supports the feature. If the selected RACH resource supports the feature, the triggering condition for the feature is determined to be met; otherwise, if the selected RACH resource does not support the feature, the triggering condition for the feature is determined not to be met.

[0110] Accordingly, it is possible to determine whether the triggering conditions of the feature are met based on whether the selected RACH resource supports the feature. This is beneficial when the network side configures a specific RACH resource with a feature combination for the terminal, and identifies the specific RACH resource that supports the feature among the specific RACH resources of the feature combination. Then, random access can be initiated through the specific RACH resource that supports the feature, so that the network side can determine the feature that triggers random access for the terminal as early as possible.

[0111] In one embodiment, the RACH resource partition configured for the terminal is also used for the terminal to determine whether the network side has configured dedicated RACH resources for the feature.

[0112] Specifically, in response to a dedicated RACH resource that is not configured with the feature, the terminal determines that the triggering condition of the feature is not met; in response to a dedicated RACH resource that is configured with the feature, the terminal selects a RACH resource and determines whether the selected RACH resource supports the feature.

[0113] In one embodiment, before selecting a random access channel (RACH) resource, the terminal may first determine whether the network side has configured a specific RACH resource for the aforementioned feature. The specific RACH resource refers to the feature corresponding to the specific RACH resource, including the feature that triggers random access.

[0114] For example, if the feature that triggers random access is SDT, and the specific RACH resources configured by the network side for the terminal only include the specific RACH resources of SDT+Redcap, since SDT+Redcap includes SDT, then it can be determined that the network side has configured the specific RACH resources that trigger the feature that triggers random access.

[0115] For example, if the feature that triggers random access is SDT, and the specific RACH resources configured by the network side for the terminal only include the specific RACH resources of CE+Redcap, since CE+Redcap does not include SDT, then it can be determined that the network side has not configured the specific RACH resources for the feature that triggers random access.

[0116] Specifically, if it is determined that the network side does not have a dedicated RACH resource configured with the aforementioned feature, it can be determined that the triggering condition of the aforementioned feature is not met. Therefore, no matter how the terminal selects a RACH resource, it cannot select a RACH resource that supports the aforementioned feature. Thus, it is not necessary to select a random access channel RACH resource and determine whether the selected RACH resource supports the aforementioned feature, thereby avoiding unnecessary operations.

[0117] When it is determined that the network-side device has configured a dedicated RACH resource with the aforementioned feature, the triggering conditions of the aforementioned feature can be determined before selecting the random access channel RACH resource, and it can be determined whether the selected RACH resource supports the aforementioned feature.

[0118] In one embodiment, the RACH resource partition configured for the terminal is also used for the terminal to determine the type of random access ultimately initiated.

[0119] Wherein, in response to the selected RACH resource supporting the feature, the terminal determines that the type of the final initiated random access is feature-based random access; in response to the selected RACH resource not supporting the feature, the terminal determines that the type of the final initiated random access is non-feature-based random access.

[0120] In the above embodiments, determining whether the triggering condition of the feature is met based on whether the selected RACH resource supports the feature is only one of the possible determination results. Based on whether the selected RACH resource supports the feature, it can also be determined whether the type of the ultimately initiated random access is a feature-based random access.

[0121] Specifically, when it is determined that the selected RACH resource supports the feature that triggers random access, the type of the final initiated random access can be determined to be feature-based random access; when it is determined that the selected RACH resource does not support the feature that triggers random access, the type of the final initiated random access can be determined to be non-feature-based random access.

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

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

[0124] In one embodiment, the RACH resource partition configured for the terminal is also used for the terminal to determine whether the network side has configured dedicated RACH resources for the feature.

[0125] Specifically, in response to a dedicated RACH resource configured with the aforementioned feature, the type of the ultimately initiated random access is determined to be feature-based random access; in response to a dedicated RACH resource not configured with the aforementioned feature, the type of the ultimately initiated random access is determined to be non-feature-based random access.

[0126] In the above embodiments, determining whether the triggering condition of the feature is met based on whether a dedicated RACH resource for the feature is configured is only one of the optional determination results based on whether a dedicated RACH resource for the feature is configured. Based on whether a dedicated RACH resource for the feature is configured, it can also be determined whether the type of the ultimately initiated random access is feature-based random access.

[0127] Specifically, when a dedicated RACH resource configured with the aforementioned feature is identified, the type of random access initiated can be determined to be feature-based random access; when a dedicated RACH resource not configured with the aforementioned feature is identified, the type of random access initiated can be determined to be non-feature-based random access.

[0128] For example, if the feature that triggers random access is SDT, when it is determined that a dedicated RACH resource configured with SDT is available, the type of random access initiated can be determined to be SDT RACH. When it is determined that a dedicated RACH resource not configured with SDT is available, the type of random access initiated can be determined to be Non-SDT RACH.

[0129] For example, if the characteristic that triggers random access is Redcap, when it is determined that a dedicated RACH resource configured with Redcap is available, the type of random access initiated can be determined to be msg1-based Redcap RACH. When it is determined that a dedicated RACH resource not configured with Redcap is available, the type of random access initiated can be determined to be Non-msg1-based Redcap RACH.

[0130] Corresponding to the aforementioned embodiments of the trigger condition determination method and resource partition configuration method, this disclosure also provides embodiments of the trigger condition determination device and the resource partition configuration device.

[0131] Figure 5 This is a schematic block diagram illustrating a trigger condition determination device according to an embodiment of the present disclosure. The trigger condition determination device shown in this embodiment can be applied to terminals, including but not limited to mobile phones, tablets, wearable devices, sensors, IoT devices, and other communication devices. The terminal can communicate with network-side devices, including but not limited to network-side devices in 4G, 5G, 6G, and other communication systems (which can be simply referred to as network-side devices), such as base stations and core networks.

[0132] like Figure 5 As shown, the trigger condition determination device may include:

[0133] Processing module 501 is configured to determine the feature that triggers random access; select a random access channel (RACH) resource partition; and determine whether the selected RACH resource supports the feature.

[0134] In response to the selected RACH resource supporting the feature, a triggering condition for satisfying the feature is determined; in response to the selected RACH resource not supporting the feature, a triggering condition for not satisfying the feature is determined.

[0135] In one embodiment, the processing module is further configured to determine whether the network side has configured a dedicated RACH resource for the feature;

[0136] In response to a dedicated RACH resource that is not configured with the aforementioned feature, it is determined that the triggering condition for the feature is not met; in response to a dedicated RACH resource that is configured with the aforementioned feature, a RACH resource is selected, and it is determined whether the selected RACH resource supports the aforementioned feature.

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

[0138] In one embodiment, the processing module is further configured to determine whether the network side has configured a dedicated RACH resource for the feature;

[0139] In response to a dedicated RACH resource configured with the aforementioned feature, the type of the ultimately initiated random access is determined to be feature-based random access; in response to a dedicated RACH resource not configured with the aforementioned feature, the type of the ultimately initiated random access is determined to be non-feature-based random access.

[0140] In one embodiment, the RACH resource includes a feature-specific RACH resource, wherein the feature combination includes at least two features.

[0141] In one embodiment, the selected RACH resource supports the following features:

[0142] The characteristic combination corresponding to the RACH resource includes the characteristic that triggers random access.

[0143] In one embodiment, the feature includes at least one of the following:

[0144] Capability reduction of Redcap holdings;

[0145] Enhanced CE coverage;

[0146] Radio access network (RAN) slicing;

[0147] Small Data Transmission Technology (SDT)

[0148] In one embodiment, the processing module is further configured to instruct a higher layer via the Media Access Control (MAC) layer whether the triggering conditions of the feature are met, thereby assisting the higher layer in determining whether to trigger the feature.

[0149] In one embodiment, the feature includes at least: Small Data Transmission Time (SDT).

[0150] Figure 6 This is a schematic block diagram illustrating a resource partitioning configuration device according to an embodiment of the present disclosure. The resource partitioning configuration device shown in this embodiment can be applied to network-side devices, which can communicate with terminals. The network-side devices include, but are not limited to, base stations in communication systems such as 4G base stations, 5G base stations, and 6G base stations. The terminals include, but are not limited to, communication devices such as mobile phones, tablets, wearable devices, sensors, and IoT devices.

[0151] like Figure 6 As shown, the resource partitioning configuration device may include:

[0152] The transmitting module 601 is configured to configure a random access channel (RACH) resource partition for the terminal, so that the terminal can select a RACH resource partition from the configured RACH resource partition and determine whether the selected RACH resource supports the feature of triggering random access.

[0153] Wherein, in response to the selected RACH resource supporting the feature, the terminal determines that the triggering condition of the feature is met; in response to the selected RACH resource not supporting the feature, the terminal determines that the triggering condition of the feature is not met.

[0154] In one embodiment, the RACH resource partition configured for the terminal is also used for the terminal to determine whether the network side has configured dedicated RACH resources for the feature.

[0155] Specifically, in response to a dedicated RACH resource that is not configured with the feature, the terminal determines that the triggering condition of the feature is not met; in response to a dedicated RACH resource that is configured with the feature, the terminal selects a RACH resource and determines whether the selected RACH resource supports the feature.

[0156] In one embodiment, the RACH resource partition configured for the terminal is also used for the terminal to determine the type of random access ultimately initiated.

[0157] Wherein, in response to the selected RACH resource supporting the feature, the terminal determines that the type of the final initiated random access is feature-based random access; in response to the selected RACH resource not supporting the feature, the terminal determines that the type of the final initiated random access is non-feature-based random access.

[0158] In one embodiment, the RACH resource partition configured for the terminal is also used for the terminal to determine whether the network side has configured dedicated RACH resources for the feature.

[0159] Specifically, in response to a dedicated RACH resource configured with the aforementioned feature, the type of the ultimately initiated random access is determined to be feature-based random access; in response to a dedicated RACH resource not configured with the aforementioned feature, the type of the ultimately initiated random access is determined to be non-feature-based random access.

[0160] In one embodiment, the RACH resource includes a feature-specific RACH resource, wherein the feature combination includes at least two features.

[0161] In one embodiment, the feature includes at least one of the following:

[0162] Capability reduction of Redcap holdings;

[0163] Enhanced CE coverage;

[0164] Radio access network (RAN) slicing;

[0165] Small Data Transmission Technology (SDT)

[0166] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments of the relevant methods, and will not be elaborated upon here.

[0167] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0168] Embodiments of this disclosure also provide a communication device, including: a processor; a memory for storing a computer program; wherein, when the computer program is executed by the processor, the trigger condition determination method described in any of the above embodiments is implemented.

[0169] Embodiments of this disclosure also provide a communication device, including: a processor; a memory for storing a computer program; wherein, when the computer program is executed by the processor, it implements the resource partitioning configuration method described in any of the above embodiments.

[0170] Embodiments of this disclosure also propose a computer-readable storage medium for storing a computer program that, when executed by a processor, implements the steps in the trigger condition determination method described in any of the above embodiments.

[0171] Embodiments of this disclosure also provide a computer-readable storage medium for storing a computer program that, when executed by a processor, implements the steps of the resource partitioning configuration method described in any of the above embodiments.

[0172] like Figure 7 As shown, Figure 7 This is a schematic block diagram illustrating a device 700 for determining a trigger condition according to an embodiment of the present disclosure. The device 700 can be provided as a base station. (Refer to...) Figure 7 The apparatus 700 includes a processing component 722, a wireless transmitting / receiving component 724, an antenna component 726, and a signal processing section specific to the wireless interface. The processing component 722 may further include one or more processors. One of the processors in the processing component 722 may be configured to implement the resource partitioning configuration method described in any of the above embodiments.

[0173] Figure 8 This is a schematic block diagram illustrating an apparatus 800 for resource partitioning configuration according to embodiments of the present disclosure. For example, apparatus 800 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0174] Reference Figure 8 The device 800 may include one or more of the following components: a processing component 802, a memory 804, a power supply 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.

[0175] Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the resource partitioning configuration method described above. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

[0176] Memory 804 is configured to store various types of data to support the operation of device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

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

[0178] Multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 808 includes a front-facing camera and / or a rear-facing camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

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

[0180] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0181] Sensor assembly 814 includes one or more sensors for providing status assessments of various aspects of device 800. For example, sensor assembly 814 may detect the on / off state of device 800, the relative positioning of components such as the display and keypad of device 800, changes in the position of device 800 or a component of device 800, the presence or absence of user contact with device 800, the orientation or acceleration / deceleration of device 800, and temperature changes of device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 814 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

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

[0183] 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 to perform the resource partitioning configuration method described above.

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

[0185] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0186] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

[0187] It should be noted that, in this document, 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 any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0188] The methods and apparatus provided in the embodiments of this disclosure have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this disclosure. The descriptions of the embodiments above are only for the purpose of helping to understand the methods and core ideas of this disclosure. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this disclosure. Therefore, the content of this specification should not be construed as a limitation of this disclosure.

Claims

1. A method for determining triggering conditions, characterized in that, The method, executed by a terminal, includes: The characteristics that trigger random access are determined, including: Small Data Transmission Technique (SDT); Select a RACH resource partition in the random access channel (RACH) resource partition configured on the network side device, and determine whether the selected RACH resource supports the aforementioned feature. In response to the selected RACH resource supporting the feature, determine the triggering conditions that satisfy the feature; In response to the selected RACH resource not supporting the feature, it is determined that the triggering condition for the feature is not met; The method further includes: instructing a higher layer via the Media Access Control (MAC) layer whether the triggering conditions of the feature are met, in order to assist the higher layer in determining whether to trigger the feature.

2. The method according to claim 1, characterized in that, The method further includes: Determine whether the network side has configured dedicated RACH resources for the aforementioned features; In response to a dedicated RACH resource that is not configured with the aforementioned feature, it is determined that the triggering condition for the aforementioned feature is not met; The step of selecting a Random Access Channel (RACH) resource partition and determining whether the selected RACH resource supports the aforementioned feature includes: In response to a dedicated RACH resource configured with the aforementioned feature, a RACH resource is selected, and it is determined whether the selected RACH resource supports the aforementioned feature.

3. The method according to claim 1, characterized in that, The method further includes: In response to the selected RACH resource supporting the feature, the type of the final initiated random access is determined to be feature-based random access; In response to the selected RACH resource not supporting the feature, the type of random access finally initiated is determined to be non-feature random access.

4. The method according to claim 1, characterized in that, The method further includes: Determine whether the network side has configured dedicated RACH resources for the aforementioned features; In response to a dedicated RACH resource configured with the aforementioned characteristics, the type of the ultimately initiated random access is determined to be characteristic random access; In response to a dedicated RACH resource that is not configured with the aforementioned feature, the type of the ultimately initiated random access is determined to be non-feature random access.

5. The method according to claim 1, characterized in that, The RACH resource includes a feature combination-specific RACH resource, wherein the feature combination includes at least two features.

6. The method according to claim 5, characterized in that, The selected RACH resource supports the following features: The characteristic combination corresponding to the RACH resource includes the characteristic that triggers random access.

7. A resource partitioning configuration method, characterized in that, Performed by a network-side device, the method includes: Configure a random access channel (RACH) resource partition for the terminal so that the terminal can select a RACH resource partition from the configured RACH resource partitions and determine whether the selected RACH resource supports the feature of triggering random access, the feature including: small data transmission (SDT); Specifically, in response to the selected RACH resource supporting the feature, the terminal determines that the triggering condition of the feature is met; in response to the selected RACH resource not supporting the feature, the terminal determines that the triggering condition of the feature is not met; the terminal instructs the higher layer through the Media Access Control (MAC) layer whether the triggering condition of the feature is met, in order to assist the higher layer in determining whether to trigger the feature.

8. The method according to claim 7, characterized in that, The RACH resource partition configured for the terminal is also used for the terminal to determine whether the network side has configured dedicated RACH resources for the aforementioned feature; Specifically, in response to a dedicated RACH resource that is not configured with the feature, the terminal determines that the triggering condition of the feature is not met; in response to a dedicated RACH resource that is configured with the feature, the terminal selects a RACH resource and determines whether the selected RACH resource supports the feature.

9. The method according to claim 7, characterized in that, The RACH resource partition configured for the terminal is also used by the terminal to determine the type of random access that is ultimately initiated. Wherein, in response to the selected RACH resource supporting the feature, the terminal determines that the type of the final initiated random access is feature-based random access; in response to the selected RACH resource not supporting the feature, the terminal determines that the type of the final initiated random access is non-feature-based random access.

10. The method according to claim 7, characterized in that, The RACH resource partition configured for the terminal is also used for the terminal to determine whether the network side has configured dedicated RACH resources for the aforementioned feature; Specifically, in response to a dedicated RACH resource configured with the aforementioned feature, the type of the ultimately initiated random access is determined to be feature-based random access; in response to a dedicated RACH resource not configured with the aforementioned feature, the type of the ultimately initiated random access is determined to be non-feature-based random access.

11. The method according to claim 7, characterized in that, The RACH resource includes a feature combination-specific RACH resource, wherein the feature combination includes at least two features.

12. A trigger condition determination device, characterized in that, Suitable for a terminal, the device includes: The processing module is configured to determine the feature that triggers random access, the feature including: Small Data Transmission (SDT); select the Random Access Channel (RACH) resource partition in the RACH resource partition configured on the network side device, and determine whether the selected RACH resource supports the feature; In response to the selected RACH resource supporting the feature, a triggering condition for satisfying the feature is determined; in response to the selected RACH resource not supporting the feature, a triggering condition for not satisfying the feature is determined. And by instructing higher layers through the Media Access Control (MAC) layer whether the triggering conditions of the feature are met, the higher layers are assisted in determining whether to trigger the feature.

13. A resource partitioning configuration device, characterized in that, Applicable to network-side devices, the device includes: The transmitting module is configured to configure a Random Access Channel (RACH) resource partition for the terminal, so that the terminal can select a RACH resource partition from the configured RACH resource partitions and determine whether the selected RACH resource supports the feature of triggering random access, the feature including: Small Data Transmission (SDT); Wherein, in response to the selected RACH resource supporting the feature, the terminal determines that the triggering condition of the feature is met; in response to the selected RACH resource not supporting the feature, the terminal determines that the triggering condition of the feature is not met; wherein, the terminal instructs the higher layer through the Media Access Control (MAC) layer whether the triggering condition of the feature is met, in order to assist the higher layer in determining whether to trigger the feature.

14. A communication device, characterized in that, include: processor; Memory used to store computer programs; When the computer program is executed by the processor, it implements the trigger condition judgment method according to any one of claims 1 to 6.

15. A communication device, characterized in that, include: processor; Memory used to store computer programs; When the computer program is executed by a processor, it implements the resource partitioning configuration method according to any one of claims 7 to 12.

16. A computer-readable storage medium for storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps in the trigger condition judgment method according to any one of claims 1 to 6.

17. A computer-readable storage medium for storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps in the resource partitioning configuration method according to any one of claims 7 to 12.

Images