[go: up one dir, main page]

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

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

Info

Publication number
WO2019064677A1
WO2019064677A1 PCT/JP2018/018541 JP2018018541W WO2019064677A1 WO 2019064677 A1 WO2019064677 A1 WO 2019064677A1 JP 2018018541 W JP2018018541 W JP 2018018541W WO 2019064677 A1 WO2019064677 A1 WO 2019064677A1
Authority
WO
WIPO (PCT)
Prior art keywords
grade
deployment
requirement
requirements
slice
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/018541
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 WO2019064677A1 publication Critical patent/WO2019064677A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/12—Access point controller devices

Definitions

  • the present invention relates to a management device and a network configuration control method.
  • 3GPP TS23.501 5G system
  • one or more network function units hereinafter referred to as “NF”
  • NF network function units
  • the required grade of NF varies. For example, there are multiple grades such as “only standard features are sufficient” and “require unique customization features” for functions that NF should possess, and multiple grades according to the required degree of availability exist It can.
  • shared NF the shared NF
  • grade NF the shared NF
  • soaring cost of sharing NF it is also desirable to procure appropriate grade NFs that satisfy the requirements.
  • the present invention has been made to solve the above-mentioned problems, and an object of the present invention is to avoid a rise in the procurement cost of NF.
  • a management apparatus is an NF type indicating a type of an NF corresponding to a deployment request, which is a deployment request of a network function unit (NF) configuring a slice that is a virtual network on a network infrastructure;
  • a request receiving unit for receiving the deployment request including the requirements required for the NF, the NF type and the requirements included in the deployment request received by the request receiving unit, and the NF type and requirements in advance
  • a use NF determination unit for determining an NF grade candidate to be used based on the stored available NF grade information, and a prestored information based on the NF grade candidate determined by the use NF determination unit and the requirement Search deployment information on deployed NF and / or infrastructure, and An NF that satisfies the above requirements by newly generating an NF or using an existing NF according to the determination result by the sharing availability determination unit that determines whether the NF related to the supplement can be shared or not and the sharing availability determination unit And an NF deployment unit for deploying the Note that “deployment”
  • the request receiving unit is a deployment request of a network function unit (NF) configuring a slice that is a virtual network on the network infrastructure, and an NF type indicating the type of the NF corresponding to the deployment request Accepting the deployment request including the requirements required for the NF
  • the use NF determination unit may use the NF type and requirements included in the accepted deployment request, and the memory stored in advance in association with the NF types and requirements
  • the sharing decision unit determines the deployment information regarding at least one of the pre-stored deployed NF and the infrastructure based on the determined NF grade candidate and the above requirements.
  • the NF grade candidate to be used is determined and determined according to the NF type and the requirements required for the NF. Based on the NF grade candidate and the above requirements, it is judged whether the NF related to the NF grade candidate can be shared or not, and an appropriate NF satisfying the above requirements is deployed according to the judgment result, so that multiple slices are performed as in the prior art. It is possible to avoid the need to prepare high grade NFs that satisfy all the requirements of the above, and to avoid soaring procurement costs of NFs.
  • 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. 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. Also, although the detailed process will be described later, 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.
  • the sharing availability determination unit 63 deploys at least one of the deployed NF and infrastructure information stored in advance in the deployed NF / infrastructure information table 68 based on the NF grade candidate determined by the usage NF determination unit 62 and the above-described requirements. It is a functional unit that searches information (hereinafter referred to as “deployed NF / infrastructure information”) and determines whether or not NFs related to NF grade candidates can be shared.
  • 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 availability requirement table 66 is a table storing information in which the availability requirement and the redundant configuration are associated.
  • 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 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.
  • infrastructure information information such as region name, area name, data center name, computing device ID, NF instance ID, NF specification ID, and used network (used band / available band) are stored in association with each other.
  • the NRF 20 includes the NF connection information table 21 shown in FIG. 7 in order to centrally manage the connection information of each NF, and the NF connection information table 21 includes, for example, an NF type and slice identification auxiliary information. And NF connection information are stored in association with each other.
  • the process in FIG. 8 is triggered by, for example, the deployment request of the NF from the administrator or the upper apparatus to the management apparatus 60 as a trigger.
  • the above-described deployment request is provided with, as input information, an NF type to be deployed, slice identification auxiliary information, connection information to the NF, and requirements required for the NF.
  • 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.
  • Requirements required for the above NF include functional requirements (eg, standard, no standard / no mobility, standard and predetermined customization functions etc.), availability requirements (eg, low, medium, high), connected network requirements (eg, low, medium, high) For example, 100M, 1G, 10G, etc., location requirements (eg, specific data center specification, specific area specification, specific region specification, no specification, etc.) may be mentioned.
  • functional requirements eg, standard, no standard / no mobility, standard and predetermined customization functions etc.
  • availability requirements eg, low, medium, high
  • connected network requirements eg, low, medium, high
  • location requirements eg, specific data center specification, specific area specification, specific region specification, no specification, etc.
  • the slice identification auxiliary information and the connection information to the NF may be generated as output information by the management device 60 instead of being input to the management device 60.
  • step S1 of FIG. 8 the request receiving unit 61 receives a deployment request including the above-described NF type, requirements, and the like.
  • the use NF determination unit 62 determines the NF grade to be used by executing the process shown in FIG. As described above, the use NF determination unit 62 may determine one NF grade or a plurality of NF grade candidates, but here, NF type “AMF”, functional requirement “standard” A, standard B, and original A ", availability requirement” y% or more "are input, and an example of determining one NF grade is described.
  • the use NF determination unit 62 determines a redundant configuration from the input availability requirement with reference to the availability requirement table 66 of FIG. 4 (step S21 of FIG. 9).
  • “Active-Standby” and “All-Active” are determined as redundant configurations corresponding to the availability requirement “y% or more”.
  • the use NF determination unit 62 determines the available NF grade table 67 to be referred to from the input NF type, and refers to the available NF grade table 67 to input the functional requirements and step S21. Extract an NF grade that satisfies the redundant configuration determined in step S22 (step S22).
  • the available NF grade table 67 of FIG. 5 corresponding to the input NF type “AMF” is referred to, and the functional requirements “standard A, standard B and original A” and redundant configurations “Active-Standby and All- "NF grade 8, 9" is extracted as an NF grade satisfying "Active".
  • the use NF determination unit 62 determines the lowest NF grade among the extracted NF grades as the NF grade to be used (step S23).
  • the lowest NF grade "NF grade 8” is determined as the NF grade to be used, and it is decided to use the NF specification ID "AMF 8".
  • the shareability determination unit 63 refers to the deployed NF / infrastructure information table 68 of FIG. 6 and searches for deployed NFs that satisfy the connection destination network requirements and location requirements. Then, determine whether an NF grade to be used and an NF that meets the connection destination network requirements and location requirements have already been deployed, and if the NF can be shared with other slices if deployed. To judge. In addition, in this step S3, when it is determined that sharing is possible, for example, the shared NF is selected by the following procedure.
  • the deployed NF (NF instance ID in FIG. 6) meeting these requirements is retrieved from the deployed NF / infrastructure information table 68 of FIG. 6 below using the NF specification ID, location requirements and connected network requirements as input information. 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 S4 the process proceeds to step S4, and the NF deployment unit 64 newly adds the NF grade NF to be used to the computing device meeting the location requirements. Deploy to
  • step S3 when the NF can be shared with other slices in step S3, the process proceeds to step S5, and the NF deploying unit 64 sets the deployed NF setting information stored in the deployed NF / infrastructure information table 68. Make corrections as necessary. For example, it is set to generate predetermined management information (such as traffic flow rate information) for the requested slice identification auxiliary information.
  • predetermined management information such as traffic flow rate information
  • the NF deploying unit 64 adds and updates deployed NF instance information to the deployed NF / infrastructure information table 68.
  • step S7 the NRF registration unit 65 enables the NF connection information table 21 of FIG. 7 stored by the NRF 20 to use the NF type, slice identification auxiliary information, and the like in order to enable the newly generated NF and the diverted NF. Register connection information.
  • a plurality of NF grade candidates may be determined instead of determining one NF grade.
  • step S3 of FIG. In the process of searching for deployed NFs, multiple NF grade candidates may be narrowed down to one NF grade. In this way, new deployment of NF can be avoided by sharing NF of a grade higher than the new grade, instead of newly deploying the same grade of NF.
  • step S2 of FIG. 8 the process of narrowing down from a plurality of NF grade candidates to one NF grade can be omitted, so that the whole process can be simplified. There is an advantage.
  • the sharing judgment unit 63 determines the NF grade NF which is lower than the required requirement above for the slice in which the NF grade NF is higher than the required requirement according to the requirement of the slice.
  • the new deployment request Determines that the high NF grade NF can be shared, and the NF deployment unit 64 newly creates the low NF grade NF according to the determination result and deploys it on the existing slice.
  • the above high NF grade NF can be redeployed to a slice related to a new deployment request. This can avoid the disadvantage that the high NF grade NF can not be deployed in response to a new deployment request requiring a high NF grade NF.
  • the NF deployment unit 64 and the NRF registration unit 65 may be cut out as separate devices.
  • the NF deployment unit 64 and the NRF registration unit 65 are disposed in another apparatus 60B, and accordingly, the management apparatus 60 of FIG. 3 is configured with an NF descriptor (design information of NF) and an NF setting. It may be configured as a management data generation device 60A that generates data and NRF setting data and passes it to another device 60B.
  • an NF descriptor / setting data generation / correction unit 64A and an NRF setting data generation unit 65A are provided in the management data generation apparatus 60A, and the NF descriptor / setting data generation / correction unit 64A is an NF descriptor (NF design information And NF setting data are generated and passed to the NF deployment unit 64 in another device 60B, and the NRF setting data generation unit 65A generates NRF setting data, and passes it to the NRF registration unit 65 in another device 60B.
  • the management device according to the present invention is configured by the management data generation device 60A and another device 60B, and a part of the management device 60 of FIG. Even when the functional units of the above are cut out to be configured, substantially the same processing can be performed, and similar effects can be obtained.
  • input information input from the administrator / upper level device to the management device 60 of FIG. 3 is stored in advance as a template in the management device 60, and the information actually input is the template ID and the necessary minimum information.
  • the template ID and the necessary minimum information For example, slice identification auxiliary information and the like
  • templates include OpenStack Heat Orchestration Template (HOT), OASIS TOSCA, ETSI NFV VNFD / NSD, and the like.
  • each functional block may be realized by one physically and / or logically coupled device, or directly and / or indirectly two or more physically and / or logically separated devices. It may be connected by (for example, wired and / or wireless) and realized by the plurality of devices.
  • the management device 60 in the above embodiment may function as a computer that performs the processing of the management device 60 described above.
  • FIG. 11 is a diagram showing an example of the hardware configuration of the management device 60.
  • the management device 60 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007 and the like.
  • the term “device” can be read as a circuit, a device, a unit, or the like.
  • the hardware configuration of the management device 60 may be configured to include one or more of the devices shown in the figure, or may be configured without some devices.
  • Each function in the management device 60 causes the processor 1001 to perform an operation by reading predetermined software (program) on hardware such as the processor 1001, the memory 1002, and the communication by the communication device 1004, the memory 1002 and the storage 1003. It is realized by controlling reading and / or writing of data.
  • predetermined software program
  • the processor 1001 operates, for example, an operating system to control the entire computer.
  • the processor 1001 may be configured by a central processing unit (CPU: Central Processing Unit) including an interface with a peripheral device, a control device, an arithmetic device, a register, and the like.
  • CPU Central Processing Unit
  • each functional unit of the management device 60 may be realized including the processor 1001.
  • the processor 1001 also reads a program (program code), a software module, data, and the like from the storage 1003 and / or the communication device 1004 to the memory 1002, and executes various processing according to these.
  • a program a program that causes a computer to execute at least a part of the operations described in the above embodiments is used.
  • each functional unit of the management device 60 may be realized by a control program stored in the memory 1002 and operated by the processor 1001, or may be realized similarly for other functional blocks.
  • the various processes described above have been described to be executed by one processor 1001, but may be executed simultaneously or sequentially by two or more processors 1001.
  • the processor 1001 may be implemented by one or more chips.
  • the program may be transmitted from the network via a telecommunication line.
  • the memory 1002 is a computer readable recording medium, and includes, for example, at least one of a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), and a RAM (Random Access Memory). It may be done.
  • the memory 1002 may be called a register, a cache, a main memory (main storage device) or the like.
  • the memory 1002 may store a program (program code), a software module, etc. that can be executed to implement the method according to an embodiment of the present invention.
  • the storage 1003 is a computer readable recording medium, and for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disc drive, a flexible disc, a magneto-optical disc (eg, a compact disc, a digital versatile disc, a Blu-ray A (registered trademark) disk, a smart card, a flash memory (for example, a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like may be used.
  • the storage 1003 may be called an auxiliary storage device.
  • the above-mentioned storage medium may be, for example, a database including the memory 1002 and / or the storage 1003, a server or any other suitable medium.
  • the communication device 1004 is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, or the like.
  • a network device for example, a network controller, a network card, a communication module, or the like.
  • each functional unit of the management device 60 described above may be realized including the communication device 1004.
  • the input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, and the like) that receives an input from the outside.
  • the output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside.
  • the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).
  • 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.
  • the management device 60 includes hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). It may be configured, and part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented in at least one of these hardware.
  • the configuration other than the management device 60 illustrated in FIG. 1 may have the same configuration as that of the communication terminal.
  • the input / output information may be stored in a specific place (for example, a memory), or may be managed by a management table. Information to be input or output may be overwritten, updated or added. The output information may be deleted. The input information or the like may be transmitted to another device.
  • the determination may be performed by a value (0 or 1) represented by one bit, may be performed by a boolean value (Boolean: true or false), or may be compared with a numerical value (for example, a predetermined value). Comparison with the value).
  • notification of predetermined information is not limited to what is explicitly performed, but is performed by implicit (for example, not notifying of the predetermined information) It is also good.
  • Software may be called software, firmware, middleware, microcode, hardware description language, or any other name, and may be instructions, instruction sets, codes, code segments, program codes, programs, subprograms, software modules. Should be interpreted broadly to mean applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc.
  • software, instructions, etc. may be sent and received via a transmission medium.
  • software may use a wireline technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or a website, server or other using wireless technology such as infrared, radio and microwave When transmitted from a remote source, these wired and / or wireless technologies are included within the definition of transmission medium.
  • wireline technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or a website, server or other using wireless technology such as infrared, radio and microwave
  • data, instructions, commands, information, signals, bits, symbols, chips etc may be voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any of these May be represented by a combination of
  • information, parameters, and the like described in the present specification may be represented by absolute values, may be represented by relative values from predetermined values, or may be represented by corresponding other information. .
  • Mobile communication terminals may be subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, by those skilled in the art. It may also be called a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term.
  • determining may encompass a wide variety of operations.
  • “Judgment”, “decision” are, for example, judging, calculating, calculating, processing, processing, deriving, investigating, looking up (for example, a table) (Searching in a database or another data structure), ascertaining may be regarded as “decision”, “decision”, etc.
  • “determination” and “determination” are receiving (e.g. receiving information), transmitting (e.g. transmitting information), input (input), output (output), access (accessing) (for example, accessing data in a memory) may be regarded as “judged” or “decided”.
  • the phrase “based on” does not mean “based only on,” unless expressly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • DESCRIPTION OF SYMBOLS 1 communication system 10 ... NF, 20 ... NRF, 21 ... NF connection information table, 30 ... UE, 40 ... data center, 50 ... calculation apparatus, 60 ... management apparatus, 60A ... management data generation apparatus, 60B ... another Devices 61 61 request acceptance unit 62 use NF determination unit 63 shareability determination unit 64 NF deployment unit 64A NF descriptor / setting data generation / modification unit 65 NRF registration unit 65A NRF Setting data generation unit 66: availability requirement table 67: available NF grade table 68: deployed NF / infrastructure information table 70: access device 80: network 1001: processor 1002: memory 1003: storage 1003 1004 ... communication device, 1005 ... input device, 1006 ... output device, 1007 ... bus.

Landscapes

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

Abstract

Un dispositif de gestion (60) déploie une NF sur la base d'une demande de déploiement pour une NF constituant une tranche, ladite demande de déploiement comprenant le type de NF correspondant à la demande de déploiement et une exigence requise par la NF. Le dispositif de gestion (60) comprend : une unité de détermination de NF d'utilisation (62) qui détermine un candidat de grade NF à utiliser sur la base du type de NF et de l'exigence inclus dans la demande de déploiement et des informations de grade NF utilisable préalablement mémorisées en association avec le type de NF et l'exigence ; une unité d'évaluation partageable/non partageable (63) qui, sur la base du candidat de grade NF déterminé et de l'exigence, récupère des informations de déploiement relatives à une NF et/ou une infrastructure déployée préalablement mémorisée, et évalue si la NF appartenant au candidat de grade NF peut être partagée ; et une unité de déploiement de NF (64) qui déploie une NF répondant à l'exigence en générant nouvellement une NF ou en s'appropriant d'une NF existante conformément aux résultats d'évaluation.
PCT/JP2018/018541 2017-09-26 2018-05-14 Dispositif de gestion et procédé de commande d'architecture de réseau Ceased WO2019064677A1 (fr)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=65901168

Family Applications (1)

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

Country Status (2)

Country Link
JP (1) JP2021010041A (fr)
WO (1) WO2019064677A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111416827A (zh) * 2020-03-25 2020-07-14 广州爱浦路网络技术有限公司 根据安全等级发现网络功能nf的方法

Citations (2)

* 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

Patent Citations (2)

* 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

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", INTEL, BROCADE, CYAN, RED HAT, AND TELEFONICA-NFV SERVICES, 2015, pages 1 - 8, XP055588050, 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 (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111416827A (zh) * 2020-03-25 2020-07-14 广州爱浦路网络技术有限公司 根据安全等级发现网络功能nf的方法

Also Published As

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

Similar Documents

Publication Publication Date Title
CN110876174B (zh) 网络切片选择方法、设备及系统
US20190356596A1 (en) Service link selection control method and device
EP3664372A1 (fr) Procédé de gestion de réseau, et dispositif associé
WO2019064678A1 (fr) Dispositif de gestion et procédé de commande d&#39;architecture réseau
JP6941676B2 (ja) ネットワークアクセス方法及び通信システム
JP2019021953A (ja) Ｒａｎスライスにおけるリソース管理装置及びｒａｎスライスにおけるリソース管理方法
EP3624499B1 (fr) Procédé de commande de communication et système de communication
EP3373517A1 (fr) Procédé et dispositif de configuration pour une fonction de réseau virtuel
JP2020025210A (ja) リソース割当装置およびリソース割当方法
WO2019064677A1 (fr) Dispositif de gestion et procédé de commande d&#39;architecture de réseau
WO2018061921A1 (fr) Procédé de sélection de passerelle et système de communication
US11456919B2 (en) Input and output for target device communication
JPWO2019207909A1 (ja) 対話サーバ
WO2019035287A1 (fr) Procédé de commande de communication et système de communication
JP2019139457A (ja) ログイン支援プログラム、ログイン支援方法、情報処理端末、及び、ログイン支援システム
WO2019159373A1 (fr) Procédé de commande de communication et système de communication
EP3318086A1 (fr) Sélection de réseau basée sur une rétroaction d&#39;utilisateur
CN114500368B (zh) 数据传输方法和装置及采用该装置的路由器
WO2019064676A1 (fr) Dispositif de gestion et procédé de commande d&#39;accès
JP2023116078A (ja) 通信制御装置
WO2022180987A1 (fr) Dispositif de fourniture de service et système de fourniture de service
JP7357061B2 (ja) オーソリゼーション装置
JP2018164235A (ja) 通信端末および通信制御方法
CN114143046B (zh) 一种用户隔离方法、数据传输方法、计算设备及存储介质
JP6968988B2 (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: 18862309

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP