WO2022154711A1 - Sélection de support pour segmentation - Google Patents

Sélection de support pour segmentation Download PDF

Info

Publication number
WO2022154711A1
WO2022154711A1 PCT/SE2021/051291 SE2021051291W WO2022154711A1 WO 2022154711 A1 WO2022154711 A1 WO 2022154711A1 SE 2021051291 W SE2021051291 W SE 2021051291W WO 2022154711 A1 WO2022154711 A1 WO 2022154711A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
segmented
segments
bearer
radio node
Prior art date
Application number
PCT/SE2021/051291
Other languages
English (en)
Inventor
Mattias BERGSTRÖM
Cecilia EKLÖF
Tomas Frankkila
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2022154711A1 publication Critical patent/WO2022154711A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/10Scheduling measurement reports ; Arrangements for measurement reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data

Definitions

  • the present disclosure relates to transmission of a segmented message (e.g., a segmented Radio Resource Control (RRC) message) in a wireless communication system.
  • a segmented message e.g., a segmented Radio Resource Control (RRC) message
  • RRC Radio Resource Control
  • QoE measurements have been specified for Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) and the Universal Mobile Terrestrial System (UMTS). The purpose of these application layer measurements is to measure the end user experience when using certain applications.
  • 3GPP Third Generation Partnership Project
  • LTE Long Term Evolution
  • UMTS Universal Mobile Terrestrial System
  • IP Internet Protocol
  • MTSI Multimedia Subsystem
  • QoE Measurement Collection enables configuration of application layer measurements in the User Equipment (UE) and transmission of QoE measurement result files by means of Radio Resource Control (RRC) signaling.
  • RRC Radio Resource Control
  • Application layer measurement configuration received from Operation, Administration, and Management (0AM) or the Core Network (CN) is encapsulated in a transparent container, which is forwarded to the UE in a downlink RRC message.
  • Application layer measurements received from the UE's higher layer are encapsulated in a transparent container and sent to the network in an uplink RRC message.
  • the result container is forwarded to a Trace Collector Entity (TCE).
  • TCE Trace Collector Entity
  • the enhanced node B sends an RRC Connection Reconfiguration message including a QoE configuration file to the UE, and the UE responds with an RRC Connection Reconfiguration Complete message.
  • the UE sends an RRC message called "MeasReportAppLayer" to the eNB, where this message includes a QoE measurement result file.
  • the message MeasReportAppLayer is used for transmission of the QoE measurement result file, as described in the following excerpt from the RRC specification 3GPP TS 36.331:
  • the communication between the access stratum layer (where the RRC messages are transmitted) and the application layer in the UE are done by means of Attention (AT) commands.
  • the AT commands are specified in 3GPP TS 27.007 V16.6.0 as shown in the following excerpt:
  • This command allows control of the application level measurement configuration according to 3GPP TS 25.331 [74] and 3GPP TS 36 331 [86]
  • the set command controls the presentation of the unsolicited result code
  • Read command returns the current value of ⁇ n>.
  • Test command returns values supported as a compound value.
  • ⁇ n> integer type. Disable and enable presentation of the unsolicited result code +CAPPLEVMC to the TE.
  • ⁇ app-meas_s ervi ce_type> integer type. Contains the indication of what application that is target for the application level measurement configuration.
  • ⁇ start- stop_reporting> integer type. Indicates the start and stop of the application level measurement reporting for the application indicated by the ⁇ app-meas_service_type>.
  • ⁇ app-meas_config_file_length> integer type. Indicates the number of octets of the ⁇ app- meas_config- file> parameter.
  • ⁇ app-meas_config- file> string of octets. Contains the application level measurement configmation file for the application indicated by the ⁇ app-meas_s ervi ce_type>. The parameter shall not be subject to conventional character conversion as per +CSCS.
  • This command allows the MT to provide the application level measurement report according to 3GPP TS 25.331 [74] and 3GPP TS 36.331 [86], Refer subclause 9.2 for possible ⁇ err> values.
  • ⁇ app_meas_s ervi ce_type> integer type. Contains the indication of what application that is providing the application level measurement report.
  • ⁇ app-meas_report_length> integer type. Indicates the number of octets of the ⁇ app-meas_report> parameter.
  • ⁇ app-meas_report> string of octets. Contains the application level measurement configuration file for the application indicated by the ⁇ app-meas_servi ce_type>. The parameter shall not be subject to conventional character conversion as per +CSCS.
  • RRC Segmentation of RRC messages (i.e., "RRC Segmentation") is being introduced for 3GPP Release 16. This is needed to support transmitting large RRC messages that exceed the Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) size limit, which is 9000 bytes for New Radio (NR) and 8188 bytes for LTE (see, e.g., 3GPP TS 37.873 V16.0.0).
  • RATs Radio Access Technologies
  • the segmented RRC messages are sent in the RRC messages DLDedicatedMessageSegment and ULDedicatedMessageSegment, as shown in an extract of the latest Change Requests (CRs) on the RRC specification 3GPP TS 38.331.
  • Current specifications allow for using a maximum of five segments in DL since the minimum requirement for the UEs receiver buffer is 45 Kilobytes (Kbyte) and the network is unaware of whether the UE has a larger receiver buffer or not.
  • Kbyte Kilobytes
  • UL a maximum of sixteen segments are allowed since the segmented RRC messages are sent on Signaling Radio Bearer 1 (SRB1), which has higher priority than other control plane and user plane signaling. Allowing more segments could result in delaying delivery of packet for, e.g., real-time services, in particular during poor radio conditions, which would likely cause quality degradations.
  • SRB1 Signaling Radio Bearer 1
  • RRC segments cannot be interrupted by sending other RRC messages or RRC segments. That is, once the RRC transmitter has started sending the first segment of an RRC message, it must send the remaining RRC segments for that RRC message before sending another RRC message (segmented or not). Thus, other RRC messages, if generated, will have to wait.
  • the message carrying segments i.e. ULDedicatedMessageSegment
  • SRB4 for the signalling radio bearer is not part of the current 3GPP specifications.
  • bearers In 3GPP NR and 3GPP LTE, so-called, bearers (or radio bearers) are used to transmit data over the radio interface. Different bearers may be mapped to different, so called, logical channels. Logical channels are grouped into logical channel groups, which in turn are associated with different priorities. When transmissions are made, the priorities are taken into account such that logical channels belonging to a high priority logical channel group are in general served before logical channels in low priority logical channel groups.
  • SRB is a bearer carrying signaling related messages as compared to Data Radio Bearers (DRBs) which carry user plane data.
  • DRBs Data Radio Bearers
  • SRBs which have different numbers. Which SRB a certain message is sent on can depend on the content of the message and the situation.
  • SRB4 QoE measurements may be signaled on an SRB. While it is yet to be decided, this SRB may be named SRB4 and, as such, the name SRB4 is used herein. SRB4 is likely to be configured to a logical channel and a logical channel group which have a lower priority compared to, for example, SRB1.
  • a method performed by a radio node comprises selecting, based on one or more parameters, a bearer for a transmission of a message that contains one or more segments of a segmented message.
  • the method further comprises transmitting the message on the selected bearer.
  • the segmented message is a segmented Radio Resource Control (RRC) message
  • the one or more segments are one or more segments of the segmented RRC message but less than all segments of the segmented RRC message.
  • RRC Radio Resource Control
  • the one or more parameters comprise: (a) content of the segmented message, (b) content type of the content of the segmented message, (c) information elements (IES) comprised in the segmented message, (d) a configuration received from a network node, (e) a configuration received from a network node, where the configuration indicates a bearer to be used for transmission for each of one or more groups of segmented messages, (f) a defined or configured default bearer, (g) whether one or more certain bearers are configured for the radio node to use, (h) a message type of the message that contains the segments of the segmented message, or (i) a combination of any two or more of (a)-(h).
  • the one or more parameters comprise a content type of the content of the segmented message
  • selecting the bearer for the transmission of the message that contains the one or more segments of the segmented message comprises selecting a first bearer if the content of the segmented message is of a first content type and selecting a second bearer if the content of the segmented message is of a second content type.
  • the first content type is a wireless communication device or User Equipment (UE) capability related message
  • the second content type is a Quality of Experience (QoE) related message.
  • QoE Quality of Experience
  • the one or more parameters comprise IES comprised in the segmented message
  • selecting the bearer for the transmission of the message that contains the one or more segments of the segmented message comprises selecting a first bearer if the segmented message contains one or more first IEs and selecting a second bearer if the segmented message contains one or more second IEs.
  • the segmented message is a segmented RRC message
  • the one or more parameters comprise a parameter about a maximum number of segments supported by the segmented RRC message
  • selecting the bearer for the transmission of the message that contains the one or more segments of the segmented message comprises selecting a first bearer if the segmented message supports a first maximum number of segments and selecting a second bearer if the segmented message supports a second maximum number of segments that is greater than the first maximum number of segments.
  • the method further comprises receiving configuration information from a network node, the configuration information comprising information that indicates a bearer on which a certain message is to be transmitted.
  • a maximum number of segments or a maximum size is applied to limit the number of segments or the size of the segmented message. In one embodiment, the maximum number of segments or the maximum size is based on the segmented message. In another embodiment, the maximum number of segments or the maximum size is based on the selected bearer.
  • the one or more parameters comprise a receiver buffer size of a receiving radio node to which the segmented message is transmitted, and the method further comprises receiving information that indicates the receiver buffer size of the receiving radio node.
  • selecting the bearer for the transmission of the message that contains the one or more segments of the segmented message comprises selecting the bearer for the transmission of the message that contains the one or more segments of the segmented message based on the receiver buffer size of the receiving radio node.
  • receiving the information that indicates the receiver buffer size of the receiving radio node comprises receiving the information that indicates the receiver buffer size of the receiving radio node via wireless communication device or UE capability information.
  • the information that indicates the receiver buffer size of the receiving radio node comprises information that explicitly indicates the size of the receiver buffer, information that indicates a number of segments that the receiver radio node is capable of receiving, or information that indicates one of two or more defined receiver buffer sizes.
  • the radio node is a wireless communication device.
  • the method further comprises receiving configuration information from a network node, the configuration information comprising information that indicates a particular bearer to be used for transmission based on message type and/or based on content of the segmented message.
  • the radio node is a base station.
  • the method further comprises receiving, from a wireless communication device to which the message is to be transmitted, information that indicates a receiver buffer size of the wireless communication device, and a maximum number of segments of the segmented message or a maximum size of the segmented message is based on the receiver buffer size.
  • a radio node for a cellular communications system is adapted to select, based on one or more parameters, a bearer for a transmission of a message that contains one or more segments of a segmented message based on one or more parameters.
  • a radio node for a cellular communications system comprises processing circuitry configured to cause the radio node to select, based on one or more parameters, a bearer for a transmission of a message that contains one or more segments of a segmented message based on one or more parameters.
  • a method performed by a receiving radio node comprises receiving, from a transmitting radio node, a message that contains one or more segments of a segmented message, the message being received on a particular bearer.
  • the segmented message is a segmented Radio Resource Control, RRC, message
  • the one or more segments are one or more segments of the segmented RRC message but less than all segments of the segmented RRC message.
  • the particular bearer is a function of one or more parameters comprising: (a) content of the segmented message, (b) content type of the content of the segmented message, (c) IES comprised in the segmented message, (d) a configuration received from a network node, (e) a configuration received from a network node, where the configuration indicates a bearer to be used for transmission for each of one or more groups of segmented messages, (f) a defined or configured default bearer, (g) whether one or more certain bearers are configured for the radio node to use, (h) a message type of the message that contains the segments of the segmented message, or (i) a combination of any two or more of (a)-(h).
  • the particular bearer is a function of one or more parameters
  • the receiving radio node is a base station
  • the transmitting radio node is a wireless communication device
  • the method further comprises transmitting configuration information to the wireless communication device, the configuration information comprising information that indicates a bearer on which a certain message is to be transmitted.
  • a maximum number of segments or a maximum size is applied to limit the number of segments or the size of the segmented message. In one embodiment, the maximum number of segments or the maximum size is based on the segmented message. In another embodiment, the maximum number of segments or the maximum size is based on the selected bearer.
  • the particular bearer is a function of one or more parameters comprising receiver buffer size
  • the receiving radio node is a wireless communication device
  • the transmitting radio node is a base station
  • the one or more parameters comprise a receiver buffer size of a receiving radio node to which the segmented message is transmitted
  • the method further comprises transmitting information that indicates the receiver buffer size of the wireless communication device to the base station.
  • a receiving radio node is adapted to receive, from a transmitting radio node, a message that contains one or more segments of a segmented message, the message being received on a particular bearer.
  • a receiving radio node for a cellular communications system comprises processing circuitry configured to cause the receiving radio node to receive, from a transmitting radio node, a message that contains one or more segments of a segmented message, the message being received on a particular bearer.
  • FIG 1 illustrates the Radio Resource Control (RRC) signaling flow for Quality of Experience (QoE) measurement collection in Third Generation Partnership Project (3GPP) Long Term Evolution (LTE);
  • RRC Radio Resource Control
  • QoE Quality of Experience
  • Figure 2 illustrates one example of a cellular communications system in which embodiments of the present disclosure may be implemented
  • Figure 3 is a flow chart that illustrates the operation of a radio node to transmit a message that contains one segment, but potentially more than one segment, of another message (i.e., of a segmented message such as, e.g., a segmented RRC message) in accordance with an embodiment of the present disclosure;
  • a segmented message such as, e.g., a segmented RRC message
  • Figure 4 illustrates an example of the process of Figure 3 in which the transmitting radio node is a wireless communication device and the receiving radio node is a base station;
  • Figure 5 illustrates an example of the process of Figure 3 in which the transmitting radio node is a base station and the receiving radio node is a wireless communication device;
  • FIGS 6, 7, and 8 are schematic block diagrams of example embodiments of a radio access node (e.g., a base station);
  • a radio access node e.g., a base station
  • Figures 9 and 10 are schematic block diagrams of example embodiments of a wireless communication device or User Equipment (UE);
  • Figure 11 illustrates another example system in which embodiments of the present disclosure may be implemented;
  • Figure 12 illustrates example embodiments of the host computer, base station, and UE of Figure 11;
  • FIGS 13, 14, 15, and 16 are flow charts that illustrate procedures that may be performed in the system of Figure 11 in accordance with embodiments of the present disclosure.
  • Figure 17 is a reproduction of Figure 5.7.7.1-1 of 3GPP Technical Specification (TS) 38.331.
  • Radio Node As used herein, a "radio node” is either a radio access node or a wireless communication device.
  • Radio Access Node As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals.
  • RAN Radio Access Network
  • a radio access node examples include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.
  • a base station e.g., a New Radio (NR) base station (gNB)
  • a "core network node” is any type of node in a core network or any node that implements a core network function.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like.
  • MME Mobility Management Entity
  • P-GW Packet Data Network Gateway
  • SCEF Service Capability Exposure Function
  • HSS Home Subscriber Server
  • a core network node examples include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • NSSF Network Slice Selection Function
  • NEF Network Exposure Function
  • NRF Network Exposure Function
  • NRF Network Exposure Function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • a "communication device” is any type of device that has access to an access network.
  • Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC).
  • the communication device may be a portable, hand-held, computer-comprised, or vehiclemounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.
  • One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network).
  • a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device.
  • UE User Equipment
  • MTC Machine Type Communication
  • LoT Internet of Things
  • Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC.
  • the wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.
  • Network Node As used herein, a "network node” is any node that is either part of the RAN or the core network of a cellular communications network/system.
  • the description herein sometimes uses, as an example, that there are two types of messages which can be segmented; namely messages containing UE capabilities and messages containing QoE measurement related signaling.
  • messages containing UE capabilities and messages containing QoE measurement related signaling can also apply for the case when three, or even more, types of messages are sent in segmented manner.
  • the particular types of segmented messages i.e., messages containing UE capabilities and messages containing QoE measurement related signaling
  • Additional or alternative type of segmented messages may be used.
  • a radio node or transmitter e.g., a wireless communication device (e.g., a UE) or a RAN node (e.g., a gNB)
  • sends segments e.g. on a certain bearer.
  • the segments may however not be sent by themselves but instead, as described in the background, segments may be sent within another message type which carries segments of other messages. But for the sake of readability, it may sometimes anyway be described as the segments are being sent on the bearer, which should be understood as the segments may be sent within another message which carries the segments.
  • QoE measurement files can be considered to have, comparably, low priority.
  • the UE may have other services which have more stringent requirements, such as communicational video and/or voice.
  • the QoE related signaling are to be sent to or received from the network at the same time as the UE has other traffic to send or receive and if the QoE related signaling is given higher priority than the other traffic, the requirements for the other traffic may not be met, e.g., the other traffic may not be delivered in time.
  • the packets for that service need to be delivered within a given time budget, which is the so-called Packet Delay Budget (PDB).
  • PDB Packet Delay Budget
  • the UE may send other types of Radio Resource Control (RRC) messages which also can be segmented, such as the UE capability information message.
  • RRC Radio Resource Control
  • the network may also send large RRC messages to the UE, such as the UE configuration messages, which is used to configure functions other than QoE reporting.
  • RRC messages may be time critical since they are important information for the network to have in order to serve the UE in the best way possible and for the UE to behave in the way that is expected by the network.
  • a radio node e.g., a RAN node or a wireless communication device selects a bearer on which a message carrying one or more segments of a segmented message (e.g., one or more RRC segments of a segmented RRC message). The radio node then transmits the message on the selected bearer.
  • a wireless communication device selects, from among two or more bearers, a bearer on which a message carrying one or more segments (e.g., one or more segments of a segmented RRC message) is to be transmitted.
  • the selection is such that the wireless communication device selects a first bearer (e.g., SRB1) for transmission of messages carrying segments of segmented wireless communication device capabilities, but selects a second bearer (e.g., SRB4) for transmission of messages carrying segments of segmented QoE measurement related messages.
  • Embodiments relate to bearer selection for transmission of a message that contains one or more segments of segmented message based on one or more parameters.
  • method performed by a radio node comprises selecting a bearer for a transmission of a message that contains one or more segments of a segmented message based on one or more parameters.
  • the method further comprises transmitting the message on the selected bearer.
  • the one or more segments are one or more segments of a segmented RRC message.
  • the one or more parameters comprise: (a) content of the segmented message, (b) content type of the content the segmented message (c) Information Elements (IES) comprised in the segmented message, (d) a configuration received from a network node, (e) a configuration received from a network node, where the configuration indicates a bearer to be used for transmission for each of one or more groups of segmented messages (e.g., groups of segmented messages that carry particular different content or groups of segmented message of different message types), (f) a defined or configured default bearer, (g) whether one or more certain bearers are configured for the radio node to use, (h) a message type (e.g., RRC message type) of the message that contains the segments of the segmented message, or (i) a combination of any two or more of (a)-(h).
  • a message type e.g., RRC message type
  • Embodiments of the solution(s) described herein may result in the delay requirements for different segmented message having a higher chance of being met, which improves user experience. Embodiments of the solution(s) described herein take the priorities of the messages into account at transmission, which leads to predictable and controllable behavior.
  • FIG. 2 illustrates one example of a cellular communications system 200 in which embodiments of the present disclosure may be implemented.
  • the cellular communications system 200 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC); however, embodiments of the present disclosure may be used in any type of cellular or wireless network in which segmentation and radio bearers are used.
  • the RAN includes base stations 202-1 and 202-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells 204-1 and 204-2.
  • gNBs NR base stations
  • ng-eNBs next generation eNBs
  • LTE RAN nodes connected to the 5GC
  • controlling corresponding (macro) cells 204-1 and 204-2 controlling corresponding (macro) cells 204-1 and 204-2.
  • the base stations 202-1 and 202-2 are generally referred to herein collectively as base stations 202 and individually as base station 202.
  • the (macro) cells 204-1 and 204-2 are generally referred to herein collectively as (macro) cells 204 and individually as (macro) cell 204.
  • the RAN may also include a number of low power nodes 206-1 through 206-4 controlling corresponding small cells 208-1 through 208-4.
  • the low power nodes 206-1 through 206-4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like.
  • RRHs Remote Radio Heads
  • one or more of the small cells 208-1 through 208-4 may alternatively be provided by the base stations 202.
  • the low power nodes 206-1 through 206-4 are generally referred to herein collectively as low power nodes 206 and individually as low power node 206.
  • the small cells 208-1 through 208-4 are generally referred to herein collectively as small cells 208 and individually as small cell 208.
  • the cellular communications system 200 also includes a core network 210, which in the 5GS is referred to as the 5GC.
  • the base stations 202 (and optionally the low power nodes 206) are connected to the core network 210.
  • the base stations 202 and the low power nodes 206 provide service to wireless communication devices 212-1 through 212-5 in the corresponding cells 204 and 208.
  • the wireless communication devices 212-1 through 212-5 are generally referred to herein collectively as wireless communication devices 212 and individually as wireless communication device 212.
  • the wireless communication devices 212 are oftentimes described, as an example, as UEs and as such are sometimes referred to as UEs 212.
  • Figure 3 is a flow chart that illustrates the operation of a radio node to transmit a message that contains one segment, but potentially more than one segment, of another message (i.e., of a segmented message such as, e.g., a segmented RRC message) in accordance with an embodiment of the present disclosure.
  • the radio node may be, for example, a RAN node (e.g., a base station 202) or a wireless communication device 212. Because the radio node is transmitting in this procedure, it is referred to as a "transmitting radio node” in order to distinguish it from the radio node that receives the message (which is referred to as a "receiving radio node”). Note that optional steps are represented by dashed lines/boxes.
  • the transmitting radio node optionally determines a receive buffer size of a receiving radio node to which it is to transmit a message carrying one or more segments of a segmented message (step 300).
  • the message includes only a single segment of the segment message; however, in other embodiments, the message may include more than one segment (but less than all segments) of the segmented message. As discussed below, in one embodiment, this is done by receiving capability information from the receiving radio node (step 300A).
  • the transmitting radio node may receive configuration information (e.g., from a network node) that provides one or more configurations related to bearer selection (step 302).
  • the one or more configurations may include, for example, a configuration that indicates a bearer to be used for each of two or more content types and/or for each of two or more message types.
  • the transmitting radio node selects a bearer on which to transmit the message that contains one or more segments of the segmented message based on one or more parameters (step 304).
  • the selection of the bearer is the selection of the bearer from a set of available bearers (e.g., a set of configured or defined bearers).
  • the set of available bearers includes at least two bearers (e.g., SIB1 and SIB4 in the case of 3GPP NR).
  • the one or more parameters used by the transmitting radio node to select the bearer on which to transmit the message that contains segment(s) of the segmented message include any one or more of the following parameters:
  • content of the segmented message such as, e.g., the content type (e.g., WCD or UE capabilities or QoE related content) of the content of the segmented message or Information Elements (IES) contained in the segmented message; • a configuration received from a network node (e.g., a configuration that indicates the bearer to use for each of two or more content types and/or for each of two or more message types), which may be received in step 302;
  • a network node e.g., a configuration that indicates the bearer to use for each of two or more content types and/or for each of two or more message types
  • message type of the message carrying the segments of the segmented message e.g., type of RRC message such as, e.g., a legacy RRC message type for RRC segments or a new RRC message type for carrying a larger number of RRC segments.
  • the transmitting radio node transmits the message carrying the segment(s) of the segmented message to the receiving radio node on the selected bearer (step 306).
  • the transmitting radio node limits the number of segments for the segmented message or the maximum size of the segmented message based on, e.g., the receive buffer size of the receiving radio node.
  • the maximum number of segments and/or the maximum size of the segmented message may, for example, be dependent on the segmented message and/or dependent on the selected radio bearer.
  • Figure 4 illustrates an example of the process of Figure 3 in which the transmitting radio node is a wireless communication device 212 and the receiving radio node is a base station 202. Again, optional steps are represented by dashed lines/boxes.
  • the wireless communication device 212 receives, from the base station 202, configuration information related to bearer selection (step 400).
  • the one or more configurations provided by the configuration information may include, for example, a configuration that indicates a bearer to be used for each of two or more content types and/or for each of two or more message types.
  • the wireless communication device 212 selects a bearer on which to transmit a message that contains one or more segments of a segmented message based on one or more parameters (step 402).
  • the message includes only a single segment of the segment message; however, in other embodiments, the message may include more than one segment (but less than all segments) of the segmented message.
  • the selection of the bearer is the selection of the bearer from a set of available bearers (e.g., a set of configured or defined bearers).
  • the set of available bearers includes at least two bearers (e.g., SIB1 and SIB4 in the case of 3GPP NR).
  • the one or more parameters used by the wireless communication device 212 to select the bearer on which to transmit the message that contains segment(s) of the segmented message include any one or more of the parameters listed above with respect to step 304 of Figure 3. These parameters are described below in more detail.
  • the wireless communication device 212 transmits the message carrying the segment(s) of the segmented message to the base station 202 on the selected bearer (step 404). Note that, in one embodiment, the wireless communication device 212 limits the number of segments of the segmented message and/or the maximum size of the segmented message based on, e.g., the receive buffer size of the base station 202. As discussed above, the maximum number of segments and/or the maximum size of the segmented message may, for example, be dependent on the segmented message and/or dependent on the selected radio bearer.
  • Figure 5 illustrates an example of the process of Figure 3 in which the transmitting radio node is a base station 202 and the receiving radio node is a wireless communication device 212. Again, optional steps are represented by dashed lines/boxes.
  • the base station 202 optionally determines a receive buffer size of the wireless communication device 212 to which it is to transmit a message carrying one or more segments of a segmented message (step 500).
  • the message includes only a single segment of the segment message; however, in other embodiments, the message may include more than one segment (but less than all segments) of the segmented message. As discussed below, in one embodiment, this is done by receiving capability information from the wireless communication device 212 (step 500A).
  • the base station 202 selects a bearer on which to transmit a message that contains one or more segments of a segmented message based on one or more parameters (step 502).
  • the selection of the bearer is the selection of the bearer from a set of available bearers (e.g., a set of configured or defined bearers).
  • the set of available bearers includes at least two bearers (e.g., SIB1 and SIB4 in the case of 3GPP NR).
  • the one or more parameters used by the base station 202 to select the bearer on which to transmit the message that contains segment(s) of the segmented message include any one or more of the parameters listed above with respect to step 304 of Figure 3. These parameters are described below in more detail.
  • the base station 202 transmits the message carrying the segment(s) of the segmented message to the wireless communication device 212 on the selected bearer (step 504).
  • the base station 202 limits the number of segments of the segmented message and/or the maximum size of the segmented message based on, e.g., the receive buffer size of the wireless communication device 212.
  • the maximum number of segments and/or the maximum size of the segmented message may, for example, be dependent on the segmented message and/or dependent on the selected radio bearer.
  • the radio node selects the bearer on which to transmit the message carrying one or more, but potentially multiple, segments of the segmented message as follows:
  • the radio node selects a first bearer if the content of the segmented message of a first content type
  • the radio node selects a second bearer if the content of the segmented message of a second content type.
  • the wireless communication device 212 may select SRB1 for transmission of the message if the segments carried by the message are segments of a WCD or UE capability message.
  • the wireless communication device 212 may select SRB4 for transmission of the message if the segments carried by the message are segments of a QoE related message.
  • the radio node selects the bearer on which to transmit the message carrying one or more, but potentially multiple, segments of a segmented message as follows:
  • the radio node selects a first bearer if the segments are of a segmented message which contains certain IES
  • the radio node selects a second bearer if the segments are of a segmented message which contains other specified IEs.
  • the network may indicate to the wireless communication device 212 (e.g., in step 400 of Figure 4) which bearer a certain message shall be sent on.
  • the network may indicate that the wireless communication device 212 is to send segments of a QoE measurement related message on a certain bearer.
  • the wireless communication device 212 may consider a certain bearer a default bearer.
  • the default bearer may be different for different messages. For example, if a WCD or UE capability related message is segmented, those segments are by default sent on SRB1, while if a QoE measurement related message is segmented, those segments are by default sent on SRB4.
  • the wireless communication device 212 may consider which bearers are configured when determining on which bearer the wireless communication device 212 shall send the segments of a message.
  • the wireless communication device 212 may refrain from sending QoE measurements.
  • the wireless communication device 212 considers different maximum allowed numbers of segments depending on the message which is segmented. For a first segmented message (e.g., carrying a first content type or being of a first segmented message type), the wireless communication device 212 may apply a first number as the maximum number of segments, while, for a second segmented message (e.g., carrying a second content type or being of a second segmented message type), the wireless communication device 212 may apply a second number as the maximum number of segments.
  • a first segmented message e.g., carrying a first content type or being of a first segmented message type
  • the wireless communication device 212 may apply a second number as the maximum number of segments.
  • the maximum allowed number of segments is applied by the wireless communication device 212 by limiting the number of segments of the segmented message to the maximum allowed number of segments, e.g., when dividing the segmented message into segments to be transmitted in messages, such as the message in step 404 of Figure 4.
  • the base station 202 may apply the maximum allowed number of segments as a limit when segmenting the message to provide the segments to be transmitted in messages, such as the message in step 504 of Figure 5.
  • the wireless communication device 212 (UE) may consider the maximum number of segments to be 5 for a segmented UE capability message and consider the maximum number of segments may be 10 for a segmented QoE measurement report.
  • the time it takes for the wireless communication device 212 to transmit these segmented messages can be different.
  • the UE capability message may benefit from reaching the network very quickly, while a QoE measurement report may not be as time critical and hence it can be beneficial if the wireless communication device 212 can create larger messages even if they take a longer time to transmit.
  • the wireless communication device 212 considers different maximum allowed sizes, e.g., measured in kByte, for the message which is to be segmented. For a first segmented message, the wireless communication device 212 may apply a first number as the maximum size, while, for a second message, the wireless communication device 212 may apply a second number as the maximum size.
  • maximum allowed sizes e.g., measured in kByte
  • the maximum allowed number of segments or the maximum allowed size that the wireless communication device 212 may use is, in one example embodiment, configured by the network (e.g., in step 400 of Figure 4).
  • the wireless communication device 212 considers different maximum allowed numbers of segments depending on the bearer on which the message is to be sent. For a message which should be sent on a first bearer, the wireless communication device 212 applies a first number as the maximum number of segments. For a message which should be sent on a second bearer, the wireless communication device 212 applies a second number as the maximum number of segments.
  • the maximum allowed number of segments is applied by the wireless communication device 212 by limiting the number of segments of the segmented message to the maximum allowed number of segments, e.g., when divided the segmented message into segments to be transmitted in messages such as the message in step 404 of Figure 4.
  • the base station 202 may apply the maximum allowed number of segments as a limit when divided the segmented message into segments to be transmitted in messages such as the message in step 504 of Figure 5.
  • the wireless communication device 212 may consider the maximum number of segments to be 5 for messages sent on SRB1, while the wireless communication device 212 may consider the maximum number of segments to be 10 for messages sent on SRB4. This may result in that UE capability related messages can use at most 5 segments in case they are sent on SRB1, while the QoE related messages can use at most 10 segments in case they are sent on SRB4.
  • the time it takes for the wireless communication device 212 to transmit these segmented messages can be different.
  • the UE capability message may benefit from reaching the network very quickly, while a QoE measurement report may not be as time critical and hence it can be beneficial if the wireless communication device 212 can create larger messages even if they take longer time to transmit.
  • the maximum allowed number of segments for different bearers that the wireless communication device 212 may use for sending different messages may be configured by the network (e.g., in step 400 of Figure 4).
  • RRC Message for Segments based on Message Type fs described in the Background section above generic RRC messages have been defined for sending RRC segments in DL and UL, respectively.
  • the current messages have limitations when it comes to how many segments that may be use for an RRC message that needs to be segmented, 5 for DL and 16 for UL.
  • an extension of the current RRC messages for segments can be used.
  • the extension is used to select which bearer is used for transmission.
  • the radio node transmits the message carrying the segments of the segmented message as follows:
  • the node transmits the message carrying the segments of the segmented message on a first bearer (e.g., SRB1) if the legacy RRC message for segments (without extension) is used, and • the node transmits the message carrying the segments of the segmented message on a second bearer (e.g., SRB2) if the RRC message for segments with extension is used.
  • a first bearer e.g., SRB1
  • a second bearer e.g., SRB2
  • a new RRC messages for segments may be defined, for DL and/or UL, respectively.
  • the new RRC message for segments may determine that these segments would be sent on a particular bearer (e.g., SRB4).
  • the network has no knowledge about the receiver buffer size in the wireless communication device 212, except for the minimum requirement defined in 3GPP specifications.
  • the network would need to know if the wireless communication device 212 has implemented a receiver buffer that only fulfills the minimum requirements or if it has a larger receiver buffer size.
  • Such information can be included in the UE radio capability information that the wireless communication device 212sends to the network (e.g., in step 500A of Figure 5). This can be done in any one of the follow ways. However, these are only examples.
  • the wireless communication device 212 indicates the size, e.g., in kByte, of the receiver buffer.
  • the wireless communication device 212 indicates the number of segments it is capable of receiving.
  • the wireless communication device 212 may indicate different limits for different access types, or
  • receiver buffer sizes are defined (e.g., by 3GPP specification) for the receiver buffer size of the wireless communication device 212, and the wireless communication device 212 indicates which of these receiver buffer sizes applies.
  • the receiver buffer sizes are defined and encoded, for example, as follows:
  • the network queries the wireless communication device 212 for the size. For example, the network can send a first QoE configuration message, assuming that the wireless communication device 212 has a 45 kByte receiver buffer, where the QoE configuration message is small enough to not exceed this assumed limit. If the wireless communication device 212 has a larger receiver buffer, it sends a response indicating the actual receiver buffer size. The network may then send another QoE configuration message, which may be larger than the first assumed limit, i.e. larger than 45 kByte.
  • a radio node may:
  • a wireless communication device 212 sends the segments of a message on SRB1 if the message is a WCD or UE capability message, while a wireless communication device 212 sends the segments of a message on SRB1 if the message is a QoE related message and if no more than 5 segments are needed. However, if >5 segments would be needed to send the QoE related message, then the wireless communication device 212 sends the segments on SRB4. It should be understood that other combinations of the above embodiments are also possible.
  • the UE will send the segments on SRB1 or SRB4, depending on which message is carried in the segments.
  • the RRC layer may be implemented in various ways including in a cloud environment.
  • the functionality of the network e.g., of a network node such as, e.g., the base station 202
  • the network can be implemented in a cloud environment.
  • FIG. 6 is a schematic block diagram of a radio access node 600 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes.
  • the radio access node 600 may be, for example, the base station 202 or a network node that implements all or part of the functionality of the base station 202 or gNB as described herein.
  • the radio access node 600 includes a control system 602 that includes one or more processors 604 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 606, and a network interface 608.
  • the one or more processors 604 are also referred to herein as processing circuitry.
  • the radio access node 600 may include one or more radio units 610 that each includes one or more transmitters 612 and one or more receivers 614 coupled to one or more antennas 616.
  • the radio units 610 may be referred to or be part of radio interface circuitry.
  • the radio unit(s) 610 is external to the control system 602 and connected to the control system 602 via, e.g., a wired connection (e.g., an optical cable).
  • the radio unit(s) 610 and potentially the antenna(s) 616 are integrated together with the control system 602.
  • the one or more processors 604 operate to provide one or more functions of the radio access node 600 as described herein (e.g., all or part of the functionality of the base station 202 or gNB as described herein).
  • the function(s) are implemented in software that is stored, e.g., in the memory 606 and executed by the one or more processors 604.
  • Figure 7 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 600 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.
  • a "virtualized" radio access node is an implementation of the radio access node 600 in which at least a portion of the functionality of the radio access node 600 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)).
  • the radio access node 600 may include the control system 602 and/or the one or more radio units 610, as described above.
  • the control system 602 may be connected to the radio unit(s) 610 via, for example, an optical cable or the like.
  • the radio access node 600 includes one or more processing nodes 700 coupled to or included as part of a network(s) 702.
  • Each processing node 700 includes one or more processors 704 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 706, and a network interface 708.
  • processors 704 e.g., CPUs, ASICs, FPGAs, and/or the like
  • functions 710 of the radio access node 600 described herein are implemented at the one or more processing nodes 700 or distributed across the one or more processing nodes 700 and the control system 602 and/or the radio unit(s) 610 in any desired manner.
  • some or all of the functions 710 of the radio access node 600 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environ ment(s) hosted by the processing node(s) 700.
  • control system 602 additional signaling or communication between the processing node(s) 700 and the control system 602 is used in order to carry out at least some of the desired functions 710.
  • the control system 602 may not be included, in which case the radio unit(s) 610 communicate directly with the processing node(s) 700 via an appropriate network interface(s).
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 600 or a node (e.g., a processing node 700) implementing one or more of the functions 710 of the radio access node 600 in a virtual environment according to any of the embodiments described herein is provided.
  • a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • FIG 8 is a schematic block diagram of the radio access node 600 according to some other embodiments of the present disclosure.
  • the radio access node 600 includes one or more modules 800, each of which is implemented in software.
  • the module(s) 800 provide the functionality of the radio access node 600 described herein (e.g., all or part of the functionality of the base station 202 or gNB as described herein). This discussion is equally applicable to the processing node 700 of Figure 7 where the modules 800 may be implemented at one of the processing nodes 700 or distributed across multiple processing nodes 700 and/or distributed across the processing node(s) 700 and the control system 602.
  • FIG. 9 is a schematic block diagram of a wireless communication device 900 according to some embodiments of the present disclosure.
  • the wireless communication device 900 is, for example, the wireless communication device 900 or UE as described above.
  • the wireless communication device 900 includes one or more processors 902 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 904, and one or more transceivers 906 each including one or more transmitters 908 and one or more receivers 910 coupled to one or more antennas 912.
  • the transceiver(s) 906 includes radio-front end circuitry connected to the antenna(s) 912 that is configured to condition signals communicated between the antenna(s) 912 and the processor(s) 902, as will be appreciated by on of ordinary skill in the art.
  • the processors 902 are also referred to herein as processing circuitry.
  • the transceivers 906 are also referred to herein as radio circuitry.
  • the functionality of the wireless communication device 900 described above e.g., all or part of the functionality of the wireless communication device 212 or UE as described herein
  • the wireless communication device 900 may include additional components not illustrated in Figure 9 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 900 and/or allowing output of information from the wireless communication device 900), a power supply (e.g., a battery and associated power circuitry), etc.
  • user interface components e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 900 and/or allowing output of information from the wireless communication device 900
  • a power supply e.g., a battery and associated power circuitry
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 900 according to any of the embodiments described herein is provided.
  • a carrier comprising the aforementioned computer program product is provided.
  • the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • FIG 10 is a schematic block diagram of the wireless communication device 900 according to some other embodiments of the present disclosure.
  • the wireless communication device 900 includes one or more modules 1000, each of which is implemented in software.
  • the module(s) 1000 provide the functionality of the wireless communication device 900 described herein (e.g., all or part of the functionality of the wireless communication device 212 or UE as described herein).
  • a communication system includes a telecommunication network 1100, such as a 3GPP- type cellular network, which comprises an access network 1102, such as a RAN, and a core network 1104.
  • the access network 1102 comprises a plurality of base stations 1106A, 1106B, 1106C, such as Node Bs, eNBs, gNBs, or other types of wireless Access Points (APs), each defining a corresponding coverage area 1108A, 1108B, 1108C.
  • Each base station 1106A, 1106B, 1106C is connectable to the core network 1104 over a wired or wireless connection 1110.
  • a first UE 1112 located in coverage area 1108C is configured to wirelessly connect to, or be paged by, the corresponding base station 1106C.
  • a second UE 1114 in coverage area 1108A is wirelessly connectable to the corresponding base station 1106A. While a plurality of UEs 1112, 1114 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1106.
  • the telecommunication network 1100 is itself connected to a host computer 1116, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm.
  • the host computer 1116 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections 1118 and 1120 between the telecommunication network 1100 and the host computer 1116 may extend directly from the core network 1104 to the host computer 1116 or may go via an optional intermediate network 1122.
  • the intermediate network 1122 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 1122, if any, may be a backbone network or the Internet; in particular, the intermediate network 1122 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 11 as a whole enables connectivity between the connected UEs 1112, 1114 and the host computer 1116.
  • the connectivity may be described as an Over-the-Top (OTT) connection 1124.
  • the host computer 1116 and the connected UEs 1112, 1114 are configured to communicate data and/or signaling via the OTT connection 1124, using the access network 1102, the core network 1104, any intermediate network 1122, and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 1124 may be transparent in the sense that the participating communication devices through which the OTT connection 1124 passes are unaware of routing of uplink and downlink communications.
  • the base station 1106 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 1116 to be forwarded (e.g., handed over) to a connected UE 1112. Similarly, the base station 1106 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1112 towards the host computer 1116.
  • a host computer 1202 comprises hardware 1204 including a communication interface 1206 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 1200.
  • the host computer 1202 further comprises processing circuitry 1208, which may have storage and/or processing capabilities.
  • the processing circuitry 1208 may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the host computer 1202 further comprises software 1210, which is stored in or accessible by the host computer 1202 and executable by the processing circuitry 1208.
  • the software 1210 includes a host application 1212.
  • the host application 1212 may be operable to provide a service to a remote user, such as a UE 1214 connecting via an OTT connection 1216 terminating at the UE 1214 and the host computer 1202.
  • the host application 1212 may provide user data which is transmitted using the OTT connection 1216.
  • the communication system 1200 further includes a base station 1218 provided in a telecommunication system and comprising hardware 1220 enabling it to communicate with the host computer 1202 and with the UE 1214.
  • the hardware 1220 may include a communication interface 1222 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 1200, as well as a radio interface 1224 for setting up and maintaining at least a wireless connection 1226 with the UE 1214 located in a coverage area (not shown in Figure 12) served by the base station 1218.
  • the communication interface 1222 may be configured to facilitate a connection 1228 to the host computer 1202.
  • connection 1228 may be direct or it may pass through a core network (not shown in Figure 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 1220 of the base station 1218 further includes processing circuitry 1230, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the base station 1218 further has software 1232 stored internally or accessible via an external connection.
  • the communication system 1200 further includes the UE 1214 already referred to.
  • the UE's 1214 hardware 1234 may include a radio interface 1236 configured to set up and maintain a wireless connection 1226 with a base station serving a coverage area in which the UE 1214 is currently located.
  • the hardware 1234 of the UE 1214 further includes processing circuitry 1238, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the UE 1214 further comprises software 1240, which is stored in or accessible by the UE 1214 and executable by the processing circuitry 1238.
  • the software 1240 includes a client application 1242.
  • the client application 1242 may be operable to provide a service to a human or non-human user via the UE 1214, with the support of the host computer 1202.
  • the executing host application 1212 may communicate with the executing client application 1242 via the OTT connection 1216 terminating at the UE 1214 and the host computer 1202.
  • the client application 1242 may receive request data from the host application 1212 and provide user data in response to the request data.
  • the OTT connection 1216 may transfer both the request data and the user data.
  • the client application 1242 may interact with the user to generate the user data that it provides.
  • the host computer 1202, the base station 1218, and the UE 1214 illustrated in Figure 12 may be similar or identical to the host computer 1116, one of the base stations 1106A, 1106B, 1106C, and one of the UEs 1112, 1114 of Figure 11, respectively.
  • the inner workings of these entities may be as shown in Figure 12 and independently, the surrounding network topology may be that of Figure 11.
  • the OTT connection 1216 has been drawn abstractly to illustrate the communication between the host computer 1202 and the UE 1214 via the base station 1218 without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the network infrastructure may determine the routing, which may be configured to hide from the UE 1214 or from the service provider operating the host computer 1202, or both. While the OTT connection 1216 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 1226 between the UE 1214 and the base station 1218 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1214 using the OTT connection 1216, in which the wireless connection 1226 forms the last segment.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 1216 may be implemented in the software 1210 and the hardware 1204 of the host computer 1202 or in the software 1240 and the hardware 1234 of the UE 1214, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 1216 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 1210, 1240 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1216 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 1218, and it may be unknown or imperceptible to the base station 1218.
  • measurements may involve proprietary UE signaling facilitating the host computer 1202's measurements of throughput, propagation times, latency, and the like.
  • the measurements may be implemented in that the software 1210 and 1240 causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 1216 while it monitors propagation times, errors, etc.
  • FIG. 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section.
  • the host computer provides user data.
  • sub-step 1302 (which may be optional) of step 1300, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 1306 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1308 the UE executes a client application associated with the host application executed by the host computer.
  • FIG 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1404 (which may be optional), the UE receives the user data carried in the transmission.
  • FIG. 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section.
  • the UE receives input data provided by the host computer. Additionally or alternatively, in step 1502, the UE provides user data.
  • sub-step 1504 (which may be optional) of step 1500, the UE provides the user data by executing a client application.
  • sub-step 1506 (which may be optional) of step 1502, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in sub-step 1508 (which may be optional), transmission of the user data to the host computer. In step 1510 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 1604 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • Embodiment 1 A method performed by a radio node (202; 212), the method comprising selecting (304) a bearer for a transmission of a message that contains one or more segments of a segmented message based on one or more parameters.
  • Embodiment 2 The method of embodiment 1 further comprising transmitting (306) the message on the selected bearer.
  • Embodiment 3 The method of embodiment 1 or 2 wherein the one or more segments are one or more segments of a Radio Resource Control, RRC, message.
  • RRC Radio Resource Control
  • Embodiment 4 The method of any of embodiments 1 to 3 wherein the one or more parameters comprise: (a) content of the segmented message; (b) content type of the content the segmented message; (c) information elements, IES, comprised in the segmented message; (d) a configuration received from a network node; (e) a configuration received from a network node, where the configuration indicates a bearer to be used for transmission for each of one or more groups of segmented messages (e.g., groups of segmented messages that carry particular different content or groups of segmented message of different message types); (f) a defined or configured default bearer; (g) whether one or more certain bearers are configured for the radio node to use; (h) a message type (e.g., RRC message type) of the message that contains the segments of the segmented message; or (i) a combination of any two or more of (a)- (h).
  • a message type e.g., RRC message type
  • Embodiment 5 The method of any of embodiments 1 to 4 wherein a maximum number of segments or a maximum size is applied to limit the number of segments or the size of the message.
  • Embodiment 6 The method of embodiment 5 wherein the maximum number of segments or the maximum size is based on the message or the segmented message (e.g., based on the content of the segmented message or a message type of the message).
  • Embodiment 7 The method of embodiment 5 wherein the maximum number of segments or the maximum size is based on the selected bearer.
  • Embodiment 8 The method of any of embodiments 1 to 7 wherein the radio node is a wireless communication device (212).
  • Embodiment 9 The method of embodiment 8 further comprising receiving (400) configuration information from a network node (212), the configuration information comprising information that indicates a particular bearer to be used for transmission based on message type and/or based on content of the segmented message.
  • Embodiment 10 The method of embodiment 8 or 9, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.
  • Embodiment 11 The method of any of embodiments 1 to 7 wherein the radio node is a base station (202).
  • Embodiment 12 The method of embodiment 11 further comprising receiving (500), from a wireless communication device (212) to which the message is to be transmitted, information that indicates a receiver buffer size of the wireless communication device (212), and a maximum number of segments of the segmented message or a maximum size of the segmented message is based on the receiver buffer size.
  • Embodiment 13 The method of embodiment 11 or 12, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless communication device.
  • Embodiment 14 A wireless communication device comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the wireless communication device.
  • Embodiment 15 A base station comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the base station.
  • Embodiment 16 A User Equipment, UE, comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • an antenna configured to send and receive wireless signals
  • radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry
  • the processing circuitry being configured to perform any of the steps of any of the Group A embodiments
  • an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry
  • Embodiment 17 A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a User Equipment, UE; wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a User Equipment, UE; wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • Embodiment 18 The communication system of the previous embodiment further including the base station.
  • Embodiment 19 The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
  • Embodiment 20 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • Embodiment 21 A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
  • Embodiment 22 The method of the previous embodiment, further comprising, at the base station, transmitting the user data.
  • Embodiment 23 The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.
  • Embodiment 24 A User Equipment, UE, configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform the method of the previous 3 embodiments.
  • Embodiment 25 A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a User Equipment, UE; wherein the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any of the Group A embodiments.
  • Embodiment 26 The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
  • Embodiment 27 The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE's processing circuitry is configured to execute a client application associated with the host application.
  • Embodiment 28 A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.
  • Embodiment 29 The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.
  • Embodiment 30 A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station; wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • a host computer comprising: communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station; wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • Embodiment 31 The communication system of the previous embodiment, further including the UE.
  • Embodiment 32 The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • Embodiment 33 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • Embodiment 34 The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • Embodiment 35 A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • Embodiment 36 The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.
  • Embodiment 37 The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.
  • Embodiment 38 The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application; wherein the user data to be transmitted is provided by the client application in response to the input data.
  • Embodiment 39 A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • a host computer comprising a communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • Embodiment 40 The communication system of the previous embodiment further including the base station.
  • Embodiment 41 The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
  • Embodiment 42 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • Embodiment 43 A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • Embodiment 44 The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.
  • Embodiment 45 The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes et des procédés de sélection de support radio lors de la transmission d'un message segmenté. Dans un mode de réalisation, un procédé mis en œuvre par un nœud radio comprend la sélection, sur la base d'un ou de plusieurs paramètres, d'un support pour une transmission d'un message qui contient un ou plusieurs segments d'un message segmenté. Dans un mode de réalisation, le procédé comprend en outre la transmission du message sur le support sélectionné. Dans un mode de réalisation, le message segmenté est un message de commande de ressources radio (RRC) segmenté, et le ou les segments constituent un ou plusieurs segments du message RRC segmenté mais moins que tous les segments du message RRC segmenté. Dans un mode de réalisation, le ou les paramètres comprennent un contenu du message segmenté, un type de contenu du message segmenté, des éléments d'informations (IE) compris dans le message segmenté, une configuration reçue, un support par défaut, si certains supports sont configurés pour une utilisation et/ou un type de message.
PCT/SE2021/051291 2021-01-14 2021-12-20 Sélection de support pour segmentation WO2022154711A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163137452P 2021-01-14 2021-01-14
US63/137,452 2021-01-14

Publications (1)

Publication Number Publication Date
WO2022154711A1 true WO2022154711A1 (fr) 2022-07-21

Family

ID=79282941

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2021/051291 WO2022154711A1 (fr) 2021-01-14 2021-12-20 Sélection de support pour segmentation

Country Status (1)

Country Link
WO (1) WO2022154711A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200068447A1 (en) * 2017-04-25 2020-02-27 China Academy Of Telecommunications Technology Communication method and device

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200068447A1 (en) * 2017-04-25 2020-02-27 China Academy Of Telecommunications Technology Communication method and device

Non-Patent Citations (11)

* Cited by examiner, † Cited by third party
Title
"Radio Resource Management Strategies in UMTS", 17 June 2005, JOHN WILEY & SONS, Chichester, ISBN: 978-0-470-02277-1, article PÉREZ-ROMERO JORDI ET AL: "UMTS Radio Interface Description : Perez-Romero/Radio Resource Management Strategies in UMTS", pages: 47 - 118, XP055900030, DOI: 10.1002/0470022795.ch3 *
3GPP TS 25.331
3GPP TS 27.007
3GPP TS 36.331
3GPP TS 37.873
3GPP TS 38.331
CHINA UNICOM (RAPPORTEUR): "Email discussion summary on solutions for LTE QMC", vol. RAN WG2, no. Berlin, Germany; 20170821 - 20170825, 20 August 2017 (2017-08-20), XP051318193, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20170820] *
ERICSSON: "Configuration and reporting of QoE measurements", vol. RAN WG2, no. Electronic meeting; 20210809 - 20210827, 6 August 2021 (2021-08-06), XP052034619, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_115-e/Docs/R2-2108109.zip R2-2108109 - Configuration and reporting of QoE measurements.docx> [retrieved on 20210806] *
ERICSSON: "NR QoE Measurement Triggering, Configuration, Collection and Reporting", vol. RAN WG2, no. Electronic meeting; 20200817 - 20200828, 6 August 2020 (2020-08-06), XP051911074, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_111-e/Docs/R2-2007600.zip R2-2007600 - NR QoE Measurement Triggering, Configuration, Collection and Reporting.docx> [retrieved on 20200806] *
ERICSSON: "Proposed CR on update of interfrequency measurement cell info list, reading of SIB11/12, inclusion of Measured Results on RACH", 3GPP DRAFT; R2-030763 MEASUREMENT ISSUES, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Seoul, Korea; 20030403, 3 April 2003 (2003-04-03), XP050123342 *
SAMSUNG: "Transfer of segmented UECapabilityInformation by SRB2", vol. RAN WG2, no. Elbonia; 20200224 - 20200306, 14 February 2020 (2020-02-14), XP051849316, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_109_e/Docs/R2-2000765.zip R2-2000765 Transfer of segmented UECapabilityInformation by SRB2.doc> [retrieved on 20200214] *

Similar Documents

Publication Publication Date Title
US11778493B2 (en) Data collection method, device, and system
EP3493591B1 (fr) Procédé de commande de transmission de service et dispositif associé
KR101901953B1 (ko) 보고 수신 방법 및 네트워크 장치, 그리고 보고 수행 방법 및 기지국
US11395256B2 (en) Communication method, device, and system
WO2019104685A1 (fr) Procédé de communication et dispositif de communication
US20230044291A1 (en) RRC SEGMENTATION AND QoE
EP3791681A1 (fr) Procédés permettant de suspendre un état inactif lors de la reprise et de reprendre l&#39;état inactif lors de la suspension
US20220014901A1 (en) Method and apparatus for identifying user equipment capability in sidelink transmission
US20220394519A1 (en) Systems and methods for validating parameters
CN110050415B (zh) 用于上行链路传送的方法和设备
WO2018228558A1 (fr) Procédé de transmission de données, dispositif de réseau et dispositif terminal
JP2023504763A (ja) QoSマッピング
EP3975592A1 (fr) Procédé de communication, dispositif terminal et dispositif de réseau
WO2021162627A1 (fr) Gestion de priorisation de liaison montante intra-équipement utilisateur
WO2022179367A1 (fr) Nouveau procédé de fourniture de paramètres externes pour une session af
US20230292173A1 (en) Autonomous activation of a feature at a wireless communication device to meet survival time of an application consuming a communication service
US20230021043A1 (en) HANDLING OVERLAPPING OF MULTIPLE PHYSICAL UPLINK SHARED CHANNELS (PUSCHs)
WO2022154711A1 (fr) Sélection de support pour segmentation
WO2020159419A1 (fr) Spécification de contenu de rapport de qualité dans msg3
EP4233449B1 (fr) Commutation de branche ul en mode de double connectivité avec agrégation de porteuses
WO2014000611A1 (fr) Procédé et dispositif de transmission de données
US20230224998A1 (en) Small data transmission
US20240007905A1 (en) Dynamic change of active queue management (aqm) location
WO2021230800A1 (fr) Support radio à surdébit réduit
WO2022238911A1 (fr) Direction commandée d&#39;un équipement utilisateur à la suite d&#39;un découpage en tranches

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21839706

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21839706

Country of ref document: EP

Kind code of ref document: A1