WO2022234847A1 - 通信制御方法及びユーザ装置 - Google Patents
通信制御方法及びユーザ装置 Download PDFInfo
- Publication number
- WO2022234847A1 WO2022234847A1 PCT/JP2022/019529 JP2022019529W WO2022234847A1 WO 2022234847 A1 WO2022234847 A1 WO 2022234847A1 JP 2022019529 W JP2022019529 W JP 2022019529W WO 2022234847 A1 WO2022234847 A1 WO 2022234847A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mbs
- data
- timer
- multicast
- rrc
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 40
- 238000000034 method Methods 0.000 title claims abstract description 32
- 230000004044 response Effects 0.000 claims abstract description 19
- 238000010295 mobile communication Methods 0.000 claims abstract description 16
- 230000011664 signaling Effects 0.000 claims abstract description 16
- 230000005540 biological transmission Effects 0.000 abstract description 53
- 238000010586 diagram Methods 0.000 description 17
- 230000007704 transition Effects 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 238000012384 transportation and delivery Methods 0.000 description 5
- 238000007726 management method Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 2
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 2
- 230000009849 deactivation Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000002716 delivery method Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006866 deterioration Effects 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
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
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/38—Connection release triggered by timers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
Definitions
- the present disclosure relates to a communication control method and user equipment used in a mobile communication system.
- NR New Radio
- RAT Radio Access Technology
- LTE Long Term Evolution
- a 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).
- the communication control method includes, in an RRC connected state, receiving MBS data from a base station, managing a timer for measuring a time during which data and signaling are not transmitted/received to/from the base station, and and transitioning from the RRC connected state to an RRC idle state upon expiration of the RRC connected state.
- Managing the timer includes, when receiving the MBS data transmitted by multicast or broadcast, controlling the timer not to start even if the MBS data is received.
- a 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).
- the communication control method includes managing a timer that counts time during which data is not transmitted or received from the base station, and transitioning from an RRC connected state to an RRC idle state in response to expiration of the timer. and Managing the timer includes restarting the timer by transmitting or receiving restart information before the timer expires when MBS data transmitted by multicast or broadcast is received from the base station. include.
- a user device comprises a processor that executes the communication control method according to the first aspect or the second aspect.
- FIG. 1 is a diagram showing the configuration of a mobile communication system according to one embodiment; FIG. It is a figure which shows the structure of UE (user apparatus) which concerns on one Embodiment.
- FIG. 2 is a diagram showing the configuration of a gNB (base station) according to one embodiment; FIG. 2 is a diagram showing the configuration of a protocol stack of a user plane radio interface that handles data; FIG. 2 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals); FIG. 2 is a diagram showing a correspondence relationship between a downlink logical channel and a transport channel according to an embodiment; FIG. 3 illustrates a method of distributing MBS data according to one embodiment; FIG.
- FIG. 4 illustrates a split MBS bearer according to one embodiment; It is a figure which shows the operation example of the 1st operation pattern which concerns on one Embodiment. It is a figure which shows the operation example of the 2nd operation pattern which concerns on one Embodiment. It is a figure which shows the operation example of the 3rd operation pattern which concerns on one Embodiment. It is a figure which shows the operation example of the 4th operation pattern which concerns on one Embodiment.
- NR 5G system
- an object of the present disclosure is to provide a communication control method and user equipment that realize improved multicast/broadcast services.
- FIG. 1 is a diagram showing the configuration of a mobile communication system according to one embodiment.
- This mobile communication system conforms to the 5th generation system (5GS: 5th Generation System) of the 3GPP standard.
- 5GS will be described below as an example
- an LTE (Long Term Evolution) system may be at least partially applied to the mobile communication system.
- a sixth generation (6G) system may be at least partially applied to the mobile communication system.
- the mobile communication system includes a user equipment (UE: User Equipment) 100, a 5G radio access network (NG-RAN: Next Generation Radio Access Network) 10, a 5G core network (5GC: 5G Core Network) 20.
- UE User Equipment
- NG-RAN Next Generation Radio Access Network
- 5G core network 5G Core Network
- the UE 100 is a mobile wireless communication device.
- the UE 100 may be any device as long as it is used by a user.
- the UE 100 is a mobile phone terminal (including a smartphone) and/or a tablet terminal, a notebook PC, a communication module (including a communication card or chipset), a sensor or a device provided in a sensor, a vehicle or a device provided in a vehicle ( (Vehicle UE), aircraft or equipment installed in the aircraft (Aerial UE).
- the NG-RAN 10 includes a base station (called “gNB” in the 5G system) 200.
- the gNBs 200 are interconnected via an Xn interface, which is an interface between base stations.
- the gNB 200 manages one or more cells.
- the gNB 200 performs radio communication with the UE 100 that has established connection with its own cell.
- the gNB 200 has a radio resource management (RRM) function, a user data (hereinafter simply referred to as “data”) routing function, a measurement control function for mobility control/scheduling, and the like.
- RRM radio resource management
- a “cell” is used as a term indicating the minimum unit of a wireless communication area.
- a “cell” is also used as a term indicating a function or resource for radio communication with the UE 100 .
- One cell belongs to one carrier frequency.
- the gNB can also be connected to the EPC (Evolved Packet Core), which is the LTE core network.
- EPC Evolved Packet Core
- LTE base stations can also connect to 5GC.
- An LTE base station and a gNB may also be connected via an inter-base station interface.
- 5GC20 includes AMF (Access and Mobility Management Function) and UPF (User Plane Function) 300.
- AMF performs various mobility control etc. with respect to UE100.
- AMF manages the mobility of UE 100 by communicating with UE 100 using NAS (Non-Access Stratum) signaling.
- the UPF controls data transfer.
- AMF and UPF are connected to gNB 200 via NG interface, which is a base station-core network interface.
- FIG. 2 is a diagram showing the configuration of the UE 100 (user equipment) according to one embodiment.
- the UE 100 includes a receiver 110, a transmitter 120, and a controller .
- the receiving unit 110 performs various types of reception under the control of the control unit 130.
- the receiver 110 includes an antenna and a receiver.
- the receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal (received signal) to control section 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 a baseband signal (transmission signal) output from the control unit 130 into a radio signal and transmits the radio signal from an antenna.
- Control unit 130 performs various controls in the UE 100.
- Control unit 130 includes at least one processor and at least one memory.
- the memory stores programs 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 programs stored in the memory to perform various processes.
- FIG. 3 is a diagram showing the configuration of the gNB 200 (base station) according to one embodiment.
- the gNB 200 includes a transmitter 210, a receiver 220, a controller 230, and a backhaul communicator 240.
- the transmission unit 210 performs various transmissions under the control of the control unit 230.
- Transmitter 210 includes an antenna and a transmitter.
- the transmitter converts a baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits the radio signal from an antenna.
- the receiving unit 220 performs various types of reception under the control of the control unit 230.
- the receiver 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 the baseband signal (received signal) to the control unit 230 .
- Control unit 230 performs various controls in the gNB200.
- Control unit 230 includes at least one processor and at least one memory.
- the memory stores programs 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 programs 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.
- Backhaul communication unit 240 is connected to AMF/UPF 300 via a base station-core network interface.
- the gNB may be composed of a CU (Central Unit) and a DU (Distributed Unit) (that is, functionally divided), and the two units may be connected via an F1 interface.
- FIG. 4 is a diagram showing the configuration of the protocol stack of the radio interface of the user plane that handles data.
- the radio interface protocol of the user plane includes a physical (PHY) layer, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, SDAP (Service Data Adaptation Protocol) layer.
- PHY physical
- MAC Medium Access Control
- RLC Radio Link Control
- PDCP Packet Data Convergence Protocol
- SDAP Service Data Adaptation Protocol
- the PHY layer performs encoding/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 physical channels.
- the MAC layer performs data priority control, retransmission processing by hybrid ARQ (HARQ: Hybrid Automatic Repeat reQuest), random access procedures, 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 transport channels.
- the MAC layer of gNB 200 includes a scheduler. The scheduler determines uplink and downlink transport formats (transport block size, modulation and coding scheme (MCS: Modulation and Coding Scheme)) and resource blocks to be allocated to UE 100 .
- MCS Modulation and Coding Scheme
- the RLC layer uses the functions of the MAC layer and PHY layer to transmit data to the RLC layer on the receiving side. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the gNB 200 via logical channels.
- the PDCP layer performs header compression/decompression and encryption/decryption.
- the SDAP layer maps IP flows, which are units for QoS (Quality of Service) control by the core network, and radio bearers, which are units for QoS control by AS (Access Stratum). Note that SDAP may not be present when the RAN is connected to the EPC.
- FIG. 5 is a diagram showing the protocol stack configuration of the radio interface of the control plane that handles signaling (control signals).
- the radio interface protocol stack of the control plane has an RRC (Radio Resource Control) layer and a NAS (Non-Access Stratum) layer instead of the SDAP layer shown in FIG.
- RRC signaling for various settings is transmitted between the RRC layer of the UE 100 and the RRC layer of the gNB 200.
- the RRC layer controls logical, transport and physical channels according to establishment, re-establishment and release of radio bearers.
- RRC connection connection between the RRC of UE 100 and the RRC of gNB 200
- UE 100 is in the RRC connected state.
- RRC connection no connection between RRC of UE 100 and RRC of gNB 200
- UE 100 is in RRC idle state.
- UE 100 is in RRC inactive state.
- the NAS layer located above the RRC layer performs session management and mobility management.
- NAS signaling is transmitted between the NAS layer of UE 100 and the NAS layer of AMF 300B.
- the UE 100 has an application layer and the like in addition to the radio interface protocol.
- MBS is a service that enables data transmission from the NG-RAN 10 to the UE 100 via broadcast or multicast, that is, point-to-multipoint (PTM).
- MBS may be called MBMS (Multimedia Broadcast and Multicast Service).
- Use cases (service types) of MBS include public safety communication, mission critical communication, V2X (Vehicle to Everything) communication, IPv4 or IPv6 multicast distribution, IPTV (Internet Protocol TeleVision), group communication, and software distribution. .
- FIG. 6 is a diagram showing a correspondence relationship between downlink logical channels and transport channels according to an embodiment.
- 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 in an MBSFN area consisting of multiple cells, each cell performs synchronous transmission of the same signal (same data) in the same MBSFN subframe.
- SC-PTM transmission The logical channels used for SC-PTM transmission are SC-MTCH (Single Cell Multicast Traffic Channel) and SC-MCCH (Single Cell Multicast Control Channel), and the transport channel used for SC-PTM transmission is DL-SCH (Downlink Shared Channel). ).
- SC-PTM transmission is primarily designed for single-cell transmission, with broadcast or multicast data transmission on a cell-by-cell basis.
- Physical channels used for SC-PTM transmission are PDCCH (Physical Downlink Control Channel) and PDSCH (Physical Downlink Control Channel), enabling dynamic resource allocation.
- MBS may be provided using a scheme similar to the SC-PTM transmission scheme.
- MBS may be provided using the MBSFN transmission scheme.
- MBS may be read as multicast.
- MBS may be provided by broadcast.
- MBS data shall refer to data provided by MBS.
- MBS control channel shall refer to MCCH or SC-MCCH.
- MBS traffic channel shall refer to MTCH or SC-MTCH.
- MBS data may also be transmitted by unicast.
- MBS data may also be referred to as MBS packets or MBS traffic.
- the network can provide different MBS services for each MBS session.
- An MBS session is identified by at least one of a 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
- MBS session identifiers may be referred to as MBS service identifiers or multicast group identifiers.
- MBS sessions include multicast sessions and broadcast sessions.
- a multicast session is a session for delivering multicast services.
- a multicast service provides a service to a group of UEs 100 participating in a multicast session for applications that require reliable QoS.
- a multicast session can be used by UE 100 in the RRC connected state.
- MBS data is multicast.
- UE 100 needs to be in RRC connected state to receive a multicast session.
- a broadcast session is a session for delivering broadcast services.
- a broadcast service provides service to all UEs 100 within a specific service area.
- a broadcast session can be used by UE 100 in all RRC states (RRC idle state, RRC inactive state and RRC connected state).
- FIG. 7 is a diagram showing a method of distributing MBS data according to one embodiment.
- MBS data (MBS Traffic) is distributed to multiple UEs from a single data source (application service provider).
- a 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 In shared MBS data delivery, a connection is established between NG-RAN10 and 5GC20, which are 5G radio access networks (5G RAN), and MBS data is delivered from 5GC20 to NG-RAN10.
- 5G RAN 5G radio access networks
- MBS connection In the following, such a connection (tunnel) will be referred to as an "MBS connection”.
- An MBS connection may also be called a Shared MBS Traffic delivery connection or a shared transport.
- the MBS connection terminates at the NG-RAN 10 (ie gNB 200).
- An MBS connection may have a one-to-one correspondence with an MBS session.
- gNB 200 selects either PTP (Point-to-Point: unicast) or PTM (Point-to-Multipoint: multicast or broadcast) transmission method at its own discretion, and transmits MBS data to UE 100 in 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-RAN 10 and UE 100, and MBS data is delivered individually from 5GC 20 to UE 100.
- MBS data is delivered individually from 5GC 20 to UE 100.
- Such a unicast may be called a PDU Session.
- Unicast (PDU session) terminates at the UE 100 .
- split MBS bearer Next, a split MBS bearer according to one embodiment will be described.
- the gNB 200 can configure the UE 100 with an MBS bearer separated into a PTP communication path and a PTM communication path (hereinafter referred to as a "split MBS bearer" as appropriate). This allows the gNB 200 to dynamically switch transmission of MBS data to the UE 100 between PTP (PTP communication path) and PTM (PTM communication path). Alternatively, the gNB 200 can double transmit the same MBS data using both PTP (PTP communication path) and PTM (PTM communication path) to increase reliability.
- the predetermined layer that terminates the split is the MAC layer (HARQ), RLC layer, PDCP layer, or SDAP layer.
- HARQ MAC layer
- RLC layer PDCP layer
- SDAP layer SDAP layer.
- FIG. 8 is a diagram illustrating a split MBS bearer according to one embodiment.
- a PTP communication path is called a PTP leg and a PTM communication path is called a PTM leg.
- a functional unit corresponding to each layer is called an entity.
- MBS data is multicast.
- each of the PDCP entity of gNB 200 and the PDCP entity of UE 100 separates MBS bearers (data radio bearers) used for MBS into PTP legs and PTM legs.
- MBS bearers data radio bearers
- a PDCP entity is provided for each bearer.
- Each of gNB 200 and UE 100 has two RLC entities, one MAC entity, and one PHY entity provided for each leg.
- a PHY entity may be provided for each leg.
- the UE 100 may have two MAC entities.
- the PHY entity uses a cell RNTI (C-RNTI: Cell Radio Network Temporary Identifier) assigned to UE 100 on a one-to-one basis to transmit and receive PTP leg data.
- C-RNTI Cell Radio Network Temporary Identifier
- the PHY entity transmits and receives data of the PTM leg using a group RNTI (G-RNTI: Group Radio Network Temporary Identifier) assigned one-to-one with the MBS session.
- the C-RNTI is different for each UE 100, but the G-RNTI is a common RNTI for multiple UEs 100 that receive one MBS session.
- a split MBS bearer is set from the gNB 200 to the UE 100, and the PTM leg is activated. must have been In other words, even if a split MBS bearer is configured in the UE 100, the gNB 200 cannot perform PTM transmission of MBS data using this PTM leg when the PTM leg is in a deactivation state.
- a split MBS bearer in order for the gNB 200 and the UE 100 to perform PTP transmission (unicast) of MBS data using the PTP leg, a split MBS bearer must be set from the gNB 200 to the UE 100 and the PTP leg must be activated. There is In other words, even if a split MBS bearer is configured in the UE 100, the gNB 200 cannot perform PTP transmission of MBS data using this PTP leg when the PTP leg is in an inactive state.
- UE 100 monitors the PDCCH (Physical Downlink Control Channel) to which the G-RNTI associated with the MBS session is applied in a state where the PTM leg is activated (that is, performs blind deactivation of the PDCCH using the G-RNTI). coding). UE 100 may monitor the PDCCH only at scheduling opportunities for the MBS session.
- PDCCH Physical Downlink Control Channel
- the UE 100 does not monitor the PDCCH to which the G-RNTI associated with the MBS session is applied while the PTM leg is deactivated (that is, does not perform blind decoding of the PDCCH using the G-RNTI). .
- the UE 100 monitors the PDCCH to which the C-RNTI is applied while the PTP leg is activated.
- DRX Discontinuous Reception
- UE 100 monitors PDCCH during the set On Duration.
- UE 100 may monitor the PDCCH of the cell even if the cell is deactivated.
- the UE 100 may monitor the PDCCH to which the C-RNTI is applied in preparation for normal unicast downlink transmission other than MBS data while the PTP leg is deactivated. However, when a cell (frequency) associated with an MBS session is designated, UE 100 may not monitor the PDCCH for the MBS session.
- a split MBS bearer as described above is set by an RRC message (for example, an RRC Reconfiguration message) transmitted from the RRC entity of gNB200 to the RRC entity of UE100.
- RRC message for example, an RRC Reconfiguration message
- RRC state transition by data inactivity timer Next, RRC state transition by a data inactivity timer according to an embodiment will be described.
- a data inactivity timer is specified in the current specifications of 5G/NR.
- the data inactivity timer is a timer that measures the time during which data and signaling between the UE 100 and the gNB 200 are not transmitted or received.
- a data inactivity timer can be set by the gNB 200 for the UE 100 in the RRC connected state.
- the UE 100 transitions from the RRC connected state to the RRC idle state upon expiration of the data inactivity timer.
- the UE 100 When the data inactivity timer is set, the UE 100 starts the data inactivity timer in response to transmission or reception of data or signaling. UE 100 restarts the data inactivity timer in response to transmission or reception of data or signaling before the data inactivity timer expires. Note that "restarting the data inactivity timer” means resetting and restarting the data inactivity timer.
- a DTCH logical channel is a dedicated logical channel for data transmission.
- a DCCH logical channel is a dedicated logical channel for signaling transmission.
- a DCCH logical channel is a dedicated logical channel for signaling transmission.
- the gNB 200 sets up an MBS bearer for the UE 100 in the RRC connected state, and starts transmitting MBS data by multicast. At this point, the gNB 200 recognizes that the UE 100 is in the RRC connected state. The UE 100 starts a data inactivity timer upon receiving MBS data transmitted by multicast. And when the data inactivity timer is running, if the radio condition deteriorates in the UE 100, the UE 100 cannot successfully receive MBS data and does not restart the data inactivity timer. After that, the UE 100 transitions to the RRC idle state upon expiration of the data inactivity timer. This causes a problem of RRC state mismatch between the gNB 200 and the UE 100 .
- the MBS data may be provided not only by multicast but also by broadcast.
- UE 100 generally transmits feedback information (eg, acknowledgment information (ACK/NACK)) regarding data reception to gNB 200 when receiving data transmitted by normal unicast. Therefore, as described above, even if the UE 100 transitions to the RRC idle state due to deterioration of the radio state, the gNB 200 does not receive the feedback information from the UE 100, and the UE 100 transitions to the RRC idle state. I can guess. Therefore, the problem of RRC state mismatch is not significant.
- feedback information eg, acknowledgment information (ACK/NACK)
- the UE 100 receiving MBS data transmitted by multicast means any of the following: 1) The UE 100 is configured with an MBS bearer having only a PTM leg, and receives MBS data via the MBS bearer. do. 2) UE 100 is configured with a split MBS bearer having a PTM leg and a PTP leg, and receives MBS data via the PTM leg. 3) UE 100 receives MBS data using G-RNTI.
- the UE 100 manages the data inactivity timer.
- the UE 100 controls not to start the data inactivity timer even if the MBS data is received.
- the UE 100 since the UE 100 does not start the data inactivity timer, there is no transition to the RRC idle state in response to the expiration of the data inactivity timer, and the above-described RRC state mismatch problem is resolved.
- the UE 100 when receiving MBS data transmitted by unicast, the UE 100 starts or restarts the data inactivity timer upon receiving the MBS data.
- the problem of RRC state inconsistency is not significant because the transmission of feedback information is configured for unicast.
- the UE 100 receiving MBS data transmitted by unicast means any of the following: 1) The UE 100 is configured with an MBS bearer having only a PTP leg, and receives the MBS data via the MBS bearer. receive. 2) UE 100 is configured with a split MBS bearer having a PTM leg and a PTP leg, and receives MBS data via the PTP leg. 3) UE 100 receives MBS data using C-RNTI.
- FIG. 9 is a diagram showing an operation example of the first operation pattern according to one embodiment.
- the UE 100 is in the RRC connected state, and the data inactivity timer is set from the gNB 200 to the UE 100.
- step S101 the gNB 200 transmits MBS data by multicast.
- the UE 100 receives MBS data transmitted by multicast.
- step S102 the UE 100 receives the MBS data transmitted by multicast, but controls so as not to start the data inactivity timer. Note that even if the data inactivity timer has already started at this point, the UE 100 controls not to restart the data inactivity timer. For example, before step S102, the UE 100 starts a data inactivity timer in response to normal unicast transmission and reception of data (data that is not MBS data), and in step S102, the UE 100 starts the data inactivity timer. Control not to restart.
- step S103 the gNB 200 instructs the UE 100 to receive MBS data by unicast.
- UE100 receives this instruction from gNB200.
- this instruction may be an RRC Reconfiguration message that sets up an MBS bearer with only a PTP leg, or an instruction to activate the PTP leg of a split MBS bearer already set in the UE 100 (for example, MAC CE ( Control Element) or DCI (Donwlink Control Information)).
- MAC CE Control Element
- DCI Donwlink Control Information
- step S104 the gNB 200 transmits MBS data to the UE 100 by unicast.
- the UE 100 receives MBS data transmitted by unicast.
- step S105 the UE 100 starts a data inactivity timer in response to receiving MBS data transmitted by unicast.
- steps S106 and S107 the UE 100 restarts the data inactivity timer in response to receiving MBS data transmitted by unicast.
- the UE 100 controls not to start the data inactivity timer even if the MBS data is received. This makes it possible to simplify the process of determining whether or not to start the data inactivity timer in the UE 100 .
- FIG. 10 is a diagram showing an operation example of the second operation pattern according to one embodiment.
- this operation example it is assumed that the UE 100 is in the RRC connected state and the data inactivity timer is set from the gNB 200 to the UE 100.
- step S201 the gNB 200 transmits MBS data by unicast or multicast.
- UE 100 receives MBS data.
- step S202 the UE 100 receives MBS data, but controls so as not to start the data inactivity timer. Note that even if the data inactivity timer has already started at this point, the UE 100 controls not to restart the data inactivity timer. For example, before step S202, UE 100 starts a data inactivity timer in response to normal unicast transmission and reception of data (data that is not MBS data), and in step S202, UE 100 starts the data inactivity timer. Control not to restart.
- the UE 100 controls to start/not start the data inactivity timer when MBS data is received, according to the setting information from the gNB 200 .
- FIG. 11 is a diagram showing an operation example of the third operation pattern according to one embodiment. In this operation example, it is assumed that the UE 100 is in the RRC connected state and the data inactivity timer is set from the gNB 200 to the UE 100.
- step S301 the gNB 200 transmits to the UE 100 setting information for setting whether to start the data inactivity timer when receiving MBS data.
- UE100 receives the setting information from gNB200.
- the configuration information is sent to the UE 100 in, for example, an RRC Reconfiguration message.
- the configuration information may further include an MBS session identifier (such as TMGI) corresponding to the MBS data.
- the configuration information includes, for each of multiple MBS sessions that the gNB 200 stops, the identifier of the MBS session (such as TMGI) and whether or not to start the data inactivity timer when receiving MBS data belonging to the MBS session. Contains a set of information to set.
- step S302 the gNB 200 transmits MBS data.
- UE 100 receives MBS data.
- step S303 when MBS data is received, the UE 100 controls to start/not start the data inactivity timer according to the setting information received in step S301.
- the setting information may be information for setting whether to transmit feedback information (eg, acknowledgment information (ACK/NACK)) for MBS data.
- feedback information eg, acknowledgment information (ACK/NACK)
- UE 100 starts a data inactivity timer when receiving MBS data for which transmission of feedback information is set, and starts a data inactivity timer when receiving MBS data for which transmission of feedback information is not set. Control not to start.
- the data inactivity timer covers data and signaling sent and received by unicast.
- the UE 100 receives MBS data transmitted by multicast
- the UE 100 starts a data inactivity timer when transmitting and receiving data by normal unicast.
- the data inactivity timer is in operation and normal unicast data transmission/reception is not performed
- the UE 100 transitions to the RRC idle state upon expiration of the data inactivity timer. Since UE 100 needs to be in the RRC connected state in order to receive MBS data transmitted by multicast, UE 100 transitioning to the RRC idle state cannot receive MBS data transmitted by multicast.
- the UE 100 when receiving MBS data transmitted by multicast, the UE 100 restarts the data inactivity timer by transmitting restart information to the gNB 200 before the data inactivity timer expires.
- the current specification defines that the UE 100 restarts the data inactivity timer by transmitting signaling. Therefore, the UE 100 restarts the data inactivity timer according to the transmission of the restart information. Therefore, the UE 100 can continuously receive MBS data transmitted by multicast without transitioning to the RRC idle state in response to expiration of the data inactivity timer.
- FIG. 12 is a diagram showing an operation example of the fourth operation pattern according to one embodiment. In this operation example, it is assumed that the UE 100 is in the RRC connected state and the data inactivity timer is set from the gNB 200 to the UE 100.
- step S401 the UE 100 starts a data inactivity timer.
- the UE 100 starts a data inactivity timer in response to unicast transmission/reception of data (data that is not MBS data).
- the UE 100 may start a data inactivity timer according to transmission/reception of signaling.
- step S402 the gNB 200 transmits MBS data by multicast.
- the UE 100 receives MBS data transmitted by multicast.
- the UE 100 determines whether the remaining time before the data inactivity timer expires is equal to or less than a threshold.
- the threshold may be a value set by the UE 100 itself. Also, the threshold may be a value set in the UE 100 from the gNB 200.
- the UE 100 transmits restart information to the gNB 200 in step S404.
- UE 100 may transmit the restart information in an RRC message.
- the UE 100 may transmit with MAC CE.
- the restart information may be information for notifying the gNB 200 to reset the data inactivity timer and restart.
- the restart information may be a 1-bit flag indicating that the UE 100 continues to receive MBS data.
- gNB200 may transmit the response with respect to the said restart information to UE100 according to reception of restart information.
- step S405 the UE 100 resets and restarts the data inactivity timer in response to the transmission of the restart information.
- the UE 100 may periodically transmit restart information before the data inactivity timer expires.
- UE 100 may have a separate timer for transmitting restart information.
- the UE 100 starts and restarts the timer when transmitting the restart information, and transmits the restart information again when the timer expires.
- the UE 100 stops (or discards) the timer when it stops receiving MBS data (when it loses interest in receiving or when the MBS data transmission/MBS session ends).
- the value of the timer may be set from gNB200.
- the restart information may be transmitted from the gNB 200.
- the gNB 200 manages the data inactivity timer similarly to the UE 100 , and the gNB 200 starts/resumes the data inactivity timer according to unicast data transmission/reception with the UE 100 .
- the gNB 200 transmits the restart information to the UE 100 by unicast.
- UE 100 restarts the data inactivity timer managed by itself in response to receiving the restart information.
- the gNB 200 may reset and restart the data inactivity timer managed by itself in response to receiving the restart information from the UE 100 .
- Each of the operation patterns described above is not limited to being implemented independently, but can be implemented by combining two or more operation patterns. For example, some steps of one motion pattern may be added to another motion pattern. Also, some steps of one operation pattern may be replaced with some steps of another operation pattern.
- 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 that causes a computer to execute each process performed by the UE 100 or the gNB 200 may be provided.
- the program may be recorded on a computer readable medium.
- a computer readable medium allows the installation of the program on the computer.
- the computer-readable medium on which the program is recorded may be a non-transitory recording medium.
- the non-transitory recording medium is not particularly limited, but may be, for example, a recording medium such as CD-ROM or DVD-ROM.
- circuits that execute each process performed by the UE 100 or the gNB 200 may be integrated, and at least part of the UE 100 or the gNB 200 may be configured as a semiconductor integrated circuit (chipset, SoC: System on a chip).
- chipsset, SoC System on a chip
- the terms “based on” and “depending on,” unless expressly stated otherwise, “based only on.” does not mean The phrase “based on” means both “based only on” and “based at least in part on.” Similarly, the phrase “depending on” means both “only depending on” and “at least partially depending on.” Also, “obtain/acquire” may mean obtaining information among stored information, or it may mean obtaining information among information received from other nodes. or it may mean obtaining the information by generating the information.
- the terms “include,” “comprise,” and variations thereof are not meant to include only the recited items, and may include only the recited items or in addition to the recited items. Means that it may contain further items.
- references to elements using the "first,” “second,” etc. designations used in this disclosure do not generally limit the quantity or order of those elements. These designations may be used herein as a convenient method of distinguishing between two or more elements. Thus, references to first and second elements do not imply that only two elements may be employed therein, or that the first element must precede the second element in any way.
- references to first and second elements do not imply that only two elements may be employed therein, or that the first element must precede the second element in any way.
- NG-RAN 5G RAN
- 5GC 5G CN
- UE 110 Reception unit 120: Transmission unit 130: Control unit 200: gNB 210: Transmission unit 220: Reception unit 230: Control unit 240: Backhaul communication unit
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
まず、実施形態に係る移動通信システムの構成について説明する。図1は、一実施形態に係る移動通信システムの構成を示す図である。この移動通信システムは、3GPP規格の第5世代システム(5GS:5th Generation System)に準拠する。以下において、5GSを例に挙げて説明するが、移動通信システムにはLTE(Long Term Evolution)システムが少なくとも部分的に適用されてもよい。また、移動通信システムには第6世代(6G)システムが少なくとも部分的に適用されてもよい。
次に、一実施形態に係るMBSについて説明する。MBSは、NG-RAN10からUE100に対してブロードキャスト又はマルチキャスト、すなわち、1対多(PTM:Point To Multipoint)でのデータ送信を可能とするサービスである。MBSは、MBMS(Multimedia Broadcast and Multicast Service)と呼ばれてもよい。なお、MBSのユースケース(サービス種別)としては、公安通信、ミッションクリティカル通信、V2X(Vehicle to Everything)通信、IPv4又はIPv6マルチキャスト配信、IPTV(Internet Protocol TeleVision)、グループ通信、及びソフトウェア配信等がある。
次に、一実施形態に係るスプリットMBSベアラについて説明する。
次に、一実施形態に係るデータ不活性タイマ(data inactivity timer)によるRRC状態遷移について説明する。
次に、一実施形態に係る第1動作パターンについて説明する。
次に、一実施形態に係る第2動作パターンについて、上述の動作パターンとの相違点を主として説明する。
次に、一実施形態に係る第3動作パターンについて、上述の動作パターンとの相違点を主として説明する。
次に、一実施形態に係る第4動作パターンについて、上述の動作パターンとの相違点を主として説明する。
上述の各動作パターンでは、データ不活性タイマがUE100に設定された前提下において、MBSデータ受信に伴うタイマの取り扱いについて述べたが、gNB200は、マルチキャスト(PTM)でMBSデータを送信する場合、UE100にデータ不活性タイマを設定しないという動作が考えられる。この場合、RRC Reconfigurationメッセージにおいて、MBS設定(もしくはPTM設定)とデータ不活性タイマ設定は排他的に設定可能である。もしくは、MBS設定(もしくはPTM設定)が行われている場合、UE100はデータ不活性タイマが設定されていても、これを無視してもよい。つまり、データ不活性タイマが設定されていないと見なしてもよい。
20 :5GC(5G CN)
100 :UE
110 :受信部
120 :送信部
130 :制御部
200 :gNB
210 :送信部
220 :受信部
230 :制御部
240 :バックホール通信部
Claims (7)
- マルチキャスト・ブロードキャストサービス(MBS)を提供する移動通信システムにおけるユーザ装置が実行する通信制御方法であって、
RRC(Radio Resource Control)コネクティッド状態において、基地局からMBSデータを受信することと、
前記基地局とのデータ及びシグナリングの送受信が行われない時間を計時するタイマを管理することと、
前記タイマの満了に応じて、前記RRCコネクティッド状態からRRCアイドル状態に遷移することと、を有し、
前記タイマを管理することは、マルチキャスト又はブロードキャストで送信される前記MBSデータを受信する場合、当該MBSデータを受信しても前記タイマを開始しないように制御することを含む
通信制御方法。 - 前記タイマを管理することは、ユニキャストで送信される前記MBSデータを受信する場合、当該MBSデータの受信に応じて前記タイマを開始又は再開することをさらに含む
請求項1に記載の通信制御方法。 - 前記タイマを管理することは、ユニキャストで送信される前記MBSデータを受信する場合であっても、当該MBSデータを受信しても前記タイマを開始しないように制御することをさらに含む
請求項2に記載の通信制御方法。 - 前記タイマを開始しないように制御することは、前記基地局から、前記MBSデータの受信に対して前記タイマを開始しないように設定されている場合、前記タイマを開始しないように制御することを含む
請求項1乃至3のいずれか1項に記載の通信制御方法。 - マルチキャスト・ブロードキャストサービス(MBS)を提供する移動通信システムにおけるユーザ装置が実行する通信制御方法であって、
基地局とのデータの送信及び受信が行われない時間を計時するタイマを管理することと、
前記タイマの満了に応じて、RRCコネクティッド状態からRRCアイドル状態に遷移することと、を有し、
前記タイマを管理することは、マルチキャストで送信されるMBSデータを前記基地局から受信する場合、前記タイマが満了する前に、再開情報を送信又は受信することにより前記タイマを再開することを含む
通信制御方法。 - 前記タイマを再開することは、前記タイマが満了するまでの残り時間が閾値以下である場合、前記再開情報を送信することを含む
請求項5に記載の通信制御方法。 - 請求項1又は5に記載の通信制御方法を実行するプロセッサを備える
ユーザ装置。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2023518696A JPWO2022234847A5 (ja) | 2022-05-02 | 通信制御方法、ユーザ装置、及びプロセッサ | |
EP22798951.4A EP4322559A1 (en) | 2021-05-07 | 2022-05-02 | Communication control method and user equipment |
CN202280047339.XA CN117598018A (zh) | 2021-05-07 | 2022-05-02 | 通信控制方法和用户设备 |
US18/503,004 US20240080935A1 (en) | 2021-05-07 | 2023-11-06 | Communication control method and user equipment |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021-079265 | 2021-05-07 | ||
JP2021079265 | 2021-05-07 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/503,004 Continuation US20240080935A1 (en) | 2021-05-07 | 2023-11-06 | Communication control method and user equipment |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022234847A1 true WO2022234847A1 (ja) | 2022-11-10 |
Family
ID=83932737
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2022/019529 WO2022234847A1 (ja) | 2021-05-07 | 2022-05-02 | 通信制御方法及びユーザ装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20240080935A1 (ja) |
EP (1) | EP4322559A1 (ja) |
CN (1) | CN117598018A (ja) |
WO (1) | WO2022234847A1 (ja) |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2021079265A (ja) | 2021-03-05 | 2021-05-27 | 株式会社三洋物産 | 遊技機 |
-
2022
- 2022-05-02 WO PCT/JP2022/019529 patent/WO2022234847A1/ja active Application Filing
- 2022-05-02 CN CN202280047339.XA patent/CN117598018A/zh active Pending
- 2022-05-02 EP EP22798951.4A patent/EP4322559A1/en active Pending
-
2023
- 2023-11-06 US US18/503,004 patent/US20240080935A1/en active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2021079265A (ja) | 2021-03-05 | 2021-05-27 | 株式会社三洋物産 | 遊技機 |
Non-Patent Citations (6)
Title |
---|
3GPP TS 38.300, September 2020 (2020-09-01) |
3GPP TS 38.321 |
3GPP TS 38.331 |
ASUSTEK: "UE stay in RRC_CONNECTED when no MBS data ongoing", 3GPP DRAFT; R2-2103450, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20210412 - 20210420, 1 April 2021 (2021-04-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051992080 * |
ERICSSON: "Aspects of Group Scheduling", 3GPP DRAFT; R2-2103517, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20210412, 1 April 2021 (2021-04-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051992123 * |
HUAWEI, HISILICON (RAPPORTEUR): "Email discussion report on [105#49][NR] LBT impacts in MAC", 3GPP DRAFT; R2-1904114 REPORT OF THE EMAIL DISCUSSION [105#49] LBT MODELING FOR MAC, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Xi’an, China; 20190408 - 20190412, 29 March 2019 (2019-03-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051693345 * |
Also Published As
Publication number | Publication date |
---|---|
EP4322559A1 (en) | 2024-02-14 |
US20240080935A1 (en) | 2024-03-07 |
JPWO2022234847A1 (ja) | 2022-11-10 |
CN117598018A (zh) | 2024-02-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022085757A1 (ja) | 通信制御方法 | |
WO2022085717A1 (ja) | 通信制御方法 | |
US20240080939A1 (en) | Communication control method and user equipment | |
WO2022153991A1 (ja) | 通信制御方法 | |
WO2022030452A1 (ja) | 通信制御方法、基地局、及びユーザ装置 | |
WO2022025013A1 (ja) | 通信制御方法 | |
WO2023140144A1 (ja) | 通信方法及びユーザ装置 | |
WO2022138450A1 (ja) | 通信制御方法及びユーザ装置 | |
WO2022234847A1 (ja) | 通信制御方法及びユーザ装置 | |
JP7508576B2 (ja) | 通信制御方法 | |
WO2022085646A1 (ja) | 通信制御方法 | |
WO2022030518A1 (ja) | 通信制御方法 | |
WO2022239773A1 (ja) | 通信制御方法 | |
US20240080940A1 (en) | Communication control method | |
JP7425259B2 (ja) | 通信制御方法及び基地局 | |
WO2022239774A1 (ja) | 通信制御方法、基地局、及びユーザ装置 | |
JP7502574B2 (ja) | 通信方法、ユーザ装置、プロセッサ、プログラム、及び移動通信システム | |
WO2022153990A1 (ja) | 通信制御方法及びユーザ装置 | |
WO2023013607A1 (ja) | 通信方法 | |
WO2023002988A1 (ja) | 通信方法 | |
WO2023074721A1 (ja) | 通信方法及びユーザ装置 | |
WO2024071158A1 (ja) | 通信方法、基地局、及びユーザ装置 | |
US20240237143A1 (en) | Communication method | |
WO2022085573A1 (ja) | 通信制御方法 | |
WO2023013608A1 (ja) | 通信方法 |
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: 22798951 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023518696 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022798951 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2022798951 Country of ref document: EP Effective date: 20231106 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202280047339.X Country of ref document: CN |