Equipment for multicast and broadcast services

Abstract

Embodiments of the present application relate to a method and apparatus for multicast and broadcast services (MBS). An exemplary method includes: determining an association identification (ID) for associating a common layer entity with a first lower layer entity of a multicast data radio bearer (M-DRB) and a second lower layer entity of a unicast data radio bearer (U-DRB); and transmitting configuration information including the association ID. Embodiments of the present application can support dynamic changes between point-to-multipoint (PTM) mode and point-to-point (PTP) mode, while providing lossless and seamless conversion and / or switching between the PTM mode and the PTP mode.

Description

Technical Field

[0001] Embodiments of the present application generally relate to wireless communication technology, and more particularly, to a method and apparatus for multicast and broadcast service (MBS). Background Art

[0002] In New Radio (NR) Rel-17, the MBS plan focuses on small area mixed mode multicast (also referred to as Objective A in TR 23.757). Objective A is about enabling generic MBS services on 5G systems (5GS), and identified use cases that can benefit from this feature. These use cases include, but are not limited to: public safety and mission critical, vehicle-to-everything (V2X) applications, transparent Internet Protocol version 4 (Ipv4) / Internet Protocol version 6 (Ipv6) multicast delivery, Internet Protocol Television (IPTV), software delivery over wireless, group communications, and Internet of Things (IoT) applications. In these use cases, the requirements for service continuity and reliability have changed. To support the above requirements, one of the objectives introduced in RP-201038 is to specify support for dynamic changes in broadcast / multicast service delivery between multicast (e.g., point-to-multipoint (PTM) mode) and unicast (e.g., point-to-point (PTP) mode) with service continuity for a given user equipment (UE).

[0003] In view of the foregoing, the industry desires to improve technologies for multicast and broadcast services to support dynamic changes between PTM mode and PTP mode while providing lossless and seamless conversion and / or switching between PTM mode and PTP mode. Summary of the invention

[0004] Some embodiments of the present application at least provide a technical solution for multicast and broadcast services.

[0005] According to some embodiments of the present application, a method may include: determining an association identification (ID) for associating a common layer entity with a first lower layer entity for a multicast data radio bearer (M-DRB) and a second lower layer entity for a unicast data radio bearer (U-DRB); and sending configuration information including the association identification (ID).

[0006] According to some other embodiments of the present application, a method may include: receiving configuration information including an association identification (ID) for associating a common layer entity with a first lower layer entity for M-DRB and a second lower layer entity for U-DRB; and configuring at least one of the common layer entity, the first lower layer entity, and the second lower layer entity based on the configuration information.

[0007] According to some other embodiments of the present application, a device may include: a common Packet Data Convergence Protocol (PDCP) entity; a first Radio Link Control (RLC) entity for M-DRB; and at least one second RLC entity, wherein each of the at least one second RLC entity is associated with a U-DRB of a UE.

[0008] According to some other embodiments of the present application, a device may include: a common PDCP entity; a first RLC entity for M-DRB; and a second RLC entity for U-DRB, wherein the common PDCP entity is associated with the first RLC entity and the second RLC entity.

[0009] Some embodiments of the present application also provide an apparatus comprising: at least one non-transitory computer-readable medium having computer-executable instructions stored therein; at least one receiver; at least one transmitter; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver, and the at least one transmitter. The computer-executable instructions are programmed to implement any of the methods set forth above with the at least one receiver, the at least one transmitter, and the at least one processor.

[0010] The embodiments of the present application provide a technical solution for multicast and broadcast services. Therefore, the embodiments of the present application can support dynamic changes between PTM mode and PTP mode, and provide lossless and seamless conversion and / or switching between PTM mode and PTP mode. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to describe the manner in which the advantages and features of the present application can be obtained, the description of the present application is presented by reference to specific embodiments thereof illustrated in the accompanying drawings. These drawings depict only example embodiments of the present application and therefore should not be considered limiting of its scope.

[0012] Figure 1 is a schematic diagram illustrating an exemplary wireless communication system 100 according to some embodiments of the present application;

[0013] Figure 2 is a flowchart illustrating a method of MBS according to some other embodiments of the present application;

[0014] Figure 3 An example of configuring an association identification (ID) according to some embodiments of the present application is described;

[0015] Figure 4 Another example of configuring an association identification (ID) according to some embodiments of the present application is described;

[0016] Figure 5 Another example of configuring an association identification (ID) according to some embodiments of the present application is described;

[0017] Figure 6 An example of a protocol structure of a BS according to some embodiments of the present application is described;

[0018] Figure 7 An example of a protocol structure of a BS according to some other embodiments of the present application is described;

[0019] Figure 8 An example of a PDCP entity of a BS according to some embodiments of the present application is described;

[0020] Fig. 9 Another example of a PDCP entity of a BS according to some embodiments of the present application is described;

[0021] Fig.10 Another example of a PDCP entity of a BS according to some embodiments of the present application is described;

[0022] Fig.11 is a flowchart illustrating a method of MBS according to some other embodiments of the present application;

[0023] Fig.12 An example of a protocol structure of a UE according to some embodiments of the present application is described;

[0024] Fig.13 An example of a protocol structure of a UE according to some other embodiments of the present application is described;

[0025] Fig.14 An example of a PDCP entity of a UE according to some embodiments of the present application is described;

[0026] Fig.15 A simplified block diagram illustrating an apparatus of an MBS according to some embodiments of the present application; and

[0027] Fig.16 A simplified block diagram illustrating an apparatus of an MBS according to some other embodiments of the present application. DETAILED DESCRIPTION

[0028] The detailed description of the accompanying drawings is intended as a description of the currently preferred embodiments of the present application, and is not intended to represent the only form in which the present application can be practiced. It should be understood that the same or equivalent functions can be accomplished by different embodiments that are intended to be included in the spirit and scope of the present application.

[0029] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architectures and new service cases (e.g., 3GPP 5G, 3GPP LTE Release 8, etc.). Those skilled in the art will appreciate that the embodiments in the present application may also be applicable to similar technical problems with the development of network architectures and new service cases.

[0030] Figure 1 is a schematic diagram illustrating an exemplary wireless communication system 100 according to an embodiment of the present application.

[0031] like Figure 1 , the wireless communication system 100 includes at least one BS 101 and at least one UE 102. Specifically, for the purpose of illustration, the wireless communication system 100 includes one BS 101 and two UEs 102 (eg, UE 102a and UE 102b). Figure 1 A specific number of BSs 101 and UEs 102 are depicted in FIG. 1 , but it is contemplated that any number of BSs 101 and UEs 102 may be included in wireless communication system 100 .

[0032] BS 101 may also be referred to as an access point, an access terminal, a base station, a macro cell, a Node-B, an enhanced Node B (eNB), a gNB, a Home Node-B, a relay node, or a device, or described using other terms used in the art. BS 101 is typically part of a radio access network that may include a controller communicatively coupled to BS 101.

[0033] UE 102 may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, and a modem), etc. According to an embodiment of the present application, UE 102 may include a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiver, or any other device capable of sending and receiving communication signals on a wireless network. In some embodiments, UE 102 may include a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, UE 102 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terms used in the art.

[0034] The wireless communication system 100 is compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with wireless communication networks, cellular telephone networks, time division multiple access (TDMA)-based networks, code division multiple access (CDMA)-based networks, orthogonal frequency division multiple access (OFDMA)-based networks, LTE networks, 3GPP-based networks, 3GPP 5G networks, satellite communication networks, high altitude platform networks, and / or other communication networks.

[0035] BS101 may transmit the same MBS data to UE 102a and UE 102b. For example, the MBS data may be transmitted to UE 102a and UE 102b via a PTM mode. In another example, the MBS data may be transmitted to UE 102a and UE 102b, respectively, via a PTP mode. In NR Rel-17, one goal is to specify support for dynamic changes in broadcast / multicast service delivery between multicast (PTM) and unicast (PTP) with service continuity for a given UE. In order to support dynamic, seamless and lossless switching between PTM transmission and PTP transmission, a solution based on a radio access network (RAN) needs to be considered. A RAN-based solution should address the following issues: 1) how to support dynamic changes in PTM mode and PTP mode within the RAN; and 2) how to provide lossless and seamless conversion and / or switching between PTM mode and PTP mode within the RAN.

[0036] Therefore, the embodiments of the present application provide a technical solution for MBS, which can support dynamic changes between the PTM mode and the PTP mode, while providing lossless and seamless conversion and / or switching between the PTM mode and the PTP mode. More details about the embodiments of the present application will be described in the following text in combination with the accompanying drawings.

[0037] Figure 2 is a flowchart illustrating a method of MBS according to some embodiments of the present application. The method may be performed by a BS (eg, Figure 1 BS101) shown in the implementation.

[0038] exist Figure 2In the exemplary method shown in , in step 202, BS101 may determine an association identification (ID) for associating a common layer entity with a first lower layer entity (e.g., a lower layer entity for an M-DRB) and a second lower layer entity (e.g., a lower layer entity for a U-DRB). In some embodiments, the first lower layer entity may refer to a lower layer entity of a U-DRB, and the second lower layer entity may refer to a lower layer entity of an M-DRB. In some embodiments, the association identification (ID) may also be used to associate an M-DRB with a U-DRB. For example, the association identification (ID) is used to associate a multicast RLC bearer with a unicast RLC bearer, wherein the multicast RLC bearer and the unicast RLC bearer may have the same common layer entity.

[0039] M-DRB may refer to a radio bearer or RLC bearer for data transmission via PTM mode. M-DRB is scrambled by a group radio network temporary identifier (G-RNTI) in at least one cell. M-DRB may also be named a multicast radio bearer (MRB). U-DRB may refer to a radio bearer or RLC bearer for data transmission via PTP mode. U-DRB is scrambled by a cell radio network temporary identifier (C-RNTI). U-DRB may also be named a data radio bearer (DRB). The same approach of a single radio bearer (SRB) may also be considered. For example, M-DRB may be replaced by M-SRB, which may refer to a radio bearer or RLC bearer for signaling transmission via PTM mode. U-DRB may be replaced by U-SRB, which may refer to a radio bearer or RLC bearer for signaling transmission via PTP mode.

[0040] After determining the association identification (ID), in step 204, BS 101 may transmit configuration information including the association identification (ID) to UE 102 (e.g., UE 102a or UE 102b). According to some embodiments of the present application, the configuration information may include at least one of the following: information for configuring a common layer entity, information for configuring a first lower layer entity, and information for configuring a second lower layer entity. Using the associated ID, the common layer entity, the first lower layer entity, and the second lower layer entity are associated for data transmission of the same MBS service.

[0041] According to some embodiments of the present application, an association identification (ID) may be transmitted to the UE 102 in a radio resource control (RRC) reconfiguration message.

[0042] According to some embodiments of the present application, the common layer entity may include a sequence numbering function. The sequence numbering function may include at least one of the following functions: sequence number allocation for each packet, packet reordering, and packet duplication.

[0043] According to some embodiments of the present application, the common layer may include a PDCP entity, the first lower layer entity may include a first RLC entity, and the second lower layer entity may include a second RLC entity.

[0044] In an embodiment of the present application, the association identification (ID) may include one of the following: M-DRB ID, U-DRB ID, logical channel ID (LCID), temporary mobile group identifier (TMGI), G-RNTI; and any other ID used to identify the association (e.g., a new ID different from the above IDs). In this embodiment, the association identification (ID) should be unique in a cell or a multicast area including at least one cell. Therefore, if the association identification (ID) is a U-DRB ID, the U-DRB ID may be a specific U-DRB ID used to identify the association, and is different from the U-DRB ID of UE 102. Similarly, if the association identification (ID) is an LCID, the LCID may be a specific LCID used to identify the association, and is different from the LCID of UE 102. For example, a specific LCID index and value may be represented by the following table specified in the 3GPP standard document TS38.321. In the table, each LCID index may have a corresponding identification of a logical channel of the MBS.

[0045] index LCID value 30 to 35 Identification of MBS logical channels

[0046] In this embodiment, the association identification (ID) may be included in the first configuration information of the PDCP entity, the second configuration information of the first RLC entity, and the third configuration information of the second RLC entity.

[0047] For example, Figure 3 An example of configuring an association identification (ID) according to some embodiments of the present application is described.

[0048] like Figure 3 As shown in FIG. 5 , the first configuration information of the PDCP entity may be a RadioBearerConfig information element (IE), which at least includes SDAP-config for configuring the Service Data Adaptation Protocol (SDAP) and PDCP-config for configuring PDCP.

[0049] The second configuration information of the first RLC entity may be CellGroupConfigforM-DRB IE, which includes RLC-BearerConfig(M-DRB ID, LCID1) for configuring the first RLC entity of M-DRB, MAC-CellGroupConfig for configuring the media access control (MAC) layer of M-DRB, and PHY-CellGroupConfig for configuring the PHY layer of M-DRB.

[0050] The third configuration information of the second RLC entity may be CellGroupConfigforU-DRB-UE102 IE, which includes RLC-BearerConfig(U-DRB ID, LCID2) for configuring the second RLC entity of U-DRB, MAC-CellGroupConfig for configuring the MAC layer of U-DRB, and PHY-CellGroupConfig for configuring the PHY layer of U-DRB.

[0051] like Figure 3 As shown in FIG. 1 , all RadioBearerConfig IEs, CellGroupConfigforM-DRB IEs and CellGroupConfigforU-DRB-UE102 IEs include an association identification (ID), so that UE 102 can associate the PDCP entity with the first RLC and the second RLC after receiving the above three IEs, and UE 102 can also associate the first RLC with the second RLC.

[0052] According to the above embodiments of the present application, the RadioBearerConfig IE and CellGroupConfig IE specified in the 3GPP standard document may be changed. For example, an association identification (ID) may be added to the above two IEs as follows.

[0053] RadioBearerConfig IE

[0054]

[0055] CellGroupConfig IE

[0056]

[0057]

[0058] In another embodiment of the present application, the association identification (ID) may include the M-DRB ID of the M-DRB and the U-DRB ID of the U-DRB. In this embodiment, BS101 may use the M-DRB ID and the U-DRB ID of UE102 as the association identification (ID).

[0059] In this embodiment, the association identification (ID) may be included in the fourth configuration information of the PDCP entity and the fifth configuration information of the first RLC entity and the second RLC entity.

[0060] In an embodiment of the present application, the fourth or fifth configuration information may include an activation indication indicating whether to use M-DRB, U-DRB or both. In another embodiment of the present application, the fourth or fifth configuration information may include a switching indication indicating switching from M-DRB to U-DRB or from U-DRB to M-DRB.

[0061] For example, Figure 4 An example of configuring an association identification (ID) according to some embodiments of the present application is described.

[0062] like Figure 4 As shown in FIG. , the fourth configuration information of the PDCP entity may be the RadioBearerConfig IE, which at least includes PDCP-config for configuring the PDCP entity.

[0063] The fifth configuration information of the first RLC entity and the second RLC entity may be a CellGroupConfig IE, which includes at least RLC-BearerConfig-M-DRB for configuring the first RLC entity as an M-DRB and RLC-BearerConfig-U-DRB for configuring the second RLC entity as a U-DRB.

[0064] like Figure 4 As shown in , both the RadioBearerConfig IE and the CellGroupConfig IE include the M-DRB ID of the M-DRB and the U-DRB ID of the U-DRB as association identifiers (IDs), so that the UE 102 can associate the PDCP entity with the first RLC and the second RLC after receiving the above IEs.

[0065] exist Figure 4 In the example, the CellGroupConfig IE also includes an activation leg indication (both, M-DRB, U-DRB) for indicating whether to use M-DRB, U-DRB or both. In addition, the CellGroupConfig IE also includes a switching indication (to U-DRB, to M-DRB) for indicating switching from M-DRB to U-DRB or from U-DRB to M-DRB.

[0066] According to the above-mentioned embodiments of the present application, the RadioBearerConfig IE and CellGroupConfig IE specified in the 3GPP standard document may be changed. For example, an association identification (ID) may be added to the RadioBearerConfig IE as follows.

[0067] RadioBearerConfig Information Element

[0068]

[0069]

[0070] In another embodiment of the present application, the CellGroupConfig IE may include only the RLC-BearerConfig-M-DRB IE or the RLC-BearerConfig-U-DRB IE. If only the RLC-BearerConfig-M-DRB IE is configured, the UE will use the M-DRB with the corresponding configuration, such as PDCP-Config and RLC-BearerConfig-M-DRB to receive data transmission. If only the RLC-BearerConfig-U-DRB IE is configured, the UE will use the DRB with the corresponding configuration, such as PDCP-Config and RLC-BearerConfig-U-DRB to receive data transmission.

[0071] According to some other embodiments of the present application, the common layer may include at least one of a PDCP entity, an RLC entity, and a MAC entity, the first lower layer entity may include a first physical (PHY) entity, and the second lower layer entity may include a second PHY entity. The common layer may also include at least one of a PDCP entity, an RLC entity, a MAC entity, and a higher portion of a PHY entity, and the first lower layer entity may include a first lower portion of a PHY entity, and the second lower layer entity may include a second lower portion of a PHY entity.

[0072] In an embodiment of the present application, the association identification (ID) may be included in the sixth configuration information of the radio bearer and the seventh configuration information of the cell group.

[0073] For example, Figure 5 An example of configuring an association identification (ID) according to some embodiments of the present application is described.

[0074] like Figure 5 As shown in FIG. 5 , the sixth configuration information of the radio bearer may be RadioBearerConfig IE, which at least includes PDCP-config for configuring the PDCP entity.

[0075] The seventh configuration information of the cell group may be CellGroupConfig IE, which includes at least RLC-BearerConfig IE for configuring the RLC entity, MAC-CellgroupConfig IE for configuring the MAC entity, PHY-CellGroupConfig-M-DRB IE for configuring the first physical entity of M-DRB and PHY-CellGroupConfig-U-DRB IE for configuring the second physical entity of U-DRB.

[0076] like Figure 5 As shown in FIG. 1 , both the RadioBearerConfig IE and the CellGroupConfig IE include an association identification (ID) (eg, an M-DRB ID or a specific LCID), so that the UE 102 can associate at least one of the PDCP entity, the RLC entity, and the MAC entity with the two physical entities after receiving the above IEs.

[0077] According to some embodiments of the present application, BS101 may include: a common layer entity; a first lower layer entity of the M-DRB; and at least one second lower layer entity, wherein each of the at least one second lower layer entity is associated with a U-DRB of the UE, wherein the common layer entity is associated with the first lower layer entity of the M-DRB and the at least one second lower layer entity.

[0078] In an embodiment of the present application, the common layer entity may include at least one of a PDCP entity, an RLC entity, and a MAC entity, the first lower layer entity may include a first PHY layer, and at least one second lower layer entity may include at least one second PHY entity. In this embodiment, BS101 may include: a PDCP entity, an RLC entity, a MAC entity, a PHY entity of an M-DRB; and at least one PHY entity of at least one U-DRB, wherein each of the at least one PHY entity is associated with a U-DRB of a UE. The common layer may also include at least one of a PDCP entity, an RLC entity, a MAC entity, and a higher portion of a PHY entity, and the first lower layer entity may include a first lower portion of a PHY entity, and at least one second lower layer entity may include at least one second lower portion of a PHY entity.

[0079] For example, Figure 6 An example of a protocol structure of a BS according to some embodiments of the present application is described.

[0080] like Figure 6As shown in FIG, a protocol structure of a BS (e.g., BS 102) may include a PDCP entity, an RLC entity, and a MAC entity. The PDCP entity, the RLC entity, and the MAC entity may be associated with a PHY entity of an M-DRB and two PHY entities of two U-DRBs, one of which is associated with the U-DRB of UE 102a and the other with the U-DRB of UE 102b. Figure 6 In the embodiment, the M-DRB, U-DRB of UE 102a and U-DRB of UE 102b may have the same LCID, for example, a specific LCID may be used for both the M-DRB and all U-DRBs. In the physical layer, the M-DRB is scrambled by the G-RNTI, the U-DRB of UE 102a is scrambled by the C-RNTI of UE 102a, and the U-DRB of UE 102b is scrambled by the C-RNTI of UE 102b.

[0081] In another embodiment of the present application, the common layer entity may include a PDCP entity, the first lower layer entity may include a first RLC entity, and the at least one second lower layer entity may include at least one second RLC entity. In this embodiment, BS101 may include: a common PDCP entity; an RLC entity of an M-DRB; and at least one RLC entity of at least one U-DRB, wherein each of the at least one RLC entity is associated with a U-DRB of a UE.

[0082] For example, Figure 7 An example of a protocol structure of a BS according to some embodiments of the present application is described.

[0083] like Figure 7 As shown in FIG. 1 , a protocol structure of a BS (e.g., BS 102) may include a common PDCP entity, which may be associated with one RLC entity for an M-DRB and two RLC entities for two U-DRBs, one RLC entity associated with the U-DRB of UE 102a and the other RLC entity associated with the U-DRB of UE 102b. Each of the three RLC entities may be associated with a corresponding PHY entity.

[0084] exist Figure 7In the embodiment, the protocol structure of BS102 may include a MAC entity. The M-DRB has a specific LCID (e.g., LCID1) that is unique in a cell or a multicast area (e.g., a cell list) that includes at least one cell. Each U-DRB may have a corresponding LCID. For example, the U-DRB of UE 102a may have LCID2, and the U-DRB of UE 102b may have LCID3. In the physical layer, the M-DRB is scrambled by the G-RNTI, the U-DRB of UE 102a is scrambled by the C-RNTI of UE102a, and the U-DRB of UE102b is scrambled by the C-RNTI of UE102b. In some other embodiments, the M-DRB, U-DRB of UE102a, and the U-DRB of UE102b may have the same specific LCID.

[0085] Those skilled in the art will appreciate that the two RLC entities of the two UEs are only for illustrative purposes. According to some other embodiments of the present application, BS101 may have at least one RLC entity, each RLC entity being associated with a U-DRB of a UE, having a corresponding LCID, and being associated with a PHY entity.

[0086] In the above embodiment, a common PDCP entity is used for the M-DRB and at least one U-DRB. The biggest advantage of the common PDCP entity with the same sequence numbering function is to provide service continuity when switching between the M-DRB and the U-DRB.

[0087] In order to provide lossless switching between M-DRB and U-DRB, some embodiments of the present application provide the functionality of a common PDCP entity.

[0088] In an embodiment of the present application, the common PDCP entity may first assign a COUNT value or a sequence number to a PDCP service data unit (SDU). Then, the common PDCP entity may copy the PDCP SDU into multiple PDCP SDUs, wherein the multiple PDCP SDUs may include a first PDCP SDU of an M-DRB and at least one second PDCP SDU of at least one U-DRB, and wherein each of the at least one second PDCP SDU is associated with a U-DRB of a UE.

[0089] Thereafter, in case the header compression function is configured in the common PDCP entity, the common PDCP entity may perform header compression on each of the plurality of PDCP SDUs.

[0090] When security functions are configured for each U-DRB, for each of at least one second PDCP SDU, the common PDCP entity may use the COUNT value or sequence number of the UE associated with the PDCP SDU, the security algorithm and the key to perform integrity protection and / or encryption for the PDCP SDU to generate a secure PDCP SDU.

[0091] After generating at least one secure PDCP SDU, the common PDCP entity may add a COUNT value or a sequence number to a first PDCP SDU to generate a first PDCP protocol data unit (PDU) of the M-DRB, and add a COUNT value or a sequence number to each of the at least one secure PDCP SDU to generate at least one second PDCP PDU of the at least one U-DRB. Thereafter, the common PDCP entity may submit the first PDCP PDU to an RLC entity of the M-DRB, and submit each of the at least one second PDCP PDU to an RLC entity of a U-DRB of the at least one U-DRB.

[0092] For example, Figure 8 An example of a PDCP entity of a BS (eg, BS 102) according to some embodiments of the present application is described. Figure 8 In the example of , a common PDCP entity is used for M-DRB and U-DRB of UE 102 (e.g., UE 102a or UE 102b). Figure 8 In the example, security features are configured for U-DRB.

[0093] like Figure 8 As shown in the figure, the PDCP entity may include the following functionalities (also called functional modules).

[0094] Common sequence numbering function: For PDCP SDUs received from a layer higher than the PDCP layer, the common sequence numbering function may assign a COUNT value or a sequence number thereto. In an embodiment of the present application, the COUNT value or the sequence number may be continuous for the PDCP SDU sequence.

[0095] Duplicate function: The duplicate function may duplicate the PDCP SDU into two PDCP SDUs (named PDCP SDU A and PDCP SDU B), PDCP SDU A is used for the M-DRB, and PDCP SDU B is used for the U-DRB of the UE 102.

[0096] Header compression function: The header compression function is an optional function. If it is configured in the common PDCP entity, header compression can be performed on PDCP SDU A and PDCP SDU B. If it is not configured in the common PDCP entity, the common PDCP entity will not perform header compression on PDCP SDU A and PDCP SDU B.

[0097] Security function (e.g., integrity protection function and / or ciphering function): The security function may perform integrity protection and ciphering of PDCP SDU B using a COUNT value or sequence number associated with the PDCP SDU, the security algorithm and key of the UE 102. Thereafter, the PDCP SDU B is changed to a secure PDCP SDU B.

[0098] Since no security function is configured for the M-DRB, the PDCP entity shall skip the integrity protection and ciphering of PDCP SDU A.

[0099] PDCP header adding function: The PDCP header adding function can add the same COUNT value or sequence number in the headers of PDCP SDU A and secure PDCP SDU B. Using the header, PDCP SDU A becomes PDCP PDU A, and secure PDCP SDU B becomes PDCP PDU B.

[0100] The PDCP entity may then deliver PDCP PDU A to the associated RLC entity of the M-DRB and PDCP PDU B to the associated RLC entity of the U-DRB of UE 102.

[0101] Fig. 9 Another example of a PDCP entity of a BS (eg, BS 102) according to some embodiments of the present application is described. Figure 8 Unlike the example of , a common PDCP entity is used for the M-DRB and at least one U-DRB of at least one UE (e.g., the U-DRB of UE 102a and the U-DRB of UE 102b). Fig. 9 In an instance, security functions are configured for each U-DRB of at least one U-DRB.

[0102] like Fig. 9 As shown in the figure, the PDCP entity may include the following functionalities (also called functional modules).

[0103] Common sequence numbering function: For PDCP SDUs received from a layer higher than the PDCP layer, the common sequence numbering function may assign a COUNT value or a sequence number thereto. In an embodiment of the present application, the COUNT value or the sequence number may be continuous for the PDCP SDU sequence.

[0104] Copy function: The copy function may copy the PDCP SDU into three PDCP SDUs (named PDCP SDU A, PDCP SDU B, and PDCP SDU C), PDCP SDU A being used for the M-DRB, PDCP SDU B being used for the U-DRB of the UE 102a, and PDCP SDU C being used for the U-DRB of the UE 102b.

[0105] Header compression function: The header compression function is an optional function. If it is configured in the common PDCP entity, header compression can be performed for PDCP SDU A, PDCP SDU B and PDCP SDU C. If it is not configured in the common PDCP entity, the common PDCP entity will not perform header compression on PDCP SDU A, PDCP SDU B and PDCP SDU C.

[0106] Security function (e.g., integrity protection function and / or encryption function): The security function may use the COUNT value or sequence number associated with the PDCP SDU B, the security algorithm and key of the UE 102a to perform integrity protection and encryption of the PDCP SDU B, and use the COUNT value or sequence number associated with the PDCP SDU C, the security algorithm and key of the UE 102b to perform integrity protection and encryption of the PDCP SDU C. Then, the PDCP SDU B is changed to a secure PDCP SDU B, and the PDCP SDU C is changed to a secure PDCP SDU C.

[0107] Since no security function is configured for M-DRB, the PDCP entity shall skip integrity protection and ciphering of PDCP SDU A.

[0108] PDCP header adding function: The PDCP header adding function may add the same COUNT value or sequence number in the headers of PDCP SDU A, secure PDCP SDU B, and PDCP SDU C. Using the header, PDCP SDU A is changed to PDCP PDU A, secure PDCP SDU B is changed to PDCP PDU B, and secure PDCP SDU C is changed to PDCP PDU C.

[0109] The PDCP entity may then submit PDCP PDU A to the associated RLC entity of the M-DRB, PDCP PDU B to the associated RLC entity of the U-DRB of UE 102a, and PDCP PDU C to the associated RLC entity of the U-DRB of UE 102b.

[0110] In another embodiment of the present application, security functions may not be configured for each U-DRB. In this embodiment, the common PDCP entity may first allocate a COUNT value or a sequence number for the PDCP SDU.

[0111] Thereafter, if the header compression function is configured in the common PDCP entity, the common PDCP entity may perform header compression on the PDCP SDU.

[0112] Then, the common PDCP entity may add the COUNT value or sequence number associated with the PDCP SDU to generate the PDCP PDU. Thereafter, the common PDCP entity may copy the PDCP PDU into multiple PDCP PDUs, wherein the multiple PDCP PDUs include a first PDCP PDU of the M-DRB and at least one second PDCP PDU of at least one U-DRB, wherein each of the at least one second PDCP PDU is associated with a U-DRB of the UE.

[0113] After duplicating the plurality of PDCP PDUs, the common PDCP entity may submit a first PDCP PDU of the M-DRB to an RLC entity of the M-DRB, and submit each of at least one second PDCP PDU to an RLC entity of a U-DRB of at least one U-DRB.

[0114] For example, Fig.10 Another example of a PDCP entity of a BS (eg, BS 102) according to some embodiments of the present application is described. Fig.10 In the example of FIG. 1 , a common PDCP entity is used for an M-DRB of at least one UE and at least one U-DRB (e.g., a U-DRB of UE 102a, a U-DRB of UE 102b, and a U-DRB of UE 102c). Figure 1 In addition, Fig.10 In an instance, security functionality is not configured for each U-DRB of at least one U-DRB.

[0115] like Fig.10 As shown in the figure, the PDCP entity may include the following functionalities (also called functional modules).

[0116] Common sequence numbering function: For PDCP SDUs received from a layer higher than the PDCP layer, the common sequence numbering function may assign a COUNT value or a sequence number thereto. In an embodiment of the present application, the COUNT value or the sequence number may be continuous for the PDCP SDU sequence.

[0117] Header compression function: The header compression function is an optional function. If it is configured in the common PDCP entity, header compression can be performed on the PDCP SDU. If it is not configured in the common PDCP entity, the common PDCP entity will not perform header compression on the PDCP SDU.

[0118] PDCP header adding function: The PDCP header adding function can add a COUNT value or a sequence number to the header of the PDCP SDU. Using the header, the PDCP SDU is changed into a PDCP PDU.

[0119] Copy function: The copy function can copy the PDCP PDU into four PDCP SDUs (named PDCP PDU A, PDCP PDU B, PDCP PDU C, and PDCP PDU D), PDCP PDU A is used for M-DRB, PDCP PDU B is used for U-DRB of UE 102a, PDCP PDU C is used for U-DRB of UE 102b, and PDCP PDU D is used for U-DRB of UE 102c.

[0120] The PDCP entity may then submit PDCP PDU A to the associated RLC entity of the M-DRB, PDCP PDU B to the associated RLC entity of the U-DRB of UE 102a, PDCP PDU C to the associated RLC entity of the U-DRB of UE 102b, and PDCP PDU D to the associated RLC entity of the U-DRB of UE 102c.

[0121] Fig.11 1 is a flowchart illustrating a method of MBS according to some embodiments of the present application. The method may be performed by UE 102 (eg, Figure 1 UE102a or UE102b) shown in FIG.

[0122] exist Fig.11In the exemplary method shown in , in step 1102, UE 102 may receive configuration information including an association identification (ID) for associating a common layer entity with a first lower layer entity of an M-DRB and a second lower layer entity of a U-DRB from BS 101. In some embodiments, the association identification (ID) may also be used to associate an M-DRB and a U-DRB. For example, the association identification (ID) is used to associate a multicast RLC bearer and a unicast RLC bearer, wherein the multicast RLC bearer and the unicast RLC bearer may have the same common layer entity.

[0123] M-DRB may refer to a radio bearer or RLC bearer for data transmission via PTM mode. M-DRB is scrambled by G-RNTI in at least one cell. M-DRB may also be named MRB. U-DRB may refer to a radio bearer or RLC bearer for data transmission via PTP mode. U-DRB is scrambled by C-RNTI. U-DRB may also be named DRB. The same approach of a single radio bearer (SRB) may also be considered. For example, M-DRB may be replaced by M-SRB, which may refer to a radio bearer or RLC bearer for signaling transmission via PTM mode. U-DRB may be replaced by U-SRB, which may refer to a radio bearer or RLC bearer for signaling transmission via PTP mode.

[0124] According to some embodiments of the present application, the configuration information may include at least one of the following: information for configuring a common layer entity, information for configuring a first lower layer entity, and information for configuring a second lower layer entity.

[0125] According to some embodiments of the present application, the common layer entity may include a sequence numbering function. The sequence numbering function may include at least the following functions: sequence number allocation for each packet, packet reordering, and packet duplication.

[0126] According to some embodiments of the present application, an association identification (ID) may be received in a radio resource control (RRC) reconfiguration message.

[0127] According to some other embodiments of the present application, the common layer may include a PDCP entity, the first lower layer entity may include a first RLC entity, and the second lower layer entity may include a second RLC entity.

[0128] In an embodiment of the present application, the association identification (ID) may include one of the following: M-DRB ID, U-DRB ID, logical channel ID (LCID), temporary mobile group identifier (TMGI), G-RNTI; and any other ID used to identify the association (e.g., a new ID different from the above IDs). In this embodiment, the association identification (ID) should be unique in a cell or a multicast area including at least one cell. Therefore, if the association identification (ID) is a U-DRB ID, then the U-DRB ID may be a specific U-DRB ID used to identify the association, and is different from the U-DRB ID of UE 102. Similarly, if the association identification (ID) is an LCID, then the LCID may be a specific LCID used to identify the association, and is different from the LCID of UE 102. For example, a specific LCID index and value may be represented by the following table specified in the 3GPP standard document TS38.321:

[0129] index LCID value 30 to 35 Identification of MBS logical channels

[0130] In this embodiment, the association identification (ID) may be included in the first configuration information of the PDCP entity, the second configuration information of the first RLC entity, and the third configuration information of the second RLC entity. Specific examples of the first configuration information, the second configuration information, and the third configuration information may be referred to. Figure 3 .

[0131] In another embodiment of the present application, the association identification (ID) may include the M-DRB ID of the M-DRB and the U-DRB ID of the U-DRB. In this embodiment, BS101 may use the M-DRB ID and the U-DRB ID of UE102 as the association identification (ID).

[0132] In this embodiment, the association identification (ID) may be included in the fourth configuration information of the PDCP entity and the fifth configuration information of the first RLC entity and the second RLC entity.

[0133] In an embodiment of the present application, the fourth or fifth configuration information may include an activation indication indicating whether to use M-DRB, U-DRB or both. In another embodiment of the present application, the fourth or fifth configuration information may include a switching indication indicating switching from M-DRB to U-DRB or from U-DRB to M-DRB.

[0134] Specific examples of the fourth configuration information and the fifth configuration information can be found in Figure 4 .

[0135] According to some other embodiments of the present application, the common layer may include at least one of a PDCP entity, an RLC entity, and a MAC entity, the first lower layer entity may include a first physical (PHY) entity, and the second lower layer entity may include a second PHY entity. In an embodiment of the present application, the association identification (ID) may be an M-DRB ID or a specific LCID of an MRB. The common layer may also include at least one of a PDCP entity, an RLC entity, a MAC entity, and a higher portion of a PHY entity, and the first lower layer entity may include a first lower portion of a physical (PHY) entity, and the second lower layer entity may include a second lower portion of a PHY entity.

[0136] In an embodiment of the present application, the association identification (ID) may be included in the sixth configuration information of the radio bearer and the seventh configuration information of the cell group. Specific examples of the sixth configuration information and the seventh configuration information may refer to Figure 5 .

[0137] After receiving the configuration information, in step 1104, the UE 102 may configure at least one of the common layer entity, the first lower layer entity, and the second lower layer entity based on the configuration information.

[0138] According to some embodiments of the present application, UE 102 (e.g., UE 102a or UE 102b) may include: a common layer entity; a first lower layer entity of an M-DRB; and a second lower layer entity of a U-DRB, wherein the common layer entity is associated with the first lower layer entity and the second lower layer entity.

[0139] In an embodiment of the present application, the common layer entity may include at least one of a PDCP entity, an RLC entity, and a MAC entity. The first lower layer entity may include a first PHY entity, and the second lower layer entity may include a second PHY entity. In this embodiment of the present application, UE 102 (e.g., UE 102a or UE 102b) may include: a PDCP entity, an RLC entity, a MAC entity, a first PHY entity of an M-DRB, and a second PHY entity of a U-DRB, wherein each of the PDCP entity, the RLC entity, and the MAC entity is associated with the first RLC entity and the second RLC entity. The common layer may also include at least one of a PDCP entity, an RLC entity, a MAC entity, and a higher portion of a PHY entity, and the first lower layer entity may include a first lower portion of a PHY entity, and the second lower layer entity may include a second lower portion of a PHY entity.

[0140] Fig.12 An example of a protocol structure of a UE according to some embodiments of the present application is described.

[0141] like Fig.12As shown in , the protocol structure of UE 102 (e.g., UE 102a or UE 102b) may include a PDCP entity, an RLC entity, and a MAC layer. The PDCP entity, the RLC entity, and the MAC layer may be associated with a PHY entity of an M-DRB and a PHY entity of a U-DRB. The common layer may also include at least one of the PDCP entity, the RLC entity, the MAC entity, and the upper portion of the PHY entity, and the first lower layer entity may include a first lower portion of a physical (PHY) entity, and the second lower layer entity may include a second lower portion of the PHY entity. Fig.12 In the physical layer, the M-DRB is scrambled by the G-RNTI and the U-DRB of the UE 102 is scrambled by the C-RNTI of the UE 102.

[0142] In another embodiment of the present application, the common layer entity may include a PDCP entity, the first lower layer entity may include a first RLC entity, and the second lower layer entity may include a second RLC entity. In this embodiment, UE 102 (e.g., UE 102a or UE 102b) may include: a common PDCP entity; a first RLC entity of an M-DRB; and a second RLC entity of a U-DRB, wherein the common PDCP entity is associated with the first RLC entity and the second RLC entity.

[0143] For example, Fig.13 An example of a protocol structure of a UE according to some embodiments of the present application is described.

[0144] like Fig.13 , the protocol structure of UE 102 (e.g., UE 102a or UE 102b) may include a common PDCP entity, and the common PDCP entity may be associated with one RLC entity for an M-DRB and one RLC entity for a U-DRB of UE 102. Each of the two RLC entities may be associated with a corresponding PHY entity.

[0145] exist Fig.13 In the embodiment of the present invention, the protocol structure of UE 102 may include a MAC entity. The M-DRB has a specific LCID (e.g., LCID1) that is unique in a cell or a multicast area including at least one cell. The U-DRB may also have a corresponding LCID (e.g., LCID2). In the physical layer, the M-DRB is scrambled by the G-RNTI, and the U-DRB of UE 102 is scrambled by the C-RNTI of UE 102.

[0146] In the above embodiment, the M-DRB and U-DRB of UE 102 use a common PDCP entity. The biggest advantage of the common PDCP entity is that it provides service continuity when switching between M-DRB and U-DRB.

[0147] In order to provide lossless switching between M-DRB and U-DRB, some embodiments of the present application provide the functionality of a common PDCP entity.

[0148] In an embodiment of the present application, for a PDCP PDU received from a layer lower than the PDCP layer, the common PDCP entity may remove a COUNT value or a sequence number from the PDCP PDU to generate a PDCP SDU.

[0149] The common PDCP entity may also determine whether the PDCP PDU is received from the first RLC entity or the second RLC entity. If the PDCP PDU is received from the second RLC entity of the U-DRB and security functions are configured for each U-DRB, the common PDCP entity may perform integrity verification and / or decryption of the PDCP SDU using the COUNT value or sequence number of the UE associated with the PDCP PDU, the security algorithm and the key. If the PDCP PDU is received from the first RLC entity, the common PDCP entity may skip integrity verification and / or decryption.

[0150] Thereafter, when the header decompression function is configured in the common PDCP entity, the common PDCP entity may perform header decompression on the PDCP SDU.

[0151] For example, Fig.14 An example of a PDCP entity of a UE 102 (eg, UE 102a or UE 102b) according to some embodiments of the present application is described. Fig.13 In the example of , a common PDCP entity is used for M-DRB and U-DRB of UE 102 (e.g., UE 102a or UE 102b). Fig.14 In the example, security features are configured for U-DRB.

[0152] like Fig.14 As shown in the figure, the PDCP entity may include the following functionalities (also called functional modules).

[0153] PDCP header removal function: For a PDCP PDU received from a layer lower than the PDCP layer, the PDCP header removal function may remove a COUNT value or a sequence number from a header of a PDCP SDU to generate a PDCP SDU.

[0154] In addition, the PDCP entity may also determine whether the PDCP PDU is received from the first RLC entity or from the second RLC entity. If the PDCP PDU is received from the second RLC entity of the U-DRB, the associated PDCP SDU may be submitted to the security function. If the PDCP PDU is received from the first RLC entity, the common PDCP entity may skip integrity verification and / or decryption.

[0155] Security functions (e.g., integrity verification function and / or decryption function): For the PDCP PDU received from the second RLC entity of the U-DRB, the security function may perform integrity verification and decryption of the PDCP SDU using the COUNT value or sequence number associated with the PDCP PDU and the security algorithm and key of the UE 102. After performing the security function, the PDCP SDU may be submitted to the header decompression function if the header decompression function is configured, or to the reordering and duplicate discard function if the header decompression function is not configured.

[0156] Since the security function is not configured for the M-DRB, if the PDCP PDU is received from the first RLC entity of the M-DRB, the PDCP entity will skip the integrity protection and ciphering of the PDCP SDU. Therefore, if the header decompression function is configured, the PDCP SDU can be submitted to the header decompression function, or if the header decompression function is not configured, the PDCP SDU can be submitted to the reordering and duplicate discard function.

[0157] Header decompression function: The header compression function is an optional function. In case it is configured in the common PDCP entity, header decompression can be performed on the PDCP SDU. In case it is not configured in the common PDCP entity, the common PDCP entity will not perform header compression on the PDCP SDU. After performing header decompression, the PDCP SDU will be submitted to the reordering and duplicate discard function.

[0158] Reordering and duplicate discard function: This function can perform reordering and duplicate discard functions on the PDCP SDU and submit the PDCP SDU to a layer higher than the PDCP layer.

[0159] Fig.15 A simplified block diagram of an apparatus 1500 for multi-beam frequency hopping according to some embodiments of the present application is shown. The apparatus 1500 may be Figure 1 UE 102 (e.g., UE 102a or UE 102b) is shown in.

[0160] refer to Fig.15, the device 1500 may include at least one non-transitory computer-readable medium 1502, at least one receiving circuit system 1504, at least one transmitting circuit system 1506, and at least one processor 1508. In some embodiments of the present application, the at least one receiving circuit system 1504 and the at least one transmitting circuit system 1506 are integrated into at least one transceiver. The at least one non-transitory computer-readable medium 1502 may have computer-executable instructions stored therein. The at least one processor 1508 may be coupled to the at least one non-transitory computer-readable medium 1502, the at least one receiving circuit system 1504, and the at least one transmitting circuit system 1506. The computer-executable instructions may be programmed to implement a method using the at least one receiving circuit system 1504, the at least one transmitting circuit system 1506, and the at least one processor 1508. The method may be a method according to an embodiment of the present application, for example Figure 2 The method shown in .

[0161] Fig.16 A simplified block diagram illustrating an apparatus 1600 for multi-beam frequency hopping according to some embodiments of the present application. The apparatus 1600 may be Figure 1 BS101 shown in the video.

[0162] refer to Fig.16 , the device 1600 may include at least one non-transitory computer-readable medium 1602, at least one receiving circuit system 1604, at least one transmitting circuit system 1606, and at least one processor 1608. In some embodiments of the present application, the at least one receiving circuit system 1604 and the at least one transmitting circuit system 1606 are integrated into at least one transceiver. The at least one non-transitory computer-readable medium 1602 may have computer-executable instructions stored therein. The at least one processor 1608 may be coupled to the at least one non-transitory computer-readable medium 1602, the at least one receiving circuit system 1604, and the at least one transmitting circuit system 1606. The computer-executable instructions may be programmed to implement a method using the at least one receiving circuit system 1604, the at least one transmitting circuit system 1606, and the at least one processor 1608. The method may be a method according to an embodiment of the present application, for example Fig.11 The method shown in .

[0163] The method according to the embodiment of the present application may also be implemented on a programmed processor. However, the controller, flow chart and module may also be implemented on a general or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit (such as a discrete element circuit), a programmable logic device, etc. In general, any device on which a finite state machine capable of implementing the flow chart shown in the figure resides can be used to implement the processor function of the present application. For example, an embodiment of the present application provides a device for speech emotion recognition, including a processor and a memory. Computer programmable instructions for implementing the method of speech emotion recognition are stored in a memory, and the processor is configured to execute the computer programmable instructions to implement the method of speech emotion recognition. The method may be the method described above or other methods according to the embodiments of the present application.

[0164] Alternative embodiments preferably implement the method according to the embodiments of the present application in a non-transitory computer-readable storage medium storing computer programmable instructions. The instructions are preferably executed by a computer executable component preferably integrated with a network security system. The non-transitory computer-readable storage medium can be stored on any suitable computer-readable medium, such as RAM, ROM, flash memory, EEPROM, optical storage device (CD or DVD), hard drive, soft drive or any suitable device. The computer executable component is preferably a processor, but the instructions can be executed alternatively or additionally by any suitable dedicated hardware device. For example, an embodiment of the present application provides a non-transitory computer-readable storage medium having computer programmable instructions stored therein. The computer programmable instructions are configured to implement the method of speech emotion recognition described above or other methods according to the embodiments of the present application.

[0165] Although the present application has been described with reference to the specific embodiments of the present application, it is apparent that many substitutions, modifications and variations may be apparent to those skilled in the art. For example, the various components of the embodiments may be interchanged, added or substituted in other embodiments. Moreover, all elements of each figure are not necessary for the operation of the disclosed embodiments. For example, a person of ordinary skill in the field of the disclosed embodiments will be able to make and use the teachings of the present application by simply adopting the elements of the independent claims. Therefore, the embodiments of the present application set forth herein are intended to be illustrative rather than restrictive. Various changes may be made without departing from the spirit and scope of the present application.

Claims

1. A device for multicast and broadcast services, comprising: at least one non-transitory computer-readable medium having computer-executable instructions stored therein; at least one receiver; at least one transmitter; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver, and the at least one transmitter; Wherein the computer executable instructions are programmed to implement a method comprising: determining an association identification (ID) for associating a common layer entity with a first lower layer entity of a multicast data radio bearer (M-DRB) and a second lower layer entity of a unicast data radio bearer (U-DRB); and transmitting configuration information including the association identification (ID); wherein: the common layer entity comprises a Packet Data Convergence Protocol (PDCP) entity, the first lower layer entity comprises a first Radio Link Control (RLC) entity, and the second lower layer entity comprises a second RLC entity; and The configuration information includes a switching indication for indicating switching from the M-DRB to the U-DRB or from the U-DRB to the M-DRB.

2. The apparatus according to claim 1, wherein the M-DRB refers to a radio bearer or an RLC bearer used for data transmission via a point-to-multipoint (PTM) mode and is scrambled by a group radio network temporary identifier (G-RNTI) in at least one cell, and the U-DRB refers to a radio bearer or an RLC bearer used for data transmission via a point-to-point (PTP) mode and is scrambled by a cell radio network temporary identifier (C-RNTI). The apparatus of claim 1 , wherein the common layer entity comprises a sequence numbering function.

4. The apparatus of claim 1, wherein the associated identification (ID) comprises one of: M-DRB ID, U-DRB ID, Logical Channel ID (LCID), Temporary Mobile Group Identifier (TMGI), G-RNTI; and An ID identifying the association.

5. The apparatus of claim 1, wherein the association identification (ID) comprises an M-DRB ID of the M-DRB and a U-DRB ID of the U-DRB.

6. The apparatus of claim 1, further comprising: A COUNT value or sequence number is assigned to a PDCP service data unit (SDU).

7. A device for multicast and broadcast services, comprising: at least one non-transitory computer-readable medium having computer-executable instructions stored therein; at least one receiver; at least one transmitter; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver, and the at least one transmitter; Wherein the computer executable instructions are programmed to implement a method comprising: receiving configuration information including an association identification (ID) for associating a common layer entity with a first lower layer entity of a multicast data radio bearer (M-DRB) and a second lower layer entity of a unicast data radio bearer (U-DRB); and configuring at least one of the common layer entity, the first lower layer entity, and the second lower layer entity based on the configuration information; wherein: the common layer entity comprises a Packet Data Convergence Protocol (PDCP) entity, the first lower layer entity comprises a first Radio Link Control (RLC) entity, and the second lower layer entity comprises a second RLC entity; and The configuration information includes a switching indication for indicating switching from the M-DRB to the U-DRB or from the U-DRB to the M-DRB.

8. The apparatus of claim 7, wherein the M-DRB refers to a radio bearer or an RLC bearer used for data transmission via a point-to-multipoint (PTM) mode and is scrambled by a group radio network temporary identifier (G-RNTI) in at least one cell, and the U-DRB refers to a radio bearer or an RLC bearer used for data transmission via a point-to-point (PTP) mode and is scrambled by a cell radio network temporary identifier (C-RNTI).

9. The apparatus of claim 7, wherein the common layer entity comprises a sequence numbering function.

10. The apparatus of claim 7, wherein the association identification (ID) is received in a radio resource control (RRC) reconfiguration message.

11. A device for multicast and broadcast services, comprising: Common layer entities; a first lower layer entity of a multicast data radio bearer (M-DRB); as well as at least one second lower layer entity, wherein each of the at least one second lower layer entity is associated with a unicast data radio bearer (U-DRB) of a user equipment (UE); wherein the common layer entity is associated with the first lower layer entity and the at least one second lower layer entity of the M-DRB; wherein: the common layer entity comprises a Packet Data Convergence Protocol (PDCP) entity, the first lower layer entity comprises a first Radio Link Control (RLC) entity, and the at least one second lower layer entity comprises at least one second RLC entity; and The device is configured to transmit configuration information, which includes an association identification (ID) for associating the common layer entity with the first lower layer entity and one of the at least one second lower layer entities, and a switching indication for indicating switching from the M-DRB to the U-DRB or from the U-DRB to the M-DRB.

12. The apparatus of claim 11, wherein the PDCP entity allocates a COUNT value or a sequence number to a PDCP service data unit (SDU).

13. The apparatus of claim 12, wherein the PDCP entity copies a PDCP service data unit (SDU) into a plurality of PDCP SDUs, wherein the plurality of PDCP SDUs include a first PDCP SDU of the M-DRB and at least one second PDCP SDU of at least one U-DRB, wherein each PDCP SDU of the at least one PDCP SDU is associated with a U-DRB of a UE.

14. The apparatus of claim 13, wherein for each of the at least one second PDCP SDU, the PDCP entity uses The COUNT value or the sequence number of the UE associated with the PDCP SDU, a security algorithm and a key are used to perform integrity protection and / or encryption on the PDCP SDU to generate a secure PDCP SDU.

15. The apparatus of claim 14, wherein the PDCP entity: adding the COUNT value or the sequence number to the first PDCP SDU to generate a first PDCP protocol data unit (PDU) of the M-DRB; adding the COUNT value or the sequence number to each of at least one of the secure PDCP SDUs to generate at least one second PDCP PDU for the at least one U-DRB; submitting the first PDCP PDU to the first RLC entity; as well as Each of the at least one second PDCP PDU is submitted to a corresponding one of the at least one second RLC entity.

16. The apparatus of claim 13, wherein the PDCP entity performs header compression on each of the plurality of PDCP SDUs.

Images