WO2023134295A1 - 数据传输方法及相关设备、计算机可读存储介质、计算机程序产品 - Google Patents

数据传输方法及相关设备、计算机可读存储介质、计算机程序产品 Download PDF

Info

Publication number
WO2023134295A1
WO2023134295A1 PCT/CN2022/132318 CN2022132318W WO2023134295A1 WO 2023134295 A1 WO2023134295 A1 WO 2023134295A1 CN 2022132318 W CN2022132318 W CN 2022132318W WO 2023134295 A1 WO2023134295 A1 WO 2023134295A1
Authority
WO
WIPO (PCT)
Prior art keywords
ursp
rsd
information
terminal
routing
Prior art date
Application number
PCT/CN2022/132318
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/340,516 priority Critical patent/US20230337109A1/en
Publication of WO2023134295A1 publication Critical patent/WO2023134295A1/zh

Links

Images

Classifications

    • 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/14—Routing performance; Theoretical aspects
    • 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
    • H04W40/20—Communication route or path selection, e.g. power-based or shortest path routing based on geographic position or location
    • 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
    • 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

Definitions

  • the present disclosure relates to the field of communication technology, in particular, to a data transmission method, a first core network element, a second core network element, a third network element, a terminal, a communication device, a computer-readable storage medium, and a computer program product.
  • the terminal/user equipment (User Equipment, UE) policy includes the terminal routing selection policy (UE Route Selection Policy, URSP), but for the content of the URSP rules in related technologies, it needs to be further expanded according to specific business requirements to support specific Business requirements.
  • UE Route Selection Policy UE Route Selection Policy
  • Embodiments of the present disclosure provide a data transmission method, a first core network element, a second core network element, a third network element, a terminal, a communication device, a computer-readable storage medium, and a computer program product, capable of generating URSP rules When considering the height of the terminal, generate URSP rules that meet the requirements of the terminal application.
  • An embodiment of the present disclosure provides a data transmission method, the method is executed by a network element of the first core network, and the method includes: generating a terminal routing policy URSP, the URSP includes a URSP rule, and the URSP rule includes a routing descriptor RSD, RSD Including height information, the height information is used to indicate that when the height of the terminal matches the height information, the RSD is selected to transmit application data; and the URSP is delivered to the terminal through the second core network element.
  • An embodiment of the present disclosure provides a data transmission method, the method is executed by a network element of the second core network, and the method includes: receiving a terminal routing selection policy URSP sent by a network element of the first core network, the URSP includes a URSP rule, and the URSP rule It includes a routing descriptor RSD, and the RSD includes height information, and the height information is used to indicate that when the height of the terminal matches the height information, the RSD is selected to transmit application data; and the URSP is sent to the terminal.
  • An embodiment of the present disclosure provides a data transmission method, the method is executed by a third network element, and the method includes: transmitting height information to a network element of the first core network; the height information is used to generate a terminal routing selection policy URSP, and the URSP includes The URSP rule, the URSP rule includes a routing descriptor RSD, the RSD includes altitude information, and the altitude information is used to indicate that when the altitude of the terminal matches the altitude information, the RSD is selected to transmit application data.
  • An embodiment of the present disclosure provides a data transmission method, the method is executed by a terminal, and the method includes: receiving a terminal routing policy URSP from a second core network element, the URSP includes a URSP rule, and the URSP rule includes a routing descriptor RSD , the RSD includes altitude information; when the altitude of the terminal matches the altitude information, select the RSD to transmit application data.
  • An embodiment of the present disclosure provides a network element of a first core network, including: a generation unit, configured to generate a terminal routing selection policy URSP, the URSP includes a URSP rule, the URSP rule includes a routing selection descriptor RSD, and the RSD includes height information, which is used for the height information Instructing that when the height of the terminal matches the height information, select the RSD to transmit application data; a sending unit configured to send the URSP to the terminal through a network element of the second core network.
  • a generation unit configured to generate a terminal routing selection policy URSP
  • the URSP includes a URSP rule
  • the URSP rule includes a routing selection descriptor RSD
  • the RSD includes height information, which is used for the height information Instructing that when the height of the terminal matches the height information, select the RSD to transmit application data
  • a sending unit configured to send the URSP to the terminal through a network element of the second core network.
  • An embodiment of the present disclosure provides a second core network element, including: a receiving unit configured to receive a terminal routing policy URSP sent by the first core network element, the URSP includes a URSP rule, and the URSP rule includes a routing descriptor RSD,
  • the RSD includes height information, and the height information is used to indicate that when the height of the terminal matches the height information, the RSD is selected to transmit application data; the sending unit is configured to send the URSP to the terminal.
  • An embodiment of the present disclosure provides a third network element, including: a sending unit, configured to transmit height information to a network element of the first core network; the height information is used to generate a terminal routing selection policy URSP, and the URSP includes a URSP rule,
  • the URSP rule includes a routing descriptor RSD, and the RSD includes altitude information, and the altitude information is used to indicate that when the altitude of the terminal matches the altitude information, the RSD is selected to transmit application data.
  • An embodiment of the present disclosure provides a terminal, including: a receiving unit, configured to receive a terminal routing policy URSP from a second core network element, the URSP includes a URSP rule, and the URSP rule includes a routing descriptor RSD, the The RSD includes altitude information; the transmission unit is configured to select the RSD to transmit application data when the altitude of the terminal matches the altitude information.
  • An embodiment of the present disclosure provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the data transmission method described in the embodiment of the present disclosure is implemented.
  • An embodiment of the present disclosure provides a communication device, including: one or more processors; a memory configured to store one or more programs, when the one or more programs are executed by the one or more processors , so that the communication device implements the data transmission method described in the embodiments of the present disclosure.
  • An embodiment of the present disclosure provides a computer program product, including a computer program.
  • the computer program is executed by a processor, the data transmission method described in the embodiments of the present disclosure is implemented.
  • the embodiment of the present disclosure expands the URSP rules according to the specific service requirements, and expands the support of specific service demands related to altitude information compared with related technologies, and can support flexible routing selection for UEs with specific altitudes. And support routing for UEs at specific heights through application-network interaction.
  • Fig. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present disclosure.
  • FIG. 2 is a system architecture diagram of a 5G network provided by an embodiment of the present disclosure.
  • Fig. 3 schematically shows a flowchart of a data transmission method according to an embodiment of the present disclosure.
  • Fig. 4 schematically shows an interaction diagram of a data transmission method according to an embodiment of the present disclosure.
  • Fig. 5 schematically shows an interaction diagram of a data transmission method according to another embodiment of the present disclosure.
  • Fig. 6 schematically shows a flowchart of a data transmission method according to another embodiment of the present disclosure.
  • Fig. 7 schematically shows a flowchart of a data transmission method according to yet another embodiment of the present disclosure.
  • Fig. 8 schematically shows a flowchart of a data transmission method according to yet another embodiment of the present disclosure.
  • Fig. 9 schematically shows a block diagram of a network element of a first core network according to an embodiment of the present disclosure.
  • Fig. 10 schematically shows a block diagram of a second core network network element according to an embodiment of the present disclosure.
  • Fig. 11 schematically shows a block diagram of a third network element according to an embodiment of the present disclosure.
  • Fig. 12 schematically shows a block diagram of a terminal according to an embodiment of the present disclosure.
  • Fig. 13 schematically shows a schematic structural diagram of a communication device according to an embodiment of the present disclosure.
  • Example embodiments will now be described more fully with reference to the accompanying drawings.
  • Example embodiments may, however, be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete and will fully convey the concept of example embodiments to those skilled in the art.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA broadband code division multiple access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the communication system 100 may include a network device 110, and the network device 110 may be a device for communicating with a terminal 120 (or called a communication terminal, terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals located within the coverage area.
  • the network device 110 can be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolution in an LTE system Evolutionary Node B, eNB or eNodeB), it can also be a base station in a 5G communication system, or a wireless controller in a Cloud Radio Access Network (Cloud Radio Access Network, CRAN), or the network device can be a mobile Switching centers, relay stations, access points, vehicle-mounted devices, wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks or in the future evolution of public land mobile networks (Public Land Mobile Network, PLMN) network equipment, etc.
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • WCDMA Wideband Code Division Multiple Access Network
  • CRAN Cloud Radio Access Network
  • the network device can be a mobile Switching centers, relay stations, access points, vehicle-mounted devices,
  • the communication system 100 may further include at least one terminal 120 located within the coverage of the network device 110 .
  • terminal includes, but is not limited to, a connection via a wired line, such as via a Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for cellular networks, wireless local area networks (Wireless Local Area Network, WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter; and/or another terminal device configured to receive/send communication signals; and/or an Internet of Things (Internet of Things, IoT) device.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Line
  • WLAN wireless local area networks
  • DVB-H networks wireless local area networks
  • AM-FM A broadcast transmitter AM-FM A broadcast transmitter
  • IoT Internet of Things
  • a terminal arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", “wireless terminal” or “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data communication capabilities; may include radiotelephones, pagers, Internet/Internet PDAs with network access, web browsers, organizers, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • a terminal may refer to an access terminal, UE, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminals in 5G networks or terminals in future evolved PLMNs, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminals 120 may perform direct-to-device (Device to Device, D2D) communication.
  • D2D Direct-to-device
  • a 5G system or a 5G network may also be called a New Radio (New Radio, NR) system or an NR network.
  • New Radio New Radio
  • FIG. 1 exemplarily shows one network device and two terminals.
  • the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within the coverage area.
  • the present disclosure The embodiment does not limit this.
  • the communication system 100 may further include other network entities such as a network policy control entity and a mobility management entity, which are not limited in this embodiment of the present disclosure.
  • a device with a communication function in the network/system in the embodiments of the present disclosure may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal 120 with a communication function, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; communication
  • the device may also include other devices in the communication system 100, such as other network entities such as a network policy control entity and a mobility management entity, which are not limited in this embodiment of the present disclosure.
  • FIG. 2 is a system architecture diagram of a 5G network according to an embodiment of the present disclosure.
  • the devices involved in the 5G network system include: terminal (UE)>radio access network (Radio Access Network, RAN), user plane Function (User Plane Function, UPF) > data network (Data Network, DN), access and mobility management (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), policy control function (Policy Control Function (PCF) > Application Function (Application Function, AF) > Authentication Server Function (AUSF), Unified Data Management (UDM), Network Slice Selection Function (NSSF) .
  • UE terminal
  • Radio Access Network Radio Access Network
  • UPF User Plane Function
  • Data Network Data Network
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • PCF Policy Control Function
  • Application Function Application Function
  • AF Application Function
  • AUSF Authentication Server Function
  • UDM Unified Data Management
  • NSSF Network Slice Selection Function
  • network elements related to policies are mainly PCF, AMF, SMF, RAN, and UE.
  • SMF is mainly responsible for the implementation of session-related policies
  • AMF is mainly responsible for the implementation of policies related to access and UE policies
  • the policy delivery and update on the two network elements (AMF and SMF) are all controlled by PCF.
  • the PCF and the UE can use a container (Container) to monitor information related to the UE policy, including the content of the UE policy, the UE policy identifier, and the like.
  • the UE sends the container to the AMF through a non-access stratum (Non Access Stratum, NAS) message, and the AMF continues to transparently transmit it to the PCF in a way that does not perceive the container or modify the container.
  • NAS Non Access Stratum
  • the downlink direction is the opposite.
  • the PCF sends the container to the AMF, and the AMF then transparently transmits the container to the UE through a NAS message.
  • UE policy includes URSP.
  • URSP contains multiple policy rules (called URSP Rules), and each URSP Rule consists of a traffic descriptor (Traffic Descriptor) and a set of route selection descriptors (Route Selection Descriptor, RSD).
  • the traffic descriptor in URSP is used to describe a specific service.
  • a flow descriptor can correspond to one or more RSDs, and each RSD corresponds to the attribute of a PDU session, that is to say, the service data corresponding to the flow descriptor can be transmitted in the PDU session corresponding to the RSD.
  • Traffic descriptor is a traffic descriptor used to describe the matching criteria. It consists of one or more components, which can include: application descriptors (Application descriptors), IP descriptors (IP descriptors, destination IP), domain descriptors (Domain descriptors , destination fully qualified domain name (Fully Qualified Domain Name, FQDN)), non-IP descriptors (Non-IP descriptors), data network name (Data Network Name, DNN) descriptor and connection capabilities (Connection Capabilities), traffic descriptors for UE uses for application matching.
  • application descriptors Application descriptors
  • IP descriptors IP descriptors, destination IP
  • Domain descriptors Domain descriptors , destination fully qualified domain name (Fully Qualified Domain Name, FQDN)
  • non-IP descriptors Non-IP descriptors
  • data network name Data Network Name, DNN
  • connection capabilities Connection Capabilities
  • This URSP rule applies when each component in the traffic descriptor matches the corresponding information from the application. This URSP rule does not apply when any of the components in the flow descriptor have the following conditions: no corresponding information from the application is available; the corresponding information from the application does not match any value in the flow descriptor component.
  • Route Selection Descriptor Precedence indicates the RSD priority, which determines the order of using RSD. When the RSD with high priority cannot be used, other RSDs are used. Route selection components represent route selection components, which describe various network resources that applications can use.
  • SSC Mode Selection SSC Mode Selection, UE
  • Network Slice Selection Network Slice Selection
  • DNN Selection DNN Selection
  • PDU Session Type Selection UE is used to match the matching application with the PDU session type
  • non-seamless offload indication Non-Seamless Offload indication
  • Access Type preference also called Access Type preference, if the UE needs to establish a PDU session for a matching application, it will indicate the preferred access type (3GPP or non-3GPP (non -3GPP) or Multi-Access (Multi-Access))).
  • Route Selection Validation Criteria also known as route selection verification criteria, describes the corresponding validation conditions, which include time window (Time Window, also known as valid time window) and location criteria (Location Criteria , which can also be referred to as a location condition), if the current time is not within the time window or the UE location does not match the location criteria, the corresponding RSD is considered invalid.
  • time window also known as valid time window
  • Location Criteria which can also be referred to as a location condition
  • SSC mode Single Network Slice Selection Assistance Information (S-NSSAI)
  • S-NSSAI Single Network Slice Selection Assistance Information
  • PDU session type PDU session attributes
  • the URSP rule in the related art cannot solve the UE routing selection problem of a specific height, and indicates a specific preferred selection problem through the interaction between the application and the network.
  • the data transmission method provided in the embodiment of FIG. 3 may be executed by a network element of the first core network.
  • the network element of the first core network may be a PCF, but the embodiments of the present disclosure are not limited thereto.
  • the method provided by the embodiment of the present disclosure may include S310 and S320 , which will be described in detail below.
  • a terminal routing selection policy URSP is generated.
  • the URSP can include one or more (two or more) URSP rules, and each URSP rule can include a routing descriptor RSD, wherein one RSD or each RSD can include height information, and the height information refers to It indicates that when the altitude of the terminal matches the altitude information in the RSD, the corresponding RSD is selected to transmit the application data of the terminal.
  • RSD routing descriptor
  • the URSP is configured to enable the UE to map a specific service flow to a corresponding data transmission session.
  • the PCF can generate multiple URSP rules in the core network, and each URSP rule can include a traffic descriptor (Traffic Descriptor) and a routing descriptor (RSD).
  • Traffic Descriptor Traffic Descriptor
  • RSD routing descriptor
  • an application on the UE starts, it can match the Traffic Descriptor in the URSP rule generated by the core network according to the traffic characteristics of the application started by the UE to determine the corresponding URSP.
  • Each URSP rule can include one or more RSDs, and corresponding RSD priorities can be configured for different RSDs in each URSP rule according to service requirements and service types.
  • the UE can select the corresponding RSD according to the RSD priorities of the generated RSDs, and transmit the data of the application program on the data transmission session corresponding to the RSD (called business data or application data).
  • the UE is used as an example for illustration, but it is not limited thereto.
  • the method provided in the present disclosure may be applicable to any UE that needs to perform routing at a specific height.
  • the height information can be a range of values or a specific value.
  • the value of the height information can be set according to actual needs. This The disclosed embodiments do not limit this.
  • the application when supporting the UAV scenario, can define a specific routing path for the flight height of the UAV. For example, assuming that the height information in the RSD is set as the height range, take 10m-30m as an example , then when the flying height of the UAV is between 10 meters and 30 meters, the UAV can officially enter the working mode to initiate video transmission. By setting other parameters in the RSD, for example, the UAV can be connected to the network at this time Slice S-NSSAI-1, select SSC mode 3 as the business continuity mode.
  • any parameter in the RSD can be specified, such as S-NSSAI, DNN, SSC mode, can be set to any value as needed.
  • the altitude information is used as an example to illustrate the altitude range.
  • the altitude information may include one or more set altitude values, for example, 10 meters, 20 meters, and 30 meters.
  • the RSD may include a route selection valid condition
  • the route selection valid condition may include a location condition; the location condition includes altitude information.
  • the RSD may include a routing valid condition, and the routing valid condition may include the altitude information.
  • the URSP rules in order to support the above-mentioned scenarios, first add highly relevant parameters (altitude information) to the URSP rules, and also supplement the corresponding parameters in the process of AF interacting with the network to affect the URSP rules, such as AF Send altitude information and/or routing indication information directly or indirectly to the PCF.
  • highly relevant parameters altitude information
  • routing indication information directly or indirectly to the PCF.
  • the Route Selection Validation Criteria is defined, and the Route Selection Validation Criteria includes Time Window and Location Criteria.
  • Time window When the condition of the time window is satisfied (that is, the current time is within the time window), the UE will execute the RSD defined in the URSP rule. If the current time is not within the time window, the UE considers the RSD to be invalid.
  • Location condition define the UE location information matching the service flow route.
  • the UE considers the RSD to be invalid.
  • the coding rules for the regions in Location Criteria are as follows:
  • E-UTRA is the abbreviation of Evolved-UMTS Terrestrial Radio Access, that is, the evolved UMTS (Universal Mobile Telecommunications System, Universal Mobile Communications System) terrestrial wireless access.
  • TAI is the abbreviation of Tracking Area Identity, that is, location area identification or tracking area identification.
  • the embodiment of the present disclosure proposes to supplement the height information in the Route Selection Validation Criteria of the URSP rule as a condition for evaluating whether the RSD is valid.
  • the height information can be used as a specific parameter of the Location Criteria, that is, a new height information is added in the Location Criteria as the location area type, that is, the location condition includes height information.
  • Another implementation method is: Add a new parameter in Route Selection Validation Criteria that is parallel to Time Window and Location Criteria: height information, that is, the route validity conditions include height information.
  • the altitude information refers to the altitude information of the UE matching the service flow route, that is, the RSD will be executed only when the UE is at the current altitude; and the RSD will not be executed when the UE is not at the current altitude.
  • the altitude information set in the RSD is configured to indicate at least one of the following:
  • the altitude information indicates that when the altitude of the terminal matches the altitude information and the current time is within the time window, select the RSD transfer application data;
  • the altitude information indicates that when the altitude of the terminal matches the altitude information and the current location matches the location information, select the RSD Transfer application data.
  • the height of the terminal matching the height information may be that the height of the terminal is within the height range; if the height information is one or more height values, the height matching height information of the terminal may be, The height of the terminal is the same as a height value or the height difference between the two is smaller than the height difference threshold.
  • the matching of the current location with the location information may be that the current location is the same as a location in the location information or the distance between the two is smaller than a distance threshold.
  • the height information can be used alone as a condition for evaluating whether the RSD is valid, but the height information can also be used together with at least one of the time window information and the location information to form a condition for evaluating whether the RSD is valid, examples are as follows:
  • Route Selection Validation Criteria contains both time window information and altitude information
  • the RSD executes the RSD.
  • the RSD is not executed.
  • the Route Selection Validation Criteria contains both the location condition and the altitude information, if the UE's current altitude is within the altitude information and the UE's current location satisfies the location condition (that is, the current location is a matching service defined in the location condition If the current altitude of the UE does not match the altitude information, or the current location of the UE does not match the location information, that is, one of the two conditions is not satisfied, the RSD will not be executed.
  • the Route Selection Validation Criteria contains both time window information, location information, and altitude information, if the current altitude of the UE matches the altitude information, the current time of the UE is within the time window, and the current altitude of the UE If the location matches the location information, execute the RSD; when the current time of the UE is not within the time window, or the current altitude of the UE does not match the altitude information, or the current location of the UE does not match the location information, that is, one of the three conditions If not, the RSD will not be executed.
  • generating the terminal routing policy URSP may include: receiving altitude information sent by a third network element; referring to the received altitude information, deciding to set the altitude information in the path selection valid condition .
  • the third network element may be an AF, but this embodiment of the disclosure is not limited thereto.
  • the PCF receives the altitude information from the AF, it can decide whether to accept the received altitude information according to its own decision. If it accepts the altitude information, it sets the altitude information in the URSP rule. If it does not accept the altitude information, it sets the altitude information in This height information is not set in URSP rules.
  • receiving the altitude information sent by the third network element may include: receiving service parameters (Service Parameters) sent by the third network element, where the service parameters may include the altitude information.
  • Service Parameters Service Parameters
  • receiving the altitude information sent by the third network element may include: receiving the altitude information from a fourth core network element.
  • the network element of the fourth core network is configured to receive the altitude information from the third network element.
  • NEF fourth core network element
  • a specific UE, or a group of UEs, or any UE associated with an AF request (a specific UE, or a group of UE(s) or any UE that the AF request may be associated with).
  • the AF can add height information in Service Parameters, that is, when the AF requests the network to select a specific route for a UE at a specific height, it instructs the PCF to consider the request of the AF when generating URSP rules, and add the height information in the Service Parameters
  • the height information carried is set in the specific Route Selection Validation Criteria.
  • AF can send the altitude information carried in Service Parameters to PCF through NEF, or directly to PCF. After receiving the information sent by AF, PCF can decide whether to accept AF's request to set URSP rules according to its own policy.
  • the AF can carry the altitude information in the existing messages and existing parameters and send it to the PCF, and can also add new messages and/or new parameters to carry the altitude information in the existing messages.
  • the added parameter is sent to the PCF, or the height information is carried in the added parameter in the added message and sent to the PCF, which is not limited in this disclosure.
  • the RSD may include route selection components.
  • generating the terminal routing policy URSP may include: receiving routing indication information sent by the third network element; referring to the routing indication information, deciding to set the value of the target component in the routing component.
  • the target component may be any one or more components in the Route selection components of RSD, such as service session continuity mode selection (SSC Mode Selection) and/or network slice selection (Network Slice Selection) and/or DNN Selection and/or PDU Session Type Selection and/or Non-Seamless Offload indication (Non-Seamless Offload indication) and/or ProSe layer 3 UE to network relay offload indication (SSC Mode Selection) and/or network slice selection (Network Slice Selection) and/or DNN Selection and/or PDU Session Type Selection and/or Non-Seamless Offload indication (Non-Seamless Offload indication) and/or ProSe layer 3 UE to network relay offload indication (SSC Mode Selection) and/or network slice selection (Network Slice Selection) and/or DNN Selection and/or PDU Session Type Selection and/or Non-Seamless Offload indication (Non-Seamless Offload indication) and/or ProSe layer 3 UE to network relay offload indication (SSC Mode Selection)
  • ProSe Layer-3UE-to-Network Relay Offload indication ProSe Layer-3UE-to-Network Relay Offload indication
  • access type preference Access Type preference
  • PDU session pair ID ProSe Layer-3UE-to-Network Relay Offload indication
  • Routing directives are configured to set values in the target component, such as a specific SSC mode, a specific S-NSSAI or list of S-NSSAI(s), a specific DNN or list of DNN(s) , a specific PDU Session Type, a specific access type preference, including one of the 3rd Generation Partnership Project (3GPP)/non-3GPP/Multi-Access, etc. or more, the following three examples are SSC Mode, PDU Session Type, and Access Type preference, but the embodiments of the present disclosure are not limited thereto.
  • receiving the routing indication information sent by the third network element may include: receiving a service parameter sent by the third network element, where the service parameter may include the routing selection indication information.
  • the PCF may directly receive the service parameter carrying the routing indication information from the AF, or indirectly receive the service parameter carrying the routing indication information from the AF through the NEF.
  • routing indication information may be added to the service parameters, or parameters may be added, and the newly added parameters include routing indication information, which is not limited in the present disclosure.
  • the route selection indication information may include service continuity indication information; the target component may include a service session continuity mode selection component SSC Mode Selection.
  • referring to the routing indication information deciding to set the value of the target component in the routing selection component may include: referring to the service continuity indication information, deciding to set the value of the service session continuity mode selection component.
  • the service continuity indication information may include a value of a service session continuity mode.
  • the service continuity indication information may be used to indicate whether to support terminal network address change and whether to maintain service continuity when the terminal network address changes.
  • deciding to set the value of the service session continuity mode selection component may include: when the service continuity indication information indicates that the terminal network address change is not supported, setting the service session The value of the continuity mode selection component is the first business session continuity mode; when the business continuity indication information indicates that the terminal network address change is supported and the business continuity does not need to be maintained, the business session continuity mode selection component is set The value of the second service session continuity mode; when the service continuity indication information indicates that the terminal network address change is supported and service continuity needs to be maintained, the value of the service session continuity mode selection component is set to the third service Session Continuity Mode.
  • service continuity indication information can be added in Service Parameters, that is, when the AF requests the network to select a specific route for a specific service flow, it instructs the PCF to consider the request of the AF when generating the PCF rule, and transfer the service
  • the continuity indication information is used to set the SSC Mode in the Route selection components in URSP.
  • SSC mode 1 the first business session continuity mode
  • SSC mode 2 second business session continuity mode
  • SSC mode 3 the third business session continuity mode
  • the route selection indication information may include protocol data unit session type indication information; the target component may include a protocol data unit session type selection component PDU Session Type Selection.
  • deciding to set the value of the target component in the routing selection component may include: referring to the protocol data unit session type indication information, deciding to set the value of the protocol data unit session type selection component value.
  • PDU session type indication information can be added in Service Parameters (the specific value can be IPv4, or IPv6, or IPv4v6; or Enternet; or Unstructured unstructured), that is, the AF requests the network to be a specific
  • the service flow selects a specific route, it instructs PCF to consider the request of AF when generating URSP rules, and uses the PDU session type indication information carried by Service Parameters to set the PDU Session Type Selection in the Route selection components in URSP.
  • the routing indication information may include preferential access type indication information; the target component includes an access type preference component Access Type preference.
  • referring to the routing indication information, deciding to set the value of the target component in the routing selection component may include: referring to the priority access type indication information, deciding to set the value of the access type preference component.
  • priority access type indication information can be added in Service Parameters (the specific value can be 3GPP access or non-3GPP access or Multi-Access multi-access), that is, the AF requests the network to be a specific When a specific route is selected for the business flow, it instructs PCF to consider the AF request when generating URSP rules, and use the priority access type indication information carried in Service Parameters to set the Access Type preference of the PDU in Route selection components in URSP .
  • Service Parameters the specific value can be 3GPP access or non-3GPP access or Multi-Access multi-access
  • the second core network element may be an AMF, but the embodiment of the present disclosure is not limited thereto.
  • the network device 110 in the embodiment of FIG. 1 may be the core network device of the communication system, and may generate multiple URSP rules, and each URSP rule may include Traffic Descriptor and RSD.
  • Each URSP rule may include Traffic Descriptor and RSD.
  • One or more application programs can be installed on the terminal 120. When an application program on the terminal 120 is started, the terminal 120 can match the Traffic Descriptor in the URSP rule according to the traffic characteristics of the started application program, and according to the corresponding Traffic Descriptor RSD, which routes data for launched applications.
  • a URSP rule may contain one or more RSDs, and each RSD may be used to indicate a corresponding PDU session.
  • the RSD may contain parameters for establishing a PDU session, such as: DNN, Network Slice Selection Policy, S-NSSAI, PDU session type and other parameters. PDU sessions corresponding to different RSDs may provide different online experience.
  • the embodiment of the present disclosure further expands the content of the URSP rule according to specific business requirements, and can support specific business demands. For example, how to perform specific routing for UEs with specific heights such as drones, and how to support routing for UEs with specific heights through the interaction between applications and the network; Indication of business continuity; it is also possible to select a specific PDU session type through the interaction between the application and the network.
  • the first core network element is PCF
  • the second core network element is AMF
  • the third network element is AF
  • the AF and PCF directly interact for illustration.
  • Fig. 4 schematically shows an interaction diagram of a data transmission method according to an embodiment of the present disclosure.
  • the method provided by the embodiment of the present disclosure may include S41 to S44 , which will be described in detail below.
  • the AF sends the height information and routing indication information to the PCF.
  • the PCF configures the URSP.
  • the PCF After receiving the altitude information and routing indication information from the AF, the PCF refers to the altitude information and routing indication information to decide whether to accept the altitude information and/or the routing indication information. If it decides to accept the altitude information, the generated URSP rule The height information is included in the RSD. If the height information is not accepted, the height information will not be included in the RSD of the generated URSP rule; if it is decided to accept the routing indication information, refer to the routing indication information and decide to set the routing component If it decides not to accept the routing indication information, it decides to set the value of the target component in the routing selection element without referring to the routing indication information.
  • the height information and routing indication information can be included in existing parameters in existing messages, or can be included in new parameters in existing messages, or can be transmitted through new messages.
  • the implementation of the present disclosure Examples are not limited to this.
  • the PCF may also directly generate the URSP.
  • the PCF sends the URSP.
  • the PCF may put the generated URSP in a container (Container) and send it to the AMF, but this embodiment of the present disclosure is not limited thereto.
  • the AMF sends the URSP.
  • the AMF After receiving the URSP, the AMF sends the URSP to the UE through the RAN.
  • the AMF may use the NAS message to directly forward the container to the UE, but the embodiment of the present disclosure is not limited thereto.
  • the UE Based on the received URSP, the UE associates the application data with the corresponding PDU session for transmission.
  • the mechanism is as follows:
  • the UE uses the URSP rules in the URSP to check whether the characteristics of the application data match the URSP rules.
  • the order of viewing is determined according to the priority (Precedence) in the URSP rule, that is, the UE checks the matching situation in turn based on the priority order, and when the Traffic Descriptor of a URSP rule is matched, use the URSP
  • the RSD list under the rule is used to bind the PDU session.
  • the UE searches for a suitable PDU session according to the Precedence order in the RSD.
  • the RSD with a higher priority is used first. If a parameter in the RSD has one or more values, the UE chooses A combination of parameters to find whether a PDU session exists:
  • the UE If it does not exist, the UE triggers the establishment of the PDU session, and the UE reports the attribute parameters of the PDU session in the establishment request message; further,
  • the UE If the session is established successfully, the UE binds the application data to the session for transmission;
  • the UE searches again for the existence of the PDU session based on other parameter combinations in the RSD or using the parameter combination in the RSD with a lower priority (loop step 1));
  • the UE checks according to the Precedence order whether the Traffic Descriptor in the second-priority URSP rules can match the characteristics of the application data flow. When the match is successful, repeat process described earlier.
  • the embodiments of the present disclosure enable the network to consider the input information of the application (including height information and/or routing indication information) when generating URSP rules through the above-mentioned interaction mode between the application and the network, so as to generate URSP rules that meet application requirements.
  • the embodiment in FIG. 5 is illustrated by taking the first core network element as PCF, the second core network element as AMF, the third core network element as AF, and the fourth core network element as NEF, and the AF and PCF interact through the NEF.
  • Fig. 5 schematically shows an interaction diagram of a data transmission method according to another embodiment of the present disclosure.
  • the method provided by the embodiment of the present disclosure may include S51 to S55 , which will be described in detail below.
  • the AF sends altitude information and routing indication information to the NEF.
  • the NEF forwards the altitude information and the routing indication information to the PCF.
  • the PCF configures the URSP.
  • the PCF After receiving the altitude information and routing indication information from the NEF, the PCF decides whether to accept the received altitude information and routing indication information, so as to generate the URSP.
  • the PCF sends the URSP to the AMF.
  • the AMF sends the URSP to the RAN.
  • the RAN forwards the URSP to the UE.
  • the data transmission method provided in the embodiment of FIG. 6 may be executed by a network element of the second core network.
  • the network element of the second core network may be an AMF.
  • the method provided by the embodiment of the present disclosure may include S610 and S620.
  • the terminal routing selection policy URSP sent by the network element of the first core network is received.
  • the URSP includes a URSP rule, and the URSP rule includes a routing descriptor RSD, where the RSD includes altitude information, and the altitude information is used to indicate that when the altitude of the terminal matches the altitude information, the RSD is selected to transmit the application data.
  • RSD routing descriptor
  • the data transmission method provided in the embodiment of FIG. 7 may be executed by a third network element, and in an exemplary embodiment, the third network element may be an AF.
  • the method provided by the embodiment of the present disclosure may include:
  • the altitude information can be used to generate the URSP.
  • the first core network element is configured to generate a terminal routing policy URSP for the terminal according to the altitude information
  • the URSP includes a URSP rule
  • the URSP rule includes a routing descriptor RSD
  • the RSD includes
  • the altitude information the altitude information may be used to indicate that when the altitude of the terminal matches the altitude information, the RSD is selected to transmit the application data.
  • the RSD may further include a routing component.
  • the method may further include: transmitting routing indication information to the first core network element; the first core network element is further configured to refer to the routing indication information and decide to set the The value of the target component.
  • the data transmission method provided in the embodiment of FIG. 8 may be executed by a terminal, but the embodiments of the present disclosure are not limited thereto.
  • the method provided by this embodiment of the present disclosure may include S810 and S820:
  • a terminal routing selection policy URSP is received from a network element of the second core network.
  • the URSP includes URSP rules, the URSP rules include a Routing Descriptor RSD, the RSD includes altitude information.
  • the first core network element 900 provided in the embodiment of FIG. 9 may include a generating unit 910 and a sending unit 920 .
  • the generating unit 910 is configured to generate a terminal routing policy URSP, the URSP includes a URSP rule, and the URSP rule includes a routing descriptor RSD, and the RSD includes height information, and the height information is used to indicate that when the height of the terminal matches the When the above height information is selected, the RSD is selected to transmit the application data.
  • the sending unit 920 is configured to send the URSP to the terminal through a network element of the second core network.
  • the RSD may include a route selection valid condition, and the route selection valid condition includes a location condition; the location condition may include the altitude information.
  • the RSD includes routing availability conditions including the altitude information.
  • the height information may be used to indicate at least one of the following:
  • the altitude information may indicate that when the altitude of the terminal matches the altitude information, and the current time is within the time window, select the RSD transmits application data;
  • the altitude information may indicate that when the altitude of the terminal matches the altitude information, and the current location matches the location information, select the RSD transmits application data.
  • the first core network element 900 may further include a receiving unit configured to receive the altitude information sent by the third network element.
  • the generating unit 910 is further configured to refer to the received altitude information and decide to set the altitude information in the route selection valid condition.
  • the receiving unit is further configured to: receive a service parameter sent by the third network element, where the service parameter includes the altitude information.
  • the receiving unit is further configured to: receive the height information from a fourth core network element.
  • the network element of the fourth core network is configured to receive the height information from the third network element.
  • the RSD may include a routing component.
  • the first core network element 900 may further include a receiving unit configured to receive routing indication information sent by the third network element.
  • the generating unit 910 is further configured to refer to the routing indication information and decide to set the value of the target component in the routing components.
  • the receiving unit is further configured to: receive a service parameter sent by the third network element, where the service parameter may include the routing indication information.
  • the routing indication information may include service continuity indication information; the target component may include a service session continuity mode selection component.
  • the generating unit 910 is further configured to: refer to the service continuity indication information, and decide to set the value of the service session continuity mode selection component.
  • the service continuity indication information may include a value of a service session continuity mode.
  • the service continuity indication information may be used to indicate whether to support terminal network address change and whether to maintain service continuity when the terminal network address changes.
  • the generating unit 910 is further configured to: when the service continuity indication information indicates that the terminal network address change is not supported, set the value of the service session continuity mode selection component to the first service session continuity mode; when the The business continuity indication information indicates that the terminal network address change is supported, and when business continuity does not need to be maintained, the value of the business session continuity mode selection component is set to the second business session continuity mode; when the business continuity indication information When indicating that the terminal network address change is supported and service continuity needs to be maintained, the value of the service session continuity mode selection component is set to the third service session continuity mode.
  • the routing indication information may include protocol data unit session type indication information; the target component may include a protocol data unit session type selection component.
  • the generating unit 910 is further configured to: refer to the PDU session type indication information, and decide to set the value of the PDU session type selection component.
  • the routing indication information may include priority access type indication information; the target component may include an access type preference component.
  • the generating unit 910 is further configured to: refer to the preferential access type indication information, and decide to set the value of the access type preference component.
  • the second core network element 1000 provided in the embodiment of FIG. 10 may include a receiving unit 1010 and a sending unit 1020 .
  • the receiving unit 1010 is configured to receive a terminal routing policy URSP sent by a network element of the first core network, the URSP includes a URSP rule, the URSP rule includes a routing descriptor RSD, and the RSD includes height information, and the height information is used It indicates that when the altitude of the terminal matches the altitude information, the RSD is selected to transmit the application data.
  • the sending unit 1020 is configured to send the URSP to the terminal.
  • the third network element 1100 provided in the embodiment of FIG. 11 may include a sending unit 1110 .
  • the sending unit 1110 is configured to transmit the height information to a network element of the first core network.
  • the height information may be used to generate a terminal routing policy URSP, and the URSP may include a URSP rule, and the URSP rule may include a routing descriptor RSD, and the RSD may include height information, and the height information may be used to indicate when the terminal When the altitude matches the altitude information, the RSD is selected to transmit application data.
  • the RSD may further include a routing component.
  • the sending unit 1110 is further configured to transmit routing indication information to a network element of the first core network.
  • the network element of the first core network is further configured to refer to the routing indication information, and decide to set the value of the target component in the routing component.
  • the terminal 1200 provided in the embodiment of FIG. 12 may include a receiving unit 1210 and a transmitting unit 1220 .
  • the receiving unit 1210 is configured to receive a terminal routing policy URSP from a network element of the second core network, the URSP includes a URSP rule, the URSP rule includes a routing descriptor RSD, and the RSD includes height information.
  • the transmission unit 1220 is configured to select the RSD to transmit application data when the altitude of the terminal matches the altitude information.
  • each unit shown in FIGS. 9 to 12 can be implemented in software, such as programs and modules; it can also be implemented in hardware, such as one or more Application Specific Integrated Circuits (ASIC, Application Specific). Integrated Circuit), DSP, Programmable Logic Device (PLD, Programmable Logic Device), Complex Programmable Logic Device (CPLD, Complex Programmable Logic Device), Field Programmable Gate Array (FPGA, Field-Programmable Gate Array) or other electronic components accomplish.
  • ASIC Application Specific Integrated Circuit
  • DSP Programmable Logic Device
  • PLD Programmable Logic Device
  • CPLD Complex Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • FPGA Field-Programmable Gate Array
  • first core network element 900 the second core network element 1000, and the third network element 1100 mentioned above may be implemented by using communication devices.
  • An exemplary structure of a communication device is explained below.
  • Fig. 13 schematically shows a schematic structural diagram of a communication device 1300 according to an embodiment of the present disclosure.
  • the communication device may be a terminal, or a core network device, such as a first core network element and/or a second core network element and/or a third network element and/or a fourth core network element, as shown in FIG. 13
  • the communication device 1300 shown includes a processor 1310, and the processor 1310 can invoke and run a computer program from a memory, so as to implement the methods in the embodiments of the present disclosure.
  • the communication device 1300 may further include a memory 1320 .
  • the processor 1310 can invoke and run a computer program from the memory 1320, so as to implement the methods in the embodiments of the present disclosure.
  • the memory 1320 may be an independent device independent of the processor 1310 , or may be integrated in the processor 1310 .
  • the communication device 1300 may further include a transceiver 1330, and the processor 1310 may control the transceiver 1330 to communicate with other devices, specifically, to send information or data to other devices, or Receive information or data from other devices.
  • the transceiver 1330 may include a transmitter and a receiver.
  • the transceiver 1330 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 1300 may specifically be the core network device of the embodiment of the present disclosure, and the communication device 1300 may implement the corresponding process implemented by the core network device in the method of the embodiment of the present disclosure. Let me repeat.
  • the communication device 1300 may specifically be the mobile terminal/terminal of the embodiments of the present disclosure, and the communication device 1300 may implement the corresponding processes implemented by the mobile terminal/terminal in each method of the embodiments of the present disclosure. In order to save space, so I won’t go into details here.
  • processor in the embodiment of the present disclosure may be an integrated circuit chip and has a signal processing capability.
  • each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, an off-the-shelf programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component.
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the steps of the methods disclosed in the embodiments of the present disclosure may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present disclosure may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash.
  • the volatile memory can be Random Access Memory (RAM), which acts as external cache memory.
  • RAM Static Random Access Memory
  • SRAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM, DDR SDRAM enhanced synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM synchronous connection dynamic random access memory
  • Synchrobus RAM Direct Rambus RAM, DR RAM
  • An embodiment of the present disclosure also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the core network device in the embodiments of the present disclosure, and the computer program enables the computer to execute the corresponding processes implemented by the core network device in the methods of the embodiments of the present disclosure, for It is concise and will not be repeated here.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal in the embodiments of the present disclosure, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal in the various methods of the embodiments of the present disclosure , which will not be repeated here.
  • An embodiment of the present disclosure also provides a computer program product, including computer program instructions.
  • the computer program product can be applied to the core network device in the embodiments of the present disclosure, and the computer program instructions cause the computer to execute the corresponding processes implemented by the core network device in the various methods of the embodiments of the present disclosure, for the sake of brevity , which will not be repeated here.
  • the computer program product can be applied to the mobile terminal/terminal in the embodiments of the present disclosure, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal in the various methods of the embodiments of the present disclosure, For the sake of brevity, details are not repeated here.
  • the embodiment of the present disclosure also provides a computer program.
  • the computer program can be applied to the core network device in the embodiments of the present disclosure.
  • the computer program executes the corresponding functions implemented by the core network device in the various methods of the embodiments of the present disclosure. For the sake of brevity, the process will not be repeated here.
  • the computer program can be applied to the mobile terminal/terminal in the embodiments of the present disclosure.
  • the computer program executes the various methods of the embodiments of the present disclosure to be implemented by the mobile terminal/terminal For the sake of brevity, the corresponding process will not be repeated here.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present disclosure is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in various embodiments of the present disclosure.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例提供了一种数据传输方法及相关设备、计算机可读存储介质、计算机程序产品，属于通信技术领域。所述方法由第一核心网网元执行，所述方法包括：生成终端路由选择策略URSP，URSP包括URSP规则，URSP规则包括路由选择描述符RSD，RSD包括高度信息，高度信息用于指示当终端的高度匹配高度信息时，选择RSD传输应用数据；将URSP通过第二核心网网元下发至终端。

Description

数据传输方法及相关设备、计算机可读存储介质、计算机程序产品
相关申请的交叉引用
本申请基于申请号为202210028773.5、申请日为2022年1月11日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及通信技术领域，具体而言，涉及一种数据传输方法、第一核心网网元、第二核心网网元、第三网元、终端、通信设备、计算机可读存储介质及计算机程序产品。
背景技术
终端/用户设备(User Equipment，UE)策略包括终端路由选择策略(UE Route Selection Policy，URSP)，但对于相关技术中URSP规则的内容，需要根据具体的业务需求进行进一步的扩展，以支持特定的业务诉求。
发明内容
本公开实施例提供一种数据传输方法、第一核心网网元、第二核心网网元、第三网元、终端、通信设备、计算机可读存储介质及计算机程序产品，能够在生成URSP规则时考虑终端的高度，生成符合终端应用需求的URSP规则。
本公开实施例提供一种数据传输方法，所述方法由第一核心网网元执行，所述方法包括：生成终端路由选择策略URSP，URSP包括URSP规则，URSP规则包括路由选择描述符RSD，RSD包括高度信息，所述高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据；将URSP通过第二核心网网元下发至所述终端。
本公开实施例提供一种数据传输方法，所述方法由第二核心网网元执行，所述方法包括：接收第一核心网网元发送的终端路由选择策略URSP，URSP包括URSP规则，URSP规则包括路由选择描述符RSD，RSD包括高度信息，所述高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据；将URSP下发至所述终端。
本公开实施例提供一种数据传输方法，所述方法由第三网元执行，所述方法包括：向第一核心网网元传输高度信息；高度信息用于生成终端路 由选择策略URSP，URSP包括URSP规则，URSP规则包括路由选择描述符RSD，RSD包括高度信息，高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
本公开实施例提供一种数据传输方法，所述方法由终端执行，所述方法包括：从第二核心网网元接收终端路由选择策略URSP，URSP包括URSP规则，URSP规则包括路由选择描述符RSD，RSD包括高度信息；当所述终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
本公开实施例提供一种第一核心网网元，包括：生成单元，用于生成终端路由选择策略URSP，URSP包括URSP规则，URSP规则包括路由选择描述符RSD，RSD包括高度信息，高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据；发送单元，用于将URSP通过第二核心网网元下发至所述终端。
本公开实施例提供一种第二核心网网元，包括：接收单元，用于接收第一核心网网元发送的终端路由选择策略URSP，URSP包括URSP规则，URSP规则包括路由选择描述符RSD，RSD包括高度信息，高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据；发送单元，用于将URSP下发至终端。
本公开实施例提供一种第三网元，包括：发送单元，用于向第一核心网网元传输高度信息；所述高度信息用于生成终端路由选择策略URSP，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息，所述高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
本公开实施例提供一种终端，包括：接收单元，用于从第二核心网网元接收终端路由选择策略URSP，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息；传输单元，用于当所述终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
本公开实施例提供了一种计算机可读存储介质，其上存储有计算机程序，所述程序被处理器执行时实现本公开实施例中所述的数据传输方法。
本公开实施例提供了一种通信设备，包括：一个或多个处理器；存储器，配置为存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述通信设备实现本公开实施例中所述的数据传输方法。
本公开实施例提供了一种计算机程序产品，包括计算机程序，所述计算机程序被处理器执行时实现本公开实施例中所述的数据传输方法。
本公开实施例通过根据具体的业务需求对URSP规则进行扩展，相较于相关技术，扩展了与高度信息相关的特定的业务诉求的支持，能够支持具有特定的高度的UE进行灵活的路由选择，以及通过应用与网络交互来支持对特定高度的UE的路由选择。
附图说明
图1是本公开实施例提供的一种通信系统架构的示意图。
图2是本公开实施例提供的5G网络的系统架构图。
图3示意性示出了根据本公开的一实施例的数据传输方法的流程图。
图4示意性示出了根据本公开的一实施例的数据传输方法的交互示意图。
图5示意性示出了根据本公开的另一实施例的数据传输方法的交互示意图。
图6示意性示出了根据本公开的另一实施例的数据传输方法的流程图。
图7示意性示出了根据本公开的又一实施例的数据传输方法的流程图。
图8示意性示出了根据本公开的再一实施例的数据传输方法的流程图。
图9示意性示出了根据本公开的一实施例的第一核心网网元的框图。
图10示意性示出了根据本公开的一实施例的第二核心网网元的框图。
图11示意性示出了根据本公开的一实施例的第三网元的框图。
图12示意性示出了根据本公开的一实施例的终端的框图。
图13示意性示出了根据本公开的一实施例的通信设备的示意性结构图。
具体实施方式
现在将参考附图更全面地描述示例实施方式。然而，示例实施方式能够以多种形式实施，且不应被理解为限于在此阐述的范例；相反，提供这些实施方式使得本公开将更加全面和完整，并将示例实施方式的构思全面地传达给本领域的技术人员。
本公开实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(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)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统或5G系统等。
示例性的，本公开实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端进行通信。在一些实施例中，该网络设备110可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)， 还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，还可以是5G通信系统中的基站，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
该通信系统100还可以包括位于网络设备110覆盖范围内的至少一个终端120。作为在此使用的“终端”包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端可以指接入终端、UE、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端或者未来演进的PLMN中的终端等。
在一些实施例中，终端120之间可以进行终端直连(Device to Device，D2D)通信。
在一些实施例中，5G系统或5G网络还可以称为新无线(New Radio，NR)系统或NR网络。
图1示例性地示出了一个网络设备和两个终端，在一些实施例中，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端，本公开实施例对此不做限定。
在一些实施例中，该通信系统100还可以包括网络策略控制实体、移动管理实体等其他网络实体，本公开实施例对此不作限定。
应理解，本公开实施例中网络/系统中具有通信功能的设备可称为通信 设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端120，网络设备110和终端120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络策略控制实体、移动管理实体等其他网络实体，本公开实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
图2为本公开实施例的5G网络的系统架构图，如图2所示，5G网络系统中涉及到的设备包括：终端(UE)>无线接入网(Radio Access Network，RAN)、用户平面功能(User Plane Function，UPF)>数据网络(Data Network，DN)、接入和移动性管理(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、策略控制功能(Policy Control Function，PCF)>应用功能(Application Function，AF)>鉴权服务器功能(Authentication Server Function，AUSF)、统一数据管理(Unified Data Management，UDM)、网络切片选择功能(Network Slice Selection Function，NSSF)。
如图2所示，与策略相关的网元主要是PCF、AMF、SMF、RAN、UE。其中，SMF主要是负责与会话相关的策略的执行，AMF主要负责与接入和UE策略相关的策略执行，两个网元(AMF和SMF)上的策略下发、更新全都由PCF来管控。
具体到UE策略，PCF与UE之间可以通过容器(Container)来监护UE策略相关的信息，包括UE策略的内容、UE策略标识等。在上行方向上，由UE通过非接入层(Non Access Stratum，NAS)消息将容器发送给AMF，并由AMF以不感知容器或不修改容器的方式继续透传给PCF，下行方向与之相反，由PCF将容器发给AMF，AMF进而通过NAS消息将容器透传给UE。
UE策略包括URSP。URSP包含多个策略规则(称为URSP Rule)，每一个URSP Rule由流量描述符(Traffic Descriptor)和一组路由选择描述符(Route Selection Descriptor，RSD)组成。URSP中的流量描述符用于描述一种具体的业务。一个流量描述符可以对应一个或多个RSD，每一个RSD对应一个PDU会话的属性，也就是说流量描述符对应的业务数据可以传输在RSD对应的PDU会话中。
相关技术中的URSP的相关的内容如下表1和表2所示：
表1：URSP规则
Figure PCTCN2022132318-appb-000001
Figure PCTCN2022132318-appb-000002
Figure PCTCN2022132318-appb-000003
上述表1中，Rule Precedence表示规则优先级，规则优先级决定了UE使用URSP规则的顺序。Traffic descriptor是一个用于说明匹配标准的流量描述符，由一个或多个组件组成，可以包括：应用描述符(Application descriptors)、IP描述符(IP descriptors，目的IP)、域描述符(Domain descriptors，目的全限定域名(Fully Qualified Domain Name，FQDN))、非IP描述符(Non-IP descriptors)、数据网络名称(Data Network Name，DNN)描述符和连接能力(Connection Capabilities)，流量描述符供UE使用进行应用匹配。当流量描述符中的每个组件都与来自应用的相应信息匹配时，该URSP规则适用。当流量描述符中的任一组件有如下情况时，该URSP规则不适用于以下情况：没有来自应用的相应信息可用；来自应用的相应信息与流量描述符组件中的任何值都不匹配。
表2:RSD
Figure PCTCN2022132318-appb-000004
Figure PCTCN2022132318-appb-000005
上述表2中，Route Selection Descriptor Precedence表示RSD优先级，决定了使用RSD的顺序，当优先级高的RSD无法使用时，才使用其它RSD。Route selection components表示路由选择组件，描述了应用可以使用的各种 网络资源，它由一个或多个组件组成，可以包括业务会话连续性(Service and Session Continuity，SSC)模式选择(SSC Mode Selection，UE用来将匹配的应用与SSC模式相关联)、网络切片选择(Network Slice Selection，UE用来将匹配的应用于与S-NSSAI相关联)、DNN选择(DNN Selection，UE用来将匹配的应用于与DNN相关联)、协议数据单元(Protocol Data Unit，PDU)会话类型选择(PDU Session Type Selection，UE用来将匹配的应用与PDU会话类型相匹配)、有缝卸载指示(Non-Seamless Offload indication)和接入类型优先级(Access Type preference，也可称之为接入类型偏好，如果UE需要为匹配的应用建立一个PDU会话，它将表明优先的接入类型(3GPP或非3GPP(non-3GPP)或多接入(Multi-Access)))。
路径选择有效条件(Route Selection Validation Criteria)，也称为路由选择校验标准，描述了对应的生效条件，它包括时间窗口(Time Window，也可称之为有效时间窗口)和位置标准(Location Criteria，也可称之为位置条件)，如果当前时间不在时间窗口内或UE位置不匹配位置标准，则认为对应的RSD无效。
其中，SSC模式、单网络切片选择辅助信息(Single Network Slice Selection Assistance Information，S-NSSAI)、PDU会话类型和DNN都是与PDU会话属性相关的参数。
相关技术中的URSP规则不能解决特定高度的UE路由选择问题，以及通过应用与网络交互来指示特定的优选选择问题。
图3实施例提供的数据传输方法可以由第一核心网网元执行，在示例性实施例中，第一核心网网元可以是PCF，但本公开实施例并不限定于此。
如图3所示，本公开实施例提供的方法可以包括S310和S320，下面具体说明。
在S310中，生成终端路由选择策略URSP。
其中，URSP可以包括一个或多个(两个或者两个以上)URSP规则，每个URSP规则可以包括路由选择描述符RSD，其中一个RSD或者每个RSD中可以包括高度信息，高度信息是指用于指示当终端的高度匹配RSD中的高度信息时，选择对应的RSD来传输该终端的应用数据。
URSP配置为实现UE将特定的业务流映射到对应的数据传输会话上。例如，PCF可以在核心网中生成多个URSP规则，每个URSP规则均可以包括流量描述符(Traffic Descriptor)和路由选择描述符(RSD)。当UE上的某个应用程序启动时，可以根据UE启动的应用程序的流量特性，匹配核心网生成的URSP规则中的Traffic Descriptor，确定对应的URSP。每个URSP规则可以包括一个或者多个RSD，且可以根据业务需求和业务类型为每个URSP规则中的不同RSD配置对应的RSD优先级。在匹配到对应的URSP后，UE可以根据已生成的各RSD的RSD优先级，选择相应的RSD，并在与该RSD对应的数据传输会话上传输该应用程序的数据(称之为业务数据 或者应用数据)。
本公开实施例中，以UE为无人机进行举例说明，但并不限定于此，本公开提供的方法可以适用于任意需要在特定高度进行路由选择的UE。将该特定高度设置在URSP规则中的RSD中，作为RSD中的高度信息，高度信息可以是一个取值范围，也可以是某个特定的值，高度信息的取值可以根据实际需求设置，本公开实施例对此不做限定。
本公开实施例中，当支持无人机场景时，应用可以定义针对无人机的飞行高度接入特定的路由路径，例如，假设设置RSD中的高度信息为高度范围，以10m-30m为例，则当无人机的飞行高度在10米-30米时，可以使得无人机正式进入工作模式发起视频传输，通过设置该RSD中的其它参数，例如此时无人机可以接入到网络切片S-NSSAI-1，业务连续性模式选用SSC mode 3。这样可以控制无人机在刚起飞时不工作，等到了某个特定高度才开始进入工作模式，发起视频传输，并且在该特定的高度下，可以规定RSD中任意一个参数，例如S-NSSAI，DNN，SSC mode，可以根据需要设置为任意一个取值。
需要指出，上文是以高度信息为高度范围为例说明，作为替代方案，高度信息可以包括一个或多个设定的高度值，例如，10米，20米，30米。
在示例性实施例中，RSD可以包括路径选择有效条件，路径选择有效条件可以包括位置条件；位置条件包括高度信息。
在示例性实施例中，RSD可以包括路径选择有效条件，路径选择有效条件可以包括所述高度信息。
本公开实施例中，为了支持上述场景，首先在URSP规则中新增高度相关的参数(高度信息)，还可以在AF和网络交互的AF影响URSP规则的流程中，补充相应的参数，例如AF直接或间接地向PCF发送高度信息和/或路由选择指示信息。
在相关的URSP规则中，定义了路径选择有效条件Route Selection Validation Criteria，Route Selection Validation Criteria包括时间窗口(Time Window)和位置条件(Location Criteria)。
时间窗口：当时间窗口的条件满足(即当前时间位于时间窗口内)时，UE才会执行URSP规则中定义的RSD。如果当前时间不在该时间窗口内，则UE认为RSD是无效的。
位置条件：定义匹配该业务流路由的UE位置信息。当UE位置不满足位置条件(即UE位置与位置信息中的位置不同)时，则UE认为RSD是无效的。
相关技术中，Location Criteria的具体内容如下：
Length of Location Criteria(octect d)//标准的位置长度，指示Location Criteria的长度
Location Criteria中的区域的编码规则如下：
Figure PCTCN2022132318-appb-000006
其中，E-UTRA是Evolved-UMTS Terrestrial Radio Access的简写，即进化的UMTS(Universal Mobile Telecommunications System，通用移动通信系统)陆地无线接入。TAI是Tracking Area Identity的简写，即位置区标识或者跟踪区标识。
本公开实施例提出在URSP规则的Route Selection Validation Criteria中补充高度信息作为一个评估RSD是否有效的条件。
其中一种实现方式是：该高度信息可以作为Location Criteria的一个具体的参数，即在Location Criteria中新增一个高度信息作为location area type，即位置条件包括高度信息。
另一种实现方式是：在Route Selection Validation Criteria中新增一个和Time Window以及Location Criteria并列的参数：高度信息，即路径有效条件包括高度信息。
上述不同的实现方式实现高度信息与相关技术的灵活融合。
本公开实施例中，高度信息是指匹配该业务流路由的UE的高度信息，即当UE位于当前高度时，才会执行该RSD；当UE不位于当前高度时，则不执行该RSD。
在示例性实施例中，RSD中设置的高度信息配置为指示以下的至少一项：
若所述路径选择有效条件中包括时间窗口和所述高度信息，则所述高度信息指示当所述终端的高度匹配所述高度信息，且当前时间处于所述时间窗口内时，选择所述RSD传输应用数据；
若所述路径选择有效条件中包括位置信息和所述高度信息时，则所述高度信息指示当所述终端的高度匹配所述高度信息，且当前位置匹配所述位置信息时，选择所述RSD传输应用数据。
作为示例，若高度信息为高度范围，则终端的高度匹配所述高度信息可以是终端的高度处于高度范围内；若高度信息为一个或多个高度值，则终端的高度匹配高度信息可以是，终端的高度与一个高度值相同或二者的高度差值小于高度差值阈值。
作为示例，当前位置匹配所述位置信息可以是，当前位置与位置信息中的一个位置相同或二者的距离小于距离阈值。
本公开实施例中，高度信息可以单独作为评估该RSD是否有效的条件， 但高度信息也可以与时间窗口信息和位置信息中的至少一个来共同构成评估该RSD是否有效的条件，示例如下：
-当路由选择验证标准(Route Selection Validation Criteria)既包含有时间窗口信息也有高度信息时，若UE的当前高度位于该高度信息内且时间处于该时间窗口内，则执行该RSD。当UE的当前高度不位于该高度信息内，或者当前时间不位于该时间窗口内，即两个条件有一个不满足，则不执行该RSD。
-当Route Selection Validation Criteria既包含有位置条件，也包含该高度信息时，若UE的当前高度位于该高度信息内且UE的当前位置满足位置条件(即，当前位置是位置条件中定义的匹配业务流路由的UE位置信息)内时，则执行该RSD；若UE的当前高度不匹配高度信息，或者UE的当前位置不匹配位置信息，即两个条件有一个不满足，则不执行该RSD。
-当Route Selection Validation Criteria既包含有时间窗口信息，也包含有位置信息，还包含该高度信息时，若UE的当前高度匹配该高度信息，UE的当前时间处于该时间窗口内，且UE的当前位置匹配该位置信息，则执行该RSD；当UE的当前时间不位于该时间窗口内，或者UE的当前高度不匹配该高度信息，或者UE的当前位置不匹配位置信息，即三个条件有一个不满足，则不执行该RSD。
在示例性实施例中，生成终端路由选择策略URSP，可以包括：接收第三网元发送的高度信息；参考接收到的所述高度信息，决定在所述路径选择有效条件中设置所述高度信息。本公开实施例中，第三网元可以是AF，但本公开实施例并不限定于此。PCF从AF接收到高度信息之后，可以根据自身的决策决定是否要接受所接收到的高度信息，若接受该高度信息，则在URSP规则中设置该高度信息，若不接受该高度信息，则在URSP规则中不设置该高度信息。
在示例性实施例中，接收第三网元发送的高度信息，可以包括：接收所述第三网元发送的服务参数(Service Parameters)，所述服务参数可以包括所述高度信息。
在示例性实施例中，接收第三网元发送的高度信息，可以包括：从第四核心网网元接收所述高度信息。其中，所述第四核心网网元配置为从所述第三网元接收所述高度信息。
相关技术中定义了AF影响URSP规则的流程，UE可以向网络中的网元如NEF(第四核心网网元)提供的参数信息包括：
1)服务描述指示AF标识符
(Service Description indicates an AF Identifier).
2)Service Parameters.
3)一个特定的UE，或一组UE，或与AF请求相关联的任何UE(a specific UE,or a group of UE(s)or any UE that the AF request may  be associated with).
4)订阅活动(Subscription to events).
本公开实施例中，AF可以在Service Parameters中新增高度信息，即AF向网络请求为特定高度的UE选择特定的路由时，即指示PCF在生成URSP规则时考虑AF的请求，将Service Parameters中携带的高度信息设置在特定的Route Selection Validation Criteria中。AF可以通过NEF将Service Parameters中携带的高度信息发送给PCF，也可以直接发送给PCF，PCF接收到AF发送的信息后，可以根据自己的策略，决定是否接受AF的请求来设置URSP规则。
需要说明的是，AF可以将高度信息携带在已有的消息和已有的参数中发送给PCF，也可以新增消息和/或新增参数，将高度信息携带在已有的消息中的新增参数中发送给PCF，或者，将高度信息携带在新增消息中的新增参数中发送给PCF，本公开对此不做限定。
在示例性实施例中，RSD可以包括路由选择组件(Route selection components)。其中，生成终端路由选择策略URSP，可以包括：接收第三网元发送的路由选择指示信息；参考所述路由选择指示信息，决定设置所述路由选择组件中的目标组件的值。
本公开实施例中，目标组件可以是RSD的Route selection components中的任意一个或者多个组件，例如业务会话连续性模式选择(SSC Mode Selection)和/或网络切片选择(Network Slice Selection)和/或DNN Selection和/或PDU Session Type Selection和/或非无缝卸载指示(Non-Seamless Offload indication)和/或ProSe第3层UE到网络中继卸载指示(
ProSe Layer-3UE-to-Network Relay Offload indication)和/或访问类型首选项(Access Type preference)和/或PDU会话对ID
(PDU Session Pair ID)和/或RSN。路由选择指示信息配置为设置目标组件中的值，例如某个特定的SSC mode、某个特定的S-NSSAI或者S-NSSAI(s)的列表、某个特定的DNN或者DNN(s)的列表、某个特定的PDU Session Type、某个特定的接入类型偏好，包括第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)/non-3GPP/多路访问(Multi-Access)等中的一个或多个，下面以SSC Mode、PDU Session Type、Access Type preference这三个进行举例说明，但本公开实施例并不限定于此。
在示例性实施例中，接收第三网元发送的路由选择指示信息，可以包括：接收所述第三网元发送的服务参数，所述服务参数可以包括所述路由选择指示信息。
本公开实施例中，PCF可以直接从AF接收携带了路由选择指示信息的服务参数，也可以通过NEF间接地从AF接收携带了路由选择指示信息的服务参数。
本公开实施例中，可以在服务参数中新增路由选择指示信息，也可以新增参数，在该新增参数中包含路由选择指示信息，本公开对此不做限定。
在示例性实施例中，所述路由选择指示信息可以包括业务连续性指示信息；所述目标组件可以包括业务会话连续性模式选择组件SSC Mode Selection。其中，参考所述路由选择指示信息，决定设置所述路由选择组件中的目标组件的值，可以包括：参考所述业务连续性指示信息，决定设置所述业务会话连续性模式选择组件的值。
在示例性实施例中，所述业务连续性指示信息可以包括业务会话连续性模式的值。
在示例性实施例中，所述业务连续性指示信息可以用于指示是否支持终端网络地址变化以及在终端网络地址变化时是否需要保持业务连续性。其中，参考所述业务连续性指示信息，决定设置所述业务会话连续性模式选择组件的值，可以包括：当所述业务连续性指示信息指示不支持终端网络地址变化时，设置所述业务会话连续性模式选择组件的值为第一业务会话连续性模式；当所述业务连续性指示信息指示支持终端网络地址变化，且不需要保持业务连续性时，设置所述业务会话连续性模式选择组件的值为第二业务会话连续性模式；当所述业务连续性指示信息指示支持终端网络地址变化，且需要保持业务连续性时，设置所述业务会话连续性模式选择组件的值为第三业务会话连续性模式。
本公开实施例中，可以在Service Parameters中新增业务连续性指示信息，即AF向网络请求为特定的业务流选择特定的路由时，即指示PCF在生成PCF规则时考虑AF的请求，将业务连续性指示信息用于设置URSP中的Route selection components中的SSC Mode。
本公开实施例中，在Service Parameters中新增业务连续性指示信息可以有两种方式：一种是可以直接指示具体的SSC Mode的值，第二种是指示是否支持UE IP(Internet Protocol，网际互联协议)地址(终端网络地址)变化以及在IP地址变化时是否需要保持业务连续性。
其中，“不支持UE IP地址变化”对应SSC mode 1(第一业务会话连续性模式)；“支持UE IP地址变化，但是不需要保持业务连续性”对应SSC mode 2(第二业务会话连续性模式)；“支持UE IP地址变化，但是需要保持业务连续性”对应SSC mode 3(第三业务会话连续性模式)。
在示例性实施例中，所述路由选择指示信息可以包括协议数据单元会话类型指示信息；所述目标组件可以包括协议数据单元会话类型选择组件PDU Session Type Selection。其中，参考所述路由选择指示信息，决定设置所述路由选择组件中的目标组件的值，可以包括：参考所述协议数据单元会话类型指示信息，决定设置所述协议数据单元会话类型选择组件的值。
本公开实施例中，可以在Service Parameters中新增PDU会话类型指示信息(具体的值可以是IPv4，或者IPv6，或者IPv4v6；或者Enternet；或 者Unstructured非结构化)，即AF向网络请求为特定的业务流选择特定的路由时，即指示PCF在生成URSP规则时考虑AF的请求，将Service Parameters携带的PDU会话类型指示信息用于设置URSP中的Route selection components中的PDU Session Type Selection。
在示例性实施例中，所述路由选择指示信息可以包括优先接入类型指示信息；所述目标组件包括接入类型偏好组件Access Type preference。其中，参考所述路由选择指示信息，决定设置所述路由选择组件中的目标组件的值，可以包括：参考所述优先接入类型指示信息，决定设置所述接入类型偏好组件的值。
本公开实施例中，可以在Service Parameters中新增优先接入类型指示信息(具体的值可以是3GPP接入或non-3GPP接入或Multi-Access多接入)，即AF向网络请求为特定的业务流选择特定的路由时，即指示PCF在生成URSP规则时考虑AF的请求，将Service Parameters中携带的优先接入类型指示信息用于设置URSP中的Route selection components中的PDU的Access Type preference。
本公开实施例通过上述不同的指示信息的设置方式，使得AF向网络请求为特定的业务流选择特定的路由时，指示PCF在生成URSP规则中的考虑AF的请求提供了灵活和多样化的实现方式。
在S320中，将所述URSP通过第二核心网网元下发至所述终端。本公开实施例中，第二核心网网元可以是AMF，但本公开实施例并不限定于此。
例如，图1实施例中的网络设备110可以是该通信系统的核心网设备，可以生成有多个URSP规则，每个URSP规则均可以包括Traffic Descriptor和RSD。终端120上可以安装有一个或多个应用程序，当终端120上的某个应用程序启动时，终端120可以根据所启动应用程序的流量特性，匹配URSP规则中的Traffic Descriptor，并根据对应Traffic Descriptor的RSD，对所启动应用程序的数据进行路由。
URSP规则可以包含一个或多个RSD，每个RSD可以用于指示对应PDU会话。例如，RSD中可以包含有PDU会话建立的参数，如：DNN、Network Slice Selection Policy、S-NSSAI、PDU会话类型等参数。不同RSD对应的PDU会话，提供的上网体验可能不同。
本公开实施例对于URSP规则的内容，根据具体的业务需求进行进一步的扩展，能够支持特定的业务诉求。例如，针对无人机这类具有特定的高度的UE，如何进行特定的路由选择，以及通过应用与网络交互来支持对特定高度的UE的路由选择；还可以通过应用与网络交互来进行特定的业务连续性的指示；还可以通过应用与网络交互来进行特定的PDU会话类型的选择等。
参考图4，以第一核心网网元为PCF、第二核心网网元为AMF、第三网元为AF，且AF和PCF直接交互进行举例说明。
图4示意性示出了根据本公开的一实施例的数据传输方法的交互示意图。如图4所示，本公开实施例提供的方法可以包括S41至S44，下面具体说明。
在S41中，AF将高度信息和路由选择指示信息发送至PCF。
在S42中，PCF配置URSP。
PCF从AF接收高度信息和路由选择指示信息之后，参考高度信息和路由选择指示信息，决定是否接受该高度信息和/或路由选择指示信息，若决定接受该高度信息，则在生成的URSP规则的RSD中包含该高度信息，若不接受该高度信息，则在生成的URSP规则的RSD中不包含该高度信息；若决定接受该路由选择指示信息，则参考路由选择指示信息，决定设置路由选择组件中的目标组件的值，若决定不接受该路由选择指示信息，则不参考路由选择指示信息，决定设置路由选择组件中的目标组件的值。
可以理解的是，高度信息和路由选择指示信息可以包含在已有的消息中的已有参数中，也可以包含在已有消息的新增参数中，或者可以通过新增消息传输，本公开实施例对此不做限定。
需要说明的是，上述S41是在一些实施例中，即PCF也可以直接生成URSP。
在S43中，PCF发送URSP。
例如，PCF可以将生成的URSP放在一个容器(Container)里，发送给AMF，但本公开实施例并不限定于此。
在S44中，AMF发送URSP。
AMF接收到URSP之后，将URSP通过RAN发送至UE。
本公开实施例中，AMF可以使用NAS消息将容器直接转发给UE，但本公开实施例并不限定于此。
UE基于接收到的URSP将应用数据关联到相应的PDU会话上进行传输，机制如下：当应用层发送数据时，UE使用URSP中的URSP规则来查看该应用数据的特征是否匹配到了URSP规则中的某一个规则的Traffic Descriptor上，查看的顺序按照URSP规则中的优先级(Precedence)来决定，即UE基于优先级的顺序依次查看匹配情况，当匹配到一个URSP规则的Traffic Descriptor时，用该URSP规则下的RSD列表进行PDU会话的绑定。当有URSP规则匹配上时，UE按照RSD中的Precedence顺序来查找合适的PDU会话，这里优先使用优先级高的RSD，如果该RSD中的某个参数为一个或多个取值，则UE选用参数的组合查找PDU会话是否存在：
1)若存在，则将该应用数据绑定到该会话进行传输；
2)若不存在，则UE触发该PDU会话的建立，建立请求消息中UE上报PDU会话的属性参数；进一步，
2.1)若该会话建立成功，则UE将该应用数据绑定到该会话进行传输；
2.2)若该会话建立不成功，则UE基于该RSD中的其他参数组合或者使用次优先级的RSD中的参数组合再次查找PDU会话是否存在(循环步骤1))；
若根据该匹配的URSP规则中都不能找到一个合适的PDU会话进行绑定，则UE根据Precedence顺序查找次优先的URSP规则中的Traffic Descriptor是否能够匹配该应用数据流特征，当匹配成功时，重复之前描述的过程。
本公开实施例通过上述的应用和网络的交互方式，使能网络在生成URSP规则时考虑应用的输入信息(包括高度信息和/或路由选择指示信息)，从而能够生成符合应用需求的URSP规则。
图4实施例的其它内容可以参照上述其它实施例。
图5实施例以第一核心网网元为PCF、第二核心网网元为AMF、第三网元为AF、第四核心网网元为NEF，且AF和PCF通过NEF交互进行举例说明。
图5示意性示出了根据本公开的另一实施例的数据传输方法的交互示意图。如图5所示，本公开实施例提供的方法可以包括S51至S55，下面具体说明。
在S51中，AF向NEF发送高度信息和路由选择指示信息。
在S52中，NEF从AF接收到高度信息和路由选择指示信息之后，向PCF转发高度信息和路由选择指示信息。
在S53中，PCF配置URSP。
PCF从NEF接收高度信息和路由选择指示信息之后，决定是否接受所接收到的高度信息和路由选择指示信息，以此来生成URSP。
需要说明的是，上述S51和S52是可以缺省执行的，即PCF可以直接生成URSP。
在S54中，PCF向AMF发送URSP。
在S55中，AMF向RAN发送URSP。
在S56中，RAN接收到URSP之后，向UE转发URSP。
图5实施例的其它内容可以参照上述其它实施例。
图6实施例提供的数据传输方法可以由第二核心网网元执行，在示例性实施例中，第二核心网网元可以是AMF。
如图6所示，本公开实施例提供的方法可以包括S610和S620。
在S610中，接收第一核心网网元发送的终端路由选择策略URSP。
所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息，高度信息用于指示当终端的高度匹配高度信息时，选择RSD传输应用数据。
在S620中，将所述URSP下发至所述终端。
图6实施例的其它内容可以参照上述其它实施例。
图7实施例提供的数据传输方法可以由第三网元执行，在示例性实施例中，第三网元可以是AF。
如图7所示，本公开实施例提供的方法可以包括：
在S710中，向第一核心网网元传输高度信息。
所述高度信息可以用于生成URSP。例如，所述第一核心网网元配置为根据所述高度信息为所述终端生成终端路由选择策略URSP，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括所述高度信息，所述高度信息可以用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
在示例性实施例中，所述RSD还可以包括路由选择组件。其中，所述方法还可以包括：向第一核心网网元传输路由选择指示信息；所述第一核心网网元还配置为参考所述路由选择指示信息，决定设置所述路由选择组件中的目标组件的值。
图7实施例的其它内容可以参照上述其它实施例。
图8实施例提供的数据传输方法可以由终端执行，但本公开实施例并不限定于此。
如图8所示，本公开实施例提供的方法可以包括S810和S820：
在S810中，从第二核心网网元接收终端路由选择策略URSP。
所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息。
在S820中，当所述终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
图8实施例的其它内容可以参照上述其它实施例。
如图9所示，图9实施例提供的第一核心网网元900可以包括生成单元910以及发送单元920。
生成单元910配置为生成终端路由选择策略URSP，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息，所述高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
发送单元920配置为将所述URSP通过第二核心网网元下发至所述终端。
在示例性实施例中，所述RSD可以包括路径选择有效条件，所述路径选择有效条件包括位置条件；所述位置条件可以包括所述高度信息。
在示例性实施例中，所述RSD包括路径选择有效条件，所述路径选择有效条件包括所述高度信息。
在示例性实施例中，所述高度信息可以用于指示以下中的至少一项：
若所述路径选择有效条件中包括时间窗口和所述高度信息，则所述高度信息可以指示当所述终端的高度匹配所述高度信息，且当前时间处于所 述时间窗口内时，选择所述RSD传输应用数据；
若所述路径选择有效条件中包括位置条件和所述高度信息时，则所述高度信息可以指示当所述终端的高度匹配所述高度信息，且当前位置匹配所述位置信息时，选择所述RSD传输应用数据。
在示例性实施例中，第一核心网网元900还可以包括接收单元，配置为接收第三网元发送的高度信息。生成单元910还配置为参考接收到的所述高度信息，决定在所述路径选择有效条件中设置所述高度信息。
在示例性实施例中，接收单元还配置为：接收所述第三网元发送的服务参数，所述服务参数包括所述高度信息。
在示例性实施例中，接收单元还配置为：从第四核心网网元接收所述高度信息。其中，所述第四核心网网元配置为从所述第三网元接收所述高度信息。
在示例性实施例中，所述RSD可以包括路由选择组件。第一核心网网元900还可以包括接收单元，配置为接收第三网元发送的路由选择指示信息。生成单元910还配置为参考所述路由选择指示信息，决定设置所述路由选择组件中的目标组件的值。
在示例性实施例中，接收单元还配置为：接收所述第三网元发送的服务参数，所述服务参数可以包括所述路由选择指示信息。
在示例性实施例中，所述路由选择指示信息可以包括业务连续性指示信息；所述目标组件可以包括业务会话连续性模式选择组件。其中，生成单元910还配置为：参考所述业务连续性指示信息，决定设置所述业务会话连续性模式选择组件的值。
在示例性实施例中，所述业务连续性指示信息可以包括业务会话连续性模式的值。
在示例性实施例中，所述业务连续性指示信息可以用于指示是否支持终端网络地址变化以及在终端网络地址变化时是否需要保持业务连续性。其中，生成单元910还配置为：当所述业务连续性指示信息指示不支持终端网络地址变化时，设置所述业务会话连续性模式选择组件的值为第一业务会话连续性模式；当所述业务连续性指示信息指示支持终端网络地址变化，且不需要保持业务连续性时，设置所述业务会话连续性模式选择组件的值为第二业务会话连续性模式；当所述业务连续性指示信息指示支持终端网络地址变化，且需要保持业务连续性时，设置所述业务会话连续性模式选择组件的值为第三业务会话连续性模式。
在示例性实施例中，所述路由选择指示信息可以包括协议数据单元会话类型指示信息；所述目标组件可以包括协议数据单元会话类型选择组件。其中，生成单元910还配置为：参考所述协议数据单元会话类型指示信息，决定设置所述协议数据单元会话类型选择组件的值。
在示例性实施例中，所述路由选择指示信息可以包括优先接入类型指 示信息；所述目标组件可以包括接入类型偏好组件。其中，生成单元910还配置为：参考所述优先接入类型指示信息，决定设置所述接入类型偏好组件的值。
图9实施例的其它内容可以参照上述其它实施例。
如图10所示，图10实施例提供的第二核心网网元1000可以包括接收单元1010以及发送单元1020。
接收单元1010配置为接收第一核心网网元发送的终端路由选择策略URSP，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息，所述高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
发送单元1020配置为将所述URSP下发至所述终端。
图10实施例的其它内容可以参照上述其它实施例。
如图11所示，图11实施例提供的第三网元1100可以包括发送单元1110。
发送单元1110配置为向第一核心网网元传输所述高度信息。
高度信息可以用于生成终端路由选择策略URSP，URSP可以包括URSP规则，所述URSP规则可以包括路由选择描述符RSD，所述RSD可以包括高度信息，所述高度信息可以用于为指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
在示例性实施例中，所述RSD还可以包括路由选择组件。
其中，发送单元1110还配置为向第一核心网网元传输路由选择指示信息。所述第一核心网网元还配置为参考所述路由选择指示信息，决定设置所述路由选择组件中的目标组件的值。
图11实施例的其它内容可以参照上述其它实施例。
如图12所述，图12实施例提供的终端1200可以包括接收单元1210以及传输单元1220。
接收单元1210配置为从第二核心网网元接收终端路由选择策略URSP，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息。
传输单元1220配置为当所述终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
图12实施例的其它内容可以参照上述其它实施例。
需要指出，图9至图12示出的各个单元，可以采用软件方式实现，例如可以是程序和模块；也可以采用硬件方式实现，例如可以采用一个或多个应用专用集成电路(ASIC，Application Specific Integrated Circuit)、DSP、可编程逻辑器件(PLD，Programmable Logic Device)、复杂可编程逻辑器件(CPLD，Complex Programmable Logic Device)、现场可编程门阵列(FPGA，Field-Programmable Gate Array)或其他电子元件实现。
需要指出，上述的第一核心网网元900、第二核心网网元1000和第三 网元1100可以采用通信设备实现。下面说明通信设备的示例性结构。
图13示意性示出了根据本公开的一实施例的通信设备1300的示意性结构图。该通信设备可以是终端，也可以是核心网设备，例如第一核心网网元和/或第二核心网网元和/或第三网元和/或第四核心网网元，图13所示的通信设备1300包括处理器1310，处理器1310可以从存储器中调用并运行计算机程序，以实现本公开实施例中的方法。
在一些实施例中，如图13所示，通信设备1300还可以包括存储器1320。其中，处理器1310可以从存储器1320中调用并运行计算机程序，以实现本公开实施例中的方法。
其中，存储器1320可以是独立于处理器1310的一个单独的器件，也可以集成在处理器1310中。
在一些实施例中，如图13所示，通信设备1300还可以包括收发器1330，处理器1310可以控制该收发器1330与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器1330可以包括发射机和接收机。收发器1330还可以进一步包括天线，天线的数量可以为一个或多个。
在一些实施例中，该通信设备1300具体可为本公开实施例的核心网设备，并且该通信设备1300可以实现本公开实施例方法中由核心网设备实现的相应流程，为了简洁，在此不再赘述。
在一些实施例中，该通信设备1300具体可为本公开实施例的移动终端/终端，并且该通信设备1300可以实现本公开实施例的各个方法中由移动终端/终端实现的相应流程，为了节约篇幅，在此不再赘述。
应理解，本公开实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。
上述的处理器可以是通用处理器、数字信号处理器、专用集成电路、现成可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本公开实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器 (Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(SynchlinkDRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。应理解，上述存储器为示例性但不是限制性说明。
本公开实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
在一些实施例中，该计算机可读存储介质可应用于本公开实施例中的核心网设备，并且该计算机程序使得计算机执行本公开实施例的各个方法中由核心网设备实现的相应流程，为了简洁，在此不再赘述。
在一些实施例中，该计算机可读存储介质可应用于本公开实施例中的移动终端/终端，并且该计算机程序使得计算机执行本公开实施例的各个方法中由移动终端/终端实现的相应流程，在此不再赘述。
本公开实施例还提供了一种计算机程序产品，包括计算机程序指令。
在一些实施例中，该计算机程序产品可应用于本公开实施例中的核心网设备，并且该计算机程序指令使得计算机执行本公开实施例的各个方法中由核心网设备实现的相应流程，为了简洁，在此不再赘述。
在一些实施例中，该计算机程序产品可应用于本公开实施例中的移动终端/终端，并且该计算机程序指令使得计算机执行本公开实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
本公开实施例还提供了一种计算机程序。
在一些实施例中，该计算机程序可应用于本公开实施例中的核心网设备，当该计算机程序在计算机上运行时，使得计算机执行本公开实施例的各个方法中由核心网设备实现的相应流程，为了简洁，在此不再赘述。
在一些实施例中，该计算机程序可应用于本公开实施例中的移动终端/终端，当该计算机程序在计算机上运行时，使得计算机执行本公开实施例的各个方法中由移动终端/终端实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方 案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本公开所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应所述以权利要求的保护范围为准。

Claims (19)

  1. 一种数据传输方法，所述方法由第一核心网网元执行，所述方法包括：
    生成终端路由选择策略URSP，其中，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息，所述高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据；
    将所述URSP通过第二核心网网元下发至所述终端。
  2. 根据权利要求1所述的方法，其中，所述RSD包括路径选择有效条件，所述路径选择有效条件包括位置条件；所述位置条件包括所述高度信息。
  3. 根据权利要求1所述的方法，其中，所述RSD包括路径选择有效条件，所述路径选择有效条件包括所述高度信息。
  4. 根据权利要求2或3所述的方法，其中，所述高度信息用于指示以下中的至少一项：
    若所述路径选择有效条件中包括时间窗口和所述高度信息，则所述高度信息指示当所述终端的高度匹配所述高度信息；若当前时间处于所述时间窗口内，选择所述RSD传输应用数据；
    若所述路径选择有效条件中包括位置信息和所述高度信息，则所述高度信息指示当所述终端的高度匹配所述高度信息；若当前位置匹配所述位置信息，选择所述RSD传输应用数据。
  5. 根据权利要求1所述的方法，其中，所述RSD包括路由选择组件；
    所述生成终端路由选择策略URSP，包括：
    接收第三网元发送的路由选择指示信息；
    参考所述路由选择指示信息，决定设置所述路由选择组件中的目标组件的值。
  6. 根据权利要求5所述的方法，其中，所述路由选择指示信息包括业务连续性指示信息；所述目标组件包括业务会话连续性模式选择组件；
    所述参考所述路由选择指示信息，决定设置所述路由选择组件中的目标组件的值，包括：
    参考所述业务连续性指示信息，决定设置所述业务会话连续性模式选择组件的值。
  7. 根据权利要求6所述的方法，其中，所述业务连续性指示信息用于指示是否支持终端网络地址变化，以及在终端网络地址变化时是否需要保持业务连续性；
    所述参考所述业务连续性指示信息，决定设置所述业务会话连续性模式选择组件的值，包括：
    当所述业务连续性指示信息指示不支持终端网络地址变化时，设置所述业务会话连续性模式选择组件的值为第一业务会话连续性模式；
    当所述业务连续性指示信息指示支持终端网络地址变化，且不需要保持业务连续性时，设置所述业务会话连续性模式选择组件的值为第二业务会话连续性模式；
    当所述业务连续性指示信息指示支持终端网络地址变化，且需要保持业务连续性时，设置所述业务会话连续性模式选择组件的值为第三业务会话连续性模式。
  8. 根据权利要求5所述的方法，其中，所述路由选择指示信息包括协议数据单元会话类型指示信息；所述目标组件包括协议数据单元会话类型选择组件；
    所述参考所述路由选择指示信息，决定设置所述路由选择组件中的目标组件的值，包括：
    参考所述协议数据单元会话类型指示信息，决定设置所述协议数据单元会话类型选择组件的值。
  9. 根据权利要求5所述的方法，其中，所述路由选择指示信息包括优先接入类型指示信息；所述目标组件包括接入类型偏好组件；
    所述参考所述路由选择指示信息，决定设置所述路由选择组件中的目标组件的值，包括：
    参考所述优先接入类型指示信息，决定设置所述接入类型偏好组件的值。
  10. 一种数据传输方法，所述方法由第二核心网网元执行，所述方法包括：
    接收第一核心网网元发送的终端路由选择策略URSP，其中，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息，所述高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据；
    将所述URSP下发至所述终端。
  11. 一种数据传输方法，所述方法由第三网元执行，所述方法包括：
    向第一核心网网元传输高度信息；
    所述高度信息用于生成终端路由选择策略URSP，其中，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括所述高度信息，所述高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
  12. 一种数据传输方法，所述方法由终端执行，所述方法包括：
    从第二核心网网元接收终端路由选择策略URSP，其中，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息；
    当所述终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
  13. 一种第一核心网网元，包括：
    生成单元，配置为生成终端路由选择策略URSP，其中，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息，所述高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据；
    发送单元，配置为将所述URSP通过第二核心网网元下发至所述终端。
  14. 一种第二核心网网元，包括：
    接收单元，用于接收第一核心网网元发送的终端路由选择策略URSP，其中，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息，所述高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据；
    发送单元，用于将所述URSP下发至所述终端。
  15. 一种第三网元，包括：
    发送单元，配置为向第一核心网网元传输高度信息；
    所述高度信息用于生成终端路由选择策略URSP，其中，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括所述高度信息，所述高度信息用于指示当终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
  16. 一种终端，包括：
    接收单元，配置为从第二核心网网元接收终端路由选择策略URSP，所述URSP包括URSP规则，所述URSP规则包括路由选择描述符RSD，所述RSD包括高度信息；
    传输单元，配置为当所述终端的高度匹配所述高度信息时，选择所述RSD传输应用数据。
  17. 一种通信设备，包括：
    一个或多个处理器；
    存储器，配置为存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行时，使得所述通信设备实现如权利要求1至9中任一项所述的方法；或者，
    如权利要求10所述的方法；或者，
    如权利要求11所述的方法；或者，
    如权利要求12所述的方法。
  18. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序使得通信设备执行如权利要求1至9中任一项所述的方法；或者，
    如权利要求10所述的方法；或者，
    如权利要求11所述的方法；或者，
    如权利要求12所述的方法。
  19. 一种计算机程序产品，包括计算机程序，所述计算机程序被处理器执行时实现权利要求1-9中任一项所述的方法；或者，
    如权利要求10所述的方法；或者，
    如权利要求11所述的方法；或者，
    如权利要求12所述的方法。
PCT/CN2022/132318 2022-01-11 2022-11-16 数据传输方法及相关设备、计算机可读存储介质、计算机程序产品 WO2023134295A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/340,516 US20230337109A1 (en) 2022-01-11 2023-06-23 Data transmission method, related device, computer-readable storage medium, and computer program product

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210028773.5A CN116471219A (zh) 2022-01-11 2022-01-11 数据传输方法及相关设备
CN202210028773.5 2022-01-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/340,516 Continuation US20230337109A1 (en) 2022-01-11 2023-06-23 Data transmission method, related device, computer-readable storage medium, and computer program product

Publications (1)

Publication Number Publication Date
WO2023134295A1 true WO2023134295A1 (zh) 2023-07-20

Family

ID=87175794

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/132318 WO2023134295A1 (zh) 2022-01-11 2022-11-16 数据传输方法及相关设备、计算机可读存储介质、计算机程序产品

Country Status (3)

Country Link
US (1) US20230337109A1 (zh)
CN (1) CN116471219A (zh)
WO (1) WO2023134295A1 (zh)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111491346A (zh) * 2020-05-13 2020-08-04 腾讯科技（深圳）有限公司 多播通信方法、装置、计算机可读介质及电子设备
US20200359295A1 (en) * 2019-05-06 2020-11-12 Mediatek Inc Enhanced ue route selection policy (ursp) rules selection
WO2021042398A1 (zh) * 2019-09-06 2021-03-11 Oppo广东移动通信有限公司 一种通信方法及装置、网络设备、终端设备
US20210258868A1 (en) * 2020-02-14 2021-08-19 Charter Communications Operating, Llc Apparatus and methods for generating and distributing policy in wireless networks
CN113412665A (zh) * 2019-07-12 2021-09-17 Oppo广东移动通信有限公司 一种会话设置方法、网络设备、用户设备
WO2021187913A1 (ko) * 2020-03-18 2021-09-23 엘지전자 주식회사 엣지 컴퓨팅과 관련된 통신
WO2021195170A1 (en) * 2020-03-27 2021-09-30 Ofinno, Llc Location management
CN113630749A (zh) * 2021-07-07 2021-11-09 华为技术有限公司 一种获取边缘服务的方法和装置

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200359295A1 (en) * 2019-05-06 2020-11-12 Mediatek Inc Enhanced ue route selection policy (ursp) rules selection
CN113412665A (zh) * 2019-07-12 2021-09-17 Oppo广东移动通信有限公司 一种会话设置方法、网络设备、用户设备
WO2021042398A1 (zh) * 2019-09-06 2021-03-11 Oppo广东移动通信有限公司 一种通信方法及装置、网络设备、终端设备
US20210258868A1 (en) * 2020-02-14 2021-08-19 Charter Communications Operating, Llc Apparatus and methods for generating and distributing policy in wireless networks
WO2021187913A1 (ko) * 2020-03-18 2021-09-23 엘지전자 주식회사 엣지 컴퓨팅과 관련된 통신
WO2021195170A1 (en) * 2020-03-27 2021-09-30 Ofinno, Llc Location management
CN111491346A (zh) * 2020-05-13 2020-08-04 腾讯科技（深圳）有限公司 多播通信方法、装置、计算机可读介质及电子设备
CN113630749A (zh) * 2021-07-07 2021-11-09 华为技术有限公司 一种获取边缘服务的方法和装置

Also Published As

Publication number Publication date
US20230337109A1 (en) 2023-10-19
CN116471219A (zh) 2023-07-21

Similar Documents

Publication Publication Date Title
EP3820176B1 (en) Policy mapping method, apparatus, and computer-readable storage medium
KR102452092B1 (ko) 세션 관리 방법, 단말 기기 및 네트워크 기기
US11638208B2 (en) Access network selection for a UE not supporting NAS over non-3GPP access
US12089146B2 (en) Determining a type of network connection from an OS-specific connection capability
WO2021217412A1 (zh) 一种确定终端策略行为的方法及装置、网络设备
US12082273B2 (en) Methods for service transmission, terminal device and AMF
WO2021046825A1 (zh) 无线通信的方法及设备
US11706623B2 (en) Communication method in vehicle to everything, user equipment, and network device
US20220150991A1 (en) Session verification method, user equipment, and policy control function entity
WO2020206677A1 (zh) 一种配置策略的方法及装置、网络设备、终端
CN113678506B (zh) 建立会话的方法和终端设备
WO2023134323A1 (zh) 终端路由选择策略检测方法及相关设备、存储介质、程序产品
WO2021022428A1 (zh) 无线通信的方法、终端设备和网络设备
WO2020042038A1 (zh) 通信方法和设备
WO2023134295A1 (zh) 数据传输方法及相关设备、计算机可读存储介质、计算机程序产品
WO2022147836A1 (zh) 一种连接建立方法及装置、网络设备
WO2023134335A1 (zh) 数据传输方法及相关设备、计算机可读存储介质、计算机程序产品
RU2787208C2 (ru) Способ, и устройство, и пользовательское оборудование для отображения политик
US12127034B2 (en) Method for QoS control 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: 22919928

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE