[go: up one dir, main page]

WO2022101131A1 - Traitement de surcharge de tranche - Google Patents

Traitement de surcharge de tranche Download PDF

Info

Publication number
WO2022101131A1
WO2022101131A1 PCT/EP2021/080922 EP2021080922W WO2022101131A1 WO 2022101131 A1 WO2022101131 A1 WO 2022101131A1 EP 2021080922 W EP2021080922 W EP 2021080922W WO 2022101131 A1 WO2022101131 A1 WO 2022101131A1
Authority
WO
WIPO (PCT)
Prior art keywords
slice
slices
network entity
user equipment
indication
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/EP2021/080922
Other languages
English (en)
Inventor
Ashok Kumar Nayak
Anubhav Srivastava
Alexander Milinski
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Technologies Oy
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of WO2022101131A1 publication Critical patent/WO2022101131A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service

Definitions

  • the present application relates to a method, apparatus, and computer program and in particular but not exclusively to slice overload handling.
  • 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.
  • 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.
  • 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).
  • PLMN public land mobile networks
  • 3GPP radio standards such as E- UTRA, New Radio, satellite based communication systems
  • different wireless local networks for example wireless local area networks (WLAN).
  • WLAN wireless local area networks
  • 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.
  • UE user equipment
  • 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.
  • CA carrier aggregation
  • DC dual connectivity
  • two carriers from different sites 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 5GS 5G System
  • 5GS 5G System
  • 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.
  • 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.
  • ICN Information Centric Network
  • UC-CDN User-Centric Content Delivery Network
  • 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.
  • Ml MO multiple input - multiple output
  • 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.
  • 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.
  • FIG. 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.
  • UE user equipment
  • 5GRAN 5G radio access network
  • 5GCN 5G core network
  • AF application functions
  • DN data networks
  • the 5GCN 106 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).
  • SMF Session Management Function
  • 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
  • PSA PDU Session Anchor
  • DN data network
  • UE(s) exchanging traffic with the DN.
  • An IP Multimedia Subsystem 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.
  • SIP Session Initiation Protocol
  • P-CSCF Proxy-Call Session Control Functions
  • l-CSCF Interrogating- Call Session Control Function
  • S-CSCF Serving-Call Session Control Function
  • 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.
  • 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.
  • MS mobile station
  • PDA personal data assistant
  • 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.
  • 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.
  • 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.
  • base stations comprise a separate control apparatus unit or module.
  • the control apparatus can be another network element such as a radio network controller or a spectrum controller.
  • 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.
  • 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:
  • S-NSSAI 1 Voice & Video call
  • P-CSCF and S-CSCF may support Slice Single-Network Slice Selection Assistance Information (S-NSSAI) 1 , S-NSSAI 2, and S-NSSAI 3.
  • S-NSSAI Slice Single-Network Slice Selection Assistance Information
  • 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.
  • 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.
  • FIG. 4 illustrates an example case, in which P-CSCF and S-CSCF support Slice S-NSSAI
  • S-NSSAI 1 S-NSSAI 1 , S-NSSAI 2, and S-NSSAI 3, and Slice S-NSSAI 1 is overloaded at P-CSCF.
  • 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.
  • the l-CSCF 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.
  • SIP Session Initiation Protocol
  • 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.
  • 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.
  • 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.
  • P-CSCF node/server
  • slice S-NSSAI 2 is overloaded at S-CSCF.
  • 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.
  • the l-CSCF During S-CSCF assignment/selection by l-CSCF, the l-CSCF has taken overload and slice level load into consideration.
  • SIP Session Initiation Protocol
  • P-CSCF Packet Control Function
  • S-CSCF Session Initiation Protocol
  • S-NSSAI 2 a particular slice at the S-CSCF
  • S-CSCF 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.
  • S-CSCF node/server
  • S-CSCF node/server
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • P-CSCF and S-CSCF add the details of slices which are overloaded when rejecting a UE initiated request.
  • 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
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.
  • 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.
  • 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.

Landscapes

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

Abstract

L'invention concerne un appareil qui comprend un moyen pour fournir, d'un équipement utilisateur à une entité de réseau prenant en charge une pluralité de tranches, une demande d'utilisation d'une première tranche de la pluralité de tranches et pour recevoir, au niveau de l'équipement utilisateur à partir de l'entité de réseau, une indication selon laquelle la première tranche est surchargée.
PCT/EP2021/080922 2020-11-13 2021-11-08 Traitement de surcharge de tranche Ceased WO2022101131A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202011049638 2020-11-13
IN202011049638 2020-11-13

Publications (1)

Publication Number Publication Date
WO2022101131A1 true WO2022101131A1 (fr) 2022-05-19

Family

ID=78649290

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2021/080922 Ceased WO2022101131A1 (fr) 2020-11-13 2021-11-08 Traitement de surcharge de tranche

Country Status (1)

Country Link
WO (1) WO2022101131A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190174536A1 (en) * 2016-08-12 2019-06-06 Huawei Technologies Co., Ltd. Wireless network access control method and apparatus
US20190223093A1 (en) * 2016-08-16 2019-07-18 Idac Holdings, Inc. Network slice reselection

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190174536A1 (en) * 2016-08-12 2019-06-06 Huawei Technologies Co., Ltd. Wireless network access control method and apparatus
US20190223093A1 (en) * 2016-08-16 2019-07-18 Idac Holdings, Inc. Network slice reselection

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhanced IMS to 5GC Integration (Release 17)", 6 December 2019 (2019-12-06), XP051838277, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/TSG_SA/TSGS_86/Docs/SP-191094.zip 23794-Diff_100_200.zip 23794-Diff_100_200.docx> [retrieved on 20191206] *
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 <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/SA2/Docs/S2%2D1906365%2Ezip> [retrieved on 20190515] *

Similar Documents

Publication Publication Date Title
EP3886502B1 (fr) Appareil, procédé et support lisible par ordinateur associés à des informations concernant scp(s) et sepp(s) stockés dans nrf
US20230413214A1 (en) Method, apparatus and computer program
CN118945216A (zh) 动态网络能力配置
US11444984B2 (en) Terminal interoperation using called-terminal functional characteristics
US11765618B2 (en) Wireless communication system
US20230396484A1 (en) Method, apparatus and computer program
WO2023214022A1 (fr) Appareil, procédé et programme informatique
US12028777B2 (en) Apparatus and method to indicate whether a node is tracking the location of a user equipment
WO2022101131A1 (fr) Traitement de surcharge de tranche
GB2621184A (en) Apparatus, method and computer program
EP4254996A1 (fr) Gestion d&#39;adresses de cuup partagées
US12477316B2 (en) Network slice local switching at a distributed unit
WO2024182935A1 (fr) Amélioration de service de dc d&#39;ims
WO2024103415A1 (fr) Appareil, procédé et programme d&#39;ordinateur
US20250358607A1 (en) Method and device for session negotiation to use ims data channel service
EP4465595A1 (fr) Déclenchement d&#39;une procédure d&#39;authentification entre un équipement mobile et un réseau central
US8891512B2 (en) Method of handling a VoIP connection of a mobile device and related communication device
WO2025180857A1 (fr) Appareil, procédé et programme informatique
US20230246767A1 (en) Method, apparatus and computer program for enabling a communication session
WO2025153757A1 (fr) Appareil, procédé et programme informatique pour exposition directe
KR20250029665A (ko) 무선 통신 시스템에서 IMS-DC(IP(internet protocol) multimedia subsystem-data channel) 서비스를 지원하는 방법 및 장치
KR20250065106A (ko) 데이터 스트림 멀티플렉싱을 지원하기 위한 방법 및 장치
WO2025087781A1 (fr) Appareil, procédé et programme informatique
KR20250046635A (ko) IMS-DC(IP(internet protocol) multimedia subsystem-data channel) 서비스에서 데이터 스트림 멀티플렉싱을 지원하기 위한 장치 및 방법
CN120034944A (zh) 装置、方法和计算机程序

Legal Events

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

Ref document number: 21809972

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21809972

Country of ref document: EP

Kind code of ref document: A1