Random access resource configuration method and device, communication device, storage medium and program product

Abstract

This application discloses a random access resource (RO) configuration method and apparatus, communication device, storage medium, and program product. The method includes: sending first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters: a first parameter, the first parameter indicating the number of preambles for contention-based access by ordinary UEs; a second parameter, the second parameter indicating the start preamble for low-capability UEs; a third parameter, the third parameter indicating the number of preambles for low-capability UEs; and a fourth parameter, the fourth parameter indicating a subset of ROs allocated to low-capability UEs; wherein the one or more parameters are adjusted based on at least one of the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of access conflicts without signal in each period.

Description

Technical Field

[0001] This application relates to the field of wireless technology, and in particular to a random access resource configuration method and apparatus, communication equipment, storage medium, and program product. Background Technology

[0002] The Random Access Channel (RACH) is a shared transport layer access channel used by User Equipment (UE) to access a wireless network for operations such as call setup and burst data transmission. In wireless technology, the UE accesses the wireless network through a random access procedure. During this procedure, the UE randomly selects a random access resource from a predefined set of random access resources to transmit signals. When multiple UEs need to access the network, different UEs may select different random access resources and transmit signals based on their respective random access resources, thereby avoiding access conflicts between UEs.

[0003] With the introduction of low-capability (redcap) UEs, the UE types now include not only legacy UEs but also low-capability UEs. To identify different UE types, the network needs to allocate different ranges of preambles for each type. However, the current preamble allocation method lacks flexibility. When the number of a certain type of UE is small, it wastes random access resources; when the number of a certain type of UE is large, it leads to insufficient random access resources, thus affecting access efficiency. Summary of the Invention

[0004] To address the aforementioned technical problems, embodiments of this application provide a random access resource configuration method and apparatus, communication equipment, computer-readable storage medium, and computer program product.

[0005] The random access resource configuration method provided in this application embodiment is applied to the network side, and the method includes:

[0006] Send first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters:

[0007] The first parameter indicates the number of preambles required for contention-based access by a normal UE.

[0008] The second parameter indicates the start preamble of the low-capability UE;

[0009] The third parameter indicates the number of preambles for a low-capability UE;

[0010] The fourth parameter indicates the subset of ROs allocated to low-capability UEs;

[0011] The one or more parameters are adjusted based on at least one of the following in each cycle: the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of accesses without signal.

[0012] The random access resource configuration method provided in this application embodiment is applied to the UE side, and the method includes:

[0013] Receive first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters:

[0014] The first parameter indicates the number of preambles required for contention-based access by a normal UE.

[0015] The second parameter indicates the start preamble of the low-capability UE;

[0016] The third parameter indicates the number of preambles for a low-capability UE;

[0017] The fourth parameter indicates the subset of ROs allocated to low-capability UEs;

[0018] The one or more parameters are adjusted based on at least one of the following in each cycle: the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of accesses without signal.

[0019] The random access resource configuration device provided in this application embodiment is applied on the network side, and the device includes:

[0020] The sending unit is configured to send first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters:

[0021] The first parameter indicates the number of preambles required for a regular user equipment (UE) to compete for access.

[0022] The second parameter indicates the start preamble of the low-capability UE;

[0023] The third parameter indicates the number of preambles for a low-capability UE;

[0024] The fourth parameter indicates a subset of random access channel (RO) opportunities allocated to low-capability UEs.

[0025] The one or more parameters are adjusted based on at least one of the following in each cycle: the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of accesses without signal.

[0026] The random access resource configuration apparatus provided in this application embodiment is applied to the UE side, and the apparatus includes:

[0027] A receiving unit is configured to receive first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters:

[0028] The first parameter indicates the number of preambles required for contention-based access by a normal UE.

[0029] The second parameter indicates the start preamble of the low-capability UE;

[0030] The third parameter indicates the number of preambles for a low-capability UE;

[0031] The fourth parameter indicates the subset of ROs allocated to low-capability UEs;

[0032] The one or more parameters are adjusted based on at least one of the following in each cycle: the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of accesses without signal.

[0033] The communication device provided in this application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute any of the above-described random access resource configuration methods.

[0034] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute any of the above-described random access resource configuration methods.

[0035] The computer program product provided in this application includes computer program instructions that cause a computer to execute any of the above-described random access resource configuration methods.

[0036] In the technical solution of this application embodiment, the network side sends first system information, which carries a first configuration. The first configuration includes one or more of the following parameters: a first parameter, which indicates the number of preambles for contention-based access by ordinary user equipment (UE); a second parameter, which indicates the starting preamble for low-capability UEs; a third parameter, which indicates the number of preambles for low-capability UEs; and a fourth parameter, which indicates the random access channel timing (RO) subset allocated to low-capability UEs. The preamble range of low-capability UEs can be configured through one or more parameters in the first configuration. The network side adjusts one or more parameters in the first configuration based on at least one of the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of access conflicts without signal in each cycle. This achieves flexible adjustment of the preamble range for low-capability UEs, avoiding the problem of wasted or insufficient random access resources. Attached Figure Description

[0037] Figure 1 This is a schematic diagram illustrating an application scenario of an embodiment of this application;

[0038] Figure 2 This is a flowchart illustrating the random access resource configuration method provided in the embodiments of this application. Figure 1 ;

[0039] Figure 3 This is a flowchart illustrating the random access resource configuration method provided in the embodiments of this application. Figure 2 ;

[0040] Figure 4 This is a schematic diagram of preamble allocation provided in the embodiments of this application. Figure 1 ;

[0041] Figure 5 This is a schematic diagram of preamble allocation provided in the embodiments of this application. Figure 2 ;

[0042] Figure 6 This is a schematic diagram of preamble allocation provided in the embodiments of this application. Figure 3 ;

[0043] Figure 7 This is a schematic diagram of the structural composition of the random access resource configuration device provided in the embodiments of this application. Figure 1 ;

[0044] Figure 8 This is a schematic diagram of the structural composition of the random access resource configuration device provided in the embodiments of this application. Figure 2 ;

[0045] Figure 9 This is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0046] Figure 10 This is a schematic structural diagram of the chip according to an embodiment of this application. Detailed Implementation

[0047] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0048] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of this application.

[0049] like Figure 1 As shown, the communication system may include UE 110 and network device 120. Network device 120 can communicate with UE 110 via an air interface. Multi-service transmission is supported between UE 110 and network device 120.

[0050] It should be understood that the embodiments of this application are only illustrated by way of example using a communication system, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this application can be applied to various communication systems, such as 5G communication systems (also known as New Radio (NR) communication systems), or future communication systems, etc.

[0051] exist Figure 1 In the communication system shown, network device 120 can be an access network device that communicates with UE 110. The access network device can provide communication coverage for a specific geographical area and can communicate with UE 110 (e.g., UE) located within that coverage area.

[0052] Network equipment 120 can be a base station (gNB) in an NR system, or a network device in a future evolved Public Land Mobile Network (PLMN).

[0053] UE 110 can be any terminal device. For example, UE 110 can refer to an access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment, etc.

[0054] Figure 1 An exemplary illustration shows a base station and two UEs. Optionally, the wireless communication system may include multiple base station devices and each base station may include other numbers of UEs within its coverage area. This application does not limit this aspect.

[0055] It should be noted that, Figure 1 This application merely illustrates the system to which this application applies; of course, the methods shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including UE and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in the protocol.

[0056] Low-capability UEs and regular UEs can be allocated different random access resources and spectrum resources, or they can share random access resources and spectrum resources. However, sharing spectrum resources can affect both types of UEs in situations with high interference in a certain frequency band. This problem can be solved by allocating a dedicated bandwidth portion (BWP) to low-capability UEs. This requires the base station to identify the UE type through the preamble when receiving msg1, and then allocate different BWPs to different types of UEs.

[0057] To enable the base station to identify the UE type via preamble in msg1, it is necessary to divide the total preamble range into separate preamble ranges for different UE types. For this purpose, the network side needs to estimate the number of ordinary UEs and low-capability UEs in the cell, and then pre-configure random access resources (such as preamble resources, or PRACH resources) for different UE types using Man-Machine Language (MML) commands or configuration files. This configuration method requires manual confirmation, which can lead to configuration errors. Furthermore, when the number of UEs of a certain type is small, it results in wasted random access resources; when the number of UEs of a certain type is large, it leads to insufficient random access resources, thus affecting access efficiency (e.g., increased access conflict probability, increased access latency). Even if the configuration is adjusted, it still requires manual adjustment, consuming manpower. Therefore, the following technical solution is proposed in the embodiments of this application.

[0058] The technical solution of this application embodiment can be applied to the random access process. During the random access process, the UE selects a preamble from the configured preamble range and sends the preamble (i.e., sends msg1) to the base station on the PRACH. The base station detects the access signal (i.e., msg1). When the access signal is detected, the UE type can be identified through the preamble, and msg2 (i.e., random access response) is sent to the UE. The UE sends msg3 to the base station according to msg2. The base station decodes msg3. If the decoding fails, there is a situation where multiple UEs access conflict. If the base station does not detect the access signal, there is a situation where there is no signal access.

[0059] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application will be described below.

[0060] On the network side, N and R are configured through the parameters ssb-perRACH-OccasionAndCB-PreamblesPerSSB, where N represents the number of SSBs associated with a PRACH Occasion, and R represents the number of preambles for contention access per SSB per PRACH Occasion. N corresponds to the Layer 1 parameter SSB-per-rach-occasion, and R corresponds to the Layer 1 parameter CB-preambles-per-SSB. There are two possible configurations for N:

[0061] Case 1: If N < 1, it means that one SSB maps to multiple PRACH Occasions, and each PRACH Occasion has R consecutive preamble indices (0 to R-1). For example: totalNumberOfRA-Preambles = 64.

[0062] ssb-perRACH-OccasionAndCB-PreamblesPerSSB 1 / 8:12, that is, N=1 / 8, R=12. Wherein, N=1 / 8 means that one SSB is mapped to 8 PRACH Occasions; R=12 means that each PRACH Occasion has 12 consecutive preamble indices.

[0063] Scenario 2: If N ≥ 1, it means that one PRACH Occasion maps to multiple SSBs. SSB n has R consecutive preamble indices. The starting preamble index of SSB n is n * N_total_preamble / N, where n represents the index of the SSB. N_total_preamble is indicated by the parameter totalNumberOfRA-Preambles. For example: totalNumberOfRA-Preambles = 64.

[0064] The formula is ssb-perRACH-OccasionAndCB-PreamblesPerSSB 2:12, meaning N=2 and R=12. Here, N=2 represents two SSBs mapped to one PRACH Occasion; each SSB receives 32 preambles. The starting preamble index of SSB 0 is 0*64 / 2=0, and the 32 preamble indices of SSB 0 are 0 to 31. The starting preamble index of SSB 1 is 1*64 / 2=32, and the 32 preamble indices of SSB 1 are 32 to 63.

[0065] It should be noted that the random access channel timing (RACH Occasion, RO) described in the embodiments of this application can also be replaced by PRACH Occasion, that is, "RACH Occasion", "RO" and "PRACH Occasion" can be used interchangeably.

[0066] It should be noted that the network side described in the embodiments of this application can specifically be a base station.

[0067] It should be noted that the UEs described in the embodiments of this application are at least divided into two types: ordinary UEs and low-capability UEs. Among them, ordinary UEs may be, but are not limited to, enhanced mobile broadband (eMBB) UEs.

[0068] Figure 2 This is a flowchart illustrating the random access resource configuration method provided in the embodiments of this application. Figure 1 Applied to the network side, such as Figure 2 As shown, the random access resource configuration method includes the following steps:

[0069] Step 201: Send first system information, which carries a first configuration. The first configuration includes one or more of the following parameters: a first parameter indicating the number of preambles for contention-based access by ordinary UEs; a second parameter indicating the start preamble for low-capability UEs; a third parameter indicating the number of preambles for low-capability UEs; and a fourth parameter indicating the subset of ROs allocated to low-capability UEs. The one or more parameters are adjusted based on at least one of the following in each period: the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of access conflicts without signal.

[0070] In this embodiment, the base station sends first system information. In some implementations, the first system information is System Information Block 1 (SIB1). The first system information carries first configuration information, which is a configuration related to random access.

[0071] In some implementations, when the number of SSBs associated with each RO is greater than or equal to 1 (i.e., N≥1), the first configuration does not include the fourth parameter. Specifically, the first configuration includes the following parameters: a first parameter indicating the number of preambles for contention-based access by ordinary UEs; a second parameter indicating the starting preamble for low-capability UEs; and a third parameter indicating the number of preambles for low-capability UEs.

[0072] In some implementations, when the number of SSBs associated with each RO is less than 1 (i.e., N < 1), the first configuration includes a fourth parameter. Specifically, the first configuration includes the following parameters: a first parameter indicating the number of preambles for contention-based access by ordinary UEs; a second parameter indicating the starting preamble for low-capability UEs; a third parameter indicating the number of preambles for low-capability UEs; and a fourth parameter indicating the subset of ROs allocated to low-capability UEs.

[0073] It should be noted that the default / specified / conventional index of the start preamble for a normal UE is 0. Therefore, the first configuration above may not include parameters to indicate the start preamble for a normal UE.

[0074] In some descriptions, the first parameter can be denoted as CB-PreamblesPerSSB, representing the number of preambles required for contention-based access by a normal UE. The second parameter can be denoted as startPreambleForThisPartition or redcap_start_preamble, representing the starting preamble for a low-capability UE. The third parameter can be denoted as numberOfPreamblesPerSSB-ForThisPartition or redcap_preamble_num, representing the number of preambles required for a low-capability UE. The fourth parameter can be denoted as ssb-SharedRO-MaskIndex, representing the subset of ROs allocated to the low-capability UE.

[0075] The preamble range of a normal UE can be determined by the first parameter mentioned above; the preamble range of a low-capability UE can be determined by the second and third parameters mentioned above, or by the second, third, and fourth parameters mentioned above.

[0076] In some implementations, the preamble for contention-based access by a normal UE is located in a first region within the first preamble range, the preamble for a low-capability UE is located in a second region within the first preamble range, and the region within the first preamble range located between the first and second regions is the preamble for non-contention-based access.

[0077] Here, the first region refers to the area at the beginning of the first preamble range. The starting point of the first region corresponds to the starting point of the first preamble range, and the number of preambles contained in the first region is the number of preambles for normal UEs competing for access. The second region refers to the area at the end of the first preamble range. The starting point of the second region corresponds to the starting preamble of low-capability UEs, and the number of preambles contained in the second region is the number of preambles for low-capability UEs.

[0078] In some implementations, when the number of SSBs associated with each RO is greater than or equal to 1 (i.e., N≥1), the first preamble range is the preamble range associated with one SSB. Specifically, the index of the starting preamble of the first preamble range is n*N_total_preamble / N, where n represents the index of the SSB, and N_total_preamble is indicated by the parameter totalNumberOfRA-Preambles; the number of preambles in the first preamble range is totalNumberOfRA-Preambles / SSB-per-rach-occasion, where totalNumberOfRA-Preambles represents the total number of preambles for random access, and SSB-per-rach-occasion represents the number of SSBs associated with one RO.

[0079] In some implementations, when the number of SSBs associated with each RO is less than 1 (i.e., N < 1), the first preamble range is a preamble range associated with one RO. Specifically, the index of the starting preamble of the first preamble range is 0; the number of preambles in the first preamble range is totalNumberOfRA-Preambles, where totalNumberOfRA-Preambles represents the total number of preambles for random access.

[0080] Within the first preamble range, the network side (such as the base station) allocates the preamble of the front area (i.e., the first area) to ordinary UEs, the preamble of the back area (i.e., the second area) to low-capability UEs, and the preamble of the middle area (i.e., the area between the front area and the back area) to UEs with non-contention access.

[0081] In this embodiment of the application, one or more parameters in the first configuration are adjusted based on at least one of the following: the number of access conflicts of ordinary UEs, the number of access conflicts of low-capability UEs, and the number of accesses without signal in each cycle.

[0082] The period described in this embodiment can be denoted as T. Within each period T, the network side (e.g., a base station) counts at least one of the following: the number of access conflicts for ordinary UEs (denoted as EMBB_FAIL_N), the number of access conflicts for low-capability UEs (denoted as REDCAP_FAIL_N), and the number of accesses without signal. Based on at least one of these, one or more parameters in the first configuration are adjusted.

[0083] In some implementations, the network side (e.g., the base station) counts at least one of the following at the end of each period T: the number of access conflicts for ordinary UEs (denoted as EMBB_FAIL_N), the number of access conflicts for low-capability UEs (denoted as REDCAP_FAIL_N), and the number of accesses without signal. Based on at least one of these, one or more parameters in the first configuration are adjusted. After adjusting one or more parameters in the first configuration, when the transmission period of the first system information is reached, the adjusted one or more parameters are carried in the first system information.

[0084] In this embodiment, the transmission period of the first system information is fixed. For example, taking SIB1 as an example, the transmission period of SIB1 is 80ms. The one or more parameters carried in the first system information can be adjusted according to the period T. It should be noted that the length of the period T should be greater than the transmission period of the first system information, so as to avoid frequent adjustments to the parameters in the first system information.

[0085] In some implementations, the third parameter in the first system information (i.e., the number of preambles for low-capability UEs) is adjusted as follows:

[0086] 1) If the number of low-capability UE access conflicts in a period is greater than the first conflict number threshold, the number of preambles for low-capability UEs will be increased by the first step length in the next period.

[0087] Here, the first step length is denoted as redcapAddNum. The first step length can be defined by the protocol or configured on the network side.

[0088] For example: In period T1, the number of preambles for low-capability UEs is X1. If the number of access conflicts for low-capability UEs in period T1 exceeds the first conflict threshold, the number of preambles for low-capability UEs is increased by a step size redcapAddNum in the next period T2. In period T2, the number of preambles for low-capability UEs is X2 = X1 + redcapAddNum. After period T1 ends, when the transmission period of the first system information is reached, the network side sends the first system information and carries the adjusted third parameter in the first system information. The adjusted third parameter indicates that the number of preambles for low-capability UEs is X2.

[0089] 2) If the number of access conflicts of a low-capability UE in a period is greater than 0 and less than or equal to the first conflict number threshold, and the network side detects the access signal of a low-capability UE, then the number of preambles of the low-capability UE will not be adjusted in the next period.

[0090] 3) If the number of low-capability UE access conflicts is 0 in a cycle and the network side detects the access signal of the low-capability UE, then the number of preambles of the low-capability UE will be reduced in the next cycle according to the second step size.

[0091] Here, the second step size is denoted as redcapDelNum. The second step size can be defined by the protocol or configured on the network side.

[0092] For example: In period T1, the number of preambles for the low-capability UE is X1. If the number of access collisions for the low-capability UE is 0 in period T1 and the network detects an access signal from the low-capability UE, then in the next period T2, the number of preambles for the low-capability UE is reduced by a step size redcapDelNum. In period T2, the number of preambles for the low-capability UE is X2 = X1 - redcapDelNum. After period T1 ends, when the transmission period of the first system information is reached, the network sends the first system information and carries the adjusted third parameter in the first system information. The adjusted third parameter indicates that the number of preambles for the low-capability UE is X2.

[0093] 4) If the network side does not detect the access signal of the low-capability UE for L consecutive cycles (i.e., the number of times there is no signal access is L), then in the next cycle, the number of preambles of the low-capability UE will be adjusted to the first minimum number, where L is a positive integer; where the first minimum number is the minimum number of preambles of the low-capability UE, and the initial number of preambles of the low-capability UE is the first minimum number.

[0094] Here, the first minimum number (i.e., the minimum number of preambles for low-capability UEs) is denoted as redcap_min_preamble.

[0095] For example, if the network does not detect the access signal of a low-capability UE for L consecutive cycles, the number of preambles for the low-capability UE will be adjusted to redcap_min_preamble in the next cycle after L cycles.

[0096] In some implementations, when the number of SSBs associated with each RO is greater than or equal to 1, the number of preambles for a low-capability UE is greater than or equal to a first minimum number and less than or equal to a first maximum number. The first maximum number is determined based on the total number of preambles for random access, the number of SSBs associated with one RO, a second minimum number, and a third minimum number. The second minimum number is the minimum number of preambles for a normal UE, and the third minimum number is the minimum number of preambles for non-contention access.

[0097] Here, the first maximum number can be understood as the maximum number of preambles for a low-capability UE (corresponding to the case where the number of SSBs associated with each RO is greater than or equal to 1). The first maximum number can be determined by the following formula:

[0098] First maximum quantity = totalNumberOfRA-Preambles / SSB-per-rach-occasion

[0099] -embb_min_preamble-CFRA_min_preamble;

[0100] Wherein, totalNumberOfRA-Preambles represents the total number of preambles for random access; SSB-per-rach-occasion represents the number of SSBs associated with one RO; embb_min_preamble represents the second minimum number (i.e., the minimum number of preambles for a normal UE); and CFRA_min_preamble represents the third minimum number (i.e., the minimum number of preambles for non-contention access).

[0101] In some implementations, when the number of SSBs associated with each RO is less than 1, the number of preambles for a low-capability UE is greater than or equal to a first minimum number and less than or equal to a second maximum number. The second maximum number is determined based on the total number of preambles for random access, the second minimum number, and the third minimum number. The second minimum number is the minimum number of preambles for a normal UE, and the third minimum number is the minimum number of preambles for non-contention access.

[0102] Here, the second maximum number can be understood as the maximum number of preambles for a low-capability UE (corresponding to the case where the number of SSBs associated with each RO is less than 1). The second maximum number can be determined by the following formula:

[0103] Second maximum quantity = totalNumberOfRA - Preambles - embb_min_preamble

[0104] -CFRA_min_preamble;

[0105] Wherein, totalNumberOfRA-Preambles represents the total number of preambles for random access; embb_min_preamble represents the second minimum number (i.e., the minimum number of preambles for a normal UE); and CFRA_min_preamble represents the third minimum number (i.e., the minimum number of preambles for non-contention access).

[0106] In some implementations, when the number of SSBs associated with each RO is less than 1, the preamble of the low-capability UE occupies a portion of the preamble associated with one or more ROs, and the one or more ROs are a subset of ROs allocated to the low-capability UE as indicated by the fourth parameter.

[0107] In some implementations, if the number of preambles for low-capability UEs is increased in a preamble associated with an RO, and the number of preambles for low-capability UEs reaches a second maximum number, then a new RO is added, and the number of preambles for low-capability UEs is increased in the preamble associated with the new RO; wherein, the second maximum number is determined based on the total number of preambles for random access, the second minimum number, and the third minimum number, the second minimum number being the minimum number of preambles for ordinary UEs, and the third minimum number being the minimum number of preambles for non-contention access.

[0108] In some implementations, the first parameter in the first system information (i.e., the number of preambles for ordinary UE contention access) is adjusted as follows:

[0109] 1) If the number of access conflicts of a normal UE in a period is greater than the second conflict number threshold, the number of preambles of the normal UE will be increased according to the third step size in the next period.

[0110] Here, the third step length is denoted as EMBBAddNum. The third step length can be defined by the protocol or configured on the network side.

[0111] For example: In period T1, the number of preambles for a regular UE is Y1. If the number of access conflicts for a regular UE in period T1 exceeds the second conflict threshold, the number of preambles for the regular UE is increased by a step size EMBBAddNum in the next period T2. In period T2, the number of preambles for a regular UE is Y2 = Y1 + EMBBAddNum. After period T1 ends, when the transmission period of the first system information is reached, the network side sends the first system information and carries the adjusted first parameter in the first system information. The adjusted first parameter indicates that the number of preambles for the regular UE is Y2.

[0112] 2) If the number of access conflicts of a normal UE in a period is greater than 0 and less than or equal to the second conflict number threshold, and the network side detects the access signal of a normal UE, then the number of preambles of the normal UE will not be adjusted in the next period.

[0113] 3) If the number of access conflicts of a normal UE in a period is equal to 0, and the network side detects the access signal of a normal UE, then in the next period, the number of preambles of the normal UE will be reduced according to the fourth step length.

[0114] Here, the fourth step length is denoted as EMBBDelNum. The fourth step length can be defined by the protocol or configured on the network side.

[0115] For example: In period T1, the number of preambles for a regular UE is Y1. If the number of access conflicts for a regular UE is 0 and the network detects an access signal from a regular UE in period T1, then in the next period T2, the number of preambles for the regular UE is reduced by a step size EMBBDelNum. In period T2, the number of preambles for the regular UE is Y2 = Y1 - EMBBDelNum. After period T1 ends, when the transmission period of the first system information is reached, the network sends the first system information and carries the adjusted first parameter in the first system information. The adjusted first parameter indicates that the number of preambles for the regular UE is Y2.

[0116] 4) If the network side does not detect the access signal of a normal UE for K consecutive cycles (i.e., the number of times there is no signal access is K), then in the next cycle, the number of preambles of the normal UE will be adjusted to the second minimum number, where K is a positive integer; where the second minimum number is the minimum number of preambles of the normal UE, and the initial number of preambles of the normal UE is the second minimum number.

[0117] Here, the second minimum quantity (that is, the minimum number of preambles for a normal UE) is denoted as embb_min_preamble.

[0118] For example, if the network does not detect the access signal of a normal UE for K consecutive cycles, the number of preambles of the normal UE will be adjusted to embb_min_preamble in the next cycle after K cycles.

[0119] In some implementations, when the number of SSBs associated with each RO is greater than or equal to 1, the number of preambles for a normal UE is greater than or equal to the second minimum number and less than or equal to the third maximum number. The third maximum number is determined based on the total number of preambles for random access, the number of SSBs associated with one RO, the first minimum number, and the third minimum number. The first minimum number is the minimum number of preambles for low-capability UEs, and the third minimum number is the minimum number of preambles for non-contention access.

[0120] Here, the third maximum number can be understood as the maximum number of preambles for a normal UE (corresponding to the case where the number of SSBs associated with each RO is greater than or equal to 1). The third maximum number can be determined by the following formula:

[0121] The third maximum quantity = totalNumberOfRA-Preambles / SSB-per-rach-occasion

[0122] -redcap_min_preamble-CFRA_min_preamble;

[0123] Wherein, totalNumberOfRA-Preambles represents the total number of preambles for random access; SSB-per-rach-occasion represents the number of SSBs associated with one RO; redcap_min_preamble represents the first minimum number (i.e., the minimum number of preambles for low-capability UEs); and CFRA_min_preamble represents the third minimum number (i.e., the minimum number of preambles for non-contention access).

[0124] In some implementations, when the number of SSBs associated with each RO is less than 1, the number of preambles for a normal UE is greater than or equal to the second minimum number and less than or equal to the fourth maximum number. The fourth maximum number is determined based on the total number of preambles for random access, the first minimum number, and the third minimum number. The first minimum number is the minimum number of preambles for low-capability UEs, and the third minimum number is the minimum number of preambles for non-contention access.

[0125] Here, the fourth maximum number can be understood as the maximum number of preambles for a normal UE (corresponding to the case where the number of SSBs associated with each RO is less than 1). The fourth maximum number can be determined by the following formula:

[0126] Fourth maximum quantity = totalNumberOfRA - Preambles - redcap_min_preamble

[0127] -CFRA_min_preamble;

[0128] Wherein, totalNumberOfRA-Preambles represents the total number of preambles for random access; redcap_min_preamble represents the first minimum number (i.e., the minimum number of preambles for low-capability UEs); and CFRA_min_preamble represents the third minimum number (i.e., the minimum number of preambles for non-contention access).

[0129] It should be noted that when adjusting the number of preambles for low-capability UEs and / or the number of preambles for ordinary UEs in the manner described above, the number of preambles for low-capability UEs must be greater than or equal to the first minimum number and less than or equal to the first maximum number / the second maximum number, and the number of preambles for ordinary UEs must be greater than or equal to the second minimum number and less than or equal to the third maximum number / the fourth maximum number.

[0130] When the number of SSBs associated with each RO is greater than or equal to 1, when adjusting the number of preambles for low-capability UEs and / or normal UEs, the number of preambles for non-contention access should be guaranteed first. If, after adjusting the number of preambles for low-capability UEs and / or normal UEs, the number of preambles for non-contention access is less than the third minimum number (i.e., the minimum number of preambles for non-contention access), the number of preambles for normal UEs and / or low-capability UEs should be reduced (the reduction can be protocol-defined or network-configured) to ensure that the number of preambles for non-contention access reaches the third minimum number (i.e., the minimum number of preambles for non-contention access). In one scenario, if non-contention access fails to allocate preamble resources, the number of preambles for both normal UEs and low-capability UEs should be reduced by CFRADelNum / 2, and the number of preambles for non-contention access should be increased by CFRADelNum, where CFRADelNum can be protocol-defined or network-configured.

[0131] When the number of SSBs associated with each RO is less than 1, when adjusting the number of preambles for low-capability UEs and / or normal UEs in a certain RO, the number of preambles for non-contention access in that RO should be greater than or equal to the third minimum number (i.e., the minimum number of preambles for non-contention access). If, after adjusting the number of preambles for low-capability UEs and / or normal UEs, the number of preambles for non-contention access in a certain RO is less than the third minimum number (i.e., the minimum number of preambles for non-contention access), then the number of preambles for normal UEs and / or low-capability UEs in that RO should be reduced (the reduction can be protocol-defined or network-configured) to ensure that the number of preambles for non-contention access in that RO reaches the third minimum number (i.e., the minimum number of preambles for non-contention access). In one scenario, if a non-contentionable access preamble resource allocation fails in a certain RO, the number of preambles for both ordinary UEs and low-capability UEs in that RO is reduced by CFRADelNum / 2, and the number of preambles for non-contentionable access in that RO is increased by CFRADelNum. Here, CFRADelNum can be defined by the protocol or configured on the network side.

[0132] In the technical solution of this application embodiment, the network side sends first system information, which carries a first configuration. The first configuration includes one or more of the following parameters: a first parameter, which indicates the number of preambles for contention-based access by ordinary user equipment (UE); a second parameter, which indicates the starting preamble for low-capability UEs; a third parameter, which indicates the number of preambles for low-capability UEs; and a fourth parameter, which indicates the random access channel timing (RO) subset allocated to low-capability UEs. The preamble range of low-capability UEs can be configured through one or more parameters in the first configuration. The network side adjusts one or more parameters in the first configuration based on at least one of the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of access conflicts without signal in each cycle. This achieves flexible adjustment of the preamble range for low-capability UEs, avoiding the problem of wasted or insufficient random access resources.

[0133] Figure 3 This is a flowchart illustrating the random access resource configuration method provided in the embodiments of this application. Figure 2 Applied to the UE side, such as Figure 3 As shown, the random access resource configuration method includes the following steps:

[0134] Step 301: Receive first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters: a first parameter, the first parameter indicating the number of preambles for contention access by ordinary UEs; a second parameter, the second parameter indicating the start preamble for low-capability UEs; a third parameter, the third parameter indicating the number of preambles for low-capability UEs; a fourth parameter, the fourth parameter indicating the RO subset allocated to low-capability UEs; wherein, the one or more parameters are adjusted based on at least one of the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of access conflicts without signal in each period.

[0135] In this embodiment, the UE receives first system information. In some implementations, the first system information is SIB1. The first system information carries first configuration information, which is a configuration related to random access.

[0136] In some implementations, when the number of SSBs associated with each RO is greater than or equal to 1 (i.e., N≥1), the first configuration does not include the fourth parameter. Specifically, the first configuration includes the following parameters: a first parameter indicating the number of preambles for contention-based access by ordinary UEs; a second parameter indicating the starting preamble for low-capability UEs; and a third parameter indicating the number of preambles for low-capability UEs.

[0137] In some implementations, when the number of SSBs associated with each RO is less than 1 (i.e., N < 1), the first configuration includes a fourth parameter. Specifically, the first configuration includes the following parameters: a first parameter indicating the number of preambles for contention-based access by ordinary UEs; a second parameter indicating the starting preamble for low-capability UEs; a third parameter indicating the number of preambles for low-capability UEs; and a fourth parameter indicating the subset of ROs allocated to low-capability UEs.

[0138] It should be noted that the default / specified / conventional index of the start preamble for a normal UE is 0. Therefore, the first configuration above may not include parameters to indicate the start preamble for a normal UE.

[0139] In some descriptions, the first parameter can be denoted as CB-PreamblesPerSSB, representing the number of preambles required for contention-based access by a normal UE. The second parameter can be denoted as startPreambleForThisPartition or redcap_start_preamble, representing the starting preamble for a low-capability UE. The third parameter can be denoted as numberOfPreamblesPerSSB-ForThisPartition or redcap_preamble_num, representing the number of preambles required for a low-capability UE. The fourth parameter can be denoted as ssb-SharedRO-MaskIndex, representing the subset of ROs allocated to the low-capability UE.

[0140] The preamble range of a normal UE can be determined by the first parameter mentioned above; the preamble range of a low-capability UE can be determined by the second and third parameters mentioned above, or by the second, third, and fourth parameters mentioned above.

[0141] In some implementations, the preamble for contention-based access by a normal UE is located in a first region within the first preamble range, the preamble for a low-capability UE is located in a second region within the first preamble range, and the region within the first preamble range located between the first and second regions is the preamble for non-contention-based access.

[0142] Here, the first region refers to the area at the beginning of the first preamble range. The starting point of the first region corresponds to the starting point of the first preamble range, and the number of preambles contained in the first region is the number of preambles for normal UEs competing for access. The second region refers to the area at the end of the first preamble range. The starting point of the second region corresponds to the starting preamble of low-capability UEs, and the number of preambles contained in the second region is the number of preambles for low-capability UEs.

[0143] In some implementations, when the number of SSBs associated with each RO is greater than or equal to 1 (i.e., N≥1), the first preamble range is the preamble range associated with one SSB. Specifically, the index of the starting preamble of the first preamble range is n*N_total_preamble / N, where n represents the index of the SSB, and N_total_preamble is indicated by the parameter totalNumberOfRA-Preambles; the number of preambles in the first preamble range is totalNumberOfRA-Preambles / SSB-per-rach-occasion, where totalNumberOfRA-Preambles represents the total number of preambles for random access, and SSB-per-rach-occasion represents the number of SSBs associated with one RO.

[0144] In some implementations, when the number of SSBs associated with each RO is less than 1 (i.e., N < 1), the first preamble range is a preamble range associated with one RO. Specifically, the index of the starting preamble of the first preamble range is 0; the number of preambles in the first preamble range is totalNumberOfRA-Preambles, where totalNumberOfRA-Preambles represents the total number of preambles for random access.

[0145] Within the first preamble range, the network side (such as the base station) allocates the preamble of the front area (i.e., the first area) to ordinary UEs, the preamble of the back area (i.e., the second area) to low-capability UEs, and the preamble of the middle area (i.e., the area between the front area and the back area) to UEs with non-contention access.

[0146] In this embodiment of the application, one or more parameters in the first configuration are adjusted based on at least one of the following: the number of access conflicts of ordinary UEs, the number of access conflicts of low-capability UEs, and the number of accesses without signal in each cycle.

[0147] The period described in this embodiment can be denoted as T. Within each period T, the network side (e.g., a base station) counts at least one of the following: the number of access conflicts for ordinary UEs (denoted as EMBB_FAIL_N), the number of access conflicts for low-capability UEs (denoted as REDCAP_FAIL_N), and the number of accesses without signal. Based on at least one of these, one or more parameters in the first configuration are adjusted.

[0148] In some implementations, the network side (e.g., the base station) counts at least one of the following at the end of each period T: the number of access conflicts for ordinary UEs (denoted as EMBB_FAIL_N), the number of access conflicts for low-capability UEs (denoted as REDCAP_FAIL_N), and the number of accesses without signal. Based on at least one of these, one or more parameters in the first configuration are adjusted. After adjusting one or more parameters in the first configuration, when the transmission period of the first system information is reached, the adjusted one or more parameters are carried in the first system information.

[0149] In this embodiment, the transmission period of the first system information is fixed. For example, taking SIB1 as an example, the transmission period of SIB1 is 80ms. The one or more parameters carried in the first system information can be adjusted according to the period T. It should be noted that the length of the period T should be greater than the transmission period of the first system information, so as to avoid frequent adjustments to the parameters in the first system information.

[0150] It should be noted that the method for adjusting the parameters in the first system information can be referred to the above. Figure 2 Description of the relevant solutions.

[0151] For the UE, when the transmission period of the first system information is reached, the UE receives the first system information and initiates a random access procedure according to the parameters in the currently received first system information.

[0152] The technical solutions of the embodiments of this application are illustrated below with specific application examples.

[0153] Application Example 1

[0154] This application example illustrates the case where the number of SSBs associated with each RO is greater than or equal to 1 (i.e., SSB-per-rach-occasion ≥ 1). When SSB-per-rach-occasion ≥ 1, the network side does not configure the fourth parameter ssb-SharedRO-MaskIndex in SIB1. The fourth parameter indicates the subset of ROs allocated to low-capability UEs.

[0155] like Figure 4As shown, SSB-per-rach-occasion = 4, meaning one RO is associated with 4 SSBs: SSB0, SSB1, SSB2, and SSB3. For SSB n (0 ≤ n ≤ 3), the index of its associated start preamble is n * N_total_preamble / N, where n represents the SSB index, and N_total_preamble is indicated by the parameter totalNumberOfRA-Preambles. The number of preambles associated with each SSB is totalNumberOfRA-Preambles / SSB-per-rach-occasion, where totalNumberOfRA-Preambles represents the total number of preambles for random access, and SSB-per-rach-occasion represents the number of SSBs associated with one RO.

[0156] Within the preamble range associated with each SSB, there are three types of preambles: preambles for low-capability UEs, preambles for normal UEs, and preambles for non-contention-based access. The number of these three types of preambles has corresponding minimum values: redcap_min_preamble (the first minimum number), embb_min_preamble (the second minimum number), and CFRA_min_preamble (the third minimum number). Furthermore, for ease of description, the number of preambles for low-capability UEs is denoted as redcap_preamble_num, the number of preambles for normal UEs as embb_preamble_num, and the number of preambles for non-contention-based access as CFRA_preamble_num; the number of access conflicts for low-capability UEs within a period is denoted as REDCAP_FAIL_N, the number of access conflicts for normal UEs within a period is denoted as EMBB_FAIL_N, and the conflict threshold is denoted as MAX_FAIL.

[0157] The start preamble for low-capability UEs is denoted as redcap_start_preamble, where...

[0158] redcap_start_preamble=totalNumberOfRA-Preambles / SSB-per-rach-occasion

[0159] -redcap_preamble_num+1.

[0160] Herein, totalNumberOfRA-Preambles represents the total number of random access preambles; SSB-per-rach-occasion represents the number of SSBs associated with one RO.

[0161] For redcap_preamble_num, the adjustment is performed in the following manner:

[0162] 1) redcap_preamble_num is initialized to redcap_min_preamble.

[0163] 2) If REDCAP_FAIL_N counted in the current period is greater than MAX_FAIL, redcap_preamble_num is increased by the step size redcapAddNum, where when redcap_preamble_num is increased, it is required to be less than or equal to totalNumberOfRA-Preambles / SSB-per-rach-occasion

[0164] -embb_min_preamble-CFRA_min_preamble.

[0165] Herein, totalNumberOfRA-Preambles represents the total number of random access preambles; SSB-per-rach-occasion represents the number of SSBs associated with one RO.

[0166] 3) If 0 < REDCAP_FAIL_N ≤ MAX_FAIL is counted in the current period, and the network side detects an access signal of a low-capability UE, redcap_preamble_num is not adjusted.

[0167] 4) If REDCAP_FAIL_N = 0 is counted in the current period, and the network side detects an access signal of a low-capability UE, redcap_preamble_num is decreased by redcapDelNum, where when redcap_preamble_num is decreased, it is required to be greater than or equal to redcap_min_preamble.

[0168] 5) If the network side does not detect an access signal of a low-capability UE for L consecutive periods, redcap_preamble_num is decreased to redcap_min_preamble.

[0169] For embb_preamble_num, the adjustment is performed in the following manner:

[0170] 1) embb_preamble_num is initially set to embb_min_preamble.

[0171] 2) If it is counted in the current period that EMBB_FAIL_N>MAX_FAIL, embb_min_preamble is increased by the step size EMBBAddNum, wherein when embb_min_preamble is increased, it is required to be less than or equal to totalNumberOfRA-Preambles / SSB-per-rach-occasion

[0172] -redcap_min_preamble-CFRA_min_preamble.

[0173] Herein, totalNumberOfRA-Preambles represents the total number of random access preambles; SSB-per-rach-occasion represents the number of SSBs associated with one RO.

[0174] 3) If it is counted in the current period that 0<EMBB_FAIL_N≤MAX_FAIL, and the network side detects an access signal of a normal UE, embb_preamble_num is not adjusted.

[0175] 4) If it is counted in the current period that EMBB_FAIL_N=0, and the network side detects an access signal of a normal UE, embb_preamble_num is decreased by EMBBDelNum, wherein when embb_preamble_num is decreased, it is required to be greater than or equal to embb_min_preamble.

[0176] 5) If the network side does not detect an access signal of a normal UE for K consecutive periods, embb_preamble_num is decreased to embb_min_preamble.

[0177] It should be noted that when adjusting `redcap_preamble_num` and `embb_preamble_num` as described above, preamble resources for non-contentionable access should be guaranteed. If, after adjusting `redcap_preamble_num` and `embb_preamble_num`, `CFRA_preamble_num` is less than `CFRA_min_preamble`, both `redcap_preamble_num` and `embb_preamble_num` need to be reduced to bring `CFRA_preamble_num` up to `CFRA_min_preamble`. In some cases, if non-contentionable access fails to allocate preamble resources, both `redcap_preamble_num` and `embb_preamble_num` should be reduced by `CFRADelNum / 2`, and `CFRA_preamble_num` should be increased by `CFRADelNum`, where `CFRADelNum` can be defined by the protocol or configured on the network side.

[0178] Application Example 2

[0179] This application example illustrates the case where the number of SSBs associated with each RO is less than 1 (i.e., SSB-per-rach-occasion < 1). When SSB-per-rach-occasion < 1, the network side configures the fourth parameter ssb-SharedRO-MaskIndex in SIB1. The fourth parameter indicates the subset of ROs allocated to low-capability UEs.

[0180] like Figure 5 As shown, the index of the starting preamble associated with each RO is 0, and the number of preambles associated with each RO is totalNumberOfRA-Preambles, where totalNumberOfRA-Preambles represents the total number of preambles for random access.

[0181] There are three types of preambles: preambles for low-capability UEs, preambles for normal UEs, and preambles for non-contention-based access. Each of these three types of preambles has a corresponding minimum number: redcap_min_preamble (the first minimum number), embb_min_preamble (the second minimum number), and CFRA_min_preamble (the third minimum number). For ease of description, the number of preambles for low-capability UEs is denoted as redcap_preamble_num, the number of preambles for normal UEs as embb_preamble_num, and the number of preambles for non-contention-based access as CFRA_preamble_num; the number of access conflicts for low-capability UEs within a period is denoted as REDCAP_FAIL_N, the number of access conflicts for normal UEs within a period is denoted as EMBB_FAIL_N, and the conflict threshold is denoted as MAX_FAIL.

[0182] The start preamble for low-capability UEs is denoted as redcap_start_preamble, where...

[0183] redcap_start_preamble = totalNumberOfRA - Preambles - redcap_preamble_num + 1. Where totalNumberOfRA - Preambles represents the total number of preambles for random access.

[0184] Adjust redcap_preamble_num as follows:

[0185] 1) The preamble of a low-capability UE occupies part of the preamble in RO1, and redcap_preamble_num is initially redcap_min_preamble.

[0186] Here, ssb-SharedRO-MaskIndex=1, which indicates that the RO subset allocated to the low-capability UE is RO1, that is, the preamble of the low-capability UE occupies part of the preamble in RO1.

[0187] 2) If REDCAP_FAIL_N > MAX_FAIL is found in the current period, then increase redcap_preamble_num by the step size redcapAddNum. When increasing redcap_preamble_num, it must be less than or equal to totalNumberOfRA - Preambles - embb_min_preamble.

[0188] -CFRA_min_preamble.

[0189] Herein, totalNumberOfRA-Preambles represents the total number of random access preambles.

[0190] 3) If it is counted in the current period that 0<REDCAP_FAIL_N≤MAX_FAIL, and the network side detects an access signal of a low-capability UE, redcap_preamble_num is not adjusted.

[0191] 4) If it is counted in the current period that REDCAP_FAIL_N=0, and the network side detects an access signal of a low-capability UE, redcap_preamble_num is decreased by redcapDelNum, where when redcap_preamble_num is decreased, it shall be ensured to be greater than or equal to redcap_min_preamble.

[0192] 5) If after redcap_preamble_num is increased to the maximum value (i.e., totalNumberOfRA-Preambles-embb_min_preamble-CFRA_min_preamble) within RO1, redcap_preamble_num still needs to be increased, one RO2 is added, as Figure 6 shown, redcap_preamble_num is increased in RO2 in the manner of step 2) described above.

[0193] Here, ssb-SharedRO-MaskIndex=2, which is used to indicate that the RO subset allocated to the low-capability UE is RO1 and RO2, that is, the preambles of the low-capability UE occupy part of the preambles in RO1 and RO2.

[0194] 6) If the network side does not detect an access signal of a low-capability UE for L consecutive periods, the preambles allocated to the low-capability UE on RO2 are deleted, and redcap_preamble_num on RO1 is decreased to redcap_min_preamble.

[0195] For embb_preamble_num, adjustment is performed on each RO in the following manner:

[0196] 1) embb_preamble_num is initialized as embb_min_preamble.

[0197] 2) If EMBB_FAIL_N>MAX_FAIL is counted in the current period, embb_min_preamble is increased by the step size EMBBAddNum, wherein when embb_min_preamble is increased, it is required to be less than or equal to totalNumberOfRA-Preambles-redcap_min_preamble

[0198] -CFRA_min_preamble.

[0199] Wherein, totalNumberOfRA-Preambles represents the total number of random access preambles.

[0200] 3) If 0<EMBB_FAIL_N≤MAX_FAIL is counted in the current period, and the network side detects an access signal of a normal UE, embb_preamble_num is not adjusted.

[0201] 4) If EMBB_FAIL_N=0 is counted in the current period, and the network side detects an access signal of a normal UE, embb_preamble_num is decreased by EMBBBDelNum, wherein when embb_preamble_num is decreased, it is required to be greater than or equal to embb_min_preamble.

[0202] 5) If the network side does not detect an access signal of a normal UE for K consecutive periods, embb_preamble_num is decreased to embb_min_preamble.

[0203] It should be noted that when adjusting `redcap_preamble_num` and `embb_preamble_num` as described above, preamble resources for non-contentionable access in each Resource Entity (RO) should be guaranteed. If, after adjusting `redcap_preamble_num` and `embb_preamble_num`, `CFRA_preamble_num` in any RO is less than `CFRA_min_preamble`, then `redcap_preamble_num` and `embb_preamble_num` in that RO should be reduced to bring `CFRA_preamble_num` to `CFRA_min_preamble`. In some cases, if non-contentionable access preamble resource allocation fails in any RO, then `redcap_preamble_num` and `embb_preamble_num` in that RO should each be reduced by `CFRADelNum / 2`, and `CFRA_preamble_num` in that RO should be increased by `CFRADelNum`. Here, `CFRADelNum` can be defined by the protocol or configured on the network side.

[0204] The technical solution of this application embodiment achieves flexible adjustment of the preamble range of low-capability UEs by automatically adjusting redcap_preamble_num, avoiding the problem of waste or insufficiency of random access resources. Compared with manual adjustment of redcap_preamble_num, it saves manpower and improves the adjustment accuracy.

[0205] Figure 7 This is a schematic diagram of the structural composition of the random access resource configuration device provided in the embodiments of this application. Figure 1 Applied to the network side, such as Figure 7 As shown, the random access resource configuration device includes:

[0206] The sending unit 701 is configured to send first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters:

[0207] The first parameter indicates the number of preambles required for contention-based access by a normal UE.

[0208] The second parameter indicates the start preamble of the low-capability UE;

[0209] The third parameter indicates the number of preambles for a low-capability UE;

[0210] The fourth parameter indicates the subset of ROs allocated to low-capability UEs;

[0211] The one or more parameters are adjusted based on at least one of the following in each cycle: the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of accesses without signal.

[0212] In some implementations, the preamble for contention-based access by a normal UE is located in a first region within the first preamble range, and the preamble for a low-capability UE is located in a second region within the first preamble range. The region within the first preamble range located between the first region and the second region is the preamble for non-contention-based access.

[0213] In some embodiments, the apparatus further includes an adjustment unit 702; the adjustment unit 702 is configured to: if the number of access conflicts of a low-capability UE in a period is greater than a first conflict threshold, increase the number of preambles of the low-capability UE in the next period by a first step size; if the number of access conflicts of a low-capability UE in a period is greater than 0 and less than or equal to the first conflict threshold, and the network side detects an access signal of a low-capability UE, then not adjust the number of preambles of the low-capability UE in the next period; if the number of access conflicts of a low-capability UE in a period is equal to 0, and the network side detects an access signal of a low-capability UE, then decrease the number of preambles of the low-capability UE in the next period by a second step size; if the network side does not detect an access signal of a low-capability UE for L consecutive periods, then adjust the number of preambles of the low-capability UE to a first minimum number in the next period, where L is a positive integer; wherein, the first minimum number is the minimum number of preambles of the low-capability UE, and the initial number of preambles of the low-capability UE is the first minimum number.

[0214] In some implementations, when the number of SSBs associated with each RO is greater than or equal to 1, the number of preambles for the low-capability UE is greater than or equal to the first minimum number and less than or equal to the first maximum number. The first maximum number is determined based on the total number of preambles for random access, the number of SSBs associated with one RO, the second minimum number, and the third minimum number. The second minimum number is the minimum number of preambles for a normal UE, and the third minimum number is the minimum number of preambles for non-contention access. Alternatively, when the number of SSBs associated with each RO is less than 1, the number of preambles for the low-capability UE is greater than or equal to the first minimum number and less than or equal to the second maximum number. The second maximum number is determined based on the total number of preambles for random access, the second minimum number, and the third minimum number. The second minimum number is the minimum number of preambles for a normal UE, and the third minimum number is the minimum number of preambles for non-contention access.

[0215] In some implementations, if the number of SSBs associated with each RO is greater than or equal to 1, the first configuration does not include the fourth parameter; or if the number of SSBs associated with each RO is less than 1, the first configuration includes the fourth parameter.

[0216] In some implementations, when the number of SSBs associated with each RO is less than 1, the preamble of the low-capability UE occupies a portion of the preamble associated with one or more ROs, wherein the one or more ROs are a subset of ROs allocated to the low-capability UE as indicated by the fourth parameter.

[0217] In some embodiments, the adjustment unit 702 is configured to add a new RO and add the number of preambles of the low-capability UE to the preamble associated with the new RO if the number of preambles of the low-capability UE reaches a second maximum number when the number of preambles of the low-capability UE is increased in a preamble associated with a RO; wherein the second maximum number is determined based on the total number of preambles for random access, a second minimum number, and a third minimum number, the second minimum number being the minimum number of preambles for a normal UE, and the third minimum number being the minimum number of preambles for non-contention access.

[0218] In some implementations, the adjustment unit 702 is configured to: if the number of access conflicts of a regular UE in a period is greater than a second conflict threshold, increase the number of preambles of the regular UE in the next period by a third step size; if the number of access conflicts of a regular UE in a period is greater than 0 and less than or equal to the second conflict threshold, and the network side detects an access signal of a regular UE, not adjust the number of preambles of the regular UE in the next period; if the number of access conflicts of a regular UE in a period is equal to 0, and the network side detects an access signal of a regular UE, decrease the number of preambles of the regular UE in the next period by a fourth step size; if the network side does not detect an access signal of a regular UE for K consecutive periods, adjust the number of preambles of the regular UE to a second minimum number in the next period, where K is a positive integer; wherein, the second minimum number is the minimum number of preambles of the regular UE, and the initial number of preambles of the regular UE is the second minimum number.

[0219] In some implementations, when the number of SSBs associated with each RO is greater than or equal to 1, the number of preambles for the ordinary UE is greater than or equal to the second minimum number and less than or equal to the third maximum number. The third maximum number is determined based on the total number of preambles for random access, the number of SSBs associated with one RO, the first minimum number, and the third minimum number. The first minimum number is the minimum number of preambles for low-capability UEs, and the third minimum number is the minimum number of preambles for non-contention access. Alternatively, when the number of SSBs associated with each RO is less than 1, the number of preambles for the ordinary UE is greater than or equal to the second minimum number and less than or equal to the fourth maximum number. The fourth maximum number is determined based on the total number of preambles for random access, the first minimum number, and the third minimum number. The first minimum number is the minimum number of preambles for low-capability UEs, and the third minimum number is the minimum number of preambles for non-contention access.

[0220] Those skilled in the art should understand that Figure 7 The functions of each unit in the random access resource configuration device shown can be understood by referring to the relevant description of the aforementioned method. Figure 7 The functions of each unit in the random access resource configuration device shown can be implemented by a program running on a processor or by specific logic circuits.

[0221] Figure 8 This is a schematic diagram of the structural composition of the random access resource configuration device provided in the embodiments of this application. Figure 2 Applied to the UE side, such as Figure 8 As shown, the random access resource configuration device includes:

[0222] Receiving unit 801 is configured to receive first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters:

[0223] The first parameter indicates the number of preambles required for contention-based access by a normal UE.

[0224] The second parameter indicates the start preamble of the low-capability UE;

[0225] The third parameter indicates the number of preambles for a low-capability UE;

[0226] The fourth parameter indicates the subset of ROs allocated to low-capability UEs;

[0227] The one or more parameters are adjusted based on at least one of the following in each cycle: the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of accesses without signal.

[0228] In some implementations, the preamble for contention-based access by a normal UE is located in a first region within the first preamble range, and the preamble for a low-capability UE is located in a second region within the first preamble range. The region within the first preamble range located between the first region and the second region is the preamble for non-contention-based access.

[0229] In some embodiments, the apparatus further includes an access unit 802, configured to initiate a random access procedure based on one or more parameters.

[0230] Those skilled in the art should understand that Figure 8 The functions of each unit in the random access resource configuration device shown can be understood by referring to the relevant description of the aforementioned method. Figure 8 The functions of each unit in the random access resource configuration device shown can be implemented by a program running on a processor or by specific logic circuits.

[0231] Figure 9 This is a schematic structural diagram of a communication device 900 provided in an embodiment of this application. The communication device can be a UE or a network-side device (such as a base station). Figure 9 The communication device 900 shown includes a processor 910, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0232] Optionally, such as Figure 9 As shown, the communication device 900 may further include a memory 920. The processor 910 can retrieve and run computer programs from the memory 920 to implement the methods described in this embodiment.

[0233] The memory 920 can be a separate device independent of the processor 910, or it can be integrated into the processor 910.

[0234] Optionally, such as Figure 9 As shown, the communication device 900 may also include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0235] The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include antennas, and the number of antennas may be one or more.

[0236] Optionally, the communication device 900 may specifically be a network-side device (such as a base station) in the embodiments of this application, and the communication device 900 may implement the corresponding processes implemented by the network-side device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0237] Optionally, the communication device 900 may specifically be a UE in the embodiments of this application, and the communication device 900 may implement the corresponding processes implemented by the UE in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0238] Figure 10 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 10 The chip 1000 shown includes a processor 1010, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0239] Optionally, such as Figure 10 As shown, chip 1000 may further include memory 1020. Processor 1010 can retrieve and run computer programs from memory 1020 to implement the methods described in this embodiment.

[0240] The memory 1020 can be a separate device independent of the processor 1010, or it can be integrated into the processor 1010.

[0241] Optionally, the chip 1000 may also include an input interface 1030. The processor 1010 can control the input interface 1030 to communicate with other devices or chips, specifically, to acquire information or data sent by other devices or chips.

[0242] Optionally, the chip 1000 may also include an output interface 1040. The processor 1010 can control the output interface 1040 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0243] Optionally, the chip can be applied to network-side devices (such as base stations) in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network-side devices in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0244] Optionally, the chip can be applied to the UE in the embodiments of this application, and the chip can implement the corresponding processes implemented by the UE in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0245] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0246] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0247] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0248] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0249] This application also provides a computer-readable storage medium for storing computer programs.

[0250] Optionally, the computer-readable storage medium can be applied to network-side devices (such as base stations) in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the network-side devices in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0251] Optionally, the computer-readable storage medium can be applied to the UE in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the UE in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0252] This application also provides a computer program product, including computer program instructions.

[0253] Optionally, the computer program product can be applied to network-side devices (such as base stations) in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network-side devices in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0254] Optionally, the computer program product can be applied to the UE in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the UE in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0255] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0256] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0257] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0258] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

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

[0260] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A method for random access resource allocation, characterized in that, Applied to the network side, the method includes: Send first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters: The first parameter indicates the number of preambles required for a regular user equipment (UE) to compete for access. The second parameter indicates the start preamble of the low-capability UE; The third parameter indicates the number of preambles for a low-capability UE; The fourth parameter indicates a subset of random access channel (RO) opportunities allocated to low-capability UEs. The one or more parameters are adjusted based on at least one of the following in each cycle: the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of accesses without signal.

2. The method according to claim 1, characterized in that, The preamble for contention-based access by a normal UE is located in a first region within the first preamble range, and the preamble for a low-capability UE is located in a second region within the first preamble range. The region within the first preamble range located between the first region and the second region is the preamble for non-contention-based access.

3. The method according to claim 1, characterized in that, The method further includes: If the number of access conflicts of a low-capability UE in a period is greater than the first conflict threshold, then the number of preambles of the low-capability UE will be increased by the first step length in the next period. If the number of access conflicts of a low-capability UE in a period is greater than 0 and less than or equal to the first conflict number threshold, and the network side detects the access signal of a low-capability UE, then the number of preambles of the low-capability UE will not be adjusted in the next period. If the number of access conflicts of a low-capability UE in a cycle is equal to 0, and the network side detects the access signal of a low-capability UE, then in the next cycle, the number of preambles of the low-capability UE is reduced according to the second step size. If the network does not detect the access signal of a low-capability UE for L consecutive cycles, the number of preambles of the low-capability UE will be adjusted to the first minimum number in the next cycle, where L is a positive integer. Wherein, the first minimum quantity is the minimum number of preambles for a low-capability UE, and the initial number of preambles for the low-capability UE is the first minimum quantity.

4. The method according to claim 3, characterized in that, When the number of SSBs associated with each RO is greater than or equal to 1, the number of preambles of the low-capability UE is greater than or equal to the first minimum number and less than or equal to the first maximum number. The first maximum number is determined based on the total number of preambles for random access, the number of SSBs associated with one RO, the second minimum number, and the third minimum number. The second minimum number is the minimum number of preambles for a normal UE, and the third minimum number is the minimum number of preambles for non-contention access. or, When the number of SSBs associated with each RO is less than 1, the number of preambles of the low-capability UE is greater than or equal to the first minimum number and less than or equal to the second maximum number. The second maximum number is determined based on the total number of preambles for random access, the second minimum number, and the third minimum number. The second minimum number is the minimum number of preambles for a normal UE, and the third minimum number is the minimum number of preambles for non-contention access.

5. The method according to any one of claims 1 to 3, characterized in that, If the number of SSBs associated with each RO is greater than or equal to 1, the first configuration does not include the fourth parameter; or, If the number of SSBs associated with each RO is less than 1, the first configuration includes the fourth parameter.

6. The method according to claim 5, characterized in that, When the number of SSBs associated with each RO is less than 1, the preamble of the low-capability UE occupies a portion of the preamble associated with one or more ROs, wherein the one or more ROs are a subset of ROs allocated to the low-capability UE as indicated by the fourth parameter.

7. The method according to claim 6, characterized in that, The method further includes: If the number of preambles for the low-capability UE is increased in a preamble associated with an RO, and the number of preambles for the low-capability UE reaches the second maximum number, then a new RO is added, and the number of preambles for the low-capability UE is increased in the preamble associated with the new RO; wherein, the second maximum number is determined based on the total number of preambles for random access, the second minimum number, and the third minimum number, the second minimum number is the minimum number of preambles for a normal UE, and the third minimum number is the minimum number of preambles for non-contention access.

8. The method according to any one of claims 1 to 3, characterized in that, The method further includes: If the number of access conflicts for a regular UE in a period exceeds the second conflict threshold, the number of preambles for the regular UE will be increased by the third step size in the next period. If the number of access conflicts of a normal UE in a period is greater than 0 and less than or equal to the second conflict number threshold, and the network side detects the access signal of a normal UE, then the number of preambles of the normal UE will not be adjusted in the next period. If the number of access conflicts of a normal UE in a cycle is equal to 0, and the network side detects the access signal of a normal UE, then in the next cycle, the number of preambles of the normal UE will be reduced according to the fourth step size. If the network does not detect an access signal from a regular UE for K consecutive cycles, the number of preambles for the regular UE will be adjusted to the second minimum number in the next cycle, where K is a positive integer. Wherein, the second minimum quantity is the minimum number of preambles for a normal UE, and the initial number of preambles for a normal UE is the second minimum quantity.

9. The method according to claim 8, characterized in that, When the number of SSBs associated with each RO is greater than or equal to 1, the number of preambles of the ordinary UE is greater than or equal to the second minimum number and less than or equal to the third maximum number. The third maximum number is determined based on the total number of preambles for random access, the number of SSBs associated with one RO, the first minimum number, and the third minimum number. The first minimum number is the minimum number of preambles for low-capability UEs, and the third minimum number is the minimum number of preambles for non-contention access. or, When the number of SSBs associated with each RO is less than 1, the number of preambles of the ordinary UE is greater than or equal to the second minimum number and less than or equal to the fourth maximum number. The fourth maximum number is determined based on the total number of preambles for random access, the first minimum number, and the third minimum number. The first minimum number is the minimum number of preambles for low-capability UEs, and the third minimum number is the minimum number of preambles for non-contention access.

10. A method for random access resource allocation, characterized in that, Applied to the UE side, the method includes: Receive first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters: The first parameter indicates the number of preambles required for contention-based access by a normal UE. The second parameter indicates the start preamble of the low-capability UE; The third parameter indicates the number of preambles for a low-capability UE; The fourth parameter indicates the subset of ROs allocated to low-capability UEs; The one or more parameters are adjusted based on at least one of the following in each cycle: the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of accesses without signal.

11. The method according to claim 10, characterized in that, The preamble for contention-based access by a normal UE is located in a first region within the first preamble range, and the preamble for a low-capability UE is located in a second region within the first preamble range. The region within the first preamble range located between the first region and the second region is the preamble for non-contention-based access.

12. A random access resource allocation device, characterized in that, Applied to the network side, the device includes: The sending unit is configured to send first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters: The first parameter indicates the number of preambles required for contention-based access by a normal UE. The second parameter indicates the start preamble of the low-capability UE; The third parameter indicates the number of preambles for a low-capability UE; The fourth parameter indicates the subset of ROs allocated to low-capability UEs; The one or more parameters are adjusted based on at least one of the following in each cycle: the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of accesses without signal.

13. A random access resource allocation device, characterized in that, Applied to the UE side, the device includes: A receiving unit is configured to receive first system information, the first system information carrying a first configuration, the first configuration including one or more of the following parameters: The first parameter indicates the number of preambles required for contention-based access by a normal UE. The second parameter indicates the start preamble of the low-capability UE; The third parameter indicates the number of preambles for a low-capability UE; The fourth parameter indicates the subset of ROs allocated to low-capability UEs; The one or more parameters are adjusted based on at least one of the following in each cycle: the number of access conflicts for ordinary UEs, the number of access conflicts for low-capability UEs, and the number of accesses without signal.

14. A communication device, characterized in that, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 11.

15. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method as described in any one of claims 1 to 11.

16. A computer program product, characterized in that, It includes computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 11.

Images