Multicast broadcast processing method and device, related equipment and storage medium

Abstract

The invention discloses a multicast broadcast processing method and device, related equipment and a storage medium. The method is applied to a first terminal, and comprises the following steps: acquiring a relay multicast radio bearer determined by network equipment for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal; and realizing a multicast service by using the relay multicast radio bearer or the unicast resource block.

Description

Technical Field

[0001] This application relates to the field of wireless technologies, and in particular, to a method, apparatus, related device, and storage medium for processing multicast and broadcast services. Background Art

[0002] When multiple remote user equipments (remote UEs) are connected to a relay user equipment (relay UE), the network establishes a separate data radio bearer (DRB) for each remote UE for data transmission. However, there may be the same multicast and broadcast services among the services that the remote UEs receive. Transmitting through the DRB (for example, point to point (PTP)) may cause waste of resources of the proximity communication 5 (PC5) port and the communication (Uu) port between devices. In addition, considering that the relay UE may also be a subscriber of this multicast service, if it also needs to forward this data for the remote UEs, it will also cause waste of Uu port resources. Summary of the Invention

[0003] To solve the related technical problems, embodiments of this application provide a method, apparatus, related device, and storage medium for processing multicast and broadcast services.

[0004] The technical solution of the embodiments of this application is implemented as follows:

[0005] Embodiments of this application provide a method for processing multicast and broadcast services, which is applied to a first terminal and includes:

[0006] Obtain a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal;

[0007] Implement multicast services by using the relay multicast radio bearer or the unicast resource block.

[0008] In the above solution, the method further includes:

[0009] Judge whether the first terminal supports the multicast feature based on its own capabilities, and obtain a judgment result;

[0010] Obtain a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal based on the judgment result.

[0011] In the above solution, obtaining, based on the judgment result, the relay multicast radio bearer determined by the network device for the first terminal serving at least one second terminal includes:

[0012] When the judgment result indicates that the first terminal supports the multicast feature, sending a first request message to the network device; the first request message is used for the network device to determine a relay multicast radio bearer for the first terminal serving at least one second terminal;

[0013] Implementing a multicast service by using the relay multicast radio bearer includes:

[0014] Transmitting a multicast service to each of the second terminals by using the relay multicast radio bearer.

[0015] In the above solution, the relay multicast radio bearer includes the first multicast radio bearer of the first terminal itself; the first terminal communicates directly with each of the second terminals; the method further includes:

[0016] Sending the data packet of the first multicast radio bearer to each of the second terminals through the multicast radio bearer corresponding to the direct communication; the data packet of the first multicast radio bearer is encapsulated according to the PC5 interface protocol and corresponds to the radio link control channel (RLC Channel) of the second terminal.

[0017] In the above solution, the relay multicast radio bearer includes a second multicast radio bearer established; the first terminal communicates directly with each of the second terminals; the method further includes:

[0018] Determining the correspondence between the second multicast radio bearer and the resource block corresponding to the direct communication;

[0019] Transmitting a multicast service to each of the second terminals by using the correspondence.

[0020] In the above solution, the method further includes:

[0021] Sending configuration information of the target multicast service of the first terminal to the second terminal; the configuration information is used for the second terminal to join the multicast broadcast session process of the target multicast service.

[0022] In the above solution, the configuration information includes at least one of the following:

[0023] Identification information;

[0024] Forwarded multicast broadcast session control information.

[0025] In the above solution, the method further includes:

[0026] Send first information to each of the second terminals; the first information is used for the second terminals to determine whether to select the first terminal as the terminal serving themselves.

[0027] In the above solution, the method further includes:

[0028] Receive second information sent by each of the second terminals; the second information represents whether the second terminal selects the first terminal as the terminal serving itself.

[0029] In the above solution, the first information or the second information includes at least one of the following:

[0030] Indication information on whether multicast characteristics are supported;

[0031] Attribute information of multicast services;

[0032] Priority information of multicast services;

[0033] Quality information of direct communication channels.

[0034] In the above solution, the obtaining of the unicast resource block configured by the network device for the first terminal based on the judgment result includes:

[0035] When the judgment result indicates that the first terminal does not support multicast characteristics, obtain the unicast resource block configured by the network device for the first terminal;

[0036] The implementation of multicast services by using the unicast resource block includes:

[0037] Use the unicast resource block to receive multicast services sent by the network device.

[0038] An embodiment of the present application further provides a method for processing multicast and broadcast, which is applied to a network device and includes:

[0039] Provide a relay multicast radio bearer determined for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal to the first terminal; the relay multicast radio bearer or the unicast resource block is used for the first terminal to implement multicast services.

[0040] In the above solution, the method further includes:

[0041] According to whether the first terminal itself supports multicast characteristics, provide a relay multicast radio bearer determined for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal to the first terminal.

[0042] In the above solution, the method further includes:

[0043] When the first terminal supports the multicast feature, receive the first request message sent by the first terminal;

[0044] Based on the first request message, determine a relay multicast radio bearer for the first terminal serving at least one second terminal; the relay multicast radio bearer is used for the first terminal to transmit multicast services to each of the second terminals.

[0045] In the above solution, the method further includes:

[0046] When the first terminal does not support the multicast feature, configure a unicast resource block for the first terminal; the unicast resource block is used to receive the multicast service sent by the network device.

[0047] An embodiment of the present application further provides a method for processing multicast and broadcast, which is applied to a second terminal and includes:

[0048] Receive the configuration information of the target multicast service of the first terminal;

[0049] Based on the configuration information, join the multicast and broadcast session process of the target multicast service.

[0050] In the above solution, the configuration information includes at least one of the following:

[0051] Identification information;

[0052] Multicast and broadcast session control information.

[0053] In the above solution, the method further includes:

[0054] Receive the first information sent by the first terminal;

[0055] Based on the first information, determine whether to select the first terminal as the terminal serving itself.

[0056] In the above solution, the method further includes:

[0057] Send a second information to the first terminal; the second information indicates whether the second terminal selects the first terminal as the terminal serving itself.

[0058] In the above solution, the first information or the second information includes at least one of the following:

[0059] Indication information of whether it supports the multicast feature;

[0060] Attribute information of the multicast service;

[0061] Priority information of the multicast service;

[0062] Quality information of the direct communication channel.

[0063] An embodiment of the present application further provides a multicast and broadcast processing device, which is disposed on a first terminal and includes:

[0064] An obtaining unit, configured to obtain a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal;

[0065] An implementation unit, configured to implement a multicast service by using the relay multicast radio bearer or the unicast resource block.

[0066] An embodiment of the present application further provides a multicast and broadcast processing device, which is disposed on a network device and includes:

[0067] A providing unit, configured to provide a relay multicast radio bearer determined by the network device for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal to the first terminal; the relay multicast radio bearer or the unicast resource block is used for the first terminal to implement a multicast service.

[0068] An embodiment of the present application further provides a multicast and broadcast processing device, which is disposed on a second terminal and includes:

[0069] A receiving unit, configured to receive configuration information of a target multicast service of a first terminal;

[0070] A joining unit, configured to join a multicast and broadcast session process of the target multicast service based on the configuration information.

[0071] An embodiment of the present application further provides a first terminal, including: a first processor and a first memory for storing a computer program that can run on the processor,

[0072] Wherein, when the first processor is used to run the computer program, it executes the steps of any of the methods on the first terminal side.

[0073] An embodiment of the present application further provides a network device, including: a second processor and a second memory for storing a computer program that can run on the processor,

[0074] Wherein, when the second processor is used to run the computer program, it executes the steps of any of the methods on the network device side.

[0075] An embodiment of the present application further provides a second terminal, including: a third processor and a third memory for storing a computer program that can run on the processor,

[0076] Wherein, when the third processor is used to run the computer program, it executes the steps of any of the above methods on the second terminal side.

[0077] An embodiment of the present application further provides a storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the steps of any of the above methods on the first terminal side, or implements the steps of any of the above methods on the network device side, or implements the steps of any of the above methods on the second terminal side.

[0078] For the multicast and broadcast processing method, device, related equipment and storage medium provided by the embodiments of the present application, the first terminal obtains the relay multicast radio bearer determined by the network device for the first terminal serving at least one second terminal or the unicast resource block configured for the first terminal; and uses the relay multicast radio bearer or the unicast resource block to implement multicast services. The network device provides the first terminal with the relay multicast radio bearer determined by the network device for the first terminal serving at least one second terminal or the unicast resource block configured for the first terminal; the relay multicast radio bearer or the unicast resource block is used for the first terminal to implement multicast services. The second terminal receives the configuration information of the target multicast service of the first terminal; and joins the multicast and broadcast session process of the target multicast service based on the configuration information. By adopting the embodiments of the present application, by introducing the step of obtaining the relay multicast radio bearer determined by the network device for the first terminal serving at least one second terminal or the unicast resource block configured for the first terminal; and using the relay multicast radio bearer or the unicast resource block to implement multicast services, resources are fully utilized and waste of resources is avoided. Description of the Drawings

[0079] Figure 1 It is a schematic flowchart of a method for processing multicast and broadcast in an embodiment of the present application;

[0080] Figure 2 It is a schematic flowchart of another method for processing multicast and broadcast in an embodiment of the present application;

[0081] Figure 3 It is a schematic flowchart of another method for processing multicast and broadcast in an embodiment of the present application;

[0082] Figure 4 It is a schematic diagram of the protocol stack between the gNB, relay UE and remote UE in an embodiment of the present application;

[0083] Figure 5 It is a schematic diagram of the transmission of the MRB mapped to the corresponding PC5 RB through the adaptation layer in an embodiment of the present application;

[0084] Figure 6 It is a schematic diagram of a remote UE applying to join a multicast service in an embodiment of the present application;

[0085] Figure 7 Schematic structural diagram of a multicast and broadcast processing device according to an embodiment of the present application;

[0086] Figure 8 Schematic structural diagram of another multicast and broadcast processing device according to an embodiment of the present application;

[0087] Figure 9 Schematic structural diagram of another multicast and broadcast processing device according to an embodiment of the present application;

[0088] Figure 10 Schematic structural diagram of a first terminal according to an embodiment of the present application;

[0089] Figure 11 Schematic structural diagram of a network device according to an embodiment of the present application;

[0090] Figure 12 Schematic structural diagram of a second terminal according to an embodiment of the present application;

[0091] Figure 13 Schematic structural diagram of a multicast and broadcast processing system according to an embodiment of the present application. Detailed implementation manners

[0092] The present application will be further described in detail below with reference to the accompanying drawings and embodiments.

[0093] Side link relay refers to a technology in which a mobile terminal accesses the access network through a PC5 connection with another terminal and uses that terminal as a relay. In Side link RELAY, multiple remote UEs can be connected to a relay UE.

[0094] When multiple remote UEs are connected to a relay UE, the network establishes a separate DRB for each remote UE for data transmission. However, there may be the same multicast and broadcast services among the services that the remote UE may receive, and transmitting through the DRB (PTP) method will cause waste of resources (PC5 interface and Uu interface). In addition, considering that the relay UE may also be a subscriber of this multicast service, if it also needs to forward this data for the remote UE, it will also cause waste of Uu interface resources.

[0095] Based on this, in various embodiments of the present application, by the states of the network and the terminal, the commercial secret and international cryptographic algorithms are adaptively compatible to meet the requirements of interconnection.

[0096] The embodiment of the present application provides a method for processing multicast and broadcast, which is applied to a first terminal, as Figure 1 shown Figure 1Schematic flowchart of a method for processing multicast and broadcast in an embodiment of this application, including:

[0097] Step 101: Obtain the relay multicast radio bearer determined by the network device for the first terminal serving at least one second terminal or the unicast resource block configured for the first terminal;

[0098] Step 102: Implement multicast services by using the relay multicast radio bearer or the unicast resource block.

[0099] It should be noted that the first terminal, the second terminal, and the network device can all be determined according to actual situations and are not limited here. As an example, the first terminal can be a relay UE; the second terminal can be a remote UE; the network device can be a base station, denoted as gNB.

[0100] In step 101, the relay multicast radio bearer can be determined according to actual situations and is not limited here. As an example, the relay multicast radio bearer includes the first multicast radio bearer of the first terminal itself, the established second multicast radio bearer, etc. The unicast resource block can be determined according to actual situations and is not limited here. The unicast resource block can be denoted as unicastRB. As an example, it is possible to judge whether the first terminal supports the multicast feature based on the self - ability of the first terminal to obtain a judgment result; and obtain the relay multicast radio bearer determined by the network device for the first terminal serving at least one second terminal or the unicast resource block configured for the first terminal based on the judgment result.

[0101] In step 102, the specific process of implementing multicast services by using the relay multicast radio bearer or the unicast resource block can be determined according to actual situations and is not limited here. As an example, when the judgment result indicates that the first terminal supports the multicast feature, a first request message can be sent to the network device; the first request message is used for the network device to determine a relay multicast radio bearer for the first terminal serving at least one second terminal; implementing multicast services by using the relay multicast radio bearer can include transmitting multicast services to each second terminal by using the relay multicast radio bearer. When the judgment result indicates that the first terminal does not support the multicast feature, the unicast resource block configured by the network device for the first terminal can be obtained; implementing multicast services by using the unicast resource block can include receiving multicast services sent by the network device by using the unicast resource block.

[0102] By adopting the embodiment of the present application, by introducing a relay multicast radio bearer determined by a network device for a first terminal serving at least one second terminal or a unicast resource block configured for the first terminal; using the relay multicast radio bearer or the unicast resource block to implement a multicast service, resources are fully utilized and resource waste is avoided.

[0103] In one embodiment, the method further includes:

[0104] Judging whether the first terminal supports the multicast feature based on the self-capability of the first terminal to obtain a judgment result;

[0105] Obtaining a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal based on the judgment result.

[0106] In the embodiment of the present application, judging whether the first terminal supports the multicast feature based on the self-capability of the first terminal to obtain a judgment result may be judging whether the first terminal supports the multicast feature based on the self-capability of the first terminal to obtain a judgment result that the first terminal itself supports the multicast feature or the first terminal itself does not support the multicast feature.

[0107] The specific process of obtaining a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal based on the judgment result may be determined according to specific circumstances and is not limited herein. As an example, obtaining a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal based on the judgment result may include, when the judgment result indicates that the first terminal supports the multicast feature, sending a first request message to the network device; the first request message is used for the network device to determine a relay multicast radio bearer for the first terminal serving at least one second terminal. Among them, the relay multicast radio bearer may be determined according to specific circumstances and is not limited herein. As an example, the relay multicast radio bearer may include a first multicast radio bearer of the first terminal itself.

[0108] In practical applications, the PC5 interface can interact with the supported / interested / in-transit MBS service information of the remote UE and the relay UE; the UE indicates whether it supports the multicast feature in the discovery message of the PC5 interface and may further carry the interested / in-receiving multicast service information (both the relay UE and the remote UE can carry this message).

[0109] In one embodiment, obtaining a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal based on the judgment result includes:

[0110] When the judgment result indicates that the first terminal supports the multicast feature, send first request information to a network device; the first request information is used for the network device to determine a relay multicast radio bearer for the first terminal serving at least one second terminal.

[0111] Implementing the multicast service by using the relay multicast radio bearer includes:

[0112] Transmit the multicast service to each of the second terminals by using the relay multicast radio bearer.

[0113] In this embodiment, the first request information is used for the network device to determine a relay multicast radio bearer for the first terminal serving at least one second terminal; wherein, the relay multicast radio bearer can be determined according to the actual situation and is not limited herein. As an example, the relay multicast radio bearer includes a first multicast radio bearer of the first terminal itself.

[0114] This embodiment can be understood as a solution in which when the first terminal supports the multicast feature, the relay MRB serving the remote UE multiplexes the MRB of the relay UE itself. Specifically, the relay UE establishes a normal MRB, but based on the information with the remote UE, the relay UE copies the packets of the MRB from the PDCP layer and sends them to the PC5 MRB to the remote UE, and the remote UE receives the corresponding packets from the PC5 and sends them to the DRB of the corresponding remote UE.

[0115] In an embodiment, the relay multicast radio bearer includes a first multicast radio bearer of the first terminal itself; the first terminal communicates directly with each of the second terminals; the method further includes:

[0116] Send the data packets of the first multicast radio bearer to each of the second terminals through the multicast radio bearer corresponding to the direct communication; the data packets of the first multicast radio bearer are encapsulated according to the direct communication PC5 port protocol and correspond to the radio link control channel (RLC Channel) of the second terminal.

[0117] In this embodiment, the relay multicast radio bearer includes a first multicast radio bearer of the first terminal itself; this first multicast radio bearer can be denoted as MRB.

[0118] The data packets of the first multicast radio bearer are encapsulated according to the direct communication PC5 interface protocol and correspond to the radio link control channel (RLC Channel) of the second terminal. It can be understood that there is a corresponding relationship between the data packets of the first multicast radio bearer encapsulated according to the direct communication PC5 interface protocol and the radio link control channel (RLC Channel) of the second terminal. Among them, the corresponding relationship can be determined according to the actual situation and is not limited here.

[0119] In this embodiment, the Relay UE has not established an MRB for a remote for a certain MBS service yet. In actual applications, the Relay UE initiates a join process based on the multicast service information exchanged through the PC5 interface or based on the indication of the network (in the case where the remote UE under this relay UE only sends multicast service information to the network, such as initiating a join process), joins the multicast service group (MBS service 1), and at the same time indicates: whether it is used to serve the remote UE. If so, corresponding remote UE information can also be provided, such as the UE ID and the sidelink channel quality condition between this UE and the relay UE.

[0120] The gNB establishes an MRB based on the join request of the relay UE for the remote UE to receive the multicast service through the relay UE. This MRB may be different from the MRB used for normal multicast service reception without using the relay UE or be the same MRB. For multiple remote UEs under the same relay, their PDCP and RLC adopt a common configuration.

[0121] In one embodiment, the relay multicast radio bearer includes a second multicast radio bearer established; the first terminal communicates directly with each second terminal; the method further includes:

[0122] Determine the corresponding relationship between the second multicast radio bearer and the resource block corresponding to the direct communication;

[0123] Transmit multicast services to each second terminal by using the corresponding relationship.

[0124] In this embodiment, the relay multicast radio bearer includes a second multicast radio bearer established; among them, the second multicast radio bearer can be determined according to the actual situation and is not limited here. As an example, the second multicast radio bearer can be denoted as MRB.

[0125] Determine the correspondence between the second multicast radio bearer and the corresponding resource block for direct communication; wherein, the correspondence can be determined according to the actual situation and is not limited herein. As an example, the correspondence may include a one-to-one correspondence.

[0126] As an example, if a Relay UE has established an MRB for a certain MBS service, another remote UE (remote UE1) can reuse the Relay UE. When remote UE1 learns that the Relay UE has established an MRB for MBS service 1 based on the multicast service support information of the Relay UE, remote UE1 will apply to join the MBS session corresponding to this service. Optionally, it can join the existing relay group of the Relay UE (or select after interacting with the Relay UE about preferences, UE level, etc.) or establish a separate link / relay group and then join the corresponding group.

[0127] In practical applications, the Relay UE that serves the remote UE establishes an MRB independent of its own reception of MBS, and maps it to the corresponding PC5 RB through the adaptation layer (SRAP) for transmission.

[0128] In one embodiment, the method further includes:

[0129] Send the configuration information of the target multicast service of the first terminal to the second terminal; the configuration information is used for the second terminal to join the multicast broadcast session process of the target multicast service.

[0130] In this embodiment, the configuration information can be determined according to the actual situation and is not limited herein. As an example, the configuration information may include at least one of the following: identification information; forwarded multicast broadcast session control information.

[0131] In practical applications, the Relay UE sends data to multiple remote UEs in a broadcast manner: the Relay UE can be based on the indication of the base station or the base station directly configures the UE (through relay forwarding) with the group ID corresponding to this service under the Relay UE (hereinafter represented by relay group id), that is, the remote UE will receive the MBS session information corresponding to this service (such as session ID, qos flow information), the relay group id, and the corresponding protocol station configuration.

[0132] In one embodiment, the configuration information includes at least one of the following:

[0133] Identification information;

[0134] Forwarded multicast / broadcast session control information.

[0135] In this embodiment, the identification information can be determined according to the actual situation and is not limited herein. As an example, the identification information may include the group ID corresponding to the service under the relay UE, which can be represented by the relay group id.

[0136] The forwarded multicast / broadcast session control information can be determined according to the actual situation and is not limited herein. As an example, the forwarded multicast / broadcast session control information may include MBS session information, for example, session ID, qos flow information.

[0137] In practical applications, the Relay UE sends data to multiple remote UEs in a broadcast manner: the relay UE can be based on the base station indication or the base station directly configures for the UE (through the relay transfer) the group ID corresponding to the service under the relay UE (hereinafter represented by the relay group id), that is, the remote UE will receive the MBS session information corresponding to the service (such as session ID, qos flow information), the relay group id, and the corresponding protocol station configuration. If the relay groupid is assigned by the relay UE, the relay UE needs to inform the base station of this id. For subsequent data transmission, in the case of not using the relay UE MRB scheme, the base station includes the MBS session information and / or the relay group id in the SRAP layer so that the relay UE can correctly address one or more remote UEs.

[0138] In one embodiment, the method further includes:

[0139] Sending first information to each of the second terminals; the first information is used for the second terminal to determine whether to select the first terminal as the terminal serving itself.

[0140] In this embodiment, the first information can be determined according to the actual situation and is not limited herein. As an example, the first information may include at least one of the following: indication information of whether multicast characteristics are supported; attribute information of the multicast service; priority information of the multicast service; quality information of the direct communication channel. The first information can be understood as a request message, and this request message is used for the second terminal to determine whether to select the first terminal as the terminal serving itself.

[0141] In one embodiment, the method further includes:

[0142] Receive second information sent by each of the second terminals; the second information indicates whether the second terminal selects the first terminal as the terminal serving itself.

[0143] In this embodiment, the second information can be determined according to the actual situation and is not limited herein. As an example, the second information may include at least one of the following: indication information on whether multicast characteristics are supported; attribute information of multicast services; priority information of multicast services; quality information of direct communication channels. The second information can be understood as a response message, which is used by the second terminal to determine whether to select the first terminal as the terminal serving itself.

[0144] In one embodiment, the first information or the second information includes at least one of the following:

[0145] Indication information on whether multicast characteristics are supported;

[0146] Attribute information of multicast services;

[0147] Priority information of multicast services;

[0148] Quality information of direct communication channels.

[0149] In this embodiment, the indication information can be indicated by the UE in the discovery message on the PC5 interface; the indication information can indicate that the UE supports multicast characteristics or the UE does not support multicast characteristics.

[0150] The attribute information of the multicast service can be determined according to the actual situation and is not limited herein. As an example, the attribute information of the multicast service may include multicast service information carrying interests or being received.

[0151] The priority information of the multicast service can be determined according to the actual situation and is not limited herein. As an example, the priority information of the multicast service may include network broadcast or network per-UE configuration.

[0152] The quality information of the direct communication channel can be determined according to the actual situation and is not limited herein. As an example, the quality information of the direct communication channel may include information such as PC5 channel quality and PC5 quality requirements.

[0153] In practical applications, the UE indicates whether it supports the multicast feature in the discovery message on the PC5 interface, and can further carry the multicast service information of interest / received (both relay UE and remote UE can carry this message); when selecting a relay UE, in addition to considering information such as the PC5 channel quality, the Remote UE will also refer to whether the UE supports the multicast feature, and further consider whether the multicast services it is interested in / transmitting are the same as the multicast services it is interested in. The Remote UE performs priority sorting on potential Relay UEs, and its sorting rules may be based on the multicast service priorities provided by the network (which may be broadcast by the network or configured per UE by the network) or UE implementation. The UE selects the UE with the highest priority that meets the PC5 quality requirements as the Relay UE. If none of the high-priority potential relay UEs meet the PC5 quality requirements, the UE selects a relay UE according to the existing mechanism. Alternatively, for multiple potential relay UEs that meet the PC5 channel quality requirements, the remote UE selects the UE with the most matching interested and / or transmitting services as its Relay UE. If not, the UE selects a relay UE according to the existing mechanism. After the Remote UE selects a certain relay UE, it can send the multicast service information it is interested in or wants to receive during the PC5 interface establishment process or after the interface establishment. Possibly, the relay UE will also feedback the multicast service information it is transmitting / interested in.

[0154] In one embodiment, obtaining the unicast resource block configured by the network device for the first terminal based on the judgment result includes:

[0155] In the case where the judgment result indicates that the first terminal does not support the multicast feature, obtain the unicast resource block configured by the network device for the first terminal;

[0156] Implementing the multicast service using the unicast resource block includes:

[0157] Receive the multicast service sent by the network device using the unicast resource block.

[0158] In this embodiment, obtain the unicast resource block configured by the network device for the first terminal; where the unicast resource block can be determined according to the actual situation and is not limited here. As an example, the unicast resource block can be denoted as unicastRB; receiving the multicast service sent by the network device using the unicast resource block can be understood as receiving the multicast service sent by the network device using unicastRB.

[0159] In practical applications, the Relay UE does not support the air interface MBS feature. The gNB establishes a unicast RB for the relay UE to receive multicast services and indicates the remote UE ID information, mapping the RB used by the remote UE for multicast service reception to the PC5 interface transmission. Similarly, the PC5 interface packet can be configured for resource multiplexing on the PC5.

[0160] Correspondingly, an embodiment of the present application further provides a method for processing multicast and broadcast, as Figure 2 shown, Figure 2 which is a schematic flowchart of another method for processing multicast and broadcast in an embodiment of the present application, applied to a network device, including:

[0161] Step 201: Provide a relay multicast radio bearer determined for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal to the first terminal; the relay multicast radio bearer or the unicast resource block is used for the first terminal to implement multicast services.

[0162] It should be noted that the first terminal, the second terminal, and the network device can all be determined according to actual situations and are not limited herein. As an example, the first terminal can be a relay UE; the second terminal can be a remote UE; the network device can be a base station, denoted as gNB.

[0163] In step 201, the relay multicast radio bearer can be determined according to actual situations and is not limited herein. As an example, the relay multicast radio bearer includes the first multicast radio bearer of the first terminal itself, the established second multicast radio bearer, etc. The unicast resource block can be determined according to actual situations and is not limited herein. The unicast resource block can be denoted as unicastRB.

[0164] By adopting the embodiment of the present application, by introducing the acquisition of the relay multicast radio bearer determined for the first terminal serving at least one second terminal or the unicast resource block configured for the first terminal; using the relay multicast radio bearer or the unicast resource block to implement multicast services, resources are fully utilized and resource waste is avoided.

[0165] In one embodiment, the method further includes:

[0166] According to whether the first terminal itself supports the multicast feature, provide the relay multicast radio bearer determined for the first terminal serving at least one second terminal or the unicast resource block configured for the first terminal to the first terminal.

[0167] It should be noted that determining whether to provide the first terminal with a relay multicast radio bearer determined for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal according to whether the first terminal itself supports the multicast feature can be determined according to the actual situation and is not limited herein. As an example, in the case where the first terminal supports the multicast feature, the first request information sent by the first terminal can be received; based on the first request information, a relay multicast radio bearer is determined for the first terminal serving at least one second terminal; the relay multicast radio bearer is used for the first terminal to transmit multicast services to each of the second terminals. In the case where the first terminal does not support the multicast feature, a unicast resource block can be configured for the first terminal; the unicast resource block is used to receive the multicast services sent by the network device.

[0168] In one embodiment, the method further includes:

[0169] In the case where the first terminal supports the multicast feature, receive the first request information sent by the first terminal;

[0170] Based on the first request information, determine a relay multicast radio bearer for the first terminal serving at least one second terminal; the relay multicast radio bearer is used for the first terminal to transmit multicast services to each of the second terminals.

[0171] In the embodiments of the present application, the relay multicast radio bearer can be determined according to the actual situation and is not limited herein. As an example, the relay multicast radio bearer includes the first multicast radio bearer of the first terminal itself.

[0172] This embodiment can be understood as a scheme in which, in the case where the first terminal supports the multicast feature, the relay MRB serving the remote UE multiplexes the MRB of the relay UE itself. Specifically, the relay UE establishes a normal MRB, but based on the information with the remote UE, the relay UE copies the packets of the MRB from the PDCP layer and sends them to the PC5 MRB to the remote UE, and the remote UE receives the corresponding packets from the PC5 and sends them to the DRB of the corresponding remote UE.

[0173] In one embodiment, the method further includes:

[0174] In the case where the first terminal does not support the multicast feature, configure a unicast resource block for the first terminal; the unicast resource block is used to receive the multicast services sent by the network device.

[0175] In this embodiment, the unicast resource block can be determined according to actual situations, which is not limited herein. As an example, the unicast resource block can be denoted as unicastRB.

[0176] In practical applications, the Relay UE does not support the air interface MBS feature. The gNB establishes a unicastRB for the relay UE to receive multicast services, and indicates the remote UE ID information, mapping the RB used by the remote UE for multicast service reception to the transmission on the PC5 interface. Similarly, the PC5 interface packet can be configured to multiplex resources on the PC5.

[0177] Correspondingly, the embodiment of the present application further provides a method for processing multicast and broadcast, as Figure 3 shown, Figure 3 which is a schematic flowchart of another method for processing multicast and broadcast in the embodiment of the present application, applied to the second terminal, and includes:

[0178] Step 301: Receive the configuration information of the target multicast service of the first terminal.

[0179] Step 302: Join the multicast and broadcast session process of the target multicast service based on the configuration information.

[0180] It should be noted that both the first terminal and the second terminal can be determined according to actual situations, which is not limited herein. As an example, the first terminal can be a network element, for example, BSF; the second terminal can be a server, for example, HSS.

[0181] It should be noted that the first terminal, the second terminal, and the network device can all be determined according to actual situations, which is not limited herein. As an example, the first terminal can be a relay UE; the second terminal can be a remote UE; the network device can be a base station, denoted as gNB.

[0182] In step 301, receive the configuration information of the target multicast service of the first terminal; wherein, the configuration information can be determined according to actual situations, which is not limited herein. As an example, the configuration information can include at least one of the following: identification information; forwarded multicast and broadcast session control information.

[0183] In step 302, the specific process of joining the multicast and broadcast session process of the target multicast service based on the configuration information can be determined according to actual situations, which is not limited herein.

[0184] In practical applications, the Relay UE sends data to multiple remote UEs in a broadcast manner: The relay UE can be configured by the base station indication or directly by the base station to the UE (through relay forwarding) with a group ID corresponding to the service under this relay UE (hereinafter represented by relay group id). That is, the remote UE will receive the MBS session information corresponding to this service (such as session ID, qos flow information), the relay group id, and the corresponding protocol station configuration.

[0185] By adopting the embodiment of the present application, by introducing the acquisition of the relay multicast radio bearer determined by the network device for the first terminal serving at least one second terminal or the unicast resource block configured for the first terminal; using the relay multicast radio bearer or the unicast resource block to implement the multicast service, the resources are fully utilized and the waste of resources is avoided.

[0186] In one embodiment, the configuration information includes at least one of the following:

[0187] Identification information;

[0188] Multicast broadcast session control information.

[0189] In this embodiment, the identification information can be determined according to the actual situation and is not limited herein. As an example, the identification information may include the group ID corresponding to the service under the relay UE, which can be represented by relay group id.

[0190] The forwarded multicast broadcast session control information can be determined according to the actual situation and is not limited herein. As an example, the forwarded multicast broadcast session control information may include MBS session information, for example, session ID, qos flow information.

[0191] In practical applications, the Relay UE sends data to multiple remote UEs in a broadcast manner: the relay UE can be configured by the base station indication or directly by the base station for the UE (through relay forwarding) with a group ID corresponding to the service under this relay UE (hereinafter represented by relay group id), that is, the remote UE will receive the MBS session information corresponding to the service (such as session ID, qos flow information), the relay group id, and the corresponding protocol station configuration. If the relay group id is allocated by the relay UE, the relay UE needs to inform the base station of this id. For subsequent data transmission, in the case of not using the relay UE MRB scheme, the base station includes the MBS session information and / or the relay group id in the SRAP layer so that the relay UE can correctly address one or more remote UEs.

[0192] In one embodiment, the method further includes:

[0193] Receiving first information sent by the first terminal;

[0194] Determining whether to select the first terminal as the terminal serving itself based on the first information.

[0195] In this embodiment, the first information can be determined according to the actual situation and is not limited herein. As an example, the first information may include at least one of the following: indication information of whether multicast characteristics are supported; attribute information of the multicast service; priority information of the multicast service; quality information of the direct communication channel.

[0196] The specific determination process of determining whether to select the first terminal as the terminal serving itself based on the first information can be determined according to the actual situation and is not limited herein. As an example, determining whether to select the first terminal as the terminal serving itself based on the first information may be determining to select the first terminal as the terminal serving itself or not selecting the first terminal as the terminal serving itself based on the first information.

[0197] In one embodiment, the method further includes:

[0198] Sending second information to the first terminal; the second information indicates whether the second terminal selects the first terminal as the terminal serving itself.

[0199] In this embodiment, the second information can be determined according to the actual situation and is not limited herein. As an example, the second information may include at least one of the following: indication information on whether multicast characteristics are supported; attribute information of the multicast service; priority information of the multicast service; quality information of the direct communication channel.

[0200] That the second information characterizes whether the second terminal selects the first terminal as the terminal serving itself can be understood as that the second information characterizes that the second terminal selects the first terminal as the terminal serving itself or does not select the first terminal as the terminal serving itself.

[0201] In one embodiment, the first information or the second information includes at least one of the following:

[0202] Indication information on whether multicast characteristics are supported;

[0203] Attribute information of the multicast service;

[0204] Priority information of the multicast service;

[0205] Quality information of the direct communication channel.

[0206] In this embodiment, the indication information can be indicated by the UE in the discovery message on the PC5 interface; the indication information can characterize that the UE supports multicast characteristics or the UE does not support multicast characteristics.

[0207] The attribute information of the multicast service can be determined according to the actual situation and is not limited herein. As an example, the attribute information of the multicast service may include multicast service information carrying interests or being received.

[0208] The priority information of the multicast service can be determined according to the actual situation and is not limited herein. As an example, the priority information of the multicast service may include network broadcast or network per-UE configuration.

[0209] The quality information of the direct communication channel can be determined according to the actual situation and is not limited herein. As an example, the quality information of the direct communication channel may include information such as PC5 channel quality and PC5 quality requirements.

[0210] In practical applications, the UE indicates whether it supports the multicast feature in the discovery message on the PC5 interface, and can further carry the multicast service information of interest / being received (both the relay UE and the remote UE can carry this message); when selecting a relay UE, in addition to considering information such as the PC5 channel quality, the Remote UE will also refer to whether the UE supports the multicast feature, and further consider whether the multicast services it is interested in / transmitting are the same as the multicast services it is interested in. The Remote UE performs priority sorting on potential Relay UEs, and its sorting rules may be based on the multicast service priorities provided by the network (which may be broadcast by the network or configured per UE by the network) or the UE implementation. The UE selects the UE with the highest priority that meets the PC5 quality requirements as the Relay UE. If none of the high-priority potential relay UEs meet the PC5 quality requirements, the UE selects a relay UE according to the existing mechanism. Alternatively, for multiple potential relay UEs that meet the PC5 channel quality requirements, the remote UE selects the UE with the most matching interested and / or transmitting services as its Relay UE. If not, the UE selects a relay UE according to the existing mechanism. After the Remote UE selects a certain relay UE, it can send the multicast service information it is interested in or wants to receive during the establishment process of the PC5 interface or after the interface is established. Possibly, the relay UE will also feedback the multicast service information it is transmitting / interested in.

[0211] For ease of understanding, the example of the multicast and broadcast processing method in this application is specifically a method for implementing multicast and broadcast in a multi-Sidelink relay scenario. In the embodiments of this application, the PC5 interface can interact with the MBS service information supported / interesting / being transmitted by the remote UE and the relay UE; define the MRB for the Remote UE to perform multicast service transmission, which includes the MRB established by the relay side for multicast service transmission (hereinafter identified by relay MRB) and the MRB established by the remote UE (hereinafter identified by remote MRB); the Relay UE groups the remote UEs based on the service information interacted on the PC5 or the indication from the base station / CN, and performs corresponding RB mapping, etc. The detailed process includes:

[0212] 1. Relay UE Selection:

[0213] a) The UE indicates whether it supports the multicast feature in the discovery message on the PC5 interface, and can further carry the multicast service information of interest / being received (both the relay UE and the remote UE can carry this message).

[0214] b) When selecting a relay UE, the Remote UE will not only consider information such as the PC5 channel quality, but also refer to whether the UE supports the multicast feature, and further consider whether the multicast services it is interested in / transmitting are the same as the multicast services it is interested in.

[0215] i. The Remote UE performs priority sorting on potential Relay UEs. The sorting rule may be based on the multicast service priority provided by the network (which may be broadcast by the network or configured per UE by the network) or the UE implementation. The UE selects the UE with the highest priority that meets the PC5 quality requirements as the Relay UE. If none of the high-priority potential relay UEs meet the PC5 quality requirements, the UE selects a relay UE according to the existing mechanism. Or,

[0216] ii. For multiple potential relay UEs that meet the PC5 channel quality requirements, the remote UE selects the UE with the most matching interested and / or transmitting services as its Relay UE. If not, the UE selects a relay UE according to the existing mechanism.

[0217] c) After the Remote UE selects a certain relay UE, it can send the multicast service information it is interested in or wants to receive during the establishment process of the PC5 interface or after the interface is established.

[0218] d) Possibly, the relay UE will also feedback the multicast service information it is transmitting / interested in.

[0219] 2. MRB establishment:

[0220] a) The Relay UE supports the multicast feature.

[0221] i. The Relay UE has not yet established an MRB for a remote for a certain MBS service.

[0222] 1) Based on the multicast service information exchanged via the PC5 interface or based on the indication of the network (in the case where the remote UE under this relay UE only sends the multicast service information to the network, such as initiating a join process), the Relay UE initiates a join process to join the multicast service group (MBS service 1), and at the same time indicates: whether it is used to serve the remote UE, and if so, it can also provide the corresponding remote UE information, such as the UE ID and the sidelink channel quality conditions between this UE and the relay UE.

[0223] 2) The gNB establishes an MRB based on the join request of the relay UE for the remote UE to receive multicast services through the relay UE. This MRB may be different from the MRB used for normal multicast service reception without using the relay UE or be the same MRB. For multiple remote UEs under the same relay, the PDCP and RLC adopt a common configuration.

[0224] Solution 1: The relay MRB serving the remote UE reuses the MRB of the relay UE itself. The protocol stacks between the gNB, relay UE, and remote UE can be combined Figure 4 for understanding. Figure 4 This is a schematic diagram of the protocol stacks between the gNB, relay UE, and remote UE in the embodiment of this application.

[0225] In this protocol stack, the relay UE establishes a normal MRB. However, based on the information with the remote UE, the relay UE copies the packets of this MRB from the PDCP layer and sends them to the PC5 MRB to the remote UE. The remote UE receives the corresponding packets from the PC5 and sends them to the DRB of the corresponding remote UE.

[0226] Solution 2: The relay UE serving the remote UE establishes an MRB independent of the MRB used for receiving MBS by itself and maps it to the corresponding PC5 RB through an adaptation layer (SRAP) for transmission. This content can be combined Figure 5 for understanding. Figure 5 This is a schematic diagram of the MRB in the embodiment of this application being mapped to the corresponding PC5 RB through the adaptation layer for transmission.

[0227] Solution comparison: Solution 1 can reduce the establishment of internal RBs in the remote UE and the reception of corresponding data (since it is an MBS service, it is equivalent to duplicate reception), and there is no need to add an adaptation layer for mapping between IP packets and the remote UE RB transmission. In addition, considering that the MBS service is received according to the group / G-RNTI, for the same service, if the same G-RNTI is received twice, which is different from the existing mechanism, additional design for the terminal is required. Therefore, Solution 1 is simpler for the remote UE. Solution 2 can maximize the reuse of the existing unicast mechanism, but it is necessary to add mapping information of the MRB.

[0228] 3) The relay UE sends data to multiple remote UEs in a broadcast manner: The relay UE can be configured by the base station indication or directly by the base station for the UE (through relay forwarding) with a group ID corresponding to the service under this relay UE (hereinafter represented by the relay group ID). That is, the remote UE will receive the MBS session information corresponding to the service (such as session ID, QoS flow information), the relay group ID, and the corresponding protocol station configuration. If the relay group ID is assigned by the relay UE, the relay UE needs to inform the base station of this ID. For subsequent data transmission, in the case of not using the relay UE MRB scheme, the base station includes the MBS session information and / or the relay group ID in the SRAP layer so that the relay UE can correctly address one or more remote UEs.

[0229] 4) When another remote UE (remote UE1) selects this relay UE and, based on the multicast service support information of the relay UE, learns that it has established an MRB for MBS service 1 transmission, remote UE1 will apply to join the MBS session corresponding to this service. Optionally, it can join the existing relay group of this relay UE (or select after interacting with the relay UE about preferences, UE level, etc.) or establish a separate link / relay group. This content can be combined Figure 6 for understanding. Figure 6 This is a schematic diagram of a remote UE applying to join a multicast service in an embodiment of this application.

[0230] ii. If the relay UE has established an MRB for a certain MBS service, it can reuse the situation in 4) above and join the corresponding group.

[0231] b) The relay UE does not support the air interface MBS feature.

[0232] The gNB establishes a unicast RB for the relay UE to receive the multicast service, indicates the remote UE ID information, and maps the RB used by the remote UE for multicast service reception to the PC5 interface transmission. Similarly, the PC5 interface grouping can be configured for resource reuse on the PC5.

[0233] In the embodiments of the present application, the establishment of MRB and the protocol stack design in the sidelink relay scenario, especially the design of the relay UE MRB protocol stack; the design of the remote UE join process in the sidelink relay scenario (enhanced based on the join process of the relay UE); the design of the relay UE selection mechanism and information interaction: the support situation of the MBS feature between UEs through PC5 interface interaction; the distribution of MBS (air interface) data through PC5 interface broadcast; the join RB establishment and relay UE selection and other processes for receiving MBS data in the sidelink relay scenario can be implemented.

[0234] To implement the method of the embodiments of the present application, the embodiments of the present application further provide a multicast and broadcast processing device, which is set on the first terminal, as Figure 7 shown Figure 7 is a schematic structural diagram of a multicast and broadcast processing device according to an embodiment of the present application; the device 700 includes:

[0235] An obtaining unit 701, configured to obtain a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal;

[0236] An implementing unit 702, configured to implement a multicast service by using the relay multicast radio bearer or the unicast resource block.

[0237] In an embodiment, the device 700 further includes a judging unit; wherein,

[0238] The judging unit is configured to judge whether the first terminal supports the multicast feature based on the self-capability of the first terminal, and obtain a judgment result;

[0239] The obtaining unit 701 is further configured to obtain a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal based on the judgment result.

[0240] In an embodiment, the obtaining unit 701 is further configured to send a first request message to the network device when the judgment result indicates that the first terminal supports the multicast feature; the first request message is used for the network device to determine a relay multicast radio bearer for the first terminal serving at least one second terminal;

[0241] The implementing unit 702 is further configured to transmit a multicast service to each of the second terminals by using the relay multicast radio bearer.

[0242] In one embodiment, the relay multicast radio bearer includes a first multicast radio bearer of the first terminal itself; the first terminal communicates directly with each of the second terminals; the apparatus 700 further includes a sending unit, configured to send data packets of the first multicast radio bearer to each of the second terminals through the multicast radio bearer corresponding to the direct communication; the data packets of the first multicast radio bearer are encapsulated according to the direct communication PC5 interface protocol and correspond to the radio link control channel (RLC Channel) of the second terminal.

[0243] In one embodiment, the relay multicast radio bearer includes a second multicast radio bearer established; the first terminal communicates directly with each of the second terminals; the apparatus 700 further includes a determining unit and a transmitting unit; wherein,

[0244] the determining unit is configured to determine the correspondence between the second multicast radio bearer and the resource block corresponding to the direct communication;

[0245] the transmitting unit is configured to transmit multicast services to each of the second terminals by using the correspondence.

[0246] In one embodiment, the sending unit is further configured to send configuration information of the target multicast service of the first terminal to the second terminal; the configuration information is used for the second terminal to participate in the multicast broadcast session procedure of the target multicast service.

[0247] In one embodiment, the configuration information includes at least one of the following:

[0248] identification information;

[0249] forwarded multicast broadcast session control information.

[0250] In one embodiment, the sending unit is further configured to send first information to each of the second terminals; the first information is used for the second terminal to determine whether to select the first terminal as the terminal serving itself.

[0251] In one embodiment, the apparatus 700 further includes a receiving unit, configured to receive second information sent by each of the second terminals; the second information represents whether the second terminal selects the first terminal as the terminal serving itself.

[0252] In one embodiment, the first information or the second information includes at least one of the following:

[0253] indication information on whether multicast features are supported;

[0254] attribute information of the multicast service;

[0255] priority information of the multicast service;

[0256] Quality information of the direct communication channel.

[0257] In one embodiment, the obtaining unit 701 is further configured to obtain a unicast resource block configured by a network device for the first terminal when the judgment result indicates that the first terminal does not support the multicast feature.

[0258] The implementing unit 702 is further configured to receive the multicast service sent by the network device by using the unicast resource block.

[0259] To implement the method on the terminal side in the embodiments of the present application, the embodiments of the present application further provide a multicast and broadcast processing device, which is disposed on a network device, as Figure 8 shown Figure 8 FIG. is a schematic structural diagram of another multicast and broadcast processing device in the embodiments of the present application. The device 800 includes:

[0260] A providing unit 801, configured to provide a relay multicast radio bearer determined for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal to the first terminal; the relay multicast radio bearer or the unicast resource block is used for the first terminal to implement a multicast service.

[0261] In one embodiment, the providing unit 801 is further configured to provide a relay multicast radio bearer determined for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal to the first terminal according to whether the first terminal itself supports the multicast feature.

[0262] In one embodiment, the device 800 further includes a receiving unit and a determining unit; wherein,

[0263] The receiving unit is configured to receive first request information sent by the first terminal when the first terminal supports the multicast feature.

[0264] The determining unit is configured to determine a relay multicast radio bearer for the first terminal serving at least one second terminal based on the first request information; the relay multicast radio bearer is used for the first terminal to transmit a multicast service to each of the second terminals.

[0265] In one embodiment, the device 800 further includes a configuration unit; wherein,

[0266] The configuration unit is configured to configure a unicast resource block for the first terminal when the first terminal does not support the multicast feature; the unicast resource block is used to receive the multicast service sent by the network device.

[0267] To implement the method on the second terminal side in the embodiments of the present application, the embodiments of the present application further provide a processing device for multicast and broadcast, which is set on the second terminal, as Figure 9 shown Figure 9 FIG. 4 is a schematic structural diagram of another processing device for multicast and broadcast in the embodiments of the present application. The device 900 includes:

[0268] A receiving unit 901, configured to receive configuration information of a target multicast service of a first terminal;

[0269] A joining unit 902, configured to join the multicast and broadcast session process of the target multicast service based on the configuration information.

[0270] In one embodiment, the configuration information includes at least one of the following:

[0271] Identification information;

[0272] Multicast and broadcast session control information.

[0273] In one embodiment, the device 900 further includes a determining unit; wherein,

[0274] The receiving unit is further configured to receive first information sent by the first terminal;

[0275] The determining unit is configured to determine whether to select the first terminal as the terminal serving itself based on the first information.

[0276] In one embodiment, the device 900 further includes a sending unit, configured to send second information to the first terminal; the second information indicates whether the second terminal selects the first terminal as the terminal serving itself.

[0277] In one embodiment, the first information or the second information includes at least one of the following:

[0278] Indication information of whether multicast characteristics are supported;

[0279] Attribute information of the multicast service;

[0280] Priority information of the multicast service;

[0281] Quality information of the direct communication channel.

[0282] It should be noted that when the multicast and broadcast processing device provided in the above embodiments processes multicast and broadcast, only the division of the above program modules is used for illustration. In actual applications, the above processing can be allocated to different program modules according to needs, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the multicast and broadcast processing device provided in the above embodiments and the method embodiments of multicast and broadcast processing belong to the same concept. For the specific implementation process, please refer to the method embodiments, which will not be elaborated here.

[0283] Based on the hardware implementation of the above program modules, an embodiment of the present application further provides a first terminal, including: a first processor and a first memory for storing a computer program that can run on the processor. Wherein, when the first processor is used to run the computer program, the steps in the multicast and broadcast processing method provided in the above embodiments are implemented.

[0284] Based on the hardware implementation of the above program modules, an embodiment of the present application further provides a network device, including: a second processor and a second memory for storing a computer program that can run on the processor. Wherein, when the second processor is used to run the computer program, the steps in the multicast and broadcast processing method provided in the above embodiments are implemented.

[0285] Based on the hardware implementation of the above program modules, an embodiment of the present application further provides a second terminal, including: a third processor and a third memory for storing a computer program that can run on the processor. Wherein, when the third processor is used to run the computer program, the steps in the multicast and broadcast processing method provided in the above embodiments are implemented.

[0286] Correspondingly, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps in the multicast and broadcast processing method provided in the above embodiments are implemented.

[0287] It should be pointed out here that the descriptions of the above storage medium and device embodiments are similar to the descriptions of the above method embodiments and have beneficial effects similar to those of the method embodiments. For the technical details not disclosed in the storage medium and device embodiments of the present application, please refer to the descriptions of the method embodiments of the present application for understanding.

[0288] It should be noted that Figure 10 is a schematic structural diagram of the first terminal according to an embodiment of the present application. As Figure 10 shown, the first terminal 1000 includes: a first processor 1001 and a first memory 1003. Optionally, the first terminal 1000 may further include a first communication interface 1002.

[0289] It can be understood that the first memory 1003 can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory), an electrically erasable programmable read-only memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), a ferromagnetic random access memory (FRAM, ferromagnetic random access memory), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM, Compact Disc Read-Only Memory); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM, Random Access Memory), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as a static random access memory (SRAM, Static Random Access Memory), a synchronous static random access memory (SSRAM, Synchronous Static Random Access Memory), a dynamic random access memory (DRAM, Dynamic Random Access Memory), a synchronous dynamic random access memory (SDRAM, Synchronous Dynamic Random Access Memory), a double data rate synchronous dynamic random access memory (DDR SDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), an enhanced synchronous dynamic random access memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), a sync link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and a direct rambus random access memory (DRRAM, Direct Rambus Random Access Memory).The first memory 1003 described in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memories.

[0290] The method disclosed in the embodiments of the present application can be applied to or implemented by the first processor 1001. The first processor 1001 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the first processor 1001 or the instructions in the form of software. The above-mentioned first processor 1001 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 1001 can implement or execute each method, step, and logic block diagram disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or by a combination of the hardware and software modules in the decoding processor. The software module may be located in the storage medium, which is located in the first memory 1003. The first processor 1001 reads the information in the first memory 1003 and combines its hardware to complete the steps of the foregoing method.

[0291] It should be noted that Figure 11 is a schematic structural diagram of the network device in the embodiments of the present application. As Figure 11 shown, the network device 1100 includes: a second processor 1101 and a second memory 1103. Optionally, the terminal 1100 may further include a second communication interface 1102.

[0292] It can be understood that the second memory 1103 can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory), an electrically erasable programmable read-only memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), a ferromagnetic random access memory (FRAM, ferromagnetic random access memory), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM, Compact Disc Read-Only Memory); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM, Random Access Memory), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as a static random access memory (SRAM, Static Random Access Memory), a synchronous static random access memory (SSRAM, Synchronous Static Random Access Memory), a dynamic random access memory (DRAM, Dynamic Random Access Memory), a synchronous dynamic random access memory (SDRAM, Synchronous Dynamic Random Access Memory), a double data rate synchronous dynamic random access memory (DDR SDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), an enhanced synchronous dynamic random access memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), a sync link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), a direct rambus random access memory (DRRAM, Direct Rambus Random Access Memory).The second memory 1103 described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memories.

[0293] The method disclosed in the embodiments of the present application above can be applied to the second processor 1101 or implemented by the second processor 1101. The second processor 1101 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the second processor 1101 or instructions in the form of software. The above second processor 1101 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 1101 can implement or execute each method, step, and logic block diagram disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiments of the present application, it can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and this storage medium is located in the second memory 1103. The second processor 1101 reads the information in the second memory 1103 and combines its hardware to complete the steps of the foregoing method.

[0294] It should be noted that Figure 12 is a schematic structural diagram of the second terminal in the embodiments of the present application. As Figure 12 shown, the second terminal 1200 includes: a third processor 1201 and a third memory 1203. Optionally, the second terminal 1200 may further include a third communication interface 1202.

[0295] It can be understood that the third memory 1203 can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory), an electrically erasable programmable read-only memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), a ferromagnetic random access memory (FRAM, ferromagnetic random access memory), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM, Compact Disc Read-Only Memory); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM, Random Access Memory), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as a static random access memory (SRAM, Static Random Access Memory), a synchronous static random access memory (SSRAM, Synchronous Static Random Access Memory), a dynamic random access memory (DRAM, Dynamic Random Access Memory), a synchronous dynamic random access memory (SDRAM, Synchronous Dynamic Random Access Memory), a double data rate synchronous dynamic random access memory (DDR SDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), an enhanced synchronous dynamic random access memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), a sync link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and a direct rambus random access memory (DRRAM, Direct Rambus Random Access Memory).The third memory 1203 described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memories.

[0296] The method disclosed in the embodiments of the present application above can be applied to or implemented by the third processor 1201. The third processor 1201 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the third processor 1201 or instructions in the form of software. The above-mentioned third processor 1201 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The third processor 1201 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiments of the present application, it can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by the combination of the hardware and software modules in the decoding processor. The software module may be located in the storage medium, which is located in the third memory 1203. The third processor 1201 reads the information in the third memory 1203 and combines its hardware to complete the steps of the foregoing method.

[0297] To implement the method provided in the embodiments of the present application, the embodiments of the present application also provide a multicast and broadcast processing system, as Figure 13 shown Figure 13 is a schematic structural diagram of the multicast and broadcast processing system in the embodiments of the present application. The system includes: a first terminal 1301, a network device 1302, and a second terminal 1303.

[0298] Here, it should be noted that: The specific processing processes of the first terminal 1301, the network device 1302, and the second terminal 1303 have been described in detail above and will not be elaborated here.

[0299] In an exemplary embodiment, the device may be implemented by one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general purpose processors, controllers, microcontroller units (MCUs), microprocessors, or other electronic components for performing the foregoing method.

[0300] It should be understood that the phrase "one embodiment" or "an embodiment" mentioned throughout the specification means that a particular feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present application. Therefore, the appearances of the phrase "in one embodiment" or "in an embodiment" throughout the specification do not necessarily refer to the same embodiment. Additionally, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that in various embodiments of the present application, the sequence numbers of the foregoing processes do not imply the order of execution. The order of execution of each process should be determined based on its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. The sequence numbers of the embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0301] It should be noted that in the present application, the term "comprising", "including" or any other variation thereof is intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus including a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the statement "comprising a..." does not exclude the existence of additional identical elements in the process, method, article, or apparatus including the element.

[0302] The methods disclosed in several method embodiments provided in the present application can be arbitrarily combined without conflict to obtain new method embodiments.

[0303] The features disclosed in several product embodiments provided in the present application can be arbitrarily combined without conflict to obtain new product embodiments.

[0304] The features disclosed in several method or device embodiments provided by this application can be combined arbitrarily without conflict to obtain new method embodiments or device embodiments.

[0305] As mentioned above, it is only the implementation mode of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art in the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claimed rights.

[0306] It should be noted that "first", "second", etc. are used to distinguish similar objects and do not necessarily have to be used to describe a specific order or sequence.

[0307] In addition, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0308] As mentioned above, it is only the preferred embodiment of this application and is not used to limit the protection scope of this application.

Claims

1. A method for processing multicast broadcasts, characterized in that, Applied to a first terminal, including: Obtaining a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal; Implementing a multicast service by using the relay multicast radio bearer or the unicast resource block.

2. The method according to claim 1, characterized in that The method further includes: Judging whether to support the multicast feature based on the capabilities of the first terminal to obtain a judgment result; Obtaining a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal based on the judgment result.

3. The method according to claim 2, wherein The obtaining, based on the judgment result, of a relay multicast radio bearer determined by a network device for the first terminal serving at least one second terminal includes: When the judgment result indicates that the first terminal supports the multicast feature, sending a first request message to the network device; the first request message is used for the network device to determine a relay multicast radio bearer for the first terminal serving at least one second terminal; The implementing of the multicast service by using the relay multicast radio bearer includes: Transmitting a multicast service to each of the second terminals by using the relay multicast radio bearer.

4. The method according to claim 1, wherein The relay multicast radio bearer includes a first multicast radio bearer of the first terminal itself; the first terminal communicates directly with each of the second terminals; the method further includes: Sending a data packet of the first multicast radio bearer to each of the second terminals through the multicast radio bearer corresponding to the direct communication; the data packet of the first multicast radio bearer is encapsulated according to the direct communication PC5 interface protocol and corresponds to the radio link control channel (RLC Channel) of the second terminal.

5. The method according to claim 1, characterized in that, The relay multicast radio bearer includes a second multicast radio bearer established; the first terminal communicates directly with each of the second terminals; the method further includes: Determining the correspondence between the second multicast radio bearer and the resource block corresponding to the direct communication; Transmitting a multicast service to each of the second terminals by using the correspondence.

6. The method according to claim 1, characterized in that The method further includes: Sending configuration information of a target multicast service of the first terminal to the second terminal; the configuration information is used for the second terminal to join the multicast broadcast session process of the target multicast service.

7. The method according to claim 6, characterized in that, The configuration information includes at least one of the following: Identification information; Forwarded multicast broadcast session control information.

8. The method according to claim 1, wherein The method further includes: Sending a first message to each of the second terminals; the first message is used for the second terminal to determine whether to select the first terminal as the terminal serving itself.

9. The method according to claim 8, wherein The method further includes: Receiving a second message sent by each of the second terminals; the second message indicates whether the second terminal selects the first terminal as the terminal serving itself.

10. The method according to claim 9, wherein The first message or the second message includes at least one of the following: Indication information on whether the multicast feature is supported; Attribute information of the multicast service; Priority information of the multicast service; Quality information of the direct communication channel.

11. The method according to claim 2, wherein The obtaining, based on the judgment result, of a unicast resource block configured for the first terminal by a network device includes: When the judgment result indicates that the first terminal does not support the multicast feature, obtain the unicast resource block configured by the network device for the first terminal; The implementation of the multicast service by using the unicast resource block includes: Receive the multicast service sent by the network device by using the unicast resource block.

12. A method for processing multicast and broadcast, characterized in that, Applied to a network device, it includes: Provide the first terminal with a relay multicast radio bearer determined for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal; the relay multicast radio bearer or the unicast resource block is used for the first terminal to implement the multicast service.

13. The method according to claim 12, wherein The method further includes: According to whether the first terminal itself supports the multicast feature, provide the first terminal with a relay multicast radio bearer determined for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal.

14. The method according to claim 13, wherein The method further includes: When the first terminal supports the multicast feature, receive the first request information sent by the first terminal; Based on the first request information, determine a relay multicast radio bearer for the first terminal serving at least one second terminal; the relay multicast radio bearer is used for the first terminal to transmit the multicast service to each of the second terminals.

15. The method according to claim 13, wherein The method further includes: When the first terminal does not support the multicast feature, configure a unicast resource block for the first terminal; the unicast resource block is used to receive the multicast service sent by the network device.

16. A method for processing multicast and broadcast, characterized in that Applied to a second terminal, it includes: Receive the configuration information of the target multicast service of the first terminal; Based on the configuration information, join the multicast broadcast session process of the target multicast service.

17. The method according to claim 16, characterized in that, The configuration information includes at least one of the following: Identification information; Multicast broadcast session control information.

18. The method according to claim 16, characterized in that, The method further includes: Receive the first information sent by the first terminal; Based on the first information, determine whether to select the first terminal as the terminal serving itself.

19. The method according to claim 18, wherein The method further includes: Send second information to the first terminal; the second information indicates whether the second terminal selects the first terminal as the terminal serving itself.

20. The method according to claim 19, wherein The first information or the second information includes at least one of the following: Indicator information of whether it supports the multicast feature; Attribute information of the multicast service; Priority information of the multicast service; Quality information of the direct communication channel.

21. A processing device for multicast and broadcast, characterized in that, Set on the first terminal, it includes: An obtaining unit, configured to obtain a relay multicast radio bearer determined for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal by the network device; An implementing unit, configured to implement the multicast service by using the relay multicast radio bearer or the unicast resource block.

22. A processing device for multicast and broadcast, characterized in that, Set on the network device, it includes: A providing unit, configured to provide the first terminal with a relay multicast radio bearer determined for the first terminal serving at least one second terminal or a unicast resource block configured for the first terminal; the relay multicast radio bearer or the unicast resource block is used for the first terminal to implement the multicast service.

23. A processing device for multicast and broadcast, characterized in that, Set on the second terminal, it includes: A receiving unit, configured to receive the configuration information of the target multicast service of the first terminal; A joining unit, configured to join a multicast broadcast session process of the target multicast service based on the configuration information.

24. A first terminal, characterized in that, Comprising: A first processor and a first memory for storing a computer program that can run on the processor, wherein, when the first processor is used to run the computer program, it executes the steps of the method according to any one of claims 1 to 11.

25. A network device, characterized in that, Comprising: A second processor and a second memory for storing a computer program that can run on the processor, wherein, when the second processor is used to run the computer program, it executes the steps of the method according to any one of claims 12 to 15.

26. A second terminal, characterized in that, Comprising: A third processor and a third memory for storing a computer program that can run on the processor, wherein, when the third processor is used to run the computer program, it executes the steps of the method according to any one of claims 16 to 20.

27. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 11, or implements the steps of the method according to any one of claims 12 to 15, or implements the steps of the method according to any one of claims 16 to 20.

Images