Data transmission method and related equipment

Abstract

The embodiment of the invention provides a data transmission method and related equipment. The method executed by the terminal comprises the steps that a terminal routing strategy rule is received, the terminal routing strategy rule comprises a rear-end terminal routing strategy rule, the rear-end terminal routing strategy rule comprises service description information and a routing descriptor, the service description information is used for describing service information of the rear-end terminal, and the routing descriptor is used for describing the service information of the rear-end terminal; the back-end terminal accesses a mobile network through the terminal, and the route selection descriptor is used for executing route selection described in the route selection descriptor on a service matched with the service description information in the back-end terminal.

Description

Technical Field

[0001] 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

[0002] A terminal (such as UE1 in the following text) can allow one or more backend terminals (such as backend UE (User Equipment) in the following text) to access the mobile network through the terminal (such as UE1) by sharing its own hotspot. However, the backend terminals accessed 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. Summary of the invention

[0003] An embodiment of the present disclosure provides a data transmission method, which is executed by a terminal, and includes: receiving 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 the back-end terminal, wherein 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 a service in the back-end terminal that matches the service description information.

[0004] In some exemplary embodiments of the present disclosure, the method also 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 for the service of the back-end terminal, executing the target routing descriptor in the target back-end terminal routing policy rule.

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

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

[0007] 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 for creating a new target protocol data unit session is initiated.

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

[0009] 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, 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, wherein 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; and transmitting the terminal routing policy rule to the terminal.

[0010] An embodiment of the present disclosure provides a terminal, comprising: a receiving unit, used to receive 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 the back-end terminal, wherein 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 a service in the back-end terminal that matches the service description information.

[0011] The embodiment of the present disclosure provides a policy control function network element, including: a processing unit, used to generate a terminal routing policy rule, 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 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; a sending unit, used to transmit the terminal routing policy rule to the terminal.

[0012] An embodiment of the present disclosure provides a communication device, including: one or more processors; and a memory configured to store one or more programs, so that 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.

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

[0014] 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

[0015] Figure 1 It is a schematic diagram of a communication system architecture provided by an embodiment of the present disclosure.

[0016] Figure 2 It is a system architecture diagram of the 5G network provided by an embodiment of the present disclosure.

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

[0018] Figure 4The interactive diagram of the data transmission method according to an embodiment of the present disclosure is schematically shown.

[0019] Figure 5 The interactive diagram of a data transmission method according to another embodiment of the present disclosure is schematically shown.

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

[0021] Figure 7 The block diagram of a policy control function network element according to an embodiment of the present disclosure is schematically shown.

[0022] Figure 8 A schematic structural diagram of a communication device according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical solutions and advantages of the present disclosure more obvious, the exemplary embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. In the accompanying drawings, the same reference numerals represent the same elements from beginning to end. It should be understood that the embodiments described here are merely illustrative and should not be interpreted as limiting the scope of the present disclosure.

[0024] In the embodiments of the present disclosure, the term "module" or "unit" refers to a computer program or a part of a computer program with 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.

[0025] The technical solutions of the embodiments of the present disclosure can be applied to various communication systems, for example: 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.

[0026] For example, the communication system 100 used in the embodiment of the present disclosure is as follows: Figure 1 As shown. 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 in the coverage area. Optionally, the network device 110 may be a base station (Base TransceiverStation, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or 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.

[0027] The communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110. As used herein, "terminal" includes but is not limited to connecting via a wired line, such as via a Public Switched Telephone Networks (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as, for 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 radiotelephones, pagers, Internet / Intranet access, Web browsers, notepads, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or palmtop receivers or other electronic devices that include radiotelephone transceivers. A terminal may refer to 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 function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.

[0028] Optionally, the terminals 120 may perform device-to-device (D2D) communication.

[0029] Figure 1One network device and two terminals are exemplarily shown. 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.

[0030] Optionally, the communication system 100 may also 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.

[0031] It should be understood that the device with communication function in the network / system in the embodiments of the present disclosure can be referred to as a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication device may include a network device 110 and a terminal 120 having communication functions. The network device 110 and the terminal 120 may be the specific devices described above and will not be described in detail here.

[0032] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone.

[0033] Figure 2 is a system architecture diagram of a 5G network according to an embodiment of the present disclosure, such as Figure 2 As shown, the equipment involved in the 5G network system includes: terminal (UE), radio access network (Radio Access Network, RAN), user plane function (User Plane Function, UPF) network element, data network (Data Network, DN), access 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, unified data management (Unified Data Management, UDM) network element.

[0034] like Figure 2As shown in the figure, the network elements related to policies are mainly PCF, AMF, SMF, RAN, and UE. Among them, SMF is mainly responsible for the execution of policies related to sessions, and AMF is mainly responsible for the execution of policies related to access and UE policies. The policy issuance and update on the two network elements (AMF and SMF) are all controlled by PCF.

[0035] Specifically for UE policy, PCF and UE can monitor UE policy-related information through containers, including UE policy content, UE policy identifier, etc. In the uplink direction, the container is sent by UE to AMF through NAS (non-access-stratum) message, and AMF continues to transparently transmit (without perception or modification) to PCF. In the downlink direction, the PCF sends the container to AMF, and AMF then transparently transmits it to UE through NAS message.

[0036] 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 (Route Selection Descriptor, RSD). The traffic descriptor in URSP is used to describe a specific service. There can be one or more RSDs under a traffic descriptor. Each RSD corresponds to the attributes of a PDU session, which means that the service data corresponding to the traffic descriptor can run in the PDU session corresponding to the RSD.

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

[0038] Table 1: URSP Rules

[0039]

[0040]

[0041] In the above Table 1, Rule Precedence represents the rule priority, which is used to indicate the execution order of the URSP rule in the UE. The rule priority determines the order in which the UE uses the URSP rule. Traffic descriptor is a traffic descriptor / service descriptor used to describe the matching criteria, describing the service information that meets the URSP rule. It consists of one or more components, which may include application descriptors, IP descriptors (destination IP), domain name descriptors (destination FQDN (Fully Qualified Domain Name)), non-IP descriptors (Non-IP descriptors, descriptor information of non-IP services), DNN (Data Network Name, data network name) and connection capabilities. The traffic descriptor is used by the UE for application matching. Destination IP 3tuple(s) (IP address or IPv6 network prefix, port number, protocol ID of the protocol above IP) represents the target IP 3-tuple (IP address or IPv6 network prefix, port number, protocol ID of the protocol above IP). FQDN(s) or a regular expression which are used as a domain name matching criteria indicates the FQDN or regular expression used as a domain name matching criteria. This is matched against the DNN information provided by the application indicates that this matches the DNN information provided by the application. This is matched against the information provided by a UE application when it requests a network connection with certain capabilities or traffic categories indicates that this matches the information provided by a UE application when it requests a network connection with certain capabilities or traffic categories. Connection capabilities can typically be: "ims", "mms", "internet", etc. This URSP rule applies when any component in the traffic descriptor can match 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.

[0042] Table 2: RSD

[0043]

[0044]

[0045] In Table 2 above, Route Selection Descriptor Precedence indicates the RSD priority, which determines the order in which the RSDs are used. When an RSD with a higher priority cannot be used, other RSDs are used. Route selection components represent route selection components, which describe various network resources that applications can use. It consists of one or more components, including SSC (service and session continuity) mode selection (SSC Mode Selection, used by UE to select the corresponding SSC mode for matching applications), network slice selection (Network Slice Selection, a list of one or a group of S-NSSAI(s), used by UE to select the corresponding S-NSSAI for matching applications), DNN selection (DNN Selection, a list of one or a group of DNN(s) values, used by UE to select the corresponding DNN for matching applications), PDU (Protocol Data Unit) session type selection (PDU Session Type Selection, PDU session type, etc., used by UE to select the corresponding PDU session type for matching applications), Non-Seamless Offload indication and Access Type preference (also known as Access Type preference. If the UE needs to establish a PDU session for a matching application, it will indicate the preferred access type (3GPP or non-3GPP or Multi-Access)).

[0046] Route Selection Validation Criteria, route selection validation criteria parameters, or called route selection verification criteria / route selection validity conditions, describe the corresponding validity conditions. This parameter is an optional parameter, which includes the time window (Time Window, also called the effective 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 location where the RSD is valid, which can also be understood as the UE location allowed by the service traffic. When the UE current location is different from the location defined in the location validity, the RSD is invalid. That is, if the current time is not within the time window or the UE location does not match the location criteria, that is, if any of the route selection validation criteria parameters is not met, the corresponding RSD is considered invalid.

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

[0048] In the related art, the URSP rules are only formulated and issued for the terminal UE1, and are only stored and used in the 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 selection strategies and QoS rules. That is, in the related art, the 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 the enhancement of the routing selection strategy for the data of the back-end terminal accessing the mobile network through the hotspot of the 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 the UE1, and can adopt WIFI connection, Bluetooth connection, USB connection, or cellular connection methods such as 4G and 5G.

[0049] Figure 3 The method provided in the embodiment may be executed by a terminal (such as the above-mentioned UE1). Figure 3 As shown, the method provided by the embodiment of the present disclosure may include the following steps.

[0050] In S310, 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, wherein 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 a service in the back-end terminal that matches the service description information.

[0051] In an exemplary embodiment, the terminal routing policy rule includes a service descriptor, the service descriptor includes a connection back-end terminal descriptor, and the connection back-end terminal descriptor is used as service description information for connecting the back-end terminal. The terminal routing policy rule including the connection back-end terminal descriptor in the service descriptor is the back-end terminal routing policy rule.

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

[0053] 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 this terminal, and the connection backend terminal descriptor is only valid for the backend terminal service connected to this terminal.

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

[0055] In an exemplary embodiment, the terminal routing policy rule includes a rule priority, a service descriptor and a connection back-end terminal service descriptor, and the connection back-end terminal service descriptor is used as service description information for connecting the back-end terminal. The terminal routing policy rule including the service descriptor and the connection back-end terminal service descriptor is the back-end terminal routing policy rule.

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

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

[0058] 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), and the backend terminal routing policy rule includes a service descriptor, which serves as service description information for connecting the backend terminal.

[0059] In some embodiments, the UE may receive a URSP rule. For example, the URSP rule received by the UE includes a service descriptor, in which a connection backend terminal descriptor is added, and the connection backend terminal descriptor is used as the service description information for connecting 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, and the connection backend terminal service descriptor is used as the service description information for connecting 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, and the service descriptor contained in the Tether-URSP rule is used as the service description information for connecting the backend terminal.

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

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

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

[0063] Domain name descriptor;

[0064] Internet protocol descriptor;

[0065] Connectivity.

[0066] In some embodiments, when the connection backend terminal descriptor is used as the service description information, the connection backend terminal descriptor is included in the service descriptor, and the connection backend terminal descriptor includes at least one of the following: device type; domain name descriptor; Internet protocol descriptor; connection capability. In other embodiments, when the URSP rule includes a parallel service descriptor and a connection backend terminal service descriptor, and the connection backend terminal service descriptor is used as the service description information for connecting the backend terminal, the connection backend terminal service descriptor includes at least one of the following: device type; domain name descriptor; Internet protocol descriptor; connection capability. In some further embodiments, when the 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, and the service descriptor is used as the service description information, the service descriptor includes at least one of the following: device type; domain name descriptor; Internet protocol descriptor; connection capability.

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

[0068] In an exemplary embodiment, the method provided by the embodiment of the present disclosure further 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. The target back-end terminal routing policy rule reporting information reported by the terminal includes at least one of the following:

[0069] Connectivity

[0070] Rule identification;

[0071] Backend device indication information.

[0072] In the embodiments 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.

[0073] In an exemplary embodiment, the method also 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 for the service of the back-end terminal, executing the target routing descriptor in the target back-end terminal routing policy rule.

[0074] In an exemplary embodiment, the back-end terminal routing selection policy rules also include rule priorities; wherein, matching target back-end terminal routing selection policy rules from the back-end terminal routing selection policy rules for the services of the back-end terminal includes: matching the target back-end terminal routing selection policy rules from the back-end terminal routing selection policy rules in the order of rule priorities in the back-end terminal routing selection policy rules.

[0075] In an exemplary embodiment, when the target back-end terminal routing policy rule is matched to 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 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.

[0076] 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, including: 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.

[0077] In an exemplary embodiment, the method further includes: reporting target backend terminal routing policy rule reporting information matching the backend terminal service, wherein the target backend terminal routing policy rule reporting information includes at least one of connection capability, rule identifier, and backend device indication information.

[0078] In an exemplary embodiment, the method further includes: reporting capability information of the terminal, the capability information indicating whether the terminal supports executing a backend terminal routing policy rule for the backend terminal.

[0079] The data transmission method provided by the embodiment of the present disclosure enhances the URSP rule 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 the network quality assurance of the service flow of the back-end terminal that accesses the mobile network through the terminal.

[0080] Figure 4 The following is a schematic diagram showing an interaction diagram of a data transmission method according to an embodiment of the present disclosure. Figure 4 As shown, the method provided by the embodiment of the present disclosure may include:

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

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

[0083] For the following Figure 5 In any of the multiple implementation methods of the backend terminal URSP rule provided in the embodiment, if UE1 supports executing specific URSP rules for the connected backend device (i.e., the target backend terminal URSP rule), 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 rule).

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

[0085] Optionally, after receiving the reported capability information, the PCF generates a URSP rule for the backend terminal (referred to as the backend terminal URSP rule) according to the reported capability information. The PCF may determine whether the UE1 supports the URSP rule for the backend terminal according to the capability information reported by the received UE1, and 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.

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

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

[0088] Optionally, the PCF sends the generated URSP to the AMF. The PCF may send the generated URSP for the backend terminal to the AMF, and after the AMF receives the URSP, the URSP is sent to the UE1 through 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 the UE1, but the present disclosure is not limited thereto.

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

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

[0091] Based on the received URSP for the backend terminal, UE1 associates the application data of the backend UE with the corresponding PDU session according to the URSP for the backend terminal for transmission. The mechanism is as follows: When the application layer of the backend UE sends data, UE1 receives the data of the UE. Since the source of the data is the connected backend terminal, the URSP rule of the backend terminal in the URSP is used to check whether the characteristics of the application data of the backend UE match the service description information of a rule in the URSP rule of the backend terminal. The order of checking is determined by the rule priority (Precedence) in the URSP rule of the backend terminal, that is, UE 1 checks the matching situation in turn based on the order of rule priority. When the service description information of a backend terminal URSP rule is matched, the RSD list under the URSP rule of the backend terminal is used to bind the PDU session. When a backend terminal URSP rule is matched, UE 1 searches for a suitable PDU session according to the Precedence order in the RSD. Here, the RSD with a high priority is used first. If a parameter in the RSD is one or more values, UE1 selects a combination of parameters to find out whether the PDU session exists:

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

[0093] 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,

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

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

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

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

[0098] For the following Figure 5 In any of the multiple implementation methods of the backend terminal URSP rule provided in the embodiment, if UE1 matches a specific backend terminal URSP rule (i.e., the target backend terminal URSP rule) for the connected backend device, the matched backend terminal URSP rule can be reported to the network, and the reported information can be one or more of: connection capability, rule identifier (i.e., the identifier of the target backend terminal URSP rule), backend device indication information, etc. Network elements in the network, such as PCF, etc., can determine that there is currently a backend terminal / backend device access based on the reported target backend terminal URSP rule information, and can issue a specific QoS policy (i.e., target QoS policy) for the PDU session (for distinction, referred to as the target PDU session) according to the policy, which can include QoS rules, QoS profile (configuration file) information, etc.

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

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

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

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

[0103] In S510, a terminal routing policy rule is generated, and the terminal routing policy rule includes a backend terminal routing policy rule, and the backend 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 backend terminal, and the backend 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 backend terminal.

[0104] In the embodiments of the present disclosure, a terminal refers to a terminal that is connected to a back-end terminal and allows the back-end terminal to access a mobile network through the terminal, and is hereinafter represented by UE1 or this terminal. For example, UE1 can allow the back-end terminal to access a mobile network by sharing its own hotspot, but the present disclosure is not limited to this. A back-end terminal refers to a terminal that accesses a mobile network through the terminal, such as UE1. The embodiments of the present disclosure do not limit the types of back-end terminals and terminals, for example, it can be any one or more of a laptop computer, a tablet computer, a mobile phone, a drone, a robot, an Internet of Things device, etc.

[0105] Among them, the terminal routing policy URSP may include one or more (two or more) URSP rules, and each URSP rule may include one or more routing descriptors RSD. URSP can be used to enable UE (e.g., UE1 and / or backend UE) to map a specific service flow to a corresponding data transmission session. For example, PCF can generate multiple URSP rules in the core network. For UE1, each URSP rule may include a traffic descriptor (TrafficDescriptor) and a routing descriptor (RSD). When an application on UE1 is started, the Traffic Descriptor in the URSP rule generated by the core network can be matched according to the traffic characteristics of the application started by UE1 to determine the corresponding URSP. Each URSP rule may include one or more RSDs, and corresponding RSD priorities may be configured for different RSDs in each URSP rule according to service requirements and service types. After matching the corresponding URSP, UE1 can select the corresponding RSD according to the RSD priorities of the generated RSDs, and transmit the data of the application (referred to as service data or application data) on the data transmission session corresponding to the RSD.

[0106] In the disclosed embodiment, the URSP rule includes a back-end terminal URSP rule, and the back-end terminal URSP rule refers to a URSP rule set for a back-end terminal, or service description information for the back-end terminal is added to the URSP rule set for the terminal, so that the terminal can match the corresponding URSP rule for its back-end terminal.

[0107] 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 is used as service description information for connecting the backend terminal.

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

[0109] In some embodiments, when the service descriptor includes both the connection back-end terminal descriptor and other existing parameters, the other existing parameters are valid for the service of the terminal, and the connection back-end terminal descriptor is only valid for the back-end terminal service connected to the terminal. In other embodiments, when the service descriptor includes both the connection back-end terminal descriptor and other existing parameters, the other parameters included in the service descriptor except the connection back-end terminal descriptor are invalid; or the service descriptor does not include other parameters except the connection back-end terminal descriptor.

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

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

[0112] Domain name descriptor;

[0113] Internet Protocol (IP) descriptor;

[0114] Connectivity.

[0115] In some embodiments, in the traffic descriptor of the URSP rule, the following field content is added:

[0116] - A connection backend terminal descriptor, which includes service description information for the backend terminal to which the UE1 is connected (in this case, the URSP rule with the connection backend terminal descriptor added is referred to as a backend terminal URSP rule).

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

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

[0119] Domain descriptors: FQDN(s) or a regular expression whichare used as a domain name matching criteria.

[0120] IP descriptors: Destination IP 3tuple(s)(IP address orIPv6network prefix,port number,protocol ID of the protocol above IP).

[0121] Connection Capabilities: This is matched against the information provided by a UE application when it requests a network connection with certain capabilities or traffic categories. Connection capabilities can usually be: "ims", "mms", "internet", etc.

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

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

[0124] 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 service 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.

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

[0126] 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", and when the URSP rule contains the "connection back-end terminal service descriptor", the "service descriptor" is invalid, and the content may be empty, or even if there is content, the service descriptor is invalid. At this time, the URSP rule with the connection back-end terminal service descriptor added is called the back-end terminal URSP rule.

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

[0128] When UE1 receives a URSP rule containing a "connection back-end terminal service descriptor", it will match the service flow for the service of the back-end terminal connected through the hotspot, and the matching order is the priority of these URSP rules containing the "connection back-end terminal service descriptor". When the UE matches a specific URSP rule (referred to as the target back-end terminal URSP rule) for the service of the back-end 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 be executed only when the routing validity condition is met.

[0129] 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 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 URSP rule has not established a PDU session, then a new PDU session process is initiated.

[0130] In an exemplary embodiment, the 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, and the service descriptor is service description information for connecting the backend terminal.

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

[0132] In some other embodiments, a URSP rule for the backend terminal (also referred to as Tether-UE) connected to the UE1 is newly defined, 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, it may be defined as Tether-URSP, and the Tether-URSP rule may include the following content:

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

[0134] - Traffic descriptor: describes the service information of the backend terminal that complies with the Tether-URSP rules, which may further include the following:

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

[0136] Domain descriptors: FQDN(s) or a regular expression whichare used as a domain name matching criteria.

[0137] IP descriptors: Destination IP 3tuple(s)(IP address or IPv6network prefix,port number,protocol ID of the protocol above IP).

[0138] Connection Capabilities: This is matched against the information provided by a UE application when it requests a network connection with certain capabilities or traffic categories. Connection capabilities can typically be: "ims", "mms", "internet", etc.

[0139] - Route selection descriptors (RSD): The route selection described in the RSD is executed for the services matching the above traffic descriptors in the back-end terminal. The RSD may further include the following contents:

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

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

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

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

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

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

[0146] Location Criteria: defines the UE location allowed for traffic. When the UE current location is different from the location defined in the location criteria, the RSD is invalid.

[0147] 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, and 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), the RSD in the specific Tether-URSP rule can be executed (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.

[0148] The method for executing the target RSD is: if the matching Tether-URSP rule has established a PDU session (target PDU session), 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, a new PDU session process is initiated.

[0149] In S520, the URSP is transmitted to the terminal.

[0150] In some embodiments, PCF can send the generated URSP to the terminal UE1 through AMF, but the present disclosure is not limited to this. In other embodiments, the URSP rules formulated by PCF can be sent to UE1 through 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.

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

[0152] The backend terminal URSP rule can contain one or more RSDs, and each RSD can be used to indicate the corresponding PDU session. For example, the RSD can contain parameters for establishing a PDU session, such as DNN, Network Slice SelectionPolicy, S-NSSAI, PDU session type, and other parameters. PDU sessions corresponding to different RSDs may provide different Internet experience.

[0153] The data transmission method provided by the embodiment of the present disclosure enhances the URSP rules when the PCF generates the URSP for the terminal, and generates the back-end terminal URSP rules 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 the PDU session (optionally, QoS flow binding can be performed), thereby better supporting the network quality assurance of the service flow of the back-end terminal that accesses the mobile network through the terminal.

[0154] Figure 5 For other contents of the embodiment, reference may be made to the above embodiment.

[0155] Figure 6 A block diagram of a terminal according to an embodiment of the present disclosure is schematically shown. Figure 6 The terminal 600 provided in the embodiment may include a receiving unit 610 .

[0156] The receiving unit 610 is used to receive terminal routing policy rules, wherein the terminal routing policy rules include back-end terminal routing policy rules, and 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, and 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.

[0157] 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 service of the backend terminal 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 service of the backend terminal is matched to the target backend terminal routing policy rule.

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

[0159] In some exemplary embodiments of the present disclosure, the processing unit is further used for: if the target backend terminal routing policy rule also includes a target routing validity condition, then when the service of the backend terminal satisfies the target routing validity condition, executing the target routing descriptor.

[0160] In some exemplary embodiments of the present disclosure, the processing unit is also used for: 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 sending the service flow corresponding to the service of the back-end terminal on the target protocol data unit session, or initiating 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 initiating a process for creating a new target protocol data unit session.

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

[0162] In some exemplary embodiments of the present disclosure, the terminal 600 further includes a sending unit, configured to report 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.

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

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

[0165] The processing unit 710 is used to 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 sending unit 720 is used to transmit the terminal routing policy rule to the terminal.

[0166] In an exemplary embodiment, the terminal routing policy rule includes a service descriptor, the service descriptor includes a connection back-end terminal descriptor, and the connection back-end terminal descriptor is used as service description information for connecting the back-end terminal. The terminal routing policy rule including the connection back-end terminal descriptor in the service descriptor is the back-end terminal routing policy rule.

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

[0168] In an exemplary embodiment, the back-end terminal routing policy rule includes a rule priority, a service descriptor and a connection back-end terminal service descriptor, and the connection back-end terminal service descriptor is used as service description information for connecting the back-end terminal. The terminal routing policy rule including the service descriptor and the connection back-end terminal service descriptor is the back-end terminal routing policy rule.

[0169] In an exemplary embodiment, the 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, and the service descriptor is service description information for connecting the backend terminal.

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

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

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

[0173] Domain name descriptor;

[0174] Internet protocol descriptor;

[0175] Connectivity.

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

[0177] In an exemplary embodiment, the policy control function network element 700 also includes a receiving unit for receiving target back-end terminal routing selection policy rule reporting information reported by the terminal and matching the back-end terminal service, wherein the target back-end terminal routing selection policy rule reporting information includes target back-end terminal routing selection policy rules, and the target back-end terminal routing selection policy rule reporting information includes at least one of the following: connection capability; rule identifier; back-end device indication information.

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

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

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

[0181] Figure 8 The schematic structural diagram of a communication device 800 according to an embodiment of the present disclosure is schematically shown. 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 an UPF network element. Figure 8 The communication device 800 shown includes a processor 810. The processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present disclosure.

[0182] Alternatively, if Figure 8As shown, the communication device 800 may further include a memory 820. The processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present disclosure.

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

[0184] Alternatively, if Figure 8 As shown, 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, may send information or data to other devices, or receive information or data sent by other devices.

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

[0186] 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 corresponding processes implemented by various network elements in various methods of the embodiments of the present disclosure, which will not be described in detail here for the sake of brevity.

[0187] 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 corresponding processes implemented by the mobile terminal / terminal in each method of the embodiment of the present disclosure, which will not be described in detail here for the sake of brevity.

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

[0189] It should be understood that the processor of the embodiment of the present disclosure may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in software form.

[0190] The above-mentioned processor may 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 gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present disclosure may be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present disclosure may be directly embodied as being executed by a hardware decoding processor, or may be executed by a combination of hardware and software modules in the decoding processor. The software module may 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 a memory, and the processor reads the information in the memory and completes the steps of the above-mentioned method in combination with its hardware.

[0191] It can be 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 RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM (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 memory is an example and not a limitation.

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

[0193] 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 are not repeated here.

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

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

[0196] 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 are not repeated here.

[0197] 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, which will not be repeated here for the sake of brevity.

[0198] The embodiment of the present disclosure also provides a computer program.

[0199] 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 each method of the embodiments of the present disclosure. For the sake of brevity, they are not repeated here.

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

[0201] Those of ordinary skill 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. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this disclosure.

[0202] Those skilled in the art can 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.

[0203] In the several embodiments provided in the present 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 only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.

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

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

[0206] 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, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform 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.

[0207] The above is only a specific embodiment of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present disclosure, which should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A data transmission method, characterized in that, the method is executed by a terminal, and the method includes: receiving a terminal routing selection policy rule, the terminal routing selection policy rule includes a backend terminal routing selection policy rule, the backend terminal routing selection policy rule includes service description information and a routing selection descriptor, the service description information is used to describe the service information of the backend terminal, the backend terminal accesses the mobile network through the terminal, and the routing selection descriptor is used to perform the routing selection described in the routing selection descriptor on the service in the backend terminal that matches the service description information.

2. The method according to claim 1, characterized in that, the terminal routing selection policy rule includes a service descriptor, the service descriptor includes a connection backend terminal descriptor, the connection backend terminal descriptor is used as the service description information for connecting to the backend terminal, and the terminal routing selection policy rule including the connection backend terminal descriptor in the service descriptor is the backend terminal routing selection policy rule.

3. The method according to claim 2, characterized in that, the backend terminal routing selection policy rule further 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 backend terminal service descriptor, the connection backend terminal service descriptor is used as the service description information for connecting to the backend terminal, and the terminal routing selection policy rule including the service descriptor and the connection backend terminal service descriptor is the backend terminal routing selection policy rule.

5. The method according to claim 1, characterized in that, the backend terminal routing selection policy rule is a terminal routing selection policy rule for the backend terminal, the backend terminal routing selection policy rule includes a service descriptor, and the service descriptor is used as the service description information for connecting to the backend terminal.

6. The method according to claim 5, characterized in that, the backend terminal routing selection policy rule further includes a rule priority, and the rule priority indicates the execution order of the backend 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; connection capability.

8. The method according to claim 1, characterized in that, the backend terminal routing selection policy rule further includes a routing selection validity condition, and the routing selection validity condition is used to indicate that when the backend terminal meets the routing selection validity condition, the routing selection descriptor is valid.

9. The method according to claim 1, characterized in that, further includes: Report the target back-end terminal routing selection policy rule reporting information that matches the back-end terminal service. The target back-end terminal routing selection policy rule reporting information includes the matched target back-end terminal routing selection policy rule. The target back-end terminal routing selection policy rule reporting information reported by the terminal includes at least one of the following: Connection ability; Rule identifier; Back-end device indication information.

10. According to the method described in claim 1, characterized in that, it further includes: Report the ability information of the terminal. The ability information indicates whether the terminal supports executing the back-end terminal routing selection policy rule for the back-end terminal.

11. A data transmission method, characterized in that, this method is executed by a policy control function network element, and this method includes: Generate a terminal routing selection policy rule. The terminal routing selection policy rule includes a back-end terminal routing selection policy rule. The back-end terminal routing selection policy rule includes service description information and a routing selection 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 selection descriptor is used to perform the routing selection described in the routing selection descriptor on the service in the back-end terminal that matches the service description information; Transmit the terminal routing selection policy rule to the terminal.

12. According to the method described in claim 11, characterized in that, it further includes: Receive the target back-end terminal routing selection policy rule reporting information that matches the back-end terminal service reported by the terminal. The target back-end terminal routing selection policy rule reporting information includes the matched target back-end terminal routing selection policy rule. The target back-end terminal routing selection policy rule reporting information reported by the terminal includes at least one of the following: Connection ability; Rule identifier; Back-end device indication information.

13. According to the method described in claim 12, characterized in that, it further includes: Issue a target quality of service policy for the target protocol data unit session according to the target back-end terminal routing selection policy rule reporting information.

14. According to the method described in claim 11, characterized in that, generating a terminal routing selection policy rule includes: Receive the ability information reported by the terminal; If the ability information indicates that the terminal supports executing the back-end terminal routing selection policy rule for the back-end terminal, then generate a terminal routing selection policy rule including the back-end terminal routing selection policy rule.

15. A communication device, characterized in that, it includes: One or more processors; A memory configured to store one or more programs. When the one or more programs are executed by the one or more processors, the communication device implements the method described in any one of claims 1 to 10; or, The method described in any one of claims 11 to 14.

16. A computer-readable storage medium, the computer-readable storage medium stores a computer program, characterized in that, when the computer program runs on a computer, the computer executes the method described in any one of claims 1 to 10; or, The method according to any one of claims 11 to 14.

Images