WO2020001439A1 - 一种配置方法及装置 - Google Patents

一种配置方法及装置 Download PDF

Info

Publication number
WO2020001439A1
WO2020001439A1 PCT/CN2019/092814 CN2019092814W WO2020001439A1 WO 2020001439 A1 WO2020001439 A1 WO 2020001439A1 CN 2019092814 W CN2019092814 W CN 2019092814W WO 2020001439 A1 WO2020001439 A1 WO 2020001439A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network element
status information
service
network slice
Prior art date
Application number
PCT/CN2019/092814
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 EP19826341.0A priority Critical patent/EP3806394A4/en
Publication of WO2020001439A1 publication Critical patent/WO2020001439A1/zh
Priority to US17/131,231 priority patent/US11824713B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0866—Checking the configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality

Definitions

  • the present application relates to the field of mobile communication technology, and in particular, to a configuration method and device.
  • the information of the network slice may include the type of the corresponding network slice.
  • the type of the network slice includes: enhanced mobile broadband (eMBB) type network slice, ultra-low latency ( ultra low latency) type network slicing, etc.
  • eMBB enhanced mobile broadband
  • ultra-low latency ultra low latency
  • This application provides a configuration method and device, which are used to implement the configuration of system characteristics.
  • the present application provides a configuration method.
  • the method includes: a network storage network element receiving configuration information from a network slice management network element, the configuration information including network slice information, system characteristics supported by the network slice, network function NF corresponding to the system characteristic, and NF service corresponding to NF; network
  • the storage network element stores configuration information. Based on this solution, configuration of network slicing related information for network storage network elements can be realized.
  • the system characteristic includes a first system characteristic
  • the NF corresponding to the first system characteristic includes a first NF
  • the NF service corresponding to the NF includes a first NF service corresponding to the first NF.
  • the method further includes : The network storage network element receives a notification message from the first network element.
  • the first network element is a network element that supports the first NF.
  • the notification message includes status information of the NF service of the first network element.
  • the status information includes status information of the first NF service; the network storage network element determines status information of the first system characteristic according to the status information of the first NF service. Based on this solution, the status information of system characteristics in the configuration information can be updated.
  • the state information of the NF service of the first network element includes a total number of times that the NF service is called by other multiple network elements within a preset time period and / or a number of times that each NF service is called separately by other single network elements.
  • the present application provides a configuration method.
  • the method includes: the network slice management network element sends configuration information to the network storage network element, the configuration information includes the network slice information, the system characteristics supported by the network slice, the network function NF corresponding to the system characteristic, and the NF service corresponding to the NF; the network slice
  • the management network element receives a configuration completion instruction from the network storage network element. Based on this solution, configuration of network slicing related information for network storage network elements can be realized.
  • the present application provides a configuration method.
  • the method includes: the network storage network element receives a request message from the second network element, the request message includes information about the network slice, the request message is used to request to obtain status information of system features supported by the network slice; the network storage network element according to the request message, Send status information of system features supported by the network slice to the second network element.
  • the second network element can obtain the status information of the system characteristics supported by the network slice from the network storage network element, and the status information of the system characteristics supported by the network slice includes the status information of the system characteristic corresponding to the NF service.
  • the request message further includes a specified time period, and the request message is specifically used to request to obtain status information of a system feature supported by the network slice within the specified time period; then the network storage network element according to the request A message that sends status information of system characteristics supported by the network slice to the second network element includes: the network storage network element sends status information of system characteristics supported by the network slice to the second network element within a specified time period.
  • the state information of the system characteristics supported by the network slice in the specified time period includes the total number of times that the NF service corresponding to the system characteristic is called by other multiple network elements in the specified time period and / or Number of calls made by other single NEs.
  • the request message further includes a subscription period
  • the request message is specifically used to request to periodically obtain status information of system characteristics supported by the network slice; then, the network storage network element sends a second network to the second network according to the request message.
  • the meta sending of the status information of the system features supported by the network slice includes: the network storage network element periodically sends the status information of the system features supported by the network slice to the second network element according to the subscription period in the request message.
  • the status information of the system characteristics supported by the network slice includes the total number of times that the NF service corresponding to the system characteristic is called by other multiple network elements during the subscription cycle and / or is separately called by other single network elements. frequency.
  • the present application provides a configuration method.
  • the method includes: the second network element sends a request message to the network storage network element, the request message includes information about the network slice, and the request message is used to request to obtain status information of system features supported by the network slice; the second network element receives the information from the network storage network Meta network slice supports state information for system features. Based on this solution, the second network element can obtain the status information of the system characteristics supported by the network slice from the network storage network element, and the status information of the system characteristics supported by the network slice includes the status information of the system characteristic corresponding to the NF service.
  • the request message further includes a specified time period
  • the request message is specifically used to request to obtain status information of a system feature supported by the network slice within the specified time period
  • the second network element receives the information from the network.
  • the status information of the system characteristics supported by the network slice of the storage network element includes: the second network element receives the status information of the system characteristics supported by the network slice from the network storage network element within a specified time period.
  • the state information of the system characteristics supported by the network slice in the specified time period includes the total number of times that the NF service corresponding to the system characteristic is called by other multiple network elements in the specified time period and / or Number of calls made by other single NEs.
  • the request message further includes a subscription period.
  • the request message is specifically used to request to periodically obtain status information of system characteristics supported by the network slice.
  • the second network element receives the network slice support from the network storage network element.
  • the state information of the system characteristics includes: the second network element receives the state information of the system characteristics supported by the network slice that the network storage network element periodically sends according to the subscription period.
  • the status information of the system characteristics supported by the network slice includes the total number of times that the NF service corresponding to the system characteristic is called by other multiple network elements during the subscription cycle and / or is separately called by other single network elements. frequency.
  • the request message in any one of the foregoing first to fourth aspects further includes a second system characteristic among the system characteristics supported by the network slice, and the status information of the system characteristics supported by the network slice is specific It includes status information of the NF service corresponding to the second system characteristic.
  • the present application provides a device, which may be a network storage network element, a network slice management network element, a second network element, or a chip.
  • the device has a function of implementing the embodiments of any one of the first aspect, the second aspect, the third aspect, or the fourth aspect described above. This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an apparatus including: a processor and a memory; the memory is configured to store computer execution instructions, and when the apparatus is running, the processor executes the computer execution instructions stored in the memory, so that the apparatus executes The configuration method according to the first aspect or any of the first aspects, or to cause the device to perform the configuration method according to the second aspect or any of the second aspect, or to cause the device to perform the first
  • the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores instructions, and when the computer-readable storage medium runs on the computer, the computer executes the methods described in the above aspects.
  • the present application also provides a computer program product including instructions, which when executed on a computer, causes the computer to execute the methods described in the above aspects.
  • the present application further provides a system including the network storage network element in the first aspect or any one of the embodiments of the first aspect, and the network slice management network element in the second aspect.
  • the present application further provides a system including the third aspect or the network storage network element in any one of the third aspects, and the fourth aspect or any one of the fourth aspects.
  • the second network element in.
  • FIG. 1 is a schematic diagram of a possible network architecture provided by this application.
  • FIG. 2 is a schematic diagram of another possible network architecture provided by this application.
  • FIG. 3 is a flowchart of a configuration method provided by the present application.
  • FIG. 5 is a schematic diagram of a device provided by this application.
  • FIG. 6 is a schematic diagram of another device provided by the present application.
  • the network architecture and service scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that with the network The evolution of the architecture and the emergence of new business scenarios. The technical solutions provided in the embodiments of the present application are also applicable to similar technical issues.
  • the network architecture includes a network slice management network element and a network storage network element.
  • a network slice management network element may be used to configure a network storage network element, including information on configuring network slices, system features supported by the network slices, and network functions (NF) and NF services corresponding to the system features.
  • the network slice management network element may be an Operation Management and Maintenance (OAM) system.
  • OAM Operation Management and Maintenance
  • the network storage network element may be, for example, a network storage function (NRF) network element in a 5th generation (5G) communication system.
  • the functions of the network storage network element mainly include the registration, de-registration, and discovery of network functions and services.
  • the network storage network element can store the description information of the deployed network functions, such as the identification and address of network functions, supported service information, and network. Slice identification, etc.
  • the network storage network element may be referred to as an NRF network element, and may also have other names, which are not limited in this application.
  • the network architecture includes an access network device, a mobility management network element, a session management network element, a first network slice management network element, a second network slice management network element, a first network storage network element, and a second network storage network element .
  • the first network slice management network element is used to configure the first network storage network element on the core network side
  • the second network slice management network element is used to configure the second network storage network element of the access network.
  • the first network slice management network element and the second network slice management network element may be the same network element or different network elements.
  • the first network storage network element and the second network storage network element may be the same network element, or they may be different network elements.
  • this application takes the first network slice management network element and the second network slice management network element as the same network element, and the first network storage network element and the second network storage network element are the same network element. Instructions.
  • the terminal is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld or vehicle; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons, and satellites) First class).
  • the terminal may be a mobile phone, a tablet, a computer with a wireless transmitting and receiving function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, or an industrial control.
  • Access network equipment is a device that provides wireless communication functions for terminals.
  • the access network equipment includes, but is not limited to, a next-generation base station (gNB) in 5G, an evolved node B (eNB), a radio network controller (RNC), and a node B ( (node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home nodeB, or home nodeB, HNB), baseband unit (baseBand unit) , BBU), transmission point (TRP), transmission point (TRP), transmission point (TP), mobile switching center, etc.
  • gNB next-generation base station
  • eNB evolved node B
  • RNC radio network controller
  • BSC base station controller
  • BTS base transceiver station
  • home base station e.g., home nodeB, or home nodeB, HNB
  • baseband unit baseBand unit
  • BBU transmission point
  • TRP transmission point
  • TRP transmission point
  • TP
  • the session management network element is mainly used for session management in the mobile network, such as session establishment, modification, and release. Specific functions include assigning Internet protocol (IP) addresses to users, and selecting user plane network elements that provide message forwarding functions.
  • IP Internet protocol
  • the session management network element may be a session management function (SMF) network element.
  • SMF session management function
  • future communications such as 6G, the session management network element may still be an SMF network element or have another name. This application does not Be limited.
  • Mobility management network elements are mainly used for mobility management in mobile networks, such as user location updates, user registration networks, and user switching.
  • the mobility management network element may be an access and mobility management function (AMF) network element.
  • AMF access and mobility management function
  • future communications such as 6G communication, the mobility management network element may still be an AMF network element. , Or have other names, this application is not limited.
  • the above functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform).
  • the following uses the mobility management network element as an AMF network element, the session management network element as an SMF network element, and the network storage network element as an NRF network element for illustration.
  • AMF AMF
  • SMF SMF
  • NRF NRF
  • the AMF described later in this application can be replaced with a mobility management network element
  • the SMF can be replaced with a session management network element
  • the NRF can be replaced with a network storage network element.
  • a configuration method provided by the present application is used to configure NRF.
  • the method includes the following steps:
  • Step 301 The network slice management network element sends configuration information to the NRF, and accordingly, the NRF can receive the configuration information.
  • the network slice management network element here may be the network slice management network element shown in FIG. 1, or the first network slice management network element or the second network slice management network element shown in FIG. 2.
  • the configuration information includes information about network slices, system characteristics supported by the network slices, and NF and NF services corresponding to the system characteristics.
  • NF refers to the type of NF, that is, the type of NF that supports the characteristics of the system.
  • NF service refers to a function exposed by a network element supporting a NF type through a service-oriented interface, and this function can be called by network elements of other NF types (which need to be authorized).
  • the NF service is an AMF-related function that can be called by other NF-type network elements (for example, SMF network elements) on a network element that supports AMF (for example, it can be directly called an AMF network element).
  • the network slice information includes one or more single network slice selection assistance information (single network selection selection information, S-NSSAI).
  • System characteristics refer to network services provided by the network to terminals or external applications.
  • one or more system features can be deployed based on the needs of the service.
  • corresponding network elements need to be deployed in the access network and the core network, and the deployed network elements implement network function services related to system characteristics.
  • System characteristics may include, but are not limited to: Internet Protocol (IP) data unit sessions (PDU sessions), non-access layer-based short message services (non-access stratum, SMS overover) One or more combinations of NAS), location service (LCS), etc.
  • IP Internet Protocol
  • PDU sessions non-access layer-based short message services
  • SMS overover One or more combinations of NAS
  • LCS location service
  • the NF corresponding to the system characteristic may include short message service function, (SMSF), unified data management (UDM) and AMF
  • SMSF short message service function
  • UDM unified data management
  • Nsmsf_SMService is the NF service for SMSF
  • Nudm_UECM is the NF service for UDM
  • Namf_Communication is the NF service for AMF
  • the network slice When the network slice supports a certain system feature, multiple network elements of a certain NF type corresponding to the system feature can be deployed.
  • the multiple network elements support the same NF service, and the NF service can be called by other NF type network elements.
  • the interaction and cooperation between network elements achieve corresponding system characteristics.
  • Table 1 shows an example of configuration information.
  • the content included in the configuration information sent by the network slice management network element to the NRF may be an identifier of the system characteristic
  • the NF in the configuration information may be an NF type identifier
  • the NF service in the configuration information may be an identifier or a name of the NF service. The description is unified here, and will not be repeated later.
  • S-NSSAI1 is used to identify network slice 1 and S-NSSAI2 is used to identify network slice 2.
  • Network slice 1 supports system feature 1 and system feature 2.
  • the NFs corresponding to system feature 1 are NF1 and NF2, and the NF services corresponding to system feature 1 are NF service 1 and NF service 2, and NF service 1 is a service in NF1 and NF.
  • Service 2 is a service in NF2
  • NF corresponding to system characteristic 2 is NF3 and NF4
  • NF services corresponding to system characteristic 2 are NF service 3 and NF service 4
  • NF service 3 is a service in NF3, and NF service 4 is NF4.
  • NFs corresponding to system feature 1 are NF1 and NF2
  • NF service 1 is a service in NF1 and NF.
  • Service 2 is a service in NF2
  • NF corresponding to system characteristic 2 is NF3 and NF4
  • NF services corresponding to system characteristic 2 are NF service 3 and NF service 4
  • NF service 3 is a service in NF3
  • NF service 4 is NF
  • Network slice 2 supports system characteristics 3 and system characteristics 4.
  • the NFs corresponding to system characteristic 3 are NF5 and NF6.
  • the NF services corresponding to system characteristic 3 are NF service 5 and NF service 6, and NF service 5 is a service in NF5.
  • NF Service 6 is a service in NF6.
  • the NFs corresponding to system characteristic 4 are NF7, NF8, and NF9.
  • the NF services corresponding to system characteristic 4 are NF service 71, NF service 72, and NF service 8, and NF service 71 and NF service 72 are Services in NF7, NF Service 8 is a service in NF8.
  • Step 302 The NRF stores the configuration information.
  • the NRF stores configuration information locally, or stores the configuration information in an external server or database system that is dedicated to storing data.
  • step 302 the following step 303 may be further included.
  • Step 303 The NRF sends a configuration completion instruction to the network slice management network element. Accordingly, the network slice management network element may receive the configuration completion instruction.
  • the configuration completion indication is used to indicate that the configuration is complete.
  • step 302 the following steps 304 to 306 may be further included.
  • Step 304 The NRF receives a notification message from the first network element, and accordingly, the first network element can receive the notification message.
  • the configuration information of the NRF includes information of one or more network slices, system characteristics supported by the network slices, NF corresponding to the system characteristics, and NF services corresponding to the NF.
  • any system characteristic corresponding to any network slice it is called a first system characteristic.
  • Any NF corresponding to the first system characteristic is called a first NF
  • any of the NF services corresponding to the first NF among the NF services corresponding to the NF is called a first NF service.
  • a network element supporting the first NF is called a first network element.
  • the notification message includes status information of the NF service of the first network element, and the status information of the NF service of the first network element includes the status information of the first NF service.
  • the first NF is NF7 (for example, SMSF)
  • the first NF service is NF service 71 (for example, Nsmsf_SMService) and NF service 72 (for example, Nsmsf_SMSEventExposure)
  • the first network element is a NF7 Network element (for example, a SMSF network element).
  • the status information of the NF service sent by the first network element to the NRF includes the status information of the NF service 71, the NF The status information of the service 72 (where the status information of the NF service 71 and the NF service 72 is referred to as the status information of the first NF service), the status information of the NF service 10, and the status information of the NF service 11.
  • the first NF is NF8 (for example, AMF)
  • the first NF service is NF service 8 (for example, Namf_Communication)
  • the first network element is a network element that supports NF8 (for example, , AMF network element).
  • the NF service in the first network element includes NF service 8 and NF service 12
  • the status information of the NF service sent by the first network element to the NRF includes the status information of NF service 8.
  • the status information of NF service 8 is State information for the first NF service), state information for the NF service 12.
  • the status information of the NF service of the first network element includes the total number of times that the NF service is called by other multiple network elements (that is, more than one) within a preset time period and / or separately called by other single network elements.
  • the number of times further, may include the number of times that the NF service call failed and the corresponding failure reason.
  • the specific failure reasons include, but are not limited to: insufficient resources in the NF, the timer of the NF service expired, and the service caller did not respond.
  • Step 305 The NRF determines the status information of the first system characteristic according to the status information of the first NF service.
  • the NRF may store the status information of the first NF service in the above configuration information, or separately save the status information of the first NF service.
  • the first NF is NF7 (for example, SMSF)
  • the first NF service is NF service 71 (for example, Nsmsf_SMService) and NF service 72 (for example, Nsmsf_SMSEventExposure)
  • the first network element for example, (SMSF network element) is a network element that supports NF7
  • the notification message sent by the first network element includes status information of NF service 71 and status information of NF service 72 (where the status information of NF service 71 and NF service 72 is called the first -Status information of NF service), status information of NF service 10 and status information of NF service 11, after receiving the notification message, the NRF saves the status information of the NF service 71 and the status information of the NF service 72.
  • it can also State information of the NF service 10 and state information of the NF service 11 are stored.
  • the NRF also determines the status information of the system characteristics corresponding to the NF service 71 and the NF service 72 (ie, the system characteristic 4 in Table 1) according to the status information of the NF service 71 and the status information of the NF service 72.
  • the NRF determines the status information of the system characteristic 4 according to the status information of the NF service 71 and the status information of the NF 72, including but not limited to the following two methods: Method one, if the NF service 71 and the NF service 72 both implement the system characteristic 4 Directly related services, the NRF can use the sum of the number of times that NF service 71 and NF service 72 are called as the running times of system characteristic 4, that is, the status information of system characteristic 4; or, it can also use NF service 71 and NF service The number of times 71 is called and the number of times NF service 72 and NF service 72 are called are used as the status information of the system characteristic 4.
  • Method 2 If the NF service 71 is a direct service related to the realization of the system characteristic 4, and the NF service 72 is an auxiliary service to achieve the system characteristic 4, that is, the NF service 71 needs to call the NF service 72 when it is running, then the NRF can transfer the NF service 71 to The number of calls is regarded as the number of times the system characteristic 4 is run, that is, the status information of the system characteristic 4.
  • system characteristic 4 corresponds to multiple NF services
  • the status information of the system characteristic 4 needs to be determined according to the status information of the multiple NF services.
  • system characteristic 4 corresponds to NF7 and NF8
  • NF7 corresponds to NF service 71 and NF service 72
  • NF8 corresponds to NF service 8 (for example, Namf_Communication).
  • NRF can receive network elements that support NF7 (that is, SMSF network element) sends status information of NF service 71 and NF service 72, and receives status information of NF service 8 sent by a network element that supports NF8 (for example, an AMF network element), and determines status information of system characteristic 4.
  • NF service 71 and NF service 72 are both directly related services that implement system feature 4, and NF service 8 is an auxiliary service that implements system feature 4, then the NRF will sum the total number of times NF service 71 and NF service 72 were called.
  • NRF uses the sum of the number of times that NF service 71, NF service 72, and NF service 8 is called as system characteristic 4.
  • the number of running times that is, as the status information of system characteristic 4.
  • Step 306 The NRF sends a response message to the first network element, and accordingly, the first network element can receive the response message.
  • the response message is used to notify the first network element that the notification message has been received.
  • This step 306 is an optional step.
  • the foregoing first network element may be a network element corresponding to any NF in the configuration information.
  • the first network element may be a network element supporting NF1 or a network element supporting NF2.
  • Each first network element actively reports the status information of the NF service of the first network element, and then the NRF determines the status information of the system characteristics according to the status information of the NF service.
  • the status information of the system characteristics in the configuration information can be updated.
  • FIG. 4 As shown in FIG. 4, another configuration method provided for this application.
  • the method includes the following steps:
  • Step 401 The second network element sends a request message to the NRF, and accordingly, the NRF can receive the request message.
  • the request message includes information of a network slice, and the request message is used to request to obtain status information of a system feature supported by the network slice.
  • the network slice information includes one or more S-NSSAIs.
  • the second network element here may be any network element in the network, such as AMF, SMF, access network equipment, and so on.
  • Step 402 The NRF sends the status information of the system features supported by the network slice to the second network element according to the request message. Accordingly, the second network element may receive the status information of the system features supported by the network slice.
  • the NRF stores configuration information.
  • the configuration information includes network slice information, system features supported by the network slice, NF and NF services corresponding to the system feature, and status information of system features supported by the network slice.
  • the second network element can obtain the status information of the system features supported by the network slice from the NRF, and the status information of the system features supported by the network slice includes the status information of the system feature corresponding to the NF service.
  • the request message in the above step 401 further includes a second system characteristic in the system characteristics supported by the network slice
  • the request message is specifically used to request to obtain status information of the second system characteristic
  • the above step 402 In the state information of the network slice sent by the NRF to the second network, the state information of the second system feature supported by the network slice is included. That is, the request message can request to obtain the status information of the specified system characteristic.
  • Implementation method 1 The request message in the above step 401 further includes a specified time period, and the request message is specifically used to request to obtain status information of system characteristics supported by the network slice in the specified time period.
  • the NRF Send the second network element status information of the system characteristics supported by the network slice in the specified time period.
  • the NRF sends the second network element status information of the second system characteristic within a specified period of time, and the second system characteristic of the second system characteristic is sent within the specified period of time.
  • the status information may include status information of the second system characteristic corresponding to the NF service in the specified time period.
  • the status information of the NF service includes the total number of times that the NF service is called by other multiple network elements and / or the number of times that it is called by other single network elements within the specified time period. Further, the number of failed NF service invocations and the corresponding failure reason may also be included.
  • the specific failure reasons include, but are not limited to: insufficient resources in the NF, the timer of the NF service expired, and the service caller does not respond.
  • the request message in the first implementation method may also be referred to as a query message, a network slice status request (network slice status request) message, and the like.
  • the request message in the above step 401 further includes a subscription period.
  • the request message is specifically used to request to periodically obtain status information of system features supported by the network slice.
  • the NRF according to the subscription period in the request message , Periodically sending the status information of the system characteristics supported by the network slice to the second network element, and the status information of the system characteristics supported by the network slice includes the status information of the system characteristics corresponding to the NF service in the subscription period.
  • the NRF periodically sends the status information of the second system characteristic to the second network element, and the status information of the second system characteristic sent may include within the subscription period.
  • the second system characteristic corresponds to the status information of the NF service.
  • the status information of the NF service includes the total number of times that the NF service is called by other multiple network elements and / or the number of times that it is called by other single network elements during the subscription period. Further, the number of failed NF service invocations and the corresponding failure reason may also be included.
  • the specific failure reasons include, but are not limited to: insufficient resources in the NF, the timer of the NF service expired, and the service caller has not responded.
  • the main difference between the first implementation method and the second implementation method is that in the first implementation method, the NRF sends status information of system characteristics supported by the network slice to the second network element based on the request of the second network element.
  • the NRF is The system property status subscription request of the second network element includes the time period for reporting the system property supported by the network slice and / or the number of reports of the system property status in the system property status subscription request, so that the NRF can periodically report to the second network
  • the meta sends status information about the system features supported by the network slice.
  • the second network element can obtain the status information of the system characteristics supported by the network slice from the NRF, so that the running status of the system characteristics can be accurately known.
  • first network element and the second network element in this application may be the same network element or different network elements.
  • the first network element and the second network element are only used to distinguish the names. In practical applications, the first network element and the second network element may have specific names, which is not limited in this application.
  • each network element includes a hardware structure and / or a software module corresponding to each function.
  • the present invention can be implemented in the form of hardware or a combination of hardware and computer software by combining the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.
  • FIG. 5 shows a possible exemplary block diagram of a device involved in the embodiment of the present invention, and the device 500 may exist in the form of software.
  • the apparatus 500 may include a processing unit 502 and a communication unit 503.
  • the communication unit 503 may include a receiving unit and a sending unit.
  • the processing unit 502 is configured to control and manage the operations of the device 500.
  • the communication unit 503 is configured to support communication between the device 500 and other network entities.
  • the device 500 may further include a storage unit 501 for storing program code and data of the device 500.
  • the processing unit 502 may be a processor or a controller.
  • the processing unit 502 may be a general-purpose central processing unit (CPU), a general-purpose processor, digital signal processing (DSP), or an application-specific integrated circuit. circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure.
  • the processor may also be a combination that implements a computing function, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 503 may be a communication interface, a transceiver, or a transceiver circuit.
  • the communication interface is collectively referred to. In a specific implementation, the communication interface may include multiple interfaces.
  • the storage unit 501 may be a memory.
  • the device 500 may be a network slice management network element involved in the present application, or may also be a chip in the network slice management network element.
  • the processing unit 502 may support the apparatus 500 to perform the actions of the network slice management network element in the method examples described above.
  • the communication unit 503 may support communication between the device 500 and a network storage network element.
  • the communication unit 503 is configured to support the device 500 to perform steps 301 and 303 in FIG. 3.
  • the sending unit is configured to send configuration information to a network storage network element, where the configuration information includes network slice information, system characteristics supported by the network slice, and the A network function NF corresponding to the system characteristic and an NF service corresponding to the NF; and a receiving unit, configured to receive a configuration completion instruction from the network storage network element.
  • the device 500 may also be a network storage network element involved in this application, or may also be a chip in the network storage network element.
  • the processing unit 502 may support the apparatus 500 to perform the actions of the network storage network element in the method examples above.
  • the processing unit 502 is used to support the device 500 to perform steps 302 and 305 in FIG. 3, and / or other processes for the techniques described herein.
  • the communication unit 503 is configured to support communication between the device 500 and the network slice management network element, the first network element, and the second network element.
  • the communication unit is configured to support the device 500 to perform steps 301, 303, and 304 in FIG. 3 and steps 401 and 402 in FIG. 4.
  • the receiving unit is configured to receive configuration information from a network slice management network element, where the configuration information includes information about the network slice and the network.
  • the system characteristic includes a first system characteristic, an NF corresponding to the first system characteristic includes a first NF, and an NF service corresponding to the NF includes a first NF corresponding to the first NF.
  • the receiving unit is further configured to receive a notification message from a first network element, where the first network element is a network element that supports the first NF, and the notification message includes the information of the first network element
  • the state information of the NF service, the state information of the NF service of the first network element includes the state information of the first NF service; and the processing unit is further configured to determine the location information based on the state information of the first NF service.
  • the state information of the first system characteristic is described.
  • the status information of the NF service of the first network element includes a total number of times that the NF service is called by other multiple network elements within a preset time period and / or is separately determined by other single network elements. The number of calls.
  • the receiving unit is configured to receive a request message from a second network element, where the request message includes information about a network slice, and the request The message is used to request to obtain the status information of the system characteristics supported by the network slice; the sending unit is configured to send the status information of the system characteristics supported by the network slice to the second network element according to the request message.
  • the request message further includes a specified time period, and the request message is specifically used to request to obtain status information of a system feature supported by the network slice within the specified time period
  • the sending unit is specifically configured to send, to the second network element, status information of system characteristics supported by the network slice within the specified time period.
  • the status information of system characteristics supported by the network slice in the specified time period includes that the NF service corresponding to the system characteristic is used by other multiple network elements in the specified time period.
  • the request message further includes a subscription period, and the request message is specifically used to request to periodically obtain status information of a system feature supported by the network slice; and the sending unit, specifically, And configured to periodically send status information of system characteristics supported by the network slice to the second network element according to the subscription period in the request message.
  • the status information of the system characteristics supported by the network slice includes the total number of times that the NF service corresponding to the system characteristics is called by other multiple network elements in the subscription cycle and / or is The number of times each single NE is called.
  • the device 500 may be a second network element involved in this application, or may also be a chip in the second network element.
  • the processing unit 502 may support the apparatus 500 to perform the actions of the second network element in the foregoing method examples.
  • the communication unit 503 may support communication between the device 500 and a network storage network element.
  • the communication unit 503 is configured to support the device 500 to perform steps 401 and 402 in FIG. 4.
  • the sending unit is configured to send a request message to a network storage network element, where the request message includes information about a network slice, and the request message is used to request to obtain the network.
  • Status information of system characteristics supported by the slice a receiving unit, configured to receive status information of system characteristics supported by the network slice from the network storage network element.
  • the request message further includes a specified time period, and the request message is specifically used to request to obtain status information of a system feature supported by the network slice within the specified time period, Then, the receiving unit is specifically configured to receive status information of a system characteristic supported by the network slice in the specified time period from the network storage network element.
  • the status information of system characteristics supported by the network slice in the specified time period includes that the NF service corresponding to the system characteristic is used by other multiple network elements in the specified time period.
  • the request message further includes a subscription period
  • the request message is specifically used to request to periodically obtain status information of a system feature supported by the network slice
  • the receiving unit specifically uses And receiving status information of system characteristics supported by the network slice that the network storage network element periodically sends according to the subscription period.
  • the status information of the system characteristics supported by the network slice includes the total number of times that the NF service corresponding to the system characteristics is called by other multiple network elements in the subscription cycle and / or is The number of times each single NE is called.
  • the device may be the foregoing network slice management network element, or a network storage network element, or a second network element.
  • the device 600 includes: a processor 602, a communication interface 603, and a memory 601.
  • the apparatus 600 may further include a bus 604.
  • the communication interface 603, the processor 602, and the memory 601 can be connected to each other through a communication line 604.
  • the communication line 604 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture. , Referred to as EISA) bus and so on.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the communication line 604 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 6, but it does not mean that there is only one bus or one type of bus.
  • the processor 602 may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of the solution of the present application.
  • the communication interface 603 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), Wired access network, etc.
  • RAN radio access network
  • WLAN wireless local area networks
  • Wired access network etc.
  • the memory 601 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM), or other types that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (electrically server-programmable read-only memory (EEPROM)), compact disc (read-only memory (CD-ROM) or other optical disk storage, Optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can Any other media accessed by the computer, but not limited to this.
  • the memory may exist independently, and is connected to the processor through the communication line 604. The memory can also be integrated with the processor.
  • the memory 601 is configured to store computer execution instructions for executing the scheme of the present application, and the processor 602 controls execution.
  • the processor 602 is configured to execute computer execution instructions stored in the memory 601, so as to implement the configuration method provided in the foregoing embodiment of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, a computer, a server, or a data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD)), and the like.
  • Various illustrative logic units and circuits described in the embodiments of the present application may be implemented by a general-purpose processor, a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices. Discrete gate or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor. Alternatively, the general-purpose processor may also be any conventional processor, controller, microcontroller, or state machine.
  • the processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration. achieve.
  • a software unit may be stored in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium in the art.
  • the storage medium may be connected to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may be provided in an ASIC, and the ASIC may be provided in a terminal. Alternatively, the processor and the storage medium may also be provided in different components in the terminal.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

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

本申请提供一种配置方法及装置。该方法包括：网络存储网元接收来自网络切片管理网元的配置信息，配置信息包括网络切片的信息、网络切片支持的系统特性、系统特性对应的网络功能NF和与NF对应的NF服务；网络存储网元存储配置信息。基于该方案，可实现为网络存储网元进行网络切片的相关信息的配置。

Description

一种配置方法及装置
本申请要求在2018年6月26日提交中华人民共和国知识产权局、申请号为201810674390.9、发明名称为“一种配置方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种配置方法及装置。
背景技术
目前的网络构架中，基于虚拟化等技术在核心网络的一个共同的网络基础设施上切分出多个网络切片(network slice)，网络切片用于实现某个或某些业务需要的网络服务。为了表示某个类型的网络切片，网络切片的信息中可以包括对应的网络切片的类型，网络切片的类型例如包括：增强移动宽带(enhanced mobile broadband，eMBB)类型的网络切片，超低时延(ultra low latency)类型的网络切片等。在下一代通信网络中，针对不同类型的网络切片将分别支持不同的系统特性(system feature)。如何对系统特性进行配置，目前还没有得到解决。
发明内容
本申请提供一种配置方法及装置，用以实现对系统特性进行配置。
第一方面，本申请提供一种配置方法。该方法包括：网络存储网元接收来自网络切片管理网元的配置信息，配置信息包括网络切片的信息、网络切片支持的系统特性、系统特性对应的网络功能NF和与NF对应的NF服务；网络存储网元存储配置信息。基于该方案，可实现为网络存储网元进行网络切片的相关信息的配置。
在一种可能的实现方式中，系统特性包括第一系统特性,第一系统特性对应的NF包括第一NF,与NF对应的NF服务包括与第一NF对应的第一NF服务,方法还包括：网络存储网元接收来自第一网元的通知消息，第一网元为支持第一NF的网元,通知消息包括第一网元的NF服务的状态信息，第一网元的NF服务的状态信息包括第一NF服务的状态信息；网络存储网元根据第一NF服务的状态信息，确定第一系统特性的状态信息。基于该方案，可以实现更新配置信息中的系统特性的状态信息。
在一种可能的实现方式中，第一网元的NF服务的状态信息包括NF服务在预设时长内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
第二方面，本申请提供一种配置方法。该方法包括：网络切片管理网元向网络存储网元发送配置信息，配置信息包括网络切片的信息、网络切片支持的系统特性、系统特性对应的网络功能NF和与NF对应的NF服务；网络切片管理网元接收来自网络存储网元的配置完成指示。基于该方案，可实现为网络存储网元进行网络切片的相关信息的配置。
第三方面，本申请提供一种配置方法。该方法包括：网络存储网元接收来自第二网元的请求消息，请求消息包括网络切片的信息，请求消息用于请求获取网络切片支持的系统特性的状态信息；网络存储网元根据请求消息，向第二网元发送网络切片支持的系统特性的状态信息。基于该方案，第二网元可以从网络存储网元中获取到网络切片支持的系统特性的状态信息，该网络切片支持的系统特性的状态信息包括系统特性对应NF服务的状态信息。
在一种可能的实现方式中，请求消息还包括指定的时间段，则请求消息具体用于请求获取在指定的时间段内的网络切片支持的系统特性的状态信息；则网络存储网元根据请求消息，向第二网元发送网络切片支持的系统特性的状态信息，包括：网络存储网元向第二网元发送在指定时间段内的网络切片支持的系统特性的状态信息。
在一种可能的实现方式中，指定时间段内的网络切片支持的系统特性的状态信息包括系统特性对应的NF服务在指定的时间段内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
在一种可能的实现方式中，请求消息还包括订阅周期，则请求消息具体用于请求周期性的获取网络切片支持的系统特性的状态信息；则网络存储网元根据请求消息，向第二网元发送网络切片支持的系统特性的状态信息，包括：网络存储网元根据请求消息中的订阅周期，周期性地向第二网元发送网络切片支持的系统特性的状态信息。
在一种可能的实现方式中，网络切片支持的系统特性的状态信息包括系统特性对应的NF服务在订阅周期内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
第四方面，本申请提供一种配置方法。该方法包括：第二网元向网络存储网元发送请求消息，请求消息包括网络切片的信息，请求消息用于请求获取网络切片支持的系统特性的状态信息；第二网元接收来自网络存储网元的网络切片支持的系统特性的状态信息。基于该方案，第二网元可以从网络存储网元中获取到网络切片支持的系统特性的状态信息，该网络切片支持的系统特性的状态信息包括系统特性对应NF服务的状态信息。
在一种可能的实现方式中，请求消息还包括指定的时间段，请求消息具体用于请求获取在指定的时间段内的网络切片支持的系统特性的状态信息，则第二网元接收来自网络存储网元的网络切片支持的系统特性的状态信息，包括：第二网元接收来自网络存储网元的在指定时间段内的网络切片支持的系统特性的状态信息。
在一种可能的实现方式中，指定时间段内的网络切片支持的系统特性的状态信息包括系统特性对应的NF服务在指定的时间段内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
在一种可能的实现方式中，请求消息还包括订阅周期，请求消息具体用于请求周期性的获取网络切片支持的系统特性的状态信息，第二网元接收来自网络存储网元的网络切片支持的系统特性的状态信息，包括：第二网元接收网络存储网元根据订阅周期进行周期性地发送的网络切片支持的系统特性的状态信息。
在一种可能的实现方式中，网络切片支持的系统特性的状态信息包括系统特性对应的NF服务在订阅周期内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
在一种可能的实现方式中，上述第一至第四方面的任一实施例中的请求消息还包括网络切片支持的系统特性中的第二系统特性，网络切片支持的系统特性的状态信息具体包括第二系统特性对应的NF服务的状态信息。
第五方面，本申请提供一种装置，该装置可以是网络存储网元、网络切片管理网元、第二网元，也可以是芯片。该装置具有实现上述第一方面、或者第二方面、或者第三方面、或者第四方面中任意一个方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第六方面，提供了一种装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执 行如上述第一方面或第一方面中任一所述的配置方法、或者以使该装置执行如上述第二方面或第二方面中任一所述配置方法、或者以使该装置执行如上述第三方面或第三方面中任一所述的配置方法、或者以使该装置执行如上述第四方面或第四方面中任一所述的配置方法。
第七方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第八方面，本申请还提供一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第九方面，本申请还提供一种系统，该系统包括上述第一方面或第一方面的任一实施例中的网络存储网元，和，上述第二方面的网络切片管理网元。
第十方面，本申请还提供一种系统，该系统包括上述第三方面或第三方面的任一实施例中的网络存储网元，和，上述第四方面或第四方面的任一实施例中的第二网元。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为本申请提供的一种可能的网络架构示意图；
图2为本申请提供的又一种可能的网络架构示意图；
图3为本申请提供的一种配置方法流程图；
图4为本申请提供的又一种配置方法流程图；
图5为本申请提供的一种装置示意图；
图6为本申请提供的又一种装置示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图1所示，为本申请提供的一种可能的网络架构示意图。该网络架构包括网络切片管理网元和网络存储网元。
本申请中，网络切片管理网元可用于对网络存储网元进行配置，包括配置网络切片的信息、网络切片支持的系统特性、系统特性对应的网络功能(network function，NF)和NF服务。作为一种实现方式，该网络切片管理网元可以是操作管理与维护(Operation Administration and Maintenance，OAM)系统。
网络存储网元，例如可以是第五代(the 5th generation,5G)通信系统中的网络存储功能(network repository function，NRF)网元。网络存储网元的功能主要包括网络功能和服务的注册、去注册和发现等，网络存储网元可以保存部署的网络功能的描述信息，比如包括网络功能的标识和地址、支持的服务信息、网络切片标识等。在未来通信如第六代(the 6th generation,6G)中，网络存储网元可以称为NRF网元，也还可 以有其它名称，本申请不做限定。
如图2所示，为本申请提供的又一种可能的网络架构示意图。该网络架构中包括接入网设备、移动性管理网元、会话管理网元、第一网络切片管理网元、第二网络切片管理网元、第一网络存储网元和第二网络存储网元。
第一网络切片管理网元用于对核心网侧的第一网络存储网元进行配置，第二网络切片管理网元用于对接入网的第二网络存储网元进行配置。在具体实现中，第一网络切片管理网元和第二网络切片管理网元可以是同一个网元，也可以是不同的网元。第一网络存储网元和第二网络存储网元可以是同一个网元，也可以是不同的网元。为方便说明，本申请以第一网络切片管理网元和第二网络切片管理网元是同一个网元，且第一网络存储网元和第二网络存储网元是同一个网元为例进行说明。
终端是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
接入网设备，是一种为终端提供无线通信功能的设备。接入网设备例如包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
会话管理网元，主要用于移动网络中的会话管理，如会话建立、修改、释放。具体功能如为用户分配互联网协议(internet protocol，IP)地址、选择提供报文转发功能的用户面网元等。在5G中，会话管理网元可以是会话管理功能(session management function，SMF)网元，在未来通信如6G中，会话管理网元仍可以是SMF网元，或有其它的名称，本申请不做限定。
移动性管理网元，主要用于移动网络中的移动性管理，如用户位置更新、用户注册网络、用户切换等。在5G通信中，移动性管理网元可以是接入与移动性管理功能(access and mobility management function，AMF)网元，在未来通信如6G通信中，移动性管理网元仍可以是AMF网元，或者有其它名称，本申请对此不作限定。
可以理解的是,上述功能既可以是硬件设备中的网络元件,也可以是在专用硬件上运行软件功能，或者是平台(例如,云平台)上实例化的虚拟化功能。
为方便说明，本申请后续，以移动性管理网元为AMF网元，会话管理网元为SMF网元，网络存储网元为NRF网元为例进行说明。进一步地，将AMF网元简称为AMF，SMF网元简称为SMF，NRF网元简称为NRF。即本申请后续所描述的AMF均可替换为移动性管理网元，SMF均可替换为会话管理网元，NRF均可替换为网络存储网元。
下面结合图1和图2，对本申请提供的配置方法进行说明。
如图3所示，为本申请提供的一种配置方法，该方法用于对NRF进行配置。该方法包括以下步骤：
步骤301，网络切片管理网元向NRF发送配置信息，相应地，NRF可以接收到该配置信息。
这里的网络切片管理网元可以是图1所示的网络切片管理网元，或者是图2所示的第一网络切片管理网元或第二网络切片管理网元。
该配置信息包括网络切片的信息、该网络切片支持的系统特性、该系统特性对应的NF和NF服务(NF service)。
其中，NF指的是NF类型(type)，即支持该系统特性的NF的类型。
NF服务指的是:由支持NF类型的网元通过服务化接口公开的功能，该功能可以被其他NF类型(需要被授权)的网元调用。例如NF为AMF时，NF服务为支持AMF的网元(例如，可直接称为AMF网元)上可以被其他NF类型的网元(例如，SMF网元)调用的AMF相关的功能。
网络切片的信息包括一个或一个以上单个网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)。
系统特性指的是网络提供给终端或外部应用的网络服务。在一个网络切片中，根据服务的需求可以部署一个或多个系统特性。对应的，为了支持和实现该一个或多个服务，在接入网和核心网中需要部署相应的网元，部署的网元实现和系统特性有关的网络功能服务。系统特性例如可以包括但不限于：因特网协议(internet protocol，IP)数据单元会话(protocol data unit session，PDU session)、基于非接入层的短消息服务(short messaging service over non access stratum，SMS over NAS)、定位服务(location service，LCS)等中的一个或者多个组合。
例如，当系统特性为SMS over NAS(例如可以用系统特性短消息服务(system feature short message service，SF_SMS)标识)时，则该系统特性对应的NF可以包括短消息服务功能(short message service function，SMSF)、统一数据管理(unified data management，UDM)和AMF，该NF对应的NF服务可以包括Nsmsf_SMService
(Nsmsf_SMService为SMSF的NF服务)、Nudm_UECM(Nudm_UECM为UDM的NF服务)、Namf_Communication(Namf_Communication为AMF的NF服务)等。
在网络切片支持某系统特性时，该系统特性对应的某一NF类型的网元可以部署多个，该多个网元支持相同的NF服务，该NF服务可以被其它NF类型的网元调用，从而网元之间交互和配合实现对应的系统特性。
下面结合具体示例进行说明。如表1所示，为配置信息示例。
表1
Figure PCTCN2019092814-appb-000001
Figure PCTCN2019092814-appb-000002
如表1所示，为网络切片管理网元发送给NRF的配置信息所包括的内容。在具体实现中，配置信息中的系统特性可以是系统特性的标识，配置信息中的NF可以是NF类型的标识，配置信息中的NF服务可以是NF服务的标识或名称。这里做统一说明，后续不再赘述。
其中，S-NSSAI1用于标识网络切片1，S-NSSAI2用于标识网络切片2。
网络切片1支持系统特性1和系统特性2，系统特性1对应的NF为NF1和NF2，系统特性1对应的NF服务为NF服务1和NF服务2，且NF服务1是NF1中的服务，NF服务2是NF2中的服务，系统特性2对应的NF为NF3和NF4，系统特性2对应的NF服务为NF服务3和NF服务4，且NF服务3是NF3中的服务，NF服务4是NF4中的服务。
网络切片2支持系统特性3和系统特性4，系统特性3对应的NF为NF5和NF6，系统特性3对应的NF服务为NF服务5和NF服务6，且NF服务5是NF5中的服务，NF服务6是NF6中的服务，系统特性4对应的NF为NF7、NF8和NF9，系统特性4对应的NF服务为NF服务71、NF服务72和NF服务8，且NF服务71和NF服务72是NF7中的服务，NF服务8是NF8中的服务。
步骤302，NRF存储该配置信息。
例如，NRF将配置信息存储于本地，或者是将配置信息存储于外部专门用于存储数据的服务器或者数据库系统中。
通过上述方法，可实现为NRF进行网络切片的相关信息的配置。
进一步的，在步骤302之后，还可以包括以下步骤303。
步骤303，NRF向网络切片管理网元发送配置完成指示，相应地，网络切片管理网元可以接收到该配置完成指示。该配置完成指示用于指示配置完成。
进一步的，在上述步骤302或步骤303之后，还可以包括以下步骤304-步骤306。
步骤304，NRF接收来自第一网元的通知消息，相应地，第一网元可以接收到该通知消息。
NRF的配置信息包括一个或多个网络切片的信息、网络切片支持的系统特性、系统特性对应的NF和与NF对应的NF服务。
针对任一网络切片对应的任一系统特性，称为第一系统特性。该第一系统特性对应的任一NF，称为第一NF，上述与NF对应的NF服务中的与第一NF对应的任一NF服务，称为第一NF服务。支持上述第一NF的网元称为第一网元。
该通知消息包括第一网元的NF服务的状态信息，第一网元的NF服务的状态信息包括第一NF服务的状态信息。
以表1为例，若第一NF为NF7(例如,SMSF)，则第一NF服务为NF服务71(例如,Nsmsf_SMService)和NF服务72(例如，Nsmsf_SMSEventExposure)，第一网元为支持NF7的网元(例如,SMSF网元)。比如，第一网元中的NF服务包括NF服务71、NF服务72、NF服务10和NF服务11，则第一网元向NRF发送的NF服务的状态信息包 括NF服务71的状态信息、NF服务72的状态信息(其中，NF服务71和NF服务72的状态信息称为第一NF服务的状态信息)、NF服务10的状态信息和NF服务11的状态信息。
以表1为例，在又一示例中，若第一NF为NF8(例如，AMF)，则第一NF服务为NF服务8(例如Namf_Communication),第一网元为支持NF8的网元(例如,AMF网元)。比如，第一网元中的NF服务包括NF服务8、NF服务12，则第一网元向NRF发送的NF服务的状态信息包括NF服务8的状态信息(其中，NF服务8的状态信息称为第一NF服务的状态信息)、NF服务12的状态信息。
作为一种实现方式，第一网元的NF服务的状态信息包括NF服务在预设时长内被其他多个网元(即一个以上)调用的总次数和/或被其他单个网元分别调用的次数，进一步的，还可以包括NF服务调用失败的次数和对应的失败原因，具体的失败原因包括不限于：NF内的资源不足，NF服务的定时器超时，服务调用方没有回复。
步骤305，NRF根据第一NF服务的状态信息，确定第一系统特性的状态信息。
NRF接收到第一NF服务的状态信息后，可以将第一NF服务的状态信息存储于上述配置信息中，或单独保存所述第一NF的状态信息。
比如，以表1为例，若第一NF为NF7(例如，SMSF)，第一NF服务为NF服务71(例如,Nsmsf_SMService)和NF服务72(例如，Nsmsf_SMSEventExposure)，第一网元(例如,SMSF网元)为支持NF7的网元，则第一网元发送的通知消息包括NF服务71的状态信息、NF服务72的状态信息(其中，NF服务71和NF服务72的状态信息称为第一NF服务的状态信息)、NF服务10的状态信息和NF服务11的状态信息，NRF接收到通知消息后，保存NF服务71的状态信息和NF服务72的状态信息，可选的，还可以保存NF服务10的状态信息和NF服务11的状态信息。
进一步的，NRF还根据NF服务71的状态信息、NF服务72的状态信息，确定NF服务71和NF服务72对应的系统特性(即表1中的系统特性4)的状态信息。具体地，NRF根据NF服务71的状态信息、NF72的状态信息确定系统特性4的状态信息，包括但不限于以下两种方法：方法一，若NF服务71和NF服务72均为实现系统特性4的直接相关服务，则NRF可以将NF服务71、NF服务72的被调用次数的总和作为系统特性4的运行次数，即作为系统特性4的状态信息；或者，也可以将NF服务71及NF服务71被调用的次数，以及NF服务72及NF服务72被调用的次数，作为系统特性4的状态信息。方法二，若NF服务71为实现系统特性4的直接相关服务，NF服务72为实现系统特性4的辅助服务，即NF服务71在运行时需要调用NF服务72，则NRF可以将NF服务71被调用次数作为系统特性4的运行次数，即作为系统特性4的状态信息。
当系统特性4对应多个NF服务时，则需要根据该多个NF服务的状态信息，确定该系统特性4的状态信息。例如，以表1为例，系统特性4对应NF7和NF8，NF7对应NF服务71和NF服务72，NF8对应NF服务8(例如，Namf_Communication)，则NRF可以在接收到支持NF7的网元(即SMSF网元)发送的NF服务71和NF服务72的状态信息，以及接收到支持NF8的网元(例如,AMF网元)发送的NF服务8的状态信息后，确定系统特性4的状态信息。例如，若NF服务71和NF服务72均为实现系统特性4的直接相关服务，而NF服务8为实现系统特性4的辅助服务，则NRF 将NF服务71、NF服务72的被调用次数的总和作为系统特性4的运行次数，即作为系统特性4的状态信息。再比如，若NF服务71、NF服务72和NF服务8均为实现系统特性4的直接相关服务，则NRF将NF服务71、NF服务72和NF服务8的被调用次数的总和作为系统特性4的运行次数，即作为系统特性4的状态信息。
步骤306，NRF向第一网元发送响应消息，相应地，第一网元可以接收到该响应消息。该响应消息用于通知第一网元：已经接收到上述通知消息。
该步骤306为可选步骤。
需要说明的是，上述第一网元可以是配置信息中的任一NF对应的网元，比如，以表1为例，则该第一网元可以是支持NF1的网元、或是支持NF2的网元等等。通过每个第一网元主动上报第一网元的NF服务的状态信息，然后由NRF根据NF服务的状态信息，确定系统特性的状态信息。
通过上述步骤304-步骤305，或通过上述步骤304-步骤306，可以实现更新配置信息中的系统特性的状态信息。
如图4所示，为本申请提供的又一种配置方法。该方法包括以下步骤：
步骤401，第二网元向NRF发送请求消息，相应地，NRF可以接收到该请求消息。该请求消息包括网络切片的信息，该请求消息用于请求获取该网络切片支持的系统特性的状态信息。
网络切片的信息包括一个或一个以上S-NSSAI。
这里的第二网元可以是网络中的任一网元，如AMF、SMF、接入网设备等等。
步骤402，NRF根据请求消息，向第二网元发送网络切片支持的系统特性的状态信息，相应地，第二网元可以接收到该网络切片支持的系统特性的状态信息。
NRF中存储有配置信息，该配置信息包括网络切片的信息、该网络切片支持的系统特性、该系统特性对应的NF和NF服务，以及还包括网络切片支持的系统特性的状态信息。其中，NRF中的配置信息的配置方法以及配置信息中的系统特性的状态信息的更新方法可参考图3所示的实施例的相关描述，这里不再赘述。
通过上述方法，第二网元可以从NRF中获取到网络切片支持的系统特性的状态信息，该网络切片支持的系统特性的状态信息包括系统特性对应NF服务的状态信息。
作为一种实现方式，若上述步骤401的请求消息还包括网络切片支持的系统特性中的第二系统特性，则该请求消息具体用于请求获取该第二系统特性的状态信息，因此上述步骤402中，NRF向第二网络发送的网络切片的状态信息中包括该网络切片支持的第二系统特性的状态信息。即请求消息可以请求获取指定的系统特性的状态信息。
作为示例，下面介绍图4所示的实施例的两种具体实现方法。
实现方法一，上述步骤401的请求消息还包括指定的时间段，该请求消息具体用于请求获取在该指定的时间段内的网络切片支持的系统特性的状态信息，则上述步骤402中，NRF向第二网元发送在指定时间段内的网络切片支持的系统特性的状态信息。
进一步地，若该请求消息还包括第二系统特性，则NRF向第二网元发送在指定时间段内的第二系统特性的状态信息，且发送的该指定时间段内的第二系统特性的状态信息可以包括该指定时间段内的第二系统特性对应NF服务的状态信息。其中，NF服务的状态信息包括NF服务在该指定的时间段内被其他多个网元调用的总次数和/或被 其他单个网元分别调用的次数。进一步的，还可以包括NF服务调用失败的次数和对应的失败原因，具体的失败原因包括不限于：NF内的资源不足，NF服务的定时器超时，服务调用方没有回复。
需要说明的是，在具体实现中，该实现方法一中的请求消息还可以称为查询消息、网络切片状态请求(network slice status request)消息等。
实现方法二，上述步骤401的请求消息还包括订阅周期，该请求消息具体用于请求周期性的获取网络切片支持的系统特性的状态信息，则上述步骤402中，NRF根据请求消息中的订阅周期，周期性地向第二网元发送网络切片支持的系统特性的状态信息，且该网络切片支持的系统特性的状态信息包括该订阅周期内的系统特性对应NF服务的状态信息。
进一步地，若该请求消息还包括第二系统特性，则NRF周期性地向第二网元发送第二系统特性的状态信息，且发送的该第二系统特性的状态信息可以包括该订阅周期内的该第二系统特性对应NF服务的状态信息。其中，NF服务的状态信息包括NF服务在该订阅周期内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。进一步的，还可以包括NF服务调用失败的次数和对应的失败原因，具体的失败原因包括不限于：NF内的资源不足，NF服务的定时器超时，服务调用方没有回复。
上述实现方法一和实现方法二的主要区别在于：实现方法一中，NRF基于第二网元的请求向第二网元发送网络切片支持的系统特性的状态信息，实现方法二中，NRF是基于第二网元的系统特性状态订阅请求，在该系统特性状态订阅请求中包括报告网络切片支持的系统特性的时间周期和/或系统特性状态的报告次数，从而NRF可以周期性地向第二网元发送网络切片支持的系统特性的状态信息。
通过上述方法，第二网元可以从NRF获取网络切片支持的系统特性的状态信息，从而可以准确的获知系统特性的运行状态。
需要说明的是，本申请中的第一网元和第二网元可以是相同的网元，也可以是不同的网元，第一网元和第二网元仅仅是作为名称上的区分，在实际应用中，第一网元和第二网元可以有具体的名称，对此，本申请不做限定。
可以理解的是，上述实现各网元为了实现上述功能，其包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
在采用集成的单元的情况下，图5示出了本发明实施例中所涉及的装置的可能的示例性框图，该装置500可以以软件的形式存在。装置500可以包括：处理单元502和通信单元503。作为一种实现方式，该通信单元503可以包括接收单元和发送单元。处理单元502用于对装置500的动作进行控制管理。通信单元503用于支持装置500与其他网络实体的通信。装置500还可以包括存储单元501，用于存储装置500的程序代码和数据。
其中，处理单元502可以是处理器或控制器，例如可以是通用中央处理器(central  processing unit，CPU)，通用处理器，数字信号处理(digital signal processing，DSP)，专用集成电路(application specific integrated circuits，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包括一个或多个微处理器组合，DSP和微处理器的组合等等。通信单元503可以是通信接口、收发器或收发电路等，其中，该通信接口是统称，在具体实现中，该通信接口可以包括多个接口。存储单元501可以是存储器。
该装置500可以是本申请所涉及的网络切片管理网元，或者还可以为网络切片管理网元中的芯片。处理单元502可以支持装置500执行上文中各方法示例中网络切片管理网元的动作。通信单元503可以支持装置500与网络存储网元之间的通信，例如，通信单元503用于支持装置500执行图3中的步骤301和步骤303。
具体地，当通信单元503包括发送单元和接收单元时，发送单元，用于向网络存储网元发送配置信息，所述配置信息包括网络切片的信息、所述网络切片支持的系统特性、所述系统特性对应的网络功能NF和与NF对应的NF服务；接收单元，用于接收来自所述网络存储网元的配置完成指示。
该装置500还可以是本申请所涉及的网络存储网元，或者还可以为网络存储网元中的芯片。处理单元502可以支持装置500执行上文中各方法示例中网络存储网元的动作。例如，处理单元502用于支持装置500执行图3中的步骤302和步骤305，和/或用于本文所描述的技术的其它过程。通信单元503用于支持装置500与网络切片管理网元、第一网元、第二网元之间的通信。例如，通信单元用于支持装置500执行图3中的步骤301、步骤303和步骤304，图4中的步骤401和步骤402。
具体地，当通信单元503包括发送单元和接收单元时，在一个实施例中，接收单元，用于接收来自网络切片管理网元的配置信息，所述配置信息包括网络切片的信息、所述网络切片支持的系统特性、所述系统特性对应的网络功能NF和与NF对应的NF服务；处理单元，用于将所述配置信息存储于存储单元。
在一种可能的实现方式中，所述系统特性包括第一系统特性,所述第一系统特性对应的NF包括第一NF,与NF对应的NF服务包括与所述第一NF对应的第一NF服务,所述接收单元，还用于接收来自第一网元的通知消息，所述第一网元为支持所述第一NF的网元,所述通知消息包括所述第一网元的NF服务的状态信息，所述第一网元的NF服务的状态信息包括所述第一NF服务的状态信息；所述处理单元，还用于根据所述第一NF服务的状态信息，确定所述第一系统特性的状态信息。
在一种可能的实现方式中，所述第一网元的NF服务的状态信息包括所述NF服务在预设时长内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
具体地，当通信单元503包括发送单元和接收单元时，在又一个实施例中，接收单元，用于接收来自第二网元的请求消息，所述请求消息包括网络切片的信息，所述请求消息用于请求获取所述网络切片支持的系统特性的状态信息；发送单元，用于根据所述请求消息，向所述第二网元发送所述网络切片支持的系统特性的状态信息。
在一种可能的实现方式中，所述请求消息还包括指定的时间段，则所述请求消息具体用于请求获取在所述指定的时间段内的所述网络切片支持的系统特性的状态信息； 则所述发送单元，具体用于向所述第二网元发送在所述指定时间段内的所述网络切片支持的系统特性的状态信息。
在一种可能的实现方式中，所述指定时间段内的所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述指定的时间段内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
在一种可能的实现方式中，所述请求消息还包括订阅周期，则所述请求消息具体用于请求周期性的获取所述网络切片支持的系统特性的状态信息；则所述发送单元，具体用于根据所述请求消息中的所述订阅周期，周期性地向所述第二网元发送所述网络切片支持的系统特性的状态信息。
在一种可能的实现方式中，所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述订阅周期内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
该装置500可以是本申请所涉及的第二网元，或者还可以为第二网元中的芯片。处理单元502可以支持装置500执行上文中各方法示例中第二网元的动作。通信单元503可以支持装置500与网络存储网元之间的通信，例如，通信单元503用于支持装置500执行图4中的步骤401和步骤402。
具体地，当通信单元503包括发送单元和接收单元时，发送单元，用于向网络存储网元发送请求消息，所述请求消息包括网络切片的信息，所述请求消息用于请求获取所述网络切片支持的系统特性的状态信息；接收单元，用于接收来自所述网络存储网元的所述网络切片支持的系统特性的状态信息。
在一种可能的实现方式中，所述请求消息还包括指定的时间段，所述请求消息具体用于请求获取在所述指定的时间段内的所述网络切片支持的系统特性的状态信息，则所述接收单元，具体用于接收来自所述网络存储网元的在所述指定时间段内的所述网络切片支持的系统特性的状态信息。
在一种可能的实现方式中，所述指定时间段内的所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述指定的时间段内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
在一种可能的实现方式中，所述请求消息还包括订阅周期，所述请求消息具体用于请求周期性的获取所述网络切片支持的系统特性的状态信息，则所述接收单元，具体用于接收所述网络存储网元根据所述订阅周期进行周期性地发送的所述网络切片支持的系统特性的状态信息。
在一种可能的实现方式中，所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述订阅周期内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
参阅图6所示，为本申请提供的一种装置示意图，该装置可以是上述网络切片管理网元、或网络存储网元、或第二网元。该装置600包括：处理器602、通信接口603、存储器601。可选的，装置600还可以包括总线604。其中，通信接口603、处理器602以及存储器601可以通过通信线路604相互连接；通信线路604可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended  industry standard architecture，简称EISA)总线等。所述通信线路604可以分为地址总线、数据总线、控制总线等。为便于表示，图6中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
处理器602可以是一个CPU，微处理器，ASIC，或一个或多个用于控制本申请方案程序执行的集成电路。
通信接口603，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)，有线接入网等。
存储器601可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically er服务器able programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路604与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器601用于存储执行本申请方案的计算机执行指令，并由处理器602来控制执行。处理器602用于执行存储器601中存储的计算机执行指令，从而实现本申请上述实施例提供的配置方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实 现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中，ASIC可以设置于终端中。可选地，处理器和存储媒介也可以设置于终端中的不同的部件中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (51)

  1. 一种配置方法，其特征在于，包括：
    网络存储网元接收来自网络切片管理网元的配置信息，所述配置信息包括网络切片的信息、所述网络切片支持的系统特性、所述系统特性对应的网络功能NF和与NF对应的NF服务；
    所述网络存储网元存储所述配置信息。
  2. 根据权利要求1所述的方法，其特征在于，所述系统特性包括第一系统特性,所述第一系统特性对应的NF包括第一NF,与NF对应的NF服务包括与所述第一NF对应的第一NF服务,所述方法还包括：
    所述网络存储网元接收来自第一网元的通知消息，所述第一网元为支持所述第一NF的网元,所述通知消息包括所述第一网元的NF服务的状态信息，所述第一网元的NF服务的状态信息包括所述第一NF服务的状态信息；
    所述网络存储网元根据所述第一NF服务的状态信息，确定所述第一系统特性的状态信息。
  3. 根据权利要求2所述的方法，其特征在于，所述第一网元的NF服务的状态信息包括所述NF服务在预设时长内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
  4. 一种配置方法，其特征在于，包括：
    网络切片管理网元向网络存储网元发送配置信息，所述配置信息包括网络切片的信息、所述网络切片支持的系统特性、所述系统特性对应的网络功能NF和与NF对应的NF服务；
    所述网络切片管理网元接收来自所述网络存储网元的配置完成指示。
  5. 一种配置方法，其特征在于，包括：
    网络存储网元接收来自第二网元的请求消息，所述请求消息包括网络切片的信息，所述请求消息用于请求获取所述网络切片支持的系统特性的状态信息；
    所述网络存储网元根据所述请求消息，向所述第二网元发送所述网络切片支持的系统特性的状态信息。
  6. 根据权利要求5所述的方法，其特征在于，所述请求消息还包括指定的时间段，则所述请求消息具体用于请求获取在所述指定的时间段内的所述网络切片支持的系统特性的状态信息；
    则所述网络存储网元根据所述请求消息，向所述第二网元发送所述网络切片支持的系统特性的状态信息，包括：
    所述网络存储网元向所述第二网元发送在所述指定时间段内的所述网络切片支持的系统特性的状态信息。
  7. 根据权利要求6所述的方法，其特征在于，所述指定时间段内的所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述指定的时间段内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
  8. 根据权利要求5所述的方法，其特征在于，所述请求消息还包括订阅周期，则所述请求消息具体用于请求周期性的获取所述网络切片支持的系统特性的状态信息；
    则所述网络存储网元根据所述请求消息，向所述第二网元发送所述网络切片支持的系统特性的状态信息，包括：
    所述网络存储网元根据所述请求消息中的所述订阅周期，周期性地向所述第二网元发送所述网络切片支持的系统特性的状态信息。
  9. 根据权利要求8所述的方法，其特征在于，所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述订阅周期内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
  10. 一种配置方法，其特征在于，包括：
    第二网元向网络存储网元发送请求消息，所述请求消息包括网络切片的信息，所述请求消息用于请求获取所述网络切片支持的系统特性的状态信息；
    所述第二网元接收来自所述网络存储网元的所述网络切片支持的系统特性的状态信息。
  11. 根据权利要求10所述的方法，其特征在于，所述请求消息还包括指定的时间段，所述请求消息具体用于请求获取在所述指定的时间段内的所述网络切片支持的系统特性的状态信息，
    则所述第二网元接收来自所述网络存储网元的所述网络切片支持的系统特性的状态信息，包括：
    所述第二网元接收来自所述网络存储网元的在所述指定时间段内的所述网络切片支持的系统特性的状态信息。
  12. 根据权利要求11所述的方法，其特征在于，所述指定时间段内的所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述指定的时间段内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
  13. 根据权利要求10所述的方法，其特征在于，所述请求消息还包括订阅周期，所述请求消息具体用于请求周期性的获取所述网络切片支持的系统特性的状态信息，
    所述第二网元接收来自所述网络存储网元的所述网络切片支持的系统特性的状态信息，包括：
    所述第二网元接收所述网络存储网元根据所述订阅周期进行周期性地发送的所述网络切片支持的系统特性的状态信息。
  14. 根据权利要求13所述的方法，其特征在于，所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述订阅周期内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
  15. 根据权利要求5-14任一所述的方法，其特征在于，所述请求消息还包括所述网络切片支持的系统特性中的第二系统特性，所述网络切片支持的系统特性的状态信息具体包括所述第二系统特性对应的NF服务的状态信息。
  16. 一种装置，其特征在于，包括：
    接收单元，用于接收来自网络切片管理网元的配置信息，所述配置信息包括网络切片的信息、所述网络切片支持的系统特性、所述系统特性对应的网络功能NF和与NF对应的NF服务；
    处理单元，用于将所述配置信息存储于存储单元。
  17. 根据权利要求16所述的装置，其特征在于，所述系统特性包括第一系统特性, 所述第一系统特性对应的NF包括第一NF,与NF对应的NF服务包括与所述第一NF对应的第一NF服务,所述接收单元，还用于接收来自第一网元的通知消息，所述第一网元为支持所述第一NF的网元,所述通知消息包括所述第一网元的NF服务的状态信息，所述第一网元的NF服务的状态信息包括所述第一NF服务的状态信息；
    所述处理单元，还用于根据所述第一NF服务的状态信息，确定所述第一系统特性的状态信息。
  18. 根据权利要求17所述的装置，其特征在于，所述第一网元的NF服务的状态信息包括所述NF服务在预设时长内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
  19. 一种装置，其特征在于，包括：
    发送单元，用于向网络存储网元发送配置信息，所述配置信息包括网络切片的信息、所述网络切片支持的系统特性、所述系统特性对应的网络功能NF和与NF对应的NF服务；
    接收单元，用于接收来自所述网络存储网元的配置完成指示。
  20. 一种装置，其特征在于，包括：
    接收单元，用于接收来自第二网元的请求消息，所述请求消息包括网络切片的信息，所述请求消息用于请求获取所述网络切片支持的系统特性的状态信息；
    发送单元，用于根据所述请求消息，向所述第二网元发送所述网络切片支持的系统特性的状态信息。
  21. 根据权利要求20所述的装置，其特征在于，所述请求消息还包括指定的时间段，则所述请求消息具体用于请求获取在所述指定的时间段内的所述网络切片支持的系统特性的状态信息；
    则所述发送单元，具体用于向所述第二网元发送在所述指定时间段内的所述网络切片支持的系统特性的状态信息。
  22. 根据权利要求21所述的装置，其特征在于，所述指定时间段内的所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述指定的时间段内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
  23. 根据权利要求20所述的装置，其特征在于，所述请求消息还包括订阅周期，则所述请求消息具体用于请求周期性的获取所述网络切片支持的系统特性的状态信息；
    则所述发送单元，具体用于根据所述请求消息中的所述订阅周期，周期性地向所述第二网元发送所述网络切片支持的系统特性的状态信息。
  24. 根据权利要求23所述的装置，其特征在于，所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述订阅周期内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
  25. 一种装置，其特征在于，包括：
    发送单元，用于向网络存储网元发送请求消息，所述请求消息包括网络切片的信息，所述请求消息用于请求获取所述网络切片支持的系统特性的状态信息；
    接收单元，用于接收来自所述网络存储网元的所述网络切片支持的系统特性的状态信息。
  26. 根据权利要求25所述的装置，其特征在于，所述请求消息还包括指定的时间 段，所述请求消息具体用于请求获取在所述指定的时间段内的所述网络切片支持的系统特性的状态信息，
    则所述接收单元，具体用于接收来自所述网络存储网元的在所述指定时间段内的所述网络切片支持的系统特性的状态信息。
  27. 根据权利要求26所述的装置，其特征在于，所述指定时间段内的所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述指定的时间段内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
  28. 根据权利要求25所述的装置，其特征在于，所述请求消息还包括订阅周期，所述请求消息具体用于请求周期性的获取所述网络切片支持的系统特性的状态信息，
    则所述接收单元，具体用于接收所述网络存储网元根据所述订阅周期进行周期性地发送的所述网络切片支持的系统特性的状态信息。
  29. 根据权利要求28所述的装置，其特征在于，所述网络切片支持的系统特性的状态信息包括所述系统特性对应的NF服务在所述订阅周期内被其他多个网元调用的总次数和/或被其他单个网元分别调用的次数。
  30. 根据权利要求20-29任一所述的装置，其特征在于，所述请求消息还包括所述网络切片支持的系统特性中的第二系统特性，所述网络切片支持的系统特性的状态信息具体包括所述第二系统特性对应的NF服务的状态信息。
  31. 一种配置装置，其特征在于，包括：通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求1到3任一项所述的方法中，在所述装置侧进行消息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求1到3任一项所述的方法中，在所述装置进行的消息处理或控制操作。
  32. 一种配置装置，其特征在于，包括通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求4所述的方法中，在所述装置侧进行消息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求4所述的方法中，在所述装置侧进行的消息处理或控制操作。
  33. 一种配置装置，其特征在于，包括通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求5到9任一项所述的方法中，在所述装置侧进行消息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求5到9任一项所述的方法中，在所述装置侧进行的消息处理或控制操作。
  34. 一种配置装置，其特征在于，包括通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求10到15任一项所述的方法中，在所述装置侧进行消息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求10到15任一项所述的方法中，在所述装置侧进行的消息处理或控制操作。
  35. 一种芯片系统，其特征在于，包括：所述芯片系统包括至少一个处理器，和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行权利要求1到3任一项所述的方法。
  36. 一种芯片系统，其特征在于，包括：所述芯片系统包括至少一个处理器，和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行权利要求4所述的方法。
  37. 一种芯片系统，其特征在于，包括：所述芯片系统包括至少一个处理器，和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行权利要求5到9任一项所述的方法。
  38. 一种芯片系统，其特征在于，包括：所述芯片系统包括至少一个处理器，和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行权利要求10到15任一项所述的方法。
  39. 一种配置装置，其特征在于，用于执行权利要求1到3任一项所述的方法。
  40. 一种配置装置，其特征在于，用于执行权利要求4所述的方法。
  41. 一种配置装置，其特征在于，用于执行权利要求5到9任一项所述的方法。
  42. 一种配置装置，其特征在于，用于执行权利要求10到15任一项所述的方法。
  43. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行上述权利要求1到3任一项所述的方法。
  44. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行上述权利要求4所述的方法。
  45. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行上述权利要求5到9任一项所述的方法。
  46. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行上述权利要求10到15任一项所述的方法。
  47. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1到3任一项所述的方法。
  48. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求4所述的方法。
  49. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求5到9任一项所述的方法。
  50. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求10到15任一项所述的方法。
  51. 一种通信系统，其特征在于，包括如权利要求20到24任一项所述的装置，和，如权利要求25到30任一项所述的装置。
PCT/CN2019/092814 2018-06-26 2019-06-25 一种配置方法及装置 WO2020001439A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19826341.0A EP3806394A4 (en) 2018-06-26 2019-06-25 CONFIGURATION PROCEDURE AND DEVICE
US17/131,231 US11824713B2 (en) 2018-06-26 2020-12-22 Configuration method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810674390.9A CN110650029B (zh) 2018-06-26 2018-06-26 一种配置方法及装置
CN201810674390.9 2018-06-26

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/131,231 Continuation US11824713B2 (en) 2018-06-26 2020-12-22 Configuration method and apparatus

Publications (1)

Publication Number Publication Date
WO2020001439A1 true WO2020001439A1 (zh) 2020-01-02

Family

ID=68986106

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/092814 WO2020001439A1 (zh) 2018-06-26 2019-06-25 一种配置方法及装置

Country Status (4)

Country Link
US (1) US11824713B2 (zh)
EP (1) EP3806394A4 (zh)
CN (1) CN110650029B (zh)
WO (1) WO2020001439A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110650029B (zh) * 2018-06-26 2021-05-18 华为技术有限公司 一种配置方法及装置
CN114528540A (zh) * 2020-10-30 2022-05-24 华为技术有限公司 一种服务授权方法、通信装置及系统
CN112671568B (zh) * 2020-12-16 2022-12-06 中盈优创资讯科技有限公司 一种5g核心网子网切片视图的生成方法、装置及设备
CN116406511A (zh) * 2021-11-05 2023-07-07 北京小米移动软件有限公司 一种网络切片的状态信息上报方法及其装置
CN114268535B (zh) * 2021-12-20 2024-01-19 杭州东方通信软件技术有限公司 一种5g切片产品开通方法及装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018067780A1 (en) * 2016-10-05 2018-04-12 Convida Wireless, Llc Capability exposure for service instantiation

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10425830B2 (en) * 2015-09-07 2019-09-24 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
EP3400731B1 (en) * 2016-01-08 2019-09-25 Telefonaktiebolaget LM Ericsson (PUBL) Access control in a network comprising network slices
US10142994B2 (en) * 2016-04-18 2018-11-27 Electronics And Telecommunications Research Institute Communication method and apparatus using network slicing
BR112018076166A2 (pt) * 2016-06-16 2019-03-26 Huawei Tech Co Ltd método e aparelho de gerenciamento de recursos de fatia da rede
US11184830B2 (en) * 2016-06-21 2021-11-23 Huawei Technologies Co., Ltd. Systems and methods for user plane path selection, reselection, and notification of user plane changes
CN107770794B (zh) * 2016-08-15 2023-05-09 华为技术有限公司 一种网络切片配置方法及装置
CN107889155A (zh) * 2016-09-30 2018-04-06 中兴通讯股份有限公司 一种网络切片的管理方法及装置
CN108024270B (zh) * 2016-11-03 2021-09-14 华为技术有限公司 一种信息发送方法、单元和系统
EP3563610B1 (en) * 2016-12-30 2020-03-04 Telefonaktiebolaget LM Ericsson (publ) Network slice selection
US10749796B2 (en) * 2017-04-27 2020-08-18 At&T Intellectual Property I, L.P. Method and apparatus for selecting processing paths in a software defined network
CN110650029B (zh) * 2018-06-26 2021-05-18 华为技术有限公司 一种配置方法及装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018067780A1 (en) * 2016-10-05 2018-04-12 Convida Wireless, Llc Capability exposure for service instantiation

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONOYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhancements to the Service-Based Architecture (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.742, no. V0.2.0, 10 June 2018 (2018-06-10), pages 1 - 39, XP051451681 *
ANONYMOUS: "Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2(Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.502, vol. SA WG2, no. V15.2.0, 19 June 2018 (2018-06-19), pages 1 - 308, XP051472861 *
See also references of EP3806394A4

Also Published As

Publication number Publication date
EP3806394A4 (en) 2021-07-21
EP3806394A1 (en) 2021-04-14
CN110650029B (zh) 2021-05-18
US20210111947A1 (en) 2021-04-15
CN110650029A (zh) 2020-01-03
US11824713B2 (en) 2023-11-21

Similar Documents

Publication Publication Date Title
WO2020001439A1 (zh) 一种配置方法及装置
WO2020147760A1 (zh) 一种局域网通信方法、装置及系统
US20200221376A1 (en) PDU Type Setting Method, UE Policy Setting Method, and Related Entity
JP7139522B2 (ja) ローカルエリアネットワーク通信方法、装置、およびシステム
WO2021017689A1 (zh) 一种用户面数据的获取方法、装置及存储介质
WO2019029525A1 (zh) 网络功能信息的管理方法及相关设备
AU2018376020B2 (en) Communication method and device
WO2020034976A1 (zh) 一种用户群组的会话管理方法及装置
WO2019105470A1 (zh) 一种用户群组的建立方法及装置
WO2019196811A1 (zh) 通信方法和相关装置
US20220060881A1 (en) Group management method, apparatus, and system
WO2020001437A1 (zh) 一种配置方法、协商方法及装置
WO2019192445A1 (zh) 一种组播组创建、组播组加入方法及装置
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
US11310658B2 (en) Method and apparatus for determining status of terminal device, and device
WO2020199733A1 (zh) 策略控制方法、设备及系统
WO2020042848A1 (zh) 一种网络切片管理方法及装置
WO2019057015A1 (zh) 一种网络切片管理方法及装置
WO2017220021A1 (zh) 短信息处理方法及装置
WO2019238049A1 (zh) 一种地址信息的获取方法及装置
WO2021160096A1 (zh) 一种私网签约信息更新方法及装置
TW202103475A (zh) 終端設備管理方法、伺服器及終端設備
EP3934174A1 (en) Terminal management and control method, apparatus and system
US20230026631A1 (en) Disaster Recovery Processing Method and Apparatus
WO2022041854A1 (zh) 一种通信方法及通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19826341

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019826341

Country of ref document: EP

Effective date: 20210108