[go: up one dir, main page]

WO2017162273A1 - Amélioration de l'efficacité de communication indiquant la longueur de deux en-têtes dans la pdu - Google Patents

Amélioration de l'efficacité de communication indiquant la longueur de deux en-têtes dans la pdu Download PDF

Info

Publication number
WO2017162273A1
WO2017162273A1 PCT/EP2016/056250 EP2016056250W WO2017162273A1 WO 2017162273 A1 WO2017162273 A1 WO 2017162273A1 EP 2016056250 W EP2016056250 W EP 2016056250W WO 2017162273 A1 WO2017162273 A1 WO 2017162273A1
Authority
WO
WIPO (PCT)
Prior art keywords
header
headers
length
sub
data unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/EP2016/056250
Other languages
English (en)
Inventor
Krystian Pawlak
Amit Kumar Sharma
Samuli Heikki TURTINEN
Timo Koskela
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Solutions and Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions and Networks Oy filed Critical Nokia Solutions and Networks Oy
Priority to PCT/EP2016/056250 priority Critical patent/WO2017162273A1/fr
Publication of WO2017162273A1 publication Critical patent/WO2017162273A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/03—Protocol definition or specification 

Definitions

  • the invention relates to communications.
  • data may be transmitted between a transmitter and a receiver. Processing the data may cause delay to the transmission process.0 Therefore, it may be beneficial to provide solutions which enable reducing latency in the transmission process.
  • Figure 1 illustrates an example a cellular communication system to which embodiments of the invention may be applied
  • FIGS. 2 and 3 illustrate flow diagrams according to some embodiments
  • FIGS. 4A to 4F illustrate some embodiments
  • FIGS. 6A to 6B illustrate some embodiments
  • FIGS. 8 and 9 illustrate block diagrams of apparatuses according to some embodiments. 0 DETAILED DESCRIPTION OF SOME EMBODIMENTS
  • Embodiments described may be implemented in a radio system, such as in at least one of the following: Worldwide Interoperability for Micro-wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), and/or LTE-Advanced.
  • WiMAX Worldwide Interoperability for Micro-wave Access
  • GSM Global System for Mobile communications
  • GERAN GSM EDGE radio access Network
  • GRPS General Packet Radio Service
  • UMTS Universal Mobile Telecommunication System
  • W-CDMA basic wideband-code division multiple access
  • HSPA high-speed packet access
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • 5G is likely to use multiple input - multiple output (MIMO) techniques (including MIMO antennas), many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input - multiple output
  • 5G will likely be comprised of more than one radio access technology (RAT), each optimized for certain use cases and/or spectrum.
  • RAT radio access technology
  • 5G mobile communications will have a wider range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications, including vehicular safety, different sensors and real-time control.
  • 5G is expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also being integradable with existing legacy radio access technologies, such as the LTE. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE.
  • 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave).
  • inter-RAT operability such as LTE-5G
  • inter-RI operability inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave.
  • NFV network functions virtualization
  • a virtualized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware.
  • Cloud computing or cloud data storage may also be utilized.
  • radio communications this may mean node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be non-existent.
  • Some other technology advancements probably to be used are Software-Defined Networking (SDN), Big Data, and all-IP, which may change the way networks are being constructed and managed.
  • SDN Software-Defined Networking
  • Big Data Big Data
  • all-IP all-IP
  • FIG. 1 illustrates an example of a cellular communication system (also referred to as a radio communication system) to which some embodiments may be applied.
  • Cellular radio communication networks also referred to as radio communication networks
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • 3GPP 3rd Generation Partnership Project
  • the cell 100 may be, e.g., a macro cell, a micro cell, femto, or a pico- cell, for example.
  • the network element 102 may be an evolved Node B (eNB) as in the LTE and LTE-A, a radio network controller (RNC) as in the UMTS, a base station controller (BSC) as in the GSM/GERAN, or any other apparatus capable of controlling radio communication and managing radio resources within the cell 100.
  • eNB evolved Node B
  • RNC radio network controller
  • BSC base station controller
  • the implementation may be similar to LTE-A, as described above.
  • the network element 102 may be a base station or an access node.
  • the cellular communication system may be composed of a radio access network of network nodes similar to the network element 102, each controlling a respective cell or cells.
  • the network element 102 may be further connected via a core network interface to a core network 190 of the cellular communication system.
  • the core network 190 may be called Evolved Packet Core (EPC) according to the LTE terminology.
  • the core network 190 may comprise a mobility management entity (MME) and a data routing network element.
  • MME mobility management entity
  • the MME may track mobility of terminal devices 1 10, 120, and may carry out establishment of bearer services between the terminal devices 1 10, 120 and the core network 190.
  • the data routing network element may be called a System Architecture Evolution Gateway (SAE-GW). It may be configured to carry out packet routing to/from the terminal devices 1 10, 120 from/to other parts of the cellular communication system and to other systems or networks, e.g. the Internet.
  • SAE-GW System Architecture Evolution Gateway
  • the terminal devices 1 10, 120 may comprise, for example, cell phones, smart phones, tablets, and/or Machine Type Communication (MTC) devices. There may be a plurality of terminal devices 1 10, 120 within the cell 100, and thus the network element 102 may provide service for more than two terminal devices. As shown in Figure 1 , the terminal devices may be in communication (i.e. transfer data and/or control information with the network) with the network element 102 using communication links 1 12, 122 respectively. These communication links 1 12, 122 may be referred to as conventional communication links in the cellular communication system. It is obvious for a skilled person that the conventional communication links may be used to transmit, for example, voice and packet data.
  • MTC Machine Type Communication
  • the cellular communication system may support Device-to- Device (D2D) communication.
  • D2D Device-to- Device
  • terminal devices such as the terminal devices 1 10, 120
  • D2D communication link 1 14 between the terminal devices 1 10, 120 may enable data and/or configuration information transfer between the devices. Such may be beneficial, for example, in offloading the network.
  • a first terminal device 1 10 has data to transmit to a second terminal device 120. If a D2D communication link is established or may be established between the two devices 1 10, 120, it may be beneficial to transmit that data directly using the D2D link. This may decrease the load of the network as the data does not need to be transmitted via the network element 102, for example.
  • the cellular communication system may comprise a number of network elements which are similar to the network element 102, for example.
  • Different network elements for example, the network element 102 and some other similar network element (e.g. a base station) may be connected to each other wired or wirelessly (e.g. X2-interface in LTE).
  • Data and information may be transmitted between two or more network elements (e.g. base stations), between a network element and a terminal device, and also between terminal devices.
  • CA Carrier Aggregation
  • dual connectivity techniques may be utilized in the cellular communication system.
  • the cellular communication and particularly the cellular communication systems may comprise different layers to enable data transfer between entities of said system.
  • the system may utilize a Medium Access Control (MAC) layer that may map logical channels to transport channels.
  • MAC Medium Access Control
  • CCCH Common Control Channel
  • DCCH Dedicated Control Channel
  • DTCH Dedicated Traffic Channel
  • UL-SCH Uplink Shared Channel
  • a terminal device may map the UL-SCH to Physical Uplink Shared Channel (PUSCH) in order to enable the physical transfer of data in the uplink direction.
  • PUSCH Physical Uplink Shared Channel
  • Similar logic applies to downlink direction, but there may also be different logical channels to be mapped.
  • the logical channel(s) are for D2D or base station to base station (e.g. via X2 interface) communication.
  • the proposed solution may be used to, for example downlink, uplink, D2D and/or base station to base station communication.
  • the MAC layer may receive data from a Radio Link Control (RLC) layer (i.e. the logical channels are comprised in the RLC layer). Received data may be in the form of MAC Service Data Units (SDUs). That is, SDUs may be used to carry data from one layer to another, for example, from the RLC to MAC layer.
  • the processing entity e.g. network element 102 or terminal device 110
  • PDU MAC Physical Data Unit
  • PDU MAC Physical Data Unit
  • One aspect in future communication systems, particularly in cellular systems, is to reduce latency in order to increase communication efficiency (e.g. increase data rates).
  • 5G system may be one example of such system.
  • processing power of a single processor may possibly increase in the future thus enabling faster processing of data, but there may also be some limitations there. That is, processing, for example, elements of a PDU may be beneficial to be performed such that the processing of two or more elements may happen concurrently instead of processing an element after another in a consecutive manner.
  • the processing unit may be beneficial to be configured to perform parallel processing of elements of a PDU.
  • a solution for PDU structure may support parallel processing of different PDU elements, such as CEs and SDUs.
  • the solution may enable decreasing system latency in a cellular communication system, for example.
  • the solution at least in some embodiments, may decrease variance of latency, thus making the network latency more predictable.
  • MAC layer may be essentially for the same purpose (e.g. for mapping the logical channels to transport channel(s)) in the future communication system, but not necessarily named as MAC layer.
  • the described solution is particularly suitable for a 5G system.
  • a network element of a cellular communication system may structure a protocol data unit to comprise a header part at least for a first header and for a second header, wherein the protocol data unit comprises a first information element indicating a length of the first header and a second information element indicating a length of the second header.
  • the network element may cause a transmission of a signal carrying the protocol data unit to another network element of the cellular communication system.
  • a network element of a cellular communication system may obtain a protocol data unit comprising a header part at least for a first header and for a second header, wherein the protocol data unit comprises a first information element indicating a length of the first header and a second information element indicating a length of the second header.
  • the network element may determine, based on the first and second information elements, the lengths of the first and second headers.
  • the network element may perform an action based on the determined lengths of the first and second headers.
  • the described solution may be applicable to uplink and/or downlink transmissions. That is, the structured and/or obtained (e.g.
  • PDUs may be used to carry downlink and/or uplink information.
  • the network element performing the steps of Figure 2 may be the network element 102 or the terminal device 1 10, for example.
  • the network element performing the steps of Figure 2 may be the network element 102 or the terminal device 1 10, for example.
  • a skilled person will understand how the PDU transmission may be performed in a cellular communication system between, for example, eNB and User Equipment (UE).
  • the network element 102 may transmit downlink data to the terminal device 1 10 utilizing PDU(s).
  • the terminal device 1 10 may transmit uplink data to the network element 102 utilizing PDU(s).
  • the described structuring of the PDU brings additional benefits for the system as briefly described above.
  • a PDU 400 may comprise a first information element 412 and a second information element 422 indicating the lengths of the first header 410 and the second header 420.
  • first information element 412 may indicate the length 41 1 of the first header 410
  • the second information element 422 may indicate the length 421 of the second header 420.
  • the first and/or second information elements may also be referred to, for example, as first and second fields or first and second special fields.
  • the PDU 400 may comprise a part for the first and second headers 410, 420. Said part may be continuous or it may be comprised of two or more parts that are separated by some other part of the PDU. For example, there may be CEs between the two headers 410, 420. It needs to be noted that in some cases length of the first and/or the second header 410, 420 is zero. This may be indicated with the information elements 412, 422 accordingly. Thus, the PDU 400 may not necessarily comprise data 440 to which the headers 410, 420 are associated to. On the other hand, the PDU 400 may comprise only one of the headers 410, 420.
  • the first information element 412 may indicate zero.
  • the receiver of the PDU 400 may know that there are no CEs or the first header 410 in the PDU 400. The receiver may then proceed on processing the SDUs accordingly based at least partly on the length of the second header 420.
  • the PDU 400 may comprise the data part 440.
  • the data part 440 comprise one or more SDUs and/or one or more CEs.
  • the data part comprises only SDUs or similar data units.
  • the second header 420 is for the data part 440.
  • the second header is for a subpart of the data part 440 and the first header is for another subpart of the data part 440.
  • the PDU 400 may comprise one or more CEs and/or one or more SDUs.
  • the CE(s) and/or SDU(s) may be situated, for example, in the data part 440 and/or in some cases in the first header 410 and/or in the second header 420.
  • the first header 410 comprises all CEs of the PDU 400, whereas all the SDUs of the PDU are comprised in the data part 440.
  • the grouping may also be different as discussed below in more detail.
  • the header part for the first and second headers 410, 420 comprises the first and second information elements 412, 422.
  • the header part of the PDU 400 may comprise the information elements 412, 422 and also the headers 410, 420.
  • the header part may comprise, in some embodiments, a PDU control information 402.
  • Purpose of the PDU control information 402 may be to indicate how the receiver should interpret data of the PDU 400 following the PDU control information 402 (e.g. headers, CEs, and/or SDUs).
  • the PDU 400 may comprise one or more control elements 416, 417 and/or one or more service data units 442.
  • the PDU 400 may comprise the SDUs 442 and the CEs 416, 417, wherein the first header 410 is associated with the CEs 416, and wherein the second header 420 is associated with the SDUs 442.
  • the first header 410 comprises one or more sub-headers.
  • the first header 410 comprises sub-headers 414, 415, wherein a first sub-header 414 is for a first CE 416, and wherein a second sub-header 415 is for a second CE 417.
  • the second header 420 comprises one or more sub-headers.
  • the second header 420 comprises sub-headers 424 (i.e. three sub-headers), wherein each sub-header is for a particular SDU 442 (i.e. one sub-header for one SDU).
  • the first and second headers 410, 420 each comprise one or more sub-headers 414, 415, 424, each sub-header 414, 415, 424 being associated with CE 416, 417 or a SDU 442 of the PDU 400. This may mean that there is one sub-header for each CE or SDU.
  • Sub-header may carry control information of a CE or a SDU.
  • a sub-header for a CE may carry or comprise Logical Channel Identity (LCID) value indicating specific MAC Control Element. .
  • LCID Logical Channel Identity
  • This information i.e. LCID or similar identifier
  • the receiver or a scheduler
  • the PDUs, SDUs and/or CEs described may be MAC PDUs, SDUs and/or CEs, for example.
  • a sub-header for a SDU may carry or comprise an identifier (e.g. LCID) indicating a logical channel to which the SDU is related to.
  • a sub-header for a SDU carry or comprise length indicator indicating a length of the SDU.
  • the length of CE may be predetermined (e.g. defined by radio communication specifications).
  • a sub-header such as the sub-headers 414, 415, 424, does not comprise extension field (E). That is, there may not be a need for the E field because the length of the header, in which the sub-header is comprised, may be known. Also, the length of a sub-header may be known, so the receiver may acquire knowledge how many sub-headers there are in a header.
  • the second information element 422 may indicate a length of the second header 420.
  • the length of a sub-header 424 may be constant or predetermined by system parameters. Thus, by dividing the overall length of the header 420 with the length of the sub-header 424, the receiver may determine that there are 3 sub-headers 424 in the header 420.
  • the PDU 400 may be shown to comprise the first header 410, second header 420 and the SDUs 440. Further, the PDU 400 may comprise the first and second information elements 412, 422 indicating the length of the headers 410, 420. Let us further assume that the PDU 400 has been transmitted to a receiver (e.g. to a terminal device) using a transport block (TB) onto which the PDU is mapped. The receiver or some other network element that has obtained the PDU may start to process the PDU 400. The processing may comprise reading the information elements 412, 422.
  • the processing unit may determine where the second header 420 starts, and further where the SDUs 440 start. For example, the processing unit may determine the first header 410 and its location in the PDU 400, and further separate the first header 410 from the PDU 400. The first header 410 may then, in this example, be processed in consecutive way by processing the elements of the first header 410 (e.g. sub-headers and CEs) one after another. The processing of the first header 410 may be performed by said processing unit or by some other processing unit (e.g. a scheduler).
  • the processing unit may become aware about the location of the first header
  • the length of the information elements 412, 422 may be predetermined, for example, 8 bits (i.e. 1 byte) each.
  • the processing of the PDU 400 may proceed to the second header 420.
  • Processing of the first and second headers 410, 420 may be performed at least partially in parallel. That is, knowing the lengths 414, 424, the first and second headers 410, 420 may be processed simultaneously or at least substantially simultaneously.
  • One aspect having an effect to this may be the fact that, for example, the SDUs 442 within the PDU 400 may be actually received at different times. On the other hand the SDUs 442 may be received simultaneously. It is clear that processing of an SDU may not start before receiving the SDU.
  • TB comprising the SDUs 442 (e.g.
  • the receiver may acquire the PDU 400 and the payload of the PDU 400. Therefore, the SDUs 442 may be processed simultaneously, as the TB may already have been fully received before the mapping back to the MAC layer may happen.
  • the processing of the second header 420 may comprise processing the subheaders 424A-424C in parallel meaning that the sub-headers may be processed simultaneously.
  • the length of a sub-header within the second header 420 may be fixed, and thus the processing unit may know where the sub-headers are located within the second header 420.
  • the sub-header 424A may be associated with the SDU 442A
  • the sub-header 424B may be associated with the SDU 442B
  • the sub-header 424C may be associated with the SDU 442C.
  • the SDUs 442A-B may be processed in parallel.
  • the receiver may start to process the SDUs 442 of the PDU 400 after knowing the length of the second header 420 (e.g. by reading at least the second information element 422).
  • the SDUs 442 may further be transmitted or sent to a RLC layer for further processing.
  • the first header 410 is a control element header for one or more control elements and the second header 420 is a service data unit header for one or more service data units. That is, the first header 410 may comprise sub-headers which are for CEs and the second header 420 may comprise sub- headers which are for SDUs, for example.
  • the first header 410 (or the control element header) comprises the one or more CEs 416, 417. This may be beneficial, for example, when the PDU is processed as described with reference to Figure 6A. However, in some embodiments the CEs may also be located in some other part of the PDU 400. That is, not in the first header 410.
  • the PDU comprises a third information element 432.
  • the third information element 432 may indicate a length of a part 430 of the PDU 400 for one or more CEs 416, 417. Additionally or alternatively, the third information element 432 may indicate length of a part for one or more SDUs 442. However, in the example of Figure 4C, the third information element 432 may indicate the length of the part 430 (i.e. comprising the CEs 416, 417). In the case that the part 430 comprises the one or more CEs 416, 417, said part may be associated with the first header 410, for example. In some other examples, said part may be associated with the second header.
  • the receiver may acquire knowledge of lengths of the first header 410, the CE part 430, and the second header 420. Length of the SDU part 440 may be determined from the sub-headers of the second header 420.
  • Figure 6B illustrates processing of the PDU 400 that has a structure described in relation to Figure 4C.
  • Processing, by the receiver (e.g. a processing unit), of the second header 420 and the associated SDUs 442 may be similar to that of what was described in relation to Figure 6A. That is, the SDUs 442A-B may be processed in parallel, thus possibly reducing latency.
  • the additional third information element 432 may bring further benefits.
  • the receiver may now become aware of the length of the part comprising the CEs 416, 417 (the CEs are not now comprised in the first header 410).
  • the receiver may process the CEs in parallel. This may be similar as the parallel processing of the SDUs 442.
  • the first header 410 and the CEs 416, 417 may be processed simultaneously (e.g. in parallel) with the second header 420 and the SDUs 442.
  • the receiver may process the first, second, and third information elements 412, 422, 432 after obtaining the PDU 400. After processing the first and third information elements 412, 432, the receiver may cause an initiation of processing of the part A shown in Figure 6B. After processing the second information element 422, the receiver may cause an initiation of processing of the part B.
  • the part A and B may be processed in parallel by the receiver or by some other processing unit. For example, the receiver may process the part B, whereas the part A may be processed by a scheduler. Thus, the CEs 416, 417 and the SDUs 442 may be processed in parallel. Hence, latency may be reduced.
  • the third information element 432 may be, for example, 8 bits long (i.e. 1 byte). That is, the length may be indicated with 8 bits.
  • the first and second information elements 412, 422 may indicate lengths with 8 bits, for example.
  • the length of the header parts 410, 420 and/or some other part of the PDU 400 is indicated in bytes resolution.
  • the headers 410, 420, CE part 430, and the SDU part 440 may be arranged into the PDU in an alternative way compared with the examples of Figures 4B and 4C, for example.
  • the PDU 400 illustrated in Figure 4D according to an embodiment, comprises the first, second and third information elements 412, 422, 432.
  • the PDU 400 may comprise the PDU control information 402.
  • the first and second headers 410, 420 may be arranged, for example by the network element 102 or a terminal device generating or structuring the PDU 400, such that the first and second headers 410, 420 are situated in the PDU 400 after the first, second and third information elements 412, 422, 432.
  • the first header 410 does not comprise the CEs 416, 417 which are comprised in the PDU part 430 (i.e. comprising the CEs 416, 417).
  • the las part of the PDU 440 may comprise the SDUs 442.
  • the PDU 400 is generated such that the order of part 430 and 440 is reversed. It may also be that, in some embodiments, the PDU 400 is generated such that the order of the first and second headers 410, 420 is reversed. This may ably to, for example, embodiments of Figure 4A, 4B, 4C and 4D.
  • the first, second and third information elements 412, 422, 432 may be arranged in the PDU 400 in a different order, e.g. the second information element 422 may be arranged to be situated successive to the PDU 400 control information 402, wherein the first and third information elements 412, 432 may then follow.
  • the order of different elements in the PDU 400 may vary depending on the implementation. Benefits of the solution may be attained as long as there are the first and second information elements 412, 422 indicating the length of the first header 410 and the second header 420. It needs to be noted at this point that in some cases the length of the first header 410 and/or the second header 420 may be zero. The first and/or second information elements 412, 422 may so indicate.
  • the one or more sub-headers 414, 424 may be arranged, for example by the network element 102, into the first and second headers 410, 420 according to the length of the sub-headers 414, 415, 424 such that the first header 410 comprises one or more sub-headers 414, 415 having a first length (i.e. indicated with L) and the second header 420 comprises one or more sub-headers 424 having a second length (i.e. indicated with 2L).
  • L may depict one byte whereas 2L may depict two bytes. That is, L may mean that the field indicating SDU length in a sub-header is one byte and 2L may mean that the field indicating SDU length in a sub- header is two bytes.
  • a sub-header for a CE is one byte long.
  • the length of subheaders for SDUs may vary, e.g. there may be sub-headers having length of 2 bytes (e.g. one for indicating length of SDU and one for LCID) or length of 3 bytes (e.g. 2 bytes for indicating length of SDU).
  • Each sub-header 414, 415, 424 may be for a CE or a SDU. That is, each subheader may be associated with a CE or a SDU 452, 462. As the sub-headers 414, 415, 424 may be arranged by their lengths to the first and second headers 410, 420, parts 450, 460 may each comprise both CEs and SDUs at least in cases where sub-headers for CEs have a length of 2 bytes or more. For example, the sub-headers 414 may comprise one sub- header for a CE and one for a SDU, wherein said CE and SDU are comprised in the part 450.
  • the sub-headers 424 may comprise one sub-header for a CE and two for a SDU, wherein said CE and SDUs are comprised in the part 460.
  • subheaders 414 have a length of 1 byte and are for CEs. Therefore, the part 450 may comprise only CEs.
  • the part 460 may then comprise SDUs having a variable length, wherein the subheaders 424 have a fixed length (e.g. 2 or 3 bytes).
  • a length of a sub-header for a CE is fixed. That is, each subheader for CE has a fixed length which may be determined by, for example, cellular communication specifications.
  • the length of the first header 410 is indicate with number of sub-headers in the first header 410. Similar logic may apply to the second header 420 if the sub-headers in the second header 420 are of equal length.
  • the PDU 400 further comprises the third information element 432 indicating length of a part 450 of the PDU 400 for one or more control elements 452 and/or for one or more service data units 452, said part 450 being associated with the first header 410 or the second header 420.
  • the third information element 432 may be, in some embodiments, be used to indicate a length of a part comprising only CEs. However, if the sub-headers 414, 424 are arranged according to their lengths, as illustrated in Figure 4E for example, the third information element 432 may be used to indicate the length of the part 450 or the part 460. This may enable the receiver to determine where the parts 450, 460 are located in the PDU 400.
  • the length of the part 450 may be defined by the CEs and/or SDUs 452 within the part 450.
  • the length indication by the third information element 432 may further enhance the processing of the PDU at the receiver.
  • the PDU 400 comprises a fourth information element indicating a length of a third header, and a fifth information element indicating a length of another part of the PDU 400 comprising one or more CE and/or SDUs associated with the third header.
  • the third header may comprise sub-header(s) having a third length.
  • the first length may be 1 byte
  • the second length may be 2 bytes
  • the third length may be 3 bytes.
  • the first header may comprise sub-headers for CEs
  • the second and third headers may comprise sub-headers for SDUs.
  • the PDU 400 comprises a third information element indicating a length of a third header of the PDU 400.
  • the first information element 412 may indicate length of the first header 410 comprising one or more sub- headers for one or more CEs. Said CEs may be comprised in the first header 410.
  • the second information element 422 may indicate length of the second header 420 comprising one or more sub-headers for one or more SDUs.
  • the third header may comprise one or more sub-headers for one or more SDUs.
  • the sub-headers comprised in the second header 420 may have a first length (e.g. 2 bytes), whereas the sub-headers of the third header may have a second length (e.g. 3 or 4 bytes).
  • the transmitter may thus arrange the sub-headers for the SDUs according to their lengths within the PDU 400.
  • the PDU 400 may also comprise a fourth information element to enable the different SDUs to be processed in parallel. However, in some embodiments, this may not be necessary, and thus the PDU 400 may comprise three headers and three information elements indicating the lengths of the headers.
  • the PDU 400 may further comprise a padding part 470, wherein a length of the padding part 470 is based at least on the indicated lengths of the first and second headers 410, 420. Further, the length of the data part 440 may affect the length of the padding part 470.
  • the data part 440 may comprise, for example, the parts 450 and 460 in some embodiments.
  • the data part 440 may comprise, for example, the parts 450 and 460 in some embodiments.
  • the data part 440 may comprise, for example, the part 430 in some embodiments (e.g. Figure 4D).
  • the data part may generally refer to part(s) of the PDU 400 comprising the CEs and SDUs.
  • the length of the padding part 470 may be affected by the first and second headers 410, 420 and by the part of the PDU comprising the one or more SDUs.
  • the padding part 470 may be used to make the PDU 400 to be of certain predetermined length by the transmitter.
  • the length of the padding part 470 may be affected by a TB onto which the PDU 400 is mapped. For example, specification may have some requirement for the length. However, in some embodiments, the length of the PDU may vary, and thus the padding part 470 may not be necessary.
  • the predetermined length of the PDU 400 known by the receiver and the transmitter, may enable the receiver to process the PDU 400.
  • the length of the data part 440 may be known when the length of the first and second headers 410, 420 is known (i.e. indicated by the first and second information elements 412, 422).
  • the length of the padding part 470 is further based on the length of the TB onto which the PDU 400 is mapped. That is, padding bits or bytes may be used to fill the PDU 400 such that it is suitable size for a certain sized TB. Therefore, for example, the length of the padding part 470 (i.e. number of padding bits used) may be determined, by the transmitter, by determining TB length or size, deducting lengths of headers of the PDU 400 (e.g. first and second headers 410, 420) from said TB length, and deducting lengths of CE and/or SDU parts of the PDU 400 from the TB length. Thus, the transmitter may know how many padding bits needs to be used to prepare the PDU 400 to be suitable to said TB.
  • the length of the padding part 470 i.e. number of padding bits used
  • the transmitter may know how many padding bits needs to be used to prepare the PDU 400 to be suitable to said TB.
  • control information 402 e.g. control part 402
  • the control part 402 may be located, for example, in the beginning of the PDU 400. In some other cases, the location may be something else than the beginning of the PDU 400. However, in some embodiments, it may be the most beneficial to start the PDU 400 with the control part 402 as it may be used to indicate the following structure of the PDU 400. That is, the receiver may acquire knowledge, by reading the control part 402, whether there is two or three information elements (e.g. 412, 422, 432), for example.
  • control part 402 may be generated, by the transmitter, so that the control part 402 indicates how many and/or which information elements (e.g. 412, 422, 432) are present in the PDU 400.
  • the control part may indicate number of headers 410, 420 and/or number of sub-headers in a header.
  • number of CEs and/or SDUs may be indicated in some embodiments.
  • the control part 402 may indicate to the receiver which kind of PDU 400 structure is used. That is, if solution of Figure 4B would be solution #1 , solution of Figure 4C would be solution #2, and solution of Figure 4D would be solution #3, the control part could indicate which of the three solutions is used for that particular PDU.
  • control part 402 may indicate structure of the PDU 400, thus enabling the receiver to process the PDU 400 accordingly.
  • Figure 5 illustrates an embodiment.
  • the first information element 412 indicates the length of the first header 410 by indicating a number of sub-headers 504 in the first header.
  • the second information element 422 may indicate the length of the second header 420 by indicating a number of sub-headers 504 in the second header 420.
  • Similar logic may apply to the third information element 432, wherein the length of CEs and/or SDUs is predetermined in the part of the PDU 400 comprising said CEs and/or SDUs.
  • the length of a header 506 may be determined by the length of the sub-headers 502 and the number of subheaders 504. That is, for example, in the first header 410 the length of the sub-headers may be constant or predetermined (i.e. known by the transmitter and the receiver or at least by the receiver). Thus, by indicating the number of sub-headers 504 in the first header 410, the receiver may determine the length of the first header 410. Similarly, the length of the second header 420 may be determined.
  • the information elements 412, 422, 432 may be used to indicate length of different parts of the PDU 400.
  • the information elements 412, 422, 432 may have a length of 8 bits (i.e. 1 octet or 1 byte), for example. This may mean that there is a reserved space of 8 bits for each information element 412, 422, 432 in the PDU 400. Naturally, if the third information element 432 is not used, the space does not need to be reserved for the third information element.
  • the bits comprised in the first information element 412 may be used to indicate a length of the first header 410, for example.
  • Similar logic may apply to the other information elements 422, 432.
  • the bits comprised in the first information element 412 may be used to indicate the number of sub-headers in the first header 410. Similar logic may apply to the other information elements 422, 432.
  • Figure 7 illustrates a signal diagram according to an embodiment. Referring to Figure 7, a scenario of downlink transmission is shown. Similar logic may apply, however, for example to uplink transmission also.
  • the network element 102 may acquire one or more SDUs and/or one or more CEs to be mapped to a PDU (e.g. PDU 400). Said SDUs and/or the CEs may be to be transmitted to the terminal device 1 10.
  • PDU e.g. PDU 400
  • the network element 102 may structure or generate the PDU, wherein the PDU comprises said SDUs and/or CEs. Further, the PDU may comprise the first and second information elements, for example. In some examples, as described, the PDU may comprise the third, fourth and/or fifth information elements. Also, the PDU may comprise the first and second headers.
  • the network element 102 may map the PDU to a TB, and in step 706, the network element 102 may cause a transmission of signal carrying said TB to the terminal device 1 10.
  • the terminal device 1 10 may receive the transmission and acquire the TB and the PDU from the TB.
  • the terminal device 1 10 may, in step 710, process the obtained PDU.
  • the terminal device 1 10, after obtaining the PDU may cause an initiation of parallel processing of a parallel processing of the first header and the second header of the PDU. This may be enabled by the first and second information elements. That is, the parallel processing may be possible, as described with reference to Figure 6A, for example.
  • the first header may be processed further by a scheduler.
  • the second header and the SDUs may be sent to RLC layer for further processing, i.e. mapping to logical channels.
  • the parallel processing may comprise processing the one or more control elements and/or one or more service data units associated with the first header and processing the one or more control elements and/or one or more service data units associated with the second header. That is, as described with reference to Figure 6B, the CEs may be processed in parallel with the SDUs by the terminal device 1 10 or some other network element. In another example, the parallel processing of the headers comprising sub-headers grouped according to their lengths (e.g. Figure 4E) may be possible. Thus, also the CEs and SDUs in different parts (e.g. parts 450, 460) may be possible.
  • the terminal device 1 10 may determine the length of the part 450 based on the third information element. This may enable the terminal device 1 10 start the parallel processing.
  • the terminal device 1 10 may further obtain at least one of a sub-header length in the first header, a sub-header length in the second header, wherein the determining the lengths of the first and/or second headers 410, 420 is based on the number and lengths of sub-headers. Example of this is shown in Figure 5.
  • the PDU 400 comprises the third information element 432 indicating the length of the part 450 for one or more CEs and/or SDUs 452.
  • the receiver for example, the terminal device 1 10 may then further determine a length of another part 460 of the PDU 400 for one or more further CEs and/or SDUs 462, said another part 460 being associated with the first header 410 or the second header 420.
  • said another part 460 may be associated with the second header 420
  • the part 450 length indicated by the third information element 432
  • the PDU 400 is applicable for D2D communication. That is, the receiver and the transmitter may be terminal devices.
  • the defined PDU structure may not be restricted to the communication system or network elements described above. This may mean that the PDU structure may be used also in some other systems and with some other network elements, for example.
  • Figures 8 to 9 provide apparatuses 800, 900 comprising a control circuitry (CTRL) 810, 910, such as at least one processor, and at least one memory 830, 930 including a computer program code (software) 832, 932, wherein the at least one memory and the computer program code (software) 832, 932, are configured, with the at least one processor, to cause the respective apparatus 800, 900 to carry out any one of the embodiments of Figures 2 to 7, or operations thereof.
  • CTRL control circuitry
  • the memory 830, 930 may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the memory 830, 930 may comprise a database 834, 934 for storing data.
  • the apparatuses 800, 900 may further comprise radio interface (TRX) 820, 920 comprising hardware and/or software for realizing communication connectivity according to one or more communication protocols.
  • TRX radio interface
  • the TRX may provide the apparatus with communication capabilities to access the radio access network, for example.
  • the TRX may comprise standard well-known components such as an amplifier, filter, frequency-converter, (de)modulator, and encoder/decoder circuitries and one or more antennas.
  • the TRX may enable communication between the terminal device 1 10 and the network element 102 and/or the D2D communication capability. Further, the TRX may provide access to t e X2-interface for the network element 102, for example.
  • the apparatuses 800, 900 may comprise user interface 840, 940 comprising, for example, at least one keypad, a microphone, a touch display, a display, a speaker, etc.
  • the user interface 840, 940 may be used to control the respective apparatus by a user of the apparatus 800, 900.
  • the apparatus 800 may be or be comprised in a terminal device (e.g. the terminal device 1 10), such as a mobile phone or cellular phone, for example.
  • the apparatus 800 may be or be comprised in the network element 102, for example.
  • the apparatus 800 may be the network element performing the steps of Figure 2, for example.
  • control circuitry 810 may comprise a PDU structuring circuitry 812 configured to structure a PDU 400 to comprise a header part at least for a first header 410 and for a second header 420, wherein the PDU 400 comprises a first information element 412 indicating a length of the first header 410 and a second information element 422 indicating a length of the second header 420.
  • the control circuitry 810 may further comprise a transmission circuitry 814 configured to cause a transmission of a signal carrying the PDU 400 to another network element of a cellular communication system.
  • the transmission circuitry 814 may cause the radio interface 820 to transmit said signal (e.g. comprising a TB to which the PDU 400 is mapped onto).
  • the terminal device 1 10 may structure and transmit the PDU 400 to a base station or vice versa.
  • the apparatus 900 may be or be comprised in a terminal device (e.g. the terminal device 1 10), such as a mobile phone or cellular phone, for example.
  • the apparatus 900 may be or be comprised in the network element 102, for example.
  • the apparatus 900 may be the network element performing the steps of Figure 3, for example.
  • the control circuitry 910 comprises a PDU obtaining circuitry 912 configured to obtain, a PDU 400 comprising a header part at least for a first header 410 and for a second header 420, wherein the PDU 400 comprises a first information element 412 indicating a length of the first header 410 and a second information element 422 indicating a length of the second header 420; a header length determining circuitry 914 configured to determine, based on the first and second information elements 412, 422, the lengths of the first and second headers 410, 420; and an action performing circuitry 916 configured to perform an action based on the determined lengths of the first and second headers 410, 420. The action may be performed to the PDU 400.
  • the action may comprise, for example, processing the PDU 400.
  • the action at least comprises processing the first and second information elements 412, 422.
  • the action comprises processing separating the first header 410 from the PDU 400.
  • the first header 410 may be sent to a scheduler, for example.
  • the action comprises processing the CE(s) and/or SDUs of the PDU 400 based at least partly on the indicated lengths of the first and second headers 410, 420.
  • the apparatus 800 and/or the apparatus 900 may be shared between two physically separate devices, forming one operational entity. Therefore, the apparatus may be considered to depict the operational entity comprising one or more physically separate devices for executing at least some of the above-described processes.
  • the apparatuses of Figures 8 and/or 9, utilizing such a shared architecture may comprise a remote control unit (RCU), such as a host computer or a server computer, operatively coupled (e.g. via a wireless or wired network) to a remote radio head (RRH) located at a base station site.
  • RCU remote control unit
  • RRH remote radio head
  • at least some of the described processes of the network node may be performed by the RCU.
  • the execution of at least some of the described processes may be shared among the RRH and the RCU.
  • the RCU may comprise the components illustrated in Figure 8 and/or 9, and the radio interface 820 or the radio interface 920 may provide the RCU with the connection to the RRH.
  • the RRH may then comprise radio frequency signal processing circuitries and antennas, for example.
  • the RCU may generate a virtual network through which the
  • virtual networking may involve a process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network.
  • Network virtualization may involve platform virtualization, often combined with resource virtualization.
  • Network virtualization may be categorized as external virtual networking which combines many networks, or parts of networks, into the server computer or the host computer (i.e. to the RCU). External network virtualization is targeted to optimized network sharing. Another category is internal virtual networking which provides network-like functionality to the software containers on a single system. Virtual networking may also be used for testing the terminal device.
  • virtual network resources may give potential to apply parallel processing of PDUs (e.g. MAC PDUs). That is, if there are a lot of virtual resources available, the receiver may use them to process the PDUs in a parallel way (e.g. parallel processing of SDUs and/or CEs as described above). However, if the computational resources are scarce, the receiver may only process latency critical data (e.g. some SDUs or some PDUs) in the proposed way (i.e. in parallel), while rest of the data (e.g. CEs or some PDUs) may be processed consecutively.
  • latency critical data e.g. some SDUs or some PDUs
  • rest of the data e.g. CEs or some PDUs
  • the receiver may determine whether or not there is enough free processing or computational resources for parallel processing of a PDU (e.g. PDU 400). If there are, the receiver may cause parallel processing of the PDU. However, if the receiver determines that there are not enough radio resources for parallel processing, the receiver may cause consecutive processing of the PDU (i.e. CEs and/or SDUs may be processed consecutively).
  • the virtual network may provide flexible distribution of operations between the RRH and the RCU. In practice, any digital signal processing task may be performed in either the RRH or the RCU and the boundary where the responsibility is shifted between the RRH and the RCU may be selected according to implementation.
  • circuitry refers to all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of circuits and soft-ware (and/or firmware), such as (as applicable) : (i) a combination of processor(s) or (ii) portions of processor(s)/software including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus to perform various functions, and (c) circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.
  • circuitry' applies to all uses of this term in this application.
  • the term 'circuitry' would also cover an implementation of merely a processor (or multiple processors) or a portion of a processor and its (or their) accompanying software and/or firmware.
  • the term 'circuitry' would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.
  • Figures 2 to 7 may be carried out by an apparatus comprising corresponding means for carrying out at least some of the described processes.
  • Some example means for carrying out the processes may include at least one of the following: detector, processor (including dual-core and multiple-core processors), digital signal processor, controller, receiver, transmitter, encoder, decoder, memory, RAM, ROM, software, firmware, display, user interface, display circuitry, user interface circuitry, user interface software, display software, circuit, antenna, antenna circuitry, and circuitry.
  • the at least one processor, the memory, and the computer program code form processing means or comprises one or more computer program code portions for carrying out one or more operations according to any one of the embodiments of Figures 2 to 7 or operations thereof.
  • the apparatus carrying out the embodiments comprises a circuitry including at least one processor and at least one memory including computer program code. When activated, the circuitry causes the apparatus to perform at least some of the functionalities according to any one of the embodiments of Figures 2 to 7, or operations thereof.
  • the techniques and methods described herein may be implemented by various means. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or combinations thereof.
  • the apparatus(es) of embodiments may be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • processors controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.
  • the implementation can be carried out through modules of at least one chip set
  • the software codes may be stored in a memory unit and executed by processors.
  • the memory unit may be implemented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art.
  • the components of the systems described herein may be rearranged and/or complemented by additional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the given figures, as will be appreciated by one skilled in the art.
  • Embodiments as described may also be carried out in the form of a computer process defined by a computer program or portions thereof. Embodiments of the methods described in connection with Figures 2 to 7 may be carried out by executing at least one portion of a computer program comprising corresponding instructions.
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program.
  • the computer program may be stored on a computer program distribution medium readable by a computer or a processor.
  • the computer program medium may be, for example but not limited to, a record medium, computer memory, read-only memory, electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program medium may be a non- transitory medium. Coding of software for carrying out the embodiments as shown and described is well within the scope of a person of ordinary skill in the art.
  • a computer-readable medium comprises said computer program.

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil mettant en œuvre ledit procédé, le procédé comportant : la structuration, par un élément de réseau d'un système de communication cellulaire, d'une unité de données de protocole de manière à comporter une partie d'en-tête au moins destinée à un premier en-tête et à un second en-tête, l'unité de données de protocole comportant un premier élément d'information indiquant une longueur du premier en-tête et un second élément d'information indiquant une longueur du second en-tête ; et le déclenchement de l'émission d'un signal transportant l'unité de données de protocole vers un autre élément de réseau du système de communication cellulaire.
PCT/EP2016/056250 2016-03-22 2016-03-22 Amélioration de l'efficacité de communication indiquant la longueur de deux en-têtes dans la pdu Ceased WO2017162273A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2016/056250 WO2017162273A1 (fr) 2016-03-22 2016-03-22 Amélioration de l'efficacité de communication indiquant la longueur de deux en-têtes dans la pdu

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2016/056250 WO2017162273A1 (fr) 2016-03-22 2016-03-22 Amélioration de l'efficacité de communication indiquant la longueur de deux en-têtes dans la pdu

Publications (1)

Publication Number Publication Date
WO2017162273A1 true WO2017162273A1 (fr) 2017-09-28

Family

ID=55589860

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2016/056250 Ceased WO2017162273A1 (fr) 2016-03-22 2016-03-22 Amélioration de l'efficacité de communication indiquant la longueur de deux en-têtes dans la pdu

Country Status (1)

Country Link
WO (1) WO2017162273A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100232356A1 (en) * 2009-03-16 2010-09-16 Qualcomm Incorporated Layer two segmentation techniques for high data rate transmissions
US20120047573A1 (en) * 2010-08-17 2012-02-23 Richard Jeremy Duncan Methods and apparatus for detecting invalid ipv6 packets
US20130039273A1 (en) * 2010-02-10 2013-02-14 Lg Electronics Inc. Method and apparatus for receiving a medium access control protocol data unit having a fragmentation and packing extended header

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100232356A1 (en) * 2009-03-16 2010-09-16 Qualcomm Incorporated Layer two segmentation techniques for high data rate transmissions
US20130039273A1 (en) * 2010-02-10 2013-02-14 Lg Electronics Inc. Method and apparatus for receiving a medium access control protocol data unit having a fragmentation and packing extended header
US20120047573A1 (en) * 2010-08-17 2012-02-23 Richard Jeremy Duncan Methods and apparatus for detecting invalid ipv6 packets

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUANG N-F ET AL: "DESIGN OF MULTI-FIELD IPV6 PACKET CLASSIFIERS USING TERNARY CAMS", GLOBECOM '01 : IEEE GLOBAL TELECOMMUNICATIONS CONFERENCE ; SAN ANTONIO, TEXAS, USA, 25 - 29 NOVEMBER 2001, IEEE OPERATIONS CENTER, PISCATAWAY, NJ, 25 November 2001 (2001-11-25), pages 1877 - 1881, XP001054898, ISBN: 978-0-7803-7206-1 *

Similar Documents

Publication Publication Date Title
CN115843440B (zh) 通信方法和通信装置
US11711813B2 (en) Downlink control channel signaling for an aperiodic channel state information trigger
US20200214065A1 (en) User equipment category signaling in an lte-5g configuration
US20240214282A1 (en) Traffic steering for service function chaining (sfc) in next generation cellular networks
WO2020225092A1 (fr) Mappage d'en-têtes d'extension gtp-u
KR20190129191A (ko) 차세대 이동 통신 시스템에서 주변 셀의 기준 신호로 준지속적 사운딩 기준 신호를 지시하는 방법 및 장치
EP3257183B1 (fr) Agrégation cellulaire et wlan
WO2023220147A1 (fr) Fonctions de réseau de plan de commande 6g dans une architecture basée sur un service
US20200084797A1 (en) Radio band sharing between nodes
US20130223395A1 (en) Apparatus and Method for Communication
WO2018053692A1 (fr) Procédé, dispositif, et système de transmission de données
KR20240034684A (ko) 6세대(6g) 시스템 아키텍처 및 기능
GB2551485A (en) Providing service data flow description
US20150223155A1 (en) System information for device-to-device discovery
EP3257317B1 (fr) Planification de liaison montante avec une agrégation de réseau local sans fil (wlan)/de projet de partenariat de troisième génération (3gpp)
US11234151B2 (en) Management plane performance indicator transfer
WO2018031081A1 (fr) Systèmes et procédés de séquençage de protocole de convergence de données par paquets
CN115884389A (zh) 载波配置方法及通信装置
US20240172247A1 (en) Resource allocation for sidelink communication
EP4616583A1 (fr) Rapport de retard pour segments de réseau dans un trajet de communication de bout en bout
EP3403427B1 (fr) Découverte rapide de dispositif
WO2017162273A1 (fr) Amélioration de l'efficacité de communication indiquant la longueur de deux en-têtes dans la pdu
WO2024102249A1 (fr) Rapport de retard pour segments de réseau dans un trajet de communication de bout en bout
JP2020005290A (ja) Ｗｌａｎ／３ｇｐｐアグリゲーションでの上りリンクスケジューリング

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16711615

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16711615

Country of ref document: EP

Kind code of ref document: A1