Network slice configuration method and apparatus, network device, and storage medium

Abstract

The application provides a network slice configuration method and device, a network equipment and a storage medium. The network equipment acquires the access state of a target network slice in the network equipment and the terminal identifier, and updates a historical access state mapping table according to the access state to calculate the access failure rate of the terminal within a preset time range. When the access failure rate is greater than a preset threshold, an improvement reminder is generated to adjust the network service corresponding to the terminal, thereby gradually improving the accuracy of the terminal connecting the network slice and improving the accuracy of the network equipment providing the network service for the terminal.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and particularly relates to a network slice configuration method and device, a network equipment and a storage medium. BACKGROUND

[0002] The 5G network slice technology refers to a virtual logical network used on the same network equipment to provide mutually isolated network services for terminals in different application scenarios, so as to meet the differentiated network requirements of different application scenarios.

[0003] In the prior art, the network equipment performs subscription and network service provision of the corresponding 5G network slice according to the application scenario of the terminal described by the user. During the use of the network service provided by the network slice by the terminal, the network service provided by the network slice is poor due to the inconsistency between the actual application scenario of the terminal and the application scenario set in the subscription process of the network slice, which affects the accuracy of the network service provided by the network equipment to the terminal.

[0004] Therefore, how to improve the accuracy of the network service provided by the network equipment to the terminal becomes a problem to be solved. SUMMARY

[0005] The present application provides a network slice configuration method and device, a network equipment and a storage medium to solve the technical problem of improving the accuracy of the network service provided by the network equipment to the terminal.

[0006] In a first aspect, the present application provides a network slice configuration method, which is applied to a network equipment, and the method comprises the following steps:

[0007] obtaining an access state of a terminal in accessing a target network slice in the network equipment and a terminal identifier, wherein the access state comprises access success and access failure;

[0008] updating a historical access state mapping table according to the access state, and calculating an access failure rate of the terminal within a preset time range, wherein the historical access state mapping table represents the corresponding relationship between the terminal identifier and the historical access success times and the historical access failure times;

[0009] when the access failure rate is greater than a preset threshold, generating an improvement prompt to adjust the network service corresponding to the terminal.

[0010] In the above technical solution, the network equipment determines whether the network service provided by the target network slice corresponding to the terminal meets the use scenario of the terminal according to the failure rate of the terminal in accessing the target network slice, so as to generate a corresponding improvement prompt to improve the configuration of the network slice and improve the accuracy of the network service provided by the network equipment to the terminal.

[0011] Optionally, the access state of the terminal in the current access to the target network slice of the network device is obtained, and specifically includes:

[0012] The slice access request sent by the terminal is obtained, wherein the slice access request includes a target slice identifier and a terminal identifier;

[0013] The actual slice identifier accessed by the terminal is obtained according to the terminal identifier and an actual access mapping table, wherein the actual access mapping table represents a one-to-one mapping relationship between the terminal identifier and the network slice identifier actually accessed by the terminal;

[0014] The access state of the terminal in the current access to the target network slice of the network device is obtained according to the target slice identifier and the actual slice identifier accessed by the terminal.

[0015] Optionally, the method further includes:

[0016] The location information of the terminal is obtained;

[0017] The coverage range of the network service provided by the target slice is determined according to the target slice identifier and a coverage mapping table, wherein the coverage mapping table represents a one-to-one mapping relationship between the target slice identifier and the coverage range of the network service provided by the target slice.

[0018] Optionally, the access state of the terminal in the current access to the target network slice of the network device is obtained according to the target slice identifier and the actual slice identifier accessed by the terminal, and specifically includes:

[0019] When the target slice identifier is the same as the actual slice identifier accessed by the terminal, the access state is an access success state;

[0020] When the target slice identifier is different from the actual slice identifier accessed by the terminal, the type of an access failure state is determined according to the location information of the terminal and the coverage range of the target slice, wherein the access failure state includes an in-coverage failure state and an out-of-coverage failure state.

[0021] Optionally, the historical access failure times include in-coverage historical access failure times and out-of-coverage historical access failure times, and the historical access state mapping table is updated according to the access state, and specifically includes:

[0022] When the access state of the terminal is the access success state, the historical access success times in the historical access state mapping table are updated;

[0023] When the access state of the terminal is the in-coverage failure state, the in-coverage historical access failure times in the historical access state mapping table are updated;

[0024] When the access state of the terminal is the out-of-coverage failure state, the out-of-coverage historical access failure times in the historical access state mapping table are updated.

[0025] Optionally, the access failure rate comprises an in-coverage access failure rate and an out-of-coverage access failure rate; the access failure rate of the terminal in the preset time range is calculated, and specifically comprises:

[0026] According to the historical in-coverage access failure times and the total access times in the preset time range, the in-coverage access failure rate of the terminal in the preset time range is calculated.

[0027] According to the historical out-of-coverage access failure times and the total access times in the preset time range, the out-of-coverage access failure rate of the terminal in the preset time range is calculated.

[0028] The total access times are the sum of the successful access times, the historical out-of-coverage access failure times and the historical in-coverage access failure times.

[0029] Optionally, when the access failure rate is greater than a preset threshold, the network service corresponding to the terminal is adjusted, and specifically comprises:

[0030] When the in-coverage access failure rate is greater than a first preset threshold, a network-side prompt for prompting network optimization and network slice coverage enhancement is generated.

[0031] When the out-of-coverage access failure times are greater than a second preset threshold, a terminal prompt for expanding the coverage range of the target slice corresponding to the terminal is generated.

[0032] In the above technical solution, the network device obtains the reason affecting the successful connection of the terminal to the network slice according to the use position of the terminal and the coverage range of the target network slice. When the reason is that the use range of the terminal is inconsistent with the coverage range of the target network slice, a terminal prompt is generated to remind the user to adapt to the network slice and the appropriate coverage range of the subscription, otherwise, a network-side prompt is generated to improve the construction of the network device and optimize the network configuration, thereby gradually improving the accuracy of the network service provided by the network device to the terminal.

[0033] In a second aspect, the application provides a network slice configuration device, comprising:

[0034] An acquisition module is configured to acquire an access state of a terminal in accessing a target network slice of a network device and a terminal identifier; the access state comprises access success and access failure.

[0035] A processing module is configured to acquire historical access success times and historical access failure times corresponding to the terminal according to a historical access state mapping table and the terminal identifier; the historical access state mapping table represents the corresponding relationship between the terminal identifier and the historical access success times and the historical access failure times.

[0036] The processing module is further configured to update a historical access state mapping table according to the access state, and calculate an access failure rate of the terminal within a preset time range.

[0037] The processing module is further configured to generate an improvement prompt to adjust a network service corresponding to the terminal when the access failure rate is greater than a preset threshold.

[0038] In a third aspect, the present application provides an electronic device, comprising a processor and a memory connected with the processor in communication;

[0039] The memory stores computer execution instructions.

[0040] The processor executes the computer execution instructions stored in the memory to implement the network slice configuration method of the first aspect.

[0041] In a fourth aspect, the present application provides a computer readable storage medium, and the computer readable storage medium stores computer instructions, and the computer instructions are executed by the processor to implement the network slice configuration method of the first aspect.

[0042] The present application provides a network slice configuration method, device, network equipment and storage medium, the network equipment acquires the access state of the terminal accessing the target network slice of the network equipment and the terminal identifier, and updates a historical access state mapping table according to the access state, to calculate the access failure rate of the terminal within a preset time range, when the access failure rate is greater than a preset threshold, generates an improvement prompt to adjust the network service corresponding to the terminal, thereby gradually improving the accuracy of the terminal connecting the network slice, to improve the accuracy of the network equipment providing network service to the terminal. BRIEF DESCRIPTION OF DRAWINGS

[0043] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present application and, together with the specification, serve to explain the principles of the application.

[0044] Figure 1 The application scenario diagram of the network slice configuration provided by an embodiment of the present application;

[0045] Figure 2 The flowchart of the network slice configuration method provided by an embodiment of the present application;

[0046] Figure 3 The flowchart of the network slice configuration method provided by another embodiment of the present application;

[0047] Figure 4 The flowchart of the network slice configuration method provided by another embodiment of the present application;

[0048] Figure 5A structural schematic diagram of a network slice configuration device provided by an embodiment of the present application is shown in the figure.

[0049] Figure 6 A structural schematic diagram of a network device provided by an embodiment of the present application is shown in the figure.

[0050] The specific embodiments of the present application have been shown in the above figures, and will be described in more detail hereinafter. These figures and the written description are not intended to limit the scope of the present application in any way, but to illustrate the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0051] The exemplary embodiments will be described in detail herein with reference to the attached drawings. The following description is made with reference to the accompanying drawings in which like reference numerals refer to like elements, unless otherwise indicated. The following exemplary embodiments described herein are not meant to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the appended claims.

[0052] 5G network slice technology refers to a virtual logical network used on the same network device to provide mutually isolated network services for terminals using different application scenarios, so as to meet the differentiated network requirements of different application scenarios.

[0053] In the prior art, the network device provides the corresponding 5G network slice subscription and network service according to the application scenario of the terminal described by the user. During the use of the network service provided by the above network slice by the terminal, the network service provided by the network slice is poor due to the inconsistency between the actual application scenario of the terminal and the application scenario set in the subscription of the above network slice, which affects the accuracy of the network service provided by the network device to the terminal.

[0054] Therefore, how to improve the accuracy of the network service provided by the network device to the terminal becomes a problem to be solved.

[0055] To solve the above technical problems, the embodiments of the present application provide a network slice configuration method, device, network device and storage medium, aiming to solve the problem of improving the accuracy of the network service provided by the network device to the terminal. The technical concept of the present application is to use the success rate of the terminal accessing the target network slice to obtain the accuracy of the network service provided by the network device to the terminal and the reasons affecting the success rate, and to generate a corresponding network improvement reminder according to the above reasons to improve the accuracy of the network service provided by the network device to the terminal.

[0056] Figure 1 The application scenario of the network slice configuration provided by the present application is shown in the figure. Figure 1As shown, it comprises a network device 10 and a terminal 20. The network device 10 comprises a plurality of base stations, a radio access network and a core network device, which is divided into a plurality of network slices according to different application scenarios. The terminal 20 is installed with at least one application program.

[0057] When the user is using the application program installed in the terminal 20, and the application program needs network service support, the terminal determines the corresponding network slice identifier according to the network service required by the application program, and sends a request for using the network slice to the base station in the network device. The base station transmits the request to the core network device through the radio access network. In the case of meeting the network slice use condition, the network slice provides network service for the terminal. The network service of the network slice is the network service of the corresponding network slice purchased by the user of the terminal at the corresponding operator of the network device according to the preset demand.

[0058] Figure 2 A flowchart of a network slice configuration method according to an exemplary embodiment of the present application is shown. As shown, the network slice configuration method provided by the present application comprises: Figure 2

[0059] S201, the network device acquires the access state of the terminal accessing the target network slice in the network device and the terminal identifier.

[0060] The network slice is a plurality of logically independent networks divided in the network entity formed in the network device, which is used to provide a specific type of network service. For example, network slice A is used to provide network service with higher delay requirement, and network slice B is used to provide network service with high network sensitivity in the process of terminal spatial movement.

[0061] The target network slice is the network slice corresponding to the network service purchased in advance by the user of the terminal at the corresponding operator of the network device according to the preset demand.

[0062] The access state of the target network slice refers to the state of judging whether the network slice actually accessed by the terminal in this connection is consistent with the target network slice. The access state includes access success and access failure. When the access state of the target network slice is access failure, the terminal will access the network slice providing default and basic network service.

[0063] When the actually accessed network slice is consistent with the target network slice, the access state of the target network slice is access success; when the actually accessed network slice is not consistent with the target network slice, the access state of the target network slice is access failure.

[0064] The terminal identifier is an identifier for distinguishing the terminal applying for this connection of the target network slice from other terminals.​

[0065] S202, the network device updates the historical access state mapping table according to the access state, and calculates an access failure rate of the terminal within a preset time range.

[0066] The access state is obtained from step S201.

[0067] The historical access state mapping table represents a correspondence between the terminal identifier and the historical access success times and the historical access failure times.

[0068] The access failure rate is calculated by the network device according to the historical access success times and the historical access failure times obtained within the preset time range in the historical access state mapping table. More specifically, the access failure rate is a ratio of the access failure times to the total access times. The total access times are a sum of the access success times and the access failure times.

[0069] S203, when the access failure rate is greater than a preset threshold, the network device generates an improvement prompt to adjust the network service corresponding to the terminal.

[0070] The access failure rate is obtained from step S202.

[0071] The preset threshold is set according to the minimum requirement of the network device for the network service failure rate provided for the terminal.

[0072] The improvement prompt is used to remind the operator corresponding to the network device or the user using the terminal to improve the network service currently adopted by the terminal.

[0073] In the above technical solution, the network device judges whether the network service provided by the target network slice corresponding to the terminal meets the use scenario of the terminal according to the failure rate of the terminal accessing the target network slice, so as to generate a corresponding improvement prompt to perfect the configuration of the network slice and improve the accuracy of the network service provided by the network device for the terminal.

[0074] Figure 3 A flowchart of a network slice configuration method provided by the present application according to an embodiment is shown. The execution subject of the method is a network device. As shown in the figure, the network slice configuration method provided by the present application comprises: Figure 3

[0075] S301, obtaining a slice access request sent by a terminal.

[0076] The slice access request comprises a target slice identifier and a terminal identifier. The target slice identifier is a slice identifier stored locally when the terminal confirms the network service provided by the network slice in the network device for the first time.

[0077] S302, obtaining an actual slice identifier accessed by the terminal according to the terminal identifier and an actual access mapping table.​

[0078] The terminal identifier is obtained from step S301.

[0079] The network device determines the network slice identifier that the terminal actually accesses by querying the terminal identifier in the actual access mapping table corresponding to the current time stored locally. The actual access mapping table represents a one-to-one mapping relationship between the terminal identifier and the network slice identifier that the terminal actually accesses.

[0080] S303, obtain the location information of the terminal.

[0081] The location information of the terminal can be obtained through the GPS positioning information of the terminal. The information can be obtained by querying the corresponding server, or can be obtained by the application program installed on the terminal that can obtain the user's location information.

[0082] S304, determine the coverage range of the network service provided by the target slice according to the target slice identifier and the coverage mapping table.

[0083] The target slice identifier is obtained from step S301.

[0084] The coverage mapping table represents a one-to-one mapping relationship between the target slice identifier and the coverage range of the network service provided by the target slice.

[0085] The network coverage range provided by the target slice is determined according to the network device installed and set in the area where the terminal is located. When there is a network slice for providing corresponding services in the network device installed in the area where the terminal is located, the area is within the network coverage range corresponding to the target slice.

[0086] S305, obtain the access state of the terminal accessing the target network slice in the network device this time according to the target slice identifier and the actual slice identifier accessed by the terminal.

[0087] The target slice identifier is obtained from step S301, and the actual slice identifier is obtained from step S02.

[0088] The access state of the target network slice includes an access success state and an access failure state.

[0089] The process of determining the access state of the terminal accessing the target slice in the network device this time according to the target slice identifier and the actual slice identifier accessed by the terminal is as follows:

[0090] When the target slice identifier is the same as the actual slice identifier accessed by the terminal, the access state is the access success state.

[0091] When the target slice identifier is different from the actual slice identifier accessed by the terminal, a type of access failure state is determined according to the location information of the terminal and the coverage range of the target slice.

[0092] The location information of the terminal is obtained from step S303. The coverage range of the target slice is obtained from step S304.

[0093] The access failure state includes an in-coverage failure state and an out-of-coverage failure state.

[0094] More specifically, the state in which the terminal fails to connect within the coverage range of the corresponding network slice is the in-coverage failure state, and the reason for the failure includes that the network coverage area in the region is not complete or the bandwidth configured by the network device for the region is less than the daily required bandwidth of the region.

[0095] The state in which the terminal fails to connect outside the coverage range of the corresponding network slice is the out-of-coverage failure state, and the reason for the failure includes that the region in which the terminal uses the network slice greatly deviates from the coverage range of the network slice that provides network services according to the preset demand or the network service required by the user does not match the network service of the currently owned network slice.

[0096] S306, updating the historical access state mapping table according to the access state.

[0097] The access state is obtained from step S305.

[0098] The historical access state mapping table represents the correspondence between the terminal identifier and the historical access success number and the historical access failure number.

[0099] According to the type of access failure state, the historical access failure number includes an in-coverage historical access failure number and an out-of-coverage historical access failure number, that is, the access state in the historical access state mapping table includes an access success state, an in-coverage failure state, and an out-of-coverage failure state.

[0100] More specifically, the process of updating the historical access state mapping table according to the above three access states is as follows:

[0101] When the access state of the terminal is the access success state, the historical access success number in the historical access state mapping table is updated.

[0102] The historical access success number in the updated historical access state mapping table is the historical access success number in the updated historical access state mapping table plus 1.

[0103] When the access state of the terminal is the in-coverage failure state, the in-coverage historical access failure number in the historical access state mapping table is updated.

[0104] wherein the updated number of in-coverage historical access failures in the historical access state mapping table is the number of in-coverage historical access failures in the historical access state mapping table plus 1.

[0105] When the access state of the terminal is the out-of-coverage failure state, update the number of out-of-coverage historical access failures in the historical access state mapping table.

[0106] wherein the updated number of out-of-coverage historical access failures in the historical access state mapping table is the number of in-coverage historical access failures in the historical access state mapping table plus 1.

[0107] S307, calculate an access failure rate of the terminal in a preset time range.

[0108] wherein the access failure rate comprises an in-coverage access failure rate and an out-of-coverage access failure rate.

[0109] More specifically, according to the type of the access failure state, the access failure rate is calculated respectively:

[0110] When the type of the access failure state is the in-coverage access failure state, calculate the in-coverage access failure rate of the terminal in the preset time range according to the number of in-coverage historical access failures and the total number of accesses in the preset time range.

[0111] The in-coverage access failure rate is the quotient of the number of in-coverage historical access failures divided by the total number of accesses.

[0112] The total number of accesses is the sum of the number of access successes, the number of out-of-coverage historical access failures and the number of in-coverage historical access failures. Wherein the number of access successes, the number of out-of-coverage historical access failures and the number of in-coverage historical access failures are all obtained from step S306.

[0113] When the type of the access failure state is the out-of-coverage access failure state, calculate the out-of-coverage access failure rate of the terminal in the preset time range according to the number of out-of-coverage historical access failures and the total number of accesses in the preset time range.

[0114] The out-of-coverage access failure rate is the quotient of the number of out-of-coverage historical access failures divided by the total number of accesses. Wherein the number of out-of-coverage historical access failures is obtained from step S306.

[0115] Wherein the explanation of the total number of accesses has been explained in detail in the process of calculating the in-coverage access failure rate, which will not be repeated here.

[0116] S308, when the access failure rate is greater than the preset threshold, generating an improvement prompt to adjust the network service corresponding to the terminal.

[0117] More specifically, according to the type of failure rate, the type of corresponding improvement prompt generated is also different. Among them, the failure rate includes: the access failure rate in the coverage range and the access failure rate outside the coverage range. The above two failure rates are obtained from step S307.

[0118] According to the type of access failure state, the access failure rate and the corresponding preset threshold are compared to generate an improvement prompt as follows:

[0119] When the access failure rate in the coverage range is greater than the first preset threshold, a network-side prompt is generated to prompt network optimization and network slice coverage enhancement.

[0120] Among them, network optimization includes expanding the network equipment in the terminal corresponding network slice to allocate more bandwidth when providing network service to ensure normal use of the network by the user.

[0121] Network slice coverage enhancement means increasing the infrastructure of network equipment in the area corresponding to the target network slice to enhance the weak area of network service in the area or the vulnerability area that cannot use the network service.

[0122] When the number of access failures outside the coverage range is greater than the second preset threshold, a terminal prompt is generated to expand the coverage range of the target slice corresponding to the terminal.

[0123] Expanding the coverage range of the target slice corresponding to the terminal includes expanding the range of network service provided by the target slice and binding another network slice to the terminal to obtain the network service provided by another network slice. Among them, the network service coverage range of another network slice is inconsistent with the network service coverage range of the target network slice.

[0124] In the above technical solution, the network equipment obtains the reason affecting the successful connection of the terminal to the network slice according to the use position of the terminal and the coverage range of the target network slice. When the above reason is that the use range of the terminal is inconsistent with the coverage range of the target network slice, a terminal prompt is generated to remind the user to adapt to the network slice and the appropriate coverage range of the subscription, otherwise, a network-side prompt is generated to improve the construction of the network equipment and optimize the network configuration, thereby gradually improving the accuracy of the network service provided by the network equipment to the terminal.

[0125] Figure 4 The flowchart of the network slice configuration method provided by another embodiment of the present application is shown in the figure. The execution subject of the method is a network equipment. As shown in the figure, the network slice configuration method provided by the present application comprises: Figure 4

[0126] ​S401. Obtain a target network slice identifier to be accessed by a terminal and a terminal identifier.

[0127] The target network slice identifier to be accessed by the terminal and the terminal identifier are obtained according to a slice access request sent by the terminal to the network device. The slice access request includes the target slice identifier and the terminal identifier.

[0128] More specifically, the target network slice identifier has been explained in detail in step S301, and will not be repeated here.

[0129] S402. Determine the coverage range corresponding to the network slice according to the target network slice identifier.

[0130] The target slice identifier is obtained from step S401.

[0131] The coverage range corresponding to the network slice is obtained by querying the target network slice identifier in the coverage mapping table. The coverage mapping table and the corresponding coverage range have been explained in detail in step S304, and will not be repeated here.

[0132] S403. Obtain a network slice identifier actually accessed by the terminal according to the terminal identifier.

[0133] The terminal identifier is obtained from step S401.

[0134] The network slice identifier actually accessed by the terminal is obtained by querying the terminal identifier in the actual access mapping table stored locally. The actual access mapping table represents a one-to-one mapping relationship between the terminal identifier and the network slice identifier actually accessed by the terminal.

[0135] S404. Determine whether the network slice identifier accessed by the terminal is the target slice identifier.

[0136] The network slice identifier accessed by the terminal is obtained in step S403. The target slice identifier is obtained in step S401.

[0137] When the network slice identifier accessed by the terminal is the target slice identifier, the terminal access is successful this time, and step S405 is entered; otherwise, the terminal access fails this time, and step S406 is entered.

[0138] S405. Update the number of historical access successes.

[0139] The number of historical access successes is the number of historical access successes within a preset time range.

[0140] The updated number of historical access successes is the number of historical access successes before updating plus 1.

[0141] After completing this step, the current process is ended.

[0142] S406, acquire the user position and determine whether the position is in the coverage range of the target network slice.

[0143] The acquisition of the user position has been explained in detail in step S303, and will not be repeated here.

[0144] The coverage range of the target network slice is acquired from step S402.

[0145] When the user position is in the above coverage range, go to step S407; otherwise, go to step S410.

[0146] S407, update the number of historical access failures in the coverage range and calculate the access failure rate in the coverage range.

[0147] The number of historical access failures in the coverage range is the number of historical access failures in the coverage range within the preset time range, which is the same as the preset time range in step S405.

[0148] The updated number of historical access failures in the coverage range is the number of historical access failures in the coverage range before updating plus 1.

[0149] The access failure rate in the coverage range is the quotient of the number of historical access failures in the coverage range and the total number of accesses. The total number of accesses is the sum of the number of successful accesses, the number of historical access failures outside the coverage range, and the number of historical access failures in the coverage range.

[0150] S408, determine whether the access failure rate in the coverage range is greater than a first preset threshold.

[0151] The access failure rate in the coverage range is acquired from step S407.

[0152] When the above failure rate is greater than the first preset threshold, go to step S409; otherwise, end the current process to wait for the next terminal connection to the network slice.

[0153] S409, generate a network end prompt for prompting network optimization and network slice coverage enhancement.

[0154] The network end prompt has been explained in detail in step S308, and will not be repeated here.

[0155] S410, update the number of historical access failures outside the coverage range and calculate the access failure rate in the coverage range.

[0156] The number of historical access failures outside the coverage range is the number of historical access failures outside the coverage range within the preset time range, which is the same as the preset time range in step S405.

[0157] The updated number of historical access failures outside the coverage area is the same as the number of historical access failures outside the coverage area before the update plus 1.

[0158] The access failure rate outside the coverage area is the quotient of the historical access failure count outside the coverage area divided by the total number of access attempts. The total number of access attempts has been explained in detail in step S407 and will not be repeated here.

[0159] S411. Determine whether the access failure rate outside the coverage area is greater than the second preset threshold.

[0160] The access failure rate outside the coverage area is obtained from step S410.

[0161] When the failure rate exceeds the second preset threshold, proceed to step S411; otherwise, end the current process to wait for the next connection of the terminal to the network slice.

[0162] S412. Generate a terminal notification to expand the coverage of the target slice corresponding to the terminal.

[0163] The terminal reminder has been explained in detail in step S308, and will not be repeated here.

[0164] In the above technical solution, the network device obtains the accuracy of the network service provided by the network device to the terminal and the reasons affecting the accuracy by collecting the number of successful accesses and failed accesses when the terminal connects to the target network slice. In order to generate corresponding reminders to adjust the network service corresponding to the terminal, the accuracy of the terminal connecting to the network slice is gradually improved, thereby improving the accuracy of the network service provided by the network device to the terminal.

[0165] like Figure 5 As shown, one embodiment of this application provides a network slicing configuration device 500, which includes:

[0166] The acquisition module 501 is used to acquire the access status and terminal identifier of the target network slice in the network device accessed by the terminal this time. The access status includes successful access and access failure.

[0167] The processing module 502 is used to obtain the number of historical successful access attempts and the number of historical failed access attempts for a terminal based on the historical access status mapping table and the terminal identifier. The historical access status mapping table represents the correspondence between the terminal identifier and the number of historical successful access attempts and the number of historical failed access attempts.

[0168] The processing module 502 is also used to update the historical access status mapping table according to the access status, and calculate the access failure rate of the terminal within a preset time range.

[0169] The processing module 502 is further configured to generate an improvement prompt to adjust the network service corresponding to the terminal when the access failure rate is greater than a preset threshold.

[0170] As shown in the above embodiments, an embodiment of the present application provides a network device 600, which comprises a memory 601 and a processor 602. Figure 6

[0171] The memory 601 is configured to store computer instructions executable by the processor.

[0172] The processor 602 implements each step in the network slice configuration method in the above embodiments when executing the computer instructions. For details, refer to the related description in the foregoing method embodiments.

[0173] Optionally, the memory 601 can be independent or integrated with the processor 602. When the memory 601 is independently arranged, the server 600 further comprises a bus for connecting the memory 601 and the processor 602.

[0174] The present application further provides a computer readable storage medium, which stores computer instructions. When the processor executes the computer instructions, each step in the network slice configuration method in the above embodiments is implemented.

[0175] The present application further provides a computer program product, which comprises computer instructions. When the processor executes the computer instructions, each step in the network slice configuration method in the above embodiments is implemented.

[0176] Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. The present application is intended to cover any variations, uses or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice in the art to which the application pertains. The specification and examples are to be regarded as exemplary only, and the true scope and spirit of the application are indicated by the following claims.

[0177] It should be understood that the application is not limited to the precise construction that has been described above and shown in the accompanying drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the application. The scope of the application is limited only by the appended claims.​

Claims

1. A network slicing configuration method, characterized in that, The method is applied to a network device, and the method includes: Obtain the access status and terminal identifier of the target network slice in the network device during this access by the terminal; wherein, the access status includes access success status and access failure status, and the access failure status includes failure status within coverage area and failure status outside coverage area; Based on the access status, the historical access status mapping table is updated, and the access failure rate of the terminal within a preset time range is calculated; wherein, the historical access status mapping table represents the correspondence between the terminal identifier and the number of historical successful accesses and the number of historical access failures, the number of historical access failures includes the number of historical access failures within the coverage area and the number of historical access failures outside the coverage area; the access failure rate includes the access failure rate within the coverage area and the access failure rate outside the coverage area; When the access failure rate within the coverage area exceeds the first preset threshold, a network-side alert is generated to prompt network optimization and network slicing coverage enhancement. When the number of access failures outside the coverage area exceeds the second preset threshold, a terminal reminder is generated to expand the coverage area of ​​the target slice corresponding to the terminal.

2. The method according to claim 1, characterized in that, Obtaining the access status of the target network slice in the network device during this terminal access, specifically includes: Obtain the slice access request sent by the terminal; wherein the slice access request includes a target slice identifier and the terminal identifier; The actual slice identifier accessed by the terminal is obtained based on the terminal identifier and the actual access mapping table; wherein, the actual access mapping table represents a one-to-one mapping relationship between the terminal identifier and the network slice identifier actually accessed by the terminal; Based on the target slice identifier and the actual slice identifier accessed by the terminal, the access status of the target network slice in the network device accessed by the terminal this time is obtained.

3. The method according to claim 2, characterized in that, The method further includes: Obtain the location information of the terminal; The coverage area of ​​the network service provided by the target slice is determined based on the target slice identifier and the coverage mapping table; wherein, the coverage mapping table represents a one-to-one mapping relationship between the target slice identifier and the coverage area of ​​the network service provided by the target slice.

4. The method according to claim 3, characterized in that, Based on the target slice identifier and the actual slice identifier accessed by the terminal, the access status of the terminal's current access to the target network slice in the network device is obtained, specifically including: When the target slice identifier is the same as the actual slice identifier accessed by the terminal, the access status is a successful access status; When the target slice identifier is different from the actual slice identifier accessed by the terminal, the type of access failure state is determined based on the location information of the terminal and the coverage area of ​​the target slice.

5. The method according to claim 4, characterized in that, Update the historical access status mapping table according to the access status, specifically including: When the terminal's access status is successful, update the historical access success count in the historical access status mapping table; When the access status of the terminal is a failure status within the coverage area, update the number of historical access failures within the coverage area in the historical access status mapping table; When the terminal's access status is out of coverage and fails, update the number of historical access failures outside the coverage area in the historical access status mapping table.

6. The method according to claim 5, characterized in that, Calculating the access failure rate of the terminal within a preset time range specifically includes: The access failure rate of the terminal within the coverage area of ​​the preset time range is calculated based on the number of historical access failures and the total number of access failures within the coverage area of ​​the preset time range. The access failure rate of the terminal outside the coverage area within the preset time range is calculated based on the number of historical access failures and the total number of access failures outside the coverage area within the preset time range. The total number of access attempts is the sum of the number of successful access attempts, the number of historical access failures outside the coverage area, and the number of historical access failures within the coverage area.

7. A network slicing configuration device, characterized in that, include: The acquisition module is used to acquire the access status of the target network slice in the network device accessed by the terminal this time and the terminal identifier; wherein, the access status includes access success status and access failure status, and the access failure status includes failure status within coverage area and failure status outside coverage area; The processing module is used to obtain the number of historical successful accesses and the number of historical failed accesses corresponding to the terminal based on the historical access status mapping table and the terminal identifier; wherein, the historical access status mapping table represents the correspondence between the terminal identifier and the number of historical successful accesses and the number of historical failed accesses; The processing module is also used to update the historical access status mapping table according to the access status, and calculate the access failure rate of the terminal within a preset time range. The number of historical access failures includes the number of historical access failures within the coverage area and the number of historical access failures outside the coverage area; the access failure rate includes the access failure rate within the coverage area and the access failure rate outside the coverage area. The processing module is also used to generate a network-side alert for network optimization and network slicing coverage enhancement when the access failure rate within the coverage area is greater than a first preset threshold. When the number of access failures outside the coverage area exceeds the second preset threshold, a terminal reminder is generated to expand the coverage area of ​​the target slice corresponding to the terminal.

8. A network device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer instructions; When executing the computer instructions, the processor is used to implement the network slice configuration method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, are used to implement the network slice configuration method as described in any one of claims 1 to 6.

Images