WO2022085573A1 - 通信制御方法 - Google Patents
通信制御方法 Download PDFInfo
- Publication number
- WO2022085573A1 WO2022085573A1 PCT/JP2021/038145 JP2021038145W WO2022085573A1 WO 2022085573 A1 WO2022085573 A1 WO 2022085573A1 JP 2021038145 W JP2021038145 W JP 2021038145W WO 2022085573 A1 WO2022085573 A1 WO 2022085573A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mbs
- packet
- header
- base station
- control method
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 238000004891 communication Methods 0.000 title claims abstract description 39
- 230000005540 biological transmission Effects 0.000 claims abstract description 52
- 238000007906 compression Methods 0.000 claims abstract description 32
- 238000010295 mobile communication Methods 0.000 claims abstract description 25
- 230000003068 static effect Effects 0.000 claims abstract description 7
- 230000008569 process Effects 0.000 claims description 11
- 238000000101 transmission high energy electron diffraction Methods 0.000 claims description 5
- 230000006870 function Effects 0.000 description 23
- 230000006835 compression Effects 0.000 description 22
- 238000012545 processing Methods 0.000 description 22
- 230000006837 decompression Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 13
- 238000013507 mapping Methods 0.000 description 6
- 230000011664 signaling Effects 0.000 description 6
- 238000007726 management method Methods 0.000 description 4
- 230000007704 transition Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 238000012384 transportation and delivery Methods 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000001052 transient effect Effects 0.000 description 2
- 230000004308 accommodation Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/04—Protocols for data compression, e.g. ROHC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/30—Resource management for broadcast services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/02—Data link layer protocols
Definitions
- the present invention relates to a communication control method used in a mobile communication system.
- NR New Radio
- RAT Radio Access Technology
- LTE Long Term Evolution
- the communication control method is a communication control method used in a mobile communication system that provides a multicast broadcast service (MBS) from a base station to a user device, and the base station is the header of the MBS packet. While performing the header compression process that omits the transmission of the header information that is the static information contained in the After starting the transmission, the header information is transmitted separately from the compressed MBS packet.
- MBS multicast broadcast service
- the communication control method is a communication control method used in a mobile communication system that provides a multicast broadcast service (MBS) from a base station to a user apparatus, and the user apparatus is from the base station.
- MBS multicast broadcast service
- Receiving an MBS packet and using the PDCP sequence number included in the MBS packet first received by the PDCP (Packet Data Broadcast Protocol) entity of the user device from the base station as the initial value of the variable used for the predetermined PDCP operation. To set and have.
- MBS multicast broadcast service
- the communication control method is a communication control method used in a mobile communication system that provides a multicast / broadcast service (MBS) from a base station to a user apparatus, and the user apparatus is from the base station.
- MBS multicast / broadcast service
- the SADP header for the MBS packet is due to the fact that the MBS packet is received via the MBS data bearer and the SDAP (Service Data Accommodation Multicast) layer of the user apparatus considers that the MBS packet does not have the SDAP header attached.
- the MBS packet is passed to a higher layer without performing a removal process.
- the communication control method is a communication control method used in a mobile communication system that provides a multicast broadcast service (MBS) from a base station to a user apparatus, wherein the base station has one MBS session. Mapping one or a plurality of QoS (Quality of Service) flows belonging to a plurality of MBS data bearers, and the base station connecting a plurality of logical channels corresponding to the plurality of MBS data bearers to one RNTI (Radio). It has multiple transmissions by Network Temporary Idea).
- MBS multicast broadcast service
- QoS Quality of Service
- NR 5G systems
- the present invention aims to realize an improved multicast / broadcast service.
- FIG. 1 is a diagram showing a configuration of a mobile communication system according to an embodiment.
- This mobile communication system complies with the 5th generation system (5GS: 5th Generation System) of the 3GPP standard.
- 5GS 5th Generation System
- 5GS will be described as an example, but the LTE (Long Term Evolution) system may be applied at least partially to the mobile communication system, and the 6th generation (6G) system may be applied at least partially. May be done.
- mobile communication systems include a user device (UE: User Equipment) 100, a 5G radio access network (NG-RAN: Next Generation Radio Access Network) 10, and a 5G core network (5GC: 5G). It has Core Network) 20.
- UE User Equipment
- NG-RAN Next Generation Radio Access Network
- 5GC 5G core network
- the UE 100 is a mobile wireless communication device.
- the UE 100 may be any device as long as it is a device used by the user.
- the UE 100 may be a mobile phone terminal (including a smartphone), a tablet terminal, a notebook PC, or a communication module (communication card or communication card). (Including a chip set), a sensor or a device provided on the sensor, a vehicle or a device provided on the vehicle (Vehicle UE), a vehicle or a device provided on the vehicle (Arial UE).
- 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”), a measurement control function for mobility control / scheduling, and the like.
- RRM radio resource management
- Cell is used as a term to indicate the smallest unit of a wireless communication area.
- the term “cell” is also used to indicate a function or resource for wireless communication with the UE 100.
- One cell belongs to one carrier frequency.
- gNB can also connect to EPC (Evolved Packet Core), which is the core network of LTE.
- EPC Evolved Packet Core
- LTE base stations can also be connected to 5GC.
- the LTE base station and gNB can also be connected via an inter-base station interface.
- 5GC20 includes AMF (Access and Mobility Management Function) and UPF (User Plane Function) 300.
- the AMF performs various mobility controls and the like for the UE 100.
- the AMF manages the mobility of the UE 100 by communicating with the UE 100 using NAS (Non-Access Stratum) signaling.
- UPF controls data transfer.
- the AMF and UPF are connected to the gNB 200 via the NG interface, which is an interface between the base station and the core network.
- FIG. 2 is a diagram showing a configuration of a UE 100 (user device) according to an embodiment.
- the UE 100 includes a receiving unit 110, a transmitting unit 120, and a control unit 130.
- the receiving unit 110 performs various receptions under the control of the control unit 130.
- the receiving unit 110 includes an antenna and a receiver.
- the receiver converts the radio signal received by the antenna into a baseband signal (received signal) and outputs it to the control unit 130.
- the transmission unit 120 performs various transmissions under the control of the control unit 130.
- the transmitter 120 includes an antenna and a transmitter.
- the transmitter converts the baseband signal (transmission signal) output by the control unit 130 into a radio signal and transmits it from the antenna.
- the control unit 130 performs various controls on the UE 100.
- the control unit 130 includes at least one processor and at least one memory.
- the memory stores a program executed by the processor and information used for processing by the processor.
- the processor may include a baseband processor and a CPU (Central Processing Unit).
- the baseband processor modulates / demodulates and encodes / decodes the baseband signal.
- the CPU executes a program stored in the memory to perform various processes.
- FIG. 3 is a diagram showing the configuration of gNB200 (base station) according to one embodiment.
- the gNB 200 includes a transmission unit 210, a reception unit 220, a control unit 230, and a backhaul communication unit 240.
- the transmission unit 210 performs various transmissions under the control of the control unit 230.
- the transmitter 210 includes an antenna and a transmitter.
- the transmitter converts the baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits it from the antenna.
- the receiving unit 220 performs various receptions under the control of the control unit 230.
- the receiving unit 220 includes an antenna and a receiver.
- the receiver converts the radio signal received by the antenna into a baseband signal (received signal) and outputs it to the control unit 230.
- the control unit 230 performs various controls on the gNB 200.
- the control unit 230 includes at least one processor and at least one memory.
- the memory stores a program executed by the processor and information used for processing by the processor.
- the processor may include a baseband processor and a CPU.
- the baseband processor modulates / demodulates and encodes / decodes the baseband signal.
- the CPU executes a program stored in the memory to perform various processes.
- the backhaul communication unit 240 is connected to an adjacent base station via an interface between base stations.
- the backhaul communication unit 240 is connected to the AMF / UPF 300 via the base station-core network interface.
- the gNB is composed of a CU (Central Unit) and a DU (Distributed Unit) (that is, the functions are divided), and both units may be connected by an F1 interface.
- FIG. 4 is a diagram showing a configuration of a protocol stack of a wireless interface of a user plane that handles data.
- the wireless interface protocol of the user plane includes a physical (PHY) layer, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, and a PDCP (Packet Data Convergence Protocol) layer. It has an SDAP (Service Data Adjustment Protocol) layer.
- PHY physical
- MAC Medium Access Control
- RLC Radio Link Control
- PDCP Packet Data Convergence Protocol
- SDAP Service Data Adjustment Protocol
- the PHY layer performs coding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the PHY layer of the UE 100 and the PHY layer of the gNB 200 via a physical channel.
- the MAC layer performs data priority control, retransmission processing by hybrid ARQ (HARQ), random access procedure, and the like. Data and control information are transmitted between the MAC layer of the UE 100 and the MAC layer of the gNB 200 via the transport channel.
- the MAC layer of gNB200 includes a scheduler. The scheduler determines the transport format (transport block size, modulation / coding method (MCS)) of the upper and lower links and the resource block allocated to the UE 100.
- MCS modulation / coding method
- the RLC layer transmits data to the receiving RLC layer by using the functions of the MAC layer and the PHY layer. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the gNB 200 via a logical channel.
- the PDCP layer performs header compression / decompression and encryption / decryption.
- the SDAP layer maps an IP flow, which is a unit 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 broadcasts or multicasts data from NG-RAN10 to UE100, that is, one-to-many (PTM: Point To Multipoint) data transmission.
- PTM Point To Multipoint
- MBS may be referred to as MBMS (Multicast Broadcast and Multicast Service).
- the MBS use cases (service types) include public safety communication, mission-critical communication, V2X (Vehicle to Everything) communication, IPv4 or IPv6 multicast distribution, IPTV, group communication, software distribution, and the like.
- FIG. 6 is a diagram showing a correspondence relationship between a downlink logical channel (Logical channel) and a transport channel (Transport channel) according to an embodiment.
- MBSFN Multipoint Broadcast Single Frequency Network
- SC-PTM Single Cell Point To Multipoint
- the logical channels used for MBSFN transmission are MTCH (Multicast Traffic Channel) and MCCH (Multicast Control Channel), and the transport channel used for MBSFN transmission is MCH (Multicast Control Channel).
- MBSFN transmission is mainly designed for multi-cell transmission, and each cell performs synchronous transmission of the same signal (same data) in the same MBSFN subframe in an MBSFN area composed of a plurality of cells.
- 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 channels used for SC-PTM transmission are DL-SCH (Downlink). ).
- SC-PTM transmission is designed primarily for single-cell transmission and performs broadcast or multicast data transmission on a cell-by-cell basis.
- the physical channels used for SC-PTM transmission are PDCCH (Physical Downlink Control Channel) and PDSCH (Physical Downlink Control Channel), and dynamic resource allocation is possible.
- MBS may be provided using the SC-PTM transmission method.
- MBS may be provided using the MBSFN transmission method.
- MBS may be read as multicast.
- MBS may be provided by broadcast.
- MBS data means data transmitted by MBS
- the MBS control channel means MCCH or SC-MCCH
- the MBS traffic channel means MTCH or SC-MTCH.
- MBS data may be transmitted by unicast.
- MBS data may be referred to as MBS packets or MBS traffic.
- the network can provide different MBS services for each MBS session.
- the MBS session is identified by at least one of TMGI (Temporary Mobile Group Identity) and a session identifier, and at least one of these identifiers is called an MBS session identifier.
- TMGI Temporal Mobile Group Identity
- Such an MBS session identifier may be referred to as an MBS service identifier or a multicast group identifier.
- FIG. 7 is a diagram showing a method of distributing MBS data according to an embodiment.
- MBS data (MBS Traffic) is distributed from a single data source (application service provider) to a plurality of UEs.
- the 5G CN (5GC) 20 which is a 5G core network, receives MBS data from an application service provider, creates a copy of the MBS data (Replication), and distributes it.
- NG-RAN10 5G radio access networks
- 5G RAN 5G radio access networks
- MBS connection such a connection (tunnel) will be referred to as an “MBS connection”.
- the MBS connection may be referred to as a Shared MBS Traffic delivery connection or a shared transport.
- the MBS connection is terminated at NG-RAN10 (ie, gNB200).
- the MBS connection may have a one-to-one correspondence with the MBS session.
- the gNB 200 selects either PTP (Point-to-Point: Unicast) or PTM (Point-to-Multipoint: Multicast or Broadcast) at its own discretion, and transmits MBS data to the UE 100 by the selected method.
- PTP Point-to-Point: Unicast
- PTM Point-to-Multipoint: Multicast or Broadcast
- a unicast session is established between NG-RAN10 and UE100, and MBS data is individually distributed from 5GC20 to UE100.
- MBS data is individually distributed from 5GC20 to UE100.
- Such a unicast may be called a PDU session.
- Unicast (PDU session) ends at UE100.
- header compression process Next, the header compression process according to the embodiment will be described.
- FIG. 8 is a diagram showing a layer 2 structure of gNB200 in the downlink according to the embodiment.
- the physical layer provides a transport channel (Transport Channels) to the MAC layer.
- the MAC layer provides a logical channel (Logical Channels) to the RLC layer.
- the RLC layer provides an RLC channel (RLC Channels) to the PDCP layer.
- the PDCP layer provides radio bearers to the SDAP layer.
- the SDAP layer provides QoS Flows.
- the SDAP layer performs a process of associating (mapping) the QoS flow with the wireless bearer.
- the PDCP layer has a PDCP entity provided for each wireless bearer.
- Each PDCP entity has a function of performing processing by RoHC (Entity Header Compression).
- RoHC Entity Header Compression
- An example of using RoHC as the header compression protocol will be described below, but other protocols, for example, EHC (Ethernet Header Compression) may be used.
- the RoHC function performs IP header compression processing (hereinafter, simply referred to as "header compression processing").
- the data to be applied to RoHC is the user data flowing on the data radio bearer. Headers that can be compressed by RoHC include, for example, RTP, UDP, TCP, and IP headers.
- the RoHC function of the PDCP layer of gNB200 (hereinafter referred to as “gNB side RoHC function”) performs header compression by RoHC before performing encryption (ciphering).
- the RoHC function of the PDCP layer of the UE 100 (hereinafter referred to as “UE side RoHC function”) performs header decompression (header restoration) by RoHC after performing deciphering.
- the gNB side RoHC function performs state transitions in the order of, for example, IR (Initialization and Refresh) state, FO (First Order) state, and SO (Second Order) state.
- IR Initialization and Refresh
- FO First Order
- SO Serviced Order
- the compression rate of the header is the highest.
- the UE side RoHC function performs state transitions in the order of, for example, NC (No Control) state, SC (Static Contact) state, and FC (Full Contact) state.
- NC No Control
- SC Static Contact
- FC Full Contact
- the initial state of the RoHC function on the UE side is the NC state, and there is no information (header decompression context) necessary for header decompression, so that the decompression process cannot be executed correctly.
- the UE side RoHC function receives the header decompression context, it transitions to the FC state. After that, the transition to the SC state and the NC state is triggered by the continuous header decompression failure.
- RoHC is a header compression protocol mainly assuming unicast, and the following problems may occur.
- the UE 100 that participates in a certain MBS session from the beginning receives an uncompressed MBS packet that has not been subjected to header compression processing from the gNB 200, acquires header information from the uncompressed MBS packet, and provides information necessary for header decompression (header decompression context). ) Can be retained.
- the UE 100 that participated in the MBS session from the middle cannot receive the uncompressed MBS packet that has not been subjected to the header compression processing from the gNB 200, so that it cannot hold the information (header decompression context) necessary for header decompression, and the target header Unrecoverable. Therefore, there is a problem that the UE 100 that participates in the MBS session from the middle cannot normally perform the reception processing of the MBS packet.
- the UE 100 that participates in the MBS session from the middle can normally perform the reception processing of the MBS packet by the following method.
- the gNB 200 transmits a compressed MBS packet that has undergone header compression processing while performing header compression processing that omits transmission of header information that is static information included in the header of the MBS packet. After starting the transmission of the compressed MBS packet, the gNB 200 transmits the header information separately from the compressed MBS packet.
- the UE 100 that participates in the MBS session from the middle can hold the header information (header decompression context) by receiving the header information transmitted from the gNB 200 separately from the compressed MBS packet. Therefore, the UE 100 that participates in the MBS session from the middle can normally perform the reception processing of the MBS packet. Specifically, the UE 100 that has received the compressed MBS packet and the header information restores the header of the received compressed MBS packet by using the received header information.
- the gNB 200 transmits a compressed MBS packet via the MBS traffic channel.
- the gNB 200 transmits header information via a channel different from the MBS traffic channel.
- the gNB 200 transmits header information via a control channel for MBS (MBS control channel) to be transmitted by broadcast.
- MBS MBS control channel
- the gNB 200 may periodically transmit header information via the MBS control channel.
- the gNB 200 may transmit header information via an individual control channel (DCCH: Distributed Control Channel) transmitted by unicast.
- DCCH Distributed Control Channel
- the gNB 200 may transmit the header information to the UE 100 when the MBS reception setting is made to the UE 100.
- FIG. 9 is a diagram showing an operation example of a mobile communication system related to the header compression process according to the embodiment.
- step S101 gNB200 starts MBS transmission for a certain MBS session.
- step S102 the UE 100A that participates in the MBS session from the beginning starts receiving MBS for the MBS session.
- the UE 100A is in the RRC connected state, the RRC idle state, or the RRC inactive state.
- the UE 100A When the header information is not notified on the control channel (MBS control channel or individual control channel), the UE 100A is instructed to acquire the header information from the received packet as usual, or transmits uncompressed. It may be judged that it has been done.
- step S103 the gNB 200 transmits an uncompressed MBS packet by PTM via the MBS traffic channel.
- step S104 when the PDCP layer of the UE 100A receives the uncompressed MBS packet from the gNB 200, it acquires the header information to be compressed from the received uncompressed MBS packet and holds the header information (header decompression context).
- step S105 the gNB 200 transmits a compressed MBS packet to which header compression processing has been performed by PTM via the MBS traffic channel.
- step S106 when the PDCP layer of the UE 100A receives the compressed MBS packet from the gNB 200, the header information of the received compressed MBS packet is restored by using the header information held in step S104, and the MBS packet is passed to the upper layer.
- step S107 the UE 100B participates in the MBS session from the middle and starts receiving MBS for the MBS session.
- the UE 100B is in the RRC connected state, the RRC idle state, or the RRC inactive state.
- the gNB 200 transmits header information whose transmission is omitted due to the header compression process via the control channel (MBS control channel or individual control channel).
- the gNB 200 includes an identifier of the MBS traffic channel corresponding to the header information, an identifier of the MBS session corresponding to the header information (group RNTI, TMGI, and / or service ID), and the said.
- group RNTI, TMGI, and / or service ID an identifier of the MBS session corresponding to the header information.
- At least one of the QoS flow identifier, bearer identifier, RLC channel identifier, and logical channel identifier corresponding to the MBS session may be included in the message.
- step S109 when the PDCP layer of the UE 100B receives the header information from the gNB 200, the PDCP layer holds the received header information (header decompression context).
- the PDCP layer of the UE 100B may hold the above identifier received from the gNB 200 in association with the header information (header decompression context). It should be noted that the UE 100B may determine that when the header information is notified from the gNB 200, it is instructed that the header information cannot be (or does not have to be) acquired from the received packet.
- step S110 the gNB 200 transmits a compressed MBS packet to which header compression processing has been performed by PTM via the MBS traffic channel.
- step S111 when the PDCP layer of the UE 100B receives the compressed MBS packet from the gNB 200, it restores the header of the received compressed MBS packet using the header information held in step S109, and passes the MBS packet to the upper layer.
- step S112 when the PDCP layer of the UE 100A receives the compressed MBS packet from the gNB 200, the header information of the received compressed MBS packet is restored by using the header information held in step S104, and the MBS packet is passed to the upper layer.
- FIG. 10 is a diagram showing another operation example of the mobile communication system related to the header compression processing according to the embodiment.
- the gNB 200 transmits an uncompressed MBS packet that has not been subjected to header compression processing at a predetermined cycle. Specifically, the gNB 200 transmits the uncompressed MBS packet at a predetermined cycle after starting the transmission of the compressed MBS packet subjected to the header compression processing.
- steps S201 to S207 is the same as the operation of steps S101 to S107 of FIG.
- the gNB 200 transmits an uncompressed MBS packet by PTM via the MBS traffic channel.
- the gNB 200 may transmit uncompressed MBS packets via a control channel (MBS control channel or individual control channel).
- step S209 when the PDCP layer of the UE 100B receives the uncompressed MBS packet from the gNB 200, it acquires the header information to be compressed from the received uncompressed MBS packet and holds the header information (header decompression context).
- steps S210 to S212 is the same as the operation of steps S110 to S112 of FIG.
- the gNB 200 may determine a predetermined period for transmitting the uncompressed MBS packet according to the QoS request of the MBS session.
- the period length determined in response to the QoS request of the MBS session may be notified to the gNB 200 from the core network (AMF or the like).
- the cycle length is determined by the allowable amount of access delay to the MBS session of the UE 100.
- the predetermined cycle in which the gNB 200 transmits the uncompressed MBS packet may be linked (synchronized) with the change timing (modification boundary) of the MBS control channel. For example, the gNB 200 transmits uncompressed data in the same subframe as the modification boundary of the MBS control channel (or the MBS traffic channel transmission opportunity immediately after that).
- the predetermined cycle in which the gNB 200 transmits the uncompressed MBS packet is the timing in which the UE 100 and the gNB 200 are synchronized.
- SFN means a system frame number.
- the PDCP layer of the UE 100 sets and updates the PDCP variable according to the PDCP sequence number (PDCP SN) included in the packet received from the gNB 200. Normally, the UE 100B sets the initial value of the PDCP variable to zero, and updates (increments) the PDCP variable in response to receiving a packet from the gNB 200.
- PDCP SN PDCP sequence number
- the UE 100 who participated in a certain MBS session from the beginning can update the PDCP variables sequentially to the latest state.
- the UE 100 that participates in the MBS session from the middle can receive the MBS packet having the PDCP sequence number having a value far from the initial value, there is a possibility that the operation of the PDCP layer (predetermined PDCP operation) cannot be performed normally. There is.
- the UE 100 that participates in the MBS session from the middle can normally perform a predetermined PDCP operation by the following method.
- the PDCP entity of the UE 100 sets the PDCP sequence number included in the MBS packet first received from the gNB 200 as the initial value of the variable (PDCP variable) used for the predetermined PDCP operation. That is, when the PDCP entity of the UE 100 receives the MBS packet transmitted by the PTM, the PDCP sequence number included in the MBS packet first received from the gNB 200 is set as the initial PDCP variable instead of setting the PDCP variable to zero. Set as a value. As a result, the UE 100 that participates in the MBS session from the middle can normally perform the predetermined PDCP operation.
- the predetermined PDCP operation is at least one of the reception window control and the packet sorting operation.
- the PDCP variable used for receiving window control may be at least one of RX_NEXT and RX_DELIV.
- RX_NEXT is the sequence number of the PDCP SDU expected to be received next.
- RX_DELIV is the sequence number of the oldest PDCP SDU that is waiting for reception and has not yet been provided to the upper layer. Normally, the initial values of RX_NEXT and RX_DELIV are "0".
- the PDCP variable used for the packet sorting operation may be RX_REORD.
- RX_REORD is a sequence number of PDCP SDU that started a timer indicating the maximum time for waiting for packet rearrangement. For example, if the sequence number of the received packet is smaller than that of the UE 100, the UE 100 discards the packet.
- FIG. 11 is a diagram showing an operation example of a mobile communication system relating to a PDCP variable according to an embodiment.
- step S301 the gNB 200 starts MBS transmission for a certain MBS session.
- step S302 the UE 100A that participates in the MBS session from the beginning starts receiving MBS for the MBS session.
- the UE 100A is in the RRC connected state, the RRC idle state, or the RRC inactive state.
- the UE 100A may receive the MBS bearer (PDCP) setting from the gNB 200 and execute it.
- PDCP MBS bearer
- step S303 the gNB 200 transmits an MBS packet (PDCP packet) by PTM via the MBS bearer. It is assumed that the sequence number (PDCP sequence number) included in the PDCP header of this MBS packet (PDCP packet) is “0”.
- step S304 when the PDCP layer of the UE 100A receives the MBS packet from the gNB 200, the PDCP sequence number “0” included in the received MBS packet is set as the initial value of the PDCP variable, and a predetermined PDCP operation is performed.
- the UE 100B participates in the MBS session from the middle and starts receiving MBS for the MBS session.
- the UE 100B is in the RRC connected state, the RRC idle state, or the RRC inactive state.
- the UE 100B may receive the MBS bearer (PDCP) setting from the gNB 200 and execute it.
- PDCP MBS bearer
- step S306 the gNB 200 transmits an MBS packet (PDCP packet) by PTM via the MBS bearer. It is assumed that the sequence number (PDCP sequence number) included in the PDCP header of this MBS packet (PDCP packet) is “n”. However, "n" is an integer of 1 or more.
- step S307 when the PDCP layer of the UE 100B first receives the MBS packet (PDCP packet) via the MBS bearer, the PDCP sequence number “n” included in the first received MBS packet is set as the initial value of the PDCP variable. Then, perform a predetermined PDCP operation.
- step S308 when the PDCP layer of the UE 100A receives the MBS packet (PDCP packet) via the MBS bearer, the PDCP variable is updated with the PDCP sequence number “n” included in the received MBS packet.
- step S309 the gNB 200 transmits an MBS packet (PDCP packet) by PTM via the MBS bearer. It is assumed that the sequence number (PDCP sequence number) included in the PDCP header of this MBS packet (PDCP packet) is “n + 1”.
- step S310 when the PDCP layer of the UE 100B receives an MBS packet (PDCP packet) via the MBS bearer, the PDCP variable is updated with the PDCP sequence number “n + 1” included in the received MBS packet.
- step S311 when the PDCP layer of the UE 100A receives the MBS packet (PDCP packet) via the MBS bearer, the PDCP variable is updated with the PDCP sequence number “n + 1” included in the received MBS packet.
- the initial value of each PDCP variable was updated from the received MBS packet, but it is not limited to this.
- the initial value of each PDCP variable may be set from gNB200 to UE100.
- the initial value of each PDCP variable may be given from gNB200 when the MBS reception setting is performed in the signaled signaling.
- FIG. 12 is a diagram showing a data flow in the gNB 200 and the UE 100. Here, the downlink will be described.
- the SDAP layer of gNB200 performs a process of associating (mapping) a QoS flow with a wireless bearer, and assigns an SDAP header including an identifier of the QoS flow to the SDAP SDU (that is, an IP packet). Pass to the PDCP layer.
- the SDAP layer of the UE 100 receives the SDAP PDU from the PDCP layer, removes the SDAP header attached to the SDAP PDU, and passes the SDAP SDU (that is, an IP packet) to the upper layer.
- the SDAP header includes a QoS flow identifier, but in the case of only a downlink like MBS, the QoS flow identifier is not so meaningful due to the following reasons 1 to 3. Therefore, for MBS, the format without SDAP header is used to reduce overhead.
- Reflective mapping (operation of determining the QoS flow identifier of the uplink packet from the QoS flow identifier of the downlink packet) does not require the QoS flow identifier in the case of MBS.
- QoS flow is the minimum unit of QoS control in the core network, but it is QoS control in bearer units in wireless, and there is no particular QoS control in UE100, so the QoS flow identifier in MBS with only downlink. Is not necessary.
- the UE 100 that receives the MBS packet from the gNB 200 via the MBS data bearer considers that the received MBS packet does not have the SDAP header added to the received MBS packet in the SDAP layer, so that the SADP header for the MBS packet is not added.
- the MBS packet IP packet is passed to the upper layer without performing the removal process.
- the UE 100 determines that the MBS data bearer is transmitted without the SDAP header regardless of the setting of the SDAP header in the RRC. That is, even if the UE 100 receives the setting information (RRC setting information) related to the SDAC layer setting from the gNB 200, the UE 100 receives the MBS packet in the upper layer without performing the SADP header removal processing for the received MBS packet regardless of the setting information. Pass to.
- RRC setting information the setting information related to the SDAC layer setting from the gNB 200
- the gNB 200 multiplexes a plurality of logical channels corresponding to a plurality of applications by one C-RNTI (Cell Radio Network Temporary Identifier), that is, one PDSCH (Physical Downlink Shared Channel). Can be sent.
- C-RNTI Cell Radio Network Temporary Identifier
- PDSCH Physical Downlink Shared Channel
- MBS packets (logical channel for MBS) and normal unicast packets (logical channel for unicast) are sent by one C-RNTI (one PDSCH) as in unicast transmission. It is considered that multiple transmissions can be made.
- one group RNTI (one PDSCH) has a plurality of logics. It is considered that the channels cannot be multiplexed.
- the core network (5GC20) performs QoS control in units of QoS flows
- one MBS service may have a plurality of QoS flows.
- a plurality of QoS flows belonging to one MBS service can be mapped to different logical channels and transmitted by multiplex in one RNTI (one group RNTI) in the MAC layer.
- the gNB 200 maps one or more QoS flows belonging to one MBS session to multiple MBS data bearers in the SDAP layer. Then, the gNB 200 multiplexes and transmits a plurality of logical channels corresponding to the plurality of MBS data bearers in one RNTI (one group RNTI). As a result, a plurality of logical channels can be efficiently transmitted.
- FIG. 13 is a diagram showing an operation example of multiple transmission of a plurality of logical channels according to an embodiment.
- the SDAP layer maps a plurality of QoS flows belonging to one MBS session to k bearers.
- k is an integer of 2 or more.
- a plurality of QoS flows belonging to one MBS session means a plurality of QoS flows associated with one session identifier.
- the RLC layer of gNB200 passes MBS data of k logical channels corresponding to k bearers (k RLC channels) to the MAC layer.
- the MAC layer of gNB200 multiplexes and transmits MBS data of k logical channels in one group RNTI.
- the physical (PHY) layer of the gNB 200 transmits the allocation information of the PDSCH carrying the MBS data to the UE 100 by the PDCCH (Physical Downlink Control Channel) to which one group RNTI is applied.
- PDCCH Physical Downlink Control Channel
- the gNB 200 multiplexes and transmits the different logical channels in one group RNTI only when different QoS flows mapped to different logical channels are associated with one MBS session.
- the physical (PHY) layer of the UE 100 receives the PDSCH associated with the group RNTI.
- the MAC layer of the UE 100 passes the MBS data to the RLC layer via the corresponding logical channels.
- the UE 100 may determine that these logical channels are associated with one MBS session because these k logical channels are transmitted in the same group RNTI.
- the SDAP layer of the UE 100 passes MBS data of k bearers (multiple QoS flows) to a higher layer (for example, an application layer).
- the base station may be an NR base station (gNB)
- the base station may be an LTE base station (eNB).
- the base station may be a relay node such as an IAB (Integrated Access and Backhaul) node.
- the base station may be a DU (Distributed Unit) of an IAB node.
- a program may be provided that causes a computer to execute each process performed by the UE 100 or gNB 200.
- the program may be recorded on a computer-readable medium.
- Computer-readable media can be used to install programs on a computer.
- the computer-readable medium on which the program is recorded may be a non-transient recording medium.
- the non-transient recording medium is not particularly limited, but may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.
- a circuit that executes each process performed by the UE 100 or the gNB 200 may be integrated, and at least a part of the UE 100 or the gNB 200 may be configured as a semiconductor integrated circuit (chipset, SoC).
- NG-RAN 5G RAN
- 5GC 5G CN
- UE 110 Receiver unit 120: Transmitter unit 130: Control unit 200: gNB 210: Transmitter 220: Receiver 230: Control 240: Backhaul communication unit
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (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、グループ通信、及びソフトウェア配信等がある。
次に、一実施形態に係るヘッダ圧縮処理について説明する。
次に、一実施形態に係るPDCP変数について説明する。
次に、一実施形態に係るSDAPヘッダについて説明する。
次に、一実施形態に係る論理チャネルについて説明する。
上述の実施形態において、基地局がNR基地局(gNB)である一例について説明したが基地局がLTE基地局(eNB)であってもよい。また、基地局は、IAB(Integrated Access and Backhaul)ノード等の中継ノードであってもよい。基地局は、IABノードのDU(Distributed Unit)であってもよい。
20 :5GC(5G CN)
100 :UE
110 :受信部
120 :送信部
130 :制御部
200 :gNB
210 :送信部
220 :受信部
230 :制御部
240 :バックホール通信部
Claims (9)
- 基地局からユーザ装置に対してマルチキャスト・ブロードキャストサービス(MBS)を提供する移動通信システムで用いる通信制御方法であって、
前記基地局が、MBSパケットのヘッダに含まれる静的な情報であるヘッダ情報の送信を省略するヘッダ圧縮処理を行いつつ、前記ヘッダ圧縮処理が行われた圧縮MBSパケットを送信することと、
前記基地局が、前記圧縮MBSパケットの送信を開始した後、前記圧縮MBSパケットとは別に前記ヘッダ情報を送信することと、を有する
通信制御方法。 - 前記圧縮MBSパケット及び前記ヘッダ情報を受信した前記ユーザ装置が、前記受信したヘッダ情報を用いて、前記受信した圧縮MBSパケットのヘッダを復元することをさらに有する
請求項1に記載の通信制御方法。 - 前記圧縮MBSパケットを送信することは、MBSトラフィックチャネルを介して前記圧縮MBSパケットを送信することを含み、
前記ヘッダ情報を送信することは、前記MBSトラフィックチャネルと異なるチャネルを介して前記ヘッダ情報を送信することを含む
請求項1又は2に記載の通信制御方法。 - 前記ヘッダ情報を送信することは、前記ヘッダ圧縮処理が行われていない非圧縮MBSパケットを所定周期で送信することを含み、
前記非圧縮MBSパケットは、前記ヘッダ情報を含む
請求項1又は2に記載の通信制御方法。 - 基地局からユーザ装置に対してマルチキャスト・ブロードキャストサービス(MBS)を提供する移動通信システムで用いる通信制御方法であって、
前記ユーザ装置が、前記基地局からMBSパケットを受信することと、
前記ユーザ装置のPDCP(Packet Data Convergence Protocol)エンティティが、前記基地局から最初に受信したMBSパケットに含まれるPDCPシーケンス番号を、所定PDCP動作に用いる変数の初期値として設定することと、を有する
通信制御方法。 - 前記所定PDCP動作は、受信ウィンドウ制御及びパケット並び替え動作のうち少なくとも一方である
請求項5に記載の通信制御方法。 - 基地局からユーザ装置に対してマルチキャスト・ブロードキャストサービス(MBS)を提供する移動通信システムで用いる通信制御方法であって、
前記ユーザ装置が、前記基地局からMBSデータベアラを介してMBSパケットを受信することと、
前記ユーザ装置のSDAPレイヤが、前記MBSパケットにSDAP(Service Data Adaptation Protocol)ヘッダが付与されていないとみなすことにより、前記MBSパケットに対するSADPヘッダ除去処理を行わずに、前記MBSパケットを上位レイヤに渡すことと、を有する
通信制御方法。 - 前記ユーザ装置が、SDAPレイヤの設定に関する設定情報を前記基地局から受信することをさらに有し、
前記MBSパケットを前記上位レイヤに渡すことは、前記設定情報にかかわらず、前記SADPヘッダ除去処理を行わずに、前記MBSパケットを前記上位レイヤに渡すことを含む
請求項7に記載の通信制御方法。 - 基地局からユーザ装置に対してマルチキャスト・ブロードキャストサービス(MBS)を提供する移動通信システムで用いる通信制御方法であって、
前記基地局が、1つのMBSセッションに属する1つ又は複数のQoS(Quality of Service)フローを複数のMBSデータベアラにマッピングすることと、
前記基地局が、前記複数のMBSデータベアラに対応する複数の論理チャネルを1つのRNTIで多重して送信することと、を有する
通信制御方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202180084303.4A CN116803107A (zh) | 2020-10-19 | 2021-10-14 | 通信控制方法 |
EP21882714.5A EP4216578A4 (en) | 2020-10-19 | 2021-10-14 | COMMUNICATION CONTROL METHOD |
JP2022557465A JPWO2022085573A5 (ja) | 2021-10-14 | 通信制御方法、ユーザ装置及びプロセッサ | |
US18/303,400 US20230262518A1 (en) | 2020-10-19 | 2023-04-19 | Communication control method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202063093386P | 2020-10-19 | 2020-10-19 | |
US63/093,386 | 2020-10-19 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/303,400 Continuation US20230262518A1 (en) | 2020-10-19 | 2023-04-19 | Communication control method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022085573A1 true WO2022085573A1 (ja) | 2022-04-28 |
Family
ID=81290485
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/038145 WO2022085573A1 (ja) | 2020-10-19 | 2021-10-14 | 通信制御方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20230262518A1 (ja) |
EP (1) | EP4216578A4 (ja) |
CN (1) | CN116803107A (ja) |
WO (1) | WO2022085573A1 (ja) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004533152A (ja) * | 2001-03-28 | 2004-10-28 | クゥアルコム・インコーポレイテッド | 無線通信システムにおけるオーバーヘッドメッセージングのための方法および装置 |
WO2007111320A1 (ja) * | 2006-03-28 | 2007-10-04 | Ntt Docomo, Inc. | 移動通信システム、通信ノード、基地局及び方法 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20200034484A (ko) * | 2018-09-21 | 2020-03-31 | 삼성전자주식회사 | 무선 통신 시스템에서 데이터를 송수신하는 방법 및 장치 |
EP3903524B1 (en) * | 2019-03-27 | 2023-02-15 | Samsung Electronics Co., Ltd. | Method and apparatus for processing pdcp control data in system supporting high-reliability low-latency service |
-
2021
- 2021-10-14 EP EP21882714.5A patent/EP4216578A4/en active Pending
- 2021-10-14 CN CN202180084303.4A patent/CN116803107A/zh active Pending
- 2021-10-14 WO PCT/JP2021/038145 patent/WO2022085573A1/ja active Application Filing
-
2023
- 2023-04-19 US US18/303,400 patent/US20230262518A1/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004533152A (ja) * | 2001-03-28 | 2004-10-28 | クゥアルコム・インコーポレイテッド | 無線通信システムにおけるオーバーヘッドメッセージングのための方法および装置 |
WO2007111320A1 (ja) * | 2006-03-28 | 2007-10-04 | Ntt Docomo, Inc. | 移動通信システム、通信ノード、基地局及び方法 |
Non-Patent Citations (5)
Title |
---|
3GPP TS 38.300, September 2020 (2020-09-01) |
INTEL CORPORATION: "Consideration of L2 protocol impact by MBS", 3GPP TSG RAN WG2 #111-E; R2-2006952, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 7 August 2020 (2020-08-07), Electronic meeting; 20200817 - 20200828, XP051911811 * |
MEDIATEK INC.: "Overview on NR MBS Architecture", 3GPP TSG RAN WG2 #111-E; R2-2006574, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 7 August 2020 (2020-08-07), electronic; 20200817 - 20200828, XP051911517 * |
SAMSUNG: "On Stage-2 aspects and overview of NR MBS", 3GPP TSG RAN WG2 #111-E; R2-2007672, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. e-Meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), e-Meeting; 20200817 - 20200828e-Meeting; 20200817 - 20200828, XP051912301 * |
See also references of EP4216578A4 |
Also Published As
Publication number | Publication date |
---|---|
JPWO2022085573A1 (ja) | 2022-04-28 |
EP4216578A4 (en) | 2024-03-20 |
EP4216578A1 (en) | 2023-07-26 |
CN116803107A (zh) | 2023-09-22 |
US20230262518A1 (en) | 2023-08-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10448363B2 (en) | Base station, user terminal, and communication control method | |
US10476694B2 (en) | Base station and user terminal, for transmitting and receiving multicast data using semi-persistent scheduling | |
WO2022085717A1 (ja) | 通信制御方法 | |
US20240080939A1 (en) | Communication control method and user equipment | |
WO2022153991A1 (ja) | 通信制御方法 | |
US20230337327A1 (en) | Communication control method and user equipment | |
JP2023100957A (ja) | 通信制御方法、ユーザ装置及びプロセッサ | |
WO2022085573A1 (ja) | 通信制御方法 | |
WO2022085646A1 (ja) | 通信制御方法 | |
WO2023063323A1 (ja) | 通信方法、ユーザ装置、及び基地局 | |
WO2022234847A1 (ja) | 通信制御方法及びユーザ装置 | |
JP7425259B2 (ja) | 通信制御方法及び基地局 | |
WO2023013670A1 (ja) | 通信方法及びユーザ装置 | |
WO2022080230A1 (ja) | 通信制御方法 | |
WO2023063371A1 (ja) | 通信方法 | |
US20230188950A1 (en) | Communication control method | |
US20240080940A1 (en) | Communication control method | |
JP7502574B2 (ja) | 通信方法、ユーザ装置、プロセッサ、プログラム、及び移動通信システム | |
WO2022085644A1 (ja) | 通信制御方法 | |
EP4366332A1 (en) | Communications method, user device, and base station | |
WO2023074721A1 (ja) | 通信方法及びユーザ装置 | |
US20240179580A1 (en) | Communication method | |
WO2023074529A1 (ja) | 通信方法 | |
WO2023002988A1 (ja) | 通信方法 | |
US20240040662A1 (en) | Communication control method and user equipment |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21882714 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2022557465 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2021882714 Country of ref document: EP Effective date: 20230419 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180084303.4 Country of ref document: CN |