WO2019024981A1 - Prise en charge d'attribution de ressource dans un réseau de communication radio - Google Patents

Prise en charge d'attribution de ressource dans un réseau de communication radio Download PDF

Info

Publication number
WO2019024981A1
WO2019024981A1 PCT/EP2017/069385 EP2017069385W WO2019024981A1 WO 2019024981 A1 WO2019024981 A1 WO 2019024981A1 EP 2017069385 W EP2017069385 W EP 2017069385W WO 2019024981 A1 WO2019024981 A1 WO 2019024981A1
Authority
WO
WIPO (PCT)
Prior art keywords
function
session
node
established
establishment request
Prior art date
Application number
PCT/EP2017/069385
Other languages
English (en)
Inventor
Yong Yang
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/EP2017/069385 priority Critical patent/WO2019024981A1/fr
Publication of WO2019024981A1 publication Critical patent/WO2019024981A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels

Definitions

  • the invention relates to methods for supporting resource allocation in a radio communication network having a control plane function separated from a user plane function, a control plane node for supporting resource allocation in a radio communication network having a control plane function separated from a user plane function, a user plane node for supporting resource allocation in a radio communication network having a control plane function separated from a user plane function, corresponding computer programs, and corresponding computer program products.
  • TDF traffic detection function
  • Sxa/b between a combined SGW-C/PGW-C and a combined SGW-U/PGW-U.
  • UP function can support
  • An architecture reference, from 3GPP TS 23.214, is 4.2.1 Non-roaming and roaming architectures.
  • Fig. 1 shows the architecture reference model in the case of separation between CP function and UP function. This architecture reference model covers non-roaming as well as home routed and local breakout roaming scenarios.
  • the architecture in Fig. 1 only depicts the case when the CP and UP functions of all SGW, PGW and TDF nodes are split. However, other cases when the CP and UP function of only one of these nodes is split while the CP and UP function of the other interfacing nodes are not split, e.g. PGWs CP and UP is split while SGWs CP and UP is not split, are also supported.
  • the split architecture of a node does not put any architectural requirements on the peer nodes with which it interfaces.
  • TDF is an optional functional entity.
  • the Gx interface is defined between the PGW-C and Policy and Charging Rules Function (PCRF) in the visited network.
  • PCRF Policy and Charging Rules Function
  • a combined SGW/PGW documented in TS 23.401 remains possible in a deployment with separated CP and UP functions. This is enabled by supporting an Sx interface with a common parameter structure for non- combined and combined cases.
  • Fig. 2 shows the architecture reference model for a combined SGW/PGW in the case of separation between control plane and user plane.
  • the drive in 3GPP is however aiming for a generic UP function, i.e. a 3GPP agnostic UP function.
  • the Sxa, Sxb and Sxc interfaces are however very 3GPP specific, and the assumed change seem to require that the UP function should know the it e.g. is a SGW-U.
  • a UP function for SGW e.g. needs to support N4 interface for 5G.
  • An object of the invention is to enable a user plane (UP) function to allocate proper resources for an Sx session, still allowing the UP function to be a 3GPP agnostic node.
  • a method for supporting resource allocation in a radio communication network having a control plane (CP) function separated from a UP function is performed in a CP node of the radio communication network and comprises sending a session establishment request to a UP function for a present interface between the CP function and the UP function, wherein the session
  • the establishment request comprises information associated with the Sx session to be established, and/or sending a session modification request to a UP function for a present interface between the CP function and the UP function, wherein the session modification request comprises information associated with the Sx session to be established.
  • the UP function By sending information associated with an Sx session to be established, from a control plane, CP, function being separate from a UP function, the UP function is enabled to allocate proper resources for the Sx session.
  • the method may further comprise deriving at least an Sx session attribute for the Sx session to be established between the CP function and the UP function based on user equipment, UE, context and/or operator policies.
  • the information may comprise one or more session attributes for the Sx session to be established.
  • the one or more session attributes may comprise: one or more UP function features to be used for the Sx session, and/or indication of one or more attribute parameters, which affect the UP function to allocate hardware and software resources.
  • the one or more attribute parameters may comprise one or more of the following UE context and operator polices: UE identity, mapped UE usage type, Dedicated Core Network Identity, ID, Single Network Slice Selection Assistance information, S-NSSAI, where the Slice/Service type identifies the expected Network Slice behaviour in terms of features and services, current radio access type, RAT, Access type, and Charging method.
  • the one or more attribute parameters may comprise a numeric value corresponding to hardware and software resources to allocate.
  • the information may be sent in an Sx Session Establishment Request and/or in an Sx Session Modification Request message.
  • a method for supporting resource allocation in a radio communication network having a CP function separated from a UP function is performed in a UP node of the radio communication network and comprises receiving a session
  • the session establishment request from a CP function for a present interface between the CP function and the UP function, wherein the session establishment request comprises information associated with the Sx session to be established, and/or receiving a session modification request from a CP function for a present interface between the CP function and the UP function, wherein the session modification request comprises information associated with the Sx session to be established.
  • the method may further comprise allocating one or more resources based on the received information.
  • the received information may comprise one or more session attributes for the Sx session.
  • the one or more session attributes may comprise: one or more UP function features to be used for the Sx session, and/or indication of one or more parameters, which affect the UP function to allocate hardware and software resources.
  • the one or more attribute parameters may comprise one or more of the following UE context and operator polices: UE identity, mapped UE usage type, Dedicated Core Network Identity, ID, Single Network Slice Selection Assistance information, S-NSSAI, where the Slice/Service type identifies the expected Network Slice behaviour in terms of features and services, current radio access type, RAT, Access type, and Charging method.
  • the one or more attribute parameters may comprise a numeric value corresponding to hardware and software resources to allocate.
  • the information may be received in an Sx Session Establishment Request and/or in an Sx Session Modification Request message.
  • a CP node for supporting resource allocation in a radio communication network having a CP function separated from a UP function.
  • the CP node comprises a processor and a computer program product storing instructions that, when executed by the processor, causes the CP node to send a session establishment request to a UP function for a present interface between the CP function and the UP function, wherein the session establishment request comprises information associated with the Sx session to be established, and/or send a session modification request to a UP function for a present interface between the CP function and the UP function, wherein the session modification request comprises information associated with the Sx session to be established.
  • a UP node for supporting resource allocation in a radio communication network having a CP function separated from a UP function.
  • the UP node comprises a processor, and a computer program product storing instructions that, when executed by the processor, causes the UP node to receive a session establishment request from a CP function for a present interface between the CP function and the UP function, wherein the session establishment request comprises
  • a control CP node for supporting resource allocation in a radio communication network having a CP function separated from a UP function.
  • the CP node comprises a communication manager for sending a session establishment request to a UP function for a present interface between the CP function and the UP function, wherein the session establishment request comprises information associated with the Sx session to be established, and/or for sending a session
  • the session modification request to a UP function for a present interface between the CP function and the UP function, wherein the session modification request comprises information associated with the Sx session to be established.
  • a UP node for supporting resource allocation in a radio communication network having a CP function separated from a UP function.
  • the UP node comprises a communication manager for receiving a session establishment request from a CP function for a present interface between the CP function and the UP function, wherein the session establishment request comprises information associated with the Sx session to be established, and/or for receiving a session modification request from a CP function for a present interface between the CP function and the UP function, wherein the session modification request comprises information associated with the Sx session to be established.
  • a seventh aspect there is presented a computer program for supporting resource allocation in a radio communication network having a CP function separated from a UP function.
  • the computer program is presented.
  • a computer program for supporting resource allocation in a radio communication network having a CP function separated from a UP function.
  • UP node comprising computer program code which, when run on a UP node, causes the UP node to receive a session establishment request from a CP function for a present interface between the CP function and the UP function, wherein the session establishment request comprises information associated with the Sx session to be established, and/or to receive a session modification request from a CP function for a present interface between the CP function and the UP function, wherein the session modification request comprises information associated with the Sx session to be established.
  • a computer program product comprising a computer program and a computer readable storage means on which the computer program is stored is also presented.
  • all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a/an/the element, apparatus, component, means, step, etc.” are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.
  • FIG. 1 schematically illustrates an architecture reference model in the case of separation between control plane and user plane
  • Fig. 2 schematically illustrates an architecture reference model for a combined SGW/PGW in the case of separation between control plane and user plane
  • Fig. 3 is a signalling diagram schematically illustrating Sx session handling as presented herein;
  • Fig. 4 is a flowchart schematically illustrating an embodiment for a control plane presented herein
  • Fig. 5 is a flowchart schematically illustrating an embodiment for a user plane presented herein;
  • Fig. 6 is a schematic diagram illustrating some components of a control plane presented herein;
  • Fig. 7 is a schematic diagram illustrating some components of a user plane presented herein;
  • Fig. 8 is a schematic diagram showing functional modules of a control plane presented herein.
  • Fig. 9 is a schematic diagram showing functional modules of a user plane presented herein. DETAILED DESCRIPTION
  • UP control plane
  • SGW serving gateway
  • PGW packet gateway
  • TDF traffic detection function
  • SGW-U is required to support the Buffering Action Rule, and parameters related to handle the Downlink data buffering, and on the other hand a SGW-U need not handle the quality of service (QoS) Enforcement Rule.
  • QoS quality of service
  • PGW-U is required to perform counting packets and applying QoS enforcement per Service Data Flow (SDF), per bearer
  • Different features implemented in an UP function also have different requirements on hardware and software. To e.g. handle downlink buffering efficiently and avoiding that packets are dropped, it is efficient to have more memory to store Downlink user data. To e.g. be able to handle more complicated routing, e.g. to route UP packets based on applications, which requires deep packet inspection (DPI), this requires more central processing unit (CPU) power.
  • DPI deep packet inspection
  • the UP function thus needs to know characteristics or attributes of the Sx session to be established in order to serve the Sx Session better.
  • 3GPP is aiming for a generic UP function, i.e. a 3GPP agnostic UP function, while Sxa, Sxb and Sxc are very 3GPP specific.
  • the UP function should e.g. thus know that it is a SGW-U.
  • a UP function needs to support the N4 interface for 5G.
  • Sxa/Sxb/Sxc these requirements are for the CP function, not for the UP function. 3. If the UP function uses Sx Session type information, i.e. Sxa, Sxb or Sxc, to validate the presence of certain IEs, it will lead inter-operability issues, as the UP function doesn't have a complete picture whether the IE shall be present or not.
  • the Sxa, Sxb, Sxc and Sxab interfaces are too coarse information, which just represents reference points between different Packet Forwarding Control Protocol (PFCP) entities. They cannot be used for allocating proper resource, e.g. for hardware (CPU, memory etc.), software (e.g. different modelling), even connectivity (some parts of the UP function may have dedicated ingress and egress path with different band width).
  • PFCP Packet Forwarding Control Protocol
  • a UP function knows it is a PGW-U, i.e. Sxb is applicable, and validates the presence of IE "Volume Quota", which is specified to be applicable to Sxb. This is however incorrect, the UP function cannot know that this IE is only valid for an Sx Session of which the corresponding PDN connection is charged in real time, i.e. on-line charging.
  • UP function is implemented utilizing network virtualization on a cloud based environment, regardless whether it is built by using virtual machine on top of a kind of middleware then on a common hardware, or when using container solutions, where each of container "owns" exclusively some hardware, so that a UP function can be made of a number of container which may have quite different characteristics, e.g. container 1 may have 10 CPU and 2MB memory while container 2 may have 2 CPU and 1000 MB memory. In such scenarios it may be reasonable to provide the UP function with the Sx Session characteristics.
  • Sx Session Attributes may instead be introduced.
  • the IE, Sx session attributes, may be encoded with bitmap style, indicating what UP features, and what characteristics of hardware/software resource are required for the given Sx Session.
  • Sx Session attributes may be extendible and should not be limited by the current defined features.
  • the CP function may derive such Sx Session Attributes based on e.g.: user equipment, UE, identity (e.g. International Mobile Subscriber Identity, IMSI), wherein an ending of 100-1000 of the UE identity may e.g. identify machine type, such as traffic sign or water meter; mapped UE usage type, e.g. corresponding operating condition when roaming from one country to another;
  • identity e.g. International Mobile Subscriber Identity, IMSI
  • IMSI International Mobile Subscriber Identity
  • Access Point Name of the PDN that a UE is attempting to access is supported UP function features which is obtained during Sx association setup procedure;
  • S-NSSAI Single Network Slice Selection Assistance information
  • SST Slice/Service type
  • RAT radio access technology
  • UP function features IE indicates the features currently supported by the UP function as specified in 8.2.25 of 3GPP TS 29.244 as presented in the following table.
  • the UP function features IE takes the form of a bitmask where each bit set indicates that the corresponding feature is supported. Spare bits shall be ignored by the receiver. The same bitmask is defined for all PFCP interfaces.
  • Feature Octet/Bit The octet and bit number within the Supported-Features IE, e.g. "5 / 1".
  • Feature A short name that can be used to refer to the octet/bit and to the feature.
  • Interface A list of applicable interfaces to the feature.
  • Fig. 3 depicts in detail, how the new IE may be used during Sx Session establishment.
  • the CP function first sends an Sx association setup request to the UP function.
  • the UP function returns an Sx association setup response, with all UP function features.
  • the CP function sends an Sx session
  • the UP function returns an Sx session establishment response.
  • the UP function selected earlier may e.g. be a combined SGW-U/PGW-U, but due to UE mobility a new UP function (SGW-U) is selected.
  • SGW-U new UP function
  • the old Sx session then needs to be modified, e.g. it doesn't require any Downlink data handling, and the updated Sx Session Attributes are thus provided to the old UP function.
  • the CP then sends an Sx session modification request, including the new IE - Sx session attribute, with updated information.
  • the UP function returns an Sx session modification response.
  • the Sx Session attributes IE indicates the attributes of the Sx Session to be established, i.e. the Sx Session may require a list of UP function features, which are a subset of features that the UP function reported during Sx association setup procedure.
  • the Sx Session attributes may include information related to UE usage type, e.g. information mapped from UE usage type.
  • the Sx session attribute may be coded as shown in the following table.
  • the UE usage type is here used as a main parameter to select a proper dedicated core network, which has specific characteristics/functions or scaling, to isolate specific UEs or subscribers (e.g. machine-to-machine
  • M2M mobile broadband subscribers
  • subscribers belonging to a specific enterprise or separate administrative domain, etc. subscribers to a specific enterprise or separate administrative domain, etc.
  • the presented way to enable a UP function to allocate propter resources for an Sx session is an efficient mechanism, without breaking the principle that a UP function is a 3GPP agnostic node.
  • the mechanism provides required attributes information of the Sx session to be established from the CP function to the UP function.
  • a method, according to an embodiment, for supporting resource allocation in a radio communication network having a CP function separated from a UP function is presented with reference to Fig. 4.
  • the method is performed in a CP node of the radio communication network and comprises sending S110 a session establishment request to a UP function for a present interface between the CP function and the UP function, wherein the session
  • the method may further comprise deriving at least an Sx session attribute for the Sx session to be established between the CP function and the UP function based on UE context and/or operator policies. This may e.g. be performed during an Sx association setup.
  • the information may comprise one or more session attributes for the Sx session to be established.
  • the one or more session attributes may comprise: one or more UP function features to be used for the Sx session, and/or indication of one or more attribute parameters, which affect the UP function to allocate hardware and software resources.
  • the one or more attribute parameters may comprise one or more of the following UE context and operator policies: user equipment, UE, identity, mapped UE usage type, Dedicated Core Network Identity, ID, Single Network Slice Selection
  • the one or more attribute parameters may comprise a numeric value corresponding to hardware and software resources to allocate.
  • Each attribute parameter may e.g. be mapped to a numeric value, e.g. each parameter type may be mapped to a range of values, such as IMSI range 1, 2, 3, UE usage type 10, 11, 12, and dedicated core network (DCN) ID 101, 102, 103.
  • DCN dedicated core network
  • the information may be sent in an Sx Session Establishment Request and/or in an Sx Session Modification Request message.
  • a method, according to an embodiment, for supporting resource allocation in a radio communication network having a CP function separated from a UP function is presented with reference to Fig. 5.
  • the method is performed in a UP node of the radio communication network and comprises receiving S200 a session establishment request from a CP function for a present interface between the CP function and the UP function, wherein the session
  • the establishment request comprises information associated with the Sx session to be established, and/or receiving S200 a session modification request from a CP function for a present interface between the CP function and the UP function, wherein the session modification request comprises information associated with the Sx session to be established.
  • the method may further comprise allocating S210 one or more resources based on the received information.
  • the received information may comprise one or more session attributes for the Sx session.
  • the one or more session attributes may comprise: one or more UP function features to be used for the Sx session, and/or indication of one or more parameters, which affect the UP function to allocate hardware and software resources.
  • the one or more attribute parameters may comprise one or more of the following UE context and operator policies: UE identity, mapped UE usage type, Dedicated Core Network Identity, ID, Single Network Slice Selection Assistance information, S-NSSAI, where the Slice/Service type (SST) identifies the expected Network Slice behaviour in terms of features and services, current radio access type, RAT, Access type (3GPP access or non-3GPP access), and Charging method (online/offline charging).
  • the one or more attribute parameters may comprise a numeric value corresponding to hardware and software resources to allocate.
  • the information may be received in an Sx Session Establishment Request and/or in an Sx Session Modification Request message.
  • a CP node according to an embodiment for supporting resource allocation in a radio communication network having a CP function separated from a UP function, is presented with reference to Fig. 6.
  • the CP node comprises a processor 10 and a computer program product 12, 13 storing instructions that, when executed by the processor, causes the CP node to send S110 a session establishment request to a UP function for a present interface between the CP function and the UP function, wherein the session
  • the establishment request comprises information associated with the Sx session to be established, and/or to send S110 a session modification request to a UP function for a present interface between the CP function and the UP function, wherein the session modification request comprises information associated with the Sx session to be established.
  • the CP node may further be caused to derive S100 at least an Sx session attribute to be established for the present interface between the CP function and the UP function based on UE context and/or operator policies. This may e.g. be performed during an Sx association setup.
  • the information may comprise one or more session attributes for the Sx session to be established.
  • the one or more session attributes may comprise: one or more UP function features to be used for the Sx session, and/or indication of one or more attribute parameters, which affect the UP function to allocate hardware and software resources.
  • the one or more attribute parameters may comprise one or more of the following UE context and operator polices: user equipment, UE, identity, mapped UE usage type, Dedicated Core Network Identity, ID, Single Network Slice Selection
  • the one or more attribute parameters may comprise a numeric value corresponding to hardware and software resources to allocate.
  • the information may be sent in an Sx Session Establishment Request and/or in an Sx Session Modification Request message.
  • Fig. 6 is a schematic diagram showing some components of the CP node.
  • the processor 10 may be provided using any combination of one or more of a suitable central processing unit, CPU, multiprocessor, microcontroller, digital signal processor, DSP, application specific integrated circuit etc., capable of executing software instructions of a computer program 14 stored in a memory.
  • the memory can thus be considered to be or form part of the computer program product 12.
  • the processor 10 may be configured to execute methods described herein with reference to Fig. 6.
  • the memory may be any combination of read and write memory, RAM, and read only memory, ROM.
  • the memory may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.
  • a second computer program product 13 in the form of a data memory may also be provided, e.g. for reading and/or storing data during execution of software instructions in the processor 10.
  • the data memory can be any combination of read and write memory, RAM, and read only memory, ROM, and may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.
  • the data memory may e.g. hold other software instructions 15, to improve functionality for the CP node.
  • the CP node may further comprise an input/output (I/O) interface 11 including e.g. a user interface.
  • the CP may further comprise a receiver configured to receive signalling from other nodes, and a transmitter configured to transmit signalling to other nodes (not illustrated).
  • Other components of the CP are omitted in order not to obscure the concepts presented herein.
  • Fig. 8 is a schematic diagram showing functional blocks of the CP node.
  • the modules may be implemented as only software instructions such as a computer program executing in the cache server or only hardware, such as application specific integrated circuits, field programmable gate arrays, discrete logical components, transceivers, etc. or as a combination thereof. In an alternative embodiment, some of the functional blocks may be implemented by software and other by hardware.
  • the modules correspond to the steps in the methods illustrated in Fig. 4, comprising a determination manager unit 80 and a communication manager unit 81.
  • a determination manager unit 80 and a communication manager unit 81.
  • these modules do not necessarily correspond to process modules, but can be written as instructions according to a
  • the determination manger 80 is for supporting resource allocation in a radio communication network having a CP function separated from a UP function.
  • This module corresponds to the derive step S100 of Fig. 4.
  • This module can e.g. be implemented by the processor 10 of Fig. 6, when running the computer program.
  • the communication manger 81 is for supporting resource allocation in a radio communication network having a CP function separated from a UP function.
  • This module corresponds to the send step S110 of Fig. 4.
  • This module can e.g. be implemented by the processor 10 of Fig. 6, when running the computer program.
  • Fig. 7 is a schematic diagram showing some components of the UP node.
  • the processor 20 may be provided using any combination of one or more of a suitable central processing unit, CPU, multiprocessor, microcontroller, digital signal processor, DSP, application specific integrated circuit etc., capable of executing software instructions of a computer program 24 stored in a memory.
  • the memory can thus be considered to be or form part of the computer program product 22.
  • the processor 20 may be configured to execute methods described herein with reference to Fig. 5.
  • the memory may be any combination of read and write memory, RAM, and read only memory, ROM.
  • the memory may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.
  • a second computer program product 23 in the form of a data memory may also be provided, e.g. for reading and/or storing data during execution of software instructions in the processor 20.
  • the data memory can be any combination of read and write memory, RAM, and read only memory, ROM, and may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.
  • the data memory may e.g. hold other software instructions 25, to improve functionality for the UP node.
  • the UP node may further comprise an input/output (I/O) interface 21 including e.g. a user interface.
  • the UP may further comprise a receiver configured to receive signalling from other nodes, and a transmitter configured to transmit signalling to other nodes (not illustrated).
  • Other components of the UP are omitted in order not to obscure the concepts presented herein.
  • Fig. 9 is a schematic diagram showing functional blocks of the UP.
  • the modules may be implemented as only software instructions such as a computer program executing in the cache server or only hardware, such as application specific integrated circuits, field programmable gate arrays, discrete logical components, transceivers, etc. or as a combination thereof.
  • some of the functional blocks may be
  • modules correspond to the steps in the methods illustrated in Fig. 5, comprising a determination manager unit 90 and a communication manager unit 91.
  • a determination manager unit 90 and a communication manager unit 91.
  • these modules do not necessarily correspond to process modules, but can be written as instructions according to a
  • the determination manger 90 is for supporting resource allocation in a radio communication network having a CP function separated from a UP function. This module corresponds to the allocate step S210 of Fig. 5. This module can e.g. be implemented by the processor 20 of Fig. 7, when running the computer program.
  • the communication manger 91 is for supporting resource allocation in a radio communication network having a CP function separated from a UP function.
  • This module corresponds to the receive step S200 of Fig. 5.
  • This module can e.g. be implemented by the processor 20 of Fig. 7, when running the computer program.
  • a computer program product 12, 13, 22, 23 comprising a computer program 14, 15, 24, 25 and a computer readable storage means on which the computer program 14, 15, 24, 25 is stored, is also presented.

Landscapes

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

Abstract

La présente invention concerne un procédé destiné à prendre en charge une attribution de ressource dans un réseau de communication radio ayant une fonction de plan de commande (CP) séparée d'une fonction de plan d'utilisateur (UP) Le procédé est réalisé dans un nœud CP du réseau de communication radio et consiste : à envoyer (S110) une demande d'établissement de session à une fonction UP pour une interface présente entre la fonction CP et la fonction UP, la demande d'établissement de session comprenant des informations associées à la session Sx à établir, et/ou à envoyer (S110) une demande de modification de session à une fonction UP pour une interface présente entre la fonction CP et la fonction UP, la demande de modification de session comprenant des informations associées à la session Sx à établir. L'invention concerne également un nœud CP, un nœud UP, un programme informatique et un produit programme d'ordinateur.
PCT/EP2017/069385 2017-08-01 2017-08-01 Prise en charge d'attribution de ressource dans un réseau de communication radio WO2019024981A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/069385 WO2019024981A1 (fr) 2017-08-01 2017-08-01 Prise en charge d'attribution de ressource dans un réseau de communication radio

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/069385 WO2019024981A1 (fr) 2017-08-01 2017-08-01 Prise en charge d'attribution de ressource dans un réseau de communication radio

Publications (1)

Publication Number Publication Date
WO2019024981A1 true WO2019024981A1 (fr) 2019-02-07

Family

ID=59631736

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/069385 WO2019024981A1 (fr) 2017-08-01 2017-08-01 Prise en charge d'attribution de ressource dans un réseau de communication radio

Country Status (1)

Country Link
WO (1) WO2019024981A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022002419A1 (fr) * 2020-06-30 2022-01-06 Telefonaktiebolaget Lm Ericsson (Publ) Gestion d'identifiant de session pour des passerelles de plan d'utilisateur colocalisées
JP2022520040A (ja) * 2019-02-14 2022-03-28 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 拡張されたｕｐ機能要求ｐｆｃｐアソシエーション解放

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017078776A1 (fr) * 2015-11-06 2017-05-11 Intel IP Corporation Attribution de ressources d'un plan utilisateur
US20170208634A1 (en) * 2016-01-18 2017-07-20 Samsung Electronics Co., Ltd Resource assignment for general packet radio service tunneling protocol (gtp) entities in 5g

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017078776A1 (fr) * 2015-11-06 2017-05-11 Intel IP Corporation Attribution de ressources d'un plan utilisateur
US20170208634A1 (en) * 2016-01-18 2017-07-20 Samsung Electronics Co., Ltd Resource assignment for general packet radio service tunneling protocol (gtp) entities in 5g

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interface between the Control Plane and the User Plane of EPC Nodes; Stage 3 (Release 14)", 3GPP STANDARD ; TECHNICAL SPECIFICATION ; 3GPP TS 29.244, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG4, no. V14.0.0, 19 June 2017 (2017-06-19), pages 1 - 137, XP051298808 *
HUAWEI: "Corrections and clean up for 23.401 related message flows", vol. SA WG2, no. Busan, Korea; 20170327 - 20170331, 6 June 2017 (2017-06-06), XP051283286, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/SA/Docs/> [retrieved on 20170606] *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2022520040A (ja) * 2019-02-14 2022-03-28 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 拡張されたｕｐ機能要求ｐｆｃｐアソシエーション解放
JP7209105B2 (ja) 2019-02-14 2023-01-19 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 拡張されたｕｐ機能要求ｐｆｃｐアソシエーション解放
WO2022002419A1 (fr) * 2020-06-30 2022-01-06 Telefonaktiebolaget Lm Ericsson (Publ) Gestion d'identifiant de session pour des passerelles de plan d'utilisateur colocalisées

Similar Documents

Publication Publication Date Title
EP2824951B1 (fr) Procédé, dispositif et système pour le marquage de paquets de données
JP5507709B2 (ja) Ｐｃｒｆがセル容量不足に自律的に応答するための方法
EP2242205A1 (fr) Procédé pour sélectionner une entité à fonction de règles de politique et de facturation dans le scénario sans itinérance
EP3110197B1 (fr) Procédé de détection et de contrôle d&#39;application dans un scénario d&#39;itinérance et une v-pcrf
EP2648367B1 (fr) Procédé et système pour réaliser la détection et le contrôle d&#39;applications dans une session ip-can prenant en charge la double pile
CN102238517B (zh) 机器类通信事件上报方法、装置及系统
EP2421326A1 (fr) Procédé et appareil destinés à obtenir l&#39;identification d&#39;un groupe de dispositifs de communication de type machine
CN102045695B (zh) 一种获取mtc服务器地址信息的方法及系统
US10949315B2 (en) Performance measurements related to virtualized resources
WO2014149059A1 (fr) Autorisation de surveillance et de rapport pour application de politique dynamique dans des réseaux de vente en gros multi-opérateur
CN102238507A (zh) 确定策略和计费规则功能的方法及系统
EP2642690A1 (fr) Fonction de facturation et politique gérées par un seul opérateur pour des réseaux de convergence fixe-mobile
US9485106B2 (en) Method for processing TDF session and PCRF
WO2019024981A1 (fr) Prise en charge d&#39;attribution de ressource dans un réseau de communication radio
CN106507382B (zh) 一种Diameter消息路由方法和路由代理节点
CN101494554B (zh) 上报策略模型信息的方法和设备
US9532205B2 (en) Method and system for identifying application detection and control function mode
US10051638B2 (en) Method for enhanced policy and charging control in telecommunications networks
CN110890967A (zh) 一种计费处理方法、网元及网络系统
CN102238510B (zh) 机器类通信的策略下发方法及系统
CN104380783A (zh) 一种流量监测的方法、装置及系统
JP2014531159A (ja) 潜在的な複数のエンティティと互いに関連するメッセージを処理すること

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: 17752329

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: 17752329

Country of ref document: EP

Kind code of ref document: A1