A resource estimation method and related device
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SHANGHAI HUAWEI TECH CO LTD
- Filing Date
- 2021-08-31
- Publication Date
- 2026-06-05
Smart Images

Figure CN115734229B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communications, and more particularly to a resource estimation method and related equipment. Background Technology
[0002] When communication technologies are applied in business-to-business (B2B) scenarios, they need to meet the business requirements within a specific region. These requirements may include latency, speed, reliability, and other specifications.
[0003] To meet the above business needs, appropriate communication resources need to be planned. Currently, there is no accurate planning method that can configure sufficient and non-redundant communication resources for business needs. Summary of the Invention
[0004] This application provides a resource estimation method and related equipment for reasonably estimating and planning access network resources.
[0005] In a first aspect, embodiments of this application provide a resource estimation method, including:
[0006] Obtain communication system parameters and the service requirements of the target service; determine access network requirements based on the service requirements; determine first resource configuration information based on the communication system parameters and the access network requirements, wherein the first resource configuration information is information on the first access network resources allocated to the target service.
[0007] In this embodiment, the communication system parameters reflect the air interface resources that the communication system can provide; the service requirements of the target service reflect the air interface resources required by the service. Determining the first resource configuration information through the communication system parameters and service requirements is to configure resources based on the requirements and the capabilities of the communication system. This can provide appropriate air interface resources based on the target service, meeting service requirements while preventing excessive redundancy of communication resources.
[0008] In one possible implementation, the business requirements include at least one of the following: rate requirements, latency reliability requirements, and user concurrency requirements.
[0009] In one possible implementation, the communication system parameters include at least one of the following: operator, frequency band, bandwidth, time slot allocation, standard, and user's near, middle, and far location information.
[0010] The standard can be 4G, but it can also be 5G, time division duplexing (TDD), frequency division duplexing (FDD), etc. There are no restrictions here.
[0011] In one possible implementation, the step of determining access network requirements based on service needs may specifically include: determining access network requirements based on a service decomposition algorithm and service needs; and the step of determining first resource configuration information based on communication system parameters and access network requirements may specifically include: obtaining first resource configuration information based on access network requirements, communication system parameters, and a resource estimation algorithm.
[0012] In this embodiment, the first resource configuration information is determined by a business decomposition algorithm and a resource estimation method. The algorithm is scalable and highly flexible, which improves the flexibility of the method shown in this embodiment.
[0013] In one possible implementation, the step of obtaining the first resource configuration information based on access network requirements, communication system parameters, and a resource estimation method may specifically include: determining the scheduling period corresponding to the communication system parameters based on the communication system parameters; determining the packet loss rate (BLER) of the access network requirements based on the access network requirements; determining the inherent resources occupied by the access network based on the system signaling configuration and / or system symbol configuration; determining the spectral efficiency and the number of space layers based on the signal-to-interference-plus-noise ratio (SINR) and the packet loss rate (BLER); and obtaining the first resource configuration information based on the scheduling period, the packet loss rate (BLER), the inherent resources, the spectral efficiency, the number of space layers, and the resource estimation method.
[0014] The empty layer number refers to the number of multiple input multiple output (MIMO) layers. Optionally, the empty layer number can be the number of single-user MIMO (SU MIMO) layers or the number of multiple-user MIMO (MU MIMO) layers.
[0015] In one possible implementation, the step of determining the spectral efficiency and the number of empty layers based on the signal-to-interference-plus-noise ratio (SINR) and the packet loss rate (BLER) may specifically include: determining the order of the modulation and coding scheme (MCS) and the number of empty layers based on the SINR and the packet loss rate (BLER); and determining the spectral efficiency based on the order of the modulation and coding scheme.
[0016] In this embodiment of the application, the spectral efficiency can be determined by querying the RTT baseline using the MCS order and the number of empty layers.
[0017] In one possible implementation, the step of determining the modulation and coding scheme order based on the signal-to-interference-noise ratio (SINR) and packet loss rate (BLER) may specifically include: querying a modulation and coding scheme order-BLER level table based on the SINR to determine the order of the modulation and coding scheme; the MCS-BLER level table includes BLER level entries corresponding to the target level; the target level includes 10... -2 Level, 10 -3 Level, 10 -4 Level, and 10 -n At least one of the grades, where n≥6.
[0018] In this application embodiment, the MCS order-BLER gradation table is also called the MCS baseline, which currently only has 10. -1 Level and 10 -5 The embodiments of this application extend the range of BLER levels to which the MCS baseline applies.
[0019] In one possible implementation, the service requirements include the requirements for target services within the target area; the first resource allocation information includes: the number of base stations allocated to the target services within the target area.
[0020] In this embodiment of the application, the number of base stations allocated to the target service within the target area is determined. Then, the target service within the target area can be provided with sufficient and non-redundant access network resources through this number of base stations.
[0021] In one possible implementation, the service requirements include the requirements of the target service within the target cell; the first resource allocation information includes: the proportion of air interface resources allocated to the target service within the target cell.
[0022] In this application, the target service within the target cell is a slice service, which serves as the unit for resource allocation within the cell. The method described in this application allocates appropriate access network resources for the slice within the cell, ensuring the smooth operation of services within the slice.
[0023] In one possible implementation, after determining the first resource configuration information, the method further includes: determining the current air interface quality and / or the number of RBs, where the number of RBs represents the amount of scheduling resources used by a single network device to provide services for the target service; and determining second resource configuration information based on communication system parameters, access network requirements, and the air interface quality and / or the number of RBs, where the second resource configuration information is information about the second access network resources allocated to the target service.
[0024] In this embodiment, air interface quality and / or RB count reflect the communication status of the network device providing access network resources for the target service. After determining the first resource configuration information, if a suitable communication status cannot be guaranteed based on the first resource configuration information, the resource allocation of the access network is adjusted according to the communication status. This can make the allocated access network resources more suitable for the actual access network status, ensuring the normal operation of the target service.
[0025] In one possible implementation, after determining the first resource configuration information, the method further includes: sending the first resource configuration information to a network device, wherein the first resource configuration information is used by the network device to provide first access network resources for the target service.
[0026] In this embodiment, resource estimation and allocation are performed by the network management device, and the allocation result (first resource configuration information) is sent to the network device. The network device only needs to provide access network resources for the target service based on the first resource configuration information, without having to determine the configuration of access network resources through other calculations, thus saving the computing resources of the network device.
[0027] In one possible implementation, after determining the first resource configuration information, the method further includes: providing first access network resources for the target service based on the first resource configuration information.
[0028] In this embodiment, the estimation and allocation of access network resources, as well as the action of providing access network resources for the target service, are all implemented by the network device. The network device does not need to obtain the allocation result (first resource configuration information) from other devices, thereby reducing the latency of providing access network resources for the target service and improving efficiency.
[0029] Secondly, embodiments of this application provide a network management device, including a processor and a memory, wherein the processor and the memory are coupled.
[0030] Memory, used to store programs;
[0031] A processor for executing a program in memory, causing the processor to perform the data processing method described in the first aspect.
[0032] Thirdly, embodiments of this application provide a network device, including a processor and a memory, wherein the processor is coupled to the memory;
[0033] Memory, used to store programs;
[0034] A processor for executing a program in memory, causing the processor to perform the data processing method described in the first aspect.
[0035] Fourthly, embodiments of this application provide a chip including at least one processor and an interface;
[0036] An interface is used to provide program instructions or data to at least one processor;
[0037] At least one processor is used to execute the program instructions to implement the method described in the first aspect.
[0038] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed, implements the method described in the first aspect.
[0039] In a sixth aspect, embodiments of this application provide a computer program product comprising: computer program code, which, when executed, implements the method described in the first aspect.
[0040] The beneficial effects of aspects two through six are described in aspect one and will not be repeated here. Attached Figure Description
[0041] Figure 1 This is a schematic diagram illustrating an application scenario of the resource estimation method provided in the embodiments of this application;
[0042] Figure 2 A schematic diagram of a network architecture for the resource estimation method provided in the embodiments of this application;
[0043] Figure 3 A flowchart illustrating the resource estimation method provided in this application embodiment;
[0044] Figure 4 A schematic diagram of the resource estimation method provided in the embodiments of this application;
[0045] Figure 5 Another network architecture diagram for the resource estimation method provided in the embodiments of this application;
[0046] Figure 6 A schematic diagram of the network management device provided in the embodiments of this application;
[0047] Figure 7 A schematic diagram of the structure of a network device provided in an embodiment of this application;
[0048] Figure 8 This is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation
[0049] like Figure 1 As shown, Figure 1This diagram illustrates a possible application scenario applicable to an embodiment of this application, including a terminal device 110 and an access network device 120. The terminal device 110 and the access network device 120 can communicate to transmit data.
[0050] Optional, in Figure 1 The network architecture shown may also include a core network device 130. Terminal device 110 can connect wirelessly to access network device 120, and access network device 120 can connect to core network device 130 via wired or wireless means. Core network device 130 and access network device 120 can be independent and different physical devices, or they can be the same physical device integrating all or part of the logical functions of core network device 130 and access network device 120.
[0051] It should be noted that, in Figure 1 In the network architecture shown, the terminal device 110 can be fixed or movable, without limitation. Figure 1 The network architecture shown may also include other network devices, such as wireless relay devices and wireless backhaul devices, without limitation. Figure 1 In the architecture shown, there is no limit to the number of terminal devices, access network devices, and core network devices.
[0052] The technical solutions in this application can be applied to various communication systems, such as Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, and future mobile communication systems.
[0053] The following explanations of some terms or nouns used in this application are also part of the invention content.
[0054] I. Terminal equipment.
[0055] A terminal device, also known as a user equipment (UE), is a device with wireless transceiver capabilities. Terminal devices can be deployed on land, including indoors or outdoors; on water (such as ships); and in the air (e.g., on airplanes, drones, balloons, and satellites). These terminal devices can be mobile phones, tablets, personal digital assistants (PDAs), computers with wireless transceiver capabilities, virtual reality terminal devices, augmented reality terminal devices, wireless terminal devices in industrial control, wireless terminal devices in telemedicine, wireless terminal devices in smart grids, wireless terminal devices in smart cities, and wireless terminal devices in smart homes. Terminal devices can be fixed or mobile. This application does not limit this.
[0056] II. Network Equipment
[0057] Network equipment can be access network equipment, also known as radio access network (RAN) equipment, which is a device that provides wireless communication functions for terminal devices. Access network equipment includes, but is not limited to: next-generation node B (gNB), evolved node B (eNB), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP) in 5G, base stations in future mobile communication systems, or access points in WiFi systems. Access network equipment can also be radio controllers, centralized units (CU), and / or distributed units (DU) in cloud radio access network (CRAN) scenarios, or network equipment can be relay stations, vehicle-mounted equipment, and network equipment in future evolved PLMN networks.
[0058] The terminal device can communicate with multiple access network devices using different technologies. For example, the terminal device can communicate with access network devices supporting long-term evolution (LTE), access network devices supporting 5G, or simultaneously with both LTE-enabled and 5G-enabled access network devices. This application's embodiments are not limited to these specific examples.
[0059] In some B2B scenarios, such as industrial parks and intelligent orchard bases, users have raised Service Level Agreement (SLA) requirements for communication quality within the scenario area. An SLA is a mutually agreed-upon agreement between a communication service provider and a communication user. This agreement defines the types of services that the communication service provider provides to the communication user, the quality of service, and the service provider's commitment to ensuring the performance and reliability of the service.
[0060] For example, in different scenarios, there are SLA requirements as shown in Table 1 below:
[0061] Table 1
[0062]
[0063] In these scenarios, sufficient communication resources are required to meet SLA requirements. When constructing access networks for campuses, public networks, etc., it is necessary to estimate the required communication resources based on SLA requirements. In this embodiment, SLA requirements are also referred to as service requirements.
[0064] Currently, there is no accurate communication resource estimation scheme that can allocate sufficient and non-redundant communication resources to meet business needs.
[0065] like Figure 2 As shown, this application embodiment provides a network architecture, including a network management device and an access network device. The access network device can be... Figure 1 The access network device 120 is used to provide access network resources for terminal devices of the target service. The network management device includes a service requirement decomposition module and a resource estimation module, used to estimate and allocate access network resources based on the service requirements of the target service and the communication system parameters of the access network device. Optionally, the architecture may also include a user interface for the network management device to obtain the service requirements of the target service and the communication system parameters of the access network device.
[0066] Optionally, the network management device can be an operation support system (OSS). It can also be other devices besides OSS, such as a network management server, etc., without limitation. The following description uses OSS as the network management device to illustrate the method of this application embodiment, and does not constitute a limitation on the network management device.
[0067] like Figure 3 As shown, based on Figure 2 The architecture shown in this application provides a resource estimation method, which can be executed by a network management device or by a chip within the network management device. The following explanation uses an OSS (Optical Service Optimization System) network management device as an example. Figure 3The method shown may include the following operations:
[0068] 301. Obtain communication system parameters and the business requirements of the target service.
[0069] OSS obtains communication system parameters, which represent the parameters of the communication resources that the access network equipment can provide. Optionally, the network management equipment can obtain the communication system parameters from the user interface through the communication system parameter table shown in Table 2. The table header contains descriptions of the items included in the table, and the instructions are used to guide the user in filling in the corresponding table items.
[0070] Table 2
[0071]
[0072] It is worth noting that Table 2 is only an example of a communication system parameter table, and the table may include more or less information, which is not limited here.
[0073] It is worth noting that, in addition to the user interface, network management devices can also obtain communication system parameters through other means, such as human-machine interfaces and machine-to-machine interfaces, which are not limited here.
[0074] Optionally, the content in the table entries can be pre-configured by the operator. Users only need to select one or more access network devices from different configurations. OSS obtains the user's access network device selection result and can then know the communication system parameters of the access network device selected by the user based on the parameters pre-configured by the operator.
[0075] Communication system parameters can include network performance baselines, as shown in Table 3. These baselines represent the signal-to-interference-plus-noise ratio (SINR) ranges for far, medium, near, and excellent points. Based on the SINR values, the ranges of excellent, near, medium, and far points near the access network equipment can be distinguished using the network performance baselines.
[0076] Table 3
[0077]
[0078] Optionally, the network performance baseline can also represent the range of reference signal receiving power (RSRP) at far, medium, and far points. Based on the RSRP value, the range of the best point, near point, medium point, and far point near the access network equipment can be distinguished. This is not limited here.
[0079] Optionally, the RSRP and / or SINR mentioned above can be the RSRP and / or SINR of the synchronization signal and PBCH block (SSB), which is not limited here.
[0080] The network performance baseline defines the range of excellent near, mid, and far points near the access network device. Based on the network performance baseline, the range of excellent near, mid, and far points near the access network device can be tested, and the division of this range can be presented to the user. The user can determine the ratio of near, far, and far points in Table 4 below based on the actual location of the terminal device.
[0081] Optionally, in addition to the division of near, middle and far points, the embodiments of this application can also divide the area near the access network device in the form of a grid, the corresponding network performance baseline, and the method of determining the range based on the SINR value or RSRP value, as described in Table 3 above, which will not be repeated here.
[0082] OSS obtains the service requirements of the target service. Optionally, the network management device can obtain the service requirements from the user interface through the service requirements table shown in Table 4. The table header contains descriptions of the items included in the table, and the instructions are used to guide the user in filling in the corresponding table items.
[0083] Table 4
[0084]
[0085] It is worth noting that Table 4 shows a variety of items included in the business requirements. Depending on the application scenario, some or all of the specific parameters of the items can be filled in. For example, the example in Table 4 includes items such as customer name and UC number.
[0086] It is worth noting that Table 4 is just an example of a business requirements table, and the table may include more or less information, which is not limited here.
[0087] It is worth noting that, in addition to the user interface, network management devices can also obtain the business requirements of the target business through other means, such as human-machine interface, machine-to-machine interface, etc., which are not limited here.
[0088] Optionally, service requirements may include the requirements of target services within the target area. In this scenario, OSS is used to determine the number of base stations that need to be deployed within the target area to meet the requirements of the target services.
[0089] 302. Determine access network requirements based on business needs.
[0090] Service requirements are the demands of a target service on the entire communication network. OSS can use these service requirements to allocate them to different parts of the network, such as the access network, transmission network, and core network, thereby obtaining the access network requirements.
[0091] For example, taking the E2E latency requirements in Table 3 as an example, OSS can derive Formula 2 from the latency calculation formula (Formula 1), and then calculate the latency requirements of the access network portion based on Formula 2. Where T... E2E T represents the total end-to-end (E2E) delay. UE T represents the latency of the target service on the terminal device. AN T represents the latency of the target service in the access network. TN T represents the latency of the target service in the transmission network. CN This indicates the latency of the target service in the core network.
[0092] T E2E =T UE +T AN +T TN +T CN ...Formula 1
[0093]
[0094] In Formula 2, T 接入网 T represents the latency requirement in the access network requirements. 业务需求 This indicates the E2E latency requirement in business needs.
[0095] In this embodiment, Formula 2 is also referred to as the service decomposition algorithm. The service decomposition algorithm is used to decompose service requirements to obtain access network requirements. It is worth noting that Formula 2 is only an example of the service decomposition algorithm. The service decomposition algorithm can also be used to calculate other access network requirements, such as uplink transmission rate, downlink message length, etc., which are not limited here.
[0096] 303. Based on the communication system parameters and access network requirements, determine the first resource configuration information, which is the information of the first access network resource allocated to the target service.
[0097] The communication system parameters represent the access network resources that the access network equipment can provide, and the access network requirements represent the access network resources required to complete the target service. The OSS can determine the access network resources allocated to the target service based on the communication system parameters and the access network requirements, which is referred to as the first resource configuration information in this application embodiment.
[0098] Optionally, the first resource configuration information may include the number of cells. Since the number of cells that a base station can support is fixed, the number of cells depends on the number of base stations. Therefore, in this embodiment, determining the number of cells is equivalent to determining the number of base stations, and is not limited here.
[0099] Optionally, OSS can determine the initial configuration information using resource estimation algorithms. For example... Figure 4 As shown, OSS calculates the following four parameters based on communication system parameters and access network requirements: 1. Scheduling period; 2. Packet loss rate (BLER); 3. Inherent resources; 4. Spectrum efficiency and number of empty layers. These four parameters are described below:
[0100] 1. Scheduling cycle.
[0101] The OSS determines the scheduling period corresponding to the communication system parameters. Specifically, the OSS determines the number of time slots in the scheduling period based on the slot configuration in the communication system parameters; then it determines the length of the time slot based on the subcarrier spacing (SCS) in the communication system parameters; and finally, it determines the scheduling period by multiplying the number of time slots by the time slot length. For example, as shown in Table 2, with a slot configuration of 7:3 and a subcarrier spacing of 30kHz, the scheduling period is determined to be 7 + 3 = 10 slots, and the time slot length corresponding to the subcarrier spacing of 30kHz is determined to be 0.5ms, thus the scheduling period is determined to be 10 × 0.5ms = 5ms. Here, the scheduling period is the period for access network equipment scheduling.
[0102] Optionally, after determining the scheduling period, OSS can also determine the number of uplink and downlink scheduling units in each scheduling period based on the time slot allocation. For example, if the time slot allocation in Table 2 is 7:3, then 70% of the scheduling units in the scheduling period are determined to be uplink scheduling units and 30% of the scheduling units are determined to be downlink scheduling units.
[0103] The requirements for scheduling units vary depending on the specific access network requirements. For example, if the access network requirements include rate requirements, then the data rate of each scheduling unit (resource block, RB) is the user rate divided by (scheduling period × number of scheduling units). Alternatively, if the access network requirements include latency requirements, then it may be necessary for one scheduling unit (RB) to transmit all received data completely within a scheduling period. In this case, the data rate of each scheduling unit is the packet size multiplied by (scheduling period / packet interval).
[0104] 2. Packet loss rate (BLER).
[0105] OSS determines the packet loss rate (BLER) corresponding to the access network requirements.
[0106] The method for determining the packet loss rate (BLER) varies depending on the specific access network requirements. For example, if access network requirements include speed requirements, the corresponding BLER can be directly obtained based on those speed requirements.
[0107] Optionally, when the target business is the business of different users, the latency and reliability requirements of the corresponding application can be determined according to the different levels of the users, so as to provide corresponding BLER for different applications.
[0108] 3. Inherent resources.
[0109] The OSS determines the inherent resources occupied by the access network based on the system signaling configuration and / or system symbol configuration in the communication system parameters. The system signaling configuration includes configuration information for control signaling, and the system symbol configuration includes the symbol configuration in subframes other than data symbols, such as pilot symbol configuration. Both the system signaling configuration and the system symbol configuration are used to determine the inherent resources occupied by the transmission of other content in the access network besides service data transmission.
[0110] Optionally, after determining the inherent resources, OSS can also determine the minimum resource element (RE) number in each scheduling unit (RB) based on the inherent resources. Optionally, the number of REs in an RB can be taken as the number of subcarriers × the number of symbols - the number of symbols occupied by inherent resources.
[0111] 4. Spectral efficiency and number of empty layers.
[0112] OSS determines the spectral efficiency and number of empty layers based on the signal-to-interference-plus-noise ratio (SINR) and packet loss rate (BLER).
[0113] By using the network performance baseline, OSS can query the SINR value of terminal devices in the corresponding area (e.g., within the near point). Based on the SINR value of the terminal devices, OSS can query the MCS baseline and determine the modulation and coding scheme (MCS) order. OSS can also determine the number of empty layers based on the antenna configuration and user location in the communication system parameters. Then, based on the determined MCS order and number of empty layers, OSS can query the RTT baseline and determine the corresponding spectral efficiency.
[0114] To determine spectral efficiency and the number of empty layers, the following two baselines need to be established in advance:
[0115] a) MCS selection baseline.
[0116] For example, the BLER level is 10.-1 The baseline for MCS selection at each level is shown in Table 5:
[0117] Table 5
[0118]
[0119] For different packet loss rates (reliability) BLER levels, different MCS selection baselines are constructed. For example, BLER can be 10. -2 Level, 10 -3 Level, 10 -4 Level, and 10 -n At least one of the grades, where n≥6. By constructing MCS order selection baselines for different BLER grades, the accuracy and efficiency of MCS order selection prediction can be effectively improved.
[0120] b) RTT demodulation baseline.
[0121] For example, the RTT demodulation baseline can be shown in Table 6:
[0122] Table 6
[0123]
[0124] Different business scenarios (industrial manufacturing, ports, etc.) have different baselines for BLER. Therefore, in this embodiment, the RTT demodulation baseline queried for different scenarios is different, which can improve the accuracy of the prediction.
[0125] Optionally, RTT demodulation baselines for different industries can be constructed through on-site channel characteristic measurements and simulations.
[0126] like Figure 4 As shown, once the scheduling period, packet loss rate (BLER), inherent resources, spectral efficiency, and number of empty layers are determined, these four parameters can be input into the resource estimation algorithm to calculate the first resource configuration information.
[0127] Optionally, the business scenario can also be determined through resource estimation methods, and the business scenario can be determined according to business needs.
[0128] In different application scenarios, business requirements vary, resulting in different initial resource configuration information. The following explanation will use the scenario of calculating the number of cells (base stations) and reserving slice resources as an example:
[0129] It is worth noting that there can be multiple target services. Multiple target services can be assigned to multiple base stations or cells for communication, or they can be assigned to the same base station or cell for communication. There is no limitation here.
[0130] 1) Calculation scenario for the number of cells (base stations).
[0131] For example, when the service requirements include the requirements of the target service within the target area, the first resource configuration information includes the number of base stations allocated to the target service within the target area.
[0132] OSS divides the target area into several regions based on base station coverage or service deployment areas. The input region's CASE requirements are then used to define service requirements, with each industry corresponding to one CASE.
[0133] (a) Number of cells required for OSS latency calculation: The number of available RBs in a scheduling unit is equal to the total number of RBs in the scheduling unit minus the number of RBs in the channel overhead (inherent resources). For details, please refer to the explanation of inherent resources, which will not be repeated here.
[0134] Optionally, for scenarios where latency requirements are not high, The value of X is determined based on factors such as the product's latency handling capabilities.
[0135] (b) When allocating scheduling resources for cells in OSS, scheduling resources can be allocated to services requiring latency first, and then the unallocated scheduling resources in the cells can be allocated to non-latency services. Therefore, the resources allocated to non-latency services do not need to increase the number of cells. Optionally, these scheduling resources allocated to non-latency services can be used to meet rate requirements.
[0136] The number of RBs allocated to non-latency services = the total number of RBs required for the target service rate - the number of latency cells × (the number of scheduling units in the scheduling cycle - the number of scheduling units occupied by latency) × the number of RBs available in each scheduling unit; where the target service can be a single-user service or a multi-user service, there is no limitation here.
[0137] (c) Recalculate the number of cells with rate requirements:
[0138]
[0139] The number of remaining RBs required for the target service rate is the number of services that have not been allocated resources after allocating scheduling resources in the delay cell for non-delay services in step (b).
[0140] (d) Next, calculate the number of cells within the target area:
[0141] The number of cells in the target area = the number of cells required for latency + the number of cells required for speed;
[0142] During the calculation process, the number of cells is rounded up; and the number of cells is calculated separately in the uplink and downlink directions, and the maximum value between the uplink and downlink calculation results is taken in the end.
[0143] If the target business needs to deploy terminal devices in more than one region, it is necessary to calculate the number of cells required in multiple regions, and add these cell numbers together to obtain the total number of cells in the region.
[0144] 2) Slice resource reservation scenario.
[0145] For example, when the service requirements include the requirements of the target service within the target cell, specifically the requirements of the target service allocated to the same slice within the target cell, the first resource allocation information includes the proportion of air interface resources allocated to the target service within the target cell.
[0146] OSS needs to be planned in advance, the CASE requirements of a single cell need to be determined, and then resources need to be reserved on a cell-by-cell basis.
[0147] The proportion reserved for slicing can be determined by multiplying the reserved proportion with different redundancy coefficients, based on the value strategy of each input parameter in the resource and estimation method and the different application scenarios of the slice. This can determine the average, minimum or maximum value of the reserved proportion.
[0148]
[0149] The total number of redundancy blocks (RBs) in the target service scheduling unit within the slice can be obtained by referring to a table based on the channel bandwidth and subcarrier spacing, referencing the 3GPP standard. The target service can be a single-user service or a multi-user service; no specific limitation is made here.
[0150] Optionally, the reservation ratio can be calculated and reserved separately for the uplink and downlink directions.
[0151] Optionally, the method in this application embodiment can also achieve the allocation of slice resources within the cell while determining the number of base stations in the target area.
[0152] It is worth noting that the cell (base station) number calculation and slice resource reservation scenarios are only examples of application scenarios for the embodiments of this application. Based on the architecture and method of the embodiments of this application, access network configuration can also be determined in other scenarios, which are not limited here.
[0153] Optionally, after step 304, the OSS can transmit the first resource configuration information to the access network device. The access network device receives the first resource configuration information and provides access network resources to the terminal device of the target service according to the first resource configuration information.
[0154] 304. Determine the current air interface quality and / or RB number.
[0155] Optionally, after step 303, OSS may also receive the current air interface quality and / or RB number from the access network device; wherein, the RB number is the number of scheduling resources used by a single network device (access network device) providing services for the target service.
[0156] 305. Based on the current air interface quality and / or number of RBs, determine the second resource configuration information, which is the information of the second access network resources allocated to the target service.
[0157] The current air interface quality and / or RB count reflect the communication status of the access network equipment that provides access network resources for the target service. Based on the current air interface quality and / or RB count, it can be determined whether the access network equipment currently meets the service requirements of the target service. If not, the access network resources allocated to the target service are re-planned to obtain the second resource configuration information.
[0158] For example, if the number of base stations (RBs) allocated to the target service is 300, but the current number of RBs is 280, then it is necessary to reallocate base stations or cells to the target service to provide more RB resources. Or, if the terminal of the target service is allocated in the area of the midpoint of the base station, but the air interface quality in that area does not meet the air interface quality requirements of the midpoint (e.g., the SINR value is too low), then there may be phenomena such as excessive packet loss rate. Therefore, it is necessary to re-divide the near, medium and far ranges for the target service and then reallocate access network resources.
[0159] It is worth noting that steps 304 and 305 are optional steps, and steps 304 and 305 can also be omitted; there is no restriction here.
[0160] In this embodiment of the application, the information (supply) of access network resources that the access network equipment can provide is determined by the communication system resources, and the information (demand) of access network resources required by the target service is determined by the service requirements. Thus, based on the supply and demand, access network resources are reasonably allocated, avoiding insufficient or excessive resource allocation.
[0161] Optionally, in the embodiments of this application, it is also possible to... Figure 2 or Figure 3 The functions of the network management equipment are integrated into the access network equipment. For example... Figure 5 As shown, Figure 2 The service decomposition module, resource estimation (resource configuration module), and status monitoring module on the central network management device are all integrated into the access network device. Figure 5 The network architecture can achieve Figure 3 The process shown, in which, Figure 5 In the architecture shown, Figure 3 The execution entities for each step are all access network devices, which will not be elaborated here.
[0162] The method provided by the embodiments of this application has been described above. The device used to implement the method is described below.
[0163] Please see Figure 6 This application provides a network management device 600, which includes a processor 601 and a memory 602, wherein the processor 601 and the memory 602 are coupled.
[0164] Memory 602 is used to store programs;
[0165] Processor 601 is configured to execute the program in memory 602, causing processor 601 to perform the aforementioned... Figures 3 to 4 The steps performed by the network management device in any embodiment are used to implement the corresponding resource estimation method.
[0166] Please see Figure 7 This application provides a network device 700, including a processor 701 and a memory 702, wherein the processor 701 is coupled to the memory 702;
[0167] Memory 702 is used to store programs;
[0168] Processor 701 is configured to execute the program in memory 702, causing processor 701 to perform the aforementioned... Figures 3 to 4 The steps performed by the network device in any of the embodiments enable the corresponding resource estimation method.
[0169] Please see Figure 8 This application provides a chip 800, which includes at least one processor 801 and a communication interface 802. The communication interface 802 and the at least one processor 801 are interconnected via a line. The at least one processor 801 is used to run computer programs or instructions to perform the aforementioned functions. Figures 3 to 4 Resource estimation method corresponding to any of the embodiments.
[0170] The communication interface 802 in the chip can be an input / output interface, pins, or circuits.
[0171] In one possible implementation, the chip 800 described above in this application further includes at least one memory 803, which stores instructions. The memory 803 can be an internal storage unit of the chip, such as a register, cache, etc., or it can be a storage unit of the chip itself (e.g., read-only memory, random access memory, etc.).
[0172] 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.
[0173] 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 an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.
[0174] 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.
[0175] Furthermore, 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. The integrated unit can be implemented in hardware or as a software functional unit.
[0176] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it 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 all or part 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.
Claims
1. A resource estimation method, characterized in that, include: Obtain communication system parameters and the business requirements of the target service; Based on the service decomposition algorithm and the aforementioned service requirements, the access network requirements are determined; Based on the communication system parameters, determine the scheduling period corresponding to the communication system parameters; Based on the access network requirements, determine the packet loss rate (BLER) of the access network requirements; Based on the system signaling configuration and / or system symbol configuration, determine the inherent resources occupied by the access network; The spectral efficiency and number of empty layers are determined based on the signal-to-interference-plus-noise ratio (SINR) and the packet loss rate (BLER). Based on the scheduling period, the packet loss rate (BLER), the inherent resources, the spectrum efficiency, the number of empty layers, and the resource estimation method, the first resource configuration information is obtained, which is the information of the first access network resources allocated to the target service.
2. The method according to claim 1, characterized in that, The business requirements include: At least one of the following: rate requirements, latency and reliability requirements, and user concurrency requirements.
3. The method according to claim 1, characterized in that, The communication system parameters include: At least one of the following: operator, frequency band, bandwidth, time slot allocation, standard, and user location information.
4. The method according to claim 1, characterized in that, The determination of spectral efficiency and number of empty layers based on signal-to-interference-plus-noise ratio (SINR) and packet loss rate (BLER) includes: The modulation and coding scheme order and the number of empty layers are determined based on the signal-to-interference-plus-noise ratio (SINR) and the packet loss rate (BLER). The spectral efficiency is determined based on the order of the modulation and coding scheme.
5. The method according to claim 4, characterized in that, Based on the signal-to-interference-plus-noise ratio (SINR) and the packet loss rate (BLER), the modulation and coding scheme order is determined, including: Based on the signal-to-interference-noise ratio (SINR), consult the modulation and coding scheme (MCS) order-packet loss rate (BLER) level table to determine the MCS order; The MCS order-BLER grading table includes BLER grading entries corresponding to the target grading; the target grading includes 10. -2 Level, 10 -3 Level, 10 -4 Level, and 10 -n At least one of the grades, where n≥6.
6. The method according to any one of claims 1 to 5, characterized in that, The business requirements include the requirements of the target business within the target area; The first resource configuration information includes: the number of base stations allocated to the target service within the target area.
7. The method according to any one of claims 1 to 5, characterized in that, The service requirements include the requirements of the target services within the target cell; The first resource configuration information includes: the proportion of air interface resources allocated to the target service within the target cell.
8. The method according to any one of claims 1 to 5, characterized in that, After determining the first resource configuration information, the method further includes: Determine the current air interface quality and / or the number of redundancy blocks (RBs), where the number of RBs represents the amount of scheduling resources used by a single network device to provide services for the target service; Based on the communication system parameters, the access network requirements, the air interface quality, and / or the number of RBs, second resource configuration information is determined, which is information about the second access network resources allocated to the target service.
9. The method according to any one of claims 1 to 5, characterized in that, After determining the first resource configuration information, the method further includes: The first resource configuration information is sent to the network device, and the first resource configuration information is used by the network device to provide the first access network resources for the target service.
10. The method according to any one of claims 1 to 5, characterized in that, After determining the first resource configuration information, the method further includes: Based on the first resource configuration information, the first access network resources are provided for the target service.
11. A network management device, characterized in that, It includes a processor and a memory, wherein the processor is coupled to the memory; The memory is used to store programs; The processor is configured to execute a program in the memory, such that the processor performs the method as described in any one of claims 1 to 10.
12. A network device, characterized in that, It includes a processor and a memory, wherein the processor is coupled to the memory; The memory is used to store programs; The processor is configured to execute a program in the memory, such that the processor performs the method as described in any one of claims 1 to 10.
13. A chip, characterized in that, Includes at least one processor and interface; The interface is used to provide program instructions or data to the at least one processor; The at least one processor is used to execute the program instructions to implement the method as described in any one of claims 1 to 10.
14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, implements the method as described in any one of claims 1 to 10.
15. A computer program product, the computer program product comprising: Computer program code, when the computer program code is run, implements the method as described in any one of claims 1 to 10.