CN118828776A - A routing scheduling method, network device and storage medium - Google Patents

Abstract

The application provides a routing scheduling method, network equipment and a storage medium, wherein the method comprises the following steps: acquiring equipment identification information of user equipment; determining the routing scheduling data of the service corresponding to the user equipment based on the equipment identification information; and carrying out routing scheduling on the service of the user equipment based on the routing scheduling data of the service corresponding to the user equipment.

Description

A routing scheduling method, network device and storage medium

Technical Field

The present application relates to the field of communication technology, and in particular to a routing scheduling method, a network device and a storage medium.

Background Art

In the related technology, when selecting routing data, the packet filter set (Packet Filter Set) of the packet header field used by the Quality of Service (QoS) of the fifth generation mobile communication technology (5G) or the application identification (Application Identification, APP ID), full qualified domain name (Full Qualified Domain Name, FQDN), Internet Protocol (Internet Protocol, IP) triplet used by the user terminal to determine the slice for the session is usually used.

However, whether it is the Packet Filter Set of the packet header field used by 5G QoS, or the APP ID, FQDN, IP triplet used by the user terminal to determine the slice for the session, these are mainly the attribute characteristics of the service application. They use the services running on the device to select 5G slices and 5G QoS, which reflects the differentiation dimension at the service level and is strongly related to the service attributes. It can be seen that in the related technology, when selecting routing data such as 5G slices and 5G QoS, the services running on the 5G access devices in the related technology are used for selection. The selection method is single. If it is used in some usage scenarios that do not pay attention to the service, it will lead to a low personalized differentiation dimension of network services and a poor application experience.

Summary of the invention

In view of this, the embodiments of the present application hope to provide a routing scheduling method, a network device and a storage medium, which can expand the way of routing selection, improve the personalized differentiation dimension of network services, and thus enhance the application experience.

The technical solution of the embodiment of the present application is implemented as follows:

In a first aspect, an embodiment of the present application provides a routing scheduling method, which is applied to a network device, and the method includes:

Obtain device identification information of the user's device;

Determine routing scheduling data for a service corresponding to the user equipment based on the equipment identification information;

Based on the route scheduling data of the service corresponding to the user equipment, route scheduling is performed on the service of the user equipment.

In a second aspect, an embodiment of the present application provides a routing scheduling method, which is applied to a network device, and the method includes:

Sending a user routing selection policy URSP table to a user equipment, wherein the URSP table at least reflects a correspondence between the device identification information of the user equipment and the corresponding subscribed routing data and/or routing policy data;

receiving subscription routing data and/or routing policy data corresponding to the device identification information of the user equipment and determined by using the URSP table and the device identification information and sent by the user equipment;

Based on the received subscription routing data and/or routing policy data corresponding to the device identification information of the user equipment, routing scheduling is performed on the service of the user equipment.

In a third aspect, an embodiment of the present application provides a network device, the network device comprising: a determination unit and a scheduling unit; wherein:

The determining unit is used to obtain device identification information of the user equipment; based on the device identification information, determine the routing scheduling data of the service corresponding to the user equipment; the scheduling unit is used to perform routing scheduling on the service of the user equipment based on the routing scheduling data of the service corresponding to the user equipment;

Alternatively, the determination unit is used to send a user routing selection policy URSP table to the user equipment, wherein the URSP table at least reflects the correspondence between the device identification information of the user equipment and the corresponding contracted routing data and/or routing policy data; receive the contracted routing data and/or routing policy data corresponding to the device identification information of the user equipment determined by using the URSP table and the device identification information, which are sent by the user equipment; and the scheduling unit is used to perform routing scheduling for the service of the user equipment based on the received contracted routing data and/or routing policy data corresponding to the device identification information of the user equipment.

In a fourth aspect, an embodiment of the present application provides a network device, the network device comprising: a processor and a memory; when the processor executes a running program stored in the memory, the above-mentioned routing scheduling method is implemented.

In a fourth aspect, an embodiment of the present application provides a storage medium on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned routing scheduling method is implemented.

The embodiment of the present application provides a routing scheduling method, a network device and a storage medium, the method comprising: obtaining device identification information of a user device; determining routing scheduling data of a service corresponding to the user device based on the device identification information; and performing routing scheduling on the service of the user device based on the routing scheduling data of the service corresponding to the user device. By adopting the above implementation scheme, in the process of routing scheduling, the network device can determine the routing scheduling data corresponding to the device identification information based on the device identification information through the received device identification information sent by the user device. Since the routing scheduling data is related to the device identification information, when the network device receives different device identification information, the selected routing scheduling data will also be different, and thus the corresponding routes can be matched for different device identification information. Moreover, since different user devices have unique device identification information, the method of matching routes using device identification information has less correlation with the attribute characteristics of the service itself. Therefore, in some application scenarios that do not pay attention to the service, the above method can be used to perform personalized routing scheduling for the services corresponding to different user devices, thereby improving the personalized differentiation dimension of 5G network services and providing a stronger application experience.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of an exemplary 5G network architecture;

FIG2 is a schematic diagram of an exemplary 5G network slicing;

FIG3 is a schematic diagram of an exemplary process of receiving and configuring a terminal user routing selection policy (User Equipment Route Selection Policy, URSP);

FIG4 is a schematic diagram showing an exemplary principle of classification and marking of user plane traffic and a mapping method of QoS flows and access network (AN) resources;

FIG5 is a schematic diagram of an exemplary 5G+ industrial Internet business data transmission system architecture;

FIG6 is a flow chart of a routing scheduling method provided in an embodiment of the present application;

FIG. 7 is a schematic diagram of a process of performing routing scheduling based on a device ID during a user equipment (UE) registration process provided by an embodiment of the present application;

FIG8 is a schematic diagram of a UE registration update process in a Third Generation Partnership Project (3GPP) provided in an embodiment of the present application;

FIG9 is a schematic diagram of a process of performing routing scheduling based on a device ID during a UE session establishment process provided by an embodiment of the present application;

FIG10 is a schematic diagram of a UE session establishment and update process in 3GPP provided in an embodiment of the present application;

FIG11 is a schematic diagram of a process for determining a QoS rule according to a device ID in uplink service data provided by an embodiment of the present application;

FIG12 is a schematic diagram of a process for determining QoS rules according to a device ID in downlink service data provided by an embodiment of the present application;

FIG13 is a second flow chart of a routing scheduling method provided in an embodiment of the present application;

FIG14 is a structural diagram 1 of a network device 1 provided in an embodiment of the present application;

FIG. 15 is a second structural diagram of a network device 1 provided in an embodiment of the present application.

DETAILED DESCRIPTION

In order to enable a more detailed understanding of the features and technical contents of the embodiments of the present application, the technical solution of the present application is further elaborated in detail below in combination with the drawings and specific embodiments of the specification. The attached drawings are for reference only and are not used to limit the embodiments of the present application.

Unless otherwise defined, all technical and scientific terms used in this application have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used in this application are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

In the following description, reference is made to "some embodiments", which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict. It should also be noted that the terms "first/second/third" involved in the embodiments of the present application are only used to distinguish similar objects and do not represent a specific ordering of the objects. It is understandable that "first/second/third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

In order to make the technical solutions of the embodiments of the present application clearer, the relevant technologies involved in the application scenarios of the 5G network industry are first introduced.

(1) 5G network architecture

The 5G network architecture determined in the 3GPP-related protocols of the technical specifications for network function virtualization and software-defined networking is shown in Figure 1. The system architecture includes end-to-end nodes or network elements, including 5G UE, access network equipment (R)AN, and user plane function (UPF).

The 5G control plane adopts a service-based architecture. The control plane network elements include the Authentication Server Function (AUSF), which can provide authentication-related functions; Access and Mobility Management Function (AMF); Session Management Function (SMF); Network Slice Selection Function (NSSF), which manages network slice-related information, such as selecting network slices for terminals; Network Exposure Function (NEF), which is responsible for opening the network function entity of the 5G core network capability to third parties or non-3GPP environments. It can be regarded as an agent, conversion point, or API aggregation point; Network Repository Function (NRF), which is responsible for network function service registration and status monitoring, etc., to achieve automatic management, selection and scalability of network function services, and allow each network function to discover other network functions; Policy Control function (PCF); Unified Database (UNDF); Management, UDM), which can complete functions such as user contract data management, authentication information generation, mobility management, short message routing, etc.; Data Network (DN), which can be a 5GC external data network (Internet, etc.) and Application Function (AF), which is similar to an application server, which interacts with other 5G core network control plane NFs and provides business services.

Among them, the N1 interface is the signaling plane interface between UE and AMF; the N2 interface is the signaling plane interface between (R)AN and AMF; the N3 interface is the interface between 5G(R)AN and UPF, which is mainly used to transmit the uplink and downlink user plane data between 5G(R)AN and UPF; the N4 interface is the interface between SMF and UPF, which is used to transmit the control plane information between SMF and UPF; the N6 interface is the interface between UPF and DN, which is used to transmit the uplink and downlink user data flows between UPF and DN; the N9 interface is the user plane interface between UPF and UPF, which is used to transmit the uplink user data flow and the downlink user data flow between UPFs.

(2) 5G network slicing

By dividing network resources into multiple network slices, 5G network slices can provide differentiated services for industries with different service requirements (e.g., latency, reliability, capacity, isolation, and other functions). 5G network slices can be shown in Figure 2. The operator network will not only serve information consumption services with "Best Effort transmission" as the communication requirement, but also meet production control services with "deterministic transmission" as the communication requirement. The operator network can allocate logically or physically isolated network resources for these services with different communication requirements. These network resources include not only the network functions of the 5G core network control plane and user plane, but also the resources of the wireless network and transmission network.

It should be noted that the relevant names involved in Figure 2 are explained as follows:

Massive Machine Type Communication (mMTC);

Enhance Mobile Broadband (eMBB)

Ultra Reliable & Low Latency Communication (URLLC);

Active Antenna Unit (AAU);

Distributed Unit (DU);

Centralized Unit (CU).

(3) Terminal Slice Selection

When the service flow of the terminal service application needs to use the communication service, the terminal initiates the protocol data unit (PDU) session establishment process for it. A PDU session refers to the process of communication between a UE and a DN. Based on the URSP rules, the terminal can specify the network slice identification information (Single Network Slice Selection Assistance Information, S-NSSAI) that it wants to use in the process of initiating the establishment of the PDU session, or the network can be responsible for specifying the network slice used by the PDU session. Generally, if the network application service flow needs to use a specific network slice, the operator should provide the corresponding network slice for the service flow in the URSP. Therefore, the terminal should carry the relevant S-NSSAI information in the process of establishing the PDU session to request the network to select the corresponding slice and provide the corresponding slice service for the network application service.

As shown in Figure 3, the process of receiving and configuring the terminal URSP is shown. The URSP is the core rule for configuring and managing slices for the terminal. The URSP is generated during the slice subscription and activation process and acts on the terminal in the slice service process to guide the terminal to place the service data on the corresponding slice according to the service characteristics TD. According to the requirements of mobile Internet applications for 5G network services, the mobile application provider signs a service level agreement (SLA) with the 5G network operator. The 5G network operator will provide network slice services that meet the SLA agreement for mobile Internet applications and create URSP.

For URSP, URSP is defined in the 3GPP specification to describe the association between service flows from business applications and slices. As shown in Table 1, Table 1 is an example of URSP rules, in which the routing description is used to describe the slice S-NSSAI and other communication routing characteristics used by the service flow that conforms to the service flow description. The routing descriptor is shown in Table 2 below. TD is a key attribute to achieve diversification and customization of slice services. TD provides different service granularities. The appropriate TD should be flexibly selected according to diversified business needs (point-line-tube). TD mainly reflects the attribute characteristics of mobile Internet applications. The current TD defined by 3GPP mainly includes APP ID, FQDN, IP triplet and data network name (DataNetwork Name, DNN).

Table 1 URSP rules

Table 2 Routing Descriptor

(4) 5G QoS

The control of 5G service quality is not based on the bearer strategy, but is implemented at the QoS flow level. Each QoS flow can be classified and marked by the QoS Flow Identifier (QFI). Different PDU sessions can be distinguished by their QoS flows. In other words, the QoS flow is the smallest granularity of distinction in the PDU session. The same PDU session can contain up to 64 QoS flows with different QFIs. However, the same QFI can be reused in different PDU sessions. User data with the same QFI has the same processing method when forwarding. The QoS flow is controlled by the SMF. On the access network side, the SMF can provide it with QoS configuration through the AMF, or it can be preset. On the UE side, the QoS rules required for uplink transmission can be provided by the SMF during the establishment or modification of the PDU session, or can be derived through the reflective QoS mechanism. On the UPF side, its packet detection rules (Packet Detection Rules, PDR) are configured by the SMF. In the 5G system, due to the differences in traffic, latency, etc. among various services, the types of QoS flows are divided into three categories:

The first category is the Guaranteed Bit Rate (GBR) QoS flow. The bit rate of this type of GBR QoS flow will not be affected by network resources.

The second type is the Non-Guaranteed Bit Rate (Non-GBR) QoS flow. This type of QoS flow adapts to the network status by reducing the rate, but can occupy resources for a long time.

The third type, Delay Critical GBR QoS flow, is a new type added in 5G and is mainly used in ultra-reliable and low-latency communication (URLLC) scenarios.

The principles of user plane traffic classification and marking and the mapping method of QoS flow and AN resources are shown in Figure 4. In the downlink (DL) direction, UPF can classify the arriving data according to the SDF priority in the service data flow (SDF) template. By marking the QFI of the QoS flow on the user plane of N3 and N9, UPF can transmit the classification mark of the user plane traffic belonging to a QoS flow, and then AN can bind the QoS flow with AN resources, such as Data Radio Bearer (DRB). There is no strict 1:1 ratio between QoS flow and AN resource allocation, which depends on the AN resources established by AN to map to the QoS flow.

If there are no matching resources and all QoS flows are associated with one or several downstream packet filters, the UPF will discard the downstream data packets.

In the uplink direction, the UE will evaluate the uplink data packets according to the packet filters (PacketFilter) in the QoS rules, and the evaluation is based on the priority value order in ascending order in the QoS rules until a matching QoS rule is found (which PacketFilter matches the uplink data packet). The UE will then use the QoS flow identifier QFI in the corresponding QoS rule to bind the uplink data packet and the QoS flow, and then the UE will bind the QoS flow to the allocated AN resources.

If no matching sample is found and the default QoS rule contains one or more uplink packet filters (PacketFilter), the UE will discard the uplink data packet.

(5) 5G+Industrial Internet Communication Network Architecture

The most commonly used system architecture for 5G+Industrial Internet business data transmission is shown in Figure 5. Various industry terminals access the 5G network through 5G gateways or 5G customer premises equipment (CPE). Industry terminals can connect to 5G CPE through existing Wi-Fi, wired, etc. 5G CPE accesses the 5G system through the subscriber identity module (SIM) to complete end-to-end communication. In this networking architecture, no changes are required on the terminal side, and the introduction of the 5G system in the end-to-end architecture can be achieved without perception.

It should be noted that the related names in FIG. 5 are explained as follows:

Management and Orchestration (MANO);

Enhanced Message Service (EMS).

Based on the above description, in the actual application process, when using 5G slices, the UE uses APP ID, FQDN, IP triplet and DNN as TD when establishing a session to determine the slice information S-NSSAI selected by the terminal device.

For the use of 5G QoS, if it is IP type data, 5G uses one or more of the following IP header fields as a packet filter set to identify and filter the data packets and map them to different 5GQFIs to provide different 5G QoS services, as shown below:

-Source/destination IP address or IPv6 prefix.

-Source/destination port number.

-Protocol ID of the protocol above IP/Next header type.

-Type of Service(TOS)(IPv4)/Traffic class(IPv6)and Mask.

-Flow Label(IPv6).

-Security parameter index.

-Packet Filter direction

If it is Ethernet type data, 5G uses one or more of the following Ethernet frame header fields as a Packet Filter Set to identify and filter the data packets and map them to different 5G QFIs to provide different 5G QoS services, as shown below:

-Source/destination MAC address.

-Ethertype as defined in IEEE 802.3[131].

-Customer-VLAN tag(C-TAG)and/or Service-VLAN tag(S-TAG)VID fields asdefined in IEEE Std 802.1Q[98].

-Customer-VLAN tag(C-TAG)and/or Service-VLAN tag(S-TAG)PCP/DEI fieldsas defined in IEEE Std 802.1Q[98].

-IP Packet Filter Set,in the case that Ethertype indicates IPv4/IPv6payload.

-Packet Filter direction.

Whether it is the Packet Filter Set of the packet header field used by 5G QoS or the APP ID, FQDN, IP triplet and DNN used by the terminal to determine the slice for the session, these mainly reflect the attribute characteristics of the business application. They use the information in the business running on the 5G access device (for example, the 5G gateway) to determine the selection of 5G slices and 5G QoS, and are strongly bound to the relevant information of the business. In some usage scenarios that do not focus on the business, the network service personalization distinction dimension is small and the user application experience is poor.

Based on this, an embodiment of the present application provides a routing scheduling method, as shown in FIG6, which is applied to a network device and can select a route in some usage scenarios of the 5G+ industry that do not focus on services. The method may include:

S101. Obtain device identification information sent by UE.

In the embodiments of the present application, UE may include a gateway, CPE, a mobile terminal, etc. In general, a gateway is a device that connects different network domains; CPE in a cellular network is responsible for connecting other devices without cellular modules to the cellular network through CPE, and CPE has a cellular module. Specifically, regarding the description of UE, UE may also be referred to as terminal equipment, access terminal, terminal equipment unit (Subscriber Unit), terminal equipment station, mobile station, mobile station (Mobile Station, MS), remote station, remote terminal, mobile device, user terminal, terminal (Terminal), wireless communication equipment, terminal equipment agent or terminal equipment device. Terminal equipment may include various handheld devices with wireless communication functions, vehicle-mounted devices, Internet of Things (IoT) devices, wearable devices, computing devices or other processing devices connected to a wireless modem. It may also include a user unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a wireless modem (Modem), a handheld device (Handset), a laptop computer (Laptop Computer), a machine type communication (MTC) terminal, and a station (ST) in a wireless local area network (WLAN). It may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, and a next generation communication system, for example, a terminal device in a 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN) network.

In the embodiment of the present application, the device identification information (Identity, ID) of the UE is information carried by the UE itself, which is used to identify and distinguish different UEs. The device ID can be an identification device type (i.e., an identification of a class of devices) or a device (an identification of a single device). The device ID can be a physical address (Media Access Control Address, MAC), a MAC address range, or other identification information. Exemplarily, if the UE is a gateway, the device identification information of the UE includes the device ID of the gateway, which can be the MAC address of the gateway.

In an embodiment of the present application, the network device includes a 5G network device, and routing scheduling is implemented through the 5G network device.

In the embodiment of the present application, obtaining the device identification information of the UE may be that the network device receives a registration request sent by the UE, wherein the registration request carries the device ID.

In an embodiment of the present application, the network device receives the device ID of the UE carried in the registration request sent by the UE, which can be obtained during the process of the UE registering with the network device. Specifically, the UE initiates a registration request to the network device in the 5G network, and the registration request carries the device ID of the UE. Among them, the device ID is used to identify the UE type or a single UE. The device ID can be a MAC address, a MAC address range, or other identification information jointly recognized by the network provider and the user equipment manufacturer.

It should be noted that the specific form of the device ID is not specifically limited in the embodiments of the present application and can be selected according to actual conditions.

In the embodiment of the present application, when the UE initiates a registration request to a network device in the 5G network, the UE first initiates a registration request to the RAN in the 5G network, that is, the RAN in the 5G network receives the registration request sent by the UE, and the registration request carries the device ID of the UE. When the RAN receives the registration request carrying the device ID of the UE, the RAN forwards the registration request to the AMF in the 5G network, and the AMF receives the registration request initiated by the UE forwarded by the RAN, wherein the forwarded registration request carries the device ID of the UE.

S102: Determine routing scheduling data for a service corresponding to the UE based on the device identification information.

In the embodiment of the present application, the routing scheduling data includes subscription routing data and/or routing policy data. Based on the device identification information, the subscription routing data and/or routing policy data of the service corresponding to the user equipment can be determined.

In an embodiment of the present application, different device IDs received by a network device may use different contract routing data and/or routing policy data when scheduling services for UE.

In an embodiment of the present application, after the AMF receives the registration request information carrying the device ID of the UE forwarded by the RAN, the AMF initiates a request information to the UDM in the 5G network according to the device ID in the registration request, and the request information is used to request to obtain the contract routing data related to the device ID. The contract routing data may include the contracted 5G slice, session and service continuity mode (Session and Service Continuity Mode, SSC), access mode (3GPP or non-3GPP) and 5G QoS information, among which the 5G QoS information may include QFI, 5QI or specific QoS indicators, such as latency, jitter, reliability, etc.

In an embodiment of the present application, after the AMF receives the registration request information carrying the device ID of the UE forwarded by the RAN, the AMF may also initiate a request information to the PCF in the 5G network based on the device ID in the registration request. The request information is used to request routing policy data related to the device ID. The routing policy data may include 5G slicing, SSC mode, access method (3GPP or non-3GPP) and 5G QoS information, etc., wherein the 5G QoS information may include QFI, 5QI or specific QoS indicators, such as latency, jitter, reliability, etc.

It should be noted that the above-mentioned 5G slices, SSC modes, access methods (3GPP or non-3GPP) and 5G QoS information (including QFI, 5QI or specific QoS indicators, such as latency, jitter, reliability, etc.) can be included in either the contracted routing data or the routing policy data, and can be obtained from either of the two.

In an embodiment of the present application, after UDM receives the contract routing data for obtaining services related to the device ID sent by AMF and/or PCF receives the routing policy data for obtaining services related to the device ID sent by AMF, UDM determines the contract routing data for the service corresponding to the UE and sends it to AMF, or PCF determines the routing policy data for the service corresponding to the UE and sends it to AMF.

In an embodiment of the present application, AMF obtains contract routing data and/or routing policy data, and sends the acquired contract information related to the device ID and/or policy information related to the device ID to SMF in the 5G network, wherein the contract information includes contract routing data, and the policy information includes routing policy data.

S103: Perform routing scheduling for the service of the UE based on the routing scheduling data of the service corresponding to the UE.

In an embodiment of the present application, after the network device in the 5G network obtains the contracted routing data and/or routing policy data, the 5G network performs routing scheduling for the services related to the device according to the contracted routing data or routing policy data corresponding to the device ID. Among them, routing scheduling may include determining 5G slices, SSC modes, access methods (3GPP or non-3GPP) and 5G QoS information, etc. Among them, the 5G QoS information includes the information obtained by the SMF derived from the contracted routing data or routing policy data, such as sending and configuring the QoS rule information related to the device ID to the UE, RAN and UPF, for UE-related uplink and downlink service identification, such as determining the uplink and downlink QFI.

It should be noted that since the contracted routing data and routing policy data correspond to the device ID, after the 5G network obtains the device ID, it can directly obtain the 5G slice corresponding to the device ID based on the device ID.

Based on the above embodiment, during the UE registration process, the process of performing route scheduling based on the device ID is shown in FIG. 7 .

It should be noted that each specific execution process in FIG. 7 may refer to the above embodiment and will not be described in detail here.

It should be noted that the equipment identity Equipment Identity interacted between the UE and the Equipment Identity Register (Equipment Identity Register, EIR) in step 11 of the 3GPP registration process in Figure 7 can also be used as the equipment ID in this application. It can be selected according to actual conditions and is not specifically limited in the embodiments of this application.

In the embodiment of the present application, for 3GPP, the above UE registration update process is specifically embodied in the figure shown in Figure 8. Figure 8 shows that in the process of UE registering with the 5G network, the registration process of the UE in 3GPP is realized by adding the newly added information related to the device ID.

It should be noted that the process of registering through the newly added device ID information has been described in the above embodiment, and the rest can refer to the specific implementation process in the relevant technology, which will not be repeated here.

In another embodiment of the present application, obtaining the device identification information of the UE may be receiving a session establishment request sent by the UE, wherein the session establishment request includes the device ID.

In an embodiment of the present application, the network device receives the device identification information ID of the UE carried in the session establishment request sent by the UE, which can be obtained in the process of the UE establishing a session request to the network device. Specifically, the UE initiates a session establishment request to the network device in the 5G network, and the session establishment request carries the device ID of the UE. Among them, the device ID is used to identify the type of UE or a single UE. The device ID can be a MAC address, a MAC address range, or other identification information jointly recognized by the network provider and the user equipment manufacturer.

It should be noted that the specific form of the device ID is not specifically limited in the embodiments of the present application and can be selected according to actual conditions.

In an embodiment of the present application, when the UE initiates a session establishment request to a network device in a 5G network, the UE first initiates a session establishment request to the AMF in the 5G network, that is, the AMF in the 5G network receives the session establishment request sent by the UE, and the session establishment request carries the device ID of the UE. When the AMF receives the session establishment request carrying the device ID of the UE, the AMF sends the session establishment request information to the SMF in the 5G network, and the SMF receives the session establishment request initiated by the UE sent by the AMF, wherein the session establishment request information carries the device ID of the UE.

In an embodiment of the present application, after SMF receives the session establishment request information carrying the device ID of the UE sent by AMF, SMF initiates a request information to the UDM in the 5G network according to the device ID in the session establishment request, and the request information is used to request to obtain the contract routing data related to the device ID. The contract routing data may include the contracted 5G slice, SSC mode, access method (3GPP or non-3GPP) and 5G QoS information. Among them, the 5G QoS information may include QFI, 5QI or specific QoS indicators, such as latency, jitter, reliability, etc.

In an embodiment of the present application, after the SMF receives the session establishment request information carrying the device ID of the UE sent by the AMF, the SMF can also initiate a request information to the PCF in the 5G network based on the device ID in the session establishment request. The request information is used to request to obtain routing policy data related to the device ID. The routing policy data may include 5G slicing, SSC mode, access method (3GPP or non-3GPP) and 5G QoS information, etc., wherein the 5G QoS information may include QFI, 5QI or specific QoS indicators, such as latency, jitter, reliability, etc.

It should be noted that the above-mentioned 5G slices, SSC modes, access methods (3GPP or non-3GPP) and 5G QoS information (including QFI, 5QI or specific QoS indicators, such as latency, jitter, reliability, etc.) can be included in either the contracted routing data or the routing policy data, and can be obtained from either of the two.

In an embodiment of the present application, after UDM receives the contract routing data for obtaining services related to the device ID sent by SMF and/or PCF receives the routing policy data for obtaining services related to the device ID sent by SMF, UDM determines the contract routing data for the service corresponding to the UE and sends it to SMF, or PCF determines the routing policy data for the service corresponding to the UE and sends it to SMF.

In an embodiment of the present application, after the network device in the 5G network obtains the contracted routing data and/or routing policy data, the 5G network performs routing scheduling for the services related to the device according to the contracted routing data or routing policy data corresponding to the device ID. Among them, routing scheduling may include determining 5G slices, SSC modes, access methods (3GPP or non-3GPP) and 5G QoS information, etc. Among them, the 5G QoS information includes the information obtained by the SMF derived from the contracted routing data or routing policy data, such as sending and configuring the QoS rule information related to the device ID to the UE, RAN and UPF, for UE-related uplink and downlink service identification, such as determining the uplink and downlink QFI.

Based on the above embodiment, during the UE session establishment process, the process of performing route scheduling based on the device ID is shown in FIG. 9 .

It should be noted that each specific execution process in FIG. 9 may refer to the above embodiment and will not be described in detail here.

In the embodiment of the present application, for 3GPP, the above UE session establishment update process is specifically embodied in the figure shown in Figure 10. Figure 10 shows that in the process of UE establishing a session with the 5G network, the session establishment process of the UE in 3GPP is realized through the newly added information related to the device ID.

It should be noted that the process of establishing a session through the newly added device ID information has been described in the above embodiment, and the rest can refer to the specific implementation process in the relevant technology, which will not be repeated here.

Based on the above embodiments, the UE obtains the contracted routing data from the UDM through the device ID during the registration process or during the session establishment process, or obtains the routing policy data from the PCF through the device ID. The device ID is used to identify the device type (the identification of a class of devices) or a single device (a certain device identification), and the device ID can be a MAC address, a MAC address range, or other identification information. The contracted routing data and routing policy data of the device ID and routing selection can support very diverse and rich configurations and real-time updates. For example, the routing selection corresponding to device ID1 is contracted routing data 1. If the contracted routing data is changed and the device manufacturer is changed, the routing selection corresponding to device ID1 may be contracted routing data 2, which can be changed and is not tied together and cannot be changed. However, it is required that the terminal has the ability to obtain and identify the device ID.

In an embodiment of the present application, the device identification information of a 5G access device (the 5G gateway in the 5G+Industrial Internet communication networking architecture as shown in FIG5 ) can be used to determine the selection of 5G slicing and 5G QoS, which can overcome the shortcomings that related mechanisms and processes cannot support the selection of 5G slicing, 5G QoS, etc. based on device identification information. It can be applied in 5G+ industry scenarios, and by identifying device information, it can realize the selection of 5G slicing and 5G QoS at the granularity of devices such as gateways, etc. In some usage scenarios that do not focus on business, it can add a dimension of personalized differentiation of network services and improve the application experience.

It can be understood that in a route scheduling method provided in an embodiment of the present application, in the process of scheduling routes, the network device can determine the route scheduling data corresponding to the device identification information based on the device identification information received from the user device. Because the route scheduling data is related to the device identification information, when the network device receives different device identification information, the selected route scheduling data will also be different, so that the corresponding routes can be matched for different device identification information. Moreover, because different user devices have unique device identification information, the method of matching routes using device identification information has less correlation with the attribute characteristics of the service itself. Therefore, in some application scenarios that do not pay attention to the service, the above method can be used to perform personalized route scheduling for the services corresponding to different user devices, thereby improving the personalized differentiation dimension of 5G network services and providing a stronger application experience.

In one embodiment, when scheduling the route corresponding to the UE's service, the UE's device ID is obtained, and it can also be by receiving a service data packet associated with the UE, the service data packet containing the UE's device identification information; based on the device ID, the route scheduling data of the service corresponding to the UE is determined, and it can also be based on the UE's device ID, the service quality QoS rule of the UE's service corresponding to the service data packet is determined; based on the route scheduling data of the service corresponding to the UE, the UE's service is routed and scheduled, and it can also be based on the UE's device ID, the UE's service is routed and scheduled, and the UE's service is routed and scheduled using the QoS rule of the service corresponding to the UE.

In the embodiment of the present application, routing scheduling of UE services can realize related transmission processing of service data packets.

In an embodiment of the present application, the industry gateway carries the device ID through the data packet, the 5G network determines the device ID based on the data packet field, and uses the device ID as the packet filter in the 5G QoS rule to identify the data packet and determine the corresponding QoS rules, such as QFI.

It should be noted that although the relevant QoS rules in the 5G network are also judged through data packets, they are judged through the packet header, such as the IP address, triplet, source address, destination address, and port number, to determine which QFI the data packet needs to match.

In the technical solution of the embodiment of the present application, it is implemented based on the device ID, while in the related technical solution, the data packet does not contain the device ID. In the embodiment of the present application, the device ID is added to the data packet, and a position is determined in the data packet for supplementation. The data packet supplemented with the device ID enables the network device to no longer need to make judgments through IP addresses, triples, etc., corresponding to QoS, but can make judgments based on the device ID. If a device ID corresponds to the same QFI, user devices sharing the same device ID use the same QFI.

In an embodiment of the present application, receiving a service data packet associated with the UE may be the sending end sending uplink service data to the industry gateway on the terminal side.

It should be noted that the sending end may include a source data sending point, which is similar to a real data source.

In an embodiment of the present application, when the industry gateway on the terminal side receives an uplink service data packet sent by the sender, the industry gateway identifies the device ID in the uplink service data packet. The specific method of identifying the device ID may include the following two methods:

1) After receiving the uplink service data packet sent by the sender, the terminal-side industry gateway marks the device ID in a specific field in the header of the uplink service data packet. For example, if IP data is received, the device ID is marked in the option field of the IP data.

2) After the terminal-side industry gateway re-encapsulates the uplink data with a specific protocol, it marks the device ID in the header field of the encapsulation protocol. If the terminal-side industry gateway receives the data, the terminal-side industry gateway uses the TAN transmission protocol for encapsulation, and then marks the device ID in the TAN protocol specific field. Or, the device ID is marked in the IP data packet header field encapsulated outside the TAN field.

In the embodiment of the present application, through the above two methods, it is possible to add the device ID of the UE in the service data packet, and the location of the device ID can be the packet header of the service data packet containing the device identification information of the user equipment.

In an embodiment of the present application, after the terminal-side industry gateway identifies the device ID in the data packet header of the uplink service data, the terminal-side industry gateway sends the uplink service data carrying the device ID to the 5G network.

It should be noted that when the terminal-side industry gateway is combined with the 5G CPE function, the terminal-side industry gateway sends the uplink business data carrying the device ID to the 5G network, which can be understood as an internal data processing process.

In an embodiment of the present application, the CPE in the 5G network determines the 5G QoS rules based on the received device ID, uses it as a packet filter to identify uplink service data packets, determines the corresponding QFI, and routes and schedules the UE's services according to the service QoS rules corresponding to the determined UE.

In an embodiment of the present application, the quality of service QoS rules of the service data packet are determined based on the device identification information of the UE. The QoS rules corresponding to the device ID of the UE can be searched from the first information, and the found QoS rules are used as the QoS rules of the service data packet.

In an embodiment of the present application, the first information includes a correspondence between a device ID of at least one UE and a QoS rule.

In an embodiment of the present application, when searching for QoS rules from the first information, it is first necessary to obtain the first information, and the first information can be obtained before the sender sends the uplink service data to the industry gateway on the terminal side. Specifically, it can include SMF sending QoS rule information related to the device ID to UE, RAN and UPF for device-related uplink service identification and determination of uplink QFI. Among them, the binding relationship between the device ID and the QoS rule can be determined in advance by the equipment provider and the network provider through negotiation, and pre-configured in the SMF, or the SMF obtains it from the UDM or PCF.

In an embodiment of the present application, the method for SMF to obtain the device ID and QoS rule binding relationship from UDM and/or PCF includes SMF obtaining it through AMF during the registration process (AMF obtains the device ID and QoS rule binding relationship from UDM and/or PCF during the session) or SMF obtaining it from UDM and/or PCF during the session.

In an embodiment of the present application, after obtaining the first information, the 5G network can search for QoS rules corresponding to the device ID from the first information based on the device identification information of the UE.

In an embodiment of the present application, the network can find the QoS rule corresponding to the device ID in the first information based on the device ID contained in the acquired uplink service data packet, and then perform data transmission routing scheduling for the related service based on the QoS rule.

Based on the above embodiment, a flowchart of determining QoS rules according to device ID in uplink service data is shown in FIG. 11 . The specific execution process in FIG. 11 can refer to the above embodiment and will not be repeated here.

In another embodiment of the present application, receiving a service data packet associated with the UE may be the sending end sending downlink service data to the industry gateway on the network side.

It should be noted that the sending end may include a source data sending point, which is similar to a real data source.

In an embodiment of the present application, when the network-side industry gateway receives a downlink service data packet sent by the sender, the network-side industry gateway identifies the device ID in the downlink service data packet. The specific method of identifying the device ID may include the following two methods:

1) After receiving the downlink service data packet sent by the sender, the network-side industry gateway marks the device ID in a specific field in the header of the downlink service data packet. For example, if IP data is received, the device ID is marked in the option field of the IP data.

2) After the network-side industry gateway re-encapsulates the downlink data with a specific protocol, it marks the device ID in the header field of the encapsulation protocol. If the network-side industry gateway receives the data, the network-side industry gateway uses the TAN transmission protocol for encapsulation, and then marks the device ID in the TAN protocol specific field. Or, the device ID is marked in the IP data packet header field encapsulated outside the TAN field.

In the embodiment of the present application, through the above two methods, it is possible to add the UE's device ID to the downlink service data packet, and the location of the device ID can be the header of the downlink service data packet containing the UE's device identification information.

In an embodiment of the present application, after the network-side industry gateway identifies the device ID in the data packet header of the downlink service data, the network-side industry gateway sends the downlink service data carrying the device ID to the 5G network.

In an embodiment of the present application, the UPF in the 5G network determines the 5G QoS rules based on the received device ID, uses it as a Packet Filter to identify downlink service data packets, determines the corresponding QFI, and transmits the service data packets according to the determined QoS rules.

In an embodiment of the present application, when determining the quality of service QoS rules of a service data packet based on the device identification information of the UE, the QoS rules corresponding to the device ID of the UE can be searched from the first information, and the found QoS rules are used as the QoS rules of the service data packet.

In an embodiment of the present application, the first information includes a correspondence between a device ID of at least one UE and a QoS rule.

In an embodiment of the present application, when searching for QoS rules from the first information, it is first necessary to obtain the first information, and the first information can be obtained before the sender sends the uplink service data to the industry gateway on the terminal side. Specifically, it can include SMF sending QoS rule information related to the device ID to UE, RAN and UPF for device-related uplink service identification and determination of uplink QFI. Among them, the binding relationship between the device ID and the QoS rule can be determined in advance by the equipment provider and the network provider through negotiation, and pre-configured in the SMF, or the SMF obtains it from the UDM or PCF.

In an embodiment of the present application, the method for SMF to obtain the device ID and QoS rule binding relationship from UDM and/or PCF includes SMF obtaining it through AMF during the registration process (AMF obtains the device ID and QoS rule binding relationship from UDM and/or PCF during the session) or SMF obtaining it from UDM and/or PCF during the session.

In an embodiment of the present application, after obtaining the first information, the 5G network can search for QoS rules corresponding to the device ID from the first information based on the device identification information of the UE.

In an embodiment of the present application, the network can search the first information for the QoS rule corresponding to the device ID according to the device ID contained in the acquired downlink service data packet, and then perform data transmission of the related service according to the QoS rule.

In an embodiment of the present application, the downlink service data packet will also be sent to the 5G UE/CPE.

In an embodiment of the present application, the 5G UE/CPE sends the downlink service data packet to the terminal-side industry gateway. When the terminal-side industry gateway and the 5G CPE function are combined, this process can be an internal data processing flow.

Based on the above embodiment, a flowchart of determining QoS rules according to device ID in downlink service data is shown in FIG. 12 . The specific execution process in FIG. 12 can refer to the above embodiment and will not be repeated here.

It should be noted that the advantage of using the device ID carried in the data packet is that the existing processes of the 5G network are less modified and less dependent on the upgrade of the 5G network. However, it is necessary to deploy industry gateways on the terminal side and the network side.

In an embodiment of the present application, a routing scheduling method is also provided, as shown in FIG. 13, which is applied to a network device. When routing scheduling is performed on a service of a UE, the method may include:

S201. Send a user route selection policy (UE Route Selection Policy, URSP) table to the UE, where the URSP table at least reflects the correspondence between the UE's device ID and the corresponding subscription route data and/or route policy data.

In an embodiment of the present application, the URSP table describes the correspondence between mobile applications and network slices, etc., and the UE selects corresponding network slices, etc. for the mobile application according to the URSP rules.

In an embodiment of the present application, by expanding the information in the existing URSP table, a correspondence between the device ID and the contracted routing data and/or routing policy data is added to the URSP table, that is, the device ID is added to the URSP table as the traffic descriptor (Traffic Descriptor, TD) of the URSP table to implement device-granular routing scheduling, wherein the routing scheduling may include 5G slicing, SSC mode, and access mode (3GPP or non-3GPP).

In the embodiment of the present application, the traffic descriptor TD included in the URSP table includes a device ID.

In an embodiment of the present application, the network device sends a URSP table to the UE. The UE can determine the routing scheduling data corresponding to the device ID of the UE based on the URSP table sent by the network device and its own corresponding device ID. The routing scheduling data includes contract routing data and/or routing policy data.

In the embodiment of the present application, illustratively, the extension mode and examples of the device ID in the URSP table as a TD are shown in the following Table 3.

Table 3 URSP table - add device ID

It should be noted that there are two ways to configure the UE through the URSP table. One is to write the rules directly in the UE, and only the new URSP table adds a device ID table item information; the other way is that the 5G network transmits it to the UE in real time. The transmission process has not changed. Only the device ID item is added to the transmission table. After the UE obtains the URSP table, it can select the routing scheduling data according to its own device ID. Compared with the method of using routing policy data or contracted routing data in the above-mentioned embodiment, the method of using routing policy data or contracted routing data determines what kind of routing to use by the network device through the contracted routing data or routing policy data, and the method of using the URSP table, if the contracted routing data or policy data does not necessarily carry the route, but it is carried in the URSP table, the UE can select the route at the beginning.

It should be noted that Table 3 exemplifies routing selection based on a certain content, and Table 4 shows a specific way of using routing.

Table 4 Example of adding URSP entry rules for device ID

In Table 4, routing descriptor priority = 1; network slice selection: S-NSSAI-a; SSC mode selection: SSC mode 3; DNN selection: Internet; access type preference: 3GPP access.

It should be noted that the issuance and update of URSP are consistent with the methods in the related art and will not be described in detail here.

S202: Receive subscription routing data and/or routing policy data corresponding to the device ID of the UE determined by using the URSP table and the device ID, sent by the UE.

In an embodiment of the present application, after the UE determines the contracted routing data and/or routing policy data corresponding to the device ID of the UE, the contracted routing data and/or routing policy data corresponding to the device ID of the UE is sent to the network device.

S203: Perform routing scheduling for services of the user equipment based on the received subscription routing data and/or routing policy data corresponding to the device ID of the UE.

In an embodiment of the present application, the network device may perform routing scheduling based on the contracted routing data and/or routing policy data sent by the user equipment, and perform data processing on the corresponding service.

In the embodiment of the present application, a device ID is added to the URSP table, and the URSP table with the device ID added can be directly sent to the UE through the network device. The TD contained in the URSP table contains the device ID, and the device ID can be used as identification information to identify the UE. Each device ID corresponds to the route. The UE can match information in the URSP based on the device ID it carries, and determine the contracted routing data and/or routing policy data corresponding to its own device ID from the multiple groups of corresponding relationships contained in the URSP table. The network device schedules the contracted routing data and/or routing policy data corresponding to the device ID to realize the processing of service data according to the contracted routing data and/or routing policy data.

In the embodiment of the present application, routing selection is performed by means of a URSP table, which has the advantage of reusing the URSP table issuance and update process in the related technology, but requires the network to support the binding of the device ID and the routing selection policy in the URSP table, and also requires the user device to have the ability to obtain and identify the device ID.

It should be noted that the URSP table can be directly configured in the UE or sent to the UE through the PCF.

Based on this, the present application proposes that in the 5G+ industry scenario, the device identification information is identified to realize the device-level routing selection such as 5G slicing, SSC mode, access mode (3GPP or non-3GPP) and 5G QoS selection, such as the 5G slice corresponding to the service transmitted to 5G by the device with device ID A is S-NSSAI-a, SSC mode is SSC 3, access mode is 3GPP, and the 5G QoS requirements for the service transmitted on the device with device ID A are QFI x or 5G QoS-related specific requirements such as bandwidth, latency, reliability, etc. Compared with the prior art, the selection of 5G slicing and 5G QoS at the granularity of the application at the gateway device level is realized through the identification of device information, and in some scenarios that do not focus on the service, the personalized differentiation dimension of network services is expanded to improve the application experience.

Based on the above embodiment, in another embodiment of the present application, a network device 1 is provided. As shown in FIG. 14 , the network device 1 includes:

The determination unit 10 is used to obtain the device ID of the UE; based on the device ID, determine the routing scheduling data of the service corresponding to the UE; the scheduling unit 11 is used to perform routing scheduling on the service of the UE based on the routing scheduling data of the service corresponding to the UE; or, the determination unit 10 is used to send a user routing selection policy URSP table to the UE, the URSP table at least reflecting the correspondence between the device ID of the UE and the corresponding contracted routing data and/or routing policy data; receive the contracted routing data and/or routing policy data corresponding to the device ID of the UE determined by using the URSP table and the device ID sent by the UE; the scheduling unit 11 is used to perform routing scheduling on the service of the UE based on the received contracted routing data and/or routing policy data corresponding to the device ID of the UE.

Optionally, the network device may further include: a receiving unit;

The receiving unit is configured to receive a registration request sent by the UE, where the registration request includes a device ID; or receive a session establishment request sent by the UE, where the session establishment request includes a device ID.

Optionally, the determination unit 10 is further configured to determine, based on the device ID, subscription routing data and/or routing policy data of a service corresponding to the UE.

Optionally, the receiving unit is further configured to receive a service data packet associated with the UE, where the service data packet includes a device ID of the UE.

The determining unit 10 is further configured to determine a QoS rule of a service of the UE corresponding to the service data packet based on the device ID of the UE.

The scheduling unit 11 is further configured to perform routing scheduling on the services of the UE by utilizing the QoS rules of the services corresponding to the UE.

Optionally, the network device may further include: a search unit;

A search unit is used to obtain first information, search for QoS rules corresponding to the UE's device ID from the first information, wherein the first information includes a correspondence between at least one UE's device ID and the QoS rules; and use the found QoS rules as QoS rules for service data packets.

Optionally, the header of the service data packet includes the device ID of the UE.

Optionally, the traffic descriptor TD contained in the URSP table contains the device ID.

A network device provided in an embodiment of the present application obtains the device ID of the UE; determines the route scheduling data of the service corresponding to the UE based on the device ID; and performs route scheduling on the service of the UE based on the route scheduling data of the service corresponding to the UE. It can be seen that in a network device proposed in an embodiment of the present application, in the process of scheduling the route, the network device can determine the route scheduling data corresponding to the device identification information based on the device identification information through the device identification information sent by the received user device. Because the route scheduling data is related to the device identification information, when the network device receives different device identification information, the selected route scheduling data will also be different, and then the corresponding route can be matched for different device identification information. Moreover, because different user devices have unique device identification information, the method of matching the route using the device identification information has less correlation with the attribute characteristics of the service itself. Therefore, in some application scenarios that do not pay attention to the service, the above method can be used to perform personalized route scheduling for the services corresponding to different user devices, thereby improving the personalized differentiation dimension of 5G network services and providing a stronger application experience.

Figure 15 is a schematic diagram of the composition structure of a network device 1 provided in an embodiment of the present application. In actual applications, based on the same public concept of the above-mentioned embodiment, as shown in Figure 15, the network device 1 in the embodiment of the present application includes a processor 12, a memory 13 and a communication bus 14.

In the specific implementation process, the above-mentioned determination unit 10, scheduling unit 11, receiving unit, sending unit, and search unit can be implemented by a processor 12 located on the network device 1, and the above-mentioned processor 12 can be at least one of a specific application integrated circuit (ASIC, Application Specific Integrated Circuit), a digital signal processor (DSP, Digital Signal Processor), a digital signal processing image processing device (DSPD, Digital Signal Processing Device), a programmable logic image processing device (PLD, Programmable Logic Device), a field programmable gate array (FPGA, Field Programmable Gate Array), a CPU, a controller, a microcontroller, and a microprocessor. It can be understood that for different devices, the electronic device used to implement the above-mentioned processor function can also be other, and the embodiments of the present application are not specifically limited.

In the embodiment of the present application, the communication bus 14 is used to realize the connection communication between the processor 12 and the memory 13; when the processor 12 executes the running program stored in the memory 13, the following routing scheduling method is implemented:

Obtaining a device ID of the UE; determining routing scheduling data corresponding to the UE based on the device ID; performing routing scheduling on the services of the UE based on the routing scheduling data corresponding to the UE; or, sending a user routing selection policy URSP table to the user equipment, the URSP table at least reflecting the correspondence between the device identification information of the user equipment and the corresponding contracted routing data and/or routing policy data; receiving the contracted routing data and/or routing policy data corresponding to the device identification information of the user equipment determined by using the URSP table and the device identification information, sent by the user equipment; performing routing scheduling on the services of the user equipment based on the received contracted routing data and/or routing policy data corresponding to the device identification information of the user equipment.

Furthermore, the processor 12 is further configured to receive a registration request sent by the UE, where the registration request includes a device ID; or receive a session establishment request sent by the UE, where the session establishment request includes a device ID.

Furthermore, the processor 12 is further configured to determine, based on the device ID, subscription routing data and/or routing policy data of a service corresponding to the UE.

Furthermore, the processor 12 is also used to receive a service data packet associated with the UE, the service data packet including the device ID of the UE; determine the QoS rule of the UE corresponding to the service data packet based on the device ID of the UE; and perform routing scheduling on the UE's service using the QoS rule of the service corresponding to the UE.

Furthermore, the above-mentioned processor 12 is also used to obtain the first information, search for the QoS rules corresponding to the UE's device ID from the first information, wherein the first information includes the correspondence between at least one UE's device ID and the QoS rules; and use the found QoS rules as the QoS rules for the service data packets.

Furthermore, the header of the service data packet includes the device ID of the UE.

Furthermore, the traffic descriptor TD included in the URSP table includes the device ID.

Based on the above embodiments, the embodiments of the present application provide a storage medium on which a computer program is stored. The above computer-readable storage medium stores one or more programs. The above one or more programs can be executed by one or more processors and applied to a network device. The computer program implements the routing scheduling method as described above.

It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), and includes a number of instructions for enabling an image display device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (11)

1. A routing scheduling method, characterized in that it is applied to a network device, the method comprising: Obtain device identification information of the user's device; Determining, based on the device identification information, routing scheduling data for the service corresponding to the user equipment; Based on the routing scheduling data of the service corresponding to the user equipment, routing scheduling is performed on the service of the user equipment. 2. The method according to claim 1, wherein obtaining device identification information of the user device comprises: receiving a registration request sent by the user equipment, wherein the registration request includes the equipment identification information; or, A session establishment request sent by the user equipment is received, where the session establishment request includes the device identification information. 3. The method according to claim 1, wherein determining the routing scheduling data of the service corresponding to the user equipment based on the equipment identification information comprises: Based on the device identification information, the subscription routing data and/or routing policy data of the service corresponding to the user equipment is determined. 4. The method according to claim 1, characterized in that: The obtaining of device identification information of the user device includes: receiving a service data packet associated with the user equipment, wherein the service data packet includes device identification information of the user equipment; The determining, based on the device identification information, routing scheduling data of the service corresponding to the user equipment includes: Determine, based on the device identification information of the user equipment, a quality of service QoS rule for the service of the user equipment corresponding to the service data packet; Performing route scheduling on the service of the user equipment based on the route scheduling data of the service corresponding to the user equipment includes: The service of the user equipment is routed and scheduled by utilizing the QoS rule of the service corresponding to the user equipment. 5. The method according to claim 4, characterized in that the determining the quality of service (QoS) rule of the service data packet based on the device identification information of the user equipment comprises: Acquire first information, and search the first information for a QoS rule corresponding to the device identification information of the user equipment, wherein the first information includes a correspondence between the device identification information of at least one user equipment and the QoS rule; The found QoS rule is used as the QoS rule of the service data packet. 6. The method according to claim 4 is characterized in that the header of the service data packet contains device identification information of the user equipment. 7. A routing scheduling method, characterized in that it is applied to a network device, the method comprising: Sending a user routing selection policy URSP table to a user equipment, wherein the URSP table at least reflects a correspondence between the device identification information of the user equipment and the corresponding subscribed routing data and/or routing policy data; receiving subscription routing data and/or routing policy data corresponding to the device identification information of the user equipment and determined by using the URSP table and the device identification information and sent by the user equipment; Based on the received subscription routing data and/or routing policy data corresponding to the device identification information of the user equipment, routing scheduling is performed on the service of the user equipment. 8. The method according to claim 7, characterized in that the traffic descriptor TD contained in the URSP table contains the device identification information. 9. A network device, characterized in that the network device comprises: a determination unit and a scheduling unit; wherein: The determining unit is used to obtain device identification information of the user equipment; based on the device identification information, determine the routing scheduling data of the service corresponding to the user equipment; the scheduling unit is used to perform routing scheduling on the service of the user equipment based on the routing scheduling data of the service corresponding to the user equipment; Or, the determination unit is used to send a user routing selection policy URSP table to the user equipment, the URSP table at least reflecting the correspondence between the device identification information of the user equipment and the corresponding contract routing data and/or routing policy data; receiving the contract routing data and/or routing policy data corresponding to the device identification information of the user equipment determined by using the URSP table and the device identification information, which are sent by the user equipment; and the scheduling unit is used to perform routing scheduling for the service of the user equipment based on the received contract routing data and/or routing policy data corresponding to the device identification information of the user equipment. 10. A network device, characterized in that the network device comprises: a processor and a memory; when the processor executes the running program stored in the memory, the method according to any one of claims 1 to 6 is implemented, or when the processor executes the running program stored in the memory, the method according to any one of claims 7 to 8 is implemented. 11. A storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented, or when the computer program is executed by a processor, the method according to any one of claims 7 to 8 is implemented.