WO2019075763A1 - 用于传输数据的方法、终端设备和网络设备 - Google Patents

用于传输数据的方法、终端设备和网络设备 Download PDF

Info

Publication number
WO2019075763A1
WO2019075763A1 PCT/CN2017/107168 CN2017107168W WO2019075763A1 WO 2019075763 A1 WO2019075763 A1 WO 2019075763A1 CN 2017107168 W CN2017107168 W CN 2017107168W WO 2019075763 A1 WO2019075763 A1 WO 2019075763A1
Authority
WO
WIPO (PCT)
Prior art keywords
rule
terminal device
network device
pdu session
identifier
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/107168
Other languages
English (en)
French (fr)
Inventor
唐海
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to CN202010099121.1A priority Critical patent/CN111182572B/zh
Priority to PCT/CN2017/107168 priority patent/WO2019075763A1/zh
Priority to KR1020207014334A priority patent/KR102370267B1/ko
Priority to BR112020007560-4A priority patent/BR112020007560B1/pt
Priority to KR1020227006555A priority patent/KR102477765B1/ko
Priority to JP2020521884A priority patent/JP7063988B2/ja
Priority to ES17928855T priority patent/ES2900193T3/es
Priority to CN201780092464.1A priority patent/CN110809899B/zh
Priority to US16/755,879 priority patent/US11304260B2/en
Priority to AU2017436351A priority patent/AU2017436351B2/en
Priority to EP17928855.0A priority patent/EP3700268B1/en
Priority to PL17928855T priority patent/PL3700268T3/pl
Priority to RU2020116371A priority patent/RU2761443C2/ru
Priority to CA3079480A priority patent/CA3079480C/en
Priority to EP21196875.5A priority patent/EP3965367A1/en
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to PCT/CN2017/111688 priority patent/WO2019075816A1/zh
Priority to AU2018353168A priority patent/AU2018353168A1/en
Priority to EP18868123.3A priority patent/EP3691380B1/en
Priority to CN202010303770.9A priority patent/CN111654922B/zh
Priority to PCT/CN2018/091888 priority patent/WO2019076075A1/zh
Priority to JP2020521993A priority patent/JP7182621B2/ja
Priority to KR1020207013837A priority patent/KR102477774B1/ko
Priority to CN201880057322.6A priority patent/CN111052832B/zh
Priority to PCT/CN2018/104911 priority patent/WO2019076167A1/zh
Priority to TW107136608A priority patent/TWI779117B/zh
Publication of WO2019075763A1 publication Critical patent/WO2019075763A1/zh
Priority to US16/850,844 priority patent/US11330666B2/en
Anticipated expiration legal-status Critical
Priority to US17/590,604 priority patent/US20220159781A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/248—Connectivity information update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the embodiments of the present application relate to the field of communications, and, more particularly, to a method, a terminal device, and a network device for transmitting data.
  • a terminal device In a wireless communication network, a terminal device needs to complete a protocol data unit (PDU) session establishment process before performing related services.
  • PDU protocol data unit
  • the terminal device After the terminal device initiates the session establishment process to the network device, the terminal device cannot know the establishment of the session, so that the terminal device cannot adjust the session establishment policy in time, which affects the performance of the communication system.
  • the embodiments of the present application provide a method, a terminal device, and a network device for transmitting data, which are beneficial to improving performance of a communication system.
  • a first aspect provides a method for transmitting data, the method comprising: the terminal device transmitting a first request message to the network device, where the first request message is used to apply for N in the first protocol data unit PDU session.
  • the session of the data stream is established; the terminal device receives a response message of the first request message sent by the network device, where the response message is used to indicate that the network device refuses to perform M in the N data streams in the first PDU session.
  • the session of the data stream is established, N and M are both positive integers, and N is greater than or equal to M.
  • the situation that the session establishment is fed back to the terminal device by the network device enables the terminal device to adjust the session establishment policy in time, thereby facilitating the performance of the communication system.
  • the response message carries a reject cause value, where the reject cause value is used to indicate that the first PDU session does not support the M data streams.
  • the terminal device can appropriately adjust the PDU session to initiate session establishment or modification to the network device. In turn, the possibility of successful establishment of a PDU session can be improved.
  • the response message carries each data in the M data streams.
  • the method further includes: in response to the response message, the terminal device sends a second request message to the network device, where the second request message is used to apply for the M in the second PDU session. Session establishment of at least one of the data streams.
  • the first request message carries an identifier of the first PDU session
  • the second request message carries an identifier of the second PDU session, where the second PDU session is used to adjust the first PDU session.
  • the first PDU session after the identification.
  • the method before the responding to the response message, the method further includes: the terminal device adjusting, according to the M data streams, a setup parameter of the second PDU session that is not the first PDU session. .
  • the response message carries an identifier of the second PDU session.
  • the network device is a session management function SMF device.
  • a second aspect provides a method for transmitting data, including: receiving, by a network device, a first request message sent by a terminal device, where the first request message is used to apply for performing N data in a first protocol data unit PDU session.
  • the session of the stream is established; the network device sends a response message of the first request message to the terminal device, where the response message is used to indicate that the network device refuses to perform M data in the N data streams in the first PDU session.
  • the session of the stream is established, N and M are both positive integers, and N is greater than or equal to M.
  • the response message carries a reject cause value, where the reject cause value is used to indicate that the first PDU session does not support the M data streams.
  • the response message carries an identifier of each of the M data streams.
  • the method further includes: receiving, by the network device, a second request message sent by the terminal device, where the second request message is used to apply for performing the M data streams in the second PDU session.
  • a session of at least one data stream is established.
  • the response message carries an identifier of the second PDU session that is not recommended by the network device and is not the first PDU session.
  • the network device is a session management function SMF device, and the method further includes: the SMF device triggering, according to the first request message, the access network device to perform the N in the first PDU session. a session establishment of the data stream; the SMF device receives a data flow list corresponding to the first PDU session sent by the access network device, where the data flow list includes the M (N-M) of the N data streams received by the first PDU session.
  • the third aspect provides a method for transmitting data, including: the terminal device acquiring the at least one rule according to the identifier of each rule in the at least one rule in the user equipment routing policy URSP; the terminal device according to the at least one A rule is to initiate establishment or modification of at least one protocol data unit PDU session corresponding to the at least one rule to the network device, respectively.
  • the terminal device can obtain a certain rule according to the rule identifier, and the network device does not send all the rules to the terminal device at one time, which reduces the pressure on the network device and improves the communication flexibility.
  • the at least one rule is a plurality of rules
  • the terminal device initiates, according to the multiple rules, a plurality of protocol data unit PDU sessions that are in one-to-one correspondence with the plurality of rules, respectively.
  • modifying comprising: the terminal device initiating establishment or modification of the multiple PDU sessions to the network device according to the priority of the multiple rules.
  • the priority level of each rule can be characterized by the identity of each rule.
  • the first rule in the at least one rule includes at least one of the following parameters: a radio access technology RAT, a session and a service continuity mode, a single network slice assistance information S-NSSAI, Split type, data network name DNN, and data flow filter.
  • the first parameter of the at least one parameter includes multiple values that represent priorities
  • the terminal device initiates establishment of a first protocol data unit PDU session to the network device according to the first rule.
  • modifying comprising: the terminal device initiating establishment or modification of the first PDU session to the network device according to the priority of the multiple values.
  • the terminal device initiates the establishment or modification of the first protocol data unit PDU session to the network device according to the first rule in the at least one rule, including: the terminal device according to the first rule, Sending a first request message to the network device, where the first request message is used to request the network device to perform session establishment of N data flows in the first PDU session; and the terminal device sends the network to the network according to the first rule
  • the method further includes: receiving, by the terminal device, a response message of the first request message sent by the network device, where the response message is used to indicate that the network device rejects the first PDU.
  • the session establishment of the M data streams in the N data streams is performed in the session, and N and M are both positive integers, and N is greater than or equal to M.
  • the response message carries a reject reason value, and the reject cause value Used to indicate at least one of the following cases: PDU session not supported, RAT access not allowed, session or traffic continuity mode not satisfied, S-NSSAI error, DNN not supported, and PDU session identification not recognized.
  • the method further includes: adjusting, by the terminal device, a value of a parameter in the first rule corresponding to the reject reason value in response to the response message; the terminal device according to the adjusted A rule is to send a second request message to the network device, where the second request message is used to request the network device to perform session establishment of at least one of the M data streams in the first PDU session.
  • the parameter of the first rule corresponding to the reject reason value includes multiple values that represent a priority
  • the terminal device adjusts the first corresponding to the reject cause value in response to the response message.
  • the value of a rule parameter includes: the terminal device adjusts, according to the response message, a value of the parameter of the first URSP corresponding to the reject reason value to a value higher than a value of the previous initiation of the first PDU session. .
  • the response message carries the value of the parameter of the first rule that is recommended by the network device, and the terminal device adjusts the value corresponding to the reject reason value in response to the response message.
  • the value of the parameter of the first URSP includes: the terminal device adjusts a value of the parameter of the first rule corresponding to the reject reason value to the first rule that is recommended by the network device and corresponds to the reject reason value. The value of the parameter.
  • the method further includes: receiving, by the terminal device, a second rule of the URSP that is sent by the network device, except for the first rule in the at least one rule, and an identifier of the first rule; Obtaining the first rule according to the identifier of the first rule, the device: after the second PDU session corresponding to the second rule is established, the terminal device acquires the first rule by using a user plane according to the identifier of the first rule Or the terminal device triggers the network device to deliver the first rule by using the control plane according to the identifier of the first rule.
  • the method further includes: the terminal device receiving the identifier of the server; after establishing the second PDU session corresponding to the second rule, the terminal device passes the user according to the identifier of the first rule After the first rule is obtained, the terminal device obtains the first rule by using a user plane according to the identifier of the first rule and the identifier of the server after the second PDU session corresponding to the second rule is established.
  • the second rule has a higher priority than the first rule.
  • the terminal device obtains the at least one rule according to the identifier of each rule in the at least one rule of the user equipment routing policy URSP, including: in the process of performing network registration by the terminal device, The terminal device acquires the at least one rule according to the identifier of each rule in the at least one rule.
  • a fourth aspect provides a method for transmitting data, where the method includes: in a process of performing network registration by a terminal device, the network device sends, by using multiple messages, a plurality of user equipment routing policies URSP to the terminal device. rule.
  • the network device sends, by using a plurality of messages, a plurality of rules in the user equipment routing policy URSP, including: performing network on the terminal device, in the process of performing network registration by the terminal device. During the registration process, the network device sends the multiple rules to the terminal device through multiple messages of the control plane according to the priority of the multiple rules.
  • the network device is a policy control function PCF device.
  • a fifth aspect provides a method for transmitting data, where the method includes: in a process of performing network registration by a terminal device, the network device sends, to the terminal device, a user equipment routing policy URSP other than the first rule.
  • the second rule and the identifier of the first rule so that the terminal device acquires the first rule by using a user plane according to the identifier of the first rule after establishing a second PDU session corresponding to the second rule.
  • the method further includes: the network device sending an identifier of the server to the terminal device, so that the terminal device is configured according to the first PDU session corresponding to the second rule, according to the first The identifier of the rule and the identifier of the server are obtained by the user plane.
  • the network device is a policy control function PCF device.
  • a terminal device for performing the method of any of the above first aspect or any of the possible implementations of the first aspect.
  • the terminal device comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
  • a network device for performing the second aspect or the second aspect described above The method in any possible implementation.
  • the network device comprises means for performing the method of any of the above-described second or second aspects of the second aspect.
  • a terminal device for performing the method in any of the above-mentioned third aspect or any possible implementation of the third aspect.
  • the terminal device comprises means for performing the method in any of the possible implementations of the third aspect or the third aspect described above.
  • a network device for performing the method in any of the above possible implementations of the fourth aspect or the fourth aspect.
  • the network device comprises means for performing the method of any of the above-described fourth or fourth aspects of the fourth aspect.
  • a network device for performing the method in any of the possible implementation manners of the fifth aspect or the fifth aspect.
  • the network device comprises means for performing the method of any of the possible implementations of the fifth or fifth aspect above.
  • a terminal device comprising: a memory, a processor, an input interface, and an output interface.
  • the memory, the processor, the input interface, and the output interface are connected by a bus system.
  • the memory is for storing instructions for executing the memory stored instructions for performing the method of any of the first aspect or the first aspect of the first aspect.
  • a network device comprising: a memory, a processor, an input interface, and an output interface.
  • the memory, the processor, the input interface, and the output interface are connected by a bus system.
  • the memory is for storing instructions for executing the memory stored instructions for performing the method of any of the above-described second aspect or any of the possible implementations of the second aspect.
  • a terminal device comprising: a memory, a processor, an input interface, and an output interface.
  • the memory, the processor, the input interface, and the output interface are connected by a bus system.
  • the memory is for storing instructions for executing the memory stored instructions for performing the method of any of the above-described third aspect or any of the possible implementations of the third aspect.
  • a network device comprising: a memory, a processor, an input interface, and an output interface.
  • the memory, the processor, the input interface, and the output interface are connected by a bus system.
  • the memory is for storing instructions for executing the memory stored instructions for performing the method of any of the possible implementations of the fourth aspect or the fourth aspect above.
  • a network device comprising: a memory, a processor, an input interface, and an output interface.
  • the memory, the processor, the input interface, and the output interface are connected by a bus system.
  • the memory is for storing instructions for executing the memory stored instructions for performing the method of any of the above fifth or fifth possible implementations.
  • a sixteenth aspect a computer storage medium for storing a method in performing any of the above first aspect or any of the possible implementations of the first aspect, or any possible implementation of the second aspect or the second aspect above
  • a seventeenth aspect a computer program product comprising instructions, when executed on a computer, causing a computer to perform the method of any of the above-described first aspect or any of the alternative implementations of the first aspect, or The method of any of the alternative implementations of the second aspect or the second aspect, or the method of any of the foregoing third or third aspect, or any of the foregoing fourth or fourth aspects A method in an implementation, or a method in any of the possible implementations of the fifth or fifth aspect above.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • FIG. 2 shows a schematic block diagram of a method for transmitting data in an embodiment of the present application.
  • FIG. 3 shows another schematic block diagram of a method for transmitting data in an embodiment of the present application.
  • FIG. 4 shows still another schematic block diagram of a method for transmitting data in an embodiment of the present application.
  • FIG. 5 shows still another schematic block diagram of a method for transmitting data in an embodiment of the present application.
  • FIG. 6 shows still another schematic block diagram of a method for transmitting data in an embodiment of the present application.
  • FIG. 7 shows still another schematic block diagram of a method for transmitting data in an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a terminal device of an embodiment of the present application.
  • FIG. 9 shows a schematic block diagram of a network device of an embodiment of the present application.
  • FIG. 10 is another schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 11 is another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 12 shows still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 13 is still another schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 14 shows still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 15 is still another schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 16 shows still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 17 shows still another schematic block diagram of a network device according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the technical solutions of the embodiments of the present application can be applied to various communication systems based on non-orthogonal multiple access technologies, such as a sparse code multiple access (SCMA) system, and a low-density signature (Low). Density Signature (LDS) system, etc., of course, the SCMA system and the LDS system may also be referred to as other names in the communication field; further, the technical solution of the embodiment of the present application can be applied to multi-carrier using non-orthogonal multiple access technology.
  • SCMA sparse code multiple access
  • LDS Density Signature
  • Orthogonal Frequency Division Multiplexing OFDM
  • Filter Bank Multi-Carrier FBMC
  • General Frequency Division Multiplexing Generalized Frequency Division Multiplexing (OFDM)) Frequency Division Multiplexing (GFDM)
  • Filtered Orthogonal Frequency Division Multiplexing Filtered-OFDM, F-OFDM
  • FIG. 1 shows a wireless communication system 100 to which an embodiment of the present application is applied.
  • the wireless communication system 100 can include an access network device 110.
  • Access network device 110 may be a device that communicates with the terminal device.
  • Access network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices (e.g., UEs) located within the coverage area.
  • terminal devices e.g., UEs
  • the access network device 110 may be a Next Generation Radio Access Network (NG RAN), or a base station (gNB) in the NR system, or a cloud radio access network (Cloud Radio).
  • NG RAN Next Generation Radio Access Network
  • gNB base station
  • Cloud Radio cloud radio access network
  • the wireless controller in the Access Network, CRAN), or the access network device can be a relay station, an access point, an in-vehicle device, a wearable device, or a future evolved public land mobile network (Public Land) Network devices in the Mobile Network, PLMN).
  • the access network device 110 may also be a base station in an LTE system, for example, an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) device.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • the wireless communication system 100 also includes at least one terminal device 120 located within the coverage of the access network device 110.
  • Terminal device 120 can be mobile or fixed.
  • the terminal device 120 may refer to an access terminal, a user equipment (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, and a wireless communication.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • the wireless communication system 100 also includes a core network device 130 in communication with an access network device.
  • the core network device 130 may be a 5G core network device, for example, an Access and Mobility Management Function (AMF), and, for example, a Session Management Function (SMF).
  • the core network device 130 may also be an Evolved Packet Core (EPC) device of the LTE network, for example, a session management function + a core network side data gateway (Session Management Function+Core Packet Gateway, SMF+) PGW-C) equipment.
  • EPC Evolved Packet Core
  • SMF+PGW-C can simultaneously implement the functions that SMF and PGW-C can achieve.
  • the AMF may perform information interaction with the SMF.
  • the SMF obtains information on the radio access network side from the AMF.
  • the AMF may obtain the fallback identifier from the radio access network, or may be used to indicate that the first bearer/stream for the terminal device is not successfully established.
  • the wireless communication system 100 exemplarily shows an access network device, a core network device, and two terminal devices.
  • the wireless communication system 100 may include multiple access network devices and coverage of each access network device.
  • Other numbers of terminal devices may be included in the scope, which is not limited in this embodiment of the present application.
  • the wireless communication system 100 may further include a Mobile Management Entity (MME), a Unified Data Management (UDM), an Authentication Server Function (AUSF), and a user plane function (User).
  • MME Mobile Management Entity
  • UDM Unified Data Management
  • AUSF Authentication Server Function
  • User user plane function
  • Other network entities such as a Plane Function (UPF) and a Signaling Gateway (SGW), are not limited in this embodiment of the present application.
  • PPF Plane Function
  • SGW Signaling Gateway
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • FIG. 2 shows a schematic block diagram of a method 200 for transmitting data in an embodiment of the present application.
  • the terminal device shown in FIG. 2 may be a terminal device as shown in FIG. 1, and the network device shown in FIG. 2 may be a core network device as shown in FIG. 1.
  • the method 200 includes some or all of the following:
  • the terminal device sends a first request message to the network device, where the first request message is used to apply for session establishment of N data streams in the first protocol data unit PDU session.
  • the terminal device receives a response message of the first request message sent by the network device, where the response message is used to indicate that the network device refuses to perform the N data flows in the first PDU session.
  • the session of the M data streams is established, N and M are both positive integers, and N is greater than or equal to M.
  • the terminal device may send a non-access stratum to the core network device (Non-Access Stratum). (NAS) message
  • the NAS message may request to establish or modify a certain PDU session
  • the NAS message may carry an identifier (Identity, ID) of the PDU session
  • the core network device may know after receiving the NAS message.
  • the session in which the data flow is established in which PDU session.
  • a terminal device may have multiple PDU sessions.
  • the embodiment of the present application is directed to one of a plurality of PDU sessions of one terminal device.
  • the core network device may trigger the access network device to perform multiple data flows to be established or modified in the PDU session.
  • the access network device can further determine, according to the request, which data flows can be established in the PDU session, and the data flow cannot be established in the PDU session, and the access network device can further send a data flow to the core network device.
  • a list, the data flow list may be a data flow list accepted by the access network device, or may be a data flow list rejected by the access network device.
  • the core network device may send a response message to the terminal device, and notify the terminal device that the network device rejects part of the data stream in the requested data stream, and the terminal device rejects part of the data stream. After that, adjustment can be made accordingly, for example, the parameters for establishing the PDU session can be adjusted, or the session establishment of the rejected data stream can be re-initiated by changing the PDU session.
  • the method for transmitting data in the embodiment of the present application by feeding back the situation of session establishment to the terminal device, enables the terminal device to adjust the session establishment policy in time, thereby improving the performance of the communication system.
  • the embodiment of the present application may be applied to a 5G communication system, that is, the core network device in the embodiment of the present application may be an SMF in the 5G.
  • the SMF may interact with the UPF to establish a session.
  • the response message carries a reject reason value, where the reject reason value is used to indicate that the first PDU session does not support the M data streams.
  • the network side may refuse to establish one or more flows in one PDU session, which may be for various reasons, for example, PDU session may not be allowed, Radio Access Technology (RAT) access is not allowed, session Or the S-NSSAI error, the Data Network Name (DNN) is not supported, and the PDU session ID is not recognized.
  • the network side may carry the cause value in the response message sent to the terminal device.
  • the network side may pre-arrange with the terminal device to use several bits to indicate the foregoing various reasons, for example, may be used. 0001 indicates that the PDU session is not allowed, and 0010 indicates that the RAT access is not allowed or the like.
  • the PDU session is not allowed to be a PDU session full, and no data flow can be added in the PDU session.
  • the PDU session not allowed and the PDU session identifier can be regarded as being not supported by the PDU session.
  • the terminal device may perform appropriate adjustment on the PDU session, and initiate session establishment or modification to the network device again. In turn, the possibility of successful establishment of a PDU session can be improved.
  • the response message carries an identifier of each of the M data streams.
  • the network device may further indicate, by using the response message, which data streams are rejected by the network side, for example, the response message may carry a data flow list accepted by the network device, and the terminal device may be according to the accepted data flow list. Further, it can be determined which data streams are rejected. It is also possible to carry a list of data streams rejected by the network device directly in the response message.
  • the data flow list can include an identification of a plurality of data flows.
  • the terminal device After the terminal device knows which data streams are rejected, the terminal device can perform session adjustment on the rejected data streams in a targeted manner. The terminal device does not need to know which data it is. The flow is rejected, and once the reason for the rejection is known, the terminal device can make session adjustments for all data streams.
  • the method further includes: in response to the response message, the terminal device sends a second request message to the network device, where the second request message is used to apply for performing the M data streams in the second PDU session.
  • a session of at least one data stream is established.
  • the first request message carries an identifier of the first PDU session
  • the second request message carries an identifier of the second PDU session, where the second PDU session is an identifier after adjusting the identifier of the first PDU session.
  • the method before the responding to the response message, the method further includes: the terminal device adjusting, according to the M data streams, a setup parameter of the second PDU session that is not the first PDU session.
  • the terminal device can adjust the session establishment of the data flow. For example, if the terminal device knows that the identity of the previous PDU session is not recognized by the local network, the terminal device may generate a new identity and use the content of the previous PDU session to establish a session for the rejected data stream. Specifically, if the local network identifies the PDU session identifiers 1 to 100, and the identifier of the previous PDU session is 101, the local network cannot identify the PDU session identifier, and the network side can notify the terminal device that the PDU session identifier is not recognized.
  • the terminal device can generate a new PDU session identifier between 1 and 100, re-use the PDU session to initiate a session establishment or modification request, and carry the newly generated PDU session identifier in the request. For another example, if the terminal device knows that the previous PDU session does not allow the rejected data stream, the terminal device can bundle the rejected data stream into another PDU session, and initiate the PDU session establishment again. Specifically, the terminal device may modify a setup parameter of another PDU session, and associate the rejected data flow with the PDU session.
  • the response message carries an identifier of the second PDU session.
  • the network device may send the suggested PDU session to the terminal device, for example, the network device may directly carry the identifier of the suggested PDU session in the response message, if the network device determines that the data flow is rejected because the PDU session is not supported. . Or the network device determines that the identifier of the PDU session is not recognized, and the network device can identify the PDU session identifier to the terminal device.
  • the network device can send a suggested value of various parameters corresponding to the rejection reason value to the terminal device.
  • the embodiments of the present application are not limited thereto.
  • a flowchart of a method 300 for transmitting data in an embodiment of the present application will be described in detail below with reference to FIG.
  • the method is described by taking a 5G communication system as an example, and the method 300 includes the following or all of the contents:
  • the UE sends a first PDU session establishment or modification request to the SMF, where the NAS message carries the identifier of the first PDU session.
  • the SMF may interact with the UPF to establish a session.
  • the SMF may also trigger a radio access network (Radio Access Network, RAN) to perform a session establishment or modification request after receiving the first PDU session establishment or modification request.
  • RAN Radio Access Network
  • the RAN may reply to the SMF, and carry a flow list that is received or rejected.
  • the SMF may carry the refusal list by replying to the UE, and may be all rejected, or partially rejected, or may carry the recommended reason, and may also carry the recommended value, that is, The identifier of the proposed PDU session or suggested PDU session.
  • the UE may perform corresponding adjustment to re-initiate the establishment or modification of the PDU session. Specifically, the UE may send a request for establishing or modifying a second PDU session to the SMF, and may carry a new PDU session identifier (the PDU session identifier is not recognized), or may carry the identifier of the second PDU session (replace the PDU session). And the Flow that was previously rejected.
  • FIG. 4 shows a schematic block diagram of a method 400 for transmitting data in an embodiment of the present application. As shown in FIG. 4, the method 400 includes the following parts or all of the contents:
  • the network device receives a first request message sent by the terminal device, where the first request message is used to apply for session establishment of N data streams in the first protocol data unit PDU session.
  • the network device sends a response message of the first request message to the terminal device, where the response message is used to indicate that the network device rejects the session of the M data streams in the N data streams in the first PDU session.
  • N and M are both positive integers, and N is greater than or equal to M.
  • the method for transmitting data in the embodiment of the present application by feeding back the situation of session establishment to the terminal device, enables the terminal device to adjust the session establishment policy in time, thereby improving the performance of the communication system.
  • the response message carries a reject reason value, where the reject reason value is used to indicate that the first PDU session does not support the M data streams.
  • the response message carries an identifier of each of the M data streams.
  • the method further includes: receiving, by the network device, a second request message sent by the terminal device, where the second request message is used to apply for performing at least one of the M data streams in the second PDU session.
  • the session is established.
  • the response message carries an identifier of the second PDU session that is not recommended by the network device and is not the first PDU session.
  • the network device is a session management function SMF device, and the method further includes: the SMF device, according to the first request message, triggering the access network device to perform session establishment of the N data streams in the first PDU session.
  • the SMF device receives, by the SMF device, a data flow list corresponding to the first PDU session sent by the access network device, where the data flow list includes the M data flows or the N data flows received by the first PDU session ( NM) data streams.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be implemented in the present application.
  • the implementation of the examples constitutes any limitation.
  • FIG. 5 shows a schematic block diagram of a method 500 for transmitting data in an embodiment of the present application. As shown in FIG. 5, the method 500 includes the following parts or all of the contents:
  • the terminal device acquires the at least one rule according to the identifier of each rule in the at least one rule in the user equipment routing policy URSP.
  • the terminal device initiates establishment or modification of at least one protocol data unit PDU session corresponding to the at least one rule to the network device according to the at least one rule.
  • the concept of a UE Route Selection Policy (URSP) is introduced, and the URSP policy specifies a routing policy of the UE for different data flows.
  • Each terminal device has only one URSP.
  • Each URSP can have multiple rules.
  • the terminal device can initiate a PDU session establishment based on each rule.
  • the terminal device may initiate a PDU session establishment or modification based on one or more parameters in a certain rule.
  • the one or more parameters can be an access RAT, session or traffic continuity, network slicing or offloading, and the like.
  • the parameters in the rule can be measured by the core network and sent to the terminal device during the registration process of the terminal device, and the terminal device initiates the process of establishing or modifying the session.
  • the rule identifier can be introduced, so that the terminal device can obtain a certain rule according to the rule identifier, and the network device does not send all the rules to the terminal device at one time, thereby reducing the pressure on the network device and improving the pressure. Communication flexibility.
  • the at least one rule is a plurality of rules
  • the terminal device initiates, according to the multiple rules, the establishment or modification of a plurality of protocol data unit PDU sessions corresponding to the plurality of rules, respectively, to the network device, including: The terminal device initiates establishment or modification of the multiple PDU sessions to the network device according to the priority of the multiple rules.
  • multiple rules in the URSP may introduce a priority concept, that is, the terminal device may preferentially initiate establishment or modification of a PDU session corresponding to the rule to the network device based on a certain rule.
  • the terminal device can also classify multiple rules and prioritize each type of rule.
  • the PDU sessions initiated by the same type of rules can be sorted without any order, that is, the PDU session can be initiated in any order.
  • the priority level of each rule can be characterized by the identity of each rule. For example, once the terminal device obtains the rule #1, the terminal device can consider the rule #1 to have the highest priority.
  • the first rule in the at least one rule includes at least one of the following parameters: a radio access technology RAT, a session and a service continuity mode, and a single network slice assistance information.
  • S-NSSAI offload type
  • data network name DNN data network name DNN
  • data stream filter data network name DNN
  • Each rule in the URSP may include any combination of the foregoing various parameters, and the foregoing various parameters are merely illustrative, and the embodiments of the present application are not limited thereto. this.
  • the first parameter of the at least one parameter includes multiple values that represent the priority
  • the terminal device initiates establishment or modification of the first protocol data unit PDU session to the network device according to the first rule, including: The terminal device initiates establishment or modification of the first PDU session to the network device according to the priority of the multiple values.
  • the first rule may include an access RAT, a session and traffic continuity mode, and a single network slice assist information S-NSSAI, and the value of the access RAT is a 3rd Generation Partnership Project (3GPP). Access and Wireless Local Area Networks (WLAN) access.
  • the session and business continuity modes include mode 3 and mode 2, and the S-NSSAI includes S-NSSAI-a and S-NSSAI-b.
  • the values of the various parameters may be prioritized.
  • the access RAT may preferentially use 3GPP access
  • the S-NSSAI may preferentially use S-NSSAI-a
  • the session and service continuity mode may preferentially use mode 3.
  • the terminal device may randomly select a value of a parameter in a rule corresponding to the PDU session when the PDU session is initiated or modified for the first time.
  • the terminal device can also directly select the value of a certain parameter with a higher priority to improve the possibility of successful establishment of the PDU session. If the terminal device randomly selects a parameter value when the PDU session is initiated or modified for the first time, the terminal device may select the priority of the parameter when the network device rejects the PDU session request because the parameter does not meet the requirement. A higher value initiates the PDU session request again.
  • the terminal device initiates establishment or modification of the first protocol data unit PDU session to the network device according to the first rule in the at least one rule, where the terminal device sends the network protocol device to the network device according to the first rule.
  • a first request message the first request message is used to request the network device to perform session establishment of N data streams in the first PDU session; and the terminal device initiates a first PDU to the network device according to the first rule
  • the method further includes: receiving, by the terminal device, a response message of the first request message sent by the network device, where the response message is used to indicate that the network device refuses to perform the N in the first PDU session. Sessions of M data streams in each data stream are established, N and M are positive integers, and N is greater than or equal to M.
  • the response message carries a reject reason value, where the reject reason value is used to indicate at least one of the following situations: the PDU session is not supported, the RAT access is not allowed, the session or the service continuity mode is not satisfied, and the S- NSSAI errors, DNN not supported, and PDU session IDs are not recognized.
  • the network side may refuse to establish one or more flows in one PDU session, which may be for various reasons, for example, it may be that the PDU session is not allowed, the RAT access is not allowed, the session or service continuity mode is not satisfied, and S- The parameter in the rule corresponding to the PDU session in the URSP does not meet the requirements, and the PDU session identifier is not recognized.
  • the network side may carry the cause value in the response message sent to the terminal device. Specifically, the network side may pre-arrange with the terminal device to use several bits to indicate the foregoing various reasons, for example, may be used. 0001 indicates that the PDU session is not allowed, and 0010 indicates that the RAT access is not allowed or the like. Once the terminal device learns that a parameter in the corresponding rule in the URSP does not meet the requirement, the terminal device may adjust the value of the parameter.
  • the method further includes: adjusting, by the terminal device, a value of a parameter in the first rule corresponding to the reject reason value in response to the response message; the terminal device according to the adjusted first rule
  • the network device sends a second request message, where the second request message is used to request the network device to perform session establishment of at least one of the M data streams in the first PDU session. Standing.
  • the parameter of the first rule corresponding to the reject reason value includes multiple values that represent the priority
  • the terminal device adjusts the parameter of the first rule corresponding to the reject reason value in response to the response message.
  • the value includes: the terminal device adjusts, according to the response message, a value of the parameter of the first URSP corresponding to the reject reason value to a value higher than a value of the previous initiation of the first PDU session.
  • the response message carries the value of the parameter of the first rule that is recommended by the network device
  • the terminal device adjusts the first URSP corresponding to the reject reason value in response to the response message.
  • the value of the parameter includes: the terminal device adjusts a value of the parameter of the first rule corresponding to the reject reason value to a value of a parameter of the first rule that is recommended by the network device and corresponding to the reject reason value.
  • the terminal device after receiving the response message, performs the modification according to the recommended value if the network device carries the recommended value in the response message. If the recommended value is not carried, the parameter in the rule corresponding to the rejection reason value may be Adjust according to the priority of the parameter. For example, if the network device replies that the access RAT access is not satisfied, the terminal device may select a RAT with a higher priority to initiate the PDU session establishment again. If the network device replies that the access RAT access is not satisfied, and the recommended RAT access is carried in the reply as 3GPP access, the terminal device may directly initiate the PDU session establishment according to the 3GPP access.
  • the method further includes: the terminal device receiving, by the network device, a second rule of the URSP except the first rule in the at least one rule and an identifier of the first rule; the terminal device according to the first rule The first rule is obtained by the terminal device, after the second PDU session corresponding to the second rule is established, the first rule is obtained by the user plane according to the identifier of the first rule, or the terminal device The network device is triggered to send the first rule by using the control plane according to the identifier of the first rule.
  • the network device sends a URSP policy to the terminal device through a Policy Control Function (PCF).
  • PCF Policy Control Function
  • the method further includes: the terminal device receiving the identifier of the server; after the second PDU session corresponding to the second rule is established, the terminal device acquires the first part by using the user plane according to the identifier of the first rule
  • the rule includes: after the second PDU session corresponding to the second rule is established, the terminal device acquires the first rule by using a user plane according to the identifier of the first rule and the identifier of the server.
  • the second rule has a higher priority than the first rule.
  • the PCF may not be completely sent to the terminal device through a signaling message, and then the PCF may batch-subscribe to the terminal device through the control plane.
  • a plurality of rules in the URSP are sent, for example, a plurality of rules can be grouped, and a set of rules is sent by each of the messages, or the plurality of rules can be prioritized and sent in batches with high priority.
  • the terminal device may also send the identifier of the required rule to the PCF after receiving the batch of rules each time. Specifically, if the PCF first sends the rules 1 and 2 to the terminal device, the terminal device may send the PCF to the PCF. The identification of rules 3 and 4 is fed back so that the PCF sends rule 3 and rule 4 to the terminal device again.
  • the PCF may also send a part of the rule to the terminal device first, and carry the identifier of another part of the rule. After the terminal device establishes the user plane according to a part of the rule, the terminal device may acquire the user face according to the identifier of another part of the rule. Further, the PCF may also send the identifier of the server that stores another part of the rule to the terminal device. After the terminal device establishes the user plane according to the part of the rule, the terminal device may obtain another part in the corresponding server of the user plane according to the identifier of another part of the rule. rule.
  • the terminal device separately obtains the at least one rule according to the identifier of each rule in the at least one rule of the user equipment routing policy URSP, including: in the process of performing network registration by the terminal device, the terminal device according to the at least An identifier of each rule in a rule to obtain the at least one rule.
  • FIG. 6 shows a schematic block diagram of a method 600 for transmitting data in an embodiment of the present application. As shown in FIG. 6, the method 600 includes the following parts or all of the contents:
  • the network device sends, by using multiple messages, multiple rules in the user equipment routing policy URSP to the terminal device.
  • the method for transmitting data in the embodiment of the present application can effectively reduce the network pressure and improve the communication flexibility by acquiring the URSP policy in batches.
  • the network device sends the multiple rules in the user equipment routing policy URSP to the terminal device by using a plurality of messages, including: in the process of performing network registration by the terminal device, The network device sends the multiple rules to the terminal device through multiple messages of the control plane according to the priorities of the multiple rules.
  • the network device is a policy control function PCF.
  • FIG. 7 shows a schematic block diagram of a method 700 for transmitting data in an embodiment of the present application. As shown in FIG. 7, the method 700 includes the following parts or all of the contents:
  • the network device in the process of performing network registration by the terminal device, the network device sends, to the terminal device, a second rule of the user equipment routing policy URSP except the first rule, and an identifier of the first rule, so that the terminal device is in the After the second PDU session corresponding to the second rule is established, the first rule is obtained by the user plane according to the identifier of the first rule.
  • the method for transmitting data in the embodiment of the present application can effectively reduce the network pressure and improve the communication flexibility by acquiring the URSP policy in batches.
  • the method further includes: the network device sending the identifier of the server to the terminal device, so that the terminal device, according to the second PDU session corresponding to the second rule, according to the identifier of the first rule The identifier of the server, obtained by the user plane.
  • the network device is a policy control function PCF.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be implemented in the present application.
  • the implementation of the examples constitutes any limitation.
  • FIG. 8 shows a schematic block diagram of a terminal device 800 of an embodiment of the present application. As shown in FIG. 8, the terminal device 800 includes:
  • the sending unit 810 is configured to send, to the network device, a first request message, where the first request message is used to apply for session establishment of N data flows in the first protocol data unit PDU session;
  • the receiving unit 820 is configured to receive a response message of the first request message sent by the network device, where the response message is used to indicate that the network device refuses to perform M data flows in the N data streams in the first PDU session.
  • the session is established, N and M are both positive integers, and N is greater than or equal to M.
  • the terminal device in the embodiment of the present application by receiving the session establishment situation fed back by the network device, enables the terminal device to adjust the session establishment policy in time, thereby facilitating High communication system performance.
  • the response message carries a reject reason value, where the reject reason value is used to indicate that the first PDU session does not support the M data streams.
  • the response message carries an identifier of each of the M data streams.
  • the sending unit is further configured to: send, in response to the response message, a second request message to the network device, where the second request message is used to apply for performing at least one of the M data streams in the second PDU session.
  • a session of a data stream is established.
  • the first request message carries an identifier of the first PDU session
  • the second request message carries an identifier of the second PDU session, where the second PDU session is an identifier after adjusting the identifier of the first PDU session.
  • the terminal device before the terminal device is responsive to the response message, the terminal device further includes: a processing unit, configured to adjust, according to the M data streams, a setup parameter of the second PDU session that is not the first PDU session.
  • a processing unit configured to adjust, according to the M data streams, a setup parameter of the second PDU session that is not the first PDU session.
  • the response message carries an identifier of the second PDU session.
  • the network device is a session management function SMF device.
  • terminal device 800 may correspond to the terminal device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the terminal device 800 respectively implement FIG. 2 and FIG. 3 .
  • the corresponding process of the terminal device in the method is not described here for brevity.
  • FIG. 9 shows a schematic block diagram of a network device 900 in accordance with an embodiment of the present application.
  • the network device 900 includes:
  • the receiving unit 910 is configured to receive a first request message sent by the terminal device, where the first request message is used to apply for session establishment of N data streams in the first protocol data unit PDU session;
  • the sending unit 920 is configured to send, to the terminal device, a response message of the first request message, where the response message is used to indicate that the network device refuses to perform M data streams in the N data streams in the first PDU session.
  • Session establishment, N and M are both positive integers, and N is greater than or equal to M.
  • the network device in the embodiment of the present application by feeding back the session establishment to the terminal device, enables the terminal device to adjust the session establishment policy in time, thereby improving the performance of the communication system.
  • the response message carries a reject reason value, where the reject reason value is used to indicate that the first PDU session does not support the M data streams.
  • the response message carries an identifier of each of the M data streams.
  • the receiving unit is further configured to receive a second request message sent by the terminal device, where the second request message is used to apply for performing a session of at least one of the M data streams in the second PDU session. set up.
  • the response message carries an identifier of the second PDU session that is not recommended by the network device and is not the first PDU session.
  • the network device is a session management function SMF device, and the network device further includes: a processing unit, configured to trigger, according to the first request message, the access network device to perform the N data flows in the first PDU session.
  • the receiving unit is further configured to receive, by the access network device, a data flow list corresponding to the first PDU session, where the data flow list includes the M data streams or the first PDU session received (NM) data streams in N data streams.
  • the network device 900 may correspond to the network device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the network device 900 respectively implement the network in the method of FIG. The corresponding process of the device is not described here for brevity.
  • FIG. 10 shows a schematic block diagram of a terminal device 1000 of an embodiment of the present application.
  • the terminal device 1000 includes:
  • the processing unit 1100 is configured to separately acquire the at least one rule according to the identifier of each rule in the at least one rule in the user equipment routing policy URSP.
  • the processing unit 1100 is further configured to initiate, according to the at least one rule, the establishment or modification of at least one protocol data unit PDU session corresponding to the at least one rule to the network device.
  • the terminal device in the embodiment of the present invention can obtain a certain rule according to the rule identifier, and the network device does not send all the rules to the terminal device at one time, which reduces the pressure on the network device and improves the communication flexibility.
  • the at least one rule is a plurality of rules
  • the processing unit is specifically configured to: initiate, according to the priorities of the multiple rules, the establishment or modification of the multiple PDU sessions to the network device.
  • the first rule in the at least one rule includes at least one of the following parameters: a radio access technology RAT, a session and a service continuity mode, a single network slice assist information S-NSSAI, a split type, a data network Name DNN and data stream filter.
  • the first parameter of the at least one parameter includes a plurality of values characterizing the priority
  • the processing unit is specifically configured to: initiate, according to the priority of the multiple values, the establishment or modification of the first PDU session to the network device.
  • the processing unit is further configured to send, according to the first rule, a first request message to the network device, where the first request message is used to request the network device to perform N data flows in the first PDU session.
  • the session is established; after the processing unit initiates the establishment or modification of the first PDU session to the network device according to the first rule, the terminal device further includes: a receiving unit, configured to receive the first request message sent by the network device The response message is used to indicate that the network device refuses to perform session establishment of M data streams in the N data streams in the first PDU session, where N and M are positive integers, and N is greater than or equal to M .
  • the response message carries a reject reason value, where the reject reason value is used to indicate at least one of the following situations: the PDU session is not supported, the RAT access is not allowed, the session or the service continuity mode is not satisfied, and the S- NSSAI errors, DNN not supported, and PDU session IDs are not recognized.
  • the terminal device further includes: the processing unit is further configured to: adjust, according to the response message, a value of a parameter in the first rule corresponding to the reject reason value; and send, by the sending unit, according to the adjusted The first rule is to send a second request message to the network device, where the second request message is used to request the network device to perform session establishment of at least one of the M data streams in the first PDU session.
  • the parameter of the first rule corresponding to the reject reason value includes multiple values representing a priority
  • the processing unit is further configured to: in response to the response message, the first URSP corresponding to the reject reason value The value of the parameter is adjusted to a higher priority than the value of the previous initiation of the first PDU session.
  • the response message carries a value of the parameter of the first rule that is recommended by the network device
  • the processing unit adjusts the first URSP corresponding to the reject reason value in response to the response message.
  • the value of the parameter includes: the processing unit adjusts a value of the parameter of the first rule corresponding to the reject reason value to a value of a parameter of the first rule that is recommended by the network device and corresponding to the reject reason value.
  • the terminal device further includes: a receiving unit, configured to receive, by the network device, a second rule of the URSP except the first rule of the at least one rule and an identifier of the first rule;
  • the identifier of the first rule, the first rule is obtained, including:
  • the processing unit After the processing unit establishes the second PDU session corresponding to the second rule, the first rule is obtained by the user plane according to the identifier of the first rule, or the processing unit is configured according to the first rule
  • the identifier of the network triggers the network device to deliver the first rule by using a control plane.
  • the receiving unit is further configured to receive an identifier of the server.
  • the processing unit obtains the first rule by using a user plane according to the identifier of the first rule.
  • the processing unit acquires the first rule by using a user plane according to the identifier of the first rule and the identifier of the server.
  • the second rule has a higher priority than the first rule.
  • the processing unit separately acquires the at least one rule according to the identifier of each rule in the at least one rule of the user equipment routing policy URSP, including: in the process of performing network registration by the terminal device, the processing unit is configured according to the The identifier of each rule in at least one rule acquires the at least one rule.
  • terminal device 1000 may correspond to the terminal device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the terminal device 1000 respectively implement the terminal in the method of FIG.
  • the corresponding process of the device is not described here for brevity.
  • FIG. 11 shows a schematic block diagram of a network device 2000 of an embodiment of the present application.
  • the network device 2000 includes:
  • the sending unit 2100 is configured to send, in the process of performing network registration by the terminal device, multiple rules in the user equipment routing policy URSP to the terminal device by using multiple messages.
  • the network device in the embodiment of the present application can effectively reduce the network pressure and improve the communication flexibility by acquiring the URSP policy in batches.
  • the processing unit is specifically configured to: in the process of performing network registration by the terminal device, sequentially, according to the priority of the multiple rules, sequentially send multiple messages to the control plane
  • the terminal device sends the plurality of rules.
  • the network device is a policy control function PCF.
  • the network device 2000 may correspond to the terminal device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the network device 2000 respectively implement the terminal in the method of FIG.
  • the corresponding process of the device is not described here for brevity.
  • FIG. 12 shows a schematic block diagram of a network device 3000 of an embodiment of the present application. As shown in FIG. 12, the network device 3000 includes:
  • the sending unit 3100 is configured to send, to the terminal device, a second rule in the user equipment routing policy URSP, except the first rule, and an identifier of the first rule, in the process of performing network registration, to facilitate the terminal.
  • the first rule is obtained by the user plane according to the identifier of the first rule.
  • the network device in the embodiment of the present application can effectively reduce the network pressure and improve the communication flexibility by acquiring the URSP policy in batches.
  • the sending unit is further configured to send the identifier of the server to the terminal device, so that after the terminal device establishes the second PDU session corresponding to the second rule, according to the identifier of the first rule, the server The identity of the first rule is obtained through the user face.
  • the network device is a policy control function PCF.
  • the network device 3000 may correspond to the terminal device in the method embodiment of the present application, and the foregoing and other operations and/or functions of the respective units in the network device 3000 respectively implement the terminal in the method of FIG.
  • the corresponding process of the device is not described here for brevity.
  • the embodiment of the present application further provides a terminal device 4000, which may be the terminal device 800 in FIG. 8 , which can be used to execute the content of the terminal device corresponding to the method 200 in FIG. 2 .
  • the terminal device 4000 includes an input interface 4010, an output interface 4020, a processor 4030, and a memory 4040.
  • the input interface 4010, the output interface 4020, the processor 4030, and the memory 4040 can be connected by a bus system.
  • the memory 4040 is for storing programs, instructions or code.
  • the processor 4030 is configured to execute a program, an instruction or a code in the memory 4040 to control the input interface 4010 to receive a signal, control the output interface 4020 to transmit a signal, and complete the operations in the foregoing method embodiments.
  • the terminal device in the embodiment of the present application can adjust the session establishment policy in time by receiving the session establishment feedback fed back by the network device, thereby facilitating the performance of the communication system.
  • the processor 4030 may be a central processing unit (CPU), and the processor 4030 may also be other general-purpose processors, digital signal processors, application specific integrated circuits, and ready-made Program gate arrays or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and more.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 4040 can include a read only memory and a random access memory, and is directed to the processor The 4030 provides instructions and data.
  • a portion of the memory 4040 can also include a non-volatile random access memory.
  • the memory 4040 can also store information of the device type.
  • each content of the above method may be completed by an integrated logic circuit of hardware in the processor 4030 or an instruction in a form of software.
  • the content of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 4040, and the processor 4030 reads the information in the memory 4040 and combines the hardware to complete the contents of the above method. To avoid repetition, it will not be described in detail here.
  • the transmitting unit in the terminal device 800 can be implemented by the output interface 4020 in FIG. 13, and the receiving unit in the terminal device 800 can be implemented by the input interface 4010 in FIG.
  • the embodiment of the present application further provides a network device 5000, which may be the network device 900 in FIG. 9, which can be used to execute the content of the network device corresponding to the method 400 in FIG. .
  • the network device 5000 includes an input interface 5010, an output interface 5020, a processor 5030, and a memory 5040.
  • the input interface 5010, the output interface 5020, the processor 5030, and the memory 5040 can be connected by a bus system.
  • the memory 5040 is for storing programs, instructions or code.
  • the processor 5030 is configured to execute a program, an instruction, or a code in the memory 5040 to control the input interface 5010 to receive a signal, control the output interface 5020 to transmit a signal, and perform operations in the foregoing method embodiments.
  • the network device in the embodiment of the present application by feeding back the session establishment to the terminal device, enables the terminal device to adjust the session establishment policy in time, thereby improving the performance of the communication system.
  • the processor 5030 may be a central processing unit (CPU), and the processor 5030 may also be other general-purpose processors, digital signal processors, application specific integrated circuits, ready-made Program gate arrays or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and more.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 5040 can include read only memory and random access memory and provides instructions and data to the processor 5030. A portion of the memory 5040 can also include a non-volatile random access memory. For example, the memory 5040 can also store information of the device type.
  • each content of the above method may be completed by an integrated logic circuit of hardware in the processor 5030 or an instruction in a form of software.
  • the content of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 5040, and the processor 5030 reads the information in the memory 5040 and combines the hardware to complete the contents of the above method. To avoid repetition, it will not be described in detail here.
  • the transmitting unit in the network device 900 can be implemented by the output interface 5020 in FIG. 14, and the receiving unit in the network device 900 can be implemented by the input interface 5010 in FIG.
  • the embodiment of the present application further provides a terminal device 6000, which may be the terminal device 1000 in FIG. 10, which can be used to execute the content of the terminal device corresponding to the method 500 in FIG. .
  • the terminal device 6000 includes an input interface 6010, an output interface 6020, a processor 6030, and a memory 6060.
  • the input interface 6010, the output interface 6020, the processor 6030, and the memory 6060 can be connected by a bus system.
  • the memory 6060 is for storing programs, instructions or code.
  • the processor 6030 is configured to execute a program, an instruction or a code in the memory 6060 to control the input interface 6010 to receive a signal, control the output interface 6020 to transmit a signal, and complete the operations in the foregoing method embodiments.
  • the terminal device in the embodiment of the present application can obtain a certain rule according to the rule identifier, and the network device does not send all the rules to the terminal device at one time, thereby reducing the pressure on the network device and improving the communication flexibility. .
  • the processor 6030 may be a central processing unit (CPU), and the processor 6030 may also be other general-purpose processors, digital signal processors, application specific integrated circuits, and ready-made Program gate arrays or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and more.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 6060 can include read only memory and random access memory and provides instructions and data to the processor 6030.
  • a portion of the memory 6060 can also include a non-volatile random access memory.
  • the memory 6060 can also store information of the device type.
  • each content of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 6030 or an instruction in a form of software. Incorporating the method disclosed in the embodiment of the present application
  • the capacity can be directly implemented as a hardware processor execution, or by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 6060, and the processor 6030 reads the information in the memory 6060 and combines the hardware to complete the contents of the above method. To avoid repetition, it will not be described in detail here.
  • the processing unit in the terminal device 1000 can be implemented by the processor 6030 in FIG.
  • the embodiment of the present application further provides a network device 7000, which may be the network device 2000 in FIG. 11, which can be used to execute the content of the network device corresponding to the method 600 in FIG. .
  • the network device 7000 includes an input interface 7010, an output interface 7020, a processor 7030, and a memory 7040.
  • the input interface 7010, the output interface 7020, the processor 7030, and the memory 7040 can be connected by a bus system.
  • the memory 7040 is for storing programs, instructions or codes.
  • the processor 7030 is configured to execute a program, an instruction or a code in the memory 7040 to control the input interface 7010 to receive a signal, control the output interface 7020 to send a signal, and complete the operations in the foregoing method embodiments.
  • the network device in the embodiment of the present application can effectively reduce the network pressure and improve the communication flexibility by acquiring the URSP policy in batches.
  • the processor 7030 may be a central processing unit (CPU), and the processor 7030 may also be other general-purpose processors, digital signal processors, application specific integrated circuits, and ready-made Program gate arrays or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and more.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 7040 can include read only memory and random access memory and provides instructions and data to the processor 7030. A portion of the memory 7040 can also include a non-volatile random access memory. For example, the memory 7040 can also store information of the device type.
  • each content of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 7030 or an instruction in a form of software.
  • the content of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 7040, and the processor 7030 reads the information in the memory 7040.
  • the content of the above method is completed in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the transmitting unit in the network device 2000 can be implemented by the output interface 7020 in FIG.
  • the embodiment of the present application further provides a network device 8000, which may be the network device 3000 in FIG. 12, which can be used to execute the content of the network device corresponding to the method 700 in FIG. .
  • the network device 8000 includes an input interface 8010, an output interface 8020, a processor 8030, and a memory 8040.
  • the input interface 8010, the output interface 8020, the processor 8030, and the memory 8040 can be connected by a bus system.
  • the memory 8040 is for storing programs, instructions or code.
  • the processor 8030 is configured to execute a program, an instruction, or a code in the memory 8040 to control the input interface 8010 to receive a signal, control the output interface 8020 to transmit a signal, and perform operations in the foregoing method embodiments.
  • the network device in the embodiment of the present application can effectively reduce the network pressure and improve the communication flexibility by acquiring the URSP policy in batches.
  • the processor 8030 may be a central processing unit (CPU), and the processor 8030 may also be other general-purpose processors, digital signal processors, application specific integrated circuits, and ready-made Program gate arrays or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and more.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 8040 can include read only memory and random access memory and provides instructions and data to the processor 8030.
  • a portion of the memory 8040 can also include a non-volatile random access memory.
  • the memory 8040 can also store information of the device type.
  • each content of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 8030 or an instruction in a form of software.
  • the content of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 8040, and the processor 8030 reads the information in the memory 8040 and combines its hardware to complete the contents of the above method. To avoid repetition, it will not be described in detail here.
  • the transmitting unit in the network device 3000 can be implemented by the output interface 8020 in FIG.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application 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.
  • This functionality if implemented as a software functional unit and sold or used as a standalone product, can be stored on a computer readable storage medium.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例公开了一种用于传输数据的方法、终端设备和网络设备，该方法包括：终端设备向网络设备发送第一请求消息，该第一请求消息用于申请在第一协议数据单元PDU会话中进行N个数据流的会话建立；该终端设备接收该网络设备发送的该第一请求消息的响应消息，该响应消息用于指示该网络设备拒绝在该第一PDU会话中进行该N个数据流中的M个数据流的会话建立，N和M均为正整数，且N大于或等于M。本申请实施例的方法、终端设备和网络设备，有利于提高通信系统的性能。

Description

用于传输数据的方法、终端设备和网络设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种用于传输数据的方法、终端设备和网络设备。
背景技术
在无线通信网络中，终端设备需要完成协议数据单元(Protocol Data Unit，PDU)会话的建立过程才可以进行相关的业务。现有技术中，当终端设备向网络设备发起会话建立过程之后，终端设备无法获知该会话建立的情况，使得终端设备不能及时地对会话建立策略进行调整，影响了通信系统的性能。
发明内容
有鉴于此，本申请实施例提供了一种用于传输数据的方法、终端设备和网络设备，有利于提高通信系统的性能。
第一方面，提供了一种用于传输数据的方法，该方法包括：终端设备向网络设备发送第一请求消息，该第一请求消息用于申请在第一协议数据单元PDU会话中进行N个数据流的会话建立；该终端设备接收该网络设备发送的该第一请求消息的响应消息，该响应消息用于指示该网络设备拒绝在该第一PDU会话中进行该N个数据流中的M个数据流的会话建立，N和M均为正整数，且N大于或等于M。
通过网络设备向终端设备反馈会话建立的情况，使得终端设备能够及时地对会话建立策略进行调整，从而有利于提高通信系统的性能。
在一种可能的实现方式中，该响应消息携带拒绝原因值，该拒绝原因值用于指示该第一PDU会话不支持该M个数据流。
通过在响应消息中携带拒绝原因值，使得当终端设备根据响应消息获知是由于PDU会话不支持的原因，终端设备可以对PDU会话进行适当的调整，再次向网络设备发起会话建立或修改。进而可以提高PDU会话建立成功的可能性。
在一种可能的实现方式中，该响应消息携带该M个数据流中每个数据 流的标识。
在一种可能的实现方式中，该方法还包括：该终端设备响应于该响应消息，向该网络设备发送第二请求消息，该第二请求消息用于申请在第二PDU会话中进行该M个数据流中的至少一个数据流的会话建立。
在一种可能的实现方式中，该第一请求消息携带该第一PDU会话的标识，该第二请求消息携带该第二PDU会话的标识，该第二PDU会话为调整该第一PDU会话的标识之后的该第一PDU会话。
在一种可能的实现方式中，该终端设备响应于该响应消息之前，该方法还包括：该终端设备根据该M个数据流，调整非该第一PDU会话的该第二PDU会话的建立参数。
在一种可能的实现方式中，该响应消息携带该第二PDU会话的标识。
在一种可能的实现方式中，该网络设备为会话管理功能SMF设备。
第二方面，提供了一种用于传输数据的方法，包括：网络设备接收终端设备发送的第一请求消息，该第一请求消息用于申请在第一协议数据单元PDU会话中进行N个数据流的会话建立；该网络设备向该终端设备发送该第一请求消息的响应消息，该响应消息用于指示该网络设备拒绝在该第一PDU会话中进行该N个数据流中的M个数据流的会话建立，N和M均为正整数，且N大于或等于M。
在一种可能的实现方式中，该响应消息携带拒绝原因值，该拒绝原因值用于指示该第一PDU会话不支持该M个数据流。
在一种可能的实现方式中，该响应消息携带该M个数据流中每个数据流的标识。
在一种可能的实现方式中，该方法还包括：该网络设备接收该终端设备发送的第二请求消息，该第二请求消息用于申请在第二PDU会话中进行该M个数据流中的至少一个数据流的会话建立。
在一种可能的实现方式中，该响应消息携带该网络设备建议的非该第一PDU会话的该第二PDU会话的标识。
在一种可能的实现方式中，该网络设备为会话管理功能SMF设备，该方法还包括：该SMF设备根据该第一请求消息，触发接入网设备在该第一PDU会话中进行该N个数据流的会话建立；该SMF设备接收该接入网设备发送的与该第一PDU会话对应的数据流列表，该数据流列表包括该M 个数据流或该第一PDU会话接收的该N个数据流中的(N-M)个数据流。
第三方面，提供了一种用于传输数据的方法，包括：终端设备根据用户设备路由选择策略URSP中至少一个规则中每个规则的标识，分别获取该至少一个规则；该终端设备根据该至少一个规则，分别向网络设备发起与该至少一个规则一一对应的至少一个协议数据单元PDU会话的建立或修改。
通过引入规则标识，使得终端设备可以根据规则标识来获取某一规则，而不再是网络设备一次性将所有规则下发给终端设备，减轻了网络设备的压力，并且提高了通信灵活性。
在一种可能的实现方式中，该至少一个规则为多个规则，该终端设备根据该多个规则，分别向网络设备发起与该多个规则一一对应的多个协议数据单元PDU会话的建立或修改，包括：该终端设备根据该多个规则的优先级，依次向该网络设备发起该多个PDU会话的建立或修改。
可选地，可以由每个规则的标识来表征每个规则的优先等级。
在一种可能的实现方式中，该至少一个规则中的第一规则包括以下参数中的至少一种参数：无线接入技术RAT、会话和业务连续性模式、单网络切片辅助信息S-NSSAI、分流类型、数据网络名称DNN和数据流过滤器。
在一种可能的实现方式中，该至少一种参数中的第一参数包括表征优先级的多个值，该终端设备根据该第一规则，向网络设备发起第一协议数据单元PDU会话的建立或修改，包括：该终端设备根据该多个值的优先级，向该网络设备发起第一PDU会话的建立或修改。
在一种可能的实现方式中，该终端设备根据该至少一个规则中的第一规则，向网络设备发起第一协议数据单元PDU会话的建立或修改，包括：该终端设备根据该第一规则，向该网络设备发送第一请求消息，该第一请求消息用于请求该网络设备在该第一PDU会话中进行N个数据流的会话建立；在该终端设备根据该第一规则，向该网络设备发起第一PDU会话的建立或修改之后，该方法还包括：该终端设备接收该网络设备发送的该第一请求消息的响应消息，该响应消息用于指示该网络设备拒绝在该第一PDU会话中进行该N个数据流中的M个数据流的会话建立，N和M均为正整数，N大于或等于M。
在一种可能的实现方式中，该响应消息携带拒绝原因值，该拒绝原因值 用于指示以下情况中的至少一种情况：PDU会话不支持、RAT接入不允许、会话或业务连续性模式不满足、S-NSSAI错误、DNN不支持和PDU会话标识不被识别。
在一种可能的实现方式中，该方法还包括：该终端设备响应于该响应消息，调整与该拒绝原因值对应的该第一规则中的参数的值；该终端设备根据调整后的该第一规则，向该网络设备发送第二请求消息，该第二请求消息用于请求该网络设备在第一PDU会话中进行该M个数据流中的至少一个数据流的会话建立。
在一种可能的实现方式中，与该拒绝原因值对应的该第一规则的参数包括表征优先级的多个值，该终端设备响应于该响应消息，调整与该拒绝原因值对应的该第一规则的参数的值，包括：该终端设备响应于该响应消息，将与该拒绝原因值对应的该第一URSP的参数的值调整为优先级高于前一次发起第一PDU会话建立的值。
在一种可能的实现方式中，该响应消息携带该网络设备建议的与该拒绝原因值对应的该第一规则的参数的值，该终端设备响应于该响应消息，调整与该拒绝原因值对应的该第一URSP的参数的值，包括：该终端设备将与该拒绝原因值对应的该第一规则的参数的值调整为该网络设备建议的与该拒绝原因值对应的该第一规则的参数的值。
在一种可能的实现方式中，该方法还包括：该终端设备接收该网络设备发送的该URSP中除该至少一个规则中第一规则外的第二规则以及该第一规则的标识；该终端设备根据第一规则的标识，获取该第一规则，包括：该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识，通过用户面获取该第一规则，或该终端设备根据该第一规则的标识，触发该网络设备通过控制面将该第一规则下发。
在一种可能的实现方式中，该方法还包括：该终端设备接收服务器的标识；该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识，通过用户面获取该第一规则，包括：该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识和该服务器的标识，通过用户面获取该第一规则。
在一种可能的实现方式中，该第二规则的优先级高于该第一规则的优先级。
在一种可能的实现方式中，终端设备根据用户设备路由选择策略URSP中至少一个规则中每个规则的标识，分别获取该至少一个规则，包括：在该终端设备进行网络注册的过程中，该终端设备根据该至少一个规则中每个规则的标识，获取该至少一个规则。
第四方面，提供了一种用于传输数据的方法，该方法包括：在终端设备进行网络注册的过程中，网络设备通过多条消息向该终端设备发送用户设备路由选择策略URSP中的多个规则。
通过分批次获取URSP策略，可以有效地降低网络压力，提高通信灵活性。
在一种可能的实现方式中，该在终端设备进行网络注册的过程中，网络设备通过多条消息向该终端设备发送用户设备路由选择策略URSP中的多个规则，包括：在终端设备进行网络注册的过程中，该网络设备根据该多个规则的优先级，依次通过控制面的多条消息向该终端设备发送该多个规则。
在一种可能的实现方式中，该网络设备为策略控制功能PCF设备。
第五方面，提供了一种用于传输数据的方法，该方法包括：在终端设备进行网络注册的过程中，网络设备向该终端设备发送用户设备路由选择策略URSP中除第一规则之外的第二规则和该第一规则的标识，以便于该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识，通过用户面获取该第一规则。
通过分批次获取URSP策略，可以有效地降低网络压力，提高通信灵活性。
在一种可能的实现方式中，该方法还包括：该网络设备向该终端设备发送服务器的标识，以便于该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识和该服务器的标识，通过用户面获取该第一规则。
在一种可能的实现方式中，该网络设备为策略控制功能PCF设备。
第六方面，提供了一种终端设备，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该终端设备包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元。
第七方面，提供了一种网络设备，用于执行上述第二方面或第二方面的 任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的单元。
第八方面，提供了一种终端设备，用于执行上述第三方面或第三方面的任意可能的实现方式中的方法。具体地，该终端设备包括用于执行上述第三方面或第三方面的任意可能的实现方式中的方法的单元。
第九方面，提供了一种网络设备，用于执行上述第四方面或第四方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第四方面或第四方面的任意可能的实现方式中的方法的单元。
第十方面，提供了一种网络设备，用于执行上述第五方面或第五方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第五方面或第五方面的任意可能的实现方式中的方法的单元。
第十一方面，提供了一种终端设备，该终端设备包括：存储器、处理器、输入接口和输出接口。其中，存储器、处理器、输入接口和输出接口通过总线系统相连。该存储器用于存储指令，该处理器用于执行该存储器存储的指令，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第十二方面，提供了一种网络设备，该网络设备包括：存储器、处理器、输入接口和输出接口。其中，存储器、处理器、输入接口和输出接口通过总线系统相连。该存储器用于存储指令，该处理器用于执行该存储器存储的指令，用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第十三方面，提供了一种终端设备，该终端设备包括：存储器、处理器、输入接口和输出接口。其中，存储器、处理器、输入接口和输出接口通过总线系统相连。该存储器用于存储指令，该处理器用于执行该存储器存储的指令，用于执行上述第三方面或第三方面的任意可能的实现方式中的方法。
第十四方面，提供了一种网络设备，该网络设备包括：存储器、处理器、输入接口和输出接口。其中，存储器、处理器、输入接口和输出接口通过总线系统相连。该存储器用于存储指令，该处理器用于执行该存储器存储的指令，用于执行上述第四方面或第四方面的任意可能的实现方式中的方法。
第十五方面，提供了一种网络设备，该网络设备包括：存储器、处理器、输入接口和输出接口。其中，存储器、处理器、输入接口和输出接口通过总线系统相连。该存储器用于存储指令，该处理器用于执行该存储器存储的指令，用于执行上述第五方面或第五方面的任意可能的实现方式中的方法。
第十六方面，提供了一种计算机存储介质，用于储存为执行上述第一方面或第一方面的任意可能的实现方式中的方法，或者上述第二方面或第二方面的任意可能的实现方式中的方法，或者上述第三方面或第三方面的任意可能的实现方式中的方法，或者上述第四方面或第四方面的任意可能的实现方式中的方法，或者上述第五方面或第五方面的任意可能的实现方式中的方法所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
第十七方面，提供了一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面的任一可选的实现方式中的方法，或者上述第二方面或第二方面的任一可选的实现方式中的方法，或者上述第三方面或第三方面的任意可能的实现方式中的方法，或者上述第四方面或第四方面的任意可能的实现方式中的方法，或者上述第五方面或第五方面的任意可能的实现方式中的方法。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1示出了本申请实施例一个应用场景的示意图。
图2示出了本申请实施例的用于传输数据的方法的示意性框图。
图3示出了本申请实施例的用于传输数据的方法的另一示意性框图。
图4示出了本申请实施例的用于传输数据的方法的再一示意性框图。
图5示出了本申请实施例的用于传输数据的方法的再一示意性框图。
图6示出了本申请实施例的用于传输数据的方法的再一示意性框图。
图7示出了本申请实施例的用于传输数据的方法的再一示意性框图。
图8示出了本申请实施例的终端设备的示意性框图。
图9示出了本申请实施例的网络设备的示意性框图。
图10示出了本申请实施例的终端设备的另一示意性框图。
图11示出了本申请实施例的网络设备的另一示意性框图。
图12示出了本申请实施例的网络设备的再一示意性框图。
图13示出了本申请实施例的终端设备的再一示意性框图。
图14示出了本申请实施例的网络设备的再一示意性框图。
图15示出了本申请实施例的终端设备的再一示意性框图。
图16示出了本申请实施例的网络设备的再一示意性框图。
图17示出了本申请实施例的网络设备的再一示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
应理解，本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、LTE系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、新无线(New Radio，NR)或未来的5G系统等。
特别地，本申请实施例的技术方案可以应用于各种基于非正交多址接入技术的通信系统，例如稀疏码多址接入(Sparse Code Multiple Access，SCMA)系统、低密度签名(Low Density Signature，LDS)系统等，当然SCMA系统和LDS系统在通信领域也可以被称为其他名称；进一步地，本申请实施例的技术方案可以应用于采用非正交多址接入技术的多载波传输系统，例如采用非正交多址接入技术正交频分复用(Orthogonal Frequency Division Multiplexing，OFDM)、滤波器组多载波(Filter Bank Multi-Carrier，FBMC)、通用频分复用(Generalized Frequency Division Multiplexing，GFDM)、滤波正交频分复用(Filtered-OFDM，F-OFDM)系统等。
图1示出了本申请实施例应用的无线通信系统100。该无线通信系统100可以包括接入网设备110。接入网设备110可以是与终端设备通信的设备。接入网设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备(例如UE)进行通信。可选地，该接入网设备110可以是下一代无线接入网(Next Generation Radio Access Network，NG RAN)，或者是NR系统中的基站(gNB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该接入网设备可以为中继站、接入点、车载设备、可穿戴设备，或者未来演进的公共陆地移动网络(Public Land  Mobile Network，PLMN)中的网络设备等。可选地，该接入网设备110也可以是LTE系统中的基站，例如，演进的通用路基无线接入网(Evolved Universal Terrestrial Radio Access Network，E-UTRAN)设备。
该无线通信系统100还包括位于接入网设备110覆盖范围内的至少一个终端设备120。终端设备120可以是移动的或固定的。可选地，终端设备120可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
该无线通信系统100还包括与接入网设备进行通信的核心网设备130。可选地，该核心网设备130可以是5G核心网设备，例如，接入与移动性管理功能(Access and Mobility Management Function，AMF)，又例如，会话管理功能(Session Management Function，SMF)。可选地，该核心网设备130也可以是LTE网络的分组核心演进(Evolved Packet Core，EPC)设备，例如，会话管理功能+核心网侧的数据网关(Session Management Function+Core Packet Gateway，SMF+PGW-C)设备。
应理解，SMF+PGW-C可以同时实现SMF和PGW-C所能实现的功能。
可选地，在本申请实施例中，AMF可以与SMF进行信息交互，例如，SMF从AMF获取一些无线接入网侧的信息。
可选地，在本申请实施例中，AMF可以从无线接入网中获取回落标识，或者，用于指示针对终端设备的第一承载/流未成功建立的消息。
图1示例性地示出了一个接入网设备、一个核心网设备和两个终端设备，可选地，该无线通信系统100可以包括多个接入网设备并且每个接入网设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
可选地，该无线通信系统100还可以包括移动管理实体(Mobile Management Entity，MME)、统一数据管理(Unified Data Management，UDM)，认证服务器功能(Authentication Server Function，AUSF)，用户面功能(User  Plane Function，UPF)，信令网关(Signaling Gateway，SGW)等其他网络实体，本申请实施例对此不作限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
图2示出了本申请实施例的用于传输数据的方法200的示意性框图。图2中所示的终端设备可以是如图1所示的终端设备，图2中所示的网络设备可以是如图1所示的核心网设备。该方法200包括以下部分或全部内容：
S210，终端设备向网络设备发送第一请求消息，所述第一请求消息用于申请在第一协议数据单元PDU会话中进行N个数据流的会话建立。
S220，所述终端设备接收所述网络设备发送的所述第一请求消息的响应消息，所述响应消息用于指示所述网络设备拒绝在所述第一PDU会话中进行所述N个数据流中的M个数据流的会话建立，N和M均为正整数，且N大于或等于M。
具体地，当终端设备申请针对多个数据流(Flow)在一个协议数据单元(Protocol Data Unit，PDU)会话中建立会话时，终端设备可以向核心网设备发送非接入层(Non-Access Stratum，NAS)消息，该NAS消息可以请求建立或修改某个PDU会话，并且该NAS消息中可以携带该PDU会话的标识(Identity，ID)，核心网设备在接收到该NAS消息之后，就可以获知在哪个PDU会话中建立数据流的会话。应理解，一个终端设备可能会有多个PDU会话，本申请实施例是针对一个终端设备的多个PDU会话中的某一个PDU会话。核心网设备在接收到终端设备发送的该会话建立或修改请求之后，核心网设备可以触发接入网设备进行多个数据流在该PDU会话中建立或修改。接入网设备进而可以根据请求判断哪些数据流可以在该PDU会话中进行会话建立，那么数据流不能够在该PDU会话中进行会话建立，接入网设备进而可以向核心网设备发送一个数据流列表，该数据流列表可以是该接入网设备接受的数据流列表，也可以是接入网设备拒绝的数据流列表。核心网设备在接收到该数据流列表之后，可以向终端设备发送响应消息，告诉终端设备网络设备拒绝请求的数据流中的部分数据流，终端设备在有部分数据流被拒 绝之后，就可以进行相应地调整，例如，可以调整建立该PDU会话的参数，或者换一个PDU会话重新发起被拒绝数据流的会话建立等。
因此，本申请实施例的用于传输数据的方法，通过向终端设备反馈会话建立的情况，使得终端设备能够及时地对会话建立策略进行调整，从而有利于提高通信系统的性能。
应理解，本申请实施例可以应用于5G通信系统，也就是说，本申请实施例的核心网设备可以是5G中的SMF。可选地，在会话建立过程中，SMF可以与UPF交互进行会话建立。
可选地，该响应消息携带拒绝原因值，该拒绝原因值用于指示该第一PDU会话不支持该M个数据流。
通常，网络侧可以拒绝一个或多个Flow在一个PDU会话中建立，可以是多种原因，例如，可能是PDU会话不允许、无线接入技术(Radio Access Technology，RAT)接入不允许、会话或业务连续性模式不满足、(Single-Network Slice Selection Assistance Information，S-NSSAI)错误、数据网络名称(Data Network Name，DNN)不支持和PDU会话标识不被识别。在本申请实施例中，网络侧在向终端设备发送的响应消息中可以携带原因值，具体地，网络侧可以和终端设备预先约定好用几个bit来表示上述各种原因，例如，可以用0001表示PDU会话不允许，0010表示RAT接入不允许等。其中，PDU会话不允许可以是PDU会话满了，不能在该PDU会话中添加数据流等，PDU会话不允许和PDU会话标识可以都看成是PDU会话不支持。当终端设备根据响应消息获知是由于PDU会话不支持的原因，终端设备可以对PDU会话进行适当的调整，再次向网络设备发起会话建立或修改。进而可以提高PDU会话建立成功的可能性。
可选地，该响应消息携带该M个数据流中每个数据流的标识。
进一步地，网络设备还可以通过响应消息向终端设备指示是哪些数据流被网络侧拒绝了，例如，可以在该响应消息中携带网络设备接受的数据流列表，终端设备可以根据接受的数据流列表进一步地可以确定出来哪些数据流被拒绝了。也可以直接在响应消息中携带网络设备拒绝的数据流列表。数据流列表可以包括多个数据流的标识。
终端设备在获知是哪些数据流被拒绝了之后，终端设备可以针对性的对这些被拒绝的数据流进行会话调整。终端设备也可以不用知道是哪些数据 流被拒绝了，一旦获知拒绝原因，那么终端设备可以对所有的数据流进行会话调整。
可选地，该方法还包括：该终端设备响应于该响应消息，向该网络设备发送第二请求消息，该第二请求消息用于申请在第二PDU会话中进行该M个数据流中的至少一个数据流的会话建立。
可选地，该第一请求消息携带该第一PDU会话的标识，该第二请求消息携带该第二PDU会话的标识，该第二PDU会话为调整该第一PDU会话的标识之后的该第一PDU会话。
可选地，该终端设备响应于该响应消息之前，该方法还包括：该终端设备根据该M个数据流，调整非该第一PDU会话的该第二PDU会话的建立参数。
由上述可知，终端设备在获知被拒绝的数据流列表，以及拒绝原因是PDU会话不支持之后，终端设备可以对该数据流的会话建立进行调整。例如，若终端设备知道是由于前一次PDU会话的标识不被本地网络识别，那么终端设备可以产生一个新的标识，再次使用前一次PDU会话的内容对拒绝的数据流进行会话建立。具体地，若本地网络识别PDU会话标识1～100，而前一次的PDU会话的标识为101，那么本地网络是无法识别该PDU会话标识的，网络侧可以告诉终端设备该PDU会话标识不被识别，那么终端设备可以产生一个新的PDU会话标识在1～100之间，重新采用该PDU会话发起会话建立或修改请求，并且在该请求中携带新产生的PDU会话标识。再例如，若终端设备知道是由于前一次PDU会话不允许被拒绝的数据流，终端设备可以将该被拒绝的数据流捆绑到另外一个PDU会话中，再次发起PDU会话建立。具体地，终端设备可以修改另外一个PDU会话的建立参数，将被拒绝的数据流与该PDU会话进行关联。
可选地，该响应消息携带该第二PDU会话的标识。
具体地，网络设备一旦判断出来是因为PDU会话不支持造成一些数据流被拒绝，网络设备可以向终端设备发送建议的PDU会话，例如，网络设备可以在响应消息中直接携带建议的PDU会话的标识。或者网络设备判断出来是由于PDU会话的标识不被识别，网络设备可以向终端设备建议的PDU会话标识。总之，网络设备可以向终端设备发送与拒绝原因值对应的各种参数的建议值。本申请实施例不限于此。
下面将结合图3详细介绍一下本申请实施例的用于传输数据的方法300的流程图。该方法是以5G通信系统为例进行描述的，该方法300包括以下或全部内容：
S301，UE向SMF发送第一PDU会话建立或修改请求，该NAS消息携带该第一PDU会话的标识。
S302，SMF在接收到该第一PDU会话建立或修改请求之后，可以与UPF交互进行会话建立。
S303，SMF也可以在接收到该第一PDU会话建立或修改请求之后，触发无线接入网(RadioAccess Network，RAN)进行会话建立或修改请求。
S304，RAN在进行会话建立之后，可以向SMF进行回复，携带接收或拒绝的Flow列表。
S305，SMF在接收到RAN的回复之后，可以通过向UE进行回复，可以携带拒绝的列表，可以是全部拒绝，也可以是部分拒绝，也可以携带拒绝的原因，还可以携带建议值，也就是建议的PDU会话或者建议的PDU会话的标识。
S306，UE在接收到回复消息之后，可以进行相应地调整，重新发起PDU会话的建立或修改。具体地，UE可以向SMF发送第二PDU会话的建立或修改请求，可以携带新的PDU会话标识(PDU会话标识不被识别)，也可以携带该第二PDU会话的标识(更换PDU会话)，以及之前被拒绝的Flow。
图4示出了本申请实施例的用于传输数据的方法400的示意性框图。如图4所示，该方法400包括以下部分内容或全部内容：
S410，网络设备接收终端设备发送的第一请求消息，该第一请求消息用于申请在第一协议数据单元PDU会话中进行N个数据流的会话建立。
S420，该网络设备向该终端设备发送该第一请求消息的响应消息，该响应消息用于指示该网络设备拒绝在该第一PDU会话中进行该N个数据流中的M个数据流的会话建立，N和M均为正整数，且N大于或等于M。
因此，本申请实施例的用于传输数据的方法，通过向终端设备反馈会话建立的情况，使得终端设备能够及时地对会话建立策略进行调整，从而有利于提高通信系统的性能。
可选地，该响应消息携带拒绝原因值，该拒绝原因值用于指示该第一PDU会话不支持该M个数据流。
可选地，该响应消息携带该M个数据流中每个数据流的标识。
可选地，该方法还包括：该网络设备接收该终端设备发送的第二请求消息，该第二请求消息用于申请在第二PDU会话中进行该M个数据流中的至少一个数据流的会话建立。
可选地，该响应消息携带该网络设备建议的非该第一PDU会话的该第二PDU会话的标识。
可选地，该网络设备为会话管理功能SMF设备，该方法还包括：该SMF设备根据该第一请求消息，触发接入网设备在该第一PDU会话中进行该N个数据流的会话建立；该SMF设备接收该接入网设备发送的与该第一PDU会话对应的数据流列表，该数据流列表包括该M个数据流或该第一PDU会话接收的该N个数据流中的(N-M)个数据流。
应理解，网络设备描述的网络设备与终端设备之间的交互及相关特性、功能等与终端设备的相关特性、功能相应。并且相关内容在上述方法200和方法300中已经作了详尽描述，为了简洁，在此不再赘述。
还应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
图5示出了本申请实施例的用于传输数据的方法500的示意性框图。如图5所示，该方法500包括以下部分内容或全部内容：
S510，终端设备根据用户设备路由选择策略URSP中至少一个规则中每个规则的标识，分别获取该至少一个规则。
S520，该终端设备根据该至少一个规则，分别向网络设备发起与该至少一个规则一一对应的至少一个协议数据单元PDU会话的建立或修改。
具体地，在5G中，引入了用户设备路由选择策略(UE Route Selection Policy，URSP)的概念，URSP策略规定了UE对于不同数据流的路由策略。其中，每一个终端设备只有一个URSP，每一个URSP中可以有多种规则，终端设备可以基于每一个规则发起一个PDU会话建立。具体地，终端设备可以基于某个规则中的一个或多个参数发起一个PDU会话建立或修改。例如，该一个或多个参数可以是接入RAT、会话或业务连续性、网络切片或者分流等。该规则中的参数可以由核心网测得，在终端设备进行注册过程中发送给终端设备，终端设备据此来发起会话的建立或修改流程。在本申 请实施例中，可以引入规则标识，使得终端设备可以根据规则标识来获取某一规则，而不再是网络设备一次性将所有规则下发给终端设备，减轻了网络设备的压力，并且提高了通信灵活性。
可选地，该至少一个规则为多个规则，该终端设备根据该多个规则，分别向网络设备发起与该多个规则一一对应的多个协议数据单元PDU会话的建立或修改，包括：该终端设备根据该多个规则的优先级，依次向该网络设备发起该多个PDU会话的建立或修改。
具体地，在本申请实施例中，该URSP中的多个规则可以引入优先级概念，也就是说终端设备可以优先基于某种规则向网络设备发起与该规则对应的PDU会话的建立或修改。终端设备也可以将多个规则进行分类，将每一类规则进行优先级排序，对于同一类的规则内部发起的PDU会话可以不用排序，也就是说可以任意次序发起PDU会话。
可选地，可以由每个规则的标识来表征每个规则的优先等级。例如，终端设备一旦获得规则#1，终端设备可以认为该规则#1的优先等级最高。
可选地，该至少一个规则中的第一规则包括以下参数中的至少一种参数：无线接入技术RAT、会话和业务连续性模式、单网络切片辅助信息
S-NSSAI、分流类型、数据网络名称DNN和数据流过滤器。
应理解，这里是以第一规则为了进行描述的，在URSP中的每一个规则都可以包括上述各种参数的任意组合，并且上述各种参数仅仅只是示意性说明，本申请实施例并不限于此。
可选地，该至少一种参数中的第一参数包括表征优先级的多个值，该终端设备根据该第一规则，向网络设备发起第一协议数据单元PDU会话的建立或修改，包括：该终端设备根据该多个值的优先级，向该网络设备发起第一PDU会话的建立或修改。
举例来说，第一规则可以包括接入RAT、会话和业务连续性模式以及单网络切片辅助信息S-NSSAI，并且接入RAT的值为第三代合作伙伴项目(3rd Generation Partnership Project，3GPP)接入(access)和无线局域网(Wireless Local Area Networks，WLAN)access。会话和业务连续性模式包括模式3和模式2，S-NSSAI包括S-NSSAI-a和S-NSSAI-b。可以将各个参数的值进行优先级排序，例如，接入RAT可以优先使用3GPP access，S-NSSAI可以优先使用S-NSSAI-a，会话和业务连续性模式可以优先使用模式3等。一 旦网络设备反馈某一个参数的值不合适，那么终端设备可以调整为其他值。终端设备可以在第一次发起PDU会话建立或修改时，随机选择与该PDU会话对应的规则中某一参数的值。终端设备也可以直接选择优先级较高的某一参数的值，来提高PDU会话建立成功的可能性。若终端设备在第一次发起PDU会话建立或修改时是随机选择的某一参数的值，在网络设备由于该参数不满足要求而拒绝该PDU会话请求时，终端设备可以选择该参数的优先级更高的值再次发起该PDU会话请求。
可选地，该终端设备根据该至少一个规则中的第一规则，向网络设备发起第一协议数据单元PDU会话的建立或修改，包括：该终端设备根据该第一规则，向该网络设备发送第一请求消息，该第一请求消息用于请求该网络设备在该第一PDU会话中进行N个数据流的会话建立；在该终端设备根据该第一规则，向该网络设备发起第一PDU会话的建立或修改之后，该方法还包括：该终端设备接收该网络设备发送的该第一请求消息的响应消息，该响应消息用于指示该网络设备拒绝在该第一PDU会话中进行该N个数据流中的M个数据流的会话建立，N和M均为正整数，N大于或等于M。
可选地，该响应消息携带拒绝原因值，该拒绝原因值用于指示以下情况中的至少一种情况：PDU会话不支持、RAT接入不允许、会话或业务连续性模式不满足、S-NSSAI错误、DNN不支持和PDU会话标识不被识别。
通常，网络侧可以拒绝一个或多个Flow在一个PDU会话中建立，可以是多种原因，例如，可能是PDU会话不允许、RAT接入不允许、会话或业务连续性模式不满足、S-NSSAI错误、DNN不支持等URSP中与该PDU会话对应的规则中的参数不满足要求，也可以是PDU会话标识不被识别。在本申请实施例中，网络侧在向终端设备发送的响应消息中可以携带原因值，具体地，网络侧可以和终端设备预先约定好用几个bit来表示上述各种原因，例如，可以用0001表示PDU会话不允许，0010表示RAT接入不允许等。终端设备一旦获知是URSP中对应规则中的某个参数不满足要求时，终端设备可以对该参数的值进行调整。
可选地，该方法还包括：该终端设备响应于该响应消息，调整与该拒绝原因值对应的该第一规则中的参数的值；该终端设备根据调整后的该第一规则，向该网络设备发送第二请求消息，该第二请求消息用于请求该网络设备在第一PDU会话中进行该M个数据流中的至少一个数据流的会话建 立。
可选地，与该拒绝原因值对应的该第一规则的参数包括表征优先级的多个值，该终端设备响应于该响应消息，调整与该拒绝原因值对应的该第一规则的参数的值，包括：该终端设备响应于该响应消息，将与该拒绝原因值对应的该第一URSP的参数的值调整为优先级高于前一次发起第一PDU会话建立的值。
可选地，该响应消息携带该网络设备建议的与该拒绝原因值对应的该第一规则的参数的值，该终端设备响应于该响应消息，调整与该拒绝原因值对应的该第一URSP的参数的值，包括：该终端设备将与该拒绝原因值对应的该第一规则的参数的值调整为该网络设备建议的与该拒绝原因值对应的该第一规则的参数的值。
也就是说，终端设备在接收到响应消息后，如果网络设备在响应消息中携带了建议值，则根据建议值进行修改，如果没有携带建议值，则与拒绝原因值对应的规则中的参数可以按照参数的优先级进行调整。例如，如果网络设备回复的是接入RAT接入不满足，终端设备可以选择优先级更高的RAT接入再次发起PDU会话建立。如果网络设备回复的是接入RAT接入不满足，并且在该回复中携带了建议RAT接入为3GPP access，则终端设备可以直接根据3GPP access再次发起PDU会话建立。
可选地，该方法还包括：该终端设备接收该网络设备发送的该URSP中除该至少一个规则中第一规则外的第二规则以及该第一规则的标识；该终端设备根据第一规则的标识，获取该第一规则，包括：该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识，通过用户面获取该第一规则，或该终端设备根据该第一规则的标识，触发该网络设备通过控制面将该第一规则下发。
本领域技术人员理解，在终端设备进行网络注册的过程中，网络设备通过策略控制功能(Policy Control Funtion，PCF)向终端设备下发URSP策略。
可选地，该方法还包括：该终端设备接收服务器的标识；该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识，通过用户面获取该第一规则，包括：该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识和该服务器的标识，通过用户面获取该第一规则。
可选地，该第二规则的优先级高于该第一规则的优先级。
在本申请实施例中，为了减轻网络压力，并且在URSP策略过大的情况下，PCF可能无法通过一条信令消息完全下发给终端设备，那么PCF可以通过控制面分批次向终端设备下发URSP中的多个规则，例如，可以将多个规则进行分组，每条消息下发一组规则，或者也可以对该多个规则进行优先级排序主动分批次下发，优先级高的可以先下发，终端设备还可以在每次接收完一批规则之后，向PCF发送要求的规则的标识，具体地，若PCF首次向终端设备下发规则1和规则2，终端设备可以向PCF反馈规则3和规则4的标识，使得PCF再次向终端设备发送规则3和规则4。
PCF也可以是先向终端设备发送一部分规则，并携带另外一部分规则的标识，在终端设备根据一部分规则建立好用户面之后，终端设备可以根据另外一部分规则的标识在用户面来获取。进一步地，PCF还可以向终端设备下发存储另外一部分规则的服务器的标识，终端设备在根据一部分规则建立好用户面之后，就可以根据另外一部分规则的标识在用户面相应的服务器中获取另外一部分规则。
通过分批次获取URSP策略，可以有效地降低网络压力，提高通信灵活性。
可选地，终端设备根据用户设备路由选择策略URSP中至少一个规则中每个规则的标识，分别获取该至少一个规则，包括：在该终端设备进行网络注册的过程中，该终端设备根据该至少一个规则中每个规则的标识，获取该至少一个规则。
图6示出了本申请实施例的用于传输数据的方法600的示意性框图。如图6所示，该方法600包括以下部分内容或全部内容：
S610，在终端设备进行网络注册的过程中，网络设备通过多条消息向该终端设备发送用户设备路由选择策略URSP中的多个规则。
因此，本申请实施例的用于传输数据的方法，通过分批次获取URSP策略，可以有效地降低网络压力，提高通信灵活性。
可选地，该在终端设备进行网络注册的过程中，网络设备通过多条消息向该终端设备发送用户设备路由选择策略URSP中的多个规则，包括：在终端设备进行网络注册的过程中，该网络设备根据该多个规则的优先级，依次通过控制面的多条消息向该终端设备发送该多个规则。
可选地，该网络设备为策略控制功能PCF。
图7示出了本申请实施例的用于传输数据的方法700的示意性框图。如图7所示，该方法700包括以下部分内容或全部内容：
S710，在终端设备进行网络注册的过程中，网络设备向该终端设备发送用户设备路由选择策略URSP中除第一规则之外的第二规则和该第一规则的标识，以便于该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识，通过用户面获取该第一规则。
本申请实施例的用于传输数据的方法，通过分批次获取URSP策略，可以有效地降低网络压力，提高通信灵活性。
可选地，该方法还包括：该网络设备向该终端设备发送服务器的标识，以便于该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识和该服务器的标识，通过用户面获取该第一规则。
可选地，该网络设备为策略控制功能PCF。
应理解，网络设备描述的网络设备与终端设备之间的交互及相关特性、功能等与终端设备的相关特性、功能相应。并且相关内容在上述方法600中已经作了详尽描述，为了简洁，在此不再赘述。
还应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上文中详细描述了根据本申请实施例的用于传输数据的方法，下面将结合图8至图17，描述根据本申请实施例的用于传输数据的装置，方法实施例所描述的技术特征适用于以下装置实施例。
图8示出了本申请实施例的终端设备800的示意性框图。如图8所示，该终端设备800包括：
发送单元810，用于向网络设备发送第一请求消息，该第一请求消息用于申请在第一协议数据单元PDU会话中进行N个数据流的会话建立；
接收单元820，用于接收该网络设备发送的该第一请求消息的响应消息，该响应消息用于指示该网络设备拒绝在该第一PDU会话中进行该N个数据流中的M个数据流的会话建立，N和M均为正整数，且N大于或等于M。
因此，本申请实施例的终端设备，通过接收网络设备反馈的会话建立的情况，使得终端设备能够及时地对会话建立策略进行调整，从而有利于提 高通信系统的性能。
可选地，该响应消息携带拒绝原因值，该拒绝原因值用于指示该第一PDU会话不支持该M个数据流。
可选地，该响应消息携带该M个数据流中每个数据流的标识。
可选地，该发送单元，还用于响应于该响应消息，向该网络设备发送第二请求消息，该第二请求消息用于申请在第二PDU会话中进行该M个数据流中的至少一个数据流的会话建立。
可选地，该第一请求消息携带该第一PDU会话的标识，该第二请求消息携带该第二PDU会话的标识，该第二PDU会话为调整该第一PDU会话的标识之后的该第一PDU会话。
可选地，该终端设备响应于该响应消息之前，该终端设备还包括：处理单元，用于根据该M个数据流，调整非该第一PDU会话的该第二PDU会话的建立参数。
可选地，该响应消息携带该第二PDU会话的标识。
可选地，该网络设备为会话管理功能SMF设备。
应理解，根据本申请实施例的终端设备800可对应于本申请方法实施例中的终端设备，并且终端设备800中的各个单元的上述和其它操作和/或功能分别为了实现图2和图3方法中终端设备的相应流程，为了简洁，在此不再赘述。
图9示出了本申请实施例的网络设备900的示意性框图。如图9所示，该网络设备900包括：
接收单元910，用于接收终端设备发送的第一请求消息，该第一请求消息用于申请在第一协议数据单元PDU会话中进行N个数据流的会话建立；
发送单元920，用于向该终端设备发送该第一请求消息的响应消息，该响应消息用于指示该网络设备拒绝在该第一PDU会话中进行该N个数据流中的M个数据流的会话建立，N和M均为正整数，且N大于或等于M。
因此，本申请实施例的网络设备，通过向终端设备反馈会话建立的情况，使得终端设备能够及时地对会话建立策略进行调整，从而有利于提高通信系统的性能。
可选地，该响应消息携带拒绝原因值，该拒绝原因值用于指示该第一PDU会话不支持该M个数据流。
可选地，该响应消息携带该M个数据流中每个数据流的标识。
可选地，该接收单元，还用于接收该终端设备发送的第二请求消息，该第二请求消息用于申请在第二PDU会话中进行该M个数据流中的至少一个数据流的会话建立。
可选地，该响应消息携带该网络设备建议的非该第一PDU会话的该第二PDU会话的标识。
可选地，该网络设备为会话管理功能SMF设备，该网络设备还包括：处理单元，用于根据该第一请求消息，触发接入网设备在该第一PDU会话中进行该N个数据流的会话建立；该接收单元，还用于接收该接入网设备发送的与该第一PDU会话对应的数据流列表，该数据流列表包括该M个数据流或该第一PDU会话接收的该N个数据流中的(N-M)个数据流。
应理解，根据本申请实施例的网络设备900可对应于本申请方法实施例中的网络设备，并且网络设备900中的各个单元的上述和其它操作和/或功能分别为了实现图4方法中网络设备的相应流程，为了简洁，在此不再赘述。
图10示出了本申请实施例的终端设备1000的示意性框图。如图10所示，该终端设备1000包括：
处理单元1100，用于根据用户设备路由选择策略URSP中至少一个规则中每个规则的标识，分别获取该至少一个规则。
该处理单元1100，还用于根据该至少一个规则，分别向网络设备发起与该至少一个规则一一对应的至少一个协议数据单元PDU会话的建立或修改。
本申请实施例的终端设备，可以根据规则标识来获取某一规则，而不再是网络设备一次性将所有规则下发给终端设备，减轻了网络设备的压力，并且提高了通信灵活性。
可选地，该至少一个规则为多个规则，该处理单元具体用于：根据该多个规则的优先级，依次向该网络设备发起该多个PDU会话的建立或修改。
可选地，该至少一个规则中的第一规则包括以下参数中的至少一种参数：无线接入技术RAT、会话和业务连续性模式、单网络切片辅助信息S-NSSAI、分流类型、数据网络名称DNN和数据流过滤器。
可选地，该至少一种参数中的第一参数包括表征优先级的多个值，该处 理单元具体用于：根据该多个值的优先级，向该网络设备发起第一PDU会话的建立或修改。
可选地，该处理单元还用于根据该第一规则，向该网络设备发送第一请求消息，该第一请求消息用于请求该网络设备在该第一PDU会话中进行N个数据流的会话建立；在该处理单元根据该第一规则，向该网络设备发起第一PDU会话的建立或修改之后，该终端设备还包括：接收单元，用于接收该网络设备发送的该第一请求消息的响应消息，该响应消息用于指示该网络设备拒绝在该第一PDU会话中进行该N个数据流中的M个数据流的会话建立，N和M均为正整数，N大于或等于M。
可选地，该响应消息携带拒绝原因值，该拒绝原因值用于指示以下情况中的至少一种情况：PDU会话不支持、RAT接入不允许、会话或业务连续性模式不满足、S-NSSAI错误、DNN不支持和PDU会话标识不被识别。
可选地，该终端设备还包括：该处理单元还用于响应于该响应消息，调整与该拒绝原因值对应的该第一规则中的参数的值；发送单元，用于根据调整后的该第一规则，向该网络设备发送第二请求消息，该第二请求消息用于请求该网络设备在第一PDU会话中进行该M个数据流中的至少一个数据流的会话建立。
可选地，与该拒绝原因值对应的该第一规则的参数包括表征优先级的多个值，该处理单元还用于响应于该响应消息，将与该拒绝原因值对应的该第一URSP的参数的值调整为优先级高于前一次发起第一PDU会话建立的值。
可选地，该响应消息携带该网络设备建议的与该拒绝原因值对应的该第一规则的参数的值，该处理单元响应于该响应消息，调整与该拒绝原因值对应的该第一URSP的参数的值，包括：该处理单元将与该拒绝原因值对应的该第一规则的参数的值调整为该网络设备建议的与该拒绝原因值对应的该第一规则的参数的值。
可选地，该终端设备还包括：接收单元，用于接收该网络设备发送的该URSP中除该至少一个规则中第一规则外的第二规则以及该第一规则的标识；该处理单元根据第一规则的标识，获取该第一规则，包括：
该处理单元在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识，通过用户面获取该第一规则，或该处理单元根据该第一规 则的标识，触发该网络设备通过控制面将该第一规则下发。
可选地，该接收单元，还用于接收服务器的标识；该处理单元在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识，通过用户面获取该第一规则，包括：该处理单元在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识和该服务器的标识，通过用户面获取该第一规则。
可选地，该第二规则的优先级高于该第一规则的优先级。
可选地，该处理单元根据用户设备路由选择策略URSP中至少一个规则中每个规则的标识，分别获取该至少一个规则，包括：在该终端设备进行网络注册的过程中，该处理单元根据该至少一个规则中每个规则的标识，获取该至少一个规则。
应理解，根据本申请实施例的终端设备1000可对应于本申请方法实施例中的终端设备，并且终端设备1000中的各个单元的上述和其它操作和/或功能分别为了实现图5方法中终端设备的相应流程，为了简洁，在此不再赘述。
图11示出了本申请实施例的网络设备2000的示意性框图。如图11所示，该网络设备2000包括：
发送单元2100，用于在终端设备进行网络注册的过程中，通过多条消息向该终端设备发送用户设备路由选择策略URSP中的多个规则。
因此，本申请实施例的网络设备，通过分批次获取URSP策略，可以有效地降低网络压力，提高通信灵活性。
可选地，该在终端设备进行网络注册的过程中，该处理单元具体用于：在终端设备进行网络注册的过程中，根据该多个规则的优先级，依次通过控制面的多条消息向该终端设备发送该多个规则。
可选地，该网络设备为策略控制功能PCF。
应理解，根据本申请实施例的网络设备2000可对应于本申请方法实施例中的终端设备，并且网络设备2000中的各个单元的上述和其它操作和/或功能分别为了实现图6方法中终端设备的相应流程，为了简洁，在此不再赘述。
图12示出了本申请实施例的网络设备3000的示意性框图。如图12所示，该网络设备3000包括：
发送单元3100，用于在终端设备进行网络注册的过程中，向该终端设备发送用户设备路由选择策略URSP中除第一规则之外的第二规则和该第一规则的标识，以便于该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识，通过用户面获取该第一规则。
因此，本申请实施例的网络设备，通过分批次获取URSP策略，可以有效地降低网络压力，提高通信灵活性。
可选地，该发送单元，还用于向该终端设备发送服务器的标识，以便于该终端设备在建立与该第二规则对应的第二PDU会话之后，根据该第一规则的标识和该服务器的标识，通过用户面获取该第一规则。
可选地，该网络设备为策略控制功能PCF。
应理解，根据本申请实施例的网络设备3000可对应于本申请方法实施例中的终端设备，并且网络设备3000中的各个单元的上述和其它操作和/或功能分别为了实现图7方法中终端设备的相应流程，为了简洁，在此不再赘述。
如图13所示，本申请实施例还提供了一种终端设备4000，该终端设备4000可以是图8中的终端设备800，其能够用于执行与图2中方法200对应的终端设备的内容。该终端设备4000包括：输入接口4010、输出接口4020、处理器4030以及存储器4040，该输入接口4010、输出接口4020、处理器4030和存储器4040可以通过总线系统相连。该存储器4040用于存储包括程序、指令或代码。该处理器4030，用于执行该存储器4040中的程序、指令或代码，以控制输入接口4010接收信号、控制输出接口4020发送信号以及完成前述方法实施例中的操作。
因此，本申请实施例的终端设备，通过接收网络设备反馈的会话建立的情况，使得终端设备能够及时地对会话建立策略进行调整，从而有利于提高通信系统的性能。
应理解，在本申请实施例中，该处理器4030可以是中央处理单元(Central Processing Unit，CPU)，该处理器4030还可以是其他通用处理器、数字信号处理器、专用集成电路、现成可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器4040可以包括只读存储器和随机存取存储器，并向处理器 4030提供指令和数据。存储器4040的一部分还可以包括非易失性随机存取存储器。例如，存储器4040还可以存储设备类型的信息。
在实现过程中，上述方法的各内容可以通过处理器4030中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的内容可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器4040，处理器4030读取存储器4040中的信息，结合其硬件完成上述方法的内容。为避免重复，这里不再详细描述。
一个具体的实施方式中，终端设备800中的发送单元可以由图13中的输出接口4020实现，终端设备800中的接收单元可以由图13中的输入接口4010实现。
如图14所示，本申请实施例还提供了一种网络设备5000，该网络设备5000可以是图9中的网络设备900，其能够用于执行与图4中方法400对应的网络设备的内容。该网络设备5000包括：输入接口5010、输出接口5020、处理器5030以及存储器5040，该输入接口5010、输出接口5020、处理器5030和存储器5040可以通过总线系统相连。该存储器5040用于存储包括程序、指令或代码。该处理器5030，用于执行该存储器5040中的程序、指令或代码，以控制输入接口5010接收信号、控制输出接口5020发送信号以及完成前述方法实施例中的操作。
因此，本申请实施例的网络设备，通过向终端设备反馈会话建立的情况，使得终端设备能够及时地对会话建立策略进行调整，从而有利于提高通信系统的性能。
应理解，在本申请实施例中，该处理器5030可以是中央处理单元(Central Processing Unit，CPU)，该处理器5030还可以是其他通用处理器、数字信号处理器、专用集成电路、现成可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器5040可以包括只读存储器和随机存取存储器，并向处理器5030提供指令和数据。存储器5040的一部分还可以包括非易失性随机存取存储器。例如，存储器5040还可以存储设备类型的信息。
在实现过程中，上述方法的各内容可以通过处理器5030中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的内容可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器5040，处理器5030读取存储器5040中的信息，结合其硬件完成上述方法的内容。为避免重复，这里不再详细描述。
一个具体的实施方式中，网络设备900中的发送单元可以由图14中的输出接口5020实现，网络设备900中的接收单元可以由图14中的输入接口5010实现。
如图15所示，本申请实施例还提供了一种终端设备6000，该终端设备6000可以是图10中的终端设备1000，其能够用于执行与图5中方法500对应的终端设备的内容。该终端设备6000包括：输入接口6010、输出接口6020、处理器6030以及存储器6060，该输入接口6010、输出接口6020、处理器6030和存储器6060可以通过总线系统相连。该存储器6060用于存储包括程序、指令或代码。该处理器6030，用于执行该存储器6060中的程序、指令或代码，以控制输入接口6010接收信号、控制输出接口6020发送信号以及完成前述方法实施例中的操作。
因此，本申请实施例的终端设备，可以根据规则标识来获取某一规则，而不再是网络设备一次性将所有规则下发给终端设备，减轻了网络设备的压力，并且提高了通信灵活性。
应理解，在本申请实施例中，该处理器6030可以是中央处理单元(Central Processing Unit，CPU)，该处理器6030还可以是其他通用处理器、数字信号处理器、专用集成电路、现成可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器6060可以包括只读存储器和随机存取存储器，并向处理器6030提供指令和数据。存储器6060的一部分还可以包括非易失性随机存取存储器。例如，存储器6060还可以存储设备类型的信息。
在实现过程中，上述方法的各内容可以通过处理器6030中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的内 容可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器6060，处理器6030读取存储器6060中的信息，结合其硬件完成上述方法的内容。为避免重复，这里不再详细描述。
一个具体的实施方式中，终端设备1000中的处理单元可以由图15中的处理器6030实现。
如图16所示，本申请实施例还提供了一种网络设备7000，该网络设备7000可以是图11中的网络设备2000，其能够用于执行与图6中方法600对应的网络设备的内容。该网络设备7000包括：输入接口7010、输出接口7020、处理器7030以及存储器7040，该输入接口7010、输出接口7020、处理器7030和存储器7040可以通过总线系统相连。该存储器7040用于存储包括程序、指令或代码。该处理器7030，用于执行该存储器7040中的程序、指令或代码，以控制输入接口7010接收信号、控制输出接口7020发送信号以及完成前述方法实施例中的操作。
因此，本申请实施例的网络设备，通过分批次获取URSP策略，可以有效地降低网络压力，提高通信灵活性。
应理解，在本申请实施例中，该处理器7030可以是中央处理单元(Central Processing Unit，CPU)，该处理器7030还可以是其他通用处理器、数字信号处理器、专用集成电路、现成可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器7040可以包括只读存储器和随机存取存储器，并向处理器7030提供指令和数据。存储器7040的一部分还可以包括非易失性随机存取存储器。例如，存储器7040还可以存储设备类型的信息。
在实现过程中，上述方法的各内容可以通过处理器7030中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的内容可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器7040，处理器7030读取存储器7040中的信息， 结合其硬件完成上述方法的内容。为避免重复，这里不再详细描述。
一个具体的实施方式中，网络设备2000中的发送单元可以由图16中的输出接口7020实现。
如图17所示，本申请实施例还提供了一种网络设备8000，该网络设备8000可以是图12中的网络设备3000，其能够用于执行与图7中方法700对应的网络设备的内容。该网络设备8000包括：输入接口8010、输出接口8020、处理器8030以及存储器8040，该输入接口8010、输出接口8020、处理器8030和存储器8040可以通过总线系统相连。该存储器8040用于存储包括程序、指令或代码。该处理器8030，用于执行该存储器8040中的程序、指令或代码，以控制输入接口8010接收信号、控制输出接口8020发送信号以及完成前述方法实施例中的操作。
因此，本申请实施例的网络设备，通过分批次获取URSP策略，可以有效地降低网络压力，提高通信灵活性。
应理解，在本申请实施例中，该处理器8030可以是中央处理单元(Central Processing Unit，CPU)，该处理器8030还可以是其他通用处理器、数字信号处理器、专用集成电路、现成可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器8040可以包括只读存储器和随机存取存储器，并向处理器8030提供指令和数据。存储器8040的一部分还可以包括非易失性随机存取存储器。例如，存储器8040还可以存储设备类型的信息。
在实现过程中，上述方法的各内容可以通过处理器8030中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的内容可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器8040，处理器8030读取存储器8040中的信息，结合其硬件完成上述方法的内容。为避免重复，这里不再详细描述。
一个具体的实施方式中，网络设备3000中的发送单元可以由图17中的输出接口8020实现。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各 示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
该作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
该功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(RandomAccess Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限 于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应该以权利要求的保护范围为准。

Claims (66)

  1. 一种用于传输数据的方法，其特征在于，包括：
    终端设备向网络设备发送第一请求消息，所述第一请求消息用于申请在第一协议数据单元PDU会话中进行N个数据流的会话建立；
    所述终端设备接收所述网络设备发送的所述第一请求消息的响应消息，所述响应消息用于指示所述网络设备拒绝在所述第一PDU会话中进行所述N个数据流中的M个数据流的会话建立，N和M均为正整数，且N大于或等于M。
  2. 根据权利要求1所述的方法，其特征在于，所述响应消息携带拒绝原因值，所述拒绝原因值用于指示所述第一PDU会话不支持所述M个数据流。
  3. 根据权利要求1或2所述的方法，其特征在于，所述响应消息携带所述M个数据流中每个数据流的标识。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备响应于所述响应消息，向所述网络设备发送第二请求消息，所述第二请求消息用于申请在第二PDU会话中进行所述M个数据流中的至少一个数据流的会话建立。
  5. 根据权利要求4所述的方法，其特征在于，所述第一请求消息携带所述第一PDU会话的标识，所述第二请求消息携带所述第二PDU会话的标识，所述第二PDU会话为调整所述第一PDU会话的标识之后的所述第一PDU会话。
  6. 根据权利要求4所述的方法，其特征在于，所述终端设备响应于所述响应消息之前，所述方法还包括：
    所述终端设备根据所述M个数据流，调整非所述第一PDU会话的所述第二PDU会话的建立参数。
  7. 根据权利要求6所述的方法，其特征在于，所述响应消息携带所述第二PDU会话的标识。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述网络设备为会话管理功能SMF设备。
  9. 一种用于传输数据的方法，其特征在于，包括：
    网络设备接收终端设备发送的第一请求消息，所述第一请求消息用于申请在第一协议数据单元PDU会话中进行N个数据流的会话建立；
    所述网络设备向所述终端设备发送所述第一请求消息的响应消息，所述响应消息用于指示所述网络设备拒绝在所述第一PDU会话中进行所述N个数据流中的M个数据流的会话建立，N和M均为正整数，且N大于或等于M。
  10. 根据权利要求9所述的方法，其特征在于，所述响应消息携带拒绝原因值，所述拒绝原因值用于指示所述第一PDU会话不支持所述M个数据流。
  11. 根据权利要求9或10所述的方法，其特征在于，所述响应消息携带所述M个数据流中每个数据流的标识。
  12. 根据权利要求9至11中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备接收所述终端设备发送的第二请求消息，所述第二请求消息用于申请在第二PDU会话中进行所述M个数据流中的至少一个数据流的会话建立。
  13. 根据权利要求9至12中任一项所述的方法，其特征在于，所述响应消息携带所述网络设备建议的非所述第一PDU会话的所述第二PDU会话的标识。
  14. 根据权利要求9至13中任一项所述的方法，其特征在于，所述网络设备为会话管理功能SMF设备，所述方法还包括：
    所述SMF设备根据所述第一请求消息，触发接入网设备在所述第一PDU会话中进行所述N个数据流的会话建立；
    所述SMF设备接收所述接入网设备发送的与所述第一PDU会话对应的数据流列表，所述数据流列表包括所述M个数据流或所述第一PDU会话接收的所述N个数据流中的(N-M)个数据流。
  15. 一种用于传输数据的方法，其特征在于，包括：
    终端设备根据用户设备路由选择策略URSP中至少一个规则中每个规则的标识，分别获取所述至少一个规则；
    所述终端设备根据所述至少一个规则，分别向网络设备发起与所述至少一个规则一一对应的至少一个协议数据单元PDU会话的建立或修改。
  16. 根据权利要求15所述的方法，其特征在于，所述至少一个规则为多个规则，所述终端设备根据所述多个规则，分别向网络设备发起与所述多个规则一一对应的多个协议数据单元PDU会话的建立或修改，包括：
    所述终端设备根据所述多个规则的优先级，依次向所述网络设备发起所述多个PDU会话的建立或修改。
  17. 根据权利要求15或16所述的方法，其特征在于，所述至少一个规则中的第一规则包括以下参数中的至少一种参数：无线接入技术RAT、会话和业务连续性模式、单网络切片辅助信息S-NSSAI、分流类型、数据网络名称DNN和数据流过滤器。
  18. 根据权利要求17所述的方法，其特征在于，所述至少一种参数中的第一参数包括表征优先级的多个值，所述终端设备根据所述第一规则，向网络设备发起第一协议数据单元PDU会话的建立或修改，包括：
    所述终端设备根据所述多个值的优先级，向所述网络设备发起第一PDU会话的建立或修改。
  19. 根据权利要求15至18中任一项所述的方法，其特征在于，所述终端设备根据所述至少一个规则中的第一规则，向网络设备发起第一协议数据单元PDU会话的建立或修改，包括：
    所述终端设备根据所述第一规则，向所述网络设备发送第一请求消息，所述第一请求消息用于请求所述网络设备在所述第一PDU会话中进行N个数据流的会话建立；
    在所述终端设备根据所述第一规则，向所述网络设备发起第一PDU会话的建立或修改之后，所述方法还包括：
    所述终端设备接收所述网络设备发送的所述第一请求消息的响应消息，所述响应消息用于指示所述网络设备拒绝在所述第一PDU会话中进行所述N个数据流中的M个数据流的会话建立，N和M均为正整数，N大于或等于M。
  20. 根据权利要求19所述的方法，其特征在于，所述响应消息携带拒绝原因值，所述拒绝原因值用于指示以下情况中的至少一种情况：PDU会话不支持、RAT接入不允许、会话或业务连续性模式不满足、S-NSSAI错误、DNN不支持和PDU会话标识不被识别。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括：
    所述终端设备响应于所述响应消息，调整与所述拒绝原因值对应的所述第一规则中的参数的值；
    所述终端设备根据调整后的所述第一规则，向所述网络设备发送第二请求消息，所述第二请求消息用于请求所述网络设备在第一PDU会话中进行所述M个数据流中的至少一个数据流的会话建立。
  22. 根据权利要求21所述的方法，其特征在于，与所述拒绝原因值对应的所述第一规则的参数包括表征优先级的多个值，所述终端设备响应于所述响应消息，调整与所述拒绝原因值对应的所述第一规则的参数的值，包括：
    所述终端设备响应于所述响应消息，将与所述拒绝原因值对应的所述第一URSP的参数的值调整为优先级高于前一次发起第一PDU会话建立的值。
  23. 根据权利要求21所述的方法，其特征在于，所述响应消息携带所述网络设备建议的与所述拒绝原因值对应的所述第一规则的参数的值，所述终端设备响应于所述响应消息，调整与所述拒绝原因值对应的所述第一URSP的参数的值，包括：
    所述终端设备将与所述拒绝原因值对应的所述第一规则的参数的值调整为所述网络设备建议的与所述拒绝原因值对应的所述第一规则的参数的值。
  24. 根据权利要求15至23中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收所述网络设备发送的所述URSP中除所述至少一个规则中第一规则外的第二规则以及所述第一规则的标识；
    所述终端设备根据第一规则的标识，获取所述第一规则，包括：
    所述终端设备在建立与所述第二规则对应的第二PDU会话之后，根据所述第一规则的标识，通过用户面获取所述第一规则，或
    所述终端设备根据所述第一规则的标识，触发所述网络设备通过控制面将所述第一规则下发。
  25. 根据权利要求24所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收服务器的标识；
    所述终端设备在建立与所述第二规则对应的第二PDU会话之后，根据 所述第一规则的标识，通过用户面获取所述第一规则，包括：
    所述终端设备在建立与所述第二规则对应的第二PDU会话之后，根据所述第一规则的标识和所述服务器的标识，通过用户面获取所述第一规则。
  26. 根据权利要求24或25所述的方法，其特征在于，所述第二规则的优先级高于所述第一规则的优先级。
  27. 根据权利要求15至26中任一项所述的方法，其特征在于，终端设备根据用户设备路由选择策略URSP中至少一个规则中每个规则的标识，分别获取所述至少一个规则，包括：
    在所述终端设备进行网络注册的过程中，所述终端设备根据所述至少一个规则中每个规则的标识，获取所述至少一个规则。
  28. 一种用于传输数据的方法，其特征在于，包括：
    在终端设备进行网络注册的过程中，网络设备通过多条消息向所述终端设备发送用户设备路由选择策略URSP中的多个规则。
  29. 根据权利要求28所述的方法，其特征在于，所述在终端设备进行网络注册的过程中，网络设备通过多条消息向所述终端设备发送用户设备路由选择策略URSP中的多个规则，包括：
    在终端设备进行网络注册的过程中，所述网络设备根据所述多个规则的优先级，依次通过控制面的多条消息向所述终端设备发送所述多个规则。
  30. 根据权利要求28或29所述的方法，其特征在于，所述网络设备为策略控制功能PCF设备。
  31. 一种用于传输数据的方法，其特征在于，包括：
    在终端设备进行网络注册的过程中，网络设备向所述终端设备发送用户设备路由选择策略URSP中除第一规则之外的第二规则和所述第一规则的标识，以便于所述终端设备在建立与所述第二规则对应的第二PDU会话之后，根据所述第一规则的标识，通过用户面获取所述第一规则。
  32. 根据权利要求31所述的方法，其特征在于，所述方法还包括：
    所述网络设备向所述终端设备发送服务器的标识，以便于所述终端设备在建立与所述第二规则对应的第二PDU会话之后，根据所述第一规则的标识和所述服务器的标识，通过用户面获取所述第一规则。
  33. 根据权利要求31或32所述的方法，其特征在于，所述网络设备为策略控制功能PCF设备。
  34. 一种终端设备，其特征在于，包括：
    发送单元，用于向网络设备发送第一请求消息，所述第一请求消息用于申请在第一协议数据单元PDU会话中进行N个数据流的会话建立；
    接收单元，用于接收所述网络设备发送的所述第一请求消息的响应消息，所述响应消息用于指示所述网络设备拒绝在所述第一PDU会话中进行所述N个数据流中的M个数据流的会话建立，N和M均为正整数，且N大于或等于M。
  35. 根据权利要求34所述的终端设备，其特征在于，所述响应消息携带拒绝原因值，所述拒绝原因值用于指示所述第一PDU会话不支持所述M个数据流。
  36. 根据权利要求34或35所述的终端设备，其特征在于，所述响应消息携带所述M个数据流中每个数据流的标识。
  37. 根据权利要求34至36中任一项所述的终端设备，其特征在于，所述发送单元，还用于响应于所述响应消息，向所述网络设备发送第二请求消息，所述第二请求消息用于申请在第二PDU会话中进行所述M个数据流中的至少一个数据流的会话建立。
  38. 根据权利要求37所述的终端设备，其特征在于，所述第一请求消息携带所述第一PDU会话的标识，所述第二请求消息携带所述第二PDU会话的标识，所述第二PDU会话为调整所述第一PDU会话的标识之后的所述第一PDU会话。
  39. 根据权利要求37所述的终端设备，其特征在于，所述终端设备还包括：
    处理单元，用于根据所述M个数据流，调整非所述第一PDU会话的所述第二PDU会话的建立参数。
  40. 根据权利要求39所述的终端设备，其特征在于，所述响应消息携带所述第二PDU会话的标识。
  41. 根据权利要求34至40中任一项所述的终端设备，其特征在于，所述网络设备为会话管理功能SMF设备。
  42. 一种网络设备，其特征在于，包括：
    接收单元，用于接收终端设备发送的第一请求消息，所述第一请求消息用于申请在第一协议数据单元PDU会话中进行N个数据流的会话建立；
    发送单元，用于向所述终端设备发送所述第一请求消息的响应消息，所述响应消息用于指示所述网络设备拒绝在所述第一PDU会话中进行所述N个数据流中的M个数据流的会话建立，N和M均为正整数，且N大于或等于M。
  43. 根据权利要求42所述的网络设备，其特征在于，所述响应消息携带拒绝原因值，所述拒绝原因值用于指示所述第一PDU会话不支持所述M个数据流。
  44. 根据权利要求42或43所述的网络设备，其特征在于，所述响应消息携带所述M个数据流中每个数据流的标识。
  45. 根据权利要求42至44中任一项所述的网络设备，其特征在于，所述接收单元，还用于接收所述终端设备发送的第二请求消息，所述第二请求消息用于申请在第二PDU会话中进行所述M个数据流中的至少一个数据流的会话建立。
  46. 根据权利要求42至45中任一项所述的网络设备，其特征在于，所述响应消息携带所述网络设备建议的非所述第一PDU会话的所述第二PDU会话的标识。
  47. 根据权利要求42至46中任一项所述的网络设备，其特征在于，所述网络设备为会话管理功能SMF设备，所述网络设备还包括：
    处理单元，用于根据所述第一请求消息，触发接入网设备在所述第一PDU会话中进行所述N个数据流的会话建立；
    所述接收单元，还用于接收所述接入网设备发送的与所述第一PDU会话对应的数据流列表，所述数据流列表包括所述M个数据流或所述第一PDU会话接收的所述N个数据流中的(N-M)个数据流。
  48. 一种终端设备，其特征在于，包括：
    处理单元，用于根据用户设备路由选择策略URSP中至少一个规则中每个规则的标识，分别获取所述至少一个规则；
    所述处理单元，还用于根据所述至少一个规则，分别向网络设备发起与所述至少一个规则一一对应的至少一个协议数据单元PDU会话的建立或修改。
  49. 根据权利要求48所述的终端设备，其特征在于，所述至少一个规则为多个规则，所述处理单元具体用于：
    根据所述多个规则的优先级，依次向所述网络设备发起所述多个PDU会话的建立或修改。
  50. 根据权利要求48或49所述的终端设备，其特征在于，所述至少一个规则中的第一规则包括以下参数中的至少一种参数：无线接入技术RAT、会话和业务连续性模式、单网络切片辅助信息S-NSSAI、分流类型、数据网络名称DNN和数据流过滤器。
  51. 根据权利要求50所述的终端设备，其特征在于，所述至少一种参数中的第一参数包括表征优先级的多个值，所述处理单元具体用于：
    根据所述多个值的优先级，向所述网络设备发起第一PDU会话的建立或修改。
  52. 根据权利要求48至51中任一项所述的终端设备，其特征在于，所述处理单元还用于根据所述第一规则，向所述网络设备发送第一请求消息，所述第一请求消息用于请求所述网络设备在所述第一PDU会话中进行N个数据流的会话建立；
    在所述处理单元根据所述第一规则，向所述网络设备发起第一PDU会话的建立或修改之后，所述终端设备还包括：
    接收单元，用于接收所述网络设备发送的所述第一请求消息的响应消息，所述响应消息用于指示所述网络设备拒绝在所述第一PDU会话中进行所述N个数据流中的M个数据流的会话建立，N和M均为正整数，N大于或等于M。
  53. 根据权利要求52所述的终端设备，其特征在于，所述响应消息携带拒绝原因值，所述拒绝原因值用于指示以下情况中的至少一种情况：PDU会话不支持、RAT接入不允许、会话或业务连续性模式不满足、S-NSSAI错误、DNN不支持和PDU会话标识不被识别。
  54. 根据权利要求53所述的终端设备，其特征在于，所述终端设备还包括：
    所述处理单元还用于响应于所述响应消息，调整与所述拒绝原因值对应的所述第一规则中的参数的值；
    发送单元，用于根据调整后的所述第一规则，向所述网络设备发送第二请求消息，所述第二请求消息用于请求所述网络设备在第一PDU会话中进行所述M个数据流中的至少一个数据流的会话建立。
  55. 根据权利要求54所述的终端设备，其特征在于，与所述拒绝原因值对应的所述第一规则的参数包括表征优先级的多个值，所述处理单元还用于响应于所述响应消息，将与所述拒绝原因值对应的所述第一URSP的参数的值调整为优先级高于前一次发起第一PDU会话建立的值。
  56. 根据权利要求54所述的终端设备，其特征在于，所述响应消息携带所述网络设备建议的与所述拒绝原因值对应的所述第一规则的参数的值，所述处理单元响应于所述响应消息，调整与所述拒绝原因值对应的所述第一URSP的参数的值，包括：
    所述处理单元将与所述拒绝原因值对应的所述第一规则的参数的值调整为所述网络设备建议的与所述拒绝原因值对应的所述第一规则的参数的值。
  57. 根据权利要求48至56中任一项所述的终端设备，其特征在于，所述终端设备还包括：
    接收单元，用于接收所述网络设备发送的所述URSP中除所述至少一个规则中第一规则外的第二规则以及所述第一规则的标识；
    所述处理单元根据第一规则的标识，获取所述第一规则，包括：
    所述处理单元在建立与所述第二规则对应的第二PDU会话之后，根据所述第一规则的标识，通过用户面获取所述第一规则，或
    所述处理单元根据所述第一规则的标识，触发所述网络设备通过控制面将所述第一规则下发。
  58. 根据权利要求57所述的终端设备，其特征在于，所述接收单元，还用于接收服务器的标识；
    所述处理单元在建立与所述第二规则对应的第二PDU会话之后，根据所述第一规则的标识，通过用户面获取所述第一规则，包括：
    所述处理单元在建立与所述第二规则对应的第二PDU会话之后，根据所述第一规则的标识和所述服务器的标识，通过用户面获取所述第一规则。
  59. 根据权利要求57或58所述的终端设备，其特征在于，所述第二规则的优先级高于所述第一规则的优先级。
  60. 根据权利要求48至59中任一项所述的终端设备，其特征在于，所述处理单元根据用户设备路由选择策略URSP中至少一个规则中每个规则的标识，分别获取所述至少一个规则，包括：
    在所述终端设备进行网络注册的过程中，所述处理单元根据所述至少一个规则中每个规则的标识，获取所述至少一个规则。
  61. 一种网络设备，其特征在于，包括：
    发送单元，用于在终端设备进行网络注册的过程中，通过多条消息向所述终端设备发送用户设备路由选择策略URSP中的多个规则。
  62. 根据权利要求61所述的网络设备，其特征在于，所述在终端设备进行网络注册的过程中，所述处理单元具体用于：
    在终端设备进行网络注册的过程中，根据所述多个规则的优先级，依次通过控制面的多条消息向所述终端设备发送所述多个规则。
  63. 根据权利要求61或62所述的网络设备，其特征在于，所述网络设备为策略控制功能PCF设备。
  64. 一种网络设备，其特征在于，包括：
    发送单元，用于在终端设备进行网络注册的过程中，向所述终端设备发送用户设备路由选择策略URSP中除第一规则之外的第二规则和所述第一规则的标识，以便于所述终端设备在建立与所述第二规则对应的第二PDU会话之后，根据所述第一规则的标识，通过用户面获取所述第一规则。
  65. 根据权利要求64所述的网络设备，其特征在于，所述发送单元，还用于向所述终端设备发送服务器的标识，以便于所述终端设备在建立与所述第二规则对应的第二PDU会话之后，根据所述第一规则的标识和所述服务器的标识，通过用户面获取所述第一规则。
  66. 根据权利要求64或65所述的网络设备，其特征在于，所述网络设备为策略控制功能PCF设备。
PCT/CN2017/107168 2017-10-20 2017-10-20 用于传输数据的方法、终端设备和网络设备 Ceased WO2019075763A1 (zh)

Priority Applications (27)

Application Number Priority Date Filing Date Title
EP21196875.5A EP3965367A1 (en) 2017-10-20 2017-10-20 Data transmission method, terminal device, and network device
KR1020207014334A KR102370267B1 (ko) 2017-10-20 2017-10-20 데이터 전송 방법, 단말 기기 및 네트워크 기기
BR112020007560-4A BR112020007560B1 (pt) 2017-10-20 Método para transmitir dados e dispositivo terminal
KR1020227006555A KR102477765B1 (ko) 2017-10-20 2017-10-20 데이터 전송 방법, 단말 기기 및 네트워크 기기
JP2020521884A JP7063988B2 (ja) 2017-10-20 2017-10-20 データ伝送方法、端末装置及びネットワーク装置
ES17928855T ES2900193T3 (es) 2017-10-20 2017-10-20 Método de transmisión de datos y dispositivo terminal para la selección de una regla en una directiva de selección de ruta de UE (URSP)
PCT/CN2017/107168 WO2019075763A1 (zh) 2017-10-20 2017-10-20 用于传输数据的方法、终端设备和网络设备
US16/755,879 US11304260B2 (en) 2017-10-20 2017-10-20 Data transmission method, terminal device, and network device
AU2017436351A AU2017436351B2 (en) 2017-10-20 2017-10-20 Data transmission method, terminal device, and network device
EP17928855.0A EP3700268B1 (en) 2017-10-20 2017-10-20 Data transmission method and terminal device for the selection of a rule in a ue route selection policy (ursp)
PL17928855T PL3700268T3 (pl) 2017-10-20 2017-10-20 Sposób transmisji danych i urządzenie końcowe do wyboru reguły w polityce wyboru trasy sprzętu UE (URSP)
RU2020116371A RU2761443C2 (ru) 2017-10-20 2017-10-20 Способ передачи данных, терминальное устройство и сетевое устройство
CA3079480A CA3079480C (en) 2017-10-20 2017-10-20 Initiating establishment of protocol data unit session method and terminal device
CN202010099121.1A CN111182572B (zh) 2017-10-20 2017-10-20 用于传输数据的方法、终端设备和网络设备
CN201780092464.1A CN110809899B (zh) 2017-10-20 2017-10-20 用于传输数据的方法和网络设备
PCT/CN2017/111688 WO2019075816A1 (zh) 2017-10-20 2017-11-17 用于传输数据的方法、终端设备和会话管理功能smf设备
KR1020207013837A KR102477774B1 (ko) 2017-10-20 2018-06-19 데이터 전송을 위한 방법, 단말 기기 및 세션 관리 기능 기기
CN201880057322.6A CN111052832B (zh) 2017-10-20 2018-06-19 用于传输数据的方法、终端设备和会话管理功能smf设备
EP18868123.3A EP3691380B1 (en) 2017-10-20 2018-06-19 Method for transmitting data, terminal device, and session management function (smf) device
CN202010303770.9A CN111654922B (zh) 2017-10-20 2018-06-19 用于传输数据的方法和终端设备
PCT/CN2018/091888 WO2019076075A1 (zh) 2017-10-20 2018-06-19 用于传输数据的方法、终端设备和会话管理功能smf设备
JP2020521993A JP7182621B2 (ja) 2017-10-20 2018-06-19 データ伝送方法、端末装置及びセッション管理機能（ｓｍｆ）装置
AU2018353168A AU2018353168A1 (en) 2017-10-20 2018-06-19 Method for transmitting data, terminal device, and session management function (SMF) device
PCT/CN2018/104911 WO2019076167A1 (zh) 2017-10-20 2018-09-10 用于传输数据的方法、终端设备和会话管理功能smf设备
TW107136608A TWI779117B (zh) 2017-10-20 2018-10-17 用於傳輸資料的方法、終端設備和會話管理功能smf設備
US16/850,844 US11330666B2 (en) 2017-10-20 2020-04-16 Data transmitting method and terminal device
US17/590,604 US20220159781A1 (en) 2017-10-20 2022-02-01 Data transmission method, terminal device, and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/107168 WO2019075763A1 (zh) 2017-10-20 2017-10-20 用于传输数据的方法、终端设备和网络设备

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/755,879 A-371-Of-International US11304260B2 (en) 2017-10-20 2017-10-20 Data transmission method, terminal device, and network device
US17/590,604 Continuation US20220159781A1 (en) 2017-10-20 2022-02-01 Data transmission method, terminal device, and network device

Publications (1)

Publication Number Publication Date
WO2019075763A1 true WO2019075763A1 (zh) 2019-04-25

Family

ID=66173169

Family Applications (4)

Application Number Title Priority Date Filing Date
PCT/CN2017/107168 Ceased WO2019075763A1 (zh) 2017-10-20 2017-10-20 用于传输数据的方法、终端设备和网络设备
PCT/CN2017/111688 Ceased WO2019075816A1 (zh) 2017-10-20 2017-11-17 用于传输数据的方法、终端设备和会话管理功能smf设备
PCT/CN2018/091888 Ceased WO2019076075A1 (zh) 2017-10-20 2018-06-19 用于传输数据的方法、终端设备和会话管理功能smf设备
PCT/CN2018/104911 Ceased WO2019076167A1 (zh) 2017-10-20 2018-09-10 用于传输数据的方法、终端设备和会话管理功能smf设备

Family Applications After (3)

Application Number Title Priority Date Filing Date
PCT/CN2017/111688 Ceased WO2019075816A1 (zh) 2017-10-20 2017-11-17 用于传输数据的方法、终端设备和会话管理功能smf设备
PCT/CN2018/091888 Ceased WO2019076075A1 (zh) 2017-10-20 2018-06-19 用于传输数据的方法、终端设备和会话管理功能smf设备
PCT/CN2018/104911 Ceased WO2019076167A1 (zh) 2017-10-20 2018-09-10 用于传输数据的方法、终端设备和会话管理功能smf设备

Country Status (12)

Country Link
US (3) US11304260B2 (zh)
EP (3) EP3965367A1 (zh)
JP (2) JP7063988B2 (zh)
KR (3) KR102477765B1 (zh)
CN (4) CN111182572B (zh)
AU (2) AU2017436351B2 (zh)
CA (1) CA3079480C (zh)
ES (1) ES2900193T3 (zh)
PL (1) PL3700268T3 (zh)
RU (1) RU2761443C2 (zh)
TW (1) TWI779117B (zh)
WO (4) WO2019075763A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115915072A (zh) * 2021-08-26 2023-04-04 大唐移动通信设备有限公司 一种端到端的pdu会话管理方法、装置及网络设备
US12213194B2 (en) 2019-06-21 2025-01-28 Nokia Technologies Oy Method and apparatus for admission control of sessions based on priority

Families Citing this family (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111182572B (zh) * 2017-10-20 2021-03-05 Oppo广东移动通信有限公司 用于传输数据的方法、终端设备和网络设备
CN110149651B (zh) * 2018-02-13 2021-09-14 华为技术有限公司 一种确定ssc模式的方法及装置
CN112087815B (zh) * 2019-06-13 2023-03-10 华为技术有限公司 通信方法、装置及系统
CN110474969B (zh) * 2019-07-29 2021-07-16 华为技术有限公司 会话管理方法及装置
CN110557798B (zh) * 2019-08-26 2022-08-12 中国联合网络通信集团有限公司 一种确定ursp的方法及装置
JP7401567B2 (ja) * 2019-09-12 2023-12-19 オッポ広東移動通信有限公司 無線通信の方法および装置
WO2021066423A1 (en) 2019-10-02 2021-04-08 Samsung Electronics Co., Ltd. Method and device for data rate control in network slice in wireless communication system
EP4079048A1 (en) * 2019-12-19 2022-10-26 Telefonaktiebolaget Lm Ericsson (Publ) Slice and/or subscriber identification module device lock
CN113365267B (zh) * 2020-03-06 2025-02-18 华为技术有限公司 通信方法和装置
WO2021201448A1 (en) * 2020-03-30 2021-10-07 Samsung Electronics Co., Ltd. Methods and systems for managing continuity of data flow in 5g networks
US12363616B2 (en) * 2020-05-21 2025-07-15 Apple Inc. Enhancements for handling network slice quota
CN115868207B (zh) * 2020-05-28 2025-03-14 高通股份有限公司 建立协议数据单元会话的方法
CN115428362B (zh) * 2020-06-03 2025-06-03 Oppo广东移动通信有限公司 信息处理方法及装置
CN113950106B (zh) * 2020-07-15 2023-07-07 华为技术有限公司 多接入连接建立的方法、装置和系统
CN114080056B (zh) * 2020-08-13 2024-08-09 中国移动通信有限公司研究院 一种会话更新方法、终端和网络侧设备
CN112188643B (zh) * 2020-10-09 2022-11-15 哲库科技(北京)有限公司 Pdu会话的建立方法、装置、终端及存储介质
CN114697998A (zh) * 2020-12-28 2022-07-01 中国移动通信有限公司研究院 协商方法、装置、设备及可读存储介质
CN116250360A (zh) * 2021-01-11 2023-06-09 Oppo广东移动通信有限公司 一种连接建立方法及装置、网络设备
WO2022160123A1 (zh) * 2021-01-27 2022-08-04 Oppo广东移动通信有限公司 接入方式选择方法、终端设备和网络设备
WO2022165787A1 (zh) * 2021-02-07 2022-08-11 Oppo广东移动通信有限公司 参数配置方法、装置、设备及存储介质
CN115334138B (zh) * 2021-04-26 2023-09-01 华为技术有限公司 Quic数据传输方法、装置、客户端及服务端
CN113225124B (zh) * 2021-05-07 2022-04-19 广州爱浦路网络技术有限公司 卫星终端端对端通信链路的建立方法、系统、装置及介质
CN115473814B (zh) * 2021-05-24 2025-01-24 中国移动通信有限公司研究院 一种网络切片连接配置方法、装置及网络设备
CN115412979B (zh) * 2021-05-28 2025-06-17 展讯半导体(南京)有限公司 一种会话切换方法、装置、芯片及模组设备
CN113423073B (zh) * 2021-06-08 2023-01-31 Oppo广东移动通信有限公司 消息处理方法、装置、电子设备和存储介质
CN113163511B (zh) * 2021-06-28 2021-10-26 中移(上海)信息通信科技有限公司 信息处理方法、装置、网络网元、终端及可读存储介质
CN117529966A (zh) * 2021-07-15 2024-02-06 Oppo广东移动通信有限公司 一种数据传输方法及装置、终端设备、网络设备
CN113795019B (zh) * 2021-08-09 2022-12-30 华为技术有限公司 一种通信控制方法和通信设备
EP4152045A1 (en) 2021-09-16 2023-03-22 Samsung Electronics Co., Ltd. Image sensor for measuring distance and camera module including the same
CN118077305A (zh) * 2021-09-30 2024-05-24 三星电子株式会社 在nsacf处维持ma pdu会话的无线网络和方法
WO2023058134A1 (ja) * 2021-10-05 2023-04-13 楽天モバイル株式会社 原因特定システム及び原因特定方法
CN116074921A (zh) * 2021-11-02 2023-05-05 广州三星通信技术研究有限公司 网络切片连接方法、装置、设备及介质
CN116346882A (zh) * 2021-12-24 2023-06-27 中移(成都)信息通信科技有限公司 一种会话处理方法、装置、通信设备和存储介质
CN116506891A (zh) * 2022-01-18 2023-07-28 北京小米移动软件有限公司 Ursp信息的传输方法、装置及存储介质
CN116527560A (zh) * 2022-01-20 2023-08-01 广州三星通信技术研究有限公司 更新用户设备路由选择策略的方法、用户设备和服务器
CN114915996B (zh) * 2022-05-16 2024-10-25 Oppo广东移动通信有限公司 通信异常处理方法及相关装置
CN114666919B (zh) * 2022-05-18 2022-08-30 广州世炬网络科技有限公司 随机接入方法、信息广播方法、装置及电子设备
CN115696491A (zh) * 2022-09-27 2023-02-03 中国联合网络通信集团有限公司 协议数据单元会话建立方法、装置和设备
CN119815575B (zh) * 2023-10-10 2025-11-14 中国电信股份有限公司技术创新中心 一种协议数据单元pdu会话建立方法及相关装置
CN120825819A (zh) * 2024-04-11 2025-10-21 大唐移动通信设备有限公司 业务会话建立方法、装置及可读存储介质
WO2026044216A1 (en) * 2024-08-22 2026-02-26 Dish Wireless L.L.C. Managing priority traffic in a wireless network
WO2026063597A1 (en) * 2024-09-20 2026-03-26 Samsung Electronics Co., Ltd. Managing network slicing capability of ue in wireless network

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107018194A (zh) * 2017-04-07 2017-08-04 厦门天锐科技股份有限公司 一种策略及时正确下载的实现方法
US20170303259A1 (en) * 2016-04-18 2017-10-19 Electronics And Telecommunications Research Institute Communication method and apparatus using network slicing

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100464308C (zh) 2007-04-20 2009-02-25 北京搜狗科技发展有限公司 一种用户词库同步更新的方法和系统
CN101651909B (zh) 2008-08-12 2012-03-07 华为技术有限公司 无线链路建立的请求方法、设备和系统
EP2689567B1 (en) * 2011-03-22 2015-06-24 Telefonaktiebolaget L M Ericsson (publ) Network node and method to route through or around traffic detection function nodes
EP2849488A1 (en) 2012-05-10 2015-03-18 Fujitsu Limited Mobile setting negotiation method and device
CN103546304B (zh) 2012-07-11 2017-08-25 华为技术有限公司 业务处理方法、设备及系统
CN103428708B (zh) 2013-08-08 2016-03-16 中国科学院计算技术研究所 一种认知无线网络中的无线接入方法和系统
US9860872B2 (en) 2014-06-03 2018-01-02 Intel Corporation In-band control signaling for integrated WLAN/3GPP RAT architectures
CN112911726B (zh) 2014-06-19 2023-04-07 北京三星通信技术研究有限公司 一种用户平面承载建立的方法及装置
ES2926077T3 (es) 2014-09-05 2022-10-21 Huawei Tech Co Ltd Método y aparato de negociación de las políticas de descarga
US20190037636A1 (en) 2016-02-17 2019-01-31 Lg Electronics Inc. Method for transmitting/receiving location registration-related message in wireless communication system and apparatus for same
CN107241764B (zh) * 2016-03-29 2020-11-06 电信科学技术研究院 一种上行、下行小数据传输方法及装置
US10667181B2 (en) * 2016-04-04 2020-05-26 Motorola Mobility Llc PDU sessions with various types of session continuity
CN106155818B (zh) 2016-06-17 2018-09-07 腾讯科技（深圳）有限公司 一种终端拉取信息的处理方法和终端以及服务器
CN106900081B (zh) 2016-08-23 2019-06-25 中国移动通信有限公司研究院 接入网节点粒度的用户面数据隧道传输的方法及装置
CN106851856B (zh) 2016-12-23 2019-04-09 电信科学技术研究院有限公司 一种基于移动中继的无线通信建立方法及网络设备
CN107018542A (zh) 2017-03-27 2017-08-04 中兴通讯股份有限公司 网络系统中状态信息的处理方法、装置及存储介质
US10820185B2 (en) * 2017-05-08 2020-10-27 Qualcomm Incorporated Mobility between areas with heterogeneous network slices
JP2020113808A (ja) 2017-05-09 2020-07-27 シャープ株式会社 端末装置、ａｍｆ、ｓｍｆ、コアネットワーク装置、及び通信制御方法
JP6854712B2 (ja) * 2017-06-19 2021-04-07 シャープ株式会社 Ｕｅ及びｕｅの通信制御方法
WO2018236164A1 (ko) 2017-06-21 2018-12-27 엘지전자(주) 무선 통신 시스템에서 서비스 요청 절차 수행 방법 및 이를 위한 장치
IL272552B2 (en) * 2017-08-11 2023-09-01 Idac Holdings Inc Traffic routing and switching between multiple access networks
CN111182572B (zh) 2017-10-20 2021-03-05 Oppo广东移动通信有限公司 用于传输数据的方法、终端设备和网络设备
US10855814B2 (en) * 2017-10-20 2020-12-01 Comcast Cable Communications, Llc Non-access stratum capability information

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170303259A1 (en) * 2016-04-18 2017-10-19 Electronics And Telecommunications Research Institute Communication method and apparatus using network slicing
CN107018194A (zh) * 2017-04-07 2017-08-04 厦门天锐科技股份有限公司 一种策略及时正确下载的实现方法

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "PDU Session vs PDU Session Resource", 3GPP TSG-RAN WG3 MEETING #97 R3-173219, 25 August 2017 (2017-08-25), XP051320048 *
ERICSSON: "TS 23.501: Clean up of PCF and Reference Point Names for PCC", SA WG2 MEETING #121 S2-173014, 19 May 2017 (2017-05-19), XP051281524 *
OPPO: "Updating for clause 6.1.2.2 in TS 23503", TS 23503. SAWG2 MEETING #123 S2-176999, 17 October 2017 (2017-10-17), XP051359695 *
See also references of EP3700268A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12213194B2 (en) 2019-06-21 2025-01-28 Nokia Technologies Oy Method and apparatus for admission control of sessions based on priority
CN115915072A (zh) * 2021-08-26 2023-04-04 大唐移动通信设备有限公司 一种端到端的pdu会话管理方法、装置及网络设备

Also Published As

Publication number Publication date
EP3700268A4 (en) 2020-10-14
RU2761443C2 (ru) 2021-12-08
PL3700268T3 (pl) 2022-02-07
EP3691380A4 (en) 2020-11-11
ES2900193T3 (es) 2022-03-16
CN110809899A (zh) 2020-02-18
KR102370267B1 (ko) 2022-03-03
AU2017436351B2 (en) 2023-08-03
JP7182621B2 (ja) 2022-12-02
TW201931935A (zh) 2019-08-01
CN111654922B (zh) 2022-04-15
JP2020537855A (ja) 2020-12-24
RU2020116371A (ru) 2021-11-22
US20220159781A1 (en) 2022-05-19
US11330666B2 (en) 2022-05-10
WO2019075816A1 (zh) 2019-04-25
BR112020007560A2 (pt) 2020-09-24
EP3700268A1 (en) 2020-08-26
EP3691380A1 (en) 2020-08-05
AU2018353168A1 (en) 2020-06-04
CN111052832A (zh) 2020-04-21
KR102477774B1 (ko) 2022-12-14
KR20200071106A (ko) 2020-06-18
RU2020116371A3 (zh) 2021-11-22
US11304260B2 (en) 2022-04-12
KR20220030323A (ko) 2022-03-10
AU2017436351A1 (en) 2020-06-11
US20200296777A1 (en) 2020-09-17
EP3700268B1 (en) 2021-10-06
CN111654922A (zh) 2020-09-11
WO2019076167A1 (zh) 2019-04-25
TWI779117B (zh) 2022-10-01
KR20200074973A (ko) 2020-06-25
JP2021502731A (ja) 2021-01-28
JP7063988B2 (ja) 2022-05-09
KR102477765B1 (ko) 2022-12-14
CN111182572A (zh) 2020-05-19
EP3691380B1 (en) 2023-01-18
WO2019076075A1 (zh) 2019-04-25
CN110809899B (zh) 2024-03-01
CN111052832B (zh) 2025-07-01
CA3079480A1 (en) 2019-04-25
EP3965367A1 (en) 2022-03-09
CA3079480C (en) 2023-06-13
CN111182572B (zh) 2021-03-05
US20200245405A1 (en) 2020-07-30

Similar Documents

Publication Publication Date Title
WO2019075763A1 (zh) 用于传输数据的方法、终端设备和网络设备
CN112913212A (zh) 控制面-用户面分离的用户面功能控制
TW201935906A (zh) 無線通訊的方法、網路設備和終端設備
CN113286291A (zh) 多接入场景中的连接处理方法和装置
WO2019127038A1 (zh) 用于数据传输的方法、终端设备和网络设备
CN111034316B (zh) 用于传输数据的方法、终端设备和会话管理功能smf设备
WO2019028795A1 (zh) 确定业务路径的方法和设备
WO2019061037A1 (zh) 用于数据处理的方法和终端设备

Legal Events

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

Ref document number: 17928855

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3079480

Country of ref document: CA

Ref document number: 2020521884

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207014334

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017928855

Country of ref document: EP

Effective date: 20200520

ENP Entry into the national phase

Ref document number: 2017436351

Country of ref document: AU

Date of ref document: 20171020

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020007560

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112020007560

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200416