WO2022152119A1 - 返回网络的通知方法、装置及终端 - Google Patents

返回网络的通知方法、装置及终端 Download PDF

Info

Publication number
WO2022152119A1
WO2022152119A1 PCT/CN2022/071314 CN2022071314W WO2022152119A1 WO 2022152119 A1 WO2022152119 A1 WO 2022152119A1 CN 2022071314 W CN2022071314 W CN 2022071314W WO 2022152119 A1 WO2022152119 A1 WO 2022152119A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
terminal
notification
return
returning
Prior art date
Application number
PCT/CN2022/071314
Other languages
English (en)
French (fr)
Inventor
蒲文娟
鲍炜
杨晓东
刘选兵
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to EP22738998.8A priority Critical patent/EP4266751A1/en
Priority to JP2023542744A priority patent/JP2024503858A/ja
Publication of WO2022152119A1 publication Critical patent/WO2022152119A1/zh
Priority to US18/222,472 priority patent/US20230370911A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0072Transmission or use of information for re-establishing the radio link of resource information of target access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/18Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/183Processing at user equipment or user record carrier
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0066Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/14Reselecting a network or an air interface
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06De-registration or detaching
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/25Maintenance of established connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/14Reselecting a network or an air interface
    • H04W36/144Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1443Reselecting a network or an air interface over a different radio air interface technology between licensed networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/005Multiple registrations, e.g. multihoming
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • H04W88/06Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a notification method, device and terminal for returning to a network.
  • multi-card terminals there are not only single-card terminals, but also dual-card or multi-card terminals on the market, which are collectively referred to as multi-card terminals.
  • the capabilities of the multi-card terminal can be single-send single-receive, single-send double-receive, and double-send double-receive.
  • a feature of a multi-card terminal is that it can reside on multiple networks at the same time, but different multi-card terminals have different implementations, and some multi-card terminals can transmit and receive simultaneously on multiple networks without affecting each other.
  • Some multi-card terminals can reside on multiple networks at the same time, but may reside on two networks in a time-division manner, that is, they reside on network A for a period of time to listen to the paging of network A, and reside on network B for a period of time to listen to the paging of network A.
  • the multi-card terminal is in the connected state in network A, and may leave network A and switch to network B to perform some services.
  • the multi-card terminal When the multi-card terminal is ready to switch from network A to network B, it can send a leave notification to network A, so that after network A receives the leave notification sent by the multi-card terminal, it can avoid scheduling or paging the multi-card terminal during this period. , thereby saving network resources.
  • the embodiments of the present application provide a notification method, device and terminal for returning to the network, which can solve the problem that the UE cannot notify the network side that the UE has returned to the network, so that the UE has been unable to receive or send data, or the UE sends unnecessary data under certain conditions. Notification problem.
  • an embodiment of the present application provides a notification method for returning to a network, which is executed by a terminal, and the method includes:
  • an embodiment of the present application provides a notification device for returning to a network, which is applied to a terminal, and the device includes:
  • the judgment module is 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 to send the return notification to the network.
  • an embodiment of the present application further provides a terminal, including a processor, a memory, and a program or instruction stored on the memory and executable on the processor, where the program or instruction is processed by the When the server executes, it implements the steps of the notification method returning to the network as described above.
  • an embodiment of the present application provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the above-mentioned notification method for returning to the network is implemented. step.
  • an embodiment of the present application provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction, and implement the first aspect the method described.
  • a computer program product is provided, the computer program product is stored in a non-volatile storage medium, the computer program product is executed by at least one processor to implement the method of the first aspect.
  • the terminal determines whether to send a return notification to the network, and if it determines to send the return notification to the network, the terminal sends the return notification to the network, so that the terminal can timely and effectively notify the network side that the terminal has Returning to the network enables the terminal to receive or send data normally.
  • 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.
  • FIG. 1 shows a schematic diagram of a wireless communication system
  • Fig. 2 shows the format schematic diagram of BSR
  • FIG. 3 shows a schematic flowchart of a notification method for returning to a network according to an embodiment of the present application
  • Fig. 4 and Fig. 5 show the format schematic diagram of the MAC CE of the embodiment of the present application
  • FIG. 6 is a schematic structural diagram of a notification device for returning to a network according to an embodiment of the present application.
  • FIG. 7 shows a schematic diagram of the composition of a terminal according to an embodiment of the present application.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA single carrier frequency Division Multiple Access
  • SC-FDMA single carrier frequency Division Multiple Access
  • a CDMA system may implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA).
  • UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants.
  • a TDMA system may implement a radio technology such as the Global System for Mobile Communication (GSM).
  • GSM Global System for Mobile Communication
  • OFDMA system can realize such as UltraMobile Broadband (UMB), Evolution-UTRA (Evolution-UTRA, E-UTRA), IEEE802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. radio technology.
  • UMB UltraMobile Broadband
  • Evolution-UTRA Evolution-UTRA
  • E-UTRA Evolution-UTRA
  • IEEE802.11 Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • Flash-OFDM Flash-OFDM
  • UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS).
  • LTE and higher LTE eg LTE-A
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP
  • CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • 3GPP2 3rd Generation Partnership Project 2
  • the techniques described herein may be used for both 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 purposes, and NR terminology is used in much of the following description, but the techniques are also applicable to applications other than NR system applications.
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • 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 terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a personal digital assistant (Personal Digital Assistant) , PDA), mobile Internet Device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device and other terminal-side devices, it should be noted that the specific type of the terminal 11 is not limited in the embodiments of this application .
  • the network side device 12 may be a base station or a core network, wherein the above-mentioned base station may 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 points, etc.), or a location server (for example: E-SMLC or LMF (Location Manager Function)), where the base station may be referred to as Node B, Evolved Node B, Access Point, Base Transceiver Station (Base Transceiver Station, BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Node B, Evolved Node B (eNB), Home B Node, home evolved Node B, WLAN access point, WiFi node or some other suitable term 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 this Only the base station
  • multi-card terminals there are not only single-card terminals, but also dual-card or multi-card terminals on the market, which are collectively referred to as multi-card terminals.
  • the capabilities of the multi-card terminal can be single-send single-receive, single-send double-receive, and double-send double-receive.
  • a feature of a multi-card terminal is that it can reside on multiple networks at the same time.
  • the multi-card terminal is in a connected state in network A and may leave network A and switch to network B to perform some services.
  • the multi-card terminal can send a leave notification to network A, so that after network A receives the leave notification sent by the multi-card terminal, it can avoid scheduling or paging the multi-card terminal during this period. , thereby saving network resources.
  • BSR buffer state report
  • the network side can allocate uplink resources of a suitable size to the UE according to the size of the data amount indicated in the BSR, for the UE to perform uplink transmission.
  • BSR includes short (short) BSR format, long BSR format, short truncated (short Truncated) BSR format, long truncated (Long Truncated) BSR format, priority (Pre-emptive) BSR format 5 kinds, the existing BSR format is shown in the figure 2 shown.
  • the LCG ID is the logical channel group (Logical Channel Group, LCG) ID
  • the buffer size is the amount of data to be transmitted corresponding to the LCG ID
  • the MAC CE is the medium access control (Medium Access Control, MAC) control signaling (Control Element) , CE).
  • the embodiment of the present application provides a notification method for returning to the network, which is executed by a terminal, as shown in FIG. 3 , including:
  • Step 101 determine whether to send a return notification to the network
  • Step 102 If it is determined to send the return notification to the network, send the return notification to the network.
  • the terminal determines whether to send a return notification to the network, and if it determines to send the return notification to the network, the terminal sends the return notification to the network, so that the terminal can timely and effectively notify the network side that the terminal has returned to the network , enabling the terminal to receive or send data normally.
  • 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.
  • determining whether to send a return notification to the network includes:
  • the preset condition includes at least one of the following:
  • the first preset condition when the terminal returns to the network, there is no uplink data and/or signaling to be sent;
  • the first preset condition is determined based on at least one of the following:
  • the indication of the MAC layer of the terminal the indication of the radio resource control (Radio Resource Control, RRC) layer of the terminal, the indication of the Service Data Adaptation Protocol (Service Data Adaptation Protocol, SDAP) layer of the terminal, the The indication of the (Packet Data Convergence Protocol, PDCP) layer of the terminal, and the indication of the physical layer (Physical, PHY) of the terminal.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • Physical layer Physical layer
  • the MAC layer of the terminal When there is uplink data or signaling to be sent, the MAC layer of the terminal sends indication information to the RRC layer.
  • the terminal when the terminal returns to the network, at least one of SDAP, PDCP, RRC, MAC, and PHY of the terminal is restored or restarted, and new uplink data is generated after the restoration or restart.
  • the second preset condition no buffer status report (Buffer Status Report, BSR) is triggered when the terminal returns to the network;
  • the third preset condition when the terminal returns to the network, the buffer status report BSR is triggered but there is no resource for sending the BSR; for example, the terminal does not have physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) resources, or the terminal does not have Resources dedicated to sending the BSR.
  • the terminal when the terminal returns to the network, the buffer status report BSR is triggered but there is no resource for sending the BSR; for example, the terminal does not have physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) resources, or the terminal does not have Resources dedicated to sending the BSR.
  • Physical Uplink Shared Channel Physical Uplink Shared Channel
  • Fourth preset condition when the terminal returns to the network, there is uplink data to be sent, but the uplink data has already triggered the BSR, and there is no resource for sending the uplink data.
  • the resource for sending the uplink data includes a configured grant (configured grant) or a dynamic grant (dynamic grant).
  • the BSR is triggered before the UE leaves the network, and the network can allocate certain transmission resources to the UE based on the BSR. After that, because the UE leaves the network, the network decides to temporarily suspend the configured transmission resources, that is, the UE cannot use these resources for transmission. After the UE returns to the network, these resources are still in the suspended state, and the UE may not be able to trigger the BSR because the triggering conditions of the BSR are not met at this time, so the suspended transmission resources cannot be resumed. In this case, the UE should report to the network. The side sends a return notification.
  • the network configures the terminal to send a return notification
  • the sixth preset condition before the terminal returns to the network, it leaves the network according to the first indication information of the network: an implementation manner is that before the terminal leaves the network, it sends a leaving request to the network side, and the network After receiving, the side sends first indication information, where 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.
  • Seventh preset condition the terminal leaves the network autonomously.
  • the terminal can also avoid sending unnecessary return notifications, and can also let the network know that the terminal has returned to the network, saving network resources.
  • 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.
  • the radio resource control RRC layer of the terminal determines whether to send a return notification to the network.
  • the MAC layer of the terminal determines that the terminal returns to the network; or, the MAC layer of the terminal receives indication information of the RRC layer, and the indication information indicates the The terminal returns to the network.
  • the terminal may be a multi-card terminal, and may reside in multiple networks.
  • the terminal in this embodiment is not limited to a multi-card terminal, and may also be a single-card terminal.
  • the terminal can reside in multiple networks, the multiple networks include 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, and the multi-card terminal is in the connected state in network A, Send a leave notification to network A; after that, the multi-card terminal remains in the RRC connection state in network A, switches to network B to initiate RRC connection or recovery, and processes corresponding services; When processing services, it is decided to return to network A, then the RRC layer of the multi-card terminal instructs the MAC layer that the terminal returns to the network. Once the RRC instruction is received or the MAC judges that the terminal has returned to the network, the MAC layer judges whether to send or not according to whether the preset conditions are met. A return notification is sent to network A, and if the preset conditions are met, a return notification is sent to network A.
  • the multi-card terminal remains in the RRC connected state when the network A is kept in the RRC connected state after sending the leave notification, or it can receive a response message from the network A, and the response message explicitly or implicitly instructs the terminal to stay in the RRC connection state.
  • RRC connected state when the network A is kept in the RRC connected state after sending the leave notification, or it can receive a response message from the network A, and the response message explicitly or implicitly instructs the terminal to stay in the RRC connection state.
  • the method before judging 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.
  • the RRC layer of the terminal determines whether to send a return notification to the network as an example, the multi-card terminal is in the connected state of network A and sends a leaving notification to network A. ; After that, the multi-card terminal remains in the RRC connection state in network A, switches to network B to initiate RRC connection or recovery, and processes the corresponding service; when the service of the multi-card terminal in network B ends and/or there is no service to be processed, decide Returning to network A, the RRC layer of the multi-card terminal instructs the MAC layer to return to the network.
  • the RRC layer When the terminal returns to network A, the RRC layer requests or instructs to resume PDCP; PDCP judges 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 bottom radio link control (Radio Link Control, RLC) protocol layer and/or MAC layer; After the RRC layer receives the PDCP instruction, if no uplink data is indicated to send, the RRC layer generates a return The notification is sent to the MAC layer for transmission.
  • RLC Radio Link Control
  • sending the return notification to the network includes at least one of the following:
  • Trigger a dedicated scheduling request (Scheduling Request, SR), the SR is used to instruct the terminal to return to the network;
  • 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 an instruction to the MAC layer, indicating that the terminal has returned to the network;
  • 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. Before that, the MAC layer receives the return notification generated by the RRC layer from the RRC layer. Further, the RRC layer indicates that the current message content is the return notification;
  • Trigger channel state information (Channel State Information, CSI) reporting or sounding reference signal (Sounding Reference Signal, SRS) transmission.
  • CSI Channel State Information
  • SRS Sounding Reference Signal
  • the BSR when the existing BSR trigger condition may not be satisfied when the terminal returns to the network, it is necessary to introduce a new BSR trigger condition, that is, the BSR is triggered when the terminal returns to the network.
  • the BSR may be any one of a regular BSR, a periodic BSR, an empty BSR, and a Pre-emptive BSR.
  • the empty BSR means that there is no valid data in the BSR.
  • 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 may be referred to as a MAC subheader, and the specific value field may be referred to as a MAC. Protocol data unit.
  • the MAC CE may only include one LCID field, and when the LCID field takes a value of the first preset value, it means that the terminal returns to the network or that the terminal can perform data transmission normally. send and receive.
  • the MAC CE includes an LCID field (the value can be the first preset value) and a numerical field (or a direction field).
  • the LCID field is When the first preset value is set, it means that the UE returns to the network, when the value of the direction field is 1, it means that the UE is ready to receive downlink data, and a value of 0 means that the UE requests the network side to start uplink scheduling.
  • the LCID field may also be replaced with an extended logical channel identifier eLCID.
  • the eLCID field includes a first parameter (eg Codepoint) and a second parameter (eg Index).
  • the BSR satisfies any of the following:
  • the buffer size field does not appear
  • the value of the buffer size field is a preset value, such as 0;
  • the value of the LCID field is a preset value, such as 000;
  • the BSR When the BSR satisfies any of the above items, the BSR represents that the terminal returns to the network.
  • the SR is sent if the terminal has dedicated SR resources.
  • the terminal has PUSCH resources, perform any of the following:
  • 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.
  • the PUSCH resource may be a resource dedicated for the terminal to send the return notification.
  • a random access is initiated, if the UE has a dedicated random access channel (Physical Random Access Channel, RACH) resource, use dedicated RACH resource to perform random access, if not, the UE performs contention RACH.
  • PUCCH Physical Uplink Control Channel
  • CSI reporting or SRS transmission is triggered.
  • the method before judging to send a return notification to the network, the method further includes:
  • a configuration of a first resource of the network is acquired to send the return notification to the network by using the first resource.
  • the configuration of the first resource may be maintained by the existing configuration of the terminal, or may be obtained by the terminal from the network side, for example, the configuration of the first resource is carried in the response message sent by the network A to the notification of leaving the terminal.
  • the first resource includes at least one of the following:
  • the terminal returning to the network includes at least one of the following:
  • the first time is before the end of the gap, and there are T seconds from the end of the gap, and T is specified by the network configuration or protocol;
  • the gap is an autonomous gap determined by the terminal and the network through negotiation or autonomously.
  • the above gap can be understood as a period of time or a period of time that occurs periodically. During this period of time, the terminal does not monitor scheduling or send and receive data on the current network (eg, network A), but switches to other networks to perform certain services. At or after the end of the gap, the terminal should return to network A and start to resume monitoring scheduling or start sending and receiving data.
  • 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 cycle, The purpose of the gap (for Multi-SIM purpose), the addition or modification or release of the gap configuration.
  • the UE when the UE receives an RRC release message in network A or the UE releases the RRC connection locally, or when the UE enters the RRC idle or inactive state, the UE does not send the busy indication information, or the UE Discard the generated busy indication information, which includes the following steps:
  • Step 1 UE is in connected state in network A;
  • Step 2 UE receives the paging message at network B;
  • Step 3 The UE decides to send a busy indication on the network B, for example, the UE determines that the service of the network A is important and/or the service of the network B is not a voice service, the UE decides to notify the network B, and the UE will go to the network A to process the service in the future;
  • Step 4 The UE sends a leave request on network A or applies for a gap to network A for switching to network B to send a busy indication;
  • Step 5 UE receives the connection release message sent by network A;
  • Step 6 The UE does not send the busy indication to the network B, or if the busy indication has been generated, the UE discards the busy indication;
  • Step 7 The UE may initiate an RRC connection in network B.
  • the execution subject may be a notification device for returning to the network, or a module in the notification device for returning to the network for executing the notification method for loading the returning network.
  • the method for notifying the returning network provided by the embodiment of the present application is described by taking the notifying method for returning to the network performing the loading and returning to the network as an example.
  • the embodiment of the present application provides a notification device for returning to the network, which is applied to the terminal 300.
  • the device includes:
  • Judging module 310 for judging whether to send a return notification to the network
  • the sending module 320 is configured to send the return notification to the network if it is determined to send the return notification to the network.
  • the terminal determines whether to send a return notification to the network, and if it determines to send the return notification to the network, the terminal sends the return notification to the network, so that the terminal can timely and effectively notify the network side that the terminal has Returning to the network enables the terminal to receive or send data normally.
  • 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.
  • the judging module is specifically configured to judge 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:
  • the first preset condition when the terminal returns to the network, there is no uplink data and/or signaling to be sent;
  • the first preset condition is determined based on at least one of the following:
  • 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 can be understood that there may also be a request and response process between different protocol layers of the terminal.
  • 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 buffer).
  • the MAC layer of the terminal sends indication information to the RRC layer.
  • at least one of SDAP, PDCP, RRC, MAC, and PHY of the terminal is restored or restarted, and new uplink data is generated after the restoration or restart.
  • the second preset condition when the terminal returns to the network, no buffer status report BSR is triggered;
  • the third preset condition when the terminal returns to the network, the buffer status report BSR is triggered but there is no resource for sending the BSR; for example, the terminal does not have PUSCH resources, or the terminal does not have resources dedicated to sending the BSR.
  • Fourth preset condition when the terminal returns to the network, there is uplink data to be sent, but the uplink data has already triggered the BSR, and there is no resource for sending the uplink data;
  • the resource for sending the uplink data includes a configured grant (configured grant) or a dynamic grant (dynamic grant).
  • the BSR is triggered before the UE leaves the network, and the network can allocate certain transmission resources to the UE based on the BSR. After that, because the UE leaves the network, the network decides to temporarily suspend the configured transmission resources, that is, the UE cannot use these resources for transmission. After the UE returns to the network, these resources are still in the suspended state, and the UE may not be able to trigger the BSR because the triggering conditions of the BSR are not met at this time, so the suspended transmission resources cannot be resumed. In this case, the UE should report to the network. The side sends a return notification.
  • the network configures the terminal to send a return notification
  • the sixth preset condition before the terminal returns to the network, it leaves the network according to the first indication information of the network: an implementation manner is that before the terminal leaves the network, it sends a leaving request to the network side, and the network After receiving, the side sends first indication information, where 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.
  • Seventh preset condition the terminal leaves the network autonomously.
  • the terminal can specify under what circumstances the terminal should send a return notification, so that the terminal can timely and effectively notify the network side that the terminal has returned to the network, so that the terminal can receive or send data normally.
  • the terminal can also avoid sending unnecessary return notifications, and can also let the network know that the terminal has returned to the network, saving network resources.
  • the sending module is specifically configured to perform at least one of the following:
  • 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
  • Trigger CSI reporting or SRS transmission Trigger CSI reporting or SRS transmission.
  • the existing BSR trigger condition may not be satisfied when the terminal returns to the network, so it is necessary to introduce a new BSR trigger condition, that is, the BSR is triggered when the terminal returns to the network.
  • the BSR may be any one of a regular BSR, a periodic BSR, an empty BSR, and a Pre-emptive BSR.
  • the empty BSR means that there is no valid data in the BSR.
  • 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 may be referred to as a MAC subheader, and the specific value field may be referred to as a MAC. Protocol data unit.
  • the MAC CE may only include one LCID field, and when the LCID field takes a value of the first preset value, it means that the terminal returns to the network or that the terminal can perform data transmission normally. send and receive.
  • the MAC CE includes an LCID field (the value can be the first preset value) and a numerical field (or a direction field).
  • the LCID field is When the first preset value is set, it means that the UE returns to the network, when the value of the direction field is 1, it means that the UE is ready to receive downlink data, and a value of 0 means that the UE requests the network side to start uplink scheduling.
  • the LCID field may also be replaced with an extended logical channel identifier eLCID.
  • the eLCID field includes a first parameter (eg Codepoint) and a second parameter (eg Index).
  • the BSR satisfies any of the following:
  • the buffer size field does not appear
  • the value of the buffer size field is the default value
  • the value of the LCID field is the default value
  • the sending module is specifically configured to send the SR if the terminal has dedicated SR resources.
  • the sending module is specifically configured to perform any one of the following if the terminal has PUSCH resources:
  • 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.
  • the PUSCH resource may be a resource dedicated for the terminal to send the return notification.
  • the sending module is specifically configured to initiate random access if the terminal does not have available PUSCH resources and/or PUCCH resources, and use the dedicated RACH resources if the UE has dedicated random access channel (RACH) resources. Perform random access, if not, the UE performs contention RACH.
  • RACH random access channel
  • the sending module is specifically configured to trigger CSI reporting or SRS sending if the terminal has dedicated resources for reporting CSI or SRS.
  • the apparatus further includes a processing module configured to perform at least one of the following:
  • the PDCP layer of the terminal is requested to indicate whether there is uplink data to be sent.
  • the apparatus further includes:
  • an obtaining module configured to obtain the configuration of the first resource of the network, so as to send the return notification to the network by using the first resource.
  • the first resource includes at least one of the following:
  • the terminal returning to the network includes at least one of the following:
  • the first time is before the end of the gap, and there are T seconds from the end of the gap, and T is specified by the network configuration or protocol;
  • the gap is an autonomous gap determined by the terminal and the network through negotiation or autonomously.
  • the above gap can be understood as a period of time or a period of time that occurs periodically. During this period of time, the terminal does not monitor scheduling or send and receive data on the current network (eg, network A), but switches to other networks to perform certain services. At or after the end of the gap, the terminal should return to network A and start to resume monitoring scheduling or start sending and receiving data.
  • 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 cycle, The purpose of the gap (for Multi-SIM purpose), the addition or modification or release of the gap configuration.
  • the notification device for returning to the network may be a device, or may be a component, an integrated circuit, or a chip in a terminal.
  • the apparatus may be a mobile electronic device or a non-mobile electronic device.
  • the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (personal digital assistant).
  • UMPC ultra-mobile personal computer
  • netbook or a personal digital assistant
  • the non-mobile electronic device may be a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., the embodiment of the present application There is no specific limitation.
  • Network Attached Storage NAS
  • personal computer personal computer, PC
  • television television
  • teller machine a self-service machine
  • the notification device for returning to the network in the embodiment of the present application may be a device having an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • an embodiment of the present application further provides a terminal, including a processor, a memory, a program or an instruction stored in the memory and executable on the processor, and the above-mentioned return is realized when the program or instruction is executed by the processor.
  • a terminal including a processor, a memory, a program or an instruction stored in the memory and executable on the processor, and the above-mentioned return is realized when the program or instruction is executed by the processor.
  • the terminal in this embodiment of the present application includes the mobile electronic device and the non-mobile electronic device described above.
  • 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, The user input unit 57 , the interface unit 58 , the memory 59 , the processor 510 , and the power supply 511 and other components.
  • the terminal structure shown in FIG. 7 does not constitute a limitation on the terminal, and the terminal may include more or less components than the one shown, or combine some components, or arrange different components.
  • the terminals include but are not limited to mobile phones, tablet computers, notebook computers, handheld computers, vehicle-mounted terminals, wearable devices, and pedometers.
  • the radio frequency unit 51 may be used for receiving and sending signals in the process of sending and receiving information or during a call. Specifically, after receiving the downlink data from the base station, it is processed by the processor 510; The uplink data is sent to the base station.
  • the radio frequency 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.
  • the radio frequency unit 51 can also communicate with the network and other devices through a wireless communication system.
  • the memory 59 may be used to store software programs as well as various data.
  • the memory 59 may mainly include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program (such as a sound playback function, an image playback function, etc.) required for at least one function, and the like; Data created by the use of the mobile phone (such as audio data, phone book, etc.), etc.
  • memory 59 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
  • the processor 510 is the control center of the terminal, uses various interfaces and lines to connect various parts of the entire terminal, and executes by running or executing the software programs and/or modules stored in the memory 59, and calling the data stored in the memory 59. Various functions of the terminal and processing data, so as to monitor the terminal as a whole.
  • the processor 510 may include one or at least two processing units; preferably, the processor 510 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, etc., and the modem
  • the modulation processor mainly handles wireless communication. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 510.
  • the terminal 50 may also include a power supply 511 (such as a battery) for supplying power to various components.
  • a power supply 511 (such as a battery) for supplying power to various components.
  • the power supply 511 may be logically connected to the processor 510 through a power management system, so as to manage charging, discharging, and power consumption management through the power management system. Function.
  • the terminal 50 includes some unshown functional modules, which are not repeated here.
  • the processor 510 is configured to determine whether to send the 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.
  • the processor 510 is specifically configured to determine 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:
  • the first preset condition when the terminal returns to the network, there is no uplink data and/or signaling to be sent;
  • the second preset condition when the terminal returns to the network, no buffer status report BSR is triggered;
  • the third preset condition when the terminal returns to the network, the buffer status report BSR is triggered but there is no resource for sending the BSR;
  • Fourth preset condition when the terminal returns to the network, there is uplink data to be sent, but the uplink data has already triggered the BSR, and there is no resource for sending the uplink data;
  • the network configures the terminal to send a return notification
  • the sixth preset condition before returning to the network, the terminal leaves the network according to the first indication information of the network:
  • Seventh preset condition the terminal leaves the network autonomously.
  • 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.
  • the RRC layer of the terminal determines whether to send a return notification to the network.
  • the processor 510 sends the return notification to the network, including at least one of the following:
  • 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
  • Trigger CSI reporting or SRS transmission Trigger CSI reporting or SRS transmission.
  • the MAC CE includes a specific LCID field and/or a specific value field.
  • the BSR satisfies any of the following:
  • the buffer size field does not appear
  • the value of the buffer size field is the default value
  • the value of the LCID field is the default value
  • the radio frequency unit 51 is configured to send the SR if the terminal has dedicated SR resources.
  • the processor 510 is configured to perform any one of the following if the terminal has PUSCH resources:
  • 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.
  • the processor 510 is configured to initiate random access if the terminal does not have available PUSCH resources and/or PUCCH resources.
  • the processor 510 is configured to trigger CSI reporting or SRS transmission if the terminal has dedicated resources for reporting CSI or SRS.
  • the processor 510 is further configured to perform 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.
  • the radio frequency unit 51 is further configured to acquire the configuration of the first resource of the network, so as to send the return notification to the network by using the first resource.
  • the first resource includes at least one of the following:
  • the first preset condition is determined based on at least one of the following:
  • 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.
  • the terminal returning to the network includes at least one of the following:
  • the first time is before the end of the gap, and there are T seconds from the end of the gap, and T is specified by the network configuration or protocol;
  • Embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the above-mentioned embodiment of the method for notifying a network return is implemented, and The same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.
  • the processor is the processor in the electronic device described in the foregoing embodiments.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the above-mentioned notification method of returning to the network.
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is configured to run a program or an instruction to implement the above-mentioned notification method of returning to the network.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip, or the like.
  • the terms “comprising”, “comprising” or any other variation thereof are intended to encompass a non-exclusive inclusion, such that a process, method, article or device that includes a list of elements does not include those elements, It also includes other elements not expressly listed or inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase “comprising a" does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.
  • the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in the reverse order depending on the functions involved. To perform functions, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to some examples may be combined in other examples.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开一种返回网络的通知方法、装置及终端,属于通信技术领域。一种返回网络的通知方法,由终端执行,所述方法包括:判断是否向网络发送返回通知;若判断向所述网络发送所述返回通知,向所述网络发送所述返回通知。

Description

返回网络的通知方法、装置及终端
相关申请的交叉引用
本申请主张在2021年01月15日在中国提交的中国专利申请No.202110057640.6的优先权,其全部内容通过引用包含于此。
技术领域
本申请涉及通信技术领域,尤其涉及一种返回网络的通知方法、装置及终端。
背景技术
目前市场上不仅存在单卡终端,还存在双卡或多卡终端,统称多卡终端。多卡终端的能力可以是单发单收、单发双收和双发双收等。
多卡终端的一个特点是可以在多个网络同时驻留,但是不同多卡终端的实现方式不同,有的多卡终端可以在多个网络同时发送和接收互不影响。而有的多卡终端可以在多个网络同时驻留但是可能采用时分的方式在两个网络驻留,也就是一段时间在网络A驻留听网络A的paging,一段时间在网络B驻留听网络B的paging;或者一段时间在网络A处于连接态收发数据,而一段时间要到网络B接收paging;或者一段时间在网络A收发数据,而一段时间要到网络B上建立连接进行数据的收发。
多卡终端在网络A处于连接态,可能会离开网络A切换到网络B执行某些业务。当多卡终端准备从网络A切换到网络B时,可向网络A发送离开通知,使得网络A收到多卡终端发送的离开通知后,可以避免在这段时间内调度或寻呼多卡终端,从而节省网络资源。
目前,多卡终端返回网络时如何通知网络尚不明确,这样可能会使得UE无法通知网络侧UE已返回网络,从而导致UE一直无法接收或发送数据,或者在某些条件下UE发送不必要的通知,浪费网络资源。
发明内容
本申请实施例提供了一种返回网络的通知方法、装置及终端,能够解决UE无法通知网络侧UE已返回网络,从而导致UE一直无法接收或发送数据或者在某些条件下UE发送不必要的通知的问题。
第一方面,本申请实施例提供了一种返回网络的通知方法,由终端执行,所述方法包括:
判断是否向网络发送返回通知;
若判断向所述网络发送所述返回通知,向所述网络发送所述返回通知。
第二方面,本申请实施例提供了一种返回网络的通知装置,应用于终端,所述装置包括:
判断模块,用于判断是否向网络发送返回通知;
发送模块,用于若判断向所述网络发送所述返回通知,向所述网络发送所述返回通知。
第三方面,本申请实施例还提供了一种终端,包括处理器,存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如上所述的返回网络的通知方法的步骤。
第四方面,本申请实施例提供了一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如上所述的返回网络的通知方法的步骤。
第五方面,本申请实施例提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现如第一方面所述的方法。
第六方面,提供了一种计算机程序产品,所述计算机程序产品被存储在非易失的存储介质中,所述计算机程序产品被至少一个处理器执行以实现如第一方面所述的方法。
在本申请实施例中,终端判断是否向网络发送返回通知,若判断向所述网络发送所述返回通知,终端向所述网络发送所述返回通知,这样终端可以及时有效地通知网络侧终端已返回网络,能够使得终端正常接收或发送数据。 在某些条件下,例如,终端的其他行为被触发导致上行发送时,终端还可以避免发送不必要的返回通知也可以让网络知道所述终端已返回网络,节省网络资源。
附图说明
为了更清楚地说明本申请实施例的技术方案,下面将对本申请实施例的描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1表示无线通信系统的示意图;
图2表示BSR的格式示意图;
图3表示本申请实施例返回网络的通知方法的流程示意图;
图4和图5表示本申请实施例MAC CE的格式示意图;
图6表示本申请实施例返回网络的通知装置的结构示意图;
图7表示本申请实施例的终端的组成示意图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚地描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员所获得的所有其他实施例,都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换,以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外,说明书以及权利要求中“和/或”表示所连接对象的至少其中之一,字符“/”,一般表示前后关联对象是一种“或”的关系。
本文所描述的技术不限于长期演进型(Long Term Evolution,LTE)/LTE的演进(LTE-Advanced,LTE-A)系统,并且也可用于各种无线通信系统,诸如码分多址(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)和其他系统。术语“系统”和“网络”常被可互换地使用。CDMA系统可实现诸如CDMA2000、通用地面无线电接入(Universal Terrestrial Radio Access,UTRA)等无线电技术。UTRA包括宽带CDMA(Wideband Code Division Multiple Access,WCDMA)和其他CDMA变体。TDMA系统可实现诸如全球移动通信系统(Global System for Mobile Communication,GSM)之类的无线电技术。OFDMA系统可实现诸如超移动宽带(UltraMobile Broadband,UMB)、演进型UTRA(Evolution-UTRA,E-UTRA)、IEEE802.11(Wi-Fi)、IEEE 802.16(WiMAX)、IEEE 802.20、Flash-OFDM等无线电技术。UTRA和E-UTRA是通用移动电信系统(Universal Mobile Telecommunications System,UMTS)的部分。LTE和更高级的LTE(如LTE-A)是使用E-UTRA的新UMTS版本。UTRA、E-UTRA、UMTS、LTE、LTE-A以及GSM在来自名为“第三代伙伴项目”(3rd Generation Partnership Project,3GPP)的组织的文献中描述。CDMA2000和UMB在来自名为“第三代伙伴项目2”(3GPP2)的组织的文献中描述。本文所描述的技术既可用于以上提及的系统和无线电技术,也可用于其他系统和无线电技术。以下描述出于示例目的描述了NR系统,并且在以下大部分描述中使用NR术语,但是这些技术也可应用于NR系统应用以外的应用。
以下描述提供示例而并非限定权利要求中阐述的范围、适用性或者配置。可以对所讨论的要素的功能和布置作出改变而不会脱离本公开的精神和范围。各种示例可恰适地省略、替代、或添加各种规程或组件。例如,可以按不同于所描述的次序来执行所描述的方法,并且可以添加、省去、或组合各种步 骤。另外,参照某些示例所描述的特征可在其他示例中被组合。
请参见图1,图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中,终端11也可以称作终端设备或者用户终端(User Equipment,UE),终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数字助理(Personal Digital Assistant,PDA)、移动上网装置(Mobile Internet Device,MID)、可穿戴式设备(Wearable Device)或车载设备等终端侧设备,需要说明的是,在本申请实施例中并不限定终端11的具体类型。网络侧设备12可以是基站或核心网,其中,上述基站可以是5G及以后版本的基站(例如:gNB、5G NR NB等),或者其他通信系统中的基站(例如:eNB、WLAN接入点、或其他接入点等),或者为位置服务器(例如:E-SMLC或LMF(Location Manager Function)),其中,基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station,BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set,BSS)、扩展服务集(Extended Service Set,ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点或所述领域中其他某个合适的术语,只要达到相同的技术效果,所述基站不限于特定技术词汇,需要说明的是,在本申请实施例中仅以NR系统中的基站为例,但是本申请实施例并不限定基站的具体类型和具体通信系统。
目前市场上不仅存在单卡终端,还存在双卡或多卡终端,统称多卡终端。多卡终端的能力可以是单发单收、单发双收和双发双收等。
多卡终端的一个特点是可以在多个网络同时驻留,多卡终端在网络A处于连接态,可能会离开网络A切换到网络B执行某些业务。当多卡终端准备从网络A切换到网络B时,可向网络A发送离开通知,使得网络A收到多卡终端发送的离开通知后,可以避免在这段时间内调度或寻呼多卡终端,从而节省网络资源。
当UE有缓存的上行数据要发送时,可发送缓存状态报告(Buffer state  report,BSR)给网络侧,其中指示一个或多个逻辑信道组的buffer size(即待传输的数据量)。网络侧可以根据BSR里指示的数据量的大小为UE分配合适大小的上行资源,供UE进行上行传输。BSR包括短(short)BSR format,long BSR format,短截型(short Truncated)BSR format,长截型(Long Truncated)BSR format,优先(Pre-emptive)BSR format5种,现有BSR的格式如图2所示。其中,LCG ID为逻辑信道组(Logical Channel Group,LCG)ID,buffer size为对应LCG ID的待传输的数据量,MAC CE为媒体接入控制(Medium Access Control,MAC)控制信令(Control Element,CE)。
本申请实施例提供了一种返回网络的通知方法,由终端执行,如图3所示,包括:
步骤101:判断是否向网络发送返回通知;
步骤102:若判断向所述网络发送所述返回通知,向所述网络发送所述返回通知。
本实施例中,终端判断是否向网络发送返回通知,若判断向所述网络发送所述返回通知,终端向所述网络发送所述返回通知,这样终端可以及时有效地通知网络侧终端已返回网络,能够使得终端正常接收或发送数据。在某些条件下,例如,终端的其他行为被触发导致上行发送时,终端还可以避免发送不必要的返回通知也可以让网络知道所述终端已返回网络,节省网络资源。
一些实施例中,判断是否向网络发送返回通知,包括:
在满足预设条件时,判断向所述网络发送所述返回通知,所述预设条件包括以下至少一项:
第一预设条件:所述终端返回所述网络时没有待发送的上行数据和/或信令;
其中,所述第一预设条件为基于以下至少一项确定:
所述终端的MAC层的指示、所述终端的无线资源控制(Radio Resource Control,RRC)层的指示、所述终端的服务数据适配协议(Service Data  Adaptation Protocol,SDAP)层的指示、所述终端的(Packet Data Convergence Protocol,PDCP)层的指示、所述终端的物理层(Physical,PHY)的指示。可以理解的是,所述终端的不同协议层之间还可以存在请求和响应过程。例如,所述终端的RRC层请求所述终端的MAC层指示所述终端当前是否有待发送的上行数据或信令(例如,缓存中有数据)。在有上行数据或信令要发送的情况下,所述终端的MAC层向RRC层发送指示信息。一种实施方式中,所述终端返回网络时,恢复或者重启所述终端的SDAP、PDCP、RRC、MAC、PHY中至少之一,在恢复或重启后,产生了新的上行数据。
第二预设条件:所述终端返回所述网络时没有缓存状态报告(Buffer Status Report,BSR)被触发;
第三预设条件:所述终端返回所述网络时缓存状态报告BSR被触发但是没有发送所述BSR的资源;例如,终端没有物理上行共享信道(Physical Uplink Shared Channel,PUSCH)资源,或者终端没有专门用于发送所述BSR的资源。
第四预设条件:所述终端返回所述网络时有待发送的上行数据但所述上行数据已经触发过BSR,且没有发送所述上行数据的资源。
其中,发送所述上行数据的资源包括配置授权(configured grant)或动态的授权(dynamic grant)。例如,UE离开网络前触发过BSR,网络可以基于BSR为UE分配一定的传输资源,之后由于UE离开网络,网络决定将所配置的传输资源暂时挂起,即UE无法使用这些资源进行传输,当UE返回网络后,这些资源仍处于挂起状态,而UE此时可能因为不满足BSR的触发条件而无法触发BSR,从而无法恢复被挂起的传输资源,在这种情况下,UE应该向网络侧发送返回通知。
第五预设条件:所述网络配置所述终端发送返回通知;
第六预设条件:所述终端返回所述网络前,根据所述网络的第一指示信息离开所述网络:一种实施方式为,所述终端离开网络前,向网络侧发送离开请求,网络侧收到后发送第一指示信息,第一指示信息可以用于响应所述 离开请求、或配置终端在返回网络时所需的资源。
第七预设条件:所述终端自主离开所述网络。
本实施例中,通过设置预设条件,可以明确终端在何种情况下应当发送返回通知,使得终端可以及时有效地通知网络侧终端已返回网络,能够使得终端正常接收或发送数据,在某些条件下,例如,终端的其他行为被触发导致上行发送时,终端还可以避免发送不必要的返回通知也可以让网络知道所述终端已返回网络,节省网络资源。
一些实施例中,判断是否向网络发送返回通知,包括:
所述终端的MAC层判断是否向网络发送返回通知;或
所述终端的无线资源控制RRC层判断是否向网络发送返回通知。
一具体示例中,判断是否向网络发送返回通知之前,所述终端的MAC层判断所述终端返回所述网络;或者,所述终端的MAC层接收RRC层的指示信息,所述指示信息指示所述终端返回所述网络。
本实施例中,终端可以为多卡终端,可以驻留在多个网络。但本实施例的终端并不局限为多卡终端,还可以为单卡终端。
一具体实施例中,以终端可以驻留在多个网络,多个网络包括网络A和网络B,终端的MAC层判断是否向网络发送返回通知为例,多卡终端在网络A为连接态,向网络A发送离开通知;之后多卡终端在网络A保持在RRC连接态,切换到网络B发起RRC连接或恢复,处理相应的业务;当多卡终端在网络B的业务结束和/或没有要处理的业务时,决定返回网络A,则多卡终端的RRC层向MAC层指示终端返回网络,一旦收到RRC的指示或MAC判断终端已返回网络,MAC层根据是否满足预设条件判断是否发送向网络A发送返回通知,如果满足预设条件,则向网络A发送返回通知。
其中,多卡终端在网络A保持在RRC连接态可以是发送离开通知后保持在RRC连接态,也可以是收到了网络A的响应消息,且该响应消息显式或隐式地指示终端保持在RRC连接态。
另一具体实施例中,判断是否向所述网络发送返回通知之前,所述方法 还包括以下至少一项:
所述终端的RRC层请求或指示恢复所述终端的分组数据汇聚协议PDCP层;
所述终端的RRC层请求所述终端的PDCP层指示是否有上行数据待发送。
以终端可以驻留在多个网络,多个网络包括网络A和网络B,终端的RRC层判断是否向网络发送返回通知为例,多卡终端在网络A为连接态,向网络A发送离开通知;之后多卡终端在网络A保持在RRC连接态,切换到网络B发起RRC连接或恢复,处理相应的业务;当多卡终端在网络B的业务结束和/或没有要处理的业务时,决定返回网络A,则多卡终端的RRC层向MAC层指示终端返回网络,终端回到网络A时,RRC层请求或指示恢复PDCP;PDCP判断是否有上行数据,并向RRC层指示是否有上行数据;若有上行数据,PDCP还向底层无线链路控制(Radio Link Control,RLC)协议层和/或MAC层发送数据;RRC层收到PDCP指示后,若指示无上行数据发送,RRC层生成返回通知,发送给MAC层进行传输。
一些实施例中,判断向所述网络发送所述返回通知后,向所述网络发送所述返回通知,包括以下至少一项:
生成或触发BSR;
生成MAC控制元素CE,所述MAC CE用于指示所述终端返回所述网络;
触发专用调度请求(Scheduling Request,SR),该SR用于指示所述终端返回所述网络;
所述终端的MAC层请求RRC层生成所述返回通知,在这之前,RRC层向MAC层发送请求或指示,指示终端已返回网络;
所述终端的RRC层请求MAC层生成所述返回通知;
所述RRC层生成所述返回通知;
所述终端的MAC层发送RRC层生成的所述返回通知,在这之前,MAC层从RRC层接收RRC层生成的返回通知,进一步地,RRC层指示当前的消息内容为返回通知;
发起随机接入;
触发信道状态信息(Channel State Information,CSI)上报或探测参考信号(Sounding Reference Signal,SRS)发送。
一些实施例中,当终端返回网络时现有的BSR触发条件可能不满足时,因此有必要引入新的BSR触发条件,即当终端返回网络时触发BSR。其中,BSR可以是常规BSR、周期性BSR、空BSR、Pre-emptive BSR中任意一个。其中空BSR表示BSR中没有有效的数据。
一些实施例中,用以指示所述终端返回所述网络的所述MAC CE包括特定LCID域和/或特定数值域,其中,LCID域可以称为MAC子头部,特定数值域可以称为MAC协议数据单元。
一具体示例中,如图4所示,MAC CE可以仅包括一个LCID域,当该LCID域取值为第一预设值时,表示所述终端返回网络或表示所述终端可以正常进行数据的收发。
另一具体示例中,如图5所示,MAC CE包括一个LCID域(取值可为第一预设值)和一个数值域(或者方向域),当收到该MAC CE,若LCID域为第一预设值时,表示UE返回网络,方向域值为1时表示UE准备好接收下行数据,值为0表示UE请求网络侧开始上行调度。
在另一些实施例中,LCID域还可以被替换为扩展逻辑信道标识eLCID。所述eLCID域包含第一参数(如Codepoint)和第二参数(如Index)。
一些实施例中,所述BSR满足以下任一项:
buffer size域不出现;
buffer size域的值为预设值,比如为0;
LCID域的值为预设值,比如为000;
BSR为空;
当BSR满足以上任一项时,该BSR代表终端返回网络。
一些实施例中,若所述终端存在专用SR资源,发送SR。
一些实施例中,若所述终端有PUSCH资源,执行以下任一项:
发送所述BSR;
发送所述MAC CE;
所述RRC层生成所述返回通知;
所述终端的MAC层请求RRC层生成所述返回通知;
所述终端的RRC层请求MAC层生成所述返回通知;
所述终端的MAC层发送RRC层生成的所述返回通知。
一些实施例中,所述PUSCH资源可以是专用于终端发送所述返回通知的资源。
一些实施例中,若所述终端没有可用的PUSCH资源和/或物理上行控制信道(Physical Uplink Control Channel,PUCCH)资源,发起随机接入,若UE有专用随机接入信道(Physical Random Access Channel,RACH)资源,则使用专用RACH资源执行随机接入,若没有,UE执行竞争RACH。
一些实施例中,若所述终端有上报CSI或SRS的专用资源,触发CSI上报或SRS发送。
一些实施例中,判断向所述网络发送返回通知之前,所述方法还包括:
获取所述网络的第一资源的配置,以利用所述第一资源向所述网络发送所述返回通知。第一资源的配置可以是保持终端现有配置,还可以是终端从网络侧获取的,例如网络A发送对终端离开通知的响应消息中携带第一资源的配置。
一些实施例中,所述第一资源包括以下至少一项:
configured grant类型type1;
configured grant type2;
物理上行共享信道PUSCH资源;
物理上行控制信道PUCCH资源;
专用调度请求SR资源;
专用随机接入信道RACH资源;
专用探测参考信号SRS资源;
专用信道状态信息CSI上报资源。
一些实施例中,所述终端返回所述网络包括以下至少一项:
在间隙gap结束之前返回所述网络或未约定gap长度而返回所述网络;
在第一时刻或第一时刻之前返回所述网络,所述第一时刻在gap结束之前,且距离gap结束有T秒,T由网络配置或者协议约定;
在所述网络调度的gap结束之后返回所述网络。
其中,所述gap为所述终端和所述网络协商确定或自主Autonomous gap。
上述gap可以理解为一段时间或者周期性出现的一段时间,在这段时间内终端不在当前网络(例如网络A)监听调度或进行数据的收发,而是切换到其他网络执行某些业务。在gap结束时或之后,终端应该返回网络A,开始恢复监听调度或者开始进行数据的收发。Gap可以由终端上报给网络,也可以由网络配置给终端,其中gap可以包含以下至少一项:时间长度duration/length,开始时间(gap start time),结束时间(gap end time),gap周期,gap的用途(for Multi-SIM purpose),gap配置的添加或修改或释放。
一具体实施例中,当UE在网络A收到RRC释放消息或者UE本地释放RRC连接,或者UE进入了RRC空闲(idle)或非激活(inactive)态时,UE不发送繁忙指示信息,或者UE丢弃已经生成的繁忙指示信息,具体包括以下步骤:
步骤1:UE在网络A处于连接态;
步骤2:UE在网络B收到了寻呼消息;
步骤3:UE决定在网络B发送繁忙指示,例如,UE判断网络A的业务重要和/或网络B的业务不是语音业务,UE决定通知网络B,UE在未来一段时间内去网络A处理业务;
步骤4:UE在网络A发送离开请求或者向网络A申请了一个gap,用于切换到网络B发送繁忙指示;
步骤5:UE收到了网络A发送的连接释放消息;
步骤6:UE不向网络B发送繁忙指示,或者如果繁忙指示已经生成时, UE丢弃繁忙指示;
步骤7:UE可以在网络B发起RRC连接。
需要说明的是,本申请实施例提供的返回网络的通知方法,执行主体可以为返回网络的通知装置,或者该返回网络的通知装置中的用于执行加载返回网络的通知方法的模块。本申请实施例中以返回网络的通知装置执行加载返回网络的通知方法为例,说明本申请实施例提供的返回网络的通知方法。
本申请实施例提供了一种返回网络的通知装置,应用于终端300,如图6所示,所述装置包括:
判断模块310,用于判断是否向网络发送返回通知;
发送模块320,用于若判断向所述网络发送所述返回通知,向所述网络发送所述返回通知。
在本申请实施例中,终端判断是否向网络发送返回通知,若判断向所述网络发送所述返回通知,终端向所述网络发送所述返回通知,这样终端可以及时有效地通知网络侧终端已返回网络,能够使得终端正常接收或发送数据。在某些条件下,例如,终端的其他行为被触发导致上行发送时,终端还可以避免发送不必要的返回通知也可以让网络知道所述终端已返回网络,节省网络资源。
一些实施例中,所述判断模块具体用于在满足预设条件时,判断向所述网络发送所述返回通知,所述预设条件包括以下至少一项:
第一预设条件:所述终端返回所述网络时没有待发送的上行数据和/或信令;
一些实施例中,所述第一预设条件为基于以下至少一项确定:
所述终端的MAC层的指示、所述终端的RRC层的指示、所述终端的服务数据适配协议SDAP层的指示、所述终端的PDCP层的指示、所述终端的物理层的指示。可以理解的是,所述终端的不同协议层之间还可以存在请求和响应过程。例如,所述终端的RRC层请求所述终端的MAC层指示所述终端当前是否有待发送的上行数据或信令(例如,缓存中有数据)。在有上行数 据或信令要发送的情况下,所述终端的MAC层向RRC层发送指示信息。一种实施方式中,所述终端返回网络时,恢复或者重启所述终端的SDAP、PDCP、RRC、MAC、PHY中至少之一,在恢复或重启后,产生了新的上行数据。
第二预设条件:所述终端返回所述网络时没有缓存状态报告BSR被触发;
第三预设条件:所述终端返回所述网络时缓存状态报告BSR被触发但是没有发送所述BSR的资源;例如,终端没有PUSCH资源,或者终端没有专门用于发送所述BSR的资源。
第四预设条件:所述终端返回所述网络时有待发送的上行数据但所述上行数据已经触发过BSR,且没有发送所述上行数据的资源;
其中,发送所述上行数据的资源包括配置授权(configured grant)或动态的授权(dynamic grant)。例如,UE离开网络前触发过BSR,网络可以基于BSR为UE分配一定的传输资源,之后由于UE离开网络,网络决定将所配置的传输资源暂时挂起,即UE无法使用这些资源进行传输,当UE返回网络后,这些资源仍处于挂起状态,而UE此时可能因为不满足BSR的触发条件而无法触发BSR,从而无法恢复被挂起的传输资源,在这种情况下,UE应该向网络侧发送返回通知。
第五预设条件:所述网络配置所述终端发送返回通知;
第六预设条件:所述终端返回所述网络前,根据所述网络的第一指示信息离开所述网络:一种实施方式为,所述终端离开网络前,向网络侧发送离开请求,网络侧收到后发送第一指示信息,第一指示信息可以用于响应所述离开请求、或配置终端在返回网络时所需的资源。
第七预设条件:所述终端自主离开所述网络。
本实施例中,通过设置预设条件,可以明确终端在何种情况下应当发送返回通知,使得终端可以及时有效地通知网络侧终端已返回网络,能够使得终端正常接收或发送数据,在某些条件下,例如,终端的其他行为被触发导致上行发送时,终端还可以避免发送不必要的返回通知也可以让网络知道所述终端已返回网络,节省网络资源。
一些实施例中,所述发送模块具体用于执行以下至少一项:
生成或触发BSR;
生成MAC控制元素CE,所述MAC CE用于指示所述终端返回所述网络;
触发SR;
所述终端的MAC层请求RRC层生成所述返回通知;
所述终端的RRC层请求MAC层生成所述返回通知;
所述RRC层生成所述返回通知;
所述终端的MAC层发送RRC层生成的所述返回通知;
发起随机接入;
触发CSI上报或SRS发送。
一些实施例中,当终端返回网络时现有的BSR触发条件可能不满足,因此有必要引入新的BSR触发条件,即当终端返回网络时触发BSR。其中,BSR可以是常规BSR、周期性BSR、空BSR、Pre-emptive BSR中任意一个。其中空BSR表示BSR中没有有效的数据。
一些实施例中,用以指示所述终端返回所述网络的所述MAC CE包括特定LCID域和/或特定数值域,其中,LCID域可以称为MAC子头部,特定数值域可以称为MAC协议数据单元。
一具体示例中,如图4所示,MAC CE可以仅包括一个LCID域,当该LCID域取值为第一预设值时,表示所述终端返回网络或表示所述终端可以正常进行数据的收发。
另一具体示例中,如图5所示,MAC CE包括一个LCID域(取值可为第一预设值)和一个数值域(或者方向域),当收到该MAC CE,若LCID域为第一预设值时,表示UE返回网络,方向域值为1时表示UE准备好接收下行数据,值为0表示UE请求网络侧开始上行调度。
在另一些实施例中,LCID域还可以被替换为扩展逻辑信道标识eLCID。所述eLCID域包含第一参数(如Codepoint)和第二参数(如Index)。
一些实施例中,所述BSR满足以下任一项:
buffer size域不出现;
buffer size域的值为预设值;
LCID域的值为预设值;
BSR为空。
一些实施例中,所述发送模块具体用于若所述终端存在专用SR资源,发送SR。
一些实施例中,所述发送模块具体用于若所述终端有PUSCH资源,执行以下任一项:
发送所述BSR;
发送所述MAC CE;
所述RRC层生成所述返回通知;
所述终端的MAC层请求RRC层生成所述返回通知;
所述终端的RRC层请求MAC层生成所述返回通知;
所述终端的MAC层发送RRC层生成的所述返回通知。
一些实施例中,所述PUSCH资源可以是专用于终端发送所述返回通知的资源。
一些实施例中,所述发送模块具体用于若所述终端没有可用的PUSCH资源和/或PUCCH资源,发起随机接入,若UE有专用随机接入信道(RACH)资源,则使用专用RACH资源执行随机接入,若没有,UE执行竞争RACH。
一些实施例中,所述发送模块具体用于若所述终端有上报CSI或SRS的专用资源,触发CSI上报或SRS发送。
一些实施例中,所述装置还包括处理模块,用于执行以下至少一项:
请求或指示恢复所述终端的分组数据汇聚协议PDCP层;
请求所述终端的PDCP层指示是否有上行数据待发送。
一些实施例中,所述装置还包括:
获取模块,用于获取所述网络的第一资源的配置,以利用所述第一资源向所述网络发送所述返回通知。
一些实施例中,所述第一资源包括以下至少一项:
configured grant类型type1;
configured grant type2;
物理上行共享信道PUSCH资源;
物理上行控制信道PUCCH资源;
专用调度请求SR资源;
专用随机接入信道RACH资源;
专用探测参考信号SRS资源;
专用信道状态信息CSI上报资源。
一些实施例中,所述终端返回所述网络包括以下至少一项:
在间隙gap结束之前返回所述网络或未约定gap长度而返回所述网络;
在第一时刻或第一时刻之前返回所述网络,所述第一时刻在gap结束之前,且距离gap结束有T秒,T由网络配置或者协议约定;
在所述网络调度的gap结束之后返回所述网络。
其中,所述gap为所述终端和所述网络协商确定或自主Autonomous gap。
上述gap可以理解为一段时间或者周期性出现的一段时间,在这段时间内终端不在当前网络(例如网络A)监听调度或进行数据的收发,而是切换到其他网络执行某些业务。在gap结束时或之后,终端应该返回网络A,开始恢复监听调度或者开始进行数据的收发。Gap可以由终端上报给网络,也可以由网络配置给终端,其中gap可以包含以下至少一项:时间长度duration/length,开始时间(gap start time),结束时间(gap end time),gap周期,gap的用途(for Multi-SIM purpose),gap配置的添加或修改或释放。
本申请实施例中的返回网络的通知装置可以是装置,也可以是终端中的部件、集成电路、或芯片。该装置可以是移动电子设备,也可以为非移动电子设备。示例性的,移动电子设备可以为手机、平板电脑、笔记本电脑、掌上电脑、车载电子设备、可穿戴设备、超级移动个人计算机(ultra-mobile personal computer,UMPC)、上网本或者个人数字助理(personal digital assistant, PDA)等,非移动电子设备可以为网络附属存储器(Network Attached Storage,NAS)、个人计算机(personal computer,PC)、电视机(television,TV)、柜员机或者自助机等,本申请实施例不作具体限定。
本申请实施例中的返回网络的通知装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统,可以为ios操作系统,还可以为其他可能的操作系统,本申请实施例不作具体限定。
可选的,本申请实施例还提供一种终端,包括处理器,存储器,存储在存储器上并可在所述处理器上运行的程序或指令,该程序或指令被处理器执行时实现上述返回网络的通知方法的实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
需要注意的是,本申请实施例中的终端包括上述所述的移动电子设备和非移动电子设备。
图7为实现本申请各个实施例的一种终端的硬件结构示意图,该终端50包括但不限于:射频单元51、网络模块52、音频输出单元53、输入单元54、传感器55、显示单元56、用户输入单元57、接口单元58、存储器59、处理器510、以及电源511等部件。本领域技术人员可以理解,图7中示出的终端结构并不构成对终端的限定,终端可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。在本申请实施例中,终端包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
应理解的是,本申请实施例中,射频单元51可用于收发信息或通话过程中,信号的接收和发送,具体的,将来自基站的下行数据接收后,给处理器510处理;另外,将上行的数据发送给基站。通常,射频单元51包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外,射频单元51还可以通过无线通信系统与网络和其他设备通信。
存储器59可用于存储软件程序以及各种数据。存储器59可主要包括存储程序区和存储数据区,其中,存储程序区可存储操作系统、至少一个功能 所需的应用程序(比如声音播放功能、图像播放功能等)等;存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外,存储器59可以包括高速随机存取存储器,还可以包括非易失性存储器,例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器510是终端的控制中心,利用各种接口和线路连接整个终端的各个部分,通过运行或执行存储在存储器59内的软件程序和/或模块,以及调用存储在存储器59内的数据,执行终端的各种功能和处理数据,从而对终端进行整体监控。处理器510可包括一个或至少两个处理单元;优选的,处理器510可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统、用户界面和应用程序等,调制解调处理器主要处理无线通信。可以理解的是,上述调制解调处理器也可以不集成到处理器510中。
终端50还可以包括给各个部件供电的电源511(比如电池),优选的,电源511可以通过电源管理系统与处理器510逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外,终端50包括一些未示出的功能模块,在此不再赘述。
一些实施例中,处理器510用于判断是否向网络发送返回通知;若判断向所述网络发送所述返回通知,射频单元51用于向所述网络发送所述返回通知。
一些实施例中,处理器510具体用于在满足预设条件时,判断向所述网络发送所述返回通知,所述预设条件包括以下至少一项:
第一预设条件:所述终端返回所述网络时没有待发送的上行数据和/或信令;
第二预设条件:所述终端返回所述网络时没有缓存状态报告BSR被触发;
第三预设条件:所述终端返回所述网络时缓存状态报告BSR被触发但是没有发送所述BSR的资源;
第四预设条件:所述终端返回所述网络时有待发送的上行数据但所述上行数据已经触发过BSR,且没有发送所述上行数据的资源;
第五预设条件:所述网络配置所述终端发送返回通知;
第六预设条件:所述终端返回所述网络前,根据所述网络的第一指示信息离开所述网络:
第七预设条件:所述终端自主离开所述网络。
一些实施例中,判断是否向网络发送返回通知,包括:
所述终端的MAC层判断是否向网络发送返回通知;或
所述终端的RRC层判断是否向网络发送返回通知。
一些实施例中,处理器510判断向所述网络发送所述返回通知后,向所述网络发送所述返回通知,包括以下至少一项:
生成或触发BSR;
生成MAC控制元素CE,所述MAC CE用于指示所述终端返回所述网络;
触发SR;
所述终端的MAC层请求RRC层生成所述返回通知;
所述终端的RRC层请求MAC层生成所述返回通知;
所述RRC层生成所述返回通知;
所述终端的MAC层发送RRC层生成的所述返回通知;
发起随机接入;
触发CSI上报或SRS发送。
一些实施例中,所述MAC CE包括特定LCID域和/或特定数值域。
一些实施例中,所述BSR满足以下任一项:
buffer size域不出现;
buffer size域的值为预设值;
LCID域的值为预设值;
BSR为空。
一些实施例中,射频单元51用于若所述终端存在专用SR资源,发送SR。
一些实施例中,处理器510用于若所述终端有PUSCH资源,执行以下任一项:
发送所述BSR;
发送所述MAC CE;
所述RRC层生成所述返回通知;
所述终端的MAC层请求RRC层生成所述返回通知;
所述终端的RRC层请求MAC层生成所述返回通知;
所述终端的MAC层发送RRC层生成的所述返回通知。
一些实施例中,处理器510用于若所述终端没有可用的PUSCH资源和/或PUCCH资源,发起随机接入。
一些实施例中,处理器510用于若所述终端有上报CSI或SRS的专用资源,触发CSI上报或SRS发送。
一些实施例中,处理器510还用于执行以下至少一项:
所述终端的RRC层请求或指示恢复所述终端的分组数据汇聚协议PDCP层;
所述终端的RRC层请求所述终端的PDCP层指示是否有上行数据待发送。
一些实施例中,射频单元51还用于获取所述网络的第一资源的配置,以利用所述第一资源向所述网络发送所述返回通知。
一些实施例中,所述第一资源包括以下至少一项:
configured grant类型type1;
configured grant type2;
物理上行共享信道PUSCH资源;
物理上行控制信道PUCCH资源;
专用调度请求SR资源;
专用随机接入信道RACH资源;
专用探测参考信号SRS资源;
专用信道状态信息CSI上报资源。
一些实施例中,所述第一预设条件为基于以下至少一项确定:
所述终端的MAC层的指示、所述终端的RRC层的指示、所述终端的服 务数据适配协议SDAP层的指示、所述终端的PDCP层的指示、所述终端的物理层的指示。
一些实施例中,所述终端返回所述网络包括以下至少一项:
在间隙gap结束之前返回所述网络或未约定gap长度而返回所述网络;
在第一时刻或第一时刻之前返回所述网络,所述第一时刻在gap结束之前,且距离gap结束有T秒,T由网络配置或者协议约定;
在所述网络调度的gap结束之后返回所述网络。
本申请实施例还提供一种可读存储介质,所述可读存储介质上存储有程序或指令,该程序或指令被处理器执行时实现上述返回网络的通知方法的实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
其中,所述处理器为上述实施例中所述的电子设备中的处理器。所述可读存储介质,包括计算机可读存储介质,如计算机只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现上述返回网络的通知方法的实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片、系统芯片、芯片系统或片上系统芯片等。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外,需要指出的是,本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能,还 可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能,例如,可以按不同于所描述的次序来执行所描述的方法,并且还可以添加、省去、或组合各种步骤。另外,参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端(可以是手机,计算机,服务器,或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述,但是本申请并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的,本领域的普通技术人员在本申请的启示下,在不脱离本申请宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本申请的保护之内。

Claims (33)

  1. 一种返回网络的通知方法,由终端执行,所述方法包括:
    判断是否向网络发送返回通知;
    若判断向所述网络发送所述返回通知,向所述网络发送所述返回通知。
  2. 根据权利要求1所述的返回网络的通知方法,其中,判断是否向网络发送返回通知,包括:
    在满足预设条件时,判断向所述网络发送所述返回通知,所述预设条件包括以下至少一项:
    第一预设条件:所述终端返回所述网络时没有待发送的上行数据和/或信令;
    第二预设条件:所述终端返回所述网络时没有缓存状态报告BSR被触发;
    第三预设条件:所述终端返回所述网络时缓存状态报告BSR被触发但是没有发送所述BSR的资源;
    第四预设条件:所述终端返回所述网络时有待发送的上行数据但所述上行数据已经触发过BSR,且没有发送所述上行数据的资源;
    第五预设条件:所述网络配置所述终端发送返回通知;
    第六预设条件:所述终端返回所述网络前,根据所述网络的第一指示信息离开所述网络:
    第七预设条件:所述终端自主离开所述网络。
  3. 根据权利要求1所述的返回网络的通知方法,其中,判断是否向网络发送返回通知,包括:
    所述终端的MAC层判断是否向网络发送返回通知;或
    所述终端的RRC层判断是否向网络发送返回通知。
  4. 根据权利要求1所述的返回网络的通知方法,其中,判断向所述网络发送所述返回通知后,向所述网络发送所述返回通知,包括以下至少一项:
    生成或触发BSR;
    生成MAC控制元素CE,所述MAC CE用于指示所述终端返回所述网络;
    触发SR;
    所述终端的MAC层请求RRC层生成所述返回通知;
    所述终端的RRC层请求MAC层生成所述返回通知;
    所述RRC层生成所述返回通知;
    所述终端的MAC层发送RRC层生成的所述返回通知;
    发起随机接入;
    触发CSI上报或SRS发送。
  5. 根据权利要求4所述的返回网络的通知方法,其中,所述MAC CE包括特定逻辑信道标识LCID域和/或特定数值域。
  6. 根据权利要求4所述的返回网络的通知方法,其中,所述BSR满足以下任一项:
    buffer size域不出现;
    buffer size域的值为预设值;
    LCID域的值为预设值;
    BSR为空。
  7. 根据权利要求4所述的返回网络的通知方法,其中,若所述终端存在专用SR资源,发送SR。
  8. 根据权利要求4所述的返回网络的通知方法,其中,若所述终端有PUSCH资源,执行以下任一项:
    发送所述BSR;
    发送所述MAC CE;
    所述RRC层生成所述返回通知;
    所述终端的MAC层请求RRC层生成所述返回通知;
    所述终端的RRC层请求MAC层生成所述返回通知;
    所述终端的MAC层发送RRC层生成的所述返回通知。
  9. 根据权利要求4所述的返回网络的通知方法,其中,若所述终端没有 可用的PUSCH资源和/或PUCCH资源,发起随机接入。
  10. 根据权利要求4所述的返回网络的通知方法,其中,若所述终端有上报CSI或SRS的专用资源,触发CSI上报或SRS发送。
  11. 根据权利要求1所述的返回网络的通知方法,其中,判断是否向所述网络发送返回通知之前,所述方法还包括以下至少一项:
    所述终端的RRC层请求或指示恢复所述终端的分组数据汇聚协议PDCP层;
    所述终端的RRC层请求所述终端的PDCP层指示是否有上行数据待发送。
  12. 根据权利要求1所述的返回网络的通知方法,其中,判断向所述网络发送返回通知之前,所述方法还包括:
    获取所述网络的第一资源的配置,以利用所述第一资源向所述网络发送所述返回通知。
  13. 根据权利要求12所述的返回网络的通知方法,其中,所述第一资源包括以下至少一项:
    configured grant类型type1;
    configured grant type2;
    物理上行共享信道PUSCH资源;
    物理上行控制信道PUCCH资源;
    专用调度请求SR资源;
    专用随机接入信道RACH资源;
    专用探测参考信号SRS资源;
    专用信道状态信息CSI上报资源。
  14. 根据权利要求2所述的返回网络的通知方法,其中,所述第一预设条件为基于以下至少一项确定:
    所述终端的MAC层的指示、所述终端的RRC层的指示、所述终端的服务数据适配协议SDAP层的指示、所述终端的PDCP层的指示、所述终端的物理层的指示。
  15. 根据权利要求2所述的返回网络的通知方法,其中,所述终端返回所述网络包括以下至少一项:
    在间隙gap结束之前返回所述网络或未约定gap长度而返回所述网络;
    在第一时刻或第一时刻之前返回所述网络,所述第一时刻在gap结束之前,且距离gap结束有T秒,T由网络配置或者协议约定;
    在所述网络调度的gap结束之后返回所述网络。
  16. 一种返回网络的通知装置,应用于终端,所述装置包括:
    判断模块,用于判断是否向网络发送返回通知;
    发送模块,用于若判断向所述网络发送所述返回通知,向所述网络发送所述返回通知。
  17. 根据权利要求16所述的返回网络的通知装置,其中,所述判断模块具体用于在满足预设条件时,判断向所述网络发送所述返回通知,所述预设条件包括以下至少一项:
    第一预设条件:所述终端返回所述网络时没有待发送的上行数据和/或信令;
    第二预设条件:所述终端返回所述网络时没有缓存状态报告BSR被触发;
    第三预设条件:所述终端返回所述网络时缓存状态报告BSR被触发但是没有发送所述BSR的资源;
    第四预设条件:所述终端返回所述网络时有待发送的上行数据但所述上行数据已经触发过BSR,且没有发送所述上行数据的资源;
    第五预设条件:所述网络配置所述终端发送返回通知;
    第六预设条件:所述终端返回所述网络前,根据所述网络的第一指示信息离开所述网络:
    第七预设条件:所述终端自主离开所述网络。
  18. 根据权利要求16所述的返回网络的通知装置,其中,所述发送模块具体用于执行以下至少一项:
    生成或触发BSR;
    生成MAC控制元素CE,所述MAC CE用于指示所述终端返回所述网络;
    触发SR;
    所述终端的MAC层请求RRC层生成所述返回通知;
    所述终端的RRC层请求MAC层生成所述返回通知;
    所述RRC层生成所述返回通知;
    所述终端的MAC层发送RRC层生成的所述返回通知;
    发起随机接入;
    触发CSI上报或SRS发送。
  19. 根据权利要求18所述的返回网络的通知装置,其中,所述MAC CE包括特定LCID域和/或特定数值域。
  20. 根据权利要求18所述的返回网络的通知装置,其中,所述BSR满足以下任一项:
    buffer size域不出现;
    buffer size域的值为预设值;
    LCID域的值为预设值;
    BSR为空。
  21. 根据权利要求18所述的返回网络的通知装置,其中,所述发送模块具体用于若所述终端存在专用SR资源,发送SR。
  22. 根据权利要求18所述的返回网络的通知装置,其中,所述发送模块具体用于若所述终端有PUSCH资源,执行以下任一项:
    发送所述BSR;
    发送所述MAC CE;
    所述RRC层生成所述返回通知;
    所述终端的MAC层请求RRC层生成所述返回通知;
    所述终端的RRC层请求MAC层生成所述返回通知;
    所述终端的MAC层发送RRC层生成的所述返回通知。
  23. 根据权利要求18所述的返回网络的通知装置,其中,所述发送模块 具体用于若所述终端没有可用的PUSCH资源和/或PUCCH资源,发起随机接入。
  24. 根据权利要求18所述的返回网络的通知装置,其中,所述发送模块具体用于若所述终端有上报CSI或SRS的专用资源,触发CSI上报或SRS发送。
  25. 根据权利要求16所述的返回网络的通知装置,其中,所述装置还包括处理模块,用于执行以下至少一项:
    请求或指示恢复所述终端的分组数据汇聚协议PDCP层;
    请求所述终端的PDCP层指示是否有上行数据待发送。
  26. 根据权利要求16所述的返回网络的通知装置,其中,所述装置还包括:
    获取模块,用于获取所述网络的第一资源的配置,以利用所述第一资源向所述网络发送所述返回通知。
  27. 根据权利要求26所述的返回网络的通知装置,其中,所述第一资源包括以下至少一项:
    configured grant类型type1;
    configured grant type2;
    物理上行共享信道PUSCH资源;
    物理上行控制信道PUCCH资源;
    专用调度请求SR资源;
    专用随机接入信道RACH资源;
    专用探测参考信号SRS资源;
    专用信道状态信息CSI上报资源。
  28. 根据权利要求17所述的返回网络的通知装置,其中,所述第一预设条件为基于以下至少一项确定:
    所述终端的MAC层的指示、所述终端的RRC层的指示、所述终端的服务数据适配协议SDAP层的指示、所述终端的PDCP层的指示、所述终端的 物理层的指示。
  29. 根据权利要求17所述的返回网络的通知装置,其中,所述终端返回所述网络包括以下至少一项:
    在间隙gap结束之前返回所述网络或未约定gap长度而返回所述网络;
    在第一时刻或第一时刻之前返回所述网络,所述第一时刻在gap结束之前,且距离gap结束有T秒,T由网络配置或者协议约定;
    在所述网络调度的gap结束之后返回所述网络。
  30. 一种终端,包括处理器,存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,其中,所述程序或指令被所述处理器执行时实现如权利要求1-15中任一项所述的返回网络的通知方法的步骤。
  31. 一种可读存储介质,所述可读存储介质上存储程序或指令,其中,所述程序或指令被处理器执行时实现如权利要求1-15中任一项所述的返回网络的通知方法的步骤。
  32. 一种芯片,包括处理器和通信接口,其中,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现如权利要求1-15中任一项所述的返回网络的通知方法的步骤。
  33. 一种计算机程序产品,其中,所述计算机程序产品被存储在非易失的存储介质中,所述计算机程序产品被至少一个处理器执行以实现如权利要求1-15中任一项所述的返回网络的通知方法的步骤。
PCT/CN2022/071314 2021-01-15 2022-01-11 返回网络的通知方法、装置及终端 WO2022152119A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP22738998.8A EP4266751A1 (en) 2021-01-15 2022-01-11 Method and device for notifying to return to network and terminal
JP2023542744A JP2024503858A (ja) 2021-01-15 2022-01-11 ネットワークへの復帰の通知方法、端末、可読記憶媒体及びチップ
US18/222,472 US20230370911A1 (en) 2021-01-15 2023-07-16 Notification method and apparatus for returning to network, and terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110057640.6A CN114765822A (zh) 2021-01-15 2021-01-15 返回网络的通知方法、装置及终端
CN202110057640.6 2021-01-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/222,472 Continuation US20230370911A1 (en) 2021-01-15 2023-07-16 Notification method and apparatus for returning to network, and terminal

Publications (1)

Publication Number Publication Date
WO2022152119A1 true WO2022152119A1 (zh) 2022-07-21

Family

ID=82364914

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/071314 WO2022152119A1 (zh) 2021-01-15 2022-01-11 返回网络的通知方法、装置及终端

Country Status (5)

Country Link
US (1) US20230370911A1 (zh)
EP (1) EP4266751A1 (zh)
JP (1) JP2024503858A (zh)
CN (1) CN114765822A (zh)
WO (1) WO2022152119A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104303549A (zh) * 2012-04-06 2015-01-21 马维尔国际贸易有限公司 在多无线电接入技术蜂窝网络中执行空闲模式信令减少的系统和方法
CN108337743A (zh) * 2018-03-27 2018-07-27 青岛海信移动通信技术股份有限公司 一种双卡双系统的终端设备及其通信方法
WO2018232560A1 (en) * 2017-06-19 2018-12-27 Qualcomm Incorporated INTERCELLULAR REPLI TRANSFER FOR APPLICATION SUPPORT IN WIRELESS SYSTEMS
CN111758282A (zh) * 2020-05-18 2020-10-09 北京小米移动软件有限公司 小区切换方法及装置、存储介质
WO2020252795A1 (zh) * 2019-06-21 2020-12-24 Oppo广东移动通信有限公司 无线通信的方法、终端设备,接入网设备和核心网设备
CN113225778A (zh) * 2020-01-20 2021-08-06 维沃移动通信有限公司 消息通知方法、终端和网络设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104303549A (zh) * 2012-04-06 2015-01-21 马维尔国际贸易有限公司 在多无线电接入技术蜂窝网络中执行空闲模式信令减少的系统和方法
WO2018232560A1 (en) * 2017-06-19 2018-12-27 Qualcomm Incorporated INTERCELLULAR REPLI TRANSFER FOR APPLICATION SUPPORT IN WIRELESS SYSTEMS
CN108337743A (zh) * 2018-03-27 2018-07-27 青岛海信移动通信技术股份有限公司 一种双卡双系统的终端设备及其通信方法
WO2020252795A1 (zh) * 2019-06-21 2020-12-24 Oppo广东移动通信有限公司 无线通信的方法、终端设备,接入网设备和核心网设备
CN113225778A (zh) * 2020-01-20 2021-08-06 维沃移动通信有限公司 消息通知方法、终端和网络设备
CN111758282A (zh) * 2020-05-18 2020-10-09 北京小米移动软件有限公司 小区切换方法及装置、存储介质

Also Published As

Publication number Publication date
EP4266751A1 (en) 2023-10-25
JP2024503858A (ja) 2024-01-29
CN114765822A (zh) 2022-07-19
US20230370911A1 (en) 2023-11-16

Similar Documents

Publication Publication Date Title
KR101299277B1 (ko) 롱 텀 이볼루션에서 데이터 전송의 종료를 표시함으로써 배터리에 대해 효과적인 상태 또는 구성으로 전환하는 방법 및 장치
EP3383127B1 (en) Suspending a connection in a wireless communication system
EP2901803B1 (en) Power preference indicator timer
CN107113879B (zh) 用于无线设备的不连续操作的系统和方法
US20180213576A1 (en) Connection Release Assistance Information
WO2018107498A1 (zh) 用于非连续接收的方法和装置
JP2020504576A (ja) 無線アクセスネットワークにおける輻輳緩和のための技術
WO2022152054A1 (zh) 省电处理方法、装置及终端
WO2022174839A1 (zh) 通信设备的工作方法、装置及通信设备
CN110169146B (zh) 非连续接收的管理方法和装置
US20230189352A1 (en) Service Collision Handling Method and Apparatus, and Terminal
WO2022028603A1 (zh) 数据传输方法、装置及电子设备
WO2022152119A1 (zh) 返回网络的通知方法、装置及终端
WO2022100505A1 (zh) 信息处理方法、装置及终端
WO2021184417A1 (zh) 一种数据传输方法及相关产品
CN113225778A (zh) 消息通知方法、终端和网络设备
WO2022152129A1 (zh) 上行数据发送增强流程的触发方法、装置及终端
WO2023066129A1 (zh) 信息上报方法、设备及可读存储介质
WO2022262865A1 (zh) Gap处理方法、装置、终端及可读存储介质
WO2022205266A1 (en) Method and apparatus for data transmission in non-connected state
WO2023051366A1 (zh) 一种控制传输的方法及相关装置
WO2017128309A1 (zh) 一种寻呼方法、网络设备及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22738998

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023542744

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 2022738998

Country of ref document: EP

Effective date: 20230720

NENP Non-entry into the national phase

Ref country code: DE