WO2023036287A1 - 用户设备执行的方法、基站的传输方法及用户设备 - Google Patents

用户设备执行的方法、基站的传输方法及用户设备 Download PDF

Info

Publication number
WO2023036287A1
WO2023036287A1 PCT/CN2022/118073 CN2022118073W WO2023036287A1 WO 2023036287 A1 WO2023036287 A1 WO 2023036287A1 CN 2022118073 W CN2022118073 W CN 2022118073W WO 2023036287 A1 WO2023036287 A1 WO 2023036287A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
rlc
pdcp entity
user equipment
mrb
Prior art date
Application number
PCT/CN2022/118073
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 EP22866748.1A priority Critical patent/EP4401463A1/en
Publication of WO2023036287A1 publication Critical patent/WO2023036287A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present disclosure relates to the technical field of wireless communication, and more specifically, the present disclosure relates to a method executed by a user equipment, a transmission method of a base station, and the user equipment.
  • Goal A 5G Multicast Broadcast Service Architecture Improvement
  • 3rd Generation Partnership Project 3rd Generation Partnership Project: 3GPP
  • RAN#86 plenary meeting Huawei proposed the work item of NR Multicast and Broadcast Service (NR MBS) (see non-patent literature: RP-193248 : New WID: NR Multicast and Broadcast Service) was approved. This work item is intended to provide support for Objective A in the RAN.
  • This disclosure discusses related issues involved in the RAN achieving the above work objectives.
  • the purpose of the present invention is to provide a method and a base station for user equipment to perform re-establishment of the PDCP entity associated to the RLC entity of different modes in different ways for the separated radio bearer RB associated to the radio link control RLC of different modes transmission method and user equipment.
  • the present invention provides a method performed by user equipment.
  • the packet data convergence protocol PDCP reconstruction instruction reestablishPDCP sent by the base station.
  • the reestablishment mode of the PDCP entity is determined according to the reestablishPDCPAsAMUM sent by the base station, which is different from the PDCP reestablishment instruction.
  • the radio resource control RRC message received by the user equipment includes a PDCP reestablishment indication reestablishPDCP for a separate radio bearer RB and a first indication identifier for determining a PDCP reestablishment mode
  • non-acknowledgment is used
  • the PDCP entity is recreated in the UM RB mode of the radio bearer mode; otherwise, the PDCP entity is reestablished in the AM RB mode of the radio bearer mode in the acknowledged mode.
  • the radio resource control RRC message received by the user equipment includes a PDCP reestablishment indication reestablishPDCP for a separate RB and a first indication identifier for determining a PDCP reestablishment mode
  • the radio in the confirmation mode The PDCP entity is rebuilt in AM RB mode; otherwise, the PDCP entity is recreated in unacknowledged radio bearer UM RB mode.
  • the first indication identifier reestablishPDCPAsAMUM has two value modes, one of which is used to indicate that the radio bearer UM RB in unacknowledged mode is used to reestablish the PDCP entity, and the other value is used to Indicates that the radio bearer AM RB in confirmed mode is used to reestablish the PDCP entity.
  • radio resource control RRC message received by the user equipment contains the PDCP reestablishment instruction reestablishPDCP and the value corresponds to the value corresponding to the PDCP entity reestablished in the radio bearer AM RB mode in confirmed mode If the first indication identifier of the radio bearer AM RB in confirmed mode is used to reestablish the PDCP entity; if the RRC message received by the user equipment contains the PDCP reestablishment instruction reestablishPDCP and the value is reestablished PDCP in the unacknowledged mode radio bearer UM RB mode If the first indicator of the value corresponding to the entity is used, the PDCP entity is recreated in the radio bearer UM RB mode of the unacknowledged mode.
  • the second indication identifier reestablishPDCPIndication sent by the base station, which is different from the packet data convergence protocol PDCP reconstruction indication. Determine the reconstruction of the PDCP entity and the reconstruction mode of the PDCP entity.
  • the second indication identifier reestablishPDCPIndication has two values, one of which is used to indicate the reestablishment of the PDCP entity in the radio bearer UM RB mode in unacknowledged mode, and the other value is used to indicate
  • the PDCP entity is reconstructed in the radio bearer AM RB mode in the confirmation mode, and the PDCP entity reconstruction and the mode of reconstructing the PDCP entity are determined by setting the second indicator to a corresponding value.
  • a separate radio bearer RB associated with a radio link control RLC of a different mode when the corresponding packet data convergence protocol PDCP entity receives a request from the upper layer to reestablish the PDCP entity, The PDCP entity is recreated according to the radio bearer AM RB mode in the acknowledged mode.
  • the base station indicates reestablish PDCP to indicate to the user equipment whether the corresponding PDCP needs to be reestablished through the packet data convergence protocol PDCP.
  • the first indicator reestablishPDCPAsAMUM of the reestablishment indication indicates the PDCP entity reestablishment mode to the user equipment, or indicates the PDCP entity reestablishment and the PDCP entity reestablishment mode to the user equipment through the second indicator reestablishPDCPIndication different from the PDCP reestablishment indication.
  • the user equipment of the present invention includes: a processor; and a memory storing instructions; wherein the instructions execute the method according to any one of claims 1 to 8 when executed by the processor.
  • connection method of the user equipment the transmission method of the base station and the user equipment of the present invention, it is possible to control the separated radio bearer RB of the RLC for the radio links associated with different modes, and to rebuild the RLC entities associated with different modes in different ways PDCP entity.
  • FIG. 1 are schematic diagrams showing specific configurations of radio bearers for receiving MBS services.
  • Fig. 2 is a schematic diagram showing the execution method of the user equipment according to the first embodiment.
  • Fig. 3 is a schematic diagram showing the execution method of the user equipment in the second embodiment.
  • Fig. 4 is a brief structural block diagram of the user equipment UE involved in the present invention.
  • UE User Equipment, user equipment.
  • RRC Radio Resource Control, radio resource control.
  • RRC_CONNECTED RRC connected state.
  • RRC_INACTIVE RRC is inactive.
  • RRC_IDLE RRC idle state.
  • RAN Radio Access Network, wireless access network.
  • New RAT new radio access technology.
  • MBMS Multimedia Broadcast/Multicast Service, multimedia broadcast multicast service.
  • MBS Multicast Broadcast Services, multicast broadcast service.
  • PDCP Packet Data Convergence Protocol, packet data convergence protocol.
  • RLC Radio Link Control, wireless link control.
  • the RLC can be an RLC in an acknowledged mode (Acknowledged Mode, AM), that is, AM RLC, or an RLC in an unacknowledged mode (Unacknowledged Mode, UM), that is, UM RLC, or a transparent mode (Transparent Mode).
  • AM Acknowledged Mode
  • UM unacknowledged Mode
  • TM transparent Mode
  • a UM RLC entity is configured as a transmitting UM RLC entity or as a receiving UM RLC entity, and submits or receives RLC data PDUs.
  • the AM RLC entity includes a transmitting end and a receiving end, and submits or receives RLC data PDUs and RLC control PDUs.
  • the RLC entity submits or receives RLC data PDU and RLC control PDU (i.e. status PDU), and the receiving end of the AM RLC entity uses the status PDU to inform the peer RLC entity (i.e. the sending end of another AM RLC entity) about Its successfully received RLC data PDUs and RLC data PDUs detected as lost.
  • RLC data PDU and RLC control PDU i.e. status PDU
  • SDU Service Data Unit, service data unit.
  • SDU Service Data Unit
  • PDU Protocol Data Unit, protocol data unit.
  • the data packet that this layer receives or delivers from the lower layer is called PDU.
  • a PDCP data PDU is a data packet obtained by adding a PDCP header to a PDCP SDU.
  • RB Radio Bearer, radio bearer.
  • MRB MBS radio bearer, that is, a radio bearer that is configured for MBS multicast/broadcast transmission (A radio bearer that is configured for MBS multicast/broadcast delivery).
  • the MBS-MCCH Multicast Control Channel, multicast control channel.
  • the MBS-MCCH is used to transmit control information related to receiving MBS services.
  • SC-MCCH Single Cell Multicast Control Channel, single cell multicast control channel.
  • TMGI Temporary Mobile Group Identity, temporary mobile group identity.
  • PLMN Public Land Mobile Network, public land mobile network.
  • RNTI Radio Network Temporary Identifier, wireless network temporary identifier.
  • PTM Point to Multipoint, point to multipoint, a delivery method of MBS business.
  • the RAN node delivers a single copy of MBS data packets over radio to a set of UEs via radio (a RAN node delivers a single copy of MBS data packets over radio to a set of UEs).
  • PTP Point to Point, point to point, a delivery method of MBS business.
  • the RAN node delivers copies of multiple MBS data packets to each UE via radio (a RAN node delivers separate copies of MBS data packet over radio to individual UE).
  • LTE SC-PTM LTE Single Cell Point to Multipoint, long term evolution single cell point to multipoint.
  • MBS multicast or multicast communication service means that the same service and the same specific content are simultaneously provided to a group of specific UEs.
  • a multicast traffic is delivered to the UE using the multicast session.
  • a UE in RRC_CONNECTED can use PTP and/or PTM to receive a multicast traffic.
  • G-RNTI Group RNTI, group RNTI, used to scramble the scheduling and transmission of MTCH (used to scramble the scheduling and transmission of MTCH).
  • NR MBS supports 1-1 mapping between G-RNTI and MBS session (One-to-one mapping between G-RNTI and MBS session is supported in NR MBS).
  • network can be used interchangeably, and the network can be a long-term evolution LTE network, an NR network, an enhanced long-term evolution eLTE network, or other networks defined in subsequent evolution versions of 3GPP.
  • the base station broadcasts the MBMS service and its scheduling information supported by the system information and the message transmitted on the SC-MCCH channel.
  • the radio bearer configuration information used to transmit the MBMS service is predefined .
  • the UE can know the MBMS service that the current cell or base station supports or is in progress by receiving the corresponding system information and the message transmitted on the SC-MCCH.
  • the UE needs to receive a certain MBMS service, it establishes a radio bearer according to predefined parameters and receives data. In this case, UE can receive MBMS service without establishing RRC connection.
  • MBS MBS services
  • some MBS services can also be scheduled in a manner similar to SC-PTM, so that UEs in the RRC idle state and RRC inactive state can also receive the MBS services.
  • MBS services there are another part of MBS services that require the UE to establish an RRC connection with the base station, and then the base station configures for the UE through dedicated RRC signaling (also called a dedicated RRC message), and the radio bearer for receiving these MBS services can also be configured by the base station through dedicated RRC signaling.
  • the order is UE configuration.
  • (a) to (c) of FIG. 1 are schematic diagrams showing specific configurations of radio bearers for receiving MBS services.
  • the radio bearer may be an MRB configured with only PTM transmission (as shown in (a) of Figure 1), or a separate MRB (split MRB) configured with PTM and PTP at the same time (as shown in (b) of Figure 1 ) Or only MRBs for PTP transmission are configured (as shown in (c) of FIG. 1 ). It should be noted that (a)-(c) of FIG. 1 only show the PDCP entity and RLC entity corresponding to the bearer and the relationship between them. In the downlink direction, the PDCP PDU encapsulated by the PDCP entity is delivered to the RLC entity.
  • the base station can dynamically decide whether to use PTM or PTP to transmit the MBS session (or PDCP PDU).
  • PTM RLC and PTP RLC can adopt different modes, for example, PTM RLC is configured as UM RLC and PTP RLC is configured as AM RLC.
  • the PTM RLC of the separate MRB is configured as UM RLC and the PTP RLC is configured as AM RLC, when the corresponding PDCP entity is requested to re-establish, how to re-establish the RLC associated to different modes
  • the PDCP entity of the entity is a problem to be solved.
  • Embodiment 1 The base station instructs the UE to use RRC signaling to reestablish the PDCP entity of the separate MRB associated with the RLC entity of different modes
  • Fig. 2 is a schematic diagram showing the execution method of the user equipment according to the first embodiment.
  • the base station can indicate whether the corresponding PDCP needs to be reestablished by indicating reestablishPDCP through PDCP reestablishment, and indicate the reestablishment mode of the PDCP entity through the first indicator reestablishPDCPAsAMUM different from the PDCP reestablishment indication, and indicate that the PDCP entity is reestablished in UM MRB mode or AM The PDCP entity is rebuilt in MRB mode.
  • the user equipment determines whether the corresponding PDCP needs to be reestablished according to the PDCP reestablishment instruction reestablishPDCP sent by the base station (refer to step S101), and determines the reestablishment mode of the PDCP entity according to the first indication reestablishPDCPAsAMUM different from the PDCP reestablishment instruction sent by the base station (refer to step S102).
  • the first indicator reestablishPDCPAsAMUM can indicate the reestablishment of the PDCP entity in one of the following ways:
  • the received RRC message contains the PDCP reestablishment instruction reestablishPDCP for a separate MRB and the first indicator used to determine the PDCP reestablishment mode, then use the UM MRB method to recreate the PDCP entity; otherwise, use the AM MRB method to recreate the PDCP entity.
  • the value of the first indicator can be true or 1 or other predefined values. When the indicated indicator appears, it means that the PDCP entity is rebuilt in the UM MRB mode.
  • the received RRC message contains the PDCP reestablishment instruction reestablishPDCP for a separate MRB and the first indicator used to determine the PDCP reestablishment mode, then use the AM MRB method to recreate the PDCP entity; otherwise, use the UM MRB method to recreate the PDCP entity.
  • the value of the first indicator can be true or 1 or other predefined values, when the indicated indicator appears, it means that the AM MRB mode is used to rebuild the PDCP entity.
  • the first indicator reestablishPDCPAsAMUM has two value modes, one value is used to indicate that the PDCP entity is reestablished in the UM MRB mode, and the other value is used to indicate the PDCP entity is reestablished in the AM MRB mode.
  • the base station indicates the re-establishment manner of the PDCP entity by setting the first indication flag to a corresponding value.
  • the AM MRB mode is used to reconstruct the PDCP entity; if the received RRC message contains PDCP The reestablishment instruction reestablishPDCP and the first indication flag whose value is the value corresponding to the value corresponding to the reconstruction of the PDCP entity in the UM MRB mode are used to reconstruct the PDCP entity in the UM MRB mode.
  • the PDCP re-establishment indication and the first indication identifier are carried in the same RRC message.
  • the PDCP entity is re-established in the manner indicated by the first indication.
  • the first indicator can only be configured for separate MRBs associated with RLC entities of different modes.
  • reestablishPDCP is used to indicate that the PDCP entity should be re-established (Indicates that PDCP should be re-established.).
  • the PDCP entity may be re-established according to the first indication configuration shown in the above embodiment.
  • Fig. 3 is a schematic diagram showing the execution method of the user equipment in the second embodiment.
  • the base station instructs the reestablishment of the PDCP entity and the reestablishment manner of the PDCP entity by using a second indication identifier reestablishPDCPIndication different from the PDCP reestablishment indication.
  • the user equipment determines the reestablishment of the PDCP entity and the reestablishment mode of the PDCP entity according to the second indicator reestablishPDCPIndication sent by the base station, which is different from the PDCP reestablishment indication (refer to step S201).
  • the second indicator reestablishPDCPIndication has two values, one of which is used to indicate that the PDCP entity is reestablished in the UM MRB manner, and the other value is used to indicate that the PDCP entity is reestablished in the AM MRB manner.
  • the base station indicates the re-establishment of the PDCP entity and the manner of re-establishing the PDCP entity by setting the second indication flag as a corresponding value.
  • the PDCP entity When it is necessary to re-establish the PDCP entity that separates the MRB, the PDCP entity is re-established in the manner indicated by the second indication.
  • the first indicator can only be configured for separate MRBs associated with RLC entities of different modes.
  • Embodiment 2 For separate MRBs associated with RLCs in different modes, pre-define how to recreate the PDCP entity
  • the corresponding PDCP entity when the corresponding PDCP entity receives a request from the upper layer to re-establish the PDCP entity, it re-establishes the PDCP entity in the AM MRB manner.
  • Embodiment 4 for the separate MRBs associated with RLCs in different modes, when the corresponding PDCP entity receives a request from the upper layer to re-establish the PDCP entity, it re-establishes the PDCP entity in the UM MRB manner.
  • Embodiment 5 if the received RRC message configured for the detached MRB includes the PDCP reestablishment indication reestablishPDCP and the information element HFN_Initial for configuring or initializing the HFN, then rebuild the PDCP entity of the detached MRB according to the UM MRB; otherwise, Reconstruct the PDCP entity of the split MRB according to the AM MRB.
  • the base station if the base station wants the UE to re-establish the PDCP entity according to the UM MRB, it must carry the information element HFN_Initial.
  • a new PDCP entity re-establishment method is defined for separate MRBs configured with different RLC modes.
  • Embodiment 6 for separate MRBs configured with different RLC modes, when the corresponding PDCP entity receives a request from the upper layer to reestablish the PDCP entity, at least one of the following operations is performed:
  • the following describes an embodiment of re-establishing a PDCP entity in the AM MRB manner described in the embodiment of the present invention.
  • the operation of performing PDCP entity reconstruction includes at least one of the following:
  • the following describes an embodiment of re-establishing a PDCP entity in the UM MRB manner described in the embodiment of the present invention.
  • the operations to be performed on re-establishing the PDCP entity according to the UM MRB method include at least one of the following:
  • the reconstruction of the PDCP entity in the AM/UM MRB manner may also include other operations not listed in the foregoing embodiments.
  • the PDCP entities described in this disclosure are all receiving PDCP entities (the receiving PDCP entity).
  • mrb-ContinueROHC is used to indicate that the PDCP entity continues or resets the ROHC header compression protocol during the PDCP reconstruction process.
  • mrbContinueEHC_DL indicates that the During the PDCP reconstruction process, the PDCP entity continues or resets the downlink EHC header compression protocol.
  • t-Reordering is used to detect the loss of PDCP data PDUs.
  • COUNT is composed of the superframe number HFN and the PDCP sequence number SN (The COUNT value is composed of a HFN and the PDCP SN), RX_NEXT is the state variable used to indicate the COUNT value of the next PDCP SDU expected to be received, RX_DELIV is used to indicate the state variable of the COUNT value of the first PDCP SDU that has not been delivered to the upper layer but is still waiting to be received, HFN is the Hyper Frame Number.
  • the HFN of the initial value (COUNT) of RX_NEXT and RX_DELIV is determined by HFN_Initial, and the PDCP SN is determined by the sequence number x of the first received PDCP PDU or SDU.
  • the PDCP SN is (x-0.5 ⁇ 2[pdcp-SN-SizeDL -1])modulo(2[pdcp-SN-SizeDL]).
  • pdcp-SN-SizeDL is the downlink PDCP sequence number size (PDCP sequence number size for downlink).
  • Fig. 4 is a brief structural block diagram of the user equipment UE involved in the present invention.
  • the user equipment UE300 includes a processor 301 and a memory 302 .
  • the processor 301 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 302 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories.
  • Memory 302 has program instructions stored thereon. When the instructions are executed by the processor 301, the above method described in detail in the present invention and executed by the user equipment may be executed.
  • the PTM RLC entity is also referred to as the RLC entity associated with PTM or the RLC entity configured with G-RNTI or the RLC entity associated with G-RNTI or the RLC entity used for PTM transmission;
  • the PTP RLC entity is also referred to as PTP The associated RLC entity or the RLC entity used for PTP transport.
  • an MBS service (or MBS session) can be identified by an MBS identifier, and the MBS identifier can be a TMGI and/or a session identifier sessionId, where the TMGI can include a PLMN identifier and/or a service identifier, so The above service identifier uniquely identifies an MBS service within a PLMN.
  • computer-executable instructions or programs running on the device according to the present disclosure may be programs that cause a computer to realize the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU).
  • the program or information processed by the program may be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.
  • Computer-executable instructions or programs for implementing the functions of the various embodiments of the present disclosure can be recorded on computer-readable storage media.
  • the corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
  • the so-called “computer system” here may be a computer system embedded in the device, which may include an operating system or hardware (such as peripheral devices).
  • the "computer-readable storage medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium that dynamically stores a program for a short period of time, or any other recording medium readable by a computer.
  • circuits for example, single-chip or multi-chip integrated circuits.
  • Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSPs digital signal processors
  • ASICs application-specific integrated circuits
  • FPGAs field-programmable gate arrays
  • a general-purpose processor can be a microprocessor, or it can be any existing processor, controller, microcontroller, or state machine.
  • the above-mentioned circuits may be digital circuits or analog circuits. Where new integrated circuit technologies have emerged to replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.
  • present disclosure is not limited to the above-described embodiments. Although various examples of the embodiments have been described, the present disclosure is not limited thereto.
  • Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

Landscapes

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

Abstract

本发明提供一种用户设备的连接方法、基站的传输方法以及用户设备。本发明的用户设备执行的方法，对于关联到不同模式的无线链路控制RLC实体的分离无线承载RB，按照由基站发出的分组数据汇聚协议PDCP重建指示reestablishPDCP来确定相应的PDCP实体是否需要重建，按照由基站发出的不同于PDCP重建指示的第一指示标识reestablishPDCPAsAMUM来确定PDCP实体的重建方式。

Description

用户设备执行的方法、基站的传输方法及用户设备 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及用户设备执行的方法、基站的传输方法及用户设备。
背景技术
一项关于5G组播广播服务架构改进的研究项目SI(具体见SP-190625)已获得批准，并正在进行中。此SI的目标之一(称为目标A)是在5GS中支持通用MBS服务，已经确定的可以受益于此特性的用例包括(但不限于)公共安全、V2X应用，透明IPv4/IPv6组播传输，IPTV，无线软件传输，群组通信和物联网应用。相应的，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#86次全会上，华为提出了NR多播和广播服务(NR MBS)的工作项目(参见非专利文献：RP-193248：New WID：NR Multicast and Broadcast Service)获得批准。该工作项目旨在RAN中提供对目标A的支持。
本公开讨论RAN达成上述工作目标所涉及的相关问题。
发明内容
本发明的目的在于提供一种针对关联到不同模式的无线链路控制RLC的分离无线承载RB，采用不同的方式重建所述关联到不同模式的RLC实体的PDCP实体的用户设备执行的方法、基站的传输方法以及用户设备。
为了解决上述问题，本发明提供了一种用户设备执行的方法，该方法对于关联到不同模式的无线链路控制RLC实体的分离无线承载RB，按照由基站发出的分组数据汇聚协议PDCP重建指示reestablishPDCP来确定相应的PDCP实体是否需要重建，按照由基站发出的不同于PDCP重建指示的第一指示标识reestablishPDCPAsAMUM来确定PDCP实体的重建方式。
根据上述的用户设备执行的方法，如果用户设备接收到的无线资源控制RRC消息中包含针对一个分离无线承载RB的PDCP重建指示reestablishPDCP以及用于确定PDCP重建方式的第一指示标识，则采用非确认模式的无线承载UM RB方式重建PDCP实体；否则，采用确认模式的无线承载AM RB方式重建PDCP实体。
根据上述的用户设备执行的方法，如果用户设备接收到的无线资源控制RRC消息中包含针对一个分离RB的PDCP重建指示reestablishPDCP以及用于确定PDCP重建方式的第一指示标识，则采用确认模式的无线承载AM RB方式重建PDCP实体；否则，采用非确认模式的无线承载UM RB方式重建PDCP实体。
根据上述的用户设备执行的方法，所述第一指示标识reestablishPDCPAsAMUM有两个取值方式，其中一个取值用于指示采用非确认模式的无线承载UM RB方式重建PDCP实体，另一个取值用于指示采用确认模式的无线承载AM RB方式重建PDCP实体，如果用户设备接收到的无线资源控制RRC消息中包含PDCP重建指示reestablishPDCP以及取值为采用确认模式的无线承载AM RB方式重建PDCP实体对应的值的第一指示标识，则采用确认模式的无线承载AM RB方式重建PDCP实体；如果用户设备接收到的RRC消息中包含PDCP重建指示reestablishPDCP以及取值为采用非确认模式的无线承载UM RB方式重建PDCP实体对应的值的第一指示标识，则采用非确认模式的无线承载UM RB方式重建PDCP实体。
本发明的另一种用户设备执行的方法，对于关联到不同模式的无线链路控制RLC的分离无线承载RB，按照由基站发出的不同于分组数据汇聚协议PDCP重建指示的第二指示标识reestablishPDCPIndication来确定PDCP实体重建以及PDCP实体的重建方式。
根据上述的用户设备执行的方法，所述第二指示标识reestablishPDCPIndication有两个取值，其中一个取值用于指示采用非确认模式的无线承载UM RB方式重建PDCP实体，另一个取值用于指示采用确认模式的无线承载AM RB方式重建PDCP实体，通过将第二指示标识设置为相应的值来确定PDCP实体重建以及重建PDCP实体的方式。
本发明的另外一种用户设备执行的方法，对于关联到不同模式的无线链路控制RLC的分离无线承载RB，当对应的分组数据汇聚协议PDCP实体接收到来自上层的重建PDCP实体的请求时，按照确认模式的无线承载AM RB方式重建PDCP实体。
本发明的再一种用户设备执行的方法，对于关联到不同模式的无线链路控制RLC的分离无线承载RB，当对应的分组数据汇聚协议PDCP实体接收到来自上层的重建PDCP实体的请求时，按照非确认模式的无线承载UM RB方式重建PDCP实体。
本发明的基站的传输方法，对于关联到不同模式的无线链路控制RLC的分离无线承载RB，基站通过分组数据汇聚协议PDCP重建指示reestablishPDCP对用户设备指示相应的PDCP是否需要重建、通过不同于PDCP重建指示的第一指示标识reestablishPDCPAsAMUM对用户设备指示PDCP实体的重建方式，或者通过不同于PDCP重建指示的第二指示标识reestablishPDCPIndication来对用户设备指示PDCP实体重建以及PDCP实体的重建方式。
本发明的用户设备，包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行根据权利要求1至8中任一项所述的方法。
发明效果
通过本发明的用户设备的连接方法、基站的传输方法以及用户设备，能够针对关联到不同模式的无线链路控制RLC的分离无线承载RB，采用不同的方式重建所述关联到不同模式的RLC实体的PDCP实体。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1的(a)～(c)是表示接收MBS业务的无线承载的具体配置的示意图。
图2为表示实施例一的用户设备的执行方法的示意图。
图3为表示实施例二的用户设备的执行方法的示意图。
图4是本发明涉及的用户设备UE的简要结构框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语，术语的具体含义可参见3GPP最新相关文档，例如TS38.300、TS38.321、TS38.323、TS38.331等。此外，本公开实施例不限于广播/组播业务，也可以应用于其他应用场景。
UE：User Equipment，用户设备。
RRC：Radio Resource Control，无线资源控制。
RRC_CONNECTED：RRC连接态。
RRC_INACTIVE：RRC非激活态。
RRC_IDLE：RRC空闲态。
RAN：Radio Access Network，无线接入网。
NR：New RAT，新无线访问技术。
MBMS：Multimedia Broadcast/Multicast Service，多媒体广播多播业务。
MBS：Multicast Broadcast Services，多播广播业务。
PDCP：Packet Data Convergence Protocol，分组数据汇聚协议。
RLC：Radio Link Control，无线链路控制。
作为一种示例，RLC可以是确认模式(Acknowledged Mode，AM)的RLC，即AM RLC，也可以是非确认模式(Unacknowledged Mode，UM)的RLC，即UM RLC，还可以是透传模式(Transparent Mode，TM)的RLC，即TM RLC。UM RLC实体被配置为传输UM RLC实体或接收UM RLC实体，并提交或接收RLC数据PDU。AM RLC实体包括传输端和接收端，并提交或接收RLC数据PDU和RLC控制PDU。在AM模式下，RLC实体提交或接收RLC数据PDU和RLC控制PDU(即状态PDU)，所述AM RLC实体接收端采用状态PDU通知对等RLC实体(即另一个AM RLC实体的发送端)关于其成功接收的RLC数据PDU和检测为丢失 的RLC数据PDU。
SDU：Service Data Unit，服务数据单元。将本层从上层接收或递交上层的数据包称为SDU。
PDU：Protocol Data Unit，协议数据单元。将本层从下层接收或递交下层的数据包称为PDU。例如，PDCP数据PDU是PDCP SDU增加PDCP报头后得到的数据包。
RB：Radio Bearer，无线承载。
MRB：MBS无线承载，即一个配置用于MBS多播/广播传输的无线承载(A radio bearer that is configured for MBS multicast/broadcast delivery)。
MCCH：Multicast Control Channel，多播控制信道。MBS-MCCH用于传输与接收MBS服务相关的控制信息。
SC-MCCH：Single Cell Multicast Control Channel，单小区多播控制信道。
TMGI：Temporary Mobile Group Identity，临时移动组标识。
PLMN：Public Land Mobile Network，公众陆地移动网。
RNTI：Radio Network Temporary Identifier，无线网络临时标识。
PTM：Point to Multipoint，点到多点，一种MBS业务的递送(deliver)方式。在PTM递送方式中，RAN节点将一份MBS数据包通过无线电递送给一组UE(a RAN node delivers a single copy of MBS data packets over radio to a set of UEs)。
PTP：Point to Point，点到点，一种MBS业务的递送方式。在PTP递送方式中，RAN节点将多个MBS数据包的副本通过无线电分别递送给每个UE(a RAN node delivers separate copies of MBS data packet over radio to individual UE)。
LTE SC-PTM：LTE Single Cell Point to Multipoint，长期演进单小区点到多点。
MTCH：Multicast Traffic Channel，多播业务信道。MBS组播(或组播通信业务)是指相同的服务和相同的特定内容被同时提供给一组特定的UE。使用组播会话将一个组播通信业务递送给UE。
一个处于RRC_CONNECTED的UE可以采用PTP和/或PTM来接收 一个组播通信业务。
G-RNTI：Group RNTI，群组RNTI，用于加扰MTCH的调度和传输(used to scramble the scheduling and transmission of MTCH)。NR MBS支持G-RNTI和MBS会话之间1-1映射关系(One-to-one mapping between G-RNTI and MBS session is supported in NR MBS)。
本公开中，网络、基站和RAN可互换使用，所述网络可以是长期演进LTE网络、NR网络、增强的长期演进eLTE网络，也可以是3GPP后续演进版本中定义的其他网络。
在LTE SC-PTM中，基站通过系统信息及SC-MCCH信道上传输的消息广播其支持的多媒体广播多播服务MBMS业务及其调度信息，用于传输MBMS业务的无线承载配置信息是预定义的。UE通过接收对应的系统信息和SC-MCCH上传输的消息就可以知道当前小区或基站支持或正在进行的MBMS业务。当UE需要接收某个MBMS业务时，按照预定义的参数建立无线承载并接收数据。在这种情况下，UE不需要建立RRC连接就可以接收MBMS业务。
在NR MBS中，一部分MBS业务(service)也可采用与SC-PTM类似的方式调度，使得处于RRC空闲态和RRC非激活态的UE也可以接收所述MBS业务。但是，还存在另一部分MBS业务需要UE与基站建立RRC连接，然后基站通过专用RRC信令(也称为专用RRC消息)为UE配置，并且接收这些MBS业务的无线承载也可由基站通过专用RRC信令为UE配置。图1的(a)～(c)是表示接收MBS业务的无线承载的具体配置的示意图。所述无线承载可以是仅配置了PTM传输的MRB(如图1的(a)所示)，或者同时配置了PTM和PTP的分离MRB(split MRB)(如图1的(b)所示)或者仅配置了PTP传输的MRB(如图1的(c)所示)。需要说明的是，图1的(a)-(c)仅示出了承载对应的PDCP实体和RLC实体以及两者间的关系。在下行方向上，经PDCP实体封装后的PDCP PDU递交给RLC实体。对于分离MRB，基站可以动态的决定采用PTM还是PTP传输MBS会话(或PDCP PDU)。对于图1b所示的分离MRB，PTM RLC和PTP RLC可以采用不同的模式，例如PTM RLC被配置为UM RLC，PTP RLC被配置为AM RLC。
对于配置了不同RLC模式的分离MRB，例如分离MRB的PTM RLC被配置为UM RLC并且PTP RLC被配置为AM RLC，当对应的PDCP实体被请求重建时，如何重建所述关联到不同模式的RLC实体的PDCP实体是需要解决的问题。
以下提供四种实施方式解决上述问题。需要说明的是本发明实施例以配置了不同RLC模式的分离MRB为例进行描述，但是本发明实施例也可以应用于其他配置了不同RLC模式的分离RB。
实施方式一 基站通过RRC信令指示UE采用何种方式重建关联到不同模式的RLC实体的分离MRB的PDCP实体
图2为表示实施例一的用户设备的执行方法的示意图。实施例一中，基站可以通过PDCP重建指示reestablishPDCP指示相应的PDCP是否需要重建，通过不同于PDCP重建指示的第一指示标识reestablishPDCPAsAMUM指示PDCP实体的重建方式，指示采用UM MRB方式重建PDCP实体或采用AM MRB方式重建PDCP实体。用户设备按照基站发出的PDCP重建指示reestablishPDCP确定相应的PDCP是否需要重建(参照步骤S101)，按照基站发出的不同于PDCP重建指示的第一指示标识reestablishPDCPAsAMUM确定PDCP实体的重建方式(参照步骤S102)。
第一指示标识reestablishPDCPAsAMUM可以通过以下方式之一指示PDCP实体的重建：
(1)如果接收到的RRC消息中包含针对一个分离MRB的PDCP重建指示reestablishPDCP以及用于确定PDCP重建方式的第一指示标识，则采用UM MRB方式重建PDCP实体；否则，采用AM MRB方式重建PDCP实体。第一指示标识的取值可以为真或1或其他预定义的值，当所示指示标识出现，表示采用UM MRB方式重建PDCP实体。
(2)如果接收到的RRC消息中包含针对一个分离MRB的PDCP重建指示reestablishPDCP以及用于确定PDCP重建方式的第一指示标识，则采用AM MRB方式重建PDCP实体；否则，采用UM MRB方式重建PDCP实体。第一指示标识的取值可以为真或1或其他预定义的值，当所示指示 标识出现，表示采用AM MRB方式重建PDCP实体。
(3)第一指示标识reestablishPDCPAsAMUM有两个取值方式，其中一个取值用于指示采用UM MRB方式重建PDCP实体，另一个取值用于指示采用AM MRB方式重建PDCP实体。基站通过将第一指示标识设置为相应的值来指示PDCP实体的重建方式。如果接收到的RRC消息中包含PDCP重建指示reestablishPDCP以及取值为采用AM MRB方式重建PDCP实体对应的值的第一指示标识，则采用AM MRB方式重建PDCP实体；如果接收到的RRC消息中包含PDCP重建指示reestablishPDCP以及取值为采用UM MRB方式重建PDCP实体对应的值的第一指示标识，则采用UM MRB方式重建PDCP实体。
PDCP重建指示和第一指示标识携带在同一RRC消息中。当需要重建分离MRB的PDCP实体时，按照第一指示标识指示的方式重建PDCP实体。
可以规定，第一指示标识仅可以为关联到不同模式的RLC实体的分离MRB配置。
其中，reestablishPDCP用于指示PDCP实体应该重建(Indicates that PDCP should be re-established.)。
需要说明的是，除了通过PDCP重建指示触发PDCP重建外，其他事件触发配置了不同RLC模式的分离MRB的PDCP重建时，可以根据上述实施例中所示第一指示标识配置的方式重建PDCP实体。
图3为表示实施例二的用户设备的执行方法的示意图。在实施例二中，基站通过不同于PDCP重建指示的第二指示标识reestablishPDCPIndication指示PDCP实体重建以及PDCP实体的重建方式。用户设备按照基站发出的不同于PDCP重建指示的第二指示标识reestablishPDCPIndication来确定PDCP实体重建以及PDCP实体的重建方式(参照步骤S201)。所述第二指示标识reestablishPDCPIndication有两个取值，其中一个取值用于指示采用UM MRB方式重建PDCP实体，另一个取值用于指示采用AM MRB方式重建PDCP实体。基站通过将第二指示标识设置为相应的值来指示PDCP实体重建以及重建PDCP实体的方式。
当需要重建分离MRB的PDCP实体时，按照第二指示标识指示的方 式重建PDCP实体。
可以规定，第一指示标识仅可以为关联到不同模式的RLC实体的分离MRB配置。
实施方式二 对于关联到不同模式的RLC的分离MRB，预定义采用何种方式重建PDCP实体
在实施例三中，对于关联到不同模式的RLC的分离MRB，当对应的PDCP实体接收到来自上层的重建PDCP实体的请求时，按照AM MRB方式重建PDCP实体。
在实施例四中，对于关联到不同模式的RLC的分离MRB，当对应的PDCP实体接收到来自上层的重建PDCP实体的请求时，按照UM MRB方式重建PDCP实体。
实施方式三
在实施例五中，如果接收到的针对分离MRB配置的RRC消息中包含PDCP重建指示reestablishPDCP以及用于配置或初始化HFN的信息元素HFN_Initial，则按照UM MRB重建所述分离MRB的PDCP实体；否则，按照AM MRB重建所述分离MRB的PDCP实体。
在本实施例中，如果基站希望UE按照UM MRB重建PDCP实体，则必须携带信息元素HFN_Initial。
实施方式四
为配置了不同RLC模式的分离MRB定义一种新的PDCP实体重建方式。
在实施例六中，对于配置了不同RLC模式的分离MRB，当其对应的PDCP实体接收到来自上层的重建PDCP实体的请求时，执行以下操作至少一项：
(1)如果没有配置mrbContinueEHC_DL，对所有存储的PDCP SDU采用EHC执行头解压(perform header decompression using EHC for all stored PDCP SDUs if drbContinueEHC-DL is not configured)。
(2)如果没有配置mrb-ContinueROHC，对所有存储的PDCP SDU采用ROHC执行头解压(perform header decompression using ROHC for all stored PDCP SDUs if drbContinueROHC is not configured)。
(3)如果配置了HFN的初始值HFN_Initial，并且如果t-Reordering正在运行，停止并重置(reset)t-Reordering，在进行头解压后按照COUNT升序向上层交付所有存储的PDCP SDU(deliver all stored PDCP SDUs to the upper layers in ascending order of associated COUNT values after performing header decompression)。
(4)如果配置了HFN的初始值HFN_Initial，则RX_NEXT和RX_DELIV设置为初始值。
以下描述本发明实施例中所述的采用AM MRB方式重建PDCP实体的实施例。
按照AM MRB方式重建PDCP实体执行PDCP实体重建的操作包括以下至少一项：
(1)如果没有配置mrbContinueEHC_DL，对所有存储的PDCP SDU采用EHC执行头解压(perform header decompression using EHC for all stored PDCP SDUs if drbContinueEHC-DL is not configured)。
(2)如果没有配置mrb-ContinueROHC，对所有存储的PDCP SDU采用ROHC执行头解压(perform header decompression using ROHC for all stored PDCP SDUs if drbContinueROHC is not configured)。
以下描述本发明实施例中所述的采用UM MRB方式重建PDCP实体的实施例。
按照UM MRB方式重建PDCP实体执行的操作包括以下至少一项：
(1)如果定时器t-Reordering正在运行，则停止并重置t-Reordering(stop and reset t-Reordering)，在执行头解压缩后，按照COUNT值升序方式向上层交付所有存储的PDCP SDU(for UM DRBs，deliver all stored PDCP SDUs to the upper layers in ascending order of associated COUNT values after performing header decompression)。
(2)设置RX_NEXT和RX_DELIV为初始值。
需要说明的是，按照AM/UM MRB方式重建PDCP实体还可以包括未在上述实施例中列出的其他操作。此外，本公开中所述的PDCP实体都是接收PDCP实体(the receiving PDCP entity)。
此外，以下简要地描述在本公开实施例中涉及的参数的含义，具体可见3GPP最新技术规范，mrb-ContinueROHC用于指示在PDCP重建过程中PDCP实体继续或重置ROHC头压缩协议，mrbContinueEHC_DL指示在PDCP重建过程中PDCP实体继续或重置下行EHC头压缩协议，t-Reordering用于检测PDCP数据PDU的丢失，COUNT由超帧号HFN和PDCP序列号SN组成(The COUNT value is composed of a HFN and the PDCP SN)，RX_NEXT是用于指示下一个期望接收到的PDCP SDU的COUNT值的状态变量，RX_DELIV用于指示第一个未交付上层但仍在等待接收的PDCP SDU的COUNT值的状态变量，HFN是超帧号(Hyper Frame Number)。RX_NEXT和RX_DELIV的初始值(COUNT)的HFN由HFN_Initial确定，PDCP SN由第一个接收到的PDCP PDU或SDU的序列号x确定，例如PDCP SN为(x-0.5×2[pdcp-SN-SizeDL-1])modulo(2[pdcp-SN-SizeDL])。pdcp-SN-SizeDL是下行PDCP序列号大小(PDCP sequence number size for downlink)。
图4是本发明涉及的用户设备UE的简要结构框图。如图4所示，该用户设备UE300包括处理器301和存储器302。处理器301例如可以包括微处理器、微控制器、嵌入式处理器等。存储器302例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器302上存储有程序指令。该指令在由处理器301运行时，可以执行本发明详细描述的由用户设备执行的上述方法。
本公开实施例中PTM RLC实体也称为PTM关联的RLC实体或配置了G-RNTI的RLC实体或关联了G-RNTI的RLC实体或用于PTM传输的RLC实体；PTP RLC实体也称为PTP关联的RLC实体或用于PTP传输的RLC实体。
需要说明的是，一个MBS业务(或称为MBS会话)可通过一个MBS标识来标识，所述MBS标识可以是TMGI和/或会话标识sessionId，其中 TMGI可以包括PLMN标识和/或服务标识，所述服务标识在一个PLMN内唯一标识一个MBS业务。
另外，运行在根据本公开的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本公开各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本公开的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本公开也包括不偏离本公开主旨的任何设计改动。另外，可以在权利要求的范围内对本公开进行多种改动，通过适 当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (2)

  1. 一种用户设备，包含：
    处理单元，被配置为接收来自上层的分组数据汇聚协议PDCP实体重建请求，
    如果所述PDCP实体是分离多播广播业务无线承载MRB的PDCP实体，则所述分离MRB的点到多点PTM无线链路控制RLC被配置为非确认模式UM RLC并且点到点PTP RLC被配置为确认模式AM RLC，并且
    如果所述分离MRB没有被配置指示在PDCP重建过程中PDCP实体继续或重置ROHC头压缩协议的字段，则对所有存储的PDCP服务数据单元SDU采用ROHC执行头解压缩。
  2. 一种用户设备，包含：
    处理单元，被配置为接收来自上层的分组数据汇聚协议PDCP实体重建请求，
    如果所述PDCP实体是分离多播广播业务无线承载MRB的PDCP实体，则所述分离MRB的点到多点PTM无线链路控制RLC被配置为非确认模式UM RLC并且点到点PTP RLC被配置为确认模式AM RLC，并且
    如果所述分离MRB没有被配置指示在PDCP重建过程中PDCP实体继续或重置EHC头压缩协议的字段，则对所有存储的PDCP服务数据单元SDU采用EHC执行头解压缩。
PCT/CN2022/118073 2021-09-10 2022-09-09 用户设备执行的方法、基站的传输方法及用户设备 WO2023036287A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22866748.1A EP4401463A1 (en) 2021-09-10 2022-09-09 Method performed by user equipment, transmission method for base station, and user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111065941.X 2021-09-10
CN202111065941.XA CN115802416A (zh) 2021-09-10 2021-09-10 用户设备执行的方法、基站的传输方法及用户设备

Publications (1)

Publication Number Publication Date
WO2023036287A1 true WO2023036287A1 (zh) 2023-03-16

Family

ID=85417249

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/118073 WO2023036287A1 (zh) 2021-09-10 2022-09-09 用户设备执行的方法、基站的传输方法及用户设备

Country Status (3)

Country Link
EP (1) EP4401463A1 (zh)
CN (1) CN115802416A (zh)
WO (1) WO2023036287A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729269A (zh) * 2008-10-16 2010-06-09 中兴通讯股份有限公司 一种多媒体广播组播业务实现方法、系统和承载选择方法
CN101867879A (zh) * 2003-08-21 2010-10-20 高通股份有限公司 广播/多播内容的外部编码方法及其相关装置
CN110431876A (zh) * 2017-08-10 2019-11-08 Lg电子株式会社 在无线通信系统中执行与um rlc实体相关联的pdcp实体的重建的方法及其设备
US20200260524A1 (en) * 2019-02-12 2020-08-13 Samsung Electronics Co., Ltd Methods and apparatuses for transmitting and receiving data in wireless communication system
CN115038049A (zh) * 2021-03-05 2022-09-09 维沃移动通信有限公司 多播业务的接收方法、配置方法、终端及网络侧设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101867879A (zh) * 2003-08-21 2010-10-20 高通股份有限公司 广播/多播内容的外部编码方法及其相关装置
CN101729269A (zh) * 2008-10-16 2010-06-09 中兴通讯股份有限公司 一种多媒体广播组播业务实现方法、系统和承载选择方法
CN110431876A (zh) * 2017-08-10 2019-11-08 Lg电子株式会社 在无线通信系统中执行与um rlc实体相关联的pdcp实体的重建的方法及其设备
US20200260524A1 (en) * 2019-02-12 2020-08-13 Samsung Electronics Co., Ltd Methods and apparatuses for transmitting and receiving data in wireless communication system
CN115038049A (zh) * 2021-03-05 2022-09-09 维沃移动通信有限公司 多播业务的接收方法、配置方法、终端及网络侧设备

Also Published As

Publication number Publication date
EP4401463A1 (en) 2024-07-17
CN115802416A (zh) 2023-03-14

Similar Documents

Publication Publication Date Title
US12010592B2 (en) Sidelink communications method and apparatus
WO2022085640A1 (ja) 端末装置、基地局装置、および方法
WO2021221009A1 (ja) 端末装置、方法、および、集積回路
WO2023036287A1 (zh) 用户设备执行的方法、基站的传输方法及用户设备
WO2022085664A1 (ja) 端末装置、基地局装置、および方法
WO2022080300A1 (ja) 端末装置および方法
WO2022131342A1 (ja) 端末装置、基地局装置、および、方法
WO2022138450A1 (ja) 通信制御方法及びユーザ装置
JP2023126994A (ja) 端末装置、基地局装置、方法、および、集積回路
JP2023130533A (ja) 端末装置、基地局装置、方法、および、集積回路
WO2023001240A1 (zh) 由用户设备ue执行的方法及用户设备
WO2024120476A1 (zh) 由用户设备执行的方法以及用户设备
WO2023036173A1 (zh) 状态报告发送方法、无线承载重传执行方法及用户设备
WO2023066188A1 (zh) 进行小区切换的方法及用户设备
JP7481588B2 (ja) 通信方法、ユーザ装置、移動通信システム、チップセット、及びプログラム
WO2022138567A1 (ja) 端末装置、基地局装置、および方法
WO2022080301A1 (ja) 端末装置および方法
WO2024120475A1 (zh) 恢复rrc连接的方法以及用户设备
WO2022080304A1 (ja) 端末装置、基地局装置、および方法
JP7494064B2 (ja) 端末装置、基地局装置、方法、および、集積回路
JP7469571B2 (ja) 通信方法、ユーザ装置、ネットワークノード、チップセット、及びプログラム
WO2022080339A1 (ja) 端末装置および方法
WO2022255293A1 (ja) 端末装置、基地局装置、および方法
WO2022255279A1 (ja) 端末装置、基地局装置、および方法
WO2024032500A1 (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: 22866748

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022866748

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022866748

Country of ref document: EP

Effective date: 20240410