Communication control method, user device, processor, program, and mobile communication system

Enhanced RLC and PDCP operations in 5G systems address reliability and flexibility issues in multicast/broadcast services by optimizing RLC settings and PDCP processing, reducing errors and packet losses during handovers and initial reception.

JP2024167338AActive Publication Date: 2024-12-03KYOCERA CORP
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2024147833
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2020-08-03
Filing Date
2024-08-29
Publication Date
2024-12-03
Estimated Expiration
2041-08-02

AI Technical Summary

Technical Problem

Existing 5G mobile communication systems face challenges in providing reliable and flexible multicast/broadcast services due to limitations in Radio Link Control (RLC) and Packet Data Convergence Protocol (PDCP) operations, particularly during handovers and initial MBS data reception.

Method used

Implementing enhanced RLC and PDCP operations in 5G systems, including setting RLC entities to Acknowledged Mode (AM) for improved reliability and flexibility, and optimizing PDCP operations for MBS by performing duplicate packet discard, packet reordering, and sequence number management during handovers.

Benefits of technology

Enhances the reliability and flexibility of multicast/broadcast services by reducing burst errors and packet losses during initial reception and handovers, thereby improving the overall performance of MBS in 5G networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024167338000001_ABST
    Figure 2024167338000001_ABST
Patent Text Reader

Abstract

To provide a communication control method, a user device, and a processor that realize an improved multicast / broadcast service.SOLUTION: In 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, a base station gNB transmits a message to a user device UE that configures a Radio Link Control (RLC) entity of the user device, the message includes an information element that specifies an operation mode of the RLC entity for an MBS traffic channel that transmits MBS data.SELECTED DRAWING: Figure 8
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a communication control method, a user equipment, and a processor for use in a mobile communication system. [Background technology]

[0002] In recent years, the fifth generation (5G) mobile communication system has been attracting attention. NR (New Radio), the radio access technology (RAT) of the 5G system, has features such as high speed, large capacity, high reliability, and low latency compared to LTE (Long Term Evolution), the fourth generation radio access technology. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP technical specification "3GPP TS 38.300 V16.2.0 (2020-07)" Summary of the Invention

[0004] A communication control method according to a first aspect 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 equipment, and includes transmitting a message from the base station to the user equipment for configuring an RLC (Radio Link Control) entity of the user equipment, the message including an information element that specifies an operation mode of the RLC entity for an MBS traffic channel that transmits MBS data.

[0005] A communication control method according to a second aspect 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 includes the steps of the user device receiving MBS data from the base station and an RLC (Radio Link Control) entity of the user device setting a sequence number of the MBS data first received from the base station as an initial value of a variable to be used for a specified RLC operation.

[0006] A communication control method according to a third aspect 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, the method comprising: the user device receiving MBS data from the base station; and a Packet Data Convergence Protocol (PDCP) entity of the user device performing MBS reception processing on the MBS data, wherein performing the MBS reception processing includes the PDCP entity performing at least one of a duplicate packet discarding process and a packet reordering process without performing at least one of a decryption process and a header decompression process.

[0007] A communication control method according to a fourth aspect 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 includes the steps of: the user device receiving MBS data from a first cell; the user device performing a handover from the first cell to a second cell; and, if a PDCP (Packet Data Convergence Protocol) entity of the user device fails to receive the MBS data during the handover, transmitting a sequence number indicating the MBS data that was unsuccessfully received to the second cell. [Brief description of the drawings]

[0008] [Figure 1] 1 is a diagram showing a configuration of a mobile communication system according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing a configuration of a UE (user equipment) according to an embodiment. [Diagram 3] A diagram showing the configuration of a gNB (base station) according to an embodiment. [Figure 4] A diagram showing the configuration of a protocol stack of a wireless interface of a user plane that handles data. [Diagram 5] FIG. 2 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals). [Figure 6] FIG. 2 is a diagram illustrating a correspondence relationship between downlink logical channels and transport channels according to an embodiment. [Figure 7] FIG. 4 is a diagram illustrating an example of an operation according to the first embodiment. [Figure 8] FIG. 4 is a diagram showing a specific example of an operation according to the first embodiment. [Figure 9] FIG. 2 is a diagram illustrating an RLC operation according to the first embodiment. [Figure 10] FIG. 2 is a diagram illustrating an RLC operation of AM according to the first embodiment. [Figure 11] FIG. 2 is a diagram illustrating an RLC operation of a UM according to the first embodiment. [Figure 12] FIG. 11 is a diagram for explaining a PDCP operation mode according to the second embodiment. [Figure 13] FIG. 11 is a diagram for explaining a PDCP operation mode according to the second embodiment. [Figure 14] FIG. 11 is a diagram illustrating an example of PDCP operation according to the second embodiment. [Figure 15] FIG. 11 is a diagram showing a handover operation according to the second embodiment. [Figure 16] FIG. 11 is a diagram showing another example of the handover operation according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] The introduction of multicast and broadcast services to the 5G system (NR) is being considered. It is hoped that the NR multicast and broadcast services will provide improved services compared to the LTE multicast and broadcast services.

[0010] Therefore, an object of the present disclosure is to realize an improved multicast / broadcast service.

[0011] A mobile communication system according to an embodiment will be described with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0012] (Configuration of a mobile communication system) First, a configuration of a mobile communication system according to an embodiment will be described. 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). In the following, 5GS will be described as an example, but the LTE (Long Term Evolution) system may be applied at least in part to the mobile communication system.

[0013] As shown in FIG. 1, the mobile communication system includes a user equipment (UE) 100, a 5G radio access network (NG-RAN) 10, and a 5G core network (5GC) 20.

[0014] The UE 100 is a mobile wireless communication device. The UE 100 may be any device that is used by a user, and may be, for example, 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 a sensor, a vehicle or a device provided in a vehicle (Vehicle UE), or an aircraft or a device provided in an aircraft (Aerial UE).

[0015] The NG-RAN 10 includes a base station (called "gNB" in the 5G system) 200. The gNBs 200 are connected to each other via an 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 and scheduling, and the like. The term "cell" is used to indicate the smallest unit of a wireless communication area. The term "cell" is also used to indicate a function or resource for performing wireless communication with the UE 100. One cell belongs to one carrier frequency.

[0016] In addition, gNBs can also be connected to the Evolved Packet Core (EPC), which is the core network of LTE. LTE base stations can also be connected to 5GC. LTE base stations and gNBs can also be connected via an inter-base station interface.

[0017] The 5GC20 includes an Access and Mobility Management Function (AMF) and a User Plane Function (UPF) 300. The AMF performs various mobility controls for the UE 100. The AMF manages the mobility of the UE 100 by communicating with the UE 100 using Non-Access Stratum (NAS) signaling. The UPF controls data forwarding. The AMF and the UPF are connected to the gNB 200 via an NG interface, which is an interface between a base station and a core network.

[0018] FIG. 2 is a diagram showing a configuration of a UE 100 (user equipment) according to the embodiment.

[0019] As shown in FIG. 2, the UE 100 includes a receiving unit 110, a transmitting unit 120, and a control unit .

[0020] 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 a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 130.

[0021] The transmission unit 120 performs various transmissions under the control of the control unit 130. The transmission unit 120 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 130 into a radio signal and transmits it from the antenna.

[0022] The control unit 130 performs various controls in the UE 100. The control unit 130 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU (Central Processing Unit). The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processing.

[0023] FIG. 3 is a diagram showing the configuration of a gNB200 (base station) according to an embodiment.

[0024] As shown in FIG. 3, the gNB 200 includes a transmitter 210, a receiver 220, a control unit 230, and a backhaul communication unit 240.

[0025] The transmission unit 210 performs various transmissions under the control of the control unit 230. The transmission unit 210 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits it from the antenna.

[0026] 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 a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 230.

[0027] The control unit 230 performs various controls in the gNB 200. The control unit 230 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processing.

[0028] The backhaul communication unit 240 is connected to adjacent base stations via an inter-base station interface. The backhaul communication unit 240 is connected to the AMF / UPF 300 via a base station-core network interface. Note that the gNB is composed of a CU (Central Unit) and a DU (Distributed Unit) (i.e., the functions are divided), and both units may be connected to each other via an F1 interface.

[0029] FIG. 4 is a diagram showing the configuration of a protocol stack of a radio interface of a user plane that handles data.

[0030] As shown in FIG. 4, the user plane radio interface protocol includes a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer.

[0031] The PHY layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the PHY layer of the UE 100 and the PHY layer of the gNB 200 via a physical channel.

[0032] The MAC layer performs data priority control, retransmission processing using hybrid ARQ (HARQ), random access procedures, etc. Data and control information are transmitted between the MAC layer of the UE 100 and the MAC layer of the gNB 200 via a transport channel. The MAC layer of the gNB 200 includes a scheduler. The scheduler determines the uplink and downlink transport format (transport block size, modulation and coding scheme (MCS)) and the resource blocks to be assigned to the UE 100.

[0033] The RLC layer transmits data to the RLC layer on the receiving side 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.

[0034] The PDCP layer performs header compression / decompression and encryption / decryption.

[0035] The SDAP layer maps IP flows, which are the units for QoS control by the core network, to radio bearers, which are the units for QoS control by the AS (Access Stratum). Note that if the RAN is connected to the EPC, the SDAP is not necessary.

[0036] FIG. 5 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals).

[0037] As shown in FIG. 5, the protocol stack of the radio interface of the control plane has a Radio Resource Control (RRC) layer and a Non-Access Stratum (NAS) layer instead of the SDAP layer shown in FIG.

[0038] Between the RRC layer of the UE 100 and the RRC layer of the gNB 200, RRC signaling for various settings is transmitted. The RRC layer controls logical channels, transport channels, and physical channels according to the establishment, re-establishment, and release of radio bearers. When there is a connection (RRC connection) between the RRC of the UE 100 and the RRC of the gNB 200, the UE 100 is in an RRC connected state. When there is no connection (RRC connection) between the RRC of the UE 100 and the RRC of the gNB 200, the UE 100 is in an RRC idle state. When the connection between the RRC of the UE 100 and the RRC of the gNB 200 is suspended, the UE 100 is in an RRC inactive state.

[0039] The NAS layer, which is 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 AMF 300.

[0040] In addition, the UE 100 has an application layer and the like in addition to the protocol of the radio interface.

[0041] (MBS) Next, the MBS according to the embodiment will be described. The MBS is a service for broadcasting or multicasting, that is, transmitting data from the NG-RAN 10 to the UE 100 in a one-to-many (PTM: Point To Multipoint) manner. The MBS may be called an MBMS (Multimedia Broadcast and Multicast Service). Note that use cases (service types) of the MBS include public safety communication, mission critical communication, V2X (Vehicle to Everything) communication, IPv4 or IPv6 multicast distribution, IPTV, group communication, and software distribution.

[0042] There are two types of MBS transmission methods in LTE: MBSFN (Multicast Broadcast Single Frequency Network) transmission and SC-PTM (Single Cell Point To Multipoint) transmission. Fig. 6 is a diagram showing a correspondence relationship between downlink logical channels and transport channels according to the embodiment.

[0043] As shown in Figure 6, 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 designed mainly for multi-cell transmission, and in an MBSFN area consisting of multiple cells, each cell synchronously transmits the same signal (same data) in the same MBSFN subframe.

[0044] The logical channels used for SC-PTM transmission are the Single Cell Multicast Traffic Channel (SC-MTCH) and the Single Cell Multicast Control Channel (SC-MCCH), and the transport channel used for SC-PTM transmission is the Downlink Shared Channel (DL-SCH). SC-PTM transmission is designed primarily for single-cell transmission, and transmits data by broadcast or multicast on a cell-by-cell basis. The physical channels used for SC-PTM transmission are the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH), which enable dynamic resource allocation.

[0045] In the following, an example in which an MBS is provided using the SC-PTM transmission method will be mainly described, but an MBS may also be provided using the MBSFN transmission method. Also, an example in which an MBS is provided by multicast will be mainly described. Therefore, MBS may be read as multicast. However, an MBS may also be provided by broadcast.

[0046] In the following, MBS data refers to data transmitted by the MBS, the MBS control channel refers to the MCCH or SC-MCCH, and the MBS traffic channel refers to the MTCH or SC-MTCH.

[0047] The network can provide different MBS services for each MBS session. The MBS services are identified by at least one of a Temporary Mobile Group Identity (TMGI) and a session identifier, and at least one of these identifiers is called an MBS service identifier. Such an MBS service identifier may be called an MBS session identifier or a multicast group identifier.

[0048] (First embodiment) Next, a first embodiment will be described on the premise of the above-mentioned mobile communication system and MBS. The first embodiment is an embodiment related to an RLC operation for the MBS.

[0049] (1) RLC setting operation for MBS There are three operation modes for the RLC layer: AM (Acknowledged Mode), UM (Unacknowledged Mode), and TM (Transparent Mode). Of these modes, only AM supports the retransmission function using Automatic Repeat reQuest (ARQ). AM is a mode in which retransmission control is performed by sending ACK feedback from the receiving RLC entity to the transmitting RLC entity.

[0050] In LTE multicast services, the operation mode of the RLC entity is set to UM. However, if a mechanism that enables AM to be applied to NR multicast services could be realized, it is believed that the reliability and flexibility of multicast communication can be improved.

[0051] FIG. 7 is a diagram illustrating an example of the operation according to the first embodiment.

[0052] 7, a UE 100a in an RRC connected state and a UE 100b in an RRC idle state exist in a cell C managed by the gNB 200. It is assumed that the UE 100a and the UE 100b are interested in receiving MBS data belonging to the same MBS service (the same MBS session).

[0053] The gNB 200 transmits a message (hereinafter referred to as a "configuration message") for configuring the RLC entity of the UE 100. The configuration message includes an information element (hereinafter referred to as "RLC configuration information") that specifies an operation mode of the RLC entity for the MBS traffic channel that transmits MBS data.

[0054] The RLC configuration information specifies, as an operation mode of the RLC entity, either a first mode (i.e., AM) in which automatic retransmission control is performed or a second mode in which automatic retransmission control is not performed. The second mode is UM or TM, but the following mainly describes an example in which the second mode is UM.

[0055] For example, the gNB 200 transmits a configuration message by broadcast. Each of the UE 100a in the RRC connected state and the UE 100b in the RRC idle state receives the configuration message. By transmitting the configuration message by broadcast, the UE 100b in the RRC idle state can also receive the configuration message.

[0056] For example, the configuration message may be MBS system information transmitted via a Broadcast Control Channel (BCCH).The configuration message may be MBS control information transmitted via an MBS control channel.

[0057] Alternatively, the configuration message may be UE-specific signaling. For example, the configuration message may be an RRC Reconfiguration message, which is a type of RRC message. Such UE-specific signaling and broadcast signaling may be used in combination.

[0058] In this case, the setting contents broadcast in the MBS system information or the MBS control channel may be different from the setting contents in the dedicated signaling. However, the UE 100 receiving the dedicated signaling (specifically, the UE 100a in the RRC connected state) applies the dedicated signaling with priority over the broadcast signaling. This enables a setting such as feedback permission (AM) for a certain UE 100 and feedback not permission (UM) for other UEs 100.

[0059] The configuration message may include an identifier associated with the RLC configuration information. This identifier is an identifier for identifying an MBS traffic channel, for example, an MBS service identifier and / or a group RNTI (Radio Network Temporary Identifier). This allows the operation mode of the RLC entity to be specified for each MBS traffic channel. In the following, an example in which an MBS service identifier (for example, TMGI) is used as such an identifier will be mainly described.

[0060] The configuration message may include multiple sets of RLC configuration information and MBS service identifiers. For example, in the configuration message, MBS service identifier #1 may be associated with RLC configuration information specifying AM, and MBS service identifier #2 may be associated with RLC configuration information specifying UM.

[0061] In the first embodiment, when the UE 100 is in the RRC connected state, the UE 100 may set the operation mode of the RLC entity according to the RLC setting information included in the setting message. When the UE 100 is in the RRC idle state or the RRC inactive state, the UE 100 may set the second mode (UM) regardless of the RLC setting information included in the setting message. The UE 100 in the RRC idle state or the RRC inactive state cannot transmit ACK / NACK feedback (STATUS PDU) to the gNB 200, so it is assumed that the UE 100 is operated in the second mode (UM).

[0062] However, in the gNB 200, the RLC entity associated with the MBS traffic channel operates in AM. Therefore, the UE 100b having the RLC entity of UM needs to be able to process AM packets (AMD PDU) from the gNB 200. Therefore, the gNB 200 may limit the sequence number length used in AM to a setting that matches the sequence number length existing in UM. For example, the sequence number length used in AM may be set to 12 bits, which is the maximum sequence number length existing in UM. Alternatively, the sequence number length of a UM packet (UMD PDU) may be extended to 18 bits.

[0063] After the operation mode of the RLC entity of each UE 100 is set by the configuration message, the gNB 200 transmits MBS data via the MBS traffic channel. Each UE 100 receives the MBS data.

[0064] FIG. 8 is a diagram showing a specific example of the operation according to the first embodiment.

[0065] 8, in step S101, the gNB 200 transmits a configuration message. Here, it is assumed that the configuration message is transmitted on a broadcast control channel or an MBS control channel. The UE 100 receives the configuration message.

[0066] When UE 100 receives the configuration message, if it is in an RRC connected state (step S102: YES) and if AM is specified in the configuration message (step S103: YES), it configures an AM RLC entity (AM RLC entity) for the MBS traffic channel in step S104.

[0067] On the other hand, if UE 100 receives the configuration message and is not in an RRC connected state (step S102: NO) or if UM is specified in the configuration message (step S103: NO), then in step S106, UE 100 configures a UM RLC entity (UM RLC entity) for the MBS traffic channel.

[0068] In step S106, the gNB 200 transmits the MBS data via the MBS traffic channel. The UE 100 receives the MBS data. Here, the RLC entity of the UE 100 processes a packet (AMD PDU) corresponding to the MBS data.

[0069] Although an example has been described in which the second mode in which automatic retransmission control is not performed is UM, the second mode may be a newly defined RLC operation mode. Such an RLC operation mode is an operation mode in which AMD PDUs can be received but feedback-related operations (e.g., polling for ARQ and Status Reporting) are not performed. When AM is specified by broadcast signaling, the RLC entity of the UE 100 in the RRC idle state or the RRC inactive state may operate in such a new RLC operation mode.

[0070] (2) RLC operation for MBS Next, the RLC operation for MBS according to the first embodiment will be described. The receiving RLC entity performs reception processing using a sliding window that moves according to the reception of an RLC packet. Such a sliding window is controlled by each variable of the RLC entity.

[0071] Each variable used for such sliding window control is initialized when an RLC entity is established or re-established. The sequence number corresponding to the initial value is basically "0", and the initial position of the sliding window is determined based on this. In the case of unicast communication, the UE 100 can first receive an RLC packet with sequence number "0" from the gNB 200, so there is no problem with handling such variables.

[0072] However, in the case of MBS, UE 100 can join in the middle of an MBS session, and it is uncertain which sequence number UE 100 will receive first. Therefore, the first received packet may be outside the sliding window. In this case, RLC reception processing cannot be performed until the subsequent packet enters the sliding window. Therefore, a burst error may occur at the beginning of MBS reception.

[0073] Therefore, the RLC entity of the UE 100 changes the above-mentioned variables to match the sequence number of the first received RLC packet. Fig. 9 is a diagram showing an RLC operation according to the first embodiment.

[0074] As shown in FIG. 9, in step S201, the RLC entity of UE100 receives MBS data (RLC packet) from gNB200.

[0075] In step S202, the RLC entity of UE100 sets the sequence number of the MBS data (RLC packet) first received from gNB200 as the initial value of a variable used for a predetermined RLC operation (e.g., sliding window control).

[0076] This ensures that the first received packet falls within the sliding window, and the RLC reception process works normally, reducing the possibility of a burst error occurring at the beginning of MBS reception.

[0077] FIG. 10 is a diagram showing an RLC operation of the AM according to the first embodiment. As shown in FIG. 10, the AM RLC entity of the UE 100 manages a receiving window, which is a type of sliding window. The AM RLC entity of the UE 100 temporarily stores packets received within the receiving window in a receiving buffer, reassembles the packets, and passes them to a higher layer. The AM RLC entity of the UE 100 discards packets having a sequence number (SN) outside the receiving window. The size of the receiving window is determined according to the sequence number length. A variable that determines the start point of such a receiving window is called "RX_Next". The AM RLC entity of the UE 100 sets the sequence number of the MBS data (RLC packet) first received from the gNB 200 as the initial value of the variable "RX_Next".

[0078] FIG. 11 is a diagram showing the RLC operation of the UM according to the first embodiment. As shown in FIG. 11, the UM RLC entity of the UE 100 manages a reassembly window, which is a type of sliding window, and a window used for discarding packets (herein referred to as a Discard window). The UM RLC entity of the UE 100 reassembles packets having sequence numbers within the Reassembly window and outside the Discard window in a reception buffer, and passes them to a higher layer. Packets having other sequence numbers are discarded. Such a variable that determines the end point of the Reassembly window is called "RX_Next_Highest". The UM RLC entity of the UE 100 sets the sequence number of the MBS data (RLC packet) first received from the gNB 200 as the initial value of the variable "RX_Next_Highest".

[0079] Second embodiment Next, the second embodiment will be described, focusing mainly on the differences from the first embodiment. The second embodiment is an embodiment related to PDCP operation for MBS.

[0080] (1) PDCP operation for MBS PDCP entities are not used in LTE multicast and broadcast services. However, handover is expected to be supported in NR MBS, and it is desirable for the PDCP entity to be able to compensate for packet loss during handover. In addition, a PDCP entity is required when applying PDCP duplication, in which the PDCP entity transmits the same PDCP packet twice over two paths, to MBS.

[0081] Here, in the case of multicast, for example, when UE 100 that has joined communication halfway through an MBS session performs the next PDCP reception operation, there is a risk that the packet cannot be processed normally.

[0082] Header Decompression PDCP header compression achieves header compression (IP header compression, etc.) by first storing the upper layer header (IP header, etc.) of the packet received by the receiving PDCP entity, then the transmitting PDCP entity removes the header from the second packet and transmits it, combines the header stored in the receiving PDCP entity, and passes it to the upper entity. For this reason, UE 100 that joined the MBS session midway through has not received the first packet, and therefore cannot decompress the header (i.e., play the packet).

[0083] De-ciphering If a PDCP packet is encrypted, decryption (decryption) is not possible without information such as a key and a sequence number derived from a UE identifier, etc. For example, a UE 100 that joins an MBS session midway through cannot decrypt the packet because it does not have the information necessary for decryption.

[0084] On the other hand, when multiple bearers (i.e., multiple data paths) are terminated by one PDCP entity, such as in PDCP duplication, the following PDCP receiving operation may be required.

[0085] -Duplicate discarding When duplicate PDCP packets (i.e., multiple PDCP packets with the same sequence number) are received via multiple bearers, the packets must be discarded to avoid duplication. Specifically, the receiving PDCP entity passes all but one of the multiple PDCP packets with the same sequence number to the upper layer and discards the other PDCP packets.

[0086] Packet reordering If the receiving PDCP entity does not receive PDCP packets in the order of their sequence numbers, it must reorder the PDCP packets before passing them to the upper layer. However, in the case of a UM bearer, packet reordering is not required.

[0087] Therefore, in the second embodiment, a receiving PDCP entity that receives PDCP packets via multiple bearers including a bearer for an MBS service performs a PDCP reception operation for MBS reception. Specifically, in the PDCP reception operation for MBS reception, the receiving PDCP entity performs at least one of a duplicate packet discard process and a packet reordering process without performing at least one of a descrambling process and a header decompression process. The receiving PDCP entity may also remove the PDCP header.

[0088] 12 and 13 are diagrams for explaining PDCP operation modes according to the second embodiment. In the second embodiment, the PDCP entity operates in one of three operation modes.

[0089] As shown in Fig. 12, mode A is a mode applied to bearers of user data other than MBS data (e.g., unicast data). In mode A, the transmitting PDCP entity performs sequence number assignment, header compression, encryption, PDCP header assignment, and routing / duplication on packets from an upper layer. The receiving PDCP entity performs PDCP header removal, decryption, packet reordering, duplicate packet discarding, and header decompression on packets from the transmitting PDCP entity.

[0090] Mode B is applied to the bearer of control data such as RRC messages. In Mode B, the transmitting PDCP entity performs sequence number assignment, header compression, PDCP header assignment, and routing / duplication for packets from the upper layer. The receiving PDCP entity performs PDCP header removal and header decompression for packets from the transmitting PDCP entity.

[0091] As shown in Fig. 13, Mode C is a mode applied to a bearer of MBS data (MBS bearer). In Mode C, the transmitting PDCP entity performs sequence number assignment, PDCP header assignment, and routing / duplication processing on packets from an upper layer. The receiving PDCP entity performs PDCP header removal, packet reordering, and duplicate packet discarding on packets from the transmitting PDCP entity.

[0092] For MBS, the gNB 200 configures the UE 100 so that the PDCP entity of the UE 100 operates in mode C. For example, the gNB 200 transmits an RRC message (e.g., an RRC Reconfiguration message) to the UE 100 for setting up a bearer.

[0093] Here, the gNB 200 includes in the configuration information an information element indicating that the bearer is a bearer for MBS (MBS bearer). For example, an information element such as "multicast-bearer ENUM(true) optional" is added to each bearer configuration in the RRC message.

[0094] When the UE 100 receives such an RRC message from the gNB 200, the UE 100 generates a PDCP entity for MBS operating in mode C. The PDCP entity for MBS performs MBS reception processing on MBS data belonging to the MBS bearer.

[0095] FIG. 14 is a diagram illustrating an example of the PDCP operation according to the second embodiment.

[0096] 14, in step S301, the PDCP entity of the UE 100 receives MBS data (PDCP packets) from the gNB 200. Here, it is assumed that the PDCP entity of the gNB 200 has not performed header compression processing and encryption processing on PDCP packets belonging to an MBS service (MBS session).

[0097] In step S302, the PDCP entity of the UE 100 removes the PDCP header from the received PDCP packet, and then performs a duplicate packet discard process and / or a packet reorder process using the reception buffer. However, the PDCP entity of the UE 100 does not perform a header decompression process and a descrambling process on the received PDCP packet.

[0098] (2) PDCP operation during handover during MBS reception Next, a PDCP operation at the time of handover during MBS reception according to the second embodiment will be described. UE 100 may execute handover during MBS reception. Handover refers to a cell switching operation of UE 100 in an RRC connected state. In the following, it is mainly assumed that each cell before and after handover (i.e., source cell and target cell) provides the same MBS service (same MBS session).

[0099] If the UE 100 executes handover while receiving an MBS, there is a risk that packets of the MBS data may be lost due to a connection operation to a target cell, etc. The PDCP layer has a function of retransmitting PDCP packets based on feedback (status report) from the UE 100 to the gNB 200. In the second embodiment, the retransmission function of the PDCP layer makes it possible to compensate for packet losses at the time of handover during MBS reception in the target cell.

[0100] Fig. 15 is a diagram showing a handover operation according to the second embodiment. Fig. 15 shows an example in which a source cell C1 and a target cell C2 are managed by one gNB 200.

[0101] 15, UE 100 in the RRC connected state performs handover from the source cell C1 to the target cell C2 while receiving MBS data from the source cell C1. Here, if the PDCP entity of UE 100 fails to receive the MBS data during handover, it transmits a sequence number (specifically, a PDCP sequence number) indicating the MBS data (PDCP packet) that has failed to be received to the target cell C2 after the handover.

[0102] When a handover command is set from the source cell C1 (when the RRC layer requests PDCP re-establishment), the PDCP entity of the UE 100 transmits the sequence number of the missing packet to the target cell C2 after the PDCP re-establishment process is completed. The UE 100 may further transmit an MBS service identifier associated with the sequence number of the missing packet to the target cell C2. The PDCP entity of the UE 100 may transmit a status report message of the PDCP layer to the target cell C2 by including a sequence number indicating the MBS data that has failed to be received (i.e., the missing PDCP packet) in the status report message.

[0103] When the gNB 200 receives the sequence number of a missing packet from the UE 100 via the target cell C2, the gNB 200 transmits (resends) the missing packet to the UE 100 via the target cell C2 based on the sequence number. This allows the target cell C2 to compensate for packet losses at the time of handover during MBS reception by using the retransmission function of the PDCP layer, thereby improving the reliability of MBS reception.

[0104] Fig. 16 is a diagram showing another example of the handover operation according to the second embodiment. Fig. 15 shows an example in which the source cell C1 and the target cell C2 are managed by different gNBs 200 (gNB 200A and gNB 200B).

[0105] In the operating environment shown in Fig. 16, it is assumed that the source cell C1 and the target cell C2 provide MBS services asynchronously. That is, the target cell C2 does not provide the MBS service (MBS session) provided by the target cell C1.

[0106] In such a case, even if the gNB 200B that manages the target cell C2 receives the sequence number of the missing packet from the UE 100, the gNB 200B does not hold the missing packet. Therefore, the gNB 200B notifies the gNB 200A that manages the source cell C1 of the missing sequence number (and the MBS service identifier). The gNB 200A forwards the missing packet (PDCP packet) to the gNB 200B based on the notification from the gNB 200B (data forwarding). The gNB 200B transmits the PDCP packet from the gNB 200A to the UE 100.

[0107] (Other embodiments) The above-described embodiments are not limited to being implemented separately and independently, but can be implemented in combination of two or more embodiments.

[0108] A program may be provided that causes a computer to execute each process performed by the UE 100 or the gNB 200. The program may be recorded in a computer-readable medium. Using the computer-readable medium, it is possible to install the program in the computer. Here, 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, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.

[0109] In addition, circuits that execute each process performed by UE100 or gNB200 may be integrated, and at least a part of UE100 or gNB200 may be configured as a semiconductor integrated circuit (chip set, SoC).

[0110] The above describes the embodiments in detail with reference to the drawings, but the specific configuration is not limited to that described above, and various design changes, etc. are possible without departing from the spirit of the invention.

[0111] This application claims priority to Japanese Patent Application No. 2020-132044 (filed August 3, 2020), the entire contents of which are incorporated herein by reference.

Claims

1. A communication control method for use in a mobile communication system that provides a multicast and broadcast service (MBS) from a network node to a user device, comprising: said user equipment receiving MBS data from said network node; A packet data convergence protocol (PDCP) entity of the user equipment performs an MBS reception process on the MBS data; The performing of the MBS reception process includes performing at least one of a duplicate packet discard process and a packet reordering process by the PDCP entity without performing a descrambling process by the PDCP entity. Communications control method.

2. A user device, a receiver for receiving Multicast and Broadcast Service (MBS) data from a network node; A control unit including a Packet Data Convergence Protocol (PDCP) entity that performs MBS reception processing on the MBS data, In the MBS reception process, the PDCP entity does not perform a descrambling process, but performs at least one of a duplicate packet discard process and a packet reordering process. User equipment.

3. A method for carrying out the communication method according to claim 1, Processor.

4. A method for causing a user device to execute the communication method according to claim 1. program.

5. The user equipment according to claim 2 and a network node. Mobile communication system.

Citation Information

Patent Citations

  • User device and duplicate packet processing method

    JP2016092700A

  • Method and apparatus for indicating ciphering instructions for sidelink radio bearer in d2d communication system

    JP2017538383A

  • Base station

    JP2019134476A

  • Handling Packet Data Convergence Protocol Data Units

    US20130242859A1