WO2017114327A1 - 网络切片管理装置和网络切片管理方法 - Google Patents

网络切片管理装置和网络切片管理方法 Download PDF

Info

Publication number
WO2017114327A1
WO2017114327A1 PCT/CN2016/111939 CN2016111939W WO2017114327A1 WO 2017114327 A1 WO2017114327 A1 WO 2017114327A1 CN 2016111939 W CN2016111939 W CN 2016111939W WO 2017114327 A1 WO2017114327 A1 WO 2017114327A1
Authority
WO
WIPO (PCT)
Prior art keywords
network slice
network
network element
information
application
Prior art date
Application number
PCT/CN2016/111939
Other languages
English (en)
French (fr)
Inventor
王晓燕
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP16881116.4A priority Critical patent/EP3389313B1/en
Publication of WO2017114327A1 publication Critical patent/WO2017114327A1/zh
Priority to US16/022,972 priority patent/US10638308B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1063—Application servers providing network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/53—Network services using third party service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present invention relates to communication technologies, and in particular, to a network slice management apparatus and a network slice management method.
  • SCEF Service Capability Exposure Function
  • the network architecture 1 includes application servers 101 and 102, service capability opening function device 103, and network elements 104 to 107.
  • the service capability opening function device 103 includes application software programming interfaces 103a to 103c, and the service capability opening function device 103.
  • the application server 101 and the application server 102 can cooperate with the application server 102 to implement a third-party or carrier-trusted domain application (such as an operator-owned service).
  • service capability opening function device 103 can interact with the network elements 104 to 107 to acquire information required by the application.
  • Some typical network capability open functions defined in the current standard are as follows:
  • the application sends a request to the service capability opening function device 103, and the request carrying message type indicates that the number of users in a certain geographical area is acquired, and the geographic area information is carried at the same time.
  • the service capability opening function device 103 maps the geographic area into a Routing Area Identifier (RAI)/Service Area Identifier (SAI) and a Cell Identity (CID, according to the geographical area information and the configuration information in the request message.
  • the cell Identifier list is mapped to a network element such as a mobility management entity (MME, Mobility Management Entity/Serving GPRS Support Node (SGSN)).
  • MME Mobility Management Entity/Serving GPRS Support Node
  • the service capability open function device 103 queries the MME/SGSN node for the RAI/SAI/CID and obtains the number of users at these locations.
  • the business capability open function device 103 returns the number of users to the application (ie, the application server 101 and/or the application server 102 that implements the application).
  • the third-party application requests the service capability open function device 103 to access the QoS request of an application, so that when the user accesses the application, the QoS of the service flow of the corresponding application is guaranteed. Proceed as follows:
  • the application initiates a Qos guarantee request to the service capability open function device 103, where the request message carries the flow characteristics of the application (for example, the IP address of the application server), and the required Qos parameters are applied.
  • the request message carries the flow characteristics of the application (for example, the IP address of the application server), and the required Qos parameters are applied.
  • the service capability opening function device 103 finds a Policy and Charging Control Rule Function (PCRF) according to the configuration, and sends the flow characteristics of the application and the required Qos to the PCRF.
  • PCRF Policy and Charging Control Rule Function
  • the service capability opening function device 103 performs Qos guarantee on the flow of the application according to the flow characteristics of the application.
  • the concept of network slicing is proposed, that is, in order to meet the needs of different IoT applications, different networks are established to meet the needs of different IoT applications.
  • Different networks here can be called network slices.
  • Each network slice contains at least one network element required for each application, depending on the needs of different applications.
  • 3GPP DECOR Proprietary Core Network for Existing Networks
  • it is proposed to establish a corresponding proprietary core network for different MVNO, enterprise or IoT applications to meet different network requirements. It can be seen that the proprietary core network belongs to a form of network slicing.
  • a first embodiment of the present invention provides a network slice management device that cooperates with a service capability open function device and an application management device, and includes: a communicator, configured to receive a creation network from the application management device. a slice request, where the network slice request includes a network slice feature and a network slice feature name; a processor, configured to generate a network slice identifier according to the network slice feature, and establish a name identifier of the network slice identifier and a network slice feature name And a memory for storing the name identification relationship; wherein the transceiver is further configured to send the name identification relationship to the service capability open function device and send a create network slice response to the application management device.
  • the network slice management apparatus further cooperates with the domain name system
  • the processor is further configured to generate a network slice according to the network slice feature, and establish the And mapping, by the transceiver, the mapping relationship to the domain name system.
  • a second embodiment of the present invention provides a network slice management apparatus that cooperates with a service capability opening function device and an application server, and includes: a memory for storing network slice information; and a communicator for Receiving a network element address query request from the service capability open function device, where the network element address query request includes application information and a network element type indication, where the network element type indication is used to indicate that the application server is to acquire a network element of the Internet Protocol address; a processor, configured to acquire network slice information by the memory based on the application information, and acquire, according to the network slice information and the network element type indication, a network element to be acquired by the application server The internet protocol address; and the communicator is further configured to send an internet protocol address of the network element to be acquired by the application server to the service capability open function device.
  • the network element address query request further includes a tracking area identifier
  • the processor is further configured to use, according to the network slice information, the tracking area identifier,
  • the network element type indicates that an internet protocol address of the network element to be acquired by the application server is obtained.
  • the communicator is further configured to send a trace identifier and a network element internet protocol address list to the service capability open function device.
  • a third embodiment of the present invention provides a service capability opening function device that works in conjunction with a domain name system and an application server, including: a memory for storing network slice information; and a communicator for receiving from the application server.
  • An application request wherein the application request includes application information; and a processor configured to acquire network slice information from the memory according to the network slice identifier of the application information, and construct a fully qualified domain name according to the network slice information; wherein the communicator Further for transmitting the fully qualified domain name to the domain name system to obtain an internet protocol address of a corresponding network element, the communicator further configured to send the application request to the network element according to the internet protocol address .
  • the processor is further configured to acquire a tracking area identifier according to the location information, and according to the network slice The information and the tracking area identifier constructing the tracking area identifier fully qualified domain name, and the communicator is further configured to send the tracking area identifier to the fully qualified domain name to the domain name system to obtain a network protocol address of the corresponding network element.
  • the communicator is further configured to send the application request to the network element according to the network protocol address.
  • a fourth embodiment of the present invention provides a service capability opening function device that cooperates with an application server and a network slice management device, and includes: a communicator for receiving a network extension from the network slice management device.
  • Information and an application request from the application server wherein the network topology information includes a network element network protocol address list and a name identification relationship of a network slice identifier and a network slice feature name, the application request including application information; a memory, And storing, by the processor, the network slice identifier according to the network slice name of the application information and the name identifier relationship, and the network slice identifier according to the network slice identifier
  • the network element network address list obtains a network protocol address of the network element, where the communicator is further configured to send the application request to the network element according to the network protocol address.
  • the network topology information further includes a tracking area identifier
  • the application request includes further including location information
  • the processor further configured to Bit
  • the tracking information identifier is obtained by the memory
  • the network protocol address of the network element is obtained by the network element network protocol address list according to the network slice identifier and the tracking area identifier.
  • a fifth embodiment of the present invention provides a network slice management method for a network slice management device, where the network slice management device includes a communicator, a processor, and a memory, where the processors are respectively coupled to The communicator and the memory, the memory is configured to store network slice information, including: receiving, by the communicator, a network element address query request from a service capability open function device, where the network element address query The request includes application information and a network element type indication, where the network element type indicates a network protocol address used to indicate a network element to be acquired by the application server; and the processor acquires a network slice from the memory based on the application information.
  • the network protocol address of the network element to be obtained is to the service capability open function device.
  • the network slice management method further includes: by using the processor, according to the The network slice information, the tracking area identifier, and the network element type indicate that a network protocol address of the network element to be acquired by the application server is obtained.
  • the network slice management method further includes: sending, by the communicator, a trace identifier and a network element network protocol address list to the service Ability to open functional devices.
  • a sixth embodiment of the present invention provides a network slice management method for a service capability open function device, where the service capability open function device includes a communicator, a processor, and a memory, where the processors are respectively coupled.
  • the memory is configured to store network slice information, including: receiving, by the communicator, an application request from an application server, where the application request includes application information;
  • the processor obtains network slice information from the memory according to the network slice identifier of the application information, and constructs a fully qualified domain name according to the network slice information by using the processor, and sends the Fully qualified domain name to the domain name system to obtain a network protocol address of the corresponding network element; and by the communicator, sending the application request to the network element according to the network protocol address.
  • the network slice management method further includes: obtaining, by the processor, according to the location information Tracking area identifier; by the processor, constructing a tracking area identifier fully qualified domain name according to the network slice information and the tracking area identifier; sending, by the communicator, the tracking area identifier complete qualified domain name to the a domain name system to obtain a network protocol address of a corresponding network element; and by the communicator, sending the application request to the network element according to the network protocol address.
  • a seventh embodiment of the present invention provides a network slice for a service capability open function device.
  • the management method, the service capability open function device includes a communicator, a processor, and a memory, wherein the processor is coupled to the communicator and the memory respectively, including: receiving, by the communicator, a network slice management Network topology information of the device; receiving, by the communicator, an application request from the application management device, wherein the network topology information includes a network element network protocol address list, a network slice identifier, and a name of a network slice feature name Identifying a relationship, the application request includes application information; storing, by the memory, the network topology information; by the processor, according to the network slice name of the application information and the name identifier relationship, Obtaining, by the processor, the network slice identifier, where the network protocol address of the network element is obtained by the network element network protocol address list according to the network slice identifier; and by using the communicator, according to the network The protocol address
  • the network topology information further includes a tracking area identifier
  • the application request includes further including location information
  • the network slice management method further includes: Obtaining, by the processor, the tracking area identifier corresponding to the location information by the memory according to the location information; and by using, by the processor, according to the network slice identifier and the tracking area identifier
  • the network element network protocol address list obtains a network protocol address of the network element.
  • the service capability opening function device obtains the information of the corresponding network slice according to the information provided by the application request, and then queries the address of the network element in the network slice and communicates with the network element to ensure the service.
  • the capability open function device can find the middle network element of the network slice of the core network.
  • Figure 1 is a structural diagram of a network architecture
  • FIG. 2 is a signaling flowchart of a network slice management system according to a first embodiment of the present invention
  • FIG. 3 is a structural diagram of a network slice management apparatus according to a first embodiment of the present invention.
  • FIG. 4 is a structural diagram of a service capability opening apparatus according to a first embodiment of the present invention.
  • FIG. 5 is a signaling flowchart of a network slice management system according to a first embodiment of the present invention
  • FIG. 6 is a signaling flowchart of a network slice management system according to a second embodiment of the present invention.
  • FIG. 7 is a signaling flowchart of a network slice management system according to a third embodiment of the present invention.
  • FIG. 8 is a schematic diagram showing the hardware structure of a service capability opening function device according to an embodiment of the present invention.
  • Table 1 is a list of abbreviations and key terms defined in the following examples, please refer to it.
  • FIG. 2 and FIG. 5 are signal flow diagrams of a network slice management system for implementing a network slice management method according to a first embodiment of the present invention.
  • the network slice management system 2 includes an application management device 21 and a network.
  • the network slice management device 22 and the service capability opening device 24 can be two independent devices or in the same device.
  • the application management device 21 can communicate with the network slice management device 22 to establish a network slice, and the application server 25 can transmit the service.
  • the capability opening device 24 works in conjunction with the domain name system 23 and the network element 26.
  • FIG. 3 is a structural diagram of the network slice management device 22 .
  • the network slice management device 22 includes a communication device 221 , a processor 223 , a memory 225 , a power supply 227 , and an incoming interface 229 .
  • the access interface 229 is available
  • the keyboard 229a and the display screen 229b are connected, and the communicator 221 is used for communication between the network slice management device 22 and other devices/devices/network elements or communication networks.
  • the access interface 229 can be connected to other devices according to actual application requirements or the access interface 229 can be omitted, and the keyboard 229a and the display screen 229b are merely examples.
  • FIG. 4 is a structural diagram of the service capability opening device 24 .
  • the service capability opening device 24 includes a communicator 241 , a processor 243 , and a memory 245 .
  • the processor 243 is coupled to the communication device 241 and the memory 245 .
  • the communicator 241 is used for communication between the service capability opening device 24 and other devices/devices or communication networks, and the memory 245 can store operating systems and other applications.
  • the operation of the network cache system will be described below with reference to FIGS. 2, 3, 4, and 5.
  • the application management device 21 may send a create network slice request to the network slice management device 22 based on the requirements of different applications, so that the network slice management device 22 creates a network slice for the needs of the application.
  • the application management device 21 can implement application management of the MVNO/Enterprise/IoT, and the created network slice request includes a network slice feature and a network slice feature name, and the network slice feature can be regarded as a feature of the application, and the network slice feature name can be The name taken by the application management device 21 for the network slice feature is such that the application management device 21 facilitates recording and management.
  • step 201 the communicator 221 of the network slice management device 22 receives the create network slice request from the application management device 21, and the processor 223 of the network slice management device 22 generates a network slice identifier according to the network slice feature that creates the network slice request, to The network side can identify which network slice is determined according to the network slice identifier.
  • step 202 the processor 223 establishes a network slice identifier and a name identifier relationship of the network slice feature name, so that the network slice feature name can be found according to a network slice feature name.
  • the network slice identifier, the memory 225 can be used to store the name identification relationship.
  • the processor 223 In step 203, the processor 223 generates a network slice according to the network slice feature of the network slice request, and takes the automatic meter reading application as an example.
  • the network slice feature can be transmitted without mobility, packet transmission, and low real-time requirements.
  • the network slice includes data that does not need to support mobility, and is not busy when data is sent. You can choose to support the control plane to carry small packets and network elements that do not support the user plane.
  • the processor 223 establishes an image relationship between the network element domain name of the included network element of the network slice and the Internet Protocol address. It should be noted that if the network slice management system 2 does not include the domain name system 23, step 204 may be omitted as appropriate.
  • step 205 the communicator 221 of the network slice management device 22 transmits a name identification relationship to the service capability open function device 24; in step 206, the communicator 221 sends a create network slice response to the application management device 21, where the network is created.
  • the slice response may further include a network slice identifier according to actual requirements.
  • creating a network slice response further includes the network slice identifier as an optional solution; in step 207, the communicator 221 sends an image of the network element domain name and the internet protocol address of the network element. Relation to the domain name system 23.
  • step 207 only needs to be performed in the network slice management system 2 including the domain name system 23, otherwise it may be omitted; the execution order of step 205, step 206 and step 207 does not have a certain relationship, for example, step 207 may be earlier than step 206. Step 207 is performed, or step 206 can be performed earlier than steps 205 and 207.
  • the foregoing steps 200 to 207 can be regarded as a process of creating a network slice. Next, how the application server 25 searches for a network slice after the network slice is created will be further explained.
  • the application server 25 sends an application request to the service capability opening function device 24; in step 209, the communicator 241 of the service capability opening function device 24 receives an application request, where the application request Contains application information, which may include a network slice feature name or a network slice identifier. If the application information is a network slice identifier, the processor 243 of the service capability open function device 24 acquires network slice information from the memory 245 based on the network slice identifier of the application information.
  • the processor 243 first obtains the network slice identifier from the memory 245 according to the network slice identifier and the name identifier of the network slice feature name; the processor 243 further identifies the network slice identifier according to the application information.
  • the memory 245 obtains network slice information, where the obtained network slice information may include, but is not limited to, an internet protocol address, a domain name information, a network element configuration state, and the like of the network element.
  • the processor 243 constructs a fully qualified domain name according to the network slice information, which may be: the host name of the PCRF carries the network slice information, that is, the fully qualified domain name carries the network slice information, for example, the slice identifier. tac.epc. Mnc ⁇ MNC>.mcc ⁇ MCC>.3gppnetwork.org.
  • the communicator 241 of the service capability opening function device 24 sends the fully qualified domain name to the domain name system 23; in step 212, after receiving the fully qualified domain name, the domain name system 23 can be stored according to the fully qualified domain name and the local end.
  • the communicator 241 of the service capability open function device 24 will send an application request to the network element 26 according to the internet protocol address.
  • the network element 26 is a PCRF and the application request is to request the service capability open function device 24 to access the QoS request of an application, so that when the user accesses the application, the QoS of the service flow of the corresponding application is guaranteed, and the service capability is
  • the communicator 241 of the open function device 24 sends the application request to the PCRF according to the Internet Protocol address, the PCRF can guarantee the QoS of the service flow of the corresponding application according to the application request.
  • the processor 243 of the service capability opening function device 24 may obtain a corresponding tracking area identifier according to the location information; in step 210, the processor 243 is configured according to The network slice information and the tracking area identifier construct the tracking area identifier to be a fully qualified domain name, which may be: an extended slice identifier in the tracking area identifier fully qualified domain name, for example: slice identifier. tac-lb ⁇ TAC-low-byte>.tac-hb ⁇ TAC-high-byte>.tac.epc.mnc ⁇ MNC>.mcc ⁇ MCC>.3gppnetwork.org.
  • the communicator 241 of the service capability opening function device 24 sends the tracking area identifier fully qualified domain name to the domain name system 23; in step 212, after receiving the tracking area identifier fully qualified domain name, the domain name system 23 can follow the tracking area. Identifying the fully qualified domain name and the mapping relationship between the network element domain name of the network element stored by the local end and the Internet Protocol address, and obtaining the corresponding Internet Protocol address of the network element; in step 212, the domain name system 23 sends the Internet Protocol address to the service capability.
  • the open function device 24 in step 213, the communicator 241 of the service capability open function device 24 will send an application request to the network element 26 according to the internet protocol address.
  • the network element 26 is an MME/SGSN and the application request is to request acquisition from the service capability open function device 24
  • the number of users in a certain geographical area after the communicator 241 of the service capability opening function device 24 sends an application request to the MME/SGSN according to the Internet Protocol address, the MME/SGSN can open the function device through the service capability according to the application request. 24 returns the number of users in a geographic area to the application server 25.
  • the service capability opening function device 24 acquires the information of the corresponding network slice according to the information provided by the application request, and then queries the address of the network element in the network slice and communicates with the network element. Further, it is ensured that the service capability opening function means 24 can find the network element of the network slice of the core network.
  • the network slice management system 3 includes a network slice management device 22 and a service capability opening device 24.
  • the network slice management device 22 and the service capability opening device 24 can be two independent devices or in the same device.
  • the application server 25 can work with the network slice management device 22 and the network element 26 through the service capability opening device 24. It should be noted that, in this embodiment, the application server 25 searches for the network slice after the network slice is created. For the process of creating the network slice, refer to the related description of steps 200 to 207 of the foregoing first embodiment. This is not mentioned here.
  • the application server 25 sends an application request to the service capability opening function device 24, where the application request includes application information and a network element type indication, and the network element type indicates a network element indicating the Internet Protocol address to be acquired by the application server 25.
  • the application request includes application information, and the application information may include a network slice feature name or a network slice identifier.
  • the communicator 241 of the service capability opening function device 24 receives the application request and sends a network element address query request to the network slice management device 22 according to the application request, where the network element address query request includes the application information and the network element type indication;
  • the application information may include a network slice feature name or a network slice identifier.
  • the communicator 221 of the network slice management device 22 receives the network element address query request; if the application information is a network slice identifier, the processor 223 of the network slice management device 22 obtains the network slice identifier from the memory 225 according to the application information. Network slice information. If the application information includes the network slice feature name, the processor 223 first obtains the network slice identifier from the memory 225 according to the network slice identifier and the name identifier of the network slice feature name; the processor 223 further identifies the network slice identifier according to the application information.
  • the memory 225 obtains network slice information, where the network slice information may be included, but not limited to, an internet protocol address, a domain name information, a network element configuration state, and the like of the network element.
  • step 303 the processor 223 acquires the Internet Protocol address of the network element to be acquired by the application server 25 according to the network slice information and the network element type.
  • step 304 the communicator 221 sends the Internet of the network element to be acquired by the application server 25.
  • the protocol address is sent to the service capability opening function device 24.
  • step 305 the communicator 241 of the service capability opening function device 24 transmits an application request to the network element 26 according to the Internet Protocol address.
  • the network element 26 is a PCRF and the application request is to request the service capability open function device 24 to access the QoS request of the application, so that the user accesses the application, the QoS of the service flow of the corresponding application is guaranteed, and thus the network element
  • the type indicating the network element used to indicate the Internet Protocol address to be acquired by the application server 25 is the PCRF. Open in business capabilities After the communicator 241 of the function device 24 sends the application request to the PCRF according to the Internet Protocol address, the PCRF can guarantee the QoS of the service flow of the corresponding application according to the application request.
  • the processor 243 of the service capability opening function device 24 may obtain a corresponding tracking area identifier according to the location information, and the communicator 241 sends the network element according to the application request.
  • step 303 the processor is configured to acquire an internet protocol address of the network element to be acquired by the application server 25 according to the network slice information, the tracking area identifier, and the network element type indication.
  • step 304 and step 305 as described above are performed, and will not be described here.
  • the network element 26 is the MME/SGSN and the application request is to request the service capability open function device 24 to acquire the number of users in a certain geographical area
  • the network element type indication is used to indicate the Internet protocol to be acquired by the application server 25.
  • the network element of the address is the MME/SGSN.
  • the service capability opening function device 24 acquires information corresponding to the network slice according to the information provided by the application request, and then queries the address of the network element in the network slice and communicates with the network element. Further, it is ensured that the service capability opening function means 24 can find the network element of the network slice of the core network.
  • FIG. 7 is a signaling flowchart of a method for implementing a network slice management system in a network slice management system 4 according to a third embodiment of the present invention.
  • the network slice management system 4 includes a network slice management device 22 and a service capability opening device 24.
  • the network slice management device 22 and the service capability opening device 24 can be two independent devices or in the same device.
  • the application server 25 can work with the network slice management device 22 and the network element 26 through the service capability opening device 24. It should be noted that, in this embodiment, the application server 25 searches for the network slice after the network slice is created. For the process of creating the network slice, refer to the related description of steps 200 to 207 of the foregoing first embodiment. This is not mentioned here.
  • step 400 the communicator 221 of the network slice management device 22 sends the network topology information to the service capability opening device 24, where the network topology information includes but is not limited to the network element internet protocol address list and the network slice identifier and the network slice feature name.
  • the name identification relationship wherein the network element internet protocol address list is used to record the internet protocol address of the network element.
  • the communicator 241 of the business capability opening device 24 receives the network topology information and stores it in the storage 245.
  • step 401 the application server 25 sends an application request to the service capability opening function device 24, wherein the application request includes application information, and the application information may include a network slice feature name or a network slice identifier; in step 402, the service capability opening device 24 The communicator 241 receives the application request; if the application information is a network slice feature name, the processor 243 of the service capability opening device 24 acquires the network slice identifier from the memory 245 according to the network slice name and the name identification relationship of the application information; If the network slice identifier is included, step 402 can be omitted.
  • step 403 the processor 243 acquires an internet protocol address of the network element by the network element internet protocol address list according to the network slice identifier; in step 404, the communicator 241 sends an application request according to the internet protocol address of the network element to Network element 26.
  • the network element 26 is a PCRF and the application request is to request the service capability open function device 24 to access the QoS request of an application, so that when the user accesses the application, the QoS of the service flow of the corresponding application is guaranteed, and the service capability is
  • the communicator 241 of the open function device 24 sends the application request to the PCRF according to the Internet Protocol address, the PCRF can guarantee the QoS of the service flow of the corresponding application according to the application request.
  • the network topology information further includes a tracking area identifier and the application request further includes location information.
  • the processor 243 includes a network slice according to the application information. The name and the name identification relationship are obtained by the memory 245, and the tracking area identifier corresponding to the location information is further obtained by the memory 245 according to the location information; if the application information includes the network slice identifier, the processing is performed in step 402.
  • the 243r acquires the tracking area identifier corresponding to the location information from the memory 245 based only on the location information.
  • the processor 243 obtains the Internet Protocol address of the network element from the network element Internet Protocol address list according to the network slice identifier and the tracking area identifier.
  • the communicator 241 of the service capability opening function device 24 will be based on the Internet Protocol address.
  • the MME/SGSN can return the number of users in a certain geographical area to the application server 25 through the service capability opening function device 24 according to the application request.
  • the service capability opening function device 24 acquires the information of the corresponding network slice according to the information provided by the application request, and then queries the address of the network element in the network slice and communicates with the network element. Further, it is ensured that the service capability opening function means 24 can find the network element of the network slice of the core network.
  • FIG. 8 is a schematic diagram showing the hardware structure of the service capability opening function device 5 according to an embodiment of the present invention.
  • the business capability open function device 5 includes a processor 51, a memory 52, an input/output interface 53, a communication interface 54, and a bus 55.
  • the processor 51, the memory 52, the input/output interface 53 and the communication interface 54 realize a communication connection with each other via the bus 55.
  • the processor 51 can be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for executing related programs.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the memory 52 may be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM).
  • Memory 52 can store operating systems and other applications.
  • the program code for implementing the technical solution provided by the embodiment of the present invention is stored in the memory 52 and executed by the processor 51 when the technical solution provided by the embodiment of the present invention is implemented by software or firmware.
  • the input/output interface 53 is for receiving input data and information, and outputting data such as an operation result.
  • Communication interface 54 implements communication between cache edge server 5 and other devices or communication networks using transceivers such as, but not limited to, a communicator and a transceiver module.
  • Bus 55 may include a path for communicating information between various components of service capability open functionality 5, such as processor 51, memory 52, input/output interface 53, and communication interface 54.
  • the service capability open function device 5 shown in FIG. 8 only shows the processor 51, the memory 52, the input/output interface 53, the communication interface 54, and the bus 55, in the specific implementation process, the technology in the art Personnel should understand that the business capability open function device 5 also contains other devices necessary for normal operation. At the same time, according to specific needs, those skilled in the art should understand that the business capability open function device 5 may also include hardware devices that implement other additional functions. Moreover, those skilled in the art will appreciate that the service capability open function device 5 may also only include the devices or modules necessary to implement the embodiments of the present invention, and does not necessarily include all of the devices shown in FIG.
  • FIG. 8 The hardware structure shown in FIG. 8 and the above description are applicable to various network slice management apparatuses provided by embodiments of the present invention.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

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

Abstract

本发明实施例提供了一种网络切片管理装置、业务能力开放功能装置和网络切片管理方法，透过本发明的网络切片管理装置及业务能力开放功能装置，业务能力开放功能装置根据应用请求提供的信息获取对应网络切片的信息，然后查询网络切片内网元的地址并与网元进行通信，进而确保业务能力开放功能装置可查找到核心网的网络切片的中网元。

Description

网络切片管理装置和网络切片管理方法
本申请要求于2015年12月31日提交中国专利局、申请号为201511031163.7、发明名称为“网络切片管理装置和网络切片管理方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通讯技术，尤其涉及网络切片管理装置和网络切片管理方法。
背景技术
随着移动运营商运营模式的多样化，运营商将网络的信息作为能力开放给第三方，从而激发新的商业模式的产生。在3GPP的网络能力开放项目中，增加了业务能力开放功能(SCEF,Service Capability Exposure Function)实体，进行网络拓扑的屏蔽以及网络信息的开放，其实现业务能力开放功能实体的网落架构1如图1所示。
在图1中，网落架构1包括应用服务器101与102、业务能力开放功能装置103以及网元104到107，业务能力开放功能装置103包括应用软件编程接口103a到103c，业务能力开放功能装置103可藉由各应用软件编程接口103a到103c与应用服务器101与应用服务器102配合工作，应用服务器101与应用服务器102可实现第三方或者运营商信任域的应用(比如运营商自营业务)。
再者，业务能力开放功能装置103可与网元104到107进行交互，获取应用所需信息。当前标准中定义的部分典型网络能力开放功能如下所示：
第三方应用需要获取某个地理区域内用户的数量，步骤如下：
应用向业务能力开放功能装置103发请求，请求携带消息类型指明是获取某地理区域内的用户数，同时携带地理区域信息。
业务能力开放功能装置103根据请求消息中的地理区域信息以及配置信息，将地理区域映像为路由区标识(RAI,Routing Area Identifier)/服务区标识(SAI,Serving Area Identifier)/小区标识(CID,Cell Identifier)列表，进而映射到移动管理实体(MME,Mobility Management Entity/服务GPRS支持节点(SGSN,Serving GPRS Support Node)等网元。
业务能力开放功能装置103向MME/SGSN节点查询RAI/SAI/CID，获取这些位置下的用户数。
业务能力开放功能装置103将用户数返回给应用(即实现该应用的应用服务器101及/或应用服务器102)。
第三方应用向业务能力开放功能装置103请求访问某个应用的Qos请求，以使得用户访问该应用时，保障对应应用的业务流的Qos。步骤如下：
应用向业务能力开放功能装置103发起Qos保障请求，请求消息中携带应用的流特征(例如，应用服务器的IP地址)，应用所需要的Qos参数。
业务能力开放功能装置103根据配置查找到策略与计费控制规则实体(PCRF,Policy and Charging Control Rule Function)，并向PCRF发送应用的流特征以及需要的Qos。
业务能力开放功能装置103根据应用的流特征对应用的流进行Qos保障。
在3GPP SA1的SMARTER项目(面向未来5G网络)中，提出了网络切片的概念，即为了满足不同的物联网应用的需求，建立不同的网络来满足不同的物联网应用的需求。这里不同的网络可以称之为网路切片。根据不同应用的需求，每个网络切片包含每个应用所需要的至少一网元。此外，在当前的3GPP DECOR(专有核心网，针对现有的网络)项目中，提出可以为不同的MVNO、企业或者IoT应用建立相对应的专有核心网，满足其不同的网络需求。可见专有核心网属于网络切片的一种形态。
惟，就专有核心网(网络切片)与网络能力开放特性的结合，目前还没有以使得SCEF查找到专有核心网(即应用对应的网络切片)中网元(即图1中的网元104、网元105、网元106及网元107)的技术方案。
发明内容
本发明的目的在于提供一种可正确查找到核心网的网络切片的中网元的网络切片管理系统。
为达上述目的，本发明第一实施例提供了一种与业务能力开放功能装置以及应用管理装置协同工作的网络切片管理装置，包括：通讯器，用于接收来自所述应用管理装置的创建网络切片请求，其中所述网络切片请求包括网络切片特征以及网络切片特征名称；处理器，用于根据所述网络切片特征产生网络切片标识，以及建立所述网络切片标识及网络切片特征名称的名称标识关系；以及存储器，用于存储所述名称标识关系；其中，所述收发器进一步用于发送所述名称标识关系至所述业务能力开放功能装置以及发送创建网络切片响应至所述应用管理装置。
结合第一实施例，在另种可能的第一实现方式中，所述网络切片管理装置进一步与域名系统协同工作所述处理器进一步用于根据所述网络切片特征产生网络切片，并建立所述网络切片的所包含的网元的网元域名与互联网协议地址的映射关系，所述收发器进一步用于发送所述映射关系至所述域名系统。
为达上述目的，本发明第二实施例提供了一种与业务能力开放功能装置以及应用服务器协同工作的网络切片管理装置，包括：存储器，用于存储网络切片信息；通讯器，用于 接收来自至所述业务能力开放功能装置的网元地址查询请求，其中所述网元地址查询请求包括应用信息以及网元类型指示，所述网元类型指示用于指示所述应用服务器所要获取的互联网协议地址的网元；处理器，用于基于所述应用信息由所述存储器获取网络切片信息，以及根据所述网络切片信息以及所述网元类型指示获取所述应用服务器所要获取的网元的互联网协议地址；以及所述通讯器进一步用于发送所述应用服务器所要获取的网元的互联网协议地址至所述业务能力开放功能装置。
结合第二实施例，在另种可能的第一实现方式中，所述网元地址查询请求进一步包括跟踪区标识，所述处理器进一步用于根据所述网络切片信息、所述跟踪区标识以及所述网元类型指示获取所述应用服务器所要获取的网元的互联网协议地址。
结合第二实施例，在另种可能的第二实现方式中，所述通讯器进一步用于发送踪区标识以及网元互联网协议地址列表至所述业务能力开放功能装置。
为达上述目的，本发明第三实施例提供了一种与域名系统以及应用服务器协同工作的业务能力开放功能装置，包括：存储器用于存储网络切片信息；通讯器用于接收来自所述应用服务器的应用请求，其中所述应用请求包含应用信息；以及处理器用于根据所述应用信息的网络切片标识由所述存储器获取网络切片信息，以及根据所述网络切片信息建构完全合格域名；其中，通讯器进一步用于发送所述完全合格域名至所述域名系统，以获得相对应的网元的互联网协议地址，所述通讯器进一步用于根据所述互联网协议地址发送所述应用请求至所述网元。
结合第三实施例，在另种可能的第一实现方式中，其中所述应用请求进一步包含位置信息，所述处理器更用于根据所述位置信息获取跟踪区标识，以及根据所述网络切片信息跟所述跟踪区标识建构跟踪区标识完全合格域名，所述通讯器进一步用于发送所述跟踪区标识完全合格域名至所述域名系统，以获得相对应的网元的网络协议地址，所述通讯器进一步用于根据所述网络协议地址发送所述应用请求至所述网元。
为达上述目的，本发明第四实施例提供了一种与应用服务器以及网络切片管理装置协同工作的业务能力开放功能装置，包括：通讯器，用于接收来自所述网络切片管理装置的网络拓普信息以及来自所述应用服务器的应用请求，其中所述网络拓普信息包括网元网络协议地址列表以及网络切片标识及网络切片特征名称的名称标识关系，所述应用请求包含应用信息；存储器，用于存储所述网络拓普信息；以及处理器，用于根据所述应用信息的网络切片名称以及所述名称标识关系所述存储器获取所述网络切片标识，以及根据所述网络切片标识由所述网元网络协议地址列表获取网元的网络协议地址；其中，所述通讯器进一步用于根据所述网络协议地址，发送所述应用请求至所述网元。
结合第四实施例，在另种可能的第一实现方式中，其中所述网络拓普信息进一步包括跟踪区标识；所述应用请求包含进一步包含位置信息，所述处理器进一步用于根据所述位 置信息由所述存储器获取所述与位置信息相对应的跟踪区标识，以及根据所述网络切片标识与所述跟踪区标识由所述网元网络协议地址列表获取所述网元的网络协议地址。
为达上述目的，本发明第五实施例提供了一种用于网络切片管理装置的网络切片管理方法，所述网络切片管理装置包含通讯器、处理器及存储器，所述处理器分别耦接至所述通讯器及所述存储器，所述存储器用于存储网络切片信息，包括：藉由所述通讯器，接收来自至业务能力开放功能装置的网元地址查询请求，其中所述网元地址查询请求包括应用信息以及网元类型指示，所述网元类型指示用于指示应用服务器所要获取的网元的网络协议地址；藉由所述处理器，基于所述应用信息由所述存储器获取网络切片信息；藉由所述处理器，根据所述网络切片信息以及所述网元类型指示获取所述应用服务器所要获取的网元的网络协议地址；以及藉由所述通讯器，发送所述应用服务器所要获取的网元的网络协议地址至所述业务能力开放功能装置。
结合第五实施例，在另种可能的第一实现方式中，其中所述网元地址查询请求进一步包括跟踪区标识，所述的网络切片管理方法进一步包括:藉由所述处理器，根据所述网络切片信息、所述跟踪区标识以及所述网元类型指示获取所述应用服务器所要获取的网元的网络协议地址。
结合第五实施例，在另种可能的第二实现方式中，其中所述的网络切片管理方法进一步包括:藉由所述通讯器，发送踪区标识以及网元网络协议地址列表至所述业务能力开放功能装置。
为达上述目的，本发明第六实施例提供了一种用于业务能力开放功能装置的网络切片管理方法，所述业务能力开放功能装置包含通讯器、处理器及存储器，所述处理器分别耦接至所述通讯器及所述存储器，所述存储器用于存储网络切片信息，包括：藉由所述通讯器，接收来自应用服务器的应用请求，其中所述应用请求包含应用信息；藉由所述处理器，根据所述应用信息的网络切片标识由所述存储器获取网络切片信息；藉由所述处理器，根据所述网络切片信息建构完全合格域名；藉由所述通讯器，发送所述完全合格域名至所述域名系统，以获得相对应的网元的网络协议地址；以及藉由所述通讯器，根据所述网络协议地址发送所述应用请求至所述网元。
结合第六实施例，在另种可能的第一实现方式中，其中所述应用请求进一步包含位置信息，所述的网络切片管理方法进一步包括:藉由所述处理器，根据所述位置信息获取跟踪区标识；藉由所述处理器，根据所述网络切片信息跟所述跟踪区标识建构跟踪区标识完全合格域名；藉由所述通讯器，发送所述跟踪区标识完全合格域名至所述域名系统，以获得相对应的网元的网络协议地址；以及藉由所述通讯器，根据所述网络协议地址发送所述应用请求至所述网元。
为达上述目的，本发明第七实施例提供了一种用于业务能力开放功能装置的网络切片 管理方法，所述业务能力开放功能装置包含通讯器、处理器及存储器，所述处理器分别耦接至所述通讯器及所述存储器，包括：藉由所述通讯器，接收来自网络切片管理装置的网络拓普信息；藉由所述通讯器，接收来自所述应用管理装置的应用请求，其中所述网络拓普信息包括网元网络协议地址列表、网络切片标识及网络切片特征名称的名称标识关系，所述应用请求包含应用信息；藉由所述存储器，存储所述网络拓普信息；藉由所述处理器，根据所述应用信息的网络切片名称以及所述名称标识关系由所述存储器获取所述网络切片标识；藉由所述处理器，根据所述网络切片标识由所述网元网络协议地址列表获取网元的网络协议地址；以及藉由所述通讯器，根据所述网络协议地址，发送所述应用请求至所述网元。
结合第七实施例，在另种可能的第一实现方式中，其中所述网络拓普信息进一步包括跟踪区标识，所述应用请求包含进一步包含位置信息，所述的网络切片管理方法进一步包括:藉由所述处理器，根据所述位置信息由所述存储器获取所述与位置信息相对应的跟踪区标识；以及藉由所述处理器，根据所述网络切片标识与所述跟踪区标识由所述网元网络协议地址列表获取所述网元的网络协议地址。
综上所述，透过本发明的实施例，业务能力开放功能装置根据应用请求提供的信息获取对应网络切片的信息，然后查询网络切片内网元的地址并与网元进行通信，进而确保业务能力开放功能装置可查找到核心网的网络切片的中网元。
附图说明
图1是网落架构的结构图；
图2是依据本发明第一实施例的一网络切片管理系统的信令流程图；
图3是依据本发明第一实施例的网络切片管理装置的结构图；
图4是依据本发明第一实施例的业务能力开放装置的结构图；
图5是依据本发明第一实施例的一网络切片管理系统的信令流程图；
图6是依据本发明第二实施例的网络切片管理系统的信令流程图；
图7是依据本发明第三实施例的网络切片管理系统的信令流程图；
图8是依据本发明一实施例的业务能力开放功能装置的硬件结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本 发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
表1 为与后续各实施例相关的缩略语和关键术语定义表，敬请参阅。
Figure PCTCN2016111939-appb-000001
表1
图2及图5是本发明第一实施例的一网络切片管理系统2实现网络切片管理方法的信令流程图，由图2及图5可知，网络切片管理系统2包含应用管理装置21、网络切片管理装置22、域名系统23、业务能力开放装置24、应用服务器25以及网元26。网络切片管理装置22以及业务能力开放装置24可为两个独立的装置或者并于同个装置内，应用管理装置21可跟网络切片管理装置22沟通以建立网络切片，应用服务器25可透过业务能力开放装置24与域名系统23以及网元26配合工作。
请参阅图3，其为网络切片管理装置22的结构图，由图2可知，网络切片管理装置22包含通讯器221、处理器223、存储器225、电源227以及入机接口229，处理器223耦接至通讯器221、存储器225以及入机接口229；电源227用于供电予通讯器221、处理器223以及入机接口229；存储器225可以存储操作系统和其他应用程序；入机接口229可供键盘229a以及显示屏229b连接，通讯器221用于网络切片管理装置22与其他设备/装置/网元或通信网络之间的通信。需注意者，入机接口229可视实际应用需求供其它装置连接或者入机接口229可被省略，而键盘229a以及显示屏229b仅为示例。
请参阅图4，其为业务能力开放装置24的结构图，由图4可知，业务能力开放装置24包含通讯器241、处理器243以及存储器245，处理器243耦接至通讯器241以及存储器245，通讯器241用于业务能力开放装置24与其他设备/装置或通信网络之间的通信，存储器245可以存储操作系统和其他应用程序。为简明起见，下文将结合图2、图3、图4以及图5说明网络缓存系统的作用进行说明。
请先参阅图2，于步骤200中，应用管理装置21可基于不同应用的需求，发送创建网络切片请求至网络切片管理装置22，以让网络切片管理装置22为了应用的需求创建网络切片。具体而言，应用管理装置21可实现MVNO/企业/IoT的应用管理，创建网络切片请求包含网络切片特征以及网络切片特征名称，网络切片特征可视为所述应用的特征，网络切片特征名称可为应用管理装置21为所述网络切片特征所取的名称，以让应用管理装置21便于记录以及管理。
于步骤201中，网络切片管理装置22的通讯器221接收来自应用管理装置21的创建网络切片请求，网络切片管理装置22的处理器223根据创建网络切片请求的网络切片特征产生网络切片标识，以让网络侧可以根据网络切片标识识别出是哪个网络切片；于步骤202中，处理器223建立网络切片标识及网络切片特征名称的名称标识关系，以便可根据一网络切片特征名称找出与其相对应的网络切片标识，存储器225可用于存储名称标识关系。
于步骤203中，处理器223根据创建网络切片请求的网络切片特征产生网络切片，以自动抄表这应用为例，网络切片特征可为无需移动性，小包传输，实时性要求低，而所产生的网络切片则包含不需要支持移动性，非忙时进行数据发送，可以选择支持控制面携带小包以及不支持用户面的网元。于步骤204中，处理器223建立网络切片的所包含的网元的网元域名与互联网协议地址的映像关系。需注意者，如网络切片管理系统2未包含域名系统23，则步骤204可适当省略。
接下来于步骤205中，网络切片管理装置22的通讯器221发送名称标识关系至业务能力开放功能装置24；于步骤206中，通讯器221发送创建网络切片响应至应用管理装置21，其中创建网络切片响应可视实际需求进一步包含网络切片标识，换言之，创建网络切片响应进一步包含网络切片标识为一可选方案；于步骤207中，通讯器221发送网元的网元域名与互联网协议地址的映像关系至域名系统23。需注意者，步骤207仅需在网络切片管理系统2包含域名系统23才执行，否则可省略；步骤205、步骤206及步骤207的执行顺序并无一定关系，例如步骤207可早于步骤206及步骤207被执行，或者步骤206可早于步骤205及步骤207被执行。前述步骤200到步骤207可视为网络切片的创建过程，接下来将进一步说明于网络切片创建后，应用服务器25如何对网络切片进行查找。
请参阅图5，于步骤208中，应用服务器25发送应用请求至业务能力开放功能装置24；于步骤209中，业务能力开放功能装置24的通讯器241接收应用请求，其中所述应用请求 包含应用信息，应用信息可包含网络切片特征名称或网络切片标识。如应用信息是包含网络切片标识，业务能力开放功能装置24的处理器243根据应用信息的网络切片标识由存储器245获取网络切片信息。
如应用信息是包含网络切片特征名称，则处理器243将先根据网络切片标识及网络切片特征名称的名称标识关系，由存储器245获取网络切片标识；处理器243再根据应用信息的网络切片标识由存储器245获取网络切片信息，其中获取网络切片信息可包含但不限于网元的互联网协议地址、域名信息以及网元配置状态等。于步骤210中，处理器243根据网络切片信息建构完全合格域名，具体可以为：PCRF的主机名中携带网络切片信息，即完全合格域名中携带网络切片信息，例如：切片标识.tac.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org。
于步骤211中，业务能力开放功能装置24的通讯器241发送完全合格域名至域名系统23；于步骤212中，域名系统23收到完全合格域名后，便可根据完全合格域名以及本地端所存储的网元的网元域名与互联网协议地址的映像关系，获取相对应的网元的互联网协议地址；于步骤212中，域名系统23发送互联网协议地址到业务能力开放功能装置24；于步骤213中，业务能力开放功能装置24的通讯器241将根据互联网协议地址，将应用请求发送至网元26。
举例而言，如网元26为PCRF且应用请求为向业务能力开放功能装置24请求访问某个应用的QoS请求，以使得用户访问该应用时，保障对应应用的业务流的QoS，在业务能力开放功能装置24的通讯器241将根据互联网协议地址将应用请求发送至PCRF后，PCRF便可根据应用请求保障对应应用的业务流的QoS。
在另个例子中，如应用请求进一步包含位置信息，于步骤209中，业务能力开放功能装置24的处理器243可根据位置信息获取相对应的跟踪区标识；于步骤210中，处理器243根据网络切片信息跟跟踪区标识建构跟踪区标识完全合格域名，具体可以为：在跟踪区标识完全合格域名中扩充切片标识，例如：切片标识.tac-lb<TAC-low-byte>.tac-hb<TAC-high-byte>.tac.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org。
于步骤211中，业务能力开放功能装置24的通讯器241发送跟踪区标识完全合格域名至域名系统23；于步骤212中，域名系统23收到跟踪区标识完全合格域名后，便可根据跟踪区标识完全合格域名以及本地端所存储的网元的网元域名与互联网协议地址的映像关系，获取相对应的网元的互联网协议地址；于步骤212中，域名系统23发送互联网协议地址到业务能力开放功能装置24；于步骤213中，业务能力开放功能装置24的通讯器241将根据互联网协议地址，将应用请求发送至网元26。
举例而言，如网元26为MME/SGSN且应用请求为向业务能力开放功能装置24请求获取 某个地理区域内用户的数量，在业务能力开放功能装置24的通讯器241将根据互联网协议地址将应用请求发送至MME/SGSN后，MME/SGSN便可根据应用请求透过业务能力开放功能装置24返回某个地理区域内用户的数量给应用服务器25。
综上所述，透过本发明的第一实施例，业务能力开放功能装置24根据应用请求提供的信息获取对应网络切片的信息，然后查询网络切片内网元的地址并与网元进行通信，进而确保业务能力开放功能装置24可查找到核心网的网络切片的中网元。
图6是本发明第二实施例的一网络切片管理系统3实现网络切片管理方法的信令流程图，由图6可知，网络切片管理系统3包含网络切片管理装置22、业务能力开放装置24、应用服务器25以及网元26。网络切片管理装置22以及业务能力开放装置24可为两个独立的装置或者并于同个装置内，应用服务器25可透过业务能力开放装置24与网络切片管理装置22以及网元26配合工作。在此需说明的是，本实施例着重于网络切片创建后，应用服务器25如何对网络切片进行查找，关于网络切片的创建过程可参考前述第一实施例步骤200到步骤207的相关说明，在此不加赘述。
于步骤300中，应用服务器25发送应用请求至业务能力开放功能装置24，其中应用请求包含应用信息以及网元类型指示，网元类型指示用于指示应用服务器25所要获取的互联网协议地址的网元，所述应用请求包含应用信息，应用信息可包含网络切片特征名称或网络切片标识。
于步骤301中，业务能力开放功能装置24的通讯器241接收应用请求并根据应用请求发送网元地址查询请求至网络切片管理装置22，其中网元地址查询请求包含应用信息以及网元类型指示；应用信息可包含网络切片特征名称或网络切片标识。
于步骤302中，网络切片管理装置22的通讯器221接收网元地址查询请求；如应用信息是包含网络切片标识，网络切片管理装置22的处理器223根据应用信息的网络切片标识由存储器225获取网络切片信息。如应用信息是包含网络切片特征名称，则处理器223将先根据网络切片标识及网络切片特征名称的名称标识关系，由存储器225获取网络切片标识；处理器223再根据应用信息的网络切片标识由存储器225获取网络切片信息，其中获取网络切片信息可包含但不限于网元的互联网协议地址、域名信息以及网元配置状态等。
于步骤303中，处理器223根据网络切片信息以及网元类型指示获取应用服务器25所要获取的网元的互联网协议地址；于步骤304中，通讯器221发送应用服务器25所要获取的网元的互联网协议地址至业务能力开放功能装置24；于步骤305中，业务能力开放功能装置24的通讯器241将根据互联网协议地址，将应用请求发送至网元26。
举例而言，如网元26为PCRF且应用请求为向业务能力开放功能装置24请求访问某个应用的QoS请求，以使得用户访问该应用时，保障对应应用的业务流的QoS，因此网元类型指示用于指示应用服务器25所要获取的互联网协议地址的网元即为PCRF。在业务能力开放 功能装置24的通讯器241将根据互联网协议地址将应用请求发送至PCRF后，PCRF便可根据应用请求保障对应应用的业务流的QoS。
在另个例子中，如应用请求进一步包含位置信息，于步骤301中，业务能力开放功能装置24的处理器243可根据位置信息获取相对应的跟踪区标识，通讯器241根据应用请求发送网元地址查询请求至网络切片管理装置22其中网元地址查询请求包含跟踪区标识、应用信息以及网元类型指示；应用信息可包含网络切片特征名称或网络切片标识；如何获取网络切片信息如前述步骤302所述，在此不再加以说明。于步骤303中，述处理器用于根据网络切片信息、跟踪区标识以及网元类型指示获取应用服务器25所要获取的网元的互联网协议地址。接下来便执行如前所述的步骤304以及步骤305，在此亦不再加以说明。
举例而言，如网元26为MME/SGSN且应用请求为向业务能力开放功能装置24请求获取某个地理区域内用户的数量，因此网元类型指示用于指示应用服务器25所要获取的互联网协议地址的网元即为MME/SGSN。在业务能力开放功能装置24的通讯器241将根据互联网协议地址将应用请求发送至MME/SGSN后，MME/SGSN便可根据应用请求透过业务能力开放功能装置24返回某个地理区域内用户的数量给应用服务器25。
综上所述，透过本发明的第二实施例，业务能力开放功能装置24根据应用请求提供的信息获取对应网络切片的信息，然后查询网络切片内网元的地址并与网元进行通信，进而确保业务能力开放功能装置24可查找到核心网的网络切片的中网元。
图7是本发明第三实施例的一网络切片管理系统4实现网络切片管理方法的信令流程图，由图7可知，网络切片管理系统4包含网络切片管理装置22、业务能力开放装置24、应用服务器25以及网元26。网络切片管理装置22以及业务能力开放装置24可为两个独立的装置或者并于同个装置内，应用服务器25可透过业务能力开放装置24与网络切片管理装置22以及网元26配合工作。在此需说明的是，本实施例着重于网络切片创建后，应用服务器25如何对网络切片进行查找，关于网络切片的创建过程可参考前述第一实施例步骤200到步骤207的相关说明，在此不加赘述。
于步骤400中，网络切片管理装置22的通讯器221发送网络拓普信息至业务能力开放装置24，其中网络拓普信息包含但不限于网元互联网协议地址列表以及网络切片标识及网络切片特征名称的名称标识关系，其中网元互联网协议地址列表用于记录网元的互联网协议地址。业务能力开放装置24的通讯器241接收网络拓普信息，并将其存储到储存器245。
于步骤401中，应用服务器25发送应用请求至业务能力开放功能装置24，其中应用请求包含应用信息，应用信息可包含网络切片特征名称或网络切片标识；于步骤402中，业务能力开放装置24的通讯器241接收应用请求；如应用信息是包含网络切片特征名称，业务能力开放装置24的处理器243根据应用信息的网络切片名称以及名称标识关系由存储器245获取所述网络切片标识；如应用信息是包含网络切片标识，则步骤402可省略。
于步骤403中，处理器243根据所述网络切片标识由所述网元互联网协议地址列表获取网元的互联网协议地址；于步骤404中，通讯器241根据网元的互联网协议地址发送应用请求至网元26。
举例而言，如网元26为PCRF且应用请求为向业务能力开放功能装置24请求访问某个应用的QoS请求，以使得用户访问该应用时，保障对应应用的业务流的QoS，在业务能力开放功能装置24的通讯器241将根据互联网协议地址将应用请求发送至PCRF后，PCRF便可根据应用请求保障对应应用的业务流的QoS。
在另个例子中，所述网络拓普信息进一步包括跟踪区标识且应用请求更包含位置信息，于步骤402中，如应用信息是包含网络切片特征名称，处理器243除了根据应用信息的网络切片名称以及名称标识关系由存储器245获取所述网络切片标识，并进一步根据位置信息由存储器245获取与位置信息相对应的跟踪区标识；如如应用信息是包含网络切片标识，于步骤402中，处理器243仅根据位置信息由存储器245获取与位置信息相对应的跟踪区标识。于步骤403中，处理器243根据网络切片标识以及跟踪区标识，由网元互联网协议地址列表获取网元的互联网协议地址。
举例而言，如网元26为MME/SGSN且应用请求为向业务能力开放功能装置24请求获取某个地理区域内用户的数量，在业务能力开放功能装置24的通讯器241将根据互联网协议地址将应用请求发送至MME/SGSN后，MME/SGSN便可根据应用请求透过业务能力开放功能装置24返回某个地理区域内用户的数量给应用服务器25。
综上所述，透过本发明的第三实施例，业务能力开放功能装置24根据应用请求提供的信息获取对应网络切片的信息，然后查询网络切片内网元的地址并与网元进行通信，进而确保业务能力开放功能装置24可查找到核心网的网络切片的中网元。
图8是依据本发明一实施例的业务能力开放功能装置5的硬件结构示意图。如图8所示，业务能力开放功能装置5包括处理器51、存储器52、输入/输出接口53、通信接口54和总线55。其中，处理器51、存储器52、输入/输出接口53和通信接口54通过总线55实现彼此之间的通信连接。
处理器51可以采用通用的中央处理器(Central Processing Unit，CPU)，微处理器，应用专用集成电路(Application Specific Integrated Circuit，ASIC)，或者一个或多个集成电路，用于执行相关程序，以实现本发明实施例所提供的技术方案。
存储器52可以是只读存储器(Read Only Memory，ROM)，静态存储设备，动态存储设备或者随机存取存储器(Random Access Memory，RAM)。存储器52可以存储操作系统和其他应用程序。在通过软件或者固件来实现本发明实施例提供的技术方案时，用于实现本发明实施例提供的技术方案的程序代码保存在存储器52中，并由处理器51来执行。
输入/输出接口53用于接收输入的数据和信息，输出操作结果等数据。
通信接口54使用例如但不限于通讯器以及收发模块一类的收发装置，来实现缓存边缘服务器5与其他设备或通信网络之间的通信。
总线55可包括一通路，在业务能力开放功能装置5各个部件(例如处理器51、存储器52、输入/输出接口53和通信接口54)之间传送信息。
应注意，尽管图8所示的业务能力开放功能装置5仅仅示出了处理器51、存储器52、输入/输出接口53、通信接口54以及总线55，但是在具体实现过程中，本领域的技术人员应当明白，业务能力开放功能装置5还包含实现正常运行所必须的其他器件。同时，根据具体需要，本领域的技术人员应当明白，业务能力开放功能装置5还可包含实现其他附加功能的硬件器件。此外，本领域的技术人员应当明白，业务能力开放功能装置5也可仅仅包含实现本发明实施例所必须的器件或模块，而不必包含图8中所示的全部器件。
图8所示的硬件结构以及上述描述适用于本发明实施例所提供的各种网络切片管理装置。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，上述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，上述的存储介质可为磁盘、光盘、只读存储记忆体(ROM：Read-Only Memory)或随机存储记忆体(RAM：Random Access Memory)等。
本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本发明的限制。

Claims (14)

  1. 一种与业务能力开放功能装置以及应用服务器协同工作的网络切片管理装置，其特征在于，包括：
    存储器，用于存储网络切片信息；
    通讯器，用于接收来自至所述业务能力开放功能装置的网元地址查询请求，其中所述网元地址查询请求包括应用信息以及网元类型指示，所述网元类型指示用于指示所述应用服务器所要获取的互联网协议地址的网元；
    处理器，用于基于所述应用信息由所述存储器获取网络切片信息，以及根据所述网络切片信息以及所述网元类型指示获取所述应用服务器所要获取的网元的互联网协议地址；以及
    所述通讯器进一步用于发送所述应用服务器所要获取的网元的互联网协议地址至所述业务能力开放功能装置。
  2. 如权利要求1所述的网络切片管理装置，其特征在于，其中所述网元地址查询请求进一步包括跟踪区标识，所述处理器进一步用于根据所述网络切片信息、所述跟踪区标识以及所述网元类型指示获取所述应用服务器所要获取的网元的互联网协议地址。
  3. 如权利要求1所述的网络切片管理装置，其特征在于，其中所述通讯器进一步用于发送踪区标识以及网元互联网协议地址列表至所述业务能力开放功能装置。
  4. 一种与域名系统以及应用服务器协同工作的业务能力开放功能装置，其特征在于，包括：
    存储器，用于存储网络切片信息
    通讯器，用于接收来自所述应用服务器的应用请求，其中所述应用请求包含应用信息；以及
    处理器，用于根据所述应用信息的网络切片标识由所述存储器获取网络切片信息，以及根据所述网络切片信息建构完全合格域名；
    其中，通讯器进一步用于发送所述完全合格域名至所述域名系统，以获得相对应的网元的互联网协议地址，所述通讯器进一步用于根据所述互联网协议地址发送所述应用请求至所述网元。
  5. 如权利要求4所述的网络切片管理装置，其特征在于，其中所述应用请求进一步包含位置信息，所述处理器更用于根据所述位置信息获取跟踪区标识，以及根据所述网络切片信息跟所述跟踪区标识建构跟踪区标识完全合格域名，所述通讯器进一步用于发送所述跟踪区标识完全合格域名至所述域名系统，以获得相对应的网元的互联网协议地址，所述通讯器进一步用于根据所述互联网协议地址发送所述应用请求至所述网元。
  6. 一种与应用服务器以及网络切片管理装置协同工作的业务能力开放功能装置，其特征在于，包括：
    通讯器，用于接收来自所述网络切片管理装置的网络拓普信息以及来自所述应用服务器的应用请求，其中所述网络拓普信息包括网元互联网协议地址列表以及网络切片标识及网络切片特征名称的名称标识关系，所述应用请求包含应用信息；
    存储器，用于存储所述网络拓普信息；以及
    处理器，用于根据所述应用信息的网络切片名称以及所述名称标识关系所述存储器获取所述网络切片标识，以及根据所述网络切片标识由所述网元互联网协议地址列表获取网元的互联网协议地址；
    其中，所述通讯器进一步用于根据所述互联网协议地址，发送所述应用请求至所述网元。
  7. 如权利要求6所述的网络切片管理装置，其特征在于，其中所述网络拓普信息进一步包括跟踪区标识；所述应用请求包含进一步包含位置信息，所述处理器进一步用于根据所述位置信息由所述存储器获取所述与位置信息相对应的跟踪区标识，以及根据所述网络切片标识与所述跟踪区标识由所述网元互联网协议地址列表获取所述网元的互联网协议地址。
  8. 一种用于网络切片管理装置的网络切片管理方法，所述网络切片管理装置包含通讯器、处理器及存储器，所述处理器分别耦接至所述通讯器及所述存储器，所述存储器用于存储网络切片信息，其特征在于，包括：
    藉由所述通讯器，接收来自至业务能力开放功能装置的网元地址查询请求，其中所述网元地址查询请求包括应用信息以及网元类型指示，所述网元类型指示用于指示应用服务器所要获取的网元的互联网协议地址；
    藉由所述处理器，基于所述应用信息由所述存储器获取网络切片信息；
    藉由所述处理器，根据所述网络切片信息以及所述网元类型指示获取所述应用服务器所要获取的互联网协议地址的网元；以及
    藉由所述通讯器，发送所述应用服务器所要获取的网元的互联网协议地址至所述业务能力开放功能装置。
  9. 如权利要求8所述的网络切片管理方法，其特征在于，其中所述网元地址查询请求进一步包括跟踪区标识，所述的网络切片管理方法进一步包括:
    藉由所述处理器，根据所述网络切片信息、所述跟踪区标识以及所述网元类型指示获取所述应用服务器所要获取的网元的互联网协议地址。
  10. 如权利要求8所述的网络切片管理方法，其特征在于，其中所述的网络切片管理方法进一步包括:
    藉由所述通讯器，发送踪区标识以及网元互联网协议地址列表至所述业务能力开放功能装置。
  11. 一种用于业务能力开放功能装置的网络切片管理方法，所述业务能力开放功能装置包含通讯器、处理器及存储器，所述处理器分别耦接至所述通讯器及所述存储器，所述存储器用于存储网络切片信息，其特征在于，包括：
    藉由所述通讯器，接收来自应用服务器的应用请求，其中所述应用请求包含应用信息；
    藉由所述处理器，根据所述应用信息的网络切片标识由所述存储器获取网络切片信息；
    藉由所述处理器，根据所述网络切片信息建构完全合格域名；
    藉由所述通讯器，发送所述完全合格域名至所述域名系统，以获得相对应的网元的互联网协议地址；以及
    藉由所述通讯器，根据所述互联网协议地址发送所述应用请求至所述网元。
  12. 如权利要求11所述的网络切片管理方法，其特征在于，其中所述应用请求进一步包含位置信息，所述的网络切片管理方法进一步包括:
    藉由所述处理器，根据所述位置信息获取跟踪区标识；
    藉由所述处理器，根据所述网络切片信息跟所述跟踪区标识建构跟踪区标识完全合格域名；
    藉由所述通讯器，发送所述跟踪区标识完全合格域名至所述域名系统，以获得相对应的网元的互联网协议地址；以及
    藉由所述通讯器，根据所述互联网协议地址发送所述应用请求至所述网元。
  13. 一种用于业务能力开放功能装置的网络切片管理方法，所述业务能力开放功能装置包含通讯器、处理器及存储器，所述处理器分别耦接至所述通讯器及所述存储器，其特征在于，包括：
    藉由所述通讯器，接收来自网络切片管理装置的网络拓普信息；
    藉由所述通讯器，接收来自所述应用管理装置的应用请求，其中所述网络拓普信息包括网元互联网协议地址列表以及网络切片标识及网络切片特征名称的名称标识关系，所述应用请求包含应用信息；
    藉由所述存储器，存储所述网络拓普信息；
    藉由所述处理器，根据所述应用信息的网络切片名称以及所述名称标识关系由所述存储器获取所述网络切片标识；
    藉由所述处理器，根据所述网络切片标识由所述网元互联网协议地址列表获取网元的互联网协议地址；以及
    藉由所述通讯器，根据所述互联网协议地址，发送所述应用请求至所述网元。
  14. 如权利要求13所述的网络切片管理方法，其特征在于，其中所述网络拓普信息进一步包括跟踪区标识，所述应用请求包含进一步包含位置信息，所述的网络切片管理方法进一步包括:
    藉由所述处理器，根据所述位置信息由所述存储器获取所述与位置信息相对应的跟踪区标识；以及
    藉由所述处理器，根据所述网络切片标识与所述跟踪区标识由所述网元互联网协议地址列表获取所述网元的互联网协议地址。
PCT/CN2016/111939 2015-12-31 2016-12-24 网络切片管理装置和网络切片管理方法 WO2017114327A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16881116.4A EP3389313B1 (en) 2015-12-31 2016-12-24 Network slice management apparatus and network slice management method
US16/022,972 US10638308B2 (en) 2015-12-31 2018-06-29 Network slice management apparatus and network slice management method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201511031163.7 2015-12-31
CN201511031163.7A CN106937362B (zh) 2015-12-31 2015-12-31 网络切片管理装置和网络切片管理方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/022,972 Continuation US10638308B2 (en) 2015-12-31 2018-06-29 Network slice management apparatus and network slice management method

Publications (1)

Publication Number Publication Date
WO2017114327A1 true WO2017114327A1 (zh) 2017-07-06

Family

ID=59224621

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/111939 WO2017114327A1 (zh) 2015-12-31 2016-12-24 网络切片管理装置和网络切片管理方法

Country Status (4)

Country Link
US (1) US10638308B2 (zh)
EP (1) EP3389313B1 (zh)
CN (1) CN106937362B (zh)
WO (1) WO2017114327A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019029645A1 (zh) * 2017-08-11 2019-02-14 华为技术有限公司 一种网络切片管理方法及装置
CN110621045A (zh) * 2018-06-20 2019-12-27 华为技术有限公司 一种物联网业务路由的方法

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109548137B (zh) 2017-08-11 2022-04-22 华为技术有限公司 会话信息管理方法和装置
CN109041138B (zh) 2017-08-11 2019-08-13 华为技术有限公司 通信方法及源基站、目标基站、核心网设备
CN109429244B (zh) * 2017-08-29 2022-06-28 中兴通讯股份有限公司 一种网络切片子网实例的管理数据隔离的方法和装置
CN109600760B (zh) * 2017-09-30 2022-04-22 华为技术有限公司 网络管理方法、设备及系统
CN109600768B (zh) 2017-09-30 2022-06-07 华为技术有限公司 网络切片的管理方法、设备及系统
CN109768875B (zh) * 2017-11-10 2021-10-15 华为技术有限公司 网络切片的策略管理方法、装置、设备及系统
CN110022223B (zh) * 2018-01-10 2022-01-21 中兴通讯股份有限公司 一种网络切片配置方法、第一网元和第二网元
CN110048987B (zh) * 2018-01-15 2021-06-22 华为技术有限公司 一种多媒体系统入口网元的选择方法、注册方法及装置
CN110120879B (zh) * 2018-02-06 2020-12-01 华为技术有限公司 一种应用服务水平协议的保障方法、设备及系统
CN111356182A (zh) * 2018-12-21 2020-06-30 中兴通讯股份有限公司 一种资源的调度、处理方法及装置
US12002117B1 (en) * 2019-03-12 2024-06-04 T-Mobile Innovations Llc Advanced metering with distributed ledger control
CN114765787A (zh) * 2020-12-31 2022-07-19 阿里巴巴集团控股有限公司 服务请求与提供方法、设备及存储介质
CN114915670B (zh) * 2022-04-12 2023-10-24 中国人民解放军战略支援部队信息工程大学 一种支持多种协议共存的网络切片实现方法与装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008054189A (ja) * 2006-08-28 2008-03-06 Funai Electric Co Ltd 通信システム及び遠隔監視システム
JP2008227756A (ja) * 2007-03-09 2008-09-25 Softbank Mobile Corp Ｉｐアドレス管理システム
CN102461316A (zh) * 2009-06-18 2012-05-16 瑞典爱立信有限公司 移动电信系统中的方法和布置
CN104581990A (zh) * 2013-10-23 2015-04-29 思科技术公司 虚拟演进分组核心中的节点选择

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101616169B (zh) * 2008-06-23 2013-03-13 华为技术有限公司 选择服务提供实体的方法、系统、服务选择实体、服务管理实体
JP5788294B2 (ja) * 2011-11-08 2015-09-30 株式会社日立製作所 ネットワークシステムの管理方法
WO2016190670A1 (ko) * 2015-05-26 2016-12-01 엘지전자 주식회사 무선 통신 시스템에서 데이터 트래픽을 전송하는 방법 및 단말
US10506471B2 (en) * 2015-06-11 2019-12-10 Nec Corporation Network management system and method for a shared radio access network, RAN, infrastructure
WO2017003235A1 (ko) * 2015-06-30 2017-01-05 엘지전자(주) 무선 통신 시스템에서 그룹 메시지를 전송하기 위한 방법 및 이를 위한 장치
CN108029007B (zh) * 2015-07-31 2022-04-26 康维达无线有限责任公司 用于小小区网络中的服务层和应用的通知和触发
KR102409214B1 (ko) * 2015-08-03 2022-06-15 콘비다 와이어리스, 엘엘씨 사용자 장비를 위한 이동 코어 네트워크 서비스 노출
WO2017025152A1 (en) * 2015-08-07 2017-02-16 Nec Europe Ltd. Network management method and system for a shared radio access network, ran, infrastructure
CN108141756A (zh) * 2015-09-29 2018-06-08 瑞典爱立信有限公司 促成网络切片管理
WO2017063708A1 (en) * 2015-10-15 2017-04-20 Telefonaktiebolaget Lm Ericsson (Publ) Apparatus and method for attaching user equipment to a mobile communications network
WO2017067599A1 (en) * 2015-10-22 2017-04-27 Siemens Aktiengesellschaft Device for use in a network, controller, network and method
WO2017086848A1 (en) * 2015-11-18 2017-05-26 Telefonaktiebolaget Lm Ericsson (Publ) Radio network node, network node and methods performed therein
WO2017113100A1 (en) * 2015-12-29 2017-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Network nodes and methods performed therein for enabling communication in a communication network
EP3398305B1 (en) * 2015-12-29 2021-10-27 Telefonaktiebolaget LM Ericsson (PUBL) Method and architecture for virtualized network service provision

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008054189A (ja) * 2006-08-28 2008-03-06 Funai Electric Co Ltd 通信システム及び遠隔監視システム
JP2008227756A (ja) * 2007-03-09 2008-09-25 Softbank Mobile Corp Ｉｐアドレス管理システム
CN102461316A (zh) * 2009-06-18 2012-05-16 瑞典爱立信有限公司 移动电信系统中的方法和布置
CN104581990A (zh) * 2013-10-23 2015-04-29 思科技术公司 虚拟演进分组核心中的节点选择

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Architecture Enhancements for Service Capability Exposure (Release 13)", 3GPP TR 23.708 V13.0.0, 21 June 2015 (2015-06-21), XP051294242 *
See also references of EP3389313A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019029645A1 (zh) * 2017-08-11 2019-02-14 华为技术有限公司 一种网络切片管理方法及装置
CN110621045A (zh) * 2018-06-20 2019-12-27 华为技术有限公司 一种物联网业务路由的方法
CN110621045B (zh) * 2018-06-20 2022-05-13 华为云计算技术有限公司 一种物联网业务路由的方法
US11716669B2 (en) 2018-06-20 2023-08-01 Huawei Cloud Computing Technologies Co., Ltd. Internet of things service routing method

Also Published As

Publication number Publication date
EP3389313B1 (en) 2020-03-25
EP3389313A4 (en) 2018-11-07
US10638308B2 (en) 2020-04-28
CN106937362B (zh) 2020-04-14
CN106937362A (zh) 2017-07-07
US20180310169A1 (en) 2018-10-25
EP3389313A1 (en) 2018-10-17

Similar Documents

Publication Publication Date Title
WO2017114327A1 (zh) 网络切片管理装置和网络切片管理方法
US11864019B2 (en) Time-sensitive networking communication method and apparatus
KR102605458B1 (ko) 분석 기능 발견 방법 및 장치
KR102046700B1 (ko) 메시지 버스 서비스 디렉토리
US20200195511A1 (en) Network management method and related device
WO2020224463A1 (zh) 一种数据分析方法及装置
WO2019029525A1 (zh) 网络功能信息的管理方法及相关设备
JP7514383B2 (ja) ネットワーク機能発見サービス向上を提供するための方法、システムおよびコンピュータ読取可能媒体
WO2019223661A1 (zh) 一种识别应用标识的方法、设备及系统
WO2021057128A1 (zh) 一种基于nf的通信方法、设备及存储介质
WO2021004528A1 (zh) 应用实例的地址获取方法、装置、设备及存储介质
US20230008647A1 (en) Connection establishment method, communication apparatus, and system
WO2020249032A1 (zh) 通信方法及装置
CN108199913B (zh) 一种实现时延测试的方法及设备
WO2018196843A1 (zh) 资源请求方法及装置
WO2020038337A1 (zh) 网络配置方法、装置及系统
US10135916B1 (en) Integration of service scaling and external health checking systems
US11122131B1 (en) Edge cloud resource location using enhanced DNS service
WO2020253626A1 (zh) 确定边缘应用的方法、装置、设备及存储介质
CN112752352B (zh) 一种中间会话管理功能i-smf确定方法和设备
US10334414B2 (en) Managing multiple mobile devices on different operator networks
US10334413B2 (en) Managing mobile devices on different operator networks
EP3422674A1 (en) A method of resolving a domain name by a dns server to a plurality of ip addresses based on location information of the user equipment
WO2024001811A1 (zh) 信息发送方法和装置
EP4311280A1 (en) Communication method and device

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016881116

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016881116

Country of ref document: EP

Effective date: 20180710