Patent Application
20240275829
The embodiments herein relate to methods for upgrading a first data session for a first media type to handle a second media type and network nodes and a communications device implementing the methods in a communications network. A corresponding computer program and 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, which may also be referred to as a beam or a beam group, with each service area or cell area being 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) and this work continues in the coming 3GPP releases, for example to evolve the specifications of the Fifth Generation (5G) network also referred to as 5G New Radio (NR). 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 communications systems pursuant to the 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 of
The AN 203 may further comprise an Access Gateway (AGW) (not shown in
To support fast mobility between NR and LTE and avoid change of core network, LTE eNBs can 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.
The IMS is a standardized architectural framework for delivering IP-based multimedia services. Historically, mobile phones have provided voice call services over a circuit-switched-style network, rather than strictly over an IP packet-switched network. However, now alternative methods of delivering voice, e.g., Voice over IP (VoIP), or other multimedia services have become available. VoIP over a 5G network may also be referred to as Vo5G or Voice over NR (VoNR).
A Proxy Call Session Control Function (P-CSCF) in the role of the AF 220 may interact with the Policy and Charging Architecture of the 5GC, for example with a Policy and Charging Function (PCF) 206d. The P-CSCF may be a first contact point within the IP Multimedia Core Network (IM CN) subsystem and it may ensure that relevant Session Initiation Protocol (SIP) messages contain the correct or up to date information about a user location information of the UE 12 provided by the access network 203 currently used by the UE 12.
The 5G System architecture supports an N5 interface between the PCF 206d and the P-CSCF and also supports an Rx interface between the PCF 206d and the P-CSCF, to enable IMS service. Rx support between the PCF 206d and the P-CSCF may be needed for backwards compatibility for early deployments using Diameter between the IMS and the 5GC functions.
The PCF 206d supports a unified policy framework to govern the network behavior. Specifically, the PCF 206d may provide Policy and Charging Control (PCC) rules to a Session Management Function (SMF) 206c together with an authorized Quality of Service (QoS) to be enforced by the SMF 206c. Further, the PCF 206d may request access network information, including user location information, from the SMF 206c and reports the received access network information, including the user location information, to the P-CSCF.
The SMF 206c supports different functionalities. Specifically, the SMF 206c may receive PCC rules from the PCF 206d over an N7 interface, enforce the authorized QoS and report the access network information to the PCF 206d as mentioned above. Further, the SMF 206c may have an N4 interface to the UPF 206b.
The IMS may further comprise a multimedia application server, such as a Multimedia Telephony Application Server (MTAS).
The IMS may further comprise other types of CSCFs, e.g., a Serving CSCF (S-CSCF) and an Interrogating CSCF (I-CSCF).
Virtual Reality (VR) is gaining more appeal among users due to its power of illustration among other things. Today, IMS is only setup for voice channels with limited bandwidth. The access network is also be restricted accordingly.
Thus, if a user wants to add VR to an ongoing voice call this will be problematic due to the limited bandwidth of the voice channel.
An object of embodiments herein may be to obviate some of the problems related to handling multiple media types during a communications session, or at least reduce the impact of them. For example, a specific object of embodiments herein may be to enable an upgrade of a data session, such as a Protocol Data Unit (PDU) session for IMS, for a first media type, such as voice, to handle a second media type, such as VR.
In embodiments herein the UEs are informed of what needs to be done in order to successfully either establish a new data session for the second media type, such as a VR IMS session, or upgrade the ongoing data session for the first media type, such as a normal IMS voice session, to handle the second media type as an add on mid-ongoing session.
According to a first aspect, the object is achieved by method for upgrading a first data session for a first media type to handle a second media type. The data session may be a multimedia session or be associated with a multimedia session, for example an IMS session. Thus in embodiments herein the data session may also be referred to as a service session. Thus, embodiments herein also describe methods for upgrading a first service session, such as a first IMS session, for a first media type to handle a second media type. For example, the first service session may be replaced by a second upgraded service session, such as a second IMS session, which handles the second media type. Each service session may be established over a respective PDU session.
The method comprises transmitting, by an application node associated with a communications network, to a policy controlling node of the communications network, a request for a first identifier of a first network slice of the communications network. The first network slice is used to set up the first data session to a communications device. Specifically, the data session may be set up between a first communications device, e.g., on an originating side of the data session, and a second communications device, e.g., on a terminating side of the data session.
The method further comprises receiving, by the application node, the first identifier of the first network slice from the policy controlling node in response to the transmitted request for the first identifier.
The method further comprises forwarding, by the application node, the first identifier of the first network slice to a multimedia application server.
The method further comprises receiving, by the multimedia application server, a request from the first communications device to upgrade the first data session to handle a second media type, wherein the request to handle the second media type comprises session description information corresponding to an upgraded data session handling the second media type.
The method further comprises sending, by the multimedia application server, in response to the received request, and based on the first identifier of the first network slice and the session description information, an indication to the communications device that a second data session on a second network slice identified by a second identifier is required for the upgrade to handle the second media type to take place. The indication may be sent to the first or the second communications device.
According to a second aspect, the object is achieved by a method, performed by a multimedia application server, for upgrading a first data session for a first media type to handle a second media type. The data session may be a multimedia session, for example an IMS session.
The method comprises receiving, from an application node associated with a communications network, a first identifier of a first network slice of the communications network. The first data session is established by a communications device through the first network slice. Specifically, the data session may be set up between a first communications device, e.g., on an originating side of the data session, and a second communications device, e.g., on a terminating side of the data session.
The method further comprises receiving a request, from the first communications device to upgrade the first data session to handle a second media type, wherein the request comprises session description information corresponding to an upgraded data session handling the second media type. The request may be received from the first communications device or the second communications device.
The method further comprises sending, in response to the received request, and based on the first identifier of the first network slice and the session description information, an indication to the communications device that a second data session on a second network slice identified by a second identifier is required for the upgrade to handle the second media type to take place. The indication may be sent to the first or the second communications device.
According to a third aspect, the object is achieved by a multimedia application server. The multimedia application server is configured to perform the method according to the second aspect.
According to a fourth aspect, the object is achieved by a method, performed by a communications device, for upgrading a first data session of a first media type to handle a second media type, the method comprising:
According to a fifth aspect, the object is achieved by a communications device. The communications device is configured to perform the method according to the fourth aspect.
According to a sixth aspect, the object is achieved by a method, performed by an application node associated with a communications network, for assisting in upgrading a first data session for a first media type to handle a second media type. The method comprising:
According to a seventh aspect, the object is achieved by an application node. The application node is configured to perform the method according to the sixth aspect.
According to an eighth aspect, the object is achieved by a method, performed by a policy controlling node of a communications network. The method comprises:
Receiving, from an application node associated with the communications network, a request for a first identifier of a first network slice of the communications network. The first network slice is used for a first data session between a first communications device and a second communications device; and
According to a ninth aspect, the object is achieved by a policy controlling node. The policy controlling node is configured to perform the method according to the sixth aspect.
According to a further aspect, the object is achieved by a computer program comprising instructions, which when executed by a processor, causes the processor to perform actions according to any of the aspects above.
According to a yet 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 multimedia application server sends the indication to the communications device that the second data session on the second network slice is required for the upgrade in response to the request for the upgrade, and based on the first identifier of the first network slice and the session description information, the upgrade is enabled.
A further advantage of embodiments herein is that they enable upgrading the data session to handle second media types requiring higher bandwidth than the first media type. For example, the first media type may be voice, while the second media type may be used for providing video conferencing with multiple users or virtual reality.
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, an object of embodiments herein may be to obviate some of the problems related to upgrading an IMS session in connection with a service provided by a communications network. The service may for example be a voice service.
For example, if a user wants to add VR to an ongoing voice call this will be problematic due to the limited bandwidth of the voice channel. Thus, an object of embodiments herein may be to obviate some of the problems related to handling multiple media types requiring substantially different network performance and resources during a communications session.
In embodiments herein communications devices, such as UEs, are informed of what needs to be done in order to successfully either establish a new data session for the second media type, such as a VR IMS session, or upgrade the ongoing data session for the first media type, such as a normal IMS voice session, to handle the second media type as an add on mid-ongoing session.
In embodiments herein the IMS domain acquires information about the network slice, e.g., as identified by the Single Network Slice Selection Assistance Information (S-NSSAI), used for a PDU IMS session, that is a PDU session for IMS services. This enables the IMS domain to decide whether an IMS session may be upgraded to handle VR or not. The IMS domain is configured with the S-NSSAIs that identify network slices that are able to handle VR. The IMS domain is therefore able to check whether or not the currently used S-NSSAI used is adequate for VR as well.
With the above in mind, embodiments herein propose that the MTAS acquires the S-NSSAI used for the PDU session for IMS, e.g., during IMS session setup. This enables the MTAS to decide on the appropriate action if a UE for example initiates a regular IMS session and wants to upgrade it mid-session to handle VR or initiates a VR session from the get-go, that is from the IMS session setup. Embodiments herein will be exemplified with the mid-session upgrade.
The MTAS instructs the originating UE and the terminating UE if a new PDU IMS session with a new appropriate S-NSSAI is required or not.
If one of the UEs cannot establish a new PDU session for IMS because it does not have the correct subscription for the required S-NSSAI, it may reject the session or the request to upgrade the ongoing IMS session.
Embodiments herein relate to IMS and therefore a brief overview of a procedure for establishing an IMS session will first be given with reference to
Embodiments herein relate to communications networks in general.
Each CN of the first communications network 500a comprises one or more CN nodes, such as a first session management node 506c_a implementing the SMF 206c and a first policy controlling node 506d a implementing the PCF 206d. The first policy controlling node 506d_a may besides handling policies for resource reservation also handle charging. The first CN may further comprise a first access and mobility management node 506a_a implementing the AMF 206a and a first user plane node 506b_a implementing the UPF 206b. The SMF 206c, the PCF 206d, the AMF 206a and the UPF 206b were all described above in relation to
In a 4G-embodiment the first session management node 506c_a and the first access and mobility management node 506a_a may be implemented by a Mobility Management Entity (MME). The first user plane node 506b_a may be implemented by a Packet Data Network Gateway (PDN-GW) in 4G.
The CN nodes may be logical nodes for performing the above-mentioned CN functions which each may be implemented in one or more physical nodes or devices.
The first communications network 500a may be a wireless communications network, or a communications network supporting wireless and wireline convergence, such as 5G Wireless Wireline Convergence.
Then the first AN 503a may comprise one or more RANs. The wireless communications network may use a number of different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, 5G, New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations. Embodiments herein relate to recent technology trends that are of particular interest in a 5G context. However, embodiments are also applicable in further development of the existing wireless communications systems such as e.g. LTE.
Access nodes operate in the communications network 500 such as a radio access node. The radio access node provides radio coverage over a geographical area, a service area referred to as a cell, 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 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 may be referred to as a serving radio access node and communicates with a UE with Downlink (DL) transmissions to the UE and Uplink (UL) transmissions from the UE.
A number of communications devices operate in the communications network 500, such as a first communications device 512a. The first communications device 512a may correspond to the originating UE 12a of
The first AN 503a may be a Radio Access Network (RAN) corresponding to the radio access network 10 of
The second communications network 500b may be a wireless communications network or a communications network supporting wireless and wireline convergence, such as 5G Wireless Wireline Convergence.
A number of communications devices operate in the second communications network 500b, such as a second communications device 512b. The second communications device 512b may correspond to the terminating UE 12b of
In some embodiments the second communications network 500b is the same communications network as the first communications network 500a.
The second application network 520b comprises one or more application nodes, such as a second application node 521b and a second core application node 522b for providing a service for the second communications device 512b.
For example, the P-CSCF may be implemented by the first and the second application nodes 521a, 521b while an IMS core function, such as the S-CSCF, may be implemented by the first and second core application nodes 522a, 522b. In general, the one or more application nodes may be logical nodes for performing the above-mentioned application functions. Each application node may be implemented in one or more physical nodes or devices.
As mentioned above, the IMS further comprises a multimedia application server, such as a first multimedia application server 523a in the first application network 520a and a second multimedia application server 523b in the second application network 520b.
Generally, an application function interacts with the CN to provide specific services, such as voice, video, gaming, and VR, and may affect routing and/or policy decisions affecting quality of service. An example of an application function is IMS providing voice and video calling services. In embodiments herein the services may be real-time services providing real-time data, such as real-time media.
The service may be provided to the communications device 512a, 512b through the CN of the communications network 500a, 500b. For example, the service may be provided by a data session, such as a Protocol Data Unit (PDU) session. The data session provides end-to-end user plane connectivity between the communications device 512a, 512b and a specific Data Network 530a, 530b through the user plane node 506b_a, 506b_b. For example, for voice over IMS a PDU session for IMS voice may provide end-to-end user plane connectivity between the first communications device 512a and the second communications device 512b in the second communications network 500b.
A data session, such as a PDU Session, may support one or more QoS Flows. There may be a one-to-one mapping between QoS Flow and QoS profile. For example, for 5G the one-to-one mapping between QoS Flow and QoS profile means that all packets belonging to a specific QoS Flow may have the same 5Q1.
The session management node, such as the first session management node 506c_a, or the second session management node 506c_b may control the data session through the N4 interface.
It should be understood by the skilled in the art that “communications device” and “UE” are non-limiting terms which mean any terminal, wireless 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.
Methods herein may in a first aspect be performed by a multimedia application server, such as the first multimedia application server 523a or the second multimedia application server 523b, and in a second aspect by a communications device, such as the first or the second communication device 512a, 512b, and in a third aspect by an application node, such as the first and the second application node 521 a, 521b, and in a fourth aspect by a policy controlling node, such as the first or the second policy controlling node 506d_a, 506d_b. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a first cloud 540a as shown in
In the cloud implementation, the functions of anyone or all of the multimedia application server 523a, 523b, the communications device 512a, 512b, the application node 521a, 521b, and the policy controlling node 506d_a, 506d_b may be deployed in a virtualized environment. The signaling sequences between the nodes or functions does not change if some or all of them are deployed in the cloud.
Exemplifying methods for upgrading a first data session for a first media type to handle a second media type according to embodiments herein will now be described with reference to
The data session may also be referred to as a service session. Thus, embodiments herein describe methods for upgrading a first service session, such as a first IMS session, for a first media type to handle a second media type. For example, the first service session may be replaced by a second upgraded service session, such as a second IMS session, which handles the second media type. Each service session may be established over a respective PDU session.
The exemplifying methods will also be described with further reference to
The exemplifying methods disclosed in connection with
It is further assumed that the first communications network 500a represents the originating side and the second communications network 500b represents the terminating side. The following may be a description of actions in a call flow. Actions 701 to 703 are valid for both the originating side and the terminating side. Thus, both the first communications device 512a and the second communications device 512b perform these actions. However,
The communications devices 512a, 512b, such as the first communications device 512a and the second communications device 512b, may each register in 5GC, e.g., according to 3gpp TS 23.502 v. 17.1.0.
The communications device 512a, 512b may establish a default data session, such as a default PDU IMS session, i.e., a PDU session for IMS, e.g., in accordance with 3gpp TS 23.502 17.1.0.
The communications device 512a, 512b registers in IMS, e.g., according to 3gpp TS 23.228 17.1.0 and TS 24.229 17.3.1.
The communications device 512a, 512b initiates a dedicated service session over a dedicated data session, such as a dedicated PDU session for IMS, with another communications device 512a, 512b. For example, the first communications device 512a initiates a dedicated IMS session over a dedicated PDU session for IMS with the second communications device 512b based on end user activity.
The first communications device 512a initiates a dedicated service session over a dedicated PDU session for IMS towards the second communications device 512b by sending a session control message indicating a session initiation to the second communications device 512b. The session control message indicating the session initiation may also be referred to as a session initiation message. For example, the first communications device 512a initiates an IMS session towards the second communications device 512b by sending a SIP INVITE to the second communications device 512b according to 3gpp TS 24.229 v. 17.3.1.
The first application node 521 a may send an Npcf_PolicyAuthorisation_Subscribe to the first policy controlling node 506d_a to fetch the first identifier of the first network slice S-NSSAI_1a used for this IMS session. This may be done in response to the SIP INVITE message from the first communications device 512a.
The first identifier of the first network slice S-NSSAI_1a used is returned from the first policy controlling node 506d_a in the response in action 707.
The first application node 521 a inserts the first network slice identifier S-NSSAI_1 a used for the data session in the INVITE message to the first multimedia application server 523a.
The first application node 521 a forwards the first network slice identifier S-NSSAI_1a used for the first IMS session in the SIP INVITE message to the second application node 522a, such as an S-CSCF. The SIP INVITE message is transmitted to the first multimedia application server 523a.
The first multimedia application server 523a saves the S-NSSAI 1 used for the IMS session in the session state.
The first multimedia application server 512a may remove the S-NSSAI1 from the SIP INVITE message before forwarding the SIP INVITE message to a node in the second application network 520b, such as the terminating IMS network 520b.
In the terminating network 500b similar actions take place in the IMS nodes as in the originating network 500a.
Specifically, the second multimedia application server 523b at the terminating end may receive a SIP INVITE via the second application network 520b.
The second multimedia application server 523b may then forward the SIP INVITE to the second communications device 512b on the terminating side.
The UE sends a SIP 200 OK to the originating side.
When a SIP 200 OK sent from the second communications device 512b arrives at the second application node 521b at the terminating end in the second application network 520b, it fetches the first network slice identifier S-NSSAI_1 b used by the second communications device 512b from the second policy controlling node 506d_b, e.g. by sending an Npcf_PolicyAuthorisation_Subscribe as described in action 706 above.
The second application node 521b forwards the SIP 200 OK, and includes the first network slice identifier S-NSSAI_1b used by the second communications device 512b, to the second multimedia application server 523b.
Then the second multimedia application server 523b stores the first network slice identifier S-NSSAI_1b of the second communications device 512b in the IMS session state associated with the first IMS session of the second communications device 512b.
The second multimedia application server 523b strips the first network slice identifier S-NSSAI_1b from the SIP 200 OK before forwarding the SIP 200 OK onwards.
The IMS session between the first communication device 512a and the second communication device 512b is then established. Both the first multimedia application server 523a and the second multimedia application server 523b have stored the first network slice identifier S-NSSAI_1a, S-NSSAI_1b used by the first communications device 512a and the second communications device 512b respectively for establishing the PDU session for IMS. That is, the first multimedia application server 523a have stored the first network slice identifier S-NSSAI_1a of the first communications network (originating side), while the second multimedia application server 523b have stored the first network slice identifier S-NSSAI_1 b of the second communications network (terminating side).
At some later point in the IMS session the first communications device 512a decides to upgrade the first IMS session. For example, the first communications device 512a decides to add on VR to the IMS session, which requires a much larger bandwidth than voice.
The first communications device 512a issues a Re-INVITE message with a new Session Description Protocol (SDP) information reflecting the virtual reality session. This is forwarded all the way to first multimedia application server 523a.
The first multimedia application server 523a realizes that the first network slice identifier S-NSSAI_1a used by the first communications device 512a for establishing the PDU session for IMS is not applicable for this upgraded IMS session and a that a new second network slice identifier S-NSSAI_2a is required for VR. The first multimedia application server 523a may note that in the stored session state so that it may request the first communications device 512a (in the SIP response to be sent back to the first communications device 512a) to initiate a new PDU session for the upgraded IMS session.
In addition, the first multimedia application server 523a may inform the second communications device 512b at the terminating side that a new network slice is required at the originating side for the upgraded session, by inserting information in a SIP RE-INVITE information to that effect so that the second communications device 512b knows about this. Note that this is optional and has no impact on the second communications device 512b decision to whether or not the second communications device 512b should change network slices in the second communications network 500b to upgrade the IMS session.
The Re-INVITE information is sent from first multimedia application server 523a to the second application network 520b.
The Re-INVITE information is forwarded, e.g., via the second application node 521b, to the second multimedia application server 523b.
The second multimedia application server 523b may require that the second communications device 512b initiates a new PDU session for this upgraded IMS session. If the second multimedia application server 523b requires that the second communications device 512b initiates the new PDU session, it inserts to the second communications device 512b in the INVITE message information to that effect.
For example, the second multimedia application server 523b may include an indication that a second data session on the second network slice NS2a, NS2b identified by the second identifier S-NSSAI_2a, S-NSSAI_2b is required for the upgrade to handle the second media type to take place.
The indication may comprise a list of possible new network slice identifiers, which are configured in the second multimedia application server 523b, to be used by the second communications device 512b. The second communications device 512b should select a network slice identifier that it has in its access network subscription profile.
The second multimedia application server 523b forwards the modified SIP INVITE message to the second communications device 512b.
The second communications device 512b decides to accept the creation of a new second PDU session for IMS.
The second communications device 512b may accept the upgrade, or in other words the use of the second PDU session on the second network slice, by returning the SIP 200 OK message to the second application network 520b indicating that it will create the second PDU session for the new IMS session, such as a VR session.
The second multimedia application server 523b forwards the SIP 200 OK message from the second application network 520b to the first multimedia application server 523a. which may forward the message to the first communications network 500a, such as the originating side.
The first multimedia application server 523a forwards the message to the first communications network 500a, such as the originating side. The SIP 200 OK message arrives at the first multimedia application server 523a which may insert in the request to the first communications device 512a necessary information for the first communications device 512a to use a new PDU session for that new IMS session into the SIP 200 OK message. For example, the first multimedia application server 523a may include a list of possible new network slice identifiers, which are configured in first multimedia application server 523a, to be used by the first communications device 512a. The first communications device 512a should select a network slice identifier out of the received new network slice identifiers, which are configured in first multimedia application server 523a, such that it also matches with the network slice identifiers that it has in its access network subscription profile.
After receiving the SIP 200 OK message the first communications device 512a knows that a second PDU session is required at the originating end.
Now both the first communications device 512a and the second communications device 512b are aware that the new PDU session is required. Hence, they will tear down the ongoing IMS session, establish a new PDU IMS session with the new network slice identifier. Then the first communications device 512a initiates a new VR session which results in a successful IMS session. The call flow will not be described here since it corresponds to the first call flow including actions 701-712.
If both ends have to establish a new PDU session to have a new network slice identifier then they will both do so and register to the application network 520a, 520b, such as IMS register, over the new data session, such as a new PDU IMS session. The originating side then establishes a new IMS VR session to the terminating second communications device 512b as described above and shown in the above call flow.
There are other cases that may be addressed in addition to the example where both ends have to establish a new PDU session. Three such cases are discussed below.
The second communications device 512b now receives the second IMS VR session over the already established PDU session for IMS.
In this example the application node acquired the network slice identifier used for the PDU IMS session at IMS session setup. The network slice identifier may also be acquired during registration. This would remove action 706 and the equivalent action in the terminating network if applicable.
Exemplifying methods according to embodiments herein will now be described with reference to flowcharts of
The methods are for upgrading a first data session for a first media type to handle a second media type. The data session may also be referred to as a service session.
In some embodiments the application network 520a, 520b is an Internet Protocol-based multimedia system, such as IMS, providing the service to the communications devices 512a, 512b. Thus, the first and second data sessions may each be an IMS session.
The second media type may require a higher bandwidth or higher Quality of Service, QoS, than the first media type.
The second media type may, for example, be any one or more out of: Virtual Reality, VR, Augmented Reality, AR, and Mixed Reality, MR.
The method comprises one or more of the following actions, which actions may be taken in any suitable order.
The multimedia application server 523a, 523b receives the first identifier S-NSSAI_1a, S-NSSAI1b of the first network slice NS1a, NS1b of the communications network 500a, 500b from the application node 521a, 521b associated with the communications network 500a, 500b. The first data session is established by the communications device 512a, 512b through the first network slice NS1a, NS1b.
The first identifier S-NSSAI_1 a, S-NSSAI_1b of the first network slice NS1a, NS1b may be received during session setup of the first data session from the policy controlling node 506d_a, 506d_b in Npcf_PolicyAuthorisation_Subscribe Response. However, the first identifier S-NSSAI_1a, S-NSSAI_1 b of the first network slice NS1a, NS1b may also be received in other messages, for example during the registration procedure of the communications device 512a, 512b with the application network 520a, 520b.
Action 801 is related to action 709 of
In some embodiments the multimedia application server 523a, 523b saves the first identifier S-NSSAI_1a, S-NSSAI_1b of the first network slice in the session state associated with the first data session.
Action 801 is related to action 710 of
The multimedia application server 523a, 523b receives a request, from the first communications device 512a to upgrade the first data session to handle the second media type. The request comprises session description information corresponding to an upgraded data session handling the second media type.
The request may be a Re-invite SIP message, e.g., from the first communications device 512a. The session description information may be a Session Description Protocol information. For example, the Re-invite message may comprise SDP information corresponding to an upgraded IMS session. The following example embodiments will be described based on the assumption that the request is received from the first communications device 512a.
Action 803 is related to actions 714 and 716 of
The multimedia application server 523a, 523b may determine, based on the received first identifier S-NSSAI1a, S-NSSAI1b and the received session description information corresponding to the upgraded data session, to instruct the communications device 512a, 512b that the second data session on the second network slice NS2a, NS2b identified by the second identifier S-NSSAI_2a, S-NSSAI_2b is required for the upgrade to the second media type to take place.
For example, the first multimedia application server 523a may determine to instruct the first communications device 512a that the second data session on the second network slice NS2a of the first communications network 500a identified by the second identifier S-NSSAI_2a is required for the upgrade to the second media type to take place.
At the second communications network 500b, the second multimedia application server 523b may determine to instruct the second communications device 512b that the second data session on the second network slice NS2b of the second communications network 500b identified by the second identifier S-NSSAI_2b is required for the upgrade to the second media type to take place.
Since the multimedia application server 523a, 523b has received the received first identifier S-NSSAI1a, S-NSSAI1b and the received session description information corresponding to the upgraded data session in actions 801 and 803 above it is able to make this determination. The determination may for example be based on a match or mismatch between the received first identifier S-NSSAI1a, S-NSSAI1b and a required network slice identifier based on the received session description information corresponding to the upgraded data session.
Action 804 is related to actions 715 and 717 of
In response to the received request, and based on the first identifier S-NSSAI1a, S-NSSAI1b of the first network slice NS1a, NS1b and the session description information, the multimedia application server 523a, 523b sends an indication to the communications device 512a, 512b that a second data session on the second network slice NS2a, NS2b identified by the second identifier S-NSSAI_2a, S-NSSAI_2b is required for the upgrade to handle the second media type to take place.
The indication may be sent in a SIP message. For example, the second multimedia application server 523b may send the indication to the second communications device 512b in a SIP INVITE message. In another example, the first multimedia application server 523a may send the indication to the first communications device 512a in a SIP 200 OK response. This was detailed when describing
The indication may also be sent at SDP level.
In some embodiments the indication to the communications device 512a, 512b that the second data session on the second network slice NS2a, NS2b identified by the second identifier S-NSSAI_2a, S-NSSAI_2b is required for the upgrade to handle the second media type to take place is a list of second identifiers S-NSSAI_2a, S-NSSAI_2b, each associated with the respective second network slice NS2a, NS2b, which are configured in the multimedia application server 523a, 523b and support the second media type.
The list of second identifiers S-NSSAI_2a, S-NSSAI_2b sent to the communications device 512a, 512b may be determined by the multimedia application server 523a, 523b based on configured network slice identifiers in the multimedia application server 523a, 523b and based on which of the configured network slice identifiers that support the second media type. Thus, the multimedia application server 523a, 523b may select the second S-NSSAIs from its configured network slice identifiers based on which of the configured network slice identifiers that support the second media type.
Action 805 is related to actions 716 and 718 of
In some embodiments, wherein the first data session is established between the first communications device 512a and the second communications device 512b, and wherein the method is performed by the first multimedia application server 523a associated with the first communications network 500a providing the first data session to the first communications device 512a, the method further comprises the below actions.
Thus, in some embodiments the first multimedia application server 523a receives from the second multimedia application server 523b of the second application network 520b providing the first data session to the second communications device 512b, a session initiation message indicating that the second data session is to be initiated at the second communications network 500b.
The session initiation message may for example be a SIP 200 OK message.
Action 806 is related to action 721b of
When action 806 has been performed the first multimedia application server 523a may send the session initiation message indicating that the second data session is to be initiated at the second communications network 500b to the first communications device 512a, in response to the received indication that the second data session is to be initiated.
Action 807 is related to action 722 of
The method comprises one or more or the following actions.
The communications device 512a, 512b establishes the first data session between the first communications device 512a and the second communications device 512b. The communications device 512a, 512b is one of the first or the second communications device 512a, 512b. The first data session is established by the communications device 512a, 512b on the first network slice NS1a, NS1b of the communications network 500a, 500b serving the communications device 512a, 512b wherein the first network slice NS1a, NS1b is identified by the first identifier S-NSSAI_1a, S-NSSAI_1 b.
Action 901 is related to actions 704-711 of
The first communications device 512a may send a request, to the application network 520a to upgrade the first data session to handle the second media type.
When the method is performed by the first communications device 512a then the first communications device 512a may send a request, to the first application network 520a, to upgrade the first data session to handle the second media type. The request from the first communications device 512a may be a SIP Invite message.
Action 902 is related to actions 705 of
The communications device 512a, 512b receives, from the multimedia application server 523a, 523b of the applications network 500a, 500b associated with the communications network 500a, 500b and controlling the first data session, the indication S-NSSAI_2a, S-NSSAI_2b that the second data session on the second network slice NS2a, NS2b identified by the second identifier S-NSSAI2a, S-NSSAI_2b is required for upgrading the first data session to handle the second media type.
As mentioned above in relation to action 805, in some embodiments the indication to the communications device 512a, 512b that the second data session is required for the upgrade to take place is a list of second identifiers S-NSSAI_2a, S-NSSAI_2b, each associated with the respective second network slice NS2a, NS2b, which are configured in the multimedia application server 523a, 523b and support the second media type.
The communications device 512a, 512b may receive the indication that the second data session on the second network slice NS2a, NS2b is required for the upgrade to handle the second media type to take place in response to the request to upgrade the first data session sent in action 902 above. For example, the first communications device 512a may receive the indication that the second data session on the second network slice NS2a is required in response to the request to upgrade the first data session which was described in action 722 above. In some embodiments the second communications device 512b receives the indication that the second data session on the second network slice NS2b is required as detailed in action 718 above. The request to upgrade the first data session may be sent by the first communications device 512a as described above in action 902.
The communications device 512a, 512b may further receive session description information corresponding to the upgraded data session handling the second media type, from the multimedia application server 523a, 523b. For example, the second communications device 512b may receive the session description information.
Action 903 is related to action 718 of
In response to the received indication that the second data session on the second network slice NS2a, NS2b is required for the upgrade to the second media type to take place, the communications device 512a, 512b may determine whether or not to upgrade the first data session to the second data session based on the second identifier S-NSSAI_2a, S-NSSAI_2b and an access network subscription profile of the communications device 512a, 512b.
Action 904 is related to action 719 of
In further response to the received indication that the second data session on the second network slice NS2b is required for upgrading the first data session, the second communications device 512b may send a response to the multimedia application server 523a, 523b, such as the second multimedia application server 523b.
The response indicates whether or not the second communications device 512b is able to initiate the second data session with the second identifier S-NSSAI_2b for upgrading the first data session to handle the second media type. The response is based on the received second identifier S-NSSAI_2b and an access network subscription profile of the second communications device 512b. A positive response may imply acceptance by the second communications device 512b.
The response may be a SIP message, such as a SIP 200 OK message. The second application network 520b may forward the response to the first application network 520a and the first communications device 512a.
The response may indicate an acceptance or a rejection of the upgrade, for example, one of the following:
Action 905 is related to action 720 of
In order to upgrade the first data session, the communications device 512a, 512b may tear down the first data session.
Then the communications device 512a, 512b may establish the second data session based on the second identifier S-NSSAI_2a, S-NSSAI_2b.
The establishment of the second data session may be seen as an acceptance from the first communications device 512a of the received request for upgrading the first data session, that is, of the received indication of the required upgrade.
The method comprises one or more or the following actions.
The application node 521 a, 521b transmits, to the policy controlling node 506d_a, 506d_b of the communications network 500a, 500b, a request for the first identifier S-NSSAI1 of the first network slice NS1a, NS1b of the communications network 500a. As mentioned above, the first network slice NS1a, NS1b is used to establish the first data session by the communications device 512a, 512b.
In some embodiments transmitting the request for the first identifier S-NSSAI1 is performed in response to an initiation of the first data session. For example, the initiation of the first data session may be performed by the first communications device 512a by sending a SIP INVITE message to the second communications device 512b via the first application node 521a, such as a first P-CSCF.
Action 1001 is related to action 706 of
The application node 521 a, 521b then receives, from the policy controlling node 506d_a, 506d_b, the first identifier S-NSSAI1 of the first network slice NS1a, NS1b in response to the transmitted request for the first identifier.
Action 1002 is related to action 707 of
The application node 521 a, 521b then forwards the first identifier S-NSSAI_1 a, S-NSSAI_1b of the first network slice NS1a, NS1b to the multimedia application server 523a, 523b, such that the multimedia application server 523a, 523b is able to determine whether or not the first data session is able to handle the second media type based on the first identifier S-NSSAI_1a, S-NSSAI_1b of the first network slice NS1a, NS1b and session description information corresponding to an upgraded data session handling the second media type.
Action 1003 is related to action 709 of
The policy controlling node 506d_a, 506d_b receives, from the application node 521a, 521b associated with the communications network 500a, 500b, the request for the first identifier S-NSSAI_1a, S-NSSAI_1 b of the first network slice NS1a, NS1b of the communications network 500a. As mentioned above, the first network slice NS1a, NS1b is used for the first data session between the first communications device 512a and the second communications device 512b.
Action 1101 is related to action 706 of
The policy controlling node 506d_a, 506d_b sends the first identifier S-NSSAI_1 a, S-NSSAI_1b of the first network slice NS1a, NS1b to the application node 521a, 521b in response to the received request.
Action 1102 is related to action 707 of
The multimedia application server 523a, 523b may comprise a processing module 1201 for performing the above method actions. The processing module 1201 may comprise a receiving module 1210 to, e.g. receive different messages.
Thus the multimedia application server 523a, 523b is configured to, e.g. by means of the receiving module 1210, receive the first identifier S-NSSAI_1a, S-NSSAI1b of the first network slice NS1a, NS1b of the communications network 500a, 500b from the application node 521a, 521b. The first data session is established by the communications device 512a, 512b through the first network slice NS1a, NS1b.
The multimedia application server 523a, 523b is configured to, e.g. by means of the receiving module 1210, receive the request, from the first communications device 512a to upgrade the first data session to handle the second media type. The request comprises session description information corresponding to an upgraded data session handling the second media type.
The processing module 1201 may comprise a sending module 1220 to, e.g. send different messages. Thus the multimedia application server 523a, 523b is configured to, e.g. by means of the sending module 1220, send the indication to the communications device 512a, 512b that the second data session on the second network slice NS2a, NS2b identified by the second identifier S-NSSAI_2a, S-NSSAI_2b is required for the upgrade to handle the second media type to take place. The multimedia application server 523a, 523b is configured to, e.g. by means of the sending module 1220, send the indication in response to the received request, and based on the first identifier S-NSSAI1a, S-NSSAI1b of the first network slice NS1a, NS1b and the session description information.
The processing module 1201 may comprise a determining module 1230. Thus the multimedia application server 523a, 523b may be configured to, e.g. by means of the determining module 1230, determine based on the received first identifier S-NSSAI1a, S-NSSAI1b and the received session description information corresponding to the upgraded data session, to instruct the communications device 512a, 512b that the second data session on the second network slice NS2a, NS2b identified by the second identifier S-NSSAI_2 a, S-NSSAI_2b is required for the upgrade to the second media type to take place.
In some embodiments the first data session is adapted to be established between the first communications device 512a and the second communications device 512b, and the multimedia application server 523a, 523b is the first multimedia application server 523a associated with the first communications network 500a adapted to provide the first data session to the first communications device 512a. Then the first multimedia application server 523a may be further configured to, e.g. by means of the receiving module 1210, receive from the second multimedia application server 523b associated with the second communications network 500b, the session initiation message indicating that the second data session is to be initiated at the second communications network 500b.
Then the multimedia application server 523a, 523b may be further configured to, e.g. by means of the sending module 1220, send the indication to the first communications device 512a that the second data session on the second network slice NS2a, NS2b identified by the second identifier S-NSSAI_2a, S-NSSAI_2b is required for the upgrade to the second media type to take place, in response to the received indication that the second data session is to be initiated.
In some embodiments the multimedia application server 523a, 523b is further configured to, e.g. by means of a memory module 1202, save the first identifier S-NSSAI_1 a, S-NSSAI_1b of the first network slice in the session state associated with the first data session.
In some embodiments the multimedia application server 523a, 523b is further configured to, e.g. by means of the receiving module 1210, receive the first identifier S-NSSAI_1 a, S-NSSAI_1b of the first network slice NS1a, NS1b during session setup of the first data session from the policy controlling node 506d in an Npcf_PolicyAuthorisation_Subscribe Response or during the registration procedure of the communications device 512a, 512b with the application network 520a, 520b.
The communications device 512a, 512b may comprise a processing module 1301 for performing the above method actions. The processing module 1301 may comprise an establishing module 1310 to, e.g. establish the data session, such as an IMS session, or in other words a PDU session for IMS.
Thus, the communications device 512a, 512b is configured to, e.g. by means of the establishing module 1310, establish the first data session between the first communications device 512a and the second communications device 512b. The communications device 512a, 512b is one of the first or the second communications device 512a, 512b. The first data session is adapted to be established by the communications device 512a, 512b on the first network slice NS1a, NS1b of the communications network 500a, 500b adapted to serve the communications device 512a. The first network slice NS1a, NS1b is adapted to be identified by the first identifier S-NSSAI_1 a, S-NSSAI_1b.
The processing module 1301 may comprise a receiving module 1320 to, e.g. receive different messages.
Thus, the communications device 512a, 512b is configured to, e.g. by means of the receiving module 1320, receive from the multimedia application server 523a, 523b associated with the communications network 500a, 500b and adapted to control the first data session, an indication S-NSSAI_2a, S-NSSAI_2b that the second data session on the second network slice NS2a, NS2b identified by the second identifier S-NSSAI2a, S-NSSAI_2 b is required for upgrading the first data session to handle the second media type.
The processing module 1301 may comprise a determining module 1330.
Then the communications device 512a, 512b may be further configured to, e.g. by means of the determining module 1330, determine whether or not to upgrade the first data session to the second data session based on the second identifier S-NSSAI_2a, S-NSSAI_2 b and an access network subscription profile of the communications device 512a, 512b. The determination may be performed in response to the received indication that the second data session on the second network slice NS2a, NS2b is required for the upgrade to the second media type to take place.
The processing module 1301 may comprise a sending module 1340. In some embodiments the communications device 512a, 512b is further configured to, e.g. by means of the sending module 1340, send, to the multimedia application server 523a, 523b, a response to the received indication that the second data session on the second network slice NS2a, NS2b is required for upgrading the first data session. The response indicates whether or not the second communications device 512b is able to initiate the second data session with the second identifier S-NSSAI2a, S-NSSAI_2b for upgrading the first data session to handle the second media type. The response is based on the received second identifier S-NSSAI_2b and an access network subscription profile of the second communications device 512b.
In some embodiments the communications device 512a, 512b is adapted to be the first communications device 512a. Then the communications device 512a, 512b may further be configured to, e.g. by means of the sending module 1340, send a request, to the first application network 520a, to upgrade the first data session to handle the second media type.
The communications device 512a, 512b may further be configured to, e.g. by means of the receiving module 1320, receive the indication that the second data session on the second network slice NS2a is required for the upgrade to handle the second media type to take place in response to the request to upgrade the first data session.
The application node 521 a, 521b may comprise a processing module 1401 for performing the above method actions. The processing module 1401 may comprise a sending module 1410 to, e.g. send messages.
Thus, the application node 521 a, 521b is configured to, e.g. by means of the receiving module 1310, send to the policy controlling node 506d_a, 506d_b of the communications network 500a, 500b, the request for the first identifier S-NSSAI1 of the first network slice NS1a, NS1b of the communications network 500a. The first network slice NS1a, NS1b is used to establish the first data session by the communications device 512a, 512b.
The processing module 1401 may further comprise a receiving module 1420.
Thus, the application node 521 a, 521b is configured to, e.g. by means of the receiving module 1420, receive, from the policy controlling node 506d_a, 506d_b, the first identifier S-NSSAI1 of the first network slice NS1a, NS1b in response to the transmitted request for the first identifier.
The application node 521 a, 521b is configured to, e.g. by means of the sending module 1420, forward the first identifier S-NSSAI_1a, S-NSSAI_1b of the first network slice NS1a, NS1b to the multimedia application server 523a, 523b such that the multimedia application server 523a, 523b is able to determine whether or not the first data session is able to handle the second media type based on the first identifier S-NSSAI_1 a, S-NSSAI_1b of the first network slice NS1a, NS1b and session description information corresponding to an upgraded data session handling the second media type.
In some embodiments the application node 521 a, 521b is configured to transmit the request in response to an initiation of the first data session.
The policy controlling node 506d_a, 506d_b may comprise a receiving module 1510 and a sending module 1520.
The policy controlling node 506d_a, 506d_b is configured to, e.g. by means of the receiving module 1510, receive from an application node 521a, 521b associated with the communications network 500a, 500b, the request for the first identifier S-NSSAI_1a, S-NSSAI_1b of the first network slice NS1a, NS1b of the communications network 500a. The first network slice NS1a, NS1b is adapted to be used for the first data session between the first communications device 512a and the second communications device 512b.
The policy controlling node 506d_a, 506d_b is configured to, e.g. by means of the sending module 1520, send the first identifier S-NSSAI_1 a, S-NSSAI_1 b of the first network slice NS1a, NS1b to the application node 521a, 521b in response to the received request.
The multimedia application server 523a, 523b, the communications device 512a, 512b, the application node 521a, 521b, and the policy controlling node 506d_a, 506d_b may comprise a respective input and output unit, 1206, 1306, 1406 and 1506 configured to communicate with each other. The input and output unit may comprise a receiver (not shown) and a transmitter (not shown).
The embodiments herein may be implemented through a respective processor or one or more processors, such as the respective processing circuit 1204, 1304, 1404 and 1504 in the multimedia application server 523a, 523b, the communications device 512a, 512b, the application node 521 a, 521b, and the policy controlling node 506d_a, 506d_b depicted in
The multimedia application server 523a, 523b, the communications device 512a, 512b, the application node 521a, 521b, and the policy controlling node 506d_a, 506d_b may further comprise a respective memory 1202, 1302, 1402 and 1502 comprising one or more memory units. The memory comprises instructions executable by the processor in the multimedia application server 523a, 523b, the communications device 512a, 512b, the application node 521a, 521b, and the policy controlling node 506d_a, 506d_b.
Each respective memory 1202, 1302, 1402 and 1502 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 multimedia application server 523a, 523b, communications device 512a, 512b, application node 521a, 521b, and policy controlling node 506d_a, 506d_b.
In some embodiments, a respective computer program 1203, 1303, 1403 and 1503 comprises instructions, which when executed by the at least one processor, cause the at least one processor of the respective multimedia application server 523a, 523b, communications device 512a, 512b, application node 521a, 521b, and policy controlling node 506d_a, 506d_b to perform the actions above.
In some embodiments, a respective carrier 1205, 1305, 1405 and 1505 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 in 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 multimedia application server 523a, 523b, communications device 512a, 512b, application node 521a, 521b, and policy controlling node 506d_a, 506d_b, 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
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.
In an optional subaction (not shown) the host computer provides the user data by executing a host application. In a second action 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third action 3512, the UE receives the user data carried in the transmission.
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.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/SE2021/050753 | 7/27/2021 | WO |
