WO2022184044A1 - 多播业务的接收方法、配置方法、终端及网络侧设备 - Google Patents

多播业务的接收方法、配置方法、终端及网络侧设备 Download PDF

Info

Publication number
WO2022184044A1
WO2022184044A1 PCT/CN2022/078553 CN2022078553W WO2022184044A1 WO 2022184044 A1 WO2022184044 A1 WO 2022184044A1 CN 2022078553 W CN2022078553 W CN 2022078553W WO 2022184044 A1 WO2022184044 A1 WO 2022184044A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
multicast service
reconfiguration
layer
indication information
Prior art date
Application number
PCT/CN2022/078553
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 EP22762509.2A priority Critical patent/EP4304212A1/en
Publication of WO2022184044A1 publication Critical patent/WO2022184044A1/zh
Priority to US18/241,867 priority patent/US20230422346A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present application belongs to the technical field of wireless communication, and specifically relates to a method for receiving a multicast service, a method for configuring the service, a terminal and a network side device.
  • MBSFN Multicast Broadcast Single Frequency Network
  • MBMS Multimedia Broadcast Multicast Service
  • SC-PTM Single Cell Point to Multipoint
  • the control information (control channel parameters, traffic channel parameters, scheduling information, etc.) and data information of the MBMS service are sent in a broadcast manner, so that both idle and connected UEs can receive the MBMS service.
  • the biggest difference between SC-PTM and MBSFN is that it is only dispatched in a single cell, and services are scheduled by the Group Radio Network Tempory Identity (G-RNTI).
  • G-RNTI Group Radio Network Tempory Identity
  • the scheduling information is notified by the Physical Downlink Control Channel (PDCCH) scrambled by G-RNTI, and the data part is sent by multicast. It is equivalent to that the interested UE monitors the G-RNTI to obtain data scheduling and then receives it.
  • the network side can configure two paths for the UE to transmit at the same time, one is a point-to-point (Point to Point, PTP) path, and the other is a point-to-multipoint (Point to Multipoint, PTM) path.
  • the PTM path refers to the use of a public wireless network temporary identity (Radio Network Tempory Identity, RNTI), such as G-RNTI to scramble the PDCCH, and all users in the group monitor the G-RNTI scheduling and receive subsequent scheduling data.
  • RNTI Radio Network Tempory Identity
  • the transmission can be received by multiple UEs at a time
  • the PTP path refers to the use of the UE-specific Cell Radio Network Temporary Identifier (C-RNTI) to scramble the PDCCH. Only this UE can monitor the C-RNTI. Scheduling of the RNTI and receiving subsequent scheduling data, a transmission can only be received by one UE at a time.
  • C-RNTI Cell Radio Network Temporary Identifier
  • PTM transmits to multiple UEs at the same time, and the transmission efficiency is high, but it needs to comprehensively consider the coverage of all UEs, so the selection of transmission parameters needs to be applicable to all UEs as much as possible, such as using omnidirectional antennas, considering poor users link quality, etc., PTM may not work well for individual UEs with extremely poor link quality.
  • PTP is a dedicated transmission of a UE. You can adjust the transmission parameters by considering the link of the user, such as using a directional or shaped antenna, and set the appropriate transmission parameters according to the current link of the UE. Therefore, the transmission effect for a single UE is better. Good, but if there are multiple users, multiple transmission resources are required, and the resource efficiency is low.
  • the multicast transmission mode of LTE does not support the two transmission modes of PTM and PTP, which is equivalent to the mode of only supporting PTM, and the LTE MBSFN mode is that all service transmissions in the entire synchronization area are strictly synchronized, while SC -
  • the PTM method is independent scheduling in a single cell, and does not consider continuous reception optimization across cells.
  • the MBSFN method For the multicast transmission designed by NR, it has been determined that the MBSFN method is not used. Because the scheduling efficiency is relatively low, strict synchronization between multiple cells cannot be guaranteed. If only single-cell scheduling is considered in the SC-PTM method, then When the UE performs cross-cell handover, it may cause discontinuous reception of multicast services, affecting user experience. And the conversion of multiple transmission path combination modes of PTP and PTM is a unique requirement of NR, and the problem of continuous reception during conversion needs to be solved.
  • the purpose of the embodiments of the present application is to provide a multicast service receiving method, configuration method, terminal and network side equipment, which can solve the problem of continuous reception of multicast services during cell handover or PTP and PTM path switching.
  • a method for receiving a multicast service executed by a terminal, including:
  • the reconfiguration information includes at least one of the following: used to indicate the PDCP SN of the multicast service or the target MRB of the multicast service before reconfiguration and The first indication information for synchronization after reconfiguration, the second indication information for instructing the PDCP layer operation performed by the terminal, the third indication information for instructing the RLC layer operation performed by the terminal, the RLC layer reconfiguration information , and, PDCP layer reconfiguration information;
  • Corresponding layer 2 processing is performed according to the reconfiguration information.
  • a method for configuring a multicast service is provided, which is performed by a network side device, including:
  • the reconfiguration information of the multicast service sent to the terminal includes at least one of the following: used to indicate the PDCP SN of the multicast service or the target MRB of the multicast service before reconfiguration and reconfiguration.
  • the first indication information of whether to be synchronized afterward the second indication information used to indicate the PDCP layer operation performed by the terminal, the third indication information used to indicate the RLC layer operation performed by the terminal, the RLC layer reconfiguration information, and , PDCP layer reconfiguration information.
  • a device for receiving a multicast service including:
  • a receiving module configured to receive reconfiguration information of a multicast service sent by a network side device, where the reconfiguration information includes at least one of the following: a PDCP SN used to indicate the multicast service or the target MRB of the multicast service first indication information for synchronization before and after reconfiguration, second indication information for instructing the PDCP layer operation performed by the terminal, third indication information for instructing the RLC layer operation performed by the terminal, RLC layer reconfiguration information, and PDCP layer reconfiguration information;
  • An execution module configured to execute corresponding layer 2 processing according to the reconfiguration information.
  • a device for configuring a multicast service including:
  • a sending module configured to send the reconfiguration information of the multicast service to the terminal, the reconfiguration information includes at least one of the following: a PDCP SN used to indicate that the multicast service or the target MRB of the multicast service is reconfiguring The first indication information for synchronization before configuration and after reconfiguration, the second indication information for instructing the PDCP layer operation performed by the terminal, the third indication information for instructing the RLC layer operation performed by the terminal, the RLC layer Reconfiguration information, and PDCP layer reconfiguration information.
  • a PDCP SN used to indicate that the multicast service or the target MRB of the multicast service is reconfiguring The first indication information for synchronization before configuration and after reconfiguration, the second indication information for instructing the PDCP layer operation performed by the terminal, the third indication information for instructing the RLC layer operation performed by the terminal, the RLC layer Reconfiguration information, and PDCP layer reconfiguration information.
  • a terminal in a fifth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor.
  • a network side device in a sixth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the The processor implements the steps of the method as described in the second aspect when executed.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect, or the The steps of the method of the second aspect.
  • a chip in an eighth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction, and implements the method described in the first aspect. the method described, or implement the method described in the second aspect.
  • a computer program product is provided, the computer program product is stored in a non-volatile storage medium, the computer program product is executed by at least one processor to implement the method according to the first aspect, or A method as described in the second aspect is implemented.
  • a tenth aspect provides a communication device configured to perform the method of the first aspect, or to perform the method of the second aspect.
  • the UE can maintain continuous reception of multicast services during cell handover or path switching of multicast services under the instruction of the network side, which not only ensures the flexibility of network scheduling, but also ensures that UE users Experience, on the basis of improving the QoS and experience of UE receiving MBS services, to further ensure system efficiency.
  • FIG. 1 is a block diagram of a wireless communication system to which an embodiment of the application can be applied;
  • FIG. 2 is a schematic diagram of a protocol stack architecture of a terminal according to an embodiment of the present application
  • FIG. 3 is a schematic flowchart of a method for receiving a multicast service according to an embodiment of the present application
  • FIG. 4 is a schematic flowchart of a method for configuring a multicast service according to an embodiment of the present application
  • FIG. 5 is a schematic structural diagram of an apparatus for receiving a multicast service according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of an apparatus for configuring a multicast service according to an embodiment of the present application
  • FIG. 7 is a schematic structural diagram of a communication device according to an embodiment of the application.
  • FIG. 8 is a schematic diagram of a hardware structure of a terminal according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a hardware structure of a network side device according to an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • the following description describes a New Radio (NR) system for example purposes, and uses NR terminology in most of the description below, although these techniques are also applicable to applications other than NR system applications, such as 6th generation ( 6th Generation , 6G) communication system.
  • 6th generation 6th Generation
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (Vehicle User Equipment, VUE), pedestrian terminal (Pedestrian User Equipment, PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, Wireless Local Area Network (WLAN) ) access point, WiFi node, Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary, it should be noted that , in the embodiments of the present application, only the base station in the NR system is used as an example, but the specific type of the base station is not limited.
  • BSS Basic Service Set
  • ESS Extended Service Set
  • Node B Evolved Node B
  • FIG. 2 is a schematic diagram of a protocol stack architecture of a terminal according to an embodiment of the present application.
  • DRB Data Radio Bearer
  • MRB MBMS radio bearer
  • a terminal may have multiple unicast DRBs, or multiple MRBs corresponding to a Temporary Mobile Group Identity (TMGI) or G-RNTI, or even multiple TMGIs or G-RNTIs.
  • TMGI Temporary Mobile Group Identity
  • G-RNTI Temporary Mobile Group Identity
  • Each TMGI or G-RNTI corresponds to one or more MRBs.
  • PTP paths can be configured, all of them can be configured with only PTM legs, or some of them can be configured with PTP legs, and the rest can only be configured with PTM legs.
  • PTM leg and PTP leg have a common Packet Data Convergence Protocol (PDCP) entity, so in the process of multicast service path conversion or cell handover, PDCP can be used layer to achieve continuous reception of multicast services.
  • PDCP Packet Data Convergence Protocol
  • FIG. 3 is a schematic flowchart of a method for receiving a multicast service according to an embodiment of the present application.
  • the method for receiving a multicast service includes:
  • Step 31 Receive the reconfiguration information of the multicast service sent by the network side device, the reconfiguration information includes at least one of the following: a PDCP sequence number ( Sequence Number, SN) the first indication information of whether to synchronize before and after reconfiguration, the second indication information used to indicate the PDCP layer operation performed by the terminal, and used to indicate the radio link control performed by the terminal.
  • each multicast service may be configured with at least one MRB, and each MRB may be configured with one or two RLC entities, and the one or two RLC entities share one PDCP layer entity.
  • Step 32 Perform corresponding layer 2 processing according to the reconfiguration information.
  • the UE can maintain continuous reception of the multicast service during cell handover or path change of the multicast service under the instruction of the network side, which not only ensures the flexibility of network scheduling, but also ensures the user experience of the UE. , on the basis of improving the quality of service (Quality of Service, QoS) and experience of the UE receiving MBS services, to further ensure system efficiency.
  • QoS Quality of Service
  • the network side may send the reconfiguration information of the multicast service to the terminal during the cell handover process or before the path conversion of the multicast service.
  • the terminal performs corresponding layer 2 processing according to the reconfiguration information in the process of cell handover or when the path of the multicast service is switched.
  • whether the PDCP SN is synchronized before and after reconfiguration is equivalent to whether the PDCP SN is synchronized between the source cell and the target cell, that is, the source cell before reconfiguration corresponds to the target cell after reconfiguration.
  • the reconfiguration information sent by the network side includes at least one of the following: used to indicate the multicast service or the target MRB of the multicast service
  • the first indication information of whether the PDCP SN is synchronized in the source cell and the target cell the second indication information used to indicate the PDCP layer operation performed by the terminal, and the third indication information used to indicate the RLC layer operation performed by the terminal , RLC layer reconfiguration information, and, PDCP layer reconfiguration information.
  • the terminal Since the terminal switches from the source cell to the target cell during cell handover, if the PDCP SNs allocated by the source cell and the target cell are synchronized for the MRB of the same multicast service, that is, the same PDCP SN is allocated to the same data packet (the same The data content of the PDCP SN is exactly the same), in this case, the terminal only needs to sort the PDCP SN according to the data packets received by the source cell and the target cell to ensure continuous and lossless service reception.
  • the premise of PDCP SN synchronization between the source cell and the target cell is: the content and pipeline of the multicast service data sent by the core network to different base stations or cells are the same, that is, a temporary mobility group identifier (TMGI) service corresponds to an MBS protocol input unit (Protocol Data Unit, PDU) session (session), MBS PDU session can contain different QoS flows (flow), there is a layer of core network (CN) tunnel at the MBS PDU session layer (level) (tunnel) SN number, there can also be a first-level CN SN number in each QoS flow granularity.
  • TMGI temporary mobility group identifier
  • PDCP SN CN SN.
  • Flows and other QoS flows that do not require lossless reception maintain a many-to-one mapping to MRB, abandoning PDCP SN synchronization.
  • the network side can also map some QoS flows that do not require lossless reception to one MRB as needed to reduce the number of MRBs and complexity.
  • the reconfiguration information does not include: The first indication information of whether the PDCP SN of the multicast service or the target MRB of the multicast service is synchronized before and after reconfiguration. That is, optionally, if the path of the multicast service needs to be converted, the reconfiguration information sent by the network side includes at least one of the following: second indication information used to instruct the terminal to perform a PDCP layer operation, used to The third indication information indicating the RLC layer operation performed by the terminal, the RLC layer reconfiguration information, and the PDCP layer reconfiguration information.
  • the second indication information includes at least one of the following:
  • Indication information that the terminal performs an Acknowledged Mode (AM) or Unacknowledged Mode (Unacknowledged Mode, UM) operation on the PDCP layer;
  • AM Acknowledged Mode
  • UM Unacknowledged Mode
  • the PDCP SN of the terminal receives the indication information whether the state variable needs to be maintained;
  • Indication information of whether the terminal needs to perform PDCP status report reporting after accessing the target cell is not limited.
  • the second indication information includes at least one of the following:
  • the method further includes:
  • a PTP RLC entity is configured in the reconfiguration information of the multicast service or the target MRB of the multicast service, and the mode of the PTP RLC entity is RLC AM, the multicast service or the multicast service is defaulted to The PDCP SN of the target MRB is synchronized before and after reconfiguration;
  • the PDCP SN of the multicast service or the target MRB of the multicast service is reconfigured. Synchronization before and after reconfiguration.
  • performing corresponding layer 2 processing according to the reconfiguration information includes at least one of the following:
  • the data of the described multicast service are sorted according to the PDCP SN, and are submitted to the upper layer according to the ascending order of the PDCP SN;
  • the MRB of the multicast service may have various combination configurations of multiple paths, for example, only the PTM path is used for transmission, only the PTP path is used for transmission, or both the PTM path and the PTP path are used for transmission, Therefore, the network side needs to explicitly or implicitly indicate to the terminal whether the corresponding PDCP layer should perform AM or UM operations.
  • the so-called explicit instruction means that the network side instructs the PDCP layer of the terminal to perform AM or UM operation by displaying the instruction. For example, 1 bit is used to explicitly indicate whether the multicast service of the target cell and the source cell or whether the PDCP SN of the target MRB of the multicast service is synchronized.
  • the implicit indication means that the terminal can determine that the PDCP layer performs AM or UM operation through the reconfiguration information of the RLC layer.
  • performing an AM or UM operation on the PDCP layer includes:
  • the AM or UM operation is performed on the PDCP layer (that is, an explicit instruction);
  • an AM or UM operation (ie, implicit indication) is performed on the PDCP layer.
  • performing an AM or UM operation on the PDCP layer includes at least one of the following:
  • the mode of the configured RLC entity is RLC AM, which performs AM operations on the PDCP layer;
  • the mode of the configured RLC entity is RLC UM, which performs UM operations on the PDCP layer;
  • the reconfiguration information indicates that the target MRB of the multicast service is configured with both the PTP RLC entity and the PTM RLC entity (that is, the PTP leg and the PTM leg are configured at the same time), and the modes of the PTP RLC entity and the PTM RLC entity are both For RLC AM, perform AM operations on the PDCP layer;
  • the reconfiguration information indicates that the target MRB of the multicast service is configured with both the PTP RLC entity and the PTM RLC entity (that is, the PTP leg and the PTM leg are configured at the same time), and the modes of the PTP RLC entity and the PTM RLC entity are both For RLC UM, perform UM operation on PDCP layer;
  • the mode of the PTP RLC entity is RLC AM
  • PTM The mode of the RLC entity is RLC UM, which performs AM or UM operations on the PDCP layer.
  • performing corresponding layer 2 processing according to the reconfiguration information includes at least one of the following:
  • the second indication information indicates that the PDCP SN receiving state variable does not need to be maintained, and/or, the first indication information indicates the multicast service or the target MRB of the multicast service.
  • the PDCP SNs are not synchronized before and after reconfiguration, sort the data of the multicast service received before reconfiguration according to the PDCP SN, and submit it to the upper layer in the ascending order of PDCP SN, and the PDCP of the multicast service
  • the receiving state variable is reset to the initial value, the data of the multicast service received after the reconfiguration is sorted according to the PDCP SN, and submitted to the upper layer according to the ascending order of the PDCP SN;
  • PDCP SN synchronization may not be achieved in all cases before and after reconfiguration, or PDCP SN synchronization is not required in some cases. In such cases, it is also necessary to standardize the L2 layer processing behavior of the UE. , try to ensure continuous reception.
  • the data of multicast services received from the source cell are sorted according to PDCP SN, and submitted in ascending order of PDCP SN.
  • the PDCP SN of the received data is 0-5, 7, 8, 10, which is equivalent to 6 And 9 is missing (missing), 0-5 are sent to the upper layer in order, 7-10 are buffered in the receive buffer (buffer), waiting for 6 and 9.
  • the data (7, 8, 10) currently in the receiving buffer are also submitted to the upper layer in ascending order, and then the PDCP receiving state variable of the multicast service is reset. Be the initial value, start the reception of the data of the multicast service of the target cell, sort according to the PDCP SN, and deliver it to the upper layer according to the ascending order of the PDCP SN.
  • the second indication information indicates that the PDCP SN receiving state variable needs to be maintained, and/or the first indication information indicates the PDCP of the multicast service or the target MRB of the multicast service
  • the SN is synchronized before reconfiguration and after reconfiguration, and the PDCP SN receiving state variables of the multicast service and the data in the reception buffer are retained, and the data of the multicast service received before and after reconfiguration are processed according to the PDCP SN. Sort and submit to the upper layer in ascending order of PDCP SN;
  • the PDCP SN reception state variables and the received buffered data of the UE before the reconfiguration can continue to be retained, and the multicast services received before and after the reconfiguration can be retained.
  • the second indication information indicates that the terminal needs to report the PDCP status report, generate and report the PDCP status report according to the current PDCP reception situation.
  • FMC first missing Count
  • bitmap bitmap
  • the network side receives the PDCP status report of the UE, and can use the PTP leg to retransmit the data packets missing from the UE to make up for the receiving gap (gap).
  • performing corresponding layer 2 processing according to the reconfiguration information includes at least one of the following:
  • the second indication information indicates that the PDCP SN receiving state variable does not need to be maintained, and/or, the first indication information indicates the multicast service or the target MRB of the multicast service.
  • the PDCP SNs are not synchronized before and after reconfiguration, sort the data of the multicast service received before reconfiguration according to the PDCP SN, and submit it to the upper layer in the ascending order of PDCP SN, and the PDCP of the multicast service
  • the receiving state variable is reset to the initial value, the data of the multicast service received after the reconfiguration is sorted according to the PDCP SN, and submitted to the upper layer according to the ascending order of the PDCP SN;
  • PDCP SN synchronization may not be achieved in all cases before and after reconfiguration, or PDCP SN synchronization is not required in some cases. In such cases, it is also necessary to standardize the L2 layer processing behavior of the UE. , try to ensure continuous reception.
  • the second indication information indicates that the PDCP SN receiving state variable needs to be maintained, and/or the first indication information indicates the PDCP of the multicast service or the target MRB of the multicast service
  • the SN is synchronized before and after the reconfiguration, and the PDCP SN receiving state variables of the multicast service and the data in the reception buffer are kept, and the data of the multicast service received before and after the reconfiguration are stored according to the PDCP SN. Sort and submit them to the upper layer in ascending order of PDCP SN;
  • PDCP UM entity sort the data of the multicast service received before the reconfiguration according to the PDCP SN, and submit it to the upper layer according to the ascending order of the PDCP SN, and reset the PDCP reception state variable of the multicast service to the initial value. value, sort the data of the multicast service received after reconfiguration according to PDCP SN, and submit it to the upper layer according to the ascending order of PDCP SN.
  • the PDCP UM entity does not need to consider the PDCP SN synchronization, and still resets the PDCP receiving state variable of the multicast service to the initial value (the PDCP UM entity of the target cell is cleared), and the data received before the reconfiguration is based on the existing Submit to the upper layer in ascending order, and then continue to sort the reconfigured data by its own PDCP SN, which is equivalent to sorting the data before and after reconfiguration.
  • sorting the data of the multicast service received after reconfiguration according to PDCP SN, and submitting it to the upper layer according to the ascending order of PDCP SN includes: using the first PDCP received after reconfiguration The SN plus 1 is used as the upper boundary variable of the PDCP receiving window, and the data of the multicast service received after the reconfiguration is sorted according to the PDCP SN, and delivered to the upper layer according to the ascending order of the PDCP SN.
  • performing corresponding layer 2 processing according to the reconfiguration information includes:
  • the terminal can receive according to the existing RLC AM receiving entity behavior, or set the first received RLC SN plus 1 as the upper boundary of the RLC UM receiving window.
  • reconstructing the PDCP layer includes:
  • PDCP AM reconstruction including reset of header compression and security update, because the header compression process of the target cell and the security parameters of the target cell are to be used;
  • the UE will reset all PDCP SN receiving state variables, but if PDCP SN synchronization is supported, the PDCP UM reconstruction after reconfiguration can also perform AM-like PDCP SN receiving state variable retention, which is convenient for reconfiguration
  • the pre- and mid-configured data are sorted by PDCP SN.
  • the default rebuild behavior is to clear all state, similar to creating a new entity.
  • the terminal performing a data recovery (data recovery) operation at the PDCP layer includes:
  • performing the reset, release or new creation of the PDCP layer by the terminal includes: clearing all PDCP entities of the source cell, or releasing the existing PDCP entities, and re-establishing a new PDCP entity from the initialization state. the PDCP entity.
  • the main solution is that, for example, the target cell and the source cell do not maintain PDCP SN synchronization, so the PDCP SN variable reception status of the source cell remains meaningless and cannot be sorted, so it is reset in the target cell.
  • the target cell and the source cell do not maintain PDCP SN synchronization, so the PDCP SN variable reception status of the source cell remains meaningless and cannot be sorted, so it is reset in the target cell.
  • the target cell and the source cell do not maintain PDCP SN synchronization, so the PDCP SN variable reception status of the source cell remains meaningless and cannot be sorted, so it is reset in the target cell.
  • the synchronization of PDCP SNs cannot be maintained.
  • the RLC layer operation performed by the terminal includes: the terminal performs RLC reset or release or new creation. Because in different cells, the RLC layer has different scheduling methods, and the RLC layer segmentation is completely different from the UM SN allocation (allocation), so the RLC entity of the source cell must be released or reset, and reset or create a new one in the target cell. RLC entity. In the case of cross-cell, for both PTM leg and PTP leg, RLC needs to be cleared.
  • the UE is in the same cell, and the serving cell does not change, but due to the configuration change or path switching of the multicast service, there will also be special operations that need to perform continuous reception.
  • This example takes path conversion as an example to illustrate, and other situations are similar.
  • performing corresponding layer 2 processing according to the reconfiguration information includes at least one of the following:
  • the PDCP UM entity since there is no feedback path, there is no place for enhancement.
  • the data of the multicast service is received according to the converted path, and the PDCP SN repetition detection is performed in the PDCP entity. and reordering operations, submitted to the upper layer in ascending order of PDCP SN;
  • the content that can be enhanced is: if the converted path contains a PTP RLC entity in an activated RLC AM mode, the PDCP status report is triggered;
  • the path switching instruction is sent through Layer 1 (L1) signaling or MAC CE, after the physical layer or the MAC layer receives and decodes the path switching instruction, it informs the PDCP layer through the interlayer interface, and the PDCP layer Data reception is performed according to the activated receiving entity in the path switching instruction.
  • L1 Layer 1
  • MAC CE Layer 1
  • the PTP RLC entity and the PTM RLC entity do not need to have influence, and can proceed according to the existing behavior of the respective entities.
  • triggering the reporting of the PDCP status report includes one of the following:
  • the PDCP status report is generated and reported according to the current PDCP reception situation, and there is no need to wait for the Hybrid automatic repeat request (HARQ) process timer, that is, the current FMC+bitmap, As long as a PDCP SN is not received correctly at the current moment, it is directly set to 0 in the bitmap, which means that it is not received correctly;
  • HARQ Hybrid automatic repeat request
  • the terminal can trigger the PDCP status report when it receives the path switch signaling, but because one or more PDCP PDUs may be undergoing HARQ process operations, such as HARQ retx, that is, the current PDCP PDU It is possible to succeed in subsequent HARQ retransmissions, so the UE can start a HARQ process timer first when the PDCP status report is triggered.
  • the specific value of the HARQ process timer can be configured by the network side or specified by the standard or implemented by the UE.
  • the UE can effectively avoid the wrong reporting of NACK , that is, it is not received correctly when the reporting trigger is triggered, but the correct reception is obtained through HARQ retransmission during the HARQ process timer, so that the PDCP SN can be reported as an ACK after the HARQ process timer expires, avoiding redundant Residual retransmission.
  • an embodiment of the present application further provides a method for configuring a multicast service, which is performed by a network side device, including:
  • Step 41 The reconfiguration information of the multicast service sent to the terminal, the reconfiguration information includes at least one of the following: used to indicate the PDCP SN of the multicast service or the target MRB of the multicast service before reconfiguration and the first indication information for synchronization after reconfiguration, the second indication information for instructing the PDCP layer operation performed by the terminal, the third indication information for instructing the RLC layer operation performed by the terminal, the RLC layer reconfiguration information, and PDCP layer reconfiguration information.
  • the second indication information includes at least one of the following:
  • the PDCP SN of the terminal receives the indication information whether the state variable needs to be maintained;
  • the second indication information includes at least one of the following:
  • the network side device will preferentially configure the lossless reception for the data flow that requires a higher block error rate in the QoS requirements, for example, the block error rate requirement is lower than 10 ⁇ -5 or 10 ⁇ -6.
  • the PTP leg is generally configured at the same time, and the PTP leg is configured as RLC AM.
  • a PTP leg In order to achieve lossless reception, a PTP leg must be configured in the target cell, and the PTP leg must be configured as RLC AM. At the same time, if there are other users in the target cell that receive the same multicast service, it is also necessary to configure PTM at the same time. leg, PTP leg can be configured as RLC UM, so that point-to-multipoint can send multicast service data to multiple terminals at the same time, which will have high resource efficiency.
  • the reconfiguration information of the multicast service by the target cell can be sent to the source cell through interface signaling (Xn interface signaling), and the source cell can then send it to the handover terminal through handover signaling.
  • the source cell and the target cell it can be judged through the interaction of the Xn interface whether the PDCP SN synchronization is satisfied.
  • the source cell and the target cell exchange a certain MRB corresponding to the TMGI service through an explicit process. Whether the PDCP SN is synchronized, or the source cell can determine whether the MRB supports PDCP SN synchronization through an implicit process. Therefore, it is considered that PDCP SN synchronization is supported.
  • the indication information of whether the terminal needs to perform PDCP layer reconstruction includes:
  • the indication of PDCP AM re-establishment also includes the reset and security update of header compression, because the header compression process of the target cell and the security parameters of the target cell are to be used;
  • the indication information of whether the terminal needs to perform a data recovery (data recovery) operation at the PDCP layer includes:
  • the PDCP status report is an uplink feedback process, so there must be a PTP leg, and the PTP leg is configured with an RLC AM, and PDCP is transmitted on this PTP leg.
  • Status report if the target PDCP is UM, the feedback PDCP status report cannot be configured because there is no uplink path for bearer and transmission.
  • the third indication information used to instruct the RLC layer operation performed by the terminal includes: an indication used to indicate whether the terminal performs RLC reset or release or new creation.
  • an MRB has only the leg of the RLC UM, that is, the PTM is configured as the RLC UM, or the PTM and the PTP are configured as the RLC UM, a certain degree of continuous reception can also be achieved when the PDCP SN is synchronized.
  • the execution subject may be a device for receiving a multicast service, or, in the device for receiving a multicast service, a method for executing a method for receiving a multicast service is executed. control module.
  • a method for receiving a multicast service performed by a device for receiving a multicast service is used as an example to describe the device for receiving a multicast service provided by the embodiments of the present application.
  • an embodiment of the present application further provides an apparatus 50 for receiving a multicast service, including:
  • a receiving module 51 configured to receive reconfiguration information of a multicast service sent by a network side device, where the reconfiguration information includes at least one of the following: a PDCP used to indicate the multicast service or a target MRB of the multicast service
  • the first indication information for whether the SN is synchronized before and after reconfiguration the second indication information for instructing the PDCP layer operation performed by the terminal, and the third indication information for instructing the RLC layer operation performed by the terminal , RLC layer reconfiguration information, and, PDCP layer reconfiguration information;
  • the execution module 52 is configured to execute corresponding layer 2 processing according to the reconfiguration information.
  • the second indication information includes at least one of the following:
  • the PDCP SN of the terminal receives the indication information whether the state variable needs to be maintained;
  • the executing module 52 configured to execute corresponding layer 2 processing according to the reconfiguration information, includes at least one of the following:
  • the data of the described multicast service are sorted according to the PDCP SN, and are submitted to the upper layer according to the ascending order of the PDCP SN;
  • the execution module 52 is configured to perform AM or UM operation on the PDCP layer according to the indication information that the terminal performs the AM or UM operation on the PDCP layer in the reconfiguration information;
  • the executing module 52 is configured to execute AM or UM operation on the PDCP layer according to the reconfiguration information of the RLC layer in the reconfiguration information.
  • the executing module 52 is further configured to execute at least one of the following:
  • the AM operation is performed on the PDCP layer;
  • the target MRB indicated in the reconfiguration information is only configured with a PTP RLC entity or a PTM RLC entity, and the mode of the configured RLC entity is RLC UM, perform a UM operation on the PDCP layer;
  • the AM operation is performed on the PDCP layer
  • the target MRB of the multicast service is configured with a PTP RLC entity and a PTM RLC entity at the same time, and the modes of the PTP RLC entity and the PTM RLC entity are both RLC UM, perform a UM operation on the PDCP layer;
  • the PDCP layer Perform AM or UM operations.
  • the apparatus for receiving the multicast service further includes:
  • the first processing module is used for if a PTP RLC entity is configured in the reconfiguration information of the multicast service or the target MRB of the multicast service, and the mode of the PTP RLC entity is RLC AM, by default the multicast
  • the PDCP SN of the service or the target MRB of the multicast service is synchronized before and after reconfiguration;
  • the second processing module is configured to, if there is a one-to-one mapping relationship between the QoS flow of the multicast service and the MRB before the reconfiguration and after the reconfiguration, default the multicast service or the target of the multicast service
  • the PDCP SN of the MRB is synchronized before and after reconfiguration.
  • the execution module 52 is configured to execute at least one of the following:
  • the second indication information indicates that the PDCP SN receiving state variable does not need to be maintained, and/or the first indication information indicates the PDCP SN of the multicast service or the target MRB of the multicast service
  • sort the data of the multicast service received before the reconfiguration according to the PDCP SN and submit it to the upper layer according to the ascending order of the PDCP SN, and report the PDCP reception status of the multicast service.
  • the variable is reset to the initial value, the data of the multicast service received after the reconfiguration is sorted according to the PDCP SN, and submitted to the upper layer according to the ascending order of the PDCP SN;
  • the second indication information indicates that the PDCP SN receiving state variable needs to be maintained, and/or the first indication information indicates that the multicast service or the PDCP SN of the target MRB of the multicast service is in Synchronize before and after reconfiguration, keep the PDCP SN receiving state variable of the multicast service and receive buffered data, and sort the data of the multicast service received before and after reconfiguration according to PDCP SN , and submit it to the upper layer in ascending order of PDCP SN;
  • the PDCP status report is generated and reported according to the current PDCP reception situation.
  • the execution module 52 is configured to execute at least one of the following:
  • the second indication information indicates that the PDCP SN receiving state variable does not need to be maintained, and/or the first indication information indicates the PDCP SN of the multicast service or the target MRB of the multicast service
  • sort the data of the multicast service received before the reconfiguration according to the PDCP SN and submit it to the upper layer according to the ascending order of the PDCP SN, and report the PDCP reception status of the multicast service.
  • the variable is reset to the initial value, the data of the multicast service received after the reconfiguration is sorted according to the PDCP SN, and submitted to the upper layer according to the ascending order of the PDCP SN;
  • the second indication information indicates that the PDCP SN receiving state variable needs to be maintained, and/or the first indication information indicates that the multicast service or the PDCP SN of the target MRB of the multicast service is in Synchronize before and after reconfiguration, keep the PDCP SN receiving state variable of the multicast service and receive buffered data, and sort the data of the multicast service received before and after reconfiguration according to PDCP SN , and submit it to the upper layer in ascending order of PDCP SN;
  • the data of the multicast service received before the reconfiguration is sorted according to the PDCP SN, and submitted to the upper layer according to the ascending order of the PDCP SN, and the PDCP reception state variable of the multicast service is reset to the initial value
  • the data of the multicast service received after the reconfiguration is sorted according to the PDCP SN, and delivered to the upper layer according to the ascending order of the PDCP SN.
  • the execution module 52 is further configured to use the first PDCP SN received after the reconfiguration plus 1 as the upper boundary variable of the PDCP receiving window, and use the data of the multicast service received after the reconfiguration according to the PDCP SN.
  • SNs are sorted and submitted to the upper layer in ascending order of PDCP SNs.
  • the executing module 52 is further configured to execute at least one of the following if the second indication information indicates that the terminal needs to reset, release or create an RLC layer:
  • the RLC entity is reset, released or newly created
  • the first RLC SN received plus 1 is set as the upper boundary of the RLC UM receive window.
  • the execution module 52 is configured to execute at least one of the following:
  • the data of the multicast service is received according to the converted path, and the PDCP SN repetition detection and reordering operations are performed on the PDCP entity, and are delivered to the upper layer according to the PDCP SN ascending order;
  • the PDCP AM entity For the PDCP AM entity, if the converted path contains the PTP RLC entity in the activated RLC AM mode, the PDCP status report is triggered;
  • the path switch instruction For the PDCP AM entity, if the path switch instruction is sent through layer-one signaling or MAC CE, after the physical layer or the MAC layer receives and decodes the path switch instruction, it informs the PDCP layer through the interlayer interface, and the PDCP layer switches according to the path.
  • the active receiving entity in the indication performs data reception.
  • the execution module 52 is further configured to execute one of the following:
  • the PDCP status report When the PDCP status report is triggered, the PDCP status report is generated and reported according to the current PDCP reception situation;
  • the HARQ process timer is started, and after the HARQ process timer expires, the PDCP status report is generated and reported according to the PDCP reception situation.
  • the apparatus for receiving the multicast service in this embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal.
  • the device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the apparatus for receiving the multicast service in the embodiment of the present application may be an apparatus having an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the apparatus for receiving a multicast service provided by the embodiment of the present application can implement each process implemented by the method embodiment in FIG. 3 , and achieve the same technical effect. To avoid repetition, details are not described here.
  • the execution subject may be a configuration device for multicast services, or, in the configuration device for multicast services, the configuration method for executing multicast services control module.
  • the device for configuring a multicast service provided by the embodiment of the present application is described by taking a method for configuring a multicast service performed by a device for configuring a multicast service as an example.
  • an embodiment of the present application further provides an apparatus 60 for configuring a multicast service, including:
  • the sending module 61 is used to send the reconfiguration information of the multicast service to the terminal, where the reconfiguration information includes at least one of the following: the PDCP SN used to indicate that the multicast service or the target MRB of the multicast service is in The first indication information for synchronization before and after reconfiguration, the second indication information for instructing the PDCP layer operation performed by the terminal, the third indication information for instructing the RLC layer operation performed by the terminal, RLC Layer reconfiguration information, and PDCP layer reconfiguration information.
  • the second indication information includes at least one of the following:
  • the PDCP SN of the terminal receives the indication information whether the state variable needs to be maintained;
  • the apparatus for receiving a multicast service provided by the embodiment of the present application can implement each process implemented by the method embodiment in FIG. 4 , and achieve the same technical effect. To avoid repetition, details are not described here.
  • an embodiment of the present application further provides a communication device 70, including a processor 71, a memory 72, a program or instruction stored in the memory 72 and executable on the processor 71, for example, the communication
  • the device 70 is a terminal
  • the program or instruction is executed by the processor 71
  • each process of the above-mentioned embodiment of the method for receiving a multicast service is implemented, and the same technical effect can be achieved.
  • the communication device 70 is a network-side device, when the program or instruction is executed by the processor 71, each process of the above-mentioned embodiment of the multicast service configuration method can be realized, and the same technical effect can be achieved. To avoid repetition, details are not repeated here. .
  • FIG. 8 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 80 includes but is not limited to: a radio frequency unit 81, a network module 82, an audio output unit 83, an input unit 84, a sensor 85, a display unit 86, a user input unit 87, an interface unit 88, a memory 89, a processor 810 and other components .
  • the terminal 80 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 810 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 8 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 84 may include a graphics processor (Graphics Processing Unit, GPU) 841 and a microphone 842. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 86 may include a display panel 861, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 87 includes a touch panel 871 and other input devices 872 .
  • the touch panel 871 is also called a touch screen.
  • the touch panel 871 may include two parts, a touch detection device and a touch controller.
  • Other input devices 872 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.
  • the radio frequency unit 81 receives the downlink data from the network side device, and then processes it to the processor 810; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 81 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 89 may be used to store software programs or instructions as well as various data.
  • the memory 89 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 89 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 810 may include one or more processing units; optionally, the processor 810 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 810.
  • the radio frequency unit 81 is configured to receive the reconfiguration information of the multicast service sent by the network side device, and the reconfiguration information includes at least one of the following: used to indicate the multicast service or the target MRB of the multicast service.
  • the processor 810 is configured to perform corresponding layer 2 processing according to the reconfiguration information.
  • the second indication information includes at least one of the following:
  • the PDCP SN of the terminal receives the indication information whether the state variable needs to be maintained;
  • the processor 810 is configured to execute at least one of the following:
  • the data of the described multicast service are sorted according to the PDCP SN, and are submitted to the upper layer according to the ascending order of the PDCP SN;
  • the processor 810 is configured to perform the AM or UM operation on the PDCP layer according to the indication information that the terminal performs the AM or UM operation on the PDCP layer in the reconfiguration information;
  • the processor 810 is configured to perform AM or UM operation on the PDCP layer according to the reconfiguration information of the RLC layer in the reconfiguration information.
  • the processor 810 is configured to execute at least one of the following:
  • the AM operation is performed on the PDCP layer;
  • the target MRB indicated in the reconfiguration information is only configured with a PTP RLC entity or a PTM RLC entity, and the mode of the configured RLC entity is RLC UM, perform a UM operation on the PDCP layer;
  • the AM operation is performed on the PDCP layer
  • the target MRB of the multicast service is configured with a PTP RLC entity and a PTM RLC entity at the same time, and the modes of the PTP RLC entity and the PTM RLC entity are both RLC UM, perform a UM operation on the PDCP layer;
  • the PDCP layer Perform AM or UM operations.
  • the processor 810 is configured to execute if a PTP RLC entity is configured in the reconfiguration information of the multicast service or the target MRB of the multicast service, and the mode of the PTP RLC entity is RLC AM, By default, the PDCP SN of the multicast service or the target MRB of the multicast service is synchronized before and after reconfiguration;
  • the processor 810 is configured to execute a one-to-one mapping relationship between the QoS flow of the multicast service and the MRB before and after the reconfiguration, by default, the multicast service or the The PDCP SN of the target MRB is synchronized before and after reconfiguration.
  • the processor 810 is configured to execute at least one of the following:
  • the second indication information indicates that the PDCP SN receiving state variable does not need to be maintained, and/or the first indication information indicates the PDCP SN of the multicast service or the target MRB of the multicast service
  • sort the data of the multicast service received before the reconfiguration according to the PDCP SN and submit it to the upper layer according to the ascending order of the PDCP SN, and report the PDCP reception status of the multicast service.
  • the variable is reset to the initial value, the data of the multicast service received after the reconfiguration is sorted according to the PDCP SN, and submitted to the upper layer according to the ascending order of the PDCP SN;
  • the second indication information indicates that the PDCP SN receiving state variable needs to be maintained, and/or the first indication information indicates that the multicast service or the PDCP SN of the target MRB of the multicast service is in Synchronize before and after reconfiguration, keep the PDCP SN receiving state variable of the multicast service and receive buffered data, and sort the data of the multicast service received before and after reconfiguration according to PDCP SN , and submit it to the upper layer in ascending order of PDCP SN;
  • the PDCP status report is generated and reported according to the current PDCP reception situation.
  • the processor 810 is configured to execute at least one of the following:
  • the second indication information indicates that the PDCP SN receiving state variable does not need to be maintained, and/or the first indication information indicates the PDCP SN of the multicast service or the target MRB of the multicast service
  • sort the data of the multicast service received before the reconfiguration according to the PDCP SN and submit it to the upper layer according to the ascending order of the PDCP SN, and report the PDCP reception status of the multicast service.
  • the variable is reset to the initial value, the data of the multicast service received after the reconfiguration is sorted according to the PDCP SN, and submitted to the upper layer according to the ascending order of the PDCP SN;
  • the second indication information indicates that the PDCP SN receiving state variable needs to be maintained, and/or the first indication information indicates that the multicast service or the PDCP SN of the target MRB of the multicast service is in Synchronize before and after reconfiguration, keep the PDCP SN receiving state variable of the multicast service and receive buffered data, and sort the data of the multicast service received before and after reconfiguration according to PDCP SN , and submit it to the upper layer in ascending order of PDCP SN;
  • the data of the multicast service received before the reconfiguration is sorted according to the PDCP SN, and submitted to the upper layer according to the ascending order of the PDCP SN, and the PDCP reception state variable of the multicast service is reset to the initial value
  • the data of the multicast service received after the reconfiguration is sorted according to the PDCP SN, and delivered to the upper layer according to the ascending order of the PDCP SN.
  • the processor 810 is configured to execute the first PDCP SN received after the reconfiguration plus 1 as the upper boundary variable of the PDCP receiving window, and the data of the multicast service received after the reconfiguration is performed according to the PDCP SN. Sort and submit to the upper layer in ascending order of PDCP SN.
  • the processor 810 is configured to execute at least one of the following if the second indication information indicates that the terminal needs to reset, release or create an RLC layer:
  • the RLC entity is reset, released or newly created
  • the first RLC SN received plus 1 is set as the upper boundary of the RLC UM receive window.
  • the processor 810 is configured to execute at least one of the following:
  • the data of the multicast service is received according to the converted path, and the PDCP SN repetition detection and reordering operations are performed on the PDCP entity, and are delivered to the upper layer according to the PDCP SN ascending order;
  • the PDCP AM entity For the PDCP AM entity, if the converted path contains the PTP RLC entity in the activated RLC AM mode, the PDCP status report is triggered;
  • the path switch instruction For the PDCP AM entity, if the path switch instruction is sent through layer-one signaling or MAC CE, after the physical layer or the MAC layer receives and decodes the path switch instruction, it informs the PDCP layer through the interlayer interface, and the PDCP layer switches according to the path.
  • the active receiving entity in the indication performs data reception.
  • the processor 810 is configured to execute one of the following:
  • the PDCP status report When the PDCP status report is triggered, the PDCP status report is generated and reported according to the current PDCP reception situation;
  • the HARQ process timer is started, and after the HARQ process timer expires, the PDCP status report is generated and reported according to the PDCP reception situation.
  • the network device 900 includes: an antenna 91 , a radio frequency device 92 , and a baseband device 93 .
  • the antenna 91 is connected to the radio frequency device 92 .
  • the radio frequency device 92 receives information through the antenna 91, and sends the received information to the baseband device 93 for processing.
  • the baseband device 93 processes the information to be sent and sends it to the radio frequency device 92
  • the radio frequency device 92 processes the received information and sends it out through the antenna 91 .
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 93 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 93 .
  • the baseband apparatus 93 includes a processor 94 and a memory 95 .
  • the baseband device 93 may include, for example, at least one baseband board on which a plurality of chips are arranged. As shown in FIG. 9 , one of the chips is, for example, the processor 94 , which is connected to the memory 95 to call the program in the memory 95 and execute it.
  • the network devices shown in the above method embodiments operate.
  • the baseband device 93 may further include a network interface 96 for exchanging information with the radio frequency device 92, and the interface is, for example, a common public radio interface (CPRI for short).
  • CPRI common public radio interface
  • the network-side device in this embodiment of the present application further includes: instructions or programs that are stored in the memory 95 and run on the processor 94, and the processor 94 invokes the instructions or programs in the memory 95 to execute the modules shown in FIG. 4 .
  • An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the above-mentioned method for receiving a multicast service or a method for configuring a multicast service is implemented.
  • a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the above-mentioned method for receiving a multicast service or a method for configuring a multicast service is implemented.
  • the processor is the processor in the terminal described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used for running network-side device programs or instructions to implement the above multicast service
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is used for running network-side device programs or instructions to implement the above multicast service
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • An embodiment of the present application further provides a program product, the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement the above-mentioned method for receiving a multicast service or a method for receiving a multicast service.
  • the various processes of the configuration method embodiments can achieve the same technical effect, and are not repeated here to avoid repetition.
  • the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of this application.
  • a storage medium such as ROM/RAM, magnetic disk, CD-ROM

Landscapes

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

Abstract

本申请公开了一种多播业务的接收方法、配置方法、终端及网络侧设备，该多播业务的接收方法包括：接收网络侧设备发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息；根据所述重配置信息执行对应的层二处理。

Description

多播业务的接收方法、配置方法、终端及网络侧设备
相关申请的交叉引用
本申请主张在2021年3月5日在中国提交的中国专利申请No.202110247370.5的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于无线通信技术领域，具体涉及一种多播业务的接收方法、配置方法、终端及网络侧设备。
背景技术
在长期演进(Long Term Evolution，LTE)的广播多播传输中，支持多播广播单频网络(Multicast Broadcast Single Frequency Network，MBSFN)方式多媒体多播广播业务(Multimedia Broadcast Multicast Service，MBMS)发送和单小区点对多点(Single cell Point to Multipoint，SC-PTM)方式多播业务发送。MBSFN的方式中，处于同一个MBSFN区域的小区会同步的发送相同的广播业务，便于用户设备(User Equipment，UE，也称为终端)进行接收。MBMS业务的控制信息(控制信道参数、业务信道参数和调度信息等)和数据信息都是广播方式发送，使得空闲态(idle)态UE和连接态UE都可以接收MBMS业务。SC-PTM跟MBSFN方式最大的不同是只在单小区调度发送，由组无线网络临时标识(Group Radio Network Tempory Identity，G-RNTI)来进行业务调度。在广播消息里广播控制信道参数、业务的标识和周期信息等，调度信息由G-RNTI加扰的物理下行控制信道(Physical Downlink Control Channel，PDCCH)来进行通知，数据部分是组播方式发送，相当于感兴趣的UE监听G-RNTI获得数据调度进而进行接收。
对于一个多播业务，网络侧可以为UE同时配置两条路径进行传输，一条是点对点(Point to Point，PTP)路径，另一条是点对多点(Point to Multipoint，PTM)路径。PTM路径是指使用公共的无线网络临时标识(Radio Network  Tempory Identity，RNTI)，例如G-RNTI进行PDCCH的加扰，所有组内的用户共同监听G-RNTI的调度和接收其后的调度数据，传输一次可以被多个UE共同接收，而PTP路径是指使用UE专用的小区无线网络临时标识(Cell Radio Network Temporary Identifier，C-RNTI)进行PDCCH的加扰，只有这个UE可以监听到该C-RNTI的调度和接收其后的调度数据，传输一次只能被一个UE接收。
PTM是同时向多个UE进行传输，传输效率较高，但它需要综合考虑对所有UE的覆盖，因此在传输参数的选择上需要尽量适用于所有UE，例如使用全向天线，考虑较差用户的链路质量等，PTM可能对于个别极差链路质量的UE效果不好。而PTP是一个UE的专属传输，可以考虑这个用户的链路情况，调整发送参数，例如使用定向或者赋形天线，根据当前UE的链路设置适合的传输参数，因此对单个UE的传输效果较好，但是如果是多个用户，则需要多个传输资源，资源效率较低。
在现有技术中，LTE的多播传输方式并未支持PTM和PTP两种传输方式，相当于仅支持PTM的方式，且LTE MBSFN方式是整个同步区域内所有的业务发送都严格同步，而SC-PTM方式是单小区独立调度，并不考虑跨小区的连续接收优化。
NR设计的多播传输，首先已经确定不使用MBSFN的方式，因为调度效率比较低，因此多小区之间的严格同步是无法确保的，如果完全按照SC-PTM的方式仅考虑单小区调度，则UE在跨小区切换时，会造成对多播业务接收不连续的情况，影响用户体验。并且PTP和PTM多种传输路径组合方式的转换，是NR特有的需求，需要解决转换时的连续接收问题。
发明内容
本申请实施例的目的是提供一种多播业务的接收方法、配置方法、终端及网络侧设备，能够解决小区切换或PTP和PTM路径转换时多播业务的连续接收问题。
为了解决上述技术问题，本申请是这样实现的：
第一方面，提供了一种多播业务的接收方法，由终端执行，包括：
接收网络侧设备发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息；
根据所述重配置信息执行对应的层二处理。
第二方面，提供了一种多播业务的配置方法，由网络侧设备执行，包括：
向终端发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息。
第三方面，提供了一种多播业务的接收装置，包括：
接收模块，用于接收网络侧设备发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息；
执行模块，用于根据所述重配置信息执行对应的层二处理。
第四方面，提供了一种多播业务的配置装置，包括：
发送模块，用于向终端发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层 操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息。
第五方面，提供了一种终端，该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种网络侧设备，该网络侧设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第七方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第八方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现如第一方面所述的方法，或实现如第二方面所述的方法。
第九方面，提供了一种计算机程序产品，所述计算机程序产品存储在非易失的存储介质中，所述计算机程序产品被至少一个处理器执行以实现如第一方面所述的方法，或实现如第二方面所述的方法。
第十方面，提供了一种通信设备，被配置为执行如第一方面所述的方法，或执行如第二方面所述的方法。
在本申请实施例中，UE可以在网络侧的指示下在小区切换时或者多播业务的路径转换时维持对多播业务的连续接收，既保障了网络调度的灵活性也确保了UE的用户体验，在提升UE接收MBS业务的QoS和体验的基础上，进一步确保系统效率。
附图说明
图1为本申请实施例可应用的一种无线通信系统的框图；
图2为本申请实施例的终端的协议栈架构示意图；
图3为本申请实施例的多播业务的接收方法的流程示意图；
图4为本申请实施例的多播业务的配置方法的流程示意图；
图5为本申请实施例的多播业务的接收装置的结构示意图；
图6为本申请实施例的多播业务的配置装置的结构示意图；
图7为本申请实施例的通信设备的结构示意图；
图8为本申请实施例的终端的硬件结构示意图；
图9为本申请实施例的网络侧设备的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以 上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，尽管这些技术也可应用于NR系统应用以外的应用，如第6代(6 th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、无线局域网(Wireless Local Area Network，WLAN)接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的多播业务的接收方法、配置方法、终端及网络侧设备进行详细地说明。
请参考图2，图2为本申请实施例的终端的协议栈架构示意图，图2中仅画了一个单播数据无线承载(Data Radio Bearer，DRB)和一个MBMS无线承载(mbms radio bearer，MRB)，方便举例并明确给出二者之间的协议栈 关联性。在实际中，终端可以有多个单播DRB，也可以有一个临时移动组标识(Temporary Mobile Group Identity，TMGI)或G-RNTI对应的多个MRB，甚至可以有多个TMGI或G-RNTI，每个TMGI或G-RNTI对应一个或者多个MRB。其中，多个MRB中，可以全部配置PTP路径(leg)，可以全部仅配置PTM leg，也可以有部分配置PTP leg，其余仅仅只配置PTM leg。从图2可以看出，对于一个MRB，其PTM leg和PTP leg具有公共的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)实体，因此在多播业务路径转换或者小区切换的过程中可以通过PDCP层来实现对多播业务的连续接收。
请参考图3，图3为本申请实施例的多播业务的接收方法的流程示意图，该多播业务的接收方法包括：
步骤31：接收网络侧设备发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP序列号(Sequence Number，SN)在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的无线链路控制(Radio Link Control，RLC)层操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息；
本申请实施例中，每个多播业务可以配置有至少一个MRB，每个MRB配置有一个或两个RLC实体，该一个或两个RLC实体共用一个PDCP层实体。
步骤32：根据所述重配置信息执行对应的层二处理。
本申请实施例中，UE可以在网络侧的指示下在小区切换时或者多播业务的路径转换时维持对多播业务的连续接收，既保障了网络调度的灵活性也确保了UE的用户体验，在提升UE接收MBS业务的服务质量(Quality of Service，QoS)和体验的基础上，进一步确保系统效率。
本申请实施例中，网络侧可以在小区切换过程中或者多播业务的路径转换之前，向终端发送多播业务的重配置信息。终端在小区切换过程中或者多播业务的路径转换时，根据所述重配置信息执行对应的层二处理。
当应用于小区切换过程时，PDCP SN在重配置前和重配置后是否同步，相当于PDCP SN在源小区和目标小区是否同步，即重配置前对应源小区，重配置后对应目标小区。
本申请实施例中，可选的，若在小区切换的过程中，网络侧发送的所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在源小区和目标小区是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息。
由于在进行小区切换时，终端从源小区切换到目标小区，如果源小区和目标小区对于同一个多播业务的MRB其分配的PDCP SN同步，即相同的PDCP SN分给相同的数据包(相同PDCP SN的数据内容是完全一样)，在这种情况下，终端只需要按照源小区和目标小区接收的数据包进行PDCP SN排序，即可确保连续及无损的业务接收效果。
本申请实施例中，源小区和目标小区PDCP SN同步的前提是：核心网发送到不同的基站或小区的多播业务的数据，其内容和管道都是一样的，即一个临时移动组标识(TMGI)业务对应一个MBS协议输入单元(Protocol Data Unit，PDU)会话(session)，MBS PDU会话可以包含不同的QoS流(flow)，在MBS PDU会话层(level)有一层核心网(CN)隧道(tunnel)SN号，在每个QoS流粒度还可以有一级CN SN号。
对于不同的基站或小区来说，为了要获得统一的PDCP SN，最简单且没有额外开销的方式，就是令PDCP SN＝CN SN，为了实现这种关系，需要将CN SN的数据流和MRB之间进行一一映射，即将一个MBS PDU会话的所有数据映射到一个MRB上，该MRB的PDCP SN＝PDU会话层CN SN，或者一个QoS流和一个MRB之间一对一映射，该MRB的PDCP SN＝QoS流层CN SN，这两种映射方式都可以确保PDCP SN在不同小区之间的同步。
当一个MBS PDU会话支持的最大MRB个数和最大QoS流个数相等时， 可以很容易的实现QoS流和MRB之间的一一映射，从而对于每个MRB PDCP SN＝QoS流层CN SN，对每个MRB都实现跨小区的PDCP SN同步，继而可以进行无损接收；
当一个MBS PDU会话支持的最大MRB个数小于最大QoS流个数时，此时，意味着QoS流和MRB之间一定存在多对一映射，则网络侧可以根据算法，将需要无损接收的QoS流和MRB之间的一对一映射，从而实现PDCP SN跨小区同步，而对于其它不需要无损接收的QoS流可以多对一映射到同一个MRB，放弃PDCP SN同步；或者当需要无损接收的QoS流过多，仍旧不能全部支持时，可以根据QoS流的优先级，将高优先级的需要无损接收的QoS流与MRB之间一一映射，而将其它低优先级的需要无损接收的QoS流和其它不需要无损接收的QoS流维持到MRB的多对一映射，放弃PDCP SN同步。
当然，MBS PDU会话支持的最大MRB个数和最大QoS流个数相等时，网络侧也可以根据需要，将一些不需要无损接收的QoS流多对一映射到一个MRB上，以减少MRB个数和复杂度。
由于多播业务发生PTP路径和PTM路径的转换并不涉及小区的切换，是在同一小区中，只是传输多播业务的路径发生了转换，此时，重配置信息中不包括：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息。即，可选的，若多播业务的路径需要发生转换，网络侧发送的所述重配置信息包括以下至少一项：用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息。
本申请实施例中，可选的，若执行小区切换，所述第二指示信息包括以下至少一项：
所述终端是否需要进行PDCP层的重建的指示信息；
所述终端是否需要进行PDCP层的数据恢复的指示信息；
所述终端对PDCP层执行确认模式(Acknowledged Mode，AM)或非确认模式(Unacknowledged Mode，UM)操作的指示信息；
所述终端是否需要进行PDCP层的复位操作、释放(release)或新建操作的指示信息；
所述终端的PDCP SN接收状态变量是否需要保持的指示信息；
所述终端在接入所述目标小区之后是否需要在进行PDCP状态报告上报的指示信息。
本申请实施例中，可选的，若执行多播业务的路径切换，所述第二指示信息包括以下至少一项：
所述终端是否需要进行PDCP层的数据恢复的指示信息；
所述终端是否需要进行PDCP状态报告上报的指示信息。
本申请实施例中，可选的，所述方法还包括：
若所述多播业务或所述多播业务的目标MRB的重配置信息中配置了PTP RLC实体，且所述PTP RLC实体的模式为RLC AM，默认所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步；
和/或
若重配置前和重配置后所述多播业务的QoS流和MRB之间均为一对一的映射关系，默认所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步。
本申请实施例中，可选的，根据所述重配置信息执行对应的层二处理包括以下至少一项：
对PDCP层进行重建；
对PDCP层进行数据恢复；
对PDCP层进行复位、释放或新建；
对PDCP层执行AM或UM操作；
将重配置前和重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
在所述多播业务的目标PTP路径上发送PDCP状态报告上报；
对RLC层进行复位、释放或新建。
本申请实施例中，由于多播业务的MRB可能存在多种路径的各种组合配置，例如，只使用PTM路径传输，只使用PTP路径传输，或者，既使用PTM路径传输又使用PTP路径传输，因而，网络侧需要显示或者隐式指示终端，对应的PDCP层应该执行AM还是UM操作。
所谓显式指示，是指网络侧通过显示指令指示终端PDCP层执行AM或UM操作。例如，通过1bit明确指示目标小区和源小区的多播业务或者所述多播业务的目标MRB的PDCP SN是否同步。
而隐式指示，是指终端可以通过RLC层的重配置信息，确定PDCP层执行AM或UM操作。
通过显式指示的方式更加灵活，而通过隐式指示的方式无额外开销。
即，本申请实施例中，可选的，对PDCP层执行AM或UM操作包括：
根据所述重配置信息中的终端对PDCP层执行AM或UM操作的指示信息，对PDCP层执行AM或UM操作(即显式指示)；
或者
根据所述重配置信息中的RLC层的重配置信息，对PDCP层执行AM或UM操作(即隐式指示)。
本申请实施例中，可选的，根据所述重配置信息中的RLC层的重配置信息，对PDCP层执行AM或UM操作包括以下至少一项：
若所述重配置信息中指示为所述多播业务的目标MRB只配置了PTP RLC实体或者PTM RLC实体(即只配置了PTP leg或只配置了PTM leg)，且配置的RLC实体的模式为RLC AM，对PDCP层执行AM操作；
若所述重配置信息中指示为所述多播业务的目标MRB只配置了PTP RLC实体或者PTM RLC实体(即只配置了PTP leg或只配置了PTM leg)，且配置的RLC实体的模式为RLC UM，对PDCP层执行UM操作；
若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和PTM RLC实体(即同时配置了PTP leg和PTM leg)，且PTP RLC实体和PTM RLC实体的模式均为RLC AM，对PDCP层执行AM操作；
若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和PTM RLC实体(即同时配置了PTP leg和PTM leg)，且PTP RLC实体和PTM RLC实体的模式均为RLC UM，对PDCP层执行UM操作；
若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和PTM RLC实体(即同时配置了PTP leg和PTM leg)，且PTP RLC实体的模式为RLC AM，PTM RLC实体的模式为RLC UM，对PDCP层执行AM或UM操作。
本申请实施例中，可选的，根据所述重配置信息执行对应的层二处理包括以下至少一项：
1)对于PDCP AM实体，若所述第二指示信息指示PDCP SN接收状态变量不需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后不同步，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
本申请实施例中，重配置前和重配置后并不是所有情况都能达到PDCP SN同步，或者有些情况不需要进行PDCP SN同步，则在这样的情况下，也需要规范UE的L2层处理行为，尽量确保连续接收。
举例来说，将从源小区接收的多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交，例如接收的数据的PDCP SN为0-5，7，8，10， 相当于6和9是缺失(missing)，将0-5顺序递交高层，7-10放在接收缓存(buffer)中缓存，等待6和9。当接收到小区切换指令，或者，多播业务的路径切换指令，将当前接收缓存中的数据(7，8，10)也按升序递交高层，然后将所述多播业务的PDCP接收状态变量复位为初始值，开始目标小区的所述多播业务的数据的接收，并按照PDCP SN进行排序，按照PDCP SN的升序递交给高层。
2)对于PDCP AM实体，若所述第二指示信息指示PDCP SN接收状态变量需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步，保留所述多播业务的PDCP SN接收状态变量和接收缓存的数据，将重配置前和重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
对于UE来说，如果重配置后支持PDCP SN同步，则UE在重配置前的PDCP SN接收状态变量和接收缓存的数据可以继续保留，将重配置前和重配置后接收的所述多播业务的数据，按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，例如在源小区接收的数据的PDCP SN＝0，1，2，4，5，在目标小区接收到数据的PDCP SN＝3，4，5，6……，则UE判断目标小区的4，5是重复接收，3刚好补足了缺口(gap)，因此将PDCP SN＝0-6排序并按升序递交高层，实现了无损操作。
3)对于PDCP AM实体，若所述第二指示信息指示所述终端需要进行PDCP状态报告上报，根据当前的PDCP接收情况生成PDCP状态报告并上报。
本申请施例中，可以采用第一次缺失计数(first missing Count，FMC)+位图(bitmap)方式上报PDCP状态报告，例如FMC＝10，bitmap＝11110000，意味着PDCP SN＝0-9，11-14正确接收，PDCP SN＝10，15-18没有正确接收。
本申请实施例中，网络侧接收到UE的PDCP状态报告，可以使用PTP leg 对UE缺失的数据包进行重新传输，补足接收缺口(gap)。例如，网络侧PTM继续按照当前的情况进行发送，UE在目标PTM leg接收到第一个数据包SN＝19，网络侧再使用PTP leg为UE传输SN＝10，15-18这几个数据包，继而UE就可以对所有数据包进行按序排序，并按照升序递交高层。
本申请实施例中，可选的，根据所述重配置信息执行对应的层二处理包括以下至少一项：
1)对于PDCP UM实体，若所述第二指示信息指示PDCP SN接收状态变量不需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后不同步，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
本申请实施例中，重配置前和重配置后并不是所有情况都能达到PDCP SN同步，或者有些情况不需要进行PDCP SN同步，则在这样的情况下，也需要规范UE的L2层处理行为，尽量确保连续接收。
2)对于PDCP UM实体，若所述第二指示信息指示PDCP SN接收状态变量需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步，保留所述多播业务的PDCP SN接收状态变量和接收缓存的数据，将重配置前和重配置后接收的所述多播业务的数据，按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
3)对于PDCP UM实体，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层。
即，PDCP UM实体不需要考虑PDCP SN同步，仍旧将所述多播业务的 PDCP接收状态变量复位为初始值(进行目标小区的PDCP UM实体清零)，将重配置前接收数据按照现有的升序递交高层，之后对重配置后的数据继续进行自己的PDCP SN排序，相当于重配置前和重配置后各自排序，重配置前的数据先递交高层，后续重配置后的数据递交高层。
本申请实施例中，对于PDCP UM实体，没有PDCP状态报告上报机制，因此网络侧无法知道UE的接收情况，只能依赖于网络侧实现，例如源小区接收状态为PDCP SN＝0-10，12-15正确接收，UE接入目标小区之后，接收PDCP SN＝11，12，13……，UE可以将重复包进行删除，缺口进行补足，顺序递交到高层。
本申请实施例中，可选的，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层包括：以重配置后接收的第一个PDCP SN加1作为PDCP接收窗口的上边界变量，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层。
本申请实施例中，可选的，根据所述重配置信息执行对应的层二处理包括：
若所述第二指示信息指示所述终端需要进行RLC层的复位、释放或新建，执行以下至少一项：
1)RLC实体复位、释放或新建；
对于RLC AM实体(只能是PTP leg)，因为这个PTP leg是UE专用(specific)的，因此网络侧可以独立维护UE的状态变量，即从PDCP SN＝0，1，2……这样的顺序开始发送，终端按照现有的RLC AM接收实体行为进行接收；
2)对于RLC UM模式的PTM RLC实体，因为PTM leg是所有UE公共的，因此网络侧不可能根据新加入的UE来进行状态变量调整，而可以按照已有的PTM leg的发送情况，继续进行例如SN＝100，101，102……这样当前顺序继续发送，则新加入的UE将接收的第一个RLC SN加1设置为RLC  UM接收窗口的上边界；
3)对于RLC UM模式的PTP RLC实体，因为这个PTP leg是UE专用(specific)的，因此网络侧可以独立维护UE的状态变量，即从PDCP SN＝0，1，2……这样的顺序开始发送，终端可以按照现有的RLC AM接收实体行为进行接收，或者，将接收的第一个RLC SN加1设置为RLC UM接收窗口的上边界。
本申请实施例中，可选的，对PDCP层进行重建包括：
1)对于PDCP层执行RLC AM对应的重建，其行为就是现有的PDCP SN接收状态变量保持；
2)PDCP AM重建，包括头压缩的复位和安全更新，因为要开始使用目标小区的头压缩过程以及目标小区的安全参数；
3)PDCP UM重建，UE会将所有PDCP SN接收状态变量复位，但如果支持了PDCP SN同步，则在重配置后的PDCP UM重建也可以执行类似AM的PDCP SN接收状态变量保持，便于重配置前和中配置后的数据进行PDCP SN排序。默认的重建行为就是清零全部状态，与新建一个实体类似。
本申请实施例中，可选的，所述终端进行PDCP层的数据恢复(data recovery)操作包括：
1)对于PDCP层执行RLC AM对应的数据恢复，其行为就是PDCP SN接收状态变量保持，即与上述PDCP SN同步的指示达到类似的效果；
2)PDCP UM数据恢复，UE会将所有PDCP SN接收状态变量复位，但如果支持了PDCP SN同步，则在重配置后的PDCP UM重建也可以执行类似AM的PDCP SN接收状态变量保持，便于重配置前和中配置后的数据进行PDCP SN排序。
3)PDCP AM/UM数据恢复的指示，不包括头压缩的复位和安全更新，多用于PDCP实体没变的情况，例如路径转换或者本小区同步重配置等。
本申请实施例中，可选的，所述终端进行PDCP层的复位、释放或新建包括：将源小区的PDCP实体全部清零，或者释放掉现有PDCP实体，重新 再从初始化状态建立一个新的PDCP实体。主要应对的是，例如目标小区和源小区没有保持PDCP SN同步，因此源小区的PDCP SN变量接收状态保持没有任何意义，也无法进行排序，因此在目标小区清零重来。例如虽然是RLC AM的多播业务，但由于优先级较低，并没有被分配QoS流到MRB的一一映射，故而无法保持PDCP SN同步。
本申请实施例中，终端执行的RLC层操作包括：所述终端执行RLC复位或者释放或新建。由于在不同小区，RLC层有不同的调度方式，RLC层分段和UM SN分配(allocation)完全不一样，因此源小区的RLC实体必须释放或者复位，在目标小区重新清零或者建一个新的RLC实体。跨小区情况，针对PTM leg和PTP leg，都需要RLC清零。
本申请实施例中，UE在同一个小区内，并没有发生服务小区变更，但由于多播业务的配置变化或者路径转换，也会有需要进行连续接收的特殊操作。本例以路径转换为例，进行说明，其它情况类似。
本申请实施例中，可选的，若多播业务发生路径转换，根据所述重配置信息执行对应的层二处理包括以下至少一项：
1)对于PDCP实体，因为是在同一个小区之内的操作，因此PDCP实体是保持不变的，PDCP实体的SN状态，头压缩和安全等，都是继续保持的；
2)对于PDCP UM实体，由于不存在反馈通路，因此没有可以增强的地方，对于UE来说，按照转换后的路径进行所述多播业务的数据的接收，并在PDCP实体进行PDCP SN重复检测和重排序操作，按照PDCP SN升序递交至高层；
3)对于PDCP AM实体，由于具有PTP leg且配置为RLC AM，因此可以增强的内容在于：若转换后的路径中包含激活的RLC AM模式的PTP RLC实体，触发PDCP状态报告上报；
4)对于PDCP AM实体，若路径转换指示通过层一(L1)信令或者MAC CE发送，物理层或者MAC层接收到所述路径转换指示并解码之后，通过层间接口告知PDCP层，PDCP层按照所述路径转换指示中的激活的接收实体进行数据接收。
在多播业务路径转化的过程中，PTP RLC实体和PTM RLC实体，不需要有影响，按照各自实体现有的行为继续进行即可。
本申请实施例中，可选的，触发PDCP状态报告上报包括以下之一：
1)在PDCP状态报告触发时，根据当前的PDCP接收情况生成PDCP状态报告并上报，不需要进行混合自动重传请求(Hybrid automatic repeat request，HARQ)进程定时器的等待，即当前FMC+bitmap，只要某PDCP SN在当前时刻没有正确接收，则直接在bitmap中设置为0，意思是未正确接收；
2)在PDCP状态报告触发时，启动HARQ进程定时器，在HARQ进程定时器超时之后，根据PDCP接收情况生成PDCP状态报告并上报。
终端可以在接收到路径转换信令时，触发PDCP状态报告，但由于目前一个或者多个PDCP PDU有可能正在进行HARQ进程操作(process operation)，例如HARQ retx等，也就是说，当前这个PDCP PDU有可能在后续的HARQ重传中获得成功，因此UE可以在PDCP状态报告触发时，先启动一个HARQ进程定时器，HARQ进程定时器的具体取值可以是由网络侧配置或者标准规定或者UE实现选取，等HARQ进程定时器超时之后，再根据当时的接收状态，决定FMC+bitmap数值，进行上报；在这种情况下，相较于前一种立即上报的方式，可以有效避免UE错误上报NACK，即在触发上报(reporting trigger)时没有正确接收，但在HARQ进程定时器期间通过HARQ重传获得了正确接收，这样这个PDCP SN在HARQ进程定时器超时之后就可以作为ACK上报，避免了冗余重传。
请参考图4，本申请实施例还提供一种多播业务的配置方法，由网络侧设备执行，包括：
步骤41：向终端发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息。
本申请实施例中，可选的，若执行小区切换，所述第二指示信息包括以下至少一项：
所述终端是否需要进行PDCP层的重建的指示信息；
所述终端是否需要进行PDCP层的数据恢复的指示信息；
所述终端对PDCP层执行AM或UM操作的指示信息；
所述终端是否需要进行PDCP层的复位、释放或新建的指示信息；
所述终端的PDCP SN接收状态变量是否需要保持的指示信息；
所述终端是否需要在接入所述目标小区之后是否需要进行PDCP状态报告上报的指示信息。
本申请实施例中，可选的，若执行多播业务的路径切换，所述第二指示信息包括以下至少一项：
所述终端是否需要进行PDCP层的数据恢复的指示信息；
所述终端是否需要进行PDCP状态报告上报的指示信息。
一般情况下，网络侧设备会优先针对QoS需求中对误块率要求较高的数据流，例如误块率要求低于10^-5或者10^-6，进行无损接收的配置。另外，一般还会同时配置PTP leg，且PTP leg配置为RLC AM。
针对小区切换的场景，为了实现无损接收，在目标小区必须配置一个PTP leg，且PTP leg配置为RLC AM，同时如果目标小区中还有其它的用户接收相同的多播业务，还需要同时配置PTM leg，PTP leg可以配置为RLC UM，以进行点对多点同时向多个终端发送多播业务的数据，将具有很高的资源效率。目标小区对多播业务的重配置信息，可以通过接口信令(Xn接口信令)发送给源小区，源小区再通过切换信令发送给切换的终端。
本申请实施例中，对于源小区和目标小区来说，可以通过Xn接口的交互来判断，是否满足PDCP SN同步，例如源小区和目标小区通过显式的过程，交互TMGI业务对应的某一个MRB的PDCP SN是否同步，或者源小区可以通过隐式的过程，判断MRB是否支持PDCP SN同步，例如源小区和目标小区对于某一个QoS流和MRB之间都是配置了一对一的映射关系，因此 就认为支持PDCP SN同步。
本申请实施例中，可选的，所述终端是否需要进行PDCP层的重建的指示信息包括：
1)对于PDCP层执行RLC AM对应的重建的指示，其行为就是PDCP SN接收状态变量保持，即与上述PDCP SN同步的指示达到类似的效果；
2)PDCP AM重建的指示，还包括头压缩的复位和安全更新，因为要开始使用目标小区的头压缩过程以及目标小区的安全参数；
3)PDCP UM重建的指示。
本申请实施例中，可选的，所述终端是否需要进行PDCP层的数据恢复(data recovery)操作的指示信息包括：
1)对于PDCP层执行RLC AM对应的数据恢复的指示，其行为也是现有的接收状态和SN变量保持，即与上述PDCP SN sync指示达到类似的效果，从这个效果上可以二选一；
2)PDCP UM数据恢复的指示；
3)PDCP AM/UM数据恢复的指示，不包括头压缩的复位和安全更新，多用于PDCP实体没变的情况，例如路径转换或者本小区同步重配置等。
本申请实施例中，可选的，对于终端是否需要进行PDCP状态报告上报，PDCP状态报告是一个上行反馈过程，因此必须有PTP leg，且PTP leg配置了RLC AM，在此PTP leg上传输PDCP状态报告；如果目标PDCP为UM，则不能配置反馈PDCP状态报告，因为没有上行通路进行承载和传输。
本申请实施例中，用于指示所述终端执行的RLC层操作的第三指示信息包括：用于指示所述终端是否执行RLC复位或者释放或新建的指示。
本申请实施例中，如果一个MRB仅有RLC UM的leg，即PTM配置为RLC UM，或者PTM和PTP配置为RLC UM，在PDCP SN同步的情况下，也能实现一定程度的连续接收。
需要说明的是，本申请实施例提供的多播业务的接收方法，执行主体可以为多播业务的接收装置，或者，该多播业务的接收装置中的用于执行多播 业务的接收方法的控制模块。本申请实施例中以多播业务的接收装置执行多播业务的接收方法为例，说明本申请实施例提供的多播业务的接收装置。
请参考图5，本申请实施例还提供一种多播业务的接收装置50，包括：
接收模块51，用于接收网络侧设备发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息；
执行模块52，用于根据所述重配置信息执行对应的层二处理。
可选的，所述第二指示信息包括以下至少一项：
所述终端是否需要进行PDCP层的重建的指示信息；
所述终端是否需要进行PDCP层的数据恢复的指示信息；
所述终端对PDCP层执行AM或UM操作的指示信息；
所述终端是否需要进行PDCP层的复位、释放或新建的指示信息；
所述终端的PDCP SN接收状态变量是否需要保持的指示信息；
所述终端是否需要进行PDCP状态报告上报的指示信息。
可选的，所述执行模块52，用于根据所述重配置信息执行对应的层二处理包括以下至少一项：
对PDCP层进行重建；
对PDCP层进行数据恢复；
对PDCP层进行复位、释放或新建；
对PDCP层执行AM或UM操作；
将重配置前和重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为 初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
在所述多播业务的目标PTP路径上发送PDCP状态报告上报；
对RLC层进行复位、释放或新建。
可选的，所述执行模块52，用于根据所述重配置信息中的终端对PDCP层执行AM或UM操作的指示信息，对PDCP层执行AM或UM操作；
或者
所述执行模块52，用于根据所述重配置信息中的RLC层的重配置信息，对PDCP层执行AM或UM操作。
可选的，所述执行模块52，还用于执行以下至少一项：
若所述重配置信息中指示为所述多播业务的目标MRB只配置了PTP RLC实体或者PTM RLC实体，且配置的RLC实体的模式为RLC AM，对PDCP层执行AM操作；
若所述重配置信息中指示为所述多播业务的目标MRB只配置了PTP RLC实体或者PTM RLC实体，且配置的RLC实体的模式为RLC UM，对PDCP层执行UM操作；
若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和PTM RLC实体，且PTP RLC实体和PTM RLC实体的模式均为RLC AM，对PDCP层执行AM操作；
若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和PTM RLC实体，且PTP RLC实体和PTM RLC实体的模式均为RLC UM，对PDCP层执行UM操作；
若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和PTM RLC实体，且PTP RLC实体的模式为RLC AM，PTM RLC实体的模式为RLC UM，对PDCP层执行AM或UM操作。
可选的，所述多播业务的接收装置还包括：
第一处理模块，用于若所述多播业务或所述多播业务的目标MRB的重 配置信息中配置了PTP RLC实体，且所述PTP RLC实体的模式为RLC AM，默认所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步；
和/或
第二处理模块，用于若重配置前和重配置后所述多播业务的QoS流和MRB之间均为一对一的映射关系，默认所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步。
可选的，所述执行模块52，用于执行以下至少一项：
对于PDCP AM实体，若所述第二指示信息指示PDCP SN接收状态变量不需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后不同步，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
对于PDCP AM实体，若所述第二指示信息指示PDCP SN接收状态变量需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步，保留所述多播业务的PDCP SN接收状态变量和接收缓存的数据，将重配置前和重配置后接收的所述多播业务的数据，按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
对于PDCP AM实体，若所述第二指示信息指示所述终端需要进行PDCP状态报告上报，根据当前的PDCP接收情况生成PDCP状态报告并上报。
可选的，所述执行模块52，用于执行以下至少一项：
对于PDCP UM实体，若所述第二指示信息指示PDCP SN接收状态变量不需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后不同步，将重配置前接收的 所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
对于PDCP UM实体，若所述第二指示信息指示PDCP SN接收状态变量需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步，保留所述多播业务的PDCP SN接收状态变量和接收缓存的数据，将重配置前和重配置后接收的所述多播业务的数据，按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
对于PDCP UM实体，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层。
可选的，所述执行模块52，还用于以重配置后接收的第一个PDCP SN加1作为PDCP接收窗口的上边界变量，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层。
可选的，所述执行模块52，还用于若所述第二指示信息指示所述终端需要进行RLC层的复位、释放或新建，执行以下至少一项：
RLC实体复位、释放或新建；
对于PTM RLC实体，将接收的第一个RLC SN加1设置为RLC UM接收窗口的上边界。
可选的，若多播业务发生路径转换，所述执行模块52，用于执行以下至少一项：
对于PDCP UM实体，按照转换后的路径进行所述多播业务的数据的接收，并在PDCP实体进行PDCP SN重复检测和重排序操作，按照PDCP SN升序递交至高层；
对于PDCP AM实体，若转换后的路径中包含激活的RLC AM模式的PTP RLC实体，触发PDCP状态报告上报；
对于PDCP AM实体，若路径转换指示通过层一信令或者MAC CE发送，物理层或者MAC层接收到所述路径转换指示并解码之后，通过层间接口告知PDCP层，PDCP层按照所述路径转换指示中的激活的接收实体进行数据接收。
可选的，所述执行模块52，还用于执行以下之一：
在PDCP状态报告触发时，根据当前的PDCP接收情况生成PDCP状态报告并上报；
在PDCP状态报告触发时，启动HARQ进程定时器，在HARQ进程定时器超时之后，根据PDCP接收情况生成PDCP状态报告并上报。
本申请实施例中的多播业务的接收装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的多播业务的接收装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的多播业务的接收装置能够实现图3的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，本申请实施例提供的多播业务的配置方法，执行主体可以为多播业务的配置装置，或者，该多播业务的配置装置中的用于执行多播业务的配置方法的控制模块。本申请实施例中以多播业务的配置装置执行多播业务的配置方法为例，说明本申请实施例提供的多播业务的配置装置。
请参考图6，本申请实施例还提供一种多播业务的配置装置60，包括：
发送模块61，用于向终端发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息。
可选的，所述第二指示信息包括以下至少一项：
所述终端是否需要进行PDCP层的重建的指示信息；
所述终端是否需要进行PDCP层的数据恢复的指示信息；
所述终端对PDCP层执行AM或UM操作的指示信息；
所述终端是否需要进行PDCP层的复位、释放或新建的指示信息；
所述终端的PDCP SN接收状态变量是否需要保持的指示信息；
所述终端是否需要进行PDCP状态报告上报的指示信息。
本申请实施例提供的多播业务的接收装置能够实现图4的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
如图7所示，本申请实施例还提供一种通信设备70，包括处理器71，存储器72，存储在存储器72上并可在所述处理器71上运行的程序或指令，例如，该通信设备70为终端时，该程序或指令被处理器71执行时实现上述多播业务的接收方法实施例的各个过程，且能达到相同的技术效果。该通信设备70为网络侧设备时，该程序或指令被处理器71执行时实现上述多播业务的配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
图8为实现本申请实施例的一种终端的硬件结构示意图。该终端80包括但不限于：射频单元81、网络模块82、音频输出单元83、输入单元84、传感器85、显示单元86、用户输入单元87、接口单元88、存储器89、以及处理器810等部件。
本领域技术人员可以理解，终端80还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器810逻辑相连，从而通过 电源管理系统实现管理充电、放电、以及功耗管理等功能。图8中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元84可以包括图形处理器(Graphics Processing Unit，GPU)841和麦克风842，图形处理器841对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元86可包括显示面板861，可以采用液晶显示器、有机发光二极管等形式来配置显示面板861。用户输入单元87包括触控面板871以及其他输入设备872。触控面板871，也称为触摸屏。触控面板871可包括触摸检测装置和触摸控制器两个部分。其他输入设备872可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元81将来自网络侧设备的下行数据接收后，给处理器810处理；另外，将上行的数据发送给网络侧设备。通常，射频单元81包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器89可用于存储软件程序或指令以及各种数据。存储器89可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器89可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器810可包括一个或多个处理单元；可选的，处理器810可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界 面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器810中。
其中，射频单元81，用于接收网络侧设备发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层重配置信息，以及，PDCP层重配置信息；
处理器810，用于根据所述重配置信息执行对应的层二处理。
可选的，所述第二指示信息包括以下至少一项：
所述终端是否需要进行PDCP层的重建的指示信息；
所述终端是否需要进行PDCP层的数据恢复的指示信息；
所述终端对PDCP层执行AM或UM操作的指示信息；
所述终端是否需要进行PDCP层的复位、释放或新建的指示信息；
所述终端的PDCP SN接收状态变量是否需要保持的指示信息；
所述终端是否需要进行PDCP状态报告上报的指示信息。
可选的，所述处理器810用于执行以下至少一项：
对PDCP层进行重建；
对PDCP层进行数据恢复；
对PDCP层进行复位、释放或新建；
对PDCP层执行AM或UM操作；
将重配置前和重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
在所述多播业务的目标PTP路径上发送PDCP状态报告上报；
对RLC层进行复位、释放或新建。
可选的，所述处理器810用于根据所述重配置信息中的终端对PDCP层执行AM或UM操作的指示信息，对PDCP层执行AM或UM操作；
或者
所述处理器810用于根据所述重配置信息中的RLC层的重配置信息，对PDCP层执行AM或UM操作。
可选的，所述处理器810用于执行以下至少一项：
若所述重配置信息中指示为所述多播业务的目标MRB只配置了PTP RLC实体或者PTM RLC实体，且配置的RLC实体的模式为RLC AM，对PDCP层执行AM操作；
若所述重配置信息中指示为所述多播业务的目标MRB只配置了PTP RLC实体或者PTM RLC实体，且配置的RLC实体的模式为RLC UM，对PDCP层执行UM操作；
若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和PTM RLC实体，且PTP RLC实体和PTM RLC实体的模式均为RLC AM，对PDCP层执行AM操作；
若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和PTM RLC实体，且PTP RLC实体和PTM RLC实体的模式均为RLC UM，对PDCP层执行UM操作；
若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和PTM RLC实体，且PTP RLC实体的模式为RLC AM，PTM RLC实体的模式为RLC UM，对PDCP层执行AM或UM操作。
可选的，所述处理器810用于执行若所述多播业务或所述多播业务的目标MRB的重配置信息中配置了PTP RLC实体，且所述PTP RLC实体的模式为RLC AM，默认所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步；
和/或
所述处理器810用于执行若重配置前和重配置后所述多播业务的QoS流和MRB之间均为一对一的映射关系，默认所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步。
可选的，所述处理器810用于执行以下至少一项：
对于PDCP AM实体，若所述第二指示信息指示PDCP SN接收状态变量不需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后不同步，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
对于PDCP AM实体，若所述第二指示信息指示PDCP SN接收状态变量需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步，保留所述多播业务的PDCP SN接收状态变量和接收缓存的数据，将重配置前和重配置后接收的所述多播业务的数据，按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
对于PDCP AM实体，若所述第二指示信息指示所述终端需要进行PDCP状态报告上报，根据当前的PDCP接收情况生成PDCP状态报告并上报。
可选的，所述处理器810用于执行以下至少一项：
对于PDCP UM实体，若所述第二指示信息指示PDCP SN接收状态变量不需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后不同步，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升 序递交给高层；
对于PDCP UM实体，若所述第二指示信息指示PDCP SN接收状态变量需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步，保留所述多播业务的PDCP SN接收状态变量和接收缓存的数据，将重配置前和重配置后接收的所述多播业务的数据，按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
对于PDCP UM实体，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层。
可选的，所述处理器810用于执行以重配置后接收的第一个PDCP SN加1作为PDCP接收窗口的上边界变量，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层。
可选的，所述处理器810用于执行若所述第二指示信息指示所述终端需要进行RLC层的复位、释放或新建，执行以下至少一项：
RLC实体复位、释放或新建；
对于RLC UM实体，将接收的第一个RLC SN加1设置为RLC UM接收窗口的上边界。
可选的，所述处理器810用于执行以下至少一项：
对于PDCP UM实体，按照转换后的路径进行所述多播业务的数据的接收，并在PDCP实体进行PDCP SN重复检测和重排序操作，按照PDCP SN升序递交至高层；
对于PDCP AM实体，若转换后的路径中包含激活的RLC AM模式的PTP RLC实体，触发PDCP状态报告上报；
对于PDCP AM实体，若路径转换指示通过层一信令或者MAC CE发送，物理层或者MAC层接收到所述路径转换指示并解码之后，通过层间接口告 知PDCP层，PDCP层按照所述路径转换指示中的激活的接收实体进行数据接收。
可选的，所述处理器810用于执行以下之一：
在PDCP状态报告触发时，根据当前的PDCP接收情况生成PDCP状态报告并上报；
在PDCP状态报告触发时，启动HARQ进程定时器，在HARQ进程定时器超时之后，根据PDCP接收情况生成PDCP状态报告并上报。
本申请实施例还提供了一种网络侧设备。如图9所示，该网络设备900包括：天线91、射频装置92、基带装置93。天线91与射频装置92连接。在上行方向上，射频装置92通过天线91接收信息，将接收的信息发送给基带装置93进行处理。在下行方向上，基带装置93对要发送的信息进行处理，并发送给射频装置92，射频装置92对收到的信息进行处理后经过天线91发送出去。
上述频带处理装置可以位于基带装置93中，以上实施例中网络侧设备执行的方法可以在基带装置93中实现，该基带装置93包括处理器94和存储器95。
基带装置93例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图9所示，其中一个芯片例如为处理器94，与存储器95连接，以调用存储器95中的程序，执行以上方法实施例中所示的网络设备操作。
该基带装置93还可以包括网络接口96，用于与射频装置92交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
具体地，本申请实施例的网络侧设备还包括：存储在存储器95上并可在处理器94上运行的指令或程序，处理器94调用存储器95中的指令或程序执行图4所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述多播业务的接收方法或者 多播业务的配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现上述多播业务的接收方法或者多播业务的配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种程序产品，所述程序产品存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现上述多播业务的接收方法或者多播业务的配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (27)

  1. 一种多播业务的接收方法，由终端执行，包括：
    接收网络侧设备发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标无线承载MRB的分组数据汇聚协议序列号PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的无线链路控制RLC层操作的第三指示信息，RLC层配置信息，以及，PDCP层配置信息；
    根据所述重配置信息执行对应的层二处理。
  2. 根据权利要求1所述的方法，其中，所述第二指示信息包括以下至少一项：
    所述终端是否需要进行PDCP层的重建的指示信息；
    所述终端是否需要进行PDCP层的数据恢复的指示信息；
    所述终端对PDCP层执行确认模式AM或非确认模式UM操作的指示信息；
    所述终端是否需要进行PDCP层的复位、释放或新建的指示信息；
    所述终端的PDCP SN接收状态变量是否需要保持的指示信息；
    所述终端是否需要进行PDCP状态报告上报的指示信息。
  3. 根据权利要求1所述的方法，其中，根据所述重配置信息执行对应的层二处理包括以下至少一项：
    对PDCP层进行重建；
    对PDCP层进行数据恢复；
    对PDCP层进行复位、释放或新建；
    对PDCP层执行AM或UM操作；
    将重配置前和重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    在所述多播业务的目标点对点PTP路径上发送PDCP状态报告上报；
    对RLC层进行复位、释放或新建。
  4. 根据权利要求3所述的方法，其中，对PDCP层执行AM或UM操作包括：
    根据所述重配置信息中的终端对PDCP层执行AM或UM操作的指示信息，对PDCP层执行AM或UM操作；
    或者
    根据所述重配置信息中的RLC层配置信息，对PDCP层执行AM或UM操作。
  5. 根据权利要求4所述的方法，其中，根据所述重配置信息中的RLC配置信息，对PDCP层执行AM或UM操作包括以下至少一项：
    若所述重配置信息中指示为所述多播业务的目标MRB只配置了PTP RLC实体或者PTM RLC实体，且配置的RLC实体的模式为RLC AM，对PDCP层执行AM操作；
    若所述重配置信息中指示为所述多播业务的目标MRB只配置了PTP RLC实体或者PTM RLC实体，且配置的RLC实体的模式为RLC UM，对PDCP层执行UM操作；
    若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和点对多点PTM RLC实体，且PTP RLC实体和PTM RLC实体的模式均为RLC AM，对PDCP层执行AM操作；
    若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和PTM RLC实体，且PTP RLC实体和PTM RLC实体的模式均为RLC UM，对PDCP层执行UM操作；
    若所述重配置信息中指示为所述多播业务的目标MRB同时配置了PTP RLC实体和PTM RLC实体，且PTP RLC实体的模式为RLC AM，PTM RLC实体的模式为RLC UM，对PDCP层执行AM或UM操作。
  6. 根据权利要求3所述的方法，其中，根据所述重配置信息执行对应的层二处理包括以下至少一项：
    对于PDCP AM实体，若所述第二指示信息指示PDCP SN接收状态变量不需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后不同步，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    对于PDCP AM实体，若所述第二指示信息指示PDCP SN接收状态变量需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步，保留所述多播业务的PDCP SN接收状态变量和接收缓存的数据，将重配置前和重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    对于PDCP AM实体，若所述第二指示信息指示所述终端需要进行PDCP状态报告上报，根据当前的PDCP接收情况生成PDCP状态报告并上报。
  7. 根据权利要求3所述的方法，其中，根据所述重配置信息执行对应的层二处理包括以下至少一项：
    对于PDCP UM实体，若所述第二指示信息指示PDCP SN接收状态变量不需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后不同步，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后 接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    对于PDCP UM实体，若所述第二指示信息指示PDCP SN接收状态变量需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步，保留所述多播业务的PDCP SN接收状态变量和接收缓存的数据，将重配置前和重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    对于PDCP UM实体，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层。
  8. 根据权利要求6或7所述的方法，其中，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层包括：
    以重配置后接收的第一个PDCP SN加1作为PDCP接收窗口的上边界变量，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层。
  9. 根据权利要求3所述的方法，其中，根据所述重配置信息执行对应的层二处理包括：
    若所述第二指示信息指示所述终端需要进行RLC层的复位、释放或新建，执行以下至少一项：
    RLC实体复位、释放或新建；
    对于RLC UM实体，将接收的第一个RLC SN加1设置为RLC UM接收窗口的上边界。
  10. 根据权利要求3所述的方法，其中，若多播业务发生路径转换，根据所述重配置信息执行对应的层二处理包括以下至少一项：
    对于PDCP UM实体，按照转换后的路径进行所述多播业务的数据的接收，并在PDCP实体进行PDCP SN重复检测和重排序操作，按照PDCP SN升序递交至高层；
    对于PDCP AM实体，若转换后的路径中包含激活的RLC AM模式的PTP RLC实体，触发PDCP状态报告上报；
    对于PDCP AM实体，若路径转换指示通过层一信令或者媒体接入控制控制单元MAC CE发送，物理层或者MAC层接收到所述路径转换指示并解码之后，通过层间接口告知PDCP层，PDCP层按照所述路径转换指示中的激活的接收实体进行数据接收。
  11. 根据权利要求10所述的方法，其中，触发PDCP状态报告上报包括以下之一：
    在PDCP状态报告触发时，根据当前的PDCP接收情况生成PDCP状态报告并上报；
    在PDCP状态报告触发时，启动混合自动重传请求HARQ进程定时器，在HARQ进程定时器超时之后，根据PDCP接收情况生成PDCP状态报告并上报。
  12. 根据权利要求1所述的方法，其中，还包括：
    若所述重配置信息中配置了PTP RLC实体，且所述PTP RLC实体的模式为RLC AM，默认所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步；
    和/或
    若重配置前和重配置后所述多播业务的服务质量QoS流和MRB之间均为一对一的映射关系，默认所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步。
  13. 一种多播业务的配置方法，由网络侧设备执行，包括：
    向终端发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重 配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层配置信息，以及，PDCP层配置信息。
  14. 根据权利要求13所述的方法，其中，所述第二指示信息包括以下至少一项：
    所述终端是否需要进行PDCP层的重建的指示信息；
    所述终端是否需要进行PDCP层的数据恢复的指示信息；
    所述终端对PDCP层执行AM或UM操作的指示信息；
    所述终端是否需要进行PDCP层的复位、释放或新建的指示信息；
    所述终端的PDCP SN接收状态变量是否需要保持的指示信息；
    所述终端是否需要进行PDCP状态报告上报的指示信息。
  15. 一种多播业务的接收装置，包括：
    接收模块，用于接收网络侧设备发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层配置信息，以及，PDCP层配置信息；
    执行模块，用于根据所述重配置信息执行对应的层二处理。
  16. 根据权利要求15所述的装置，其中，
    所述执行模块，用于根据所述重配置信息执行对应的层二处理包括以下至少一项：
    对PDCP层进行重建；
    对PDCP层进行数据恢复；
    对PDCP层进行复位、释放或新建；
    对PDCP层执行AM或UM操作；
    将重配置前和重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    在所述多播业务的目标PTP路径上发送PDCP状态报告上报；
    对RLC层进行复位、释放或新建。
  17. 根据权利要求16所述的装置，其中，
    所述执行模块，用于根据所述重配置信息中的终端对PDCP层执行AM或UM操作的指示信息，对PDCP层执行AM或UM操作；
    或者
    所述执行模块，用于根据所述重配置信息中的RLC层配置信息，对PDCP层执行AM或UM操作。
  18. 根据权利要求16所述的装置，其中，
    所述执行模块，用于执行以下至少一项：
    对于PDCP AM实体，若所述第二指示信息指示PDCP SN接收状态变量不需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后不同步，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    对于PDCP AM实体，若所述第二指示信息指示PDCP SN接收状态变量需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步，保留所述多播业务的PDCP SN接收状态变量和接收缓存的数据，将重配置前和重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    对于PDCP AM实体，若所述第二指示信息指示所述终端需要进行PDCP状态报告上报，根据当前的PDCP接收情况生成PDCP状态报告并上报。
  19. 根据权利要求16所述的装置，其中，
    所述执行模块，用于执行以下至少一项：
    对于PDCP UM实体，若所述第二指示信息指示PDCP SN接收状态变量不需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后不同步，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    对于PDCP UM实体，若所述第二指示信息指示PDCP SN接收状态变量需要保持，和/或，所述第一指示信息指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后同步，保留所述多播业务的PDCP SN接收状态变量和接收缓存的数据，将重配置前和重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层；
    对于PDCP UM实体，将重配置前接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层，将所述多播业务的PDCP接收状态变量复位为初始值，将重配置后接收的所述多播业务的数据按照PDCP SN进行排序，并按照PDCP SN的升序递交给高层。
  20. 根据权利要求16所述的装置，其中，若多播业务发生路径转换，所述执行模块，用于执行以下至少一项：
    对于PDCP UM实体，按照转换后的路径进行所述多播业务的数据的接收，并在PDCP实体进行PDCP SN重复检测和重排序操作，按照PDCP SN升序递交至高层；
    对于PDCP AM实体，若转换后的路径中包含激活的RLC AM模式的PTP  RLC实体，触发PDCP状态报告上报；
    对于PDCP AM实体，若路径转换指示通过层一信令或者MAC CE发送，物理层或者MAC层接收到所述路径转换指示并解码之后，通过层间接口告知PDCP层，PDCP层按照所述路径转换指示中的激活的接收实体进行数据接收。
  21. 一种多播业务的配置装置，包括：
    发送模块，用于，向终端发送的多播业务的重配置信息，所述重配置信息包括以下至少一项：用于指示所述多播业务或者所述多播业务的目标MRB的PDCP SN在重配置前和重配置后是否同步的第一指示信息，用于指示所述终端执行的PDCP层操作的第二指示信息，用于指示所述终端执行的RLC层操作的第三指示信息，RLC层配置信息，以及，PDCP层配置信息。
  22. 一种终端，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，其中，所述程序或指令被所述处理器执行时实现如权利要求1至12任一项所述的多播业务的接收方法的步骤。
  23. 一种网络侧设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，其中，所述程序或指令被所述处理器执行时实现如权利要求13或14所述的多播业务的配置方法的步骤。
  24. 一种可读存储介质，所述可读存储介质上存储程序或指令，其中，所述程序或指令被处理器执行时实现如权利要求1至12任一项所述的多播业务的接收方法，或者实现如权利要求13或14所述的多播业务的配置方法的步骤。
  25. 一种芯片，包括处理器和通信接口，其中，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至12任一项所述的多播业务的接收方法，或者实现如权利要求13或14所述的多播业务的配置方法。
  26. 一种计算机程序产品，其中，所述程序产品被存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现如权利要求1至12任一项所述的多播业务的接收方法，或者实现如权利要求13或14所述的多播业 务的配置方法。
  27. 一种通信设备，其中，被配置为执行如权利要求1至12任一项所述的多播业务的接收方法，或者执行如权利要求13或14所述的多播业务的配置方法。
PCT/CN2022/078553 2021-03-05 2022-03-01 多播业务的接收方法、配置方法、终端及网络侧设备 WO2022184044A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22762509.2A EP4304212A1 (en) 2021-03-05 2022-03-01 Multicast service receiving method, multicast service configuration method, terminal, and network side device
US18/241,867 US20230422346A1 (en) 2021-03-05 2023-09-02 Multicast service receiving method, multicast service configuration method, terminal, and network side device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110247370.5A CN115038049B (zh) 2021-03-05 2021-03-05 多播业务的接收方法、配置方法、终端及网络侧设备
CN202110247370.5 2021-03-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/241,867 Continuation US20230422346A1 (en) 2021-03-05 2023-09-02 Multicast service receiving method, multicast service configuration method, terminal, and network side device

Publications (1)

Publication Number Publication Date
WO2022184044A1 true WO2022184044A1 (zh) 2022-09-09

Family

ID=83118440

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/078553 WO2022184044A1 (zh) 2021-03-05 2022-03-01 多播业务的接收方法、配置方法、终端及网络侧设备

Country Status (4)

Country Link
US (1) US20230422346A1 (zh)
EP (1) EP4304212A1 (zh)
CN (1) CN115038049B (zh)
WO (1) WO2022184044A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115802416A (zh) * 2021-09-10 2023-03-14 夏普株式会社 用户设备执行的方法、基站的传输方法及用户设备
WO2024077421A1 (zh) * 2022-10-09 2024-04-18 北京小米移动软件有限公司 组播业务数据的传输方法及装置、存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111866975A (zh) * 2020-05-18 2020-10-30 中兴通讯股份有限公司 切换方法及装置、信息发送方法及装置
CN111901766A (zh) * 2020-04-27 2020-11-06 中兴通讯股份有限公司 承载配置、上下文信息管理、释放方法、装置和设备
CN111901765A (zh) * 2020-04-27 2020-11-06 中兴通讯股份有限公司 模式配置方法、装置、设备和存储介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018032469A1 (en) * 2016-08-18 2018-02-22 Qualcomm Incorporated Techniques and apparatuses for sc-ptm configuration in handover signaling for service continuity
CN113411755B (zh) * 2017-12-28 2022-10-04 华为技术有限公司 一种通信方法、及相关产品

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111901766A (zh) * 2020-04-27 2020-11-06 中兴通讯股份有限公司 承载配置、上下文信息管理、释放方法、装置和设备
CN111901765A (zh) * 2020-04-27 2020-11-06 中兴通讯股份有限公司 模式配置方法、装置、设备和存储介质
CN111866975A (zh) * 2020-05-18 2020-10-30 中兴通讯股份有限公司 切换方法及装置、信息发送方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
VIVO: "Dynamic PTM PTP switch for RRC Connected UE", 3GPP DRAFT; R2-2100833, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. E-Meeting; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973930 *

Also Published As

Publication number Publication date
CN115038049A (zh) 2022-09-09
EP4304212A1 (en) 2024-01-10
CN115038049B (zh) 2024-01-23
US20230422346A1 (en) 2023-12-28

Similar Documents

Publication Publication Date Title
US20230422346A1 (en) Multicast service receiving method, multicast service configuration method, terminal, and network side device
US20230254749A1 (en) Multicast service transmission method and apparatus, and communications device
US20230171844A1 (en) Multicast service receiving method, multicast service configuration method, terminal, and network-side device
WO2022121876A1 (zh) 多播业务的确认模式传输方法、装置、设备及存储介质
US20230188950A1 (en) Communication control method
CN113938438B (zh) 数据处理方法、数据处理装置及第一终端
JP7469571B2 (ja) 通信方法、ユーザ装置、ネットワークノード、チップセット、及びプログラム
US20240187140A1 (en) 5g multicast-broadcast services (mbs) multiplexing, reliability, and power savings
US20240080935A1 (en) Communication control method and user equipment
WO2023066106A1 (zh) 数据丢弃方法、装置、终端及网络侧设备
WO2024099093A1 (zh) 数据传输方法、装置、终端、网络侧设备及系统
US20240031279A1 (en) Service data processing method and apparatus, and device
JP7481588B2 (ja) 通信方法、ユーザ装置、移動通信システム、チップセット、及びプログラム
WO2022000253A1 (en) Methods and apparatus of reliable multicast transmission with compact protocol stack
US20240022358A1 (en) Managing harq transmissions in multicast communication
WO2022198415A1 (zh) 提高mbs业务可靠性的方法及装置、终端设备、网络设备
CN117941384A (zh) 通信方法
AU2021359510A1 (en) Sn synchronization method, apparatus and device for multicast broadcast service, and readable storage medium
WO2022212731A1 (en) 5g multicast-broadcast services (mbs): multiplexing, reliability, and power savings
CN118018965A (zh) 5g多播-广播服务（mbs）：复用、可靠性和功率节省
CN115696216A (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: 22762509

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022762509

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022762509

Country of ref document: EP

Effective date: 20231005

NENP Non-entry into the national phase

Ref country code: DE