Auxiliary carrier configuration processing method, device and equipment

Abstract

The present invention provides a method, apparatus, and device for secondary carrier configuration and processing, relating to the field of communications technology. The method comprises: obtaining service reliability requirement information; determining the number of carriers required for the service based on the reliability requirement information; and, if the number of carriers required for the service differs from the current number of carriers, performing one of the following actions: configuring and activating the corresponding secondary carrier; deactivating the corresponding secondary carrier; or deconfiguring the corresponding secondary carrier. The present invention addresses the problem that existing secondary carrier configurations cannot meet service reliability requirements.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method, device and equipment for processing auxiliary carrier configuration. Background Art

[0002] To fully utilize operators' spectrum resources, various equipment manufacturers have introduced multi-carrier technologies. In mobile communication systems, downlink power and code channels are relatively precious resources. Fully and rationally utilizing these resources is crucial to improving system capacity and performance without increasing costs. Given a given total transmit power, a power amplifier typically uses two to four carriers, which can function as both primary and secondary carriers. Due to varying carrier loads, some carriers require less power and code channels, while others require more.

[0003] Current technical solutions configure secondary carriers through blind pairing or based on terminal measurement results, and activate them based on rate requirements. However, for some services, such as industrial control services, the reliability requirements of the services cannot be met. Summary of the Invention

[0004] The object of the present invention is to provide a method, apparatus and device for processing auxiliary carrier configuration to meet the reliability requirements of services.

[0005] To achieve the above-mentioned object, an embodiment of the present invention provides a secondary carrier configuration processing method, which is executed by a network-side device and includes:

[0006] Obtain business reliability requirement information;

[0007] determining the number of carriers required for the service based on the reliability requirement information;

[0008] If the number of carriers required by the service is different from the current number of carriers, perform one of the following actions:

[0009] Configure and activate the corresponding secondary carrier;

[0010] Deactivate the corresponding secondary carrier;

[0011] To configure the corresponding secondary carrier.

[0012] Optionally, obtaining the reliability requirement information of the service includes at least one of the following methods:

[0013] Obtain reliability requirement information input via dedicated network operation equipment;

[0014] Obtain reliability requirement information input via local portal equipment;

[0015] Obtain the reliability requirement information in the service quality QoS information of the business contract.

[0016] Optionally, determining the number of carriers required for the service according to the reliability requirement information includes:

[0017] Based on the current network configuration, service characteristics, and signal quality, the number of carriers corresponding to the reliability requirement information is determined.

[0018] Optionally, the determining, based on the current network configuration, service characteristics, and signal quality, the number of carriers corresponding to the reliability requirement information includes:

[0019] In the service reliability table, query the number of carriers corresponding to the reliability requirement information under the current network configuration, service characteristics and signal quality;

[0020] The service reliability table records the relationship between network configuration, service characteristics, signal quality, reliability information and the number of carriers.

[0021] Optionally, the method further includes:

[0022] If the number of carriers corresponding to the reliability requirement information is not found in the service reliability table, the output number of carriers is obtained through the established target model with the reliability requirement information and the current network configuration, service characteristics and signal quality as input.

[0023] Optionally, the service reliability table is obtained by performing simulation evaluation based on preset simulation parameters; or,

[0024] The service reliability table is obtained by statistics based on target data; or

[0025] The service reliability table is obtained through actual service measurement; or,

[0026] The service reliability table is obtained through a target model trained based on sample data.

[0027] Optionally, the service reliability table is grouped by signal quality and / or service characteristics.

[0028] Optionally, after configuring and activating the corresponding secondary carrier, the method further includes:

[0029] Dynamically monitor the reliability information of current services;

[0030] If the monitoring result indicates that the reliability requirement information is not met, the process returns to the step of determining the number of carriers required for the service based on the reliability requirement information.

[0031] Optionally, the method further includes:

[0032] When the corresponding secondary carrier is configured and activated, the packet data convergence protocol PDCP replication function is correspondingly enabled.

[0033] Optionally, the network side device supports reliability information statistics at QoS flow level, 5QI level, slice level, and 5QI+slice level.

[0034] Optionally, the reliability requirement information includes at least one of the following:

[0035] reliability;

[0036] Delay;

[0037] Packet loss rate;

[0038] Packet error rate;

[0039] Bit error rate;

[0040] Block error rate.

[0041] Optionally, the service characteristics are obtained in at least one of the following ways:

[0042] Obtaining service characteristics input via dedicated network operation equipment;

[0043] Obtaining business characteristics input via a local portal device;

[0044] Parse the target item;

[0045] Get the business characteristics entered by the user.

[0046] To achieve the above-mentioned objective, an embodiment of the present invention provides a secondary carrier configuration processing device, including:

[0047] Acquisition module, used to obtain reliability requirement information of the business;

[0048] A determination module, configured to determine the number of carriers required for the service based on the reliability requirement information;

[0049] The first processing module is configured to, when the number of carriers required by the service is different from the current number of carriers, perform one of the following actions:

[0050] Configure and activate the corresponding secondary carrier;

[0051] Deactivate the corresponding secondary carrier;

[0052] To configure the corresponding secondary carrier.

[0053] Optionally, the acquisition module is further configured to:

[0054] Obtain reliability requirement information input via dedicated network operation equipment;

[0055] Obtain reliability requirement information input via local portal equipment;

[0056] Obtain the reliability requirement information in the service quality QoS information of the business contract.

[0057] Optionally, the determining module is further configured to:

[0058] Based on the current network configuration, service characteristics, and signal quality, the number of carriers corresponding to the reliability requirement information is determined.

[0059] Optionally, the determining module includes:

[0060] A query submodule, configured to query the service reliability table for the number of carriers corresponding to the reliability requirement information under the current network configuration, service characteristics, and signal quality;

[0061] The service reliability table records the relationship between network configuration, service characteristics, signal quality, reliability information and the number of carriers.

[0062] Optionally, the determining module further includes:

[0063] A processing submodule is used to obtain the output number of carriers through the established target model, using the reliability requirement information and the current network configuration, service characteristics and signal quality as input, if the number of carriers corresponding to the reliability requirement information is not found in the service reliability table.

[0064] Optionally, the service reliability table is obtained by performing simulation evaluation based on preset simulation parameters; or,

[0065] The service reliability table is obtained by statistics based on target data; or

[0066] The service reliability table is obtained through actual service measurement; or,

[0067] The service reliability table is obtained through a target model trained based on sample data.

[0068] Optionally, the service reliability table is grouped by signal quality and / or service characteristics.

[0069] Optionally, the device further comprises:

[0070] Monitoring module, used to dynamically monitor the reliability information of current services;

[0071] The second processing module is configured to return to the step of determining the number of carriers required for the service according to the reliability requirement information if the monitoring result indicates that the reliability requirement information is not met.

[0072] Optionally, the device further comprises:

[0073] The third processing module is configured to enable a packet data convergence protocol (PDCP) replication function when configuring and activating a corresponding secondary carrier.

[0074] Optionally, the network side device supports reliability information statistics at QoS flow level, 5QI level, slice level, and 5QI+slice level.

[0075] Optionally, the reliability requirement information includes at least one of the following:

[0076] reliability;

[0077] Delay;

[0078] Packet loss rate;

[0079] Packet error rate;

[0080] Bit error rate;

[0081] Block error rate.

[0082] Optionally, the service characteristics are obtained in at least one of the following ways:

[0083] Obtaining service characteristics input via dedicated network operation equipment;

[0084] Obtaining business characteristics input via a local portal device;

[0085] Parse the target item;

[0086] Get the business characteristics entered by the user.

[0087] To achieve the above objectives, an embodiment of the present invention provides a network-side device, including a processor, wherein the processor is configured to:

[0088] Obtain business reliability requirement information;

[0089] determining the number of carriers required for the service based on the reliability requirement information;

[0090] If the number of carriers required by the service is different from the current number of carriers, perform one of the following actions:

[0091] Configure and activate the corresponding secondary carrier;

[0092] Deactivate the corresponding secondary carrier;

[0093] To configure the corresponding secondary carrier.

[0094] Optionally, the processor is further configured to:

[0095] Obtain reliability requirement information input via dedicated network operation equipment;

[0096] Obtain reliability requirement information input via local portal equipment;

[0097] Obtain the reliability requirement information in the service quality QoS information of the business contract.

[0098] Optionally, the processor is further configured to:

[0099] Based on the current network configuration, service characteristics, and signal quality, the number of carriers corresponding to the reliability requirement information is determined.

[0100] Optionally, the processor is further configured to:

[0101] In the service reliability table, query the number of carriers corresponding to the reliability requirement information under the current network configuration, service characteristics and signal quality;

[0102] The service reliability table records the relationship between network configuration, service characteristics, signal quality, reliability information and the number of carriers.

[0103] Optionally, the processor is further configured to:

[0104] If the number of carriers corresponding to the reliability requirement information is not found in the service reliability table, the output number of carriers is obtained through the established target model with the reliability requirement information and the current network configuration, service characteristics and signal quality as input.

[0105] Optionally, the service reliability table is obtained by performing simulation evaluation based on preset simulation parameters; or,

[0106] The service reliability table is obtained by statistics based on target data; or

[0107] The service reliability table is obtained through actual service measurement; or,

[0108] The service reliability table is obtained through a target model trained based on sample data.

[0109] Optionally, the service reliability table is grouped by signal quality and / or service characteristics.

[0110] Optionally, the processor is further configured to:

[0111] Dynamically monitor the reliability information of current services;

[0112] If the monitoring result indicates that the reliability requirement information is not met, the process returns to the step of determining the number of carriers required for the service based on the reliability requirement information.

[0113] Optionally, the processor is further configured to:

[0114] When the corresponding secondary carrier is configured and activated, the packet data convergence protocol PDCP replication function is correspondingly enabled.

[0115] Optionally, the network side device supports reliability information statistics at QoS flow level, 5QI level, slice level, and 5QI+slice level.

[0116] Optionally, the reliability requirement information includes at least one of the following:

[0117] reliability;

[0118] Delay;

[0119] Packet loss rate;

[0120] Packet error rate;

[0121] Bit error rate;

[0122] Block error rate.

[0123] Optionally, the service characteristics are obtained in at least one of the following ways:

[0124] Obtaining service characteristics input via dedicated network operation equipment;

[0125] Obtaining business characteristics input via a local portal device;

[0126] Parse the target item;

[0127] Get the business characteristics entered by the user.

[0128] To achieve the above-mentioned objectives, an embodiment of the present invention provides a network-side device, including a transceiver, a processor, a memory, and a program or instruction stored on the memory and executable on the processor; when the processor executes the program or instruction, the auxiliary carrier configuration processing method as described above is implemented.

[0129] To achieve the above object, an embodiment of the present invention provides a readable storage medium having a program or instruction stored thereon, which implements the steps in the above-mentioned secondary carrier configuration processing method when executed by a processor.

[0130] The beneficial effects of the above technical solution of the present invention are as follows:

[0131] The method of the embodiment of the present invention, after obtaining the reliability requirement information of the service, determines the number of carriers that can meet the requirements of the service, and then performs one of the following actions when the determined number of carriers is different from the current number of carriers: configuring and activating the corresponding auxiliary carrier; deactivating the corresponding auxiliary carrier; deconfiguring the corresponding auxiliary carrier to meet the current service reliability requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0132] Figure 1 This is a flowchart of a secondary carrier configuration processing method according to an embodiment of the present invention;

[0133] Figure 2 To realize the system architecture of industry business;

[0134] Figure 3 This is a structural diagram of a secondary carrier configuration processing device according to an embodiment of the present invention;

[0135] Figure 4 This is a structural diagram of a network-side device according to an embodiment of the present invention;

[0136] Figure 5 This is a structural diagram of a network-side device according to another embodiment of the present invention. DETAILED DESCRIPTION

[0137] In order to make the technical problems, technical solutions and advantages to be solved by the present invention clearer, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0138] It should be understood that references throughout this specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present invention. Therefore, the appearances of "in one embodiment" or "in an embodiment" throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0139] In various embodiments of the present invention, it should be understood that the size of the serial numbers of the following processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0140] Additionally, the terms "system" and "network" are often used interchangeably herein.

[0141] In the embodiments provided herein, it should be understood that "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A; B can also be determined based on A and / or other information.

[0142] like Figure 1 As shown, a secondary carrier configuration processing method according to an embodiment of the present invention is executed by a network-side device, including:

[0143] Step 101: Obtaining service reliability requirement information;

[0144] Step 102: determining the number of carriers required for the service based on the reliability requirement information;

[0145] Step 103: When the number of carriers required by the service is different from the current number of carriers, perform one of the following actions: configure and activate the corresponding secondary carrier; deactivate the corresponding secondary carrier; or deconfigure the corresponding secondary carrier.

[0146] According to the above steps, in the method of the embodiment of the present invention, after obtaining the reliability requirement information of the service, the network-side device determines the number of carriers that can meet the requirements of the service, and then, when the determined number of carriers is different from the current number of carriers, performs one of the following actions: configuring and activating the corresponding auxiliary carrier; deactivating the corresponding auxiliary carrier; deconfiguring the corresponding auxiliary carrier to meet the current service reliability requirement.

[0147] In this embodiment, it should be known that the network side device may be a base station or other network element devices connected to the base station, which will not be listed here one by one.

[0148] The number of carriers required for the service and the current number of carriers include the total number of carriers, that is, the sum of the numbers of primary carriers and secondary carriers.

[0149] The reliability requirement information is the reliability information corresponding to the reliability requirement of the service. The reliability information may include multiple pieces of information (indicators), and the reliability information is also called reliability indicator information. Optionally, the reliability requirement information includes at least one of the following:

[0150] Reliability; latency; packet loss rate; packet error rate; bit error rate; block error rate.

[0151] Of course, the reliability requirement information includes but is not limited to the above indicators.

[0152] Optionally, this embodiment further includes:

[0153] When the corresponding secondary carrier is configured and activated, the packet data convergence protocol PDCP replication function is correspondingly enabled.

[0154] That is, when the number of carriers N required for a service is greater than 1, in addition to configuring and activating the corresponding secondary carrier, the PDCP replication function may also be enabled to ensure that the service reliability meets the requirements.

[0155] Optionally, step 101 includes at least one of the following methods:

[0156] Obtain reliability requirement information input via dedicated network operation equipment;

[0157] Obtain reliability requirement information input via local portal equipment;

[0158] Obtain the reliability requirement information in the service quality QoS information of the business contract.

[0159] That is, Figure 2 In the system architecture shown, network-side equipment, such as a gNB, obtains service reliability requirement information. On the one hand, the reliability requirement information is input from private network operator equipment. This reliability information is transmitted to the gNB via the Communication Service Management Function (CSMF), Network Slice Management Function (NSMF), and Radio Access Network-Network Slice Subnet Management Function (RAN-NSSMF). This requires that reliability requirement information (e.g., reliability and latency) be added to the interfaces of each network element. On the other hand, the reliability requirement information is input from local portal equipment. This reliability information is transmitted to the gNB via local control equipment (e.g., radio network management). This requires that reliability requirement information (e.g., reliability and latency) be added to the interfaces of each network element. Alternatively, if a user subscribes to reliability requirement information in the corresponding QoS information during service subscription, the gNB can also obtain reliability requirement information in the QoS information, such as the packet error rate and service delay budget, and transmit it to the gNB via the core network.

[0160] Optionally, in this embodiment, step 102 includes:

[0161] Based on the current network configuration, service characteristics, and signal quality, the number of carriers corresponding to the reliability requirement information is determined.

[0162] Here, considering that the number of carriers required for the service determined by the reliability requirement information varies in different scenarios, the number of carriers corresponding to the reliability requirement information of the service will be determined based on the current network configuration, service characteristics and signal quality.

[0163] Network configuration primarily involves configuring various functional switches and parameters that affect latency or reliability, such as whether slot repetition is enabled, whether pre-scheduling is enabled, and the Scheduling Request (SR) period. Service characteristics include the size of service packets and the packet transmission interval. Signal quality includes the received signal power (RSRP) and signal-to-noise ratio (SINR) of the terminal signal.

[0164] Optionally, the service characteristics are obtained in at least one of the following ways:

[0165] Obtaining service characteristics input via dedicated network operation equipment;

[0166] Obtaining business characteristics input via a local portal device;

[0167] Parse the target item;

[0168] Get the business characteristics entered by the user.

[0169] Here, the target items include QOS information, BSR, scheduling information, inter-layer interaction information, IP packets, etc.

[0170] Then, the service characteristics can be input into the network side equipment through the dedicated network operation equipment or the local portal equipment, in the same process as the transmission of reliability requirement information; they can also be filled into the reliability table by manual input; they can also be obtained based on the network side equipment's BSR, scheduling information, inter-layer interaction information, IP unpacking, etc. Among them, the services with higher reliability requirements are generally industry services, and industry terminals generally only carry out a single service (such as status reporting) in a single direction (such as the uplink direction). Therefore, the network side equipment can obtain the service packet size from the amount of service to be transmitted in the BSR reported by the terminal (the actual service packet size needs to be obtained by subtracting the packet headers of the PDCP, RLC, SDAP layers), and obtain the service packet sending period according to the interval reported by the terminal BSR (not the period of the periodic BSR set by the network and the time configuration of the retransmission of the BSR, but the actual sending interval of the BSR); the network side equipment obtains the service packet size based on the scheduling information of each uplink or downlink (the actual service packet size needs to be obtained by subtracting the packet headers of the PDCP, RLC, SDAP layers). The service packet transmission interval is obtained based on the scheduled interval (obtained by subtracting the packet headers of the SDAP and MAC layers). The terminal transmits the service characteristics to the communication layer through inter-layer interaction between the application layer and the communication layer (such as the IP layer, PDCP layer, and MAC layer), and encapsulates them into the data packet of the corresponding communication layer (correspondingly, it is necessary to add relevant fields of the service characteristics to the packet header of the corresponding communication layer). The network-side device obtains the service packet size and packet transmission period by unpacking the IP packet, PDCP packet, or MAC packet. The network-side device can report the service characteristic information obtained through BSR, scheduling information, IP unpacking, etc. to the upper layer through inter-layer interaction for use in establishing and querying reliability tables.

[0171] Optionally, in this embodiment, determining the number of carriers corresponding to the reliability requirement information based on the current network configuration, service characteristics, and signal quality includes:

[0172] In the service reliability table, query the number of carriers corresponding to the reliability requirement information under the current network configuration, service characteristics and signal quality;

[0173] The service reliability table records the relationship between network configuration, service characteristics, signal quality, reliability information and the number of carriers.

[0174] In other words, the network-side device already has a service reliability table that records the relationship between network configuration, service characteristics, signal quality, reliability information, and the number of carriers. This allows users to query the service reliability table to obtain the number of carriers corresponding to the reliability requirements of the service under the current network configuration, service characteristics, and signal quality. In this way, configuring or activating secondary carriers based on this number of carriers will ensure that the service reliability requirements are met in the current scenario.

[0175] For example, the QoS contracted for industrial control services is a reliability of 99.999% with a latency of less than 10ms. When an industry terminal accesses the network to initiate an industrial control service, the core network obtains the contract information for the industrial control service from the Unified Data Management (UDM) entity, and obtains the reliability requirement information (packet error rate) of 99.999% and a service latency of 10ms. Industry customers enter the service packet size and packet sending interval into the network through the local portal, and transmit it to the base station through the local control equipment. Based on the packet size of the industrial control service (100Byte), the packet sending interval information (100ms), and the signal quality reported by the industrial control terminal (RSRP = -80dBm, SINR = 15dB), the base station queries the service reliability information that can be provided under different carrier numbers from the existing reliability grid table (service reliability table). The query results are as follows:

[0176] Table 1

[0177]

[0178] Table 2

[0179]

[0180] However, since activating one carrier in Table 1 achieves a reliability of 99.99%, which cannot meet the 99.999% reliability requirement for industrial control services, activating two carriers in Table 2 achieves a reliability of 99.999%. Therefore, the number of carriers corresponding to the reliability requirement for industrial control services is two. Therefore, the base station can configure and activate a secondary carrier for terminals in this industry. Of course, the PDCP double replication function can also be enabled.

[0181] Optionally, in this embodiment, the service reliability table is obtained by performing simulation evaluation based on preset simulation parameters; or,

[0182] The service reliability table is obtained by statistics based on target data; or

[0183] The service reliability table is obtained through actual service measurement; or,

[0184] The service reliability table is obtained through a target model trained based on sample data.

[0185] Among them, in the method (simulation method) of obtaining a service reliability table by performing simulation evaluation based on preset simulation parameters, the preset simulation parameters include at least network configuration, service characteristics, signal quality, and number of carriers. In this way, by setting specific preset simulation parameters, the reliability information under different scenarios is simulated, and the service reliability tables corresponding to different scenarios are obtained and stored inside the network side device.

[0186] In the method of obtaining a service reliability table based on target data statistics (existing network statistics method), the target data are different numbers of carriers, different service characteristics, different signal qualities, different network configurations, and different reliability information. Specifically, in order to obtain statistical data under different numbers of carriers, different service characteristics, different signal qualities, and different network configurations, specific services with reliability requirements (different service characteristics are carried on different 5QI (5G QoS identifier) / slices / 5QI+slices) are carried on separate 5QI / slices, or separate 5QI+slices, or the base station supports QoS flow identification (QoSFlow Indication, QFI). When performing statistics, the number of activated carriers and signal quality of the terminal where the service is located, as well as the network configuration on the specific bearer, are obtained to achieve the goal of distinguishing the number of carriers, service characteristics, signal quality, network configuration, and reliability information statistics.

[0187] In the method of obtaining the service reliability table through actual service measurement (actual measurement method), that is, for the service to be tested with different service characteristics, the service to be tested is carried on a separate 5QI / slice, or a separate 5QI+slice, and the configuration and activation of different numbers of carriers are tested respectively. The reliability information of the specific 5QI or specific slice or specific 5QI+slice or the current QoS flow is counted through the base station to obtain the reliability information corresponding to the current service characteristics, signal quality, network configuration, and different numbers of carriers.

[0188] In the AI ​​method (AI method), a service reliability table is generated by training a target model based on sample data. The sample data is historical service information collected by network-side equipment, including network configuration, service characteristics, signal quality, number of carriers, and reliability information. The target model is trained based on this sample data to obtain reliability information for different numbers of carriers. Then, by setting different network configurations, service characteristics, signal quality, and number of carriers as model inputs, the corresponding reliability information is output to generate a service reliability table.

[0189] The target model is a deep neural network model, such as a DNN. This model can be implemented within the base station, at the network management system, or on an external device (such as a radio intelligent controller (RIC)). If the model is not within the base station, the network management system or external device will send the output to the base station.

[0190] Of course, when the network-side equipment performs reliability information statistics, it needs to obtain information such as the service characteristics of the service, the signal quality of the carried terminal, the number of carriers, and the network parameter configuration, and record them in different reliability tables based on their association.

[0191] It should also be noted that during the service reliability table generation process, the service characteristics may be obtained by at least one of the following methods: obtaining service characteristics input via private network operator equipment; obtaining service characteristics input via local portal equipment; parsing target items; or obtaining service characteristics input by users. The specific implementation is the same as described above and will not be further described here. Optionally, the network-side device supports reliability information statistics at the QoS flow level, 5QI level, slice level, and 5QI+slice level.

[0192] In addition, in this embodiment, considering the resource consumption of storing a large number of service reliability tables, optionally, the service reliability tables are grouped according to signal quality and / or service characteristics.

[0193] Specifically, if reliability information (reliability indicators) do not differ significantly within a certain range of packet sizes and packet transmission intervals, the packet sizes and packet transmission intervals within this range can be grouped together. This type of service characteristic corresponds to a reliability table or a row within the table, with signal quality serving as the virtual division unit. Conversely, if reliability indicators do not differ significantly within a certain range of signal quality, signal quality can be segmented and grouped together. This type of service characteristic corresponds to a reliability table or a row within the table, with service characteristics serving as the virtual division unit. It is also possible to segment and group both service characteristics and signal quality simultaneously, further reducing the size of the reliability table. Furthermore, different network configurations, different numbers of carriers, and different reliability requirements also serve as division units in the reliability table. For example, an SR period of 5ms and a number of 2 carriers correspond to a reliability grid or several rows within the table. This allows for limiting and implementing a wide range of service characteristics and signal quality.

[0194] For example, different service characteristics form different service reliability tables, and each service reliability table is divided into units based on signal quality. Service characteristics with a small impact on service reliability information (e.g., less than 0.00000001%) are grouped together. Based on simulation / statistics / measurement / AI methods, eight groups are obtained, including service packet sizes of less than 100B, 100-200B, 200-300B, 300-500B, 500-800B, 800-1200B, 1200-1400B, and more than 1400B. Two groups are obtained with packet transmission intervals of less than 5ms and more than 5ms. Therefore, grouping based on service characteristics will form 16 service reliability tables, and each service reliability table is divided into units based on signal quality, network configuration, number of carriers, and reliability information.

[0195] Of course, when grouping the service reliability table based on signal quality or service characteristics, corresponding grouping rules can be preset, such as the grouping rules for the service packet size mentioned above. However, in the simulation / statistics / actual measurement / AI method, it may be found that the preset grouping rules are not applicable. The grouping rules can also be adjusted according to the results of simulation / statistics / actual measurement / AI.

[0196] It should be noted that, as can be seen from the above content, the service reliability table in this embodiment is limited, and there is a situation where the number of carriers corresponding to the obtained reliability requirement information cannot be found through the table. Therefore, optionally, this embodiment also includes:

[0197] If the number of carriers corresponding to the reliability requirement information is not found in the service reliability table, the output number of carriers is obtained through the established target model with the reliability requirement information and the current network configuration, service characteristics and signal quality as input.

[0198] Here, the target model trained as described above is used to input the obtained reliability requirement information, current network configuration, service characteristics, and signal quality to obtain the number of carriers required for the service. Then, secondary carriers are configured and activated based on the number of carriers.

[0199] For example, an industry customer enters the industrial control service packet size (100 bytes), packet transmission interval (100ms), and service reliability requirements (99.999% reliability, 20ms latency) through a local portal device. These are then transmitted to the base station via the local control device. The base station queries the service reliability table and cannot obtain the required number of carriers. It then inputs the signal quality (RSRP = -80dBm, SINR = 15dB), service packet size (100 bytes), service packet transmission interval (100ms), and service reliability requirements (99.999%, 20ms) into the DNN deep neural network model, obtaining the required number of carriers as four. This information is then transmitted to the base station, which then configures and activates three secondary carriers for the industry terminal, or one secondary carrier, establishes dual connections on each carrier, and enables the PDCP quad replication function.

[0200] In addition, considering that network configuration, signal quality, etc. may change dynamically during service, optionally, in this embodiment, after configuring and activating the corresponding secondary carrier, the following steps are further included:

[0201] Dynamically monitor the reliability information of current services;

[0202] If the monitoring result indicates that the reliability requirement information is not met, the process returns to the step of determining the number of carriers required for the service based on the reliability requirement information.

[0203] Among them, dynamic monitoring is specifically: carrying the current service on a specific 5QI or a specific slice or a specific 5QI+ slice, and performing 5QI-level or slice-level or 5QI+ slice-level indicator statistics. The base station can also be upgraded to support QoS flow-level indicator statistics, that is, the base station can dynamically select the QoS flow or 5QI or slice or 5QI+ slice to be monitored, periodically count the reliability indicators, and compare them with the obtained service reliability requirement information.

[0204] In this way, if the monitoring result cannot meet the requirements (e.g., signal quality deteriorates) or is much higher than the service reliability information (e.g., terminal signal quality improves), the process returns to step 102 to redetermine the number of carriers. When the redetermined number of carriers is greater than the original number of carriers, new secondary carriers need to be added, and the network-side device will configure and activate the secondary carriers accordingly. When the redetermined number of carriers is less than the original number of carriers, secondary carriers need to be reduced, and the network-side device will deconfigure and deactivate the secondary carriers accordingly.

[0205] In summary, the method of the embodiments of the present invention allows the network side to obtain service reliability indicator information through methods such as local portals, private network operation platforms, and contract information. Combined with the reliability information that the network can provide under different carrier counts, the network can dynamically configure and activate secondary carriers, dual connectivity, and PDCP replication functions to meet the reliability requirements of industry services. When the signal quality of the terminal deteriorates, causing the service reliability requirements to be unmet under the current carrier count configuration, the base station can also dynamically configure and activate secondary carriers, dual connectivity, and PDCP replication functions to ensure service reliability requirements in mobile scenarios.

[0206] like Figure 3 As shown, an auxiliary carrier configuration processing device according to an embodiment of the present invention includes:

[0207] An acquisition module 310 is used to acquire reliability requirement information of a service;

[0208] A determination module 320, configured to determine the number of carriers required for the service based on the reliability requirement information;

[0209] The first processing module 330 is configured to, when the number of carriers required by the service is different from the current number of carriers, perform one of the following actions:

[0210] Configure and activate the corresponding secondary carrier;

[0211] Deactivate the corresponding secondary carrier;

[0212] To configure the corresponding secondary carrier.

[0213] Optionally, the acquisition module is further configured to:

[0214] Obtain reliability requirement information input via dedicated network operation equipment;

[0215] Obtain reliability requirement information input via local portal equipment;

[0216] Obtain the reliability requirement information in the service quality QoS information of the business contract.

[0217] Optionally, the determining module is further configured to:

[0218] Based on the current network configuration, service characteristics, and signal quality, the number of carriers corresponding to the reliability requirement information is determined.

[0219] Optionally, the determining module includes:

[0220] A query submodule, configured to query the service reliability table for the number of carriers corresponding to the reliability requirement information under the current network configuration, service characteristics, and signal quality;

[0221] The service reliability table records the relationship between network configuration, service characteristics, signal quality, reliability information and the number of carriers.

[0222] Optionally, the determining module further includes:

[0223] A processing submodule is used to obtain the output number of carriers through the established target model, using the reliability requirement information and the current network configuration, service characteristics and signal quality as input, if the number of carriers corresponding to the reliability requirement information is not found in the service reliability table.

[0224] Optionally, the service reliability table is obtained by performing simulation evaluation based on preset simulation parameters; or,

[0225] The service reliability table is obtained by statistics based on target data; or

[0226] The service reliability table is obtained through actual service measurement; or,

[0227] The service reliability table is obtained through a target model trained based on sample data.

[0228] Optionally, the service reliability table is grouped by signal quality and / or service characteristics.

[0229] Optionally, the device further comprises:

[0230] Monitoring module, used to dynamically monitor the reliability information of current services;

[0231] The second processing module is configured to return to the step of determining the number of carriers required for the service according to the reliability requirement information if the monitoring result indicates that the reliability requirement information is not met.

[0232] Optionally, the device further comprises:

[0233] The third processing module is configured to enable a packet data convergence protocol (PDCP) replication function when configuring and activating a corresponding secondary carrier.

[0234] Optionally, the network side device supports reliability information statistics at QoS flow level, 5QI level, slice level, and 5QI+slice level.

[0235] Optionally, the reliability requirement information includes at least one of the following:

[0236] reliability;

[0237] Delay;

[0238] Packet loss rate;

[0239] Packet error rate;

[0240] Bit error rate;

[0241] Block error rate.

[0242] Optionally, the service characteristics are obtained in at least one of the following ways:

[0243] Obtaining service characteristics input via dedicated network operation equipment;

[0244] Obtaining business characteristics input via a local portal device;

[0245] Parse the target item;

[0246] Get the business characteristics entered by the user.

[0247] After obtaining the reliability requirement information of the service, the device determines the number of carriers that can meet the requirements of the service, and then performs one of the following actions when the determined number of carriers is different from the current number of carriers: configuring and activating the corresponding auxiliary carrier; deactivating the corresponding auxiliary carrier; deconfiguring the corresponding auxiliary carrier to meet the current service reliability requirements.

[0248] It should be noted that the device is a device that applies the above-mentioned secondary carrier configuration processing method, and the implementation of the above-mentioned method embodiment is applicable to the device and can also achieve the same technical effect.

[0249] like Figure 4 As shown, a network side device 400 according to an embodiment of the present invention includes a processor 410,

[0250] The processor 410 is used to obtain reliability requirement information of the service;

[0251] determining the number of carriers required for the service based on the reliability requirement information;

[0252] If the number of carriers required by the service is different from the current number of carriers, perform one of the following actions:

[0253] Configure and activate the corresponding secondary carrier;

[0254] Deactivate the corresponding secondary carrier;

[0255] To configure the corresponding secondary carrier.

[0256] Optionally, the processor is further configured to:

[0257] Obtain reliability requirement information input via dedicated network operation equipment;

[0258] Obtain reliability requirement information input via local portal equipment;

[0259] Obtain the reliability requirement information in the service quality QoS information of the business contract.

[0260] Optionally, the processor is further configured to:

[0261] Based on the current network configuration, service characteristics, and signal quality, the number of carriers corresponding to the reliability requirement information is determined.

[0262] Optionally, the processor is further configured to:

[0263] In the service reliability table, query the number of carriers corresponding to the reliability requirement information under the current network configuration, service characteristics and signal quality;

[0264] The service reliability table records the relationship between network configuration, service characteristics, signal quality, reliability information and the number of carriers.

[0265] Optionally, the processor is further configured to:

[0266] If the number of carriers corresponding to the reliability requirement information is not found in the service reliability table, the output number of carriers is obtained through the established target model with the reliability requirement information and the current network configuration, service characteristics and signal quality as input.

[0267] Optionally, the service reliability table is obtained by performing simulation evaluation based on preset simulation parameters; or,

[0268] The service reliability table is obtained by statistics based on target data; or

[0269] The service reliability table is obtained through actual service measurement; or,

[0270] The service reliability table is obtained through a target model trained based on sample data.

[0271] Optionally, the service reliability table is grouped by signal quality and / or service characteristics.

[0272] Optionally, the processor is further configured to:

[0273] Dynamically monitor the reliability information of current services;

[0274] If the monitoring result indicates that the reliability requirement information is not met, the process returns to the step of determining the number of carriers required for the service based on the reliability requirement information.

[0275] Optionally, the processor is further configured to:

[0276] When the corresponding secondary carrier is configured and activated, the packet data convergence protocol PDCP replication function is correspondingly enabled.

[0277] Optionally, the network side device supports reliability information statistics at QoS flow level, 5QI level, slice level, and 5QI+slice level.

[0278] Optionally, the reliability requirement information includes at least one of the following:

[0279] reliability;

[0280] Delay;

[0281] Packet loss rate;

[0282] Packet error rate;

[0283] Bit error rate;

[0284] Block error rate.

[0285] Optionally, the service characteristics are obtained in at least one of the following ways:

[0286] Obtaining service characteristics input via dedicated network operation equipment;

[0287] Obtaining business characteristics input via a local portal device;

[0288] Parse the target item;

[0289] Get the business characteristics entered by the user.

[0290] After obtaining the reliability requirement information of the service, the network-side device of this embodiment determines the number of carriers that can meet the requirements of the service, and then, when the determined number of carriers is different from the current number of carriers, performs one of the following actions: configuring and activating the corresponding auxiliary carrier; deactivating the corresponding auxiliary carrier; deconfiguring the corresponding auxiliary carrier to meet the current service reliability requirement.

[0291] A network side device according to another embodiment of the present invention, such as Figure 5 As shown, it includes a transceiver 510, a processor 500, a memory 520, and a program or instruction stored in the memory 520 and executable on the processor 500; when the processor 500 executes the program or instruction, the above-mentioned auxiliary carrier configuration processing method is implemented.

[0292] The transceiver 510 is configured to receive and send data under the control of the processor 500 .

[0293] Among them, Figure 5In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 500 and memory represented by memory 520. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 510 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 when performing operations.

[0294] A readable storage medium according to an embodiment of the present invention stores a program or instruction thereon. When the program or instruction is executed by a processor, the steps in the auxiliary carrier configuration processing method described above are implemented, and the same technical effect can be achieved. To avoid repetition, they are not described here.

[0295] The processor is the processor in the secondary carrier configuration processing method described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0296] It should be further noted that many functional components described in this specification are referred to as modules in order to more particularly emphasize the independence of their implementation methods.

[0297] In embodiments of the present invention, modules can be implemented in software so that they can be executed by various types of processors. For example, an identified executable code module can include one or more physical or logical blocks of computer instructions, for example, which can be constructed as objects, procedures, or functions. Nevertheless, the executable code of the identified module does not need to be physically located together, but can include different instructions stored in different locations, which, when logically combined together, constitute the module and achieve the specified purpose of the module.

[0298] In fact, executable code module can be a single instruction or many instructions, and can even be distributed on a plurality of different code segments, distributed in the middle of different programs, and distributed across a plurality of memory devices.Similarly, operating data can be identified in the module, and can be implemented and organized in the data structure of any appropriate type according to any appropriate form.Described operating data can be collected as a single data set, or can be distributed in different locations (including on different storage devices), and can only be present on a system or network as an electronic signal at least in part.

[0299] When a module can be implemented using software, given the current state of hardware technology, those skilled in the art can build corresponding hardware circuits to implement the corresponding functions of the module, regardless of cost. The hardware circuits may include conventional very large scale integration (VLSI) circuits or gate arrays, as well as existing semiconductors such as logic chips and transistors, or other discrete components. Modules may also be implemented using programmable hardware devices, such as field programmable gate arrays, programmable array logic, or programmable logic devices.

[0300] The above exemplary embodiments are described with reference to the accompanying drawings. Many different forms and embodiments are possible without departing from the spirit and teachings of the present invention. Therefore, the present invention should not be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be complete and perfect and will convey the scope of the invention to those skilled in the art. In the drawings, component sizes and relative sizes may be exaggerated for clarity. The terminology used herein is for purposes of describing specific exemplary embodiments only and is not intended to be limiting. As used herein, the singular forms "a," "an," and "the" are intended to include plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms "comprising" and / or "including," when used in this specification, indicate the presence of stated features, integers, steps, operations, components, and / or elements, but do not preclude the presence or addition of one or more other features, integers, steps, operations, components, elements, and / or groups thereof. Unless otherwise indicated, when stated, a range of values ​​includes the upper and lower limits of that range and any subranges therebetween.

[0301] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.

Claims

1. A method for configuring a secondary carrier, characterized in that: Executed by network-side devices, including: Obtaining business reliability requirement information; determining the number of carriers required for the service based on the reliability requirement information; If the number of carriers required by the service is different from the current number of carriers, perform one of the following actions: Configure and activate the corresponding secondary carrier; Deactivate the corresponding secondary carrier; To configure the corresponding secondary carrier; The determining, according to the reliability requirement information, the number of carriers required for the service includes: Determining the number of carriers corresponding to the reliability requirement information based on the current network configuration, service characteristics, and signal quality; wherein the network configuration includes at least one of the following: whether time slot repetition is enabled, and whether pre-scheduling and scheduling request periods are enabled; the service characteristics include the size of service packets and the packet transmission interval; and the signal quality includes at least one of the following: received power and signal-to-noise ratio; The method further comprises: When the corresponding secondary carrier is configured and activated, the packet data convergence protocol PDCP replication function is correspondingly enabled.

2. The method according to claim 1, characterized in that The obtaining of the reliability requirement information of the service includes at least one of the following methods: Obtain reliability requirement information input via dedicated network operation equipment; Obtain reliability requirement information input via local portal equipment; Obtain the reliability requirement information in the service quality QoS information of the business contract.

3. The method according to claim 1, characterized in that The determining, based on the current network configuration, service characteristics, and signal quality, the number of carriers corresponding to the reliability requirement information includes: In the service reliability table, query the number of carriers corresponding to the reliability requirement information under the current network configuration, service characteristics and signal quality; The service reliability table records the relationship between network configuration, service characteristics, signal quality, reliability information and the number of carriers.

4. The method according to claim 3, characterized in that Also includes: If the number of carriers corresponding to the reliability requirement information is not found in the service reliability table, the output number of carriers is obtained through the established target model with the reliability requirement information and the current network configuration, service characteristics and signal quality as input.

5. The method according to claim 3, characterized in that The service reliability table is obtained by simulation evaluation based on preset simulation parameters; or The service reliability table is obtained by statistics based on target data; or The service reliability table is obtained through actual service measurement; or, The service reliability table is obtained through a target model trained based on sample data.

6. The method according to claim 3, characterized in that The service reliability table is grouped by signal quality and / or service characteristics.

7. The method according to claim 1, characterized in that After configuring and activating the corresponding secondary carrier, the method further includes: Dynamically monitor the reliability information of current services; If the monitoring result indicates that the reliability requirement information is not met, the process returns to the step of determining the number of carriers required for the service based on the reliability requirement information.

8. The method according to claim 1, wherein The network side device supports reliability information statistics at QoS flow level, 5QI level, slice level, and 5QI+slice level.

9. The method according to claim 1, characterized in that The reliability requirement information includes at least one of the following: reliability; Delay; Packet loss rate; Packet error rate; Bit error rate; Block error rate.

10. The method according to claim 3 or 4, characterized in that The service characteristics are obtained in at least one of the following ways: Obtaining service characteristics input via dedicated network operation equipment; Obtaining business characteristics input via a local portal device; Parse the target item; Get the business characteristics entered by the user.

11. A secondary carrier configuration processing device, characterized in that: include: Acquisition module, used to obtain reliability requirement information of the business; A determination module, configured to determine the number of carriers required for the service based on the reliability requirement information; The first processing module is configured to, when the number of carriers required by the service is different from the current number of carriers, perform one of the following actions: Configure and activate the corresponding secondary carrier; Deactivate the corresponding secondary carrier; To configure the corresponding secondary carrier; The determining module is further configured to: Determining the number of carriers corresponding to the reliability requirement information based on the current network configuration, service characteristics, and signal quality; wherein the network configuration includes at least one of the following: whether time slot repetition is enabled, and whether pre-scheduling and scheduling request periods are enabled; the service characteristics include the size of service packets and the packet transmission interval; and the signal quality includes at least one of the following: received power and signal-to-noise ratio; The third processing module is configured to enable a packet data convergence protocol (PDCP) replication function when configuring and activating a corresponding secondary carrier.

12. The device according to claim 11, characterized in that The determining module is further configured to: Based on the current network configuration, service characteristics, and signal quality, the number of carriers corresponding to the reliability requirement information is determined.

13. The device according to claim 12, characterized in that The determination module includes: A query submodule, configured to query the service reliability table for the number of carriers corresponding to the reliability requirement information under the current network configuration, service characteristics, and signal quality; The service reliability table records the relationship between network configuration, service characteristics, signal quality, reliability information and the number of carriers.

14. The device according to claim 13, characterized in that The determining module further includes: A processing submodule is used to obtain the output number of carriers through the established target model, using the reliability requirement information and the current network configuration, service characteristics and signal quality as input, if the number of carriers corresponding to the reliability requirement information is not found in the service reliability table.

15. A network side device, characterized in that: comprising a processor configured to: Obtaining business reliability requirement information; determining the number of carriers required for the service based on the reliability requirement information; If the number of carriers required by the service is different from the current number of carriers, perform one of the following actions: Configure and activate the corresponding secondary carrier; Deactivate the corresponding secondary carrier; To configure the corresponding secondary carrier; The determining, according to the reliability requirement information, the number of carriers required for the service includes: Determining the number of carriers corresponding to the reliability requirement information based on the current network configuration, service characteristics, and signal quality; wherein the network configuration includes at least one of the following: whether time slot repetition is enabled, and whether pre-scheduling and scheduling request periods are enabled; the service characteristics include the size of service packets and the packet transmission interval; and the signal quality includes at least one of the following: received power and signal-to-noise ratio; The processor is further configured to: When the corresponding secondary carrier is configured and activated, the packet data convergence protocol PDCP replication function is correspondingly enabled.

16. A network-side device, comprising: A transceiver, a processor, a memory, and a program or instruction stored in the memory and executable on the processor; wherein the processor implements the auxiliary carrier configuration processing method according to any one of claims 1 to 10 when executing the program or instruction.

17. A readable storage medium having a program or instruction stored thereon, characterized in that: When the program or instruction is executed by a processor, the steps in the secondary carrier configuration processing method according to any one of claims 1 to 10 are implemented.

Images