CN114363954A - Congestion control method and device, terminal and network side equipment - Google Patents
Congestion control method and device, terminal and network side equipment Download PDFInfo
- Publication number
- CN114363954A CN114363954A CN202011063723.8A CN202011063723A CN114363954A CN 114363954 A CN114363954 A CN 114363954A CN 202011063723 A CN202011063723 A CN 202011063723A CN 114363954 A CN114363954 A CN 114363954A
- Authority
- CN
- China
- Prior art keywords
- network
- terminal
- congestion
- congestion control
- disaster
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application discloses a congestion control method, a congestion control device, a terminal and network side equipment, and belongs to the technical field of communication. The congestion control method comprises the following steps: performing congestion control in a case where the second network is in a congested state; the congestion control includes: preferentially rejecting request messages or services of the first terminal; or, preferentially releasing the service or session of the first terminal; or, preferentially registering the first terminal; the second network is a network which provides services for the first terminal under the condition that the first network is in a disaster state, and the first terminal is a terminal which is signed to the first network. By executing congestion control, the service of the terminal subscribed to the second network can be guaranteed preferentially, and the communication performance of the subscribed terminal of the second network in the congestion state is improved.
Description
Technical Field
The application belongs to the technical field of communication, and particularly relates to a congestion control method, a congestion control device, a terminal and network side equipment.
Background
When the network is in a congested state, the network side device will reject the request of the terminal. If disaster (disaster) occurs in the first network, the terminal subscribed to the first network can access the second network, causing congestion of the second network, and when the second network executes congestion control, the second network can indiscriminately refuse requests of the terminal subscribed to the first network and the terminal subscribed to the second network, thereby affecting communication of the terminal subscribed to the second network.
Disclosure of Invention
An object of the embodiments of the present application is to provide a congestion control method, an apparatus, a terminal, and a network side device, which can solve the problem that communication performance of a contracted terminal of a second network is relatively poor in a congested state.
In order to solve the technical problem, the present application is implemented as follows:
in a first aspect, a congestion control method is provided, which is applied to a network side device of a second network, and includes:
performing congestion control in a case where the second network is in a congested state;
the congestion control includes:
preferentially rejecting request messages or services of the first terminal;
or, preferentially releasing the service or session of the first terminal;
or, preferentially registering the first terminal;
the second network is a network which provides services for the first terminal under the condition that the first network is in a disaster state, and the first terminal is a terminal which is signed to the first network.
In a second aspect, a congestion control method is provided, which is applied to a first terminal, and includes:
receiving backoff information sent by a second network, wherein the backoff information comprises a first backoff timer, the second network is a network for providing service for a first terminal under the condition that the first network is in a disaster state, and the first terminal is a terminal signed to the first network;
a first backoff timer is started.
In a third aspect, a congestion control apparatus is provided, which is applied to a network side device of a second network, and includes:
an execution module configured to execute congestion control when the second network is in a congested state;
the congestion control includes:
preferentially rejecting request messages or services of the first terminal;
or, preferentially releasing the service or session of the first terminal;
or, preferentially registering the first terminal;
the second network is a network which provides services for the first terminal under the condition that the first network is in a disaster state, and the first terminal is a terminal which is signed to the first network.
In a fourth aspect, a congestion control apparatus is provided, which is applied to a first terminal, and includes:
a receiving module, configured to receive backoff information sent by a second network, where the backoff information includes a first backoff timer, the second network is a network that provides a service for a first terminal when the first network is in a disaster state, and the first terminal is a terminal that has signed a contract with the first network;
and the starting module is used for starting the first backoff timer.
In a fifth aspect, a network side device is provided, where the terminal includes a processor, a memory, and a program or an instruction stored in the memory and executable on the processor, and the program or the instruction, when executed by the processor, implements the steps of the congestion control method according to the first aspect.
In a sixth aspect, a terminal is provided, comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the congestion control method according to the second aspect.
In a seventh aspect, there is provided a readable storage medium on which a program or instructions are stored, which program or instructions, when executed by a processor, implement the steps of the congestion control method according to the first aspect, or implement the steps of the congestion control method according to the second aspect.
In an eighth aspect, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or instruction, to implement the congestion control method according to the first aspect, or to implement the congestion control method according to the second aspect.
In the embodiment of the present application, in the case where the second network is in a congested state, congestion control is performed; the congestion control includes: preferentially rejecting request messages or services of the first terminal; or, preferentially releasing the service or session of the first terminal; or, preferentially registering the first terminal; the second network is a network which provides services for the first terminal under the condition that the first network is in a disaster state, and the first terminal is a terminal which is signed to the first network. By executing congestion control, the service of the terminal subscribed to the second network can be guaranteed preferentially, and the communication performance of the subscribed terminal of the second network in the congestion state is improved.
Drawings
Fig. 1 is a block diagram of a network system according to an embodiment of the present application;
fig. 2 is a flowchart of a congestion control method provided in an embodiment of the present application;
fig. 3 is a second flowchart of a congestion control method according to an embodiment of the present application;
fig. 4a to fig. 4d are flowcharts illustrating information interaction between devices according to an embodiment of the present disclosure;
fig. 5 is a block diagram of a first congestion control apparatus according to an embodiment of the present application;
fig. 6 is a structural diagram of a second congestion control apparatus according to an embodiment of the present application;
fig. 7 is a block diagram of a communication device provided in an embodiment of the present application;
fig. 8 is a structural diagram of a terminal provided in an embodiment of the present application;
fig. 9 is a structural diagram of a network-side device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.
It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications, such asGeneration 6 (6)thGeneration, 6G) communication system.
Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but a specific type of the Base Station is not limited.
The congestion control method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.
Referring to fig. 2, fig. 2 is a flowchart of a congestion control method provided in an embodiment of the present application, where the congestion control method is applied to a network-side device of a second network, and includes:
the congestion control includes:
preferentially rejecting request messages or services of the first terminal;
or, preferentially releasing the service or session of the first terminal;
or, preferentially registering the first terminal;
the second network is a network which provides services for the first terminal under the condition that the first network is in a disaster state, and the first terminal is a terminal which is signed to the first network.
As described above, a disaster condition (disasserter condition) may be a condition that causes a breakdown or abnormality in the first network, which may not be able to provide a service. It is to be understood that the disaster situation in this application is only a generalized concept, that is, any other situation that causes the first network to be in a breakdown state or needs another network to serve the first network can be considered as the situation that the first network is in the disaster situation. The second network is a network capable of providing services to the first network in the event of a disaster condition in the first network. The first network and the second network may agree that the first network is in a disaster state such that the second network provides services to the first network in the event that the first network is in a disaster state.
The second network and the first network may belong to the same operator or may belong to different operators. The first terminal is a terminal subscribed to the first Network, and a home Network or a home Public Land Mobile Network (PLMN) of the first terminal is the first Network, that is, the first Network may be a Network or a PLMN in a disaster state. The second network is a network or PLMN that can serve the first network in a disaster situation.
Performing congestion control in a case where the second network is in a congested state, the congestion control including: preferentially rejecting request messages or services of the first terminal; or, preferentially releasing the service or session of the first terminal; or, preferentially registering the first terminal.
For example, when the second network is in a congested state, if a request message sent by the first terminal is received, congestion control is performed to preferentially reject the request message of the first terminal and guarantee a service of the second terminal, where the second terminal is a terminal subscribed to the second network.
In this embodiment, in a case where the second network is in a congested state, congestion control is performed; the congestion control includes: preferentially rejecting request messages or services of the first terminal; or, preferentially releasing the service or session of the first terminal; or, preferentially registering the first terminal; the second network is a network which provides services for the first terminal under the condition that the first network is in a disaster state, and the first terminal is a terminal which is signed to the first network. By executing congestion control, the service of the terminal subscribed to the second network can be guaranteed preferentially, and the communication performance of the subscribed terminal of the second network in the congestion state is improved.
In the above, the preferentially rejecting the request message or the service of the first terminal includes:
and rejecting the request message or service of the first terminal, and responding to at least part of the request message or service of a second terminal, wherein the second terminal is a terminal signed to the second network to respond to the service of the second terminal preferentially.
The congestion control further comprises: and sending back-off information to the first terminal, wherein the back-off information comprises a first back-off timer. The first terminal starts the first back-off timer after receiving the first back-off timer, and in the running process of the first back-off timer, the first terminal cannot send a request message or service to the second network, so that the second network can respond to the service of the second terminal, and the service of the second terminal is preferentially guaranteed.
Further, the backoff information further includes at least one of a cause value indicating congestion and a disaster area; the cause value is used for indicating the reason and/or the type of congestion control executed by the second network, and the disaster area is an effective area in which the first back-off timer runs.
The disaster area is a disaster area to which the first network is applicable in a disaster state, and in the disaster area, the first terminal cannot access the first network. The disaster area may be preset, for example, a fixed disaster area is preset for the first network, or the disaster area is dynamically determined according to the actual situation, for example, the network side device of the first network dynamically determines the disaster area according to the cause of the disaster state of the first network, and sends the disaster area to the network side device of the second network, and the network side device of the second network sends the disaster area to the first terminal. The determination of the disaster area can be flexibly set according to the actual situation, and is not limited herein.
The first back-off timer may be stopped if the first terminal moves out of the disaster area.
Different control modes for the first terminal under two congestion types are provided below.
In a first case, that is, in a case where the cause value indicates a first congestion type, the first congestion type is used to indicate that the first terminal is prohibited from sending a Non-Access Stratum (NAS) signaling message to the second network. The first terminal does not initiate a NAS signaling message to the second network after receiving the cause value indicating the first congestion type.
In a second case, that is, in a case where the cause value indicates a second congestion type, the second congestion type is used to indicate that the first terminal is prohibited from sending NAS signaling messages related to session management to the second network;
and/or the second congestion type is used for indicating that the first terminal is allowed to send a mobility management related NAS signaling message to the second network.
If the cause value indicates the second congestion type, the first terminal may not be able to send a session management related NAS signaling message to the second network, and/or the first terminal may send a mobility management related NAS signaling message to the second network.
Further, after the performing congestion control, the method further includes:
receiving disaster relief information sent by the first network;
and sending the disaster relief information to the first terminal.
The disaster relief information is used to instruct the first network to recover to normal. And after receiving the disaster contact information sent by the network side equipment of the first network, the network side equipment of the second network sends the disaster relief information to the first terminal. Specifically, the network side device of the second network may carry the disaster relief information in an NAS message, a Radio Resource Control (RRC) message, or a system message, and send the NAS message, the RRC message, or the system message to the first terminal.
Referring to fig. 3, fig. 3 is a flowchart of a congestion control method provided in an embodiment of the present application, where the congestion control method is applied to a first terminal, and includes:
The first terminal starts the first back-off timer after receiving the first back-off timer, and in the running process of the first back-off timer, the first terminal cannot send a request message or service to the second network, so that the second network can respond to the service of the second terminal, and the service of the second terminal is preferentially guaranteed, and the second terminal is a terminal signed to the second network.
In this embodiment, a first terminal receives backoff information sent by a second network, where the backoff information includes a first backoff timer, the second network is a network that provides a service for the first terminal when the first network is in a disaster state, and the first terminal is a terminal that signs up to the first network; a first backoff timer is started. By the method, the second network can preferentially respond to the service of the second terminal, and the communication performance of the terminal which is signed to the second network in the congestion state of the second network is improved.
Further, the backoff information further includes at least one of a cause value indicating congestion and a disaster area; the cause value is used for indicating the cause and/or type of congestion control, and the disaster area is an effective area in which the first back-off timer runs.
The disaster area is a disaster area to which the first network is applicable in a disaster state, and in the disaster area, the first terminal cannot access the first network. The disaster area may be preset, for example, a fixed disaster area is preset for the first network, or the disaster area is dynamically determined according to the actual situation, for example, the network side device of the first network dynamically determines the disaster area according to the cause of the disaster state of the first network, and sends the disaster area to the network side device of the second network, and the network side device of the second network sends the disaster area to the first terminal. The determination of the disaster area can be flexibly set according to the actual situation, and is not limited herein. The first back-off timer may be stopped if the first terminal moves out of the disaster area.
Different control modes for the first terminal under two congestion types are provided below.
In a first case, that is, in a case where the cause value indicates a first congestion type, the first congestion type is used to indicate that the first terminal is prohibited from sending a Non-Access Stratum (NAS) signaling message to the second network. The first terminal does not initiate a NAS signaling message to the second network after receiving the cause value indicating the first congestion type.
In a second case, that is, in a case where the cause value indicates a second congestion type, the second congestion type is used to indicate that the first terminal is prohibited from sending NAS signaling messages related to session management to the second network;
and/or the second congestion type is used for indicating that the first terminal is allowed to send a mobility management related NAS signaling message to the second network.
If the cause value indicates the second congestion type, the first terminal may not be able to send a session management related NAS signaling message to the second network, and/or the first terminal may send a mobility management related NAS signaling message to the second network.
Further, after the starting the first backoff timer, the method further includes:
receiving disaster relief information sent by the first network or the second network;
stopping the first backoff timer.
The disaster relief information is used to instruct the first network to recover to normal. The network side device of the first network may directly send the disaster relief information to the first terminal, or may send the disaster relief information to the network side device of the second network, and the network side device of the second network sends the disaster relief information to the first terminal. Specifically, the disaster relief information is carried in a NAS message, an RRC message, or a system message.
The first terminal stops the first back-off timer after receiving the disaster release message.
Further, after the starting the first backoff timer, the method further includes:
stopping the first back-off timer if the first terminal is not in the disaster area;
initiating a de-registration process with the second network;
a first network selection is performed.
If the first terminal moves out of the disaster area after starting the first back-off timer, namely the first terminal is not in the disaster area, the first back-off timer is stopped, a de-registration process is initiated to the second network, and first network selection is executed, namely PLMN selection is executed, so as to select the first network. After selecting the first network, the first terminal may send request information or a service to the first network.
Further, before the receiving the backoff information sent by the second network, the method further includes:
under the condition that the first terminal starts a second backoff timer, if receiving information that the first network enters a disaster state, stopping the second backoff timer, wherein the second backoff timer is configured to the first terminal by the first network;
performing a public land mobile network, PLMN, selection in a disaster situation to select the second network.
In the above, the first network is a network that provides a service for the first terminal when the network subscribed by the first terminal is in a disaster state. And if the information that the first network enters the disaster state is received, namely the first network is also in the disaster state, stopping the second backoff timer, and performing PLMN selection in the disaster state to select the second network, wherein in this case, the second network is a network for providing services for the first terminal under the condition that the network signed by the first terminal is in the disaster state.
The information of the disaster state of the first network is carried in the system message of the second network and is sent to the first terminal by the second network.
The congestion control method provided in the present application is exemplified below.
As shown in fig. 4a, under congestion control of the second network, the second network preferentially guarantees the service of the second terminal and rejects the request of the first terminal, and the congestion control method includes:
step 410, the first network is in a disaster state (disasserter condition), wherein the second network is a network that provides services for the first network in the disaster state;
step 411, after the second network has network congestion, executing congestion control, wherein the execution principle is that the second network preferentially rejects the request of the first terminal and preferentially ensures the service of the second terminal, and the second terminal is a terminal signed to the second network;
step 412, under the congestion control of the second network, the second network sends the first backoff timer to the first terminal, and optionally sends a cause value for indicating congestion and/or a disaster area;
step 413, after receiving the first back-off timer sent by the second network, the first terminal starts the first back-off timer, and during the operation of the first back-off timer, the first terminal cannot initiate a signaling request process on the second network.
In the above, the types of cause value indications are different, and the congestion control method for the first terminal is also different.
In case the cause value indicates a first congestion type, the second network performs a first congestion control, i.e.,
executing first congestion control after the second network is congested, wherein the execution principle is that the second network preferentially rejects the request of the first terminal;
under the control of the first congestion, the second network sends a first backoff timer, optionally, a cause value for indicating congestion and/or a disaster area to the first terminal;
and the first terminal starts the first back-off timer after receiving the first back-off timer sent by the second network, and the first terminal cannot initiate an NAS request process on the second network when the first back-off timer runs.
In case the cause value indicates the first congestion type, the second network performs a second congestion control, i.e.,
executing second congestion control after the second network has network congestion, wherein the execution principle is that the second network preferentially rejects the request of the first terminal;
under the control of the second congestion, the second network sends the first back-off timer, optionally, a cause value for indicating congestion and/or a disaster area to the first terminal;
the first terminal starts the first back-off timer after receiving the first back-off timer sent by the second network, and during the operation of the first back-off timer, the first terminal may initiate a NAS signaling procedure related to mobility management on the second network, but cannot initiate a NAS signaling procedure related to session management.
The second network and the first network may belong to different operators; the second network may provide services for the first network in a disaster state; the first terminal is a terminal subscribed to the first Network, and may also be understood that a Home Public Land Mobile Network (HPLMN) to which the first terminal belongs is the first Network; the disaster area is the effective range in which the first back-off timer runs.
As shown in fig. 4b, when the first terminal has the first back-off timer running, the first back-off timer is stopped after receiving the disaster release information of the first network. The congestion control method comprises the following steps:
step 420, the first terminal is running a first back-off timer provided by the second network;
step 421, the first terminal receives disaster relief information of the first network, where the disaster relief information of the first network may be sent by the first network or sent by the second network, that is, step 421 may include step 421a, sending a first back-off timer by the first network, or step 421b, sending the first back-off timer by the second network;
step 423, the first terminal stops the first back-off timer after receiving the disaster relief message of the first network.
As shown in fig. 4c, after moving out of the disaster area, the first terminal stops the first back-off timer and initiates a logout procedure to the second network. The congestion control method comprises the following steps:
step 430, the first terminal moves out of the disaster area;
step 431, the first terminal stops the first back-off timer;
step 432, the first terminal initiates a deregistration process to the second network.
The disaster area is an area to which the first network is applicable in a disaster state, and in the disaster area, the first terminal cannot access the first network.
As shown in fig. 4d, the first terminal has a running second back-off timer, and after receiving the information that the first network enters the disaster state, the first terminal stops the second back-off timer and enters PLMN selection in the disaster state. The congestion control method comprises the following steps:
step 441, the first terminal is running a second back-off timer;
step 442, the first terminal receives the information that the first network enters the disaster state, which may specifically include step 442a, sending the information that the first network enters the disaster state, or step 442b, sending the information that the second network enters the disaster state;
step 443, the first terminal stops the second back-off timer;
step 444, the first network enters PLMN selection in a disaster state to select the second network.
According to the congestion control method, in a disaster (disaster) scene, a network providing service for a network in a disaster state performs congestion control preferentially on a terminal of the disaster network (namely, the network in the disaster state), namely preferentially refusing a request of the terminal of the disaster network, and provides a back-off timer and a cause value, so that the situation that the user experience of the terminal of the network is reduced due to the fact that the service is provided for the terminal of the disaster network is avoided.
It should be noted that, in the congestion control method provided in the embodiment of the present application, the execution subject may be a congestion control device, or a control module in the congestion control device for executing the congestion control method. In the embodiment of the present application, a congestion control device executes a congestion control method as an example, and the congestion control device provided in the embodiment of the present application is described.
Referring to fig. 5, fig. 5 is a structural diagram of a congestion control apparatus according to an embodiment of the present application, and a first congestion control apparatus 500 applied to a network side device of a second network includes:
an executing module 501, configured to execute congestion control when the second network is in a congested state;
the congestion control includes:
preferentially rejecting request messages or services of the first terminal;
or, preferentially releasing the service or session of the first terminal;
or, preferentially registering the first terminal;
the second network is a network which provides services for the first terminal under the condition that the first network is in a disaster state, and the first terminal is a terminal which is signed to the first network.
Further, the preferentially rejecting the request message or service of the first terminal includes:
rejecting the request message or service of the first terminal and responding to at least part of the request message or service of a second terminal, wherein the second terminal is a terminal signed to the second network.
Further, the congestion control further includes:
and sending back-off information to the first terminal, wherein the back-off information comprises a first back-off timer.
Further, the backoff information further includes at least one of a cause value indicating congestion and a disaster area;
the cause value is used for indicating the cause and/or type of congestion control performed by the second network, and the disaster area is an effective area in which the first back-off timer is operated.
Further, in a case that the cause value indicates a first congestion type, the first congestion type is used to indicate that the first terminal is prohibited from sending NAS signaling messages to the second network.
Further, in a case that the cause value indicates a second congestion type, the second congestion type is used to indicate that the first terminal is prohibited from sending NAS signaling messages related to session management to the second network;
and/or the second congestion type is used for indicating that the first terminal is allowed to send a mobility management related NAS signaling message to the second network.
Further, the first congestion control apparatus 500 further includes:
the receiving module is used for receiving disaster relief information sent by the first network;
and the sending module is used for sending the disaster relief information to the first terminal.
Further, the sending module is specifically configured to:
and carrying the disaster relief information in NAS information, RRC information or system information and sending the NAS information, RRC information or system information to the first terminal.
The first congestion control apparatus 500 in the embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal.
The first congestion control device 500 in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.
The first congestion control apparatus 500 provided in this embodiment of the present application can implement each process implemented in the method embodiment of fig. 2, and achieve the same technical effect, and for avoiding repetition, details are not described here again.
Referring to fig. 6, fig. 6 is a structural diagram of a second congestion control apparatus according to an embodiment of the present application, and the second congestion control apparatus 600 is applied to a first terminal, and is characterized by including:
a first receiving module 601, configured to receive backoff information sent by a second network, where the backoff information includes a first backoff timer, the second network is a network that provides a service for a first terminal when the first network is in a disaster state, and the first terminal is a terminal that signs up to the first network;
an initiating module 602 is configured to initiate a first backoff timer.
Further, the backoff information further includes at least one of a cause value indicating congestion and a disaster area;
the cause value is used for indicating the cause and/or type of congestion control, and the disaster area is an effective area in which the first back-off timer runs.
Further, in a case that the cause value indicates a first congestion type, the first congestion type is used to indicate that the first terminal is prohibited from sending NAS signaling messages to the second network.
Further, in a case that the cause value indicates a second congestion type, the second congestion type is used to indicate that the first terminal is prohibited from sending NAS signaling messages related to session management to the second network;
and/or the second congestion type is used for indicating that the first terminal is allowed to send a mobility management related NAS signaling message to the second network.
Further, the second congestion control apparatus 600 further includes:
the second receiving module is used for receiving disaster relief information sent by the first network or the second network;
a first stopping module, configured to stop the first backoff timer.
Further, the disaster relief information is carried in NAS messages, RRC messages, or system messages.
Further, the second congestion control apparatus 600 further includes:
a second stopping module, configured to stop the first backoff timer if the first terminal is not located in the disaster area;
a sending module, configured to initiate a deregistration process to the second network;
a first selection module to perform a first network selection.
Further, the second congestion control apparatus 600 further includes:
a third stopping module, configured to stop a second back-off timer if receiving information that the first network enters a disaster state when the first terminal has started the second back-off timer, where the second back-off timer is configured to the first terminal by the first network;
and the second selection module is used for selecting the public land mobile network PLMN in a disaster state so as to select the second network.
Further, the information that the first network enters the disaster state is carried in the system message of the second network.
The second congestion control apparatus 600 in the embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal.
The second congestion control device 600 in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.
The second congestion control device 600 provided in this embodiment of the present application can implement each process implemented in the method embodiment of fig. 3, and achieve the same technical effect, and is not described here again to avoid repetition.
Optionally, as shown in fig. 7, an embodiment of the present application further provides a communication device 70, which includes a processor 71, a memory 72, and a program or an instruction stored on the memory 72 and executable on the processor 71, for example, when the communication device 70 is a terminal, the program or the instruction is executed by the processor 71 to implement the processes of the congestion control method embodiment shown in fig. 3, and the same technical effect can be achieved. When the communication device 70 is a network-side device, the program or the instructions are executed by the processor 71 to implement the processes of the congestion control method embodiment shown in fig. 2, and the same technical effects can be achieved, and are not described herein again to avoid repetition.
Fig. 8 is a schematic diagram of a hardware structure of a terminal for implementing the embodiment of the present application.
The terminal 1000 includes, but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010.
Those skilled in the art will appreciate that terminal 1000 can also include a power supply (e.g., a battery) for powering the various components, which can be logically coupled to processor 1010 via a power management system to provide management of charging, discharging, and power consumption via the power management system. The terminal structure shown in fig. 8 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and thus will not be described again.
It should be understood that in the embodiment of the present application, the input Unit 1004 may include a Graphics Processing Unit (GPU) 10041 and a microphone 10042, and the Graphics Processing Unit 10041 processes image data of still pictures or videos obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also referred to as a touch screen. The touch panel 10071 may include two parts, a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.
In this embodiment of the application, the radio frequency unit 1001 receives downlink data from a network side device and then processes the downlink data to the processor 1010; in addition, the uplink data is transmitted to the base station. In general, radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
The memory 1009 may be used to store software programs or instructions and various data. The memory 1009 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, and the like) required for at least one function, and the like. Further, the Memory 1009 may include a high-speed random access Memory and may also include a nonvolatile Memory, where the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable PROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
The radio frequency unit 1001 is configured to receive backoff information sent by a second network, where the backoff information includes a first backoff timer, the second network is a network that provides a service for a first terminal when the first network is in a disaster state, and the first terminal is a terminal that has signed a contract to the first network;
a processor 1010 configured to start a first backoff timer.
Further, the backoff information further includes at least one of a cause value indicating congestion and a disaster area;
the cause value is used for indicating the cause and/or type of congestion control, and the disaster area is an effective area in which the first back-off timer runs.
Further, in a case that the cause value indicates a first congestion type, the first congestion type is used to indicate that the first terminal is prohibited from sending NAS signaling messages to the second network.
Further, in a case that the cause value indicates a second congestion type, the second congestion type is used to indicate that the first terminal is prohibited from sending NAS signaling messages related to session management to the second network;
and/or the second congestion type is used for indicating that the first terminal is allowed to send a mobility management related NAS signaling message to the second network.
Further, the radio frequency unit 1001 is further configured to receive disaster relief information sent by the first network or the second network;
stopping the first backoff timer.
Further, the disaster relief information is carried in NAS messages, RRC messages, or system messages.
Further, after the starting the first backoff timer, the method further includes:
a processor 1010, further configured to stop the first backoff timer if the first terminal is not located in the disaster area;
a radio frequency unit 1001, further configured to initiate a deregistration process to the second network;
the processor 1010 is further configured to perform a first network selection.
Further, before the receiving the backoff information sent by the second network, the method further includes:
the processor 1010 is further configured to, when a second backoff timer is started by the first terminal, stop the second backoff timer if information that the first network enters a disaster state is received, where the second backoff timer is configured to the first terminal by the first network; performing a public land mobile network, PLMN, selection in a disaster situation to select the second network.
Further, the information that the first network enters the disaster state is carried in the system message of the second network.
The terminal 1000 provided in the foregoing embodiment can implement each process implemented by the method embodiment in fig. 3, and achieve the same technical effect, and for avoiding repetition, details are not described here again.
Specifically, the embodiment of the application further provides a network side device. As shown in fig. 9, the network-side device 1100 includes: antenna 111, radio frequency device 112, baseband device 113. The antenna 111 is connected to a radio frequency device 112. In the uplink direction, the rf device 112 receives information through the antenna 111 and sends the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes information to be transmitted and transmits the information to the rf device 112, and the rf device 112 processes the received information and transmits the processed information through the antenna 111.
The above-mentioned band processing apparatus may be located in the baseband apparatus 113, and the method performed by the network side device in the above embodiment may be implemented in the baseband apparatus 113, where the baseband apparatus 113 includes the processor 114 and the memory 115.
The baseband device 113 may include at least one baseband board, for example, and a plurality of chips are disposed on the baseband board, as shown in fig. 9, wherein one chip, for example, the processor 114, is connected to the memory 115 to call the program in the memory 115 to perform the network operation shown in the above method embodiment.
The baseband device 113 may further include a network interface 116, for exchanging information with the radio frequency device 112, for example, a Common Public Radio Interface (CPRI).
Specifically, the network side device of the embodiment of the present invention further includes: the instructions or programs stored in the memory 115 and capable of being executed on the processor 114, and the processor 114 calls the instructions or programs in the memory 115 to execute the method executed by each module shown in fig. 5, and achieve the same technical effect, and are not described herein in detail to avoid repetition.
An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the method embodiments shown in fig. 2 to fig. 3, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.
The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or an instruction, to implement each process of the method embodiments in fig. 2 to 3, and achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network) to execute the methods according to the embodiments of the present application.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (26)
1. A congestion control method is applied to a network side device of a second network, and is characterized by comprising the following steps:
performing congestion control in a case where the second network is in a congested state;
the congestion control includes:
preferentially rejecting a request message or service of a first terminal;
or, preferentially releasing the service or session of the first terminal;
or, preferentially registering the first terminal;
the second network is a network which provides services for the first terminal under the condition that the first network is in a disaster state, and the first terminal is a terminal which is signed to the first network.
2. The method of claim 1, wherein the preferentially rejecting the request message or service of the first terminal comprises:
rejecting the request message or service of the first terminal and responding to at least part of the request message or service of a second terminal, wherein the second terminal is a terminal signed to the second network.
3. The method according to claim 1 or 2, wherein the congestion control further comprises:
and sending back-off information to the first terminal, wherein the back-off information comprises a first back-off timer.
4. The method of claim 3, wherein the backoff information further comprises at least one of a cause value indicating congestion and a disaster area;
the cause value is used for indicating the cause and/or type of congestion control performed by the second network, and the disaster area is an effective area in which the first back-off timer is operated.
5. The method of claim 4, wherein the first congestion type is used to indicate that the first terminal is prohibited from sending non-access stratum (NAS) signaling messages to the second network if the cause value indicates the first congestion type.
6. The method according to claim 4, wherein in case that the cause value indicates a second congestion type, the second congestion type is used to indicate that the first terminal is prohibited from sending session management related NAS signaling messages to the second network;
and/or the second congestion type is used for indicating that the first terminal is allowed to send a mobility management related NAS signaling message to the second network.
7. The method of claim 1, further comprising, after the performing congestion control:
receiving disaster relief information sent by the first network;
and sending the disaster relief information to the first terminal.
8. The method of claim 7, wherein sending the disaster relief information to the first terminal comprises:
and carrying the disaster relief information in NAS information, Radio Resource Control (RRC) information or system information, and sending the NAS information, the RRC information or the system information to the first terminal.
9. A congestion control method applied to a first terminal is characterized by comprising the following steps:
receiving backoff information sent by a second network, wherein the backoff information comprises a first backoff timer, the second network is a network for providing service for a first terminal under the condition that the first network is in a disaster state, and the first terminal is a terminal signed to the first network;
a first backoff timer is started.
10. The method of claim 9, wherein the backoff information further comprises at least one of a cause value indicating congestion and a disaster area;
the cause value is used for indicating the cause and/or type of congestion control, and the disaster area is an effective area in which the first back-off timer runs.
11. The method of claim 10, wherein the first congestion type is used to indicate that the first terminal is prohibited from sending non-access stratum (NAS) signaling messages to the second network if the cause value indicates the first congestion type.
12. The method of claim 10, wherein in case the cause value indicates a second congestion type, the second congestion type is used to indicate that the first terminal is prohibited from sending session management related NAS signaling messages to the second network;
and/or the second congestion type is used for indicating that the first terminal is allowed to send a mobility management related NAS signaling message to the second network.
13. The method of claim 9, further comprising, after the starting the first backoff timer:
receiving disaster relief information sent by the first network or the second network;
stopping the first backoff timer.
14. The method of claim 13, wherein the disaster relief information is carried in a NAS message, a radio resource control, RRC, message, or a system message.
15. The method of claim 9, further comprising, after the starting the first backoff timer:
stopping the first back-off timer if the first terminal is not in the disaster area;
initiating a de-registration process with the second network;
a first network selection is performed.
16. The method of claim 9, wherein before the receiving the backoff information sent by the second network, further comprising:
under the condition that the first terminal starts a second backoff timer, if receiving information that the first network enters a disaster state, stopping the second backoff timer, wherein the second backoff timer is configured to the first terminal by the first network;
performing a public land mobile network, PLMN, selection in a disaster situation to select the second network.
17. The method of claim 16, wherein the information that the first network entered a disaster state is carried in a system message of the second network.
18. A congestion control apparatus applied to a network side device of a second network, comprising:
an execution module configured to execute congestion control when the second network is in a congested state;
the congestion control includes:
preferentially rejecting a request message or service of a first terminal;
or, preferentially releasing the service or session of the first terminal;
or, preferentially registering the first terminal;
the second network is a network which provides services for the first terminal under the condition that the first network is in a disaster state, and the first terminal is a terminal which is signed to the first network.
19. The apparatus of claim 18, wherein the preferentially rejecting the request message or service of the first terminal comprises:
rejecting the request message or service of the first terminal and responding to at least part of the request message or service of a second terminal, wherein the second terminal is a terminal signed to the second network.
20. The apparatus according to claim 18 or 19, wherein the congestion control further comprises:
and sending back-off information to the first terminal, wherein the back-off information comprises a first back-off timer.
21. A congestion control apparatus applied to a first terminal, comprising:
a receiving module, configured to receive backoff information sent by a second network, where the backoff information includes a first backoff timer, the second network is a network that provides a service for a first terminal when the first network is in a disaster state, and the first terminal is a terminal that has signed a contract with the first network;
and the starting module is used for starting the first backoff timer.
22. The apparatus of claim 21, wherein the backoff information further comprises at least one of a cause value indicating congestion and a disaster area;
the cause value is used for indicating the cause and/or type of congestion control, and the disaster area is an effective area in which the first back-off timer runs.
23. The apparatus of claim 22, wherein the first congestion type is used to indicate that the first terminal is prohibited from sending NAS signaling messages to the second network if the cause value indicates the first congestion type.
24. A network-side device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the congestion control method according to any one of claims 1 to 8.
25. A terminal comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, which program or instructions, when executed by the processor, carry out the steps of the congestion control method according to any of claims 9 to 17.
26. A readable storage medium, characterized in that it stores thereon a program or instructions which, when executed by a processor, implement the steps of the congestion control method according to any one of claims 1 to 8, or which, when executed by a processor, implement the steps of the congestion control method according to any one of claims 9 to 17.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011063723.8A CN114363954A (en) | 2020-09-30 | 2020-09-30 | Congestion control method and device, terminal and network side equipment |
| PCT/CN2021/121310 WO2022068813A1 (en) | 2020-09-30 | 2021-09-28 | Congestion control method and apparatus, and terminal and network-side device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011063723.8A CN114363954A (en) | 2020-09-30 | 2020-09-30 | Congestion control method and device, terminal and network side equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114363954A true CN114363954A (en) | 2022-04-15 |
Family
ID=80949667
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011063723.8A Pending CN114363954A (en) | 2020-09-30 | 2020-09-30 | Congestion control method and device, terminal and network side equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114363954A (en) |
| WO (1) | WO2022068813A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023214832A1 (en) * | 2022-05-04 | 2023-11-09 | Samsung Electronics Co., Ltd. | Method and apparatus for obtaining emergency service in telecommunication system |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103379659B (en) * | 2012-04-17 | 2016-08-03 | 电信科学技术研究院 | Access request implementation method and device under a kind of multipriority scene |
| ES2689847T3 (en) * | 2013-09-17 | 2018-11-16 | Intel IP Corporation | Congestion control for short messaging service in 3rd Generation Association Project (3GPP) systems |
| US10034325B2 (en) * | 2015-09-24 | 2018-07-24 | Mediatek Inc. | Enhance at command for backoff timer control |
| JP7045808B2 (en) * | 2017-06-19 | 2022-04-01 | シャープ株式会社 | UE and UE communication control method |
| CN110063087A (en) * | 2017-11-07 | 2019-07-26 | 联发科技股份有限公司 | The method and apparatus of back-off timer are handled in session management layer congestion control |
| CN110719607B (en) * | 2018-07-12 | 2021-03-16 | 维沃移动通信有限公司 | Network congestion indication method, device and equipment |
| CN110602744B (en) * | 2019-09-06 | 2020-08-07 | 南京大鱼半导体有限公司 | Method and device for congestion control of Internet of things, storage medium and electronic equipment |
-
2020
- 2020-09-30 CN CN202011063723.8A patent/CN114363954A/en active Pending
-
2021
- 2021-09-28 WO PCT/CN2021/121310 patent/WO2022068813A1/en active Application Filing
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023214832A1 (en) * | 2022-05-04 | 2023-11-09 | Samsung Electronics Co., Ltd. | Method and apparatus for obtaining emergency service in telecommunication system |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022068813A1 (en) | 2022-04-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2022089565A1 (en) | Secondary cell group information configuration, acquisiton method, and communication device | |
| CN114339811A (en) | Method and device for executing target operation and terminal equipment | |
| CN113965993A (en) | Direct communication starting control method and related equipment | |
| CN115150904B (en) | Communication path switching method, device and terminal | |
| US20230328789A1 (en) | Busy indication transmission method and apparatus | |
| US20230362884A1 (en) | Information Processing Method and Device | |
| WO2022068813A1 (en) | Congestion control method and apparatus, and terminal and network-side device | |
| EP4243502A1 (en) | Relay communication method and device | |
| CN114080045B (en) | Data transmission processing method, resource allocation method and related equipment | |
| KR20230107874A (en) | Secondary cell group control method, terminal and network-side device | |
| CN114302492A (en) | Slicing request method, terminal and network side equipment | |
| CN115134797B (en) | Emergency service processing method, network side equipment and terminal | |
| CN114071645B (en) | Access control method, device, terminal and network side equipment | |
| CN114071445B (en) | Configuration method of information transmission mode, terminal and network side equipment | |
| CN115086882B (en) | Transmission method, apparatus, device, and readable storage medium | |
| US20230262794A1 (en) | Method for establishing connected state, terminal, core network function, and access network device | |
| CN113784384B (en) | Mode switching method, terminal and network side equipment | |
| US20230345340A1 (en) | Network-changing method and apparatus, and terminal | |
| WO2023066289A1 (en) | Cell reselection method and apparatus, and related device | |
| CN114071797A (en) | Information transmission method and device, multi-card terminal and readable storage medium | |
| CN115134761A (en) | Switching method, device, network side equipment and terminal | |
| CN114828293A (en) | Connection maintaining method and device and electronic equipment | |
| CN114980151A (en) | Validity checking method and device for system information block, terminal and storage medium | |
| CN115278788A (en) | Method, device and equipment for processing radio link failure and readable storage medium | |
| CN116939889A (en) | Resource control method, device, terminal and network side equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |