Method for Adjusting Service Slice, Electronic Device, and Storage Medium
The service slice adjustment method for 5G terminals addresses the inability to schedule resources effectively by adjusting sub-slice parameters based on service demand and network parameters, resulting in improved resource allocation and utilization.
Patent Information
- Application Number
- JP2024516681
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-10-25
- Filing Date
- 2022-07-28
- Publication Date
- 2025-06-23
- Estimated Expiration
- 2042-07-28
AI Technical Summary
Current 5G network slice solutions are only implemented on the core network side, radio access network layer, and transmission network layer, leaving the terminal side unable to reasonably schedule terminal resources according to various service scenarios and user requirements.
A service slice adjustment method is proposed for the terminal side, which involves obtaining service demand parameters and current network parameters, and adjusting each sub-slice parameter of the application service slice accordingly to optimize resource allocation.
This method enables the terminal to efficiently schedule resources based on service scenarios and user demands, preventing resource wastage, improving power and heat management, and enhancing the utilization of terminal resources.
Smart Images

Figure 0007697143000001 
Figure 0007697143000002 
Figure 0007697143000003
Abstract
Description
Technical Field
[0001] This application is proposed based on a Chinese patent application with an application number of 202111241569.3 and an application date of October 25, 2021, claims the priority of the Chinese patent application, and here, the entire content of the Chinese patent application is incorporated into this application by reference.
[0002] The embodiments of this application relate to the technical field of communications, for example, a method for adjusting service slices, an electronic device, and a storage medium.
Background Art
[0003] With the development and evolution of 5G terminals, a single network service design can no longer meet the requirements of 5G multi-service multi-scenarios. According to the requirements of various services and scenarios, differentiated customization, allocation, and scheduling of end-to-end network resources, etc., are called slices. The 5G network slice technology can be divided into five parts: 5G networking architecture slice, core network slice, transmission network slice, and radio network slice. Different slices can meet the requirements of network communication quality such as throughput, bandwidth, latency, and reliability in different service scenarios. In response to the differentiated needs of users, the base station system side has corresponding differentiated slice strategy designs, and according to the current three major application scenarios of 5G, for example, network slice solutions for extended mobile broadband applied to services with large bandwidth and large data volume, network slice solutions applied to millisecond-level low-latency communication, and high network density and coverage network slice solutions applied to the field of Internet of Things.
[0004] Currently, the network slice solution is only implemented on the core network side and then on the radio access network layer and the transmission network layer. Therefore, the terminal side cannot reasonably schedule terminal resources according to various service scenarios and user requirements.
Summary of the Invention
Problems to be Solved by the Invention
[0005] The main objective of the embodiments of this application is to propose a service slice adjustment method, an electronic device, and a storage medium. On the terminal side, it is intended to realize reasonably scheduling terminal resources according to the service scenarios and user requirements of the application service slice.
Means for Solving the Problems
[0006] To achieve at least the above objective, the embodiments of this application provide a service slice adjustment method, which is applied to a terminal and includes steps of obtaining service demand parameters of an application service slice configured for the terminal and current network parameters of the terminal, where the service demand parameters include service demand parameters of each sub-slice of the application service slice, and adjusting each sub-slice parameter of the application service slice according to the service demand parameters and the current network parameters.
[0007] To achieve at least the above objective, the embodiments of this application further provide an electronic device, which includes at least one processor and a memory communicatively connected to the at least one processor. The memory stores instructions executable by the at least one processor. When the instructions are executed by the at least one processor, the at least one processor can execute the above service slice adjustment method.
[0008] To at least achieve the above object, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the above method for adjusting a service slice is realized.
Brief Description of the Drawings
[0009]
Figure 1
Figure 2
Figure 3
Figure 3a
Figure 3b
Figure 4
Figure 5
Figure 6
Figure 7
Modes for Carrying Out the Invention
[0010] To make the objectives, technical solutions and advantages of the embodiments of this application clearer, each embodiment of this application will be described in detail below with reference to the drawings. However, those skilled in the art can understand that in each embodiment of this application, many technical details are proposed for readers to better understand this application. However, even without these technical details and various deformations and changes based on the following embodiments, the technical solutions claimed in this application can be realized. The division of the following embodiments is for convenience of explanation and does not limit the specific implementation forms of this application in any way. Unless there is a contradiction, each embodiment can be combined with or cited from each other.
[0011] In response to the differentiated needs of users, the base station system side has a corresponding differentiated slice strategy design. According to the three main application scenarios of current 5G, for example, there are network slice solutions for extended mobile broadband applied to services with large bandwidth and large data volume, network slice solutions applied to millisecond-level low-latency communication, and high network density and coverage network slice solutions applied to the field of Internet of Things. For users on the 5G terminal side, when the terminal user is involved in high-speed upload and download, high-resolution video and audio, multi-player online games, multi-player online live streaming, high resolution, etc., the required throughput is very large. In this case, it is necessary to perform slice processing in the high-speed throughput mode. When the terminal user only performs WeChat chat, web browsing, and transmission of small files, the required throughput is very small. In this case, it is only necessary to perform slice processing in the low-speed throughput mode. Conventional network slicing is only performed on the core network side, and then on the radio access network layer and the transmission network layer, but it is not mentioned on the terminal side. Although slice processing is not performed on the terminal, if it is assigned by the system or the current operating throughput and channels are redundant, waste of traffic and power consumption will occur. If the assigned throughput and channels are insufficient, or the channels are congested and the bit error is serious, freezes and lags will occur when actually used.
[0012] One embodiment of the present application relates to a method for adjusting a service slice, which is applied to the terminal side and includes steps 101 to 102 as shown in FIG. 1.
[0013] Step 101: Obtain the service demand parameters of the application service slice configured for the terminal and the current network parameters of the terminal. The service demand parameters include the service demand parameters of each sub-slice of the application service slice.
[0014] In one exemplary implementation, the application service slice of the terminal is broadly classified into a data service slice and a call service slice. Specifically, it includes high-throughput application service slices such as high-speed download and upload, high-resolution video, high-resolution video calls, high-traffic games, cloud services, augmented reality, and virtual reality, and low-throughput application service slices such as network chat services, web browsing, single-player mini-games, mobile phone payments, mobile phone browsing, and low-speed transmission. Due to different service natures, the network types, upload and download traffic requirements, latency, number of simultaneously accessed terminals, etc. required for the above different services are all different. Even in the case of the same application service slice (for example, the game service slice), there are different real-time requirements, such as single-player online game service slices, multiplayer online network game service slices, low-resolution game service slices, high-resolution game service slices, 2D game service slices, 3D game service slices, etc. Since the screens, resolutions, stories, maps, whether they are 3D, etc. of different game service slices are different, the slice parameters required for the game service slice are different.
[0015] In one exemplary implementation, the service demand parameters may include information such as throughput, throughput rate, spectrum range (i.e., operating frequency), spectrum bandwidth, interference parameters, and uplink power parameters. Obtaining the service demand parameters of the application service slice configured for the terminal may include the following four methods.
[0016] Method 1: When detecting the application service slice opened by the terminal, collect the RF information parameter set of the terminal, perform statistical analysis on the RF information parameter set, and obtain the service demand parameters of the application service slice.
[0017] Method 2: When detecting the application service slice opened by the terminal, obtain the delay when opening the application service slice and when executing the application service slice, obtain the opening speed of the application service slice, and obtain the service demand parameters of the application service slice according to the delay, speed, and a predetermined target threshold.
[0018] Method 3: The slice network information of the base station core network, bearer network, and transmission network is sent to the terminal through a specific message. After receiving the corresponding slice network information, the terminal uses the slice network information transmitted from the base station as the service demand parameters of the terminal's application service slice.
[0019] The service demand information set by the user UI interface refers to the slice demand requirements and settings dedicated to the terminal user. This setting is performed through the setting menu of the terminal UI interface. Through the defined switching window and options, the user can set the slice demand on the terminal side. For example, information such as maximum uplink throughput, maximum downlink throughput, service matching network speed throughput, minimum delay throughput, minimum power consumption throughput, extended signal throughput, game mode throughput, high-resolution video mode throughput, cooling mode throughput, red packet slice mode throughput, etc. can be mentioned.
[0020] In one exemplary implementation, Method 1 and Method 2 can be combined and used. After setting different weighting parameters for the parameters collected by Method 1 and Method 2, the service demand parameters can be obtained by the weighting method.
[0021] In one exemplary implementation, the current network parameters may include throughput, network speed, throughput rate, spectral range (i.e., operating frequency), spectral bandwidth, interference parameters, uplink power parameters, etc., and the current network parameters are obtained by analyzing the current RF information parameter set of the terminal.
[0022] Step 102, adjust each sub-slice parameter of the application service slice according to the service demand parameters and the current network parameters.
[0023] In one exemplary implementation, each sub-slice parameter of the application service slice may include a throughput sub-slice parameter, a power sub-slice parameter, a bandwidth sub-slice parameter, a spectrum sub-slice parameter, an interference sub-slice parameter, and a resource block (abbreviated as RB) sub-slice parameter, etc. When a difference is detected between the service demand parameters and the current network parameters (i.e., the service demand parameters and the current network parameters are different or the difference is greater than a predetermined threshold), adjust each sub-slice parameter to the parameter value corresponding to the service demand parameters.
[0024] The method for adjusting a service slice according to the present application is to obtain the service demand parameters of the application service slice configured for the terminal and the current network parameters of the terminal in the process of resource scheduling on the terminal side. The service demand parameters include the service demand parameters of each sub-slice of the application service slice, and adjust the parameters of each sub-slice of the application service slice according to the service demand parameters and the current network parameters. By adjusting the slice parameters of each application service slice according to the service demand parameters and the current network parameters of each application service slice, the terminal can perform resource scheduling according to the service scenarios and user demands of each application service slice, prevent the problem that the peak of the application service slice does not reach the standard due to inappropriate configuration of the terminal, balance the demand and the network resources of the terminal, play a role in power saving and heat reduction, improve the rationality of the scheduling of terminal resources and the utilization rate of terminal resources, and solve the problem that in the prior art, the network slice solution is only performed on the core network side, so the terminal side cannot reasonably schedule terminal resources according to various service scenarios and user demands.
[0025] One embodiment of the present application relates to a method for adjusting a service slice. As shown in FIG. 2, it includes steps 201 to 203.
[0026] Step 201: Obtain the service demand parameters of the application service slice configured for the terminal and the current network parameters of the terminal. The service demand parameters include the service demand parameters of each sub-slice of the application service slice.
[0027] In one exemplary implementation, this step is substantially the same as step 101 of the embodiment of the present application, and the repeated description is omitted here.
[0028] Step 202, select a slice adjustment mode corresponding to the application service slice from a predetermined slice adjustment mode according to the service demand parameters, where the slice adjustment mode is used to indicate the adjustment order of each sub-slice parameter of the application service slice.
[0029] In one exemplary implementation, since the adjustment of the application service slice of the 5G terminal relates to each sub-slice parameter of each application service slice (such as throughput sub-slice, power sub-slice, spectrum sub-slice, antenna sub-slice, etc.), before adjusting each sub-slice parameter of the application service slice, it is necessary to determine the adjustment order of each sub-slice parameter of the application service slice. The module can calculate according to the current service demand, information of the connected base station (optionally used to indicate the adjustment method of each sub-slice parameter of the application service slice), its own radio parameter conditions (optionally, that is, the current network parameters), and the internal parameter model (storing information such as a predetermined slice adjustment mode, peak uplink and downlink throughput in different application service slice configurations, and the stored peak and average uplink and downlink rates reached by different application software each time in the past), and can match the slice adjustment mode corresponding to the optimal application service slice.
[0030] In addition, this application can further store the model parameters, test parameters, and control parameters of each 5G slice (i.e., application service slice) on the terminal side, including different bandwidths, powers, spectrums, interferences, RB (resource block) resources, Long Term Evolution (abbreviated as LTE), New Radio (abbreviated as NR), Carrier Aggregation (abbreviated as CA) mode, uplink channel estimation (Sounding Reference Signal, abbreviated as SRS) mode, multiple-in multiple-out (abbreviated as MIMO) mode, and slice parameter storage in the uplink / downlink antenna switching mode. At the same time, it is also used to control the storage of each slice adjustment parameter and driver code, store the peak uplink / downlink throughput in different slice configurations, the peaks and average uplink / downlink rates reached by different application software in the past, and update the throughput value required for the storage of application software in real time based on a large amount of usage data.
[0031] Step 203: Adjust each sub-slice parameter of the application service slice according to the service demand parameters, current network parameters, and slice adjustment mode corresponding to the application service slice.
[0032] In one exemplary implementation, this step is substantially the same as the adjustment method in step 102 of the embodiment of this application, except for adding the adjustment order of each sub-slice parameter. Here, duplicate descriptions are omitted.
[0033] The embodiment of this application can, based on other embodiments, obtain the adjustment order of each sub-slice parameter of the application service slice according to the current demand of the application service slice, and adjust each sub-slice parameter according to the priority, thereby improving the adjustment efficiency of the application service slice.
[0034] One embodiment of the present application relates to a method for adjusting a service slice. As shown in FIG. 3, it includes steps 301 to 303.
[0035] Step 301: Obtain the service demand parameters of the application service slice configured for the terminal and the current network parameters of the terminal. The service demand parameters include the service demand parameters of each sub-slice of the application service slice.
[0036] In one exemplary implementation, this step is substantially the same as step 101 of the embodiment of the present application, and the repeated description is omitted here.
[0037] Step 302: Obtain a parameter change value according to the service demand parameters and the current network parameters, and obtain an adjustment step and an adjustment method according to the parameter change value.
[0038] In one exemplary implementation, according to the current network parameters and service demand parameters, compare the parameter change values before and after the change, select one or two adjustment methods for each sub-slice parameter, and select an adjustment step according to the size of the parameter change value.
[0039] In one exemplary implementation, the adjustment methods include three methods: hard slice circuit adjustment method, soft slice program adjustment method, and soft-hard combination adjustment.
[0040] In one exemplary implementation, for the hard slice circuit adjustment method, the hard slice circuit does not need to change the RF driver code and is implemented by the logic gate devices and switches built into the terminal. The inputs of the logic gates and switch devices are general-purpose input / output ports (abbreviated as GPIO). The input signal is the slice indication signal of the base station or the slice indication signal output by the slice mode mapping algorithm unit. The realization of the hard slice circuit is as follows: The multiplexing switch detects the threshold slice requirements of different networks and services, and controls the current MIMO mode, SRS mode, power size, and sensitivity size of the terminal. Taking the SRS method of NR hard slicing as an example, the multiplexing switch detects the threshold slice requirements of different networks and services, controls the circuit switching logic, and forces the current SRS mode of the terminal to modes such as PMI, 1T2R, 2T4R, 1T4R. The hard slice circuit is shown in Figure 3a.
[0041] In one exemplary implementation, the soft slice program adjustment method includes parameter control and adjustment based on the soft slice program. The soft slice adjustment includes network standard slices, the NR operating bandwidth slices of the terminal, CA combination slices, SRS operating mode slices, MIMO operating mode slices, and scheduling parameter slices. Inside the terminal, there is a normal default RF channel driver code for controlling the mobile phone to operate according to the default parameters. However, the RFC configuration is mostly not carried out for specific targets but is large-scale and comprehensive and cannot meet the requirements of the corresponding service scenarios. The soft slice control unit performs different slice configurations by calling different RF driver codes, that is, controls the network channel and operating mode configurations for different services and requirements through the RF driver program. As shown in Figure 3b, when divided by network standard slices, the RFC is configured as RFC_LTEonly, RFC_SA, RFC_NSA. When divided by slice bandwidth, the RFC code is divided into several modes such as RFC_WB1, RFC_WB2, RF3_WB3,... RFC_WBn. In the case of slice division based on different CA combination methods, the RF driver code (abbreviated as Request For Comments, RFC) code is divided into several modes such as RFC_CA1, RFC_CA2, RF3_CA3,... RFC_CAn. In the case of slice division based on different SRS operating modes, the RFC code is divided into several modes such as RFC_SRS_PMI, RFC_SRS_1T2R, RF3_SRS_1T4R, RFC_SRS_2T4R. In the case of slice division based on different MIMO operating modes, the RFC code is divided into several modes such as RFC_DL_SISO, RFC_DL_22mimo, RFC_DL_33mimo, RFC_DL_44mimo, RFC_UL_SISO, RFC_UL_MIMO.In the case of slice splitting based on different scheduling parameter operation modes, the current different scheduling restriction parameters MOD1, MOD2, MOD3, MODn divide the RFC code into several modes of RFC_MOD1, RFC_MOD2, RFC_MOD3, RFC_MODn.
[0042] In one exemplary implementation, the adjustment step may include fine-grained adjustment, medium-grained adjustment, coarse-grained adjustment, or any other appropriate granularity adjustment step. For example, by comparing the difference between the current network throughput information and the target throughput, a corresponding granularity adjustment method is selected to meet the differentiated network requirements of different users and services. When the current uplink / downlink throughput increase demand is small, the terminal can be directly switched from the LTE mode to the LTE CA mode or the LTE MIMO mode. When the current uplink / downlink throughput increase demand is medium, the terminal can be directly switched from the LTE mode to the SA mode or the NSA mode. When the current uplink / downlink throughput increase demand is large, the terminal can be switched from the current LTE mode to the NR CA mode or the NR CA+LTE CA mode, and the granularity increases in turn. Different granularities are mapped to different throughput adjustment thresholds and steps, and the adjustment is realized by closed-loop optimization until the requirements of service characteristics are met.
[0043] Step 303: Adjust each sub-slice parameter of the application service slice according to the adjustment step, adjustment method, service demand parameters, and current network parameters.
[0044] In one exemplary implementation, this step is substantially the same as the adjustment method in step 102 of the embodiments of the present application, except that the adjustment method and adjustment step of each sub-slice parameter are set, and the repeated description is omitted here.
[0045] Embodiments of the present application can also select appropriate adjustment steps and adjustment methods according to the service demand of the application service slice and the current network parameters based on other examples, improving the adjustment efficiency of the application service slice.
[0046] One example of the present application relates to a method for adjusting a service slice, which is applied to the terminal side and includes steps 401 to 404 as shown in FIG. 4.
[0047] In step 401, obtain the service demand parameters of the application service slice configured for the terminal and the current network parameters of the terminal. The service demand parameters include the service demand parameters of each sub-slice of the application service slice.
[0048] In one exemplary implementation, this step is substantially the same as step 101 of the embodiments of the present application, and the repeated description is omitted here.
[0049] In step 402, adjust the power sub-slice parameters of the application service slice according to the service demand parameters and the current network parameters.
[0050] In one exemplary implementation, when the sub-slice is a power sub-slice, the service demand parameter is the target uplink power parameter, the current network parameter is the current uplink power parameter. If there is a difference between the target uplink power parameter and the current uplink power parameter, adjust the uplink power parameter of the power sub-slice according to the target uplink power parameter. The uplink power parameter includes three adjustment methods: the maximum power limit adjustment method, the extended uplink power adjustment method, and the shared power adjustment method.
[0051] In one exemplary implementation, the maximum power limit adjustment method includes calling the corresponding maximum transmission power limit according to the target uplink power parameter and the service scenario. For example, the uplink maximum transmission power limit value of NR is predefined, and the uplink power limit values of NSA and SA may also be different. For example, in the NSA mode, the power level is 3, the default power of NR is 23 dBm, and the maximum power is generally less than 24.5 dBm. In the SA mode, the power level is 2, the default power is 25 dB, and the maximum power is generally less than 26.5 dB. If the current uplink signal of the mobile phone is weak, the user's service needs to improve the quality and throughput of the uplink signal by increasing the uplink power. In this case, it is necessary to increase the uplink power limit value of NR through the power slice control of NR. In the case of service scenario A, call the PowerA maximum transmission power limit value. In the case of service scenario B, call the PowerB maximum transmission power limit value. Generally, call the default maximum power limit value of PowerC.
[0052] In one exemplary implementation, for the uplink power adjustment method, the uplink power parameters of the power sub-slice include the main antenna power parameter and the backup antenna power parameter. First, the main antenna power parameter of the power sub-slice is adjusted according to the target uplink power parameter. When the main antenna power parameter meets a predetermined power limit value, the backup antenna power parameter of the power sub-slice is adjusted according to the target uplink power parameter. The adjustment of the backup antenna power parameter may reduce the overall insertion loss through several passive device paths to increase the system power. By changing the slicing method of the power level, the normal power level PC3 can be changed to the high power mode of PC2, or by changing the slicing method for calibrating the maximum target power, specific high power calibration slice parameters can be called to increase the target maximum power output. In addition, this may be performed by the main-backup antenna compensation method. The backup antenna can perform specific power compensation as needed. For example, if the power of the main antenna of NR is 25 dB and the power of the backup antenna is 22 dB by default, according to the specific requirements of the current uplink service and network situation, the uplink power parameter can be compensated by 0 - 4 dB to obtain uplink antenna slice powers of 22, 23, 24, 25, and 26 respectively.
[0053] In one exemplary implementation, when the power sub-slice is a shared power slice, the uplink power parameters include the New Radio (NR) power parameter (5G) and the Long-Term Evolution (LTE) anchor power parameter (4G), and adjusting the sizes and ratios of the NR power parameter and the LTE anchor power parameter in the power sub-slice according to the target uplink power parameter. For example, when LTE and NR operate simultaneously and shared power control is set, if NR operates at the maximum transmission power, LTE can fallback to a specific power, and similarly, if LTE operates at the maximum power, NR can also fallback to a specific power. Here, slice processing is performed on the power values to which LTE or NR fallback, for example, fallback by 2dB, 4dB, 6dB, 8dB, 10dB, 12dB respectively, and adjust the NR power and the LTE anchor power according to the current service demand and network conditions.
[0054] In step 403, adjust the spectral sub-slice parameters of the application service slice according to the service demand parameters and the current network parameters.
[0055] In one exemplary implementation, when the sub-slice is a spectral sub-slice, the service demand parameters are the target operating frequency and the target throughput, the current network parameters are the current operating frequency and the current throughput, if there is a difference between the target operating frequency and the current operating frequency, adjust the operating frequency of the spectral sub-slice according to the target operating frequency. If there is a difference between the target throughput and the current throughput, obtain the target spectral bandwidth corresponding to the target throughput from the correspondence between the predetermined throughput and the spectral bandwidth, and adjust the spectral bandwidth of the spectral sub-slice according to the target spectral bandwidth.
[0056] In one exemplary implementation, regarding the adjustment of the operating frequency of spectral sub-slices, for example, N78 has a spectral range of 3300 - 3800 MHz. N78 is divided into three bands: band A (3300 - 3500 MHz), band B (3500 - 3700 MHz), and band C (3700 - 3800 MHz), and assigned to different users and services respectively. The band division here can be realized by a variable filter to control the slicing of a specific spectral range. When a difference is detected between the target operating frequency and the current operating frequency, for example, when the current operating frequency is 3400 MHz and the target operating frequency is 3600 MHz, in this case, the difference between the current operating frequency and the target operating frequency is 200 MHz. Further, the operating frequency of the spectral sub-slice of the application service slice needs to be divided into the spectral band corresponding to the target operating frequency, and the operating frequency of the spectral sub-slice of the application service slice needs to be adjusted to the target operating frequency.
[0057] In one exemplary implementation, regarding the adjustment of the spectral bandwidth of a spectral sub-slice, for example, N78 has multiple bandwidth values of 10M, 20M, 40M, 50M, 60M, 80M, 90M, and 100M. Different service demands and network conditions correspond to different bandwidths, and the current service throughput is divided into corresponding interval level ranges such as 100Mbps, 200Mbps, 400Mbps, 500Mbps, 600Mbps, 800Mbps, 900Mbps, 1000Mbps and above. When the service throughput is 100Mbps, the corresponding spectral bandwidth is 10M. When the service throughput is 200Mbps, the corresponding spectral bandwidth is 20M, and so on. When the target throughput is 300Mbps and the current throughput is 100Mbps, there is a certain difference between the current throughput and the target throughput of the spectral sub-slice. If it operates at the target throughput using the spectral bandwidth of 10M corresponding to the current throughput, it will cause service delay and congestion. To ensure the normal transmission and execution of the service, it is necessary to adjust the spectral bandwidth of the spectral sub-slice to the spectral bandwidth of 30M corresponding to the target throughput. Also, the invocation of different bandwidths is restricted by different codes, that is, services with small throughput call small bandwidths, and services with large throughput call large bandwidths. Furthermore, due to different uplink qualities, it is necessary to call different NR spectral bandwidths. For example, when there are requirements for uplink communication quality, values such as the Error Vector Magnitude (abbreviated as EVM) can also be adjusted. In this case, it is necessary to call the NR bandwidth value within the EVM threshold range. Taking the N1 frequency band as an example, if the requirement for EVM is less than 1.5%, only bandwidths below 20M of N1 can be called. If the requirement for EVM is less than 2%, bandwidths below 30M of N1 can be called. If the requirement for EVM is less than 3%, bandwidths below 40M of N1 can be called.
[0058] In one exemplary implementation, when the spectral sub-slice is a shared spectral slice, the operating frequency of the spectral sub-slice includes the new radio NR operating frequency (5G) and the long-term evolution LTE operating frequency (4G), the spectral bandwidth of the spectral sub-slice includes the new radio NR spectral bandwidth (5G) and the long-term evolution LTE spectral bandwidth (4G), the size and ratio of the NR operating frequency and the LTE operating frequency in the spectral sub-slice are adjusted according to the target operating frequency, and the size and ratio of the NR spectral bandwidth and the LTE spectral bandwidth in the spectral sub-slice are adjusted according to the target spectral bandwidth. For example, when NR and LTE operate in the same frequency band of FDD such as N1, N3, N5, N7, N8 and LTE B1, B3, B5, B7, B8, the throughput can be improved by using the debugging of the shared spectrum. For example, N1 uses the spectrum of LTE B1, but the bandwidth of N1 is more flexible than 30 MHz, 40 MHz, 50 MHz, etc. By sharing in this way, the throughput rate in the corresponding spectrum can be improved. As a difference, the conventional shared spectrum cannot be sliced, that is, it is a unified spectrum sharing mode, while here the scope, section, and bandwidth of spectrum sharing can be adjusted by the spectral sub-slice. By detecting the signal quality, throughput requirements, or mutual interference situation of LTE and NR in the shared spectrum, dynamic spectral slice sharing is performed, and it is determined which frequency range of LTE shares with the NR frequency range.
[0059] In step 404, the antenna sub-slice parameters of the application service slice are adjusted according to the service demand parameters and the current network parameters.
[0060] In one exemplary implementation, when the sub-slice is an antenna sub-slice, the service demand parameter is the target throughput, the current network parameter is the current throughput, according to the correspondence between a predetermined throughput and the number of antennas, the target number of antennas corresponding to the target throughput and the current number of antennas corresponding to the current throughput are respectively obtained, according to the difference between the target number of antennas and the current number of antennas, the number of antennas of the antenna sub-slice is adjusted, according to the correspondence between a predetermined throughput and the single-frequency bandwidth, the target single-frequency bandwidth corresponding to the target throughput and the current single-frequency bandwidth corresponding to the current throughput are respectively obtained, and according to the difference between the target single-frequency bandwidth and the current single-frequency bandwidth, the single-frequency bandwidth of the antenna sub-slice is adjusted.
[0061] In one exemplary implementation, regarding the adjustment of the number of antennas of the antenna sub-slice, for example, there are more than a dozen 4G-5G antennas in a 5G terminal. When the terminal operates in the single-band SA mode, there are at least 2 antennas, and the maximum is 4 antennas. When the terminal operates in the NR CA mode such as N41-N79, the maximum can reach 8 antennas. When the terminal operates in the NSA mode, the number of antennas is also affected by the current number of LTE anchors. For example, in the case of B3(4)+N78(4), the number of antennas can reach 8 antennas. In the case of B1(4)+B3(4)+B8(2)+N78(4), and when B1 and B3 do not share antennas, the number of antennas can reach 14. The antenna slice module divides the terminal antenna mode into several modes such as 1 antenna, 2 antennas, 3 antennas, and N antennas, sets the limit throughput corresponding to one number of antennas to a specific threshold. For example, below 500M corresponds to 2 antennas, 500M-1600M corresponds to 4 antennas, 1600M-2400M corresponds to 8 antennas, and above 2400M corresponds to 10 antennas. The terminal controls, through the internal driver code and configuration file, the opening of different numbers of 4G-5G antennas by the terminal and the sequence of opening the antennas, thereby performing slice control based on the number of antennas.
[0062] In one exemplary implementation, for the adjustment of the single - frequency bandwidth of an antenna sub - slice, for example, the antenna bandwidth includes two parts: the single - frequency bandwidth and the total supported bandwidth. The RF chip of the terminal can support 5M, 10M, 15M, 20M, 30M, 40M, 50M, 60M, 70M, 80M, 90M, 100M in TDD and FDD frequency bandwidths, and can also support higher bandwidths such as 200M and above in the carrier aggregation frequency bandwidth. In a specific operating line or frequency band, the frequency band range that the terminal can support is also different. For example, Operator A has FreA = 3500MHz - 3600MHz, Operator B has FreB = 3400MHz - 3700MHz, and Operator C has FreC = 3300MHz - 3800MHz. The higher the throughput requirement, the higher the required single - frequency bandwidth, the more frequency channels that need to be supported by the throughput, and the wider the required antenna coverage bandwidth. Here, by adjusting antenna matching or antenna tuning, the operating frequency of the antenna is sliced within the corresponding demand range, and frequencies, bandwidths, and ranges exceeding the slice demand are shielded or weakened.
[0063] In one exemplary implementation, the depth of the resonance frequency of the antenna sub - slice can also be adjusted. For example, when the terminal has a high demand for the antenna efficiency of a specific frequency band, frequency, or channel, fixed - point slice control is performed, the antenna matching is adjusted, and the resonance depth of this frequency can be enhanced to the target threshold requirement until the signal strength or throughput meets the threshold requirement.
[0064] In one exemplary implementation, the present application can also adjust the application service slice or the operating mode of the terminal according to the current network parameters.
[0065] In one exemplary implementation, when the current service demand is high throughput, the mobile phone slices into a large bandwidth, multi-MIMO mode. When the current service demand freezes under LTE, the mobile phone slices into the NR mode. When the NSA mode LTE anchor signal is unstable, the mobile phone slices into the SA mode. When the current service demand freezes under non-CA LTE and the 5G NR signal is weak, the mobile phone slices into a strong LTE CA link combination. When a single NR cannot meet the service scenario, the mobile phone slices into an LTE CA+NR combination mode or an NR CA mode. When the current service demand freezes in a specific SRS 1T2R mode, the mobile phone slices into a better signal quality 1T4R or 2T4R SRS mode. When the service demand freezes in the SISO or primary diversity mode, the mobile phone slices into the NR MIMO mode. When there are upstream freezes or intermittent problems in the current service demand, the mobile phone slices into the power priority mode.
[0066] Example 1: Currently, if it is necessary to download a large-traffic game software or program, a slice monitoring program, taking the mimo circuit control of NR hard slicing such as N78 mimo slice control as an example, when the user demand is small traffic and throughput, the control signal controls NR to enter the 1*1mimo or 2*2mimo mode, and when the user demand is large traffic and throughput, the control signal controls NR to enter the 4*4mimo mode. When the terminal receives the control instruction, it turns off or on the corresponding RX mimo circuit and antenna of N78, configures the RFC RF driver, and forces the mobile phone into different MIMO slice modes until the throughput meets the target threshold requirement.
[0067] Example 2: As an example of SRS mode slice adjustment, in the case of a demand that requires the current peak throughput or a demand that requires peak throughput stability, hardware or software SRS slice control on the terminal side is performed. Taking the SRS method of NR hard slice as an example, the threshold slice demands of different networks and services are detected by a multiplexing switch, the circuit switching logic is controlled, and the current terminal SRS mode is forced into several modes such as PMI, 1T2R, 2T4R, and 1T4R. Or, a soft slice control unit is used to call different SRS slices to configure an RF driver program. Specifically, under the corresponding throughput service demand, the terminal is set to several modes such as RFC_SRS_PMI, RFC_SRS_1T2R, RF3_SRS_1T4R, and RFC_SRS_2T4R by the RF driver code RFC.
[0068] Example 3: In the case of a service demand that requires the current large upload throughput, uplink dual transmission circuit control can be performed by NR hard slice. Taking the uplink dual transmission of N78 as an example, when the user's uplink service is high but the current upload throughput cannot meet the user's service demand, N78 can be forced into the uplink mimo dual transmission mode by slice control, that is, the tx1 and tx2 links operate simultaneously. When the user's uplink service demand throughput is low but the current uplink throughput is redundant, it can be sliced into a single NR transmission mode.
[0069] Embodiments of the present application can also adjust the respective sub-slice parameters of the application service slice in various ways based on other examples, improving the diversity of application service slice adjustment.
[0070] One embodiment of the present application relates to a method for adjusting a service slice, which is applied to the terminal side and may include the following steps 501 to 503 as shown in FIG. 5.
[0071] Step 501: Obtain the service demand parameters of the application service slice configured for the terminal and the current network parameters of the terminal. The service demand parameters include the service demand parameters of each sub-slice of the application service slice.
[0072] In one exemplary implementation, this step is substantially the same as step 101 of the embodiments of the present application, and duplicate descriptions are omitted here.
[0073] Step 502: Adjust the parameters of each sub-slice of the application service slice according to the service demand parameters and the current network parameters.
[0074] In one exemplary implementation, this step is substantially the same as step 102 of the embodiments of the present application, and duplicate descriptions are omitted here.
[0075] Step 503: Obtain the performance parameters during the execution of the adjusted application service slice. When the performance parameters meet a predetermined stop condition, stop the adjustment of the application service slice.
[0076] In one exemplary implementation, after adjusting the application service slice once, run the application service slice and analyze the execution parameters collected during the execution of the application service slice to obtain the performance parameters during the execution of the application service slice (information such as packet loss rate, bit error rate, delay, etc.). When the performance parameters meet a predetermined stop condition (i.e., meet the current service demand), the adjustment of the application service slice can be stopped; otherwise, continuously adjust the application service slice.
[0077] Embodiments of the present application, based on other examples, can also stop adjusting the application service slice after adjusting the application service slice once, detect the current performance of the application service slice, and stop adjusting the application service slice when the performance meets the predetermined conditions. As a result, the method for adjusting the service slice according to the present application performs closed-loop feedback control and can accurately determine whether to end the adjustment of the service slice.
[0078] Another embodiment of the present application relates to an adjustment device for a service slice. Hereinafter, in one exemplary implementation, the details of the adjustment device for the service slice in this embodiment will be described. The following content is only the implementation details provided for easy understanding and is not essential for the implementation of this example. FIG. 6 is a schematic diagram of the adjustment device for the service slice described in this embodiment, and includes an acquisition module 601 and an adjustment module 602.
[0079] The acquisition module 601 is configured to acquire the service demand parameters of the application service slice configured for the terminal and the current network parameters of the terminal. The service demand parameters include the service demand parameters of each sub-slice of the application service slice.
[0080] In one exemplary implementation, the acquisition module 601 may further include a traffic prediction unit To and and a service detection unit To and .
[0081] The traffic prediction unit To is is configured to acquire the service demand parameter method of the application service slice according to Method 1 or Method 2 related to Step 101 of the embodiment of the present application.
[0082] The service detection unit To is is configured to acquire the service demand parameter method of the application service slice according to Method 3 or Method 4 related to Step 101 of the embodiment of the present application.
[0083] The adjustment module 602 is configured to adjust each sub-slice parameter of the application service slice according to the service demand parameters and the current network parameters.
[0084] In one exemplary implementation, the adjustment module 602 may further include a power adjustment unit To and , a frequency adjustment unit To and , and an antenna adjustment unit To and .
[0085] The power adjustment unit To is is configured to adjust the power sub-slice parameter of the application service slice according to the service demand parameters and the current network parameters.
[0086] The frequency adjustment unit To is is configured to adjust the frequency sub-slice parameter of the application service slice according to the service demand parameters and the current network parameters.
[0087] The antenna adjustment unit To is is configured to adjust the antenna sub-slice parameter of the application service slice according to the service demand parameters and the current network parameters.
[0088] In one exemplary implementation, the adjustment device of the service slice may further include a hard slice adjustment method unit and a soft slice program adjustment method unit, and the functions of these units are to provide two methods for the adjustment module to perform slice parameter adjustment.
[0089] In one exemplary implementation, the adjustment device of the service slice may further include an adjustment decision unit, and the function of this unit is to determine the adjustment step and adjustment method for the adjustment module to perform slice parameter adjustment.
[0090] In one exemplary implementation, the service slice adjustment device may further include an adjustment sequence unit, and the function of this unit is to determine the order in which the adjustment module adjusts the power adjustment unit, the frequency adjustment unit, and the antenna adjustment unit.
[0091] In one exemplary implementation, the service slice adjustment device may further include a parameter storage unit, and the function of this unit is to store the relevant parameters of each service slice and store data such as the peak up and down throughput in different configurations of each service slice.
[0092] Obviously, this embodiment is a system embodiment corresponding to the above method embodiment, and this embodiment can be implemented in combination with the above method embodiment. The relevant technical details and technical effects mentioned in the above embodiments are also valid in this embodiment. To avoid repetition, the repeated description is omitted here. Correspondingly, the relevant technical details mentioned in this embodiment can also be applied to the above embodiments.
[0093] It should be noted that each module according to this embodiment is a logical module. In an actual application, one logical unit may be one physical unit, may be a part of one physical unit, or may be realized by a combination of multiple physical units. Also, to emphasize the innovative part of this application, units not closely related to solving the technical problems mentioned in this application are not introduced in this embodiment, but this does not mean that there are no other units in this embodiment.
[0094] Another embodiment of the present application relates to an electronic device. As shown in FIG. 7, it includes at least one processor 701 and a memory 702 communicatively connected to the at least one processor 701. Instructions executable by the at least one processor 701 are stored in the memory 702. When the instructions are executed by the at least one processor 701, the at least one processor 701 can execute the service slice adjustment method in each of the above embodiments.
[0095] The memory and the processor are connected by a bus, which may include any number of interconnected buses and bridges, and the bus connects various circuits of one or more processors and the memory. The bus can also connect various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and thus will not be described further herein. The bus interface provides an interface between the bus and the transceiver. The transceiver may be one element, or may be multiple elements, such as multiple receivers and transmitters, and provides a unit for communicating with various other devices over a transmission medium. The data processed by the processor is transmitted over a wireless medium via an antenna, and further, the antenna receives the data and transmits the data to the processor.
[0096] The processor is responsible for managing the bus and normal processing and can also provide various functions including timing, peripheral interface, voltage regulation, power management, and other control functions. The memory can be used to store data used by the processor when performing operations.
[0097] Another embodiment of the present application relates to a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the above method embodiments are realized.
[0098] That is, as can be understood by those skilled in the art, all or some of the steps for implementing the method of the above embodiments can be completed by a program instructing relevant hardware. The program is stored in a storage medium and includes a plurality of instructions for causing a device (such as a single-chip microcomputer, chip, etc.) or a processor to execute all or some of the steps of the method described in each embodiment of the present application. The above storage medium includes various media capable of storing program codes, such as a USB memory, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
[0099] As can be understood by those skilled in the art, the above embodiments are specific examples for implementing the present application. In actual applications, various changes can be made to its form and details without departing from the essence and scope of the present application.
Claims
1. A method for adjusting a service slice, which is applied to a terminal and includes steps of obtaining service demand parameters of an application service slice configured for the terminal and current network parameters of the terminal, where the service demand parameters include service demand parameters of each sub-slice of the application service slice; adjusting each sub-slice parameter of the application service slice according to the service demand parameters and the current network parameters; The step of adjusting each sub-slice parameter of the application service slice according to the service demand parameters and the current network parameters includes at least one of the following: selecting a slice adjustment mode corresponding to the application service slice from a predetermined slice adjustment mode according to the service demand parameters, where the slice adjustment mode indicates an adjustment order of each sub-slice parameter of the application service slice, and adjusting each sub-slice parameter of the application service slice according to the service demand parameters, the current network parameters, and the slice adjustment mode corresponding to the application service slice; or When the sub-slice is a power sub-slice, the service demand parameter is the target uplink power parameter, the current network parameter is the current uplink power parameter. When there is a difference between the target uplink power parameter and the current uplink power parameter, the step of adjusting the uplink power parameter of the power sub-slice according to the target uplink power parameter. The uplink power parameter includes the main antenna power parameter and the backup antenna power parameter. The step of adjusting the uplink power parameter of the power sub-slice according to the target uplink power parameter includes the step of adjusting the main antenna power parameter of the power sub-slice according to the target uplink power parameter. When the main antenna power parameter satisfies a predetermined power limit value, the step of adjusting the backup antenna power parameter of the power sub-slice according to the target uplink power parameter. The step of adjusting the backup antenna power parameter of the power sub-slice is a step performed by changing the power level or calibrating the maximum target power or power compensation, or, When the sub-slice is a spectrum sub-slice and there is a difference between the target operating frequency and the current operating frequency, the step of adjusting the operating frequency of the spectrum sub-slice according to the target operating frequency. The service demand parameter is the target operating frequency and the target throughput, the current network parameter is the current operating frequency and the current throughput. When there is a difference between the target throughput and the current throughput, obtaining the target spectrum bandwidth corresponding to the target throughput from the correspondence between the predetermined throughput and the spectrum bandwidth, and the step of adjusting the spectrum bandwidth of the spectrum sub-slice according to the target spectrum bandwidth, or, According to the correspondence relationship between a predetermined throughput and the number of antennas, respectively obtaining a target number of antennas corresponding to a target throughput and a current number of antennas corresponding to a current throughput; the sub-slice is an antenna sub-slice, the service demand parameter is the target throughput, the current network parameter is the current throughput, and adjusting the number of antennas of the antenna sub-slice according to the difference between the target number of antennas and the current number of antennas; according to the correspondence relationship between a predetermined throughput and a single-frequency bandwidth, respectively obtaining a target single-frequency bandwidth corresponding to the target throughput and a current single-frequency bandwidth corresponding to the current throughput; and adjusting the single-frequency bandwidth of the antenna sub-slice according to the difference between the target single-frequency bandwidth and the current single-frequency bandwidth. A method for adjusting a service slice including the above steps.
2. Before the step of adjusting each sub-slice parameter of the application service slice according to the service demand parameter and the current network parameter, obtaining a parameter change value according to the service demand parameter and the current network parameter; further including obtaining an adjustment step and an adjustment method for adjusting each sub-slice parameter of the application service slice according to the parameter change value. The method for adjusting a service slice according to claim 1.
3. When the power sub-slice is a shared power slice, the uplink power parameter includes a new radio NR power parameter and a long-term evolution LTE anchor power parameter. The step of adjusting the uplink power parameter of the power sub-slice according to the target uplink power parameter is The method for adjusting a service slice according to claim 1, comprising the step of adjusting the sizes and ratios of the new radio NR power parameter and the long-term evolution LTE anchor power parameter in the power sub-slice according to the target uplink power parameter.
4. When the spectrum sub-slice is a shared spectrum slice, the operating frequency of the spectrum sub-slice includes the new radio NR operating frequency and the long-term evolution LTE operating frequency, and the spectrum bandwidth of the spectrum sub-slice includes the new radio NR spectrum bandwidth and the long-term evolution LTE spectrum bandwidth. The step of adjusting the operating frequency of the spectrum sub-slice according to the target operating frequency includes the step of adjusting the sizes and ratios of the new radio NR operating frequency and the long-term evolution LTE operating frequency in the spectrum sub-slice according to the target operating frequency. The method for adjusting a service slice according to claim 1, wherein the step of adjusting the spectrum bandwidth of the spectrum sub-slice according to the target spectrum bandwidth includes the step of adjusting the sizes and ratios of the new radio NR spectrum bandwidth and the long-term evolution LTE spectrum bandwidth in the spectrum sub-slice according to the target spectrum bandwidth.
5. The step of obtaining the service demand parameters of the application service slice configured for the terminal is When detecting the application service slice opened by the terminal, collecting the RF information parameter set of the terminal, performing statistical analysis on the RF information parameter set, and obtaining the service demand parameters of the application service slice, or When detecting the application service slice opened by the terminal, obtaining the delay when opening the application service slice and when executing the application service slice, obtaining the opening speed of the application service slice, and obtaining the service demand parameters of the application service slice according to the delay, the speed, and a predetermined target threshold value, or Taking the slice network information transmitted from the received base station as the service demand parameters of the application service slice, or The method for adjusting a service slice according to claim 1, including the step of receiving, by a user interaction interface, the service demand parameters of the application service slice input by a user.
6. After the step of adjusting each sub-slice parameter of the application service slice according to the service demand parameters and the current network parameters, Obtaining the performance parameters when executing the adjusted application service slice, and When the performance parameters meet a predetermined stop condition, stopping the adjustment of the application service slice. The method for adjusting a service slice according to claim 1 further includes these steps.
7. A method for adjusting a service slice, applied to a terminal, Obtaining the service demand parameters of an application service slice configured for the terminal and the current network parameters of the terminal, where the service demand parameters include the service demand parameters of each sub-slice of the application service slice, Adjusting each sub-slice parameter of the application service slice according to the service demand parameters and the current network parameters, and The step of obtaining service demand parameters of an application service slice configured for a terminal is as follows: When detecting the application service slice opened by the terminal, collecting an RF information parameter set of the terminal, performing statistical analysis on the RF information parameter set, and obtaining service demand parameters of the application service slice; or When detecting the application service slice opened by the terminal, obtaining a delay when opening the application service slice and when executing the application service slice, obtaining a speed of opening the application service slice, and obtaining service demand parameters of the application service slice according to the delay, the speed, and a predetermined target threshold; or Taking slice network information transmitted from a received base station as service demand parameters of the application service slice; or Receiving, by a user interaction interface, service demand parameters of the application service slice input by a user, and a method for adjusting a service slice including the above steps.
8. An electronic device, including at least one processor; a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the at least one processor can execute the method for adjusting a service slice according to any one of claims 1 to 7.
9. A computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the computer-readable storage medium can realize the method for adjusting a service slice according to any one of claims 1 to 7.
Citation Information
Patent Citations
Base station, terminal device, method and recording medium
EP3739960A1
Bandwidth adjustment method and apparatus, communication device, and computer readable storage medium
EP3843451A1
Radio communication system, radio communication method, centralized control station, and radio base station
JP2017103553A
Base station, terminal device, method and recording medium
WO2019138753A1