WO2022268117A1

WO2022268117A1 - 5g slice test method, apparatus and system, and storage medium

Info

Publication number: WO2022268117A1
Application number: PCT/CN2022/100418
Authority: WO
Inventors: 宋丹; 孔露婷; 刘军; 李男
Original assignee: 中国移动通信有限公司研究院; 中国移动通信集团有限公司
Priority date: 2021-02-07
Filing date: 2022-06-22
Publication date: 2022-12-29
Also published as: CN113259983A; CN112867054A; CN113259983B

Abstract

Disclosed are a 5G slice test method, apparatus and system, and a storage medium. The method comprises: configuring a test parameter associated with a network slice service for a terminal; in the process that the terminal performs the network slice service, performing at least two test processes on the terminal to obtain the test result of the test index of each test process, the at least two test processes are used for testing the test index of the terminal in a multi-network slice service concurrence scenario, or used for testing the test index of the terminal in a single network slice service scenario; and generating a test result for the terminal using the test result of the test index of each test process.

Description

5G slice test method, device, test system and storage medium

Cross References to Related Applications

This disclosure claims priority to Chinese Patent Application No. 202110690681.9 filed in China on June 22, 2021, the entire contents of which are hereby incorporated by reference.

technical field

The present disclosure relates to the technical field of equipment testing, and in particular to a 5G slice testing method, device, testing system and storage medium.

Background technique

In order to meet the increasing service requirements, in the fifth generation communication mobile technology (5G), a network slicing (also called slicing) technology is proposed. Network slicing technology can provide differentiated services for different user groups, and set different quality of service (Quality of Service, QoS) and data network name (Data Network Name, DNN) on a user-by-user basis within the slice; the slicing function supported is 5G Distinguishing features from other existing communication systems.

In related technologies, there is no technical solution for testing network slicing.

Contents of the invention

In order to solve related technical problems, embodiments of the present disclosure provide a 5G slice test method, device, test system, and storage medium.

The technical scheme of the embodiment of the present disclosure is realized in this way:

An embodiment of the present disclosure provides a 5G slice test method, including:

Configure the test parameters associated with the network slicing service to the terminal;

During the process of the terminal performing network slicing services, at least two test procedures are executed on the terminal to obtain the test results of the test indicators of each test procedure; the at least two test procedures are used to test multi-network slicing services A test indicator of the terminal in a concurrent scenario, or a test indicator for testing the terminal in a single network slice business scenario;

The test results for the terminal are generated by using the test results of the test indicators of each test process.

In the above scheme, the indicators of each test process are different, and the business of each test process is the same;

Or, the indicators of each test process are the same, and the business of each test process is different;

Or, the indicators of each test process are different, and the business of each test process is different.

In the above solution, in the scenario of concurrent multi-network slicing services, the number of services is N, and the number of network slices is M; M is less than or equal to N; M and N are both integers.

In the above scheme, at least two services use the same network slice or each service uses a network slice;

Execute a test process for each service or execute a test process on the protocol data unit session (Protocol Data Unit Session, PDU Session) of each network slice.

In the above solution, it also includes: configuring at least two PDU Sessions to the terminal;

Execute at least two services in parallel on at least two PDU Sessions.

In the above solution, it also includes: configuring a PDU Session on a network slice to the terminal, wherein the one PDU Session corresponds to at least two services;

Executing the at least two services in parallel on the one PDU Session.

In the above solution, when the test indicators of each test process are different, the test indicators of each test process are related to each other.

In the above solution, the test parameters associated with the network slicing service include at least one of the following:

Parameters used to characterize network slices;

Parameters used to characterize business attributes;

Parameters of the UE Route Selection Policy (URSP).

In the above solution, the parameters used to characterize the network slice include at least one of the following:

Network slice identification;

QoS;

and / or,

The parameters used to characterize business attributes include at least one of the following:

Business application identification;

Business fully qualified domain name (Fully Qualified Domain Name, FQDN) information;

The Internet Protocol (IP) triplet information of the business;

Business DNN information;

Service connection capability (Connection Capability, CC) information.

In the above solution, the two test procedures include a first test procedure and a second test procedure; the first test procedure and the second test procedure include one or a combination of the following test indicators:

Downlink throughput;

delay;

Uplink throughput;

power consumption.

In the above solution, a virtual network environment is constructed; the network slicing service performed on the terminal is a service of the virtual network environment.

In the above solution, the value of the test parameter is configured once for the terminal; during the process of the terminal performing the network slicing service, the at least two test procedures are sequentially executed for the terminal;

Based on the obtained test results of the test indicators of the test process and corresponding test judgment conditions, the test results for the terminal are generated; the test judgment conditions are used to judge the success or failure of the test of the corresponding test process.

In the above scheme, when the test result obtained by the first test process in the at least two test processes does not meet the test judgment condition, the test is ended; the first test process is the at least two test processes executed sequentially except the last one Other testing processes outside the testing process.

In the above solution, the value of the test parameter is configured once for the terminal; during the process of the terminal performing the network slicing service, the at least two test procedures are executed in parallel for the terminal;

Based on the test results of the test indicators of each test process and the corresponding test judgment conditions, the test results for the terminal are generated; the test judgment conditions are used to judge the success or failure of the corresponding test process.

In the above solution, Q times of test parameters are configured to the terminal; Q is an integer greater than or equal to 2; each time a test parameter is configured, the terminal performs the at least Two test procedures;

Based on the test results of the test indicators of the test process obtained each time and the corresponding test judgment conditions, the test results for the terminal are generated; the test judgment conditions are used to judge the success or failure of the test of the corresponding test process.

In the above scheme, during each sequential execution of the at least two test procedures for the terminal, when the test value of the test index obtained by the first test procedure in the at least two test procedures does not meet the test judgment condition , to end the test; the first test process is a test process except the last test process among the at least two test processes executed sequentially.

In the above scheme, Q times of test parameters are configured to the terminal; Q is an integer greater than or equal to 2; each time a test parameter is configured, the terminal performs the at least Two test procedures;

An embodiment of the present disclosure also provides a 5G slice test device, including:

The configuration unit is used to configure test parameters associated with the network slicing service to the terminal;

The test unit is configured to execute at least two test procedures on the terminal during the network slicing service process of the terminal, and obtain the test results of the test indicators of each test procedure; the at least two test procedures are used for testing The test index of the terminal in the multi-network slicing business concurrent scenario, or used to test the test index of the terminal in the single network slicing business scenario; use the test result of the test index of each test process to generate the test index for the terminal test results.

An embodiment of the present disclosure also provides a 5G slice test system, including: a processor and a communication interface; wherein,

said processor for:

Configuring test parameters associated with the network slicing service to the terminal through the communication interface; and performing at least two test procedures on the terminal during the process of performing the network slicing service on the terminal, to obtain the test index of each test procedure Test results; the at least two test procedures are used to test the test indicators of the terminal in a multi-network slice business scenario, or to test the test indicators of the terminal in a single network slice business scenario; and use each The test result of the test indicator of the test process generates a test result for the terminal.

An embodiment of the present disclosure also provides a 5G slice test system, including: a processor and a memory for storing a computer program that can run on the processor,

Wherein, when the processor is configured to run the computer program, it executes the steps of any one of the above methods.

An embodiment of the present disclosure also provides a storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of any one of the above methods are implemented.

The test method, device, test system and storage medium provided by the embodiments of the present disclosure configure the test parameters associated with the network slicing service to the terminal; during the process of the terminal performing the network slicing service, at least two tests are performed on the terminal The process is to obtain the test results of the test indicators of each test process; the at least two test processes are used to test the test indicators of the terminal in the multi-network slicing business concurrent scenario, or to test the single network slicing business scenario. The test index of the terminal; using the test result of the test index of each test process to generate the test result for the terminal, the solution of the embodiment of the present disclosure performs the test through at least two test processes for network slicing, The test results of the test indicators of each test process are used to generate the test results of the network slicing service, thereby realizing multi-dimensional testing, which can meet the test requirements of performance indicators in different application scenarios, improve test efficiency, and improve test results to reflect the terminal Confidence in real performance.

Description of drawings

FIG. 1 is a schematic flow diagram of a method for testing 5G slices according to an embodiment of the present disclosure;

FIG. 2 is a schematic diagram of a multi-dimensional 5G slice test process according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of another multi-dimensional 5G slice test process according to an embodiment of the present disclosure;

4 is a schematic structural diagram of a 5G slice test device according to an embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of a 5G slice test system according to an embodiment of the present disclosure.

detailed description

The present disclosure will be further described in detail below in conjunction with the accompanying drawings and embodiments.

When testing network slicing services, you can use the "single input-single output" test method, that is, input one line of measurement input, and obtain one line of test output through one line of test output. Whether the test passed. The test method of "multiple input-single output" can also be used, that is, input multiple measurement input quantities, and obtain one test output quantity through multiple measurement input quantities. Through this test output quantity, it can be judged whether the test is passed or not. That is, a single dimension is used to describe the test results. However, for network slicing, describing test results by a single dimension is usually not enough. Therefore, it is necessary to introduce multi-dimensional testing methods.

Based on this, in various embodiments of the present disclosure, the test is performed through at least two test procedures for the network slicing service, and the test results of the performance indicators of each test procedure are used to generate test results.

An embodiment of the present disclosure provides a 5G slice test method, which is applied to a test system, as shown in FIG. 1 , the method includes:

Step 101: configure test parameters associated with the network slicing service to the terminal;

Step 102: During the process of the terminal performing network slicing services, execute at least two test procedures on the terminal to obtain the test results of the test indicators of each test procedure; the at least two test procedures are used to test multiple The test indicators of the terminal in the concurrent network slicing business scenario, or the test indicators used to test the terminal in the single network slicing business scenario;

Step 103: Using the test results of the test indicators of each test process, generate test results for the terminal.

Wherein, in actual application, since the test object is a terminal, the terminal may also be called a test terminal or a verification terminal. Since the test network slicing service performance test is performed on the terminal, the target performance index can be determined based on the service performance requirements; then, the target test parameters can be determined according to the target performance index, so that the network slicing service can be associated with the terminal configuration based on the target test parameters test parameters; correspondingly, at least two test procedures for measuring target performance indicators based on the target test parameters are generated.

Here, the network slicing service refers to a service using network slicing. Specifically, it may be 5G network slicing.

In practical applications, in the scenario of concurrent multi-network slicing services, two factors, network slicing and services, need to be considered. Therefore, the following relationship can exist between network slicing and the number of services:

The number of services is N, and the number of network slices is M; M is less than or equal to N; both M and N are integers.

That is to say, one network slice can be used by multiple services, or one network slice can be used by one service. Therefore, in actual application, the following situations can occur:

In the first case, at least two services use the same network slice; a test process is executed for each of the at least two services; for example, the terminal has service A and service B, and both service A and service B use Slice 1, execute test process A for business A, and test process B for business B;

In the second case, at least two services use the same network slice; a test process is executed on the PDU Session of each network slice; the terminal has services A, B, and C; among them, service A and service B both use slice 1, and service C uses slice 2; execute test process A on the PDU Session corresponding to slice 1 for service A, and test process B on the PDU Session corresponding to slice 2 for service C;

In the third case, each service uses a network slice (that is, each service uses a different network slice), and executes a test process on the PDU Session of each network slice; for example, the terminal has service A and service B; Among them, service A uses slice 1, and service B uses slice 2; for service A, test process A is executed on the PDU Session corresponding to slice 1, and for service B, test process B is executed on the PDU Session corresponding to slice 2.

In the fourth case, at least two services use the same PDU Session on the same network slice, and execute a test process for each service of the PDU Session, that is, execute multiple test processes in parallel on the PDU Session. Exemplarily, the terminal has business A and business B; wherein, both business A and business B use PDU Session 1 of slice 1; for business A, test procedure A is executed on PDU Session 1 of slice 1, and for business B in Execute test process B on PDU Session1.

It can be seen from the above description that in the scenario of concurrent multi-network slicing services, at least two services use the same network slice or each service uses one network slice; Execute a test process on the PDU Session.

Wherein, in the case of executing a test process on the PDU Session of each network slice, when configuring the test parameters associated with the network slice service to the terminal, at least two PDU Sessions need to be configured to the terminal, so as to realize multiple The concurrency of network slicing services means that at least two services are executed in parallel on at least two PDU Sessions.

Wherein, in the case where the one PDU Session corresponds to at least two services, when configuring the test parameters associated with the network slice service to the terminal, it is necessary to configure a PDU Session on a network slice to the terminal, where , the one PDU Session corresponds to at least two services; and, the at least two services are executed in parallel on the one PDU Session.

Specifically, for each PDU Session, it is necessary to receive the PDU Session connection establishment request sent by the terminal; the request carries the corresponding parameters and network slice identifiers used to characterize the service attributes; and sends a PDU Session establishment completion message to the terminal; in the message It carries corresponding parameters used to characterize network slices and parameters used to characterize service attributes.

Exemplarily, assuming that two PDU Sessions are configured, for the first PDU Session, the terminal initiates a PDU Session connection establishment request; the request carries the parameters and network slice identifiers corresponding to the first PDU Session for representing service attributes; the test system sends The terminal sends a PDU Session establishment completion message; the message carries parameters corresponding to the first PDU Session for representing network slices and parameters for representing service attributes; for the second PDU Session, the terminal also initiates the establishment of a PDU Session connection Request; the request carries the parameters corresponding to the second PDU Session used to characterize the service attributes and the network slice identifier; the test system sends a PDU Session establishment completion message to the terminal; the message carries the parameters corresponding to the second PDU Session used to characterize the network Parameters of slices and parameters used to characterize business attributes.

Correspondingly, in the case where the at least two test procedures are used to test the test indicators of the terminal in a single network slicing service scenario, the at least two test procedures are executed on the PDU Session of the first network slicing service; Exemplarily, the terminal has service A; wherein, service A uses slice 1, and test process A and test process B are executed on the PDU Session corresponding to slice 1 for the service.

In actual application, the test indicators of each test process are different and/or the business of each test process is different; specifically, the indicators of each test process are different, and the business of each test process is the same; it can also be that each test process The indicators of each test process are the same, and the business of each test process is different; it is also possible that the indicators of each test process are different, and the business of each test process is different.

Wherein, each test process can test a test indicator (also called a performance indicator); in the case that the test indicators of each test process are different, the test indicators of each test process can be correlated with each other.

Here, the association may include at least one of the following: positive correlation; negative correlation; the test index measured by one test process and the test index measured by another test process are mutual results. The positive correlation means that the test index measured by one test process increases with the increase of the test index measured by another test process, or decreases with the decrease of the test index measured by another test process. Negative correlation means that the test index measured by one test process decreases with the increase of the test index measured by another test process, or increases with the decrease of the performance index measured by another test process. Mutual results means: the test result of one test process (such as the measured test index) can be used as the test parameter configuration or test condition of another test process, and the test result of another test process can also be used as the test result of the one test process. Test parameter configuration or test conditions.

In an embodiment, the test parameters associated with the network slicing service may include at least one of the following:

Parameters used to characterize network slices;

Parameters used to characterize business attributes;

URSP parameters.

Wherein, in an embodiment, the parameters used to characterize network slices include at least one of the following:

Network slice identification;

QoS.

Here, in actual application, the network slice identifier may include Single Network Slice Selection Assistance Information (S-NSSAI), which may also be called Network Slice Selection Assistance Information (NSSAI) .

In one embodiment, the parameters used to characterize business attributes include at least one of the following:

Business application identification;

FQDN information of the business;

Service IP triplet information;

Business DNN information;

CC information of the business.

Among them, in actual application, one business corresponds to one application, so there will be a corresponding application identification (Application Identification, APP ID). FQDN can also be called a fully qualified domain name. The IP triplet may include: destination IP, destination port, and protocol type. CC can also be referred to as a connection type.

In actual application, according to the requirements of the test, the test result of the test index of the test process may be: a numerical value, or a data packet, and the like.

When the test results of the test indicators of the test process contain test values, the test indicators of each test process are correlated with each other.

Specifically, in an embodiment, the two test procedures include a first test procedure and a second test procedure; the first test procedure and the second test procedure satisfy one of the following:

The test index of the first test process includes throughput; the test index of the second test process includes delay;

The test index of the first test process includes downlink throughput; the test index of the second test process includes uplink throughput;

The test index of the first test process includes throughput; the test index of the second test process includes power consumption.

Wherein, in actual application, the throughput corresponding to the delay and power consumption may be uplink throughput, downlink throughput or uplink and downlink throughput.

It can be seen from the above description that the first test process and the second test process include one or a combination of the following test indicators:

Downlink throughput;

delay;

Uplink throughput;

power consumption.

In an embodiment, the at least two test procedures can be used to test the test indicators of the terminal under a network parameter configuration in the multi-network slice service concurrent scenario; the at least two test procedures can also be used to test Test indicators of the terminal under different network parameter configurations in a multi-network slicing business concurrent scenario.

In an embodiment, the at least two test procedures may be used to test the test indicators of the terminal under one network parameter configuration in a single network slice service scenario; the at least two test procedures may also be used to test the Test indicators of the terminal under different network parameter configurations in a single network slicing business scenario.

In actual application, the test environment may be virtual. Based on this, in an embodiment, a virtual network environment is constructed; the network slicing service performed on the terminal is a service of the virtual network environment.

Here, the service in the virtual network environment refers to a virtual service that does not exist in reality, such as a service simulated by an application program simulator in a test system.

In actual application, in step 102, at least one round of testing may be performed on the terminal during the execution of at least two test procedures on the terminal; in each round of testing, the terminal is configured with the network slicing service associated Test parameters.

Here, in each round of testing, at least two testing processes may be executed sequentially, or at least two testing processes may be executed in parallel; in actual application, which method to use may be determined according to needs.

Specifically, in one embodiment, the value of the test parameter is configured to the terminal once, that is, the test parameter is configured once; during the process of the terminal performing network slicing services, the at least two tests are sequentially performed on the terminal process;

Wherein, when the test result obtained by the first test process in the at least two test processes does not meet the test judgment condition, the test is ended; the first test process is the at least two test processes executed sequentially except the last test process other testing procedures.

In an embodiment, the value of the test parameter is configured once for the terminal; during the process of the terminal performing network slicing services, the at least two test procedures are executed in parallel for the terminal;

Based on the test results of the test indicators of each test process and the corresponding test judgment conditions, the test results for the terminal are generated.

In one embodiment, Q times of test parameters are configured to the terminal; Q is an integer greater than or equal to 2; each time a test parameter is configured, the terminal is sequentially executed during the process of performing network slicing services on the terminal. Describe at least two test procedures;

Based on the test results of the test indicators of the test process obtained each time and the corresponding test judgment conditions, the test results for the terminal are generated.

Wherein, in one embodiment, during each sequential execution of the at least two test procedures on the terminal, when the test value of the test index obtained by the first test procedure in the at least two test procedures does not meet the When the judgment condition is tested, the test ends; the first test process is a test process except the last test process among at least two test processes executed in sequence.

In one embodiment, Q times of test parameters are configured to the terminal; Q is an integer greater than or equal to 2; each time a test parameter is configured, during the process of performing network slicing services on the terminal, all tests are executed on the terminal in parallel. Describe at least two test procedures;

Here, in actual application, the test judgment condition is associated with the type of the test result of the test index of the test process; for example, when the test result of the test index of the test process is a test value, the test judgment condition can be is the test index threshold; when the test value of the test index of the test process does not meet the test index threshold, it is considered that the test of the test process fails, and when it meets the test index threshold, it is considered that the test of the test process is successful. That is to say, according to the test value of the test index of each round of testing and the corresponding test index threshold, it is determined whether the test process in the corresponding round passes. When the test result of the test indicator of the test flow is a data packet, the test judgment condition can be a set data packet; when the data packet of the test flow does not match the set data packet, it is considered that the test of the test flow fails. , when the test packet of the test flow matches the set data packet, it is considered that the test of the test flow is successful.

In each round of testing, the values of the testing parameters associated with the network slicing service configured to the terminal are different.

Here, in actual application, the current round (also referred to as the current round) can be set according to the test results of the previous P rounds of tests (the value of each round of test parameters and the corresponding test results of passing or failing). ) The value of the test parameter. Wherein, P is an integer greater than or equal to 1.

In each round of testing, the set test judgment conditions may be the same or different.

At the end of this round of testing, if all the testing processes pass the test, it is judged that this round of testing has passed;

At the end of the current round of testing, if there is a test process that fails the test, it is judged that the current round of testing has failed.

In the embodiment of the present disclosure, the test parameter configuration of the network slicing service is performed, therefore, the test result of the terminal may also be referred to as the test result of the network slicing service for the terminal.

In actual application, the specific content of the generated test result for the terminal can be determined according to needs; for example, it can include the test result of each test process and information about the success or failure of the corresponding test process in each round of testing; It may also contain only information about the success or failure of each round of testing; it may also include both the test result of each test process and the information about the success or failure of the corresponding test process, as well as the information about the success or failure of each round of testing.

In the test method provided by the embodiments of the present disclosure, the test parameters associated with the network slicing service are configured to the terminal; during the process of the terminal performing the network slicing service, at least two test procedures are executed on the terminal to obtain the test procedure of each test procedure The test result of the test index; the at least two test procedures are used to test the test index of the terminal in the multi-network slice business concurrent scenario, or to test the test index of the terminal in the single network slice business scenario; using The test results of the test indicators of each test process generate the test results for the terminal. In the solution of the embodiment of the present disclosure, the test is performed through at least two test processes for network slicing, and the test indicators of each test process are used. The test results are generated from the test results, thereby realizing multi-dimensional testing, which can meet the test requirements of performance indicators in different application scenarios, improve test efficiency, and improve the credibility of test results reflecting the real performance of the terminal.

The present disclosure will be further described in detail below in combination with application embodiments.

In the application embodiment, the terminal is in a New Radio (NR) cell. The test system is called an instrument, and it can also be called a test platform.

In order to test, you can configure the NR cell. When configuring, you can refer to the parameters of the live network, including:

(1) Default parameter configuration

Specific parameters can refer to Table 1.

Table 1

Wherein, in the description of Table 1, U represents an uplink time slot, D represents a downlink time slot, G represents a guard period (Guard Period, GP), and S represents a special time slot.

(2) Network slicing configuration, that is, service configuration

For specific parameters, please refer to Table 2, where TBD means to be determined.

Table 2

It is also necessary to configure the parameters of the Universal Subscriber Identity Module (USIM) (commonly referred to as the USIM card). For specific parameters, refer to Table 3.

table 3

During the test, the terminal needs to complete the registration process of the NR cell, and the process shown in Table 4 can be used specifically.

Table 4

Wherein, in Table 4, U represents a terminal, which may also be called user equipment (User Equipment, UE), and S represents a test system (ie, a test platform). <-- indicates that the test system sends a message to the terminal; --> indicates that the terminal sends a message to the test system, and RRC indicates Radio Resource Control (Radio Resource Control).

table 5

Table 6

信息元素information element	值value	说明illustrate
Extended protocol discriminatorExtended protocol discriminator	‘0111 1110’B'0111 1110'B	5GS mobility management消息5GS mobility management news
Security header typeSecurity header type	‘0000’B'0000'B	不设置完保Do not set full protection
Spare half octetSpare half octet	‘0000’B'0000'B	the
DL NAS TRANSPORT message identityDL NAS TRANSPORT message identity	‘0110 1000’B'0110 1000'B	the
Payload container typePayload container type	‘0101’B'0101'B	UE policy containerUE policy container
Spare half octetSpare half octet	'0000'B'0000'B	the
Payload containerPayload container	见表7See Table 7	the

Table 7

Table 8

Table 9

Table 10

Table 11

Table 12

Table 13

Table 14

指标index	预期值Expected value
业务A，下行TCP吞吐量Service A, downlink TCP throughput	TBD(表示待定)TBD (to be determined)
业务B，PING包时延Service B, PING packet delay	TBDTBD

Table 15

Application Example 1

In this application example:

(1) Test purpose: To verify whether the terminal service performance meets the requirements in the multi-slice concurrent scenario of Enhanced Mobile Broadband (eMBB) and Ultra-Reliable and Low Latency Communications (uRLLC).

(2) Scope of application: applicable to terminals with slicing capability.

(3) Test conditions:

[Test system configuration]

Cell A is an NR cell;

Cell ID (Cell Id) = 01 Tracking Area Code (Tracking Area Code, TAC) = 01;

Mobile Country Code (Mobile Country Code, MCC) = 460 Mobile Network Code (Mobile Network Code, MNC) = 00;

Test frequency band = n41;

Test frequency point = f1;

Uplink/Downlink Modulation and coding scheme (UL/DL MCS) dynamic configuration;

Maximum allowable transmit power (P-MAX) = 10dBm;

Ideal channel environment;

Slice 1 corresponds to 5G service quality indication (5G QoS Identifier, 5QI) 9;

Slice 2 corresponds to 5QI 80.

[terminal configuration]

The terminal is powered off, no USIM card is inserted in the terminal, and no slice identifier is pre-configured on the terminal.

[Business Configuration]

Service A: downlink transmission control protocol (Transmission Control Protocol, TCP) service transmission;

Service B: detection packet (PING packet), the size of which is 32 bytes.

The testing process includes the following steps:

Step 1: The NR cell remains closed;

Step 2: Insert the USIM card into the terminal and turn it on;

Step 3: activate NR cell A;

Step 4: The terminal initiates random access on cell A, and after the random access is completed, the terminal sends RRC Setup Complete (RRCSetupComplete) and a registration request (REGISTRATION REQUEST);

Step 5: Execute steps 5-12 in Table 4 to complete the authentication and security procedures;

Step 6: The instrument sends a registration acceptance (REGISTRATION ACCEPT) message, and configures different types of authorized network slice selection auxiliary information (Allowed S-NSSAI) and configured NSSAI (Configured NSSAI), see Table 5; among them, Table 5 shows The content of the REGISTRATION ACCEPT message is displayed;

Step 7: The terminal replies with a REGISTRATION COMPLETE message;

Step 8: The instrument sends a downlink non-access stratum transport (DL NAS TRANSPORT) message to configure routing policy (URSP) related parameters to the terminal, where the payload container type (Payload container type) is set to "terminal policy container (UE Policy container) container)" ('0101'B), carrying the MANAGE UE POLICY COMMAND message. The "terminal policy part type (UE policy part type)" in the MANAGE UE POLICY COMMAND message is set to "URSP" ('0001'B), see Table 6 and Table 7. The "UE policy part contents" message carries URSP configuration information, maps DNN_1 to slice 1, and maps DNN_2 to slice 2, see Table 8 to Table 10 for details; Table 6 shows DL The content of the NAS TRANSPORT message; Table 7 shows the content of the value MANAGE UE POLICY COMMAND message of the information element Payload container in Table 6; Table 8 shows the message content of the information element UE policy part contents in Table 7; Table 9 shows Table 8 shows the signaling content of an information element Route selection descriptor list; Table 10 shows the signaling content of another information element Route selection descriptor list in Table 8;

Step 9: The terminal replies with an uplink NAS TRANSPORT message, carrying a MANAGE UE POLICY COMPLETE message;

Step 10: The user initiates service A, and the terminal initiates a PDU Session connection establishment request; specifically, the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request (PDU Session Establishment Request), and the PDU Session Establishment Request carries DNN=DNN_1 and correct Single network slice selection assistance information (S-NSSAI) identifier, see Table 11 and Table 12; wherein, Table 11 shows the content of the UL NAS TRANSPORT message; Table 12 shows the value PDU of the information element Payload container in Table 11 The message content of SESSION ESTABLISHMENT REQUEST.

Step 11: After the instrument receives the request, configure test parameters such as DNN, S-NSSAI and QoS Class Identifier (QCI) to the terminal by replying PDU Session Establishment Accept, see Table 13; Wherein, Table 13 shows the content of the PDU Session Establishment Accept message;

Step 12: The user initiates service B, and the terminal initiates a PDU Session connection establishment request; specifically, the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request, and the Session Establishment Request carries DNN=DNN_2 and the correct S-NSSAI identifier, see Table 11 and Table 12;

Step 13: The instrument configures test parameters such as DNN, S-NSSAI and QCI to the terminal by replying PDU Session Establishment Accept, see Table 13;

Step 14: Keep the terminal executing service A and service B in parallel; the terminal executes the throughput test process of service A on the first PDU Session, and obtains the test value of the throughput performance index of service A executed by the terminal;

Step 15: Set the throughput performance index threshold according to Table 14, and judge whether the test process of Service A passes according to the throughput performance test value of service A obtained in step 14 and the throughput performance index threshold set in Table 14; if not test, then end the current round of testing, that is, end this test, and do not perform step 16; specifically, when the throughput performance test value is greater than or equal to the throughput performance index threshold, that is, meets the threshold, the test process is considered to pass; when the throughput performance If the throughput performance test value is less than the threshold of the throughput performance index, that is, if the threshold is not met, the test process is deemed to have failed;

Step 16: Keep the parallel service A and service B of the terminal, the terminal executes the delay test process of service B on the second PDU Session, and obtains the test value of the delay performance index of the terminal executing service B;

Step 17: Set the delay performance index threshold according to Table 14, and judge whether the test process of Service B is passed according to the delay performance test value of service B obtained in step 16 and the delay performance index threshold set in Table 14; specifically , when the delay performance test value is less than or equal to the delay performance index threshold, that is, the threshold is met, the test process is considered to pass; when the delay performance test value is greater than the delay performance index threshold, that is, the threshold is not met, the test process is considered to be failed;

Step 18: If both step 15 and step 17 pass the test, determine that the test is passed, end the test process of service A and service B, and generate the test result of the terminal; if there is a test process that fails the test in step 15 and step 17, then Judging that the test fails, end the test process of business A and business B, and generate the test result of the terminal; the test result of the terminal can include the test pass or fail result of the throughput test process of business A, and the delay test of business B Pass or fail results of the tests for the process;

Step 19: release the RRC link, and shut down the terminal;

Step 20: Deactivate NR cell A.

Wherein, in actual application, the delay performance index threshold can be set according to Table 14 first, and then the set delay performance index threshold can be directly used in steps 15 and 17.

In the above process, the throughput test process of service A and the delay test process of service B are executed in sequence. The throughput test process of service A and the delay test process of service B can also be executed in parallel, that is to say, steps 14 and 16 can also be executed at the same time, that is, the terminal executes the throughput test process of service A on the first PDU Session , execute the delay test process of service B on the second PDU Session in parallel.

It can be seen from the above description that Step 1 and Step 2 are the leading steps; Step 3 to Step 18 are the main steps; Step 19 and Step 20 are the end steps.

Application Example 2

In this application example:

(1) Test purpose: To test the business performance under different network parameter configurations in a multi-slice concurrency scenario.

(2) Scope of application: applicable to terminals with slicing capability.

(3) Test conditions:

[Test system configuration]

Cell A is an NR cell;

CellId＝01 TAC＝01;

MCC=460 MNC=00;

Test frequency band = n41;

Test frequency point = f1;

UL/DL MCS dynamic configuration

P-MAX=10dBm;

Ideal channel environment.

[terminal configuration]

[Business Configuration]

Service A: downlink TCP service transmission;

Business B: PING packet, the packet size is 32 bytes.

The testing process includes the following steps:

Step 1: The NR cell remains closed;

Step 2: Insert the USIM card into the terminal and turn it on;

Step 3: activate NR cell A;

Step 4: The terminal initiates random access in cell A, and after the random access is completed, the terminal sends RRCSetupComplete and REGISTRATION REQUEST;

Step 6: The instrument sends a REGISTRATION ACCEPT message, and configures different types of Allowed S-NSSAI and Configured NSSAI, see Table 5; where, Table 5 shows the content of the REGISTRATION ACCEPT message;

Step 7: The terminal replies with a REGISTRATION COMPLETE message;

Step 8: The instrument sends a downlink non-access stratum transmission (DL NAS TRANSPORT) message to configure URSP-related parameters to the terminal, where the Payload container type is set to "UE Policy container" ('0101'B), carrying MANAGE UE POLICY COMMAND information. The "UE policy part type" in the MANAGE UE POLICY COMMAND message is set to "URSP" ('0001'B), see Table 6 and Table 7. The "UE policy part contents" message carries URSP configuration information, maps DNN_1 to slice 1, and maps DNN_2 to slice 2, see Table 8 to Table 10 for details; among them, Table 8 shows the information element UE policy in Table 7 The message content of part contents; Table 9 shows the signaling content of an information element Route selection descriptor list in Table 8; Table 10 shows the signaling content of another information element Route selection descriptor list in Table 8;

Step 9: The terminal replies with the UL NAS TRANSPORT message, carrying the MANAGE UE POLICY COMPLETE message;

Step 10: The user initiates service A, and the terminal initiates a PDU Session connection establishment request; specifically, the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request, and carries DNN=DNN_1 and the correct S-NSSAI identifier in the DU Session Establishment Request, See Table 11 and Table 12; wherein, Table 11 shows the content of the UL NAS TRANSPORT message; Table 12 shows the message content of the value PDU SESSION ESTABLISHMENT REQUEST of the information element Payload container in Table 11.

Step 11: After the instrument receives the request, configure the test parameters such as DNN, S-NSSAI and QCI to the terminal by replying PDU Session Establishment Accept, see Table 13; wherein, Table 13 shows the content of the PDU Session Establishment Accept message;

Step 14: Ensure that business A and business B are executed in parallel;

Step 15: The terminal executes the throughput test process of service A on the first PDU Session, and obtains the test value of the throughput performance index of service A;

Step 16: Set the throughput performance index threshold according to Table 14, and judge whether the current test process passes according to the service A throughput performance test value obtained in Step 15 and the throughput performance index threshold set in Table 14. If it passes, go to step 17; if it doesn’t pass, it is judged that the current round of testing has not passed, and the current round of testing is ended, and then step 19 is executed; specifically, when the throughput performance test value is greater than or equal to the throughput performance index threshold, it is considered The test process is passed; when the throughput performance test value is less than the throughput performance index threshold, that is, the threshold is not met, the test process is considered to have failed;

Step 17: When the throughput performance index of service A executed by the terminal meets the threshold, and under the condition that service A and service B are executed in parallel, the terminal executes the delay test process of service B on the second PDU Session, and obtains the time delay of service B. The test value of the delay performance index, then perform step 18;

Step 18: Set the delay performance index threshold according to Table 14, and judge whether the current test process passes according to the PING packet delay performance index test value of service B obtained in Step 17 and the delay performance index threshold set in Table 14. If it passes, it is judged that the current round of testing is passed, and the current round of testing is ended, and step 19 is performed; if it is not passed, it is judged that the current round of testing has not passed, and the current round of testing is ended, and step 19 is performed;

Step 19: The instrument sends a PDU session modification command (PDU SESSION MODIFICATION COMMAND) message to configure the QoS parameters of service A to the terminal, see Table 15;

Step 20: The terminal replies that the PDU session modification is complete (PDU SESSION MODIFICATION COMPLETE) to confirm the parameter modification, and then execute step 21;

Step 21: Under the condition that business A and business B are executed in parallel, the terminal executes the throughput test process of business A on the first PDU Session, and obtains the test value of the throughput performance index of business A;

Step 22: Set the throughput performance index threshold according to Table 14, and judge whether the current test process passes according to the throughput performance test value of service A obtained in Step 21 and the throughput performance index threshold set in Table 14. If passed, perform the steps 23; If it fails, it is judged that the current round of tests has failed, and then execute step 25;

Step 23: The terminal executes the throughput performance index of service A to meet the threshold value. Under the condition that the parallel execution of service A and service B is guaranteed, the terminal executes the delay test process of service B in parallel on the second PDU Session, and obtains the delay test process of service B. The test value of the delay performance index;

Step 24: Set the delay performance index threshold according to Table 14, and judge whether the current test process passes according to the service B PING packet delay performance index test value obtained in step 23 and the delay performance index threshold set in Table 14. If it is passed, it is judged that the current round of testing is passed, and the current round of testing is ended, and step 25 is performed;

Step 25: The instrument sends a PDU SESSION MODIFICATION COMMAND message to modify the QoS configuration parameters of service B, see Table 15;

Step 26: The terminal replies with PDU SESSION MODIFICATION COMPLETE to confirm the parameter modification, and then execute step 27;

Step 27: Under the condition that business A and business B are executed in parallel, the terminal executes the throughput test process of business A on the first PDU Session, and obtains the test value of the throughput performance index of business A

Step 28: Set the throughput performance index threshold according to Table 14, and judge whether the current test process passes according to the service A throughput performance test value obtained in Step 27 and the throughput performance index threshold set in Table 14. If it passes, go to step 29; if it doesn’t pass, judge that the current round of testing has failed, and end the test;

Step 29: When the throughput performance index of service A executed by the terminal meets the threshold, and in the case of ensuring parallel execution of service A and service B, the terminal executes the delay test process of service B in parallel on the second PDU Session to obtain service B The test value of the delay performance index;

Step 30: set the delay performance index threshold according to Table 14, and judge whether the current test process passes through according to the test value of the service B PING packet delay performance index obtained in step 29 and the delay performance index threshold set in Table 14. If it passes, it is judged that the current round of testing is passed, and the test is ended; if it is not passed, it is judged that the current round of testing has not passed, and the test is ended;

Step 31: end the test process of service A and service B, and generate the test result of the terminal; the test result includes the QoS parameter (ie 5QI) of each round of test and the result of passing or failing the test of each test process;

Step 32: release the RRC link, and shut down the terminal;

Step 33: Deactivate NR cell A.

It can be seen from the above description that in this application embodiment, it is tested whether the service performance under different network parameter configurations (that is, different 5QI configurations) can meet the requirements, and the tests in step 18, step 24 and step 30 all pass the test.

In the above process, the throughput test process of service A and the delay test process of service B are executed in sequence. The throughput test process of service A and the delay test process of service B can also be executed in parallel, that is, steps 15 and 17 are executed at the same time, that is, the terminal executes the throughput test process of service A on the first PDU Session, parallel Execute the delay test process of service B in parallel on the second PDU Session; similarly, steps 21 and 23 are executed at the same time, and steps 27 and 29 are executed at the same time.

Wherein, in actual application, the delay performance index threshold can be set according to Table 14 first, and then the set delay performance index threshold can be directly used in steps 16, 18, 22, 24, 28 and 30.

Step 1 and Step 2 are leading steps; Step 3 to Step 31 are main steps; Step 32 and Step 33 are ending steps.

Application Example Three

In this application example:

(1) Test purpose: To verify whether the terminal service performance meets the requirements in the eMBB single network slice scenario.

(2) Scope of application: applicable to terminals with slicing capability.

(3) Test conditions:

[Test system configuration]

Cell A is an NR cell;

CellId＝01 TAC＝01;

MCC=460 MNC=00;

Test frequency band = n41;

Test frequency point = f1;

UL/DL MCS dynamic configuration;

P-MAX=10dBm;

Ideal channel environment;

Slice 1 corresponds to 5QI 9.

[terminal configuration]

The terminal is powered off, no USIM card is inserted into the terminal, and no slice identifier is pre-configured on the terminal.

[Business Configuration]

Service A: downlink TCP service transmission.

Table 16

Table 17

Table 18

Table 19

Table 20

Table 21

指标index	预期值Expected value
业务A，下行TCP吞吐量Service A, downlink TCP throughput	TBDTBD
业务A，PING包时延Service A, PING packet delay	TBDTBD

The testing process includes the following steps:

Step 1: The NR cell remains closed;

Step 2: Insert the USIM card into the terminal and turn it on;

Step 3: activate NR cell A;

Step 5: Execute steps 5-12 in Table 4 to complete the authentication and security process;

Step 6: The instrument sends a REGISTRATION ACCEPT message, and configures different types of Allowed NSSAI and Configured NSSAI, see Table 16; where, Table 16 shows the contents of the REGISTRATION ACCEPT message;

Step 7: The terminal replies with a REGISTRATION COMPLETE message;

Step 8: The instrument sends a DL NAS TRANSPORT message to configure URSP-related parameters to the terminal, where the Payload container type is set to "UE Policy container" ('0101'B), and carries the MANAGE UE POLICY COMMAND message. The "UE policy part type" in the MANAGE UE POLICY COMMAND message is set to "URSP" ('0001'B), see Table 6 and Table 7. Wherein, "UE policy part contents" carries URSP configuration information, maps DNN_1 to slice 1, see Table 17; wherein, Table 17 shows the message content of the information element UE policy part contents in Table 7;

Step 9: Verify that the terminal replies to UL NAS TRANSPORT with MANAGE UE POLICY COMPLETE message;

Step 10: The user initiates service A, and the terminal initiates a PDU Session connection establishment request; specifically, the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request, and carries DNN=DNN_1 and the correct S-NSSAI identifier in the PDU Session Establishment Request, See Table 18 and Table 19; wherein, Table 18 shows the content of the UL NAS TRANSPORT message; Table 19 shows the message content of the value PDU SESSION ESTABLISHMENT REQUEST of the information element Payload container in Table 18;

Step 11: After receiving the request, the instrument configures test parameters such as DNN, S-NSSAI and QCI to the terminal by replying PDU Session Establishment Accept, see Table 20, to ensure that business A is carried out normally; among them, Table 20 shows the PDU Session The content of the Establishment Accept message;

Step 12: Execute the throughput test process of service A, and obtain the test value of the throughput performance index of service A executed by the terminal;

Step 13: Set the throughput performance index threshold according to Table 21, and judge whether the test process of Service A passes according to the throughput performance test value of service A obtained in step 12 and the throughput performance index threshold set in Table 21; if not test, then end the current round of testing, that is, end this test, and do not perform step 14;

Step 14: Execute the delay test process of service A, and obtain the test value of the delay performance index of the terminal executing service A;

Step 15: Set the delay performance index threshold according to Table 21, and judge whether the delay test process of Service A is passed according to the service A delay performance index test value obtained in step 14 and the delay performance index threshold set in Table 21;

Step 16: If the throughput test process in step 13 and the delay test process in step 15 all pass the test, then determine that this round of testing is passed, end the test process of service A, and generate the test result of the terminal; if in step 13 If there is a test process that fails the test in the throughput test process and the delay test process in step 15, then it is judged that this round of tests has not passed, and the test result of the terminal is generated;

Step 17: release the RRC link, and shut down the terminal;

Step 18: Deactivate NR cell A.

Wherein, in actual application, the delay performance index threshold can be set according to Table 21 first, and then the set delay performance index threshold can be directly used in steps 13 and 15.

In the above process, the throughput test process and delay test process of service A are executed in sequence. The throughput test process and delay test process of service A can also be executed in parallel, that is to say, steps 12 and 14 can also be performed simultaneously, that is, the throughput test process of service A is executed, and the delay test process of service A is executed in parallel.

It can be seen from the above description that Step 1 and Step 2 are the leading steps; Step 3 to Step 16 are the main steps; Step 17 and Step 18 are the end steps.

Application Example 4

In this example:

(1) Test purpose: To verify whether the throughput performance of the terminal meets the requirements when the terminal performs bidirectional data transmission in the eMBB single network slicing scenario.

(2) Scope of application: applicable to terminals with slicing capability.

(3) Test conditions:

[Test system configuration]

Cell A is an NR cell;

CellId＝01 TAC＝01;

MCC=460 MNC=00;

Test frequency band = n41;

Test frequency point = f1;

UL/DL MCS dynamic configuration

P-MAX=10dBm;

Ideal channel environment;

Slice 1 corresponds to 5QI 9.

[terminal configuration]

[Business Configuration]

Service A: bidirectional TCP service transmission.

Table 22

指标index	预期值Expected value
业务A，下行TCP吞吐量Service A, downlink TCP throughput	TBDTBD
业务A，上行TCP吞吐量Service A, uplink TCP throughput	TBDTBD

The testing process includes the following steps:

Step 1: The NR cell remains closed;

Step 2: Insert the USIM card into the terminal and turn it on;

Step 3: activate NR cell A;

Step 6: The instrument sends a REGISTRATION ACCEPT message, and configures different types of Allowed NSSAI and Configured NSSAI, see Table 16; where, Table 16 shows the content of the REGISTRATION ACCEPT message;

Step 7: The terminal replies with a REGISTRATION COMPLETE message;

Step 10: The instrument and the user initiate service A two-way TCP service transmission, and the terminal initiates a PDU Session connection establishment request; specifically, the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request, and carries DNN=DNN_1 and For the correct S-NSSAI identification, see Table 18 and Table 19; among them, Table 18 shows the content of the UL NAS TRANSPORT message; Table 19 shows the message content of the value PDU SESSION ESTABLISHMENT REQUEST of the information element Payload container in Table 18;

Step 11: After receiving the request, the instrument configures the test parameters such as DNN, S-NSSAI and QCI to the terminal by replying PDU Session Establishment Accept to ensure the normal operation of service A, see Table 20; among them, Table 20 shows the PDU Session The content of the Establishment Accept message;

Step 12: Execute the downlink throughput test process of service A, and obtain the test value of the downlink throughput performance index of service A executed by the terminal;

Step 13: Set the downlink throughput performance index threshold according to Table 22, and determine the downlink throughput test process of Service A based on the downlink throughput performance test value of service A obtained in step 12 and the downlink throughput performance index threshold set in Table 22 Whether it is passed; if the test is not passed, then end the current round of testing, that is, end this test, and do not perform step 14;

Step 14: Continue to perform the downlink throughput test of service A, and at the same time perform the uplink throughput test of service A, and obtain the uplink throughput test value of service A performed by the terminal;

Step 15: Set the uplink throughput performance index threshold according to Table 22, and judge whether the uplink throughput test process of Service A passes according to the uplink throughput test value of service A obtained in step 14 and the uplink throughput index threshold set in Table 22 ;

Step 16: If both the downlink throughput test process in step 13 and the uplink throughput test process in step 15 pass the test, then it is judged that the test is passed, the test process of service A is ended, and the test result of the terminal is generated; if in step 13 If there is a test process that fails the test in the downlink throughput test process and the uplink throughput test process in step 15, then it is judged that the test has not passed, and the test result of the terminal is generated;

Step 17: release the RRC link, and shut down the terminal;

Step 18: Deactivate NR cell A.

Wherein, in actual application, the delay performance index threshold can be set according to Table 22 first, and then the set delay performance index threshold can be directly used in steps 15 and 17.

In the above process, the uplink throughput test process of service A and the downlink throughput test process of service A are executed in sequence. The throughput test process of service A and the downlink throughput test process of service A can also be executed in parallel, that is, steps 12 and 14 are executed at the same time, that is, the terminal executes the downlink throughput test process of service A, and executes the uplink throughput of service A in parallel. Throughput testing process.

Application Embodiment Five

In this application example:

(1) Test purpose: To verify whether the terminal service performance under different network parameter configurations meets the requirements in the eMBB single network slice scenario.

(2) Scope of application: applicable to terminals with slicing capability.

(3) Test conditions:

[Test system configuration]

Cell A is an NR cell;

CellId＝01 TAC＝01;

MCC=460 MNC=00;

Test frequency band = n41;

Test frequency point = f1;

UL/DL MCS dynamic configuration

P-MAX=10dBm;

Ideal channel environment;

Slice 1 corresponds to 5QI 9.

[terminal configuration]

The terminal is powered off, no USIM card is inserted in the terminal, and no slice identifier is pre-configured on the terminal. [Business Configuration]

Service A: downlink TCP service transmission.

Table 23

The testing process includes the following steps:

Step 1: The NR cell remains closed;

Step 2: Insert the USIM card into the terminal and turn it on;

Step 3: activate NR cell A;

Step 7: The terminal replies with a REGISTRATION COMPLETE message;

Step 8: The instrument sends a DL NAS TRANSPORT message to configure URSP-related parameters to the terminal, where the Payload container type is set to "UE Policy container" ('0101'B), and carries the MANAGE UE POLICY COMMAND message. The "UE policy part type" in the MANAGE UE POLICY COMMAND message is set to "URSP" ('0001'B), see Table 6 and Table 7. Among them, "UE policy part contents" carries URSP configuration information, and DNN_1 is mapped to slice 1, see Table 17; wherein, Table 17 shows the content of the information element UE policy part contents message in Table 7;

Step 12: Execute the throughput test process of service A, and obtain the test value of the throughput performance index of service A;

Step 13: Set the throughput performance index threshold according to Table 21, and judge whether the current test process passes according to the service A throughput performance test value obtained in Step 12 and the throughput performance index threshold set in Table 21. If it passes, go to step 14; if it doesn’t pass, then judge that the current round of testing has failed, end the current round of testing, and go to step 16;

Step 14: Execute the delay test process of service A, and obtain the test value of the delay performance index of service A

Step 15: Set the delay performance index threshold according to Table 21, and judge whether the current test process passes according to the service A delay performance index test value obtained in Step 14 and the delay performance index threshold set in Table 21. If it passes, it is judged that the current round of testing is passed, and the current round of testing is ended, and step 16 is performed; if it is not passed, it is judged that the current round of testing has not passed, and the current round of testing is ended, and step 16 is performed;

Step 16: The instrument sends a PDU SESSION MODIFICATION COMMAND message to configure the QoS parameters of service A to the terminal, see Table 23;

Step 17: The terminal replies with PDU SESSION MODIFICATION COMPLETE to confirm the parameter modification;

Step 18: Execute the throughput test process of service A, and obtain the test value of the throughput performance index of service A;

Step 19: Set the throughput performance index threshold according to Table 21, and judge whether the current test process passes according to the service A throughput performance test value obtained in Step 18 and the throughput performance index threshold set in Table 21. If it passes, go to step 20; if it doesn’t pass, then it is judged that the current round of testing has not passed, and go to step 22;

Step 20: Execute the delay test process of service A, and obtain the test value of the delay performance index of service A;

Step 21: set the delay performance index threshold according to Table 21, and judge whether the current test process passes according to the service B PING packet delay performance index test value obtained in step 20 and the delay performance index threshold set in Table 21. If it is passed, it is judged that the current round of testing is passed, and the current round of testing is ended, and step 22 is performed;

Step 22: The instrument sends a PDU SESSION MODIFICATION COMMAND message to modify the QoS configuration parameters of service A, see Table 23;

Step 23: The terminal replies with PDU SESSION MODIFICATION COMPLETE to confirm the parameter modification;

Step 24: Execute the throughput test process of service A, and obtain the test value of the throughput performance index of service A;

Step 25: Set the throughput performance index threshold according to Table 21, and judge whether the current test process passes according to the service A throughput performance test value obtained in Step 24 and the throughput performance index threshold set in Table 21. If it passes, go to step 26; if it doesn’t pass, it is judged that the current round of testing has not passed, and the test ends;

Step 26: Execute the delay test process of service A, and obtain the test value of the delay performance index of service A;

Step 27: Set the delay performance index threshold according to Table 21, and judge whether the current test process passes according to the service A delay performance index test value obtained in Step 26 and the delay performance index threshold set in Table 21. If it passes, it is judged that the current round of testing is passed, and the test is ended; if it is not passed, it is judged that the current round of testing has not passed, and the test is ended;

Step 28: End the test process of service A, and generate the test result of the terminal;

Step 29: release the RRC link, and shut down the terminal;

Step 30: Deactivate NR cell A.

It can be seen from the above description that in this application embodiment, it is tested whether the service performance under different network parameter configurations (that is, different 5QI configurations) can meet the requirements, and the tests in step 15, step 21 and step 27 all pass the test.

Wherein, in actual application, the delay performance index threshold can be set according to Table 21 first, and then the set delay performance index threshold can be directly used in steps 13, 15, 19, 21, 25 and 27.

Step 1 and Step 2 are leading steps; Step 3 to Step 28 are main steps; Step 29 and Step 30 are ending steps.

In the above process, the throughput test process and delay test process of service A are executed in sequence. The throughput test process of service A and the delay test process of service A can also be executed in parallel, that is, steps 12 and 14 are executed at the same time, that is, the throughput test process of service A is executed, and the delay test process of service A is executed in parallel ; Similarly, steps 18 and 20 are executed simultaneously, and steps 24 and 26 are executed simultaneously.

Application Embodiment Six

In this application example:

(1) Test purpose: To verify whether the throughput performance of the terminal bidirectional data transmission under different network parameter configurations meets the requirements in the eMBB single network slicing scenario.

(2) Scope of application: applicable to terminals with slicing capability.

(3) Test conditions:

[test system configuration];

Cell A is an NR cell;

CellId＝01 TAC＝01;

MCC=460 MNC=00;

Test frequency band = n41;

Test frequency point = f1;

UL/DL MCS dynamic configuration;

P-MAX=10dBm;

Ideal channel environment;

Slice 1 corresponds to 5QI 9.

[terminal configuration]

[Business Configuration]

Service A: bidirectional TCP service transmission.

Table 24

The testing process includes the following steps:

Step 1: The NR cell remains closed;

Step 2: Insert the USIM card into the terminal and turn it on;

Step 3: activate NR cell A;

Step 7: The terminal replies with a REGISTRATION COMPLETE message;

Step 12: Execute the downlink throughput test process of service A, and obtain the test value of the downlink throughput performance index of service A;

Step 13: Set the downlink throughput performance index threshold according to Table 22, and judge whether the current test process passes according to the service A downlink throughput performance test value obtained in Step 12 and the downlink throughput performance index threshold set in Table 22, if passed , execute step 14; if not pass, then judge that the current round of testing has not passed, end the current round of testing, and execute step 16;

Step 14: Continue to perform the downlink throughput test of service A, and perform the uplink throughput test of service A at the same time, and obtain the test value of the uplink throughput performance index of service A;

Step 15: Set the uplink throughput performance threshold according to Table 22, and judge whether the current test process passes according to the uplink throughput performance test value of Service A obtained in Step 14 and the delay performance index threshold set in Table 22. If it passes, it is judged that the current round of testing is passed, and the current round of testing is ended, and step 16 is performed;

Step 16: The instrument sends a PDU SESSION MODIFICATION COMMAND message to configure the QoS parameters of service A to the terminal, see Table 24;

Step 18: Execute the downlink throughput test process of service A, and obtain the test value of the downlink throughput performance index of service A;

Step 19: Set the downlink throughput performance index threshold according to Table 22, and judge whether the current test process passes according to the service A downlink throughput performance test value obtained in Step 18 and the downlink throughput performance index threshold set in Table 22, if passed , go to step 20; if not pass, it is judged that the current round of test has not passed, go to step 22;

Step 20: Continue to perform the downlink throughput test of service A, and perform the uplink throughput test of service A at the same time, and obtain the uplink throughput performance test value of service A;

Step 21: Set the uplink throughput performance index threshold according to Table 22, set the uplink throughput performance index threshold according to the service A uplink throughput performance test value obtained in step 20 and Table 22, and judge whether the current test process passes. If it is passed, it is judged that the current round of testing is passed, and the current round of testing is ended, and step 22 is performed;

Step 22: The instrument sends a PDU SESSION MODIFICATION COMMAND message to modify the QoS configuration parameters of service A, see Table 24;

Step 23: The terminal replies with PDU SESSION MODIFICATION COMPLETE to confirm the parameter modification

Step 24: Execute the downlink throughput test process of service A, and obtain the test value of the downlink throughput performance index of service A;

Step 25: Set the downlink throughput performance index threshold according to Table 22, and judge whether the current test process passes according to the downlink throughput performance test value of service A obtained in step 24 and the downlink throughput performance index threshold set in Table 22. If it passes, go to step 26; if it doesn’t pass, it is judged that the current round of testing has not passed, and the test ends;

Step 26: Continue to perform the downlink throughput test of service A, and perform the uplink throughput test of service A at the same time, and obtain the test value of the uplink throughput performance of service A;

Step 27: Set the uplink throughput performance index threshold according to Table 22, and judge whether the current test process passes according to the uplink throughput performance test value of service A obtained in step 26 and the uplink throughput performance index threshold set in Table 22, if passed , it is judged that the current round of testing is passed, and the test is ended; if it is not passed, it is judged that the current round of testing has not passed, and the test is ended;

Step 29: release the RRC link, and shut down the terminal;

Step 30: Deactivate NR cell A.

Wherein, in actual application, the delay performance index threshold can be set according to Table 22 first, and then the set delay performance index threshold can be directly used in steps 13, 15, 19, 21, 25 and 27.

In the above process, the uplink throughput test process of service A and the downlink throughput test process of service A are executed in sequence. The throughput test process of service A and the downlink throughput test process of service A can also be executed in parallel, that is, steps 12 and 14 are executed at the same time, that is, the downlink throughput test process of service A is executed, and the uplink throughput of service A is executed in parallel. Quantitative testing; similarly, steps 18 and 20 are executed simultaneously; steps 24 and 26 are executed simultaneously.

It can be seen from the above description that in this application embodiment, the test of whether the single network slice service performance under different network parameter configurations (that is, different 5QI configurations) can meet the requirements is passed in steps 15, 21 and 27. Step 1 and Step 2 are leading steps; Step 3 to Step 28 are main steps; Step 29 and Step 30 are ending steps.

Application Example Seven

In this application example:

(1) Purpose of the test: To verify whether the terminal supports associating services and slices through DNN, and whether the services can be carried out normally after associating slices.

(2) Scope of application: applicable to terminals with slicing capability.

(3) Test conditions:

[Test system configuration]

Cell A is an NR cell;

CellId＝01 TAC＝01;

MCC=460 MNC=00;

Test frequency band = n41;

Test frequency point = f1;

UL/DL MCS dynamic configuration;

P-MAX=10dBm;

Ideal channel environment.

Service A: Based on the data transmission service generated by the application simulator, a data packet with a size of 32 bytes is generated and filled with a random number sequence; the corresponding DNN is DNN_1;

Service B: Based on the data transmission service generated by the application simulator, a data packet with a size of 200 bytes is generated and filled with a random number sequence; the corresponding DNN is DNN_2;

[terminal configuration]

Table 25

Table 26

Table 27

Table 28

The testing process includes the following steps:

Step 1: The NR cell remains closed;

Step 2: Insert the USIM card into the terminal and turn it on;

Step 3: activate NR cell A;

Step 4: The terminal initiates random access in cell A. After the random access is completed, the terminal sends RRCSetupComplete and REGISTRATION REQUEST messages; wherein, the REGISTRATION REQUEST message sent by the terminal does not carry "Requested NSSAI";

Step 6: The instrument sends a REGISTRATION ACCEPT message, and configures different types of Allowed NSSAI and Configured NSSAI, see Table 25; where, Table 25 shows the content of the REGISTRATION ACCEPT message;

Step 7: The terminal replies with a REGISTRATION COMPLETE message. At this time, the terminal completes the registration and stores the Allowed NSSAI and Configured NSSAI of the current PLMN;

Step 8: The instrument sends DL NAS TRANSPORT, where the Payload container type is set to "UE Policy container" ('0101'B), carrying the MANAGE UE POLICY COMMAND message. In the MANAGE UE POLICY COMMAND message, "UE policy part type" is set to "URSP" ('0001'B), and "UE policy part contents" carries URSP configuration information, see Table 6 to Table 10 for details; among them, Table 6 shows Table 7 shows the content of the DL NAS TRANSPORT message; Table 7 shows the content of the MANAGE UE POLICY COMMAND message of the value of the information element Payload container in Table 6; Table 8 shows the message content of the information element UE policy part contents in Table 7; Table 9 Shows the signaling content of an information element Route selection descriptor list in Table 8; Table 10 shows the signaling content of another information element Route selection descriptor list in Table 8;

Step 9: The terminal replies to UL NAS TRANSPORT with MANAGE UE POLICY COMPLETE message;

Step 10: The user initiates service A, and the terminal initiates a PDU Session connection establishment request; specifically, the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request, and carries DNN=DNN_1 and the correct S-NSSAI identifier in the PDU Session Establishment Request, See Table 26 and Table 27; wherein, Table 26 shows the content of the UL NAS TRANSPORT message; Table 27 shows the message content of the value PDU SESSION ESTABLISHMENT REQUEST of the information element Payload container in Table 26;

Step 11: After receiving the request, the instrument configures DNN, S-NSSAI and QCI to the terminal by replying PDU Session Establishment Accept, see Table 28 for details; where, Table 28 shows the content of the PDU Session Establishment Accept message;

Step 12: After completing the establishment of the PDU Session, the terminal performs service A through the corresponding PDU Session;

Step 13: Keep service A running normally, the user initiates service B, and the terminal initiates a PDU Session connection establishment request; specifically, the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request, and carries DNN=DNN_2 and correct in the PDU Session Establishment Request S-NSSAI logo, see 26 and Table 27;

Step 14: After receiving the request, the instrument configures DNN, S-NSSAI and QCI to the terminal by replying PDU Session Establishment Accept, see Table 28 for details;

Step 15: After completing the establishment of the PDU Session, the terminal performs service B through the corresponding PDU Session;

Step 16: Keep business A and business B running at the same time, execute the test process to verify whether business A is normally carried out on the corresponding PDU Session; specifically, execute the test process so that the terminal transmits the data packet of service A to the service platform through the PDU Session Simulator; at the same time, the terminal directly sends the original simulated data packet of service A generated by the application simulator to the service platform simulator; compare the service A data packet received through the PDU Session with the service A data packet directly transmitted by the terminal , compare the number of bytes in the data packet and compare the random number sequence bit by bit. If the two are consistent, it proves that business A is mapped to the correct slice, and proceed to the following steps; otherwise, the verification of the mapping relationship between business A and the slice fails, and the test is judged to have failed, and the test is stopped, that is, step 17 is not performed;

Step 17: Keep business A and business B running at the same time, execute the test process to verify whether business B is normally carried out on the corresponding PDU Session; specifically, execute the test process so that the terminal transmits the data packet of business B to the The service platform simulator; at the same time, the terminal directly sends the original simulated data packet of service B generated by the application simulator to the service platform simulator; the service platform simulator compares the service B data packet received through the PDU Session, and the terminal directly For the transmitted service B data packet, compare the number of bytes in the data packet and compare the random number sequence bit by bit. If the two are consistent, it proves that business B is mapped to the correct slice, and the test is determined to pass; otherwise, the verification of the mapping relationship between service B and slice fails, and the test is determined to fail;

Step 18: End the test process of business A and business B, and generate the test result of the terminal; the test result includes the test pass or fail result of each test process;

Step 19: End business A and business B;

Step 20: The instrument sends an RRCRelease message to release the NR link, that is, release the RRC link;

Step 21: Deactivate NR cell A.

Among them, in step 16 and step 17, it can also be executed in parallel in the following manner:

After the establishment of the PDU Session is completed, compare the data packet generated by terminal service A (the original simulated data packet sent directly to the service platform simulator) and the data packet received by the service platform simulator through the corresponding PDU Session to verify whether service A can The corresponding PDU Session (the first PDU Session) is normally carried out; at the same time, compare the data packet generated by the terminal business B with the data packet received by the business platform simulator through the corresponding PDU Session, and verify whether the business B can Session (Second PDU Session) works normally.

It can be seen from the above description that in this application embodiment, it is tested whether the terminal can associate the correct slice through the DNN information issued by the service and initiate a PDU connection establishment request, and the service can proceed normally after associating the slice. In addition, Step 1 and Step 2 are leading steps; Step 3 to Step 18 are main steps; Step 19, Step 20 and Step 21 are ending steps.

Application Embodiment Eight

In this application example:

(1) Purpose of the test: To verify whether the terminal supports associating services and slices through the APP ID, and whether the business can proceed normally after associating slices.

(2) Scope of application: applicable to terminals with slicing capability.

(3) Test conditions:

[Test system configuration]

Cell A is an NR cell;

CellId＝01 TAC＝01;

MCC=460 MNC=00;

Test frequency band = n41;

Test frequency point = f1;

UL/DL MCS dynamic configuration;

P-MAX=10dBm;

Ideal channel environment.

[terminal configuration]

Service A: Based on the data transmission service generated by the application simulator, a data packet with a size of 32 bytes is generated and filled with a sequence of random numbers;

Service B: Based on the data transmission service generated by the application simulator, a data packet with a size of 200 bytes is generated and filled with a sequence of random numbers.

Table 29

Table 30

Table 31

The testing process includes the following steps:

Step 1: The NR cell remains closed;

Step 2: Insert the USIM card into the terminal and turn it on;

Step 3: activate NR cell A;

Step 8: The instrument sends DL NAS TRANSPORT, where the Payload container type is set to "UE Policy container" ('0101'B), carrying the MANAGE UE POLICY COMMAND message. In the MANAGE UE POLICY COMMAND message, "UE policy part type" is set to "URSP" ('0001'B), and "UE policy part contents" carries URSP configuration information. See Table 6, Table 7, Table 29, Table 9, and Table 10 for details; wherein, Table 29 shows the message content of the information element UE policy part contents in Table 7;

Step 10: The user initiates service A, and the terminal initiates a PDU Session connection establishment request; specifically, verify that the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request, and carries the correct S-NSSAI identifier in the PDU Session Establishment Request, see Table 30 and Table 31; wherein, Table 30 shows the content of the UL NAS TRANSPORT message; Table 31 shows the message content of the value PDU SESSION ESTABLISHMENT REQUEST of the information element Payload container in Table 30;

Step 11: The instrument replies PDU Session Establishment Accept, configures DNN, S-NSSAI and QCI, etc., see Table 28 for details;

Step 13: Keep service A running normally, the user initiates service B, and the terminal initiates a PDU Session connection establishment request; specifically, the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request, and carries the correct S-NSSAI in the PDU Session Establishment Request Identification, see Table 30 and Table 31; wherein, Table 30 shows the content of the UL NAS TRANSPORT message; Table 31 shows the message content of the value PDU SESSION ESTABLISHMENT REQUEST of the information element Payload container in Table 30;

Step 14: The instrument replies PDU Session Establishment Accept, configures DNN, S-NSSAI and QCI, etc., see Table 28 for details;

Step 19: End business A and business B;

Step 21: Deactivate NR cell A.

After completing the establishment of PDU Session, verify whether business A can be normally carried out on the corresponding PDU Session (the first PDU Session); at the same time, verify whether business B can be carried out normally on the corresponding PDU Session (the second PDU Session).

In step 10, the terminal determines the correct S-NSSAI according to the APP ID of service A in URSP, so as to associate service A with the network slice through the APP ID of service A; correspondingly, in step 13, the terminal determines the correct S-NSSAI according to service B in URSP Determine the correct S-NSSAI to associate service B with the network slice through the APP ID of service B.

The specific processing process of verifying whether the service can be normally carried out on the corresponding PDU Session can be understood by referring to the seventh application embodiment, and will not be repeated here.

It can be seen from the above description that in this application embodiment, the test terminal can associate the correct slice with the APP ID issued by the service and initiate a PDU connection establishment request, and the service can proceed normally after the slice is associated. In addition, Step 1 and Step 2 are leading steps; Step 3 to Step 18 are main steps; Step 19, Step 20 and Step 21 are ending steps.

Application Embodiment Nine

In this application example:

(1) Purpose of the test: To verify whether the terminal supports associating services and slices through FQDN, and whether the services can be carried out normally after associating slices.

(2) Scope of application: applicable to terminals with slicing capability.

(3) Test conditions:

[Test system configuration]

Cell A is an NR cell;

CellId＝01 TAC＝01;

MCC=460 MNC=00;

Test frequency band = n41;

Test frequency point = f1;

UL/DL MCS dynamic configuration;

P-MAX=10dBm;

Ideal channel environment.

[terminal configuration]

Table 32

The testing process includes the following steps:

Step 1: The NR cell remains closed;

Step 2: Insert the USIM card into the terminal and turn it on;

Step 3: activate NR cell A;

Step 8: The instrument sends DL NAS TRANSPORT, where the Payload container type is set to "UE Policy container" ('0101'B), carrying the MANAGE UE POLICY COMMAND message. In the MANAGE UE POLICY COMMAND message, "UE policy part type" is set to "URSP" ('0001'B), and "UE policy part contents" carries URSP configuration information. See Table 6, Table 7, Table 32, Table 9 and Table 10; wherein, Table 32 shows the message content of the information element UE policy part contents in Table 7;

Step 10: The user initiates service A, and the terminal initiates a PDU Session connection establishment request; specifically, verify that the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request, and carries the correct S-NSSAI identifier in the PDU Session Establishment Request, see Table 30 and Table 31;

Step 13: Keep service A running normally, the user initiates service B, and the terminal initiates a PDU Session connection establishment request; specifically, the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request, and carries the correct S-NSSAI in the PDU Session Establishment Request Identification, see Table 30 and Table 31;

Step 19: End business A and business B;

Step 21: Deactivate NR cell A.

Among them, in step 10 to step 15, it can also be executed in parallel in the following manner:

In step 10, the terminal determines the correct S-NSSAI according to the FQDN of service A in the URSP, so as to associate service A with the network slice through the FQDN of service A; correspondingly, in step 13, the terminal determines the correct S-NSSAI according to the FQDN of service B in the URSP , determine the correct S-NSSAI to associate service B with the network slice through the FQDN of service B.

From the above description, it can be seen that in this application embodiment, the test terminal can associate the correct slice through the FQDN issued by the service and initiate a PDU connection establishment request, and the service can proceed normally after the associated slice. In addition, Step 1 and Step 2 are leading steps; Step 3 to Step 18 are main steps; Step 19, Step 20 and Step 21 are ending steps.

Application Example Ten

In this application example:

(1) Test purpose: Verify that the terminal supports URSP configuration update, and whether it can associate services to the correct slice after updating URSP.

(2) Scope of application: applicable to terminals with slicing capability.

(3) Test conditions:

[Test system configuration]

Cell A is an NR cell;

CellId＝01 TAC＝01;

MCC=460 MNC=00;

Test frequency band = n41;

Test frequency point = f1;

UL/DL MCS dynamic configuration;

P-MAX=10dBm;

Ideal channel environment.

[terminal configuration]

Table 33

Table 34

Table 35

Table 36

The testing process includes the following steps:

Step 1: The NR cell remains closed;

Step 2: Insert the USIM card into the terminal and turn it on;

Step 3: activate NR cell A;

Step 8: The instrument sends DL NAS TRANSPORT to configure URSP-related parameters to the terminal, where the Payload container type is set to "UE Policy container" ('0101'B), carrying the MANAGE UE POLICY COMMAND message. In the MANAGE UE POLICY COMMAND message, "UE policy part type" is set to "URSP" ('0001'B), "UE policy part contents" carries URSP configuration information, and DNN_1 is mapped to slice 1. For details, see Table 6 to Table 10 ;

Step 11: The terminal initiates service A, and the terminal initiates a PDU Session connection establishment request; specifically, the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request, and the terminal carries DNN=DNN_1 and the correct S-NSSAI identifier in the PDU establishment request, See Table 33 and Table 34; wherein, Table 33 shows the content of the UL NAS TRANSPORT message; Table 34 shows the message content of the value PDU SESSION ESTABLISHMENT REQUEST of the information element Payload container in Table 33;

Step 12: After receiving the request, the instrument configures DNN, S-NSSAI and QCI to the terminal by replying PDU Session Establishment Accept, see Table 35; where, Table 35 shows the content of the PDU Session Establishment Accept message;

Step 13: After completing the establishment of the PDU Session, execute the test process to verify whether business A is normally carried out on the first PDU Session;

Step 14: The instrument sends DL NAS TRANSPORT to update and configure URSP related parameters to the terminal, where the Payload container type is set to "UE Policy container" ('0101'B), carrying the MANAGE UE POLICY COMMAND message. In the MANAGE UE POLICY COMMAND message, "UE policy part type" is set to "URSP" ('0001'B), "UE policy part contents" carries URSP configuration information, and DNN_1 is mapped to slice 2, see Table 36 for details; among them, Table 36 shows the message content of the information element UE policy part contents;

Step 15: The terminal replies to UL NAS TRANSPORT with MANAGE UE POLICY COMPLETE message;

Step 16: The user initiates service A, and the terminal initiates a PDU Session connection establishment request. Specifically, the terminal sends a UL NAS TRANSPORT message and carries a PDU Session Establishment Request. The terminal carries DNN=DNN_1 and the correct S-NSSAI identifier in the PDU establishment request, See Table 33 and Table 34;

Step 17: After receiving the request, the instrument will reply PDU Session Establishment Accept, configure DNN, S-NSSAI and QCI, etc., see Table 35;

Step 18: After completing the establishment of the PDU Session, execute the test process to verify whether business A is normally carried out on the second PDU Session;

Step 19: End the test process of service A, and generate the test result of the terminal; the test result includes the test pass or fail result of each test process;

Step 20: End business A and business B;

Step 21: The instrument sends an RRCRelease message to release the NR link, that is, release the RRC link;

Step 22: Deactivate NR cell A.

It can be seen from the above description that in this application embodiment, it is tested whether the terminal can support URSP update, and can correctly associate the service with the updated slice. In addition, Step 1 and Step 2 are leading steps; Step 3 to Step 19 are main steps; Step 20, Step 21 and Step 22 are ending steps.

The solution provided by the embodiments of the present disclosure can configure a test input 1 to the terminal to test multiple test outputs 1~P of the terminal, as shown in Figure 2; it can also configure multiple test inputs 1~P to the terminal. K, a plurality of test output quantities 1 to P of the test terminal, as shown in FIG. 3 , where K and P may be equal or different.

In order to implement the method of the embodiment of the present disclosure, the embodiment of the present disclosure also provides a 5G slice test device, which is set on the test system, as shown in FIG. 4 , the device includes:

The configuration unit 401 is configured to configure test parameters associated with the network slicing service to the terminal;

The testing unit 402 is configured to execute at least two test procedures on the terminal during the network slicing service process of the terminal, and obtain the test results of the test indicators of each test procedure; the at least two test procedures are used to test the The test index of the terminal in the multi-network slicing service concurrent scenario, or the test index for testing the terminal in the single network slicing service scenario; and use the test result of the test index of each test process to generate test results.

Wherein, in an embodiment, the configuration unit 401 is configured to configure at least two PDU Sessions to the terminal;

Execute at least two services in parallel on at least two PDU Sessions.

Wherein, in an embodiment, the configuration unit 401 is configured to configure a PDU Session on a network slice to the terminal, where the one PDU Session corresponds to at least two services;

Executing the at least two services in parallel on the one PDU Session.

In an embodiment, the configuration unit 401 is configured to configure a value of a test parameter to the terminal;

The testing unit 402 is used for:

During the process of the terminal performing the network slicing service, sequentially execute the at least two test procedures on the terminal;

Wherein, in one embodiment, the test unit 402 is configured to end the test when the test result obtained by the first test process in the at least two test processes does not meet the test judgment condition; the first test process is Other test processes except the last test process among at least two test processes executed in sequence.

The testing unit 402 is used for:

During the process of the terminal performing network slicing services, executing the at least two test procedures in parallel on the terminal;

Based on the test results of the test indicators of each test process and the corresponding test judgment conditions, the test results for the terminal are generated; the test judgment conditions are used to judge the success or failure of the test of the corresponding test process.

In one embodiment, the configuration unit 401 is configured to configure Q times of test parameters to the terminal; Q is an integer greater than or equal to 2;

The testing unit 402 is used for:

Each time the test parameters are configured, during the process of the terminal performing network slicing services, the at least two test procedures are sequentially executed on the terminal;

In an embodiment, during each sequential execution of the at least two test procedures on the terminal, when the test value of the test index obtained by the first test procedure in the at least two test procedures does not satisfy the test judgment condition, the test unit 402 ends the test; the first test process is a test process except the last test process among at least two test processes executed in sequence.

The testing unit 402 is used for:

Each time the test parameters are configured, during the process of the terminal performing network slicing services, the at least two test procedures are executed in parallel on the terminal;

In practical application, the configuration unit 401 and the testing unit 402 can be implemented by a processor in the 5G slice testing device combined with a communication interface.

It should be noted that: when the test device provided by the above-mentioned embodiment is tested, the division of the above-mentioned program modules is used as an example for illustration. The internal structure of the program is divided into different program modules to complete all or part of the processing described above. In addition, the 5G slice test device provided in the above embodiment is based on the same idea as the test method embodiment, and its specific implementation process is detailed in the method embodiment, and will not be repeated here.

Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiment of the present disclosure, the embodiment of the present disclosure also provides a 5G slice test system, as shown in FIG. 5 , the 5G slice test system 500 includes:

The communication interface 501 is capable of information interaction with the terminal;

The processor 502 is connected to the communication interface 501 to implement information interaction with the terminal, and is used to execute the methods provided by one or more technical solutions on the side of the 5G slice test system described above when running the computer program. Instead, the computer program is stored on the memory 503 .

Specifically, the processor 502 is configured to:

Configure test parameters associated with the network slicing service to the terminal through the communication interface 501; and execute at least two test procedures on the terminal during the process of performing the network slicing service on the terminal, and obtain test indicators for each test procedure The test results; the at least two test procedures are used to test the test indicators of the terminal in the multi-network slicing concurrent scenario, or to test the test indicators of the terminal in the single network slicing scenario; and use each The test results of the test indicators of a test process are generated to generate test results for the terminal.

Wherein, in an embodiment, the processor 502 is configured to: configure at least two PDU Sessions to the terminal through the communication interface 501;

Execute at least two services in parallel on at least two PDU Sessions.

In one embodiment, the processor 502 is configured to:

Configure the value of the test parameter once to the terminal;

Wherein, in one embodiment, the processor 502 is configured to end the test when the test result obtained by the first test procedure in the at least two test procedures does not satisfy the test judgment condition; the first test procedure is Other test processes except the last test process among at least two test processes executed in sequence.

In one embodiment, the processor 502 is configured to:

Configure the value of the test parameter once to the terminal;

In one embodiment, the processor 502 is configured to:

Configuring Q test parameters to the terminal; Q is an integer greater than or equal to 2;

Wherein, in one embodiment, during each sequential execution of the at least two test procedures on the terminal, when the test value of the test index obtained by the first test procedure in the at least two test procedures does not meet the When the judgment condition is tested, the processor 502 ends the test; the first test process is a test process except the last test process among at least two test processes executed sequentially.

In one embodiment, the processor 502 is configured to:

It is used to configure Q times of test parameters to the terminal; Q is an integer greater than or equal to 2;

It should be noted that: the specific processing process of the processor 502 can be understood with reference to the above method.

Of course, in actual application, various components in the 5G slice test system 500 are coupled together through the bus system 504 . It can be understood that the bus system 504 is used to realize connection and communication between these components. In addition to the data bus, the bus system 504 also includes a power bus, a control bus and a status signal bus. However, for clarity of illustration, the various buses are labeled as bus system 504 in FIG. 5 .

The memory 503 in the embodiment of the present disclosure is used to store various types of data to support the operation of the 5G slice test system 500 . Examples of such data include: any computer programs for operating on the 5G slice test system 500 .

The methods disclosed in the foregoing embodiments of the present disclosure may be applied to the processor 502 or implemented by the processor 502 . The processor 502 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor 502 or an instruction in the form of software. The aforementioned processor 502 may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The processor 502 may implement or execute various methods, steps, and logic block diagrams disclosed in the embodiments of the present disclosure. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present disclosure may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and the storage medium is located in the memory 503, and the processor 502 reads the information in the memory 503, and completes the steps of the foregoing method in combination with its hardware.

In an exemplary embodiment, the 5G slice test system 500 can be implemented by one or more application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), DSP, programmable logic device (Programmable Logic Device, PLD), complex programmable logic device (Complex Programmable Logic Device, CPLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processor, controller, microcontroller (Micro Controller Unit, MCU), microprocessor (Microprocessor), or Other electronic components are implemented for performing the aforementioned method.

It can be understood that the memory 503 in the embodiment of the present disclosure may be a volatile memory or a nonvolatile memory, and may also include both volatile and nonvolatile memories. Among them, the non-volatile memory can be read-only memory (Read Only Memory, ROM), programmable read-only memory (Programmable Read-Only Memory, PROM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory , EPROM), Electrically Erasable Programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), Magnetic Random Access Memory (ferromagnetic random access memory, FRAM), Flash Memory (Flash Memory), Magnetic Surface Memory , CD, or CD-ROM (Compact Disc Read-Only Memory, CD-ROM); magnetic surface storage can be disk storage or tape storage. The volatile memory can be Random Access Memory (RAM), which acts as an external cache. By way of illustration and not limitation, many forms of RAM are available such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory Memory (Dynamic Random Access Memory, DRAM), Synchronous Dynamic Random Access Memory (Synchronous Dynamic Random Access Memory, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate Synchronous Dynamic Random Access Memory, DDRSDRAM), enhanced Synchronous Synchronous Dynamic Random Access Memory (Enhanced Synchronous Dynamic Random Access Memory, ESDRAM), Synchronous Connection Dynamic Random Access Memory (SyncLink Dynamic Random Access Memory, SLDRAM), Direct Memory Bus Random Access Memory (Direct Rambus Random Access Memory, DRRAM ). The memories described by embodiments of the present disclosure are intended to include, but are not limited to, these and any other suitable types of memories.

In an exemplary embodiment, an embodiment of the present disclosure also provides a storage medium, that is, a computer storage medium, specifically a computer-readable storage medium, for example, including a memory 503 storing a computer program, and the above-mentioned computer program can be used by the 5G slice test system 500 The processor 502 is executed to complete the steps described in the foregoing method. The computer-readable storage medium can be memories such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM.

It should be noted that: "first", "second", etc. are used to distinguish similar objects, and not necessarily used to describe a specific order or sequence.

In addition, the technical solutions described in the embodiments of the present disclosure may be combined arbitrarily if there is no conflict.

The above descriptions are only preferred embodiments of the present disclosure, and are not intended to limit the protection scope of the present disclosure.

Claims

A 5G slice test method, comprising:

Configure the test parameters associated with the network slicing service to the terminal;

During the process of the terminal performing network slicing services, at least two test procedures are executed on the terminal to obtain the test results of the test indicators of each test procedure; the at least two test procedures are used to test multi-network slicing services A test indicator of the terminal in a concurrent scenario, or a test indicator for testing the terminal in a single network slice business scenario;

The test results for the terminal are generated by using the test results of the test indicators of each test process.
The method according to claim 1, wherein,

The indicators of each test process are different, and the business of each test process is the same;

Or, the indicators of each test process are the same, and the business of each test process is different;

Or, the indicators of each test process are different, and the business of each test process is different.
The method according to claim 1, wherein, in the scenario of concurrent multi-network slicing services, the number of services is N, and the number of network slices is M; M is less than or equal to N; M and N are both integers.
The method according to claim 3, wherein at least two services use the same network slice or each service uses one network slice;

Execute a test process for each service or execute a test process on the protocol data unit session PDU Session of each network slice.
The method according to claim 4, further comprising:

Configure at least two protocol data unit session PDU Session to the terminal;

Execute at least two services in parallel on at least two PDU Sessions.
The method according to claim 4, further comprising:

Configuring a PDU Session on a network slice to the terminal, wherein the one PDU Session corresponds to at least two services;

Executing the at least two services in parallel on the one PDU Session.
The method according to claim 1, wherein, in the case that the test indexes of each test flow are different, the test indexes of each test flow are correlated with each other.
The method according to claim 1, wherein the test parameters associated with the network slicing service include at least one of the following:

Parameters used to characterize network slices;

Parameters used to characterize business attributes;

Parameters of the terminal routing selection policy URSP.
The method according to claim 8, wherein the parameters for characterizing network slices include at least one of the following:

Network slice identification;

Quality of Service QoS;

and / or,

The parameters used to characterize business attributes include at least one of the following:

Business application identification;

Business fully qualified domain name FQDN information;

Internet Protocol IP triplet information of the service;

Business data network name DNN information;

Service connection capability CC information.
The method according to claim 1, wherein the two test procedures include a first test procedure and a second test procedure; the first test procedure and the second test procedure include one or a combination of the following test indicators:

Downlink throughput;

delay;

Uplink throughput;

power consumption.
The method according to claim 1, wherein a virtual network environment is constructed; the network slicing service performed on the terminal is a service of the virtual network environment.
The method according to any one of claims 1 to 11, wherein the value of the test parameter is configured once for the terminal; during the process of performing the network slicing service on the terminal, the at least two testing process;

Based on the obtained test results of the test indicators of the test process and corresponding test judgment conditions, the test results for the terminal are generated; the test judgment conditions are used to judge the success or failure of the test of the corresponding test process.
The method according to claim 12, wherein, when the test result obtained by the first test process in the at least two test processes does not meet the test judgment condition, the test is ended; the first test process is at least two sequentially executed Other test processes except the last test process in the first test process.
The method according to any one of claims 1 to 11, wherein the value of the test parameter is configured once for the terminal; during the process of performing the network slicing service on the terminal, the at least two tests are executed in parallel on the terminal. testing process;

Based on the test results of the test indicators of each test process and the corresponding test judgment conditions, the test results for the terminal are generated; the test judgment conditions are used to judge the success or failure of the test of the corresponding test process.
The method according to any one of claims 1 to 11, wherein Q times of test parameters are configured to the terminal; Q is an integer greater than or equal to 2; each time a test parameter is configured, network slicing services are performed on the terminal During the process, the at least two test procedures are sequentially executed on the terminal;

Based on the test results of the test indicators of the test process obtained each time and the corresponding test judgment conditions, the test results for the terminal are generated; the test judgment conditions are used to judge the success or failure of the test of the corresponding test process.
The method according to claim 15, wherein, in the process of sequentially executing the at least two test procedures on the terminal each time, when the test indicators obtained by the first test procedure in the at least two test procedures are tested When the value does not satisfy the test judgment condition, the test ends; the first test process is a test process except the last test process among the at least two test processes executed sequentially.
The method according to any one of claims 1 to 11, wherein Q times of test parameters are configured to the terminal; Q is an integer greater than or equal to 2; each time a test parameter is configured, network slicing services are performed on the terminal During the process, the at least two test procedures are executed in parallel on the terminal;

Based on the test results of the test indicators of the test process obtained each time and the corresponding test judgment conditions, the test results for the terminal are generated; the test judgment conditions are used to judge the success or failure of the test of the corresponding test process.
A 5G slice test device, comprising:

The configuration unit is used to configure test parameters associated with the network slicing service to the terminal;

The test unit is configured to execute at least two test procedures on the terminal during the network slicing service process of the terminal, and obtain the test results of the test indicators of each test procedure; the test indicators of each test procedure are different and/or Or the business of each test process is different; the at least two test processes are used to test the test indicators of the terminal in the concurrent multi-network slice business scenario, or to test the test of the terminal in the single network slice business scenario Index: using the test result of the test index of each test process to generate the test result for the terminal.
A 5G slice test system, including: a processor and a communication interface; wherein,

said processor for:

Configuring test parameters associated with the network slicing service to the terminal through the communication interface; and performing at least two test procedures on the terminal during the process of performing the network slicing service on the terminal, to obtain the test index of each test procedure Test results; the at least two test procedures are used to test the test indicators of the terminal in a multi-network slice business scenario, or to test the test indicators of the terminal in a single network slice business scenario; and use each The test result of the test indicator of the test process generates a test result for the terminal.
A 5G slice testing system, comprising: a processor and a memory for storing a computer program capable of running on the processor,

Wherein, when the processor is used to run the computer program, it executes the steps of the method according to any one of claims 1 to 17.
A storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 17 are implemented.