Apparatus, method and computer program

Abstract

The invention provides a device. The apparatus comprises means at an entity for determining burst timing information for at least one uplink periodic traffic flow for an application at an uplink ingress node, determining feedback information based on the burst timing information and radio access network (RAN) information, and providing the feedback information to a function associated with the application.

Description

Technical Field

[0001] The present application relates to a method, apparatus, system, and computer program, particularly but not limited to, for burst arrival time determination of UL flows. Background Art

[0002] A communication system can be viewed as a facility that enables communication sessions between two or more entities (such as user terminals, base stations, and / or other nodes) by providing a bearer between the various entities involved in the communication path. A communication system can be provided, for example, by a communication network and one or more compatible communication devices. A communication session can include, for example, data communications for bearer communications, such as voice, video, electronic mail (email), text messaging, multimedia, and / or content data, etc. Non-limiting examples of the services provided include two-way or multi-way calls, data communications or multimedia services, and access to a data network system (such as the Internet).

[0003] In a wireless communication system, at least a portion of a communication session between at least two stations is conducted over a wireless link. Examples of wireless systems include public land mobile networks (PLMNs), satellite-based communication systems, and different wireless local networks, such as wireless local area networks (WLANs). Some wireless systems can be divided into cells and are therefore often referred to as cellular systems.

[0004] A user can access a communication system through an appropriate communication device or terminal. The user's communication device may be referred to as a user device (UE) or user equipment. The communication device is equipped with appropriate signal receiving and sending devices to enable communication, such as enabling access to a communication network or communicating directly with other users. The communication device can access a carrier provided by a station (e.g., a base station of a cell) and send and / or receive communications on the carrier.

[0005] A communication system and associated equipment typically operate according to a given standard or specification that specifies what each entity associated with the system is allowed to do and how it should be achieved. Communication protocols and / or parameters for the connection are also typically defined. An example of a communication system is UTRAN (3G radio). Other examples of communication systems are the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology, and the so-called 5G or New Radio (NR) networks. NR is being standardized by the Third Generation Partnership Project (3GPP). Summary of the invention

[0006] In a first aspect, a device is provided, comprising components at an entity for: determining burst timing information for at least one uplink periodic service flow of an application at an uplink ingress node, determining feedback information based on the burst timing information and radio access network RAN ​​information, and providing feedback information to a function associated with the application.

[0007] The entity may comprise: a RAN node. The means for determining the burst timing information may comprise means for receiving the burst timing information from the uplink ingress node via a time sensitive communication time synchronization function.

[0008] The apparatus may include means for receiving burst timing information in time sensitive communication assistance information from a session management function.

[0009] The uplink ingress node may be configured to observe burst timing information via indications from a time sensitive communications time synchronization function.

[0010] The entity may comprise a time sensitive communication time synchronization function. The means for determining the burst timing information may comprise means for receiving the burst timing information from an uplink ingress node.

[0011] The apparatus may include means for receiving burst timing information using a port management information container.

[0012] The apparatus may include means for providing an indication to an uplink ingress node to observe burst timing information.

[0013] The apparatus may include means for receiving, at the entity, RAN information from a RAN node.

[0014] The entity may comprise: an uplink ingress node. The means for determining the burst timing information may comprise: means for observing the burst timing information.

[0015] The apparatus may include means for providing feedback information to a function associated with the application using a port management information container.

[0016] The apparatus may include means for providing feedback information to a function associated with an application via an access and mobility management function.

[0017] The apparatus may include means for providing feedback information to an access and mobility management function using non-access stratum session management signaling.

[0018] The apparatus may include means for receiving, at an entity, an indication to observe burst timing information, and determining feedback information based on the observed burst timing information.

[0019] The port management information container may include: an indication.

[0020] The indication may include at least one of the following: an indication of an uplink periodic traffic flow, and a measurement configuration.

[0021] The burst timing information may include at least one of: burst periodicity, absolute burst arrival time, burst arrival time variation, and offset time to a configured scheduling grant.

[0022] The RAN information may include at least one of: RAN configuration, and RAN node burst arrival time preference.

[0023] The uplink ingress node may include: user equipment, or a device-side time-sensitive network converter.

[0024] The feedback information may include: preferred uplink burst timing information.

[0025] In a second aspect, a method is provided, comprising: at an entity: determining burst timing information for at least one uplink periodic service flow of an application at an uplink ingress node, determining feedback information based on the burst timing information and radio access network RAN ​​information, and providing feedback information to a function associated with the application.

[0026] The entity may comprise: a RAN node. Determining the burst timing information may comprise receiving the burst timing information from an uplink ingress node via a time sensitive communication time synchronization function.

[0027] The method may include receiving burst timing information in time sensitive communications assistance information from a session management function.

[0028] The uplink ingress node may be configured to observe burst timing information via indications from a time sensitive communications time synchronization function.

[0029] The entity may include: a time sensitive communication time synchronization function. Determining the burst timing information may include: receiving the burst timing information from an uplink ingress node.

[0030] The method may include receiving burst timing information using a port management information container.

[0031] The method may include providing an indication to an uplink ingress node to observe burst timing information.

[0032] The method may include receiving, at an entity, RAN information from a RAN node.

[0033] The entity may include: an uplink ingress node. Determining the burst timing information may include: observing the burst timing information.

[0034] The method may include providing feedback information to a function associated with the application using a port management information container.

[0035] The method may include providing feedback information to a function associated with the application via an access and mobility management function.

[0036] The method may include providing feedback information to an access and mobility management function using non-access stratum session management signaling.

[0037] The method may include receiving an indication at an entity to observe burst timing information, and determining feedback information based on the observed burst timing information.

[0038] The port management information container may include: an indication.

[0039] The indication may include at least one of the following: an indication of an uplink periodic traffic flow, and a measurement configuration.

[0040] The burst timing information may include at least one of: burst periodicity, absolute burst arrival time, burst arrival time variation, and offset time to a configured scheduling grant.

[0041] The RAN information may include at least one of: RAN configuration, and RAN node burst arrival time preference.

[0042] The uplink ingress node may include: user equipment, or a device-side time-sensitive network converter.

[0043] The feedback information may include: preferred uplink burst timing information.

[0044] In a third aspect, a device is provided, comprising: at least one processor and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the device to at least: determine burst timing information for at least one uplink periodic service flow of an application at an uplink ingress node, determine feedback information based on the burst timing information and radio access network RAN ​​information, and provide feedback information to a function associated with the application.

[0045] The entity may comprise: a RAN node. The apparatus may be configured to: receive burst timing information from an uplink ingress node via a time sensitive communication time synchronization function.

[0046] The apparatus may be configured to receive burst timing information in the time sensitive communication assistance information from the session management function.

[0047] The uplink ingress node may be configured to observe burst timing information via indications from a time sensitive communications time synchronization function.

[0048] The apparatus may be configured to receive burst timing information from an uplink ingress node.

[0049] The apparatus may be configured to receive the burst timing information using a port management information container.

[0050] The apparatus may be configured to provide an indication to an uplink ingress node to observe burst timing information.

[0051] The apparatus may be configured to receive, at the entity, RAN information from a RAN node.

[0052] The entity may include: an uplink ingress node. The apparatus may be configured to: observe burst timing information.

[0053] The apparatus may be configured to provide feedback information to a function associated with the application using a port management information container.

[0054] The apparatus may be configured to provide feedback information to a function associated with an application via an access and mobility management function.

[0055] The apparatus may be configured to provide feedback information to an access and mobility management function using non-access stratum session management signaling.

[0056] The apparatus may be configured to receive an indication at an entity to observe burst timing information and determine feedback information based on the observed burst timing information.

[0057] The port management information container may include: an indication.

[0058] The indication may include at least one of the following: an indication of an uplink periodic traffic flow, and a measurement configuration.

[0059] The burst timing information may include at least one of: a burst period, an absolute burst arrival time, a burst arrival time variation, and an offset time to a configured scheduling grant.

[0060] The RAN information may include at least one of: RAN configuration, and RAN node burst arrival time preference.

[0061] The uplink ingress node may include: user equipment, or a device-side time-sensitive network converter.

[0062] The feedback information may include: preferred uplink burst timing information.

[0063] In a fourth aspect, a computer-readable medium comprising program instructions is provided, wherein the program instructions are used to cause the device to perform at least the following items at an entity: determine burst timing information for at least one uplink periodic service flow of an application at an uplink ingress node, determine feedback information based on the burst timing information and radio access network RAN ​​information, and provide feedback information to a function associated with the application.

[0064] The entity may comprise: a RAN node. Determining the burst timing information may comprise receiving the burst timing information from an uplink ingress node via a time sensitive communication time synchronization function.

[0065] The apparatus may be caused to perform: receiving, from a session management function, burst timing information in time sensitive communication assistance information.

[0066] The uplink ingress node may be configured to observe burst timing information via indications from a time sensitive communications time synchronization function.

[0067] The entity may include: a time sensitive communication time synchronization function. Determining the burst timing information may include: receiving the burst timing information from an uplink ingress node.

[0068] The apparatus may be caused to perform: receiving burst timing information using a port management information container.

[0069] The apparatus may be caused to perform: providing an indication to an uplink ingress node to observe burst timing information.

[0070] The apparatus may be caused to perform: receiving, at an entity, RAN information from a RAN node.

[0071] The entity may include: an uplink ingress node. Determining the burst timing information may include: observing the burst timing information.

[0072] The apparatus may be caused to perform: providing feedback information to a function associated with the application using a port management information container.

[0073] The apparatus may be caused to perform: providing feedback information to a function associated with an application via an access and mobility management function.

[0074] The apparatus may be caused to perform: providing feedback information to an access and mobility management function using non-access stratum session management signaling.

[0075] The apparatus may be caused to perform: receiving, at an entity, an indication to observe burst timing information, and determining feedback information based on the observed burst timing information.

[0076] The port management information container may include: an indication.

[0077] The indication may include at least one of the following: an indication of an uplink periodic traffic flow, and a measurement configuration.

[0078] The burst timing information may include at least one of: burst periodicity, absolute burst arrival time, burst arrival time variation, and offset time to a configured scheduling grant.

[0079] The RAN information may include at least one of: RAN configuration, and RAN node burst arrival time preference.

[0080] The uplink ingress node may include: user equipment, or a device-side time-sensitive network converter.

[0081] The feedback information may include: preferred uplink burst timing information.

[0082] In a fifth aspect, a non-transitory computer-readable medium comprising program instructions is provided, the program instructions being used to cause an apparatus to at least perform the method according to the third or fourth aspect.

[0083] Many different embodiments have been described above. It should be understood that further embodiments may be provided by combining any two or more of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0085] Figure 1 A schematic diagram of an example 5GS communication system is shown;

[0086] Figure 2 A schematic diagram of an example mobile communication device is shown;

[0087] Figure 3 A schematic diagram of an example control device is shown;

[0088] Figure 4 A flow chart showing a method according to an example embodiment is shown;

[0089] Figure 5 shows a signaling flow according to an example embodiment;

[0090] Figure 6 shows a signaling flow according to an example embodiment;

[0091] Figure 7 shows a signaling flow according to an example embodiment

[0092] Figure 8 A signaling flow according to an example embodiment is shown. DETAILED DESCRIPTION

[0093] Before explaining the examples in detail, refer to Figures 1 to 3 Certain general principles of wireless communication systems and mobile communication devices are briefly explained to aid understanding of the underlying techniques of the described examples.

[0094] An example of a suitable communication system is a 5G system (5GS). The network architecture in the 5GS may be a network architecture similar to that of advanced LTE. The base station of the NR system may be referred to as a next generation node B (gNB). Changes in the network architecture may depend on the need to support various radio technologies and more refined QoS support, as well as some on-demand requirements, such as QoS levels to support QoE from the user's perspective. In addition, network-aware services and applications, as well as service- and application-aware networks, may bring changes to the architecture. These are related to information-centric networks (ICNs) and user-centric content delivery networks (UC-CDN) approaches. NR may use multiple-input multiple-output (MIMO) antennas, more base stations or nodes than LTE (the so-called small cell concept), which include macro sites that operate in collaboration with small stations, and may also employ various radio technologies for better coverage and higher data rates.

[0095] 5G networks may utilize network function virtualization (NFV), a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that can be operably connected or linked together to provide services. Virtualized network functions (VNFs) may include one or more virtual machines that use standard or common types of servers rather than custom hardware to run computer program code. Cloud computing or data storage may also be utilized. In radio communications, this may mean that node operations are performed at least in part in a server, host, or node that is operably coupled to a remote radio head. Node operations may also be distributed among multiple servers, nodes, or hosts. It should also be understood that the division of labor between core network operations and base station operations may be different from that in LTE, or even nonexistent.

[0096] Figure 1 A schematic representation of a 5G system (5GS) 100 is shown. The 5GS may include: a user equipment (UE) 102 (also referred to as a communication device or terminal), a 5G radio access network (5GRAN) 104, a 5G core network (5GCN) 106, one or more application functions (AFs) 108, and one or more data networks (DNs) 110.

[0097] An example 5G core network (CN) includes functional entities. The 5GCN 106 may include: one or more access and mobility management functions (AMFs) 112, one or more session management functions (SMFs) 114, an authentication server function (AUSF) 116, a unified data management (UDM) 118, one or more user plane functions (UPFs) 120, a unified data repository (UDR) 122, and / or a network exposure function (NEF) 124. The UPF is controlled by the SMF (session management function) which receives policies from the PCF (policy control function). The time-sensitive communication time synchronization function (TSCTSF) 126 forwards the time-sensitive communication assistance container (TSCAC) to the SMF via the (PCF).

[0098] The CN is connected to the terminal device via a radio access network (RAN). The 5G RAN may include one or more gNodeB (GNB) distributed unit functions connected to one or more gNodeB (GNB) centralized unit functions. The RAN may include one or more access nodes.

[0099] The role of UPF (User Plane Function) is called PSA (Protocol Data Unit (PDU) Session Anchor), and UPF can be responsible for forwarding frames back and forth between DN (Data Network) and the tunnel established by 5G towards (multiple) UEs that exchange services with DN.

[0100] Now refer to Figure 2 describing in more detail possible mobile communication devices, Figure 2A schematic partial cross-sectional view of a communication device 200 is shown. Such a communication device is generally referred to as a user equipment (UE) or terminal. Suitable mobile communication devices can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include a mobile station (MS) or mobile device, such as a mobile phone or a so-called "smart phone", a computer equipped with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal data assistant (PDA) or a tablet computer equipped with wireless communication capabilities, an IP voice (VoIP) phone, a portable computer, a desktop computer, an image capture terminal device (such as a digital camera), a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a smart device, a wireless client device (CPE), or any combination of these, etc. The mobile communication device can provide, for example, data communication for carrying communication (such as voice, email (email), text message, multimedia, etc.). Therefore, a variety of services can be proposed and provided to the user via the user's communication device. Non-limiting examples of these services include: two-way or multi-way calls, data communications or multimedia services or simply access to a data communications network system, such as the Internet. Broadcast or multicast data may also be provided to the user. Non-limiting examples of content include: downloads, television and radio programs, videos, advertisements, various alerts, and other information.

[0101] The mobile device is typically equipped with at least one data processing entity 201, at least one memory 202, and other possible components 203, which are used to assist in performing the tasks it is designed to perform with software and hardware, including controlling access and communication with access systems and other communication devices. Data processing, storage, and other related control devices can be provided on appropriate circuit boards and / or in chipsets. This feature is represented by reference numeral 204. The user can control the operation of the mobile device through a suitable user interface (such as a keyboard 205, voice commands, a touch screen or touchpad, a combination thereof, etc.). A display 208, a speaker, and a microphone can also be provided. In addition, the mobile communication device may include appropriate connectors (wired or wireless) to connect to other devices and / or for connecting external accessories (such as hands-free devices) thereto.

[0102] The mobile device 200 may receive signals via appropriate means for receiving, over the air or radio interface 207, and may transmit signals via appropriate means for transmitting radio signals. Figure 2 In FIG. 2 , the transceiver arrangement is schematically indicated by block 206. The transceiver arrangement 206 may be provided, for example, by a radio part and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0103] Figure 3 An example of a control device 300 for a communication system is shown, for example, the control device 300 is coupled to and / or used to control a station (such as a RAN node, such as a base station, eNB or gNB, a relay node, or a core network node (such as an MME or S-GW or P-GW), or a core network function (such as an AMF / SMF), or a server or host) of an access system. The method can be implemented in a single control device, or across more than one control device. The control device can be integrated with a node or module of the core network or RAN, or located outside a node or module of the core network or RAN. In some embodiments, the base station includes a separate control device unit or module. In other embodiments, the control device can be another network element, such as a radio network controller or a spectrum controller. In some embodiments, each base station can have such a control device, as well as a control device provided in a radio network controller. The control device 300 can be arranged to be provided in a service area of ​​the system to control communications. The control device 300 includes at least one memory 301, at least one data processing unit 302, 303, and an input / output interface 304. The control device can be coupled to a receiver and a transmitter of the base station via an interface. The receiver and / or the transmitter may be implemented as a radio front end or a remote radio head.

[0104] Consideration is being given to the need for application-specific downstream scheduling to enable 5GS to meet very low latency requirements (e.g., meeting a 2 ms packet delay budget (PDB)). In particular, application-specific transmission scheduling adjustments and capabilities are needed to meet very low PDB for QoS flows from a 5GS perspective for periodic traffic flows (based on feedback from the RAN WG).

[0105] In addition, the need to obtain feedback from the RAN (e.g., considering DL packet transmission time slots for applications to avoid buffering in the RAN) is being considered. That is, how to enable the RAN to provide feedback to applications for low-latency communication (e.g., considering DL packet transmission time slots for applications to avoid buffering in the RAN) is being considered.

[0106] While the focus is on downstream scheduling, any changes to upstream scheduling should not be ruled out if similar enhancements to downstream scheduling can be applied.

[0107] There are two approaches for providing burst timing feedback from the Next Generation Radio Access Network (NG-RAN) to applications, namely a passive approach and an active approach.

[0108] In the passive approach, after a Time Sensitive Communication (TSC) application starts sending a flow, at a RAN node, feedback is provided to the application by the RAN node based on the observed ingress burst arrival times.

[0109] In the active approach, feedback (eg, transmission scheduling preferences) is provided to the application before the transmission begins, so that the application can use the provided information to determine the transmission time.

[0110] A proposal based on a passive feedback mechanism has been proposed, in which the RAN node observes the burst arrival time (BAT) of received downlink (DL) packets and provides feedback to the application function via the SMF.

[0111] Upon receiving a DL packet for a Quality of Service (QoS) flow from the UPF via the user plane, if the NG-RAN has received an indication of support for burst arrival time adaptation in the Time Sensitive Communication Assistance Information (TSCAI) for a given QoS flow, and the NG-RAN determines that the burst arrival time needs to be adjusted, the NG-RAN sends an indication to the SMF including a burst arrival time offset value. The burst arrival offset can take a positive or negative value.

[0112] Passive methods are also considered as part of complete RAN feedback. In other proposals, when active feedback is given, the RAN node derives feedback for both uplink (UL) and DL nodes. The RAN node also derives passive feedback for DL ​​nodes.

[0113] For passive feedback, the entity providing application-specific feedback should be aware of the current radio configuration (Time Division Duplex (TDD) configuration) and the actual burst arrival times with reference to the physical layer resource configuration (scheduling) at the radio interface.

[0114] One entity for feedback acquisition is the RAN node (base station), which is responsible for radio configuration and is also the entry node to the radio interface for DL ​​application flows, which enables the RAN node to directly observe the arrival time of DL bursts. Therefore, the RAN node derives the RAN feedback in the above proposal.

[0115] The above proposal provides a scheme in which the RAN node (e.g., the Central Unit Control Plane (CU-CP) of the gNB) derives feedback based on the observed burst arrival time, but the scheme does not describe how to detect the arrival time of the burst and the scheme focuses on DL flows.

[0116] One issue is how to derive UL flow RAN feedback for periodicity in a RAN node (or more generally on the network side) that is not the ingress node to the radio interface for UL application flows. Only the UE, being the ingress node to the radio interface for UL packets, can observe the UL BAT, but the RAN node derives the UL flow feedback for applications.

[0117] In one proposal, the UE determines a relative burst arrival time offset value with reference to the burst arrival time (BAT) experienced by the UE and the scheduled UL timeslot at the UE, and sends the time offset to the RAN via a radio resource control (RRC) message.

[0118] This proposal affects the RRC protocol. A proposal to signal auxiliary information (including UL data packet arrival times) for auxiliary scheduling configuration from the UE to the RAN via RRC has been rejected for standardization.

[0119] A solution has been provided for providing active and passive RAN feedback from a RAN node to an application for a DL flow, but no consideration has been given to how the RAN feedback is derived by a RAN node (or a central node) for a UL flow.

[0120] Figure 4 A flow chart of a method according to an example embodiment is shown. The method is performed at an entity. The entity may include: a RAN node (e.g., a gNB), a core network node (e.g., a time-sensitive communication time synchronization function (TSCTSF)), or an uplink ingress node (e.g., a UE or device-side time-sensitive network translator DS-TT).

[0121] In S1 , the method comprises: at an uplink ingress node, determining burst timing information for at least one uplink periodic traffic flow of an application.

[0122] In S2, the method includes: determining feedback information based on burst timing information and radio access network RAN ​​information.

[0123] In S3, the method includes providing feedback information to a function associated with the application.

[0124] The burst timing information may include at least one of: burst periodicity, absolute burst arrival time, burst arrival time variation, and offset time to a configured scheduling grant.

[0125] The RAN information may include at least one of: RAN configuration, and RAN node burst arrival time preference.

[0126] The uplink ingress node may be: a user equipment (UE) or a device-side time-sensitive network translator (DS-TT).

[0127] The feedback information may include: preferred UL burst timing information.

[0128] The uplink ingress node can be: UE or DS-TT.

[0129] The UL periodic service flow may be: a QoS flow.

[0130] When the entity is a RAN node, determining the burst timing information comprises receiving the burst timing information from an uplink ingress node via the TSCTSF.The method may comprise receiving the burst timing information in time sensitive communication assistance information from a session management function.

[0131] The TSCTSF may provide an indication to the uplink ingress node to observe timing information. The indication may be provided in the PMIC. The indication may include at least one of the following items: an indication of an uplink periodic service flow (e.g., a packet filter identifying an UL service flow), and a measurement configuration (e.g., measurement type (absolute BAT, offset), measurement period, and reporting interval).

[0132] In a first example embodiment, a device side TSN translator (DS-TT) observes the burst arrival time of the UL flow. Alternatively or additionally, the UE observes the burst arrival time and transmits the result to the DS-TT. The burst timing information based on the burst arrival time is then transmitted to the RAN node via the TSCTSF. In this example embodiment, the DS-TT indicates the UL burst arrival time information in the port management information container (PMIC) transfer from the DS-TT to the TSCTSF (entrance of the DS-TT).

[0133] TSCTSF considers the UE-DS-TT residence time and calculates the expected UL burst arrival time information to the SMF within the TSC auxiliary container (TSCAC).

[0134] The timing information is delivered from the SMF to the RAN node as part of the TSC Assistance Information (TSCAI).

[0135] After receiving the burst timing information, the RAN node derives feedback based on the UL burst timing information and the RAN configuration, and forwards the feedback to the application function.

[0136] Figure 5 A signaling flow chart according to a first exemplary embodiment is shown. Figures 5 to 8 In the example scenario shown, the TSC application function requests an AF session with the requested QoS. The application function indicates in the request its capability for mid-stream (passive) adjustment of burst transmission times. The 5G session with the requested QoS is set up and the application sender starts sending bursts of periodic UL flows.

[0137] exist Figure 5In step 1, after receiving the adjustment capability information from the AF, the TSCTSF sends an indication to the DS-TT in the PMIC to start UL BAT measurement and report BAT information to the TSCTSF. The indication includes: a packet filter to identify the UL service flow for which BAT measurement and reporting are to be performed. The filter type depends on the PDU session type.

[0138] If the UE performs UL BAT measurement, DS-TT forwards the BAT measurement indication and packet filter to the UE. The UE compares the packet filter with the filter it has in the QoS rule for mapping UL packets to QoS flows. If there is a direct match, the UE is able to perform BAT measurements at the specific QoS flow level. The measurement indication may include: measurement type (absolute BAT, offset), measurement period, and reporting interval.

[0139] Alternatively, the burst timing adjustment capability of the application sender may be indicated to the RAN, and the RAN may transmit the capability to the UE in the form of RRC signaling. In this case, the QFI may be used as a reference for which QoS flow to perform BAT measurement and reporting.

[0140] In step 2, the UE observes the arrival time of the UL bursts of the periodic flow and transmits the UL burst timing information to the DS-TT.

[0141] Alternatively, the DS-TT applies the packet filter it receives from the TSCTSF to observe the UL BAT.

[0142] In step 3, the DS-TT includes the UL burst timing information in a Port Management Information Container (PMIC) and sends the PMIC to the TSCTSF as specified in the 3GPP standard.

[0143] In step 4, the TSC TSF receives the UL burst timing information in the PMIC from the DS-TT, includes the UL burst timing information in the TSCAC, and sends the TSCAC to the SMF through the PCF.

[0144] In step 5, if the UL burst arrival time is observed by DS-TT, the SMF calculates the burst arrival time at the radio by considering the UE dwell time. The SMF includes the burst timing information in the TSCAI and sends the TSCAI to the RAN node using PDU Session Change signaling.

[0145] The RAN node derives feedback for the UL by considering the UL burst arrival information and the RAN configuration in step 6. The RAN feedback is transmitted to the AF.

[0146] When the entity comprises a core network node (e.g., a TSCTSF), determining the burst timing information may include: receiving the burst timing information from an uplink ingress node. The burst timing information may be received in a port management information container (PMIC). The method may include: receiving RAN information from a RAN node at the entity. The method may include: providing an indication to the uplink ingress node to observe the burst timing information as described above.

[0147] In a second example embodiment, the DS-TT observes the burst arrival time of the UL flow (alternatively, the UE observes the burst arrival time and transmits the result to the DS-TT), and the burst arrival time information is transmitted from the DS-TT to the TSCTSF. In this example, PMIC delivery is utilized for the UL burst arrival time information transmission from the DS-TT to the TSCTSF.

[0148] TSCTSF considers the RAN configuration or the burst arrival time preference of the RAN to derive the UL burst arrival time.

[0149] In order for the TSCTSF to derive the UL burst arrival time, the radio configuration of the RAN node, or the UL burst arrival time preference of the RAN node is transmitted to the TSCTSF.

[0150] Figure 6 A signaling flow diagram for a second example embodiment is shown.

[0151] Step 1 to Step 3 reference Figure 5 is described.

[0152] In step 4, TSCTSF considers observed burst arrival time and RAN burst arrival time preference or radio configuration to derive feedback information (eg preferred UL burst timing information). If DS-TT observes UL burst arrival time, TSCTSF considers UE dwell time to calculate feedback information.

[0153] In step 5, the TSCTSF provides feedback information to the AF.

[0154] When the entity comprises an uplink ingress node, the method comprises observing burst timing information.

[0155] The method may include receiving an indication at an entity to observe burst timing information and determining feedback information based on the observed burst timing information.

[0156] The indication may be provided from the TSCTSF using the PMIC, or from the non-access stratum (NAS) signaling of the SMF. The indication may include at least one of the following: an indication of an uplink periodic service flow (e.g., a packet filter identifying the UL service flow), and a measurement configuration (e.g., measurement type (absolute BAT, offset), measurement period, and reporting interval).

[0157] The method may include providing, using the PMIC, feedback information to a function associated with the application.

[0158] In a third example embodiment, the UE observes the burst arrival time and periodicity of UL data packets and derives the UL burst arrival time by comparing the observed burst arrival time with the allocated radio resources and / or radio configuration. The UE transmits UL RAN feedback information to the TSCTSF via DS-TT using PMIC, and the TSCTSF forwards the feedback information to the application function.

[0159] Figure 7 A signaling flow diagram according to a third example embodiment is shown.

[0160] In this example, the PMIC from the TSCTSF to the DS-TT includes the burst timing adjustment capability applied and an indication to derive the preferred UL burst timing feedback.

[0161] In step 2, the UE observes the burst arrival time and periodicity of UL data packets and derives UL feedback information by comparing the observed burst arrival time with the timing of the allocated radio resources.

[0162] In step 3, DS-TT includes the UL RAN feedback in a Port Management Information Container (PMIC) and sends the PMIC to the TSCTSF as specified in the 3GPP standard.

[0163] In step 4, the TSCTSF provides RAN feedback to the AF.

[0164] Alternatively, when the entity includes an uplink ingress node, the method may include providing feedback information to a function associated with the application via the AMF. The feedback information may be provided to the AMF using non-access stratum (NAS) session management (SM) signaling.

[0165] In the fourth exemplary embodiment, as described for the third exemplary embodiment, the UE observes the burst arrival time and periodicity of UL data packets, and derives feedback information (e.g., preferred BAT) by comparing the observed burst arrival time with the allocated radio resources and / or radio configuration. The UE then transmits the UL burst timing information in NAS SM signaling and associates it with the corresponding QoS flow mapped to the service filter.

[0166] The UE includes the UL feedback in the NAS SM signaling and sends the NAS SM signaling to the AMF, and the AMF forwards the NAS SM signaling to the TSCTSF via the PCF.

[0167] The TSCTSF provides the received feedback to the AF.

[0168] Figure 8 A signaling flow diagram according to a fourth example embodiment is shown.

[0169] In step 1, the UE receives an indication from the SMF to determine the burst timing feedback.

[0170] In step 2, the UE observes the burst arrival time and periodicity of UL data packets and derives feedback by comparing the observed burst arrival time with the allocated radio resources and / or radio configuration.

[0171] In step 3, the UE transmits feedback information in NAS SM signaling to the AMF, and the AMF forwards the feedback information to the AF via the SMF, PCF, and TSCTSF.

[0172] refer to Figures 4 to 8 The described method enables determination of preferred UL burst timing information.Since a typical TDD mode has more DL timeslots than UL timeslots, this has a greater impact on the delay of the UL flow than the DL flow.

[0173] This approach does not impact RAN protocols and minimizes the impact on 5GC protocols by utilizing containers specific to time-sensitive communications.

[0174] The device may include at the entity: a component for determining burst timing information of at least one uplink periodic service flow for an application at an uplink ingress node, a component for determining feedback information based on the burst timing information and radio access network RAN ​​information, and a component for providing feedback information to a function associated with the application.

[0175] It should be understood that the apparatus may include or be coupled to other units or modules for transmission and / or reception, such as a radio part or a radio head, etc. Although the apparatus has been described as one entity, the different modules and memories may be implemented in one or more physical or logical entities.

[0176] It should be noted that although some embodiments have been described in relation to 5G networks, similar principles may be applied to other related networks and communication systems. Therefore, although certain embodiments are described above by way of example with reference to certain example architectures for wireless networks, technologies and standards, the embodiments may be applied to any other suitable form of communication system in addition to the communication system shown and described herein.

[0177] It is also noted herein that while example embodiments are described above, various changes and modifications may be made to the disclosed scheme without departing from the scope of the present invention.

[0178] Generally, various embodiments may be implemented in hardware or dedicated circuit systems, software, logic, or any combination thereof. Some aspects of the present disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the present disclosure may be illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be fully understood that, as non-limiting examples, the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0179] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0180] (a) hardware circuit implementation only (such as implementation of analog and / or digital circuitry only), and

[0181] (b) a combination of hardware circuitry and software such as (where applicable):

[0182] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0183] (ii) any portion of a hardware processor(s) with software (including digital signal processor(s), software, and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions), and (c) hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), that requires software (e.g., firmware) to operate, but may be absent when not required for operation.

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

[0185] Embodiments of the present disclosure may be implemented by computer software executed by a data processor of a mobile device (such as in a processor entity), or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products) include software routines, applets and / or macros that can be stored in a data storage medium of any readable device, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform an embodiment when the program is run. One or more computer executable components may be at least one set of software code or a portion thereof.

[0186] Furthermore, it should be noted in this regard that any logic flow blocks shown in the figures may represent program steps, or interconnected logic circuits, boxes and functions, or combinations of program steps and logic circuits, boxes and functions. The software may be stored on physical media (such as memory chips, or memory blocks implemented within a processor), on magnetic media (such as hard disks or floppy disks), and on optical media (such as, for example, DVDs and their data variants, CDs). The physical media is non-transient media.

[0187] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.

[0188] Embodiments of the present disclosure may be practiced in various components, such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available to convert a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0189] The scope of protection sought by various embodiments of the present disclosure is set forth by the independent claims. Embodiments and features described in this specification that do not belong to the scope of the independent claims (if any) should be interpreted as helping to understand various examples of the present disclosure.

[0190] The foregoing description has provided a complete and informative description of exemplary embodiments of the present disclosure by way of non-limiting examples. However, when read in conjunction with the accompanying drawings and the appended claims, various modifications and adjustments may be apparent to those skilled in the relevant art in view of the foregoing description. However, all such and similar modifications of the teachings of the present disclosure will still fall within the scope of the present invention as defined in the appended claims. In fact, there are additional embodiments that include a combination of one or more embodiments with any other embodiments previously discussed.

Claims

1. An apparatus comprising means for: At an uplink ingress node, determining burst timing information for at least one uplink periodic traffic flow of an application; Determining feedback information based on the burst timing information and the radio access network RAN ​​information; as well as The feedback information is provided to a function associated with the application.

2. The apparatus according to claim 1, wherein the entity comprises: A RAN node, and said means for determining said burst timing information, said means for determining said burst timing information comprising means for receiving said burst timing information from said uplink ingress node via a time sensitive communication time synchronization function.

3. The device according to claim 2, comprising: Means for receiving said burst timing information in time sensitive communications assistance information from a session management function.

4. The apparatus according to any one of claims 2 or 3, wherein the uplink ingress node is configured to observe the burst timing information through instructions from the time-sensitive communication time synchronization function.

5. The apparatus of claim 1, wherein the entity comprises: A time sensitive communication time synchronization function, and said means for determining said burst timing information, said means for determining said burst timing information comprising: means for receiving said burst timing information from said uplink ingress node.

6. The device according to claim 5, comprising: Means for receiving said burst timing information using a port management information container.

7. The device according to any one of claims 5 or 6, comprising: Means for providing an indication to said uplink ingress node to observe said burst timing information.

8. The device according to any one of claims 5 to 7, comprising: Means for receiving, at said entity, said RAN information from a RAN node.

9. The apparatus of claim 1, wherein the entity comprises: The uplink ingress node, and the means for determining the burst timing information, the means comprising: means for observing the burst timing information.

10. The device according to claim 9, comprising: Means for providing the feedback information to the function associated with the application using a port management information container.

11. The apparatus according to claim 9, comprising: Means for providing said feedback information to said function associated with said application via an access and mobility management function.

12. The device according to claim 11, comprising: Means for providing said feedback information to said access and mobility management function using non-access stratum session management signaling.

13. The device according to any one of claims 9 to 12, comprising: Means for receiving an indication at said entity to observe said burst timing information, and determining feedback information based on said observed burst timing information.

14. An apparatus according to claim 4, 7 or 13, wherein a port management information container includes the indication.

15. The apparatus of claim 4, 7, 13 or 14, wherein the indication comprises at least one of: an indication of the uplink periodic traffic flow, and a measurement configuration.

16. The apparatus according to any one of claims 1 to 15, wherein the burst timing information comprises at least one of the following: burst periodicity, absolute burst arrival time, burst arrival time variation, and offset time to a configured scheduling grant.

17. The apparatus according to any one of claims 1 to 16, wherein the RAN information comprises at least one of: RAN configuration, and RAN node burst arrival time preference.

18. The apparatus according to any one of claims 1 to 17, wherein the uplink ingress node comprises: User equipment, or device-side time-sensitive network converter.

19. The apparatus according to any one of claims 1 to 18, wherein the feedback information comprises: Preferred uplink burst timing information.

20. A method comprising, at an entity: At an uplink ingress node, determining burst timing information for at least one uplink periodic traffic flow of an application; Determining feedback information based on the burst timing information and the radio access network RAN ​​information; as well as The feedback information is provided to a function associated with the application.

21. An apparatus comprising: at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus at the entity to at least: At an uplink ingress node, determining burst timing information for at least one uplink periodic traffic flow of an application; Determining feedback information based on the burst timing information and the radio access network RAN ​​information; as well as The feedback information is provided to a function associated with the application.

22. A computer-readable medium comprising: Program instructions for causing the apparatus to perform at least the following at the entity: At an uplink ingress node, determining burst timing information for at least one uplink periodic traffic flow of an application; Determining feedback information based on the burst timing information and the radio access network RAN ​​information; as well as The feedback information is provided to a function associated with the application.

Images