CN115297058A

CN115297058A - Method, device, terminal and storage medium for processing network congestion

Info

Publication number: CN115297058A
Application number: CN202110418353.3A
Authority: CN
Inventors: 杨海城; 周金星
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2021-04-19
Filing date: 2021-04-19
Publication date: 2022-11-04
Also published as: WO2022222753A1

Abstract

The embodiment of the invention relates to the field of communication and discloses a method for processing network congestion. In the invention, a request for establishing an MA PDU session is initiated, if a channel with network congestion and a channel with successful session establishment exist in a plurality of channels of the MA PDU session requested to be established, a Steering, switching and shunting (Access Traffic Steering, switching, splitting and ATSSS) rule table of Access flow sent by a network side is monitored, and a channel used by a terminal is determined according to an active undetermined mode in the ATSSS rule table. The terminal is prevented from continuously sending the session establishment request through the current unspecified channel, namely the channel with network congestion is prevented from successfully establishing the session, so that the network congestion is prevented from being aggravated.

Description

Network congestion processing method, device, terminal and storage medium

Technical Field

The embodiment of the application relates to the field of communication, in particular to a method, a device, a terminal and a storage medium for processing network congestion.

Background

When there is too much traffic in the network, which causes data packets to be delayed or lost, thereby degrading the network performance, this condition is called network congestion, which is a network state with continuous overload, and can cause the performance of the whole network to be degraded, or even cause the network traffic to be dropped in a severe case.

When network congestion occurs in a certain channel in an established Multi-Access Protocol Data Unit (MA PDU) session, a terminal may still initiate a session establishment request through the channel in which the network congestion occurs, resulting in an increased network congestion situation.

Disclosure of Invention

The embodiment of the present application mainly aims to provide a method for processing network congestion, which can avoid the situation of network congestion from getting worse.

In order to achieve the above object, the present application provides a method for processing network congestion, including: initiating a request for establishing an MAPDU session, monitoring a Steering, switching and shunting (Switching, distributing and Switching) rule table of Access Traffic issued by a network side if a channel with network congestion and a channel with successful session establishment exist in a plurality of channels of the MAPDU session requested to be established, and determining a channel used by a terminal according to an active undetermined mode in the ATSSS rule table.

In order to achieve the above object, an embodiment of the present application further provides a device for processing network congestion, including an establishment module, configured to initiate an establishment request of a multiple access packet data unit MA PDU session; the management module is used for monitoring an ATSSS rule table issued by a network side when a channel with network congestion and a channel with successful session establishment exist in a plurality of channels of the MA PDU session requested to be established; and determining the channel used by the terminal according to the active-pending mode in the ATSSS rule table.

In order to achieve the above object, an embodiment of the present application further provides a terminal, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the above-described method of handling network congestion.

In order to achieve the above object, an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the above processing method for network congestion.

The method for processing network congestion provided by the embodiment of the application establishes an MA PDU session, the MA PDU session has a plurality of session channels, if a channel with network congestion and a channel with successful session establishment exist, an Access Traffic Steering, switching, splitting, and SSS (Access Traffic Steering, switching, splitting, and Switching) rule table sent by a network side is obtained, the ATSSS rule table is updated by the network side according to network conditions, an Active-Standby Active-pending Mode of a Steering Mode Switching Mode in the ATSSS rule table indicates a terminal to use a certain specified channel, the terminal preferentially uses an Active channel, when the Active channel is unavailable, the channel to be pending is changed, the channel with successful session establishment is preferentially selected by the network side to be the Active channel, therefore, the channel in the MA PDU session is specified according to the Active-Standby Mode in the ATSSS rule table, the terminal can be ensured to use the currently specified channel, namely, the session successfully established by the terminal is specified to be an Active channel, and the occurrence of network congestion is avoided.

Drawings

One or more embodiments are illustrated by the figures in the accompanying drawings, which correspond to and are not intended to limit the embodiments.

Fig. 1 is a flow chart of a method of handling network congestion in accordance with an embodiment of the present invention;

fig. 2 is a flowchart of a method of handling network congestion including a registration procedure according to another embodiment of the present invention;

fig. 3 is a flowchart of a processing method including determining network congestion for each session channel establishment result flow according to another embodiment of the present invention;

fig. 4 is a flowchart of a method for handling network congestion including a new MAPDU session procedure according to another embodiment of the present invention;

FIG. 5 is a diagram illustrating a structure of S-NSSAI data in the related art;

FIG. 6 is a flow chart for determining S-NSSAI according to another embodiment of the present invention;

fig. 7 is a flow diagram of a method of processing network congestion including the process of determining network slices from a locally maintained URSP rules table in accordance with another embodiment of the present invention;

fig. 8 is a flow chart of a method of processing network congestion including the flow of determining network slices from a network side URSP in accordance with another embodiment of the present invention;

fig. 9 is a schematic diagram of a processing device for network congestion according to another embodiment of the present invention;

fig. 10 is a schematic configuration diagram of a terminal according to another embodiment of the present invention.

Detailed Description

To make the objects, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that in the examples of the present application, numerous technical details are set forth in order to provide a better understanding of the present application. However, the technical solution claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments. The following embodiments are divided for convenience of description, and should not constitute any limitation to the specific implementation manner of the present application, and the embodiments may be mutually incorporated and referred to without contradiction.

The embodiment of the invention provides a method for processing network congestion, which is applied to a terminal, and comprises the following steps: a mobile phone, a tablet, and the like, in addition, the network side of this embodiment needs to support the ATSSS function. The Access Traffic Steering, switching, and Splitting function is introduced by the 3gpp r16 version, and is mainly used for path optimization, seamless Switching, multipath concurrence, and the like of a terminal MA (Multi-Access) service, thereby improving user experience.

In this embodiment, a terminal initiates a request for establishing a Multi-Access Protocol Data Unit (MA PDU) session; if a channel with network congestion and a channel with successful session establishment exist in the multiple channels of the MA PDU session requested to be established, monitoring an ATSSS rule table issued by a network side; and determining the channel used by the terminal according to the active-pending mode in the ATSSS rule table. The terminal determines the used channel according to the specified channel in the Active-Standby Active-pending mode in the ATSSS rule table, so that the mobile terminal is ensured not to establish a session through the channel with network congestion, and the condition that the network congestion is aggravated is avoided.

The implementation details of the network congestion processing method of the present embodiment will be specifically described below with reference to fig. 1, and the following description is only provided for facilitating understanding of the implementation details and is not necessary for implementing the present solution.

Step 101, initiate a request for establishment of a MA PDU session. Namely, the application of the MAPDU session is initiated to the network side.

In a 5G network, a Data Protocol Data Unit (PDU) session, referred to as an MAPDU session, may transmit Data via multiple access technologies. MAPDU sessions may use both third Generation Partnership project (3rd Generation Partnership project, 3gpp) access technologies, such as: long Term Evolution (LTE), new radio, NR, and non-3 GPP access technologies, such as Wireless Local Area Network (WLAN).

An MAPDU session includes multiple channels, for example: the MAPDU session includes a 5G channel using NR access technology and a WiFi channel using WLAN access technology, for example: the MAPDU session includes a 5G channel using NR technology and a WIFI1 channel and a WIFI2 channel using WLAN access technology, and for example, the MAPDU session includes a 5G1 channel and a 5G2 channel using NR access technology and a WIFI channel using WLAN access technology. The number of channels specifically included in the MA PDU session and the access technology used by each channel may be created according to actual requirements, which does not cause a limitation to this embodiment.

After the execution of step 101 is completed, step 102 is entered.

Step 102, judging whether a channel with network congestion and a channel with successful session establishment exist in a plurality of established channels of the MA PDU session.

In one example, if a session establishment rejection message sent by a network side is monitored, the reason for carrying the session establishment rejection message is that resources are insufficient; it is determined that there is a path in the MA PDU session where network congestion occurs.

And if receiving the session establishment receiving message based on a certain channel, judging that a channel with successful session establishment exists in the MAPDU session.

For example, the terminal monitors whether a PDU Session Establishment Reject message is received from the network side, and carries a reason: and if the message is monitored, judging that a channel with network congestion exists in the MA PDU, and determining the channel with the MAPDU congestion by the terminal based on the channel. If the terminal further receives a session establishment receiving message based on a certain channel, and the successfully established session channel and the network-congested session channel have the same PDU Session ID, it is determined that multiple channels in the MAPDU exist, namely the channel with the network congestion and the channel with the successfully established session. In this embodiment, when a session is established, due to insufficient resources, congestion occurs on the network side, which causes at least one channel in the MA PDU session to be rejected from establishing the session.

And 103, monitoring an ATSSS rule table issued by a network side if a channel with network congestion and a channel with successful session establishment exist.

If the ATSSS rule table issued by the network side is monitored, step 104 is executed.

And step 104, determining a channel used by the terminal according to an active-pending mode in an ATSSS rule table.

Specifically, after monitoring an ATSSS rule table issued by a network side, the terminal analyzes the ATSSS rule table and stores the ATSSS rule table to the local, the terminal designates the channel as an Active channel when an Active channel in the ATSSS rule table is available, and the terminal designates the channel as a standby channel when the Active channel is unavailable.

For ease of understanding, the following shows part of the content of the ATSSS rule table specified in the 3GPP specification.

According to the specification of 3GPP TS 24.193, the network side can indicate the terminal to use a certain specified channel through an Active-Standby Mode in the Steering Mode conversion Mode. The terminal preferentially uses the Active channel, and uses the Standby channel when the channel is unavailable.

The coding specification of the SteeringMode mode is described in Table 6.1.3.2-1.

TABLE 1

The encoding specification of the acid-state by mode in the Steering mode is described in Table 6.1.3.2-1.

TABLE 2

For the sake of understanding, the following description will be made by taking as an example that the established MA PDU session includes a 5G channel using NR access technology and a WIFI channel using WLAN access technology, describing a processing method of network congestion,

the terminal equipment establishes an MAPDU session, and monitors an ATSSS rule table issued by a network side if the session establishment based on the 5G channel is successful if network congestion occurs in a WIFI channel in the MAPDU. And if the ATSSS rule table is monitored, analyzing the rule table and storing the rule table to the local. If the active channel in the analyzed acceptable-standby mode in the ATSSS rule table is designated as the 5G channel, the terminal uses the 5G channel and does not use the WIFI channel, the terminal is prevented from sending a request to a network side through the WIFI channel, and the channel with network congestion is enabled to be more congested.

The ATSSS rule table in this embodiment is issued by the network side, the network may consider the network performance, and preferentially select an available channel in the active-standby mode, where the channel where no network congestion occurs is an active channel.

It should be noted that the method of this embodiment may be applied to a scenario where network congestion is not generated yet, a session may be accessed normally, but data transmission is slow, for example: in a certain area, multiple people are connected with a certain WIFi, although WIFI can be accessed, the terminal cannot use a WIFI channel to carry out normal data transmission, and at the moment, the appointed channel can also be determined through an ATSSS rule table.

In the related technology, when a channel in the MAPDU session is not successfully established due to network congestion, the mobile terminal still applies for establishing a session to the network side through the channel with congestion, so that the network congestion situation of the channel is aggravated.

In some embodiments, as shown in fig. 2, before step 101, step 100 is further included: register to the network and determine that the 5G network side supports the sss function. I.e. the terminal registers with the 5G network and discovers that the network supports the ATSSS functionality.

Specifically, 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 determining whether the network supports the ATSSS function through the ats _ ind field of the Registration Accept message, but this embodiment may also determine through other manners, and this embodiment is not limited to this.

15:03:10.219 0xB80A NR5G NAS MM5G Plain OTA Incoming Msg--Registration accept

nwk_feature_supp_inc＝1(0x1)

nwk_feature_supported

length＝2(0x2)

emf＝1(0x1)(Emergency srv fallback supported in NR connected to 5GCN only)

emc＝0(0x0)(Emergency srv not supported)

……

ats_ind＝1(0x1)。

This step may be applied to a case where the terminal is not registered to the network side, and after registration, it is queried whether the network supports the ATSSS function.

In some embodiments, referring to FIG. 3, step 102 may be implemented as follows:

step 1021, determining whether all session channels in the MAPDU session are successfully established, if so, executing step 1022, and if not, executing step 1023.

Specifically, whether a PDU Session Establishment Accept message based on all channels on the network side is received is monitored, if so, it indicates that the MAPDU Session is successfully established, step 1022 is executed, otherwise, step 1023 is executed.

Step 1022, determining whether there are session channels that need to release session resources and session channels that do not need to release session resources in the MA PDU session, if yes, executing step 103, otherwise, ending the process.

In one example, whether a session resource release message is received is monitored, and when the session resource release message is received, it indicates that although the establishment of an MAPDU session is successful, network side resources are insufficient due to the change of network transmission flow, so that network congestion occurs, which causes at least one channel of the MAPDU to be required to release resources, and the establishment of the session is rejected. For example, if the terminal monitors that the network side sends a PDU Session Modification request or PDU Session Release message to the terminal, and carries a reason: and (4) judging that a channel with network congestion exists in the MAPDU session. When a channel which needs to release the session resources exists and a channel which does not need to release the session resources exists, it indicates that a channel in which network congestion occurs and a channel in which the session is successfully established exist in the MAPDU session.

And 1023, judging whether a successfully established session channel exists in the established MAPDU session, if so, executing 103, otherwise, ending the flow.

In this embodiment, after the MAPDU session is successfully established, it is still continuously concerned whether the channel in the MAPDU session is required to be released due to network congestion, and when the network is congested, the channel used by the terminal can still be determined based on the ATSSS table, thereby avoiding the situation of network congestion from being aggravated.

In some embodiments, referring to fig. 4, when network congestion occurs to all channels in an MAPDU session, the MAPDU session may be re-established based on a new network slice, and the following steps are performed:

and 105, if network congestion occurs to all channels in the MA PDU session, determining the S-NSSAI for identifying the network slice according to the terminal routing strategy URSP rule table.

A User Routing Selection Policy (URSP) rule table has a Routing Selection descriptor (rsd), a Routing component in the rsd has a Network Slice Selection parameter, and an MAPDU session determines, through the Network Slice Selection parameter in the rsd, an S-NSSAI (Single Network Slice Selection Assistance Information) for identifying a Network Slice.

A brief introduction to S-NSSAI is provided below.

The S-NSSAI identifies a network slice, and the structure of the S-NSSAI is shown in FIG. 5 and consists of two parts:

1) SST (Slice/Service type), slice/Service type, which refers to the expected network Slice behavior in terms of functionality and Service. SST can be a standard value, such as Enhanced Mobile Broadband (eMBB), ultra-Reliable and Low Latency Communications (urrllc), mass internet of things (MassibeLot), or a non-standard value.

2) SD (Slice diffirector), a Slice Differentiator, which is optional information, supplements Slice/service types to distinguish multiple network slices of the same Slice/service type.

The SST length is 1 byte, the value of 0-127 is the value range of standard SST, the current protocol only uses three values, the value of 128-255 belongs to the operator self-defined range, the value defined by the operator is only effective in the local network, and the value is universal for the standard value of the whole network.

Step 106 is executed after the execution of step 105 is completed.

And step 106, initiating a new MA PDU session establishment request, wherein the new MA PDU session establishment request carries S-NSSAI. The terminal will carry the S-NSSAI when creating a new MA PDU session, indicating the network slice it wishes to apply for.

In this embodiment, when network congestion occurs in all channels in an MA PDU session, that is, network congestion occurs in a network slice, 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 that it is avoided that the MA PDU session continuously initiates a session establishment request to a network with the network congestion, which causes more serious network congestion. It should be noted that, when there is a channel in the MAPDU session where network congestion occurs, a new S-NSSAI network slice may be determined.

In some embodiments, referring to FIG. 6, step 105 comprises:

step 1051: if the URSP rule table issued by the network side is monitored, if yes, execute step 1052, otherwise execute step 1053.

Step 1052: and if the URSP rule table issued by the network side is monitored, determining the S-NSSAI according to the URSP rule table issued by the network side.

Specifically, the monitored URSP rule table issued by the network side is analyzed and stored.

Step 1053: and if the URSP rule table issued by the network side is not monitored, determining the S-NSSAI according to the locally stored URSP rule table.

It should be noted that, when the URSP rule table is locally stored, the mobile terminal may also determine the S-NSSAI directly according to the locally stored URSP rule table without monitoring the URSP rule table.

The URSP rules in this embodiment 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 over the PDU session by using different access networks.

In some embodiments, the step 1052 of determining the S-NSSAI according to the URSP rule table issued by the network side may be implemented by the following steps: matching the flow descriptor of the MA PDU session with the flow descriptor in a URSP rule table issued by a network side to obtain a matched table item; and determining the S-NSSAI according to the routing descriptor in the matched table entry.

Specifically, a URSP rule table issued by the network side is analyzed and stored, and Traffic Descriptor of the MAPDU session is matched with the rule table issued by the network side, so that S-NSSAI of the designated network slice is obtained.

The traffic descriptor field in this embodiment may include: DNN (Data Network Name), APP ID, FQDN (full Qualified Domain Name), but is not limited thereto.

For example, the traffic descriptor is APPID, APPID in MAPDU is APP1, the terminal matches APP1 with the traffic descriptor of the entry with the highest priority according to the order from high to low in the priority in the URSP rule table, if the traffic descriptor of the entry with the highest priority is APP2 and is different from APP1, then matches APP1 with the traffic descriptor of the entry with the second highest priority, if the traffic descriptor of the entry with the second highest priority is APP3 and is different from the traffic descriptor APP1 in MAPDU, then matches it with the traffic descriptor of the entry with the third highest priority, and so on until a matching entry is found, and obtains S-NSSAI of the specified network slice in the routing descriptor rsd in the matching entry.

In this embodiment, the URSP rule table on the network side is updated based on the quality of the network slice, and the URSP updated on the network side is matched, which is beneficial to finding a network slice with good network quality and without network congestion.

In some embodiments, determining S-NSSAI according to the locally stored URSP rule table in step 1053 may be implemented by: monitoring an ATSSS rule table issued by a network side; matching the flow descriptor field in the ATSSS rule table with the flow descriptor field in the URSP rule table stored locally according to the sequence of rule priority from high to low in the ATSSS rule table to obtain a matching table entry in the URSP rule table; and determining the S-NSSAI according to the routing descriptor in the matched table entry. One entry in the URSP rule table is a URSP rule.

Specifically, the terminal performs matching in a locally stored URSP rule list according to the sequence from high priority to low priority in the ATSSS rule table and according to the Traffic Descriptor field in the ATSSS rule, so as to obtain the S-NSSAI of the specified network slice.

For example: if the flow descriptor is APPID, the APPID in the table entry with the highest priority in the ATSSS rule table issued by the network side is APP1, the APP1 is matched with the flow descriptor of each table entry in the URSP rule table, if the matching is not successful, the table entry with the second highest priority in the ATSSS rule table is selected for matching, if the APPID in the table entry with the second highest priority in the ATSSS rule table is APP2, and the table entry with the Nth highest priority in the URSP rule table is also APP2, the table entry with the Nth highest priority is the matching table entry, and S-NSSAI is obtained according to the routing selector rsd in the matching table entry.

If the terminal device matches a URSP rule, the terminal device will establish an MA PDU session according to a network slice in the URSP rule, and when the network slice in the URSP rule is in a congestion state and the URSP rule has a higher priority in a local URSP rule table, the terminal will continuously send a session establishment request based on the network slice in the congestion state, so that the congested network is more congested.

In some embodiments, when all channels in an MAPDU session requested to be established are congested, a monitoring network side issues an ATSSS rule table, and if the monitored ATSSS rule table carries an identifier of a network slice, for example: and S-NSSAI reestablishes the MAPDU session according to the carried network slice identifier, wherein the request of the reestablished MAPDU session carries the identifier of the network slice.

It should be noted that when the monitored ATSSS rule table carries the identifier of the network slice, the network slice may be determined based on the ATSSS table, and when the monitored ATSSS rule table does not carry the identifier of the network slice, the S-NSSAI may be determined according to the URSP rule table.

The present application provides another method for processing network congestion, as shown in fig. 7, including:

step 101, initiate a request for establishment of a MA PDU session.

Step 102, judging whether a channel with network congestion and a channel with successful session establishment exist in a plurality of established channels of the MA PDU session. If so, go to step 103, otherwise, go to step 1054.

And 103, monitoring an ATSSS rule table issued by the network side.

And step 104, if the ATSSS rule table is monitored, determining a channel used by the terminal according to an active-pending mode in the ATSSS rule table.

Step 1054, if network congestion occurs in all channels in the MA PDU session, then the ATSSS rule table issued by the network side is monitored.

And 1055, determining S-NSSAI according to the ATSSS rule table issued by the network side and the URSP rule table stored locally.

Specifically, matching a traffic descriptor of an MA PDU session with a traffic descriptor in a URSP rule table issued by a network side to obtain a matching table entry; and determining the S-NSSAI according to the routing descriptor in the matched table entry.

Step 106, initiating a new MA PDU session establishment request, wherein the new MA PDU session establishment request carries the S-NSSAI.

In the embodiment, when an MAPDU session is established, if a successfully established session channel exists in the MAPDU session under the condition that network congestion occurs in the channel, the specified channel is determined based on an ATSSS rule table, and the terminal uses the specified channel instead of the channel with network congestion, so that the situation that the network congestion is increased because the terminal continuously sends a session establishment request through the channel with network congestion is avoided; in addition, the application determines a new network slice based on the ATSSS rule table and uses the rule priority of the ATSSS rule table, so that the problem that the used network slice is not accurately found due to the fact that information such as the rule priority of the locally-stored URSP rule table is not updated more can be avoided.

The present application provides another method for processing network congestion, as shown in fig. 8, including:

step 101, initiate a request for establishment of a MA PDU session.

Step 1021, determining whether all session channels in the MA PDU session are successfully established, if so, executing step 1022, and if not, executing step 1023.

Specifically, whether a PDU Session Establishment Accept message based on all channels on the network side is received is monitored, if so, the MA PDU Session Establishment is successful, step 1022 is executed, otherwise, step 1023 is executed.

Step 1022, determining whether there are session channels that need to release session resources and session channels that do not need to release session resources in the MA PDU session, if yes, executing step 103, otherwise, executing step 1056.

Step 1023, determine if there is a successfully established session channel in the established MA PDU session, if there is, execute step 103, otherwise execute step 1056.

And 103, monitoring an ATSSS rule table issued by the network side.

Step 1056, if network congestion occurs in all channels in the MA PDU session, then S-NSSAI is determined according to the URSP rule table issued by the network side.

In the embodiment, in the MAPDU session establishment process and after successful establishment, if a channel with network congestion exists in the MAPDU session, an available channel is designated or an MAPDU session is established based on a new network slice again, so as to avoid aggravation of the network congestion condition.

The steps of the above methods are divided for clarity, and the implementation may be combined into one step or split some steps, and the steps are divided into multiple steps, so long as the same logical relationship is included, which are all within the protection scope of the present patent; it is within the scope of the patent to add insignificant modifications to the algorithms or processes or to introduce insignificant design changes to the core design without changing the algorithms or processes.

An embodiment of the present invention further provides a device for processing network congestion, as shown in fig. 9, including: an establishing module 901, configured to initiate a request for establishing a multi-access packet data unit MA PDU session; a management module 902, configured to monitor an ats ss rule table delivered by a network side when a channel with network congestion and a channel with successful session establishment exist in multiple channels of the MA PDU session requested to be established; and determining the channel used by the terminal according to the active-pending mode in the ATSSS rule table.

In an example, the management module 902 is further configured to determine, according to the terminal routing policy URSP rule table, an S-NSSAI for identifying a network slice when network congestion occurs on all channels in the MA PDU session; the establishing module 901 is further configured to initiate a new MA PDU session establishment request, where the new MA PDU session establishment request carries the S-NSSAI.

In an example, the management module 902 is further configured to determine, when monitoring the URSP rule table delivered by the network side, the S-NSSAI according to the URSP rule table delivered by the network side; and when the URSP rule table transmitted by the network side is not monitored, determining the S-NSSAI according to the locally stored URSP rule table.

In an example, the management module 902 is further configured to monitor an sss rule table issued by the network side; matching the flow descriptor field in the ATSSS rule table with the flow descriptor field in the URSP rule table stored locally according to the sequence of the priorities from high to low in the ATSSS rule table to obtain a matching table entry in the URSP rule table; and determining the S-NSSAI according to the routing descriptor in the matched table entry.

In an example, the management module 902 is further configured to match a traffic descriptor of the MA PDU session with a traffic descriptor in a URSP rule table delivered by the network side, so as to obtain a matching entry; and determining the S-NSSAI according to the routing descriptor in the matched table entry.

In an example, the management module 902 is further configured to, when a PDU Session Establishment Reject message sent by the network side is monitored, where the Session Establishment Reject message carries a reason that resources are insufficient; determining that a path with network congestion exists in the MA PDU session.

In an example, the management module 902 is further configured to, when a PDU Session Modification Reject message or a PDU Session Release message is monitored, carry a reason that resources are insufficient; then it is determined that there is a path in the MA PDU session where network congestion occurs.

It should be understood that this embodiment is an apparatus embodiment corresponding to the above embodiment, and this embodiment can be implemented in cooperation with the above embodiment. The related technical details mentioned in the above embodiments are still valid in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the above-described embodiments.

It should be noted that each module referred to in this embodiment is a logical module, and in practical applications, one logical unit may be one physical unit, may be a part of one physical unit, and may be implemented by a combination of multiple physical units. In addition, in order to highlight the innovative part of the present invention, elements that are not so closely related to solving the technical problems proposed by the present invention are not introduced in the present embodiment, but this does not indicate that other elements are not present in the present embodiment.

An embodiment of the present invention also provides a terminal, as shown in fig. 10, including at least one processor 1001; and a memory 1002 communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the above-described method of handling network congestion.

Where the memory and processor are connected by a bus, the bus may comprise any number of interconnected buses and bridges, the bus connecting together various circuits of the memory and the processor or processors. The bus may also connect various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are well known in the art, and therefore, will not be described any further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor is transmitted over a wireless medium via an antenna, which further receives the data and transmits the data to the processor.

The processor is responsible for managing the bus and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And the memory may be used to store data used by the processor in performing operations.

Embodiments of the present invention also provide a computer-readable storage medium storing a computer program. The computer program realizes the above-described method embodiments when executed by a processor.

That is, as can be understood by those skilled in the art, all or part of the steps in the method for implementing the embodiments described above may be implemented by a program instructing related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples for carrying out the invention, and that various changes in form and details may be made therein without departing from the spirit and scope of the invention in practice.

Claims

1. A method for processing network congestion is applied to a terminal and comprises the following steps:

initiating a request for establishing a multi-access packet data unit (MAPDU) session;

monitoring an ATSSS rule table issued by a network side if a channel with network congestion and a channel with successful session establishment exist in a plurality of channels of the MAPDU session requested to be established; and determining the channel used by the terminal according to the active-pending mode in the ATSSS rule table.

2. The method of claim 1, wherein after the initiating the request for establishing the multiple access packet data unit MAPDU session, the method further comprises:

if network congestion occurs in all channels in the MAPDU session, determining S-NSSAI for identifying a network slice according to a terminal routing strategy URSP rule table;

and initiating a new MAPDU session establishment request, wherein the new MAPDU session establishment request carries the S-NSSAI.

3. The method for processing network congestion according to claim 2, wherein the determining S-NSSAI for identifying a network slice according to a terminal routing policy, URSP, rule table comprises:

if the URSP rule table issued by the network side is monitored, determining S-NSSAI according to the URSP rule table issued by the network side; or,

and if the URSP rule table issued by the network side is not monitored, determining the S-NSSAI according to the locally stored URSP rule table.

4. The method of claim 3, wherein determining the S-NSSAI for identifying the network slice according to the locally maintained URSP rule table comprises:

monitoring an ATSSS rule table issued by a network side;

matching the flow descriptor field in the ATSSS rule table with the flow descriptor field in the URSP rule table stored locally according to the sequence of the priorities from high to low in the ATSSS rule table to obtain a matching table entry in the URSP rule table;

and determining the S-NSSAI according to the routing descriptor in the matched table entry.

5. The method of claim 3, wherein the determining the S-NSSAI according to the URSP rule table issued by the network side comprises:

matching the flow descriptor of the MAPDU session with a flow descriptor in a URSP rule table issued by the network side to obtain a matching table entry;

6. The method according to any of claims 1 to 5, wherein after the initiating the request for establishment of a multiple access packet data unit, MA, PDU session, further comprises:

if a PDU Session Establishment Reject message sent by a network side is monitored, the reason for carrying the Session Establishment Reject message is that resources are insufficient;

determining that a channel with network congestion exists in the MAPDU session.

7. The method for handling network congestion according to any of claims 1 to 5, wherein the method further comprises: after the establishment of the MAPDU session is successful,

if the PDU Session Modification Reject message or PDU Session Release Session Release message is monitored, and the reason for carrying is insufficient resources;

determining that a channel with network congestion exists in the MAPDU session.

8. An apparatus for handling network congestion, comprising:

the establishment module is used for initiating an establishment request of a multi-access packet data unit (MA PDU) session;

the management module is used for monitoring an ATSSS rule table issued by a network side when a channel with network congestion and a channel with successful session establishment exist in a plurality of channels of the MA PDU session requested to be established; and determining the channel used by the terminal according to the active-pending mode in the ATSSS rule table.

9. A terminal, comprising:

at least one processor; and (c) a second step of,

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of handling network congestion according to any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the method for handling network congestion of any one of claims 1 to 7.