WO2019081005A1 - Garantie d'homogénéité de tranche e2e grâce à des segments de tranche flexibles - Google Patents

Garantie d'homogénéité de tranche e2e grâce à des segments de tranche flexibles

Info

Publication number
WO2019081005A1
WO2019081005A1 PCT/EP2017/077257 EP2017077257W WO2019081005A1 WO 2019081005 A1 WO2019081005 A1 WO 2019081005A1 EP 2017077257 W EP2017077257 W EP 2017077257W WO 2019081005 A1 WO2019081005 A1 WO 2019081005A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
slice
management entity
network
nssmf
Prior art date
Application number
PCT/EP2017/077257
Other languages
English (en)
Inventor
Emmanouil Pateromichelakis
Konstantinos Samdanis
Xueli AN
Chenghui Peng
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to PCT/EP2017/077257 priority Critical patent/WO2019081005A1/fr
Publication of WO2019081005A1 publication Critical patent/WO2019081005A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements

Definitions

  • the present invention relates to the field of wireless communications, and more particularly to the field of network slicing.
  • Network Slicing is a key enabler for fifth generation (5G) which allows new business value creation opportunities by accommodating verticals, application providers and other third parties. In particular, it enables a concurrent deployment of multiple logical, self-contained networks on a common physical infrastructure with diverse business demands.
  • the technical report 3GPP TR 23.501 (Release 15), entitled: “System architecture for the 5G system” defines a network slice as a complete logical network comprising a set of Network Functions (NFs) and corresponding resources, which are necessary to provide certain network capabilities and network characteristics.
  • a network slice may include both a Radio Access Network (RAN) or Access Network (AN), a Transport Network (TN) and a Core Network (CN).
  • RAN Radio Access Network
  • AN Access Network
  • TN Transport Network
  • CN Core Network
  • Network slicing accommodates distinct Service Level Agreements (SLAs) and supports a fully customized network resource provision translated into different End-to-End (E2E) Key Performance Indicators (KPIs), thereby transforming the static "one size fits all" paradigm to a network of capabilities in which logical networks are created on- demand with the appropriate isolation, and to a resource optimization in order to serve a particular service type.
  • a Network Slice Instance (NSI), which represents the realization of a network slice for a particular service, may be defined as a set of NFs and resources for these NFs arranged and configured, thereby forming a complete logical network to meet certain network characteristics.
  • 5G mobile networks are envisioned to be heterogeneous by integrating all previous RAN generation and, at the same time, introducing new technologies such as New Radio (NR) and millimeter wave (mmWave).
  • 5G offers a variety of service assurance even when the bandwidth requirements and selected backhaul paths are the same, due to different radio conditions (i.e., cell center/cell edge, weather conditions), access technologies (e.g., LTE, mmWave, WiFi) which determine the reliability and may use different backhaul paths, backhaul technologies (e.g., base station (BS) connected via optical or microwave) connected via different backhaul topologies, and connectivity options (e.g., dual connectivity, Coordinated Multipoint (CoMP) or conventional single path connectivity, Cloud- RAN (C-RAN) connectivity).
  • BS base station
  • C-RAN Cloud- RAN
  • a network slice may be requested to serve a large geographic area (e.g., Munich). In such a case, it may search among different types of equipment and technology across the RAN, CN and TN (e.g., BackHaul/FrontHaul (BH/FH)), with diverse characteristics.
  • BH/FH BackHaul/FrontHaul
  • SLA homogeneous service provision
  • CN CN
  • TN e.g., BackHaul/FrontHaul
  • AIVs Acoustic Induced Vibrations
  • the invention relates to a cross-domain slice management entity (NSMF) for enabling a service provision (SLA) across an end-to-end (E2E) network slice.
  • the cross-domain slice management entity is configured to create slice segments for the E2E network slice based on a slice request and on domain status information from a domain ((R) AN, TN, CN) within the E2E network slice, to configure the slice segments such that all slice segments have an identical service provision, to map the configured slice segments to each domain across the E2E network slice amongst at least a radio access network (RAN) domain, a transport network (TN) domain and a core network (CN) domain, as to obtain domain specific mapping information, and to send the domain specific mapping information to respective domain specific management entities (AN-NSSMF, TN- NSSMF, CN-NSSMF) using dedicated interfaces.
  • RAN radio access network
  • TN transport network
  • CN core network
  • slice segments for the E2E network slice covering a geographical area, which are configured to have each an identical service provision (e.g., an equal SLA/QoS).
  • the slice segments may be defined as a group of slice resources with equal service provision (SLA/QoS).
  • a slice segment may be defined as a set of network functions (e.g., RAN-FH/BH-CN) and resources for these network functions that belong to a network slice and are arranged and configured within the specified geographical area in order to provide a controlled service provision (e.g., SLA).
  • slice segments allows to simplify the problem by dividing it into smaller E2E instances with nearly-identical service provision (but not lower than the desired service provision), based on the radio/propagation conditions, the BH/FH resource availability and the CN resource utilization.
  • the benefits of the proposed solution may be the provision of an equal service (e.g., QoS/SLA) over an entire geographical area with no over- provisioning of resources, and the fact that a slice segment defines a way of SLA treatment and thereby allows to avoid any calculation per user treatment to ensure the desired QoS.
  • QoS/SLA equal service
  • the slice request comprises at least one of slice service provision requirement and slice coverage requirement
  • the domain status information comprises at least one of statistics on a status and/or load of the domains, statistics on a traffic distribution, density and mobility patterns of users per slice area, user location
  • the domain specific mapping information comprises slice segment information containing a slice segment identifier for each slice segment, and configuration information containing radio resource management (RRM) policies for users in an area covered by a slice segment.
  • RRM radio resource management
  • the cross-domain slice management entity is configured to send configuration parameters based on a user distribution to a RAN domain management entity (AN-NSSMF).
  • the domain specific mapping information sent to the respective domain specific management entities is RAN domain mapping information, which is sent as a slice segment-to-RAN mapping message to the RAN domain management entity (AN-NSSMF), and/or TN domain mapping information, which is sent as a slice segment-to-TN mapping message to a TN domain management entity (TN-NSSMF), and/or CN domain mapping information, which is sent as a slice segment-to-CN mapping message to a CN domain management entity (CN-NSSM F).
  • RAN domain mapping information which is sent as a slice segment-to-RAN mapping message to the RAN domain management entity (AN-NSSMF)
  • TN-NSSMF TN domain management entity
  • CN-NSSM F CN domain management entity
  • the TN domain mapping information is sent from a mobile cross-domain slice management entity (e.g., NSMF) directly and/or via a fixed cross-domain slice management entity or via another operating entity (e.g., an entity of a same level as the slice management entity).
  • a mobile cross-domain slice management entity e.g., NSMF
  • another operating entity e.g., an entity of a same level as the slice management entity.
  • the invention relates to a domain specific management entity (AN- NSSMF, TN-NSSMF, CN-NSSMF) as specified in the first aspect and/or any one of the domain specific management entity (AN- NSSMF, TN-NSSMF, CN-NSSMF) as specified in the first aspect and/or any one of the domain specific management entity (AN- NSSMF, TN-NSSMF, CN-NSSMF) as specified in the first aspect and/or any one of the domain specific management entity (AN- NSSMF, TN-NSSMF, CN-NSSMF) as specified in the first aspect and/or any one of the domain specific management entity (AN- NSSMF, TN-NSSMF, CN-NSSMF) as specified in the first aspect and/or any one of the domain specific management entity (AN- NSSMF, TN-NSSMF, CN-NSSMF) as specified in the first aspect and/or any one of the domain specific management entity (AN- NSSMF, TN-NSSMF,
  • the domain specific management entity is configured to match user distributions to configured slice segments, to store radio resource management (RRM) policies for users in an area covered by a slice segment, and to send slice segment information comprising the RRM policies to a corresponding domain (AN, TN, CN).
  • RRM radio resource management
  • the invention relates to a domain ((R) AN, TN, CN), which is configured to obtain, from a corresponding domain specific management entity as claimed in the second aspect, slice segment information comprising RRM policies, and to apply, at a node of the domain, a RRM policy amongst the RRM policies.
  • the node of the domain is configured to trigger a change in the applied RRM policy in order to support the configured slice segments.
  • the node of the domain triggers the change in the applied RRM policy by sending a message (RRM_CoMP_Policy_Trigger message) to the corresponding domain specific management entity.
  • the invention relates to a method for enabling a service provision (SLA) across an end-to-end (E2E) network slice.
  • the method is performed at a cross-domain slice management entity and comprises the step of creating slice segments for the E2E network slice based on a slice request and on domain status information from a domain ((R) AN, TN, CN) within the E2E network slice, the step of configuring the slice segments such that all slice segments have an identical service provision, the step of mapping the configured slice segments to each domain across the E2E network slice amongst at least a radio access network (RAN) domain, a transport network (TN) domain and a core network (CN) domain, as to obtain domain specific mapping information, and the step of sending the domain specific mapping information to respective domain specific management entities (AN-NSSMF, TN-NSSMF, CN-NSSMF) using dedicated interfaces.
  • RAN radio access network
  • TN transport network
  • CN core network
  • the invention relates to a method, which is performed at a domain specific management entity and comprises the step of matching user distributions to configured slice segments, the step of storing radio resource management (RRM) policies for users in an area covered by a slice segment, and the step of sending slice segment information comprising the RRM policies to a corresponding domain (AN, TN, CN).
  • RRM radio resource management
  • the invention relates to a method, which is performed at a domain and comprises the step of obtaining, from a corresponding domain specific management entity, slice segment information comprising RRM policies, and the step of applying, at a node of the domain, a RRM policy amongst the RRM policies.
  • the invention relates to a computer program product comprising a program code for performing a method according to any one of fourth, fifth and sixth aspects when executed on a computer. Thereby, the method can be performed in an automatic and repeatable manner.
  • the computer program can be performed by the above apparatuses.
  • chip modules or based on a signal processing device or chip controlled by a software routine or program stored in a memory, written on a computer-readable medium or downloaded from a network such as the Internet.
  • Fig. 1 shows an exemplary scenario of a slice segment creation based on a user location
  • Fig. 2 shows a first flow chart (2-A) illustrating an allocation of weight to nodes and a second flow chart (2-B) illustrating an adapted graph-based solution to find a number of maximal cliques covering an entire graph, according to an embodiment of the present invention
  • Fig. 3 shows a message sequence chart (MSC) for slice instantiation and slice segment mapping per domain ((R) AN, TN, CN), according to an embodiment of the present invention
  • Fig. 4 shows a schematic signaling chart illustrating a transmission of a TN domain mapping information from a mobile cross-domain slice management entity (NSMF) towards a TN domain management entity (TN-NSSMF) according to two options, according to an embodiment of the present invention
  • Fig. 5 shows a message sequence chart (MSC) illustrating a RRM CoM P policy application at a RAN node, according to an embodiment of the present invention.
  • the gist of the present invention is to create and configure slice segments at a cross-domain slice management entity (or unit) in order to allocate an E2E network slice across RAN and/or TN and/or CN with equal area-KPIs.
  • Fig. 1 shows an exemplary scenario of a slice segment creation based on a user location distribution, according to an embodiment of the present invention.
  • the left side of the drawing shows a location distribution of users (e.g., User Equipment (UE) devices) in an area covered by a slice x.
  • a slice management entity e.g., Network Slice
  • NMF Network Slice Su bnet Management Function
  • SSMF Network Slice Su bnet Management Function
  • the right part of the drawing shows the clustering of the geographical area covered by the slice x into four slice segments or clusters (numbered from 1 to 4) with different configuration policies.
  • the slice management entity may create all possible combinations of slice segments and configurations (e.g., for low, medium, high load), and the Base Stations (BSs) may then apply one of the configurations based on the real-time information about the connected users. It shall be also noted that, for different slices, different slice segments and configurations may be defined based on the target KPI/SLA.
  • the criteria for the slice segment creation and the slice segment dimensioning as areas in which the involved entities may be identified by some potential SLA parameters and QoS-related measurements, and also by the expected/estimated location distribution of users in a geographical area covered by a slice.
  • those criteria may comprise a Signal-to-lnterference-plus-Noise Ratio (SINR) (path loss and interference), a spectral efficiency, an uplink/downlink load at a BS, an access channel delay (connectivity density), a throughput (difference between BH and radio), a delay (re-transmission probability (for radio), processing delay/queuing (e.g., for router, switch), probe or in traffic (for E2E)), and reliability (percentage of traffic successfully delivered).
  • SINR Signal-to-lnterference-plus-Noise Ratio
  • the expected/estimated location distribution of the users may be known from the actual/expected positioning of users in a geographical area based on mobility patterns and/or historical data/statistics on the distribution of users in this area and/or at worst an assumption of a uniform distribution over the slice coverage area.
  • the configuration of the slice segments for the E2E network slice may be mainly based on parameters and user location distributions and/or patterns based on statistics, in order to ensure an equal area-QoS and/or SLA within each slice segment.
  • a core part of the configuration is to define the parameters (e.g., size, coverage) of the slice segments in such a way that identical service provision (i.e., equal area-KPI) can be achieved per slice cluster (i.e., per slice segment).
  • the criteria for the selection of the cluster parameterization may, for example, comprise a location distribution of users per slice segment in an entire area and per BS area, BH constraints (e.g., ideal and/or non-ideal BH, type, topology, availability, dynamicity), a target KPI per slice, an estimated KPI achieved according to slice requirements, a user's estimated SIN (initial selection of serving BS by Reference Signal Received Power (RSRP) and/or Reference Signal Received Quality (RSRQ)), a spectral efficiency and/or a min- max throughput using SINR and min-max allocated bandwidth, a delay (e.g., probability of retransmissions (Automatic Repeat reQuest (ARQ), Hybrid ARQ (HARQ), probe, propagation latency, number of hops), a reliability (e.g., probability of successfully decoding X traffic at the BS-UE link in a frame), a connection density (number of connected devices per area), and Radio
  • BH constraints e.g.,
  • the slice segment creation, dimensioning and configuration may comprise creating a graph of users based on user distribution information and slice requirements, as presented in the following steps 1 to 7.
  • the cross-domain slice management entity e.g., NSMF in 3GPP
  • the cross-domain slice management entity may collect and create a set of user distribution patterns for the given E2E network slice based on statistics and slice coverage requirements.
  • a graph of users may be created.
  • the nodes or vertices may be the generated potential user coordinates (according to the user distribution) and the edges may show whether two users are initially served by the same BS and/or the same predefined group of BSs.
  • a weight may be introduced to each node using, as a metric, an estimation of achieving the target KPI.
  • a potential M policy may be further applied.
  • an estimated KPI (eKPI) per user is calculated based on an expected location (taking into account a serving BS as the closest one, the other ones as interfering BS) (step depicted as S2-2).
  • the estimated KPI is assessed with respect to the target KPI (step depicted as S2-3). If an estimated KPI (eKPI) is less than the target KPI, then, for each slice cluster, alternative KPIs (aKPIs) per given policy (e.g., Coordinated Multipoint (CoMP)) are calculated based on an expected location and expected gains from each policy (step depicted as S2-4). Amongst all alternative KPIs (aKPIs), the lowest KPI that is greater than the target KPI is selected as "agreed_KPI” and a weight of node is attributed to the "agreed_KPI” (step depicted as S2-5). If an estimated KPI (eKPI) is greater than the target KPI, a weight node is attributed to the estimated KPI (eKPI) (step depicted as S2-6).
  • aKPIs e.g., Coordinated Multipoint
  • an edge may be introduced between the users, taking into account the serving BS.
  • the graph (per user distribution and per slice) may be solved by partitioning nodes into slice clusters with equal area-KPI, which is the summation of weights of the
  • each slice cluster/segment will contain users with different RRM policies, but since their exact location is unknown, only the percentage of users corresponding to each policy will be used. So, the RAN can perform its own scheduling and the BH can be provisioned more efficiently.
  • solving the graph leads to the provision of slice clusters/segments, different RRM policies to be applied, a range (min, max) of users per cluster, and a percentage of users per RRM policy.
  • the problem to be solved consists in finding a number of maximal cliques to cover the entire graph, wherein each maximal clique has the same intra-clique sum node weight, as depicted in the flow chart of Fig.
  • step S2-7 all complete sub-graphs of the graph G(V,E) are listed and sorted, where V is the set of users and E is the set of edges between users for a given distribution.
  • step S2-8 the sum-node weights for all complete sub-graphs are calculated and stored.
  • step S2-9 all combinations of sub-graphs that include all nodes of the graph and do not have duplicate nodes are generated.
  • step S2-10 the minimum and maximum sum-weights for each combination of sub-graphs are calculated.
  • step S2-11 the combination of sub-graphs that has a minimum difference of sum-weights is selected and extracted.
  • the second, third, fourth and fifth steps may be iteratively performed for a next user distribution.
  • the involved domains ((R) AN, TN, CN) may be informed about the slice segment activation, the covered area and the slice cluster/segment parameters for the different user distributions.
  • the present invention proposes a slice segment mapping per domain for the E2E network slice covering a geographical area.
  • Fig. 3 shows a message sequence chart (MSC) for slice instantiation and slice segment mapping per domain ((R) AN, TN, CN), according to an embodiment of the present invention.
  • the cross-domain slice management entity receives a slice request, for example, from a Communication Service Management Function (CSMF) entity or an application or a third party or a vertical.
  • the slice request may comprise, in a non-limitative manner, at least one of slice service provision requirement and slice coverage requirement.
  • the cross-domain slice management entity also receives periodically domain specific status information from respective domains ((R) AN, TN, CN) through respective domain specific management entities ((R) AN domain management entity, TN domain management entity and CN domain management entity).
  • those domain specific management entities may be, for example, domain specific Network Slice Subnet Management Function (i.e., (R) AN-NSSMF, TN-NSSMF, CN-NSSMF) entities.
  • the domain specific status information may comprise, in a non- limitative manner, at least one of statistics on a status and/or load of the domains, statistics on a traffic distribution, density and mobility patterns of users per slice area, user location information, a resource situation and resource availability.
  • the cross-domain slice management entity performs the steps 1 to 6 as above- mentioned for the slice segment creation, dimensioning and configuration.
  • the cross-domain slice management entity (NSMF) generates domain specific mapping information by mapping the configured slice segments to each domain across the E2E network slice amongst the (R) AN, TN and CN domains, and sends that domain specific mapping information to the respective domain specific management entities, namely (R) AN-NSSMF, TN-NSSMF and CN- NSSMF entities as depicted, using dedicated interfaces.
  • the domain specific mapping information may comprise slice segment information containing a slice identifier (denoted as Slice ID) (i.e., an E2E network slice identifier), a slice segment identifier (denoted as Segment ID) for each slice segment, and configuration information containing Radio Resource Management (RRM) policies for users in an area covered by a slice segment.
  • Slice ID i.e., an E2E network slice identifier
  • Segment ID i.e., an E2E network slice identifier
  • RRM Radio Resource Management
  • the RAN domain mapping information may be sent as a slice segment-to-RAN mapping message to the RAN domain management entity (AN-NSSMF), the TN domain mapping information may be sent as a slice segment-to-TN mapping message to the TN domain management entity (TN-NSSMF), and the CN domain mapping information may be sent as a slice segment-to-CN mapping message to the CN domain management entity (CN-NSSM F).
  • AN-NSSMF RAN domain management entity
  • TN-NSSMF TN domain management entity
  • CN-NSSM F CN domain management entity
  • the cross-domain slice management entity sends configuration parameters based on a user distribution to the RAN domain management entity (AN-NSSMF).
  • the configuration parameters may be sent as a Segment_Distr_Params message and comprise the following parameters: service identifiers (IDs), distribution type, min-max number of users (e.g., UEs) to be supported, coverage, RRM policy parameters and percentage of users per RRM policy.
  • each domain specific management entity matches the user distributions to the configured slice segments, stores the RRM policies for users in an area covered by a slice segment, and sends slice segment information comprising those RRM policies towards its corresponding domain (AN, TN, CN).
  • a RRM policy will be then applied at a node (e.g., BS) of the involved domain (e.g., AN).
  • the slice segment information may also be sent from the cross-domain slice management entity (NSMF) towards another entity of the same level, for example, another cross- domain slice management entity (NSMF) or any operating entity, in order to notify it about the expected load of the network in case of sharing RAN domain resources.
  • NSMF cross-domain slice management entity
  • NSMF cross-domain slice management entity
  • the TN domain mapping information may be sent from a mobile cross-domain slice management entity (e.g., mobile NSMF) towards the TN domain management entity (e.g., TN-NSSMF) according to two options, namely either directly as achieved in step S3-4 of Fig. 3 (option 1), or via a fixed cross-domain slice management entity (e.g., fixed NSMF) or another operating entity of the same level as the cross-domain slice management entity (option 2).
  • a mobile cross-domain slice management entity e.g., mobile NSMF
  • TN-NSSMF TN domain management entity
  • two options namely either directly as achieved in step S3-4 of Fig. 3 (option 1), or via a fixed cross-domain slice management entity (e.g., fixed NSMF) or another operating entity of the same level as the cross-domain slice management entity (option 2).
  • Fig. 5 shows a message sequence chart (MSC) illustrating a RRM CoMP policy application at a RAN node, according to an embodiment of the present invention.
  • the (R)AN domain management entity e.g., AN-NSSMF
  • slice segment information which comprises RRM policy information, resources and coverage
  • all RAN nodes e.g., Nodes B, eNodes B, gNBs.
  • the RAN nodes can then apply a certain RRM policy such as a CoMP policy, for example.
  • RRC radio resource control
  • step S5-2 the user (e.g., UE device) sends radio measurements towards a serving RAN node (e.g., serving gNB) of the cell.
  • a serving RAN node e.g., serving gNB
  • the serving RAN node e.g., serving gNB
  • the serving RAN node triggers, in step S5-3, a change in the applied RRM policy, in order to support the new/modified configured slice segments, by sending a dedicated message towards the (R)AN domain management entity (e.g., AN-NSSMF).
  • the RRM policy is to enable
  • CoMP Coordinated Multipoint Tx/Rx
  • RRM_CoMP_Policy_Trigger message which may comprise information about UE ID, slice segment ID, target gNB ID and CoMP scheme.
  • the (R)AN domain management entity e.g., AN-NSSMF
  • the other involved RAN node e.g., gNB
  • step S5-5 the other involved RAN node (e.g., gNB) sends an acknowledgment message towards the serving RAN node (e.g., serving gNB).
  • the serving RAN node e.g., serving gNB
  • step S5-6 the user (e.g., UE device) sends radio measurements towards both RAN nodes (e.g., serving gNB, gNB).
  • the serving RAN node e.g., serving gNB
  • CSI UE channel state information
  • step S5-8 the serving RAN node and the other involved RAN node serve the user (e.g., UE device) jointly in order to enhance his KPI.
  • the user e.g., UE device
  • the present invention relates to a cross-domain slice management entity (NSMF) for enabling a service provision (SLA) across an end-to-end (E2E) network slice.
  • the cross-domain slice management entity is configured to create slice segments for the E2E network slice based on a slice request and on domain status information from a domain ((R) AN, TN, CN) within the E2E network slice, to configure the slice segments such that all slice segments have an identical service provision, to map the configured slice segments to each domain across the E2E network slice amongst at least a radio access network (RAN) domain, a transport network (TN) domain and a core network (CN) domain, as to obtain domain specific mapping information, and to send the domain specific mapping information to respective domain specific management entities (AN-NSSMF, TN- NSSMF, CN-NSSMF) using dedicated interfaces.
  • RAN radio access network
  • TN transport network
  • CN core network
  • the present invention can ensure a unified-homogeneous service provision across an E2E network slice within a geographical area, which is subject to a fluctuating performance due to multiple dynamically changing factors across a heterogeneous set of wireless and BH technologies and of technology domains.
  • a computer program may be stored/distributed on a suitable medium, such as an optical storage medium or a solid-state medium supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems.
  • a suitable medium such as an optical storage medium or a solid-state medium supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems.

Landscapes

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

Abstract

La présente invention concerne une entité de gestion de tranche à travers un domaine (NSMF) pour permettre une fourniture de service (SLA) à travers une tranche de réseau de bout en bout (E2E). L'entité de gestion de tranche à travers un domaine est configurée pour créer des segments de tranche pour la tranche de réseau E2E en fonction d'une demande de tranche et d'informations d'état de domaine provenant d'un domaine ((R)AN, TN, CN) à l'intérieur de la tranche de réseau E2E, configurer les segments de tranche de sorte que tous les segments de tranche aient une fourniture de service identique, mapper les segments de tranche configurés sur chaque domaine à travers la tranche de réseau E2E parmi au moins un domaine de réseau d'accès radio (RAN), un domaine de réseau de transport (TN) et un domaine de réseau central (CN), de façon à obtenir des informations de mappage spécifiques au domaine, et envoyer les informations de mappage spécifiques au domaine à des entités de gestion spécifiques au domaine respectif (AN-NSSMF, TN-NSSMF, CN-NSSMF) grâce à des interfaces spécialisées.
PCT/EP2017/077257 2017-10-25 2017-10-25 Garantie d'homogénéité de tranche e2e grâce à des segments de tranche flexibles WO2019081005A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/077257 WO2019081005A1 (fr) 2017-10-25 2017-10-25 Garantie d'homogénéité de tranche e2e grâce à des segments de tranche flexibles

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/077257 WO2019081005A1 (fr) 2017-10-25 2017-10-25 Garantie d'homogénéité de tranche e2e grâce à des segments de tranche flexibles

Publications (1)

Publication Number Publication Date
WO2019081005A1 true WO2019081005A1 (fr) 2019-05-02

Family

ID=60245076

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/077257 WO2019081005A1 (fr) 2017-10-25 2017-10-25 Garantie d'homogénéité de tranche e2e grâce à des segments de tranche flexibles

Country Status (1)

Country Link
WO (1) WO2019081005A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110958133A (zh) * 2019-11-01 2020-04-03 北京邮电大学 网络切片映射方法、设备、服务器和存储介质
WO2021028027A1 (fr) * 2019-08-13 2021-02-18 Nokia Solutions And Networks Oy Réalisation d'accords de niveau de service dans des scénarios de tranche de réseau joignant de multiples capacités de réseau
WO2021159461A1 (fr) * 2020-02-14 2021-08-19 Nokia Shanghai Bell Co., Ltd. Procédé de gestion d'isolation de tranches de réseau
WO2022096193A1 (fr) * 2020-11-06 2022-05-12 Nokia Technologies Oy Procédés et mécanismes d'amélioration de la couverture de tranches
CN114651430A (zh) * 2019-11-07 2022-06-21 华为技术有限公司 用于管理切片服务水平协议信息在通信网络中的分配的网络实体
CN115208777A (zh) * 2021-03-25 2022-10-18 中国移动通信有限公司研究院 一种信息处理方法、装置、平台设备及网络设备
US11576020B1 (en) * 2019-08-15 2023-02-07 Netsia, Inc. Apparatus and method for a unified slice manager
US11844012B2 (en) 2021-07-02 2023-12-12 Cisco Technology, Inc. Mapping and stitching network slices across various domains based on a border gateway protocol attribute

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017032280A1 (fr) * 2015-08-21 2017-03-02 Huawei Technologies Co., Ltd. Procédé et appareil pour une segmentation de réseau

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017032280A1 (fr) * 2015-08-21 2017-03-02 Huawei Technologies Co., Ltd. Procédé et appareil pour une segmentation de réseau

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
BEHRISCH, M.; TARAZ, A.: "Efficiently covering complex networks with cliques of similar vertices", THEORETICAL COMPUTER SCIENCE, vol. 355, no. 1, 2006, pages 37 - 47, XP025024894, DOI: doi:10.1016/j.tcs.2005.12.005
BYUNG JUN AHN ETRI KOREA (REP OF): "Draft Recommendation: Framework of IMT-2020 network architecture;IMT-O-043", vol. 10/11, 10 February 2017 (2017-02-10), pages 1 - 31, XP044205937, Retrieved from the Internet <URL:https://www.itu.int/ifa/t/2017/sg11/exchange/wp3/q10/FG_IMT-2020_Deliverables_2016/O-043.docx> [retrieved on 20170210] *
FLINCK C SARTORI A ANDRIANOV C MANNWEILER N SPRECHER NOKIA H: "Network Slicing Management and Orchestration; draft-flinck-slicing-management-00.txt", NETWORK SLICING MANAGEMENT AND ORCHESTRATION; DRAFT-FLINCK-SLICING-MANAGEMENT-00.TXT; INTERNET-DRAFT: INTERNET ENGINEERING TASK FORCE, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 G, 3 July 2017 (2017-07-03), pages 1 - 10, XP015120602 *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021028027A1 (fr) * 2019-08-13 2021-02-18 Nokia Solutions And Networks Oy Réalisation d'accords de niveau de service dans des scénarios de tranche de réseau joignant de multiples capacités de réseau
US11968099B2 (en) 2019-08-13 2024-04-23 Nokia Solutions And Networks Oy Realization of service level agreements in network slice scenarios joining multiple network capabilities
US11576020B1 (en) * 2019-08-15 2023-02-07 Netsia, Inc. Apparatus and method for a unified slice manager
CN110958133A (zh) * 2019-11-01 2020-04-03 北京邮电大学 网络切片映射方法、设备、服务器和存储介质
CN114651430A (zh) * 2019-11-07 2022-06-21 华为技术有限公司 用于管理切片服务水平协议信息在通信网络中的分配的网络实体
CN114651430B (zh) * 2019-11-07 2023-09-01 华为技术有限公司 用于管理切片服务水平协议信息在通信网络中的分配的网络实体
WO2021159461A1 (fr) * 2020-02-14 2021-08-19 Nokia Shanghai Bell Co., Ltd. Procédé de gestion d'isolation de tranches de réseau
WO2022096193A1 (fr) * 2020-11-06 2022-05-12 Nokia Technologies Oy Procédés et mécanismes d'amélioration de la couverture de tranches
CN115208777A (zh) * 2021-03-25 2022-10-18 中国移动通信有限公司研究院 一种信息处理方法、装置、平台设备及网络设备
US11844012B2 (en) 2021-07-02 2023-12-12 Cisco Technology, Inc. Mapping and stitching network slices across various domains based on a border gateway protocol attribute

Similar Documents

Publication Publication Date Title
US11445434B2 (en) Method, terminal device, and network side device for accessing network side device
US11039363B2 (en) Method for controlling radio access resources in a communication network
WO2019081005A1 (fr) Garantie d&#39;homogénéité de tranche e2e grâce à des segments de tranche flexibles
CN109600755B (zh) 网络资源部署及评估的方法、和设备
US11445515B2 (en) Network slice selection based on requested service
CN113875192B (zh) 第一实体、第二实体、第三实体及由之执行的用于在通信网络中提供服务的方法
KR20180137823A (ko) 네트워크 가상화 및 세션 관리 방법 및 장치
CN108012339B (zh) 具有无线电调度器的无线电通信网络
Zanzi et al. On guaranteeing end-to-end network slice latency constraints in 5G networks
US11438210B2 (en) Apparatus and method for handling managed object priorities in 5G network
WO2023029757A1 (fr) Procédé d&#39;estimation de ressource et dispositif associé
US11601947B2 (en) Systems and methods for network slice selection according to application specific request
EP3907933A1 (fr) Gestionnaire de qualité de service pour tranches de réseau d&#39;un réseau
Moubayed et al. Dynamic spectrum management through resource virtualization with m2m communications
US11791976B2 (en) Systems and methods for dynamic time division duplex adjustment in a wireless network
US20240064563A1 (en) Systems and methods for network design and configuration based on user-level usage modeling
US11888699B1 (en) Method and system for hybrid network slicing
US11595251B2 (en) Systems and methods for dynamically allocating resources based on configurable resource priority
US20240007931A1 (en) Systems and methods for performing access control
ES2751281T3 (es) Método para controlar recursos de acceso radio en una red de comunicación
CN117643085A (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: 17793913

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

Country of ref document: EP

Kind code of ref document: A1