Header compression state handling in multicast-broadcast service, MBS, provision

By dynamically transitioning to an initialization state for context establishment and then compressing headers, the method addresses the challenge of new devices joining multicast-broadcast services, ensuring efficient and reliable header compression and reducing packet drops.

WO2024235452A1PCT designated stage expired Publication Date: 2024-11-21TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2023/063109
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-16
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In multicast-broadcast services, existing header compression technologies face challenges when new wireless communication devices join or are handed over during ongoing sessions, leading to packet drops and inefficiencies due to the lack of context establishment between compressors and decompressors.

Method used

A method where a device dynamically transitions to an initialization state for data header compression upon receiving an alert, sending initialization data headers to establish context with new and existing devices, and then switches to a compression state for sending compressed headers, allowing for efficient context establishment and minimizing packet drops.

Benefits of technology

This approach ensures reliable and efficient data header compression for multiple wireless communication devices, reducing packet drops and enabling reliable communication even in delay-sensitive and mission-critical scenarios like mission-critical push-to-talk technologies.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2023063109_21112024_PF_FP_ABST
    Figure EP2023063109_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a method of a device (12) configured to control data header compression to a plurality of wireless communication devices (17a-17c) in a multicast-broadcast service (MBS) session, and a device (12) performing the method. Further disclosed is a computer program (112) and a computer program product. In an aspect, a method of a device (12) configured to control data header compression to a plurality of wireless communication devices (17a, 17b) in an MBS session is provided. The method comprises receiving (S101) an alert that a further wireless communication device (17c) requests to join the MBS session, transitioning (S102), in response to the alert, to an initialization state (20) of the data header compression for sending initialization data headers to the further joining wireless communication device (17c) and the plurality of wireless communication devices (17a, 17b) already participating in the MBS session, in order to establish a context between a compressor with which the device (12) is associated and a decompressor of each of the wireless communication devices (17a, 17, 17c); and upon the context being established: transitioning (S103) to a compression state (21, 22) of the data header compression for sending compressed data headers to the wireless communication devices (17a, 17b) and the further joining wireless communication device (17c) participating in the MBS session.
Need to check novelty before this filing date? Find Prior Art

Description

HEADER COMPRESSION STATE HANDLING IN MULTICAST-BROADCAST SERVICE, MBS, PROVISIONTECHNICAL FIELD

[0001] The present disclosure relates to a method of a device configured to control data header compression to a plurality of wireless communication devices in a multicast -broadcast service (MBS) session, and a device performing the method. Further disclosed is a computer program and a computer program product.BACKGROUND

[0002] Robust header compression (ROHC) has been standardized in IETF (“Internet Engineering Task Force”) and provides a means to reduce amount of data required to be sent over a link to a recipient by reducing a part of a data header which either is the same, which predictably changes, or which seldomly changes.

[0003] In the ROHC approach, different states are defined which controls a level of compression being applied at a compressor of the sender when sending packets and how to handle the received packets in a decompressor at the recipient.

[0004] Initially, the packets are sent uncompressed to establish a so-called context between the compressor and decompressor, and once the context has been established, the packets can be sent fully compressed.

[0005] However, this approach is problematic upon new recipients requesting to receive data in an ongoing multicast-broadcast service (MBS) session, or being handed over from a neighbouring radio base station, and there is thus room for improvement.SUMMARY

[0006] One objective is to provide an improved method of controlling data header compression to a plurality of wireless communication devices in an MBS session.

[0007] This objective is attained in a first aspect by a method of a device configured to control data header compression to a plurality of wireless communication devices in an MBS session. The method comprises receiving an alertthat a further wireless communication device requests to join the MBS session, transitioning, in response to the alert, to an initialization state of the data header compression for sending initialization data headers to the further joining wireless communication device and the plurality of wireless communication devices already participating in the MBS session, in order to establish a context between a compressor with which the device is associated and a decompressor of each of the wireless communication devices; and upon the context being established transitioning to a compression state of the data header compression for sending compressed data headers to the wireless communication devices and the further joining wireless communication device participating in the MBS session.

[0008] This objective is attained in a second aspect by a device configured to control data header compression to a plurality of wireless communication devices in an MBS session. The device comprises a processing unit and a memory, said memory containing instructions executable by said processing unit, whereby the device is operative to receiving an alert that a further wireless communication device requests to join the MBS session, transitioning, in response to the alert, to an initialization state of the data header compression for sending initialization data headers to the further joining wireless communication device and the plurality of wireless communication devices already participating in the MBS session, in order to establish a context between a compressor with which the device is associated and a decompressor of each of the wireless communication devices; and upon the context being established transitioning to a compression state of the data header compression for sending compressed data headers to the wireless communication devices and the further joining wireless communication device participating in the MBS session.

[0009] This embodiment proposes an advantageous solution where a device of a radio base station dynamically can fall back to an initialization and refresh state upon performing ROHC and start to send initialization data, such as ROHC initialization and refresh packet data headers for allowing establishment of context at the wireless communication devices when a new wireless communication devices enters the MBS session, and the benefit of ROHC or other appropriate header compression technologies such as e.g. Ethernet header compression (EHC) in which embodiments may be implemented can thus be taken advantage of upon performing an MBS. As is understood, the wireless communication device may stablish directcommunication with the radio base station, or be handed over from a neighbouring base station.

[0010] In an embodiment, the alert is configured to be received from a control plane device (11).

[0011] In an embodiment, the device configured to control data header compression is a central unit-user plane (CU-UP) device and the control plane device providing the alert is a central unit-control plane (CU-CP) device.

[0012] In an embodiment, the alert is configured to comprise an identifier of an established MBS radio bearer (MRB) over which the MBS session is setup in order for the device to transition to the initialization state for the identified MRB.

[0013] In an embodiment, the alert is received in an MC BEARER CONTEXT MODIFICATION REQUEST message being modified to comprise the identifier of the MRB and an instruction to transition to the initialization state for the identified MRB.

[0014] In an embodiment, the alert is configured to be received from a user plane device.

[0015] In an embodiment, the device configured to control data header compression is a CU-UP device and the user plane device providing the alert is a distributed unit (DU) device.

[0016] In an embodiment, the alert is configured to comprise an identifier of an established MRB over which the MBS session is setup in order for the device to transition to the initialization state for the identified MRB.

[0017] In an embodiment, the alert is received in an ASSISTANCE INFORMATION DATA message being modified to comprise the identifier of the MRB.

[0018] In an embodiment, the alert is received in an ASSISTANCE INFORMATION DATA message being modified to comprise the identifier of the MRB and an instruction to transition to the initialization state for the identified MRB, in case the further wireless communication device requesting to join the MBS session already has been configured with the MRB for the MBS session.

[0019] In an embodiment, the method further comprises initiating a timer after transitioning to the initialization state, determining, after the timer has expired, ifone or more further alerts are received that a further wireless communication device requests to join the MBS session; and if not transitioning to the compression state of the data header compression for sending compressed data headers.

[0020] In an embodiment, the method further comprises re-transitioning to the compression state of the data header compression for sending compressed data headers.

[0021] In an embodiment, the determining, after the timer has expired, if one or more further alerts are received that a further wireless communication device requests to join the MBS session further comprises determining that one or more further alerts have been received before the expiry of the timer.

[0022] In a third aspect, a computer program is provided comprising computerexecutable instructions for causing a device to perform steps recited in the method of the first aspect when the computer-executable instructions are executed on a processing unit included in the device.

[0023] In a fourth aspect, a computer program product is provided comprising a computer readable medium, the computer readable medium having the computer program according to the third aspect embodied thereon.

[0024] Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a / an / the element, apparatus, component, means, step, etc." are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Aspects and embodiments are now described, by way of example, with reference to the accompanying drawings, in which:

[0026] Figure 1 illustrates a device in the form of a radio base station in which embodiment may be implemented;

[0027] Figure 2 illustrates prior art unidirectional mode compressor state transitions in ROHC;

[0028] Figure 3 shows a flowchart illustrating a method according to an embodiment;

[0029] Figure 4 illustrates modified unidirectional mode compressor state transitions in ROHC according to an embodiment;

[0030] Figure 5 shows a signalling diagram illustrating a method according to an embodiment;

[0031] Figure 6 shows a signalling diagram illustrating a method according to another embodiment;

[0032] Figure 7 shows a signalling diagram illustrating a method according to a further embodiment;

[0033] Figure 8 illustrates setting of a timer according to an embodiment;

[0034] Figure 9 illustrates a device according to an embodiment; and

[0035] Figure 10 illustrates a network in the form of an Open RAN (O-RAN), in which embodiments may be implemented.DETAILED DESCRIPTION

[0036] The aspects of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the invention are shown.

[0037] These aspects may, however, be embodied in many different forms and should not be construed as limiting; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and to fully convey the scope of all aspects of invention to those skilled in the art. Like numbers refer to like elements throughout the description.

[0038] In ROHC, three different modes have been defined in communication between devices such as communication between a radio base station - commonly referred to as a so-called gNodeB (gNB) in 5thgeneration (5G) communication systems - and a wireless communication device referred to as a User Equipment (UE) typically embodied in the form of a smart phone, a tablet, a connected vehicle, etc.

[0039] The three modes in ROHC comprises Unidirectional mode (U-mode), Bidirectional Optimistic mode (0-mode) and Bidirectional Reliable mode (R-mode).Within ROHC, it is also defined when and how to transition between the different modes.

[0040] In addition, within each of the three modes, different states are defined which controls a degree of compression being used when sending packets and how to handle received packets in the decompressor at the receiving side.

[0041] In U-mode, the data packets are sent from the compressor of the sender (i.e. the gNB) to the decompressor of the recipient (i.e. the UE) without any feedback from the decompressor. This mode is typically used when no return path is available, or when handling of feedback is not desired. Further, any ROHC compression must start in U-mode.

[0042] The transition to a state with higher degree of compression in U-mode requires several data packet transmissions to assure that the decompressor of the recipient has received enough information to continue in the higher compression state (called an optimistic approach), while transition to a state with a lower degree of compression is controlled by periodic timers and when irregularities are detected.

[0043] During the lifetime of the ROHC session, transition back to states using a lower degree of compression may be required for instance if the context is out-of-sync between the compressor and decompressor.

[0044] ROHC is an important feature in wireless communication systems where e.g. radio access network (RAN) capacity and air interface resources are limited. For instance, a common service using ROHC is Voice over New Radio (VoNR). An Internet Protocol (IP), User Datagram Protocol (UDP) and Real-time Transport Protocol (RTP) header in IPv4 has a size of 40 bytes and a size of 60 bytes in IPv6, and can be compressed to 1 and 3 bytes, respectively, by using ROHC.

[0045] When applying ROHC in a multiple receiver scenario, only U-mode is typically utilized with unidirectional links being setup to the respective receiver.

[0046] Figure 1 illustrates a gNB 10 in a 5G communication system. The gNB 10 comprises a central unit (CU) being split into a CU-CP 11 (“control plane”) and a CU- UP 12 (“user plane”) being connected over an El interface.

[0047] The CU-CP 11 connects to an access and mobility management function (AMF, not shown) of a core network 13 over interface N2 carrying control plane signalling while the CU-UP 12 connects to a data network 14, such as the Internet, viaan N3mb interface and a multicast / broadcast user plane function 15 (UPF) for transporting user data.

[0048] The Nsmb interface is used in case a multicast / broadcast service (MBS) session is set up where data is sent to a plurality of UEs 173-170. If only a single UE is to receive data, an alternative interface N3 (not shown) is utilized by the CU-UP 12 for transporting data over an UPF to the data network 14.

[0049] Further, the CU-CP 11 connects to a distributed unit 16 (DU) via interface Fi-C and further to one or more UEs iya-c via interface Uu, while the CU-UP 12 connects to the DU 16 via interface Fi-U (and further on to the UEs iya-c via interface Uu).

[0050] The ROHC framework is part of the Packet Data Convergence Protocol (PDCP) protocol which is managed by the CU-UP 12 and communicates with a corresponding PCPD entity in the UEs iya-c. A PDCP instance for an MBS session may be connected to several DUs and each DU may have several user plane connections over Fi-U, each carrying the same packet data unit (PDU) being compressed using ROHC.

[0051] ROHC with multiple receiving UEs may be handled by providing configuration information to the ROHC decompressor of a UE via unicast before the actual broadcast data is sent. The benefit of such approach is that when a new UE enters the broadcast session, for instance a third UE 17c, only configuration information may be sent to third UE 17c via unicast while data compression can be maintained via the broadcast session towards all the UEs already participating in the MBS session, such as first UE 17a and second UE 17b. The main drawback with such an approach is that additional unicast signalling is required to be setup by the gNB 10 and there is a risk that the third UE 17c would not be able to receive the unicast information before a compressed packet is sent causing a packet drop for the third UE 17c, unless the compressed packet is delayed until confirmation of the unicast configuration information is received at the gNB 10, which is non optimal for delay sensitive services.

[0052] In an alternative it is envisaged that failures in the form of packet drops are indicated via feedback from an individual UE (such as the third UE 17c) over the unicast link to the gNB 10 such that the gNB 10 may rebroadcast the samecompressed packet for reducing the packet drops. A problem with this alternative is the synchronization required between unicast link and the broadcast link and the delay that this introduces.

[0053] With reference again to Figure 1, the establishing of MBS sessions is a dynamic process where e.g. the third UE 17c may either join or leave a session being ongoing with the first UE 17a and the second UE 17b.

[0054] Further, for mobility reasons, the third UE 17c may be handed over from a previously serving gNB to the gNB 10 and thus a new PDCP entity in the form of the CU-UP 12 where an MBS session is already ongoing.

[0055] Currently, only the CU-CP 11 and the DU 16 have knowledge about a new UE 17c entering the MBS session. Thus, the CU-UP 12 handling the PDCP and ROHC is unaware of the fact that a context needs to be established between a compressor of the gNB 10 and a decompressor of the the MBS session-entering third UE 17c in order for the third UE 17c to subsequently be able to process compressed data sent from the gNB 10 the third UE 17c.

[0056] Figure 2 illustrates prior art U-mode compressor state transitions. As previously mentioned, data packets are sent in one direction in U-mode; from the gNB 10 to the UEs 173-170 (i.e. from the compressor of the gNB 10 to the decompressor of each of the UEs 173-170 ).

[0057] The ROHC compressor at the gNB 10 operates in three states: Initialization and Refresh (IR) state 20, First Order (FO) state 21 and Second Order (SO) state 22, where the IR 20 state transmits data headers in a form that requires no context to have been established between the compressor and the decompressor for the decompressor to be able to process and correctly interpret the received data headers. The data headers transmitted by the gNb 10 in the IR state further serve to establish a context between the compressor of the gNB 10 and the decompressors of the UEs 173-170 (including updating / refreshing a previously established context), while the FO state 21 and the SO state 22 each transmits compressed data each with an increasing compression gain relying on the established context. Packets transmitted in the IR state 20 are commonly referred to as Initialization and Refresh packets. The established context between the compressor of the gNB 10 and thedecompressors of the UEs 173-170 will in the following occasionally be referred to as “decompression context”.

[0058] The context comprises information about static fields, dynamic fields and their change pattern in the protocol data headers. This information is used by the compressor to compress the packet as efficiently as possible and then by the decompressor to decompress the packet to its original state.

[0059] This ultimately maintains the compressor and decompressor in synchronization in order for the decompressor to correctly decompress the compressed data headers transmitted in the FO state 21 and the SO state 22.

[0060] Whether or not the ROHC compressor moves to the FO state 21 or the SO state 22 for transmitting compressed data depends on the correctness of the decompressor context.

[0061] As shown in Figure 2, the ROHC compressor uses a so-called optimistic approach and aims at sending just enough information in order for the decompressor at each UE iya-c to maintain the correct decompressor context (i.e. for the decompressor to maintain synchronization with the compressor).

[0062] In case of errors occurring, a timer is utilized to periodically transit to lower states in order to re-synchronize the compressor and the decompressor. Thus, the compressor moves to a lower state to send packets that comprise enough information to correct any errors in the decompressor context, but this approach results in lower compression gain.

[0063] However, the utilization of the timers cannot resolve the problem of a new UE 17c entering an ongoing MBS session; if the timers are set short it may limit the amount of dropped packets due to decompression failures, but at the cost of limited compression gain.

[0064] If the timers are set to be too lengthy and the new UE 17c enters the MBS session shortly after the ROHC state machine of Figure 2 has transitioned to the FO state 21 or the SO state 22, numerous data packets will be discarded for the new UE 17c.

[0065] If the ROHC is implemented in for instance a mission critical communication (MCC) scenario where for instance emergency personnel such as fire fighters is dependent on mission-critical push-to-talk (MCPTT) technologies, thereliability of the communication is of high importance and a solution where many packets potentially are dropped is not good enough.

[0066] Figure 3 illustrates a flowchart of a method of a device, in this example the CU-UP 12, configured to control data header compression to a plurality of UEs iya-c in an MBS session for resolving this issue.

[0067] Reference is further made to Figure 4 illustrating U-mode compressor state transitions according to this embodiment.

[0068] As mentioned hereinabove, the CU-UP 12 is unaware that a further UE 17c enters an MBS session where two other UEs 17a, 17b already are participating.

[0069] In a first step S101, the CU-UP 12 therefore receives an alert from either the CU-CP 11 over the El interface or from the DU 16 over the Fi-U interface that the further UE 17c requests to join the MBS session which is ongoing with the other two UEs 17a, 17b.

[0070] In response to the alert, the CU-UP 12 transitions in step S102 to the IR state 20 of the data header compression for sending initialization data headers to the further joining UE 17c and the plurality of UEs 17a, 17b already participating in the MBS session in order to establish a context with all the UEs tya-c.

[0071] Thereafter, upon the context being established in S102, the CU-UP 12 transitions in step S103 to a compression state of the data header compression - i.e. either the FO state 21 or the SO state 22, or even first the FO state 21 and then the SO state 22 - for sending compressed data headers to all three UEs 173-170 now participating in the MBS session.

[0072] In other words, the CU-UP 12 has advantageously established a context between the compressor with which the CU-UP 12 is associated (i.e. the compressor of the gNB 10 in which the CU-CP 12 is arranged) and the decompressor of each of the UEs 173-170.

[0073] As illustrated with the dash-dot -indicated line of Figure 4 extending from the FO state 21 and the SO state 22 back to the IR state 20, as soon as a further UE wishes to enter an ongoing MBS session, the CU-UP 12 will in this embodiment transition directly from its current state (i.e. either from the SO state 22 or the FO state 21) to the IR state 20 for transmitting one or more initialization data headers in order to establish a decompression context with all the UEs lya-c.

[0074] Thus, in contrast to the prior art, this embodiment proposes an advantageous solution where the CU-UP 12 dynamically can fall back to the IR state 20 upon performing ROHC and start to send initialization data, such as ROHC initialization and refresh packet data headers for allowing establishment of decompression context at the UEs 173-170 when a new UE 17c enters the MBS session, and the benefit of ROHC or other appropriate header compression technologies such as e.g. Ethernet header compression (EHC) in which embodiments may be implemented can thus be taken advantage of upon performing an MBS.

[0075] Advantageously, data packets are no longer dropped due to a new UE 17c (and its decompressor) not having established context with the compressor of the gNB 10, and ROHC is possible to use for multiple recipients also for applications requiring reliable communication, such as for instance MCPTT.

[0076] Further, compared to solutions using unicast configuration to the new UE, the solution provided by embodiments herein can also be applied to delay sensitive services which has strict requirement on the reliability. A solution using unicast communication to provide additional data to the new UE may not be possible to synchronize with the actual user data, particularly in a split architecture where the CU-CP 11 and the CU-UP 12 operates independently when the connection is setup and may even be realized by different physical nodes.

[0077] As mentioned, the alert to the CU-UP 12 is triggered by the device with which an MBS radio bearer (MRB) is established with the UEs 17a, 17b participating in an ongoing MBS session (and with which device an MRB is established with the further UE 17c entering the MBS session), i.e. either the CU-CP 11 or the DU 16.

[0078] In the following, embodiments using either El application protocol (E1AP) between the CU-CP 11 and the CU-CP 12 or Fl application protocol (FiAP) between the DU 16 and the CU-UP 12 will be described.

[0079] When a first UE enters an MBS Session, the MBS session will be setup in the RAN triggered over N2 via NG application protocol (NGAP) signalling with the core network 13. Thereafter, the CU-CP 11 will trigger the setup of the MBS session in the CU-UP 12 via El and the user plane over Nsmb will be established. In addition, communication over the Fi-U will be setup and the UE will receive MBSconfiguration data by means of a radio resource configuration (RRC) reconfiguration procedure.

[0080] Figure 5 illustrates a signalling diagram where E1AP is utilized to alert the CU-UP 12 according to an embodiment of a new UE 17c entering an ongoing MBS session.

[0081] The CU-CP 11 detects in step S100 a new UE 17c entering the MBS session either by(a) a new UE entering the MBS session, in which case an NGAP message referred to as a “PDU SESSION MODIFICATION REQUEST” is received by the CU-CP 11 over the N2 interface, or(b) a UE being handed over from a neighbouring gNB using MBS, in which case an NGAP message referred to as a “HANDOVER REQUEST” is received by the CU-CP 11 over the N2 interface.

[0082] Either way, the CU-CP 11 will send an alert in step Sioia to the CU-UP 12. In this embodiment, an existing E1AP protocol message MC BEARER CONTEXT MODIFICATION REQUEST is updated with an indication of that a new UE 17c requests to use the MRB already being established with the gNB 10 for the ongoing MBS session with the other UEs 17a, 17b, and the purpose of the request, i.e. to establish decompression context.

[0083] As shown in Figure 5, the established MRB is identified by means of an MRB ID and the purpose of the request is indicated with a new Information Element (IE) MBS PDPC ROHC reset. In other words, the MBS PDPC ROHC reset is effectively an instruction to the CU-UP 12 to transition to the IR state 20 for the identified established MRB over which the ongoing MBS session is setup.

[0084] In response to the alert, the CU-UP 12 transitions in step S102 to the IR state 20 of the data header compression for sending IR packets to the further joining UE 17c and the plurality of UEs 17a, 17b already participating in the MBS session in order to establish a context between the gNB 10 and all the UEs tya-c.

[0085] In other words, when the CU-UP 12 receives the above E1AP message with the MBS PDCP ROHC reset IE activated, the CU-UP 12 will trigger the reinitialization of the context between the compressor of the gNB 10 and decompressorfor all UEs 173-170 taking part in the MBS session by falling back to the IR state and sending IR packets.

[0086] The CU-UP may reply in step SiO2a with a confirmation message MC BEARER CONTEXT MODIFICATION RESPONSE indicating whether or not the reestablishing of context is successful or not.

[0087] Thereafter, upon the context being established in S102, the CU-UP 12 transitions in step S103 to a compression state of the data header compression - i.e. the FO state 21 or the SO state 22 - for sending compressed data headers to all three UEs 173-170 now participating in the MBS session.

[0088] The CU-CP 11 hold an MBS session context containing all information describing the MBS session being conducted, amongst other things an indication of the MRB ID with a list of the UEs 173-0 using it per CU-UP (an MRB ID may be reused for another CU-UP) for connecting to the MBS session.

[0089] Whenever a new UE, in this example UE 17c, wishes to partake in an MBS session (triggered over NGAP), it is analysed if an additional UE already is provided with MBS user data, i.e. if the additional UE already has been RRC configured with the appropriate MRB(s) of the MBS session and the new UE 17c thus is ready to receive user data via an already existing MRB for which an PDCP entity is configured in a specific CU-UP 12.

[0090] If this is the case, the CU-UP 12 is informed by means of E1AP signalling, e.g. by means of the new indication MRB ID within the already specified E1AP message MC BEARER CONTEXT MODIFICATION REQUEST.

[0091] Further, as discussed hereinabove, the new IE MBS PDCP ROHC reset is in this example added to IE group referred to as “MC Bearer Context To Modify” as indicated e.g. in section 9.3.3.34 of 3GPP TS 37.483.

[0092] As an alternative to modifying an already existing message (i.e. the MC BEARER CONTEXT MODIFICATION REQUEST message) as discussed above, a new message is created comprising an “MBS PDCP ROHC reset” indication, i.e. an IE triggering the re-initialization of the context between the compressor of the gNB 10 and decompressor for all UEs 173-170 taking part in the MBS session.

[0093] Figure 6 illustrates a signalling diagram where F1AP is utilized to alert the CU-UP 12 according to an embodiment.

[0094] Again, as in previously described Figure 5, a new UE 17c enters the MBS session either by the UE 17c turning directly to the gNB 10 or by the UE 17c being handed over to the gNB 10 from a neighbouring gNB using MBS. The CU-CP 11 is thus triggered accordingly in step S100 by receiving one of the two previously discussed NGAP messages.

[0095] Either way, the DU 16 receives information that the new UE 17c joins the MBS session by an F1AP message UE CONTEXT MODIFICATION REQUEST message sent from the CU-CP 11 to the DU 16 and responds to the CU-CP 11 with a UE CONTEXT MODIFICATION RESPONSE message to confirm the request from the CU-CP 11.

[0096] In step Sioib, the DU 16 sends an alert to the CU-UP 12, i.e. an inband indication over the Fi-U interface, in the form of an ASSISTANCE INFORMATION DATA message to inform the CU-CP 12 that the new UE 17c is entering the MBS session. This message is referred to as a PDU Type 2 message.

[0097] As illustrated, the established MRB(s) is identified by means of MRB ID(s) and the new UE 17c added for each MRB may be identified by means of the IE indicated “MBS PDCP user”. Further, the message may optionally include an indication that an ROHC reset is to be performed (cf. step Sioia).

[0098] In this embodiment, the CU-UP 12 determines in step Stoic from the UE identifier “MBS PDCP user” whether or not the UE entering the MBS session is the first UE entering the session or an additional UE entering the MBS session where an initial UE already is included. If it is the first UE entering the MBS session, there is no need to transition to the IR state. However, for any additional UE, the transition to the IR state in step S102 will be undertaken.

[0099] Thus, for the ongoing MBS session specified by MRB ID to which the new additional UE 17c is being added, the CU-UP 12 transitions in step S102 to the IR state 20 of the data header compression for sending initialization data headers to the further joining UE 17c and the plurality of UEs 17a, 17b already participating in the MBS session in order to establish a context with all the UEs tya-c.

[0100] Thereafter, upon the context being established in S102, the CU-UP 12 transitions in step S103 to a compression state of the data header compression - i.e.to the FO state 21 or the SO state 22 - for sending compressed data headers to all three UEs 173-170 now participating in the MBS session.

[0101] In contrast to using E1AP, several Fi-U connections may be used for one specific MBS session and therefore the alert must be provided also for the setup with a first UE taking part of the MBS session. Therefore, a solution over E1AP may be preferred since in such case the alert only needs to be provided in case any additional UE is added to the MBS session.

[0102] Figure 7 illustrates a signalling diagram where F1AP is utilized to alert the CU-UP 12 according to an alternative embodiment.

[0103] Again, as in Figures 5 and 6, a new UE 17c enters the MBS session either by the UE 17c turning directly to the gNB 10 or by the UE 17c being handed over to the gNB 10 from a neighbouring gNB using MBS. The CU-CP 11 is thus triggered accordingly in step S100 by receiving one of the two previously discussed NGAP messages.

[0104] Either way, the DU 16 receives in step Siooc information that the new UE 17c joins the MBS session by an F1AP message sent from the CU-CP 11 to the DU 16.

[0105] However, in this embodiment, it is assumed that the new UE 17c already is configured with an MRB (i.e. after an RRC reconfiguration message containing MRB configuration information has been sent to the UE 17c). The CU-CP 12 will indicate by a new IE group in the F1AP message DL RRC MESSAGE TRANSFER that a new UE 17c has been added to the MRB and that a ROHC reset is required.

[0106] As previously described, the established MRB is identified by means of an MRB ID and the purpose of the request is indicated with the IE MBS PDPC ROHC reset.

[0107] In step Sioib, the DU 16 sends an alert to the CU-UP 12, i.e. an inband indication over the Fi-U interface, in the form of an ASSISTANCE INFORMATION DATA message over Fi-U to inform the CU-CP 12 that the new UE 17c is entering the MBS session identified by means of MRB ID and the indication that decompression context needs to be established.

[0108] For the ongoing MBS session specified by MRB ID to which the new UE 17c is being added, the CU-UP 12 transitions in step S102 to the IR state 20 of the data header compression for sending initialization data headers to the further joiningUE 17c and the plurality of UEs 17a, 17b already participating in the MBS session in order to establish a decompression context with all the UEs tya-c.

[0109] Thereafter, upon the decompression context being established in S102, the CU-UP 12 transitions in step S103 to a compression state of the data header compression - i.e. either the FO state 21 or the SO state 22, or even first the FO state 21 and then the SO state 22 - for sending compressed data headers to all three UEs 173-170 now participating in the MBS session.

[0110] Under certain conditions, a number of UEs may join the same MRB over a relatively short time period, for instance in a scenario where a group of users that are travelling together reaches a point where hand over is necessary. Another example is when a group of users having a meeting is requested to join the same session. The efficiency of the header compression may suffer significantly if a transition to the IR state is performed for each joining user.

[0111] In these scenarios, when the CU-UP 12 is alerted in step S101 that decompressor context should be established, it will in an embodiment apply a mechanism to limit a reset frequency of the ROHC compressor of the gNB 10, i.e. to limit the frequency of the CU-UP 12 transitioning to the IR state when more than one UE joins an MBS session.

[0112] Figure 8 shows a flowchart illustrating this embodiment. Upon the CU-UP 12 receiving an alert in step S101 that one or more new UEs 17c joins the MBS session, the CU-UP 12 transitions to the IR state in step S102 for establishing decompression context.

[0113] However, in this embodiment, the CU-UP 12 initiates a timer T (typically resetting the timer to zero) in step SiO2b and thereafter waits in step S102C until the timer T has reached a threshold value T_hold, where the timer T expires.

[0114] Any further alerts of UE(s) joining the MBS session during this time period will not be attended to in order to avoid activation of further transitions to the IR state in a scenario where the CU-UP 12 already is transitioning to the IR state for establishing decompression context.

[0115] When the timer T has reached T_hold, the CU-UP 12 proceeds to determining in step SiO2d if any further alert of a new UE joining the MBS session is received.

[0116] If not, the CU-UP 12 transitions in step S103 to the FO or SO state for sending compressed data to the UEs of the MBS session , as previously described.

[0117] If so, the CU-UP again re-transitions to the IR state in step S102 and the process is repeated.

[0118] As is understood, the length of the timer threshold value T_hold being set is depending on the specific application, and particularly depending on the frequency of the packets being transferred by the UEs iya-c. For voice this is commonly 20 ms, while for other applications it is typically longer. It may be envisaged that the length of the timer threshold value T_hold is derived from a quality of service configuration for the MRB or from the specific application, such as 20 ms in case of e.g. VoNR.

[0119] As is understood, the CU-UP 12 may in an embodiment store an alert received even before the timer has expired in step 102c b. If so, the CU-UP 12 may determine immediately after T_hold has been reached that a re-transition to the IR state in step S102 is to be performed even if no further alert is received immediately after the expiry.

[0120] Figure 9 illustrates a device, such as e.g. the CU-UP 12, configured to control data header compression to a plurality of UEs in an MBS session according to an embodiment. The steps of the method performed by the CU-UP 12 are in practice performed by a processing unit 111 embodied in the form of one or more microprocessors arranged to execute a computer program 112 downloaded to a suitable storage volatile medium 113 associated with the microprocessor, such as a Random Access Memory (RAM), or a non-volatile storage medium such as a Flash memory or a hard disk drive. The processing unit 111 is arranged to cause the CU-UP 12 to carry out the method according to embodiments described herein, when the appropriate computer program 112 comprising computer-executable instructions is downloaded to the storage medium 113 and executed by the processing unit 111. The storage medium 113 may also be a computer program product comprising the computer program 112. Alternatively, the computer program 112 may be transferred to the storage medium 113 by means of a suitable computer program product, such as a Digital Versatile Disc (DVD) or a memory stick. As a further alternative, the computer program 112 may be downloaded to the storage medium 113 over a network. The processing unit 111 may alternatively be embodied in the form of a digital signal processor (DSP), an application specific integrated circuit (ASIC), afield-programmable gate array (FPGA), a complex programmable logic device (CPLD), etc. The CU-UP 12 further comprises an interface 114 over which data may be received and transmitted.

[0121] Figure 10 illustrates a network in the form of an Open RAN 100 (O-RAN), in which embodiments may be implemented. For example, the method may be implemented in the CU-CP 600 of the O-RAN receiving an alert from either the O- CU-CP 500 or the O-DU 700 of the O-RAN 100.

[0122] With reference to the O-RAN 100, the role of a Non-Real Time RAN intelligent controller (RIC) 200 is among other things, such as providing a service management and orchestration framework, to serve one or more radio base stations 300 (i.e. RAN sites) referred to as O-eNB via 01 interface and to provide high-level control signals to Near-Real Time RICs 400 via Al interface; such signals include but not limited to policy-based guidance, ML model management, and enrichment of data. The role of Near- Real Time RICs 400 is to perform low-level control signals to O-RAN compatible network elements including the one or more O-eNBs 300, O-CU- CP 500, O-CU-UP 600 and O-DU 700 via E2 interface. Further included is an 0-RU 800 (“radio unit”) connected to the O-DU 700 via a control, user and synchronization (CUS) plane as well as via a management (M) plane, and an O-Cloud 900, i.e. a cloud platform.

[0123] The aspects of the present disclosure have mainly been described above with reference to a few embodiments and examples thereof. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the invention, as defined by the appended patent claims.

[0124] Thus, while various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Claims

CLAIMS1. A method of a device (12) configured to control data header compression to a plurality of wireless communication devices (17a, 17b) in a multicast -broadcast service, MBS, session, the method comprising: receiving (S101) an alert that a further wireless communication device (17c) requests to join the MBS session; transitioning (S102), in response to the alert, to an initialization state (20) of the data header compression for sending initialization data headers to the further joining wireless communication device (17c) and the plurality of wireless communication devices (17a, 17b) already participating in the MBS session, in order to establish a context between a compressor with which the device (12) is associated and a decompressor of each of the wireless communication devices (17a, 17, 17c); and upon the context being established: transitioning (S103) to a compression state (21, 22) of the data header compression for sending compressed data headers to the wireless communication devices (17a, 17b) and the further joining wireless communication device (17c) participating in the MBS session.

2. The method of claim 1, the alert being configured to be received (Sioia) from a control plane device (11).

3. The method of claim 2, the device (12) configured to control data header compression being a central unit-user plane, CU-UP, device and the control plane device (11) providing the alert being a central unit-control plane, CU-CP, device.

4. The method of any one of the preceding claims, the alert being configured to comprise an identifier of an established MBS radio bearer, MRB, over which the MBS session is setup in order for the device (12) to transition (S102) to the initialization state for the identified MRB.

5. The method of claim 4, the alert being received (Sioia) in an MC BEARER CONTEXT MODIFICATION REQUEST message being modified to comprise the identifier of the MRB and an instruction to transition (S102) to the initialization state for the identified MRB.

6. The method of claim 1, the alert being configured to be received (Sioib) from a user plane device (16).

7. The method of claim 6, the device (12) configured to control data header compression being a central unit-user plane, CU-UP, device and the user plane device (16) providing the alert being a distributed unit, DU, device.

8. The method of any one of claims 6 or 7, the alert being configured to comprise an identifier of an established MBS radio bearer, MRB, over which the MBS session is setup in order for the device (12) to transition (S102) to the initialization state for the identified MRB.

9. The method of claim 8, the alert being received (Sioib) in an ASSISTANCE INFORMATION DATA message being modified to comprise the identifier of the MRB.

10. The method of claim 8, the alert being received (Sioib) in an ASSISTANCE INFORMATION DATA message being modified to comprise the identifier of the wireless communication device joining the MBS session; the method further comprising: determining (Sioic) from said identifier if the wireless communication device joining the MBS session is an additional wireless communication device being added to the MBS session having at least one wireless communication device already participating; and if so the initialization state (20) will be transitioned to.

11. The method of any one of the preceding claims, further comprising: initiating (SiO2b) a timer after transitioning (S102) to the initialization state (20); determining (SiO2d), after the timer has expired (SiO2c), if one or more further alerts are received (SiO2d) that a further wireless communication device requests to join the MBS session; and if not transitioning (S103) to the compression state (21, 22) of the data header compression for sending compressed data headers.

12. The method of claim 11, further comprising: re-transitioning (S102) to the compression state (21, 22) of the data header compression for sending compressed data headers.

13. The method of claim 12, wherein the determining (SiO2d), after the timer has expired (SiO2c), if one or more further alerts are received (SiO2d) that a further wireless communication device requests to join the MBS session further comprisesdetermining that one or more further alerts have been received before the expiry of the timer.

14. A computer program (112) comprising computer-executable instructions for causing a device (12) to perform steps recited in any one of claims 1-13 when the computer-executable instructions are executed on a processing unit (111) included in the device (12).

15. A computer program product comprising a computer readable medium (113), the computer readable medium having the computer program (112) according to claim 14 embodied thereon.

16. A device (12) configured to control data header compression to a plurality of wireless communication devices (17a, 17b) in a multicast-broadcast service, MBS, session, the device (12) comprising a processing unit (111) and a memory (113), said memory containing instructions (112) executable by said processing unit (111), whereby the device (12) is operative to: receiving (S101) an alert that a further wireless communication device (17c) requests to join the MBS session; transitioning (S102), in response to the alert, to an initialization state (20) of the data header compression for sending initialization data headers to the further joining wireless communication device (17c) and the plurality of wireless communication devices (17a, 17b) already participating in the MBS session, in order to establish a context between a compressor with which the device (12) is associated and a decompressor of each of the wireless communication devices (17a, 17, 17c); and upon the context being established: transitioning (S103) to a compression state (21, 22) of the data header compression for sending compressed data headers to the wireless communication devices (17a, 17b) and the further joining wireless communication device (17c) participating in the MBS session.

17. The device (12) of claim 16, the device (12) being operative to receive (Sioia) the alert from a control plane device (11).

18. The device (12) of claim 17, the device (12) configured to control data header compression being a central unit-user plane, CU-UP, device and the control plane device (11) providing the alert being a central unit-control plane, CU-CP, device.

19. The device (12) of any one of the preceding claims, the alert being configured to comprise an identifier of an established MBS radio bearer, MRB, over which the MBS session is setup in order for the device (12) to transition (S102) to the initialization state for the identified MRB.

20. The device (12) of claim 19, the device (12) being operative to receive (Sioia) the alert in an MC BEARER CONTEXT MODIFICATION REQUEST message being modified to comprise the identifier of the MRB and an instruction to transition (S102) to the initialization state for the identified MRB.

21. The device (12) of claim 16, the device (12) being operative to receive (Sioib) the alert from a user plane device (16).

22. The device (12) of claim 21, the device (12) configured to control data header compression being a central unit-user plane, CU-UP, device and the user plane device (16) providing the alert being a distributed unit, DU, device.

23. The device (12) of any one of claims 21 or 22, the alert being configured to comprise an identifier of an established MBS radio bearer, MRB, over which the MBS session is setup in order for the device (12) to transition (S102) to the initialization state for the identified MRB.

24. The device (12) of claim 23, the device (12) being operative to receive (Sioib) the alert in an ASSISTANCE INFORMATION DATA message being modified to comprise the identifier of the MRB.

25. The device (12) of claim 23, the device (12) being operative to receive (101b) the alert in an ASSISTANCE INFORMATION DATA message being modified to comprise the identifier of the wireless communication device joining the MBS session; and further to: determining (Sioic) from said identifier if the wireless communication device joining the MBS session is an additional wireless communication device being added to the MBS session having at least one wireless communication device already participating; and if so the initialization state (20) will be transitioned to.

26. The device (12) of any one claims 16-25, further being operative to: initiating (SiO2b) a timer after transitioning (S102) to the initialization state (20); determining (SiO2d), after the timer has expired (SiO2c), if one or more further alerts are received (SiO2d) that a further wireless communication device requests to join the MBS session; and if not transitioning (S103) to the compression state (21, 22) of the data header compression for sending compressed data headers.

27. The device (12) of claim 26, further being operative to: re-transitioning (S102) to the compression state (21, 22) of the data header compression for sending compressed data headers.

28. The device (12) of claim 27, further being operative to, when determining (SiO2d), after the timer has expired (SiO2c), if one or more further alerts are received (SiO2d) that a further wireless communication device requests to join the MBS session, determining that one or more further alerts have been received before the expiry of the timer.

Citation Information

Patent Citations

  • Method and device of processing context information in multicast and broadcast service

    CN101998248A

  • Method for the exchange of data packets in a network of distributed stations, device for compression of data packets and device for decompression of data packets

    US20070165635A1

  • Communication method and communication apparatus

    WO2023011004A1

  • Managing reception of multicast and / or broadcast services after a state transition

    WO2023069709A1