Data transmission method and related device

Abstract

Provided in the embodiments of the present disclosure are a data transmission method and a related device. A method executed by a terminal comprises: receiving a terminal route selection strategy rule, the terminal route selection strategy rule comprising a backend terminal route selection strategy rule, the backend terminal route selection strategy rule comprising service description information and a route selection descriptor, the service description information being used for describing service information of a backend terminal, the backend terminal accessing a mobile network by means of the terminal, and the route selection descriptor being used for executing route selection described in the route selection descriptor for a service matched with the service description information in the backend terminal. Therefore, the network quality guarantee of a service flow of a backend terminal which accesses a mobile network by means of the present terminal can be better supported.

Description

Data transmission method and related equipment

[0001] Priority information

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on December 7, 2023, with application number 2023116840018 and application name “Data transmission method and related equipment”, all contents of which are incorporated by reference into this application. Technical Field

[0003] The present disclosure relates to the field of communication technology, and in particular to a data transmission method, a communication device, and a computer-readable storage medium. Background Art

[0004] A terminal (e.g., UE1 below) can share its hotspot to allow one or more backend terminals (e.g., backend UE (User Equipment) below) to access the mobile network through the terminal (e.g., UE1). However, backend terminals accessing through the hotspot can usually only use the default QoS (Quality of Service) flow of the default PDU (Protocol Data Unit) session of UE1 for data transmission, and the network quality of the backend terminals cannot be guaranteed.

[0005] Summary of the Invention

[0006] An embodiment of the present disclosure provides a data transmission method, which is executed by a terminal. The method includes: receiving a terminal routing policy rule, wherein the terminal routing policy rule includes a back-end terminal routing policy rule, and the back-end terminal routing policy rule includes service description information and a routing descriptor. The service description information is used to describe service information of the back-end terminal, and the back-end terminal accesses a mobile network through the terminal. The routing descriptor is used to execute the routing described in the routing descriptor for a service in the back-end terminal that matches the service description information.

[0007] In some exemplary embodiments of the present disclosure, the method further includes: when the back-end terminal accesses the mobile network through the terminal, matching the target back-end terminal routing policy rule from the back-end terminal routing policy rule for the service of the back-end terminal; when the target back-end terminal routing policy rule is matched to the service of the back-end terminal, executing the target routing descriptor in the target back-end terminal routing policy rule.

[0008] In some exemplary embodiments of the present disclosure, the back-end terminal routing policy rules also include rule priorities; wherein, matching the target back-end terminal routing policy rules from the back-end terminal routing policy rules for the services of the back-end terminal includes: matching the target back-end terminal routing policy rules from the back-end terminal routing policy rules in the order of the rule priorities in the back-end terminal routing policy rules.

[0009] In some exemplary embodiments of the present disclosure, when the service of the back-end terminal is matched to the target back-end terminal routing policy rule, the target routing descriptor in the target back-end terminal routing policy rule is executed, including: if the target back-end terminal routing policy rule also includes a target routing validity condition, then when the service of the back-end terminal meets the target routing validity condition, the target routing descriptor is executed.

[0010] In some exemplary embodiments of the present disclosure, when the target back-end terminal routing policy rule is matched for the service of the back-end terminal, the target routing descriptor in the target back-end terminal routing policy rule is executed, including: if the routing policy rule corresponding to the service of the back-end terminal already has a matching target protocol data unit session, then the service flow corresponding to the service of the back-end terminal is sent on the target protocol data unit session, or, an update process for the target protocol data unit session is initiated; if the routing policy rule corresponding to the service of the back-end terminal does not have a matching target protocol data unit session, then a process of creating a new target protocol data unit session is initiated.

[0011] In some exemplary embodiments of the present disclosure, the method further includes: reporting target back-end terminal routing policy rule reporting information that matches the back-end terminal service, the target back-end terminal routing policy rule reporting information includes the matched target back-end terminal routing policy rule, and the target back-end terminal routing policy rule reporting information reported by the terminal includes at least one of connection capability, rule identifier, and back-end device indication information.

[0012] An embodiment of the present disclosure provides a data transmission method, which is executed by a policy control function network element. The method includes: generating a terminal routing policy rule, the terminal routing policy rule including a back-end terminal routing policy rule, the back-end terminal routing policy rule including service description information and a routing descriptor, the service description information being used to describe service information of the back-end terminal, the back-end terminal accessing a mobile network through the terminal, the routing descriptor being used to execute the routing described in the routing descriptor for a service in the back-end terminal that matches the service description information; and transmitting the terminal routing policy rule to the terminal.

[0013] An embodiment of the present disclosure provides a terminal, including: a receiving unit, configured to receive terminal routing policy rules, wherein the terminal routing policy rules include back-end terminal routing policy rules, wherein the back-end terminal routing policy rules include service description information and a routing descriptor, wherein the service description information is used to describe service information of the back-end terminal, wherein the back-end terminal accesses a mobile network through the terminal, and the routing descriptor is used to execute routing described in the routing descriptor for a service in the back-end terminal that matches the service description information.

[0014] The present disclosure provides a policy control function network element, including:

[0015] a processing unit, configured to generate a terminal routing policy rule, the terminal routing policy rule including a backend terminal routing policy rule, the backend terminal routing policy rule including service description information and a routing descriptor, the service description information being used to describe service information of a backend terminal, the backend terminal accessing a mobile network via a terminal, the routing descriptor being used to execute routing described in the routing descriptor for a service matching the service description information in the backend terminal;

[0016] A sending unit is configured to transmit the terminal routing policy rule to the terminal.

[0017] An embodiment of the present disclosure provides a communication device, comprising: 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 described in the embodiment of the present disclosure.

[0018] An embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon. When the computer program is run on a computer, the computer implements the data transmission method described in the embodiment of the present disclosure.

[0019] The embodiments of the present disclosure provide a computer program product, including a computer program. When the computer program is executed by a computer, the data transmission method described in the embodiments of the present disclosure is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG1 is a schematic diagram of a communication system architecture provided by an embodiment of the present disclosure.

[0021] FIG2 is a system architecture diagram of a 5G network provided by an embodiment of the present disclosure.

[0022] FIG3 schematically shows a flow chart of a data transmission method according to an embodiment of the present disclosure.

[0023] FIG4 schematically shows an interaction diagram of a data transmission method according to an embodiment of the present disclosure.

[0024] FIG5 schematically shows an interactive diagram of a data transmission method according to another embodiment of the present disclosure.

[0025] FIG6 schematically shows a block diagram of a terminal according to an embodiment of the present disclosure.

[0026] FIG7 schematically shows a block diagram of a policy control function network element according to an embodiment of the present disclosure.

[0027] FIG8 schematically shows a schematic structural diagram of a communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0028] To make the objectives, technical solutions, and advantages of the present disclosure more apparent, exemplary embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. In the accompanying drawings, like reference numerals represent like elements throughout. It should be understood that the embodiments described herein are merely illustrative and should not be construed as limiting the scope of the present disclosure.

[0029] In the embodiments of the present disclosure, the term "module" or "unit" refers to a computer program or a part of a computer program that has a predetermined function and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0030] The technical solutions of the embodiments of the present 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), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5G system or future evolved mobile communication system, etc.

[0031] Exemplarily, a communication system 100 applied in an embodiment of the present disclosure is shown in FIG1 . The communication system 100 may include a network device 110, which may be a device that communicates with a terminal 120 (or referred to as a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminals located within the coverage area. Optionally, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, 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 may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

[0032] The communication system 100 also includes at least one terminal 120 located within the coverage area of ​​the network device 110. As used herein, "terminal" includes, but is not limited to, a connection via a wired line, such as a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or a wireless interface, such as a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and / or another terminal configured to receive / send communication signals; and / or an Internet of Things (IoT) device. 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 telephones; Personal Communications System (PCS) terminals that may combine cellular radiotelephones with data processing, fax, and data communications capabilities; Personal Digital Assistants (PDAs) that may include a radiotelephone, pager, Internet / Intranet access, a web browser, a notepad, a calendar, and / or a Global Positioning System (GPS) receiver; and conventional laptop and / or handheld receivers or other electronic devices that include a radiotelephone transceiver. A terminal may be referred to as an access terminal, user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a 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 PDA, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.

[0033] Optionally, the terminals 120 may perform device-to-device (D2D) communication with each other.

[0034] FIG1 exemplarily shows a network device and two terminals. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminals within its coverage area, which is not limited in the embodiments of the present disclosure.

[0035] Optionally, the communication system 100 may further include other network elements such as a policy control function network element, an access mobility management function network element, a session management function network element, and a user plane function network element, which is not limited in the embodiments of the present disclosure.

[0036] It should be understood that in the embodiments of the present disclosure, devices having communication functions in a network / system may be referred to as communication devices. Taking the communication system 100 shown in FIG1 as an example, the communication devices may include a network device 110 and a terminal 120 having communication functions. Network device 110 and terminal 120 may be the specific devices described above and will not be further described here.

[0037] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone.

[0038] Figure 2 is a system architecture diagram of a 5G network according to an embodiment of the present disclosure. As shown in Figure 2, 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) network element, data network (Data Network, DN), access and mobility management function (Access and Mobility Management Function, AMF) network element, session management function (Session Management Function, SMF) network element, policy control function (Policy Control Function, PCF) network element, application function (Application Function, AF) network element, authentication server function (Authentication Server Function, AUSF) network element, and unified data management (Unified Data Management, UDM) network element.

[0039] As shown in Figure 2, the policy-related network elements are mainly PCF, AMF, SMF, RAN, and UE. The SMF is primarily responsible for executing session-related policies, while the AMF is primarily responsible for executing access and UE-related policies. The PCF manages the issuance and update of policies for both network elements (AMF and SMF).

[0040] Specifically for 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 container is sent by the UE to the AMF through a NAS (non-access-stratum) message, and the AMF continues to transparently transmit (without perception or modification) to the PCF. In the downlink direction, the PCF sends the container to the AMF, and the AMF then transparently transmits it to the UE through a NAS message.

[0041] UE policy includes URSP (UE Route Selection Policy). URSP contains multiple policy rules (called URSP Rule or Terminal Route Selection Policy Rule). Each URSP Rule includes a traffic descriptor / service descriptor (Traffic Descriptor) and a set of route selection descriptors (RSD). The traffic descriptor in URSP is used to describe a specific service. A traffic descriptor can have one or more RSDs under it. Each RSD corresponds to the attributes of a PDU session. In other words, the service data corresponding to the traffic descriptor can run in the PDU session corresponding to the RSD.

[0042] The relevant contents of URSP in the related art are shown in Table 1 and Table 2 below:

[0043] Table 1: URSP Rules

[0044] In Table 1 above, Rule Precedence determines the order in which the UE applies URSP rules. A traffic descriptor is a traffic descriptor / service descriptor used to specify matching criteria. It describes service information that matches the URSP rule and consists of one or more components, optionally including application descriptors, IP descriptors (destination IP address), domain descriptors (destination FQDN), non-IP descriptors (descriptors for non-IP services), DNN (Data Network Name), and connection capabilities. The traffic descriptor is used by the UE for application matching. The target IP 3-tuple (IP address or IPv6 network prefix, port number, and protocol ID for protocols above IP) is used. Connection capabilities typically include "ims," ​​"mms," "internet," and so on. The URSP rule applies when any component in the traffic descriptor matches the corresponding information from the application. When the response information from the application does not match any value in the traffic descriptor component, this URSP rule does not apply.

[0045] Table 2: RSD

[0046] In Table 2 above, RSD priority (Route Selection Descriptor Precedence) determines the order in which RSDs are used. When an RSD with a higher priority is unavailable, other RSDs are used. Route selection components describe the various network resources that can be used by the application. It consists of one or more components, including SSC (service and session continuity) mode selection (SSC Mode Selection), network slice selection (Network Slice Selection), DNN selection (DNN Selection), PDU (Protocol Data Unit) session type selection (PDU Session Type Selection), non-seamless offload indication, ProSe Layer 3 UE to network relay offload indication, access type preference, PDU session pair ID, RSN, and route selection validation criteria parameters.

[0047] The routing validation criteria parameter, or routing verification criteria / routing validity condition, describes the corresponding validation conditions. This parameter is an optional parameter, which includes the time window (Time Window, also called the valid time window) and the location criteria (Location Criteria, also called location validity). Among them, the time window defines the time when the RSD is valid, which can also be understood as the time allowed by the service traffic. When the current time is not within the time window, the RSD is invalid. The location validity defines the UE position where the RSD is valid, which can also be understood as the UE position allowed by the service traffic. When the UE's current position is different from the position defined in the location validity, the RSD is invalid. That is, if the current time is not within the time window or the UE position does not match the location criteria, that is, if any of the routing validation criteria parameters is not met, the corresponding RSD is considered invalid.

[0048] Among them, SSC mode selection is used by the UE to select the corresponding SSC mode for the matching application, and DNN selection is used by the UE to select the corresponding DNN for the matching application. PDU session type selection is used by the UE to select the corresponding PDU session type for the matching application. Access type priority can also be called access type preference. If the UE needs to establish a PDU session for the matching application, it will indicate the preferred access type (3GPP or non-3GPP or Multi-Access).

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

[0050] In the related art, URSP rules are only formulated and issued for this terminal UE1, and are only stored and used in this terminal. As a result, the back-end terminal accessed through the hotspot can only use the default QoS flow of the default PDU session of UE1 for data transmission, and cannot configure specific routing strategies and QoS rules. That is, in the related art, this terminal UE1 cannot distinguish the data of the back-end terminal accessed through the UE1 hotspot, and map it to a specific QoS flow to ensure the network quality of the back-end terminal. The embodiment of the present disclosure enhances the URSP rules to achieve an enhancement of the routing strategy for the data of the back-end terminal accessing the mobile network through the hotspot of UE1, so as to achieve network quality assurance for the data transmission of the business data of the back-end terminal. The embodiment of the present disclosure does not limit the connection method between UE1 and the back-end terminal accessing the mobile network through UE1, and can adopt WIFI connection, Bluetooth connection, USB connection, or cellular connection methods such as 4G and 5G.

[0051] The method provided in the embodiment of Figure 3 may be executed by a terminal (eg, the aforementioned UE1). As shown in Figure 3, the method provided in the embodiment of the present disclosure may include the following steps.

[0052] In S310, a terminal routing policy rule is received, where the terminal routing policy rule includes a back-end terminal routing policy rule. The back-end terminal routing policy rule includes service description information and a routing descriptor. The service description information is used to describe the service information of the back-end terminal. The back-end terminal accesses the mobile network through the terminal. The routing descriptor is used to execute the routing described in the routing descriptor for the service matching the service description information in the back-end terminal.

[0053] Specifically, in this embodiment, a terminal refers to a terminal connected to a backend terminal and allowing the backend terminal to access a mobile network through the terminal, hereinafter referred to as UE1 or this terminal. A backend terminal refers to a terminal that accesses a mobile network through the terminal, such as UE1.

[0054] Optionally, in one embodiment, the terminal may receive the terminal routing policy rule sent by the PCF network element.

[0055] In an exemplary embodiment, the terminal routing policy rule includes a service descriptor, which includes a connection backend terminal descriptor as service description information for the connection backend terminal. The terminal routing policy rule including the connection backend terminal descriptor in the service descriptor is a backend terminal routing policy rule.

[0056] In an exemplary embodiment, the backend terminal routing policy rule further includes a rule priority.

[0057] In an exemplary embodiment, when the service descriptor includes both the connection backend terminal descriptor and other existing parameters, the other existing parameters are valid for the service of the terminal, and the connection backend terminal descriptor is only valid for the backend terminal service connected to the terminal.

[0058] In an exemplary embodiment, when the service descriptor includes both the connection backend terminal descriptor and other existing parameters, the parameters other than the connection backend terminal descriptor included in the service descriptor are invalid; or, the service descriptor does not include parameters other than the connection backend terminal descriptor.

[0059] In an exemplary embodiment, a terminal routing policy rule includes a rule priority, a service descriptor, and a connection backend terminal service descriptor, wherein the connection backend terminal service descriptor serves as service description information for the connection backend terminal. A terminal routing policy rule including the service descriptor and the connection backend terminal service descriptor is a backend terminal routing policy rule.

[0060] In an exemplary embodiment, the traffic descriptor is empty or invalid.

[0061] In an exemplary embodiment, the service descriptor is valid for the service of the terminal; and the service descriptor of the connected back-end terminal is valid for the back-end terminal connected through the terminal.

[0062] In an exemplary embodiment, the backend terminal routing policy rule is a terminal routing policy rule for the backend terminal (which may be referred to as a Tether-URSP rule). The backend terminal routing policy rule includes a service descriptor, which serves as service description information for connecting the backend terminal.

[0063] In some embodiments, the UE may receive a URSP rule. For example, the URSP rule received by the UE includes a service descriptor, and a connection backend terminal descriptor is added to the service descriptor. The connection backend terminal descriptor serves as the service description information for connecting to the backend terminal. In this case, the URSP rule may also be referred to as a backend terminal routing policy rule. For another example, the URSP rule received by the UE includes a connection backend terminal service descriptor in parallel with the service descriptor. The connection backend terminal service descriptor serves as the service description information for connecting to the backend terminal. In this case, the URSP rule may also be referred to as a backend terminal routing policy rule. In other embodiments, the UE may receive a Tether-URSP rule, that is, a URSP rule specifically for the backend terminal. The service descriptor contained in the Tether-URSP rule serves as the service description information for connecting to the backend terminal.

[0064] In an exemplary embodiment, the backend terminal routing policy rule further includes a rule priority, and the rule priority indicates the execution order of the backend terminal routing policy rule in the terminal.

[0065] In an exemplary embodiment, the service description information includes at least one of the following:

[0066] Device type, used to indicate the device type of the backend terminal;

[0067] Domain name descriptor;

[0068] Internet Protocol Descriptor;

[0069] Connectivity.

[0070] In some embodiments, when a backend terminal connection descriptor serves as service description information, the backend terminal connection descriptor is included in the service descriptor, and the backend terminal connection descriptor includes at least one of the following: device type; domain name descriptor; internet protocol descriptor; and connection capabilities. In other embodiments, when a URSP rule includes a service descriptor and a backend terminal connection service descriptor in parallel, and the backend terminal connection service descriptor serves as service description information for connecting to the backend terminal, the backend terminal connection service descriptor includes at least one of the following: device type; domain name descriptor; internet protocol descriptor; and connection capabilities. In still other embodiments, when a backend terminal routing policy rule is a terminal routing policy rule for the backend terminal, and the backend terminal routing policy rule includes a service descriptor, when the service descriptor serves as the service description information, the service descriptor includes at least one of the following: device type; domain name descriptor; internet protocol descriptor; and connection capabilities.

[0071] In an exemplary embodiment, the backend terminal routing policy rule further includes a routing validity condition, where the routing validity condition is used to indicate that the routing descriptor is valid when the backend terminal satisfies the routing validity condition.

[0072] In an exemplary embodiment, the method provided by the embodiment of the present disclosure may further include: reporting target backend terminal routing policy rule reporting information that matches the backend terminal service, wherein the target backend terminal routing policy rule reporting information includes the matched target backend terminal routing policy rule. The target backend terminal routing policy rule reporting information reported by the terminal includes at least one of the following:

[0073] Connectivity

[0074] Rule identification;

[0075] Backend device indication information.

[0076] In an embodiment of the present disclosure, the back-end device indication information may be a unique identifier of the back-end terminal, for example, it may be a hardware identifier and / or a SIM card (Subscriber Identity Module, smart card / user identity card) identifier of the back-end terminal, and the present disclosure does not limit this. When the back-end terminal is a terminal with a single service (such as an Internet of Things terminal), the back-end device indication information can not only uniquely identify the back-end terminal, but also determine the type of service or connection capability initiated by the back-end terminal. If multiple services are running on the back-end terminal (such as a mobile phone), the service initiated by the back-end terminal can be determined by the connection capability and / or rule identifier.

[0077] In an exemplary embodiment, the method of this embodiment may further include: when the back-end terminal accesses the mobile network through the terminal, matching the target back-end terminal routing policy rule from the back-end terminal routing policy rule for the back-end terminal's service; when the target back-end terminal routing policy rule is matched to the back-end terminal's service, executing the target routing descriptor in the target back-end terminal routing policy rule.

[0078] In an exemplary embodiment, the back-end terminal routing policy rules may further include rule priorities; wherein, the target back-end terminal routing policy rules are matched from the back-end terminal routing policy rules for the back-end terminal services, specifically, it may be: matching the target back-end terminal routing policy rules from the back-end terminal routing policy rules in the order of the rule priorities in the back-end terminal routing policy rules.

[0079] In an exemplary embodiment, when the target back-end terminal routing policy rule is matched for the service of the back-end terminal, the target routing descriptor in the target back-end terminal routing policy rule is executed. Specifically, if the target back-end terminal routing policy rule also includes a target routing validity condition, then when the service of the back-end terminal meets the target routing validity condition, the target routing descriptor is executed.

[0080] In an exemplary embodiment, when the target back-end terminal routing policy rule is matched for the service of the back-end terminal, the target routing descriptor in the target back-end terminal routing policy rule is executed. Specifically, if the routing policy rule corresponding to the service of the back-end terminal already has a target protocol data unit session that can be matched, then the service flow corresponding to the service of the back-end terminal is sent on the target protocol data unit session, or an update process of the target protocol data unit session is initiated; if the routing policy rule corresponding to the service of the back-end terminal does not have a target protocol data unit session that can be matched, then a process of creating a new target protocol data unit session is initiated.

[0081] In an exemplary embodiment, the method of this embodiment may further include: reporting target backend terminal routing policy rule reporting information that matches the backend terminal service, the target backend terminal routing policy rule reporting information including at least one of connection capability, rule identifier, and backend device indication information.

[0082] In an exemplary embodiment, the method of this embodiment may further include: reporting capability information of the terminal, where the capability information indicates whether the terminal supports executing a backend terminal routing policy rule for the backend terminal.

[0083] The data transmission method provided by the embodiment of the present disclosure enhances the URSP rules and generates back-end terminal URSP rules for the back-end terminal that accesses the mobile network through this terminal, thereby enabling the service flow of the back-end terminal that accesses the mobile network through this terminal to select a PDU session (optionally, QoS flow binding can be performed), thereby better supporting network quality assurance of the service flow of the back-end terminal that accesses the mobile network through this terminal.

[0084] FIG4 schematically shows an interactive diagram of a data transmission method according to an embodiment of the present disclosure. As shown in FIG4 , the method provided by the embodiment of the present disclosure may include:

[0085] Optionally, in S41 , UE1 reports capability information to PCF.

[0086] For example, UE1 can report capability information to PCF through the base station, AMF and SMF in sequence.

[0087] For any of the multiple implementation methods of the backend terminal URSP rules provided in the embodiment of Figure 5 below, if UE1 supports executing specific URSP rules for the connected backend device (i.e., the target backend terminal URSP rules), UE1 can report the capability information of UE1 in the registration process, mobility management process, or terminal capability reporting process, indicating that UE1 supports executing URSP rules for the backend device (i.e., the backend terminal URSP rules).

[0088] In S42, the PCF generates a URSP.

[0089] Optionally, after receiving the reported capability information, the PCF generates a URSP rule for the backend terminal (referred to as a backend terminal URSP rule) based on the reported capability information. The PCF may determine whether the UE1 supports the URSP rule for the backend terminal based on the capability information reported by the received UE1. If the UE1 supports it, the URSP rule for the backend terminal is generated; if the UE1 does not support it, the URSP rule for the backend terminal is not generated.

[0090] It should be noted that the above S41 is optional, that is, the PCF may also directly generate the URSP for the backend terminal.

[0091] In S43 , the PCF sends the generated URSP for the backend terminal to UE1 .

[0092] Optionally, the PCF sends the generated URSP to the AMF. The PCF may send the generated URSP for the backend terminal to the AMF. After receiving the URSP, the AMF sends the URSP to UE1 via the base station / RAN. In the embodiment of the present disclosure, the AMF may use a NAS message to directly forward the URSP for the backend terminal to UE1, but the present disclosure is not limited to this.

[0093] Optionally, the PCF sends the generated URSP to the SMF, the SMF sends the URSP to the AMF, the AMF sends the URSP to the base station, and the base station sends the URSP to UE1.

[0094] In S44, UE1 matches the URSP rule for the backend UE.

[0095] Based on the received URSP for the backend terminal, UE1 associates the backend UE's application data with the corresponding PDU session for transmission according to the URSP for the backend terminal. The mechanism is as follows: When the backend UE's application layer sends data, UE1 receives the UE's data. Since the data source is the connected backend terminal, UE1 uses the backend terminal URSP rules in the URSP to check whether the characteristics of the backend UE's application data match the service description information of a rule in the backend terminal URSP rules. The order of checking is determined by the rule priority (Precedence) in the backend terminal URSP rules. That is, UE1 checks the matching results in order of rule priority. When the service description information of a backend terminal URSP rule is matched, the RSD list under the backend terminal URSP rule is used to bind the PDU session. When a backend terminal URSP rule is matched, UE1 searches for a suitable PDU session according to the priority (Precedence) in the RSD. Here, the RSD with the highest priority is given priority. If a parameter in the RSD has one or more values, UE1 uses a combination of parameters to check whether the PDU session exists:

[0096] 1) If it exists, the application data of the backend UE is bound to the session for transmission;

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

[0098] 2.1) If the session is successfully established, UE1 binds the application data of the backend UE to the session for transmission;

[0099] 2.2) If the session establishment fails, UE1 searches again for the existence of a PDU session based on other parameter combinations in the RSD or a parameter combination in an RSD with lower priority (loop step 1);

[0100] If a suitable PDU session cannot be found for binding according to the matching backend terminal URSP rule, UE1 searches the priority order to see whether the service description information in the second-priority backend terminal URSP rule can match the application data flow characteristics of the backend UE. When a match is found, the previously described process is repeated.

[0101] Optionally, in S45, UE1 reports the URSP rule information matched for the backend UE (ie, the target backend terminal URSP rule information) to PCF through the base station, AMF, and SMF in sequence.

[0102] For any of the multiple implementations of the backend terminal URSP rule provided in the embodiment of FIG. 5 below, if UE1 matches a specific backend terminal URSP rule (i.e., a target backend terminal URSP rule) for the connected backend device, the matched backend terminal URSP rule may be reported to the network. The reported information may include one or more of: connection capability, rule identifier (i.e., identifier of the target backend terminal URSP rule), backend device indication information, etc. A network element in the network, such as a PCF, may determine that a backend terminal / backend device is currently connected based on the reported target backend terminal URSP rule information, and may then issue a specific QoS policy (i.e., a target QoS policy) for the PDU session (referred to as the target PDU session for distinction) based on the policy. This may include QoS rules, QoS profile information, etc.

[0103] In S46 , the PCF determines a QoS policy for the PDU session of the backend UE.

[0104] In S47a, the PCF sends QoS rules to the backend UE through the SMF, AMF and base station in sequence.

[0105] In S47b, the PCF sends the QoS profile information to the base station through the SMF and AMF in sequence.

[0106] The data transmission method provided in the embodiment of FIG5 can be executed by a PCF network element, but the present disclosure is not limited thereto. As shown in FIG5 , the method provided in the embodiment of the present disclosure may include:

[0107] In S510, a terminal routing policy rule is generated, which includes a back-end terminal routing policy rule. The back-end terminal routing policy rule includes service description information and a routing descriptor. The service description information is used to describe the service information of the back-end terminal. The back-end terminal accesses the mobile network through the terminal. The routing descriptor is used to execute the routing described in the routing descriptor for the service matching the service description information in the back-end terminal.

[0108] In the embodiments of the present disclosure, a terminal refers to a terminal that is connected to a backend terminal and allows the backend terminal to access a mobile network through the terminal, and is hereinafter referred to as UE1 or this terminal. For example, UE1 can allow the backend terminal to access the mobile network by sharing its own hotspot, but the present disclosure is not limited to this. The backend terminal refers to a terminal that accesses the mobile network through the terminal, such as UE1. The embodiments of the present disclosure do not limit the backend terminal and the type of terminal. For example, it can be any one or more of a laptop computer, a tablet computer, a mobile phone, a drone, a robot, an IoT device, etc.

[0109] The terminal routing policy (URSP) may include one or more (two or more) URSP rules, each of which may include one or more routing descriptors (RSDs). The URSP can be used to enable a UE (e.g., UE1 and / or backend UE) to map specific service flows to corresponding data transmission sessions. For example, the PCF may generate multiple URSP rules in the core network. For UE1, each URSP rule may include a traffic descriptor (Traffic Descriptor) and a routing descriptor (RSD). When an application on UE1 is launched, the corresponding URSP can be determined by matching the traffic characteristics of the application launched by UE1 with the Traffic Descriptor in the URSP rule generated by the core network. Each URSP rule may include one or more RSDs, and RSD priorities can be configured for different RSDs in each URSP rule based on service requirements and service types. After matching the corresponding URSP, UE1 selects the corresponding RSD based on the RSD priorities of the generated RSDs and transmits the application's data (referred to as service data or application data) on the data transmission session corresponding to the RSD.

[0110] In the embodiment of the present disclosure, the URSP rule includes the back-end terminal URSP rule, and the back-end terminal URSP rule refers to the URSP rule set for the back-end terminal, or the service description information for the back-end terminal is added to the URSP rule set for the current terminal, so that the current terminal can match the corresponding URSP rule for its back-end terminal.

[0111] In an exemplary embodiment, the backend terminal routing policy rule includes a service descriptor, and the service descriptor includes a connection backend terminal descriptor, and the connection backend terminal descriptor serves as service description information of the connection backend terminal.

[0112] In an exemplary embodiment, the backend terminal routing policy rule may further include a rule priority.

[0113] In some embodiments, when a service descriptor includes both a connection backend terminal descriptor and other existing parameters, the other existing parameters are valid for the service of the current terminal, and the connection backend terminal descriptor is only valid for the service of the current terminal connected to the current terminal. In other embodiments, when a service descriptor includes both a connection backend terminal descriptor and other existing parameters, the parameters included in the service descriptor other than the connection backend terminal descriptor are invalid; or, the service descriptor does not include parameters other than the connection backend terminal descriptor.

[0114] In an exemplary embodiment, the service description information includes at least the following:

[0115] Device type, used to indicate the device type of the backend terminal;

[0116] Domain name descriptor;

[0117] Internet Protocol (IP) descriptor;

[0118] Connectivity.

[0119] In some embodiments, the following fields are added to the traffic descriptor of the URSP rule:

[0120] The backend terminal connection descriptor includes service description information for the backend terminal connected to the UE1 (the URSP rule with the backend terminal connection descriptor added is referred to as the backend terminal URSP rule).

[0121] Exemplarily, the connection backend terminal descriptor may further include the following information:

[0122] Device type: refers to the device type of the backend terminal, such as drones, smart watches, XR (Extended Reality) devices, etc.

[0123] Domain descriptors: FQDN(s) or regular expressions used as domain name matching criteria.

[0124] IP descriptors: Target IP 3-tuple (IP address or IPv6 network prefix, port number, protocol ID for protocols above IP).

[0125] Connection Capabilities: This matches the information provided by the back-end terminal application when requesting a network connection with specific capabilities or service classes. Connection capabilities can typically be: "ims", "mms", "internet", etc.

[0126] In an exemplary embodiment, when a service descriptor includes both a connection backend terminal descriptor and other existing parameters, the other existing parameters are valid for the service of the terminal, and the connection backend terminal descriptor is only valid for the service of the backend terminal connected to the terminal. In other embodiments, when a service descriptor includes both a connection backend terminal descriptor and other existing parameters, the other parameters are invalid. That is, when a service descriptor includes a "connection backend terminal descriptor," only the parameters in the "connection backend terminal descriptor" are valid; or the service descriptor does not need to include other parameters.

[0127] When UE1 receives a URSP rule containing a "connection backend terminal descriptor", it can match the service flow for the service of the backend terminal connected through the hotspot, and the matching order can be the priority of these URSP rules containing the "connection backend terminal descriptor". When the UE matches a specific URSP rule for the service of the backend terminal connected through the hotspot (the specific URSP rule is called the target backend terminal URSP rule), the RSD in the specific URSP rule will be executed (the RSD executed in the specific URSP rule is called the target RSD). Furthermore, if the specific URSP rule contains a "routing validity condition", the target RSD will be executed only when the routing validity condition is met.

[0128] Exemplarily, the method for executing the target RSD is: if the matching URSP rule has established a PDU session (for distinction, referred to as the target PDU session), then the business flow of the back-end terminal is sent on the PDU session, or an update process of the PDU session is initiated; if the matching URSP rule has not established a PDU session, then a new PDU session process is initiated.

[0129] In an exemplary embodiment, the backend terminal routing policy rule includes a rule priority, a service descriptor, and a connected backend terminal service descriptor, where the connected backend terminal service descriptor serves as service description information of the connected backend terminal.

[0130] In other embodiments, a "connection back-end terminal service descriptor" is added to the URSP rule. That is, the "connection back-end terminal service descriptor" is listed alongside the "service descriptor." When the URSP rule includes the "connection back-end terminal service descriptor," the "service descriptor" becomes invalid and may be empty, or even if it contains content, the service descriptor is invalid. In this case, the URSP rule with the added connection back-end terminal service descriptor is referred to as the back-end terminal URSP rule.

[0131] In other embodiments, a "connection back-end terminal service descriptor" is added to the URSP rule, that is, the "connection back-end terminal service descriptor" is listed in parallel with the "service descriptor". When the URSP rule contains the "connection back-end terminal service descriptor", the "service descriptor" content can be empty. At this time, the URSP rule is only valid for the back-end terminal; when the URSP rule contains both the "connection back-end terminal service descriptor" content and the "service descriptor" content, the URSP rule is valid for both the current terminal service and the back-end terminal service.

[0132] When UE1 receives a URSP rule containing a "connection backend terminal service descriptor", it will match the service flow for the service of the backend terminal connected through the hotspot. The matching order is the priority of these URSP rules containing the "connection backend terminal service descriptor". When the UE matches a specific URSP rule (called the target backend terminal URSP rule) for the service of the backend terminal connected through the hotspot, the RSD (target RSD) in the specific URSP rule can be executed. Furthermore, if the specific URSP rule contains a "routing validity condition", the target RSD will only be executed when the routing validity condition is met.

[0133] Exemplarily, the method for executing the target RSD is: if the matching URSP rule has established a PDU session (for distinction, referred to as the target PDU session), then the business flow of the back-end terminal is sent on the PDU session, or an update process for the PDU session is initiated; if the matching URSP rule has not established a PDU session, then a new PDU session process is initiated.

[0134] In an exemplary embodiment, the backend terminal routing policy rule is a terminal routing policy rule for a backend terminal. The backend terminal routing policy rule includes a service descriptor, and the service descriptor serves as service description information for connecting to the backend terminal.

[0135] In an exemplary embodiment, the backend terminal routing policy rule further includes a rule priority, and the rule priority indicates the execution order of the backend terminal routing policy rule in the terminal.

[0136] In some further embodiments, a new URSP rule is defined for the backend terminal (also referred to as Tether-UE) connected to the UE1. That is, the PCF may generate a URSP rule for the backend terminal (the URSP rule may be referred to as the backend terminal URSP rule). For example, the rule may be defined as Tether-URSP. The Tether-URSP rule may include the following content:

[0137] Rule priority: used to indicate the execution order of the Tether-URSP rules in UE1.

[0138] Traffic descriptor: describes the traffic information of the backend terminal that complies with the Tether-URSP rules. It may further include the following:

[0139] Device type: refers to the device type of the backend terminal, such as drones, smart watches, XR devices, etc.

[0140] Domain descriptors: FQDN(s) or regular expressions used as domain name matching criteria.

[0141] IP descriptors: Target IP 3-tuple (IP address or IPv6 network prefix, port number, protocol ID for protocols above IP).

[0142] Connection Capabilities: This matches the information provided by the back-end terminal application when requesting a network connection with specific capabilities or service classes. Connection capabilities can typically be: "ims", "mms", "internet", etc.

[0143] Route selection descriptors (RSD): Execute the routing described in the RSD for the services matching the above traffic descriptors in the backend terminal. RSD may further include the following content:

[0144] Business Continuity Mode Selection (SSC Mode Selection);

[0145] Network Slice Selection: A list of one or a group of S-NSSAI(s);

[0146] DNN Selection: A list of one or a set of DNN(s) values;

[0147] PDU Session Type Selection: PDU session type, etc.

[0148] Routing validity conditions, which may include at least one of the following:

[0149] Time window: defines the time allowed for traffic. When the time is not within the time window, the RSD is invalid.

[0150] Location Criteria: defines the UE location allowed for traffic. If the UE's current location is different from the location defined in the location criteria, the RSD is invalid.

[0151] When UE1 receives the Tether-URSP rule, it can match the service flow for the service of the back-end terminal connected through the hotspot. The matching order is the priority of these Tether-URSP rules. When UE1 matches a specific Tether-URSP rule for the service of the back-end terminal connected through the hotspot (the matched specific Tether-URSP rule is called the target back-end terminal URSP rule), it can execute the RSD in the specific Tether-URSP rule (the executed RSD is called the target RSD). If the specific Tether-URSP rule contains a "routing validity condition", the target RSD will be executed only when the routing validity condition is met.

[0152] The method for executing the target RSD is: if the matching Tether-URSP rule has established a PDU session (target PDU session), then the service flow of the back-end terminal is sent on the PDU session, or an update process for the PDU session is initiated; if the matching Tether-URSP rule has not established a PDU session, then a new PDU session process is initiated.

[0153] In S520, the terminal routing policy rule is transmitted to the terminal.

[0154] In some embodiments, the PCF may send the generated URSP rules to the terminal UE1 through the AMF, but the present disclosure is not limited to this. In other embodiments, the URSP rules formulated by the PCF may be sent to the UE1 through the SMF, AMF and base station in sequence. The back-end terminal URSP rules (i.e., Tether-URSP rules) in the URSP rules are mainly used to determine which Tether-URSP rule matches the business flow when the back-end terminal initiates a new business flow. If the matching Tether-URSP rule already has a matching PDU session, the business flow is sent on the PDU session, or an update process for the PDU session is initiated; if the matching Tether-URSP rule does not have a matching PDU session, a new PDU session process is initiated.

[0155] URSP has multiple URSP rules, including backend terminal URSP rules (i.e., Tether-URSP rules). One or more applications can be installed on the backend terminal. When an application on the backend terminal is started, UE1 can match the service description information in the backend terminal URSP rules based on the traffic characteristics of the application started by the backend terminal, and route the data of the started application according to the RSD of the corresponding service description information.

[0156] Backend terminal URSP rules can include one or more RSDs, each of which can be used to indicate a corresponding PDU session. For example, an RSD can include parameters for establishing a PDU session, such as the DNN, network slice selection policy, S-NSSAI, and PDU session type. PDU sessions corresponding to different RSDs may provide different Internet experiences.

[0157] The data transmission method provided by the embodiment of the present disclosure enhances the URSP rules when the PCF generates a URSP for the terminal, and generates a back-end terminal URSP rule for the back-end terminal that accesses the mobile network through the terminal, thereby enabling the service flow of the back-end terminal that accesses the mobile network through the terminal to select a PDU session (optionally, QoS flow binding can be performed), thereby better supporting network quality assurance of the service flow of the back-end terminal that accesses the mobile network through the terminal.

[0158] For other contents of the embodiment of FIG. 5 , reference may be made to the above-mentioned embodiment.

[0159] FIG6 schematically shows a block diagram of a terminal according to an embodiment of the present disclosure. The terminal 600 provided in the embodiment of FIG6 may include a receiving unit 610 .

[0160] The receiving unit 610 is used to receive terminal routing policy rules, which include back-end terminal routing policy rules. The back-end terminal routing policy rules include service description information and routing descriptors. The service description information is used to describe the service information of the back-end terminal. The back-end terminal accesses the mobile network through the terminal. The routing descriptor is used to execute the routing described in the routing descriptor for the service that matches the service description information in the back-end terminal.

[0161] In an exemplary embodiment, the terminal 600 also includes a processing unit for matching a target backend terminal routing policy rule from the backend terminal routing policy rule for the backend terminal's service when the backend terminal accesses a mobile network through the terminal; and executing a target routing descriptor in the target backend terminal routing policy rule when the target backend terminal routing policy rule is matched for the backend terminal's service.

[0162] In some exemplary embodiments of the present disclosure, the backend terminal routing policy rule further includes a rule priority, wherein the processing unit is further configured to match the target backend terminal routing policy rule from the backend terminal routing policy rules according to the order of the rule priorities in the backend terminal routing policy rule.

[0163] In some exemplary embodiments of the present disclosure, the processing unit is further configured to: if the target backend terminal routing policy rule also includes a target routing validity condition, then when the backend terminal service meets the target routing validity condition, execute the target routing descriptor.

[0164] In some exemplary embodiments of the present disclosure, the processing unit is further used to: if the routing selection policy rule corresponding to the service of the back-end terminal already has a matching target protocol data unit session, then send the service flow corresponding to the service of the back-end terminal on the target protocol data unit session, or initiate an update process for the target protocol data unit session; if the routing selection policy rule corresponding to the service of the back-end terminal does not have a matching target protocol data unit session, then initiate a process for creating a new target protocol data unit session.

[0165] In some exemplary embodiments of the present disclosure, the terminal 600 also includes a sending unit for reporting target back-end terminal routing policy rule reporting information that matches the back-end terminal service, the target back-end terminal routing policy rule reporting information includes target back-end terminal routing policy rules, and the target back-end terminal routing policy rule reporting information includes at least one of connection capability, rule identifier, and back-end device indication information.

[0166] In some exemplary embodiments of the present disclosure, the terminal 600 further includes a sending unit, configured to report capability information of the terminal, where the capability information indicates whether the terminal supports executing a backend terminal routing policy rule for a backend terminal.

[0167] For other contents of the terminal provided in the embodiment of FIG. 6 , reference may be made to the other embodiments described above.

[0168] FIG7 schematically shows a block diagram of a policy control function network element according to an embodiment of the present disclosure. The policy control function network element 700 provided in the embodiment of FIG7 may include a processing unit 710 and a sending unit 720 .

[0169] Processing unit 710 is configured to generate terminal routing policy rules, including backend terminal routing policy rules. The backend terminal routing policy rules include service description information and routing descriptors. The service description information is used to describe service information of the backend terminal, through which the backend terminal accesses the mobile network. The routing descriptor is used to execute the routing described in the routing descriptor for services matching the service description information in the backend terminal. Transmitting unit 720 is configured to transmit the terminal routing policy rules to the terminal.

[0170] In an exemplary embodiment, the terminal routing policy rule includes a service descriptor, which includes a connection backend terminal descriptor as service description information for the connection backend terminal. The terminal routing policy rule including the connection backend terminal descriptor in the service descriptor is a backend terminal routing policy rule.

[0171] In an exemplary embodiment, the backend terminal routing policy rule further includes a rule priority.

[0172] In an exemplary embodiment, a backend terminal routing policy rule includes a rule priority, a service descriptor, and a connected backend terminal service descriptor, wherein the connected backend terminal service descriptor serves as service description information for the connected backend terminal. A terminal routing policy rule including the service descriptor and the connected backend terminal service descriptor is a backend terminal routing policy rule.

[0173] In an exemplary embodiment, the backend terminal routing policy rule is a terminal routing policy rule for a backend terminal. The backend terminal routing policy rule includes a service descriptor, and the service descriptor serves as service description information for connecting to the backend terminal.

[0174] In an exemplary embodiment, the backend terminal routing policy rule further includes a rule priority, and the rule priority indicates the execution order of the backend terminal routing policy rule in the terminal.

[0175] In an exemplary embodiment, the service description information includes at least the following:

[0176] Device type, used to indicate the device type of the backend terminal;

[0177] Domain name descriptor;

[0178] Internet Protocol Descriptor;

[0179] Connectivity.

[0180] In an exemplary embodiment, the backend terminal routing policy rule further includes a routing validity condition, where the routing validity condition is used to indicate that the routing descriptor is valid when the backend terminal satisfies the routing validity condition.

[0181] In an exemplary embodiment, the policy control function network element 700 also includes a receiving unit for receiving target back-end terminal routing policy rule reporting information reported by the terminal that matches the back-end terminal service. The target back-end terminal routing policy rule reporting information includes the target back-end terminal routing policy rule. The target back-end terminal routing policy rule reporting information includes at least one of the following: connection capability; rule identification; back-end device indication information.

[0182] In an exemplary embodiment, the processing unit 710 is further configured to deliver a target quality of service policy for a target protocol data unit session according to the target backend terminal routing policy rule reporting information.

[0183] In an exemplary embodiment, the policy control function network element 700 further includes a receiving unit configured to receive capability information reported by a terminal. The processing unit 710 is further configured to generate a terminal routing policy including the backend terminal routing policy rule if the capability information indicates that the terminal supports executing the backend terminal routing policy rule for the backend terminal.

[0184] For other contents of the policy control function network element provided in the embodiment of FIG. 7 , reference may be made to the other embodiments described above.

[0185] FIG8 schematically illustrates a schematic structural diagram of a communication device 800 according to an embodiment of the present disclosure. The communication device may be a terminal such as a UE, or a network device such as a base station, or a PCF network element and / or a NEF network element and / or an AF network element and / or an SMF network element and / or a UPF network element. The communication device 800 shown in FIG8 includes a processor 810, which may call and execute a computer program from a memory to implement the method in the embodiment of the present disclosure.

[0186] Optionally, as shown in FIG8 , the communication device 800 may further include a memory 820. The processor 810 may call and execute a computer program from the memory 820 to implement the method in the embodiment of the present disclosure.

[0187] The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .

[0188] Optionally, as shown in FIG8 , the communication device 800 may further include a transceiver 830 , and the processor 810 may control the transceiver 830 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0189] The transceiver 830 may include a transmitter (which may be used as the transmitting unit in the above embodiment) and a receiver (which may be used as the receiving unit in the above embodiment). The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

[0190] Optionally, the communication device 800 may specifically be various network elements of the embodiments of the present disclosure, and the communication device 800 may implement the corresponding processes implemented by each network element in each method of the embodiments of the present disclosure. For the sake of brevity, they will not be repeated here.

[0191] Optionally, the communication device 800 may specifically be a mobile terminal / terminal of an embodiment of the present disclosure, and the communication device 800 may implement the corresponding processes implemented by the mobile terminal / terminal in each method of the embodiment of the present disclosure. For the sake of brevity, they will not be repeated here.

[0192] Optionally, the processor 810 , the memory 820 , and the transceiver 830 may implement bidirectional communication with each other via the communication bus 840 .

[0193] It should be understood that the processor of the embodiment of the present disclosure may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment may be completed by hardware integrated logic circuits in the processor or software instructions.

[0194] The above-mentioned 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 device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present disclosure can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in conjunction with the embodiments of the present disclosure can be directly embodied as being executed by a hardware decoding processor, or can be executed 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 art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above-mentioned method in combination with its hardware.

[0195] It is understood that the memory in the embodiments of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of 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-mentioned memory is by way of example and not limitation.

[0196] The embodiment of the present disclosure also provides a computer-readable storage medium for storing a computer program.

[0197] Optionally, the computer-readable storage medium can be applied to each network element in the embodiments of the present disclosure, and the computer program enables the computer to execute the corresponding processes implemented by each network element in each method of the embodiments of the present disclosure. For the sake of brevity, they will not be repeated here.

[0198] Optionally, 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. For the sake of brevity, they are not repeated here.

[0199] An embodiment of the present disclosure also provides a computer program product, including computer program instructions.

[0200] Optionally, the computer program product can be applied to each network element in the embodiments of the present disclosure, and the computer program instructions enable the computer to execute the corresponding processes implemented by each network element in each method of the embodiments of the present disclosure. For the sake of brevity, they will not be repeated here.

[0201] Optionally, the computer program product can be applied to the mobile terminal / terminal in the embodiments of the present disclosure, and the computer program instructions enable 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, they are not repeated here.

[0202] The embodiments of the present disclosure also provide a computer program.

[0203] Optionally, the computer program can be applied to each network element in the embodiments of the present disclosure. When the computer program runs on a computer, the computer executes the corresponding processes implemented by each network element in the various methods of the embodiments of the present disclosure. For the sake of brevity, they will not be repeated here.

[0204] Optionally, the computer program can be applied to the mobile terminal / terminal in the embodiments of the present disclosure. When the computer program runs on the computer, the computer executes 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, they are not repeated here.

[0205] Those skilled in the art will appreciate that the units and algorithm steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians 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.

[0206] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0207] In the several embodiments provided in this disclosure, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units described is merely a logical functional division. In actual implementation, other division methods may be used, such as combining or integrating multiple units or components into another system, or omitting or not implementing certain features.

[0208] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0209] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0210] If the functions are implemented in the form of 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 the present disclosure, 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. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0211] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A data transmission method, characterized in that: The method is executed by a terminal, and includes: A terminal routing policy rule is received, wherein the terminal routing policy rule includes a back-end terminal routing policy rule, wherein the back-end terminal routing policy rule includes service description information and a routing descriptor, wherein the service description information is used to describe service information of the back-end terminal, and the back-end terminal accesses a mobile network through the terminal, and the routing descriptor is used to execute the routing described in the routing descriptor for the service matching the service description information in the back-end terminal.

2. The method according to claim 1, characterized in that The terminal routing policy rule includes a service descriptor, and the service descriptor includes a connection back-end terminal descriptor. The connection back-end terminal descriptor serves as service description information for connecting the back-end terminal. The terminal routing policy rule that includes the connection back-end terminal descriptor in the service descriptor is the back-end terminal routing policy rule.

3. The method according to claim 1 or 2, characterized in that: The back-end terminal routing selection policy rule also includes a rule priority.

4. The method according to claim 1, characterized in that: The terminal routing selection policy rule includes a rule priority, a service descriptor and a connection back-end terminal service descriptor. The connection back-end terminal service descriptor serves as service description information for connecting the back-end terminal. The terminal routing selection policy rule including the service descriptor and the connection back-end terminal service descriptor is the back-end terminal routing selection policy rule.

5. The method according to claim 1, characterized in that: The back-end terminal routing policy rule is a terminal routing policy rule for the back-end terminal. The back-end terminal routing policy rule includes a service descriptor, and the service descriptor is service description information for connecting the back-end terminal.

6. The method according to claim 5, characterized in that The back-end terminal routing selection policy rule further includes a rule priority, and the rule priority indicates the execution order of the back-end terminal routing selection policy rule in the terminal.

7. The method according to any one of claims 1 to 6, characterized in that The service description information includes at least one of the following: Device type, used to indicate the device type of the backend terminal; Domain name descriptor; Internet protocol descriptor; Connectivity.

8. The method according to any one of claims 1 to 7, characterized in that The back-end terminal routing policy rule further includes a routing validity condition, and the routing validity condition is used to indicate that when the back-end terminal satisfies the routing validity condition, the routing descriptor is valid.

9. The method according to any one of claims 1 to 8, characterized in that Also includes: Reporting target back-end terminal routing policy rule reporting information that matches the back-end terminal service, wherein the target back-end terminal routing policy rule reporting information includes the matched target back-end terminal routing policy rule, and the target back-end terminal routing policy rule reporting information reported by the terminal includes at least one of the following: Connectivity Rule identification; Backend device indication information.

10. The method according to any one of claims 1 to 8, characterized in that Also includes: Reporting capability information of the terminal, wherein the capability information indicates whether the terminal supports executing a backend terminal routing policy rule for the backend terminal.

11. A data transmission method, characterized in that: The method is performed by a policy control function network element, and the method includes: Generate a terminal routing policy rule, wherein the terminal routing policy rule includes a back-end terminal routing policy rule, wherein the back-end terminal routing policy rule includes service description information and a routing descriptor, wherein the service description information is used to describe service information of a back-end terminal, wherein the back-end terminal accesses a mobile network through a terminal, and the routing descriptor is used to perform routing described in the routing descriptor on a service matching the service description information in the back-end terminal; The terminal routing policy rule is transmitted to the terminal.

12. The method according to claim 11, characterized in that Also includes: receiving target backend terminal routing policy rule reporting information matching the backend terminal service reported by the terminal, wherein the target backend terminal routing policy rule reporting information includes the matched target backend terminal routing policy rule, and the target backend terminal routing policy rule reporting information reported by the terminal includes at least one of the following: Connectivity Rule identification; Backend device indication information.

13. The method according to claim 12, characterized in that Also includes: A target quality of service policy is issued for a target protocol data unit session according to the target back-end terminal routing policy rule reporting information.

14. The method according to any one of claims 11 to 13, characterized in that The generating terminal routing selection policy rule comprises: Receiving capability information reported by the terminal; If the capability information indicates that the terminal supports executing the backend terminal routing policy rule for the backend terminal, a terminal routing policy rule including the backend terminal routing policy rule is generated.

15. A communication device, characterized in that: include: one or more processors; A memory configured to store one or more programs, which, when executed by the one or more processors, enables the communication device to implement the method according to any one of claims 1 to 10; or A method as claimed in any one of claims 11 to 14.

16. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is run on a computer, the computer is caused to perform the method according to any one of claims 1 to 10; or A method as claimed in any one of claims 11 to 14.

17. A computer program product, characterized in that comprising a computer program, which, when executed by a computer, implements the method according to any one of claims 1 to 10; or, A method as claimed in any one of claims 11 to 14.

Images