WO2022138450A1 - 通信制御方法及びユーザ装置 - Google Patents

通信制御方法及びユーザ装置 Download PDF

Info

Publication number
WO2022138450A1
WO2022138450A1 PCT/JP2021/046549 JP2021046549W WO2022138450A1 WO 2022138450 A1 WO2022138450 A1 WO 2022138450A1 JP 2021046549 W JP2021046549 W JP 2021046549W WO 2022138450 A1 WO2022138450 A1 WO 2022138450A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission
mbs
ptp
ptm
status report
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/JP2021/046549
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
真人 藤代
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kyocera Corp
Original Assignee
Kyocera Corp
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 Kyocera Corp filed Critical Kyocera Corp
Priority to JP2022571378A priority Critical patent/JP7549043B2/ja
Publication of WO2022138450A1 publication Critical patent/WO2022138450A1/ja
Priority to US18/339,896 priority patent/US20230337327A1/en
Anticipated expiration legal-status Critical
Priority to JP2024147391A priority patent/JP7723164B2/ja
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present disclosure relates to a communication control method and a user device used in a mobile communication system.
  • NR New Radio
  • RAT Radio Access Technology
  • LTE Long Term Evolution
  • the communication control method is a communication control method executed by a user device in a mobile communication system that provides a multicast / broadcast service (MBS), and is a communication control method for PTP (Point-To-Point) transmission and PTM (Point). -Depending on the receipt of MBS data transmitted from the base station by any transmission method of To-Multipoint) transmission and the switching of the transmission method between the PTP transmission and the PTM transmission. It includes triggering the transmission of a status report indicating the reception status of MBS data in a predetermined layer of the user apparatus, and transmitting the status report to the base station.
  • MBS multicast / broadcast service
  • the user device is a user device used in a mobile communication system that provides a multicast / broadcast service (MBS), and is used for PTP (Point-To-Point) transmission and PTM (Point-To-Multipoint) transmission.
  • a receiver that receives MBS data transmitted from a base station by any of the transmission methods of the above, and a predetermined user device according to the fact that the transmission method is switched between the PTP transmission and the PTM transmission. It includes a control unit that triggers transmission of a status report indicating the reception status of MBS data in the layer, and a transmission unit that transmits the status report to the base station.
  • logical channel logical channel
  • Transport channel Transport channel
  • NR 5G system
  • the purpose of this disclosure is to realize an improved multicast / broadcast service.
  • FIG. 1 is a diagram showing a configuration of a mobile communication system according to an embodiment.
  • This mobile communication system complies with the 5th generation system (5GS: 5th Generation System) of the 3GPP standard.
  • 5GS 5th Generation System
  • 5GS will be described as an example, but the LTE (Long Term Evolution) system may be applied at least partially to the mobile communication system, and the 6th generation (6G) system may be applied at least partially. May be done.
  • mobile communication systems include a user device (UE: User Equipment) 100, a 5G radio access network (NG-RAN: Next Generation Radio Access Network) 10, and a 5G core network (5GC: 5G). It has Core Network) 20.
  • UE User Equipment
  • NG-RAN Next Generation Radio Access Network
  • 5GC 5G core network
  • the UE 100 is a mobile wireless communication device.
  • the UE 100 may be any device as long as it is a device used by the user.
  • the UE 100 may be a mobile phone terminal (including a smartphone), a tablet terminal, a notebook PC, or a communication module (communication card or communication card).
  • a device including a chipset), a sensor or a device provided on the sensor, a vehicle or a device provided on the vehicle (Vehicle UE), a flying object or a device provided on the flying object (Arial UE).
  • the NG-RAN 10 includes a base station (referred to as "gNB” in a 5G system) 200.
  • the gNB 200 are connected to each other via the Xn interface, which is an interface between base stations.
  • the gNB 200 manages one or more cells.
  • the gNB 200 performs wireless communication with the UE 100 that has established a connection with its own cell.
  • the gNB 200 has a radio resource management (RRM) function, a routing function for user data (hereinafter, simply referred to as “data”), a measurement control function for mobility control / scheduling, and the like.
  • RRM radio resource management
  • Cell is used as a term to indicate the smallest unit of a wireless communication area.
  • the term “cell” is also used to indicate a function or resource for wireless communication with the UE 100.
  • One cell belongs to one carrier frequency.
  • gNB can also connect to EPC (Evolved Packet Core), which is the core network of LTE.
  • EPC Evolved Packet Core
  • LTE base stations can also be connected to 5GC.
  • the LTE base station and gNB can also be connected via an inter-base station interface.
  • 5GC20 includes AMF (Access and Mobility Management Function) and UPF (User Plane Function) 300.
  • the AMF performs various mobility controls and the like for the UE 100.
  • the AMF manages the mobility of the UE 100 by communicating with the UE 100 using NAS (Non-Access Stratum) signaling.
  • UPF controls data transfer.
  • the AMF and UPF are connected to the gNB 200 via the NG interface, which is an interface between the base station and the core network.
  • FIG. 2 is a diagram showing a configuration of a UE 100 (user device) according to an embodiment.
  • the UE 100 includes a receiving unit 110, a transmitting unit 120, and a control unit 130.
  • the receiving unit 110 performs various receptions under the control of the control unit 130.
  • the receiving unit 110 includes an antenna and a receiver.
  • the receiver converts the radio signal received by the antenna into a baseband signal (received signal) and outputs it to the control unit 130.
  • the transmission unit 120 performs various transmissions under the control of the control unit 130.
  • the transmitter 120 includes an antenna and a transmitter.
  • the transmitter converts the baseband signal (transmission signal) output by the control unit 130 into a radio signal and transmits it from the antenna.
  • the control unit 130 performs various controls on the UE 100.
  • the control unit 130 includes at least one processor and at least one memory.
  • the memory stores a program executed by the processor and information used for processing by the processor.
  • the processor may include a baseband processor and a CPU (Central Processing Unit).
  • the baseband processor modulates / demodulates and encodes / decodes the baseband signal.
  • the CPU executes a program stored in the memory to perform various processes.
  • FIG. 3 is a diagram showing the configuration of gNB200 (base station) according to one embodiment.
  • the gNB 200 includes a transmission unit 210, a reception unit 220, a control unit 230, and a backhaul communication unit 240.
  • the transmission unit 210 performs various transmissions under the control of the control unit 230.
  • the transmitter 210 includes an antenna and a transmitter.
  • the transmitter converts the baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits it from the antenna.
  • the receiving unit 220 performs various receptions under the control of the control unit 230.
  • the receiving unit 220 includes an antenna and a receiver.
  • the receiver converts the radio signal received by the antenna into a baseband signal (received signal) and outputs it to the control unit 230.
  • the control unit 230 performs various controls on the gNB 200.
  • the control unit 230 includes at least one processor and at least one memory.
  • the memory stores a program executed by the processor and information used for processing by the processor.
  • the processor may include a baseband processor and a CPU.
  • the baseband processor modulates / demodulates and encodes / decodes the baseband signal.
  • the CPU executes a program stored in the memory to perform various processes.
  • the backhaul communication unit 240 is connected to an adjacent base station via an interface between base stations.
  • the backhaul communication unit 240 is connected to the AMF / UPF 300 via the base station-core network interface.
  • the gNB is composed of a CU (Central Unit) and a DU (Distributed Unit) (that is, the functions are divided), and both units may be connected by an F1 interface.
  • FIG. 4 is a diagram showing a configuration of a protocol stack of a wireless interface of a user plane that handles data.
  • the wireless interface protocol of the user plane includes a physical (PHY) layer, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, and a PDCP (Packet Data Convergence Protocol) layer. It has an SDAP (Service Data Adjustment Protocol) layer.
  • PHY physical
  • MAC Medium Access Control
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • SDAP Service Data Adjustment Protocol
  • the PHY layer performs coding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the PHY layer of the UE 100 and the PHY layer of the gNB 200 via a physical channel.
  • the MAC layer performs data priority control, retransmission processing by hybrid ARQ (HARQ), random access procedure, and the like. Data and control information are transmitted between the MAC layer of the UE 100 and the MAC layer of the gNB 200 via the transport channel.
  • the MAC layer of gNB200 includes a scheduler. The scheduler determines the transport format (transport block size, modulation / coding method (MCS)) of the upper and lower links and the resource block allocated to the UE 100.
  • MCS modulation / coding method
  • the RLC layer transmits data to the receiving RLC layer by using the functions of the MAC layer and the PHY layer. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the gNB 200 via a logical channel.
  • the PDCP layer performs header compression / decompression and encryption / decryption.
  • the SDAP layer maps an IP flow, which is a unit in which a core network performs QoS control, with a wireless bearer, which is a unit in which an AS (Access Stratum) controls QoS.
  • IP flow which is a unit in which a core network performs QoS control
  • wireless bearer which is a unit in which an AS (Access Stratum) controls QoS.
  • AS Access Stratum
  • FIG. 5 is a diagram showing a configuration of a protocol stack of a wireless interface of a control plane that handles signaling (control signal).
  • the protocol stack of the radio interface of the control plane has an RRC (Radio Resource Control) layer and a NAS (Non-Access Stratum) layer in place of the SDAP layer shown in FIG.
  • RRC signaling for various settings is transmitted between the RRC layer of UE100 and the RRC layer of gNB200.
  • the RRC layer controls logical channels, transport channels, and physical channels in response to the establishment, re-establishment, and release of radio bearers.
  • RRC connection connection between the RRC of the UE 100 and the RRC of the gNB 200
  • the UE 100 is in the RRC connected state.
  • RRC connection no connection between the RRC of the UE 100 and the RRC of the gNB 200
  • the UE 100 is in the RRC idle state.
  • the connection between the RRC of the UE 100 and the RRC of the gNB 200 is suspended, the UE 100 is in the RRC inactive state.
  • the NAS layer located above the RRC layer performs session management, mobility management, etc.
  • NAS signaling is transmitted between the NAS layer of the UE 100 and the NAS layer of the AMF300B.
  • the UE 100 has an application layer and the like in addition to the wireless interface protocol.
  • MBS is a service that enables broadcast or multicast, that is, one-to-many (PTM: Point To Multipoint) data transmission from NG-RAN10 to UE100.
  • PTM Point To Multipoint
  • MBS may be referred to as MBMS (Multicast Broadcast and Multicast Service).
  • the MBS use cases (service types) include public safety communication, mission-critical communication, V2X (Vehicle to Everything) communication, IPv4 or IPv6 multicast distribution, IPTV, group communication, software distribution, and the like.
  • FIG. 6 is a diagram showing a correspondence relationship between a downlink logical channel (Logical channel) and a transport channel (Transport channel) according to an embodiment.
  • MBSFN Multipoint Broadcast Single Frequency Network
  • SC-PTM Single Cell Point To Multipoint
  • the logical channels used for MBSFN transmission are MTCH (Multicast Traffic Channel) and MCCH (Multicast Control Channel), and the transport channel used for MBSFN transmission is MCH (Multicast Control Channel).
  • MBSFN transmission is mainly designed for multi-cell transmission, and each cell performs synchronous transmission of the same signal (same data) in the same MBSFN subframe in an MBSFN area composed of a plurality of cells.
  • the logical channels used for SC-PTM transmission are SC-MTCH (Single Cell Multicast Traffic Channel) and SC-MCCH (Single Cell Multicast Control Channel).
  • the transport channel used for SC-PTM transmission is DL-SCH (Downlink Shared Channel).
  • SC-PTM transmission is designed primarily for single-cell transmission and performs broadcast or multicast data transmission on a cell-by-cell basis.
  • the physical channels used for SC-PTM transmission are PDCCH (Physical Downlink Control Channel) and PDSCH (Physical Downlink Control Channel), and dynamic resource allocation is possible.
  • MBS may be provided using a method similar to the SC-PTM transmission method.
  • MBS may be provided using the MBSFN transmission method.
  • MBS may be read as multicast.
  • MBS may be provided by broadcast.
  • MBS data means data provided by MBS
  • MBS control channel means MCCH or SC-MCCH
  • MBS traffic channel means MTCH or SC-MTCH.
  • MBS data may be transmitted by unicast.
  • MBS data may be referred to as MBS packets or MBS traffic.
  • the network can provide different MBS services for each MBS session.
  • the MBS session is identified by at least one of TMGI (Temporary Mobile Group Identity) and a session identifier, and at least one of these identifiers is called an MBS session identifier.
  • TMGI Temporal Mobile Group Identity
  • Such an MBS session identifier may be referred to as an MBS service identifier or a multicast group identifier.
  • FIG. 7 is a diagram showing a method of distributing MBS data according to an embodiment.
  • MBS data (MBS Traffic) is distributed from a single data source (application service provider) to a plurality of UEs.
  • the 5G CN (5GC) 20 which is a 5G core network, receives MBS data from an application service provider, creates a copy of the MBS data (Replication), and distributes it.
  • NG-RAN10 5G radio access networks
  • 5G RAN 5G radio access networks
  • MBS connection such a connection (tunnel) will be referred to as an “MBS connection”.
  • the MBS connection may be referred to as a Shared MBS Traffic delivery connection or a shared transport.
  • the MBS connection is terminated at NG-RAN10 (ie, gNB200).
  • the MBS connection may have a one-to-one correspondence with the MBS session.
  • the gNB 200 selects either PTP (Point-to-Point: Unicast) or PTM (Point-to-Multipoint: Multicast or Broadcast) transmission method at its own discretion, and MBS data is sent to the UE 100 by the selected transmission method. To send.
  • PTP Point-to-Point: Unicast
  • PTM Point-to-Multipoint: Multicast or Broadcast
  • a unicast session is established between NG-RAN10 and UE100, and MBS data is individually distributed from 5GC20 to UE100.
  • MBS data is individually distributed from 5GC20 to UE100.
  • Such a unicast may be called a PDU session.
  • Unicast (PDU session) ends at UE100.
  • split MBS bearer Next, the split MBS bearer according to the embodiment will be described.
  • the gNB 200 may set the MBS bearer (hereinafter, appropriately referred to as “split MBS bearer”) separated into the PTP communication path and the PTM communication path in the UE 100.
  • the gNB 200 can dynamically switch the transmission of MBS data to the UE 100 between PTP (PTP communication path) and PTM (PTM communication path).
  • the gNB 200 can improve reliability by double-transmitting the same MBS data by using PTP (PTP communication path) and PTM (PTM communication path) in combination.
  • the predetermined layer that terminates the split is a MAC layer (HARQ), an RLC layer, a PDCP layer, or a SDAP layer.
  • HARQ MAC layer
  • RLC Radio Link Control
  • PDCP Packet Control Protocol
  • SDAP Secure Sockets Layer
  • FIG. 8 is a diagram showing a split MBS bearer according to an embodiment.
  • the PTP communication path will be referred to as a PTP leg
  • the PTM communication path will be referred to as a PTM leg
  • the functional part corresponding to each layer is called an entity.
  • each of the PDCP entity of gNB200 and the PDCP entity of UE100 separates the MBS bearer, which is a bearer (data radio bearer) used for MBS, into a PTP leg and a PTM leg.
  • the PDCP entity is provided for each bearer.
  • Each of gNB200 and UE100 has two RLC entities provided for each leg, one MAC entity, and one PHY entity.
  • the PHY entity may be provided for each leg.
  • the UE 100 may have two MAC entities.
  • the PHY entity sends and receives PTP leg data using a cell RNTI (C-RNTI: Cell Radio Network Entity Identifier) that is assigned one-to-one with the UE 100.
  • C-RNTI Cell Radio Network Entity Identifier
  • the PHY entity sends and receives PTM leg data using the group RNTI (G-RNTI: Group Radio Network Entity Identifier) that is assigned one-to-one with the MBS session.
  • G-RNTI Group Radio Network Entity Identifier
  • a split MBS bearer is set from gNB200 to UE100, and the PTM leg is activated. Must have been. In other words, even if the split MBS bearer is set in the UE 100, the gNB 200 cannot perform PTM transmission of MBS data using this PTM leg when the PTM leg is in the deactivation state.
  • the split MBS bearer is set from the gNB 200 to the UE 100 and the PTP leg is activated. There is. In other words, even if the split MBS bearer is set in the UE 100, the gNB 200 cannot perform PTP transmission of MBS data using this PTP leg when the PTP leg is in the inactive state.
  • the UE 100 monitors the PDCCH (Physical Downlink Control Channel) to which the G-RNTI associated with the MBS session is applied while the PTM leg is activated (that is, the blind display of the PDCCH using the G-RNTI). Do the coding).
  • the UE 100 may monitor the PDCCH only at the scheduling opportunity of the MBS session.
  • the UE 100 does not monitor the PDCCH to which the G-RNTI associated with the MBS session is applied (ie, does not blind decode the PDCCH using the G-RNTI) when the PTM leg is deactivated. ..
  • the UE 100 monitors the PDCCH to which the C-RNTI is applied while the PTP leg is activated.
  • the UE 100 monitors the PDCCH in the set on period (OnDuration) when the intermittent reception (DRX: Discontinuus Reception) in the PTP leg is set.
  • OnDuration the on period
  • DRX Discontinuus Reception
  • the UE 100 may monitor the PDCCH of the cell even if the cell is deactivated.
  • the UE 100 may monitor the PDCCH to which C-RNTI is applied in preparation for normal unicast downlink transmission other than MBS data in a state where the PTP leg is deactivated. However, the UE 100 does not have to monitor the PDCCH for the MBS session when the cell (frequency) associated with the MBS session is specified.
  • the split MBS bearer as described above is set by the RRC message (for example, RRC Configuration message) transmitted by the RRC entity of gNB200 to the RRC entity of UE100.
  • RRC message for example, RRC Configuration message
  • FIG. 9 is a diagram showing an operation example 1 relating to activation and deactivation of the leg according to the embodiment.
  • the RRC entity of gNB200 sends an RRC message including the setting of the split MBS bearer (split bearer) shown in FIG. 8 to the UE 100.
  • the RRC message is, for example, an RRC Reconnection message.
  • the RRC entity of the UE 100 establishes a split MBS bearer based on the settings contained in the RRC message received from the gNB 200.
  • the UE 100 may establish a plurality of split MBS bearers according to the setting from the gNB 200.
  • the gNB 200 may instruct the UE 100 in the initial state of each leg (that is, activation or deactivation of each leg) by the same message.
  • the RRC entity of gNB200 sends an RRC message containing the bearer setting of the split MBS bearer to the UE 100, the RRC message includes the activation or deactivation instruction of each leg together with the bearer setting.
  • Such an RRC message may include at least one of an identifier of the leg (PTP leg, PTM leg) to be instructed and an identifier indicating either activation or deactivation.
  • the RRC message may include an identifier (eg, TMGI, G-RNTI, session identifier, QoS flow identifier, bearer identifier) associated with the MBS session (split MBS bearer) to be instructed.
  • step S12 the gNB 200 sends an instruction to individually activate or deactivate the PTP leg and the PTM leg to the UE 100.
  • the MAC entity of gNB200 may transmit a MAC control element (MAC CE) including the instruction to the UE 100.
  • the MAC entity of UE100 receives MAC CE from gNB200.
  • the PHY entity of the gNB 200 may transmit downlink control information (DCI) including the instruction to the UE 100.
  • the PHY entity of UE100 receives DCI from gNB200.
  • DCI downlink control information
  • Such a MAC CE or DCI may include at least one of an identifier of the leg (PTP leg, PTM leg) to be instructed and an identifier indicating either activation or deactivation.
  • the MAC CE or DCI may include an identifier (for example, TMGI, G-RNTI, session identifier, QoS flow identifier, bearer identifier) associated with the MBS session (split MBS bearer) to be instructed.
  • the UE 100 starts the data reception process using C-RNTI in response to the reception of the instruction to activate the PTP leg.
  • the UE 100 starts the MBS data reception processing using the G-RNTI in response to the reception of the instruction to activate the PTM leg.
  • the UE 100 ends the data reception process using the C-RNTI in response to the reception of the instruction to deactivate the PTP leg.
  • the UE 100 ends the MBS data reception processing using the G-RNTI in response to the reception of the instruction to deactivate the PTM leg.
  • the gNB 200 may transmit (PTM transmission) an instruction to activate or deactivate the PTP leg to the UE 100 via the PTM leg in the activated state.
  • PTM transmission an instruction to activate or deactivate the PTP leg to the UE 100 via the PTM leg in the activated state.
  • the gNB 200 may transmit (PTM transmission) an instruction to deactivate the PTM leg to the UE 100 via the PTM leg in the activated state.
  • PTM transmission an instruction to deactivate the PTM leg to the UE 100 via the PTM leg in the activated state.
  • the gNB 200 may transmit (PTP transmission) an instruction to activate or deactivate the PTM leg to the UE 100 via the PTP leg in the activated state. This allows the PTM leg to be individually activated or deactivated for each UE 100.
  • the gNB 200 may transmit (PTP transmission) an instruction to deactivate the PTP leg to the UE 100 via the PTP leg in the activated state. This allows the PTP leg to be individually deactivated for each UE 100.
  • the UE 100 may transmit a response to the received instruction to the gNB 200 in response to receiving an instruction from the gNB 200 to activate at least one leg of the PTP leg and the PTM leg in step S12.
  • This response may be transmitted from the MAC entity of the UE 100 to the gNB 200 via the PTP leg, for example.
  • the UE 100 may initiate a data receiving operation on the activated leg after transmitting the response.
  • the gNB 200 transmits data via the activated leg in response to receiving a response from the UE 100. That is, after receiving the response, the gNB 200 starts the data transmission operation in the leg.
  • the UE 100 may transmit a response to the received instruction to the gNB 200 in response to receiving an instruction from the gNB 200 to deactivate at least one leg of the PTP leg and the PTM leg in step S12.
  • FIG. 10 is a diagram showing an operation example 2 relating to activation and deactivation of a leg according to an embodiment. Since the basic operation of the operation example 2 is the same as that of the operation example 1, the differences from the operation example 1 will be mainly described here. The operation example 2 can be used in combination with the operation example 1.
  • the gNB 200 transmits an instruction for activating or deactivating both the PTP leg and the PTM leg to the UE 100.
  • the MAC entity of gNB200 includes both the control instruction of the PTP leg and the control instruction of the PTM leg in the MAC CE instructing the activation or deactivation of the leg.
  • the RRC entity of gNB200 sends an RRC message including the setting of the split MBS bearer (split bearer) shown in FIG. 8 to the UE 100.
  • the RRC message may include information that sets the initial state of each leg.
  • the information for setting the initial state of each leg may be the same information as the instruction included in the MAC CE or DCI described later.
  • step S22 the gNB 200 sends an instruction to the UE 100 to activate or deactivate both the PTP leg and the PTM leg.
  • the instructions are included in MAC CE or DCI.
  • the MAC CE or DCI indicates an indication value for activating both the PTP leg and the PTM leg (for example, “1”) or deactivating both the PTP leg and the PTM leg (for example, “0”).
  • the activation of both the PTP leg and the PTM leg may be the activation of the split MBS bearer or the activation of duplication using the two legs.
  • the deactivation of both the PTP leg and the PTM leg may be the deactivation of the split MBS bearer or the deactivation of double transmission using the two legs.
  • the MAC CE or DCI may include an identifier (for example, TMGI, G-RNTI, session identifier, QoS flow identifier, bearer identifier) associated with the MBS session (split MBS bearer) to be instructed.
  • MAC CE or DCI may include activation or deactivation instructions for each such identifier.
  • FIG. 11 is a diagram showing an example of a MAC CE (1 octet) that stores an instruction value for each bearer identifier (or logical channel identifier) according to an embodiment.
  • M1 to M8 correspond to bearers # 1 to # 8 (or logical channels # 1 to # 8.
  • Each field of M1 to M8 is 1 bit, and each field has one bit.
  • the indicated value for activation (eg, "1") or deactivation (eg, "0") is stored.
  • Step S23 is the same as operation example 1.
  • the UE 100 may send the response to the gNB 200.
  • the PDCP entity of the UE 100 may perform a duplicate packet discarding process of two identical MBS packets transmitted by duplication.
  • the RRC entity of the UE 100 may send a message (RAI: Entity Assistance Information / preference) to the gNB 200 to prompt the gNB 200 to release the RRC connection when the PTP leg is deactivated.
  • RAI Entity Assistance Information / preference
  • the UE 100 may be allowed to transmit the RAI even while the dynamic switching of the PTP leg and the PTM leg is being set.
  • Switching operation between PTP transmission and PTM transmission Next, the operation of switching between PTP transmission and PTM transmission according to the embodiment will be described.
  • the PTP transmission may be a method of transmitting MBS data from the gNB 200 to the UE 100 using a PTP leg (PTP communication path).
  • the PTM transmission may be a method of transmitting MBS data from the gNB 200 to the UE 100 using a PTM leg (PTM communication path).
  • the PTP transmission may be a method of transmitting MBS data from the gNB 200 to the UE 100 using a PTP bearer (PTP communication path) which is a first data radio bearer for PTP.
  • the PTM transmission may be a method of transmitting MBS data from the gNB 200 to the UE 100 using a PTM bearer (PTM communication path) which is a second data radio bearer for PTM.
  • the switching operation between PTP transmission and PTM transmission is an operation of terminating the MBS data transmission of one of the PTP transmissions and the PTM transmissions and at the same time starting the MBS data transmission of the other transmission method.
  • MBS data MBS packet
  • the MBS data MBS packet
  • the receiving unit 110 receives MBS data transmitted from the gNB 200 by either PTP (Point-To-Point) transmission or PTM (Point-To-Multipoint) transmission.
  • the control unit 130 of the UE 100 triggers the transmission of a status report indicating the reception status of MBS data in a predetermined layer of the UE 100 in response to the transmission method being switched between PTP transmission and PTM transmission.
  • the transmission unit 120 of the UE 100 transmits the status report to the gNB 200.
  • the gNB 200 can grasp the reception state of the MBS data of the UE 100 regarding the switching between the PTP transmission and the PTM transmission. Therefore, even if the MBS packet is missing when switching between PTP transmission and PTM transmission, the gNB 200 can easily identify the missing MBS packet. Therefore, when a packet loss of an MBS packet occurs, it can be retransmitted in the PDCP layer (or RLC layer), so that the reliability of communication can be improved.
  • the predetermined layer is the PDCP layer and the status report transmitted from the UE 100 to the gNB 200 is the PDCP status report (PDCP status report).
  • the predetermined layer may be an RLC layer.
  • the status report transmitted from the UE 100 to the gNB 200 may be an RLC status report (RLC Status PDU).
  • FIG. 12 is a diagram showing a configuration example of a PDCP status report according to an embodiment.
  • the PDCP status report has, as the main components, a 1-bit length "D / C” field, a 3-bit length "PDU Type” field, and a 32-bit length "FMC (First Missing”). It has a "COUNT)” field and a variable bit length "Bitmap” field.
  • the "D / C" field is a field indicating whether this PDCP PDU is a PDCP Data PDU or a PDCP Control PDU.
  • the PDCP status report corresponds to the PDCP Control PDU.
  • the "PDU Type” field is a field indicating whether the PDCP Control PDU is "PDCP status report”, "Interspired ROHC feedback", or "EHC feedback”.
  • the "FMC (First Missing COUNT)" field is a field indicating the count value (COUNT) of the PDCP SDU that was first missing in the reordering window.
  • the count value (COUNT) is composed of an HFN (Hyper Frame Number) and a PDCP sequence number.
  • the "Bitmap” field is a field indicating the missing PDCP SDU and the PDCP SDU correctly received by the receiving PDCP entity. Specifically, the "Bitmap” field indicates the reception status of PDCP SDU after FMC as "0" (missing) or "1" (correctly received).
  • FIG. 13 is a diagram showing a switching operation from PTM transmission to PTP transmission according to one embodiment.
  • the gNB 200 has established the MBS connection of the shared MBS data distribution (Shared MBS Traffic Delivery) shown in FIG. 7 as 5GC20.
  • step S101 the gNB 200 starts PTM transmission of MBS data. Specifically, the gNB 200 initiates multicast or broadcast transmission of MBS data belonging to a certain MBS session.
  • step S102 the gNB 200 transmits MBS data belonging to a certain MBS session by PTM.
  • the UE 100 receives the MBS data.
  • step S103 the PDCP entity of the UE 100 uses the sequence number of the MBS data (PDCP SDU) transmitted by the PTM that was successfully received and the sequence of the MBS data that failed to be received in order to generate the PDCP status report. Each number may be recorded.
  • PDCP SDU sequence number of the MBS data
  • step S104 the gNB 200 transmits an instruction for switching from PTM transmission to PTP transmission to the UE 100.
  • This instruction may be a PTM leg deactivation instruction and / or a PTP leg activation instruction.
  • This instruction may be a change instruction from a PTM bearer to a PTP bearer by an RRC message (for example, an RRC Modification message).
  • This instruction may include a transmission instruction or transmission setting for a PDCP status report.
  • the UE 100 may voluntarily trigger (step S107) and transmit the PDCP status report (step S108) even if there is no transmission instruction or transmission setting of the PDCP status report from the gNB 200.
  • step S105 the gNB 200 and the UE 100 perform a switching process from PTM transmission to PTP transmission. Specifically, the gNB 200 and the UE 100 end the PTM transmission of the MBS data belonging to a certain MBS session and start the PTP transmission of the MBS data belonging to the MBS session.
  • step S106 gNB200 transmits MBS data belonging to the MBS session by PTP.
  • the UE 100 receives the MBS data.
  • the UE 100 may fail to receive the last MBS data (PDCP SDU) transmitted by the PTM due to the switching process from the PTM transmission to the PTP transmission.
  • the PDCP entity of the UE 100 records the sequence number of the MBS data (PDCP SDU) that failed to be received among the MBS data (PDCP SDU) transmitted by the PTM.
  • the UE 100 may fail to receive the first MBS data (PDCP SDU) transmitted by PTP due to the switching process from PTM transmission to PTP transmission.
  • the PDCP entity of the UE 100 records the sequence number of the MBS data (PDCP SDU) that failed to be received among the MBS data (PDCP SDU) transmitted by PTP.
  • step S107 the PDCP entity of UE100 triggers the transmission of the PDCP status report. Specifically, the PDCP entity of UE 100 generates a PDCP status report as shown in FIG. 12 and passes the PDCP status report to a lower layer.
  • the PDCP entity of the UE 100 may trigger the transmission of the PDCP status report when receiving the instruction of step S104, or trigger the transmission of the PDCP status report when the switching process of step S105 is performed. It is also good.
  • the PDCP entity of the UE 100 may trigger the transmission of the PDCP status report after a lapse of a certain period of time after receiving the instruction of step S104, or the PDCP status report after a lapse of a certain time after performing the switching process of step S105. May be triggered to send.
  • a fixed time timer value
  • condition for the UE 100 to trigger the transmission of the PDCP status report there may be a condition that the sequence number of the MBS data last received by the PTM and the sequence number of the MBS data first received by the PTP are discontinuous.
  • the PDCP entity of the UE 100 triggers the transmission of the PDCP status report only when it detects such a discontinuity.
  • the condition for the UE 100 to trigger the transmission of the PDCP status report may be that it has detected a missing (discontinuous sequence number) in the MBS data transmitted by the PTM.
  • step S108 the lower layer of UE100 (RLC entity, MAC entity, and PHY entity) transmits the PDCP status report to gNB200.
  • the gNB 200 receives a PDCP status report.
  • step S109 the gNB 200 retransmits the missing MBS data to the UE 100 by PTP based on the missing packet information (FMC and Bitmap) included in the PDCP status report.
  • the UE 100 receives the MBS data retransmitted by PTP.
  • the missing MBS data can be identified based on the PDCP status report, and the missing MBS data can be supplemented by retransmission in the PDCP layer. ..
  • FIG. 14 is a diagram showing a switching operation from PTP transmission to PTM transmission according to one embodiment.
  • step S201 the gNB 200 starts PTP transmission of MBS data. Specifically, the gNB 200 initiates unicast transmission of MBS data belonging to a certain MBS session.
  • step S202 gNB200 transmits MBS data belonging to a certain MBS session by PTM.
  • the UE 100 receives the MBS data.
  • step S203 the PDCP entity of the UE 100 uses the sequence number of the MBS data (PDCP SDU) transmitted by PTP, the sequence number of the MBS data successfully received, and the sequence of the MBS data failed to be received, in order to generate the PDCP status report. Each number may be recorded.
  • PDCP SDU sequence number of the MBS data
  • step S204 the gNB 200 transmits an instruction for switching from PTP transmission to PTM transmission to the UE 100.
  • This instruction may be a PTP leg deactivation instruction and / or a PTM leg activation instruction.
  • This instruction may be a change instruction from a PTP bearer to a PTM bearer by an RRC message (for example, an RRC Modification message).
  • This instruction may include a transmission instruction or transmission setting for a PDCP status report.
  • the UE 100 may voluntarily trigger (step S207) and transmit the PDCP status report even if there is no transmission instruction or transmission setting of the PDCP status report from the gNB 200 (step S208).
  • step S205 the gNB 200 and the UE 100 perform a switching process from PTP transmission to PTM transmission. Specifically, the gNB 200 and the UE 100 end the PTP transmission of the MBS data belonging to a certain MBS session and start the PTM transmission of the MBS data belonging to the MBS session.
  • step S206 the gNB 200 transmits MBS data belonging to the MBS session by PTM.
  • the UE 100 receives the MBS data.
  • the UE 100 may fail to receive the last MBS data (PDCP SDU) transmitted by PTP due to the switching process from PTP transmission to PTM transmission.
  • the PDCP entity of the UE 100 records the sequence number of the MBS data (PDCP SDU) that failed to be received among the MBS data (PDCP SDU) transmitted by PTP.
  • the UE 100 may fail to receive the first MBS data (PDCP SDU) transmitted by the PTM due to the switching process from the PTP transmission to the PTM transmission.
  • the PDCP entity of the UE 100 records the sequence number of the MBS data (PDCP SDU) that failed to be received among the MBS data (PDCP SDU) transmitted by the PTM.
  • step S207 the PDCP entity of UE100 triggers the transmission of the PDCP status report. Specifically, the PDCP entity of UE 100 generates a PDCP status report as shown in FIG. 12 and passes the PDCP status report to a lower layer.
  • the PDCP entity of the UE 100 may trigger the transmission of the PDCP status report when receiving the instruction in step S204, or trigger the transmission of the PDCP status report when the switching process of step S205 is performed. May be good.
  • the PDCP entity of the UE 100 may trigger the transmission of the PDCP status report after a certain period of time has elapsed from receiving the instruction in step S204, or the PDCP status report after a certain period of time has elapsed from the switching process of step S205. May be triggered to send.
  • a fixed time timer value
  • condition for the UE 100 to trigger the transmission of the PDCP status report there may be a condition that the sequence number of the MBS data last received by the PTP and the sequence number of the MBS data first received by the PTM are discontinuous.
  • the PDCP entity of the UE 100 triggers the transmission of the PDCP status report only when it detects such a discontinuity.
  • the condition for the UE 100 to trigger the transmission of the PDCP status report may be the detection of a missing item (discontinuity of sequence numbers) in the MBS data transmitted by PTP.
  • step S208 the lower layer of UE100 (RLC entity, MAC entity, and PHY entity) transmits the PDCP status report to gNB200.
  • the gNB 200 receives a PDCP status report.
  • step S209 the gNB 200 retransmits the missing MBS data to the UE 100 by PTM based on the missing packet information (FMC and Bitmap) included in the PDCP status report.
  • the UE 100 receives the MBS data retransmitted by the PTM.
  • the missing MBS data can be identified based on the PDCP status report, and the missing MBS data can be supplemented by retransmission in the PDCP layer. ..
  • FIG. 15 is a diagram showing an example of changing the switching operation from PTP transmission to PTM transmission according to one embodiment.
  • steps S301 to S308 is the same as that of FIG. However, in steps S304 and S305, the gNB 200 and the UE 100 maintain an active state without deactivating the PTP communication path (PTP leg).
  • step S309 the gNB 200 retransmits the missing MBS data to the UE 100 by PTP based on the missing packet information (FMC and Bitmap) included in the PDCP status report.
  • the UE 100 receives the MBS data retransmitted by PTP.
  • the gNB 200 and the UE 100 perform the MBS data retransmission processing by the PTP while performing the MBS data initial transmission processing by the PTM.
  • the MBS data can be retransmitted by PTP only to the UE 100 in which the MBS data is missing, so that efficient retransmission processing can be realized.
  • the UE 100 may voluntarily stop the reception processing in the PTP when the missing MBS data is supplemented by retransmission.
  • the PTP communication path is configured by the PTP leg and the PTM communication path is configured by the PTM leg using the split MBS bearer has been described.
  • the PTP communication path may be configured by the first radio bearer for PTP and the PTM communication path may be configured by the second radio bearer for PTM.
  • the predetermined layer is the PDCP layer and the status report transmitted from the UE 100 to the gNB 200 is the PDCP status report (PDCP status report).
  • the PDCP entity in the above-described embodiment may be read as an RLC entity, and the PDCP status report may be read as an RLC status report (RLC Status PDU).
  • Each of the above-mentioned operation flows is not limited to the case where they are individually and independently implemented, but can be implemented by combining two or more operation flows. For example, some steps of one operation flow may be added to another operation flow, or some steps of one operation flow may be replaced with some steps of another operation flow.
  • the base station may be an NR base station (gNB)
  • the base station may be an LTE base station (eNB).
  • the base station may be a relay node such as an IAB (Integrated Access and Backhaul) node.
  • the base station may be a DU (Distributed Unit) of an IAB node.
  • a program may be provided that causes a computer to execute each process performed by the UE 100 or gNB 200.
  • the program may be recorded on a computer-readable medium.
  • Computer-readable media can be used to install programs on a computer.
  • the computer-readable medium on which the program is recorded may be a non-transient recording medium.
  • the non-transient recording medium is not particularly limited, but may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.
  • a circuit that executes each process performed by the UE 100 or the gNB 200 may be integrated, and at least a part of the UE 100 or the gNB 200 may be configured as a semiconductor integrated circuit (chipset, SoC).
  • NG-RAN 5G RAN
  • 5GC 5G CN
  • UE 110 Receiver unit 120: Transmitter unit 130: Control unit 200: gNB 210: Transmitter 220: Receiver 230: Control 240: Backhaul communication unit

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2021/046549 2020-12-23 2021-12-16 通信制御方法及びユーザ装置 Ceased WO2022138450A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2022571378A JP7549043B2 (ja) 2020-12-23 2021-12-16 通信制御方法及びユーザ装置
US18/339,896 US20230337327A1 (en) 2020-12-23 2023-06-22 Communication control method and user equipment
JP2024147391A JP7723164B2 (ja) 2020-12-23 2024-08-29 通信制御方法、ユーザ装置、ネットワークノード、プロセッサ、プログラム及び移動通信システム

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020214243 2020-12-23
JP2020-214243 2020-12-23

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/339,896 Continuation US20230337327A1 (en) 2020-12-23 2023-06-22 Communication control method and user equipment

Publications (1)

Publication Number Publication Date
WO2022138450A1 true WO2022138450A1 (ja) 2022-06-30

Family

ID=82159337

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/046549 Ceased WO2022138450A1 (ja) 2020-12-23 2021-12-16 通信制御方法及びユーザ装置

Country Status (3)

Country Link
US (1) US20230337327A1 (https=)
JP (2) JP7549043B2 (https=)
WO (1) WO2022138450A1 (https=)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024082295A1 (zh) * 2022-10-21 2024-04-25 北京小米移动软件有限公司 小区处理、小区处理指示方法和装置
JP2024543486A (ja) * 2021-11-15 2024-11-21 中国移動通信有限公司研究院 データ伝送方法、装置、通信機器及び記憶媒体
JP2025522963A (ja) * 2022-07-09 2025-07-17 グーグル エルエルシー マルチキャストセッション確立の管理

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20230147066A (ko) * 2021-02-25 2023-10-20 미쓰비시덴키 가부시키가이샤 통신 시스템 및 통신 단말

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111901765A (zh) 2020-04-27 2020-11-06 中兴通讯股份有限公司 模式配置方法、装置、设备和存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
VIVO: "Dynamic PTM PTP switch for RRC Connected UE", 3GPP DRAFT; R2-2010216, vol. RAN WG2, 23 October 2020 (2020-10-23), pages 1 - 8, XP051942897 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2024543486A (ja) * 2021-11-15 2024-11-21 中国移動通信有限公司研究院 データ伝送方法、装置、通信機器及び記憶媒体
JP2025522963A (ja) * 2022-07-09 2025-07-17 グーグル エルエルシー マルチキャストセッション確立の管理
WO2024082295A1 (zh) * 2022-10-21 2024-04-25 北京小米移动软件有限公司 小区处理、小区处理指示方法和装置

Also Published As

Publication number Publication date
JPWO2022138450A1 (https=) 2022-06-30
JP7549043B2 (ja) 2024-09-10
US20230337327A1 (en) 2023-10-19
JP7723164B2 (ja) 2025-08-13
JP2024167332A (ja) 2024-12-03

Similar Documents

Publication Publication Date Title
US20240080939A1 (en) Communication control method and user equipment
JP7723164B2 (ja) 通信制御方法、ユーザ装置、ネットワークノード、プロセッサ、プログラム及び移動通信システム
US20240015850A1 (en) Communication control method and user equipment
WO2022085717A1 (ja) 通信制御方法
US20230261970A1 (en) Communication control method
US20240080940A1 (en) Communication control method
US20260075389A1 (en) Communication control method
WO2022153991A1 (ja) 通信制御方法
JP2023100957A (ja) 通信制御方法、ユーザ装置及びプロセッサ
US20240260124A1 (en) Communication method
US12574992B2 (en) Communication control method and user equipment utilizing an inactivity timer for multicast broadcast service
JP2025024185A (ja) 通信制御方法及びユーザ装置
US20260059384A1 (en) Communication control method
US20240179800A1 (en) Communication method and user equipment

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022571378

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21910598

Country of ref document: EP

Kind code of ref document: A1