CN115842780A

CN115842780A - Rule matching method and device and terminal equipment

Info

Publication number: CN115842780A
Application number: CN202110918382.6A
Authority: CN
Inventors: 高振兴; 姜怡
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2021-08-11
Filing date: 2021-08-11
Publication date: 2023-03-24

Abstract

The application discloses a rule matching method, a rule matching device and terminal equipment, wherein the method comprises the following steps: the method comprises the steps that terminal equipment receives service data and obtains a first destination address from the service data; and the terminal equipment determines a first UE routing strategy URSP rule matched with the first destination address based on the first destination address, wherein the first URSP rule is used for determining a Protocol Data Unit (PDU) session corresponding to the service data or establishing the PDU session corresponding to the service data.

Description

Rule matching method and device and terminal equipment

Technical Field

The present application relates to the field of wireless communication technologies, and in particular, to a method and an apparatus for determining a rule matching formula, and a terminal device.

Background

The industrial terminals are divided into service devices and Customer Premise Equipment (CPE), wherein one or more service devices can be hung under one CPE. For the mobile communication network, the CPE is a terminal device, a UE routing Policy (URSP) rule is stored on the CPE, and the URSP rule cannot be used by the service device. Since the service equipment and the CPE are physically independent, and the CPE operates in a two-layer or three-layer mode of the network, the matching of the URSP rules cannot be performed in either the service equipment or the CPE.

Disclosure of Invention

In order to solve the above technical problem, embodiments of the present invention provide a rule matching method and apparatus, a terminal device, a chip, and a computer-readable storage medium.

The rule matching method provided by the embodiment of the application comprises the following steps:

the method comprises the steps that terminal equipment receives service data and obtains a first destination address from the service data;

and the terminal equipment determines a first URSP rule matched with the first destination address based on the first destination address, wherein the first URSP rule is used for determining the PDU session corresponding to the service data or establishing the PDU session corresponding to the service data.

The rule matching device provided by the embodiment of the application is applied to terminal equipment, and the device comprises:

a receiving unit, configured to receive service data;

an obtaining unit, configured to obtain a first destination address from the service data;

a determining unit, configured to determine, based on the first destination address, a first UE routing policy, URSP, rule matching the first destination address, where the first URSP rule is used to determine a PDU session corresponding to the service data or to establish the PDU session corresponding to the service data.

The terminal device provided by the embodiment of the application comprises: the system comprises a processor and a memory, wherein the memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing any one of the rule matching methods.

The chip provided by the embodiment of the application comprises: and the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes any one of the methods.

The computer-readable storage medium provided by the embodiment of the present application is used for storing a computer program, and the computer program enables a computer to execute any one of the methods.

In the technical solution of the embodiment of the present application, the terminal device matches the URSP rule based on the destination address in the service data, so that the corresponding PDU session can be determined or created through the matched URSP rule, and further, the effective transmission of the service data can be realized through the PDU session.

Drawings

FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application;

fig. 2 is a first flowchart of a rule matching method according to an embodiment of the present application;

fig. 3 is a schematic flowchart illustrating a rule matching method according to an embodiment of the present application;

fig. 4 is a third schematic flowchart of a rule matching method provided in the embodiment of the present application;

fig. 5 is a schematic structural component diagram of a rule matching apparatus provided in an embodiment of the present application;

fig. 6 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

fig. 7 is a schematic structural diagram of a chip of an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application.

As shown in fig. 1, communication system 100 may include a terminal device 110 and a network device 120. Network device 120 may communicate with terminal device 110 over the air. Multi-service transport is supported between terminal device 110 and network device 120.

It should be understood that the embodiment of the present application is only illustrated as the communication system 100, but the embodiment of the present application is not limited thereto. That is to say, the technical solution of the embodiment of the present application can be applied to various communication systems, for example: a Long Term Evolution (LTE) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), an Internet of Things (Internet of Things, ioT) System, a narrowband Band Internet of Things (NB-IoT) System, an enhanced Machine-Type Communications (eMTC) System, a 5G communication System (also called New Radio (NR)) or a future communication System, and the like.

In communication system 100 shown in fig. 1, network device 120 may be an access network device that communicates with terminal device 110. An access network device may provide communication coverage for a particular geographic area and may communicate with terminal devices 110 (e.g., UEs) located within the coverage area.

The Network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (Long Term Evolution, LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Network device 120 may be a relay station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a Network device in a Public Land Mobile Network (PLMN) for future Evolution, or the like.

Terminal device 110 may be any terminal device including, but not limited to, terminal devices that employ wired or wireless connections with network device 120 or other terminal devices.

For example, the terminal device 110 may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handset, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handset with Wireless communication capability, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolution network, etc.

The terminal Device 110 may be used for Device-to-Device (D2D) communication.

The wireless communication system 100 may further include a core network device 130 in communication with the base station, and the core network device 130 may be a 5G core network (5G core,5 gc) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (User uplink Function, SMF), and a Session Management Function (SMF). Alternatively, the Core network device 130 may also be an Evolved Packet Core (EPC) device of the LTE network, for example, a Session Management Function + Core Packet Gateway (SMF + PGW-C) device of the Core network. It is understood that SMF + PGW-C may perform the functions that SMF and PGW-C can perform simultaneously. In the network evolution process, the core network device may also be called by other names, or a new network entity is formed by dividing the functions of the core network, which is not limited in this embodiment of the present application.

Communication between the functional units in the communication system 100 may also be implemented by establishing a connection through a next generation Network (NG) interface.

For example, the terminal device establishes an air interface connection with the access network device through the NR interface, and is used to transmit user plane data and control plane signaling; the terminal equipment can establish control plane signaling connection with the AMF through an NG interface 1 (N1 for short); an access network device, such as a next generation radio access base station (gNB), may establish a user plane data connection with a UPF through an NG interface 3 (N3 for short); the access network equipment can establish control plane signaling connection with the AMF through an NG interface 2 (N2 for short); the UPF can establish a control plane signaling connection with the SMF through an NG interface 4 (N4 for short); the UPF can interact user plane data with a data network through an NG interface 6 (N6 for short); the AMF can establish a control plane signaling connection with the SMF through an NG interface 11 (N11 for short); the SMF may establish a control plane signaling connection with the PCF via NG interface 7 (N7 for short).

Fig. 1 exemplarily shows one base station, one core network device, and two terminal devices, and optionally, the wireless communication system 100 may include a plurality of base station devices and may include other numbers of terminal devices within the coverage area of each base station, which is not limited in this embodiment of the present application.

It should be noted that fig. 1 illustrates a system to which the present application is applied by way of example, and of course, the method shown in the embodiment of the present application may also be applied to other systems. Further, the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship. It should also be understood that "indication" mentioned in the embodiments of the present application may be a direct indication, an indirect indication, or an indication of an association relationship. For example, a indicates B, which may mean that a directly indicates B, e.g., B may be obtained by a; it may also mean that a indicates B indirectly, e.g. a indicates C, by which B may be obtained; it can also mean that there is an association between a and B. It should also be understood that "correspond" mentioned in the embodiments of the present application may mean that there is a direct or indirect correspondence between the two, and may also mean that there is an association relationship between the two, and may also be a relationship of indicating and being indicated, configuring and being configured, and the like. It should also be understood that "predefined" or "predefined rule" mentioned in the embodiments of the present application may be implemented by pre-saving corresponding codes, tables or other manners that may be used to indicate related information in devices (including terminal devices and network devices, for example), and the present application is not limited to the specific implementation manner thereof. Such as predefined, may refer to what is defined in the protocol. It should also be understood that, in the embodiment of the present application, the "protocol" may refer to a standard protocol in the field of communications, and may include, for example, an LTE protocol, an NR protocol, and a related protocol applied in a future communication system, which is not limited in this application.

For the convenience of understanding of the technical solutions of the embodiments of the present application, the following related technologies of the embodiments of the present application are described below, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, and all of them belong to the protection scope of the embodiments of the present application.

The URSP determines the binding relationship between service Data and a Protocol Data Unit (PDU) session, and also determines what PDU session needs to be established by the terminal device to satisfy the binding relationship. Different traffic data streams may be bound to different PDU sessions according to the URSP rules.

The URSP includes a plurality of URSP rules, each of which is composed of a Traffic Descriptor (TD) and a set of Route Selection Descriptors (RSDs). The TD in the URSP is used to describe the traffic characteristics. There may be one or more RSDs under a TD (referred to as a RSD list). Each RSD may correspond to one or more parameter value combinations, each parameter value combination corresponds to a set of PDU session characteristics, and the service data matched with the TD may be transmitted in the PDU session corresponding to a certain parameter value combination of a certain RSD under the TD.

The terminal equipment associates the service data to the corresponding PDU session for transmission based on the URSP rule, and the mechanism is as follows:

when the application layer has business data, the terminal equipment uses the URSP rule in the URSP to check whether the business characteristics of the business data are matched with the TD of a certain URSP rule, and the checking sequence can be determined according to the priority (Precedence) in the URSP rule; when a URSP rule is matched, the terminal equipment determines whether a PDU session matched with one RSD exists or not by using an RSD list under the URSP rule, if yes, the PDU session is multiplexed to transmit service data, if not, a new PDU session is established according to one RSD in the RSD list, and the service data is transmitted through the PDU session.

The RSD includes PDU Session attribute parameters associated with a PDU Session, such as Single-Network Slice Selection assistance Information (S-NSSAI), a Data Network Name (DNN), a PDU Session identifier (PDU Session id), and a PDU Session Type (PDU Session Type).

It should be noted that the URSP rules may be preconfigured on the terminal device side, or may be configured to the terminal device by the network side, where the priority of the URSP rules configured on the network side is higher than the priority of the URSP rules preconfigured on the terminal device side.

The industrial terminals are divided into service devices and CPEs, wherein one or more service devices can be hung under one CPE. For a mobile communication network, the CPE is an end device, the URSP rules are stored on the CPE, and the URSP rules cannot be used by the service device. Since the service equipment and the CPE are physically independent, and the CPE operates in a two-layer or three-layer mode of the network, the matching of the URSP rules cannot be performed in either the service equipment or the CPE.

Therefore, the following technical scheme of the embodiment of the application is provided. The technical scheme of the embodiment of the application provides a method for matching URSP rules based on a destination address, and the CPE can match the URSP rules according to the technical scheme described in the embodiment of the application.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below with specific embodiments. The above related art can be arbitrarily combined with the technical solutions of the embodiments of the present application as alternatives, which all belong to the scope of protection of the embodiments of the present application. The embodiment of the present application includes at least part of the following contents.

Fig. 2 is a schematic flow chart of a rule matching method provided in an embodiment of the present application, and as shown in fig. 2, the rule matching method includes the following steps:

step 201: and the terminal equipment receives the service data and acquires a first destination address from the service data.

Step 202: and the terminal equipment determines a first URSP rule matched with the first destination address based on the first destination address, wherein the first URSP rule is used for determining the PDU session corresponding to the service data or establishing the PDU session corresponding to the service data.

In some optional embodiments, the end device is a CPE. Here, CPE implementations fall into two categories: first, the CPE integrates the functionality of a router; the second category, CPE plugin routers. As an example, the router here may be an AR router.

In the embodiment of the present application, the following two ways may be used for the terminal device to receive the service data:

the first method is as follows: and the terminal equipment receives the service data sent by the service equipment.

The second method comprises the following steps: and the terminal equipment receives the service data from the service equipment forwarded by the router.

In the embodiment of the present application, the terminal device may obtain a destination address from the service data, and for convenience of description, the destination address is referred to as a first destination address. And the terminal equipment determines a first URSP rule matched with the first destination address based on the first destination address, wherein the first URSP rule is used for determining the PDU session corresponding to the service data or establishing the PDU session corresponding to the service data.

In the embodiment of the application, the terminal device can work in two modes, namely, an OSI two-layer mode and an OSI three-layer mode.

In some alternative embodiments, the terminal device operates in OSI's two-layer mode, and the first destination address is a destination MAC address.

In some alternative embodiments, the terminal device operates in an OSI three-layer mode, the first destination address comprising at least one parameter of a destination IP triplet comprising a protocol, a destination IP address and a destination port.

It should be noted that the IP triplet includes a protocol, an IP address, and a port. The destination IP triplet includes: protocol, destination IP address, and destination port.

In this embodiment of the present application, the terminal device determines, based on the first destination address, a first URSP rule matching the first destination address, and may be implemented in the following manner:

the terminal equipment determines whether the first destination address is matched with a destination address described in a TD of a URSP rule;

if the first destination address matches a destination address described in the TD of the URSP rule, the terminal device determines that the URSP rule is the first URSP rule matching the first destination address.

Further, in some optional embodiments, the terminal device determines, from the RSD list of the first URSP rule, a first RSD matching the session attribute parameter based on the session attribute parameter corresponding to the service data; and the terminal equipment determines the PDU session corresponding to the service data or establishes the PDU session corresponding to the service data based on the first RSD, wherein the PDU session is used for transmitting the service data.

Here, the terminal device determines, from the list of RSDs of the first URSP rule, a first RSD matching the session attribute parameter based on the session attribute parameter corresponding to the service data, and may be implemented by:

the terminal device determining whether the first network slice identity matches a network slice identity described in an RSD list of the first URSP rule;

if the first network slice identifier matches a network slice identifier described in an RSD in the RSD list of the first URSP rule, the terminal device determines that the RSD is a first RSD matching the first network slice identifier.

It should be noted that, in the above scheme, the session attribute parameter corresponding to the service data includes the first network slice identifier as an example for description, but is not limited to this, and the session attribute parameter may also include other parameters.

In the embodiment of the present application, the terminal device may pre-configure one or more URSP rules, or the network configures one or more URSP rules for the terminal device.

As an implementation manner, the terminal device receives first configuration information sent by a network, where the first configuration information is used to configure one or more URSP rules, and the URSP rules include a TD and a RSD list, where the TD is used to describe a destination address, and the RSD is used to describe a session attribute parameter.

In some optional embodiments, the first configuration information is configured by a policy control network element, and the policy control network element issues the first configuration information to the terminal device through accessing a mobility management network element. Here, the Policy Control network element may be a Policy Control Function network element (PCF). The Access Mobility Management network element may be an Access Mobility Management Function (AMF) network element.

In the above scheme, the service data may also be referred to as a service data packet, and the first destination address is carried at a header of the service data packet.

It should be noted that the technical solution of the embodiment of the present application may be applied to an industry network, but is not limited to this, and may also be applied to other types of networks.

The technical solution of the embodiment of the present application is illustrated below by referring to specific application examples. It should be noted that the following application examples are described by taking a terminal device as a CPE.

Application example 1

In this application example, the CPE uses the destination address (i.e., destination MAC address) of the second layer in the service data packet to match the URSP rule.

Here, the CPE operates in an OSI two-layer mode, and no matter whether an AR router exists between the CPE and the service device, the CPE may obtain a destination MAC address in a two-layer protocol from a service data packet, and the CPE performs matching of a URSP rule according to the destination MAC address, and further determines or establishes a PDU session according to the matched URSP rule.

Here, a TD is newly added in the URSP rule, and the TD describes a destination MAC address in the two-layer protocol, and further, optionally, the TD may also describe a PDU session of an ethernet (ethernet) type. The CPE may match the URSP rule with a destination MAC address in a two-layer protocol in the service data packet, and then determine or establish a PDU session according to the matched URSP rule.

As shown in fig. 3, the matching process of the URSP rule includes the following steps:

1. the PCF configures two URSP rules: URSP rule 1: TD (MAC 1) + RSD (slice 1); URSP rule 2: TD (MAC 2) + RSD (slice 2). UDM signs two slices for a user: section 1, section 2.

Here, TD in URSP rule 1 describes a destination MAC address, denoted MAC1. RSD in URSP rule 1 describes a slice, denoted slice 1.

Here, TD in URSP rule 2 describes a destination MAC address, denoted MAC2. RSD in URSP rule 2 describes a slice, denoted slice 2.

2. After CPE initiates a registration phase or the registration of CPE is completed, PCF sends URSP rule to CPE through AMF.

3. CPE maintains URSP rules: URSP rule 1: TD (MAC 1) + RSD (slice 1); URSP rule 2: TD (MAC 2) + RSD (slice 2).

4. The industrial terminal 1 carries out service and sends service data to CPE; the industrial terminal 2 carries out service and sends service data to the CPE.

5. The CPE receives the service data, acquires a target MAC address from the service data, matches the target MAC address with a corresponding URSP rule according to the target MAC address, establishes a PDU session based on the matched URSP rule, and transmits the service data through the PDU session.

Specifically, if the destination MAC address acquired by the CPE from the service data is MAC1, the CPE matches to the URSP rule 1 according to the destination MAC address, establishes the PDU session-1 located on the slice 1 based on the URSP rule 1, and transmits the service data of the industrial terminal 1 through the PDU session-1. If the destination MAC address acquired by the CPE from the service data is MAC2, the CPE is matched with URSP rule 2 according to the destination MAC address, PDU session-2 positioned on slice 2 is established based on URSP rule 2, and the service data of industrial terminal 2 is transmitted through PDU session-2.

It should be noted that, in the above application example, the industrial terminal hung under the CPE is a pure two-layer device.

Application example two

In the application example, the CPE uses the destination addresses of three layers in the service data packet to match the URSP rule.

Here, the CPE operates in the three-layer mode of OSI, and no matter whether there is an AR router between the CPE and the service device, the CPE may obtain a destination address in a three-layer protocol from a service data packet, and the CPE performs matching of a URSP rule according to the destination address, and further determines or establishes a PDU session according to the matched URSP rule.

Here, a TD is added in the URSP rule, where the TD describes a destination address in the three-layer protocol, such as a target IP triplet, and the CPE may match the URSP rule using the destination IP triplet in the three-layer protocol in the service data packet, and then determine or establish a PDU session according to the matched URSP rule.

As shown in fig. 4, the matching process of the URSP rule includes the following steps:

1. the PCF configures two URSP rules: URSP rule 1: TD (IP triplet 1) + RSD (slice 1); URSP rule 2: TD (IP triplet 2) + RSD (slice 2). UDM signs two slices for a user: section 1, section 2.

Here, TD in URSP rule 1 describes a destination IP triplet, denoted as IP triplet 1. RSD in URSP rule 1 describes a slice, denoted slice 1.

Here, TD in URSP rule 2 describes a destination IP triplet, denoted IP triplet 2. RSD in URSP rule 2 describes a slice, denoted slice 2.

3. CPE maintains URSP rules: URSP rule 1: TD (IP triplet 1) + RSD (slice 1); URSP rule 2: TD (IP triplet 2) + RSD (slice 2).

5. The CPE receives the service data, acquires a target IP triple from the service data, matches the target IP triple with a corresponding URSP rule according to the target IP triple, establishes a PDU session based on the matched URSP rule, and transmits the service data through the PDU session.

Specifically, if the destination IP triplet obtained by the CPE from the service data is IP triplet 1, the CPE matches to URSP rule 1 according to the destination IP triplet, establishes PDU session-1 on slice 1 based on URSP rule 1, and transmits the service data of industrial terminal 1 through PDU session-1. If the destination IP triple acquired by the CPE from the service data is the IP triple 2, the CPE is matched with the URSP rule 2 according to the destination IP triple, a PDU session-2 positioned on the slice 2 is established based on the URSP rule 2, and the service data of the industrial terminal 2 is transmitted through the PDU session-2.

It should be noted that, in the above application example, the industrial terminal hung under the CPE is a three-layer device.

According to the technical scheme of the embodiment of the application, the TD related to the second-layer destination address or the third-layer destination address is added in the URSP rule, based on the TD, the CPE uses the second-layer destination address or the third-layer destination address in the service data message to match the URSP rule, and then the existing PDU conversation is newly built or selected according to the matched URSP rule to transmit the service data. By adopting the technical scheme of the embodiment of the application, the service data of the industrial terminal can be forwarded on different network resources (such as different network slices).

Fig. 5 is a schematic structural component diagram of a rule matching device provided in an embodiment of the present application, and is applied to a terminal device, where as shown in fig. 5, the rule matching device includes:

a receiving unit 501, configured to receive service data;

an obtaining unit 502, configured to obtain a first destination address from the service data;

a determining unit 503, configured to determine, based on the first destination address, a first UE routing policy, URSP, rule matching the first destination address, where the first URSP rule is used to determine a PDU session corresponding to the service data or to establish the PDU session corresponding to the service data.

In some optional embodiments, the determining unit 503 is configured to determine whether the first destination address matches a destination address described in a traffic descriptor TD of a URSP rule; and if the first destination address is matched with a destination address described in the TD of the URSP rule, determining that the URSP rule is the first URSP rule matched with the first destination address.

In some optional embodiments, the determining unit 503 is further configured to determine, based on a session attribute parameter corresponding to the service data, a matching first RSD from a list of routing identifiers RSDs of the first URSP rule, where the matching first RSD matches the session attribute parameter; and determining a PDU session corresponding to the service data or establishing the PDU session corresponding to the service data based on the first RSD, wherein the PDU session is used for transmitting the service data.

In some optional embodiments, the session attribute parameter corresponding to the service data includes a first network slice identifier; the determining unit 503 is configured to determine whether the first network slice identifier matches a network slice identifier described in an RSD in the RSD list of the first URSP rule; if the first network slice identifier matches a network slice identifier described in an RSD in the RSD list of the first URSP rule, determining that the RSD is a first RSD matching the first network slice identifier.

In some optional embodiments, the first destination address is a destination MAC address.

In some optional embodiments, the first destination address comprises at least one parameter in a destination IP triplet comprising a protocol, a destination IP address and a destination port.

In some optional embodiments, the receiving unit 501 is further configured to receive first configuration information sent by the network, where the first configuration information is used to configure one or more URSP rules, and the URSP rules include a TD and a list of RSDs, where the TD is used to describe a destination address, and the RSDs are used to describe session attribute parameters. For

In some optional embodiments, the first configuration information is configured by a policy control network element, and is issued to the terminal device by the policy control network element through accessing a mobility management network element.

In some optional embodiments, the receiving unit 501 is configured to receive service data sent by a service device; or receiving the service data forwarded by the router from the service equipment.

In some optional embodiments, the end device is a CPE.

It will be appreciated by those skilled in the art that the function of the implementation of the elements in the rule matching apparatus shown in fig. 5 can be understood with reference to the associated description of the foregoing method. The functions of the units in the rule matching apparatus shown in fig. 5 may be implemented by a program running on a processor, or may be implemented by specific logic circuits.

Fig. 6 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device may be a terminal device, and the communication device 600 shown in fig. 6 includes a processor 610, and the processor 610 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 6, the communication device 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application.

The memory 620 may be a separate device from the processor 610, or may be integrated into the processor 610.

Optionally, as shown in fig. 6, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 630 may include a transmitter and a receiver, among others. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 600 may specifically be a terminal device in the embodiment of the present application, and the communication device 600 may implement a corresponding process implemented by the terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Fig. 7 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 700 shown in fig. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 7, the chip 700 may further include a memory 720. From the memory 720, the processor 710 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 720 may be a separate device from the processor 710, or may be integrated into the processor 710.

Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

Optionally, the chip may be applied to the terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and combines hardware thereof to complete the steps of the method.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to the terminal device in the embodiment of the present application, and the computer program instruction causes the computer to execute a corresponding process implemented by the terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of rule matching, the method comprising:

and the terminal equipment determines a first UE routing strategy URSP rule matched with the first destination address based on the first destination address, wherein the first URSP rule is used for determining a Protocol Data Unit (PDU) session corresponding to the service data or establishing the PDU session corresponding to the service data.

2. The method of claim 1, wherein the determining, by the terminal device, the first URSP rule matching the first destination address based on the first destination address comprises:

the terminal equipment determines whether the first destination address is matched with a destination address described in a service descriptor TD of a URSP rule;

3. The method of claim 1, further comprising:

the terminal equipment determines a first RSD matched with the session attribute parameter from a routing selector RSD list of the first URSP rule based on the session attribute parameter corresponding to the service data;

and the terminal equipment determines the PDU session corresponding to the service data or establishes the PDU session corresponding to the service data based on the first RSD, wherein the PDU session is used for transmitting the service data.

4. The method of claim 3, wherein the session attribute parameter corresponding to the service data comprises a first network slice identifier;

the terminal device determines a first RSD matching with the session attribute parameter from a routing selector RSD list of the first URSP rule based on the session attribute parameter corresponding to the service data, and includes:

5. The method according to any of claims 1 to 4, wherein the first destination address is a destination MAC address.

6. The method according to any of claims 1 to 4, wherein the first destination address comprises at least one parameter in a destination IP triplet comprising a protocol, a destination IP address and a destination port.

7. The method according to any one of claims 1 to 4, further comprising:

the terminal equipment receives first configuration information sent by a network, wherein the first configuration information is used for configuring one or more URSP rules, the URSP rules comprise a TD and an RSD list, the TD is used for describing a destination address, and the RSD is used for describing a session attribute parameter.

8. The method of claim 7, wherein the first configuration information is configured by a policy control network element, and is issued to the terminal device by the policy control network element through accessing a mobility management network element.

9. The method according to any one of claims 1 to 4, wherein the terminal device receives service data, comprising:

the terminal equipment receives service data sent by the service equipment; alternatively, the first and second electrodes may be,

and the terminal equipment receives the service data from the service equipment forwarded by the router.

10. The method according to any of claims 1 to 4, wherein the end device is a customer premises equipment, CPE.

11. A rule matching device is applied to terminal equipment and comprises:

a receiving unit, configured to receive service data;

12. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 10.

13. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 10.

14. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 10.