WO2022152268A1 - 逻辑信道配置方法、装置及设备 - Google Patents

逻辑信道配置方法、装置及设备 Download PDF

Info

Publication number
WO2022152268A1
WO2022152268A1 PCT/CN2022/072134 CN2022072134W WO2022152268A1 WO 2022152268 A1 WO2022152268 A1 WO 2022152268A1 CN 2022072134 W CN2022072134 W CN 2022072134W WO 2022152268 A1 WO2022152268 A1 WO 2022152268A1
Authority
WO
WIPO (PCT)
Prior art keywords
lcid
logical channel
ptm
configuration information
ptp
Prior art date
Application number
PCT/CN2022/072134
Other languages
English (en)
French (fr)
Inventor
刘佳敏
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to KR1020237023140A priority Critical patent/KR20230113634A/ko
Priority to JP2023539914A priority patent/JP2024502423A/ja
Priority to EP22739143.0A priority patent/EP4280631A1/en
Publication of WO2022152268A1 publication Critical patent/WO2022152268A1/zh
Priority to US18/347,696 priority patent/US20230354474A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present application belongs to the field of communication technologies, and in particular relates to a logical channel configuration method, apparatus and device.
  • LTE long term evolution
  • MBMS multimedia broadcast multicast service
  • MBSN multicast broadcast single frequency network
  • SC-PTM single cell point to multipoint
  • a special logical channel identification can identify the single cell multicast control channel (single cell-multicast control channel, SC-MCCH) and single cell multicast traffic channel (single cell-multicast traffic channel) channel, SC-MTCH) to distinguish unicast services, multiple SC-MCCHs and SC-MTCHs can be distinguished by group-radio network temporary identifier (G-RNTI).
  • G-RNTI group-radio network temporary identifier
  • TMGI temporary mobile group identifier
  • MRB multicast radio bearer
  • PTM path leg
  • PTP point to point
  • the service and the unicast service coordinately perform their respective scheduling, so as to ensure the normal operation of the multicast service. Therefore, how to enable the normal scheduling of multicast services in NR has become an urgent problem to be solved.
  • Embodiments of the present application provide a logical channel configuration method, apparatus, and device, which can solve the problem of how to enable normal scheduling of multicast services in NR.
  • a first aspect provides a logical channel configuration method, the method comprising: a user equipment (user equipment, UE) acquiring at least one logical channel configuration information corresponding to a first TMGI; wherein one logical channel configuration information indicates any one of the following Configuration: first configuration: PTM LCID and/or PTM radio link control (radio link control, RLC) bearer configuration; second configuration: PTP LCID and/or PTP RLC bearer configuration.
  • a logical channel configuration method includes: a network side device sends at least one logical channel configuration information corresponding to a first TMGI to a UE; wherein one logical channel configuration information indicates any one of the following configurations: One configuration: PTM LCID and/or PTM RLC bearer configuration; Second configuration: PTP LCID and/or PTP RLC bearer configuration.
  • a logical channel configuration device in a third aspect, includes an acquisition module; the acquisition module is configured to acquire at least one logical channel configuration information corresponding to the first TMGI; wherein one logical channel configuration information indicates any one of the following configurations : first configuration: PTM LCID and/or PTM RLC bearer configuration; second configuration: PTP LCID and/or PTP RLC bearer configuration.
  • a logical channel configuration device in a fourth aspect, includes a sending module; the sending module is configured to send at least one logical channel configuration information corresponding to the first TMGI to the UE; wherein one logical channel configuration information indicates any one of the following Item configuration: first configuration: PTM LCID and/or PTM RLC bearer configuration; second configuration: PTP LCID and/or PTP RLC bearer configuration.
  • a UE in a fifth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor. The steps of implementing the method as described in the first aspect.
  • a network side device in a sixth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the The processor implements the steps of the method as described in the second aspect when executed.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect, or the The steps of the method of the second aspect.
  • a chip in an eighth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction, and implements the method described in the first aspect. the method described, or implement the method described in the second aspect.
  • the UE obtains at least one logical channel configuration information corresponding to the first TMGI; wherein, one logical channel configuration information indicates any one of the following configurations: the first configuration: the LCID of the PTM and/or the PTM RLC bearer configuration; Second configuration: PTP LCID and/or PTP RLC bearer configuration.
  • the UE can obtain the logical channel configuration information of the TMGI, when the UE is interested in a certain TMGI, the UE can obtain the logical channel configuration information of the TMGI, such as the first configuration (the LCID of the PTM and/or the RLC of the PTM) Bearer configuration) and/second configuration (PTP LCID and/or PTP RLC bearer configuration), so 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 , so that the transmission efficiency of the multicast service of the UE can be improved on the basis of ensuring the system efficiency.
  • the first configuration the LCID of the PTM and/or the RLC of the PTM) Bearer configuration
  • PTP RLC bearer configuration PTP LCID and/or PTP RLC bearer configuration
  • FIG. 1 is a block diagram of a wireless communication system provided by an embodiment of the present application.
  • FIG. 2 is one of the schematic flowcharts of a logical channel configuration method provided by an embodiment of the present application
  • FIG. 3 is a second schematic flowchart of a method for configuring a logical channel provided by an embodiment of the present application
  • FIG. 4 is a schematic diagram of a protocol stack architecture of a UE provided by an embodiment of the present application.
  • FIG. 5 is one of the schematic structural diagrams of a logical channel configuration apparatus provided by an embodiment of the present application.
  • FIG. 6 is the second schematic structural diagram of a logical channel configuration apparatus provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of hardware of a communication device provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of hardware of a UE provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of hardware of a network side device provided by an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • NR terminology is used in most of the following description, although these techniques are also applicable to applications other than NR system applications, such as 6th generation ( 6th Generation, 6G) communication system.
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes UE 11 and network side equipment 12.
  • the UE 11 may also be called a terminal device or a terminal, and the UE 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA) ), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile Internet Device (MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), pedestrian terminal ( PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • UMPC ultra-mobile personal computer
  • MID mobile Internet Device
  • MID wearable device
  • VUE vehicle-mounted device
  • PUE pedestrian terminal
  • wearable devices include: bracelets, headphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as 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 (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Send Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms.
  • the base station in the NR system is taken as an example, but the specific type of the base station is not limited.
  • the network side device may configure two paths for the UE to transmit, and the two paths include: a PTP path (PTP leg) and a PTM path (PTM leg).
  • PTP path PTP leg
  • PTM leg PTP path
  • the PTM path means that the network side equipment uses a common RNTI (such as G-RNTI) to scramble the physical downlink control channel (PDCCH), and all UEs in the group jointly monitor the scheduling of the G-RNTI, and receive In the subsequent scheduling data, the data transmitted by the PTM path at one time can be received by multiple UEs, that is, the PTM transmits data to multiple UEs at the same time, and the transmission efficiency is high.
  • PTM needs to comprehensively consider the coverage of all UEs, so the transmission parameters of PTM need to be applicable to all UEs, such as using omnidirectional antennas to consider UEs with poor link quality, etc. Therefore, for individual UEs with poor link quality, PTM may be less effective.
  • the PTP path means that the network measurement equipment uses the UE-specific cell-radio network temporary identifier (C-RNTI) to scramble the PDCCH. Only the UE can monitor the scheduling of the C-RNTI, and receive subsequent The scheduling data of the PTP path can only be received by one UE at a time, that is, the PTP path is a dedicated transmission path for one UE. Therefore, the network side device can adjust the transmission parameters according to the link quality of the UE, for example, use a directional or shaped antenna, and set appropriate transmission parameters according to the link quality of the UE, so the transmission effect for a single UE is better. However, if data needs to be transmitted to multiple UEs, multiple transmission resources are required, resulting in lower transmission efficiency.
  • C-RNTI cell-radio network temporary identifier
  • an embodiment of the present application provides a logical channel configuration method.
  • the method is executed by a UE, and the method may include the following step 201 .
  • Step 201 The UE acquires at least one logical channel configuration information corresponding to the first TMGI.
  • one logical channel configuration information in the above at least one logical channel configuration information may indicate any one of the following configurations:
  • Second configuration PTP LCID and/or PTP RLC bearer configuration.
  • the above-mentioned one logical channel configuration information refers to any one logical channel configuration information in the above-mentioned at least one logical channel configuration information.
  • the logical channel configuration information in the at least one logical channel configuration information may be the same or may be different, which may be determined according to actual use requirements. This embodiment of the present application Not limited.
  • the UE may acquire at least one logical channel configuration information corresponding to the first TMGI, and then the UE may receive the first TMGI service according to the at least one logical channel configuration information, thereby ensuring the transmission of the multicast service of the UE efficiency.
  • the above-mentioned first TMGI may be a TMGI that the UE is interested in, such as a TMGI that the UE is about to receive data.
  • the above-mentioned first TMGI may include N MRBs, and one MRB in the N MRBs may correspond to one or two logical channel configuration information in the above-mentioned at least one logical channel configuration information, and N is positive integer.
  • one of the above-mentioned two logical channel configuration information may indicate the above-mentioned first configuration (the LCID of the PTM and/or the PTM RLC bearer configuration), and the other logical channel configuration information may indicate the above-mentioned second configuration (the PTP's LCID and/or the PTM RLC bearer configuration) LCID and/or PTP RLC bearer configuration).
  • one logical channel configuration information may include TMGI information and MRB information corresponding to the logical channel, so that the UE can determine the MRB corresponding to each logical channel configuration information in the above at least one logical channel configuration information .
  • N may be any possible value such as 2, 4, 8, and 16, which may be specifically determined according to actual usage requirements, which is not limited in this embodiment of the present application.
  • the quantity of the at least one logical channel configuration information is multiple.
  • the MRB corresponds to a PTM path (PTM leg) and a PTP path (PTP leg).
  • any one of the above-mentioned at least one logical channel configuration information may be implemented in the following four cases (respectively, case 1, case 2, case 3, and case 4).
  • the configuration information is taken as an example to illustrate the logical channel configuration information involved in the embodiments of the present application.
  • the implementation manner of the other logical channel configuration information in the above at least one logical channel configuration information is similar to the implementation manner of the first logical channel configuration information described below, and to avoid repetition, it is not repeated in this embodiment of the present application.
  • Case 1 In the case that a logical channel configuration information indicates the LCID of the PTM, the LCID of the PTM may be all the LCIDs in the predefined value range of the LCID of the PTM.
  • the value interval of the LCID of the PTM can be predefined (that is, stipulated by the standard/protocol), and then the UE can determine the LCID of the PTM as the middle of the value interval according to the predefined value interval of the LCID of the PTM. All LCIDs.
  • a TMGI service may be predefined to have at most M MRBs, where M is a positive integer (for example, any possible value such as 2, 4, 8, 16, etc.), and the M MRBs corresponding to the predefined MRBs are predefined.
  • M is a positive integer (for example, any possible value such as 2, 4, 8, 16, etc.)
  • the LCID of the PTM such as [35, 35+M-1] or [46-M+1, 46]
  • the value of the LCID of the above-mentioned PTM can be all the values in [46-M+1, 46] .
  • the value range of the LCID of the PTM is the same, and different TMGIs can be distinguished by G-RNTI.
  • the UE may establish M sets of protocol stack entities for the first TMGI service (service that the UE is interested in), and each set at least includes a radio link control (radio link control, RLC) entity and a packet data convergence protocol ( packet data convergence protocol, PDCP) entity, when the UE receives the scheduling of the G-RNTI corresponding to the first TMGI, the UE can determine the first TMGI according to the G-RNTI, and then according to the media scheduled by the G-RNTI
  • RLC radio link control
  • PDCP packet data convergence protocol
  • the LCID of the PTM may be the target number of LCIDs indicated by the network side device in the predefined value range of the LCID of the PTM.
  • the above target number may be indicated by first signaling, and the first signaling may be first public signaling or first dedicated radio resource control (radio resource control, RRC) signaling.
  • first signaling may be first public signaling or first dedicated radio resource control (radio resource control, RRC) signaling.
  • RRC radio resource control
  • the network side device can indicate to the UE the number of LCIDs of the PTM of a logical channel corresponding to one MBR through the above-mentioned first signaling, so that the UE can determine the value range of the LCIDs of the PTMs from the predefined value range of the PTM. LCID of the PTM.
  • the UE may determine the LCID of the PTM from the predefined value range of the LCID of the PTM according to the predefined value method of the LCID of the PTM and according to the above target quantity.
  • the LCID value method of the above-mentioned predefined PTM can be from the value interval of the LCID of the predefined PTM from the front to the back, or it can be from the back to the value interval of the LCID of the predefined PTM. value before. Specifically, it can be determined according to actual usage requirements, which is not limited in this embodiment of the present application.
  • the LCID value of the predefined PTM can be obtained from the LCID of the predefined PTM.
  • the LCID of the PTM can be 35 and 36; in the predefined PTM LCID value method, the value can be taken from the back to the front from the predefined value interval of the PTM LCID , the LCID of the PTM can be 45 and 46.
  • the UE when the UE receives the above MRB 1, it can establish two sets of receiving protocol stacks, that is, the receiving entity established by the UE includes at least two sets of RLC+PDCP receiving entities.
  • the UE can receive the LCID of the PTM.
  • the above-mentioned first common signaling may be a system information block (system information block, SIB) manner or a multicast control channel (multicast control channel, MCCH) manner, so that all interested parties All the UEs can receive the first common signaling, so as to receive the above-mentioned target quantity, and then the UEs can obtain one logical channel configuration information.
  • SIB system information block
  • MCCH multicast control channel
  • the network side device may carry the above target number in the first dedicated RRC signaling and send it to the UE, so that the UE may obtain a logical channel configuration information.
  • the network side device may send the first dedicated signaling to each of the multiple UEs once.
  • Case 3 In the case that a 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.
  • the above-mentioned second signaling may be second public signaling or second dedicated RRC signaling.
  • the network-side device may directly indicate the LCID of the PTM to the UE through the above-mentioned second signaling, for example, the second signaling may include the LCID of the PTM.
  • the above-mentioned second public signaling may be in the form of SIB or MCCH, so that the network side device can carry the LCID of the PTM in the second public signaling and send it to the UE, so that the UE can Obtain a logical channel configuration information.
  • the network side device may carry the LCID of the PTM in the second dedicated RRC signaling and send it to the UE, so that the UE may acquire a logical channel configuration information.
  • the network side device may send the UE to the UE through configuration information of a receiving entity (for example, the configuration information of the first receiving entity in the embodiment of the present application).
  • the configuration information of the receiving entity so that the UE can establish a corresponding data receiving entity according to the configuration information of the receiving entity and the above-mentioned one logical channel configuration information.
  • the logical channel configuration method provided by the embodiment of the present application may further include the following steps 202 and 203.
  • Step 202 The network side device sends the first receiving entity configuration information to the UE.
  • Step 203 The UE receives the first receiving entity configuration information sent by the network side device.
  • the above-mentioned first receiving entity configuration information may include at least one of the following: PTM RLC bearer configuration (also referred to as PTM RLC parameters), PDCP configuration (also referred to as PDCP parameters).
  • PTM RLC bearer configuration also referred to as PTM RLC parameters
  • PDCP configuration also referred to as PDCP parameters
  • 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 configure the first receiving entity according to the first receiving entity configuration information and the above-mentioned one logical channel configuration information, and establish the corresponding data receiving entity. In this way, when the corresponding data is received, it can be sent to the data receiving entity.
  • the above-mentioned first receiving entity configuration information may not include the PTM RLC bearer configuration.
  • the above-mentioned PTM RLC bearer configuration may include a PTM RLC mode (for example, an unacknowledged mode (unacknowledged mode, UM)), a PTM RLC sequence number (sequence number, SN), and a timer length; the above-mentioned PDCP Configuration can include PDCP SN and timer length.
  • a PTM RLC mode for example, an unacknowledged mode (unacknowledged mode, UM)
  • PTM RLC sequence number sequence number, SN
  • timer length a timer length
  • the above-mentioned PDCP Configuration can include PDCP SN and timer length.
  • the PTM RLC bearer configuration and the PDCP configuration may also include any other possible configurations (parameters), which may be specifically determined according to actual usage requirements, which are not limited in the embodiments of the present application.
  • Case 4 In the case that a logical channel configuration information indicates the LCID of the PTP, the LCID of the PTP may be indicated by the network side device through the third dedicated RRC signaling.
  • the network side device may indicate the LCID of the PTP to the UE through the above-mentioned third dedicated RRC signaling.
  • the above-mentioned third signaling may include (or carry) the LCID of the PTP, the information of the TMGI and the MRB (for example, the MRB ID), so that the LCID of the PTP corresponding to the MRB can be indicated to the UE.
  • the LCID of the PTP is the same as the LCID of the PTM.
  • the LCID of the PTP may be one of the two logical channel configuration information indicating the LCID of the PTM, and the other logical channel configuration information indicating the LCID of the PTP.
  • the UE can associate with the LCID of the PTM according to the TMGI and the MRB ID, thereby determining the LCID of the PTP.
  • 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.
  • the network side device can directly indicate the LCID of the PTP through the third dedicated RRC signaling.
  • LCID can also 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 can indicate the LCID of the PTP through the third dedicated RRC signaling.
  • the network side device may send the configuration information of the receiving entity to the UE through the configuration information of a receiving entity (for example, the configuration information of the second receiving entity in the embodiment of the present application), Therefore, the UE can establish a corresponding data receiving entity according to the receiving entity configuration information and the above-mentioned one logical channel configuration information.
  • a receiving entity for example, the configuration information of the second receiving entity in the embodiment of the present application
  • the logical channel configuration information provided by the embodiment of the present application may further include the following steps 204 and 205.
  • Step 204 The network side device sends the second receiving entity configuration information to the UE.
  • Step 205 The UE receives the configuration information of the second receiving entity sent by the network side device.
  • the above-mentioned second receiving entity configuration information may include at least one of the following: PTP RLC bearer configuration, PDCP configuration.
  • 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 may configure the second receiving entity according to the second receiving entity configuration information and the above-mentioned one logical channel configuration information, and establish the corresponding data receiving entity. In this way, when the corresponding data is received, it can be sent to the data receiving entity.
  • the above-mentioned first receiving entity configuration information may not include the PTP RLC bearer configuration.
  • the above-mentioned PTP RLC bearer configuration may include a PTP RLC mode, a PTP RLC SN, and a timer length; the above-mentioned PDCP configuration may include a PDCP SN and a timer length.
  • the PTP RLC bearer configuration and the PDCP configuration may also include any other possible configurations (parameters), which may be specifically determined according to actual usage requirements, which are not limited in the embodiments of the present application.
  • the UE can obtain the logical channel configuration information of the TMGI, when the UE is interested in a certain TMGI, the UE can obtain the logical channel configuration information of the TMGI, such as the first configuration (the LCID of the PTM and/or PTM RLC bearer configuration) and/or second configuration (PTP LCID and/or PTP RLC bearer configuration), so that the UE can receive TMGI services according to the logical channel configuration information, so as to improve the cooperation between UE's multicast services and unicast services
  • the transmission efficiency can be improved, and the transmission efficiency of the multicast service of the UE can be improved on the basis of ensuring the system efficiency.
  • the network side device can configure the UE for the UE according to the capability information of whether the UE supports extended LCIDs. the corresponding LCID. Based on this, the logical channel configuration method provided by the embodiment of the present application may further include the following steps 206 and 207 .
  • Step 206 After the UE enters the connected state, the UE sends the logical channel extension capability information to the network side device.
  • Step 207 The network side device receives the logical channel extension capability information sent by the UE.
  • the above-mentioned logical channel extension capability information can be used to indicate at least one of the following:
  • extended LCID extended LCID, eLCID
  • the UE supports the extended LCID of the first bit number
  • the UE supports the extended LCID of the second number of bits.
  • the UE may send the above-mentioned logical channel extension capability information to the network-side device, so that after the network-side device receives the logical channel extension capability information, the network-side device can follow the logic of the UE.
  • Channel extension capability to configure logical channels (eg, LCID of PTM and/or LCID of PTP) to the UE.
  • the above-mentioned first number of bits may be smaller than the second number of bits.
  • the first number of bits may be 1 bit
  • the second number of bits may be 2 bits.
  • the UE may not extend the capability information to the above-mentioned logical channel of the network side device, that is, in the case that the UE does not support the extended LCID, the above steps may not be performed. 206 and step 207, so that resource overhead can be saved.
  • the network side device determines that the UE does not support the extended LCID if the network side device does not receive the capability information of the extended LCID reported by the UE within a predetermined time window.
  • whether the UE supports extended LCID, the LCID of the PTM and the LCID of the PTP may be in different intervals.
  • Case 1 When the UE supports extended LCID, the LCID of the PTM is within the range of the unextended LCID or the range of the extended LCID, and the LCID of the PTP is within the range of the unextended LCID or the range of the extended LCID Inside.
  • the second case when the UE does not support the extended LCID, the LCID of the PTM is within the range of the unextended LCID or the range of the extended LCID, and the LCID of the PTP is within the range of the unextended LCID.
  • the LCID of the PTM is within the range of the extended LCID, even if the UE parses the LCID of the PTM from a certain data, the PTM
  • the LCID is an LCID field that the UE does not know, and the UE has no ability to process the data, so it can discard the data.
  • the above-mentioned logical channel extension capability information sent by the UE to the network side device may be predefined or indicated by the network side device. Specifically, it can be determined according to actual usage requirements, which is not limited in this embodiment of the present application.
  • the UE in the case where the above-mentioned logical channel extension capability information sent by the UE to the network side device is predefined, if the UE is interested in the multicast service received after the UE enters the connected state (for example, the above-mentioned first TMGI) , the UE, after entering the connected state, reports the above-mentioned logical channel extension capability information to the network side device after security activation, so that the network side device can quickly determine the PTM configuration and/or PTP configuration of the multicast service.
  • the connected state for example, the above-mentioned first TMGI
  • the logical channel configuration method provided in this embodiment of the present application may further include the following step 208. and step 209.
  • Step 208 the third signaling sent by the network side device to the UE.
  • Step 209 The UE receives the third signaling sent by the network side device.
  • the above-mentioned third signaling may be used to instruct the UE to report capability information of the extended LCID.
  • the network-side device may send the above-mentioned third signaling to the UE, thereby instructing the UE to report the capability information of the extended LCID.
  • the above-mentioned third signaling may be public signaling, or may be dedicated RRC signaling. Specifically, it can be determined according to actual usage requirements, which is not limited in this embodiment of the present application.
  • the network-side device may combine the third signaling with a notification that the multicast service (for example, the above-mentioned first TMGI) requires the UE to enter the connected state for reception.
  • the signaling is accompanied by an indication; if the above-mentioned third signaling is dedicated RRC signaling, after the UE reports the TMGI of interest, the network side device can instruct the UE to report the capability information of the extended LCID through the dedicated RRC signaling.
  • the logical channel configuration method provided in this embodiment of the present application may further include the following steps 210 to 213, or Step 210 - Step 212 and Step 214.
  • Step 210 The UE establishes the data receiving entity of the first TMGI according to the at least one logical channel configuration information.
  • the UE may establish a data receiving entity of the first TMGI according to the at least one logical channel configuration information.
  • an MRB in the first TMGI corresponds to a PDCP entity
  • the LCID of the PTM corresponds to a PTM RLC entity
  • the LCID of the PTP corresponds to a PTP RLC entity.
  • the UE when one MRB corresponds to two logical channel configuration information, the LCID of the PTM corresponds to the MRB (for example, the PTM leg LCID is bound to the MRB ID), and the LCID of the PTP also corresponds to the MRB (for example, The PTP leg LCID is bound to the MRB ID), the UE can establish two paths of a split (split) for the MRB, and the data of the two paths can be sent to the public PDCP entity corresponding to the MRB.
  • the LCID of the PTM corresponds to the MRB
  • the LCID of the PTP also corresponds to the MRB
  • the UE can establish two paths of a split (split) for the MRB, and the data of the two paths can be sent to the public PDCP entity corresponding to the MRB.
  • Step 211 the UE receives the target scheduling data.
  • Step 212 the UE determines the LCID in the target scheduling data.
  • the UE may receive the 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 also receive the scheduling data of the C-RNTI , parse out the LCID from the MAC PDU subheader, and then determine whether the LCID is the LCID of the unicast service or the LCID of the PTP, so as to send the scheduling data to the corresponding data receiving entity.
  • the UE may determine the LCID in the target scheduling data, so as to perform different operations on the target scheduling data.
  • Step 213 when the target scheduling data is the scheduling data monitored by the G-RNTI corresponding to the first TMGI, or the 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 logical channel configuration information In the case of the indicated LCID, the UE sends the target scheduling data to the data receiving entity of the first TMGI for processing.
  • the UE may determine the RLC entity and PDCP entity of the corresponding PTM according to the LCID in the target scheduling data, thereby The target scheduling data is sent to the RLC entity and PDCP entity of the PTM in the first TMGI for processing (for example, operations such as reordering, duplication detection, etc.).
  • the UE can determine according to the LCID in the target scheduling data.
  • the RLC entity and PDCP entity of the corresponding PTP thereby sending the target scheduling data to the RLC entity and PDCP entity of the PTP in the first TMGI for processing (eg, reordering, duplication detection, etc.).
  • 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.
  • the UE after the UE receives the above-mentioned target scheduling data, if the target scheduling data does not belong to the LCID supported by the UE, for example, the UE does not support the extended LCID, and the LCID in the target scheduling data is the LCID in the extended LCID interval, Then the UE can determine that the LCID in the target scheduling data does not belong to the LCID supported by the UE, that is, the LCID in the target scheduling data is an LCID domain that the UE does not recognize, then the UE can discard the target scheduling data, that is, ignore the target scheduling data.
  • an embodiment of the present application provides a logical channel configuration method.
  • the method is performed by a network side device, and the method may include the following step 301 .
  • Step 301 The network side device sends at least one logical channel configuration information corresponding to the first TMGI to the UE.
  • one logical channel configuration information in the above at least one logical channel configuration information may indicate any one of the following configurations:
  • Second configuration PTP LCID and/or PTP RLC bearer configuration.
  • the network side device may send the 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 may, according to the at least one logical channel configuration information A corresponding data receiving entity is established, thereby ensuring the normal transmission of the TMGI service.
  • the first TMGI includes N MRBs, one MRB corresponds to one logical channel configuration information or two logical channel configuration information in the above at least one logical channel configuration information, and N is a positive integer.
  • one of the above-mentioned two logical channel configuration information indicates the above-mentioned first configuration
  • the other logical channel configuration information indicates the above-mentioned second configuration
  • the LCID of the PTM may be the target number of LCIDs indicated by the network side device in the predefined value range of the LCID of the PTM.
  • the above target number may be indicated by first signaling, and the first signaling may be first public signaling or first dedicated RRC signaling.
  • the LCID of the PTM may be the LCID indicated by the network side device through the second signaling.
  • the above-mentioned second signaling may be second public signaling or second dedicated RRC signaling.
  • the LCID of the PTP may be indicated by the network side device through the third dedicated RRC signaling.
  • the LCID of the PTP is the same as the LCID of the PTM.
  • the network-side device can send the logical channel configuration information of the TMGI to the UE, when the UE reports that it is interested in a certain TMGI, the network-side device can send the logical channel configuration information of the TMGI to the UE, For example, the first configuration (PTM LCID and/or PTM RLC bearer configuration) and/or the second configuration (PTP LCID and/or PTP RLC bearer configuration), so that the UE can receive the TMGI service according to the logical channel configuration information, thereby
  • the cooperative transmission efficiency of the multicast service and the unicast service can be improved, and the transmission efficiency of the multicast service can be improved on the basis of ensuring the system efficiency.
  • FIG. 4 a schematic diagram of a protocol stack architecture of a UE provided by an embodiment of the present application, wherein the schematic diagram of the protocol stack architecture includes only one dedicated radio bearer (DRB) and one MRB, and two schematic diagrams are shown.
  • DRB dedicated radio bearer
  • MRB multiple unicast DRBs
  • MRBs multiple MRBs corresponding to one TMGI/G-RNTI
  • TMGI/G-RNTI multiple TMGI/G-RNTIs
  • each TMGI/G-RNTI corresponding to one or more MRBs.
  • the network-side devices can be configured with PTP leg, PTM leg can be configured in all, part can be configured with PTP leg, another part can be configured with PTM leg, and a part can be configured with PTP leg and PTM leg, and the other part can be configured with PTP leg or PTM leg.
  • PTP leg can be configured in all
  • part can be configured with PTP leg
  • another part can be configured with PTM leg
  • a part can be configured with PTP leg and PTM leg
  • the other part can be configured with PTP leg or PTM leg.
  • it can be determined according to actual use requirements, which is not limited in the embodiment of the present application.
  • the following exemplarily describes how the PTM leg of the MRB configures the LCID, that is, how to configure the LCID of the PTM corresponding to the MRB.
  • the standard specifies the LCID of the PTM leg (that is, the LCID of the predefined PTM leg), the method is as follows:
  • TMGI has at most M MRBs, and the value of M can be 2, 4, 8, 16 or any other possible value.
  • M can be 2, 4, 8, 16 or any other possible value.
  • LCID values corresponding to the M MRBs in the standardized "Values of LCID for DL-SCH" table. For example, currently NR has reserved LCID values as shown in Table 1:
  • the standard may specify that the value range of the LCID is [35, 35+M-1] or [46-M+1, 46] is the LCID value of the PTM corresponding to one MRB of a TMGI service.
  • the MRB may also be a radio bearer (RB) ID value that takes a value in the value interval.
  • RB radio bearer
  • the UE can establish M sets of protocol stack entities (ie, data receiving entities) for each TMGI service it is interested in.
  • Each set of protocol stack entities includes at least the PTM RLC entity and the PDCP entity.
  • the UE can determine which TMGI service it is according to the G-RNTI, and then determine the corresponding PTM RLC entity and PDCP entity according to the LCID value carried in the MAC PDU subheader scheduled by the G-RNTI, and perform service reception processing. , and submit it to the top.
  • the value range of the logical channel (ie, the LCID of the PTM) corresponding to each TMGI service is the same, and different TMGI services can be distinguished by the G-RNTI corresponding to the TMGI.
  • the network side equipment does not need to waste signaling overhead for the LCID allocation of the PTM, but the flexibility of this method is not high. If a TMGI service does not use all M logical channels, but only needs N of them (N ⁇ M), the data receiving entity corresponding to the redundant logical channel will be wasted.
  • the second method the method of dynamically configuring the number and value of logical channels by the network side device, the method is as follows:
  • the network side device configures the UE with the number of logical channels corresponding to one MRB (that is, the number of LCIDs of the PTM) through public signaling or dedicated signaling.
  • the configured number of logical channels can be within a certain range. For example, [1, M], so as to facilitate the UE to evaluate whether its own capability is sufficient to receive the data of the MRB.
  • the above-mentioned common signaling method means that the network side equipment adopts the SIB or MCCH method, and all interested UEs can receive the common signaling and the configuration information carried by the common signaling at the same time.
  • the above-mentioned dedicated signaling method means that after the UE enters the connected state, the network side device sends the configuration information corresponding to the LCID of the PTM (which can also become the logical channel information of the PTM) in the manner of dedicated (dedicated) RRC signaling (signaling). sent to the UE. If multiple UEs need to acquire the configuration information corresponding to the LCID of the PTM, the network side device needs to send the information to each of the multiple UEs once.
  • the PTM logical channel information sent by the network side device to the UE in the form of signaling configuration may include one or more of the following information:
  • the number of LCIDs of the PTM corresponding to one MRB, for example, MRB1 can have 2 logical channels, and then cooperate with the default value method of the logical channel identifier, such as the former in the remaining LCID space (such as [35, 46]). (35, 36) or extract two LCID values from the latter (45, 46) or in other ways, as two logical channel identification values corresponding to MRB 1.
  • the UE When the UE receives the MRB 1 service, it can establish two sets of data receiving protocol stacks, and the data receiving protocol stack can contain at least two sets of RLC entities + PDCP entities.
  • the parameters of the RLC entity and the PDCP entity take the default form (predefined form), such as RLC UM mode, default RLC SN, timer length, default PDCP SN, timer length, etc.
  • the LCID of the PTM corresponding to one MRB may have 2 logical channels, the LCIDs are 37 and 38 respectively, and the different RLC parameters corresponding to LCIDs 37 and 38 respectively, and PDCP parameters, etc.
  • MRB can also be an RB ID value that takes a value in the above configuration interval, or an independently configured RB ID value.
  • the network side device may explicitly indicate the binding relationship (also referred to as an association relationship) between the RB ID and the LCID to the UE.
  • the value intervals of the logical channels of different TMGI services may be the same or different, and different TMGI services may be distinguished by the G-RNTI corresponding to the TMGI.
  • the network side equipment needs to consume a certain amount of signaling overhead for the LCID allocation of the PTM, the flexibility is high.
  • the receiving UE only the number of data receiving entities corresponding to the actual configuration of the TMGI service needs to be established. The group is enough, and the created data-receiving entity will not be wasted.
  • the network side device can configure the LCID of the corresponding PTM for the UE according to the UE's capabilities. For example, if all UEs in the group support the eLCID capability, the network side device can configure the LCID of the PTM corresponding to the MRB in the TMGI into the extended LCID range, but if at least one UE in the group does not support the eLCID capability , then the network side device can only select the LCID of the PTM corresponding to the MRB of the TMGI in the currently supported LCID interval (for example, 35-46).
  • QoS quality of service
  • the extended LCID supports a 1-byte extended LCID or a 2-byte extended LCID that can correspond to different value ranges.
  • the network side device can determine which range of PTM is configured for the UE according to the capabilities of the UEs in the group and other considerations. LCID values, as shown in Tables 2 and 3:
  • the LCID value of the PTM needs to be uniformly received by multiple UEs, no matter which configuration method is used, different UEs receive the same PTM LCID value corresponding to the same MRB for the same TMGI service.
  • the LCID between them can be reused, and there can be repeated values, and the UE can Differentiated by different RNTIs.
  • An MRB of TMGI service can be configured as only PTM leg, or only PTP leg, or both PTP leg and PTM leg.
  • Multiple MRBs of a TMGI service can be of the same configuration type, but can also be of different configuration types. For example, in a TMGI service, MRBs with high reliability requirements are configured with both PTP leg and PTM leg. Requires low MRB configuration only PTM leg, etc.
  • the PTP leg is generally configured through dedicated RRC signaling. There are two ways for the LCID of the PTP corresponding to the PTP leg:
  • the default is the same as the LCID of the PTM leg (that is, the default is the same as the LCID of the PTM).
  • the network side device can indicate which MRB of which TMGI service the PTP leg belongs to For the corresponding PTP leg, for example, the network side device can carry the TMGI and MRB ID in the signaling, and the UE can determine the LCID of the corresponding PTM according to the TMGI and MRB ID.
  • the network side device can also 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 of the PTP leg is not carried, which means that the LCID of the PTM leg is multiplexed.
  • the second way display the LCID of the configured PTP leg.
  • the network-side device can configure each UE individually. For example, a certain UE supports eLCID, and the network-side device can configure the UE for that The LCID in the 1-byte extension interval or the LCID in the 2-byte extension interval, and since the logical channel of the PTP leg and the logical channel of the unicast are multiplexed and transmitted (that is, the LCID of the PTP leg and the LCID of the unicast are multiplexed), so The LCID of the PTP leg cannot be repeated with the LCID of the unicast.
  • the LCID of the PTP leg corresponding to one MRB may be different from the LCID of the PTM leg, so that the scheduling of the multicast service and the unicast service can be satisfied at the same time.
  • the LCID of the PTM leg corresponding to TMGI1 is 35-42 (that is, the PTM leg corresponding to TMGI1 uses a total of 8 logical channels), the corresponding PTM leg of TMGI2 The LCID of the PTM leg can also be 35-42 (that is, the PTM leg corresponding to TMGI2 uses a total of 8 logical channels).
  • the two services are distinguished by the scheduling of different G-RNTIs.
  • TMGI1 corresponds to 8 PTP legs
  • LCID of the PTP leg corresponding to TMGI1 also uses 35-42
  • the LCID of the PTP leg corresponding to TMGI2 can only use the unused 43- 46, or a space with eLCID enabled. That is to say, if the same UE is configured with PTP legs corresponding to different TMGI services, the LCIDs of the PTP legs and the DRB LCIDs need to be strictly different, because both the PTP leg and the unicast service are scheduled through C-RNTI. These services need to be distinguished by different LCIDs.
  • the PTP leg of the same TMGI service can determine the corresponding common PDCP entity and the PTM leg corresponding to the PTP leg through the configured MRB ID.
  • the above two ways can be used at the same time, for example, when the LCID of the PTP leg can be equal to the LCID of the PTM leg, the first way or the second way can be used to configure the LCID of the PTP leg.
  • the second method can be used to explicitly configure the LCID of the PTP leg for the UE.
  • the network side device may not know whether each UE supports the eLCID capability, and whether it supports 1-byte (bit) eLCID or 2-byte eLCID, so the network side device and the UE can implement the following solutions:
  • the network side device configures the LCID of the PTM leg corresponding to the TMGI within the existing 6-bit (bit) range, and only 35-46 of the remaining 6 bits are available. In this way, regardless of the capabilities of the UEs, it can be ensured that all UEs can normally receive the PTM leg.
  • the network side device configures the LCID of the PTM leg corresponding to the TMGI within the range of the extended 1-byte eLCID or within the range of 2-byte eLCID. In this way, the UE that only supports the extended LCID can receive the PTM leg normally, and other UEs that do not support the extended LCID can discard the data packet when parsing to an unrecognized LCID field.
  • the network side device can indicate through the configuration information whether to report the eLCID support capability after the UE enters the connected state, such as reporting whether eLCID is supported, 1-byte eLCID and/or 2- eLCID of bytes.
  • the configuration information may be public signaling or dedicated signaling. After receiving the configuration information, the UE may report the configuration information according to its own capabilities, and may not report the configuration information if it does not support eLCID.
  • the network side device configures the LCID of the PTM leg corresponding to the TMGI within the existing 6bit range, and only 35-46 of the remaining 6bits are available. In this way, regardless of the capabilities of the UEs, it can be ensured that all UEs can normally receive the PTM leg.
  • the network side device can collect the capability information of the UE in the connected state, and configure the PTP leg for it according to the capability information of the UE, wherein the LCID of the PTP leg can be configured within the capability range of the UE.
  • the UE in the connected state can report the eLCID capability by default, or the network side device can instruct the UE to report the eLCID capability as soon as possible through configuration (for example, whether to support eLCID, support 1-byte eLCID) and/or 2-byte eLCID).
  • the network side device and the UE can implement the following solutions:
  • the UE In the case where the multicast service that the UE is interested in is the multicast service received when the UE enters the connected state, after the UE enters the connected state, the UE reports its eLCID support capability as soon as possible after the security activation, which is convenient for the network side device to determine. Configuration of PTM leg and/or PTP leg.
  • the network-side device instructs the UE to report the eLCID support capability through public signaling or dedicated signaling; for example, the network-side device instructs the UE that a certain multicast service (such as a multicast service that the UE is interested in) needs to enter the connected state in the received signaling Along with instructing the UE to report the eLCID support capability; or after the UE reports the information of the interested multicast service to the network side device, the network side device instructs the UE to report the eLCID support capability through dedicated RRC signaling.
  • a certain multicast service such as a multicast service that the UE is interested in
  • the UE does not report the capability information of the eLCID, so that certain overhead can be saved.
  • the network side device If the network side device does not receive the eLCID support capability reported by the UE within a certain time window, the network side device considers that the UE does not support eLCID.
  • the network side device can determine the configuration of the LCID of the PTM leg and/or the LCID of the PTP leg. In the case that all UEs support eLCID, the network side device can use the PTM leg.
  • the LCID is configured in the eLCID interval supported by all UEs.
  • the network side equipment can be configured within the range supported by the respective UEs according to the different capabilities of each UE. Among them, the LCID of the PTP leg can be the same as the LCID of the PTM leg, or it can be different, and the LCID of the PTP leg can be associated with the LCID of the PTM leg through the MRB ID.
  • the network side device can only configure the PTP leg within the scope of the UE configuration capability.
  • the PTP leg may be determined based on the indication sequence of the interested services reported by the UE or the priority between the explicit TMGI services.
  • Example 4 UE behavior
  • the UE can establish a corresponding data receiving entity according to these configurations, wherein one MRB ID corresponds to one PDCP entity , the LCID of a PTM leg corresponds to a configured PTM RLC entity, the LCID of a PTP leg corresponds to a configured PTP RLC entity, the MRB ID is bound to the LCID of the PTM leg, and the LCID of the PTP leg is bound to the same MRB ID, so the UE Two split legs can be established for one MRB, and the data of the two legs can be sent to a common PDCP entity for operations such as reordering and duplication detection.
  • the UE receives the scheduling data of the G-RNTI, extracts the LCID from the MAC PDU subheader, determines the corresponding PTM leg entity, and performs subsequent reception processing.
  • the UE receives the scheduling data of the C-RNTI, extracts the LCID from the MAC PDU subheader, and determines the corresponding unicast receiving entity or the receiving entity of different PTP legs of different TMGIs according to the LCID, so as to perform subsequent receiving processing.
  • the execution subject may be a logical channel configuration apparatus, or a control module in the logical channel configuration apparatus for executing the logical channel configuration method.
  • the logical channel configuration device provided by the embodiment of the present application is described by taking the logical channel configuration device executing the logical channel configuration method as an example.
  • an embodiment of the present application provides a logical channel configuration apparatus 400 , and the logical channel configuration apparatus 400 includes an acquisition module 401 .
  • the obtaining module 401 is used to obtain at least one logical channel configuration information corresponding to the first TMGI; wherein, one logical channel configuration information indicates any one of the following configurations: the first configuration: the LCID of the PTM and/or the PTM RLC bearer configuration; the second Configuration: LCID for PTP and/or PTP RLC bearer configuration.
  • the first TMGI includes N MRBs, one MRB corresponds to one logical channel configuration information or two logical channel configuration information in the at least one logical channel configuration information, and N is a positive integer; One of the logical channel configuration information indicates the first configuration, and the other logical channel configuration information indicates the second configuration.
  • one piece of logical channel configuration information indicates the LCID of the PTM, and the LCID of the PTM is all the LCIDs in the predefined value range of the LCID of the PTM.
  • a logical channel configuration information indicates the LCID of the PTM
  • the LCID of the PTM is the LCID of the target number indicated by the network side device in the pre-defined value range of the LCID of the PTM
  • the target number is indicated by the first signaling
  • the first One signaling is the first common signaling or the first dedicated RRC signaling.
  • one logical channel configuration information indicates the LCID of the PTM
  • the LCID of the PTM is the LCID indicated by the network side device through the second signaling
  • the second signaling is the second public signaling or the second dedicated RRC signaling.
  • the logical channel configuration apparatus may further include a receiving module; the receiving module is configured to receive the first receiving entity configuration information sent by the network side device, and the first receiving entity configuration information includes at least one of the following: PTM RLC bearer configuration, PDCP configuration.
  • a logical channel configuration information indicates the LCID of the PTP, and the LCID of the PTP is indicated by the network side device through the third dedicated RRC signaling.
  • one MRB corresponds to two logical channel configuration information, and in the case that 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.
  • the logical channel configuration apparatus may further include a receiving module; the receiving module is configured to receive the second receiving entity configuration information sent by the network side device, and the second receiving entity configuration information includes at least one of the following: PTP RLC bearer configuration, PDCP configuration.
  • the logical channel configuration apparatus may further include a sending module; the sending module is configured to send logical channel extension capability information to the network side device after the UE enters the connected state, where the logical channel extension capability information is used to indicate at least one of the following:
  • the UE supports the extended LCID of the first bit number
  • the UE supports the extended LCID of the second number of bits.
  • the LCID of the PTM is within the range of the unextended LCID or the range of the extended LCID
  • the LCID of the PTP is within the range of the unextended LCID or the range of the extended LCID.
  • the LCID of the PTM is within the range of the unextended LCID or the range of the extended LCID, and the LCID of the PTP is within the range of the unextended LCID.
  • the logical channel configuration apparatus may further include a receiving module; the receiving module is configured to receive the third signaling sent by the network side device before the sending module sends the logical channel extension capability information to the network side device, and the third signaling uses It is used to instruct the UE to report the capability information of the extended LCID.
  • the logical channel configuration device may further include a establishing module, a receiving module and a sending module; the establishing module is configured to, after the obtaining module obtains the at least one logical channel configuration information, establish the first TMGI according to the at least one logical channel configuration information.
  • a data receiving entity a receiving module, used for receiving target scheduling data; a sending module, used for the scheduling data monitored by the group wireless network temporary identifier G-RNTI corresponding to the first TMGI in the target scheduling data, or the target scheduling data is UE
  • the target scheduling data is sent to the data receiving entity of the first TMGI for processing .
  • the UE does not support the extended LCID; the logical channel configuration apparatus may further include an execution module; the execution module is used for, after the receiving module receives the target scheduling data, in the case that the LCID in the target scheduling data does not belong to the LCID supported by the UE , the UE discards the target scheduling data.
  • An embodiment of the present application provides a logical channel configuration device. Since the logical channel configuration information of a TMGI can be obtained, when the UE is interested in a certain TMGI, it can obtain the logical channel configuration information of the TMGI, such as the first configuration (PTM's LCID and/or PTM RLC bearer configuration) and/or second configuration (PTP LCID and/or PTP RLC bearer configuration), so that TMGI services can be received according to the logical channel configuration information, thereby improving the performance of multicast services and unicast services.
  • the cooperative transmission efficiency can improve the transmission efficiency of multicast services on the basis of ensuring system efficiency.
  • an embodiment of the present application provides a logical channel configuration apparatus 500.
  • the logical channel configuration apparatus 500 includes a sending module 501; the sending module 501 is configured to send at least one logical channel configuration information corresponding to a first TMGI to a UE ;
  • a logical channel configuration information indicates any one of the following configurations: the first configuration: the LCID of the PTM and/or the PTM RLC bearer configuration; the second configuration: the LCID of the PTP and/or the PTP RLC bearer configuration.
  • the first TMGI includes N MRBs, one MRB corresponds to one logical channel configuration information or two logical channel configuration information in the at least one logical channel configuration information, and N is a positive integer; One of the logical channel configuration information indicates the first configuration, and the other logical channel configuration information indicates the second configuration.
  • a logical channel configuration information indicates the LCID of the PTM
  • the LCID of the PTM is the LCID of the target number indicated by the network side device in the pre-defined value range of the LCID of the PTM
  • the target number is indicated by the first signaling
  • the first One signaling is the first common signaling or the first dedicated RRC signaling.
  • one logical channel configuration information indicates the LCID of the PTM
  • the LCID of the PTM is the LCID indicated by the network side device through the second signaling
  • the second signaling is the second public signaling or the second dedicated RRC signaling.
  • the sending module is further configured to send first receiving entity configuration information to the UE, where the first receiving entity configuration information includes: PTM RLC bearer configuration and PDCP configuration.
  • a logical channel configuration information indicates the LCID of the PTP, and the LCID of the PTP is indicated by the network side device through the third dedicated RRC signaling.
  • one MRB corresponds to two logical channel configuration information, and in the case that 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.
  • the sending module is further configured to send second receiving entity configuration information to the UE, where the second receiving entity configuration information includes at least one of the following: PTP RLC bearer configuration, PDCP configuration.
  • the logical channel configuration apparatus further includes a receiving module, the receiving module is configured to receive the 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 used to indicate at least the following: One:
  • the UE supports the extended LCID of the first bit number
  • the UE supports the extended LCID of the second number of bits.
  • the LCID of the PTM is within the range of the unextended LCID or the range of the extended LCID
  • the LCID of the PTP is within the range of the unextended LCID or the range of the extended LCID.
  • the LCID of the PTM is within the range of the unextended LCID or the range of the extended LCID, and the LCID of the PTP is within the range of the unextended LCID.
  • the sending module is further configured to send a third signaling to the UE before the receiving module receives the logical channel extension capability information sent by the UE, where the third signaling is used to instruct the UE to report the capability information of the extended LCID.
  • the embodiment of the present application provides a logical channel configuration device. Since the logical channel configuration information of the TMGI can be sent to the UE, when the UE reports that it is interested in a certain TMGI, the logical channel configuration information of the TMGI can be sent to the UE, For example, the first configuration (PTM LCID and/or PTM RLC bearer configuration) and/or the second configuration (PTP LCID and/or PTP RLC bearer configuration), so that the UE can receive the TMGI service according to the logical channel configuration information, thereby
  • the cooperative transmission efficiency of the multicast service and the unicast service can be improved, and the transmission efficiency of the multicast service can be improved on the basis of ensuring the system efficiency.
  • the logical channel configuration apparatus in this embodiment of the present application may be an apparatus, and may also be a component, an integrated circuit, or a chip in a UE.
  • the apparatus may be a mobile UE or a non-mobile UE.
  • the mobile UE may include, but is not limited to, the types of UE11 listed above, and the non-mobile UE may be a server, a network attached storage (NAS), a personal computer (PC), a television (television). , TV), teller machine or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the logical channel configuration device in this embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the logical channel configuration apparatus provided in the embodiment of the present application can implement the various processes implemented in the foregoing method embodiments, and achieve the same technical effect. To avoid repetition, details are not described here.
  • an embodiment of the present application further provides a communication device 600, including a processor 601, a memory 602, a program or instruction stored in the memory 602 and executable on the processor 601, for example,
  • a communication device 600 including a processor 601, a memory 602, a program or instruction stored in the memory 602 and executable on the processor 601, for example,
  • the communication device 600 is a UE
  • the program or instruction is executed by the processor 601
  • each process of the above-mentioned embodiment of the logical channel configuration method can be implemented, and the same technical effect can be achieved.
  • the communication device 600 is a network side device, when the program or instruction is executed by the processor 601, each process of the above-mentioned embodiments of the logical channel configuration apparatus method can be achieved, and the same technical effect can be achieved. To avoid repetition, details are not described here.
  • FIG. 8 is a schematic diagram of a hardware structure of a UE implementing an embodiment of the present application.
  • the UE 100 includes but is not limited to: a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 110 and other components .
  • the UE 100 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 110 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the UE structure shown in FIG. 8 does not constitute a limitation on the UE, and the UE may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or 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.
  • Other input devices 1072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which are not described herein again.
  • the radio frequency unit 101 receives the downlink data from the network side device, and then processes it to the processor 110; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 109 may be used to store software programs or instructions as well as various data.
  • the memory 109 may mainly include a storage program or instruction area and a storage data area, wherein the stored program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 109 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 110 may include one or more processing units; optionally, the processor 110 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc. Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 110 .
  • the processor 110 is configured to acquire at least one logical channel configuration information corresponding to the first TMGI; wherein, one logical channel configuration information indicates any one of the following configurations: the first configuration: the LCID of the PTM and/or the PTM RLC bearer configuration; Second configuration: PTP LCID and/or PTP RLC bearer configuration.
  • the first TMGI includes N MRBs, one MRB corresponds to one logical channel configuration information or two logical channel configuration information in the at least one logical channel configuration information, and N is a positive integer; One of the logical channel configuration information indicates the first configuration, and the other logical channel configuration information indicates the second configuration.
  • one piece of logical channel configuration information indicates the LCID of the PTM, and the LCID of the PTM is all the LCIDs in the predefined value range of the LCID of the PTM.
  • a logical channel configuration information indicates the LCID of the PTM
  • the LCID of the PTM is the LCID of the target number indicated by the network side device in the pre-defined value range of the LCID of the PTM
  • the target number is indicated by the first signaling
  • the first One signaling is the first common signaling or the first dedicated RRC signaling.
  • one logical channel configuration information indicates the LCID of the PTM
  • the LCID of the PTM is the LCID indicated by the network side device through the second signaling
  • the second signaling is the second public signaling or the second dedicated RRC signaling.
  • the logical channel configuration apparatus may further include a receiving module; the receiving module is configured to receive the first receiving entity configuration information sent by the network side device, and the first receiving entity configuration information includes at least one of the following: PTM RLC bearer configuration, PDCP configuration.
  • a logical channel configuration information indicates the LCID of the PTP, and the LCID of the PTP is indicated by the network side device through the third dedicated RRC signaling.
  • one MRB corresponds to two logical channel configuration information, and if 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.
  • the radio frequency unit is configured to receive second receiving entity configuration information sent by the network side device, where the second receiving entity configuration information includes at least one of the following: PTP RLC bearer configuration, PDCP configuration.
  • the radio frequency unit can also be used to send logical channel extension capability information to the network side device after the UE enters the connected state, where the logical channel extension capability information is used to indicate at least one of the following:
  • the UE supports the extended LCID of the first bit number
  • the UE supports the extended LCID of the second number of bits.
  • the LCID of the PTM is within the range of the unextended LCID or the range of the extended LCID
  • the LCID of the PTP is within the range of the unextended LCID or the range of the extended LCID.
  • the LCID of the PTM is within the range of the unextended LCID or the range of the extended LCID, and the LCID of the PTP is within the range of the unextended LCID.
  • the radio frequency unit can be used to receive the third signaling sent by the network side device before the sending module sends the logical channel extension capability information to the network side device, and the third signaling is used to instruct the UE to report the capability information of the extended LCID. .
  • the processor 110 may be further configured to, after acquiring at least one logical channel configuration information, establish a data receiving entity of the first TMGI according to the at least one logical channel configuration information; the radio frequency unit 101 may also be configured to receive target scheduling data, the processor 110 can also be used for the scheduling data monitored by the group wireless network temporary identifier G-RNTI corresponding to the target scheduling data for the first TMGI, or the cell wireless network temporary identifier C-RNTI where the target scheduling data is the UE When the monitored scheduling data and the LCID in the target scheduling data is the LCID indicated by the logical channel configuration information, the target scheduling data is sent to the data receiving entity of the first TMGI for processing.
  • the UE does not support the extended LCID; the logical channel configuration apparatus may further include an execution module; the execution module is used for, after the receiving module receives the target scheduling data, in the case that the LCID in the target scheduling data does not belong to the LCID supported by the UE , the UE discards the target scheduling data.
  • An embodiment of the present application provides a UE. Since the logical channel configuration information of a TMGI can be obtained, when the UE is interested in a certain TMGI, it can obtain the logical channel configuration information of the TMGI, such as the first configuration (the LCID of the PTM and/or the logical channel configuration information of the TMGI). or PTM RLC bearer configuration) and/second configuration (PTP LCID and/or PTP RLC bearer configuration), so that TMGI services can be received according to the logical channel configuration information, thereby improving the cooperative transmission efficiency of multicast services and unicast services. , thereby improving the transmission efficiency of multicast services on the basis of ensuring system efficiency.
  • the network side device 700 includes: an antenna 71 , a radio frequency device 72 , and a baseband device 73 .
  • the antenna 71 is connected to the radio frequency device 72 .
  • the radio frequency device 72 receives information through the antenna 71, and sends the received information to the baseband device 73 for processing.
  • the baseband device 73 processes the information to be sent and sends it to the radio frequency device 72, and the radio frequency device 72 processes the received information and sends it out through the antenna 71.
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 73 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 73 .
  • the baseband apparatus 73 includes a processor 74 and a memory 75 .
  • the baseband device 73 may include, for example, at least one baseband board on which a plurality of chips are arranged. As shown in FIG. 9 , one of the chips is, for example, the processor 74 , which is connected to the memory 75 to call the program in the memory 75 and execute it.
  • the network-side device shown in the above method embodiments operates.
  • the baseband device 73 may further include a network interface 76 for exchanging information with the radio frequency device 72, and the interface is, for example, a common public radio interface (CPRI for short).
  • CPRI common public radio interface
  • the network-side device in this embodiment of the present invention further includes: instructions or programs that are stored in the memory 75 and run on the processor 74, and the processor 74 invokes the instructions or programs in the memory 75 to execute the modules shown in FIG. 6 .
  • the radio frequency device 72 is configured to send at least one logical channel configuration information corresponding to the first TMGI to the UE; wherein, one logical channel configuration information indicates any one of the following configurations: the first configuration: the LCID of the PTM and/or the PTM RLC bearer configuration; Second configuration: PTP LCID and/or PTP RLC bearer configuration.
  • the first TMGI includes N MRBs, one MRB corresponds to one logical channel configuration information or two logical channel configuration information in the at least one logical channel configuration information, and N is a positive integer; One of the logical channel configuration information indicates the first configuration, and the other logical channel configuration information indicates the second configuration.
  • a logical channel configuration information indicates the LCID of the PTM
  • the LCID of the PTM is the LCID of the target number indicated by the network side device in the pre-defined value range of the LCID of the PTM
  • the target number is indicated by the first signaling
  • the first One signaling is the first common signaling or the first dedicated RRC signaling.
  • one logical channel configuration information indicates the LCID of the PTM
  • the LCID of the PTM is the LCID indicated by the network side device through the second signaling
  • the second signaling is the second public signaling or the second dedicated RRC signaling.
  • the radio frequency device 72 is further configured to send first receiving entity configuration information to the UE, where the first receiving entity configuration information includes: PTM RLC bearer configuration and PDCP configuration.
  • a logical channel configuration information indicates the LCID of the PTP, and the LCID of the PTP is indicated by the network side device through the third dedicated RRC signaling.
  • one MRB corresponds to two logical channel configuration information, and in the case that 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.
  • the radio frequency apparatus 72 is further configured to send second receiving entity configuration information to the UE, where the second receiving entity configuration information includes at least one of the following: PTP RLC bearer configuration, PDCP configuration.
  • the radio frequency device 72 is configured to, before sending the logical channel configuration information to the UE, receive the logical channel extension capability information sent by the UE, where the logical channel extension capability information is used to indicate at least one of the following:
  • the UE supports the extended LCID of the first bit number
  • the UE supports the extended LCID of the second number of bits.
  • the LCID of the PTM is within the range of the unextended LCID or the range of the extended LCID
  • the LCID of the PTP is within the range of the unextended LCID or the range of the extended LCID.
  • the LCID of the PTM is within the range of the unextended LCID or the range of the extended LCID, and the LCID of the PTP is within the range of the unextended LCID.
  • the radio frequency apparatus 72 is further configured to send a third signaling to the UE before receiving the logical channel extension capability information sent by the UE, where the third signaling is used to instruct the UE to report the capability information of the extended LCID.
  • This embodiment of the present application provides a network-side device. Since the logical channel configuration information of the TMGI can be sent to the UE, when the UE reports that it is interested in a TMGI, the logical channel configuration information of the TMGI can be sent to the UE, 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), so that the UE can receive the TMGI service according to the logical channel configuration information, so that it can The cooperative transmission efficiency of the multicast service and the unicast service is improved, so that the transmission efficiency of the multicast service can be improved on the basis of ensuring the system efficiency.
  • the first configuration PTM LCID and/or PTM RLC bearer configuration
  • PTP RLC bearer configuration the second configuration
  • the cooperative transmission efficiency of the multicast service and the unicast service is improved, so that the transmission efficiency of the multicast service can be improved on the basis of ensuring the system efficiency
  • the embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the above-mentioned embodiment of the logical channel configuration method is implemented, and can achieve the same The technical effect, in order to avoid repetition, will not be repeated here.
  • the processor is the processor in the UE in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used for running a network-side device program or instruction to implement each process of the above-mentioned embodiment of the logical channel configuration method, and The same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • the methods of the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course hardware can also be used, but in many cases the former is better implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a UE (which may be a mobile phone, a computer, a server, an air conditioner, or a network side device, etc.) execute the methods described in the various embodiments of this application.
  • a storage medium such as ROM/RAM, magnetic disk, CD-ROM

Landscapes

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

Abstract

本申请公开了一种逻辑信道配置方法、装置及设备。该方法包括：UE获取第一TMGI对应的至少一个逻辑信道配置信息；其中，一个逻辑信道配置信息指示以下任意一项配置：第一配置：PTM的LCID和/或PTM RLC承载配置；第二配置：PTP的LCID和/或PTP RLC承载配置。

Description

逻辑信道配置方法、装置及设备
相关申请的交叉引用
本申请主张在2021年01月15日在中国提交的中国专利申请号202110057653.3的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种逻辑信道配置方法、装置及设备。
背景技术
在长期演进(long term evolution，LTE)的广播多播传输中，支持以多播/组播单频网络(multicast broadcast single frequency network，MBSN)方式发送多媒体广播多播业务(multimedia broadcast multicast service，MBMS)，以单小区点对多点(single cell point to multipoint，SC-PTM)方式发送多播业务。其中，对于MBSFN方式，由于多播业务有完全独立于单播的传输信道和传输时域位置，因此不需要考虑逻辑信道重叠的问题；对于SC-PTM方式，在LTE中只为多播业务分配了一个特殊的逻辑信道标识(logical channel identification，LCID)，该LCID可以标识单小区多播控制信道(single cell-multicast control channel，SC-MCCH)和单小区多播业务信道(single cell-multicast traffic channel，SC-MTCH)，以区分单播业务，多个SC-MCCH和SC-MTCH内部可以通过群组无线网络临时标识(group-radio network temporary identifier，G-RNTI)区分。
然而，新空口(new radio，NR)的多播传输比LTE的多播传输复杂，在NR中，一个临时移动群组标识(temporary mobile group identifier，TMGI)业务可能对应多个逻辑信道，且一个TMGI中的多播无线承载(multicast radio bearer，MRB)有可能同时配置PTM路径(leg)和点对点(point to point，PTP)路径，而PTM leg和PTP leg的合理配置可以保证NR中的多播业务和单播业务协调地进行各自的调度，从而保证多播业务的正常工作。因此，在NR中如何使得多播业务能够正常调度成为一个亟待解决的问题。
发明内容
本申请实施例提供一种逻辑信道配置方法、装置及设备，能够解决在NR中如何使得多播业务能够正常调度的问题。
为了解决上述技术问题，本申请是这样实现的：
第一方面，提供了一种逻辑信道配置方法，该方法包括：用户设备(user equipment，UE)获取第一TMGI对应的至少一个逻辑信道配置信息；其中，一个逻辑信道配置信息指示以下任意一项配置：第一配置：PTM的LCID和/或PTM无线链路控制(radio link control，RLC)承载配置；第二配置：PTP的LCID和/或PTP RLC承载配置。
第二方面，提供了一种逻辑信道配置方法，该方法包括：网络侧设备向UE发送第一TMGI对应的至少一个逻辑信道配置信息；其中，一个逻辑信道配置信息指示以下任意一项配置：第一配置：PTM的LCID和/或PTM RLC承载配置；第二配置：PTP的LCID和/或PTP RLC承载配置。
第三方面，提供了一种逻辑信道配置装置，该装置包括获取模块；获取模块，用于获取第一TMGI对应的至少一个逻辑信道配置信息；其中，一个逻辑信道配置信息指示以下任意一项配置：第一配置：PTM的LCID和/或PTM RLC承载配置；第二配置：PTP的LCID和/或PTP RLC承载配置。
第四方面，提供了一种逻辑信道配置装置，该装置包括发送模块；发送模块，用于向UE发送第一TMGI对应的至少一个逻辑信道配置信息；其中，一个逻辑信道配置信息指示以下任意一项配置：第一配置：PTM的LCID和/或PTM RLC承载配置；第二配置：PTP的LCID和/或PTP RLC承载配置。
第五方面，提供了一种UE，该UE包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种网络侧设备，该网络侧设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第七方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处 理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第八方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现如第一方面所述的方法，或实现如第二方面所述的方法。
在本申请实施例中，UE获取第一TMGI对应的至少一个逻辑信道配置信息；其中，一个逻辑信道配置信息指示以下任意一项配置：第一配置：PTM的LCID和/或PTM RLC承载配置；第二配置：PTP的LCID和/或PTP RLC承载配置。通过该方案，由于UE可以获取TMGI的逻辑信道配置信息，因此当UE对某个TMGI感兴趣时，UE可以获取该TMGI的逻辑信道配置信息，比如第一配置(PTM的LCID和/或PTM RLC承载配置)和/第二配置(PTP的LCID和/或PTP RLC承载配置)，如此UE可以根据该逻辑信道配置信息接收TMGI业务，从而可以提升UE的多播业务和单播业务的协作传输效率，进而可以在保证系统效率的基础上，提升UE的多播业务的传输效率。
附图说明
图1是本申请实施例提供的一种无线通信系统的框图；
图2是本申请实施例提供的逻辑信道配置方法的流程示意图之一；
图3是本申请实施例提供的逻辑信道配置方法的流程示意图之二；
图4是本申请实施例提供的UE的一种协议栈架构示意图；
图5是本申请实施例提供的一种逻辑信道配置装置的结构示意图之一；
图6是本申请实施例提供的一种逻辑信道配置装置的结构示意图之二；
图7是本申请实施例提供的一种通信设备的硬件示意图；
图8是本申请实施例提供的UE的硬件示意图；
图9是本申请实施例提供的网络侧设备的硬件示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，尽管这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括UE 11和网络侧设备12。其中，UE 11也可以称作终端设备或者终端，UE 11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定UE 11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域 中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
本申请实施例中，对于一个多播业务(例如TMGI业务)，网络侧设备可以为UE配置两条路径进行传输，该两条路径包括：PTP路径(PTP leg)和PTM路径(PTM leg)。
其中，PTM路径是指网络侧设备使用公共的RNTI(例如G-RNTI)对物理下行控制信道(physical downlink control channel，PDCCH)加扰，组内所有的UE共同监听G-RNTI的调度，并接收其后的调度数据，PTM路径一次传输的数据可以被多个UE接收，即PTM是同时向多个UE传输数据的，传输效率较高。但PTM需要综合考虑对所有UE的覆盖，因此PTM的传输参数需要适用于所有UE，例如使用全向天线，以考虑链路质量较差的UE等，因此对于个别链路质量较差的UE，PTM的效果可能较差。
PTP路径是指网络测设备使用UE专用的小区无线网络临时标识(cell-radio network temporary identifier，C-RNTI)对PDCCH加扰，只有该UE可以监听到该C-RNTI的调度，并接收其后的调度数据，PTP路径一次传输的数据只能被一个UE接收，即PTP路径是一个UE的专属传输路径。因此网络侧设备可以根据该UE的链路质量，调整发送参数，例如使用定向或者赋形天线，根据该UE的链路质量设置适合的传输参数，因此对单个UE的传输效果较好。但是如果需要向多个UE传输数据，那么需要多个传输资源，从而导致传输效率较低。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的逻辑信道配置方法进行详细地说明。
如图2所示，本申请实施例提供一种逻辑信道配置方法，该方法由UE执行，该方法可以包括下述的步骤201。
步骤201、UE获取第一TMGI对应的至少一个逻辑信道配置信息。
其中，上述至少一个逻辑信道配置信息中的一个逻辑信道配置信息可以指示以下任意一项配置：
第一配置：PTM的LCID和/或PTM RLC承载配置；
第二配置：PTP的LCID和/或PTP RLC承载配置。
需要说明的是，本申请实施例中，上述一个逻辑信道配置信息是指上述至少一个逻辑信道配置信息中的任意一个逻辑信道配置信息。其中，在该至少一个逻辑信道配置信息的数量为多个的情况下，该至少一个逻辑信道配置信息中的逻辑信道配置信息可能相同也可能不同，具体可以根据实际使用需求确定，本申请实施例不作限定。
本申请实施例中，UE可以获取上述第一TMGI对应的至少一个逻辑信道配置信息，然后UE可以根据该至少一个逻辑信道配置信息，接收第一TMGI业务，从而可以保证UE的多播业务的传输效率。
本申请实施例中，上述第一TMGI可以为UE感兴趣的TMGI，比如UE即将接收数据的TMGI。
可选地，本申请实施例中，上述第一TMGI可以包含N个MRB，该N个MRB中的一个MRB可以对应上述至少一个逻辑信道配置信息中的一个或两个逻辑信道配置信息，N为正整数。
其中，上述两个逻辑信道配置信息中的一个逻辑信道配置信息可以指示上述第一配置(PTM的LCID和/或PTM RLC承载配置)，另一个逻辑信道配置信息可以指示上述第二配置(PTP的LCID和/或PTP RLC承载配置)。
本申请实施例中，一个逻辑信道配置信息中可以包含该逻辑信道对应的TMGI的信息和MRB的信息，从而UE可以确定上述至少一个逻辑信道配置信息中的每个逻辑信道配置信息所对应的MRB。
可选地，本申请实施例中，N可以为2、4、8、16等任意可能的数值，具体可以根据实际使用需求确定，本申请实施例不做限定。
需要说明的是，在上述一个MRB对应上述至少一个逻辑信道配置信息中的两个逻辑信道配置信息的情况下，该至少一个逻辑信道配置信息的数量为多个。
另外，在一个MRB对应上述两个逻辑信道配置信息的情况下，那么该MRB对应有PTM路径(PTM leg)和PTP路径(PTP leg)。
本申请实施例中，上述至少一个逻辑信道配置信息中的任意一个逻辑信道配置信息均可以以下述四种情况(分别为情况一、情况二、情况三和情况四)实现，下面以一个逻辑信道配置信息为例，对本申请实施例中涉及的逻辑信道配置信息进行示例性的说明。
对于上述至少一个逻辑信道配置信息中的其它逻辑信道配置信息的实现方式，与下述的第一逻辑信道配置信息的实现方式类似，为避免重复，本申请实施例不与赘述。
情况一：在一个逻辑信道配置信息指示PTM的LCID的情况下，该PTM的LCID可以为预定义的PTM的LCID的取值区间中的全部LCID。
对于上述情况一，可以预定义(即标准规定/协议规定)PTM的LCID的取值区间，那么UE可以根 据预定义的PTM的LCID的取值区间，确定PTM的LCID为该取值区间的中全部LCID。
可选地，本申请实施例中，可以预定义一个TMGI业务最多有M个MRB，M为正整数(例如2、4、8、16等任意可能的数值)，并预定义该M个MRB对应的PTM的LCID，例如[35，35+M-1]或者[46-M+1，46]，那么上述一个PTM的LCID的取值可以为[46-M+1，46]中的全部数值。
可以理解，在上述情况一中，对于不同的TMGI，PTM的LCID的取值区间是相同的，不同的TMGI之间可以通过G-RNTI区分。
对于上述情况一，UE可以为第一TMGI业务(UE感兴趣的业务)，都建立M套协议栈实体，每套至少包含无线链路控制(radio link control，RLC)实体和分组数据汇聚协议(packet data convergence protocol，PDCP)实体，当UE接收到上述第一TMGI对应的G-RNTI的调度时，UE可以根据该G-RNTI，确定是该第一TMGI，然后再根据G-RNTI调度的媒体接入控制(medium access control，MAC)协议数据单元(protocol data unit，PDU)子头(subheader)中携带的LCID，从该M套协议栈实体确定对应的RLC实体和PDCP实体，进行业务接收处理，并递交高层。
本申请实施例中，对于情况一，由于PTM的LCID为预定义的，因此无需网络侧设备对PTM的LCID分配额外的信令，从而可以节省网络侧设备的信令开销。
情况二：在一个逻辑信道配置信息指示PTM的LCID的情况下，该PTM的LCID可以为预定义的PTM的LCID的取值区间中，网络侧设备指示的目标数量的LCID。
其中，上述目标数量可以通过第一信令指示，该第一信令可以为第一公共信令或第一专用无线资源控制(radio resource control，RRC)信令。
在上述情况二中，网络侧设备可以通过上述第一信令，向UE指示一个MBR对应的一个逻辑信道的PTM的LCID的数量，从而UE可以从预定义的PTM的LCID的取值区间中确定PTM的LCID。
可选地，本申请实施例中，UE可以按照预定义的PTM的LCID取值方式，根据上述目标数量，从预定义的PTM的LCID的取值区间，确定PTM的LCID。
可选地，上述预定义的PTM的LCID取值方式可以为从预定义的PTM的LCID的取值区间从前向后取值，也可以为从预定义的PTM的LCID的取值区间从后向前取值。具体可以根据实际使用需求确定，本申请实施例不做限定。
示例性地，假设上述预定义的PTM的LCID的取值区间为[35，46]，上述目标数量为2，那么在预定义的PTM的LCID取值方式可以为从预定义的PTM的LCID的取值区间从前向后取值的情况下，PTM的LCID可以为35和36；在预定义的PTM的LCID取值方式可以为从预定义的PTM的LCID的取值区间从后向前取值的情况下，PTM的LCID可以为45和46。如此，当UE接收上述MRB 1时，可以建立2套接收协议栈，即UE建立的接收实体至少包含两套RLC+PDCP接收实体，在G-RNTI的调度下，UE可以将接收到PTM的LCID＝35的数据发送到第一套RLC+PDCP接收实体进行处理，将接收到LCID＝36的数据发送到第二套RLC+PDCP接收实体进行处理。
可选地，本申请实施例中，上述第一公共信令可以为系统信息块(system information block，SIB)的方式或多播控制信道(multicast control channel，MCCH)的方式，如此所有感兴趣地UE均可以接收到该第一公共信令，从而可以接收到上述目标数量，进而UE可以获取到一个逻辑信道配置信息。
本申请实施例中，在UE进入连接态之后，网络侧设备可以将上述目标数量携带在第一专用RRC信令中发送给UE，从而UE可以获取到一个逻辑信道配置信息。对于该第一专用RRC信令，如果多个UE需要获取该一个逻辑信道配置信息，那么网络侧设备可以向该多个UE中的每个UE发送一次该第一专用信令。
情况三：在一个逻辑信道配置信息指示PTM的LCID的情况下，该PTM的LCID可以为网络侧设备通过第二信令指示的LCID。
其中，上述第二信令可以为第二公共信令或第二专用RRC信令。
对于上述情况三，网络侧设备可以直接通过上述第二信令，向UE指示PTM的LCID，比如该第二信令中可以包含PTM的LCID。
可选地，本申请实施例中，上述第二公共信令可以为SIB的方式或MCCH的方式，从而网络侧设备可以将PTM的LCID携带在第二公共信令中发送给UE，以使得UE获取到一个逻辑信道配置信息。
本申请实施例中，在UE进入连接态之后，网络侧设备可以将PTM的LCID携带在第二专用RRC信令中发送给UE，从而UE可以获取到一个逻辑信道配置信息。
示例性地，本申请实施例中，假设MRB 2对应的PTM的LCID为37和38，那么网络侧设备可以将PTM的LCID＝37和PTM的LCID＝38携带在第二信令中发送给UE，以使得UE可以获取到MRB 2对应的逻辑信道配置信息。
可选地，本申请实施例中，对于上述情况一、情况二和情况三，网络侧设备可以通过一个接收实体配置信息(例如本申请实施例中的第一接收实体配置信息)，向UE发送接收实体的配置信息，从而UE可以根据该接收实体配置信息和上述一个逻辑信道配置信息，建立对应的数据接收实体。
本申请实施例中，对于上述情况一、情况二和情况三，本申请实施例提供的逻辑信道配置方法还可以包括下述的步骤202和步骤203。
步骤202、网络侧设备向UE发送第一接收实体配置信息。
步骤203、UE接收网络侧设备发送的第一接收实体配置信息。
其中，上述第一接收实体配置信息可以包括以下至少一项：PTM RLC承载配置(也可以称为PTM RLC参数)、PDCP配置(也可以称为PDCP参数)。
本申请实施例中，网络侧设备可以向UE发送上述第一接收实体配置信息，在UE接收到该第一接收实体配置信息之后，UE可以根据该第一接收实体配置信息和上述一个逻辑信道配置信息，建立相应的数据接收实体。如此，在接收到对应的数据时，可以发送至该数据接收实体。
需要说明的是，本申请实施例中，在上述一个逻辑信道配置信息包括PTM RLC承载配置的情况下，上述第一接收实体配置信息可以不包括PTM RLC承载配置。
可选地，本申请实施例中，上述PTM RLC承载配置可以包括PTM RLC模式(例如非确认模式(unacknowledged mode，UM))，PTM RLC序列号(sequence number，SN)，定时器长度；上述PDCP配置可以包括PDCP SN和定时器长度。
当然，实际实现时，PTM RLC承载配置和PDCP配置还可以包括其他任意可能的配置(参数)，具体可以根据实际使用需求确定，本申请实施例不做限定。
情况四：在一个逻辑信道配置信息指示PTP的LCID的情况下，该PTP的LCID可以为网络侧设备通过第三专用RRC信令指示的。
对于上述情况四，网络侧设备可以通过上述第三专用RRC信令，向UE指示PTP的LCID。
本申请实施例中，上述第三信令中可以包含(或携带)PTP的LCID，TMGI和MRB的信息(例如MRB ID)，从而可以向UE指示该MRB对应的PTP的LCID。
可选地，本申请实施例中，若一个MRB对应两个逻辑信道配置信息，则在上述第三专用RRC信令中不包含PTP的LCID的情况下，PTP的LCID与PTM的LCID相同。
可以理解，上述PTP的LCID可以为上述两个逻辑信道配置信息中的一个逻辑信道配置信息指示PTM的LCID，另一个逻辑信道配置信息指示PTP的LCID。如此，当该上述第三专用RRC信令中不包含PTP的LCID(例如仅包含TMGI和MRB ID)时，UE可以根据该TMGI和MRB ID关联到该PTM的LCID，从而确定PTP的LCID。
也就是说，网络侧设备可以通过不在第三专用RRC信令中携带PTP的LCID的方式，隐式地向UE指示PTP的LCID与PTM的LCID相同。
可选地，本申请实施例中，在一个MRB对应两个逻辑信道配置信息的情况下，若PTP的LCID可以等于PTM的LCID，则网络侧设备可以通过第三专用RRC信令直接指示PTP的LCID，也可以隐式地指示PTP的LCID与PTM的LCID相同；若PTP的LCID不等于PTM的LCID，则网络侧设备可以通过第三专用RRC信令指示PTP的LCID。
可选地，本申请实施例中，对于上述情况四，网络侧设备可以通过一个接收实体配置信息(例如本申请实施例中的第二接收实体配置信息)，向UE发送接收实体的配置信息，从而UE可以根据该接收实体配置信息和上述一个逻辑信道配置信息，建立对应的数据接收实体。
本申请实施例中，对于上述情况四，本申请实施例提供的逻辑信道配置信息还可以包括下述的步骤204和步骤205。
步骤204、网络侧设备向UE发送第二接收实体配置信息。
步骤205、UE接收网络侧设备发送的第二接收实体配置信息。
其中，上述第二接收实体配置信息可以包括以下至少一项：PTP RLC承载配置、PDCP配置。
本申请实施例中，网络侧设备可以向UE发送上述第二接收实体配置信息，在UE接收到该第二接收实体配置信息之后，UE可以根据该第二接收实体配置信息和上述一个逻辑信道配置信息，建立相应的数据接收实体。如此，在接收到对应的数据时，可以发送至该数据接收实体。
需要说明的是，本申请实施例中，在上述一个逻辑信道配置信息包括PTP RLC承载配置的情况下，上述第一接收实体配置信息可以不包括PTP RLC承载配置。
可选地，本申请实施例中，上述PTP RLC承载配置可以包括PTP RLC模式，PTP RLC SN，定时器长度；上述PDCP配置可以包括PDCP SN和定时器长度。
当然，实际实现时，PTP RLC承载配置和PDCP配置还可以包括其他任意可能的配置(参数)，具体可以根据实际使用需求确定，本申请实施例不做限定。
本申请实施例中，由于UE可以获取TMGI的逻辑信道配置信息，因此当UE对某个TMGI感兴趣时，UE可以获取该TMGI的逻辑信道配置信息，比如第一配置(PTM的LCID和/或PTM RLC承载配置)和/第二配置(PTP的LCID和/或PTP RLC承载配置)，如此UE可以根据该逻辑信道配置信息接收TMGI业务，从而可以提升UE的多播业务和单播业务的协作传输效率，进而可以在保证系统效率的基础上，提升UE的多播业务的传输效率。
可选地，由于多播业务的LCID的使用方式较多，因此传统的64个LCID可能无法满足多播业务的使用需求，因此网络侧设备可以根据UE是否支持扩展LCID的能力信息，为UE配置相应的LCID。基于此，本申请实施例提供的逻辑信道配置方法还可以包括下述的步骤206和步骤207。
步骤206、在UE进入连接态之后，UE向网络侧设备发送逻辑信道扩展能力信息。
步骤207、网络侧设备接收UE发送的逻辑信道扩展能力信息。
其中，上述逻辑信道扩展能力信息可以用于指示以下至少一项：
UE是否支持扩展LCID(extended LCID，eLCID)；
UE支持第一比特数的扩展LCID；
UE支持第二比特数的扩展LCID。
本申请实施例中，在UE进入连接态之后，UE可以向网络侧设备发送上述逻辑信道扩展能力信息，如此在网络侧设备接收到该逻辑信道扩展能力信息之后，网络侧设备可以根据UE的逻辑信道扩展能力，向UE配置逻辑信道(例如PTM的LCID和/或PTP的LCID)。
可选地，本申请实施例中，上述第一比特数可以小于第二比特数。例如第一比特数可以为1比特，第二比特数可以为2比特。
可选地，本申请实施例中，在UE不支持扩展LCID的情况下，UE可以不向网络侧设备上述逻辑信道扩展能力信息，即在UE不支持扩展LCID的情况下，可以不执行上述步骤206和步骤207，如此可以节省资源开销。
可选地，本申请实施例中，若网络侧设备在预定时间窗口内，未接收到UE上报的扩展LCID的能力信息，则网络侧设备确定UE不支持扩展LCID。
可选地，本申请实施例中，UE是否支持扩展LCID，PTM的LCID和PTP的LCID可能处于不同的区间。
第一种情况：在UE支持扩展LCID的情况下，PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，PTP的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内。
第二种情况：在UE不支持扩展LCID的情况下，PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，PTP的LCID处于未扩展LCID的区间范围内。
需要说明的是，本申请实施例中，在UE不支持扩展LCID的情况下，如果PTM的LCID处于扩展LCID的区间范围内，那么即使UE从某一数据中解析出该PTM的LCID，该PTM的LCID对于UE来说是不认识的LCID域，UE没有能力处理该数据，从而可以丢弃该数据。
可选地，本申请实施例中，UE向网络侧设备发送上述逻辑信道扩展能力信息可以为预定义的，也可以为网络侧设备指示的。具体可以根据实际使用需求确定，本申请实施例不做限定。
本申请实施例中，在UE向网络侧设备发送上述逻辑信道扩展能力信息为预定义的情况下，若UE感兴趣的是在UE进入连接态之后接收的多播业务(例如上述第一TMGI)，则UE在进入连接态之后，在安全激活之后向网络侧设备上报上述逻辑信道扩展能力信息，从而便于网络侧设备快速确定该多播业务的PTM配置和/或PTP配置。
可选地，在UE向网络侧设备发送上述逻辑信道扩展能力信息为网络侧设备指示的情况下，在上述步骤206之前，本申请实施例提供的逻辑信道配置方法还可以包括下述的步骤208和步骤209。
步骤208、网络侧设备向UE发送的第三信令。
步骤209、UE接收网络侧设备发送的第三信令。
其中，上述第三信令可以用于指示UE上报扩展LCID的能力信息。
本申请实施例中，在UE向网络侧设备发送上述逻辑信道扩展能力信息之前，网络侧设备可以向UE发送上述第三信令，从而指示UE上报扩展LCID的能力信息。
可选地，本申请实施例中，上述第三信令可以为公共信令，也可以为专用RRC信令。具体可以根据实际使用需求确定，本申请实施例不做限定。
本申请实施例中，在上述第三信令为公共信令的情况下，网络侧设备可以将该第三信令与通知多播 业务(例如上述第一TMGI)需要UE进入连接态进行接收的信令一起伴随指示；在上述第三信令为专用RRC信令的情况下，在UE上报了感兴趣的TMGI之后，网络侧设备可以通过专用RRC信令指示UE上报扩展LCID的能力信息。
可选地，本申请实施例中，在上述步骤201(UE获取上述至少一个逻辑信道配置信息)之后，本申请实施例提供的逻辑信道配置方法还可以包括下述的步骤210-步骤213，或步骤210-步骤212和步骤214。
步骤210、UE根据上述至少一个逻辑信道配置信息，建立上述第一TMGI的数据接收实体。
本申请实施例中，在UE获取到上述第一TMGI对应的至少一个逻辑信道配置信息之后，UE可以根据该至少一个逻辑信道配置信息，建立第一TMGI的数据接收实体。
本申请实施例中，第一TMGI中的一个MRB对应一个PDCP实体，在MRB对应的逻辑信道配置信息指示的PTM的LCID的情况下，该PTM的LCID对应一个PTM RLC实体；在MRB对应的逻辑信道配置信息指示的PTP的LCID的情况下，该PTP的LCID对应一个PTP RLC实体。
本申请实施例中，在一个MRB对应两个逻辑信道配置信息的情况下，通过PTM的LCID与该MRB对应(例如PTM leg LCID与MRB ID绑定)，PTP的LCID也与该MRB对应(例如PTP leg LCID与MRB ID绑定)，UE可以为该MRB建立一个分叉(split)的两个路径，该两个路径的数据可以发送给MRB对应的公共PDCP实体。
步骤211、UE接收目标调度数据。
步骤212、UE确定目标调度数据中的LCID。
本申请实施例中，UE可以接收G-RNTI的调度数据，从MAC PDU subheader中解析出PTM的LCID，并将该调度数据发送至对应的数据接收实体；UE也可以接收C-RNTI的调度数据，从MAC PDU subheader中解析出LCID，然后再确定该LCID是单播业务的LCID，还是PTP的LCID，以将该调度数据发送至对应的数据接收实体。
本申请实施例中，在UE接收到上述目标调度数据之后，UE可以确定该目标调度数据中的LCID，从而对目标调度数据执行不同的操作。
步骤213、在目标调度数据为第一TMGI对应的G-RNTI监听到的调度数据，或目标调度数据为UE的C-RNTI监听到的调度数据、且目标调度数据中的LCID为逻辑信道配置信息指示的LCID的情况下，UE将目标调度数据，发送至第一TMGI的数据接收实体进行处理。
本申请实施例中，在上述目标调度数据为第一TMGI对应的G-RNTI监听到的调度数据情况下，UE可以根据目标调度数据中的LCID，确定对应的PTM的RLC实体和PDCP实体，从而将目标调度数据发送至第一TMGI中的该PTM的RLC实体和PDCP实体进行处理(例如重排序、重复检测等操作)。
相应的，在上述目标调度数据为UE的C-RNTI监听到的调度数据、且目标调度数据中的LCID为逻辑信道配置信息指示的LCID的情况下，UE可以根据目标调度数据中的LCID，确定对应的PTP的RLC实体和PDCP实体，从而将目标调度数据发送至第一TMGI中的该PTP的RLC实体和PDCP实体进行处理(例如重排序、重复检测等操作)。
步骤214、在目标调度数据中的LCID不属于UE支持的LCID的情况下，UE丢弃目标调度数据。
本申请实施例中，在UE接收到上述目标调度数据之后，如果该目标调度数据不属于UE支持的LCID，例如UE不支持扩展LCID，而目标调度数据中的LCID为扩展LCID区间中的LCID，那么UE可以确定目标调度数据中的LCID不属于UE支持的LCID，即目标调度数据中的LCID为UE不认识的LCID域，那么UE可以丢弃目标调度数据，即忽略目标调度数据。
如图3所示，本申请实施例提供一种逻辑信道配置方法，该方法由网络侧设备执行，该方法可以包括下述的步骤301。
步骤301、网络侧设备向UE发送第一TMGI对应的至少一个逻辑信道配置信息。
其中，上述至少一个逻辑信道配置信息中的一个逻辑信道配置信息可以指示以下任意一项配置：
第一配置：PTM的LCID和/或PTM RLC承载配置；
第二配置：PTP的LCID和/或PTP RLC承载配置。
本申请实施例中，网络侧设备可以向UE发送上述第一TMGI对应的至少一个逻辑信道配置信息，从而在UE接收到该至少一个逻辑信道配置信息之后，UE可以根据该至少一个逻辑信道配置信息建立对应的数据接收实体，从而可以保证TMGI业务的正常传输。
可选地，本申请实施例中第一TMGI包含N个MRB，一个MRB对应上述至少一个逻辑信道配置信息中的一个逻辑信道配置信息或两个逻辑信道配置信息，N为正整数。
其中，上述两个逻辑信道配置信息中的一个逻辑信道配置信息指示上述第一配置，另一个逻辑信道配置信息指示上述第二配置。
可选地，本申请实施例中，在一个逻辑信道配置信息指示PTM的LCID的情况下，PTM的LCID可以为预定义的PTM的LCID的取值区间中，网络侧设备指示的目标数量的LCID。
其中，上述目标数量可以通过第一信令指示，该第一信令可以为第一公共信令或为第一专用RRC信令。
可选地，本申请实施例中，在一个逻辑信道配置信息指示PTM的LCID的情况下，PTM的LCID可以为网络侧设备通过第二信令指示的LCID。
其中，上述第二信令可以为第二公共信令或第二专用RRC信令。
可选地，本申请实施例中，在一个逻辑信道配置信息指示PTP的LCID的情况下，PTP的LCID可以为网络侧设备通过第三专用RRC信令指示的。
可选地，本申请实施例中，若一个MRB对应两个逻辑信道配置信息，则在第三专用RRC信令不包含PTP的LCID的情况下，PTP的LCID与PTM的LCID相同。
本申请实施例中，由于网络侧设备可以向UE发送TMGI的逻辑信道配置信息，因此当UE上报了其对某个TMGI感兴趣时，网络侧设备可以向UE发送该TMGI的逻辑信道配置信息，比如第一配置(PTM的LCID和/或PTM RLC承载配置)和/第二配置(PTP的LCID和/或PTP RLC承载配置)，如此可以使得UE能够根据该逻辑信道配置信息接收TMGI业务，从而可以提升多播业务和单播业务的协作传输效率，进而可以在保证系统效率的基础上，提升多播业务的传输效率。
下面在结合具体的实施例，对本申请实施例提供的逻辑信道配置方法进行示例性地说明。
实施例1：配置PTM的方式
如图4所示，为本申请实施例提供的UE的一种协议栈架构示意图，其中该协议栈架构示意图中仅包括一个专用无线承载(dedicated radio bearer，DRB)和一个MRB，并示意了二者之间的协议栈关联性。在实际中，UE可以有多个单播DRB，也可以有一个TMGI/G-RNTI对应的多个MRB，甚至可以有多个TMGI/G-RNTI，每个TMGI/G-RNTI对应一个或者多个MRB。
其中，在多个MRB中，网络侧设备可以全部配置PTP leg，可以全部配置PTM leg，可以一部分部分配置PTP leg，另一部分配置PTM leg，还可以一部分配置PTP leg和PTM leg，另一部分配置PTP leg或PTM leg。具体可以根据实际使用需求确定，本申请实施例不作限定。
下面示例性地说明MRB的PTM leg如何配置LCID，即如何配置MRB对应的PTM的LCID。
第一种方式：标准中规定PTM leg的LCID(即预定义PTM leg的LCID)，方法如下：
标准规定一个TMGI最多有M个MRB，M的取值可以为2，4，8，16或者其它任意可能的值。将该M个MRB对应的LCID值，写在标准化的“Values of LCID for DL-SCH”表格中，例如目前NR有如表1所示的预留LCID值：
35-46 预留(reserved)
表1
标准可以规定LCID的取值区间为[35，35+M-1]或者[46-M+1，46]为一个TMGI业务的一个MRB对应的PTM的LCID值。同时，MRB和逻辑信道(logical channel，LCH)之间一一对应，即MRB也可以为在该取值区间取值的无线承载(RB)ID值。
对于UE接收调度数据，UE可以为其感兴趣的每个TMGI业务，都建立M套协议栈实体(即数据接收实体)，每套协议栈实体至少包含PTM RLC实体和PDCP实体，当UE接收到一个G-RNTI的调度时，UE可以根据G-RNTI确定是哪个TMGI业务，再根据G-RNTI调度的MAC PDU subheader中携带的LCID值，确定对应的PTM RLC实体和PDCP实体，进行业务接收处理，并递交高层。
在第一种方式中，每个TMGI业务对应的逻辑信道(即PTM的LCID)的取值区间是一样的，不同TMGI业务之间可以以TMGI对应的G-RNTI区分。
对于第一种方式，网络侧设备不需要为PTM的LCID分配浪费信令开销，但是该方式的灵活度不高，如果一个TMGI业务没有将M个逻辑信道全部使用，而只需要其中的N个(N<M)，则多余的逻辑信道对应的数据接收实体将被浪费。
第二种方式：网络侧设备动态配置逻辑信道个数和取值的方法，方法如下：
网络侧设备通过公共信令或者专用信令的方式，向UE配置一个MRB对应的逻辑信道个数(即PTM的LCID的数量)，可选地，配置的逻辑信道个数可以处于一定范围内，例如[1，M]，从而便于UE评估自身的能力是否足够接收该MRB的数据。
上述公共信令的方式是指网络侧设备采取SIB或者MCCH的方式，所有感兴趣的UE可以同时接收 到该公共信令和该公共信令携带的配置信息。
上述专用信令的方式是指，在UE进入连接态之后，网络侧设备以dedicated(专用)RRC signaling(信令)的方式将PTM的LCID对应的配置信息(也可以成为PTM的逻辑信道信息)发送给UE。如果多个UE需要获取PTM的LCID对应的配置信息，则网络侧设备需要向该多个UE中的每个UE发送一次。
本申请实施例中，网络侧设备以信令配置的方式，向UE发送的PTM逻辑信道信息可以包含下述一种或多种信息：
1)、一个MRB对应的PTM的LCID的个数，例如MRB1可以有2个逻辑信道，再配合默认的逻辑信道标识的取值方法，例如剩余LCID空间(比如[35，46])中从前的(35，36)或者从后的(45，46)或者按照其它方式取出两个LCID值，作为MRB 1对应的两个逻辑信道标识值。当UE接收该MRB 1业务时，可以建立2套数据接收协议栈，该数据接收协议栈至少可以包含两套RLC实体+PDCP实体，在MRB 1的TMGI对应的G-RNTI 1的调度下，若UE接收到PTM的LCID＝35的数据，则发送到第一套RLC实体+PDCP实体进行处理；若UE接收到PTM的LCID＝36的数据，则发送到第二套RLC实体+PDCP实体进行处理。其中RLC实体和PDCP实体的参数采取默认形式(预定义的形式)，例如RLC UM模式，默认的RLC SN、定时器长度，默认的PDCP SN、定时器长度等。
2)、一个MRB对应的PTM的LCID，例如MRB 1可以有2个逻辑信道，LCID分别为37和38，以及LCID 37和38分别对应的不同的RLC参数，以及PDCP参数等。
其中，MRB和LCH之间一一对应，即MRB也可以是在上述配置区间取值的RB ID值，或者独立配置RB ID取值。其中，网络侧设备可以向UE显式地指示RB ID和LCID之间的绑定关系(也可以称为关联关系)。
在第二种方式中，不同TMGI业务的逻辑信道的取值区间可以相同也可以不同，不同TMGI业务之间可以以TMGI对应的G-RNTI区分。
对于上述第二种方式，虽然网络侧设备需要为PTM的LCID分配消耗一定的信令开销，但是灵活度高，对于接收UE来说，只需建立对应TMGI业务实际配置的个数的数据接收实体组即可，不会浪费创建的数据接收实体。
可选地，如果TMGI业务需要UE进入连接态进行接收，例如具有高服务质量(quality of service，QoS)需求多播业务，网络侧设备可以根据UE的能力为UE配置响应的PTM的LCID。比如，如果群组中的所有UE都支持eLCID能力，那么网络侧设备可以将TMGI中的MRB对应的PTM的LCID配置到扩展LCID的区间中，但是如果群组中至少有一个UE不支持eLCID能力，那么网络侧设备只能在现有支持的LCID区间(例如35-46)中选择TMGI的MRB对应的PTM的LCID。
扩展LCID支持1个字节的扩展LCID或者2个字节的扩展LCID可以对应不同的取值区间，网络侧设备可以根据组内UE的能力和其它考虑，确定给UE配置在哪个区间的PTM的LCID值，如表2和表3所示：
码点(codepoint) 索引(index) LCID值
[0，(2 16-1)] [320，(2 16+319)] LCID
表2
码点(codepoint) 索引(index) LCID值
[0，244] [64，308] LCID
表3
因为PTM的LCID值需要被多个UE统一接收的，因此无论是哪种配置方式，不同UE接收到针对同一个TMGI业务的同一个MRB对应的PTM LCID值相同。
可选地，本申请实施例中，由于PTM leg使用G-RNTI调度，而单播(unicast)业务使用C-RNTI调度，他们之间的LCID是可以重复使用的，可以有重复数值，UE可以通过不同的RNTI区分。
实施例2：配置PTP的方式
TMGI业务的一个MRB可以配置为only PTM leg，或者only PTP leg，或者both PTP leg and PTM leg。一个TMGI业务的多个MRB可以是相同的配置类型，但也可以是不同的配置类型，例如，在一个TMGI 业务中，对可靠性要求高的MRB配置了both PTP leg and PTM leg，对可靠性要求低的MRB配置only PTM leg等。
PTP leg一般是通过专用RRC信令来进行配置，PTP leg对应的PTP的LCID有两种方式：
第一种方式：默认与PTM leg的LCID相同(即默认与PTM的LCID)，在配置PTP leg的LCID(即PTP的LCID)时，网络侧设备可以指示该PTP leg是哪个TMGI业务的哪个MRB对应的PTP leg，比如网络侧设备可以在信令中携带TMGI和MRB ID，UE可以根据TMGI和MRB ID确定对应的PTM的LCID。当然，网络侧设备也可以隐式或者显式的向UE指示PTP leg的LCID与PTM leg的LCID相同，例如不携带PTP leg的LCID，则意味着复用PTM leg的LCID。
第二种方式：显示配置PTP leg的LCID，由于PTP leg是UE专用的(specific)，网络侧设备可以对每个UE可以单独配置，例如某个UE支持eLCID，网络侧设备可以给该UE配置1字节扩展区间内的LCID或者2字节扩展区间内的LCID，另外由于PTP leg的逻辑信道与unicast的逻辑信道是复用传输的(即PTP leg的LCID与unicast的LCID复用)，因此PTP leg的LCID是与unicast的LCID之间不能重复。可选地，一个MRB对应的PTP leg的LCID和PTM leg的LCID可以不同，从而可以同时满足多播业务和单播业务的调度。
示例性地，单播DL-SCH LCID中剩余的只有35-46这个区间，如果TMGI1对应的PTM leg的LCID为35-42(即TMGI1对应的PTM leg共使用8个逻辑信道)，TMGI2对应的PTM leg的LCID也可以为35-42(即TMGI2对应的PTM leg共使用8个逻辑信道)，这俩业务之间是通过不同G-RNTI的调度来区分的。但是如果TMGI1对应的8个PTP leg，且TMGI1对应的PTP leg的LCID也使用35-42，那么在TMGI2对应8个PTP leg的情况，TMGI2对应的PTP leg的LCID只能使用未使用的43-46，或者启用eLCID的空间。也就是说，如果给同一个UE配置不同的TMGI业务对应的PTP leg，那么PTP leg的LCID之间以及与DRB LCID之间需要严格不同，因为PTP leg和单播业务均通过C-RNTI调度，这些业务之间需要通过不同的LCID来区分。
需要说明的是，同一个TMGI业务的PTP leg可以通过配置的MRB ID，确定对应的common PDCP实体，以及该PTP leg对应的PTM leg。例如TMGI 1的MRB ID＝35，配置了PTM leg的LCID＝35，并配置了PTP leg的LCID＝41 or 100(1比特的扩展LCID中的取值)，通过这两个leg同时关联到一个MRB ID＝35，形成了一个split的MRB。
可选地，在实施例2中，上述两种方式可以同时使用，例如在PTP leg的LCID可以等于PTM leg的LCID的情况下，可以采用第一种方式或第二种方式配置PTP leg的LCID，在PTP leg的LCID不等于PTM leg的LCID的情况下，可以采用第二种方式为UE显式配置PTP leg的LCID。
实施例3：扩展LCID能力的上报和使用
当一个广播(broadcast)或者多播(multicast)业务可能存在空闲(Idle)态UE接收或非激活(Inactive)态UE接收时，由于当前小区并不一定存储有这些UE的能力信息，因此网络侧设备可能无法知道每个UE是否支持eLCID的能力，以及支持1-byte(比特)的eLCID，还是2-byte的eLCID，因此网络侧设备和UE可以执行下述方案：
1.网络侧设备将TMGI对应的PTM leg的LCID配置在现有的6比特(bit)范围内，该6bit中剩余的只有35-46可用。如此，无论UE的能力如何，都可以确保所有UE能够正常接收PTM leg。
2.网络侧设备将TMGI对应的PTM leg的LCID配置在扩展的1-byte eLCID的范围之内或者2-byte eLCID的范围之内。如此，仅支持扩展LCID的UE可以正常的接收PTM leg，其它不支持扩展LCID的UE在解析到不认识的LCID域时，可以将数据包丢掉。
3.对于QoS要求不高的业务，网络侧设备可以通过配置信息指示在UE进入连接态后，是否进行eLCID支持能力的上报，例如上报是否支持eLCID，支持1-byte的eLCID和/或2-byte的eLCID。该配置信息可以是公共信令也可以是专用信令，UE在接收到该配置信息之后，可以根据自身的能力进行上报，如果不支持eLCID，也可以不上报。
4.网络侧设备将TMGI对应的PTM leg的LCID配置在现有的6bit范围内，该6bit中剩余的只有35-46可用。如此，无论UE的能力如何，都可以确保所有UE能够正常接收PTM leg。网络侧设备可以收集处于连接态的UE的能力信息，并根据UE的能力信息为其配置PTP leg，其中可以将PTP leg的LCID配置在UE的能力范围之内。
当一个multicast业务需要UE在连接态下进行接收时，可以默认连接态的UE上报eLCID能力，或者网络侧设备可以通过配置的方式指示UE尽快上报eLCID能力(比如是否支持eLCID，支持1-byte eLCID和/或2-byte eLCID)。其中，网络侧设备和UE可以执行下述方案：
1.预定义：在UE感兴趣的multicast业务是在UE进入连接态接收的multicast业务的情况下，在UE 进入连接态之后，UE安全激活后尽快上报自身的eLCID支持能力，便于网络侧设备确定PTM leg和/或PTP leg的配置。
2.网络侧设备通过公共信令或者专用信令指示UE上报eLCID支持能力；例如，网络侧设备在指示UE某一multicast业务(例如UE感兴趣的multicast业务)需要进入连接态接收的信令中伴随指示UE上报eLCID支持能力；或者在UE向网络侧设备上报了感兴趣的多播业务的信息之后，网络侧设备通过dedicated RRC信令指示UE上报eLCID支持能力。
3.在UE不支持eLCID的情况下，UE不上报eLCID的能力信息，从而可以节省一定的开销。
4.若网络侧设备在一定的时间窗口内，没有接收到UE上报的eLCID支持能力，则网络侧设备认为UE不支持eLCID。
5.网络侧设备在接收到每个UE的eLCID能力信息之后，可以确定PTM leg的LCID和/或PTP leg的LCID的配置，在所有UE都支持eLCID的情况下，网络侧设备可以将PTM leg的LCID配置在所有UE支持的eLCID区间。对于PTP leg的LCID的配置，网络侧设备可以根据每个UE能力的不同，配置在各自UE支持的区间范围内。其中，PTP leg的LCID可以与PTM leg的LCID相同，也可以不同，PTP leg的LCID可以与PTM leg的LCID可以通过MRB ID关联。
6.当UE对多个TMGI业务感兴趣时，如果UE支持的eLCID能力不足以支持每个TMGI业务都配置PTP leg以确保接收效果，网络侧设备可以采取仅向UE配置能力范围内的PTP leg的方式。其中，PTP leg可以基于UE上报的感兴趣的业务的指示顺序或者显式的TMGI业务之间的优先级确定。
实施例4：UE行为
在UE获取到感兴趣的TMGI业务的MRB对应的PTM leg的LCID和/或PTP leg的LCID以及相应配置之后，UE可以按照这些配置，建立相应的数据接收实体，其中一个MRB ID对应一个PDCP实体，一个PTM leg的LCID对应一个配置的PTM RLC实体，一个PTP leg的LCID对应一个配置的PTP RLC实体，通过PTM leg的LCID绑定MRB ID，PTP leg的LCID绑定相同的MRB ID,如此UE可以为一个MRB建立了split的两个leg，该两个leg的数据可以发送到共同的PDCP实体，进行重排序和重复检测等操作。
UE接收到G-RNTI的调度数据，从MAC PDU subheader里解出LCID，确定对应的PTM leg实体，从而进行后续接收处理。
UE接收到C-RNTI的调度数据，从MAC PDU subheader里解出LCID，并根据LCID，确定对应的unicast接收实体或者不同TMGI的不同PTP leg的接收实体，从而进行后续接收处理。
需要说明的是，本申请实施例提供的逻辑信道配置方法，执行主体可以为逻辑信道配置装置，或者，该逻辑信道配置装置中的用于执行逻辑信道配置方法的控制模块。本申请实施例中以逻辑信道配置装置执行逻辑信道配置方法为例，说明本申请实施例提供的逻辑信道配置装置。
如图5所示，本申请实施例提供一种逻辑信道配置装置400，该逻辑信道配置装置400包括获取模块401。获取模块401，用于获取第一TMGI对应的至少一个逻辑信道配置信息；其中，一个逻辑信道配置信息指示以下任意一项配置：第一配置：PTM的LCID和/或PTM RLC承载配置；第二配置：PTP的LCID和/或PTP RLC承载配置。
可选地，第一TMGI包含N个MRB，一个MRB对应至少一个逻辑信道配置信息中的一个逻辑信道配置信息或两个逻辑信道配置信息，N为正整数；其中，两个逻辑信道配置信息中的一个逻辑信道配置信息指示第一配置，另一个逻辑信道配置信息指示第二配置。
可选地，一个逻辑信道配置信息指示PTM的LCID，PTM的LCID为预定义的PTM的LCID的取值区间中的全部LCID。
可选地，一个逻辑信道配置信息指示PTM的LCID，PTM的LCID为预定义的PTM的LCID的取值区间中，网络侧设备指示的目标数量的LCID，目标数量通过第一信令指示，第一信令为第一公共信令或第一专用RRC信令。
可选地，一个逻辑信道配置信息指示PTM的LCID，PTM的LCID为网络侧设备通过第二信令指示的LCID，第二信令为第二公共信令或第二专用RRC信令。
可选地，逻辑信道配置装置还可以包括接收模块；接收模块，用于接收网络侧设备发送的第一接收实体配置信息，第一接收实体配置信息包括以下至少一项：PTM RLC承载配置、PDCP配置。
可选地，一个逻辑信道配置信息指示PTP的LCID，PTP的LCID为网络侧设备通过第三专用RRC信令指示的。
可选地，一个MRB对应两个逻辑信道配置信息，在第三专用RRC信令中不包含PTP的LCID的情况下，PTP的LCID与PTM的LCID相同。
可选地，逻辑信道配置装置还可以包括接收模块；接收模块，用于接收网络侧设备发送的第二接收实体配置信息，第二接收实体配置信息包括以下至少一项：PTP RLC承载配置、PDCP配置。
可选地，逻辑信道配置装置还可以包括发送模块；发送模块，用于在UE进入连接态之后，向网络侧设备发送逻辑信道扩展能力信息，逻辑信道扩展能力信息用于指示以下至少一项：
UE是否支持扩展LCID；
UE支持第一比特数的扩展LCID；
UE支持第二比特数的扩展LCID。
可选地，在UE支持扩展LCID的情况下，PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，PTP的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内；或者，
在UE不支持扩展LCID的情况下，PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，PTP的LCID处于未扩展LCID的区间范围内。
可选地，逻辑信道配置装置还可以包括接收模块；接收模块，用于在发送模块向网络侧设备发送逻辑信道扩展能力信息之前，接收网络侧设备发送的第三信令，第三信令用于指示UE上报扩展LCID的能力信息。
可选地，逻辑信道配置装置还可以包括建立模块、接收模块和发送模块；建立模块，用于在获取模块获取至少一个逻辑信道配置信息之后，根据至少一个逻辑信道配置信息，建立第一TMGI的数据接收实体；接收模块，用于接收目标调度数据；发送模块，用于在目标调度数据为第一TMGI对应的群组无线网络临时标识G-RNTI监听到的调度数据，或目标调度数据为UE的小区无线网络临时标识C-RNTI监听到的调度数据、且目标调度数据中的LCID为逻辑信道配置信息指示的LCID的情况下，将目标调度数据，发送至第一TMGI的数据接收实体进行处理。
可选地，UE不支持扩展LCID；逻辑信道配置装置还可以包括执行模块；执行模块，用于在接收模块接收目标调度数据之后，在目标调度数据中的LCID不属于UE支持的LCID的情况下，UE丢弃目标调度数据。
本申请实施例提供一种逻辑信道配置装置，由于可以获取TMGI的逻辑信道配置信息，因此当UE对某个TMGI感兴趣时，可以获取该TMGI的逻辑信道配置信息，比如第一配置(PTM的LCID和/或PTM RLC承载配置)和/第二配置(PTP的LCID和/或PTP RLC承载配置)，如此可以根据该逻辑信道配置信息接收TMGI业务，从而可以提升多播业务和单播业务的协作传输效率，进而可以在保证系统效率的基础上，提升多播业务的传输效率。
如图6所示，本申请实施例提供一种逻辑信道配置装置500，该逻辑信道配置装置500包括发送模块501；发送模块501，用于向UE发送第一TMGI对应的至少一个逻辑信道配置信息；其中，一个逻辑信道配置信息指示以下任意一项配置：第一配置：PTM的LCID和/或PTM RLC承载配置；第二配置：PTP的LCID和/或PTP RLC承载配置。
可选地，第一TMGI包含N个MRB，一个MRB对应至少一个逻辑信道配置信息中的一个逻辑信道配置信息或两个逻辑信道配置信息，N为正整数；其中，两个逻辑信道配置信息中的一个逻辑信道配置信息指示第一配置，另一个逻辑信道配置信息指示第二配置。
可选地，一个逻辑信道配置信息指示PTM的LCID，PTM的LCID为预定义的PTM的LCID的取值区间中，网络侧设备指示的目标数量的LCID，目标数量通过第一信令指示，第一信令为第一公共信令或为第一专用RRC信令。
可选地，一个逻辑信道配置信息指示PTM的LCID，PTM的LCID为网络侧设备通过第二信令指示的LCID，第二信令为第二公共信令或第二专用RRC信令。
可选地，发送模块，还用于向UE发送第一接收实体配置信息，第一接收实体配置信息包括：PTM RLC承载配置、PDCP配置。
可选地，一个逻辑信道配置信息指示PTP的LCID，PTP的LCID为网络侧设备通过第三专用RRC信令指示的。
可选地，一个MRB对应两个逻辑信道配置信息，在第三专用RRC信令不包含PTP的LCID的情况下，PTP的LCID与PTM的LCID相同。
可选地，发送模块，还用于向UE发送第二接收实体配置信息，第二接收实体配置信息包括以下至少一项：PTP RLC承载配置、PDCP配置。
可选地，逻辑信道配置装置还包括接收模块，接收模块，用于在发送模块向UE发送逻辑信道配置信息之前，接收UE发送的逻辑信道扩展能力信息，逻辑信道扩展能力信息用于指示以下至少一项：
UE是否支持扩展LCID；
UE支持第一比特数的扩展LCID；
UE支持第二比特数的扩展LCID。
可选地，在UE支持扩展LCID的情况下，PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，PTP的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内；或者，
在UE不支持扩展LCID的情况下，PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，PTP的LCID处于未扩展LCID的区间范围内。
可选地，发送模块，还用于在接收模块接收UE发送的逻辑信道扩展能力信息之前，向UE发送的第三信令，第三信令用于指示UE上报扩展LCID的能力信息。
本申请实施例提供一种逻辑信道配置装置，由于可以向UE发送TMGI的逻辑信道配置信息，因此当UE上报了其对某个TMGI感兴趣时，可以向UE发送该TMGI的逻辑信道配置信息，比如第一配置(PTM的LCID和/或PTM RLC承载配置)和/第二配置(PTP的LCID和/或PTP RLC承载配置)，如此可以使得UE能够根据该逻辑信道配置信息接收TMGI业务，从而可以提升多播业务和单播业务的协作传输效率，进而可以在保证系统效率的基础上，提升多播业务的传输效率。
本申请实施例中的逻辑信道配置装置可以是装置，也可以是UE中的部件、集成电路、或芯片。该装置可以是移动UE，也可以为非移动UE。示例性的，移动UE可以包括但不限于上述所列举的UE11的类型，非移动UE可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的逻辑信道配置装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的逻辑信道配置装置能够实现上述方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选地，如图7所示，本申请实施例还提供一种通信设备600，包括处理器601，存储器602，存储在存储器602上并可在处理器601上运行的程序或指令，例如，该通信设备600为UE时，该程序或指令被处理器601执行时实现上述逻辑信道配置方法实施例的各个过程，且能达到相同的技术效果。该通信设备600为网络侧设备时，该程序或指令被处理器601执行时实现上述逻辑信道配置装置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
图8为实现本申请实施例的一种UE的硬件结构示意图。
该UE 100包括但不限于：射频单元101、网络模块102、音频输出单元103、输入单元104、传感器105、显示单元106、用户输入单元107、接口单元108、存储器109、以及处理器110等部件。
本领域技术人员可以理解，UE 100还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器110逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图8中示出的UE结构并不构成对UE的限定，UE可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元104可以包括图形处理器(Graphics Processing Unit，GPU)1041和麦克风1042，图形处理器1041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元106可包括显示面板1061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板1061。用户输入单元107包括触控面板1071以及其他输入设备1072。触控面板1071，也称为触摸屏。触控面板1071可包括触摸检测装置和触摸控制器两个部分。其他输入设备1072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元101将来自网络侧设备的下行数据接收后，给处理器110处理；另外，将上行的数据发送给网络侧设备。通常，射频单元101包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器109可用于存储软件程序或指令以及各种数据。存储器109可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器109可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器110可包括一个或多个处理单元；可选的，处理器110可集成应用处理器和调制解调处理器， 其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器110中。
其中，处理器110，用于获取第一TMGI对应的至少一个逻辑信道配置信息；其中，一个逻辑信道配置信息指示以下任意一项配置：第一配置：PTM的LCID和/或PTM RLC承载配置；第二配置：PTP的LCID和/或PTP RLC承载配置。
可选地，第一TMGI包含N个MRB，一个MRB对应至少一个逻辑信道配置信息中的一个逻辑信道配置信息或两个逻辑信道配置信息，N为正整数；其中，两个逻辑信道配置信息中的一个逻辑信道配置信息指示第一配置，另一个逻辑信道配置信息指示第二配置。
可选地，一个逻辑信道配置信息指示PTM的LCID，PTM的LCID为预定义的PTM的LCID的取值区间中的全部LCID。
可选地，一个逻辑信道配置信息指示PTM的LCID，PTM的LCID为预定义的PTM的LCID的取值区间中，网络侧设备指示的目标数量的LCID，目标数量通过第一信令指示，第一信令为第一公共信令或第一专用RRC信令。
可选地，一个逻辑信道配置信息指示PTM的LCID，PTM的LCID为网络侧设备通过第二信令指示的LCID，第二信令为第二公共信令或第二专用RRC信令。
可选地，逻辑信道配置装置还可以包括接收模块；接收模块，用于接收网络侧设备发送的第一接收实体配置信息，第一接收实体配置信息包括以下至少一项：PTM RLC承载配置、PDCP配置。
可选地，一个逻辑信道配置信息指示PTP的LCID，PTP的LCID为网络侧设备通过第三专用RRC信令指示的。
可选地，一个MRB对应两个逻辑信道配置信息，在第三专用RRC信令中不包含PTP的LCID的情况下，PTP的LCID与PTM的LCID相同。
可选地，射频单元，用于接收网络侧设备发送的第二接收实体配置信息，第二接收实体配置信息包括以下至少一项：PTP RLC承载配置、PDCP配置。
可选地，射频单元，还可以用于在UE进入连接态之后，向网络侧设备发送逻辑信道扩展能力信息，逻辑信道扩展能力信息用于指示以下至少一项：
UE是否支持扩展LCID；
UE支持第一比特数的扩展LCID；
UE支持第二比特数的扩展LCID。
可选地，在UE支持扩展LCID的情况下，PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，PTP的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内；或者，
在UE不支持扩展LCID的情况下，PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，PTP的LCID处于未扩展LCID的区间范围内。
可选地，射频单元，可以用于在发送模块向网络侧设备发送逻辑信道扩展能力信息之前，接收网络侧设备发送的第三信令，第三信令用于指示UE上报扩展LCID的能力信息。
可选地，处理器110，还可以用于在获取至少一个逻辑信道配置信息之后，根据至少一个逻辑信道配置信息，建立第一TMGI的数据接收实体；射频单元101，还可以用于接收目标调度数据，处理器110，还可以用于在目标调度数据为第一TMGI对应的群组无线网络临时标识G-RNTI监听到的调度数据，或目标调度数据为UE的小区无线网络临时标识C-RNTI监听到的调度数据、且目标调度数据中的LCID为逻辑信道配置信息指示的LCID的情况下，将目标调度数据，发送至第一TMGI的数据接收实体进行处理。
可选地，UE不支持扩展LCID；逻辑信道配置装置还可以包括执行模块；执行模块，用于在接收模块接收目标调度数据之后，在目标调度数据中的LCID不属于UE支持的LCID的情况下，UE丢弃目标调度数据。
本申请实施例提供一种UE，由于可以获取TMGI的逻辑信道配置信息，因此当UE对某个TMGI感兴趣时，可以获取该TMGI的逻辑信道配置信息，比如第一配置(PTM的LCID和/或PTM RLC承载配置)和/第二配置(PTP的LCID和/或PTP RLC承载配置)，如此可以根据该逻辑信道配置信息接收TMGI业务，从而可以提升多播业务和单播业务的协作传输效率，进而可以在保证系统效率的基础上，提升多播业务的传输效率。
具体地，本申请实施例还提供了一种网络侧设备。如图9所示，该网络侧设备700包括：天线71、射频装置72、基带装置73。天线71与射频装置72连接。在上行方向上，射频装置72通过天线71接收信息，将接收的信息发送给基带装置73进行处理。在下行方向上，基带装置73对要发送的信息进行处 理，并发送给射频装置72，射频装置72对收到的信息进行处理后经过天线71发送出去。
上述频带处理装置可以位于基带装置73中，以上实施例中网络侧设备执行的方法可以在基带装置73中实现，该基带装置73包括处理器74和存储器75。
基带装置73例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图9所示，其中一个芯片例如为处理器74，与存储器75连接，以调用存储器75中的程序，执行以上方法实施例中所示的网络侧设备操作。
该基带装置73还可以包括网络接口76，用于与射频装置72交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
具体地，本发明实施例的网络侧设备还包括：存储在存储器75上并可在处理器74上运行的指令或程序，处理器74调用存储器75中的指令或程序执行图6所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
射频装置72，用于向UE发送第一TMGI对应的至少一个逻辑信道配置信息；其中，一个逻辑信道配置信息指示以下任意一项配置：第一配置：PTM的LCID和/或PTM RLC承载配置；第二配置：PTP的LCID和/或PTP RLC承载配置。
可选地，第一TMGI包含N个MRB，一个MRB对应至少一个逻辑信道配置信息中的一个逻辑信道配置信息或两个逻辑信道配置信息，N为正整数；其中，两个逻辑信道配置信息中的一个逻辑信道配置信息指示第一配置，另一个逻辑信道配置信息指示第二配置。
可选地，一个逻辑信道配置信息指示PTM的LCID，PTM的LCID为预定义的PTM的LCID的取值区间中，网络侧设备指示的目标数量的LCID，目标数量通过第一信令指示，第一信令为第一公共信令或为第一专用RRC信令。
可选地，一个逻辑信道配置信息指示PTM的LCID，PTM的LCID为网络侧设备通过第二信令指示的LCID，第二信令为第二公共信令或第二专用RRC信令。
可选地，射频装置72，还用于向UE发送第一接收实体配置信息，第一接收实体配置信息包括：PTM RLC承载配置、PDCP配置。
可选地，一个逻辑信道配置信息指示PTP的LCID，PTP的LCID为网络侧设备通过第三专用RRC信令指示的。
可选地，一个MRB对应两个逻辑信道配置信息，在第三专用RRC信令不包含PTP的LCID的情况下，PTP的LCID与PTM的LCID相同。
可选地，射频装置72，还用于向UE发送第二接收实体配置信息，第二接收实体配置信息包括以下至少一项：PTP RLC承载配置、PDCP配置。
可选地，射频装置72，该用于在向UE发送逻辑信道配置信息之前，接收UE发送的逻辑信道扩展能力信息，逻辑信道扩展能力信息用于指示以下至少一项：
UE是否支持扩展LCID；
UE支持第一比特数的扩展LCID；
UE支持第二比特数的扩展LCID。
可选地，在UE支持扩展LCID的情况下，PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，PTP的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内；或者，
在UE不支持扩展LCID的情况下，PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，PTP的LCID处于未扩展LCID的区间范围内。
可选地，射频装置72，还用于在接收UE发送的逻辑信道扩展能力信息之前，向UE发送的第三信令，第三信令用于指示UE上报扩展LCID的能力信息。
本申请实施例提供一种网络侧设备，由于可以向UE发送TMGI的逻辑信道配置信息，因此当UE上报了其对某个TMGI感兴趣时，可以向UE发送该TMGI的逻辑信道配置信息，比如第一配置(PTM的LCID和/或PTM RLC承载配置)和/第二配置(PTP的LCID和/或PTP RLC承载配置)，如此可以使得UE能够根据该逻辑信道配置信息接收TMGI业务，从而可以提升多播业务和单播业务的协作传输效率，进而可以在保证系统效率的基础上，提升多播业务的传输效率。
本申请实施例还提供一种可读存储介质，可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述逻辑信道配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，处理器为上述实施例中的UE中的处理器。可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、 磁碟或者光盘等。
本申请实施例另提供了一种芯片，芯片包括处理器和通信接口，通信接口和处理器耦合，处理器用于运行网络侧设备程序或指令，实现上述逻辑信道配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台UE(可以是手机，计算机，服务器，空调器，或者网络侧设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (54)

  1. 一种逻辑信道配置方法，所述方法包括：
    用户设备UE获取第一临时移动群组标识TMGI对应的至少一个逻辑信道配置信息；
    其中，一个逻辑信道配置信息指示以下任意一项配置：
    第一配置：点对多点PTM的逻辑信道标识LCID和/或PTM无线链路控制RLC承载配置；
    第二配置：点对点PTP的LCID和/或PTP RLC承载配置。
  2. 根据权利要求1所述的方法，其中，所述第一TMGI包含N个多播无线承载MRB，一个MRB对应所述至少一个逻辑信道配置信息中的一个逻辑信道配置信息或两个逻辑信道配置信息，N为正整数；
    其中，所述两个逻辑信道配置信息中的一个逻辑信道配置信息指示所述第一配置，另一个逻辑信道配置信息指示所述第二配置。
  3. 根据权利要求2所述的方法，其中，一个逻辑信道配置信息指示所述PTM的LCID；
    所述PTM的LCID为预定义的PTM的LCID的取值区间中的全部LCID。
  4. 根据权利要求2所述的方法，其中，一个逻辑信道配置信息指示所述PTM的LCID；
    所述PTM的LCID为预定义的PTM的LCID的取值区间中，网络侧设备指示的目标数量的LCID，所述目标数量通过第一信令指示，所述第一信令为第一公共信令或第一专用无线资源控制RRC信令。
  5. 根据权利要求2所述的方法，其中，一个逻辑信道配置信息指示所述PTM的LCID；
    所述PTM的LCID为网络侧设备通过第二信令指示的LCID，所述第二信令为第二公共信令或第二专用RRC信令。
  6. 根据权利要求3、4或5所述的方法，其中，所述方法还包括：
    所述UE接收网络侧设备发送的第一接收实体配置信息，所述第一接收实体配置信息包括以下至少一项：PTM RLC承载配置、分组数据汇聚协议PDCP配置。
  7. 根据权利要求2所述的方法，其中，一个逻辑信道配置信息指示所述PTP的LCID；
    所述PTP的LCID为网络侧设备通过第三专用RRC信令指示的。
  8. 根据权利要求7所述的方法，其中，所述一个MRB对应所述两个逻辑信道配置信息；
    在所述第三专用RRC信令中不包含所述PTP的LCID的情况下，所述PTP的LCID与所述PTM的LCID相同。
  9. 根据权利要求7所述的方法，其中，所述方法还包括：
    所述UE接收所述网络侧设备发送的第二接收实体配置信息，所述第二接收实体配置信息包括以下至少一项：PTP RLC承载配置、PDCP配置。
  10. 根据权利要求1所述的方法，其中，所述方法还包括：
    在所述UE进入连接态之后，所述UE向网络侧设备发送逻辑信道扩展能力信息，所述逻辑信道扩展能力信息用于指示以下至少一项：
    所述UE是否支持扩展LCID；
    所述UE支持第一比特数的扩展LCID；
    所述UE支持第二比特数的扩展LCID。
  11. 根据权利要求10所述的方法，其中，
    在所述UE支持扩展LCID的情况下，所述PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，所述PTP的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内；或者，
    在所述UE不支持扩展LCID的情况下，所述PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，所述PTP的LCID处于未扩展LCID的区间范围内。
  12. 根据权利要求10所述的方法，其中，所述UE向所述网络侧设备发送所述逻辑信道扩展能力信息之前，所述方法还包括：
    所述UE接收所述网络侧设备发送的第三信令，所述第三信令用于指示所述UE上报扩展LCID的能力信息。
  13. 根据权利要求1所述的方法，其中，所述UE获取所述至少一个逻辑信道配置信息之后，所述方法还包括：
    所述UE根据所述至少一个逻辑信道配置信息，建立所述第一TMGI的数据接收实体；
    所述UE接收目标调度数据；
    在所述目标调度数据为第一TMGI对应的群组无线网络临时标识G-RNTI监听到的调度数据，或所述目标调度数据为UE的小区无线网络临时标识C-RNTI监听到的调度数据、且所述目标调度数据中的LCID为所述逻辑信道配置信息指示的LCID的情况下，所述UE将所述目标调度数据，发送至所述第一TMGI的数据接收实体进行处理。
  14. 根据权利要求13所述的方法，其中，所述UE不支持扩展LCID；
    所述UE接收所述目标调度数据之后，所述方法还包括：
    在所述目标调度数据中的LCID不属于所述UE支持的LCID的情况下，所述UE丢弃所述目标调度数据。
  15. 一种逻辑信道配置方法，所述方法包括：
    网络侧设备向用户设备UE发送第一临时移动群组标识TMGI对应的至少一个逻辑信道配置信息；
    其中，一个逻辑信道配置信息指示以下任意一项配置：
    第一配置：点对多点PTM的逻辑信道标识LCID和/或PTM无线链路控制RLC承载配置；
    第二配置：点对点PTP的LCID和/或PTP RLC承载配置。
  16. 根据权利要求15所述的方法，其中，所述第一TMGI包含N个多播无线承载MRB，一个MRB对应所述至少一个逻辑信道配置信息中的一个逻辑信道配置信息或两个逻辑信道配置信息，N为正整数；
    其中，所述两个逻辑信道配置信息中的一个逻辑信道配置信息指示所述第一配置，另一个逻辑信道配置信息指示所述第二配置。
  17. 根据权利要求16所述的方法，其中，一个逻辑信道配置信息指示所述PTM的LCID；
    所述PTM的LCID为预定义的PTM的LCID的取值区间中，所述网络侧设备指示的目标数量的LCID，所述目标数量通过第一信令指示，所述第一信令为第一公共信令或为第一专用无线资源控制RRC信令。
  18. 根据权利要求16所述的方法，其中，一个逻辑信道配置信息指示所述PTM的LCID；
    所述PTM的LCID为网络侧设备通过第二信令指示的LCID，所述第二信令为第二公共信令或第二专用RRC信令。
  19. 根据权利要求17或18所述的方法，其中，所述方法还包括：
    所述网络侧设备向所述UE发送第一接收实体配置信息，所述第一接收实体配置信息包括：PTM RLC承载配置、分组数据汇聚协议PDCP配置。
  20. 根据权利要求16所述的方法，其中，一个逻辑信道配置信息指示所述PTP的LCID；
    所述PTP的LCID为所述网络侧设备通过第三专用RRC信令指示的。
  21. 根据权利要求20所述的方法，其中，所述一个MRB对应所述两个逻辑信道配置信息；
    在所述第三专用RRC信令不包含所述PTP的LCID的情况下，所述PTP的LCID与所述PTM的LCID相同。
  22. 根据权利要求20所述的方法，其中，所述方法还包括：
    所述网络侧设备向所述UE发送第二接收实体配置信息，所述第二接收实体配置信息包括以下至少一项：PTP RLC承载配置、PDCP配置。
  23. 根据权利要求15所述的方法，其中，所述网络侧设备向所述UE发送所述逻辑信道配置信息之前，所述方法还包括：
    所述网络侧设备接收所述UE发送的逻辑信道扩展能力信息，所述逻辑信道扩展能力信息用于指示以下至少一项：
    所述UE是否支持扩展LCID；
    所述UE支持第一比特数的扩展LCID；
    所述UE支持第二比特数的扩展LCID。
  24. 根据权利要求23所述的方法，其中，
    在所述UE支持扩展LCID的情况下，所述PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，所述PTP的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内；或者，
    在所述UE不支持扩展LCID的情况下，所述PTM的LCID处于未扩展LCID的区间范围内或扩展 LCID的区间范围内，所述PTP的LCID处于未扩展LCID的区间范围内。
  25. 根据权利要求23所述的方法，其中，所述网络侧设备接收所述UE发送的所述逻辑信道扩展能力信息之前，所述方法还包括：
    所述网络侧设备向所述UE发送的第三信令，所述第三信令用于指示所述UE上报扩展LCID的能力信息。
  26. 一种逻辑信道配置装置，所述装置包括获取模块；
    所述获取模块，用于获取第一临时移动群组标识TMGI对应的至少一个逻辑信道配置信息；
    其中，一个逻辑信道配置信息指示以下任意一项配置：
    第一配置：点对多点PTM的逻辑信道标识LCID和/或PTM无线链路控制RLC承载配置；
    第二配置：点对点PTP的LCID和/或PTP RLC承载配置。
  27. 根据权利要求26所述的装置，其中，所述第一TMGI包含N个多播无线承载MRB，一个MRB对应所述至少一个逻辑信道配置信息中的一个逻辑信道配置信息或两个逻辑信道配置信息，N为正整数；
    其中，所述两个逻辑信道配置信息中的一个逻辑信道配置信息指示所述第一配置，另一个逻辑信道配置信息指示所述第二配置。
  28. 根据权利要求27所述的装置，其中，一个逻辑信道配置信息指示所述PTM的LCID；
    所述PTM的LCID为预定义的PTM的LCID的取值区间中的全部LCID。
  29. 根据权利要求27所述的装置，其中，一个逻辑信道配置信息指示所述PTM的LCID；
    所述PTM的LCID为预定义的PTM的LCID的取值区间中，网络侧设备指示的目标数量的LCID，所述目标数量通过第一信令指示，所述第一信令为第一公共信令或第一专用无线资源控制RRC信令。
  30. 根据权利要求27所述的装置，其中，一个逻辑信道配置信息指示所述PTM的LCID；
    所述PTM的LCID为网络侧设备通过第二信令指示的LCID，所述第二信令为第二公共信令或第二专用RRC信令。
  31. 根据权利要求28、29或30所述的装置，其中，所述装置还包括接收模块；
    所述接收模块，用于接收网络侧设备发送的第一接收实体配置信息，所述第一接收实体配置信息包括以下至少一项：PTM RLC承载配置、分组数据汇聚协议PDCP配置。
  32. 根据权利要求27所述的装置，其中，一个逻辑信道配置信息指示所述PTP的LCID；
    所述PTP的LCID为网络侧设备通过第三专用RRC信令指示的。
  33. 根据权利要求32所述的装置，其中，所述一个MRB对应所述两个逻辑信道配置信息；
    在所述第三专用RRC信令中不包含所述PTP的LCID的情况下，所述PTP的LCID与所述PTM的LCID相同。
  34. 根据权利要求32所述的装置，其中，所述装置还包括接收模块；
    所述接收模块，用于接收所述网络侧设备发送的第二接收实体配置信息，所述第二接收实体配置信息包括以下至少一项：PTP RLC承载配置、PDCP配置。
  35. 根据权利要求26所述的装置，其中，所述装置还包括发送模块；
    所述发送模块，用于在UE进入连接态之后，向网络侧设备发送逻辑信道扩展能力信息，所述逻辑信道扩展能力信息用于指示以下至少一项：
    所述UE是否支持扩展LCID；
    所述UE支持第一比特数的扩展LCID；
    所述UE支持第二比特数的扩展LCID。
  36. 根据权利要求35所述的装置，其中，在所述UE支持扩展LCID的情况下，所述PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，所述PTP的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内；或者，
    在所述UE不支持扩展LCID的情况下，所述PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，所述PTP的LCID处于未扩展LCID的区间范围内。
  37. 根据权利要求35所述的装置，其中，所述装置还包括接收模块；
    所述接收模块，用于在向所述网络侧设备发送所述逻辑信道扩展能力信息之前，接收所述网络侧设备发送的第三信令，所述第三信令用于指示所述UE上报扩展LCID的能力信息。
  38. 根据权利要求26所述的装置，其中，所述装置还包括建立模块、接收模块和发送模块；
    所述建立模块，用于在获取所述至少一个逻辑信道配置信息之后，根据所述至少一个逻辑信道配置信息，建立所述第一TMGI的数据接收实体；
    所述接收模块，用于接收目标调度数据；
    所述发送模块，用于在所述目标调度数据为第一TMGI对应的群组无线网络临时标识G-RNTI监听到的调度数据，或所述目标调度数据为UE的小区无线网络临时标识C-RNTI监听到的调度数据、且所述目标调度数据中的LCID为所述逻辑信道配置信息指示的LCID的情况下，所述UE将所述目标调度数据，发送至所述第一TMGI的数据接收实体进行处理。
  39. 根据权利要求38所述的装置，其中，UE不支持扩展LCID；所述装置还包括执行模块；
    所述执行模块，用于在接收所述目标调度数据之后，在所述目标调度数据中的LCID不属于所述UE支持的LCID的情况下，所述UE丢弃所述目标调度数据。
  40. 一种逻辑信道配置装置，所述装置包括发送模块；
    所述发送模块，用于向用户设备UE发送第一临时移动群组标识TMGI对应的至少一个逻辑信道配置信息；
    其中，一个逻辑信道配置信息指示以下任意一项配置：
    第一配置：点对多点PTM的逻辑信道标识LCID和/或PTM无线链路控制RLC承载配置；
    第二配置：点对点PTP的LCID和/或PTP RLC承载配置。
  41. 根据权利要求40所述的装置，其中，所述第一TMGI包含N个多播无线承载MRB，一个MRB对应所述至少一个逻辑信道配置信息中的一个逻辑信道配置信息或两个逻辑信道配置信息，N为正整数；
    其中，所述两个逻辑信道配置信息中的一个逻辑信道配置信息指示所述第一配置，另一个逻辑信道配置信息指示所述第二配置。
  42. 根据权利要求41所述的装置，其中，一个逻辑信道配置信息指示所述PTM的LCID；
    所述PTM的LCID为预定义的PTM的LCID的取值区间中，网络侧设备指示的目标数量的LCID，所述目标数量通过第一信令指示，所述第一信令为第一公共信令或为第一专用无线资源控制RRC信令。
  43. 根据权利要求41所述的装置，其中，一个逻辑信道配置信息指示所述PTM的LCID；
    所述PTM的LCID为网络侧设备通过第二信令指示的LCID，所述第二信令为第二公共信令或第二专用RRC信令。
  44. 根据权利要求42或43所述的装置，其中，所述发送模块，还用于向所述UE发送第一接收实体配置信息，所述第一接收实体配置信息包括：PTM RLC承载配置、分组数据汇聚协议PDCP配置。
  45. 根据权利要求41所述的装置，其中，一个逻辑信道配置信息指示所述PTP的LCID；
    所述PTP的LCID为网络侧设备通过第三专用RRC信令指示的。
  46. 根据权利要求45所述的装置，其中，所述一个MRB对应所述两个逻辑信道配置信息；
    在所述第三专用RRC信令不包含所述PTP的LCID的情况下，所述PTP的LCID与所述PTM的LCID相同。
  47. 根据权利要求45所述的装置，其中，所述发送模块，还用于向所述UE发送第二接收实体配置信息，所述第二接收实体配置信息包括以下至少一项：PTP RLC承载配置、PDCP配置。
  48. 根据权利要求40所述的装置，其中，所述装置还包括接收模块；
    所述接收模块，用于在向所述UE发送所述逻辑信道配置信息之前，接收所述UE发送的逻辑信道扩展能力信息，所述逻辑信道扩展能力信息用于指示以下至少一项：
    所述UE是否支持扩展LCID；
    所述UE支持第一比特数的扩展LCID；
    所述UE支持第二比特数的扩展LCID。
  49. 根据权利要求48所述的装置，其中，
    在所述UE支持扩展LCID的情况下，所述PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，所述PTP的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内；或者，
    在所述UE不支持扩展LCID的情况下，所述PTM的LCID处于未扩展LCID的区间范围内或扩展LCID的区间范围内，所述PTP的LCID处于未扩展LCID的区间范围内。
  50. 根据权利要求48所述的装置，其中，所述发送模块，还用于在接收所述UE发送的所述逻辑信道扩展能力信息之前，所述网络侧设备向所述UE发送的第三信令，所述第三信令用于指示所述UE上报扩展LCID的能力信息。
  51. 一种用户设备UE，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至14任一项所述的逻辑信道配置方法的步骤。
  52. 一种网络侧设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求15至25任一项所述的逻辑信道配置方法的步骤。
  53. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1-14任一项所述的逻辑信道配置方法，或者实现如权利要求15至25任一项所述的逻辑信道配置方法的步骤。
  54. 一种计算机程序产品，所述计算机程序产品被至少一个处理器执行以实现如权利要求1-25中任一项所述的逻辑信道配置方法的步骤。
PCT/CN2022/072134 2021-01-15 2022-01-14 逻辑信道配置方法、装置及设备 WO2022152268A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020237023140A KR20230113634A (ko) 2021-01-15 2022-01-14 논리 채널 구성 방법, 장치 및 기기
JP2023539914A JP2024502423A (ja) 2021-01-15 2022-01-14 論理チャネル配置方法、装置及び機器
EP22739143.0A EP4280631A1 (en) 2021-01-15 2022-01-14 Method, apparatus, and device for configuring logical channel
US18/347,696 US20230354474A1 (en) 2021-01-15 2023-07-06 Logical channel configuration method and apparatus, and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110057653.3 2021-01-15
CN202110057653.3A CN114765747B (zh) 2021-01-15 2021-01-15 逻辑信道配置方法、装置及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/347,696 Continuation US20230354474A1 (en) 2021-01-15 2023-07-06 Logical channel configuration method and apparatus, and device

Publications (1)

Publication Number Publication Date
WO2022152268A1 true WO2022152268A1 (zh) 2022-07-21

Family

ID=82364869

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/072134 WO2022152268A1 (zh) 2021-01-15 2022-01-14 逻辑信道配置方法、装置及设备

Country Status (6)

Country Link
US (1) US20230354474A1 (zh)
EP (1) EP4280631A1 (zh)
JP (1) JP2024502423A (zh)
KR (1) KR20230113634A (zh)
CN (1) CN114765747B (zh)
WO (1) WO2022152268A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017086580A1 (en) * 2015-11-16 2017-05-26 Lg Electronics Inc. Method for transmitting or receiving a mac pdu in a wireless communication system and a device therefor
CN109286467A (zh) * 2017-07-19 2019-01-29 大唐移动通信设备有限公司 共享信道cqi的获取方法及装置、上报方法及装置
CN110621069A (zh) * 2018-06-19 2019-12-27 维沃移动通信有限公司 一种数据传输方法、设备及系统
CN111901766A (zh) * 2020-04-27 2020-11-06 中兴通讯股份有限公司 承载配置、上下文信息管理、释放方法、装置和设备
CN112087720A (zh) * 2019-06-12 2020-12-15 华为技术有限公司 一种通信方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101742410B (zh) * 2008-11-21 2013-02-27 中兴通讯股份有限公司 一种多媒体广播/组播业务控制消息的收发方法
CN106470498B (zh) * 2015-08-17 2020-09-29 中兴通讯股份有限公司 Sc-mcch发送方法、sc-ptm接收方法及其装置
CN111901765A (zh) * 2020-04-27 2020-11-06 中兴通讯股份有限公司 模式配置方法、装置、设备和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017086580A1 (en) * 2015-11-16 2017-05-26 Lg Electronics Inc. Method for transmitting or receiving a mac pdu in a wireless communication system and a device therefor
CN109286467A (zh) * 2017-07-19 2019-01-29 大唐移动通信设备有限公司 共享信道cqi的获取方法及装置、上报方法及装置
CN110621069A (zh) * 2018-06-19 2019-12-27 维沃移动通信有限公司 一种数据传输方法、设备及系统
CN112087720A (zh) * 2019-06-12 2020-12-15 华为技术有限公司 一种通信方法和装置
CN111901766A (zh) * 2020-04-27 2020-11-06 中兴通讯股份有限公司 承载配置、上下文信息管理、释放方法、装置和设备

Also Published As

Publication number Publication date
JP2024502423A (ja) 2024-01-19
US20230354474A1 (en) 2023-11-02
KR20230113634A (ko) 2023-07-31
CN114765747B (zh) 2023-04-18
CN114765747A (zh) 2022-07-19
EP4280631A1 (en) 2023-11-22

Similar Documents

Publication Publication Date Title
WO2021077434A1 (zh) 一种通信方法及装置
US20080233974A1 (en) Multimedia broadcast and multicast service notification in long term evolution
WO2022089349A1 (zh) Pdcp重复的配置、激活或去激活方法和终端
WO2022028540A1 (zh) 一种信息传输方法、装置、终端及网络设备
WO2021142647A1 (zh) 一种业务传输方法及装置、终端设备、网络设备
WO2014067303A1 (zh) 一种传输数据的方法、系统和设备
WO2022028539A1 (zh) 信息传输方法、装置、终端及网络侧设备
EP4030846A1 (en) Method and device for multicasting network slice
WO2021051320A1 (zh) 一种业务数据传输方法及装置、网络设备、终端设备
WO2021244516A1 (zh) 资源分配方法、终端及网络侧设备
TW202224455A (zh) 用於mbs的無線通信的裝置和方法
WO2022073246A1 (zh) 一种通信方法及装置
WO2014153705A1 (zh) 新载波类型小区的业务处理方法、装置及通信系统
CN112398605B (zh) 一种多播控制信道发送方法及装置
WO2023274133A1 (zh) 多播业务接收、接收配置方法、装置、终端及网络侧设备
WO2022205570A1 (zh) 无线通信方法、终端设备和网络设备
WO2022152268A1 (zh) 逻辑信道配置方法、装置及设备
WO2023284376A1 (zh) 一种多播业务修改通知方法及通信装置
WO2022083629A1 (zh) 寻呼消息的接收方法、寻呼配置方法、终端及网络侧设备
US11109211B2 (en) Method and device for supporting public safety net access in wireless communication system
WO2022012526A1 (zh) 处理方法、发送方法及相关设备
WO2022077444A1 (en) Method and device for dynamicaly switching multicast and broadcast service (mbs) data packet delivery modes
WO2022184043A1 (zh) 多播业务的接收方法、配置方法、终端及网络侧设备
WO2023001144A1 (zh) 多播广播业务的接收方法、发送方法、装置及设备
WO2021189458A1 (zh) 一种数据转发方法及装置、通信设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22739143

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023539914

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 20237023140

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022739143

Country of ref document: EP

Effective date: 20230816