WO2024077421A1 - 组播业务数据的传输方法及装置、存储介质 - Google Patents

组播业务数据的传输方法及装置、存储介质 Download PDF

Info

Publication number
WO2024077421A1
WO2024077421A1 PCT/CN2022/124180 CN2022124180W WO2024077421A1 WO 2024077421 A1 WO2024077421 A1 WO 2024077421A1 CN 2022124180 W CN2022124180 W CN 2022124180W WO 2024077421 A1 WO2024077421 A1 WO 2024077421A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
multicast service
state
rlc entity
service data
Prior art date
Application number
PCT/CN2022/124180
Other languages
English (en)
French (fr)
Inventor
刘晓菲
吴昱民
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2022/124180 priority Critical patent/WO2024077421A1/zh
Publication of WO2024077421A1 publication Critical patent/WO2024077421A1/zh

Links

Images

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

Definitions

  • the present disclosure relates to the field of communications, and in particular to a method and device for transmitting multicast service data, and a storage medium.
  • R17 In Release 17 (R17), only connected terminals are supported to receive multicast services. That is, if a terminal wants to receive multicast service data, it must first establish a Radio Resource Control (RRC) connection, and then receive multicast service data after the terminal enters the connected state. Obviously, this cannot meet the needs of key services such as Multicast Broadcast Service (MBS), especially for cells with a large number of terminals, which will increase the load on network equipment and cannot ensure the timeliness of MBS key services. In addition, when receiving multicast service data, the terminal needs to remain in the RRC connected state (RRC_CONNECTED), which causes a lot of power consumption of the terminal.
  • RRC Radio Resource Control
  • the terminal needs to be in a connected state to execute the receiving mechanism of multicast service data, which needs to be improved.
  • the embodiments of the present disclosure provide a method and device for transmitting multicast service data, and a storage medium.
  • a method for transmitting multicast service data is provided, the method being executed by a terminal and comprising:
  • the radio link control RLC entity is retained.
  • the multicast service includes an inactive multicast service.
  • retaining a radio link control RLC entity includes:
  • the RLC entity is retained.
  • the state of the terminal changes, including:
  • the terminal switches from a first state to a second state, the first state being different from the second state;
  • the terminal fails to switch from the first state to the second state, and switches back to the first state.
  • the state of the terminal changes, including:
  • the terminal switches from a connected state to an inactive state
  • the terminal switches from an inactive state to a connected state
  • the terminal attempts to switch from the inactive state to another state but fails, and switches back to the inactive state.
  • the method before reserving the radio link control RLC entity, the method further includes:
  • the designated message includes at least one of the following:
  • RRC radio resource control
  • the method further comprises:
  • the RLC entity is not retained.
  • the terminal stops receiving the multicast service data, including at least one of the following:
  • the terminal stops receiving the multicast service data
  • the terminal stops receiving the multicast service data.
  • the first multicast service configuration information used by the terminal becomes invalid, including at least one of the following:
  • the cell where the terminal resides does not support multicast services
  • the camping cell of the terminal does not support the first multicast service configuration information
  • the first multicast service configuration information exceeds the validity period.
  • the cell where the terminal resides does not support multicast services, including:
  • the terminal moves from an area supporting the inactive multicast service to an area not supporting the inactive multicast service.
  • the cell where the terminal resides does not support multicast services, including:
  • the terminal moves from a first cell supporting a multicast service to a second cell not supporting a multicast service.
  • the camping cell of the terminal does not support the first multicast service configuration information, including:
  • the terminal moves from an area supporting the inactive multicast service configuration information to an area not supporting the inactive multicast service configuration information.
  • the resident cell does not support the first multicast service configuration information, including:
  • the terminal moves from a third cell supporting the multicast service and supporting the first multicast service configuration information to a fourth cell supporting the multicast service but supporting the second multicast service configuration information.
  • the terminal is located in a notification area RNA based on a radio access network RAN.
  • the RLC entity is associated with a multicast broadcast service radio bearer MRB, and the MRB is used to receive the multicast service data.
  • the retaining a radio link control RLC entity includes:
  • the first RLC entity is reserved for point-to-multipoint PTM transmission.
  • the number of the RLC entities associated with the MRB is multiple;
  • the reserved radio link control RLC entity includes:
  • At least the first RLC entity used for PTM transmission is reserved.
  • the not retaining the RLC entity includes:
  • the first RLC entity for PTM transmission is not reserved.
  • the number of the RLC entities associated with the MRB is multiple;
  • the not retaining the RLC entity comprises:
  • At least a first RLC entity used for PTM transmission is not reserved.
  • the retaining the RLC entity includes any one of the following:
  • the RLC entity is not suspended.
  • not retaining the RLC entity includes any one of the following:
  • the RLC entity is suspended.
  • a method for transmitting multicast service data is provided, the method being executed by a network device and comprising:
  • the terminal When the terminal receives multicast service data, it is determined that the terminal retains a radio link control RLC entity.
  • the multicast service includes an inactive multicast service.
  • determining that the terminal reserves a radio link control RLC entity includes:
  • the state of the terminal changes, including:
  • the terminal switches from a first state to a second state, the first state being different from the second state;
  • the terminal fails to switch from the first state to the second state, and switches back to the first state.
  • the state of the terminal changes, including:
  • the terminal switches from a connected state to an inactive state
  • the terminal switches from an inactive state to a connected state
  • the terminal attempts to switch from the inactive state to another state but fails, and switches back to the inactive state.
  • the method before determining that the terminal reserves a radio link control RLC entity, the method further includes:
  • a specified message is sent to the terminal.
  • the designated message includes at least one of the following:
  • RRC radio resource control
  • the method further comprises:
  • the terminal stops receiving the multicast service data, including at least one of the following:
  • the terminal stops receiving the multicast service data
  • the terminal stops receiving the multicast service data.
  • the first multicast service configuration information used by the terminal becomes invalid, including at least one of the following:
  • the cell where the terminal resides does not support multicast services
  • the camping cell of the terminal does not support the first multicast service configuration information
  • the first multicast service configuration information exceeds the validity period.
  • the cell where the terminal resides does not support multicast services, including:
  • the terminal moves from an area supporting an inactive multicast service to an area not supporting an inactive multicast service, and determines that a cell where the terminal resides does not support the multicast service.
  • the cell where the terminal resides does not support multicast services, including:
  • the terminal moves from a first cell supporting a multicast service to a second cell not supporting a multicast service.
  • the camping cell of the terminal does not support the first multicast service configuration information, including:
  • the terminal moves from an area supporting the inactive multicast service to an area not supporting the inactive multicast service configuration information.
  • the resident cell does not support the first multicast service configuration information, including:
  • the terminal moves from a third cell supporting the multicast service and supporting the first multicast service configuration information to a fourth cell supporting the multicast service but supporting the second multicast service configuration information.
  • the terminal is located in a notification area RNA based on a radio access network RAN.
  • the RLC entity is associated with a multicast broadcast service radio bearer MRB, and the MRB is used to receive the multicast service data.
  • the determining that the terminal reserves a radio link control RLC entity includes:
  • the number of the RLC entities associated with the MRB is multiple;
  • the determining that the terminal reserves a radio link control RLC entity comprises:
  • the terminal reserves at least a first RLC entity for PTM transmission.
  • the determining that the terminal does not retain the RLC entity includes:
  • the terminal does not reserve a first RLC entity for PTM transmission.
  • the number of the RLC entities associated with the MRB is multiple;
  • the determining that the terminal does not retain the RLC entity includes:
  • the terminal does not reserve at least a first RLC entity for PTM transmission.
  • the determining that the terminal retains the RLC entity includes any one of the following:
  • the determining that the terminal does not retain the RLC entity includes any one of the following:
  • a device for transmitting multicast service data comprising:
  • the execution module is configured to reserve a radio link control RLC entity when it is determined to receive multicast service data.
  • a device for transmitting multicast service data is provided, the device being applied to a network device, comprising:
  • the determination module is configured to determine that the terminal retains a radio link control RLC entity when the terminal receives multicast service data.
  • a computer-readable storage medium wherein the storage medium stores a computer program, and the computer program is used to execute the multicast service data transmission method described in any one of the above-mentioned terminal sides.
  • a computer-readable storage medium wherein the storage medium stores a computer program, and the computer program is used to execute the multicast service data transmission method described in any one of the above-mentioned network device sides.
  • a device for transmitting multicast service data including:
  • a memory for storing processor-executable instructions
  • the processor is configured to execute any of the multicast service data transmission methods described above on the terminal side.
  • a device for transmitting multicast service data including:
  • a memory for storing processor-executable instructions
  • the processor is configured to execute any of the multicast service data transmission methods described above on the network device side.
  • the terminal when receiving multicast service data, the terminal can retain the RLC entity, thereby avoiding the problem of multicast service data packet loss or service reception interruption due to RLC reconstruction, improving the reliability of multicast service data transmission and high availability.
  • Fig. 1 is a system architecture diagram showing transmission of multicast service data according to an exemplary embodiment.
  • Fig. 2 is a schematic flow chart of a method for transmitting multicast service data according to an exemplary embodiment.
  • Fig. 3 is a schematic flow chart of another method for transmitting multicast service data according to an exemplary embodiment.
  • Fig. 4 is a schematic flow chart of another method for transmitting multicast service data according to an exemplary embodiment.
  • Fig. 5 is a schematic flow chart of another method for transmitting multicast service data according to an exemplary embodiment.
  • Fig. 6 is a schematic flow chart of another method for transmitting multicast service data according to an exemplary embodiment.
  • Fig. 7 is a schematic flow chart of another method for transmitting multicast service data according to an exemplary embodiment.
  • Fig. 8 is a block diagram of a device for transmitting multicast service data according to an exemplary embodiment.
  • Fig. 9 is a block diagram of another device for transmitting multicast service data according to an exemplary embodiment.
  • FIG. 10 is a schematic diagram of the structure of a device for transmitting multicast service data according to an exemplary embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of another device for transmitting multicast service data according to an exemplary embodiment of the present disclosure.
  • first, second, third, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "at the time of” or "when” or "in response to determining”.
  • the Multicast Broadcast Service can be marked by the following MBS service identifier:
  • TMGI Temporary Mobile Group Identity
  • MBS QoS flow ID MBS service flow identifier
  • MBS services include:
  • the terminal can receive data of the multicast service only after receiving the reception configuration information of the multicast service in the RRC connection state.
  • the network device can send the reception configuration information of the multicast service to the terminal through the terminal-specific signaling.
  • the terminal can receive the reception configuration information of the broadcast service in an idle state (IDLE), an inactive state (INACTIVE), or a connected state (CONNECTED), and receive the data of the broadcast service.
  • the network device can send the reception configuration information of the broadcast service to the terminal through system information, such as a system information block (SIB) and MBS control channel information.
  • SIB system information block
  • MBS control channel information is, for example, a broadcast service control channel (MBS Control Channel, MCCH).
  • the terminal needs to be in a connected state to receive multicast service data.
  • the present disclosure provides the following transmission method and device, storage medium for multicast service data.
  • Figure 1 it is a schematic diagram of a network architecture diagram applicable to the present disclosure.
  • the network in the present disclosure can be a 4G network, a 5G network, a 6G network or a future communication network, etc., and the present disclosure does not limit this.
  • the network architecture includes:
  • the terminal 101 may be a smart phone, a desktop computer, a laptop computer, a personal assistant (ipad), etc., which is not limited in the present disclosure.
  • the network device 102 includes but is not limited to a base station, an access network device, etc., wherein the base station may be a 4G base station, a 5G base station, or a future 6G base station, and the access network device may be a 4G access network device, a 5G access network device, or a future 6G access network device, etc., which is not limited in the present disclosure.
  • the network device 102 may also include a core network device, etc.
  • terminal 101 when terminal 101 receives multicast service data, terminal 101 may retain the RLC entity.
  • the network device 102 when the network device 102 determines that the terminal 101 receives multicast service data, it may be determined that the terminal 101 retains the RLC entity.
  • the network device 102 can continue to send multicast service data to the terminal 101 through the RLC entity retained by the terminal 101, and the terminal 101 can receive the multicast service data through the retained RLC entity.
  • the network device 102 does not need to perform RLC reconstruction operation with the terminal 101, thereby effectively avoiding the problem of multicast service data packet loss or service reception interruption, improving the reliability of multicast service data transmission and high availability.
  • the present disclosure provides a method for transmitting multicast service data, as shown in FIG. 2 , which is a flow chart of a method for transmitting multicast service data according to an embodiment, which can be executed by a terminal.
  • the method may include the following steps:
  • step 201 when it is determined to receive multicast service data, a radio link control RLC entity is reserved.
  • the RLC entity when the terminal is receiving multicast service data, the RLC entity is retained.
  • the terminal when the terminal has received the multicast service data and has not terminated the reception of the multicast service data, it is determined that the multicast service data is being received, and the terminal retains the RLC entity.
  • the terminal when the terminal is in a gap in receiving multicast service data, it is determined that the multicast service data is being received, and at this time the terminal retains the RLC entity.
  • the RLC entity when the terminal is about to receive multicast service data, the RLC entity is retained.
  • the RLC entity when the terminal is in a connected state, an idle state, or an inactive state and determines to receive multicast service data, the RLC entity is retained.
  • the terminal can determine that it is receiving or about to receive multicast service data based on the MBS service identifier, such as at least one of the TMGI, MBS Session ID, and MBS QoS flow ID, and thus retain the RLC entity.
  • the MBS service identifier such as at least one of the TMGI, MBS Session ID, and MBS QoS flow ID
  • the terminal may determine that multicast service data is being received or is about to be received based on indication information sent by the network device, and then reserve the RLC entity.
  • the indication information is used to indicate that there is a multicast service data packet to be sent on the network device.
  • the multicast service includes but is not limited to an inactive multicast service.
  • the inactive multicast service may refer to a terminal being configured to receive multicast service data in an inactive state.
  • the multicast service may include but is not limited to an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to the terminal being configured to receive multicast service data in an inactive state.
  • the connected multicast service may refer to the terminal being configured to receive multicast service data in an active state.
  • the RLC entity when the terminal is in a connected state (also called an activated state), an idle state or an inactive state and is receiving multicast service data, the RLC entity is reserved.
  • receiving multicast service data may specifically mean that the terminal has received the multicast service data and has not terminated receiving the multicast service data, or receiving multicast service data may specifically mean that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the RLC entity when the terminal is in a connected state (also called an activated state), an idle state or an inactive state and is about to receive multicast service data, the RLC entity is retained.
  • the receiving of multicast service data may mean that the terminal has not received any multicast service data before, and will receive multicast service data from the network device according to the actual service needs of the terminal.
  • the RLC entity is retained when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state and is receiving multicast service data, where the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service.
  • receiving multicast service data may specifically refer to that the terminal has received the multicast service data and has not terminated receiving the multicast service data.
  • receiving multicast service data may specifically refer to that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the terminal when the terminal is in a connected state (also called an activated state), an idle state or an inactive state, and is about to receive multicast service data, and the multicast service includes but is not limited to an inactive state multicast service and a connected state multicast service, the RLC entity is retained.
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the terminal is in a connected state (also called an activated state), an idle state, or an inactivated state, and is receiving multicast service data, where the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service.
  • the terminal determines that its own state has changed, the RLC entity is retained.
  • the terminal switches from a first state to a second state, wherein when the first state is different from the second state, the terminal determines that its state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal switches from a connected state to an inactive state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an inactive state to a connected state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an idle state to an inactive state, and it is determined that the state of the terminal has changed.
  • the state of the terminal is switched from an inactive state to an idle state, and it is determined that the state of the terminal has changed.
  • the terminal attempts to switch from the first state to the second state but fails, and switches back to the first state, and it is determined that the state of the terminal has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal attempts to switch from the inactive state to another state but fails, and switches back to the inactive state, and it is determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the connected state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the idle state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and is about to receive multicast service data, where the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service.
  • the terminal determines that its own state has changed, the RLC entity is retained.
  • the terminal switches from a first state to a second state, wherein when the first state is different from the second state, the terminal determines that its state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the state of the terminal is switched from a connected state to an inactive state, and it is determined that the state of the terminal has changed.
  • the state of the terminal is switched from an inactive state to a connected state, and it is determined that the state of the terminal has changed.
  • the state of the terminal is switched from an idle state to an inactive state, and it is determined that the state of the terminal has changed.
  • the state of the terminal is switched from an inactive state to an idle state, and it is determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch the state from the first state to the second state and switches back to the first state, and it is determined that the terminal state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal fails to switch from the inactive state to another state and switches back to the inactive state, and it is determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the connected state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the idle state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and is receiving multicast service data, where the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service.
  • the terminal receives a specified message sent by a network device, the RLC entity is retained.
  • the network device may include but is not limited to a base station, an access network device, etc., wherein the base station may be a 4G base station, a 5G base station, or a future 6G base station, and the access network device may be a 4G access network device, a 5G access network device, or a future 6G access network device, etc.
  • the network device 102 may also include a core network device, etc.
  • the designated message may be a radio resource control (RRC) release message carrying a suspension configuration, wherein the suspension configuration is used to configure the terminal to suspend an RRC connection with a network device.
  • RRC radio resource control
  • the designated message may be an RRC reconfiguration message.
  • the designated message may be an RRC resume message.
  • the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and is about to receive multicast service data.
  • the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service.
  • the network device may include but is not limited to a base station, an access network device, etc., wherein the base station may be a 4G base station, a 5G base station, or a future 6G base station, and the access network device may be a 4G access network device, a 5G access network device, or a future 6G access network device, etc.
  • the network device 102 may also include a core network device, etc.
  • the designated message may be a radio resource control (RRC) release message carrying a suspension configuration, wherein the suspension configuration is used to configure the terminal to suspend an RRC connection with a network device.
  • RRC radio resource control
  • the designated message may be an RRC reconfiguration message.
  • the designated message may be an RRC resume message.
  • the RLC entity is associated with a multicast broadcast service radio bearer (Multicast Broadcast Service Radio Bear, MRB), and the MRB is used to receive the multicast service data.
  • MRB Multicast Broadcast Service Radio Bear
  • an MRB may be associated with one or more RLC entities.
  • the terminal when retaining an RLC entity, the terminal may retain a first RLC entity for point to multipoint (PTM) transmission.
  • PTM point to multipoint
  • the RLC entity is associated with an MRB, the MRB is used to receive the multicast service data, and the number of the RLC entities associated with the MRB is multiple.
  • the terminal retains the RLC entity, at least the first RLC entity used for PTM transmission can be retained among the multiple RLC entities associated with the MRB.
  • the terminal may retain a first RLC entity for PTM transmission, but not retain a second RLC entity for point-to-point (PTP) transmission.
  • the terminal releases the second RLC entity for PTP transmission.
  • the second RLC entity for PTP transmission is rebuilt.
  • the second RLC entity for PTP transmission is suspended.
  • the terminal may reserve a first RLC entity for PTM transmission and reserve a second RLC entity for PTP transmission.
  • the terminal is in a connected state (also called an activated state), an idle state, or an inactive state, and is receiving multicast service data (or is about to receive multicast service data), and the multicast service includes but is not limited to an inactive state multicast service and a connected state multicast service.
  • the RLC entity is retained. Specifically, the RLC entity is associated with a multicast broadcast service radio bearer MRB, and the MRB is used to receive the multicast service data.
  • receiving multicast service data may specifically mean that the terminal has received the multicast service data and has not terminated receiving the multicast service data, or receiving multicast service data may specifically mean that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the RLC entity associated with the MRB is retained, and the RLC entity is the first RLC entity for PTM transmission.
  • the MRB is associated with multiple RLC entities, the first RLC entity used for PTM transmission is reserved, and the second RLC entity used for PTP transmission is released, reestablished, or suspended.
  • a first RLC entity is reserved for PTM transmission while a second RLC entity is reserved for PTP transmission.
  • the terminal switches from a first state to a second state, wherein when the first state is different from the second state, the terminal determines that its state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the state of the terminal is switched from a connected state to an inactive state, and it is determined that the state of the terminal has changed.
  • the state of the terminal is switched from an inactive state to a connected state, and it is determined that the state of the terminal has changed.
  • the state of the terminal is switched from an idle state to an inactive state, and it is determined that the state of the terminal has changed.
  • the state of the terminal is switched from an inactive state to an idle state, and it is determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch its state from the first state to the second state and switches back to the first state, and the terminal determines that its state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal fails to switch from the inactive state to another state and switches back to the inactive state, and it is determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the connected state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the idle state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal is in a connected state (also called an activated state), an idle state, or an inactive state, and is receiving multicast service data (or is about to receive multicast service data), and the multicast service includes but is not limited to an inactive state multicast service and a connected state multicast service.
  • the RLC entity When the terminal receives a designated message sent by a network device, the RLC entity is retained. Specifically, the RLC entity is associated with a multicast broadcast service radio bearer MRB, and the MRB is used to receive the multicast service data.
  • the RLC entity associated with the MRB is retained, and the RLC entity is the first RLC entity for PTM transmission.
  • the MRB is associated with multiple RLC entities, the first RLC entity used for PTM transmission is reserved, and the second RLC entity used for PTP transmission is released, reestablished, or suspended.
  • a first RLC entity is reserved for PTM transmission while a second RLC entity is reserved for PTP transmission.
  • the network device may include but is not limited to a base station, an access network device, etc., wherein the base station may be a 4G base station, a 5G base station, or a future 6G base station, and the access network device may be a 4G access network device, a 5G access network device, or a future 6G access network device, etc.
  • the network device 102 may also include a core network device, etc.
  • the designated message may be a radio resource control (RRC) release message carrying a suspension configuration, wherein the suspension configuration is used to configure the terminal to suspend an RRC connection with a network device.
  • RRC radio resource control
  • the designated message may be an RRC reconfiguration message.
  • the designated message may be an RRC resume message.
  • retaining the RLC entity includes any of the following: not releasing the RLC entity; not reestablishing the RLC entity; and not suspending the RLC entity.
  • the terminal when receiving multicast service data, the terminal can retain the RLC entity, thereby avoiding the problem of multicast service data packet loss or service reception interruption caused by RLC reconstruction, improving the reliability of multicast service data transmission and high availability.
  • the RLC entity includes but is not limited to an RLC entity associated with an MRB, and the MRB is used to receive multicast service data.
  • the MRB may be associated with only one RLC entity, which is the first RLC entity used for PTM transmission.
  • the terminal determines to receive multicast service data
  • the first RLC entity associated with the MRB and used for PTM transmission may be retained.
  • the MRB is used to receive multicast service data.
  • the first RLC entity associated with the MRB and used for PTM transmission can be retained.
  • the MRB is used to receive multicast service data. That is, the first RLC entity associated with the MRB and used for PTM transmission is not released, rebuilt or suspended.
  • the multicast service includes, but is not limited to, an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to that the terminal is configured to receive multicast service data in the inactive state.
  • the connected multicast service may refer to that the terminal is configured to receive multicast service data in the connected state.
  • receiving multicast service data may specifically mean that the terminal has received the multicast service data and has not terminated receiving the multicast service data, or receiving multicast service data may specifically mean that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the MRB may be associated with multiple RLC entities, and the MRB is used to receive multicast service data.
  • the multiple RLC entities include at least one first RLC entity for PTM transmission, and may also include at least one second RLC entity for PTP transmission.
  • the first RLC entity associated with the MRB and used for PTM transmission can be retained, that is, the first RLC entity associated with the MRB and used for PTM transmission is not released, rebuilt or suspended.
  • the terminal can release, rebuilt or suspend the second RLC entity used for PTP transmission.
  • the multicast service includes, but is not limited to, an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to that the terminal is configured to receive multicast service data in the inactive state.
  • the connected multicast service may refer to that the terminal is configured to receive multicast service data in the connected state.
  • receiving multicast service data may specifically mean that the terminal has received the multicast service data and has not terminated receiving the multicast service data, or receiving multicast service data may specifically mean that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the MRB may be associated with multiple RLC entities, and the MRB is used to receive multicast service data.
  • the multiple RLC entities include at least one first RLC entity for PTM transmission, and may also include at least one second RLC entity for PTP transmission.
  • the terminal When the terminal is receiving or about to receive multicast service data, the first RLC entity associated with the MRB and used for PTM transmission can be retained. In addition, the terminal can also retain the second RLC entity used for PTP transmission. That is, the first RLC entity associated with the MRB and used for PTM transmission is not released, rebuilt or suspended, and the second RLC entity associated with the MRB and used for PTP transmission is not released, rebuilt or suspended.
  • the multicast service includes, but is not limited to, an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to that the terminal is configured to receive multicast service data in the inactive state.
  • the connected multicast service may refer to that the terminal is configured to receive multicast service data in the connected state.
  • receiving multicast service data may specifically mean that the terminal has received the multicast service data and has not terminated receiving the multicast service data, or receiving multicast service data may specifically mean that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the terminal when receiving multicast service data, can retain the RLC entity. Specifically, when the MRB is associated with multiple RLC entities, only the first RLC entity used for PTM transmission among the multiple RLC entities can be retained, and the second RLC entity used for PTP transmission can be released, rebuilt or suspended. Alternatively, the terminal can also retain the first RLC entity used for PTM transmission among the multiple RLC entities, and retain the second RLC entity used for PTP transmission among the multiple RLC entities. This avoids the problem of multicast service data packet loss or service reception interruption caused by RLC reconstruction, improves the reliability of multicast service data transmission, and has high availability.
  • the RLC entity when the terminal determines that the state of the terminal has changed and determines to receive the multicast service data, the RLC entity is retained, including but not limited to not releasing, not reestablishing or not suspending the RLC entity.
  • the terminal switches from a first state to a second state, wherein when the first state is different from the second state, the terminal determines that its state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the state of the terminal is switched from a connected state to an inactive state, and it is determined that the state of the terminal has changed.
  • the terminal can retain the RLC entity when switching from a connected state to an inactive state and receiving the multicast service data, including but not limited to not releasing, reestablishing or suspending the RLC entity.
  • the terminal may retain the RLC entity when switching from a connected state to an inactive state and is about to receive the multicast service data, including but not limited to not releasing, not reestablishing or not suspending the RLC entity.
  • the state of the terminal is switched from an inactive state to a connected state, and it is determined that the state of the terminal has changed.
  • the terminal may retain the RLC entity when switching from an inactive state to a connected state and receiving the multicast service data, including but not limited to not releasing, reestablishing or suspending the RLC entity.
  • the terminal may retain the RLC entity when switching from an inactive state to a connected state and about to receive the multicast service data, including but not limited to not releasing, not reestablishing or not suspending the RLC entity.
  • the terminal may also switch from the inactive state to the idle state and retain the RLC entity when the terminal is receiving (or about to receive) the multicast service data.
  • the terminal switches from the idle state to the inactive state and retains the RLC entity when the terminal is receiving (or about to receive) the multicast service data, including but not limited to not releasing, not reestablishing or not suspending the RLC entity.
  • the terminal attempts to switch from the first state to the second state but fails, and switches back to the first state, and it is determined that the state of the terminal has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal may retain the RLC entity, including but not limited to not releasing, reestablishing or suspending the RLC entity, when failing to switch from the inactive state to the connected state and switching back to the inactive state while receiving the multicast service data.
  • the terminal may retain the RLC entity, including but not limited to not releasing, reestablishing or suspending the RLC entity, when failing to switch from the inactive state to the connected state and switching back to the inactive state and about to receive the multicast service data.
  • the terminal may retain the RLC entity, including but not limited to not releasing, reestablishing or suspending the RLC entity, when failing to switch from the inactive state to the idle state and switching back to the inactive state while receiving the multicast service data.
  • the terminal may retain the RLC entity, including but not limited to not releasing, reestablishing or suspending the RLC entity, when failing to switch from the inactive state to the idle state and switching back to the inactive state and about to receive the multicast service data.
  • receiving multicast service data may specifically mean that the terminal has received the multicast service data and has not terminated receiving the multicast service data, or receiving multicast service data may specifically mean that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the terminal when the terminal state changes and the terminal receives multicast service data, the terminal can retain the RLC entity, thereby avoiding the problem of multicast service data packet loss or service reception interruption due to RLC reconstruction, improving the reliability of multicast service data transmission and high availability.
  • the terminal when the terminal receives a designated message sent by the network device and determines to receive the multicast service data, the RLC entity is retained, including but not limited to not releasing, not reestablishing or not suspending the RLC entity.
  • the network device may include but is not limited to a base station, an access network device, etc., wherein the base station may be a 4G base station, a 5G base station, or a future 6G base station, and the access network device may be a 4G access network device, a 5G access network device, or a future 6G access network device, etc.
  • the network device 102 may also include a core network device, etc.
  • the designated message may be a radio resource control (RRC) release message carrying a suspension configuration, wherein the suspension configuration is used to configure the terminal to suspend the RRC connection with the network device.
  • RRC radio resource control
  • the terminal when the terminal receives a radio resource control RRC release message carrying a suspension configuration sent by a network device and is receiving a multicast service, the terminal can retain the RLC entity, including but not limited to not releasing, not reestablishing or not suspending the RLC entity.
  • the terminal when the terminal receives a radio resource control RRC release message carrying a suspension configuration sent by a network device and is about to receive a multicast service, the terminal can retain the RLC entity, including but not limited to not releasing, not reestablishing or not suspending the RLC entity.
  • the designated message may be an RRC reconfiguration message.
  • the terminal when receiving the RRC reconfiguration message sent by the network device and receiving a multicast service, the terminal may retain the RLC entity, including but not limited to not releasing, not reestablishing or not suspending the RLC entity.
  • the terminal when receiving the RRC reconfiguration message sent by the network device and about to receive the multicast service, the terminal may retain the RLC entity, including but not limited to not releasing, not reestablishing or not suspending the RLC entity.
  • the designated message may be an RRC resume message.
  • the terminal when receiving the RRC recovery message sent by the network device and receiving the multicast service, the terminal may retain the RLC entity, including but not limited to not releasing, not reestablishing or not suspending the RLC entity.
  • the terminal when receiving the RRC recovery message sent by the network device and about to receive the multicast service, the terminal may retain the RLC entity, including but not limited to not releasing, not reestablishing or not suspending the RLC entity.
  • the terminal can also retain the RLC entity when receiving other specified messages sent by the network device and determining to receive multicast service data, including but not limited to not releasing, not reestablishing or not suspending the RLC entity. This disclosure does not limit this.
  • receiving multicast service data may specifically mean that the terminal has received the multicast service data and has not terminated receiving the multicast service data, or receiving multicast service data may specifically mean that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the terminal when the terminal receives a designated message sent by a network device and receives multicast service data, the terminal can retain the RLC entity, thereby avoiding the problem of multicast service data packet loss or service reception interruption caused by RLC reconstruction, thereby improving the reliability of multicast service data transmission and high availability.
  • FIG. 3 is a flow chart of a method for transmitting multicast service data according to an embodiment, which can be executed by a terminal, and the terminal can be a smart phone, a desktop computer, a laptop computer, a personal assistant, etc., which is not limited in the present disclosure.
  • the method may include the following steps:
  • step 301 when the terminal stops receiving multicast service data, the RLC entity is not retained.
  • the RLC entity when the terminal is in a connected state (also called an activated state), an idle state, or an inactive state and stops receiving multicast service data, the RLC entity may not be retained.
  • the multicast service includes but is not limited to an inactive multicast service.
  • the inactive multicast service may refer to a terminal being configured to receive multicast service data in an inactive state.
  • the multicast service may include but is not limited to an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to the terminal being configured to receive multicast service data in an inactive state.
  • the connected multicast service may refer to the terminal being configured to receive multicast service data in a connected state.
  • the terminal when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and it is determined that the first multicast service configuration information used by the terminal is invalid, the terminal is determined to stop receiving multicast service data, and the RLC entity may not be retained.
  • a connected state also called an activated state
  • an idle state or an inactivated state when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and it is determined that the first multicast service configuration information used by the terminal is invalid, the terminal is determined to stop receiving multicast service data, and the RLC entity may not be retained.
  • the cell where the terminal resides does not support the multicast service, it can be determined that the first multicast service configuration information used by the terminal is invalid.
  • the terminal when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and because the terminal moves, the cell where the terminal currently resides does not support the multicast service, it is determined that the terminal stops receiving the multicast service data, and accordingly, the terminal may not retain the RLC entity.
  • a connected state also called an activated state
  • an idle state or an inactivated state
  • the terminal may be determined that the cell where the terminal resides does not support the multicast service.
  • the terminal when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and due to the movement of the terminal, the terminal moves to an area that does not support the inactivated multicast service, it can be determined that the resident cell of the terminal does not support the multicast service. Further, it can be determined that the first multicast service configuration information used by the terminal is invalid. At this time, it is determined that the terminal stops receiving the multicast service data, and the RLC entity can be not retained.
  • a connected state also called an activated state
  • an idle state or an inactivated state due to the movement of the terminal, the terminal moves to an area that does not support the inactivated multicast service.
  • the first multicast service configuration information used by the terminal is invalid.
  • the terminal stops receiving the multicast service data, and the RLC entity can be not retained.
  • the terminal moves from a first cell supporting the multicast service to a second cell not supporting the multicast service, and determines that the resident cell does not support the multicast service.
  • the terminal when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and due to the movement of the terminal, the terminal moves from a first cell that supports the multicast service to a second cell that does not support the multicast service, it can be determined that the resident cell of the terminal does not support the multicast service. Further, it can be determined that the first multicast service configuration information used by the terminal is invalid. At this time, it is determined that the terminal stops receiving the multicast service data and the RLC entity can be not retained.
  • the camping cell of the terminal does not support the first multicast service configuration information, it is determined that the first multicast service configuration information is invalid.
  • the terminal moves to an area that does not support the inactive multicast service configuration information, and determines that the resident cell does not support the first multicast service configuration information.
  • the terminal is in a connected state (also called an activated state), an idle state or an inactive state, and due to the movement of the terminal, the terminal moves to an area that does not support the inactive state multicast service configuration information, and it is determined that the resident cell does not support the first multicast service configuration information, and further, it is determined that the first multicast service configuration information is invalid. At this time, it is determined that the terminal stops receiving the multicast service data and does not retain the RLC entity.
  • the terminal moves from a third cell supporting multicast service and supporting the first multicast service configuration information to a fourth cell supporting multicast service but supporting the second multicast service configuration information, and determines that the resident cell does not support the first multicast service configuration information.
  • the terminal is in a connected state (also called an activated state), an idle state or an inactive state, and due to the movement of the terminal, the terminal moves from a third cell that supports the multicast service and supports the first multicast service configuration information to a fourth cell that supports the multicast service but supports the second multicast service configuration information, and it is determined that the resident cell does not support the first multicast service configuration information. Further, it is determined that the first multicast service configuration information is invalid. At this time, it is determined that the terminal stops receiving the multicast service data and does not retain the RLC entity.
  • the first multicast service configuration information exceeds a validity period, it is determined that the first multicast service configuration information is invalid.
  • the terminal may determine that the first multicast service configuration information has exceeded a validity period. Further, it is determined that the first multicast service configuration information is invalid. At this time, it is determined that the terminal stops receiving the multicast service data and does not retain the RLC entity.
  • the terminal when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state and it is determined that the multicast service session is deactivated, it is determined that the terminal stops receiving the multicast service data, and the RLC entity may not be retained.
  • a connected state also called an activated state
  • an idle state or an inactivated state when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state and it is determined that the multicast service session is deactivated, it is determined that the terminal stops receiving the multicast service data, and the RLC entity may not be retained.
  • the terminal when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, the terminal stops receiving the multicast service data, and the terminal is still in a notification area (RAN-based Notification Area, RNA) based on the radio access network RAN, the RLC entity may not be retained.
  • a connected state also called an activated state
  • an idle state or an inactivated state the terminal stops receiving the multicast service data, and the terminal is still in a notification area (RAN-based Notification Area, RNA) based on the radio access network RAN, the RLC entity may not be retained.
  • RNA RAN-based Notification Area
  • the terminal when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, the first multicast service configuration information used by the terminal is invalid, and the terminal is still in the RNA, the RLC entity can be released.
  • a connected state also called an activated state
  • the terminal when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, the cell where the terminal resides does not support multicast services, and the terminal is still in the RNA, the RLC entity can be released.
  • a connected state also called an activated state
  • an idle state or an inactivated state the cell where the terminal resides does not support multicast services, and the terminal is still in the RNA, the RLC entity can be released.
  • the terminal moves to an area that does not support inactive multicast services, or the terminal moves from a first cell that supports multicast services to a second cell that does not support multicast services, it can be determined that the resident cell does not support the multicast services.
  • the terminal when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, the cell where the terminal resides does not support the first multicast service configuration information, and the terminal is still in the RNA, the RLC entity can be released.
  • a connected state also called an activated state
  • an idle state or an inactivated state the cell where the terminal resides does not support the first multicast service configuration information, and the terminal is still in the RNA, the RLC entity can be released.
  • the terminal moves to an area that does not support inactive multicast service configuration information, or the terminal moves from a third cell that supports multicast service and supports the first multicast service configuration information to a fourth cell that supports multicast service but supports the second multicast service configuration information. It can be determined that the resident cell does not support the first multicast service configuration information.
  • the RLC entity when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state and the validity period of the first multicast service configuration information has expired and the terminal is still in the RNA, the RLC entity can be released.
  • the terminal when the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, the multicast service session is deactivated, and the terminal is still in the RNA, the RLC entity can be released.
  • a connected state also called an activated state
  • an idle state or an inactivated state the multicast service session is deactivated, and the terminal is still in the RNA, the RLC entity can be released.
  • the first multicast service configuration information used by the terminal is invalid, and the multicast service session is deactivated, and the terminal may release the RLC entity.
  • the terminal may release the RLC entity.
  • the terminal moves to an area that does not support inactive multicast services, the terminal is still in a notification area RNA based on the radio access network RAN, and the validity period of the first multicast service configuration information has expired, and the terminal may release the RLC entity.
  • the RLC entity is associated with an MRB, and the MRB is used to receive the multicast service data.
  • the terminal when releasing the RLC entity, may release the first RLC entity used for PTM transmission.
  • the terminal may re-establish the first RLC entity for PTM transmission in case of releasing the RLC entity.
  • the terminal when releasing the RLC entity, may suspend the first RLC entity used for PTM transmission.
  • the RLC entity is associated with an MRB
  • the MRB is used to receive the multicast service data
  • the terminal when releasing the RLC entity, can release at least the first RLC entity used for PTM transmission among multiple RLC entities associated with the MRB.
  • the terminal may release a first RLC entity used for PTM transmission among multiple RLC entities, and reserve a second RLC entity used for PTP transmission.
  • the terminal may reestablish a first RLC entity for PTM transmission among multiple RLC entities and reserve a second RLC entity for PTP transmission.
  • the terminal may suspend a first RLC entity used for PTM transmission among multiple RLC entities, and reserve a second RLC entity used for PTP transmission.
  • the terminal may release the first RLC entity used for PTM transmission, and release, reserve or suspend the second RLC entity used for PTP transmission.
  • the terminal may reestablish a first RLC entity for PTM transmission among a plurality of RLC entities, and release, reserve or suspend a second RLC entity for PTP transmission.
  • the terminal may suspend a first RLC entity for PTM transmission among a plurality of RLC entities, and release, reserve or suspend a second RLC entity for PTP transmission.
  • the RLC entity when the terminal is in a connected state (also called an activated state), an idle state or an inactive state and stops receiving multicast services, the RLC entity is released. Specifically, the RLC entity is associated with a multicast broadcast service radio bearer MRB, and the MRB is used to receive the multicast service data.
  • a connected state also called an activated state
  • MRB multicast broadcast service radio bearer
  • the RLC entity associated with the MRB is released, reestablished, or suspended, and the RLC entity is the first RLC entity for PTM transmission.
  • the MRB is associated with multiple RLC entities, the first RLC entity used for PTM transmission is released, re-established, or suspended, and the second RLC entity used for PTP transmission is reserved.
  • the MRB is associated with multiple RLC entities
  • the first RLC entity used for PTM transmission is released, re-established, or suspended, while the second RLC entity used for PTP transmission is released, re-established, or suspended.
  • the terminal when the terminal stops receiving multicast service data, it can release, suspend or rebuild the first RLC entity, thereby avoiding the waste of resources caused by retaining the first RLC entity when the reception of multicast service data is stopped, and a new RLC entity can be established when the terminal receives multicast service data, thereby improving the reliability of multicast service data transmission and high availability.
  • the terminal when the first multicast service configuration information used by the terminal fails, it can be determined that the terminal stops receiving the multicast service data. At this time, the terminal may not retain the RLC entity, including but not limited to releasing, reestablishing or suspending the RLC entity.
  • the terminal may not retain the RLC entity, including but not limited to releasing, reestablishing or suspending the RLC entity.
  • the terminal when the cell where the terminal resides does not support multicast service, it can be determined that the first multicast service configuration information is invalid. At this time, the terminal can determine to stop receiving the multicast service data and not retain the RLC entity, including but not limited to releasing, reestablishing or suspending the RLC entity.
  • the terminal moves to an area that does not support the inactive multicast service, it can be determined that the cell where the terminal resides does not support the multicast service.
  • the terminal determines that the resident cell does not support the multicast service, and further determines that the first multicast service configuration information used by the terminal is invalid. At this time, the terminal can determine to stop receiving the multicast service data and not retain the RLC entity, including but not limited to releasing, reestablishing or suspending the RLC entity.
  • the terminal moves from a first cell supporting a multicast service to a second cell not supporting a multicast service, it can be determined that the cell where the terminal resides does not support the multicast service.
  • a terminal moves from a first cell supporting a multicast service to a second cell that does not support a multicast service, the terminal determines that the resident cell does not support the multicast service, and further determines that the first multicast service configuration information used by the terminal is invalid.
  • the terminal can determine to stop receiving the multicast service data and does not retain the RLC entity. Specifically, the RLC entity can be released, rebuilt or suspended.
  • the terminal can determine that the first multicast service configuration information is invalid. At this time, the terminal can determine to stop receiving the multicast service data and not retain the RLC entity.
  • a terminal moves from an area supporting the inactive multicast service configuration information to an area not supporting the inactive multicast service configuration information, it can be determined that the resident cell of the terminal does not support the first multicast service configuration information.
  • the terminal determines that the resident cell does not support the first multicast service configuration information used by the terminal, and further determines that the first multicast service configuration information used by the terminal is invalid. At this time, the terminal can determine to stop receiving the multicast service data and does not retain the RLC entity. Specifically, the RLC entity can be released, rebuilt or suspended.
  • the terminal moves from a third cell supporting multicast service and supporting the first multicast service configuration information to a fourth cell supporting multicast service but supporting the second multicast service configuration information, and determines that the resident cell does not support the first multicast service configuration information.
  • a terminal moves from a third cell that supports multicast services and supports the first multicast service configuration information to a fourth cell that supports multicast services but supports the second multicast service configuration information
  • the terminal determines that the resident cell does not support the first multicast service configuration information used by the terminal, and further determines that the first multicast service configuration information used by the terminal is invalid.
  • the terminal can determine to stop receiving the multicast service data and not retain the RLC entity. Specifically, the RLC entity can be released, rebuilt or suspended.
  • the terminal can determine to stop receiving the multicast service data and not retain the RLC entity.
  • a timer corresponding to the first multicast service configuration information times out, and it is determined that the first multicast service configuration information exceeds a validity period.
  • the terminal determines that the first multicast service configuration information has exceeded its validity period, and further determines that the first multicast service configuration information used by the terminal is invalid. At this time, the terminal can determine to stop receiving the multicast service data and not retain the RLC entity. Specifically, the RLC entity can be released, rebuilt or suspended.
  • the terminal may determine to stop receiving the multicast service data and not retain the RLC entity. Specifically, the RLC entity may be released, reestablished or suspended.
  • the terminal can determine to stop receiving the multicast service data and not retain the RLC entity. Specifically, the RLC entity can be released, rebuilt or suspended.
  • the terminal when the multicast service session of the terminal is deactivated and the terminal is still in the notification area RNA based on the radio access network RAN, the terminal can determine to stop receiving the multicast service data and not retain the RLC entity. Specifically, the RLC entity can be released, rebuilt or suspended.
  • the RLC entity includes but is not limited to an RLC entity associated with an MRB, and the MRB is used to receive multicast service data.
  • the MRB may be associated with only one RLC entity, which is the first RLC entity used for PTM transmission.
  • the terminal when it determines to stop receiving the multicast service data, it can release, suspend or reestablish the first RLC entity used for PTM transmission.
  • the MRB is used to receive the multicast service data.
  • the multicast service includes but is not limited to an inactive multicast service and a connected multicast service.
  • An inactive multicast service may refer to a terminal being configured to receive multicast service data in an inactive state.
  • a connected multicast service may refer to a terminal being configured to receive multicast service data in a connected state.
  • the MRB may be associated with multiple RLC entities.
  • the multiple RLC entities include at least one first RLC entity for PTM transmission and may also include at least one second RLC entity for PTP transmission.
  • the terminal When the terminal determines to stop receiving the multicast service data, it can release, suspend or reestablish the first RLC entity used for PTM transmission.
  • the MRB is used to receive the multicast service data.
  • the terminal can retain the second RLC entity used for PTP transmission among the multiple RLC entities.
  • the multicast service includes, but is not limited to, an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to that the terminal is configured to receive multicast service data in the inactive state.
  • the connected multicast service may refer to that the terminal is configured to receive multicast service data in the connected state.
  • the MRB may be associated with multiple RLC entities.
  • the multiple RLC entities include at least one first RLC entity for PTM transmission and may also include at least one second RLC entity for PTP transmission.
  • the terminal When the terminal determines to stop receiving the multicast service data, it can release, suspend or reestablish the first RLC entity used for PTM transmission.
  • the MRB is used to receive the multicast service data.
  • the terminal can also release, suspend or reestablish the second RLC entity used for PTP transmission.
  • the multicast service includes, but is not limited to, an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to that the terminal is configured to receive multicast service data in the inactive state.
  • the connected multicast service may refer to that the terminal is configured to receive multicast service data in the connected state.
  • the terminal when the terminal stops receiving multicast service data, it can release, suspend or rebuild the RLC entity.
  • the MRB when the MRB is associated with multiple RLC entities, it can only release, suspend or rebuild the first RLC entity used for PTM transmission, and retain the second RLC entity used for PTP transmission.
  • the terminal can also release, suspend or rebuild the first RLC entity used for PTM transmission among multiple RLC entities, and release, suspend or rebuild the second RLC entity used for PTP transmission among multiple RLC entities.
  • step 201 and step 301 can be implemented separately or in combination.
  • step 201 can be executed first and then step 301, or step 301 can be executed first and then step 201.
  • the present disclosure does not limit this.
  • the embodiment of the present disclosure provides a method for transmitting multicast service data, as shown in FIG4 , which is a flow chart of a method for transmitting multicast service data according to an embodiment, which can be executed by a network device, including but not limited to a base station, an access network device, etc., wherein the base station can be a 4G base station, a 5G base station or a future 6G base station, and the access network device can be a 4G access network device, a 5G access network device or a future 6G access network device, etc.
  • the network device 102 can also include a core network device, etc.
  • the method can include the following steps:
  • step 401 when a terminal receives multicast service data, it is determined that the terminal retains a radio link control RLC entity.
  • the terminal may be a smart phone, a desktop computer, a laptop computer, a personal assistant (ipad), etc., and the present disclosure does not limit this.
  • the network device determines that the terminal is receiving multicast service data, the network device determines that the terminal reserves the RLC entity.
  • the terminal when the terminal has received the multicast service data and has not terminated the reception of the multicast service data, it is determined that the multicast service data is being received, and the terminal retains the RLC entity.
  • the terminal when the terminal is in a gap in receiving multicast service data, it is determined that the multicast service data is being received, and at this time the terminal retains the RLC entity.
  • the network device determines that the terminal is about to receive multicast service data, the network device determines that the terminal reserves the RLC entity.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and determines that the terminal receives multicast service data, and then determines that the terminal retains the RLC entity.
  • a connected state also called an activated state
  • an idle state also called an inactivated state
  • the network device when the network device determines that there are multicast service data packets to be sent, the network device may send indication information to the terminal so that the terminal determines to receive the multicast service data.
  • the multicast service includes but is not limited to an inactive multicast service.
  • the inactive multicast service may refer to a terminal being configured to receive multicast service data in an inactive state.
  • the multicast service may include but is not limited to an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to the terminal being configured to receive multicast service data in an inactive state.
  • the connected multicast service may refer to the terminal being configured to receive multicast service data in a connected state.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state, or an inactivated state, and that the terminal is receiving multicast service data, and then determines that the terminal retains the RLC entity.
  • a connected state also called an activated state
  • an idle state also called an inactivated state
  • receiving multicast service data may specifically mean that the terminal has received the multicast service data and has not terminated receiving the multicast service data, or receiving multicast service data may specifically mean that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and determines that the terminal is about to receive multicast service data, and then determines that the terminal retains the RLC entity.
  • a connected state also called an activated state
  • an idle state also called an inactivated state
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state, or an inactivated state, and determines that the terminal is receiving multicast service data, where the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service, and determines that the terminal retains the RLC entity.
  • a connected state also called an activated state
  • an idle state or an inactivated state
  • the network device determines that the terminal is receiving multicast service data, where the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service, and determines that the terminal retains the RLC entity.
  • receiving multicast service data may specifically mean that the terminal has received the multicast service data and has not terminated receiving the multicast service data, or receiving multicast service data may specifically mean that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and determines that the terminal is about to receive multicast service data, where the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service, and determines that the terminal retains the RLC entity.
  • a connected state also called an activated state
  • the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state, or an inactivated state, and determines that the terminal is receiving multicast service data, where the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service.
  • the network device determines that the terminal retains the RLC entity.
  • the network device determines that the terminal switches from a first state to a second state, wherein when the first state is different from the second state, the terminal determines that its own state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal switches from a connected state to an inactive state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an inactive state to a connected state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an idle state to an inactive state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an inactive state to an idle state, and it is determined that the state of the terminal has changed.
  • the network device determines that the terminal fails in an attempt to switch from the first state to the second state and switches back to the first state, and determines that the state of the terminal changes.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal attempts to switch from the inactive state to another state but fails, and switches back to the inactive state, and it is determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the connected state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the idle state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and it is determined that the terminal is about to receive multicast service data, where the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service.
  • a connected state also called an activated state
  • the terminal state changes, it is determined that the terminal retains the RLC entity.
  • the network device determines that the terminal switches from a first state to a second state, wherein when the first state is different from the second state, the terminal determines that its own state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal switches from a connected state to an inactive state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an inactive state to a connected state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an idle state to an inactive state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an inactive state to an idle state, and it is determined that the state of the terminal has changed.
  • the network device determines that the terminal fails in an attempt to switch from the first state to the second state and switches back to the first state, and determines that the state of the terminal changes.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal attempts to switch from the inactive state to another state but fails, and switches back to the inactive state, and it is determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the connected state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal attempts to switch from the inactive state to the idle state but fails, and switches back to the inactive state, and it can be determined that the state of the terminal has changed.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state, or an inactive state, and is receiving multicast service data, and the multicast service includes but is not limited to an inactive state multicast service and a connected state multicast service.
  • the network device sends a specified message to the terminal, the network device determines that the terminal retains the RLC entity.
  • the designated message may be a radio resource control (RRC) release message carrying a suspension configuration, wherein the suspension configuration is used to configure the terminal to suspend an RRC connection with a network device.
  • RRC radio resource control
  • the designated message may be an RRC reconfiguration message.
  • the designated message may be an RRC resume message.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state, or an inactive state, and determines that the terminal is about to receive multicast service data, where the multicast service includes but is not limited to an inactive state multicast service and a connected state multicast service.
  • a connected state also called an activated state
  • the network device sends a specified message to the terminal, it determines that the terminal retains the RLC entity.
  • the designated message may be a radio resource control (RRC) release message carrying a suspension configuration, wherein the suspension configuration is used to configure the terminal to suspend an RRC connection with a network device.
  • RRC radio resource control
  • the designated message may be an RRC reconfiguration message.
  • the designated message may be an RRC resume message.
  • the RLC entity is associated with an MRB, and the MRB is used to receive the multicast service data.
  • one MRB may be associated with one or more RLC entities.
  • the network device when the network device determines that the terminal retains the RLC entity, it may determine that the terminal retains the first RLC entity used for PTM transmission.
  • the network device when the network device determines that the terminal retains the RLC entity, it may determine that the terminal retains at least the first RLC entity used for PTM transmission among multiple RLC entities associated with the MRB.
  • the terminal may retain a first RLC entity for PTM transmission, but not retain a second RLC entity for point-to-point (PTP) transmission.
  • the terminal releases the second RLC entity for PTP transmission.
  • the second RLC entity for PTP transmission is rebuilt.
  • the second RLC entity for PTP transmission is suspended.
  • the terminal may reserve a first RLC entity for PTM transmission and reserve a second RLC entity for PTP transmission.
  • the terminal is in a connected state (also called an activated state), an idle state, or an inactive state, and is receiving multicast service data (or is about to receive multicast service data), and the multicast service includes but is not limited to an inactive state multicast service and a connected state multicast service.
  • the terminal state When it is determined that the terminal state has changed, it is determined that the terminal retains the RLC entity.
  • the RLC entity is associated with a multicast broadcast service radio bearer MRB, and the MRB is used to receive the multicast service data.
  • receiving multicast service data may specifically mean that the terminal has received the multicast service data and has not terminated receiving the multicast service data, or receiving multicast service data may specifically mean that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the terminal retains the RLC entity associated with the MRB, and the RLC entity is a first RLC entity for PTM transmission.
  • the terminal reserves a first RLC entity for PTM transmission, and releases, reestablishes, or suspends a second RLC entity for PTP transmission.
  • the terminal reserves a first RLC entity for PTM transmission and simultaneously reserves a second RLC entity for PTP transmission.
  • the terminal switches from a first state to a second state, wherein when the first state is different from the second state, it is determined that the terminal state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the state of the terminal is switched from a connected state to an inactive state, and it is determined that the state of the terminal has changed.
  • the state of the terminal is switched from an inactive state to a connected state, and it is determined that the state of the terminal has changed.
  • the state of the terminal is switched from an idle state to an inactive state, and it is determined that the state of the terminal has changed.
  • the state of the terminal is switched from an inactive state to an idle state, and it is determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch the state from the first state to the second state and switches back to the first state, and it is determined that the terminal state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal fails to switch from the inactive state to another state and switches back to the inactive state, and it is determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the connected state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the idle state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal is in a connected state (also called an activated state), an idle state, or an inactive state, and is receiving multicast service data (or is about to receive multicast service data), and the multicast service includes but is not limited to an inactive state multicast service and a connected state multicast service.
  • the network device sends a specified message to the terminal, it is determined that the terminal retains the RLC entity.
  • the RLC entity is associated with a multicast broadcast service radio bearer MRB, and the MRB is used to receive the multicast service data.
  • the terminal retains the RLC entity associated with the MRB, and the RLC entity is a first RLC entity for PTM transmission.
  • the terminal reserves a first RLC entity for PTM transmission, and releases, reestablishes, or suspends a second RLC entity for PTP transmission.
  • the terminal reserves a first RLC entity for PTM transmission and simultaneously reserves a second RLC entity for PTP transmission.
  • the designated message may be a radio resource control (RRC) release message carrying a suspension configuration, wherein the suspension configuration is used to configure the terminal to suspend an RRC connection with a network device.
  • RRC radio resource control
  • the designated message may be an RRC reconfiguration message.
  • the designated message may be an RRC resume message.
  • retaining the RLC entity includes any of the following: not releasing the RLC entity; not reestablishing the RLC entity; and not suspending the RLC entity.
  • the network device determines that the terminal receives multicast service data, it determines that the terminal retains the RLC entity, thereby avoiding the problem of multicast service data packet loss or service reception interruption caused by RLC reconstruction, improving the reliability of multicast service data transmission, ensuring that the network device and the terminal have a consistent understanding of the terminal behavior, and having high availability.
  • the RLC entity includes but is not limited to an RLC entity associated with an MRB, and the MRB is used to receive multicast service data.
  • the MRB may be associated with only one RLC entity, which is the first RLC entity used for PTM transmission.
  • the network device determines that the terminal receives multicast service data, it can determine that the terminal retains the first RLC entity associated with the MRB and used for PTM transmission.
  • the MRB is used to receive the multicast service data.
  • the network device determines that the terminal is receiving multicast service data or is about to receive multicast service data, it can be determined that the terminal retains the first RLC entity associated with the MRB and used for PTM transmission.
  • the MRB is used to receive multicast service data. That is, it is determined that the terminal does not release, reestablish or suspend the first RLC entity associated with the MRB and used for PTM transmission.
  • the multicast service includes, but is not limited to, an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to that the terminal is configured to receive multicast service data in the inactive state.
  • the connected multicast service may refer to that the terminal is configured to receive multicast service data in the connected state.
  • the MRB may be associated with multiple RLC entities.
  • the multiple RLC entities include at least one first RLC entity for PTM transmission and may also include at least one second RLC entity for PTP transmission.
  • the network device determines that the terminal is receiving or about to receive multicast service data, it can determine that the terminal retains the first RLC entity associated with the MRB and used for PTM transmission, that is, it determines that the terminal does not release, reestablish or suspend the first RLC entity associated with the MRB and used for PTM transmission.
  • the MRB is used to receive multicast service data.
  • the multicast service includes, but is not limited to, an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to that the terminal is configured to receive multicast service data in the inactive state.
  • the connected multicast service may refer to that the terminal is configured to receive multicast service data in the connected state.
  • the MRB may be associated with multiple RLC entities.
  • the multiple RLC entities include at least one first RLC entity for PTM transmission and may also include at least one second RLC entity for PTP transmission.
  • the network device determines that the terminal is receiving or about to receive multicast service data, it can determine that the terminal retains the first RLC entity associated with the MRB for PTM transmission.
  • the MRB is used to receive multicast service data.
  • the multicast service includes, but is not limited to, an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to that the terminal is configured to receive multicast service data in the inactive state.
  • the connected multicast service may refer to that the terminal is configured to receive multicast service data in the connected state.
  • receiving multicast service data may specifically mean that the terminal has received the multicast service data and has not terminated receiving the multicast service data, or receiving multicast service data may specifically mean that the terminal is in a receiving gap of receiving multicast service data, which is not limited in the present disclosure.
  • the terminal is about to receive multicast service data, which may mean that the terminal has not received any multicast service data before and is about to receive multicast service data from the network device according to the actual service needs of the terminal.
  • the network device determines that the terminal receives multicast service data, it can be determined that the terminal retains the RLC entity. Specifically, when the MRB is associated with multiple RLC entities, it can be determined that the terminal only retains the first RLC entity used for PTM transmission among the multiple RLC entities, and releases, reconstructs or suspends the second RLC entity used for PTP transmission. Alternatively, it can also be determined that the terminal retains the first RLC entity used for PTM transmission among the multiple RLC entities, and retains the second RLC entity used for PTP transmission among the multiple RLC entities. This avoids the problem of multicast service data packet loss or service reception interruption caused by RLC reconstruction, improves the reliability of multicast service data transmission, ensures that the network device and the terminal have a consistent understanding of the terminal behavior, and has high availability.
  • the network device determines that the state of the terminal has changed and that the terminal receives the multicast service data, determines that the terminal retains the RLC entity, including but not limited to determining that the terminal does not release, reestablish or suspend the RLC entity.
  • the network device determines that the terminal switches from a first state to a second state, wherein when the first state is different from the second state, the terminal determines that its own state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal switches from a connected state to an inactive state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an inactive state to a connected state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an idle state to an inactive state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an inactive state to an idle state, and it is determined that the state of the terminal has changed.
  • the network device determines that the terminal fails in an attempt to switch from the first state to the second state and switches back to the first state, and determines that the state of the terminal changes.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal attempts to switch from the inactive state to another state but fails, and switches back to the inactive state, and it is determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the connected state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the idle state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and it is determined that the terminal is about to receive multicast service data, where the multicast service includes but is not limited to an inactivated state multicast service and a connected state multicast service.
  • a connected state also called an activated state
  • the terminal state changes, it is determined that the terminal retains the RLC entity.
  • the network device determines that the terminal switches from a first state to a second state, wherein when the first state is different from the second state, the terminal determines that its own state has changed.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal switches from a connected state to an inactive state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an inactive state to a connected state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an idle state to an inactive state, and it is determined that the state of the terminal has changed.
  • the terminal switches from an inactive state to an idle state, and it is determined that the state of the terminal has changed.
  • the network device determines that the terminal fails in an attempt to switch from the first state to the second state and switches back to the first state, and determines that the state of the terminal changes.
  • the first state is a connected state and the second state is an inactive state
  • the first state is a connected state and the second state is an idle state
  • the first state is an idle state and the second state is a connected state
  • the first state is an idle state and the second state is an inactive state
  • the first state is an inactive state and the second state is a connected state
  • the first state is an inactive state and the second state is an idle state.
  • the terminal attempts to switch from the inactive state to another state but fails, and switches back to the inactive state, and it is determined that the state of the terminal has changed.
  • the terminal fails in an attempt to switch from the inactive state to the connected state and switches back to the inactive state, it can be determined that the state of the terminal has changed.
  • the terminal attempts to switch from the inactive state to the idle state but fails, and switches back to the inactive state, and it can be determined that the state of the terminal has changed.
  • the network device determines that the state of the terminal has changed, and when the terminal receives multicast service data, it determines that the terminal retains the RLC entity, thereby avoiding the problem of multicast service data packet loss or service reception interruption caused by RLC reconstruction, improving the reliability of multicast service data transmission, ensuring that the network device and the terminal have consistent understanding of the terminal behavior, and high availability.
  • the network device sends a specified message to the terminal, and when determining that the terminal receives the multicast service data, determines that the terminal retains the RLC entity, including but not limited to determining that the terminal does not release, reestablish or suspend the RLC entity.
  • the designated message may be a radio resource control (RRC) release message carrying a suspension configuration, wherein the suspension configuration is used to configure the terminal to suspend the RRC connection with the network device.
  • RRC radio resource control
  • the network device can send a wireless resource control RRC release message carrying a suspension configuration to the terminal, and when it is determined that the terminal is receiving a multicast service, determine that the terminal retains the RLC entity, including but not limited to determining that the terminal does not release, reestablish or suspend the RLC entity.
  • the network device can send a wireless resource control RRC release message carrying a suspension configuration to the terminal, and when it is determined that the terminal is about to receive a multicast service, determine that the terminal retains the RLC entity, including but not limited to determining that the terminal does not release, reestablish or suspend the RLC entity.
  • the designated message may be an RRC reconfiguration message.
  • the network device may send an RRC reconfiguration message to the terminal, and when determining that the terminal is receiving a multicast service, determine that the terminal retains the RLC entity, including but not limited to determining that the terminal does not release, reestablish or suspend the RLC entity.
  • the network device can send an RRC reconfiguration message to the terminal, and when it is determined that the terminal is about to receive a multicast service, determine that the terminal retains the RLC entity, including but not limited to determining that the terminal does not release, reestablish or suspend the RLC entity.
  • the designated message may be an RRC resume message.
  • the network device may send an RRC recovery message to the terminal, and when determining that the terminal is receiving a multicast service, determine that the terminal retains the RLC entity, including but not limited to determining that the terminal does not release, reestablish or suspend the RLC entity.
  • the network device can send an RRC recovery message to the terminal, and when it is determined that the terminal is about to receive a multicast service, determine that the terminal retains the RLC entity, including but not limited to determining that the terminal does not release, reestablish or suspend the RLC entity.
  • the network device can send a specified message to the terminal, and when it is determined that the terminal receives multicast service data, it is determined that the terminal can retain the RLC entity, thereby avoiding the problem of multicast service data packet loss or service reception interruption caused by RLC reconstruction, improving the reliability of multicast service data transmission, ensuring that the network device and the terminal have a consistent understanding of the terminal behavior, and having high availability.
  • FIG. 5 is a flow chart of a method for transmitting multicast service data according to an embodiment, which may be executed by a network device, including but not limited to a base station, an access network device, etc., wherein the base station may be a 4G base station, a 5G base station, or a future 6G base station, and the access network device may be a 4G access network device, a 5G access network device, or a future 6G access network device, etc.
  • the method may include the following steps:
  • step 501 when the terminal stops receiving the multicast service data, it is determined that the terminal does not retain the RLC entity.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state and determines that the terminal stops receiving multicast service data, it can be determined that the terminal does not retain the RLC entity.
  • a connected state also called an activated state
  • an idle state or an inactivated state determines that the terminal stops receiving multicast service data
  • the multicast service includes but is not limited to an inactive multicast service.
  • the inactive multicast service may refer to a terminal being configured to receive multicast service data in an inactive state.
  • the multicast service may include but is not limited to an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to the terminal being configured to receive multicast service data in an inactive state.
  • the connected multicast service may refer to the terminal being configured to receive multicast service data in a connected state.
  • the network device when the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and determines that the first multicast service configuration information used by the terminal is invalid, it can be determined to stop receiving the multicast service data. At this time, it is determined that the terminal does not retain the RLC entity.
  • a connected state also called an activated state
  • an idle state or an inactivated state when the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and determines that the first multicast service configuration information used by the terminal is invalid, it can be determined to stop receiving the multicast service data. At this time, it is determined that the terminal does not retain the RLC entity.
  • the cell where the terminal resides does not support the multicast service, it can be determined that the first multicast service configuration information used by the terminal is invalid.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and because the terminal moves, the cell where the terminal currently resides does not support the multicast service, and determines that the terminal stops receiving the multicast service data, and accordingly, determines that the terminal does not retain the RLC entity.
  • a connected state also called an activated state
  • an idle state or an inactivated state
  • the terminal moves to an area that does not support an inactive multicast service, it may be determined that the cell where the terminal resides does not support the multicast service.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and because the terminal moves, the terminal moves to an area that does not support inactivated multicast services. It can be determined that the resident cell of the terminal does not support multicast services. Further, it can be determined that the first multicast service configuration information used by the terminal is invalid. At this time, it is determined that the terminal stops receiving the multicast service data, and it can be determined that the terminal does not retain the RLC entity.
  • the network device determines that the terminal moves from a first cell supporting the multicast service to a second cell not supporting the multicast service, and determines that the resident cell does not support the multicast service.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and because the terminal moves, the terminal moves from a first cell that supports multicast services to a second cell that does not support multicast services. It can be determined that the resident cell of the terminal does not support multicast services. Further, it can be determined that the first multicast service configuration information used by the terminal is invalid. At this time, it is determined that the terminal stops receiving the multicast service data, and it can be determined that the terminal does not retain the RLC entity.
  • the network device determines that the first multicast service configuration information is invalid when the camping cell of the terminal does not support the first multicast service configuration information.
  • the network device determines that the terminal moves to an area that does not support inactive multicast service configuration information, and determines that the resident cell does not support the first multicast service configuration information.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state, or an inactive state, and because the terminal moves, the terminal moves to an area that does not support the inactive state multicast service configuration information, determines that the resident cell does not support the first multicast service configuration information, and further determines that the first multicast service configuration information is invalid. At this time, it is determined that the terminal stops receiving the multicast service data and determines that the terminal does not retain the RLC entity.
  • a connected state also called an activated state
  • an idle state also called an inactive state
  • the network device determines that the terminal moves from a third cell that supports multicast services and supports the first multicast service configuration information to a fourth cell that supports multicast services but supports the second multicast service configuration information, and determines that the resident cell does not support the first multicast service configuration information.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state, or an inactive state, and due to the movement of the terminal, the terminal moves from a third cell that supports the multicast service and supports the first multicast service configuration information to a fourth cell that supports the multicast service but supports the second multicast service configuration information, and determines that the resident cell does not support the first multicast service configuration information. Further, it is determined that the first multicast service configuration information is invalid. At this time, it is determined that the terminal stops receiving the multicast service data and determines that the terminal does not retain the RLC entity.
  • the network device determines that the first multicast service configuration information is invalid when determining that the validity period of the first multicast service configuration information has expired.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state, or an inactive state, and the timer corresponding to the first multicast service configuration information expires, then the terminal can determine that the validity period of the first multicast service configuration information has expired. Further, it is determined that the first multicast service configuration information is invalid. At this time, it is determined that the terminal stops receiving the multicast service data, and it is determined that the terminal does not retain the RLC entity.
  • a connected state also called an activated state
  • an idle state also called an inactive state
  • the timer corresponding to the first multicast service configuration information expires
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and determines that the multicast service session is deactivated, and determines that the terminal stops receiving the multicast service data. At this time, it is determined that the terminal does not retain the RLC entity.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, the terminal stops receiving the multicast service data, and the terminal is still in the RNA, and determines that the terminal does not retain the RLC entity.
  • a connected state also called an activated state
  • the terminal stops receiving the multicast service data
  • the terminal is still in the RNA, and determines that the terminal does not retain the RLC entity.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, the first multicast service configuration information used by the terminal is invalid, and the terminal is still in the RNA, then it can be determined that the terminal does not retain the RLC entity.
  • a connected state also called an activated state
  • an idle state or an inactivated state the first multicast service configuration information used by the terminal is invalid
  • the terminal is still in the RNA
  • the terminal determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, the cell where the terminal resides does not support multicast services, and the terminal is still in the RNA, it can be determined that the terminal does not retain the RLC entity.
  • a connected state also called an activated state
  • an idle state or an inactivated state
  • the cell where the terminal resides does not support multicast services, and the terminal is still in the RNA, it can be determined that the terminal does not retain the RLC entity.
  • the network device determines that the terminal moves to an area that does not support inactive multicast services, or the terminal moves from a first cell that supports multicast services to a second cell that does not support multicast services, and can determine that the resident cell does not support the multicast service.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, the cell where the terminal resides does not support the first multicast service configuration information, and the terminal is still in the RNA, it can be determined that the terminal does not retain the RLC entity.
  • a connected state also called an activated state
  • an idle state or an inactivated state the cell where the terminal resides does not support the first multicast service configuration information, and the terminal is still in the RNA, it can be determined that the terminal does not retain the RLC entity.
  • the network device determines that the terminal moves to an area that does not support the inactive multicast service configuration information, or the terminal moves from a third cell that supports the multicast service and supports the first multicast service configuration information to a fourth cell that supports the multicast service but supports the second multicast service configuration information. It can be determined that the resident cell does not support the first multicast service configuration information.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state or an inactivated state, and the validity period of the first multicast service configuration information has exceeded, and the terminal is still in the RNA, then it can be determined that the terminal does not retain the RLC entity.
  • a connected state also called an activated state
  • an idle state or an inactivated state the validity period of the first multicast service configuration information has exceeded
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state, or an inactivated state
  • the multicast service session is deactivated, and the terminal is still in the RNA, it can be determined that the terminal does not retain the RLC entity.
  • the RLC entity is associated with an MRB, and the MRB is used to receive the multicast service data.
  • the network device when the network device determines that the terminal does not retain the RLC entity, it may determine that the terminal releases the first RLC entity used for PTM transmission.
  • the network device when the network device determines that the terminal does not retain the RLC entity, it may determine that the terminal reestablishes the first RLC entity for PTM transmission.
  • the network device when the network device determines that the terminal does not retain the RLC entity, it may determine that the terminal suspends the first RLC entity used for PTM transmission.
  • the RLC entity is associated with an MRB
  • the MRB is used to receive the multicast service data
  • the number of the RLC entities associated with the MRB is multiple.
  • the network device determines that the terminal does not retain the RLC entity, it can be determined that the terminal does not retain at least the first RLC entity used for PTM transmission.
  • the network device determines that the terminal releases a first RLC entity used for PTM transmission and reserves a second RLC entity used for PTP transmission.
  • the network device determines that the terminal reestablishes the first RLC entity for PTM transmission and reserves the second RLC entity for PTP transmission.
  • the network device determines that the terminal suspends the first RLC entity used for PTM transmission and reserves the second RLC entity used for PTP transmission.
  • the network device determines that the terminal releases, reestablishes, or suspends a first RLC entity used for PTM transmission, and releases, reestablishes, or suspends a second RLC entity used for PTP transmission.
  • the network device determines that the terminal is in a connected state (also called an activated state), an idle state, or an inactive state, and stops receiving multicast services, and determines that the terminal does not retain the RLC entity.
  • the RLC entity is associated with a multicast broadcast service radio bearer MRB, and the MRB is used to receive the multicast service data.
  • the terminal releases, reestablishes or suspends the RLC entity associated with the MRB, and the RLC entity is a first RLC entity for PTM transmission.
  • the terminal releases, reestablishes or suspends a first RLC entity used for PTM transmission and reserves a second RLC entity used for PTP transmission.
  • the terminal releases, reestablishes or suspends a first RLC entity used for PTM transmission, and simultaneously releases, reestablishes or suspends a second RLC entity used for PTP transmission.
  • the network device when the network device determines that the terminal stops receiving multicast service data, it can determine that the terminal does not retain the RLC entity, thereby avoiding the waste of resources caused by retaining the RLC entity when the reception of multicast service data is stopped, and can ensure the subsequent reconstruction of the RLC entity, thereby improving the reliability of multicast service data transmission, ensuring that the network device and the terminal have a consistent understanding of the terminal behavior, and having high availability.
  • the network device may determine that the terminal stops receiving the multicast service data, and at this time determines that the terminal does not retain the RLC entity.
  • the network device may determine that the terminal stops receiving the multicast service data, and at this time determines that the terminal does not retain the RLC entity.
  • not retaining the RLC entity includes but is not limited to releasing, reestablishing or suspending the RLC entity.
  • the network device can determine that the terminal does not retain the RLC entity when it is determined that the terminal stops receiving multicast service data, thereby improving the reliability of multicast service data transmission, ensuring that the network device and the terminal have consistent understanding of the terminal behavior, and having high availability.
  • the network device may determine that the first multicast service configuration information is invalid when it is determined that the cell where the terminal resides does not support the multicast service. At this time, it may be determined that the terminal stops receiving the multicast service data and does not retain the RLC entity.
  • the terminal moves from an area supporting an inactive multicast service to an area not supporting an inactive multicast service, it can be determined that the cell where the terminal resides does not support the multicast service.
  • the terminal moves to an area that does not support non-activated multicast services, it is determined that the resident cell does not support multicast services, and further determines that the first multicast service configuration information used by the terminal is invalid. At this time, it can be determined that the terminal stops receiving the multicast service data and does not retain the RLC entity. Specifically, it can be determined that the terminal releases, reestablishes or suspends the RLC entity.
  • the terminal moves from a first cell supporting a multicast service to a second cell not supporting a multicast service, it can be determined that the cell where the terminal resides does not support the multicast service.
  • a terminal moves from a first cell supporting multicast services to a second cell that does not support multicast services, it is determined that the cell where the terminal resides does not support multicast services, and further, it is determined that the first multicast service configuration information used by the terminal is invalid.
  • the terminal stops receiving the multicast service data, and it is determined that the terminal does not retain the RLC entity.
  • the terminal releases, reestablishes or suspends the RLC entity.
  • the terminal when the cell where the terminal resides does not support the first multicast service configuration information, it can be determined that the first multicast service configuration information is invalid. At this time, it can be determined that the terminal stops receiving the multicast service data and determines that the terminal does not retain the RLC entity.
  • a terminal moves from an area supporting the inactive multicast service configuration information to an area not supporting the inactive multicast service configuration information, it can be determined that the resident cell of the terminal does not support the first multicast service configuration information.
  • the terminal determines that the resident cell does not support the first multicast service configuration information used by the terminal, and further determines that the first multicast service configuration information used by the terminal is invalid. At this time, it can be determined that the terminal stops receiving the multicast service data, and determines that the terminal does not retain the RLC entity. Specifically, it can be determined that the terminal releases, reestablishes or suspends the RLC entity.
  • the terminal moves from a third cell supporting multicast service and supporting the first multicast service configuration information to a fourth cell supporting multicast service but supporting the second multicast service configuration information, and determines that the resident cell does not support the first multicast service configuration information.
  • a terminal moves from a third cell that supports multicast services and supports the first multicast service configuration information to a fourth cell that supports multicast services but supports the second multicast service configuration information
  • the terminal determines that the resident cell does not support the first multicast service configuration information used by the terminal, and further determines that the first multicast service configuration information used by the terminal is invalid.
  • the terminal stops receiving the multicast service data, and determines that the terminal does not retain the RLC entity. Specifically, it can be determined that the terminal releases, reestablishes or suspends the RLC entity.
  • the terminal stops receiving the multicast service data and determines that the terminal does not retain the RLC entity.
  • a timer corresponding to the first multicast service configuration information times out, and it is determined that the first multicast service configuration information exceeds a validity period.
  • the timer corresponding to the first multicast service configuration information if the timer corresponding to the first multicast service configuration information times out, it is determined that the first multicast service configuration information has exceeded its validity period, and further, it is determined that the first multicast service configuration information used by the terminal is invalid. At this time, it can be determined that the terminal stops receiving the multicast service data, and it is determined that the terminal does not retain the RLC entity. Specifically, it can be determined that the terminal releases, reconstructs or suspends the RLC entity.
  • the terminal moves to an area that does not support inactive multicast services and the terminal is still in a notification area RNA based on a radio access network RAN, it can be determined that the resident cell of the terminal does not support multicast services.
  • the terminal determines that the resident cell does not support multicast services, and further determines that the first multicast service configuration information used by the terminal is invalid. At this time, it can be determined that the terminal stops receiving the multicast service data, and determines that the terminal does not retain the RLC entity. Specifically, it can be determined that the terminal releases, reestablishes or suspends the RLC entity.
  • the terminal moves from a first cell supporting multicast services to a second cell not supporting multicast services, and the terminal is still in a notification area RNA based on a radio access network RAN, it can be determined that the resident cell of the terminal does not support multicast services.
  • a terminal moves from a first cell supporting multicast services to a second cell that does not support multicast services, and the terminal is still in a notification area RNA based on a wireless access network RAN, the terminal determines that the resident cell does not support multicast services, and further determines that the first multicast service configuration information used by the terminal is invalid.
  • the terminal stops receiving the multicast service data, and determines that the terminal does not retain the RLC entity.
  • the terminal releases, reestablishes or suspends the RLC entity.
  • the resident cell of the terminal does not support the first multicast service configuration information and the terminal is still in a notification area RNA based on a radio access network RAN, it can be determined that the first multicast service configuration information is invalid. At this time, it can be determined that the terminal stops receiving the multicast service data and determines that the terminal does not retain the RLC entity.
  • the terminal moves to an area that does not support inactive multicast service configuration information and the terminal is still in a notification area RNA based on a radio access network RAN, it can be determined that the resident cell of the terminal does not support the first multicast service configuration information.
  • the terminal determines that the resident cell does not support the first multicast service configuration information used by the terminal, and further determines that the first multicast service configuration information used by the terminal is invalid.
  • the terminal stops receiving the multicast service data, and determines that the terminal does not retain the RLC entity. Specifically, it can be determined that the terminal releases, reestablishes or suspends the RLC entity.
  • the terminal moves from a third cell that supports multicast services and supports the first multicast service configuration information to a fourth cell that supports multicast services but supports the second multicast service configuration information, and the terminal is still in a notification area RNA based on a wireless access network RAN, it is determined that the resident cell does not support the first multicast service configuration information.
  • a terminal moves from a third cell that supports multicast services and supports the first multicast service configuration information to a fourth cell that supports multicast services but supports the second multicast service configuration information, and the terminal is still in a notification area RNA based on a wireless access network RAN, it is determined that the resident cell does not support the first multicast service configuration information used by the terminal, and further determines that the first multicast service configuration information used by the terminal is invalid.
  • the terminal stops receiving the multicast service data, and determines that the terminal does not retain the RLC entity. Specifically, it can be determined that the terminal releases, reestablishes or suspends the RLC entity.
  • the terminal stops receiving the multicast service data and determines that the terminal does not retain the RLC entity.
  • the timer corresponding to the first multicast service configuration information times out and the terminal is still in the notification area RNA based on the radio access network RAN, it is determined that the first multicast service configuration information exceeds the validity period.
  • the terminal determines that the validity period of the first multicast service configuration information has expired, and further determines that the first multicast service configuration information used by the terminal is invalid. At this time, it can be determined that the terminal stops receiving the multicast service data, and determines that the terminal does not retain the RLC entity. Specifically, it can be determined that the terminal releases, reestablishes or suspends the RLC entity.
  • the terminal when the multicast service session of the terminal is deactivated and the terminal is still in the notification area RNA based on the radio access network RAN, it can be determined that the terminal stops receiving the multicast service data and that the terminal does not retain the RLC entity. Specifically, it can be determined that the terminal releases, reestablishes or suspends the RLC entity.
  • the terminal when the first multicast service configuration information used by the terminal is invalid or the multicast service session is deactivated, it is determined that the terminal stops receiving the multicast service data, and accordingly, it is determined that the terminal does not retain the RLC entity.
  • the reliability of multicast service data transmission is improved, and the understanding of the network device and the terminal is consistent with respect to the terminal behavior, and the availability is high.
  • the RLC entity includes but is not limited to an RLC entity associated with an MRB, and the MRB is used to receive multicast service data.
  • the MRB may be associated with only one RLC entity, which is the first RLC entity used for PTM transmission.
  • the terminal stops receiving the multicast service data it can be determined that the terminal releases, suspends or reestablishes the first RLC entity used for PTM transmission.
  • the MRB is used to receive the multicast service data.
  • the multicast service includes but is not limited to an inactive multicast service and a connected multicast service.
  • An inactive multicast service may refer to a terminal being configured to receive multicast service data in an inactive state.
  • a connected multicast service may refer to a terminal being configured to receive multicast service data in a connected state.
  • the MRB may be associated with multiple RLC entities.
  • the multiple RLC entities include at least one first RLC entity for PTM transmission and may also include at least one second RLC entity for PTP transmission.
  • the terminal stops receiving multicast service data it can be determined that the terminal releases, suspends or reestablishes the first RLC entity for PTM transmission.
  • the MRB is used to receive multicast service data.
  • the terminal retains the second RLC entity for PTP transmission among multiple RLC entities.
  • the multicast service includes, but is not limited to, an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to that the terminal is configured to receive multicast service data in the inactive state.
  • the connected multicast service may refer to that the terminal is configured to receive multicast service data in the connected state.
  • the MRB may be associated with multiple RLC entities.
  • the multiple RLC entities include at least one first RLC entity for PTM transmission and may also include at least one second RLC entity for PTP transmission.
  • the terminal stops receiving multicast service data it can be determined that the terminal releases, suspends or reestablishes the first RLC entity for PTM transmission.
  • the MRB is used to receive multicast service data.
  • the multicast service includes, but is not limited to, an inactive multicast service and a connected multicast service.
  • the inactive multicast service may refer to that the terminal is configured to receive multicast service data in the inactive state.
  • the connected multicast service may refer to that the terminal is configured to receive multicast service data in the connected state.
  • the terminal when it is determined that the terminal stops receiving multicast service data, it can be determined that the terminal releases, suspends or reconstructs the RLC entity. Specifically, when the MRB is associated with multiple RLC entities, it can be determined that the terminal does not retain the first RLC entity for PTM transmission and retains the second RLC entity for PTP transmission. Alternatively, it can also be determined that the terminal does not retain the first RLC entity and does not retain the second RLC entity. This avoids the waste of resources caused by retaining the RLC entity when the reception of multicast service data is stopped, and can ensure the reconstruction of the subsequent RLC entity, thereby improving the reliability of multicast service data transmission, ensuring that the network device and the terminal have a consistent understanding of the terminal behavior, and having high availability.
  • step 401 and 501 can be implemented separately or in combination.
  • step 401 can be executed first and then step 501, or step 501 can be executed first and then step 401.
  • step 501 can be executed first and then step 401.
  • the present disclosure does not limit this.
  • FIG. 6 is a flow chart of a method for transmitting multicast service data according to an embodiment. The method can be applied to the network architecture shown in FIG. 1 , and includes the following steps:
  • step 601 when the terminal determines to receive multicast service data, it reserves a radio link control RLC entity.
  • step 602 when the terminal receives multicast service data, the network device determines that the terminal retains a radio link control RLC entity.
  • the network device can continue to send the multicast service data to the terminal through the retained RLC entity, and the terminal only needs to receive the multicast service data.
  • the terminal can retain the RLC entity when receiving multicast service data, and the network device determines that the terminal can retain the RLC entity when determining that the terminal receives multicast service data, thereby avoiding the problem of multicast service data packet loss or service reception interruption caused by RLC reconstruction, improving the reliability of multicast service data transmission, ensuring that the network device and the terminal have a consistent understanding of the terminal behavior, and having high availability.
  • FIG. 7 is a flow chart of a method for transmitting multicast service data according to an embodiment.
  • the method may be applicable to the network architecture shown in FIG. 1 , and includes the following steps:
  • step 701 the terminal determines to stop receiving multicast service data and does not retain the RLC entity.
  • step 702 the network device determines that the terminal stops receiving the multicast service data and determines that the terminal does not retain the RLC entity.
  • the network device stops sending the multicast service data to the terminal, and the terminal stops receiving the multicast service data.
  • the RLC entity when the terminal stops receiving multicast service data, the RLC entity may not be retained.
  • the network device determines that the terminal stops receiving multicast service data, it may determine that the terminal does not retain the RLC entity. This avoids the waste of resources caused by retaining the RLC entity when the multicast service data is stopped, and ensures the subsequent reconstruction of the RLC entity, thereby improving the reliability of multicast service data transmission, ensuring that the network device and the terminal have the same understanding of the terminal behavior, and having high availability.
  • Embodiment 1 A solution for retaining the RLC entity.
  • the RLC entity is retained, specifically including:
  • the terminal When the terminal receives a multicast service, it does not release, reestablish or suspend the RLC entity.
  • the RLC entity is retained. Specifically, the RLC entity is not released, reestablished, or suspended.
  • the RLC entity includes an RLC entity associated with an MRB for receiving multicast services. Further, for a scenario where one MRB is associated with multiple RLC entities, only the RLC entity for PTM transmission may be retained, and the RLC entity for PTP transmission may not be retained, including but not limited to releasing, reestablishing or suspending the RLC entity for PTP transmission.
  • the multicast service includes an inactive multicast service, that is, a multicast service in which a terminal can still receive service data when the terminal is in an inactive state.
  • the RLC entity For a terminal that performs multicast service reception, when the terminal receives an RRC Release message, an RRC reconfiguration message or an RRC recovery message with a suspension configuration sent by a network device, the RLC entity is retained, specifically, the RLC entity is not released, rebuilt or suspended.
  • the RLC entity includes an RLC entity associated with an MRB for receiving multicast services. Further, for a scenario where one MRB is associated with multiple RLC entities, only the RLC entity for PTM transmission is retained, and the RLC entity for PTP transmission is not retained, including but not limited to releasing, reestablishing or suspending the RLC entity for PTP transmission.
  • the RLC entity includes an RLC entity associated with an MRB for receiving multicast services. Further, for a scenario where one MRB is associated with multiple RLC entities, the RLC entity for PTM transmission is retained, and the RLC entity for PTP transmission is retained, including but not limited to not releasing, not reestablishing, or not suspending the RLC entity for PTM transmission, and not releasing, not reestablishing, or not suspending the RLC entity for PTP transmission.
  • the multicast service includes an inactive multicast service, that is, a multicast service in which a terminal can still receive service data when the terminal is in an inactive state.
  • Embodiment 2 a solution in which the RLC entity is not retained.
  • the RLC entity When the terminal stops receiving multicast services, the RLC entity is not retained. Specifically, it includes:
  • the terminal When the terminal stops receiving the multicast service, it releases, reestablishes or suspends the RLC entity.
  • the terminal does not retain the RLC entity, including:
  • the cell where the terminal currently resides does not support the multicast service or the first multicast service configuration information, and the terminal does not retain the RLC entity.
  • the terminal moves out of the area supporting the inactive multicast service or moves out of the area supporting the inactive multicast service configuration. Further, the terminal is still in the RNA, and the terminal does not retain the RLC entity.
  • the terminal moves from a first cell supporting the multicast service to a second cell not supporting the multicast service. Furthermore, the terminal is still in the RNA, and the terminal does not retain the RLC entity.
  • the terminal starts from a third cell that supports the multicast service and the first multicast service configuration information. Furthermore, the terminal is still in the RNA, and the terminal does not retain the RLC entity.
  • the validity period of the first multicast service configuration information exceeds, for example, a timer corresponding to the first multicast service configuration information expires.
  • the validity period of the first multicast service configuration information when the current cell where the terminal resides does not support the multicast service or the first multicast service configuration information, and the validity period of the first multicast service configuration information has expired, for example, a timer corresponding to the first beacon service configuration information expires.
  • the terminal when the multicast service session is deactivated, the terminal does not retain the RLC entity.
  • Embodiment 2 wherein not retaining the RLC entity includes releasing, reestablishing or suspending the RLC entity associated with the MRB for receiving the inactive multicast service.
  • one MRB is associated with multiple RLC entities, it includes but is not limited to not reserving (releasing, reestablishing or suspending) the RLC entity used for PTM transmission.
  • the multicast service includes an inactive multicast service.
  • the reliability of multicast service data transmission is improved and the availability is high.
  • the present disclosure also provides an application function implementation device embodiment.
  • FIG. 8 is a block diagram of a device for transmitting multicast service data according to an exemplary embodiment, wherein the device is applied to a terminal and includes:
  • the execution module 801 is configured to reserve a radio link control RLC entity when it is determined to receive multicast service data.
  • FIG. 9 is a block diagram of a transmission device for multicast service data according to an exemplary embodiment, wherein the device is applied to a network device and includes:
  • the determination module 901 is configured to determine that the terminal retains a radio link control RLC entity when the terminal receives multicast service data.
  • the relevant parts can refer to the partial description of the method embodiments.
  • the device embodiments described above are only schematic, wherein the units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the disclosed solution. A person of ordinary skill in the art may understand and implement it without creative work.
  • the present disclosure further provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is used to execute any of the multicast service data transmission methods described above on the terminal side.
  • the present disclosure also provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is used to execute any of the multicast service data transmission methods described above on the network device side.
  • the present disclosure also provides a transmission device for multicast service data, including:
  • a memory for storing processor-executable instructions
  • the processor is configured to execute any of the multicast service data transmission methods described above on the terminal side.
  • Fig. 10 is a block diagram of a multicast service data transmission device 1000 according to an exemplary embodiment.
  • the device 1000 may be a mobile phone, tablet computer, e-book reader, multimedia player, wearable device, vehicle-mounted user equipment, iPad, smart TV or other terminal.
  • device 1000 may include one or more of the following components: a processing component 1002 , a memory 1004 , a power component 1006 , a multimedia component 1008 , an audio component 1010 , an input/output (I/O) interface 1012 , a sensor component 1016 , and a communication component 1018 .
  • a processing component 1002 may include one or more of the following components: a processing component 1002 , a memory 1004 , a power component 1006 , a multimedia component 1008 , an audio component 1010 , an input/output (I/O) interface 1012 , a sensor component 1016 , and a communication component 1018 .
  • a processing component 1002 may include one or more of the following components: a processing component 1002 , a memory 1004 , a power component 1006 , a multimedia component 1008 , an audio component 1010 , an input/output (I/O) interface 1012 , a sensor component 1016 , and a communication component
  • the processing component 1002 generally controls the overall operation of the device 1000, such as operations associated with display, phone calls, random access to data, camera operations, and recording operations.
  • the processing component 1002 may include one or more processors 1020 to execute instructions to complete all or part of the steps of the above-mentioned method for transmitting multicast service data.
  • the processing component 1002 may include one or more modules to facilitate the interaction between the processing component 1002 and other components.
  • the processing component 1002 may include a multimedia module to facilitate the interaction between the multimedia component 1008 and the processing component 1002.
  • the processing component 1002 can read executable instructions from a memory to implement the steps of a method for transmitting multicast service data provided in the above-mentioned embodiments.
  • the memory 1004 is configured to store various types of data to support the operation of the device 1000. Examples of such data include instructions for any application or method operating on the device 1000, contact data, phone book data, messages, pictures, videos, etc.
  • the memory 1004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory
  • flash memory magnetic disk or optical disk.
  • the power supply component 1006 provides power to the various components of the device 1000.
  • the power supply component 1006 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 1000.
  • the multimedia component 1008 includes a display screen that provides an output interface between the device 1000 and the user.
  • the multimedia component 1008 includes a front camera and/or a rear camera.
  • the front camera and/or the rear camera can receive external multimedia data.
  • Each front camera and rear camera can be a fixed optical lens system or have a focal length and optical zoom capability.
  • the audio component 1010 is configured to output and/or input audio signals.
  • the audio component 1010 includes a microphone (MIC), and when the device 1000 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal.
  • the received audio signal can be further stored in the memory 1004 or sent via the communication component 1018.
  • the audio component 1010 also includes a speaker for outputting audio signals.
  • I/O interface 1012 provides an interface between processing component 1002 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.
  • the sensor assembly 1016 includes one or more sensors for providing various aspects of the status assessment of the device 1000.
  • the sensor assembly 1016 can detect the open/closed state of the device 1000, the relative positioning of components, such as the display and keypad of the device 1000, the sensor assembly 1016 can also detect the position change of the device 1000 or a component of the device 1000, the presence or absence of user contact with the device 1000, the orientation or acceleration/deceleration of the device 1000, and the temperature change of the device 1000.
  • the sensor assembly 1016 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact.
  • the sensor assembly 1016 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 1016 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 1018 is configured to facilitate wired or wireless communication between the device 1000 and other devices.
  • the device 1000 can access a wireless network based on a communication standard, such as Wi-Fi, 2G, 3G, 4G, 5G or 6G, or a combination thereof.
  • the communication component 1018 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel.
  • the communication component 1018 also includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the apparatus 1000 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components, and may be used to execute any of the multicast service data transmission methods described above on the terminal side.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • controllers microcontrollers, microprocessors or other electronic components
  • a non-transitory machine-readable storage medium including instructions is also provided, such as a memory 1004 including instructions, and the instructions can be executed by the processor 1020 of the device 1000 to complete the above-mentioned multicast service data transmission method.
  • the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
  • the present disclosure also provides a transmission device for multicast service data, including:
  • a memory for storing processor-executable instructions
  • the processor is configured to execute any of the multicast service data transmission methods described above on the network device side.
  • FIG. 11 is a schematic diagram of a structure of a transmission device 1100 for multicast service data according to an exemplary embodiment.
  • the device 1100 may be provided as a network device.
  • the device 1100 includes a processing component 1122, a wireless transmission/reception component 1124, an antenna component 1126, and a signal processing part specific to a wireless interface, and the processing component 1122 may further include at least one processor.
  • One of the processors in the processing component 1122 may be configured to execute any of the above-mentioned methods for transmitting multicast service data.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开提供一种组播业务数据的传输方法及装置、存储介质，其中，所述方法包括：当确定接收组播业务数据，保留无线链路控制RLC实体。本公开可以避免因RLC重建导致的组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，可用性高。

Description

组播业务数据的传输方法及装置、存储介质 技术领域
本公开涉及通信领域，尤其涉及组播业务数据的传输方法及装置、存储介质。
背景技术
在版本17(Release 17，R17)中仅支持连接态终端的组播业务接收，即终端如果要执行组播业务数据接收，必须先建立无线资源控制(Radio Resource Control，RRC)连接，终端进入连接态后进行组播业务数据接收。显然，这不能满足例如组播广播业务(Multicast Broadcast Service，MBS)关键业务的需求，特别是对于终端数量较多的小区，会使得网络设备的负载增加，且无法确保MBS关键业务的时效性。另外，在进行组播业务数据接收时，终端需要保持处于RRC连接态(RRC_CONNECTED)，造成终端的功耗很大。
可以看出，终端需要处于连接态执行组播业务数据的接收机制有待完善。
发明内容
为克服相关技术中存在的问题，本公开实施例提供一种组播业务数据的传输方法及装置、存储介质。
根据本公开实施例的第一方面，提供一种组播业务数据的传输方法，所述方法由终端执行，包括：
当确定接收组播业务数据，保留无线链路控制RLC实体。
可选地，所述组播业务包括非激活态组播业务。
可选地，所述当确定接收组播业务数据，保留无线链路控制RLC实体，包括：
当所述终端的状态发生改变，且确定接收所述组播业务数据，保留所述RLC实体。
可选地，所述终端的状态发生改变，包括：
所述终端从第一状态切换到第二状态，所述第一状态与所述第二状态不同；或者
所述终端从所述第一状态切换到所述第二状态失败，并切换回所述第一状态。
可选地，所述终端的状态发生改变，包括：
所述终端从连接态切换到非激活态；
所述终端从非激活态切换到连接态；
所述终端尝试从非激活态切换到其他状态失败，并切换回非激活态。
可选地，在所述保留无线链路控制RLC实体之前，所述方法还包括：
接收到网络设备发送的指定消息。
可选地，所述指定消息包括以下至少一项：
携带挂起配置的无线资源控制RRC释放消息；
RRC重配置消息；
RRC恢复消息。
可选地，所述方法还包括：
当所述终端停止接收所述组播业务数据，不保留所述RLC实体。
可选地，所述终端停止接收所述组播业务数据，包括以下至少一项：
当所述终端使用的第一组播业务配置信息失效，所述终端停止接收所述组播业务数据；
当所述终端的组播业务会话被去激活，所述终端停止接收所述组播业务数据。
可选地，所述终端使用的第一组播业务配置信息失效，包括以下至少一项：
所述终端的驻留小区不支持组播业务；
所述终端的驻留小区不支持所述第一组播业务配置信息；
所述第一组播业务配置信息超过有效期。
可选地，所述终端的驻留小区不支持组播业务，包括：
所述终端从支持非激活态组播业务的区域移动到不支持非激活态组播业务的区域。
可选地，所述终端的驻留小区不支持组播业务，包括：
所述终端从支持组播业务的第一小区移动到不支持组播业务的第二小区。
可选地，所述终端的驻留小区不支持所述第一组播业务配置信息，包括：
所述终端从支持非激活态组播业务配置信息的区域移动到不支持非激活态组播业务配置信息的区域。
可选地，所述驻留小区不支持所述第一组播业务配置信息，包括：
所述终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区。
可选地，所述终端处于基于无线接入网RAN的通知区域RNA内。
可选地，所述RLC实体与组播广播业务无线承载MRB关联，所述MRB用于接收所述组播业务数据。
可选地，所述保留无线链路控制RLC实体，包括：
保留用于点对多点PTM传输的第一RLC实体。
可选地，与MRB关联的所述RLC实体的数目为多个；
所述保留无线链路控制RLC实体，包括：
在与所述MRB关联的多个RLC实体中，至少保留用于PTM传输的第一RLC实体。
可选地，所述不保留RLC实体，包括：
不保留用于PTM传输的第一RLC实体。
可选地，与MRB关联的所述RLC实体的数目为多个；
所述不保留所述RLC实体，包括：
在与所述MRB关联的多个RLC实体中，至少不保留用于PTM传输的第一RLC实体。
可选地，所述保留所述RLC实体，包括以下任一项：
不释放所述RLC实体；
不重建所述RLC实体；
不挂起所述RLC实体。
可选地，不保留所述RLC实体，包括以下任一项：
释放所述RLC实体；
重建所述RLC实体；
挂起所述RLC实体。
根据本公开实施例的第二方面，提供一种组播业务数据的传输方法，所述方法由网络设备执行，包括：
当终端接收组播业务数据，确定所述终端保留无线链路控制RLC实体。
可选地，所述组播业务包括非激活态组播业务。
可选地，所述当终端接收组播业务数据，确定所述终端保留无线链路控制RLC实体，包括：
当所述终端的状态发生改变，且确定所述终端接收所述组播业务数据，确定所述终端保留所述RLC实体。
可选地，所述终端的状态发生改变，包括：
所述终端从第一状态切换到第二状态，所述第一状态与所述第二状态不同；或者
所述终端从所述第一状态切换到所述第二状态失败，并切换回所述第一状态。
可选地，所述终端的状态发生改变，包括：
所述终端从连接态切换到非激活态；
所述终端从非激活态切换到连接态；
所述终端尝试从非激活态切换到其他状态失败，并切换回非激活态。
可选地，在确定所述终端保留无线链路控制RLC实体之前，所述方法还包括：
向所述终端发送指定消息。
可选地，所述指定消息包括以下至少一项：
携带挂起配置的无线资源控制RRC释放消息；
RRC重配置消息；
RRC恢复消息。
可选地，所述方法还包括：
当所述终端停止接收所述组播业务数据，确定所述终端不保留所述RLC实体。
可选地，所述终端停止接收所述组播业务数据，包括以下至少一项：
当所述终端使用的第一组播业务配置信息失效，所述终端停止接收所述组播业务数据；
当所述终端的组播业务会话被去激活，所述终端停止接收所述组播业务数据。
可选地，所述终端使用的第一组播业务配置信息失效，包括以下至少一项：
所述终端的驻留小区不支持组播业务；
所述终端的驻留小区不支持所述第一组播业务配置信息；
所述第一组播业务配置信息超过有效期。
可选地，所述终端的驻留小区不支持组播业务，包括：
所述终端从支持非激活态组播业务的区域移动到不支持非激活态组播业务的区域，确定所述终端的驻留小区不支持组播业务。
可选地，所述终端的驻留小区不支持组播业务，包括：
所述终端从支持组播业务的第一小区移动到不支持组播业务的第二小区。
可选地，所述终端的驻留小区不支持所述第一组播业务配置信息，包括：
所述终端从支持非激活态组播业务的区域移动到不支持非激活态组播业务配置信息的区域。
可选地，所述驻留小区不支持所述第一组播业务配置信息，包括：
所述终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区。
可选地，所述终端处于基于无线接入网RAN的通知区域RNA内。
可选地，所述RLC实体与组播广播业务无线承载MRB关联，所述MRB用于接收所述组播业务数据。
可选地，所述确定所述终端保留无线链路控制RLC实体，包括：
确定所述终端保留用于点对多点PTM传输的第一RLC实体。
可选地，与MRB关联的所述RLC实体的数目为多个；
所述确定所述终端保留无线链路控制RLC实体，包括：
在与所述MRB关联的多个RLC实体中，确定所述终端至少保留用于PTM传输的第一RLC实体。
可选地，所述确定所述终端不保留所述RLC实体，包括：
确定所述终端不保留用于PTM传输的第一RLC实体。
可选地，与MRB关联的所述RLC实体的数目为多个；
所述确定所述终端不保留所述RLC实体，包括：
在与所述MRB关联的多个RLC实体中，确定所述终端至少不保留用于PTM传输的第一RLC实体。
可选地，所述确定所述终端保留所述RLC实体，包括以下任一项：
确定所述终端不释放所述RLC实体；
确定所述终端不重建所述RLC实体；
确定所述终端不挂起所述RLC实体。
可选地，所述确定所述终端不保留所述RLC实体，包括以下任一项：
确定所述终端释放所述RLC实体；
确定所述终端重建所述RLC实体；
确定所述终端挂起所述RLC实体。
根据本公开实施例的第三方面，提供一种组播业务数据的传输装置，所述装置应用于终端，包括：
执行模块，被配置为当确定接收组播业务数据，保留无线链路控制RLC实体。
根据本公开实施例的第四方面，提供一种组播业务数据的传输装置，所述装置应用于网络设备，包括：
确定模块，被配置为当终端接收组播业务数据，确定所述终端保留无线链路控制RLC实体。
根据本公开实施例的第五方面，提供一种计算机可读存储介质，所述存储介质存储有计算机程序，所述计算机程序用于执行上述终端侧任一项所述的组播业务数据的传输方法。
根据本公开实施例的第六方面，提供一种计算机可读存储介质，所述存储介质存储有计算机程序，所述计算机程序用于执行上述网络设备侧任一项所述的组播业务数据的传输方法。
根据本公开实施例的第七方面，提供一种组播业务数据的传输装置，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为用于执行上述终端侧任一项所述的组播业务数据的传输方法。
根据本公开实施例的第八方面，提供一种组播业务数据的传输装置，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为用于执行上述网络设备侧任一项所述的组播业务数据的传输方法。
本公开的实施例提供的技术方案可以包括以下有益效果：
在本公开实施例中，终端在接收组播业务数据时，可以保留RLC实体，从而避免因RLC重建导致的组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，可用性高。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明的实施例，并与说明书一起用于解释本发明的原理。
图1是根据一示例性实施例示出的一种组播业务数据的传输的系统架构图。
图2是根据一示例性实施例示出的一种组播业务数据的传输方法流程示意图。
图3是根据一示例性实施例示出的另一种组播业务数据的传输方法流程示意图。
图4是根据一示例性实施例示出的另一种组播业务数据的传输方法流程示意图。
图5是根据一示例性实施例示出的另一种组播业务数据的传输方法流程示意图。
图6是根据一示例性实施例示出的另一种组播业务数据的传输方法流程示意图。
图7是根据一示例性实施例示出的另一种组播业务数据的传输方法流程示意图。
图8是根据一示例性实施例示出的一种组播业务数据的传输装置框图。
图9是根据一示例性实施例示出的另一种组播业务数据的传输装置框图。
图10是本公开根据一示例性实施例示出的一种组播业务数据的传输装置的一结构示意图。
图11是本公开根据一示例性实施例示出的另一种组播业务数据的传输装置的一结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明的一些方面相一致的装置和方法的例子。
在本公开使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开。在本公开和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含至少一个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
在介绍本公开提供的方案之前，先介绍一下本申请涉及到的名词。
在第五代移动通信技术(5th Generation Mobile Communication Technology，5G)新空口(New Radio，NR)系统中，组播广播业务(Multicast Broadcast Service，MBS)可以通过以下MBS业务标识进行标记：
临时移动组标识(Temporary Mobile Group Identity，TMGI)；
MBS会话标识(MBS Session ID)；
MBS业务流标识(MBS QoS flow ID)。
其中，MBS业务包括：
1、组播业务
终端在RRC连接态时接收到组播业务的接收配置信息后，才能接收组播业务的数据。网络设备可以通过终端专有信令将组播业务的接收配置信息发送给终端。
2、广播业务
终端可以在空闲态(IDLE)或非激活态(INACTIVE)或连接态(CONNECTED)接收广播业务的接收配置信息，并接收广播业务的数据。网络设备可以通过系统信息，例如系统信息块(System Information Block，SIB)和MBS控制信道信息将广播业务的接收配置信息发送给终端。 其中，MBS控制信道信息例如为广播业务控制信道(MBS Control Channel，MCCH)。
可以看出，对于组播业务而言，终端需要处于连接态执行组播业务数据的接收。
为了对终端处于连接态执行组播业务数据的接收机制进行完善，在版本18(Release 18，R18)中研究支持非激活态组播业务接收，当终端进入非激活态时，也能够继续执行组播业务数据接收。但是，当终端接收到携带有挂起配置的RRC释放(RRCRelease)消息，从连接态(也称成为激活态)进入到非激活态(也称为去激活态)时，会执行无线链路控制(Radio Link Control，RLC)重建，此时终端会丢弃所有RLC数据包，停止并重置所有定时器并将所有RLC状态变量初始化。对于支持非激活态组播业务接收的终端来说，当从连接态被释放到非激活态后，如果执行上述操作，可能会导致组播业务数据包丢失或业务接收中断。
为了解决上述技术问题，本公开提供了以下组播业务数据的传输方法及装置、存储介质。如图1所示，为本公开方案所适用的一种网络架构图的示意图。本公开中的网络可以是4G网络、5G网络、6G网络或者未来的通信网络等，本公开对此不作限定，该网络架构中包括：
终端101(图1中包括101-1、101-2、101-3……)，所述终端可以是智能手机、台式机、笔记本电脑，个人助手(ipad)等，本公开对此不作限定。
网络设备102，包括但不限于基站、接入网设备等，其中，基站可以是4G基站、5G基站或未来的6G基站，接入网设备可以是4G接入网设备、5G接入网设备或未来的6G接入网设备等，本公开对此不作限定。可选的，网络设备102还可以包括核心网设备等。
在一些实施例中，在终端101接收组播业务数据的情况下，终端101可以保留RLC实体。
在另一些实施例中，网络设备102确定终端101接收组播业务数据时，可以确定终端101保留了RLC实体。
相应地，网络设备102可以继续通过终端101所保留的RLC实体，向终端101继续发送组播业务数据，终端101可以通过保留的RLC实体执行组播业务数据的接收。网络设备102无需与终端101进行RLC重建操作，从而可以有效避免组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，可用性高。
下面先从终端侧介绍本公开提供的组播业务数据的传输方法。
本公开实施例提供了一种组播业务数据的传输方法，参照图2所示，图2是根据一实施例示出的一种组播业务数据的传输方法流程图，可以由终端执行，该方法可以包括以下步骤：
在步骤201中，当确定接收组播业务数据，保留无线链路控制RLC实体。
在一个可能的实现方式中，终端正在接收组播业务数据的情况下，保留RLC实体。
在一个示例中，终端已经接收了组播业务数据，且未终止接收组播业务数据的情况下，确定正在接收组播业务数据，此时终端保留RLC实体。
在另一个示例中，终端处于接收组播业务数据的间隙的情况下，确定正在接收组播业务数据，此时终端保留RLC实体。
在另一个可能的实现方式中，终端即将接收组播业务数据的情况下，保留RLC实体。
在一个示例中，终端处于连接态、空闲态或非激活态，且确定接收组播业务数据的情况下，保留RLC实体。
在一个可能的实现方式中，终端可以基于MBS业务标识，例如TMGI、MBS Session ID、MBS QoS flow ID中的至少一项，确定正在接收或即将接收组播业务数据，进而保留RLC实体。
或者，终端可以基于网络设备发送的指示信息，确定正在接收或即将接收组播业务数据，进而保留RLC实体。该指示信息用于指示网络设备上存在待发送的组播业务数据包。
在一个可能的实现方式中，本公开中，组播业务包括但不限于非激活态组播业务。在本公开实施例中，非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。
在另一个可能的实现方式中，组播业务可以包括但不限于非激活态组播业务、连接态组播业务。在本公开实施例中，非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在激活态时接收组播业务数据。
在一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且正在接收组播业务数据的情况下，保留RLC实体。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。
在另一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且即将接收组播业务数据的情况下，保留RLC实体。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终 端实际业务需要，即将从网络设备处接收组播业务数据。
在一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且正在接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务的情况下，保留RLC实体。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。在另一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且即将接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务的情况下，保留RLC实体。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
在一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且正在接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务，终端确定自身状态发生改变的情况下，保留RLC实体。
在一个示例中，终端从第一状态切换到第二状态，其中，所述第一状态与所述第二状态不同的情况下，终端确定自身状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，所述终端从连接态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端从非激活态切换到连接态，确定所述终端的状态发生改变。
示例性地，所述终端从空闲态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端的状态从非激活态切换到空闲态，确定所述终端的状态发生改变。
在另一个示例中，所述终端尝试从第一状态切换到第二状态失败，并切换回第一状态，确定所述终端的状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，终端尝试从非激活态切换到其他状态失败，并切换回非激活态，确定所述终端的状态发生改变。
示例性地，终端尝试从非激活态切换到连接态失败，并切换回非激活态，可以确定终端的状态发生改变。
示例性地，终端尝试从非激活态切换到空闲态失败，并切换回非激活态，可以确定终端的状态发生改变。
在另一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且即将接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务，终端确定自身状态发生改变的情况下，保留RLC实体。
在一个示例中，终端从第一状态切换到第二状态，其中，所述第一状态与所述第二状态不同的情况下，终端确定自身状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，所述终端的状态从连接态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端的状态从非激活态切换到连接态，确定所述终端的状态发生改变。
示例性地，所述终端的状态从空闲态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端的状态从非激活态切换到空闲态，确定所述终端的状态发生改变。
在另一个示例中，所述终端的状态尝试从第一状态切换到第二状态失败，并切换回第一状态，确定终端状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，终端从非激活态切换到其他状态失败，并切换回非激活态，确定所述终端的状态发生改变。
示例性地，终端尝试从非激活态切换到连接态失败，并切换回非激活态，可以确定终端的状态发生改变。
示例性地，终端尝试从非激活态切换到空闲态失败，并切换回非激活态，可以确定终端的状态发生改变。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
在另一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且正在接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务，终端接收到网络设备发送的指定消息的情况下，保留RLC实体。
在本公开实施例中，网络设备可以包括但不限于基站、接入网设备等，其中，基站可以是4G基站、5G基站或未来的6G基站，接入网设备可以是4G接入网设备、5G接入网设备或未来的6G接入网设备等。可选的，网络设备102还可以包括核心网设备等。
在一个示例中，指定消息可以是携带挂起配置的无线资源控制RRC释放消息。其中，挂起配置用于配置终端挂起与网络设备的RRC连接。
在另一个示例中，指定消息可以是RRC重配置消息。
在另一个示例中，指定消息可以是RRC恢复消息。
在另一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且即将接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务，终端接收到网络设备发送的指定消息的情况下，保留RLC实体。
在本公开实施例中，网络设备可以包括但不限于基站、接入网设备等，其中，基站可以是4G基站、5G基站或未来的6G基站，接入网设备可以是4G接入网设备、5G接入网设备或未来的6G接入网设备等。可选的，网络设备102还可以包括核心网设备等。
在一个示例中，指定消息可以是携带挂起配置的无线资源控制RRC释放消息。其中，挂起配置用于配置终端挂起与网络设备的RRC连接。
在另一个示例中，指定消息可以是RRC重配置消息。
在另一个示例中，指定消息可以是RRC恢复消息。
在一个可能的实现方式中，RLC实体与组播广播业务无线承载(Multicast Broadcast Service Radio Bear，MRB)关联，所述MRB用于接收所述组播业务数据。
在一个示例中，一个MRB可以关联一个或多个RLC实体。在一个实施例中，终端在保留RLC实体时，可以保留用于点对多点(Point to Multipoint，PTM)传输的第一RLC实体。
在另一个可能的实现方式中，RLC实体与MRB关联，所述MRB用于接收所述组播业务数据，与MRB关联的所述RLC实体的数目为多个。在一个实施例中，终端在保留RLC实体时，在与MRB关联的多个RLC实体中，至少可以保留用于PTM传输的第一RLC实体。
在一个示例中，在与MRB关联的多个RLC实体中，终端可以保留用于PTM传输的第一RLC实体，不保留用于点对点(Point to Point，PTP)传输的第二RLC实体。例如：终端释放用于PTP传输的第二RLC实体。或者，重建用于PTP传输的第二RLC实体。又或者，挂起用于PTP传输的第二RLC实体。
在另一个示例中，在与MRB关联的多个RLC实体中，终端可以保留用于PTM传输的第一RLC实体，以及保留用于PTP传输的第二RLC实体。
在一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且正在接收组播业务数据(或即将接收组播业务数据)，组播业务包括但不限于非激活态组播业务、连接态组播业务，终端确定自身状态发生改变的情况下，保留RLC实体。具体地，RLC实体与组播广播业务无线承载MRB关联，所述MRB用于接收所述组播业务数据。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
如果MRB与一个RLC实体相关联，则保留与该MRB相关联的RLC实体，该RLC实体是用于PTM传输的第一RLC实体。
如果MRB与多个RLC实体相关联，则保留用于PTM传输的第一RLC实体，并释放、重建或挂起用于PTP传输的第二RLC实体。
或者，如果MRB与多个RLC实体相关联，则保留用于PTM传输的第一RLC实体，同时保留用于PTP传输的第二RLC实体。
在一个示例中，终端从第一状态切换到第二状态，其中，所述第一状态与所述第二状态不同的情况下，终端确定自身状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，所述终端的状态从连接态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端的状态从非激活态切换到连接态，确定所述终端的状态发生改变。
示例性地，所述终端的状态从空闲态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端的状态从非激活态切换到空闲态，确定所述终端的状态发生改变。
在另一个示例中，所述终端的状态尝试从第一状态切换到第二状态失败，并切换回第一状态，终端确定自身状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，终端从非激活态切换到其他状态失败，并切换回非激活态，确定所述终端的状态发生改变。
示例性地，终端尝试从非激活态切换到连接态失败，并切换回非激活态，可以确定终端的状态发生改变。
示例性地，终端尝试从非激活态切换到空闲态失败，并切换回非激活态，可以确定终端的状态发生改变。
在另一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且正在接收组播业务数据(或即将接收组播业务数据)，组播业务包括但不限于非激活态组播业务、连接态组播业务，终端接收到网络设备发送的指定消息的情况下，保留RLC实体。具体地，RLC实体与组播广播业务无线承载MRB关联，所述MRB用于接收所述组播业务数据。
如果MRB与一个RLC实体相关联，则保留与该MRB相关联的RLC实体，该RLC实体是用于PTM传输的第一RLC实体。
如果MRB与多个RLC实体相关联，则保留用于PTM传输的第一RLC实体，并释放、重建或挂起用于PTP传输的第二RLC实体。
或者，如果MRB与多个RLC实体相关联，则保留用于PTM传输的第一RLC实体，同时保留用于PTP传输的第二RLC实体。
在本公开实施例中，网络设备可以包括但不限于基站、接入网设备等，其中，基站可以是4G基站、5G基站或未来的6G基站，接入网设备可以是4G接入网设备、5G接入网设备或未来的6G接入网设备等。可选的，网络设备102还可以包括核心网设备等。
在一个示例中，指定消息可以是携带挂起配置的无线资源控制RRC释放消息。其中，挂起配置用于配置终端挂起与网络设备的RRC连接。
在另一个示例中，指定消息可以是RRC重配置消息。
在另一个示例中，指定消息可以是RRC恢复消息。
以上仅为示例性说明，实际应用中，终端在接收组播业务数据的情况下，保留RLC实体的方案均应属于本公开的保护范围。
在一个可能的实现方式中，保留所述RLC实体，包括以下任一项：不释放所述RLC实体；不重建所述RLC实体；不挂起所述RLC实体。
上述实施例中，终端在接收组播业务数据时，可以保留RLC实体，从而避免因RLC重建导致的组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，可用性高。
在一些可选实施例中，RLC实体包括但不限于与MRB关联的RLC实体，且该MRB用于接收组播业务数据。
在一个可能的实现方式中，MRB可以只关联一个RLC实体。该RLC实体是用于PTM传输的第一RLC实体。
相应地，终端确定接收组播业务数据的情况下，可以保留与MRB相关联、且用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。
其中，终端正在接收组播业务数据或即将接收组播业务数据时，可以保留与MRB相关联、且用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。即不释放、不重建或不 挂起与MRB相关联、且用于PTM传输的第一RLC实体。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。
非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
在另一个可能的实现方式中，MRB可以关联多个RLC实体，且该MRB用于接收组播业务数据。具体地，多个RLC实体中包括至少一个用于PTM传输的第一RLC实体，还可以包括至少一个用于PTP传输的第二RLC实体。
其中，终端正在接收组播业务数据或即将接收组播业务数据时，可以保留与MRB相关联的、用于PTM传输的第一RLC实体，即不释放、不重建或不挂起与MRB相关联、且用于PTM传输的第一RLC实体。另外，终端可以释放、重建或者挂起用于PTP传输的第二RLC实体。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。
非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
在另一个可能的实现方式中，MRB可以关联多个RLC实体，且该MRB用于接收组播业务数据。具体地，多个RLC实体中包括至少一个用于PTM传输的第一RLC实体，还可以包括至少一个用于PTP传输的第二RLC实体。
其中，终端正在接收组播业务数据或即将接收组播业务数据时，可以保留与MRB相关联的、用于PTM传输的第一RLC实体。另外，终端还可以保留用于PTP传输的第二RLC实体。即不释放、不重建或不挂起与MRB相关联、用于PTM传输的第一RLC实体，且不释放、不重建或不挂起与MRB相关联、用于PTP传输的第二RLC实体。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。
非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
上述实施例中，终端在接收组播业务数据时，可以保留RLC实体，具体地，在MRB关联多个RLC实体的情况下，可以只保留多个RLC实体中用于PTM传输的第一RLC实体，释放、重建或者挂起用于PTP传输的第二RLC实体。或者，终端还可以保留多个RLC实体中用于PTM传输的第一RLC实体，以及保留多个RLC实体中用于PTP传输的第二RLC实体。从而避免因RLC重建导致的组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，可用性高。
在一些可选实施例中，终端确定所述终端的状态发生改变，且确定接收所述组播业务数据的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起RLC实体。
在一个可能的实现方式中，终端从第一状态切换到第二状态，其中，所述第一状态与所述第二状态不同的情况下，终端确定自身状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，终端的状态从连接态切换到非激活态，确定所述终端的状态发生改变。
在本公开实施例中，终端可以在从连接态切换到非激活态，且正在接收所述组播业务数据的 情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
示例性地，终端可以在从连接态切换到非激活态，且即将接收所述组播业务数据的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
示例性地，终端的状态从非激活态切换到连接态，确定所述终端的状态发生改变。
在本公开实施例中，终端可以在从非激活态切换到连接态，且正在接收所述组播业务数据的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
示例性地，终端可以在从非激活态切换到连接态，且即将接收所述组播业务数据的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
以上仅为示例性说明，实际应用中，终端也可以从非激活态切换到空闲态，且正在接收(或即将接收)所述组播业务数据的情况下，保留所述RLC实体。或者，终端从空闲态切换到非激活态，且正在接收(或即将接收)所述组播业务数据的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
在另一个可能的实现方式中，所述终端尝试从第一状态切换到第二状态失败，并切换回第一状态，确定所述终端的状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，终端可以在尝试从非激活态切换到连接态失败，并切换回非激活态，且正在接收所述组播业务数据的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
示例性地，终端可以在尝试从非激活态切换到连接态失败，并切换回非激活态，且即将接收所述组播业务数据的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
示例性地，终端可以在尝试从非激活态切换到空闲态失败，并切换回非激活态，且正在接收所述组播业务数据的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
示例性地，终端可以在尝试从非激活态切换到空闲态失败，并切换回非激活态，且即将接收所述组播业务数据的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
上述实施例中，在终端状态发生改变，且终端接收组播业务数据的情况下，终端可以保留RLC实体，从而避免因RLC重建导致的组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，可用性高。
在一些可选实施例中，终端接收到网络设备发送的指定消息，且确定接收所述组播业务数据的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
在本公开实施例中，网络设备可以包括但不限于基站、接入网设备等，其中，基站可以是4G基站、5G基站或未来的6G基站，接入网设备可以是4G接入网设备、5G接入网设备或未来的6G接入网设备等。可选的，网络设备102还可以包括核心网设备等。
在一个可能的实现方式中，指定消息可以是携带挂起配置的无线资源控制RRC释放消息。其中，挂起配置用于配置终端挂起与网络设备的RRC连接。
其中，终端可以在接收到网络设备发送的携带挂起配置的无线资源控制RRC释放消息，且正在接收组播业务的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
其中，终端可以在接收到网络设备发送的携带挂起配置的无线资源控制RRC释放消息，且即将接收组播业务的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
在另一个示例中，指定消息可以是RRC重配置消息。
其中，终端可以在接收到网络设备发送的RRC重配置消息，且正在接收组播业务的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
其中，终端可以在接收到网络设备发送的RRC重配置消息，且即将接收组播业务的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
在另一个示例中，指定消息可以是RRC恢复消息。
其中，终端可以在接收到网络设备发送的RRC恢复消息，且正在接收组播业务的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
其中，终端可以在接收到网络设备发送的RRC恢复消息，且即将接收组播业务的情况下，保留所述RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体。
以上仅为示例性说明，实际应用中，终端还可以当接收到网络设备发送的其他指定消息，且确定接收组播业务数据的情况下，保留RLC实体，包括但不限于不释放、不重建或不挂起所述RLC实体，本公开对此不作限定。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
上述实施例中，在终端接收到网络设备下发的指定消息，且终端接收组播业务数据的情况下，终端可以保留RLC实体，从而避免因RLC重建导致的组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，可用性高。
在一些可选实施例中，参照图3所示，图3是根据一实施例示出的一种组播业务数据的传输方法流程图，可以由终端执行，终端可以是智能手机、台式机、笔记本电脑，个人助手等，本公开对此不作限定，该方法可以包括以下步骤：
在步骤301中，当终端停止接收组播业务数据，不保留RLC实体。
在一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且停止接收组播业务数据的情况下，可以不保留RLC实体。
在一个可能的实现方式中，本公开中，组播业务包括但不限于非激活态组播业务。在本公开实施例中，非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。
在另一个可能的实现方式中，组播业务可以包括但不限于非激活态组播业务、连接态组播业务。在本公开实施例中，非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且确定所述终端使用的第一组播业务配置信息失效的情况下，确定终端停止接收组播业务数据，此时可以不保留RLC实体。
在一个示例中，在所述终端的驻留小区不支持组播业务的情况下，可以确定所述终端使用的第一组播业务配置信息失效。
其中，终端处于连接态(也称为激活态)、空闲态或非激活态，且由于终端移动，导致终端当前驻留小区不支持组播业务的情况下，确定终端停止接收所述组播业务数据，相应地，终端可以不保留RLC实体。
可选地，所述终端从支持非激活态组播业务的区域移动到不支持非激活态组播业务的区域，则可以确定所述终端的驻留小区不支持组播业务。
其中，终端处于连接态(也称为激活态)、空闲态或非激活态，且由于终端移动，导致终端移动到不支持非激活态组播业务的区域的情况下，可以确定所述终端的驻留小区不支持组播业务，进一步地，可以确定所述终端使用的第一组播业务配置信息失效，此时确定终端停止接收所述组播业务数据，可以不保留RLC实体。
可选地，终端从支持组播业务的第一小区移动到不支持组播业务的第二小区，确定所述驻留小区不支持所述组播业务。
其中，终端处于连接态(也称为激活态)、空闲态或非激活态，且由于终端移动，导致终端从支持组播业务的第一小区移动到不支持组播业务的第二小区的情况下，可以确定所述终端的驻留小区不支持组播业务，进一步地，可以确定所述终端使用的第一组播业务配置信息失效，此时确定终端停止接收所述组播业务数据，可以不保留RLC实体。
在另一个示例中，在所述终端的驻留小区不支持所述第一组播业务配置信息的情况下，确定所述第一组播业务配置信息失效。
可选地，终端移动到不支持非激活态组播业务配置信息的区域，确定所述驻留小区不支持所述第一组播业务配置信息。
其中，终端处于连接态(也称为激活态)、空闲态或非激活态，且由于终端移动，导致终端移动到不支持非激活态组播业务配置信息的区域，确定所述驻留小区不支持所述第一组播业务配置信息，进一步地，确定所述第一组播业务配置信息失效。此时，确定终端停止接收所述组播业务数据，不保留所述RLC实体。
可选地，终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，确定所述驻留小区不支持所述第一组播业务配置信息。
其中，终端处于连接态(也称为激活态)、空闲态或非激活态，且由于终端移动，导致终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，确定所述驻留小区不支持所述第一组播业务配置信息。进一步地，确定所述第一组播业务配置信息失效。此时，确定终端停止接收所述组播业务数据，不保留所述RLC实体。
在另一个示例中，在所述第一组播业务配置信息超过有效期的情况下，确定所述第一组播业务配置信息失效。
可选地，终端处于连接态(也称为激活态)、空闲态或非激活态，第一组播业务配置信息对应的定时器到期，则终端可以确定所述第一组播业务配置信息超过有效期。进一步地，确定所述第一组播业务配置信息失效。此时，确定终端停止接收所述组播业务数据，不保留所述RLC实体。
在另一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且确定组播业务会话被去激活的情况下，确定所述终端停止接收所述组播业务数据，此时可以不保留RLC实体。
在另一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，所述终端停止接收所述组播业务数据，且终端仍处于基于无线接入网RAN的通知区域(RAN-based Notification Area，RNA)内的情况下，可以不保留RLC实体。
在一个示例中，终端处于连接态(也称为激活态)、空闲态或非激活态，所述终端使用的第一组播业务配置信息失效，且终端仍处于RNA内的情况下，可以释放RLC实体。
例如，终端处于连接态(也称为激活态)、空闲态或非激活态，终端的驻留小区不支持组播业务，且终端仍处于RNA内的情况下，可以释放RLC实体。
其中，终端移动到不支持非激活态组播业务的区域，或者终端从支持组播业务的第一小区移动到不支持组播业务的第二小区，可以确定所述驻留小区不支持所述组播业务。
再例如，终端处于连接态(也称为激活态)、空闲态或非激活态，终端的驻留小区不支持所述第一组播业务配置信息，且终端仍处于RNA内的情况下，可以释放RLC实体。
其中，所述终端移动到不支持非激活态组播业务配置信息的区域，或者所述终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，可以确定所述驻留小区不支持所述第一组播业务配置信息。
在另一个示例中，终端处于连接态(也称为激活态)、空闲态或非激活态，超过所述第一组播业务配置信息的有效期，且终端仍处于RNA内的情况下，可以释放RLC实体。
在另一个示例中，终端处于连接态(也称为激活态)、空闲态或非激活态，组播业务会话被去激活，且终端仍处于RNA内的情况下，可以释放RLC实体。
以上仅为示例性说明，实际应用中，上述情况可以组合实施，或单独实施，本公开对此不作限定。
例如，所述终端使用的第一组播业务配置信息失效，且组播业务会话被去激活，终端可以释放RLC实体。
再例如，终端的驻留小区不支持组播业务，且驻留小区不支持所述第一组播业务配置信息，且超过所述第一组播业务配置信息的有效期，终端可以释放RLC实体。
再例如，所述终端移动到不支持非激活态组播业务的区域，终端仍处于基于无线接入网RAN的通知区域RNA内，且超过所述第一组播业务配置信息的有效期，终端可以释放RLC实体。
在一个可能的实现方式中，RLC实体与MRB关联，所述MRB用于接收所述组播业务数据。
在一个示例中，终端在释放RLC实体的情况下，可以释放用于PTM传输的第一RLC实体。
在另一个示例中，终端在释放RLC实体的情况下，可以重建用于PTM传输的第一RLC实体。
在另一个示例中，终端在释放RLC实体的情况下，可以挂起用于PTM传输的第一RLC实体。
在另一个可能的实现方式中，RLC实体与MRB关联，所述MRB用于接收所述组播业务数据，与MRB关联的所述RLC实体的数目为多个。
相应地，终端在释放RLC实体的情况下，在与MRB关联的多个RLC实体中，至少可以释放 用于PTM传输的第一RLC实体。
在一个示例中，终端可以释放多个RLC实体中用于PTM传输的第一RLC实体，保留用于PTP传输的第二RLC实体。
在另一个示例中，终端可以重建多个RLC实体中用于PTM传输的第一RLC实体，保留用于PTP传输的第二RLC实体。
在另一个示例中，终端可以挂起多个RLC实体中用于PTM传输的第一RLC实体，保留用于PTP传输的第二RLC实体。
在另一个示例中，终端可以释放用于PTM传输的第一RLC实体，以及释放、保留或挂起用于PTP传输的第二RLC实体。
在另一个示例中，终端可以重建多个RLC实体中用于PTM传输的第一RLC实体，以及释放、保留或挂起用于PTP传输的第二RLC实体。
在另一个示例中，终端可以挂起多个RLC实体中用于PTM传输的第一RLC实体，以及释放、保留或挂起用于PTP传输的第二RLC实体。
在一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且停止接收组播业务的情况下，释放RLC实体。具体地，RLC实体与组播广播业务无线承载MRB关联，所述MRB用于接收所述组播业务数据。
如果MRB与一个RLC实体相关联，则释放、重建或挂起与该MRB相关联的RLC实体，该RLC实体是用于PTM传输的第一RLC实体。
如果MRB与多个RLC实体相关联，则释放、重建或挂起用于PTM传输的第一RLC实体，并保留用于PTP传输的第二RLC实体。
或者，如果MRB与多个RLC实体相关联，则释放、重建或挂起用于PTM传输的第一RLC实体，同时释放、重建或挂起用于PTP传输的第二RLC实体。
以上仅为示例性说明，实际应用中，终端在停止组播业务数据的情况下，释放、挂起或重建RLC实体的方案均应属于本公开的保护范围。
上述实施例中，终端在停止组播业务数据时，可以释放、挂起或重建第一RLC实体，从而避免在停止接收组播业务数据的情况下，仍保留第一RLC实体所造成的资源浪费，且可以在终端接收组播业务数据的情况下，建立新的RLC实体，提高了组播业务数据传输的可靠性，可用性高。
在一些可选实施例中，终端使用的第一组播业务配置信息失效的情况下，可以确定终端停止接收所述组播业务数据，此时终端可以不保留RLC实体，包括但不限于释放、重建或挂起RLC实体。
或者，终端的组播业务会话被去激活的情况下，可以确定终端停止接收所述组播业务数据，此时终端可以不保留RLC实体，包括但不限于释放、重建或挂起RLC实体。
在一些可选实施例中，在终端的驻留小区不支持组播业务的情况下，可以确定所述第一组播业务配置信息失效。此时，终端可以确定停止接收所述组播业务数据，不保留RLC实体，包括但不限于释放、重建或挂起RLC实体。
示例性地，如果所述终端移动到不支持非激活态组播业务的区域，可以确定终端的驻留小区不支持组播业务。
在本公开实施例中，如果终端从支持非激活态组播业务的区域移动到不支持非激活态组播业务的区域，则终端确定驻留小区不支持组播业务，进而确定终端使用的第一组播业务配置信息失效，此时终端可以确定停止接收所述组播业务数据，不保留RLC实体，包括但不限于释放、重建或挂起RLC实体。
示例性地，如果所述终端从支持组播业务的第一小区移动到不支持组播业务的第二小区，可以确定终端的驻留小区不支持组播业务。
在本公开实施例中，如果终端从支持组播业务的第一小区移动到不支持组播业务的第二小区，则终端确定驻留小区不支持组播业务，进而确定终端使用的第一组播业务配置信息失效，此时终端可以确定停止接收所述组播业务数据，不保留RLC实体，具体地，可以释放、重建或挂起RLC实体。
或者，在终端的驻留小区不支持所述第一组播业务配置信息的情况下，可以确定所述第一组播业务配置信息失效。此时，终端可以确定停止接收所述组播业务数据，不保留RLC实体。
示例性地，终端从支持非激活态组播业务配置信息的区域移动到不支持非激活态组播业务配置信息的区域，可以确定所述终端的驻留小区不支持所述第一组播业务配置信息。
在本公开实施例中，如果终端移动到不支持非激活态组播业务配置信息的区域，则终端确定驻留小区不支持终端使用的所述第一组播业务配置信息，进而确定终端使用的第一组播业务配置 信息失效，此时终端可以确定停止接收所述组播业务数据，不保留RLC实体，具体地，可以释放、重建或挂起RLC实体。
示例性地，终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，确定所述驻留小区不支持所述第一组播业务配置信息。
在本公开实施例中，如果终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，则终端确定驻留小区不支持终端使用的所述第一组播业务配置信息，进而确定终端使用的第一组播业务配置信息失效，此时终端可以确定停止接收所述组播业务数据，不保留RLC实体，具体地，可以释放、重建或挂起RLC实体。
或者，在所述第一组播业务配置信息超过有效期的情况下，可以确定所述第一组播业务配置信息失效。此时，终端可以确定停止接收所述组播业务数据，不保留RLC实体。
示例性地，第一组播业务配置信息对应的定时器超时，确定所述第一组播业务配置信息超过有效期。
在本公开实施例中，如果第一组播业务配置信息对应的定时器超时，则终端确定所述第一组播业务配置信息超过有效期，进而确定终端使用的第一组播业务配置信息失效，此时终端可以确定停止接收所述组播业务数据，不保留RLC实体，具体地，可以释放、重建或挂起RLC实体。
在一些可选实施例中，在终端的组播业务会话被去激活的情况下，终端可以确定停止接收所述组播业务数据，不保留RLC实体，具体地，可以释放、重建或挂起RLC实体。
在一些可选实施例中，所述终端使用的第一组播业务配置信息失效，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，终端可以确定停止接收所述组播业务数据，不保留RLC实体，具体地，可以释放、重建或挂起RLC实体。
在一些可选实施例中，所述终端的组播业务会话被去激活，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，终端可以确定停止接收所述组播业务数据，不保留RLC实体，具体地，可以释放、重建或挂起RLC实体。
在一些可选实施例中，RLC实体包括但不限于与MRB关联的RLC实体，且该MRB用于接收组播业务数据。
在一个可能的实现方式中，MRB可以只关联一个RLC实体。该RLC实体是用于PTM传输的第一RLC实体。
相应地，终端在确定停止接收组播业务数据的情况下，可以释放、挂起或重建用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在另一个可能的实现方式中，MRB可以关联多个RLC实体。具体地，多个RLC实体中包括至少一个用于PTM传输的第一RLC实体，还可以包括至少一个用于PTP传输的第二RLC实体。
其中，终端在确定停止接收组播业务数据时，可以释放、挂起或重建用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。另外，终端可以保留多个RLC实体中用于PTP传输的第二RLC实体。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。
非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在另一个可能的实现方式中，MRB可以关联多个RLC实体。具体地，多个RLC实体中包括至少一个用于PTM传输的第一RLC实体，还可以包括至少一个用于PTP传输的第二RLC实体。
其中，终端在确定停止接收组播业务数据时，可以释放、挂起或重建用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。另外，终端还可以释放、挂起或重建用于PTP传输的第二RLC实体。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。
非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
上述实施例中，终端在停止接收组播业务数据时，可以释放、挂起或重建RLC实体，具体地，在MRB关联多个RLC实体的情况下，可以只释放、挂起或重建用于PTM传输的第一RLC实体，保留用于PTP传输的第二RLC实体。或者，终端还可以释放、挂起或重建多个RLC实体中用于 PTM传输的第一RLC实体，以及释放、挂起或重建多个RLC实体中用于PTP传输的第二RLC实体。从而避免在停止接收组播业务数据的情况下，仍保留第一RLC实体所造成的资源浪费，且可以在终端接收组播业务数据的情况下，建立新的RLC实体，提高了组播业务数据传输的可靠性，可用性高。
还需要说明的是，上述步骤201与步骤301可以单独实施，也可以组合实施，在组合实施的情况下，可以先执行步骤201，再执行步骤301，或者先执行步骤301，再执行步骤201，本公开对此不作限定。
下面再从网络设备侧介绍一下本公开提供的组播业务数据的传输方法。
本公开实施例提供了一种组播业务数据的传输方法，参照图4所示，图4是根据一实施例示出的一种组播业务数据的传输方法流程图，可以由网络设备执行，网络设备包括但不限于基站、接入网设备等，其中，基站可以是4G基站、5G基站或未来的6G基站，接入网设备可以是4G接入网设备、5G接入网设备或未来的6G接入网设备等，可选的，网络设备102还可以包括核心网设备等。该方法可以包括以下步骤：
在步骤401中，当终端接收组播业务数据，确定所述终端保留无线链路控制RLC实体。
在本公开实施例中，终端可以是智能手机、台式机、笔记本电脑，个人助手(ipad)等，本公开对此不作限定。
在一个可能的实现方式中，网络设备确定终端正在接收组播业务数据的情况下，确定所述终端保留RLC实体。
在一个示例中，终端已经接收了组播业务数据，且未终止接收组播业务数据的情况下，确定正在接收组播业务数据，此时终端保留RLC实体。
在另一个示例中，终端处于接收组播业务数据的间隙的情况下，确定正在接收组播业务数据，此时终端保留RLC实体。
在另一个可能的实现方式中，网络设备确定终端即将接收组播业务数据的情况下，确定所述终端保留RLC实体。
在一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且确定终端接收组播业务数据的情况下，确定所述终端保留RLC实体。
在一个可能的实现方式中，网络设备在确定有待发送的组播业务数据包的情况下，可以向终端发送指示信息，以便让终端确定接收组播业务数据。
在一个可能的实现方式中，本公开中，组播业务包括但不限于非激活态组播业务。在本公开实施例中，非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。
在另一个可能的实现方式中，组播业务可以包括但不限于非激活态组播业务、连接态组播业务。在本公开实施例中，非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且确定终端正在接收组播业务数据的情况下，确定所述终端保留RLC实体。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。
在另一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且确定终端即将接收组播业务数据的情况下，确定所述终端保留RLC实体。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
在一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且确定终端正在接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务的情况下，确定所述终端保留RLC实体。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。
在另一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且确定所述终端即将接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务的情况下，确定所述终端保留RLC实体。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
在一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且确定所述终端正在接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务，确定终端状态发生改变的情况下，确定所述终端保留RLC实体。
在一个示例中，网络设备确定所述终端从第一状态切换到第二状态，其中，所述第一状态与所述第二状态不同的情况下，终端确定自身状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，所述终端从连接态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端从非激活态切换到连接态，确定所述终端的状态发生改变。
示例性地，所述终端从空闲态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端从非激活态切换到空闲态，确定所述终端的状态发生改变。
在另一个示例中，网络设备确定所述终端尝试从第一状态切换到第二状态失败，并切换回第一状态，确定所述终端的状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，终端尝试从非激活态切换到其他状态失败，并切换回非激活态，确定所述终端的状态发生改变。
示例性地，终端尝试从非激活态切换到连接态失败，并切换回非激活态，可以确定终端的状态发生改变。
示例性地，终端尝试从非激活态切换到空闲态失败，并切换回非激活态，可以确定终端的状态发生改变。
在另一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且确定终端即将接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务，终端状态发生改变的情况下，确定终端保留RLC实体。
在一个示例中，网络设备确定所述终端从第一状态切换到第二状态，其中，所述第一状态与所述第二状态不同的情况下，终端确定自身状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，所述终端从连接态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端从非激活态切换到连接态，确定所述终端的状态发生改变。
示例性地，所述终端从空闲态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端从非激活态切换到空闲态，确定所述终端的状态发生改变。
在另一个示例中，网络设备确定所述终端尝试从第一状态切换到第二状态失败，并切换回第一状态，确定所述终端的状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，终端尝试从非激活态切换到其他状态失败，并切换回非激活态，确定所述终端的状态发生改变。
示例性地，终端尝试从非激活态切换到连接态失败，并切换回非激活态，可以确定终端的状态发生改变。
示例性地，终端尝试从非激活态切换到空闲态失败，并切换回非激活态，可以确定终端的状态发生改变。在另一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且正在接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务，网络设备向终端发送指定消息的情况下，网络设备确定终端保留RLC实体。
在一个示例中，指定消息可以是携带挂起配置的无线资源控制RRC释放消息。其中，挂起配置用于配置终端挂起与网络设备的RRC连接。
在另一个示例中，指定消息可以是RRC重配置消息。
在另一个示例中，指定消息可以是RRC恢复消息。
在另一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激 活态，且确定终端即将接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务，网络设备向终端发送了指定消息的情况下，确定终端保留RLC实体。
在一个示例中，指定消息可以是携带挂起配置的无线资源控制RRC释放消息。其中，挂起配置用于配置终端挂起与网络设备的RRC连接。
在另一个示例中，指定消息可以是RRC重配置消息。
在另一个示例中，指定消息可以是RRC恢复消息。
在一个可能的实现方式中，RLC实体与MRB关联，所述MRB用于接收所述组播业务数据。
在一个示例中，一个MRB可以关联一个或多个RLC实体。
在一个实施例中，网络设备确定终端保留RLC实体的情况下，可以确定终端保留用于PTM传输的第一RLC实体。
在一个实施例中，网络设备确定终端保留RLC实体时，在与MRB关联的多个RLC实体中，可以确定终端至少保留用于PTM传输的第一RLC实体。
在一个示例中，在与MRB关联的多个RLC实体中，终端可以保留用于PTM传输的第一RLC实体，不保留用于点对点(Point to Point，PTP)传输的第二RLC实体。例如：终端释放用于PTP传输的第二RLC实体。或者，重建用于PTP传输的第二RLC实体。又或者，挂起用于PTP传输的第二RLC实体。
在另一个示例中，在与MRB关联的多个RLC实体中，终端可以保留用于PTM传输的第一RLC实体，以及保留用于PTP传输的第二RLC实体。
在一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且正在接收组播业务数据(或即将接收组播业务数据)，组播业务包括但不限于非激活态组播业务、连接态组播业务，确定终端状态发生改变的情况下，确定终端保留RLC实体。具体地，RLC实体与组播广播业务无线承载MRB关联，所述MRB用于接收所述组播业务数据。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
如果MRB与一个RLC实体相关联，则确定终端保留与该MRB相关联的RLC实体，该RLC实体是用于PTM传输的第一RLC实体。
如果MRB与多个RLC实体相关联，则确定终端保留用于PTM传输的第一RLC实体，并释放、重建或挂起用于PTP传输的第二RLC实体。
或者，如果MRB与多个RLC实体相关联，则确定终端保留用于PTM传输的第一RLC实体，同时保留用于PTP传输的第二RLC实体。
在一个示例中，终端从第一状态切换到第二状态，其中，所述第一状态与所述第二状态不同的情况下，确定终端状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，所述终端的状态从连接态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端的状态从非激活态切换到连接态，确定所述终端的状态发生改变。
示例性地，所述终端的状态从空闲态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端的状态从非激活态切换到空闲态，确定所述终端的状态发生改变。
在另一个示例中，所述终端的状态尝试从第一状态切换到第二状态失败，并切换回第一状态，确定终端状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，终端从非激活态切换到其他状态失败，并切换回非激活态，确定所述终端的状态发生改变。
示例性地，终端尝试从非激活态切换到连接态失败，并切换回非激活态，可以确定终端的状态发生改变。
示例性地，终端尝试从非激活态切换到空闲态失败，并切换回非激活态，可以确定终端的状态发生改变。
在另一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且正在接收组播业务数据(或即将接收组播业务数据)，组播业务包括但不限于非激活态组播业务、连接态组播业务，网络设备向终端发送指定消息的情况下，确定终端保留RLC实体。具体地，RLC实体与组播广播业务无线承载MRB关联，所述MRB用于接收所述组播业务数据。
如果MRB与一个RLC实体相关联，则确定终端保留与该MRB相关联的RLC实体，该RLC实体是用于PTM传输的第一RLC实体。
如果MRB与多个RLC实体相关联，则确定终端保留用于PTM传输的第一RLC实体，并释放、重建或挂起用于PTP传输的第二RLC实体。
或者，如果MRB与多个RLC实体相关联，则确定终端保留用于PTM传输的第一RLC实体，同时保留用于PTP传输的第二RLC实体。
在一个示例中，指定消息可以是携带挂起配置的无线资源控制RRC释放消息。其中，挂起配置用于配置终端挂起与网络设备的RRC连接。
在另一个示例中，指定消息可以是RRC重配置消息。
在另一个示例中，指定消息可以是RRC恢复消息。
在一个可能的实现方式中，保留所述RLC实体，包括以下任一项：不释放所述RLC实体；不重建所述RLC实体；不挂起所述RLC实体。
上述实施例中，网络设备在确定终端接收组播业务数据时，确定终端保留RLC实体，从而避免因RLC重建导致的组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，针对终端行为确保网络设备与终端的理解一致，可用性高。
在一些可选实施例中，RLC实体包括但不限于与MRB关联的RLC实体，且该MRB用于接收组播业务数据。
在一个可能的实现方式中，MRB可以只关联一个RLC实体。该RLC实体是用于PTM传输的第一RLC实体。
相应地，网络设备确定终端接收组播业务数据的情况下，可以确定终端保留与MRB相关联、且用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。
其中，网络设备确定终端正在接收组播业务数据或即将接收组播业务数据时，可以确定终端保留与MRB相关联、且用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。即确定终端不释放、不重建或不挂起与MRB相关联、且用于PTM传输的第一RLC实体。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。
非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在另一个可能的实现方式中，MRB可以关联多个RLC实体。具体地，多个RLC实体中包括至少一个用于PTM传输的第一RLC实体，还可以包括至少一个用于PTP传输的第二RLC实体。
其中，网络设备确定终端正在接收组播业务数据或即将接收组播业务数据时，可以确定终端保留与MRB相关联的、用于PTM传输的第一RLC实体，即确定终端不释放、不重建或不挂起与MRB相关联、且用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。另外，确定终端释放、重建或者挂起多个RLC实体中用于PTP传输的第二RLC实体。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。
非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在另一个可能的实现方式中，MRB可以关联多个RLC实体。具体地，多个RLC实体中包括至少一个用于PTM传输的第一RLC实体，还可以包括至少一个用于PTP传输的第二RLC实体。
其中，网络设备确定终端正在接收组播业务数据或即将接收组播业务数据时，可以确定终端保留与MRB相关联的、用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。另外，确定终端保留用于PTP传输的第二RLC实体。即确定终端不释放、不重建或不挂起用于PTM传输的第一RLC实体，且不释放、不重建或不挂起与MRB相关联、用于PTP传输的第二RLC实体。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。
非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在本公开中，正在接收组播业务数据具体可以指终端已经接收了组播业务数据，且未终止接收组播业务数据。或者正在接收组播业务数据具体可以指终端处于接收组播业务数据的接收间隙，本公开对此不作限定。
在本公开中，即将接收组播业务数据可以指终端之前并未接收到任何组播业务数据，根据终端实际业务需要，即将从网络设备处接收组播业务数据。
上述实施例中，网络设备确定终端接收组播业务数据时，可以确定终端保留RLC实体，具体地，在MRB关联多个RLC实体的情况下，可以确定终端只保留多个RLC实体中用于PTM传输的第一RLC实体，释放、重建或者挂起用于PTP传输的第二RLC实体。或者，还可以确定终端保留多个RLC实体中用于PTM传输的第一RLC实体，以及保留多个RLC实体中用于PTP传输的第二RLC实体。从而避免因RLC重建导致的组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，针对终端行为确保网络设备与终端的理解一致，可用性高。
在一些可选实施例中，网络设备确定所述终端的状态发生改变，且确定所述终端接收所述组播业务数据的情况下，确定所述终端保留所述RLC实体，包括但不限于确定所述终端不释放、不重建或不挂起RLC实体。
在一个示例中，网络设备确定所述终端从第一状态切换到第二状态，其中，所述第一状态与所述第二状态不同的情况下，终端确定自身状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，所述终端从连接态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端从非激活态切换到连接态，确定所述终端的状态发生改变。
示例性地，所述终端从空闲态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端从非激活态切换到空闲态，确定所述终端的状态发生改变。
在另一个示例中，网络设备确定所述终端尝试从第一状态切换到第二状态失败，并切换回第一状态，确定所述终端的状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，终端尝试从非激活态切换到其他状态失败，并切换回非激活态，确定所述终端的状态发生改变。
示例性地，终端尝试从非激活态切换到连接态失败，并切换回非激活态，可以确定终端的状态发生改变。
示例性地，终端尝试从非激活态切换到空闲态失败，并切换回非激活态，可以确定终端的状态发生改变。
在另一个可能的实现方式中，终端处于连接态(也称为激活态)、空闲态或非激活态，且确定终端即将接收组播业务数据，组播业务包括但不限于非激活态组播业务、连接态组播业务，终端状态发生改变的情况下，确定终端保留RLC实体。
在一个示例中，网络设备确定所述终端从第一状态切换到第二状态，其中，所述第一状态与所述第二状态不同的情况下，终端确定自身状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，所述终端从连接态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端从非激活态切换到连接态，确定所述终端的状态发生改变。
示例性地，所述终端从空闲态切换到非激活态，确定所述终端的状态发生改变。
示例性地，所述终端从非激活态切换到空闲态，确定所述终端的状态发生改变。
在另一个示例中，网络设备确定所述终端尝试从第一状态切换到第二状态失败，并切换回第一状态，确定所述终端的状态发生改变。
例如，第一状态为连接态，第二状态为非激活态，或者，第一状态为连接态，第二状态为空闲态，或者，第一状态为空闲态，第二状态为连接态，第一状态为空闲态，第二状态为非激活态，或者，第一状态为非激活态，第二状态为连接态，第一状态为非激活态，第二状态为空闲态。
示例性地，终端尝试从非激活态切换到其他状态失败，并切换回非激活态，确定所述终端的状态发生改变。
示例性地，终端尝试从非激活态切换到连接态失败，并切换回非激活态，可以确定终端的状态发生改变。
示例性地，终端尝试从非激活态切换到空闲态失败，并切换回非激活态，可以确定终端的状 态发生改变。上述实施例中，网络设备确定终端状态发生改变，且终端接收组播业务数据的情况下，确定终端保留RLC实体，从而避免因RLC重建导致的组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，针对终端行为确保网络设备与终端的理解一致，可用性高。
在一些可选实施例中，网络设备向终端发送指定消息，且确定终端接收所述组播业务数据的情况下，确定终端保留所述RLC实体，包括但不限于确定所述终端不释放、不重建或不挂起RLC实体。
在一个可能的实现方式中，指定消息可以是携带挂起配置的无线资源控制RRC释放消息。其中，挂起配置用于配置终端挂起与网络设备的RRC连接。
其中，网络设备可以向终端发送携带挂起配置的无线资源控制RRC释放消息，且确定终端正在接收组播业务的情况下，确定终端保留所述RLC实体，包括但不限于确定所述终端不释放、不重建或不挂起RLC实体。
其中，网络设备可以向终端发送携带挂起配置的无线资源控制RRC释放消息，且确定终端即将接收组播业务的情况下，确定终端保留所述RLC实体，包括但不限于确定所述终端不释放、不重建或不挂起RLC实体。
在另一个示例中，指定消息可以是RRC重配置消息。
其中，网络设备可以向终端发送RRC重配置消息，且确定终端正在接收组播业务的情况下，确定终端保留所述RLC实体，包括但不限于确定所述终端不释放、不重建或不挂起RLC实体。
其中，网络设备可以向终端发送RRC重配置消息，且确定终端即将接收组播业务的情况下，确定终端保留所述RLC实体，包括但不限于确定所述终端不释放、不重建或不挂起RLC实体。
在另一个示例中，指定消息可以是RRC恢复消息。
其中，网络设备可以向终端发送RRC恢复消息，且确定终端正在接收组播业务的情况下，确定终端保留所述RLC实体，包括但不限于确定所述终端不释放、不重建或不挂起RLC实体。
其中，网络设备可以向终端发送RRC恢复消息，且确定终端即将接收组播业务的情况下，确定终端保留所述RLC实体，包括但不限于确定所述终端不释放、不重建或不挂起RLC实体。
上述实施例中，网络设备可以向终端下发指定消息，且确定终端接收组播业务数据的情况下，确定终端可以保留RLC实体，从而避免因RLC重建导致的组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，针对终端行为确保网络设备与终端的理解一致，可用性高。
在一些可选实施例中，参照图5所示，图5是根据一实施例示出的一种组播业务数据的传输方法流程图，可以由网络设备执行，网络设备包括但不限于基站、接入网设备等，其中，基站可以是4G基站、5G基站或未来的6G基站，接入网设备可以是4G接入网设备、5G接入网设备或未来的6G接入网设备等，该方法可以包括以下步骤：
在步骤501中，当所述终端停止接收所述组播业务数据，确定所述终端不保留所述RLC实体。
在一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且确定终端停止接收组播业务数据的情况下，可以确定终端不保留RLC实体。
在一个可能的实现方式中，本公开中，组播业务包括但不限于非激活态组播业务。在本公开实施例中，非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。
在另一个可能的实现方式中，组播业务可以包括但不限于非激活态组播业务、连接态组播业务。在本公开实施例中，非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且确定所述终端使用的第一组播业务配置信息失效的情况下，可以确定停止接收所述组播业务数据，此时确定终端不保留RLC实体。
在一个示例中，在所述终端的驻留小区不支持组播业务的情况下，可以确定所述终端使用的第一组播业务配置信息失效。
其中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且由于终端移动，导致终端当前驻留小区不支持组播业务的情况下，确定终端停止接收所述组播业务数据，相应地，确定终端不保留RLC实体。
可选地，确定所述终端移动到不支持非激活态组播业务的区域，则可以确定所述终端的驻留小区不支持组播业务。
其中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且由于终端移动，导致终端移动到不支持非激活态组播业务的区域的情况下，可以确定所述终端的驻留小区不支持 组播业务，进一步地，可以确定所述终端使用的第一组播业务配置信息失效，此时确定终端停止接收所述组播业务数据，可以确定终端不保留RLC实体。
可选地，网络设备确定终端从支持组播业务的第一小区移动到不支持组播业务的第二小区，确定所述驻留小区不支持所述组播业务。
其中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且由于终端移动，导致终端从支持组播业务的第一小区移动到不支持组播业务的第二小区的情况下，可以确定所述终端的驻留小区不支持组播业务，进一步地，可以确定所述终端使用的第一组播业务配置信息失效，此时确定终端停止接收所述组播业务数据，可以确定终端不保留RLC实体。
在另一个示例中，网络设备在所述终端的驻留小区不支持所述第一组播业务配置信息的情况下，确定所述第一组播业务配置信息失效。
可选地，网络设备确定终端移动到不支持非激活态组播业务配置信息的区域，确定所述驻留小区不支持所述第一组播业务配置信息。
其中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且由于终端移动，导致终端移动到不支持非激活态组播业务配置信息的区域，确定所述驻留小区不支持所述第一组播业务配置信息，进一步地，确定所述第一组播业务配置信息失效。此时，确定终端停止接收所述组播业务数据，确定终端不保留所述RLC实体。
可选地，网络设备确定终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，确定所述驻留小区不支持所述第一组播业务配置信息。
其中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且由于终端移动，导致终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，确定所述驻留小区不支持所述第一组播业务配置信息。进一步地，确定所述第一组播业务配置信息失效。此时，确定终端停止接收所述组播业务数据，确定终端不保留所述RLC实体。
在另一个示例中，网络设备在确定超过所述第一组播业务配置信息的有效期的情况下，确定所述第一组播业务配置信息失效。
可选地，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，第一组播业务配置信息对应的定时器到期，则终端可以确定超过所述第一组播业务配置信息的有效期。进一步地，确定所述第一组播业务配置信息失效。此时，确定终端停止接收所述组播业务数据，确定终端不保留所述RLC实体。
在另一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且确定组播业务会话被去激活的情况下，确定所述终端停止接收所述组播业务数据，此时确定终端不保留RLC实体。
在另一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，所述终端停止接收所述组播业务数据，且终端仍处于RNA内的情况下，确定终端不保留RLC实体。
在一个示例中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，所述终端使用的第一组播业务配置信息失效，且终端仍处于RNA内的情况下，可以确定终端不保留RLC实体。
例如，确定终端处于连接态(也称为激活态)、空闲态或非激活态，终端的驻留小区不支持组播业务，且终端仍处于RNA内的情况下，可以确定终端不保留RLC实体。
其中，网络设备确定终端移动到不支持非激活态组播业务的区域，或者终端从支持组播业务的第一小区移动到不支持组播业务的第二小区，可以确定所述驻留小区不支持所述组播业务。
再例如，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，终端的驻留小区不支持所述第一组播业务配置信息，且终端仍处于RNA内的情况下，可以确定终端不保留RLC实体。
其中，网络设备确定所述终端移动到不支持非激活态组播业务配置信息的区域，或者所述终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，可以确定所述驻留小区不支持所述第一组播业务配置信息。
在另一个示例中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，超过所述第一组播业务配置信息的有效期，且终端仍处于RNA内的情况下，可以确定终端不保留RLC实体。
在另一个示例中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，组播 业务会话被去激活，且终端仍处于RNA内的情况下，可以确定终端不保留RLC实体。
在一个可能的实现方式中，RLC实体与MRB关联，所述MRB用于接收所述组播业务数据。
在一个示例中，网络设备确定终端不保留RLC实体的情况下，可以确定终端释放用于PTM传输的第一RLC实体。
在另一个示例中，网络设备确定终端不保留RLC实体的情况下，可以确定终端重建用于PTM传输的第一RLC实体。
在另一个示例中，网络设备确定终端不保留RLC实体的情况下，可以确定终端挂起用于PTM传输的第一RLC实体。
在另一个可能的实现方式中，RLC实体与MRB关联，所述MRB用于接收所述组播业务数据，与MRB关联的所述RLC实体的数目为多个。
相应地，网络设备确定终端不保留RLC实体的情况下，可以确定终端至少不保留用于PTM传输的第一RLC实体。
在一个示例中，网络设备确定终端释放用于PTM传输的第一RLC实体，保留用于PTP传输的第二RLC实体。
在另一个示例中，网络设备确定终端重建用于PTM传输的第一RLC实体，保留用于PTP传输的第二RLC实体。
在另一个示例中，网络设备确定终端挂起用于PTM传输的第一RLC实体，保留用于PTP传输的第二RLC实体。
在另一个示例中，网络设备确定终端释放、重建或挂起用于PTM传输的第一RLC实体，以及释放、重建或挂起用于PTP传输的第二RLC实体。
在一个可能的实现方式中，网络设备确定终端处于连接态(也称为激活态)、空闲态或非激活态，且停止接收组播业务的情况下，确定终端不保留RLC实体。具体地，RLC实体与组播广播业务无线承载MRB关联，所述MRB用于接收所述组播业务数据。
如果MRB与一个RLC实体相关联，则确定终端释放、重建或挂起与该MRB相关联的RLC实体，该RLC实体是用于PTM传输的第一RLC实体。
如果MRB与多个RLC实体相关联，则确定终端释放、重建或挂起用于PTM传输的第一RLC实体，并保留用于PTP传输的第二RLC实体。
或者，如果MRB与多个RLC实体相关联，则确定终端释放、重建或挂起用于PTM传输的第一RLC实体，同时释放、重建或挂起用于PTP传输的第二RLC实体。
上述实施例中，网络设备在确定终端停止组播业务数据时，可以确定终端不保留RLC实体，从而避免在停止接收组播业务数据的情况下，仍保留RLC实体所造成的资源浪费，且可以确保后续RLC实体的重建，提高了组播业务数据传输的可靠性，针对终端行为确保网络设备与终端的理解一致，可用性高。
在一些可选实施例中，网络设备在确定终端使用的第一组播业务配置信息失效的情况下，可以确定终端停止接收所述组播业务数据，此时确定终端不保留RLC实体。
或者，网络设备在确定终端的组播业务会话被去激活的情况下，可以确定终端停止接收所述组播业务数据，此时确定终端不保留RLC实体。
在本公开实施例中，不保留RLC实体包括但不限于释放、重建或挂起RLC实体。
上述实施例中，网络设备可以在确定终端停止接收组播业务数据的情况下，确定终端不保留RLC实体，提高了组播业务数据传输的可靠性，针对终端行为确保网络设备与终端的理解一致，可用性高。
在一些可选实施例中，网络设备可以在确定终端的驻留小区不支持组播业务的情况下，确定所述第一组播业务配置信息失效。此时，可以确定终端停止接收所述组播业务数据，不保留RLC实体。
示例性地，如果所述终端从支持非激活态组播业务的区域移动到不支持非激活态组播业务的区域，可以确定终端的驻留小区不支持组播业务。
在本公开实施例中，如果终端移动到不支持非激活态组播业务的区域，则确定驻留小区不支持组播业务，进而确定终端使用的第一组播业务配置信息失效，此时可以确定终端停止接收所述组播业务数据，不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
示例性地，如果所述终端从支持组播业务的第一小区移动到不支持组播业务的第二小区，可以确定终端的驻留小区不支持组播业务。
在本公开实施例中，如果终端从支持组播业务的第一小区移动到不支持组播业务的第二小区，则确定终端驻留小区不支持组播业务，进而确定终端使用的第一组播业务配置信息失效，此时可 以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
或者，在终端的驻留小区不支持所述第一组播业务配置信息的情况下，可以确定所述第一组播业务配置信息失效。此时，可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体。
示例性地，终端从支持非激活态组播业务配置信息的区域移动到不支持非激活态组播业务配置信息的区域，可以确定所述终端的驻留小区不支持所述第一组播业务配置信息。
在本公开实施例中，如果终端移动到不支持非激活态组播业务配置信息的区域，则终端确定驻留小区不支持终端使用的所述第一组播业务配置信息，进而确定终端使用的第一组播业务配置信息失效，此时可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
示例性地，终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，确定所述驻留小区不支持所述第一组播业务配置信息。
在本公开实施例中，如果终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，则终端确定驻留小区不支持终端使用的所述第一组播业务配置信息，进而确定终端使用的第一组播业务配置信息失效，此时可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
或者，在所述第一组播业务配置信息超过有效期的情况下，可以确定所述第一组播业务配置信息失效。此时，可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体。
示例性地，第一组播业务配置信息对应的定时器超时，确定所述第一组播业务配置信息超过有效期。
在本公开实施例中，如果第一组播业务配置信息对应的定时器超时，则确定所述第一组播业务配置信息超过有效期，进而确定终端使用的第一组播业务配置信息失效，此时可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
在一些可选实施例中，在终端的组播业务会话被去激活的情况下，可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
在一些可选实施例中，所述终端使用的第一组播业务配置信息失效，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
示例性地，如果所述终端移动到不支持非激活态组播业务的区域，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，可以确定终端的驻留小区不支持组播业务。
在本公开实施例中，如果终端移动到不支持非激活态组播业务的区域，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，则终端确定驻留小区不支持组播业务，进而确定终端使用的第一组播业务配置信息失效，此时可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
示例性地，如果所述终端从支持组播业务的第一小区移动到不支持组播业务的第二小区，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，可以确定终端的驻留小区不支持组播业务。
在本公开实施例中，如果终端从支持组播业务的第一小区移动到不支持组播业务的第二小区，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，则终端确定驻留小区不支持组播业务，进而确定终端使用的第一组播业务配置信息失效，此时可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
或者，在终端的驻留小区不支持所述第一组播业务配置信息的情况下，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，可以确定所述第一组播业务配置信息失效。此时，可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体。
示例性地，终端移动到不支持非激活态组播业务配置信息的区域，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，可以确定所述终端的驻留小区不支持所述第一组播业务配置信息。
在本公开实施例中，如果终端移动到不支持非激活态组播业务配置信息的区域，且所述终端 仍处于基于无线接入网RAN的通知区域RNA内的情况下，则终端确定驻留小区不支持终端使用的所述第一组播业务配置信息，进而确定终端使用的第一组播业务配置信息失效，此时可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
示例性地，终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，确定所述驻留小区不支持所述第一组播业务配置信息。
在本公开实施例中，如果终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，则确定驻留小区不支持终端使用的所述第一组播业务配置信息，进而确定终端使用的第一组播业务配置信息失效，此时可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
或者，在所述第一组播业务配置信息超过有效期，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，可以确定所述第一组播业务配置信息失效。此时，可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体。
示例性地，第一组播业务配置信息对应的定时器超时，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，确定所述第一组播业务配置信息超过有效期。
在本公开实施例中，如果第一组播业务配置信息对应的定时器超时，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，则终端确定超过所述第一组播业务配置信息的有效期，进而确定终端使用的第一组播业务配置信息失效，此时可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
在一些可选实施例中，所述终端的组播业务会话被去激活，且所述终端仍处于基于无线接入网RAN的通知区域RNA内的情况下，可以确定终端停止接收所述组播业务数据，确定终端不保留RLC实体，具体地，可以确定终端释放、重建或挂起RLC实体。
上述实施例中，可以在终端使用的第一组播业务配置信息失效，或者组播业务会话被去激活，确定所述终端停止接收所述组播业务数据，相应地，确定终端不保留RLC实体。提高了组播业务数据传输的可靠性，针对终端行为确保网络设备与终端的理解一致，可用性高。
在一些可选实施例中，RLC实体包括但不限于与MRB关联的RLC实体，且该MRB用于接收组播业务数据。
在一个可能的实现方式中，MRB可以只关联一个RLC实体。该RLC实体是用于PTM传输的第一RLC实体。
相应地，在确定终端停止接收组播业务数据的情况下，可以确定终端释放、挂起或重建用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在另一个可能的实现方式中，MRB可以关联多个RLC实体。具体地，多个RLC实体中包括至少一个用于PTM传输的第一RLC实体，还可以包括至少一个用于PTP传输的第二RLC实体。
其中，在确定终端停止接收组播业务数据时，可以确定终端释放、挂起或重建用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。另外，可以确定终端保留多个RLC实体中用于PTP传输的第二RLC实体。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。
非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
在另一个可能的实现方式中，MRB可以关联多个RLC实体。具体地，多个RLC实体中包括至少一个用于PTM传输的第一RLC实体，还可以包括至少一个用于PTP传输的第二RLC实体。
其中，在确定终端停止接收组播业务数据时，可以确定终端释放、挂起或重建用于PTM传输的第一RLC实体。其中，MRB用于接收组播业务数据。另外，还可以确定终端释放、挂起或重建多个RLC实体中用于PTP传输的第二RLC实体。
其中，组播业务包括但不限于非激活态组播业务、连接态组播业务。
非激活态组播业务可以指终端被配置为在非激活态时接收组播业务数据。连接态组播业务可以指终端被配置为在连接态时接收组播业务数据。
上述实施例中，在确定终端停止接收组播业务数据时，可以确定终端释放、挂起或重建RLC 实体，具体地，在MRB关联多个RLC实体的情况下，可以确定终端不保留用于PTM传输的第一RLC实体，保留用于PTP传输的第二RLC实体。或者，还可以确定终端不保留第一RLC实体，以及不保留第二RLC实体。从而避免在停止接收组播业务数据的情况下，仍保留RLC实体所造成的资源浪费，且可以确保后续RLC实体的重建，提高了组播业务数据传输的可靠性，针对终端行为确保网络设备与终端的理解一致，可用性高。
还需要说明的是，上述步骤401与步骤501可以单独实施，也可以组合实施，在组合实施的情况下，可以先执行步骤401，再执行步骤501，或者先执行步骤501，再执行步骤401，本公开对此不作限定。
参照图6所示，图6是根据一实施例示出的一种组播业务数据的传输方法流程图，该方法可以适用于图1所示的网络架构中，包括以下步骤：
在步骤601中，终端当确定接收组播业务数据，保留无线链路控制RLC实体。
具体实现方式与上述步骤201类似，在此不再赘述。
在步骤602中，网络设备当终端接收组播业务数据，确定所述终端保留无线链路控制RLC实体。
具体实现方式与上述步骤401类似，在此不再赘述。
相应地，网络设备可以继续通过保留下来的RLC实体向终端发送组播业务数据，终端接收该组播业务数据即可。
上述实施例中，终端在接收组播业务数据时，可以保留RLC实体，网络设备在确定终端接收组播业务数据时，确定终端可以保留RLC实体，从而避免因RLC重建导致的组播业务数据包丢失或业务接收中断的问题，提高了组播业务数据传输的可靠性，针对终端行为确保网络设备与终端的理解一致，可用性高。
参照图7所示，图7是根据一实施例示出的一种组播业务数据的传输方法流程图，该方法可以适用于图1所示的网络架构中，包括以下步骤：
在步骤701中，终端当确定停止接收组播业务数据，不保留RLC实体。
具体实现方式与上述步骤301类似，在此不再赘述。
在步骤702中，网络设备当确定终端停止接收所述组播业务数据，确定所述终端不保留所述RLC实体。
具体实现方式与上述步骤501类似，在此不再赘述。
相应地，网络设备停止向终端发送组播业务数据，终端停止接收该组播业务数据。
上述实施例中，终端在停止接收组播业务数据时，可以不保留RLC实体，另外，网络设备在确定终端停止接收组播业务数据时，可以确定终端不保留RLC实体。避免在停止接收组播业务数据的情况下，仍保留RLC实体所造成的资源浪费，且可以确保后续RLC实体的重建，提高了组播业务数据传输的可靠性，针对终端行为确保网络设备与终端的理解一致，可用性高。
下面对上述方案进一步举例说明如下。
实施例1，保留RLC实体的方案。
当终端执行组播业务接收时，保留RLC实体，具体的，包括：
终端执行组播业务接收时，不释放、不重建或不挂起RLC实体。
对于执行组播业务接收的终端，当终端从连接态切换到非激活态，或者从非激活态切换到连接态，或者从空闲态切换到非激活态，或者从非激活态切换到空闲态，或者尝试从非激活态切换到连接态(或空闲态)失败，并切换回非激活态，保留RLC实体。具体地，不释放、不重建或不挂起RLC实体。
其中，所述RLC实体包括用于组播业务接收MRB关联的RLC实体。进一步的，对于一个MRB关联多个RLC实体的场景，可以只保留用于PTM传输的RLC实体，不保留用于PTP传输的RLC实体，包括但不限于释放、重建或挂起用于PTP传输的RLC实体。
其中，所述组播业务包括非激活态组播业务，即终端处于非激活态仍能执行业务数据接收的组播业务。
对于执行组播业务接收的终端，当终端接收到网络设备下发的带有挂起配置的RRCRelease消息、RRC重配置消息或RRC恢复消息，保留RLC实体，具体地，不释放、不重建或不挂起RLC实体。
其中，所述RLC实体包括用于组播业务接收MRB关联的RLC实体。进一步的，对于一个MRB关联多个RLC实体的场景，只保留用于PTM传输的RLC实体，不保留用于PTP传输的RLC实体，包括但不限于释放、重建或挂起用于PTP传输的RLC实体。
其中，所述RLC实体包括用于组播业务接收MRB关联的RLC实体。进一步的，对于一个 MRB关联多个RLC实体的场景，保留用于PTM传输的RLC实体，保留用于PTP传输的RLC实体，包括但不限于不释放、不重建或不挂起用于PTM传输的RLC实体，不释放、不重建或不挂起用于PTP传输的RLC实体。
其中，所述组播业务包括非激活态组播业务，即终端处于非激活态仍能执行业务数据接收的组播业务。
实施例2，不保留RLC实体的方案。
当终端停止组播业务接收时，不保留RLC实体。具体的，包括：
终端停止组播业务接收时，释放、重建或挂起RLC实体。
当终端使用的第一组播业务配置信息失效，终端不保留RLC实体，包括：
终端当前的驻留小区不支持组播业务或所述第一组播业务配置信息，终端不保留RLC实体。
或者，终端移出支持非激活态组播业务的区域或移出支持非激活态组播业务配置的区域，进一步的，所述终端仍处于RNA内，终端不保留RLC实体。
具体地，终端从支持组播业务的第一小区移动到不支持组播业务的第二小区，进一步的，所述终端仍处于RNA内，终端不保留RLC实体。
具体地，终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，进一步的，所述终端仍处于RNA内，终端不保留RLC实体。
或者，超过所述第一组播业务配置信息的有效期，例如第一组播业务配置信息对应的定时器到期等。
或者，当终端当前的驻留小区不支持所述组播业务或不支持所述第一组播业务配置信息，且超过所述第一组播业务配置信息的有效期，例如第一信标业务配置信息对应的定时器到期等。
或者，当组播业务会话去激活，终端不保留RLC实体。
基于上述实施例1和实施例2，其中，所述不保留RLC实体包括释放、重建或挂起用于非激活态组播业务接收的MRB关联的RLC实体。
进一步的，对于一个MRB关联多个RLC实体的场景，包括但不限于不保留(释放、重建或挂起)用于PTM传输的RLC实体。所述组播业务包括非激活态组播业务。
上述实施例中，提高了组播业务数据传输的可靠性，可用性高。
与前述应用功能实现方法实施例相对应，本公开还提供了应用功能实现装置的实施例。
参照图8，图8是根据一示例性实施例示出的一种组播业务数据的传输装置框图，所述装置应用于终端，包括：
执行模块801，被配置为当确定接收组播业务数据，保留无线链路控制RLC实体。
参照图9，图9是根据一示例性实施例示出的一种组播业务数据的传输装置框图，所述装置应用于网络设备，包括：
确定模块901，被配置为当终端接收组播业务数据，确定所述终端保留无线链路控制RLC实体。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中上述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本公开方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
相应地，本公开还提供了一种计算机可读存储介质，所述存储介质存储有计算机程序，所述计算机程序用于执行上述终端侧任一所述的组播业务数据的传输方法。
相应地，本公开还提供了一种计算机可读存储介质，所述存储介质存储有计算机程序，所述计算机程序用于执行上述网络设备侧任一所述的组播业务数据的传输方法。
相应地，本公开还提供了一种组播业务数据的传输装置，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为用于执行上述终端侧任一所述的组播业务数据的传输方法。
图10是根据一示例性实施例示出的一种组播业务数据的传输装置1000的框图。例如装置1000可以是手机、平板电脑、电子书阅读器、多媒体播放设备、可穿戴设备、车载用户设备、ipad、智能电视等终端。
参照图10，装置1000可以包括以下一个或多个组件：处理组件1002，存储器1004，电源组件1006，多媒体组件1008，音频组件1010，输入/输出(I/O)接口1012，传感器组件1016，以 及通信组件1018。
处理组件1002通常控制装置1000的整体操作，诸如与显示，电话呼叫，数据随机接入，相机操作和记录操作相关联的操作。处理组件1002可以包括一个或多个处理器1020来执行指令，以完成上述的组播业务数据的传输方法的全部或部分步骤。此外，处理组件1002可以包括一个或多个模块，便于处理组件1002和其他组件之间的交互。例如，处理组件1002可以包括多媒体模块，以方便多媒体组件1008和处理组件1002之间的交互。又如，处理组件1002可以从存储器读取可执行指令，以实现上述各实施例提供的一种组播业务数据的传输方法的步骤。
存储器1004被配置为存储各种类型的数据以支持在装置1000的操作。这些数据的示例包括用于在装置1000上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器1004可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1006为装置1000的各种组件提供电力。电源组件1006可以包括电源管理系统，一个或多个电源，及其他与为装置1000生成、管理和分配电力相关联的组件。
多媒体组件1008包括在所述装置1000和用户之间的提供一个输出接口的显示屏。在一些实施例中，多媒体组件1008包括一个前置摄像头和/或后置摄像头。当装置1000处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1010被配置为输出和/或输入音频信号。例如，音频组件1010包括一个麦克风(MIC)，当装置1000处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1004或经由通信组件1018发送。在一些实施例中，音频组件1010还包括一个扬声器，用于输出音频信号。
I/O接口1012为处理组件1002和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1016包括一个或多个传感器，用于为装置1000提供各个方面的状态评估。例如，传感器组件1016可以检测到装置1000的打开/关闭状态，组件的相对定位，例如所述组件为装置1000的显示器和小键盘，传感器组件1016还可以检测装置1000或装置1000一个组件的位置改变，用户与装置1000接触的存在或不存在，装置1000方位或加速/减速和装置1000的温度变化。传感器组件1016可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1016还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1016还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件1018被配置为便于装置1000和其他设备之间有线或无线方式的通信。装置1000可以接入基于通信标准的无线网络，如Wi-Fi，2G，3G，4G，5G或6G，或它们的组合。在一个示例性实施例中，通信组件1018经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件1018还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1000可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述终端侧任一所述的组播业务数据的传输方法。
在示例性实施例中，还提供了一种包括指令的非临时性机器可读存储介质，例如包括指令的存储器1004，上述指令可由装置1000的处理器1020执行以完成上述组播业务数据的传输方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
相应地，本公开还提供了一种组播业务数据的传输装置，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为用于执行上述网络设备侧任一所述的组播业务数据的传输方法。
如图11所示，图11是根据一示例性实施例示出的一种组播业务数据的传输装置1100的一结构示意图。装置1100可以被提供为网络设备。参照图11，装置1100包括处理组件1122、无线发 射/接收组件1124、天线组件1126、以及无线接口特有的信号处理部分，处理组件1122可进一步包括至少一个处理器。
处理组件1122中的其中一个处理器可以被配置为用于执行上述任一所述的组播业务数据的传输方法。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或者惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (50)

  1. 一种组播业务数据的传输方法，其特征在于，所述方法由终端执行，包括：
    当确定接收组播业务数据，保留无线链路控制RLC实体。
  2. 根据权利要求1所述的方法，其特征在于，所述组播业务包括非激活态组播业务。
  3. 根据权利要求1或2所述的方法，其特征在于，所述当确定接收组播业务数据，保留无线链路控制RLC实体，包括：
    当所述终端的状态发生改变，且确定接收所述组播业务数据，保留所述RLC实体。
  4. 根据权利要求3所述的方法，其特征在于，所述终端的状态发生改变，包括：
    所述终端从第一状态切换到第二状态，所述第一状态与所述第二状态不同；或者
    所述终端从所述第一状态切换到所述第二状态失败，并切换回所述第一状态。
  5. 根据权利要求3或4所述的方法，其特征在于，所述终端的状态发生改变，包括：
    所述终端从连接态切换到非激活态；
    所述终端从非激活态切换到连接态；
    所述终端尝试从非激活态切换到其他状态失败，并切换回非激活态。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，在所述保留无线链路控制RLC实体之前，所述方法还包括：
    接收到网络设备发送的指定消息。
  7. 根据权利要求6所述的方法，其特征在于，所述指定消息包括以下至少一项：
    携带挂起配置的无线资源控制RRC释放消息；
    RRC重配置消息；
    RRC恢复消息。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述方法还包括：
    当所述终端停止接收所述组播业务数据，不保留所述RLC实体。
  9. 根据权利要求8所述的方法，其特征在于，所述终端停止接收所述组播业务数据，包括以下至少一项：
    当所述终端使用的第一组播业务配置信息失效，所述终端停止接收所述组播业务数据；
    当所述终端的组播业务会话被去激活，所述终端停止接收所述组播业务数据。
  10. 根据权利要求9所述的方法，其特征在于，所述终端使用的第一组播业务配置信息失效，包括以下至少一项：
    所述终端的驻留小区不支持组播业务；
    所述终端的驻留小区不支持所述第一组播业务配置信息；
    所述第一组播业务配置信息超过有效期。
  11. 根据权利要求10所述的方法，其特征在于，所述终端的驻留小区不支持组播业务，包括：
    所述终端从支持非激活态组播业务的区域移动到不支持非激活态组播业务的区域。
  12. 根据权利要求10或11所述的方法，其特征在于，所述终端的驻留小区不支持组播业务，包括：
    所述终端从支持组播业务的第一小区移动到不支持组播业务的第二小区。
  13. 根据权利要求10所述的方法，其特征在于，所述终端的驻留小区不支持所述第一组播业务配置信息，包括：
    所述终端从支持非激活态组播业务配置信息的区域移动到不支持非激活态组播业务配置信息的区域。
  14. 根据权利要求10或13所述的方法，其特征在于，所述驻留小区不支持所述第一组播业务配置信息，包括：
    所述终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区。
  15. 根据权利要求8-14任一项所述的方法，其特征在于，所述终端处于基于无线接入网RAN的通知区域RNA内。
  16. 根据权利要求1-15任一项所述的方法，其特征在于，所述RLC实体与组播广播业务无线承载MRB关联，所述MRB用于接收所述组播业务数据。
  17. 根据权利要求1-7任一项所述的方法，其特征在于，所述保留无线链路控制RLC实体，包括：
    保留用于点对多点PTM传输的第一RLC实体。
  18. 根据权利要求1-7任一项所述的方法，其特征在于，与MRB关联的所述RLC实体的数目为多个；
    所述保留无线链路控制RLC实体，包括：
    在与所述MRB关联的多个RLC实体中，至少保留用于PTM传输的第一RLC实体。
  19. 根据权利要求8-15任一项所述的方法，其特征在于，所述不保留RLC实体，包括：
    不保留用于PTM传输的第一RLC实体。
  20. 根据权利要求8-15任一项所述的方法，其特征在于，与MRB关联的所述RLC实体的数目为多个；
    所述不保留所述RLC实体，包括：
    在与所述MRB关联的多个RLC实体中，至少不保留用于PTM传输的第一RLC实体。
  21. 根据权利要求1-7任一项所述的方法，其特征在于，所述保留所述RLC实体，包括以下任一项：
    不释放所述RLC实体；
    不重建所述RLC实体；
    不挂起所述RLC实体。
  22. 根据权利要求8-15任一项所述的方法，其特征在于，不保留所述RLC实体，包括以下任一项：
    释放所述RLC实体；
    重建所述RLC实体；
    挂起所述RLC实体。
  23. 一种组播业务数据的传输方法，其特征在于，所述方法由网络设备执行，包括：
    当终端接收组播业务数据，确定所述终端保留无线链路控制RLC实体。
  24. 根据权利要求23所述的方法，其特征在于，所述组播业务包括非激活态组播业务。
  25. 根据权利要求23或24所述的方法，其特征在于，所述当终端接收组播业务数据，确定所述终端保留无线链路控制RLC实体，包括：
    当所述终端的状态发生改变，且确定所述终端接收所述组播业务数据，确定所述终端保留所述RLC实体。
  26. 根据权利要求25所述的方法，其特征在于，所述终端的状态发生改变，包括：
    所述终端从第一状态切换到第二状态，所述第一状态与所述第二状态不同；或者
    所述终端从所述第一状态切换到所述第二状态失败，并切换回所述第一状态。
  27. 根据权利要求25或26所述的方法，其特征在于，所述终端的状态发生改变，包括：
    所述终端从连接态切换到非激活态；
    所述终端从非激活态切换到连接态；
    所述终端尝试从非激活态切换到其他状态失败，并切换回非激活态。
  28. 根据权利要求23-27任一项所述的方法，其特征在于，在确定所述终端保留无线链路控制RLC实体之前，所述方法还包括：
    向所述终端发送指定消息。
  29. 根据权利要求28所述的方法，其特征在于，所述指定消息包括以下至少一项：
    携带挂起配置的无线资源控制RRC释放消息；
    RRC重配置消息；
    RRC恢复消息。
  30. 根据权利要求23-29任一项所述的方法，其特征在于，所述方法还包括：
    当所述终端停止接收所述组播业务数据，确定所述终端不保留所述RLC实体。
  31. 根据权利要求30所述的方法，其特征在于，所述终端停止接收所述组播业务数据，包括以下至少一项：
    当所述终端使用的第一组播业务配置信息失效，所述终端停止接收所述组播业务数据；
    当所述终端的组播业务会话被去激活，所述终端停止接收所述组播业务数据。
  32. 根据权利要求31所述的方法，其特征在于，所述终端使用的第一组播业务配置信息失效，包括以下至少一项：
    所述终端的驻留小区不支持组播业务；
    所述终端的驻留小区不支持所述第一组播业务配置信息；
    所述第一组播业务配置信息超过有效期。
  33. 根据权利要求31所述的方法，其特征在于，所述终端的驻留小区不支持组播业务，包括：
    所述终端从支持非激活态组播业务的区域移动到不支持非激活态组播业务的区域，确定所述终端的驻留小区不支持组播业务。
  34. 根据权利要求32或33所述的方法，其特征在于，所述终端的驻留小区不支持组播业务，包括：
    所述终端从支持组播业务的第一小区移动到不支持组播业务的第二小区。
  35. 根据权利要求32所述的方法，其特征在于，所述终端的驻留小区不支持所述第一组播业务配置信息，包括：
    所述终端从支持非激活态组播业务的区域移动到不支持非激活态组播业务配置信息的区域。
  36. 根据权利要求32或35所述的方法，其特征在于，所述驻留小区不支持所述第一组播业务配置信息，包括：
    所述终端从支持组播业务且支持所述第一组播业务配置信息的第三小区，移动到支持组播业务但支持第二组播业务配置信息的第四小区。
  37. 根据权利要求30-36任一项所述的方法，其特征在于，所述终端处于基于无线接入网RAN的通知区域RNA内。
  38. 根据权利要求23-37任一项所述的方法，其特征在于，所述RLC实体与组播广播业务无线承载MRB关联，所述MRB用于接收所述组播业务数据。
  39. 根据权利要求23-30任一项所述的方法，其特征在于，所述确定所述终端保留无线链路控制RLC实体，包括：
    确定所述终端保留用于点对多点PTM传输的第一RLC实体。
  40. 根据权利要求23-29任一项所述的方法，其特征在于，与MRB关联的所述RLC实体的数目为多个；
    所述确定所述终端保留无线链路控制RLC实体，包括：
    在与所述MRB关联的多个RLC实体中，确定所述终端至少保留用于PTM传输的第一RLC实体。
  41. 根据权利要求30-37任一项所述的方法，其特征在于，所述确定所述终端不保留所述RLC实体，包括：
    确定所述终端不保留用于PTM传输的第一RLC实体。
  42. 根据权利要求30-37任一项所述的方法，其特征在于，与MRB关联的所述RLC实体的数目为多个；
    所述确定所述终端不保留所述RLC实体，包括：
    在与所述MRB关联的多个RLC实体中，确定所述终端至少不保留用于PTM传输的第一RLC实体。
  43. 根据权利要求23-29任一项所述的方法，其特征在于，所述确定所述终端保留所述RLC实体，包括以下任一项：
    确定所述终端不释放所述RLC实体；
    确定所述终端不重建所述RLC实体；
    确定所述终端不挂起所述RLC实体。
  44. 根据权利要求30-37任一项所述的方法，其特征在于，所述确定所述终端不保留所述RLC实体，包括以下任一项：
    确定所述终端释放所述RLC实体；
    确定所述终端重建所述RLC实体；
    确定所述终端挂起所述RLC实体。
  45. 一种组播业务数据的传输装置，其特征在于，所述装置应用于终端，包括：
    执行模块，被配置为当确定接收组播业务数据，保留无线链路控制RLC实体。
  46. 一种组播业务数据的传输装置，其特征在于，所述装置应用于网络设备，包括：
    确定模块，被配置为当终端接收组播业务数据，确定所述终端保留无线链路控制RLC实体。
  47. 一种计算机可读存储介质，其特征在于，所述存储介质存储有计算机程序，所述计算机程序用于执行上述权利要求1-22任一项所述的组播业务数据的传输方法。
  48. 一种计算机可读存储介质，其特征在于，所述存储介质存储有计算机程序，所述计算机程序用于执行上述权利要求23-44任一项所述的组播业务数据的传输方法。
  49. 一种组播业务数据的传输装置，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为用于执行上述权利要求1-22任一项所述的组播业务数据的传输方法。
  50. 一种组播业务数据的传输装置，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为用于执行上述权利要求23-44任一项所述的组播业务数据的传输方法。
PCT/CN2022/124180 2022-10-09 2022-10-09 组播业务数据的传输方法及装置、存储介质 WO2024077421A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/124180 WO2024077421A1 (zh) 2022-10-09 2022-10-09 组播业务数据的传输方法及装置、存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/124180 WO2024077421A1 (zh) 2022-10-09 2022-10-09 组播业务数据的传输方法及装置、存储介质

Publications (1)

Publication Number Publication Date
WO2024077421A1 true WO2024077421A1 (zh) 2024-04-18

Family

ID=90668497

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/124180 WO2024077421A1 (zh) 2022-10-09 2022-10-09 组播业务数据的传输方法及装置、存储介质

Country Status (1)

Country Link
WO (1) WO2024077421A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018201476A1 (zh) * 2017-05-05 2018-11-08 华为技术有限公司 多播承载的管理方法和终端设备
CN113518466A (zh) * 2020-04-09 2021-10-19 展讯通信（上海）有限公司 组播广播业务的反馈方法及装置
CN114071372A (zh) * 2020-08-07 2022-02-18 大唐移动通信设备有限公司 多播广播业务mbs传输方法、终端及网络设备
WO2022078328A1 (zh) * 2020-10-15 2022-04-21 夏普株式会社 用户设备执行的传输方法、用户设备、基站以及基站执行的传输方法
CN115038049A (zh) * 2021-03-05 2022-09-09 维沃移动通信有限公司 多播业务的接收方法、配置方法、终端及网络侧设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018201476A1 (zh) * 2017-05-05 2018-11-08 华为技术有限公司 多播承载的管理方法和终端设备
CN113518466A (zh) * 2020-04-09 2021-10-19 展讯通信（上海）有限公司 组播广播业务的反馈方法及装置
CN114071372A (zh) * 2020-08-07 2022-02-18 大唐移动通信设备有限公司 多播广播业务mbs传输方法、终端及网络设备
WO2022078328A1 (zh) * 2020-10-15 2022-04-21 夏普株式会社 用户设备执行的传输方法、用户设备、基站以及基站执行的传输方法
CN115038049A (zh) * 2021-03-05 2022-09-09 维沃移动通信有限公司 多播业务的接收方法、配置方法、终端及网络侧设备

Similar Documents

Publication Publication Date Title
US20230096763A1 (en) Ran-5gc interactions for session join, session start, session leave, session stop, and session delete for 5g multicast broadcast services
KR20200054282A (ko) 액세스 링크의 관리 방법, 디바이스, 저장 매체 및 시스템
EP4096252A1 (en) Voice call transfer method and electronic device
CN110505589B (zh) 集群通信方法、装置、调度机、终端和系统
US20230188949A1 (en) Communication method, apparatus, and system
CN114128366A (zh) 寻呼参数确定方法、装置、通信设备和存储介质
CN111345068B (zh) 数据通信方法、装置、通信设备及存储介质
WO2024077421A1 (zh) 组播业务数据的传输方法及装置、存储介质
EP4322560A1 (en) Service data transmission method and communication apparatus
WO2023065091A1 (zh) 寻呼过滤规则确定方法及装置、通信设备及存储介质
WO2022205362A1 (zh) 寻呼处理方法及装置、通信设备及存储介质
WO2022077232A1 (zh) 无线通信方法及装置、通信设备及存储介质
WO2022021271A1 (zh) 波束切换方法及装置、网络设备、终端及存储介质
CN118176750A (zh) 组播业务数据的传输方法及装置、存储介质
WO2024060023A1 (zh) 失败处理、终端行为确定方法及装置、存储介质
WO2022011557A1 (zh) 激活资源切换方法及装置、通信设备及存储介质
WO2022246845A1 (zh) 终端能力信息的上报方法、装置、通信设备及存储介质
WO2024087229A1 (zh) 信息确定方法及装置、存储介质
TWI786013B (zh) 一種通訊方法及裝置
WO2024060022A1 (zh) 信息接收、信息发送方法及装置、存储介质
WO2022205046A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2022151217A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2022160199A1 (zh) 通信方法及装置、用户设备、网络设备及存储介质
WO2023010316A1 (zh) 通信配置方法、装置、通信设备及存储介质
WO2023130482A1 (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: 22961618

Country of ref document: EP

Kind code of ref document: A1