Data transmission method and related device

By introducing altitude information as a routing descriptor into URSP rules, the problem of not being able to support routing of UEs at specific altitudes in existing technologies is solved, enabling flexible data transmission and service continuity support for devices such as drones.

CN116471219BActive Publication Date: 2026-06-19TENCENT TECHNOLOGY (SHENZHEN) CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
TENCENT TECHNOLOGY (SHENZHEN) CO LTD
Filing Date
2022-01-11
Publication Date
2026-06-19

AI Technical Summary

Technical Problem

In existing technologies, URSP rules cannot effectively support UE routing at specific altitudes and the optimal selection of applications for network interaction.

Method used

Introducing altitude information as a condition for the routing descriptor (RSD) in URSP rules allows for the generation and distribution of URSP rules that meet the needs of terminal applications, including the routing descriptor (RSD), to instruct UEs at specific altitudes to transmit data.

Benefits of technology

It enables routing and service continuity support for UEs at specific altitudes, improves the flexibility and adaptability of data transmission, and meets the service needs of specific devices such as drones.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116471219B_ABST
    Figure CN116471219B_ABST
Patent Text Reader

Abstract

This disclosure provides a data transmission method and related equipment, belonging to the field of communication technology. The method is executed by a first core network element and includes: generating a terminal routing policy (URSP), whereby the URSP includes URSP rules, each URSP rule includes a routing descriptor (RSD), and the RSD includes altitude information. The altitude information indicates that when the terminal's altitude matches the altitude information, the RSD is selected to transmit application data; and the URSP is then distributed to the terminal via a second core network element. The solution provided by this disclosure considers the terminal's altitude when generating URSP rules, resulting in URSP rules that meet the terminal's application requirements.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to a data transmission method, a first core network element, a second core network element, a terminal, a communication device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] UE (User Equipment) policies include URSP (UE Route Selection Policy), but the content of URSP rules in related technologies needs to be further expanded according to specific business requirements to support specific business needs. Summary of the Invention

[0003] This disclosure provides a data transmission method, a first core network element, a second core network element, a terminal, a communication device, a computer-readable storage medium, and a computer program product, which can take the terminal's height into account when generating URSP rules and generate URSP rules that meet the terminal's application requirements.

[0004] This disclosure provides a data transmission method executed by a first core network element. The method includes: generating a terminal routing policy (URSP), wherein the URSP includes URSP rules, the URSP rules include routing descriptors (RSDs), and the RSDs include altitude information, wherein 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; and distributing the URSP to the terminal through a second core network element.

[0005] This disclosure provides a data transmission method executed by a second core network element. The method includes: receiving a terminal routing selection policy (URSP) sent by a first core network element, wherein the URSP includes URSP rules, the URSP rules include routing descriptors (RSDs), and the RSDs include altitude information, wherein 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; and sending the URSP to the terminal.

[0006] This disclosure provides a data transmission method executed by a third network element. The method includes: transmitting altitude information to a first core network element; the altitude information is used to generate a terminal routing selection policy (URSP), the URSP including URSP rules, the URSP rules including a routing descriptor (RSD), the RSD including altitude information, and the altitude information being used to indicate that when the altitude of the terminal matches the altitude information, the RSD is selected to transmit application data.

[0007] This disclosure provides a data transmission method executed by a terminal. The method includes: receiving a terminal routing selection policy (URSP) from a second core network element, wherein the URSP includes URSP rules, the URSP rules include routing descriptors (RSDs), and the RSDs include altitude information; and when the altitude of the terminal matches the altitude information, selecting the RSD to transmit application data.

[0008] This disclosure provides a first core network element, including: a generation unit, configured to generate a terminal routing policy (URSP), the URSP including URSP rules, the URSP rules including routing descriptors (RSDs), the RSDs including altitude information, the altitude information being used to indicate that when the altitude of the terminal matches the altitude information, the RSD is selected to transmit application data; and a sending unit, configured to send the URSP to the terminal through a second core network element.

[0009] This disclosure provides a second core network element, including: a receiving unit, configured to receive a terminal routing policy (URSP) sent by a first core network element, the URSP including URSP rules, the URSP rules including routing descriptors (RSDs), the RSDs including altitude information, the altitude information being used to indicate that when the altitude of the terminal matches the altitude information, the RSD is selected to transmit application data; and a sending unit, configured to send the URSP to the terminal.

[0010] This disclosure provides a third network element, including: a transmitting unit, configured to transmit altitude information to a first core network element; the altitude information is used to generate a terminal routing policy (URSP), the URSP including URSP rules, the URSP rules including a routing descriptor (RSD), the RSD including altitude information, and the altitude information being used to indicate that when the altitude of the terminal matches the altitude information, the RSD is selected to transmit application data.

[0011] This disclosure provides a terminal, including: a receiving unit, configured to receive a terminal routing selection policy (URSP) from a second core network element, the URSP including URSP rules, the URSP rules including a routing descriptor (RSD), the RSD including altitude information; and a transmitting unit, configured to select the RSD to transmit application data when the altitude of the terminal matches the altitude information.

[0012] This disclosure provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the data transmission method as described in the above embodiments.

[0013] This disclosure provides a communication device, including: one or more processors; and a memory configured to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the communication device implements the data transmission method as described in the above embodiments.

[0014] The method provided in this disclosure can further expand the content of URSP rules according to specific business needs, thereby supporting specific business requirements. For example, it addresses how to perform specific routing for UEs with specific altitudes, such as drones, and how to support routing for UEs at specific altitudes through application-network interaction. Attached Figure Description

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

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

[0017] Figure 3 A flowchart illustrating a data transmission method according to an embodiment of the present disclosure is shown schematically.

[0018] Figure 4 The illustration shows an interactive diagram of a data transmission method according to an embodiment of the present disclosure.

[0019] Figure 5 The illustration shows an interactive diagram of a data transmission method according to another embodiment of the present disclosure.

[0020] Figure 6 A flowchart illustrating a data transmission method according to another embodiment of the present disclosure is shown schematically.

[0021] Figure 7 A flowchart illustrating a data transmission method according to yet another embodiment of the present disclosure is shown.

[0022] Figure 8 A flowchart illustrating a data transmission method according to another embodiment of the present disclosure is shown.

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

[0024] Figure 10 A block diagram of a second core network element according to an embodiment of the present disclosure is shown schematically.

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

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

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

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

[0029] The technical solutions of this disclosure can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, or 5G system, etc.

[0030] For example, the communication system 100 used in this disclosure embodiment is as follows: Figure 1As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal 120 (or a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminals located within that coverage area. Optionally, the network device 110 may be a base station (BTS) in a GSM or CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, a base station in a 5G communication system, or a radio controller in a Cloud Radio Access Network (CRAN). Alternatively, the network device may be a mobile switching center, relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, network-side equipment in a 5G network, or network equipment in a future evolved Public Land Mobile Network (PLMN), etc.

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

[0032] Optionally, the terminals 120 can communicate directly with each other via Device to Device (D2D).

[0033] Alternatively, a 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0034] Figure 1 An exemplary network device and two terminals are shown. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within its coverage area. This disclosure does not limit the scope of the embodiments.

[0035] Optionally, the communication system 100 may also include other network entities such as a network policy control entity and a mobility management entity, which are not limited in this embodiment.

[0036] It should be understood that devices with communication functions in the network / system of this disclosure embodiment may be referred to as communication devices. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal 120 with communication functions. The network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as network policy control entities, mobility management entities, and other network entities. This disclosure does not limit this.

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

[0038] Figure 2 This is a system architecture diagram of a 5G network according to an embodiment of the present disclosure, such as... Figure 2As shown, the equipment involved in the 5G network system includes: 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).

[0039] like Figure 2 As shown, the network elements related to policies are mainly PCF, AMF, SMF, RAN, and UE. Among them, SMF is mainly responsible for the execution of session-related policies, while AMF is mainly responsible for the execution of access and UE-related policies. The policy distribution and updates on the two network elements (AMF and SMF) are all managed by PCF.

[0040] Specifically regarding UE policies, the PCF and UE can monitor UE policy-related information through containers, including the content of the UE policy and the UE policy identifier. In the uplink direction, the UE sends the container to the AMF via NAS (non-access-stratum) messages, and the AMF then forwards it to the PCF (without not noticing or modifying it). In the downlink direction, the PCF sends the container to the AMF, and the AMF then forwards it to the UE via NAS messages.

[0041] UE policies include URSPs. A URSP contains multiple policy rules (called URSP Rules), each consisting of a Traffic Descriptor and a set of Route Selection Descriptors (RSDs). The Traffic Descriptor in the URSP describes a specific service. A Traffic Descriptor can have one or more RSDs, and each RSD corresponds to an attribute of a PDU session. This means that the service data corresponding to the Traffic Descriptor can run within the PDU session corresponding to the RSD.

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

[0043] Table 1: URSP Rules

[0044]

[0045]

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

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

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

[0049] Table 2: RSD

[0050]

[0051]

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

[0053] Route Selection Validation Criteria, also known as route selection verification criteria, describes the corresponding conditions for effectiveness. It includes a time window (also known as a valid time window) and location criteria (also known as location conditions). 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.

[0054] Among them, SSC mode, S-NSSAI (Single Network Slice Selection Assistance Information), PDU session type, and DNN are all parameters related to PDU session attributes.

[0055] The URSP rules in related technologies cannot solve the UE routing problem at a specific altitude, nor can they indicate a specific preferred choice through application-network interaction.

[0056] Figure 3 The data transmission method provided in the embodiments can be executed by a first core network element. In the exemplary embodiments, the first core network element can be a PCF, but this disclosure is not limited thereto.

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

[0058] In S310, the terminal routing policy URSP is generated.

[0059] The URSP can include one or more (two or more) URSP rules, and each URSP rule can include a routing descriptor (RSD). One or each RSD can include altitude information, which is used to indicate that when the altitude of the terminal matches the altitude information in the RSD, the corresponding RSD should be selected to transmit the terminal's application data.

[0060] URSPs can be used to map specific service flows to corresponding data transmission sessions for a UE. For example, the PCF can generate multiple URSP rules in the core network, each of which can include a Traffic Descriptor and a Routing Descriptor (RSD). When an application on the UE starts, the UE can match the Traffic Descriptor in the URSP rules generated by the core network with the traffic characteristics of the application to determine the corresponding URSP. Each URSP rule can include one or more RSDs, and the priority of each RSD in the URSP rule can be configured according to service requirements and service type. After matching the corresponding URSP, the UE can select the appropriate RSD based on the priority of each generated RSD and transmit the application's data (referred to as service data or application data) in the data transmission session corresponding to that RSD.

[0061] In this embodiment of the disclosure, a drone is used as an example for illustration, but it is not limited to this. The method provided in this disclosure can be applied to any UE that needs to perform routing selection at a specific altitude. The specific altitude is set in the RSD of the URSP rule as the altitude information in the RSD. The altitude information can be a range of values ​​or a specific value. The value of the altitude information can be set according to actual needs, and this disclosure does not limit it.

[0062] In this embodiment of the disclosure, when supporting drone scenarios, the application can define a specific routing path for the drone's flight altitude. For example, assuming the altitude information in the RSD is set to 10m-30m, when the drone's flight altitude is between 10m and 30m, the drone can officially enter working mode and initiate video transmission. By setting other parameters in the RSD, such as allowing the drone to access network slice S-NSSAI-1 and selecting SSC mode 3 for service continuity, the drone can be controlled to not work upon takeoff and only enter working mode and initiate video transmission when it reaches a specific altitude. At that specific altitude, any parameter in the RSD, such as S-NSSAI, DNN, or SSC mode, can be specified and set to any value as needed.

[0063] In an exemplary embodiment, the RSD may include path selection validity conditions, which may include location conditions; the location conditions include altitude information.

[0064] In an exemplary embodiment, the RSD may include path selection validity conditions, which may include the height information.

[0065] In this embodiment of the disclosure, in order to support the above scenario, a height-related parameter (height information) is first added to the URSP rule. Furthermore, in the process of AF influencing URSP rules through interaction between AF and network, corresponding parameters can be added, such as AF directly or indirectly sending height information and / or routing indication information to PCF.

[0066] The relevant URSP rules define Route Selection Validation Criteria, which includes a Time Window and a Location Criteria.

[0067] - Time window: The UE will execute the RSD defined in the URSP rule only when the time window conditions are met. If the current time is not within the time window, the UE considers the RSD invalid.

[0068] - Location Conditions: Defines the UE location information that matches the service flow route. If the UE location does not meet the location conditions, the UE considers the RSD invalid.

[0069] In related technologies, the specific content of location criteria is as follows:

[0070]

[0071]

[0072] E-UTRA is short for Evolved-UMTS Terrestrial Radio Access. TAI is short for Tracking Area Identity.

[0073] This disclosure proposes to supplement height information in the Route Selection Validation Criteria of URSP rules as a criterion for evaluating whether an RSD is valid.

[0074] One implementation method is to use the height information as a specific parameter of the location criteria, that is, to add height information as the location area type in the location criteria, so that the location conditions include height information.

[0075] Another implementation is to add a parameter to the Route Selection Validation Criteria that is parallel to Time Window and location criteria: height information, that is, the path validity conditions include height information.

[0076] In this embodiment of the disclosure, the altitude information refers to the altitude information of the UE that matches the service flow route. That is, the RSD will only be executed when the UE is at the current altitude; the RSD will not be executed when the UE is not at the current altitude.

[0077] In an exemplary embodiment, the height information set in the RSD can be used to indicate at least one of the following:

[0078] If the valid conditions for path selection include a time window and the height information, then the height information indicates that when the height of the terminal matches the height information and the current time is within the time window, the RSD is selected to transmit application data.

[0079] If the valid path selection conditions include location information and height information, then the height information indicates that when the height of the terminal matches the height information and the current location is within the location information, the RSD is selected to transmit application data.

[0080] In this embodiment of the disclosure, height information can be used alone as a condition for evaluating the validity of the RSD. However, height information can also be used together with at least one of time window information and location information to constitute a condition for evaluating the validity of the RSD, as shown in the following example:

[0081] - When the Route Selection Validation Criteria includes both time window information and altitude information, the RSD is executed if the UE's current altitude is within the altitude information and the time is within the time window. If the UE's current altitude is not within the altitude information or the time is not within the time window, i.e., if one of the two conditions is not met, the RSD is not executed.

[0082] - When the Route Selection Validation Criteria includes both location information and altitude information, the RSD is executed only if the UE's current altitude and current location are both within the altitude and location information. If either the UE's current altitude or current location is not within the altitude or location information, i.e., one of the two conditions is not met, the RSD is not executed.

[0083] - When the Route Selection Validation Criteria includes time window information, location information, and altitude information, the RSD is executed only if the UE's current altitude is within the altitude information, the time is within the time window, and the UE's current location is within the location information. If any of the three conditions is not met, the RSD is not executed.

[0084] In an exemplary embodiment, generating a terminal routing policy (URSP) may include: receiving altitude information sent by a third network element; and, referring to the received altitude information, deciding to set the altitude information in the path selection validity conditions. In this embodiment, the third network element may be an access point (AF), but this disclosure is not limited to this. After receiving altitude information from the AF, the PCF can decide whether to accept the received altitude information based on 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 does not set the altitude information in the URSP rule.

[0085] In an exemplary embodiment, receiving altitude information sent by a third network element may include receiving service parameters sent by the third network element, wherein the service parameters may include the altitude information.

[0086] In an exemplary embodiment, receiving altitude information sent by a third network element may include receiving the altitude information from a fourth core network element. The fourth core network element may be used to receive the altitude information from the third network element.

[0087] The relevant technologies define the process by which AF affects URSP rules. The parameter information that the UE can provide to network elements such as NEF (fourth core network element) includes:

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

[0089] 2) Service Parameters.

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

[0091] 4) Subscription to events.

[0092] In this embodiment, the AF can add altitude information to the Service Parameters. Specifically, when the AF requests the network to select a specific route for a UE at a specific altitude, it instructs the PCF to consider the AF's request when generating URSP rules, setting the altitude information carried in the Service Parameters in a specific Route Selection Validation Criteria. The AF can send the altitude information carried in the Service Parameters to the PCF via the NEF, or it can send it directly to the PCF. After receiving the information from the AF, the PCF can decide whether to accept the AF's request to set the URSP rules according to its own policy.

[0093] It should be noted that AF can send altitude information to PCF in existing messages and parameters, or it can send altitude information to PCF in new messages and / or new parameters, or send altitude information to PCF in new messages and new parameters. This disclosure does not limit this.

[0094] In an exemplary embodiment, the RSD may include route selection components. Generating a terminal routing policy (URSP) may include: receiving routing indication information sent by a third network element; and determining, with reference to the routing indication information, setting the value of the target component in the route selection components.

[0095] In this embodiment of the disclosure, the target component can be any one or more of the route selection components of the RSD, such as SSC Mode Selection and / or Network Slice Selection and / or DNN Selection and / or PDU Session Type Selection and / or Non-Seamless Offload indication and / or ProSe Layer-3 UE-to-Network Relay Offload indication and / or Access Type preference and / or PDU Session Pair ID and / or RSN. The route selection indication information can be used to set values ​​in the target component, such as one or more of a specific SSC mode, a specific S-NSSAI or a list of S-NSSAI(s), a specific DNN or a list of DNN(s), a specific PDU Session Type, a specific access type preference (3GPP / non-3GPP / Multi-Access), etc. The following uses SSC Mode, PDU Session Type, and Access Type preference as examples, but this disclosure is not limited to these.

[0096] In an exemplary embodiment, receiving routing indication information sent by a third network element may include: receiving service parameters sent by the third network element, wherein the service parameters may include the routing indication information.

[0097] In this embodiment of the disclosure, the PCF can directly receive service parameters carrying routing indication information from the AF, or indirectly receive service parameters carrying routing indication information from the AF through the NEF.

[0098] In this embodiment of the disclosure, routing selection indication information can be added to the service parameters, or a new parameter can be added that includes routing selection indication information. This disclosure does not limit this.

[0099] In an exemplary embodiment, the routing indication information may include service continuity indication information; the target component may include a Service Session Continuity Mode Selection (SSC) component. Specifically, determining the value of the target component in the routing component by referring to the routing indication information may include: determining the value of the Service Session Continuity Mode Selection (SSC) component by referring to the service continuity indication information.

[0100] In an exemplary embodiment, the business continuity indication information may include a value of the business session continuity mode.

[0101] In an exemplary embodiment, the service continuity indication information can be used to indicate whether terminal network address changes are supported and whether service continuity needs to be maintained when the terminal network address changes. Specifically, determining the value of the service session continuity mode selection component by referring to the service continuity indication information may include: setting the value of the service session continuity mode selection component to a first service session continuity mode when the service continuity indication information indicates that terminal network address changes are not supported; setting the value of the service session continuity mode selection component to a second service session continuity mode when the service continuity indication information indicates that terminal network address changes are supported and service continuity does not need to be maintained; and setting the value of the service session continuity mode selection component to a third service session continuity mode when the service continuity indication information indicates that terminal network address changes are supported and service continuity needs to be maintained.

[0102] In this embodiment of the disclosure, service continuity indication information can be added to 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 AF's request when generating PCF rules, and uses the service continuity indication information to set the SSCMode in the Route selection components in the URSP.

[0103] In this embodiment of the disclosure, there are two ways to add service continuity indication information in Service Parameters: one is to directly indicate the value of the specific SSC Mode, and the other is to indicate whether the UE IP (Internet Protocol) address (terminal network address) change is supported and whether service continuity needs to be maintained when the IP address changes.

[0104] Among them, "Does not support UE IP address changes" corresponds to SSC mode 1 (first service session continuity mode); "Supports UE IP address changes, but does not require maintaining service continuity" corresponds to SSC mode 2 (second service session continuity mode); and "Supports UE IP address changes, but requires maintaining service continuity" corresponds to SSC mode 3 (third service session continuity mode).

[0105] In an exemplary embodiment, the routing indication information may include Protocol Data Unit (PDU) Session Type Indication information; the target component may include a Protocol Data Unit (PDU) Session Type Selection component. Specifically, determining the value of the target component in the routing indication component by referring to the routing indication information may include: determining the value of the Protocol Data Unit (PDU) Session Type Selection component by referring to the Protocol Data Unit (PDU) Session Type Indication information.

[0106] In this embodiment of the disclosure, PDU session type indication information (the specific value can be IPv4, IPv6, IPv4v6, Enternet, or Unstructured) can be added to 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 AF's request 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 Routeselection components in URSP.

[0107] In an exemplary embodiment, the routing indication information may include preferred access type indication information; the target component includes an access type preference component. Specifically, determining the value of the target component in the routing component by referring to the routing indication information may include: determining the value of the access type preference component by referring to the preferred access type indication information.

[0108] In this embodiment of the disclosure, priority access type indication information (the specific value can be 3GPP access, non-3GPP access, or multi-access) can be added to 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 AF's request when generating URSP rules, and uses the priority access type indication information carried in Service Parameters to set the Access Type preference of PDU in Route selection components in URSP.

[0109] In S320, the URSP is sent to the terminal via the second core network element. In this embodiment of the present disclosure, the second core network element may be an AMF, but the present disclosure is not limited to this.

[0110] For example, Figure 1 In this embodiment, network device 110 can be the core network device of the communication system, and can generate multiple URSP rules. Each URSP rule can include a Traffic Descriptor and an RSD. Terminal 120 can have one or more applications installed. When an application on terminal 120 is started, terminal 120 can match the Traffic Descriptor in the URSP rule according to the traffic characteristics of the started application, and route the data of the started application according to the RSD of the corresponding Traffic Descriptor.

[0111] URSP rules can contain one or more RSDs, each of which can be used to indicate the corresponding PDU session. For example, an RSD can contain parameters for establishing a PDU session, such as: DNN, Network Slice Selection Policy, S-NSSAI, PDU session type, etc. Different RSDs may correspond to different PDU sessions, providing different internet browsing experiences.

[0112] The method provided in this disclosure can further expand the content of URSP rules according to specific service requirements to support specific service demands. For example, it can perform specific routing selection for UEs with specific altitudes, such as drones, and support routing selection for UEs at specific altitudes through application-network interaction; furthermore, it can also provide specific service continuity indications through application-network interaction; and furthermore, it can select specific PDU session types through application-network interaction, etc.

[0113] Figure 4The example uses PCF as the first core network element, AMF as the second core network element, and AF as the third network element, with AF and PCF interacting directly.

[0114] Figure 4 The illustration schematically depicts an interaction diagram of a data transmission method according to an embodiment of the present disclosure. For example... Figure 4 As shown, the method provided in this disclosure embodiment may include:

[0115] In S41, the AF sends altitude information and routing instructions to the PCF.

[0116] In S42, after receiving altitude information and routing indication information from AF, PCF refers to the altitude information and routing indication information to decide whether to accept the altitude information and / or routing indication information. If it decides to accept the altitude information, it includes the altitude information in the RSD of the generated URSP rule; if it does not accept the altitude information, it does not include the altitude information in the RSD of the generated URSP rule. If it decides to accept the routing indication information, it refers to the routing indication information to decide to set the value of the target component in the routing component; if it decides not to accept the routing indication information, it does not refer to the routing indication information to decide to set the value of the target component in the routing component.

[0117] It is understood that altitude information and routing indication information can be included in existing parameters of existing messages, or in newly added parameters of existing messages, or can be transmitted through newly added messages; this disclosure does not limit this.

[0118] It should be noted that S41 above is optional, meaning that PCF can also directly generate URSP.

[0119] In S43, the PCF sends the generated URSP to the AMF.

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

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

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

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

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

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

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

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

[0128] If no suitable PDU session can be found for binding according to the matching URSP rules, the UE searches for the Traffic Descriptor in the next higher priority URSP rule according to the priority order to see if it can match the application data flow characteristics. If a match is found, the process described above is repeated.

[0129] The method provided in this disclosure also enables the network to consider the application's input information (height information and / or routing indication information) when generating URSP rules through the interaction between the application and the network, thereby generating URSP rules that meet the application's requirements.

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

[0131] Figure 5The example uses PCF as the first core network element, AMF as the second core network element, AF as the third core network element, and NEF as the fourth core network element, with AF and PCF interacting through NEF for illustration.

[0132] Figure 5 The illustration schematically depicts an interactive diagram of a data transmission method according to another embodiment of this disclosure. For example... Figure 5 As shown, the method provided in this disclosure embodiment may include:

[0133] In S51, the AF sends altitude information and routing instructions to the NEF.

[0134] In S52, after NEF receives altitude information and routing indication information from AF, it forwards them to PCF.

[0135] In S53, after receiving altitude information and routing indication information from NEF, PCF decides whether to accept the received altitude information and routing indication information in order to generate URSP.

[0136] It should be noted that S51 and S52 above are optional, meaning that PCF can also directly generate URSP.

[0137] In S54, the PCF sends the generated URSP to the AMF.

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

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

[0140] Figure 6 The data transmission method provided in the embodiment can be executed by a second core network element. In the exemplary embodiment, the second core network element can be an AMF.

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

[0142] In S610, a terminal routing policy URSP sent by a first core network element is received. The URSP includes URSP rules, and the URSP rules include a routing descriptor RSD. The RSD includes altitude information, which is used to indicate that when the altitude of the terminal matches the altitude information, the RSD is selected to transmit application data.

[0143] In S620, the URSP is sent to the terminal.

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

[0145] Figure 7 The data transmission method provided in the embodiment can be executed by a third network element. In the exemplary embodiment, the third network element can be an AF.

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

[0147] In the S710, altitude information is transmitted to the first core network element.

[0148] The altitude information can be used to generate a Routing Reference Spectrum (URSP). For example, the first core network element can be used to generate a Routing Reference Spectrum (URSP) for the terminal based on the altitude information. The URSP includes URSP rules, the URSP rules include Routing Reference Spectrum Descriptors (RSDs), and the RSDs include the altitude information. The altitude information can be used to indicate that when the terminal's altitude matches the altitude information, the RSD should be selected to transmit application data.

[0149] In an exemplary embodiment, the RSD may further include a routing component. The method may further include: transmitting routing indication information to a first core network element; the first core network element may also refer to the routing indication information to determine the value of a target component in the routing component.

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

[0151] Figure 8 The data transmission method provided in the embodiments can be executed by a terminal, but this disclosure is not limited thereto.

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

[0153] In S810, a terminal routing policy URSP is received from a second core network element. The URSP includes URSP rules, and the URSP rules include routing descriptors RSDs, which include height information.

[0154] In S820, when the height of the terminal matches the height information, the RSD is selected to transmit application data.

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

[0156] like Figure 9 As shown, Figure 9The first core network element 900 provided in the embodiment can generate a unit 910 and a transmission unit 920.

[0157] The generation unit 910 can be used to generate a terminal routing policy URSP, the URSP including URSP rules, the URSP rules including a routing descriptor RSD, the RSD including altitude information, the altitude information being used to indicate that when the altitude of the terminal matches the altitude information, the RSD is selected to transmit application data.

[0158] The sending unit 920 can be used to send the URSP to the terminal through the second core network element.

[0159] In an exemplary embodiment, the RSD may include path selection validity conditions, which include location conditions; the location conditions may include the altitude information.

[0160] In an exemplary embodiment, the RSD includes path selection validity conditions, which include the altitude information.

[0161] In an exemplary embodiment, the height information may be used to indicate at least one of the following:

[0162] If the valid conditions for path selection include a time window and the height information, then the height information can indicate that when the height of the terminal matches the height information and the current time is within the time window, the RSD should be selected to transmit application data.

[0163] If the valid conditions for path selection include location information and height information, then the height information can indicate that when the height of the terminal matches the height information and the current location is within the location information, the RSD should be selected to transmit application data.

[0164] In an exemplary embodiment, the first core network element 900 may further include a receiving unit, which can be used to receive altitude information sent by a third network element. The generating unit 910 may also be used to refer to the received altitude information to determine how to set the altitude information in the path selection validity conditions.

[0165] In an exemplary embodiment, the receiving unit can also be used to: receive service parameters sent by the third network element, the service parameters including the height information.

[0166] In an exemplary embodiment, the receiving unit may further be configured to: receive the altitude information from a fourth core network element. The fourth core network element may be configured to receive the altitude information from the third network element.

[0167] In an exemplary embodiment, the RSD may include a routing component. The first core network element 900 may further include a receiving unit, which can be used to receive routing indication information sent by a third network element. The generating unit 910 may also be used to determine the value of the target component in the routing component by referring to the routing indication information.

[0168] In an exemplary embodiment, the receiving unit may also be used to: receive service parameters sent by the third network element, wherein the service parameters may include the routing indication information.

[0169] In an exemplary embodiment, the routing indication information may include service continuity indication information; the target component may include a service session continuity mode selection component. The generation unit 910 may also be configured to: determine, with reference to the service continuity indication information, the value of the service session continuity mode selection component.

[0170] In an exemplary embodiment, the business continuity indication information may include a value of the business session continuity mode.

[0171] In an exemplary embodiment, the service continuity indication information can be used to indicate whether terminal network address changes are supported and whether service continuity needs to be maintained when the terminal network address changes. The generation unit 910 can also be configured to: set the value of the service session continuity mode selection component to a first service session continuity mode when the service continuity indication information indicates that terminal network address changes are not supported; set the value of the service session continuity mode selection component to a second service session continuity mode when the service continuity indication information indicates that terminal network address changes are supported and service continuity does not need to be maintained; and set the value of the service session continuity mode selection component to a third service session continuity mode when the service continuity indication information indicates that terminal network address changes are supported and service continuity needs to be maintained.

[0172] In an exemplary embodiment, the routing indication information may include Protocol Data Unit (PDU) session type indication information; the target component may include a PDU session type selection component. The generation unit 910 may also be configured to: determine the value of the PDU session type selection component by referring to the PDU session type indication information.

[0173] In an exemplary embodiment, the routing indication information may include preferred access type indication information; the target component may include an access type preference component. The generation unit 910 may also be configured to: determine, with reference to the preferred access type indication information, set the value of the access type preference component.

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

[0175] like Figure 10 As shown, Figure 10 The second core network element 1000 provided in the embodiment may include a receiving unit 1010 and a transmitting unit 1020.

[0176] The receiving unit 1010 can be used to receive a terminal routing policy URSP sent by a first core network element. The URSP includes URSP rules, the URSP rules include routing descriptors 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.

[0177] The sending unit 1020 can be used to send the URSP to the terminal.

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

[0179] like Figure 11 As shown, Figure 11 The third network element 1100 provided in the embodiment may include a transmitting unit 1110.

[0180] The transmitting unit 1110 can be used to transmit the altitude information to the first core network element.

[0181] Altitude information can be used to generate a terminal routing policy (URSP). The URSP can include URSP rules, which can include routing descriptors (RSDs). The RSDs can include altitude information, which can be used to indicate that when the altitude of the terminal matches the altitude information, the RSD should be selected to transmit application data.

[0182] In an exemplary embodiment, the RSD may further include a routing component.

[0183] The sending unit 1110 can also be used to transmit routing indication information to the first core network element. The first core network element can also refer to the routing indication information to determine the value of the target component in the routing component.

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

[0185] like Figure 12 The above, Figure 12 The terminal 1200 provided in the embodiment may include a receiving unit 1210 and a transmitting unit 1220.

[0186] The receiving unit 1210 can be used to receive a terminal routing policy URSP from a second core network element. The URSP includes URSP rules, the URSP rules include routing descriptors RSD, and the RSD includes height information.

[0187] The transmission unit 1220 can be used to select the RSD to transmit application data when the height of the terminal matches the height information.

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

[0189] Figure 13 A schematic structural diagram of a communication device 1300 according to an embodiment of the present disclosure is shown. This communication device can 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 core network element and / or a fourth core network element. Figure 13 The communication device 1300 shown includes a processor 1310, which can call and run computer programs from memory to implement the methods in the embodiments of this disclosure.

[0190] Optionally, such as Figure 13 As shown, the communication device 1300 may further include a memory 1320. The processor 1310 can retrieve and run computer programs from the memory 1320 to implement the methods described in this embodiment.

[0191] The memory 1320 can be a separate device independent of the processor 1310, or it can be integrated into the processor 1310.

[0192] Optionally, such as Figure 13 As shown, the communication device 1300 may also include a transceiver 1330, and the processor 1310 may control the transceiver 1330 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0193] 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.

[0194] Optionally, the communication device 1300 may specifically be a core network device in the embodiments of this disclosure, and the communication device 1300 may implement the corresponding processes implemented by the core network device in the various methods of the embodiments of this disclosure. For the sake of brevity, it will not be described in detail here.

[0195] Optionally, the communication device 1300 may specifically be a mobile terminal / terminal in the embodiments of this disclosure, and the communication device 1300 may implement the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of this disclosure. For the sake of brevity, it will not be described in detail here.

[0196] It should be understood that the processor in this embodiment of the disclosure may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by software instructions.

[0197] The aforementioned processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this disclosure. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this disclosure can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above methods.

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

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

[0200] Optionally, the computer-readable storage medium can be applied to the core network device in the embodiments of this disclosure, and the computer program causes the computer to execute the corresponding processes implemented by the core network device in the various methods of the embodiments of this disclosure, which will not be described in detail here for the sake of brevity.

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

[0202] This disclosure also provides a computer program product, including computer program instructions.

[0203] Optionally, the computer program product can be applied to the core network device in the embodiments of this 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 this disclosure. For the sake of brevity, they will not be described in detail here.

[0204] Optionally, the computer program product can be applied to the mobile terminal / terminal in the embodiments of this disclosure, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of this disclosure. For the sake of brevity, these will not be described in detail here.

[0205] This disclosure also provides a computer program.

[0206] Optionally, the computer program can be applied to the core network device in the embodiments of this disclosure. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the core network device in the various methods of the embodiments of this disclosure. For the sake of brevity, it will not be described in detail here.

[0207] Optionally, the computer program can be applied to the mobile terminal / terminal in the embodiments of this disclosure. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal in the various methods of the embodiments of this disclosure. For the sake of brevity, it will not be described in detail here.

[0208] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0209] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0210] In the several embodiments provided in this disclosure, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0211] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0212] In addition, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0213] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A data transmission method, characterized by, The method is executed by a first core network element, and the method includes: A terminal routing policy URSP is generated. The URSP includes URSP rules, and each URSP rule includes a routing descriptor RSD. The RSD includes altitude information, which indicates that when the terminal's altitude matches the altitude information, the RSD should be selected to transmit application data. If the RSD also includes location information, the altitude information indicates that when the terminal's altitude matches the altitude information and the terminal's current location is within the location information, the RSD should be selected to transmit application data. The URSP is sent to the terminal through the second core network element.

2. The method of claim 1, wherein, The RSD includes path selection validity conditions, which include location conditions. The location conditions include the height information.

3. The method of claim 1, wherein, The RSD includes path selection validity conditions, which include the altitude information.

4. The method according to claim 2 or 3, characterized in that, The altitude information is used to indicate at least one of the following: If the valid conditions for path selection include a time window and the height information, then the height information indicates that when the height of the terminal matches the height information and the current time is within the time window, the RSD is selected to transmit application data. If the valid path selection conditions include location information and height information, then the height information indicates that when the height of the terminal matches the height information and the current location is within the location information, the RSD is selected to transmit application data.

5. The method of claim 1, wherein, The RSD includes a routing component; The generation of the terminal routing selection policy URSP includes: Receive routing indication information sent by a third network element; Referring to the routing indication information, determine the value of the target component in the routing component.

6. The method of claim 5, wherein, The routing indication information includes service continuity indication information; The target component includes a service session continuity mode selection component; Specifically, determining the value of the target component in the routing component by referring to the routing indication information includes: Based on the business continuity indication information, determine the value of the business session continuity mode selection component.

7. The method of claim 6, wherein, The service continuity indication information is used to indicate whether changes to the terminal network address are supported and whether service continuity needs to be maintained when the terminal network address changes. Specifically, determining the value of the service session continuity mode selection component by referring to the service continuity indication information includes: When the service continuity indication information indicates that the terminal network address change is not supported, the value of the service session continuity mode selection component is set to the first service session continuity mode. When the service continuity indication information indicates that the terminal network address change is supported and service continuity is not required, the value of the service session continuity mode selection component is set to the second service session continuity mode. When the service continuity indication information indicates that the terminal network address changes are 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.

8. The method of claim 5, wherein, The routing selection indication information includes protocol data unit session type indication information; The target component includes a protocol data unit session type selection component; Specifically, determining the value of the target component in the routing component by referring to the routing indication information includes: Referencing the protocol data unit session type indication information, determine the value of the protocol data unit session type selection component.

9. The method of claim 5, wherein, The routing selection indication information includes priority access type indication information; The target component includes an access type preference component; Specifically, determining the value of the target component in the routing component by referring to the routing indication information includes: Based on the preferred access type indication information, determine the value of the access type preference component.

10. A data transmission method, characterized by, The method is executed by a second core network element, and the method includes: The system receives a terminal routing policy (URSP) sent by a first core network element. The URSP includes URSP rules, each URSP rule includes a routing descriptor (RSD), and the RSD includes altitude information. The altitude information is used to indicate that when the terminal's altitude matches the altitude information, the RSD should be selected to transmit application data. If the RSD also includes location information, the altitude information indicates that when the terminal's altitude matches the altitude information and the terminal's current location is within the location information, the RSD should be selected to transmit application data. The URSP is sent to the terminal.

11. A data transmission method, characterized by, The method is executed by a third network element, and the method includes: Transmit altitude information to the first core network element; The altitude information is used to generate a terminal routing policy (URSP). The URSP includes URSP rules, each URSP rule includes a routing descriptor (RSD), and the RSD includes the altitude information. The altitude information is used to indicate that when the terminal's altitude matches the altitude information, the RSD should be selected to transmit application data. If the RSD also includes location information, then the altitude information indicates that when the terminal's altitude matches the altitude information and the terminal's current location is within the location information, the RSD should be selected to transmit application data.

12. A data transmission method, characterized by, The method is executed by a terminal, and the method includes: The terminal routing policy URSP is received from the second core network element. The URSP includes URSP rules, and the URSP rules include routing descriptors RSD, which include height information. When the height of the terminal matches the height information, the RSD is selected to transmit application data; wherein, if the RSD also includes location information, the height information indicates that when the height of the terminal matches the height information and the current location of the terminal is within the location information, the RSD is selected to transmit application data.

13. A first core network element, comprising: A generation unit is configured to generate a terminal routing policy (URSP), wherein the URSP includes URSP rules, the URSP rules include 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; wherein, if the RSD also includes location information, the altitude information indicates that when the altitude of the terminal matches the altitude information and the current location of the terminal is within the location information, the RSD is selected to transmit application data. The sending unit is used to send the URSP to the terminal through the second core network element.

14. A second core network element, comprising: A receiving unit is configured to receive a terminal routing policy (URSP) sent by a first core network element. The URSP includes URSP rules, each URSP rule includes a routing descriptor (RSD), and the RSD includes altitude information. The altitude information is used to indicate that when the terminal's altitude matches the altitude information, the RSD should be selected to transmit application data. If the RSD also includes location information, the altitude information indicates that when the terminal's altitude matches the altitude information and the terminal's current location is within the location information, the RSD should be selected to transmit application data. A sending unit is used to send the URSP to the terminal.

15. A terminal, comprising: The receiving unit is configured to receive a terminal routing policy (URSP) from a second core network element. The URSP includes URSP rules, and the URSP rules include routing descriptors (RSDs), and the RSDs include height information. A transmission unit is configured to select the RSD to transmit application data when the height of the terminal matches the height information; wherein, if the RSD further includes location information, the height information indicates that the RSD is selected to transmit application data when the height of the terminal matches the height information and the current location of the terminal is within the location information.

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

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

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