[go: up one dir, main page]

WO2019064678A1 - Dispositif de gestion et procédé de commande d'architecture réseau - Google Patents

Dispositif de gestion et procédé de commande d'architecture réseau Download PDF

Info

Publication number
WO2019064678A1
WO2019064678A1 PCT/JP2018/018547 JP2018018547W WO2019064678A1 WO 2019064678 A1 WO2019064678 A1 WO 2019064678A1 JP 2018018547 W JP2018018547 W JP 2018018547W WO 2019064678 A1 WO2019064678 A1 WO 2019064678A1
Authority
WO
WIPO (PCT)
Prior art keywords
requirement
information
computing device
deployment
requirements
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/JP2018/018547
Other languages
English (en)
Japanese (ja)
Inventor
宏司 坪内
榑林　亮介
アシック カーン
マルケース ジョアン トリエイ
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.)
NTT Docomo Inc
Original Assignee
NTT Docomo Inc
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 NTT Docomo Inc filed Critical NTT Docomo Inc
Publication of WO2019064678A1 publication Critical patent/WO2019064678A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • the present invention has been made to solve the above-mentioned problems, and it is an object of the present invention to appropriately control a network configuration in accordance with isolation requirements.
  • the network configuration can be appropriately controlled according to the isolation requirements.
  • slices are formed for each service provided to the UE 30, and each slice provides a service corresponding to the slice.
  • NFs network function units
  • slice # 1 is configured to include NF1 to NF4
  • slice # 2 is configured to include NF1, NF2, NF5, and NF6, and NF1 and NF2 shown by thick lines in FIG. , Shared by # 2.
  • the communication system 1 is provided with an NRF (Network Repository Function) 20 that centrally manages connection information of each NF, and each NF inquires of the NRF 20 when communicating with other NFs and communicates with the NF of the communication destination NF. Get connection information.
  • NRF Network Repository Function
  • the communication system 1 includes a management device 60, the above-described NRF 20, UE 30, an access device 70 (for example, a base station, e-NodeB, etc.), the above-described NF 10, and a computing device 50. And they can be communicated with each other via the network 80.
  • the UE 30 is connected to the network 80 via the access device 70.
  • the NF 10 and the computing device 50 are housed in data centers 40 provided at various locations. Further, the NF 10 is configured in one or both of virtual NF 10 A virtually generated in a plurality of in the computing device 50 and physical NF 10 B provided in a form of occupying a device equivalent to the computing device 50. Be done.
  • the management apparatus 60 includes a request receiving unit 61, a use NF determination unit 62, a shareability determination unit 63, an NF deployment unit 64, an NRF registration unit 65, an availability requirement table 66, and an available NF grade table 67. , An isolation requirement table 69A, a computing device table 69B, and a deployed NF / infrastructure information table 68. The outline of each functional unit will be described below.
  • the request receiving unit 61 is a functional unit for receiving a deployment request including an NF type indicating the type of the NF desired to be deployed, and a requirement required for the NF.
  • the use NF determination unit 62 uses the NF grade based on the NF type and requirements included in the deployment request accepted by the request acceptance unit 61 and the information of the availability requirement table 66 and the available NF grade table 67 described later. It is a functional unit that determines a candidate. Further, the use NF determination unit 62 may determine one NF grade as an NF grade candidate to be used, or may determine a plurality of NF grade candidates. Below, it illustrates about the case where use NF deciding part 62 decides one NF grade.
  • the sharing availability determination unit 63 derives the sharing type of the NF from the isolation requirement, and determines whether the NF related to the NF grade candidate determined above can be shared according to the obtained sharing type. Is a functional unit that executes processing such as determination of
  • the NF deployment unit 64 is a functional unit that deploys an NF that satisfies the above requirements by newly generating an NF or using an existing NF according to the determination result by the shareability determination unit 63. Also, the NF deployment unit 64 adds / updates the deployed NF instance information to the NF / infrastructure information table 68.
  • the NRF registration unit 65 registers the NF type, the slice identification auxiliary information, and the connection information in an NF connection information table 21 described later of the NRF 20 so that the newly generated NF and the diverted NF can be used.
  • the available NF grade table 67 is a table that is provided for each NF type and stores information in which requirements required for the NF for the NF type are associated with available NF grades.
  • FIG. 5 shows an example where the NF type is mobility management function (AMF), and as a requirement required for the NF, an availability requirement (specifically, a redundant configuration corresponding to the availability requirement) And functional requirements (standards A to C, unique A, B) are illustrated, and available NF grades (grades 1 to 9) corresponding to these requirements are shown.
  • AMF mobility management function
  • the isolation requirement table 69A is a table that defines the correspondence between the isolation requirement and the share type, and the description related to each share type is also described.
  • the isolation requirement "low” is associated with a sharing type "A” that allows the NF to be shared between different slices, and the isolation requirement "medium” does not allow the NF to share with different slices, but the NF A computing device to be operated is associated with a sharing type “B” that enables sharing between different slices, and an isolation requirement “high” is a sharing type that does not share both the NF and the computing device that operates the NF with different slices It is mapped to "C".
  • the computing device table 69B is a table storing information on available computing devices. For example, as shown in FIG. 7, the region name, area name, data center name, computing device as information on available computing devices Information such as ID, inter-slice sharing type, and dedicated slice identification auxiliary information is stored in association with each other.
  • the NF / infrastructure information table 68 is a table storing the already deployed NF / infrastructure information (corresponding to “deployment information” in the claims), for example, as shown in FIG.
  • information on infrastructure information such as region name, area name, data center name, computing device ID, NF instance ID, NF specification ID, used network (used band / available band), shared type is stored in association with each other. There is.
  • a mobility management function AMF
  • AUSF authentication function
  • SMF session management function
  • UPF data transfer function
  • slice identification auxiliary information is information used by the user at the time of slice access, corresponds to NSSAI described in 3GPP TS 23.501 (Table 5.15.2.2-1), and eMBB, URLLC, MIoT, etc. are exemplified.
  • An IP address, FQDN, etc. are illustrated as connection information to said NF.
  • step S5 the available NW information is added to the computing device table 69B, and a condition that the available NW information satisfies the connection destination NW requirements of the NF is added, and the computing device is extracted May be
  • a computing device that newly generates an NF may be selected according to any of the selection criteria exemplified in step S5.
  • the process proceeds to step S7, and the sharing availability determination unit 63 refers to the deployed NF / infrastructure information table 68 of FIG.
  • the sharing availability determination unit 63 refers to the deployed NF / infrastructure information table 68 of FIG.
  • it is determined whether or not the NF grade NF to be used is already deployed, and if deployed, it is determined whether the NF can be shared with other slices.
  • the shared NF is selected by the following procedure.
  • the deployed NF (NF instance ID in FIG. 8) satisfying these requirements is searched from the deployed NF / infrastructure information table 68 of FIG. Show an example of determining whether sharing is possible.
  • the name, data center name, computing device ID, and NF instance ID are as follows: ⁇ Asia, jp-east, tokyo1, CN1, ins1 ⁇ Asia, jp-east, tokyo1, CN2, ins2
  • the shared NF is selected, for example, according to any of the following selection criteria. ⁇ Select one randomly. • In the network used, select the place with the least bandwidth. Select the place where the usage rate of the computing device is the lowest.
  • step S7 If it is determined in step S7 that the NF is not shareable or not deployed with other slices, the process proceeds to step S6 described above, and the NF deployment unit 64 uses the NF grade NF to be used in the computing device satisfying the location requirements. Newly deploy.
  • the same affinity group ID as the slice to be shared is specified as a deployment request parameter, while sharing NF among slices as possible. If you do not want to make this happen, specify a different affinity group ID from the slice you do not want to share as a deployment request parameter, and then search for the deployed NF with the requirement that "affinity group ID matches". This makes it appropriate to satisfy the isolation requirements such as “I would like to share NF between slices owned by MNO, but not want to share NF between slices owned by MNO and slices owned by MVNO”. Can be deployed.
  • each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured by a single bus or may be configured by different buses among the devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un dispositif de gestion (60) qui déploie une unité de fonction réseau (NF) sur la base d'une requête de déploiement pour une NF constituant une tranche, ladite requête de déploiement comprenant le type de NF correspondant à la requête de déploiement et aux exigences de la NF qui comprennent une exigence d'isolation liée au non-partage et associée à la NF. Le dispositif de gestion (60) comprend une unité de commande d'architecture réseau (62S) qui, sur la base d'au moins le type de NF, les exigences comprenant l'exigence d'isolation, et les informations pré-stockées d'ordinateur utilisable, ainsi que les informations de déploiement concernant la NF et/ou l'infrastructure déployée pré-stockée, déploie sur un ordinateur utilisable une NF correspondant à la requête de déploiement, de façon à ce que l'exigence d'isolation soit satisfaite.
PCT/JP2018/018547 2017-09-26 2018-05-14 Dispositif de gestion et procédé de commande d'architecture réseau Ceased WO2019064678A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2017-185214 2017-09-26
JP2017185214A JP2021010042A (ja) 2017-09-26 2017-09-26 管理装置およびネットワーク構成制御方法

Publications (1)

Publication Number Publication Date
WO2019064678A1 true WO2019064678A1 (fr) 2019-04-04

Family

ID=65901547

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2018/018547 Ceased WO2019064678A1 (fr) 2017-09-26 2018-05-14 Dispositif de gestion et procédé de commande d'architecture réseau

Country Status (2)

Country Link
JP (1) JP2021010042A (fr)
WO (1) WO2019064678A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021171210A1 (fr) 2020-02-26 2021-09-02 ラクテン・シンフォニー・シンガポール・プライベート・リミテッド Système de construction de service de réseau et procédé de construction de service de réseau
WO2021171073A1 (fr) 2020-02-26 2021-09-02 ラクテン・シンフォニー・シンガポール・プライベート・リミテッド Système informatique et procédé de construction de service réseau
WO2021171211A1 (fr) 2020-02-26 2021-09-02 ラクテン・シンフォニー・シンガポール・プライベート・リミテッド Système de gestion de groupe de ressources, procédé de gestion de groupe de ressources et programme
WO2022167837A1 (fr) 2021-02-04 2022-08-11 ラクテン・シンフォニー・シンガポール・プライベート・リミテッド Système de gestion de service de réseau et procédé de gestion de service de réseau
WO2025097283A1 (fr) * 2023-11-06 2025-05-15 Nokia Shanghai Bell Co., Ltd Procédé et appareil d'isolation de ressources sur un réseau de communication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015122680A (ja) * 2013-12-25 2015-07-02 株式会社日立製作所 論理ネットワークの構築方法、および、ネットワークシステム
WO2016152588A1 (fr) * 2015-03-20 2016-09-29 株式会社Ｎｔｔドコモ Dispositif de détermination d'attribution de service et procédé de détermination d'attribution de service
JP2017037522A (ja) * 2015-08-11 2017-02-16 日本電信電話株式会社 仮想化基盤選択装置及び方法、並びに、プログラム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015122680A (ja) * 2013-12-25 2015-07-02 株式会社日立製作所 論理ネットワークの構築方法、および、ネットワークシステム
WO2016152588A1 (fr) * 2015-03-20 2016-09-29 株式会社Ｎｔｔドコモ Dispositif de détermination d'attribution de service et procédé de détermination d'attribution de service
JP2017037522A (ja) * 2015-08-11 2017-02-16 日本電信電話株式会社 仮想化基盤選択装置及び方法、並びに、プログラム

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
INTEL ARCHITECTURE PROCESSORS: "Realising the Benefits of Network Functions Virtualisation in Telecoms Networks", WHITE PAPER VIRTUALISATION IN TELECOMS NETWORK, 2014, Retrieved from the Internet <URL:https://www.tieto.com/sites/default/files/atoms/files/telecomnetvirualisation330181_001.pdf> *
INTEL ET AL., END-TO-END OPTIMIZED NETWORK FUNCTION VIRTUALIZATION DEPLOYMENT, Retrieved from the Internet <URL:https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/end-to-end-optimized-nfv-paper.pdf> *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021171210A1 (fr) 2020-02-26 2021-09-02 ラクテン・シンフォニー・シンガポール・プライベート・リミテッド Système de construction de service de réseau et procédé de construction de service de réseau
WO2021171073A1 (fr) 2020-02-26 2021-09-02 ラクテン・シンフォニー・シンガポール・プライベート・リミテッド Système informatique et procédé de construction de service réseau
WO2021171071A1 (fr) 2020-02-26 2021-09-02 ラクテン・シンフォニー・シンガポール・プライベート・リミテッド Système et procédé de construction de service de réseau
WO2021171211A1 (fr) 2020-02-26 2021-09-02 ラクテン・シンフォニー・シンガポール・プライベート・リミテッド Système de gestion de groupe de ressources, procédé de gestion de groupe de ressources et programme
US11844016B2 (en) 2020-02-26 2023-12-12 Rakuten Symphony Singapore Pte. Ltd. Computer system and network service construction method
US12160793B2 (en) 2020-02-26 2024-12-03 Rakuten Symphony, Inc. Network service construction system and network service construction method
US12376026B2 (en) 2020-02-26 2025-07-29 Rakuten Symphony, Inc. Computer system and network service construction method
US12376019B2 (en) 2020-02-26 2025-07-29 Rakuten Symphony, Inc. Computer system and network slice management method
WO2022167837A1 (fr) 2021-02-04 2022-08-11 ラクテン・シンフォニー・シンガポール・プライベート・リミテッド Système de gestion de service de réseau et procédé de gestion de service de réseau
WO2025097283A1 (fr) * 2023-11-06 2025-05-15 Nokia Shanghai Bell Co., Ltd Procédé et appareil d'isolation de ressources sur un réseau de communication

Also Published As

Publication number Publication date
JP2021010042A (ja) 2021-01-28

Similar Documents

Publication Publication Date Title
WO2019064678A1 (fr) Dispositif de gestion et procédé de commande d&#39;architecture réseau
JP2019021953A (ja) Ｒａｎスライスにおけるリソース管理装置及びｒａｎスライスにおけるリソース管理方法
CN110915265B (zh) 网络接入方法及通信系统
WO2019077801A1 (fr) Système de communication, dispositif de commande de communication et procédé de communication
CN110337829B (zh) 通信控制方法及通信系统
EP3373517A1 (fr) Procédé et dispositif de configuration pour une fonction de réseau virtuel
EP3503609A1 (fr) Tranche de réseau d&#39;accès radio
WO2018061921A1 (fr) Procédé de sélection de passerelle et système de communication
WO2019064677A1 (fr) Dispositif de gestion et procédé de commande d&#39;architecture de réseau
WO2019035287A1 (fr) Procédé de commande de communication et système de communication
WO2019159373A1 (fr) Procédé de commande de communication et système de communication
WO2019159372A1 (fr) Procédé de transfert d&#39;information et groupe de nœuds
WO2020054244A1 (fr) Dispositif de génération d&#39;informations de conversation
WO2020031303A1 (fr) Dispositif de connexion de communication et procédé de connexion de communication
JP7430733B2 (ja) オーソリゼーション装置
JP2023116078A (ja) 通信制御装置
WO2019064676A1 (fr) Dispositif de gestion et procédé de commande d&#39;accès
JP2023106869A (ja) スライス管理システム及び方法
JP7077238B2 (ja) ゲートウェイ選択方法および通信システム
WO2022180987A1 (fr) Dispositif de fourniture de service et système de fourniture de service
CN116074859A (zh) 业务分流方法、系统、电子设备及计算机可读介质
JP6807799B2 (ja) サーバ
JP7357061B2 (ja) オーソリゼーション装置
JP2018164235A (ja) 通信端末および通信制御方法
JP2018085688A (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: 18860805

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP