WO2022222753A1 - 一种网络拥塞的处理方法、装置、终端、存储介质 - Google Patents

一种网络拥塞的处理方法、装置、终端、存储介质 Download PDF

Info

Publication number
WO2022222753A1
WO2022222753A1 PCT/CN2022/085426 CN2022085426W WO2022222753A1 WO 2022222753 A1 WO2022222753 A1 WO 2022222753A1 CN 2022085426 W CN2022085426 W CN 2022085426W WO 2022222753 A1 WO2022222753 A1 WO 2022222753A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
rule table
channel
network
network congestion
Prior art date
Application number
PCT/CN2022/085426
Other languages
English (en)
French (fr)
Inventor
杨海城
周金星
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2022222753A1 publication Critical patent/WO2022222753A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a method, device, terminal, and storage medium for processing network congestion.
  • Network congestion is a continuous overloaded network state, which will cause the entire network performance to decline.
  • the terminal When network congestion occurs on a channel in an established Multi-Access Protocol Data Unit (MA PDU) session, the terminal will still initiate a session establishment request through the channel with network congestion, resulting in increased network congestion.
  • MA PDU Multi-Access Protocol Data Unit
  • the present application provides a method for dealing with network congestion, including: initiating a request for establishing a MA PDU session, and monitoring the network if there are a channel in which network congestion occurs and a channel in which the session is successfully established among multiple channels of the MA PDU session requested to be established.
  • the steering, switching, and splitting (Access Traffic Steering, Switching, Splitting, ATSSS) rule table of the access traffic delivered from the side, and the channel used by the terminal is determined according to the active pending mode in the ATSSS rule table.
  • the embodiment of the present application also provides a network congestion processing device, including a establishment module for initiating an establishment request of a multiple access packet data unit MA PDU session; a management module for when the request for establishment of the MA PDU session is established.
  • a network congestion processing device including a establishment module for initiating an establishment request of a multiple access packet data unit MA PDU session; a management module for when the request for establishment of the MA PDU session is established.
  • the multiple channels when there is a channel with network congestion and a channel for which a session is successfully established, monitor the ATSSS rule table issued by the network side; determine the channel used by the terminal according to the active-pending mode in the ATSSS rule table.
  • An embodiment of the present application further provides a terminal, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein, the memory stores instructions that can be executed by the at least one processor , the instructions are executed by the at least one processor, so that the at least one processor can execute the above-mentioned method for processing network congestion.
  • the embodiments of the present application further provide a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the above-mentioned method for processing network congestion is implemented.
  • FIG. 1 is a flowchart of a method for processing network congestion according to an embodiment of the present application
  • FIG. 2 is a flowchart of a method for processing network congestion including a registration process according to another embodiment of the present application
  • FIG. 3 is a flowchart of a method for processing network congestion including a process of determining the establishment result of each session channel according to another embodiment of the present application;
  • FIG. 4 is a flowchart of a method for processing network congestion including a new MA PDU session process according to another embodiment of the present application
  • Fig. 5 is the schematic diagram of S-NSSAI data structure in the related art
  • FIG. 6 is a flowchart of determining S-NSSAI according to another embodiment of the present application.
  • FIG. 7 is a flowchart of a method for processing network congestion according to another embodiment of the present application, including a process of determining network slicing according to a locally stored URSP rule table;
  • FIG. 8 is a flowchart of a method for processing network congestion including a process of determining a network slice according to a network-side URSP according to another embodiment of the present application;
  • FIG. 9 is a schematic diagram of an apparatus for processing network congestion according to another embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a terminal according to another embodiment of the present application.
  • the main purpose of the embodiments of the present application is to provide a method for processing network congestion, which can avoid aggravation of network congestion.
  • the method for dealing with network congestion establishes a MA PDU session, and there are multiple session channels in the MA PDU session.
  • Traffic steering, switching, and splitting Access Traffic Steering, Switching, Splitting, ATSSS
  • the ATSSS rule table is updated by the network side according to the network situation.
  • the Steering Mode conversion mode in the ATSSS rule table is Active-Standby active-pending mode Instruct the terminal to use a specified channel. The terminal will use the Active active channel first. When the Active channel is unavailable, it will use the Standby pending channel instead.
  • the network side will preferentially select the channel that successfully established the session to be designated as the Active channel.
  • Specifying the channel in the MA PDU session according to the Active-Standby mode in the ATSSS rule table can ensure that the terminal uses the currently specified channel, that is, the channel for which the session is successfully established, for communication, and prevents the terminal from using the currently unspecified channel, that is, avoids the occurrence of terminal use.
  • the communication is performed on the network congested channel, so as to prevent the terminal from continuing to send the session establishment request through the network congested channel, thereby avoiding network congestion on the network congested channel from aggravating.
  • the embodiment of the present application provides a method for processing network congestion, which is applied to a terminal, such as a mobile phone, a tablet, etc.
  • a terminal such as a mobile phone, a tablet, etc.
  • the network side of this embodiment needs to support the ATSSS function.
  • the ATSSS Access Traffic Steering, Switching, Splitting, access traffic steering, switching, and splitting
  • the terminal initiates a request for establishing a Multi-Access Protocol Data Unit (MA PDU) session; if among the multiple channels of the MA PDU session requested to be established, there are channels where network congestion occurs and If the session is successfully established, monitor the ATSSS rule table issued by the network side; determine the channel used by the terminal according to the active-pending mode in the ATSSS rule table. The terminal determines the channel to be used according to the designated channel in the Active-Standby active-pending mode in the ATSSS rule table, which ensures that the mobile terminal will not establish a session through the channel where network congestion occurs, thereby avoiding the aggravation of network congestion.
  • MA PDU Multi-Access Protocol Data Unit
  • Step 101 initiate the establishment request of the MA PDU session. That is, an application for a MAPDU session is initiated to the network side.
  • a data protocol unit (Protocol Data Unit, PDU) session can transmit data through multiple access technologies, and this PDU session is called a MAPDU session.
  • MAPDU sessions can use both 3rd Generation Partnership Project (3GPP) access technologies, such as Long Term Evolution (LTE), New Radio (NR), and non-3GPP access technologies, such as Wireless Local Area Network (WirelessLocalAreaNetwork, WLAN).
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • NR New Radio
  • WLAN Wireless Local Area Network
  • a MAPDU session includes multiple channels.
  • a MAPDU session includes a 5G channel using NR access technology and a WiFi channel using WLAN access technology.
  • a MAPDU session includes a 5G channel using NR technology and a WLAN access technology.
  • the WIFI1 channel and the WIFI2 channel of the technology for example, the MAPDU session includes the 5G1 channel and the 5G2 channel using the NR access technology and the WIFI channel using the WLAN access technology.
  • the number of channels specifically included in the MA PDU session, and the access technology used by each channel can be created according to actual requirements, which does not cause restrictions on this embodiment.
  • step 102 is entered.
  • Step 102 it is judged whether there is a channel in which network congestion occurs and a channel in which the session is successfully established among the multiple channels of the established MA PDU session.
  • the reason for the session establishment rejection message is insufficient resources; it is determined that there is a channel in which network congestion occurs in the MA PDU session.
  • the terminal monitors whether it receives a PDU Session Establishment Reject session establishment rejection message from the network side, and carries the reason: insufficient resources. If the message is monitored, it is determined that there is a channel with network congestion in the MA PDU. Channels where MAPDUs are congested. If the terminal also receives a session establishment reception message based on a channel, and the successfully established session channel and the session channel in which network congestion occurs have the same PDU Session ID, that is, the PDU session ID, it is determined that multiple channels in the MAPDU have both In the channel where network congestion occurs, there are also channels where the session is established successfully. When establishing a session in this embodiment, at least one channel in the MA PDU session is refused to establish a session due to insufficient resources and congestion on the network side.
  • Step 103 If there is a channel with network congestion and a channel for which the session is successfully established, monitor the ATSSS rule table delivered by the network side.
  • step 104 is performed.
  • Step 104 Determine the channel used by the terminal according to the active-pending mode in the ATSSS rule table.
  • the terminal parses the ATSSS rule table and saves it locally. If the Active channel in the ATSSS rule table is available, the terminal designates the channel as the Active channel. When the channel is unavailable, the terminal designates the channel as the standby channel.
  • the network side can instruct the terminal to use a specified channel through the "Active-Standby" mode in the Steering Mode conversion mode, that is, the active-pending mode.
  • the terminal uses the Active channel first, and uses the Standby channel instead when the channel is unavailable.
  • ATSSS parameter contents including an ATSSS rule in the 3GPP TS 24.193 specification records the coding specification of the Steeringmode mode, as shown in Table 1 below.
  • ATSSS parameter contents including an ATSSS rule in the 3GPP TS 24.193 specification records the encoding specification of the acitve-standby mode in the Steering mode mode, as shown in Table 2 below.
  • the following takes the established MA PDU session including the 5G channel using the NR access technology and the WIFI channel using the WLAN access technology as an example to illustrate the processing method of network congestion.
  • the terminal device establishes a MAPDU session. If the WIFI channel in the MAPDU is congested and the session based on the 5G channel is successfully established, it monitors the ATSSS rule table delivered by the network side. If the ATSSS rule table is monitored, the rule table is parsed and saved locally. If the active channel specified in the active-standby mode in the ATSSS rule table is parsed as the 5G channel, the terminal uses the 5G channel and does not use the WIFI channel, which prevents the terminal from sending requests to the network side through the WIFI channel, which makes the network congestion channel more congested.
  • the ATSSS rule table in this embodiment is delivered by the network side, and the network will consider the network performance.
  • the available channels will be preferentially selected, and the channel that does not experience network congestion is the active channel.
  • the method in this embodiment can be applied not only to the scenario of network congestion, but also to scenarios where network congestion has not yet occurred, and the session can be accessed normally, but the data transmission is slow, for example, multiple people are connected in a certain area.
  • the terminal cannot use the WIFI channel for normal data transmission.
  • the designated channel can also be determined through the ATSSS rule table.
  • the mobile terminal when there is a channel in the MAPDU session that is not successfully established due to network congestion, the mobile terminal will still apply to the network side to establish a session through the congested channel, resulting in aggravated network congestion on the channel.
  • This embodiment is based on the ATSSS rule table.
  • the specified channel in Active-Standby active-pending mode determines the channel used by the terminal, so that the terminal does not use another channel, that is, the mobile terminal will not attempt to establish a session through a non-specified channel, because the ATSSS rule table is based on the network side
  • the network side will determine the information in the ATSSS rule table based on network performance and other conditions.
  • the network side When network congestion occurs, the network side will preferentially select the channel where the session is successfully established as the Active channel, and the channel where network congestion occurs as the Standby channel. Therefore, the terminal The channel to be used is determined according to the designated channel in the Active-Standby active-pending mode in the ATSSS rule table, which ensures that the mobile terminal will not establish a session through the channel where network congestion occurs, thereby avoiding the aggravation of network congestion.
  • step 101 before step 101 , it further includes step 100 : registering with the network and determining that the 5G network side supports the ATSSS function. That is, the terminal registers to the 5G network and finds that the network supports the ATSSS function.
  • the terminal determines whether the network supports the ATSSS function by detecting the ats_ind field of the Registration Accept message sent by the 5G network side.
  • the following is a procedure for judging whether the network supports the ATSSS function by using the ats_ind field of the Registration Accept message, but this embodiment may also judge in other ways, which is not limited in this embodiment.
  • This step can be applied to the case where the terminal has not yet registered with the network side, and after registration, it is queried whether the network supports the ATSSS function.
  • step 102 may be implemented in the following manner:
  • Step 1021 Determine whether all session channels in the MAPDU session are successfully established. If the establishment is successful, go to Step 1022. If the establishment fails, go to Step 1023.
  • step 1022 monitors whether the PDU Session Establishment Accept message based on all channels is received from the network side, if it is monitored, it means that the MAPDU session is established successfully, and step 1022 is performed, otherwise, step 1023 is performed.
  • Step 1022 determine whether there is a session channel that needs to release session resources and does not need to be released in the MA PDU session.
  • step 103 If the session channel of the session resource exists, go to step 103, otherwise, end the process.
  • a session resource release message When a session resource release message is received, it indicates that although the MAPDU session is successfully established, with the change of network transmission traffic, resources on the network side are insufficient and network congestion occurs. , causing at least one channel of the MAPDU to be required to release resources and refuse to establish a session. For example, if the terminal monitors that the network side sends a PDU Session Modification Reject or PDU Session Release message to the terminal, and carries the reason: insufficient resource, it is determined that there is a channel with network congestion in the MAPDU session. When there is a channel that needs to release session resources and there is a channel that does not need to release session resources, it indicates that there are channels in the MAPDU session where network congestion occurs and channels where session establishment is successful.
  • Step 1023 it is judged whether there is a successfully established session channel in the established MAPDU session, if so, step 103 is performed, otherwise, the process ends.
  • the channel used by the terminal can still be determined based on the ATSSS table, thereby avoiding the aggravation of network congestion.
  • the MAPDU session can be re-established based on a new network slice, and the steps are as follows:
  • Step 105 If network congestion occurs on all channels in the MA PDU session, the S-NSSAI used to identify the network slice is determined according to the terminal routing policy URSP rule table.
  • the User Routing Selection Policy (URSP) rule table has a route selection descriptor (rsd), the routing component in rsd has network slice selection parameters, and the MAPDU session uses the network slice selection parameters in rsd Determine the S-NSSAI (Single Network Slice Selection Assistance Information) used to identify the network slice.
  • rsd route selection descriptor
  • S-NSSAI Single Network Slice Selection Assistance Information
  • S-NSSAI identifies a network slice.
  • the structure of S-NSSAI is shown in Figure 5 and consists of two parts:
  • SST Session/Service type
  • slice/service type which refers to the expected network slice behavior in terms of functions and services.
  • SST can be a standard value, such as Enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (uRLLC), MassibeLot (MIoT), or a non-standard value.
  • eMBB Enhanced Mobile Broadband
  • uRLLC Ultra Reliable Low Latency Communications
  • MIoT MassibeLot
  • non-standard value such as Enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (uRLLC), MassibeLot (MIoT), or a non-standard value.
  • SD Slice Differentiator
  • slice differentiator this is optional information, supplementary slice/service type to distinguish multiple network slices of the same slice/service type.
  • the length of SST is 1 byte, and the value from 0 to 127 is the value range of standard SST.
  • the current protocol only uses three values.
  • the value from 128 to 255 belongs to the operator-defined range.
  • the operator-defined value is only available on this network. It is valid under the standard value, and it is common to the whole network for the standard value.
  • step 106 is executed.
  • Step 106 initiate a new MAPDU session establishment request, and the new MAPDU session establishment request carries the S-NSSAI.
  • the terminal will carry S-NSSAI when creating a new MA PDU session, indicating the network slice it wishes to apply for.
  • a new network slice is obtained based on the URSP table, and a new MA PDU session is created based on the new network slice, so as to prevent the MA PDU session from being sent to the network where it occurs.
  • a congested network continues to initiate session establishment requests, resulting in more serious network congestion.
  • a new S-NSSAI network slice may also be determined when a channel with network congestion occurs in the MAPDU session.
  • step 105 includes:
  • Step 1051 Check whether the URSP rule table delivered by the network side is monitored, if yes, go to Step 1052, otherwise go to Step 1053.
  • Step 1052 If the URSP rule table delivered by the network side is monitored, the S-NSSAI is determined according to the URSP rule table delivered by the network side.
  • the monitored URSP rule table delivered by the network side is parsed and saved.
  • Step 1053 If the URSP rule table issued by the network side is not monitored, the S-NSSAI is determined according to the locally stored URSP rule table.
  • the mobile terminal may not monitor the URSP rule table, and directly determine the S-NSSAI according to the URSP rule table saved locally.
  • the URSP rules may be provided by the network side or may be pre-configured in the UE to guide the UE to establish a data routing path on the PDU session by using different access networks.
  • determining the S-NSSAI according to the URSP rule table delivered by the network side in step 1052 can be implemented by the following steps: comparing the traffic descriptor of the MA PDU session with the traffic description in the URSP rule table delivered by the network side character matching to obtain a matching entry; the S-NSSAI is determined according to the routing descriptor in the matching entry.
  • the URSP rule table delivered by the network side is parsed and saved, and the Traffic Descriptor traffic descriptor of the MAPDU session is matched with the rule table delivered by the network side, thereby obtaining the S-NSSAI of the specified network slice.
  • the traffic descriptor field in this embodiment may include: DNN (Data Network Name, data network name), application APP ID, FQDN (Fully Qualified Domain Name, fully qualified domain name), but is not limited to this.
  • the terminal matches APP1 with the traffic descriptor of the entry with the highest priority according to the priority in the URSP rule table from high to low.
  • the traffic descriptor of the highest entry is APP2, which is different from APP1, then APP1 is matched with the traffic descriptor of the entry with the second highest priority.
  • the traffic descriptor of the entry with the second highest priority is APP3 , which is different from the traffic descriptor APP1 in the MAPDU, then it is matched with the traffic descriptor of the entry with the third highest priority, and so on, until a matching entry is found, and the routing description in the matching entry
  • the S-NSSAI of the specified network slice is obtained from the character rsd.
  • the URSP rule table on the network side is updated based on the quality of the network slice, and matching is performed based on the URSP updated on the network side, which is beneficial to find a network slice with good network quality and no network congestion yet.
  • determining the S-NSSAI according to the locally stored URSP rule table in step 1053 can be achieved by the following steps: monitoring the ATSSS rule table issued by the network side; In order, the traffic descriptor field in the ATSSS rule table is matched with the traffic descriptor field in the locally stored URSP rule table to obtain the matching table entry in the URSP rule table; described S-NSSAI.
  • An entry in the URSP rule table is a URSP rule.
  • the terminal matches the locally stored URSP rule list according to the priority in the ATSSS rule table from high to low, according to the Traffic Descriptor traffic descriptor field in the ATSSS rule, so as to obtain the S-slice of the specified network slice. NSSAI.
  • the traffic descriptor is APPID
  • the APPID in the entry with the highest priority in the ATSSS rule table delivered by the network side is APP1
  • APP1 is matched with the traffic descriptor of each entry in the URSP rule table. If there is no match If successful, the entry with the second highest priority in the ATSSS rule table is selected for matching. If the APPID of the entry with the second highest priority in the ATSSS rule table is APP2, the entry with the Nth highest priority in the URSP rule table is also APP2 , then the entry with the Nth highest priority is the matching entry, and the S-NSSAI is obtained according to the route selector rsd in the matching entry.
  • the terminal device If the terminal device matches a URSP rule, the terminal device will establish a MA PDU session according to the network slice in the URSP rule. With a higher priority, the terminal will continue to send session establishment requests based on the network slice in the congested state, which will cause the congested network to become more congested. To avoid this situation, in this embodiment, the terminal will mark the URSP rule as not possible and receive the ATSSS rule table sent by the network side, and match it with the URSP rule table according to the priority in the ATSSS rule table, because the priority in the ATSSS rule table is updated in real time by the network side, reflecting the network situation, so that Matching, it is helpful to determine the network slice without network congestion.
  • the monitoring network side delivers the ATSSS rule table. If the monitored ATSSS rule table carries the identifier of the network slice, for example: S-NSSAI, then The MAPDU session is re-established according to the carried network slice identifier, and the request for the re-established MAPDU session carries the identifier of the network slice.
  • the network slice can be determined based on the ATSSS table.
  • the monitored ATSSS rule table does not carry the identifier of the network slice, it can be determined according to the URSP rule table. Determine S-NSSAI.
  • the present application provides another method for processing network congestion, as shown in FIG. 7 , including:
  • Step 101 initiate the establishment request of the MA PDU session.
  • Step 102 it is judged whether there is a channel in which network congestion occurs and a channel in which the session is successfully established among the multiple channels of the established MA PDU session. If yes, go to step 103; otherwise, go to step 1054.
  • Step 103 Monitor the ATSSS rule table delivered by the network side.
  • Step 104 if the ATSSS rule table is monitored, the channel used by the terminal is determined according to the active-pending mode in the ATSSS rule table.
  • Step 1054 If network congestion occurs on all channels in the MA PDU session, monitor the ATSSS rule table delivered by the network side.
  • Step 1055 Determine the S-NSSAI according to the ATSSS rule table delivered by the network side and the URSP rule table stored locally.
  • the flow descriptor of the MA PDU session is matched with the flow descriptor in the URSP rule table issued by the network side to obtain a matching entry; the S-NSSAI is determined according to the routing descriptor in the matching entry.
  • Step 106 initiate a new MA PDU session establishment request, and the new MA PDU session establishment request carries the S-NSSAI.
  • a MAPDU session when a MAPDU session is established, if there is a channel in the MAPDU session and network congestion occurs, if there is a successfully established session channel, the specified channel is determined based on the ATSSS rule table, and the terminal uses the specified channel instead of the network. Congested channel, to prevent the terminal from continuously sending session establishment requests through the channel with network congestion, resulting in aggravation of network congestion; in the case of network congestion on all channels, create a MAPDU session based on a new network slice to avoid continuing to the network with network congestion. Sending a session establishment request causes the network with network congestion to become more congested.
  • the terminal when there is a session channel successfully established, the terminal is specified to use the channel through the ATSSS rule table, instead of re-establishing the MAPDU session based on the new network slice, It can save terminal resources.
  • the present application determines a new network slice based on the ATSSS rule table and the locally stored URSP rule table, and uses the rule priority of the ATSSS rule table to avoid information such as the rule priority of the locally stored URSP rule table. There is no update to the problem that the network slice used is not accurately found.
  • the present application provides another method for processing network congestion, as shown in FIG. 8 , including:
  • Step 101 initiate the establishment request of the MA PDU session.
  • Step 1021 determine whether all session channels in the MA PDU session are successfully established, if the establishment is successful, execute step 1022, and if the establishment fails, execute step 1023.
  • step 1022 monitors whether the PDU Session Establishment Accept message based on all channels is received from the network side, if it is monitored, it means that the MA PDU session is established successfully, and step 1022 is performed, otherwise, step 1023 is performed.
  • Step 1022 determine whether there is a session channel that needs to release session resources and does not need to be released in the MA PDU session.
  • step 103 If the session channel of the session resource exists, go to step 103; otherwise, go to step 1056.
  • Step 1023 determine whether there is a session channel established successfully in the established MA PDU session, if so, go to step 103, otherwise go to step 1056.
  • Step 103 Monitor the ATSSS rule table delivered by the network side.
  • Step 104 if the ATSSS rule table is monitored, the channel used by the terminal is determined according to the active-pending mode in the ATSSS rule table.
  • Step 1056 if network congestion occurs on all channels in the MA PDU session, determine the S-NSSAI according to the URSP rule table delivered by the network side.
  • Step 106 initiate a new MA PDU session establishment request, and the new MA PDU session establishment request carries the S-NSSAI.
  • the applicable network slice is determined directly based on the URSP rule table delivered by the network side.
  • the URSP rule table delivered by the network side reflects the network situation and is helpful for finding the applicable network slice.
  • the embodiment of the present application also provides a network congestion processing device, as shown in FIG. 9 , including: a establishment module 901, for initiating an establishment request of a multi-access packet data unit MA PDU session; a management module 902, for when In the multiple channels of the MA PDU session requested to be established, when there is a channel where network congestion occurs and a channel where the session is successfully established, monitor the ATSSS rule table issued by the network side; according to the active-pending mode in the ATSSS rule table Determine the channel used by the terminal.
  • a network congestion processing device including: a establishment module 901, for initiating an establishment request of a multi-access packet data unit MA PDU session; a management module 902, for when In the multiple channels of the MA PDU session requested to be established, when there is a channel where network congestion occurs and a channel where the session is successfully established, monitor the ATSSS rule table issued by the network side; according to the active-pending mode in the ATSSS rule table Determine the channel used by the terminal.
  • the management module 902 is further configured to determine the S-NSSAI used to identify the network slice according to the terminal routing policy URSP rule table when network congestion occurs on all channels in the MA PDU session; the establishment module 901 is further configured to A new MA PDU session establishment request is initiated, wherein the new MA PDU session establishment request carries the S-NSSAI.
  • the management module 902 is further configured to determine the S-NSSAI according to the URSP rule table issued by the network side when monitoring the URSP rule table issued by the network side; when the URSP rule table issued by the network side is not monitored, Then the S-NSSAI is determined according to the locally stored URSP rule table.
  • the management module 902 is further configured to monitor the ATSSS rule table delivered by the network side; according to the order of priorities in the ATSSS rule table from high to low, the traffic descriptor field in the ATSSS rule table is stored with the local The flow descriptor field in the URSP rule table is matched to obtain the matching entry in the URSP rule table; the S-NSSAI is determined according to the routing descriptor in the matching entry.
  • the management module 902 is further configured to match the traffic descriptor of the MA PDU session with the traffic descriptor in the URSP rule table delivered by the network side to obtain a matching entry; according to the matching entry The routing descriptor in determines the S-NSSAI.
  • the management module 902 is further configured to monitor the PDU Session Establishment Reject session establishment rejection message sent by the network side, and the session establishment rejection message carries the reason of insufficient resources; then determine that there is an occurrence network in the MA PDU session Congested channel.
  • the management module 902 is further configured to, when listening to the PDU Session Modification Reject session modification rejection message or the PDU Session Release session release message, and the carrying reason is insufficient resources; then determine that there is a network congestion in the MA PDU session. aisle.
  • this embodiment is a device embodiment corresponding to the above-mentioned embodiment, and this embodiment can be implemented in cooperation with the above-mentioned embodiment.
  • the related technical details mentioned in the foregoing embodiment are still valid in this embodiment, and are not repeated here in order to reduce repetition.
  • the relevant technical details mentioned in this embodiment can also be applied to the above-mentioned embodiments.
  • each module involved in this embodiment is a logical module.
  • a logical unit may be a physical unit, a part of a physical unit, or multiple physical units.
  • a composite implementation of the unit in order to highlight the innovative part of the present application, this embodiment does not introduce units that are not closely related to solving the technical problem raised by the present application, but this does not mean that there are no other units in this embodiment.
  • An embodiment of the present application further provides a terminal, as shown in FIG. 10, comprising at least one processor 1001; and a memory 1002 connected in communication with the at least one processor; wherein, the memory stores data that can be The instructions are executed by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute the above-mentioned method for processing network congestion.
  • the memory and the processor are connected by a bus, and the bus may include any number of interconnected buses and bridges, and the bus connects one or more processors and various circuits of the memory.
  • the bus may also connect together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein.
  • the bus interface provides the interface between the bus and the transceiver.
  • a transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium.
  • the data processed by the processor is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor.
  • the processor is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Instead, memory may be used to store data used by the processor in performing operations.
  • Embodiments of the present application also provide a computer-readable storage medium storing a computer program.
  • the above method embodiments are implemented when the computer program is executed by the processor.
  • the aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例涉及通信领域，公开了一种网络拥塞的处理方法。本申请中，发起MA PDU会话的建立请求，若请求建立的MA PDU会话的多个通道中，存在发生网络拥塞的通道和会话建立成功的通道，则监听网络侧下发的接入流量的转向、切换、分流(Access Traffic Steering,Switching,Splitting，ATSSS)规则表，根据ATSSS规则表中的活跃待定模式确定终端使用的通道。

Description

一种网络拥塞的处理方法、装置、终端、存储介质
交叉引用
本申请基于申请号为“202110418353.3”、申请日为2021年4月19日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请实施例涉及通信领域，特别涉及一种网络拥塞的处理方法、装置、终端、存储介质。
背景技术
当网络中存在太多的流量导致数据包被延迟或丢失，从而降低网络性能，这种情况被称之为网络拥塞，网络拥塞是一种持续过载的网络状态，会导致整个网络性能下降，严重时甚至会导致网络通信业务陷入停顿。
当建立的多接入协议数据单元(Multi-Access Protocol Data Unit，MA PDU)会话中某通道发生网络拥塞，终端仍会通过发生网络拥塞的通道发起会话建立请求，导致网络拥塞情况加重。
发明内容
本申请提供一种网络拥塞的处理方法，包括：发起MA PDU会话的建立请求，若请求建立的MA PDU会话的多个通道中，存在发生网络拥塞的通道和会话建立成功的通道，则监听网络侧下发的接入流量的转向、切换、分流(Access Traffic Steering,Switching,Splitting，ATSSS)规则表，根据ATSSS规则表中的活跃待定模式确定终端使用的通道。
本申请实施例还提供了一种网络拥塞的处理装置，包括建立模块，用于发起多接入分组数据单元MA PDU会话的建立请求；管理模块，用于当请求建立 的所述MA PDU会话的多个通道中，存在发生网络拥塞的通道和会话建立成功的通道时，监听网络侧下发的ATSSS规则表；根据所述ATSSS规则表中的活跃-待定模式确定所述终端使用的通道。
本申请实施例还提供了一种终端，包括：至少一个处理器；以及，与所述至少一个处理器通信连接的存储器；其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行上述的网络拥塞的处理方法。
为实现上述目的，本申请实施例还提供了一种计算机可读存储介质，存储有计算机程序，计算机程序被处理器执行时实现上述的网络拥塞的处理方法。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定。
图1是根据本申请一实施例中的网络拥塞的处理方法的流程图；
图2是根据本申请另一实施例中的包括注册流程的网络拥塞的处理方法的流程图；
图3是根据本申请另一实施例中的包括确定各会话通道建立结果流程的网络拥塞的处理方法的流程图；
图4是根据本申请另一实施例中包括新建MA PDU会话流程的网络拥塞的处理方法的流程图；
图5是相关技术中S-NSSAI数据结构的示意图；
图6是根据本申请另一实施例中确定S-NSSAI的流程图；
图7是根据本申请另一实施例中包括根据本地保存的URSP规则表确定网络切片这一流程的网络拥塞的处理方法的流程图；
图8是根据本申请另一实施例中包括根据网络侧URSP确定网络切片这一流程的网络拥塞的处理方法的流程图；
图9是根据本申请另一实施例中网络拥塞的处理装置的示意图；
图10是根据本申请另一实施例中终端的结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的各实施例进行详细的阐述。然而，本领域的普通技术人员可以理解，在本申请各实施例中，为了使读者更好地理解本申请而提出了许多技术细节。但是，即使没有这些技术细节和基于以下各实施例的种种变化和修改，也可以实现本申请所要求保护的技术方案。以下各个实施例的划分是为了描述方便，不应对本申请的具体实现方式构成任何限定，各个实施例在不矛盾的前提下可以相互结合相互引用。
本申请实施例的主要目的在于提出一种网络拥塞的处理方法，能够避免网络拥塞情况加重。
本申请的实施例提出的网络拥塞的处理方法，建立MA PDU会话，MA PDU会话中有多个会话通道，若存在发生网络拥塞的通道和会话建立成功的通道，则获取网络侧发送的接入流量的转向、切换、分流(Access Traffic Steering,Switching,Splitting，ATSSS)规则表，ATSSS规则表是网络侧根据网络情况进行更新的，ATSSS规则表中Steering Mode转换模式的Active-Standby活跃-待定模式指示终端使用某个指定通道，终端优先使用Active活跃通道，在Active通道出现不可用的情况时，才会改用Standby待定通道，网络侧会优先选择会话建立成功的通道指定为Active通道，因此，根据ATSSS规则表中的Active-Standby模式指定MA PDU会话中的通道，能保证终端使用当前指定的通道，即会话建立成功的通道进行通信，避免终端使用当前未指定的通道，即避免终端使用发生网络拥塞的通道进行通信，从而避免终端继续通过发生网络拥塞的通道发送会话建立请求，进而避免发生网络拥塞的通道网络拥塞情况加重。
本申请的实施例提供一种网络拥塞的处理方法，应用于终端，如：手机、平板等，另外，本实施例的网络侧需支持ATSSS功能。ATSSS(Access Traffic Steering,Switching,Splitting，接入流量的转向、切换、分流)功能是3GPPR16版本引入的，主要用于终端MA(Multi-Access，多接入)业务的路径优选、无缝切换、多路并发等，提高用户体验。
本实施例中终端发起多接入分组数据单元(Multi-Access Protocol Data Unit，MA PDU)会话的建立请求；若请求建立的所述MA PDU会话的多个通道中，存在发生网络拥塞的通道和会话建立成功的通道，则监听网络侧下发的ATSSS规则表；根据ATSSS规则表中的活跃-待定模式确定终端使用的通道。使得终端根据ATSSS规则表中的Active-Standby活跃-待定模式中的指定通道确定使用的通道，保证了移动终端不会通过发生网络拥塞的通道建立会话，从而避免了网络拥塞情况加重。
下面将结合图1对本实施例的网络拥塞的处理方法的实现细节进行具体的说明，以下内容仅为方便理解提供的实现细节，并非实施本方案的必须。
步骤101，发起MA PDU会话的建立请求。即向网络侧发起MAPDU会话的申请。
在5G网络中，一个数据协议单元(Protocol Data Unit，PDU)会话可以通过多种接入技术传输数据，这种PDU会话被称为MAPDU会话。MAPDU会话可以既使用第三代合作伙伴项目(3rd Generation Partnership Project，3GPP)接入技术，例如：长期演进(LongTermEvolution，LTE)、新空口(NewRadio，NR)，又使用非3GPP接入技术，例如无线局域网(WirelessLocalAreaNetwork，WLAN)。
MAPDU会话包括多个通道，例如：MAPDU会话中包括使用NR接入技术的5G通道，和使用WLAN接入技术的WiFi通道，又例如：MAPDU会话中包括使用NR技术的5G通道和使用WLAN接入技术的WIFI1通道和WIFI2通道，又例如MAPDU会话中包括使用NR接入技术的5G1通道和5G2通道以及使用WLAN接入技术的WIFI通道。MA PDU会话中具体包括的通道数，和每个通道使用的接入技术可根据实际需求创建，不造成对本实施例的限制。
步骤101执行完成之后，进入步骤102。
步骤102，判断建立的MA PDU会话的多个通道中，是否存在发生网络拥塞的通道和会话建立成功的通道。
在一个例子中，若监听到网络侧发送的会话建立拒绝消息，会话建立拒绝消息携带理由为资源不足；则判定MA PDU会话中存在发生网络拥塞的通道。
若接收到基于某通道的会话建立接收消息，则判定MAPDU会话中存在会 话建立成功的通道。
例如，终端监听是否收到网络侧的PDU Session Establishment Reject会话建立拒绝消息，且携带理由：资源不足insufficient resource，若监听到该消息，则判定MA PDU中存在发生网络拥塞的通道，终端基于此确定MAPDU发生拥塞的通道。若终端还接收到基于某通道的会话建立接收消息，且建立成功的会话通道与发生网络拥塞的会话通道有相同的PDU SessionID即，PDU会话ID，则判定该MAPDU中的多个通道，既有发生网络拥塞的通道，也有建立会话成功的通道。本实施例在建立会话时，因资源不足，网络侧发生拥塞导致MA PDU会话中至少一个通道被拒绝建立会话。
步骤103，若存在发生网络拥塞的通道和会话建立成功的通道，则监听网络侧下发的ATSSS规则表。
若监听到网络侧下发的ATSSS规则表，执行步骤104。
步骤104，根据ATSSS规则表中的活跃-待定模式确定所述终端使用的通道。
具体地，终端在监听到网络侧下发的ATSSS规则表后，对ATSSS规则表进行解析并保存到本地，在ATSSS规则表中的Active通道可用的情况下，终端指定通道为Active通道，当Active通道不可用时，终端指定通道为standby通道。
为便于理解，以下示出ATSSS规则表在3GPP规范中规定的部分内容。
根据3GPP TS 24.193规范，网络侧可通过Steering Mode转换模式中的“Active-Standby”模式，即活跃-待定模式指示终端使用某个指定通道。终端优先使用Active这个通道，在该通道不可用的情况时，改用Standby通道。
3GPP TS 24.193规范中的Table 6.1.3.2-1:ATSSS parameter contents including an ATSSS rule中记载了Steeringmode模式的编码规范，如下表1所示。
表1
Figure PCTCN2022085426-appb-000001
3GPP TS 24.193规范中的Table 6.1.3.2-1:ATSSS parameter contents including an ATSSS rule中记载了Steering mode模式中的acitve-standby模式的编码规范，如下表2所示。
表2
Figure PCTCN2022085426-appb-000002
为便于理解，以下以建立的MA PDU会话包括使用NR接入技术的5G通道和WLAN接入技术的WIFI通道为例，阐述网络拥塞的处理方法，
终端设备建立MAPDU会话，若MAPDU中的WIFI通道发生网络拥塞，基于5G通道的会话建立成功，则监听网络侧下发的ATSSS规则表。若监听到ATSSS规则表，则解析规则表并保存到本地。若解析出ATSSS规则表中的acitve-standby模式中指定active通道为5G通道，终端使用5G通道，不使用WIFI通道，避免终端通过WIFI通道向网络侧发送请求，使得发生网络拥塞的通道更加拥塞。
本实施例中的ATSSS规则表是网络侧下发的，网络会考虑网络性能，在active-standby模式中会优先选择可用的，未发生网络拥塞的通道为active通道。
值得一提的是，本实施例的方法除了应用于网络拥塞的场景还可以应用于尚未产生网络拥塞，会话可以正常接入，但是数据传输较慢的场景，例如：在某一区域多人连接某一WIFi，WIFI虽能接入，但是终端无法使用WIFI通道进行正常的数据传输，此时，也可以通过ATSSS规则表确定指定通道。
相关技术中，当MAPDU会话中存在通道因网络拥塞没有建立成功，移动终端仍会通过发生拥塞的通道向网络侧申请建立会话，导致该通道网络拥塞情况加重，本实施例根据ATSSS规则表中的Active-Standby活跃-待定模式中的指定通道确定终端使用的通道，使得终端不使用另外的通道，也就是说，移动终端不会通过非指定的通道尝试建立会话，由于ATSSS规则表基于网络侧下发，网络侧会基于网络性能等情况确定ATSSS规则表中的信息，在发生网络拥塞时， 网络侧会优先选择会话建立成功的通道作为Active通道，发生网络拥塞的通道作为Standby通道，因此，终端根据ATSSS规则表中的Active-Standby活跃-待定模式中的指定通道确定使用的通道，保证了移动终端不会通过发生网络拥塞的通道建立会话，从而避免了网络拥塞情况加重。
在一些实施例中，如图2所示，在步骤101之前，还包括步骤100：注册到网络并确定5G网络侧支持ATSSS功能。即终端注册到5G网络并发现该网络支持ATSSS功能。
具体地，终端通过检测5G网络侧发送的Registration Accept消息的ats_ind字段，判断该网络是否支持ATSSS功能。
以下是通过Registration Accept消息的ats_ind字段判断网络是否支持ATSSS功能的程序，但本实施例也可以通过其他方式进行判断，本实施例对此不作限定。
Figure PCTCN2022085426-appb-000003
本步骤可以应用于在终端还未注册到网络侧的情况，在注册后就查询网络是否支持ATSSS功能。
在一些实施例中，参照图3所示，步骤102可以通过如下方式实现：
步骤1021，判断MAPDU会话中所有的会话通道是否建立成功，若建立成功，执行步骤1022，若建立失败，则执行步骤1023。
具体地，监听是否收到网络侧基于所有通道的PDU Session Establishment Accept消息，若监听到，则表示MAPDU会话建立成功，执行步骤1022，否则执行步骤1023。
步骤1022，判断MA PDU会话中是否存在需要释放会话资源的会话通道和无需释放
会话资源的会话通道，若存在，执行步骤103，否则，结束流程。
在一个例子中，监听是否接收到会话资源释放消息，当收到会话资源释放消息，则表明MAPDU会话虽然建立成功，但是随着网络传输流量的变化，出现网络侧资源不足的情况，发生网络拥塞，导致MAPDU至少一个通道被要求释放资源，拒绝建立会话。例如，若终端监听到网络侧给终端发送了PDU Session Modification Reject或PDU Session Release消息，且携带理由：insufficient resource，则判定MAPDU会话中存在发生网络拥塞的通道。当存在需要释放会话资源的通道且存在不需要释放会话资源的通道，则表明MAPDU会话中存在发生网络拥塞的通道和会话建立成功的通道。
步骤1023，判断建立的MAPDU会话中，是否存在建立成功的会话通道，若存在，执行步骤103，否则结束流程。
本实施例在MAPDU会话建立成功后，仍持续关注MAPDU会话中的通道是否会因网络拥塞而被要求释放，当网络拥塞，仍能够基于ATSSS表确定终端使用的通道，从而避免网络拥塞情况加重。
在一些实施例中，参照图4所示，在MAPDU会话中所有通道发生网络拥塞时，可以基于新的网络切片重新建立MAPDU会话，步骤如下：
步骤105，若MA PDU会话中所有通道发生网络拥塞，则根据终端路由选择策略URSP规则表确定用于标识网络切片的S-NSSAI。
用户路由选择策略(User Routing Selection Policy，URSP)规则表中有路由选择描述符(route selection descriptor，rsd)，rsd中的路由选择组件有网络切片选择参数，MAPDU会话通过rsd中的网络切片选择参数确定用于标识网络切片的S-NSSAI(Single Network Slice Selection Assistance Information，单个网络切片选择辅助信息)。
以下对S-NSSAI进行简要介绍。
S-NSSAI标识一个网络切片，S-NSSAI的结构如图5所示，由两部分组成：
1)SST(Slice/Service type)，切片/服务类型，它指的是在功能和服务方面的预期网络切片行为。SST可以是一个标准值，例如增强移动宽带(Enhanced Mobile Broadband，eMBB)、超可靠度和低延迟通讯(The Ultra Reliable Low Latency Communications，uRLLC)、大规模物联网(MassibeLot，MIoT)，也可以是一个非标准值。
2)SD(Slice Differentiator)，切片差分器，这是可选信息，补充切片/服务类型，以区分相同切片/服务类型的多个网络切片。
SST长度为1字节，值0～127为标准SST的取值范围，当前协议只是用了三个值，值128～255属于运营商自定义范围，对于运营商自定义的值只在本网下有效，对于标准值全网通用。
步骤105执行完成后执行步骤106。
步骤106，发起新的MA PDU会话的建立请求，新的MAPDU会话的建立请求中携带S-NSSAI。终端在创建新的MA PDU会话时将携带S-NSSAI，表明其希望申请的网络切片。
本实施例在MA PDU会话中所有通道发生网络拥塞，即网络切片发生网络拥塞，则基于URSP表获取新的网络切片，基于新的网络切片创建新的MA PDU会话，避免MA PDU会话向发生网络拥塞的网络持续发起会话建立请求，导致网络拥塞更加严重。值得一提的是，也可以在MAPDU会话中存在发生网络拥塞的通道时，即确定新的S-NSSAI网络切片。
在一些实施例中，参照图6所示，步骤105包括：
步骤1051：是否监听到网络侧下发的URSP规则表，若是，执行步骤1052，否则执行步骤1053。
步骤1052：若监听到网络侧下发的URSP规则表，则根据网络侧下发的URSP规则表确定S-NSSAI。
具体地，将监听到的网络侧下发的URSP规则表进行解析并保存。
步骤1053：若没有监听到网络侧下发的URSP规则表，则根据本地保存的 URSP规则表确定S-NSSAI。
值得一提的是，当本地存有URSP规则表时，移动终端也可以不监听URSP规则表，直接根据本地保存的URSP规则表确定S-NSSAI。
本实施例中URSP规则可由网络侧提供或可预先配置在UE内，以导引UE通过使用不同接入网络在PDU会话上建立数据路由路径。
在一些实施例中，步骤1052中根据网络侧下发的URSP规则表确定S-NSSAI，可以通过以下步骤实现：将MA PDU会话的流量描述符与网络侧下发的URSP规则表中的流量描述符匹配，得到匹配表项；根据匹配表项中的路由选择描述符确定所述S-NSSAI。
具体地，解析网络侧下发URSP规则表并将其保存，将MAPDU会话的Traffic Descriptor流量描述符与网络侧下发的规则表进行匹配，从而得到指定网络切片的S-NSSAI。
本实施例中的流量描述符字段可以为包括：DNN(Data Network Name，数据网络名称)、应用APP ID、FQDN(Fully Qualified Domain Name,全限定域名)，但不限于此。
例如，流量描述符为APPID，MAPDU中的APPID为APP1，终端按照URSP规则表中的优先级从高到低的顺序，将APP1与优先级最高的表项的流量描述符进行匹配，若优先级最高的表项的流量描述符为APP2，与APP1不相同，则将APP1与优先级第二高的表项的流量描述符进行匹配，若优先级第二高的表项的流量描述符为APP3，与MAPDU中的流量描述符APP1不相同，则将其与优先级第三高的表项的流量描述符进行匹配，以此类推，直到找到匹配表项，在匹配表项中的路由选择描述符rsd中得到指定网络切片的S-NSSAI。
本实施例中网络侧的URSP规则表会基于网络切片的质量进行更新，基于网络侧更新的URSP进行匹配，有利于找到网络质量佳，尚未发生网络拥塞的网络切片。
在一些实施例中，步骤1053中根据本地保存的URSP规则表确定S-NSSAI，可以通过以下步骤实现：监听网络侧下发的ATSSS规则表；根据ATSSS规则 表中规则优先级从高到低的顺序，将ATSSS规则表中的流量描述符字段与本地保存的URSP规则表中的流量描述符字段进行匹配，得到URSP规则表中的匹配表项；根据匹配表项中的路由选择描述符确定所述S-NSSAI。URSP规则表中的一个表项即为一条URSP规则。
具体地，终端按照ATSSS规则表中的优先级从高到低的顺序，根据ATSSS规则中的Traffic Descriptor流量描述符字段，在本地存储的URSP规则列表中进行匹配，从而得到指定网络切片的S-NSSAI。
例如：若流量描述符为APPID，网络侧下发的ATSSS规则表中优先级最高的表项里的APPID为APP1，将APP1与URSP规则表中各表项的流量描述符进行匹配，若没有匹配成功，选择ATSSS规则表中优先级第二高的表项进行匹配，若ATSSS规则表中优先级第二高的表项APPID为APP2，URSP规则表中优先级第N高的表项也为APP2，则优先级第N高的表项即为匹配表项，根据匹配表项中的路由选择符rsd得到S-NSSAI。
若终端设备匹配有一个URSP规则，终端设备会根据该URSP规则中的网络切片建立MA PDU会话，当该URSP规则中的网络切片处于拥塞状态，且该URSP规则在本地的URSP规则表中又有较高的优先级，终端会持续基于处于拥塞状态的网络切片发送会话建立请求，导致发生拥塞的网络更加拥塞，为了避免这一情况，在本实施例中，终端会将该URSP规则标为不可用，并且接收网络侧发送的ATSSS规则表，根据ATSSS规则表中的优先级与URSP规则表进行匹配，因ATSSS规则表中的优先级是网络侧实时更新的，反应了网络情况，以此进行匹配，有利于确定未发生网络拥塞的网络切片。
在一些实施例中，当请求建立的MAPDU会话中所有通道发生拥塞，则监听网络侧下发ATSSS规则表，若监听到的ATSSS规则表中携带有网络切片的标识，例如：S-NSSAI，则根据携带的网络切片标识重新建立MAPDU会话，重新建立的MAPDU会话的请求中携带该网络切片的标识。
值得一提的是，当监听到的ATSSS规则表中携带有网络切片的标识，可以基于该ATSSS表确定网络切片，当监听到的ATSSS规则表中没有携带网络切片的标识，可以根据URSP规则表确定S-NSSAI。
本申请提供另一种网络拥塞的处理方法，如图7所示，包括：
步骤101，发起MA PDU会话的建立请求。
步骤102，判断建立的MA PDU会话的多个通道中，是否存在发生网络拥塞的通道和会话建立成功的通道。若是，执行步骤103，否则，执行步骤1054。
步骤103，监听网络侧下发的ATSSS规则表。
步骤104，若监听到ATSSS规则表，根据ATSSS规则表中的活跃-待定模式确定终端使用的通道。
步骤1054，若MA PDU会话中所有通道发生网络拥塞，则监听网络侧下发的ATSSS规则表。
步骤1055，根据网络侧下发的ATSSS规则表和本地保存的URSP规则表确定S-NSSAI。
具体地，将MA PDU会话的流量描述符与网络侧下发的URSP规则表中的流量描述符匹配，得到匹配表项；根据匹配表项中的路由选择描述符确定所述S-NSSAI。
步骤106，发起新的MA PDU会话的建立请求，新的MA PDU会话的建立请求中携带所述S-NSSAI。
本实施例在建立MAPDU会话时，在MAPDU会话中有通道发生网络拥塞的情况下，若存在建立成功的会话通道，则基于ATSSS规则表确定指定的通道，终端使用指定的通道，而不使用网络拥塞的通道，避免终端通过发生网络拥塞的通道持续发送会话建立请求，导致网络拥塞加重；在所有通道发生网络拥塞的情况下，基于新的网络切片创建MAPDU会话，避免向发生网络拥塞的网络继续发送会话建立请求，导致发生网络拥塞的网络更加拥塞，而且，本实施例在存在建立成功的会话通道时，通过ATSSS规则表指定终端使用该通道，而不是重新基于新的网络切片建立MAPDU会话，更能节约终端资源，另外，本申请基于ATSSS规则表和本地保存的URSP规则表确定新的网络切片，使用ATSSS规则表的规则优先级，可以避免本地保存的URSP规则表的规则优先级等信息更没有更新导致未准确找到使用的网络切片的问题。
本申请提供另一种网络拥塞的处理方法，如图8所示，包括：
步骤101，发起MA PDU会话的建立请求。
步骤1021，判断MA PDU会话中所有的会话通道是否建立成功，若建立成功，执行步骤1022，若建立失败，则执行步骤1023。
具体地，监听是否收到网络侧基于所有通道的PDU Session Establishment Accept消息，若监听到，则表示MA PDU会话建立成功，执行步骤1022，否则执行步骤1023。
步骤1022，判断MA PDU会话中是否存在需要释放会话资源的会话通道和无需释放
会话资源的会话通道，若存在，执行步骤103，否则，执行步骤1056。
步骤1023，判断建立的MA PDU会话中，是否存在建立成功的会话通道，若存在，执行步骤103，否则执行步骤1056。
步骤103，监听网络侧下发的ATSSS规则表。
步骤104，若监听到ATSSS规则表，根据ATSSS规则表中的活跃-待定模式确定终端使用的通道。
步骤1056，若MA PDU会话中所有通道发生网络拥塞，则根据网络侧下发的URSP规则表确定S-NSSAI。
步骤106，发起新的MA PDU会话的建立请求，新的MA PDU会话的建立请求中携带所述S-NSSAI。
本实施例在MAPDU会话建立过程中和建立成功后，若MAPDU会话中存在发生网络拥塞的通道均会指定可用的通道或重新基于新的网络切片建立MAPDU会话，以避免网络拥塞情况加重，另外，本实施例直接基于网络侧下发的URSP规则表确定适用的网络切片，URSP规则表由网络侧下发，反应了网络情况，有利于找到适用的网络切片。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本申请的实施例还提供一种网络拥塞的处理装置，如图9所示，包括：建 立模块901，用于发起多接入分组数据单元MA PDU会话的建立请求；管理模块902，用于当请求建立的所述MA PDU会话的多个通道中，存在发生网络拥塞的通道和会话建立成功的通道时，监听网络侧下发的ATSSS规则表；根据所述ATSSS规则表中的活跃-待定模式确定所述终端使用的通道。
在一个例子中，管理模块902进一步用于在所述MA PDU会话中所有通道发生网络拥塞时，根据终端路由选择策略URSP规则表确定用于标识网络切片的S-NSSAI；建立模块901进一步用于发起新的MA PDU会话的建立请求，其中，所述新的MA PDU会话建立请求中携带所述S-NSSAI。
在一个例子中，管理模块902进一步用于当监听到网络侧下发的URSP规则表，根据网络侧下发的URSP规则表确定S-NSSAI；当没有监听到网络侧下发的URSP规则表，则根据本地保存的URSP规则表确定S-NSSAI。
在一个例子中，管理模块902进一步用于监听网络侧下发的ATSSS规则表；根据ATSSS规则表中优先级从高到低的顺序，将ATSSS规则表中的流量描述符字段与所述本地保存的URSP规则表中的流量描述符字段进行匹配，得到所述URSP规则表中的匹配表项；根据所述匹配表项中的路由选择描述符确定所述S-NSSAI。
在一个例子中，管理模块902进一步用于将所述MA PDU会话的流量描述符与所述网络侧下发的URSP规则表中的流量描述符匹配，得到匹配表项；根据所述匹配表项中的路由选择描述符确定所述S-NSSAI。
在一个例子中，管理模块902进一步用于当监听到网络侧发送的PDU Session Establishment Reject会话建立拒绝消息，所述会话建立拒绝消息携带理由为资源不足；则判定所述MA PDU会话中存在发生网络拥塞的通道。
在一个例子中，管理模块902进一步用于当监听到PDU Session Modification Reject会话修改拒绝消息或PDU Session Release会话释放消息，且携带理由为资源不足；则判定所述MA PDU会话中存在发生网络拥塞的通道。
不难发现，本实施例为与上述实施例相对应的装置实施例，本实施方式可与上述实施方式互相配合实施。上述实施方式中提到的相关技术细节在本实施方式中依然有效，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在上述实施方式中。
值得一提的是，本实施方式中所涉及到的各模块均为逻辑模块，在实际应用中，一个逻辑单元可以是一个物理单元，也可以是一个物理单元的一部分，还可以以多个物理单元的组合实现。此外，为了突出本申请的创新部分，本实施方式中并没有将与解决本申请所提出的技术问题关系不太密切的单元引入，但这并不表明本实施方式中不存在其它的单元。
本申请的实施例还提供了一种终端，如图10所示，包括至少一个处理器1001；以及，与所述至少一个处理器通信连接的存储器1002；其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行上述的网络拥塞的处理方法。
其中，存储器和处理器采用总线方式连接，总线可以包括任意数量的互联的总线和桥，总线将一个或多个处理器和存储器的各种电路连接在一起。总线还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和收发机之间提供接口。收发机可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器处理的数据通过天线在无线介质上进行传输，进一步，天线还接收数据并将数据传送给处理器。
处理器负责管理总线和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器可以被用于存储处理器在执行操作时所使用的数据。
本申请的实施例还提供了一种计算机可读存储介质，存储有计算机程序。计算机程序被处理器执行时实现上述方法实施例。
即，本领域技术人员可以理解，实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域的普通技术人员可以理解，上述各实施方式是实现本申请的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本申请的精神和范围。

Claims (10)

  1. 一种网络拥塞的处理方法，应用于终端，包括：
    发起多接入分组数据单元MAPDU会话的建立请求；
    若请求建立的所述MAPDU会话的多个通道中，存在发生网络拥塞的通道和会话建立成功的通道，则监听网络侧下发的ATSSS规则表；根据所述ATSSS规则表中的活跃-待定模式确定所述终端使用的通道。
  2. 根据权利要求1所述的网络拥塞的处理方法，其中，在所述发起多接入分组数据单元MAPDU会话的建立请求后，还包括：
    若所述MAPDU会话中所有通道发生网络拥塞，则根据终端路由选择策略URSP规则表确定用于标识网络切片的S-NSSAI；
    发起新的MAPDU会话的建立请求，其中，所述新的MAPDU会话建立请求中携带所述S-NSSAI。
  3. 根据权利要求2所述的网络拥塞的处理方法，其中，所述根据终端路由选择策略URSP规则表确定用于标识网络切片的S-NSSAI，包括：
    若监听到网络侧下发的URSP规则表，则根据网络侧下发的URSP规则表确定S-NSSAI；或者，
    若没有监听到网络侧下发的URSP规则表，则根据本地保存的URSP规则表确定S-NSSAI。
  4. 根据权利要求3所述的网络拥塞的处理方法，其中，所述根据本地保存的URSP规则表确定用于标识网络切片的S-NSSAI，包括：
    监听网络侧下发的ATSSS规则表；
    根据所述ATSSS规则表中优先级从高到低的顺序，将所述ATSSS规则表中的流量描述符字段与所述本地保存的URSP规则表中的流量描述符字段进行匹配，得到所述URSP规则表中的匹配表项；
    根据所述匹配表项中的路由选择描述符确定所述S-NSSAI。
  5. 根据权利要求3或4所述的网络拥塞的处理方法，其中，所述根据网络侧下发的URSP规则表确定S-NSSAI，包括：
    将所述MAPDU会话的流量描述符与所述网络侧下发的URSP规则表中的流量描述符匹配，得到匹配表项；
    根据所述匹配表项中的路由选择描述符确定所述S-NSSAI。
  6. 根据权利要求1至5任一项所述的网络拥塞的处理方法，其中，所述发起多接入分组数据单元MA PDU会话的建立请求之后，还包括：
    若监听到网络侧发送的PDU Session Establishment Reject会话建立拒绝消息，所述会话建立拒绝消息携带理由为资源不足；
    则判定所述MAPDU会话中存在发生网络拥塞的通道。
  7. 根据权利要求1至6任一项所述的网络拥塞的处理方法，其中，所述方法还包括：所述MAPDU会话建立成功之后，
    若监听到PDU Session Modification Reject会话修改拒绝消息或PDU Session Release会话释放消息，且携带理由为资源不足；
    则判定所述MAPDU会话中存在发生网络拥塞的通道。
  8. 一种网络拥塞的处理装置，包括：
    建立模块，用于发起多接入分组数据单元MA PDU会话的建立请求；
    管理模块，用于当请求建立的所述MA PDU会话的多个通道中，存在发生网络拥塞的通道和会话建立成功的通道时，监听网络侧下发的ATSSS规则表；根据所述ATSSS规则表中的活跃-待定模式确定所述终端使用的通道。
  9. 一种终端，包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求1至7中 任一所述的网络拥塞的处理方法。
  10. 一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1至7中任一项所述的网络拥塞的处理方法。
PCT/CN2022/085426 2021-04-19 2022-04-06 一种网络拥塞的处理方法、装置、终端、存储介质 WO2022222753A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110418353.3 2021-04-19
CN202110418353.3A CN115297058A (zh) 2021-04-19 2021-04-19 一种网络拥塞的处理方法、装置、终端、存储介质

Publications (1)

Publication Number Publication Date
WO2022222753A1 true WO2022222753A1 (zh) 2022-10-27

Family

ID=83723651

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/085426 WO2022222753A1 (zh) 2021-04-19 2022-04-06 一种网络拥塞的处理方法、装置、终端、存储介质

Country Status (2)

Country Link
CN (1) CN115297058A (zh)
WO (1) WO2022222753A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117033005B (zh) * 2023-10-07 2024-01-26 之江实验室 一种无死锁路由方法、装置、存储介质及电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190306752A1 (en) * 2018-04-01 2019-10-03 Industrial Technology Research Institute Method of distributing uplink data flow between different access networks in 5g communication system and user equipment using the same
US20200260401A1 (en) * 2019-02-12 2020-08-13 Zte Corporation Session management policy support for session establishment
WO2020168236A1 (en) * 2019-02-15 2020-08-20 Idac Holdings, Inc. Multi-access pdu session

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190306752A1 (en) * 2018-04-01 2019-10-03 Industrial Technology Research Institute Method of distributing uplink data flow between different access networks in 5g communication system and user equipment using the same
US20200260401A1 (en) * 2019-02-12 2020-08-13 Zte Corporation Session management policy support for session establishment
WO2020168236A1 (en) * 2019-02-15 2020-08-20 Idac Holdings, Inc. Multi-access pdu session

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
APPLE, ERICSSON, MOTOROLA MOBILITY, LENOVO BROADCOM: "ATSSS Steering of non-MPTCP Traffic", 3GPP SA WG2 MEETING #135; S2-1910235-, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 17 October 2019 (2019-10-17), Split, Croatia; 20191014 - 20191018, XP051797010 *

Also Published As

Publication number Publication date
CN115297058A (zh) 2022-11-04

Similar Documents

Publication Publication Date Title
US10659952B2 (en) Network slice selection policy updating method and apparatus
US20200245383A1 (en) Data Transmission Channel Processing Method, Apparatus, and System
US11765584B2 (en) Message processing method and system, and user plane function device
US20210168151A1 (en) Method for implementing user plane security policy, apparatus, and system
WO2019033796A1 (zh) 会话处理方法及相关设备
US20230072956A1 (en) Slice access method, apparatus, and system
US20240089299A1 (en) Method for Providing Restricted Service, and Communications Device
US20220417101A1 (en) Communication method, apparatus, and system
EP3731545B1 (en) Communication method and devices
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
WO2018233451A1 (zh) 通信方法、装置和系统
US20220116818A1 (en) Handling of 5GSM Congestion Timers
WO2022222753A1 (zh) 一种网络拥塞的处理方法、装置、终端、存储介质
US20240015593A1 (en) Traffic flow processing method, apparatus, and system
WO2024021858A1 (zh) 通信方法、电子设备及存储介质
US10051508B2 (en) System and method for mobility support selection
CN112104464B (zh) 一种传输背景流量传输信息的方法、装置及系统
WO2022252874A1 (zh) 信令风暴抑制方法、移动终端、电子设备及存储介质
WO2022222611A1 (zh) 数据传输方法、装置、终端、存储介质
WO2023035925A1 (zh) 一种业务处理方法、装置和系统
US20230319622A1 (en) Method, device, and system for limiting data rate of network slice user, and storage medium
EP3869755A1 (en) Control plane network function, user plane network function, and packet processing method using same
WO2024093448A1 (en) Smart policy rule update
WO2021238744A1 (zh) 数据传输方法及装置
US20240056883A1 (en) Access handling when stopping 5gsm congestion timers

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: 22790862

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE