Logical channel arrangement method, apparatus, and device

Abstract

To provide a logical channel configuration method, an apparatus, and a device.SOLUTION: A method includes allowing a UE to obtain at least one logical channel configuration information corresponding to a first TMGI. One logical channel configuration information specifies either one of a PTM LCID and / or PTM RLC bearer arrangements, which is a first configuration or a PTP LCID and / or PTP RLC bearer arrangements, which is a second configuration.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] (Cross - reference to related applications) This application claims the priority of Chinese Patent Application No. 202110057653.3 filed in China on January 15, 2021, and all the contents of the said application are incorporated herein by reference.

[0002] This application belongs to the field of communication technology, and specifically relates to a logical channel allocation method, device and equipment.

Background Art

[0003] In long-term evolution (LTE) broadcast multicast transmission, it supports the transmission of multimedia broadcast multicast services (MBMS) using the multicast / broadcast single frequency network (MBSN) method and multicast services using the single cell point to multipoint (SC-PTM) method. In contrast to the MBSFN scheme, multicast services have transmission channels and transmission time domain locations completely independent of unicast, eliminating the need to consider the problem of logical channel overlap. In contrast to the SC-PTM scheme, in LTE, multicast services are assigned only one special logical channel identifier (LCID). This LCID can distinguish between single-cell multicast control channels (SC-MCCH) and single-cell multicast traffic channels (SC-MTCH), thereby differentiating unicast services. Multiple SC-MCCHs and SC-MTCHs can be further distinguished by group radio network temporary identifiers (G-RNTIs).

[0004] However, multicast transmission in new radio (NR) is more complex than multicast transmission in LTE. In NR, a single temporary mobile group identifier (TMGI) service may support multiple logical channels, and a multicast radio bearer (MRB) in a single TMGI may simultaneously deploy PTM legs and point-to-point (PTP) legs. A rational arrangement of PTM and PTP legs ensures coordinated scheduling of multicast and unicast services in NR, thereby guaranteeing the normal operation of multicast services. Therefore, how to properly schedule multicast services in NR is an urgent issue that needs to be resolved. [Overview of the Initiative] [Problems that the invention aims to solve]

[0005] The embodiments of this application provide a logical channel arrangement method, apparatus, and device that can solve the problem of how multicast services can be successfully scheduled in NR. [Means for solving the problem]

[0006] To solve the above technical problems, this application is implemented as follows.

[0007] According to a first embodiment, a logical channel placement method is provided, which includes user equipment (UE) obtaining at least one logical channel placement information corresponding to a first TMGI, wherein the one logical channel placement information indicates either a first placement which indicates a PTM LCID and / or PTM radio link control (RLC) bearer placement, or a second placement which indicates a PTP LCID and / or PTP RLC bearer placement.

[0008] According to a second embodiment, a logical channel placement method is provided, the method comprising a network-side device transmitting at least one logical channel placement information corresponding to a first TMGI to the UE, wherein the one logical channel placement information indicates either a first placement, which is a PTM LCID and / or PTM RLC bearer placement, or a second placement, which is a PTP LCID and / or PTP RLC bearer placement.

[0009] According to a third embodiment, a logical channel placement device is provided, which includes an acquisition module used to acquire at least one logical channel placement information corresponding to a first TMGI, wherein the one logical channel placement information indicates either a first placement, which is a PTM LCID and / or PTM RLC bearer placement, or a second placement, which is a PTP LCID and / or PTP RLC bearer placement.

[0010] According to a fourth aspect, a logical channel placement device is provided, the device including a transmitting module used to transmit at least one logical channel placement information corresponding to a first TMGI to a UE, wherein the one logical channel placement information indicates either a first placement, which is a PTM LCID and / or PTM RLC bearer placement, or a second placement, which is a PTP LCID and / or PTP RLC bearer placement.

[0011] According to a fifth aspect, a UE is provided, which includes a processor, memory, and a program or instruction stored in the memory and executable on the processor, wherein when the program or instruction is executed by the processor, the steps of the method according to the first aspect are realized.

[0012] According to the sixth aspect, a network-side device is provided, which includes a processor, memory, and a program or instruction stored in the memory and executable on the processor, wherein when the program or instruction is executed by the processor, the steps of the method according to the second aspect are realized.

[0013] According to the seventh aspect, a readable storage medium is provided on which a program or instruction is stored, and when the program or instruction is executed by a processor, a step of the method according to the first aspect is realized, or a step of the method according to the second aspect is realized.

[0014] According to the eighth aspect, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled with the processor, the processor executing programs or instructions for network-side equipment, and being used to implement the method according to the first aspect or the method according to the second aspect. [Effects of the Invention]

[0015] In the embodiments of this application, the UE acquires at least one logical channel placement information corresponding to a first TMGI, where the logical channel placement information indicates either a first placement, which is a PTM LCID and / or PTM RLC bearer placement, or a second placement, which is a PTP LCID and / or PTP RLC bearer placement. This scheme allows the UE to acquire the logical channel placement information of a TMGI, so that when the UE is interested in a TMGI, it can acquire the logical channel placement information of that TMGI, for example, a first placement (PTM LCID and / or PTM RLC bearer placement) and / or a second placement (PTP LCID and / or PTP RLC bearer placement). In this way, the UE can receive TMGI services based on this logical channel placement information, thereby improving the cooperative transmission efficiency of the UE's multicast and unicast services, and further improving the transmission efficiency of the UE's multicast services while ensuring system efficiency. [Brief explanation of the drawing]

[0016] [Figure 1] This is a block diagram of a wireless communication system according to an embodiment of the present application. [Figure 2] This is one flowchart of the logical channel arrangement method according to an embodiment of this application. [Figure 3] This is the second flowchart of the logical channel arrangement method according to the embodiment of this application. [Figure 4] This is a schematic diagram of the protocol stack architecture of the UE according to an embodiment of this application. [Figure 5] This is one of the schematic diagrams of the structure of a logic channel placement device according to an embodiment of this application. [Figure 6] This is the second schematic diagram of the structure of a logic channel placement device according to an embodiment of this application. [Figure 7] This is a schematic diagram of the hardware of a communication device according to an embodiment of this application. [Figure 8] This is a schematic diagram of the UE hardware according to an embodiment of this application. [Figure 9] This is a schematic hardware diagram of a network-side device according to an embodiment of the present application.

Embodiments for Carrying out the Invention

[0017] The following clearly and completely describes the technical solutions in the embodiments of the present application while combining the drawings in the embodiments of the present application. Obviously, the described embodiments are some of the embodiments of the present application, not all of them. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the protection scope of the present application.

[0018] Terms such as "first" and "second" in the specification and claims of the present application are used to distinguish similar objects and are not for describing a specific order or sequence. It should be understood that the data used in this way can be exchanged when appropriate, so that the embodiments of the present application can be implemented in an order other than that illustrated or described herein, and the objects distinguished by "first" and "second" generally belong to the same type, without limiting the number of objects. For example, the first object may be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the related objects before and after are in an "or" relationship.

[0019] It should be noted that the technologies described in the embodiments of this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but are also applicable to other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of this application are always used interchangeably, and the technologies described may be applied to the systems and radio technologies mentioned above, or to other systems and radio technologies. However, while the following description uses New Radio (NR) systems for illustrative purposes and largely employs NR terminology, these technologies may also be applied to applications other than NR systems, such as 6th Generation (6G) communication systems.

[0020] FIG. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a UE 11 and a network-side device 12. Here, the UE 11 may also be referred to as a terminal device or a terminal. The UE 11 may be a terminal-side device such as a mobile phone, a tablet personal computer, a laptop computer (or called a notebook computer), a personal digital assistant (PDA), a palm-top computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), a wearable device, or an in-vehicle device (VUE), a pedestrian terminal (PUE), etc. The wearable device includes a bracelet, earphones, glasses, etc. It should be noted that in the embodiments of the present application, the specific type of the UE 11 is not limited. The network-side device 12 may be a base station or a core network. Here, the base station may be called a Node B, an evolved Node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (TRP), or other appropriate terms in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0021] In the embodiments of this application, for a multicast service (e.g., a TMGI service), the network-side equipment may deploy two legs for transmission for the UE, the two legs including a PTP leg and a PTM leg.

[0022] Here, a PTM leg refers to the scrambling of the physical downlink control channel (PDCCH) by network-side equipment using a common RNTI (e.g., G-RNTI). All UEs in the group jointly monitor the G-RNTI scheduling and receive subsequent scheduling data. Data transmitted in a single PTM leg may be received by multiple UEs; in other words, PTM transmits data to multiple UEs simultaneously, resulting in relatively high transmission efficiency. However, because PTM needs to comprehensively consider coverage for all UEs, its transmission parameters must be applied to all UEs, for example, by using an omnidirectional antenna to account for UEs with relatively poor link quality. Therefore, the effectiveness of PTM may be relatively poor for some UEs with relatively poor link quality.

[0023] A PTP leg is a method where network-side equipment scrambles the PDCCH using a dedicated cell-radio network temporary identifier (C-RNTI) for the UE (User Entrance). Only this UE can monitor the scheduling of this C-RNTI and receive subsequent scheduling data. Data transmitted in a single PTP leg is received by only one UE; in other words, the PTP leg is a dedicated transmission leg for one UE. Therefore, network-side equipment can adjust transmission parameters based on the link quality of this UE, for example, by using a directional or forming antenna to set appropriate transmission parameters based on the link quality of this UE. As a result, the transmission efficiency for a single UE is relatively good. However, when it is necessary to transmit data to multiple UEs, multiple transmission resources are required, which results in relatively low transmission efficiency.

[0024] In the following sections, the logic channel arrangement method according to the embodiment of this application will be described in detail with reference to drawings, specific examples, and their application scenarios.

[0025] As shown in Figure 2, embodiments of the present application provide a logical channel placement method, which is performed by a UE, and which may include the following step 201.

[0026] Step 201, the UE obtains at least one logical channel placement information corresponding to the first TMGI.

[0027] Here, one of the logical channel placement information pieces mentioned above is: The first configuration is a PTM LCID and / or PTM RLC bearer configuration, A second configuration may specify either a PTP LCID configuration or a PTP RLC bearer configuration.

[0028] It should be explained that, in the embodiments of this application, the single logical channel placement information refers to any one of the at least one logical channel placement information. Here, if there are multiple instances of this at least one logical channel placement information, the logical channel placement information among these at least one logical channel placement information may be the same or different, and may be determined specifically according to the actual usage needs, and is not limited to the embodiments of this application.

[0029] In the embodiments of this application, the UE can obtain at least one logical channel placement information corresponding to the first TMGI, and based on this at least one logical channel placement information, the UE can receive the first TMGI service, thereby ensuring the transmission efficiency of the UE's multicast service.

[0030] In the embodiments of this application, the first TMGI described above may be a TMGI of interest to the UE, for example, a TMGI from which the UE intends to receive data.

[0031] Selectively, in the embodiments of this application, the first TMGI may include N MRBs, one of which corresponds to one or two of the at least one logical channel placement information, where N is a positive integer.

[0032] Here, one of the two logical channel placement pieces described above may indicate the first placement (PTM LCID and / or PTM RLC bearer placement), and the other logical channel placement piece may indicate the second placement (PTP LCID and / or PTP RLC bearer placement).

[0033] In the embodiments of this application, one logical channel placement information may include TMGI information and MRB information corresponding to this logical channel, thereby enabling the UE to determine the MRB corresponding to each of the at least one logical channel placement information.

[0034] Selectively, in the embodiments of this application, N may be any possible numerical value such as 2, 4, 8, or 16, and may be specifically determined according to the actual use needs, and is not limited to the embodiments of this application.

[0035] It should be explained that when one MRB corresponds to two of the at least one logical channel placement information, the number of these at least one logical channel placement information is multiple.

[0036] Furthermore, when one MRB corresponds to the two logical channel placement information described above, there are PTM legs and PTP legs corresponding to this MRB.

[0037] In the embodiments of this application, any one of the above-mentioned logical channel placement information can be realized in any of the following four cases (Case 1, Case 2, Case 3, and Case 4, respectively), and below, the logical channel placement information according to the embodiments of this application will be explained illustratively using one logical channel placement information as an example.

[0038] The implementation method for the other logical channel placement information among the above-mentioned at least one logical channel placement information is similar to the implementation method for the first logical channel placement information described below, and in order to avoid repetition of the explanation, it will not be explained further in the embodiments of this application.

[0039] Case 1: When one logical channel placement information indicates the LCID of a PTM, this LCID of the PTM may be any LCID within the interval that takes a predefined value for the PTM's LCID.

[0040] For Case 1 above, the interval over which the PTM's LCID values ​​can be taken may be defined in advance (i.e., specified by the standard / protocol), in which case the UE may determine that the PTM's LCIDs are all LCIDs within the interval over which the PTM's LCID values ​​can be taken, based on the predefined interval over which the PTM's LCID values ​​can be taken.

[0041] Selectively, in embodiments of this application, it may be predefined that a single TMGI service has a maximum of M MRBs, where M is a positive integer (e.g., any possible number such as 2, 4, 8, 16), and the LCID of the PTM corresponding to these M MRBs may be predefined, for example, [35, 35 + M - 1] or [46 - M + 1, 46], where the value of the LCID of the single PTM may be any number in [46 - M + 1, 46].

[0042] To make it clear, in Case 1 above, the interval over which the LCID value of PTM is taken is the same for different TMGIs, and the distinction between different TMGIs may be made by G-RNTI.

[0043] In the case described in Case 1 above, the UE may establish M sets of protocol stack entities for a first TMGI service (a service of interest to the UE), each set including at least a radio link control (RLC) entity and a packet data convergence protocol (PDCP) entity. When the UE receives a G-RNTI scheduling corresponding to the first TMGI, the UE may determine, based on the G-RNTI, that this is the first TMGI, and then, based on the LCID carried in the medium access control (MAC) protocol data unit (PDU) subheader of the G-RNTI scheduling, determine the corresponding RLC and PDCP entities from the M sets of protocol stack entities, perform service reception processing, and pass it on to the upper layer.

[0044] In the embodiments of this application, since the LCID of the PTM is predefined for Case 1, the network-side equipment does not need to assign additional signaling to the LCID of the PTM, thereby saving signaling overhead on the network-side equipment.

[0045] Case 2: When one logical channel placement information indicates the LCID of a PTM, this LCID of the PTM may be the number of LCIDs specified by the network-side device within the interval in which the LCID of the PTM takes a predefined value.

[0046] Here, the number of targets may be indicated by a first signaling, which may be a first common signaling or a first dedicated radio resource control (RRC) signaling.

[0047] In Case 2 above, the network-side device may, by the first signaling described above, instruct the UE on the number of LCIDs of the PTM for one logical channel corresponding to one MBR, thereby enabling the UE to determine the LCID of the PTM from a predefined range of PTM LCID values.

[0048] Selectively, in the embodiments of this application, the UE may determine the LCID of the PTM from an interval in which the LCID of the PTM is taken from a predetermined value, based on the number of targets, by taking a predetermined LCID value of the PTM.

[0049] The method for selectively taking the LCID value of the predefined PTM described above may involve taking the value from the beginning to the end of the interval for taking the LCID value of the predefined PTM, or taking the value from the end to the beginning of the interval for taking the LCID value of the predefined PTM. Specifically, this may be determined according to the actual usage needs and is not limited to the embodiments of this application.

[0050] For example, if the interval for taking the LCID value of the predefined PTM is [35, 46] and the number of targets is 2, then the method for taking the LCID value of the predefined PTM is to take the value from front to back within the predefined interval for taking the LCID value of the PTM, in which case the LCID of the PTM may be 35 and 36. Alternatively, the method for taking the LCID value of the predefined PTM is to take the value from back to front within the predefined interval for taking the LCID value of the PTM, in which case the LCID of the PTM may be 45 and 46. In this way, when the UE receives the MRB 1, it may establish two sets of receiving protocol stacks, that is, the receiving entities established by the UE include at least two sets of RLC+PDCP receiving entities, and in the G-RNTI scheduling, the UE may send the data for which it received LCID=35 to the first set of RLC+PDCP receiving entities for processing, and send the data for which it received LCID=36 to the second set of RLC+PDCP receiving entities for processing.

[0051] Selectively, in the embodiments of this application, the first common signaling may be in the form of a system information block (SIB) or a multicast control channel (MCCH), so that all interested UEs can receive this first common signaling and thereby receive the target number, and furthermore, the UEs can obtain one logical channel placement information.

[0052] In the embodiments of this application, after the UE enters a connected state, the network-side equipment may transmit the number of targets to the UE via a first dedicated RRC signaling, thereby enabling the UE to obtain one piece of logical channel placement information. If multiple UEs need to obtain this one piece of logical channel placement information from this first dedicated RRC signaling, the network-side equipment may transmit this first dedicated signaling once to each of these multiple UEs.

[0053] Case 3: When one logical channel placement information indicates the LCID of a PTM, this LCID of the PTM may be the LCID indicated by a second signaling by a network-side device.

[0054] Here, the second signaling may be a second common signaling or a second dedicated RRC signaling.

[0055] In the case of case 3 described above, the network-side device may directly instruct the UE on the PTM's LCID through the second signaling described above, and for example, this second signaling may include the PTM's LCID.

[0056] Selectively, in the embodiments of this application, the second common signaling may be in the form of an SIB or an MCCH, thereby allowing the network-side equipment to transmit the LCID of the PTM to the second common signaling via the second common signaling so that the UE can obtain one logical channel placement information.

[0057] In the embodiments of this application, after the UE enters a connected state, the network-side equipment may have the PTM's LCID carried to a second dedicated RRC signaling and transmitted to the UE, thereby enabling the UE to obtain one logical channel placement information.

[0058] For example, in the embodiments of this application, if the LCIDs of the PTMs corresponding to MRB 2 are 37 and 38, the network-side device may have the LCIDs of the PTMs 37 and 38 carried to the second signaling and transmitted to the UE, thereby enabling the UE to obtain logical channel placement information corresponding to MRB 2.

[0059] Selectively, in the embodiments of this application, for cases 1, 2, and 3, the network-side device may transmit entity placement information to the UE using a single receiving entity placement information (for example, the first receiving entity placement information in the embodiments of this application), thereby enabling the UE to establish the corresponding data receiving entity based on this receiving entity placement information and the single logical channel placement information.

[0060] In the embodiments of this application, the logical channel arrangement method according to the embodiments of this application may further include steps 202 and 203 below for cases 1, 2 and 3 described above.

[0061] Step 202, the network-side device transmits the first receiving entity placement information to the UE.

[0062] Step 203, the UE receives the first receiving entity placement information transmitted by the network-side device.

[0063] Here, the first receiving entity placement information described above may include at least one of the following: PTM RLC bearer placement (which may also be called PTM RLC parameters) and PDCP placement (which may also be called PDCP parameters).

[0064] In the embodiments of this application, the network-side device may transmit the first receiving entity placement information to the UE, and after the UE receives this first receiving entity placement information, the UE may establish the corresponding data receiving entity based on this first receiving entity placement information and the one logical channel placement information. In this way, when the corresponding data is received, it can be transmitted to this data receiving entity.

[0065] It should be explained that, in the embodiments of this application, if the one logical channel placement information includes a PTM RLC bearer placement, the first receiving entity placement information does not need to include a PTM RLC bearer placement.

[0066] Selectively, in the embodiments of this application, the PTM RLC bearer configuration may include a PTM RLC mode (e.g., unacknowledged mode (UM)), a PTM RLC sequence number (SN), and a timer length, and the PDCP configuration may include a PDCP SN and a timer length.

[0067] Of course, in actual implementation, the PTM RLC bearer configuration and PDCP configuration may further include any other possible configurations (parameters), which may be determined specifically according to the actual usage requirements, and are not limited to the embodiments of this application.

[0068] Case 4: When one logical channel placement information indicates a PTP LCID, this PTP LCID may also be one that the network-side equipment has indicated by a third dedicated RRC signaling.

[0069] In the case of Case 4 described above, the network-side equipment may instruct the UE to provide the PTP LCID via the third dedicated RRC signaling described above.

[0070] In the embodiments of this application, the third signaling may include (or carry) information about the PTP's LCID, TMGI, and MRB (e.g., MRB ID), thereby instructing the UE to provide the PTP's LCID corresponding to the MRB.

[0071] Selectively, in the embodiments of this application, if one MRB corresponds to two logical channel placement information, the LCID of the PTP is the same as the LCID of the PTM when the third dedicated RRC signaling does not include the LCID of the PTP.

[0072] To make it clearer, the LCID of the PTP may be such that one of the two logical channel placement pieces indicates the LCID of the PTM, and the other logical channel placement piece indicates the LCID of the PTP. Thus, if the PTP's LCID is not included in this third dedicated RRC signaling (for example, only the TMGI and MRB ID are included), the UE can determine the PTP's LCID by associating the TMGI and MRB ID with the PTM's LCID.

[0073] In other words, network-side equipment may implicitly instruct the UE that the PTP LCID is the same as the PTM LCID, without having the PTP LCID carried by a third dedicated RRC signaling.

[0074] Selectively, in embodiments of the present application, if one MRB corresponds to two logical channel placement information, and if the LCID of the PTP is equal to the LCID of the PTM, the network-side device may directly indicate the LCID of the PTP by a third dedicated RRC signaling, or implicitly indicate that the LCID of the PTP is the same as the LCID of the PTM, and if the LCID of the PTP is not equal to the LCID of the PTM, the network-side device may indicate the LCID of the PTP by a third dedicated RRC signaling.

[0075] Selectively, in the embodiments of this application, for case 4, the network-side device may transmit entity placement information to the UE using one receiving entity placement information (for example, the second receiving entity placement information in the embodiments of this application), thereby enabling the UE to establish the corresponding data receiving entity based on this receiving entity placement information and the one logical channel placement information.

[0076] In the embodiments of this application, for case 4 above, the logical channel placement information according to the embodiments of this application may further include steps 204 and 205 below.

[0077] Step 204, the network-side device sends the second incoming entity placement information to the UE.

[0078] Step 205, the UE receives the second incoming entity placement information transmitted by the network-side device.

[0079] Here, the second receiving entity placement information may include at least one of the following: a PTP RLC bearer placement and a PDCP placement.

[0080] In the embodiments of this application, the network-side device may transmit the second receiving entity placement information to the UE, and after the UE receives this second receiving entity placement information, the UE can establish the corresponding data receiving entity based on this second receiving entity placement information and the one logical channel placement information. In this way, when the corresponding data is received, it can be transmitted to this data receiving entity.

[0081] It should be explained that, in the embodiments of this application, if the one logical channel placement information includes a PTP RLC bearer placement, the first receiving entity placement information does not need to include a PTP RLC bearer placement.

[0082] Selectively, in the embodiments of this application, the PTP RLC bearer configuration may include a PTP RLC mode, a PTP RLC SN, and a timer length, and the PDCP configuration may include a PDCP SN and a timer length.

[0083] Of course, in actual implementation, the PTP RLC bearer configuration and PDCP configuration may further include any other possible configurations (parameters), which may be determined specifically according to the actual usage requirements, and are not limited to the embodiments of this application.

[0084] In the embodiments of this application, since the UE can obtain logical channel placement information of a TMGI, when the UE is interested in a TMGI, the UE can obtain the logical channel placement information of that TMGI, for example, a first placement (PTM LCID and / or PTM RLC bearer placement) and / or a second placement (PTP LCID and / or PTP RLC bearer placement). In this way, the UE can receive TMGI services based on this logical channel placement information, thereby improving the cooperative transmission efficiency of the UE's multicast and unicast services, and further improving the transmission efficiency of the UE's multicast services while ensuring system efficiency.

[0085] Because there are many selective ways in which multicast services use LCIDs, the conventional 64 LCIDs may not be able to meet the usage demands of multicast services. Therefore, network-side equipment may allocate the appropriate LCIDs for the UE based on capability information regarding whether the UE supports extended LCIDs. Based on this, the logical channel allocation method according to the embodiment of this application may further include steps 206 and 207 below.

[0086] Step 206: After the UE enters a connected state, the UE sends logical channel expansion capability information to the network-side equipment.

[0087] Step 207, the network-side equipment receives the logical channel expansion capability information transmitted by the UE.

[0088] Here, the above logical channel expansion capability information is Whether the UE supports extended LCID (eLCID), The UE supports the first bit-number extended LCID, This may be used to indicate that the UE supports a second-bit extended LCD, or at least one of the following.

[0089] In the embodiments of this application, after the UE enters a connected state, the UE may transmit the logical channel expansion capability information to the network-side equipment, and after the network-side equipment receives this logical channel expansion capability information, the network-side equipment can then place logical channels (e.g., LCIDs for PTM and / or LCIDs for PTP) in the UE based on the UE's logical channel expansion capability.

[0090] Selectively, in the embodiments of this application, the first number of bits may be smaller than the second number of bits. For example, the first number of bits may be 1 bit, and the second number of bits may be 2 bits.

[0091] Selectively, in the embodiments of this application, if the UE does not support extended LCD, the UE does not have to transmit the logical channel extension capability information to the network-side device, that is, if the UE does not support extended LCD, it does not have to perform steps 206 and 207, thus saving resource overhead.

[0092] Selectively, in embodiments of this application, if a network-side device does not receive enhanced LCD capability information reported by the UE within a predetermined time window, the network-side device determines that the UE does not support enhanced LCD.

[0093] Selectively, in the embodiments of this application, the LCID of the PTM and the LCID of the PTP may be in different intervals depending on whether the UE supports extended LCID.

[0094] Case I: When the UE supports extended LCID, the PTM's LCID is within the range of either the unextended LCID or the extended LCID, and the PTP's LCID is within the range of either the unextended LCID or the extended LCID.

[0095] Case of type two: When the UE does not support extended LCID, the PTM's LCID is within the range of either unextended LCID or extended LCID, and the PTP's LCID is within the range of unextended LCID.

[0096] It should be explained that, in the embodiments of this application, if the UE does not support extended LCID, and the LCID of the PTM falls within the extended LCID range, even if the UE parses the LCID of this PTM from some data, the LCID of this PTM is an LCID domain that the UE does not recognize, and the UE is unable to process this data and may therefore discard it.

[0097] Selectively, in the embodiments of this application, the transmission of the logical channel expansion capability information by the UE to the network-side equipment may be predefined or instructed by the network-side equipment. Specifically, this may be determined according to the actual usage requirements and is not limited to the embodiments of this application.

[0098] In embodiments of this application, if it is predefined that the UE transmits the logical channel expansion capability information to network-side equipment, and the UE is interested in multicast services (e.g., the first TMGI) received after the UE enters a connected state, the UE reports the logical channel expansion capability information to the network-side equipment after it has been securely activated, thereby facilitating the network-side equipment to quickly determine the PTM and / or PTP configuration of this multicast service.

[0099] If the network-side equipment instructs the UE to selectively transmit the logical channel expansion capability information, the logical channel arrangement method according to the embodiment of this application may further include steps 208 and 209 below, prior to step 206.

[0100] Step 208, the network-side equipment sends a third signal to the UE.

[0101] Step 209, the UE receives a third signaling signal transmitted by the network-side equipment.

[0102] Here, the third signaling described above may be used to instruct the UE to report the capabilities information of the extended LCID.

[0103] In the embodiments of this application, before the UE transmits the logical channel extension capability information to the network-side device, the network-side device may instruct the UE to report the extended LCID capability information by transmitting the third signaling to the UE.

[0104] Selectively, in the embodiments of this application, the third signaling may be a common signaling or a dedicated RRC signaling. Specifically, it may be determined according to the actual usage needs and is not limited to the embodiments of this application.

[0105] In embodiments of this application, if the third signaling is a common signaling, the network-side equipment may instruct the third signaling along with a signaling that notifies the UE that it needs to enter a connected state in order to receive multicast services (e.g., the first TMGI), and if the third signaling is a dedicated RRC signaling, after the UE has reported the TMGI of interest, the network-side equipment may instruct the UE to report the capabilities information of the extended LCID via the dedicated RRC signaling.

[0106] Selectively, in embodiments of the present application, after step 201 (where the UE obtains the above-mentioned at least one logical channel placement information), the logical channel placement method according to embodiments of the present application may further include the following steps 210 to 213, or steps 210 to 212 and step 214.

[0107] Step 210, the UE establishes the first TMGI data receiving entity based on the above at least one logical channel placement information.

[0108] In the embodiments of this application, after the UE obtains at least one logical channel placement information corresponding to the first TMGI, the UE may establish a data receiving entity for the first TMGI based on this at least one logical channel placement information.

[0109] In the embodiments of this application, one MRB of the first TMGI corresponds to one PDCP entity, and when the logical channel placement information corresponding to the MRB indicates the LCID of the PTM, this LCID of the PTM corresponds to one PTM RLC entity, and when the logical channel placement information corresponding to the MRB indicates the LCID of the PTP, this LCID of the PTP corresponds to one PTP RLC entity.

[0110] In embodiments of this application, when one MRB corresponds to two logical channel placement pieces, the UE may establish two legs to be split for this MRB, such that the LCID of the PTM corresponds to this MRB (for example, the PTM leg LCID is bound to the MRB ID) and the LCID of the PTP also corresponds to this MRB (for example, the PTP leg LCID is bound to the MRB ID), and the data of these two legs may be transmitted to a common PDCP entity corresponding to the MRB.

[0111] Step 211, the UE receives the target scheduling data.

[0112] Step 212, the UE determines the LCID in the target scheduling data.

[0113] In embodiments of this application, the UE may receive G-RNTI scheduling data, parse the PTM LCID from the MAC PDU subheader, and transmit this scheduling data to the corresponding data receiving entity; or the UE may receive C-RNTI scheduling data, parse the LCID from the MAC PDU subheader, determine whether this LCID is a unicast service LCID or a PTP LCID, and transmit this scheduling data to the corresponding data receiving entity.

[0114] In the embodiments of this application, after the UE receives the target scheduling data, the UE can determine the LCID in the target scheduling data and thereby perform different operations on the target scheduling data.

[0115] Step 213, if the target scheduling data is scheduling data monitored by the G-RNTI corresponding to the first TMGI, or if the target scheduling data is scheduling data monitored by the C-RNTI of the UE and the LCID in the target scheduling data is the LCID indicated by the logical channel placement information, the UE sends the target scheduling data to the data receiving entity of the first TMGI for processing.

[0116] In the embodiments of this application, when the target scheduling data is scheduling data monitored by a G-RNTI corresponding to a first TMGI, the UE can determine the RLC entity and PDCP entity of the corresponding PTM based on the LCID in the target scheduling data, and thereby transmit the target scheduling data to the RLC entity and PDCP entity of this PTM in the first TMGI for processing (e.g., sorting, repetition detection, etc.).

[0117] Accordingly, if the target scheduling data is scheduling data monitored by the UE's C-RNTI, and the LCID in the target scheduling data is the LCID indicated by the logical channel placement information, the UE can determine the corresponding PTP RLC entity and PDCP entity based on the LCID in the target scheduling data, and thereby send the target scheduling data to these PTP RLC entity and PDCP entity in the first TMGI for processing (e.g., sorting, repetition detection, etc.).

[0118] Step 214: If the LCID in the target scheduling data does not belong to an LCID supported by the UE, the UE discards the target scheduling data.

[0119] In embodiments of this application, after the UE receives the target scheduling data, if the target scheduling data does not belong to an LCID supported by the UE, for example, if the UE does not support extended LCIDs, but the LCID in the target scheduling data is an LCID in an extended LCID interval, the UE can determine that the LCID in the target scheduling data does not belong to an LCID supported by the UE, that is, the LCID in the target scheduling data is in an LCID domain that the UE is not aware of, and in that case the UE may discard the target scheduling data, that is, ignore the target scheduling data.

[0120] As shown in Figure 3, an embodiment of the present application provides a logical channel arrangement method, which is performed by network-side equipment, and which may include the following step 301.

[0121] Step 301, the network-side device transmits at least one logical channel placement information corresponding to the first TMGI to the UE.

[0122] Here, one of the logical channel placement information pieces mentioned above is: The first configuration is a PTM LCID and / or PTM RLC bearer configuration, A second configuration may specify either a PTP LCID configuration or a PTP RLC bearer configuration.

[0123] In the embodiments of this application, the network-side equipment may transmit at least one logical channel placement information corresponding to the first TMGI to the UE, so that after the UE receives this at least one logical channel placement information, the UE can establish a corresponding data receiving entity based on this at least one logical channel placement information, thereby ensuring the normal transmission of the TMGI service.

[0124] Selectively, in the embodiments of this application, the first TMGI includes N MRBs, where each MRB corresponds to one or two logical channel placements from the at least one logical channel placement information, and N is a positive integer.

[0125] Here, one of the two logical channel placement pieces indicates the first placement, and the other logical channel placement piece indicates the second placement.

[0126] Selectively, in the embodiments of this application, when one logical channel placement information indicates the LCID of the PTM, the LCID of the PTM may be a number of LCIDs specified by the network-side device within an interval in which it takes a predetermined value for the PTM's LCID.

[0127] Here, the number of targets may be indicated by a first signaling, which may be a first common signaling or a first dedicated RRC signaling.

[0128] Selectively, in the embodiments of this application, when one logical channel placement information indicates the LCID of the PTM, the LCID of the PTM may be the LCID indicated by the network-side device through a second signaling.

[0129] Here, the second signaling may be a second common signaling or a second dedicated RRC signaling.

[0130] Selectively, in the embodiments of this application, when one logical channel placement information indicates the LCID of the PTP, the LCID of the PTP may be one that the network-side equipment has indicated by a third dedicated RRC signaling.

[0131] Selectively, in the embodiments of this application, if one MRB corresponds to two logical channel placement information, the LCID of the PTP is the same as the LCID of the PTM, when the third dedicated RRC signaling does not include the LCID of the PTP.

[0132] In the embodiments of this application, the network-side equipment can transmit TMGI logical channel placement information to the UE. When the UE reports that it is interested in a particular TMGI, the network-side equipment can transmit the logical channel placement information of that TMGI, for example, a first placement (PTM LCID and / or PTM RLC bearer placement) and / or a second placement (PTP LCID and / or PTP RLC bearer placement), to the UE. In this way, the UE can receive TMGI services based on this logical channel placement information, thereby improving the cooperative transmission efficiency of multicast and unicast services, and further improving the transmission efficiency of multicast services while ensuring system efficiency.

[0133] The following section provides a illustrative explanation of the logic channel arrangement method according to the embodiment of this application, along with specific examples.

[0134] Example 1: Method for arranging PTM As shown in Figure 4, this is a schematic diagram of the protocol stack architecture of a UE according to an embodiment of the present application, in which only one dedicated radio bearer (DRB) and one MRB are included, and the relationship of the protocol stack between them is shown. In practice, a UE may have multiple unicast DRBs, multiple MRBs corresponding to one TMGI / G-RNTI, and consequently, each TMGI / G-RNTI may have multiple TMGI / G-RNTIs corresponding to one or more MRBs.

[0135] In this MRB, all network-side devices may be configured with PTP legs, all with PTM legs, some with PTP legs and some with PTM legs, and some with both PTP and PTM legs and some with either PTP or PTM legs. The specific configuration may be determined according to the actual usage requirements and is not limited to the embodiments of this application.

[0136] The following section provides an illustrative explanation of how to position the LCID on the PTM leg of the MRB, that is, how to position the LCID of the PTM corresponding to the MRB.

[0137] Type 1 method: A method in which the LCID of the PTM leg is specified in the standard (i.e., the LCID of the PTM leg is predefined), as follows:

[0138] The standard specifies that each TMGI can have a maximum of M MRBs, and the value of M may be 2, 4, 8, 16, or any other possible value. The LCID values ​​corresponding to these M MRBs are entered into the standardized "Values ​​of LCID for DL-SCH" table, and for example, the current NR has the reserved LCID values ​​shown in Table 1.

[0139] [Table 1]

[0140] The specification may stipulate that the interval for the LCID value is [35, 35 + M - 1] or [46 - M + 1, 46], and this is the LCID value of the PTM corresponding to one MRB of one TMGI service. At the same time, there is a one-to-one correspondence between the MRB and the logical channel (LCH), that is, the MRB may be the radio bearer (RB) ID value that takes values in this interval.

[0141] For the UE to receive scheduling data, the UE may establish M sets of protocol stack entities (i.e., data reception entities) for each TMGI service it is interested in. Each set of protocol stack entities includes at least a PTM RLC entity and a PDCP entity. When the UE receives the scheduling of one G-RNTI, the UE determines which TMGI service it is based on the G-RNTI, and then determines the corresponding PTM RLC entity and PDCP entity based on the LCID value carried in the MAC PDU subheader of the G-RNTI scheduling, performs service reception processing, and may pass it to the upper layer.

[0142] In the first method, the intervals for the values of the logical channels (i.e., the LCIDs of the PTMs) corresponding to each TMGI service are the same, and different TMGI services may be distinguished by the G-RNTI corresponding to the TMGI.

[0143] For the first method, the network-side device does not need to allocate unnecessary signaling overhead to the LCID of the PTM, but the flexibility of this method is not high. If one TMGI service does not use all M logical channels, but only needs N (N < M) of them, the data reception entities corresponding to the extra logical channels will be wasted.

[0144] Type 2 method: A method in which the number and value of logical channels are dynamically allocated by network-side equipment, as follows:

[0145] The network-side equipment, using a common signaling or dedicated signaling method, allocates a number of logical channels (i.e., the number of LCIDs in the PTM) to the UE corresponding to one MRB, and selectively, the number of allocated logical channels may be within a certain range, for example, [1,M], so that the UE can easily assess whether its own capacity is sufficient to receive the data of this MRB.

[0146] The common signaling method described above means that the network-side equipment uses either SIB or MCCH, and all interested UEs can simultaneously receive this common signaling and the placement information carried by it.

[0147] The dedicated signaling method described above involves the network-side equipment transmitting placement information (which may also be called the PTM's logical channel information) corresponding to the PTM's LCID to the UE after the UE has entered a connected state, using the dedicated RRC signaling method. If multiple UEs need to obtain placement information corresponding to the PTM's LCID, the network-side equipment needs to transmit it once for each of these multiple UEs.

[0148] In the embodiments of this application, the PTM logical channel information transmitted by the network-side device to the UE by a signaling arrangement scheme may include one or more of the following pieces of information:

[0149] 1) The number of LCIDs of a PTM corresponding to one MRB, for example MRB1 may have two logical channels, and the values ​​of the two logical channel identifiers corresponding to MRB 1 are obtained by taking two LCID values ​​from the remaining LCID space (e.g., [35,46]) by taking (35,36) from the front or (45,46) from the back or by any other method. When the UE receives this MRB 1 service, two sets of data reception protocol stacks can be established, and these data reception protocol stacks may include at least two sets of RLC entities + PDCP entities, and in the scheduling of G-RNTI 1 corresponding to the TMGI of MRB 1, when the UE receives data of PTM LCID=35, it is sent to the first set of RLC entities + PDCP entities for processing, and when the UE receives data of PTM LCID=36, it is sent to the second set of RLC entities + PDCP entities for processing. Here, the parameters for the RLC entity and PDCP entity take the default format (predefined format), such as RLC UM mode, default RLC SN, timer length, default PDCP SN, timer length, etc.

[0150] 2) An LCID of a PTM corresponding to one MRB, for example, MRB 1 may have two logical channels, the LCIDs being 37 and 38 respectively, and the LCIDs 37 and 38 correspond to different RLC parameters and PDCP parameters, respectively.

[0151] Here, there is a one-to-one correspondence between the MRB and the LCH, meaning that the MRB may be an RB ID value that takes value in the above placement interval, or an independently placed RB ID value. Here, the network-side device may explicitly instruct the UE on the binding relationship (which may also be called an association relationship) between the RB ID and the LCID.

[0152] In the second type of scheme, the intervals over which different TMGI services take logical channel values ​​may be the same or different, and different TMGI services may be distinguished by the G-RNTI corresponding to the TMGI.

[0153] Compared to the second method described above, network-side equipment needs to consume a certain signaling overhead for PTM LCID assignment, but it offers greater flexibility. For the receiving UE, it is only necessary to establish data receiving entity groups for the number of entities actually deployed to the corresponding TMGI service, and the created data receiving entities are not wasted.

[0154] Selectively, if a UE needs to enter a connected state to receive a TMGI service, such as a multicast service with a high quality of service (QoS) requirement, network-side equipment may place the appropriate PTM LCID for the UE based on the UE's capabilities. For example, if all UEs in a group support eLCID capability, network-side equipment may place the PTM LCID corresponding to the MRB in the TMGI in the extended LCID interval. However, if at least one UE in the group does not support eLCID capability, network-side equipment can only select the PTM LCID corresponding to the MRB in the TMGI from the conventionally supported LCID intervals (e.g., 35-46).

[0155] The extended LCID supports either a one-byte or two-byte extended LCID and may correspond to intervals that take different values. Network-side equipment may determine which interval of PTM LCID value to assign to a UE based on the capabilities of the UEs in the group and other considerations, as shown, for example, in Tables 2 and 3.

[0156] [Table 2]

[0157] [Table 3]

[0158] Since the PTM LCID value needs to be received uniformly by multiple UEs, regardless of the deployment scheme, the PTM LCID value corresponding to the same MRB for the same TMGI service, received by different UEs, will be the same.

[0159] Selectively, in the embodiments of this application, the PTM leg uses G-RNTI scheduling, while the unicast service uses C-RNTI scheduling. Therefore, the LCIDs between them can be used interchangeably and may have duplicate values, and the UEs can be distinguished by different RNTIs.

[0160] Example 2: Method for arranging PTP A single MRB in a TMGI service may be configured as only a PTM leg, only a PTP leg, or both a PTP leg and a PTM leg. Multiple MRBs in a single TMGI service may be of the same configuration type or different configuration types. For example, in a single TMGI service, MRBs with high reliability requirements may be configured as both a PTP leg and a PTM leg, while MRBs with low reliability requirements may be configured as only a PTM leg.

[0161] PTP legs are generally positioned using dedicated RRC signaling, and there are two methods for determining the LCID of the PTP corresponding to the PTP leg.

[0162] Type 1: By default, the LCID of the PTM leg is the same as the LCID of the PTM leg (i.e., the LCID of the PTM by default). When placing the LCID of the PTP leg (i.e., the LCID of the PTP), the network-side equipment may indicate which MRB of which TMGI service this PTP leg corresponds to. For example, the network-side equipment may carry the TMGI and MRB ID in signaling, and the UE may determine the corresponding PTM LCID based on the TMGI and MRB ID. Of course, the network-side equipment may implicitly or explicitly indicate to the UE that the LCID of the PTP leg is the same as the LCID of the PTM leg. For example, an LCID that does not carry a PTP leg means that the LCID of the PTM leg is multiplexed.

[0163] Type 2: The LCID of the PTP leg is explicitly placed, and since the PTP leg is UE-specific, network-side equipment may be placed individually on each UE. For example, if a UE supports eLCID, network-side equipment may place an LCID within a 1-byte extension or an LCID within a 2-byte extension on this UE. Also, since the logical channel of the PTP leg and the logical channel of the unicast are multiplexed and transmitted (i.e., the LCID of the PTP leg and the LCID of the unicast are multiplexed), the LCID of the PTP leg cannot overlap with the LCID of the unicast. Selectively, the LCID of a PTP leg corresponding to a single MRB may be different from the LCID of a PTM leg, thereby simultaneously satisfying the scheduling of multicast and unicast services.

[0164] For example, if the only remaining range for unicast DL-SCH LCID is 35-46, and the LCID of the PTM leg corresponding to TMGI1 is 35-42 (i.e., the PTM leg corresponding to TMGI1 uses a total of 8 logical channels), then the LCID of the PTM leg corresponding to TMGI2 may also be 35-42 (i.e., the PTM leg corresponding to TMGI2 uses a total of 8 logical channels), and these two services are distinguished by different G-RNTI scheduling. However, if TMGI1 corresponds to 8 PTP legs and the LCID of the PTP leg corresponding to TMGI1 also uses 35-42, then if TMGI2 corresponds to 8 PTP legs, the LCID of the PTP leg corresponding to TMGI2 can only use the unused 43-46 range, or it will start using the eLCID space. In other words, when deploying PTP legs corresponding to different TMGI services on the same UE, the LCIDs between the PTP legs and between them and the DRB LCIDs must be strictly different, because both the PTP legs and unicast services are scheduled by C-RNTI, and these services must be distinguished by different LCIDs.

[0165] It should be explained that PTP legs of the same TMGI service may determine the corresponding common PDCP entity and the corresponding PTM leg based on the MRB ID to which they are placed. For example, MRB ID=35 of TMGI 1 places LCID=35 in the PTM leg and LCID=41 or 100 (value in the 1-bit extended LCID) in the PTP leg, and these two legs are simultaneously associated with a single MRB ID=35 to form a single split MRB.

[0166] Selectively, in Embodiment 2, the two methods described above may be used simultaneously. For example, if the LCID of the PTP leg can be equal to the LCID of the PTM leg, the LCID of the PTP leg may be positioned using either the first or second method. If the LCID of the PTP leg is not equal to the LCID of the PTM leg, the LCID of the PTP leg may be explicitly positioned in the UE using the second method.

[0167] Example 3: Reporting and Use of Extended LCD Capabilities If a broadcast or multicast service may have idle or inactive UE receivers, the current cell may not necessarily store the capability information of these UEs. Therefore, network-side equipment may not know whether each UE supports eLCID capability, whether it supports 1-byte (bit) eLCIDs, or whether it supports 2-byte eLCIDs. For this reason, network-side equipment and UEs may implement the following measures.

[0168] 1. Network-side devices place the LCID of the PTM leg corresponding to TMGI within the conventional 6-bit range, and only bits 35-46 remain available within these 6 bits. In this way, it is possible to ensure that all UEs can receive the PTM leg successfully, regardless of the UE's capabilities.

[0169] 2. Network-side devices place the LCID of the PTM leg corresponding to the TMGI within the range of an extended 1-byte eLCID or a 2-byte eLCID. In this way, only UEs that support extended LCIDs can successfully receive the PTM leg, and other UEs that do not support extended LCIDs may discard data packets if they parse an LCID domain they do not recognize.

[0170] 3. For services with low QoS requirements, network-side equipment may, based on placement information, instruct the UE whether to report its eLCID support capability after it has entered a connected state, for example, whether it supports eLCID, and whether it supports 1-byte eLCID and / or 2-byte eLCID. This placement information may be common signaling or dedicated signaling, and the UE may, after receiving this placement information, report based on its own capability, or not report if it does not support eLCID.

[0171] 4. The network-side device places the LCID of the PTM leg corresponding to the TMGI within the conventional 6-bit range, with only 35-46 remaining available in these 6 bits. In this way, it is possible to ensure that all UEs can receive the PTM leg successfully, regardless of the UE's capabilities. The network-side device may collect capability information of connected UEs and place the PTP leg based on the UE's capability information, and here, the LCID of the PTP leg may be placed within the UE's capability range.

[0172] If a UE requires a multicast service to be received in a connected state, by default, a connected UE may report its eLCID capability, or network-side equipment may instruct the UE to report its eLCID capability (e.g., whether it supports eLCID, and whether it supports 1-byte eLCID and / or 2-byte eLCID) as soon as possible, depending on the configuration. Here, the network-side equipment and the UE may implement the following measures:

[0173] 1. It is predetermined that if the multicast service of interest to the UE is a multicast service that the UE receives when it enters a connected state, then after the UE enters a connected state, the UE will report its own eLCID support capability as soon as possible after being securely activated, facilitating network-side equipment to determine the placement of the PTM leg and / or PTP leg.

[0174] 2. Network-side equipment instructs the UE to report eLCID support capability by common or dedicated signaling, for example, by instructing the UE to report eLCID support capability in a signaling that instructs the UE to enter a connected state in order to receive a certain multicast service (e.g., a multicast service of interest to the UE), or by instructing the UE to report eLCID support capability by dedicated RRC signaling after reporting information about multicast services of interest to the network-side equipment.

[0175] 3. If the UE does not support eLCID, the UE does not report eLCID capability information, thereby saving a certain amount of overhead.

[0176] 4. If a network-side device does not receive the eLCID support capability reported by the UE within a certain time window, the network-side device will assume that the UE does not support eLCID.

[0177] 5. After receiving eLCID capability information for each UE, the network-side equipment may determine the placement of the LCIDs on the PTM leg and / or the PTP leg. If all UEs support eLCID, the network-side equipment may place the LCIDs on the PTM leg within the eLCID range supported by all UEs. For the placement of the LCIDs on the PTP leg, the network-side equipment may place them within the range supported by each UE, depending on the differences in each UE's capability. Here, the LCIDs on the PTP leg may be the same as or different from the LCIDs on the PTM leg, and the LCIDs on the PTP leg and the LCIDs on the PTM leg may be associated by an MRB ID.

[0178] 6. When the UE is interested in multiple TMGI services, and the eLCID capability supported by the UE is insufficient to ensure reception effectiveness by placing a PTP leg for each TMGI service, the network-side equipment may place only the PTP legs within its capability range for the UE. Here, the PTP legs may be determined based on the indicated order of the services of interest reported by the UE or on the explicit priority between TMGI services.

[0179] Example 4: UE's behavior After the UE obtains the LCID of the PTM leg and / or the LCID of the PTP leg corresponding to the MRB of the TMGI service of interest and the corresponding placement, the UE may establish the corresponding data receiving entity according to these placements, where one MRB ID corresponds to one PDCP entity, one PTM leg LCID corresponds to one placed PTM RLC entity, and one PTP leg LCID corresponds to one placed PTP RLC entity. By binding the LCID of the PTM leg to the MRB ID and the LCID of the PTP leg to the same MRB ID, the UE can establish two legs split for one MRB, and the data of these two legs may be sent to a common PDCP entity for operations such as sorting and repetition detection.

[0180] When the UE receives scheduling data from G-RNTI, it performs subsequent reception processing by decrypting the LCID from the MAC PDU subheader and determining the corresponding PTM leg entity.

[0181] When the UE receives C-RNTI scheduling data, it decrypts the LCID from the MAC PDU subheader and, based on the LCID, determines the corresponding unicast receiving entity or the receiving entity for a different PTP leg of a different TMGI, thereby performing subsequent receiving processing.

[0182] It should be explained that in the logical channel placement method according to the embodiment of this application, the execution body may be a logical channel placement device or a control module for executing the logical channel placement method in this logical channel placement device. In the embodiment of this application, the logical channel placement device according to the embodiment of this application will be described as an example in which the logical channel placement device executes the logical channel placement method.

[0183] As shown in Figure 5, an embodiment of the present application provides a logical channel placement device 400, which includes an acquisition module 401. The acquisition module 401 is used to acquire at least one logical channel placement information corresponding to a first TMGI, where the one logical channel placement information indicates either a first placement, which is a PTM LCID and / or PTM RLC bearer placement, or a second placement, which is a PTP LCID and / or PTP RLC bearer placement.

[0184] Selectively, the first TMGI contains N MRBs, where each MRB corresponds to one or two logical channel placements out of at least one logical channel placement information, where N is a positive integer, where one of the two logical channel placement information indicates the first placement and the other indicates the second placement.

[0185] Selectively, one logical channel placement information indicates the LCID of the PTM, and the LCID of the PTM is all LCIDs within the interval that take a predefined value for the PTM's LCID.

[0186] Selectively, one logical channel placement information indicates the LCID of the PTM, the LCID of the PTM being the LCID of the number of targets indicated by the network-side equipment within a predefined interval of the PTM's LCID values, the number of targets being indicated by a first signaling, the first signaling being either a first common signaling or a first dedicated RRC signaling.

[0187] Selectively, one logical channel placement information indicates the PTM's LCID, which is the LCID indicated by a second signaling by the network-side device, and the second signaling is either a second common signaling or a second dedicated RRC signaling.

[0188] Selectively, the logical channel placement device may further include a receiving module used to receive first received entity placement information transmitted by a network-side device, the first received entity placement information including at least one of a PTM RLC bearer placement and a PDCP placement.

[0189] Selectively, one logical channel placement information indicates the PTP LCID, which is indicated by a third dedicated RRC signaling from the network-side equipment.

[0190] Selectively, one MRB corresponds to two logical channel placement information, and the PTP's LCID is the same as the PTM's LCID if the third dedicated RRC signaling does not include the PTP's LCID.

[0191] Selectively, the logical channel placement device may further include a receiving module used to receive second received entity placement information transmitted by a network-side device, the second received entity placement information including at least one of a PTP RLC bearer placement and a PDCP placement.

[0192] Selectively, the logical channel placement device may further include a transmitting module, which is used to transmit logical channel expansion capability information to network-side devices after the UE enters a connected state, and the logical channel expansion capability information is Whether UE supports extended LCID, The UE supports the first bit-number extended LCID, This is used to indicate that the UE supports a second-bit extended LCD, or at least one of the following.

[0193] Selectively, if the UE supports extended LCID, the PTM's LCID is within the range of either the unextended LCID or the extended LCID, and the PTP's LCID is within the range of either the unextended LCID or the extended LCID, or If the UE does not support extended LCID, the PTM's LCID is within the range of either unextended LCID or extended LCID, and the PTP's LCID is within the range of unextended LCID.

[0194] Selectively, the logical channel placement device may further include a receiving module, which is used to receive a third signaling transmitted by a network-side device before the transmitting module transmits the logical channel extension capability information to the network-side device, the third signaling being used to instruct the UE to report the extended LCID capability information.

[0195] Selectively, the logical channel placement device may further include an establishment module, a receiving module, and a transmitting module, the establishment module being used to establish a first TMGI data receiving entity based on at least one logical channel placement piece after the acquisition module has acquired at least one logical channel placement piece; the receiving module being used to receive target scheduling data; and the transmitting module being used to transmit the target scheduling data to the first TMGI data receiving entity for processing when the target scheduling data is scheduling data monitored by a group radio network temporary identifier G-RNTI corresponding to the first TMGI, or scheduling data monitored by a UE cell radio network temporary identifier C-RNTI, and the LCID in the target scheduling data is the LCID indicated by the logical channel placement piece.

[0196] Selectively, the UE does not support extended LCIDs, and the logical channel placement device may further include an execution module, which the UE uses to discard target scheduling data if, after the receiving module has received the target scheduling data, the LCID in the target scheduling data does not belong to an LCID supported by the UE.

[0197] The embodiment of this application provides a logical channel placement device that can acquire logical channel placement information of a TMGI. When a UE is interested in a TMGI, it can acquire the logical channel placement information of that TMGI, for example, a first placement (PTM LCID and / or PTM RLC bearer placement) and / or a second placement (PTP LCID and / or PTP RLC bearer placement). In this way, TMGI services can be received based on this logical channel placement information, thereby improving the cooperative transmission efficiency of multicast and unicast services, and further improving the transmission efficiency of multicast services while guaranteeing system efficiency.

[0198] As shown in Figure 6, an embodiment of the present application provides a logical channel placement device 500, which includes a transmitting module 501 used to transmit at least one logical channel placement information corresponding to a first TMGI to the UE, where the one logical channel placement information indicates either a first placement, which is a PTM LCID and / or PTM RLC bearer placement, or a second placement, which is a PTP LCID and / or PTP RLC bearer placement.

[0199] Selectively, the first TMGI contains N MRBs, where each MRB corresponds to one or two logical channel placements out of at least one logical channel placement information, where N is a positive integer, where one of the two logical channel placement information indicates the first placement and the other indicates the second placement.

[0200] Selectively, one logical channel placement information indicates the LCID of the PTM, the LCID of the PTM being the LCID of the number of targets indicated by the network-side equipment within a predefined interval of the PTM's LCID values, the number of targets being indicated by a first signaling, the first signaling being either a first common signaling or a first dedicated RRC signaling.

[0201] Selectively, one logical channel placement information indicates the PTM's LCID, which is the LCID indicated by a second signaling by the network-side device, and the second signaling is either a second common signaling or a second dedicated RRC signaling.

[0202] Selectively, the transmitting module is also used to transmit a first receiving entity placement information to the UE, the first receiving entity placement information including the PTM RLC bearer placement and the PDCP placement.

[0203] Selectively, one logical channel placement information indicates the PTP LCID, which is indicated by a third dedicated RRC signaling from the network-side equipment.

[0204] Selectively, one MRB corresponds to two logical channel placement information, and the PTP LCID is the same as the PTM LCID if the third dedicated RRC signaling does not include the PTP LCID.

[0205] Selectively, the transmitting module is used to transmit a second receiving entity placement information to the UE, the second receiving entity placement information including at least one of a PTP RLC bearer placement and a PDCP placement.

[0206] Selectively, the logical channel placement device further includes a receiving module, which is used to receive logical channel expansion capability information transmitted by the UE before the transmitting module transmits the logical channel placement information to the UE, and the logical channel expansion capability information is Whether UE supports extended LCID, The UE supports the first bit-number extended LCID, This is used to indicate that the UE supports a second-bit extended LCD, or at least one of the following.

[0207] Selectively, if the UE supports extended LCID, the PTM's LCID is within the range of either the unextended LCID or the extended LCID, and the PTP's LCID is within the range of either the unextended LCID or the extended LCID, or If the UE does not support extended LCID, the PTM's LCID is within the range of either unextended LCID or extended LCID, and the PTP's LCID is within the range of unextended LCID.

[0208] Selectively, the transmitting module is also used to send a third signal to the UE before the receiving module receives the logical channel extension capability information transmitted by the UE, and the third signal is used to instruct the UE to report the extended LCID capability information.

[0209] Embodiments of this application provide a logical channel placement device capable of transmitting TMGI logical channel placement information to the UE. When the UE reports interest in a particular TMGI, the logical channel placement information of that TMGI, for example, a first placement (PTM LCID and / or PTM RLC bearer placement) and / or a second placement (PTP LCID and / or PTP RLC bearer placement), can be transmitted to the UE. In this way, the UE can receive TMGI services based on this logical channel placement information, thereby improving the cooperative transmission efficiency of multicast and unicast services, and further improving the transmission efficiency of multicast services while ensuring system efficiency.

[0210] The logical channel placement device in the embodiments of this application may be an apparatus, a component in a UE, an integrated circuit, or a chip. This apparatus may be a mobile UE or a non-mobile UE. Exemplary examples include, but are not limited to, the types of UE11 listed above, and non-mobile UEs may be servers, network-attached storage (NAS), personal computers (PCs), televisions (TVs), teller machines or self-service machines, and the embodiments of this application are not specifically limited.

[0211] The logical channel placement device in the embodiments of this application may be a device having an operating system. This operating system may be the Android® operating system, the iOS operating system, or any other possible operating system, and the embodiments of this application are not specifically limited.

[0212] The logic channel placement apparatus according to the embodiment of this application can implement each process realized by the embodiment of the above method and achieve the same technical effects, and to avoid repetition of the explanation, it will not be explained further here.

[0213] Selectively, as shown in Figure 7, embodiments of the present application further provide a communication device 600 comprising a processor 601, a memory 602, and a program or instruction stored in the memory 602 and executable on the processor 601, for example, if the communication device 600 is a UE, when this program or instruction is executed by the processor 601, each process of the embodiment of the logical channel placement method described above can be realized and the same technical effects can be achieved. If the communication device 600 is a network-side device, when this program or instruction is executed by the processor 601, each process of the embodiment of the logical channel placement device method described above can be realized and the same technical effects can be achieved. To avoid repetition of the explanation, no further explanation is provided here.

[0214] Figure 8 is a schematic diagram of the hardware structure of the UE that realizes the embodiment of this application.

[0215] This UE 100 includes, but is not limited to, a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 110.

[0216] As those skilled in the art will understand, the UE 100 may further include power supplies (e.g., batteries) to power each component, and the power supplies may be logically connected to the processor 110 by a power management system, thereby enabling functions such as charge / discharge management and power consumption management by the power management system. The UE structure shown in Figure 8 does not constitute a limitation on the UE, and the UE may include more or fewer components than those shown, or combinations of some components, or different arrangements of components, which will not be described further here.

[0217] It should be understood that, in the embodiments of this application, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042, the graphics processor 1041 processing still images or video image data obtained by an image capture device (e.g., a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be arranged in the form of a liquid crystal display, organic light-emitting diode, etc. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touchscreen. The touch panel 1071 may include two parts: a touch detection device and a touch controller. The other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control buttons, switch buttons, etc.), a trackball, a mouse, or an operating lever, and will not be described further here.

[0218] In the embodiments of this application, the radio frequency unit 101 receives downlink data from network-side equipment, processes it with the processor 110, and transmits uplink data to the network-side equipment. Generally, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0219] Memory 109 may be used to store software programs or instructions and various data. Memory 109 may mainly include a program or instruction storage area and a data storage area, where the program or instruction storage area can store an operating system, an application program or instructions necessary for at least one function (e.g., audio playback function, image playback function, etc.). Memory 109 may also include high-speed random access memory and non-volatile memory, where the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or flash memory. For example, it may be at least one magnetic disk memory device, a flash memory device, or other non-volatile solid-state memory device.

[0220] The processor 110 may include one or more processing units. Optionally, the processor 110 may integrate an application processor and a modem processor. Here, the application processor primarily handles the operating system, user interface, and application programs or instructions, while the modem processor primarily handles wireless communication, such as a baseband processor. To be clear, the modem processor does not necessarily have to be integrated into the processor 110.

[0221] Here, the processor 110 is used to obtain at least one logical channel placement information corresponding to the first TMGI, where the one logical channel placement information indicates either a first placement which indicates the LCID and / or PTM RLC bearer placement of the PTM, or a second placement which indicates the LCID and / or PTP RLC bearer placement of the PTP.

[0222] Selectively, the first TMGI contains N MRBs, where each MRB corresponds to one or two logical channel placements out of at least one logical channel placement information, where N is a positive integer, where one of the two logical channel placement information indicates the first placement and the other indicates the second placement.

[0223] Selectively, one logical channel placement information indicates the LCID of the PTM, and the LCID of the PTM is all LCIDs within the interval that take a predefined value for the PTM's LCID.

[0224] Selectively, one logical channel placement information indicates the LCID of the PTM, the LCID of the PTM being the LCID of the number of targets indicated by the network-side equipment within a predefined interval of the PTM's LCID values, the number of targets being indicated by a first signaling, the first signaling being either a first common signaling or a first dedicated RRC signaling.

[0225] Selectively, one logical channel placement information indicates the PTM's LCID, which is the LCID indicated by a second signaling by the network-side device, and the second signaling is either a second common signaling or a second dedicated RRC signaling.

[0226] Selectively, the logical channel placement device may further include a receiving module used to receive first received entity placement information transmitted by a network-side device, the first received entity placement information including at least one of a PTM RLC bearer placement and a PDCP placement.

[0227] Selectively, one logical channel placement information indicates the PTP LCID, which is indicated by a third dedicated RRC signaling from the network-side equipment.

[0228] Selectively, one MRB corresponds to two logical channel placement information, and the PTP's LCID is the same as the PTM's LCID if the third dedicated RRC signaling does not include the PTP's LCID.

[0229] Selectively, a radio frequency unit is used to receive second received entity placement information transmitted by a network-side device, the second received entity placement information including at least one of a PTP RLC bearer placement and a PDCP placement.

[0230] Selectively, the radio frequency unit may also be used to transmit logical channel expansion capability information to network-side equipment after the UE has entered a connected state, and the logical channel expansion capability information is Whether UE supports extended LCID, The UE supports the first bit-number extended LCID, This is used to indicate that the UE supports a second-bit extended LCD, or at least one of the following.

[0231] Selectively, if the UE supports extended LCID, the PTM's LCID is within the range of either the unextended LCID or the extended LCID, and the PTP's LCID is within the range of either the unextended LCID or the extended LCID, or If the UE does not support extended LCID, the PTM's LCID is within the range of either unextended LCID or extended LCID, and the PTP's LCID is within the range of unextended LCID.

[0232] Selectively, the radio frequency unit may be used to receive a third signaling transmitted by a network-side device before the transmitting module transmits logical channel expansion capability information to the network-side device, the third signaling being used to instruct the UE to report the expanded LCID capability information.

[0233] Selectively, the processor 110 may further be used to establish a data receiving entity of a first TMGI based on at least one logical channel placement information after acquiring at least one logical channel placement information, the radio frequency unit 101 may further be used to receive target scheduling data, and the processor 110 may further be used to transmit the target scheduling data to the data receiving entity of the first TMGI for processing when the target scheduling data is scheduling data monitored by a group radio network temporary identifier G-RNTI corresponding to the first TMGI, or when the target scheduling data is scheduling data monitored by a cell radio network temporary identifier C-RNTI of a UE, and the LCID in the target scheduling data is the LCID indicated by the logical channel placement information.

[0234] Selectively, the UE does not support extended LCIDs, and the logical channel placement device may further include an execution module, which the UE uses to discard target scheduling data if, after the receiving module has received the target scheduling data, the LCID in the target scheduling data does not belong to an LCID supported by the UE.

[0235] The embodiments of this application provide a UE that can acquire logical channel placement information of a TMGI. When the UE is interested in a TMGI, it can acquire the logical channel placement information of that TMGI, for example, a first placement (PTM LCID and / or PTM RLC bearer placement) and / or a second placement (PTP LCID and / or PTP RLC bearer placement). In this way, the TMGI service can be received based on this logical channel placement information, thereby improving the cooperative transmission efficiency of multicast and unicast services, and further improving the transmission efficiency of multicast services while ensuring system efficiency.

[0236] Specifically, the embodiments of this application further provide network-side equipment. As shown in Figure 9, this network-side equipment 700 includes an antenna 71, a radio frequency device 72, and a baseband device 73. The antenna 71 and the radio frequency device 72 are connected. In the uplink direction, the radio frequency device 72 receives information via the antenna 71 and transmits the received information to the baseband device 73 for processing. In the downlink direction, the baseband device 73 processes the information to be transmitted and transmits it to the radio frequency device 72, which processes the received information and then transmits it via the antenna 71.

[0237] The above-mentioned frequency band processing device may be located in the baseband device 73, and the method performed by the network-side equipment in the above embodiment may be implemented in the baseband device 73, which includes a processor 74 and a memory 75.

[0238] The baseband device 73 may include, for example, at least one baseband board on which multiple chips are installed, and as shown in Figure 9, one of the chips is, for example, a processor 74, which is connected to a memory 75 and calls a program in the memory 75 to perform the operation of the network-side equipment as shown in the embodiment of the above method.

[0239] The baseband device 73 may further include a network interface 76 used for exchanging information with the radio frequency device 72, which is, for example, a common public radio interface (CPRI).

[0240] Specifically, the network-side device of the embodiment of the present invention further includes instructions or programs stored in memory 75 and executable on processor 74, the processor 74 can call the instructions or programs in memory 75 and execute the same method as shown by each module in Figure 6, and achieve the same technical effect, which will not be described further here in order to avoid repetition of the explanation.

[0241] The radio frequency device 72 is used to transmit at least one logical channel placement information corresponding to a first TMGI to the UE, where the one logical channel placement information indicates either a first placement, which is a PTM LCID and / or PTM RLC bearer placement, or a second placement, which is a PTP LCID and / or PTP RLC bearer placement.

[0242] Selectively, the first TMGI contains N MRBs, where each MRB corresponds to one or two logical channel placements out of at least one logical channel placement information, where N is a positive integer, where one of the two logical channel placement information indicates the first placement and the other indicates the second placement.

[0243] Selectively, one logical channel placement information indicates the LCID of the PTM, the LCID of the PTM being the LCID of the number of targets indicated by the network-side equipment within a predefined interval of the PTM's LCID values, the number of targets being indicated by a first signaling, the first signaling being either a first common signaling or a first dedicated RRC signaling.

[0244] Selectively, one logical channel placement information indicates the PTM's LCID, which is the LCID indicated by a second signaling by the network-side device, and the second signaling is either a second common signaling or a second dedicated RRC signaling.

[0245] Selectively, the radio frequency device 72 is used to transmit first received entity placement information to the UE, the first received entity placement information including PTM RLC bearer placement and PDCP placement.

[0246] Selectively, one logical channel placement information indicates the PTP LCID, which is indicated by a third dedicated RRC signaling from the network-side equipment.

[0247] Selectively, one MRB corresponds to two logical channel placement information, and the PTP LCID is the same as the PTM LCID if the third dedicated RRC signaling does not include the PTP LCID.

[0248] Selectively, the radio frequency device 72 is used to transmit a second receiving entity placement information to the UE, the second receiving entity placement information including at least one of a PTP RLC bearer placement and a PDCP placement.

[0249] Selectively, the radio frequency device 72 is also used to receive logical channel expansion capability information transmitted by the UE before transmitting logical channel placement information to the UE, and the logical channel expansion capability information is Whether UE supports extended LCID, The UE supports the first bit-number extended LCID, This is used to indicate that the UE supports a second-bit extended LCD, or at least one of the following.

[0250] Selectively, if the UE supports extended LCID, the PTM's LCID is within the range of either the unextended LCID or the extended LCID, and the PTP's LCID is within the range of either the unextended LCID or the extended LCID, or If the UE does not support extended LCID, the PTM's LCID is within the range of either unextended LCID or extended LCID, and the PTP's LCID is within the range of unextended LCID.

[0251] Selectively, the radio frequency device 72 is also used to transmit a third signal to the UE before receiving the logical channel extension capability information transmitted by the UE, the third signal being used to instruct the UE to report the extended LCID capability information.

[0252] The embodiment of this application provides network-side equipment that can transmit TMGI logical channel placement information to the UE. When the UE reports interest in a particular TMGI, it can transmit the logical channel placement information of that TMGI, for example, a first placement (PTM LCID and / or PTM RLC bearer placement) and / or a second placement (PTP LCID and / or PTP RLC bearer placement), to the UE. In this way, the UE can receive TMGI services based on this logical channel placement information, thereby improving the cooperative transmission efficiency of multicast and unicast services, and further improving the transmission efficiency of multicast services while ensuring system efficiency.

[0253] Embodiments of this application further provide a readable storage medium on which a program or instruction is stored, and when this program or instruction is executed by a processor, each process of the embodiment of the logical channel arrangement method described above can be realized and the same technical effects can be achieved. To avoid repetition, no further explanation is provided here.

[0254] Here, the processor is the processor in the UE in the above embodiment. The readable storage medium includes computer-readable storage media such as computer read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0255] Embodiments of this application further provide a chip comprising a processor and a communication interface, the communication interface being coupled with the processor, the processor executing programs or instructions for network-side equipment, and used to implement each process of the embodiment of the logical channel arrangement method described above, and achieving the same technical effects. To avoid repetition, no further explanation is provided here.

[0256] It should be understood that the chips referred to in the embodiments of this application may also be called system-level chips, system chips, chip systems, or system-on-a-chip, etc.

[0257] It should be noted that, in this specification, the terms “include,” “incorporate,” or any other variation thereof are intended to cover the non-exclusive “include,” thereby including not only those elements but also other elements not explicitly listed, or elements specific to such process, method, article, or apparatus. Unless otherwise specified, an element limited by the phrase “includes one of…” is not excluded from the existence of other identical elements in a process, method, article, or apparatus containing that element. It should also be noted that the scope of methods and apparatus in embodiments of this application is not limited to performing functions in the order illustrated or discussed, but may include performing functions in a manner that is essentially simultaneous or in reverse order based on the functions involved, and methods described in a different procedure than those described, for example, may be performed, and various steps may be added, omitted, or combined. Furthermore, features described by reference to some examples may be combined with other examples.

[0258] As will be readily apparent to those skilled in the art from the above description of the embodiments, the methods of the above embodiments can be implemented in the form of software and a necessary general-purpose hardware platform. Of course, they may also be implemented in hardware, but in many cases the former is a more preferred embodiment. With this understanding in mind, the technical proposal of this application may be embodied in the form of a software product, either substantially or in part with respect to the prior art. This computer software product is stored on a single storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and contains a number of instructions for causing a single UE (which may be a mobile phone, computer, server, air conditioner, or network-side device, etc.) to perform the methods of each embodiment of this application.

[0259] The above describes embodiments of this application, accompanied by drawings; however, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can, by the suggestion of this application, make many forms, as long as they do not deviate from the spirit and claims of this application, and all of these fall within the scope of protection of this application. [Explanation of symbols]

[0260] 11. User Equipment (UE) 12 Network-side devices 71 Antenna 72 Radio frequency equipment 73 Baseband equipment 74 processors 75 memory 76 Network Interfaces 100 User Equipment (UE) 101 Radio frequency unit 102 Network Module 103 Audio Output Unit 104 Input Unit 105 Sensor 106 Display Unit 107 User Input Unit 108 Interface Unit 109 memory 400 Logical Channel Placement Device 401 Acquisition Module 500 Logical Channel Placement Device 501 Transmitter Module 600 communication devices 601 Processor 602 memory 700 Network-side devices 1041 Graphics Processor (GPU) 1042 Microphone 1061 Display Panel 1071 Touch Panel 1072 Input devices

Claims

1. A logical channel arrangement method, The user device UE obtains at least one logical channel placement information corresponding to a first temporary movement group identifier TMGI, Here, one logical channel placement information is: A first configuration comprising a point-to-multipoint PTM logical channel identifier LCID and / or a PTM radio link control RLC bearer configuration, A second configuration, which indicates either a point-to-point PTP LCID and / or a PTP RLC bearer configuration, The first TMGI includes N multicast radio bearer MRBs, where each MRB corresponds to one or two logical channel placements from the at least one logical channel placement information, and N is a positive integer of 2 or more. Herein, a logical channel arrangement method in which one of the two logical channel arrangement pieces indicates the first arrangement, and the other logical channel arrangement piece indicates the second arrangement.

2. The LCID of the PTM is all LCIDs in the interval where the LCID of the PTM takes a predetermined value. Or, The method according to claim 1, wherein the LCID of the PTM is an LCID indicated by a second signaling by a network-side device, and the second signaling is a second common signaling or a second dedicated RRC signaling.

3. The aforementioned method, The method according to claim 2, further comprising the UE receiving first received entity placement information transmitted by a network-side device, wherein the first received entity placement information includes at least one of a PTM RLC bearer placement and a packet data convergence protocol PDCP placement.

4. The method according to claim 1, wherein the LCID of the PTP is indicated by a third dedicated RRC signaling from the network-side device.

5. The aforementioned method, The method according to claim 4, further comprising the UE receiving second received entity placement information transmitted by the network-side device, wherein the second received entity placement information includes at least one of a PTP RLC bearer placement and a PDCP placement.

6. A logical channel arrangement method, The network-side device transmits at least one logical channel placement piece of information corresponding to a first temporary mobile group identifier (TMGI) to the user device UE, Here, one logical channel placement information is: A first configuration comprising a point-to-multipoint PTM logical channel identifier LCID and / or a PTM radio link control RLC bearer configuration, A second configuration, which indicates either a point-to-point PTP LCID and / or a PTP RLC bearer configuration, The first TMGI includes N multicast radio bearer MRBs, where each MRB corresponds to one or two logical channel placements from the at least one logical channel placement information, and N is a positive integer of 2 or more. Herein, a logical channel arrangement method in which one of the two logical channel arrangement pieces indicates the first arrangement, and the other logical channel arrangement piece indicates the second arrangement.

7. The LCID of the PTM is all LCIDs in the interval where the LCID of the PTM takes a predetermined value. Or, The method according to claim 6, wherein the LCID of the PTM is an LCID indicated by a second signaling by a network-side device, and the second signaling is a second common signaling or a second dedicated RRC signaling.

8. The aforementioned method, The method according to claim 7, further comprising the network-side device transmitting first received entity placement information to the UE, wherein the first received entity placement information includes a PTM RLC bearer placement and a packet data convergence protocol PDCP placement.

9. One logical channel placement information indicates the LCID of the PTP, The method according to claim 6, wherein the LCID of the PTP is indicated by the network-side device via a third dedicated RRC signaling.

10. The aforementioned method, The method according to claim 9, further comprising the network-side device transmitting second received entity placement information to the UE, wherein the second received entity placement information includes at least one of a PTP RLC bearer placement and a PDCP placement.

11. A user device UE comprising a processor, memory, and a program or instruction stored in the memory and executable on the processor, wherein when the program or instruction is executed by the processor, the steps of the logical channel arrangement method described in any one of claims 1 to 5 are realized.

12. A network-side device comprising a processor, memory, and a program or instruction stored in the memory and executable on the processor, wherein when the program or instruction is executed by the processor, the steps of the logical channel arrangement method described in any one of claims 6 to 10 are realized.

Images