Notification method, device and terminal for returning to network

Abstract

The present application discloses a notification method, device and terminal for returning to the network, belonging to the field of communication technology. A notification method for returning to the network is executed by a terminal, and the method comprises: determining whether to send a return notification to the network; if it is determined that the return notification is to be sent to the network, sending the return notification to the network. The technical solution of the embodiment of the present application can enable the terminal to notify the network side that the terminal has returned to the network, so that data can be sent and received normally on the network.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device, and terminal for notifying a return to a network. Background Art

[0002] Currently, there are not only single-card terminals on the market, but also dual-card or multi-card terminals, collectively referred to as multi-card terminals. The capabilities of multi-card terminals can include single-transmit and single-receive, single-transmit and dual-receive, or dual-transmit and dual-receive.

[0003] A feature of multi-SIM terminals is that they can reside on multiple networks simultaneously. However, different multi-SIM terminals implement this in different ways. Some multi-SIM terminals can send and receive on multiple networks simultaneously without affecting each other. Other multi-SIM terminals can reside on multiple networks simultaneously, but they may use a time-sharing method to reside on the two networks. This means that they may reside on network A for a period of time, listening to network A's paging, and on network B for a period of time, listening to network B's paging. Alternatively, they may spend some time connecting to network A to send and receive data, and some time connecting to network B to receive paging. Alternatively, they may spend some time connecting to network A to send and receive data, and some time connecting to network B to send and receive data.

[0004] A multi-SIM terminal is connected to network A and may leave network A and switch to network B to perform certain services. When the multi-SIM terminal is about to switch from network A to network B, it can send a leave notification to network A. After receiving the leave notification from the multi-SIM terminal, network A can avoid scheduling or paging the multi-SIM terminal during this period, thereby saving network resources.

[0005] Currently, it is unclear how a multi-SIM terminal notifies the network when it returns to the network. This may cause the UE to be unable to notify the network side that it has returned to the network, resulting in the UE being unable to receive or send data, or under certain conditions the UE sending unnecessary notifications, wasting network resources. Summary of the Invention

[0006] The embodiments of the present application provide a method, device and terminal for notifying the user of a return to the network, which can solve the problem that the UE cannot notify the network side that the UE has returned to the network, thereby causing the UE to be unable to receive or send data or the UE to send unnecessary notifications under certain conditions.

[0007] In a first aspect, an embodiment of the present application provides a method for notifying a terminal of a return to a network, the method comprising:

[0008] Determine whether to send a return notification to the network;

[0009] If it is determined that the return notification is to be sent to the network, the return notification is sent to the network.

[0010] In a second aspect, an embodiment of the present application provides a notification device for returning to a network, applied to a terminal, the device comprising:

[0011] A judgment module, used to judge whether to send a return notification to the network;

[0012] The sending module is configured to send the return notification to the network if it is determined that the return notification should be sent to the network.

[0013] In a third aspect, an embodiment of the present application further provides a terminal comprising a processor, a memory, and a program or instruction stored on the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the notification method for returning to the network as described above.

[0014] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the notification method of returning to the network as described above are implemented.

[0015] In a fifth aspect, an embodiment of the present application provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the method described in the first aspect.

[0016] In an embodiment of the present application, the terminal determines whether to send a return notification to the network. If it is determined that the return notification is to be sent to the network, the terminal sends the return notification to the network. In this way, the terminal can promptly and effectively notify the network side that the terminal has returned to the network, enabling the terminal to receive or send data normally. Under certain conditions, such as when other terminal behaviors are triggered to cause uplink transmission, the terminal can also avoid sending unnecessary return notifications and let the network know that the terminal has returned to the network, saving network resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0018] Figure 1 A schematic diagram showing a wireless communication system;

[0019] Figure 2 A schematic diagram showing the format of BSR;

[0020] Figure 3 A schematic diagram showing a flow chart of a method for returning notification to a network according to an embodiment of the present application;

[0021] Figure 4 and Figure 5 A schematic diagram showing the format of a MAC CE according to an embodiment of the present application;

[0022] Figure 6 A schematic diagram showing the structure of a notification device for returning to the network according to an embodiment of the present application;

[0023] Figure 7 A schematic diagram showing the composition of a terminal according to an embodiment of the present application. DETAILED DESCRIPTION

[0024] The following will be combined with the accompanying drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0025] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects and are not used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments of this application can be implemented in an order other than those illustrated or described herein. In addition, the term "and / or" in the specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0026] The technology described herein is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems and can also be used in various 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" are often used interchangeably. A CDMA system can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. A TDMA system can implement radio technologies such as Global System for Mobile Communication (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and more advanced LTE (such as LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2).The techniques described herein can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes an NR system for example, and NR terminology is used in much of the description, but these techniques can also be applied to applications beyond NR systems.

[0027] The following description provides examples and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the spirit and scope of this disclosure. The various examples may appropriately omit, substitute, or add various procedures or components. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

[0028] See Figure 1 , Figure 1The following is a block diagram of a wireless communication system applicable to embodiments of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may also be referred to as a terminal device or a user equipment (UE). The terminal 11 may be a terminal-side device such as a mobile phone, a tablet personal computer, a laptop computer, a personal digital assistant (PDA), a mobile internet device (MID), a wearable device, or an in-vehicle device. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network side device 12 can be a base station or a core network, wherein the above-mentioned base station can be a base station of 5G and later versions (for example: gNB, 5G NR NB, etc.), or a base station in other communication systems (for example: eNB, WLAN access point, or other access point, etc.), or a location server (for example: E-SMLC or LMF (Location Manager Function)), wherein the base station can be called node B, evolved node B, access point, base transceiver station (Base Transceiver Station, BTS), radio base station, radio transceiver, basic service set (Basic Service Set, BSS), extended service set (Extended Service Set, ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node or other suitable terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the embodiment of the present application is not limited to the specific type of base station and the specific communication system.

[0029] Currently, there are not only single-card terminals on the market, but also dual-card or multi-card terminals, collectively referred to as multi-card terminals. The capabilities of multi-card terminals can include single-transmit and single-receive, single-transmit and dual-receive, or dual-transmit and dual-receive.

[0030] A feature of multi-SIM terminals is that they can reside on multiple networks simultaneously. While connected to network A, a multi-SIM terminal may leave network A and switch to network B to perform certain tasks. When a multi-SIM terminal is about to switch from network A to network B, it can send a leave notification to network A. Upon receiving the leave notification, network A can avoid scheduling or paging the multi-SIM terminal during this period, thereby conserving network resources.

[0031] When the UE has cached uplink data to send, it can send a buffer status report (BSR) to the network side, which indicates the buffer size (i.e. the amount of data to be transmitted) of one or more logical channel groups. The network side can allocate uplink resources of appropriate size to the UE based on the amount of data indicated in the BSR for the UE to perform uplink transmission. BSR includes five formats: short BSR format, long BSR format, short truncated BSR format, long truncated BSR format, and pre-emptive BSR format. The existing BSR formats are as follows: Figure 2 Where, LCG ID is the logical channel group ID, buffer size is the amount of data to be transmitted corresponding to the LCG ID, and MAC CE is the media access control signaling.

[0032] The embodiment of the present application provides a notification method for returning to the network, which is executed by the terminal, such as Figure 3 Shown, including:

[0033] Step 101: Determine whether to send a return notification to the network;

[0034] Step 102: If it is determined that the return notification should be sent to the network, the return notification is sent to the network.

[0035] In this embodiment, the terminal determines whether to send a return notification to the network. If so, the terminal sends the return notification to the network. This allows the terminal to promptly and effectively notify the network side of its return to the network, enabling the terminal to receive or send data normally. Under certain conditions, such as when other terminal actions trigger uplink transmission, the terminal can avoid sending unnecessary return notifications and still inform the network of its return, thereby saving network resources.

[0036] In some embodiments, determining whether to send a return notification to the network includes:

[0037] When a preset condition is met, determining to send the return notification to the network, the preset condition including at least one of the following:

[0038] First preset condition: when the terminal returns to the network, there is no uplink data and / or signaling to be sent;

[0039] The first preset condition is determined based on at least one of the following:

[0040] The indication of the MAC layer of the terminal, the indication of the RRC layer of the terminal, the indication of the service data adaptation protocol SDAP layer of the terminal, the indication of the PDCP layer of the terminal, and the indication of the physical layer PHY of the terminal. It is understandable that there may also be a request and response process between the different protocol layers of the terminal. For example, the RRC layer of the terminal requests the MAC layer of the terminal to indicate whether the terminal currently has uplink data or signaling to be sent (for example, there is data in the cache). In the case where there is uplink data or signaling to be sent, the MAC layer of the terminal sends indication information to the RRC layer. In one embodiment, when the terminal returns to the network, at least one of the SDAP, PDCP, RRC, MAC, and PHY of the terminal is restored or restarted, and new uplink data is generated after restoration or restart.

[0041] Second preset condition: no buffer status report BSR is triggered when the terminal returns to the network;

[0042] The third preset condition: when the terminal returns to the network, a buffer status report BSR is triggered but there are no resources for sending the BSR; for example, the terminal has no PUSCH resources, or the terminal has no resources specifically used to send the BSR.

[0043] Fourth preset condition: when the terminal returns to the network, there is uplink data to be sent, but the uplink data has triggered a BSR, and there are no resources for sending the uplink data.

[0044] The resources for sending the uplink data include a configured grant or a dynamic grant. For example, before a UE leaves the network, it triggers a BSR. The network can allocate certain transmission resources to the UE based on the BSR. Later, due to the UE leaving the network, the network decides to temporarily suspend the configured transmission resources, that is, the UE cannot use these resources for transmission. When the UE returns to the network, these resources are still in the suspended state. At this time, the UE may not be able to trigger the BSR because the BSR triggering conditions are not met, and thus cannot resume the suspended transmission resources. In this case, the UE should send a return notification to the network.

[0045] Fifth preset condition: the network configures the terminal to send a return notification;

[0046] Sixth preset condition: Before the terminal returns to the network, it leaves the network according to the first indication information of the network: One implementation method is that before the terminal leaves the network, it sends a leave request to the network side, and the network side sends a first indication information after receiving it. The first indication information can be used to respond to the leave request or configure the resources required by the terminal when returning to the network.

[0047] Seventh preset condition: the terminal autonomously leaves the network.

[0048] In this embodiment, by setting preset conditions, it is possible to clarify under what circumstances the terminal should send a return notification, so that the terminal can promptly and effectively notify the network side that the terminal has returned to the network, enabling the terminal to receive or send data normally. Under certain conditions, for example, when other behaviors of the terminal are triggered and cause uplink transmission, the terminal can also avoid sending unnecessary return notifications and let the network know that the terminal has returned to the network, saving network resources.

[0049] In some embodiments, determining whether to send a return notification to the network includes:

[0050] The MAC layer of the terminal determines whether to send a return notification to the network; or

[0051] The radio resource control (RRC) layer of the terminal determines whether to send a return notification to the network.

[0052] In a specific example, before determining whether to send a return notification to the network, the MAC layer of the terminal determines whether the terminal returns to the network; or, the MAC layer of the terminal receives indication information from the RRC layer, and the indication information instructs the terminal to return to the network.

[0053] In this embodiment, the terminal may be a multi-card terminal and may reside in multiple networks. However, the terminal in this embodiment is not limited to a multi-card terminal and may also be a single-card terminal.

[0054] In a specific embodiment, taking the case where a terminal can reside in multiple networks, including network A and network B, and the MAC layer of the terminal determines whether to send a return notification to the network as an example, the multi-card terminal is in a connected state in network A and sends a leave notification to network A; thereafter, the multi-card terminal remains in an RRC connected state in network A, switches to network B to initiate an RRC connection or resume, and processes corresponding services; when the multi-card terminal's service in network B ends and / or there is no service to be processed, it decides to return to network A, then the RRC layer of the multi-card terminal instructs the MAC layer to return to the network, and once the RRC indication is received or the MAC determines that the terminal has returned to the network, the MAC layer determines whether to send a return notification to network A based on whether the preset conditions are met, and if the preset conditions are met, a return notification is sent to network A.

[0055] Among them, the multi-card terminal remains in the RRC connection state in network A either after sending a leave notification or after receiving a response message from network A, and the response message explicitly or implicitly instructs the terminal to remain in the RRC connection state.

[0056] In another specific embodiment, before determining whether to send a return notification to the network, the method further includes at least one of the following:

[0057] The RRC layer of the terminal requests or instructs to restore the Packet Data Convergence Protocol PDCP layer of the terminal;

[0058] The RRC layer of the terminal requests the PDCP layer of the terminal to indicate whether there is uplink data to be sent.

[0059] Taking the example of a terminal that can reside in multiple networks, including network A and network B, and the RRC layer of the terminal determining whether to send a return notification to the network, the multi-card terminal is in a connected state in network A and sends a leave notification to network A; thereafter, the multi-card terminal remains in an RRC connected state in network A, switches to network B to initiate an RRC connection or resume, and processes the corresponding business; when the business of the multi-card terminal in network B ends and / or there is no business to be processed, it decides to return to network A, then the RRC layer of the multi-card terminal instructs the MAC layer to return to the network, and when the terminal returns to network A, the RRC layer requests or instructs the resumption of PDCP; PDCP determines whether there is uplink data and indicates to the RRC layer whether there is uplink data; if there is uplink data, PDCP also sends data to the underlying radio link control protocol (RLC) layer and / or MAC layer; after the RRC layer receives the PDCP indication, if it indicates that there is no uplink data to be sent, the RRC layer generates a return notification and sends it to the MAC layer for transmission.

[0060] In some embodiments, after determining to send the return notification to the network, sending the return notification to the network includes at least one of the following:

[0061] Generate or trigger a BSR;

[0062] generating a MAC control element CE, where the MAC CE is used to instruct the terminal to return to the network;

[0063] Triggering a SR, where the SR is used to instruct the terminal to return to the network;

[0064] The MAC layer of the terminal requests the RRC layer to generate the return notification, and before this, the RRC layer sends a request or indication to the MAC layer, indicating that the terminal has returned to the network;

[0065] The RRC layer of the terminal requests the MAC layer to generate the return notification;

[0066] The RRC layer generates the return notification;

[0067] The MAC layer of the terminal sends the return notification generated by the RRC layer, prior to which the MAC layer receives the return notification generated by the RRC layer from the RRC layer, and further, the RRC layer indicates that the current message content is a return notification;

[0068] Initiate random access;

[0069] Trigger CSI reporting or SRS sending.

[0070] In some embodiments, when the terminal returns to the network, the existing BSR triggering conditions may not be met. Therefore, it is necessary to introduce a new BSR triggering condition, namely, triggering a BSR when the terminal returns to the network. The BSR can be any of the following: a regular BSR, a periodic BSR, an empty BSR, or a pre-emptive BSR. An empty BSR indicates that the BSR contains no valid data.

[0071] In some embodiments, the MAC CE used to instruct the terminal to return to the network includes a specific LCID field and / or a specific value field, wherein the LCID field can be called a MAC subheader and the specific value field can be called a MAC protocol data unit.

[0072] In a specific example, Figure 4 As shown, the MAC CE may include only one LCID field. When the value of the LCID field is a first preset value, it indicates that the terminal has returned to the network or that the terminal can send and receive data normally.

[0073] In another specific example, Figure 5 As shown, the MAC CE includes an LCID field (the value of which can be a first preset value) and a numerical field (or direction field). When the MAC CE is received, if the LCID field is the first preset value, it indicates that the UE returns to the network. When the direction field value is 1, it indicates that the UE is ready to receive downlink data. When the value is 0, it indicates that the UE requests the network side to start uplink scheduling.

[0074] In some other embodiments, the LCID field may also be replaced with an extended logical channel identifier eLCID. The eLCID field includes a first parameter (such as Codepoint) and a second parameter (such as Index).

[0075] In some embodiments, the BSR satisfies any of the following:

[0076] The buffer size field does not appear;

[0077] The value of the buffer size field is a preset value, such as 0;

[0078] The value of the LCID field is a preset value, such as 000;

[0079] BSR is empty;

[0080] When the BSR meets any of the above conditions, the BSR represents the terminal returning to the network.

[0081] In some embodiments, if the terminal has dedicated SR resources, an SR is sent.

[0082] In some embodiments, if the terminal has PUSCH resources, any one of the following is performed:

[0083] Sending the BSR;

[0084] Sending the MAC CE;

[0085] The RRC layer generates the return notification;

[0086] The MAC layer of the terminal requests the RRC layer to generate the return notification;

[0087] The RRC layer of the terminal requests the MAC layer to generate the return notification;

[0088] The MAC layer of the terminal sends the return notification generated by the RRC layer.

[0089] In some embodiments, the PUSCH resource may be a resource dedicated to the terminal sending the return notification.

[0090] In some embodiments, if the terminal does not have available PUSCH resources and / or PUCCH resources, random access is initiated. If the UE has dedicated random access channel (RACH) resources, random access is performed using the dedicated RACH resources. If not, the UE performs contention RACH.

[0091] In some embodiments, if the terminal has dedicated resources for reporting CSI or SRS, CSI reporting or SRS sending is triggered.

[0092] In some embodiments, before determining whether to send a return notification to the network, the method further includes:

[0093] Obtaining a configuration of a first resource of the network to send the return notification to the network using the first resource. The configuration of the first resource may be maintained as an existing configuration of the terminal, or may be obtained by the terminal from the network, for example, by including the configuration of the first resource in a response message sent by network A to the terminal's departure notification.

[0094] In some embodiments, the first resource includes at least one of the following:

[0095] configured grant type type1;

[0096] configured grant type2;

[0097] Physical uplink shared channel PUSCH resources;

[0098] Physical uplink control channel PUCCH resources;

[0099] Dedicated scheduling request SR resources;

[0100] Dedicated random access channel RACH resources;

[0101] Dedicated sounding reference signal SRS resources;

[0102] Dedicated channel state information CSI reporting resources.

[0103] In some embodiments, the terminal returning to the network includes at least one of the following:

[0104] Returning to the network before the gap ends or returning to the network without agreeing on the gap length;

[0105] Return to the network at or before a first time, where the first time is before the end of the gap and T seconds are left until the end of the gap, where T is determined by the network configuration or protocol;

[0106] Return to the network after the gap in the network scheduling ends.

[0107] The gap is determined by negotiation between the terminal and the network or is an autonomous gap.

[0108] The above-mentioned gap can be understood as a period of time or a periodic period during which the terminal does not monitor scheduling or send and receive data on the current network (for example, network A), but switches to other networks to perform certain services. At the end of or after the gap, the terminal should return to network A and resume monitoring scheduling or start sending and receiving data. The gap can be reported by the terminal to the network or configured by the network to the terminal, where the gap can include at least one of the following: duration / length, start time (gap start time), end time (gap end time), gap period, purpose of the gap (for Multi-SIM purpose), and addition, modification, or release of the gap configuration.

[0109] In a specific embodiment, when the UE receives an RRC release message in network A or the UE locally releases the RRC connection, or the UE enters the RRC idle or inactive state, the UE does not send busy indication information, or the UE discards the generated busy indication information, specifically including the following steps:

[0110] Step 1: The UE is in connected state in network A;

[0111] Step 2: The UE receives a paging message in network B.

[0112] Step 3: The UE decides to send a busy indication on network B. For example, if the UE determines that the service on network A is important and / or the service on network B is not a voice service, the UE decides to notify network B that it will go to network A to handle the service within a certain period of time.

[0113] Step 4: The UE sends a leave request on network A or applies for a gap from network A to switch to network B and send a busy indication.

[0114] Step 5: The UE receives the connection release message sent by network A;

[0115] Step 6: The UE does not send a busy indication to network B, or if a busy indication has been generated, the UE discards the busy indication;

[0116] Step 7: The UE may initiate an RRC connection in network B.

[0117] It should be noted that the return network notification method provided in the embodiments of the present application can be executed by a return network notification device, or a module in the return network notification device that is used to execute the return network notification method. In the embodiments of the present application, the return network notification method provided in the embodiments of the present application is described by taking the return network notification device executing the return network notification method as an example.

[0118] The embodiment of the present application provides a notification device for returning to the network, which is applied to the terminal 300, such as Figure 6 As shown, the device includes:

[0119] A determination module 310 is configured to determine whether to send a return notification to the network;

[0120] The sending module 320 is configured to send the return notification to the network if it is determined that the return notification should be sent to the network.

[0121] In an embodiment of the present application, the terminal determines whether to send a return notification to the network. If it is determined that the return notification is to be sent to the network, the terminal sends the return notification to the network. In this way, the terminal can promptly and effectively notify the network side that the terminal has returned to the network, enabling the terminal to receive or send data normally. Under certain conditions, such as when other terminal behaviors are triggered to cause uplink transmission, the terminal can also avoid sending unnecessary return notifications and let the network know that the terminal has returned to the network, saving network resources.

[0122] In some embodiments, the judgment module is specifically configured to judge whether to send the return notification to the network when a preset condition is met, and the preset condition includes at least one of the following:

[0123] First preset condition: when the terminal returns to the network, there is no uplink data and / or signaling to be sent;

[0124] In some embodiments, the first preset condition is determined based on at least one of the following:

[0125] The indication of the MAC layer of the terminal, the indication of the RRC layer of the terminal, the indication of the Service Data Adaptation Protocol SDAP layer of the terminal, the indication of the PDCP layer of the terminal, and the indication of the physical layer of the terminal. It is understandable that there may also be a request and response process between the different protocol layers of the terminal. For example, the RRC layer of the terminal requests the MAC layer of the terminal to indicate whether the terminal currently has uplink data or signaling to be sent (for example, there is data in the cache). In the case where there is uplink data or signaling to be sent, the MAC layer of the terminal sends indication information to the RRC layer. In one embodiment, when the terminal returns to the network, at least one of the SDAP, PDCP, RRC, MAC, and PHY of the terminal is restored or restarted, and new uplink data is generated after restoration or restart.

[0126] Second preset condition: no buffer status report BSR is triggered when the terminal returns to the network;

[0127] The third preset condition: when the terminal returns to the network, a buffer status report BSR is triggered but there are no resources for sending the BSR; for example, the terminal has no PUSCH resources, or the terminal has no resources specifically used to send the BSR.

[0128] Fourth preset condition: when the terminal returns to the network, there is uplink data to be sent, but the uplink data has triggered a BSR, and there are no resources for sending the uplink data;

[0129] The resources for sending the uplink data include a configured grant or a dynamic grant. For example, before a UE leaves the network, it triggers a BSR. The network can allocate certain transmission resources to the UE based on the BSR. Later, due to the UE leaving the network, the network decides to temporarily suspend the configured transmission resources, that is, the UE cannot use these resources for transmission. When the UE returns to the network, these resources are still in the suspended state. At this time, the UE may not be able to trigger the BSR because the BSR triggering conditions are not met, and thus cannot resume the suspended transmission resources. In this case, the UE should send a return notification to the network.

[0130] Fifth preset condition: the network configures the terminal to send a return notification;

[0131] Sixth preset condition: Before the terminal returns to the network, it leaves the network according to the first indication information of the network: One implementation method is that before the terminal leaves the network, it sends a leave request to the network side, and the network side sends a first indication information after receiving it. The first indication information can be used to respond to the leave request or configure the resources required by the terminal when returning to the network.

[0132] Seventh preset condition: the terminal autonomously leaves the network.

[0133] In this embodiment, by setting preset conditions, it is possible to clarify under what circumstances the terminal should send a return notification, so that the terminal can promptly and effectively notify the network side that the terminal has returned to the network, enabling the terminal to receive or send data normally. Under certain conditions, for example, when other behaviors of the terminal are triggered and cause uplink transmission, the terminal can also avoid sending unnecessary return notifications and let the network know that the terminal has returned to the network, saving network resources.

[0134] In some embodiments, the sending module is specifically configured to perform at least one of the following:

[0135] Generate or trigger a BSR;

[0136] generating a MAC control element CE, where the MAC CE is used to instruct the terminal to return to the network;

[0137] Trigger SR;

[0138] The MAC layer of the terminal requests the RRC layer to generate the return notification;

[0139] The RRC layer of the terminal requests the MAC layer to generate the return notification;

[0140] The RRC layer generates the return notification;

[0141] The MAC layer of the terminal sends the return notification generated by the RRC layer;

[0142] Initiate random access;

[0143] Trigger CSI reporting or SRS sending.

[0144] In some embodiments, existing BSR triggering conditions may not be met when a terminal returns to the network. Therefore, it is necessary to introduce new BSR triggering conditions, namely, triggering a BSR when the terminal returns to the network. A BSR can be any of the following: a regular BSR, a periodic BSR, an empty BSR, or a pre-emptive BSR. An empty BSR indicates that the BSR contains no valid data.

[0145] In some embodiments, the MAC CE used to instruct the terminal to return to the network includes a specific LCID field and / or a specific value field, wherein the LCID field can be called a MAC subheader and the specific value field can be called a MAC protocol data unit.

[0146] In a specific example, Figure 4 As shown, the MAC CE may include only one LCID field. When the value of the LCID field is a first preset value, it indicates that the terminal has returned to the network or that the terminal can send and receive data normally.

[0147] In another specific example, Figure 5 As shown, the MAC CE includes an LCID field (the value of which can be a first preset value) and a numerical field (or direction field). When the MAC CE is received, if the LCID field is the first preset value, it indicates that the UE returns to the network. When the direction field value is 1, it indicates that the UE is ready to receive downlink data. When the value is 0, it indicates that the UE requests the network side to start uplink scheduling.

[0148] In some other embodiments, the LCID field may also be replaced with an extended logical channel identifier eLCID. The eLCID field includes a first parameter (such as Codepoint) and a second parameter (such as Index).

[0149] In some embodiments, the BSR satisfies any of the following:

[0150] The buffer size field does not appear;

[0151] The value of the buffer size field is the preset value;

[0152] The value of the LCID field is the preset value;

[0153] The BSR is empty.

[0154] In some embodiments, the sending module is specifically configured to send an SR if the terminal has dedicated SR resources.

[0155] In some embodiments, the sending module is specifically configured to, if the terminal has PUSCH resources, perform any one of the following:

[0156] Sending the BSR;

[0157] Sending the MAC CE;

[0158] The RRC layer generates the return notification;

[0159] The MAC layer of the terminal requests the RRC layer to generate the return notification;

[0160] The RRC layer of the terminal requests the MAC layer to generate the return notification;

[0161] The MAC layer of the terminal sends the return notification generated by the RRC layer.

[0162] In some embodiments, the PUSCH resource may be a resource dedicated to the terminal sending the return notification.

[0163] In some embodiments, the sending module is specifically used to initiate random access if the terminal does not have available PUSCH resources and / or PUCCH resources, and if the UE has dedicated random access channel (RACH) resources, use the dedicated RACH resources to perform random access; if not, the UE performs contention RACH.

[0164] In some embodiments, the sending module is specifically configured to trigger CSI reporting or SRS sending if the terminal has dedicated resources for reporting CSI or SRS.

[0165] In some embodiments, the apparatus further includes a processing module configured to perform at least one of the following:

[0166] Requesting or instructing to restore a Packet Data Convergence Protocol (PDCP) layer of the terminal;

[0167] Request the PDCP layer of the terminal to indicate whether there is uplink data to be sent.

[0168] In some embodiments, the apparatus further comprises:

[0169] An acquisition module is used to acquire the configuration of the first resource of the network, so as to use the first resource to send the return notification to the network.

[0170] In some embodiments, the first resource includes at least one of the following:

[0171] configured grant type type1;

[0172] configured grant type2;

[0173] Physical uplink shared channel PUSCH resources;

[0174] Physical uplink control channel PUCCH resources;

[0175] Dedicated scheduling request SR resources;

[0176] Dedicated random access channel RACH resources;

[0177] Dedicated sounding reference signal SRS resources;

[0178] Dedicated channel state information CSI reporting resources.

[0179] In some embodiments, the terminal returning to the network includes at least one of the following:

[0180] Returning to the network before the gap ends or returning to the network without agreeing on the gap length;

[0181] Return to the network at or before a first time, where the first time is before the end of the gap and T seconds are left until the end of the gap, where T is determined by the network configuration or protocol;

[0182] Return to the network after the gap in the network scheduling ends.

[0183] The gap is determined by negotiation between the terminal and the network or is an autonomous gap.

[0184] The above-mentioned gap can be understood as a period of time or a periodic period during which the terminal does not monitor scheduling or send and receive data on the current network (for example, network A), but switches to other networks to perform certain services. At the end of or after the gap, the terminal should return to network A and resume monitoring scheduling or start sending and receiving data. The gap can be reported by the terminal to the network or configured by the network to the terminal, where the gap can include at least one of the following: duration / length, start time (gap start time), end time (gap end time), gap period, purpose of the gap (for Multi-SIM purpose), and addition, modification, or release of the gap configuration.

[0185] The notification device for returning to the network in the embodiments of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. For example, the mobile electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. The non-mobile electronic device can be a network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.

[0186] The device for notifying the user of the return network in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0187] Optionally, an embodiment of the present application also provides a terminal, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, the various processes of the embodiment of the above-mentioned notification method for returning to the network are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0188] It should be noted that the terminals in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0189] Figure 7 To implement the hardware structure diagram of a terminal in each embodiment of the present application, the terminal 50 includes but is not limited to: a radio frequency unit 51, a network module 52, an audio output unit 53, an input unit 54, a sensor 55, a display unit 56, a user input unit 57, an interface unit 58, a memory 59, a processor 510, and a power supply 511. Those skilled in the art will understand that Figure 7 The terminal structure shown in the figure does not constitute a limitation of the terminal. The terminal may include more or fewer components than shown, or combine certain components, or arrange the components differently. In the embodiments of the present application, the terminal includes but is not limited to a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted terminal, a wearable device, and a pedometer.

[0190] It should be understood that in the embodiments of the present application, the RF unit 51 can be used to receive and transmit signals during information transmission or calls. Specifically, it receives downlink data from the base station and transmits it to the processor 510 for processing; in addition, it transmits uplink data to the base station. Typically, the RF unit 51 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like. Furthermore, the RF unit 51 can communicate with the network and other devices via a wireless communication system.

[0191] Memory 59 can be used to store software programs and various data. Memory 59 may primarily include a program storage area and a data storage area. The program storage area may store an operating system and at least one application required for a function (such as a sound playback function or an image playback function); the data storage area may store data generated based on the use of the mobile phone (such as audio data, a phone book, etc.). Furthermore, memory 59 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0192] Processor 510 is the terminal's control center, connecting various components of the terminal using various interfaces and circuits. By running or executing software programs and / or modules stored in memory 59 and accessing data stored in memory 59, it performs various terminal functions and processes data, thereby providing overall terminal monitoring. Processor 510 may include one or at least two processing units; preferably, processor 510 may integrate an application processor and a modem processor. The application processor primarily handles the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into processor 510.

[0193] The terminal 50 may also include a power supply 511 (such as a battery) for supplying power to various components. Preferably, the power supply 511 may be logically connected to the processor 510 through a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption.

[0194] In addition, the terminal 50 includes some functional modules not shown, which will not be described in detail here.

[0195] In some embodiments, the processor 510 is configured to determine whether to send a return notification to the network; if it is determined to send the return notification to the network, the radio frequency unit 51 is configured to send the return notification to the network.

[0196] In some embodiments, the processor 510 is specifically configured to determine whether to send the return notification to the network when a preset condition is met, where the preset condition includes at least one of the following:

[0197] First preset condition: when the terminal returns to the network, there is no uplink data and / or signaling to be sent;

[0198] Second preset condition: no buffer status report BSR is triggered when the terminal returns to the network;

[0199] A third preset condition: when the terminal returns to the network, a buffer status report (BSR) is triggered but there are no resources to send the BSR;

[0200] Fourth preset condition: when the terminal returns to the network, there is uplink data to be sent, but the uplink data has triggered a BSR, and there are no resources for sending the uplink data;

[0201] Fifth preset condition: the network configures the terminal to send a return notification;

[0202] Sixth preset condition: before returning to the network, the terminal leaves the network according to the first instruction information of the network:

[0203] Seventh preset condition: the terminal autonomously leaves the network.

[0204] In some embodiments, determining whether to send a return notification to the network includes:

[0205] The MAC layer of the terminal determines whether to send a return notification to the network; or

[0206] The RRC layer of the terminal determines whether to send a return notification to the network.

[0207] In some embodiments, after the processor 510 determines to send the return notification to the network, sending the return notification to the network includes at least one of the following:

[0208] Generate or trigger a BSR;

[0209] generating a MAC control element CE, where the MAC CE is used to instruct the terminal to return to the network;

[0210] Trigger SR;

[0211] The MAC layer of the terminal requests the RRC layer to generate the return notification;

[0212] The RRC layer of the terminal requests the MAC layer to generate the return notification;

[0213] The RRC layer generates the return notification;

[0214] The MAC layer of the terminal sends the return notification generated by the RRC layer;

[0215] Initiate random access;

[0216] Trigger CSI reporting or SRS sending.

[0217] In some embodiments, the MAC CE includes a specific LCID field and / or a specific value field.

[0218] In some embodiments, the BSR satisfies any of the following:

[0219] The buffer size field does not appear;

[0220] The value of the buffer size field is the preset value;

[0221] The value of the LCID field is the preset value;

[0222] The BSR is empty.

[0223] In some embodiments, the radio frequency unit 51 is configured to send an SR if dedicated SR resources exist for the terminal.

[0224] In some embodiments, the processor 510 is configured to, if the terminal has PUSCH resources, perform any one of the following:

[0225] Sending the BSR;

[0226] Sending the MAC CE;

[0227] The RRC layer generates the return notification;

[0228] The MAC layer of the terminal requests the RRC layer to generate the return notification;

[0229] The RRC layer of the terminal requests the MAC layer to generate the return notification;

[0230] The MAC layer of the terminal sends the return notification generated by the RRC layer.

[0231] In some embodiments, the processor 510 is configured to initiate random access if the terminal has no available PUSCH resources and / or PUCCH resources.

[0232] In some embodiments, the processor 510 is configured to trigger CSI reporting or SRS sending if the terminal has dedicated resources for reporting CSI or SRS.

[0233] In some embodiments, the processor 510 is further configured to perform at least one of the following:

[0234] The RRC layer of the terminal requests or instructs to restore the Packet Data Convergence Protocol PDCP layer of the terminal;

[0235] The RRC layer of the terminal requests the PDCP layer of the terminal to indicate whether there is uplink data to be sent.

[0236] In some embodiments, the radio frequency unit 51 is further configured to obtain a configuration of a first resource of the network, so as to send the return notification to the network using the first resource.

[0237] In some embodiments, the first resource includes at least one of the following:

[0238] configured grant type type1;

[0239] configured grant type2;

[0240] Physical uplink shared channel PUSCH resources;

[0241] Physical uplink control channel PUCCH resources;

[0242] Dedicated scheduling request SR resources;

[0243] Dedicated random access channel RACH resources;

[0244] Dedicated sounding reference signal SRS resources;

[0245] Dedicated channel state information CSI reporting resources.

[0246] In some embodiments, the first preset condition is determined based on at least one of the following:

[0247] An indication of the MAC layer of the terminal, an indication of the RRC layer of the terminal, an indication of the Service Data Adaptation Protocol (SDAP) layer of the terminal, an indication of the PDCP layer of the terminal, and an indication of the physical layer of the terminal.

[0248] In some embodiments, the terminal returning to the network includes at least one of the following:

[0249] Returning to the network before the gap ends or returning to the network without agreeing on the gap length;

[0250] Return to the network at or before a first time, where the first time is before the end of the gap and T seconds are left until the end of the gap, where T is determined by the network configuration or protocol;

[0251] Return to the network after the gap in the network scheduling ends.

[0252] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the embodiment of the above-mentioned notification method for returning to the network are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0253] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0254] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the embodiment of the above-mentioned notification method for returning to the network, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0255] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0256] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements does not include those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0257] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course 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 the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0258] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A notification method for returning to a network, characterized in that: Executed by a terminal, the method includes: Determine whether to send a return notification to the network; If it is determined that the return notification is to be sent to the network, sending the return notification to the network; The determining whether to send a return notification to the network includes: The MAC layer of the terminal determines whether to send a return notification to the network; After the determination is made to send the return notification to the network, sending the return notification to the network includes: Initiate random access; Wherein, the terminal is a multi-card terminal; The determining whether to send a return notification to the network includes: In the case where the terminal returns to the network before the gap ends, determining whether to send the return notification to the network; The gap is a MUSIM gap.

2. The method for notifying the return network according to claim 1, characterized in that: Determine whether to send a return notification to the network, including: When a preset condition is met, it is determined to send the return notification to the network, where the preset condition includes at least one of the following: First preset condition: when the terminal returns to the network, there is no uplink data and / or signaling to be sent; Second preset condition: no buffer status report BSR is triggered when the terminal returns to the network; The third preset condition: when the terminal returns to the network, a buffer status report BSR is triggered but there is no resource to send the BSR; Fourth preset condition: when the terminal returns to the network, there is uplink data to be sent, but the uplink data has triggered a BSR, and there is no resource for sending the uplink data; Fifth preset condition: the network configures the terminal to send a return notification; Sixth preset condition: before the terminal returns to the network, the terminal leaves the network according to the first indication information of the network: Seventh preset condition: the terminal autonomously leaves the network.

3. The method for notifying the return network according to claim 1, characterized in that: After determining to send the return notification to the network, sending the return notification to the network further includes at least one of the following: Generate or trigger a BSR; generating a MAC control element CE, where the MAC CE is used to instruct the terminal to return to the network; Trigger SR; The MAC layer of the terminal requests the RRC layer to generate the return notification; The RRC layer of the terminal requests the MAC layer to generate the return notification; The RRC layer generates the return notification; The MAC layer of the terminal sends the return notification generated by the RRC layer; Trigger CSI reporting or SRS sending.

4. The method for notifying the return network according to claim 3, characterized in that: The MAC CE includes a specific logical channel identifier LCID field and / or a specific value field.

5. The method for notifying the return network according to claim 3, characterized in that: The BSR satisfies any of the following: The buffer size field does not appear; The value of the buffer size field is the preset value; The value of the LCID field is the preset value; The BSR is empty.

6. The method for notifying the return network according to claim 3, characterized in that: If the terminal has dedicated SR resources, an SR is sent.

7. The method for notifying the return network according to claim 3, characterized in that: If the terminal has PUSCH resources, perform any of the following: Sending the BSR; Sending the MAC CE; The RRC layer generates the return notification; The MAC layer of the terminal requests the RRC layer to generate the return notification; The RRC layer of the terminal requests the MAC layer to generate the return notification; The MAC layer of the terminal sends the return notification generated by the RRC layer.

8. The method for notifying the return network according to claim 3, characterized in that: If the terminal has no available PUSCH resources and / or PUCCH resources, random access is initiated.

9. The method for notifying the return network according to claim 3, characterized in that: If the terminal has dedicated resources for reporting CSI or SRS, CSI reporting or SRS sending is triggered.

10. The method for notifying the return network according to claim 1, characterized in that: Before determining whether to send a return notification to the network, the method further includes at least one of the following: The RRC layer of the terminal requests or instructs to restore the Packet Data Convergence Protocol PDCP layer of the terminal; The RRC layer of the terminal requests the PDCP layer of the terminal to indicate whether there is uplink data to be sent.

11. The method for notifying the return network according to claim 1, characterized in that: Before determining to send a return notification to the network, the method further includes: The configuration of a first resource of the network is obtained to send the return notification to the network by using the first resource.

12. The method for notifying the return network according to claim 11, characterized in that: The first resource includes at least one of the following: configured grant type type1; configured grant type2; Physical uplink shared channel PUSCH resources; Physical uplink control channel PUCCH resources; Dedicated scheduling request SR resources; Dedicated random access channel RACH resources; Dedicated sounding reference signal SRS resources; Dedicated channel state information CSI reporting resources.

13. The method for notifying the return network according to claim 2, characterized in that: The first preset condition is determined based on at least one of the following: An indication of the MAC layer of the terminal, an indication of the RRC layer of the terminal, an indication of the Service Data Adaptation Protocol SDAP layer of the terminal, an indication of the PDCP layer of the terminal, and an indication of the physical layer of the terminal.

14. The method for notifying the return network according to claim 1, characterized in that: The terminal returning to the network includes at least one of the following: Returning to the network before the gap ends or returning to the network without agreeing on the gap length; Return to the network at or before a first time, where the first time is before the end of the gap and there are T seconds left before the end of the gap, where T is determined by the network configuration or protocol; Return to the network after the gap in the network scheduling ends.

15. A notification device for returning to a network, characterized in that: Applied to a terminal, the device comprises: A judgment module, used to judge whether to send a return notification to the network; A sending module, configured to send the return notification to the network if it is determined that the return notification is to be sent to the network; The judgment module is specifically used to execute: The MAC layer of the terminal determines whether to send a return notification to the network; The sending module is specifically used to execute: Initiate random access; Wherein, the terminal is a multi-card terminal; Wherein, the judgment module is specifically used for: In the case where the terminal returns to the network before the gap ends, determining whether to send the return notification to the network; The gap is a MUSIM gap.

16. The notification device for returning to the network according to claim 15, characterized in that: The judgment module is specifically configured to judge whether to send the return notification to the network when a preset condition is met, and the preset condition includes at least one of the following: First preset condition: when the terminal returns to the network, there is no uplink data and / or signaling to be sent; Second preset condition: no buffer status report BSR is triggered when the terminal returns to the network; The third preset condition: when the terminal returns to the network, a buffer status report BSR is triggered but there is no resource to send the BSR; Fourth preset condition: when the terminal returns to the network, there is uplink data to be sent, but the uplink data has triggered a BSR, and there is no resource for sending the uplink data; Fifth preset condition: the network configures the terminal to send a return notification; Sixth preset condition: before the terminal returns to the network, the terminal leaves the network according to the first indication information of the network: Seventh preset condition: the terminal autonomously leaves the network.

17. The notification device for returning to the network according to claim 15, characterized in that: The sending module is further specifically configured to perform at least one of the following: Generate or trigger a BSR; generating a MAC control element CE, where the MAC CE is used to instruct the terminal to return to the network; Trigger SR; The MAC layer of the terminal requests the RRC layer to generate the return notification; The RRC layer of the terminal requests the MAC layer to generate the return notification; The RRC layer generates the return notification; The MAC layer of the terminal sends the return notification generated by the RRC layer; Trigger CSI reporting or SRS sending.

18. The notification device for returning to the network according to claim 17, characterized in that: The MAC CE includes a specific LCID field and / or a specific value field.

19. The notification device for returning to the network according to claim 17, characterized in that: The BSR satisfies any of the following: The buffer size field does not appear; The value of the buffer size field is the preset value; The value of the LCID field is the preset value; The BSR is empty.

20. The notification device for returning to the network according to claim 17, characterized in that: The sending module is specifically configured to send an SR if the terminal has dedicated SR resources.

21. The notification device for returning to the network according to claim 17, characterized in that: The sending module is specifically configured to execute any one of the following if the terminal has PUSCH resources: Sending the BSR; Sending the MAC CE; The RRC layer generates the return notification; The MAC layer of the terminal requests the RRC layer to generate the return notification; The RRC layer of the terminal requests the MAC layer to generate the return notification; The MAC layer of the terminal sends the return notification generated by the RRC layer.

22. The notification device for returning to the network according to claim 17, characterized in that: The sending module is specifically configured to initiate random access if the terminal has no available PUSCH resources and / or PUCCH resources.

23. The notification device for returning to the network according to claim 17, characterized in that: The sending module is specifically configured to trigger CSI reporting or SRS sending if the terminal has dedicated resources for reporting CSI or SRS.

24. The notification device for returning to the network according to claim 15, characterized in that: The apparatus further comprises a processing module configured to perform at least one of the following: Requesting or instructing to restore a packet data convergence protocol PDCP layer of the terminal; The PDCP layer of the terminal is requested to indicate whether there is uplink data to be sent.

25. The notification device for returning to the network according to claim 15, characterized in that: The device also includes: The acquisition module is used to acquire the configuration of the first resource of the network so as to use the first resource to send the return notification to the network.

26. The notification device for returning to the network according to claim 25, characterized in that: The first resource includes at least one of the following: configured grant type type1; configured grant type2; Physical uplink shared channel PUSCH resources; Physical uplink control channel PUCCH resources; Dedicated scheduling request SR resources; Dedicated random access channel RACH resources; Dedicated sounding reference signal SRS resources; Dedicated channel state information CSI reporting resources.

27. The notification device for returning to the network according to claim 16, characterized in that: The first preset condition is determined based on at least one of the following: An indication of the MAC layer of the terminal, an indication of the RRC layer of the terminal, an indication of the Service Data Adaptation Protocol SDAP layer of the terminal, an indication of the PDCP layer of the terminal, and an indication of the physical layer of the terminal.

28. The notification device for returning to the network according to claim 15, characterized in that: The terminal returning to the network includes at least one of the following: Returning to the network before the gap ends or returning to the network without agreeing on the gap length; Return to the network at or before a first time, where the first time is before the end of the gap and there are T seconds left before the end of the gap, where T is determined by the network configuration or protocol; Return to the network after the gap in the network scheduling ends.

29. A terminal, characterized in that: The method comprises a processor, a memory and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method for notifying the return network as described in any one of claims 1 to 14.

30. A readable storage medium, characterized in that: The readable storage medium stores a program or an instruction, and when the program or the instruction is executed by the processor, the steps of the method for notifying the return to the network as described in any one of claims 1 to 14 are implemented.

Images