SRIVASTAVA ANUBHAV (IN)
MILINSKI ALEXANDER (DE)
| US20190174536A1 | 2019-06-06 | |||
| US20190223093A1 | 2019-07-18 |
NEC ET AL: "Need of slice based AMF overload control at NG-RAN", vol. SA WG2, no. Reno, Nevada; 20190513 - 20190517, 15 May 2019 (2019-05-15), XP051736257, Retrieved from the Internet
| Claims 1 . An apparatus comprising means for: providing, from a user equipment to a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices; and receiving, at the user equipment from the network entity, an indication that the first slice is overloaded. 2. An apparatus according to claim 1 , wherein the network entity comprises a serving call session control function or a proxy call session control function. 3. An apparatus according to claim 1 or claim 2, wherein the first slice supports one of voice and video call, rich communication services and mission critical push to talk services. 4. An apparatus according to any of claims 1 to 3, wherein the indication is included in a response source header. 5. An apparatus according to any of claims 1 to 4, wherein the indication comprises an indication of the identity of the first slice. 6. An apparatus comprising means for: receiving, from a user equipment at a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices; and providing, to the user equipment from the network entity, an indication that the first slice is overloaded. 7. An apparatus according to claim 6, wherein the network entity comprises a serving call session control function or a proxy call session control function. 8. An apparatus according to claim 6 or claim 7, wherein the first slice supports one of voice and video call, rich communication services and mission critical push to talk services. 9. An apparatus according to any of claims 6 to 8, wherein the indication is included in a response source header. 10. An apparatus according to any of claims 6 to 9, wherein the indication comprises an indication of the identity of the first slice. 11. A method comprising: providing, from a user equipment to a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices; and receiving, at the user equipment from the network entity, an indication that the first slice is overloaded. 12. A method comprising: receiving, from a user equipment at a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices; and providing, to the user equipment from the network entity, an indication that the first slice is overloaded. 13. An apparatus comprising: at least one processor and at least one memory including a computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to: provide, from a user equipment to a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices; and receive, at the user equipment from the network entity, an indication that the first slice is overloaded. 14. An apparatus comprising: at least one processor and at least one memory including a computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to: receive, from a user equipment at a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices; and provide, to the user equipment from the network entity, an indication that the first slice is overloaded. 15. A computer readable medium comprising program instructions for causing an apparatus to perform at least the following: providing, from a user equipment to a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices; and receiving, at the user equipment from the network entity, an indication that the first slice is overloaded. A computer readable medium comprising program instructions for causing an apparatus to perform at least the following: receiving, from a user equipment at a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices; and providing, to the user equipment from the network entity, an indication that the first slice is overloaded. |
SLICE OVERLOAD HANDLING
Field
The present application relates to a method, apparatus, and computer program and in particular but not exclusively to slice overload handling.
Background
A communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations and/or other nodes by providing carriers between the various entities involved in the communications path. A communication system can be provided for example by means of a communication network and one or more compatible communication devices (also referred to as station or user equipment) and/or application servers. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, video, electronic mail (email), text message, multimedia, content data, time-sensitive network (TSN) flows and/or data in an industrial application such as critical system messages between an actuator and a controller, critical sensor data (such as measurements, video feed etc.) towards a control system and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.
In a wireless communication system at least a part of a communication session, for example, between at least two stations or between at least one station and at least one application server (e.g. for video), occurs over a wireless link. Examples of wireless systems comprise public land mobile networks (PLMN) operating based on 3GPP radio standards such as E- UTRA, New Radio, satellite based communication systems and different wireless local networks, for example wireless local area networks (WLAN). The wireless systems can typically be divided into cells, and are therefore often referred to as cellular systems.
A user can access the communication system by means of an appropriate communication device or terminal. A communication device of a user may be referred to as user equipment (UE) or user device. A communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other users. The communication device may access one or more carriers provided by the network, for example a base station of a cell, and transmit and/or receive communications on the one or more carriers. In carrier aggregation (CA) two or more carriers are combined into one channel. In dual connectivity (DC), two carriers from different sites are combined, that is a user equipment may be dual (or multi) connected to two (or more) sites.
The communication system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and/or parameters which shall be used for the connection are also typically defined. One example of a communications system is UTRAN (3G radio). Other examples of communication systems are the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) based on the E-UTRAN radio-access technology, and so-called 5G system (5GS) including the 5G or next generation core (NGC) and the 5G Access network based on the New Radio (NR) radio-access technology. 5GS including NR are being standardized by the 3rd Generation Partnership Project (3GPP).
Slicing is a concept which has been introduced in 5G. An operator transforms its network into a set of logical networks on top of a shared infrastructure, Each logical network (known as a slice) of the set of logical networks is designed to serve a defined business purpose and comprises the required network resources, configured and connected end-to-end. The slices are assigned to a subscriber for the desired services
TS 23.501 and TS 23.502 provide details of slicing in 5G. Slicing may provide requirements such as low latency, high throughput, etc.
Summary
In a first aspect there is provided an apparatus, said apparatus comprising means for providing, from a user equipment to a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices and receiving, at the user equipment from the network entity, an indication that the first slice is overloaded.
The network entity may comprise a serving call session control function or a proxy call session control function. The first slice may support one of voice and video call, rich communication services and mission critical push to talk services.
The indication may be included in a response source header.
The indication may comprise an indication of the identity of the first slice.
In a second aspect there is provided an apparatus comprising means for receiving, from a user equipment at a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices and providing, to the user equipment from the network entity, an indication that the first slice is overloaded.
The network entity may comprise a serving call session control function or a proxy call session control function.
The first slice may support one of voice and video call, rich communication services and mission critical push to talk services.
The indication may be included in a response source header.
The indication may comprise an indication of the identity of the first slice.
In a third aspect there is provided a method comprising providing, from a user equipment to a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices and receiving, at the user equipment from the network entity, an indication that the first slice is overloaded.
The network entity may comprise a serving call session control function or a proxy call session control function.
The first slice may support one of voice and video call, rich communication services and mission critical push to talk services.
The indication may be included in a response source header.
The indication may comprise an indication of the identity of the first slice. In a fourth aspect there is provided a method comprising receiving, from a user equipment at a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices and providing, to the user equipment from the network entity, an indication that the first slice is overloaded.
The network entity may comprise a serving call session control function or a proxy call session control function.
The first slice may support one of voice and video call, rich communication services and mission critical push to talk services.
The indication may be included in a response source header.
The indication may comprise an indication of the identity of the first slice.
In a fifth aspect there is provided an apparatus comprising at least one processor and at least one memory including a computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to: provide, from a user equipment to a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices and receive, at the user equipment from the network entity, an indication that the first slice is overloaded.
The network entity may comprise a serving call session control function or a proxy call session control function.
The first slice may support one of voice and video call, rich communication services and mission critical push to talk services.
The indication may be included in a response source header.
The indication may comprise an indication of the identity of the first slice.
In a sixth aspect there is provided an apparatus comprising: at least one processor and at least one memory including a computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to: receive, from a user equipment at a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices and provide, to the user equipment from the network entity, an indication that the first slice is overloaded.
The network entity may comprise a serving call session control function or a proxy call session control function.
The first slice may support one of voice and video call, rich communication services and mission critical push to talk services.
The indication may be included in a response source header.
The indication may comprise an indication of the identity of the first slice.
In a seventh aspect there is provided a computer readable medium comprising program instructions for causing an apparatus to perform at least the following providing, from a user equipment to a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices and receiving, at the user equipment from the network entity, an indication that the first slice is overloaded.
The network entity may comprise a serving call session control function or a proxy call session control function.
The first slice may support one of voice and video call, rich communication services and mission critical push to talk services.
The indication may be included in a response source header.
The indication may comprise an indication of the identity of the first slice.
In an eighth aspect there is provided a computer readable medium comprising program instructions for causing an apparatus to perform at least the following receiving, from a user equipment at a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices and providing, to the user equipment from the network entity, an indication that the first slice is overloaded. The network entity may comprise a serving call session control function or a proxy call session control function.
The first slice may support one of voice and video call, rich communication services and mission critical push to talk services.
The indication may be included in a response source header.
The indication may comprise an indication of the identity of the first slice.
In a ninth aspect there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to the third aspect or a method according to the fourth aspect.
In the above, many different embodiments have been described. It should be appreciated that further embodiments may be provided by the combination of any two or more of the embodiments described above.
Description of Figures
Embodiments will now be described, by way of example only, with reference to the accompanying Figures in which:
Figure 1 shows a schematic diagram of an example 5G system;
Figure 2 shows a schematic diagram of an example mobile communication device;
Figure 3 shows a schematic diagram of an example control apparatus;
Figure 4 shows a signalling flow between a UE and an IMS network;
Figure 5 shows a signalling flow between a UE and an IMS network;
Figure 6 shows a flowchart of a method according to an example embodiment;
Figure 7 shows a flowchart of a method according to an example embodiment; Figure 8 shows a signalling flow between a UE and an IMS network according to an example embodiment;
Figure 9 shows a signalling flow between a UE and an IMS network according to an example embodiment.
Detailed description
Before explaining in detail the examples, certain general principles of a wireless communication system and mobile communication devices are briefly explained with reference to Figures 1 to 3 to assist in understanding the technology underlying the described examples.
An example of a suitable communications system is the 5G System (5GS). Network architecture in 5GS may be similar to that of LTE-advanced. Base stations of NR systems may be known as next generation Node Bs (gNBs). Changes to the network architecture may depend on the need to support various radio technologies and finer QoS support, and some on-demand requirements for e.g. QoS levels to support QoE of user point of view. Also network aware services and applications, and service and application aware networks may bring changes to the architecture. Those are related to Information Centric Network (ICN) and User-Centric Content Delivery Network (UC-CDN) approaches. NR may use multiple input - multiple output (Ml MO) antennas, many more base stations or nodes than the LTE (a so- called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
Future networks may utilise network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into “building blocks” or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent. Figure 1 shows a schematic representation of a 5G system (5GS) 100. The 5GS may comprise a user equipment (UE) 102 (which may also be referred to as a communication device or a terminal), a 5G radio access network (5GRAN) 104, a 5G core network (5GCN) 106, one or more application functions (AF) 108 and one or more data networks (DN) 110.
An example 5G core network (CN) comprises functional entities. The 5GCN 106 may comprise one or more access and mobility management functions (AMF) 112, one or more session management functions (SMF) 114, an authentication server function (ALISF) 116, a unified data management (UDM) 118, one or more user plane functions (UPF) 120, a unified data repository (UDR) 122 and/or a network exposure function (NEF) 124. The UPF is controlled by the SMF (Session Management Function) that receives policies from a PCF (Policy Control Function).
The CN is connected to a UE via the radio access network (RAN). The 5GRAN may comprise one or more gNodeB (GNB) distributed unit functions connected to one or more gNodeB (GNB) centralized unit functions. The RAN may comprise one or more access nodes.
An UPF (User Plane Function) whose role is called PSA (PDU Session Anchor) may be responsible for forwarding frames back and forth between the DN (data network) and the tunnels established over the 5G towards the UE(s) exchanging traffic with the DN.
An IP Multimedia Subsystem (IMS) is an architectural framework for delivering IP multimedia services such as Voice and Video Call, Rich Communication Services (RCS) and Mission Critical Push To Talk (MCPTT). From the 5GC perspective, the IMS network appears as an AF. Nodes of an IMS network include Session Initiation Protocol (SIP) servers and proxies such as a Proxy-Call Session Control Functions (P-CSCF), an Interrogating- Call Session Control Function (l-CSCF) and a Serving-Call Session Control Function (S-CSCF) for processing Session Initiation Protocol (SIP) signalling packets in the IMS.
A possible mobile communication device will now be described in more detail with reference to Figure 2 showing a schematic, partially sectioned view of a communication device 200. Such a communication device is often referred to as user equipment (UE) or terminal. An appropriate mobile communication device may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a mobile station (MS) or mobile device such as a mobile phone or what is known as a ’smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), personal data assistant (PDA) or a tablet provided with wireless communication capabilities, or any combinations of these or the like. A mobile communication device may provide, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and so on. Users may thus be offered and provided numerous services via their communication devices. Non-limiting examples of these services comprise two-way or multi-way calls, data communication or multimedia services or simply an access to a data communications network system, such as the Internet. Users may also be provided broadcast or multicast data. Non-limiting examples of the content comprise downloads, television and radio programs, videos, advertisements, various alerts and other information.
A mobile device is typically provided with at least one data processing entity 201 , at least one memory 202 and other possible components 203 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The data processing, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 204. The user may control the operation of the mobile device by means of a suitable user interface such as key pad 205, voice commands, touch sensitive screen or pad, combinations thereof or the like. A display 208, a speaker and a microphone can be also provided. Furthermore, a mobile communication device may comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.
The mobile device 200 may receive signals over an air or radio interface 207 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In Figure 2 transceiver apparatus is designated schematically by block 206. The transceiver apparatus 206 may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.
Figure 3 shows an example embodiment of a control apparatus for a communication system, for example to be coupled to and/or for controlling a station of an access system, such as a RAN node, e.g. a base station, eNB or gNB, a relay node or a core network function such as AMF/SMF, or a server or host. The method may be implanted in a single control apparatus or across more than one control apparatus. The control apparatus may be integrated with or external to a node or module of a core network or RAN. In some embodiments, base stations comprise a separate control apparatus unit or module. In other embodiments, the control apparatus can be another network element such as a radio network controller or a spectrum controller. In some embodiments, each base station may have such a control apparatus as well as a control apparatus being provided in a radio network controller. The control apparatus 300 can be arranged to provide control on communications in the service area of the system. The control apparatus 300 comprises at least one memory 301 , at least one data processing unit 302, 303 and an input/output interface 304. Via the interface the control apparatus can be coupled to a receiver and a transmitter of the base station. The receiver and/or the transmitter may be implemented as a radio front end or a remote radio head.
Network Slicing in IMS
3GPP has agreed that IMS will support slicing. That is, the IMS network will be sliced to offer different kind of services. Hence, various IMS nodes such as P-CSCF and S-CSCF will support a plurality of slices. There are few slices already created in IMS for providing different kind of services, for example:
Slicel (S-NSSAI 1): Voice & Video call
Slice2 (S-NSSAI 2): RCS
Slice3 (S-NSSAI 3): MCPTT
For example, P-CSCF and S-CSCF may support Slice Single-Network Slice Selection Assistance Information (S-NSSAI) 1 , S-NSSAI 2, and S-NSSAI 3.
Telecommunication networks are made up of various nodes interconnected by communication links. These links comprise two separate logical networks. One network is used for carrying voice and user data, and the second for signaling and control information. To establish and release connections, and to access services, switches communicate with each other over the signaling network. These networks and switches are engineered to carry a certain number of active calls and process requests for calls and services at a certain rate. Occasionally, they might experience more traffic than the engineered capacity. The nodes may be said to be overloaded or in overload. Overload controls are required to maintain the throughput and the quality of service at acceptable levels. During this overload scenario, emergency and priority calls may be handled whereas normal calls are rejected.
In a scenario where a network entity such as a node, server or network function (NF) supports a plurality of slices, a particular slice of the plurality of slices may get overloaded while the node or network function (NF) is not overloaded. Figure 4 illustrates an example case, in which P-CSCF and S-CSCF support Slice S-NSSAI
1 , S-NSSAI 2, and S-NSSAI 3, and Slice S-NSSAI 1 is overloaded at P-CSCF.
During P-CSCF address assignment by SMF, the SMF has taken into consideration the load information as well as the slice level load information of P-CSCF with the help of NRF.
During S-CSCF assignment/selection by l-CSCF, the l-CSCF has taken overload and slice level load into consideration
The Session Initiation Protocol (SIP) client/UE is registered with P-CSCF and S-CSCF.
Here, P-CSCF is not overloaded but a particular slice (S-NSSAI 1) at the P-CSCF is overloaded.
One proposal for 5G networks is that when the UE makes any call to the overloaded slice (that is, sends an INVITE with Slice S-NSSAI 1), the P-CSCF will reject the call with an existing standard mechanism such as sending a 500 Server Internal Error with Retry-After header, an example of which is provided below, which means the UE can try after the timer mentioned by P-CSCF.
500 Server Internal Error
Retry-After= 1800
With this approach, the UE will assume that P-CSCF (node/server) is overloaded and hence the UE won’t try to get any service for 1800 sec. However, the P-CSCF is not overloaded and is ready to handle the traffic for other two slices S-NSSAI 2 and S-NSSAI 3 for RCS & MCPTT calls, respectively.
In an alternative scenario illustrated in Figure 5, slice S-NSSAI 2 is overloaded at S-CSCF.
During P-CSCF address assignment by SMF, the SMF has taken into consideration the load information as well as the slice level load information of P-CSCF with the help of NRF.
During S-CSCF assignment/selection by l-CSCF, the l-CSCF has taken overload and slice level load into consideration.
The Session Initiation Protocol (SIP) client/UE is registered with P-CSCF and S-CSCF. Here, S-CSCF is not overloaded but a particular slice at the S-CSCF (S-NSSAI 2) is overloaded
Similarly to the proposal described with reference to Figure 4, when UE makes any call to the overloaded slice (that is, sends an INVITE with Slice S-NSSAI 2), S-CSCF will reject it with a existing standard mechanism such as sending a 500 Server Internal Error with Retry-After header, an example of which is provided below, which means UE may try after the timer mentioned by S-CSCF.
500 Server Internal Error
Retry-After= 1800
The UE will assume that S-CSCF (node/server) is overloaded and hence won’t try to get any service for 1800 sec. However, S-CSCF is not overloaded and is ready to handle the traffic for other two slices S-NSSAI 1 and S-NSSAI 3 for voice & video and MCPTT calls, respectively.
Figure 6 shows a flowchart of a method according to an example embodiment. The method may be performed at a UE (the UE may be any suitable SIP client).
In a first step, S1 , the method comprises providing, from a user equipment to a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices.
In a second step, S2, the method comprises receiving, at the user equipment from the network entity, an indication that the first slice is overloaded.
Figure 7 shows a flowchart of a method according to an example embodiment. The method may be performed at a network entity. The network entity may be an entity of an IMS network.
In a first step, T1 , the method comprises receiving, from a user equipment at a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices.
In a second step, T2, the method comprises providing, to the user equipment from the network entity, an indication that the first slice is overloaded.
The network entity may comprise a S-CSCF or a P-CSCF. The slice may support one of voice and video call, RCS and MCPTT.
The indication may be included in a response source header. The indication may comprise the identity of the first slice.
The method provides the overload status of a particular slice to a UE so that the UE may continue to get services of the remaining available slice(s). That is, the UE, on receiving the indication, may provide a further request to the network entity to use a slice of the plurality of slices other than the first slice.
In an example embodiment, P-CSCF and S-CSCF add the details of slices which are overloaded when rejecting a UE initiated request.
For this purpose, in an example embodiment, the “Response-Source” header may be used with an extension which will carry the specific slice information. The extension details are shown in italics in the example header below. ns-ext = HCOLON "fe" HCOLON functional-entity functional-entity = fe-id fe-param) fe-id = "ue" / "p-cscf" / "i-cscf" / "s-cscf" / "e-cscf" / "mgcf" / "bgcf" / "ibcf" / "trf" / "atcf" / "agcf" / "mrfc" / "Irf" / "msc-server" / "as" / token fe-param = role / side / slice-info/token role = "tas" / "scc-as" / "ip-sm-gw" / "pf-mcptt-server" / "cf-mcptt-server" / "ncf- mcpttserver" / "cms" / "gms" / "tads" / "iua" / "msc-server-ics" / token side = "orig" / "term" / "transit"/ token slice-info = slice HCOLON s-nssai EQUAL slice-id slice-id=l*DIGIT
Figure 8 shows a signalling flow for an example embodiment where S-NSSAI 1 is overloaded at P-CSCF:
The SIP client/UE sends a REGISTRATION request to IMS, requesting the list of slices it wants to use. The Network sends 200 OK, indicates the supported slices. The UE is registered with the network. When the UE makes a voice call with slice S-NSSAI 1 , the UE sends an INVITE to the P-CSCF indicating slice S-NSSAI 1 . P-CSCF is not overloaded but slice S-NSSAI 1 is overloaded.
P-CSCF rejects the INVITE with proposed details of the slice which is in overload condition
For example:
500 Server Internal Error
Retry-After= 1800
Response-Source: <urn:3gpp:fe:p-cscf.slice:s-nssai=1>
The UE can go on to make a successful RCS and MCPTT call with the available slices S- NSSAI 2 & S-NSSAI 3, respectively
Figure 9 shows a signalling flow in an example embodiment where S-CSCF is not overloaded but slice (S-NSSAI 2) is overloaded.
The SIP client/UE sends a REGISTRATION request to IMS, requesting the list of slices it wants to use. The Network sends 200 OK, indicates the supported slices.
The UE is registered with the network. When UE makes RCS call with slice S-NSSAI 2, the UE sends an INVITE to the S-CSCF (via P-CSCF) indicating slice S-NSSAI-2.
S-CSCF rejects the invite with proposed details of the slice which is in overload condition.
For example:
500 Server Internal Error
Retry-After= 1800
Response-Source: <urn:3gpp:fe:s-cscf.slice:s-nssai=2>
Now UE can proceed to make successful voice call and MCPTT call with the available slices S-NSSA11 and S-NSSAI 3, respectively
UE may be able to get regular service such as making calls using the remaining/available slices which are not overloaded using this method. A UE will not be out of service when a slice at a network node is overloaded. The method may be implemented in a user equipment as described with reference to figure 2 or a control apparatus as described with reference to figure 3.
An apparatus may comprise means for providing, from a user equipment to a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices and receiving, at the user equipment from the network entity, an indication that the first slice is overloaded.
Alternatively, or in addition, an apparatus may comprise means for receiving, from a user equipment at a network entity supporting a plurality of slices, a request to use a first slice of the plurality of slices and providing, to the user equipment from the network entity, an indication that the first slice is overloaded.
It should be understood that the apparatuses may comprise or be coupled to other units or modules etc., such as radio parts or radio heads, used in or for transmission and/or reception. Although the apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.
It is noted that whilst embodiments have been described in relation to LTE and 5GS, similar principles can be applied in relation to other networks and communication systems. Therefore, although certain embodiments were described above by way of example with reference to certain example architectures for wireless networks, technologies and standards, embodiments may be applied to any other suitable forms of communication systems than those illustrated and described herein.
It is also noted herein that while the above describes example embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.
In general, the various example embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects of the invention may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto. While various aspects of the invention may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
The embodiments of this invention may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and/or macros, may be stored in any apparatus- readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out embodiments. The one or more computer-executable components may be at least one software code or portions of it.
Further in this regard it should be noted that any blocks of the logic flow as in the Figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD. The physical media is a non-transitory media.
The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples.
Example embodiments of the inventions may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate. The foregoing description has provided by way of non-limiting examples a full and informative description of the exemplary embodiment of this invention. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of this invention will still fall within the scope of this invention as defined in the appended claims. Indeed, there is a further embodiment comprising a combination of one or more embodiments with any of the other embodiments previously discussed.