CN111698751B - Method and device for determining URSP rule priority - Google Patents

Method and device for determining URSP rule priority Download PDF

Info

Publication number
CN111698751B
CN111698751B CN202010434923.3A CN202010434923A CN111698751B CN 111698751 B CN111698751 B CN 111698751B CN 202010434923 A CN202010434923 A CN 202010434923A CN 111698751 B CN111698751 B CN 111698751B
Authority
CN
China
Prior art keywords
ursp rule
field
parameter
priority
ursp
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010434923.3A
Other languages
Chinese (zh)
Other versions
CN111698751A (en
Inventor
苗苗
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Spreadtrum Communications Tianjin Co Ltd
Original Assignee
Spreadtrum Communications Tianjin Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Spreadtrum Communications Tianjin Co Ltd filed Critical Spreadtrum Communications Tianjin Co Ltd
Priority to CN202010434923.3A priority Critical patent/CN111698751B/en
Publication of CN111698751A publication Critical patent/CN111698751A/en
Application granted granted Critical
Publication of CN111698751B publication Critical patent/CN111698751B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/02Communication route or path selection, e.g. power-based or shortest path routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/30Routing of multiclass traffic

Abstract

The embodiment of the application discloses a method and a device for determining the priority of URSP rules, wherein the method comprises the following steps: the method comprises the steps of obtaining at least one non-default URSP rule, wherein the non-default URSP rule comprises a path descriptor TD parameter and a URSP rule priority, determining the URSP rule priority based on the TD parameter, and the URSP rule priority is used for selecting the non-default URSP rule.

Description

Method and device for determining URSP rule priority
Technical Field
The present application relates to the field of mobile communications technologies, and in particular, to a method and an apparatus for determining a priority of a URSP rule.
Background
Currently, in the third Generation Partnership Project (3 GPP), the 5th Generation Mobile Communication (5G) core network defines a User Equipment Routing Policy (URSP), and the URSP defines a service level configuration and management Policy in an important way, so as to provide a flexible configuration and management means for functions such as network slice, service and session continuity defined by the 5G core network.
In the definition of the URSP rules in the 3GPP protocol, there is a field to identify the priority of the URSP rules. In the process of URSP evaluation, evaluation and matching are required to be carried out according to the priority order of URSP rules. However, the protocol does not explicitly specify a definition method of the priority of the specific URSP rule, and therefore, the definition of the priority of the specific URSP rule is an urgent problem to be solved.
Content of application
The embodiment of the application provides a method and a device for determining the priority of a URSP rule, and provides a technical scheme for determining the priority of the URSP rule based on a path descriptor parameter in the URSP rule.
In a first aspect, an embodiment of the present application provides a method for determining a URSP rule priority, where the method includes:
acquiring at least one non-default URSP rule, wherein the non-default URSP rule comprises a path descriptor TD parameter and a URSP rule priority;
determining the URSP rule priority based on the TD parameter, the URSP rule priority being used for selection of the non-default URSP rule.
In a second aspect, an embodiment of the present application provides an apparatus for determining a URSP rule priority, where the apparatus includes:
an obtaining unit, configured to obtain at least one non-default URSP rule, where the URSP rule includes a path descriptor TD parameter, a routing descriptor RSD parameter, and a URSP rule priority;
a determining unit configured to determine the URSP rule priority based on the TD parameter, the URSP rule priority being used for selection of the non-default URSP rule.
In a third aspect, embodiments of the present application provide a terminal device, which includes a processor, a memory, a transceiver, and one or more programs, which are stored in the memory and configured to be executed by the processor, and which include instructions for performing some or all of the steps described in the method of the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium storing a computer program for electronic data exchange, wherein the computer program causes a computer to perform some or all of the steps described in the method of the first aspect.
In a fifth aspect, the present application provides a computer program product, where the computer program product includes a non-transitory computer-readable storage medium storing a computer program, where the computer program is operable to cause a computer to perform some or all of the steps described in the method according to the first aspect of the present application. The computer program product may be a software installation package.
It can be seen that, in the embodiment of the present application, a terminal device obtains at least one non-default URSP rule, where the non-default URSP rule includes a path descriptor TD parameter and a URSP rule priority, and determines the URSP rule priority based on the TD parameter, where the URSP rule priority is used for selecting the non-default URSP rule, and a technical solution for determining the URSP rule priority based on the path descriptor parameter in the URSP rule is provided.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a schematic architecture diagram of a communication system according to an embodiment of the present application;
fig. 2 is a flowchart illustrating a method for determining a URSP priority according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an apparatus for determining a URSP priority according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
It is to be understood that reference to "at least one" in the embodiments of the present application means one or more, and "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.
The embodiment of the application relates to terminal equipment. The terminal equipment comprises equipment with wireless communication function, can be deployed on land and comprises indoor or outdoor equipment, a handheld device, a wearable device or a vehicle-mounted device; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). The terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in smart home (smart home), and the like. The terminal device may also be a handheld device with wireless communication function, a vehicle-mounted device, a wearable device, a computer device or other processing device connected to a wireless modem, a terminal device in a future 5G Network, or a terminal device in a Public Land Mobile Network (PLMN) for future evolution, and the like. The terminal devices in different networks may be called different names, for example: a user equipment, an access terminal, a subscriber unit, a subscriber Station, a Mobile Station (MS), a remote Station, a remote terminal, a Mobile device, a user terminal, a Wireless communication device, a user agent or a user equipment, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) Station, a Personal Digital Assistant (PDA), a terminal device in a 5G network or a future evolution network, etc., which are not limited in this embodiment.
Hereinafter, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.
URSP rules: in 5G, policy information related to User Equipment (UE), that is, a URSP rule, is introduced, and a terminal device is used as an executor of a policy to select a Packet Data Unit (PDU) session conforming to the URSP rule for an uplink service flow. That is, some services have certain requirements for the Data Network Name (DNN) of the PDU Session to be used, the Single Network Slice Selection Assistance Information (S-NSSAI), the Session and Service Continuity (SSC) mode (mode), and the like. It is understood that the URSP rule specifies to which applications the PDU session attributes should correspond, for example, there are multiple attributes for the PDU session, and different PDU sessions may have different attributes, and the URSP specifies to which applications the various attributes of the PDU session should correspond. For example, the first PDU session has a first attribute, and applications corresponding to the first attribute can be determined according to the URSP, so that the applications are the applications allowed to be used by the first PDU session.
In 5G, a URSP rule is introduced, and the terminal device is used as a policy executor to select a proper PDU session for the upstream service flow. In the definition of the URSP rule, there is a field to identify the URSP rule priority. In the process of URSP evaluation, evaluation and matching are required to be carried out according to the priority order of the URSP rules. However, there is no specific definition method for URSP rule priority specified in the protocol.
In order to solve the above problems, the present application provides a method for determining a URSP rule priority, which includes obtaining, by a terminal device, at least one non-default URSP rule, where the non-default URSP rule includes a pathway descriptor TD parameter and a URSP rule priority, and determining the URSP rule priority based on the TD parameter, where the URSP rule priority is used for selecting the non-default URSP rule, and provides a technical solution for determining the URSP rule priority based on the pathway descriptor parameter in the URSP rule.
Referring to fig. 1, fig. 1 is a schematic diagram of a communication system according to an embodiment of the present disclosure. As shown in fig. 1, the communication system includes a network device 110 and a terminal device 120, and the description is given by taking b-3 as an example. Network device 110 and terminal device 120 are connected by wireless communications including, but not limited to: a Long Term Evolution (LTE) system, a 5G communication system (e.g., New Radio, NR)), a communication system with a converged multiple communication technologies (e.g., a communication system with a converged LTE technology and NR technology), or a communication system suitable for future New various communication systems, such as a 6G communication system and a 7G communication system, which is not limited in this embodiment of the present invention. The technical solution of the embodiment of the present application is also applicable to different network architectures, including but not limited to a relay network architecture, a dual link architecture, a Vehicle-to-any-object communication (Vehicle-to-event) architecture, and the like. The network device may be an Access network device, such as an eNodeB, an NR base station, or an Access Point (AP), and the Access network device may be connected to a core network element through a wired connection or a wireless connection.
It should be noted that the form and number of the base station 110 and the terminal device 120 shown in fig. 1 are only for example and do not constitute a limitation to the embodiment of the present application.
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 2, fig. 2 is a flowchart illustrating a method for determining a URSP priority according to an embodiment of the present application, which is applied to the illustrated communication system. As shown in fig. 2, the method for determining URSP priority includes the following steps:
s210, acquiring at least one non-default URSP rule, wherein the non-default URSP rule comprises a path descriptor TD parameter and URSP rule priority.
The 3GPP defines a URSP rule, which includes a URSP rule priority and a path Descriptor (TD) parameter for determining PDU session selection parameters required by different Applications (APPs), such as network slice, DNN and SSC modes, etc. And the terminal equipment matches the PDU session selection parameter of the APP with the path descriptor parameter in the URSP rule according to the priority of the URSP rule to decide whether to execute the URSP rule. Through one or more of the URSP rules, the terminal equipment routes the data to be sent by the APP, including to an already established PDU session or to a newly established PDU session, so as to realize data transmission.
In this embodiment of the present application, the non-default URSP rule may be obtained by the terminal device from the network device when receiving the service to be run, or may be obtained by the terminal device from the network device in advance, which is not limited in this embodiment of the present application. The URSP is issued by a Policy Control Function (PCF) through an Access and Mobility management Function (AMF).
S220, determining the URSP rule priority based on the TD parameter, wherein the URSP rule priority is used for selecting the non-default URSP rule.
In the embodiment of the application, the terminal device starts an application in the mobile communication network, and selects the non-default rule from one or more configured non-default URSP rules by matching the TD parameter of the non-default URSP rule with the application. The terminal device obtains a suitable PDU session based on a Route Selection Descriptor (RSD) parameter of the non-default URSP rule, and the terminal device selects the default URSP rule only if obtaining a suitable PDU session fails for all selected non-default URSP rules configured for the terminal device. In an example, each configured URSP rule has a URSP rule priority value, and the terminal device selects from among the one or more configured non-default URSP rules in order of the URSP rule priority values.
In a possible embodiment, the TD parameter comprises at least one of: an Application identifier (Application Descriptors) field, an IP Descriptor (IP Descriptor) field, a Non-IP Descriptor (Non-IP Descriptors) field, a DNN field, a Connection Capabilities (connectivity Capabilities) field, a Domain Descriptors field;
the determining the URSP rule priority based on the TD parameter includes: determining that the URSP rule priority value is smaller when the number of fields in the TD parameter is larger, wherein the URSP rule priority value and the URSP rule priority are in an inverse proportion relation.
Wherein, the application identifier field may include one or more application identifiers, and the application identifiers include an Operating System (OS) Id and an OSAppID; one or more IP descriptors can be included in the IP descriptor field, including destination IP address or IPV6 prefix, destination port number, IP protocol type; the non-IP descriptor field can include one or more non-IP descriptors, and the non-IP descriptors and the IP descriptors are mutually exclusive, namely the TD parameter includes one item of the IP descriptor field and the non-IP descriptor field; the data network name DNN field may include one or more DNNs; the connection capability field may include one or more connection capabilities, the connection capabilities may include one of IP Multimedia (IMS), internet, Multimedia Messaging Service (MMS), Secure User Plane Location (SUPL), the IMS indicates an IMS server capable of connecting to the operator for network registration and signaling, the internet indicates an internet capable of accessing, the MMS indicates an MMSC capable of connecting to the operator to send and receive MMS messages, the SUPL indicates a SUPL server capable of reaching the operator for GPS retrieval of information, and the Domain descriptor field may include one or more Domain descriptors, i.e., Full Qualified Domain Names (FQDNs).
Specifically, the terminal device determines the URSP rule priority according to the number of fields in the TD parameter in the URSP rule, and the smaller the URSP rule priority value of the URSP rule is, the smaller the priority value is, the higher the priority is. The larger the number of fields in the TD parameter, the greater the matching degree of the non-default URSP rule with the application-related parameter, and therefore, the smaller the URSP rule priority value of the URSP rule determined to be the larger the number of fields in the TD parameter, the higher the URSP rule priority. For example, the TD parameter in the non-default URSP rule 1 includes a DNN field and an application descriptor field, the TD parameter in the non-default URSP rule 2 includes a DNN field, an application descriptor field, and a connection capability field, the TD parameter in the non-default URSP rule 3 includes an application descriptor field, an IP descriptor field, and a domain descriptor field, and the URSP rule priority of the non-default URSP rule 2 and the non-default URSP rule 3 is higher than the URSP rule priority of the non-default URSP rule 1 according to a determination method that the URSP rule priority value is smaller as the number of fields in the TD parameter is larger, and the URSP rule priority of the non-default URSP rule 2 is equal to the URSP rule priority of the non-default URSP rule 3. Therefore, the terminal device firstly selects the non-default URSP rule 2 and/or the non-default URSP rule 3 to match with the application program, and if the matching is not successful, the non-default URSP rule 1 is matched with the application program.
In a possible embodiment, in a case that the number of fields in the TD parameter is the same and the fields in the TD parameter are not the same, the higher the priority of the fields in the TD parameter is, the smaller the priority value of the URSP rule is determined to be, and the priorities of the fields in the TD parameter from high to low are: an application identifier field, an IP descriptor field, a destination descriptor field, a DNN field, a connection capability field, a non-IP descriptor field.
Specifically, when the number of fields in the TD parameter is the same and the fields in the TD parameter are different, for example, the TD parameter in the non-default URSP rule 2 and the non-default URSP rule 3 each include three fields, but the three fields of the TD parameter in the non-default URSP rule 2 are different from the three fields of the TD parameter in the non-default URSP rule 3, and the terminal device may determine the URSP rule priority of the non-default URSP rule according to the priority of the fields in the TD parameter. For example, since the IP descriptor field and the domain descriptor field of the TD parameter in the non-default URSP rule 3 are higher in priority than the DNN field of the TD parameter in the non-default URSP rule 2, the URSP rule priority of the non-default URSP rule 3 is higher than the URSP rule priority of the non-default URSP rule 2. Therefore, the terminal device firstly selects the non-default URSP rule 3 to match with the application program, if the matching is not successful, the non-default URSP rule 2 is selected to match with the application program, and if the matching is not successful, the non-default URSP rule 1 is matched with the application program.
In a possible embodiment, the non-default URSP rule further comprises one or more routing descriptor RSD parameters, the RSD parameters including at least one of a protocol data unit session RSD priority, a seamless offload indication field, a protocol data unit, PDU, session type field, the PDU, session type field including at least one of: a session and service continuity (SCC) mode field, a single network slice selection auxiliary information (S-NSSAI) field, a DNN field, a preferred access type field, a multi-access preferred field, a time window field and a position standard field;
the determining the URSP rule priority based on the TD parameter includes:
and in the case that the number of fields in the TD parameter is the same and the fields in the TD parameter are all the same, determining that the URSP rule priority value is smaller as the number of RSD parameters is larger.
Wherein, the seamless unloading indication field indicates whether the PDU conversation corresponding to the application can be unloaded to the non-3 GPP access network; the SCC mode field is used to indicate an SSC mode that can be used to apply a corresponding PDU session; the S-NSSAI field is used for indicating single or a plurality of S-NSSAIs supported by the corresponding PDU session; the preferred access type field indicates that the access type of the PDU session corresponding to the application is 3GPP or non-3 GPP; the DNN field is used to indicate DNN information supported by the corresponding PDU session. Further, the S-NSSAI, SSC mode, DNN and preferred access type are 5G PDU session parameters for matching existing PDU sessions or for creating new PDU sessions.
Specifically, the PCF network element may determine, according to the routing request, that the URSP rule corresponding to the terminal device may include one or more RSD parameters, and if fields of TD parameters in the non-default URSP rule are the same, the terminal device may determine the priority of the URSP rule based on the RSD parameters. The greater the number of RSD parameters included in a non-default URSP rule, the greater the degree of matching of the non-default URSP rule with application-related parameters, and thus, the smaller the priority value of the URSP rule that determines the non-default URSP rule, the higher the priority. For example, assume that non-default URSP rule 1 contains TD parameters including DNN field and application descriptor field and 2 RSD parameters; the non-default URSP rule 2 comprises TD parameters and an RSD parameter, the TD parameters comprise a DNN field and an application descriptor field, and because the fields of the TD parameters in the non-default URSP rule 1 and the non-default URSP rule 2 are the same, the number of the RSD parameters in the non-default URSP rule 1 is greater than that of the RSD parameters in the non-default URSP rule 2, and therefore the URSP rule priority of the non-default URSP rule 1 is higher than that of the non-default URSP rule 2.
In a possible embodiment, in a case that the number of the RSD parameters is the same and RSD priorities are the same, it is determined that the lower the rssp rule priority value is, the higher the network slice level corresponding to the S-NSSAI field included in the PDU type field is.
Specifically, when the terminal device starts different APPs and needs to establish a new PDU session, since a Network Slice Selection Policy (NSSP) in the URSP rule includes S-NSSAIs corresponding to the different APPs, the terminal device may select, according to a correspondence between the APPs and the S-NSSAIs, an S-NSSAI corresponding to a Network Slice level that can meet the APP requirements, and establish the PDU session. Wherein the correspondence of S-NSSAI to network slice level may depend on operator configuration. Therefore, in the case that the fields of the TD parameters are all the same, the number of RSD parameters is the same, and the RSD priorities are the same, the higher the network slice level corresponding to the S-NSSAI field is, the higher the possibility that the URSP rule can meet the APP requirement is, and the smaller the priority value of the URSP rule is determined to be.
In a possible embodiment, in a case that the number of the RSD parameters is the same and RSD priorities are the same, it is determined that the URSP rule priority value of a first URSP rule is smaller than the URSP rule priority value of a second URSP rule, the first URSP rule is the URSP rule including the seamless offload indication field in the RSD parameters, and the second URSP rule is the URSP rule not including the seamless offload indication field in the RSD parameters.
Specifically, if the seamless offload indication field is included in the RSD parameter, the RSD parameter does not include S-NSSAI, SSC pattern, DNN, and preferred access type. Thus, the URSP rule priority of a non-default URSP rule containing no seamless offload indication field in the same RSD priority parameter is higher than the URSP rule priority of a non-default URSP rule containing a seamless offload indication field, when the number of RSD parameters is the same.
Wherein the URSP rule priority value of the non-default URSP rule is less than the URSP rule priority value of a default URSP rule.
In the 3GPP protocol, only the default URSP rules are explicitly specified for the URSP rule priority. Only one of the URSP rules may be a default URSP rule and the default URSP rule should contain TD parameters of the match-all type. If the URSP includes a default URSP rule and one or more non-default URSP rules, the URSP rule priority value of any non-default URSP rule is less than the URSP rule priority value of the default URSP rule, i.e., the non-default URSP rule priority is greater than the default URSP rule priority.
It can be seen that, in the method for determining the priority of the URSP rules described in the embodiment of the present application, the terminal device obtains at least one non-default URSP rule, where the non-default URSP rule includes a pathway descriptor TD parameter and a URSP rule priority, and determines the URSP rule priority based on the TD parameter, where the URSP rule priority is used for selecting the non-default URSP rule, and a technical solution for determining the URSP rule priority based on the pathway descriptor parameter in the URSP rule is provided.
The above description has introduced the solution of the embodiment of the present application mainly from the perspective of the method-side implementation process. It is understood that the electronic device comprises corresponding hardware structures and/or software modules for performing the respective functions in order to realize the above-mentioned functions. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative elements and algorithm steps described in connection with the embodiments provided herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiment of the present application, the electronic device may be divided into the functional units according to the method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
Referring to fig. 3, fig. 3 is a block diagram of functional units of an apparatus 300 for determining a URSP rule priority according to an embodiment of the present application, where the apparatus 300 for determining a URSP rule priority is applied to a terminal device, and the apparatus 300 includes: an obtaining unit 310 and a determining unit 320, wherein,
an obtaining unit 310, configured to obtain at least one non-default URSP rule, where the non-default URSP rule includes a path descriptor TD parameter and a URSP rule priority;
a determining unit 320, configured to determine the URSP rule priority based on the TD parameter, where the URSP rule priority is used for selection of the non-default URSP rule.
Optionally, the TD parameter includes at least one of: an application identifier field, an IP descriptor field, a non-IP descriptor field, a data network name DNN field, a connection capability field and a destination descriptor field;
the determining unit 320 is specifically configured to:
determining that the URSP rule priority value is smaller when the number of fields in the TD parameter is larger, wherein the URSP rule priority value and the URSP rule priority are in an inverse proportion relation.
Optionally, the determining unit 320 is further specifically configured to:
when the number of fields in the TD parameter is the same and the fields in the TD parameter are different, determining that the lower the priority value of the URSP rule is, the higher the priority of the fields in the TD parameter is, and the priority of the fields in the TD parameter from high to low are: an application identifier field, an IP descriptor field, a destination descriptor field, a DNN field, a connection capability field, a non-IP descriptor field.
Optionally, the non-default URSP rule further includes one or more routing descriptor RSD parameters, where the RSD parameters include at least one of a protocol data unit session RSD priority, a seamless offload indication field, and a protocol data unit PDU session type field, and the PDU session type field includes at least one of: a session and service continuity (SCC) mode field, a single network slice selection auxiliary information (S-NSSAI) field, a DNN field, a preferred access type field, a multi-access preferred field, a time window field and a position standard field;
the determining unit 320 is further specifically configured to:
and in the case that the number of fields in the TD parameter is the same and the fields in the TD parameter are all the same, determining that the URSP rule priority value is smaller as the number of RSD parameters is larger.
Optionally, the determining unit 320 is further specifically configured to:
and under the condition that the number of the RSD parameters is the same and the RSD priority is the same, determining that the priority value of the URSP rule is smaller when the network slice level corresponding to the S-NSSAI field in the PDU type field is higher.
Optionally, the determining unit 320 is further specifically configured to:
and under the condition that the number of fields of the RSD parameters is the same and the RSD priorities are the same, determining that the URSP rule priority value of a first URSP rule is smaller than the URSP rule priority value of a second URSP rule, wherein the first URSP rule is a non-default URSP rule of the RSD parameters including the seamless unloading indication field, and the second URSP rule is a non-default URSP rule of the RSD parameters not including the seamless unloading indication field.
Optionally, the URSP rule priority value of the non-default URSP rule is less than the URSP rule priority value of the default URSP rule.
It can be understood that the functions of each program module of the apparatus for determining the URSP rule priority in the embodiment of the present application may be specifically implemented according to the method in the foregoing method embodiment, and the specific implementation process may refer to the related description of the foregoing method embodiment, which is not described herein again.
Referring to fig. 4, fig. 4 is a terminal device according to an embodiment of the present application, where the terminal device includes: a processor, a memory, a transceiver, and one or more programs. The processor, memory and transceiver are interconnected by a communication bus.
The memory includes, but is not limited to, Random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (CD-ROM), which is used for storing computer programs and data. The communication interface is used for receiving and transmitting data.
The processor may be one or more Central Processing Units (CPUs), and in the case of one CPU, the CPU may be a single-core CPU or a multi-core CPU.
The one or more programs are stored in the memory and configured to be executed by the processor; the program includes instructions for performing the steps of:
acquiring at least one non-default URSP rule, wherein the non-default URSP rule comprises a path descriptor TD parameter and a URSP rule priority; determining the URSP rule priority based on the TD parameter, the URSP rule priority being used for selection of the non-default URSP rule.
It should be noted that, for a specific implementation process in the embodiment of the present application, reference may be made to the specific implementation process described in the foregoing method embodiment, and details are not described herein again.
The embodiment of the present application further provides a chip system, where the chip system includes at least one processor, a memory and an interface circuit, where the memory, the transceiver and the at least one processor are interconnected by a line, and the at least one memory stores a computer program; the computer program is executed by the processor for performing part or all of the steps of any of the methods as described in the above method embodiments.
Embodiments of the present application also provide a computer storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, and the computer program enables a computer to execute part or all of the steps of any one of the methods as described in the above method embodiments.
Embodiments of the present application also provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods as described in the above method embodiments. The computer program product may be a software installation package.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the above-described division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present application.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit may be stored in a computer readable memory if it is implemented in the form of a software functional unit and sold or used as a stand-alone product. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a memory, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method of the embodiments of the present application. And the aforementioned memory comprises: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable memory, which may include: flash disk, ROM, RAM, magnetic or optical disk, and the like.
The foregoing detailed description of the embodiments of the present application has been presented to illustrate the principles and implementations of the present application, and the above description of the embodiments is only provided to help understand the method and the core concept of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims (10)

1. A method of determining a user equipment path selection policy, URSP, rule priority, the method comprising:
acquiring at least one non-default URSP rule, wherein the non-default URSP rule comprises a path descriptor TD parameter and a URSP rule priority;
determining the URSP rule priority based on the TD parameter, the URSP rule priority being used for selection of the non-default URSP rule;
determining that the smaller the URSP rule priority value is, the larger the number of fields in the TD parameter is, the smaller the URSP rule priority value is, and the URSP rule priority value and the URSP rule priority are in an inverse relation.
2. The method of claim 1, wherein the TD parameter comprises at least one of: an application identifier field, an IP descriptor field, a non-IP descriptor field, a data network name DNN field, a connection capability field, a domain descriptor field.
3. The method of claim 2, wherein said determining the URSP rule priority based on the TD parameter comprises:
when the number of fields in the TD parameter is the same and the fields in the TD parameter are different, determining that the lower the priority value of the URSP rule is, the higher the priority of the fields in the TD parameter is, and the priority of the fields in the TD parameter from high to low are: an application identifier field, an IP descriptor field, a domain descriptor field, a DNN field, a connection capability field, a non-IP descriptor field.
4. The method of claim 3 wherein the non-default URSP rule further comprises one or more routing descriptor (RSD) parameters including at least one of a Protocol Data Unit (PDU) session RSD priority, a seamless offload indication field, and a PDU session type field, wherein the PDU session type field includes at least one of: a session and service continuity (SCC) mode field, a single network slice selection auxiliary information (S-NSSAI) field, a DNN field, a preferred access type field, a multi-access preferred field, a time window field and a position standard field;
the determining the URSP rule priority based on the TD parameter includes:
and in the case that the number of fields in the TD parameter is the same and the fields in the TD parameter are all the same, determining that the URSP rule priority value is smaller as the number of RSD parameters is larger.
5. The method of claim 4, wherein said determining the URSP rule priority based on the TD parameter comprises:
and under the condition that the number of the RSD parameters is the same and the RSD priority is the same, determining that the priority value of the URSP rule is smaller when the network slice level corresponding to the S-NSSAI field in the PDU type field is higher.
6. The method of claim 4, wherein said determining the URSP rule priority based on the TD parameter comprises:
and under the condition that the number of fields of the RSD parameters is the same and the RSD priorities are the same, determining that the URSP rule priority value of a first URSP rule is smaller than the URSP rule priority value of a second URSP rule, wherein the first URSP rule is a non-default URSP rule of the RSD parameters including the seamless unloading indication field, and the second URSP rule is a non-default URSP rule of the RSD parameters not including the seamless unloading indication field.
7. The method of any of claims 1-6, wherein the URSP rule priority value of the non-default URSP rule is less than the URSP rule priority value of a default URSP rule.
8. An apparatus for determining URSP rule priority, the apparatus comprising:
an obtaining unit, configured to obtain at least one non-default URSP rule, where the URSP rule includes a pathway descriptor TD parameter and a URSP rule priority;
a determining unit to determine the URSP rule priority based on the TD parameter, the URSP rule priority being used for selection of the non-default URSP rule;
determining that the smaller the URSP rule priority value is, the larger the number of fields in the TD parameter is, the smaller the URSP rule priority value is, and the URSP rule priority value and the URSP rule priority are in an inverse relation.
9. A terminal device, characterized in that the terminal device comprises a processor, a memory, a transceiver, and one or more programs stored in the memory and configured to be executed by the processor, the programs comprising instructions for carrying out the steps of the method according to any one of claims 1-7.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program causes a computer to perform the method according to any one of claims 1-7.
CN202010434923.3A 2020-05-21 2020-05-21 Method and device for determining URSP rule priority Active CN111698751B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010434923.3A CN111698751B (en) 2020-05-21 2020-05-21 Method and device for determining URSP rule priority

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010434923.3A CN111698751B (en) 2020-05-21 2020-05-21 Method and device for determining URSP rule priority

Publications (2)

Publication Number Publication Date
CN111698751A CN111698751A (en) 2020-09-22
CN111698751B true CN111698751B (en) 2021-02-09

Family

ID=72478095

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010434923.3A Active CN111698751B (en) 2020-05-21 2020-05-21 Method and device for determining URSP rule priority

Country Status (1)

Country Link
CN (1) CN111698751B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115379499A (en) * 2021-05-19 2022-11-22 华为技术有限公司 Communication method, device and system
US20230052670A1 (en) * 2021-08-12 2023-02-16 Chien-Chun Huang-Fu Enhancement of ursp association
CN113676905B (en) * 2021-08-13 2022-11-11 展讯通信(上海)有限公司 Application identifier determining method, application data transmission method and related product

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110557798A (en) * 2019-08-26 2019-12-10 中国联合网络通信集团有限公司 method and device for determining URSP
US10602422B1 (en) * 2018-12-10 2020-03-24 Verizon Patent And Licensing Inc. Application-based user equipment route selection policy mapping
CN111034268A (en) * 2018-08-10 2020-04-17 联发科技股份有限公司 Enhanced user equipment path selection policy rule matching

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111034268A (en) * 2018-08-10 2020-04-17 联发科技股份有限公司 Enhanced user equipment path selection policy rule matching
US10602422B1 (en) * 2018-12-10 2020-03-24 Verizon Patent And Licensing Inc. Application-based user equipment route selection policy mapping
CN110557798A (en) * 2019-08-26 2019-12-10 中国联合网络通信集团有限公司 method and device for determining URSP

Also Published As

Publication number Publication date
CN111698751A (en) 2020-09-22

Similar Documents

Publication Publication Date Title
CN110267327B (en) Service transmission method and device
CN108323245B (en) Registration and session establishment method, terminal and AMF entity
CN108684073B (en) It is a kind of registration and session establishment method, terminal and AMF entity
CN110557798B (en) Method and device for determining URSP
CN110474840B (en) Data transmission method, device and readable storage medium
CN111698751B (en) Method and device for determining URSP rule priority
CN110365727B (en) Communication method and related device
CN111835638B (en) Policy rule issuing method, device and system
CN111698755B (en) URSP rule-based application data routing method and user equipment
CN110392448B (en) Session reestablishment method, device and system
CN111404814A (en) Data transmission method and communication device
CN111801961A (en) Method and device for determining SSC mode
CN109729761A (en) Access method, terminal device and the network equipment of network
CN110650029A (en) Configuration method and device
CN113727331B (en) 5G base station deployment method and device
US10798762B2 (en) Method for establishing tunnel between local gateways, and gateway
WO2017035704A1 (en) Paging message sending method and device
WO2022021435A1 (en) Data transmission method, device, and storage medium
WO2021163901A1 (en) Session processing method and apparatus therefor
CN114401507A (en) Data transmission method, device and storage medium
CN112449398B (en) Path selection method and core network equipment
CN115842781A (en) Rule matching method and device and terminal equipment
CN111615100B (en) Data processing method and device
CN113473564B (en) Network slice switching method, PDU session establishing method and device
CN114125038B (en) Service scheduling method, device and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant