WO2023001146A1 - 多播广播业务的接收方法、发送方法、装置及设备 - Google Patents

多播广播业务的接收方法、发送方法、装置及设备 Download PDF

Info

Publication number
WO2023001146A1
WO2023001146A1 PCT/CN2022/106477 CN2022106477W WO2023001146A1 WO 2023001146 A1 WO2023001146 A1 WO 2023001146A1 CN 2022106477 W CN2022106477 W CN 2022106477W WO 2023001146 A1 WO2023001146 A1 WO 2023001146A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast broadcast
terminal
broadcast service
information
multicast
Prior art date
Application number
PCT/CN2022/106477
Other languages
English (en)
French (fr)
Inventor
刘佳敏
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2023001146A1 publication Critical patent/WO2023001146A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application belongs to the technical field of communication, and in particular relates to a receiving method, sending method, device and equipment of a multicast broadcast service.
  • LTE Long Term Evolution
  • UE User Equipment
  • a sidelink-based relay (relay) communication is proposed to expand coverage and improve power consumption.
  • the embodiment of the present application provides a multicast broadcast service receiving method, sending method, device and equipment, which can solve the problem that the remote UE cannot receive the MBS.
  • a method for receiving a multicast broadcast service including:
  • the first terminal sends the first request information to the second terminal;
  • the first terminal communicates with the second terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • a device for receiving a multicast broadcast service including:
  • a first sending module configured to send the first request information to the second terminal
  • the second terminal communicates with the first terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • a method for sending a multicast broadcast service including:
  • the first terminal communicates with the second terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • a device for sending a multicast broadcast service including:
  • the second receiving module is configured to receive the first request information of the first terminal
  • the first terminal communicates with the second terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • a method for sending a multicast broadcast service including:
  • the network device sends the MCCH to the second terminal
  • the second terminal is configured to receive first request information from the first terminal, the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service, and the first A terminal communicates with the second terminal through a side link;
  • the MCCH is used to determine multicast broadcast control information.
  • a device for sending a multicast broadcast service including:
  • a third sending module configured to send the MCCH to the second terminal
  • the second terminal is configured to receive first request information from the first terminal, the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service, and the first A terminal communicates with the second terminal through a side link;
  • the MCCH is used to determine multicast broadcast control information.
  • a terminal in a seventh aspect, includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor, when the program or instruction is executed by the processor.
  • a terminal including a processor and a communication interface, wherein the communication interface is used to send the first request information to the second terminal;
  • the second terminal communicates with the first terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • a terminal including a processor and a communication interface, where the communication interface is used to receive the first request information of the first terminal;
  • the first terminal communicates with the second terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • a network device in a tenth aspect, includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor, and the program or instruction is executed by the processor When executed, the steps of the method described in the fifth aspect are realized.
  • a network device including a processor and a communication interface, wherein the communication interface is used to send the MCCH to the second terminal;
  • the second terminal is configured to receive first request information from the first terminal, the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service, and the first A terminal communicates with the second terminal through a side link;
  • the MCCH is used to determine multicast broadcast control information.
  • a readable storage medium on which a program or an instruction is stored, and when the program or instruction is executed by a processor, the steps of the method as described in the first aspect are implemented, or The steps of the method described in the third aspect, or implementing the steps of the method described in the fifth aspect.
  • a chip in a thirteenth aspect, there is provided a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or an instruction to implement the method described in the first aspect method, or implement the method as described in the third aspect, or implement the method as described in the fifth aspect.
  • a computer program product is provided, the computer program product is stored in a non-volatile storage medium, and the computer program product is executed by at least one processor to implement the method as described in the first aspect , or implement the method as described in the third aspect, or implement the method as described in the fifth aspect.
  • a communication device configured to execute the method described in the first aspect, or execute the method described in the third aspect, or execute the method described in the fifth aspect.
  • the first terminal communicates with the second terminal through a side link, and the first terminal can request the second terminal to forward or stop forwarding the first multicast broadcast service, so as to realize its expected forwarding of the first multicast broadcast service. Receiving or stopping receiving of a multicast broadcast service.
  • Fig. 1 is the block diagram of wireless communication system
  • Fig. 2 is one of the method flow diagrams of the embodiment of the present application.
  • Figure 3 is a schematic diagram of the protocol stack architecture for the relay UE to send multicast broadcast control information
  • Figure 4 is a schematic diagram of the protocol stack architecture for the relay UE to send multicast broadcast services
  • FIG. 5 is a schematic diagram of forwarding a multicast broadcast service in an embodiment of the present application.
  • FIG. 6 is the second schematic flow diagram of the method of the embodiment of the present application.
  • Fig. 7 is the third schematic flow diagram of the method of the embodiment of the present application.
  • Fig. 8 is a device structure diagram corresponding to Fig. 2;
  • Fig. 9 is a device structure diagram corresponding to Fig. 6;
  • Fig. 10 is a device structure diagram corresponding to Fig. 7;
  • FIG. 11 is a structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 12 is a structural diagram of a terminal according to an embodiment of the present application.
  • FIG. 13 is a structural diagram of a network device according to an embodiment of the present application.
  • first, second and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific sequence or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein and that "first" and “second” distinguish objects. It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects.
  • “and/or” in the description and claims means at least one of the connected objects, and the character “/” generally means that the related objects are 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 for the above-mentioned system and radio technology, and can also be used for other systems and radio technologies.
  • the following description describes the New Radio (New Radio, NR) system for example purposes, and uses NR terminology in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as the 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 embodiment of the present application is applicable.
  • the wireless communication system includes a terminal 11 and a network side device 12 .
  • the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, 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 equipment, wearable devices include: smart watches, bracelets, earphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, where a base station may be called a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service Basic Service Set (BSS), Extended Service Set (ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN access point, WiFi node, transmission Receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiment of this application, only The base station in the NR system is taken as an example, but the specific type of the base station is not limited.
  • a method for receiving a multicast broadcast service includes:
  • Step 201 the first terminal sends the first request information to the second terminal;
  • the first terminal communicates with the second terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • the first terminal is the remote UE
  • the second terminal is the relay UE.
  • the remote UE requests the relay UE to forward or stop forwarding the first MBS, so as to realize its expected reception or stop receiving of the first MBS.
  • the remote UE, relay UE and base station are L3relay protocol stack architecture.
  • the first MBS is the NR MBS that the first terminal expects (also can be understood as being interested in).
  • the MBS forwarding service request sent by the remote UE to the relay UE is the first request information
  • the first request information is passed through the preset PC5 unicast signaling is sent.
  • the preset PC5 unicast signaling may be dedicated signaling for sending the first request information, such as PC5-S signaling, or PC5-Radio Resource Control (PC5-Radio Resource Control, PC5-RRC) signaling.
  • PC5-S signaling or PC5-Radio Resource Control (PC5-Radio Resource Control, PC5-RRC) signaling.
  • PC5-RRC PC5-Radio Resource Control
  • the signaling process after the security activation is used for sending, and when it is particularly sensitive to delay, it can also be sent before the security activation.
  • the PC5-S signaling mode is used, the process is similar to the LTE process, and will not be repeated here.
  • PC5-RRC signaling you can use a new RRC process, such as an MBS forwarding request (forwarding request) message, or use the existing PC5 RRC message to carry a new field to implement.
  • MBS forwarding request forwarding request
  • the first request information includes at least one of the following:
  • TMGI Temporary Mobile Group Identity
  • the Temporary Mobile Group Identity is used to clarify to the relay UE the multicast broadcast service that the remote UE is interested in; the frequency point information, sending area information, receiving area information and priority of the first multicast broadcast service At least one item in the level information is used to assist the relay UE to read the multicast broadcast service that the remote UE is interested in, for example, the relay UE finds the time-frequency resource and geographic location sent by the TMGI.
  • the priority information of the first multicast broadcast service is, for the remote UE, the relative priority between the first multicast broadcast service and its other services, different remote UEs can give the same TMGI Different priority levels.
  • the multicast broadcast service has a corresponding TMGI, and the multicast broadcast service is also called a TMGI service.
  • the relay UE After receiving the first request information from the remote UE, the relay UE will feed back response information based on the first request information to indicate whether the relay UE provides forwarding of the first multicast broadcast service.
  • the method further includes:
  • the response information is used to indicate whether the second terminal provides forwarding of the first multicast broadcast service.
  • the relay UE can perform a trial search for the first multicast broadcast service according to the first request information; after that, after finding the source cell of the first multicast broadcast service (that is, the cell where the TMGI of the first multicast broadcast service is located) ), and in the case of receiving the first multicast broadcast service, determine that the response information of the first request information is an acknowledgment response, and send it to the remote UE; if the relay UE cannot find the source cell of the first multicast broadcast service Or beyond the capability range (that is, the first multicast broadcast service cannot be received), it can be determined that the relay UE cannot provide reception of the first multicast broadcast service, then the relay UE does not need to receive the TMGI service, and determines the first request
  • the response information of the message is a negative response and is sent to the remote UE.
  • the relay UE feeds back an acknowledgment response to the remote UE by sending an MBS forwarding response (with true)/acknowledgment (Acknowledgment); the relay UE feeds back a negative response to the remote UE by sending an MBS forwarding response (with false)/reject implementation.
  • the relay UE When the relay UE is trying to search, if the first request information gives frequency point information, when the relay UE camps or is served on the frequency point corresponding to the frequency point information, it will directly search at the frequency point , if the relay UE does not camp or is served at the frequency, the relay UE needs to perform one of the following according to its own capabilities:
  • the network device Directly report the demand to the network device, and the network device will consider changing the configuration for the relay UE according to the deployment situation.
  • the relay UE directly reports to the network device, and there are remote UEs that need to relay the TMGI, and report the general frequency, sending area information, and receiving area Information, priority information, etc.
  • the network device specifies whether the frequency has the service according to its own deployment situation, whether the frequency is congested, and the priority of the existing service and TMGI service, among which the network device is considering
  • TMGI services we should not only consider the priority set by a remote UE to TMGI, but need to comprehensively consider the situation of all remote UEs, or the network equipment should consider the unicast and multicast services of all remote UEs. After that, some priority safeguards are carried out.
  • the relay UE performs an area search within its current serving cell to see if the serving cell is within the TMGI transmission area (that is, it belongs to the TMGI transmission area, that is, the range corresponding to the transmission area information of the first multicast broadcast service ), if yes, then you can directly read the TMGI in the serving cell (that is, receive the first multicast broadcast service); to the transmission range belonging to the TMGI), it can also be extended to other cells that the UE can currently read, and if other cells are found, the TMGI reading can be performed directly in the searched cell.
  • the relay UE can report TMGI+ related information to the network device, and the network device can assist in the search, or the relay UE can directly establish a unicast The (unicast) Protocol Data Unit (Protocol Data Unit, PDU) session (session) performs the reception of the TMGI.
  • the (unicast) Protocol Data Unit (Protocol Data Unit, PDU) session performs the reception of the TMGI.
  • the relay UE can directly report the TMGI+ related information to the network device, and the network device will instruct how to find the cell where the TMGI is located.
  • the network device can respond with rejection or failure to the reported TMGI+ related information, for example, there is no such TMGI transmission under the current gNB; or according to the priority policy, the relay UE cannot maintain the simultaneous reception of existing services and TMGI, and needs to abandon TMGI forwarding business.
  • the network device can also reply to the relay UE to initiate the establishment of a unicast PDU session for TMGI transmission.
  • the network device can also reconfigure the serving cell for the relay UE according to the location of the TMGI, so that the relay UE can maintain the service of the existing service and the newly added TMGI service at the same time.
  • the receiving area information can also be understood as effective range information, including the cell list (cell list) or timing advance (Timing Advance, TA ) list, indicating that the TMGI service is only allowed to be received in these cells, and other cells are not allowed to receive it, then the relay UE detects whether its own serving cell belongs to this range, if it does not belong, then it is deemed not allowed to receive, if it belongs, Then it can be received; of course, the detection range can also be extended to other cells that the UE can read, or the receiving area information can be reported to the base station, and the base station can assist in detection or appropriate reconfiguration to place the relay UE serving cell within the effective area.
  • the relay UE After the relay UE tries to search, it finds the source cell of the first multicast broadcast service, and can receive the first multicast broadcast service or receive the first multicast broadcast service after network configuration TMGI (TMGI of the first multicast broadcast service) receives the multicast control channel (MultiCast Control Channel, MCCH) and the multicast traffic channel (Multicast Traffic Channel, MTCH), etc., and returns an acknowledgment response to the remote UE on the one hand.
  • TMGI multicast control channel
  • MTCH Multicast Traffic Channel
  • the service request ends.
  • the relay UE itself is a non-MBS capable (non-MBS capable) UE, and the relay UE does not have the ability to receive the NR MBS service, so requesting forwarding of the multicast broadcast service to it will cause a waste of resources.
  • the relay UE Even if it is a relay UE that supports MBS service reception, but the relay UE only has a single-frequency point reception capability or its capability is limited, it cannot work on both the PC5 frequency point and the MBS frequency point at the same time, so it does not have the ability to forward MBS; Or, the relay UE is currently sending and receiving other services, but there is no MBS service on the current working frequency point, and searching other frequency points to find MBS services is beyond the UE's capability, so the forwarding MBS service cannot be provided; or , the relay UE can currently forward MBS services, but which type of MBS services can be provided, and how many MBS services can be provided at most, all need to consider radio frequency, processing capacity and load conditions; or, the relay UE The TMGI that can be searched currently is specific, and can be directly sent to the remote UE to select within this range, and there is no need to request TMGIs beyond this range.
  • the relay UE will send its own capability information to the remote UE to inform the remote UE of the capability of the relay UE to forward multicast broadcast services, so that the remote UE can more efficiently select the first multicast broadcast service it is interested in Provide relay UE for forwarding.
  • the relay UE broadcasts its own capability information, for example carried in a discovery (discovery) message.
  • the method further includes:
  • the first terminal receives capability information sent by the second terminal, where the capability information is used to indicate the capability of the second terminal to forward the multicast broadcast service.
  • the remote UE can receive the capability information of the relay UE, so as to determine whether the relay UE can provide the forwarding of the first multicast broadcast service from the capability information, and if the relay UE can provide the forwarding of the first multicast broadcast service Next, send the first request message to it.
  • the remote UE can receive capability information of multiple relay UEs, and select the optimal relay UE to forward the first multicast broadcast service.
  • the capability information includes at least one of the following:
  • the capability information gives the type of multicast broadcast service that supports forwarding, it may be one or more of the following: MBS service, broadcast (broadcast) service, multicast (multicast) service, multicast ( multicast for connected) services, used for idle/inactive multicast (multicast for idle/inactive) services, local (local) MBS/broadcast/multicast services.
  • MBS service broadcast (broadcast) service
  • multicast (multicast) service multicast ( multicast for connected) services, used for idle/inactive multicast (multicast for idle/inactive) services, local (local) MBS/broadcast/multicast services.
  • the capability information provides a list of multicast broadcast services that support forwarding, in addition to listing the names of the multicast broadcast services, the multicast broadcast service list can also be represented by TMGI, that is, the list of multicast broadcast services is implemented as a TMGI list (list).
  • the capability information gives the number of multicast broadcast services that support forwarding, it can be one or more of the following: total number/remaining number of MBS services; total number/remaining number of broadcast services; total number/remaining number of multicast services number. If the capability information gives relevant information about the currently forwarded multicast broadcast service, it can be the TMGI list already being forwarded and the corresponding configuration, such as Layer 2 (Layer-2) identity document (Identity document, ID), valid range, Configuration information, etc.
  • Layer 2 Layer-2
  • Identity document Identity document, ID
  • Configuration information etc.
  • the MBS may forward the service request (that is, send the first request information to the relay UE), for example:
  • the relay UE does not broadcast the capability information, or the relay UE explicitly broadcasts the capability information, and the capability information indicates that it does not support MBS forwarding, then the remote UE is not allowed to initiate an MBS forwarding service request;
  • the remote UE can still initiate an MBS forwarding service request
  • the remote UE can initiate an MBS forwarding service request, but the request should be within the forwarding capability of the relay UE and cannot be exceeded.
  • the relay UE receiving the first request information will send multicast broadcast control information to the remote UE, and configure the remote UE so that the remote UE can perform Successful reception of the first multicast broadcast service.
  • the relay UE receives the MCCH of the network device, and the received MCCH further determines the multicast broadcast control information sent to the remote UE.
  • a TMGI service can be composed of multiple logical channels, and the number of logical channels depends on the demand, and each logical channel may also have a different L2 configuration, so the network device carries the configuration corresponding to the TMGI in the MCCH Logical channel related parameters, such as the number of logical channels, logical channel identification (Logical Channel Identify, LCID) and so on.
  • the MCCH may also carry discontinuous reception (Discontinuous Reception, DRX) related parameters corresponding to TMGI, radio bearer related parameters corresponding to TMGI, or the first group identifier corresponding to TMGI.
  • DRX discontinuous Reception
  • the method further includes:
  • the first terminal receives the multicast broadcast control information sent by the second terminal;
  • the multicast broadcast control information includes at least one of the following:
  • Radio bearer related parameters corresponding to TMGI Radio bearer related parameters corresponding to TMGI
  • the first set of identifiers corresponding to TMGI The first set of identifiers corresponding to TMGI.
  • the specific content of the multicast broadcast control information may be directly obtained by the relay UE from the MCCH, or may be further determined by the content in the MCCH.
  • the logical channel related parameters may include the number of logical channels, LCID, etc.
  • the DRX related parameters are parameters indicating the DRX pattern (pattern), and may include the DRX cycle, the DRX starting position, etc.
  • the radio bearer related parameters may include the bearer position, Intervals, mapping relationships, etc.
  • the first group identifier is the PC5 group identifier, which is obtained by the relay UE based on each TMGI allocation, that is, the remote UE with the same PC5 group identifier is interested in the TMGI service corresponding to the PC5 group identifier.
  • the relay UE reads the DRX related parameters corresponding to the TMGI service in the MCCH from the Uu interface, which is to limit the on/off pattern (On/off pattern) of the TMGI service.
  • the relay UE needs a certain processing delay and resource selection delay before it can forward the service on the PC5 interface, so the DRX parameter information read from the Uu interface cannot be directly used for the PC5 link, so ,
  • the DRX-related parameters corresponding to TMGI are Uu DRX-related parameters or PC5 DRX-related parameters.
  • the relay UE processes the Uu DRX pattern indicated by the Uu DRX related parameters in the MCCH after a certain delay to obtain the PC5 DRX pattern, and thus uses the PC5 DRX related parameters that can indicate the PC5 DRX pattern as multicast broadcast control information Send to remote UE.
  • the relay UE directly sends the Uu DRX related parameters in the MCCH to the remote UE as multicast broadcast control information, the remote UE can obtain the required value from the offset or correction between the Uu pattern and the PC5 pattern. PC5 pattern.
  • the offset or correction amount between the Uu pattern and the PC5 pattern may be default or specified, or may be carried in the DRX related parameters of the multicast broadcast control information.
  • the offset or correction between the Uu pattern and the PC5 pattern can be implemented as: an on-duration offset of 5 ms, an inactivity timer increased by 3 ms, and so on.
  • the remote UE performs receiving configuration based on DRX-related parameters corresponding to TMGI, which can achieve the purpose of power saving.
  • L2 configuration information such as the LCID value of the multicast broadcast service, the quality of service ( Quality of Service, QoS) flow (flow) mapping (mapping to) Master Resource Block (Master Resource Block, MRB), L2 configuration of each MRB, sequence number (Sequence Number, SN) length, etc., are expected to be consistent with the Uu interface.
  • the Uu interface belongs to MRB1 of TMGI1, the logical channel ID is 39, the packet data convergence protocol (Packet Data Convergence Protocol, PDCP) SN length is 12, the radio link control (Radio Link Control, RLC) SN length is 12, and the RLC unacknowledged mode (Unacknowledged Mode, UM) configuration remains unchanged when PC5 forwards, and other MRBs are similar.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • UM Unacknowledged Mode
  • the remote UE does not receive two channels of data at the same time, but first receives the TMGI service on the Uu interface, moves to the edge of the cell because the link is too poor, the Uu interface cannot successfully receive it, and moves to the relay UE to continue receiving the TMGI service, no matter MRB is still an L2 entity, RLC/PDCP can be used continuously, and data packets can also be sorted and delivered on demand, which has a good effect on business continuity.
  • the radio bearer related parameters include at least one of the following:
  • the unicast bearer is bound to a PC5 multicast MBS RB.
  • the relay UE sends the configuration information of the unicast bearer and/or the configuration information of the multicast bearer to the remote UE, so that the remote UE performs the configuration based on the configuration information of the unicast bearer and/or the configuration information of the multicast bearer corresponding to the TMGI.
  • the receiving configuration implements effective receiving of the first multicast broadcast service forwarded by the relay UE.
  • the first multicast broadcast service is sent in PC5 multicast mode, it will be sent based on the first group identifier, and corresponding to a group of remote UEs with the same first group identifier, each remote UE in the group (group) is allocated
  • the feedback positions can be the same or different.
  • the first multicast broadcast service is a multicast service received by UEs in the connected state, and is bound to a PC5 multicast MBS RB through unicast bearer , indicating that the unicast bearer is used for service forwarding corresponding to the MBS RB bound to the PC5 multicast.
  • the relay UE can simultaneously use groupcast (groupcast) and unicast to forward on the PC5 interface.
  • groupcast is Point To Multipoint (PTM) scheduling
  • unicast is equivalent to the transmission of Point To Point leg (PTP leg) for binding.
  • PTM Point To Multipoint
  • the multicast broadcast control information is sent in at least one of the following ways:
  • the relay UE sends multicast broadcast control information to the remote UE through at least one of unicast, multicast or broadcast.
  • the relay UE uses PC5 unicast (unicast) to send the multicast broadcast control information, which may be sent together with the multicast broadcast control information carried by the MBS forwarding response when the confirmation response of the first request information is fed back through the MBS forwarding response .
  • PC5 unicast unicast
  • the relay UE uses PC5 groupcast or PC5 broadcast to send multicast broadcast control information, which can have higher transmission efficiency than PC5 unicast.
  • the multicast broadcast control information is sent in PC5 multicast mode or PC5 broadcast mode.
  • the multicast broadcast control information is sent based on the second group identifier, and the multicast broadcast control information includes information of multiple multicast broadcast services; wherein, the allocation of the second group identifier is independent of TMGI; or,
  • the multicast broadcast control information is sent based on the first group identifier, and the multicast broadcast control information includes multicast broadcast service information corresponding to the first group identifier.
  • the relay UE sends the multicast broadcast control information including the information of multiple multicast broadcast services (that is, the configuration corresponding to multiple TMGIs) to multiple remote UEs.
  • the allocation of the second group identity is independent of the TMGI, and the multiple remote UEs have the same second group identity and may be interested in the same or different TMGI services. It can be determined by definition or pre-configuration, or it can be sent by relay UE to remote UE through unicast signaling.
  • the multiple multicast broadcast services can be all the forwarding services currently provided by the relay UE; or all the forwarding services that the relay UE can provide.
  • TMGI services that are not forwarded in real time, they can be distinguished by special marks.
  • On-going and suspend (suspend) represents the TMGI service that is already being forwarded, and suspend represents that it can be forwarded but because no UE is interested, but the remote UE can request forwarding.
  • the relay UE sends the multicast broadcast control information including the information of a multicast broadcast service (that is, the configuration of a TMGI corresponding to the first group identifier) to multiple remote UEs.
  • the allocation of the first group of identities is based on TMGI, so the multiple remote UEs have the same first group of identities, that is, multiple remote UEs are interested in the same TMGI service.
  • LCID for example: displaying multicast broadcast control information and multicast broadcast service
  • LCID for example: displaying multicast broadcast control information and multicast broadcast service
  • configure or default the LCID of the multicast broadcast service wherein the default LCID of the multicast broadcast service is that if the multicast broadcast LCID 39-42 is reserved for business, and LCID39-42 is used by default when it is not configured, and LCID39-40, which is reserved LCID, can be used only by configuration.
  • the protocol stack architecture for the relay UE to send multicast broadcast control information is L3 split, as shown in Figure 3; the protocol stack architecture for the relay UE to send multicast broadcast services is also L3 split, as shown in Figure 4 Show.
  • the method further includes:
  • the first terminal When the first terminal requests the second terminal to forward the first multicast broadcast service through the first request information, it receives the first multicast broadcast service forwarded by the second terminal.
  • the relay UE will forward the interested multicast broadcast service to the remote UE for the forwarding request of the remote UE, such as forwarding the multicast broadcast service to the remote UE after the multicast broadcast service starts to be sent.
  • the remote UE will receive the first multicast broadcast service forwarded by the relay UE.
  • the relay UE can read the MCCH to obtain the configuration of multicast broadcast service forwarding. In this way, the relay UE performs receiving and forwarding processing through the obtained configuration when the first multicast broadcast service starts to be sent on the Uu interface.
  • the first multicast broadcast service is based on the first multicast broadcast service received by the second terminal at the Uu interface. Group ID forwarded.
  • the relay UE can put the received first multicast broadcast service on the corresponding PC5 bearer and transmit it to the interested remote UE through the first group identifier (PC5 group layer-2 ID).
  • the PDCP SN used by the same data packet of the first multicast broadcast service on the PC5 interface is the same as the PDCP SN used by the Uu interface; and/or,
  • the RLC SN used by the same data packet of the first multicast broadcast service on the PC5 interface is the same as the RLC SN used by the Uu interface.
  • the PDCP SN number received by the relay UE from the Uu interface can continue to be kept, and the same PDCP SN number is used to send data on the PC5 interface. If the SN is the same, it must be the same data packet. Therefore, operations such as sorting and deduplication of data packets can be performed based on the PDCP SN.
  • the remote UE receives multiple channels at the same time, the effect of duplication can be achieved.
  • the remote UE switches from one path to another A certain degree of business continuity can also be ensured when there is only one path.
  • the RLC SN number received by the relay UE from the Uu interface can continue to be kept, and the same RLC SN number is used to send data on the PC5 interface.
  • the displayed indication will indicate whether the PDCP SN/RLC SN of the TMGI service is synchronized with the surrounding neighboring cells.
  • the SN synchronization is indicated, it is equivalent to when the UE moves from relay1 under cell1 (cell1) to cell2 (neighboring cell of cell1) or receives at the same time, it can also use the feature of continuous ordering of PDCP/RLC SN to further improve the service Continuity; if the indication is not synchronized, the relay UE cannot perform multi-path combination, but can only receive them separately, and the service layer will process and sort them again. When switching paths, both RLC and PDCP need to be rebuilt and operated again on the new path. take over.
  • the relay UE sends data packets according to the DRX pattern. Specifically, the data packet is only sent during the active period (Active time), and during the non-active period (non-active time), the data packet needs to be cached and waits for the next on period. Wherein, if the data packet times out during the storage process (the length of the discard timer (discard timer) can come from network side configuration, QoS parameters, or relay UE implementation), then delete the data packet or continue to transmit continuously in order to ensure that the SN.
  • the length of the discard timer can come from network side configuration, QoS parameters, or relay UE implementation
  • the remote UE On the remote UE side, after the remote UE obtains the PC5 group layer-2 ID, it continues to monitor the scheduling and data packets of the PC5 group layer-2 ID at all resource pool locations without PC5 DRX related parameter configuration; when PC5 DRX is configured In the case of related parameters, the scheduling and packet monitoring of PC5 group layer-2 ID are only performed during active time.
  • the remote UE After the remote UE obtains the relevant parameters of the MRB/MTCH logical channel in the multicast broadcast control information, it establishes entities on the L2 receiving side according to the number and LCID, such as Media Access Control (Medium Access Control, MAC)/RLC/PDCP/potential SDAP etc., where the SDAP layer is not necessarily required.
  • the remote UE receives the first data packet in an MTCH, then the RLC SN of the first data packet is set as the RLC receiving entity side variable receiving side next reassembly (RX_Next_Reassembly) and the receiving side next highest (RX_Next_Highest) variable the initial value of .
  • the initial value of the RX_NEXT variable is set to (the SN+1) modulo SN space size, and the receiving side provides (RX_DELIV) variable initial value
  • the value is set to (half of the size of the SN space) modulo the size of the SN space, and it is necessary to ensure that the count (COUNT) value calculated by the above two variables should be non-negative.
  • the method further includes:
  • the first terminal receives the cell identifier corresponding to the first multicast broadcast service.
  • the relay UE informs the remote UE of the cell identifier corresponding to the first multicast broadcast service, such as the E-UTRAN Cell Global Identifier (ECGI), so that the remote UE can Knowing which cell the PDCP SN and/or RLC SN are consistent with, it is convenient for simultaneous multi-path reception or multi-path switching to identify the same cell, for example, switching from the relay to the cell, or switching from the cell to the relay Time.
  • the cell identifier corresponding to the first multicast broadcast service such as the E-UTRAN Cell Global Identifier (ECGI)
  • the cell identifier may be carried in unicast signaling interaction, or discovery process, or in the transmission of multicast broadcast control information. In this way, by acquiring the cell identifier, the remote UE moves to the cell and can directly receive the MBS service without reading the configuration again.
  • the remote UE interested in the multicast service needs to use the non-access-stratum (NAS) process to initiate the process of joining (join) multicast TMGI to the core network,
  • NAS non-access-stratum
  • the core network knows that the UE is interested in the TMGI, so that when the multicast service is activated, the core network will page the remote UE interested in the multicast service to receive the service.
  • the remote UE can perform the join process by itself when the link condition is good; or, through the PC5 interface to interact, inform the relay UE that it is interested in a multicast TMGI, and the relay UE initiates its own NAS process to the core network. Carry out the join process.
  • these two join processes can be carried out, so that the remote UE itself receives TMGI activation paging from the Uu interface, or the relay UE receives the TMGI activation (activation) paging from the Uu interface, or the remote UE and the relay UE receive paging at the same time , in case you miss it.
  • the core network will page the relevant subscribed UE, then the remote UE or relay UE will receive the paging message and start preparing to receive the multicast service.
  • the relay UE receives MCCH, and can first enter the connected state to obtain MCCH through dedicated signaling, and then release it back to idle/inactive to receive data; or if MCCH It is generated by public broadcast signaling, and the relay UE can read it. But in any case, after the relay UE can obtain the MCCH, it can send multicast broadcast control information to the remote UE. The sending of the multicast broadcast control information is as described above, and will not be repeated here.
  • the reception and forwarding of the multicast broadcast service (MTCH) of Multicast TMGI for idle/inactive are also shown above, and will not be repeated here.
  • the relay UE needs to enter the connected state to receive MTCH, and MTCH can not only configure PTM (point to Multi -point)leg, and PTP (Point to Point)leg may also be configured at the same time.
  • the network device may dynamically switch between the PTM leg and the PTP leg. Among them, the relay UE forwards the received MTCH to the remote UE, which can be:
  • Method 1 Use groupcast to forward the received MTCH.
  • the feedback position allocated to each remote UE in the group may be the same or different.
  • the relay UE can perform as many hybrid automatic repeat requests (Hybrid automatic repeat request, HARQ) as possible by knowing which UE has made an error and how many UEs have made an error. Retransmission to improve reliability and ensure that all remote UEs meet the QoS requirements as much as possible.
  • Hybrid automatic repeat request Hybrid automatic repeat request
  • Method 2 Based on the groupcast Layer-2 ID (ie, the first group identifier), all or some remote UEs interested in the multicast service are selected (if it is a part, it means that some UEs with poor link conditions are selected) Establish a unicast connection and path, and perform related PTP leg configuration and binding relationship between PTP leg and PTM leg through unicast PC5 RRC, that is, PTP leg can be configured as RLC Acknowledged Mode (Acknowledged Mode, AM), PTP leg must follow a PTM The MRB of the leg is bound, and the two legs have the same PDCP entity.
  • PTP leg can be configured as RLC Acknowledged Mode (Acknowledged Mode, AM)
  • PTP leg must follow a PTM
  • the MRB of the leg is bound, and the two legs have the same PDCP entity.
  • the data received from the PTP leg and the data received from the PTM leg are reordered and duplicated detected and deleted in the same PDCP entity according to the PDCP SN sequence number.
  • an MRB is taken as an example to illustrate the working diagram of split two legs, in which two legs can send duplicate data (duplicated data) to achieve better service reliability .
  • the method further includes:
  • the first terminal requests the second terminal to stop forwarding the first multicast broadcast service through the first request information, or stops receiving the first multicast broadcast service when the first multicast broadcast service ends.
  • a first multicast broadcast service is
  • the service that the remote UE is interested in changes, if it is no longer interested in the first multicast broadcast service, it will send the first request message to the relay UE to request to stop forwarding the first multicast broadcast service, so as to avoid invalid forwarding by the relay UE.
  • the remote UE After the remote UE sends the first request information to request the relay UE to stop forwarding the first multicast broadcast service, the remote UE can autonomously stop receiving the first multicast broadcast service; or, the remote UE learns about the first multicast broadcast service end, the remote UE can also autonomously stop receiving the first multicast broadcast service.
  • the relay UE determines that all terminals corresponding to the first multicast broadcast service have no service requirements (it can also be understood that all remote UEs interested in the first multicast broadcast service are no longer interested in the first multicast broadcast service), or, When the first multicast broadcast service ends, stop forwarding the first multicast broadcast service.
  • the relay UE only receives a request to stop forwarding sent by individual remote UEs based on its own needs. Considering that there will be other requests for the first multicast broadcast service In the case of remote UEs interested in the broadcast service, the relay UE can continue to forward, and the relay UE will send an inquiry message to all remote UEs interested in the first multicast broadcast service, asking whether they have the first multicast broadcast service Forwarding requirements to determine whether all terminals corresponding to the first multicast broadcast service have no service requirements. Therefore, optionally, after step 201, the method further includes:
  • the first terminal receives inquiry information sent by the second terminal, where the inquiry information is used to inquire whether the first terminal has a forwarding requirement for the first multicast broadcast service;
  • the first terminal sends confirmation information of the query information to the second terminal when there is a forwarding requirement of the first multicast broadcast service.
  • the relay UE can determine that there is no need to forward the first multicast broadcast service without receiving any feedback confirmation information from any remote UE.
  • the judgment to stop forwarding will be made based on whether the confirmation information fed back by any remote UE is received within the preset time.
  • an independent process or a unified process can be adopted to request forwarding or stop forwarding of the multicast broadcast service.
  • the remote UE will report every time the service it is interested in changes, and each report will carry the latest relevant information about the service it is interested in. Business-related information of interest. Therefore, the reported information can be used as the first request information to request the relay UE to forward or stop the forwarding of the multicast broadcast service. In this way, the relay UE can learn which services are no longer interested and which services are newly interested based on the latest reported information.
  • the relay UE determines whether there are other remote UEs interested in the service by inquiring information, if yes, it maintains the current forwarding, if not, it can stop the forwarding.
  • the new remote UE in the case that the relay UE is already forwarding the multicast broadcast service, if a new remote UE is interested in the relay UE already forwarding the multicast broadcast service, the new remote UE:
  • the MBS forwarding request message carries the first request information and reports the service-related information (such as TMGI) that it is interested in, and the relay UE directly replies to the Acknowledgment (Acknowledgment) for the service that is already being forwarded, and the Acknowledgment carries multicast broadcast control information , or carry the corresponding configuration of MCCH, such as MCCH Layer-2 ID.
  • the new remote UE After the new remote UE receives it, it reads the multicast broadcast control information to obtain the configuration, and uses the first group identifier corresponding to the TMGI to receive service data.
  • the relay UE has a very accurate grasp of how many remote UEs are currently interested in forwarding TMGI services, so that it can judge and stop.
  • the second is that the multicast broadcast control information and the corresponding multicast broadcast service data can be directly read through broadcasting, without displaying and telling the relay UE to know.
  • the relay UE continuously broadcasts the forwarding multicast broadcast service and the multicast broadcast control information after the first remote UE requests the forwarding of the multicast broadcast service, for example, periodically sends Carried in the discovery message. In this way, the subsequent interaction delay and signaling overhead between the remote UE and the relay UE can be saved.
  • there was no display communication process between the remote UE and the relay UE which caused the relay UE to not know how many UEs are interested in the TMGI service.
  • the relay UE When it wants to stop the TMGI service forwarding, it needs to count (Count) the surrounding UEs Inquiring information to the surrounding UE), for example, in the discovery message, add a 1-bit indication to the on-going TMGI, requesting the surrounding UE to report whether it is interested in the TMGI as soon as possible, if interested, the remote UE immediately reports to the relay UE through unicast, otherwise If the relay UE does not receive any interest report from the remote UE within a period of time, it considers that no UE is interested, and can stop forwarding to save resources.
  • Count the surrounding UEs Inquiring information to the surrounding UE
  • the relay UE can be notified through MCCH notification (notification). Since the relay UE needs to monitor the MCCH notification and MCCH change at any time, the relay UE also knows that the service is stopped, so the relay UE will reclaim PC5 resources after the service is stopped, for example Recycle the group layer-2 ID (ie PC5 group layer-2 ID) and other information related to the TMGI, and stop subsequent forwarding; if the end of the service is notified through the data PDU in the MTCH/MRB, for example, the service is performed through MAC CE Stop indication, the relay UE can resolve the MAC CE, so it also knows the service stop information, and can stop and recycle resources.
  • group layer-2 ID ie PC5 group layer-2 ID
  • the relay UE can resolve the MAC CE, so it also knows the service stop information, and can stop and recycle resources.
  • the method of the embodiment of the present application enables the remote UE to receive the multicast broadcast service from the network device, improves the transmission efficiency and coverage, and guarantees the service experience and system efficiency of the remote UE.
  • a method for sending a multicast broadcast service includes:
  • Step 601 the second terminal receives the first request information from the first terminal
  • the first terminal communicates with the second terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • the second terminal (that is, the relay UE) can receive the first request information of the first terminal (that is, the remote UE), and know that the remote UE expects to receive or stop receiving the first multicast broadcast service, so as to perform subsequent processing, so that The remote UE can receive multicast broadcast services from the network side.
  • the first request information is sent through preset PC5 unicast signaling.
  • the first request information includes at least one of the following:
  • the method before the second terminal receives the first request information of the first terminal, the method further includes:
  • the second terminal sends capability information, where the capability information is used to indicate the capability of the second terminal to forward the multicast broadcast service.
  • the capability information includes at least one of the following:
  • the second terminal after receiving the first request information from the first terminal, the second terminal further includes:
  • the second terminal feeds back response information to the first terminal according to the first request information
  • the response information is used to indicate whether the second terminal provides forwarding of the first multicast broadcast service.
  • the method before the second terminal feeds back response information to the first terminal according to the first request information, the method further includes:
  • the second terminal When the second terminal requests the second terminal to forward the first multicast broadcast service from the first request information, attempting to perform the first multicast broadcast service according to the first request information search;
  • the second terminal finds the source cell of the first multicast broadcast service and receives the first multicast broadcast service, determines that the response information is an acknowledgment response;
  • the second terminal determines that the response information is a negative response when the source cell of the first multicast broadcast service is not found.
  • the method further includes:
  • the second terminal sends multicast broadcast control information to the first terminal
  • the multicast broadcast control information includes at least one of the following:
  • Radio bearer related parameters corresponding to TMGI Radio bearer related parameters corresponding to TMGI
  • the first set of identifiers corresponding to TMGI The first set of identifiers corresponding to TMGI.
  • the multicast broadcast control information is sent in at least one of the following ways:
  • the multicast broadcast control information is sent in PC5 multicast mode or PC5 broadcast mode.
  • the multicast broadcast control information is sent based on the second group identifier, and the multicast broadcast control information includes information of multiple multicast broadcast services; wherein, the allocation of the second group identifier is independent of TMGI; or,
  • the multicast broadcast control information is sent based on the first group identifier, and the multicast broadcast control information includes multicast broadcast service information corresponding to the first group identifier.
  • the DRX-related parameters corresponding to TMGI are Uu DRX-related parameters or PC5 DRX-related parameters.
  • the method further includes:
  • the second terminal forwards the one multicast broadcast service when the first request information requests the second terminal to forward the first multicast broadcast service.
  • the first multicast broadcast service is forwarded by the second terminal based on the first group identifier after receiving the first multicast broadcast service on the Uu interface.
  • the PDCP SN used by the same data packet of the first multicast broadcast service on the PC5 interface is the same as the PDCP SN used by the Uu interface; and/or,
  • the RLC SN used by the same data packet of the first multicast broadcast service at the PC5 interface is the same as the RLC SN used by the Uu interface.
  • the method further includes:
  • the second terminal sends the cell identifier corresponding to the first multicast broadcast service to the first terminal.
  • the radio bearer related parameters include at least one of the following:
  • the unicast bearer is bound to a PC5 multicast MBS RB.
  • the method further includes:
  • the second terminal stops forwarding the first multicast broadcast service when it is determined that all terminals corresponding to the first multicast broadcast service have no service demand, or the first multicast broadcast service ends.
  • the second terminal determining that all terminals corresponding to the first multicast broadcast service have no service requirements includes:
  • the second terminal sends inquiry information to all terminals corresponding to the first multicast broadcast service when the first multicast broadcast service is forwarded in PC5 broadcast mode, and the inquiry information is used to inquire whether the terminal has Forwarding requirements of the first multicast broadcast service;
  • the second terminal determines that all terminals corresponding to the first multicast broadcast service have no service requirements.
  • this method is implemented in conjunction with the above method for receiving multicast broadcast services performed by the first terminal.
  • the implementation method of the second terminal is applicable to this method, and the same technology can also be achieved Effect.
  • a method for sending a multicast broadcast service includes:
  • Step 701 the network device sends the MCCH to the second terminal
  • the second terminal is configured to receive first request information from the first terminal, the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service, and the first A terminal communicates with the second terminal through a side link;
  • the MCCH is used to determine multicast broadcast control information.
  • the first terminal that is, the remote UE
  • the second terminal that is, the relay UE
  • the relay UE understands the remote UE's Requirements, determine the multicast broadcast control information through the received MCCH of the network device, to provide the configuration of subsequent processing for the remote UE, so that the remote UE can receive the multicast broadcast service from the network side.
  • the multicast broadcast control information includes at least one of the following:
  • Radio bearer related parameters corresponding to TMGI Radio bearer related parameters corresponding to TMGI
  • the first set of identifiers corresponding to TMGI The first set of identifiers corresponding to TMGI.
  • this method is implemented in conjunction with the above method for receiving multicast broadcast services performed by the first terminal.
  • the implementation of the network device is applicable to this method, and the same technical effect can also be achieved. .
  • the executing subject may be a sending device of a multicast broadcast service, or a device in the sending device of a multicast broadcast service that is used to execute loading of a multicast broadcast
  • the control module of the sending method of the service is described by taking the method for sending the multicast broadcast service loaded by the device for sending the multicast broadcast service as an example.
  • the receiving device 800 of the multicast broadcast service in the embodiment of the present application includes:
  • the first sending module 810 is configured to send the first request information to the second terminal;
  • the second terminal communicates with the first terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • the first request information is sent through preset PC5 unicast signaling.
  • the first request information includes at least one of the following:
  • the method before the first terminal sends the first request information to the second terminal, the method further includes:
  • the first terminal receives capability information sent by the second terminal, where the capability information is used to indicate the capability of the second terminal to forward the multicast broadcast service.
  • the capability information includes at least one of the following:
  • the device also includes:
  • a response information receiving module configured to receive response information fed back by the second terminal according to the first request information
  • the response information is used to indicate whether the second terminal provides forwarding of the first multicast broadcast service.
  • the device also includes:
  • a first receiving module configured to receive the multicast broadcast control information sent by the second terminal
  • the multicast broadcast control information includes at least one of the following:
  • Radio bearer related parameters corresponding to TMGI Radio bearer related parameters corresponding to TMGI
  • the first set of identifiers corresponding to TMGI The first set of identifiers corresponding to TMGI.
  • the multicast broadcast control information is sent in at least one of the following ways:
  • the multicast broadcast control information is sent in PC5 multicast mode or PC5 broadcast mode.
  • the multicast broadcast control information is sent based on the second group identifier, and the multicast broadcast control information includes information of multiple multicast broadcast services; wherein, the allocation of the second group identifier is independent of TMGI; or,
  • the multicast broadcast control information is sent based on the first group identifier, and the multicast broadcast control information includes multicast broadcast service information corresponding to the first group identifier.
  • the DRX-related parameters corresponding to TMGI are Uu DRX-related parameters or PC5 DRX-related parameters.
  • the device also includes:
  • a first service processing module configured to receive the first multicast broadcast service forwarded by the second terminal when the second terminal is requested to forward the first multicast broadcast service through the first request information .
  • the first multicast broadcast service is forwarded by the second terminal based on the first group identifier after receiving the first multicast broadcast service on the Uu interface.
  • the PDCP SN used by the same data packet of the first multicast broadcast service on the PC5 interface is the same as the PDCP SN used by the Uu interface; and/or,
  • the RLC SN used by the same data packet of the first multicast broadcast service on the PC5 interface is the same as the RLC SN used by the Uu interface.
  • the device also includes:
  • the cell identity receiving module is configured to receive the cell identity corresponding to the first multicast broadcast service.
  • the radio bearer related parameters include at least one of the following:
  • the unicast bearer is bound to a PC5 multicast MBS RB.
  • the device also includes:
  • the second service processing module is configured to request the second terminal to stop forwarding the first multicast broadcast service through the first request information, or stop the forwarding of the first multicast broadcast service when the first multicast broadcast service ends The first multicast broadcast service is received.
  • the device also includes:
  • An inquiry information receiving module configured to receive inquiry information sent by the second terminal, where the inquiry information is used to inquire whether the first terminal has a forwarding requirement for the first multicast broadcast service;
  • the query feedback module is configured to send confirmation information of the query information to the second terminal when there is a forwarding requirement of the first multicast broadcast service.
  • the device by requesting the relay UE to forward or stop the forwarding of the multicast broadcast service, receives the multicast broadcast service from the network side after the relay UE forwards or stops the forwarding of the multicast broadcast service based on the request, thereby improving the transmission efficiency and coverage, ensuring the service experience and system efficiency of remote UE.
  • the device can execute the above-mentioned method for receiving a multicast broadcast service performed by the first terminal, and the implementation of the above method embodiment is applicable to the device, and can also achieve the same technical effect.
  • the device for receiving the multicast broadcast service in the embodiment of the present application may be a device, a device with an operating system or an electronic device, or a component, an integrated circuit, or a chip in a terminal.
  • the apparatus or electronic equipment may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal includes but is not limited to the types of terminal 11 listed above, and the non-mobile terminal can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television , TV), teller machines or self-service machines, etc., are not specifically limited in this embodiment of the present application.
  • the device for receiving a multicast broadcast service provided by the embodiment of the present application can realize various processes implemented by the first terminal in the method embodiments shown in FIG. 2 to FIG. 5 , and details are not repeated here to avoid repetition.
  • an embodiment of the present application is a sending device 900 for a multicast broadcast service, including:
  • the second receiving module 910 is configured to receive the first request information of the first terminal
  • the first terminal communicates with the second terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • the first request information is sent through preset PC5 unicast signaling.
  • the first request information includes at least one of the following:
  • the device also includes:
  • a capability information sending module configured to send capability information, where the capability information is used to indicate the capability of the second terminal to forward multicast broadcast services.
  • the capability information includes at least one of the following:
  • the device also includes:
  • a response information feedback module configured to feed back response information to the first terminal according to the first request information
  • the response information is used to indicate whether the second terminal provides forwarding of the first multicast broadcast service.
  • the device also includes:
  • a search module configured to attempt to perform the first multicast broadcast service according to the first request information when the first request information requests the second terminal to forward the first multicast broadcast service search;
  • a first determining module configured to determine that the response information is an acknowledgment response when the source cell of the first multicast broadcast service is found and the first multicast broadcast service is received;
  • the second determining module is configured to determine that the response information is a negative response when the source cell of the first multicast broadcast service is not found.
  • the device also includes:
  • a second sending module configured to send multicast broadcast control information to the first terminal
  • the multicast broadcast control information includes at least one of the following:
  • Radio bearer related parameters corresponding to TMGI Radio bearer related parameters corresponding to TMGI
  • the first set of identifiers corresponding to TMGI The first set of identifiers corresponding to TMGI.
  • the multicast broadcast control information is sent in at least one of the following ways:
  • the multicast broadcast control information is sent in PC5 multicast mode or PC5 broadcast mode.
  • the multicast broadcast control information is sent based on the second group identifier, and the multicast broadcast control information includes information of multiple multicast broadcast services; wherein, the allocation of the second group identifier is independent of TMGI; or,
  • the multicast broadcast control information is sent based on the first group identifier, and the multicast broadcast control information includes multicast broadcast service information corresponding to the first group identifier.
  • the DRX-related parameters corresponding to TMGI are Uu DRX-related parameters or PC5 DRX-related parameters.
  • the device also includes:
  • a service forwarding module configured to forward the one multicast broadcast service when the first request information requests the second terminal to forward the first multicast broadcast service.
  • the first multicast broadcast service is forwarded by the second terminal based on the first group identifier after receiving the first multicast broadcast service on the Uu interface.
  • the PDCP SN used by the same data packet of the first multicast broadcast service on the PC5 interface is the same as the PDCP SN used by the Uu interface; and/or,
  • the RLC SN used by the same data packet of the first multicast broadcast service at the PC5 interface is the same as the RLC SN used by the Uu interface.
  • the device also includes:
  • a cell identity sending module configured to send the cell identity corresponding to the first multicast broadcast service to the first terminal.
  • the radio bearer related parameters include at least one of the following:
  • the unicast bearer is bound to a PC5 multicast MBS RB.
  • the device also includes:
  • the third service processing module is configured to stop forwarding the first multicast broadcast when it is determined that all terminals corresponding to the first multicast broadcast service have no service demand, or that the first multicast broadcast service ends business.
  • the third business processing module includes:
  • the query information sending submodule is used to send query information to all terminals corresponding to the first multicast broadcast service when the first multicast broadcast service is forwarded in PC5 broadcast mode, and the query information is used for query Whether the terminal has the forwarding requirement of the first multicast broadcast service;
  • the processing sub-module is configured to determine that all terminals corresponding to the first multicast broadcast service have no service requirements if no confirmation information of the inquiry information sent by any terminal is received.
  • the device understands that the remote UE expects to receive or stop receiving the first multicast broadcast service by receiving a request from the relay UE, so as to perform subsequent processing, so that the remote UE receives the multicast broadcast service from the network side, improving transmission efficiency and Coverage ensures the service experience and system efficiency of remote UE.
  • the device can execute the above-mentioned method for receiving a multicast broadcast service performed by the second terminal, and the implementation of the above method embodiment is applicable to the device, and can also achieve the same technical effect.
  • the device for sending the multicast broadcast service in the embodiment of the present application may be a device, a device with an operating system or an electronic device, or a component, an integrated circuit, or a chip in a terminal.
  • the apparatus or electronic equipment may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal includes but is not limited to the types of terminal 11 listed above, and the non-mobile terminal can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television , TV), teller machines or self-service machines, etc., are not specifically limited in this embodiment of the present application.
  • Network Attached Storage NAS
  • NAS Network Attached Storage
  • PC personal computer
  • TV television
  • teller machines or self-service machines etc.
  • the device for sending a multicast broadcast service provided by the embodiment of the present application can implement various processes implemented by the second terminal in the method embodiments shown in FIG. 3 to FIG. 6 , and details are not repeated here to avoid repetition.
  • the sending device 1000 of the multicast broadcast service in the embodiment of the present application includes:
  • the third sending module 1010 is configured to send the MCCH to the second terminal;
  • the second terminal is configured to receive first request information from the first terminal, the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service, and the first A terminal communicates with the second terminal through a side link;
  • the MCCH is used to determine multicast broadcast control information.
  • the multicast broadcast control information includes at least one of the following:
  • Radio bearer related parameters corresponding to TMGI Radio bearer related parameters corresponding to TMGI
  • the first set of identifiers corresponding to TMGI The first set of identifiers corresponding to TMGI.
  • the device sends MCCH to the second terminal, since the second terminal is the terminal that receives the first request information sent by the first terminal, and the first request information is the first terminal's request to the second terminal for the first multicast broadcast service
  • the second terminal understands the requirements of the remote UE, and combines the MCCH to provide follow-up processing for the first terminal, so that the first terminal can receive the multicast broadcast service from the network side.
  • the device can execute the above-mentioned method for sending a multicast broadcast service performed by the network device, and the implementation of the above method embodiment is applicable to the device, and can also achieve the same technical effect.
  • this embodiment of the present application also provides a communication device, including a processor 1101, a memory 1102, and programs or instructions stored in the memory 1102 and operable on the processor 1101, such as , when the communication device 1100 is a terminal, when the program or instruction is executed by the processor 1101, the above-mentioned method for receiving a multicast broadcast service performed by the first terminal is implemented, or the method for sending a multicast broadcast service performed by the second terminal is implemented Each process of the example, and can achieve the same technical effect.
  • the communication device 1100 is a network device
  • the program or instruction is executed by the processor 1101
  • the various processes of the above-mentioned embodiment of the method for sending a multicast broadcast service performed by the network device are implemented, and the same technical effect can be achieved. In order to avoid duplication , which will not be repeated here.
  • the embodiment of the present application also provides a terminal, including a processor and a communication interface, and the communication interface is used to send the first request information to the second terminal; wherein, the second terminal communicates with the first terminal through a side link, The first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • This terminal embodiment corresponds to the above-mentioned method embodiment executed by the first terminal, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • the embodiment of the present application also provides a terminal, including a processor and a communication interface, and the communication interface is used to receive the first request information sent by the first terminal; wherein, the communication between the first terminal and the second terminal is through a side link , the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • This terminal embodiment corresponds to the above-mentioned method embodiment executed by the second terminal, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • FIG. 12 is a schematic diagram of a hardware structure of a terminal implementing various embodiments of the present application.
  • the terminal 1200 includes, but is not limited to: a radio frequency unit 1201, a network module 1202, an audio output unit 1203, an input unit 1204, a sensor 1205, a display unit 1206, a user input unit 1207, an interface unit 1208, a memory 1209, and a processor 1210, etc. at least some of the components.
  • the terminal 1200 can also include a power supply (such as a battery) for supplying power to various components, and the power supply can be logically connected to the processor 1210 through the power management system, so as to manage charging, discharging, and power consumption through the power management system. Management and other functions.
  • a power supply such as a battery
  • the terminal structure shown in FIG. 12 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 1204 may include a graphics processor (Graphics Processing Unit, GPU) 12041 and a microphone 12042, and the graphics processor 12041 is used for the image capture device (such as the image data of the still picture or video obtained by the camera) for processing.
  • the display unit 1206 may include a display panel 12061, and the display panel 12061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 1207 includes a touch panel 12071 and other input devices 12072 . Touch panel 12071, also called touch screen.
  • the touch panel 12071 may include two parts, a touch detection device and a touch controller.
  • Other input devices 12072 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 1201 receives the downlink data from the network side device, and processes it to the processor 1210; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 1201 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the memory 1209 can be used to store software programs or instructions as well as various data.
  • the memory 1209 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area may store an operating system, an application program or instructions required by at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 1209 may include a high-speed random access memory, and may also include a nonvolatile memory, wherein the nonvolatile 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 1210 may include one or more processing units; optionally, the processor 1210 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 handle wireless communications, such as baseband processors. It can be understood that the foregoing modem processor may not be integrated into the processor 1210 .
  • the radio frequency unit 1201 is configured to send the first request information to the second terminal;
  • the second terminal communicates with the first terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • the terminal by requesting the relay UE to forward or stop the forwarding of the multicast broadcast service, receives the multicast broadcast service from the network side after the relay UE forwards or stops the forwarding of the multicast broadcast service based on the request, thereby improving the transmission efficiency and coverage, ensuring the service experience and system efficiency of remote UE.
  • the radio frequency unit 1201 is configured to receive the first request information sent by the first terminal;
  • the first terminal communicates with the second terminal through a side link, and the first request information is used to request the second terminal to forward or stop forwarding the first multicast broadcast service.
  • the terminal by receiving a request from the relay UE, understands that the remote UE expects to receive or stop receiving the first multicast broadcast service, so as to perform subsequent processing, so that the remote UE receives the multicast broadcast service from the network side, improving transmission efficiency and coverage, ensuring the service experience and system efficiency of remote UE.
  • the embodiment of the present application also provides a network device, including a processor and a communication interface, and the communication interface is used to send the MCCH to the second terminal; wherein the second terminal is used to receive the first request information of the first terminal, and the The first request information is used to request the second terminal to forward or stop the forwarding of the first multicast broadcast service, and the first terminal communicates with the second terminal through a side link; the MCCH is used for Determines the multicast broadcast control information.
  • the network device embodiment corresponds to the network device method embodiment above, and each implementation process and implementation mode of the above method embodiment can be applied to the network device embodiment, and can achieve the same technical effect.
  • the embodiment of the present application also provides a network device.
  • the network device 1300 includes: an antenna 131 , a radio frequency device 132 , and a baseband device 133 .
  • the antenna 131 is connected to the radio frequency device 132 .
  • the radio frequency device 132 receives information through the antenna 131, and sends the received information to the baseband device 133 for processing.
  • the baseband device 133 processes the information to be sent and sends it to the radio frequency device 132
  • the radio frequency device 132 processes the received information and sends it out through the antenna 131 .
  • the foregoing frequency band processing device may be located in the baseband device 133 , and the method performed by the network device in the above embodiments may be implemented in the baseband device 133 , and the baseband device 133 includes a processor 134 and a memory 135 .
  • the baseband device 133 can include at least one baseband board, for example, a plurality of chips are arranged on the baseband board, as shown in FIG.
  • the baseband device 133 may also include a network interface 136 for exchanging information with the radio frequency device 132, such as a common public radio interface (CPRI for short).
  • a network interface 136 for exchanging information with the radio frequency device 132, such as a common public radio interface (CPRI for short).
  • CPRI common public radio interface
  • the network device in the embodiment of the present invention also includes: instructions or programs stored in the memory 135 and operable on the processor 134, and the processor 134 calls the instructions or programs in the memory 135 to execute the modules shown in FIG. method, and achieve the same technical effect, in order to avoid repetition, it is not repeated here.
  • the embodiment of the present application also provides a readable storage medium.
  • the readable storage medium stores a program or an instruction.
  • the steps of the above-mentioned method performed by the first terminal are realized, or the above-mentioned
  • the steps of the method performed by the second terminal, or the various processes of the method embodiments described in the method performed by the network device above can achieve the same technical effect, and are not repeated here to avoid repetition.
  • the processor is the processor in the terminal described in the foregoing embodiments.
  • the readable storage medium includes computer readable storage medium, such as computer read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk or optical disk, etc.
  • the embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the above-mentioned steps executed by the first terminal.
  • chips mentioned in the embodiments of the present application may also be called system-on-chip, system-on-chip, system-on-a-chip, or system-on-a-chip.
  • the term “comprising”, “comprising” or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase “comprising a " does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element.
  • the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
  • the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also 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 computer software products, which are stored in a storage medium (such as ROM/RAM, magnetic disk, etc.) , 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 the present application.

Landscapes

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

Abstract

本申请公开了一种多播广播业务的接收方法、发送方法、装置及设备，属于通信技术领域。本申请实施例的多播广播业务的接收方法，包括：第一终端发送第一请求信息至第二终端；其中，所述第一终端与所述第二终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。

Description

多播广播业务的接收方法、发送方法、装置及设备
相关申请的交叉引用
本申请主张在2021年7月23日在中国提交的中国专利申请No.202110839367.2的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种多播广播业务的接收方法、发送方法、装置及设备。
背景技术
长期演进(Long Term Evolution，LTE)系统从第12个发布版本开始支持副链路(sidelink，或译为侧链路/边链路等)，用于终端用户设备(User Equipment，UE)之间不通过网络设备进行直接数据传输。其中，为了支持更广范围的通信应用和服务，提出基于sidelink的中继(relay)通信，扩展覆盖和改善功耗。
然而，现有的relay通信技术中，面对多播广播业务(Multimedia Broadcast Service，MBS)，如何实现远端(remote)UE的接收已成为亟待解决的问题。
发明内容
本申请实施例提供一种多播广播业务的接收方法、发送方法、装置及设备，能够解决remote UE无法接收MBS的问题。
第一方面，提供了一种多播广播业务的接收方法，包括：
第一终端发送第一请求信息至第二终端；
其中，所述第一终端与所述第二终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
第二方面，提供了一种多播广播业务的接收装置，包括：
第一发送模块，用于发送第一请求信息至第二终端；
其中，所述第二终端与第一终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
第三方面，提供了一种多播广播业务的发送方法，包括：
第二终端接收第一终端的第一请求信息；
其中，所述第一终端与所述第二终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
第四方面，提供了一种多播广播业务的发送装置，包括：
第二接收模块，用于接收第一终端的第一请求信息；
其中，所述第一终端与第二终端之间通过旁链路通信，所述第一请求信息用于向第二终端请求进行第一多播广播业务的转发或者停止转发。
第五方面，提供了一种多播广播业务的发送方法，包括：
网络设备发送MCCH至第二终端；
其中，所述第二终端用于接收第一终端的第一请求信息，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发，所述第一终端与所述第二终端之间通过旁链路通信；
所述MCCH用于确定多播广播控制信息。
第六方面，提供了一种多播广播业务的发送装置，包括：
第三发送模块，用于发送MCCH至第二终端；
其中，所述第二终端用于接收第一终端的第一请求信息，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发，所述第一终端与所述第二终端之间通过旁链路通信；
所述MCCH用于确定多播广播控制信息。
第七方面，提供了一种终端，该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面或第三方面所述的方法的步骤。
第八方面，提供了一种终端，包括处理器及通信接口，其中，所述通信接口用于发送第一请求信息至第二终端；
其中，所述第二终端与第一终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
第九方面，提供了一种终端，包括处理器及通信接口，其中，所述通信接口用于接收第一终端的第一请求信息；
其中，所述第一终端与第二终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
第十方面，提供了一种网络设备，该网络设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第五方面所述的方法的步骤。
第十一方面，提供了一种网络设备，包括处理器及通信接口，其中，所述通信接口用于发送MCCH至第二终端；
其中，所述第二终端用于接收第一终端的第一请求信息，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发，所述第一终端与所述第二终端之间通过旁链路通信；
所述MCCH用于确定多播广播控制信息。
第十二方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤，或者实现如第五方面所述的方法的步骤。
第十三方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法，或实现如第三方面所述的方法，或者实现如第五方面所述的方法。
第十四方面，提供了一种计算机程序产品，所述计算机程序产品被存储在非易失的存储介质中，所述计算机程序产品被至少一个处理器执行以实现如第一方面所述的方法，或实现如第三方面所述的方法，或者实现如第五方面所述的方法。
第十五方面，提供了一种通信设备，被配置为执行如第一方面所述的方法，或执行如第三方面所述的方法，或者执行如第五方面所述的方法。
在本申请实施例中，第一终端与第二终端通过旁链路通信，该第一终端能够向第二终端请求进行第一多播广播业务的转发或者停止转发，以实现其期待的对第一多播广播业务的接收或者停止接收。
附图说明
图1为无线通信系统的框图；
图2为本申请实施例的方法流程示意图之一；
图3为relay UE发送多播广播控制信息的协议栈架构示意图；
图4为relay UE发送多播广播业务的协议栈架构示意图；
图5为本申请实施例中多播广播业务的转发示意图；
图6为本申请实施例的方法流程示意图之二；
图7为本申请实施例的方法流程示意图之三；
图8为对应图2的装置结构图；
图9为对应图6的装置结构图；
图10为对应图7的装置结构图；
图11为本申请实施例的通信设备的结构图；
图12为本申请实施例的终端的结构图；
图13为本申请实施例的网络设备的结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描 述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(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节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的传输处理方法进行详细地说明。
如图2所示，本申请实施例的一种多播广播业务的接收方法，包括：
步骤201，第一终端发送第一请求信息至第二终端；
其中，所述第一终端与所述第二终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
这里，第一终端即remote UE，第二终端即relay UE，remote UE通过向relay UE请求进行第一MBS的转发或者停止转发，实现其期待的对第一MBS的接收或者停止接收。
其中，remote UE、relay UE和基站(即网络设备)为L3relay协议栈架构。
该实施例中，第一MBS为第一终端期待(也可理解为感兴趣)的NR MBS。
考虑到remote UE向relay UE发送的MBS转发业务请求即第一请求信息，由于是比较个性化的需求，且有一定的私密和隐私特征，可选地，所述第一请求信息通过预设的PC5单播信令发送。
这里，预设的PC5单播信令可以是发送该第一请求信息的专用信令，如PC5-S信令，或者PC5-无线资源控制(PC5-Radio Resource Control，PC5-RRC)信令。较佳的，使用安全激活后的信令过程进行发送，当对时延特别敏感时，也可以在安全激活之前进行发送。如果用PC5-S信令方式，则类似于LTE的过程，在此不再赘述。如果是PC5-RRC信令，则可以使用新的RRC过程，例如MBS转发请求(forwarding request)消息，或者使用现有的PC5 RRC消息里携带新的域来进行实现。
可选地，所述第一请求信息包括以下至少一项：
所述第一多播广播业务的临时移动组标识(Temporary Mobile Group  Identity，TMGI)；
所述第一多播广播业务的频点信息；
所述第一多播广播业务的发送区域信息；
所述第一多播广播业务的接收区域信息；
所述第一多播广播业务的优先级信息。
这里，临时移动组标识(Temporary Mobile Group Identity，TMGI)用于向relay UE明确remote UE感兴趣的多播广播业务；第一多播广播业务的频点信息、发送区域信息、接收区域信息和优先级信息中的至少一项，用于辅助relay UE读取到remote UE感兴趣的多播广播业务，如relay UE找到TMGI所发送的时频资源和地理位置。其中，第一多播广播业务的优先级信息，是对于该remote UE来说，该第一多播广播业务与它的其它业务之间的相对优先级，不同的remote UE对同一个TMGI可以给不同的优先级等级。
该实施例中，多播广播业务具有对应的TMGI，多播广播业务也称为TMGI业务。
relay UE接收到remote UE的第一请求信息后，会基于该第一请求信息反馈响应信息来指示该relay UE是否提供第一多播广播业务的转发。可选地，在步骤201之后，所述方法还包括：
所述第一终端接收所述第二终端根据所述第一请求信息反馈的响应信息；
其中，所述响应信息用于指示所述第二终端是否提供所述第一多播广播业务的转发。
其中，relay UE可根据该第一请求信息进行第一多播广播业务的尝试搜索；之后，在查找到该第一多播广播业务的源小区(即第一多播广播业务的TMGI所在的小区)，且接收到该第一多播广播业务的情况下，确定该第一请求信息的响应信息为确认响应，并发送至该remote UE；若relay UE无法找到第一多播广播业务的源小区或者超出能力范围(即无法接收到该第一多播广播业务)，可确定relay UE无法提供该第一多播广播业务的接收，则relay UE不需要对TMGI业务进行接收，确定该第一请求信息的响应信息为否定响应，并发送至该remote UE。
这里，relay UE向remote UE反馈确认响应，可通过发送MBS转发响应 (与成功)(forwarding response(with true))/确认(Acknowledgement)实现；relay UE向remote UE反馈否定响应，可通过发送MBS forwarding response(与失败(with false))/拒绝(reject)实现。
在relay UE在尝试搜索过程中，如果第一请求信息给出的是频点信息，则当relay UE驻留或者被服务于该频点信息对应的频点时，则直接在该频点进行搜索，如果relay UE并没有驻留或者被服务于该频点，则relay UE需要根据自身能力执行以下之一：
自主的去指定频点搜索；
执行小区重选过程去该频点搜索；
请求网络设备将该频点设置为自己的服务小区；
上报网络设备需求由网络设备考虑UE能力调整服务小区配置使得UE可以兼顾该频点读取；
直接将需求上报网络设备，由网络设备根据部署情况，考虑为该relay UE更改配置，例如relay UE直接上报网络设备，有remote UE需要中转这个TMGI，上报中将频点、发送区域信息、接收区域信息、优先级信息等都带上，网络设备根据自己的部署情况，指定这个频点是否有该业务，该频点是否拥塞，现有业务和TMGI业务的优先级情况如何，其中网络设备在考虑TMGI业务的优先级时，并不能只考虑一个remote UE对TMGI设置的优先级，而是需要综合考虑所有remote UE的情况，或者网络设备对所有的remote UE的单播业务和多播业务通盘考虑之后，进行一些优先保障措施。
在relay UE在尝试搜索过程中，如果第一请求信息给出的是发送区域信息，则：
relay UE在自己当前的服务小区范围内，进行区域搜索，看看服务小区是否在TMGI的发送区域范围(即属于TMGI发送区域范围，也就是该第一多播广播业务的发送区域信息对应的范围)内，如果是，则可以直接在服务小区进行TMGI读取(即第一多播广播业务的接收)；如果当前服务小区不在该属于TMGI的发送区域范围内(即当前服务小区范围内没有搜索到属于TMGI的发送范围)，则还可以扩大到UE当前能力能够读取的其它小区，且在搜索到了其它小区的情况下，可以直接在搜索到的小区进行TMGI读取。 如果当前服务小区范围和UE能力范围之内，都没有找到属于TMGI的发送区域范围内的小区，则relay UE可以上报TMGI+相关信息给网络设备，由网络设备辅助找寻，或者relay UE直接建立单播(unicast)协议数据单元(Protocol Data Unit，PDU)会话(session)进行该TMGI的接收。
或者，relay UE可以直接把TMGI+相关信息上报给网络设备，由网络设备指示，应该如何找到TMGI所在cell。
当然，网络设备对于上报的TMGI+相关信息，可以回复拒绝或者失败，例如当前gNB下没有该TMGI发送；或者根据优先级策略，relay UE无法同时维持现有业务和TMGI的同时接收，需要舍弃TMGI转发业务。网络设备也可以回复relay UE发起unicast PDU session建立，用于TMGI的传输。网络设备也可以根据TMGI所在的位置，为relay UE重新配置服务小区，使得relay UE可以同时维持现有业务和新加的TMGI业务的服务。
在relay UE在尝试搜索过程中，如果第一请求信息给出的是接收区域信息，该接收区域信息也可以理解为有效范围信息，包括小区列表(cell list)或者时间提前量(Timing Advance，TA)list，表明该TMGI业务仅在这些小区里是允许接收的，其它小区不允许进行接收，则relay UE检测自己的服务小区是否属于该范围，如果不属于，则认定不允许接收，如果属于，则可以接收；当然检测范围也可以扩大到UE能力能够读取的其它小区，或者上报该接收区域信息给基站，由基站辅助检测或者适当重配置将relay UE服务小区置于有效区域范围之内。
relay UE尝试搜索后，找到了第一多播广播业务的源小区，并能够接收第一多播广播业务或者经过网络侧重配置之后可以进行第一多播广播业务接收，则relay UE一方面开始对TMGI(第一多播广播业务的TMGI)对应的多播控制信道(MultiCast Control Channel，MCCH)和多播业务信道(Multicast Traffice Channel，MTCH)等进行接收，一方面向remote UE返回确认响应。
该实施例中，对于remote UE来说，如果relay UE反馈否定响应，即指示其不能提供第一多播广播业务的转发，则业务请求结束。
另外，应该知道的是，对于MBS业务的转发，需要结合relay UE进行请求。例如，自己本身是个非MBS能力(non-MBS capable)UE的relay UE， 该relay UE不具备接收NR MBS业务的能力，向其请求多播广播业务的转发会造成资源的浪费。又如，即使是支持MBS业务接收的relay UE，但该relay UE只有单频点接收能力或者能力受限不能同时在PC5频点和MBS频点上同时工作，因此它也不具备转发MBS能力；或者，该relay UE当前有其它业务正在收发，而当前的工作频点上并没有任何MBS业务，再搜索其它频点找寻MBS业务又超出了UE的能力范围，因此无法提供转发MBS服务；又或者，该relay UE当前可以进行MBS业务转发，但可以提供的是哪种类型的MBS业务，以及最多提供几个MBS业务等，都需要考虑射频、处理能力和负荷情况等；再或者，该relay UE当前能搜索到的TMGI是特定的，可以直接发送给remote UE在此范围内挑选，不需要请求超出该范围之外的TMGI。因此，relay UE会发送自身的能力信息至remote UE，来告知remote UE该relay UE转发多播广播业务的能力，以便remote UE对于其感兴趣的第一多播广播业务，进行更高效的选择可提供转发的relay UE。其中，relay UE通过广播发送自身的能力信息，例如发现(discovery)消息里携带。
相应的，该实施例中，在步骤201之前，所述方法还包括：
所述第一终端接收所述第二终端发送的能力信息，所述能力信息用于表示所述第二终端转发多播广播业务的能力。
即，remote UE可接收relay UE的能力信息，从而由该能力信息确定该relay UE是否能够提供第一多播广播业务的转发，并在该relay UE能够提供第一多播广播业务的转发的情况下向其发送第一请求信息。当然，remote UE可接收多个relay UE的能力信息，选择最优的relay UE实现第一多播广播业务的转发。
可选地，所述能力信息包括以下至少一项：
支持转发的多播广播业务的类型；
支持转发的多播广播业务列表；
支持转发的多播广播业务的数量；
当前转发的多播广播业务的相关信息。
这里，若能力信息给出支持转发的多播广播业务的类型，则可以为以下一种或多种：MBS业务，广播(broadcast)业务，组播(multicast)业务， 用于连接的组播(multicast for connected)类业务，用于空闲/非激活的组播(multicast for idle/inactive)类业务，本地的(local)MBS/broadcast/multicast类业务。若能力信息给出支持转发的多播广播业务列表，该多播广播业务列表中除列出多播广播业务的名称，还可由TMGI表示，即多播广播业务列表实现为TMGI列表(list)。若能力信息给出支持转发的多播广播业务的数量，则可以为以下一种或多种：MBS业务的总数目/剩余数目；broadcast业务的总数目/剩余数目；multicast业务的总数目/剩余数目。若能力信息给出当前转发的多播广播业务的相关信息，则可以是已经在转发的TMGI list和对应配置，例如层2(Layer-2)身份标识号(Identity document，ID)，有效范围，配置信息等。
当然，该实施例中，remote UE在接收或者未接收relay UE的能力信息的前提下，都可能MBS转发业务请求(即向relay UE发送第一请求信息)，例如：
relay UE没有广播该能力信息，或者relay UE明确广播该能力信息，且能力信息指示自己不支持MBS转发，则remote UE不允许发起MBS转发业务请求；
在没有relay UE广播该能力信息的情况下，remote UE依然可以发起MBS转发业务请求；
当relay UE广播了该能力信息，且该能力信息指示自己支持MBS相关转发的情况下，remote UE可以发起MBS转发业务请求，不过该请求应该在relay UE转发能力之内，不能超出。
该实施例中，为保证后续remote UE接收到转发的第一多播广播业务，接收第一请求信息的relay UE，会向remote UE发送多播广播控制信息，配置remote UE，以便于remote UE进行第一多播广播业务的顺利接收。其中，relay UE接收网络设备的MCCH，由接收到的MCCH进一步确定发送给remote UE的多播广播控制信息。
在NR中，一个TMGI业务可以由多个逻辑信道组成，而逻辑信道的数目按需求而定，且每个逻辑信道也可能拥有不同的L2配置，因此网络设备在MCCH中携带配置的与TMGI对应的逻辑信道相关参数，如逻辑信道的数目、 逻辑信道的标识(Logical Channel Identify，LCID)等。MCCH中还可能携带与TMGI对应的非连续接收(Discontinuous Reception，DRX)相关参数、与TMGI对应的无线承载相关参数或者与TMGI对应的第一组标识。
相应的，该实施例中，在步骤201之后，所述方法还包括：
所述第一终端接收所述第二终端发送的多播广播控制信息；
其中，所述多播广播控制信息包括以下至少一项：
与TMGI对应的逻辑信道相关参数；
与TMGI对应的DRX相关参数；
与TMGI对应的无线承载相关参数；
与TMGI对应的第一组标识。
这里，多播广播控制信息的具体内容可以是relay UE由MCCH中直接得到的，也可以是由MCCH中的内容进一步确定的。其中，逻辑信道相关参数可包括逻辑信道的数量、LCID等；DRX相关参数是指示DRX模式(pattern)的参数，可包括DRX周期、DRX起始位置等；无线承载相关参数可包括承载的位置、间隔、映射关系等。而第一组标识是PC5组标识，是relay UE基于每个TMGI进行分配得到的，即具有同一个PC5组标识的remote UE，对该PC5组标识对应的TMGI业务感兴趣。
应该知道的是，relay UE从Uu接口读取MCCH中TMGI业务对应的DRX相关参数，是限定该TMGI业务的启动/关闭模式(On/off pattern)。考虑到relay UE在接收到业务后，需要一定的处理时延和资源选择时延，才能够在PC5接口转发业务，故从Uu接口读取的DRX参数信息并不能直接用于PC5链路，因此，可选地，所述与TMGI对应的DRX相关参数为Uu DRX相关参数或者PC5 DRX相关参数。
即，一方面，relay UE将MCCH中Uu DRX相关参数指示的Uu DRX pattern，经过一定延时处理，得到PC5 DRX pattern，从而把能够指示该PC5 DRX pattern的PC5 DRX相关参数作为多播广播控制信息发送给remote UE。另一方面，若relay UE将MCCH中Uu DRX相关参数直接作为多播广播控制信息发送给remote UE，而remote UE能够由Uu pattern和PC5 pattern之间的偏移量或者矫正量，得到所需的PC5 pattern。其中，Uu pattern和PC5 pattern 之间的偏移量或者矫正量可以是默认或规定的，也可以是携带于多播广播控制信息的DRX相关参数中。具体的，Uu pattern和PC5 pattern之间的偏移量或者矫正量可以实现为：持续周期(on Duration)偏移5个ms，非激活计时器(inactivity timer)增加3ms等等。
remote UE基于与TMGI对应的DRX相关参数进行接收配置，可达到省电的目的。
而考虑到业务的连续性，该实施例中，relay UE确定的多播广播控制信息中除DRX相关参数外，其他参数特别是L2配置信息，如多播广播业务的LCID取值，服务质量(Quality of Service，QoS)流(flow)映射(mapping to)主资源块(Master Resource Block，MRB)，每个MRB的L2配置，序列号(Sequence Number，SN)长度等，期待与Uu接口一致。即，若Uu接口属于TMGI1的MRB1使用逻辑信道ID 39，分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)SN长度12，无线链路控制(Radio Link Control，RLC)SN长度12，RLC非确认模式(Unacknowledged Mode，UM)配置，在PC5转发时仍旧维持不变，其余MRB类似。这样，若一个remote UE同时可以接收来自relay UE的TMGI业务和来自Uu接口的TMGI业务，则这两个TMGI业务的配置完全一致，UE可以将两个路径的数据包进行排序和重复检测删除等，达到一个重复(duplication)传输的效果，但又不增加额外开销。并且，如果remote UE不是同时接收两路数据，而是先位于Uu接口接收TMGI业务，移动到小区边缘链路太差，Uu接口无法成功接收，移动到relay UE下继续接收该TMGI业务，则无论MRB还是L2实体，RLC/PDCP都可以接续使用，对数据包也可以进行排序和按需递交，对业务连续性有较好的作用。
可选地，所述无线承载相关参数包括以下至少一项：
单播承载的配置信息；
组播承载的配置信息；
其中，所述第一多播广播业务采用PC5单播方式发送的情况下，所述单播承载与一个PC5组播的MBS RB绑定。
也就是，relay UE发送单播承载的配置信息和/或组播承载的配置信息至 remote UE，以使remote UE基于与TMGI对应的单播承载的配置信息和/或组播承载的配置信息进行接收配置，实现对relay UE转发的第一多播广播业务的有效接收。
这里，若第一多播广播业务采用PC5组播方式发送，将基于第一组标识进行发送，则对应同一个第一组标识的一组remote UE，组(group)中的每个remote UE分配的反馈位置可以相同也可以不同。
第一多播广播业务采用PC5单播方式发送的情况下，特别的，该第一多播广播业务是连接态UE接收的多播业务，通过单播承载与一个PC5组播的MBS RB绑定，指示该单播承载用于其绑定的PC5组播的MBS RB对应的业务转发。
当然，对于连接态UE接收的多播业务，relay UE在PC5接口可以同时使用组播(groupcast)和unicast进行转发。此时，groupcast是点对多点(Point To Multipoint，PTM)调度，unicast相当于用于绑定的点对点单脚(Point To Point leg，PTP leg)的传输。
可选地，该实施例中，所述多播广播控制信息采用以下至少一种方式发送：
PC5单播；
PC5组播；
PC5广播。
即，relay UE通过单播、组播或广播中至少一种方式向remote UE发送多播广播控制信息。
其中，relay UE采用PC5单播(unicast)的方式发送多播广播控制信息，可以是在通过MBS forwarding response反馈第一请求信息的确认响应时，由该MBS forwarding response携带多播广播控制信息一起发送。
relay UE采用PC5组播(groupcast)或者PC5广播(broadcast)的方式发送多播广播控制信息，相较于PC5unicast的方式能够具有更高的传输效率。
可选地，在所述多播广播控制信息采用PC5组播方式或者PC5广播方式发送的情况下，
所述多播广播控制信息基于第二组标识发送，且所述多播广播控制信息 包括多个多播广播业务的信息；其中，所述第二组标识的分配独立于TMGI；或者，
所述多播广播控制信息基于所述第一组标识发送，且所述多播广播控制信息包括与所述第一组标识对应的多播广播业务的信息。
这样，对于PC5 groupcast或者PC5 broadcast方式发送该多播广播控制信息，可实现为：
一是，由relay UE基于第二组标识，将包括多个多播广播业务的信息(即对应多个TMGI的配置)的多播广播控制信息发送给多个remote UE。此时，第二组标识的分配独立于TMGI，该多个remote UE具有同一个第二组标识，可以对相同或不同的TMGI业务感兴趣。可以由定义或预配置确定，也可以由relay UE通过unicast signaling发送给remote UE。而该多个多播广播业务，可以是relay UE当前提供转发的所有业务；也可以是relay UE能够提供转发的所有业务，其中，即使有一些TMGI业务没有实时转发，也能够以特殊标记区分进行中(on-going)和暂停(suspend)，on-going代表已经在转发的TMGI业务，suspend代表可以转发但由于还没有UE感兴趣，但remote UE可以请求转发。
二是，由relay UE基于第一组标识，将包括一个多播广播业务的信息(即对应该第一组标识的一个TMGI的配置)的多播广播控制信息发送给多个remote UE。此时，第一组标识的分配基于TMGI，则该多个remote UE具有同一个第一组标识，即多个remote UE对同样的TMGI业务感兴趣。且，为了区分多播广播控制信息和多播广播业务传输，为多播广播控制信息和多播广播业务规定不同的逻辑信道，由LCID来区分，例如：显示给出多播广播控制信息和多播广播业务的LCID各自数值；或者，定义或配置多播广播控制信息的LCID(如LCID＝0)，配置或默认多播广播业务的LCID，其中默认多播广播业务的LCID即如果多播广播业务预留LCID 39-42，在未配置时默认使用LCID39-42，而配置就可以告知只是用预留LCID的LCID39-40。
该实施例中，基于L3relay架构，relay UE发送多播广播控制信息的协议栈架构是L3分割，如图3所示；relay UE发送多播广播业务的协议栈架构也是L3分割，如图4所示。
此外，该实施例中，可选地，在步骤201之后，所述方法还包括：
所述第一终端在通过所述第一请求信息向所述第二终端请求进行第一多播广播业务的转发的情况下，接收所述第二终端转发的第一多播广播业务。
也就是，relay UE对于remote UE请求转发的感兴趣的多播广播业务，会向remote UE进行转发，如在该多播广播业务开始发送后转发该多播广播业务给remote UE。相应的，remote UE会接收relay UE转发的第一多播广播业务。
其中，relay UE可读取MCCH，来获得多播广播业务转发的配置。这样，relay UE在第一多播广播业务开始在Uu接口发送时，通过获得的配置进行接收及转发处理。
对于relay UE采用groupcast方式转发第一多播广播业务，可选地，所述第一多播广播业务是所述第二终端在Uu接口接收到所述第一多播广播业务后，基于第一组标识转发的。
这样，针对第一多播广播业务，relay UE能够将接收的第一多播广播业务放到对应的PC5承载上通过第一组标识(PC5 group layer-2 ID)传输给感兴趣的remote UE。
为确保packet级别的业务连续性，所述第一多播广播业务的同一个数据包在PC5接口使用的PDCP SN与Uu接口使用的PDCP SN相同；和/或，
所述第一多播广播业务的同一个数据包在PC5接口使用的RLC SN与Uu接口使用的RLC SN相同。
也就是，relay UE从Uu接口接收到的PDCP SN号，可以继续保持，在PC5接口使用相同的PDCP SN号进行数据的发送，这样，Uu的一个数据包和PC5接口转发的数据包，只要PDCP SN相同就一定是同一个数据包，因此可以基于PDCP SN进行数据包的排序和重复删除等操作，在remote UE多路同时接收时达到重复(duplication)效果，在remote UE由一条路径切换到另一条路径时，也能确保一定的业务连续性。而relay UE从Uu接口接收到的RLC SN号，可以继续保持，在PC5接口使用相同的RLC SN号进行数据的发送，这样，Uu的一个数据包和PC5接口转发的数据包，只要RLC SN相同就一定是同一个数据包，因此可以基于RLC SN进行数据包的排序和重复 删除等操作，在remote UE多路同时接收时达到duplication效果，在remote UE由一条路径切换到另一条路径时，也能确保一定的业务连续性。
其中，对于broadcast业务的转发，由于broadcast一般是成片连续发送，即一个区域内同频小区都是发送该broadcast TMGI业务，这样能确保UE在这个频点上移动时，可以连续的接收该TMGI业务，因此对于broadcast TMGI业务会通过显示的指示，表明该TMGI业务的PDCP SN/RLC SN是否和周围邻小区是同步。此时，如果指示SN同步，相当于UE由小区1(cell1)下的relay1到cell2(cell1的邻小区)下移动或者同时接收时，也可以使用PDCP/RLC SN连续排序的特性，进一步提升业务连续性；如果指示不同步，则relay UE不能做多路径合并，只能分别接收，由业务层再处理和排序，在切换路径时，也需要将RLC和PDCP都重建操作，在新路径再重新接收。
而且，如果有PC5 DRX相关参数的配置，则relay UE按照DRX pattern进行数据包发送。具体的，只在活跃时期(Active time)期间进行数据包发送，而在非活跃时期(non-active time)期间，数据包需要缓存，等待下一个on周期。其中，如果数据包在存储的过程中超时(丢弃计时器(discard timer)的长度可以来自于网络侧配置，QoS参数，或者relay UE实现)，则删除数据包或者为了确保SN连续继续传输。
remote UE侧，remote UE获得PC5 group layer-2 ID之后，在没有PC5 DRX相关参数配置的情况下，持续在所有资源池位置监听PC5 group layer-2 ID的调度和数据包；在配置了PC5 DRX相关参数的情况下，仅在active time期间进行PC5 group layer-2 ID的调度和数据包监听。remote UE获得多播广播控制信息中的MRB/MTCH逻辑信道相关参数之后，按照数目和LCID分别建立L2接收侧的实体，如媒体接入控制(Medium Access Control，MAC)/RLC/PDCP/potential SDAP等，其中SDAP层不一定需要。
其中，remote UE在一个MTCH接收到第一个数据包，则将第一个数据包的RLC SN设置为RLC接收实体侧变量接收侧下一个重组(RX_Next_Reassembly)和接收侧下一个最高(RX_Next_Highest)变量的初始值。remote UE在一个MTCH接收到第一个数据包，则根据第一个数据包的PDCP SN，将RX_NEXT变量初始值设置为(该SN+1)模SN空间大小， 接收侧提供(RX_DELIV)变量初始值设置为(该SN空间大小的一半)模SN空间大小，同时需要确保以上两个变量计算出的计数(COUNT)值应该为非负数。其中，SN空间大小与SN长度有关，例如12bit SN长度，SN空间大小为212＝4096。
可选地，该实施例中，在步骤201之后，所述方法还包括：
所述第一终端接收所述第一多播广播业务对应的小区标识。
如此，relay UE通过告知remote UE第一多播广播业务对应的小区标识，如演进型-通用移动通信系统陆地无线接入网小区全局标识(E-UTRAN Cell Global Identifier，ECGI)，可使remote UE知道PDCP SN和/或RLC SN是和哪个小区保持的一致，便于多路径同时接收或者多路径切换时，对相同小区的识别，例如由relay切换到该小区下，或者由该小区下切换到relay时。当然，
其中，小区标识可是在unicast信令交互，或者discovery过程，或者多播广播控制信息发送中携带。如此，通过获取该小区标识，remote UE移动到该小区，可以直接接收MBS业务不用再次读取配置。
还应该了解的是，该实施例中，对multicast业务感兴趣的remote UE，需要使用非接入服务(non-access-stratum，NAS)过程，向核心网发起加入(join)multicast TMGI的过程，让核心网知道这个UE对这个TMGI感兴趣，从而后续等该multicast业务激活时，核心网才会寻呼对该multicast业务感兴趣的remote UE进行业务接收。其中，remote UE可在链路条件好的时候，自己进行join过程；或者，通过PC5接口进行交互，向relay UE告知自己对一个multicast TMGI感兴趣，由relay UE发起自己的NAS过程，向核心网进行join过程。当然，这两种join过程可以都进行，便于remote UE自己从Uu接口收TMGI activation寻呼，或者relay UE从Uu接口接收该TMGI激活(activation)寻呼，或者remote UE和relay UE同时收寻呼，以防错过。
join过程之后，如果multicast业务激活，核心网会寻呼相关订阅的UE，则remote UE或者relay UE会接收到寻呼消息，开始准备接收multicast业务。如果该multicast业务支持multicast for idle/inactive(即multicast TMGI for idle/inactive)，则relay UE接收MCCH，可先进入连接态通过专用信令获得 MCCH，再释放回idle/inactive接收数据；或者若MCCH是公共广播信令发生的，relay UE读取即可。但无论怎样，relay UE都可以获得MCCH后，发送多播广播控制信息给remote UE，多播广播控制信息的发送如上所述，在此不再赘述。Multicast TMGI for idle/inactive的多播广播业务(MTCH)的接收和转发也如上所示，在此不再赘述。
而如果multicast业务支持仅用于连接终端的组播(multicast for only connected UE)(即multicast TMGI for only connected UE)，relay UE需要进入连接态进行MTCH接收，且MTCH不仅可以配置PTM(point to Multi-point)leg，还可能同时配置PTP(Point to Point)leg，网络设备为了维持业务的QoS，可能在PTM leg和PTP leg之间做动态切换。其中，relay UE将接收的MTCH转发给remote UE，可以有：
方式一、使用groupcast将接收的MTCH转发。其中，group中的每个remote UE分配的反馈位置可以相同也可以不同。当然，考虑为group中的每个remote UE分配不同的反馈位置，relay UE能够通过知道具体哪个UE出错，以及多少个UE出错，尽量进行多次混合自动重传请求(Hybrid automatic repeat request，HARQ)重传，以提升可靠性，确保所有remote UE都尽量达到QoS需求。
方式二、在groupcast Layer-2 ID(即第一组标识)的基础上，为感兴趣该multicast业务的所有或者部分remote UE(如果是部分，则意味着选取链路条件较差的一些UE)建立unicast连接和路径，并通过unicast PC5 RRC进行相关的PTP leg配置以及PTP leg和PTM leg的绑定关系，即PTP leg可以配置为RLC确认模式(Acknowledged Mode，AM)，PTP leg一定跟一个PTM leg的MRB进行绑定，两个leg具有相同的PDCP实体，从PTP leg接收到的数据与从PTM leg接收到的数据在同一个PDCP实体按照PDCP SN序号进行重排序和重复检测删除等操作，从而达到QoS需求，如图5所示，以一个MRB为例说明分成两条路径(split two legs)的工作示意图，其中两条leg可以发重复数据(duplicated data)以达到更好的业务可靠性。
另外，该实施例中，在步骤201之后，所述方法还包括：
所述第一终端在通过所述第一请求信息向所述第二终端请求停止转发所 述第一多播广播业务，或者，所述第一多播广播业务结束的情况下，停止接收所述第一多播广播业务。
remote UE感兴趣的业务发生变更，如对第一多播广播业务不再感兴趣，则会发送第一请求信息向relay UE请求停止转发该第一多播广播业务，以避免relay UE无效转发。remote UE在发送第一请求信息，请求relay UE停止转发第一多播广播业务后，remote UE可自主停止对该第一多播广播业务的接收；或者，remote UE了解到第一多播广播业务结束，remote UE也可自主停止对该第一多播广播业务的接收。
relay UE确定第一多播广播业务对应的所有终端无业务需求(也可以理解为，对第一多播广播业务感兴趣的全部remote UE不再对第一多播广播业务感兴趣)，或者，第一多播广播业务结束的情况下，停止转发第一多播广播业务。
然而，若第一多播广播业务采用PC5广播方式转发，且业务未结束，relay UE仅收到个别remote UE基于自身需求发送的停止转发的请求，考虑到还会存在其他对该第一多播广播业务感兴趣的remote UE情况，relay UE可以继续保持转发，并且relay UE会发送询问信息至对该第一多播广播业务感兴趣的所有remote UE，询问其是否具有第一多播广播业务的转发需求，以确定是否第一多播广播业务对应的所有终端无业务需求。故，可选地，在步骤201之后，所述方法还包括：
所述第一终端接收由所述第二终端发送的询问信息，所述询问信息用于询问所述第一终端是否具有所述第一多播广播业务的转发需求；
所述第一终端在具有所述第一多播广播业务的转发需求的情况下，发送所述询问信息的确认信息至所述第二终端。
也就是，remote UE若具有转发需求，会反馈确认信息，若没有转发需求则不会反馈任何信息。这样，relay UE可以在未接收到任一remote UE反馈确认信息的情况下，确定无需再对该第一多播广播业务转发。当然，为避免对询问信息反馈的长时间等待，会基于预设时间内是否接收到任一remote UE反馈的确认信息来做停止转发的判断。
该实施例中，可以采取独立的过程，或者采取统一的过程，请求多播广 播业务的转发或者停止转发。例如，对于MBS forwarding request消息，remote UE每次感兴趣的业务发生变更即上报，每次上报都携带最新感兴趣的业务相关信息，如果不再感兴趣，则从上报的信息中去除不再感兴趣的业务相关信息。故，上报的信息可作为第一请求信息用于向relay UE请求多播广播业务的转发或者停止转发。这样，relay UE就可以根据最新上报信息，获知哪些业务已经不再感兴趣，哪些业务是新感兴趣的，对于新感兴趣的业务，按照上述内容完成业务接收；对于不再感兴趣的业务，relay UE通过询问信息确定该业务是否还有其它remote UE感兴趣，如果有则维持现有转发，如果没有则可以停止转发。
也可以采取消息里，删除+增加/更新/修改(delete+add/update/modify)的信令方式，显示列出哪些业务不再感兴趣，哪些业务新加入，或者变化等，relay UE收到后，分别针对新感兴趣的业务、不再感兴趣的业务进行如上处理。
另外，该实施例中，在relay UE已经在转发多播广播业务的情况下，若一个新的remote UE对该relay UE已经在转发多播广播业务感兴趣，则新的remote UE：
一是，可以发送其第一请求信息，请求relay UE向其转发该多播广播业务。例如，通过MBS forwarding request消息携带第一请求信息，上报自己感兴趣的业务相关信息(如TMGI)，relay UE对已经在转发的业务，直接回复确认(Acknowledgement)，该Acknowledgement携带多播广播控制信息，或者携带MCCH的对应配置，例如MCCH Layer-2 ID。该新的remote UE收到之后，读取多播广播控制信息获得配置，使用TMGI对应的第一组标识接收业务数据。此时，relay UE对于当前有多少个remote UE感兴趣正在转发的TMGI业务掌握非常精准，便于它判断停止。
二是，可以通过广播，直接读取多播广播控制信息和对应的多播广播业务数据，无需显示告知relay UE知道。这里，relay UE是在经第一个remote UE请求该多播广播业务转发之后，对已经在转发的多播广播业务，以及多播广播控制信息都是不断进行广播的，例如，周期性发送的发现(discovery)消息里携带。如此，能够节省后来的remote UE和relay UE之间的交互时延以 及信令开销。当然，后来的remote UE和relay UE之间缺乏显示沟通过程，导致relay UE并不能了解有多少个UE感兴趣TMGI业务，当它希望停止TMGI业务转发时，需要计数(Counting)周围UE(即发送询问信息至周围UE)，例如也是在discovery消息里，on-going TMGI里增加1bit指示，要求周围UE尽快上报是否对该TMGI感兴趣，如果感兴趣则remote UE立即通过unicast上报给relay UE，否则如果在一段时间内relay UE没有接收到任何remote UE的感兴趣上报，认为没有UE感兴趣，可以停止转发，节省资源。
对于业务结束，一方面可通过MCCH通知(notification)方式通知，则由于relay UE需要随时监听MCCH notification和MCCH变更relay UE也是知道业务停止的，因此relay UE会在业务停止之后，回收PC5资源，例如回收与该TMGI相关的group layer-2 ID(即PC5 group layer-2 ID)等信息，停止后续的转发；如果业务结束是通过MTCH/MRB中的数据PDU进行通知的，例如通过MAC CE进行业务停止指示，则relay UE由于可以解析MAC CE，因此它也知道业务停止信息，可以进行停止和资源回收。
综上，本申请实施例的方法，能够使得remote UE可以接收来自网络设备的多播广播业务，提升了传输效率和覆盖，保障了remote UE的业务体验和系统效率。
如图6所示，本申请实施例的一种多播广播业务的发送方法，包括：
步骤601，第二终端接收第一终端的第一请求信息；
其中，所述第一终端与所述第二终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
如此，第二终端(即relay UE)能够接收第一终端(即remote UE)的第一请求信息，了解remote UE期待的对第一多播广播业务的接收或者停止接收，以便后续进行处理，使得remote UE可以接收来自网络侧的多播广播业务。
可选地，所述第一请求信息通过预设的PC5单播信令发送。
可选地，所述第一请求信息包括以下至少一项：
所述第一多播广播业务的TMGI；
所述第一多播广播业务的频点信息；
所述第一多播广播业务的发送区域信息；
所述第一多播广播业务的接收区域信息；
所述第一多播广播业务的优先级信息。
可选地，在所述第二终端接收第一终端的第一请求信息的步骤之前，所述方法还包括：
所述第二终端发送能力信息，所述能力信息用于表示所述第二终端转发多播广播业务的能力。
可选地，所述能力信息包括以下至少一项：
支持转发的多播广播业务的类型；
支持转发的多播广播业务列表；
支持转发的多播广播业务的数量；
当前转发的多播广播业务的相关信息。
可选地，所述第二终端接收第一终端的第一请求信息之后，还包括：
所述第二终端根据所述第一请求信息反馈响应信息至所述第一终端；
其中，所述响应信息用于指示所述第二终端是否提供所述第一多播广播业务的转发。
可选地，在所述第二终端根据所述第一请求信息反馈响应信息至所述第一终端的步骤之前，所述方法还包括：
所述第二终端在所述第一请求信息向所述第二终端请求进行第一多播广播业务的转发的情况下，根据所述第一请求信息进行所述第一多播广播业务的尝试搜索；
所述第二终端在查找到所述第一多播广播业务的源小区，且接收到所述第一多播广播业务的情况下，确定所述响应信息为确认响应；
所述第二终端在未查找到所述第一多播广播业务的源小区的情况下，确定所述响应信息为否定响应。
可选地，在所述第二终端接收第一终端的第一请求信息的步骤之后，所述方法还包括：
所述第二终端发送多播广播控制信息至所述第一终端；
其中，所述多播广播控制信息包括以下至少一项：
与TMGI对应的逻辑信道相关参数；
与TMGI对应的DRX相关参数；
与TMGI对应的无线承载相关参数；
与TMGI对应的第一组标识。
可选地，所述多播广播控制信息采用以下至少一种方式发送：
PC5单播；
PC5组播；
PC5广播。
可选地，在所述多播广播控制信息采用PC5组播方式或者PC5广播方式发送的情况下，
所述多播广播控制信息基于第二组标识发送，且所述多播广播控制信息包括多个多播广播业务的信息；其中，所述第二组标识的分配独立于TMGI；或者，
所述多播广播控制信息基于所述第一组标识发送，且所述多播广播控制信息包括与所述第一组标识对应的多播广播业务的信息。
可选地，所述与TMGI对应的DRX相关参数为Uu DRX相关参数或者PC5 DRX相关参数。
可选地，在所述第二终端接收第一终端的第一请求信息的步骤之后，所述方法还包括：
所述第二终端在所述第一请求信息向所述第二终端请求进行第一多播广播业务的转发的情况下，转发所述一多播广播业务。
可选地，所述第一多播广播业务是所述第二终端在Uu接口接收到所述第一多播广播业务后，基于第一组标识转发的。
可选地，所述第一多播广播业务的同一数据包在PC5接口使用的PDCP SN与Uu接口使用的PDCP SN相同；和/或，
所述第一多播广播业务的同一数据包在PC5接口使用的RLC SN与Uu接口使用的RLC SN相同。
可选地，在所述第二终端接收第一终端的第一请求信息的步骤之后，所述方法还包括：
所述第二终端发送所述第一多播广播业务对应的小区标识至所述第一终端。
可选地，所述无线承载相关参数包括以下至少一项：
单播承载配置；
组播承载配置；
其中，所述第一多播广播业务采用PC5单播方式发送的情况下，单播承载与一个PC5组播的MBS RB绑定。
可选地，在所述第二终端接收第一终端的第一请求信息的步骤之后，所述方法还包括：
所述第二终端在确定所述第一多播广播业务对应的所有终端无业务需求，或者，所述第一多播广播业务结束的情况下，停止转发所述第一多播广播业务。
可选地，所述第二终端确定所述第一多播广播业务对应的所有终端无业务需求，包括：
所述第二终端在所述第一多播广播业务采用PC5广播方式转发的情况下，发送询问信息至所述第一多播广播业务对应的所有终端，所述询问信息用于询问终端是否具有所述第一多播广播业务的转发需求；
所述第二终端在未接收到任一终端发送的所述询问信息的确认信息的情况下，确定所述第一多播广播业务对应的所有终端无业务需求。
需要说明的是，该方法是与上述由第一终端执行的多播广播业务的接收方法配合实现的，上述方法实施例中，第二终端的实现方式适用于该方法，也能达到相同的技术效果。
如图7所示，本申请实施例的一种多播广播业务的发送方法，包括：
步骤701，网络设备发送MCCH至第二终端；
其中，所述第二终端用于接收第一终端的第一请求信息，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发，所述第一终端与所述第二终端之间通过旁链路通信；
所述MCCH用于确定多播广播控制信息。
这里，第一终端(即remote UE)通过向第二终端(即relay UE)发送第 一请求信息，向relay UE请求进行第一多播广播业务的转发或者停止转发，relay UE了解到remote UE的需求，通过接收到的网络设备的MCCH确定多播广播控制信息，来为remote UE提供后续处理的配置，使得remote UE可以接收来自网络侧的多播广播业务。
可选地，所述多播广播控制信息包括以下至少一项：
与TMGI对应的逻辑信道相关参数；
与TMGI对应的DRX相关参数；
与TMGI对应的无线承载相关参数；
与TMGI对应的第一组标识。
需要说明的是，该方法是与上述由第一终端执行的多播广播业务的接收方法配合实现的，上述方法实施例中，网络设备的实现方式适用于该方法，也能达到相同的技术效果。
还需要说明的是，本申请实施例提供的多播广播业务的发送方法，执行主体可以为多播广播业务的发送装置，或者该多播广播业务的发送装置中的用于执行加载多播广播业务的发送方法的控制模块。本申请实施例中以多播广播业务的发送装置执行加载多播广播业务的发送方法为例，说明本申请实施例提供的多播广播业务的发送方法。
如图8所示，本申请实施例的多播广播业务的接收装置800，包括：
第一发送模块810，用于发送第一请求信息至第二终端；
其中，所述第二终端与第一终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
可选地，所述第一请求信息通过预设的PC5单播信令发送。
可选地，所述第一请求信息包括以下至少一项：
所述第一多播广播业务的临时移动组标识TMGI；
所述第一多播广播业务的频点信息；
所述第一多播广播业务的发送区域信息；
所述第一多播广播业务的接收区域信息；
所述第一多播广播业务的优先级信息。
可选地，所述第一终端发送第一请求信息至第二终端之前，还包括：
所述第一终端接收所述第二终端发送的能力信息，所述能力信息用于表示所述第二终端转发多播广播业务的能力。
可选地，所述能力信息包括以下至少一项：
支持转发的多播广播业务的类型；
支持转发的多播广播业务列表；
支持转发的多播广播业务的数量；
当前转发的多播广播业务的相关信息。
可选地，所述装置还包括：
响应信息接收模块，用于接收所述第二终端根据所述第一请求信息反馈的响应信息；
其中，所述响应信息用于指示所述第二终端是否提供所述第一多播广播业务的转发。
可选地，所述装置还包括：
第一接收模块，用于接收所述第二终端发送的多播广播控制信息；
其中，所述多播广播控制信息包括以下至少一项：
与TMGI对应的逻辑信道相关参数；
与TMGI对应的DRX相关参数；
与TMGI对应的无线承载相关参数；
与TMGI对应的第一组标识。
可选地，所述多播广播控制信息采用以下至少一种方式发送：
PC5单播；
PC5组播；
PC5广播。
可选地，在所述多播广播控制信息采用PC5组播方式或者PC5广播方式发送的情况下，
所述多播广播控制信息基于第二组标识发送，且所述多播广播控制信息包括多个多播广播业务的信息；其中，所述第二组标识的分配独立于TMGI；或者，
所述多播广播控制信息基于所述第一组标识发送，且所述多播广播控制 信息包括与所述第一组标识对应的多播广播业务的信息。
可选地，所述与TMGI对应的DRX相关参数为Uu DRX相关参数或者PC5 DRX相关参数。
可选地，所述装置还包括：
第一业务处理模块，用于在通过所述第一请求信息向所述第二终端请求进行第一多播广播业务的转发的情况下，接收所述第二终端转发的第一多播广播业务。
可选地，所述第一多播广播业务是所述第二终端在Uu接口接收到所述第一多播广播业务后，基于第一组标识转发的。
可选地，所述第一多播广播业务的同一个数据包在PC5接口使用的PDCP SN与Uu接口使用的PDCP SN相同；和/或，
所述第一多播广播业务的同一个数据包在PC5接口使用的RLC SN与Uu接口使用的RLC SN相同。
可选地，所述装置还包括：
小区标识接收模块，用于接收所述第一多播广播业务对应的小区标识。
可选地，所述无线承载相关参数包括以下至少一项：
单播承载的配置信息；
组播承载的配置信息；
其中，所述第一多播广播业务采用PC5单播方式发送的情况下，所述单播承载与一个PC5组播的MBS RB绑定。
可选地，所述装置还包括：
第二业务处理模块，用于在通过所述第一请求信息向所述第二终端请求停止转发所述第一多播广播业务，或者，所述第一多播广播业务结束的情况下，停止接收所述第一多播广播业务。
可选地，所述装置还包括：
询问信息接收模块，用于接收由所述第二终端发送的询问信息，所述询问信息用于询问所述第一终端是否具有所述第一多播广播业务的转发需求；
询问反馈模块，用于在具有所述第一多播广播业务的转发需求的情况下，发送所述询问信息的确认信息至所述第二终端。
该装置，通过向relay UE请求进行多播广播业务的转发或者停止转发，在relay UE基于请求进行多播广播业务的转发或者停止转发后，接收来自网络侧的多播广播业务，提升了传输效率和覆盖，保障了remote UE的业务体验和系统效率。
需要说明的是，该装置可执行上述由第一终端执行的多播广播业务的接收方法，上述方法实施例的实现方式适用于该装置，也能达到相同的技术效果。
本申请实施例中的多播广播业务的接收装置可以是装置，具有操作系统的装置或电子设备，也可以是终端中的部件、集成电路、或芯片。该装置或电子设备可以是移动终端，也可以为非移动终端。示例性的，移动终端包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例提供的多播广播业务的接收装置能够实现图2至图5的方法实施例中第一终端实现的各个过程，为避免重复，这里不再赘述。
如图9所示，本申请实施例一种多播广播业务的发送装置900，包括：
第二接收模块910，用于接收第一终端的第一请求信息；
其中，所述第一终端与第二终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
可选地，所述第一请求信息通过预设的PC5单播信令发送。
可选地，所述第一请求信息包括以下至少一项：
所述第一多播广播业务的TMGI；
所述第一多播广播业务的频点信息；
所述第一多播广播业务的发送区域信息；
所述第一多播广播业务的接收区域信息；
所述第一多播广播业务的优先级信息。
可选地，所述装置还包括：
能力信息发送模块，用于发送能力信息，所述能力信息用于表示所述第 二终端转发多播广播业务的能力。
可选地，所述能力信息包括以下至少一项：
支持转发的多播广播业务的类型；
支持转发的多播广播业务列表；
支持转发的多播广播业务的数量；
当前转发的多播广播业务的相关信息。
可选地，所述装置还包括：
响应信息反馈模块，用于根据所述第一请求信息反馈响应信息至所述第一终端；
其中，所述响应信息用于指示所述第二终端是否提供所述第一多播广播业务的转发。
可选地，所述装置还包括：
搜索模块，用于在所述第一请求信息向所述第二终端请求进行第一多播广播业务的转发的情况下，根据所述第一请求信息进行所述第一多播广播业务的尝试搜索；
第一确定模块，用于在查找到所述第一多播广播业务的源小区，且接收到所述第一多播广播业务的情况下，确定所述响应信息为确认响应；
第二确定模块，用于在未查找到所述第一多播广播业务的源小区的情况下，确定所述响应信息为否定响应。
可选地，所装置还包括：
第二发送模块，用于发送多播广播控制信息至所述第一终端；
其中，所述多播广播控制信息包括以下至少一项：
与TMGI对应的逻辑信道相关参数；
与TMGI对应的DRX相关参数；
与TMGI对应的无线承载相关参数；
与TMGI对应的第一组标识。
可选地，所述多播广播控制信息采用以下至少一种方式发送：
PC5单播；
PC5组播；
PC5广播。
可选地，在所述多播广播控制信息采用PC5组播方式或者PC5广播方式发送的情况下，
所述多播广播控制信息基于第二组标识发送，且所述多播广播控制信息包括多个多播广播业务的信息；其中，所述第二组标识的分配独立于TMGI；或者，
所述多播广播控制信息基于所述第一组标识发送，且所述多播广播控制信息包括与所述第一组标识对应的多播广播业务的信息。
可选地，所述与TMGI对应的DRX相关参数为Uu DRX相关参数或者PC5 DRX相关参数。
可选地，所述装置还包括：
业务转发模块，用于在所述第一请求信息向所述第二终端请求进行第一多播广播业务的转发的情况下，转发所述一多播广播业务。
可选地，所述第一多播广播业务是所述第二终端在Uu接口接收到所述第一多播广播业务后，基于第一组标识转发的。
可选地，所述第一多播广播业务的同一数据包在PC5接口使用的PDCP SN与Uu接口使用的PDCP SN相同；和/或，
所述第一多播广播业务的同一数据包在PC5接口使用的RLC SN与Uu接口使用的RLC SN相同。
可选地，所述装置还包括：
小区标识发送模块，用于发送所述第一多播广播业务对应的小区标识至所述第一终端。
可选地，所述无线承载相关参数包括以下至少一项：
单播承载配置；
组播承载配置；
其中，所述第一多播广播业务采用PC5单播方式发送的情况下，单播承载与一个PC5组播的MBS RB绑定。
可选地，所述装置还包括：
第三业务处理模块，用于在确定所述第一多播广播业务对应的所有终端 无业务需求，或者，所述第一多播广播业务结束的情况下，停止转发所述第一多播广播业务。
可选地，所述第三业务处理模块包括：
询问信息发送子模块，用于在所述第一多播广播业务采用PC5广播方式转发的情况下，发送询问信息至所述第一多播广播业务对应的所有终端，所述询问信息用于询问终端是否具有所述第一多播广播业务的转发需求；
处理子模块，用于在未接收到任一终端发送的所述询问信息的确认信息的情况下，确定所述第一多播广播业务对应的所有终端无业务需求。
该装置通过接收relay UE的请求，了解remote UE期待的对第一多播广播业务的接收或者停止接收，以便后续进行处理，使得remote UE接收来自网络侧的多播广播业务，提升了传输效率和覆盖，保障了remote UE的业务体验和系统效率。
需要说明的是，该装置可执行上述由第二终端执行的多播广播业务的接收方法，上述方法实施例的实现方式适用于该装置，也能达到相同的技术效果。本申请实施例中的多播广播业务的发送装置可以是装置，具有操作系统的装置或电子设备，也可以是终端中的部件、集成电路、或芯片。该装置或电子设备可以是移动终端，也可以为非移动终端。示例性的，移动终端包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例提供的多播广播业务的发送装置能够实现图3至图6的方法实施例中第二终端实现的各个过程，为避免重复，这里不再赘述。
如图10所示，本申请实施例的多播广播业务的发送装置1000，包括：
第三发送模块1010，用于发送MCCH至第二终端；
其中，所述第二终端用于接收第一终端的第一请求信息，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发，所述第一终端与所述第二终端之间通过旁链路通信；
所述MCCH用于确定多播广播控制信息。
可选地，所述多播广播控制信息包括以下至少一项：
与TMGI对应的逻辑信道相关参数；
与TMGI对应的DRX相关参数；
与TMGI对应的无线承载相关参数；
与TMGI对应的第一组标识。
这里，该装置发送MCCH至第二终端，由于第二终端是接收第一终端发送的第一请求信息的终端，第一请求信息又是第一终端向第二终端请求进行第一多播广播业务的转发或者停止转发的，第二终端了解到remote UE的需求，结合该MCCH，来为第一终端提供后续处理，使得第一终端可以接收来自网络侧的多播广播业务。
需要说明的是，该装置可执行上述由网络设备执行的多播广播业务的发送方法，上述方法实施例的实现方式适用于该装置，也能达到相同的技术效果。
可选的，如图11所示，本申请实施例还提供一种通信设备，包括处理器1101，存储器1102，存储在存储器1102上并可在所述处理器1101上运行的程序或指令，例如，该通信设备1100为终端时，该程序或指令被处理器1101执行时实现上述由第一终端执行的多播广播业务的接收方法，或者由第二终端执行的多播广播业务的发送方法实施例的各个过程，且能达到相同的技术效果。该通信设备1100为网络设备时，该程序或指令被处理器1101执行时实现上述由网络设备执行的多播广播业务的发送方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，通信接口用于发送第一请求信息至第二终端；其中，所述第二终端与第一终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。该终端实施例是与上述由第一终端执行的方法实施例对应的，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。
本申请实施例还提供一种终端，包括处理器和通信接口，通信接口用于接收第一终端发送的第一请求信息；其中，所述第一终端与第二终端之间通 过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。该终端实施例是与上述由第二终端执行的方法实施例对应的，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。
具体地，图12为实现本申请各个实施例的一种终端的硬件结构示意图。
该终端1200包括但不限于：射频单元1201、网络模块1202、音频输出单元1203、输入单元1204、传感器1205、显示单元1206、用户输入单元1207、接口单元1208、存储器1209、以及处理器1210等中的至少部分部件。
本领域技术人员可以理解，终端1200还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1210逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图12中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1204可以包括图形处理器(Graphics Processing Unit，GPU)12041和麦克风12042，图形处理器12041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1206可包括显示面板12061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板12061。用户输入单元1207包括触控面板12071以及其他输入设备12072。触控面板12071，也称为触摸屏。触控面板12071可包括触摸检测装置和触摸控制器两个部分。其他输入设备12072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1201将来自网络侧设备的下行数据接收后，给处理器1210处理；另外，将上行的数据发送给网络侧设备。通常，射频单元1201包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1209可用于存储软件程序或指令以及各种数据。存储器1209可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像 播放功能等)等。此外，存储器1209可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器1210可包括一个或多个处理单元；可选的，处理器1210可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1210中。
其中，若该终端执行第一终端对应的方法，射频单元1201，用于发送第一请求信息至第二终端；
其中，所述第二终端与第一终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
该终端，通过向relay UE请求进行多播广播业务的转发或者停止转发，在relay UE基于请求进行多播广播业务的转发或者停止转发后，接收来自网络侧的多播广播业务，提升了传输效率和覆盖，保障了remote UE的业务体验和系统效率。
若该终端执行第二终端对应的方法，射频单元1201用于接收第一终端发送的第一请求信息；
其中，所述第一终端与第二终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
该终端，通过接收relay UE的请求，了解remote UE期待的对第一多播广播业务的接收或者停止接收，以便后续进行处理，使得remote UE接收来自网络侧的多播广播业务，提升了传输效率和覆盖，保障了remote UE的业务体验和系统效率。
本申请实施例还提供一种网络设备，包括处理器和通信接口，通信接口用于发送MCCH至第二终端；其中，所述第二终端用于接收第一终端的第一请求信息，所述第一请求信息用于向所述第二终端请求进行第一多播广播业 务的转发或者停止转发，所述第一终端与所述第二终端之间通过旁链路通信；所述MCCH用于确定多播广播控制信息。
该网络设备实施例是与上述网络设备方法实施例对应的，上述方法实施例的各个实施过程和实现方式均可适用于该网络设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络设备。如图13所示，该网络设备1300包括：天线131、射频装置132、基带装置133。天线131与射频装置132连接。在上行方向上，射频装置132通过天线131接收信息，将接收的信息发送给基带装置133进行处理。在下行方向上，基带装置133对要发送的信息进行处理，并发送给射频装置132，射频装置132对收到的信息进行处理后经过天线131发送出去。
上述频带处理装置可以位于基带装置133中，以上实施例中网络设备执行的方法可以在基带装置133中实现，该基带装置133包括处理器134和存储器135。
基带装置133例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图13所示，其中一个芯片例如为处理器134，与存储器135连接，以调用存储器135中的程序，执行以上方法实施例中所示的网络设备操作。
该基带装置133还可以包括网络接口136，用于与射频装置132交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
具体地，本发明实施例的网络设备还包括：存储在存储器135上并可在处理器134上运行的指令或程序，处理器134调用存储器135中的指令或程序执行图7所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述由第一终端执行的方法的步骤，或者实现上述由第二终端执行的方法的步骤，或者实现上述由网络设备执行的方法所述的方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述由第一终端执行的方法的步骤，或者实现上述由第二终端执行的方法的步骤，或者实现上述由网络设备执行的方法所述的方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片、系统芯片、芯片系统或片上系统芯片等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (48)

  1. 一种多播广播业务的接收方法，包括：
    第一终端发送第一请求信息至第二终端；
    其中，所述第一终端与所述第二终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
  2. 根据权利要求1所述的方法，其中，所述第一请求信息通过预设的PC5单播信令发送。
  3. 根据权利要求1所述的方法，其中，所述第一请求信息包括以下至少一项：
    所述第一多播广播业务的临时移动组标识TMGI；
    所述第一多播广播业务的频点信息；
    所述第一多播广播业务的发送区域信息；
    所述第一多播广播业务的接收区域信息；
    所述第一多播广播业务的优先级信息。
  4. 根据权利要求1所述的方法，其中，在所述第一终端发送第一请求信息至第二终端的步骤之前，所述方法还包括：
    所述第一终端接收所述第二终端发送的能力信息，所述能力信息用于表示所述第二终端转发多播广播业务的能力。
  5. 根据权利要求4所述的方法，其中，所述能力信息包括以下至少一项：
    支持转发的多播广播业务的类型；
    支持转发的多播广播业务列表；
    支持转发的多播广播业务的数量；
    当前转发的多播广播业务的相关信息。
  6. 根据权利要求1所述的方法，其中，在所述第一终端发送第一请求信息至第二终端的步骤之后，所述方法还包括：
    所述第一终端接收所述第二终端根据所述第一请求信息反馈的响应信息；
    其中，所述响应信息用于指示所述第二终端是否提供所述第一多播广播业务的转发。
  7. 根据权利要求1所述的方法，其中，在所述第一终端发送第一请求信息至第二终端的步骤之后，所述方法还包括：
    所述第一终端接收所述第二终端发送的多播广播控制信息；
    其中，所述多播广播控制信息包括以下至少一项：
    与TMGI对应的逻辑信道相关参数；
    与TMGI对应的非连续接收DRX相关参数；
    与TMGI对应的无线承载相关参数；
    与TMGI对应的第一组标识。
  8. 根据权利要求7所述的方法，其中，所述多播广播控制信息采用以下至少一种方式发送：
    PC5单播；
    PC5组播；
    PC5广播。
  9. 根据权利要求8所述的方法，其中，在所述多播广播控制信息采用PC5组播方式或者PC5广播方式发送的情况下，
    所述多播广播控制信息基于第二组标识发送，且所述多播广播控制信息包括多个多播广播业务的信息；其中，所述第二组标识的分配独立于TMGI；或者，
    所述多播广播控制信息基于所述第一组标识发送，且所述多播广播控制信息包括与所述第一组标识对应的多播广播业务的信息。
  10. 根据权利要求7所述的方法，其中，所述与TMGI对应的DRX相关参数为Uu DRX相关参数或者PC5 DRX相关参数。
  11. 根据权利要求1所述的方法，其中，在所述第一终端发送第一请求信息至第二终端的步骤之后，所述方法还包括：
    所述第一终端在通过所述第一请求信息向所述第二终端请求进行第一多 播广播业务的转发的情况下，接收所述第二终端转发的第一多播广播业务。
  12. 根据权利要求11所述的方法，其中，所述第一多播广播业务是所述第二终端在Uu接口接收到所述第一多播广播业务后，基于第一组标识转发的。
  13. 根据权利要求11所述的方法，其中，所述第一多播广播业务的同一个数据包在PC5接口使用的分组数据汇聚协议序列号PDCP SN与Uu接口使用的PDCP SN相同；和/或，
    所述第一多播广播业务的同一个数据包在PC5接口使用的无线链路控制序列号RLC SN与Uu接口使用的RLC SN相同。
  14. 根据权利要求1所述的方法，其中，在所述第一终端发送第一请求信息至第二终端的步骤之后，所述方法还包括：
    所述第一终端接收所述第一多播广播业务对应的小区标识。
  15. 根据权利要求7所述的方法，其中，所述无线承载相关参数包括以下至少一项：
    单播承载的配置信息；
    组播承载的配置信息；
    其中，所述第一多播广播业务采用PC5单播方式发送的情况下，所述单播承载与一个PC5组播的多播广播业务无线承载MBS RB绑定。
  16. 根据权利要求1所述的方法，其中，在所述第一终端发送第一请求信息至第二终端的步骤之后，所述方法还包括：
    所述第一终端在通过所述第一请求信息向所述第二终端请求停止转发所述第一多播广播业务，或者，所述第一多播广播业务结束的情况下，停止接收所述第一多播广播业务。
  17. 根据权利要求1所述的方法，其中，在所述第一终端发送第一请求信息至第二终端的步骤之后，所述方法还包括：
    所述第一终端接收由所述第二终端发送的询问信息，所述询问信息用于询问所述第一终端是否具有所述第一多播广播业务的转发需求；
    所述第一终端在具有所述第一多播广播业务的转发需求的情况下，发送所述询问信息的确认信息至所述第二终端。
  18. 一种多播广播业务的发送方法，包括：
    第二终端接收第一终端的第一请求信息；
    其中，所述第一终端与所述第二终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
  19. 根据权利要求18所述的方法，其中，所述第一请求信息通过预设的PC5单播信令发送。
  20. 根据权利要求18所述的方法，其中，所述第一请求信息包括以下至少一项：
    所述第一多播广播业务的TMGI；
    所述第一多播广播业务的频点信息；
    所述第一多播广播业务的发送区域信息；
    所述第一多播广播业务的接收区域信息；
    所述第一多播广播业务的优先级信息。
  21. 根据权利要求18所述的方法，其中，在所述第二终端接收第一终端的第一请求信息的步骤之前，所述方法还包括：
    所述第二终端发送能力信息，所述能力信息用于表示所述第二终端转发多播广播业务的能力。
  22. 根据权利要求21所述的方法，其中，所述能力信息包括以下至少一项：
    支持转发的多播广播业务的类型；
    支持转发的多播广播业务列表；
    支持转发的多播广播业务的数量；
    当前转发的多播广播业务的相关信息。
  23. 根据权利要求18所述的方法，其中，在所述第二终端接收第一终端的第一请求信息的步骤之后，所述方法还包括：
    所述第二终端根据所述第一请求信息反馈响应信息至所述第一终端；
    其中，所述响应信息用于指示所述第二终端是否提供所述第一多播广播业务的转发。
  24. 根据权利要求18所述的方法，其中，在所述第二终端根据所述第一请求信息反馈响应信息至所述第一终端的步骤之前，所述方法还包括：
    所述第二终端在所述第一请求信息向所述第二终端请求进行第一多播广播业务的转发的情况下，根据所述第一请求信息进行所述第一多播广播业务的尝试搜索；
    所述第二终端在查找到所述第一多播广播业务的源小区，且接收到所述第一多播广播业务的情况下，确定所述响应信息为确认响应；
    所述第二终端在未查找到所述第一多播广播业务的源小区的情况下，确定所述响应信息为否定响应。
  25. 根据权利要求18所述的方法，其中，在所述第二终端接收第一终端的第一请求信息的步骤之后，所述方法还包括：
    所述第二终端发送多播广播控制信息至所述第一终端；
    其中，所述多播广播控制信息包括以下至少一项：
    与TMGI对应的逻辑信道相关参数；
    与TMGI对应的DRX相关参数；
    与TMGI对应的无线承载相关参数；
    与TMGI对应的第一组标识。
  26. 根据权利要求25所述的方法，其中，所述多播广播控制信息采用以下至少一种方式发送：
    PC5单播；
    PC5组播；
    PC5广播。
  27. 根据权利要求26所述的方法，其中，在所述多播广播控制信息采用PC5组播方式或者PC5广播方式发送的情况下，
    所述多播广播控制信息基于第二组标识发送，且所述多播广播控制信息包括多个多播广播业务的信息；其中，所述第二组标识的分配独立于TMGI；或者，
    所述多播广播控制信息基于所述第一组标识发送，且所述多播广播控制信息包括与所述第一组标识对应的多播广播业务的信息。
  28. 根据权利要求24所述的方法，其中，所述与TMGI对应的DRX相关参数为Uu DRX相关参数或者PC5 DRX相关参数。
  29. 根据权利要求18所述的方法，其中，在所述第二终端接收第一终端的第一请求信息的步骤之后，所述方法还包括：
    所述第二终端在所述第一请求信息向所述第二终端请求进行第一多播广播业务的转发的情况下，转发所述一多播广播业务。
  30. 根据权利要求29所述的方法，其中，所述第一多播广播业务是所述第二终端在Uu接口接收到所述第一多播广播业务后，基于第一组标识转发的。
  31. 根据权利要求29所述的方法，其中，所述第一多播广播业务的同一数据包在PC5接口使用的PDCP SN与Uu接口使用的PDCP SN相同；和/或，
    所述第一多播广播业务的同一数据包在PC5接口使用的RLC SN与Uu接口使用的RLC SN相同。
  32. 根据权利要求18所述的方法，其中，在所述第二终端接收第一终端的第一请求信息的步骤之后，所述方法还包括：
    所述第二终端发送所述第一多播广播业务对应的小区标识至所述第一终端。
  33. 根据权利要求25所述的方法，其中，所述无线承载相关参数包括以下至少一项：
    单播承载的配置信息；
    组播承载的配置信息；
    其中，所述第一多播广播业务采用PC5单播方式发送的情况下，所述单 播承载与一个PC5组播的MBS RB绑定。
  34. 根据权利要求18所述的方法，其中，在所述第二终端接收第一终端的第一请求信息的步骤之后，所述方法还包括：
    所述第二终端在确定所述第一多播广播业务对应的所有终端无业务需求，或者，所述第一多播广播业务结束的情况下，停止转发所述第一多播广播业务。
  35. 根据权利要求34所述的方法，其中，所述第二终端确定所述第一多播广播业务对应的所有终端无业务需求的步骤，包括：
    所述第二终端在所述第一多播广播业务采用PC5广播方式转发的情况下，发送询问信息至所述第一多播广播业务对应的所有终端，所述询问信息用于询问终端是否具有所述第一多播广播业务的转发需求；
    所述第二终端在未接收到任一终端发送的所述询问信息的确认信息的情况下，确定所述第一多播广播业务对应的所有终端无业务需求。
  36. 一种多播广播业务的发送方法，包括：
    网络设备发送多播控制信道MCCH至第二终端；
    其中，所述第二终端用于接收第一终端的第一请求信息，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发，所述第一终端与所述第二终端之间通过旁链路通信；
    所述MCCH用于确定多播广播控制信息。
  37. 根据权利要求36所述的方法，其中，所述多播广播控制信息包括以下至少一项：
    与TMGI对应的逻辑信道相关参数；
    与TMGI对应的DRX相关参数；
    与TMGI对应的无线承载相关参数；
    与TMGI对应的第一组标识。
  38. 一种多播广播业务的接收装置，包括：
    第一发送模块，用于发送第一请求信息至第二终端；
    其中，所述第二终端与第一终端之间通过旁链路通信，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发。
  39. 根据权利要求38所述的装置，其中，还包括：
    第一接收模块，用于接收所述第二终端发送的多播广播控制信息；
    其中，所述多播广播控制信息包括以下至少一项：
    与TMGI对应的逻辑信道相关参数；
    与TMGI对应的DRX相关参数；
    与TMGI对应的无线承载相关参数；
    与TMGI对应的第一组标识。
  40. 一种多播广播业务的发送装置，包括：
    第二接收模块，用于接收第一终端的第一请求信息；
    其中，所述第一终端与第二终端之间通过旁链路通信，所述第一请求信息用于向第二终端请求进行第一多播广播业务的转发或者停止转发。
  41. 根据权利要求40所述的装置，其中，还包括：
    第二发送模块，用于发送多播广播控制信息至所述第一终端；
    其中，所述多播广播控制信息包括以下至少一项：
    与TMGI对应的逻辑信道相关参数；
    与TMGI对应的DRX相关参数；
    与TMGI对应的无线承载相关参数；
    与TMGI对应的第一组标识。
  42. 一种多播广播业务的发送装置，包括：
    第三发送模块，用于发送MCCH至第二终端；
    其中，所述第二终端用于接收第一终端的第一请求信息，所述第一请求信息用于向所述第二终端请求进行第一多播广播业务的转发或者停止转发，所述第一终端与所述第二终端之间通过旁链路通信；
    所述MCCH用于确定多播广播控制信息。
  43. 一种终端，包括处理器，存储器及存储在所述存储器上并可在所述 处理器上运行的程序或指令，其中，所述程序或指令被所述处理器执行时实现如权利要求1至17任一项所述的多播广播业务的接收方法的步骤，或者实现如权利要求18至35任一项所述的多播广播业务的发送方法的步骤。
  44. 一种网络设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，其中，所述程序或指令被所述处理器执行时实现如权利要求36或37所述的多播广播业务的发送的步骤。
  45. 一种可读存储介质，所述可读存储介质上存储程序或指令，其中，所述程序或指令被处理器执行时实现如权利要求1至17任一项所述的多播广播业务的接收方法，或者，如权利要求18至35任一项所述的多播广播业务的发送方法，或者，如权利要求36或37所述的多播广播业务的发送方法。
  46. 一种芯片，包括处理器和通信接口，其中，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至17任一项所述的多播广播业务的接收方法，或者，如权利要求18至35任一项所述的多播广播业务的发送方法，或者，如权利要求36或37所述的多播广播业务的发送方法。
  47. 一种计算机程序产品，其中，所述程序产品被存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现如权利要求1至17任一项所述的多播广播业务的接收方法，或者，如权利要求18至35任一项所述的多播广播业务的发送方法，或者，如权利要求36或37所述的多播广播业务的发送方法。
  48. 一种通信设备，其中，被配置为执行如权利要求1至17任一项所述的多播广播业务的接收方法，或者，执行如权利要求18至35任一项所述的多播广播业务的发送方法，或者，执行如权利要求36或37所述的多播广播业务的发送方法。
PCT/CN2022/106477 2021-07-23 2022-07-19 多播广播业务的接收方法、发送方法、装置及设备 WO2023001146A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110839367.2 2021-07-23
CN202110839367.2A CN115696218A (zh) 2021-07-23 2021-07-23 多播广播业务的接收方法、发送方法、装置及设备

Publications (1)

Publication Number Publication Date
WO2023001146A1 true WO2023001146A1 (zh) 2023-01-26

Family

ID=84980008

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/106477 WO2023001146A1 (zh) 2021-07-23 2022-07-19 多播广播业务的接收方法、发送方法、装置及设备

Country Status (2)

Country Link
CN (1) CN115696218A (zh)
WO (1) WO2023001146A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180234808A1 (en) * 2015-08-12 2018-08-16 Kyocera Corporation Radio terminal
CN111448808A (zh) * 2018-01-03 2020-07-24 康维达无线有限责任公司 用于IoT应用的5G网络中的多播和广播服务
CN112640346A (zh) * 2018-08-09 2021-04-09 康维达无线有限责任公司 用于5g ev2x的侧链路上的广播、多播和单播

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180234808A1 (en) * 2015-08-12 2018-08-16 Kyocera Corporation Radio terminal
CN111448808A (zh) * 2018-01-03 2020-07-24 康维达无线有限责任公司 用于IoT应用的5G网络中的多播和广播服务
CN112640346A (zh) * 2018-08-09 2021-04-09 康维达无线有限责任公司 用于5g ev2x的侧链路上的广播、多播和单播

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
VIVO: "Overview of NR MBS", 3GPP DRAFT; R2-2007033, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200818 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911881 *

Also Published As

Publication number Publication date
CN115696218A (zh) 2023-02-03

Similar Documents

Publication Publication Date Title
US11632788B2 (en) Data scheduling method, base station, and system
CN107431969B (zh) 通信资源分配方法及装置、终端设备、基站和通信系统
CN105075343A (zh) 用于在异构通信环境中选择网络和分发业务的方法和装置
WO2021142647A1 (zh) 一种业务传输方法及装置、终端设备、网络设备
WO2022056806A1 (zh) 一种mbs业务的管理方法及装置、终端设备、网络设备
KR20230095948A (ko) 5g 무선 네트워크에서 멀티캐스트 및 브로드캐스트 서비스를 위한 관심 인디케이션을 송신하는 방법 및 시스템
WO2022033473A1 (zh) 数据传输方法、装置及通信设备
TW202224454A (zh) 用於mbs的無線通信的裝置和方法
KR101606789B1 (ko) 멀티미디어 서비스를 수신하는 유휴 모드 상태의 단말들을 고려한 효과적인 멀티미디어 데이터 전송 방법
CN113676922B (zh) 一种终端设备协作方法及装置
US20230354153A1 (en) Path processing method and apparatus, terminal, network device, and storage medium
WO2021174399A1 (zh) 时钟同步方法、装置、设备及存储介质
WO2023001146A1 (zh) 多播广播业务的接收方法、发送方法、装置及设备
WO2022078394A1 (zh) 多播业务的传输方法、装置及通信设备
WO2022012526A1 (zh) 处理方法、发送方法及相关设备
WO2014121599A1 (zh) 传递蜂窝网络负荷信息的方法和相关设备
WO2021142646A1 (zh) 一种业务传输方法及装置、通信设备
WO2023001144A1 (zh) 多播广播业务的接收方法、发送方法、装置及设备
WO2021051321A1 (zh) 一种业务数据传输方法及装置、终端设备
WO2023284682A1 (zh) 中继的识别方法、中继的确定方法、终端及网络侧设备
WO2021189458A1 (zh) 一种数据转发方法及装置、通信设备
WO2024066858A1 (zh) 一种通信的方法和装置
WO2023051507A1 (zh) Ue的能力变更方法、终端及网络侧设备
WO2022206505A1 (zh) 业务数据处理方法、装置及设备
WO2022021235A1 (zh) 一种mbs业务的传输方法及装置、通信设备

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: 22845311

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE