Method and device for transmitting busy indication

Abstract

This application discloses a method and apparatus for transmitting a busy indication, belonging to the field of wireless communication technology. The method for transmitting a busy indication includes: after a terminal receives a paging message, it determines whether to send a busy indication to the network side; if it determines to send a busy indication to the network side, it sends the busy indication to the network side. In this application, when a terminal receives a paging message, if the conditions for sending a busy indication are met, it can send a busy indication to the network side, thereby enabling the network side to perform corresponding processing and avoiding the waste of network resources caused by continuing to paging the terminal. If the conditions are not met, the terminal can choose not to send a busy indication, thereby minimizing the impact on the services currently being performed by the terminal.

Description

Technical Field

[0001] This application belongs to the field of wireless communication technology, and specifically relates to a method and apparatus for transmitting a busy indication. Background Technology

[0002] Currently, the market offers not only single-SIM terminals but also dual-SIM or multi-SIM terminals, collectively referred to as multi-SIM terminals. Multiple SIM cards may originate from the same or different operators and can be physical cards or virtual cards, such as eSIMs. Multi-SIM terminals can offer single-transmit / single-receive, single-transmit / dual-receive, and dual-transmit / dual-receive capabilities. A key feature of multi-SIM terminals is their ability to reside on multiple networks. However, the implementation methods differ. Some multi-SIM terminals can simultaneously send and receive on multiple networks without interference. Others, while residing on multiple networks, may employ a time-division multiplexing approach. For example, they might reside on network A for a period listening for paging requests, and then switch to network B for another period to listen for paging requests. Alternatively, they might maintain a connected state on network A for a period sending and receiving data, while switching to network B for another period to receive paging requests. Or, they might maintain a connected state on network A for a period sending and receiving data, while establishing a connection on network B for another period to send and receive data.

[0003] In Rel-17 or later protocol versions, the air interface paging message sent by the network may carry a paging cause value to indicate why the network is paging the UE. For example, the network may be paging the UE because a VoNR service (i.e., a voice call) has arrived. The UE can determine its subsequent behavior based on the paging cause value carried in the paging message received from the air interface. For example, if the terminal is a dual-SIM terminal, and SIM 1 is playing a game, if SIM 2 receives a paging message with a paging cause value of VoNR, the terminal may choose to initiate a Radio Resource Control (RRC) connection establishment on SIM 2 or restore the RRC connection to the RRC connected state to send and receive the corresponding data. As another example, if SIM 1 is making a voice call, and SIM 2 receives a paging message with a paging cause value of SMS, the multi-SIM terminal may choose not to process SIM 2's service. In this case, the network of SIM 2 may not know that the UE has chosen not to process SIM 2's service, and thus continue paging the UE, resulting in a waste of network resources. Summary of the Invention

[0004] The purpose of this application is to provide a method and apparatus for transmitting busy indications, which can solve the problem that when a terminal chooses not to process the service that triggers the current paging, the network side continues to paging the terminal, resulting in a waste of network resources.

[0005] To solve the above-mentioned technical problems, this application is implemented as follows:

[0006] Firstly, a method for transmitting a busy indication is provided, executed by a terminal, the method comprising:

[0007] Upon receiving a paging message, determine whether to send a busy indication to the network side;

[0008] If it is determined that a busy indication should be sent to the network side, then the busy indication should be sent to the network side.

[0009] Secondly, a method for transmitting a busy indication is provided, executed by a network-side device, the method comprising:

[0010] Receive busy indication sent by the terminal;

[0011] Perform the corresponding operation based on the busy indicator.

[0012] Thirdly, a busy indication transmission device is provided, comprising:

[0013] The judgment module is used to determine whether to send a busy indication to the network side after listening for a paging message;

[0014] The first sending module is used to send a busy indication to the network side if it is determined that a busy indication should be sent.

[0015] Fourthly, a busy indication transmission device is provided, comprising:

[0016] The first receiving module is used to receive busy indications sent by the terminal;

[0017] The processing module is used to perform the corresponding operation according to the busy indication.

[0018] Fifthly, a terminal is provided, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0019] In a sixth aspect, a network-side device is provided, the network-side device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as described in the second aspect.

[0020] In a seventh aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0021] Eighthly, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run network-side device programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0022] In a ninth aspect, a program product is provided, the program product being stored in a non-volatile storage medium, the program product being executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0023] In this embodiment, when a terminal receives a paging message, if the conditions for sending a busy indication are met, it can send a busy indication to the network side, enabling the network side to perform corresponding processing and avoiding the waste of network resources caused by continuing to paging the terminal. If the conditions are not met, the terminal can choose not to send a busy indication, thereby minimizing the impact on the services currently being performed by the terminal. Attached Figure Description

[0024] Figure 1 This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0025] Figure 2 This is a flowchart illustrating the method for transmitting a busy indication according to an embodiment of this application;

[0026] Figure 3 This is a flowchart illustrating the method for transmitting a busy indication according to an embodiment of this application;

[0027] Figure 4 This is a schematic diagram of the structure of the busy indication transmission device according to an embodiment of this application;

[0028] Figure 5 This is a schematic diagram of the structure of the busy indication transmission device according to an embodiment of this application;

[0029] Figure 6 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0030] Figure 7 This is a schematic diagram of the hardware structure of the terminal according to an embodiment of this application;

[0031] Figure 8 This is a schematic diagram of the hardware structure of the network-side device according to an embodiment of this application. Detailed Implementation

[0032] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0033] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0034] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can 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 this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. However, the following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description, although these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0035] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or user equipment (UE). The terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), etc. Wearable devices include wristbands, headphones, glasses, etc. It should be noted that this application does not limit the specific type of terminal 11. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this embodiment of the application, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0036] The method and apparatus for transmitting busy indications provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0037] To avoid redundancy, unless otherwise specified in this application, Figure 2 The specific methods described in the embodiments can be extended to other embodiments in this application.

[0038] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating a busy indication transmission method according to an embodiment of this application. The method is executed by a terminal and includes:

[0039] Step 21: After receiving a paging message, determine whether to send a busy indication to the network side;

[0040] Step 22: If it is determined that a busy indication should be sent to the network side, then send the busy indication to the network side.

[0041] The terminal in this application embodiment can be a single-SIM terminal or a multi-SIM terminal.

[0042] When the terminal in this embodiment is a multi-card terminal, the terminal can be regarded as the terminal corresponding to one of the multiple cards of the multi-card terminal.

[0043] In this embodiment, when a terminal receives a paging message, if the conditions for sending a busy indication are met, it can send a busy indication to the network side, enabling the network side to perform corresponding processing and avoiding the waste of network resources caused by continuing to paging the terminal. If the conditions are not met, the terminal can choose not to send a busy indication, thereby minimizing the impact on the services currently being performed by the terminal.

[0044] In other embodiments of this application, the terminal may also be a single-SIM terminal. For example, when the terminal does not want to handle the service that triggered the paging, it can send a busy indication to the network side, enabling the network side to perform the corresponding processing and avoiding the waste of network resources caused by continuing to paging the terminal. If the conditions are not met, the terminal may choose not to send a busy indication, thereby minimizing the impact on the service currently being performed by the terminal.

[0045] In this embodiment of the application, optionally, the busy indicator includes at least one of the following: RRC layer busy indicator and Non-Access Stratum (NAS) busy indicator. It can also be represented as: AS layer busy indicator and NAS busy indicator.

[0046] In this embodiment of the application, optionally, after detecting a paging message, determining whether to send a busy indication to the network side includes:

[0047] If at least one of the first, second, and third conditions is met, it is determined that the busy indication will be sent to the network side, wherein:

[0048] The first condition includes at least one of the following:

[0049] A1) The paging message is sent by the network side of one of the cards of the terminal, and the service priority corresponding to the paging message is lower than or equal to the service priority that the terminal is executing or will execute on other cards;

[0050] In this embodiment, the terminal can be a multi-SIM terminal. Condition A1) above can also be interpreted as: the service priority corresponding to the paging message received by the terminal is lower than or equal to the service priority being executed or to be executed by other terminals, wherein the other terminals and the terminal refer to multiple terminals corresponding to multiple cards of a multi-SIM terminal. Alternatively, the service priority corresponding to the paging message is lower than or equal to the service priority being executed or to be executed by other terminals, wherein the other terminals and the terminal are related to or share the same user equipment.

[0051] In this embodiment, the service priority corresponding to the paging message and the service priority of the terminal in other cards being executed or to be executed can be implemented by the terminal, agreed upon by a protocol, or configured by the network side. The service priority corresponding to the paging message can be the service type indicated by the paging reason value carried in the paging message.

[0052] A2) The paging message is sent by the network side of one of the cards in the terminal, and the other cards in the terminal are executing or will execute preset services;

[0053] The preset services are, for example, voice services or games.

[0054] In this embodiment of the application, the terminal can be a multi-SIM terminal. Condition A2) above can also be interpreted as: when the terminal receives a paging message, other terminals are executing or about to execute a preset service, wherein the other terminals and the terminal are multiple terminals corresponding to multiple cards of a multi-SIM terminal, or the other terminals and the terminal are related to or share the same user equipment.

[0055] In this embodiment of the application, the preset service can be implemented by the terminal, agreed upon by the protocol, or configured by the network side.

[0056] A3) Before the terminal hears the paging message, it has not sent any departure indication information to the network side. The departure indication information is used to indicate that the terminal cannot send or receive data on the network side.

[0057] The departure indication information includes: departure message, departure request, departure notification, negotiated departure, handover notification, or handover request, etc. These are all used to indicate that the terminal cannot send or receive data on the network side, or to request the network side to release the terminal, or to indicate that the terminal cannot listen to and / or respond to paging, or to indicate that the terminal is busy on other SIM cards, or to indicate that the terminal leaves the network side, or to indicate that the terminal switches to the network side corresponding to another SIM card.

[0058] One implementation involves the terminal not sending the departure indication information to the network side within a preset time period prior to receiving the paging message. This preset time period can be implemented based on the terminal, network configuration, or protocol agreement.

[0059] A4) The terminal did not send the busy indication to the network side before it heard the paging message;

[0060] One implementation involves the terminal not sending the busy indication to the network side within a preset time period prior to receiving the paging message. This preset time period can be implemented based on the terminal, network configuration, or protocol agreement.

[0061] The second condition includes at least one of the following:

[0062] B1) The anchor base station or the last serving base station can receive or process the RRC layer busy indication or request the terminal to send the RRC layer busy indication;

[0063] In this embodiment of the application, if the terminal is a multi-card terminal, the anchor base station or the last-served base station is the anchor base station or the last-served base station of the card that received the paging message.

[0064] In this embodiment, the anchor base station or the last-served base station can notify the terminal via dedicated signaling or broadcast messages that, upon receiving a paging message from the network, if it is busy or unable to process the service that triggered the paging, it requests to send the RRC layer busy indication information to the network. Alternatively, the anchor base station or the last-served base station can notify the terminal via dedicated signaling or broadcast messages that the network side can receive and / or process the RRC layer busy indication information.

[0065] B2) The anchor base station or the last-served base station supports sending paging reason values;

[0066] In this embodiment, the anchor base station or the last-served base station supports sending paging reason values. This means that when the terminal receives a paging message from the anchor base station or the last-served base station, it may decide to send the busy indication based on the paging reason value. Therefore, the anchor base station or the last-served base station may also support receiving the busy indication. The terminal can also determine whether the anchor base station or the last-served base station supports sending paging reason values ​​based on protocol agreements or other information. For example, if sending paging reason values ​​is supported within a PLMN, the terminal can obtain PLMN information to determine whether the anchor base station or the last-served base station supports sending paging reason values.

[0067] B3) The anchor base station or the last-served base station supports functions or features related to multi-SIM terminals;

[0068] The third condition includes at least one of the following:

[0069] C1) The core network is able to receive or process NAS busy indications or request the terminal to send NAS busy indications;

[0070] In this embodiment of the application, if the terminal is a multi-card terminal, the core network is the core network of the card that receives the paging message.

[0071] Optionally, the core network may include, but is not limited to, at least one of the following: core network equipment, core network nodes, core network functions, core network elements, Mobility Management Entity (MME), Access Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Serving Gateway (SGW), PDN Gateway (PDN Gateway), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Serving GPRS Support Node (SGSN), Gateway GPRS Support Node (GGSN), and Application Function.

[0072] C2) The core network supports sending paging reason values;

[0073] C3) The core network supports functions or features related to multi-card terminals.

[0074] To avoid redundancy, unless otherwise specified, the specific descriptions of the first and second conditions can also be applied to the third condition.

[0075] In this embodiment of the application, optionally, after detecting a paging message, determining whether to send a busy indication to the network side includes:

[0076] If at least one of the fourth, fifth, and sixth conditions is met, it is determined that the busy indication will not be sent to the network side, wherein:

[0077] The fourth condition includes at least one of the following:

[0078] D1) The paging message is sent by the network side of one of the cards of the terminal, and the service priority corresponding to the paging message is higher than the service priority that the terminal is executing or will execute on other cards;

[0079] In this embodiment, the terminal can be a multi-SIM terminal. Condition D1) can also be interpreted as: the service priority corresponding to the paging message received by the terminal is higher than the service priority being executed or about to be executed by other terminals, wherein the other terminals and the terminal refer to multiple terminals corresponding to multiple cards of a multi-SIM terminal. Alternatively, the service priority corresponding to the paging message is higher than the service priority being executed or about to be executed by other terminals, wherein the other terminals and the terminal are related to or share the same user equipment.

[0080] In this embodiment, the service priority corresponding to the paging message and the service priority of the terminal in other cards being executed or to be executed can be implemented by the terminal, agreed upon by a protocol, or configured by the network side. The service priority corresponding to the paging message can be the service type indicated by the paging reason value carried in the paging message.

[0081] D2) Before the terminal hears the paging message, it has sent a departure indication message to the network side. The departure indication message is used to indicate that the terminal cannot send or receive data on the network side.

[0082] The departure indication information includes: departure message, departure request, departure notification, negotiated departure, handover notification, or handover request, etc. These are all used to indicate that the terminal cannot send or receive data on the network side, or to request the network side to release the terminal, or to indicate that the terminal cannot listen to and / or respond to paging, or to indicate that the terminal is busy on other SIM cards, or to indicate that the terminal leaves the network side, or to indicate that the terminal switches to the network side corresponding to another SIM card.

[0083] In one implementation, the terminal has sent the departure indication information to the network side within a preset time period before detecting the paging message. The preset time period can be based on terminal implementation, network configuration, or protocol agreement.

[0084] D3) The terminal had sent the busy indication to the network side before it heard the paging message;

[0085] In one implementation, the terminal has sent a busy indication to the network side within a preset time period before receiving the paging message. This preset time period can be implemented based on the terminal, network configuration, or protocol agreement.

[0086] The fifth condition includes at least one of the following:

[0087] E1) The anchor base station or the last-served base station is unable to receive or process the RRC layer busy indication or does not require the terminal to send the RRC layer busy indication;

[0088] In this embodiment of the application, if the terminal is a multi-card terminal, the anchor base station or the last-served base station is the anchor base station or the last-served base station of the card that received the paging message.

[0089] In this embodiment, the anchor base station or the last-served base station can inform the terminal via dedicated signaling or broadcast messages that, upon receiving a paging message from the network, if it is busy or unable to process the service that triggered the paging, it is not required to send the RRC layer busy indication information to the network. Alternatively, the anchor base station or the last-served base station can inform the terminal via dedicated signaling or broadcast messages that the network cannot receive and / or process the RRC layer busy indication information.

[0090] E2) The anchor base station or the last-served base station does not support sending paging reason values;

[0091] In this embodiment, the anchor base station or the last serving base station does not support sending paging reason values. This means that when the terminal receives a paging message from the anchor base station or the last serving base station, it cannot determine whether to send the busy indication based on the paging reason value. Therefore, the anchor base station or the last serving base station may not support receiving the busy indication. The terminal can also determine whether the anchor base station or the last serving base station supports sending paging reason values ​​based on protocol agreements or other information.

[0092] E3) The anchor base station or the last-served base station does not support functions or features related to multi-SIM terminals;

[0093] The sixth condition includes at least one of the following:

[0094] F1) The core network is unable to receive or process a NAS busy indication or request the terminal to send a NAS busy indication;

[0095] In this embodiment of the application, if the terminal is a multi-card terminal, the core network is the core network of the card that receives the paging message.

[0096] Optionally, the core network may include, but is not limited to, at least one of the following: core network equipment, core network nodes, core network functions, core network elements, Mobility Management Entity (MME), Access Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Serving Gateway (SGW), PDN Gateway (PDN Gateway), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Serving GPRS Support Node (SGSN), Gateway GPRS Support Node (GGSN), and Application Function.

[0097] F2) The core network does not support sending paging reason values;

[0098] The F3 core network does not support functions or features related to multi-card terminals.

[0099] In this embodiment of the application, optionally, before determining whether to send a busy indication to the network side, at least one of the following is included:

[0100] 1) Receive first indication information via broadcast message or dedicated signaling, the first indication information being used to indicate whether the anchor base station or the last-served base station can receive or process the RRC layer busy indication or to request the terminal to send the RRC layer busy indication;

[0101] Optionally, the dedicated signaling is an RRC release message, an RRC connection release message, or an RRC connection reconfiguration message.

[0102] In some other embodiments of this application, optionally, whether the anchor base station or the last-served base station can receive or process the RRC layer busy indication can also be implicitly indicated in other ways.

[0103] 2) Receive second indication information via broadcast message or dedicated signaling, the second indication information being used to indicate whether the core network can receive or process the NAS busy indication or to request the terminal to send the NAS busy indication;

[0104] Optionally, the dedicated signaling may be an RRC release message, an RRC connection release message, an RRC connection reconfiguration message, or a NAS message.

[0105] In some other embodiments of this application, optionally, whether the core network can receive or process NAS busy indications can also be implicitly indicated in other ways.

[0106] 3) Receive third indication information via broadcast message or dedicated signaling, the third indication information being used to indicate whether the anchor base station or the last-served base station supports sending a paging reason value;

[0107] 4) Receive fourth indication information via broadcast message or dedicated signaling, the fourth indication information being used to indicate whether the core network supports sending paging reason values;

[0108] 5) Receive the fifth indication information via broadcast message or dedicated signaling, the fifth indication information being used to indicate whether the anchor base station or the last-served base station supports functions or features related to multi-SIM terminals;

[0109] 6) Receive the sixth indication information via broadcast message or dedicated signaling, the sixth indication information being used to indicate whether the core network supports functions or features related to multi-card terminals;

[0110] 7) Send a seventh indication message to the network side, the seventh indication message being used to indicate whether the terminal supports sending the busy indication.

[0111] In some embodiments of this application, the terminal sends a seventh indication message to the network side, indicating whether the terminal supports sending an RRC layer busy indication. When the network side receives the seventh indication message, if it releases the terminal again, if the terminal supports sending an RRC layer busy indication, the network side can release the terminal to the RRC inactive state; if the terminal does not support sending an RRC layer busy indication, the network side can release the terminal to the RRC idle state.

[0112] In some embodiments, optionally, if at least one of the first, second, and third conditions is met, it is determined to send the busy indication to the network side, including at least one of the following:

[0113] 1) If the second condition and the third condition are satisfied, or if the first condition, the second condition and the third condition are satisfied, determine to send the RRC layer busy indication or send the busy indication according to the RRC status when the terminal receives the paging message;

[0114] Further optionally, sending the busy indication based on the RRC status when the terminal receives the paging message includes:

[0115] If the terminal is in the RRC inactive state, send the RRC layer busy indication; or

[0116] If the terminal is in RRC idle state, send the NAS busy indication.

[0117] 2) If the third condition is not met and the second condition is met, or if the third condition is not met and the first and second conditions are met, determine that the RRC layer busy indication should be sent;

[0118] Further optionally, if the third condition is not met and the second condition is met, or if the third condition is not met and the first and second conditions are met, the terminal sends the RRC layer busy indication if it is in the RRC inactive state, or does not send the RRC layer busy indication if it is in the RRC idle state.

[0119] 3) If the second condition is not met and the third condition is met, or if the second condition is not met and the first condition and the third condition are met, determine that the NAS busy indication is sent;

[0120] In this embodiment of the application, optionally, determining whether to send a busy indication to the network side includes at least one of the following:

[0121] 1) If the second condition is not met and the third condition is met, or if the second condition is not met and the first condition and the third condition are met, it is determined that the busy indication will not be sent;

[0122] The statement that "do not send busy indications" includes not sending RRC layer busy indications and NAS busy indications.

[0123] 2) If the second condition is not met and the third condition is not met, it is determined that the busy indication will not be sent.

[0124] The statement that "do not send busy indications" includes not sending RRC layer busy indications and NAS busy indications.

[0125] In this embodiment of the application, optionally, sending the NAS busy indication when the second condition is not met and the third condition is met, or when the second condition is not met and the first condition and the third condition are met, further includes: the RRC layer reporting the busy indication or the paging reason value in the paging message to the upper layer.

[0126] In this embodiment of the application, optionally, after the RRC layer reports the busy indication or the paging reason value in the paging message to the upper layer, the terminal enters the RRC idle state.

[0127] In this embodiment of the application, optionally, after the terminal enters the RRC idle state, it further includes:

[0128] Set the release reason value.

[0129] Optionally, the release reason value includes at least one of the following: RRC connection failure, RRC connection recovery failure, busy indication failure, and a first reason value. The first reason value is another reason value besides RRC connection failure, RRC connection recovery failure, and busy indication failure.

[0130] In this embodiment of the application, optionally, the busy indication is carried by one of the following messages: RRC connection recovery request message, RRC connection recovery complete message, RRC connection establishment request message, RRC connection establishment complete message, Security Mode Command (SMC) complete message, or NAS message.

[0131] Further optionally, if the terminal is in RRC idle state when it receives the paging message, the busy indication is carried by one of the following messages: RRC connection establishment request message, RRC connection establishment complete message, Security Mode Command (SMC) complete message, and NAS message.

[0132] If the terminal is in an RRC inactive state when it receives a paging message, the busy indication is carried by one of the following messages: RRC connection restoration request message, RRC connection restoration complete message, Security Mode Command (SMC) complete message, and NAS message.

[0133] In this embodiment of the application, optionally, the method for transmitting the busy indication may further include: sending release indication information to the network side, the release indication information being used to instruct the network side to release the terminal.

[0134] Further optionally, the busy indication information is used to instruct the network side to release the terminal to a first RRC state, the first RRC state being an RRC idle state or an RRC inactive state.

[0135] Optionally, the release indication information may be carried by one of the following messages: RRC connection recovery request message, RRC connection recovery complete message, RRC connection establishment request message, RRC connection establishment complete message, Security Mode Command (SMC) complete message, and NAS message.

[0136] In this embodiment of the application, the release indication information can be sent simultaneously with the busy indication. For example, if the terminal is in an RRC inactive state when it receives a paging message, the terminal sends a NAS busy indication through an RRC connection recovery completion message, and carries the release indication information in the RRC connection recovery completion message.

[0137] In this embodiment of the application, optionally, the method for transmitting the busy indication may further include: indicating a second timer duration to the network side, the second timer duration being used to indicate the duration during which the terminal is busy or unable to receive paging messages.

[0138] Optionally, the duration of the second timer is carried by one of the following messages: RRC connection recovery request message, RRC connection recovery complete message, RRC connection establishment request message, RRC connection establishment complete message, safe mode command SMC complete message, and NAS message.

[0139] In this embodiment of the application, the duration of the second timer can be sent simultaneously with the busy indication. Alternatively, the second timer can be sent simultaneously with the busy indication and the release indication information.

[0140] The duration of the second timer can also be a value agreed upon in the protocol.

[0141] In this embodiment of the application, optionally, after sending a busy indication to the network side, at least one of the following is also included:

[0142] If no RRC release message is received, the terminal enters the RRC idle state;

[0143] If the T319 timer times out, the terminal enters the RRC idle state; a first timer is started, which is used to indicate the waiting time for the terminal to receive the RRC release message.

[0144] Optionally, the first timer is a newly defined timer, and its duration may differ from that of the T319 timer. The value of the first timer may also be agreed upon by the protocol.

[0145] In this embodiment of the application, optionally, after starting the first timer, the following steps are also included:

[0146] If an RRC release message is received, stop the first timer; or

[0147] If the first timer times out, the terminal is released to the first RRC state, which is either an RRC idle state or an RRC inactive state.

[0148] Optionally, if the terminal sends a release instruction to the network side, the first RRC state can be the first RRC state indicated in the release instruction or the first RRC state agreed upon in the protocol.

[0149] In this embodiment of the application, optionally, the method for transmitting the busy indication further includes: sending the first timer duration and / or the first RRC status to the network side when sending the busy indication or before sending the busy indication.

[0150] Optionally, sending the busy indication to the network side includes: if a random access channel failure occurs when sending the busy indication to the network side, then stopping the sending of the busy indication.

[0151] Please refer to Figure 3 This application also provides a method for transmitting a busy indication, executed by a network-side device, the method comprising:

[0152] Step 31: Receive the busy indication sent by the terminal;

[0153] Step 32: Perform the corresponding operation according to the busy indication.

[0154] In this embodiment, the network side receives the busy indication sent by the terminal and performs corresponding processing to avoid the waste of network resources caused by continuing to page the terminal.

[0155] In this embodiment of the application, optionally, the busy indicator includes at least one of the following: RRC layer busy indicator and NAS busy indicator.

[0156] In this embodiment of the application, optionally, the busy indicator includes an RRC layer busy indicator; performing the corresponding operation according to the busy indicator includes:

[0157] Perform a first operation based on the busy indication, the first operation including at least one of the following:

[0158] Stop or cease initiating paging related to the terminal;

[0159] Discard, block, or cache incoming downlink data or signaling.

[0160] In this embodiment of the application, optionally, performing the first operation according to the busy indication includes:

[0161] Upon receiving the RRC layer busy indication, a second timer is started;

[0162] The first operation is performed during the operation of the second timer;

[0163] If an uplink message is received from the terminal, stop the second timer;

[0164] If the second timer times out, stop the first operation.

[0165] Optionally, the uplink message may include an RRC connection establishment request, an RRC connection recovery request message, a TAU, or an RNAU.

[0166] In this embodiment of the application, optionally, the busy indicator includes a NAS busy indicator; performing the corresponding operation according to the busy indicator includes:

[0167] Perform a second operation based on the busy indication, the second operation including at least one of the following:

[0168] Send the busy indication to the anchor base station or the last base station served by the terminal;

[0169] Stop sending downlink data or signaling to the anchor base station or the last-served base station of the terminal;

[0170] Stop or cease initiating paging related to the terminal;

[0171] Discard, block, or cache incoming downlink data or signaling.

[0172] Optionally, performing a second operation based on the busy indication includes:

[0173] Upon receiving the NAS busy indication, a second timer is started;

[0174] The second operation is performed during the operation of the second timer;

[0175] If an uplink message is received from the terminal, stop the second timer;

[0176] If the second timer times out, stop the second operation.

[0177] Optionally, the method for transmitting the busy indication further includes: receiving release indication information sent by the terminal, the release indication information being used to instruct the network side to release the terminal.

[0178] Optionally, after receiving the release instruction information sent by the terminal, the method further includes:

[0179] According to the release instruction information, send an RRC release message to the terminal; or release the terminal to the RRC idle state or RRC inactive state indicated in the release instruction information.

[0180] The method for transmitting the busy indication described above will be illustrated below with specific embodiments.

[0181] Embodiment 1 of the present invention: A multi-card terminal sends an RRC busy indication to the network where the inactive RRC card 2 is located.

[0182] Step 1: The terminal is in RRC inactive state on SIM 2 and is listening for paging on SIM 2.

[0183] Step 2: The terminal detects the paging message sent by the network of SIM 2 on SIM 2 and determines that it should send an RRC layer busy indication to the network of SIM 2.

[0184] Further, if the first condition and / or the second condition are met, it is determined that an RRC layer busy indication will be sent to the network of card 2. The first condition includes at least one of the following:

[0185] The first condition includes at least one of the following:

[0186] A1) The paging message is sent by the network side of one of the cards of the terminal, and the service priority corresponding to the paging message is lower than or equal to the service priority that the terminal is executing or will execute on other cards;

[0187] For example, based on the paging reason value carried in the paging message received from SIM 2, the terminal knows the service type that SIM 2 needs to perform, and the terminal also knows the service type that SIM 1 is currently performing. The terminal compares the priorities of the service types of the two cards to determine whether to send a busy indication. The service priorities of the two cards can be implemented by the terminal, agreed upon by a protocol, or configured by the network.

[0188] For example, if SIM 2 is for data services and SIM 1 is for voice services, then the service priority of SIM 2 is lower than that of SIM 1.

[0189] A2) The paging message is sent by the network side of one of the cards in the terminal, and the other cards in the terminal are executing or will execute preset services;

[0190] For example, if the UE is performing a voice service on SIM 1, in order not to interrupt the service being performed on SIM 1, the terminal sends a busy indication to the network where SIM 2 is located.

[0191] A3) Before the terminal hears the paging message, it has not sent any departure indication information to the network side. The departure indication information is used to indicate that the terminal cannot send or receive data on the network side.

[0192] A4) The terminal did not send the busy indication to the network side before it heard the paging message;

[0193] The second condition includes at least one of the following:

[0194] B1) The anchor base station or the last serving base station can receive or process the RRC layer busy indication or request the terminal to send the RRC layer busy indication;

[0195] In this embodiment of the application, the anchor base station or the last-served base station is the anchor base station or the last-served base station of card 2.

[0196] Optionally, before determining whether to send a busy indication to the network side, the method further includes: receiving first indication information via broadcast message or dedicated signaling, wherein the first indication information is used to indicate whether the anchor base station or the last-served base station can receive or process the RRC layer busy indication or to request the terminal to send the RRC layer busy indication;

[0197] Optionally, the dedicated signaling is an RRC release message or an RRC reconfiguration message.

[0198] In some other embodiments of this application, optionally, whether the anchor base station or the last-served base station can receive or process the RRC layer busy indication can also be implicitly indicated in other ways.

[0199] B2) The anchor base station or the last-served base station supports sending paging reason values;

[0200] B3) The anchor base station or the last-served base station supports functions or features related to multi-SIM terminals;

[0201] Step 3: The terminal uses card 2 to send an RRC connection restoration request message, which carries an RRC layer busy indication;

[0202] Step 4: The terminal receives the RRC connection restoration message;

[0203] Step 5: If the terminal receives an RRC Release message, it enters the corresponding RRC state according to the message's instructions (e.g., remaining in the RRC inactive state or entering the RRC idle state). If the terminal does not receive an RRC Release message, it enters the idle state. Further, if the terminal does not receive an RRC Release message within the duration of a predefined timer (e.g., a T319 timer, or a new timer with a shorter duration), it enters the idle state after the timer expires. Optionally, the terminal can set the release reason value to one of the following: RRC Resume Failure, Busy Indication Failure, or Other.

[0204] Embodiment 2 of the present invention: The terminal sends a NAS busy indication to the network where card 2 is located.

[0205] Step 1: The terminal is in the RRC idle state on SIM 2 and is listening for paging locations on SIM 2.

[0206] Step 2: The terminal detects a paging message (CN paging) sent by the network of SIM 2 on SIM 2 and determines that it is sending a NAS busy indication to the network of SIM 2.

[0207] Furthermore, if the first and / or third conditions are met, a NAS busy indication is sent to the network of card 2. If the conditions are not met, the UE does not send a busy indication.

[0208] The first condition can be found in Example 1.

[0209] The third condition includes at least one of the following:

[0210] C1) The core network is able to receive or process NAS busy indications or request the terminal to send NAS busy indications;

[0211] In this embodiment of the application, the core network is the core network of card 2.

[0212] In some other embodiments of this application, optionally, whether the core network is able to receive or process NAS busy indications can also be implicitly indicated in other ways.

[0213] In this embodiment of the application, optionally, before determining whether to send a busy indication to the network side, the method further includes: receiving first indication information through a broadcast message or dedicated signaling, wherein the first indication information is used to indicate whether the anchor base station or the last-served base station can receive or process the RRC layer busy indication or to request the terminal to send the RRC layer busy indication.

[0214] Optionally, the dedicated signaling may be an RRC release message, an RRC reconfiguration message, or a NAS message.

[0215] Optionally, whether the anchor base station or the last-served base station can receive or process the RRC layer busy indication can also be implicitly indicated in other ways.

[0216] C2) The core network supports sending paging reason values;

[0217] C3) The core network supports functions or features related to multi-card terminals.

[0218] Step 3: The terminal sends an RRC connection establishment request message;

[0219] Step 4: The terminal receives the RRC connection establishment message;

[0220] Step 5: The terminal sends an RRC connection establishment complete message (i.e., msg5), which carries a NAS busy indication.

[0221] Optionally, it also carries a release indication information to instruct the network side to release the terminal. Further optionally, it indicates that the RRC released by the network side is in an RRC idle state or an RRC inactive state.

[0222] Step 6: If the terminal receives an RRC release message, it enters the corresponding RRC state according to the instructions in the RRC release message (e.g., remaining in the RRC inactive state or entering the RRC idle state). If the terminal does not receive an RRC release message, the UE performs a local release. The released RRC state can be determined based on the RRC state reported by the terminal in the release instruction message in Step 5, or released to the corresponding RRC state according to the protocol (e.g., released to the RRC idle state according to the protocol). Optionally, if no RRC release message is received during the operation of a predefined timer, the UE performs a local release.

[0223] Optionally, the release reason value can be set to one of RRC connection failure, busy indication failure, or other.

[0224] The scheme in this embodiment can also be used in the RRC inactive state, where the UE sends a busy indication. The solution is simply to replace the RRC connection establishment request, RRC connection establishment, and RRC connection establishment completion messages in the above scheme with the RRC connection recovery request, RRC connection recovery, and RRC connection recovery completion messages.

[0225] Embodiment 3 of the present invention: Terminal behavior when the second condition is not met

[0226] Step 1: If the second condition in step 2 of embodiment 1 is not met, the terminal may perform one of the following operations:

[0227] a) The terminal does not send an RRC layer busy indication. The process ends.

[0228] b) The terminal decides to send a NAS busy indication.

[0229] Furthermore, if the second condition is not met because the terminal received a paging reason value, but the anchor base station or the last serving base station cannot receive or process the RRC layer busy indication, then the terminal sends a NAS busy indication.

[0230] Further optionally, it may be sent when the core network is able to receive or process a NAS busy indication, or when the third condition in Embodiment 2 is met.

[0231] At the same time, the terminal's RRC layer will report the busy indication or paging cause value to the upper layer.

[0232] Step 2: The upper layer of the terminal generates a NAS message, which carries a NAS busy indication. This NAS message is sent to the RRC layer, and at the same time, the RRC layer is requested to initiate an RRC connection recovery request. Optionally, the NAS layer indicates an access category to the RRC layer, for example, Access category = 0.

[0233] Step 3: After receiving the NAS message sent by the upper layer, the RRC layer of the UE executes the Unified Access Control (UAC) (if the upper layer does not provide an access type, the RRC layer can set the access type number for this access attempt, such as 0), and sends an RRC connection recovery request to the network side of SIM 2.

[0234] Step 4: The terminal receives the RRC connection restoration message;

[0235] Step 5: The terminal sends an RRC connection restoration complete message, which carries the NAS busy indication from Step 3. Optionally, it also carries release indication information to instruct the network side to release the terminal. Further optionally, the RRC state released by the network side is either RRC idle or RRC inactive.

[0236] Step 6: Upon receiving the RRC release message, the terminal enters the corresponding RRC state (idle or inactive state) according to network instructions. If the terminal does not receive the RRC release message, it releases the RRC locally. The released RRC state can be determined based on the RRC state reported by the terminal in Step 5 or according to the protocol (e.g., the protocol specifies releasing to the RRC idle state). Optionally, if no RRC release message is received during the execution of a predefined timer, the terminal releases the RRC locally. Optionally, the release reason value can be set to one of RRC connection failure, busy indication failure, or other.

[0237] Step 7: The base station sends a NAS busy indication to the core network;

[0238] Step 8: After the core network receives the NAS busy indication, perform one of the following operations:

[0239] a) Send the above busy indication to the anchor base station or the last-served base station of Card 2.

[0240] b) Stop sending downlink data / signaling to the anchor base station or the last-served base station; optionally, stop for a period of time.

[0241] Embodiment 4 of the present invention: After the RRC layer sends a busy indication to the upper layer, it can enter the RRC idle state.

[0242] Step 1: In Step 1 of Embodiment 3, after the terminal's RRC layer reports the busy indication or paging reason value to the upper layer, it enters the RRC idle state. Optionally, the release reason value can be set to one of RRC recovery failure, busy indication failure, or other.

[0243] Step 2: The upper layer of the terminal generates a NAS message, which carries a NAS busy indication. This NAS message is sent to the RRC layer, simultaneously requesting the RRC layer to initiate RRC connection recovery. Optionally, the NAS layer indicates an access category to the RRC layer, for example, Access category = 0.

[0244] Step 3: After receiving the NAS message sent by the upper layer, the terminal's RRC layer executes UAC and sends an RRC connection establishment request message to the anchor base station of card 2 or the last base station it served.

[0245] Step 4: The terminal receives the RRC connection establishment message;

[0246] Step 5: The terminal sends an RRC connection establishment complete message, which carries the NAS busy indication from Step 3. Optionally, the RRC connection establishment complete message also carries release indication information, used to instruct the serving anchor base station or the last serving base station to release the terminal. Optionally, the RRC state released by the anchor base station or the last serving base station is indicated as RRC idle state or RRC inactive state.

[0247] Step 6: Upon receiving the RRC release message, the terminal enters the corresponding RRC state (RRC idle state or RRC inactive state) according to network instructions. If the terminal does not receive the RRC release message, it releases the RRC locally. The released RRC state can be determined based on the RRC state reported by the terminal in Step 5 or according to the protocol (e.g., the protocol specifies releasing to the RRC idle state). Optionally, if no RRC release message is received during the execution of a predefined timer, the terminal releases the RRC locally. Optionally, the release reason value can be set to one of RRC connection failure, busy indication failure, or other.

[0248] Step 7: The anchor base station of Card 2 or the last-served base station sends a NAS busy indication to the core network;

[0249] Step 8: The core network received a busy message from the NAS layer and will not initiate core network paging for the terminal for a period of time thereafter.

[0250] In the above embodiments, if a Random Access Channel (RACH) failure occurs when the terminal sends an RRC layer or NAS busy indication, the terminal stops sending the busy indication.

[0251] It should be noted that the busy indication transmission method provided in this application embodiment can be executed by a busy indication transmission device, or by a control module within the busy indication transmission device for executing the busy indication transmission method. This application embodiment uses the busy indication transmission device executing the busy indication transmission method as an example to illustrate the busy indication transmission device provided in this application embodiment.

[0252] Please refer to Figure 4 This application embodiment also provides a busy indication transmission device 40, including:

[0253] The judgment module 41 is used to determine whether to send a busy indication to the network side after listening to the paging message;

[0254] The first sending module 42 is used to send a busy indication to the network side if it is determined that a busy indication should be sent to the network side.

[0255] In this embodiment, upon receiving a paging message, if the conditions for sending a busy indication are met, a busy indication can be sent to the network side, enabling the network side to perform corresponding processing and avoiding the waste of network resources caused by continuing to paging the terminal. If the conditions are not met, a busy indication can be refrained from being sent, thereby minimizing the impact on currently running services.

[0256] Optionally, the busy indicator includes at least one of the following: RRC layer busy indicator and NAS busy indicator.

[0257] Optionally, the judgment module 41 is configured to determine to send the busy indication to the network side if at least one of the first condition, the second condition, and the third condition is met, wherein:

[0258] The first condition includes at least one of the following:

[0259] The paging message is sent by the network side of one of the cards of the terminal, and the service priority corresponding to the paging message is lower than or equal to the service priority that the terminal is executing or will execute on other cards;

[0260] The paging message is sent by the network side of one of the cards in the terminal, while the other cards in the terminal are executing or will execute preset services.

[0261] Before the terminal hears the paging message, it has not sent any departure indication information to the network side. The departure indication information is used to indicate that the terminal cannot send or receive data on the network side.

[0262] The terminal did not send the busy indication to the network side before it heard the paging message;

[0263] The second condition includes at least one of the following:

[0264] The anchor base station or the last-served base station can receive or process the RRC layer busy indication or request the terminal to send the RRC layer busy indication.

[0265] Anchor base stations or last-served base stations support sending paging reason values;

[0266] The anchor base station or the last-served base station supports functions or features related to multi-SIM terminals;

[0267] The third condition includes at least one of the following:

[0268] The core network can receive or process NAS busy indications or request the terminal to send NAS busy indications;

[0269] The core network supports sending paging reason values;

[0270] The core network supports functions or features related to multi-card terminals.

[0271] Optionally, the method for transmitting the busy indication further includes at least one of the following:

[0272] The first receiving module is used to receive first indication information through broadcast messages or dedicated signaling. The first indication information is used to indicate whether the anchor base station or the last-served base station can receive or process the RRC layer busy indication or to request the terminal to send the RRC layer busy indication.

[0273] The second receiving module is used to receive second indication information via broadcast message or dedicated signaling. The second indication information is used to indicate whether the core network can receive or process the NAS busy indication or to request the terminal to send the NAS busy indication.

[0274] The third receiving module is used to receive third indication information via broadcast message or dedicated signaling. The third indication information is used to indicate whether the anchor base station or the last-served base station supports sending a paging reason value.

[0275] The fourth receiving module is used to receive fourth indication information via broadcast messages or dedicated signaling. The fourth indication information is used to indicate whether the core network supports sending paging reason values.

[0276] The fifth receiving module is used to receive the fifth indication information through broadcast messages or dedicated signaling. The fifth indication information is used to indicate whether the anchor base station or the last-served base station supports functions or features related to multi-card terminals.

[0277] The sixth receiving module is used to receive the sixth indication information via broadcast message or dedicated signaling. The sixth indication information is used to indicate whether the core network supports functions or features related to multi-card terminals.

[0278] The second sending module is used to send a seventh indication information to the network side, the seventh indication information being used to indicate whether the terminal supports sending the busy indication.

[0279] Optionally, if at least one of the first, second, and third conditions is met, it is determined that the busy indication will be sent to the network side, including at least one of the following:

[0280] If the second condition and the third condition are satisfied, or if the first condition, the second condition and the third condition are satisfied, it is determined to send the RRC layer busy indication or send the busy indication according to the RRC status when the terminal receives the paging message;

[0281] If the third condition is not met and the second condition is met, or if the third condition is not met and the first and second conditions are met, it is determined that the RRC layer busy indication should be sent.

[0282] If the second condition is not met and the third condition is met, or if the second condition is not met and the first and third conditions are met, it is determined that the NAS busy indication should be sent.

[0283] Optionally, the determination module 41 is further configured to perform at least one of the following:

[0284] If the second condition is not met and the third condition is met, or if the second condition is not met and the first condition and the third condition are met, it is determined that the busy indication will not be sent.

[0285] If neither the second condition nor the third condition is met, it is determined that the busy indication will not be sent.

[0286] Optionally, sending the busy indication based on the RRC status when the terminal receives the paging message includes:

[0287] If the terminal is in an RRC inactive state, it sends the RRC layer busy indication; or

[0288] If the terminal is in RRC idle state, send the NAS busy indication.

[0289] Optionally, the busy indication is carried by one of the following messages: RRC connection recovery request message, RRC connection recovery complete message, RRC connection establishment request message, RRC connection establishment complete message, Security Mode Command (SMC) complete message, or NAS message.

[0290] Optionally, the busy indication transmission device further includes at least one of the following:

[0291] The third sending module is used to send release indication information to the network side, the release indication information being used to instruct the network side to release the terminal;

[0292] The fourth sending module is used to indicate the duration of the second timer to the network side. The duration of the second timer is used to indicate the duration during which the terminal is busy or unable to receive paging messages.

[0293] Optionally, the release indication information and / or the duration of the second timer may be carried by one of the following messages: RRC connection restoration request message, RRC connection restoration complete message, RRC connection establishment request message, RRC connection establishment complete message, Security Mode Command (SMC) complete message, or NAS message.

[0294] Optionally, the busy indication transmission device further includes at least one of the following:

[0295] The first processing module is used to send a busy indication to the network side and, if no RRC release message is received, the terminal enters the RRC idle state.

[0296] The second processing module is used to cause the terminal to enter the RRC idle state if the T319 timer times out.

[0297] The third processing module is used to start the first timer, which is used to indicate the waiting time for the terminal to receive the RRC release message.

[0298] Optionally, the busy indication transmission device further includes at least one of the following:

[0299] The fourth processing module is used to stop the first timer if an RRC release message is received;

[0300] The fifth processing module is used to release the terminal to the first RRC state if the first timer times out, wherein the first RRC state is either an RRC idle state or an RRC inactive state.

[0301] Optionally, the busy indication transmission device further includes:

[0302] The fifth sending module is used to send the first timer duration and / or the first RRC status to the network side when sending the busy indication or before sending the busy indication.

[0303] Optionally, sending the NAS busy indication when the second condition is not met and the third condition is met, or when the second condition is not met and the first condition and the third condition are met, further includes:

[0304] The RRC layer reports the busy indication or the paging reason value in the paging message to the upper layer.

[0305] Optionally, the busy indication transmission device further includes:

[0306] The sixth processing module is used to enable the terminal to enter the RRC idle state after the RRC layer reports the busy indication or the paging reason value in the paging message to the upper layer.

[0307] Optionally, the busy indication transmission device further includes:

[0308] The seventh processing module is used to set the release reason value after the terminal enters the RRC idle state.

[0309] Optionally, the release reason value includes at least one of the following: RRC connection failure, RRC connection recovery failure, busy indication failure, and a first reason value.

[0310] Optionally, the busy indication transmission device further includes:

[0311] The eighth processing module is used to stop sending the busy indication if a random access channel failure occurs when sending a busy indication to the network side.

[0312] The busy indication transmission device in this application embodiment can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminal 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not impose specific limitations.

[0313] The busy indicator transmission device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit it.

[0314] The busy indication transmission device provided in this application embodiment can achieve Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0315] It should be noted that the busy indication transmission method provided in this application embodiment can be executed by a busy indication transmission device, or by a control module within the busy indication transmission device for executing the busy indication transmission method. This application embodiment uses the busy indication transmission device executing the busy indication transmission method as an example to illustrate the busy indication transmission device provided in this application embodiment.

[0316] Please refer to Figure 5 This application embodiment also provides a busy indication transmission device 50, including:

[0317] The receiving module 51 is used to receive a busy indication sent by the terminal;

[0318] Processing module 52 is used to perform corresponding operations according to the busy indication.

[0319] Optionally, the busy indicator includes at least one of the following: RRC layer busy indicator and NAS busy indicator.

[0320] Optionally, the busy indication includes an RRC layer busy indication; the processing module 52 is configured to perform a first operation based on the busy indication, the first operation including at least one of the following:

[0321] Stop or cease initiating paging related to the terminal;

[0322] Discard, block, or cache incoming downlink data or signaling.

[0323] Optionally, performing the first operation based on the busy indication includes:

[0324] Upon receiving the RRC layer busy indication, a second timer is started;

[0325] The first operation is performed during the operation of the second timer;

[0326] If an uplink message is received from the terminal, stop the second timer;

[0327] If the second timer times out, stop the first operation.

[0328] Optionally, the busy indication includes a NAS busy indication; the processing module 52 is configured to perform a second operation based on the busy indication, the second operation including at least one of the following:

[0329] Send the busy indication to the anchor base station or the last base station served by the terminal;

[0330] Stop sending downlink data or signaling to the anchor base station or the last-served base station of the terminal;

[0331] Stop or cease initiating paging related to the terminal;

[0332] Discard, block, or cache incoming downlink data or signaling.

[0333] Optionally, performing a second operation based on the busy indication includes:

[0334] Upon receiving the NAS busy indication, a second timer is started;

[0335] The second operation is performed during the operation of the second timer;

[0336] If an uplink message is received from the terminal, stop the second timer;

[0337] If the second timer times out, stop the second operation.

[0338] Optionally, the busy indication transmission device 50 further includes:

[0339] The second receiving module is used to receive release instruction information sent by the terminal, the release instruction information being used to instruct the network side to release the terminal.

[0340] Optionally, the busy indication transmission device 50 further includes at least one of the following:

[0341] The sending module is used to send an RRC release message to the terminal according to the release indication information;

[0342] The release module is used to release the terminal to the RRC idle state or RRC inactive state indicated in the release instruction information.

[0343] The busy indication transmission device provided in this application embodiment can achieve Figure 3 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0344] like Figure 6As shown, this application embodiment also provides a communication device 60, including a processor 61, a memory 62, and a program or instructions stored in the memory 62 and executable on the processor 61. For example, when the communication device 60 is a terminal, the program or instructions executed by the processor 61 implement the various processes of the above-described busy indication transmission method embodiment, and achieve the same technical effect. When the communication device 60 is a network-side device, the program or instructions executed by the processor 61 implement the various processes of the above-described busy indication transmission method embodiment, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0345] Figure 7 This is a schematic diagram of the hardware structure of a terminal according to an embodiment of this application. The terminal 70 includes, but is not limited to, components such as: a radio frequency unit 71, a network module 72, an audio output unit 73, an input unit 74, a sensor 75, a display unit 76, a user input unit 77, an interface unit 78, a memory 79, and a processor 710.

[0346] Those skilled in the art will understand that the terminal 70 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 710 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 7 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0347] It should be understood that, in this embodiment, the input unit 74 may include a graphics processing unit (GPU) 741 and a microphone 742. The GPU 741 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 76 may include a display panel 761, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 77 includes a touch panel 771 and other input devices 772. The touch panel 771 is also called a touch screen. The touch panel 771 may include a touch detection device and a touch controller. Other input devices 772 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0348] In this embodiment, the radio frequency unit 71 receives downlink data from the network-side device and processes it for the processor 710; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 71 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0349] The memory 79 can be used to store software programs or instructions and various data. The memory 79 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 79 may include high-speed random access memory and non-volatile memory, which may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0350] Processor 710 may include one or more processing units; optionally, processor 710 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 710.

[0351] The processor 710 is used to listen to the paging message and determine whether to send a busy indication to the network side.

[0352] Radio frequency unit 71 is used to send the busy indication to the network side if it is determined that a busy indication should be sent to the network side.

[0353] Optionally, the busy indicator includes at least one of the following: RRC layer busy indicator and NAS busy indicator.

[0354] Optionally, the processor 710 is configured to, upon receiving a paging message, determine whether to send a busy indication to the network side, including:

[0355] If at least one of the first, second, and third conditions is met, it is determined that the busy indication will be sent to the network side, wherein:

[0356] The first condition includes at least one of the following:

[0357] The paging message is sent by the network side of one of the cards of the terminal, and the service priority corresponding to the paging message is lower than or equal to the service priority that the terminal is executing or will execute on other cards;

[0358] The paging message is sent by the network side of one of the cards in the terminal, while the other cards in the terminal are executing or will execute preset services.

[0359] Before the terminal hears the paging message, it has not sent any departure indication information to the network side. The departure indication information is used to indicate that the terminal cannot send or receive data on the network side.

[0360] The terminal did not send the busy indication to the network side before it heard the paging message;

[0361] The second condition includes at least one of the following:

[0362] The anchor base station or the last-served base station can receive or process the RRC layer busy indication or request the terminal to send the RRC layer busy indication.

[0363] Anchor base stations or last-served base stations support sending paging reason values;

[0364] The anchor base station or the last-served base station supports functions or features related to multi-SIM terminals;

[0365] The third condition includes at least one of the following:

[0366] The core network can receive or process NAS busy indications or request the terminal to send NAS busy indications;

[0367] The core network supports sending paging reason values;

[0368] The core network supports functions or features related to multi-card terminals.

[0369] Optionally, the radio frequency unit 71 is further configured to perform at least one of the following:

[0370] The first indication information is received by broadcasting a message or using dedicated signaling. The first indication information is used to indicate whether the anchor base station or the last-served base station can receive or process the RRC layer busy indication or to request the terminal to send the RRC layer busy indication.

[0371] The second indication information is received via broadcast message or dedicated signaling. The second indication information is used to indicate whether the core network can receive or process the NAS busy indication or to request the terminal to send the NAS busy indication.

[0372] The third indication information is received via broadcast message or dedicated signaling, and the third indication information is used to indicate whether the anchor base station or the last-served base station supports sending a paging reason value.

[0373] The fourth indication information is received via broadcast message or dedicated signaling, and the fourth indication information is used to indicate whether the core network supports sending paging reason values.

[0374] The fifth indication information is received via broadcast message or dedicated signaling. The fifth indication information is used to indicate whether the anchor base station or the last-served base station supports functions or features related to multi-card terminals.

[0375] The sixth indication information is received via broadcast message or dedicated signaling. The sixth indication information is used to indicate whether the core network supports functions or features related to multi-card terminals.

[0376] A seventh indication message is sent to the network side, the seventh indication message being used to indicate whether the terminal supports sending the busy indication.

[0377] Optionally, the processor 710 is configured to determine to send the busy indication to the network side if at least one of the first, second, and third conditions is met, including at least one of the following:

[0378] If the second condition and the third condition are satisfied, or if the first condition, the second condition and the third condition are satisfied, it is determined to send the RRC layer busy indication or send the busy indication according to the RRC status when the terminal receives the paging message;

[0379] If the third condition is not met and the second condition is met, or if the third condition is not met and the first and second conditions are met, it is determined that the RRC layer busy indication should be sent.

[0380] If the second condition is not met and the third condition is met, or if the second condition is not met and the first and third conditions are met, it is determined that the NAS busy indication should be sent.

[0381] Optionally, the processor 710 is configured to determine whether to send a busy indication to the network side, including at least one of the following:

[0382] If the second condition is not met and the third condition is met, or if the second condition is not met and the first condition and the third condition are met, it is determined that the busy indication will not be sent.

[0383] If neither the second condition nor the third condition is met, it is determined that the busy indication will not be sent.

[0384] Optionally, the processor 710 is configured to send the busy indication based on the RRC status when the terminal receives the paging message, including:

[0385] If the terminal is in an RRC inactive state, it sends the RRC layer busy indication; or

[0386] If the terminal is in RRC idle state, send the NAS busy indication.

[0387] Optionally, the busy indication is carried by one of the following messages: RRC connection recovery request message, RRC connection recovery complete message, RRC connection establishment request message, RRC connection establishment complete message, Security Mode Command (SMC) complete message, or NAS message.

[0388] Optionally, the radio frequency unit 71 is further configured to perform at least one of the following:

[0389] Send a release instruction message to the network side, the release instruction message being used to instruct the network side to release the terminal;

[0390] The network side is instructed on the duration of a second timer, which indicates the duration during which the terminal is busy or unable to receive paging messages.

[0391] Optionally, the release indication information and / or the duration of the second timer may be carried by one of the following messages: RRC connection restoration request message, RRC connection restoration complete message, RRC connection establishment request message, RRC connection establishment complete message, Security Mode Command (SMC) complete message, or NAS message.

[0392] Optionally, the processor 710 is further configured to perform at least one of the following after sending a busy indication to the network side:

[0393] If no RRC release message is received, the terminal enters the RRC idle state;

[0394] If the T319 timer times out, the terminal enters the RRC idle state;

[0395] Start a first timer, which is used to indicate the waiting time for the terminal to receive the RRC release message.

[0396] Optionally, the processor 710 is also configured to perform:

[0397] If an RRC release message is received, stop the first timer; or

[0398] If the first timer times out, the terminal is released to the first RRC state, which is either an RRC idle state or an RRC inactive state.

[0399] Optionally, the radio frequency unit 71 is further configured to send the first timer duration and / or the first RRC status to the network side when sending the busy indication or before sending the busy indication.

[0400] Optionally, the processor 710 is further configured to determine to send the NAS busy indication when the second condition is not met and the third condition is met, or when the second condition is not met and the first condition and the third condition are met, further comprising:

[0401] The RRC layer reports the busy indication or the paging reason value in the paging message to the upper layer.

[0402] Optionally, the processor 710 is further configured to enter the RRC idle state after reporting the busy indication or the paging reason value in the paging message to the upper layer at the RRC layer.

[0403] Optionally, the processor 710 is also configured to set a release reason value after entering the RRC idle state.

[0404] Optionally, the release reason value includes at least one of the following: RRC connection failure, RRC connection recovery failure, busy indication failure, and a first reason value.

[0405] Optionally, the processor 710 is further configured to stop sending the busy indication if a random access channel failure occurs when sending a busy indication to the network side.

[0406] This application also provides a network-side device. For example... Figure 8 As shown, the network device 80 includes an antenna 81, a radio frequency (RF) device 82, and a baseband device 83. The antenna 81 is connected to the RF device 82. In the uplink direction, the RF device 82 receives information through the antenna 81 and sends the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes the information to be transmitted and sends it to the RF device 82. The RF device 82 processes the received information and then transmits it through the antenna 81.

[0407] The aforementioned frequency band processing device can be located in the baseband device 83. The method executed by the network-side device in the above embodiments can be implemented in the baseband device 83, which includes a processor 84 and a memory 85.

[0408] Baseband device 83 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 8As shown, one of the chips, for example, is a processor 84, which is connected to a memory 85 to call the program in the memory 85 and execute the network device operation shown in the above method embodiment.

[0409] The baseband device 83 may also include a network interface 86 for exchanging information with the radio frequency device 82, such as a common public radio interface (CPRI).

[0410] Specifically, the network-side device in this embodiment of the invention further includes: instructions or programs stored in memory 85 and executable on processor 84, wherein processor 84 calls the instructions or programs in memory 85 to execute. Figure 5 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0411] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described busy indication transmission method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0412] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described busy indication transmission method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0413] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0414] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run network-side device programs or instructions to implement the various processes of the above-described embodiment of the transmission method for busy indication executed by the terminal, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0415] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run network-side device programs or instructions to implement the various processes of the above-described embodiment of the transmission method for busy indication executed by the network side, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0416] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0417] This application also provides a program product, which is stored in a non-volatile storage medium. The program product is executed by at least one processor to implement the various processes of the above-described embodiment of the transmission method for the busy indication executed by the terminal, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0418] This application also provides a program product, which is stored in a non-volatile storage medium. The program product is executed by at least one processor to implement the various processes of the above-described embodiment of the transmission method for busy indication executed by the network side, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0419] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0420] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0421] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method of transmission of a busy indication, characterized by, The method is executed by a terminal, and comprises: after listening to a paging message sent by a first network side, judging whether to send a busy indication to the first network side; if it is judged to send the busy indication to the first network side, sending the busy indication to the first network side; the busy indication is used to indicate that the terminal does not accept paging or rejects paging; the busy indication is also used to indicate that the first network side releases the terminal to a first RRC state, and the first RRC state is an RRC idle state; the judging whether to send the busy indication to the first network side comprises: judging whether to send the busy indication to the first network side according to an RRC state when the paging message is received.

2. The method of claim 1, wherein, the busy indication comprises at least one of a radio resource control (RRC) layer busy indication and a non-access stratum (NAS) busy indication.

3. The method of claim 1, wherein, after listening to a paging message, judging whether to send a busy indication to the first network side, comprises: if at least one of a first condition, a second condition and a third condition is met, it is judged to send the busy indication to the first network side, wherein: the first condition comprises at least one of: the paging message is sent by the first network side of a card of the terminal, and a service priority corresponding to the paging message is lower than or equal to a service priority of a service being executed or to be executed by other cards of the terminal; the paging message is sent by the first network side of a card of the terminal, and a preset service is being executed or to be executed by other cards of the terminal; before listening to the paging message, the terminal has not sent a leaving indication information to the first network side, and the leaving indication information is used to indicate that the terminal cannot receive and transmit data on the first network side; before listening to the paging message, the terminal has not sent the busy indication to the first network side; the second condition comprises at least one of: an anchor base station or a last serving base station can receive or process an RRC layer busy indication or require the terminal to send the RRC layer busy indication; the anchor base station or the last serving base station supports sending a paging cause value; the anchor base station or the last serving base station supports a function or feature related to a multi-card terminal; the third condition comprises at least one of: a core network can receive or process an NAS busy indication or require the terminal to send the NAS busy indication; the core network supports sending a paging cause value; the core network supports a function or feature related to a multi-card terminal.

4. The method of claim 1, wherein, before the judging whether to send the busy indication to the first network side, at least one of the following is further included: first indication information is received through a broadcast message or dedicated signaling, and the first indication information is used to indicate whether an anchor base station or a last serving base station can receive or process an RRC layer busy indication or require the terminal to send the RRC layer busy indication; second indication information is received through a broadcast message or dedicated signaling, and the second indication information is used to indicate whether a core network can receive or process an NAS busy indication or require the terminal to send the NAS busy indication; receiving third indication information through broadcast message or dedicated signaling, the third indication information being used for indicating whether the anchor base station or the last serving base station supports sending paging cause value; receiving fourth indication information through broadcast message or dedicated signaling, the fourth indication information being used for indicating whether the core network supports sending paging cause value; receiving fifth indication information through broadcast message or dedicated signaling, the fifth indication information being used for indicating whether the anchor base station or the last serving base station supports multi-card terminal related function or feature; receiving sixth indication information through broadcast message or dedicated signaling, the sixth indication information being used for indicating whether the core network supports multi-card terminal related function or feature; sending seventh indication information to the first network side, the seventh indication information being used for indicating whether the terminal supports sending the busy indication.

5. The method of claim 3, wherein, determining to send the busy indication to the first network side in the case that at least one of the first condition, the second condition and the third condition is met, including at least one of the following: in the case that the second condition and the third condition are met or the first condition, the second condition and the third condition are met, determining to send the RRC layer busy indication or determining whether to send the busy indication to the first network side according to the RRC state of the terminal when the paging message is received; in the case that the third condition is not met and the second condition is met, or the third condition is not met and the first condition and the second condition are met, determining to send the RRC layer busy indication; in the case that the second condition is not met and the third condition is met, or the second condition is not met and the first condition and the third condition are met, determining to send the NAS busy indication.

6. The method of claim 3, wherein, determining whether to send the busy indication to the first network side includes at least one of the following: in the case that the second condition is not met and the third condition is met, or the second condition is not met and the first condition and the third condition are met, determining not to send the busy indication; in the case that the second condition is not met and the third condition is not met, determining not to send the busy indication.

7. The method of claim 1 or 5, wherein, determining whether to send the busy indication to the first network side according to the RRC state of the terminal when the paging message is received, including: if the terminal is in RRC inactive state, sending RRC layer busy indication; or if the terminal is in RRC idle state, sending NAS busy indication.

8. The method of claim 1, wherein, the busy indication is carried by one of the following messages: RRC connection resume request message, RRC connection resume complete message, RRC connection setup request message, RRC connection setup complete message, security mode command (SMC) complete message, NAS message.

9. The method of claim 4, wherein, the method further includes: determining paging cause of the paging message according to the third indication information and / or the fourth indication information.

10. The method of claim 1, wherein, further including at least one of the following: sending release indication information to the first network side, the release indication information being used for indicating that the first network side releases the terminal; indicating a second timer length to the first network side, the second timer length being used to indicate a time length during which the terminal is busy or unable to receive a paging message.

11. The method of claim 10, wherein, The release indication information and / or the second timer length is carried by one of the following messages: an RRC connection resume request message, an RRC connection resume complete message, an RRC connection setup request message, an RRC connection setup complete message, a security mode command (SMC) complete message, and a NAS message.

12. The method of claim 1, wherein, After sending the busy indication to the first network side, the method further includes at least one of the following: If an RRC release message is not received, the terminal enters an RRC idle state. If a T319 timer expires, the terminal enters an RRC idle state, and a first timer is started, the first timer being used to indicate a waiting time length during which the terminal receives an RRC release message.

13. The method of claim 12, wherein, After starting the first timer, the method further includes: If an RRC release message is received, the first timer is stopped; or If the first timer expires, the terminal releases to a first RRC state, the first RRC state being an RRC idle state or an RRC inactive state.

14. The method of claim 13, wherein, The method further includes: Before or when sending the busy indication, the first timer length and / or the first RRC state are sent to the first network side.

15. The method of claim 5, wherein, In a case where the second condition is not met and the third condition is met, or the second condition is not met and the first condition and the third condition are met, sending the NAS busy indication further includes: An RRC layer reports the busy indication or a paging cause value in the paging message to an upper layer.

16. The method of claim 15, wherein, After the RRC layer reports the busy indication or the paging cause value in the paging message to the upper layer, the method further includes: The terminal enters an RRC idle state.

17. The method of claim 12 or 16, wherein, After the terminal enters the RRC idle state, the method further includes: A release cause value is set.

18. The method of claim 17, wherein, The release cause value includes at least one of the following: an RRC connection failure, an RRC connection resume failure, a busy indication failure, and a first cause value.

19. The method of claim 1, wherein, The sending of the busy indication to the first network side includes: If a random access channel failure occurs when the busy indication is sent to the first network side, the sending of the busy indication is stopped.

20. A method of transmission of a busy indication, characterized by, The method is performed by a device of a first network side, and the method includes: Receiving a busy indication sent by a terminal; Performing a corresponding operation according to the busy indication; The busy indication is used to indicate that the terminal does not accept or rejects a paging of the first network side; The busy indication is also used to instruct the first network side to release the terminal to a first RRC state, the first RRC state being an RRC idle state. The busy indication is sent by the terminal according to an RRC state when a paging message sent by the first network side is received.

21. The method of claim 20, wherein, The busy indication includes at least one of the following: an RRC layer busy indication and a NAS busy indication.

22. The method of claim 21, wherein, The busy indication includes an RRC layer busy indication, and performing a corresponding operation according to the busy indication includes: Performing a first operation according to the busy indication, the first operation including at least one of the following: Stopping or no longer initiating a paging related to the terminal; Discarding or blocking or buffering the arrived downlink data or signaling.

23. The method of claim 22, wherein, The first operation performed according to the busy indication comprises: Starting a second timer after receiving the RRC layer busy indication; Performing the first operation during the running of the second timer; Stopping the second timer if an uplink message sent by the terminal is received; Stopping the first operation if the second timer expires.

24. The method of claim 21, wherein, The busy indication comprises a NAS busy indication; and performing a corresponding operation according to the busy indication comprises: Performing a second operation according to the busy indication, the second operation comprising at least one of: Sending the busy indication to an anchor base station or a last serving base station of the terminal; Stopping sending downlink data or signaling to the anchor base station or the last serving base station of the terminal; Stopping or no longer initiating paging related to the terminal; Discarding or blocking or buffering the arrived downlink data or signaling.

25. The method of claim 24, wherein, The second operation performed according to the busy indication comprises: Starting a second timer after receiving the NAS busy indication; Performing the second operation during the running of the second timer; Stopping the second timer if an uplink message sent by the terminal is received; Stopping the second operation if the second timer expires.

26. The method of claim 20, wherein, Further comprising: Receiving release indication information sent by the terminal, the release indication information being used to instruct the first network side to release the terminal.

27. The method of claim 26, wherein, After receiving the release indication information sent by the terminal, further comprising at least one of: Sending an RRC release message to the terminal according to the release indication information; Releasing the terminal to an RRC idle state or an RRC inactive state indicated in the release indication information.

28. The method of claim 20, wherein, After receiving the busy indication sent by the terminal, the method further comprises: Sending an RRC release message to the terminal according to the busy indication.

29. An apparatus for transmission of a busy indication, the apparatus comprising: Comprise: A judging module, configured to judge whether to send a busy indication to the first network side after listening to a paging message sent by the first network side; A first sending module, configured to send the busy indication to the first network side if it is judged to send the busy indication to the first network side; The busy indication is used to instruct the terminal not to accept paging or to reject paging; The busy indication is further used to instruct the first network side to release the terminal to a first RRC state, the first RRC state being an RRC idle state; The judging module is configured to judge whether to send the busy indication to the first network side according to an RRC state when the paging message is received.

30. The apparatus of claim 29, wherein, The busy indication comprises at least one of a radio resource control (RRC) layer busy indication and a non-access stratum (NAS) busy indication.

31. The apparatus of claim 29, wherein: the judging module is configured to judge to send the busy indication to the first network side if at least one of a first condition, a second condition and a third condition is met, wherein: the first condition comprises at least one of: the paging message is sent by the first network side of a card of the terminal, and a service priority corresponding to the paging message is lower than or equal to a service priority of a service being executed or to be executed by the terminal on another card. The paging message is sent by the first network side of a card of the terminal, and other cards of the terminal are performing or will perform preset services; The terminal does not send a leaving indication information to the first network side before listening to the paging message, and the leaving indication information is used to indicate that the terminal cannot receive and transmit data on the first network side; The terminal does not send the busy indication to the first network side before listening to the paging message; The second condition includes at least one of the following: The anchor base station or the last serving base station can receive or process the RRC layer busy indication or require the terminal to send the RRC layer busy indication; The anchor base station or the last serving base station supports sending a paging cause value; The anchor base station or the last serving base station supports a function or feature related to the multi-card terminal; The third condition includes at least one of the following: The core network can receive or process the NAS busy indication or require the terminal to send the NAS busy indication; The core network supports sending a paging cause value; The core network supports a function or feature related to the multi-card terminal.

32. The apparatus of claim 29, wherein, Further comprising at least one of the following: A first receiving module is configured to receive first indication information through a broadcast message or dedicated signaling, and the first indication information is used to indicate whether the anchor base station or the last serving base station can receive or process the RRC layer busy indication or require the terminal to send the RRC layer busy indication; A second receiving module is configured to receive second indication information through a broadcast message or dedicated signaling, and the second indication information is used to indicate whether the core network can receive or process the NAS busy indication or require the terminal to send the NAS busy indication; A third receiving module is configured to receive third indication information through a broadcast message or dedicated signaling, and the third indication information is used to indicate whether the anchor base station or the last serving base station supports sending a paging cause value; A fourth receiving module is configured to receive fourth indication information through a broadcast message or dedicated signaling, and the fourth indication information is used to indicate whether the core network supports sending a paging cause value; A fifth receiving module is configured to receive fifth indication information through a broadcast message or dedicated signaling, and the fifth indication information is used to indicate whether the anchor base station or the last serving base station supports a function or feature related to the multi-card terminal; A sixth receiving module is configured to receive sixth indication information through a broadcast message or dedicated signaling, and the sixth indication information is used to indicate whether the core network supports a function or feature related to the multi-card terminal; A second sending module is configured to send seventh indication information to the first network side, and the seventh indication information is used to indicate whether the terminal supports sending the busy indication.

33. The apparatus of claim 29, wherein, Whether to send the busy indication to the first network side is determined according to an RRC state when the paging message is received, including: If the terminal is in an RRC inactive state, an RRC layer busy indication is sent; or If the terminal is in an RRC idle state, an NAS busy indication is sent.

34. The apparatus of claim 29, wherein, The busy indication is carried in one of the following messages: an RRC connection resume request message, an RRC connection resume complete message, an RRC connection setup request message, an RRC connection setup complete message, a security mode command (SMC) complete message, and an NAS message.

35. The apparatus of claim 32, wherein, Further comprising: A module for determining a paging cause of the paging message according to the third indication information and / or the fourth indication information.

36. The apparatus of claim 29, wherein, Further comprising at least one of the following: A third sending module, configured to send release indication information to the first network side, the release indication information being used to instruct the first network side to release the terminal; A fourth sending module, configured to instruct the first network side of a second timer duration, the second timer duration being used to instruct a duration during which the terminal is busy or unable to receive a paging message.

37. The apparatus of claim 29, wherein, Further comprising at least one of the following: A first processing module, configured to, after sending the busy indication to the first network side, enter an RRC idle state if an RRC release message is not received; A second processing module, configured to, if a T319 timer expires, enter an RRC idle state; A third processing module, configured to start a first timer, the first timer being used to instruct a waiting duration during which the terminal receives an RRC release message.

38. The apparatus of claim 37, wherein, Further comprising at least one of the following: A fourth processing module, configured to, if an RRC release message is received, stop the first timer; A fifth processing module, configured to, if the first timer expires, release the terminal to a first RRC state, the first RRC state being an RRC idle state or an RRC inactive state.

39. The apparatus of claim 38, wherein, Further comprising: A fifth sending module, configured to, when or before sending the busy indication, send the first timer duration and / or the first RRC state to the first network side.

40. An apparatus for transmitting a busy indication, the apparatus comprising: The device is a device of a first network side, comprising: A first receiving module, configured to receive a busy indication sent by a terminal; A processing module, configured to perform a corresponding operation according to the busy indication; The busy indication is used to instruct the terminal to not accept or reject a paging of the first network side; The busy indication is also used to instruct the first network side to release the terminal to a first RRC state, the first RRC state being an RRC idle state; The busy indication is sent by the terminal according to an RRC state when a paging message sent by the first network side is received.

41. The apparatus of claim 40, wherein, The busy indication comprises an RRC layer busy indication; the processing module is configured to perform a first operation according to the busy indication, the first operation comprising at least one of the following: Stopping or no longer initiating a paging related to the terminal; Discarding or blocking or buffering arrived downlink data or signaling.

42. The apparatus of claim 40, wherein, The busy indication comprises an NAS busy indication; the processing module is configured to perform a second operation according to the busy indication, the second operation comprising at least one of the following: Sending the busy indication to an anchor base station or a last serving base station of the terminal; Stopping sending downlink data or signaling to the anchor base station or the last serving base station of the terminal; Stopping or no longer initiating a paging related to the terminal; Discarding or blocking or buffering arrived downlink data or signaling.

43. A terminal, characterized by A processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions being executed by the processor to implement the steps of the busy indication transmission method according to any one of claims 1 to 19.

44. A first network-side device, the device comprising: A computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to carry out the steps of the method of claim 20 to 28.

45. A readable storage medium, characterized by, A computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to carry out the method of claim 1 to 19, or the steps of the method of claim 20 to 28.

Images