A slice selection method, system and related apparatus

Abstract

A slice selection method, system and related device are provided. In the method, a CPE receives a data packet sent by a UE, the CPE stores a correspondence between network services subscribed by the UE and slices, the CPE determines a slice corresponding to the data packet based on a network service type subscribed by the UE, and routes the data packet to the corresponding slice. By implementing the technical solutions provided in the present application, the CPE can provide differentiated network services for UEs that have subscribed to different network services.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of terminals and communication, and in particular to a slice selection method, system and related device. BACKGROUND

[0002] Currently, in a 5th Generation (5G) communication system, a terminal can access a cellular network through a slice. In order to meet the needs of users in different scenarios, the types of slices are also increasing. An operator can provide differentiated network services to users through different slices.

[0003] For an application scenario in which a Customer Premise Equipment (CPE) exists, a terminal needs to access the CPE first, and the CPE determines a slice corresponding to data sent by the terminal according to a routing policy. The CPE can only identify an IP triple in the routing policy as a routing matching standard of the data, so as to determine the corresponding slice. However, the terminal can subscribe to different network services, and different network services need different slices.

[0004] Therefore, how the CPE provides differentiated network services to terminals subscribing to different network services is a problem to be solved. SUMMARY

[0005] The present application provides a slice selection method, system and related device. By implementing the slice selection method provided in the embodiments of the present application, the CPE can determine a slice network corresponding to data sent by a terminal based on a network service subscribed to by the terminal. In this way, the data sent by the same type of application in different terminals subscribing to different network services can be routed to different slice networks. The CPE can provide differentiated network services to terminals subscribing to different network services.

[0006] In a first aspect, the present application provides a slice selection method, which can include: a first terminal receiving a first data packet sent by a second terminal, the second terminal establishing a communication connection with the first terminal through a wireless fidelity (Wi-Fi) network, and the first terminal establishing a communication connection with a network side through a cellular network; the first terminal determining one or more network services subscribed to by the second terminal, each network service in the one or more network services being associated with a slice network; the first terminal determining that a network service type of the first data packet is a first network service in the one or more network services; and the first terminal transmitting the first data packet to the network side through a first slice network associated with the first network service.

[0007] The first terminal can be a CPE, and the second terminal can be a user terminal such as a mobile phone, a tablet computer, a computer, and the like.

[0008] In a possible implementation, the first data packet can be a service request data packet.

[0009] In this way, the first terminal can determine the slice network to which the data sent by the second terminal corresponds according to the network service subscribed by the second terminal. The first terminal can provide differentiated network services for the second terminals subscribing to different network services.

[0010] With reference to the first aspect, in a possible implementation, the first terminal determines the one or more network services subscribed by the second terminal based on the first identifier of the second terminal, including: the first terminal determines the one or more network services subscribed by the second terminal based on the first identifier of the second terminal.

[0011] With reference to the first aspect, in a possible implementation, the first terminal determines the one or more network services subscribed by the second terminal based on the first identifier of the second terminal, including: the first terminal determines the one or more network services subscribed by the second terminal based on the first identifier of the second terminal.

[0012] In this way, the first terminal can conveniently and accurately find the network service subscribed by the second terminal.

[0013] With reference to the first aspect, in a possible implementation, before the first terminal receives the first data packet sent by the second terminal, the method can further include: the first terminal receives terminal route selection policy (URSP) information sent by the network side, the URSP information including one or more slice parameter information, the one or more slice parameter information including first slice parameter information, and the first slice parameter information being used to indicate the first slice network.

[0014] With reference to the first aspect, in a possible implementation, the first terminal determines the one or more network services subscribed by the second terminal, including: the first terminal determines that the one network service subscribed by the second terminal is a first network service; and the first terminal determines that the network service type corresponding to the first data packet is the first network service in the one or more network services, including: the first terminal determines that the network service type corresponding to the first data packet is the first network service.

[0015] With reference to the first aspect, in a possible implementation manner, in a case that the first network service is a directed service, the first terminal determines that the network service type corresponding to the first data packet is the first network service, including: the first terminal acquires a service feature in the first data packet; the first terminal matches the service feature with a service feature corresponding to the directed service in the URSP information; in a case that the service feature is successfully matched with the service feature corresponding to the directed service in the URSP information, the first terminal determines that the network service type corresponding to the first data packet is the first network service.

[0016] Generally, the second terminal can subscribe to a directed service for a specific service or a specific application of the second terminal. Therefore, it is needed to match whether the data is sent by the application in which the specific service is located or the specific application according to the URSP rule, if yes, the network service of the data is the directed service, if no, the network service corresponding to the data is not the directed service.

[0017] With reference to the first aspect, in a possible implementation manner, the first terminal determines one or more network services to which the second terminal subscribes, including: the first terminal determines a plurality of network services to which the second terminal subscribes; and the first terminal determines that the network service type corresponding to the first data packet is a first network service in the one or more network services, including: the first terminal determines that the network service type corresponding to the first data packet is the first network service in the plurality of network services based on a service feature of the first data packet and service features corresponding to the plurality of network services in the URSP information.

[0018] With reference to the first aspect, in a possible implementation manner, the first terminal determines that the network service type corresponding to the first data packet is the first network service in the plurality of network services based on a service feature of the first data packet and service features corresponding to the plurality of network services in the URSP information, including: the first terminal acquires a service feature in the first data packet; the first terminal respectively matches the service feature with service features corresponding to the plurality of network services in the URSP information; and in a case that the service feature is successfully matched with the service feature corresponding to the first network service in the URSP information, the first terminal determines that the network service type corresponding to the first data packet is the first network service.

[0019] With reference to the first aspect, in a possible implementation manner, before the first terminal receives the first data packet sent by the second terminal, the method can further include: the first terminal establishes an association relationship between a first identifier of the second terminal and one or more network services in the second terminal based on subscription information sent by the second terminal.

[0020] With reference to the first aspect, in a possible implementation manner, the first terminal transmits the first data packet to the network side through the first slice network associated with the first network service, including: in a case where a protocol data unit (PDU) session corresponding to the first slice network has been established between the first terminal and the network side, the first terminal transmits the first data packet to the network side through the first slice network based on the PDU session.

[0021] With reference to the first aspect, in a possible implementation manner, the first terminal transmits the first data packet to the network side through the first slice network associated with the first network service, including: the first terminal establishes a PDU session corresponding to the first slice network with the network side based on the slice parameter information; and the first terminal transmits the first data packet to the network side through the first slice network based on the PDU session.

[0022] With reference to the first aspect, in a possible implementation manner, after the first terminal transmits the first data packet to the network side through the first slice network associated with the first network service, the method can further include: the first terminal receives a second data packet sent by the network side; and in a case where the first slice network is a low-latency slice network, the first terminal accelerates sending the second data packet to the second terminal.

[0023] Exemplarily, the second data packet can be a service response data packet.

[0024] With reference to the first aspect, in a possible implementation manner, the method can further include: the first terminal receives allowed network slice selection assistance information (Allowed NSSAI) sent by the network side, the Allowed NSSAI being used to indicate a set of slice networks allowed to transmit data by the first terminal; and the first slice network is included in the set of slice networks.

[0025] With reference to the first aspect, in a possible implementation manner, the first identifier includes a username of the second terminal and / or a media access control (MAC) address of the second terminal.

[0026] With reference to the first aspect, in a possible implementation manner, the username of the second terminal can be a mobile phone number of the second terminal.

[0027] With reference to the first aspect, in a possible implementation manner, the service feature of the first data packet includes at least one of an application (App) ID of a first application, IP triple information, data network name (DNN) information, and full qualified domain name (FQDN) information; and the first application is an application of the second terminal that sends the first data packet.

[0028] In a second aspect, a slice selection system is provided, which includes a first terminal and a second terminal. The second terminal establishes a communication connection with the first terminal through a wireless fidelity (Wi-Fi) network, and the first terminal establishes a communication connection with a network side through a cellular network. The second terminal is configured to send a first data packet to the first terminal. The first terminal is configured to receive the first data packet sent by the second terminal. The first terminal is configured to determine one or more network services to which the second terminal subscribes, each of the one or more network services being associated with a slice network. The first terminal is configured to determine that a network service type corresponding to the first data packet is a first network service in the one or more network services. The first terminal is configured to transmit the first data packet to the network side through a first slice network associated with the first network service.

[0029] The first terminal can be a customer premises equipment (CPE), and the second terminal can be a mobile phone, a tablet, a computer, or the like.

[0030] In this way, the first terminal can determine a slice network corresponding to the data sent by the second terminal according to a network service to which the second terminal subscribes. The first terminal can provide differentiated network services for second terminals subscribing to different network services.

[0031] In a possible implementation, the first terminal can further perform the method in any possible implementation of the first aspect.

[0032] In a possible implementation, the second terminal can further perform the method in any possible implementation of the second aspect.

[0033] In a third aspect, a communication apparatus is provided, which includes one or more processors, one or more memories, and a transceiver. The transceiver and the one or more memories are coupled to the one or more processors. The one or more memories are configured to store computer program codes including computer instructions. When the one or more processors execute the computer instructions, the communication apparatus performs the method in any possible implementation of the first terminal in the first aspect.

[0034] The communication apparatus can be the first terminal or a device in other product forms.

[0035] In a fourth aspect, a communication apparatus is provided, which includes one or more processors, one or more memories, and a transceiver. The transceiver and the one or more memories are coupled to the one or more processors. The one or more memories are configured to store computer program codes including computer instructions. When the one or more processors execute the computer instructions, the communication apparatus performs the method in any possible implementation of the second terminal in the first aspect.

[0036] The communication device can be a second terminal or a device in other product forms.

[0037] In a fifth aspect, the present application provides a computer storage medium, including computer instructions, when the computer instructions are run on a computer, the computer executes the method in any possible implementation manner of the first aspect.

[0038] In a sixth aspect, the present application provides a computer program product, when the computer program product is run on a computer, the computer executes the method in any possible implementation manner of the first aspect.

[0039] In a seventh aspect, the present application provides a chip or chip system, applied to a first terminal, including a processing circuit and an interface circuit, the interface circuit is used for receiving code instructions and transmitting to the processing circuit, the processing circuit is used for running the code instructions to execute the method in any possible implementation manner of the first aspect. BRIEF DESCRIPTION OF DRAWINGS

[0040] Figure 1 is a communication system schematic diagram provided by an embodiment of the present application;

[0041] Figure 2 is a structure schematic diagram of a terminal provided by an embodiment of the present application;

[0042] Figure 3 is a structure schematic diagram of a CPE provided by an embodiment of the present application;

[0043] Figure 4 is a URSP format schematic diagram provided by an embodiment of the present application;

[0044] Figure 5 is a CPE access core network flow schematic diagram provided by an embodiment of the present application;

[0045] Figure 6 is a UE access CPE flow schematic diagram provided by an embodiment of the present application;

[0046] Figure 7 is a UE, CPE and core network interaction schematic diagram provided by an embodiment of the present application;

[0047] Figure 8A is a data format schematic diagram provided by an embodiment of the present application;

[0048] Figure 8B is a data format schematic diagram provided by an embodiment of the present application;

[0049] Figure 9 is a slice selection method flow schematic diagram provided by an embodiment of the present application;

[0050] Figure 10 is a URSP flow process schematic diagram provided by an embodiment of the present application;

[0051] Figure 11 is a different network service signing scenario schematic diagram provided by an embodiment of the present application;

[0052] Figure 12 is a user interface schematic diagram provided by an embodiment of the present application;

[0053] Figure 13 is a flow process schematic diagram for determining a network service type corresponding to a data packet sent by a UE provided by an embodiment of the present application;

[0054] Figure 14 is a device structure schematic diagram provided by an embodiment of the present application;

[0055] Figure 15 is a device structure schematic diagram provided by an embodiment of the present application;

[0056] Figure 16 is a device structure schematic diagram provided by an embodiment of the present application;

[0057] Figure 17 is a device structure schematic diagram provided by an embodiment of the present application. DETAILED DESCRIPTION

[0058] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0059] The terms used in the embodiments of the present application are only for the purpose of describing the specific embodiments, and are not intended to be a limitation of the present application. As used in the specification and the appended claims of the present application, the singular forms “a,” “an,” and “the” are intended to include plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” used in the present application means and includes any or all possible combinations of one or more listed items.

[0060] The terms "first", "second", etc. are used only for the purpose of description and shall not be construed to imply or indicate relative importance or imply the number of the indicated technical features. Therefore, the features defined with "first", "second" can explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, the meaning of "a plurality of" is two or more, unless otherwise specified.

[0061] The terms "first", "second", etc. in the description and claims of the present application are used to distinguish different objects, not to describe the specific order of the objects. For example, the first target object and the second target object are used to distinguish different target objects, not to describe the specific order of the target objects.

[0062] In the embodiments of the present application, the words "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Rather, the use of the words "exemplary" or "for example" is intended to present related concepts in a concrete manner.

[0063] Before introducing the technical solutions of the embodiments of the present application, first, the communication system of the embodiments of the present application is described in conjunction with the accompanying drawings.

[0064] Figure 1 An exemplary schematic diagram of a communication system provided by the embodiments of the present application is shown. Referring to FIG. 1, Figure 1 The communication system 10 includes terminals 100 (for example, a mobile phone 101, a watch 102, a computer 103, a projector 104, etc.), CPEs 200 and a core network. It should be noted that in actual applications, the number of terminals 100 and CPEs can be one or more, Figure 1 The number of terminals 100 and CPEs 200 of the communication system 10 shown is only an adaptive example, and the present application does not limit this.

[0065] It should be further noted that the core network can be a device cluster composed of one or more core network devices, and optionally, the core network device can be an access and mobility management function (AMF), which is mainly responsible for access control, mobility management (MM), attachment and detachment, gateway selection and other functions. The core network device involved in the embodiments of the present application is not limited to AMF.

[0066] The terminal 100 can be a wireless communication chip, a wireless sensor, or a wireless communication terminal, and can also be referred to as a user equipment (UE), a station (STA), or a terminal device. For example, the terminal 100 can be a mobile phone supporting wireless fidelity (Wi-Fi) communication function, a tablet computer supporting Wi-Fi communication function, a set-top box supporting Wi-Fi communication function, a smart television supporting Wi-Fi communication function, a smart wearable device supporting Wi-Fi communication function, a vehicle-mounted communication device supporting Wi-Fi communication function, and a computer supporting Wi-Fi communication function, and the like. Optionally, the terminal can support the 802.11be standard. The terminal can also support various wireless local area network (WLAN) standards of the 802.11 family, such as 802.11be, 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0067] For example, the CPE 200 and the terminal 100 can be devices applied in the Internet of Vehicles, Internet of Things (IoT) nodes, sensors, smart cameras in smart homes, smart remote controllers, smart water and electricity meters, and sensors in smart cities, and the like.

[0068] It should be noted that the CPE 200 and the terminal 100 in the present application can also be a wireless communication device supporting parallel transmission of multiple links, for example, a multi-link device or a multi-band device. Compared with a device supporting only single-link transmission, the multi-link device has higher transmission efficiency and higher throughput.

[0069] Although the present application is described with the network deployed between the CPE 200 and the terminal 100 using IEEE 802.11 as an example, it is easy for those skilled in the art to understand that various aspects of the present application can be extended to other networks using various standards or protocols, such as BLUETOOTH, high performance radio local area network (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, mainly used in Europe), and wide area network (WAN), wireless local area network (WLAN), personal area network (PAN), or other now known or later developed networks. Therefore, regardless of the coverage range and wireless access protocol used, various aspects provided by the present application can be applied to any suitable wireless network.

[0070] In a possible implementation, a wired network can also be deployed between the CPE 200 and the terminal 100, and the terminal 100 can be a wired communication chip, a wired sensor, or a wired communication terminal, etc., i.e., a device connected to the CPE 200 through a network cable. In the present application, a wireless network is deployed between the CPE 200 and the terminal 100 as an example. For the scenario of deploying a wired network between the CPE and the terminal, the technical solutions in the embodiments of the present application can also be referred to, and the present application will not be repeated.

[0071] The following describes an exemplary terminal 100 provided by the embodiments of the present application. Figure 2 is a structural schematic diagram of the terminal 100 provided by the embodiments of the present application.

[0072] Referring to Figure 2 , the embodiments are specifically described below by taking the terminal 100 as an example. It should be understood that the terminal 100 can have more or fewer components than those shown in the figure, can combine two or more components, or can have a different component configuration. The various components shown in the figure can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0073] The terminal 100 can include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headset jack 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 can include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0074] It can be understood that the structure shown in the embodiments of the present application does not constitute a specific limitation on the terminal 100. In other embodiments of the present application, the terminal 100 can include more or fewer components than shown, or combine certain components, or split certain components, or different component arrangements. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0075] The processor 110 can include one or more processing units, for example: the processor 110 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units can be independent devices, or can be integrated into one or more processors.

[0076] The controller can be the nerve center and command center of the terminal 100. The controller can generate operation control signals according to instruction operation codes and timing signals, and complete the control of fetching instructions and executing instructions.

[0077] The processor 110 can also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can hold instructions or data that the processor 110 has recently used or is likely to use again. If the processor 110 needs to use the instructions or data again, it can be retrieved directly from the memory. This avoids repeated accesses and reduces the latency of the processor 110, thus improving the efficiency of the system.

[0078] In some embodiments, the processor 110 can include one or more interfaces. The interfaces can include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0079] The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 can include multiple sets of I2C buses. The processor 110 can be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. For example, the processor 110 can be coupled to the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through the I2C bus interface to realize the touch function of the terminal 100.

[0080] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple sets of I2S buses. The processor 110 can be coupled to the audio module 170 through the I2S bus to realize communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can deliver audio signals to the wireless communication module 160 through the I2S interface to realize the function of answering a phone through a Bluetooth headset.

[0081] The PCM interface can also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled through a PCM bus interface.

[0082] The UART interface is a universal serial data bus used for asynchronous communication. The bus can be a bidirectional communication bus. It converts data to be transmitted between serial communication and parallel communication.

[0083] The MIPI interface can be used to connect the processor 110 and peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate through the CSI interface to realize the shooting function of the terminal 100. The processor 110 and the display screen 194 communicate through the DSI interface to realize the display function of the terminal 100.

[0084] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0085] The SIM interface can be used to communicate with the SIM card interface 195 to realize the function of transmitting data to the SIM card or reading data in the SIM card.

[0086] The USB interface 130 is an interface that meets the USB standard specification, and can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the terminal 100, and can also be used to transmit data between the terminal 100 and peripheral devices. It can also be used to connect a headset to play audio through the headset. The interface can also be used to connect other electronic devices, such as AR devices, etc.

[0087] It can be understood that the interface connection relationship between the modules shown in the embodiments of the present application is only illustrative and does not constitute a structural limitation of the terminal 100. In some other embodiments of the present application, the terminal 100 can also use different interface connection methods or combinations of multiple interface connection methods in the above embodiments.

[0088] The charging management module 140 is used to receive charging input from a charger. The charger can be a wireless charger or a wired charger.

[0089] The power management module 141 is configured to connect the battery 142 and the charging management module 140 to the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160.

[0090] The wireless communication function of the terminal 100 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor.

[0091] The antenna 1 and the antenna 2 are configured to transmit and receive electromagnetic wave signals. Each antenna in the terminal 100 can be configured to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example, the antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in combination with a tuning switch.

[0092] The mobile communication module 150 can provide a solution for wireless communication including 2G / 3G / 4G / 5G, etc. applied to the terminal 100. The mobile communication module 150 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, filter, amplify, etc. the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can also amplify signals modulated by the modem processor and convert the signals into electromagnetic waves to be radiated through the antenna 1. In some embodiments, at least part of the functional modules of the mobile communication module 150 can be arranged in the processor 110. In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 can be arranged in the same device.

[0093] The modem processor can include a modulator and a demodulator. The modulator is configured to modulate a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is configured to demodulate a received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal processed by the baseband processor is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to the loudspeaker 170A and the microphone 170B, etc.) or displays an image or a video through the display screen 194. In some embodiments, the modem processor can be a separate device. In some other embodiments, the modem processor can be independent of the processor 110 and arranged in the same device as the mobile communication module 150 or other functional modules.

[0094] The wireless communication module 160 can provide a solution for wireless communication including wireless local area networks (WLAN) (e.g., wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) technology, etc. applied to the terminal 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency-modulates and filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 can also receive signals to be transmitted from the processor 110, frequency-modulate them, amplify them, and radiate them as electromagnetic waves via the antenna 2.

[0095] In some embodiments, antenna 1 and mobile communication module 150 of terminal 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, so that terminal 100 can communicate with a network and other devices through wireless communication technology. The wireless communication technology can include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS can include global positioning system (GPS), global navigation satellite system (GLONASS), beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite based augmentation systems (SBAS).

[0096] Terminal 100 implements a display function through a GPU, display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, connected to display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations, for graphics rendering. Processor 110 can include one or more GPUs that execute program instructions to generate or change display information.

[0097] The display screen 194 is configured to display images, videos, and the like. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flex light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-OLED, a quantum dot light emitting diodes (QLED), or the like. In some embodiments, the terminal 100 can include one or N display screens 194, where N is a positive integer greater than 1.

[0098] The terminal 100 can implement the photographing function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, and the application processor.

[0099] The ISP is configured to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, the light is transmitted to the camera photosensitive element through the lens, the light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing to convert it into an image visible to the naked eye. The ISP can also perform algorithm optimization on the noise, brightness, and color of the image. The ISP can also optimize the exposure, color temperature, and other parameters of the shooting scene. In some embodiments, the ISP can be arranged in the camera 193.

[0100] The camera 193 is configured to capture still images or videos. An object generates an optical image through a lens and projects it onto a photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then transmitted to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, the terminal 100 can include one or N cameras 193, where N is a positive integer greater than 1.

[0101] The digital signal processor is used to process digital signals, in addition to being able to process digital image signals, it can also process other digital signals. For example, when the terminal 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy, etc.

[0102] The video codec is used to compress or decompress digital video. The terminal 100 can support one or more video codecs. In this way, the terminal 100 can play or record videos in multiple encoding formats, such as: moving picture experts group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0103] The NPU is a neural-network (NN) calculation processor, which can quickly process input information by drawing on the structure of a biological neural network, such as drawing on the transmission mode between human brain neurons, and can also constantly self-learn. Through the NPU, intelligent cognitive applications of the terminal 100 can be realized, such as: image recognition, face recognition, voice recognition, text understanding, etc.

[0104] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal 100. The external memory card communicates with the processor 110 through the external memory interface 120 to realize data storage functions. For example, music, video, etc. Files are saved in the external memory card.

[0105] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the terminal 100 by running the instructions stored in the internal memory 121. The internal memory 121 can include a program storage area and a data storage area. The program storage area can store an operating system, at least one application required by a function (such as a face recognition function, a fingerprint recognition function, a mobile payment function, etc.), etc. The data storage area can store data created during the use of the terminal 100 (such as face information template data, fingerprint information template, etc.). In addition, the internal memory 121 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0106] The terminal 100 can realize audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor, etc. For example, music playing, recording, etc.

[0107] The audio module 170 is used to convert digital audio information into analog audio signals output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals.

[0108] The speaker 170A, also called "loudspeaker", is used to convert audio electrical signals into sound signals. The terminal 100 can listen to music or listen to a hands-free call through the speaker 170A.

[0109] The receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals. When the terminal 100 answers a call or a voice message, the receiver 170B can be held close to the human ear to listen to the voice.

[0110] The microphone 170C, also called "microphone", "sound transducer", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak into the microphone 170C through the human mouth to input sound signals into the microphone 170C. The terminal 100 can be provided with at least one microphone 170C.

[0111] The earphone interface 170D is used to connect a wired earphone. The earphone interface 170D can be a USB interface 130, or a 3.5mm open mobile terminal platform (OMTP) standard interface, a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0112] The pressure sensor 180A is used to sense pressure signals, and can convert pressure signals into electrical signals.

[0113] The gyroscope sensor 180B can be used to determine the motion posture of the terminal 100.

[0114] The barometric sensor 180C is used to measure air pressure.

[0115] The magnetic sensor 180D includes a Hall sensor. The terminal 100 can use the magnetic sensor 180D to detect the opening and closing of a flip leather cover.

[0116] The acceleration sensor 180E can detect the magnitude of acceleration of the terminal 100 in various directions (generally three axes). When the terminal 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the posture of the electronic device, applied to landscape / portrait screen switching, pedometer, etc.

[0117] The distance sensor 180F is used to measure distance.

[0118] The proximity light sensor 180G can include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode can be an infrared light emitting diode. The terminal 100 emits infrared light outwardly through the light emitting diode. The terminal 100 detects infrared reflected light from nearby objects using the photodiode.

[0119] The ambient light sensor 180L is used to sense ambient light brightness. The terminal 100 can adaptively adjust the display screen 194 brightness according to the sensed ambient light brightness.

[0120] The fingerprint sensor 180H is used to collect a fingerprint.

[0121] The temperature sensor 180J is used to detect temperature.

[0122] The touch sensor 180K, also referred to as a "touch panel". The touch sensor 180K can be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 together form a touch screen, also referred to as a "touch panel". The touch sensor 180K is used to detect a touch operation acting on or near the touch sensor 180K.

[0123] The keys 190 include a power on key, a volume key, and the like. The keys 190 can be mechanical keys. They can also be touch type keys. The terminal 100 can receive key input, and generate key signal input related to user settings and function control of the terminal 100.

[0124] The motor 191 can generate a vibration prompt.

[0125] The indicator 192 can be an indicator light, and can be used to indicate a charging state, a power change, and can also be used to indicate a message, a missed call, a notification, and the like.

[0126] The SIM card interface 195 is used to connect a SIM card. The SIM card interface 195 can also be compatible with an external storage card. The terminal 100 interacts with a network through the SIM card, and implements functions such as calling and data communication.

[0127] Next, an exemplary CPE 200 of the present application is introduced.

[0128] Figure 3 The structure schematic diagram of the exemplary CPE 200 is shown in FIG. 2, and the components of the CPE 200 are described as follows. Figure 3The CPE 200 comprises at least one processor 201, at least one transceiver 203, one or more antennas 205, and at least one SIM card interface 206. Optionally, the CPE 200 can further comprise at least one memory 202 and at least one network interface 204. The processor 201, the memory 202, the transceiver 203, and the network interface 204 are connected, for example, through a bus. The antenna 205 is connected to the transceiver 203. The network interface 204 is configured to enable the CPE to be connected to other communication devices through a communication link, for example, a terminal device can be connected through the network interface 204. In the embodiments of the present application, the connection can comprise various interfaces, transmission lines or buses, etc., and the embodiments are not limited in this regard. The SIM card interface 206 is configured to enable the CPE to communicate with a core network through a mobile network, and the specific description can refer to the description of the terminal side, which will not be repeated here.

[0129] The processor in the embodiments of the present application, for example, the processor 201, can comprise at least one of the following types: a general central processing unit (CPU), a digital signal processor (DSP), a microprocessor, an application-specific integrated circuit (ASIC), a microcontroller unit (MCU), a field programmable gate array (FPGA), or an integrated circuit for implementing logical operations. For example, the processor 201 can be a single-CPU processor or a multi-CPU processor. The at least one processor 201 can be integrated in one chip or located on multiple different chips.

[0130] The memory in the embodiments of the present application, for example, the memory 202, can include at least one of the following types: read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, and can also be an electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory can also be a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and capable of being accessed by a computer, but not limited thereto.

[0131] The memory 202 can exist independently and be connected with the processor 201. Alternatively, the memory 202 can also be integrated with the processor 201, for example, integrated in a chip. The memory 202 can store program codes for executing the technical solutions of the embodiments of the present application and be controlled to execute by the processor 201. The executed computer program codes can also be regarded as a driver of the processor 201. For example, the processor 201 is used to execute the computer program codes stored in the memory 202, so as to implement the technical solutions in the embodiments of the present application. Alternatively, the memory 202 can also be outside the chip and connected with the processor 201 through an interface.

[0132] The transceiver 203 can be configured to support the receiving or transmitting of radio frequency signals between the CPE and a terminal, and between the CPE and a core network device. The transceiver 203 can be connected to the antenna 205. The transceiver 203 includes a transmitter Tx and a receiver Rx. Specifically, the one or more antennas 205 can receive radio frequency signals, the receiver Rx of the transceiver 203 is configured to receive the radio frequency signals from the antenna and convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and provide the digital baseband signals or digital intermediate frequency signals to the processor 201 for further processing, such as demodulation processing and decoding processing, by the processor 201. In addition, the transmitter Tx in the transceiver 203 is also configured to receive modulated digital baseband signals or digital intermediate frequency signals from the processor 201, and convert the modulated digital baseband signals or digital intermediate frequency signals into radio frequency signals, and transmit the radio frequency signals through the one or more antennas 205. Specifically, the receiver Rx can selectively perform one or more levels of down-mixing processing and analog-to-digital conversion processing on the radio frequency signals to obtain digital baseband signals or digital intermediate frequency signals, and the order of the down-mixing processing and the analog-to-digital conversion processing can be adjustable. The transmitter Tx can selectively perform one or more levels of up-mixing processing and digital-to-analog conversion processing on the modulated digital baseband signals or digital intermediate frequency signals to obtain radio frequency signals, and the order of the up-mixing processing and the digital-to-analog conversion processing can be adjustable. The digital baseband signals and the digital intermediate frequency signals can be collectively referred to as digital signals.

[0133] The above communication system can be used to support the fifth generation (5G) access technology and future-oriented communication technology, such as new radio (NR) access technology. For example, the description of the embodiments of the present application is described by taking the standalone (SA) in 5G as an example. In fact, the technical solutions of the present application can also be applied to non-standalone (NSA) and other scenarios, which are not limited by the present application.

[0134] The 5G communication system introduces the concept of network slicing. Network slicing technology can divide a physical network into multiple virtual networks. Each virtual network is regarded as a "network slice", and each network slice is independent of each other. Different protocol data unit (PDU) sessions in a terminal can require a network slice corresponding to the PDU session to provide services.

[0135] In order for those skilled in the art to better understand the present application, the concept of network slicing and other possible background technologies related to the present application are briefly described as follows:

[0136] Network slice as a key technology of 5G has been widely valued and researched in 3GPP and other various international standardization organizations. It can meet the customized needs of operators for various industries, vertical markets and various virtual operation businesses. Network slice is a logical network that provides specific network capabilities and network characteristics. It can be a logical network with different network capabilities and network characteristics customized according to different service requirements or tenants on the basis of physical or virtual network infrastructure. Network slice is composed of a group of network functions and the resources (for example, computing resources, storage resources, network resources) required by the network functions.

[0137] In the embodiments of the present application, the network slice can be referred to as slice for short.

[0138] The network slice can be configured by an operation, administration and maintenance system (OAM). Single network slice selection assistance information (S-NSSAI) is used to identify a network slice.

[0139] The S-NSSAI includes at least one of the following: slice type, slice / service type (SST) information. Optionally, the S-NSSAI can also include slice differentiator (SD). The SST information is used to indicate the behavior of the network slice, for example, the characteristics of the network slice and the service type. The SD information is the complementary information of the SST, for example: if the SST points to multiple network slices, the SD can assist in corresponding to a unique network slice.

[0140] There are various types of services in a terminal, such as enhanced mobile broadband service (eMBB), ultra-reliable low latency communications (URLLC), massive machine type communication (mMTC), etc., and the network slices corresponding to the PDU sessions of different types of services can be different. Different applications in the terminal can correspond to different types of services, that is, the applications in the terminal can correspond to different network slices. It should be noted that even if the same type of service, due to the difference in the operator or service provider providing, it can also correspond to different network slices. That is, the network slice can provide network resources for at least one PDU session of the terminal.

[0141] In the existing standard, the core network sends a UE route selection policy (URSP) to the terminal to enable the terminal to determine the routing mode of data (which can be understood as the data of different types of services), and the URSP can be used to indicate the service characteristics and slice network activation parameters that need to be transmitted on the slice network, and the routing mode includes specific routing to which slice or using a non-slice network to transmit data.

[0142] For example, the URSP includes a URSP rule, a precedence value of the URSP rule, a traffic descriptor, a length of a route selection descriptor list, and a route selection descriptor. Figure 4 The format of the URSP shown in the example is as follows: the URSP includes, but is not limited to, a URSP rule length field, a precedence value of the URSP rule field, a traffic descriptor length field, a Traffic descriptor field, a route selection descriptor list length field, and a Route selection descriptor field.

[0143] The route selection descriptor list field is used to carry the slice network activation parameters, and the slice network activation parameters include, but are not limited to, one or more S-NSSAI parameters corresponding to the slice.

[0144] The traffic descriptor field is used to carry the information (or parameters) corresponding to the traffic characteristics that need to be transmitted on the slice as described above. The definitions of other fields can refer to the description in the 3GPP standard, which will not be described here.

[0145] The description of the traffic descriptor field in the 3GPP 24526 protocol is as follows:

[0146] Traffic descriptor component type identifier (traffic descriptor field type definition)

[0147] Bits (bit)

[0148]

[0149] Among them, OS Id+App Id constitutes the application descriptor (Application descriptors) information, which is used to identify the application in the operating system, and can also be understood as Application descriptors can be used to indicate which applications in the operating system can transmit data through the slice network. Among them, OS Id is used to identify the operating system, and App Id is used to identify the application in the operating system. For example, App Id can be the application package name of the application, that is, the UE downloads and installs the application from any platform or store, and the installation package of the application contains App Id. The UE can store the installation package name of the application after installing the application.

[0150] It should be noted that the above standard is applicable to the interaction between the terminal and the core network, that is, the terminal can match the URSP issued by the core network through the App Id and other parameters of the current application to route the data of the application to the specified slice. However, in the application scenario of CPE, since the existing CPE only has forwarding function and does not have corresponding slice and access CPE UE and UE traffic matching. Therefore, in this scenario, the CPE can only route the data of the application to the corresponding slice through the matching mode of the IP triple group (including IPv4 remote address type or IPv6 remote address / prefix length type, Protocol identifier / next header type, Single remote port type), DNN (that is, DNN type) and / or FQDN (that is, Destination FQDN type) in the URSP.

[0151] However, in some scenarios, the user can sign up for different data services on the LAN side, such as low-latency services, large-bandwidth services, targeted services, and the like. Different data services have different requirements for data transmission networks. However, the CPE can only route data sent by the UE to the corresponding slice according to the URSP. However, different UEs can sign up for different types of network services, and different types of network services correspond to different slices. Currently, the CPE cannot associate the service type of the UE with different slices. In this way, the CPE cannot meet the differentiated network requirements of the UE.

[0152] The following will be described in conjunction with Figure 2 the application scenarios shown in the existing standards, the interaction process of the terminal, the CPE and the core network is briefly described:

[0153] 1) CPE accesses the core network

[0154] In conjunction with Figure 2 , Figure 5 a flowchart of the CPE accessing the core network in the embodiment of the present application is shown, as Figure 5 shown, the CPE accessing the core network can include the following steps:

[0155] S101, the CPE sends a registration request Registration request message to the core network.

[0156] Specifically, the CPE will initiate a registration process in the case of booting, restarting or updating, for example, the CPE will initiate a registration process after booting, or the CPE will also initiate a registration process after refreshing. The registration process can be understood as the CPE registering into the network.

[0157] For example, referring to Figure 5 , the CPE sends a Registration request message to the core network to request to initiate a registration process. For example, the Registration request message can carry registration type, security parameters and the like, it should be noted that for the core network, the CPE is equivalent to a UE, so the specific process of initiating registration can refer to the UE registration process in the existing standards, and the present application will not be described again.

[0158] S102, the core network sends a registration acceptance Registration accept message to the CPE.

[0159] Specifically, after the core network agrees that the CPE registers into the network, the core network sends a Registration accept message to the CPE. The Registration accept message can carry one or more parameters for indicating that the CPE accesses the core network. For example, in the embodiment, the Registration accept message carries Allowed Network Slice Selection Assistance Information (Allowed NSSAI) for indicating one or more slices allowed to be accessed by the CPE.

[0160] S103, the CPE saves the Allowed NSSAI.

[0161] For example, the CPE can save the Allowed NSSAI to a storage unit, such as a memory of the CPE, for use in subsequent establishment of a PDU session.

[0162] S104, the core network sends a Manage UE policy command message to the CPE.

[0163] Specifically, the core network sends the Manage UE policy command message to the CPE, and the message includes but is not limited to the URSP. For example, as described above, the URSP can include a service feature (such as an IP triple, an App Id, etc.) and a slice network activation parameter.

[0164] S105, the CPE saves the URSP.

[0165] Specifically, after the CPE obtains the URSP transmitted from the core network, the CPE can decode the URSP to obtain and store parameters and information carried in each field of the URSP.

[0166] S106, the CPE sends a Manage UE policy complete message to the core network.

[0167] Specifically, after the CPE successfully saves each parameter included in the URSP, the CPE can send the Manage UE policy complete message to the core network to indicate that the CPE has successfully processed the URSP.

[0168] Exemplarily, if the CPE fails to successfully resolve the URSP or fails to successfully save the URSP due to other reasons, the CPE sends a Manage UE policy command reject message to the core network.

[0169] 2) UE accesses the CPE

[0170] Specifically, in the communication system of the embodiment of the present application, the UE accesses the core network through the CPE, Figure 6 Exemplarily, the specific process of connecting the UE to the CPE is shown. As shown in the figure, Figure 6 The UE accessing the CPE can include the following steps:

[0171] S201, the UE sends an Authentication Request message to the CPE.

[0172] S202, the CPE sends an Authentication Responce message to the UE.

[0173] S203, the UE sends an Association Request message to the CPE.

[0174] S204, the CPE sends an Association Responce message to the UE.

[0175] The CPE receives the Association Response sent by the UE, determines that the UE successfully accesses the CPE, or can be understood as successfully accessing the core network through the CPE.

[0176] The specific details and related descriptions of the above steps S201 to S204 can refer to the standard of 802.11 protocol, and the present application will not be repeated.

[0177] 3) UE, CPE and core network interact with data.

[0178] Specifically, after the UE accesses the CPE, the Wi-Fi channel between the UE and the CPE is established. The UE can send data to the CPE through the Wi-Fi channel between the UE and the CPE, and the CPE forwards the data to the core network through the mobile communication network between the CPE and the core network. In addition, the CPE can also receive data corresponding to the UE sent by the core network through the mobile communication network. Then, the CPE forwards the data to the UE through the Wi-Fi channel between the CPE and the UE. Thus, the data interaction between the UE and the core network can be realized.

[0179] Figure 7An exemplary flow diagram of the interaction between the UE, the CPE and the core network is shown in FIG. 1, which can include the following steps: Figure 7 An exemplary flow diagram of the interaction between the UE, the CPE and the core network is shown in FIG. 1, which can include the following steps:

[0180] S301, the UE sends a data packet 1 to the CPE.

[0181] The UE sends the data packet 1 to the CPE through a Wi-Fi channel between the UE and the CPE. The format of the data packet 1 can be as shown in FIG. 2 or FIG. 3. Figure 8A or Figure 8B

[0182] Referring to FIG. 2 and FIG. 3, the UE and the CPE can interact with each other at the network layer, and the data packet 1 can be an IP data packet. The data packet 1 can carry a data part and an IP header (i.e., the header in the figure). The IP header can include a fixed part (also referred to as a fixed field) and a variable part (also referred to as a variable field). The fixed field can include, but is not limited to, parameters such as a destination address and a source address. The variable field can include an optional field and a reserved field (also referred to as a padding field). Figure 8A The fields included in the fixed part are fixed and unchangeable, that is, each data packet sent by the UE to the CPE needs to carry the fields in the fixed part as shown in FIG. 4. The information carried in the fields can be the same or different. The fields included in the variable part and the lengths of the fields are variable, that is, the field names, positions and lengths included in the variable part can be the same or different for different UEs or in different application scenarios, which are not limited in the present application. It should be noted that Figure 8A the names and positions of the parameters in the format of the data packet 1 shown in FIG. 2 and FIG. 3 are only exemplary, which are not limited in the present application. Figure 8A

[0183] Referring to FIG. 2 and FIG. 3, the UE and the CPE can interact with each other at the network layer, and the data packet 1 can be an IP data packet. The data packet 1 can carry a data part and an IP header (i.e., the header in the figure). The IP header can include a fixed part (also referred to as a fixed field) and a variable part (also referred to as a variable field). The fixed field can include, but is not limited to, parameters such as a destination address and a source address. The variable field can include an optional field and a reserved field (also referred to as a padding field). Figure 8B The fixed part in the IP header can refer to the description in FIG. 5, which will not be described herein. The optional field part in the IP header of the data packet 1 can include an App Id of an application sending the data packet 1 in the UE. It should be noted that Figure 8A the position of the App Id field in the optional field as shown in FIG. 2 and FIG. 3 is only exemplary, and the length and position of the field can be set according to actual needs, which are not limited in the present application. Figure 8B S302, the CPE acquires an IP triple.

[0184]

[0185] ​​​For example, the URSP issued by the core network includes an IP triple. The CPE acquires the IP triple in response to the received data packet 1 sent by the UE.

[0186] Optionally, the URSP issued by the core network also includes an App Id. The CPE can also acquire the App Id of the application sending the data packet 1 in the UE from the data packet 1.

[0187] S303, the CPE checks the IP triple.

[0188] For example, the CPE matches the acquired IP triple with the IP triple indicated by the URSP stored in S105. If the IP triple is matched successfully, that is, each parameter in the IP triple exists in the URSP issued by the core network. The CPE determines that the IP triple check is successful, and the data packet corresponding to the IP triple can be routed to the slice network.

[0189] For example, if the IP triple check fails, that is, any parameter in the IP triple does not exist in the URSP, the CPE determines that the check fails, and the data packet will be routed to the default slice, which is usually a low-priority slice, or to the non-slice network.

[0190] Optionally, the CPE can also match the App Id of the application sending the data packet 1 in the UE acquired from the data packet 1 with the App Id in the URSP. If the App Id is matched successfully, that is, the App Id of the application sending the data packet 1 exists in the URSP issued by the core network. The CPE determines that the App Id check is successful, and the data packet 1 corresponding to the App Id can be routed to the slice corresponding to the App Id in the URSP.

[0191] Optionally, the CPE can also match the App Id of the application sending the data packet 1 in the UE acquired from the data packet 1, and the IP triple, with the App Id and the IP triple in the URSP.

[0192] S304a, the CPE routes the data packet 1 to the specified slice.

[0193] For example, after the CPE successfully verifies the IP triple, it can further acquire other related information of the slice, such as the NSSAI of the slice, based on other information in the URSP, such as the slice network activation parameters described above.

[0194] For example, the CPE can match the NSSAI of the slice with the Allowed NSSAI stored in S103 to determine whether the core network allows the data of the UE to be routed to the slice.

[0195] The CPE binds the IP triple in the data packet 1 to the PDU session corresponding to the slice, so that the data packets containing the IP triple subsequently received can be routed to the corresponding slice through the bound PDU session. Illustratively, the binding can mean that the CPE records the IP triple and the related information (such as a service interface or a routing table entry) of the PDU session in the memory, so that after the CPE detects the data (i.e. the data packet containing the IP triple) corresponding to the IP triple, the CPE determines the PDU session bound to the IP triple and routes the data to the slice corresponding to the PDU session.

[0196] Here, the CPE can have bound the IP triple in the data packet 1 to the PDU session corresponding to the slice before step S304a.

[0197] Optionally, after the CPE verifies the App Id successfully, the CPE can further obtain other related information of the slice based on other information in the URSP, such as the slice network activation parameter described above, for example, the NSSAI of the slice.

[0198] In one example, if the CPE detects that the PDU session corresponding to the slice is not established, the CPE needs to trigger a PDU session establishment process. Still referring to Figure 7 The method further includes:

[0199] S304b, the CPE sends a PDU session establishment request message to the core network.

[0200] Illustratively, the CPE initiates a PDU session establishment process to establish the PDU session corresponding to the slice. Illustratively, the PDU session establishment request message carries the NSSAI of the slice corresponding to the IP triple or the App Id.

[0201] S304c, the core network sends a PDU session establishment success message to the CPE.

[0202] Illustratively, the core network establishes the PDU session of the slice corresponding to the NSSAI based on the received PDU session establishment request message, and returns the PDU session establishment success message to the CPE after the PDU session is established successfully.

[0203] It should be noted that the specific details of the PDU session establishment process can refer to the PDU session establishment process specified in the existing standard, and will not be described herein.

[0204] Specifically, after receiving the PDU session establishment success message, the CPE confirms that the PDU session has been established successfully and binds the data stream corresponding to the IP triplet to the PDU session.

[0205] In another example, if the CPE detects that the PDU session for the slice corresponding to the IP triplet or App ID has been established, the CPE directly binds the IP triplet, App ID and PDU session without executing the PDU session establishment process.

[0206] Optionally, after receiving data packet 1, the core network can reply with data packet 2 to the UE via the CPE. For details, please refer to... Figure 7 After the core network receives data packet 1, the interaction between the UE, CPE, and core network also includes the following steps:

[0207] S305, the core network sends data packet 2 to the CPE.

[0208] For example, after receiving packet 1, the core network can generate packet 2 based on packet 1 and then send packet 2 to the CPE.

[0209] Optionally, the core network can receive data packets sent by another UE or server. The core network parses the data packet, encapsulates it into data packet 2, and then sends it to the CPE.

[0210] It is understood that the embodiments of this application do not limit how the core network generates or obtains data packet 2.

[0211] S306, CPE sends data packet 2 to UE.

[0212] For example, after receiving data packet 2 from the core network, the CPE can parse data packet 2 to determine the destination receiving device, such as the UE. The CPE can then send data packet 2 to the destination receiving device, i.e., the UE.

[0213] For information on the downlink data transmission process between the UE, CPE, and core network, please refer to the descriptions in existing standards; they will not be repeated here.

[0214] Figure 7The process shown in the middle is based on the traffic characteristics (which can include but are not limited to one or more of App Id, IP triple, DNN, FQDN) indicated by the URSP issued by the core network. If the verification is successful, the CPE is allowed to route the data to the slice network. In some scenarios, users can open different network services to experience differentiated network services. However, the CPE cannot associate the services opened by the user with the slice, and can only determine the slice matched by the data sent by the user terminal through the URSP. The slice determined according to the URSP may not be consistent with the slice corresponding to the service opened by the user, so that the user cannot be provided with differentiated network services. For example, if the terminal of user A opens a low-latency network service, the low-latency network service corresponds to a low-latency slice. When the terminal of user A sends data to the core network through the CPE, the CPE should route the data to the low-latency slice. However, if the CPE only determines that the slice corresponding to the data sent by the terminal of user A is a general slice according to the URSP. Then user A cannot experience low-latency network services.

[0215] The embodiment of the present application provides a slice selection method, and the CPE can associate the network service of the UE with the slice. The CPE can route the data sent by the UE to the slice associated with the network service of the UE based on the network service of the UE. In this way, the CPE can provide differentiated network services for different UEs.

[0216] In the slice selection method provided in the embodiment of the present application, the UE can subscribe to a network service in the CPE. Different network services can be associated with different slices. The CPE can route the data sent by the UE to the slice corresponding to the service subscribed by the UE based on the service subscribed by the UE. In this way, the UE can experience differentiated network services.

[0217] Figure 9 An exemplary slice selection method provided by the embodiment of the present application is shown. As shown in Figure 9 The slice selection method provided by the embodiment of the present application can include the following steps:

[0218] S401, the CPE 200 accesses the core network 300.

[0219] In some examples, the CPE 200 accessing the core network 300 can include the following steps:

[0220] 1, the modem module 2003 in the CPE 200 initiates registration to the core network 300.

[0221] Here, reference can be made to the description in step S101, which will not be repeated here.

[0222] 2. The core network 300 can send the URSP and the subscription information of the CPE 200 to the CPE 200.

[0223] For example, the core network 300 can send the URSP and the subscription information of the CPE 200 to the modem module 2003 of the CPE 200. The CPE 200 can subscribe to one or more network services provided by the operator. For example, the operator can provide network services including one or more of the following: a large bandwidth high priority service, a large bandwidth medium priority service, a large bandwidth low priority service, a targeted service, a low latency service, and the like.

[0224] It can be understood that the classification of network services provided by different operators can be different, and the types and names of network services can also be different. Embodiments of the present application do not limit the types and names of network services to which the CPE 200 can subscribe.

[0225] In embodiments of the present application, a targeted service can be a network service provided by an operator for a specific service of a company. The operator can provide one or more targeted slices to provide network services only for the specific service, that is, only data sent by the UE 100 for the specific service can be routed to the slice provided by the operator for the specific service, and data for other services cannot be routed to the slice provided by the operator for the specific service. For example, a network service provided by an operator for a specific game can be referred to as a targeted service. A network service provided by an operator for coal mine operations can also be referred to as a targeted service. A network service provided by an operator for a power grid company can also be referred to as a targeted service. It can be understood that embodiments of the present application do not limit the specific targeted service.

[0226] In embodiments of the present application, one network service can correspond to one slice. Different network services correspond to different slices. The CPE 200 can subscribe to one or more network services provided by the operator, which can mean that the CPE 200 has the permission to use one or more slices provided by the operator. In embodiments of the present application, the CPE 200 having the permission to use the first slice can mean that the CPE 200 can route data to the first slice and can transmit data to the core network through the first slice.

[0227] The CPE 200 can parse the URSP sent by the core network, and the CPE 200 can parse the slice information. The slice information can indicate the slices that can be used in the CPE 200 and the slices that can be provided to the UE 100.

[0228] For example, referring to Figure 10 , the CPE 200 can parse the URSP, which can specifically include the following steps:

[0229] S4011, the CPE 200 traverses the terminal routing selection policy URSP list according to the priority.

[0230] For example, the CPE 200 can traverse the URSP list according to the priority. There can be multiple URSP rules in the URSP list. Optionally, the URSP rule at the front of the URSP list has a higher priority than the URSP rule at the back of the URSP list.

[0231] S4012, the CPE 200 determines whether there is a URSP of the next priority in the URSP list. If yes, step S4013 is performed, and if no, step S4011 is performed.

[0232] It can be understood that the CPE 200 can first match the URSP of the highest priority in the URSP list. If the URSP of the highest priority is matched successfully, step S4012 is not performed. If the URSP of the highest priority is not matched successfully, the URSP of the next priority is matched.

[0233] S4013, the CPE 200 performs traffic descriptor matching.

[0234] The CPE 200 determines whether the service indicated by the traffic descriptor of the URSP rule includes the service of the CPE 200 or is the same as the service of the CPE 200.

[0235] S4014, the CPE 200 determines whether the traffic descriptor is matched successfully. If yes, step S4015 is performed, and if no, step S4012 is performed.

[0236] If the CPE 200 determines that the service indicated by the traffic descriptor includes the service of the CPE 200 or is the same as the service of the CPE 200, the CPE 200 determines whether the traffic descriptor is matched successfully. Then, the CPE 200 performs step S4015. Otherwise, the CPE 200 continues to perform S4012 to query the next URSP rule.

[0237] S4015, the CPE 200 traverses the route selection descriptor list.

[0238] The CPE 200 traverses each S-NSSAI in the route selection descriptor list.

[0239] S4016, the CPE 200 determines whether the S-NSSAI is contained in the allowed NSSAI, if yes, it performs step S4017, if no, it performs step S4012.

[0240] The CPE 200 determines whether each S-NSSAI in the Route selection descriptor list is contained in the allowed NSSAI. If yes, it performs step S4017. If no, it performs step S4012, i.e. traverses the next URSP rule.

[0241] S4017, the CPE 200 selects the S-NSSAI as the PDU session activation parameter.

[0242] S4018, the CPE 200 determines that the DNN & NSSAI has been activated successfully, if yes, it performs step S4019, if no, it performs step S40110.

[0243] S4019, the CPE 200 determines that there is no need to activate the PDU session again.

[0244] S40110, the CPE 200 activates the PDU session with the S-NSSAI.

[0245] S40111, the CPE 200 determines that the slice selection fails.

[0246] If the CPE 200 does not traverse the URSP of the next highest priority, the CPE 200 determines that the slice selection fails.

[0247] It can be understood that the specific process of the CPE 200 analyzing the URSP can refer to the description in the existing standard, which will not be repeated here.

[0248] 3, the modem 203 in the CPE 200 can report the slice information to the slice application module in the CPE 200.

[0249] 4, the slice application module in the CPE 200 records the slice information.

[0250] 5, the slice application module in the CPE 200 initiates dialing.

[0251] 6, the modem 203 in the CPE 200 establishes the PDU session of multiple slices based on the dialing initiated by the slice application module.

[0252] Here, the specific process of the CPE 200 dialing and establishing the PDU session of the slice can refer to the existing standard, which will not be repeated here.

[0253] S402, the UE 100 accesses the CPE 200.

[0254] The specific process of the UE 100 accessing the CPE 200 can refer to the description in S201-S204, which will not be repeated here.

[0255] In the embodiment of the present application, before or after the UE 100 performs step S402, the UE 100 can perform identity authentication and subscribe to network services. The CPE 200 can obtain the identity information of the UE 100 and the network service information subscribed by the UE 100 through the identity authentication of the UE 100.

[0256] Optionally, the UE 100 can perform identity authentication and subscribe to network services through Portal (portal or entry web page) authentication.

[0257] For example, the user can turn on the Wi-Fi in the UE 100, and when connecting the CPE 200, the UE 100 can display a webpage for identity authentication, and the user can input the username and password in the webpage to perform identity authentication. After the UE 100 performs identity authentication, the CPE 200 can obtain the MAC address of the UE 100.

[0258] Further, the UE 100 can subscribe to one or more network services that the CPE can provide. For example, Figure 11 The scenario of the terminal subscribing to the network services provided by the CPE is shown. As Figure 11 shown, the terminal 1 can subscribe to the large bandwidth high priority service provided by the CPE. The terminal 2 can subscribe to the large bandwidth medium priority service provided by the CPE. The terminal 3 can subscribe to the large bandwidth low priority service provided by the CPE. The terminal 4 can subscribe to the low latency service provided by the CPE. The terminal 5 can subscribe to the multi-slice service (i.e. multiple services among the large bandwidth high priority service, the large bandwidth medium priority service, the large bandwidth low priority service, the low latency service, the directional service, etc.) provided by the CPE. The terminal 6 can subscribe to the directional service provided by the CPE.

[0259] The CPE 200 can preconfigure the names of the slices that the CPE can provide, and the CPE can associate (or bind) the names of the slices with the slice IDs. The subscription of the network service by the UE can mean that after the UE selects the name of one or more slices that the CPE can provide in the CPE, the CPE associates the identity of the UE with the slice corresponding to the name of the slice selected by the UE. In this way, the UE has the right to use the slice.

[0260] In the embodiment of the present application, the right of the UE to use the slice can mean that the data sent by the UE can be transmitted to the core network (or referred to as the network side) through the slice.

[0261] Optionally, there can be an administrator user in the CPE, and a terminal connected to the CPE through a USB or a network port can be referred to as the administrator user. Embodiments of the present application do not limit the administrator user. For example, the administrator user can configure the name of the slice that the CPE 200 can provide. In addition, the administrator user can subscribe the network service that the CPE 200 can provide for other UEs.

[0262] It can be understood that the SIM card in the CPE 200 can subscribe one or more network services at the operator. The network service that the CPE 200 can provide for the UE 100 is the network service that the SIM card in the CPE 200 has subscribed at the operator. For example, if the SIM card in the CPE 200 subscribes a low-latency service at the operator, the CPE 200 can provide the low-latency service for the UE 100. Only when the SIM card in the CPE 200 subscribes multiple network services at the operator, the UE 100 can subscribe a multi-slice service.

[0263] Further, optionally, the UE 100 can subscribe the network service that the CPE 200 can provide by logging in a webpage. Alternatively, the UE 100 can subscribe the network service that the CPE 200 can provide through the administrator user. Embodiments of the present application do not limit the manner in which the UE 100 subscribes the network service.

[0264] For example, Figure 12 A user interface diagram for subscribing a network service is shown. As shown in Figure 12 The user interface 1200 can be used to select the network service that the UE 100 subscribes and to subscribe the network service. The user interface 1200 can include a control 1201, a control 1202, an option box 1203, an input box 1204, a control 1205, and a control 1206. After the user clicks the control 1201 and the control 1202, the option box 1203 can be displayed in the user interface 1200. The user can select the network service in the option box and input the user name (for example, the mobile phone number 131********) in the input box 1204. After the user clicks the control 1205, the UE with the mobile phone number 131******** can successfully subscribe the network service selected by the user in the option box 1203. Optionally, the user can click the control 1206 to view the cost explanation of different network services or the cost explanation of the network service selected by the user.

[0265] It can be understood that the UE 100 can display the user interface 1200, and the user can subscribe the network service for the UE 100 in the user interface 1200.

[0266] Optionally, the user interface 1200 can also be displayed in the UE of the administrator user of the CPE 200. The administrator user can sign up the different UEs to the network service in the user interface 1200.

[0267] Further, after the UE signs up the network service provided by the CPE 200, the CPE 200 can associate (or bind) the UE with the slice corresponding to the network service signed up by the UE.

[0268] Optionally, the CPE 200 can record the identifier of the UE and the slice associated therewith or the ID of the slice in the database. The identifier of the UE can be the MAC address of the UE or the mobile phone number of the UE, which is not limited herein.

[0269] For example, when the UE 100 performs the portal authentication, the CPE 200 can save the username of the UE 100 and can obtain the MAC address of the UE 100. The CPE 200 can save the username and the MAC address of the UE 100 into the portal information database.

[0270] For example, after the UE 100 signs up one or more network services that can be provided by the CPE 200, the CPE 200 can associate the username of the UE 100 and the slice ID corresponding to the network service signed up by the UE 100, and save the same into the user database. The CPE 200 can update the username and the MAC address of the UE 100 saved in the portal information database into the user database. The CPE 200 can associate the username and the MAC address of the UE 100 with the slice ID corresponding to the network service signed up by the UE 100, and save the same into the user database.

[0271] It can be understood that different UEs can sign up the same network service. One slice ID in the CPE 200 can be associated with the usernames of multiple UEs.

[0272] For example, in a possible implementation, after the CPE associates the username of the UE 100 and the slice ID corresponding to the network service signed up by the UE 100, the CPE 200 can generate the routing rule of the UE 100. The routing rule is used to indicate the CPE 200 to transmit the data of the UE 100 to the core network through the slice corresponding to the network service signed up by the UE 100 based on which PDU session.

[0273] S403, the UE 100 sends a data packet R1 to the CPE 200.

[0274] The UE 100 can send a data packet R1 to the CPE 200. The data packet R1 can be a service request. The data packet R1 can carry an IP triple, and the format of the data packet can be as shown in Figure 8A Alternatively, the data packet can also carry an App Id, and the format of the data packet can be as shown in Figure 8B Alternatively, the data packet R1 can also carry a mobile phone number of the UE 100. The specific format of the data packet is not limited herein.

[0275] In an example, the UE 100 sends the data packet R1 to the CPE 200, including: S403a, the UE 100 sends the data packet R1 to the Wi-Fi module 2001 of the CPE 200; and S403b, the Wi-Fi module of the CPE 200 sends the data packet R1 to the routing module 2002 of the CPE 200.

[0276] S404, the CPE 200 determines a network service type A1 corresponding to the data packet R1.

[0277] The CPE 200 can determine the network service type A1 corresponding to the data packet R1. Specifically, the CPE 200 can first determine a network service to which the UE 100 sending the data packet R1 is subscribed. If the network service to which the UE 100 is subscribed contains only one network service and is not a targeted service, the CPE 200 can determine that the network service type A1 corresponding to the data packet R1 is the network service to which the UE 200 is subscribed.

[0278] Alternatively, in an example, if the network service type to which the UE 100 is subscribed is a targeted service, the CPE 200 needs to match the service characteristics (e.g., the IP triple, or the IP triple and the App Id, etc.) carried in the data packet R1 with the service characteristics corresponding to the targeted service slice in the URSP. If the matching is successful, the CPE 200 determines that the network service type A1 corresponding to the data packet R1 is a targeted service. If the matching is not successful, the CPE 200 determines that the network service A1 corresponding to the data packet R1 is a common service, i.e., the CPE 200 can route the data packet R1 to a default slice.

[0279] Optionally, in one possible implementation, if the network service type subscribed to by the UE100 is a multi-slice service (i.e., containing multiple network services), then the CPE200 needs to match the service characteristics carried in data packet R1 with the service characteristics corresponding to the slices associated with the multiple network services in the URSP. If the service characteristics carried in data packet R1 successfully match the service characteristics corresponding to the slice associated with network service A2 in the URSP, then the CPE200 determines that the network service type A1 corresponding to data packet R1 is network service A2. If the match fails, then the CPE200 determines that the network service A1 corresponding to data packet R1 is a normal service, that is, the CPE200 can route data packet R1 to the default slice. Optionally, in one possible implementation, if the match fails, the CPE200 can route data packet R1 to a high-bandwidth, high-priority service slice. This can improve the user experience.

[0280] Optionally, in one possible implementation, the CPE200 determining the network service type A1 corresponding to the data packet R1 may include: the CPE200 determining the network service subscribed by the UE100 that sent the data packet R1, and determining the network service type A1 corresponding to the data packet R1 based on the network service subscribed by the UE.

[0281] For example, such as Figure 13 As shown, taking the example of a CPE200 that has signed a contract with an operator for five network service types—high-bandwidth high-priority service, high-bandwidth medium-priority service, high-bandwidth low-priority service, low-latency service, and targeted service—the CPE200 determines that the network service type A1 corresponding to the data packet R1 to be sent may include:

[0282] S4041, CPE200 determines the network service type subscribed by UE100 that sent data packet R1.

[0283] The network service types that UE100 can subscribe to can be one or more of the following: high-bandwidth high-priority service, high-bandwidth medium-priority service, high-bandwidth low-priority service, low-latency service, and targeted service.

[0284] When the network service type subscribed to by UE100 can be any one or more of the following: high-bandwidth high-priority service, high-bandwidth medium-priority service, high-bandwidth low-priority service, low-latency service, and targeted service, the network service type A1 corresponding to data packet R1 is determined based on the network service subscribed to by the UE, including the following cases:

[0285] Scenario 1: UE100 only subscribes to high-bandwidth, high-priority services

[0286] S4042a, the CPE 200 determines that the UE 100 sending the data packet R1 is subscribed to the large bandwidth high priority service.

[0287] Exemplarily, the CPE 200 can determine that the UE 100 is subscribed to the large bandwidth high priority service based on the MAC address of the UE 100 or the mobile phone number of the UE 100 carried in the data packet R1.

[0288] S4044a, the CPE 200 determines that the network service type A1 is the large bandwidth high priority service.

[0289] Then, the CPE 200 can determine that the network service type A1 is the large bandwidth high priority service.

[0290] Case 2: the UE 100 is only subscribed to the large bandwidth medium priority service

[0291] S4042b, the CPE 200 determines that the UE 100 sending the data packet R1 is subscribed to the large bandwidth medium priority service.

[0292] Exemplarily, the CPE 200 can determine that the UE 100 is subscribed to the large bandwidth medium priority service based on the MAC address of the UE 100 or the mobile phone number of the UE 100 carried in the data packet R1.

[0293] S4044b, the CPE 200 determines that the network service type A1 is the large bandwidth high priority service.

[0294] Case 3: the UE 100 is only subscribed to the large bandwidth low priority service

[0295] S4042c, the CPE 200 determines that the UE 100 sending the data packet R1 is subscribed to the large bandwidth low priority service.

[0296] Exemplarily, the CPE 200 can determine that the UE 100 is subscribed to the large bandwidth low priority service based on the MAC address of the UE 100 or the mobile phone number of the UE 100 carried in the data packet R1.

[0297] S4044c, the CPE 200 determines that the network service type A1 is the large bandwidth low priority service.

[0298] Case 4: the UE 100 is only subscribed to the directed service

[0299] S4042d, the CPE 200 determines that the UE 100 sending the data packet R1 is subscribed to the directed service.

[0300] Exemplarily, the CPE 200 can determine that the UE 100 is subscribed to the directed service based on the MAC address of the UE 100 or the mobile phone number of the UE 100 carried in the data packet R1.

[0301] S4043d, the CPE 200 matches the service feature in the data packet R1 with the feature of the targeted service in the URSP.

[0302] S4044d, the CPE 200 determines that the network service type A1 is the targeted service.

[0303] It can be understood that the UE 100 is subscribed to the targeted service, and only the specific application in the UE 100 corresponds to the targeted service, and other applications are not the targeted service. Therefore, the CPE 200 needs to match the service feature in the data packet R1 with the feature of the targeted service in the URSP to determine whether the data packet R1 is sent by the specific application corresponding to the targeted service in the UE 100. If the matching is successful, the CPE 200 determines that the network service type A1 is the targeted service. If the matching is not successful, the CPE 200 determines that the network service type A1 is not the targeted service.

[0304] Case 5: The UE 100 is only subscribed to the low-latency service

[0305] S4042e, the CPE 200 determines that the UE 100 sending the data packet R1 is subscribed to the low-latency service.

[0306] Exemplarily, the CPE 200 can determine that the UE 100 is subscribed to the large-bandwidth low-priority service based on the MAC address of the UE 100 or the mobile phone number of the UE 100 carried in the data packet R1.

[0307] S4044e, the CPE 200 determines that the network service type A1 is the low-latency service.

[0308] Case 6: The UE 100 is subscribed to the multi-slice service

[0309] S4042f, the CPE 200 determines that the UE 100 sending the data packet R1 is subscribed to the multi-slice service.

[0310] Exemplarily, the CPE 200 can determine that the UE 100 is subscribed to the multi-slice service based on the MAC address of the UE 100 or the mobile phone number of the UE 100 carried in the data packet R1. That is, the UE 100 is subscribed to multiple network services in the large-bandwidth high-priority service, the low-latency service, and the targeted service.

[0311] S4043f, the CPE 200 determines the network service type A1 corresponding to the data packet R1 based on the service feature in the data packet R1 and the URSP.

[0312] The CPE 200 can match the service feature in the data packet R1 with the service feature corresponding to each network service in the multi-slice service in the URSP respectively. If the service feature in the data packet R1 matches the service feature of the low-latency service in the multi-slice service successfully, the CPE 200 can determine that the network service type A1 of the data packet R1 is the low-latency service. If the service feature in the data packet R1 matches the service feature of the directional service in the multi-slice service successfully, the CPE 200 can determine that the network service type A1 of the data packet R1 is the directional service. If the service feature in the data packet R1 matches the service feature of the large-bandwidth high-priority service in the multi-slice service successfully, the CPE 200 can determine that the network service type A1 of the data packet R1 is the large-bandwidth high-priority service.

[0313] In a possible implementation, if the service feature of the data packet R1 does not match the service feature of the directional service, the service feature of the low-latency service, and the service feature of the large-bandwidth high-priority service, the CPE 200 determines that the network service A1 corresponding to the data packet R1 is the ordinary service, that is, the CPE 200 can route the data packet R1 to the default slice.

[0314] Optionally, in a possible implementation, if the service feature of the data packet R1 does not match the service feature of the directional service, the service feature of the low-latency service, and the service feature of the large-bandwidth high-priority service, the CPE 200 can also determine that the network service A1 corresponding to the data packet R1 is the large-bandwidth high-priority service, that is, the CPE 200 can route the data packet R1 to the large-bandwidth high-priority service slice. In this way, the user experience can be improved.

[0315] It can be understood that the data transmission rate of the default slice is lower than the data transmission rate of the directional slice, the low-latency service slice, the large-bandwidth high-priority service slice, the large-bandwidth medium-priority service slice, the large-bandwidth low-priority service slice, and the like. The data transmission rate of the large-bandwidth high-priority service slice is higher than the data transmission rate of the large-bandwidth medium-priority service slice. The data transmission rate of the large-bandwidth medium-priority service slice is higher than the data transmission rate of the large-bandwidth low-priority service slice. S405, the CPE 200 routes the data packet R1 to the slice S1 corresponding to the network service type A1.

[0316] The CPE 200 can route the data packet R1 to the slice S1 corresponding to the network service type A1.

[0317] Exemplarily, referring to Figure 13Case 1: S4045a, in a case that the network service type A1 is a large bandwidth high priority service, the CPE 200 can route the data packet R1 to a large bandwidth high priority service slice. Case 2: S4045b, in a case that the network service type A1 is a large bandwidth medium priority service, the CPE 200 can route the data packet R1 to a large bandwidth medium priority service slice. Case 3: S4045c, in a case that the network service type A1 is a large bandwidth low priority service, the CPE 200 can route the data packet R1 to a large bandwidth low priority service slice. Case 4: S4045d, in a case that the network service type A1 is a low latency service, the CPE 200 can route the data packet R1 to a directed service slice. Case 5: S4045e, in a case that the network service type A1 is a directed service, the CPE 200 can route the data packet R1 to a low latency service slice.

[0318] Optionally, when the CPE 200 parses the App Id carried in the data packet R1, the CPE 200 can re-encapsulate the data packet R1, and the re-encapsulated data packet R1 does not include the App Id to avoid the core network side from being unable to identify the App Id in the optional field, resulting in compatibility problems.

[0319] It can be understood that, in a possible implementation, when the CPE 200 determines that the UE 100 does not subscribe to the network service provided by the CPE 200, the CPE 200 can route the data packet R1 to a default slice.

[0320] Optionally, in a possible implementation, when the CPE 200 determines that the UE 100 does not subscribe to the network service provided by the CPE 200, the CPE 200 can not send the data packet R1 to the core network 300. That is, the CPE 200 does not provide network services for the UE 100.

[0321] Optionally, the core network 300 can also send a service response R2 based on the data packet R1. That is, optionally, the slice selection method provided by the embodiment of the application can further include steps S406-S408a and S408b.

[0322] S406, the core network 300 sends a data packet R2 to the CPE 200.

[0323] The core network 300 can send a data packet R2 to the UE 100 through the CPE 200 based on the data packet R1 sent by the UE 100.

[0324] S407, the CPE 200 determines whether the data packet R2 corresponds to a low latency service slice. If yes, step S408b is performed, and if not, step S408a is performed.

[0325] CPE 200 can determine whether data packet R2 corresponds to the low latency slice. When CPE 200 determines that data packet R1 corresponds to the low latency slice, CPE 200 can add the service characteristics (e.g., IP triplets, or IP triplets and App Id) of data packet R1 to the feature table. When the service characteristics of service response R2 match the service characteristics in the feature table, CPE 200 can determine that the service response corresponds to the low latency slice. Otherwise, data packet R2 does not correspond to the low latency slice.

[0326] It can be understood that, generally, data (e.g., data packet R1) sent by UE 100 in uplink is routed to the low latency slice, and data (e.g., data packet R2) received in downlink.

[0327] S408a, if data packet R2 does not correspond to the low latency slice, sending data packet R2 to UE 100.

[0328] S408b, if data packet R2 corresponds to the low latency slice, sending data packet R2 to UE 100 at a speed-up.

[0329] If data packet R2 corresponds to the low latency slice, CPE 200 can speed up the Wi-Fi link through which data packet R2 is transmitted in downlink. For example, if data packet R2 is sent to CPE 200 through the low latency slice, CPE 200 can determine that data packet R2 corresponds to the low latency slice. Then, CPE 200 can speed up the Wi-Fi link through which data packet R2 is transmitted by using the higame module in CPE 200.

[0330] In this way, CPE can associate the network service subscribed by UE with the slice. Then, CPE 200 can route data sent by UE subscribed to different types of network services to different slices. For example, if UE1 subscribes to the low latency slice, and if UE2 subscribes to the large bandwidth high priority slice, CPE 200 can route data sent by application A in UE1 to the low latency slice, and CPE 200 can route data sent by application A in UE2 to the large bandwidth high priority slice. In this way, CPE 200 can provide differentiated network services to users.

[0331] In some scenarios, the administrator user can also set a virtual Wi-Fi access point in the CPE 200 and set a password of the virtual Wi-Fi access point. The administrator user can also associate the information (for example, the name and password of the virtual Wi-Fi access point) of the virtual Wi-Fi access point with a slice. The data sent by the UE connected to the virtual Wi-Fi access point can be routed to the same slice (that is, the slice associated with the information of the virtual Wi-Fi access point). In this way, it can be avoided that each user needs to perform separate operations to bind a slice or pay for access, and the user experience can be improved.

[0332] For example, taking outdoor CPE multi-player game as an example. The administrator user can set a virtual Wi-Fi access point of the CPE 200. For example, the virtual Wi-Fi access point is xx game slice Wi-Fi, and a Wi-Fi password is set. The administrator user can also associate the xx game slice Wi-Fi with the xx game slice. It can be understood that the CPE subscribes to many slices, including the xx game slice. The UE connected to the xx game slice Wi-Fi can perform xx game slice service. Optionally, the CPE can associate and store the MAC address of the UE connected to the xx game slice Wi-Fi and the xx game slice into a database.

[0333] In this way, for multi-player game, group outdoor game, and the like, the user authentication process is reduced.

[0334] In the above scenario in which the CPE 200 is provided with a virtual Wi-Fi access point, the slice selection method provided by the embodiment of the present application can include:

[0335] 1. The CPE 200 accesses the core network. The CPE 200 is provided with a virtual Wi-Fi access point, and the access information of the virtual Wi-Fi access point is associated with a slice S2.

[0336] Here, the process that the CPE 200 accesses the core network can refer to the description in the above step S401, and will not be described here again.

[0337] The CPE 200 is provided with a virtual Wi-Fi access point, and the access information of the virtual Wi-Fi access point is associated with a slice S2.

[0338] 2. The UE 100 accesses the CPE 200.

[0339] Here, the description in the above step S402 can be referred to, and will not be described here again.

[0340] 3. The UE 100 sends a data packet R1 to the CPE 200.

[0341] Here, reference can be made to the description in step S403 above.

[0342] 4, the CPE 200 determines whether the UE 100 accesses the virtual Wi-Fi access point, if yes, the data packet R1 is routed to the slice S2 associated with the virtual Wi-Fi access point; if not, the CPE 200 can perform steps S404-S405 described above.

[0343] In the embodiments of the present application, the CPE 200 or CPE can be referred to as a first terminal. The UE, or UE 100, UE1, UE2 can be referred to as a second terminal. The data packet R1 can be referred to as a first data packet, and the data packet R2 can be referred to as a second data packet. The network in which the slice S1 is located can be referred to as a first slice network.

[0344] The embodiments can divide the CPE 200 into functional modules according to the above method examples, for example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The integrated module can be implemented in the form of hardware. It should be noted that the division of the modules in the embodiments is illustrative, and is only a logical functional division. When actually implemented, another division manner can be used.

[0345] Figure 14 A structural schematic diagram of an apparatus 1400 is shown. The apparatus 1400 can include a Wi-Fi module 2001, a routing module 2002, a modem module 2003, a slice application module 2004, and a UI module 2005. Wherein:

[0346] The Wi-Fi module 2001 can be used to obtain and save the MAC address of the UE accessed through the Wi-Fi into the database, and the Wi-Fi module 2001 can also send the saved MAC address of the accessed UE to the routing module 2002.

[0347] Optionally, the Wi-Fi module 2001 can also be used to accelerate the downlink low-latency service.

[0348] Optionally, referring to Figure 11 , the Wi-Fi module 2001 can further include a Wi-Fi card routing strategy management module and a Wi-Fi data packet management module. The Wi-Fi card routing strategy management module can be used to manage and save the URSP issued by the core network. The Wi-Fi data packet management module accelerates the data transmitted to the CPE 200 through the low-latency service slice.

[0349] The routing module 2002 can be used to associate the MAC address of the UE with the network service and the slice to which the UE subscribes.

[0350] The routing module 2002 can also be configured to construct an end-to-end data path according to the MAC address of the UE, the association between the network service to which the UE is subscribed and the slice, and the routing rule of the slice.

[0351] The routing module 2002 can also be configured to be responsible for refreshing the dynamic routing rule according to the network state.

[0352] The routing module 2002 can also be configured to refresh the database in which the MAC address of the UE is saved and refresh the routing rule in a case where the Portal information authentication of the UI module 2005 changes or the configuration in the UI module 2005 changes. For example, in a case where the MAC address changes after re-accessing, or the user changes the subscription of the slice, or the user cancels the subscription, the routing module 2002 refreshes the routing rule.

[0353] The routing module 2002 can also be configured to perform the above steps S404-S405, which will not be repeated here.

[0354] The modem module 2003 can be configured to receive the URSP sent by the core network and report the URSP information to the slice application module 2004.

[0355] The modem module 2003 can also be configured to perform the above steps S4011-S40111, which will not be repeated here.

[0356] The slice application module 2004 can be configured to initiate the establishment of a multi-slice session according to the URSP information reported by the modem module 2003 and the allowed slice and the disallowed slice information.

[0357] The slice application module 2004 can be configured to report the PDU session information to the UI module 2005.

[0358] The UI module 2005 can be configured to display a UI interface and provide a user interface for the user to perform Portal authentication. The UI module 2005 can also be configured to configure the association between the UE and the subscribed service and slice.

[0359] The UI module 2005 can also be configured to associate the username of the UE with the MAC address of the UE, save the association between the username of the UE and the MAC address of the UE in a database, and send the association to the router module 2002.

[0360] The apparatus 1400 can be the CPE 200 in the above embodiments.

[0361] In another example, Figure 15A structural diagram of the apparatus 1500 is shown, which can include a transceiver 1501. The transceiver 1501 can be configured to receive first route selection policy (URSP) information from a network side, the first URSP information including an application identifier (App Id) and first slice parameter information, the App Id being used to identify an application, and the first slice parameter information being used to indicate a first slice network; and the apparatus 1500 performs data interaction with the network side through a cellular network.

[0362] The transceiver 1501 can also be configured to receive a data packet sent by a UE through a Wi-Fi network. The data packet can carry an App Id of an application sending the data packet in the UE.

[0363] The transceiver 1501 can also be configured to, when determining that a network service corresponding to a subscription of the UE sending the data packet corresponds to the first slice, transmit the data packet to the network side through the first slice network.

[0364] The transceiver 1501 can also be configured to, when the App Id in the data packet is the same as the App Id in the first URSP information, transmit the data packet to the network side through the first slice network indicated by the first slice parameter information.

[0365] On the basis of the method embodiments, the first URSP information further includes other service characteristic information, and the other service characteristic information includes at least one of IP triple information, data network name (DNN) information, and full qualified domain name (FQDN) information.

[0366] The transceiver 1501 is also configured to receive second URSP information from the network side, the second URSP information including an App Id, other service characteristic information, and second slice parameter information, the second slice parameter information being used to indicate a second slice network, and the first slice parameter information being different from the second slice parameter information.

[0367] The apparatus 1500 further includes a processing unit 1502, which can be configured to, when the other service characteristic information in the second URSP information is different from the other service characteristic information in the first URSP information, update the second URSP information, and the other service characteristic information in the updated second URSP information being the same as the other service characteristic information in the first URSP information.

[0368] The processing unit 1502 can be configured to determine a network service type and a corresponding slice corresponding to a data packet sent by the UE according to a network service subscribed by the UE.

[0369] The processing unit 1502 can be configured to match the service feature of the data packet sent by the UE with the service feature of the directed service in the URSP when it is determined that the network service to which the UE subscribes is a directed service, and determine that the network service type corresponding to the data packet sent by the UE is a directed service if the matching is successful.

[0370] On the basis of the method embodiments described above, the transceiver unit 1501 is further configured to transmit the data packet to the network side through a non-slice network or a third slice network when it is determined that the UE does not subscribe to the service, or the UE subscribes to a directed service but the service feature of the data packet sent by the UE does not match the service feature in the URSP, and the third slice network can be a default slice.

[0371] On the basis of the method embodiments described above, the transceiver unit 1501 is further configured to transmit the data of the first application on the first slice network based on the PDU session if a protocol data unit (PDU) session corresponding to the first slice network has been established between the second electronic device and the network side.

[0372] On the basis of the method embodiments described above, the processing unit 1502 can be configured to establish a PDU session corresponding to the first slice network with the network side based on the slice parameter information if no PDU session corresponding to the first slice network has been established between the device 1500 and the network side, and the transceiver unit 1501 can be configured to transmit the data packet on the first slice network based on the PDU session.

[0373] On the basis of the method embodiments described above, the transceiver unit 1501 can be further configured to receive allowed network slice selection assistance information (Allowed NSSAI) from the network side, where the Allowed NSSAI is used to indicate a set of slice networks allowed to transmit data by the device 1500, and the first slice network is included in the set of slice networks.

[0374] On the basis of the method embodiments described above, the App Id can be the application package name of the application.

[0375] The device 1500 can be the CPE 200 in the embodiments described above.

[0376] In yet another example, Figure 16 A structural schematic diagram of a device 1600 is shown, which includes a processing unit 1601 and a transceiver unit 1602. The processing unit 1601 is configured to run an application program that sends a data packet. The transceiver unit 1602 is configured to send the data packet to the device 1500 through a Wi-Fi network, and the data packet can carry an App Id.

[0377] On the basis of the method embodiments described above, the App Id is the application package name of the application.

[0378] The apparatus 1600 can be the UE 100 in the above-described embodiments.

[0379] In yet another example, Figure 17 A schematic block diagram of an apparatus 1700 according to an embodiment of the present application is shown. The apparatus 1700 can include a processor 1701 and a transceiver / transmit-receive pin 1702, and optionally further include a memory 1703.

[0380] The various components of the apparatus 1700 are coupled together by a bus 1704, which can include a data bus, a power bus, a control bus, and a state signal bus. For the sake of clarity, the various buses are illustrated in Figure as the bus 1704.

[0381] Optionally, the memory 1703 can be used to store instructions in the above-described method embodiments. The processor 1701 can be used to execute the instructions in the memory 1703, and control the receive pin to receive signals and the transmit pin to transmit signals.

[0382] The apparatus 1700 can be the UE 100 or the CPE 200 in the above-described method embodiments. Illustratively, when the apparatus is the CPE 200 described above, the memory 1703 can further store information such as the MAC address of the UE, the username of the UE, and the like, and the association information between the network service to which the UE is subscribed and the slice corresponding to the network service.

[0383] The apparatus 1700 can be a chip, which can implement the slice selection method described in the above-described embodiments.

[0384] All relevant content of each step involved in the above-described method embodiments can be cited from the function description of the corresponding function module, and will not be repeated here.

[0385] The present embodiment also provides a computer storage medium, which stores computer instructions, and when the computer instructions run on an electronic device, the electronic device executes the above-described related method steps to implement a slice selection method in the above-described embodiments.

[0386] The present embodiment also provides a computer program product, which, when running on a computer, causes the computer to execute the above-described related steps to implement a slice selection method in the above-described embodiments.

[0387] In addition, the embodiments of the present application further provide an apparatus, which can be a chip, a component or a module, and the apparatus can comprise a processor and a memory connected to each other; the memory is used to store computer-executable instructions; when the apparatus is running, the processor can execute the computer-executable instructions stored in the memory, so that the chip executes one of the slice selection methods in the above method embodiments.

[0388] Among them, the electronic device, computer storage medium, computer program product or chip provided by the embodiment are all used to execute the corresponding method provided above, so the beneficial effects that can be achieved by them can refer to the beneficial effects in the corresponding method provided above, which will not be repeated here.

[0389] The above embodiments are only used to illustrate the technical solutions of the present application, but not limit the present application; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

[0390] In the above embodiments, according to the context, the term "when" can be interpreted as meaning "if" or "after" or "in response to determining" or "in response to detecting". Similarly, according to the context, the phrase "upon determining" or "if detecting (the stated condition or event)" can be interpreted as meaning "if determining" or "in response to determining" or "upon detecting (the stated condition or event)" or "in response to detecting (the stated condition or event)".

[0391] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk) and the like.

[0392] Those of ordinary skill in the art understand that all or part of the processes in the above embodiments can be implemented by a computer program to instruct the relevant hardware, which can be stored in a computer readable storage medium. The program can include the processes of the above method embodiments when executed. The aforementioned storage medium includes ROM or random access memory (RAM), magnetic disk or optical disk, and various media that can store program codes.

Claims

1. A slice selection method, characterized in that, include: The first terminal receives the first data packet sent by the second terminal. The second terminal establishes a communication connection with the first terminal through a Wi-Fi network. The first terminal establishes a communication connection with the network side through a cellular network. The first terminal determines one or more network services subscribed to by the second terminal, and each of the one or more network services is associated with a slice network. The first terminal determines that the network service type corresponding to the first data packet is the first network service among the one or more network services; The first terminal transmits the first data packet to the network side through the first slice network associated with the first network service.

2. The method according to claim 1, characterized in that, The first terminal determines one or more network services subscribed to by the second terminal, including: The first terminal searches for one or more network services associated with the first identifier in the first database of the first terminal based on the first identifier of the second terminal. The first database stores the identifiers of one or more terminals and one or more network services associated with the identifiers of the one or more terminals, and the identifiers of the one or more terminals include the first identifier. The first terminal determines one or more network services that the second terminal has subscribed to.

3. The method according to any one of claims 1 or 2, characterized in that, Before the first terminal receives the first data packet sent by the second terminal, the method further includes: The first terminal receives Terminal Routing Policy (URSP) information sent by the network side. The URSP information includes one or more slice parameter information, including a first slice parameter information, which is used to indicate the first slice network.

4. The method according to claim 3, characterized in that, The first terminal determines one or more network services subscribed to by the second terminal, including: The first terminal determines that the network service subscribed to by the second terminal is the first network service; The first terminal determines that the network service type corresponding to the first data packet is the first network service among the one or more network services, including: The first terminal determines that the network service type corresponding to the first data packet is the first network service.

5. The method according to claim 4, characterized in that, When the first network service is a targeted service, the first terminal determines that the network service type corresponding to the first data packet is the first network service, including: The first terminal acquires the service characteristics in the first data packet; The first terminal matches the service features with the service features corresponding to the targeted service in the URSP information; If the service characteristics match the service characteristics corresponding to the targeted service in the URSP information, the first terminal determines that the network service type corresponding to the first data packet is the first network service.

6. The method according to claim 2, characterized in that, The first terminal determines one or more network services subscribed to by the second terminal, including: The first terminal determines multiple network services subscribed to by the second terminal; The first terminal determines that the network service type corresponding to the first data packet is the first network service among the one or more network services, including: Based on the service characteristics of the first data packet and the service characteristics corresponding to the multiple network services in the URSP information, the first terminal determines that the network service type corresponding to the first data packet is the first network service among the multiple network services.

7. The method according to claim 6, characterized in that, the first terminal determines the network service type corresponding to the first data packet as the first network service among the plurality of network services based on the service characteristics of the first data packet and the service characteristics corresponding to the plurality of network services in the URSP information, including: The first terminal acquires the service characteristics in the first data packet; The first terminal matches the service features with the service features corresponding to the multiple network services in the URSP information respectively; If the service characteristics match the service characteristics corresponding to the first network service in the URSP information, the first terminal determines that the network service type corresponding to the first data packet is the first network service.

8. The method according to claim 2, characterized in that, Before the first terminal receives the first data packet sent by the second terminal, the method further includes: Based on the subscription information sent by the second terminal, the first terminal establishes an association between the first identifier of the second terminal and one or more network services in the second terminal.

9. The method according to any one of claims 4-8, characterized in that, The first terminal transmits the first data packet to the network side through a first slice network associated with the first network service, including: If a Protocol Data Unit (PDU) session corresponding to the first slice network has been established between the first terminal and the network side, the first terminal transmits the first data packet to the network side through the first slice network based on the PDU session.

10. The method according to claim 9, characterized in that, The first terminal transmits the first data packet to the network side through a first slice network associated with the first network service, including: The first terminal establishes a PDU session with the network side corresponding to the first slice network based on the slice parameter information; The first terminal transmits the first data packet to the network side through the first slice network based on the PDU session.

11. The method according to claim 1, characterized in that, After the first terminal transmits the first data packet to the network side through the first slice network associated with the first network service, the method further includes: The first terminal receives the second data packet sent by the network side through the first slice network; When the first slice network is a low-latency slice network, the first terminal accelerates the transmission of the second data packet to the second terminal.

12. The method according to claim 11, characterized in that, The method further includes: The first terminal receives AllowedNSSAI, a network slice selection assistance information sent by the network side. The AllowedNSSAI indicates the set of slice networks that allow the first terminal to transmit data. The first slice network is included in the set of slice networks.

13. The method according to any one of claims 10-12, characterized in that, The first identifier includes the username of the second terminal and / or the media storage control MAC address of the second terminal.

14. The method according to claim 13, characterized in that, The service characteristics of the first data packet include at least one of the following: App ID of the first application, IP triplet information, data network name (DNN) information, and destination full domain name (FQDN) information; the first application is the application in the second terminal that sends the first data packet.

15. A slice selection system, characterized in that, It includes a first terminal and a second terminal. The second terminal establishes a communication connection with the first terminal through a Wi-Fi network, and the first terminal establishes a communication connection with the network side through a cellular network. The second terminal is used to send the first data packet to the first terminal; The first terminal is used to receive the first data packet sent by the second terminal; The first terminal is used to determine one or more network services subscribed to by the second terminal, wherein each of the one or more network services is associated with a slice network; The first terminal is used to determine that the network service type corresponding to the first data packet is the first network service among the one or more network services; The first terminal is used to transmit the first data packet to the network side through a first slice network associated with the first network service.

16. A communication device applied to a first terminal, characterized in that, The device includes one or more processors, one or more memories, and a transceiver; wherein the transceiver, the one or more memories, and the one or more processors are coupled together, the one or more memories being used to store computer program code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the communication device to perform the method as described in any one of claims 1-14.

17. A computer-readable storage medium applied to a first terminal, characterized in that, The computer-readable storage medium stores instructions that, when executed on the first terminal, cause the first terminal to perform the method as described in any one of claims 1-14.

18. A chip or chip system applied to a first terminal, characterized in that, It includes a processing circuit and an interface circuit, the interface circuit being used to receive code instructions and transmit them to the processing circuit, the processing circuit being used to execute the code instructions to perform the method as described in any one of claims 1-14.

19. A computer program product, applied to a first terminal, characterized in that, The computer program product includes a computer program or instructions that, when executed on the first terminal, cause the first terminal to perform the method as described in any one of claims 1-14.

Images