Terminal route selection policy (ursp) detection method and related devices

Abstract

The embodiment of the present disclosure provides a terminal routing selection policy (URSP) detection method and related equipment, and belongs to the technical field of communication. The method is executed by a first core network element, and the method comprises the following steps: acquiring first policy segment identifier (PSI) information corresponding to a first URSP rule reported by a target terminal, the first URSP rule matching a target service flow initiated by the target terminal; generating a first service flow detection rule according to the first URSP rule obtained according to the first PSI information; configuring the first service flow detection rule to a user plane function (UPF) network element of a first protocol data unit (PDU) session, the first PDU session corresponding to the first URSP rule, wherein the UPF network element is used to detect whether a target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, and a first detection result is obtained; and receiving the first detection result sent by the UPF network element. Through the scheme provided by the embodiment of the present disclosure, the execution of the URSP rule on the terminal can be detected.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to a terminal routing strategy URSP detection method, a first core network element, a target terminal, a user plane function (UPF) network element, communication equipment, a computer-readable storage medium, and a computer program product. Background Technology

[0002] The UE (User Equipment) policies sent from the network side to the terminal side include URSP (UERoute Selection Policy) policies. URSP policies include one or more URSP rules, but the relevant technologies do not involve a scheme to detect whether the URSP rules are correctly executed by the UE. Summary of the Invention

[0003] This disclosure provides a terminal routing policy URSP detection method, a first core network element, a target terminal, a user plane function (UPF) network element, a communication device, a computer-readable storage medium, and a computer program product, which can determine whether the UE has correctly executed the URSP rules issued by the network side.

[0004] This disclosure provides a terminal routing policy URSP detection method, which is executed by a first core network element. The method includes: obtaining first policy segment identifier (PSI) information corresponding to a first URSP rule reported by a target terminal, wherein the first URSP rule matches a target service flow initiated by the target terminal; generating a first service flow detection rule based on the first URSP rule obtained from the first PSI information; configuring the first service flow detection rule to a user plane function (UPF) network element of a first protocol data unit (PDU) session, wherein the first PDU session corresponds to the first URSP rule, wherein the first service flow detection rule is used to instruct the UPF network element to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, thereby obtaining a first detection result; and receiving the first detection result sent by the UPF network element.

[0005] This disclosure provides a terminal routing policy URSP detection method, executed by a target terminal. The method includes: when initiating a target service flow, determining a first URSP rule matching the target service flow and obtaining a first policy segment identifier (PSI) information corresponding to the first URSP rule; reporting the first PSI information to a first core network element; the first PSI information instructing the first core network element to generate a first service flow detection rule based on the first URSP rule obtained from the first PSI information, and configuring the first service flow detection rule to a user plane function (UPF) network element of a first protocol data unit (PDU) session, where the first PDU session corresponds to the first URSP rule; the first service flow detection rule instructing the UPF network element to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, obtaining a first detection result and sending it to the first core network element.

[0006] This disclosure provides a terminal routing policy URSP detection method. The method is executed by a User Plane Function (UPF) network element of a first Protocol Data Unit (PDU) session. The first PDU session corresponds to a first URSP rule, and the first URSP rule corresponds to a first Policy Segment Identifier (PSI) information. The first URSP rule matches a target service flow initiated by a target terminal. The method includes: receiving a first service flow detection rule of the first URSP rule sent by a first core network element; the first PSI information instructing the first core network element to generate the first service flow detection rule based on the first URSP rule obtained from the first PSI information; detecting whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, obtaining a first detection result; and transmitting the first detection result to the first core network element.

[0007] This disclosure provides a method for detecting a terminal routing policy URSP (Urban Routing Policy). The method is executed by an Application Function (AF) network element and includes: receiving URSP rule execution notification information sent by a first core network element. The URSP rule execution notification information indicates the execution status of a URSP rule on a terminal or terminal group. The URSP rule includes a first URSP rule, and the terminal or terminal group includes a target terminal. The first URSP rule matches a target service flow initiated by the target terminal. First Policy Segment Identifier (PSI) information instructs the first core network element to obtain the first Policy Segment Identifier (PSI) information corresponding to the first URSP rule reported by the target terminal. Based on the first URSP rule obtained from the first PSI information, a first service flow detection rule is generated. The first service flow detection rule is configured to a User Plane Function (UPF) network element in a first Protocol Data Unit (PDU) session, where the first PDU session corresponds to the first URSP rule. The first service flow detection rule instructs the UPF network element to detect whether a target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, thereby obtaining a first detection result. The first core network element is also used to receive the first detection result and generate the URSP rule execution notification information based on the first detection result.

[0008] This disclosure provides a first core network element, including: an acquisition unit, configured to acquire first policy segmentation identifier (PSI) information corresponding to a first URSP rule reported by a target terminal, wherein the first URSP rule matches a target service flow initiated by the target terminal; a generation unit, configured to generate a first service flow detection rule based on the first URSP rule obtained from the first PSI information; a configuration unit, configured to configure the first service flow detection rule to a User Plane Function (UPF) network element of a first Protocol Data Unit (PDU) session, wherein the first PDU session corresponds to the first URSP rule, wherein the first service flow detection rule is used to instruct the UPF network element to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, and obtain a first detection result; and a receiving unit, configured to receive the first detection result sent by the UPF network element.

[0009] This disclosure provides a target terminal, including: a determining unit, configured to determine a first URSP rule matching the target service flow when initiating a target service flow, and obtain first policy segmentation identifier (PSI) information corresponding to the first URSP rule; and a reporting unit, configured to report the first PSI information to a first core network element. The first PSI information is used to instruct the first core network element to generate a first service flow detection rule based on the first URSP rule obtained from the first PSI information, and to configure the first service flow detection rule to a User Plane Function (UPF) network element of a first Protocol Data Unit (PDU) session, wherein the first PDU session corresponds to the first URSP rule; the first service flow detection rule is used to instruct the UPF network element to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, obtain a first detection result, and send it to the first core network element.

[0010] This disclosure provides a User Plane Function (UPF) network element, which corresponds to a first Protocol Data Unit (PDU) session. The first PDU session corresponds to a first URSP rule, and the first URSP rule corresponds to a first Policy Segmentation Identifier (PSI) information. The first URSP rule matches a target service flow initiated by a target terminal. The UPF network element includes: a receiving unit, configured to receive a first service flow detection rule of the first URSP rule sent by a first core network element, wherein the first PSI information is used to instruct the first core network element to generate the first service flow detection rule based on the first URSP rule obtained from the first PSI information; a detection unit, configured to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, and obtain a first detection result; and a transmission unit, configured to transmit the first detection result to the first core network element.

[0011] This disclosure provides an Application Function (AF) network element, including: a receiving unit, configured to receive URSP rule execution notification information sent by a first core network element. The URSP rule execution notification information is used to indicate the execution status of URSP rules at a terminal or terminal group. The URSP rule includes a first URSP rule, and the terminal or terminal group includes a target terminal. The first URSP rule matches a target service flow initiated by the target terminal. First Policy Segment Identifier (PSI) information is used to instruct the first core network element to obtain the first Policy Segment Identifier (PSI) information corresponding to the first URSP rule reported by the target terminal, generate a first service flow detection rule based on the first URSP rule obtained from the first PSI information, and configure the first service flow detection rule to a User Plane Function (UPF) network element of a first Protocol Data Unit (PDU) session. The first PDU session corresponds to the first URSP rule. The first service flow detection rule is used to instruct the UPF network element to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, and obtain a first detection result to send to the first core network element. The first detection result is used to instruct the first core network element to generate the URSP rule execution notification information based on the first detection result.

[0012] This disclosure provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the Terminal Routing Policy URSP detection method as described in the above embodiments.

[0013] This disclosure provides a communication device, including: one or more processors; and a memory configured to store one or more programs, which, when executed by the one or more processors, enable the communication device to implement the Terminal Routing Policy URSP detection method as described in the above embodiments.

[0014] The solution provided in this disclosure addresses the issue of URSP rule execution in UEs by proposing a scheme for detecting URSP rule execution. This scheme obtains the first URSP rule by acquiring the first PSI information reported by the target terminal through a first core network element. A first service flow detection rule is generated based on this first URSP rule. This first service flow detection rule is configured in the UPF network element of the first PDU session. The first service flow detection rule instructs the UPF network element to detect whether the target service flow sent by the target terminal in the first PDU session matches the first service flow detection rule, and a first detection result is obtained. The first core network element receives the first detection result sent by the UPF network element to determine whether the UE has correctly executed the URSP rule issued by the network side. Attached Figure Description

[0015] Figure 1 This is a schematic diagram of a communication system architecture provided in an embodiment of this disclosure.

[0016] Figure 2 This is a system architecture diagram of a 5G network provided in an embodiment of this disclosure.

[0017] Figure 3 A flowchart illustrating a terminal routing policy URSP detection method according to an embodiment of the present disclosure is shown.

[0018] Figure 4 The illustration shows an interactive diagram of a terminal routing policy URSP detection method according to an embodiment of the present disclosure.

[0019] Figure 5 The diagram illustrates an interaction of a terminal routing policy URSP detection method according to another embodiment of the present disclosure.

[0020] Figure 6 The diagram illustrates an interaction of a terminal routing policy URSP detection method according to yet another embodiment of the present disclosure.

[0021] Figure 7 The diagram illustrates an interaction of a terminal routing policy URSP detection method according to another embodiment of the present disclosure.

[0022] Figure 8 A flowchart illustrating a terminal routing policy URSP detection method according to another embodiment of the present disclosure is shown.

[0023] Figure 9 A flowchart illustrating a terminal routing policy URSP detection method according to yet another embodiment of the present disclosure is shown.

[0024] Figure 10 A flowchart illustrating a terminal routing policy URSP detection method according to another embodiment of the present disclosure is shown.

[0025] Figure 11 A block diagram of a first core network element according to an embodiment of the present disclosure is shown schematically.

[0026] Figure 12 A block diagram of a target terminal according to an embodiment of the present disclosure is shown schematically.

[0027] Figure 13 A block diagram of a User Plane Function (UPF) network element according to an embodiment of the present disclosure is shown schematically.

[0028] Figure 14A block diagram of an application function AF network element according to an embodiment of the present disclosure is shown schematically.

[0029] Figure 15 A schematic structural diagram of a communication device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0030] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be more thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art.

[0031] The technical solutions of this disclosure can be applied to various communication systems, such as: Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), or 5G systems, etc. For example, the communication system 100 applied in this disclosure embodiment is as follows: Figure 1As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal 120 (or a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminals located within that coverage area. Optionally, the network device 110 may be a base station (BTS) in a GSM or CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, a base station in a 5G communication system, or a radio controller in a Cloud Radio Access Network (CRAN). Alternatively, the network device may be a mobile switching center, relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, network-side equipment in a 5G network, or network equipment in a future evolved Public Land Mobile Network (PLMN), etc.

[0032] The communication system 100 also includes at least one terminal 120 located within the coverage area of ​​network device 110. As used herein, "terminal" includes, but is not limited to, devices configured to receive / transmit communication signals via wired connections, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM broadcast transmitters; and / or another terminal. A terminal configured to communicate via a wireless interface may be referred to as a "wireless communication terminal," "wireless terminal," or "mobile terminal." Examples of mobile terminals include, but are not limited to, satellite or cellular phones; personal communications system (PCS) terminals that can combine cellular radiotelephony with data processing, fax, and data communication capabilities; PDAs that may include radiotelephones, pagers, Internet / intranet access, web browsers, notebooks, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or handheld receivers or other electronic devices that include radiotelephone transceivers. A terminal can refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in future evolved PLMNs, etc. Optionally, terminals 120 can perform device-to-device (D2D) communication. Optionally, the 5G system or 5G network can also be referred to as a New Radio (NR) system or NR network.

[0033] Figure 1An exemplary diagram illustrates a network device and two terminals. Optionally, the communication system 100 may include multiple network devices, and each network device may include other numbers of terminals within its coverage area; this disclosure does not limit this. Optionally, the communication system 100 may also include other network entities such as a network policy control entity and a mobility management entity; this disclosure does not limit this. It should be understood that devices with communication functions in the network / system of this disclosure may be referred to as communication devices. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal 120 with communication functions. The network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as network policy control entities, mobility management entities, and other network entities. This disclosure does not limit this.

[0034] It should be understood that the terms "system" and "network" are often used interchangeably in this paper. The term "and / or" in this paper is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three cases: A exists alone, A and B exist simultaneously, and B exists alone.

[0035] Figure 2 This is a system architecture diagram of a 5G network according to an embodiment of the present disclosure, such as... Figure 2 As shown, the equipment involved in a 5G network system includes: User Equipment (UE) > Radio Access Network (RAN), User Plane Function (UPF) > Data Network (DN), Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF) > Application Function (AF) > Authentication Server Function (AUSF), and Unified Data Management (UDM). Figure 2 As shown, the network elements related to policies are mainly PCF, AMF, SMF, RAN, and UE. Among them, SMF is mainly responsible for the execution of session-related policies, while AMF is mainly responsible for the execution of access and UE-related policies. The policy distribution and updates on the two network elements (AMF and SMF) are all managed by PCF.

[0036] Specifically, regarding UE policies, the PCF and UE can monitor UE policy-related information through containers, including the content and identifier of the UE policy. In the uplink direction, the UE sends the container to the AMF via NAS (non-access-stratum) messages, and the AMF then forwards it to the PCF (without not noticing or modifying it). In the downlink direction, the PCF sends the container to the AMF, which then forwards it to the UE via NAS messages. UE policies include URSPs. A URSP contains multiple policy rules (called URSP Rules), each consisting of a Traffic Descriptor / Service Descriptor and a set of Route Selection Descriptors (RSDs). The Traffic Descriptor in the URSP describes a specific service. A Traffic Descriptor can have one or more RSDs, and each RSD corresponds to an attribute of a PDU session. This means that the service data corresponding to the Traffic Descriptor can run within the PDU session corresponding to the RSD.

[0037] The relevant content of URSP in related technologies is shown in Tables 1 and 2 below:

[0038] Table 1: URSP Rules

[0039]

[0040]

[0041] In Table 1 above, Rule Precedence indicates rule priority, which determines the order in which the UE uses URSP rules. A traffic descriptor is a traffic descriptor used to describe matching criteria. It consists of one or more components, optionally including application descriptors, IP descriptors (also called network address descriptors, destination IP), domain descriptors (destination FQDN (Fully Qualified Domain Name)), non-IP descriptors (also called non-network address descriptors), DNN (Data Network Name) descriptors, and connection capabilities. The traffic descriptor is used by the UE for application matching. The URSP rule applies when each component in the traffic descriptor matches the corresponding information from the application. The URSP rule does not apply when any component in the traffic descriptor has the following conditions:

[0042] - No relevant information from the application is available;

[0043] - The corresponding information from the application does not match any value in the traffic descriptor component.

[0044] Table 2: RSD

[0045]

[0046]

[0047] In Table 2 above, Route Selection Descriptor Precedence indicates the RSD priority, which determines the order in which RSDs are used. Only when a high-priority RSD cannot be used will another RSD be used. Route selection components describe the various network resources that an application can use. They consist of one or more components and may include SSC (service and session continuity) mode selection (used by the UE to associate a matching application with an SSC mode), network slice selection (used by the UE to associate a matching application with an S-NSSAI), DNN selection (used by the UE to associate a matching application with a DNN), PDU (Protocol Data Unit) session type selection (used by the UE to match a matching application with a PDU session type), non-Seamless Offload indication, and access type preference (also known as access type preference, which indicates the preferred access type (3GPP or non-3GPP or multi-access) if the UE needs to establish a PDU session for a matching application).

[0048] Route Selection Validation Criteria, also known as route selection validation criteria, describes the corresponding validity conditions. It includes a time window (also called a valid time window) and location criteria (also called valid area parameters). If the current time is not within the time window or the UE location does not match the location criteria, the corresponding RSD is considered invalid. Among these, SSC mode, S-NSSAI (Single Network Slice Selection Assistance Information), PDU session type, and DNN are all parameters related to PDU session attributes. When the network sends user equipment policy (UE policy) to the terminal, it divides the UE policy into one or more sections for transmission. Each section corresponds to an identifier, i.e., policy section identifier (PSI). The PCF or AMF sends the UE policy to the UE, and the UE policy may include URSP policies. UE policies are divided into one or more sections. Each section corresponds to a PSI (policy section identifier) ​​sent to the UE. PSI is also called UPSI (UE PSI). This means that the network side can divide the UE policy into multiple sections and send them to the UE in one or more NAS messages.

[0049] In 5G (5th Generation Mobile Communication Technology) system design, the UE triggers a UE policy reporting process. This reporting can be completed during the initial registration process or during the mobility management process when the UE switches from EPS (Evolved Packet System, also known as a 4G system) to a 5G network. When the URSP is lost or invalid, the UE uses the initial registration process to retrieve the URSP rules. The UE can include its stored PSI information in this process, and the PCF receives the PSI information reported by the UE. Alternatively, the PCF can obtain the UE's PSI information from the UDR (Unified Data Repository) and then compare the PSI information retrieved from the UDR with the PSI information reported by the UE. If they are different, the PCF sends the URSP content corresponding to the different PSI to the UE, that is, it sends the URSP content corresponding to the PSI information retrieved from the UDR to the UE. If they are the same, the PCF does not need to return the URSP content to the UE.

[0050] Each UE's policy section is identified by a UPSI, which consists of the following two parts:

[0051] a)a PLMN ID part containing the PLMN ID of the PLMN of the PCF which provides the UE policies; and

[0052] b)a UE policy section code(UPSC)containing a unique value within the PLMN selected by the PCF.

[0053] Each segment is identified by a PSI, and the PSI / UPSI includes the PLMN ID and the UE policy section code (UPSC).

[0054] The relevant technologies do not include a scheme for detecting whether URSP rules are correctly executed by the UE. This disclosure addresses the issue of URSP rule execution by the UE by proposing a scheme for detecting URSP rule execution, used to determine whether the UE has correctly executed the URSP rules issued by the network side.

[0055] Figure 3The terminal routing policy URSP detection method provided in the embodiment can be executed by a first core network element. In the exemplary embodiment, the first core network element can be a PCF, but this disclosure is not limited thereto. Figure 3 As shown, the method provided in this disclosure embodiment may include:

[0056] In S310, the first policy segment identifier (PSI) information corresponding to the first URSP rule reported by the target terminal is obtained. The first URSP rule matches the target service flow initiated by the target terminal. In this embodiment of the present disclosure, the target terminal can be any UE. When a UE initiates a new service flow (referred to as the target service flow), it determines which URSP rule the service flow matches. The URSP rule that matches the target service flow is called the first URSP rule. The first URSP rule may be any of the URSP rules. Each URSP rule has corresponding PSI information, and here the PSI information corresponding to the first URSP rule is referred to as the first PSI information.

[0057] URSP (Uniform Router Service Provider) can be used to map specific service flows to corresponding data transmission sessions for the UE (User Equipment). For example, the PCF (Process Control Function) can generate multiple URSP rules in the core network. Each URSP rule can include a Traffic Descriptor and a Routing Descriptor (RSD). When an application starts on the terminal, the UE can match the Traffic Descriptor in the URSP rules generated by the core network based on the traffic characteristics of the application, thus determining the corresponding URSP. Each URSP rule can include one or more RSDs, and the RSD priority can be configured for different RSDs in each URSP rule according to service requirements and service type. After matching the corresponding URSP, the terminal can select the appropriate RSD based on the RSD priorities of the generated RSDs and transmit the application's data (referred to as service data or application data, here referred to as the target service flow) in the data transmission session corresponding to that RSD.

[0058] In an exemplary embodiment, obtaining the first policy segment identifier (PSI) information corresponding to the first URSP rule reported by the target terminal may include: if the first PDU session has already been established when the target terminal initiates the target service flow, then in the modification process of the first PDU session triggered by the target terminal, obtaining the first PSI information from a second core network element. In this embodiment, the second core network element may be used to receive the first PSI information from a third core network element. The third core network element may be used to receive the first PSI information from the target terminal.

[0059] In an exemplary embodiment, the second core network element may be an SMF, but this disclosure is not limited thereto. The third core network element may be an AMF, but this disclosure is not limited thereto.

[0060] In an exemplary embodiment, obtaining the first policy segment identifier (PSI) information corresponding to the first URSP rule reported by the target terminal may include: if the first PDU session is not established when the target terminal initiates the target service flow, then during the establishment process of the first PDU session triggered by the target terminal, obtaining the first PSI information from a second core network element. In this embodiment, the second core network element may be used to receive the first PSI information from a third core network element. The third core network element may be used to receive the first PSI information from the target terminal.

[0061] In this embodiment of the disclosure, when the UE initiates a new target service flow, it will determine which URSP rule the target service flow is matched with. If the matched URSP rule (the first URSP rule) has already established a PDU session (referred to as the first PDU session), the target service flow will be sent on the PDU session. If the matched URSP rule has not established a PDU session, a new PDU session establishment process will be initiated, referred to as the first PDU session establishment process.

[0062] (1) If the first URSP rule that matches has already established the first PDU session, the UE triggers the modification procedure of the first PDU session and sends a NAS message to the network (sent to the AMF through the base station and finally to the PCF). The message contains the first PSI information of the first URSP rule that matches the newly added target service flow.

[0063] (2) If the first URSP rule that matches does not establish the first PDU session, the UE initiates the establishment process of the first PDU session and sends the first PSI information of the first URSP rule that matches the target service flow to the network (sent to the AMF through the base station and finally to the PCF).

[0064] In S320, a first service flow detection rule is generated based on the first URSP rule obtained from the first PSI information.

[0065] In an exemplary embodiment, the first traffic flow detection rule may include at least one of the first network address descriptor, the first domain descriptor, and the first non-network address descriptor. In this embodiment, after the PCF obtains the reported first PSI information, it can obtain the first URSP rule corresponding to the first PSI information. The first URSP rule includes Rule Precedence and Traffic descriptor, and optionally may also include one or more of the following: Application descriptors (referred to as the first application descriptor), IP descriptors (referred to as the first network address descriptor), Domain descriptors (referred to as the first domain descriptor), Non-IP descriptors (referred to as the first non-network address descriptor), DNN, Connection Capabilities, List of Route Selection Descriptors, and various parameters of each RSD.

[0066] After obtaining the first URSP rule, the PCF can select some or all of its parameters to generate the corresponding first Packet Detection Rule (PDR). For example, if the first URSP rule includes IP descriptors, then those IP descriptors can be included in the first PDR. If the first URSP rule includes domain descriptors, then those domain descriptors can be included in the first PDR. If the first URSP rule includes non-IP descriptors, then those non-IP descriptors can be included in the first PDR. As another example, if the first URSP rule includes application descriptors, then those application descriptors can be included in the first PDR. If the first URSP rule includes a DNN, then that DNN can be included in the first PDR. For example, if the first URSP rule includes IP descriptors, domain descriptors, application descriptors, and DNN, then the first PDR includes the IP descriptors and domain descriptors; or, the first PDR includes the IP descriptors, domain descriptors, application descriptors, and DNN; or, the first PDR includes the IP descriptors, domain descriptors, and application descriptors, etc. The first PDR rule may have been stored on the PCF when the first PDU session was established, or it may be obtained by the PCF after receiving the first PSI information.

[0067] In S330, the first service flow detection rule is configured to the user plane function (UPF) network element of the first protocol data unit (PDU) session. The first PDU session corresponds to the first URSP rule. The first service flow detection rule can be used to instruct the UPF network element to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, and obtain a first detection result.

[0068] In an exemplary embodiment, configuring the first service flow detection rule to the User Plane Function (UPF) network element of the first Protocol Data Unit (PDU) session may include: sending the first service flow detection rule to a second core network element. The second core network element can be used to send the first service flow detection rule to the UPF network element. In this embodiment, the second core network element may be an SMF, but this disclosure is not limited thereto. For example, if a first PDU session has been established, the PCF sends the first service flow detection rule to the SMF, and the SMF sends the first PDR rule to the UPF of the first PDU session. When the target UE sends the target service flow on the first PDU session, the UPF will detect whether the target service flow matches the first PDR rule. As another example, if a first PDU session has not yet been established, the PCF sends the first service flow detection rule to the SMF, and the SMF sends the first PDR rule to the UPF of the first PDU session. When the first PDU session is established, when the target UE sends the target service flow on the first PDU session, the UPF will detect whether the target service flow matches the first PDR rule and obtain a first detection result. UPF will send the first detection result to SMF, indicating whether the target service flow on the first PDU session matches the first PDR rule.

[0069] In S340, the first detection result sent by the UPF network element is received.

[0070] In an exemplary embodiment, receiving the first detection result sent by the UPF network element may include: receiving the first detection result from a second core network element. The second core network element may be used to receive the first detection result from the UPF network element.

[0071] In an exemplary embodiment, receiving the first detection result sent by the UPF network element may include: receiving the first detection result when the first detection result indicates that the target service flow matches the first service flow detection rule; or receiving the first detection result when the first detection result indicates that the target service flow does not match the first service flow detection rule; or receiving the first detection result when the first detection result indicates that the target service flow matches or does not match the first service flow detection rule.

[0072] In this embodiment, the UPF sends a first detection result to the SMF, indicating whether the target service flow on the first PDU session matches the first PDR rule. The SMF reports the first detection result to the PCF. One scenario is that the UPF only reports the result to the PCF when the target service flow on the first PDU session does not match the first PDR rule. If only the mismatch case needs to be uploaded, and the matching case is not required, the data transmission volume between the SMF and PCF can be reduced, thus lowering the storage space occupied. Another scenario is that the UPF reports the result to the PCF regardless of whether the target service flow on the first PDU session matches or does not match the first PDR rule. When the SMF reports both matches and mismatches to the PCF simultaneously, the PCF can directly calculate the total number of matches and mismatches and their respective proportions based on the received data, thus accelerating the calculation speed. Yet another scenario is that the UPF only reports the result to the PCF when the target service flow on the first PDU session matches the first PDR rule. If only the matching case needs to be uploaded, and the mismatch case is not required, the data transmission volume between the SMF and PCF can be reduced, thus lowering the storage space occupied. This disclosure does not limit this approach.

[0073] In an exemplary embodiment, the first service flow detection rule may include a detection frequency, which can be used to instruct the UPF network element to periodically detect data packets in the target service flow according to the detection frequency. In this embodiment, a detection frequency can also be added to the first PDR rule. The UPF detects data packets on the first PDU session once at fixed intervals according to the detection frequency. Because the UE is untrusted by default and may make erroneous operations, it may put data from multiple service flows on the first PDU session for transmission. Therefore, during the periodic detection by the UPF according to the detection frequency, the first detection result of some data packets (data packets in the target service flow) may match, while the first detection result of some data packets (data packets from other service flows that have been mistakenly put into the target service flow) may not match.

[0074] like Figure 4 As shown, the method provided in this disclosure embodiment may include:

[0075] In S41, the UE reports the executed URSP information, which includes PSI information.

[0076] In S41, the UE can be any UE, referred to as the target UE. The URSP information reported by the UE refers to the information related to the first URSP rule that matches the target service flow newly initiated by the UE. The PSI information contained therein is called the first PSI information, and the corresponding PDU session is called the first PDU session.

[0077] S41 can send the corresponding first PSI information to PCF during the PDU session establishment process or PDU session update process. UE can report the first PSI information to PCF in sequence through base station, AMF and SMF.

[0078] In S42, the PCF sends the corresponding service flow detection rule to the SMF based on the received first PSI information, which is called the first service flow detection rule.

[0079] In S43, after the SMF receives the first service flow detection rule, it forwards the first service flow detection rule to the UPF of the first PDU session.

[0080] In S44, after the UPF of the first PDU session receives the first service flow detection rule, it detects whether the target service flow sent by the UE in the first PDU session matches the rule, thereby generating a first detection result, and reporting the first detection result to the SMF as a service detection status.

[0081] In S45, after the SMF receives the service detection status, it sends the service detection status to the PCF.

[0082] In an exemplary embodiment, the method may further include: generating URSP rule execution notification information based on the first detection result, wherein the URSP rule execution notification information is used to indicate the execution status of URSP rules on a terminal or a terminal group, wherein the URSP rule includes the first URSP rule, and the terminal or the terminal group includes the target terminal; and sending the URSP rule execution notification information to the application function AF network element.

[0083] In an exemplary embodiment, the method may further include: receiving a URSP execution status subscription request message sent by the AF network element, the URSP execution status subscription request message including information of the URSP rule and information of the AF network element; authenticating the URSP execution status subscription request message according to the information of the AF network element; generating a URSP execution status subscription response message according to the authentication result; and sending the URSP execution request subscription response message to the AF network element.

[0084] In an exemplary embodiment, the method may further include: receiving URSP rule configuration information sent by the AF network element; generating the URSP rule with reference to the URSP rule configuration information; and sending the information of the URSP rule to the AF network element.

[0085] In this embodiment of the disclosure, the AF can influence the PCF to generate URSP rules, for example, by defining the process by which the AF influences the URSP rules. The parameter information that the AF can provide to network elements such as the NEF in the network may include, but is not limited to:

[0086] 1)Service Description indicates an AF Identifier.

[0087] 2) Service Parameters.

[0088] 3)a specific UE, or a group of UE(s) or any UE that the AF request maybe associated with.

[0089] 4) Subscription to events.

[0090] This disclosure proposes that URSP rule configuration information can be carried in the aforementioned service parameters. The URSP rule configuration information may include configuration information that the AF (Automatic Function) wishes to influence any one or more parameters in Tables 1 and 2. After the PCF (Power Processor) receives the URSP rule configuration information from the AF or the NEF (Neural Function), it can decide whether to accept the URSP rule configuration information based on its own decision. If accepted, it generates URSP rules with reference to the URSP rule configuration information; if not accepted, it generates URSP rules without referencing the URSP rule configuration information.

[0091] For example, such as Figure 6 As shown, the method provided in this disclosure embodiment may include:

[0092] In S61, AF sends URSP rule configuration information to PCF.

[0093] In S62, after receiving the URSP rule configuration information from the AF, the PCF refers to the URSP rule configuration information to determine how to generate the URSP. It is understood that the URSP rule configuration information can be included in existing parameters of an existing message, or in newly added parameters of an existing message, or it can be transmitted through a new message; this disclosure does not limit this. It should be noted that S61 above is optional, meaning the PCF can also directly configure the URSP.

[0094] In S63, the PCF sends the generated URSP to the AMF.

[0095] PCF may place the configured URSP in a container and send it to AMF, but this disclosure is not limited thereto.

[0096] In S64, after the AMF receives the URSP, it sends the URSP to the UE via the RAN.

[0097] In this embodiment of the disclosure, the AMF can use NAS messages to directly forward the container to the UE, but this disclosure is not limited thereto.

[0098] For example, such as Figure 7 As shown, the method provided in this disclosure embodiment may include:

[0099] In S71, AF sends URSP rule configuration information to NEF.

[0100] In S72, after the NEF receives the URSP rule configuration information from the UE, it forwards it to the PCF.

[0101] In S73, after receiving the URSP rule configuration information from the NEF, the PCF refers to the URSP rule configuration information to determine how to generate the URSP. It should be noted that S71 and S72 are optional; that is, the PCF can also directly configure the URSP.

[0102] In S74, the PCF sends the configured URSP to the AMF.

[0103] In S75, after the AMF receives the URSP, it sends the URSP to the UE via the RAN.

[0104] In this embodiment of the disclosure, it is assumed that the PCF receives the URSP rule configuration information from the AF or the NEF, generates the URSP rule, and then returns the information of the generated URSP rule, such as the URSP rule ID (identity) and / or PSI information, to the AF.

[0105] like Figure 5 As shown, the method provided in this disclosure embodiment may include:

[0106] In S51, AF sends a URSP execution status subscription request message to PCF.

[0107] After receiving the URSP rule information returned by the PCF, if the AF wants to know whether the URSP rule has been correctly executed after being sent to the UE or UE group, the AF can send a URSP execution status subscription request message to the PCF. The URSP execution status subscription request message can include at least the information of the URSP rule that the AF wants to know the execution status of in the UE or UE group, as well as the information of the AF, such as the AF ID.

[0108] In S52, after receiving the URSP execution status subscription request message, the PCF authenticates the URSP execution status subscription request message based on the AF information carried in the message, and determines whether the AF can subscribe to the information (i.e. whether it can subscribe to the execution status of the URSP rules on the UE or UE group). If the authentication is successful, the PCF sends a URSP execution status subscription response message to the AF as a subscription success message; if the authentication fails, the PCF sends a URSP execution status subscription response message to the AF as a subscription failure message.

[0109] In S53, if the PCF accepts the URSP rule execution status subscription request sent by the AF, when the PCF receives the URSP service execution status reported by the SMF (such as the first detection result mentioned above), it will send a message to the AF according to the received service execution status. The message indicates the status of the URSP rule being executed by the UE or UE group, which is called URSP execution status notification information. The URSP execution status notification information may optionally include the UE ID information, the URSP rule ID information and / or PSI information.

[0110] In this embodiment of the disclosure, the URSP execution status notification information includes an indication of the execution status. The indication of the execution status can be any one or more of the following: the detection result of a certain URSP rule on a certain UE, such as the first detection result of the first URSP rule on the target UE, which is included in the URSP execution status subscription request message sent by the AF to the PCF; the detection result of a certain URSP rule on all UEs or UE groups to which it is issued, which is included in the URSP execution status subscription request message sent by the AF to the PCF; the detection result of each URSP rule in the URSP execution status subscription request message sent by the AF to the PCF on each UE or UE group to which it is issued; and statistical information generated based on the detection results of each URSP rule in the URSP execution status subscription request message sent by the AF to the PCF on each UE or UE group to which it is issued.

[0111] The statistical information generated based on the detection results of each URSP rule in the URSP execution status subscription request message sent by AF to PCF on each UE or UE group to which it was issued may include any one or more of the following: the percentage of UEs that match the detection result within a certain period of time among the UEs to which the URSP rule was issued, for example, assuming that a certain URSP rule is issued to 100 UEs, and the detection result of 50 of the 100 UEs is a match, then the obtained percentage is 50%; the percentage of UEs that do not match the detection result within a certain period of time among the UEs to which the URSP rule was issued.

[0112] The content of the execution status indication included in the URSP execution status notification information may vary depending on the content carried in the URSP execution status subscription request message sent by the AF to the PCF. For example, if the URSP execution status subscription request message requests the return of statistical information, then the returned URSP execution status notification information will include statistical information.

[0113] In an exemplary embodiment, the method may further include: sending blocking indication information corresponding to the first service flow detection rule, wherein the blocking indication information can be used to instruct the UPF network element to block target service flows that do not match the first service flow detection rule. Specifically, when the SMF sends the first PDR rule to the UPF, it can instruct the UPF to block target service flows that do not conform to the first PDR rule. The UPF detects the target service flow of the first PDU session, and when the target service flow does not conform to the first PDR rule, it can report the information to the SMF and simultaneously block the target service flow according to the SMF's instructions.

[0114] In an exemplary embodiment, the method may further include: when the first detection result indicates that the target service flow does not match the first service flow detection rule, generating a URSP rule matching error message, wherein the URSP rule matching error message can be used to indicate that the first URSP rule matched by the target terminal on the first PDU session is incorrect; and sending the URSP rule matching error message to the target terminal. In this embodiment of the present disclosure, when the PCF receives a message from the SMF containing a first detection result that the target service flow does not conform to the first PDR rule, it may send a URSP rule matching error message to the target UE. The URSP rule matching error message can be used to indicate that the first URSP rule match of the target UE on the first PDU session is incorrect. The URSP rule matching error message may contain the ID of the first PDU session and the first PSI information of the first URSP rule. When the target UE receives a URSP rule mismatch message, it can re-match the target service flow on the first PDU session with other URSP rules until a suitable URSP rule is found. The other suitable URSP rule found can be called the second URSP rule. The case where the target service flow of the target UE is sent through the second PDU session of the second URSP rule can be referred to the above description of the target service flow being sent through the first PDU session of the first URSP rule.

[0115] The UE associates application data with the corresponding PDU session for transmission based on the received URSP. The mechanism is as follows: When the application layer sends data, the UE uses URSP rules to check whether the characteristics of the application data match the Traffic Descriptor of a certain rule in the URSP. The order of checking is determined by the priority of the URSP rules. That is, the UE checks the matching situation in order of priority. When a URSP rule's Traffic Descriptor is matched, the UE uses the RSD list under that URSP rule to bind the PDU session. When a URSP rule is matched, the UE searches for a suitable PDU session according to the priority order in the RSD. Here, the higher priority RSD is used first. If a parameter in the RSD has one or more values, the UE uses the combination of parameters to check if the PDU session exists.

[0116] 1) If it exists, bind the application data to the session for transmission;

[0117] 2) If it does not exist, the UE triggers the establishment of the PDU session, and the UE reports the attribute parameters of the PDU session in the establishment request message; furthermore,

[0118] 2.1) If the session is successfully established, the UE will bind the application data to the session for transmission;

[0119] 2.2) If the session establishment fails, the UE will search again for the existence of the PDU session based on other parameter combinations in the RSD or using parameter combinations in the next lower priority RSD (repeating step 1).

[0120] The method provided in this disclosure can detect the execution result of URSP rules and feed the execution result back to the application-side AF.

[0121] Figure 8 The URSP detection method for terminal routing selection provided in this embodiment can be executed by the target terminal.

[0122] like Figure 8 As shown, the method provided in this disclosure embodiment may include:

[0123] In S810, when initiating a target service flow, a first URSP rule matching the target service flow is determined, and the first policy segment identifier (PSI) information corresponding to the first URSP rule is obtained.

[0124] In S820, the first PSI information is reported to the first core network element. The first PSI information can be used to instruct the first core network element to generate a first service flow detection rule based on the first URSP rule obtained from the first PSI information, and to configure the first service flow detection rule to the User Plane Function (UPF) network element of the first Protocol Data Unit (PDU) session, where the first PDU session corresponds to the first URSP rule. The first service flow detection rule can be used to instruct the UPF network element to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, obtain a first detection result, and send it to the first core network element.

[0125] In an exemplary embodiment, reporting the first PSI information to a first core network element may include: if a first PDU session has already been established when the target service flow is initiated, triggering a modification process for the first PDU session; and during the modification process of the first PDU session, sending the first PSI information to a third core network element. The third core network element may be used to send the first PSI information to a second core network element. The second core network element may be used to send the first PSI information to the first core network element.

[0126] In an exemplary embodiment, reporting the first PSI information to a first core network element may include: if the first PDU session is not established when the target service flow is initiated, triggering a first PDU session establishment process; during the first PDU session establishment process, sending the first PSI information to a third core network element. The third core network element may be used to send the first PSI information to a second core network element; the second core network element may be used to send the first PSI information to the first core network element; after the first PDU session is established, sending the target service flow on the first PDU session.

[0127] In an exemplary embodiment, the method may further include: receiving a URSP rule mismatch message from the first core network element, wherein the URSP rule mismatch message may be used to indicate that the first URSP rule matched by the target terminal on the first PDU session is incorrect; rematching a second URSP rule for the target service flow according to the URSP rule mismatch message; and sending the target service flow on the second PDU session corresponding to the second URSP rule.

[0128] The first core network element can also be used to generate a URSP rule mismatch message when the first detection result indicates that the target service flow does not match the first service flow detection rule. Figure 8 Other aspects of the embodiments can be found in the other embodiments described above.

[0129] Figure 9 The terminal routing policy URSP detection method provided in the embodiment can be executed by the user plane function UPF network element of the first protocol data unit (PDU) session. The first PDU session corresponds to the first URSP rule, the first URSP rule corresponds to the first policy segmentation identifier (PSI) information, and the first URSP rule matches the target service flow initiated by the target terminal.

[0130] like Figure 9 As shown, the method provided in this disclosure embodiment may include:

[0131] In S910, the first service flow detection rule of the first URSP rule sent by the first core network element is received. The first PSI information can be used to instruct the first core network element to generate the first service flow detection rule based on the first URSP rule obtained from the first PSI information.

[0132] In S920, it is detected whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, and a first detection result is obtained.

[0133] In S930, the first detection result is transmitted to the first core network element.

[0134] In an exemplary embodiment, receiving the first service flow detection rule from the first URSP rule sent by the first core network element may include: receiving the first service flow detection rule from a second core network element. The second core network element may be used to receive the first service flow detection rule from the first core network element.

[0135] In an exemplary embodiment, transmitting the first detection result to the first core network element may include sending the first detection result to a second core network element. The second core network element may be used to send the first detection result to the first core network element.

[0136] In an exemplary embodiment, the first service flow detection rule may include at least one of a first network address descriptor, a first domain descriptor, and a first non-network address descriptor. Detecting whether a target service flow sent by the target terminal in the first PDU session matches the first service flow detection rule and obtaining a first detection result may include: detecting whether the target service flow matches the first service flow detection rule; if they do not match, the first detection result is that the target service flow does not match the first service flow detection rule; if they match, the first detection result is that the target service flow matches the first service flow detection rule.

[0137] In an exemplary embodiment, the first service flow detection rule may include a detection frequency. Specifically, detecting whether a target service flow sent by the target terminal in the first PDU session matches the first service flow detection rule and obtaining a first detection result may include: periodically detecting whether data packets in the target service flow match the first service flow detection rule according to the detection frequency, and obtaining the first detection result.

[0138] In an exemplary embodiment, the method may further include: receiving blocking indication information corresponding to the first service flow detection rule, wherein the blocking indication information can be used to instruct the UPF network element to block a target service flow that does not match the first service flow detection rule. The method may further include: if the first detection result indicates that the target service flow does not match the first service flow detection rule, then blocking the target service flow.

[0139] Figure 9 Other aspects of the embodiments can be found in the other embodiments described above.

[0140] Figure 10The terminal routing policy URSP detection method provided in the embodiments can be executed by the application function (AF) network element, but this disclosure is not limited thereto.

[0141] like Figure 10 As shown, the method provided in this disclosure embodiment may include:

[0142] In S1030, a URSP rule execution notification message sent by a first core network element is received. The URSP rule execution notification message can be used to indicate the execution status of URSP rules in a terminal or terminal group. The URSP rule may include a first URSP rule. The terminal or the terminal group may include a target terminal. The first URSP rule matches the target service flow initiated by the target terminal.

[0143] The first core network element can be used to obtain the first policy segment identifier (PSI) information corresponding to the first URSP rule reported by the target terminal, generate a first service flow detection rule based on the first URSP rule obtained from the first PSI information, and configure the first service flow detection rule to the user plane function (UPF) network element of the first protocol data unit (PDU) session, where the first PDU session corresponds to the first URSP rule. The first service flow detection rule can be used to instruct the UPF network element to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, and obtain a first detection result. The first detection result can be used to instruct the first core network element to generate the URSP rule execution notification information based on the received first detection result.

[0144] Continue to refer to Figure 10 Optionally, prior to S1030, the following may also be included:

[0145] In S1010, a URSP execution status subscription request message is sent to the first core network element. The URSP execution status subscription request message includes information about the URSP rule and information about the AF network element. The URSP execution status subscription request message can be used to instruct the first core network element to authenticate the URSP execution status subscription request message based on the information of the AF network element, and generate a URSP execution status subscription response message based on the authentication result.

[0146] In S1020, the URSP execution request subscription response message sent by the first core network element is received.

[0147] In an exemplary embodiment, the method may further include: sending URSP rule configuration information to the first core network element. The URSP rule configuration information can be used to instruct the first core network element to generate the URSP rule with reference to the URSP rule configuration information, and to receive information about the URSP rule sent by the first core network element. In this embodiment, the first core network element may also be used to generate the URSP rule with reference to the URSP rule configuration information and to receive information about the URSP rule sent by the first core network element.

[0148] Figure 10 Other aspects of the embodiments can be found in the other embodiments described above.

[0149] like Figure 11 As shown, Figure 11 The first core network element 1100 provided in the embodiment may include: an acquisition unit 1110, a generation unit 1120, a configuration unit 1130, and a receiving unit 1140. The acquisition unit 1110 can be used to acquire the first policy segment identifier (PSI) information corresponding to the first URSP rule reported by the target terminal, wherein the first URSP rule matches the target service flow initiated by the target terminal. The generation unit 1120 can be used to generate a first service flow detection rule based on the first URSP rule obtained from the first PSI information. The configuration unit 1130 can be used to configure the first service flow detection rule to the user plane function (UPF) network element of the first protocol data unit (PDU) session, wherein the first PDU session corresponds to the first URSP rule, and the first service flow detection rule can be used to instruct the UPF network element to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, thereby obtaining a first detection result. The receiving unit 1140 can be used to receive the first detection result sent by the UPF network element.

[0150] In an exemplary embodiment, the acquisition unit 1110 may further be used to: if the first PDU session has already been established when the target terminal initiates the target service flow, then in the modification process of the first PDU session triggered by the target terminal, acquire the first PSI information from the second core network element. The second core network element may be used to receive the first PSI information from a third core network element; the third core network element may be used to receive the first PSI information from the target terminal.

[0151] In an exemplary embodiment, the acquisition unit 1110 may further be used to: if the first PDU session is not established when the target terminal initiates the target service flow, then during the establishment process of the first PDU session triggered by the target terminal, acquire the first PSI information from a second core network element. The second core network element may be used to receive the first PSI information from a third core network element; the third core network element may be used to receive the first PSI information from the target terminal.

[0152] In an exemplary embodiment, the first service flow detection rule may include at least one of a first network address descriptor, a first domain descriptor, a first non-network address descriptor, etc.

[0153] In an exemplary embodiment, the first service flow detection rule may include a detection frequency, which can be used to instruct the UPF network element to periodically detect data packets in the target service flow according to the detection frequency.

[0154] In an exemplary embodiment, the first core network element 1100 may further include a sending unit, which can be used to send the first service flow detection rule to the second core network element. The second core network element can be used to send the first service flow detection rule to the UPF network element.

[0155] In an exemplary embodiment, the receiving unit 1140 may be further configured to: receive the first detection result from a second core network element. The second core network element may be configured to receive the first detection result from the UPF network element.

[0156] In an exemplary embodiment, the receiving unit 1140 may be further configured to: receive the first detection result when the first detection result indicates that the target service flow matches the first service flow detection rule; or, receive the first detection result when the first detection result indicates that the target service flow does not match the first service flow detection rule; or, receive the first detection result when the first detection result indicates that the target service flow matches or does not match the first service flow detection rule.

[0157] In an exemplary embodiment, the first core network element 1100 may further include: a generation unit, configured to generate URSP rule execution notification information based on the first detection result, wherein the URSP rule execution notification information is used to indicate the execution status of URSP rules in a terminal or terminal group, the URSP rule including the first URSP rule, and the terminal or terminal group including the target terminal. The first core network element 1100 may further include a sending unit, configured to send the URSP rule execution notification information to an application function (AF) network element.

[0158] In an exemplary embodiment, the receiving unit 1140 can further be used to receive a URSP execution status subscription request message sent by the AF network element, the URSP execution status subscription request message including information about the URSP rules and information about the AF network element. The first core network element 1100 may further include a generation unit, which can be used to authenticate the URSP execution status subscription request message based on the information of the AF network element, and generate a URSP execution status subscription response message based on the authentication result. The first core network element 1100 may further include a sending unit, which can be used to send the URSP execution request subscription response message to the AF network element.

[0159] In an exemplary embodiment, the receiving unit 1140 can also be used to receive URSP rule configuration information sent by the AF network element. The first core network element 1100 may further include a generation unit, which can be used to generate the URSP rule with reference to the URSP rule configuration information. The first core network element 1100 may further include a sending unit, which can be used to send the URSP rule information to the AF network element.

[0160] In an exemplary embodiment, the first core network element 1100 may further include a sending unit, which can be used to send blocking indication information corresponding to the first service flow detection rule. The blocking indication information can be used to instruct the UPF network element to block the target service flow that does not match the first service flow detection rule.

[0161] In an exemplary embodiment, the generation unit 1120 can also be used to generate a URSP rule mismatch message when the first detection result indicates that the target service flow does not match the first service flow detection rule, to indicate that the first URSP rule matched by the target terminal in the first PDU session is incorrect. The first core network element 1100 may also include a sending unit, which can be used to send the URSP rule mismatch message to the target terminal.

[0162] Figure 11 Other aspects of the embodiments can be found in the other embodiments described above.

[0163] like Figure 12 As shown, Figure 12The target terminal 1200 provided in the embodiment may include a determining unit 1210 and a reporting unit 1220. The determining unit 1210 can be used to determine a first URSP rule matching the target service flow when initiating a target service flow, and obtain first policy segmentation identifier (PSI) information corresponding to the first URSP rule. The reporting unit 1220 can be used to report the first PSI information to a first core network element. The first PSI information can be used to instruct the first core network element to generate a first service flow detection rule based on the first URSP rule obtained from the first PSI information, and configure the first service flow detection rule to the user plane function (UPF) network element of the first protocol data unit (PDU) session. The first core network element can be used to generate the first service flow detection rule based on the first URSP rule obtained from the first PSI information, and configure the first service flow detection rule to the user plane function (UPF) network element of the first protocol data unit (PDU) session, where the first PDU session corresponds to the first URSP rule. The UPF network element can be used to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, obtain a first detection result, and send it to the first core network element.

[0164] In an exemplary embodiment, the reporting unit 1220 can also be used to: if the first PDU session has already been established when the target service flow is initiated, trigger a modification process for the first PDU session. The target terminal 1200 may further include a sending unit, which can be used to send the first PSI information to a third core network element during the modification process of the first PDU session. In this embodiment, the third core network element can be used to send the first PSI information to a second core network element. The second core network element can be used to send the first PSI information to the first core network element.

[0165] In an exemplary embodiment, the reporting unit 1220 can also be used to: trigger the establishment process of the first PDU session if the first PDU session is not established when initiating the target service flow. The target terminal 1200 may further include a sending unit, which can be used to send the first PSI information to a third core network element during the establishment process of the first PDU session. The third core network element can be used to send the first PSI information to a second core network element; the second core network element can be used to send the first PSI information to the first core network element. The sending unit can also be used to send the target service flow on the first PDU session after the first PDU session is established.

[0166] In an exemplary embodiment, the target terminal 1200 may further include a receiving unit, configured to receive a URSP rule mismatch message from the first core network element. The URSP rule mismatch message may indicate that the first URSP rule matched by the target terminal on the first PDU session is incorrect. The determining unit 1210 may further be configured to re-match a second URSP rule for the target service flow based on the URSP rule mismatch message. The target terminal 1200 may further include a sending unit, configured to send the target service flow on the second PDU session corresponding to the second URSP rule. The first core network element may further be configured to generate the URSP rule mismatch message when the first detection result indicates that the target service flow does not match the first service flow detection rule. Figure 12 Other aspects of the embodiments can be found in the other embodiments described above.

[0167] like Figure 13 As shown, Figure 13 The User Plane Function (UPF) network element 1300 provided in this embodiment corresponds to a first Protocol Data Unit (PDU) session. The first PDU session corresponds to a first URSP rule, and the first URSP rule corresponds to a first Policy Segmentation Identifier (PSI) information. The first URSP rule matches a target service flow initiated by a target terminal. The UPF network element 1300 may include a receiving unit 1310, a detection unit 1320, and a transmission unit 1330. The receiving unit 1310 can be used to receive a first service flow detection rule from the first URSP rule sent by a first core network element. The first PSI information can be used to instruct the first core network element to generate the first service flow detection rule based on the first URSP rule obtained from the first PSI information. The detection unit 1320 can be used to detect whether the target service flow sent by the target terminal in the first PDU session matches the first service flow detection rule, and obtain a first detection result. The transmission unit 1330 can be used to transmit the first detection result to the first core network element.

[0168] In an exemplary embodiment, the receiving unit 1310 may further be used to: receive the first service flow detection rule from a second core network element. The second core network element may be used to receive the first service flow detection rule from a first core network element.

[0169] In an exemplary embodiment, the User Plane Function (UPF) network element 1300 may further include a transmitting unit, which can be used to transmit the first detection result to a second core network element. The second core network element can be used to transmit the first detection result to the first core network element.

[0170] In an exemplary embodiment, the first service flow detection rule may include at least one of a first network address descriptor, a first domain descriptor, a first non-network address descriptor, etc.

[0171] The detection unit 1320 can be used to perform the following steps: detect whether the target service flow matches the first service flow detection rule; if it does not match, the first detection result obtained is that the target service flow does not match the first service flow detection rule; if it matches, the first detection result obtained is that the target service flow matches the first service flow detection rule.

[0172] In an exemplary embodiment, the first service flow detection rule may include a detection frequency. The detection unit 1320 may be used to perform the following steps: periodically detecting whether data packets in the target service flow match the first service flow detection rule according to the detection frequency, and obtaining the first detection result.

[0173] In an exemplary embodiment, the receiving unit 1310 can also be used to receive blocking indication information corresponding to the first service flow detection rule. The blocking indication information can be used to instruct the UPF network element to block the target service flow that does not match the first service flow detection rule. The User Plane Function (UPF) network element 1300 can further include a blocking unit, which can be used to block the target service flow if the first detection result indicates that the target service flow does not match the first service flow detection rule. Figure 13 Other aspects of the embodiments can be found in the other embodiments described above.

[0174] like Figure 14 The above, Figure 14The application function AF network element 1400 provided in the embodiment may include a receiving unit 1410. The receiving unit 1410 can be used to receive URSP rule execution notification information sent by a first core network element. The URSP rule execution notification information is used to indicate the execution status of URSP rules at a terminal or terminal group. The URSP rule includes a first URSP rule, and the terminal or terminal group includes a target terminal. The first URSP rule matches a target service flow initiated by the target terminal. The first core network element can be used to obtain the first policy segment identifier (PSI) information corresponding to the first URSP rule reported by the target terminal, generate a first service flow detection rule based on the first URSP rule obtained from the first PSI information, and configure the first service flow detection rule to the user plane function (UPF) network element of a first protocol data unit (PDU) session. The first PDU session corresponds to the first URSP rule. The UPF network element can be used to detect whether the target service flow sent by the target terminal on the first PDU session matches the first service flow detection rule, and obtain a first detection result. The first core network element can also be used to receive the first detection result and generate the URSP rule execution notification information based on the first detection result.

[0175] In an exemplary embodiment, the application function (AF) network element 1400 may further include a sending unit, which can be used to send a URSP execution status subscription request message to the first core network element. The URSP execution status subscription request message includes information about the URSP rules and information about the AF network element. The first core network element is further used to authenticate the URSP execution status subscription request message based on the information of the AF network element, and generate a URSP execution status subscription response message based on the authentication result. The receiving unit 1410 may also be used to receive the URSP execution request subscription response message sent by the first core network element.

[0176] In an exemplary embodiment, the application function (AF) network element 1400 may further include a sending unit, which can be used to send URSP rule configuration information to the first core network element. The first core network element may also be used to generate the URSP rule with reference to the URSP rule configuration information. The receiving unit 1410 may also be used to receive the URSP rule information sent by the first core network element. Figure 14 Other aspects of the embodiments can be found in the other embodiments described above.

[0177] Figure 15A schematic structural diagram of a communication device 1500 according to an embodiment of the present disclosure is shown. This communication device may be a terminal or other communication devices, such as a first core network element and / or a second core network element and / or a third core network element and / or a user plane function network element and / or an application function network element. Figure 15 The communication device 1500 shown includes a processor 1510, which can call and run computer programs from memory to implement the methods in the embodiments of this disclosure. Optionally, as Figure 15 As shown, the communication device 1500 may further include a memory 1520. The processor 1510 can retrieve and run computer programs from the memory 1520 to implement the methods in the embodiments of this disclosure. The memory 1520 may be a separate device independent of the processor 1510, or it may be integrated into the processor 1510. Optionally, as... Figure 15 As shown, the communication device 1500 may further include a transceiver 1530. The processor 1510 can control the transceiver 1530 to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 1530 may include a transmitter and a receiver. The transceiver 1530 may further include an antenna, and the number of antennas may be one or more.

[0178] Optionally, the communication device 1500 may specifically be a first core network element and / or a second core network element and / or a third core network element and / or a user plane function network element and / or an application function network element in the various methods of the embodiments of the present disclosure. Furthermore, the communication device 1500 can implement the corresponding processes implemented by the first core network element and / or the second core network element and / or the third core network element and / or the user plane function network element and / or the application function network element in the various methods of the embodiments of the present disclosure. For simplicity, these will not be elaborated further here. Alternatively, the communication device 1500 may specifically be a mobile terminal / terminal in the embodiments of the present disclosure. Furthermore, the communication device 1500 can implement the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of the present disclosure. For simplicity, these will not be elaborated further here.

[0179] It should be understood that the processor in this disclosure embodiment may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this disclosure. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this disclosure can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0180] It is understood that the memory in the embodiments of this disclosure can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory. It should be understood that the above-described memory is exemplary and not limiting.

[0181] This disclosure also provides a computer-readable storage medium for storing computer programs.

[0182] Optionally, the computer-readable storage medium can be applied to the first core network element and / or the second core network element and / or the third core network element and / or the user plane function network element and / or the application function network element in the embodiments of this disclosure, and the computer program causes the computer to execute the corresponding processes implemented by the first core network element and / or the second core network element and / or the third core network element and / or the user plane function network element and / or the application function network element in the various methods of the embodiments of this disclosure. For the sake of brevity, it will not be described in detail here.

[0183] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal in the embodiments of this disclosure, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of this disclosure. For the sake of brevity, these will not be described in detail here.

[0184] This disclosure also provides a computer program product, including computer program instructions. Optionally, the computer program product can be applied to the first core network element and / or the second core network element and / or the third core network element and / or the user plane function network element and / or the application function network element in the embodiments of this disclosure, and the computer program instructions cause the computer to execute the corresponding processes implemented by the first core network element and / or the second core network element and / or the third core network element and / or the user plane function network element and / or the application function network element in the various methods of the embodiments of this disclosure. For simplicity, further details are omitted here. Optionally, the computer program product can be applied to the mobile terminal / terminal in the embodiments of this disclosure, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of this disclosure. For simplicity, further details are omitted here.

[0185] This disclosure also provides a computer program. Optionally, the computer program can be applied to the first core network element and / or the second core network element and / or the third core network element and / or the user plane function network element and / or the application function network element in the embodiments of this disclosure. When the computer program runs on a computer, it causes the computer to execute the corresponding processes implemented by the first core network element and / or the second core network element and / or the third core network element and / or the user plane function network element and / or the application function network element in the various methods of the embodiments of this disclosure. For simplicity, these will not be described in detail here. Optionally, the computer program can be applied to the mobile terminal / terminal in the embodiments of this disclosure. When the computer program runs on a computer, it causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of this disclosure. For simplicity, these will not be described in detail here.

[0186] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution.

[0187] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A method for detecting a terminal routing policy URSP, characterized in that, The method is executed by a first core network element, and the method includes: Obtain the first policy segment identifier (PSI) information corresponding to the first URSP rule reported by the target terminal, and match the first URSP rule with the target service flow initiated by the target terminal. The first URSP rule is obtained based on the first PSI information. Some or all of the parameters in the first URSP rule are selected to generate a first service flow detection rule. The first service flow detection rule includes the detection frequency. The first service flow detection rule is configured to the user plane function UPF network element of the first protocol data unit (PDU) session, the first PDU session corresponds to the first URSP rule, wherein the first service flow detection rule is used to instruct the UPF network element to periodically detect whether the data packets in the target service flow sent by the target terminal on the first PDU session match the first service flow detection rule according to the detection frequency, and obtain the first detection result; The system receives a first detection result sent by the UPF network element. The first detection result indicates whether the target service flow on the first PDU session matches the first service flow detection rule, so as to determine whether the target terminal correctly executes the URSP rule issued by the network side.

2. The method according to claim 1, characterized in that, Obtain the first policy segment identifier (PSI) information corresponding to the first URSP rule reported by the target terminal, including: If the first PDU session has already been established when the target terminal initiates the target service flow, then in the modification process of the first PDU session triggered by the target terminal, the first PSI information is obtained from the second core network element.

3. The method according to claim 1, characterized in that, Obtain the first policy segment identifier (PSI) information corresponding to the first URSP rule reported by the target terminal, including: If the first PDU session is not established when the target terminal initiates the target service flow, the first PSI information is obtained from the second core network element during the establishment process of the first PDU session triggered by the target terminal.

4. The method according to claim 1, characterized in that, The first service flow detection rule includes at least one of a first network address descriptor, a first domain descriptor, and a first non-network address descriptor.

5. The method according to claim 1, characterized in that, Receiving the first detection result sent by the UPF network element includes: When the first detection result indicates that the target service flow matches the first service flow detection rule, the first detection result is received; or... When the first detection result indicates that the target service flow does not match the first service flow detection rule, the first detection result is received; or... When the first detection result indicates that the target service flow matches or does not match the first service flow detection rule, the first detection result is received.

6. The method according to claim 1, characterized in that, Also includes: Based on the first detection result, URSP rule execution notification information is generated. The URSP rule execution notification information is used to indicate the execution status of URSP rules on a terminal or terminal group. The URSP rule includes the first URSP rule, and the terminal or terminal group includes the target terminal. The URSP rule execution notification information is sent to the application function AF network element.

7. The method according to claim 1, characterized in that, Also includes: Send blocking indication information corresponding to the first service flow detection rule. The blocking indication information is used to instruct the UPF network element to block the target service flow that does not match the first service flow detection rule.

8. A method for detecting a terminal routing policy URSP, characterized in that, The method is executed by the target terminal, and the method includes: When initiating a target service flow, a first URSP rule matching the target service flow is determined, and the first policy segment identifier (PSI) information corresponding to the first URSP rule is obtained; Report the first PSI information to the first core network element; The first PSI information is used to instruct the first core network element to obtain the first URSP rule based on the first PSI information, select some or all of the parameters in the first URSP rule to generate a first service flow detection rule, and configure the first service flow detection rule to the user plane function UPF network element of the first protocol data unit (PDU) session. The first PDU session corresponds to the first URSP rule, and the first service flow detection rule includes the detection frequency. The first service flow detection rule is used to instruct the UPF network element to periodically detect whether the data packets in the target service flow sent by the target terminal on the first PDU session match the first service flow detection rule according to the detection frequency, obtain the first detection result and send it to the first core network element; The first detection result indicates whether the target service flow on the first PDU session matches the first service flow detection rule, so as to determine whether the target terminal correctly executes the URSP rules issued by the network side.

9. A method for detecting a terminal routing policy URSP, characterized in that, The method is executed by the User Plane Function (UPF) network element of the first Protocol Data Unit (PDU) session, the first PDU session corresponds to the first URSP rule, the first URSP rule corresponds to the first Policy Segmentation Identifier (PSI) information, and the first URSP rule is matched with the target service flow initiated by the target terminal. The method includes: The first core network element receives the first URSP rule sent by the first core network element, and the first PSI information is used to instruct the first core network element to obtain the first URSP rule according to the first PSI information. The first service flow detection rule is generated by selecting some or all of the parameters in the first URSP rule according to the content of the first URSP rule. The first service flow detection rule includes the detection frequency. According to the detection frequency, the data packets in the target service flow sent by the target terminal in the first PDU session are periodically detected to see if they match the first service flow detection rule, and a first detection result is obtained. The first detection result is transmitted to the first core network element. The first detection result indicates whether the target service flow on the first PDU session matches the first service flow detection rule, so as to determine whether the target terminal correctly executes the URSP rule issued by the network side.

10. A first core network element, characterized in that, include: The acquisition unit is used to acquire the first policy segment identifier (PSI) information corresponding to the first URSP rule reported by the target terminal, wherein the first URSP rule matches the target service flow initiated by the target terminal. The generation unit is configured to obtain the first URSP rule based on the first PSI information, and select some or all of the parameters of the first URSP rule to generate a first service flow detection rule, wherein the first service flow detection rule includes a detection frequency. The configuration unit is used to configure the first service flow detection rule to the user plane function (UPF) network element of the first protocol data unit (PDU) session, wherein the first PDU session corresponds to the first URSP rule, and wherein the first service flow detection rule is used to instruct the UPF network element to periodically detect whether the data packets in the target service flow sent by the target terminal on the first PDU session match the first service flow detection rule according to the detection frequency, and obtain the first detection result; The receiving unit is used to receive the first detection result sent by the UPF network element. The first detection result indicates whether the target service flow on the first PDU session matches the first service flow detection rule, so as to determine whether the target terminal correctly executes the URSP rule issued by the network side.

11. A target terminal, characterized in that, include: The determining unit is used to determine a first URSP rule that matches the target service flow when initiating the target service flow, and to obtain the first policy segment identifier (PSI) information corresponding to the first URSP rule; The reporting unit is used to report the first PSI information to the first core network element; The first PSI information is used to instruct the first core network element to obtain the first URSP rule based on the first PSI information, select some or all of the parameters in the first URSP rule to generate a first service flow detection rule, and configure the first service flow detection rule to the user plane function UPF network element of the first protocol data unit (PDU) session. The first PDU session corresponds to the first URSP rule, and the first service flow detection rule includes the detection frequency. The first service flow detection rule is used to instruct the UPF network element to periodically detect whether the data packets in the target service flow sent by the target terminal on the first PDU session match the first service flow detection rule according to the detection frequency, obtain the first detection result and send it to the first core network element; The first detection result indicates whether the target service flow on the first PDU session matches the first service flow detection rule, so as to determine whether the target terminal correctly executes the URSP rules issued by the network side.

12. A User Plane Function (UPF) network element, characterized in that, The User Plane Function (UPF) network element corresponds to a first Protocol Data Unit (PDU) session, the first PDU session corresponds to a first URSP rule, the first URSP rule corresponds to a first Policy Segmentation Identifier (PSI) information, and the first URSP rule matches the target service flow initiated by the target terminal. The UPF network element includes: The receiving unit is configured to receive the first service flow detection rule of the first URSP rule sent by the first core network element. The first PSI information is used to instruct the first core network element to obtain the first URSP rule according to the first PSI information, and to select some or all of the parameters of the first URSP rule to generate the first service flow detection rule. The first service flow detection rule includes a detection frequency. The detection unit is configured to periodically detect whether the data packets in the target service flow sent by the target terminal in the first PDU session match the first service flow detection rules according to the detection frequency, and obtain a first detection result; The transmission unit is used to transmit the first detection result to the first core network element. The first detection result indicates whether the target service flow on the first PDU session matches the first service flow detection rule, so as to determine whether the target terminal correctly executes the URSP rule issued by the network side.

13. A communication device, characterized in that, include: One or more processors; A memory configured to store one or more programs, which, when executed by one or more processors, cause the communication device to implement the method as described in any one of claims 1 to 7; or, The method as described in claim 8; or, The method as described in claim 9.

14. A computer-readable storage medium storing a computer program, characterized in that, The computer program causes the communication device to perform the method as described in any one of claims 1 to 7; or... The method as described in claim 8; or, The method as described in claim 9.

15. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the method of any one of claims 1-7; or... The method as described in claim 8; or, The method as described in claim 9.

Images