WO2023060402A1 - Procédé et appareil pour des services de multidiffusion et de diffusion - Google Patents

Procédé et appareil pour des services de multidiffusion et de diffusion Download PDF

Info

Publication number
WO2023060402A1
WO2023060402A1 PCT/CN2021/123129 CN2021123129W WO2023060402A1 WO 2023060402 A1 WO2023060402 A1 WO 2023060402A1 CN 2021123129 W CN2021123129 W CN 2021123129W WO 2023060402 A1 WO2023060402 A1 WO 2023060402A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
hfn
value
wrapping around
indicated
Prior art date
Application number
PCT/CN2021/123129
Other languages
English (en)
Inventor
Mingzeng Dai
Jing HAN
Yibin ZHUO
Lianhai WU
Le Yan
Original Assignee
Lenovo (Beijing) Limited
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 Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2021/123129 priority Critical patent/WO2023060402A1/fr
Publication of WO2023060402A1 publication Critical patent/WO2023060402A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • 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

Definitions

  • Embodiments of the present application generally relate to wireless communication technology, especially to a method and apparatus for multicast and broadcast services (MBS) .
  • MMS multicast and broadcast services
  • NR new radio
  • the MBS plans to focus on a small area mixed mode multicast (also referred to as Objective A in the TR 23.757) .
  • the Objective A is about enabling general MBS services over 5G system (5GS) and the identified use cases that could benefit from this feature.
  • These use cases include but are not limited to: public safety and mission critical, vehicle to everything (V2X) applications, transparent internet protocol version 4 (IPv4) /internet protocol version 6 (IPv6) multicast delivery, internet protocol television (IPTV) , software delivery over wireless, group communications and internet of things (IoT) applications.
  • V2X vehicle to everything
  • IPv4 transparent internet protocol version 4
  • IPv6 internet protocol version 6
  • IPTV internet protocol television
  • IoT internet of things
  • the packet data convergence protocol (PDCP) entity is common for the point to multipoint (PTM) leg and point to point (PTP) leg. Since the PTM leg is used for multicast session (s) for multiple user equipment (UE) , for a UE later joining the multicast session (s) , PDCP related initial values for each state variables cannot always be “0” as legacy unicast, regardless of whether the first received MBS data packet comes from the PTM leg or PTP leg.
  • the PDCP related initial values include the initial value for PDCP sequence number (SN) and PDCP hyper frame number (HFN) , wherein the initial value of PDCP HFN can be indicated by a gNB.
  • the UE may receive the indicated initial value of PDCP HFN after the PDCP SN wrapping around while the gNB sent it before the SN wrapping around. Then, the indicated initial value of PDCP HFN used as the initial PDCP HFN value by the UE should be the indicated PDCP HFN value plus one rather than the indicated PDCP HFN value, which causes the PDCP HFN desynchronization between the UE and gNB.
  • the industry desires an improved technology for multicast and broadcast services, so as to avoid PDCP HFN desynchronization between the remote side and the network side for a multicast radio bearer (MRB) in MBS caused by PDCP SN wrapping around.
  • MRB multicast radio bearer
  • Embodiments of the present application at least provide a technical solution for multicast and broadcast services, especially providing a technical solution on setting the initial value of PDCP SN and PDCP HFN by UE for an MRB.
  • a UE may include: a processor; and a transceiver coupled to the processor; wherein the processor is configured to: receive, via the transceiver, PDCP information associated with an MRB from a network apparatus; determine if there is an existence of overflow of PDCP SN based on the PDCP information received from the network apparatus; and in response to determining the existence of the overflow of the PDCP SN or not, determine PDCP HFN information associated with the PDCP SN
  • a method for MBS may include: receiving, PDCP information associated with an MRB from a network apparatus; determining if there is an existence of overflow of PDCP SN based on the PDCP information received from the network apparatus; and in response to determining the existence of the overflow of the PDCP SN or not, determining PDCP HFN information associated with the PDCP SN
  • the PDCP information includes information associated with determining PDCP SN wrapping around and an indicated PDCP HFN value, and the PDCP HFN information is a PDCP HFN initial value.
  • the existence of overflow of PDCP SN means that PDCP SN wrapping around has happened.
  • the PDCP HFN initial value is determined as the indicated PDCP HFN value plus one; and in the case that the PDCP SN wrapping around did not happen, the PDCP HFN initial value is determined as the indicated PDCP HFN value.
  • the information associated with determining PDCP SN wrapping around is a reference PDCP SN value, and in the case that the reference PDCP SN value is larger than or equal to a PDCP SN value of a first received data packet, the UE determines that the PDCP SN wrapping around did not happen; otherwise, the UE determines that the PDCP SN wrapping around has happened.
  • the information associated with determining PDCP SN wrapping around is a PDCP SN window value
  • the PDCP SN window value indicates a data packet number before receiving the indicated PDCP HFN value or indicates a data packet number before receiving a first data packet via the MRB
  • a PDCP SN value of a first received data packets minus the PDCP SN window value is larger than 0, the UE determines that the PDCP SN wrapping around did not happen; otherwise, the UE determines that the PDCP SN wrapping around has happened.
  • the PDCP HFN initial value is determined as the indicated PDCP HFN value; and in the case that the PDCP SN wrapping around did not happen, the PDCP HFN initial value is determined as the indicated PDCP HFN value minus one.
  • the information associated with determining PDCP SN wrapping around is a reference PDCP SN value, and in the case that the reference PDCP SN value is larger than or equal to a PDCP SN value of a first received data packet, the UE determines that the PDCP SN wrapping around did not happen; otherwise, the UE determines that the PDCP SN wrapping around has happened.
  • the information associated with determining PDCP SN wrapping around is a PDCP SN window value
  • the PDCP SN window value indicates a data packet number before receiving the indicated PDCP HFN value or indicates a data packet number before receiving a first data packet via the MRB
  • a PDCP SN value of a first received data packets minus the PDCP SN window value is larger than 0, the UE determines that the PDCP SN wrapping around did not happen; otherwise, the UE determines that the PDCP SN wrapping around has happened.
  • the UE is further configured to:transmit a PDCP HFN desynchronization indication to the network apparatus to indicate that PDCP HFN desynchronization happened in the UE.
  • the PDCP HFN desynchronization indication is transmitted in a PDCP status report.
  • the network apparatus is a base station
  • the PDCP information is transferred to the UE by a distributed unit (DU) of the base station from a central unit (CU) of the base station.
  • DU distributed unit
  • CU central unit
  • a network apparatus may include: a processor; and a transceiver coupled to the processor; wherein the processor is configured to: transmit, via the transceiver, PDCP information associated with an MRB from a network apparatus, wherein the PDCP information is used for the UE to determine if there is an overflow of PDCP SN to adjust PDCP HFN information associated with the PDCP SN; and transmit data packets via the MRB to the UE
  • the network apparatus is further configured to receive a PDCP HFN desynchronization indication from the UE, which indicates that PDCP HFN desynchronization happened in the UE.
  • the PDCP HFN desynchronization indication can be received in a PDCP status report.
  • the network apparatus is a base station; a central unit control plane (CU-CP) unit of the CU of the base station transmits both a requiring indication for information associated with determining PDCP SN wrapping around and an indicated PDCP HFN value required indication, or only an indicated PDCP HFN value required indication, to a central unit user plane (CU-UP) unit of the CU; and the CU-UP unit transmits both the information associated with determining PDCP SN wrapping around in response to the requiring indication for information associated with determining PDCP SN wrapping around and the indicated PDCP HFN value in response to the indicated PDCP HFN value required indication, or only the indicated PDCP HFN value in response to the indicated PDCP HFN value required indication, to the CU-UP unit.
  • CU-CP central unit control plane
  • Embodiments of the present application provide a technical solution for multicast and broadcast services, which can at least ensure the UE to correctly set the initial value of PDCP SN and PDCP HFN for an MRB and avoid the PDCP HFN desynchronization between the remote side and the network side.
  • FIG. 1 is a schematic diagram illustrating an exemplary wireless communication system according to some embodiments of the present application.
  • FIG. 2 is a schematic diagram illustrating an internal structure of a BS according to some embodiments of the present application.
  • FIG. 3 is a schematic diagram illustrating an internal structure of a BS according to some other embodiments of the present application.
  • FIG. 4 is a schematic diagram illustrating the PDCP HFN desynchronization between the UE and gNB.
  • FIG. 5 is a flow chart illustrating a method for MBS according to some embodiments of the present application.
  • FIG. 6 is a schematic diagram illustrating a PDCP HFN initial value determination solution according to some embodiments of the present application.
  • FIG. 7 is a schematic diagram illustrating a PDCP HFN initial value determination solution according to some other embodiments of the present application.
  • FIG. 8 illustrates an exemplary format of a PDCP status report according to some embodiments of the present application.
  • FIG. 9 is a flow chart illustrating an exemplary procedure of a method for MBS considering the internal structure of a BS according to some embodiments of the present application.
  • FIG. 10 illustrates a simplified block diagram of an apparatus for MBS according to some embodiments of the present application.
  • FIG. 11 illustrates a simplified block diagram of an apparatus for MBS according to some other embodiments of the present application.
  • FIG. 1 illustrates a schematic diagram of an exemplary wireless communication system 100 according to some embodiments of the present application.
  • the wireless communication system 100 includes at least one BS 101 and at least one UE 102.
  • the wireless communication system 100 includes one BS 101 and two UE 102 (e.g., a UE 102a and UE 102b) for illustrative purpose.
  • UE 102a and UE 102b e.g., a UE 102a and UE 102b
  • FIG. 1 a specific number of BSs and UEs are illustrated in FIG. 1 for simplicity, it is contemplated that the wireless communication system 100 may include more or less BSs and UEs in some other embodiments of the present application.
  • the wireless communication system 100 is compatible with any type of network that is capable of sending and receiving wireless communication signals.
  • the wireless communication system 100 is compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, an LTE network, a 3GPP-based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • the BS 101 may communicate with a core network (CN) node (not shown) , e.g., a mobility management entity (MME) or a serving gateway (S-GW) , a mobility management function (AMF) or a user plane function (UPF) etc. via an interface.
  • CN core network
  • MME mobility management entity
  • S-GW serving gateway
  • AMF mobility management function
  • UPF user plane function
  • a BS also be referred to as an access point, an access terminal, a base, a macro cell, a node-B, an enhanced node B (eNB) , a gNB, a home node-B, a relay node, or a device, or described using other terminology used in the art.
  • a BS may also refer to as a radio access network (RAN) node.
  • RAN radio access network
  • Each BS may serve a number of UE (s) within a serving area, for example, a cell or a cell sector via a wireless communication link.
  • Neighbor BSs may communicate with each other as necessary, e.g., during a handover procedure for a UE.
  • the UE 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • computing devices such as desktop computers, laptop computers, personal digital assistants (PDAs) , tablet computers, smart televisions (e.g., televisions connected to the Internet) , set-top boxes, game consoles, security systems (including security cameras) , vehicle on-board computers, network devices (e.g., routers, switches, and modems) , or the like.
  • the UE may include a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • the UE may include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • the UE may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art.
  • FIG. 2 is a schematic diagram illustrating an internal structure of a RAN node, e.g., a BS according to some embodiments of the present application.
  • the internal structure of a RAN node may be split into a CU 200 and at least one DU 202 (e.g., two DUs shown in FIG. 2) .
  • a RAN node e.g., BS 101
  • DU 202 e.g., two DUs shown in FIG. 2
  • FIG. 2 a specific number of DUs 202 are depicted in FIG. 2, it is contemplated that any number of DUs 202 may be included in the BS.
  • the CU 200 and DU 202 are connected with each other by an interface called F1 as specified in 3GPP standard documents.
  • the RRC layer functionality, service data adaptation protocol (SDAP) functionality, and the PDCP layer functionality (or PDCP entity) are located in the CU 200.
  • the radio link control (RLC) layer functionality, medium access control (MAC) layer functionality, and the physical (PHY) layer functionality are located in the DU 202.
  • the CU may be further separated into a CU-CP unit and at least one CU-UP unit.
  • FIG. 3 is a schematic diagram illustrating an internal structure of a BS according to some other embodiments of the present application.
  • the CU is separated into a CU-CP unit and at least one CU-UP unit.
  • the CU-CP unit and each CU-UP unit may be connected with each other by an interface called E1 as specified in 3GPP standard documents.
  • the CU-CP unit and the DU are connected by an interface called F1-C as specified in 3GPP documents.
  • Each CU-UP unit and the DU are connected by an interface called F1-U as specified in 3GPP standard documents.
  • the CU-UP unit may map the MBS session into one or more MRBs. The mapping is performed by a QoS flow to MRB mapping in the SDAP layer. For example, at least one QoS flow of the session may be mapped to an MRB.
  • a split MBS RB (e.g., MRB) includes both PTM transmission and PTP transmission.
  • PTP transmission also referred to as PTP leg or PTP mode
  • a gNB utilizes a UE-specific RLC entity, MAC entity and physical layer to individually generate and deliver separate copies of MBS data packets to each UEs independently, and uses physical downlink control channel (PDCCH) with cyclic redundancy check (CRC) scrambled by UE-specific radio network temporary identifier (RNTI) (e.g., C-RNTI) to schedule UE-specific physical downlink shared channel (PDSCH) scrambled with the same UE-specific RNTI.
  • PDCCH physical downlink control channel
  • CRC cyclic redundancy check
  • RNTI radio network temporary identifier
  • a gNB utilizes a group RLC entity, MAC entity and physical layer to generate and deliver copies of MBS data packets to a set of UEs and uses group-common PDCCH with CRC scrambled by group-common RNTI to schedule group-common PDSCH scrambled with the same group-common RNTI.
  • the UE needs to know the initial values of PDCP state variables.
  • the receiving PDCP entity shall maintain the following PDCP state variables:
  • This state variable indicates the COUNT value of the next PDCP SDU expected to be received.
  • the initial value is 0, except for sidelink broadcast and groupcast, and for SRBs configured with state variables continuation.
  • the initial value of the SN part of RX_NEXT is (x +1) modulo (2 [sl-PDCP-SN-Size] ) , where x is the SN of the first received PDCP Data PDU.
  • the initial value is the value stored in PDCP entity for the corresponding source SRB.
  • source SRB configured with state variables continuation the initial value is the value stored in PDCP entity for the corresponding target SRB.
  • This state variable indicates the COUNT value of the first PDCP SDU not delivered to the upper layers, but still waited for.
  • the initial value is 0, except for sidelink broadcast and groupcast, and for SRBs configured with state variables continuation.
  • the initial value of the SN part of RX_DELIV is (x –0.5 ⁇ 2 [sl-PDCP-SN-Size–1] ) modulo (2 [sl-PDCP-SN-Size] ) , where x is the SN of the first received PDCP Data PDU.
  • the initial value is the value stored in PDCP entity for the corresponding source SRB.
  • For source SRB configured with state variables continuation the initial value is the value stored in PDCP entity for the corresponding target SRB.
  • FIG. 4 illustrates the issue of PDCP HFN desynchronization between the UE and gNB in one option.
  • the PDCP SN part of COUNT values of the PDCP states variables are set by the UE according to the PDCP SN of the first received packet and the PDCP HFN indicated by the gNB. That is, the UE can set the initial value of PDCP HFN as that indicated by the gNB.
  • the value range of PDCP SN is 0... 1023.
  • the PDCP SN wraps around for every 1024 packets (e.g., PDCP SDUs) .
  • the PDCP HFN will increase one.
  • the initial value of PDCP HFN e.g., N sent by the gNB before the PDCP SN wrapping around may be received by the UE after the PDCP SN wrapping around.
  • the indicated PDCP HFN e.g., N used by the UE as the initial PDCP HFN may be different from the real PDCP HFN, which should be N+1, and PDCP HFN desynchronization happened between the UE and gNB.
  • embodiments of the present application propose an improved technical solution for MBS, especially an improved technical solution for correctly setting the initial value of PDCP HFN for an MRB by the UE.
  • the PDCP SN and PDCP HFN refer to the PDCP SN and PDCP HFN.
  • FIG. 5 illustrates a flow chart of a method for MBS according to some embodiments of the present application.
  • the method is illustrated in a system level by an apparatus in a remote side (or a UE side) and an apparatus in a network side (or a BS side) , persons skilled in the art should understand that the method implemented in the remote side and that implemented in the network side can be separately implemented and incorporated by other apparatus with the like functions.
  • an apparatus in the network side may transmit PDCP information associated with an MRB to the apparatus in the remote side (also referred to as a remote apparatus or terminal device etc. ) , e.g., the UE 102a or 102b in FIG. 1.
  • the UE will receive the PDCP information for the MRB.
  • the PDCP information is used for the UE to determine if there is an overflow of PDCP SN to adjust PDCP HFN information associated with the PDCP SN.
  • the network apparatus may transmit data packets via the MRB to the UE.
  • the UE will determine if there is an existence of overflow of PDCP SN based on the PDCP information received from the network apparatus in step 504.
  • the UE in response to determining the existence of the overflow of the PDCP SN or not, the UE will determine PDCP HFN information associated with the PDCP SN .
  • the PDCP information includes information associated with determining PDCP SN wrapping around and an indicated PDCP HFN value
  • the PDCP HFN information is a PDCP HFN initial value.
  • the existence of overflow of PDCP SN means that PDCP SN wrapping has happened.
  • he information associated with determining PDCP SN wrapping around is for determining whether PDCP SN wrapping around has happened by the UE to further determine a PDCP HFN initial value for the MRB based on the indicated PDCP HFN value.
  • Embodiments of the present application provide various manners for indicating the information associated with determining PDCP SN wrapping around, e.g., by a reference PDCP SN value or by a PDCP SN window value etc., which will be specifically illustrated in the following text.
  • the information associated with determining PDCP SN wrapping around and the indicated PDCP HFN value can be transmitted to the UE together in a RRC signaling (e.g. with a MBS configuration) , or in a PDCP control PDU, or separate transmitted to the UE.
  • the network apparatus may separately indicate information associated with determining PDCP SN wrapping around and the indicated PDCP HFN value to the UE by separate higher layer signaling, e.g., separate RRC signaling.
  • the network apparatus may separately indicate information associated with determining PDCP SN wrapping around and the indicated PDCP HFN value to the UE by separate signaling, e.g. one is transmitted by RRC signaling and the other is transmitted by the PDCP control PDU.
  • the UE will determine a PDCP HFN initial value for a receiving data packet of the MRB from the network apparatus based on the information associated with determining PDCP SN wrapping around and the indicated PDCP HFN value.
  • the determined PDCP HFN initial value can be used for determining the PDCP SNPDCP COUNT value, and can also be used for PDCP status report and security operation.
  • a field "First Missing Count" (FMC) is included for indicating the COUNT value of the first missing PDCP SDU within the reordering window.
  • data packet (or packet) means any MBS packet, and should not be limited pure data packet.
  • the information associated with determining PDCP SN wrapping around is a reference PDCP SN value. That is, a reference PDCP SN value will be configured and transmitted to the UE with the indicated PDCP HFN value by the network apparatus, e.g., the gNB.
  • the indicated PDCP HFN value e.g., N
  • the indicated PDCP HFN value is configured to be received before a PDCP SN wrapping around while it is received after the PDCP SN wrapping around. Then, when the reference PDCP SN value is larger than or equal to a PDCP SN value of the first received data packet, the UE determines that the PDCP SN wrapping around did not happen. Otherwise, i.e., when the reference PDCP SN value is smaller than the PDCP SN value of the first received data packet, the UE determines that the PDCP SN wrapping around has happened.
  • the PDCP HFN initial value for the MRB will be determined as the indicated PDCP HFN value plus one, e.g., N+1.
  • the UE can increase the initial value of PDCP HFN by 1 or directly set the initial value of PDCP HFN as the value of the indicated PDCP HFN increased by 1.
  • the PDCP HFN initial value will be determined as the indicated PDCP HFN value, e.g., N.
  • the indicated PDCP HFN value is configured to be received after a PDCP SN wrapping around while is received before the PDCP SN wrapping around. Then, when the reference PDCP SN value is larger than or equal to a PDCP SN value of the first received data packet, the UE determines that the PDCP SN wrapping around did not happen. Otherwise, i.e., when the reference PDCP SN value is smaller than the PDCP SN value of the first received data packet, the UE determines that the PDCP SN wrapping around has happened. In such scenarios, when the PDCP SN wrapping around has happened, the PDCP HFN initial value will be determined as the indicated PDCP HFN value.
  • the PDCP HFN initial value will be determined as the indicated PDCP HFN value minus one, e.g., N-1.
  • the UE can decrease the initial value of PDCP HFN by 1 or directly set the initial value of PDCP HFN as the value of the indicated PDCP HFN decreased by 1.
  • FIG. 6 is a schematic diagram illustrating a PDCP HFN initial value determination solution according to some embodiments of the present application.
  • the range of PDCP SN value is 0... 1023. That is, PDCP SN wraps around for every 1024 data packets (e.g., PDCP SDUs) .
  • the gNB may also provide a reference PDCP SN value as well as an indicated PDCP HFN value to the UE.
  • the reference PDCP SN value e.g., "512" and the indicated PDCP HFN value, e.g., "100” can be included in a RRC signaling, e.g., the RRCReconfiguration message related to the MRB related configuration.
  • the UE When the UE starts to receive the data packet of the MRB, the UE will read the PDCP SN value of the first received data packet. If the PDCP SN value of the first received data packet, e.g., 700 is larger than or the same as the reference PDCP SN value (e.g., 700>512) , the UE will determine that PDCP SN wrapping around has not happened and set the PDCP HFN initial value as the indicated PDCP HFN value, e.g., 100.
  • the UE will determine that PDCP SN wrapping around has happened and determine the PDCP HFN initial value as the indicated PDCP HFN value plus one, e.g., 101.
  • the information associated with determining PDCP SN wrapping around is a PDCP SN window value, wherein the PDCP SN window value indicates a data packet number before receiving the indicated PDCP HFN value or indicates a data packet number before receiving the first data packet via the MRB. That is, a PDCP SN window value will be configured and transmitted to the UE with the indicated PDCP HFN value by the network apparatus, e.g., the gNB.
  • An exemplary PDCP SN window value may indicate the number of PDCP PDUs before receiving the indicated PDCP HFN value or before receiving the first data packets (PDCP SDUs) via the MRB.
  • the indicated PDCP HFN value e.g., N
  • the indicated PDCP HFN value is configured to be received before a PDCP SN wrapping around while it is received after the PDCP SN wrapping around. Then, when the PDCP SN value of the first received data packets minus the PDCP SN window value is larger than 0, the UE determines that the PDCP SN wrapping around did not happen. Otherwise, i.e., when the PDCP SN value of the first received data packets minus the PDCP SN window value is smaller than or equal to 0, the UE determines that the PDCP SN wrapping around has happened.
  • the PDCP HFN initial value will be determined as the indicated PDCP HFN value plus one, e.g., N+1.
  • the UE can increase the initial value of PDCP HFN by 1 or directly set the initial value of PDCP HFN as the value of the indicated PDCP HFN increased by 1.
  • the PDCP HFN initial value will be determined as the indicated PDCP HFN value, e.g., N.
  • the indicated PDCP HFN value is configured to be received after a PDCP SN wrapping around while it is received before the PDCP SN wrapping around. Then, when the PDCP SN value of the first received data packets minus the PDCP SN window value is larger than 0, the UE determines that the PDCP SN wrapping around did not happen. Otherwise, i.e., when the PDCP SN value of the first received data packets minus the PDCP SN window value is smaller than or equal to 0, the UE determines that the PDCP SN wrapping around has happened. In such scenarios, when the PDCP SN wrapping around has happened, the PDCP HFN initial value will be determined as the indicated PDCP HFN value.
  • the PDCP HFN initial value will be determined as the indicated PDCP HFN value minus one, e.g., N-1.
  • the UE can decrease the initial value of PDCP HFN by 1 or directly set the initial value of PDCP HFN as the value of the indicated PDCP HFN decreased by 1.
  • FIG. 7 is a schematic diagram illustrating a PDCP HFN initial value determination solution according to some other embodiments of the present application.
  • the PDCP SN value range is 0 ... 1023. Accordingly, the PDCP SN wraps around for every 1024 data packets (e.g., PDCP SDUs) .
  • the gNB may also provide a PDCP SN window value as well as an indicated PDCP HFN value to the UE.
  • the PDCP SN window value e.g., "200" and the indicated PDCP HFN value, e.g., "100” can be included in a RRC signaling, e.g., the RRCReconfiguration message related to the MRB related configuration.
  • the UE will determine that PDCP SN wrapping around has not happened and set the PDCP HFN initial value as the indicated PDCP HFN value, e.g. 100.
  • the UE will determine that the PDCP SN wrapping around has happened and determine the PDCP HFN initial value as the indicated PDCP HFN value plus one, e.g., 101.
  • UE may deduce that PDCP HFN desynchronization happened, e.g., based on the information associated with determining PDCP SN wrapping around, e.g., a reference PDCP SN value or a PDCP SN window value. Then, the UE will send a PDCP HFN desynchronization indication to the network apparatus, e.g., the gNB to indicate that PDCP HFN desynchronization happened in the UE. For example, the UE may transmit the PDCP HFN desynchronization indication in a PDCP status report.
  • the network side can know that PDCP HFN desynchronization may happen when it configured the indicated PDCP HFN value. Based on the PDCP HFN desynchronization indication, the network side can also perform necessary retransmission related enhancement and avoid data loss by implementation. In another example, the UE may transmit the PDCP HFN desynchronization indication in a PDCP control PDU.
  • the PTM transmission may be deactivated or activated.
  • the UE will send a PDCP status report to the network side, e.g., to the gNB.
  • the PDCP status report may include the PDCP COUNT value (e.g., PDCP HFN and PDCP SN) of the missing data packets, e.g., PDCP SDUs.
  • the gNB may perform necessary retransmission of the missing PDCP SDUs.
  • the UE If the UE deduces that PDCP HFN synchronization may happen, e.g., based on the reference PDCP SN value or the PDCP SN window value, the UE will also report the PDCP HFN synchronization to the gNB by a PDCP HFN synchronization indication in the PDCP status report.
  • the gNB may ignore the PDCP HFN value in the PDCP status report and perform the retransmission at least of the missing PDCP SDUs according to the reported PDCP SN value of the missing PDCP SDUs and assume that the latest PDCP HFN value is used for the missing PDCP SDUs.
  • FIG. 8 illustrates an exemplary format of a PDCP status report according to some embodiments of the present application.
  • the size of the exemplary format of the PDCP status report may be 5 bytes with M optional bytes, wherein M is an integer larger than or equal to 1.
  • M is an integer larger than or equal to 1.
  • the header of the PDCP status report may include:
  • the D/C field may be set to "1" to indicate that the PDU is a data PDU;
  • PDU Type field with 3 bits indicating the type of the PDU
  • the PDCP HFN field may be configured to be set as "1" to indicate that PDCP HFN desynchronization happened and to be set as "0" to indicate that PDCP HFN desynchronization did not happen;
  • field “FMC” means the first missing count and indicates the COUNT value of the first missing PDCP SDU.
  • the internal structure of a BS is split into two parts, i.e., CU (e.g., gNB-CU) and at least one DU (e.g., gNB-DU) .
  • the CU can be separated into a CU-CP unit (e.g., gNB-CU-CP) and at least one CU-UP unit (e.g., gNB-CU-UP) . Since the CU-UP unit is responsible for user data transmission and the CU-CP unit has no idea of the PDCP SN and PDCP HFN, the CU-CP unit is unable to configure the information associated with determining PDCP SN wrapping around and indicated PDCP HFN value to the UE. Accordingly, the coordination between the CU-CP unit and CU-UP unit is needed for setting the information associated with determining PDCP SN wrapping around and the indicated PDCP HFN value.
  • the CU-CP unit of the CU of the BS may transmit to the CU-UP unit of the CU a requiring indication for information associated with determining PDCP SN wrapping around and an indicated PDCP HFN value required indication.
  • the requiring indication for information associated with determining PDCP SN wrapping around may be a reference PDCP SN value required indication or a PDCP SN window required indication etc.
  • the CU-UP unit will transmit to the CU-CP unit the information associated with determining PDCP SN wrapping around in response to the requiring indication for information associated with determining PDCP SN wrapping around and the indicated PDCP HFN value in response to the indicated PDCP HFN value required indication.
  • the CU-UP unit will transmit to the CU-CP unit a reference PDCP SN value in response to the reference PDCP SN value required indication or a PDCP SN window value in response to the PDCP SN window value required indication.
  • the CU-CP unit will transmit the received information associated with determining PDCP SN wrapping around and the indicated PDCP HFN value to the DU, and the DU will transfer the received information associated with determining PDCP SN wrapping around and the indicated PDCP HFN value to the UE.
  • the CU-CP unit may transmit to the CU-UP unit only an indicated PDCP HFN value required indication, and the CU-UP unit will transmit to the CU-CP unit only the indicated PDCP HFN value in response to the indicated PDCP HFN value required indication.
  • the CU-CP unit will transmit the received indicated PDCP HFN value to the DU, and the DU will transfer the received indicated PDCP HFN value to the UE.
  • the information associated with determining PDCP SN wrapping around may not be needed, because the network ensures that the PDCP SN wrapping around will not happen when UE receives the indicated PDCP HFN or receives the first packets from the network.
  • FIG. 9 is a flow chart illustrating an exemplary procedure of a method for MBS considering the internal structure of a BS according to some embodiments of the present application.
  • the CU-CP unit (CU-CP) of the CU of a BS may send a message, e.g., BEARER CONTEXT MODIFICATION REQUEST to the CU-UP unit (CU-UP) of the CU in step 901, e.g., with an MRB to be setup list.
  • the CU-CP unit may include a requiring indication for information associated with determining PDCP SN wrapping around and an indicated PDCP HFN value required indication for each MRB in the message, which means that the initial PDCP count value should be configured to the UE for each MRB.
  • the requiring indication for information associated with determining PDCP SN wrapping around may be a reference PDCP SN value required indication or a PDCP SN window value required information.
  • the CU-UP unit may send a message, e.g., BEARER CONTEXT MODIFICATION RESPONSE in response to the message from the CU-CP unit, wherein an MRB setup list may be included.
  • the CU-UP unit may also provide the reference PDCP SN value or PDCP SN window value in response to the reference PDCP SN value required indication or PDCP SN window value required indication, together with an indicated PDCP HFN value for each MRB.
  • the CU-UP unit may provide the reference PDCP SN value or PDCP SN window value together with the indicated PDCP HFN value in a PDCP control PDU for each MRB in response to the message from the CU-CP unit.
  • the CU-UP unit sends the PDCP control PDU to the UE via the DU.
  • the CU-CP unit may also provide the MBS information to the DU in step 905, e.g., in UE CONTEXT MODIFICATION REQUEST, to setup the MRB for the UE.
  • the DU will provide the G-RNTI assigned to the MBS session indicated by the MBS information to the CU-CP unit in step 907, e.g., in UE CONTEXT MODIFICATION RESPONSE.
  • the CU may send a RRC message to the UE to configure the MRB, which will be transferred to the UE by the DU.
  • the RRC message includes the MRB configuration and the reference PDCP SN value (or PDCP SN window value) and the indicated PDCP HFN value, etc.
  • the UE will set the PDCP HFN initial value in step 911 as illustrated above, which will not be repeated.
  • FIG. 10 illustrates a block diagram of an apparatus 1000 for MBS according to some embodiments of the present application.
  • the apparatus 1000 may include at least one non-transitory computer-readable medium 1001, at least one receiving circuitry 1002, at least one transmitting circuitry 1004, and at least one processor 1006 coupled to the non-transitory computer-readable medium 1001, the receiving circuitry 1002 and the transmitting circuitry 1004.
  • the apparatus 1000 may be a terminal device (e.g., a UE) configured to perform a method illustrated in the above or the like.
  • the at least one processor 1006, transmitting circuitry 1004, and receiving circuitry 1002 are described in the singular, the plural is contemplated unless a limitation to the singular is explicitly stated.
  • the receiving circuitry 1002 and the transmitting circuitry 1004 can be combined into a single device, such as a transceiver.
  • the apparatus 1000 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 1001 may have stored thereon computer-executable instructions to cause a processor to implement the method with respect to the terminal device as described above.
  • the computer-executable instructions when executed, cause the processor 1006 interacting with receiving circuitry 1002 and transmitting circuitry 1004, so as to perform the steps with respect to the apparatus in the remote side, e.g., UE as depicted above.
  • an apparatus in the remote side includes: at least one non-transitory computer-readable medium having computer-executable instructions stored thereon; at least one receiving circuitry; at least one transmitting circuitry; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiving circuitry and the at least one transmitting circuitry, wherein by the cooperation of the at least one non-transitory computer-readable medium, at least one receiving circuitry, at least one transmitting circuitry, and at least one processor, the apparatus is configured to: receive, from a network apparatus, information associated with determining PDCP SN wrapping around and an indicated PDCP HFN value for an MRB, wherein the information associated with determining PDCP SN wrapping around is for determining whether PDCP SN wrapping around has happened by the UE; and determine a PDCP HFN initial value for a receiving data packet of the MRB from the network apparatus based on the information associated with determining PDCP SN wrapping around and the indicated
  • the non-transitory computer-readable medium 1001 may have stored thereon computer-executable instructions to cause a processor to implement the method with respect to the CU or DU as described above.
  • the computer-executable instructions when executed, cause the processor 1006 interacting with receiving circuitry 1002 and transmitting circuitry 1004, so as to perform the steps with respect to the apparatus in the network side, e.g., a BS illustrated above.
  • an apparatus in the network side includes: at least one non-transitory computer-readable medium having computer-executable instructions stored thereon; at least one receiving circuitry; at least one transmitting circuitry; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiving circuitry and the at least one transmitting circuitry, wherein by the cooperation of the at least one non-transitory computer-readable medium, at least one receiving circuitry, at least one transmitting circuitry, and at least one processor, the apparatus is configured to: transmit, to a UE, information associated with PDCP SN wrapping around and an indicated PDCP HFN value for an MRB, and transmit data packets via the MRB to the UE. Wherein the information associated with determining PDCP SN wrapping around is for determining whether PDCP SN wrapping around has happened by the UE to further determine a PDCP HFN initial value for the MRB based on the indicated PDCP HFN value.
  • FIG. 11 is a block diagram of an apparatus for MBS according to some other embodiments of the present application.
  • the apparatus 1100 for example a UE or a BS may include at least one processor 1102 and at least one transceiver 1104.
  • the transceiver 1104 may include at least one separate receiving circuitry 1106 and transmitting circuitry 1108, or at least one integrated receiving circuitry 1106 and transmitting circuitry 1108.
  • the processor when the apparatus 1100 is a UE, is configured to: receive, from a network apparatus, information associated with determining PDCP SN wrapping around and an indicated PDCP HFN value for an MRB, wherein the information associated with determining PDCP SN wrapping around is for determining whether PDCP SN wrapping around has happened by the UE; and determine a PDCP HFN initial value for a receiving data packet of the MRB from the network apparatus based on the information associated with determining PDCP SN wrapping around and the indicated PDCP HFN value.
  • the processor may be configured to: transmit, to a UE, information associated with PDCP SN wrapping around and an indicated PDCP HFN value for an MRB, and transmit data packets via the MRB to the UE.
  • the information associated with determining PDCP SN wrapping around is for determining whether PDCP SN wrapping around has happened by the UE to further determine a PDCP HFN initial value for the MRB based on the indicated PDCP HFN value.
  • the method according to embodiments of the present application can also be implemented on a programmed processor.
  • the controllers, flowcharts, and modules may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like.
  • any device on which resides a finite state machine capable of implementing the flowcharts shown in the figures may be used to implement the processor functions of this application.
  • an embodiment of the present application provides an apparatus for MBS, including a processor and a memory.
  • Computer programmable instructions for implementing a method are stored in the memory, and the processor is configured to perform the computer programmable instructions to implement the method.
  • the method may be a method as stated above or other method according to an embodiment of the present application.
  • An alternative embodiment preferably implements the methods according to embodiments of the present application in a non-transitory, computer-readable storage medium storing computer programmable instructions.
  • the instructions are preferably executed by computer-executable components preferably integrated with a network security system.
  • the non-transitory, computer-readable storage medium may be stored on any suitable computer readable media such as RAMs, ROMs, flash memory, EEPROMs, optical storage devices (CD or DVD) , hard drives, floppy drives, or any suitable device.
  • the computer-executable component is preferably a processor but the instructions may alternatively or additionally be executed by any suitable dedicated hardware device.
  • an embodiment of the present application provides a non-transitory, computer-readable storage medium having computer programmable instructions stored therein.
  • the computer programmable instructions are configured to implement a method as stated above or other method according to an embodiment of the present application.
  • the terms “includes, “ “including, “ or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
  • An element proceeded by “a, “ “an, “ or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element.
  • the term “another” is defined as at least a second or more.
  • the terms “having, “ and the like, as used herein, are defined as “including. "

Landscapes

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

Abstract

Les modes de réalisation de la présente demande concernent des procédés et des appareils pour des services de multidiffusion et de diffusion (MBS). Un procédé donné à titre d'exemple pour des services de multidiffusion et de diffusion peut consister à : recevoir des informations PDCP associées à un MRB en provenance d'un appareil de réseau ; déterminer s'il existe un débordement de PDCP SN sur la base des informations PDCP reçues en provenance de l'appareil de réseau ; et, en réponse à la détermination de l'existence, ou non, du débordement de PDCP SN, déterminer des informations PDCP HFN associées au PDCP SN.
PCT/CN2021/123129 2021-10-11 2021-10-11 Procédé et appareil pour des services de multidiffusion et de diffusion WO2023060402A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/123129 WO2023060402A1 (fr) 2021-10-11 2021-10-11 Procédé et appareil pour des services de multidiffusion et de diffusion

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/123129 WO2023060402A1 (fr) 2021-10-11 2021-10-11 Procédé et appareil pour des services de multidiffusion et de diffusion

Publications (1)

Publication Number Publication Date
WO2023060402A1 true WO2023060402A1 (fr) 2023-04-20

Family

ID=85987122

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/123129 WO2023060402A1 (fr) 2021-10-11 2021-10-11 Procédé et appareil pour des services de multidiffusion et de diffusion

Country Status (1)

Country Link
WO (1) WO2023060402A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1444811A (zh) * 2000-08-01 2003-09-24 诺基亚有限公司 数据传输方法、用户设备和gprs/edge无线接入网
US20150280905A1 (en) * 2014-04-01 2015-10-01 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for detecting and correcting pdcp hyper frame number (hfn) desynchronization
US20190245800A1 (en) * 2016-11-04 2019-08-08 Samsung Electronics Co., Ltd. Method and device for processing packet by terminal in wireless communication system
US20210168597A1 (en) * 2017-06-26 2021-06-03 Samsung Electronics Co., Ltd. Device and method for detecting mismatch of encryption parameter in wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1444811A (zh) * 2000-08-01 2003-09-24 诺基亚有限公司 数据传输方法、用户设备和gprs/edge无线接入网
US20150280905A1 (en) * 2014-04-01 2015-10-01 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for detecting and correcting pdcp hyper frame number (hfn) desynchronization
US20190245800A1 (en) * 2016-11-04 2019-08-08 Samsung Electronics Co., Ltd. Method and device for processing packet by terminal in wireless communication system
US20210168597A1 (en) * 2017-06-26 2021-06-03 Samsung Electronics Co., Ltd. Device and method for detecting mismatch of encryption parameter in wireless communication system

Similar Documents

Publication Publication Date Title
EP3611995B1 (fr) Procédé de communication, dispositif de communication et système de communication s'y rapportant
US10736065B2 (en) Method and apparatus for time synchronization in device-to-device communication
US10485042B2 (en) Method for reconfiguring wireless bearer and device thereof
JP2013102491A (ja) 無線通信システムにおいて差分符号化を備えたデフォルトコンフィギュレーション
US11665775B2 (en) Communications device, infrastructure equipment, communications system and methods
US20220014901A1 (en) Method and apparatus for identifying user equipment capability in sidelink transmission
WO2022027443A1 (fr) Procédé et appareil pour services de diffusion et de multidiffusion
US20240031870A1 (en) Media data transmission method and communication apparatus
US20230180340A1 (en) Method and apparatus for small data transmission
US20230362721A1 (en) Method and apparatus for multicast and broadcast services
WO2023060402A1 (fr) Procédé et appareil pour des services de multidiffusion et de diffusion
US20240236619A1 (en) Method and apparatus for multicast and broadcast services
WO2024031228A1 (fr) Procédé et appareil de prise en charge de services de diffusion et de multidiffusion
WO2022151177A1 (fr) Procédés et appareils de services de diffusion non sélective et de diffusion sélective
WO2024020728A1 (fr) Procédés et appareils de transmission simultanée sur de multiples trajets
CN112703815B (zh) 一种数据包重排序方法、电子设备及存储介质
WO2023245649A1 (fr) Procédé et appareil de prise en charge d'une gestion de budget de retard
CN115150910B (zh) 通信方法及通信装置
WO2023216258A1 (fr) Procédés et appareils pour une opération de gestion de réception de sdu pdcp
WO2022151254A1 (fr) Procédé et appareil de transmission de données
WO2023283828A1 (fr) Procédés et appareils de transfert
WO2024065257A1 (fr) Procédés et appareils d'amélioration de lcp avec des informations de cot partagées
WO2023245566A1 (fr) Procédés et appareil pour prendre en charge une rétroaction harq par accès aléatoire pour une réception de multidiffusion en rrc inactive
US20230328543A1 (en) Method and apparatus for multicast and broadcast services
WO2022027582A1 (fr) Procédé et appareil pour des services de multidiffusion et de diffusion

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: 21960153

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE