WO2021069552A1 - Identification de flux de réseau à contraintes de temps dans un flux de qos 3gpp - Google Patents

Identification de flux de réseau à contraintes de temps dans un flux de qos 3gpp Download PDF

Info

Publication number
WO2021069552A1
WO2021069552A1 PCT/EP2020/078223 EP2020078223W WO2021069552A1 WO 2021069552 A1 WO2021069552 A1 WO 2021069552A1 EP 2020078223 W EP2020078223 W EP 2020078223W WO 2021069552 A1 WO2021069552 A1 WO 2021069552A1
Authority
WO
WIPO (PCT)
Prior art keywords
time sensitive
quality
packet
child
service flow
Prior art date
Application number
PCT/EP2020/078223
Other languages
English (en)
Inventor
Pilar ANDRÉS MALDONADO
Troels Emil Kolding
Devaki Chandramouli
Original Assignee
Nokia Technologies 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 Technologies Oy filed Critical Nokia Technologies Oy
Publication of WO2021069552A1 publication Critical patent/WO2021069552A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2491—Mapping quality of service [QoS] requirements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]

Definitions

  • Time sensitive networks may be used to support a variety of applications including applications such as ultra-reliable low-latency communications (URLLC), industrial verticals, and/or the like.
  • applications such as ultra-reliable low-latency communications (URLLC), industrial verticals, and/or the like.
  • URLLC ultra-reliable low-latency communications
  • industrial verticals and other mission critical applications there may be some requirements that are relatively unique, such as certain requirements for low latency, deterministic data transmission, and high reliability, when compared to other 5G cellular services.
  • an apparatus configured to at least: receive at least one packet including a header, the header including a quality of service flow identifier and one or more child identifiers, the one or more child identifiers identifying respective time sensitive streams within a quality of service flow identified by the quality of service flow identifier; map, based at least on the quality of service flow identifier and one of the one or more child identifiers, a time sensitive stream to a time sensitive communication assistance information; and forward, based on the time sensitive communication assistance information, the time sensitive stream.
  • the map between the time sensitive stream and the time sensitive communication assistance information may be based on explicit signaling from the session management function.
  • the map between the time sensitive stream and the time sensitive communication assistance information may be implicit based on the time sensitive communication assistance information.
  • the apparatus may be further caused to at least modify, based on the one of the one or more child identifiers, a quality of service flow context for a modification of the protocol data unit session associated with the time sensitive stream.
  • the apparatus may comprise or is comprised in a base station.
  • an apparatus configured to at least: receive a packet of a time sensitive stream; determine, based on a header of the packet, a quality of service flow identifier; map a child identifier to the time sensitive stream, the child identifier uniquely identifying the time sensitive stream within a quality of service flow identified by the quality of service flow identifier; and forward, towards a base station, a user plane packet encapsulating at least a portion of the time sensitive stream, a user plane packet header indicating the child identifier and the quality of service flow identifier for the quality of service flow carrying the time sensitive stream.
  • the user plane packet may include a general packet radio service tunnel protocol packet or a service data adaptation protocol packet.
  • the packet may be received from a time sensitive network end station.
  • An allocation of the child identifier and the map between the quality of service flow identifier and the child identifier may be explicit based on signaling received from a session management function.
  • the apparatus may be further caused to at least allocate the child identifier in response to the packet of the time sensitive stream being received.
  • the apparatus may be further caused to at least modify, based on one or more child identifiers, a quality of service flow context for a modification of a protocol data unit session associated with the time sensitive stream.
  • the map between the quality of service flow identifier and the child identifier is derived from information obtained from a service data adaptation protocol header and/or obtained from the packet of the time sensitive stream.
  • the apparatus may comprise or be comprised in a network node, a user plane function, a session management function, and/or a user equipment.
  • FIG. 1 A depicts an example of a portion of a time sensitive network, in accordance with some example embodiments
  • FIG. IB depicts an example of a 3GPP bridge for a time sensitive network, in accordance with some example embodiments
  • FIG. 2 depicts example of time sensitive network traffic class mappings to 3 GPP QoS flow, in accordance with some example embodiments
  • FIG. 3 depicts an example of a single Time Sensitive Communications Assistance Information (TSCAI) description per QoS flow, in accordance with some example embodiments;
  • TSCAI Time Sensitive Communications Assistance Information
  • FIG. 4 depicts TSCAI description per time sensitive network stream, in accordance with some example embodiments
  • FIG. 5A depicts an example of the child ID, in accordance with some example embodiments.
  • FIG. 5B depicts an example of a system using the child ID, in accordance with some example embodiments.
  • FIG. 6 shows an example of a QoS flow definition augmented to include one or more child IDs, in accordance with some example embodiments.
  • FIG. 7A depicts an example of signaling diagram including child IDs, in accordance with some example embodiments.
  • FIG. 7B depicts another example of a signaling diagram including the child ID, in accordance with some example embodiments;
  • FIG. 7C depicts an example of a signaling flow for a user equipment requested protocol data unit session modification procedure, in accordance with some example embodiments;
  • FIG. 7D depicts an example of a signaling diagram for a session management function requested protocol data unit session modification, in accordance with some example embodiments
  • 3GPP wireless technologies may be applied in addition to wired time sensitive networking (TSN) to provide additional flexibility with respect to mobility and to provide scalability with respect to the quantity of sensors, actuators, and/or the like which can be supported.
  • TSN wired time sensitive networking
  • a TSN or other source of deterministic traffic may couple to a user equipment and use the 3 GPP wireless network as a bridge to enable the traffic to traverse the 3GPP network to another device or network, such as another TSN network.
  • deterministic traffic refers to predictable, such as periodic traffic, an example of which is TSN traffic, which may be in accordance with IEEE 802.1 series standards, for example.
  • the CUC 102 may be configured in accordance with the one or more of the IEEE 802.1 series of TSN standards.
  • the CUC may control the configuration of end stations 107A-F and/or applications at the end stations.
  • the CUC may interface with the CNC 104 to make requests to the CNC for deterministic, TSN communications (e.g., TSN flows) with specific requirements for those flows between end stations.
  • TSN flow may represent a time sensitive, deterministic stream of traffic between end stations. These TSN flows may have low delay and/or strict timing requirements for time sensitive networks.
  • a TSN flow (also referred to as a TSN stream) between end stations may be used in an industrial control application (e.g., robot, etc.) requiring low delay and/or strict, deterministic timing between the end stations.
  • the TSN flow may also have requirements for ultra-low reliability.
  • the CNC 104 may provide a proxy for the TSN bridges 105A-C and the corresponding interconnections, and provide a proxy for control applications that require deterministic communication.
  • the CNC may define the schedules, such as gate schedules, on which all TSN traffic is transmitted (or received) between the end stations including any intervening devices such as the TSN bridges 105A-C.
  • the schedules may define periodic transmission and/or reception.
  • the UE 164 and/or RAN 170 may be configured with a schedule such as a gate schedule (which may be in accordance with IEEE 802. IQbv).
  • the gate schedule defines when traffic, such as burst, can be transmitted (or received) over the link in order to satisfy the low-latency and/or deterministic needs of TSN.
  • the gate schedule may define the periodicity of the transmission and/or reception of a given device.
  • the links e.g., uplinks and/or downlinks
  • the links via the RAN represent the wireless part of the end-to-end connection between the TSN system 188A and another device or network, such as the TSN system 188B.
  • one or more of the bridges 105A-C may be implemented using the 3GPP bridge 105D of FIG. ID to provide TSN support over the 5G wireless system. From the perspective of the end stations 107A and D for example, the 5G system’s 3GPP bridge 105D appears like a more traditional wired TSN bridge.
  • the TSN may be configured to define up to eight traffic classes with corresponding priorities for the traffic classes, so that one or more TSN streams may be mapped to the traffic class(es). Therefore, the per-UPF 3 GPP bridge may provide ports at which ingress TSN streams are mapped to one or more TSN traffic classes. While the UPF may map individual service data flows or an entire traffic class into a 3 GPP QoS flow of a PDU session. In other words, a 3GPP/5G system’s QoS flow may have one or more TSN streams aggregated into the same 3GPP/5G QoS flow.
  • Time Sensitive Communications Assistance Information may be provided as well.
  • the TSCAI may indicate (e.g., define, describe, etc.) the TSC traffic characteristics for use in the 5G system.
  • the TSCAI may include parameters, such as flow direction, periodicity for transmit and/or receive, and burst arrival time. These parameters may be used to allow more efficient scheduling of the deterministic traffic flows at a base station, such as a gNB base station serving the RAN 170.
  • a network node such as the SMF 176 or other network node, may determine the TSCAI and then the SMF may provide the TSCAI to a gNB, such as the gNB serving RAN 170.
  • the TSCAI may be determined based on information received from the TSN application function (AF) 150.
  • the TSCAI may play a role in the radio access network’s ability to achieve optimized scheduling.
  • the integrated 3GPP-TSN may include the adaptation of the representation of parameters and/or semantics.
  • a QoS flow may be considered the finest granularity of QoS differentiation in the PDU session.
  • the relevant scheduling information (which may be received from the CNC) may be per port and per TSN traffic class. With only eight available values of deterministic service differentiation in the TSN domain, this leads to whether in the 3GPP domain there may be one or more 3GPP QoS flows mapped to the same TSN traffic class.
  • the 5G system may provide a 3 GPP bridge that directly receives the resource requests from the CNC based on the capabilities previously reported and the CUC requirements.
  • the 5G system may have less freedom to optimize the management of TSN deterministic QoS flows as the information it receives from the CNC is limited.
  • the mapping between TSN streams, TSN traffic class, 3GPP QoS flow, and TSCAI may become more relevant.
  • FIG. 2 depicts some of the possible mapping options, such as N:N 202, N:M 220, and N: 1 230, between TSN traffic classes and QoS flows.
  • N:N mapping 202 a TSN traffic class 206 (including a plurality of TSN streams) is mapped to a 3GPP QoS flow 208, while another TSN traffic class 210 (including a plurality of TSN streams) is mapped to another 3GPP QoS flow 212.
  • the TSN bridge receives TSN streams having the same TSN traffic class 222A-D, each of which is mapped to a corresponding QoS flow 224A-D.
  • the TSN streams 232 (all of which have the same TSN traffic class in this example) are all mapped to the same QoS flow 236, and the TSN stream 234 is also mapped to QoS flow 236.
  • the QoS flows may be characterized by a QoS profile, one or more QoS rules, and one or more uplink and downlink packet detection rules (PDRs).
  • the QoS flow ID (QFI) is used to identify a QoS flow in 3GPP’s 5G system.
  • the QFI may be assigned by the SMF, and the QFI may be unique within a protocol data unit (PDU) session.
  • PDU protocol data unit
  • the QFI is carried encapsulated in the General Packet Radio Service Tunnel Protocol-user plane (GTP-U) header between the gNB base station and the UPF.
  • GTP-U General Packet Radio Service Tunnel Protocol-user plane
  • the TSCAI granularity may limit the TSCAI use at the gNB as it may be difficult to discern the specific information of each TSN stream if more than one TSN stream is aggregated in the QoS Flow. If the gNB does not have the detailed traffic pattern information per TSN stream, the configuration of configured grants (CGs) or semi-persistent scheduling (SPSs) may be less than optimal.
  • CGs configured grants
  • SPSs semi-persistent scheduling
  • FIG. 4 depicts one TSCAI description per TSN stream.
  • the TSN stream 402 is mapped to a corresponding TSCAI description 404 and to the QoS flow 450 (which in this example has a QFI of “1”).
  • the TSN stream 412 is mapped to a corresponding TSCAI description 414 and to the QoS flow 450 (which in this example has a QFI of “1”).
  • the TSN stream 422 has a corresponding TSCAI description 424 and to the QoS flow 450 (which in this example has a QFI of “1”).
  • the TSN stream 432 is mapped to a corresponding TSCAI description 434 and to the QoS flow 436 (which in this example has a QFI of “2”).
  • FIG. 4 may provide additional granularity, it may not efficiently identify the aggregated TSN streams placed into QoS flow 1 450 in the 5G system.
  • the identification of the TSN streams that are aggregated in a QoS flow there is provided a new identifier (ID), which is referred herein as a “child ID.”
  • ID a new identifier
  • the child ID identifies a single (e.g., one) TSN stream aggregated into a QoS flow.
  • the child ID provides smaller granularity, when compared to just a QFI that identifies the overall 3GPP QoS flow but not the TSN streams in the QoS flow if there is more than one TSN stream aggregated to that QoS flow.
  • FIG. 5A depicts an example of the child ID, in accordance with some example embodiments.
  • FIG. 5A depicts the QoS flow definition including the mappings between the TSN streams (having a TSN traffic class), the corresponding TSCAI, QoS flows (which are each identified by a QFI), and respective child IDs, in accordance with some example embodiments.
  • the TSN stream 1 502A and TSN stream 2 502B both having a TSN traffic class of 3
  • TSN stream 502C which has a TSN traffic class of 7 are mapped into the same QoS flow 550 (identified with, e.g., the “QFI 1”).
  • the QFI 1 the QoS flow definition
  • the TSN streams 502A-C each have a corresponding TSCAI 504A-C.
  • each TSN stream 502A-C within the 3GPP QoS flow 550 has a respective child ID 569A-C to distinguish each of the TSN streams 502A-C within the QoS flow 550.
  • FIG. 5 A shows the example of the child IDs being used to identify the TSN streams within a 3GPP QoS flow in the case of one TSCAI per TSN stream (as in FIG. 4, for example), the child IDs may also be used to identify the TSN streams within a 3GPP QoS flow in the case of one TSCAI per QoS flow (as in FIG. 3, for example).
  • the child ID may be included in a field, such as an optional field within the QoS flow definition.
  • the QoS flow definition may be augmented to include a fourth element, such as the child ID(s) 569A-C.
  • the child ID element may comprise a list of the child IDs 569A-C the QoS flow 550 is carrying.
  • FIG. 5B depicts the TSN streams 502A-C identified within the QoS flow, QFI 1 550 based on the respective child IDs 569A-C for each of the TSN streams.
  • FIG. 6 shows an example of a 3 GPP QoS flow definition 600 augmented to include on or more child IDs 620 being carried by a given QoS flow, in accordance with some example embodiments.
  • the child ID 620 may be managed in the same or similar manner as the QFI 610.
  • the child ID may be allocated by the SMF, when a new service traffic (e.g., TSN stream) is aggregated into a QoS flow, although the child ID may be allocated at other times as well.
  • the child ID signaling from the SMF towards the UE, gNB, and/or UPF may be similar in some respects to QFI signaling.
  • the child ID may be forwarded with the updated definition 600 of the QoS flow.
  • the UPF may allocate the child ID, when the first data packet from a TSN stream is processed in the user plane.
  • a network node such as a UPF or SMF, may allocate the child ID by for example, selecting a child ID (e.g., from a group of available child IDs) and assign the selected child ID to a specific TSN stream within a QoS flow.
  • the network node may determine which child IDs are not being used in a QoS flow to identify TSN streams, and select one of the child IDs not currently being used to assign to a TSN stream.
  • the child ID may be unique within a QoS flow.
  • the UE, gNB, and/or UPF may mark data packets with the child ID.
  • the UE may add the child ID in a header, such as the Service Data Adaptation Protocol (SDAP) header, to assist the gNB in recognizing the TSN stream.
  • SDAP Service Data Adaptation Protocol
  • the UPF may add the child ID in the GTP-U header.
  • the gNB base station may forward the child ID to the UPF or UE (e.g., the gNB to UPF for an uplink stream and gNB to UE for a downlink stream), although there may be cases where the UE or UPF may benefit from having this information at a higher layer before examining the PDU content.
  • the child IDs may each map to the TSCAI for a specific TSN stream at the gNB in at least two different ways, such as explicit mapping and implicit mapping.
  • explicit mapping indication if the SMF is responsible for child ID allocation, the received signaling from the SMF to the gNB may include the mapping between the TSCAI and the child ID, so that the gNB can use the mapping for handling of upstream or downstream packets associated with a TSN flow being handled by the 3GPP bridge.
  • the UPF may mark the GTP-U packet with a new allocated child ID (assuming the received packet from a TSN stream does not already map to a child ID).
  • the gNB may use the detailed traffic arrival timing description in the TSCAI (e.g., burst arrival time, etc. that is received from the SMF) to derive the mapping between the TSCAI and the child ID from the arrival time of the data packet at the gNB.
  • the traffic information may be provisioned, from the TSN AF to the 5G system, on a per TSN stream.
  • This provisioned information may include traffic filters and/or markers (e.g., a combination virtual local area network ID, source MAC, etc.) to be used in the SMF to derive the packet detection rules (PDRs) and the forwarding action rules (FAR) to be forwarded to the UPF to enable user plane child ID marking per TSN stream.
  • PDRs packet detection rules
  • FAR forwarding action rules
  • the SDAP and GTP-U header may, as noted, be augmented to include child ID as a field.
  • the PDU session procedures may be augmented to include the child ID when needed during the establishment, modification, and/or release of a QoS flow.
  • FIG. 7A depicts a signaling diagram 700 showing the child ID used when forwarding a downlink TSN stream, in accordance with some example embodiments.
  • the child ID may assist in identifying individual TSN streams when there are multiple TSN streams merged into a single QoS flow being handled by the 3 GPP system and, in particular, the 3 GPP bridge.
  • the child ID facilitates the management of a downlink TSN stream in the user plane within a 3GPP bridge, such as 3GPP bridge 105D.
  • the UE may map the child ID with a specific TSN stream and modify the context of the QoS flow accordingly.
  • Each user plane entity may be responsible for modifying its current QoS flow context.
  • the UPF may not be able send the whole QoS flow definition as the SMF usually does.
  • each TSN stream is also mapped to at least a QoS flow ID (QFI) (e.g., QFI1 at FIG. 5A identifying QoS flow 550).
  • QFI QoS flow ID
  • the UPF may inspect a TSN frame (e.g., a packet) and from the Ethernet header information, the UPF may map the TSN stream to a QFI and child ID combination.
  • the UPF compares the fields of the data packet received to the stored PDRs to classify it.
  • the matching PDR may contain a FAR that details the forwarding the UPF should apply such as the creation of the outer GTP-U header including the child ID.
  • the UPF 182 may forward to the gNB 170 the GTP-U packet encapsulating the TSN stream, wherein the GTP-U header includes at least the QFI and the corresponding child ID for the received TSN stream.
  • the gNB 170 may forward to the UE 164 an SDAP packet encapsulating the TSN stream frame, and this SDAP packet may have a header including the QFI and if needed, the child ID.
  • the DS-TT 162 performs translation and provides the TSN stream frame to the end station 107A.
  • end-to-end communications are established between the TSN end stations 107 A and 107D via the 3 GPP bridge 105D, in accordance with some example embodiments.
  • the 3GPP bridge 105D receives at least one TSN stream.
  • the UE 164 may then map the TSN stream to a corresponding QFI and child ID, in accordance with some example embodiments. The mapping is based on the QoS rules the SMF configures (or UE-derived if the UPF was responsible for child ID allocation and there is no signaling from the SMF forwarding the child ID) in the UE in 702.
  • the UE 164 may also mark, at 766, the SDAP packet header with the child ID (as well as he QFI), so that the SDAP encapsulated TSN stream (a packet in the TSN stream, for example) can be distinguished from other TSN steams in the same QoS flow identified by the QFI.
  • the gNB 170 may then forward to the UPF 182 the TSN stream encapsulated in a GTP-U packet having a header marked with the QFI and/or child ID.
  • the UPF 182 receives the TSN stream and forwards it to the TSN end station 107D.
  • FIG. 7C depicts an example of a signaling flow for a UE requested PDU session modification procedure, in accordance with some example embodiments.
  • the process at FIG. 7C may be in accordance with 3GPP TS 23.502 augmented to include child IDs.
  • the SMF 176 may send, at 782, to the AMF 172 a message, such as the Nsmf_PDUSession_UpdateSMContext response including the child ID within the updated QoS profile.
  • the AMF 172 may then send to the gNB 170 a message, such as the N2 session request including the child ID within the updated QoS profile.
  • the gNB 170 may issue a specific signaling exchange with the UE 164 including the child ID within the updated QoS profile.
  • the N4 session modification request and response between the UPF 182 and SMF 176 may also include the child ID and corresponding
  • the SMF 176 may decide, at 790B, to modify, at 790B, a PDU session and add, modify, or release one or more child ID(s) within a QoS flow.
  • SM SMF initiated session management
  • FIG. 8 depicts a block diagram of a network node 800, in accordance with some example embodiments.
  • the network node 800 may be configured to provide one or more network side functions, such as abase station (e.g., RAN 170), AMF 172, PCF 180, AF 150, CNC 104, CUC 102, and/or other network nodes.
  • the network node 800 may include a network interface 802, a processor 820, and a memory 804, in accordance with some example embodiments.
  • the network interface 802 may include wired and/or wireless transceivers to enable access other nodes including base stations, devices 152-180, the Internet, and/or other nodes.
  • the memory 804 may comprise volatile and/or non-volatile memory including program code, which when executed by at least one processor 820 provides, among other things, the processes disclosed herein with respect to the network node.
  • the gNB type base station may also map, based at least on the quality of service flow identifier and the child identifier, a time sensitive stream to a time sensitive communication assistance information.
  • the gNB type base station may also forward, based on the time sensitive communication assistance information, the time sensitive stream.
  • the network node comprises or is comprised in a user plane function (UPF).
  • UPF user plane function
  • the UPF may receive a packet of a time sensitive stream.
  • the packet may be received from a time sensitive network end station.
  • the UPF may map the quality of service flow identifier to a child identifier uniquely identifying the time sensitive stream within a quality of service flow identified by the quality of service flow identifier.
  • the user plane packet comprises a general packet radio service tunnel protocol packet.
  • an allocation of the child identifier and the map between the quality of service flow identifier and the child identifier is explicit based on signaling received from a session management function.
  • FIG. 9 illustrates a block diagram of an apparatus 10, in accordance with some example embodiments.
  • the apparatus 10 may include at least one antenna 12 in communication with a transmitter 14 and a receiver 16 Alternatively transmit and receive antennas may be separate.
  • the apparatus 10 may also include a processor 20 configured to provide signals to and receive signals from the transmitter and receiver, respectively, and to control the functioning of the apparatus.
  • Processor 20 may be configured to control the functioning of the transmitter and receiver by effecting control signaling via electrical leads to the transmitter and receiver.
  • processor 20 may be configured to control other elements of apparatus 10 by effecting control signaling via electrical leads connecting processor 20 to the other elements, such as a display or a memory.
  • the processor 20 may, for example, be embodied in a variety of ways including circuitry, at least one processing core, one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and/or the like), or some combination thereof. Accordingly, although illustrated in FIG. 9 as a single processor, in some example embodiments the processor 20 may comprise a plurality of processors or processing cores.
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the apparatus 10 may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like.
  • Signals sent and received by the processor 20 may include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wi-Fi, wireless local access network (WLAN) techniques, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, and/or the like.
  • these signals may include speech data, user generated data, user requested data, and/or the like.
  • the apparatus 10 may be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and/or the like. Further, for example, the apparatus 10 may be capable of operating in accordance with 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division- Synchronous Code Division Multiple Access (TD-SCDMA), and/or the like. The apparatus 10 may be additionally capable of operating in accordance with 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and/or the like. Additionally, for example, the apparatus 10 may be capable of operating in accordance with 4G wireless communication protocols, such as LTE Advanced, 5G, and/or the like as well as similar wireless communication protocols that may be subsequently developed.
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data GSM Environment
  • the processor 20 may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as the speaker 24, the ringer 22, the microphone 26, the display 28, and/or the like.
  • the processor 20 and/or user interface circuitry comprising the processor 20 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions, for example, software and/or firmware, stored on a memory accessible to the processor 20, for example, volatile memory 40, non-volatile memory 42, and/or the like.
  • the apparatus 10 may include a battery for powering various circuits related to the mobile terminal, for example, a circuit to provide mechanical vibration as a detectable output.
  • the user input interface may comprise devices allowing the apparatus 20 to receive data, such as a keypad 30 (which can be a virtual keyboard presented on display 28 or an externally coupled keyboard) and/or other input devices.
  • apparatus 10 may also include one or more mechanisms for sharing and/or obtaining data.
  • the apparatus 10 may include a short-range radio frequency (RF) transceiver and/or interrogator 64, so data may be shared with and/or obtained from electronic devices in accordance with RF techniques.
  • RF radio frequency
  • the apparatus 10 including the Wi-Fi or wireless local area networking modem may also be capable of transmitting and/or receiving data from electronic devices according to various wireless networking techniques, including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN techniques such as IEEE 802.11 techniques, IEEE 802.15 techniques, IEEE 802.16 techniques, and/or the like.
  • various wireless networking techniques including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN techniques such as IEEE 802.11 techniques, IEEE 802.15 techniques, IEEE 802.16 techniques, and/or the like.
  • the apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, and/or the like, which may store information elements related to a mobile subscriber.
  • SIM subscriber identity module
  • R-UIM removable user identity module
  • eUICC embedded user identity module
  • UICC universal integrated circuit card
  • the apparatus 10 may include volatile memory 40 and/or non-volatile memory 42.
  • volatile memory 40 may include Random Access Memory (RAM) including dynamic and/or static RAM, on-chip or off-chip cache memory, and/or the like.
  • RAM Random Access Memory
  • Non-volatile memory 42 which may be embedded and/or removable, may include, for example, read-only memory, flash memory, magnetic storage devices, for example, hard disks, floppy disk drives, magnetic tape, optical disc drives and/or media, non-volatile random access memory (NVRAM), and/or the like. Like volatile memory 40, non-volatile memory 42 may include a cache area for temporary storage of data.
  • volatile memory 40 non-volatile memory 42 may include a cache area for temporary storage of data.
  • At least part of the volatile and/or non-volatile memory may be embedded in processor 20.
  • the memories may store one or more software programs, instructions, pieces of information, data, and/or the like which may be used by the apparatus for performing operations disclosed herein.
  • the apparatus may be configured to cause the operations disclosed herein with respect to the base stations/WLAN access points and network nodes including the UEs.
  • the memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10.
  • the memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10.
  • the processor 20 may be configured using computer code stored at memory 40 and/or 42 to the provide operations disclosed herein with respect to the UE.
  • a “computer-readable medium” may be any non-transitory media that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry, with examples depicted at FIG. 9, computer-readable medium may comprise a non-transitory computer-readable storage medium that may be any media that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
  • the UE may determine, based on a header of the packet, a quality of service flow identifier.
  • the UE may map the quality of service flow identifier to a child identifier uniquely identifying the time sensitive stream within a quality of service flow identified by the quality of service flow identifier. [0099] In some example embodiments, the UE may forward, towards a base station, a user plane packet encapsulating the time sensitive stream encapsulated, the user plane packet including a header indicating the child identifier and the quality of service flow identifier for the quality of service flow carrying the time sensitive stream.
  • the user plane packet comprises a service data adaptation protocol packet.
  • the packet is received from a time sensitive network end station.
  • an allocation of the child identifier and the map between the quality of service flow identifier and the child identifier is explicit based on signaling received from a session management function.
  • the UE may modify, based on one or more child identifiers, a quality of service flow context for a modification of a protocol data unit session associated with the time sensitive stream.
  • the map between the quality of service flow identifier and the child identifier includes the time sensitive stream, wherein the map is derived from a service data adaptation protocol header and information about the time sensitive stream.
  • the base stations and user equipment (or one or more components therein) and/or the processes described herein can be implemented using one or more of the following: a processor executing program code, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field programmable gate array (FPGA), and/or combinations thereof.
  • ASIC application-specific integrated circuit
  • DSP digital signal processor
  • FPGA field programmable gate array

Landscapes

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

Abstract

Selon des modes de réalisation, l'invention peut concerner un appareil configuré au moins : pour recevoir au moins un paquet incluant un entête, l'entête incluant un identifiant de flux de qualité de service et un ou plusieurs identifiants d'enfants, l'identifiant ou les identifiants d'enfants identifiant des flux à contraintes de temps respectifs dans un flux de qualité de service identifié par l'identifiant de flux de qualité de service ; pour mapper, sur la base au moins de l'identifiant de flux de qualité de service et de l'identifiant ou d'un des identifiants d'enfants, un flux à contrainte de temps vers une information d'assistance de communication à contrainte de temps ; et pour rediriger, sur la base de l'information d'assistance de communication à contrainte de temps, le flux à contrainte de temps. L'invention concerne également des systèmes, des procédés, et des articles manufacturés.
PCT/EP2020/078223 2019-10-11 2020-10-08 Identification de flux de réseau à contraintes de temps dans un flux de qos 3gpp WO2021069552A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962914020P 2019-10-11 2019-10-11
US62/914,020 2019-10-11

Publications (1)

Publication Number Publication Date
WO2021069552A1 true WO2021069552A1 (fr) 2021-04-15

Family

ID=72885515

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2020/078223 WO2021069552A1 (fr) 2019-10-11 2020-10-08 Identification de flux de réseau à contraintes de temps dans un flux de qos 3gpp

Country Status (1)

Country Link
WO (1) WO2021069552A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852978A (zh) * 2021-09-24 2021-12-28 京信网络系统股份有限公司 基站数据处理方法、装置、设备和存储介质
CN115150334A (zh) * 2022-09-02 2022-10-04 北京智芯微电子科技有限公司 基于时间敏感网络的数据传输方法、装置及通信设备
US20220345415A1 (en) * 2021-04-22 2022-10-27 Moxa Inc. Apparatuses and methods for supporting class-based scheduling in a time-sensitive networking (tsn) network
WO2023093368A1 (fr) * 2021-11-26 2023-06-01 中兴通讯股份有限公司 Procédé de commande de transmission de données, dispositif et support de stockage
WO2023174023A1 (fr) * 2022-03-18 2023-09-21 华为技术有限公司 Procédé et appareil de communication
WO2023236065A1 (fr) * 2022-06-07 2023-12-14 Nokia Shanghai Bell Co., Ltd. Configuration de réseautage sensible au temps

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16)", 23 September 2019 (2019-09-23), XP051839499, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/Latest_SA2_Specs/DRAFT_INTERIM/Archive/23501-g20_Postponed_23.501%20CR1592_NOT_23501_CR1345r2_CRs_Implemented.zip> [retrieved on 20190923] *
HUAWEI ET AL: "Discussion on system enhancement for TSN logical bridge management", vol. SA WG2, no. Kochi, India; 20190121 - 20190125, 15 January 2019 (2019-01-15), XP051595358, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/SA2/Docs/S2%2D1900590%2Ezip> [retrieved on 20190115] *
HUAWEI ET AL: "Updates on Solution #18", vol. SA WG2, no. West Palm Beach, USA; 20181126 - 20181130, 20 November 2018 (2018-11-20), XP051490408, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/WG2%5FArch/TSGS2%5F129BIS%5FWest%5FPalm%5FBeach/Docs/S2%2D1812232%2Ezip> [retrieved on 20181120] *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220345415A1 (en) * 2021-04-22 2022-10-27 Moxa Inc. Apparatuses and methods for supporting class-based scheduling in a time-sensitive networking (tsn) network
US11824788B2 (en) * 2021-04-22 2023-11-21 Moxa Inc. Apparatuses and methods for supporting class-based scheduling in a time-sensitive networking (TSN) network
CN113852978A (zh) * 2021-09-24 2021-12-28 京信网络系统股份有限公司 基站数据处理方法、装置、设备和存储介质
CN113852978B (zh) * 2021-09-24 2023-12-12 京信网络系统股份有限公司 基站数据处理方法、装置、设备和存储介质
WO2023093368A1 (fr) * 2021-11-26 2023-06-01 中兴通讯股份有限公司 Procédé de commande de transmission de données, dispositif et support de stockage
WO2023174023A1 (fr) * 2022-03-18 2023-09-21 华为技术有限公司 Procédé et appareil de communication
WO2023236065A1 (fr) * 2022-06-07 2023-12-14 Nokia Shanghai Bell Co., Ltd. Configuration de réseautage sensible au temps
CN115150334A (zh) * 2022-09-02 2022-10-04 北京智芯微电子科技有限公司 基于时间敏感网络的数据传输方法、装置及通信设备

Similar Documents

Publication Publication Date Title
US20210400524A1 (en) Method to support 5g time sensitive communications
US11825337B2 (en) 5G system support for virtual TSN bridge management, QoS mapping and TSN Qbv scheduling
WO2021069552A1 (fr) Identification de flux de réseau à contraintes de temps dans un flux de qos 3gpp
US11956157B2 (en) Activation of PDU session and QOS flows in 3GPP-based ethernet bridges
KR102267267B1 (ko) 세션 컨텍스트 변환
US20220263743A1 (en) Selective packet duplication or alternative packet transmission based on survival time
US20220078662A1 (en) TSN-CELLULAR COMMUNICATION SYSTEM QoS MAPPING AND RAN OPTIMIZATION BASED ON TSN TRAFFIC PATTERN RELATED INFORMATION
WO2021136636A1 (fr) Regroupement d&#39;un flux de qualité de service (qos) pour des communications d&#39;équipement utilisateur à équipement utilisateur
CN113746585B (zh) 授时方法和通信装置
CN112636884B (zh) 一种消息传输方法和装置
US20230019215A1 (en) TSC-5G QoS MAPPING WITH CONSIDERATION OF ASSISTANCE TRAFFIC INFORMATION AND PCC RULES FOR TSC TRAFFIC MAPPING AND 5G QoS FLOWS BINDING
CN114009144B (zh) Tsn业务转发的分组延迟预算确定
CN112423340A (zh) 一种用户面信息上报方法及装置
CN113938904A (zh) 数据传输的方法和装置
WO2017080422A1 (fr) Procédé et dispositif de gestion de qos
CN107211317B (zh) 利用wlan/3gpp聚合的上行链路调度
WO2023160116A1 (fr) Procédé et appareil de communication
US20230038925A1 (en) Qos flow configuration for user equipment to user equipment communications
WO2023284551A1 (fr) Procédé, dispositif et système de communication
US20240137801A1 (en) Adaptive forwarding handling of data packets
CN111050354B (zh) Rrc连接重配置的方法、装置、相关设备及存储介质
WO2024067194A1 (fr) Procédé de communication, appareil de communication et système de communication
WO2024113069A1 (fr) Systèmes et procédés de gestion de qualité de service pour un trafic de réalité étendue
WO2021128225A1 (fr) Procédé de traitement de flux de service, appareil et système
CN118202700A (zh) 信息传输方法及装置、存储介质

Legal Events

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

Ref document number: 20792322

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20792322

Country of ref document: EP

Kind code of ref document: A1