CN116567783A

CN116567783A - Slice selection method, system and related device

Info

Publication number: CN116567783A
Application number: CN202210111677.7A
Authority: CN
Inventors: 赵志华; 黄瑜; 惠少博
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-01-29
Filing date: 2022-01-29
Publication date: 2023-08-08
Also published as: WO2023143300A1

Abstract

A slice selection method, system and related apparatus. In the method, a CPE receives a data packet sent by a UE, the CPE stores the corresponding relation between network services subscribed by the UE and slices, the CPE determines the slices corresponding to the data packet based on the network service types subscribed by the UE, and routes the data packet to the corresponding slices. By implementing the technical scheme provided by the application, the CPE can provide differentiated network services for the UE subscribed with different network services.

Description

Slice selection method, system and related device

Technical Field

The present disclosure relates to the field of terminals and communications technologies, and in particular, to a slice selection method, a system, and a related device.

Background

Currently, in the fifth generation (5th Generation,5G) communication system, terminals can access the cellular network through a slice. In order to meet the demands of users in different scenes, the types of slices are also increasing. Operators may offer differentiated network services to subscribers through different slices.

For an application scenario where a user front-end device (Customer Premise Equipment, CPE) exists, a terminal needs to be accessed to 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 IP triplets in the routing policy as a route match criteria for the data to determine the corresponding slice. However, the terminal may sign up for different network services, which require different slices.

Thus, how to provide differentiated network services for terminals subscribed to different network services by the CPE is a problem to be solved.

Disclosure of Invention

The application provides a slice selection method, a system and a related device, and by implementing the slice selection method provided by the embodiment of the application, CPE can determine a slice network corresponding to data sent by a terminal based on network service signed by the terminal. Thus, the data sent by the same type of application in different terminals can be routed to different slicing networks by terminals subscribed to different network services. The CPE may provide differentiated network services for terminals subscribing to different network services.

In a first aspect, the present application provides a slice selection method, which may include: the method comprises the steps that a first terminal receives a first data packet sent by a second terminal, the second terminal establishes communication connection with the first terminal through a wireless fidelity Wi-Fi network, and the first terminal establishes communication connection with a network side through a cellular network; the first terminal determines one or more network services subscribed by the second terminal, and each network service in the one or more network services is associated with a slicing network; the first terminal determines the network service type corresponding to the first data packet as a first network service in one or more network services; the first terminal transmits a service request first data packet to a network side through a first slice network associated with a first network service.

The first terminal may be a CPE, and the second terminal may be a user terminal such as a mobile phone, a tablet, a computer, or the like.

In one possible implementation, the first data packet may be a service request data packet.

Thus, the first terminal can determine the slicing network corresponding to the data sent by the second terminal according to the network service subscribed by the second terminal. The first terminal may provide differentiated network services for the second terminal subscribing to different network services.

With reference to the first aspect, in one possible implementation manner, the determining, by the first terminal, one or more network services subscribed by the second terminal based on the first identifier of the second terminal includes: the first terminal determines one or more network services subscribed to by the second terminal based on the first identification of the second terminal.

With reference to the first aspect, in one possible implementation manner, the first terminal determines one or more network services subscribed by the second terminal based on the first identifier of the second terminal, including that the first terminal searches a first database of the first terminal for one or more network services associated with the first identifier based on the first identifier of the second terminal; the method comprises the steps that 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 comprise a first identifier; the first terminal determines one or more network services subscribed to by the second terminal.

Thus, the first terminal can conveniently and accurately find out the network service subscribed by the second terminal.

With reference to the first aspect, in one possible implementation manner, before the first terminal receives the first data packet sent by the second terminal, the method may further include: the first terminal receives terminal routing strategy URSP information sent by a network side, wherein the URSP information comprises one or more slice parameter information, the one or more slice parameter information comprises first slice parameter information, and the first slice parameter information is used for indicating a first slice network.

With reference to the first aspect, in one possible implementation manner, the determining, by the first terminal, one or more network services subscribed to by the second terminal includes: the first terminal determines that one network service subscribed by the second terminal is a first network service; the first terminal determining that the network service type corresponding to the first data packet is a first network service of the one or more network services, including: the first terminal determines the network service type corresponding to the first data packet as a first network service.

With reference to the first aspect, in one possible implementation manner, in a case that the first network service is a directional service, the determining, by the first terminal, that a network service type corresponding to the first data packet is the first network service includes: the method comprises the steps that a first terminal obtains service characteristics in a first data packet; the first terminal matches the service characteristics with the service characteristics corresponding to the directional service in the URSP information; under the condition that the service characteristics are successful with the service characteristics corresponding to the directional 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.

In general, the second terminal may sign up for a specific service or an application specific targeted service for the second terminal. Therefore, whether the application where the specific service is or the data sent by the specific application is needed to be matched according to the URSP rule, if so, the network service of the data is a directional service; if the data is sent by other applications in the second terminal, the network service corresponding to the data is not the directional service.

With reference to the first aspect, in one possible implementation manner, the determining, by the first terminal, one or more network services subscribed to by the second terminal includes: the first terminal determines a plurality of network services signed by the second terminal; the first terminal determining that the network service type corresponding to the first data packet is a first network service of the one or more network services, including: the first terminal determines that the network service type corresponding to the first data packet is a first network service of 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.

With reference to the first aspect, in one possible implementation manner, the determining, by the first terminal, based on the service feature of the first data packet and the service feature corresponding to the plurality of network services in the urs p information, that the network service type corresponding to the first data packet is a first network service of the plurality of network services includes: the method comprises the steps that a first terminal obtains service characteristics in a first data packet; the first terminal respectively matches the service characteristics with the service characteristics corresponding to a plurality of network services in the URSP; under the condition that the service characteristics are successfully matched with the service characteristics corresponding to the first network service in the URSP, the first terminal determines that the network service type corresponding to the first data packet is the first network service.

With reference to the first aspect, in one possible implementation manner, before the first terminal receives the first data packet sent by the second terminal, the method may 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.

With reference to the first aspect, in one possible implementation manner, the transmitting, by a first terminal, a first data packet to the network side through a first slice network associated with a first network service includes: in case that a protocol data unit PDU session corresponding to the first slice network is 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.

With reference to the first aspect, in one possible implementation manner, the transmitting, by a first terminal, a first data packet to a network side through a first slice network associated with the first network service includes: the first terminal establishes a PDU session corresponding to a first slice network with a network side based on slice parameter information; the first terminal transmits a first data packet to a network side through a first slice network based on the PDU session.

With reference to the first aspect, in one 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 may further include: the first terminal receives a second data packet sent by a network side; and in the case that the first slice network is a low-delay slice network, the first terminal sends the second data packet to the second terminal in an acceleration way.

The second data packet may be a traffic response data packet, for example.

With reference to the first aspect, in a possible implementation manner, the method may further include: the method comprises the steps that a first terminal receives allowable network slice selection auxiliary information allowable NSSAI sent by a network side, wherein the allowable NSSAI is used for indicating a slice network set allowing the first terminal to transmit data; the first slice network is included in a set of slice networks.

With reference to the first aspect, in one possible implementation manner, the first identifier includes a user name of the second terminal, and/or a media storage control MAC address of the second terminal.

With reference to the first aspect, in one possible implementation manner, the user name of the second terminal may be a mobile phone number of the second terminal.

With reference to the first aspect, in one possible implementation manner, the service feature of the first data packet includes at least one of App Id, IP triplet information, data network name DNN information, and destination full-scale domain name FQDN information of the first application; the first application is an application in the second terminal that transmits the first data packet.

A second aspect provides a slice selection system, which is characterized by comprising a first terminal and a second terminal, wherein the second terminal establishes communication connection with the first terminal through a Wi-Fi network, and the first terminal establishes communication connection with a network side through a cellular network; the second terminal is used for sending a first data packet to the first terminal; the first terminal is used for receiving a first data packet sent by the second terminal; the first terminal is used for determining one or more network services subscribed by the second terminal, and each network service in the one or more network services is associated with a slicing network; the first terminal is used for determining that the network service type corresponding to the first data packet is a first network service in one or more network services; the first terminal is used for transmitting the first data packet to the network side through a first slice network associated with a first network service.

In a possible implementation manner, the first terminal may further perform the method in any one of the possible implementation manners of the first aspect.

In a possible implementation manner, the second terminal may further perform the method in any one of the possible implementation manners of the second aspect.

In a third aspect, the present application provides a communication device comprising one or more processors, one or more memories, and a transceiver. The transceiver, the one or more memories being coupled to one or more processors, the one or more memories being for storing computer program code comprising computer instructions that, when executed by the one or more processors, cause the communications apparatus to perform the method in any of the possible implementations of the first terminal in the first aspect described above.

The communication device may be a first terminal or other product form of equipment.

In a fourth aspect, the present application provides a communication device comprising one or more processors, one or more memories, and a transceiver. The transceiver, the one or more memories being coupled to one or more processors, the one or more memories being for storing computer program code comprising computer instructions that, when executed by the one or more processors, cause the communications apparatus to perform the method in any of the possible implementations of the second terminal of the first aspect.

The communication device may be a second terminal or other product form of equipment.

In a fifth aspect, the present application provides a computer storage medium comprising computer instructions which, when run on a computer, cause the computer to perform the method of any one of the possible implementations of the first aspect.

In a sixth aspect, the present application provides a computer program product for, when run on a computer, causing the computer to perform the method of any one of the possible implementations of the first aspect.

In a seventh aspect, the present application provides a chip or chip system for use in a first terminal, comprising processing circuitry and interface circuitry, the interface circuitry being for receiving code instructions and for transmitting to the processing circuitry, the processing circuitry being for executing the code instructions to perform the method of any one of the possible implementations of the first aspect.

Drawings

Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of a CPE according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a URSP format provided in an embodiment of the present application;

fig. 5 is a schematic flow chart of accessing a CPE to a core network according to an embodiment of the present application;

fig. 6 is a schematic flow chart of a UE accessing a CPE according to an embodiment of the present application;

fig. 7 is a schematic diagram of interaction between a UE, CPE and a core network according to an embodiment of the present application;

FIG. 8A is a schematic diagram of a data format provided in an embodiment of the present application;

FIG. 8B is a schematic diagram of a data format according to an embodiment of the present application;

fig. 9 is a schematic flow chart of a slice selection method according to an embodiment of the present application;

FIG. 10 is a schematic diagram of a parsing URSP flow provided in an embodiment of the present application;

fig. 11 is a schematic diagram of a subscription different network service scenario provided in an embodiment of the present application;

FIG. 12 is a schematic diagram of a user interface provided by an embodiment of the present application;

fig. 13 is a flowchart of determining a network service type corresponding to a data packet sent by a UE according to an embodiment of the present application;

FIG. 14 is a schematic view of a device according to an embodiment of the present disclosure;

FIG. 15 is a schematic view of a device according to an embodiment of the present disclosure;

FIG. 16 is a schematic view of a device according to an embodiment of the present disclosure;

fig. 17 is a schematic view of a device structure according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

The terminology used in the following embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates to the contrary. It should also be understood that the term "and/or" as used in this application refers to and encompasses any or all possible combinations of one or more of the listed items.

The terms "first," "second," and the like, are used below for descriptive purposes only and are not to be construed as implying or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature, and in the description of embodiments of the present application, unless otherwise indicated, the meaning of "a plurality" is two or more.

The terms first and second and the like in the description and in the claims of embodiments of the present application are used for distinguishing between different objects and not necessarily for describing a particular sequential order of objects. For example, the first target object and the second target object, etc., are used to distinguish between different target objects, and are not used to describe a particular order of target objects.

In the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

Before describing the technical solution of the embodiments of the present application, a description is first given of the communication system of the embodiments of the present application with reference to the accompanying drawings.

Fig. 1 schematically illustrates a communication system according to an embodiment of the present application. Referring to fig. 1, the communication system 10 includes a terminal 100 (e.g., a mobile phone 101, a watch 102, a computer 103, a projector 104, etc.), a CPE200, and a core network. It should be noted that, in practical applications, the number of terminals 100 and CPEs may be one or more, and the number of terminals 100 and CPEs 200 of the communication system 10 shown in fig. 1 is merely an adaptive example, which is not limited in this application.

It should be further noted that the core network may be a device cluster formed by one or more core network devices, and optionally, the core network devices may be access and mobility management functions (access and mobility management function, AMF), mainly responsible for access control, mobility management (mobility management, MM), attachment and detachment, and gateway selection. The core network device according to the embodiment of the present application is not limited to AMF.

The terminal 100 may be a wireless communication chip, a wireless sensor, a wireless communication terminal, or the like, and may also be referred to as a User Equipment (UE), a Station (STA), or a terminal device. For example, the terminal 100 may be a mobile phone supporting a wireless fidelity (wireless fidelity, wi-Fi) communication function, a tablet computer supporting a Wi-Fi communication function, a set-top box supporting a Wi-Fi communication function, a smart television supporting a Wi-Fi communication function, a smart wearable device supporting a Wi-Fi communication function, a vehicle communication device supporting a Wi-Fi communication function, a computer supporting a Wi-Fi communication function, or the like. Optionally, the terminal may support 802.11be standard. The terminal may also support multiple wireless local area network (wireless local area network, WLAN) systems of 802.11 families, such as 802.11be, 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11 a.

For example, the CPE200 and the terminal 100 may be devices applied in the internet of things, internet of things nodes, sensors, etc. in the internet of things (IoT, internet of things), smart cameras in smart homes, smart remote controllers, smart water meter meters, sensors in smart cities, etc.

It should be noted that, the CPE200 and the terminal 100 in the present application may also be a wireless communication device that supports parallel transmission of multiple links, for example, referred to as a multi-link device (multi-link device) or a multi-band device (multi-band device). A multi-link device has higher transmission efficiency and higher throughput than a device that supports only a single link transmission.

Although the present application is illustrated with respect to a network in which IEEE 802.11 is deployed between CPE200 and terminal 100, those skilled in the art will readily appreciate that various aspects of the present application may be extended to other networks employing various standards or protocols, such as BLUETOOTH, high performance wireless local area networks (high performance radio local area network, HIPERLAN), a wireless standard similar to the IEEE 802.1 standard and used primarily in europe, as well as wide area networks (wide area network, WAN), wireless local area networks (wireless local area network, WLAN), personal area networks (personal area network, PAN), or other now known or later developed networks. Accordingly, the various aspects provided herein may be applicable to any suitable wireless network regardless of the coverage area and wireless access protocol used.

In one possible implementation, a wired network may be further disposed between the CPE200 and the terminal 100, and the terminal 100 may be a wired communication chip, a wired sensor, a wired communication terminal, or the like, that is, a device connected to the CPE200 through a network cable. In this application, a wireless network is disposed between the CPE200 and the terminal 100, and for a scenario in which a wired network is disposed between the CPE and the terminal, reference may be made to the technical solution in the embodiment of the present application, which is not repeated in this application.

An exemplary terminal 100 provided in an embodiment of the present application is described below. Fig. 2 is a schematic structural diagram of a terminal 100 according to an embodiment of the present application.

Referring to fig. 2, an embodiment will be specifically described below using the terminal 100 as an example. It should be understood that terminal 100 may have more or fewer components than shown, may combine two or more components, or may have a different configuration of components. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

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

It should be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the terminal 100. In other embodiments of the present application, terminal 100 may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a memory, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller may be a neural hub and a command center of the terminal 100, among others. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

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

The I2C interface is a bi-directional synchronous serial bus comprising a serial data line (SDA) and a serial clock line (derail clock line, SCL). In some embodiments, the processor 110 may contain multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, charger, flash, camera 193, etc., respectively, through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through an I2C bus interface to implement a touch function of the terminal 100.

The I2S interface may be used for audio communication. In some embodiments, the processor 110 may contain multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through the I2S interface, to implement a function of answering a call through the bluetooth headset.

PCM interfaces may also be used for audio communication to sample, quantize and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface.

The UART interface is a universal serial data bus for asynchronous communications. The bus may be a bi-directional communication bus. It converts the data to be transmitted between serial communication and parallel communication.

The MIPI interface may be used to connect the processor 110 to peripheral devices such as a display 194, a camera 193, and the like. The MIPI interfaces include camera serial interfaces (camera serial interface, CSI), display serial interfaces (display serial interface, DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the photographing function of terminal 100. The processor 110 and the display 194 communicate through a DSI interface to implement the display function of the terminal 100.

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

The SIM interface may be used to communicate with the SIM card interface 195 to perform functions of transferring data to or reading data from the SIM card.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the terminal 100, or may be used to transfer data between the terminal 100 and a peripheral device. And can also be used for connecting with a headset, and playing audio through the headset. The interface may also be used to connect other electronic devices, such as AR devices, etc.

It should be understood that the interfacing relationship between the modules illustrated in the embodiment of the present invention is only illustrative, and does not limit the structure of the terminal 100. In other embodiments of the present application, the terminal 100 may also use different interfacing manners, or a combination of multiple interfacing manners in the foregoing embodiments.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger.

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like.

The wireless communication function of the terminal 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in terminal 100 may be configured to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the terminal 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the 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 is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc., applied on the terminal 100. The wireless communication module 160 may 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, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

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, such that terminal 100 may communicate with a network and other devices via wireless communication techniques. The wireless communication techniques may include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a beidou satellite navigation system (beidou navigation satellite system, BDS), a quasi zenith satellite system (quasi-zenith satellite system, QZSS) and/or a satellite based augmentation system (satellite based augmentation systems, SBAS).

Terminal 100 implements display functions via a GPU, display 194, and application processor, etc. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light emitting diode (AMOLED), a flexible light-emitting diode (flex), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the terminal 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The terminal 100 may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. ISP can also optimize the noise, brightness and color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted 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, terminal 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the terminal 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, etc.

Video codecs are used to compress or decompress digital video. The terminal 100 may support one or more video codecs. In this way, the terminal 100 may play or record video in a variety of encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent cognition of the terminal 100 can be implemented by the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to realize the memory capability of the extension terminal 100. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store computer executable program code including instructions. The processor 110 executes various functional applications of the terminal 100 and data processing by executing instructions stored in the internal memory 121. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an operating system, an application required for at least one function (such as a face recognition function, a fingerprint recognition function, a mobile payment function, etc.), and the like. The storage data area may store data created during use of the terminal 100 (e.g., face information template data, fingerprint information templates, etc.), and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like.

The terminal 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals.

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The terminal 100 can listen to music or to handsfree calls through the speaker 170A.

A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When the terminal 100 receives a telephone call or voice message, it is possible to receive voice by approaching the receiver 170B to the human ear.

Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The terminal 100 may be provided with at least one microphone 170C.

The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be a USB interface 130 or a 3.5mm open mobile electronic device platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal.

The gyro sensor 180B may be used to determine a motion gesture of the terminal 100.

The air pressure sensor 180C is used to measure air pressure.

The magnetic sensor 180D includes a hall sensor. The terminal 100 may detect the opening and closing of the flip cover using the magnetic sensor 180D.

The acceleration sensor 180E may detect the magnitude of acceleration of the terminal 100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the terminal 100 is stationary. The electronic equipment gesture recognition method can also be used for recognizing the gesture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The terminal 100 emits infrared light outward through the light emitting diode. The terminal 100 detects infrared reflected light from nearby objects using a photodiode.

The ambient light sensor 180L is used to sense ambient light level. The terminal 100 may adaptively adjust the brightness of the display 194 according to the perceived ambient light level.

The fingerprint sensor 180H is used to collect a fingerprint.

The temperature sensor 180J is for detecting temperature.

The touch sensor 180K, also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The terminal 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the terminal 100.

The motor 191 may generate a vibration cue.

The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card interface 195 may also be compatible with external memory cards. The terminal 100 interacts with the network through the SIM card to realize functions such as call and data communication.

Next, an exemplary CPE200 of an embodiment of the present application is described.

Fig. 3 is a schematic diagram illustrating the structure of a CPE200, and referring to fig. 3, the CPE200 includes 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 CPE200 may also include 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, by a bus. An antenna 205 is connected to the transceiver 203. The network interface 204 is used to enable the CPE to connect to other communication equipment via a communication link, e.g. terminal equipment may be connected via the network interface 204. In the embodiment of the present application, the connection may include various interfaces, transmission lines, buses, and the like, which is not limited in this embodiment. The SIM card interface 206 is used to enable the CPE to communicate with the core network through the mobile network, and the specific description can refer to the description on the terminal side, which is not repeated here.

A processor in an embodiment of the present application, such as processor 201, may include at least one of the following types: a general purpose central processing unit (Central Processing Unit, CPU), a digital signal processor (Digital Signal Processor, DSP), a microprocessor, an Application-specific integrated circuit (ASIC), a microcontroller (Microcontroller Unit, MCU), a field programmable gate array (Field Programmable Gate Array, FPGA), or an integrated circuit for implementing logic operations. For example, processor 201 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The at least one processor 201 may be integrated in one chip or located on a plurality of different chips.

The memory in the embodiment of the present application, for example, the memory 202, may 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 (random access memory, RAM) or other types of dynamic storage devices that can store information and instructions, and electrically erasable programmable read-only memory (Electrically erasable programmabler-only memory, EEPROM). In some scenarios, the memory may also be, but is not limited to, a compact disk (compact disc read-only memory) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

The memory 202 may be stand alone and coupled to the processor 201. Alternatively, the memory 202 may be integrated with the processor 201, for example within a single chip. The memory 202 is capable of storing program codes for executing the technical solutions of the embodiments of the present application, and the execution is controlled by the processor 201, and various types of executed computer program codes can also be regarded as drivers of the processor 201. For example, the processor 201 is configured to execute computer program codes stored in the memory 202, thereby implementing the technical solutions in the embodiments of the present application. Alternatively, the memory 202 may be external to the chip and connected to the processor 201 via an interface.

The transceiver 203 may be used to support reception or transmission of radio frequency signals between the CPE and the terminal, and between the CPE and the core network device, and the transceiver 203 may be connected to an antenna 205. The transceiver 203 includes a transmitter Tx and a receiver Rx. Specifically, the one or more antennas 205 may receive radio frequency signals, and the receiver Rx of the transceiver 203 is configured to receive the radio frequency signals from the antennas, 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, so that the processor 201 performs further processing, such as demodulation processing and decoding processing, on the digital baseband signals or digital intermediate frequency signals. The transmitter Tx in the transceiver 203 is also configured to receive a modulated digital baseband signal or digital intermediate frequency signal from the processor 201, convert the modulated digital baseband signal or digital intermediate frequency signal to a radio frequency signal, and transmit the radio frequency signal via the one or more antennas 205. In particular, the receiver Rx may selectively perform one or more steps of down-mixing and analog-to-digital conversion on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency signal, where the order of the down-mixing and analog-to-digital conversion is adjustable. The transmitter Tx may selectively perform one or more stages of up-mixing processing and digital-to-analog conversion processing on the modulated digital baseband signal or the digital intermediate frequency signal to obtain a radio frequency signal, and the sequence of the up-mixing processing and the digital-to-analog conversion processing may be adjustable. The digital baseband signal and the digital intermediate frequency signal may be collectively referred to as a digital signal.

The above communication system may be used to support a fifth generation (5G) access technology and a future-oriented communication technology, for example, a New Radio (NR) access technology, and by way of example, the description of the embodiments of the present application uses a stand alone network (SA) in 5G as an example, and in fact, the technical solution of the present application may also be applied to other scenarios such as non-stand alone Network (NSA).

The 5G communication system introduces the concept of network slicing, which enables to divide one physical network into a plurality of virtual networks. A virtual network acts as a "network slice" and each network slice is independent of the other. Different protocol data unit (protocol data unit, PDU) sessions in one terminal may require network slices corresponding to the PDU sessions to provide services.

For a better understanding of the present application, the following is a brief description of the concept of network slicing and other possible background art to which the present application relates:

network slicing is a key technology of 5G, and is widely paid attention to and studied in 3GPP and other various international standardization organizations. The method can meet the customization requirements of operators for various industries, vertical markets and various virtual operation services. A Network Slice is a logical Network (Network Slice: A logical Network that provides specific Network capabilities and Network characteristics) that provides specific Network capabilities and Network characteristics. It may be a logical network with different network capabilities and network characteristics customized according to different service requirements or tenants, etc., over a physical or virtual network infrastructure. A network slice is made up of a set of network functions and their required resources (e.g., computing resources, storage resources, network resources).

In the embodiments of the present application, the network slice may be simply referred to as a slice.

The network slice may be configured by an operation, administration, and maintenance system (OAM). The single network slice selection assistance information (single network slice selection assistance information, S-NSSAI) is used to identify one network slice.

The S-NSSAI includes at least one of: slice type, service type (SST) information, optionally, S-NSSAI may also include slice distinguishing information (slice differentiator, SD). Wherein the SST information is used to indicate the behavior of the network slice, such as the characteristics of the network slice and the service type, and the SD information is complement information of the SST, such as: if the SST points to multiple network slices, the SD may assist in corresponding to a unique one of the network slices.

There are multiple types of services in the terminal, such as enhanced mobile broadband services (enhanced mobile broadband, eMBB), ultra-reliable low latency communications (ultra-reliable low latency communications, URLLC), mass machine type communications (massive machine type communication, mctc), etc., while the network slices corresponding to PDU sessions for different types of services may be different. Different applications in the terminal may correspond to different traffic types, that is, the applications in the terminal may correspond to different network slices. It should be noted that even the same service type may correspond to different network slices due to different operators or service providers. That is, the network slice may provide network resources for at least one PDU session of the terminal.

In existing standards, the core network determines the routing manner of data (data that can be understood as applications of different traffic types) by sending UE routing policies (UE route selection policy, urs) to the terminal, which may be used to indicate traffic characteristics and slice network activation parameters that need to be transmitted over the slice network, including which slice to route specifically to, or to transmit data using a non-slice network.

Exemplary, fig. 4 is a schematic diagram of a format of an exemplary illustrated urs, including, but not limited to: a urs rule length (Length of URSP rule) field, a priority (Precedence value of URSP rule) field of the urs rule, a traffic descriptor length (Length of Traffic descriptor) field, a Traffic descriptor field, a routing descriptor list length (Length of Route selection descriptor list) field, and a Route selection descriptor field.

Wherein Route selection descriptor list field is used to carry the slice network activation parameters including, but not limited to: S-NSSAI corresponding to one or more slices.

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 definition of other fields may be referred to the description in the 3GPP standard and is not described here in detail.

The description of the Traffic descriptor field in the 3GPP 24526 protocol is as follows:

traffic descriptor component type identifier (service descriptor field type definition)

Bits (bit position)

Wherein, the OS id+app Id constitutes application descriptor (Application descriptors) information for identifying applications in the operating system, it is also understood that Application descriptors may be used to indicate which applications in the operating system may transmit data through the slice network. Wherein, OS Id is used for identifying the operating system, app Id is used for identifying the application in the operating system. For example, the App Id may be an application package name of the application, that is, the UE downloads and installs the application from any platform or store, the App Id is included in the installation package of the application, and the UE may store the installation package name of the application after installing the application.

It should be noted that the above criteria apply to interactions between the terminal and the core network, that is, the terminal may match the urs issued by the core network with the App Id and other parameters of the current application to route the application data to the designated slice. However, in the application scenario where the CPE exists, since the existing CPE only has a forwarding function, there is no corresponding slice and service matching between the UE accessing the CPE and the UE. Thus, in this scenario, the CPE can only route the data of the application to the corresponding slice by matching means of IP triplets (including IPv4 remote address type or IPv6 remote address/prefix length type, protocol identifier/next header type, single remote port type), DNN (i.e., DNN type) and/or FQDN (i.e., destination FQDN type) in the urs.

However, in some scenarios, a user may sign up for different data traffic on the LAN side, e.g., low latency traffic, large bandwidth traffic, directional traffic, etc. Different data services have different demands on the data transmission network. However, the CPE can only route data sent in the UE to the corresponding slice according to the urs. However, different UEs may sign up for different types of network traffic, which correspond to different slices. Currently, CPE cannot associate a UE's traffic type with different slices. Thus, the CPE cannot meet the network requirements of UE differentiation.

The following is a simple description of the interaction flow of the terminal, CPE and core network in the existing standard with reference to the application scenario shown in fig. 2:

1) CPE access core network

Referring to fig. 2, fig. 5 shows a schematic flow chart of CPE accessing a core network in an embodiment of the present application, and as shown in fig. 5, the CPE accessing the core network may include the following steps:

s101, the CPE sends a registration request Registration request message to the core network.

Specifically, the CPE initiates a registration process under the conditions of startup, restarting or updating, for example, after startup, the CPE initiates a registration process, or after refreshing, the CPE initiates a registration process, which can be understood as the CPE registering to the network.

Illustratively, referring to fig. 5, the cpe sends Registration request a message to the core network requesting initiation of the registration procedure. For example, the Registration request message may carry information such as a registration type and a security parameter, and it should be noted that, for the core network, the CPE is equivalent to the UE, so the specific registration initiating procedure may refer to the UE registration procedure in the existing standard, which is not repeated in the present application.

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

Specifically, after the core network agrees that the CPE registers to access the network, a Registration accept message is sent to the CPE. The Registration accept message may carry one or more parameters for indicating that the CPE has access to the core network. Illustratively, in this embodiment, the Registration accept message carries network slice selection enabled auxiliary information (Allowed Network Slice Selection Assistance Information, allowed NSSAI) for indicating one or more slices that the CPE is enabled to access.

S103, the CPE stores the Allowed NSSAI.

Illustratively, the CPE may save the Allowed nsai to a storage element, such as the memory of the CPE, for use in subsequently establishing PDU session.

And S104, the core network sends a management terminal strategy command Manage UE policy command message to the CPE.

Specifically, the core network sends Manage UE policy command a message to the UE, including but not limited to a urs p. Illustratively, as described above, the urs may include traffic characteristics (e.g., IP triplets, app Id, etc.) and slice network activation parameters.

S105, the CPE stores the URSP.

Specifically, after acquiring the urs transmitted from the core network, the CPE may decode the urs to acquire and store parameters and information carried in each field in the urs.

And S106, the CPE sends a management terminal strategy completion Manage UE policy complete message to the core network.

Specifically, after the CPE successfully saves the parameters included in the urs, a Manage UE policy complete message may be sent to the core network to indicate that the CPE has successfully processed the urs.

Illustratively, if the CPE fails to resolve the urs or fails to save the urs for other reasons, the CPE sends a management terminal policy command failure Manage UE policy command reject message to the core network.

2) UE accessing CPE

Specifically, in the communication system according to the embodiment of the present application, the UE accesses the core network through the CPE, and fig. 6 schematically illustrates a specific flow of the UE connecting to the CPE. As shown in fig. 6, the UE accessing the CPE may include the steps of:

S201, the UE sends an authentication request Authentication Request message to the CPE.

S202, the CPE sends an authentication response Authentication Responce message to the UE.

S203, the UE sends an association request Association Request message to the CPE.

S204, the CPE sends an association response Association Responce message to the UE.

The CPE receives Association Response sent by the UE and determines that the UE has successfully accessed the CPE, or may understand that the UE has successfully accessed the core network through the CPE.

The specific details of step S201 to step S204 and the related descriptions may refer to the standard of the 802.11 protocol, which is not repeated herein.

3) And the UE and the CPE perform data interaction with the core network.

Specifically, after the UE accesses the CPE, a Wi-Fi channel between the UE and the CPE is established. The UE may send data to the CPE through a Wi-Fi channel between the UE and the CPE, and the CPE forwards the data to the core network through a mobile communication network between the CPE and the core network. And, the CPE may also receive data corresponding to the UE transmitted by the core network through the mobile communication network. The CPE then forwards the data to the UE via a Wi-Fi channel between the CPE and the UE. Thus, data interaction between the UE and the core network can be achieved.

Fig. 7 schematically illustrates a flow chart of UE, CPE interaction with a core network, as shown in fig. 7, which may specifically include the following steps:

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

Illustratively, the UE sends the data packet 1 to the CPE through the Wi-Fi channel with the CPE, and the format of the data packet 1 may be as shown in fig. 8A or fig. 8B.

Referring to fig. 8A, specifically, there is three layers (i.e. network layers) of data interaction between the UE and the CPE, where the data packet 1 may also be referred to as an IP data packet, and the data packet 1 may carry a data portion and an IP packet header (i.e. a header in the drawing), where the IP packet header includes a fixed portion (which may also be referred to as a fixed field) and a variable portion (which may also be referred to as a variable field), where the fixed field includes, but is not limited to: the variable fields include optional fields and reserved fields (which may also be referred to as padding fields) for parameters such as destination address, source address, etc. The fields included in the fixed portion are illustratively fixed, that is, each packet sent by the UE to the CPE needs to carry the fields in the fixed portion shown in fig. 8A, which may be the same or different. The fields included in the variable part and the lengths of the fields are all variable, that is, different UEs, or in different application scenarios, the field names, positions and lengths included in the variable part may be the same or different, which is not limited in this application. Note that, the names and positions of the parameters in the format of the data packet 1 shown in fig. 8A are only exemplary, and the present application is not limited thereto.

Referring to fig. 8B, the data packet 1 may carry a data portion and an IP packet header (i.e., a header in the drawing), where the IP packet header includes a fixed portion (which may also be referred to as a fixed field) and a variable portion (which may also be referred to as a variable field). The fixed part of the IP header may refer to the description in fig. 8A, and will not be described herein. The optional field part in the IP header in packet 1 may include the App Id of the application transmitting packet 1 in the UE. It should be noted that, the location of the App Id field in the optional field shown in fig. 8B is merely an exemplary example, and the length and location of the field may be set according to actual requirements, which is not limited in this application.

S302, the CPE acquires the IP triples.

The description will be given by taking the example that the urls issued by the core network include IP triplets. And the CPE responds to the received data packet 1 sent by the UE to acquire the IP triples.

Optionally, an App Id may also be included in the urs issued by the core network. The CPE may also obtain from the data packet 1 the App Id of the application in the UE that sent the data packet 1.

S303, the CPE checks the IP triples.

Illustratively, the CPE matches the acquired IP triplet with the urs indicated IP triplet stored in S105. If the matching of the IP triples is successful, i.e. each parameter in the IP triples exists in the urs issued by the core network. The CPE determines that the verification of the IP triplet is successful and the packet corresponding to the IP triplet can be routed to the slicing network.

Illustratively, if the IP triplet fails the check, i.e., any parameter in the IP triplet is not present in the urs, the CPE determines that the check fails, the packet will be routed to the default slice, typically the low priority slice, or the packet will be routed to a non-slice network.

Optionally, the CPE may also match the App Id obtained from the data packet 1 to the App Id in the urs of the application in the UE that sent the data packet 1. If the App Id matching is successful, the App Id of the application that sends the data packet 1 exists in the urs 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 urs.

Optionally, the CPE may also match the App Id and IP triplet obtained from the data packet 1 to the App Id and IP triplet in the urs for the application in the UE that sent the data packet 1.

S304a, the CPE routes packet 1 to the designated slice.

Illustratively, after the CPE successfully verifies the IP triplet, it may further obtain other relevant information of the slice, such as nsai of the slice, based on other information in the urs, such as the slice network activation parameters described above, etc.

Illustratively, the CPE may match the nsai of the slice with the Allowed nsai stored in S103 to determine whether the core network allows the data of the UE to be routed to the slice.

The CPE binds the IP triples in the data packet 1 with the PDU session corresponding to the slice, so that the data packets containing the IP triples which are received subsequently can be routed to the corresponding slice through the bound PDU session. For example, binding may refer to that the CPE records the IP triplet and 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 corresponding to the IP triplet (i.e. the data packet including the IP triplet), the CPE determines the PDU session bound to the IP triplet, and routes the data to the slice corresponding to the PDU session.

Here, the CPE may have bound the IP triplet in the data packet 1 with the PDU session corresponding to the slice before step S304 a.

Optionally, after the App Id is successfully verified by the CPE, other relevant information of the slice, such as nsai of the slice, may be further obtained based on other information in the urs p, such as the slice network activation parameters described above, etc.

In one example, if the CPE detects that the PDU session corresponding to the slice is not established, the PDU session establishment procedure needs to be triggered, and still referring to fig. 7, the method further includes:

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

Illustratively, the CPE initiates a PDU session establishment procedure to the core network to establish a PDU session corresponding to the slice. Illustratively, the PDU session establishment request message carries the nsai of the slice corresponding to the IP triplet or App Id.

And S304c, the core network sends a PDU session establishment success message to the CPE.

The core network establishes a PDU session of a slice corresponding to the nsai based on the received PDU session establishment request message, and returns a PDU session establishment success message to the CPE after the PDU session is successfully established.

It should be noted that, the specific details of the PDU session establishment procedure may refer to the PDU session establishment procedure specified in the existing standard, and will not be described in detail in this application.

Specifically, after receiving the PDU session establishment success message, the CPE determines that the PDU session is successfully established, and binds the data stream corresponding to the IP triplet with the PDU session.

In another example, if the CPE detects that the PDU session of 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 procedure.

Optionally, after receiving the data packet 1, the core network may reply the data packet 2 to the UE through the CPE. Specifically, referring to fig. 7, after the core network receives the data packet 1, the interaction between the UE, the CPE and the core network specifically further includes the following steps:

the core network sends data packet 2 to the CPE S305.

Illustratively, the core network may generate a data packet 2 based on the data packet 1 after receiving the data packet 1, and then transmit the data packet 2 to the CPE.

Alternatively, the core network may receive a data packet sent by another UE or server. The core network parses the data packet and encapsulates it into data packet 2, which is then sent to the CPE.

It will be appreciated that the embodiments of the present application do not limit how the core network generates the data packet 2 or obtains the data packet 2.

S306, the CPE sends the data packet 2 to the UE.

Illustratively, after receiving the data packet 2 sent by the core network, the CPE may parse the data packet 2 to determine a destination receiving device, e.g., UE, of the data packet 2. The CPE may send the data packet 2 to the intended receiving device, i.e. UE.

The downlink data transmission flows of the UE, CPE and core network may be described in the existing standards, and will not be described in detail herein.

The procedure shown in fig. 7 is based on a service feature (which may include, but is not limited to, one or more of App Id, IP triplet, DNN, FQDN) indicated by the urs issued by the core network, and if the verification is successful, the CPE is allowed to route data to the slicing network. In some scenarios, a user may open different network services to experience differentiated network services. However, the CPE cannot associate the service opened by the user with the slice, and can only determine the slice to which the data sent by the user terminal matches through the urs. However, the slice determined according to the urs may not be consistent with the slice corresponding to the service opened by the user, and thus, differentiated network services cannot be provided for the user. 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. Then the CPE should route the data onto the low latency slice when the user a's terminal sends the data to the core network through the CPE. However, if the CPE determines that the slice corresponding to the data transmitted by the terminal of the user a is a normal slice only according to the urs. User a cannot experience low-latency web services.

The embodiment of the application provides a slice selection method, and CPE can correlate network service of UE with slices. The CPE may route data sent by the UE to a slice associated with the UE's network traffic based on the UE's network traffic. In this way, the CPE may provide differentiated network services to different UEs.

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

Fig. 9 exemplarily illustrates a slice selection method provided in an embodiment of the present application. As shown in fig. 9, a slice selection method provided in an embodiment of the present application may include the following steps:

s401, the CPE200 accesses the core network 300.

In some examples, the CPE200 accessing the core network 300 may include the steps of:

1. a modem (modem) module 2003 in the CPE200 initiates registration with the core network 300.

Here, reference may be made to the description in step S101, and a detailed description is omitted here.

2. The core network 300 may send the bsp and subscription information of the CPE200 to the CPE 200.

Illustratively, the core network 300 may send the urs and subscription information of the CPE200 to the modem module 2003 of the CPE 200. CPE200 may sign up for one or more network services to an operator. For example, the types of network services that may be provided at an operator include: one or more of a large bandwidth high priority service, a large bandwidth medium priority service, a large bandwidth low priority service, a directional service, a low latency service, and the like.

It will be appreciated that the classification of network traffic at different operators may be different, as may the type and name of network traffic. The embodiment of the present application does not limit the type and name of network service that the CPE200 can sign up for.

In the embodiment of the application, the directional service may be a network service provided by an operator for a specific service of a certain company. An operator may provide one or more directional slices that provide network services only for that particular service, i.e., only the UE100 sends data for that particular service that can be routed to the slices provided by the operator for that particular service, and data for other services cannot be routed to the slices provided by the operator for that particular service. For example, an operator providing network services for a certain game may be referred to as a directional service. The network service provided by the operator for coal mine operation may also be referred to as a directional service. The network services provided by an operator for a grid company may also be referred to as directional services. It can be appreciated that the embodiments of the present application are not limited to specific directional traffic.

In the embodiment of the present application, a network service may correspond to a slice. Different network traffic corresponds to different slices. The CPE200 may sign up for one or more network services to the operator may mean that the CPE200 opens rights to use one or more slices at the operator. In this embodiment, the CPE200 having the right to use the first slice may mean that the CPE200 may route data to the first slice, and may transmit the data to the core network through the first slice.

The CPE200 may parse the urs issued by the core network, and the CPE200 may parse the slice information. The slice information may indicate the slices that can be used in CPE200, as well as the slices that can be provided to UE 100.

Illustratively, referring to fig. 10, the cpe200 parsing the urs may specifically include the steps of:

s4011, the CPE200 traverses the terminal routing policy urs list by priority.

Illustratively, the CPE200 may traverse the urs list by priority. A plurality of urs rules may be in the list of urs. Optionally, the preceding urs rule of the urs list has a higher priority than the following urs rule.

S4012, the CPE200 determines if there is a next priority urs in the list of urs. If so, step S4013 is performed, and if not, step S40111 is performed.

It can be appreciated that the CPE200 may first match the highest priority urs in the urs list, if the highest priority urs match successfully, step S4012 is not executed, and if the highest priority urs match unsuccessfully, the next priority urs are matched.

S4013, the CPE200 performs traffic descriptor Traffic descriptor matching.

The CPE200 determines whether the service indicated by the service descriptor of the urs rule includes the service of the CPE200 or whether the service indicated by the service descriptor of the urs rule is identical to the service of the CPE 200.

S4014, the CPE200 determines Traffic descriptor whether the matching is successful, if so, executes step S4015, and if not, executes step S4012.

If the CPE200 determines Traffic descriptor that the indicated traffic includes traffic of the CPE200 or is the same as the traffic of the CPE200, the CPE200 determines Traffic descriptor if the match was successful. The CPE200 performs step S4015. Otherwise, the CPE200 continues to execute S4012, querying the next urs rule.

S4015, the CPE200 traverses the routing description list Route selection descriptor list.

The CPE200 traverses each S-nsai in the routing description list Route selection descriptor list on a piece-by-piece basis.

S4016, the CPE200 determines whether S-nsai is included in the allowed nsai, if so, performs step S4017, and if not, performs step S4012.

The CPE200 determines if each S-nsai in the routing description list Route selection descriptor list is contained in an allowed nsai. If yes, step S4017 is performed. If not, then step S4012 is performed, i.e., traversing the next URSP rule.

The CPE200 selects S-nsai as the PDU session activation parameter S4017.

S4018, the CPE200 determines that DNN & nsai has been activated successfully, if yes, then step S4019 is performed, and if no, then step S40110 is performed.

S4019, the CPE200 determines that the PDU session need not be re-activated.

The CPE200 activates PDU session with S-nsai S40110.

S40111, the CPE200 determines that the slice selection fails.

If the CPE200 does not traverse to the next highest priority urs, the CPE200 determines that the slice selection failed.

It can be appreciated that the specific procedure for the CPE200 to parse the urs may refer to descriptions in the existing standards, and will not be described herein.

3. The modem203 in the CPE200 may report slice information to a slice application module in the CPE 200.

4. The slice application module in CPE200 records slice information.

5. The slice application module in CPE200 initiates the dialing.

6. The modem203 in the CPE200 establishes PDU session for multiple slices based on the dial initiated by the slice application module.

The specific procedure of the CPE200 dialing and establishing the PDU session of the slice may refer to the existing standard, and will not be described herein.

S402, the UE100 accesses the CPE200.

The specific procedure of the UE100 accessing the CPE200 may refer to descriptions in S201-S204, and will not be repeated here.

In the embodiment of the present application, before or after the UE100 performs step S402, the UE100 may perform identity authentication and sign up for network services. The CPE200 may acquire the identification information of the UE100 and the network service information subscribed to by the UE100 through identity authentication of the UE 100.

Optionally, the UE100 may perform identity authentication and sign up for network services through Portal (web Portal or Portal) authentication.

Illustratively, the user may turn on Wi-Fi in the UE100, and when the CPE200 is connected, the UE100 may display a web page for identity authentication, and the user may input a user name and a password in the web page for identity card. The identity authentication at the UE100 is that the CPE200 may obtain the MAC address of the UE 100.

Further, the UE100 may sign up for network services that one or more CPEs are capable of providing. Fig. 11 illustrates a scenario of a network service provided by a terminal at a subscribed CPE, for example. As shown in fig. 11, the terminal 1 may sign up for a high-bandwidth high-priority service provided by the CPE. The terminal 2 may sign up for the large bandwidth medium priority service provided by the CPE. The terminal 3 may sign up for the large bandwidth low priority service provided by the CPE. The terminal 4 may sign up for low-latency services provided by the CPE. The terminal 5 may sign up for multiple slice services (i.e. multiple ones of the services large bandwidth high priority service, large bandwidth medium priority service, large bandwidth low priority service, low latency service, directional service, etc.) provided by the CPE. The terminal 6 may sign up for the directional service provided by the CPE.

CPE200 may pre-configure the names of the slices that the CPE is able to provide and the CPE may associate (or refer to as a binding) the names of the slices with the slice IDs. The UE signing up for the network service may mean that, after the UE selects one or more slice names that the CPE can provide in the CPE, the CPE associates the identifier of the UE with a slice corresponding to the slice name selected by the UE. Thus, the UE has the right to use the slice.

In the embodiment of the present application, the UE having the authority to use the slice may mean that data sent by the UE may be transmitted to the core network (or referred to as a network side) through the slice.

Alternatively, there may be an administrator user in the CPE, and a terminal connected to the CPE through a USB or a network port may be referred to as an administrator user, for example. The embodiments of the present application are not limited to administrator users. Illustratively, the management user may configure the names of the slices that CPE200 is able to provide. And, the administrator user may sign up for other UEs for network services that CPE200 is capable of providing.

It will be appreciated that the SIM card in CPE200 may sign up for one or more network services at the operator. The network service that the CPE200 can provide to the UE100 is network service that the SIM card in the CPE200 has subscribed to at the operator. For example, if a SIM card in the CPE200 signs up for low latency service at the operator, the CPE200 may provide low latency service to the UE 100. The UE100 may sign up for the multi-slice service only when the SIM card in the CPE200 signs up for the multiple network services at the operator.

Further optionally, the UE100 may sign up for network services that the CPE200 can provide by logging in to a web page. Alternatively, the UE100 may sign up for network services that the CPE200 can provide by an administrator user. The embodiment of the present application does not limit the manner in which the UE100 signs up for the network service.

Illustratively, fig. 12 shows a user interface schematic for signing up for network traffic. As shown in fig. 12, the user interface 1200 may be used to select and sign up for network traffic for the UE 100. Control 1201, control 1202, options box 1203, input box 1204, control 1205, and control 1206 may be included in user interface 1200. After the user clicks control 1201 and control 1202, an option box 1203 may be displayed in user interface 1200. The user may select a network service in the option box and input a user name (e.g., a phone number 131) in the input box 1204. After the user clicks the control 1205, the UE with the mobile phone number 131 may successfully sign up for the network service selected by the user in the option box 1203. Alternatively, the user may click control 1206 to view tariff notes corresponding to different network services, or to the network service selected by the user.

It will be appreciated that the UE100 may display the user interface 1200 in which the user may sign up for the UE100 for network services.

Optionally, the user interface 1200 may also be displayed in the UE of the administrator user of the CPE 200. An administrator user may sign up for network services for different UEs in the user interface 1200.

Further, after the UE signs up for the network service provided by the CPE200, the CPE200 may associate (or referred to as binding) the UE with a slice corresponding to the network service that the UE signs up for.

Alternatively, the CPE200 may record in a database the slice with which the UE's identity is associated or the ID of the slice. The identity of the UE may be the MAC address of the UE or the mobile phone number of the UE, which is not limited herein.

Illustratively, upon portal authentication of the UE100, the CPE200 may save the UE's username and may obtain the MAC address of the UE 200. The CPE200 may save the user name and MAC address of the UE100 into a portal information database.

Illustratively, after the UE100 signs up for one or more network services that can be provided in the CPE200, the CPE may establish an association between the user name of the UE100 and a slice ID corresponding to the network service that the UE100 signs up for, and store the association in the user database. The CPE200 may update the user database with the user name and the MAC address of the UE100 stored in the portal information database, and the CPE200 may establish an association between the user name and the MAC address of the UE100 and the slice ID corresponding to the network service subscribed by the UE100, and store the association in the user database.

It is to be appreciated that different UEs may sign up for the same network service. One slice ID in the CPE200 may establish an association with the user names of a plurality of UEs.

Illustratively, in one possible implementation, after the CPE establishes an association between the user name of the UE100 and the slice ID corresponding to the network service subscribed to by the UE100, the CPE200 may generate the routing rule of the UE 100. The routing rule is used to instruct the CPE200 to transmit the data of the UE100 to the core network through the slice corresponding to the network service subscribed by the UE100 based on which PDU session.

S403, the UE100 sends the data packet R1 to the CPE 200.

The UE100 may send a data packet R1 to the CPE 200. The data packet R1 may be a service request. The packet R1 may carry an IP triplet, and the format of the packet may be as shown in fig. 8A, for example. Alternatively, the data packet may also carry an App Id, and the format of the data packet may be as shown in fig. 8B, for example. Optionally, the data packet R1 may also carry a mobile phone number of the UE 100. The specific format of the data packet is not limited herein.

Illustratively, in one possible implementation, the UE100 sending the data packet R1 to the CPE200 includes: s403a, the UE100 sends the data packet R1 to the Wi-Fi module 2001 of the CPE 200; s403b, the Wi-Fi module in the CPE200 sends the data packet R1 to the routing module 2002 in the CPE 200.

S404, the CPE200 determines a network service type A1 corresponding to the data packet R1.

CPE200 may determine the network traffic type A1 to which packet R1 corresponds. Specifically, the CPE200 may first determine the network service subscribed to by the UE100 that sent the data packet R1. If the network service subscribed by the UE100 is only one network service and is not a directional service, the CPE200 may determine that the network service type A1 corresponding to the data packet R1 is the network service subscribed by the UE 200.

Optionally, in one possible implementation, if the network service subscribed to by the network service type subscribed to by the UE100 is a directional service. The CPE200 needs to match the service characteristics (e.g., the IP triplet, or the IP triplet and App Id, etc.) carried in the data packet R1 with the service characteristics corresponding to the directional service slice in the urs p, and if the matching is successful, the CPE200 determines that the network service type A1 corresponding to the data packet R1 is the directional service. If the matching is unsuccessful, the CPE200 determines that the network service A1 corresponding to the data packet R1 is a normal service, i.e. the CPE200 may route the data packet R1 to a default slice.

Optionally, in one possible implementation manner, if the network service subscribed by the network service type subscribed by the UE100 is a multi-slice service, that is, includes a plurality of network services, the CPE200 needs to match the service characteristics carried in the data packet R1 with the service characteristics corresponding to the slices associated with the plurality of network services in the urs respectively. If the service features carried in the data packet R1 are successfully matched with the service features corresponding to the associated slices of the network service A2 in the multiple network services in the urs, the CPE200 determines that the network service type A1 corresponding to the data packet R1 is the network service A2. If the matching is unsuccessful, the CPE200 determines that the network service A1 corresponding to the data packet R1 is a normal service, i.e. the CPE200 may route the data packet R1 to a default slice. Alternatively, in one possible implementation, if the match is unsuccessful, the CPE200 may route the data packet R1 to a large bandwidth high priority traffic slice. In this way, the user experience may be improved.

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

For example, as shown in fig. 13, taking a network service that the CPE200 signs up with an operator for five network service types, i.e., a high-bandwidth high-priority service, a medium-bandwidth priority service, a high-bandwidth low-priority service, a low-latency service, and a directional service, the CPE200 may determine that the network service type A1 corresponding to the transmission data packet R1 includes:

s4041, the CPE200 determines the network service type subscribed to by the UE100 that sent the data packet R1.

The network traffic type subscribed to by the UE100 may be one or more of a high priority traffic with a large bandwidth, a medium priority traffic with a large bandwidth, a low latency traffic, and a directional traffic.

When the network service type subscribed by the UE100 may be any one or more of a high priority service with a large bandwidth, a medium priority service with a large bandwidth, a low latency service, and a directional service, determining the network service type A1 corresponding to the data packet R1 based on the network service subscribed by the UE includes the following cases:

Case 1: UE100 signs up only for large bandwidth high priority traffic

S4042a, the CPE200 determines that the UE100 transmitting the data packet R1 signs up for the high bandwidth high priority service.

Illustratively, the CPE200 may determine that the UE100 signs up for the high-bandwidth high-priority service based on the MAC address of the UE100 or the mobile phone number of the UE100 carried in the data packet R1.

S4044a, the CPE200 determines that the network traffic type A1 is a high bandwidth high priority traffic.

CPE200 may then determine that network traffic type A1 is a large bandwidth high priority traffic.

Case 2: UE100 signs up only for large bandwidth medium priority traffic

S4042b, the CPE200 determines that the UE100 transmitting the data packet R1 signs up for the large bandwidth medium priority service.

Illustratively, the CPE200 may determine that the UE100 signs up for the large bandwidth medium priority service based on the MAC address of the UE100 or the mobile phone number of the UE100 carried in the data packet R1.

S4044b, the CPE200 determines that the network traffic type A1 is a high bandwidth high priority traffic.

Case 3: UE100 signs up only for large bandwidth low priority traffic

S4042c, the CPE200 determines that the UE100 transmitting the data packet R1 signs up for the high bandwidth low priority service.

Illustratively, the CPE200 may determine that the UE100 signs up for the high bandwidth low priority service based on the MAC address of the UE100 or the handset number of the UE100 carried in the data packet R1.

S4044c, the CPE200 determines that the network traffic type A1 is a large bandwidth low priority traffic.

Case 4: UE100 signs up for directional traffic only

S4042d, the CPE200 determines that the UE100 transmitting the data packet R1 signs up for the directional service.

Illustratively, the CPE200 may determine that the UE100 signs up for the directional service based on the MAC address of the UE100 or the mobile phone number of the UE100 carried in the data packet R1.

S4043d, the CPE200 matches the traffic characteristics in the data packet R1 with the characteristics of the targeted traffic in the urs.

S4044d, if the matching is successful, the CPE200 determines that the network traffic type A1 is a directional traffic.

It will be appreciated that UE100 is subscribed to the directional service, and that only certain applications in UE100 correspond to the directional service, and none of the other applications are the directional service. The CPE200 needs to match the traffic characteristics in the data packet R1 with the characteristics of the targeted traffic in the urs to determine whether the data packet R1 is sent by the particular application to which the targeted traffic in the UE100 corresponds. If the match is successful, the CPE200 determines that the network traffic type A1 is a targeted traffic. If the match is unsuccessful, the CPE200 determines that the network traffic type A1 is not targeted traffic.

Case 5: UE100 signs up only for low latency services

S4042e, the CPE200 determines that the UE100 transmitting the data packet R1 signs up for the low latency service.

S4044e, the CPE200 determines that the network traffic type A1 is a low latency traffic.

Case 6: UE100 signs up for multi-slice service

S4042f, the CPE200 determines that the UE100 transmitting the data packet R1 signs up for the multi-slice service.

Illustratively, the CPE200 may determine that the UE100 signs up for the multi-slice service based on the MAC address of the UE100 or the mobile phone number of the UE100 carried in the data packet R1. I.e. UE100 has subscribed to multiple network services among a large bandwidth high priority service, a low latency service, a directional service.

S4043f, the CPE200 determines the network traffic type A1 corresponding to the data packet R1 based on the traffic characteristics in the data packet R1 and the urs.

The CPE200 may match the traffic characteristics in the data packet R1 with the traffic characteristics corresponding to each of the network traffic in the multislice traffic in the urs, respectively. If the service characteristics in the data packet R1 are successfully matched with the service characteristics of the low-delay service in the multi-slice service, the CPE200 may determine that the network service type A1 of the data packet R1 is the low-delay service. If the service characteristics in the data packet R1 are successfully matched with the service characteristics of the directional service in the multi-slice service, the CPE200 may determine that the network service type A1 of the data packet R1 is the directional service. If the service characteristics in the data packet R1 are successfully matched with the service characteristics of the high-bandwidth and high-priority service in the multi-slice service, the CPE200 may determine that the network service type A1 of the data packet R1 is the high-bandwidth and high-priority service.

In one possible implementation, if the traffic characteristics of the data packet R1 are not matched with the traffic characteristics of the directional traffic, the traffic characteristics of the low-latency traffic, and the high-bandwidth high-priority traffic, the CPE200 determines that the network traffic A1 corresponding to the data packet R1 is a normal traffic, i.e., the CPE200 may route the data packet R1 to a default slice.

Optionally, in one possible implementation manner, if the traffic characteristics of the data packet R1 do not match the traffic characteristics of the directional traffic, the traffic characteristics of the low latency traffic, and the high priority traffic with large bandwidth, the CPE200 may also determine that the network traffic A1 corresponding to the data packet R1 is the high priority traffic with large bandwidth, that is, the CPE200 may route the data packet R1 to the slice with large bandwidth and high priority traffic. In this way, the user experience may be improved.

It will be appreciated that the data transmission rate of the default slice is lower than the data transmission rate of the above-described directional slice, low latency traffic slice, large bandwidth high priority slice, large bandwidth medium priority slice, large bandwidth low priority slice, etc. The data transmission rate of the large bandwidth high priority slices is higher than the data transmission rate of the large bandwidth medium priority slices. The data transmission rate of the large bandwidth medium priority slice is higher than the data transmission rate of the large bandwidth low priority slice. S405, the CPE200 routes the data packet R1 to the slice S1 corresponding to the network traffic type A1.

CPE200 may route data packet R1 to slice S1 corresponding to network traffic type A1.

For example, referring to fig. 13, case 1: s4045a, in case the network traffic type A1 is a large bandwidth high priority traffic, the CPE200 may route the data packet R1 to the large bandwidth high priority traffic slice. Case 2: s4045b, in case the network traffic type A1 is a large bandwidth medium priority traffic, the CPE200 may route the data packet R1 to the large bandwidth medium priority traffic slice. Case 3: s4045c, in case the network traffic type A1 is a large bandwidth low priority traffic, the CPE200 may route the data packet R1 to the large bandwidth low priority traffic slice. Case 4: s4045d, in case the network traffic type A1 is low latency traffic, the CPE200 may route the data packet R1 to the directional traffic slice. Case 5: s4045e, in case the network traffic type A1 is directional traffic, the CPE200 may route the data packet R1 to a low latency traffic slice.

Optionally, when the CPE200 parses that the App Id is carried in the data packet R1, the CPE200 may repackage the data packet R1, where the repackaged data packet R1 does not include the App Id to avoid that the core network side cannot identify the App Id in the optional field, which leads to a compatibility problem.

It will be appreciated that in one possible implementation, when the CPE200 determines that the UE100 is not subscribed to the network service provided by the CPE200, the CPE200 may route the data packet R1 to a default slice.

Alternatively, in one possible implementation, when the CPE200 determines that the UE100 is not subscribed to the network service provided by the CPE200, the CPE200 may not send the data packet R1 to the core network 300. That is, the CPE200 does not provide network services for the UE 100.

Optionally, the core network 300 may also send a service response R2 based on the data packet R1. That is, optionally, a slice selection method provided in the embodiments of the present application may further include step S406 to step S408a, and step S408b.

The core network 300 sends a packet R2 to the CPE 200S 406.

The core network 300 may transmit the data packet R2 to the UE100 through the CPE200 based on the data packet R1 transmitted by the UE 100.

In S407, the CPE200 determines whether the packet R2 corresponds to a low latency traffic slice. If yes, step S408b is executed, and if no, step S408a is executed.

CPE200 may determine if packet R2 corresponds to a low latency slice. When CPE200 is determining that packet R1 corresponds to a low latency traffic slice, the traffic characteristics (e.g., IP triplets, or IP triplets and App Id) of packet R1 may be added to the characteristics table. When the traffic characteristics of the traffic response R2 match the traffic characteristics in the characteristics table, the CPE200 may determine that the traffic response corresponds to a low latency slice. Otherwise, the data packet R2 does not correspond to a low latency traffic slice.

It will be appreciated that, typically, the UE100 routes data (e.g., packet R1) sent upstream to a low latency traffic slice, and then receives data (e.g., packet R2) downstream.

S408a, if the data packet R2 does not correspond to the low latency traffic slice, the data packet R2 is sent to the UE100.

And S408b, if the data packet R2 corresponds to the low-delay service slice, the data packet R2 is sent to the UE100 in an acceleration way.

If the packet R2 corresponds to a low latency traffic slice, the CPE200 accelerates the Wi-Fi link that transmits the packet R2 downstream. Illustratively, if the data packet R2 is sent to the CPE200 through a low latency traffic slice, the CPE200 may determine that the data packet R2 corresponds to the low latency traffic slice. The CPE200 may then accelerate the Wi-Fi link that transmits the data packet R2 through a higame module in the CPE 200.

In this way, the CPE can associate network traffic subscribed to by the UE with the slice. The CPE200 may then route the data sent by the UEs subscribed to different types of network traffic onto different slices. For example, if UE1 signs a low latency traffic slice, if UE2 signs a high bandwidth high priority traffic slice, then CPE200 may route data sent by application a in UE1 to the low latency traffic slice, and CPE200 may route data sent by application a in UE2 to the high bandwidth high priority traffic slice. In this way, the CPE200 can provide differentiated network services to the user.

In some scenarios, the administrator user may also set a virtual Wi-Fi access point in the CPE200 and set the password of the virtual Wi-Fi access point. The administrator user may also associate information of the virtual Wi-Fi access point (e.g., the virtual Wi-Fi access point name and password) with a slice. Data transmitted by UEs connected to the virtual Wi-Fi access point may all be routed to the same slice (i.e., one slice associated with the information of the virtual Wi-Fi access point). Thus, each user can be prevented from needing to independently operate to bind slices or pay access, and user experience is improved.

Illustratively, take outdoor CPE multi-player game play as an example. The administrator user may set the virtual Wi-Fi access point of the CPE 200. For example, the virtual Wi-Fi access point is xx game slice Wi-Fi and sets a Wi-Fi password. The administrator user may also associate xx game slices Wi-Fi with xx game slices, it being understood that CPE signs up for many slices, including xx game slices. And the UE accessed through the xx game slice Wi-Fi can perform xx game slice service. Alternatively, the CPE may associate and store in a database the MAC address of the UE accessing xx game slice Wi-Fi with xx game slice.

Thus, for multi-player game play, the scenes such as outdoor group play of the group and the like also reduce the process of user authentication.

In the scenario where the CPE200 is provided with a virtual Wi-Fi connection point, a slice selection method provided in the embodiment of the present application may include:

1, CPE200 accesses the core network. The CPE200 is provided with a virtual Wi-Fi access point and associates access information of the Wi-Fi access point with the slice S2.

Here, the procedure of accessing the core network by the CPE200 may refer to the description in step S401, which is not repeated here.

The CPE200 is provided with a virtual Wi-Fi access point and associates access information of the virtual Wi-Fi access point with the slice S2.

2, ue100 accesses CPE200.

Here, reference may be made to the description in step S402 described above, and the description is not repeated here.

3, ue100 sends a data packet R1 to CPE200.

Here, reference may be made to the description in step S403 described above.

4, CPE200 judges whether UE100 accesses the virtual Wi-Fi access point, if yes, route the data packet R1 to the slice S2 correlated with the virtual Wi-Fi access point; if not, the CPE200 may perform steps S404-S405 described above.

In the embodiment of the present application, the CPE200 or the CPE may be referred to as a first terminal. UE, or UE100, UE1, UE2 may be referred to as a second terminal. The data packet R1 may be referred to as a first data packet and the data packet R2 may be referred to as a second data packet. The network in which slice S1 is located may be referred to as a first slice network.

The present embodiment may divide the functional modules of the CPE200 according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules described above may be implemented in hardware. It should be noted that, in this embodiment, the division of the modules is schematic, only one logic function is divided, and another division manner may be implemented in actual implementation.

Fig. 14 shows a schematic structural diagram of an apparatus 1400. The apparatus 1400 may include: wi-Fi module 2001, routing module 2002, modem module 2003, slice application module 2004, UI module 2005. Wherein:

the Wi-Fi module 2001 may be configured to acquire and store the MAC address of the UE accessed through Wi-Fi in a database, and the Wi-Fi module 2001 may also send the stored MAC address of the accessed UE to the routing module 2002.

Optionally, wi-Fi module 2001 may also be used to accelerate downstream low latency traffic.

Optionally, referring to fig. 11, the Wi-Fi module 2001 may further include a Wi-Fi network card routing policy management module, a Wi-Fi packet management module. The Wi-Fi network card routing policy management module can be used for managing and saving URSPs issued by the core network. The Wi-Fi packet management module accelerates the data transmitted downstream to CPE200 by the low latency traffic slice.

The routing module 2002 may be configured to associate the MAC address of the UE with the network traffic subscribed to by the UE, and the slice.

The routing module 2002 may also be configured to construct an end-to-end data path according to the association relationship between the MAC address of the UE and the network service subscribed by the UE, the slice, and the routing rule of the slice.

The routing module 2002 may also be configured to be responsible for refreshing dynamic routing rules based on network status.

Routing module 2002 may also be used to refresh the database holding the MAC address of the UE, while refreshing the routing rules, in the event of a change in Portal information authentication of UI module 2005 or a change in configuration in UI module 2005. For example, the routing module 2002 refreshes the routing rules in case of a MAC address change after re-access, or a subscriber subscription slice change, a subscriber cancellation subscription, etc.

The routing module 2002 may also be used to perform the steps S404-S405 described above, which are not described herein.

The modem module 2003 may be configured to receive the urs transmitted by the core network and report the urs information to the slice application module 2004.

The modem module 2003 may also be used to perform the above steps S4011-S40111, which are not described here again.

The slice application module 2004 may be configured to initiate establishment of a multi-path slice session based on the urs information reported by the modem module 2003 and the allowed slices, the disallowed slice information, etc.

Slice application module 2004 may be used to report PDU session information to UI module 2005.

UI module 2005 can be used to display UI interfaces as well as provide user interfaces for Portal authentication by the user. UI module 2005 can also be used to configure association of UE with subscribed services, slices.

The UI module 2005 may be further configured to correlate the user name of the UE with the MAC address of the UE, store the association relationship between the user name and the MAC address of the UE in a database, and send the association relationship to the router module 2002.

The apparatus 1400 may be the CPE200 in the above-described embodiment.

In another example, fig. 15 shows a schematic structural diagram of an apparatus 1500, the apparatus 1500 may include: a transceiver unit 1501. The transceiver unit 1501 may be configured to receive first routing policy urs p information of a terminal device from a network side, where the first urs p information includes an application identifier App Id and first slice parameter information, where the App Id is used to identify an application, and the first slice parameter information is used to indicate a first slice network; the apparatus 1500 interacts data with the network side over a cellular network.

The transceiver 1501 may also be configured to receive a data packet sent by the UE through the Wi-Fi network. The data packet may carry an App Id of an application in the UE that transmits the data packet.

The transceiver 1501 may be further configured to transmit the data packet to the network side through the first slice network when determining a first slice corresponding to the network service subscribed by the UE sending the data packet.

The transceiver 1501 may be further configured to transmit the data packet to the network side through the first slicing network indicated by the first slicing parameter information when the App Id in the data packet is the same as the App Id in the first urs information.

On the basis of the above method embodiment, the first urs information further includes other service feature information, where the other service feature information includes at least one of: IP triplet information, data network name DNN information, destination full size domain name FQDN information.

The transceiver 1501 is further configured to receive second urs p information from the network side, where the second urs p information includes App Id, other service feature information, and second slice parameter information, where the second slice parameter information is used to indicate a second slice network, and the first slice parameter information is different from the second slice parameter information.

The apparatus 1500 further comprises a processing unit 1502, configured to update the second urs information when other service feature information in the second urs information is different from other service feature information in the first urs information, and the other service feature information in the updated second urs information is the same as the other service feature information in the first urs information.

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

The processing unit 1502 may be configured to, when determining that the network service subscribed by the UE is a directional service, match a service feature in a data packet sent by the UE with a service feature of the directional service in the urs, and if the matching is successful, determine that a network service type corresponding to the data packet sent by the UE is the directional service.

On the basis of the above method embodiment, the transceiver 1501 is further configured to transmit, when it is determined that the UE does not sign up for the service, or the UE signs up for the directional service, the data packet to the network side through the non-slice network or the third slice network when the service characteristics of the data packet sent by the UE are not matched with the service characteristics in the urs, where the third slice network may be a default slice.

On the basis of the above method embodiment, the transceiver 1501 is further configured to transmit data of the first application on the first chip network based on the PDU session if a protocol data unit PUD session corresponding to the first chip network has been established between the second electronic device and the network side.

On the basis of the above method embodiment, the processing unit 1502 may be configured to, in a case where a protocol data unit PUD session corresponding to the first slice network is not established between the apparatus 1500 and the network side, establish a PDU session corresponding to the first slice network with the network side based on slice parameter information; the transceiving unit 1501 may be configured to transmit the data packet over the first slice network based on the PDU session.

On the basis of the above method embodiment, the transceiver 1501 may be further configured to receive, from the network side, allowed network slice selection assistance information Allowed NSSAI, where Allowed NSSAI is used to indicate a slice network set that allows the apparatus 1500 to transmit data; the first slice network is included in a set of slice networks.

On the basis of the method embodiment, the App Id may be an application package name of the application.

The apparatus 1500 may be the CPE200 in the above-described embodiment.

In yet another example, fig. 16 illustrates a schematic structural diagram of an apparatus 1600, the apparatus 1600 comprising: a processing unit 1601 and a transceiver unit 1602, where the processing unit 1601 is configured to run an application for transmitting data packets. The transceiver unit 1602 is configured to send a data packet to the device 1500 through the Wi-Fi network, where the data packet may carry an App Id.

On the basis of the method embodiment, app Id is the application package name of the application.

The apparatus 1600 may be the UE100 in the above-described embodiments.

In yet another example, fig. 17 shows a schematic block diagram of an apparatus 1700 of an embodiment of the present application. The apparatus 1700 may include: the processor 1701 and transceiver/transceiving pin 1702, optionally, also include a memory 1703.

The various components of device 1700 are coupled together by bus 1704, where bus 1704 includes a power bus, control bus, and status signal bus in addition to the data bus. For clarity of illustration, however, the various buses are referred to in the figures as buses 1704.

Optionally, the memory 1703 may be used to store instructions in the foregoing method embodiments. The processor 1701 is operable to execute instructions in the memory 1703 and control the receive pins to receive signals and the transmit pins to transmit signals.

The apparatus 1700 may be the UE100 or CPE200 in the method embodiments described above. For example, when the apparatus is the CPE200 described above, the memory 1703 may also store the MAC address, the user name, and the like of the UE in the above embodiment as well as the association information between the network service subscribed to by the UE and the slice corresponding to the network service.

The apparatus 1700 may be a chip that may implement one of the slice selection methods described in the above embodiments.

All relevant contents of each step related to the above method embodiment may be cited to the functional description of the corresponding functional module, which is not described herein.

The present embodiment also provides a computer storage medium having stored therein computer instructions which, when executed on an electronic device, cause the electronic device to perform the above-described related method steps to implement a slice selection method according to the above-described embodiments.

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

In addition, embodiments of the present application also provide an apparatus, which may be specifically a chip, a component, or a module, and may include a processor and a memory connected to each other; the memory is configured to store computer-executable instructions, and when the apparatus is running, the processor may execute the computer-executable instructions stored in the memory, so that the chip performs a slice selection method in the above method embodiments.

The electronic device, the computer storage medium, the computer program product, or the chip provided in this embodiment are used to execute the corresponding methods provided above, so that the beneficial effects thereof can be referred to the beneficial effects in the corresponding methods provided above, and will not be described herein.

The above embodiments are merely for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

As used in the above embodiments, the term "when …" may be interpreted to mean "if …" or "after …" or "in response to determination …" or "in response to detection …" depending on the context. Similarly, the phrase "at the time of determination …" or "if detected (a stated condition or event)" may be interpreted to mean "if determined …" or "in response to determination …" or "at the time of detection (a stated condition or event)" or "in response to detection (a stated condition or event)" depending on the context.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may 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 may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk), etc.

Those of ordinary skill in the art will appreciate that implementing all or part of the above-described method embodiments may be accomplished by a computer program to instruct related hardware, the program may be stored in a computer readable storage medium, and the program may include the above-described method embodiments when executed. And the aforementioned storage medium includes: ROM or random access memory RAM, magnetic or optical disk, etc.

Claims

1. A method of slice selection, comprising:

the method comprises the steps that a first terminal receives a first data packet sent by a second terminal, the second terminal establishes communication connection with the first terminal through a wireless fidelity Wi-Fi network, and the first terminal establishes communication connection with a network side through a cellular network;

the first terminal determines one or more network services subscribed by the second terminal, and each network service in the one or more network services is associated with a slicing network;

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;

the first terminal transmits the first data packet to the network side through a first cut-off network associated with the first network service.

2. The method of claim 1, wherein the first terminal determining one or more network services subscribed to by the second terminal comprises:

the first terminal searches a first database of the first terminal for one or more network services associated with the first identifier based on the first identifier of the second terminal, the first database stores the identifiers of the one or more terminals and the one or more network services associated with the identifiers of the one or more terminals, and the identifiers of the one or more terminals comprise the first identifier;

the first terminal determines one or more network services subscribed by the second terminal.

3. The method according to any of claims 1 or 2, wherein before the first terminal receives the first data packet sent by the second terminal, the method further comprises:

the first terminal receives terminal routing strategy URSP information sent by the network side, wherein the URSP information comprises one or more piece of slice parameter information, the one or more piece of slice parameter information comprises first piece of slice parameter information, and the first piece of slice parameter information is used for indicating the first piece of slice network.

4. A method according to claim 3, wherein the first terminal determining one or more network services subscribed to by the second terminal comprises:

the first terminal determines that the network service subscribed by the second terminal is the first network service;

the first terminal determining that the network service type corresponding to the first data packet is a first network service of the one or more network services, including:

and the first terminal determines the network service type corresponding to the first data packet as the first network service.

5. The method according to claim 4, wherein, in the case that the first network service is a directional 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 service characteristics in the first data packet;

the first terminal matches the service characteristics with the service characteristics corresponding to the directional service in the URSP information;

and under the condition that the service characteristics are successfully matched with the service characteristics corresponding to the directional 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 of claim 2, wherein the first terminal determining one or more network services subscribed to by the second terminal comprises:

the first terminal determines a plurality of network services subscribed by the second terminal;

the first terminal determines that the network service type corresponding to the first data packet is a first network service in 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.

7. The method of claim 6, wherein the determining, by the first terminal, that the network service type corresponding to the first data packet is the first network service of 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 urs information, comprises:

the first terminal acquires service characteristics in the first data packet;

the first terminal respectively matches the service characteristics with the service characteristics corresponding to the network services in the URSP;

And under the condition that the service characteristics are successfully matched with the service characteristics corresponding to the first network service in the URSP, the first terminal determines that the network service type corresponding to the first data packet is the first network service.

8. The method of claim 2, wherein before the first terminal receives the first data packet sent by the second terminal, the method further comprises:

and the first terminal establishes an association relation between the first identifier of the second terminal and one or more network services in the second terminal based on the subscription information sent by the second terminal.

9. The method according to any of claims 1-8, wherein the first terminal transmitting the first data packet to the network side through a first cut-off network associated with the first network service, comprising:

and under the condition that a protocol data unit PDU session corresponding to the first slice network is 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 any of claims 1-8, wherein the first terminal transmitting the first data packet to the network side through a first cut-off network associated with the first network service, comprising:

The first terminal establishes a PDU session corresponding to the first slice network with the network side 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 of claim 1, wherein after the first terminal transmits the first data packet to the network side through a first chip network associated with the first network service, the method further comprises:

the first terminal receives a second data packet sent by the network side through the first chip network;

and in the case that the first slice network is a low-delay slice network, the first terminal sends the second data packet to the second terminal in an acceleration way.

12. The method according to any one of claims 1-11, further comprising:

the first terminal receives allowable network slice selection auxiliary information allowable NSSAI sent by the network side, wherein the allowable NSSAI is used for indicating a slice network set allowing the first terminal to transmit data; the first slicing network is included in the set of slicing networks.

13. The method according to any of claims 1-12, wherein the first identification comprises a user name of the second terminal, and/or a media storage control, MAC, address of the second terminal.

14. The method of claim 13, wherein the traffic characteristics of the first data packet include at least one of App Id, IP triplet information, data network name DNN information, destination full domain name FQDN information of the first application; the first application is an application for sending the first data packet in the second terminal.

15. The slice selection system is characterized by comprising a first terminal and a second terminal, wherein the second terminal establishes communication connection with the first terminal through a wireless fidelity Wi-Fi network, and the first terminal establishes communication connection with a network side through a cellular network;

the second terminal is used for sending a first data packet to the first terminal;

the first terminal is used for receiving a first data packet sent by the second terminal;

the first terminal is used for determining one or more network services subscribed by the second terminal, and each network service in the one or more network services is associated with a slicing network;

The first terminal is configured to determine that a network service type corresponding to the first data packet is a first network service of the one or more network services;

the first terminal is used for transmitting the first data packet to the network side through a first slice network associated with the first network service.

16. A communications device comprising one or more processors, one or more memories, and a transceiver; wherein the transceiver, the one or more memories are coupled to the one or more processors, the one or more memories for storing computer program code comprising computer instructions that, when executed by the one or more processors, cause the communications apparatus to perform the method of any of claims 1-14.

17. The communication device of claim 16, wherein the communication device is a first terminal.

18. A computer readable storage medium having instructions stored therein which, when run on a computer, cause the computer to perform the method of any of claims 1-14.

19. A chip or chip system for a first terminal, comprising processing circuitry and interface circuitry, the interface circuitry to receive code instructions and to transmit to the processing circuitry, the processing circuitry to execute the code instructions to perform the method of any of claims 1-14.

20. A computer program product which, when run on a computer, causes the computer to perform the method of any of claims 1-14.