Logical channel configuration 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 priority to China Patent Application No. 202110057653.3, filed in China on January 15, 2021, the entire contents of which are incorporated herein by reference.

[0002] The present application relates to the field of communications technology, and in particular to a logical channel allocation method, apparatus and device. [Background technology]

[0003] In the broadcast / multicast transmission of long term evolution (LTE), it is supported to transmit multimedia broadcast multicast service (MBMS) in a multicast / broadcast single frequency network (MBSN) manner and to transmit multicast service in a single cell point to multipoint (SC-PTM) manner. Here, in the MBSFN scheme, since a multicast service has a completely independent transmission channel and transmission time domain position from a unicast service, there is no need to consider the problem of overlapping logical channels. In contrast to the SC-PTM scheme, only one special logical channel identification (LCID) is assigned to a multicast service in LTE, and this LCID can distinguish a single cell-multicast control channel (SC-MCCH) and a single cell-multicast traffic channel (SC-MTCH) to distinguish a unicast service. Multiple SC-MCCHs and SC-MTCHs can be distinguished by a group-radio network temporary identifier (G-RNTI).

[0004] However, the multicast transmission of new radio (NR) is more complicated than that of LTE. In NR, one temporary mobile group identifier (TMGI) service may correspond to multiple logical channels, and a multicast radio bearer (MRB) in one TMGI may simultaneously configure a PTM leg and a point to point (PTP) leg. The rational configuration of the PTM leg and the PTP leg can ensure that the scheduling of the multicast service and the unicast service in NR is coordinated, thereby ensuring the normal operation of the multicast service. Therefore, how to properly schedule a multicast service in NR is an issue that needs to be resolved quickly. Summary of the Invention [Problem to be solved by the invention]

[0005] The embodiments of the present application provide a logical channel configuration method, apparatus, and device that can solve the problem of how to successfully schedule multicast services in NR. [Means for solving the problem]

[0006] In order to solve the above technical problems, the present application is realized as follows.

[0007] According to a first aspect, there is provided a logical channel configuration method, the method including: a user equipment (UE) obtaining at least one logical channel configuration information corresponding to a first TMGI, where the one logical channel configuration information indicates one of a first configuration, which is a PTM LCID and / or a PTM radio link control (RLC) bearer configuration, and a second configuration, which is a PTP LCID and / or a PTP RLC bearer configuration.

[0008] According to a second aspect, a logical channel configuration method is provided, the method including: a network side device sending at least one logical channel configuration information corresponding to a first TMGI to a UE, where the one logical channel configuration information indicates one of a first configuration, which is a PTM LCID and / or a PTM RLC bearer configuration, and a second configuration, which is a PTP LCID and / or a PTP RLC bearer configuration.

[0009] According to a third aspect, there is provided a logical channel configuration device, the device including: an acquisition module; the acquisition module is used for acquiring at least one logical channel configuration information corresponding to a first TMGI, where the one logical channel configuration information indicates one of a first configuration, which is a PTM LCID and / or a PTM RLC bearer configuration, and a second configuration, which is a PTP LCID and / or a PTP RLC bearer configuration.

[0010] According to a fourth aspect, there is provided a logical channel configuration device, the device including: a transmitting module; the transmitting module is used for transmitting at least one logical channel configuration information corresponding to a first TMGI to a UE, where the one logical channel configuration information indicates one of a first configuration, which is a PTM LCID and / or a PTM RLC bearer configuration, and a second configuration, which is a PTP LCID and / or a PTP RLC bearer configuration.

[0011] According to a fifth aspect, there is provided a UE comprising a processor, a memory and a program or instructions stored in the memory and executable on the processor, the program or instructions, when executed by the processor, implementing steps of the method according to the first aspect.

[0012] According to a sixth aspect, there is provided a network side device comprising a processor, a memory, and a program or instructions stored in the memory and executable on the processor, the program or instructions, when executed by the processor, realising the steps of the method according to the second aspect.

[0013] According to a seventh aspect, there is provided a readable storage medium having a program or instructions stored thereon, the program or instructions, when executed by a processor, performing steps of the method according to the first aspect or performing steps of the method according to the second aspect.

[0014] According to an eighth aspect, there is provided a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to execute a program or instruction of a network side device to realize the method according to the first aspect or to realize the method according to the second aspect. Effect of the Invention

[0015] In an embodiment of the present application, the UE obtains at least one logical channel configuration information corresponding to a first TMGI, where the one logical channel configuration information indicates one of the following configurations: a first configuration, which is a PTM LCID and / or a PTM RLC bearer configuration, and a second configuration, which is a PTP LCID and / or a PTP RLC bearer configuration. With this method, the UE can obtain the logical channel configuration information of the TMGI, so that when the UE is interested in a TMGI, the UE can obtain the logical channel configuration information of the TMGI, such as the first configuration (PTM LCID and / or PTM RLC bearer configuration) and / or the second configuration (PTP LCID and / or PTP RLC bearer configuration), and thus the UE can receive the TMGI service according to the logical channel configuration information, thereby improving the cooperative transmission efficiency of the UE's multicast service and unicast service, and further improving the transmission efficiency of the UE's multicast service while ensuring system efficiency. [Brief description of the drawings]

[0016] [Figure 1] 1 is a block diagram of a wireless communication system according to an embodiment of the present application. [Diagram 2] 1 is a flowchart of a logical channel configuration method according to an embodiment of the present application. [Diagram 3] 2 is a second flowchart of a logical channel configuration method according to an embodiment of the present application. [Figure 4] FIG. 2 is a schematic diagram of a protocol stack architecture of a UE according to an embodiment of the present application; [Diagram 5] 1 is a structural schematic diagram of a logical channel configuration device according to an embodiment of the present application; [Figure 6] 2 is a second structural schematic diagram of a logical channel configuration device according to an embodiment of the present application; [Figure 7] 1 is a hardware schematic diagram of a communication device according to an embodiment of the present application; [Figure 8] FIG. 2 is a hardware schematic diagram of a UE according to an embodiment of the present application. [Figure 9] FIG. 2 is a hardware schematic diagram of a network side device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] The following clearly and completely describes the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application, and obviously, the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by those skilled in the art on the basis of the embodiments of the present application without any creative efforts are within the scope of protection of the present application.

[0018] The terms "first," "second," etc. in the specification and claims of the present application are intended to distinguish between similar objects and are not intended to describe a particular order or sequence. It is to be understood that data so used are interchangeable where appropriate, such that the embodiments of the present application may be performed in an order other than that shown or described herein, and that the objects distinguished by "first" and "second" are generally of the same type and do not limit the number of objects, e.g., the first object may be one or more. Note that "and / or" in the specification and claims represents at least one of the objects connected, and the character " / " generally represents an "or" relationship between the related objects.

[0019] It should be noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be applied 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 the present application are always used interchangeably, and the techniques described may be used in the above-mentioned systems and radio technologies, or in other systems and radio technologies. However, although the following description describes a New Radio (NR) system for illustrative purposes and uses NR terminology in most of the following description, these techniques may be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.

[0020] FIG. 1 shows a block diagram of a wireless communication system to which the embodiment of the present application can be applied. The wireless communication system includes a UE 11 and a network side device 12. Here, the UE 11 may be called a terminal device or a terminal, and 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 palmtop computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), a wearable device, a vehicle-mounted device (VUE), a pedestrian terminal (PUE), etc., and the wearable device includes a bracelet, an earphone, glasses, etc. It should be noted that the embodiment of the present application does not limit the specific type of the UE 11. The network side equipment 12 may be a base station or a core network, where 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 receiving point (TRP), or any other suitable term in the art, and as long as the same technical effect is achieved, the base station is not limited to a specific technical term, and it should be explained that in the embodiments of this application, only a base station in an NR system is taken as an example, but the specific type of the base station is not limited.

[0021] In an embodiment of the present application, for one multicast service (e.g., a TMGI service), the network side equipment may configure and transmit two legs for the UE, where the two legs include a PTP leg and a PTM leg.

[0022] Here, the PTM leg refers to a network device scrambling a physical downlink control channel (PDCCH) using a common RNTI (e.g., G-RNTI), and all UEs in the group jointly monitor the scheduling of the G-RNTI and receive the subsequent scheduling data, and the data transmitted once in the PTM leg may be received by multiple UEs, that is, PTM transmits data to multiple UEs at the same time, and the transmission efficiency is relatively high. However, since PTM needs to comprehensively consider the coverage for all UEs, the transmission parameters of PTM need to be applied to all UEs, such as using an omnidirectional antenna to consider UEs with relatively poor link quality. Therefore, for some UEs with relatively poor link quality, the effect of PTM may be relatively poor.

[0023] The PTP leg refers to the network side equipment scrambling the PDCCH with a cell-radio network temporary identifier (C-RNTI) dedicated to the UE, and only the UE can monitor the scheduling of the C-RNTI and receive the subsequent scheduling data. The data transmitted in one time on the PTP leg is received by only one UE, that is, the PTP leg is a dedicated transmission leg for one UE. Therefore, the network side equipment can adjust the transmission parameters according to the link quality of the UE, for example, use a directional or forming antenna to set appropriate transmission parameters according to the link quality of the UE. Therefore, the transmission effect for a single UE is relatively good. However, if data needs to be transmitted to multiple UEs, multiple transmission resources are required, which makes the transmission efficiency relatively low.

[0024] The logical channel configuration method according to the embodiment of the present application will be described in detail below with reference to specific embodiments and application scenarios in conjunction with the drawings.

[0025] As shown in FIG. 2, an embodiment of the present application provides a logical channel configuration method, which is performed by a UE, and may include the following step 201.

[0026] Step 201: the UE obtains at least one logical channel configuration information corresponding to a first TMGI.

[0027] Here, one piece of logical channel allocation information among the at least one piece of logical channel allocation information is A first configuration, comprising a PTM LCID and / or a PTM RLC bearer configuration; The second configuration may indicate one of the following configurations: PTP LCID and / or PTP RLC bearer configuration.

[0028] It should be noted that in the embodiment of the present application, the one logical channel configuration information is any one of the at least one logical channel configuration information, where, when the number of the at least one logical channel configuration information is plural, the logical channel configuration information of the at least one logical channel configuration information may be the same or different, and may be specifically determined according to actual usage demand, and is not limited in the embodiment of the present application.

[0029] In an embodiment of the present application, the UE can obtain at least one logical channel configuration information corresponding to the above-mentioned first TMGI, and the UE can receive the first TMGI service based on the at least one logical channel configuration information, thereby ensuring the transmission efficiency of the UE's multicast service.

[0030] In an embodiment of the present application, the first TMGI may be a TMGI of interest to the UE, for example, a TMGI from which the UE wishes to receive data.

[0031] Optionally, in an embodiment of the present application, the first TMGI may include N MRBs, and one MRB among the N MRBs may correspond to one or two logical channel configuration information of the at least one logical channel configuration information, where N is a positive integer.

[0032] Here, one of the two logical channel configuration information may indicate the first configuration (PTM LCID and / or PTM RLC bearer configuration), and the other logical channel configuration information may indicate the second configuration (PTP LCID and / or PTP RLC bearer configuration).

[0033] In an embodiment of the present application, one logical channel configuration information may include TMGI information and MRB information corresponding to this logical channel, so that the UE can determine the MRB corresponding to each logical channel configuration information among the at least one logical channel configuration information.

[0034] Optionally, in the embodiment of the present application, N may be any possible value such as 2, 4, 8, 16, etc., and may be specifically determined according to actual usage demand, and is not limited in the embodiment of the present application.

[0035] It should be noted that when the one MRB corresponds to two logical channel configuration information of the at least one logical channel configuration information, the number of the at least one logical channel configuration information is plural.

[0036] In addition, when one MRB corresponds to the above two pieces of logical channel configuration information, there are a PTM leg and a PTP leg corresponding to this MRB.

[0037] In an embodiment of the present application, any one of the at least one logical channel configuration information can be realized in the following four cases (Case 1, Case 2, Case 3 and Case 4, respectively). In the following, one logical channel configuration information is taken as an example to exemplify the logical channel configuration information related to the embodiment of the present application.

[0038] The implementation method of other logical channel configuration information among the at least one logical channel configuration information is similar to the implementation method of the first logical channel configuration information below, and in order to avoid repetition of description, it will not be further described in the embodiments of the present application.

[0039] Case 1: When one piece of logical channel configuration information indicates an LCID of a PTM, the LCID of this PTM may be all LCIDs in a section that takes on a predefined LCID value of the PTM.

[0040] For case 1 above, the interval in which the PTM's LCID takes on the value may be predefined (i.e., specified by the standard / protocol), and the UE may then determine, based on the interval in which the PTM's LCID takes on the predefined value, that the PTM's LCID is all LCIDs in the interval in which this value takes on.

[0041] Optionally, in an embodiment of the present application, a TMGI service may be predefined to have a maximum of M MRBs, where M is a positive integer (e.g., any possible value such as 2, 4, 8, 16, etc.), and the LCID of the PTM corresponding to the M MRBs is predefined, for example, [35, 35+M-1] or [46-M+1, 46], and the value of the LCID of the above PTM may be any value in [46-M+1, 46].

[0042] As can be seen, in the above case 1, the intervals in which the LCID of the PTM takes the value for different TMGIs are the same, and the different TMGIs may be distinguished by the G-RNTI.

[0043] For the above case 1, 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 scheduling of a G-RNTI corresponding to the first TMGI, the UE may determine that it is the first TMGI based on the G-RNTI, and determine corresponding RLC entities and PDCP entities from the M sets of protocol stack entities based on an LCID carried in a medium access control (MAC) protocol data unit (PDU) subheader of the G-RNTI scheduling, perform service reception processing, and pass it to an upper layer.

[0044] In the embodiment of the present application, for case 1, the LCID of the PTM is predefined, so that the network side device does not need to assign additional signaling to the LCID of the PTM, thereby saving the signaling overhead of the network side device.

[0045] Case 2: When one piece of logical channel allocation information indicates an LCID of a PTM, the LCID of this PTM may be a target number of LCIDs indicated by a network side device in a section in which the LCID value of the predefined PTM is taken.

[0046] Wherein, the target number may be indicated by a first signaling, and the first signaling may be a first common signaling or a first dedicated radio resource control (RRC) signaling.

[0047] In the above case 2, the network side device may indicate to the UE by the first signaling the number of LCIDs of the PTM of one logical channel corresponding to one MBR, so that the UE can determine the LCID of the PTM from the interval in which the LCID of the PTM takes on a predefined value.

[0048] Alternatively, in an embodiment of the present application, the UE may determine the LCID of the PTM from an interval in which the LCID of the predefined PTM is taken based on the target number in a manner of taking the LCID value of the predefined PTM.

[0049] Alternatively, the method of obtaining the LCID value of the predefined PTM may be from the front to the back of the section in which the LCID value of the predefined PTM is obtained, or may be from the back to the front of the section in which the LCID value of the predefined PTM is obtained. Specifically, it may be determined according to actual usage demand, and is not limited in the embodiment of the present application.

[0050] For example, if the interval in which the LCID of the predefined PTM takes a value is [35, 46] and the target number is 2, the LCID of the PTM may be 35 and 36 when the LCID of the predefined PTM takes a value from front to back in the interval in which the LCID of the predefined PTM takes a value, and the LCID of the PTM may be 45 and 46 when the LCID of the predefined PTM takes a value from back to front in the interval in which the LCID of the predefined PTM takes a value. In this way, when the UE receives the MRB 1, two sets of receiving protocol stacks may be established, that is, the receiving entity established by the UE includes at least two sets of RLC+PDCP receiving entities, and in the scheduling of G-RNTI, the UE may transmit data received with LCID=35 of the PTM to a first set of RLC+PDCP receiving entities for processing, and transmit data received with LCID=36 to a second set of RLC+PDCP receiving entities for processing.

[0051] Alternatively, in an embodiment of the present application, the first common signaling may be in the form of a system information block (SIB) or a multicast control channel (MCCH), in this way all interested UEs can receive this first common signaling, thereby receiving the target number, and the UEs can obtain one logical channel configuration information.

[0052] In the embodiment of the present application, after the UE enters a connected state, the network side equipment may send the above target number to the UE via a first dedicated RRC signaling, so that the UE can obtain one logical channel configuration information. For this first dedicated RRC signaling, if multiple UEs need to obtain this one logical channel configuration information, the network side equipment may send this first dedicated signaling once to each UE in the multiple UEs.

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

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

[0055] For the above case 3, the network side device may directly indicate the LCID of the PTM to the UE through the above second signaling, for example, the second signaling may include the LCID of the PTM.

[0056] Alternatively, in the embodiments of the present application, the above-mentioned second common signaling may be in the form of SIB or MCCH, whereby the network side equipment may send the LCID of the PTM carried in the second common signaling to the UE, so that the UE obtains one logical channel configuration information.

[0057] In an embodiment of the present application, after the UE enters a connected state, the network side equipment may send the LCID of the PTM to the UE via a second dedicated RRC signaling, so that the UE can obtain one logical channel configuration information.

[0058] For example, in an embodiment of the present application, if the LCIDs of the PTM corresponding to MRB 2 are 37 and 38, the network side equipment may carry the LCID of PTM=37 and the LCID of PTM=38 in the second signaling and send it to the UE, so that the UE can obtain the logical channel configuration information corresponding to MRB 2.

[0059] Alternatively, in the embodiment of the present application, for the above cases 1, 2 and 3, the network side equipment may send entity configuration information to the UE by one receiving entity configuration information (for example, the first receiving entity configuration information in the embodiment of the present application), so that the UE can establish a corresponding data receiving entity according to the receiving entity configuration information and the above one logical channel configuration information.

[0060] In the embodiment of the present application, for the above cases 1, 2 and 3, the logical channel configuration method according to the embodiment of the present application may further include the following steps 202 and 203.

[0061] Step 202: the network side device sends first receiving entity configuration information to the UE.

[0062] Step 203, the UE receives first receiving entity configuration information sent by the network side equipment.

[0063] Here, the first receiving entity configuration information may include at least one of a PTM RLC bearer configuration (which may be referred to as a PTM RLC parameter) and a PDCP configuration (which may be referred to as a PDCP parameter).

[0064] In the embodiment of the present application, the network side device may send the first receiving entity configuration information to the UE, and after the UE receives the first receiving entity configuration information, the UE may establish a corresponding data receiving entity according to the first receiving entity configuration information and the one logical channel configuration information, so that the corresponding data can be sent to the data receiving entity when it is received.

[0065] It should be noted that in the embodiment of the present application, when the one logical channel configuration information includes a PTM RLC bearer configuration, the first receiving entity configuration information does not need to include a PTM RLC bearer configuration.

[0066] Optionally, in an embodiment of the present 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 the PDCP configuration may further include any other possible configurations (parameters), and may be specifically determined according to actual usage needs, and are not limited to the embodiments of the present application.

[0068] Case 4: When one piece of logical channel configuration information indicates the LCID of a PTP, the LCID of the PTP may be indicated by the network side device through a third dedicated RRC signaling.

[0069] For the above case 4, the network side device may indicate the LCID of the PTP to the UE through the third dedicated RRC signaling.

[0070] In an embodiment of the present application, the third signaling may include (or carry) the LCID of the PTP, the TMGI and information of the MRB (e.g., the MRB ID), thereby indicating the LCID of the PTP corresponding to this MRB to the UE.

[0071] Optionally, in an embodiment of the present application, if one MRB corresponds to two logical channel configuration information, when the LCID of the PTP is not included in the third dedicated RRC signaling, the LCID of the PTP is the same as the LCID of the PTM.

[0072] It can be understood that the LCID of the PTP may be such that one of the two logical channel configuration information indicates the LCID of the PTM, and another logical channel configuration information indicates the LCID of the PTP. Thus, if the third dedicated RRC signaling does not include the LCID of the PTP (for example, only includes the TMGI and the MRB ID), the UE can determine the LCID of the PTP by associating it with the LCID of the PTM based on the TMGI and the MRB ID.

[0073] In other words, the network side device may implicitly indicate to the UE that the LCID of the PTP is the same as the LCID of the PTM by not carrying the LCID of the PTP in the third dedicated RRC signaling.

[0074] Alternatively, in the embodiment of the present application, when one MRB corresponds to two logical channel configuration information, if the LCID of the PTP can be 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 may implicitly indicate that the LCID of the PTP is the same as the LCID of the PTM; 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] Alternatively, in the embodiment of the present application, for the above case 4, the network side equipment may send entity configuration information to the UE through one receiving entity configuration information (for example, the second receiving entity configuration information in the embodiment of the present application), so that the UE can establish a corresponding data receiving entity according to the receiving entity configuration information and the above one logical channel configuration information.

[0076] In the embodiment of the present application, for the above case 4, the logical channel configuration information according to the embodiment of the present application may further include the following steps 204 and 205.

[0077] Step 204: the network side device sends the second receiving entity configuration information to the UE.

[0078] Step 205, the UE receives the second receiving entity configuration information sent by the network side equipment.

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

[0080] In the embodiment of the present application, the network side device may send the second receiving entity configuration information to the UE, and after the UE receives the second receiving entity configuration information, the UE can establish a corresponding data receiving entity according to the second receiving entity configuration information and the one logical channel configuration information, and can send the corresponding data to the data receiving entity when receiving the corresponding data.

[0081] It should be noted that in the embodiment of the present application, when the one logical channel configuration information includes a PTP RLC bearer configuration, the first receiving entity configuration information does not need to include a PTP RLC bearer configuration.

[0082] Optionally, in the embodiment of the present 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 the PDCP configuration may further include any other possible configurations (parameters), and may be specifically determined according to actual usage needs, and are not limited in the embodiments of the present application.

[0084] In an embodiment of the present application, a UE can obtain logical channel configuration information of a TMGI, so that when a UE is interested in a TMGI, the UE can obtain logical channel configuration information of the TMGI, such as a first configuration (PTM LCID and / or PTM RLC bearer configuration) and / or a second configuration (PTP LCID and / or PTP RLC bearer configuration), and thus the UE can receive a TMGI service based on the logical channel configuration information, thereby improving the cooperative transmission efficiency of the UE's multicast service and unicast service, and further improving the transmission efficiency of the UE's multicast service while ensuring system efficiency.

[0085] Alternatively, because of the many ways of using LCIDs in multicast services, the conventional 64 LCIDs may not be able to meet the demands of multicast services. Therefore, the network side device may configure a corresponding LCID for the UE based on the capability information of whether the UE supports an extended LCID. Based on this, the logical channel configuration method according to the embodiment of the present application may further include the following steps 206 and 207.

[0086] Step 206, after the UE enters a connected state, the UE sends logical channel extension capability information to a network side device.

[0087] Step 207: the network side equipment receives the logical channel extension capability information sent by the UE.

[0088] Here, the logical channel extension capability information is Whether the UE supports extended LCID (eLCID); The UE supports an extended LCID having a first number of bits; and that the UE supports an extended LCID of the second number of bits.

[0089] In an embodiment of the present application, after the UE enters a connected state, the UE may send the above-mentioned logical channel extension capability information to the network side equipment, and after the network side equipment receives this logical channel extension capability information in this manner, the network side equipment can configure a logical channel (e.g., a PTM LCID and / or a PTP LCID) for the UE based on the UE's logical channel extension capability.

[0090] Optionally, in the embodiment of the present application, the first bit number may be smaller than the second bit number, for example, the first bit number may be 1 bit and the second bit number may be 2 bits.

[0091] Alternatively, in the embodiment of the present application, if the UE does not support the extended LCID, the UE does not need to send the above logical channel extended capability information to the network side equipment, i.e., if the UE does not support the extended LCID, the above steps 206 and 207 do not need to be performed, thus saving resource overhead.

[0092] Optionally, in an embodiment of the present application, if the network side equipment does not receive capability information of the extended LCID reported by the UE within a predetermined time window, the network side equipment determines that the UE does not support the extended LCID.

[0093] Optionally, in the embodiment of the present application, the LCID of the PTM and the LCID of the PTP may be in different intervals depending on whether the UE supports the extended LCID.

[0094] First case: When the UE supports the extended LCID, the LCID of the PTM is within the interval range of the unextended LCID or the interval range of the extended LCID, and the LCID of the PTP is within the interval range of the unextended LCID or the interval range of the extended LCID.

[0095] Second case: When the UE does not support the extended LCID, the LCID of the PTM is within the interval range of the unextended LCID or the interval range of the extended LCID, and the LCID of the PTP is within the interval range of the unextended LCID.

[0096] It should be noted that in the embodiment of the present application, if the UE does not support the extended LCID, if the LCID of the PTM is within the range of the extended LCID, 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 not capable of processing this data, and may therefore discard this data.

[0097] Optionally, in the embodiment of the present application, the UE sends the logical channel extension capability information to the network side device, which may be predefined or instructed by the network side device, and may be specifically determined according to actual usage demand, which is not limited in the embodiment of the present application.

[0098] In an embodiment of the present application, when it is pre-defined that the UE sends the above logical channel extension capability information to the network side equipment, if the UE is interested in a multicast service (e.g., the above first TMGI) received after the UE enters a connected state, the UE will report the above logical channel extension capability information to the network side equipment after being securely activated after entering the connected state, thereby facilitating the network side equipment to quickly determine the PTM configuration and / or PTP configuration of this multicast service.

[0099] Alternatively, when the network side equipment instructs the UE to transmit the above logical channel extension capability information to the network side equipment, before the above step 206, the logical channel configuration method according to the embodiment of the present application may further include the following steps 208 and 209.

[0100] Step 208, the network side device sends a third signaling to the UE.

[0101] Step 209, the UE receives the third signaling sent by the network side equipment.

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

[0103] In an embodiment of the present application, before the UE transmits the logical channel extended capability information to the network side equipment, the network side equipment may instruct the UE to report the capability information of the extended LCID by transmitting the third signaling to the UE.

[0104] Optionally, in the embodiment of the present application, the third signaling may be common signaling or dedicated RRC signaling. Specifically, it may be determined according to actual usage demand, and is not limited in the embodiment of the present application.

[0105] In an embodiment of the present application, when the third signaling is common signaling, the network side device may indicate the third signaling together with signaling notifying that the UE needs to enter a connected state to receive a multicast service (e.g., the first TMGI), and when the third signaling is dedicated RRC signaling, after the UE reports the TMGI of interest, the network side device may instruct the UE to report capability information of the extended LCID by dedicated RRC signaling.

[0106] Optionally, in an embodiment of the present application, after the above step 201 (the UE obtains the at least one logical channel configuration information), the logical channel configuration method according to the embodiment 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 a data receiving entity for the first TMGI based on the at least one logical channel configuration information.

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

[0109] In an embodiment of the present application, one MRB of the first TMGI corresponds to one PDCP entity, and when the logical channel configuration information corresponding to the MRB indicates the LCID of a PTM, the LCID of the PTM corresponds to one PTM RLC entity, and when the logical channel configuration information corresponding to the MRB indicates the LCID of a PTP, the LCID of the PTP corresponds to one PTP RLC entity.

[0110] In an embodiment of the present application, when one MRB corresponds to two logical channel configuration information, the LCID of the PTM corresponds to this MRB (e.g., the PTM leg LCID is bound to the MRB ID), and the LCID of the PTP also corresponds to this MRB (e.g., the PTP leg LCID is bound to the MRB ID), so that the UE may establish two legs split for this MRB, and the data of the two legs may be transmitted to a common PDCP entity corresponding to the MRB.

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

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

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

[0114] In an embodiment of the present application, after the UE receives the target scheduling data, the UE can determine the LCID in the target scheduling data, and perform different operations on the target scheduling data accordingly.

[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 configuration information, the UE sends the target scheduling data to a data receiving entity of the first TMGI for processing.

[0116] In an embodiment of the present application, when the above target scheduling data is scheduling data monitored by a G-RNTI corresponding to a first TMGI, the UE can determine the RLC entity and the PDCP entity of the corresponding PTM based on the LCID in the target scheduling data, and thereby send the target scheduling data to the RLC entity and the PDCP entity of this PTM in the first TMGI for processing (e.g., operations such as reordering, repeat detection, etc.).

[0117] Correspondingly, when the above target scheduling data is the 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 configuration information, the UE can determine the RLC entity and the PDCP entity of the corresponding PTP based on the LCID in the target scheduling data, and thereby send the target scheduling data to the RLC entity and the PDCP entity of this PTP in the first TMGI for processing (e.g., operations such as reordering, repeat detection, etc.).

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

[0119] In an embodiment of the present 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, the UE does not support an extended LCID but the LCID in the target scheduling data is an LCID in an extended LCID section, the UE can determine that the LCID in the target scheduling data does not belong to an LCID supported by the UE, i.e., the LCID in the target scheduling data is an LCID domain that the UE does not recognize, so the UE may discard the target scheduling data, i.e., ignore the target scheduling data.

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

[0121] Step 301: a network side device sends at least one logical channel configuration information corresponding to a first TMGI to a UE.

[0122] Here, one piece of logical channel allocation information among the at least one piece of logical channel allocation information is A first configuration, comprising a PTM LCID and / or a PTM RLC bearer configuration; The second configuration may indicate one of the following configurations: PTP LCID and / or PTP RLC bearer configuration.

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

[0124] Optionally, in an embodiment of the present application, the first TMGI includes N MRBs, where one MRB corresponds to one logical channel configuration information or two logical channel configuration information among the at least one logical channel configuration information, and N is a positive integer.

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

[0126] Alternatively, in an embodiment of the present application, when one logical channel configuration information indicates an LCID of a PTM, the LCID of the PTM may be a target number of LCIDs indicated by a network side device in a section in which the LCID of the PTM takes a predefined value.

[0127] Here, the target number may be indicated by a first signaling, and the first signaling may be a first common signaling or a first dedicated RRC signaling.

[0128] Optionally, in the embodiment of the present application, when one piece of logical channel configuration information indicates the LCID of the PTM, the LCID of the PTM may be the LCID indicated by the network side device through the second signaling.

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

[0130] Optionally, in the embodiment of the present application, when one piece of logical channel configuration information indicates the LCID of the PTP, the LCID of the PTP may be indicated by the network side device through a third dedicated RRC signaling.

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

[0132] In an embodiment of the present application, the network side equipment can send logical channel configuration information of TMGI to the UE, so that when the UE reports that it is interested in a certain TMGI, the network side equipment can send the logical channel configuration information of this TMGI, for example, a first configuration (LCID of PTM and / or PTM RLC bearer configuration) and / or a second configuration (LCID of PTP and / or PTP RLC bearer configuration) to the UE, so that the UE can receive the TMGI service based on this logical channel configuration information, thereby improving the cooperative transmission efficiency of the multicast service and the unicast service, and further improving the transmission efficiency of the multicast service while ensuring the system efficiency.

[0133] In the following, a logical channel configuration method according to an embodiment of the present application will be illustratively described in conjunction with a specific embodiment.

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

[0135] Here, in a plurality of MRBs, the network side devices may all be configured with PTP legs, all may be configured with PTM legs, some may be configured with PTP legs and some may be configured with PTM legs, some may be configured with PTP legs and PTM legs and some may be configured with PTP legs or PTM legs.Specifically, it may be determined according to actual usage demand, and is not limited in the embodiment of the present application.

[0136] The following describes, by way of example, how to arrange an LCID in the PTM leg of an MRB, i.e., how to arrange an LCID in a PTM corresponding to an MRB.

[0137] The first method is to specify the LCID of the PTM leg in the standard (i.e., to define the LCID of the PTM leg in advance), as follows:

[0138] The standard specifies that there are a maximum of M MRBs per TMGI, where the value of M can be 2, 4, 8, 16, or any other possible value. The LCID values ​​corresponding to these M MRBs are entered into a standardized "Values ​​of LCID for DL-SCH" table, 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 taking 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 taking 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 taking 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. However, the flexibility of this method is not high. If one TMGI service does not use all M logical channels but only N (N < M) of them, the data reception entities corresponding to the extra logical channels will be wasted.

[0144] The second method is a method in which the number and values ​​of logical channels are dynamically allocated by the network side device, as follows.

[0145] The network side equipment configures the number of logical channels (i.e., the number of LCIDs of PTM) corresponding to one MRB to the UE through common signaling or dedicated signaling, and optionally, the number of configured logical channels may be within a certain range, such as [1,M], so that the UE can easily evaluate whether its own capability is sufficient to receive the data of this MRB.

[0146] The above-mentioned common signaling manner means that the network side device adopts the manner of SIB or MCCH, and all interested UEs can simultaneously receive this common signaling and the configuration information carried by this common signaling.

[0147] The above-mentioned dedicated signaling method is that after the UE enters a connected state, the network side equipment sends the configuration information corresponding to the LCID of the PTM (also called the logical channel information of the PTM) to the UE in the manner of dedicated RRC signaling. If multiple UEs need to obtain the configuration information corresponding to the LCID of the PTM, the network side equipment needs to send once for each UE in these multiple UEs.

[0148] In an embodiment of the present application, the PTM logical channel information sent by the network side device to the UE through a signaling configuration may include one or more of the following information:

[0149] 1), the number of LCIDs of PTM corresponding to one MRB, for example, MRB1 may have two logical channels, and the two LCID values ​​are taken from the remaining LCID space (for example, [35,46]) by a method of taking the default logical channel identifier value, for example, by taking two LCID values ​​from the front (35,36) or the rear (45,46) or other methods, and are the values ​​of the two logical channel identifiers corresponding to MRB1. When the UE receives this MRB1 service, it can establish two sets of data reception protocol stacks, and the 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 LCID=35 of PTM, it sends it to the first set of RLC entities+PDCP entities for processing, and when the UE receives data of LCID=36 of PTM, it sends it to the second set of RLC entities+PDCP entities for processing. Here, the parameters of the RLC entity and the PDCP entity take default formats (predefined formats), such as RLC UM mode, default RLC SN, timer length, default PDCP SN, timer length, etc.

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

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

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

[0153] In contrast to the second method, the network side device needs to consume a certain amount of signaling overhead for allocating LCIDs for PTMs, but it has high flexibility. For the receiving UE, it only needs to establish data receiving entity groups as many as the number actually allocated to the corresponding TMGI service, and the created data receiving entities will not be wasted.

[0154] Alternatively, for a TMGI service, such as a multicast service with high quality of service (QoS) demand, if the UE needs to enter a connected state to receive, the network side device may configure the LCID of the corresponding PTM for the UE based on the capability of the UE. For example, if all UEs in a group support the eLCID capability, the network side device may configure the LCID of the PTM corresponding to the MRB in the TMGI in the extended LCID range, but if at least one UE in the group does not support the eLCID capability, the network side device can only select the LCID of the PTM corresponding to the MRB in the TMGI from the conventional supported LCID range (e.g., 35 to 46).

[0155] The extended LCID may support a one-byte extended LCID or a two-byte extended LCID, and may correspond to different intervals of values. The network side device may determine which interval the LCID value of the PTM should be configured for the UE based on the capabilities of the UEs in the group and other considerations, for example as shown in Tables 2 and 3.

[0156] [Table 2]

[0157] [Table 3]

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

[0159] Alternatively, in an embodiment of the present application, since the PTM leg uses G-RNTI scheduling, but the unicast service uses C-RNTI scheduling, the LCIDs between them can be overlapped and may have overlapping values, and the UE can distinguish them by different RNTIs.

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

[0161] The PTP leg is generally configured by dedicated RRC signaling, and the PTP LCID corresponding to the PTP leg has the following two methods:

[0162] The first method: the LCID is the same as the PTM leg LCID by default (i.e., the LCID of the PTM by default). When configuring the LCID of the PTP leg (i.e., the LCID of the PTP), the network side device may indicate which PTP leg corresponds to which MRB of which TMGI service, for example, the network side device may carry the TMGI and MRB ID in the signaling, and the UE may determine the LCID of the corresponding PTM according to the TMGI and MRB ID. Of course, the network side device 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, the LCID that does not carry the PTP leg means that the LCID of the PTM leg is multiplexed.

[0163] Second type: LCID of PTP leg is explicitly configured. Since PTP leg is UE specific, network side equipment may configure it for each UE separately. For example, if a UE supports eLCID, network side equipment may configure LCID in 1 byte extension section or LCID in 2 byte extension section for this UE. Also, since PTP leg logical channel and unicast logical channel are multiplexed and transmitted (i.e., PTP leg LCID and unicast LCID are multiplexed), PTP leg LCID cannot overlap with unicast LCID. Optionally, PTP leg LCID corresponding to one MRB may be different from PTM leg LCID, so that the scheduling of multicast service and unicast service can be met at the same time.

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

[0165] It should be noted that the PTP leg of the same TMGI service may determine the corresponding common PDCP entity and the PTM leg corresponding to this PTP leg according to the configured MRB ID. For example, MRB ID=35 of TMGI 1 configures PTM leg LCID=35 and PTP leg LCID=41 or 100 (value in 1-bit extended LCID), and these two legs are simultaneously associated with one MRB ID=35 to form one split MRB.

[0166] Alternatively, in embodiment 2, the above two methods may be used simultaneously. For example, when the LCID of the PTP leg can be equal to the LCID of the PTM leg, the LCID of the PTP leg may be configured in the first method or the second method; when 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 configured in the UE in the second method.

[0167] Example 3: Reporting and use of extended LCID capabilities When there may be idle UEs receiving a broadcast or multicast service or inactive UEs receiving a broadcast or multicast service, the capability information of these UEs may not be stored in the current cell, so the network side device may not know whether each UE supports eLCID capability, whether it supports 1-byte eLCID, or whether it supports 2-byte eLCID. Therefore, the network side device and the UE may implement the following solution.

[0168] 1. The network side device places the LCID of the PTM leg corresponding to the TMGI in the conventional 6-bit range, and the remaining 6 bits are only available from 35 to 46. In this way, it is possible to ensure that all UEs can receive the PTM leg normally, regardless of the UE's capabilities.

[0169] 2. The network side device places the LCID of the PTM leg corresponding to the TMGI within the extended 1-byte eLCID range or the 2-byte eLCID range. In this way, only UEs that support the extended LCID can receive the PTM leg normally, and other UEs that do not support the extended LCID may discard the data packet if they analyze an unrecognized LCID domain.

[0170] 3. For services with low QoS requirements, the network side device may use the configuration information to indicate whether the UE should report eLCID support capability after entering a connected state, such as whether to support eLCID, and whether to report 1-byte eLCID and / or 2-byte eLCID. The configuration information may be common signaling or dedicated signaling, and the UE may report based on its own capability after receiving the configuration information, or may not report if it does not support eLCID.

[0171] 4. The network side device arranges the LCID of the PTM leg corresponding to the TMGI within the conventional 6-bit range, and only 35 to 46 are available in the remaining 6 bits. In this way, it can be ensured that all UEs can receive the PTM leg normally regardless of the UE's capabilities. The network side device may collect the capability information of the UE in the connected state, and arrange the PTP leg therefor according to the UE's capability information, where the LCID of the PTP leg may be arranged within the UE's capability range.

[0172] If a UE needs to receive a multicast service in a connected state, the UE may report eLCID capability in a connected state by default, or the network side device may instruct the UE to report eLCID capability (e.g., whether eLCID is supported, and whether 1-byte eLCID and / or 2-byte eLCID are supported) as soon as possible in a configured manner. Here, the network side device and the UE may implement the following scheme.

[0173] 1. By pre-defining, when the multicast service of interest to the UE is a multicast service that the UE receives when it enters a connected state, after the UE enters a connected state, the UE reports its own eLCID support capability as soon as possible after being safely activated, so as to facilitate the network side equipment to determine the configuration of the PTM leg and / or PTP leg.

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

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

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

[0177] 5. After receiving the eLCID capability information of each UE, the network side device may determine the configuration of the LCID of the PTM leg and / or the LCID of the PTP leg. If all UEs support eLCID, the network side device may configure the LCID of the PTM leg in the eLCID range supported by all UEs. For the configuration of the LCID of the PTP leg, the network side device may configure it within the range supported by each UE according to the difference of each UE capability. Here, the LCID of the PTP leg may be the same as or different from the LCID of the PTM leg, and the LCID of the PTP leg and the LCID of the PTM leg may be associated with each other by the MRB ID.

[0178] 6. When a UE is interested in multiple TMGI services, if the eLCID capability supported by the UE is not sufficient to configure a PTP leg for each TMGI service to ensure reception efficiency, the network side device may adopt a method of configuring only PTP legs within the capability range to the UE, where the PTP legs may be determined based on the indication order of the services of interest reported by the UE or the explicit priority among the TMGI services.

[0179] Example 4: UE 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 it is interested in and corresponding configurations, the UE may establish a corresponding data receiving entity according to these configurations, where one MRB ID corresponds to one PDCP entity, one PTM leg LCID corresponds to one configured PTM RLC entity, and one PTP leg LCID corresponds to one configured 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 split legs for one MRB, and send the data of the two legs to a common PDCP entity to perform operations such as sorting and repeat detection.

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

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

[0182] It should be noted that in the logical channel configuration method according to the embodiment of the present application, the execution body may be a logical channel configuration device or a control module for executing the logical channel configuration method in the logical channel configuration device. In the embodiment of the present application, the logical channel configuration device according to the embodiment of the present application is taken as an example to execute the logical channel configuration method by the logical channel configuration device.

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

[0184] Optionally, the first TMGI includes N MRBs, where one MRB corresponds to one logical channel configuration information or two logical channel configuration information among the at least one logical channel configuration information, and N is a positive integer, where one logical channel configuration information among the two logical channel configuration information indicates a first configuration and another logical channel configuration information indicates a second configuration.

[0185] Alternatively, one piece of logical channel configuration information indicates the LCID of the PTM, and the LCID of the PTM is all LCIDs in a section that takes on a predefined LCID value of the PTM.

[0186] Alternatively, one logical channel configuration information indicates an LCID of a PTM, where the LCID of the PTM is a target number of LCIDs indicated by a network side device in a section taking on a predefined LCID value of the PTM, where the target number is indicated by first signaling, where the first signaling is a first common signaling or a first dedicated RRC signaling.

[0187] Optionally, one logical channel configuration information indicates an LCID of a PTM, where the LCID of the PTM is an LCID indicated by the network side device through second signaling, and the second signaling is a second common signaling or a second dedicated RRC signaling.

[0188] Optionally, the logical channel configuration device may further include a receiving module, where the receiving module is used for receiving first receiving entity configuration information sent by the network side equipment, and the first receiving entity configuration information includes at least one of a PTM RLC bearer configuration and a PDCP configuration.

[0189] Optionally, one logical channel configuration information indicates an LCID of a PTP, and the LCID of the PTP is indicated by the network side device through a third dedicated RRC signaling.

[0190] Alternatively, one MRB corresponds to two logical channel configuration information, and when the LCID of the PTP is not included in the third dedicated RRC signaling, the LCID of the PTP is the same as the LCID of the PTM.

[0191] Optionally, the logical channel configuration device may further include a receiving module, where the receiving module is used for receiving second receiving entity configuration information sent by the network side equipment, and the second receiving entity configuration information includes at least one of a PTP RLC bearer configuration and a PDCP configuration.

[0192] Optionally, the logical channel configuration device may further include a sending module, and the sending module is used for sending logical channel extension capability information to a network side device after the UE enters a connected state, and the logical channel extension capability information is represented as: Whether the UE supports extended LCID; The UE supports an extended LCID having a first number of bits; and that the UE supports an extended LCID of a second number of bits.

[0193] Alternatively, when the UE supports the extended LCID, the LCID of the PTM is within the interval range of the unextended LCID or the interval range of the extended LCID, and the LCID of the PTP is within the interval range of the unextended LCID or the interval range of the extended LCID; or When the UE does not support the extended LCID, the LCID of the PTM is within the interval range of the unextended LCID or the interval range of the extended LCID, and the LCID of the PTP is within the interval range of the unextended LCID.

[0194] Optionally, the logical channel configuration device may further include a receiving module, where the receiving module is used to receive a third signaling sent by the network side equipment before the sending module sends the logical channel extended capability information to the network side equipment, and the third signaling is used to instruct the UE to report the capability information of the extended LCID.

[0195] Optionally, the logical channel configuration device may further include an establishment module, a receiving module, and a transmitting module, where the establishment module is used for establishing a data receiving entity of the first TMGI based on the at least one logical channel configuration information after the acquisition module acquires the at least one logical channel configuration information, the receiving module is used for receiving target scheduling data, and the transmitting module is used for transmitting 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 the target scheduling data is scheduling data monitored by a cell radio network temporary identifier C-RNTI of the UE, and the LCID in the target scheduling data is the LCID indicated by the logical channel configuration information.

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

[0197] An embodiment of the present application provides a logical channel configuration device, which can obtain logical channel configuration information of a TMGI, so that when a UE is interested in a TMGI, it can obtain the logical channel configuration information of the TMGI, such as a first configuration (PTM LCID and / or PTM RLC bearer configuration) and / or a second configuration (PTP LCID and / or PTP RLC bearer configuration), and thus can receive a TMGI service based on the logical channel configuration information, thereby improving the cooperative transmission efficiency of multicast services and unicast services, and further improving the transmission efficiency of multicast services while ensuring system efficiency.

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

[0199] Optionally, the first TMGI includes N MRBs, where one MRB corresponds to one logical channel configuration information or two logical channel configuration information among the at least one logical channel configuration information, and N is a positive integer, where one logical channel configuration information among the two logical channel configuration information indicates a first configuration and another logical channel configuration information indicates a second configuration.

[0200] Alternatively, one logical channel configuration information indicates an LCID of a PTM, where the LCID of the PTM is a target number of LCIDs indicated by a network side device in a section taking on a predefined LCID value of the PTM, where the target number is indicated by first signaling, where the first signaling is a first common signaling or a first dedicated RRC signaling.

[0201] Optionally, one logical channel configuration information indicates an LCID of a PTM, where the LCID of the PTM is an LCID indicated by the network side device through second signaling, and the second signaling is a second common signaling or a second dedicated RRC signaling.

[0202] Optionally, the sending module is further used for sending first receiving entity configuration information to the UE, where the first receiving entity configuration information includes a PTM RLC bearer configuration and a PDCP configuration.

[0203] Optionally, one logical channel configuration information indicates an LCID of a PTP, and the LCID of the PTP is indicated by the network side device through a third dedicated RRC signaling.

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

[0205] Optionally, the sending module is further used for sending second receiving entity configuration information to the UE, where the second receiving entity configuration information includes at least one of a PTP RLC bearer configuration and a PDCP configuration.

[0206] Optionally, the logical channel configuration device further includes a receiving module, and the receiving module is used to receive logical channel extension capability information sent by the UE before the sending module sends the logical channel configuration information to the UE, and the logical channel extension capability information is: Whether the UE supports extended LCID; The UE supports an extended LCID having a first number of bits; and that the UE supports an extended LCID of a second number of bits.

[0207] Alternatively, when the UE supports the extended LCID, the LCID of the PTM is within the interval range of the unextended LCID or the interval range of the extended LCID, and the LCID of the PTP is within the interval range of the unextended LCID or the interval range of the extended LCID; or When the UE does not support the extended LCID, the LCID of the PTM is within the interval range of the unextended LCID or the interval range of the extended LCID, and the LCID of the PTP is within the interval range of the unextended LCID.

[0208] Optionally, the transmitting module is further used for transmitting third signaling to the UE before the receiving module receives the logical channel extended capability information transmitted by the UE, the third signaling being used to instruct the UE to report the capability information of the extended LCID.

[0209] An embodiment of the present application provides a logical channel configuration device, which can send logical channel configuration information of a TMGI to a UE, so that when a UE reports that it is interested in a TMGI, it can send the logical channel configuration information of the TMGI, for example, a first configuration (PTM LCID and / or PTM RLC bearer configuration) and / or a second configuration (PTP LCID and / or PTP RLC bearer configuration) to the UE, so that the UE can receive a TMGI service based on the logical channel configuration information, thereby improving the cooperative transmission efficiency of multicast services and unicast services, and further improving the transmission efficiency of multicast services while ensuring system efficiency.

[0210] The logical channel configuration device in the embodiment of the present application may be a device, and may be a component, an integrated circuit, or a chip in a UE. The device may be a mobile UE or a non-mobile UE. Exemplarily, the mobile UE may include, but is not limited to, the types of UE 11 listed above, and the non-mobile UE may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a deposit payment machine or a self-service machine, etc., and the embodiment of the present application is not specifically limited.

[0211] The logical channel configuration device in the embodiment of the present application may be a device having an operating system, which may be an Android operating system, an ios operating system, or other possible operating systems, and the embodiment of the present application is not specifically limited.

[0212] The logical channel configuration device according to the embodiments of the present application can realize each process realized by the embodiments of the above method and achieve the same technical effects, and will not be described further here in order to avoid repetition of description.

[0213] Optionally, as shown in Fig. 7, the embodiment of the present application further provides a communication device 600, including a processor 601, a memory 602, and a program or instruction stored in the memory 602 and executable on the processor 601, for example, when the communication device 600 is a UE, when the program or instruction is executed by the processor 601, each process of the embodiment of the above logical channel configuration method can be realized, and the same technical effect can be achieved. When the communication device 600 is a network side device, when the program or instruction is executed by the processor 601, each process of the embodiment of the above logical channel configuration device method can be realized, and the same technical effect can be achieved. In order to avoid repetition, no further description will be given here.

[0214] FIG. 8 is a hardware structural schematic diagram of a UE implementing an embodiment of the present application.

[0215] The UE 100 includes components such as, but 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 can be understood by those skilled in the art, the UE 100 may further include a power source (e.g., a battery) for powering each component, and the power source may be logically connected to the processor 110 by a power management system, so that the power management system can realize functions such as charging / discharging management and power consumption management. The UE structure shown in Figure 8 does not constitute a limitation on the UE, and the UE may include more or less components than the number of components shown, or a combination of some components, or a different arrangement of components, and will not be further described here.

[0217] It should be understood that in the embodiment of the present application, the input unit 104 may include a graphics processor (GPU) 1041 and a microphone 1042, and the graphics processor 1041 processes image data of still or video images obtained by an image capture device (e.g., a camera) in a video capture mode or an image capture mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be arranged in the form of a liquid crystal display, an organic light emitting diode, and the like. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. 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, and a control lever, which will not be described further herein.

[0218] In the embodiment of the present application, the radio frequency unit 101 receives downlink data from the network side device, and then causes the processor 110 to process the data, and transmits uplink data to the network side device. In general, 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, etc.

[0219] The memory 109 may be used to store software programs or instructions and various data. The 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 instruction required for at least one function (e.g., a sound playback function, an image playback function, etc.), etc. The memory 109 may include a high-speed random access memory or a non-volatile memory, where the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. For example, the memory 109 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, where the application processor mainly processes an operating system, a user interface, and application programs or instructions, and the modem processor mainly processes wireless communication, such as a baseband processor. As can be understood, the modem processor does not have to be integrated into the processor 110.

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

[0222] Optionally, the first TMGI includes N MRBs, where one MRB corresponds to one logical channel configuration information or two logical channel configuration information among the at least one logical channel configuration information, and N is a positive integer, where one logical channel configuration information among the two logical channel configuration information indicates a first configuration and another logical channel configuration information indicates a second configuration.

[0223] Alternatively, one piece of logical channel configuration information indicates the LCID of the PTM, and the LCID of the PTM is all LCIDs in a section that takes on a predefined LCID value of the PTM.

[0224] Alternatively, one logical channel configuration information indicates an LCID of a PTM, where the LCID of the PTM is a target number of LCIDs indicated by a network side device in a section taking on a predefined LCID value of the PTM, where the target number is indicated by first signaling, where the first signaling is a first common signaling or a first dedicated RRC signaling.

[0225] Optionally, one logical channel configuration information indicates an LCID of a PTM, where the LCID of the PTM is an LCID indicated by the network side device through second signaling, and the second signaling is a second common signaling or a second dedicated RRC signaling.

[0226] Optionally, the logical channel configuration device may further include a receiving module, where the receiving module is used for receiving first receiving entity configuration information sent by the network side equipment, and the first receiving entity configuration information includes at least one of a PTM RLC bearer configuration and a PDCP configuration.

[0227] Optionally, one logical channel configuration information indicates an LCID of a PTP, and the LCID of the PTP is indicated by the network side device through a third dedicated RRC signaling.

[0228] Alternatively, one MRB corresponds to two logical channel configuration information, and when the LCID of the PTP is not included in the third dedicated RRC signaling, the LCID of the PTP is the same as the LCID of the PTM.

[0229] Optionally, the radio frequency unit is used to receive second receiving entity configuration information sent by the network side equipment, where the second receiving entity configuration information includes at least one of a PTP RLC bearer configuration and a PDCP configuration.

[0230] Optionally, the radio frequency unit may be further used for sending logical channel extension capability information to a network side device after the UE enters a connected state, and the logical channel extension capability information includes: Whether the UE supports extended LCID; The UE supports an extended LCID having a first number of bits; and that the UE supports an extended LCID of a second number of bits.

[0231] Alternatively, when the UE supports the extended LCID, the LCID of the PTM is within the interval range of the unextended LCID or the interval range of the extended LCID, and the LCID of the PTP is within the interval range of the unextended LCID or the interval range of the extended LCID; or When the UE does not support the extended LCID, the LCID of the PTM is within the interval range of the unextended LCID or the interval range of the extended LCID, and the LCID of the PTP is within the interval range of the unextended LCID.

[0232] Optionally, the radio frequency unit may be used to receive a third signaling sent by the network side equipment before the transmitting module sends the logical channel extended capability information to the network side equipment, and the third signaling is used to instruct the UE to report the capability information of the extended LCID.

[0233] Alternatively, the processor 110 may be further used for establishing a data receiving entity for the first TMGI based on the at least one logical channel configuration information after obtaining the at least one logical channel configuration information, and the radio frequency unit 101 may be further used for receiving target scheduling data, and the processor 110 may be further used for transmitting the target scheduling data to the data receiving entity for processing by the first TMGI 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 the UE, and the LCID in the target scheduling data is the LCID indicated by the logical channel configuration information.

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

[0235] An embodiment of the present application provides a UE that can obtain logical channel configuration information of a TMGI, so that when the UE is interested in a TMGI, it can obtain the logical channel configuration information of the TMGI, such as a first configuration (PTM LCID and / or PTM RLC bearer configuration) and / or a second configuration (PTP LCID and / or PTP RLC bearer configuration), and thus can receive a TMGI service based on the logical channel configuration information, thereby improving the cooperative transmission efficiency of multicast services and unicast services, and further improving the transmission efficiency of multicast services while ensuring system efficiency.

[0236] Specifically, an embodiment of the present application further provides a network side device. As shown in Fig. 9, the network side device 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 through 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, and the radio frequency device 72 processes the received information and then sends it out through the antenna 71.

[0237] The above frequency band processing device may be located in a baseband device 73, and the method performed by the network side equipment in the above embodiments 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 a plurality of chips are installed, and as shown in FIG. 9, one of the chips is, for example, a processor 74, which is connected to a memory 75, calls a program in the memory 75, and performs the operation of the network side equipment shown in the embodiment of the above method.

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

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

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

[0242] Optionally, the first TMGI includes N MRBs, where one MRB corresponds to one logical channel configuration information or two logical channel configuration information among the at least one logical channel configuration information, and N is a positive integer, where one logical channel configuration information among the two logical channel configuration information indicates a first configuration and another logical channel configuration information indicates a second configuration.

[0243] Alternatively, one logical channel configuration information indicates an LCID of a PTM, where the LCID of the PTM is a target number of LCIDs indicated by a network side device in a section taking on a predefined LCID value of the PTM, where the target number is indicated by first signaling, where the first signaling is a first common signaling or a first dedicated RRC signaling.

[0244] Optionally, one logical channel configuration information indicates an LCID of a PTM, where the LCID of the PTM is an LCID indicated by the network side device through second signaling, and the second signaling is a second common signaling or a second dedicated RRC signaling.

[0245] Optionally, the radio frequency unit 72 is further used for sending first receiving entity configuration information to the UE, where the first receiving entity configuration information includes a PTM RLC bearer configuration and a PDCP configuration.

[0246] Optionally, one logical channel configuration information indicates an LCID of a PTP, and the LCID of the PTP is indicated by the network side device through a third dedicated RRC signaling.

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

[0248] Optionally, the radio frequency unit 72 is further used to send second receiving entity configuration information to the UE, where the second receiving entity configuration information includes at least one of a PTP RLC bearer configuration and a PDCP configuration.

[0249] Optionally, the radio frequency device 72 is further used for receiving logical channel extension capability information transmitted by the UE before transmitting the logical channel configuration information to the UE, and the logical channel extension capability information is: Whether the UE supports extended LCID; The UE supports an extended LCID having a first number of bits; and that the UE supports an extended LCID of a second number of bits.

[0250] Alternatively, when the UE supports an extended LCID, the LCID of the PTM is within the interval range of the unextended LCID or the interval range of the extended LCID, and the LCID of the PTP is within the interval range of the unextended LCID or the interval range of the extended LCID; or When the UE does not support the extended LCID, the LCID of the PTM is within the interval range of the unextended LCID or the interval range of the extended LCID, and the LCID of the PTP is within the interval range of the unextended LCID.

[0251] Optionally, the radio frequency device 72 is further used to transmit a third signaling to the UE before receiving the logical channel extended capability information transmitted by the UE, the third signaling being used to instruct the UE to report the capability information of the extended LCID.

[0252] An embodiment of the present application provides a network side device, which can send logical channel configuration information of a TMGI to a UE, so that when the UE reports that it is interested in a TMGI, it can send the logical channel configuration information of the TMGI, for example, a first configuration (PTM LCID and / or PTM RLC bearer configuration) and / or a second configuration (PTP LCID and / or PTP RLC bearer configuration) to the UE, so that the UE can receive a TMGI service based on the logical channel configuration information, thereby improving the cooperative transmission efficiency of multicast service and unicast service, and further improving the transmission efficiency of multicast service while ensuring system efficiency.

[0253] The embodiments of the present application further provide a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, each process of the embodiment of the above logical channel allocation method can be realized and the same technical effect can be achieved. In order to avoid repetition, no further description will be given here.

[0254] Here, the processor is the processor in the UE in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

[0255] The embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, the processor is used to execute the program or instruction of the network side equipment, and realize each process of the embodiment of the above logical channel configuration method, and can achieve the same technical effect. In order to avoid repetition of the description, no further description will be given here.

[0256] It should be understood that the chips referred to in the embodiments of the present application may be referred to as system level chips, system chips, chip systems, or systems on chips.

[0257] It should be explained that in this specification, the terms "comprise", "include", or any other variants thereof are intended to cover the non-exclusive "comprise", whereby a process, method, article, or apparatus that includes a set of elements includes not only those elements, but also other elements not expressly listed or inherent to such process, method, article, or apparatus. In the absence of further limitations, an element limited by the phrase "comprises a" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes this element. It should be pointed out that the scope of the method and apparatus in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions in an essentially simultaneous manner or in reverse order based on the functions involved, for example, the described method can be performed in a different order than described, and various steps can be added, omitted, or combined. Also, features described with reference to some examples can be combined in other examples.

[0258] From the above description of the embodiments, it is clear to those skilled in the art that the methods of the above embodiments can be realized in the form of software and a necessary general-purpose hardware platform. Of course, they can also be realized in hardware, but in many cases the former is a more preferred embodiment. With this understanding in mind, the technical solution of the present application may be substantially or in part embodied in the form of a software product. The computer software product is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and includes some instructions for causing a UE (which may be a mobile phone, a computer, a server, an air conditioner, or a network side device, etc.) to execute the methods described in each embodiment of the present application.

[0259] The above describes the embodiments of the present application in conjunction with the drawings, but the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not limiting. Those skilled in the art can take the suggestions of this application and make many forms without departing from the spirit and scope of the claims of this application, all of which belong to the protection scope of this application. [Explanation of symbols]

[0260] 11 User Equipment (UE) 12 Network side devices 71 Antenna 72 Radio Frequency Devices 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 Sensors 106 Display unit 107 User Input Unit 108 Interface Unit 109 Memory 400 Logical channel arrangement device 401 Acquisition Module 500 Logical channel arrangement device 501 Transmitting module 600 Communication Equipment 601 Processor 602 Memory 700 Network side equipment 1041 Graphics Processor (GPU) 1042 Microphone 1061 Display Panel 1071 Touch Panel 1072 Input Device

Claims

1. A logical channel arrangement method, comprising: The user equipment UE obtains at least one logical channel configuration information corresponding to a first temporary mobility group identifier TMGI; Here, one piece of logical channel allocation information is a first arrangement, comprising a point-to-multipoint PTM logical channel identifier LCID and / or a PTM radio link control RLC bearer arrangement; A second configuration, the logical channel configuration method indicating one of a point-to-point PTP LCID and / or a PTP RLC bearer configuration.

2. The first TMGI includes N multicast radio bearer MRBs, where one MRB corresponds to one or two pieces of the at least one logical channel configuration information, where N is a positive integer; The method of claim 1 , wherein one of the two pieces of logical channel configuration information indicates the first configuration and another piece of logical channel configuration information indicates the second configuration.

3. One logical channel configuration information indicates the LCID of the PTM, The method according to claim 2 , wherein the LCIDs of the PTM are all LCIDs in an interval that takes on a predefined value of the LCID of the PTM.

4. One logical channel configuration information indicates the LCID of the PTM, 3. The method according to claim 2, wherein the LCID of the PTM is a target number of LCIDs indicated by a network side device in a section taking a value of a predefined LCID of the PTM, the target number being indicated by first signaling, the first signaling being a first common signaling or a first dedicated radio resource control (RRC) signaling.

5. One logical channel configuration information indicates the LCID of the PTM, The method according to claim 2, wherein the LCID of the PTM is an LCID indicated by a network side device through second signaling, and the second signaling is a second common signaling or a second dedicated RRC signaling.

6. The method comprises: The method of claim 3, 4 or 5, further comprising: the UE receiving first receiving entity configuration information sent by a network side equipment, the first receiving entity configuration information including at least one of a PTM RLC bearer configuration and a Packet Data Convergence Protocol (PDCP) configuration.

7. One piece of logical channel configuration information indicates the LCID of the PTP, The method according to claim 2 , wherein the LCID of the PTP is indicated by a network side device through a third dedicated RRC signaling.

8. The one MRB corresponds to the two pieces of logical channel configuration information, The method of claim 7, wherein if the third dedicated RRC signaling does not include an LCID of the PTP, the LCID of the PTP is the same as an LCID of the PTM.

9. The method comprises:

8. The method of claim 7, further comprising: the UE receiving second receiving entity configuration information sent by the network side equipment, wherein the second receiving entity configuration information includes at least one of a PTP RLC bearer configuration and a PDCP configuration.

10. The method comprises: The method further includes the UE sending logical channel extension capability information to a network side device after the UE enters a connected state, and the logical channel extension capability information includes: Whether the UE supports extended LCID; The UE supports an extended LCID of a first number of bits; and that the UE supports an extended LCID of a second number of bits.

11. If the UE supports an extended LCID, the LCID of the PTM is within the range of an unextended LCID or the range of an extended LCID, and the LCID of the PTP is within the range of an unextended LCID or the range of an extended LCID, or The method according to claim 10, wherein, when the UE does not support an extended LCID, the LCID of the PTM is within the range of an unextended LCID or the range of an extended LCID, and the LCID of the PTP is within the range of an unextended LCID.

12. Before the UE transmits the logical channel extension capability information to the network side equipment, the method further comprises: The method of claim 10, further comprising: the UE receiving third signaling sent by the network side equipment, the third signaling being used to instruct the UE to report capability information of an extended LCID.

13. After the UE obtains the at least one logical channel configuration information, the method includes: The UE establishes a data receiving entity for the first TMGI based on the at least one logical channel configuration information; receiving target scheduling data at the UE; 2. The method of claim 1, further comprising: when the target scheduling data is scheduling data monitored by a Group Radio Network Temporary Identifier G-RNTI corresponding to a first TMGI, or when the target scheduling data is scheduling data monitored by a Cell Radio Network Temporary Identifier C-RNTI of the UE and an LCID in the target scheduling data is an LCID indicated by the logical channel configuration information, the UE transmitting the target scheduling data to a data receiving entity of the first TMGI for processing.

14. The UE does not support extended LCID; After the UE receives the target scheduling data, the method comprises: The method of claim 13, further comprising: if an LCID in the target scheduling data does not belong to an LCID supported by the UE, the UE discarding the target scheduling data.

15. A logical channel arrangement method, comprising: The network side equipment transmits at least one logical channel configuration information corresponding to the first temporary mobility group identifier (TMGI) to the user equipment (UE); Here, one piece of logical channel allocation information is a first arrangement, comprising a point-to-multipoint PTM logical channel identifier LCID and / or a PTM radio link control RLC bearer arrangement; A second configuration, the logical channel configuration method indicating one of a point-to-point PTP LCID and / or a PTP RLC bearer configuration.

16. The first TMGI includes N multicast radio bearer MRBs, where one MRB corresponds to one or two pieces of the at least one logical channel configuration information, where N is a positive integer; The method of claim 15, wherein one of the two pieces of logical channel configuration information indicates the first configuration and another piece of logical channel configuration information indicates the second configuration.

17. One logical channel configuration information indicates the LCID of the PTM, 17. The method according to claim 16, wherein the LCID of the PTM is a target number of LCIDs indicated by the network side device in a section taking a value of a predefined LCID of the PTM, the target number being indicated by first signaling, the first signaling being a first common signaling or a first dedicated radio resource control (RRC) signaling.

18. One logical channel configuration information indicates the LCID of the PTM, The method according to claim 16, wherein the LCID of the PTM is an LCID indicated by a network side device through second signaling, and the second signaling is a second common signaling or a second dedicated RRC signaling.

19. The method comprises: The method according to claim 17 or 18, further comprising: the network side equipment sending first receiving entity configuration information to the UE, the first receiving entity configuration information including a PTM RLC bearer configuration and a Packet Data Convergence Protocol (PDCP) configuration.

20. One piece of logical channel configuration information indicates the LCID of the PTP, The method according to claim 16, wherein the LCID of the PTP is indicated by the network side device through a third dedicated RRC signaling.

21. The one MRB corresponds to the two pieces of logical channel configuration information, The method of claim 20, wherein if the third dedicated RRC signaling does not include an LCID of the PTP, the LCID of the PTP is the same as an LCID of the PTM.

22. The method comprises:

21. The method of claim 20, further comprising: the network side equipment sending second receiving entity configuration information to the UE, wherein the second receiving entity configuration information includes at least one of a PTP RLC bearer configuration and a PDCP configuration.

23. Before the network side equipment transmits the logical channel configuration information to the UE, the method further comprises: The method further includes receiving logical channel extension capability information sent by the UE, the logical channel extension capability information being: Whether the UE supports extended LCID; The UE supports an extended LCID of a first number of bits; and that the UE supports an extended LCID of a second number of bits.

24. If the UE supports an extended LCID, the LCID of the PTM is within the range of an unextended LCID or the range of an extended LCID, and the LCID of the PTP is within the range of an unextended LCID or the range of an extended LCID, or The method according to claim 23, wherein, when the UE does not support an extended LCID, the LCID of the PTM is within a range of an unextended LCID or within a range of an extended LCID, and the LCID of the PTP is within a range of an unextended LCID.

25. Before the network side equipment receives the logical channel extension capability information transmitted by the UE, the method includes: The method of claim 23, further comprising: the network side equipment sending a third signaling to the UE, the third signaling being used to instruct the UE to report capability information of an extended LCID.

26. A logical channel arrangement device, comprising: an acquisition module; The acquiring module is used for acquiring at least one logical channel configuration information corresponding to a first temporary mobility group identifier (TMGI); Here, one piece of logical channel allocation information is a first arrangement, comprising a point-to-multipoint PTM logical channel identifier LCID and / or a PTM radio link control RLC bearer arrangement; A logical channel configuration device, which indicates a second configuration, which is one of a point-to-point PTP LCID and / or a PTP RLC bearer configuration.

27. The first TMGI includes N multicast radio bearer MRBs, where one MRB corresponds to one or two pieces of the at least one logical channel configuration information, where N is a positive integer; 27. The apparatus of claim 26, wherein one of the two pieces of logical channel configuration information indicates the first configuration and another piece of logical channel configuration information indicates the second configuration.

28. One logical channel configuration information indicates the LCID of the PTM, The apparatus of claim 27, wherein the PTM LCIDs are all LCIDs in an interval that takes on a predefined PTM LCID value.

29. One logical channel configuration information indicates the LCID of the PTM, 28. The apparatus according to claim 27, wherein the LCID of the PTM is a target number of LCIDs indicated by a network side device in a section taking a value of a predefined LCID of the PTM, the target number being indicated by first signaling, the first signaling being a first common signaling or a first dedicated radio resource control (RRC) signaling.

30. One logical channel configuration information indicates the LCID of the PTM, The apparatus according to claim 27, wherein the LCID of the PTM is an LCID indicated by a network side device through second signaling, and the second signaling is a second common signaling or a second dedicated RRC signaling.

31. The apparatus further includes a receiving module; The device according to claim 28, 29 or 30, wherein the receiving module is used for receiving first receiving entity configuration information sent by a network side equipment, and the first receiving entity configuration information includes at least one of a PTM RLC bearer configuration and a Packet Data Convergence Protocol PDCP configuration.

32. One piece of logical channel configuration information indicates the LCID of the PTP, The apparatus according to claim 27, wherein the LCID of the PTP is indicated by a network side device through a third dedicated RRC signaling.

33. The one MRB corresponds to the two pieces of logical channel configuration information, 33. The apparatus of claim 32, wherein if the third dedicated RRC signaling does not include an LCID of the PTP, the LCID of the PTP is the same as an LCID of the PTM.

34. The apparatus further includes a receiving module; The apparatus according to claim 32, wherein the receiving module is used for receiving second receiving entity configuration information sent by the network side equipment, and the second receiving entity configuration information includes at least one of a PTP RLC bearer configuration and a PDCP configuration.

35. The apparatus further includes a transmission module; The sending module is used for sending logical channel extension capability information to a network side device after the UE enters a connected state, and the logical channel extension capability information includes: Whether the UE supports extended LCID; The UE supports an extended LCID of a first number of bits; and that the UE supports an extended LCID of a second number of bits.

36. If the UE supports an extended LCID, the LCID of the PTM is within the range of an unextended LCID or the range of an extended LCID, and the LCID of the PTP is within the range of an unextended LCID or the range of an extended LCID, or The apparatus of claim 35, wherein when the UE does not support an extended LCID, the LCID of the PTM is within a range of an unextended LCID or within a range of an extended LCID, and the LCID of the PTP is within a range of an unextended LCID.

37. The apparatus further includes a receiving module; 36. The apparatus of claim 35, wherein the receiving module is used for receiving a third signaling sent by the network side equipment before sending the logical channel extension capability information to the network side equipment, and the third signaling is used for instructing the UE to report capability information of an extended LCID.

38. The apparatus further includes an establishing module, a receiving module, and a transmitting module; The establishment module is used for establishing a data receiving entity of the first TMGI according to the at least one logical channel configuration information after obtaining the at least one logical channel configuration information; the receiving module is used for receiving target scheduling data; 27. The apparatus of claim 26, wherein the sending module is used by the UE to send the target scheduling data to a 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 a first TMGI, or when the target scheduling data is scheduling data monitored by a cell radio network temporary identifier (C-RNTI) of the UE and an LCID in the target scheduling data is an LCID indicated by the logical channel configuration information.

39. The UE does not support an extended LCID, and the apparatus further includes an execution module; The apparatus of claim 38, wherein the execution module is used by the UE to discard the target scheduling data after receiving the target scheduling data if an LCID in the target scheduling data does not belong to an LCID supported by the UE.

40. A logical channel configuration device, comprising: a transmitting module; The sending module is used for sending at least one logical channel configuration information corresponding to a first temporary mobility group identifier (TMGI) to a user equipment (UE); Here, one piece of logical channel allocation information is a first arrangement, comprising a point-to-multipoint PTM logical channel identifier LCID and / or a PTM radio link control RLC bearer arrangement; A logical channel configuration device, which indicates a second configuration, which is one of a point-to-point PTP LCID and / or a PTP RLC bearer configuration.

41. The first TMGI includes N multicast radio bearer MRBs, where one MRB corresponds to one or two pieces of the at least one logical channel configuration information, where N is a positive integer; 41. The apparatus of claim 40, wherein one of the two pieces of logical channel configuration information indicates the first configuration and another piece of logical channel configuration information indicates the second configuration.

42. One logical channel configuration information indicates the LCID of the PTM, 42. The apparatus of claim 41, wherein the PTM LCID is a target number of LCIDs indicated by a network side device in a period in which the PTM LCID value is a predefined PTM LCID value, the target number being indicated by first signaling, the first signaling being a first common signaling or a first dedicated radio resource control (RRC) signaling.

43. One logical channel configuration information indicates the LCID of the PTM, The apparatus according to claim 41, wherein the LCID of the PTM is an LCID indicated by a network side device through second signaling, and the second signaling is a second common signaling or a second dedicated RRC signaling.

44. 44. The apparatus according to claim 42 or 43, wherein the sending module is further used for sending first receiving entity configuration information to the UE, the first receiving entity configuration information including a PTM RLC bearer configuration and a Packet Data Convergence Protocol (PDCP) configuration.

45. One piece of logical channel configuration information indicates the LCID of the PTP, The apparatus of claim 41, wherein the LCID of the PTP is indicated by a network side device through a third dedicated RRC signaling.

46. The one MRB corresponds to the two pieces of logical channel configuration information, 46. ​​The apparatus of claim 45, wherein if the third dedicated RRC signaling does not include an LCID of the PTP, the LCID of the PTP is the same as an LCID of the PTM.

47. 46. ​​The apparatus of claim 45, wherein the sending module is further used for sending second receiving entity configuration information to the UE, the second receiving entity configuration information including at least one of a PTP RLC bearer configuration and a PDCP configuration.

48. The apparatus further includes a receiving module; The receiving module is used for receiving logical channel extension capability information transmitted by the UE before transmitting the logical channel configuration information to the UE, and the logical channel extension capability information includes: Whether the UE supports extended LCID; The UE supports an extended LCID of a first number of bits; and that the UE supports an extended LCID of a second number of bits.

49. If the UE supports an extended LCID, the LCID of the PTM is within the range of an unextended LCID or the range of an extended LCID, and the LCID of the PTP is within the range of an unextended LCID or the range of an extended LCID, or The apparatus of claim 48, wherein, when the UE does not support an extended LCID, the LCID of the PTM is within a range of an unextended LCID or within a range of an extended LCID, and the LCID of the PTP is within a range of an unextended LCID.

50. 49. The apparatus of claim 48, wherein the sending module is further used by the network side equipment to send third signaling to the UE before receiving the logical channel extension capability information sent by the UE, the third signaling being used to instruct the UE to report capability information of an extended LCID.

51. A user equipment (UE) comprising a processor, a memory, and a program or instructions stored in the memory and executable on the processor, the program or instructions implementing the steps of the logical channel arrangement method according to any one of claims 1 to 14 when executed by the processor.

52. A network side device comprising a processor, a memory, and a program or instructions stored in the memory and executable on the processor, the network side device realizing the steps of the logical channel arrangement method according to any one of claims 15 to 25 when the program or instructions are executed by the processor.

53. A readable storage medium having a program or instructions stored thereon, the program or instructions being executed by a processor to implement the logical channel allocation method of any one of claims 1 to 14, or to implement the steps of the logical channel allocation method of any one of claims 15 to 25.

54. A computer program product which, when executed by at least one processor, implements the steps of the logical channel allocation method according to any one of claims 1 to 25.

Images