WO2024012305A1 - 连接恢复方法、装置、终端及网络侧设备 - Google Patents

连接恢复方法、装置、终端及网络侧设备 Download PDF

Info

Publication number
WO2024012305A1
WO2024012305A1 PCT/CN2023/105413 CN2023105413W WO2024012305A1 WO 2024012305 A1 WO2024012305 A1 WO 2024012305A1 CN 2023105413 W CN2023105413 W CN 2023105413W WO 2024012305 A1 WO2024012305 A1 WO 2024012305A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
multicast service
message
cell
network side
Prior art date
Application number
PCT/CN2023/105413
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 维沃移动通信有限公司
Publication of WO2024012305A1 publication Critical patent/WO2024012305A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • This application belongs to the field of communication technology, and specifically relates to a connection recovery method, device, terminal and network side equipment.
  • Embodiments of the present application provide a connection recovery method, device, terminal and network-side equipment, which can solve the problem of heavy network load.
  • the first aspect provides a connection recovery method, including:
  • the terminal camps in the first cell in an inactive state and receives the first multicast service
  • a first message is sent, and the first message is used to request connection recovery.
  • connection recovery method including:
  • the network side device receives a first message sent by the terminal, where the first message is used to request connection recovery;
  • the terminal is a terminal camping on the first cell in an inactive state to receive the first multicast service.
  • connection recovery device including:
  • the first receiving module is used to camp on the first cell in the inactive state and receive the first multicast service
  • the first sending module is configured to send a first message when the terminal meets the preset conditions, where the first message is used to request connection recovery.
  • connection recovery device including:
  • a first receiving module configured to receive a first message sent by the terminal, where the first message is used to request connection recovery;
  • the terminal is a terminal camping on the first cell in an inactive state to receive the first multicast service.
  • a terminal in a fifth aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the present application is implemented.
  • the embodiment provides the steps of the connection recovery method.
  • a terminal including a processor and a communication interface, wherein the communication interface is used to camp on the first cell in an inactive state and receive the first multicast service; when the terminal meets preset conditions In the case of , the first message is sent, and the first message is used to request connection recovery.
  • a network-side device including a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the present application is implemented.
  • the embodiment provides the steps of the connection recovery method.
  • a network side device including a processor and a communication interface, wherein the communication interface is used to receive a first message sent by a terminal, and the first message is used to request connection recovery; wherein, the terminal It is a terminal that camps on the first cell in an inactive state and receives the first multicast service.
  • a readable storage medium is provided.
  • Programs or instructions are stored on the readable storage medium.
  • the steps of the terminal-side connection recovery method provided by the embodiments of the present application are implemented.
  • the steps of the connection recovery method on the network side device side provided by the embodiment of the present application are implemented.
  • a chip in a tenth aspect, includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the terminal side provided by the embodiments of the present application.
  • the connection recovery method, or the processor is used to run a program or instructions to implement the connection recovery method on the network side device side provided in the embodiment of the present application.
  • a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the methods provided by the embodiments of the present application.
  • the steps of the connection recovery method on the terminal side, or the computer program/program product is executed by at least one processor to implement the steps of the connection recovery method on the network side device side provided by the embodiment of the present application.
  • a frequency domain resource determination system including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the terminal side connection recovery method provided by the embodiment of the present application.
  • the network side device can The steps of executing the connection recovery method on the network side device side provided by the embodiment of the present application.
  • the terminal camps in the first cell in an inactive state and receives the first multicast service; when the terminal meets the preset conditions, the terminal sends a first message, and the first message is To request connection recovery. This is okay Supports terminals to receive multicast services in inactive state, thereby reducing network load. In addition, by sending the first message, when the terminal receives the multicast service in the inactive state, it can promptly request connection recovery to improve the flexibility of terminal state switching.
  • Figure 1 is a block diagram of a wireless communication system applicable to the embodiment of the present application.
  • Figure 2 is a flow chart of a connection recovery method provided by an embodiment of the present application.
  • Figure 3 is a flow chart of another connection recovery method provided by an embodiment of the present application.
  • Figure 4 is a structural diagram of a connection recovery device provided by an embodiment of the present application.
  • FIG. 5 is a structural diagram of another connection recovery device provided by an embodiment of the present application.
  • Figure 6 is a structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 7 is a structural diagram of a terminal provided by an embodiment of the present application.
  • Figure 8 is a structural diagram of a network side device provided by an embodiment of the present application.
  • first, second, etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first" and “second” are distinguished objects It is usually one type, and the number of objects is not limited.
  • the first object can be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the related objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced, LTE-A Long Term Evolution
  • LTE-A Long Term Evolution
  • 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
  • NR New Radio
  • 6G 6th Generation
  • FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable.
  • the wireless communication system includes a terminal 11 and a network side device 12.
  • the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, or a super mobile personal computer.
  • Tablet Personal Computer Tablet Personal Computer
  • laptop computer laptop computer
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • UMPC ultra-mobile personal computer
  • UMPC mobile Internet device
  • MID mobile Internet device
  • augmented reality augmented reality, AR
  • VR virtual reality
  • robots wearable devices
  • Vehicle user equipment VUE
  • pedestrian terminal pedestrian terminal
  • PUE pedestrian terminal
  • smart home home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.
  • game consoles personal computers (personal computer, PC), teller machine or self-service machine and other terminal-side devices.
  • Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets) bracelets, smart anklets, etc.), smart wristbands, smart clothing, etc.
  • the network side device 12 may include an access network device or a core network device, where the network side device 12 may also be called a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a wireless access network unit.
  • the network side device 12 may include a base station, a Wireless Local Area Network (WLAN) access point or a WiFi node, etc.
  • WLAN Wireless Local Area Network
  • the base station may be called a Node B, an Evolved Node B (eNB), an access point, a base transceiver station ( Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B-node, home evolved B-node, sending and receiving point ( Transmitting Receiving Point (TRP) 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 terms. It should be noted that in the embodiment of this application, only the NR system is used The base station is introduced as an example, and the specific type of base station is not limited.
  • Core network equipment may include but is not limited to at least one of the following: core network nodes, core network functions, mobility management entities (Mobility Management Entity, MME), access mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Services Discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data warehousing (Unified Data Repository, UDR), home subscriber server (Home Subscriber Server, HSS), centralized network configuration ( Centralized network configuration, CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (Local NEF, or L-NEF), Binding Support Function (Binding Support Function, BSF), application function (Application Function, AF), etc.
  • MME mobility management entities
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • connection recovery method provided by embodiments of the present application will be described through some embodiments and application scenarios. Methods, devices, terminals and network-side equipment are described in detail.
  • Figure 2 is a flow chart of a connection recovery method provided by an embodiment of the present application. As shown in Figure 2, it includes the following steps, including:
  • the terminal camps in the first cell in an inactive state and receives the first multicast service.
  • the above-mentioned first cell may be a multicast service cell (multicast cell) that sends the above-mentioned first multicast service, or the above-mentioned first cell may be a cell (non-Multicast cell) that does not send the first multicast service, but the above-mentioned When the terminal is camped in the cell, the terminal can receive the first multicast service.
  • multicast cell multicast service cell
  • non-Multicast cell a cell that does not send the first multicast service
  • the multicast service may be expressed as a multicast service, or may be expressed as a multicast/broadcast service (Multicast/Broadcast Service, MBS).
  • MBS Multicast/Broadcast Service
  • the above preset conditions may be agreed upon in the protocol, configured on the network side, or determined by the terminal itself.
  • the above-mentioned first message may be sent in the above-mentioned first cell, or may be sent in the second cell.
  • the terminal camps on the first cell in the inactive state to receive the first multicast service, and the terminal performs cell reselection and reselects to The second cell, and sends the above-mentioned first message, wherein the first cell can be a Multicast cell or a non-Multicast cell, for example: other cells with the same coverage area as the Multicast cell, the same coverage area here can be all Or partially the same.
  • the above steps can support the terminal to receive multicast services in the inactive state.
  • the network load of the terminal in the inactive state is less than the network load of the terminal in the connected state. Therefore, the embodiment of the present application can reduce Network load.
  • the complexity and power consumption of the inactive state are lower than those of the connected state. Therefore, the power consumption of the terminal can also be reduced.
  • the terminal when the terminal receives the multicast service in the inactive state, it can promptly request connection recovery to improve the flexibility of terminal state switching.
  • connection recovery updated multicast configurations, new cell multicast configurations, new multicast transmission methods can be obtained from the network side, and some abnormal reception conditions can be reported. This can ensure that the terminal responds to multicast services in a timely and normal manner. Reception improves the terminal experience and system efficiency while ensuring the reception effect.
  • the terminal satisfying preset conditions includes at least one of the following:
  • the terminal receives a notification message sent by the network side, where the notification message is used to notify that the configuration of the first multicast service has changed;
  • the terminal performs cell reselection
  • the terminal performs mobility management
  • the terminal is no longer interested in the first multicast service
  • the quality with which the terminal receives the first multicast service matches the preset quality, and the preset quality indicates that the first multicast service cannot continue to be received.
  • the above notification message may include at least one of the following:
  • Layer 1 Layer 1
  • Media Access Control Medium Access Control, MAC
  • Radio Resource Control Radio Resource Control, RRC
  • the configuration of the multicast service may include but is not limited to: multicast/broadcast service radio bearer (MBS (Multicast/Broadcast Service) radio bear, MRB) configuration, time domain pattern (pattern) ), frequency domain resources, dynamic scheduling information, etc.
  • MRS Multicast/Broadcast Service radio bearer
  • MRB multicast/broadcast service radio bearer
  • pattern time domain pattern
  • the time domain pattern can include configurations such as cycle length, cycle starting position, and activation duration within the cycle.
  • the configuration change of the above multicast service may be a change of part or all of the configuration.
  • the above terminal may perform cell reselection by reselecting the terminal to another cell.
  • the above terminal execution of mobility management may be that the terminal executes mobility management evaluation.
  • the above terminal is no longer interested in the first multicast service.
  • the terminal determines by itself that it is no longer interested in the first multicast service. For example: Based on the terminal implementation, the first multicast service is no longer required. If the terminal requests to enter the inactive state (Inactive) to receive the multicast service for the purpose of power saving, the terminal can request the network when the power is replenished or the power is sufficient. The connection is restored. That is to say, in the embodiment of the present application, the request for connection recovery can be sent based on the terminal.
  • connection recovery can be initiated based on different reasons to improve the flexibility of multicast service reception.
  • the above terminal performs cell reselection, including at least one of the following:
  • the terminal is reselected from the first cell to a second cell, and the first cell is a multicast service cell that sends the first multicast service;
  • the terminal is reselected from a first effective area to a third cell, the first effective area is an effective area of the first multicast service, and the third cell does not belong to the first effective area.
  • the above reselection of the terminal from the first cell to the second cell can also be understood as the terminal selection from the first cell to the second cell.
  • connection recovery is initiated.
  • the above-mentioned reselection to the third cell may be that the terminal selects/reselects a cell from a cell in which the current multicast service configuration is valid, and reselects to other invalid cells outside the valid cell list/valid cell range, then initiates connection recovery.
  • This embodiment mainly describes cell reselection, specifically as follows:
  • the terminal When the terminal reselects a cell from the current multicast cell, or the terminal reselects from a cell with valid multicast configuration to a cell outside the valid configuration area, it means that the multicast cell configuration stored by the terminal at this time is no longer effective.
  • the terminal also needs to trigger connection recovery and re-apply to the network for the configuration or transmission method of the new cell.
  • the terminal initiates a connection restoration request in the new cell.
  • a connection restoration request in the new cell.
  • the method of initiation please refer to other embodiments or implementations. It may also adopt different methods to indicate the clear purpose of its connection restoration request to the network.
  • At least one of the following methods can be used for subsequent processing:
  • the terminal can be allowed to enter the connection first. state, perform data transmission or signaling process, and at the same time send the new configuration of the multicast service to the terminal through RRC reconfiguration signaling.
  • the new cell can keep the terminal in Connected and continue to receive services.
  • the network can send an RRC Release message to the terminal again to release it to the inactive state (Inactive) for service reception.
  • the cell information and configuration that supports multicast services can be sent to the terminal, or a unicast bearer can be established for the terminal to continue receiving multicast services.
  • This new configuration may not be the configuration supported by this cell, or it may be the configuration supported by other cells under the internal base station (intra-gNB), or it may be other cells such as ID, frequency information, etc. are sent to the terminal, and at the same time, they are directly released to Inactive for service reception.
  • terminal Context the terminal context
  • the network side determines the terminal's interested service information as soon as possible, as well as the terminal's current configuration information, to facilitate the network side in each
  • it is decided whether to send new cell configuration information to the terminal For example: If the cell corresponding to the current multicast service configuration is inconsistent with the Multicast cell stored in the terminal context, it means that the terminal has moved and a new configuration needs to be resent to the terminal. When there is no cell information, you can also compare the current configuration with the configuration stored in the terminal context. If they are the same, it means that the terminal configuration can continue to be used without sending updates.
  • PDCP Packet Data Convergence Protocol
  • COUNT Packet Data Convergence Protocol count
  • the above terminal performs mobility management, including at least one of the following due to mobility:
  • the terminal camps on the first cell and stops receiving the first multicast service
  • the measurement result of the terminal for the reference signal of the first cell matches a first preset measurement result, and the first preset measurement result indicates that the terminal cannot continue to receive the first multi-channel signal in the first cell. Broadcasting business;
  • the quality of the first multicast service received by the terminal matches the preset quality, and the preset quality indicates that the terminal cannot continue to receive the first multicast service in the first cell;
  • the measurement result of the multicast channel or multicast signal by the terminal matches a second preset measurement result, and the second preset measurement result indicates that the terminal cannot continue to receive the first multicast in the first cell. business;
  • the information of the terminal indicates that it cannot continue to receive the first multicast service.
  • the terminal camped in the first cell and stopping receiving the first multicast service may be that the terminal camped in the first cell needs to stop receiving the first multicast service due to movement or other reasons.
  • the above-mentioned stop reception point The first multicast service may be stopping receiving the first multicast service because the first multicast service can no longer be received.
  • the above-mentioned first preset measurement result, preset quality and second preset measurement result may be values defined by the protocol or values configured on the network side.
  • the above measurement results can be measurement results such as reference signal received power (RSRP), signal-to-noise ratio (SNR), reference signal receiving quality (RSRQ), etc.
  • RSRP reference signal received power
  • SNR signal-to-noise ratio
  • RSRQ reference signal receiving quality
  • the above measurement result matches the first preset measurement result.
  • the first preset measurement result indicates that the terminal cannot continue to receive the first multicast service in the first cell.
  • the measurement result may be lower than the first preset measurement result.
  • the measurement result indicates that if the terminal continues to receive the first multicast service in the first cell, the reception may be unsuccessful. Therefore, the terminal cannot continue to receive the first multicast service.
  • the above-mentioned second preset measurement result matches.
  • the second preset measurement result indicates that the terminal cannot continue to receive the first multicast service in the first cell.
  • the measurement result may be lower than the second preset measurement result. , which means that the terminal may fail to receive the first multicast service if it continues to receive the first multicast service in the first cell. Therefore, the terminal cannot continue to receive the first multicast service.
  • the quality of the above-mentioned first multicast service may include quality information such as decoding failure rate, decoding success rate, block error rate, number of consecutive failed decoding data blocks, reception failure probability within a certain period of time, and so on.
  • the above quality matches the preset quality.
  • the preset quality indicates that the terminal cannot continue to receive the first multicast service in the first cell.
  • the decoding failure rate is higher than the preset value, which means that the terminal cannot continue to receive the service. If the first multicast service or the decoding success rate is lower than a preset value, it means that the first multicast service cannot continue to be received. It should be noted that, for different receiving parameters, the values of the above preset values may be different.
  • the information of the terminal indicating that it cannot continue to receive the first multicast service may be based on the information implemented by the terminal that it is determined that it cannot continue to receive the first multicast service. For example, the reception quality information evaluated by the terminal itself does not meet the requirements, or the terminal's Battery information.
  • the terminal when at least one of the above-mentioned items is not caused by movement, the terminal may also be triggered to send the above-mentioned first message.
  • the quality of the first multicast service received by the terminal matches the preset quality, including at least one of the following:
  • the terminal fails to receive data of the first multicast service for N1 consecutive times;
  • the number of failures for the terminal to receive data of the first multicast service reaches N2 times
  • the data failure ratio of the terminal in receiving the first multicast service is higher than or equal to the first preset ratio
  • the terminal does not correctly receive the first multicast service
  • the number of times the terminal correctly receives the first multicast service is less than N3 times;
  • the proportion of the terminal correctly receiving the first multicast service is lower than the second preset proportion
  • the terminal During the N4 consecutive discontinuous reception (Discontinuous Reception, DRX) periods, the terminal has no Correctly receiving the first multicast service;
  • the data failure ratio of the terminal in receiving the first multicast service is higher than or equal to the third preset ratio
  • the number of times the terminal correctly receives the first multicast service is less than N9 times;
  • the proportion of the terminal correctly receiving the first multicast service is lower than the fourth preset proportion
  • the quality of the first multicast service received by the terminal does not meet the preset requirements
  • N1 to N10 are positive integers.
  • the above N1 to N10 are defined by the protocol, configured by the network side, or determined by the terminal.
  • the above time window, duration, preset ratio, and preset requirements are defined by the protocol, or configured on the network side, or determined by the terminal.
  • the above-mentioned failure to receive data of the first multicast service may be a failure to receive a data block of the first multicast service, wherein the failure of the data block may be reflected by a failure to decode a physical downlink shared channel (PDSCH).
  • PDSCH physical downlink shared channel
  • the first time window may not be configured. For example, as long as the terminal fails to receive data of a multicast service for N2 times, the first message is sent.
  • the arrival described above can be understood as greater than or equal to, for example, the number of times the terminal fails to receive data of the first multicast service is greater than or equal to N2 times.
  • receiving the first multicast service in the first cell here refers to the terminal camp.
  • the first multicast service may be sent by the first cell or by other cells.
  • This embodiment mainly describes mobility, specifically as follows:
  • Mobility has a certain similarity with the cell reselection described in the above embodiments, in which the triggering and judgment of cell reselection comply with the mobility rules of the terminal idle state (Idle state) defined by the protocol.
  • Idle state the mobility rules of the terminal idle state defined by the protocol.
  • multicast service reception has special characteristics, because the terminal does not need to reside in the multicast cell, but can receive multicast services in the multicast cell. It is similar to the multi-reception capability, maintaining one cell and receiving multicast in another cell.
  • the idle mobility rules defined by the protocol are carried out in the resident cell, such as cell selection and reselection, while the receiving multicast cell can determine whether it can continue to receive based on another set of rules.
  • the terminal receiving the multicast service considers that the original multicast cell reception cannot continue under at least one of the following circumstances, and triggers the connection recovery process:
  • the terminal When the terminal is in the current multicast service cell, its RSRP is lower than the threshold, such as the RSRP of the common reference signal is low. at the threshold;
  • the terminal When the terminal is in the current multicast service cell, it can no longer receive multicast services
  • the terminal When the terminal receives multicast service quality from the current multicast service cell, it is poor enough to meet certain conditions; for example, at least one of the following:
  • the failure to receive multicast service data reaches N2 times, or is higher than a certain proportion
  • multicast service data is correctly received less than N3 times, or less than a certain proportion
  • the reception quality does not meet the requirements.
  • the block error rate does not meet the Quality of Service (QoS) indicator, or is higher than the threshold.
  • QoS Quality of Service
  • Another example is: the RSRP of the path loss reference is lower than the threshold;
  • the multicast signal measurement meets a certain threshold.
  • the multicast RSRP is lower than a threshold
  • the terminal when it evaluates that the reception quality does not meet the requirements, it can also initiate a report to the network.
  • the terminal After meeting the above conditions, the terminal initiates an RRC Resume Request process from the current resident cell. This process can be the same as in other embodiments.
  • the terminal can also try to carry its own purpose information in the connection recovery request process.
  • multicast-related information can also be retained in the terminal Context. This is also to allow the network side to determine the terminal's interested business information as soon as possible, as well as the terminal's current configuration information, to facilitate the network side to make decisions in various situations. , whether to send new cell configuration information to the terminal. For example: If the cell corresponding to the current multicast service configuration is inconsistent with the Multicast cell stored in the terminal context, it means that the terminal has moved and a new configuration needs to be resent to the terminal. In the absence of cell information, you can also compare the current configuration with the configuration stored in the terminal context. If they are the same, it means that the terminal configuration can continue to be used without sending updates. If the optional configuration remains unchanged, the current cell configuration can also be sent. The progress (such as PDCP COUNT information) is sent to the terminal so that the terminal can receive it synchronously as soon as possible. If it is different, it means that new configuration needs to be sent.
  • PDCP COUNT information is sent to the terminal so that the terminal can receive it synchronously as
  • the terminal is no longer interested in the first multicast service, including: the terminal is no longer interested in the first multicast service due to movement or cell reselection; and /or
  • the quality of the terminal receiving the first multicast service matching the preset quality includes: not caused by movement or cell reselection, the quality of the terminal receiving the first multicast service matching the preset quality.
  • the terminal is no longer interested in the first multicast service, which may be: Without moving or changing cells, when the terminal's home or resident cell remains unchanged, some situation changes will still occur, causing the terminal to no longer be interested in the first multicast service, thereby reporting or interacting with the network .
  • the quality of the terminal receiving the first multicast service may match the preset quality when the terminal's home or resident cell remains unchanged without moving or changing cells. , some situation changes will still occur, causing the quality of the first multicast service to change, causing the quality of the first multicast service to match the preset quality.
  • connection recovery is not initiated due to movement or cell reselection, so as to improve the flexibility of the terminal in receiving multicast services.
  • This embodiment mainly describes poor reception quality or the terminal is not interested.
  • the details can be as follows:
  • the situation of moving or changing cells is not involved.
  • the terminal's home or resident cell remains unchanged, some situation changes will still occur, causing the terminal to report or interact with the network.
  • the terminal receiving the multicast service considers that the original multicast cell reception is abnormal or changes under at least one of the following circumstances, and triggers the connection recovery process:
  • the terminal When the terminal is in the current multicast service cell, it can no longer receive multicast services
  • the quality is poor enough to meet certain conditions; for example:
  • the failure to receive multicast service data reaches N2 times, or is higher than a certain proportion
  • multicast service data is correctly received less than N3 times, or less than a certain proportion
  • the reception quality does not meet the requirements.
  • the block error rate does not meet the QoS indicator or is higher than the threshold;
  • the multicast signal measurement meets a certain threshold, for example, the multicast RSRP is lower than a threshold;
  • the terminal can report to the network when the power is replenished or the power is sufficient;
  • the terminal When the terminal itself evaluates the reception quality and does not meet the requirements, it can also initiate a report to the network.
  • the terminal can immediately make an RRC connection recovery request, interact with and report to the network side. Due to this situation, the purpose of the terminal is not simply to obtain updated configuration in order to continue receiving multicast services. Therefore, in this case, the terminal can no longer carry additional information in the connection recovery request, which is to enter Connected state.
  • the terminal When the terminal enters the RRC Connected state through the normal connection recovery request and the connection recovery process sent by the network side, the terminal can perform at least one of the following:
  • the terminal requests the Connected state from the network to receive multicast services
  • the terminal reports its own Multicast reception information to the network, such as various triggered indicators and measurement results, etc., so that the network side can provide reasonable solutions;
  • the terminal initiates the leaving process of the multicast service to the core network (the corresponding process of joining indicates that the terminal is no longer interested in the multicast service).
  • the terminal leaving information will subsequently be notified by the core network node to the serving base station, and the serving base station can then transfer the terminal to the core network.
  • De-configure the multicast service configuration When the terminal has no other service transmission needs, it can be released back to the Idle state;
  • the terminal's request and report to the network side will cause the network to perform reasonable operations.
  • terminals with poor links can be kept in Connected, such as point-to-point path (point-to-point leg, PTP leg), etc. Supplement and guarantee the transmission effect.
  • the first message is also used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the above-mentioned first message may explicitly or implicitly indicate at least one of the above-mentioned items.
  • the purpose of the above request for connection recovery may be to obtain the new configuration of the multicast service, or to quickly enter the connection state.
  • the network side device can quickly respond to the content indicated by the first message to meet the communication needs of the terminal.
  • the signaling content carried in the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send;
  • the message header of the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the signaling content carried in the above-mentioned first message is used to indicate the above-mentioned at least one item, and may include indication information indicating the above-mentioned at least one item in the above-mentioned signaling content.
  • the message header of the above-mentioned first message is used to indicate the above-mentioned at least one item, the signaling content carried by the first message remains different, and the message header of the first message carries indication information indicating the above-mentioned at least one item.
  • the first message is RRC signaling
  • the content of the RRC signaling remains unchanged, but information is added to the other layer 2 header (L2 header) of the RRC signaling to indicate at least one of the above, for example: media access control header (MAC header), Radio Link Control header (Radio Link Control header, RLC header), Packet Data Convergence Protocol header (PDCP header) and other added information indicate at least one of the above.
  • MAC header media access control header
  • Radio Link Control header Radio Link Control header
  • PDCP header Packet Data Convergence Protocol header
  • At least one of the above items may be indicated through signaling content or a message header, thereby improving the flexibility of the message format.
  • the first message is sent together with a buffer status report (Buffer Status Report, BSR).
  • BSR Buffer Status Report
  • the above-mentioned first message and the BSR may be sent together.
  • the first message and the BSR may be sent at the same time.
  • the BSR can be reported while requesting connection recovery, so that the network side device can determine whether to subsequently authorize uplink resources for the terminal to transmit uplink data based on whether the BSR exists, or to directly use release signaling (release signaling) to carry updated configuration information. Directly release the terminal, make timely judgment on terminal needs, and improve the timeliness and efficiency of data transmission of the terminal.
  • release signaling release signaling
  • the method further includes the following:
  • the terminal receives a connection recovery (RRC Resume) message
  • the terminal receives an RRC release message, where the RRC release message carries the configuration of the first multicast service change.
  • connection recovery message and RRC release message can be based on the terminal's connection recovery request and the terminal context information, and the network side can determine whether it needs to send a connection recovery to the terminal, or directly carry the new multicast service configuration information in the release message.
  • the terminal context information stores the terminal's Multicast cell information and/or the version information of the multicast configuration obtained by the terminal, which facilitates the network side to determine whether the latest configuration needs to be sent to the terminal.
  • the terminal can access the connection state in time or obtain the changed configuration.
  • the method further includes:
  • the terminal receives the first multicast service in an inactive state based on the changed configuration of the first multicast service.
  • the terminal can receive the first multicast service in an inactive state in a timely manner based on the changed configuration, so as to improve the effect of the terminal receiving the multicast service.
  • the terminal receives the first multicast service in an inactive state based on the changed configuration of the first multicast service, including at least one of the following:
  • the terminal resets or resets the RLC layer and the lower layer based on the changed configuration of the first multicast service, and starts receiving the first multicast service from a new protocol stack;
  • the terminal performs continuous reception of the first multicast service at the PDCP layer based on the changed configuration of the first multicast service.
  • the above-mentioned resetting or resetting the RLC layer and the lower layer, and starting to receive the first multicast service from the new protocol stack may be: resetting or resetting the RLC layer and the lower layer, and starting to receive the first multicast service from the initial state of the new protocol stack.
  • the first multicast service may be: resetting or resetting the RLC layer and the lower layer, and starting to receive the first multicast service from the initial state of the new protocol stack.
  • the above-mentioned continuous reception of the first multicast service at the PDCP layer may include the following:
  • the PDCP layer sorts the data packets of the first multicast service based on at least one of the sequence number (SN) and the count value (COUNT value) of the data packet;
  • the data packets of the first multicast service are sorted at the PDCP layer based on at least one of the sequence number SN and the count value of the data packet.
  • the above explicit indication on the network side may be to directly instruct the PDCP entity that the SN/COUNT values of its data packets can continue to be sorted before and after reconfiguration.
  • the above implicit indication on the network side can be that if the multicast/broadcast service radio bearer (Multicast/Broadcast Service, MBS) corresponding to a PDCP entity satisfies the one-to-one mapping between the quality of service flow (QoS flow) and the MRB, or all-to-one (all to one) mapping, it can be considered that the MRB can synchronize the PDCP SN/COUNT value between different base stations, so the SN/COUNT value of its data packet can continue to be used before and after reconfiguration. Sorting is performed; otherwise, the PDCP entity is re-established, and there is no need to perform sorting work before and after reconfiguration.
  • MBS multicast/broadcast service radio bearer
  • the method further includes at least one of the following:
  • the terminal sends a second message to the network side device, where the second message is used to request receiving the first multicast service in the connected state;
  • the terminal reports the reception quality information of the terminal for the first multicast service to the network side device;
  • the terminal initiates a leaving process of the first multicast service.
  • the first multicast service can be quickly received in the connected state through the above-mentioned second message.
  • the above reception quality information may be decoding failure rate, decoding success rate, block error rate, number of consecutive decoding failed data blocks, reception failure probability within a certain period of time, measurement results and other quality information.
  • the network side device can provide reasonable solutions, such as variable configuration or allowing the terminal to enter the connected state to receive multicast services when the reception quality is poor.
  • This embodiment mainly describes the multicast configuration changes, specifically as follows:
  • the terminal In a Multicast cell, due to situation changes, when the multicast service configuration is changed, the terminal needs to be notified. After the terminal is notified, it can immediately make a connection recovery request to the network.
  • the terminal can take at least one of the following methods to more clearly indicate the purpose of resuming the connection:
  • connection recovery request message carries information indicating that the terminal is for the purpose of updating the multicast service configuration
  • the terminal can trigger BSR and send it together with the connection recovery request message if the uplink resources can accommodate it;
  • the information about the subsequent data can be carried in other ways that do not increase overhead, for example, using the R field in the MAC subheader. Or use a special Logical Channel Identity (LCID) field, etc., to show distinction;
  • LCID Logical Channel Identity
  • connection recovery request message can be sent.
  • At least one of the following methods can be used for subsequent processing:
  • At least one of the following records can be saved in the terminal Context:
  • the multicast service identifier that the terminal is interested in or is receiving such as Temporary Mobile Group Identity (TMGI);
  • G-RNTI Group-Radio Network Temporary Identity
  • DRX DRX
  • MRB MRB
  • RLC bearer Radio Link Control Bearer
  • the home cell or effective area information of the multicast service currently received by the terminal such as cell identification, Public Land Mobile Network (PLMN) identification, effective area information, etc.;
  • PLMN Public Land Mobile Network
  • the configuration version information of the multicast service currently received by the terminal For example, the current configuration version is 0.
  • the purpose of retaining the above information may be for the network side to determine the terminal's interested service information and current configuration information as quickly as possible, so that the network side can decide whether to send configuration update information to the terminal under various circumstances. For example, if the cell configuration version information sent by the current multicast service is inconsistent with the version information stored in the terminal context, it means that the terminal configuration has not been updated in time, and new configuration needs to be resent to the terminal. In the absence of version information, you can also compare the current configuration with the configuration stored in the terminal context. If they are the same, it means that the terminal configuration is the latest version, and there is no need to send an update. If they are different, it means that an updated configuration needs to be sent.
  • the terminal When the terminal receives the new configuration, generally, for RLC and lower layers, it can reset or reset and start receiving from the initialization state of the new protocol stack.
  • the PDCP layer because it has important functions such as business continuity and reordering, needs to meet continuity requirements as much as possible.
  • Explicit means directly indicating that the SN/COUNT values of the PDCP packets can continue to be sorted before and after reconfiguration. Implicit way, for example, when the MRB corresponding to a PDCP entity satisfies the one-to-one mapping between QoS flow and MRB, or all to one mapping, it can be considered that the MRB can achieve PDCP SN/COUNT between different base stations. Value synchronization, so before and after reconfiguration, the SN/COUNT value of its data packets can continue to be sorted; otherwise, the PDCP entity is re-established, and there is no need to perform sorting work before and after reconfiguration.
  • the terminal camps in the first cell in an inactive state and receives the first multicast service; when the terminal meets the preset conditions, the terminal sends a first message, and the first message is To request connection recovery.
  • This can support the terminal to receive multicast services in the inactive state, thus reducing the network load. Additionally, by sending the first message It can be realized that when the terminal receives multicast services in the inactive state, it can promptly request connection recovery to improve the flexibility of terminal state switching.
  • the terminal can also perform connection recovery in time, obtain updated multicast configuration, new cell multicast configuration, new multicast transmission method from the network side, and report some reception exceptions, ensuring that the terminal The timely and normal reception of multicast services improves the terminal experience and system efficiency while ensuring the reception effect.
  • Figure 3 is a flow chart of another connection recovery method provided by an embodiment of the present application. As shown in Figure 3, it includes the following steps:
  • the network side device receives the first message sent by the terminal, and the first message is used to request connection recovery;
  • the terminal is a terminal camping on the first cell in an inactive state to receive the first multicast service.
  • the method before the network side device receives the first message sent by the terminal, the method further includes:
  • the network side device sends a notification message to the terminal, where the notification message is used to notify that the configuration of the first multicast service changes.
  • the first message is also used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the signaling content carried in the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send;
  • the message header of the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the first message is received together with a buffer status report BSR.
  • the method further includes the following:
  • the network side device sends a connection recovery message to the terminal
  • the network side device sends a radio resource control RRC release message to the terminal, where the RRC release message carries the configuration of the first multicast service change.
  • the RRC release message is sent to the terminal.
  • the network side device determines that the terminal needs to continue receiving the first multicast service in an inactive state based on the terminal context of the terminal, and the terminal context includes at least one of the following:
  • the service identification information of the multicast service that the terminal is interested in or is receiving
  • the home cell information of the multicast service that the terminal is interested in or is receiving
  • Valid area information of the multicast service that the terminal is interested in or is receiving is included in
  • the configuration information includes at least one of the following:
  • the method further includes at least one of the following:
  • the network side device receives a second message sent by the terminal, where the second message is used to request receiving the first multicast service in a connected state;
  • the network side device receives the reception quality information of the terminal for the first multicast service reported by the terminal;
  • the network side device accepts the leaving process of the first multicast service initiated by the terminal.
  • this embodiment is an implementation of the network-side device corresponding to the embodiment shown in Figure 2.
  • the relevant description of the embodiment shown in Figure 2 please refer to the relevant description of the embodiment shown in Figure 2 to avoid repeated explanations. No further details will be given in this embodiment.
  • connection recovery device 400 includes:
  • the first receiving module 401 is used to camp on the first cell in the inactive state and receive the first multicast service
  • the first sending module 402 is configured to send a first message when the terminal meets the preset conditions, where the first message is used to request connection recovery.
  • the terminal meeting preset conditions includes at least one of the following:
  • the terminal receives a notification message sent by the network side, where the notification message is used to notify that the configuration of the first multicast service has changed;
  • the terminal performs cell reselection
  • the terminal performs mobility management
  • the terminal is no longer interested in the first multicast service
  • the quality with which the terminal receives the first multicast service matches the preset quality, and the preset quality indicates that the first multicast service cannot continue to be received.
  • the terminal performs cell reselection, including at least one of the following:
  • the terminal is reselected from the first cell to a second cell, and the first cell is a multicast service cell that sends the first multicast service;
  • the terminal is reselected from a first effective area to a third cell, the first effective area is an effective area of the first multicast service, and the third cell does not belong to the first effective area.
  • the terminal performs mobility management, including at least one of the following due to mobility:
  • the terminal camps on the first cell and stops receiving the first multicast service
  • the measurement result of the terminal for the reference signal of the first cell matches a first preset measurement result, and the first preset measurement result indicates that the terminal cannot continue to receive the first multi-channel signal in the first cell. Broadcasting business;
  • the quality of the first multicast service received by the terminal matches the preset quality, and the preset quality indicates that the terminal The first multicast service cannot continue to be received in the first cell;
  • the measurement result of the multicast channel or multicast signal by the terminal matches a second preset measurement result, and the second preset measurement result indicates that the terminal cannot continue to receive the first multicast in the first cell. business;
  • the information of the terminal indicates that it cannot continue to receive the first multicast service.
  • the quality of the first multicast service received by the terminal matches the preset quality, including at least one of the following:
  • the terminal fails to receive data of the first multicast service for N1 consecutive times;
  • the number of failures for the terminal to receive data of the first multicast service reaches N2 times
  • the data failure ratio of the terminal in receiving the first multicast service is higher than or equal to the first preset ratio
  • the terminal does not correctly receive the first multicast service
  • the number of times the terminal correctly receives the first multicast service is less than N3 times;
  • the proportion of the terminal correctly receiving the first multicast service is lower than the second preset proportion
  • the data failure ratio of the terminal in receiving the first multicast service is higher than or equal to the third preset ratio
  • the number of times the terminal correctly receives the first multicast service is less than N9 times;
  • the proportion of the terminal correctly receiving the first multicast service is lower than the fourth preset proportion
  • the quality of the first multicast service received by the terminal does not meet the preset requirements
  • N1 to N10 are positive integers.
  • the terminal cannot be interested in the first multicast service, including: the terminal is no longer interested in the first multicast service due to movement or cell reselection; and/or
  • the quality of the terminal receiving the first multicast service matching the preset quality includes: not caused by movement or cell reselection, the quality of the terminal receiving the first multicast service matching the preset quality.
  • the first message is also used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the signaling content carried in the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send;
  • the message header of the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the first message is sent together with the cache status report BSR.
  • the device also includes the following:
  • the second receiving module is used to receive the connection recovery message
  • the third receiving module is configured to receive a radio resource control RRC release message, where the RRC release message carries the configuration of the first multicast service change.
  • the device also includes:
  • the fourth receiving module is configured to receive the first multicast service in an inactive state based on the changed configuration of the first multicast service.
  • the fourth receiving module is used for at least one of the following:
  • the continuous reception of the first multicast service at the PDCP layer includes the following:
  • the data packets of the first multicast service are sorted at the PDCP layer based on at least one of the sequence number SN and the count value of the data packet.
  • the device also includes at least one of the following:
  • a second sending module configured for the terminal to send a second message to the network side device, where the second message is used to request receiving the first multicast service in a connected state;
  • a third sending module configured to report the reception quality information of the terminal for the first multicast service to the network side device
  • the fourth sending module is used to initiate the leaving process of the first multicast service.
  • the above connection restoration device can reduce network load.
  • connection recovery device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip.
  • the electronic device may be a terminal or other devices other than the terminal.
  • the terminal may include but is not limited to the types of terminals listed in the embodiments of this application, and other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiments of this application.
  • NAS Network Attached Storage
  • connection recovery device provided by the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 2 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • Figure 5 is a structural diagram of another connection recovery device provided by an embodiment of the present application. As shown in Figure 5, the connection recovery device 500 includes:
  • the first receiving module 501 is used to receive a first message sent by the terminal, where the first message is used to request connection recovery;
  • the terminal is a terminal camping on the first cell in an inactive state to receive the first multicast service.
  • the device also includes:
  • the first sending module is configured to send a notification message to the terminal, where the notification message is used to notify that the configuration of the first multicast service has changed.
  • the first message is also used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the signaling content carried in the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send;
  • the message header of the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the first message is received together with a buffer status report BSR.
  • the device also includes the following:
  • a second sending module configured to send a connection recovery message to the terminal
  • the third sending module is configured to send a radio resource control RRC release message to the terminal, where the RRC release message carries the configuration of the first multicast service change.
  • the RRC release message is sent to the terminal.
  • the network side device determines that the terminal needs to continue receiving the first multicast service in an inactive state based on the terminal context of the terminal, and the terminal context includes at least one of the following:
  • the service identification information of the multicast service that the terminal is interested in or is receiving
  • the home cell information of the multicast service that the terminal is interested in or is receiving
  • Valid area information of the multicast service that the terminal is interested in or is receiving is included in
  • the configuration information includes at least one of the following:
  • the device also includes at least one of the following:
  • a second receiving module configured to receive a second message sent by the terminal, where the second message is used to request receiving the first multicast service in the connected state;
  • a third receiving module configured to receive the reception quality information of the terminal for the first multicast service reported by the terminal;
  • An accepting module configured to accept the leaving process of the first multicast service initiated by the terminal.
  • the above multicast service receiving device can reduce network load.
  • the system information sending device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip.
  • the electronic device may be a network side device.
  • the system information sending device provided by the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 3 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • this embodiment of the present application also provides a communication device 600, which includes a processor 601 and a memory 602.
  • the memory 602 stores programs or instructions that can be run on the processor 601, for example.
  • the communication device 600 is a terminal
  • the program or instruction is executed by the processor 601
  • each step of the terminal-side connection recovery method embodiment is implemented, and the same technical effect can be achieved.
  • the communication device 600 is a network-side device
  • each step of the above-mentioned connection recovery method embodiment on the network-side device side is implemented, and the same technical effect can be achieved.
  • the steps are not included here. Again.
  • Embodiments of the present application also provide a terminal, including a processor and a communication interface.
  • the communication interface is used to camp in the first cell in an inactive state and receive the first multicast service; when the terminal meets preset conditions Next, a first message is sent, and the first message is used to request connection recovery.
  • This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment.
  • Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • FIG. 7 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.
  • the terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, a processor 710, etc. At least some parts.
  • the terminal 700 may also include a power supply (such as a battery) that supplies power to various components.
  • the power supply may be logically connected to the processor 710 through a power management system, thereby managing charging, discharging, and power consumption through the power management system. Management and other functions.
  • the terminal structure shown in FIG. 7 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or some components may be combined or arranged differently, which will not be described again here.
  • the input unit 704 may include a graphics processing unit (Graphics Processing Unit, GPU) 7041 and a microphone 7042.
  • the graphics processing unit 7041 is responsible for the image capture device (GPU) in the video capture mode or the image capture mode. Process the image data of still pictures or videos obtained by cameras (such as cameras).
  • the display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 707 includes a touch panel 7071 and at least one of other input devices 7072 .
  • Touch panel 7071 also called touch screen.
  • the touch panel 7071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 7072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.
  • the radio frequency unit 701 after receiving the downlink data from the network side device, the radio frequency unit 701 can transmit it to the processing unit 701.
  • the processor 710 performs processing; in addition, the radio frequency unit 701 can send uplink data to the network side device.
  • the radio frequency unit 701 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.
  • Memory 709 may be used to store software programs or instructions as well as various data.
  • the memory 709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc.
  • memory 709 may include volatile memory or non-volatile memory, or memory 709 may include both volatile and non-volatile memory.
  • non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM) , SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM).
  • RAM Random Access Memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM Double Data Rate SDRAM
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM enhanced synchronous dynamic random access memory
  • Synch link DRAM synchronous link dynamic random access memory
  • SLDRAM direct memory bus
  • the processor 710 may include one or more processing units; optionally, the processor 710 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above-mentioned modem processor may not be integrated into the processor 710.
  • the radio frequency unit 701 is used to camp on the first cell in an inactive state and receive the first multicast service; when the terminal meets the preset conditions, send a first message, and the first message is used to Request connection restoration.
  • the terminal meeting preset conditions includes at least one of the following:
  • the terminal receives a notification message sent by the network side, where the notification message is used to notify that the configuration of the first multicast service has changed;
  • the terminal performs cell reselection
  • the terminal performs mobility management
  • the terminal is no longer interested in the first multicast service
  • the quality with which the terminal receives the first multicast service matches the preset quality, and the preset quality indicates that the first multicast service cannot continue to be received.
  • the terminal performs cell reselection, including at least one of the following:
  • the terminal is reselected from the first cell to a second cell, and the first cell is a multicast service cell that sends the first multicast service;
  • the terminal is reselected from a first effective area to a third cell, the first effective area is an effective area of the first multicast service, and the third cell does not belong to the first effective area.
  • the terminal performs mobility management, including at least one of the following due to movement:
  • the terminal camps on the first cell and stops receiving the first multicast service
  • the measurement result of the terminal for the reference signal of the first cell matches a first preset measurement result, and the first preset measurement result indicates that the terminal cannot continue to receive the first multi-channel signal in the first cell. Broadcasting business;
  • the quality of the first multicast service received by the terminal matches the preset quality, and the preset quality indicates that the terminal cannot continue to receive the first multicast service in the first cell;
  • the measurement result of the multicast channel or multicast signal by the terminal matches a second preset measurement result, and the second preset measurement result indicates that the terminal cannot continue to receive the first multicast in the first cell. business;
  • the information of the terminal indicates that it cannot continue to receive the first multicast service.
  • the quality of the first multicast service received by the terminal matches the preset quality, including at least one of the following:
  • the terminal fails to receive data of the first multicast service for N1 consecutive times;
  • the number of failures for the terminal to receive data of the first multicast service reaches N2 times
  • the data failure ratio of the terminal in receiving the first multicast service is higher than or equal to the first preset ratio
  • the terminal does not correctly receive the first multicast service
  • the number of times the terminal correctly receives the first multicast service is less than N3 times;
  • the proportion of the terminal correctly receiving the first multicast service is lower than the second preset proportion
  • the data failure ratio of the terminal in receiving the first multicast service is higher than or equal to the third preset ratio
  • the number of times the terminal correctly receives the first multicast service is less than N9 times;
  • the proportion of the terminal correctly receiving the first multicast service is lower than the fourth preset proportion
  • the quality of the first multicast service received by the terminal does not meet the preset requirements
  • N1 to N10 are positive integers.
  • the terminal cannot be interested in the first multicast service, including: the terminal is no longer interested in the first multicast service due to movement or cell reselection; and/or
  • the quality of the terminal receiving the first multicast service matching the preset quality includes: not caused by movement or cell reselection, the quality of the terminal receiving the first multicast service matching the preset quality.
  • the first message is also used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the signaling content carried in the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send;
  • the message header of the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the first message is sent together with the cache status report BSR.
  • the radio frequency unit 701 is also used for the following:
  • Radio resource control RRC release message where the RRC release message carries the configuration of the first multicast service change.
  • the radio frequency unit 701 is also used to:
  • the terminal receives the first multicast service in an inactive state based on the changed configuration of the first multicast service.
  • the terminal receives the first multicast service in an inactive state based on the changed configuration of the first multicast service, and the radio frequency unit 701 is also used for at least one of the following:
  • the continuous reception of the first multicast service at the PDCP layer includes the following:
  • the data packets of the first multicast service are sorted at the PDCP layer based on at least one of the sequence number SN and the count value of the data packet.
  • the radio frequency unit 701 is also used for at least one of the following:
  • the above terminals can reduce network load.
  • An embodiment of the present application also provides a network side device, including a processor and a communication interface, wherein the communication interface is used to receive a first message sent by a terminal, and the first message is used to request connection recovery; wherein, the terminal It is a terminal that camps on the first cell in an inactive state and receives the first multicast service.
  • This network-side device embodiment corresponds to the above-mentioned network-side device-side method embodiment, and each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network-side device. embodiment, and can achieve the same technical effect.
  • the embodiment of the present application also provides a network side device.
  • the network side device 800 includes: an antenna 801 , a radio frequency device 802 , a baseband device 803 , a processor 804 and a memory 805 .
  • Antenna 801 is connected to radio frequency device 802.
  • the radio frequency device 802 receives information through the antenna 801 and sends the received information to the baseband device 803 for processing.
  • the baseband device 803 processes the information to be sent and sends it to the radio frequency device 802.
  • the radio frequency device 802 processes the received information and then sends it out through the antenna 801.
  • the method performed by the network side device in the above embodiment can be implemented in the baseband device 803, which includes a baseband processor.
  • the baseband device 803 may include, for example, at least one baseband board on which multiple chips are disposed, as shown in FIG. Program to perform the network device operations shown in the above method embodiments.
  • the network side device may also include a network interface 806, which is, for example, a common public radio interface (CPRI).
  • a network interface 806, which is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 800 in this embodiment of the present invention also includes: instructions or programs stored in the memory 805 and executable on the processor 804.
  • the processor 804 calls the instructions or programs in the memory 805 to execute each of the steps shown in Figure 5. The method of module execution and achieving the same technical effect will not be described in detail here to avoid duplication.
  • the radio frequency device 802 is used for the network side device to receive the first message sent by the terminal, and the first message is used to request connection recovery;
  • the terminal is a terminal camping on the first cell in an inactive state to receive the first multicast service.
  • the radio frequency device 802 is also used to:
  • the first message is also used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the signaling content carried in the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send;
  • the message header of the first message is used to indicate at least one of the following:
  • the terminal has uplink data to send.
  • the first message is received together with a buffer status report BSR.
  • the radio frequency device 802 is also used for one of the following:
  • the RRC release message is sent to the terminal.
  • the network side device determines that the terminal needs to continue receiving the first multicast service in an inactive state based on the terminal context of the terminal, and the terminal context includes at least one of the following:
  • the service identification information of the multicast service that the terminal is interested in or is receiving
  • the home cell information of the multicast service that the terminal is interested in or is receiving
  • Valid area information of the multicast service that the terminal is interested in or is receiving is included in
  • the configuration information includes at least one of the following:
  • the radio frequency device 802 is also used for at least one of the following:
  • the above network side devices can reduce network load.
  • Embodiments of the present application also provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the connection recovery method provided by the embodiments of the present application are implemented.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes computer readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.
  • An embodiment of the present application further provides a chip.
  • the chip includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the above connection recovery method embodiment. Each process can achieve the same technical effect. To avoid duplication, it will not be described again here.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
  • Embodiments of the present application further provide a computer program/program product.
  • the computer program/program product is stored in a storage medium.
  • the computer program/program product is executed by at least one processor to implement the above connection recovery method embodiment.
  • Each process can achieve the same technical effect. To avoid repetition, we will not go into details here.
  • Embodiments of the present application also provide a frequency domain resource determination system, including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the connection recovery method on the terminal side provided by the embodiment of the present application.
  • the network side device can The steps of executing the connection recovery method on the network side device side provided by the embodiment of the present application.
  • the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
  • the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk , CD), including several instructions to cause a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of this application.

Landscapes

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

Abstract

本申请公开了一种连接恢复方法、装置、终端及网络侧设备，属于通信技术领域，本申请实施例的连接恢复方法包括：终端在非激活态下驻留第一小区，并接收第一多播业务；在所述终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。

Description

连接恢复方法、装置、终端及网络侧设备
相关申请的交叉引用
本申请主张在2022年7月15日在中国提交的中国专利申请No.202210836819.6的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种连接恢复方法、装置、终端及网络侧设备。
背景技术
目前通信系统中只支持终端在连接态(Connected))下接收多播(multicast)业务，这样可能会使得大量终端保留在连接态进行多播业务接收，从而导致网络负荷较大。
发明内容
本申请实施例提供一种连接恢复方法、装置、终端及网络侧设备，能够解决网络负荷较大的问题。
第一方面，提供了一种连接恢复方法，包括：
终端在非激活态下驻留第一小区，并接收第一多播业务；
在所述终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。
第二方面，提供了一种连接恢复方法，包括：
网络侧设备接收终端发送第一消息，所述第一消息用于请求连接恢复；
其中，所述终端为在非激活状态下驻留第一小区接收第一多播业务的终端。
第三方面，提供了一种连接恢复装置，包括：
第一接收模块，用于在非激活态下驻留第一小区，并接收第一多播业务；
第一发送模块，用于在终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。
第四方面，提供了一种连接恢复装置，包括：
第一接收模块，用于接收终端发送第一消息，所述第一消息用于请求连接恢复；
其中，所述终端为在非激活状态下驻留第一小区接收第一多播业务的终端。
第五方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现本申请实施例提供的连接恢复方法的步骤。
第六方面，提供了一种终端，包括处理器及通信接口，其中，所述通信接口用于在非激活态下驻留第一小区，并接收第一多播业务；在终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。
第七方面，提供了一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现本申请实施例提供的连接恢复方法的步骤。
第八方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述通信接口用于接收终端发送第一消息，所述第一消息用于请求连接恢复；其中，所述终端为在非激活状态下驻留第一小区接收第一多播业务的终端。
第九方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现本申请实施例提供的终端侧的连接恢复方法的步骤，或者，所述程序或指令被处理器执行时实现本申请实施例提供的网络侧设备侧的连接恢复方法的步骤。
第十方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现本申请实施例提供的终端侧的连接恢复方法，或者，所述处理器用于运行程序或指令，实现本申请实施例提供的网络侧设备侧的连接恢复方法。
第十一方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现本申请实施例提供的终端侧的连接恢复方法的步骤，或者，所述计算机程序/程序产品被至少一个处理器执行以实现本申请实施例提供的网络侧设备侧的连接恢复方法的步骤。
第十二方面，提供了一种频域资源确定系统，包括：终端和网络侧设备，所述终端可用于执行本申请实施例提供的终端侧的连接恢复方法的步骤，所述网络侧设备可用于执行本申请实施例提供的网络侧设备侧的连接恢复方法的步骤。
在本申请实施例中，终端在非激活态下驻留第一小区，并接收第一多播业务；在所述终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。这样可以 支持终端在非激活态下接收多播业务，从而可以降低网络负荷。另外，通过发送第一消息可以实现终端在非激活态下接收多播业务的情况下，可以及时请求连接恢复，以提高终端状态切换的灵活性。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例提供的一种连接恢复方法的流程图；
图3是本申请实施例提供的另一种连接恢复方法的流程图；
图4是本申请实施例提供的一种连接恢复装置的结构图；
图5是本申请实施例提供的另一种连接恢复装置的结构图；
图6是本申请实施例提供的一种通信设备的结构图；
图7是本申请实施例提供的一种终端的结构图；
图8是本申请实施例提供的一种网络侧设备的结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(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)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统， 并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer，PC)、柜员机或者自助机等终端侧设备，可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，网络侧设备12也可以称为无线接入网设备、无线接入网(Radio Access Network,RAN)、无线接入网功能或无线接入网单元。网络侧设备12可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点或WiFi节点等，基站可被称为节点B、演进节点B(eNB)、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(Mobility Management Entity，MME)、接入移动管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户平面功能(User Plane Function，UPF)、策略控制功能(Policy Control Function，PCF)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)、边缘应用服务发现功能(Edge Application Server Discovery Function，EASDF)、统一数据管理(Unified Data Management，UDM)，统一数据仓储(Unified Data Repository，UDR)、归属用户服务器(Home Subscriber Server，HSS)、集中式网络配置(Centralized network configuration，CNC)、网络存储功能(Network Repository Function，NRF)，网络开放功能(Network Exposure Function，NEF)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的一种连接恢复方 法、装置、终端及网络侧设备进行详细地说明。
请参见图2，图2是本申请实施例提供的一种连接恢复方法的流程图，如图2所示，包括以下步骤，包括：
201、终端在非激活态下驻留第一小区，并接收第一多播业务。
其中，上述第一小区可以为发送上述第一多播业务的多播业务小区(multicast cell)，或者，上述第一小区可以为不发送第一多播业务的小区(非Multicast cell)，但上述终端驻留在该小区时，终端能够接收到第一多播业务。
本申请实施例中，多播业务可以表示为multicast业务，或者可以表示为多播/广播业务(Multicast/Broadcast Service，MBS)。
202、在所述终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。
上述预设条件可以是协议约定的，或者网络侧配置的，或者终端自行决定的。
上述第一消息可以是在上述第一小区发送，也可以是在第二小区发送，例如：终端在非激活态驻留第一小区接收第一多播业务，终端执行小区重选，重选到第二小区，并发送上述第一消息，其中，该第一小区，可以是Multicast小区，也可以是非Multicast小区，例如：与Multicast小区存在相同覆盖范围的其它小区，这里的相同覆盖范围可以是全部或者部分相同。
本申请实施例中，通过上述步骤可以支持终端在非激活态下接收多播业务，终端在非激活态时的网络负荷是小于终端在连接态时的网络负荷，因此，本申请实施例可以降低网络负荷。另外，对终端来说，非激活态的复杂度和耗电也低于连接态，因此，也可以降低终端的功耗。
另外，通过发送第一消息可以实现终端在非激活态下接收多播业务的情况下，可以及时请求连接恢复，以提高终端状态切换的灵活性。另外，通过请求连接恢复，可以从网络侧获得更新的多播配置、新小区多播配置、新的多播传输方式，以及上报一些接收异常情况，这样可以确保终端对多播业务的及时和正常接收，使得在保障接收效果的基础上提升了终端的体验和系统效率。
作为一种可选的实施方式，所述终端满足预设条件包括如下至少一项：
所述终端接收到网络侧发送的通知消息，所述通知消息用于通知所述第一多播业务的配置发生变更；
所述终端执行小区重选；
所述终端执行移动性管理；
所述终端对所述第一多播业务不再感兴趣；
所述终端接收所述第一多播业务的质量与预设质量匹配，所述预设质量表示不能继续接收所述第一多播业务。
上述通知消息可以包括如下至少一项：
寻呼消息、层一(Layer 1，L1)信令、媒体接入控制(Medium Access Control，MAC)信令、无线资源控制(Radio Resource Control，RRC)消息、公共信令。
本申请实施例中，本申请实施例中，多播业务的配置可以包括但不限于：多播/广播业务无线承载(MBS(Multicast/Broadcast Service)radio bear，MRB)配置、时域图案(pattern)、频域资源、动态调度信息等，其中，时域pattern可以包括周期长度、周期起始位置和周期内激活时长等配置
上述多播业务的配置发生变更可以是部分或者全部配置发生变更。
通过上述通知消息可以实现在第一多播业务的配置发生变更的情况下，请求连接恢复，以在连接态接收第一多播业务，或者请求获取第一多播业务的新配置。
上述终端执行小区重选可以是，终端重选到其他小区。
上述终端执行移动性管理可以是，终端执行移动性管理评估。
上述终端对所述第一多播业务不再感兴趣可以是，终端自行决定的不再对第一多播业务。例如：基于终端实现不再对第一多播业务，如终端是为了省电效果请求进入非激活态(Inactive)接收multicast业务，则终端可以在电量获得补充或者电量充足的情况下，向网络请求连接恢复。也就是说，本申请实施例中，向请求连接恢复可以基于终端实现发送。
该实施方式中，可以实现基于不同原因发起连接恢复，以提高多播业务接收的灵活性。
在一些实施方式中，上述终端执行小区重选，包括如下至少一项：
所述终端从所述第一小区重选到第二小区，所述第一小区为发送所述第一多播业务的多播业务小区；
所述终端从第一有效区域重选到第三小区，所述第一有效区域为所述第一多播业务的有效区域，且所述第三小区不属于所述第一有效区域。
上述终端从第一小区重选到第二小区也可以理解为，终端从所述第一小区选择到第二小区。该实施方式中，可以实现当UE从当前multicast业务的小区，发生了小区选择/重选到其它小区，则发起连接恢复。
上述重选到第三小区可以是，终端从当前multicast业务配置有效的小区，发生了小区选择/重选，重选到有效小区列表/有效小区范围之外的其它无效小区，则发起连接恢复。
在一个实施例如下：
该实施例主要描述小区重选，具体可以如下：
当终端从当前multicast cell发生了小区重选，或者终端从当前multicast配置有效的小区重选到了一个配置有效区域之外的小区时，意味着终端此时存储的multicast cell的配置不再生效，则终端也需要触发连接恢复，重新向网络申请新小区的配置或者传输方式。
终端在新小区进行连接恢复请求的发起，其中，发起的方式可以参见其他实施例或者实施方式，也可以采取不同的方式，将自己连接恢复请求的明确目的向网络进行表明。
对于网络侧新小区来说，接收终端的连接恢复请求消息，获得其中的终端ID信息，可以采取以下至少一种方式进行后续处理：
对终端进行连接恢复命令的发送，让终端进入连接态；当网络不能明确判断终端恢复连接的目的时，或者网络通过终端的指示发现有其它后续上行数据，或者网络侧有发送给该终端的其它下行信令或者下行数据时，或者终端的感兴趣业务发生变化时，或者新小区可以容纳终端在连接态进行multicast业务接收，或者新小区并不支持multicast业务等等，都可以让终端先进入连接态，进行数据传输或者信令过程，同时通过RRC重配置信令将multicast业务的新配置发送给终端，新小区可以将终端保留在Connected继续进行业务接收。或者在完成上述过程之后，网络可以再次向终端发送RRC释放(RRC Release)消息，释放其到非激活态(Inactive)进行业务接收。或者，由于新小区不支持multicast业务，可以将支持multicast业务的小区信息和配置发送给终端，或者为终端建立单播承载继续接收multicast业务。
对终端直接发送RRC Release消息，其中携带新小区配置；这种方式是信令开销最小且最快捷的获得新配置的方式，当网络可以判断或者预估终端就是为了multicast业务配置而发起连接恢复时，可以直接将multicast业务的新配置发送给终端，这个新配置可以并不是本小区支持的配置，也可以是内部基站(intra-gNB)下的其它小区支持的配置，也可以将其它小区例如小区id、频点信息等发给终端，同时直接释放其到Inactive进行业务接收。
同样的，对于小区重选情况，终端上下文(终端Context)里可以保留多播相关的信息，也是为了网络侧尽快的确定终端的感兴趣业务信息，以及终端当前的配置信息，便于网络侧在各种情况下决定，是否为终端发送新小区配置信息。例如：如果当前multicast业务配置所对应的小区与终端context里存储的Multicast小区不一致，说明终端发生了移动，需要给终端重新发送新的配置。在没有小区信息的情况下，也可以通过对比当前配置和终端context里存储的配置，如果一样，说明终端配置可以继续使用，不用发送更新，可选的配置不变情况也可以将当前小区的发送进度发送给终端，如将分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)计数(COUNT)信息发送给终端，便于终端尽快同步接收，如果不一样，则说明需要发送新配置。
在一些实施方式中，上述终端执行移动性管理，包括由于移动导致的如下至少一项：
所述终端驻留在所述第一小区，停止接收所述第一多播业务；
所述终端针对所述第一小区的参考信号的测量结果与第一预设测量结果匹配，所述第一预设测量结果表示所述终端在所述第一小区不能继续接收所述第一多播业务；
所述终端接收所述第一多播业务的质量与预设质量匹配，所述预设质量表示所述终端在所述第一小区不能继续接收所述第一多播业务；
所述终端对多播信道或者多播信号的测量结果与第二预设测量结果匹配，所述第二预设测量结果表示所述终端在所述第一小区不能继续接收所述第一多播业务；
所述终端的信息表示不能继续接收所述第一多播业务。
上述终端驻留在所述第一小区，停止接收所述第一多播业务可以是，终端驻留在第一小区，由于移动等原因导致终端需要停止接收所述第一多播业务。另外，上述停止接收所 述第一多播业务可以是，由于无法再接收第一多播放业务，而停止接收第一多播放业务。
上述第一预设测量结果、预设质量和第二预设测量结果可以是协议定义的值，或者网络侧配置的值。
上述测量结果可以是参考信号接收功率(reference signal received power，RSRP)、信噪比(Signal-to-Noise Ratio，SNR)、参考信号接收质量(Reference Signal Receiving Quality，RSRQ)等测量结果。
上述测量结果与第一预设测量结果匹配，所述第一预设测量结果表示所述终端在所述第一小区不能继续接收所述第一多播业务可以是，测量结果低于第一预设测量结果，即表示终端在所述第一小区如果还继续接收第一多播业务可能会接收不成功，因此，终端不能继续接收所述第一多播业务。
上述第二预设测量结果匹配，所述第二预设测量结果表示所述终端在所述第一小区不能继续接收所述第一多播业务可以是，测量结果低于第二预设测量结果，即表示终端在所述第一小区如果还继续接收第一多播业务可能会接收不成功，因此，终端不能继续接收所述第一多播业务。
上述第一多播业务的质量可以如解码失败率、解码成功率、误块率、连续解码失败数据块数量、一定时长内接收失败概率等质量信息。
上述质量与预设质量匹配，所述预设质量表示所述终端在所述第一小区不能继续接收所述第一多播业务可以是，解码失败率高于预设值，即表示不能继续接收所述第一多播业务，或者，解码成功率低于预设值，即表示不能继续接收所述第一多播业务。需要说明的是，针对不同的接收参数，上述预设值的取值可以不同。
上述终端的信息表示不能继续接收所述第一多播业务可以是，基于终端实现的信息，确定不能继续接收第一多播业务，例如：终端自己评估的接收质量信息不满足要求，或者终端的电量信息。
需要说明的是，一些实施方式中，上述至少一项不由移动导致的情况下，也可以触发终端发送上述第一消息。
在一些实施方式中，所述终端接收所述第一多播业务的质量与预设质量匹配，包括如下至少一项：
所述终端连续N1次接收所述第一多播业务的数据失败；
在第一时间窗口内，所述终端接收所述第一多播业务的数据失败次数达到N2次；
在第二时间窗口内，所述终端接收所述第一多播业务的数据失败比例高于或者等于第一预设比例；
在第一持续时间内，所述终端没有正确接收到所述第一多播业务；
在第三时间窗口内，所述终端正确接收到所述第一多播业务的次数少于N3次；
在第三时间窗口内，所述终端正确接收到所述第一多播业务的比例低于第二预设比例；
在连续的N4个非连续接收(Discontinuous Reception，DRX)周期内，所述终端没有 正确接收到所述第一多播业务；
在连续的N5个DRX周期内，所述终端接收所述第一多播业务的数据失败次数达到N6次；
在连续的N7个DRX周期内，所述终端接收所述第一多播业务的数据失败比例高于或者等于第三预设比例；
在连续的N8个DRX周期内，所述终端正确接收到所述第一多播业务的次数少于N9次；
在连续的N10个DRX周期内，所述终端正确接收到所述第一多播业务的比例低于第四预设比例；
所述终端接收所述第一多播业务的质量不满足预设要求；
其中，N1至N10为正整数。
上述N1至N10为协议定义的，或者网络侧配置，或者终端决定的。
上述时间窗口、持续时间、预设比例、预设要求为协议定义的，或者网络侧配置，或者终端决定的。
上述接收所述第一多播业务的数据失败可以是，接收第一多播业务的数据块失败，其中，数据块失败可以通过物理下行共享信道(Physical downlink shared channel，PDSCH)解码失败来体现。
在一些实施方式中，可以不配置第一时间窗口，例如，只要终端接收一多播业务的数据失败次数达到N2次，则发送上述第一消息。
另外，上述描述的到达可以理解为大于或者等于，如终端接收第一多播业务的数据失败次数大于或者等于N2次。
该实施方式中，可以实现从多个维度确定是否在第一小区是否能继续接收所述第一多播业务，需要说明的是，这里在第一小区接收第一多播业务是指终端驻留在第一小区，但第一多播业务可以是第一小区发送的，也可以是其他小区发送的。
一个实施例如下：
该实施例主要描述的是移动性，具体可以如下：
移动性和上述实施例描述的小区重选具有一定的类似性，其中，小区重选的触发和判断遵从协议定义的终端空闲态(Idle态)的移动规则。但multicast业务接收具有特殊性，由于终端可以不驻留在multicast cell，但能够在multicast cell接收多播业务，类似于多接收能力，保持一个小区驻留，另一个小区接收多播。在驻留小区进行协议定义的Idle移动规则，例如小区选择重选等，而在接收multicast cell可以基于另一套规则判断其是否能够继续接收。
在这种情况下，接收multicast业务的终端在如下至少一种情况下，认为原有multicast cell接收不能继续，触发连接恢复过程：
当终端从当前multicast业务的小区，其RSRP低于门限，如公共参考信号的RSRP低 于门限；
当终端从当前multicast业务的小区，无法再接收multicast业务；
当终端从当前multicast业务的小区，接收multicast业务质量，差到了满足一定条件；例如如下至少一项：
连续N1次接收multicast业务数据块失败；
在窗口T1内，接收multicast业务数据失败达到N2次，或者高于一定比例；
持续T2时间，没有正确进行multicast业务接收；
在窗口T3内，正确接收multicast业务数据少于N3次，或者低于一定比例；
持续N4个DRX周期(DRX cycle)，没有正确接收multicast业务；
持续N5个DRX cycle，接收multicast业务数据失败达到N6次，或者高于一定比例；
持续N7个DRX cycle，正确接收multicast业务数据少于N3次，或者低于一定比例；
接收质量不满足要求，例如：误块率不满足服务质量(Quality of Service，QoS)指标，或者高于门限，又例如：路径损耗参考的RSRP低于门限值；
当终端从当前multicast业务的小区，对于multicast信号测量，满足一定门限，如multicast RSRP低于一个门限；
其它，基于终端实现，例如：当终端自己评估接收质量不满足要求，也可以向网络发起上报。
在满足上述条件之后，终端从当前驻留小区，发起RRC恢复请求(RRC Resume Request)过程，该过程可以同其他实施例，终端也可以在连接恢复请求的过程中尽量携带自己的目的信息。
对于网络侧新小区来说，接收终端的连接恢复请求消息，获得其中的终端ID信息，可以采取如上述小区重选实施例中对应部分所列进行后续处理。
同样的，对于更换小区情况，终端Context里也可以保留多播相关的信息，也是为了网络侧尽快的确定终端的感兴趣业务信息，以及终端当前的配置信息，便于网络侧在各种情况下决定，是否为终端发送新小区配置信息。例如：如果当前multicast业务配置所对应的小区与终端context里存储的Multicast cell不一致，说明终端发生了移动，需要给终端重新发送新的配置。在没有小区信息的情况下，也可以通过对比当前配置和终端context里存储的配置，如果一样，说明终端配置可以继续使用，不用发送更新，可选的配置不变情况也可以将当前小区的发送进度(例如PDCP COUNT信息)发送给终端，便于终端尽快同步接收，如果不一样，则说明需要发送新配置。
在一些实施方式中，所述终端对所述第一多播业务不能感兴趣，包括：不因移动或者小区重选导致的，所述终端对所述第一多播业务不再感兴趣；和/或
所述终端接收所述第一多播业务的质量与预设质量匹配包括：不因移动或者小区重选导致的，终端接收所述第一多播业务的质量与预设质量匹配。
上述不因移动或者小区重选导致的，所述终端对所述第一多播业务不再感兴趣可以是， 在不涉及移动或者换小区，当终端归属或者驻留小区不变的情况下，依然会发生一些情况的变化，使得终端对所述第一多播业务不再感兴趣，从而向网络上报或者交互。
上述不因移动或者小区重选导致的，终端接收所述第一多播业务的质量与预设质量匹配可以是，在不涉及移动或者换小区，当终端归属或者驻留小区不变的情况下，依然会发生一些情况的变化，使得第一多播业务的质量变化，导致第一多播业务的质量与预设质量匹配。
该实施方式中，可以实现不因移动或者小区重选发起连接恢复，以提高终端接收多播业务的灵活性。
一个实施例如下：
该实施例主要描述接收质量差或者终端不感兴趣，具体可以如下：
在本实施例中，不涉及移动或者换小区的情况，当终端归属或者驻留小区不变的情况下，依然会发生一些情况的变化，使得终端需要跟网络上报或者交互。
在这种情况下，接收multicast业务的终端在如下至少一种情况下，认为原有multicast cell接收出现异常或者变化，触发连接恢复过程：
当终端从当前multicast业务的小区，无法再接收multicast业务；
当终端不再对multicast业务感兴趣；
当终端从当前multicast业务的小区，接收multicast业务质量，差到了满足一定条件；例如：
连续N1次接收multicast业务数据块失败；
在窗口T1内，接收multicast业务数据失败达到N2次，或者高于一定比例；
持续T2时间，没有正确进行multicast业务接收；
在窗口T3内，正确接收multicast业务数据少于N3次，或者低于一定比例；
持续N4个DRX cycle，没有正确接收multicast业务；
持续N5个DRX cycle，接收multicast业务数据失败达到N6次，或者高于一定比例；
持续N6个DRX cycle，正确接收multicast业务数据少于N3次，或者低于一定比例；
接收质量不满足要求，例如误块率不满足QoS指标，或者高于门限；
当终端从当前multicast业务的小区，对于multicast信号测量，满足一定门限，例如multicast RSRP低于一个门限；
其它，基于终端实现，例如：
如果终端是为了省电效果请求进入Inactive接收multicast业务，则终端可以在电量获得补充或者电量充足的情况下，向网络上报；
当终端自己评估接收质量不满足要求，也可以向网络发起上报。
在上述情况发生时，终端可以立即进行RRC连接恢复请求，与网络侧进行交互和上报。由于此种情况，终端的目的并不是单一的为了继续进行多播业务接收而获取更新的配置，因此在这种情况下，终端可以不再连接恢复请求中携带额外信息，就是目的为了进入 连接态。
当终端通过正常连接恢复请求和网络侧发送的连接恢复过程，进入RRC连接(RRC Connected)状态之后，终端可以进行如下至少一项：
终端向网络请求Connected状态接收multicast业务；
终端向网络上报自己的Multicast接收信息，例如触发的各项指标和测量结果等，便于网络侧给出合理的解决方案；
终端向核心网发起multicast业务的离开过程(加入的对应过程，表明终端不再对该多播业务感兴趣)，终端离开信息后续会由核心网节点通知给服务基站，服务基站就可以将该终端关于multicast业务的配置进行去配置，当终端没有其它业务传输需求时，就可以释放回Idle状态；
终端向网络侧的请求和上报，会使得网络做出合理的操作，例如对于链路不好的终端可以将其保留在Connected，例如点到点路径(point-to-point leg，PTP leg)等对传输效果进行补充和保障。
作为一种可选的实施方式，所述第一消息还用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
上述第一消息可以是显式或者隐式指示上述至少一项。
上述请求连接恢复的目的可以是获取多播业务的新配置，或者快速进入连接态。
该实施方式中，由于上述第一消息还用于指示如下至少一项，这样可以使得网络侧设备快速响应上述第一消息指示的内容，以满足终端的通信需求。
在一些实施方式中，所述第一消息携带的信令内容用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送；
或者，
所述第一消息的消息头用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
上述第一消息携带的信令内容用于指示上述至少一项，可以是在上述信令内容中包括指示上述至少一项的指示信息。
上述第一消息的消息头用于指示上述至少一项，第一消息携带的信令内容保持不同，在第一消息的消息头中携带指示上述至少一项的指示信息。例如：第一消息为RRC信令，该RRC信令内容保持不变，但在RRC信令的其它层二头(L2 header)里增加信息指示上述至少一项，例如：媒体接入控制头(MAC header)，无线链路控制头(Radio Link Control header，RLC header)，分组数据汇聚协议头(PDCP header)等增加信息指示上述至少一项。
该实施方式中，可以通过信令内容或者消息头指示上述至少一项，从而提高消息格式的灵活性。
作为一种可选的实施方式，所述第一消息与缓存状态报告(Buffer Status Report，BSR)一起发送。
上述第一消息和BSR一起发送可以是，第一消息和BSR同时发送。
这样可以实现在请求连接恢复的同时上报BSR，以使得网络侧设备基于BSR是否存在判断后续是进行上行资源授权用于终端传输上行数据，还是直接以释放信令(release信令)携带更新配置信息直接释放终端，对终端需求进行及时判断，并提高终端的数据传输及时性和效率。
作为一种可选的实施方式，发送第一消息之后，所述方法还包括如下一项：
所述终端接收连接恢复(RRC Resume)消息；
所述终端接收RRC释放消息，所述RRC释放消息携带所述第一多播业务变更的配置。
上述连接恢复消息和RRC释放消息可以是网络侧根据终端的连接恢复请求，结合终端上下文信息，判断是否需要给终端发送连接恢复，还是直接在释放消息里携带新的multicast业务配置信息。其中，在终端上下文信息里，存储终端的Multicast cell信息和/或终端拿到的multicast配置的版本信息，便于网络侧判断是否需要给终端发送最新的配置。
该实施方式中，可以实现终端及时接入连接态，或者获取变更的配置。
在一些实施方式中，所述终端接收RRC释放消息之后，所述方法还包括：
所述终端基于所述第一多播业务变更的配置，在非激活态接收所述第一多播业务。
该实施方式中，可以实现终端及时基于变更的配置在非激活态接收第一多播业务，以提高终端接收多播业务效果。
在一些实施方式中，所述终端基于所述第一多播业务变更的配置，在非激活态接收所述第一多播业务，包括如下至少一项：
所述终端基于所述第一多播业务变更的配置，对RLC层和下层进行复位或者重置，并从新协议栈开始接收所述第一多播业务；
所述终端基于所述第一多播业务变更的配置，在PDCP层进行所述第一多播业务的连续性接收。
上述对RLC层和下层进行复位或者重置，并从新协议栈开始接收所述第一多播业务可以是，对RLC层和下层进行复位或者重置，并从新协议栈的初始状开始接收所述第一多播业务。
上述在PDCP层进行所述第一多播业务的连续性接收，可以包括如下一项：
基于网络侧显式指示，在PDCP层基于数据包的序列号(Sequence Number，SN)和计数值(COUNT值)中的至少一项，对所述第一多播业务的数据包进行排序；
基于网络侧隐式指示，在PDCP层基于数据包的序列号SN和计数值中的至少一项，对所述第一多播业务的数据包进行排序。
上述网络侧显式指示可以是，直接指示PDCP实体在重配置之前和之后，其数据包的SN/COUNT值可以继续进行排序。
上述网络侧隐式指示可以是，一个PDCP实体所对应的多播/广播业务无线承载(Multicast/Broadcast Service，MBS)如果满足服务质量流(QoS flow)与MRB一对一映射，或者全对一(all to one)映射时，则可以认为该MRB在不同的基站之间可以做到PDCP SN/COUNT值的同步，因此在重配置之前和重配置之后，其数据包的SN/COUNT值可以继续进行排序；否则，PDCP实体重新建立，不用进行重配置前后的排序工作。
在一些实施方式中，在所述终端进入连接态之后，所述方法还包括如下至少一项：
所述终端向网络侧设备发送第二消息，所述第二消息用于请求在连接态接收所述第一多播业务；
所述终端向网络侧设备上报所述终端对于所述第一多播业务的接收质量信息；
所述终端发起所述第一多播业务的离开过程。
该实施方式中，通过上述第二消息可以快速在连接态接收第一多播业务。
上述接收质量信息可以是解码失败率、解码成功率、误块率、连续解码失败数据块数量、一定时长内接收失败概率、测量结果等质量信息。
通过上述接收质量信息可以让网络侧设备给合理的解决方案，如在接收质量较差的情况下，变量配置或者让终端进入连接态接收多播业务等。
一个实施例如下：
该实施例主要描述multicast配置变化，具体可以如下：
Multicast小区，由于情况变化，对multicast业务配置进行变更时，需要对终端进行通知，终端获得通知之后，可以立即向网络进行连接恢复请求。
终端在发送连接恢复请求时，可以采取以下至少一种方式，更加明确指明恢复连接的目的：
在连接恢复请求消息中，携带信息，指示终端是为了multicast业务配置更新的目的；
如果终端此时有其它上行数据要发，则可以触发BSR，在上行资源可以容纳的情况下，与连接恢复请求消息一起发送；
如果终端此时有其它上行数据要发，在上行资源不够容纳BSR的情况下，以其它不增加开销的方式携带后续还有数据这个信息，例如，利用MAC子头(MAC subheader)中的R域或者采用特殊的逻辑信道标识(Logical Channel Identity，LCID)域等，以示区分；
按照上行资源情况，可以只发送连接恢复请求消息。
对于网络侧来说，接收终端的连接恢复请求消息，获得其中的终端ID信息，可以采取以下至少一种方式进行后续处理：
对终端进行连接恢复命令的发送，让终端进入连接态；当网络不能明确判断终端恢复连接的目的时，或者网络通过终端的指示发现有其它后续上行数据，或者网络侧有发送给 该终端的其它下行信令或者下行数据时，或者终端的感兴趣业务发生变化时等等，都可以让终端先进入连接态，进行数据传输或者信令过程，同时通过RRC重配置信令将multicast业务的新配置发送给终端。在完成上述过程之后，网络可以再次向终端发送RRC Release消息，释放其到Inactive进行业务接收。
对终端直接发送RRC Release消息，其中携带更新后的新配置；这种方式是信令开销最小且最快捷的获得新配置的方式，当网络可以判断或者预估终端就是为了multicast业务配置更新而发起连接恢复时，可以直接将multicast业务更新后的配置发送给终端，同时直接释放其到Inactive进行业务接收。
特别的，对于一个Inactive终端来说，如果它需要在Inactive状态继续接收multicast业务，则终端Context里可以保存如下至少一项纪录：
终端感兴趣或者正在接收的multicast业务标识，例如临时移动群组标识(Temporary Mobile Group Identity，TMGI)；
终端感兴趣或者正在接收的multicast业务配置，例如组无线网络临时标识(Group-Radio Network Temporary Identity，G-RNTI)，DRX配置，MRB配置，无线链路控制承载(RLC bearer)配置等；
终端当前接收的multicast业务的归属小区或者有效区域信息，例如小区标识、公共陆地移动网络(Public Land Mobile Network，PLMN)标识、有效区域信息等；
终端当前接收的multicast业务其配置版本信息，例如当前配置版本为0。
保留上述信息的目的，可以是为了网络侧尽快的确定终端的感兴趣业务信息，以及当前的配置信息，便于网络侧在各种情况下决定，是否为终端发送配置更新信息。例如如果当前multicast业务发送的小区配置版本信息与终端context里存储的版本信息不一致，说明终端的配置没有及时更新，需要给终端重新发送新的配置。在没有版本信息的情况下，也可以通过对比当前配置和终端context里存储的配置，如果一样，说明终端配置为最新版本，不用发送更新，如果不一样，则说明需要发送更新配置。
终端接收到新配置，一般情况下，对于RLC及以下层，可以采取复位或者重置的方式，从新协议栈的初始化状态开始接收。而PDCP层，由于具有业务连续性和重排序等重要功能，需要尽量满足连续性需求。可以有隐式或者显式的连续性操作指示，显式就是直接指明该PDCP在重配置之前和之后，其数据包的SN/COUNT值可以继续进行排序。隐式方式，例如，当一个PDCP实体所对应的MRB如果满足QoS flow与MRB一对一映射，或者all to one映射时，则可以认为该MRB在不同的基站之间可以做到PDCP SN/COUNT值的同步，因此在重配置之前和重配置之后，其数据包的SN/COUNT值可以继续进行排序；否则，PDCP实体重新建立，不用进行重配置前后的排序工作。
在本申请实施例中，终端在非激活态下驻留第一小区，并接收第一多播业务；在所述终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。这样可以支持终端在非激活态下接收多播业务，从而可以降低网络负荷。另外，通过发送第一消息 可以实现终端在非激活态下接收多播业务的情况下，可以及时请求连接恢复，以提高终端状态切换的灵活性。
另外，本申请实施例中，终端还可以及时进行连接恢复，从网络侧获得更新的多播配置、新小区多播配置、新的多播传输方式，以及上报一些接收异常情况，确保了终端对多播业务的及时和正常接收，使得在保障接收效果的基础上提升了终端的体验和系统效率。
请参见图3，图3是本申请实施例提供的另一种连接恢复方法的流程图，如图3所示，包括以下步骤：
301、网络侧设备接收终端发送第一消息，所述第一消息用于请求连接恢复；
其中，所述终端为在非激活状态下驻留第一小区接收第一多播业务的终端。
可选的，所述网络侧设备接收终端发送第一消息之前，所述方法还包括：
所述网络侧设备向所述终端发送通知消息，所述通知消息用于通知所述第一多播业务的配置发生变更。
可选的，所述第一消息还用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
可选的，所述第一消息携带的信令内容用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送；
或者，
所述第一消息的消息头用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
可选的，所述第一消息与缓存状态报告BSR一起接收。
可选的，所述网络侧设备接收终端发送第一消息之后，所述方法还包括如下一项：
所述网络侧设备向所述终端发送连接恢复消息；
所述网络侧设备向所述终端发送无线资源控制RRC释放消息，所述RRC释放消息携带所述第一多播业务变更的配置。
可选的，在所述网络侧设备确定所述终端需要在非激活态继续接收所述第一多播业务的情况下，向所述终端发送所述RRC释放消息。
可选的，所述网络侧设备基于所述终端的终端上下文，确定所述终端需要在非激活态继续接收所述第一多播业务，所述终端上行下文包括如下至少一项：
所述终端感兴趣或者正在接收的多播业务的业务标识信息；
所述终端感兴趣或者正在接收的多播业务的配置信息；
所述终端感兴趣或者正在接收的多播业务的归属小区信息；
所述终端感兴趣或者正在接收的多播业务的有效区域信息。
可选的，所述配置信息包括如下至少一项：
配置、配置版本信息。
可选的，所述网络侧设备向所述终端发送连接恢复消息之后，所述方法还包括如下至少一项：
所述网络侧设备接收所述终端发送的第二消息，所述第二消息用于请求在连接态接收所述第一多播业务；
所述网络侧设备接收所述终端上报的所述终端对于所述第一多播业务的接收质量信息；
所述网络侧设备接受所述终端发起的所述第一多播业务的离开过程。
需要说明的是，本实施例作为与图2所示的实施例中对应的网络侧设备的实施方式，其具体的实施方式可以参见图2所示的实施例的相关说明，以为避免重复说明，本实施例不再赘述。
请参见图4，图4是本申请实施例提供的一种连接恢复装置的结构图，如图4所示，连接恢复装置400包括：
第一接收模块401，用于在非激活态下驻留第一小区，并接收第一多播业务；
第一发送模块402，用于在终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。
可选的，所述终端满足预设条件包括如下至少一项：
所述终端接收到网络侧发送的通知消息，所述通知消息用于通知所述第一多播业务的配置发生变更；
所述终端执行小区重选；
所述终端执行移动性管理；
所述终端对所述第一多播业务不再感兴趣；
所述终端接收所述第一多播业务的质量与预设质量匹配，所述预设质量表示不能继续接收所述第一多播业务。
可选的，所述终端执行小区重选，包括如下至少一项：
所述终端从所述第一小区重选到第二小区，所述第一小区为发送所述第一多播业务的多播业务小区；
所述终端从第一有效区域重选到第三小区，所述第一有效区域为所述第一多播业务的有效区域，且所述第三小区不属于所述第一有效区域。
可选的，所述终端执行移动性管理，包括由于移动导致的如下至少一项：
所述终端驻留在所述第一小区，停止接收所述第一多播业务；
所述终端针对所述第一小区的参考信号的测量结果与第一预设测量结果匹配，所述第一预设测量结果表示所述终端在所述第一小区不能继续接收所述第一多播业务；
所述终端接收所述第一多播业务的质量与预设质量匹配，所述预设质量表示所述终端 在所述第一小区不能继续接收所述第一多播业务；
所述终端对多播信道或者多播信号的测量结果与第二预设测量结果匹配，所述第二预设测量结果表示所述终端在所述第一小区不能继续接收所述第一多播业务；
所述终端的信息表示不能继续接收所述第一多播业务。
可选的，所述终端接收所述第一多播业务的质量与预设质量匹配，包括如下至少一项：
所述终端连续N1次接收所述第一多播业务的数据失败；
在第一时间窗口内，所述终端接收所述第一多播业务的数据失败次数达到N2次；
在第二时间窗口内，所述终端接收所述第一多播业务的数据失败比例高于或者等于第一预设比例；
在第一持续时间内，所述终端没有正确接收到所述第一多播业务；
在第三时间窗口内，所述终端正确接收到所述第一多播业务的次数少于N3次；
在第四时间窗口内，所述终端正确接收到所述第一多播业务的比例低于第二预设比例；
在连续的N4个非连续接收DRX周期内，所述终端没有正确接收到所述第一多播业务；
在连续的N5个DRX周期内，所述终端接收所述第一多播业务的数据失败次数达到N6次；
在连续的N7个DRX周期内，所述终端接收所述第一多播业务的数据失败比例高于或者等于第三预设比例；
在连续的N8个DRX周期内，所述终端正确接收到所述第一多播业务的次数少于N9次；
在连续的N10个DRX周期内，所述终端正确接收到所述第一多播业务的比例低于第四预设比例；
所述终端接收所述第一多播业务的质量不满足预设要求；
其中，N1至N10为正整数。
可选的，所述终端对所述第一多播业务不能感兴趣，包括：不因移动或者小区重选导致的，所述终端对所述第一多播业务不再感兴趣；和/或
所述终端接收所述第一多播业务的质量与预设质量匹配包括：不因移动或者小区重选导致的，终端接收所述第一多播业务的质量与预设质量匹配。
可选的，所述第一消息还用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
可选的，所述第一消息携带的信令内容用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送；
或者，
所述第一消息的消息头用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
可选的，所述第一消息与缓存状态报告BSR一起发送。
可选的，所述装置还包括如下一项：
第二接收模块，用于接收连接恢复消息；
第三接收模块，用于接收无线资源控制RRC释放消息，所述RRC释放消息携带所述第一多播业务变更的配置。
可选的，所述装置还包括：
第四接收模块，用于基于所述第一多播业务变更的配置，在非激活态接收所述第一多播业务。
可选的，所述第四接收模块用于如下至少一项：
基于所述第一多播业务变更的配置，对无线链路控制RLC层和下层进行复位或者重置，并从新协议栈开始接收所述第一多播业务；
基于所述第一多播业务变更的配置，在分组数据汇聚协议PDCP层进行所述第一多播业务的连续性接收。
可选的，所述在PDCP层进行所述第一多播业务的连续性接收，包括如下一项：
基于网络侧显式指示，在PDCP层基于数据包的序列号SN和计数值中的至少一项，对所述第一多播业务的数据包进行排序；
基于网络侧隐式指示，在PDCP层基于数据包的序列号SN和计数值中的至少一项，对所述第一多播业务的数据包进行排序。
可选的，所述装置还包括如下至少一项：
第二发送模块，用于所述终端向网络侧设备发送第二消息，所述第二消息用于请求在连接态接收所述第一多播业务；
第三发送模块，用于向网络侧设备上报所述终端对于所述第一多播业务的接收质量信息；
第四发送模块，用于发起所述第一多播业务的离开过程。
上述连接恢复装置可以降低网络负荷。
本申请实施例中的连接恢复装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于本申请实施例所列举的终端的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的连接恢复装置能够实现图2所示的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
请参见图5，图5是本申请实施例提供的另一种连接恢复装置的结构图，如图5所示，连接恢复装置500包括：
第一接收模块501，用于接收终端发送第一消息，所述第一消息用于请求连接恢复；
其中，所述终端为在非激活状态下驻留第一小区接收第一多播业务的终端。
可选的，所述装置还包括：
第一发送模块，用于向所述终端发送通知消息，所述通知消息用于通知所述第一多播业务的配置发生变更。
可选的，所述第一消息还用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
可选的，所述第一消息携带的信令内容用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送；
或者，
所述第一消息的消息头用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
可选的，所述第一消息与缓存状态报告BSR一起接收。
可选的，所述装置还包括如下一项：
第二发送模块，用于向所述终端发送连接恢复消息；
第三发送模块，用于向所述终端发送无线资源控制RRC释放消息，所述RRC释放消息携带所述第一多播业务变更的配置。
可选的，在所述网络侧设备确定所述终端需要在非激活态继续接收所述第一多播业务的情况下，向所述终端发送所述RRC释放消息。
可选的，所述网络侧设备基于所述终端的终端上下文，确定所述终端需要在非激活态继续接收所述第一多播业务，所述终端上行下文包括如下至少一项：
所述终端感兴趣或者正在接收的多播业务的业务标识信息；
所述终端感兴趣或者正在接收的多播业务的配置信息；
所述终端感兴趣或者正在接收的多播业务的归属小区信息；
所述终端感兴趣或者正在接收的多播业务的有效区域信息。
可选的，所述配置信息包括如下至少一项：
配置、配置版本信息。
可选的，所述装置还包括如下至少一项：
第二接收模块，用于接收所述终端发送的第二消息，所述第二消息用于请求在连接态接收所述第一多播业务；
第三接收模块，用于接收所述终端上报的所述终端对于所述第一多播业务的接收质量信息；
接受模块，用于接受所述终端发起的所述第一多播业务的离开过程。
上述多播业务接收装置可以降低网络负荷。
本申请实施例中的系统信息发送装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是网络侧设备。
本申请实施例提供的系统信息发送装置能够实现图3所示的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图6所示，本申请实施例还提供一种通信设备600，包括处理器601和存储器602，存储器602上存储有可在所述处理器601上运行的程序或指令，例如，该通信设备600为终端时，该程序或指令被处理器601执行时实现上述终端侧的连接恢复方法实施例的各个步骤，且能达到相同的技术效果。该通信设备600为网络侧设备时，该程序或指令被处理器601执行时实现上述网络侧设备侧的连接恢复方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，所述通信接口用于在非激活态下驻留第一小区，并接收第一多播业务；在终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图7为实现本申请实施例的一种终端的硬件结构示意图。
该终端700包括但不限于：射频单元701、网络模块702、音频输出单元703、输入单元704、传感器705、显示单元706、用户输入单元707、接口单元708、存储器709以及处理器710等中的至少部分部件。
本领域技术人员可以理解，终端700还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器710逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图7中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元704可以包括图形处理单元(Graphics Processing Unit，GPU)7041和麦克风7042，图形处理单元7041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元706可包括显示面板7061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板7061。用户输入单元707包括触控面板7071以及其他输入设备7072中的至少一种。触控面板7071，也称为触摸屏。触控面板7071可包括触摸检测装置和触摸控制器两个部分。其他输入设备7072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元701接收来自网络侧设备的下行数据后，可以传输给处理 器710进行处理；另外，射频单元701可以向网络侧设备发送上行数据。通常，射频单元701包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器709可用于存储软件程序或指令以及各种数据。存储器709可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器709可以包括易失性存储器或非易失性存储器，或者，存储器709可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器709包括但不限于这些和任意其它适合类型的存储器。
处理器710可包括一个或多个处理单元；可选的，处理器710集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器710中。
其中，射频单元701用于在非激活态下驻留第一小区，并接收第一多播业务；在所述终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。
可选的，所述终端满足预设条件包括如下至少一项：
所述终端接收到网络侧发送的通知消息，所述通知消息用于通知所述第一多播业务的配置发生变更；
所述终端执行小区重选；
所述终端执行移动性管理；
所述终端对所述第一多播业务不再感兴趣；
所述终端接收所述第一多播业务的质量与预设质量匹配，所述预设质量表示不能继续接收所述第一多播业务。
可选的，所述终端执行小区重选，包括如下至少一项：
所述终端从所述第一小区重选到第二小区，所述第一小区为发送所述第一多播业务的多播业务小区；
所述终端从第一有效区域重选到第三小区，所述第一有效区域为所述第一多播业务的有效区域，且所述第三小区不属于所述第一有效区域。
可选的，所述终端执行移动性管理，包括由于移动导致的如下至少一项：
所述终端驻留在所述第一小区，停止接收所述第一多播业务；
所述终端针对所述第一小区的参考信号的测量结果与第一预设测量结果匹配，所述第一预设测量结果表示所述终端在所述第一小区不能继续接收所述第一多播业务；
所述终端接收所述第一多播业务的质量与预设质量匹配，所述预设质量表示所述终端在所述第一小区不能继续接收所述第一多播业务；
所述终端对多播信道或者多播信号的测量结果与第二预设测量结果匹配，所述第二预设测量结果表示所述终端在所述第一小区不能继续接收所述第一多播业务；
所述终端的信息表示不能继续接收所述第一多播业务。
可选的，所述终端接收所述第一多播业务的质量与预设质量匹配，包括如下至少一项：
所述终端连续N1次接收所述第一多播业务的数据失败；
在第一时间窗口内，所述终端接收所述第一多播业务的数据失败次数达到N2次；
在第二时间窗口内，所述终端接收所述第一多播业务的数据失败比例高于或者等于第一预设比例；
在第一持续时间内，所述终端没有正确接收到所述第一多播业务；
在第三时间窗口内，所述终端正确接收到所述第一多播业务的次数少于N3次；
在第四时间窗口内，所述终端正确接收到所述第一多播业务的比例低于第二预设比例；
在连续的N4个非连续接收DRX周期内，所述终端没有正确接收到所述第一多播业务；
在连续的N5个DRX周期内，所述终端接收所述第一多播业务的数据失败次数达到N6次；
在连续的N7个DRX周期内，所述终端接收所述第一多播业务的数据失败比例高于或者等于第三预设比例；
在连续的N8个DRX周期内，所述终端正确接收到所述第一多播业务的次数少于N9次；
在连续的N10个DRX周期内，所述终端正确接收到所述第一多播业务的比例低于第四预设比例；
所述终端接收所述第一多播业务的质量不满足预设要求；
其中，N1至N10为正整数。
可选的，所述终端对所述第一多播业务不能感兴趣，包括：不因移动或者小区重选导致的，所述终端对所述第一多播业务不再感兴趣；和/或
所述终端接收所述第一多播业务的质量与预设质量匹配包括：不因移动或者小区重选导致的，终端接收所述第一多播业务的质量与预设质量匹配。
可选的，所述第一消息还用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
可选的，所述第一消息携带的信令内容用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送；
或者，
所述第一消息的消息头用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
可选的，所述第一消息与缓存状态报告BSR一起发送。
可选的，发送第一消息之后，所述射频单元701还用于如下一项：
接收连接恢复消息；
接收无线资源控制RRC释放消息，所述RRC释放消息携带所述第一多播业务变更的配置。
可选的，所述终端接收RRC释放消息之后，所述射频单元701还用于：
所述终端基于所述第一多播业务变更的配置，在非激活态接收所述第一多播业务。
可选的，所述终端基于所述第一多播业务变更的配置，在非激活态接收所述第一多播业务，射频单元701还用于如下至少一项：
基于所述第一多播业务变更的配置，对无线链路控制RLC层和下层进行复位或者重置，并从新协议栈开始接收所述第一多播业务；
基于所述第一多播业务变更的配置，在分组数据汇聚协议PDCP层进行所述第一多播业务的连续性接收。
可选的，所述在PDCP层进行所述第一多播业务的连续性接收，包括如下一项：
基于网络侧显式指示，在PDCP层基于数据包的序列号SN和计数值中的至少一项，对所述第一多播业务的数据包进行排序；
基于网络侧隐式指示，在PDCP层基于数据包的序列号SN和计数值中的至少一项，对所述第一多播业务的数据包进行排序。
可选的，在所述终端进入连接态之后，射频单元701还用于如下至少一项：
向网络侧设备发送第二消息，所述第二消息用于请求在连接态接收所述第一多播业务；
向网络侧设备上报所述终端对于所述第一多播业务的接收质量信息；
发起所述第一多播业务的离开过程。
上述终端可以降低网络负荷。
本申请实施例还提供一种网络侧设备，包括处理器及通信接口，其中，所述通信接口用于接收终端发送第一消息，所述第一消息用于请求连接恢复；其中，所述终端为在非激活状态下驻留第一小区接收第一多播业务的终端。该网络侧设备实施例与上述网络侧设备侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备 实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图8所示，该网络侧设备800包括：天线801、射频装置802、基带装置803、处理器804和存储器805。天线801与射频装置802连接。在上行方向上，射频装置802通过天线801接收信息，将接收的信息发送给基带装置803进行处理。在下行方向上，基带装置803对要发送的信息进行处理，并发送给射频装置802，射频装置802对收到的信息进行处理后经过天线801发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置803中实现，该基带装置803包括基带处理器。
基带装置803例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图8所示，其中一个芯片例如为基带处理器，通过总线接口与存储器805连接，以调用存储器805中的程序，执行以上方法实施例中所示的网络设备操作。
该网络侧设备还可以包括网络接口806，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的网络侧设备800还包括：存储在存储器805上并可在处理器804上运行的指令或程序，处理器804调用存储器805中的指令或程序执行图5所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
其中，射频装置802用于网络侧设备接收终端发送第一消息，所述第一消息用于请求连接恢复；
其中，所述终端为在非激活状态下驻留第一小区接收第一多播业务的终端。
可选的，所述网络侧设备接收终端发送第一消息之前，射频装置802还用于：
向所述终端发送通知消息，所述通知消息用于通知所述第一多播业务的配置发生变更。
可选的，所述第一消息还用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
可选的，所述第一消息携带的信令内容用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送；
或者，
所述第一消息的消息头用于指示如下至少一项：
请求连接恢复的目的；
所述终端有上行数据要发送。
可选的，所述第一消息与缓存状态报告BSR一起接收。
可选的，所述网络侧设备接收终端发送第一消息之后，射频装置802还用于如下一项：
向所述终端发送连接恢复消息；
向所述终端发送无线资源控制RRC释放消息，所述RRC释放消息携带所述第一多播 业务变更的配置。
可选的，在所述网络侧设备确定所述终端需要在非激活态继续接收所述第一多播业务的情况下，向所述终端发送所述RRC释放消息。
可选的，所述网络侧设备基于所述终端的终端上下文，确定所述终端需要在非激活态继续接收所述第一多播业务，所述终端上行下文包括如下至少一项：
所述终端感兴趣或者正在接收的多播业务的业务标识信息；
所述终端感兴趣或者正在接收的多播业务的配置信息；
所述终端感兴趣或者正在接收的多播业务的归属小区信息；
所述终端感兴趣或者正在接收的多播业务的有效区域信息。
可选的，所述配置信息包括如下至少一项：
配置、配置版本信息。
可选的，所述网络侧设备向所述终端发送连接恢复消息之后，射频装置802还用于如下至少一项：
接收所述终端发送的第二消息，所述第二消息用于请求在连接态接收所述第一多播业务；
接收所述终端上报的所述终端对于所述第一多播业务的接收质量信息；
接受所述终端发起的所述第一多播业务的离开过程。
上述网络侧设备可以降低网络负荷。
本申请实施例还提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现本申请实施例提供的连接恢复方法的步骤。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述连接恢复方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述连接恢复方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种频域资源确定系统，包括：终端和网络侧设备，所述终端可用于执行本申请实施例提供的终端侧的连接恢复方法的步骤，所述网络侧设备可用于执行本申请实施例提供的网络侧设备侧的连接恢复方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排 他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (29)

  1. 一种连接恢复方法，包括：
    终端在非激活态下驻留第一小区，并接收第一多播业务；
    在所述终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。
  2. 如权利要求1所述的方法，其中，所述终端满足预设条件包括如下至少一项：
    所述终端接收到网络侧发送的通知消息，所述通知消息用于通知所述第一多播业务的配置发生变更；
    所述终端执行小区重选；
    所述终端执行移动性管理；
    所述终端对所述第一多播业务不再感兴趣；
    所述终端接收所述第一多播业务的质量与预设质量匹配，所述预设质量表示不能继续接收所述第一多播业务。
  3. 如权利要求2所述的方法，其中，所述终端执行小区重选，包括如下至少一项：
    所述终端从所述第一小区重选到第二小区，所述第一小区为发送所述第一多播业务的多播业务小区；
    所述终端从第一有效区域重选到第三小区，所述第一有效区域为所述第一多播业务的有效区域，且所述第三小区不属于所述第一有效区域。
  4. 如权利要求2所述的方法，其中，所述终端执行移动性管理，包括由于移动导致的如下至少一项：
    所述终端驻留在所述第一小区，停止接收所述第一多播业务；
    所述终端针对所述第一小区的参考信号的测量结果与第一预设测量结果匹配，所述第一预设测量结果表示所述终端在所述第一小区不能继续接收所述第一多播业务；
    所述终端接收所述第一多播业务的质量与预设质量匹配，所述预设质量表示所述终端在所述第一小区不能继续接收所述第一多播业务；
    所述终端对多播信道或者多播信号的测量结果与第二预设测量结果匹配，所述第二预设测量结果表示所述终端在所述第一小区不能继续接收所述第一多播业务；
    所述终端的信息表示不能继续接收所述第一多播业务。
  5. 如权利要求4所述的方法，其中，所述终端接收所述第一多播业务的质量与预设质量匹配，包括如下至少一项：
    所述终端连续N1次接收所述第一多播业务的数据失败；
    在第一时间窗口内，所述终端接收所述第一多播业务的数据失败次数达到N2次；
    在第二时间窗口内，所述终端接收所述第一多播业务的数据失败比例高于或者等于第一预设比例；
    在第一持续时间内，所述终端没有正确接收到所述第一多播业务；
    在第三时间窗口内，所述终端正确接收到所述第一多播业务的次数少于N3次；
    在第四时间窗口内，所述终端正确接收到所述第一多播业务的比例低于第二预设比例；
    在连续的N4个非连续接收DRX周期内，所述终端没有正确接收到所述第一多播业务；
    在连续的N5个DRX周期内，所述终端接收所述第一多播业务的数据失败次数达到N6次；
    在连续的N7个DRX周期内，所述终端接收所述第一多播业务的数据失败比例高于或者等于第三预设比例；
    在连续的N8个DRX周期内，所述终端正确接收到所述第一多播业务的次数少于N9次；
    在连续的N10个DRX周期内，所述终端正确接收到所述第一多播业务的比例低于第四预设比例；
    所述终端接收所述第一多播业务的质量不满足预设要求；
    其中，N1至N10为正整数。
  6. 如权利要求2所述的方法，其中，所述终端对所述第一多播业务不能感兴趣，包括：不因移动或者小区重选导致的，所述终端对所述第一多播业务不再感兴趣；和/或
    所述终端接收所述第一多播业务的质量与预设质量匹配包括：不因移动或者小区重选导致的，终端接收所述第一多播业务的质量与预设质量匹配。
  7. 如权利要求1至6中任一项所述的方法，其中，所述第一消息还用于指示如下至少一项：
    请求连接恢复的目的；
    所述终端有上行数据要发送。
  8. 如权利要求7所述的方法，其中，所述第一消息携带的信令内容用于指示如下至少一项：
    请求连接恢复的目的；
    所述终端有上行数据要发送；
    或者，
    所述第一消息的消息头用于指示如下至少一项：
    请求连接恢复的目的；
    所述终端有上行数据要发送。
  9. 如权利要求1至6中任一项所述的方法，其中，所述第一消息与缓存状态报告BSR一起发送。
  10. 如权利要求1至6中任一项所述的方法，其中，发送第一消息之后，所述方法还包括如下一项：
    所述终端接收连接恢复消息；
    所述终端接收无线资源控制RRC释放消息，所述RRC释放消息携带所述第一多播业务变更的配置。
  11. 如权利要求10所述的方法，其中，所述终端接收RRC释放消息之后，所述方法还包括：
    所述终端基于所述第一多播业务变更的配置，在非激活态接收所述第一多播业务。
  12. 如权利要求11所述的方法，其中，所述终端基于所述第一多播业务变更的配置，在非激活态接收所述第一多播业务，包括如下至少一项：
    所述终端基于所述第一多播业务变更的配置，对无线链路控制RLC层和下层进行复位或者重置，并从新协议栈开始接收所述第一多播业务；
    所述终端基于所述第一多播业务变更的配置，在分组数据汇聚协议PDCP层进行所述第一多播业务的连续性接收。
  13. 如权利要求12所述的方法，其中，所述在PDCP层进行所述第一多播业务的连续性接收，包括如下一项：
    基于网络侧显式指示，在PDCP层基于数据包的序列号SN和计数值中的至少一项，对所述第一多播业务的数据包进行排序；
    基于网络侧隐式指示，在PDCP层基于数据包的序列号SN和计数值中的至少一项，对所述第一多播业务的数据包进行排序。
  14. 如权利要求10所述的方法，其中，在所述终端进入连接态之后，所述方法还包括如下至少一项：
    所述终端向网络侧设备发送第二消息，所述第二消息用于请求在连接态接收所述第一多播业务；
    所述终端向网络侧设备上报所述终端对于所述第一多播业务的接收质量信息；
    所述终端发起所述第一多播业务的离开过程。
  15. 一种连接恢复方法，包括：
    网络侧设备接收终端发送第一消息，所述第一消息用于请求连接恢复；
    其中，所述终端为在非激活状态下驻留第一小区接收第一多播业务的终端。
  16. 如权利要求15所述的方法，其中，所述网络侧设备接收终端发送第一消息之前，所述方法还包括：
    所述网络侧设备向所述终端发送通知消息，所述通知消息用于通知所述第一多播业务的配置发生变更。
  17. 如权利要求15或16所述的方法，其中，所述第一消息还用于指示如下至少一项：
    请求连接恢复的目的；
    所述终端有上行数据要发送。
  18. 如权利要求17所述的方法，其中，所述第一消息携带的信令内容用于指示如下至少一项：
    请求连接恢复的目的；
    所述终端有上行数据要发送；
    或者，
    所述第一消息的消息头用于指示如下至少一项：
    请求连接恢复的目的；
    所述终端有上行数据要发送。
  19. 如权利要求15或16所述的方法，其中，所述第一消息与缓存状态报告BSR一起接收。
  20. 如权利要求15或16所述的方法，其中，所述网络侧设备接收终端发送第一消息之后，所述方法还包括如下一项：
    所述网络侧设备向所述终端发送连接恢复消息；
    所述网络侧设备向所述终端发送无线资源控制RRC释放消息，所述RRC释放消息携带所述第一多播业务变更的配置。
  21. 如权利要求20所述的方法，其中，在所述网络侧设备确定所述终端需要在非激活态继续接收所述第一多播业务的情况下，向所述终端发送所述RRC释放消息。
  22. 如权利要求21所述的方法，其中，所述网络侧设备基于所述终端的终端上下文，确定所述终端需要在非激活态继续接收所述第一多播业务，所述终端上行下文包括如下至少一项：
    所述终端感兴趣或者正在接收的多播业务的业务标识信息；
    所述终端感兴趣或者正在接收的多播业务的配置信息；
    所述终端感兴趣或者正在接收的多播业务的归属小区信息；
    所述终端感兴趣或者正在接收的多播业务的有效区域信息。
  23. 如权利要求22所述的方法，其中，所述配置信息包括如下至少一项：
    配置、配置版本信息。
  24. 如权利要求20所述的方法，其中，所述网络侧设备向所述终端发送连接恢复消息之后，所述方法还包括如下至少一项：
    所述网络侧设备接收所述终端发送的第二消息，所述第二消息用于请求在连接态接收所述第一多播业务；
    所述网络侧设备接收所述终端上报的所述终端对于所述第一多播业务的接收质量信息；
    所述网络侧设备接受所述终端发起的所述第一多播业务的离开过程。
  25. 一种连接恢复装置，包括：
    第一接收模块，用于在非激活态下驻留第一小区，并接收第一多播业务；
    第一发送模块，用于在终端满足预设条件的情况下，发送第一消息，所述第一消息用于请求连接恢复。
  26. 一种连接恢复装置，包括：
    第一接收模块，用于接收终端发送第一消息，所述第一消息用于请求连接恢复；
    其中，所述终端为在非激活状态下驻留第一小区接收第一多播业务的终端。
  27. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至14任一项所述的连接恢复方法的步骤。
  28. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求15至24任一项所述的连接恢复方法的步骤。
  29. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至14任一项所述的连接恢复方法的步骤，或者，所述程序或指令被处理器执行时实现如权利要求15至24任一项所述的连接恢复方法的步骤。
PCT/CN2023/105413 2022-07-15 2023-06-30 连接恢复方法、装置、终端及网络侧设备 WO2024012305A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210836819.6A CN117440325A (zh) 2022-07-15 2022-07-15 连接恢复方法、装置、终端及网络侧设备
CN202210836819.6 2022-07-15

Publications (1)

Publication Number Publication Date
WO2024012305A1 true WO2024012305A1 (zh) 2024-01-18

Family

ID=89535525

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/105413 WO2024012305A1 (zh) 2022-07-15 2023-06-30 连接恢复方法、装置、终端及网络侧设备

Country Status (2)

Country Link
CN (1) CN117440325A (zh)
WO (1) WO2024012305A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021077434A1 (zh) * 2019-10-26 2021-04-29 华为技术有限公司 一种通信方法及装置
WO2022033168A1 (zh) * 2020-08-14 2022-02-17 大唐移动通信设备有限公司 一种mbs业务数据传输方法和网络侧装置及设备
WO2022037706A1 (zh) * 2020-08-21 2022-02-24 华为技术有限公司 一种通信方法及装置
CN114554558A (zh) * 2020-11-25 2022-05-27 维沃移动通信有限公司 消息发送方法、装置和终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021077434A1 (zh) * 2019-10-26 2021-04-29 华为技术有限公司 一种通信方法及装置
WO2022033168A1 (zh) * 2020-08-14 2022-02-17 大唐移动通信设备有限公司 一种mbs业务数据传输方法和网络侧装置及设备
WO2022037706A1 (zh) * 2020-08-21 2022-02-24 华为技术有限公司 一种通信方法及装置
CN114554558A (zh) * 2020-11-25 2022-05-27 维沃移动通信有限公司 消息发送方法、装置和终端

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Multicast session reception in RRC INACTIVE", 3GPP DRAFT; R2-2103907, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. E-meeting; 20210412 - 20210420, 2 April 2021 (2021-04-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052175229 *
TAO QI, ZTE, SANECHIPS: "Multicast reception in RRC_INACTIVE", 3GPP DRAFT; R2-2212926; TYPE DISCUSSION; NR_MBS_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 2, no. Toulouse, FR; 20221114 - 20221118, 4 November 2022 (2022-11-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052216995 *

Also Published As

Publication number Publication date
CN117440325A (zh) 2024-01-23

Similar Documents

Publication Publication Date Title
WO2022262636A1 (zh) 驻网方法和装置
WO2023174222A1 (zh) 语音业务处理方法、设备及可读存储介质
WO2023284682A1 (zh) 中继的识别方法、中继的确定方法、终端及网络侧设备
WO2024012305A1 (zh) 连接恢复方法、装置、终端及网络侧设备
US20220046576A1 (en) Apparatus, method and computer program for performing radio access notification area update
WO2024012304A1 (zh) 多播业务接收方法、装置、终端及网络侧设备
WO2023185929A1 (zh) 资源控制方法、装置、终端及网络侧设备
WO2023165422A1 (zh) 寻呼指示方法、装置、终端及网络侧设备
WO2024140383A1 (zh) 信号检测结果处理方法、装置及终端
WO2023160604A1 (zh) 非连接态终端的确定方法、终端及网络侧设备
WO2023207947A1 (zh) 小区重配置方法、装置、终端及网络侧设备
WO2023185845A1 (zh) 通信方法、装置及相关设备
WO2024017244A1 (zh) 信息发送方法、信息接收方法、装置及相关设备
WO2023193676A1 (zh) 测量上报处理方法、装置、终端及网络侧设备
WO2024027681A1 (zh) Ue能力控制方法、装置、终端及网络侧设备
WO2023185794A1 (zh) 通信处理方法、终端及网络侧设备
WO2024027678A1 (zh) 扩展非连续接收的配置方法及装置、通信设备
WO2023174321A1 (zh) 语音业务的实现方法、装置及终端
WO2023217141A1 (zh) 终端定位方法、终端及网络侧设备
WO2023193677A1 (zh) 测量处理方法、装置、终端及网络侧设备
WO2023109679A1 (zh) 语音回落方法、装置、终端及可读存储介质
WO2023202560A1 (zh) 辅小区组信息发送方法、接收方法、终端、设备和介质
WO2023155850A1 (zh) 候选小区的配置方法、装置、终端及网络侧设备
WO2024012373A1 (zh) Ai模型信息传输方法、装置及设备
WO2024001954A1 (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: 23838797

Country of ref document: EP

Kind code of ref document: A1