Test method, device and equipment for terminal slice selection and readable storage medium

Abstract

Embodiments of the present application provide a terminal slice selection test method, device and equipment and a readable storage medium, a slice identifier of a data packet and an address identifier carried in the data packet are acquired, an address identifier of a server corresponding to the slice identifier is searched in a first mapping table, if the address identifier of the server is the same as the address identifier carried in the data packet, it is determined that the terminal slice routing selection is correct, or if the address identifier of the server is not the same as the address identifier carried in the data packet, it is determined that the terminal slice routing selection is incorrect, wherein the first mapping table records a mapping relationship between the address identifier of the server and the slice identifier of an application service.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a test method, apparatus, device, and readable storage medium for terminal slice selection. Background Technology

[0002] In related technologies, testing solutions for terminal slicing capabilities require the terminal to track internal data transmission paths. This method requires the terminal to open data interfaces and specific tools for data capture and analysis, making it impractical for widespread application. Summary of the Invention

[0003] This application provides a testing method, apparatus, device, and readable storage medium for terminal slice selection, addressing the problem that testing schemes for terminal slice selection in related technologies lack widespread applicability.

[0004] In a first aspect, a test method for terminal slice selection is provided, applied to a first device, including:

[0005] Obtain the slice identifier of the data packet, and the address identifier carried in the data packet;

[0006] Look up the address identifier of the server corresponding to the slice identifier in the first mapping table;

[0007] If the address identifier of the server is the same as the address identifier carried in the data packet, then the terminal slice routing selection is determined to be correct; otherwise, the terminal slice routing selection is incorrect.

[0008] The first mapping table records the mapping relationship between the server's address identifier and the application service's slice identifier.

[0009] Optionally, the address identifier of the server corresponding to the slice identifier is searched in the first mapping table; if the address identifier of the server is the same as the address identifier carried in the data packet, the terminal slice routing is determined to be correct; otherwise, the terminal slice routing is determined to be incorrect, including:

[0010] A second mapping table is determined, which records the mapping relationship between the slice identifier of the PDU session carrying the data packet and the address identifier carried by the data packet after the terminal slice selection.

[0011] In the first mapping table, the address identifier of the corresponding server is found by using the slice identifier in the second mapping table as an index, and then compared with the address identifier in the second mapping table;

[0012] If the address identifier in the second mapping table is in the address identifier of the server corresponding to the slice identifier in the first mapping table, then the terminal slice route selection is determined to be correct.

[0013] If the address identifier in the second mapping table is not in the address identifier of the server corresponding to the slice identifier in the first mapping table, then the terminal slice routing is determined to be incorrect.

[0014] Optionally, the method further includes:

[0015] Obtain a third mapping table, which records the mapping relationship between the identifier of the application service and the slice identifier used by the application service;

[0016] Obtain the fourth mapping table, which records the mapping relationship between the identifier of the application service and the address identifier of the server used by the application service;

[0017] The first mapping table is determined based on the third mapping table and the fourth mapping table.

[0018] Optionally, the slice identifier of the data packet is: the slice identifier of the slice used by the data packet obtained by the first device based on the PDU session used by the received data packet.

[0019] Optionally, the address identifier carried by the data packet includes: an IP address, or a port number, or both an IP address and a port number.

[0020] Secondly, a testing device for terminal slice selection is provided, applied to a first device, comprising:

[0021] The first acquisition module is used to acquire the slice identifier of the data packet and the address identifier carried in the data packet;

[0022] The lookup module is used to look up the address identifier of the server corresponding to the slice identifier in the first mapping table;

[0023] The judgment module is used to determine that the terminal slice routing selection is correct if the address identifier of the server is the same as the address identifier carried in the data packet; otherwise, the terminal slice routing selection is incorrect.

[0024] The first mapping table records the mapping relationship between the server's address identifier and the application service's slice identifier.

[0025] Optionally, the testing apparatus further includes:

[0026] The first determining module is used to determine the second mapping table, which records the relationship between the slice identifier of the PDU session carrying the data packet and the address identifier carried by the data packet after the terminal slice selection.

[0027] The lookup module is further configured to: look up the address identifier of the corresponding server in the first mapping table using the slice identifier in the second mapping table as an index, and compare it with the address identifier in the second mapping table;

[0028] The judgment module is further configured to: if the address identifier in the second mapping table is in the address identifier of the server corresponding to the slice identifier in the first mapping table, then determine that the terminal slice routing is correct; if the address identifier in the second mapping table is not in the address identifier of the server corresponding to the slice identifier in the first mapping table, then determine that the terminal slice routing is incorrect.

[0029] Optionally, the testing apparatus further includes:

[0030] The second acquisition module is used to acquire a third mapping table, which records the mapping relationship between the identifier of the application service and the slice identifier used by the application service.

[0031] The third acquisition module is used to acquire the fourth mapping table, which records the mapping relationship between the identifier of the application service and the address identifier of the server used by the application service.

[0032] The second determining module is used to determine the first mapping table based on the third mapping table and the fourth mapping table.

[0033] Optionally, the slice identifier of the data packet is: the slice identifier of the slice used by the data packet obtained by the first device based on the PDU session used by the received data packet.

[0034] Thirdly, a communication device is provided, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, performs the steps of the method described in the first aspect.

[0035] Fourthly, a readable storage medium is provided, on which a program is stored, which, when executed by a processor, implements the steps of the method described in the first aspect.

[0036] In this embodiment, the segment identifier of the data packet and the address identifier carried in the data packet are obtained; then, the address identifier of the server corresponding to the segment identifier is searched in the first mapping table; if the address identifier of the server is the same as the address identifier carried in the data packet, the terminal segment routing selection is determined to be correct; otherwise, the terminal segment routing selection is incorrect. There are no requirements on the terminal side, the terminal does not need to develop additional testing functions for segment selection testing, and the terminal does not need to provide any signaling and data logs. Therefore, it is applicable to non-commercial terminals in the R&D verification stage and commercial terminals that support slicing through OTA upgrades, and has broad application feasibility. Attached Figure Description

[0037] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0038] Figure 1 This is a schematic diagram of application layer data transmission by a terminal in a 5G mobile communication network via a PDU session;

[0039] Figure 2 This is a diagram illustrating how the terminal maps application layer data to incorrect slices and PDU sessions;

[0040] Figure 3 This is a flowchart of the terminal slice selection test method provided in the embodiments of this application;

[0041] Figure 4 This is a schematic diagram of the terminal slice selection test in Example 1;

[0042] Figure 5 This is a schematic diagram of the terminal slice selection test device provided in the embodiments of this application;

[0043] Figure 6 This is a schematic diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0045] The term "comprising," and any variations thereof, used in the specification and claims of this application, is intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product, or apparatus. Furthermore, the use of "and / or" in the specification and claims indicates at least one of the connected objects, such as A and / or B, indicating the inclusion of A alone, B alone, or both A and B.

[0046] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0047] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. However, the following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description, although these technologies can also be applied to applications other than NR systems, such as 6th Generation (6G) communication systems.

[0048] To facilitate understanding of the embodiments of this application, the following technical points are introduced first:

[0049] I. Regarding Protocol Data Unit (PDU) sessions:

[0050] In mobile communication networks, a PDU session can be understood as a connection between a terminal and an external network access point gateway. Taking 5G technology as an example, a PDU session is characterized by an IP address assigned to the terminal and a Data Network Name (DNN) (a User Plane Function (UPF) identifier that identifies different destination networks outside the 5G network). The methods by which the terminal performs application layer data transmission through the PDU session in a 5G mobile communication network are as follows... Figure 1 As shown.

[0051] Taking the upstream data packet as an example, the terminal requests to establish a PDU session -> the network and the terminal negotiate to establish a PDU session and determine the source IP address and DNN assigned to the terminal -> data packets from different applications form multiple different data streams -> after passing through a Quality of Service (QoS) filter, a QoS flow is formed (multiple data streams with the same QoS requirements can be mapped to the same QoS flow) -> the QoS flow is mapped to the PDU session (multiple QoS flows can be mapped to the same PDU session).

[0052] II. Regarding the relationship between slices and PDU sessions:

[0053] Slices are carried through PDU sessions. A PDU session can only carry one slice. When the slice service is enabled, each PDU session will carry a slice identifier.

[0054] III. UE Route Selection Policy (URSP) Rules:

[0055] URSP rules describe the mapping relationship between application services and slices. The terminal selects the corresponding slice for the application service according to the URSP rules. Considering that the actual bearer of the slice is the PDU session, it can also be assumed that the terminal selects or establishes the correct PDU session for the application service according to the URSP rules and transmits the application service data stream on the PDU session.

[0056] See Figure 2When a terminal maps application layer data to the wrong slice and PDU session due to URSP rule parsing errors or application service identification errors, the application layer data may still reach the correct server, but the slice service subscribed to by that application will not be available, affecting the performance improvements such as security and latency brought by slicing. Furthermore, because application layer data packets themselves do not carry identification information (such as the AppID), and have already undergone layer-by-layer encapsulation through the transport layer, IP layer, and PDCP layer during transmission through the PDU session, it is impossible to identify which application service the data packet originates from from the packet itself. Therefore, it is impossible to verify whether the correct application service is being carried on the PDU session.

[0057] In scenarios involving multiple slices, multiple application services, and multiple PDU sessions, verifying how the terminal correctly selects the slice and corresponding PDU session for transmission according to the URSP rules for the application layer data stream is an urgent problem to be solved.

[0058] See Figure 3 This application provides a terminal slice selection test method, which is applied to a first device, such as a test instrument, a network element device for terminal testing, or other electronic devices for terminal testing. The specific steps include: step 301, step 302 and step 303.

[0059] Step 301: Obtain the slice identifier that carries the data packet slice, and the address identifier carried in the data packet;

[0060] The slice identifier of the above data packet can also be understood as the slice identifier that carries the data packet slice.

[0061] Step 302: Look up the address identifier of the server corresponding to the slice identifier in the first mapping table;

[0062] Step 303: If the address identifier of the server is the same as the address identifier carried in the data packet, then the terminal slice routing selection is determined to be correct; otherwise, the terminal slice routing selection is determined to be incorrect.

[0063] The first mapping table records the mapping relationship between the server's address identifier and the application service's slice identifier.

[0064] It is understood that application services can also be described as applications (APP), and the type of application services is not specifically limited in this application embodiment.

[0065] In one embodiment of this application, the address identifier of the server corresponding to the slice identifier is searched in the first mapping table; if the address identifier of the server is the same as the address identifier carried in the data packet, the terminal slice routing is determined to be correct; otherwise, the terminal slice routing is determined to be incorrect, including:

[0066] A second mapping table is determined, which records the mapping relationship between the slice identifier of the PDU session carrying the data packet and the address identifier carried by the data packet after the terminal slice selection.

[0067] In the first mapping table, the address identifier of the corresponding server is found by using the slice identifier in the second mapping table as an index, and then compared with the address identifier in the second mapping table;

[0068] If the address identifier in the second mapping table is in the address identifier of the server corresponding to the slice identifier in the first mapping table, then the terminal slice route selection is determined to be correct.

[0069] If the address identifier in the second mapping table is not in the address identifier of the server corresponding to the slice identifier in the first mapping table, then the terminal slice routing is determined to be incorrect.

[0070] It is understandable that a second mapping table is determined when each data packet is received, or a second mapping table is determined when all data packets are received.

[0071] In one embodiment of this application, the method further includes:

[0072] Obtain a third mapping table, which records the mapping relationship between the identifier of the application service and the slice identifier used by the application service;

[0073] Obtain the fourth mapping table, which records the mapping relationship between the identifier of the application service and the address identifier of the server used by the application service;

[0074] The first mapping table is determined based on the third mapping table and the fourth mapping table.

[0075] In one embodiment of this application, the slice identifier of the data packet is: the slice identifier of the slice used by the data packet obtained by the first device based on the PDU session used by the received data packet.

[0076] In one embodiment of this application, the address identifier carried by the data packet includes: an IP address, or a port number, or both an IP address and a port number.

[0077] In this embodiment, there are no requirements for the terminal side. The terminal does not need to develop additional testing functions for slicing testing, nor does it need to provide any signaling or data logs. Therefore, this solution is applicable to both non-commercial terminals in the R&D verification stage and commercial terminals that have been upgraded to support slicing via Over-the-Air (OTA) technology. In this embodiment, the testing function is implemented at the PDU session level and above, eliminating the need to track link layer data or perform full data packet comparison, thus reducing the complexity and computational load of the test. The testing solution in this embodiment is based on a testing system and does not require real network cooperation. When performing tests with a large testing volume, such as terminal network access testing, operator database access testing, post-evaluation testing, and third-party certification testing, it can effectively improve testing efficiency and reduce testing costs, and has great potential for practical application.

[0078] The following is based on Figure 4 The method shown is illustrated using a test instrument (or described as a test device) as an example.

[0079] The testing instrument generates a first mapping table, which is used to record the mapping relationship between the server's address identifier and the application service's slice identifier. The specific method may include steps 1 to 4.

[0080] Step 1: Based on the application service to be tested and the corresponding slice identifier configured by the user, the testing instrument generates an application service identifier for each application service to be tested input by the user, and forms a mapping table from application service identifier to slice identifier. The mapping table contains one or more mapping relationships between the "identifier of the application service and the slice identifier used by the application service" in this test.

[0081] Table 1: Third Mapping Table

[0082] Application business identifier Slice identifiers used by application services APP#1 S-NSSAI = 1 APP#2 S-NSSAI=2

[0083] Step 2: Based on the test system configuration, the test instrument obtains the address identifier, which refers to the address identifier of the server used by each application service to be tested, and forms a mapping table from application service identifier to address identifier. The mapping table contains one or more mapping relationships between "the identifier of the application service and the address identifier of the server used by the application service" in this test.

[0084] Table 2: Fourth Mapping Table

[0085] Application business identifier The address identifier of the server used by the application business APP#1 IP#1 APP#2 IP#2

[0086] Step 3: Based on Step 1 and Step 2, form a mapping table from slice identifier to address identifier (first mapping table). The mapping table contains one or more mapping relationships, and should at least include the mapping relationship between "the slice identifier used by the application service and the address identifier of the server used by the application service" in this test.

[0087] Optionally, based on steps 1 and 2, a mapping table of application service identifiers, slice identifiers, and address identifiers is formed. The mapping table contains one or more mapping relationships between "the identifier of the application service and the slice identifier used by the application service and the address identifier of the server used by the application service" in this test.

[0088] Table 3: First Mapping Table

[0089] Slice identifiers used by application services The address identifier of the server used by the application business S-NSSAI = 1 IP#1 S-NSSAI=2 IP#2

[0090] Table 4: First Mapping Table

[0091]

[0092] Step 4: The testing instrument saves the mapping table generated in step 3, which is denoted as the first mapping table.

[0093] Based on step 1, the application service identifier can be any symbol or number that can uniquely identify the application service and distinguish it from other services;

[0094] Based on step 1, the slice identifier can be the S-NSSAI of the slice used by the application service, or other numbers or symbols that can correspond to the S-NSSAI of the slice used by the application service.

[0095] Based on step 2, the address identifier can be the IP address or port number of the server used by the application service during the test, or both the IP address and port number.

[0096] This operation runs one or more application services on the terminal. According to existing solutions, this operation triggers the terminal to select the correct slice for each application service based on URSP rules and establish a corresponding PDU session. After the application service data stream is mapped to the corresponding slice and PDU session within the terminal, application service data transmission occurs on the PDU session.

[0097] The testing instrument constructs a second mapping table, which records the mapping relationship between the slice identifier carrying the data packet and the address identifier carried by the data packet after terminal slice selection. Specifically:

[0098] a) The test instrument receives data packets, obtains the slice identifier of the slice used by the data packet according to the PDU session used by the received data packet, and records the slice identifier of each data packet.

[0099] b) The testing instrument decodes each received data packet to obtain the IP address or port number or both of the data packet, which is denoted as the "address identifier to be compared".

[0100] c) Based on 3a) and 3b), the test instrument creates a "slice identifier -> address identifier to be compared" mapping relationship for each received data packet, forming a second mapping table.

[0101] Table 5: Second Mapping Table

[0102] Data packets Packet slice identifier The address identifier carried in the data packet (the address identifier to be compared). Flow#1' S-NSSAI = 1 IP#1' Flow #2' S-NSSAI=2 IP#2'

[0103] The testing instrument uses a second mapping table for each received data packet to look up the address identifier in the first mapping table, using the slice identifier in the second mapping table as an index, and compares it with the address identifier in the second mapping table.

[0104] The testing instrument determines the test results. If the address identifier in the second mapping table is found in the address identifier corresponding to the slice identifier in the first mapping table, then the terminal slice routing is correct; if the address identifier in the second mapping table is not found in the address identifier corresponding to the slice identifier in the first mapping table, then the terminal slice routing is incorrect.

[0105] Example 1

[0106] See Figure 4 The first mapping table is formed by following these steps:

[0107] a) Based on the testing requirements, the testing instrument generates identifiers APP#1 and APP#2 for the application services to be tested; the slice identifier S-NSSAI is used as the slice identifier, APP#1 uses the slice identifier S-NSSAI=1, and APP#2 uses the slice identifier S-NSSAI=2; the testing instrument generates a mapping table {“APP1—>S-NSSAI=1”, “APP2—>S-NSSAI=2”}.

[0108] b) Use the IP address of the server used by the application business as the address identifier. Test system configuration: The test system records the server address identifier of APP#1 as IP#1 and the server address identifier of APP#2 as IP#2, and generates a mapping table {“APP#1—>IP#1”, “APP#2—>IP#2”}.

[0109] c) The testing instrument generates a first mapping table {“S-NSSAI=1—>IP#1”, “S-NSSAI=2—>IP#2”} or {“APP#1—>S-NSSAI=1—>IP#1”, “APP#2—>S-NSSAI=2—>IP#2”}

[0110] 2. Run APP#1 and APP#2 on the terminal to trigger the terminal to perform slice selection and establish corresponding PDU session #1 (carrying slice identifier S-NSSAI=1) and PDU session #2 (carrying slice identifier S-NSSAI=2). After the terminal performs slice selection, the data generated by APP#1 and APP#2 are transmitted on PDU session #1 and PDU session #2, respectively. If the terminal slice selection is correct, Flow#1 carries the data generated by APP#1, and Flow#2 carries the data generated by APP#2.

[0111] 3. Construct the second mapping table according to the following steps.

[0112] a) The test instrument receives data packets. The data stream received from PDU session #1 is recorded as Flow#1'. The slice identifier of Flow#1' is obtained from PDU session #1 as S-NSSAI=1, and the data packet slice identifier of Flow#1' is recorded as S-NSSAI=1. Similarly, the data stream received from PDU session #2 is recorded as Flow#2', and the data packet slice identifier of Flow#2' is recorded as S-NSSAI=2.

[0113] b) The testing instrument decodes the data packets of Flow#1' and Flow#2' in sequence, obtains the destination IP address of each data packet (denoted as IP'), and generates a comparison mapping relationship {S-NSSAI=1, IP'} or {S-NSSAI=2, IP'} for each data packet.

[0114] 4. Generate test results: Using S-NSSAI in the mapping relationship to be compared as an index, look up the corresponding IP address in the first mapping table. Taking {S-NSSAI=1, IP'} as an example, find the IP address corresponding to S-NSSAI=1 in the first mapping table as IP#1. Compare IP' and IP#1. If IP' = IP#1, the terminal slice route selection is correct; if IP' ≠ IP#1, the terminal slice route selection is incorrect.

[0115] See Figure 5 This application provides a terminal slice selection testing device, applied to a first device. The testing device 500 includes:

[0116] The first acquisition module 501 is used to acquire the slice identifier of the data packet and the address identifier carried in the data packet;

[0117] The lookup module 502 is used to look up the address identifier of the server corresponding to the slice identifier in the first mapping table;

[0118] The judgment module 503 is used to determine that the terminal slice routing selection is correct if the address identifier of the server is the same as the address identifier carried in the data packet; otherwise, it determines that the terminal slice routing selection is incorrect.

[0119] The first mapping table records the mapping relationship between the server's address identifier and the application service's slice identifier.

[0120] In one embodiment of this application, the testing apparatus further includes:

[0121] The first determining module is used to determine the second mapping table, which records the relationship between the slice identifier of the PDU session carrying the data packet and the address identifier carried by the data packet after the terminal slice selection.

[0122] The lookup module is further configured to: look up the address identifier of the corresponding server in the first mapping table using the slice identifier in the second mapping table as an index, and compare it with the address identifier in the second mapping table;

[0123] The judgment module is further configured to: if the address identifier in the second mapping table is in the address identifier of the server corresponding to the slice identifier in the first mapping table, then determine that the terminal slice routing is correct; if the address identifier in the second mapping table is not in the address identifier of the server corresponding to the slice identifier in the first mapping table, then determine that the terminal slice routing is incorrect.

[0124] In one embodiment of this application, the testing apparatus further includes:

[0125] The second acquisition module is used to acquire a third mapping table, which records the mapping relationship between the identifier of the application service and the slice identifier used by the application service.

[0126] The third acquisition module is used to acquire the fourth mapping table, which records the mapping relationship between the identifier of the application service and the address identifier of the server used by the application service.

[0127] The second determining module is used to determine the first mapping table based on the third mapping table and the fourth mapping table.

[0128] In one embodiment of this application, the slice identifier of the data packet is: the slice identifier of the slice used by the data packet obtained by the first device based on the PDU session used by the received data packet.

[0129] The apparatus provided in this application embodiment can achieve... Figure 3 The various processes implemented in the method embodiments shown achieve the same technical effects, and will not be described again here to avoid repetition.

[0130] like Figure 6 As shown, this application embodiment also provides an electronic device 600, including a processor 601, a memory 602, and a program or instructions stored in the memory 602 and executable on the processor 601. When the program or instructions are executed by the processor 601, they implement the above-mentioned... Figure 3 The various processes in the method embodiments can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0131] This application embodiment also provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the above-described functionality. Figure 3 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0132] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0133] The steps of the methods or algorithms described in this application can be implemented in hardware or by executing software instructions on a processor. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, portable hard disk, read-only optical disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can be housed in an ASIC. Alternatively, the ASIC can be housed in a core network interface device. Of course, the processor and storage medium can also exist as discrete components in the core network interface device.

[0134] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0135] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

[0136] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, embodiments of this application can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this application can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0137] This application describes embodiments of methods, apparatus (systems), and computer program products according to embodiments of this application with reference to flowchart illustrations and / or block diagrams. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0138] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1The function specified in one or more boxes.

[0139] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0140] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

Claims

1. A test method for terminal slice selection, applied to a first device, the first device including network element devices for terminal testing, characterized in that, include: Obtain the slice identifier of the data packet, and the address identifier carried in the data packet; Look up the address identifier of the server corresponding to the slice identifier in the first mapping table; If the address identifier of the server is the same as the address identifier carried in the data packet, then the terminal slice routing selection is determined to be correct. Alternatively, if the address identifier of the server is different from the address identifier carried in the data packet, the terminal slice routing selection is determined to be incorrect. The first mapping table records the mapping relationship between the server's address identifier and the application service's slice identifier. The address identifier of the server corresponding to the slice identifier is searched in the first mapping table; if the address identifier of the server is the same as the address identifier carried in the data packet, the terminal slice routing is determined to be correct; or, if the address identifier of the server is not the same as the address identifier carried in the data packet, the terminal slice routing is determined to be incorrect, including: A second mapping table is determined, which records the mapping relationship between the slice identifier of the PDU session carrying the data packet and the address identifier carried by the data packet after the terminal slice selection. In the first mapping table, the address identifier of the corresponding server is found by using the slice identifier in the second mapping table as an index, and then compared with the address identifier in the second mapping table; If the address identifier in the second mapping table is in the address identifier of the server corresponding to the slice identifier in the first mapping table, then the terminal slice routing is determined to be correct; or, if the address identifier in the second mapping table is not in the address identifier of the server corresponding to the slice identifier in the first mapping table, then the terminal slice routing is determined to be incorrect.

2. The method according to claim 1, characterized in that, The method further includes: Obtain a third mapping table, which records the mapping relationship between the identifier of the application service and the slice identifier used by the application service; Obtain the fourth mapping table, which records the mapping relationship between the identifier of the application service and the address identifier of the server used by the application service; The first mapping table is determined based on the third mapping table and the fourth mapping table.

3. The method according to claim 1, characterized in that, The slice identifier of the data packet is: the slice identifier of the slice used by the data packet obtained by the first device based on the PDU session used by the received data packet.

4. The method according to claim 1, characterized in that, The address identifier carried by the data packet includes: IP address, or port number, or IP address and port number.

5. A terminal slice selection testing apparatus, applied to a first device, the first device comprising network element equipment for terminal testing, characterized in that, include: The first acquisition module is used to acquire the slice identifier of the data packet and the address identifier carried in the data packet; The lookup module is used to look up the address identifier of the server corresponding to the slice identifier in the first mapping table; The judgment module is used to determine that the terminal slice routing selection is correct if the address identifier of the server is the same as the address identifier carried in the data packet, or to determine that the terminal slice routing selection is incorrect if the address identifier of the server is not the same as the address identifier carried in the data packet. The first mapping table records the mapping relationship between the server's address identifier and the application service's slice identifier. The testing apparatus also includes: The first determining module is used to determine the second mapping table, which records the relationship between the slice identifier of the session carrying the data packet and the address identifier carried by the data packet after the terminal slice is selected. The lookup module is further configured to: look up the address identifier of the corresponding server in the first mapping table using the slice identifier in the second mapping table as an index, and compare it with the address identifier in the second mapping table; The judgment module is further configured to: if the address identifier in the second mapping table is in the address identifier of the server corresponding to the slice identifier in the first mapping table, then determine that the terminal slice routing is correct; if the address identifier in the second mapping table is not in the address identifier of the server corresponding to the slice identifier in the first mapping table, then determine that the terminal slice routing is incorrect.

6. The testing apparatus according to claim 5, characterized in that, The testing apparatus also includes: The second acquisition module is used to acquire a third mapping table, which records the mapping relationship between the identifier of the application service and the slice identifier used by the application service. The third acquisition module is used to acquire the fourth mapping table, which records the mapping relationship between the identifier of the application service and the address identifier of the server used by the application service. The second determining module is used to determine the first mapping table based on the third mapping table and the fourth mapping table.

7. The testing apparatus according to claim 5, characterized in that, The slice identifier of the data packet is: the slice identifier of the slice used by the data packet obtained by the first device based on the PDU session used by the received data packet.

8. A communication device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method as described in any one of claims 1 to 4.

9. A readable storage medium, characterized in that, The readable storage medium stores a program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 4.

Images