Packet data communication

Abstract

According to an example aspect of the present invention, there is provided an apparatus configured to compile a medium access control, MAC, packet data unit, PDU, the MAC PDU comprising plural sub-packet data units, sub-PDUs, each sub-PDU comprising a subheader which comprises a logical channel identifier, the apparatus being configured to process data sub-PDUs and control sub- PDUs, include in the MAC PDU at least one of a contiguous block of data sub-PDUs or a contiguous block of control sub-PDUs, and include in the MAC PDU a preconfigured logical channel identifier before a predetermined one of the contiguous blocks to indicate that the predetermined one of the contiguous blocks begins, when the MAC PDU comprises the predetermined one of the contiguous blocks.

Description

PACKET DATA COMMUNICATIONFIELD

[0001] The present disclosure relates to packet-based communication of data, such as, for example, in the context of cellular wireless networking.BACKGROUND

[0002] Packet-based communication involves conducting communications by transmitting and receiving packets of data. The packets may be of the same size or differing sizes, and a data stream may be conveyed using a stream of packets. Packets communicated in a network, or over a single interface in the network, may originate in different nodes, or in different applications in a single node. When packets become available for transmission over an interface which is busy, the packets may be placed in a queue, from which they are then transmitted when the interface becomes available. Data packets may be encapsulated into a larger protocol data unit, for later decapsulation at another node.SUMMARY

[0003] According to some aspects, there is provided the subject-matter of the independent claims. Some embodiments are defined in the dependent claims. The scope of protection sought for various embodiments of the invention is set out by the independent claims. The embodiments, examples and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the invention.

[0004] According to a first aspect of the present disclosure, there is provided an apparatus comprising at least one processing core and at least one memory storing instructions that, when executed by the at least one processing core, cause the apparatus at least to compile a medium access control, MAC, packet data unit, PDU, the MAC PDU comprising plural sub-packet data units, sub-PDUs, each sub-PDU comprising a subheader which comprises a logical channel identifier, the apparatus being configured to process datasub-PDUs and control sub-PDUs, include in the MAC PDU at least one of a contiguous block of data sub-PDUs or a contiguous block of control sub-PDUs, and include in the MAC PDU a preconfigured logical channel identifier before a predetermined one of the contiguous blocks to indicate that the predetermined one of the contiguous blocks begins, when the MAC PDU comprises the predetermined one of the contiguous blocks.

[0005] According to a second aspect of the present disclosure, there is provided a method comprising compiling a medium access control, MAC, packet data unit, PDU, the MAC PDU comprising plural sub-packet data units, sub-PDUs, each sub-PDU comprising a subheader which comprises a logical channel identifier, including in the MAC PDU at least one of a contiguous block of data sub-PDUs or a contiguous block of control sub-PDUs, and including in the MAC PDU a preconfigured logical channel identifier before a predetermined one of the contiguous blocks to indicate that the predetermined one of the contiguous blocks begins, when the MAC PDU comprises the predetermined one of the contiguous blocks.

[0006] According to a third aspect of the present disclosure, there is provided a non- transitory computer readable medium having stored thereon a set of computer readable instructions that, when executed by at least one processor, cause an apparatus to at least compile a medium access control, MAC, packet data unit, PDU, the MAC PDU comprising plural sub-packet data units, sub-PDUs, each sub-PDU comprising a subheader which comprises a logical channel identifier, the set of computer readable instructions being configured to process data sub-PDUs and control sub-PDUs, include in the MAC PDU at least one of a contiguous block of data sub-PDUs or a contiguous block of control sub-PDUs, and include in the MAC PDU a preconfigured logical channel identifier before a predetermined one of the contiguous blocks to indicate that the predetermined one of the contiguous blocks begins, when the MAC PDU comprises the predetermined one of the contiguous blocks.

[0007] According to a fourth aspect of the present disclosure, there is provided an apparatus comprising means for compiling a medium access control, MAC, packet data unit, PDU, the MAC PDU comprising plural sub-packet data units, sub-PDUs, each sub-PDU comprising a subheader which comprises a logical channel identifier, including in the MAC PDU at least one of a contiguous block of data sub-PDUs or a contiguous block of control sub-PDUs, and including in the MAC PDU a preconfigured logical channel identifier beforea predetermined one of the contiguous blocks to indicate that the predetermined one of the contiguous blocks begins, when the MAC PDU comprises the predetermined one of the contiguous blocks.

[0008] According to a fifth aspect of the present disclosure, there is provided an apparatus comprising at least one processing core and at least one memory storing instructions that, when executed by the at least one processing core, cause the apparatus at least to receive a medium access control, MAC, packet data unit, PDU, the MAC PDU comprising plural sub-packet data units, sub-PDUs, each sub-PDU comprising a subheader which comprises a logical channel identifier, the MAC PDU comprising at least one of a contiguous block of data sub-PDUs or a contiguous block of control sub-PDUs, and determine based on a preconfigured logical channel identifier in the MAC PDU that a predetermined one of the contiguous blocks begins after the preconfigured logical channel identifier, the MAC PDU comprising the predetermined one of the contiguous blocks.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] FIGURE 1 illustrates an example system in accordance with at least some embodiments of the present invention;

[0010] FIGURE 2A illustrates a first MAC PDU in accordance with at least some embodiments of the present disclosure;

[0011] FIGURE 2B illustrates a second MAC PDU in accordance with at least some embodiments of the present disclosure;

[0012] FIGURE 3 illustrates an example apparatus capable of supporting at least some embodiments of the present invention;

[0013] FIGURE 4 illustrates signalling in accordance with at least some embodiments of the present invention, and

[0014] FIGURE 5 is a flow graph of a method in accordance with at least some embodiments of the present invention.EMBODIMENTS

[0015] Disclosed herein are methods to construct a medium access control, MAC, protocol data unit, PDU, wherein data and control parts are separated into contiguous blocks. This facilitates the handling of such MAC PDUs in nodes where the data and control parts may be processed in pipeline, optionally such that the MAC PDU is begun to be fed to a transmitter or MAC layer before it has been fully encoded or decoded, respectively. This provides the benefit that handling of the MAC PDU is faster, saving time. Further, providing the data and control parts in contiguous blocks has the effect that an indication, such as a bit, is not needed in each subheader to indicate whether control or data is present after this subheader, enhancing communication efficiency. Further, subheaders may be made equal in size, which facilitates their processing in hardware. When data and control sub-PDUs are handled in different hardware processing cores, the structures of data and control sub-PDU subheaders may be made different, for example, data sub-PDUs may be provided with subheaders of equal size to facilitate HW processing whereas among control sub-PDUs subheader size may be allowed to differ.

[0016] FIGURE 1 illustrates an example system in accordance with at least some embodiments of the present invention. This system includes base stations 130, 135 in communication with user equipments, UEs, such as UE 110. A radio link connects base station 130 with UE 110. The radio link may be bidirectional, comprising an uplink, UL, to convey information from UE 110 toward base station 130, and a downlink, DL, to convey information from the base station 130 toward UE 110. A cellular communication system may comprise hundreds or thousands of base stations, of which only two are illustrated in FIGURE 1 for the sake of clarity of the illustration. The base stations may be distributed in that they comprise a centralized unit, CU, and one or more distributed unit, DU. A base station is an example of a base node.

[0017] Base station 130 is further coupled communicatively with core network node 140, which may comprise, for example, an evolved packet core, EPC, mobility management entity, MME, a home subscriber server, HSS, a 5G unified data repository, UDR, a call session control function, CSCF, or a 5G access and mobility management function, AMF. The core network node 140 may be coupled with further core network nodes, and with a network 150, which may comprise the Internet or a corporate network, for example. The system may communicate with further networks via network 150. Examples of the further core network nodes, which are not illustrated in FIGURE 1 for the sake of clarity, include gateways and subscriber information repositories. Core network nodes may be virtualized inthe sense that they may run as software modules on computing substrates, such that more than one virtualized network node may run on a same physical computing substrate. The network may be configured to function in accordance with a suitable cellular standard such as long term evolution, LTE, fifth generation, 5G, which is also known as New Radio, NR, or sixth generation, 6G standards as defined by the 3rdgeneration partnership project, 3GPP. To obtain interoperation, UEs attaching to the network are configured to support a same standard as the network.

[0018] Base station 130 controls, in the example of FIGURE 1 cells 130A and 130B, of which UE 110 is in the situation illustrated in FIGURE 1 attached with cell 130A, and base station 135 controls, in the example of FIGURE 1, cells 135A and 135B. The number of cells, or beams, may be in excess of what is illustrated in FIGURE 1. It is also possible that a base station has a single cell or beam. While illustrated as sector-shaped, cells of a same base station may be omnidirectional and operate on different frequencies, for example. A mobility event may comprise a switch from one beam to another beam of the same cell, or a switch from one cell to another cell. To support mobility procedures, UEs, including UE 110, are configured to conduct mobility measurements to measure signal strengths of adjacent beams and / or cells, and report results of these measurements to the network, which may then take a decision concerning a mobility event, such as a beam change or a cell switch.

[0019] Base stations, BS, such as base stations 130 and 135, are configured to transmit various kinds of information to UEs. In addition to payload, such as the content of voice and video calls, application data and transferred user files, base stations transmit various kinds of configuration information to control the functioning of UEs in their cells. This configuration information includes grants to use air interface resources for UL and DL, for example.

[0020] Information exchanged between BSs and UEs may be conveyed using a layer model, wherein a layer- 1 comprises a physical layer responsible for the transmission and reception of unstructured raw data. Layer- 1 provides transmission and reception of data between a device and a physical transmission medium. A layer-2 data link layer comprises a MAC layer and a logical link control, LLC, layer. Layer-2 provides node-to-node data transfer, wherein the MAC layer controls how nodes gain access to transmission medium to transmit data, and the LLC layer identifies and encapsulates network layer protocols, and performs error checking and frame synchronization. Layer-3 is a network layer whichprovides means of transferring packets from one node to another connected in networks. A radio resource control, RRC, function is performed on layer-3, for example. Layer-4 is a transport layer for conveying data sequences from a source to a destination node across a network, while controlling quality of service, QoS, procedures. Layer-5 is a session layer, layer-6 a presentation layer and finally layer-7 is the application layer which uses the lower layers to accomplish user-level tasks.

[0021] A MAC PDU, in general, comprises one or more of the following: A MAC subheader only, including padding in the subheader, A MAC subheader and a MAC service data unit, SDU, A MAC subheader and a MAC control element, CE, and finally A MAC subheader and padding. In particular, a MAC PDU may comprise plural sub-PDUs with MAC SDUs and plural sub-PDUs with MAC CEs. In general, control sub-PDUs include a MAC CE as payload, and data sub-PDUs include a MAC SDU as payload. In more general terms, control sub-PDUs may also include an SDU of a Signaling Radio Bearer, SRB, as payload or an SDU of a Data Radio Bearer, DRB, as payload (e.g., low data rate applications).

[0022] Disclosed herein are ways to compile a MAC PDU such that data and control are separated to contiguous blocks, and a preconfigured logical channel identifier is used to indicate the start of either the contiguous data block or the contiguous control block, as will be described in more detail herein below. When the contiguous data block is positioned first in the MAC PDU, the preconfigured logical channel identifier is used to indicate the start of the contiguous control block and when the contiguous control block is positioned first in the MAC PDU, the preconfigured logical channel identifier is used to indicate the start of the contiguous data block. In the former case the contiguous control block is a predetermined one of the contiguous blocks, and in the latter case the contiguous data block is the predetermined one of the contiguous blocks. Using a specific logical channel identifier to indicate the start of the contiguous block which is first in the MAC PDU is not necessary, since the start of this contiguous block is implicitly indicated by the start of the MAC PDU. If this contiguous block is absent, and the MAC PDU comprises only the contiguous block which would be second in the sequence of contiguous blocks if both blocks were present, the preconfigured logical channel identifier may be entered at the start of the MAC PDU to inform the receiver of the type of sub-PDUs which follow.

[0023] The preconfigured logical channel identifier may be provided in the MAC PDU outside of a sub-PDU or in a sub-PDU which doesn’t comprise a MAC CE or MAC SDU. The preconfigured logical channel identifier may thus indicate that a contiguous block of the sub-PDUs of the predetermined type begins without indicating a specific logical channel that a payload of the sub-PDU where the preconfigured logical channel identifier relates to. A subheader with the preconfigured LCID may be considered to be a MAC CE which has fixed size of zero bits.

[0024] Subheader size and subheader content may be fixed for data sub-PDUs including data, that is, at least data radio bearer data and possibly also signalling radio bearer, SRB, data. Optionally, subheader size and content can vary for MAC CEs and possibly also MAC SDUs for SRBs.

[0025] FIGURE 2 A illustrates a first MAC PDU 201 in accordance with at least some embodiments of the present disclosure. MAC PDU 201 of FIGURE 2A is arranged so that it comprises first a contiguous block of control sub-PDUs 210, 220, followed by a contiguous block of data sub-PDUs 230 ... 240. The three dots indicate that the number of data sub- PDUs may be in excess of three, and likewise the number of control sub-PDUs in the contiguous block of control sub-PDUs may be in excess of two, or may comprise only a single control sub-PDU.

[0026] By a contiguous block of control sub-PDUs it is meant a sequence of control sub-PDUs with no data sub-PDUs therein between. By a contiguous block of data sub-PDUs it is meant a sequence of data sub-PDUs with no control sub-PDUs therein between.

[0027] In PAC PDU 201, a first control sub-PDU 210 comprises a subheader 212 and a MAC CE 214. A second control sub-PDU 220 comprises a subheader 222 and a MAC CE 224. These are followed in MAC PDU 201 by a preconfigured logical channel identifier, LCID, 205, which signifies that the contiguous block of data sub-PDUs in MAC PDU 201 begins. The receiving node may then conclude, that all sub-PDUs after logical channel identifier 205 are data sub-PDUs. The receiving node may likewise conclude that sub-PDUs 210, 220 are control sub-PDUs since they do not follow preconfigured LCID 205. First data sub-PDU 230 comprises subheader 232 and MAC SDU 234, and the last data sub-PDU 240 comprises subheader 242 and MAC SDU 244. Padding may be appended to the end of MAC PDU 201, which is not illustrated in FIGURE 2A, to obtain a desired length of MAC PDU 201.

[0028] The inclusion of preconfigured LCID 205 provides technical benefits in the compilation and handling of PAC PDU 201. For example, subheaders 212, 222, 232, . . . , 242 need not comprise a separate indicator, such as a bit, to indicate whether they are comprised in a data sub-PDU or a control sub-PDU, since this may be determined from how their location in MAC PDU 201 relates to the location of preconfigured LCID 205. Thus the size of MAC PDU 201 may be made smaller, without reducing the quantity of payload MAC CEs and MAC SDUs carried therein. Further, as the control sub-PDUs and the data sub- PDUs are in contiguous blocks, they can be fed to distinct hardware processing cores for rapid handling, which facilitates processing of high-bitrate data in the MAC SDUs.

[0029] The preconfigured LCID 205 which indicates the start of the contiguous block of data sub-PDUs may be hard-coded in a receiver during manufacture, or it may be configured by a network node during operation.

[0030] In a variant of the MAC PDU of FIGURE 2A, there are no control sub-PDUs present, in which case the MAC PDU begins with preconfigured LCID 205 to inform the receiver that what follows are data sub-PDUs. Likewise, in the event there happen to be no data sub-PDUs in MAC PDU 201, the MAC PDU will comprise merely control sub-PDUs and preconfigured LCID 205 is not included at all, since it indicates the start of the contiguous block of data sub-PDUs and this contiguous block doesn’t start in such a MAC PDU which lacks data sub-PDUs. In all these variants, and the one illustrated in FIGURE 2A, the sizes of data sub-PDU subheaders 232, . . ., 242 may be the same to facilitate rapid hardware processing of the data sub-PDUs. Also when the size of data sub-PDU subheaders is constant, the sizes of the control sub-PDU subheaders may be allowed to vary.

[0031] FIGURE 2B illustrates a second MAC PDU 202 in accordance with at least some embodiments of the present disclosure. MAC PDU 202 of FIGURE 2B resembles that of FIGURE 2A, however here a contiguous block of data sub-PDUs 250, 260 is first in the MAC PDU, and a contiguous block of control sub-PDUs 270, . . . , 280 is after it. In this case, a second preconfigured LCID 206 signifies the start of the contiguous block of control sub- PDUs, unlike in FIGURE 2A where preconfigured LCID 205 signifies the start of the contiguous block of data sub-PDUs. Data sub-PDUs 250, 260 comprise a subheader 252, 262, and a MAC SDU 254, 264, respectively, as illustrated. On the other hand the control sub-PDUs 270, ..., 280 comprise a subheader 272, ..., 282, and a MAC CE 274, ..., 284, respectively, as illustrated.

[0032] The MAC PDU 202 of FIGURE 2B provides the same benefits as that of FIGURE 2A in terms of being well suited to processing the control and data sub-PDUs in distinct hardware processing cores, for example. Also, as the second preconfigured LCID 206 is used to identify the contiguous block of control sub-PDUs and, implicitly, also the contiguous block of data sub-PDUs which is before it, also here a benefit is obtained in terms of making the subheaders smaller as they need not indicate for each sub-PDU separately whether it is of the control or data type. When no separate data / control indicator bit is used, the subheader may be made smaller, or a longer LCID may be used enabling use of more logical channels.

[0033] The preconfigured LCID 206 which indicates the start of the contiguous block of control sub-PDUs may be hard-coded in a receiver during manufacture, or it may be configured by a network node during operation.

[0034] In a variant of the MAC PDU of FIGURE 2B, there are no data sub-PDUs present, in which case the MAC PDU begins with second preconfigured LCID 206 to inform the receiver that what follows are control sub-PDUs. Likewise, in the event there happen to be no control sub-PDUs in MAC PDU 202, the MAC PDU will comprise merely data sub- PDUs and second preconfigured LCID 206 is not included at all, since it indicates the start of the contiguous block of control sub-PDUs and this contiguous block doesn’t start in such a MAC PDU. In all these variants, and the one illustrated in FIGURE 2B, the sizes of data sub-PDU subheaders 252, 262 may be the same to facilitate rapid hardware processing of the data sub-PDUs. Also when the size of data sub-PDU subheaders is fixed the sizes of the control sub-PDU subheaders may be allowed to vary.

[0035] In some embodiments, the solutions of FIGURE 2A and / or FIGURE 2B are adapted so that encapsulation of at least a part of payload of the control sub-PDUs, that is the MAC CEs, into a data sub-PDU MAC SDU is performed. Alternatively, payload of at least a part of low data rate data sub-PDU MAC SDUs is performed into a high data rate data sub-PDU MAC SDU. In these embodiments, a subheader of the data sub-PDU into which the encapsulating is performed may be selected so as to comprise a LCID which indicates that this data sub-PDU comprises MAC CE payload and / or the at least the part of the low data rate MAC SDU(s). This MAC SDU comprising the encapsulated information would be handled in hardware configured to process data sub-PDUs in systems which have distinct hardware processing cores for the data sub-PDUs and control sub-PDUs. In some ofthese embodiments, a single high-bitrate MAC SDU may comprise encapsulated therein both at least one MAC CE and at least one low-bit rate MAC SDU. The logical channel identifier in the subheader accompanying this high-bitrate MAC SDU may identify the encapsulation type as either control, low-bitrate data or a combination of control and low- bitrate data, in other words, three logical channel identifiers may be reserved for this indication.

[0036] When a MAC CE is encapsulated in a high-bitrate MAC SDU, a technical advantage is obtained in that it is available earlier as high-bitrate MAC SDUs may be processed using more capable hardware. Further or alternatively, in MAC PDUs as illustrated in FIGURE 2B where data is first, the MAC SDU comprising the encapsulated MAC CE(s) is available in the receiver before any non-encapsulated MAC CEs are. Thus time would be gained in the latter case even if the encapsulating MAC SDU is not high-data rate in nature.

[0037] In some embodiments, a transmitter is configured to select an arrangement for the MAC PDU based on a type of resource grant used to communicate the MAC PDU. For example, if an UL grant is a Msg3 or MsgA grant of a random access procedure, the control sub-PDUs may be put before data sub-PDUs. As another example, if the UL grant is an UL grant for initial physical uplink shared channel, PUSCH, transmission in a small data transmission, SDT, procedure or in general a RRC Resume, RRC Setup or RRC Reestablishment procedure, after a handover procedure, the control sub-PDUs may be put before data sub-PDUs. Thus a selection of the FIGURE 2A or 2B embodiment may be made dynamically based on a type of a grant.

[0038] Otherwise, if a grant type is not used to select which contiguous block to place first, control sub-PDUs may be placed in front of the MAC PDU in the downlink direction and at the end of the MAC PDU in the uplink direction. A motivation for this comes from UE processing: the MAC CEs being in front of the MAC PDU in DL allows UE to start processing the MAC CEs already at MAC before the whole MAC PDU may not even have been processed by the physical layer, whereas placing MAC CEs at the end of the MAC PDU in UL allows UE the most time in preparing the MAC CEs in real time, such as buffer status reporting, BSR, which needs to account also the data that was multiplexed in the MAC PDU where the BSR is transmitted.

[0039] LCID for either or both the control and data LCID space(s) may be allocated to indicate the start of the control or the data part of the MAC PDU, respectively. The LCID space for data and control may be either the same space, or different spaces. When the spaces are different, they may overlap in part, or be non-overlapping.

[0040] A node compiling the MAC PDU may process the data sub-PDUs in a physical processing core distinct from a main processor of the node. Likewise, a receiver node processing the received MAC PDU may process the data sub-PDUs in a physical processing core distinct from a main processor of the receiving node.

[0041] Turning then to the subheaders and their constituent fields in more detail, a subheader of a data sub-PDU may have the following fields:

[0042] Here each row is an octet, that is, eight bits. The one-bit R fields for R bits are reserved, the LCID to be input into the LCID field is a logical channel identifier of five bits and lengths fields L are used to indicate a length of the MAC SDU of the sub-PDU in which this subheader is comprised.

[0043] The following is an example of an LCID-only subheader suitable for including, for example, the preconfigured LCID 205 or second preconfigured LCID 206:

[0044] In the examples presented above, the LCIDD space of 5 bits is long enough for data sub-PDUs which allows exploitation of up to 30 LCID values for data radio bearers, DRBs, or associated logical channels. One specific LCID value could be preconfigured, as described herein above, to indicate the start of the control part in the MAC PDU (e.g., ’00000'), for example, while another one may be used to indicate a start of padding in the remaining part of the MAC PDU (e.g., ‘ 11111’).

[0045] In one example, control sub-PDU subheaders have the following structure:

[0046] This LCIDc only subheader can be used for fixed sized MAC CEs, wherein no length field required since the fixed length of the MAC CE is known. It may also be used for indication of the start of the contiguous block of data sub-PDUs in MAC PDU where control sub-PDUs are first, and the indication of the start of the padding in the remaining part of the MAC PDU after the control and data sub-PDUs.

[0047] The LCIDc + 1-byte L shown above may be used for variable-sized MAC CEs, which often require only a 1-byte length field. The presence of the L-field in the subheader may be deduced from the LCIDc value by the receiving MAC entity. The following LCIDc + 2 -byte length field subheader may be used signaling radio bearer, SRB, data and any DRBs transmitted using the control part of the MAC PDU, such as low bit rate data. The availability of the L field in the MAC subheader may be deduced from the LCIDc value by the receiving MAC entity (e.g., LCIDc mapped to SRB or DRB):

[0048] Sometimes an extended LCID, eLCID, is used. In the following LCIDc + eLCIDc subheader may be used for fixed-size MAC CEs, where no length field is required. Specific LCIDc values could be used to indicate the availability of eLCIDc:

[0049] Finally, the following LCIDc + eLCIDc + 1-byte L subheader may be used for variable-sized MAC CEs, where the length field is needed. The availability of the L field in the subheader may be deduced from the eLCIDc value by the receiving MAC entity. Specific LCIDc value could be used, in turn, to indicate the availability of eLCIDc:

[0050] Overall, the LCID may be up to 8 bits long in case the reserved “R” fields in the example formats described above are incorporated in the LCID field.

[0051] FIGURE 3 illustrates an example apparatus capable of supporting at least some embodiments of the present invention. Illustrated is device 300, which may comprise, for example, a mobile communication device such as UE 110 of FIGURE 1 or, in applicable parts, a base station or other communication node. Comprised in device 300 is processor 310, which may comprise, for example, a single- or multi-core processor wherein a singlecore processor comprises one processing core and a multi-core processor comprises more than one processing core. Processor 310 may comprise, in general, a control device. Processor 310 may comprise more than one processor. When processor 310 comprises more than one processor, device 300 may be a distributed device wherein processing of tasks takes place in more than one physical unit. Processor 310 may be a control device. A processing core may comprise, for example, a Cortex-A8 processing core manufactured by ARM Holdings or a Zen processing core designed by Advanced Micro Devices Corporation. A processing core or processor may be, or may comprise, at least one qubit. Processor 310 may comprise at least one Qualcomm Snapdragon and / or Intel Atom processor. Processor 310 may comprise at least one application-specific integrated circuit, ASIC. Processor 310 may comprise at least one field-programmable gate array, FPGA. Processor 310, optionally together with memory and computer instructions, may be means for performing methodsteps in device 300, such as compiling, including and / or abstaining. Processor 310 may be configured, at least in part by computer instructions, to perform actions.

[0052] A processor may comprise circuitry, or be constituted as circuitry or circuitries, the circuitry or circuitries being configured to perform phases of methods in accordance with embodiments described herein. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in only analogue and / or digital circuitry, and (b) combinations of hardware circuits and software, such as, as applicable: (i) a combination of analogue and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memoiy(ies) that work together to cause an apparatus, such as a mobile phone or base station, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor s) or a portion of a microprocessor s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0053] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0054] Device 300 may comprise memory 320. Memory 320 may comprise randomaccess memory and / or permanent memory. Memory 320 may comprise at least one RAM chip. Memory 320 may be a computer readable medium. Memory 320 may comprise solid- state, magnetic, optical and / or holographic memory, for example. Memory 320 may be at least in part accessible to processor 310. Memory 320 may be at least in part comprised in processor 310. Memory 320 may be means for storing information. Memory 320 may comprise computer instructions that processor 310 is configured to execute. When computer instructions configured to cause processor 310 to perform certain actions are stored in memory 320, and device 300 overall is configured to run under the direction of processor 310 using computer instructions from memory 320, processor 310 and / or its at least oneprocessing core may be considered to be configured to perform said certain actions. Memory 320 may be at least in part external to device 300 but accessible to device 300. Memory 320 may be transitory or non-transitory. The term “non-transitory”, as used herein, is a limitation of the medium itself (that is, tangible, not a signal) as opposed to a limitation on data storage persistency (for example, RAM vs. ROM).

[0055] Device 300 may comprise a transmitter 330. Device 300 may comprise a receiver 340. Transmitter 330 and receiver 340 may be configured to transmit and receive, respectively, information in accordance with at least one cellular or non-cellular standard. Transmitter 330 may comprise more than one transmitter. Receiver 340 may comprise more than one receiver. Transmitter 330 and / or receiver 340 may be configured to operate in accordance with global system for mobile communication, GSM, wideband code division multiple access, WCDMA, 5G, 6G, long term evolution, LTE, IS-95, wireless local area network, WLAN, Ethernet and / or worldwide interoperability for microwave access, WiMAX, standards, for example.

[0056] Device 300 may comprise a near-field communication, NFC, transceiver 350. NFC transceiver 350 may support at least one NFC technology, such as NFC, Bluetooth, Wibree or similar technologies.

[0057] Device 300 may comprise user interface, UI, 360. UI 360 may comprise at least one of a display, a keyboard, a touchscreen, a vibrator arranged to signal to a user by causing device 300 to vibrate, a speaker or a microphone. A user may be able to operate device 300 via UI 360, for example to accept incoming telephone calls, to originate telephone calls or video calls, to browse the Internet, to manage digital files stored in memory 320 or on a cloud accessible via transmitter 330 and receiver 340, or via NFC transceiver 350, and / or to play games.

[0058] Device 300 may comprise or be arranged to accept a user identity module 370. User identity module 370 may comprise, for example, a subscriber identity module, SIM, card installable in device 300. A user identity module 370 may comprise information identifying a subscription of a user of device 300. A user identity module 370 may comprise cryptographic information usable to verify the identity of a user of device 300 and / or to facilitate encryption of communicated information and billing of the user of device 300 for communication effected via device 300.

[0059] Processor 310 may be furnished with a transmitter arranged to output information from processor 310, via electrical leads internal to device 300, to other devices comprised in device 300. Such a transmitter may comprise a serial bus transmitter arranged to, for example, output information via at least one electrical lead to memory 320 for storage therein. Alternatively to a serial bus, the transmitter may comprise a parallel bus transmitter. Likewise processor 310 may comprise a receiver arranged to receive information in processor 310, via electrical leads internal to device 300, from other devices comprised in device 300. Such a receiver may comprise a serial bus receiver arranged to, for example, receive information via at least one electrical lead from receiver 340 for processing in processor 310. Alternatively to a serial bus, the receiver may comprise a parallel bus receiver.

[0060] Device 300 may comprise further devices not illustrated in FIGURE 3. For example, where device 300 comprises a smartphone, it may comprise at least one digital camera. Some devices 300 may comprise a back-facing camera and a front-facing camera, wherein the back-facing camera may be intended for digital photography and the frontfacing camera for video telephony. Device 300 may comprise a fingerprint sensor arranged to authenticate, at least in part, a user of device 300. In some embodiments, device 300 lacks at least one device described above. For example, some devices 300 may lack a NFC transceiver 350 and / or user identity module 370.

[0061] Processor 310, memory 320, transmitter 330, receiver 340, NFC transceiver 350, UI 360 and / or user identity module 370 may be interconnected by electrical leads internal to device 300 in a multitude of different ways. For example, each of the aforementioned devices may be separately connected to a master bus internal to device 300, to allow for the devices to exchange information. However, as the skilled person will appreciate, this is only one example and depending on the embodiment various ways of interconnecting at least two of the aforementioned devices may be selected without departing from the scope of the present invention.

[0062] FIGURE 4 illustrates signalling in accordance with at least some embodiments of the present invention. On the vertical axes are disposed, on the left, a receiving device RX and on the right, a transmitting device TX. These may correspond to a user equipment, UE, and a base station, BS, respectively, for example. Hardware processing cores Hl and H2 are comprised in receiving device RX. Time advances from the top toward the bottom.

[0063] In phase 410, a MAC PDU is provided from the transmitting device to the receiving device over a communication interface, such as a radio interface or a wire-line interface, for example. In phase 420 receiving device RX opens up the MAC PDU to obtain therefrom the contiguous blocks of the control sub-PDUs and the data sub-PDUs. In the example of FIGURE 4, the data sub-PDUs are of a high bitrate type.

[0064] In phase 430 the contiguous block of data sub-PDUs is provided to first processing core Hl for hardware-optimized low-latency handling, and in phase 440 the contiguous block of control sub-PDUs are provided to second processing core H2 for handling. In some embodiments, second processing core H2 is absent and a main processor of receiver RX handles the contiguous block of control sub-PDUs.

[0065] In phase 450 first processing core Hl processes the data sub-PDUs, including determining the LCIDs, demultiplexing the MAC SDUs, mapping from logical channels to transport channels and performing error control using, for example, hybrid automatic repeat request, HARQ, processes. The processing of phase 450 is accelerated further in embodiments where the data sub-PDU subheaders are of a same size and, optionally, also a same structure. The processed data is forwarded from first processing core Hl onward to e.g. applications of the receiving device RX in phase 460.

[0066] On the control side, the second processing core H2 processes the control sub- PDUs, including determining the LCIDs, demultiplexing the MAC SDUs, mapping from logical channels to transport channels and performing error control using, for example, hybrid automatic repeat request, HARQ, processes. The thus obtained control data is provided, phase 480, to a main processor of receiving device RX, for example to configure, phase 490, aspects of the communication channel used in conveying phase 410.

[0067] FIGURE 5 is a flow graph of a method in accordance with at least some embodiments of the present invention. The phases of the illustrated method may be performed in a transmitting device, such as a base station or a user equipment, for example, or in a control device configured to control the functioning thereof, when installed therein.

[0068] Phase 510 comprises compiling a medium access control, MAC, packet data unit, PDU, the MAC PDU comprising plural sub-packet data units, sub-PDUs, each sub- PDU comprising a subheader which comprises a logical channel identifier. Phase 520 comprises including in the MAC PDU at least one of a contiguous block of data sub-PDUsor a contiguous block of control sub-PDUs. Finally, phase 530 comprises including in the MAC PDU a preconfigured logical channel identifier before a predetermined one of the contiguous blocks to indicate that the predetermined one of the contiguous blocks begins, when the MAC PDU comprises the predetermined one of the contiguous blocks.

[0069] It is to be understood that the embodiments of the invention disclosed are not limited to the particular structures, process steps, or materials disclosed herein, but are extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular embodiments only and is not intended to be limiting.

[0070] Reference throughout this specification to one embodiment or an embodiment means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Where reference is made to a numerical value using a term such as, for example, about or substantially, the exact numerical value is also disclosed.

[0071] As used herein, a plurality of items, structural elements, compositional elements, and / or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present invention may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as de facto equivalents of one another, but are to be considered as separate and autonomous representations of the present invention.

[0072] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the preceding description, numerous specific details are provided, such as examples of lengths, widths, shapes, etc., to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances,well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.

[0073] While the forgoing examples are illustrative of the principles of the present invention in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the invention. Accordingly, it is not intended that the invention be limited, except as by the claims set forth below.

[0074] The verbs “to comprise” and “to include” are used in this document as open limitations that neither exclude nor require the existence of also un-recited features. The features recited in depending claims are mutually freely combinable unless otherwise explicitly stated. Furthermore, it is to be understood that the use of "a" or "an", that is, a singular form, throughout this document does not exclude a plurality.

[0075] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.INDUSTRIAL APPLICABILITY

[0076] At least some embodiments of the present invention find industrial application in data communication over a network.ACRONYMS LIST eLCID extended LCIDLCID logical channel identifierMAC medium access controlMAC CE MAC control elementMAC SDU MAC service data unitPDU protocol data unitREFERENCE SIGNS LIST

Claims

CLAIMS:

1. An apparatus comprising at least one processing core and at least one memory storing instructions that, when executed by the at least one processing core, cause the apparatus at least to:- compile a medium access control, MAC, packet data unit, PDU, the MAC PDU comprising plural sub-packet data units, sub-PDUs, each sub-PDU comprising a subheader which comprises a logical channel identifier, the apparatus being configured to process data sub-PDUs and control sub-PDUs;- include in the MAC PDU at least one of a contiguous block of data sub-PDUs or a contiguous block of control sub-PDUs, and- include in the MAC PDU a preconfigured logical channel identifier before a predetermined one of the contiguous blocks to indicate that the predetermined one of the contiguous blocks begins, when the MAC PDU comprises the predetermined one of the contiguous blocks.

2. The apparatus according to claim 1, configured to include in the MAC PDU the two contiguous blocks such that the contiguous block of data sub-PDUs is before the contiguous block of control sub-PDUs, and the contiguous block of control sub-PDUs is the predetermined contiguous block.

3. The apparatus according to claim 1, configured to include in the MAC PDU the two contiguous blocks such that the contiguous block of control sub-PDUs is before the contiguous block of data sub-PDUs, and the contiguous block of data sub-PDUs is the predetermined contiguous block.

4. The apparatus according to claim 1, configured to abstain from including the preconfigured logical channel identifier in the MAC PDU when the MAC PDU does not comprise the predetermined one of these contiguous blocks.

5. The apparatus according to any of claims 1 - 4, wherein all subheaders of the data sub- PDUs are of a same size.

6. The apparatus according to claim 5, wherein the subheaders of the data sub-PDUs all share a same field structure.

7. The apparatus according to any of claims 1 - 6, further configured to select an arrangement for the MAC PDU based on a type of resource grant used to communicate the MAC PDU.

8. The apparatus according to claim 7, wherein when the resource grant is from a random access process, the apparatus is configured to place any control sub-PDUs before any data sub-PDUs and / or when the grant is an uplink grant for a shared uplink channel, the apparatus is configured to place any control sub-PDUs before any data sub-PDUs.

9. The apparatus according to any of claims 1 - 8, further configured to encapsulate at least a part of payload of the control sub-PDUs into a data sub-PDU, and / or configured to encapsulate payload of at least a part of low data rate data sub-PDUs into a high data rate data sub-PDU.

10. The apparatus according to claim 9, configured to select for a subheader of the data sub- PDU into which the encapsulating is performed a logical channel identifier which indicates that this data sub-PDU comprises the control sub-PDU payload and / or the at least the part of the low data rate sub-PDU.

11. The apparatus according to any of claims 1 - 10, further configured to select for data sub-PDU subheaders and control sub-PDU subheaders logical channel identifiers from separate identifier spaces.

12. The apparatus according to any of claims 1 - 10, further configured to select for data sub-PDU subheaders and control sub-PDU subheaders logical channel identifiers from a same identifier space.

13. The apparatus according to any of claims 1 - 12, configured to include in subheaders of control sub-PDUs a length field indicating a length of the respective control sub-PDU, unless the respective control sub-PDU is of a type which has fixed length.

14. The apparatus according to any of claims 1 - 13, further configured to transmit the compiled MAC PDU to a node15. A method comprising:- compiling a medium access control, MAC, packet data unit, PDU, the MAC PDU comprising plural sub-packet data units, sub-PDUs, each sub-PDU comprising a subheader which comprises a logical channel identifier;- including in the MAC PDU at least one of a contiguous block of data sub-PDUs or a contiguous block of control sub-PDUs, and- including in the MAC PDU a preconfigured logical channel identifier before a predetermined one of the contiguous blocks to indicate that the predetermined one of the contiguous blocks begins, when the MAC PDU comprises the predetermined one of the contiguous blocks.

16. The method according to claim 15, comprising including in the MAC PDU the two contiguous blocks such that the contiguous block of data sub-PDUs is before the contiguous block of control sub-PDUs, and the contiguous block of control sub-PDUs is the predetermined contiguous block.

17. The method according to claim 15, comprising including in the MAC PDU the two contiguous blocks such that the contiguous block of control sub-PDUs is before the contiguous block of data sub-PDUs, and the contiguous block of data sub-PDUs is the predetermined contiguous block.

18. The method according to claim 15, comprising abstaining from including the preconfigured logical channel identifier in the MAC PDU when the MAC PDU does not comprise the predetermined one of these contiguous blocks.

19. The method according to any of claims 15 - 18, wherein all subheaders of the data sub- PDUs are of a same size.

20. The method according to claim 19, wherein the subheaders of the data sub-PDUs all share a same field structure.

21. The method according to any of claims 15 - 20, further comprising selecting an arrangement for the MAC PDU based on a type of resource grant used to communicate the MAC PDU.

22. The method according to claim 21, wherein when the resource grant is from a random access process, the method comprising placing any control sub-PDUs before any data sub- PDUs and / or when the grant is an uplink grant for a shared uplink channel, the method comprising placing any control sub-PDUs before any data sub-PDUs.

23. The method according to any of claims 15 - 22, further configured to encapsulate at least a part of payload of the control sub-PDUs into a data sub-PDU, and / or configured to encapsulate payload of at least a part of low data rate data sub-PDUs into a high data rate data sub-PDU.

24. The method according to claim 23, configured to select for a subheader of the data sub- PDU into which the encapsulating is performed a logical channel identifier which indicates that this data sub-PDU comprises the control sub-PDU payload and / or the at least the part of the low data rate sub-PDU.

25. The method according to any of claims 15 - 24, further configured to select for data sub- PDU subheaders and control sub-PDU subheaders logical channel identifiers from separate identifier spaces.

26. The method according to any of claims 15 - 24, further configured to select for data sub- PDU subheaders and control sub-PDU subheaders logical channel identifiers from a same identifier space.

27. The method according to any of claims 15 - 26, configured to include in subheaders of control sub-PDUs a length field indicating a length of the respective control sub-PDU, unless the respective control sub-PDU is of a type which has fixed length.

28. The method according to any of claims 15 - 26, further configured to transmit the compiled MAC PDU to a node.

29. A non-transitory computer readable medium having stored thereon a set of computer readable instructions that, when executed by at least one processor, cause an apparatus to at least:- compile a medium access control, MAC, packet data unit, PDU, the MAC PDU comprising plural sub-packet data units, sub-PDUs, each sub-PDU comprising a subheader which comprises a logical channel identifier, the set of computer readable instructions being configured to process data sub-PDUs and control sub-PDUs;- include in the MAC PDU at least one of a contiguous block of data sub-PDUs or a contiguous block of control sub-PDUs, and- include in the MAC PDU a preconfigured logical channel identifier before a predetermined one of the contiguous blocks to indicate that the predetermined one of the contiguous blocks begins, when the MAC PDU comprises the predetermined one of the contiguous blocks.

30. An apparatus comprising at least one processing core and at least one memory storing instructions that, when executed by the at least one processing core, cause the apparatus at least to:- receive a medium access control, MAC, packet data unit, PDU, the MAC PDU comprising plural sub-packet data units, sub-PDUs, each sub-PDU comprising a subheader which comprises a logical channel identifier;- the MAC PDU comprising at least one of a contiguous block of data sub-PDUs or a contiguous block of control sub-PDUs, and- determine based on a preconfigured logical channel identifier in the MAC PDU that a predetermined one of the contiguous blocks begins after the preconfigured logical channel identifier, the MAC PDU comprising the predetermined one of the contiguous blocks.

Images