WO2021243837A1 - 基于ursp规则的应用数据路由方法及用户设备 - Google Patents

基于ursp规则的应用数据路由方法及用户设备 Download PDF

Info

Publication number
WO2021243837A1
WO2021243837A1 PCT/CN2020/106335 CN2020106335W WO2021243837A1 WO 2021243837 A1 WO2021243837 A1 WO 2021243837A1 CN 2020106335 W CN2020106335 W CN 2020106335W WO 2021243837 A1 WO2021243837 A1 WO 2021243837A1
Authority
WO
WIPO (PCT)
Prior art keywords
parameter
pdu session
ursp rule
mapping relationship
application data
Prior art date
Application number
PCT/CN2020/106335
Other languages
English (en)
French (fr)
Inventor
付志伟
苗苗
Original Assignee
北京紫光展锐通信技术有限公司
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 北京紫光展锐通信技术有限公司 filed Critical 北京紫光展锐通信技术有限公司
Priority to US18/007,526 priority Critical patent/US20230217347A1/en
Publication of WO2021243837A1 publication Critical patent/WO2021243837A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/246—Connectivity information discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/306—Route determination based on the nature of the carried application
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/308—Route determination based on user's profile, e.g. premium users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/248—Connectivity information update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • This application relates to the technical field of communication processing, and in particular to an application data routing method and user equipment based on URSP rules.
  • UE Route Selection Policy (URSP) evaluation requires traffic descriptor (TD) parameters and URSP rules associated with the application Match the Traffic Descriptor parameter in, and then create a corresponding routing path for the application according to the route selection descriptor (Route Selection Descriptor, RSD) in the successfully matched URSP rule. How to select a routing path for application data is currently not clearly stipulated in the agreement.
  • TD traffic descriptor
  • RSD Route Selection Descriptor
  • the embodiment of the application discloses an application data routing method and user equipment based on URSP rules, so as to realize application data selection routing path and improve user experience.
  • the first aspect of the embodiments of the present application discloses an application data routing method based on URSP rules.
  • the method is applied to a user equipment UE, and the method includes the following steps:
  • the UE obtains the URSP rule list and the routing description RSD indication in the URSP rule list; the UE establishes a PDU Session according to the RSD indication;
  • the UE obtains the TD parameter in the URSP rule, and establishes a mapping relationship between the TD parameter and the PDU Session;
  • the UE obtains application data and corresponding parameters of the application data, and determines a routing path of the application data according to the corresponding parameters and the mapping relationship.
  • an application data routing device based on URSP rules including:
  • the obtaining unit is used to obtain the URSP rule list and the routing description RSD indication in the URSP rule list;
  • the processing unit is used to establish a PDU Session according to the RSD instruction
  • the acquiring unit is further configured to acquire TD parameters in the URSP rule
  • the processing unit is further configured to establish a mapping relationship between the TD parameter and the PDU Session; obtain application data and corresponding parameters of the application data, and determine the routing path of the application data according to the corresponding parameters and the mapping relationship .
  • a terminal including a processor, a memory, a communication interface, and one or more programs, the one or more programs are stored in the memory and configured to be executed by the processor,
  • the program includes instructions for executing the steps in the method described in the first aspect.
  • a fourth aspect of the embodiments of the present application discloses a computer-readable storage medium, which is characterized by storing a computer program for electronic data exchange, wherein the computer program causes a computer to execute the method described in the first aspect.
  • the fifth aspect of the embodiments of the present application discloses a computer program product, wherein the above-mentioned computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the above-mentioned computer program is operable to cause a computer to execute operations as in the embodiments of the present application. Some or all of the steps described in the first aspect.
  • the computer program product may be a software installation package.
  • the technical solution provided by this application is that the UE obtains the URSP rule list and the routing description RSD indication in the URSP rule list; the UE establishes a PDU Session according to the RSD indication, and then obtains the TD parameters in the URSP rule, and then Establish a mapping relationship between TD parameters and PDU Sessions, so that when the UE has application data, it can obtain the parameters corresponding to the application data (ie TD parameters), and then obtain the PDU Session of the corresponding parameters according to the parameters and the mapping relationship to determine The routing path of the application data is PDU Session.
  • This technical solution can make the application data and the routing path more fit, realize the matching between the application data and the routing path, and improve the user experience.
  • FIG. 1A is a system architecture diagram of an exemplary communication system provided by an embodiment of the present application.
  • FIG. 1B is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of an application data routing method based on URSP rules provided by an embodiment of the present application
  • Fig. 3 is a schematic structural diagram of an application data routing device based on URSP rules provided by an embodiment of the present application
  • Fig. 4 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • the "plurality” appearing in the embodiments of the present application refers to two or more than two.
  • the descriptions of the first, second, etc. appearing in the embodiments of this application are only used for illustration and distinguishing the description objects, and there is no order, and it does not mean that the number of devices in the embodiments of this application is particularly limited, and does not constitute a reference to this application. Any limitations of the embodiment.
  • the "connection” appearing in the embodiments of this application refers to various connection modes such as direct connection or indirect connection to realize communication between devices, which is not limited in the embodiments of this application.
  • Application APP refers to various applications installed on the device, such as video applications, browser applications, etc.
  • the protocol data unit refers to the data unit transferred between peer layers.
  • the PDU of the physical layer is a data bit (bit)
  • the PDU of the data link layer is a data frame (frame)
  • the PDU of the network layer is a packet (packet)
  • the PDU of the transport layer is a data segment (segment), and other higher levels
  • the PDU is data.
  • PDU Session Session is the granularity unit of the slice network in the fifth-generation 5G mobile communication system.
  • Network slicing is an on-demand networking method that allows operators to separate multiple virtual end-to-end networks on a unified infrastructure. Each network slicing is carried out from the wireless access network bearer network to the core network. Logic isolation to adapt to various types of applications. In a network slice, it can be divided into at least three parts: wireless network sub-slice, bearer network sub-slice, and core network sub-slice.
  • the user equipment routing option policy (UE Route Selection Policy, URSP) is one of the policy information provided by the 5G core network 5GC from the policy control function entity (Policy Control Function, PCF) to the user equipment (User Equipment, UE).
  • Policy Control Function Policy Control Function
  • UE User Equipment
  • the UE uses this strategy to determine how to route the data outbound path.
  • the UE can determine whether the detected application can be associated with an established PDU session, whether it can be routed to a non-non-3GPP path other than the PDU session, or whether a new PDU session can be established.
  • An important input data in the URSP rule is the parameters in the traffic descriptor (Traffic Descriptor, TD), which can be carried by the application when it initiates a network request.
  • Traffic Descriptor Traffic Descriptor
  • the operating system After the operating system obtains the Traffic Descriptor parameter associated with the application, and the UE obtains the URSP rule list from the network, it matches the corresponding routing descriptor RSD according to the rules evaluated by the URSP, and then selects the data according to the routing path indicated by the RSD parameter routing.
  • the technical solutions of the embodiments of the present application can be applied to an exemplary communication system 100 as shown in FIG. 1A.
  • the exemplary communication system 100 includes a terminal 110 and a network device 120, and the terminal 110 is in communication connection with the network device 120.
  • the example communication system 100 may be, for example, a global system of mobile communication (GSM) system, a code division multiple access (Code Division Multiple Access, CDMA) system, and a wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • New Radio New Radio
  • NR New Radio
  • LTE-U LTE-based access to unlicensed spectrum
  • NR-U Universal Mobile Telecommunication System
  • UMTS Universal Mobile Telecommunication System
  • the communication system in the embodiments of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, can also be applied to a dual connectivity (Dual Connectivity, DC) scenario, and can also be applied to a standalone (SA) deployment.
  • CA Carrier Aggregation
  • DC Dual Connectivity
  • the embodiment of the application does not limit the applied frequency spectrum.
  • the embodiments of this application can be applied to licensed spectrum or unlicensed spectrum.
  • the terminal 110 in the embodiment of the present application may refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or User device.
  • the terminal can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), and a wireless communication function Handheld devices, computing devices or other processing devices connected to wireless modems, relay devices, in-vehicle devices, wearable devices, terminals in the future 5G network or public land mobile network (PLMN) that will evolve in the future This is not limited in the embodiment of the present application. As shown in FIG.
  • the terminal 110 in the terminal of the embodiment of the present application may include one or more of the following components: a processor 110, a memory 120, and an input/output device 130.
  • the processor 110 is respectively communicatively connected with the memory 120 and the input/output device 130. .
  • the network device 120 in the embodiment of the present application may be a device for communicating with a terminal.
  • the network device may be an evolved NodeB (eNB or eNodeB) in an LTE system, or a cloud wireless access network (cloud wireless access network).
  • the radio access network (CRAN) scenario of the wireless controller, or the network device can be a relay device, an access point, an in-vehicle device, a wearable device, and a network device in the future 5G network or a network in the future evolved PLMN network Equipment, one or a group of antenna panels (including multiple antenna panels) of the base station in the 5G system, or, it can also be a network node that constitutes a gNB or transmission point, such as a baseband unit (BBU), or distributed A unit (distributed unit, DU), etc., is not limited in the embodiment of the present application.
  • BBU baseband unit
  • DU distributed A unit
  • the gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (AAU).
  • AAU active antenna unit
  • CU realizes part of the functions of gNB
  • DU realizes part of the functions of gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implements radio resource control (radio resource control, RRC) and packet data convergence protocol (packet data convergence protocol, PDCP) layer functions.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the DU is responsible for processing the physical layer protocol and real-time services, and realizes the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer.
  • RLC radio link control
  • MAC media access control
  • PHY physical
  • AAU realizes some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by DU , Or, sent by DU+AAU.
  • the network device may be a device including one or more of the CU node, the DU node, and the AAU node.
  • the CU can be divided into network equipment in an access network (radio access network, RAN), and the CU can also be divided into network equipment in a core network (core network, CN), which is not limited in this application.
  • the terminal 110 or the network device 120 includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through processes, for example, Linux operating systems, Unix operating systems, Android operating systems, iOS operating systems, or windows operating systems.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of this application do not specifically limit the specific structure of the execution body of the methods provided in the embodiments of this application, as long as it can be provided according to the embodiments of this application by running a program that records the codes of the methods provided in the embodiments of this application.
  • the execution subject of the method provided in the embodiment of the present application may be a terminal, or a functional module in the terminal that can call and execute the program.
  • the UE Route Selection Policy (URSP) evaluation requires the application-related path descriptor (Traffic Descriptor, TD) parameters and The Traffic Descriptor parameter in the URSP rule is matched, and then a corresponding routing path is created for the application according to the route selection descriptor (Route Selection Descriptor, RSD) in the successfully matched URSP rule. How to choose a routing path for an application is currently not clearly stipulated in the agreement.
  • Figure 2 provides an application data routing method based on URSP rules.
  • the method is implemented under the network architecture shown in Figure 1A.
  • the method shown in Figure 2 can be executed by the terminal shown in Figure 1B.
  • the method is shown in Figure 2 and includes the following steps:
  • Step S201 The UE obtains the user equipment routing option policy URSP rule list and the routing descriptor RSD indication in the URSP rule list; the UE establishes the protocol data unit session PDU Session according to the RSD indication;
  • the RSD indication in the above-mentioned URSP rule list may include multiple RSD indications, of course, it may also be one RSD indication, and this application does not limit the number of the above-mentioned RSD indications.
  • the way of establishing a PDU Session based on the RSD indication can be found in the protocol.
  • Step S202 The UE obtains the path descriptor TD parameter in the URSP rule, and establishes the mapping relationship between the TD parameter and the PDU Session;
  • the aforementioned TD parameters include one or any combination of the following:
  • One or more application identifiers (Application Identifiers, APP ID)
  • IP Descriptors One or more Internet Protocol Descriptors IP Descriptors
  • One or more data network names (Data Network Name, DNN);
  • One or more routing descriptors are One or more routing descriptors.
  • Step S203 The UE obtains application data and corresponding parameters of the application data, and determines a routing path of the application data according to the corresponding parameters and the mapping relationship.
  • the corresponding parameter of the application data may specifically be a TD parameter corresponding to the application data.
  • the type of the TD parameter in the mapping relationship needs to be the same as that of the TD parameter.
  • the above TD parameter may be DDN
  • the established mapping relationship is the mapping relationship between DDN and PDU Session
  • the above UE may obtain the corresponding DDN of the application data.
  • the DDN and the mapping relationship query the specific PDU Session1 to determine the routing path of the application data as the PDU Session1.
  • the above-mentioned TD parameter may also be APP ID+Connection Capabilities;
  • the established mapping relationship may be: the mapping relationship between APP ID+Connection Capabilities and PDU Session, which the UE can obtain The corresponding APP ID + Connection Capabilities of the application data, so that the specific PDU Session 2 can be queried through the APP ID + Connection Capabilities and the mapping relationship, so as to determine that the routing path of the application data is the PDU Session 2.
  • the UE obtains the URSP rule list and the routing description RSD indication in the URSP rule list; the UE establishes the PDU Session according to the RSD indication, then obtains the TD parameters in the URSP rule, and then establishes the relationship between the TD parameters and the PDU Session
  • the parameter corresponding to the application data ie TD parameter
  • the PDU Session of the corresponding parameter can be obtained according to the parameter and the mapping relationship, so as to determine the routing path of the application data.
  • This technical solution can make the application data and the routing path more fit, realize the matching between the application data and the routing path, and improve the user experience.
  • the foregoing determining the routing path of the application data according to the corresponding parameter and the mapping relationship specifically includes:
  • the UE obtains the first PDU Session corresponding to the corresponding parameter by querying the mapping relationship according to the corresponding parameter, and determines that the routing path of the application data is the first PDU Session.
  • the above method further includes:
  • the UE If the URSP rule is updated, the UE re-establishes a new PDU Session according to the updated URSP rule, and establishes a new mapping relationship between the new PDU Session and the TD parameter of the updated URSP rule.
  • the URSP rules There are multiple ways to update the URSP rules. For example, in an optional embodiment, if the operator of the network is changed, the URSP rules will be updated. Of course, in practical applications, it can also be the UE’s system (OS ) After the upgrade, the updated URSP rules are executed. Of course, in practical applications, the above-mentioned way of updating the URSP rules can also be a variety of other technical scenarios.
  • the UE acquiring the TD parameters in the URSP rule, and establishing the mapping relationship between the TD parameters and the PDU Session specifically includes:
  • the TD parameters in the URSP rule include: APP ID and IP Descriptor; the UE establishes a mapping relationship between APP ID, IP Descriptor and the PDU Session.
  • the UE acquiring the TD parameters in the URSP rule, and establishing the mapping relationship between the TD parameters and the PDU Session specifically includes:
  • the TD parameter in the URSP rule includes: APP ID; the UE establishes a mapping relationship between the APP ID and the PDU Session.
  • the UE acquiring the TD parameters in the URSP rule and establishing the mapping relationship between the TD parameters and the PDU Session specifically includes:
  • the TD parameter in the URSP rule includes: IP Descriptor; the UE establishes a mapping relationship between the IP Descriptor and the PDU Session.
  • the UE acquiring the TD parameter in the URSP rule, and establishing the mapping relationship between the TD parameter and the PDU Session specifically includes:
  • the UE establishes a mapping relationship between APP ID + Connection Capabilities and the PDU Session.
  • the UE acquiring the TD parameter in the URSP rule, and establishing the mapping relationship between the TD parameter and the PDU Session specifically includes:
  • the TD parameters in the URSP rule include: APP ID and FQDN; the UE establishes a mapping relationship between APP ID, target fully qualified domain name (Fully Qualified Domain Name, FQDN and the PDU Session).
  • the above technical solution uses the APP ID, IP descriptor, Domain Descriptor, DNN, and Connection Capabilities parameters specified by the TD parameters as the attributes of the network interface (Network Interface) to create a corresponding relationship (ie mapping relationship) with the PDU Session.
  • the operating system obtains the characteristic attributes of the application data, such as the APP ID corresponding to the application data, the destination IP address or FQDN information sent by the application data is included in the established correspondence (ie mapping relationship), then Application data can be routed and sent through the designated PDU Session.
  • This application does not need to change the interface between the application program and the operating system to realize the application data routing through the designated path or access to the designated network slice (ie the corresponding PDU Session), which realizes the matching of the application data and the network slice, and improves the user experience.
  • Embodiment 1 of the present application provides a method for routing application data based on URSP rules.
  • the method may specifically include: UE obtaining a certain URSP rule, a certain URSP rule includes DNN and Connection Capabilities parameters, and the UE according to the RSD included in the URSP rule Instruct the establishment of PDU Session1, then the OS first establishes the PDU Session according to the RSD indication of the URSP rule, and then the OS creates a mapping relationship between the DNN+Connection Capabilities parameter in the URSP rule and the PDU Session.
  • the application data of the data service request can route the data according to the previously created mapping relationship. Specifically, the application initiates the data service request with the corresponding parameters and can be used as the two TD parameters of DNN and Connection Capabilities to obtain the data and PDU The mode of Session correspondence.
  • the second embodiment of this application provides an application data routing method based on URSP rules.
  • the method may specifically include: the UE obtains a certain URSP rule, and a certain URSP rule contains APP ID+IP Descriptor (or APP ID+FQDN) parameters, and the UE
  • the PDU Session is established according to the RSD indication contained in the URSP rule, then the OS first establishes the PDU Session according to the RSD indication of the URSP rule, and then the OS applies the APP ID+IP Descritptor (or APP ID+FQDN) parameter in the URSP rule to the PDU Session Establish a mapping relationship.
  • the application APP ID is the APP ID and the data needs to be routed to the destination address indicated by the IP Descriptor (or FQDN) parameter, then the PDU Session can be routed.
  • the specific application (APP ID) that specifies the IP Descriptor (or FQDN) parameter routing data can be used as a way to obtain the mapping relationship between the three TD parameters and the PDU Session.
  • the third embodiment of this application provides an application data routing method based on URSP rules.
  • the method may specifically include: the UE obtains a certain URSP rule, a certain URSP rule only contains IP Descriptor (or FQDN) parameters, and the UE is based on the RSD of the URSP rule Instruct the establishment of a PDU Session, and then the OS establishes a mapping relationship between the IP Descritptor (or FQDN) parameter in the URSP rule and the PDU Session. All data routed to the destination address indicated by the IPDescriptor (or FQDN) parameter can be routed through the PDUSession.
  • the routing data to the specified IPDescriptor (or FQDN) parameter can be used as a way to obtain the corresponding relationship between the two TD parameters and the PDUSession.
  • the fourth embodiment of this application provides an application data routing method based on URSP rules.
  • the method may specifically include: the UE obtains a certain URSP rule, a certain URSP rule contains only APP ID parameters, and the UE establishes a PDU according to the RSD instructions in the URSP rule Session, the OS first establishes a PDU Session according to the RSD indication of the URSP rule. Then the OS establishes a mapping relationship between the APP ID parameter in the URSP rule and the PDU Session. Only the data of the application indicated by the APP ID can be routed through the PDU Session.
  • Fig. 3 provides an application data routing device based on URSP rules.
  • the device can be installed in a user equipment or terminal. As shown in Fig. 3, the device includes:
  • the obtaining unit 301 is configured to obtain the URSP rule list and the routing description RSD indication in the URSP rule list;
  • the processing unit 302 is configured to establish a PDU Session according to the RSD instruction
  • the obtaining unit 301 is further configured to obtain TD parameters in the URSP rule;
  • the processing unit 302 is further configured to establish a mapping relationship between the TD parameters and the PDU Session; obtain application data and corresponding parameters of the application data, and determine the routing path of the application data according to the corresponding parameters and the mapping relationship.
  • the UE obtains the URSP rule list and the routing description RSD indication in the URSP rule list; the UE establishes the PDU Session according to the RSD indication, then obtains the TD parameters in the URSP rule, and then establishes the relationship between the TD parameters and the PDU Session
  • the parameter corresponding to the application data ie TD parameter
  • the PDU Session of the corresponding parameter can be obtained according to the parameter and the mapping relationship, so as to determine the routing path of the application data.
  • This technical solution can make the application data and the routing path more fit, realize the matching between the application data and the routing path, and improve the user experience.
  • the aforementioned TD parameters include one or any combination of the following:
  • One or more application identifiers Application Identifiers
  • IP Descriptors One or more Internet Protocol Descriptors IP Descriptors
  • One or more DNNs are One or more DNNs.
  • One or more routing descriptors are One or more routing descriptors.
  • the processing unit 302 is specifically configured to query and obtain the first PDU Session corresponding to the corresponding parameter from the mapping relationship according to the corresponding parameter, and determine that the routing path of the application data is the first PDU Session.
  • the processing unit 302 is specifically configured to re-establish a new PDU Session according to the updated URSP rule when the URSP rule is updated, and establish a new mapping relationship between the new PDU Session and the TD parameter of the updated URSP rule.
  • the URSP rules There are multiple ways to update the URSP rules. For example, in an optional embodiment, if the operator of the network is changed, the URSP rules will be updated. Of course, in practical applications, it can also be the UE’s system (OS ) After the upgrade, the URSP rules are updated. Of course, in practical applications, the above-mentioned way of updating the URSP rules can also be a variety of other technical scenarios.
  • the processing unit 302 is specifically configured to: if the TD parameters in the URSP rule include: APP ID and IP Descriptor; establish a mapping relationship between APP ID, IP Descriptor and the PDU Session.
  • the processing unit 302 is specifically configured to, if the TD parameter in the URSP rule includes: APP ID; establish a mapping relationship between the APP ID and the PDU Session.
  • the processing unit 302 is specifically configured to, if the TD parameter in the URSP rule includes: IP Descriptor; establish a mapping relationship between the IP Descriptor and the PDU Session.
  • the processing unit 302 is specifically configured to establish a mapping relationship between the APP ID+Connection Capabilities and the PDU Session if the TD parameter in the URSP rule includes: APP ID+Connection Capabilities.
  • the processing unit 302 is specifically configured to, if the TD parameters in the URSP rule include: APP ID and FQDN; establish a mapping relationship between APP ID+FQDN and the PDU Session.
  • FIG. 4 is a device 70 (such as a terminal) provided by an embodiment of the present application.
  • the device 70 includes a processor 701, a memory 702, and a communication interface 703.
  • the processor 701, the memory 702, and the communication interface 703 The bus 704 is connected to each other.
  • the memory 702 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 (compact disc read-only memory, CD-ROM), the memory 702 is used for related computer programs and data.
  • the communication interface 703 is used to receive and send data.
  • the processor 701 may be one or more central processing units (CPU).
  • CPU central processing units
  • the CPU may be a single-core CPU or a multi-core CPU.
  • the processor 701 in the device 70 is configured to read the computer program code stored in the memory 702, and perform the following operations:
  • the URSP rule-based application data routing apparatus of the above-mentioned application program can all execute the steps performed by the UE in the above-mentioned URSP rule-based application data routing apparatus shown in FIG. 2.
  • An embodiment of the present application also provides a chip system.
  • the chip system includes at least one processor, a memory, and an interface circuit.
  • the memory, the transceiver, and the at least one processor are interconnected by wires, and the at least one memory
  • a computer program is stored therein; when the computer program is executed by the processor, the method flow shown in FIG. 2 is realized.
  • the embodiment of the present application also provides a computer-readable storage medium in which a computer program is stored.
  • a computer program is stored.
  • the method flow shown in FIG. 2 is implemented.
  • the embodiment of the present application also provides a computer program product.
  • the computer program product runs on a terminal, the method flow shown in FIG. 2 is realized.
  • An embodiment of the present application also provides a terminal, including a processor, a memory, a communication interface, and one or more programs, the one or more programs are stored in the memory and configured to be executed by the processor
  • the program includes instructions for executing the steps in the method of the embodiment shown in FIG. 2.
  • an electronic device includes a hardware structure and/or software template corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of the present application may divide the electronic device into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the disclosed device may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the above-mentioned units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical or other forms.
  • the units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the aforementioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable memory.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory, A number of instructions are included to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the foregoing methods of the various embodiments of the present application.
  • the aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.
  • the program can be stored in a computer-readable memory, and the memory can include: a flash disk , Read-only memory (English: Read-Only Memory, abbreviation: ROM), random access device (English: Random Access Memory, abbreviation: RAM), magnetic disk or optical disc, etc.

Abstract

本申请实施例提供一种基于URSP规则的应用数据路由方法及用户设备，所述方法包括：UE获取URSP规则列表以及URSP规则列表内的路由选择描述RSD指示；UE依据所述RSD指示建立PDU Session；UE获取所述URSP规则中的TD参数，建立所述TD参数与PDU Session之间的映射关系；UE获取应用数据以及应用数据的对应参数，依据所述对应参数和所述映射关系确定所述应用数据的路由路径。本申请提供的技术方案具有用户体验度高的优点。

Description

基于URSP规则的应用数据路由方法及用户设备 技术领域
本申请涉及通信处理技术领域，尤其涉及一种基于URSP规则的应用数据路由方法及用户设备。
背景技术
在第三代合作计划(3rd Generation Partnership Project，3GPP)协议中，用户设备路由选项策略(UE Route Selection Policy，URSP)评估需要与应用相关联的通路描述符(Traffic Descriptor，TD)参数与URSP规则中的Traffic Descriptor参数进行匹配，然后根据匹配成功的URSP规则中的路由选择描述符(Route Selection Descriptor，RSD)为应用创建相应的路由通路。如何为应用数据选择路由通路，目前协议还未明确约定。
发明内容
本申请实施例公开了一种基于URSP规则的应用数据路由方法及用户设备，以实现应用数据选择路由通路，提高用户体验度。
本申请实施例第一方面公开了基于URSP规则的应用数据路由方法，所述方法应用于用户设备UE，所述方法包括如下步骤：
UE获取URSP规则列表以及URSP规则列表内的路由选择描述RSD指示；UE依据所述RSD指示建立PDU Session；
UE获取所述URSP规则中的TD参数，建立所述TD参数与PDU Session之间的映射关系；
UE获取应用数据以及应用数据的对应参数，依据所述对应参数和所述映射关系确定所述应用数据的路由路径。
第二方面，提供一种基于URSP规则的应用数据路由装置，包括：
获取单元，用于获取URSP规则列表以及URSP规则列表内的路由选择描述RSD指示；
处理单元，用于依据所述RSD指示建立PDU Session；
所述获取单元，还用于获取所述URSP规则中的TD参数；
所述处理单元，还用于建立所述TD参数与PDU Session之间的映射关系；获取应用数据以及应用数据的对应参数，依据所述对应参数和所述映射关系确定所述应用数据的路由路径。
第三方面，提供一种终端，包括处理器、存储器、通信接口，以及一个或多个程序，所述一个或多个程序被存储在所述存储器中，并且被配置由所述处理器执行，所述程序包括用于执行第一方面所述的方法中的步骤的指令。
本申请实施例第四方面公开了一种计算机可读存储介质，其特征在于，存储用于电子数据交换的计算机程序，其中，所述计算机程序使得计算机执行第一方面所述的方法。
本申请实施例第五方面公开了一种计算机程序产品，其中，上述计算机程序产品包括存储了计算机程序的非瞬时性计算机可读存储介质，上述计算机程序可操作来使计算机执行如本申请实施例第一方面中所描述的部分或全部步骤。该计算机程序产品可以为一个软件安装包。
通过实施本申请实施例，本申请提供的技术方案UE获取URSP规则列表以及URSP规则列表内的路由选择描述RSD指示；UE依据所述RSD指示建立PDU Session，然后获取URSP规则中的TD参数，然后建立TD参数与PDU Session之间的映射关系，这样在UE具有应用数据时，可以获取该应用数据对应的参数(即TD参数)，然后依据该参数以及映射关系获取对应参数的PDU Session，从而确定该应用数据的路由路径为PDU Session。此技术方案能够让应用数据与路由路径更加的贴合，实现了应用数据与路由通路之间的匹配，提高了用户体验度。
附图说明
以下对本申请实施例用到的附图进行介绍。
图1A是本申请实施例提供的一种示例通信系统的系统架构图；
图1B是本申请实施例提供的一种终端的结构示意图；
图2是本申请实施例提供的一种基于URSP规则的应用数据路由方法的流程示意图；
图3是本申请实施例提供的一种基于URSP规则的应用数据路由装置的结 构示意图；
图4是本申请实施例提供的一种设备的结构示意图。
具体实施方式
下面结合本申请实施例中的附图对本申请实施例进行描述。
本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/“，表示前后关联对象是一种“或”的关系。
本申请实施例中出现的“多个”是指两个或两个以上。本申请实施例中出现的第一、第二等描述，仅作示意与区分描述对象之用，没有次序之分，也不表示本申请实施例中对设备个数的特别限定，不能构成对本申请实施例的任何限制。本申请实施例中出现的“连接”是指直接连接或者间接连接等各种连接方式，以实现设备间的通信，本申请实施例对此不做任何限定。
应用程序APP，是指设备安装的各种应用程序，如视频应用程序、浏览器应用程序等。
协议数据单元(Protocol Data Unit，PDU)，是指对等层次之间传递的数据单位。物理层的PDU是数据位(bit)，数据链路层的PDU是数据帧(frame)，网络层的PDU是数据包(packet)，传输层的PDU是数据段(segment)，其他更高层次的PDU是数据(data)。
PDU会话Session，是第五代5G移动通信系统中的切片网络的粒度单位。
网络切片，是一种按需组网的方式，可以让运营商在统一的基础设施上分离出多个虚拟的端到端网络，每个网络切片从无线接入网承载网再到核心网上进行逻辑隔离，以适配各种各样类型的应用。在一个网络切片中，至少可分为无线网子切片、承载网子切片和核心网子切片三部分。
用户设备路由选项策略(UE Route Selection Policy，URSP)，是5G核心网5GC从策略控制功能实体(Policy Control Function，PCF)向用户设备(User Equipment，UE)提供的策略信息之一。UE使用该策略来确定如何路由数据外向通路。通过URSP规则UE可以确定检测到的应用程序是否可以与已经建 立的PDU会话相关联，是否可以路由到PDU会话之外的非non-3GPP通路，或者是否可以建立新的PDU会话。URSP规则中一个重要的输入数据就是通路描述符(Traffic Descriptor，TD)中的参数，这些参数可以由应用在发起网络请求时携带。操作系统获取到与应用程序关联的Traffic Descriptor参数后，并且UE从网络获取到URSP规则列表后，按照URSP评估的规则匹配出相应的路由选择描述符RSD，然后按照RSD参数表示的路由通路选择数据路由。
本申请实施例的技术方案可以应用于如图1A所示的示例通信系统100，该示例通信系统100包括终端110和网络设备120，终端110与网络设备120通信连接。
该示例通信系统100例如可以是：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、免授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、免授权频谱上的NR(NR-based access tounlicensed spectrum，NR-U)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、下一代通信系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，以及车辆间(Vehicle to Vehicle，V2V)通信等，本申请实施例也可以应用于这些通信系统。可选地，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
本申请实施例对应用的频谱并不限定。例如，本申请实施例可以应用于授权频谱，也可以应用于免授权频谱。
本申请实施例中的终端110可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、中继设备、车载设备、可穿戴设备，未来5G网络中的终端或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端等，本申请实施例对此并不限定。如图1B所示，本申请实施例终端中的终端110可以包括一个或多个如下部件：处理器110、存储器120和输入输出装置130，处理器110分别与存储器120、输入输出装置130通信连接。
本申请实施例中的网络设备120可以是用于与终端通信的设备，该网络设备可以是LTE系统中的演进型基站(evoled NodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该网络设备可以为中继设备、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(baseband unit，BBU)，或，分布式单元(distributed unit，DU)等，本申请实施例并不限定。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者， 由DU+AAU发送的。可以理解的是，网络设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，可以将CU划分为接入网(radio access network，RAN)中的网络设备，也可以将CU划分为核心网(core network，CN)中的网络设备，本申请对此不做限定。
在本申请实施例中，终端110或网络设备120包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端，或者，是终端中能够调用程序并执行程序的功能模块。
目前，在第三代合作计划(3rd Generation Partnership Project,3GPP)协议中，用户设备路由选项策略(UE Route Selection Policy，URSP)评估需要与应用相关联的通路描述符(Traffic Descriptor，TD)参数与URSP规则中的Traffic Descriptor参数进行匹配，然后根据匹配成功的URSP规则中的路由选择描述符(Route Selection Descriptor，RSD)为应用创建相应的路由通路。如何为应用程序选择路由通路，目前协议还未明确约定。
参阅图2，图2提供了一种基于URSP规则的应用数据路由方法，该方法在如图1A所示网络构架下实现，如图2所示的方法可以由如图1B所示的终端执行，该方法如图2所示，包括如下步骤：
步骤S201、UE获取用户设备路由选项策略URSP规则列表以及URSP规则列表内的路由选择描述符RSD指示；UE依据所述RSD指示建立协议数据单元会话PDU Session；
在一种可选的方案中，
上述URSP规则列表中内的RSD指示可以包括多个RSD指示，当然也可 以为一个RSD指示，本申请对上述RSD指示的数量并不限制。上述依据RSD指示建立PDU Session的方式可以参见协议规定。
步骤S202、UE获取所述URSP规则中的通路描述符TD参数，建立所述TD参数与PDU Session之间的映射关系；
在一种可选的方案中，上述TD参数包括下述中的一种或任意组合：
一个或者多个应用程序标识符(Application Identifiers，APP ID)
一个或多个网际协议描述符IP Descriptors；
一个或则和多个非网际协议描述符non-IP Descriptors；
一个或多个数据网络名称(Data Network Name，DNN)；
一个或多个连接能力Connection Capabilities；
一个或多个域描述符Domain Descriptors；
一个或多个路由选择描述符。
步骤S203、UE获取应用数据以及应用数据的对应参数，依据所述对应参数和所述映射关系确定所述应用数据的路由路径。
在一种可选的方案中，上述应用数据的对应参数具体可以为应用数据对应的TD参数，需要说明的是，上述TD参数与映射关系中的TD参数类型需要相同。例如，在一种可选的实施例中，上述TD参数可以为DDN，建立的映射关系为DDN与PDU Session之间的映射关系，上述UE可以获取该应用数据的对应的DDN，这样即可以通过该DDN以及映射关系查询具体的PDU Session1，从而确定该应用数据的路由路径为该PDU Session1。又如，在另一种可选实施例中，上述TD参数还可以为APP ID+Connection Capabilities；建立的映射关系可以为：APP ID+Connection Capabilities与PDU Session之间的映射关系，上述UE可以获取该应用数据的对应的APP ID+Connection Capabilities，这样即可以通过该APP ID+Connection Capabilities以及映射关系查询具体的PDU Session2，从而确定该应用数据的路由路径为该PDU Session2。
本申请提供的技术方案UE获取URSP规则列表以及URSP规则列表内的路由选择描述RSD指示；UE依据所述RSD指示建立PDU Session，然后获取URSP规则中的TD参数，然后建立TD参数与PDU Session之间的映射关系， 这样在UE具有应用数据时，可以获取该应用数据对应的参数(即TD参数)，然后依据该参数以及映射关系获取对应参数的PDU Session，从而确定该应用数据的路由路径为PDU Session。此技术方案能够让应用数据与路由路径更加的贴合，实现了应用数据与路由通路之间的匹配，提高了用户体验度。
在一种可选的技术方案中，上述依据所述对应参数和所述映射关系确定所述应用数据的路由路径具体包括：
UE依据所述对应参数从所述映射关系中查询得到所述对应参数对应的第一PDU Session，确定所述应用数据的路由路径为所述第一PDU Session。
在一种可选的技术方案中，上述方法还包括：
若更新URSP规则时，UE依据更新后的URSP规则重新建立新的PDU Session，建立新的PDU Session与更新后的URSP规则的TD参数的新的映射关系。
上述更新URSP规则的方式可以为多种，例如，在一种可选的实施例中，若更换网络的运营商，则会更新URSP规则，当然在实际应用中，还可以是UE的系统(OS)升级后，执行的URSP规则的更新。当然在实际应用中，上述更新URSP规则的方式还可以为多种其他的技术场景。
在一种具体实现方式中，UE获取所述URSP规则中的TD参数，建立所述TD参数与PDU Session之间的映射关系具体包括：
若所述URSP规则中的TD参数包括：APP ID与IP Descriptor；所述UE建立APP ID、IP Descriptor与所述PDU Session之间的映射关系。
在另一种具体实现方式中，所述UE获取所述URSP规则中的TD参数，建立所述TD参数与PDU Session之间的映射关系具体包括：
若所述URSP规则中的TD参数包括：APP ID；所述UE建立APP ID与所述PDU Session之间的映射关系。
在又一种具体实现方式中，所述UE获取所述URSP规则中的TD参数，建立所述TD参数与PDU Session之间的映射关系具体包括：
若所述URSP规则中的TD参数包括：IP Descriptor；所述UE建立IP Descriptor与所述PDU Session之间的映射关系。
在又一种具体实现方式中，所述UE获取所述URSP规则中的TD参数， 建立所述TD参数与PDU Session之间的映射关系具体包括：
若所述URSP规则中的TD参数包括：APP ID+Connection Capabilities，所述UE建立APP ID+Connection Capabilities与所述PDU Session之间的映射关系。
在一种可选实施例中，所述UE获取所述URSP规则中的TD参数，建立所述TD参数与PDU Session之间的映射关系具体包括：
若所述URSP规则中的TD参数包括：APP ID与FQDN；所述UE建立APP ID、目标全限定域名(Fully Qualified Domain Name，FQDN与所述PDU Session之间的映射关系。
上述技术方案将TD参数指定的APP ID，IP descriptor，Domain Descriptor，DNN,Connection Capabilities参数作为网络接口(Network Interface)属性与该PDU Session创建一种对应关系(即映射关系)，当某应用发起数据业务(即应用数据)时，操作系统获取应用数据的特征属性，例如应用数据对应的APP ID，应用数据发送的目的IP地址或者FQDN信息包含在已经建立的对应关系(即映射关系)中，那么应用数据可通过指定PDU Session进行路由发送。本申请无需改变应用程序与操作系统的接口即可实现应用数据通过指定通路路由或者接入指定网络切片(即对应的PDU Session)，实现了应用数据与网络切片的匹配，提高了用户体验度。
实施例一
本申请实施例一提供了一种基于URSP规则的应用数据路由方法，该方法具体可以包括：UE获取某URSP规则，某URSP规则中包含DNN与Connection Capabilities参数，并且UE依据该URSP规则包含的RSD指示建立PDU Session1，那么OS首先根据该URSP规则的RSD指示建立PDU Session，然后OS将该URSP规则中的的DNN+Connection Capabilities参数与该PDU Session创建映射关系，当UE的应用发起相应参数的数据业务请求时，该数据业务请求的应用数据即可按照之前创建的映射关系路由数据，具体的，应用程序发起相应参数的数据业务请求即可作为DNN与Connection Capabilities这两个TD参数获取其与PDU Session对应关系的方式。
实施例二
本申请实施例二提供了一种基于URSP规则的应用数据路由方法，该方法具体可以包括：UE获取某URSP规则，某URSP规则中包含APP ID+IP Descriptor(或者APP ID+FQDN)参数，UE依据URSP规则包含的RSD指示建立PDU Session，那么OS首先根据该URSP规则的RSD指示建立PDU Session，然后OS将该URSP规则中的APP ID+IP Descritptor(或者APP ID+FQDN)参数与该PDU Session建立映射关系。如果应用程序APP ID为该APP ID并且需要向该IP Descriptor(或者FQDN)参数指示的目的地址路由数据即可通过该PDU Session进行路由。这里具体应用(APP ID)该向指定IP Descriptor(或者FQDN)参数路由数据可以作为或者上述三个TD参数获取其与PDU Session映射关系的方式。
实施例三
本申请实施例三提供了一种基于URSP规则的应用数据路由方法，该方法具体可以包括：UE获取某URSP规则，某URSP规则中仅包含IP Descriptor(或者FQDN)参数，UE依据URSP规则的RSD指示建立PDU Session，然后OS将该URSP规则中的IP Descritptor(或者FQDN)参数与该PDU Session建立映射关系。所有向该IP Descriptor(或者FQDN)参数指示的目的地址路由的数据即可通过该PDU Session进行路由。这里向指定IP Descriptor(或者FQDN)参数路由数据可以作为或者上述两个TD参数获取其与PDU Session对应关系的方式。
实施例四
本申请实施例四提供了一种基于URSP规则的应用数据路由方法，该方法具体可以包括：UE获取某URSP规则，某URSP规则中仅包含APP ID参数，UE依据URSP规则内的RSD指示建立PDU Session，那么OS首先根据该URSP规则的RSD指示建立PDU Session。然后OS将该URSP规则中的APP ID参数与该PDU Session建立映射关系。仅有该APP ID指示的应用程序的数据可通过该PDU Session进行路由。
参阅图3，图3提供了一种基于URSP规则的应用数据路由装置，该装置可以设置在用户设备或终端内，该装置如图3所示，包括：
获取单元301，用于获取URSP规则列表以及URSP规则列表内的路由选择描述RSD指示；
处理单元302，用于依据所述RSD指示建立PDU Session；
获取单元301，还用于获取所述URSP规则中的TD参数；
处理单元302，还用于建立所述TD参数与PDU Session之间的映射关系；获取应用数据以及应用数据的对应参数，依据所述对应参数和所述映射关系确定所述应用数据的路由路径。
本申请提供的技术方案UE获取URSP规则列表以及URSP规则列表内的路由选择描述RSD指示；UE依据所述RSD指示建立PDU Session，然后获取URSP规则中的TD参数，然后建立TD参数与PDU Session之间的映射关系，这样在UE具有应用数据时，可以获取该应用数据对应的参数(即TD参数)，然后依据该参数以及映射关系获取对应参数的PDU Session，从而确定该应用数据的路由路径为PDU Session。此技术方案能够让应用数据与路由路径更加的贴合，实现了应用数据与路由通路之间的匹配，提高了用户体验度。
在一种可选的方案中，上述TD参数包括下述中的一种或任意组合：
一个或者多个应用程序标识符Application Identifiers；
一个或多个网际协议描述符IP Descriptors；
一个或则和多个非网际协议描述符non-IP Descriptors；
一个或多个DNN；
一个或多个连接能力Connection Capabilities；
一个或多个域描述符Domain Descriptors；
一个或多个路由选择描述符。
在一种可选的技术方案中，
处理单元302，具体用于依据所述对应参数从所述映射关系中查询得到所述对应参数对应的第一PDU Session，确定所述应用数据的路由路径为所述第一PDU Session。
在一种可选的技术方案中，在一种可选的技术方案中，
处理单元302，具体用于若更新URSP规则时，依据更新后的URSP规则重新建立新的PDU Session，建立新的PDU Session与更新后的URSP规则的 TD参数的新的映射关系。
上述更新URSP规则的方式可以为多种，例如，在一种可选的实施例中，若更换网络的运营商，则会更新URSP规则，当然在实际应用中，还可以是UE的系统(OS)升级后，执行的URSP规则的更新。当然在实际应用中，上述更新URSP规则的方式还可以为多种其他的技术场景。
在一种具体实现方式中，在一种可选的技术方案中，
处理单元302，具体用于若所述URSP规则中的TD参数包括：APP ID与IP Descriptor；建立APP ID、IP Descriptor与所述PDU Session之间的映射关系。
在另一种具体实现方式中，在一种可选的技术方案中，
处理单元302，具体用于若所述URSP规则中的TD参数包括：APP ID；建立APP ID与所述PDU Session之间的映射关系。
在又一种具体实现方式中，在一种可选的技术方案中，
处理单元302，具体用于若所述URSP规则中的TD参数包括：IP Descriptor；建立IP Descriptor与所述PDU Session之间的映射关系。
在又一种具体实现方式中，在一种可选的技术方案中，
处理单元302，具体用于若所述URSP规则中的TD参数包括：APP ID+Connection Capabilities，建立APP ID+Connection Capabilities与所述PDU Session之间的映射关系。
在一种可选实施例中，在一种可选的技术方案中，
处理单元302，具体用于若所述URSP规则中的TD参数包括：APP ID与FQDN；建立APP ID+FQDN与所述PDU Session之间的映射关系。
请参见图4，图4是本申请实施例提供的一种设备70(例如终端)，该设备70包括处理器701、存储器702和通信接口703，所述处理器701、存储器702和通信接口703通过总线704相互连接。
存储器702包括但不限于是随机存储记忆体(random access memory，RAM)、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable read only memory，EPROM)、或便携式只读存储器(compact disc read-only memory，CD-ROM)，该存储器702用于相关计算机程序及数据。通信接口703用于接收和发送数据。
处理器701可以是一个或多个中央处理器(central processing unit，CPU)，在处理器701是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
该设备70中的处理器701用于读取所述存储器702中存储的计算机程序代码，执行以下操作：
获取URSP规则列表以及URSP规则列表内的路由选择描述RSD指示；依据所述RSD指示建立PDU Session；
获取所述URSP规则中的TD参数，建立所述TD参数与PDU Session之间的映射关系；
获取应用数据以及应用数据的对应参数，依据所述对应参数和所述映射关系确定所述应用数据的路由路径。
其中，上述方法实施例涉及的各场景的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。上述应用程序的基于URSP规则的应用数据路由装置均可执行上述图2所示的基于URSP规则的应用数据路由装置中UE所执行的步骤。
本申请实施例还提供一种芯片系统，所述芯片系统包括至少一个处理器，存储器和接口电路，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述至少一个存储器中存储有计算机程序；所述计算机程序被所述处理器执行时，图2所示的方法流程得以实现。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，当其在网络设备上运行时，图2所示的方法流程得以实现。
本申请实施例还提供一种计算机程序产品，当所述计算机程序产品在终端上运行时，图2所示的方法流程得以实现。
本申请实施例还提供一种终端，包括处理器、存储器、通信接口，以及一个或多个程序，所述一个或多个程序被存储在所述存储器中，并且被配置由所述处理器执行，所述程序包括用于执行图2所示实施例的方法中的步骤的指令。
上述主要从方法侧执行过程的角度对本申请实施例的方案进行了介绍。可 以理解的是，电子设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模板。本领域技术人员应该很容易意识到，结合本文中所提供的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对电子设备进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模板并不一定是本申请所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置，可通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如上述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
上述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部 单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
上述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储器中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储器中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本申请各个实施例上述方法的全部或部分步骤。而前述的存储器包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读存储器中，存储器可以包括：闪存盘、只读存储器(英文：Read-Only Memory，简称：ROM)、随机存取器(英文：Random Access Memory，简称：RAM)、磁盘或光盘等。
以上对本申请实施例进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的一般技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (19)

  1. 一种基于URSP规则的应用数据路由方法，其特征在于，所述方法应用于用户设备UE，所述方法包括如下步骤：
    用户设备UE获取用户设备路由选项策略URSP规则列表以及URSP规则列表内的路由选择描述RSD指示；UE依据所述RSD指示建立协议数据单元会话PDU Session；
    UE获取所述URSP规则中的通路描述符TD参数，建立所述TD参数与PDU Session之间的映射关系；
    UE获取应用数据以及应用数据的对应参数，依据所述对应参数和所述映射关系确定所述应用数据的路由路径。
  2. 根据权利要求1所述的方法，其特征在于，所述依据所述对应参数和所述映射关系确定所述应用数据的路由路径具体包括：
    所述UE依据所述对应参数从所述映射关系中查询得到所述对应参数对应的第一PDU Session，确定所述应用数据的路由路径为所述第一PDU Session。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    若更新URSP规则时，UE依据更新后的URSP规则重新建立新的PDU Session，建立新的PDU Session与更新后的URSP规则的TD参数的新的映射关系。
  4. 根据权利要求1-3任意一项所述的方法，其特征在于，所述TD参数包括下述中的一种或任意组合：
    一个或者多个应用程序标识符APP ID；
    一个或多个网际协议描述符IP Descriptors；
    一个或则和多个非网际协议描述符non-IP Descriptors；
    一个或多个数据网络名称DNN；
    一个或多个连接能力Connection Capabilities；
    一个或多个域描述符Domain Descriptors；
    一个或多个路由选择描述符。
  5. 根据权利要求1所述的方法，其特征在于，所述UE获取所述URSP规则中的TD参数，建立所述TD参数与PDU Session之间的映射关系具体包括：
    若所述URSP规则中的TD参数包括：APP ID与IP Descriptor；所述UE建立APP ID、IP Descriptor与所述PDU Session之间的映射关系。
  6. 根据权利要求1所述的方法，其特征在于，所述UE获取所述URSP规则中的TD参数，建立所述TD参数与PDU Session之间的映射关系具体包括：
    若所述URSP规则中的TD参数包括：APP ID；所述UE建立APP ID与所述PDU Session之间的映射关系。
  7. 根据权利要求1所述的方法，其特征在于，所述UE获取所述URSP规则中的TD参数，建立所述TD参数与PDU Session之间的映射关系具体包括：
    若所述URSP规则中的TD参数包括：IP Descriptor或FQDN；所述UE建立IP Descriptor或目标全限定域名FQDN与所述PDU Session之间的映射关系。
  8. 根据权利要求1所述的方法，其特征在于，所述UE获取所述URSP规则中的TD参数，建立所述TD参数与PDU Session之间的映射关系具体包括：
    若所述URSP规则中的TD参数包括：APP ID与FQDN；所述UE建立APP ID、FQDN与所述PDU Session之间的映射关系。
  9. 一种基于URSP规则的应用数据路由装置，其特征在于，包括：
    获取单元，用于获取用户设备路由选项策略URSP规则列表以及URSP规则列表内的路由选择描述RSD指示；
    处理单元，用于依据所述RSD指示建立协议数据单元会话PDU Session；
    所述获取单元，还用于获取所述URSP规则中的通路描述符TD参数；
    所述处理单元，还用于建立所述TD参数与PDU Session之间的映射关系；获取应用数据以及应用数据的对应参数，依据所述对应参数和所述映射关系确定所述应用数据的路由路径。
  10. 根据权利要求9所述的装置，其特征在于，
    所述处理单元，具体用于依据所述对应参数从所述映射关系中查询得到所述对应参数对应的第一PDU Session，确定所述应用数据的路由路径为所述第一PDU Session。
  11. 根据权利要求9所述的装置，其特征在于，
    所述处理单元，还用于若更新URSP规则时，依据更新后的URSP规则重新建立新的PDU Session，建立新的PDU Session与更新后的URSP规则的TD参数的新的映射关系。
  12. 根据权利要求9-11任意一项所述的装置，其特征在于，所述TD参数包括下述中的一种或任意组合：
    一个或者多个应用程序标识符Application Identifiers；
    一个或多个网际协议描述符IP Descriptors；
    一个或则和多个非网际协议描述符non-IP Descriptors；
    一个或多个DNN；
    一个或多个连接能力Connection Capabilities；
    一个或多个域描述符Domain Descriptors；
    一个或多个路由选择描述符。
  13. 根据权利要求9所述的装置，其特征在于，
    所述处理单元，具体用于若所述URSP规则中的TD参数包括：APP ID与IP Descriptor；所述UE建立APP ID、IP Descriptor与所述PDU Session之间的映射关系。
  14. 根据权利要求9所述的装置，其特征在于，
    所述处理单元，具体用于若所述URSP规则中的TD参数包括：APP ID；所述UE建立APP ID与所述PDU Session之间的映射关系。
  15. 根据权利要求9所述的装置，其特征在于，
    所述处理单元，具体用于若所述URSP规则中的TD参数包括：IP Descriptor或FQDN；所述UE建立IP Descriptor或FQDN与所述PDU Session之间的映射关系。
  16. 根据权利要求9所述的装置，其特征在于，
    所述处理单元，具体用于若所述URSP规则中的TD参数包括：APP ID与FQDN；所述UE建立APP ID、FQDN与所述PDU Session之间的映射关系。
  17. 一种终端，其特征在于，包括处理器、存储器、通信接口，以及一个或多个程序，所述一个或多个程序被存储在所述存储器中，并且被配置由所述处理器执行，所述程序包括用于执行如权利要求1-8任一项所述的方法中的步骤的指令。
  18. 一种计算机可读存储介质，其特征在于，存储用于电子数据交换的计算机程序，其中，所述计算机程序使得计算机执行如权利要求1-8任一项所述的方法。
  19. 一种计算机程序产品，其特征在于，所述计算机程序产品包括存储了计算机程序的非瞬时性计算机可读存储介质，所述计算机程序可操作来使计算机执行如权利要求1-8任一项所述的方法。
PCT/CN2020/106335 2020-06-01 2020-07-31 基于ursp规则的应用数据路由方法及用户设备 WO2021243837A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/007,526 US20230217347A1 (en) 2020-06-01 2020-07-31 Method for ursp rule-based application data routing, user equipment, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010486954.3 2020-06-01
CN202010486954.3A CN111698755B (zh) 2020-06-01 2020-06-01 基于ursp规则的应用数据路由方法及用户设备

Publications (1)

Publication Number Publication Date
WO2021243837A1 true WO2021243837A1 (zh) 2021-12-09

Family

ID=72479147

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/106335 WO2021243837A1 (zh) 2020-06-01 2020-07-31 基于ursp规则的应用数据路由方法及用户设备

Country Status (3)

Country Link
US (1) US20230217347A1 (zh)
CN (1) CN111698755B (zh)
WO (1) WO2021243837A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4207709A4 (en) * 2020-10-30 2024-04-24 Samsung Electronics Co Ltd ELECTRONIC DEVICE WITH A CARRIER NETWORK AND OPERATING METHOD THEREFOR
CN115333686A (zh) * 2021-05-10 2022-11-11 展讯通信（上海）有限公司 限时业务的实现方法及相关产品
CN113993176A (zh) * 2021-09-26 2022-01-28 深圳市广和通无线股份有限公司 路由选择策略更新方法、终端及网络侧设备
CN114501593B (zh) * 2021-12-29 2024-04-05 西安广和通无线软件有限公司 网络切片接入方法、装置、系统和存储介质
CN116419365A (zh) * 2021-12-31 2023-07-11 维沃移动通信有限公司 数据传输方法、装置及终端
CN116723587B (zh) * 2023-08-07 2023-11-21 荣耀终端有限公司 一种会话管理方法及电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109315004A (zh) * 2017-08-11 2019-02-05 华为技术有限公司 Pdu类型的设置方法、ue策略的设置方法及相关实体
CN109743766A (zh) * 2018-02-13 2019-05-10 华为技术有限公司 一种数据路由选择的方法及装置
US10660077B2 (en) * 2018-08-09 2020-05-19 Lenovo (Singapore) Pte Ltd Uplink transmission power allocation

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019127038A1 (zh) * 2017-12-26 2019-07-04 Oppo广东移动通信有限公司 用于数据传输的方法、终端设备和网络设备
CN110474840B (zh) * 2018-05-09 2022-05-10 华为技术有限公司 数据传输方法、装置和可读存储介质
US11496573B2 (en) * 2018-06-22 2022-11-08 Huawei Technologies Co., Ltd. Optimizing user equipment operation by conditioning multiple policies on information elements
US11039369B2 (en) * 2018-08-10 2021-06-15 Mediatek Inc. Handling 5G QoS rules on QoS operation errors
CN110557798B (zh) * 2019-08-26 2022-08-12 中国联合网络通信集团有限公司 一种确定ursp的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109315004A (zh) * 2017-08-11 2019-02-05 华为技术有限公司 Pdu类型的设置方法、ue策略的设置方法及相关实体
CN109743766A (zh) * 2018-02-13 2019-05-10 华为技术有限公司 一种数据路由选择的方法及装置
US10660077B2 (en) * 2018-08-09 2020-05-19 Lenovo (Singapore) Pte Ltd Uplink transmission power allocation

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control framework for the 5G System (5GS); Stage 2 (Release 16)", 3GPP DRAFT; 23503-G41_CORRECTION_IMPLEMENTATION_CR0344R5, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 6 April 2020 (2020-04-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051868820 *

Also Published As

Publication number Publication date
US20230217347A1 (en) 2023-07-06
CN111698755A (zh) 2020-09-22
CN111698755B (zh) 2021-11-26

Similar Documents

Publication Publication Date Title
WO2021243837A1 (zh) 基于ursp规则的应用数据路由方法及用户设备
EP3585095B1 (en) Method and device for controlling qos, smf, upf, ue, pcf and an
US11812496B2 (en) User group session management method and apparatus
WO2021223335A1 (zh) 应用程序的路由选择方法及相关装置
CN110324246B (zh) 一种通信方法及装置
CN113766534B (zh) 网络切片映射方法及相关装置
US10999768B2 (en) Session context handling method, network element, and terminal device
WO2019051671A1 (zh) 配置anr的方法、终端设备、基站和核心网设备
JP7198906B2 (ja) 能力管理方法及び通信装置
US20230199550A1 (en) Relay Management Method and Communication Apparatus
KR20210024160A (ko) 통신 방법 및 장치
WO2022171051A1 (zh) 一种通信方法和通信装置
CN109429366B (zh) 一种pdu会话处理方法及设备
WO2020048517A1 (zh) 一种rrc连接方法、设备及系统
WO2021134446A1 (zh) 一种信息处理方法和通信装置以及通信系统
US20230156833A1 (en) Packet Forwarding Method, Apparatus, and System
CN113285827A (zh) 数据传输方法、系统及相关装置
US20220263879A1 (en) Multicast session establishment method and network device
EP3499922B1 (en) Method, device and computer-readable storage medium for applying qos based on user plane data mapping
WO2020078248A1 (zh) 无线通信方法及设备
WO2021036891A1 (zh) 一种无线承载处理的方法及终端设备
US20230363024A1 (en) Transmission method, transmission apparatus, communication device, and readable storage medium
WO2019090770A1 (zh) 切换过程中确定核心网类型的方法、终端设备、接入网设备和核心网设备
EP4037368A1 (en) Communication method and communication device
US10904747B2 (en) Service data packet encapsulation method and apparatus

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20939395

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20939395

Country of ref document: EP

Kind code of ref document: A1