WO2022149489A1 - 通信制御方法及びユーザ装置 - Google Patents
通信制御方法及びユーザ装置 Download PDFInfo
- Publication number
- WO2022149489A1 WO2022149489A1 PCT/JP2021/048137 JP2021048137W WO2022149489A1 WO 2022149489 A1 WO2022149489 A1 WO 2022149489A1 JP 2021048137 W JP2021048137 W JP 2021048137W WO 2022149489 A1 WO2022149489 A1 WO 2022149489A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- rrc
- mbs
- state
- setting
- message
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000004891 communication Methods 0.000 title claims abstract description 39
- 238000010295 mobile communication Methods 0.000 claims abstract description 15
- 230000007704 transition Effects 0.000 claims description 17
- 230000008569 process Effects 0.000 claims description 8
- 238000009826 distribution Methods 0.000 description 48
- 230000004048 modification Effects 0.000 description 37
- 238000012986 modification Methods 0.000 description 37
- 230000005540 biological transmission Effects 0.000 description 30
- 101150014328 RAN2 gene Proteins 0.000 description 22
- 238000010586 diagram Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 9
- 230000008859 change Effects 0.000 description 7
- 230000011664 signaling Effects 0.000 description 7
- 101100533725 Mus musculus Smr3a gene Proteins 0.000 description 5
- 230000004044 response Effects 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
- 238000005259 measurement Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000000717 retained effect Effects 0.000 description 3
- 101100274486 Mus musculus Cited2 gene Proteins 0.000 description 2
- 101150096622 Smr2 gene Proteins 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 238000002716 delivery method Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000001052 transient effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000004481 post-translational protein modification Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- 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
-
- 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/40—Connection management for selective distribution or broadcast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
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 method executed by a user device in a mobile communication system that provides a multicast / broadcast service (MBS).
- the communication control method is that the user device in the RRC (Radio Resource Control) connected state receives an RRC message including the MBS setting required for MBS reception from the base station, and the RRC idle from the RRC connected state.
- the user apparatus that has transitioned to the state or the RRC inactive state has the MBS reception using the MBS setting received during the RRC connected state.
- the RRC message is an RRC Reconnection message or an RRC Release message.
- the user device is a device used in a mobile communication system that provides a multicast / broadcast service (MBS).
- the user device is a receiving unit that receives an RRC message including an MBS setting required for MBS reception from a base station when the user device is in the RRC (Radio Resource Control) connected state, and from the RRC connected state. It has a control unit that performs the MBS reception using the MBS setting received in the RRC connected state after transitioning to the RRC idle state or the RRC inactive state.
- the RRC message is an RRC Reconnection message or an RRC Release message.
- NR 5G systems
- 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 3GPP standard 5th generation system (5GS: 5th Generation System).
- 5GS 5th Generation System
- 5GS will be described as an example, but an LTE (Long Term Evolution) system and / or a 6th generation (6G) system may be applied to a mobile communication system at least partially.
- LTE Long Term Evolution
- 6G 6th generation
- 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 is a mobile phone terminal (including a smartphone), a tablet terminal, a notebook PC, a communication module (including a communication card or a chipset), a sensor or a device provided in the sensor, a vehicle or a device provided in the vehicle (Vehicle UE). ) And / or a flying object or a device (Arial UE) provided on the flying object.
- the NG-RAN 10 includes a base station (called “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”), and / or a measurement control function for mobility control / scheduling.
- 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 ARP (Hybrid Automatic Repeat request), 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 for which a core network performs QoS (Quality of Service) control, with a wireless bearer, which is a unit for which AS (Access Stratum) controls QoS.
- QoS Quality of Service
- 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 from NG-RAN10 to UE100, that is, one-to-many (PTM: Point To Multipoint) data transmission.
- MBS use cases (service types) are assumed to be public safety communication, mission-critical communication, V2X (Vehicle to Everything) communication, IPv4 or IPv6 multicast distribution, IPTV, group communication, software distribution, and the like.
- the broadcast service provides services to all UEs 100 in a particular service area for applications that do not require highly reliable QoS.
- the multicast service provides services to a group of UEs 100 participating in the multicast service, not to all UEs 100.
- the multicast service can provide the same content to a group of UEs 100 in a more wirelessly efficient manner than a broadcast service.
- FIG. 6 is a diagram showing an outline of MBS traffic distribution according to one embodiment.
- MBS traffic is delivered 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 traffic from an application service provider, replicates the MBS traffic, and distributes it.
- 5GC shared MBS traffic distribution (5GC Shared MBS Traffic delivery)
- 5GC individual MBS traffic distribution (5GC Individual MBS Traffic delivery).
- the 5GC20 receives a single copy of the MBS data packets and distributes individual copies of those MBS data packets to the individual UE 100 via a PDU (Protocol Data Unit) session for each UE 100. do. Therefore, it is necessary to associate one PDU session with the multicast session for each UE 100.
- PDU Protocol Data Unit
- the 5GC20 receives a single copy of the MBS data packet and delivers the single copy of those MBS packet packets to the RAN node (that is, gNB200).
- the gNB 200 delivers them to one or more UEs 100.
- PTP Point-to-Point
- PTM Point-to-Multipoint
- the gNB 200 wirelessly distributes individual copies of MBS data packets to individual UEs 100.
- the gNB 200 wirelessly distributes a single copy of the MBS data packet to the group of UE 100.
- the gNB 200 dynamically determines whether to use PTM or PTP as a method of delivering MBS traffic to one UE 100.
- the PTP distribution method and the PTM distribution method are mainly related to the user plane.
- As the control mode of MBS traffic distribution there are two distribution modes, distribution mode 1 and distribution mode 2.
- FIG. 7 is a diagram showing a distribution mode according to an embodiment.
- the distribution mode 1 (Delivery mode 1) is a distribution mode that can be used by the UE 100 in the RRC connected state, and is a distribution mode for high QoS requirements. Delivery mode 1 is used only for multicast sessions among MBS sessions. In one embodiment, it is assumed that the distribution mode 1 is used for the multicast session, but the distribution mode 1 may be used for the broadcast session. In the distribution mode 1, the UE 100 in the RRC idle state or the RRC inactive state may also be available.
- the MBS reception setting in the distribution mode 1 is performed by the RRC Reconnection message (or RRC Release message) which is an RRC message transmitted by unicast from the gNB 200 to the UE 100.
- the MBS receive configuration includes scheduling information for the MBS traffic channel carrying the MBS traffic.
- the MBS traffic channel which is a kind of logical channel, may be called MTCH (Multicast Traffic Channel).
- the MBS traffic channel is mapped to DL-SCH (Downlink Shared Channel), which is a kind of transport channel.
- Delivery mode 2 is a delivery mode that can be used not only by the UE 100 in the RRC connected state but also by the UE 100 in the RRC idle state or the RRC inactive state, and is a delivery mode for low QoS requirements.
- the distribution mode 2 is used for the broadcast session among the MBS sessions. However, the distribution mode 2 may also be applicable to a multicast session.
- the setting of MBS reception in the distribution mode 2 is performed by a logical channel broadcast from the gNB 200 to the UE 100, for example, BCCH (Broadcast Control Channel) or MCCH (Multicast Control Channel).
- BCCH Broadcast Control Channel
- MCCH Multicast Control Channel
- 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. 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.
- split MBS bearer Next, the split MBS bearer according to the embodiment will be described.
- the split MBS bearer is available in delivery mode 1 described above.
- 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 traffic to the UE 100 between the PTP (PTP communication path) and the PTM (PTM communication path).
- the gNB 200 can be used in combination with PTP and PTM to double-transmit the same MBS traffic to improve reliability.
- the gNB 200 can improve reliability by first sending MBS traffic to a plurality of UEs 100 by PTM and retransmitting MBS traffic to a specific UE 100.
- 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.
- the gNB 200 cannot perform PTM transmission of MBS traffic using this PTM leg when the PTM leg is in the deactivation state even if the split MBS bearer is set in the UE 100.
- the gNB 200 and the UE 100 perform PTP transmission (unicast) of MBS traffic using the PTP leg.
- 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, the gNB 200 cannot perform PTP transmission of MBS traffic using this PTP leg when the PTP leg is in the inactive state even if the split MBS bearer is set in the UE 100.
- 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 traffic 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 a configuration example of an RRC Reconnection message used for setting MBS reception in the distribution mode 1.
- the RRC Reconnection message transmitted from the gNB 200 to the UE 100 includes the MBS setting required for MBS reception as an information element.
- the MBS settings include the basic reception settings, which are the basic settings for MBS reception, and the RRC connected dedicated settings, which are applicable only to MBS reception in the RRC connected state.
- the basic reception setting is a setting common to all RRC states (that is, RRC connected state, RRC idle state, RRC inactive state).
- the basic reception settings include MTCH scheduling information.
- the MTCH scheduling information includes at least one of a group RNTI, an MBS session identifier, a transmission occasion, and a transmission BWP (Bandwidth Part).
- the group RNTI is an RNTI commonly assigned to the group of UE100.
- the transmission occasion is a candidate for the timing (for example, subframe) at which the gNB 200 transmits MBS traffic using the MTCH.
- the transmission BWP is a BWP in which the gNB 200 transmits MBS traffic using the MTCH.
- the BWP is a bandwidth portion narrower than the frequency bandwidth of one cell, and is for limiting the operating bandwidth of the UE 100.
- the RRC connected dedicated setting is a setting related to the split MBS bearer, and includes, for example, at least one of the bearer setting of the split MBS bearer, the dynamic switching setting between PTP and PTM, and the PTP leg setting. Since the PTM leg setting can be used even in the RRC idle state or the RRC inactive state, it may be included in the basic reception setting.
- the RRC connected-only settings may include HARQ feedback settings.
- the gNB 200 transitions the UE 100 to an RRC idle state or an RRC inactive state.
- the gNB 200 may be in a situation where the UE 100 cannot be maintained in the RRC connected state due to congestion.
- the UE 100 can continue MBS reception even when it transitions to the RRC idle state or the RRC inactive state.
- the UE 100 continues to apply the MBS settings provided by the RRC Configuration message as the MBS settings used in the RRC idle state or the RRC inactive state. That is, the UE 100 reuses the MBS settings provided during the RRC connected state.
- the UE 100 when the UE 100 according to one embodiment is in the RRC connected state, it receives an RRC Configuration message (RRC message) including MBS settings required for MBS reception from the base station. After transitioning from the RRC connected state to the RRC idle state or the RRC inactive state, the UE 100 performs MBS reception using the MBS setting received in the RRC connected state.
- RRC message RRC Configuration message
- the UE 100 performs a process of invalidating the RRC connected dedicated setting included in the MBS setting received in the RRC connected state when transitioning to the RRC idle state or the RRC inactive state. As a result, the storage capacity of the UE 100 can be saved, and the occurrence of unexpected errors can be suppressed.
- FIG. 10 is a diagram showing an operation according to one embodiment.
- step S101 the UE 100 is in the RRC connected state in the cell of the gNB 200.
- step S102 the gNB 200 transmits an RRC Connection message including an MBS setting, that is, a basic reception setting and an RRC connected dedicated setting, to the UE 100.
- the UE 100 receives the RRC Reconnection message.
- step S103 the UE 100 stores and applies the MBS settings included in the received RRC Configuration message.
- step S104 the UE 100 receives the MBS traffic from the gNB 200 using the MBS setting applied in step S103, that is, the basic reception setting and the RRC connected dedicated setting.
- the UE 100 receives the MBS setting in the RRC Configuration message and receives the MBS traffic.
- step S105 the gNB 200 identifies the UE 100 to be transitioned to the RRC idle state or the RRC inactive state.
- the gNB 200 may specify the UE 100 receiving the target MBS session as the UE 100 that transitions to the RRC idle state or the RRC inactive state. For example, when the MBS traffic transmission in step S104 is performed by multicast, the gNB 200 requests the 5GC 20 to provide information and identifies the UE 100 receiving the target MBS session. On the other hand, when the MBS traffic transmission in step S104 is performed by broadcasting, the gNB 200 receives information from the UE 100 in advance by the MBS interest indication message (MII). Thereby, the gNB 200 identifies the UE 100 receiving the target MBS session.
- MII MBS interest indication message
- the gNB 200 may specify the non-moving UE 100 as the UE 100 that transitions to the RRC idle state or the RRC inactive state.
- the moving UE 100 it is desirable that the moving UE 100 be maintained in the RRC connected state because the gNB 200 may need to perform handover control in order to guarantee the continuity of the MBS service.
- the gNB 200 shifts the non-moving UE 100 to the RRC idle state or the RRC inactive state. Thereby, the load of gNB200 can be reduced.
- the gNB 200 can reduce the load on the gNB 200 by shifting the non-moving UE 100 to the RRC idle state or the RRC inactive state.
- the gNB 200 may be specified as a UE 100 that does not move the UE 100 whose stay time in the own cell exceeds a predetermined time. Further, the gNB 200 may specify the UE 100 that does not move based on the position information periodically received from the UE 100. Alternatively, the gNB 200 may specify the UE 100 that does not move by being notified of the movement state by the UE 100. The notification may be notified by a request from gNB200. The notification may be notified by the UE 100 itself (for example, when the moving state changes). The movement state may be notified using the MBS Interest Indication (MII). The movement state may be notified in association with interest information for MBS reception.
- MII MBS Interest Indication
- step S106 the gNB 200 transmits an RRC Release message to the UE 100 specified in step S105.
- the UE 100 receives the RRC Release message.
- the gNB 200 transmits an RRC Release message including a suspend context as an information element to the UE 100.
- step S107 the UE 100 transitions to the RRC idle state or the RRC inactive state based on the received RRC Release message.
- step S108 the UE 100 continues to apply the basic reception setting and performs a process of invalidating the RRC connected dedicated setting.
- the process of invalidating is discarding the RRC connected dedicated setting (discard), suspending the application of the RRC connected dedicated setting (suspend), or deactivating the RRC connected dedicated setting (deactivate).
- the RRC connected dedicated setting In the case of suspend or deactive, the RRC connected dedicated setting is retained without being discarded. The retained RRC connected-only settings can be restored (enabled) when the UE 100 returns to the RRC connected state again.
- the operation of the UE 100 transitioning from the RRC inactive state to the RRC connected state is called resume (RRC resume).
- the UE 100 does not have to enable the held RRC connected dedicated setting at the time of RRC resume.
- the UE 100 enables the RRC connected dedicated setting when the cell when transitioning to the RRC idle state or the RRC inactive state and the cell when returning to the RRC connected state are the same, and these are different cells. In this case, the RRC connected-only setting may not be enabled (details will be described in the modification described later).
- the UE 100 may release the entity used only in the RRC connected state, for example, the RLC entity of the PTP leg.
- the UE 100 may reconfigure the associated entity, for example, suspend the split (or join) function of the PDCP entity.
- step S109 the UE 100 continues to receive MBS traffic in the RRC idle state or the RRC inactive state by using the basic reception setting.
- the UE 100 retains the RRC connected dedicated setting when transitioning from the RRC connected state to the RRC inactive state.
- the UE 100 can quickly set the split MBS bearer and the like by effectively utilizing the held settings.
- the gNB 200 when the UE 100 transitions to the RRC inactive state and the gNB 200 when returning to the RRC connected state may be the same, or these gNB 200s may be different.
- the UE 100 that has transitioned to the RRC inactive state retains the RRC connected dedicated setting in the RRC inactive state.
- the UE 100 transmits a notification to the gNB 200 indicating that the RRC connected dedicated setting is held during the resume operation of transitioning from the RRC inactive state to the RRC connected state.
- the gNB 200 instructs the UE 100 whether or not to enable the RRC connected dedicated setting held by the UE 100.
- FIG. 11 is a diagram showing an operation according to the first modification of the embodiment.
- the gNB 200a when the UE 100 transitions to the RRC inactive state and the gNB 200b when the UE 100 returns to the RRC connected state are different will be described.
- steps S201 to S208 is the same as that of the above-described embodiment.
- the UE 100 invalidates and retains the RRC connected dedicated setting when transitioning to the RRC inactive state.
- step S109 the UE 100 continues to receive MBS traffic in the RRC inactive state using the basic reception setting.
- step S210 the UE 100 in the RRC inactive state performs cell reselection from the cell of gNB200a to the cell of gNB200b.
- the UE 100 When the UE 100 decides to resume the RRC connection, it starts a random access procedure with the gNB 200b in step S211.
- a general random access procedure for RRC resumes includes the following 1) -5). 1) Transmission of random access preamble (Msg1) from UE100 to gNB200b 2) Transmission of random access response (Msg2) from gNB200b to UE100 3) Transmission of RRC Procedure Request message (Msg3) from UE100 to gNB200b 4) Transmission of RRC Procedure Request message (Msg3) from gNB200b Transmission of RRC Resume message (Msg4) to UE100 5) Transmission of RRC Resume Complete message (Msg5) from UE100 to gNB200b
- Msg1 and Msg3 are integrated into one message (MsgA).
- Msg2 and Msg4 are integrated into one message (MsgB).
- the UE 100 transmits Msg1 or MsgA using a special PRACH (Physical Random Access Channel) resource. As a result, the UE 100 notifies the gNB 200b that it holds the RRC connected dedicated setting (step S211a).
- the UE 100 transmits Msg3, MsgA, or Msg5 that includes an information element indicating that it holds the RRC connected dedicated setting. As a result, the UE 100 notifies the gNB 200b that it holds the RRC connected dedicated setting (step S211a).
- the gNB 200b Upon receiving the retention notification from the UE 100, the gNB 200b determines whether or not to enable the RRC connected dedicated setting held by the UE 100, and transmits an instruction indicating the determination result to the UE 100 (step S212). For example, the gNB 200b may decide to enable the RRC connected dedicated setting held by the UE 100 only when the context information of the UE 100 can be acquired from the gNB 200a.
- the UE 100 When the UE 100 receives an instruction from gNB200b to enable the RRC connected dedicated setting, the UE 100 activates the held RRC connected dedicated setting. On the other hand, if the UE 100 does not receive an instruction from the gNB 200b to enable the RRC connected dedicated setting, the UE 100 does not enable the held RRC connected dedicated setting. In this case, the UE 100 may discard the held RRC connected dedicated setting.
- the second modification of the above-described embodiment will be mainly described as being different from the above-described embodiment.
- the UE 100 retains the RRC connected dedicated setting when transitioning from the RRC connected state to the RRC idle state or the RRC inactive state.
- the multicast session (delivery mode 1) is basically a network-controlled delivery mode in which the UE 100 is maintained in the RRC connected state. However, the UE 100 is transitioned to the RRC idle state or the RRC inactive state due to temporary network congestion or the like.
- the split MBS bearer in the RRC connected dedicated setting is often set to the UE 100 at the cell end.
- the gNB 200 may transmit MBS traffic using the PTP leg.
- the gNB 200 may transmit MBS traffic using the PTP leg in order to eliminate packet loss during the handover.
- the UE 100 that transitions to the RRC idle state or the RRC inactive state and holds the RRC connected dedicated setting notifies the gNB 200 before reselecting the cell to another cell at the cell end. ..
- the gNB 200 (network) can perform mobility control for the UE 100 based on the notification.
- the UE 100 when it is determined that the predetermined condition (trigger condition) for cell reselection is satisfied in the RRC idle state or the RRC inactive state, the UE 100 starts a random access procedure for the gNB 200. The UE 100 sends a notification to the gNB 200 indicating that a predetermined condition is satisfied in the random access procedure.
- the predetermined condition Trigger condition
- FIG. 12 is a diagram showing an operation according to the second modification of the embodiment.
- the UE 100 transitions to the RRC inactive state, but it may be assumed that the UE 100 transitions to the RRC idle state. That is, the RRC inactive state in FIG. 12 may be read as the RRC idle state.
- steps S301 to S308 are the same as that of the above-described embodiment.
- the UE 100 invalidates and retains the RRC connected dedicated setting when transitioning to the RRC inactive state (or RRC idle state).
- the UE 100 continues to receive MBS traffic in the RRC inactive state (or RRC idle state) using the basic reception setting.
- the UE 100 detects a trigger related to cell reselection from the cell of gNB200 to another cell.
- the trigger condition for cell reselection may be a condition that actually triggers cell reselection, or may be a condition that indicates a sign that triggers cell reselection.
- the trigger condition may include a threshold value set from the gNB 200 to the UE 100 (for example, RSRP / RSRQ threshold value) and information (event information) for designating the comparison target.
- the UE 100 When the UE 100 detects a trigger related to cell reselection, it starts a random access procedure with gNB200 in step S311.
- the UE 100 sends a notification to the gNB 200 indicating that the trigger condition for cell reselection has been satisfied.
- the same method as in the first modification of the above-described embodiment can be used. That is, the UE 100 notifies the gNB 200 that the trigger condition for cell reselection is satisfied by transmitting Msg1 or MsgA using a special PRACH resource (step S311a).
- the UE 100 notifies the gNB 200 that the trigger condition for cell reselection is satisfied by transmitting Msg3, MsgA, or Msg5 including an information element indicating that the trigger condition for cell reselection is satisfied. (Step S311a).
- the UE 100 may transmit a measurement report including a radio measurement result indicating its own radio status to the gNB 200 for use in the mobility control in step S312.
- the gNB 200 performs mobility control (handover control or cell reselection control) for the UE 100 based on the notification received from the UE 100 in step S311a. For example, the gNB 200 shifts the UE 100 to the RRC connected state and then performs a handover to another cell. Alternatively, the gNB 200 causes the UE 100 to perform cell reselection to another cell after keeping the UE 100 in the RRC idle state or the RRC inactive state. In this case, the gNB 200 may instruct the UE 100 to discard the RRC connected dedicated setting.
- mobility control handover control or cell reselection control
- the UE 100 having the RRC connected dedicated setting in the RRC connected state is prohibited from transitioning to the RRC idle state or the RRC inactive state.
- the gNB 200 releases (discards) the RRC connected dedicated setting to the UE 100 before transitioning the UE 100 to the RRC idle state or the RRC inactive state, and then releases (discards) the RRC idle state or the RRC inactive state.
- the UE 100 is transitioned to the state. Then, the UE 100 transitions to the RRC idle state or the RRC inactive state after the RRC connected dedicated setting is released by the gNB 200.
- FIG. 13 is a diagram showing an operation according to the third modification of the embodiment.
- the operation of steps S401 to S405 is the same as that of the above-described embodiment.
- the gNB 200 may specify the UE 100 capable of transitioning to the RRC idle state or the RRC inactive state. For example, the gNB 200 identifies a UE 100 that is unlikely to transmit an uplink for a certain period of time or a UE 100 that has no unicast communication.
- the gNB 200 may specify the UE 100 that has transmitted a message prompting the release of the RRC connection, for example, a RAI (Releasation Assistance Information) message.
- a RAI Releasation Assistance Information
- step S406 the gNB 200 transmits an RRC Reconnection message including an information element indicating that the RRC connected dedicated setting is released to the specified UE 100.
- step S407 the UE 100 releases (discards) the RRC connected dedicated setting in response to the reception of the RRC Reconnection message in step S406.
- the UE 100 is in a state of having only the MBS setting (basic reception setting) of the PTM among the MBS settings.
- step S408 the gNB 200 sends an RRC Release message to the UE 100 that has released the RRC connected dedicated setting.
- the UE 100 receives the RRC Release message.
- step S409 the UE 100 transitions to the RRC idle state or the RRC inactive state based on the received RRC Release message.
- step S410 the UE 100 continues to apply the basic reception setting.
- step S411 the UE 100 continues to receive MBS traffic in the RRC idle state or the RRC inactive state by using the basic reception setting.
- the MBS setting is performed by the RRC Resolution message
- a scenario in which the MBS setting is performed by the RRC Release message may be assumed.
- the MBS setting is performed by the RRC Release message
- the gNB 200 may be prohibited from setting the RRC connected only by the RRC Release message.
- the information element related to the RRC connected dedicated setting may be a condition setting that cannot be used in the RRC Release message.
- MBS settings shall be standardized in the area range consisting of multiple cells.
- the UE 100 that has transitioned to the RRC idle state or the RRC inactive state can continue to receive MBS traffic within the area without updating the MBS setting.
- the area range may be defined as an area that does not require notification according to the first modification and the second modification of the above-described embodiment.
- the UE 100 receives an RRC message (RRC Reconnection message or RRC Release message) including area information indicating an area range for which the MBS setting is valid from the gNB 200.
- RRC message RRC Reconnection message or RRC Release message
- the UE 100 that has transitioned to the RRC idle state or the RRC inactive state performs MBS reception using the MBS setting within the area range indicated by the area information.
- FIG. 14 is a diagram showing an operation according to the fourth modification of the embodiment.
- the operation of steps S501 to S507 is the same as that of the above-described embodiment.
- the gNB 200 sets the area range in which the MBS setting is valid in the UE 100 by transmitting the area information to the UE 100 together with the MBS setting.
- the area information may be a list consisting of identifiers (cell identifiers) of each cell constituting the area range. Since each cell notifies the identifier of its own cell, the UE 100 can determine whether or not it is within the area range by using the set list.
- the area information may be an identifier indicating an area range (area identifier). Since each cell notifies the area identifier of the area range to which the cell belongs, the UE 100 can determine whether or not it is within the area range by using the set area identifier.
- step S507 the UE 100 transitions to the RRC idle state or the RRC inactive state based on the RRC Release message received in step S506.
- the UE 100 continues to receive MBS traffic using the basic reception setting among the MBS settings set from the gNB 200.
- the UE 100 considers that the MBS setting is valid within the area range set from the gNB 200, and does not notify the network even when the cell is reselected.
- the UE 100 When the UE 100 moves to a cell outside the area range, the UE 100 receives a new MBS setting from this cell by performing random access to the cell outside the area range. Alternatively, when the UE 100 detects a cell outside the area range, it may receive a new MBS setting from this cell by randomly accessing the current cell before moving out of the area range. good.
- the gNB 200 notifies the UE 100 by an RRC Release message whether or not the MBS setting (specifically, the basic reception setting) by the RRC Reconnection message can be used even in the RRC idle state or the RRC inactive state. do. That is, the UE 100 receives an RRC Release message from the gNB 200 including information indicating whether or not the MBS setting received in the RRC connected state can be used in the RRC idle state or the RRC inactive state.
- FIG. 15 is a diagram showing an operation according to the fifth modification of the embodiment.
- step S606 the gNB 200 transmits an RRC Release message including any of the following information A) and B) to the UE 100.
- the information indicating the expiration date may be represented by at least one of SFN (System Frame Number), H-SFN (Hyper SFN), and a subframe.
- the information indicating the expiration date may be a timer value indicating the time length of the expiration date.
- the UE 100 sets the MBS setting in the RRC Reconnection message in step S602 only when the RRC Release message including the information indicating that continuous use is permitted is received from the gNB 200 (step S606). Continue to use in RRC idle state or RRC inactive state.
- the UE 100 continuously uses the MBS setting in the RRC Reconnection message in step S602 in the RRC idle state or the RRC inactive state only within the expiration date set in the RRC Release message.
- the UE 100 activates a timer (timer corresponding to the timer value) when transitioning to the RRC idle state or the RRC inactive state (step S607), and this timer is set. Continue to use MBS settings until expiration.
- the UE 100 who is still interested in receiving the MBS may receive a new MBS setting from the gNB 200 by performing random access to the gNB 200. ..
- the UE 100 may notify the gNB 200 that the access is for updating the MBS settings.
- the notification may be presented in Msg1 / MsgA with a special PRACH resource or in Msg3.
- the UE 100 may try to acquire the MBS setting by the distribution mode 2.
- the UE 100 who is no longer interested in receiving MBS may discard the MBS setting set in the RRC Reconnection message.
- the UE 100 receives an RRC Release message including adjacent cell information.
- the adjacent cell information includes an identifier of the adjacent cell and an identifier indicating an MBS service (MBS session) provided by the adjacent cell.
- MBS session MBS service
- the UE 100 can preferentially select a cell that provides an MBS service of interest when performing cell reselection in the RRC idle state or the RRC inactive state.
- the UE 100 that has transitioned to the RRC idle state or the RRC inactive state controls cell reselection based on the received adjacent cell information.
- FIG. 16 is a diagram showing an operation according to the sixth modification of the embodiment.
- step S706 the gNB 200 transmits an RRC Release message including the adjacent cell information to the UE 100.
- the gNB 200 may send an RRC Release message including adjacent cell information and MBS settings (specifically, basic reception settings) to the UE 100.
- This adjacent cell information includes an identifier of an adjacent cell (cell identifier) and a list of identifiers (session identifiers) indicating MBS services provided by the adjacent cell.
- the UE 100 regards the cell for which the MBS setting of interest is provided as the highest priority in the cell reselection, and performs the cell reselection.
- 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).
- MBS Multicast Broadcast Service
- R2 defines the following two modes. 1: Delivery mode for high quality of service (QoS) requirements available in connected (in the absence of data reception, the UE may be able to switch to another state, but undecided). 2: Delivery mode for "low" QoS requirements. The UE can receive data even if it is inactive / idle (details undecided). R2 assumes that delivery mode 1 (in the case of R17) is used only for multicast sessions. R2 assumes that delivery mode 2 is used for the broadcast session. -The applicability of the distribution mode 2 to the multicast session needs further study. • No data: The UE may remain RRC connected if there is no data in progress in the multicast session. In other cases, further consideration is needed.
- QoS quality of service
- the UE receives the MBS setting (in the case of broadcast / delivery mode 2) by BCCH and / or MCCH (undecided), which can be received in idle / inactive mode. Connected mode needs further consideration.
- the notification mechanism is used to notify changes in MBS control information.
- control plane of NR MBS will be considered in consideration of the LTE eMBMS mechanism and the latest RAN2 agreement.
- Delivery mode 1 is considered primarily for data reception in the RRC connected, but configuration aspects have not yet been agreed. It can be very straightforward that the MBS configuration is provided by RRC reconfiguration, but it is still under consideration that the MCCH will be received in a connected manner like LTE eMBMS. Delivery mode 1 should be accompanied by, for example, PTP / PTM split bearers and / or lossless handovers, given the expectations for high QoS services. RRC reconfiguration should be used to configure delivery mode 1 in our view, as it makes no sense if these UE-specific configurations are provided via the MCCH.
- Proposal 1 In delivery mode 1, RAN2 should agree to use RRC reconfiguration for MBS configuration.
- WID clearly shows that RRC connected and idle / inactive should have the greatest commonality with respect to MBS configuration, as follows, while RAN2 for multicast and broadcast sessions respectively. And agreed to different delivery modes.
- the RRC resetting of the distribution mode 1 includes information unique to the distribution mode 1 such as the PTP / PTM split bearer and the handover-related information, in addition to the MTCH scheduling information which is a block common to the distribution mode 2. Therefore, the details need to be further examined at this point.
- Proposal 2 RAN2 should agree to aim for maximum commonality between the two delivery modes, eg, using a common structure and IE, from the perspective of MBS configuration.
- MCCH in FIG. 17 refers only to MTCH scheduling information, that is, MTCH settings related to MBS session information. In the case of distribution mode 1, adjacent cell information is not required.
- the baseline is that the UE should be kept RRC connected for delivery mode 1, i.e., a multicast session that requires high QoS.
- RRC connected for delivery mode 1 i.e., a multicast session that requires high QoS.
- other / exceptional cases are still worth considering.
- RAN2 From the perspective of RAN2, it may be beneficial for both the network and the UE to support this feature. It is assumed that when / when the UE is released inactive depends on the implementation of gNB, and whether the UE is released idle depends on the core network. One concern about receiving MBS data at idle is that the gNB releases the UE context. On the other hand, the UE context is retained when it is inactive. This means that the controllability of gNB may be lost, which may contradict the general concept of delivery mode 1. Therefore, RAN2 should agree that distribution mode 1 can be received by the UE at least inactive, but further consideration is needed at idle.
- Proposal 3 In delivery mode 1, RAN2 should agree that delivery mode 1 can be received by the UE at least inactive. Further consideration is needed for idols.
- RRC reconfiguration Idle / inactive UEs continue to apply the MBS configuration provided by the RRC reconfiguration. This option is simple because the UE only reuses the MBS settings originally provided for RRC Connected. However, consider the behavior of some UEs when transitioning to idle / inactive and / or when resuming RRC connected, for example, how to handle PTP / PTM split bearer settings if configured. May need to be done.
- RRC release Idle / inactive UEs apply the MBS settings provided by RRC release. While this option is obvious, it may not be efficient because it is doubtful whether the MBS settings are different from those previously provided by the RRC reconfiguration.
- -Option 3 Switching the distribution mode from mode 1 to mode 2
- the UE is switched from distribution mode 1 to distribution mode 2 before being released idle / inactive.
- Delivery mode 2 is designed to receive data in all RRC states, as RAN2 agreed, so this option is another simple solution. However, it may be expected that packet loss and / or delay will occur during switching, for example due to the acquisition of MCCH.
- RAN2 considers, but is not limited to, the above options, and should discuss how to provide a delivery mode 1 setting for idle / inactive data reception.
- Proposal 4 If Proposal 3 can be agreed, RAN2 should discuss how the delivery mode 1 setting for inactive data reception is provided to the UE.
- the configuration is provided by two messages: SIB20 and SC-MCCH.
- the SIB 20 provides SC-MCCH scheduling information
- the SC-MCCH provides SC-MTCH scheduling information including G-RNTI and TMGI, and adjacent cell information.
- the advantage of the LTE two-stage setting as shown in FIG. 18 is that the SC-MCCH scheduling is independent of the SIB20 scheduling in terms of repeat period, period, change period, and the like. In particular, frequent scheduling / updating of the SC-MCCH has been facilitated for delay-sensitive services and / or UEs that join late in the session. According to WID, one of the applications is group communication, so the same applies to NR MBS.
- Findings 1 In LTE, a two-step configuration using SIB20 and SC-MCCH is useful for different scheduling of these control channels. This is also useful for NR MBS.
- Proposal 5 RAN2 should agree to use a two-step setting with different NR MBS messages, such as SC-PTM SIB20 and SC-MCCH.
- NR MBS is expected to support the various types of use cases described in WID.
- NR MBS is an application that is tolerant of delays such as IoT, from delay-sensitive applications such as mission-critical and V2X, in addition to other aspects of requirements from lossless applications such as software distribution to UDP-type streaming such as IPTV. It is noticed that it should be properly designed to meet various requirements. Some of these services may be covered by delivery mode 2, but other services with "high QoS requirements" require delivery mode 1. In this sense, it is beneficial for the gNB to be able to choose to use delivery mode 2 for the multicast session.
- RAN2 since RAN2 has already agreed to allow data reception on the RRC connected, it is easy to allow the UE on the RRC connected to receive the MBS settings. It makes no sense if the UE needs to transition idle / inactive just to get the MCCH. It is easy to allow a connected UE to receive MCCH, but scheduling flexibility (because the UE may need a "gap") and / or UE power consumption (UE is C- It may not be optimal in terms of (because it is necessary to monitor "SC-RNTI" in addition to RNTI and G-RNTI). Therefore, further discussion may be needed as to whether the UE receives MBS settings via MCCH or RRC reconfiguration.
- Proposal 6 RAN2 should agree that delivery mode 2 can be used for multicast sessions in addition to broadcast sessions.
- Proposal 7 In distribution mode 2, RAN2 should agree that the MBS settings can also be received by RRC connected UEs. Further consideration is required as to whether MCCH or RRC is reset.
- control channel design for distribution mode 2 should consider flexibility and its resource efficiency. Otherwise, for example, if a delay-tolerant service and a delay-sensitive service are configured together in one control channel, the control channel should be configured to meet the delay requirements from the delay-sensitive service. More signaling overhead can be incurred due to frequent scheduling.
- Purpose A of SA2 SI is about enabling general MBS services via 5GS, and the identified use cases that may benefit from this feature are public safety, mission critical, Includes, but is not limited to, V2X applications, transparent IPv4 / IPv6 multicast distribution, IPTV, software distribution over radio, group communication, and IoT applications.
- Finding 2 The NR MBS control channel for delivery mode 2 is required to be flexible and resource efficient for various types of use cases.
- one MCCH frequently provides delay-sensitive services and another MCCH sparsely provides delay-tolerant services.
- LTE SC-PTM there is a limitation that one cell can have only one SC-MCCH.
- NR MBS delivery mode 2 should remove such restrictions. If multiple MCCHs are allowed in the cell, each MCCH has different scheduling settings, such as repeat periods, that can be optimized for a particular service. Further consideration is needed on how the UE identifies the MCCH that provides the service of interest.
- Proposal 8 In delivery mode 2, RAN2 should discuss whether the cell supports multiple MCCHs, which was not in LTE.
- a new paradigm for NR is support for on-demand SI transmission.
- This concept can be reused for MCCH in delivery mode 2, i.e., on-demand MCCH.
- MCCH delivery mode 2
- a delay-tolerant service MCCH is provided on demand, which can optimize signaling resource consumption.
- the network has another option to provide MCCH on a regular basis, i.e., for delay-sensitive services rather than on-demand.
- Proposal 9 In delivery mode 2, RAN2 should discuss options when MCCH is provided on demand, which was not in LTE.
- the SIB provides MTCH scheduling information directly, i.e. without MCCH. This will provide optimizations for delay-tolerant services and / or power-sensitive UEs.
- the UE may request an SIB (on-demand), and the gNB may start providing the SIB and the corresponding service after the request from the plurality of UEs. These UEs do not need to monitor the repeatedly broadcast MCCH.
- Proposal 10 In delivery mode 2, RAN2 should discuss options such as SIB providing MTCH scheduling information directly when multicast reception without MCCH (ie, one-step configuration) is supported.
- MII MBMS Interest Indications
- MBMS MBMS Interest Indications
- MBMS MBMS Interest Indications
- Counting was specified.
- the UE-triggered MII contains information related to the MBMS frequency of interest, the MBMS service of interest, the MBMS priority, and the MBMS ROM (receive-only mode).
- the counting response triggered by the network through the counting request of a particular MBMS service contains information related to the MBSFN area of interest and the MBMS service.
- MII is mainly used for networks to ensure that UEs can continue to receive services of interest during the connected state.
- Counting is used to allow the network to determine if a sufficient number of UEs are interested in receiving the service.
- Finding 3 In LTE eMBMS, two types of UE assistance information are introduced for different purposes. That is, MBMS interest indication is introduced for NB scheduling, and MBMS counting is introduced for MCE session control.
- NR MBS In the case of NR MBS, multicast services such as group communication use cases are expected, and since the network already has complete knowledge of MBS services that the connected UE is receiving / interested in, for example, the network Assistance information from the UE, such as the decision to deliver PTP / PTM, is useless to the network.
- Assistance information from the UE such as the decision to deliver PTP / PTM, is useless to the network.
- the same does not apply to broadcast services and / or idle / inactive UEs.
- the problem solved by counting with MII in LTE eMBMS that is, finding 3, still exists in NR MBS. Therefore, RAN2 needs to consider whether assistance information such as MII and counting is useful for NR MBS.
- ROM and SFN are not supported as described in WID, so Rel-17 does not need MII MBMS ROM information and information about the counting response MBSFN area.
- Proposal 11 RAN2 needs to agree to introduce NR MBS UE assistance information, such as MBS interest indication and / or MBS counting.
- LTE eMBMS neither MII nor counting can collect information from the idle UE even if most of the UEs are receiving the broadcast service in the RRC idle state. This is, in our understanding, one of the remaining problems with LTE eMBMS in terms of session control and resource efficiency.
- the same problem may exist in UEs in the idle / inactive state.
- the network does not know if the idle / inactive UE is not receiving / interested in the broadcast service. Therefore, the network may continue to provide PTM transmissions even if no UE is being serviced. Such unnecessary PTMs should be avoided if the gNB is aware of the interests of the idle / inactive UE. Conversely, if the PTM goes down while there are still idle / inactive UEs receiving service, many UEs may request a connection at the same time. This is also undesirable.
- Proposal 12 RAN2 needs to consider whether UE assistance information such as MBS counting is also collected from the idle / inactive UE.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
まず、実施形態に係る移動通信システムの構成について説明する。
次に、一実施形態に係るMBSについて説明する。
次に、一実施形態に係るスプリットMBSベアラについて説明する。スプリットMBSベアラは、上述の配信モード1において利用可能である。
次に、一実施形態に係る動作について説明する。以下において、配信モードとして配信モード1を用いる場合を主として想定する。
次に、上述の実施形態の第1変更例について、上述の実施形態との相違点を主として説明する。
1)UE100からgNB200bへのランダムアクセスプリアンブル(Msg1)の送信
2)gNB200bからUE100へのランダムアクセス応答(Msg2)の送信
3)UE100からgNB200bへのRRC Resume Requestメッセージ(Msg3)の送信
4)gNB200bからUE100へのRRC Resumeメッセージ(Msg4)の送信
5)UE100からgNB200bへのRRC Resume Completeメッセージ(Msg5)の送信
他方、2ステップのランダムアクセスプロシージャは、Msg1及びMsg3が1つのメッセージ(MsgA)に統合され、Msg2及びMsg4が1つのメッセージ(MsgB)に統合される。
次に、上述の実施形態の第2変更例について、上述の実施形態との相違点を主として説明する。本変更例において、UE100は、RRCコネクティッド状態からRRCアイドル状態又はRRCインアクティブ状態へ遷移する場合、RRCコネクティッド専用設定を保持するものとする。
次に、上述の実施形態の第3変更例について、上述の実施形態との相違点を主として説明する。
次に、上述の実施形態の第4変更例について、上述の実施形態との相違点を主として説明する。
次に、上述の実施形態の第5変更例について、上述の実施形態との相違点を主として説明する。
次に、上述の実施形態の第6変更例について、上述の実施形態との相違点を主として説明する。
上述の各変更例は、別個独立して実施する場合に限らず、2以上の変更例を組み合わせて実施可能である。
(導入)
NRのマルチキャストブロードキャストサービス(MBS)に関する改訂されたワークアイテムが承認された。MBSの2つの配信モードを次のように導入することが合意された。
1:コネクティッド(データ受信がない場合、UEは他の状態に切り替えることができる可能性があるが、未定)で利用可能な高QoS(信頼性、遅延)要件のための配信モード。
2:「低」QoS要件のための配信モード。UEはインアクティブ/アイドルでもデータを受信し得る(詳細は未定)。
・R2は、(R17の場合)配信モード1がマルチキャストセッションにのみ使用されることを前提とする。
・R2は、配信モード2がブロードキャストセッションに使用されることを前提とする。
・配信モード2のマルチキャストセッションへの適用性は、更なる検討が必要である。
・データなし:マルチキャストセッションで進行中のデータがない場合、UEはRRCコネクティッドに留まり得る。その他の場合は、更なる検討が必要である。
RAN2の合意に従って、この時点での2つの配信モードを表1に要約する。
配信モード1は、主にRRCコネクティッドでのデータ受信のために検討されるが、設定の側面はまだ合意されていない。MBS設定がRRC再設定によって提供されることは非常に平易であり得るが、LTE eMBMSのようにコネクティッドでMCCHが受信されることはまだ検討中である。配信モード1は高QoSサービスに期待されることを考慮すると、例えば、PTP/PTMスプリットベアラ及び/又はロスレスハンドオーバなどを伴うべきである。これらのUE固有の設定がMCCHを介して提供されている場合、意味がないため、私たちの見解では、配信モード1の設定にRRC再設定が使用されるべきである。
アイドル/インアクティブのUEは、RRC再設定によって提供されたMBS設定を引き続き適用する。UEは元々RRCコネクティッド用に提供されたMBS設定を再利用するだけなので、このオプションは単純である。しかし、アイドル/インアクティブに遷移する場合及び/又はRRCコネクティッドをレジュームする場合に、例えば、設定されている場合はPTP/PTMスプリットベアラ設定を処理する方法など、いくつかのUEの動作を検討する必要がある可能性がある。
アイドル/インアクティブのUEは、RRC解放によって提供されるMBS設定を適用する。このオプションは明快であるが、MBS設定が以前にRRC再設定によって提供されたものと異なるかどうかは疑わしいため、効率的ではない可能性がある。
UEは、アイドル/インアクティブに解放される前に、配信モード1から配信モード2に切り替えられる。配信モード2は、RAN2が合意したように、すべてのRRC状態でデータを受信できるように設計されているため、このオプションはもう1つの簡単な解決策である。しかし、例えば、MCCHの取得が原因で、スイッチング中にパケット損失及び/又は遅延が発生することが予想される可能性がある。
LTE SC-PTMにおいて、設定は2つのメッセージ、即ち、SIB20及びSC-MCCHによって提供される。SIB20は、SC-MCCHスケジューリング情報を提供し、SC-MCCHは、G-RNTI及びTMGIを含むSC-MTCHスケジューリング情報、及び隣接セル情報を提供する。
LTE eMBMSでは、ネットワークがMBMSセッションの開始/停止を含むMBMSデータ配信の適切な決定をするために、UEの受信/興味サービスを収集する2種類の方法、つまりMBMS興味インディケーション(MII)とMBMSカウンティングが指定された。UEによってトリガされるMIIには、興味を持つMBMS周波数、興味を持つMBMSサービス、MBMS優先度、およびMBMS ROM(受信専用モード)に関連する情報が含まれている。特定のMBMSサービスのカウンティング要求を介してネットワークによってトリガされるカウンティング応答には、興味を持つMBSFNエリアおよびMBMSサービスに関連する情報が含まれている。
Claims (10)
- マルチキャスト・ブロードキャストサービス(MBS)を提供する移動通信システムにおいてユーザ装置が実行する通信制御方法であって、
RRC(Radio Resource Control)コネクティッド状態にある前記ユーザ装置が、MBS受信に必要なMBS設定を含むRRCメッセージを基地局から受信することと、
前記RRCコネクティッド状態からRRCアイドル状態又はRRCインアクティブ状態に遷移した前記ユーザ装置が、前記RRCコネクティッド状態時に受信した前記MBS設定を用いて、前記MBS受信を行うことと、を有し、
前記RRCメッセージは、RRC Reconfigurationメッセージ又はRRC Releaseメッセージである
通信制御方法。 - 前記受信することは、前記RRCコネクティッド状態における前記MBS受信にのみ適用可能なRRCコネクティッド専用設定を含む前記RRC Reconfigurationメッセージを受信することを含む
請求項1に記載の通信制御方法。 - 前記ユーザ装置が、前記RRCアイドル状態又は前記RRCインアクティブ状態に遷移する際に、前記受信したRRC Reconfigurationメッセージに含まれる前記RRCコネクティッド専用設定を無効化する処理を行うことをさらに有する
請求項2に記載の通信制御方法。 - 前記RRCインアクティブ状態に遷移した前記ユーザ装置が、前記RRCインアクティブ状態において前記RRCコネクティッド専用設定を保持することと、
前記ユーザ装置が、前記RRCインアクティブ状態から前記RRCコネクティッド状態に遷移するレジューム動作時に、前記RRCコネクティッド専用設定を保持していることを示す通知を前記基地局に送信することと、をさらに有する
請求項2又は3に記載の通信制御方法。 - 前記RRCアイドル状態又は前記RRCインアクティブ状態に遷移した前記ユーザ装置が、前記RRCコネクティッド専用設定を保持することと、
前記ユーザ装置が、前記RRCアイドル状態又は前記RRCインアクティブ状態において、セル再選択に関する所定条件が満たされたと判定した場合、前記基地局に対するランダムアクセスプロシージャを開始することと、
前記ランダムアクセスプロシージャにおいて、前記所定条件が満たされたことを示す通知を前記基地局に送信することと、をさらに有する
請求項2又は3に記載の通信制御方法。 - 前記RRCコネクティッド状態において前記RRCコネクティッド専用設定を有する前記ユーザ装置は、前記RRCアイドル状態又は前記RRCインアクティブ状態への遷移が禁止され、
前記ユーザ装置が、前記基地局により前記RRCコネクティッド専用設定が解放された後に、前記RRCアイドル状態又は前記RRCインアクティブ状態に遷移することをさらに有する
請求項2に記載の通信制御方法。 - 前記受信することは、前記MBS設定が有効なエリア範囲を示すエリア情報を含む前記RRCメッセージを受信することを含み、
前記MBS受信を行うことは、前記エリア情報が示す前記エリア範囲内において、前記MBS設定を用いて前記MBS受信を行うことを含む
請求項1乃至6のいずれか1項に記載の通信制御方法。 - 前記RRCメッセージは、前記RRC Reconfigurationメッセージであり、
前記ユーザ装置が、前記RRCコネクティッド状態時に受信した前記MBS設定を前記RRCアイドル状態又は前記RRCインアクティブ状態において使用可能とするか否かを示す情報を含むRRC Releaseメッセージを前記基地局から受信することをさらに有する
請求項1乃至7のいずれか1項に記載の通信制御方法。 - 前記受信することは、隣接セル情報を含む前記RRC Releaseメッセージを受信することを含み、
前記隣接セル情報は、隣接セルの識別子と、前記隣接セルが提供するMBSサービスを示す識別子とを含み、
前記RRCアイドル状態又は前記RRCインアクティブ状態に遷移した前記ユーザ装置が、前記隣接セル情報に基づいてセル再選択を制御することをさらに有する
請求項1乃至8のいずれか1項に記載の通信制御方法。 - マルチキャスト・ブロードキャストサービス(MBS)を提供する移動通信システムにおいて用いるユーザ装置であって、
前記ユーザ装置がRRC(Radio Resource Control)コネクティッド状態にあるときに、MBS受信に必要なMBS設定を含むRRCメッセージを基地局から受信する受信部と、
前記RRCコネクティッド状態からRRCアイドル状態又はRRCインアクティブ状態に遷移した後に、前記RRCコネクティッド状態時に受信した前記MBS設定を用いて前記MBS受信を行う制御部と、を有し、
前記RRCメッセージは、RRC Reconfigurationメッセージ又はRRC Releaseメッセージである
ユーザ装置。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202180095165.XA CN116918358A (zh) | 2021-01-06 | 2021-12-24 | 通信控制方法和用户设备 |
EP21917709.4A EP4258705A4 (en) | 2021-01-06 | 2021-12-24 | COMMUNICATION CONTROL METHOD AND USER EQUIPMENT |
JP2022574005A JP7448689B2 (ja) | 2021-01-06 | 2021-12-24 | 通信制御方法及びユーザ装置 |
US18/348,129 US20230354465A1 (en) | 2021-01-06 | 2023-07-06 | Communication control method and user equipment |
JP2024029811A JP2024059904A (ja) | 2021-01-06 | 2024-02-29 | 通信制御方法、ユーザ装置、チップセット、プログラム、基地局及びシステム |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202163134280P | 2021-01-06 | 2021-01-06 | |
US63/134,280 | 2021-01-06 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/348,129 Continuation US20230354465A1 (en) | 2021-01-06 | 2023-07-06 | Communication control method and user equipment |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022149489A1 true WO2022149489A1 (ja) | 2022-07-14 |
Family
ID=82357284
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/048137 WO2022149489A1 (ja) | 2021-01-06 | 2021-12-24 | 通信制御方法及びユーザ装置 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20230354465A1 (ja) |
EP (1) | EP4258705A4 (ja) |
JP (2) | JP7448689B2 (ja) |
CN (1) | CN116918358A (ja) |
WO (1) | WO2022149489A1 (ja) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP4319471A1 (en) * | 2022-08-03 | 2024-02-07 | Acer Incorporated | Method of user equipment receiving multicast multicast/broadcast service data, ue, and method of a cell providing a multicast multicast/broadcast service data |
WO2024034567A1 (ja) * | 2022-08-09 | 2024-02-15 | 京セラ株式会社 | 通信方法 |
WO2024034566A1 (ja) * | 2022-08-09 | 2024-02-15 | 京セラ株式会社 | 通信方法 |
WO2024082295A1 (zh) * | 2022-10-21 | 2024-04-25 | 北京小米移动软件有限公司 | 小区处理、小区处理指示方法和装置 |
EP4366453A1 (en) * | 2022-11-04 | 2024-05-08 | Nokia Technologies Oy | Method to use quality of service to control multicast reception of user equipment in rrc inactive state |
WO2024162425A1 (ja) * | 2023-02-03 | 2024-08-08 | 京セラ株式会社 | 通信方法 |
WO2024162426A1 (ja) * | 2023-02-03 | 2024-08-08 | 京セラ株式会社 | 通信方法 |
WO2024186027A1 (en) * | 2023-03-08 | 2024-09-12 | Lg Electronics Inc. | Method and apparatus for multicast configuration in a wireless communication system |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3101923B1 (en) * | 2014-01-31 | 2018-09-26 | Kyocera Corporation | Mbms measurement control method and user terminal |
EP3873126A4 (en) | 2018-10-26 | 2022-02-16 | NEC Corporation | RADIO TERMINAL, RADIO ACCESS NETWORK NODE, AND METHOD THEREOF |
EP3928576B1 (en) | 2019-04-01 | 2023-10-25 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Apparatus and method of wireless communication |
-
2021
- 2021-12-24 EP EP21917709.4A patent/EP4258705A4/en active Pending
- 2021-12-24 CN CN202180095165.XA patent/CN116918358A/zh active Pending
- 2021-12-24 WO PCT/JP2021/048137 patent/WO2022149489A1/ja active Application Filing
- 2021-12-24 JP JP2022574005A patent/JP7448689B2/ja active Active
-
2023
- 2023-07-06 US US18/348,129 patent/US20230354465A1/en active Pending
-
2024
- 2024-02-29 JP JP2024029811A patent/JP2024059904A/ja active Pending
Non-Patent Citations (5)
Title |
---|
3GPP TS 38.300, September 2020 (2020-09-01) |
CMCC: "Discussion on MBS supported UEs", 3GPP DRAFT; R2-2007416, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051912163 * |
See also references of EP4258705A4 |
VIVO: "Discussion on idle and inactive mode UEs", 3GPP DRAFT; R2-2007037, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911885 * |
VIVO: "MBS Service Continuity for RRC Connected UE", 3GPP DRAFT; R2-2007035, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911883 * |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP4319471A1 (en) * | 2022-08-03 | 2024-02-07 | Acer Incorporated | Method of user equipment receiving multicast multicast/broadcast service data, ue, and method of a cell providing a multicast multicast/broadcast service data |
WO2024034567A1 (ja) * | 2022-08-09 | 2024-02-15 | 京セラ株式会社 | 通信方法 |
WO2024034566A1 (ja) * | 2022-08-09 | 2024-02-15 | 京セラ株式会社 | 通信方法 |
WO2024082295A1 (zh) * | 2022-10-21 | 2024-04-25 | 北京小米移动软件有限公司 | 小区处理、小区处理指示方法和装置 |
EP4366453A1 (en) * | 2022-11-04 | 2024-05-08 | Nokia Technologies Oy | Method to use quality of service to control multicast reception of user equipment in rrc inactive state |
WO2024162425A1 (ja) * | 2023-02-03 | 2024-08-08 | 京セラ株式会社 | 通信方法 |
WO2024162426A1 (ja) * | 2023-02-03 | 2024-08-08 | 京セラ株式会社 | 通信方法 |
WO2024186027A1 (en) * | 2023-03-08 | 2024-09-12 | Lg Electronics Inc. | Method and apparatus for multicast configuration in a wireless communication system |
Also Published As
Publication number | Publication date |
---|---|
JP2024059904A (ja) | 2024-05-01 |
JP7448689B2 (ja) | 2024-03-12 |
US20230354465A1 (en) | 2023-11-02 |
EP4258705A4 (en) | 2023-12-06 |
JPWO2022149489A1 (ja) | 2022-07-14 |
EP4258705A1 (en) | 2023-10-11 |
CN116918358A (zh) | 2023-10-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022149489A1 (ja) | 通信制御方法及びユーザ装置 | |
WO2022085757A1 (ja) | 通信制御方法 | |
JP6347005B1 (ja) | ユーザ端末、通信方法及びプロセッサ | |
WO2022153991A1 (ja) | 通信制御方法 | |
WO2022085717A1 (ja) | 通信制御方法 | |
WO2022025013A1 (ja) | 通信制御方法 | |
US20240080939A1 (en) | Communication control method and user equipment | |
WO2022030452A1 (ja) | 通信制御方法、基地局、及びユーザ装置 | |
US20240179797A1 (en) | Communication method, network apparatus, and user equipment | |
US20230362595A1 (en) | Communication control method and user equipment | |
US20240080645A1 (en) | Communication control method | |
US20240179798A1 (en) | Communication method | |
US20240237143A1 (en) | Communication method | |
WO2022210545A1 (ja) | 通信制御方法及びユーザ装置 | |
WO2022202834A1 (ja) | 通信制御方法及びユーザ装置 | |
JP7508634B2 (ja) | 通信制御方法、基地局、ユーザ装置及びプロセッサ | |
WO2024162425A1 (ja) | 通信方法 | |
WO2024096049A1 (ja) | 通信方法及びネットワーク装置 | |
WO2024034567A1 (ja) | 通信方法 | |
WO2022085646A1 (ja) | 通信制御方法 | |
JP2024123238A (ja) | 通信制御方法、ユーザ装置、プロセッサ、プログラム及び移動通信システム | |
JP2024084816A (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: 21917709 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2022574005 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2021917709 Country of ref document: EP Effective date: 20230706 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180095165.X Country of ref document: CN |