Patent Application
20250211537
The embodiments herein relate to network nodes and methods for traffic steering policies in a wireless communications network. A corresponding computer program and a computer program carrier are also disclosed.
In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and/or User Equipments (UE), communicate via a Local Area Network such as a Wi-Fi network or a Radio Access Network (RAN) to one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cell areas. Each service area or cell area may provide radio coverage via a beam or a beam group. Each service area or cell area is typically served by a radio access node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in 5G. A service area or cell area is a geographical area where radio coverage is provided by the radio access node. The radio access node communicates over an air interface operating on radio frequencies with the wireless device within range of the radio access node.
Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (4G) network, have been completed within the 3rd Generation Partnership Project (3GPP). A Fifth Generation (5G) network also referred to as 5G New Radio (NR) has also been specified and work is now directed to further specifications of the 5G network. This work will continue in the coming 3GPP releases.
As a reference, the EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN/LTE is a variant of a 3GPP radio access network wherein the radio access nodes are directly connected to the EPC core network rather than to RNCs used in 3G networks. In general, in E-UTRAN/LTE the functions of a 3G RNC are distributed between the radio access nodes, e.g. eNodeBs in LTE, and the core network. As such, the RAN of an EPS has an essentially “flat” architecture comprising radio access nodes connected directly to one or more core networks, i.e. they are not connected to RNCs. To compensate for that, the E-UTRAN specification defines a direct interface between the radio access nodes, this interface being denoted the X2 interface.
For wireless communication systems pursuant to 3GPP Evolved Packet System, (EPS), also referred to as Long Term Evolution, LTE, or 4G, standard specifications, such as specified in 3GPP TS 36.300 and related specifications, the access nodes 103-104 corresponds typically to Evolved NodeBs (eNBs) and the network node 106 corresponds typically to either a Mobility Management Entity (MME) and/or a Serving Gateway (SGW). The eNB is part of the radio access network 10, which in this case is the E-UTRAN (Evolved Universal Terrestrial Radio Access Network), while the MME and SGW are both part of the EPC (Evolved Packet Core network). The eNBs are inter-connected via the X2 interface, and connected to EPC via the S1 interface, more specifically via S1-C to the MME and S1-U to the SGW.
For wireless communication systems pursuant to 3GPP 5G System, 5GS (also referred to as New Radio, NR, or 5G) standard specifications, such as specified in 3GPP TS 38.300 and related specifications, on the other hand, the access nodes 103-104 corresponds typically to an 5G NodeB (gNB) and the network node 106 corresponds typically to either an Access and Mobility Management Function (AMF) and/or a User Plane Function (UPF). The gNB is part of the radio access network 10, which in this case is the NG-RAN (Next Generation Radio Access Network), while the AMF and UPF are both part of the 5G Core Network (5GC). The gNBs are inter-connected via the Xn interface, and connected to 5GC via the NG interface, more specifically via NG-C to the AMF and NG-U to the UPF.
To support fast mobility between NR and LTE and avoid change of core network, LTE eNBs may also be connected to the 5G-CN via NG-U/NG-C and support the Xn interface. An eNB connected to 5GC is called a next generation eNB (ng-eNB) and is considered part of the NG-RAN. LTE connected to 5GC will not be discussed further in this document; however, it should be noted that most of the solutions/features described for LTE and NR in this document also apply to LTE connected to 5GC. In this document, when the term LTE is used without further specification it refers to LTE-EPC.
AF represents external trusted or non-trusted functions integrated in the operator network to interact with 5GC. The AF is part of the 5GC architecture and uses the mechanisms and interfaces specified for 5GC and OAM.
The Policy Control function (PCF) supports different functionality, e.g. unified policy framework to govern network behavior, provides policy rules to Control Plane function(s) to enforce them, and accesses subscription information relevant for policy decisions in a Unified Data Repository (UDR).
The Session Management function (SMF) supports different functionalities, e.g. SMF receives Policy Charging and Control (PCC) rules from the PCF and configures the UPF accordingly.
SMF is the network function that has the information of which UPFs conform the user Protocol Data Unit (PDU) Session, and with which role (PDU Session Anchor, Branching Point, ULCL), and to which Data Network (DN) Access (or Data Network Access Identifier (DNAI)) they are steering the traffic to among other. The DNAI is an identifier of the Access to the DN when access has been distributed, e.g. for edge computing.
The User Plane function (UPF) supports handling of user plane traffic based on the rules received from the SMF, e.g. packet inspection and different enforcement actions such as QoS handling.
Existing API enables an AF to influence traffic routing indirectly using a routing profile IDs within ‘Routing to Location’ element that may refer to a pre-agreed policy between the AF and the 5GC. The PCF(s) transform(s) the AF requests into PCC Rules that apply to PDU Sessions. This is further described e.g. in 3GPP TS 23.501 v17.4.0 “System Architecture for the 5G System; Stage 2” (clause 5.6.7) and 3GPP TS 29.514 v17.4.0 “5G System; Policy Authorization Service; Stage 3” in the Npcf_PolicyAuthorization Service (clause 4.2.2.8/4.2.3.8) and 3GPP TS 29.522 v17.5.0 “5G System; Network Exposure Function Northbound APIs” (clause 4.4.7). AF requests are sent to the PCF via N5 or via a Network Exposure Function (NEF) if non-trusted AF. If the AF request does not refer to a specific ongoing IP session, and instead e.g. refers to a group of UEs, the information provided by the AF is stored in UDR.
RouteToLocation element that finally shall be processed by PCF is described corresponding API and copied here:
When the Traffic Influence API is used today, the PCF maps the routing information (e.g. Routing Profile IDs) received from AF to a RouteToLocation parameters provided in the PCC Rule. This is further described in 3GPP TS 23.503 “Policy and Charging Control Framework for the 5G System” (AF incluenced Traffic Steering Enforcement control).
However, a problem is that the mapping between a profile information and the traffic steering policy only refer to a single Traffic Steering Policy without considering the specific traffic direction (UL or DL) so it cannot be used for asymmetric Service Function Chaining (SFC) where uplink and downlink paths differs.
An object of embodiments herein may be to obviate some of the problems related to influencing traffic routing.
Embodiments herein introduce explicit Traffic Steering policies for uplink and/or downlink when there is a need for the AF to influence 5GC routing. Thus, embodiments herein may provide a solution for enhancing an AF's influence on traffic routing with explicit uplink and/or downlink traffic steering identifiers. For example:
According to an aspect of embodiments herein, the object is achieved by a method, performed by a first network node implementing an AF in a wireless communications network for influencing traffic routing associated with a wireless communications device in the wireless communications network, the method comprises:
transmitting, to a second network node implementing a network exposure function of the wireless communications network or to a third network node implementing a policy and charging function of the wireless communications network, a request to influence the traffic routing associated with the wireless communications device, wherein the request includes an indication of a traffic steering policy for a specific traffic on a specific user session associated with the wireless communications device.
The indication of the traffic steering policy request may include an indication of a first traffic steering policy for uplink traffic and/or a second traffic steering policy for downlink traffic.
The specific user session associated with the wireless communications device may be a user PDU session.
According to a second aspect of embodiments herein, the object is achieved by a first network node implementing an AF in a wireless communications network. The first network node is configured for influencing traffic routing associated with a wireless communications device in the wireless communications network. The first network node is further configured for performing the method according to the first aspect above.
According to a third aspect of embodiments herein, the object is achieved by a method, performed by a second network node implementing a NEF in a wireless communications network, for influencing traffic routing associated with a wireless communications device in the wireless communications network, the method comprises:
The specific user session associated with the wireless communications device may be a user PDU session.
According to a fourth aspect of embodiments herein, the object is achieved by a second network node implementing a NEF in a wireless communications network. The second network node is configured for influencing traffic routing associated with a wireless communications device in the wireless communications network. The second network node is further configured for performing the method according to the third aspect above.
According to a fifth aspect of embodiments herein, the object is achieved by a method, performed by a third network node implementing a PCF in a wireless communications network, for influencing traffic routing associated with a wireless communications device in the wireless communications network, the method comprises:
The specific user session associated with the wireless communications device may be a user PDU session.
According to a sixth aspect of embodiments herein, the object is achieved by a third network node implementing a PCF in a wireless communications network. The third network node is configured for influencing traffic routing associated with a wireless communications device in the wireless communications network. The third network node is further configured for performing the method according to the fifth aspect above.
According to a further aspect, the object is achieved by a computer program comprising instructions, such as computer readable code units, which when executed by a processor of a network node, causes the network node to perform actions according to any of the aspects above.
According to a further aspect, the object is achieved by a carrier comprising the computer program of the aspect above, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.
Since the request to influence the traffic routing associated with the wireless communications device includes an indication of the traffic steering policy for the specific traffic, such as DL or UL traffic, on the specific user session associated with the wireless communications device the request may be used for asymmetric SFC where for example uplink and downlink paths differs.
In the figures, features that appear in some embodiments are indicated by dashed lines.
The various aspects of embodiments disclosed herein, including particular features and advantages thereof, will be readily understood from the following detailed description and the accompanying drawings, in which:
As mentioned above, there are challenges and issues with how to influence traffic routing.
An object of embodiments herein is therefore to improve methods for influencing traffic routing.
Embodiments herein provide mechanisms for an AF to influence directly on uplink and downlink traffic steering policies associated to a specific UE, target group of UEs, and specific flow per specific DNAI.
Embodiments herein have the following advantages:
Embodiments herein relate to communication networks in general, and specifically to wireless communication networks.
Access nodes operate in the wireless communications network 100 such as a radio access node 111. The radio access node 111 provides radio coverage over a geographical area, a service area referred to as a cell 115, which may also be referred to as a beam or a beam group of a first radio access technology (RAT), such as 5G, LTE, Wi-Fi or similar. The radio access node 111 may be a NR-RAN node, transmission and reception point e.g. a base station, a radio access node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a gNB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of communicating with a wireless device within the service area depending e.g. on the radio access technology and terminology used. The respective radio access node 111 may be referred to as a serving radio access node and communicates with a UE with Downlink (DL) transmissions on a DL channel 123-DL to the UE and Uplink (UL) transmissions on an UL channel 123-UL from the UE.
A number of wireless communications devices operate in the wireless communication network 100, such as a UE 121.
The UE 121 may be a mobile station, a non-access point (non-AP) STA, a STA, a user equipment and/or a wireless terminal, that communicate via one or more Access Networks (AN), e.g. RAN, e.g. via the radio access node 111 to one or more core networks (CN) e.g. comprising a first CN node 131, for example implementing an AF. The CN may further comprise second CN node 132, for example implementing a NEF. The CN may further comprise third CN node 133, for example implementing a PCF.
It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.
In scenarios related to embodiments herein the AF may influence traffic routing in 5GC.
In scenarios related to embodiments herein the PCF is the receiver, directly or through the UDR, or the NEF, of AF information to influence traffic routing in 5GC.
In scenarios related to embodiments herein the SMF may receive dynamic PCC rules from the PCF with traffic routing information or traffic steering policies for uplink and downlink. It also may hold pre-defined PCC rules with pre-configured traffic steering policies (TSP) for uplink and downlink.
In scenarios related to embodiments herein the UPF may receive forwarding parameters specifying the policy to follow when a Packet Detection Rule (PDR) is matched. That is, in both directions uplink and downlink parameters shall be specified in different PDRs.
Embodiments herein are based on the following:
Thus, the AF may add the new elements in a message comprising routing influencing information. The message may be sent using an API.
1. a The AF may use an API, such as Nnef_TrafficInfluence API, to influence how to route a specific traffic on a specific user session, such as a PDU session, by providing a UE IP address together with the request. The AF may include Traffic Steering Policy IDs, identifying specific traffic steering policies such as a specific traffic steering policy for DL and/or a specific traffic steering policy for UL, in the request.
1.b The NEF identifies the PCF serving the PDU Session and triggers an Npcf_PolicyAuthorization Request, for example as described in 3GPP TS 23.502 v17.4.0 “Procedures for the 5G system, Stage 2”, clause 4.3.6.4.
2. a AF may use Nnef_TrafficInfluence API to influence how to route a specific traffic for a UE or a group of UEs, by providing UE ID such as a Generic Public Subscription Identifier (GPSI) or External Group ID together with the request. 5G System supports management of 5G Virtual Network (VN) Group identification and membership (i.e. definition of 5G VN group identifiers and membership) and 5G VN Group data (i.e. definition of 5G VN group data). The 5G VN Group management may be configured by a network administrator or may be managed dynamically by AF.
A 5G VN group may comprise of a set of UEs using private communication for 5G LAN-type services and is characterized by the following:
5G VN group identities: External Group ID and Internal Group ID are used to identify the 5G VN group.
The AF may include Traffic Steering Policy IDs, such as DL TSP ID and/or UL TSP ID, in the request.
2.b The NEF may store the information in the UDR, as described in 3GPP TS 23.502, clause 4.3.6.2.
2.c The UDR may provide the stored traffic steering information to the PCF, e.g., through an API Nudr_DataNotification.
3. The PCF uses TSP explicit request coming from AF and uses the TSP ID for UL and/or the TSP ID for DL in corresponding PCC rule(s). That is, the PCF transforms the TSP ID for UL and/or the TSP ID for DL into corresponding PCC rule(s).
4. The PCF may send PCC rule(s) to the SMF. The PCC Rule may comprise SDF Filters or Application ID and TSP IDs.
5. The SMF may send Packet Detection Rules, PDRs, information to identify the specific traffic and Forwarding Action Rules, FAR, with forwarding policies according to the TSP ID for UL and/or TSP ID for DL to request the UPF to forward the specific traffic according to these TSPs
6. UPF may apply the PDRs and specific forwarding policies based on TSP ID. User data traffic will at some point in time arrive at the UPF which will forward the user data traffic to N6-LAN. N6 is a reference point between the UPF and the DN. N6-LAN is a Local Area Network (LAN) between the 5GC and a DN. In N6-LAN Service Functions (SFs), such as proxies and Network Address Translations (NATs) are deployed that rely on service function chaining technology to make sure specific traffic is steered through the right SFs.
Exemplifying methods according to embodiments herein will now be described with reference to a flow chart in
In action 601, the first network node 131 transmits, to a second network node 132 implementing a network exposure function of the wireless communications network 100, a request to influence the traffic routing associated with the wireless communications device 121. The request includes a traffic steering policy for a specific traffic on a specific user session associated with the wireless communications device 121.
The indication of the traffic steering policy may include an indication of a first traffic steering policy for uplink traffic and/or a second traffic steering policy for downlink traffic. In some embodiments herein the indication of the traffic steering policy includes identifiers of the traffic steering policy. For example, the indication of the traffic steering policy may include TSP IDs, such as DL TSP ID and/or UL TSP ID, in the request.
The specific user session associated with the wireless communications device 121 may be a user PDU session.
The indication of the traffic steering policy may be associated to a specific UE, target group of UEs, and specific flow per specific DNAI.
In some embodiments herein the request to the second network node 132 or the third network node 133 further includes a network address of the wireless communications device 121 or includes a network public identity of the wireless communications device 121 or of a group of wireless communications devices 121.
The indication of the traffic steering policy for the specific traffic on the specific user session may be specific to an access to a DN identified by the DNAI in the request.
Exemplifying methods according to embodiments herein will now be described with reference to a flow chart in
The method actions of
In action 701 the second network node 132 receives, from the first network node 131, implementing the AF in the wireless communications network 100, a request to influence the traffic routing associated with the wireless communications device 121. The request includes a traffic steering policy for the specific traffic on the specific user session associated with the wireless communications device 121.
For example, the indication of the traffic steering policy may include TSP IDs, such as DL TSP ID and/or UL TSP ID, in the request.
The indication of the traffic steering policy may be associated to a specific UE, target group of UEs, and specific flow per specific DNAI.
In action 702 the second network node 132 transmits, to the third network node 133, implementing the policy and charging function of the wireless communications network, the received traffic steering policy for the specific traffic on the specific user session associated with the wireless communications device 121.
Exemplifying methods according to embodiments herein will now be described with reference to a flow chart in
The method actions of
In action 801 the third network node 133 receives, from the second network node 132, a traffic steering policy for the specific traffic on the specific user session associated with the wireless communications device 121.
In action 802 the third network node 133 creates a PCC rule based on the traffic steering policy for the specific traffic on the specific user session.
For example, the third network node 133 may use a TSP explicit request coming from the first network node 131 and use the TSP ID for UL and/or the TSP ID for DL to create corresponding PCC rule(s). The third network node 133 may send the PCC rule(s) to the SMF.
Embodiments herein provide a solution to the problems mentioned above by enhancing the AF's influence on traffic steering by adding traffic steering policies for specific traffic. Thus, embodiments herein enable the AF to request predefined SFC for traffic flow(s) related with target UE(s). Thus, the AF may influence with explicit traffic steering policies per flow.
In order to fulfill uplink and downlink different traffic steering policies using AF routing influence directly, new elements may be added in the interface so that UL and DL traffic steering policies may be provided for the specific traffic and traffic direction.
The PCF shall check and apply the request. The required PCC rules are provisioned to include or modify traffic steering policies for UL and DL traffic steering according to what has been required from AF directly or through NEF.
In some embodiments herein the PCC rule either indicates traffic steering or N6 traffic routing, but not both simultaneously. Therefore, in order to not impact further in PCF, SMF and UPF, a proposal is to add new traffic steering rules for DL and UL in a mutually exclusive way with current routing info and/or routing profile ID.
This solution thus proposes to add UL Traffic Steering Policy ID and DL Traffic Steering Policy ID to the existing Nnef_TrafficInfluence and NpcfPolicyAutorization, Nudr_DataNotification. The AF request may either contain UL and DL AF-TSP IDs, or just one if any of the direction does not require any steering policy, for Service Chaining or Traffic Routes for steering to a local DN, but not both Service Chaining and Traffic Routes for steering to the local DN. PCF may use AF-TSP IDs directly or maps to local defined TSP ID provided to the SMF in the PCC Rule to avoid the AF to know how TSP ID are set in the 5GC and therefore isolate it from system configuration changes, i.e. the TSP IDs configured in the 5GC may be modified without impacting the UL Traffic Steering Policy ID and DL Traffic Steering Policy ID that the AF uses (AF-TSP IDs).
AF: Support of providing new information in the Nnef_TrafficInfluence API, to provide explicitly UL and DL traffic steering policy, such as AF-TSPs, in its requests or only one of them.
NEF: Support of new information in the Nnef_TrafficInfluence API, and pass it to UDR and PCF.
UDR: Supports storage of AF-TSP IDs in the AF influence on routing parameters.
PCF: Accepts new information and uses it or maps to local TSP defined, as traffic steering policies associated to the PCC rule(s) impacted.
The first network node 131, the second network node 132 and the third network node 133 may comprise a respective input and output interface, IF, 906, 1006, 1106 configured to communicate with each other, see
The first network node 131, the second network node 132 and the third network node 133 may further comprise a respective receiving unit 910, 1010, 1110, and transmitting unit 920, 1020, 1120, see
The third network node 133 may further comprise a creating unit 1130 which for example may create a PCC rule based on the traffic steering policy for the specific traffic on the specific user session. For example, the third network node 133 and/or the creating unit 1130 may be configured to use a TSP explicit request coming from the first network node 131 and use the TSP ID for UL and/or the TSP ID for DL to create corresponding PCC rule(s).
The third network node 133 may further be configured to create the PCC rule by being configured to map the routing information, e.g. Routing Profile IDs, received from the first network node 131, to the RouteToLocation parameters provided in the PCC Rule.
The embodiments herein may be implemented through a respective processor or one or more processors, such as the respective processor 904, 1004, and 1104, of a processing circuitry in the first network node 131, the second network node 132 and the third network node 133 and depicted in
The first network node 131, the second network node 132 and the third network node 133 may further comprise a respective memory 902, 1002, and 1102 comprising one or more memory units. The memory comprises instructions executable by the processor in the first network node 131, the second network node 132 and the third network node 133.
Each respective memory 902, 1002 and 1102 is arranged to be used to store e.g. information, data, configurations, and applications to perform the methods herein when being executed in the respective first network node 131, the second network node 132 and the third network node 133.
The first network node 131 is configured to transmit, to the second network node 132 implementing the network exposure function of the wireless communications network 100 or to the third network node 133 implementing the policy and charging function of the wireless communications network 100, the request to influence the traffic routing associated with the wireless communications device 121. The request includes the indication of the traffic steering policy for the specific traffic on the specific user session associated with the wireless communications device 121. The specific user session associated with the wireless communications device 121 may be a user PDU session.
The first network node 131 and/or the processor 904 may be configured to include the indication of the first traffic steering policy for uplink traffic and/or the second traffic steering policy for downlink traffic in the indication of the traffic steering policy.
In some embodiments the first network node 131 and/or the processor 904 is configured to include the identifiers of the traffic steering policy in the indication of the traffic steering policy.
The first network node 131 and/or the processor 904 may be configured to include the network address of the wireless communications device 121 or the network public identity of the wireless communications device 121 or of the group of wireless communications devices in the 121 request to the second network node (132) or the third network node (133).
The second network node 132 is configured to receive, from the first network node 131 implementing the AF in the wireless communications network 100, the request to influence the traffic routing associated with the wireless communications device 121. The request includes the indication of the traffic steering policy for the specific traffic on the specific user session associated with the wireless communications device 121.
The second network node 132 is further configured to transmit, to the third network node 133 implementing the policy and charging function of the wireless communications network 100 or to the UDR 503 the received indication of the traffic steering policy for the specific traffic on the specific user session associated with the wireless communications device 121.
The third network node 133 is configured to receive, from the first network node 131 or from the second network node 132 or from the UDR, the indication of the traffic steering policy for the specific traffic on the specific user session associated with the wireless communications device 121.
The third network node 133 and/or the processor 1104 is further configured to create the PCC rule based on the indication of the traffic steering policy for the specific traffic on the specific user session.
The second network node 132 and the third network node 133 are each configured to receive the first traffic steering policy for uplink traffic and/or the second traffic steering policy for downlink traffic included in the received indication of the traffic steering policy.
In some embodiments, a respective computer program 903, 1003 and 1103 comprises instructions, which when executed by the at least one processor, cause the at least one processor of the respective first network node 131, the second network node 132 and the third network node 133 to perform the actions above. The respective computer program 903, 1003 and 1103 may be loaded into the respective memory 902, 1002, and 1102.
In some embodiments, a respective carrier 905, 1005 and 1105 comprises the respective computer program, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.
Those skilled in the art will also appreciate that the units described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the respective wireless communications device 601 and network node 602, that when executed by the respective one or more processors such as the processors described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).
With reference to
The telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220. The intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown).
The communication system of
Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230. Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to
The communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330. The hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in
The communication system 3300 further includes the UE 3330 already referred to. Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located. The hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338. The software 3331 includes a client application 3332. The client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310. In the host computer 3310, an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the user, the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 may transfer both the request data and the user data. The client application 3332 may interact with the user to generate the user data that it provides. It is noted that the host computer 3310, base station 3320 and UE 3330 illustrated in
In
The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime.
A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 3350 between the host computer 3310 and UE 3330, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer's 3310 measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.
When using the word “comprise” or “comprising” it shall be interpreted as non-limiting, i.e. meaning “consist at least of”.
The embodiments herein are not limited to the above described preferred embodiments. Various alternatives, modifications and equivalents may be used.
| Number | Date | Country | Kind |
|---|---|---|---|
| 22382300.6 | Mar 2022 | EP | regional |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/SE2023/050271 | 3/27/2023 | WO |
