Control elements for medium access control configured in association with logical channel identifier in wireless communications systems

Abstract

A network node of a telecommunications system comprises processor circuitry and an interface. The processor circuitry is configured to establish an association between a configuration parameter and a format type for a control element (MAC CE) of a medium access control (MAC) protocol. The configuration parameter is configured to indicate one of plural control element format types. The interface is configured to transmit a signal which includes the configuration parameter to a wireless terminal.

Description

CONTROL ELEMENTS FOR MEDIUM ACCESS CONTROL CONFIGURED IN ASSOCIATION WITH LOGICAL CHANNEL IDENTIFIER IN WIRELESS COMMUNICATIONS SYSTEMS

[0001] The technology relates to wireless communications, and particularly to resource utilization in sliced networks.

[0002] A radio access network typically resides between wireless devices, such as user equipment (UEs), mobile phones, mobile stations, or any other device having wireless termination, and a core network. Example of radio access network types includes the GRAN, GSM radio access network; the GERAN, which includes EDGE packet radio services; UTRAN, the UMTS radio access network; E-UTRAN, which includes Long-Term Evolution; and NG-UTRAN, the New Radio (NR).

[0003] A radio access network may comprise one or more access nodes, such as base station nodes, which facilitate wireless communication or otherwise provides an interface between a wireless terminal and a telecommunications system. A non-limiting example of a base station can include, depending on radio access technology type, a Node B (“NB”), an enhanced Node B (“eNB”), a home eNB (“HeNB”), a gNB (for a New Radio [“NR”] technology system), or some other similar terminology.

[0004] The 3rd Generation Partnership Project (“3GPP”) is a group that, e.g., develops collaboration agreements such as 3GPP standards that aim to define globally applicable technical specifications and technical reports for wireless communication systems. Various 3GPP documents may describe certain aspects of radio access networks. Overall architecture for a fifth-generation system, e.g., the 5G System, also called “NR” or “New Radio”, as well as “NG” or “Next Generation”, is shown in Fig. 1, and is also described in 3GPP TS 38.300. The 5G NR network is comprised of NG RAN (Next Generation Radio Access Network) and 5GC (5G Core Network). As shown, NGRAN is comprised of gNBs (e.g., 5G Base stations) and ng-eNBs (i.e. LTE base stations). An Xn interface exists between gNB-gNB, between (gNB)-(ng-eNB) and between (ng-eNB)-(ng-eNB). The Xn is the network interface between NG-RAN nodes. Xn-U stands for Xn User Plane interface and Xn-C stands for Xn Control Plane interface. A NG interface exists between 5GC and the base stations (i.e. gNB & ng-eNB). A gNB node provides NR user plane and control plane protocol terminations towards the UE and is connected via the NG interface to the 5GC. The 5G NR (New Radio) gNB is connected to AMF (Access and Mobility Management Function) and UPF (User Plane Function) in 5GC (5G Core Network).

[0005] In 3GPP wireless communication systems, a Medium Access Control, MAC, control element, CE, herein referred to as “MAC CE” is a way of control signaling at the MAC sublayer. MAC CEs are multiplexed in a MAC protocol data unit, e.g., MAC PDU, together with user data, e.g., in a MAC service data unit, SDU. A MAC CE requires that its MAC subheader indicate the relevant information of the MAC CE. For example, a Logical Channel Identity, LCID, in the subheader indicates the type of the MAC CE. For the variable-sized MAC CE, a length field, L, in the subheader indicates the total size of the MAC CE. Based on the header information, the sender and receiver are able to exchange the MAC CE successfully. in addition to the L and LCID fields, the MAC subheader also includes a format field, F, and a reserved field, R. Fig. 2 depicts an example of an uplink (UL) MAC PDU including MAC CEs. Fig. 3 depicts an example of a downlink (DL) MAC PDU including MAC CEs.

[0006] As wireless communications systems have been evolving, many MAC CEs have been introduced to support various functions. But the use of MAC CEs entails various problems or complications, some of which are described briefly below in terms of, e.g., security risks, overhead, and extendability.

[0007] As the first example problem, currently MAC CE is not security protected, e.g., MAC CE is neither ciphered nor integrity protected. The plaintext of the MAC CE is transmitted over the air, so all the contents are exposed or could be leaked to attackers or unauthorized users. It is possible that the attacker may send any MAC CE with fake contents or use this information for other types of security attacks. Currently, a Radio Network Temporary Identifier, RNTI, is used to scramble downlink control information, DCI. This RNTI scrambling provides a certain level of security. However, if the RNTI information is leaked, the MAC CE cannot be security protected. Moreover, for each MAC CE, the LCID value to use is deterministic. This means that all the user equipments, UEs, in the wireless communications network always use the same LCID value. Thus, the contents of the MAC CE are exposed easily from the security perspective.

[0008] Secondly, there may be problems concerning the MAC CE header overhead due to the limited number of LCID space, e.g., the limited number of bits in the LCID field, or the limited number of available LCIDs (likely in view of the limited number of bits, and the introduction of an enhanced LCID field, eLCID. In NR, 6-bit LCID field, which supports up to 64 LCID values, was introduced as shown in Fig. 4. Among the 64 values, only 30 values are allowed for MAC CEs. The other values are dedicated to logical channel data, padding, and a Common Control Channel, CCCH, message. Thus, in some situations there may currently be a shortage of LCID. In Rel-18 NR, 55 downlink, DL, MAC CEs and 56 uplink, UL, MAC CEs are defined. To resolve the shortage of LCIDs, the eLCID field was introduced as an extension of the LCID field as shown in Fig. 5. If the LCID field is set to 34, an eLCID field with one octet sized. For example, as shown in Fig. 5, if an LCID value 34 is set, an eLCID field of 1 byte (1 octet) is present, as shown in Fig. 5. It increases the header overhead by one byte. But while providing the advantage of more LCIDs, the reality is that only a few MAC CEs are used by a UE.

[0009] A third problem relates to limited extendibility. The MAC subheader format is deterministic. For instance, the size of LCID field is always 6-bit long which supports up to 64 values. The limited length of the LCID field decreases the flexibility of the extension, especially when more than LCID values are required for the UE at a given time. On the other hand, only a few LCID values may be needed. In this case, 6-bit of size is unnecessary.

[0010] What is needed are methods, apparatus, and / or techniques to address one or more problems or issues involved with the use of MAC CEs.

[0011] In one of its example aspects the technology disclosed herein concerns a network node of a telecommunications system. In an example embodiment and mode network node comprises processor circuitry and an interface. The processor circuitry is configured to establish an association between a configuration parameter and a format type for a control element (MAC CE) of a medium access control (MAC) protocol. The configuration parameter is configured to indicate one of plural control element format types. The interface is configured to transmit a signal which includes the configuration parameter to a wireless terminal. Methods of operating such network nodes are also disclosed.

[0012] In another of its example aspects the technology disclosed herein concerns a wireless terminal which communicates with a network node through a radio access network. In an example embodiment and mode the wireless terminal comprises receiver circuitry and processor circuitry. The receiver circuitry is configured to obtain a configuration parameter from a signal received from the network node over the radio access network and to receive a MAC protocol data unit (MAC PDU) from the radio access network. The processor circuitry is configured to determine from the configuration parameter which one of plural MAC CE format types the wireless terminal should use to interpret a control element (MAC CE) of a medium access control (MAC) protocol data unit (MAC PDU) received by the wireless terminal over the radio access network. Methods of operating such wireless terminals are also disclosed.

[0013] In yet another of its example aspects the technology disclosed herein concerns a network node of a telecommunications system. In an example embodiment and mode the network node comprises processor circuitry and an interface. The processor circuitry is configured to configure a format configuration of a medium access control (MAC) control element (MAC CE) and to include in a signal an indication of the format configuration. The interface is configured to transmit the signal to a wireless terminal. Methods of operating such network nodes are also disclosed.

[0014] In another of its example aspects the technology disclosed herein concerns a wireless terminal which communicates with a network node through a radio access network. In an example embodiment and mode the wireless terminal comprises receiver circuitry and processor circuitry. The receiver circuitry is configured to receive a signal from a network node. The processor circuitry configured to determine from the signal an indication of a format configuration of a medium access control (MAC) control element (MAC CE). Methods of operating such wireless terminals are also disclosed.

[0015] In yet another of its example aspects the technology disclosed herein concerns a network node of a telecommunications system. In an example embodiment and mode the network node comprises processor circuitry and an interface. The processor circuitry is configured to configure a format configuration of a medium access control (MAC) subheader and to include in a signal an indication of the format configuration. The interface is configured to transmit the signal to a wireless terminal. Methods of operating such network nodes are also disclosed.

[0016] In another of its example aspects the technology disclosed herein concerns a wireless terminal which communicates with a network node through a radio access network. In an example embodiment and mode the wireless terminal comprises receiver circuitry and processor circuitry. The receiver circuitry is configured to receive a signal from a network node. The processor circuitry is configured to determine from the signal an indication of a format configuration of a medium access control (MAC) subheader. Methods of operating such wireless terminals are also provided.

[0017] The foregoing and other objects, features, and advantages of the technology disclosed herein will be apparent from the following more particular description of preferred embodiments as illustrated in the accompanying drawings in which reference characters refer to the same parts throughout the various views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the technology disclosed herein.Fig. 1 is a diagrammatic view of overall architecture for a 5G New Radio system.Fig. 2 is a diagrammatic view depicting an example uplink (UL) MAC PDU including MAC CEs.Fig. 3 is a diagrammatic view depicting an example of a downlink (DL) MAC PDU including MAC CEs.Fig. 4 is a diagrammatic view depicting an example MAC subheader format with R / F / LCID and L field.Fig. 5 is a diagrammatic view depicting an example MAC subheader format with R / F / LCID, eLCID, and L field.Fig. 6 is a diagrammatic view of a communications system comprising a network node and a wireless terminal and which may operate with established associations between a configuration parameter and a format type for a control element (MAC CE) of a medium access control (MAC) protocol.Fig. 7 is a diagrammatic view showing an example scenario of plural sets of associations between a configuration parameter and a format type for a control element (MAC CE) of a medium access control (MAC) protocol.Fig. 8A is a schematic view which shows in more detail example structures and functionalities that may, in a first example embodiment and mode, comprise or be included in the communications network of Fig. 6.Fig. 8B is a schematic view which shows in more detail example structures and functionalities that may, in a second example embodiment and mode, comprise or be included in the communications network of Fig. 6.Fig. 9 is a diagrammatic view of a communications system comprising a network node and a wireless terminal and which includes control elements with configurable format for medium access control (MAC).Fig. 10 is a diagrammatic view depicting a Single-entry Power Headroom Report (PHR) MAC CE format of 3GPR NR MAC specification.Fig. 11 is a diagrammatic view depicting a first example Single-entry Power Headroom Report (PHR) MAC CE format according to a first example for the embodiment and mode of Fig. 9.Fig. 12 is a diagrammatic view depicting a second example Single-entry Power Headroom Report (PHR) MAC CE format according to a second example for the embodiment and mode of Fig. 9.Fig. 13 is a flowchart depicting an exemplary signaling flow of MAC CE configuration.Fig. 14A is a schematic view which shows in more detail example structures and functionalities that may, in first example embodiment and mode, comprise or be included in the communication network of Fig. 9.Fig. 14 B is a schematic view which shows in more detail example structures and functionalities that may, in a second example embodiment and mode, comprise or be included in the communication network of Fig. 9.Fig. 15 is a diagrammatic view of a communications system comprising a network node and a wireless terminal and which includes subheaders with configurable format for medium access control (MAC).Fig. 16A is a schematic view which shows in more detail example structures and functionalities that may, in a first example embodiment and mode, comprise or be included in the communications network of Fig. 15.Fig. 16B is a schematic view which shows in more detail example structures and functionalities that may, in a second example embodiment and mode, comprise or be included in the communications network of Fig. 15.Fig. 17 is a diagrammatic view depicting a default MAC subheader format.Fig. 18 is a diagrammatic view depicting an example configured MAC subheader format.Fig. 19 is a diagrammatic view depicting an example configured MAC subheader format.Fig. 20 is a diagrammatic view showing example elements comprising electronic machinery which may comprise a wireless terminal, a radio access node, and a core network node according to an example embodiment and mode.

[0018] In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the technology disclosed herein. However, it will be apparent to those skilled in the art that the technology disclosed herein may be practiced in other embodiments that depart from these specific details. That is, those skilled in the art will be able to devise various arrangements which, although not explicitly described or shown herein, embody the principles of the technology disclosed herein and are included within its spirit and scope. In some instances, detailed descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the technology disclosed herein with unnecessary detail. All statements herein reciting principles, aspects, and embodiments of the technology disclosed herein, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure.

[0019] Thus, for example, it will be appreciated by those skilled in the art that block diagrams herein can represent conceptual views of illustrative circuitry or other functional units embodying the principles of the technology. Similarly, it will be appreciated that any flow charts, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

[0020] As used herein, the term “telecommunication system” or “communications system” can refer to any network of devices used to transmit information. A non-limiting example of a telecommunication system is a cellular network or other wireless communication system. As used herein, the term “cellular network” or “cellular radio access network” can refer to a network distributed over cells, each cell served by at least one fixed-location transceiver, such as a base station. A “cell” may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (“IMTAdvanced”); IMT-2020, e.g., 5G; IMT-2030, e.g., 6G, etc. All or a subset of the cell may be adopted by 3GPP as licensed bands (e.g., frequency band) to be used for communication between a base station, such as a Node B, and a UE terminal. A cellular network using licensed frequency bands can include configured cells. Configured cells can include cells of which a UE terminal is aware and in which it is allowed by a base station to transmit or receive information. Examples of cellular radio access networks include E-UTRAN, and any successors thereof (e.g., NUTRAN).

[0021] A core network (CN) may comprise numerous servers, routers, and other equipment. As used herein, the term “core network” can refer to a device, group of devices, or sub-system in a telecommunication network that provides services to users of the telecommunications network. Examples of services provided by a core network include aggregation, authentication, call switching, service invocation, gateways to other networks, etc. A core network may communicate over a RAN-CN interface (e.g., N2 interface) with one or more radio access networks (RAN).

[0022] A radio access network (RAN) may communicate with one or more core networks. A radio access network (RAN) typically comprises plural access nodes. As used herein, the term “access node”, “node”, or “base station” can refer to any device or group of devices that facilitates wireless communication or otherwise provides an interface between a wireless terminal and a telecommunications system. A non-limiting example of a base station can include, in the 3GPP specification, a Node B (“NB”), an enhanced Node B (“eNB”), a home eNB (“HeNB”), a gNB (for a New Radio [“NR”] technology system), or some other similar terminology.

[0023] A radio access network (RAN) 22 serves wireless terminals, which also form part of the radio access network (RAN). As used herein, the term “wireless terminal” can refer to any electronic device used to communicate voice and / or data via a telecommunications system, such as (but not limited to) a cellular network. Other terminology used to refer to wireless terminals and non-limiting examples of such devices can include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, cellular phones, smart phones, personal digital assistants (“PDAs”), laptop computers, tablets, netbooks, e-readers, wireless modems, etc.

[0024] A wireless terminal communicates with its serving radio access network (RAN) over a radio or air interface. Communication between radio access network (RAN) and wireless terminal over the radio interface occurs by utilization of “resources”. Any reference to a “resource” herein means “radio resource” unless otherwise clear from the context that another meaning is intended. In general, as used herein a radio resource (“resource”) is a time-frequency unit that can carry information across a radio interface, e.g., either signal information or data information.

[0025] Communication between radio access network (RAN) 24 and wireless terminal over the radio interface 32 may occur on various layers. Layer 1 includes radio layer 1 or the physical layer. Higher layers, e.g., layers higher than Layer 1 may include radio layer 2 and radio resource control layer 3. The layer 1 communication may occur by utilization of “resources”. Reference to a “resource” herein means “radio resource” unless otherwise clear from the context that another meaning is intended. In general, as used herein a radio resource (“resource”) is a time-frequency unit that can carry information across a radio interface, e.g., either signal information or data information.

[0026] An example of a radio resource occurs in the context of a “frame” of information that is typically formatted and prepared, e.g., by a node. In Long Term Evolution (LTE) a frame, which may have both downlink portion(s) and uplink portion(s), is communicated between the base station and the wireless terminal. Each LTE frame may comprise plural subframes. For example, in the time domain, a 10 ms frame consists of ten one millisecond subframes. An LTE subframe is divided into two slots (so that there are thus 20 slots in a frame). The transmitted signal in each slot is described by a resource grid comprised of resource elements (RE). Each column of the two-dimensional grid represents a symbol (e.g., an OFDM symbol on downlink (DL) from node to wireless terminal; an SC-FDMA symbol in an uplink (UL) frame from wireless terminal to node). Each row of the grid represents a subcarrier. A resource element (RE) is the smallest time-frequency unit for downlink transmission in the subframe. That is, one symbol on one sub-carrier in the sub-frame comprises a resource element (RE) which is uniquely defined by an index pair (k,l) in a slot (where k and l are the indices in the frequency and time domain, respectively). In other words, one symbol on one sub-carrier is a resource element (RE). Each symbol comprises a number of sub-carriers in the frequency domain, depending on the channel bandwidth and configuration. The smallest time-frequency resource supported by the standard today is a set of plural subcarriers and plural symbols (e.g., plural resource elements (RE)) and is called a resource block (RB). A resource block may comprise, for example, 84 resource elements, i.e., 12 subcarriers and 7 symbols, in case of normal cyclic prefix In 5G New Radio (“NR”), a frame consists of 10 ms duration. A frame consists of 10 subframes with each having 1ms duration similar to LTE. Each subframe consists of 2μ slots. Each slot can have either 14 (normal CP) or 12 (extended CP) OFDM symbols. A Slot is a typical unit for transmission used by scheduling mechanism. NR allows transmission to start at any OFDM symbol and to last only as many symbols as required for communication. This is known as "mini-slot" transmission. This facilitates very low latency for critical data communication as well as minimizes interference to other RF links. Mini-slots help to achieve lower latency in 5G NR architecture. Unlike slots, mini-slots are not tied to the frame structure. It helps in puncturing the existing frame without waiting to be scheduled. See, for example, https: / / www.rfwireless-world.com / 5G / 5G-NR-Mini-Slot.html, which is incorporated herein by reference.

[0027] In general, communication protocols between the wireless terminal and the telecommunication system may be categorized into Access Stratum (AS) and Non-Access Stratum (NAS). AS protocols, such as Radio Resource Control (RRC) and Medium Access Control (MAC), may be used for the wireless terminal to communicate with access nodes of a RAN, whereas NAS protocol(s), such as the NAS protocol specified in 3GPP TS 24.501, may be used for the wireless terminal to communicate with entities (e.g., AMF) of a CN(s), via access nodes of a RAN. Consequently, the wireless terminal may comprise a function to manage the AS protocols, and a separate function to manage the NAS protocol(s). Herein, terminology “NAS” may be used in some context to refer to the function built into the wireless terminal to manage the NAS protocol(s). Similarly, “RRC” may be used in some context to refer to the function built into the wireless terminal to manage the RRC protocol.

[0028] ASSOCIATION OF MAC CE AND MAC CE IDENTIFY Fig. 6 shows a communications system which comprises a network node NN and a wireless terminal UE. The communications system of Fig. 6 may operate with established associations between a configuration parameter and a format type for a control element (MAC CE) of a medium access control (MAC) protocol, as herein described. The network node NN may be either a core network node or a node of a radio access network, such as a RAN access node, e.g., a base station node, for example. The wireless terminal UE may be any electronic device used to communicate voice and / or data via a telecommunications system, such as (but not limited to) a cellular network. Other terminology used to refer to wireless terminals and non-limiting examples of such devices can include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, cellular phones, smart phones, personal digital assistants (“PDAs”), laptop computers, tablets, netbooks, e-readers, wireless modems, etc.be any Fig. 6 depicts certain basic, example, representative acts or steps performed in the communications system, e.g., by network node NN and wireless terminal UE. Such basic acts are now briefly described with reference to acts 6-1 through and including 6-5 and are understood more fully in the context of the ensuing description.

[0029] Act 6-1 comprises the network node NN establishing an association between a control element (MAC CE) of a medium access control (MAC) protocol and a MAC CE identity. For example, act 6-1 includes the network node NN establishing an association between a format type for a control element (MAC CE) of a medium access control (MAC) protocol and a configuration parameter. The configuration parameter is configured to indicate one of plural control element format types. In an example non-limiting implementation, the configuration parameter comprises a Logical Channel Identity, LCID, e.g., a LCID value. In other words, in such non-limiting implementation LCID is used as an identity of each MAC CE. However, for other implementations it is possible to define and use a different identity of the MAC CE, in which case such other or different identity of MAC CE may replace the LCID of the example implementation.

[0030] Act 6-2 comprises the network node NN transmitting a signal, shown in Fig. 6 as signal S, which includes the configuration parameter to a wireless terminal. In the case of the network node NN being a core network node, the signal S may be transmitted to a radio access network and then from the radio access network over a radio interface to the wireless terminal UE. In the case of the network node NN being a radio access network node, the signal S is transmitted from the radio access network over a radio interface to the wireless terminal UE. As shown in Fig. 6, the signal S includes the configuration parameter intended for transmission to the wireless terminal UE. The configuration parameter may be included in an information parameter of the signal S. The signal S may be a radio resource control (RRC) signal, for example.

[0031] Act 6-3 comprises the wireless terminal UE receiving and obtaining the configuration parameter from the signal S. The signal is received from the network node over the radio interface from the radio access network, whether the signal S was prepared at a core network node NN or a radio access network node.

[0032] Act 6-4 comprises the wireless terminal UE subsequently receiving a MAC protocol data unit (MAC PDU) from the radio access network. The MAC PDU may be received over the radio interface from the radio access network.

[0033] Act 6-5 comprises the wireless terminal UE determining, from the configuration parameter, which one of plural MAC CE format types the wireless terminal should use to interpret a control element (MAC CE) of the medium access control (MAC) protocol data unit (MAC PDU) which is received by the wireless terminal over the radio access network.

[0034] The foregoing overview of simplified acts or steps of Fig. 6 is explained further below. In the ensuing discussion, it should be understood that “network” may be used interchangeably with “network node”, except where otherwise clear from the context.

[0035] In the example embodiment and mode basically represented in Fig. 6, the network (e.g., gNB in 5G wireless communications systems) configures one or more MAC CE formats, e.g., format types, that the UE should recognize. The network also configures an LCID value for each MAC CE format. The UE identifies which MAC CE format should be used to interpret a MAC CE in a MAC PDU using an association between the MAC CE format and the LCID value. The association is known, e.g., stored in memory or a processor circuitry, of both the network node NN and the wireless terminal UE. A MAC CE configuration can be associated with a MAC CE format and a LCID value. Based on the association, the UE interprets MAC CE using a MAC CE format whose LCID value matches to the value of the LCID field.

[0036] For example, in a case that a value indicated by a LCID field in an MAC subheader associated with the MAC CE is a first LCID, the UE uses a MAC CE format associated with the first LCID. In a case that a value of a LCID field in a MAC subheader associated with the MAC CE is a second LCID, the UE uses a MAC CE format associated with the second LCID.

[0037] The configuration may be based on an RRC signaling from a gNB or other network entity to the UE.

[0038] Fig. 7 depicts an example of LCID value allocation for some MAC CEs. It shows the MAC CE configurations of two UEs, namely, UE 1 and UE 2. Each UE is configured with four MAC CEs. The MAC CE configuration can be an information element of RRC signaling. For UE 1, LCID value 5 is allocated to Long Buffer Status Report (BSR) MAC CE which is an uplink MAC CE transmitted by UE to the network, LCID value 6 I s allocated to Short BSR MAC CE which is an uplink MAC CE transmitted by UE to the network, LCID value 3 is allocated to Long DRX Command MAC CE which is a downlink MAC CE transmitted by the network to the UE, and LCID value 9 is allocated to DRX Command MAC CE which is a downlink MAC CE transmitted by the network to the UE. For UE 2, LCID value 6 is allocated to Long Buffer Status Report (BSR) MAC CE which is an uplink MAC CE transmitted by UE to the network, LCID value 10 is allocated to Short BSR MAC CE which is an uplink MAC CE transmitted by UE to the network, LCID value 7 is allocated to Long DRX Command MAC CE which is a downlink MAC CE transmitted by the network to the UE, and LCID value 14 is allocated to DRX Command MAC CE which is a downlink MAC CE transmitted by the network to the UE. Based on the configuration including the LCID value allocation, the UE and network can exchange the MAC CE successfully.

[0039] Thus, Fig. 7 shows that the network node NN may establish a plurality of associations, and even plural sets of associations. A first set of associations is shown as “set 1” at the left of Fig. 7; a second set of associations is shown as “set 2” at the right of Fig. 7. The network node NN thus may establish plural sets of associations, each set of associations comprising associations of plural potential configuration parameters and plural potential corresponding MAC CE format types for a set of one or more wireless terminals.

[0040] Each association is an association of one of a set of potential configuration parameters and one of a set of potential corresponding MAC CE format types. Accordingly, the network node NN selects a selected one of the set of potential configuration parameters for inclusion as the configuration parameter to be transmitted to the wireless terminal. The selection and transmission enable the wireless terminal to determine from the selected one of the set of potential configuration parameters which one of the plural MAC CE format types the wireless terminal should use to interpret a MAC CE in a MAC protocol data unit (MAC PDU) to be received by the wireless terminal, as depicted also in act 6-5.

[0041] Thus, as understood, e.g., from Fig. 7, on an example embodiment and mode, it is possible that different UEs may use different LCID values for the same MAC CE.

[0042] In some scenarios or circumstances it may not be possible that all MAC CE’s LCID values are separately configured by an RRC signaling. Such separate configuring may increase the signaling overhead. Instead, as an example feature for the example embodiment and mode of Fig. 6, a default LCID value may be pre-configured. The default LCID value is used when the LCID value of the MAC CE is not configured. In an exemplary embodiment, if a MAC CE has its default LCID value and its LCID value is not configured by an RRC signaling, the UE uses the default value for the MAC CE. If a MAC CE does not have its default LCID value and its LCID value is not configured by an RRC signaling, the UE assumes or expects that the MAC CE is not configured to use. The default LCID value can be pre-defined by the specification, or pre-defined by the network and UE.

[0043] In some example embodiments and modes, only a subset of total MAC CEs may have a configurable LCID value by the RRC signaling. Some essential MAC CE may have a dedicated LCID value. For those MAC CEs, their LCID values are deterministic. In an exemplary embodiment, the essential MAC CEs can include at least one of CCCH, padding, Timing Advance Command, SCell Activation. The characteristic of this embodiment is that MAC CEs are categorized into two groups: 1) MAC CE whose LCID value is fixed, 2) MAC CE whose LCID value is not fixed but configured by an RRC message.

[0044] In some exemplary embodiments, the default LCID value may be used before a specified time point. The time point could be either the entry of RRC connected state, upon reception of an RRCSetup, upon transmission of RRCSetupComplete, upon reception of RRCReconfiguration, upon transmission of RRCReconfigurationComplete, upon reception of RRCResume, upon transmission of RRCResumeComplete, or other specified time point.

[0045] In an exemplary embodiment, the default LCID value can be used only before a specified time point. The default LCID value is not used after the specified time point. In other words, the MAC CE whose LCID value is not configured by an RRC message is considered as not configured to use, irrespective of the default LCID value. The time point could be either the entry of RRC connected state, upon reception of an RRCSetup, upon transmission of RRCSetupComplete, upon reception of RRCReconfiguration, upon transmission of RRCReconfigurationComplete, upon reception of RRCResume, upon transmission of RRCResumeComplete, or other specified time point.

[0046] Fig. 8A and Fig. 8B show in more detail example structures and functionalities that may, in respective first and second example embodiments and modes, comprise or be included in the communications network of Fig. 6. In the communications system of Fig. 8A, the network node NN comprises a core network node. By contrast, in the communications system of Fig. 8B, the network node NN comprises a radio access network.

[0047] Fig. 8A and Fig. 8B both show that the example communications networks, which may be 5G networks, for example, comprise core network 20. The core network 20 may comprise one or more core network nodes, such as core network node 21. The core network node 21 may comprise or be realized by any suitable type of core network node, such as a core network management entity, e.g., an Access and Mobility Management Function (AMF). One or more of the core network nodes 21 may comprise core node processor circuitry, such as core node processor(s) 22. The core network 20 and one or more of its constituent core network nodes 21 is connected to at least one radio access network 24 through a core-RAN interface circuit 23. The core-RAN interface circuit 23 may be connected to wireline(s) 28.

[0048] The radio access network 24 in turn comprises one or more radio access network (RAN) nodes, such as example base station node 26. The base station node 26 serves at least one cell. The radio access network, RAN, 24 typically comprises plural access nodes, one example access node 26 being illustrated as a base station node in Fig. 8A and Fig. 8B.

[0049] Fig. 8A and Fig. 8B both show the radio access network 24, and base station node 26 through its cell in particular communicating with wireless terminal 30 across a radio or air interface 32. The base station node 26 may, and usually does, communicate with plural wireless terminals across the air interface 32. Only one wireless terminal 30 is shown for sake of simplicity, it being understood that other wireless terminals may be provided and may operate in similar manner as the wireless terminal 30 herein illustrated.

[0050] Fig. 8A and Fig. 8B show base station node 26 as comprising base station processor circuitry which may comprise one or more base station processors 34, as well as base station transceiver circuitry 36. As illustrated in Fig. 5A, the base station transceiver circuitry 36 may be a transmission and reception point (TRP). The transmission and reception point (TRP) 36 may further comprise transmitter circuitry and receiver circuitry. The base station processors 34 may comprise frame / message handler / generator 40 which prepares and generates information including user data and messages, e.g., signaling, for transmission over the radio interface 32, as which also processes information received over the radio interface 32.

[0051] The base station node 26 may be structured essentially as shown in Fig. 8A and Fig. 8B or may be a node having architecture such as split architecture comprising a central unit and one or more distributed units that comprise mobile termination (MT). The base station processor(s) may include one or more TRPs.

[0052] Fig. 8A and Fig. 8B also show various example constituent components and functionalities of wireless terminal 30. For example, Fig. 8A and Fig. 8B show wireless terminal 30 as comprising terminal transceiver circuitry 50. The transceiver circuitry 50 in turn may comprise terminal transmitter circuitry 52 and terminal receiver circuitry 54. The terminal transceiver circuitry 50 may include antenna(e) for the wireless transmission. Terminal transmitter circuitry 52 may include, e.g., amplifier(s), modulation circuitry and other conventional transmission equipment. Terminal receiver circuitry 54 may comprise, e.g., amplifiers, demodulation circuitry, and other conventional receiver equipment.

[0053] Fig. 8A and Fig. 8B further show wireless terminal 30 also comprising wireless terminal processor circuitry, e.g., one or more wireless terminal processor(s) 60. The wireless terminal 30, e.g., wireless terminal processor(s) 60, may comprise terminal frame or message handler / generator 62. The wireless terminal 30 may also comprise user interfaces 66, including one or more user interfaces. Such user interfaces may serve for both user input and output operations, and may comprise (for example) a keyboard, a mouse, a screen such as a touch screen that can both display information to the user and receive information entered by the user. The user interface 66 may also include other types of devices, such as a speaker, a microphone, or a haptic feedback device, for example.

[0054] In the example embodiment and mode of Fig. 8A the network node NN which performs acts such as act 6-1 and act 6-2 of Fig. 6 is a core network node, such as core network node 21 of Fig. 8A. Fig. 8A particularly shows that the core node processor(s) 22 of core network node 21 is configured to establish the association between a configuration parameter and a format type for a control element (MAC CE) of a medium access control (MAC) protocol, as described herein. Further, in the example embodiment and mode of Fig. 8A, the core-RAN interface circuit 23 is the interface that, under direction of core node processor(s) 22, transmits the signal S which includes the configuration parameter to the wireless terminal 30.

[0055] In the example embodiment and mode of Fig. 8B the network node NN which performs acts such as act 6-1 and act 6-2 of Fig. 6 is a radio access network node , such as radio access network node 26 of Fig. 8B. Fig. 8B particularly shows that the base station processor(s) 34 of base station node 26 comprise an association controller 42 which serves to establish the association between a configuration parameter and a format type for a control element (MAC CE) of a medium access control (MAC) protocol, as described herein. Further, in the example embodiment and mode of Fig. 8B, the core-RAN interface circuit 23 is the base station transceiver circuitry 36, under direction of base station processor(s) 34, transmits the signal S which includes the configuration parameter to the wireless terminal 30.

[0056] The wireless terminal 30 of both Fig. 8A and Fig. 8B may perform the acts 6-3 through and including 6-5 of Fig. 6. In particular the wireless terminal processor(s) 60 may be involved in performing act 6-3 through act 6-3. The wireless terminal processor(s) 60 are configured to perform many functions for operation of the wireless terminal in general, as known to the person skilled in the art. For performing functions germane to the technology disclosed herein, in an example embodiment and mode the wireless terminal processor(s) 60 may be structure or configured to comprise or realize several functionalities or units including signal analyzer 70 and MAC PDU handler 72. The signal analyzer 70, which may comprise or be subsumed in terminal frame or message handler / generator 62, analyzes the signal S to obtain the configuration parameter which, in an example embodiment and mode, is an LCID value. The MAC PDU handler 72, which also may comprise or be subsumed in terminal frame or message handler / generator 62, serves to perform act 6-5, e.g., to determine from the configuration parameter of the signal S which one of plural MAC CE format types the wireless terminal should use to interpret a control element (MAC CE) of a medium access control (MAC) protocol data unit (MAC PDU) which is received by the wireless terminal over the radio access network.

[0057] Therefore, in one of its example aspects, e.g., in the example embodiments and modes of Fig. 6, Fig. 8A, the network (e.g. gNB in 5G wireless communications systems) configures one or more MAC CE formats that the UE should recognize. The network also configures an LCID value for each MAC CE format. The UE identifies which MAC CE format should be used to interpret a MAC CE in a MAC PDU using association between the MAC CE format and the LCID value. In a case that a value indicated by a LCID field in an MAC subheader associated with the MAC CE is a first LCID, the UE uses a MAC CE format associated with the first LCID. In a case that a value of a LCID field in a MAC subheader associated with the MAC CE is a second LCID, the UE uses a MAC CE format associated with the second LCID. The configuration is based on an RRC signaling from a gNB or other network entity to the UE.

[0058] Moreover, a default LCID value may be pre-configured for the case that the LCID value of the MAC CE format is not configured. If a MAC CE format has its default LCID value and its LCID value is not configured by an RRC signaling, the UE uses the default value for the MAC CE format. If a MAC CE format does not have its default LCID value and its LCID value is not configured by an RRC signaling, the UE assumes that the MAC CE format is not configured to use.

[0059] The RRC signaling for signal S may any appropriate radio resource control (RRC) signal, such as RRCSetup, RRCReconfiguration, RRCResume or RRCRelease message.

[0060] In accordance with an example aspect of the technology of the example embodiment and mode of Fig. 6, Fig. 8A, and Fig 8B, the location of a field in the MAC CE is configured by an RRC signaling from a gNB or other network entity to the UE. The network (gNB (base station) or other network entity) configures one or more MAC CE format and the associated a LCID value that the UE should use. In an example implementation, only a subset of the MAC may have a configurable LCID value.

[0061] CONTROL ELEMENTS WITH CONFIGURABLE FORMATS Fig. 9 shows a communications system which comprises a network node NN and a wireless terminal UE. As example aspect of the example embodiment and mode of Fig. 9 includes control elements with configurable format for medium access control (MAC). The network node NN of Fig. 9 may be either a core network node or a node of a radio access network, such as a RAN access node, e.g., a base station node, for example. The wireless terminal UE may be any electronic device used to communicate voice and / or data via a telecommunications system, such as (but not limited to) a cellular network, as mentioned above Fig. 9 depicts certain basic, example, representative acts or steps performed in the communications system, e.g., by network node NN and wireless terminal UE. Such basic acts are now briefly described with reference to act 9-1 through and including act 9-6 and are understood more fully in the context of the ensuing description.

[0062] Act 9-1 comprises a network node NN configuring a format, e.g., a format configuration, of a medium access control (MAC) control element (MAC CE). Act 9-1 may comprise configuring the at least one of the following: a location of a field / bit, size of the field, and size of the MAC CE. That is, the format configuration may include at least one of the following: a location of a field / bit, size of the field, and size of the MAC CE. Act 9-1 may comprise configuring the location of plural fields of the MAC CE, or of size of plural fields. Optionally, act 9-1 may further comprise the network node NN configuring a size of the MAC CE. Act 9-2 comprises including an indication of the format configuration of the medium access control (MAC) control element (MAC CE) in a signal. Act 9-3 comprises transmitting the signal to the wireless terminal, e.g., to wireless terminal 30. The signal transmitted from the network node NN to wireless terminal 30 may comprise a radio resource control (RRC) signal. Act 9-4 comprises the wireless terminal receiving the signal from a network node. Act 9-5 comprises the wireless terminal determining from the signal the indication of the format configuration for a medium access control (MAC) control element (MAC CE). The wireless terminal may also optionally determine the size of the MAC CE from the signal. E2-1-6 comprises receiving a medium access control (MAC) control element (MAC CE) for which the signal applies. An optional but typical act 9-7 comprises the wireless terminal using format configuration to decode at least part of the medium access control (MAC) control element (MAC CE).

[0063] As understood with reference to example implementations described herein, act 9-1 and act 9-2 may be performed by processor circuitry of network node NN, and act 9-5 and act 9-6 may be performed by processor circuitry of wireless terminal 30. Moreover, the technology disclosed herein encompasses computer program products wherein coded instructions are stored on tangible non-transient media which, when executed by a processor, perform one or more of the acts shown in Fig. 9.

[0064] Describing operation of the example embodiment and mode of Fig. 9 in more detail, in an exemplary embodiment, the network (e.g. gNB in 5G wireless communications systems) configures the location of each field of a MAC CE that the UE should use. The configuration is based on an RRC signaling from a gNB or other network entity to the UE. Also, the total size of MAC CE can be configured by the same RRC message. Based on the field and the location and the size, the MAC CE format is determined by the UE, e.g., by wireless terminal 30.

[0065] Fig. 10 depicts Single-entry Power Headroom Report (PHR) MAC CE format of 3GPR NR MAC specification. The MAC CE of Fig. 10 consists of P bit, R bit, PH (Power Headroom) field of 6 bits, MPE / DPC / R field of 2 bits, and Pcmax,f,c field of 6 bits. Currently, the format of Fig. 10 is deterministic, so all the UEs supporting the same release of the specification use the same format. If an unauthorized user decodes the MAC CE, all the information of the fields in the MAC CE will be exposed to the unauthorized user.

[0066] To resolve the problem, e.g. the problem of exposure of fields of the MAC CE to unauthorized user(s), in an exemplary embodiment, the exact location of each field and total size of a MAC CE can be configured by RRC signaling. Fig. 11 depicts a first example of single-entry PHR MAC CE format by configuration of field location (position) and the size of the MAC CE. In the MAC CE configuration of Fig. 11, , it is indicated that the configuration is for single-entry Power Headroom Report MAC CE, the size of the MAC CE is 2 bytes (octets), PH field (Type 1 PH of PCell) of 6 bits long starts from the 3rd bit from the right, P bit is located at the first bit (from the right), Pcmax,f,c field starts from the 9th bit, and MPE field starts from the 15th bit. In the example of Fig. 11, the start position is counted from the right side of the first octet. However, it is possible to count from the left side or from any other predetermined position. Thus, the location of the field of the medium access control (MAC) control element (MAC CE) may be expressed with respect to a reference location of the medium access control (MAC) control element (MAC CE). Any bit which is not configured with any field is considered as R (reserved) bit. In the example of Fig. 11, the second bit is considered as R bit.

[0067] An example format of the signal S for the example embodiment and mode of Fig. 9 may also be understood with reference to the single-entry PHR MAC CE format shown in Fig. 11. For example, when deformating the RRC signal, the UE would decode the first field of the signal and determine that the MAC type is single entry PHR, e.g., the first field may include some value that indicates single entry PHR, and other values in the first field would indicate other types of MAC CE. Then, based on the value in the first field of the RRC signal, the decoder knows what other fields are included in the order shown in the chart of Fig. 11. That is, the second field of the signal would include a value of number of octets, and the third and remaining fields would specify the bit positions of the remaining fields in the order given (Type 1 PH, P, Pcmax, MPE).

[0068] In some exemplary embodiments, only subset of fields / bits of a MAC CE may have a configurable location by the RRC signaling. Some essential fields / bits may have a fixed location. For those fields / bits, their locations are deterministic. The characteristic of this embodiment is that fields / bits are categorized into two groups: 1) fields / bits whose location is fixed, 2) fields / bits whose location is not fixed but configured by an RRC message. Thus in some example embodiments and modes, the network node NN may exclude from the signal a location of a field of the medium access control (MAC) control element (MAC CE) for which a default location is specified, e.g., for the field / bit whose location is fixed. In such a situation, the wireless terminal may use a default location for a field of the medium access control (MAC) control element (MAC CE) for which field location is not configured in the signal. Moreover, the wireless terminal may know to exclude from the medium access control (MAC) control element (MAC CE) a field for which the wireless terminal does not have a default location and for which a field location is not configured in the signal.

[0069] In some example embodiments and situations, it may not be possible to separately configure all MAC CE’s fields by an RRC signaling. The separate configuration of all MAC CE’s fields may not be possible due to the increase in the signaling overhead. In such situations, such as when signaling overhead is a concern, default location(s) of fields / bits may be pre-configured for many of not all of the MAC CE fields / bits. The default location is used when the location of the fields / bits is not configured in a simplified RRC signal that includes fields / bits only for those MAC CE fields for which the network does not want to use the default location(s). If a field / bit has its default location and its location is not configured by the RRC signaling, the UE uses the default location for the field / bit. On the other hand, it a field / bit does not have its default location and its location is not configured by an RRC signaling, the UE assumes or expects that the field / bit is not included in the MAC CE. The default location of field / bit can be pre-defined by the specification, or pre-defined by the network and UE.

[0070] In the example embodiments in which one or more field(s) / bit(s) of the MAC CE is preconfigured, or for which a default value is known both to the network node NN and the wireless terminal, the RRC signal, e.g., signal S, may not include a signal field corresponding to such location. For such a signal S in which not all signal field(s) / bit(s) are included, the RRC protocol provides a way of designating “optional fields” and whether such optional signal fields are included in the signal or not. For example, each optional field may have an indicator which specifies whether the field is present or not. The indicator may be binary (0 and 1). If the indicator says that the signal field is present, it will be present. Accordingly, the RRC protocol provides a mapping of the fields that are present so that interpretation of the RRC signal can be understood when the signal omits signal fields corresponding to default location values, for example.

[0071] In some exemplary embodiments, the default location may be used before a specified time point. The time point could be either the entry of RRC connected state, upon reception of an RRCSetup, upon transmission of RRCSetupComplete, upon reception of RRCReconfiguration, upon transmission of RRCReconfigurationComplete, upon reception of RRCResume, upon transmission of RRCResumeComplete, or other specified time point.

[0072] In an exemplary embodiment, the default location can be used only before a specified time point. The default location is not used after the specified time point. In other words, the field / bit whose location is not configured by an RRC message is considered as not configured to use, irrespective of the default location. The time point could be either the entry of RRC connected state, upon reception of an RRCSetup, upon transmission of RRCSetupComplete, upon reception of RRCReconfiguration, upon transmission of RRCReconfigurationComplete, upon reception of RRCResume, upon transmission of RRCResumeComplete, or other specified time point.

[0073] In an exemplary embodiment, it is possible that different UEs may use different MAC CE formats for the same MAC CE, for the same type of MAC CE. For example, a first single-entry Power Headroom Report MAC CE received by a first wireless terminal may be provided by the network node NN with a first signal which prescribes a first set of one or more locations for one or more MAC CE fields, while a second single-entry Power Headroom Report MAC CE received by a second wireless terminal may be provided by the network node NN with a second signal which prescribes a second and different set of one or more locations for one or more MAC CE fields.

[0074] Fig. 12 depicts a second example of single-entry PHR MAC CE format by configuration of field location (position) and the size of the MAC CE. In the MAC CE configuration of Fig. 12, it is indicated that the configuration is for single-entry Power Headroom Report MAC CE, the size of the MAC CE is 2 bytes (octets), PH field (Type 1 PH of PCell) of 6 bits long starts from the 3rd bit from the right, P bit is located at the first bit (from the right). Pcmax,f,c field is not configured by the RRC signaling but it has a default location starting from the 9th bit. MPE field is not configured by the RRC signaling but it does not have a default location. Therefore, an MPE field is not included in the MAC CE format. In the example of Fig. 12, the start position is counted from the right side. However, it is possible to count froms the left side. Any bit which is not configured with any field is considered as R (reserved) bit. In the example of Fig. 12, the second bit is considered as R bit.

[0075] In an exemplary embodiment, it may be possible that the size of the MAC CE is not configured by RRC signaling. In this case, the default size can be used. The default size is a pre-defined value to be used when the size of the MAC CE is not configured. In another exemplary case, the minimum octet size (byte aligned size) of the MAC CE which can include all the configured field and the fields which have to be presented in the MAC CE. The fields which have to be presented in the MAC CE may include the fields / bits having the default location. In another exemplary case, the pre-defined maximum size can be used. The pre-defined maximum size may be the maximum size of the value range of the MAC CE, which can be configured by the RRC signaling.

[0076] Thus, a MAC CE configuration may comprise at least one of the following: LCID value for the MAC CE, and MAC CE format configuration. Based on the format configuration of location of fields / bit in the MAC CE, size of the MAC CE and size of fields, the MAC CE format can be determined. Thus, one of the example aspects of the technology disclosed herein makes MAC CE format configurable by the network. Fig. 13 depicts an exemplary signaling flow of MAC CE configuration. When the network node (base station in the figure) decides to provide / configure / change the MAC CE configuration for the UE, the corresponding MAC CE configuration can be transmitted from the network to the UE. The message which delivers the MAC CE configuration may be an RRC message. The UE applies the configuration when the UE receives the configuration. After the UE applies the MAC CE configuration, both the network and UE perform transmissions and / or reception based on the configured MAC CE configuration.

[0077] Fig. 14A and Fig. 14B show in more detail example structures and functionalities that may, in respective first and second example embodiments and modes, comprise or be included in the communications network of Fig. 9. In the communications system of Fig. 14A, the network node NN comprises a core network node. By contrast, in the communications system of Fig. 14B, the network node NN comprises a radio access network.

[0078] Fig. 14A and Fig. 14B both show that the example communications networks, which may be 5G networks, for example, comprise core network 20. The core network 20 may comprise one or more core network nodes, such as core network node 21. The core network node 21 may comprise or be realized by any suitable type of core network node, such as a core network management entity, e.g., an Access and Mobility Management Function (AMF). One or more of the core network nodes 21 may comprise core node processor circuitry, such as core node processor(s) 22. The core network 20 and one or more of its constituent core network nodes 21 is connected to at least one radio access network 24 through a core-RAN interface circuit 23. The core-RAN interface circuit 23 may be connected to wireline(s) 28.

[0079] The radio access network 24 in turn comprises one or more radio access network (RAN) nodes, such as example base station node 26. The base station node 26 serves at least one cell. The radio access network, RAN, 24 typically comprises plural access nodes, one example access node 26 being illustrated as a base station node in Fig. 14A and Fig. 14B.

[0080] Fig. 14A and Fig. 14B both show the radio access network 24, and base station node 26 through its cell in particular communicating with wireless terminal 30 across a radio or air interface 32. The base station node 26 may, and usually does, communicate with plural wireless terminals across the air interface 32. Only one wireless terminal 30 is shown for sake of simplicity, it being understood that other wireless terminals may be provided and may operate in similar manner as the wireless terminal 30 herein illustrated.

[0081] Fig. 14A and Fig. 14B show base station node 26 as comprising base station processor circuitry which may comprise one or more base station processors 34, as well as base station transceiver circuitry 36. As illustrated in Fig. 5A, the base station transceiver circuitry 36 may be a transmission and reception point (TRP). The transmission and reception point (TRP) 36 may further comprise transmitter circuitry and receiver circuitry. The base station processors 34 may comprise frame / message handler / generator 40 which prepares and generates information including user data and messages, e.g., signaling, for transmission over the radio interface 32, as which also processes information received over the radio interface 32.

[0082] The base station node 26 may be structured essentially as shown in Fig. 14A and Fig. 14B or maybe a node having architecture such as split architecture comprising a central unit and one or more distributed units that comprise mobile termination (MT). The base station processor(s) may include one or more TRPs.

[0083] Fig. 14A and Fig. 14B also show various example constituent components and functionalities of wireless terminal 30. For example, Fig. 14A and Fig. 14B show wireless terminal 30 as comprising terminal transceiver circuitry 50. The transceiver circuitry 50 in turn may comprise terminal transmitter circuitry 52 and terminal receiver circuitry 54. The terminal transceiver circuitry 50 may include antenna(e) for the wireless transmission. Terminal transmitter circuitry 52 may include, e.g., amplifier(s), modulation circuitry and other conventional transmission equipment. Terminal receiver circuitry 54 may comprise, e.g., amplifiers, demodulation circuitry, and other conventional receiver equipment.

[0084] Fig. 14A and Fig. 14B further show wireless terminal 30 also comprising wireless terminal processor circuitry, e.g., one or more wireless terminal processor(s) 60. The wireless terminal 30, e.g., wireless terminal processor(s) 60, may comprise terminal frame or message handler / generator 62. The wireless terminal 30 may also comprise user interfaces 66, including one or more user interfaces. Such user interfaces may serve for both user input and output operations, and may comprise (for example) a keyboard, a mouse, a screen such as a touch screen that can both display information to the user and receive information entered by the user. The user interface 66 may also include other types of devices, such as a speaker, a microphone, or a haptic feedback device, for example.

[0085] In the example embodiment and mode of Fig. 14A the network node NN which performs acts such as act 9-1 through act 9-3 of Fig. 9 is a core network node, such as core network node 21 of Fig. 14A. Fig. 14A particularly shows that the core node processor(s) 22 of core network node 21 is configured to configure a format configuration for a medium access control (MAC) control element (MAC CE). As indicated previously the format configuration may include at least one of the following: a location of a field / bit (and preferably locations of plural fields), size of the field(s), and size of the MAC CE. Further, in the example embodiment and mode of Fig. 14A, the core-RAN interface circuit 23 is the interface that, under direction of core node processor(s) 22, transmits the signal S which includes the location of the field(s) of the medium access control (MAC) control element (MAC CE), and optionally the size of the MAC CE, to the wireless terminal 30.

[0086] In the example embodiment and mode of Fig. 14B the network node NN which performs acts such as act 9-1 and act 9-2 of Fig. 9 is a radio access network node, such as radio access network node 26 of Fig. 14B. Fig. 14B particularly shows that the base station processor(s) 34 of base station node 26 comprise MAC CE format controller 82 which serves configure or prepare a format configuration for a medium access control (MAC) control element (MAC CE). Further, in the example embodiment and mode of Fig. 14B, the base station transceiver circuitry 36, under direction of base station processor(s) 34, transmits the signal S which includes the configuration parameter to the wireless terminal 30.

[0087] The wireless terminal 30 of both Fig. 14A and Fig. 14B may perform the acts E2-1-3 through and including E2-1-7 of Fig. 9. In particular the wireless terminal processor(s) 60 may be involved in performing act 9-5 and optional act 9-7. The wireless terminal processor(s) 60 are configured to perform many functions for operation of the wireless terminal in general, as known to the person skilled in the art. For performing functions germane to the technology disclosed herein, in an example embodiment and mode the wireless terminal processor(s) 60 may be structure or configured to comprise or realize several functionalities or units including signal analyzer 70 and MAC PDU handler 72. The signal analyzer 70, which may comprise or be subsumed in terminal frame or message handler / generator 62, analyzes the signal S to obtain the format information from the Signal S, including the location(s) of the field(s) of the MAC CE. The MAC PDU handler 72, which also may comprise or be subsumed in terminal frame or message handler / generator 62, serves to perform act 9-5, e.g., to interpret a control element (MAC CE) of a medium access control (MAC) protocol data unit (MAC PDU) which is received by the wireless terminal over the radio access network based on the information included in the signal S, i.e., the format configuration, e.g., the location(s) of the field(s), and optionally if not a default value, the size of the MAC CE.

[0088] Therefore, in one of its example aspects, e.g., in the example embodiments and modes of Fig. 9, Fig. 14A, and Fig. 14B, the location of a field in the MAC CE is configured by an RRC signaling from a gNB or other network entity to the UE. A default location may be pre-configured for the case that the location of a field is not configured.

[0089] If a field of the MAC CE has its default location and its location is not configured by an RRC signaling, the UE uses the default location for the field. If a field of the MAC CE does not have its default location and its location is not configured by an RRC signaling, the UE assumes that the field is not present.

[0090] The RRC signaling may be either RRCSetup, RRCReconfiguration, RRCResume or RRCRelease message.

[0091] Furthermore, in one of its example aspects, e.g., in the example embodiments and modes of Fig. 9, Fig. 14A, and Fig. 14B, the size of the MAC CE is configured by an RRC signaling from a gNB or other network entity to the UE. If the size of the MAC CE is not configured, the following options exist: Option 1: Default size is used.

[0092] Option 2: The minimum octet size which can include all the configured fields and the fields which have to be presented in the MAC CE.

[0093] Option 3: The pre-defined maximum size is used.

[0094] For some fields / bits of the MAC CE, default size may be pre-configured for the case that the size of a field is not configured. If a field of the MAC CE has its default size and its size is not configured by an RRC signaling, the UE uses the default size for the field. If a field of the MAC CE does not have its default size and its size is not configured by an RRC signaling, the UE assumes that the field is not present.

[0095] The default MAC CE format is used for message of a part of random access procedure.

[0096] In the example embodiments and modes of Fig. 9, Fig. 14A, and Fig. 14B, the network (gNB (base station) or other network entity) configures the MAC CE format which the UE should use. The format configuration may include at least one of the following: location of a field / bit, size of the field, and size of the MAC CE. The format configuration may be done by RRC signaling from gNB (base station) or other network entity to the UE. The RRC signaling may be either RRCSetup, RRCReconfiguration, RRCResume or RRCRelease message. For some fields / bits of the MAC CE, default location may be pre-configured for the case that the location of a field is not configured. If a field of the MAC CE has its default location and its location is not configured by an RRC signaling, the UE uses the default location for the field. If a field of the MAC CE does not have its default location and its location is not configured by an RRC signaling, the UE assumes that the field is not present.

[0097] CONFIGURABLE MEDIUM ACCESS CONTROL SUBHEADERS Fig. 15 shows a communications system which comprises a network node NN and a wireless terminal UE. As example aspect of the example embodiment and mode of Fig. 15 includes medium access control (MAC) subheader(s) with a configurable format. The network node NN of Fig. 15 may be either a core network node or a node of a radio access network, such as a RAN access node, e.g., a base station node, for example. The wireless terminal UE may be any electronic device used to communicate voice and / or data via a telecommunications system, such as (but not limited to) a cellular network, as mentioned above Fig. 15 depicts certain basic, example, representative acts or steps performed in the communications system, e.g., by network node NN and wireless terminal UE. Such basic acts are now briefly described with reference to act 15-1 through and including act 15-6 and are understood more fully in the context of the ensuing description.

[0098] Act 15-1 comprises a network node NN configuring a format, e.g., a format configuration, of a medium access control (MAC) subheader. Act 15-1 may comprise configuring the at least one of the following: a location of a field / bit, size of the field, and size of the MAC subheader. That is, the format configuration may include at least one of the following: a location of a field / bit, size of the field, and size of the MAC subheader. Act 15-1 may comprise configuring the location of plural fields of the MAC subheader, or of size of plural fields. Optionally, act 15-1 may further comprise the network node NN configuring a size of the MAC subheader. Act 15-2 comprises including an indication of the format configuration of the medium access control (MAC) subheader in a signal. Act 15-3 comprises transmitting the signal to the wireless terminal, e.g., to wireless terminal 30. The signal transmitted from the network node NN to wireless terminal 30 may comprise a radio resource control (RRC) signal. Act 15-4 comprises the wireless terminal receiving the signal from a network node. Act 15-5 comprises the wireless terminal determining from the signal the indication of the format configuration for a medium access control (MAC) subheader. The wireless terminal may also optionally determine the size of the MAC subheader from the signal. E3-1-6 comprises receiving a medium access control (MAC) PDU for which the signal applies. An optional but typical act 15-7 comprises the wireless terminal using format configuration to decode at least part of the medium access control (MAC) PDU.

[0099] As understood with reference to example implementations described herein, act 15-1 and act 15-2 may be performed by processor circuitry of network node NN, and act 15-5 and act 15-6 may be performed by processor circuitry of wireless terminal 30. Moreover, the technology disclosed herein encompasses computer program products wherein coded instructions are stored on tangible non-transient media which, when executed by a processor, perform one or more of the acts shown in Fig. 15.

[0100] Describing operation of the example embodiment and mode of Fig. 15 in more detail, the network (e.g. gNB in 5G wireless communications systems) configures the location of each field of a MAC subheader that the UE should use. The configuration is based on an RRC signaling from a gNB or other network entity to the UE. Also, the total size of MAC subheader can be configured by the same RRC message. Based on the field and the location and the size, the MAC subheader format is determined.

[0101] In prior art practice, the MAC subheader format is deterministic, so all the UEs supporting the same release of the specification use the same subheader format. As a result of this prior art practice, if an unauthorized user decodes the MAC subheader, all the information of the fields in the MAC subheader will be exposed to the unauthorized user.

[0102] To resolve the problem of unauthorized access, in the example embodiment and mode of Fig. 15, the exact location of each field (and / or total size) of a MAC subheader can be configured by RRC signaling. In some exemplary implementations, only subset of fields / bits of a MAC subheader may have a configurable location by the RRC signaling.

[0103] Some essential fields / bits may have a fixed location. For those fields / bits, their locations are deterministic. The characteristic of this embodiment is that fields / bits of the MAC subheader are categorized into two groups: 1) fields / bits whose location is fixed, 2) fields / bits whose location is not fixed but configured by an RRC message. Thus in some example embodiments and modes, the network node NN may exclude from the signal a location of a field of the medium access control (MAC) subheader for which a default location is specified, e.g., for the field / bit whose location is fixed. In such a situation, the wireless terminal may use a default location for a field of the medium access control (MAC) subheader for which field location is not configured in the signal. Moreover, the wireless terminal may know to exclude from the medium access control (MAC) subheader a field for which the wireless terminal does not have a default location and for which a field location is not configured in the signal.

[0104] In some example embodiments and situations, it It may not be possible to separately configures all MAC subheader fields using RRC signaling. The separate configuration of all MAC subheader fields may not be possible due to the increase in the signaling overhead. In such situations, such as when the signaling overhead is a concern, default location(s) of fields / bits may be pre-configured for many if not all of the MAC subheader fields / bits. The default location is used when the location of the fields / bits is not configured in a simplified RRC signal that includes fields / bits only for those MAC subheader fields for which the network does not want to use the default location(s) If a field / bit has its default location and its location is not configured by an RRC signaling, the UE uses the default location for the field / bit. On the other hand if a field / bit does not have its default location and its location is not configured by an RRC signaling, the UE assumes or expects that the field / bit is not included in the MAC subheader. The default location of field / bit can be pre-defined by the specification, or pre-defined by the network and UE.

[0105] In the example embodiments in which one or more field(s) / bit(s) of the MAC subheader is preconfigured, or for which a default value is known both to the network node NN and the wireless terminal, the RRC signal, e.g., signal S, may not include a signal field corresponding to such location. For such a signal S in which not all signal field(s) / bit(s) are included, the RRC protocol provides a way of designating “optional fields” and whether such optional signal fields are included in the signal or not. For example, each optional field may have an indicator which specifies whether the field is present or not. The indicator may be binary (0 and 1). If the indicator says that the signal field is present, it will be present. Accordingly, the RRC protocol provides a mapping of the fields that are present so that interpretation of the RRC signal can be understood when the signal omits signal fields corresponding to default location values, for example.

[0106] In some exemplary embodiments, the default location may be used before a specified time point. The time point could be either the entry of RRC connected state, upon reception of an RRCSetup, upon transmission of RRCSetupComplete, upon reception of RRCReconfiguration, upon transmission of RRCReconfigurationComplete, upon reception of RRCResume, upon transmission of RRCResumeComplete, or other specified time point.

[0107] For MAC PDU transmitted / received before the completion of random access procedure, the default location may be used. For MAC PDU transmitted / received as a part of random access procedure, the default location may be used. In an exemplary embodiment, CCCH message or random access-related message may use a default MAC subheader format using the default location, in order to avoid the confusion between the network and UE.

[0108] In an exemplary embodiment, the default location can be used only before a specified time point. The default location is not used after the specified time point. In other words, the field / bit whose location is not configured by an RRC message is considered as not configured to use, irrespective of the default location. The time point could be either the entry of RRC connected state, upon reception of an RRCSetup, upon transmission of RRCSetupComplete, upon reception of RRCReconfiguration, upon transmission of RRCReconfigurationComplete, upon reception of RRCResume, upon transmission of RRCResumeComplete, or other specified time point.

[0109] In an exemplary embodiment, it is possible that different UEs may use different MAC subheader formats.

[0110] Fig. 16A and Fig. 16B show in more detail example structures and functionalities that may, in respective first and second example embodiments and modes, comprise or be included in the communications network of Fig. 15. In the communications system of Fig. 16A, the network node NN comprises a core network node. By contrast, in the communications system of Fig. 16B, the network node NN comprises a radio access network.

[0111] Fig. 16A and Fig. 16B both show that the example communications networks, which may be 5G networks, for example, comprise core network 20. The core network 20 may comprise one or more core network nodes, such as core network node 21. The core network node 21 may comprise or be realized by any suitable type of core network node, such as a core network management entity, e.g., an Access and Mobility Management Function (AMF). One or more of the core network nodes 21 may comprise core node processor circuitry, such as core node processor(s) 22. The core network 20 and one or more of its constituent core network nodes 21 is connected to at least one radio access network 24 through a core-RAN interface circuit 23. The core-RAN interface circuit 23 may be connected to wireline(s) 28.

[0112] The radio access network 24 in turn comprises one or more radio access network (RAN) nodes, such as example base station node 26. The base station node 26 serves at least one cell. The radio access network, RAN, 24 typically comprises plural access nodes, one example access node 26 being illustrated as a base station node in Fig. 16A and Fig. 16B.

[0113] Fig. 16A and Fig. 16B both show the radio access network 24, and base station node 26 through its cell in particular communicating with wireless terminal 30 across a radio or air interface 32. The base station node 26 may, and usually does, communicate with plural wireless terminals across the air interface 32. Only one wireless terminal 30 is shown for sake of simplicity, it being understood that other wireless terminals may be provided and may operate in similar manner as the wireless terminal 30 herein illustrated.

[0114] Fig. 16A and Fig. 16B show base station node 26 as comprising base station processor circuitry which may comprise one or more base station processors 34, as well as base station transceiver circuitry 36. As illustrated in Fig. 5A, the base station transceiver circuitry 36 may be a transmission and reception point (TRP). The transmission and reception point (TRP) 36 may further comprise transmitter circuitry and receiver circuitry. The base station processors 34 may comprise frame / message handler / generator 40 which prepares and generates information including user data and messages, e.g., signaling, for transmission over the radio interface 32, as which also processes information received over the radio interface 32.

[0115] The base station node 26 may be structured essentially as shown in Fig. 16A and Fig. 16B or maybe a node having architecture such as split architecture comprising a central unit and one or more distributed units that comprise mobile termination (MT). The base station processor(s) may include one or more TRPs.

[0116] Fig. 16A and Fig. 16B also show various example constituent components and functionalities of wireless terminal 30. For example, Fig. 16A and Fig. 16B show wireless terminal 30 as comprising terminal transceiver circuitry 50. The transceiver circuitry 50 in turn may comprise terminal transmitter circuitry 52 and terminal receiver circuitry 54. The terminal transceiver circuitry 50 may include antenna(e) for the wireless transmission. Terminal transmitter circuitry 52 may include, e.g., amplifier(s), modulation circuitry and other conventional transmission equipment. Terminal receiver circuitry 54 may comprise, e.g., amplifiers, demodulation circuitry, and other conventional receiver equipment.

[0117] Fig. 16A and Fig. 16B further show wireless terminal 30 also comprising wireless terminal processor circuitry, e.g., one or more wireless terminal processor(s) 60. The wireless terminal 30, e.g., wireless terminal processor(s) 60, may comprise terminal frame or message handler / generator 62. The wireless terminal 30 may also comprise user interfaces 66, including one or more user interfaces. Such user interfaces may serve for both user input and output operations, and may comprise (for example) a keyboard, a mouse, a screen such as a touch screen that can both display information to the user and receive information entered by the user. The user interface 66 may also include other types of devices, such as a speaker, a microphone, or a haptic feedback device, for example.

[0118] In the example embodiment and mode of Fig. 16A the network node NN which performs acts such as act 15-1 through act 15-3 of Fig. 15 is a core network node, such as core network node 21 of Fig. 16A. Fig. 16A particularly shows that the core node processor(s) 22 of core network node 21 is configured to configure a format configuration for a medium access control (MAC) subheader. As indicated previously the format configuration may include at least one of the following: a location of a field / bit (and preferably locations of plural fields), size of the field(s), and size of the MAC subheader. Further, in the example embodiment and mode of Fig. 16A, the core-RAN interface circuit 23 is the interface that, under direction of core node processor(s) 22, transmits the signal S which includes the location of the field(s) of the medium access control (MAC) subheader, and optionally the size of the MAC subheader, to the wireless terminal 30.

[0119] In the example embodiment and mode of Fig. 16B the network node NN which performs acts such as act 15-1 and act 15-2 of Fig. 15 is a radio access network node, such as radio access network node 26 of Fig. 16B. Fig. 16B particularly shows that the base station processor(s) 34 of base station node 26 comprise MAC subheader format controller 86 which serves configure or prepare a format configuration for a medium access control (MAC) subheader. Further, in the example embodiment and mode of Fig. 16B, the base station transceiver circuitry 36, under direction of base station processor(s) 34, transmits the signal S which includes the configuration parameter to the wireless terminal 30.

[0120] The wireless terminal 30 of both Fig. 16A and Fig. 16B may perform the acts E3-1-3 through and including act 15-7 of Fig. 15. In particular the wireless terminal processor(s) 60 may be involved in performing act 15-2 and optional act 15-7. The wireless terminal processor(s) 60 are configured to perform many functions for operation of the wireless terminal in general, as known to the person skilled in the art. For performing functions germane to the technology disclosed herein, in an example embodiment and mode the wireless terminal processor(s) 60 may be structure or configured to comprise or realize several functionalities or units including signal analyzer 70 and MAC PDU handler 72. The signal analyzer 70, which may comprise or be subsumed in terminal frame or message handler / generator 62, analyzes the signal S to obtain the format information from the Signal S, including the location(s) of the field(s) of the MAC subheader. The MAC PDU handler 72, which also may comprise or be subsumed in terminal frame or message handler / generator 62, serves to perform act 15-2, e.g., to interpret a subheaderof a medium access control (MAC) protocol data unit (MAC PDU) which is received by the wireless terminal over the radio access network based on the information included in the signal S, i.e., the format configuration, e.g., the location(s) of the field(s), and optionally if not a default value, the size of the MAC subheader.

[0121] In an example implementation, if signaling overhead is a concern or limitation, the size of the MAC subheader may not be configured by RRC signaling. In this case, the default size of the subheader can be used. The default size is a pre-defined value to be used when the size of the MAC subheader is not configured. In another example implementation, the minimum octet size (byte aligned size) of the MAC subheader, the minimum size which can include all the configured fields and the fields which have to be presented in the MAC subheader, can be used. The fields which have to be presented in the MAC subheader may include the fields / bits having the default location. In another example implementation, the pre-defined maximum size of the subheader can be used. The pre-defined maximum size may be the maximum size of the value range of the MAC subheader, which can be configured by the RRC signaling.

[0122] Thus, summarizing some of the foregoing, the example embodiment and mode of Fig. 15 includes configuring the location of a field in the MAC subheader by an RRC signaling from a gNB or other network entity to the UE. A default location may be pre-configured for the case that the location of a field is not configured. If a field of the MAC subheader has its default location and its location is not configured by an RRC signaling, the UE uses the default location for the field. If a field of the MAC subheader does not have its default location and its location is not configured by an RRC signaling, the UE assumes that the field is not present. The RRC signaling may be either RRCSetup, RRCReconfiguration, RRCResume or RRCRelease message.

[0123] Moreover, the example embodiment and mode of Fig. 15 optionally includes configuring the size of the MAC subheader by a RRC signaling from a gNB or other network entity to the UE. If the size of the MAC subheader is not configured, the following options are provided: Option 1: Default size is used.

[0124] Option 2: The minimum octet size which can include all the configured fields and the fields which have to be presented in the MAC subheader.

[0125] Option 3: The pre-defined maximum size is used The size of each field is determined by the number of possible configurations. Usually, the size is likely close to the maximum value. However, only a few configurations (values) are frequently used whereas other configurations (values) are theoretically possible but rarely used. For this reason, the size of each field in the MAC CE or MAC subheader can be configured by RRC signaling from a gNB or other network entity to the UE. It can reduce the size of MAC CE or the size of MAC subheader.

[0126] Fig. 17 depicts a default MAC subheader format where LCID field of 6 bits, F bit and L field of 8 bits . The length of L field depends on F bit information or other configuration. A 6 bit of LCID field can indicate 64 LCID values from 0 to 63 codepoint. If a UE requires more than 64 LCID values considering the number of logical channel data and the number of MAC CEs needed for the UE, eLCID field with one byte additional overhead shall be used. However, there is reserved bit (R bit) in the MAC CE.

[0127] Fig. 18 depicts an example of MAC subheader format where the size of LCID field is configured with 7 bits and F bit is not configured. Also, the location of the LCID field starting from the first bit from the right is configured. In the example, up to 128 LCID values can be configured to the UE. Since F bit determining the length of L field is not configured, the length of L field is fixed. In the example, 1 byte length of L field is assumed.

[0128] If the size of the field is not configured, the default size and default location can be used. The default size may be pre-configured for the case that the size of a field is not configured. If a field of MAC CE or MAC subheader has its default size and its size is not configured by an RRC signaling, the UE uses the default size for the field. If a field of MAC CE or MAC subheader does not have its default size and its size is not configured by an RRC signaling, the UE assumes that the field is not present.

[0129] For MAC PDU transmitted / received before the completion of random access procedure, the default size may be used. For MAC PDU transmitted / received as a part of random access procedure, the default size may be used. In an exemplary embodiment, CCCH message or random access-related message may use a default MAC subheader format or MAC CE format using the default location and size, in order to avoid the confusion between the network and UE.

[0130] For the technology disclosed herein it is generally assumed that at least one MAC subheader is included in a MAC PDU. However, there may be only one MAC header in the MAC PDU. In this case, the MAC header format can be configured by the network, similarly to the case of MAC subheader.

[0131] Based on the configuration of location of fields / bit in the MAC subheader, size of the MAC subheader and size of fields, MAC subheader format can be determined. Thus, this invention makes MAC subheader format configurable by the network. Fig. 19 depicts an exemplary signaling flow of MAC subheader configuration. When the network node (base station in the figure) decides to provide / configure / change the MAC subheader configuration for the UE, the corresponding MAC subheader configuration can be transmitted from the network to the UE. The message which delivers the MAC subheader configuration may be an RRC message. The UE applies the configuration when the UE receives the configuration. After the UE applies the MAC subheader configuration, both the network and UE perform transmissions and / or reception based on the configured MAC subheader configuration.

[0132] FURTHER CONSIDERATIONS The technology disclosed herein includes a configurable MAC CE and MAC subheader format by allowing RRC configuration to indicate size, location, and the presence based on default value. In some example example embodiments and modes, “default” can be replaced by “pre-configured” or “pre-defined” or determined without an RRC signaling to configure. A “default” means that it is used when a dedicated value is not configured by an RRC signaling.

[0133] Example aspects of the technology disclosed herein include the following features and / or benefits: A LCID value is not deterministic but is configurable by the network via an RRC signaling which is security protected. LCID value is not exposed to the attacker or unauthorized user.

[0134] The network can choose the value of LCID based on the demand of the LCID usage. For instance, only the MAC CEs which are likely to use can be configured with LCID value. It reduces the unnecessary reservation of LCID field. It reduces the header overhead due to eLCID field.

[0135] The location of each field of MAC CE or MAC subheader is not exposed to the attacker or unauthorized user.

[0136] It should be understood that the various foregoing example embodiments and modes may be utilized in conjunction with one or more example embodiments and modes described herein. For example, the example embodiments and modes of Fig. 6, Fig. 9, and Fig. 15 may be utilized in combination with one or more other example embodiments and modes disclosed herein.

[0137] Certain units and functionalities of the communications systems may be implemented by electronic machinery. For example, electronic machinery may refer to the processor circuitry described herein, such as core node processor(s) 22, base station processors 34, and wireless terminal processor(s) 60. Moreover, the term “processor circuitry” is not limited to mean one processor, but may include plural processors, with the plural processors operating at one or more sites. Moreover, as used herein the term “server” is not confined to one server unit but may encompass plural servers and / or other electronic equipment, and may be co-located at one site or distributed to different sites. With these understandings, Fig. 19 shows an example of electronic machinery, e.g., processor circuitry, as comprising one or more processors 490, program instruction memory 492; other memory 494 (e.g., RAM, cache, etc.); input / output interfaces 496 and 497, peripheral interfaces 498; support circuits 499; and busses 500 for communication between the aforementioned units. The processor(s) 490 may comprise the processor circuitries described herein, for example, core node processor(s) 22, base station processors 34, and wireless terminal processor(s) 60.

[0138] A memory or register described herein may be depicted by memory 194, or any computer-readable medium, may be one or more of readily available memory such as random access memory (RAM), read only memory (ROM), floppy disk, hard disk, flash memory or any other form of digital storage, local or remote, and is preferably of non-volatile nature, as and such may comprise memory. The support circuits 499 are coupled to the processors 490 for supporting the processor in a conventional manner. These circuits include cache, power supplies, clock circuits, input / output circuitry and subsystems, and the like.

[0139] The processes and methods of the disclosed embodiments may be implemented as a software routine. Alternatively or additionally, some or all of method steps that are disclosed therein may be performed in hardware as well as by a processor running software. As such, the embodiments may be implemented in software, as executed upon a computer system, in hardware as an application specific integrated circuit or other type of hardware implementation, or a combination of software and hardware. The software routines of the disclosed embodiments are capable of being executed on any computer operating system and is capable of being performed using any CPU architecture.

[0140] The functions of the various elements including functional blocks, including but not limited to those labeled or described as “computer”, “processor” or “controller”, may be provided through the use of hardware such as circuit hardware and / or hardware capable of executing software in the form of coded instructions stored on computer readable medium. Thus, such functions and illustrated functional blocks are to be understood as being either hardware-implemented and / or computer-implemented, and thus, machine-implemented.

[0141] In terms of hardware implementation, the functional blocks may include or encompass, without limitation, digital signal processor (DSP) hardware, reduced instruction set processor, hardware (e.g., digital or analog) circuitry including but not limited to application specific integrated circuit(s) [ASIC], and / or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.

[0142] In terms of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer and processor and controller may be employed interchangeably herein. When provided by a computer or processor or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed. Moreover, use of the term “processor” or “controller” may also be construed to refer to other hardware capable of performing such functions and / or executing software, such as the example hardware recited above.

[0143] Nodes that communicate using the air interface also have suitable radio communications circuitry. Moreover, the technology disclosed herein may additionally be considered to be embodied entirely within any form of computer-readable memory, such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.

[0144] The acts described herein, including but not limited to the acts of Fig. 6, Fig. 9, and Fig. 15, may be performed by a software program product stored tangibly on a non-transient computer-readable medium which, when executed by one or more processors as herein mentioned, performs such acts either in whole or in part.

[0145] Moreover, each functional block or various features of the wireless terminal 30, core network node 21, and base station node 26 employed in each of the aforementioned embodiments may be implemented or executed by circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.

[0146] It will be appreciated that the technology disclosed herein is directed to solving radio communications-centric issues and is necessarily rooted in computer technology and overcomes problems specifically arising in radio communications. Moreover, the technology disclosed herein improves resource selection and resource utilization in a communications system.

[0147] The technology disclosed herein encompasses one or more of the following non-limiting, non-exclusive example embodiments and modes: Embodiment E1-1: A network node of a telecommunications system, the network node comprising: processor circuitry configured to establish an association between a configuration parameter and a format type for a control element (MAC CE) of a medium access control (MAC) protocol, the configuration parameter being configured to indicate one of plural control element format types; an interface configured to transmit a signal which includes the configuration parameter to a wireless terminal.

[0148] Embodiment E1-2: The network node of Embodiment E1-1, wherein the configuration parameter comprises a Logical Channel Identity, LCID, value.

[0149] Embodiment E1-3: The network node of Embodiment E1-1, wherein the signal comprises a radio resource control (RRC) signal.

[0150] Embodiment E1-4: The network node of Embodiment E1-3, wherein the configuration parameter is included in an information signal of radio resource control (RRC) signal.

[0151] Embodiment E1-5: The network node of Embodiment E1-1, wherein the processor circuitry is configured to: establish a plurality of associations, each association being an association of one of a set of potential configuration parameters and one of a set of potential corresponding MAC CE format types; select a selected one of the set of potential configuration parameters for inclusion as the configuration parameter to be transmitted to the wireless terminal.

[0152] Embodiment E1-6: The network node of Embodiment E1-5, wherein the interface circuitry is configured to transmit the selected one of the set of potential configuration parameters to the wireless terminal and thereby enable the wireless terminal to determine from the selected one of the set of potential configuration parameters which one of the plural MAC CE format types the wireless terminal should use to interpret a MAC CE in a MAC protocol data unit (MAC PDU) to be received by the wireless terminal.

[0153] Embodiment E1-7: The network node of Embodiment E1-5, wherein the processor circuitry is configured to establish plural sets of associations, each set of associations comprising associations of plural potential configuration parameters and plural potential corresponding MAC CE format types for a set of one or more wireless terminals; and wherein the interface circuitry is configured to transmit a signal which includes a configuration parameter which is selected for the set of or more wireless terminals.

[0154] Embodiment E1-8: The network node of Embodiment E1-7, wherein the processor circuitry is configured to flexibly associate different ones of the plural sets of associations with different sets of one or more wireless terminals.

[0155] Embodiment E1-9: The network node of Embodiment E1-8, wherein the set of potential configuration parameters comprises a set of Logical Channel Identity, LCID, values, and wherein the processor circuitry is configured to associate, for different ones one or more wireless terminals, different LCID values for the same MAC CE format type.

[0156] Embodiment E1-10: The network node of Embodiment E1-5, wherein the set of potential configuration parameters comprises a set of Logical Channel Identity, LCID, values.

[0157] Embodiment E1-11: The network node of Embodiment E1-10, wherein the processor circuitry is further configured to preconfigure at least one Logical Channel Identity, LCID, value outside of the set as a default Logical Channel Identity, LCID, value and to cause the interface circuit to exclude the default Logical Channel Identity, LCID, value when transmitting a signal to the wireless terminal in a situation in which the network node intends for the wireless terminal to use a default MAC CE format type.

[0158] Embodiment E1-12: The network node of Embodiment E1-11, wherein the default Logical Channel Identity, LCID, value is valid for a predetermined time.

[0159] Embodiment E1-13: The network node of Embodiment E1-10, wherein the processor circuitry is further configured to preconfigure at least one Logical Channel Identity, LCID, value outside of the set as a dedicated Logical Channel Identity, LCID, value for association with an essential MAC CE format type, and wherein the essential MAC CE format type serves to signify one of: a common control channel (CCCH), padding, a Timing Advance Command, a SCell Activation command.

[0160] Embodiment E1-14: The network node of Embodiment E1-1, wherein the network node comprises a base station node that communicates over a radio interface with the wireless terminal.

[0161] Embodiment E1-15: The network node of Embodiment E1-1, wherein the network node comprises a core network node that communicates through a radio access network with the wireless terminal.

[0162] Embodiment E1-16: A method in a network node of a telecommunications system, the method comprising: establishing an association between a configuration parameter and a format type for a control element (MAC CE) of a medium access control (MAC) protocol, the configuration parameter being configured to indicate one of plural control element format types; transmitting a signal which includes the configuration parameter to a wireless terminal.

[0163] Embodiment E1-17: The method of Embodiment E1-16, wherein the configuration parameter comprises a Logical Channel Identity, LCID, value.

[0164] Embodiment E1-18: The method of Embodiment E1-16, wherein the signal comprises a radio resource control (RRC) signal.

[0165] Embodiment E1-19: The method of Embodiment E1-16, further comprising: establishing a plurality of associations, each association being an association of one of a set of potential configuration parameters and one of a set of potential corresponding MAC CE format types; selecting a selected one of the set of potential configuration parameters for inclusion as the configuration parameter to be transmitted to the wireless terminal.

[0166] Embodiment E1-20: The method of Embodiment E1-19, further comprising transmitting the selected one of the set of potential configuration parameters to the wireless terminal and thereby enable the wireless terminal to determine from the selected one of the set of potential configuration parameters which one of the plural MAC CE format types the wireless terminal should use to interpret a MAC CE in a MAC protocol data unit (MAC PDU) to be received by the wireless terminal.

[0167] Embodiment E1-21: The method of Embodiment E1-19, further comprising: establishing plural sets of associations, each set of associations comprising associations of plural potential configuration parameters and plural potential corresponding MAC CE format types for a set of one or more wireless terminals; and transmitting a signal which includes a configuration parameter which is selected for the set of or more wireless terminals.

[0168] Embodiment E1-22: The method of Embodiment E1-21, further comprising flexibly associating different ones of the plural sets of associations with different sets of one or more wireless terminals.

[0169] Embodiment E1-23: The method of Embodiment E1-22, wherein the set of potential configuration parameters comprises a set of Logical Channel Identity, LCID, values, and wherein the processor circuitry is configured to associate, for different ones one or more wireless terminals, different LCID values for the same MAC CE format type.

[0170] Embodiment E1-24: The method of Embodiment E1-16, wherein the set of potential configuration parameters comprises a set of Logical Channel Identity, LCID, values.

[0171] Embodiment E1-25: The method of Embodiment E1-24, further comprising: preconfiguring at least one Logical Channel Identity, LCID, value outside of the set as a default Logical Channel Identity, LCID, value; and causing the interface circuit to exclude the default Logical Channel Identity, LCID, value when transmitting a signal to the wireless terminal in a situation in which the network node intends for the wireless terminal to use a default MAC CE format type.

[0172] Embodiment E1-26: The method of Embodiment E1-25, wherein the default Logical Channel Identity, LCID, value is valid for a predetermined time.

[0173] Embodiment E1-27: The method of Embodiment E1-24, wherein the processor circuitry is further configured to preconfigure at least one Logical Channel Identity, LCID, value outside of the set as a dedicated Logical Channel Identity, LCID, value for association with an essential MAC CE format type, and wherein the essential MAC CE format type serves to signify one of: a common control channel (CCCH), padding, a Timing Advance Command, a SCell Activation command.

[0174] Embodiment E1-28: A wireless terminal which communicates with a network node through a radio access network, the wireless terminal comprising: receiver circuitry configured to: obtain a configuration parameter from a signal received from the network node over the radio access network; and receive a MAC protocol data unit (MAC PDU) from the radio access network; processor circuitry configured to determine from the configuration parameter which one of plural MAC CE format types the wireless terminal should use to interpret a control element (MAC CE) of a medium access control (MAC) protocol data unit (MAC PDU) received by the wireless terminal over the radio access network.

[0175] Embodiment E1-29: The wireless terminal of Embodiment E1-28, wherein processor circuitry is configured to interpret the MAC CE in view of an established association between the configuration parameter and the format type for a control element (MAC CE).

[0176] Embodiment E1-30: The wireless terminal of Embodiment E1-28, wherein the configuration parameter comprises a Logical Channel Identity, LCID, value.

[0177] Embodiment E1-31: The wireless terminal of Embodiment E1-28, wherein the signal comprises a radio resource control (RRC) signal.

[0178] Embodiment E1-32: The wireless terminal of Embodiment E1-28, wherein the configuration parameter is included in an information signal of radio resource control (RRC) signal.

[0179] Embodiment E1-33: The wireless terminal of Embodiment E1-28, wherein when processor circuitry is further configured, when the wireless terminal does not receive the configuration parameter, to use a default MAC CE format type to interpret the control element (MAC CE) of the medium access control (MAC) protocol data unit (MAC PDU) received by the wireless terminal over the radio access network.

[0180] Embodiment E1-34: The wireless terminal of Embodiment E1-33, wherein when processor circuitry is further configured, when the wireless terminal does not receive the configuration parameter, to use the default MAC CE format type to interpret the control element (MAC CE) during an eligible time for the default MAC CE format type.

[0181] Embodiment E1-35: A method in a wireless terminal which communicates with a network node through a radio access network, the method comprising: obtaining a configuration parameter from a signal received from the network node over the radio access network; and receiving a MAC protocol data unit (MAC PDU) from the radio access network; determining from the configuration parameter which one of plural MAC CE format types the wireless terminal should use to interpret a control element (MAC CE) of a medium access control (MAC) protocol data unit (MAC PDU) received by the wireless terminal over the radio access network.

[0182] Embodiment E1-36: The method of Embodiment E1-35, further comprising interpreting the MAC CE in view of an established association between the configuration parameter and the format type for a control element (MAC CE).

[0183] Embodiment E1-37: The method of Embodiment E1-35, wherein the configuration parameter comprises a Logical Channel Identity, LCID, value.

[0184] Embodiment E1-38: The method of Embodiment E1-35, wherein the signal comprises a radio resource control (RRC) signal.

[0185] Embodiment E1-39: The method of Embodiment E1-35, wherein the configuration parameter is included in an information signal of radio resource control (RRC) signal.

[0186] Embodiment E1-40: The method of Embodiment E1-35, further comprising, when the wireless terminal does not receive the configuration parameter, using a default MAC CE format type to interpret the control element (MAC CE) of the medium access control (MAC) protocol data unit (MAC PDU) received by the wireless terminal over the radio access network.

[0187] Embodiment E1-41: The method of Embodiment E1-40, further comprising, when the wireless terminal does not receive the configuration parameter, using the default MAC CE format type to interpret the control element (MAC CE) during an eligible time for the default MAC CE format type.

[0188] Embodiment E2-1: A network node of a telecommunications system, the network node comprising: processor circuitry configured to configure a format configuration of a medium access control (MAC) control element (MAC CE) and to include in a signal an indication of the format configuration; and an interface configured to transmit the signal to a wireless terminal.

[0189] Embodiment E2-2: The network node of Embodiment E2-1, wherein the format configuration comprises at least one of a location of a field / bit of the MAC CE, size of the field, and size of the MAC CE.

[0190] Embodiment E2-3: The network node of Embodiment E2-2, wherein when the MAC CE includes an optional field / bit, the signal comprises an optional field which specifies whether the MAC CE field / bit is present in the signal.

[0191] Embodiment E2-4: The network node of Embodiment E2-2, wherein the processor is circuitry is configured to configure locations of plural fields of a medium access control (MAC) control element (MAC CE) and to include, in the signal, indications of the locations of the plural fields of the medium access control (MAC) control element (MAC CE).

[0192] Embodiment E2-5: The network node of Embodiment E2-2, wherein the processor circuitry is configured to configure the signal whereby the location of the field of the medium access control (MAC) control element (MAC CE) is expressed with respect to a reference location of the medium access control (MAC) control element (MAC CE).

[0193] Embodiment E2-6: The network node of Embodiment E2-2, wherein the processor circuitry is further configured to configure a size of the medium access control (MAC) control element (MAC CE) and to include the size in the signal.

[0194] Embodiment E2-7: The network node of Embodiment E2-2, wherein the processor circuitry is further configured to exclude from the signal a location of a field of the medium access control (MAC) control element (MAC CE) for which a default location is specified and the default location is intended by the network to be used by the wireless terminal.

[0195] Embodiment E2-8: The network node of Embodiment E2-2, wherein the signal comprises a radio resource control (RRC) signal.

[0196] Embodiment E2-9: A method in a network node of a telecommunications system, the method comprising: configuring a format configuration of a medium access control (MAC) control element (MAC CE); including in a signal an indication of the format configuration of the medium access control (MAC) control element (MAC CE); and, transmitting the signal to a wireless terminal.

[0197] Embodiment E2-10: The method of Embodiment E2-9, wherein method comprises configuring at least one of the following: a location of a field / bit of the MAC CE, size of the field, and size of the MAC CE.

[0198] Embodiment E2-11: The method of Embodiment E2-10, wherein when the MAC CE includes an optional field / bit, the signal comprises an optional field which specifies whether the MAC CE field / bit is present in the signal.

[0199] Embodiment E2-12: The method of Embodiment E2-10, wherein method comprises configuring locations of plural fields of a medium access control (MAC) control element (MAC CE) and to include, in the signal, indications of the locations of the plural fields of the medium access control (MAC) control element (MAC CE).

[0200] Embodiment E2-13: The method of Embodiment E2-10, further comprising configuring the signal whereby the location of the field of the medium access control (MAC) control element (MAC CE) is expressed with respect to a reference location of the medium access control (MAC) control element (MAC CE).

[0201] Embodiment E2-14: The method of Embodiment E2-10, further comprising configuring a size of the medium access control (MAC) control element (MAC CE) to include the size in the signal.

[0202] Embodiment E2-15: The method of Embodiment E2-10, further comprising excluding from the signal a location of a field of the medium access control (MAC) control element (MAC CE) for which a default location is specified and the default location is intended by the network to be used by wireless terminal.

[0203] Embodiment E2-16: The method of Embodiment E2-10, wherein the signal comprises a radio resource control (RRC) signal.

[0204] Embodiment E2-17: A wireless terminal which communicates with a network node through a radio access network, the wireless terminal comprising: receiver circuitry configured to receive a signal from a network node; processor circuitry configured to determine from the signal an indication of a format configuration of a medium access control (MAC) control element (MAC CE).

[0205] Embodiment E2-18: The wireless terminal of Embodiment E2-17, wherein the format configuration includes at least one of the following: a location of a field / bit, size of the field, and size of the MAC CE processor circuitry is configured to determine from the signal indications of locations of plural fields of the medium access control (MAC) control element (MAC CE).

[0206] Embodiment E2-19: The wireless terminal of Embodiment E2-18, wherein when the MAC CE includes an optional field / bit, the signal comprises an optional field which specifies whether the MAC CE field / bit is present in the signal.

[0207] Embodiment E2-20: The wireless terminal of Embodiment E2-17, wherein processor circuitry is configured to determine from the signal indications of locations of plural fields of the medium access control (MAC) control element (MAC CE).

[0208] Embodiment E2-21: The wireless terminal of Embodiment E2-17, wherein processor circuitry is configured to determine the location of the field of the medium access control (MAC) control element (MAC CE) with respect to a reference location of the medium access control (MAC) control element (MAC CE).

[0209] Embodiment E2-22: The wireless terminal of Embodiment E2-17, wherein the processor circuitry is further configured to determine from the signal a size of the medium access control (MAC) control element (MAC CE).

[0210] Embodiment E2-23: The wireless terminal of Embodiment E2-17, wherein the processor circuitry is further configured to use a default location for a field of the medium access control (MAC) control element (MAC CE) for which field location is not configured in the signal.

[0211] Embodiment E2-24: The wireless terminal of Embodiment E2-17, wherein the processor circuitry is further configured to use a default size for the medium access control (MAC) control element (MAC CE) when a size for the medium access control (MAC) control element (MAC CE) is not configured in the signal.

[0212] Embodiment E2-25: The wireless terminal of Embodiment E2-17, wherein the processor circuitry is further configured to exclude from the medium access control (MAC) control element (MAC CE) a field for which the wireless terminal does not have a default location and for which a field location is not configured in the signal.

[0213] Embodiment E2-26: The wireless terminal of Embodiment E2-17, wherein the processor circuitry is further configured to use the location of the field to decode at least part of the medium access control (MAC) control element (MAC CE).

[0214] Embodiment E2-27: The wireless terminal of Embodiment E2-17, wherein the signal comprises a radio resource control (RRC) signal.

[0215] Embodiment E2-28: A method in a wireless terminal which communicates with a network node through a radio access network, the method comprising: receiving a signal from a network node; determining from the signal an indication of a format configuration of a medium access control (MAC) control element (MAC CE).

[0216] Embodiment E2-29: The method of Embodiment E2-28, further comprising determining from the signal indications of locations of plural fields of the medium access control (MAC) control element (MAC CE).

[0217] Embodiment E2-30: The method of Embodiment E2-29, wherein when the MAC CE includes an optional field / bit, the signal comprises an optional field which specifies whether the MAC CE field / bit is present in the signal.

[0218] Embodiment E2-31: The method of Embodiment E2-28, further comprising determining the location of the field of the medium access control (MAC) control element (MAC CE) with respect to a reference location of the medium access control (MAC) control element (MAC CE).

[0219] Embodiment E2-32: The method of Embodiment E2-28, further comprising determining from the signal a size of the medium access control (MAC) control element (MAC CE).

[0220] Embodiment E2-33The method of Embodiment E2-28, further comprising using a default location for a field of the medium access control (MAC) control element (MAC CE) for which field location is not configured in the signal.

[0221] Embodiment E2-34: The method of Embodiment E2-28, further comprising excluding from the medium access control (MAC) control element (MAC CE) a field for which the wireless terminal does not have a default location and for which a field location is not configured in the signal.

[0222] Embodiment E2-35: The method of Embodiment E2-28, further comprising using a default size for the medium access control (MAC) control element (MAC CE) when a size for the medium access control (MAC) control element (MAC CE) is not configured in the signal.

[0223] Embodiment E2-36: The method of Embodiment E2-28, further comprising using the location of the field to decode at least part of the medium access control (MAC) control element (MAC CE).

[0224] Embodiment E2-37: The method of Embodiment E2-28, wherein the signal comprises a radio resource control (RRC) signal.

[0225] Embodiment E3-1: A network node of a telecommunications system, the network node comprising: processor circuitry configured to configure a format configuration of a medium access control (MAC) subheader and to include in a signal an indication of the format configuration; and an interface configured to transmit the signal to a wireless terminal.

[0226] Embodiment E3-2: The network node of Embodiment E3-1, wherein the format configuration comprises at least one of a location of a field / bit of the MAC CE, size of the field, and size of the MAC subheader.

[0227] Embodiment E3-3: The network node of Embodiment E3-2, wherein when the MAC subheader includes an optional field / bit, the signal comprises an optional field which specifies whether the MAC subheader field / bit is present in the signal.

[0228] Embodiment E3-4: The network node of Embodiment E3-2, wherein the processor is circuitry is configured to configure locations of plural fields of the medium access control (MAC) subheader and to include, in the signal, indications of the locations of the plural fields of the medium access control (MAC) subheader.

[0229] Embodiment E3-5: The network node of Embodiment E3-2, wherein the processor circuitry is configured to configure the signal whereby the location of the field of the medium access control (MAC) subheader is expressed with respect to a reference location of the medium access control (MAC) subheader.

[0230] Embodiment E3-6: The network node of Embodiment E3-2, wherein the processor circuitry is further configured to configure a size of the medium access control (MAC) subheader and to include the size in the signal.

[0231] Embodiment E3-7: The network node of Embodiment E3-2, wherein the processor circuitry is further configured to exclude from the signal a location of a field of the medium access control (MAC) subheader for which a default location is specified and the default location is intended by the network to be used by the wireless terminal.

[0232] Embodiment E3-8: The network node of Embodiment E3-1, wherein the signal comprises a radio resource control (RRC) signal.

[0233] Embodiment E3-9: A method in a network node of a telecommunications system, the method comprising: configuring a format configuration of a medium access control (MAC) subheader; including in a signal an indication of the format configuration of the medium access control (MAC) subheader; and, transmitting the signal to a wireless terminal.

[0234] Embodiment E3-10: The method of Embodiment E3-9, wherein method comprises configuring at least one of the following: a location of a field / bit of the MAC CE, size of the field, and size of the MAC subheader.

[0235] Embodiment E3-11: The method of Embodiment E3-10, wherein when the MAC subheader includes an optional field / bit, the signal comprises an optional field which specifies whether the MAC subheader field / bit is present in the signal.

[0236] Embodiment E3-12: The method of Embodiment E3-10, wherein method comprises configuring locations of plural fields of a medium access control (MAC) subheader and to include, in the signal, indications of the locations of the plural fields of the medium access control (MAC) subheader.

[0237] Embodiment E3-13: The method of Embodiment E3-10, further comprising configuring the signal whereby the location of the field of the medium access control (MAC) subheader is expressed with respect to a reference location of the medium access control (MAC) control element (MAC CE).

[0238] Embodiment E3-14: The method of Embodiment E3-10, further comprising configuring a size of the medium access control (MAC) subheader to include the size in the signal.

[0239] Embodiment E3-15: The method of Embodiment E3-10, further comprising excluding from the signal a location of a field of the medium access control (MAC) subheader for which a default location is specified and the default location is intended by the network to be used by the wireless terminal.

[0240] Embodiment E3-16: The method of Embodiment E3-10, wherein the signal comprises a radio resource control (RRC) signal.

[0241] Embodiment E3-17: A wireless terminal which communicates with a network node through a radio access network, the wireless terminal comprising: receiver circuitry configured to receive a signal from a network node; processor circuitry configured to determine from the signal an indication of a format configuration of a medium access control (MAC) subheader.

[0242] Embodiment E3-18: The wireless terminal of Embodiment E3-17, wherein the format configuration includes at least one of the following: a location of a field / bit, size of the field, and size of the MAC subheader, and wherein the processor circuitry is configured to determine from the signal indications of locations of plural fields of the medium access control (MAC) subheader.

[0243] Embodiment E3-19: The method of Embodiment E3-18, wherein when the MAC subheader includes an optional field / bit, the signal comprises an optional field which specifies whether the MAC subheader field / bit is present in the signal.

[0244] Embodiment E3-20: The wireless terminal of Embodiment E3-17, wherein processor circuitry is configured to determine from the signal indications of locations of plural fields of the medium access control (MAC) subheader.

[0245] Embodiment E3-21: The wireless terminal of Embodiment E3-17, wherein processor circuitry is configured to determine the location of the field of the medium access control (MAC) subheader with respect to a reference location of the medium access control (MAC) control element (MAC CE).

[0246] Embodiment E3-22: The wireless terminal of Embodiment E3-17, wherein the processor circuitry is further configured to determine from the signal a size of the medium access control (MAC) subheader.

[0247] Embodiment E3-23: The wireless terminal of Embodiment E3-17, wherein the processor circuitry is further configured to use a default location for a field of the medium access control (MAC) subheader for which field location is not configured in the signal.

[0248] Embodiment E3-24: The wireless terminal of Embodiment E3-17, wherein the processor circuitry is further configured to use a default size for the medium access control (MAC) subheader when a size for the medium access control (MAC) control element (MAC CE) is not configured in the signal.

[0249] Embodiment E3-25: The wireless terminal of Embodiment E3-17, wherein the processor circuitry is further configured to exclude from the medium access control (MAC) subheader a field for which the wireless terminal does not have a default location and for which a field location is not configured in the signal.

[0250] Embodiment E3-26: The wireless terminal of Embodiment E3-17, wherein the processor circuitry is further configured to use the location of the field to decode at least part of the medium access control (MAC) subheader.

[0251] Embodiment E3-27: The wireless terminal of Embodiment E3-17, wherein the signal comprises a radio resource control (RRC) signal.

[0252] Embodiment E3-28: A method in a wireless terminal which communicates with a network node through a radio access network, the method comprising: receiving a signal from a network node; determining from the signal an indication of a format configuration of a medium access control (MAC) subheader.

[0253] Embodiment E3-29: The method of Embodiment E3-28, further comprising determining from the signal indications of locations of plural fields of the medium access control (MAC) subheader.

[0254] Embodiment E3-28: The method of Embodiment E3-30, wherein when the MAC subheader includes an optional field / bit, the signal comprises an optional field which specifies whether the MAC subheader field / bit is present in the signal.

[0255] Embodiment E3-31: The method of Embodiment E3-28, further comprising determining from the signal indications of locations of plural fields of the medium access control (MAC) subheader.

[0256] Embodiment E3-32: The method of Embodiment E3-28, further comprising determining the location of the field of the medium access control (MAC) subheader with respect to a reference location of the medium access control (MAC) subheader.

[0257] Embodiment E3-33: The method of Embodiment E3-28, further comprising determining from the signal a size of the medium access control (MAC) subheader.

[0258] Embodiment E3-34: The method of Embodiment E3-28, further comprising using a default location for a field of the medium access control (MAC) subheader for which field location is not configured in the signal.

[0259] Embodiment E3-35: The method of Embodiment E3-28, further comprising excluding from the medium access control (MAC) subheader a field for which the wireless terminal does not have a default location and for which a field location is not configured in the signal.

[0260] Embodiment E3-36: The method of Embodiment E3-28, further comprising using a default size for the medium access control (MAC) subheader when a size for the medium access control (MAC) control element (MAC CE) is not configured in the signal.

[0261] Embodiment E3-37: The method of Embodiment E3-28, further comprising using the location of the field to decode at least part of the medium access control (MAC) subheader.

[0262] Although the description above contains many specificities, these should not be construed as limiting the scope of the technology disclosed herein but as merely providing illustrations of some of the presently preferred embodiments of the technology disclosed herein. Thus the scope of the technology disclosed herein should be determined by the appended claims and their legal equivalents. Therefore, it will be appreciated that the scope of the technology disclosed herein fully encompasses other embodiments which may become obvious to those skilled in the art, and that the scope of the technology disclosed herein is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more." The above-described embodiments could be combined with one another. All structural, chemical, and functional equivalents to the elements of the above-described preferred embodiment that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. Moreover, it is not necessary for a device or method to address each and every problem sought to be solved by the technology disclosed herein, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims.

[0263] <Cross Reference> This patent application claims priority on US Patent Application No. 63 / 677,580 filed on July 31, 2024, the entire contents of which are hereby incorporated by reference.

Claims

1. A network node of a telecommunications system, the network node comprising: processor circuitry configured to establish an association between a configuration parameter and a format type for a control element (MAC CE) of a medium access control (MAC) protocol, the configuration parameter being configured to indicate one of plural control element format types; an interface configured to transmit a signal which includes the configuration parameter to a wireless terminal.

2. The network node of claim 1, wherein the configuration parameter comprises a Logical Channel Identity, LCID, value.

3. The network node of claim 1, wherein the signal comprises a radio resource control (RRC) signal.

4. The network node of claim 3, wherein the configuration parameter is included in an information signal of radio resource control (RRC) signal.

5. The network node of claim 1, wherein the processor circuitry is configured to: establish a plurality of associations, each association being an association of one of a set of configuration parameters and one of a set of corresponding MAC CE format types; select a selected one of the set of configuration parameters for inclusion as the configuration parameter to be transmitted to the wireless terminal.

6. The network node of claim 5, wherein the interface circuitry is configured to transmit the selected one of the set of configuration parameters to the wireless terminal and thereby enable the wireless terminal to determine from the selected one of the set of configuration parameters which one of the plural MAC CE format types the wireless terminal should use to interpret a MAC CE in a MAC protocol data unit (MAC PDU) to be received by the wireless terminal.

7. The network node of claim 1, wherein the network node comprises a base station node that communicates over a radio interface with the wireless terminal.

8. A wireless terminal which communicates with a network node through a radio access network, the wireless terminal comprising: receiver circuitry configured to: obtain a configuration parameter from a signal received from the network node over the radio access network; and receive a MAC protocol data unit (MAC PDU) from the radio access network; processor circuitry configured to determine from the configuration parameter which one of plural MAC CE format types the wireless terminal should use to interpret a control element (MAC CE) of a medium access control (MAC) protocol data unit (MAC PDU) received by the wireless terminal over the radio access network.

9. The wireless terminal of claim 8, wherein processor circuitry is configured to interpret the MAC CE in view of an established association between the configuration parameter and the format type for a control element (MAC CE).

10. The wireless terminal of claim 8, wherein the configuration parameter comprises a Logical Channel Identity, LCID, value.

11. The wireless terminal of claim 8, wherein the signal comprises a radio resource control (RRC) signal.

12. The wireless terminal of claim 8, wherein the configuration parameter is included in an information signal of radio resource control (RRC) signal.

13. The wireless terminal of claim 8, wherein when processor circuitry is further configured, when the wireless terminal does not receive the configuration parameter, to use a default MAC CE format type to interpret the control element (MAC CE) of the medium access control (MAC) protocol data unit (MAC PDU) received by the wireless terminal over the radio access network.

14. The wireless terminal of claim 13, wherein when processor circuitry is further configured, when the wireless terminal does not receive the configuration parameter, to use the default MAC CE format type to interpret the control element (MAC CE) during an eligible time for the default MAC CE format type.

15. A method in a wireless terminal which communicates with a network node through a radio access network, the method comprising: obtaining a configuration parameter from a signal received from the network node over the radio access network; and receiving a MAC protocol data unit (MAC PDU) from the radio access network; determining from the configuration parameter which one of plural MAC CE format types the wireless terminal should use to interpret a control element (MAC CE) of a medium access control (MAC) protocol data unit (MAC PDU) received by the wireless terminal over the radio access network.

Images