WO2018170748A1 - 一种选择核心网设备的方法及装置 - Google Patents

一种选择核心网设备的方法及装置 Download PDF

Info

Publication number
WO2018170748A1
WO2018170748A1 PCT/CN2017/077586 CN2017077586W WO2018170748A1 WO 2018170748 A1 WO2018170748 A1 WO 2018170748A1 CN 2017077586 W CN2017077586 W CN 2017077586W WO 2018170748 A1 WO2018170748 A1 WO 2018170748A1
Authority
WO
WIPO (PCT)
Prior art keywords
management device
mobility management
group
type
identifier
Prior art date
Application number
PCT/CN2017/077586
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 PCT/CN2017/077586 priority Critical patent/WO2018170748A1/zh
Priority to CN201780088461.0A priority patent/CN110431865B/zh
Priority to EP17901991.4A priority patent/EP3592016B1/en
Publication of WO2018170748A1 publication Critical patent/WO2018170748A1/zh
Priority to US16/577,878 priority patent/US11129211B2/en

Links

Images

Classifications

    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method and apparatus for selecting a core network device.
  • the network can slice the same physical device of the core network into multiple logical core network network slice instances through the slicing technology, and each core network network slice instance can be customized according to specific business scenarios or user requirements.
  • each core network network slice instance can be customized according to specific business scenarios or user requirements.
  • operators can customize different network slice instances to meet the specific requirements of each service by freely and flexibly combining network performance indicators such as rate, capacity, coverage, delay, reliability, security, and availability.
  • the network deploys a plurality of dedicated core networks (DCNs), where the dedicated core network is the above-mentioned core network network slice instance.
  • DCNs dedicated core networks
  • Each DCN serves a user of a certain type or group.
  • the network defines a usage type for each user belonging to a certain type or group. As shown in Figure 1,
  • Step 101 The eNB sends a NAS request message of the UE to the MME1.
  • Step 102 The MME1 queries the HSS according to the Usage Type of the UE whether it can provide services for the UE.
  • Step 103 The HSS returns a query result to the MME1, where the query result indicates that the MME1 cannot provide services for the UE, and carries the MME identity information that can provide services for the UE as MME2.
  • Step 104 The MME2 sends a redirection command to the eNB, carrying the identifier information of the MME2.
  • Step 105 The eNB sends the NAS request of the terminal to the MME2 according to the identifier information of the MME2.
  • the dedicated core network determines a dedicated core network capable of serving the terminal according to the usage type of the terminal. If the private core network capable of serving the terminal is itself, the dedicated core network continues to provide services for the terminal. If the dedicated core network capable of serving the terminal is not itself, the dedicated core network notifies the radio access network node of the correct dedicated core network identity, and the radio access network node re-transfers the access request of the terminal to the correct dedicated core. network.
  • the dedicated core network determines whether the dedicated core network that is accessed is correct. When the dedicated core network that is accessed is incorrect, the access request of the terminal is forwarded to the terminal through the redirection process. The correct dedicated core network, resulting in additional signaling overhead and increased access latency.
  • the embodiment of the present invention provides a method and an apparatus for selecting a core network device, which are used to solve the problem of an increase in access delay caused by a redirection process of a terminal in the prior art, and an additional signaling overhead.
  • the embodiment of the present application provides a method for selecting a core network device, including: an access network node receiving an access layer message sent by a terminal, where the access layer message includes a NAS request message and a network selection auxiliary parameter, and the access network
  • the node determines the group identifier of the at least one mobility management device group according to the network selection auxiliary parameter query configuration information, and determines the device identifier of the target mobility management device according to the group identifier of the at least one mobility management device group, where the configuration information includes the network selection assistance parameter and the mobility management.
  • the network selection assistance parameter includes the type of the mobility management device, and the configuration information includes Corresponding relationship between the type of the mobile management device and the group identity of the mobility management device group; the access network node determines the group identity of the at least one mobility management device group according to the network selection assistance parameter query configuration information, including: the access network node according to the mobility management The type of the device queries the correspondence between the type of the mobility management device and the group identity of the mobility management device group, and determines the group identity of the at least one mobility management device group. Therefore, when the type of the mobility management device is matched, the matching success rate is high, and the access network node can relatively easily select a mobility management device for the terminal.
  • the network selection assistance parameter includes at least one slice type
  • the configuration information includes a correspondence relationship between the slice type and the group identity of the mobility management device group
  • the access network node queries the configuration information according to the network selection assistance parameter to determine at least A group identity of a mobility management device group, comprising: the access network node determining a group identity of the at least one mobility management device group according to the correspondence between the slice type and the group identity of the mobility management device group according to the at least one slice type. Therefore, when the slice type is matched, the matching success rate is high, and the access network node can relatively easily select a mobility management device for the terminal.
  • the network selection assistance parameter includes a type of the mobility management device and at least one slice type;
  • the configuration information includes a correspondence between the type of the mobility management device, the slice type, and the group identity of the mobility management device group;
  • Including indication information indicates that the access network node selects the mobility management device group according to the network selection assistance parameter according to the indication access network node; the access network node determines the group of the at least one mobility management device group according to the network selection auxiliary parameter query configuration information.
  • the identifier includes: when the indication information indicates that the access network node selects the mobility management device group according to the type of the mobility management device in the network selection assistance parameter, the access network node queries the type of the mobility management device and the mobility management according to the type of the mobility management device.
  • the access network node queries the correspondence between the type of the mobility management device and the group identity of the mobility management device group according to the type of the mobility management device, and determines the group of the at least one mobility management device group.
  • the identifier is used as the first group of identifiers; the access network node queries the correspondence between the slice type and the group identifier of the mobility management device group according to the at least one slice type, and determines the group identifier of the at least one mobility management device group as the second group identifier group; The network access node determines the group identifier of the at least one mobility management device group according to the intersection or union of the first group of identifier groups and the second group of identifier groups. Therefore, the access network node determines the matching rule according to the indication information, and the matching manner is more flexible.
  • the network selection assistance parameter includes a type of the mobility management device and at least one slice type;
  • the configuration information includes a correspondence between the type of the mobility management device, the slice type, and the group identity of the mobility management device group;
  • the access network The node determines the group identifier of the at least one mobility management device group according to the network selection auxiliary parameter query configuration information, and the access network node queries the correspondence between the type of the mobility management device and the group identity of the mobility management device group according to the type of the mobility management device.
  • the access network node Determining, by the access network node, the group identity of the at least one mobility management device group as the first group identity group; the access network node querying the correspondence between the slice type and the group identity of the mobility management device group according to the at least one slice type, determining the at least one mobility management device group
  • the group identifier is used as the second group identifier group; the access network node determines the group identifier of the at least one mobility management device group according to the intersection or union of the first group identifier group and the second group identifier group; or, when the access network node moves according to the Manage the type of device to query the type and move of the mobile management device
  • the group identifier of the at least one mobility management device group is determined as the first group identifier group, the correspondence between the slice type and the group identifier of the mobility management device group is not queried according to the at least one slice type.
  • the group identifier of the at least one mobility management device group included in the first group of identifier groups is used as the group identifier of the finally determined at least one mobility management device group. Therefore, the access network section According to the preset matching rule, the point is flexibly selected according to which one or which network selects the auxiliary parameter to query the configuration information, the matching manner is more flexible, and the matching efficiency is higher.
  • At least one slice type includes a default slice type, the default slice type is specified by the terminal or set by the network configuration; the access network node queries the slice type and mobility management according to at least one slice type. Determining, by the access network node, the correspondence between the slice type and the group identifier of the mobility management device group according to the default slice type, and determining at least one of the group identifiers of the device group. The group ID of the mobility management device group. Therefore, determining the group identifier of the mobility management device group according to the default slice type can effectively meet the basic requirements of the terminal and reduce the network access delay of the terminal.
  • the configuration information is sent by the respective mobility management device to the access network node, or configured by the network management device for the access network node. Therefore, the access network node can obtain configuration information in multiple ways, which is more flexible.
  • the access network node determines the device identity of the target mobility management device according to the group identity of the at least one mobility management device, including: the access network node selects the target mobility management device from the at least one mobility management device group.
  • the group performs a NAS node selection function on each mobility management device in the target mobility management device group to determine a device identity of the target mobility management device. Therefore, the access network node can determine the device identifier of the target mobility management device by using the prior art, and the compatibility with the prior art is better.
  • the configuration information further includes weight information corresponding to the mobility management device type of each mobility management device group; the access network node selects the target mobility management device group from the at least one mobility management device group, including: The access network node selects the target mobility management device group from the at least one mobility management device group according to the weight information of each mobility management device group in the at least one mobility management device group corresponding to the mobility management device type. Therefore, the access network node determines the target mobility management device group according to the weight information of each mobility management device group in the at least one mobility management device group corresponding to the mobility management device type, so as to ensure load balancing of each mobility management device group.
  • the configuration information further includes weight information corresponding to the slice type of each mobility management device group; at least one slice type includes a default slice type, and the default slice type is specified by the terminal or configured by the network.
  • the access network node selects the target mobility management device group from the at least one mobility management device group, including: the access network node corresponding to the default slice type according to each mobility management device group in the at least one mobility management device group Weight information, selecting a target mobility management device group from at least one mobility management device group.
  • the access network node determines the target mobility management device group according to the weight information corresponding to the default slice type of each mobility management device group in the at least one mobility management device group, so as to ensure load balancing of each mobility management device group.
  • the present application provides an apparatus for selecting a core network device for performing the method of any of the above aspects or any of the possible aspects of the first aspect.
  • the apparatus comprises means for performing the method of any of the above-described first aspect or any of the possible aspects of the first aspect.
  • the application provides an access network node, including a transceiver, a processor, and a memory.
  • the transceiver, the processor and the memory can be connected by a bus system.
  • the memory is for storing a program, instruction or code for executing a program, instruction or code in the memory to perform the method of any of the first aspect or the first aspect of the first aspect.
  • the embodiment of the present invention provides a communication system, where the system includes the access network node in the foregoing third aspect, and optionally, the system may further include the solution provided in the embodiment of the present application. Other devices that the access network node interacts with.
  • the present application provides a computer readable storage medium, stored in the computer readable storage medium There is an instruction, when run on a computer, that causes the computer to perform the method of any of the above aspects or any of the possible aspects of the first aspect.
  • the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • FIG. 1 is a flow chart of a terminal accessing a franchise core network in the background art of the present application
  • FIG. 2 is a schematic diagram of an application scenario of selecting a core network device according to an embodiment of the present application
  • FIG. 3 is a flowchart of an overview of selecting a core network device in an embodiment of the present application.
  • FIG. 4 is a specific flowchart of a first implementation manner of determining, by an access network node, a group identifier of at least one mobility management device group according to an embodiment of the present disclosure
  • FIG. 5 is a specific flowchart of a second implementation manner of determining, by an access network node, a group identifier of at least one mobility management device group according to an embodiment of the present disclosure
  • FIG. 6 is a specific flowchart of determining a target mobility management device group when the configuration information includes weight information corresponding to a slice type of each mobility management device group in the embodiment of the present application;
  • FIG. 7 is a specific flowchart of a third implementation manner of determining, by an access network node, a group identifier of at least one mobility management device group according to an embodiment of the present disclosure
  • FIG. 8 is a schematic structural diagram of an apparatus for selecting a core network device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of an access network node in an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a specific application scenario of the present application. It should be noted that the core network network slice example in FIG. 2 is only an example and is not limited to the present application.
  • the carrier network deploys four core network network slicing instances for Enhanced Mobile Broadband (eMBB), Massive Internet of Things (MIoT), and vehicle-to-external information exchange. (Vehicle to X, V2X), and four business scenarios of Ultra Reliable & Low Latency Communication (uRLLC).
  • eMBB Enhanced Mobile Broadband
  • MIoT Massive Internet of Things
  • uRLLC Ultra Reliable & Low Latency Communication
  • the core network segmentation instance of eMBB and mIoT has a shared control plane function, which is recorded as Common CP 1.
  • the core network segmentation instance of V2X and URLLC also has a shared control plane function, which is recorded as Common CP 2.
  • the RAN Node is shared by all core network network slice instances.
  • the RAN Node can first access the Common CP 1.
  • the RAN Node can be connected first. Enter Common CP 2.
  • the terminal in the present application is a terminal device supporting a 5G network, but the terminal to which the present application can be applied is not limited thereto, and can be applied to all kinds of terminal devices, including mobile phones, Internet of things devices, smart home devices, and industrial control devices. , vehicle equipment, etc.
  • the RAN Node in this application is an access network node, and may be a 3GPP radio access network node, or may be a non-3GPP access point, such as a Wi-Fi access point, or a fixed network access point.
  • the Slice instance Common Part refers to one or more slice instances.
  • Episode control plane devices or network features such as mobility management devices or Mobility Management Function (MMF).
  • MMF Mobility Management Function
  • Slice instance Dedicated Part refers to the control plane device or network function exclusive to the core network slice instance, such as session management device or network management function (SMF).
  • SMF network management function
  • an embodiment of the present application provides a method for selecting a core network device, including:
  • Step 300 The access network node receives the message sent by the terminal, where the access layer message includes a Non-Access Stratum (NAS) request message and a network selection assistance parameter; the network selection assistance parameter is used to indicate that the access network node is the terminal. Select a mobile management device.
  • NAS Non-Access Stratum
  • the access layer message herein may be a Radio Resource Control (RRC) message.
  • RRC Radio Resource Control
  • Step 310 The access network node determines the group identifier of the at least one mobility management device group according to the network selection auxiliary parameter query configuration information, where the configuration information includes the correspondence between the network selection assistance parameter and the group identifier of the mobility management device group.
  • Step 320 The access network node determines the device identifier of the target mobility management device according to the group identifier of the at least one mobility management device group.
  • Step 330 The access network node sends a NAS request message to the mobility management device indicated by the device identifier of the target mobility management device.
  • the access network node before performing step 300, obtains configuration information. Specifically, the configuration information is sent by each mobility management device to the access network node, or the network management device is the access network node. Configured.
  • the access network node determines the device identifier of the target mobility management device according to the group identifier of the at least one mobility management device, and may adopt the following method: the access network node is from the at least one mobility management device group. Select the target mobility management device group. Then, the access network node performs a NAS node selection function on each of the mobile management devices in the target mobility management device group to determine the device identity of the target mobility management device.
  • each mobility management device in the mobility management device group configures its own weight information to the access network node, and the access network node determines a mobility management device according to the load balancing principle.
  • a mobility management device group includes three mobility management devices A1, A2, and A3, and the weight information of A1, A2, and A3 is 10%, 60%, and 30%, respectively, and therefore, every 10 are allocated to the mobility management device.
  • the RAN Node assigns one NAS request message to A1, six NAS request messages to A2, and three NAS request messages to A3.
  • the type of mobility management device referred to in this application is used to indicate the processing mechanism or behavior of the mobility management device to support the functions and services provided by one or more slices, for example, Type of MMF, AMF Type .
  • the slice type is used to indicate the processing mechanism or behavior of the network slice to support the functions and services provided by the slice, for example, Type of SMF, Slice Type, Service Type.
  • the group ID of the mobility management device group can be represented by the MMF Group ID.
  • the device identification of the mobility management device can be represented by the MMF Instance ID.
  • the device identifier of each mobility management device may be carried when the mobility management device sends configuration information to the access network node, or is carried by the network management device when configuring configuration information for the access network node.
  • the terminal may obtain the type and/or slice type of the mobility management device through the mobility management device, or the terminal configures the type and/or slice type of the mobility management device in advance.
  • the mobility management device mentioned in this application may also be a Core Access and Mobility Management Function (AMF).
  • the type of the mobility management device may also be an AMF Type.
  • the group identity of the mobility management device group may be represented by an AMF Group ID
  • the device identity of the mobility management device may be represented by an AMF Instance ID.
  • step 310 in the embodiment of the present application is described below.
  • the network selection assistance parameter includes a type of the mobility management device
  • the configuration information includes a correspondence between the type of the mobility management device and the group identity of the mobility management device group.
  • the access network node queries the correspondence between the type of the mobility management device and the group identity of the mobility management device group according to the type of the mobility management device, and determines the group identity of the at least one mobility management device group.
  • the correspondence between the type of the mobility management device and the group identity of the mobility management device group is as shown in Table 1.
  • the types of mobility management devices in Table 1 give the fields eMBB+mIoT and V2X+URLLC, but for the sake of understanding, the actual implementation may be expressed in numerical or scalar manner, for example, C001 for eMBB+mIoT and D001 for eMBB, D002. Represents mIoT and so on. It should be understood that the various information listed in Table 1 is merely exemplary and is not intended to limit the application.
  • FIG. 4 The specific implementation process of the first implementation manner is illustrated by using FIG. 4 as an example.
  • the RAN Node receives the configuration message sent by the MMF 1 and the MMF 2.
  • the MMF currently connected by the RAN Node includes the MMF 1 and the MMF 2, and the MMF 1 and the MMF 2 respectively send configuration messages to the RAN Node, and the configuration message sent by the MMF1 is
  • the mapping between the Type of MMF and the MMF Group ID supported by the MMF2 includes the mapping between the Type of MMF and the MMF Group ID supported by the MMF2, as shown in Table 1. It is assumed here that the MMF 1Group includes only one mobility management device MMF1, and the MMF 1Group includes only one mobility management device MMF2.
  • each mobility management device in the MMF 1Group sends configuration information to the RAN Node, and the RAN Node collects the number of MMFs that send the same configuration information, and knows the number of MMFs included in the MMF 1Group and each. MMF Instance ID.
  • the configuration information is sent to the RAN Node by using the MMF as an example.
  • the configuration information of the RAN Node can also be configured in advance by the network management device.
  • the UE sends an RRC message to the RAN Node, where the NAS request message and the Type of MMF are included, for example, the Type of MMF is eMBB+mIoT.
  • step 300 For details, refer to step 300.
  • the RAN Node obtains the MMF 1 Group ID according to the Type of MMF query configuration information provided by the UE, that is, Table 1.
  • S404 The RAN Node performs the NAS node selection function according to the MMF 1Group ID to obtain the MMF 1Instance ID.
  • step 320 For details, refer to step 320.
  • S405 The RAN Node forwards the NAS request message of the UE to the MMF indicated by the MMF 1Instance ID.
  • step 330 For details, refer to step 330.
  • the MMF 1 sends a NAS accept message (NAS accept) to the UE, including a Type of MMF.
  • NAS accept NAS accept message
  • the NAS information may or may not be consistent with the Type of MMF provided by the UE.
  • the MMF 1 needs to update the Type of MMF.
  • the RAN Node may perform an NAS node selection function according to the default MMF Group to obtain an MMF Instance ID to the MMF.
  • the MMF indicated by the Instance ID forwards the NAS request message of the UE.
  • the network selection assistance parameter at this time may further include at least one slice type
  • the configuration information further includes a correspondence relationship between the slice type and the group identifier of the mobility management device group.
  • the RAN Node fails to query the matched MMF Group from the configuration information according to the Type of MMF provided by the UE, the RAN Node may query the correspondence between the slice type and the group identifier of the mobility management device group according to the at least one slice type, and determine at least one For the group ID of the mobility management device group, refer to the second implementation.
  • the configuration information further includes weight information corresponding to the mobility management device type of each mobility management device group, and the access network node selects the target mobility management from the at least one mobility management device group.
  • the device group may adopt the following method: the access network node selects the target mobility management device group from the at least one mobility management device group according to the weight information of each mobility management device group corresponding to the mobility management device type in the at least one mobility management device group. .
  • the three mobile management device groups are G1, G2, and G3, respectively, and the three mobile management devices have the same type, and the weight information corresponding to the mobile management device type of G1, G2, and G3 is 20% and 50%, respectively. 30%, therefore, for every 10 NAS request messages assigned to this type of mobility management device group, the RAN Node assigns 2 NAS request messages to G1, 5 NAS request messages to G2, and 3 NAS request message assignments. Give G3.
  • the network selection auxiliary parameter includes at least one slice type
  • the configuration information includes a correspondence between the slice type and the group identifier of the mobility management device group.
  • the access network node queries the correspondence between the slice type and the group identifier of the mobility management device group according to the at least one slice type, and determines the group identifier of the at least one mobility management device group.
  • the correspondence between the slice type and the group identifier of the mobility management device group is as shown in Table 2.
  • the RAN Node selects the MMF for the UE according to the Type of MMF.
  • the MMF can be selected for the terminal by adopting the embodiment as shown in FIG. 5.
  • FIG. 5 The specific implementation process of the second implementation manner is illustrated by using FIG. 5 as an example.
  • S501 The RAN Node receives the configuration message sent by the MMF 1 and the MMF 2.
  • the MMF currently connected by the RAN Node includes the MMF 1 and the MMF 2, and the MMF 1 and the MMF 2 respectively send configuration messages to the RAN Node
  • the configuration message sent by the MMF1 is Includes the mapping between Type of SMF and MMF Group ID supported by MMF1, and the configuration sent by MMF2.
  • the message includes the mapping between Type of SMF and MMF Group ID supported by MMF2, as shown in Table 2.
  • the configuration information is sent to the RAN Node by using the MMF as an example.
  • the configuration information of the RAN Node can also be configured in advance by the network management device.
  • S502 The UE sends an RRC message to the RAN Node, where the NAS request message and the Type of SMF are included, for example, the Type of SMF is eMBB.
  • step 300 For details, refer to step 300.
  • S503 The RAN Node queries the configuration information according to the Type of SMF provided by the UE, that is, Table 2, to obtain an MMF 1 Group ID.
  • S504 The RAN Node performs the NAS node selection function according to the MMF 1Group ID to obtain the MMF 1Instance ID.
  • step 320 For details, refer to step 320.
  • S505 The RAN Node forwards the NAS request message of the UE to the MMF indicated by the MMF 1Instance ID.
  • step 330 For details, refer to step 330.
  • the MMF1 sends a NAS accept message to the UE, including a Type of MMF.
  • the UE can obtain the type of the mobility management device by S506, and the RRC can include the NAS request message and the Type of MMF when the UE sends an access layer message to the RAN Node.
  • the network selection assistance parameter at this time may further include a type of the mobility management device, where the configuration information includes a correspondence between the type of the mobility management device and the group identity of the mobility management device group, when the RAN Node fails to provide the Type of SMF according to the UE.
  • the RAN Node may query the correspondence between the type of the mobility management device and the group identity of the mobility management device group according to the type of the mobility management device, and determine the group identity of the at least one mobility management device group. See the first implementation for details.
  • At least one slice type includes a default slice type, and the default slice type is specified by the terminal or set by the network configuration.
  • the access network node queries the correspondence between the slice type and the group identifier of the mobility management device group according to the default slice type, and determines the group identifier of the at least one mobility management device group.
  • the group identifier of the at least one mobility management device group is determined for the terminal according to the default slice type.
  • the UE sends an RRC message to the RAN Node, including the NAS request message and the Type of SMF, where the Type of SMF includes eMBB and V2X, and the eMBB is the default slice type, because the operator may not deploy the eMBB+V2X sharing.
  • Type of MMF at which point the access network node may not be able to find MMFs that support both eMBB and V2X. Therefore, when the eMBB is the default slice type, the access network node may determine the group identifier of the at least one mobility management device group according to the correspondence between the eMBB query slice type and the group identity of the mobility management device group.
  • the eMBB is the default slice type that can be specified by the terminal or set by the network configuration.
  • the configuration information further includes weight information corresponding to the slice type for each mobility management device group.
  • the access network node selects the target mobility management device group from the at least one mobility management device group, and may perform weight information corresponding to the default slice type according to each mobility management device group in the at least one mobility management device group.
  • a target mobility management device group is selected from at least one mobility management device group.
  • the configuration information further includes how to determine the target mobility management device group when each mobility management device group corresponds to the slice type weight information.
  • the RAN Node receives the configuration message sent by the MMF 1, the MMF 2, and the MMF3, as shown in Table 3.
  • the configuration information sent by each MMF further includes weight information corresponding to the slice type of the MMF, for example, in Figure 6.
  • Load Information Weight Factor per SMF type).
  • the UE sends an RRC message to the RAN Node, where the NAS request message and the Type of SMF are included, for example, the Type of SMF is eMBB.
  • step 300 For details, refer to step 300.
  • the RAN Node queries the configuration information according to the Type of SMF provided by the UE, that is, Table 3, to obtain an MMF 1 Group ID and an MMF 3 Group ID.
  • step 310 For details, refer to step 310.
  • the RAN Node selects the MMF 3 Group ID according to the weight information of the eMBB, that is, the weight factor, respectively, according to the MMF 1 Group ID and the MMF 3 Group ID.
  • MMF 1 sets eMBB's weight factor to 3 and MMF 2 sets eMBB's weight factor to 7, then RAN Node will treat 30% of the total eMBB service to MMF 1 and will account for 70% of eMBB.
  • MMF 3 sets eMBB's weight factor to 7.
  • the RAN Node performs the NAS node selection function according to the MMF 3Group ID to obtain the MMF 3Instance ID.
  • step 320 refers to step 320 in S604 and S605.
  • S606 The RAN Node forwards the NAS request message of the UE to the MMF indicated by the MMF 3Instance ID.
  • step 330 For details, refer to step 330.
  • the MMF3 sends a NAS accept message to the UE, including a Type of MMF.
  • the Type of SMF includes a slice type, which can be directly used as the default slice type.
  • the default slice type needs to be determined.
  • the MMF 1Group ID and the MMF 3 Group ID are obtained according to the eMBB lookup table 3
  • the MMF 2Group is obtained according to the URLLC query table 3.
  • ID when eMBB is the default slice type, the MMF is determined by the method shown in FIG. 6.
  • the URLLC is the default slice type
  • the RAN Node performs the NAS node selection function according to the MMF 2Group ID to obtain the target mobility management device.
  • Equipment Identity is the default slice type.
  • the group identifier of the at least one mobility management device group is first determined according to the default slice type query table 3, and then the target mobile device group is further determined according to the method shown in FIG. 6. Group ID.
  • the network selection assistance parameter includes a type of the mobility management device and at least one slice type
  • the configuration information includes a correspondence between a type of the mobility management device, a slice type, and a group identity of the mobility management device group
  • the configuration information further includes an indication Information indicating that the access network node selects the mobility management device according to the network selection assistance parameter Backup group
  • the configuration information herein may include a correspondence between the type of the mobility management device, the slice type, and the correspondence between the group identifiers of the mobility management device group, or the configuration information herein may include the mobility management device.
  • the access network node when the indication information indicates that the access network node selects the mobility management device group according to the type of the mobility management device in the network selection assistance parameter, the access network node queries the type and the mobility of the mobility management device according to the type of the mobility management device. The correspondence between the group identifiers of the management device group is determined, and the group identifier of the at least one mobility management device group is determined.
  • a second case when the indication information indicates that the access network node selects the mobility management device group according to at least one of the network selection assistance parameters, the access network node queries the slice type and the group of the mobility management device group according to the at least one slice type. Determining, by the identifier, a group identifier of the at least one mobility management device group;
  • the access network node when the indication information indicates that the access network node selects the mobility management device group according to the type of the mobility management device and the at least one slice type in the network selection assistance parameter, the access network node queries the mobility management according to the type of the mobility management device.
  • Corresponding relationship between the type of the device and the group identity of the mobility management device group determining the group identity of the at least one mobility management device group as the first group identity group; the access network node querying the slice type and the mobility management device group according to the at least one slice type Corresponding relationship of the group identifier, determining the group identifier of the at least one mobility management device group as the second group identifier group; the access network node determining the at least one mobility management device according to the intersection or union of the first group identifier group and the second group identifier group The group ID of the group.
  • the order in which the access network node determines the first group of identifiers to combine the second group of identifier groups is not limited.
  • the configuration information includes the correspondence between the type of the mobility management device, the slice type, and the group identity of the mobility management device group.
  • the UE sends an RRC message to the RAN Node, including a NAS request message, and a Type of SMF and a Type of MMF, the Type of MMF is eMBB+mIoT, and the Type of SMF is eMBB.
  • the indication information indicates that the access network node selects the mobility management device group according to the type of the mobility management device and the at least one slice type in the network selection assistance parameter
  • the RAN Node obtains the MMF 1Group according to the Type of SMF query configuration information provided by the UE, that is, Table 4. ID and MMF 3Group ID.
  • the RAN Node obtains the MMF 1 Group ID according to the Type of MMF lookup table 4 provided by the UE.
  • the RAN Node determines the MMF 1Group ID as the MMF Group with the highest matching degree according to the above query result.
  • the UE sends an RRC message to the RAN Node, including a NAS request message, and a Type of SMF and a Type of MMF, the Type of MMF is eMBB, and the Type of SMF is eMBB.
  • the indication information indicates that the access network node selects the mobility management device group according to the type of the mobility management device and the at least one slice type in the network selection assistance parameter
  • the RAN Node obtains the configuration information according to the Type of SMF provided by the UE, that is, Table 4, MMF 1Group ID and MMF3Group ID.
  • the RAN Node cannot match the appropriate MMF group according to the Type of MMF lookup table 4 provided by the UE, because in actual applications, each Type of MMF is usually represented by a numerical scalar, and the value defined by eMBB+mIoT is 003, defined by eMBB. The value is 002. at this time.
  • the RAN Node does not obtain an intersection according to the foregoing query result.
  • the MMF Group ID and the MMF 3 Group ID are determined to be the MMF Group with the highest matching degree.
  • the configuration information further includes weight information corresponding to the slice type of each mobility management device group, the access network node selects the target mobility management device group from the at least one mobility management device group.
  • the indication information may also be configured in the RAN Node by default, and the RAN Node performs the foregoing process according to the default configuration rule, and does not need to be separately indicated by the configuration information sent by each MMF.
  • S701 The RAN Node receives configuration messages sent by MMF 1, MMF 2, and MMF3, as shown in Table 4. In addition, the same indication information is included in each configuration information.
  • the UE sends an RRC message to the RAN Node, where the NAS request message, the Type of SMF, and the Type of MMF, for example, the Type of MMF is eMBB+mIoT, and the Type of SMF is eMBB.
  • step 300 For details, refer to step 300.
  • the RAN Node determines, according to the indication information, which one or more network selection assistance parameters select the mobility management device group, to obtain the MMF1Group ID.
  • the RAN Node queries Table 4 to obtain the MMF 1 Group ID;
  • the RAN Node when the indication information indicates that the RAN Node selects the mobility management device group according to the Type of SMF, the RAN Node queries Table 4 to obtain the MMF 1 Group ID and the MMF 3 Group ID;
  • the RAN Node when the indication information indicates that the RAN Node selects the mobility management device group according to the Type of SMF and the Type of MMF, the RAN Node queries Table 4, the first group identification group includes the MMF 1 Group ID, and the second group identification group includes the MMF1 Group ID and the MMF. 3Group ID, the RAN Node takes the intersection of the first group of the identifier group and the second group of the identifier group, and obtains the MMF 1 Group ID, or obtains the merged group according to the first group of the identifier group and the second group of the identifier group, and obtains the MMF 1 Group ID and the MMF 3 Group. ID.
  • MMF 1Group ID is taken as an example, and it can also be an MMF 3 Group ID.
  • S704 The RAN Node performs the NAS node selection function according to the MMF 1Group ID to obtain the MMF 1Instance ID.
  • step 320 For details, refer to step 320.
  • S705 The RAN Node forwards the NAS request message of the UE to the MMF indicated by the MMF 1Instance ID.
  • step 330 For details, refer to step 330.
  • the MMF1 sends a NAS accept message to the UE, including a Type of MMF.
  • the network selection auxiliary parameter includes a type of the mobility management device and at least one slice type
  • the configuration information includes a correspondence between a type of the mobility management device, a slice type, and a group identity of the mobility management device group
  • step 310 the following can be specifically divided into the following two cases:
  • the access network node queries the correspondence between the type of the mobility management device and the group identity of the mobility management device group according to the type of the mobility management device, and determines the group identity of the at least one mobility management device group as the first group identity group;
  • the access network node queries the correspondence between the slice type and the group identifier of the mobility management device group according to the at least one slice type, and determines the group identifier of the at least one mobility management device group as the second group identifier group; the access network node according to the first group identifier
  • the intersection or union of the group with the second set of identification groups determines the group identification of the at least one mobility management device group.
  • the specific implementation of the first case is consistent with the third case of the third implementation, except that the MMF is not required to send the indication information.
  • the second case is: when the access network node queries the correspondence between the type of the mobility management device and the group identity of the mobility management device group according to the type of the mobility management device, determining the group identity of the at least one mobility management device group as the first group identity group
  • the group identifier of the at least one mobility management device group included in the first group of identifier groups is used as the finally determined at least one mobility management.
  • Group ID of the device group is used as the finally determined at least one mobility management.
  • the access network node may first query the correspondence between the type of the mobility management device and the group identity of the mobility management device group according to the type of the mobility management device, and if the group identifier of the at least one mobility management device group is queried, it is not necessary to further according to at least A slice type queries the correspondence between the slice type and the group identifier of the mobility management device group. Therefore, the matching method is simpler and more flexible, and the matching efficiency is higher.
  • the access network node may first query the correspondence between the slice type and the group identifier of the mobility management device group according to the at least one slice type, and if the group identifier of the at least one mobility management device group is queried, it is not necessary to further move according to the The type of the management device queries the correspondence between the type of the mobility management device and the group identity of the mobility management device group. Therefore, the type of the mobility management device or the slice type is preferentially matched, and the configuration can be flexibly configured according to actual network requirements.
  • the present application further provides an apparatus for selecting a core network device, where the apparatus may be used to perform the steps performed by the access network node device in FIG. 3, and therefore, the apparatus for selecting a core network device provided by the embodiment of the present application is provided.
  • the apparatus may be used to perform the steps performed by the access network node device in FIG. 3, and therefore, the apparatus for selecting a core network device provided by the embodiment of the present application is provided.
  • Embodiments can be found in the implementation of the method.
  • an apparatus for selecting a core network device includes:
  • the receiving unit 810 is configured to receive a radio resource control access layer message sent by the terminal, where the access layer message includes a non-access stratum NAS request message and a network selection assisting parameter;
  • the processing unit 820 is configured to determine, according to the network selection auxiliary parameter query configuration information, a group identifier of the at least one mobility management device group, where the configuration information includes a correspondence between the network selection assistance parameter and the group identifier of the mobility management device group, and according to the at least one mobile
  • the group identifier of the management device group determines the device identifier of the target mobility management device
  • the sending unit 830 is configured to send a NAS request message to the mobility management device indicated by the device identifier of the target mobility management device.
  • the network selection assistance parameter includes a type of the mobility management device, and the configuration information includes a correspondence between the type of the mobility management device and the group identity of the mobility management device group;
  • the processing unit 820 is specifically configured to:
  • the network selection assistance parameter includes at least one slice type, and the configuration information includes a correspondence between the slice type and the group identifier of the mobility management device group;
  • the unit 820 is specifically configured to:
  • the network selection assistance parameter includes a type of the mobility management device and at least one slice type;
  • the configuration information includes a correspondence between the type of the mobility management device, the slice type, and the group identity of the mobility management device group; Including the indication information, the indication information instructing the access network node to query the configuration information according to the network selection auxiliary parameter indicated by the indication information;
  • the processing unit 820 is specifically configured to:
  • the indication information indicates the type of the mobility management device included in the network selection assistance parameter
  • the correspondence between the type of the mobility management device and the group identity of the mobility management device group is queried according to the type of the mobility management device, and the at least one mobility management device group is determined.
  • the group identifier of the at least one mobility management device group determines, when the indication information indicates at least one slice type included in the network selection assistance parameter, the group identifier of the at least one mobility management device group according to the correspondence between the slice type and the group identifier of the mobility management device group according to the at least one slice type;
  • the correspondence between the type of the mobility management device and the group identity of the mobility management device group is determined according to the type of the mobility management device, and determining Determining, by the group identifier of the at least one mobility management device group, a group identifier of the at least one mobility management device group as a second group according to the correspondence between the slice type and the group identity of the mobility management device group according to the at least one slice type An identification group; determining a group identifier of the at least one mobility management device group according to an intersection or a union of the first group identification group and the second group identification group.
  • the network selection assistance parameter includes a type of the mobility management device and at least one slice type;
  • the configuration information includes a correspondence between a type of the mobility management device, a slice type, and a group identity of the mobility management device group;
  • the processing unit 820 is specifically configured to:
  • the correspondence between the type of the mobility management device and the group identity of the mobility management device group is determined, and when the group identity of the at least one mobility management device group is determined as the first group identity group, no longer according to at least one slice.
  • the group identifier of the at least one mobility management device group included in the first group identifier group is used as the group identifier of the finally determined at least one mobility management device group.
  • At least one slice type includes a default slice type, and the default slice type is specified by the terminal or set by the network configuration;
  • the processing unit 820 is specifically configured to: when the group identifier of the at least one mobility management device group is determined, according to the correspondence between the slice type and the group identifier of the mobility management device group, the processing unit 820 is specifically configured to:
  • the configuration information is sent to the device by each mobile management device or configured by the network management device for the device.
  • the processing unit 820 is specifically configured to:
  • Performing a NAS node selection function on each of the mobile management devices in the target mobility management device group determines the device identity of the target mobility management device.
  • the configuration information further includes weight information corresponding to the mobility management device type of each mobility management device group;
  • the processing unit 820 is specifically configured to:
  • the configuration information further includes weight information corresponding to the slice type of each mobility management device group; at least one slice type includes a default slice type, and the default slice type is specified by the terminal or configured by the network. set up;
  • the processing unit 820 is specifically configured to:
  • the present application further provides an access network node, which can be used to perform the steps performed by the access network node in FIG. 3, and therefore, an implementation manner of the access network node provided in this embodiment of the present application can be referred to. The implementation of the method will not be repeated here.
  • an embodiment of the present application provides an access network node 900, where the device includes a transceiver 910, a processor 920, and a memory 930.
  • the transceiver 910, the processor 920, and the memory 930 can pass through a bus.
  • the system is connected.
  • the memory 930 is configured to store a program, an instruction, or a code
  • the processor 920 is configured to execute a program, an instruction, or a code in the memory 930 to perform: receiving, by the transceiver 910, a radio resource control access layer message sent by the terminal, and accessing
  • the layer message includes a non-access stratum NAS request message and a network selection auxiliary parameter; determining, according to the network selection auxiliary parameter query configuration information, a group identifier of the at least one mobility management device group, where the configuration information includes a network selection auxiliary parameter and a group of the mobility management device group Corresponding relationship of the identifier; and determining a device identity of the target mobility management device according to the group identity of the at least one mobility management device group; transmitting, by the transceiver 910, the NAS management message to the mobility management device indicated by the device identity of the target mobility management device.
  • the functions of the receiving unit 810 and the sending unit 830 in FIG. 8 can be implemented by the transceiver 910 in FIG. 9, and the function of the processing unit 820 in FIG. 8 can be used in FIG.
  • the processor 920 is implemented.
  • the method provided by the embodiment of the present application can effectively avoid the process of redirection, reduce the signaling interaction between the network devices, and reduce the network access delay of the terminal.
  • the matching success rate is high, and the access network node can easily select a mobility management device for the terminal, but may not fully satisfy the access requirement of the terminal.
  • the matching success rate is lower.
  • the access network node may be unable to select a mobility management device that meets the conditions for the terminal. In this case, a default mobility management device may be set, or one mobility management device may be selected from the first group identification group or the second group identification group. The group ID of the group.
  • the terminal can only access one core network network sharding instance, which cannot meet the requirements and requirements for the simultaneous access of multiple core network network sharding instances, and is provided by the embodiment of the present application.
  • the method can support the scenario that the terminal accesses multiple core network network slice instances at the same time.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Abstract

一种选择核心网设备的方法及装置，该方法包括：接入网节点接收终端发送的接入层消息，接入层消息包括NAS请求消息和网络选择辅助参数；接入网节点根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，配置信息包括网络选择辅助参数与移动管理设备组的组标识的对应关系，并根据所述至少一个移动管理设备组的组标识确定目标移动管理设备的设备标识；接入网节点向目标移动管理设备的设备标识指示的移动管理设备发送NAS请求消息。因此，能够有效避免重定向的过程，减少了各个网络设备之间的信令交互，降低了终端入网时延。

Description

一种选择核心网设备的方法及装置 技术领域
本申请涉及通信技术领域，尤其涉及一种选择核心网设备的方法及装置。
背景技术
在未来通信系统中，网络可以通过切片技术将核心网的同一套物理设备切分出多个逻辑的核心网网络切片实例，每个核心网网络切片实例可以根据具体的商业场景或用户需求做定制化，从而满足多样性业务，且同时保证了网络切片实例之间的相互隔离。因此，运营商可以通过对速率、容量、覆盖率、延迟、可靠性、安全性和可用性等网络性能指标进行自由灵活组合，定制不同的网络切片实例，从而满足各个业务的具体要求。
现有技术中，网络会部署多个专用核心网(Dedicated Core Network，DCN)，这里的专用核心网即上述的核心网网络切片实例。每个DCN服务于某一类型或某一群组的用户。网络为每个属于某一类型或群组的用户定义了一个使用类型(Usage Type)。如图1所示，
步骤101：eNB将UE的NAS请求消息发送至MME1。
步骤102：MME1根据该UE的Usage Type向HSS查询自身能否为该UE提供服务。
步骤103：HSS向MME1回复查询结果，该查询结果指示MME1不能为该UE提供服务，携带能够为UE提供服务的MME标识信息为MME2。
步骤104：MME2向eNB发送重定向命令，携带MME2的标识信息。
步骤105：eNB根据MME2的标识信息，将终端的NAS请求发送至MME2。
因此，当终端通过无线接入网节点接入某个专用核心网时，该专用核心网根据终端的Usage Type确定能够服务该终端的专用核心网。如果能够服务该终端的专用核心网为自身，则该专用核心网继续为该终端提供服务。如果能够服务该终端的专用核心网非自身，则该专用核心网通知无线接入网节点正确的专用核心网标识，由无线接入网节点重新将该终端的接入请求转发到正确的专用核心网。
现有技术中需要终端接入专用核心网后，由专用核心网判断接入的专用核心网是否正确，当接入的专用核心网不正确时，通过重定向过程将终端的接入请求转发到正确的专用核心网，因此带来额外的信令开销，并导致接入时延增加。
发明内容
本申请实施例提供一种选择核心网设备的方法及装置，用以解决现有技术中终端由于重定向过程导致的接入时延增加，以及额外信令开销的问题。
第一方面，本申请实施例提供一种选择核心网设备的方法，包括：接入网节点接收终端发送的接入层消息，接入层消息包括NAS请求消息和网络选择辅助参数，接入网节点根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，根据至少一个移动管理设备组的组标识确定目标移动管理设备的设备标识，配置信息包括网络选择辅助参数与移动管理设备组的组标识的对应关系；接入网节点向目标移动管理设备的设备标识指示的移动管理设备发送NAS请求消息。因此，采用本申请实施例提供的方法能够有效避免重定向的过程，减少了各个网络设备之间的信令交互，降低了终端入网时延。
在一种可能的设计中，网络选择辅助参数包括移动管理设备的类型，配置信息包括移 动管理设备的类型与移动管理设备组的组标识的对应关系；接入网节点根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，包括：接入网节点根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。因此，当匹配移动管理设备的类型时，匹配成功率较高，接入网节点可以比较容易为终端选择出一个移动管理设备。
在一种可能的设计中，网络选择辅助参数包括至少一个切片类型，配置信息包括切片类型与移动管理设备组的组标识的对应关系；接入网节点根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，包括：接入网节点根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。因此，当匹配切片类型时，匹配成功率较高，接入网节点可以比较容易为终端选择出一个移动管理设备。
在一种可能的设计中，网络选择辅助参数包括移动管理设备的类型和至少一个切片类型；配置信息包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系；配置信息还包括指示信息，指示信息指示接入网节点根据指示接入网节点根据网络选择辅助参数选择移动管理设备组；接入网节点根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，包括：当指示信息指示接入网节点根据网络选择辅助参数中的移动管理设备的类型选择移动管理设备组时，接入网节点根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识；或者，当指示信息指示接入网节点根据网络选择辅助参数中的至少一个切片类型选择移动管理设备组时，接入网节点根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识；或者，当指示信息指示接入网节点根据网络选择辅助参数中的移动管理设备的类型和至少一个切片类型选择移动管理设备组时，接入网节点根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组；接入网节点根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第二组标识组；接入网节点根据第一组标识组与第二组标识组的交集或并集确定至少一个移动管理设备组的组标识。因此，接入网节点根据指示信息确定匹配规则，匹配方式更加灵活。
在一种可能的设计中，网络选择辅助参数包括移动管理设备的类型和至少一个切片类型；配置信息包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系；接入网节点根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，包括：接入网节点根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组；接入网节点根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第二组标识组；接入网节点根据第一组标识组与第二组标识组的交集或并集确定至少一个移动管理设备组的组标识；或者，当接入网节点根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组时，不再根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，将第一组标识组中包括的至少一个移动管理设备组的组标识作为最终确定的至少一个移动管理设备组的组标识。因此，接入网节 点根据预设的匹配规则灵活选择根据哪个或哪几个网络选择辅助参数查询配置信息，匹配方式更加灵活，匹配效率更高。
在一种可能的设计中，至少一个切片类型包括一个缺省的切片类型，缺省的切片类型由终端指定或由网络配置设定；接入网节点根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识，包括：接入网节点根据缺省的切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。因此，根据缺省的切片类型确定移动管理设备组的组标识，能够有效满足终端的基本需求，降低了终端入网时延。
在一种可能的设计中，配置信息是由各个移动管理设备发送给接入网节点，或由网络管理设备为接入网节点配置的。因此，接入网节点可通过多种方式获得配置信息，更加灵活。
在一种可能的设计中，接入网节点根据至少一个移动管理设备的组标识确定目标移动管理设备的设备标识，包括：接入网节点从至少一个移动管理设备组中选取出目标移动管理设备组，对目标移动管理设备组中的各个移动管理设备执行NAS节点选择功能确定目标移动管理设备的设备标识。因此，接入网节点可通过现有技术确定目标移动管理设备的设备标识，与现有技术的兼容性较好。
在一种可能的设计中，配置信息还包括每个移动管理设备组对应于移动管理设备类型的权重信息；接入网节点从至少一个移动管理设备组中选取出目标移动管理设备组，包括：接入网节点根据至少一个移动管理设备组中每个移动管理设备组对应于移动管理设备类型的权重信息，从至少一个移动管理设备组中选取出目标移动管理设备组。因此，接入网节点根据至少一个移动管理设备组中每个移动管理设备组对应于移动管理设备类型的权重信息确定目标移动管理设备组，以保障各个移动管理设备组的负载均衡。
在一种可能的设计中，配置信息还包括每个移动管理设备组对应于切片类型的权重信息；至少一个切片类型包括一个缺省的切片类型，缺省的切片类型由终端指定或由网络配置设定；接入网节点从至少一个移动管理设备组中选取出目标移动管理设备组，包括：接入网节点根据至少一个移动管理设备组中每个移动管理设备组对应于缺省的切片类型的权重信息，从至少一个移动管理设备组中选取出目标移动管理设备组。接入网节点根据至少一个移动管理设备组中每个移动管理设备组对应于缺省的切片类型的权重信息确定目标移动管理设备组，以保障各个移动管理设备组的负载均衡。
第二方面，本申请提供一种选择核心网设备的装置，用于执行上述第一方面或第一方面的任意可能的设计的方法。具体地，该装置包括用于执行上述第一方面或第一方面的任意可能的设计的方法的单元。
第三方面，本申请提供一种接入网节点，包括收发器、处理器和存储器。其中，收发器、处理器以及所述存储器之间可以通过总线系统相连。该存储器用于存储程序、指令或代码，所述处理器用于执行所述存储器中的程序、指令或代码，以完成上述第一方面或第一方面的任意可能的实现方式中的方法。
第四方面，本发明实施例提供了一种通信系统，该系统包括上述第三方面所述的接入网节点，可选的，该系统还可以包括本申请实施例提供的方案中与所述接入网节点进行交互的其他设备。
第五方面，本申请提供了一种计算机可读存储介质，所述计算机可读存储介质中存储 有指令，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面的任意可能的设计的方法。
第六方面，本申请还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
图1为本申请背景技术中终端接入专营核心网的流程图；
图2为本申请实施例中选择核心网设备的应用场景示意图；
图3为本申请实施例中选择核心网设备的概述流程图；
图4为本申请实施例中接入网节点确定至少一个移动管理设备组的组标识的第一种实现方式具体流程图；
图5为本申请实施例中接入网节点确定至少一个移动管理设备组的组标识的第二种实现方式具体流程图；
图6为本申请实施例中配置信息包括每个移动管理设备组对应于切片类型的权重信息时确定目标移动管理设备组的具体流程图；
图7为本申请实施例中接入网节点确定至少一个移动管理设备组的组标识的第三种实现方式具体流程图；
图8为本申请实施例中选择核心网设备的装置的结构示意图；
图9为本申请实施例中接入网节点的结构示意图。
具体实施方式
下面结合附图，对本申请的实施例进行描述。
图2为本申请的具体应用场景示意图。须知，图2中的核心网网络切片实例仅为举例，不作为本申请的限定。
具体的，运营商网络部署了四个核心网网络切片实例，分别针对于增强型移动互联网(Enhance Mobile Broadband，eMBB)，泛在物联网(Massive Internet of Things，mIoT)，车对外界的信息交换(Vehicle to X，V2X)，和超高可靠性与超低时延通信(Ultra Reliable&Low Latency Communication，uRLLC)四种商业场景。其中，eMBB和mIoT的核心网网络切片实例存在共享的控制面功能，记为Common CP 1。V2X和URLLC的核心网网络切片实例也存在一个共享的控制面功能，记为Common CP 2。RAN Node被所有的核心网网络切片实例共享。
基于图2的应用场景，UE1具备同时接入eMBB和mIoT的业务需求时，可通过RAN Node首先接入Common CP 1，UE2具备同时接入V2X和URLLC的业务需求时，可通过RAN Node首先接入Common CP 2。
本申请中的终端为支持5G网络的终端设备，但本申请能够应用的终端不受限于此，还可以应用于所有种类的终端设备，包括手机、物联网设备，智能家居设备，工业控制设备，车辆设备等。本申请中的RAN Node为接入网节点，可以是3GPP无线接入网节点，也可以是非3GPP的接入点，比如Wi-Fi接入点，或固网接入点。
图2中，切片实例共享部分(Slice instance Common Part)是指一个或多个切片实例共 享的控制面设备或网络功能，例如移动性管理设备或网络功能(Mobility Management Function，MMF)。切片实例独享部分(Slice instance Dedicated Part)是指核心网切片实例独享的控制面设备或网络功能，例如会话管理设备或网络功能(Session Management Function，SMF)。本申请实施例为简单起见，仅以MMF代表Slice instance Common Part，以SMF代表Slice Instance Dedicated Part，不作为本申请的限定。
参阅图3所示，本申请实施例提供一种选择核心网设备的方法，包括：
步骤300：接入网节点接收终端发送的消息，接入层消息包括非接入层(Non Access Stratum，NAS)请求消息和网络选择辅助参数；网络选择辅助参数用于指示接入网节点为终端选择移动管理设备。
应理解的是，这里的接入层消息可以为无线资源控制(Radio Resource Control，RRC)消息。
步骤310：接入网节点根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，配置信息包括网络选择辅助参数与移动管理设备组的组标识的对应关系。
步骤320：接入网节点根据至少一个移动管理设备组的组标识确定目标移动管理设备的设备标识。
步骤330：接入网节点向目标移动管理设备的设备标识指示的移动管理设备发送NAS请求消息。
在一种可能的设计中，在执行步骤300之前，接入网节点获取配置信息，具体的，配置信息是由各个移动管理设备发送给接入网节点，或由网络管理设备为接入网节点配置的。
针对步骤320，在一种可能的设计中，接入网节点根据至少一个移动管理设备的组标识确定目标移动管理设备的设备标识可以采用如下方法：接入网节点从至少一个移动管理设备组中选取出目标移动管理设备组。然后，接入网节点对目标移动管理设备组中的各个移动管理设备执行NAS节点选择功能确定目标移动管理设备的设备标识。
具体的，移动管理设备组中的各个移动管理设备将自身的权重信息配置给接入网节点，接入网节点根据负载均衡原则确定一个移动管理设备。例如，一个移动管理设备组中包括三个移动管理设备A1、A2、A3，A1、A2、A3的权重信息分别为10％、60％、30％，因此，每10个分配至该移动管理设备组的NAS请求消息中，RAN Node将1个NAS请求消息分配给A1，6个NAS请求消息分配给A2，3个NAS请求消息分配给A3。
应理解的是，本申请中提到的移动管理设备的类型用于指示移动管理设备的处理机制或行为，以支持一个或多个切片所提供的功能和服务，例如，Type of MMF、AMF Type。切片类型用于指示网络切片的处理机制或行为，以支持切片所提供的功能和服务，例如，Type of SMF，Slice Type，Service Type。移动管理设备组的组标识可以用MMF Group ID表示。移动管理设备的设备标识可以用MMF Instance ID表示。每个移动管理设备的设备标识可以在该移动管理设备向接入网节点发送配置信息时携带，或者，网络管理设备为接入网节点配置配置信息时携带。此外，终端可以通过移动管理设备获得移动管理设备的类型和/或切片类型，或者，终端提前配置好移动管理设备的类型和/或切片类型。应理解的是，本申请中提到的移动管理设备也可以是接入和移动性管理设备(Core Access and Mobility Management Function，AMF)。移动管理设备的类型也可以是AMF Type，相应的，移动管理设备组的组标识可以用AMF Group ID表示，移动管理设备的设备标识可以用AMF Instance ID表示。
下面针对本申请实施例中步骤310的几种可能实现方式进行说明。
第一种实现方式：网络选择辅助参数包括移动管理设备的类型，配置信息包括移动管理设备的类型与移动管理设备组的组标识的对应关系。
此时，针对步骤310，接入网节点根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。
移动管理设备的类型与移动管理设备组的组标识的对应关系如表1所示。
表1
Figure PCTCN2017077586-appb-000001
表1中的移动管理设备的类型给出字段eMBB+mIoT和V2X+URLLC，只是为了便于理解，实际实现时可能采用数值或标量的方式表示，例如用C001代表eMBB+mIoT，D001代表eMBB，D002代表mIoT等。需理解，表1列出的多种信息仅是例举，并不对本申请构成限定。
下面以图4为例说明第一种实现方式的具体实现流程。
S401：RAN Node接收MMF 1和MMF 2发送的配置消息。
具体的，在RAN Node与MMF的接口配置过程中，RAN Node当前连接的MMF，如图4包括MMF 1和MMF 2，MMF 1和MMF 2分别向RAN Node发送配置消息，MMF1发送的配置消息中包括MMF1支持的Type of MMF与MMF Group ID的对应关系，MMF2发送的配置消息中包括MMF2支持的Type of MMF与MMF Group ID的对应关系，如表1所示。这里假设MMF 1Group仅包括一个移动管理设备MMF1，MMF 1Group仅包括一个移动管理设备MMF2。当MMF 1Group包括多个移动管理设备时，MMF 1Group中的每个移动管理设备都会向RAN Node发送配置信息，RAN Node统计发送相同配置信息的MMF的数量，获知MMF 1Group包括的MMF数量和每个MMF的Instance ID。须知这里仅以各MMF将配置信息发送给RAN Node为例进行说明，还可以通过网络管理设备为RAN Node提前配置各个配置信息。
S402：UE向RAN Node发送RRC消息，其中包括NAS请求消息和Type of MMF，例如Type of MMF为eMBB+mIoT。
S402具体可参考步骤300。
S403：RAN Node根据UE提供的Type of MMF查询配置信息，即表1，得到MMF 1Group ID。
S403具体可参考第一种实现方式。
S404：RAN Node根据MMF 1Group ID执行NAS节点选择功能获得MMF 1Instance ID。
S404具体可参考步骤320。
S405：RAN Node向MMF 1Instance ID指示的MMF转发UE的NAS请求消息。
S405具体可参考步骤330。
S406：MMF 1向UE发送NAS接受消息(NAS accept)，其中包括Type of MMF。该NAS信息可能与UE提供Type of MMF一致，也可能不一致，例如MMF 1需要更新Type of MMF。
须知，当RAN Node未能根据UE提供的Type of MMF从配置信息中查询到匹配的MMF Group时，RAN Node可根据缺省的MMF Group，执行NAS节点选择功能获得一个MMF Instance ID，向该MMF Instance ID指示的MMF转发UE的NAS请求消息。应理解的是，NAS节点选择功能与现有技术一致，重复之处不再赘述。
此外，此时的网络选择辅助参数还可包括至少一个切片类型，配置信息还包括切片类型与移动管理设备组的组标识的对应关系。当RAN Node未能根据UE提供的Type of MMF从配置信息中查询到匹配的MMF Group时，RAN Node可以根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识，具体参阅第二种实现方式。
进一步地，在一种可能的设计中，配置信息还包括每个移动管理设备组对应于移动管理设备类型的权重信息，此时接入网节点从至少一个移动管理设备组中选取出目标移动管理设备组可以采用以下方法：接入网节点根据至少一个移动管理设备组中每个移动管理设备组对应于移动管理设备类型的权重信息，从至少一个移动管理设备组中选取出目标移动管理设备组。
例如，确定出三个移动管理设备组分别为G1、G2、G3，这三个移动管理设备的类型相同，G1、G2、G3对应于移动管理设备类型的权重信息分别为20％、50％、30％，因此，每10个分配至该种类型移动管理设备组的NAS请求消息中，RAN Node将2个NAS请求消息分配给G1，5个NAS请求消息分配给G2，3个NAS请求消息分配给G3。
第二种实现方式：网络选择辅助参数包括至少一个切片类型，配置信息包括切片类型与移动管理设备组的组标识的对应关系。
此时，针对步骤310，接入网节点根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。
切片类型和移动管理设备组的组标识的对应关系如表2所示。
表2
Figure PCTCN2017077586-appb-000002
需理解，表2列出的多种信息仅是例举，并不对本申请构成限定。
上述图4所示的实施例中，RAN Node根据Type of MMF为UE选择MMF。但在某些情况下，例如漫游场景或跨省场景，运营商很可能没有部署这种共享类型的MMF。这样RAN Node就无法根据Type of MMF来进行选择。此时，采用如图5所述的实施例就能实现为终端选择MMF。
下面以图5为例说明第二种实现方式的具体实现流程。
S501：RAN Node接收MMF 1和MMF 2发送的配置消息。
具体的，在RAN Node与MMF的接口配置过程中，RAN Node当前连接的MMF，如图5包括MMF 1和MMF 2，MMF 1和MMF 2分别向RAN Node发送配置消息，MMF1发送的配置消息中包括MMF1支持的Type of SMF与MMF Group ID的对应关系，MMF2发送的配置 消息中包括MMF2支持的Type of SMF与MMF Group ID的对应关系，如表2所示。须知这里仅以各MMF将配置信息发送给RAN Node为例进行说明，还可以通过网络管理设备为RAN Node提前配置各个配置信息。
S502：UE向RAN Node发送RRC消息，其中包括NAS请求消息和Type of SMF，例如Type of SMF为eMBB。
S502具体可参考步骤300。
S503：RAN Node根据UE提供的Type of SMF查询配置信息，即表2，得到MMF 1Group ID。
S503具体可参考第二种实现方式。
S504：RAN Node根据MMF 1Group ID执行NAS节点选择功能获得MMF 1Instance ID。
S504具体可参考步骤320。
S505：RAN Node向MMF 1Instance ID指示的MMF转发UE的NAS请求消息。
S505具体可参考步骤330。
S506：MMF1向UE发送NAS接受消息，其中包括Type of MMF。
因此，通过S506，UE可以获得移动管理设备的类型，下次UE发送向RAN Node发送接入层消息时，RRC可以包括NAS请求消息和Type of MMF。
此外，此时的网络选择辅助参数还可包括移动管理设备的类型，配置信息包括移动管理设备的类型与移动管理设备组的组标识的对应关系，当RAN Node未能根据UE提供的Type of SMF从配置信息中查询到匹配的MMF Group时，RAN Node可以根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识，具体参阅第一种实现方式。
进一步地，在一种可能的设计中，至少一个切片类型包括一个缺省的切片类型，缺省的切片类型由终端指定或由网络配置设定。针对步骤310，接入网节点根据缺省的切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。此时，考虑到需首先满足终端接入缺省的切片类型的切片的需求，根据缺省的切片类型，为终端确定至少一个移动管理设备组的组标识。
例如，UE向RAN Node发送RRC消息，其中包括NAS请求消息和Type of SMF，其中，Type of SMF包括eMBB和V2X，eMBB为缺省的切片类型，由于运营商可能没有部署eMBB+V2X这种共享类型的MMF，此时接入网节点可能无法找到同时支持eMBB和V2X的MMF。因此，当eMBB为缺省的切片类型时，接入网节点可根据eMBB查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。这里的eMBB为缺省的切片类型可以由终端指定或由网络配置设定。
此外，在一种可能的设计中，配置信息还包括每个移动管理设备组对应于切片类型的权重信息。此时，接入网节点从至少一个移动管理设备组中选取出目标移动管理设备组，可根据至少一个移动管理设备组中每个移动管理设备组对应于缺省的切片类型的权重信息，从至少一个移动管理设备组中选取出目标移动管理设备组。
如图6所示，说明配置信息还包括每个移动管理设备组对应于切片类型的权重信息时，如何确定目标移动管理设备组。
S601：RAN Node接收MMF 1、MMF 2、MMF3发送的配置消息，如表3所示，此外，每个MMF发送的配置信息中还包括该MMF对应于切片类型的权重信息,例如图6中的负载 信息(Weight Factor per SMF type)。
表3
Figure PCTCN2017077586-appb-000003
S602：UE向RAN Node发送RRC消息，其中包括NAS请求消息和Type of SMF，例如Type of SMF为eMBB。
S602具体可参考步骤300。
S603：RAN Node根据UE提供的Type of SMF查询配置信息，即表3，得到MMF 1Group ID和MMF 3Group ID。
S603具体可参考步骤310。
S604：RAN Node根据MMF 1Group ID和MMF 3Group ID分别对应于eMBB的权重信息，即weight factor，选择MMF 3Group ID。
具体的，假设MMF 1设定eMBB的weight factor为3，MMF 2设定eMBB的weight factor为7，那么RAN Node将占总数30％的eMBB业务交由MMF 1处理，将占总数70％的eMBB业务交由MMF 3处理。
S605：RAN Node根据MMF 3Group ID执行NAS节点选择功能获得MMF 3Instance ID。
S604和S605具体可参考步骤320。
S606：RAN Node向MMF 3Instance ID指示的MMF转发UE的NAS请求消息。
S606具体可参考步骤330。
S607：MMF3向UE发送NAS接受消息，其中包括Type of MMF。
上述实施例中，Type of SMF包括一种切片类型，可直接作为缺省的切片类型。当Type of SMF包括多个切片类型时，需要确定缺省的切片类型，根据Type of SMF包括eMBB和URLLC，根据eMBB查询表3得到MMF 1Group ID和MMF 3Group ID，根据URLLC查询表3得到MMF 2Group ID，当eMBB为缺省的切片类型时，采用如图6所示的方法确定MMF，当URLLC为缺省的切片类型时，RAN Node根据MMF 2Group ID执行NAS节点选择功能获得目标移动管理设备的设备标识。或者，由于Type of SMF包括eMBB和URLLC，首先根据缺省的切片类型查询表3，确定至少一个移动管理设备组的组标识，然后再根据如图6所示的方法进一步确定目标移动设备组的组标识。
第三种实现方式：网络选择辅助参数包括移动管理设备的类型和至少一个切片类型；配置信息包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系；配置信息还包括指示信息，指示信息指示接入网节点根据网络选择辅助参数选择移动管理设 备组；
应理解的是，这里的配置信息可以包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系三者之间的对应关系，又或者，这里的配置信息可以包括移动管理设备的类型与移动管理设备组的组标识两者之间的对应关系，以及切片类型与移动管理设备组的组标识两者之间的对应关系。
根据指示信息的不同，这里又可具体分为三种情况：
第一种情况：当指示信息指示接入网节点根据网络选择辅助参数中的移动管理设备的类型选择移动管理设备组时，接入网节点根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。
第一种情况的具体实现方法与第一种实现方式一致。
第二种情况：当指示信息指示接入网节点根据网络选择辅助参数中的至少一个切片类型选择移动管理设备组时，接入网节点根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识；
第二种情况的具体实现方法与第二种实现方式一致。
第三种情况：当指示信息指示接入网节点根据网络选择辅助参数中的移动管理设备的类型和至少一个切片类型选择移动管理设备组时，接入网节点根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组；接入网节点根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第二组标识组；接入网节点根据第一组标识组与第二组标识组的交集或并集确定至少一个移动管理设备组的组标识。
须知，针对第三种情况，接入网节点确定第一组标识组合第二组标识组的次序不作限定。
表4
Figure PCTCN2017077586-appb-000004
如表4所示，配置信息包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系。
例如，UE向RAN Node发送RRC消息，其中包括NAS请求消息，和Type of SMF和Type of MMF，Type of MMF为eMBB+mIoT，Type of SMF为eMBB。当指示信息指示接入网节点根据网络选择辅助参数中移动管理设备的类型和至少一个切片类型选择移动管理设备组时，RAN Node根据UE提供的Type of SMF查询配置信息，即表4，得到MMF 1Group ID和MMF 3Group ID。RAN Node根据UE提供的Type of MMF查询表4，得到MMF 1Group ID。 RAN Node根据上述查询结果取交集确定MMF 1Group ID为匹配度最高的MMF Group。
又例如，UE向RAN Node发送RRC消息，其中包括NAS请求消息，和Type of SMF和Type of MMF，Type of MMF为eMBB，Type of SMF为eMBB。当指示信息指示接入网节点根据网络选择辅助参数中的移动管理设备的类型和至少一个切片类型选择移动管理设备组时，RAN Node根据UE提供的Type of SMF查询配置信息，即表4，得到MMF 1Group ID和MMF3Group ID。RAN Node根据UE提供的Type of MMF查询表4，无法匹配到合适的MMF group，因为，在实际应用中，各个Type of MMF通常用数值标量表示，eMBB+mIoT定义的值为003，eMBB定义的值为002。此时。RAN Node根据上述查询结果取不到交集，此时根据上述查询结果取并集，确定MMF 1Group ID和MMF 3Group ID为匹配度最高的MMF Group。进一步地，若配置信息还包括每个移动管理设备组对应于切片类型的权重信息时，接入网节点从至少一个移动管理设备组中选取出目标移动管理设备组。
应理解的是，该指示信息也可默认配置在RAN Node中，RAN Node根据默认的配置规则执行上述过程，不需要每个MMF发送的配置信息单独指示。
下面以图7为例说明第三种实现方式的具体实现流程。
S701：RAN Node接收MMF 1、MMF 2，MMF3分别发送的配置消息，如表4所示。此外，每个配置信息中还包括相同的指示信息。
S702：UE向RAN Node发送RRC消息，其中包括NAS请求消息、Type of SMF和Type of MMF，例如Type of MMF为eMBB+mIoT，Type of SMF为eMBB。
S702具体可参考步骤300。
S703：RAN Node根据指示信息确定根据哪个或哪几个网络选择辅助参数选择移动管理设备组，得到MMF1Group ID。
具体可以参考第三种实现方式：
例如，当指示信息指示RAN Node根据Type of MMF选择移动管理设备组时，RAN Node查询表4，得到MMF 1Group ID；
又例如，当指示信息指示RAN Node根据Type of SMF选择移动管理设备组时，RAN Node查询表4，得到MMF 1Group ID和MMF 3Group ID；
又例如，当指示信息指示RAN Node根据Type of SMF和Type of MMF选择移动管理设备组时，RAN Node查询表4，第一组标识组包括MMF 1Group ID，第二组标识组包括MMF1Group ID和MMF 3Group ID，RAN Node根据第一组标识组和第二组标识组取交集，得到MMF 1Group ID，或者，根据第一组标识组和第二组标识组取并集，得到MMF 1Group ID和MMF 3Group ID。
须知，这里仅以最终确定MMF 1Group ID为例进行说明，还可以为MMF 3Group ID。
S704：RAN Node根据MMF 1Group ID执行NAS节点选择功能获得MMF 1Instance ID。
S704具体可参考步骤320。
S705：RAN Node向MMF 1Instance ID指示的MMF转发UE的NAS请求消息。
S505具体可参考步骤330。
S706：MMF1向UE发送NAS接受消息，其中包括Type of MMF。
第四种实现方式：网络选择辅助参数包括移动管理设备的类型和至少一个切片类型；配置信息包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系；
此时，针对步骤310，具体又可分为以下两种情况：
第一种情况：接入网节点根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组；接入网节点根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第二组标识组；接入网节点根据第一组标识组与第二组标识组的交集或并集确定至少一个移动管理设备组的组标识。
第一种情况的具体实现方法与第三种实现方式中第三种情况一致，只是无需MMF发送指示信息。
第二种情况：当接入网节点根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组时，不再根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，将第一组标识组中包括的至少一个移动管理设备组的组标识作为最终确定的至少一个移动管理设备组的组标识。
因此，接入网节点可先根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，若查询到至少一个移动管理设备组的组标识，则无需再次根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，因此，匹配方式更加简便灵活，匹配效率更高。
应理解的是，接入网节点还可先根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，若查询到至少一个移动管理设备组的组标识，则无需再次根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，因此，优先匹配移动管理设备的类型还是切片类型，可根据实际网络需要灵活进行配置。
基于同一构思，本申请还提供了一种选择核心网设备的装置，该装置可以用于执行上述图3中接入网节点设备执行的步骤，因此本申请实施例提供的选择核心网设备的装置的实施方式可以参见该方法的实施方式。
例如，参阅图8所示，一种选择核心网设备的装置，包括：
接收单元810，用于接收终端发送的无线资源控制接入层消息，接入层消息包括非接入层NAS请求消息和网络选择辅助参数；
处理单元820，用于根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，配置信息包括网络选择辅助参数与移动管理设备组的组标识的对应关系；以及根据至少一个移动管理设备组的组标识确定目标移动管理设备的设备标识；
发送单元830，用于向目标移动管理设备的设备标识指示的移动管理设备发送NAS请求消息。
在一种可能的设计中，网络选择辅助参数包括移动管理设备的类型，配置信息包括移动管理设备的类型与移动管理设备组的组标识的对应关系；
根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识时，处理单元820，具体用于：
根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。
在一种可能的设计中，网络选择辅助参数包括至少一个切片类型，配置信息包括切片类型与移动管理设备组的组标识的对应关系；
根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识时，处 理单元820，具体用于：
根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。
在一种可能的设计中，网络选择辅助参数包括移动管理设备的类型和至少一个切片类型；配置信息包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系；配置信息还包括指示信息，指示信息指示接入网节点根据指示信息指示的网络选择辅助参数查询配置信息；
根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识时，处理单元820，具体用于：
当指示信息指示网络选择辅助参数中包括的移动管理设备的类型时，根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识；
或者，当指示信息指示网络选择辅助参数中包括的至少一个切片类型时，根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识；
或者，当指示信息指示网络选择辅助参数中包括的移动管理设备的类型和至少一个切片类型时，根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组；根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第二组标识组；根据第一组标识组与第二组标识组的交集或并集确定至少一个移动管理设备组的组标识。
在一种可能的设计中，网络选择辅助参数包括移动管理设备的类型和至少一个切片类型；配置信息包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系；
根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识时，处理单元820，具体用于：
根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组；根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第二组标识组；根据第一组标识组与第二组标识组的交集或并集确定至少一个移动管理设备组的组标识；
或者，根据移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组时，不再根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，将第一组标识组中包括的至少一个移动管理设备组的组标识作为最终确定的至少一个移动管理设备组的组标识。
在一种可能的设计中，至少一个切片类型包括一个缺省的切片类型，缺省的切片类型由终端指定或由网络配置设定；
根据至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识时，处理单元820，具体用于：
根据缺省的切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少 一个移动管理设备组的组标识。
在一种可能的设计中，配置信息是由各个移动管理设备发送给装置，或由网络管理设备为装置配置的。
在一种可能的设计中，根据至少一个移动管理设备的组标识确定目标移动管理设备的设备标识时，处理单元820，具体用于：
从至少一个移动管理设备组中选取出目标移动管理设备组；
对目标移动管理设备组中的各个移动管理设备执行NAS节点选择功能确定目标移动管理设备的设备标识。
在一种可能的设计中，配置信息还包括每个移动管理设备组对应于移动管理设备类型的权重信息；
从至少一个移动管理设备组中选取出目标移动管理设备组时，处理单元820，具体用于：
根据至少一个移动管理设备组中每个移动管理设备组对应于移动管理设备类型的权重信息，从至少一个移动管理设备组中选取出目标移动管理设备组。
在一种可能的设计中，配置信息还包括每个移动管理设备组对应于切片类型的权重信息；至少一个切片类型包括一个缺省的切片类型，缺省的切片类型由终端指定或由网络配置设定；
从至少一个移动管理设备组中选取出目标移动管理设备组时，处理单元820，具体用于：
根据至少一个移动管理设备组中每个移动管理设备组对应于缺省的切片类型的权重信息，从至少一个移动管理设备组中选取出目标移动管理设备组。
应理解的是，上述单元的具体划分仅作为举例，不做为本申请的限定。
基于同一构思，本申请还提供了一种接入网节点，该设备可以用于执行上述图3中接入网节点执行的步骤，因此本申请实施例提供的接入网节点的实施方式可以参见该方法的实施方式，重复之处不再赘述。
参阅图9所示，本申请实施例提供一种接入网节点900，该设备包括收发器910，处理器920和存储器930，其中，收发器910、处理器920以及存储器930之间可以通过总线系统相连。该存储器930用于存储程序、指令或代码，处理器920用于执行存储器930中的程序、指令或代码，以具体执行：通过收发器910接收终端发送的无线资源控制接入层消息，接入层消息包括非接入层NAS请求消息和网络选择辅助参数；根据网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，配置信息包括网络选择辅助参数与移动管理设备组的组标识的对应关系；以及根据至少一个移动管理设备组的组标识确定目标移动管理设备的设备标识；通过收发器910向目标移动管理设备的设备标识指示的移动管理设备发送NAS请求消息。
需要说明的是，一个具体的实施方式中，图8中的接收单元810和发送单元830的功能可以用图9中的收发器910实现，图8中的处理单元820的功能可以用图9中的处理器920实现。
因此，采用本申请实施例提供的方法能够有效避免重定向的过程，减少了各个网络设备之间的信令交互，降低了终端入网时延。特别地，当只匹配Type of MMF或者Type of SMF时，匹配成功率较高，接入网节点可以比较容易为终端选择出一个移动管理设备，但可能无法完全满足终端的接入需求。当匹配Type of MMF和Type of SMF时，匹配成功率较低， 接入网节点可以无法地为终端选择出一个满足条件的移动管理设备，此时可以设置一个缺省的移动管理设备，或从第一组标识组或第二组标识组中选择一个移动管理设备组的组标识。
此外，相较于现有技术中，终端只可以接入一个核心网网络切片实例，无法满足一些复杂终端还具有同时接入多个核心网网络切片实例的能力与需求，采用本申请实施例提供的方法，能够支持终端同时接入多个核心网网络切片实例的场景。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本申请实施例是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (20)

  1. 一种选择核心网设备的方法，其特征在于，包括：
    接入网节点接收终端发送的无线资源控制接入层消息，所述接入层消息包括非接入层NAS请求消息和网络选择辅助参数；
    所述接入网节点根据所述网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，所述配置信息包括网络选择辅助参数与移动管理设备组的组标识的对应关系；
    所述接入网节点根据所述至少一个移动管理设备组的组标识确定目标移动管理设备的设备标识；
    所述接入网节点向所述目标移动管理设备的设备标识指示的移动管理设备发送所述NAS请求消息。
  2. 如权利要求1所述的方法，其特征在于，所述网络选择辅助参数包括移动管理设备的类型，所述配置信息包括移动管理设备的类型与移动管理设备组的组标识的对应关系；
    所述接入网节点根据所述网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，包括：
    所述接入网节点根据所述移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。
  3. 如权利要求1所述的方法，其特征在于，所述网络选择辅助参数包括至少一个切片类型，所述配置信息包括切片类型与移动管理设备组的组标识的对应关系；
    所述接入网节点根据所述网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，包括：
    所述接入网节点根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。
  4. 如权利要求1所述的方法，其特征在于，所述网络选择辅助参数包括移动管理设备的类型和至少一个切片类型；所述配置信息包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系；所述配置信息还包括指示信息，所述指示信息指示所述接入网节点根据所述网络选择辅助参数选择移动管理设备组；
    所述接入网节点根据所述网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，包括：
    当所述指示信息指示所述接入网节点根据所述网络选择辅助参数中的移动管理设备的类型选择移动管理设备组时，所述接入网节点根据所述移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识；
    或者，当所述指示信息指示所述接入网节点根据所述网络选择辅助参数中的至少一个切片类型选择移动管理设备组时，所述接入网节点根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识；
    或者，当所述指示信息指示所述网络选择辅助参数中包括的移动管理设备的类型和至少一个切片类型选择移动管理设备组时，所述接入网节点根据所述移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设 备组的组标识作为第一组标识组；所述接入网节点根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第二组标识组；所述接入网节点根据所述第一组标识组与所述第二组标识组的交集或并集确定至少一个移动管理设备组的组标识。
  5. 如权利要求1所述的方法，其特征在于，所述网络选择辅助参数包括移动管理设备的类型和至少一个切片类型；所述配置信息包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系；
    所述接入网节点根据所述网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，包括：
    所述接入网节点根据所述移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组；所述接入网节点根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第二组标识组；所述接入网节点根据所述第一组标识组与所述第二组标识组的交集或并集确定至少一个移动管理设备组的组标识；
    或者，当所述接入网节点根据所述移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组时，不再根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，将所述第一组标识组中包括的至少一个移动管理设备组的组标识作为最终确定的至少一个移动管理设备组的组标识。
  6. 如权利要求3-5任一项所述的方法，其特征在于，所述至少一个切片类型包括一个缺省的切片类型，所述缺省的切片类型由所述终端指定或由网络配置设定；
    所述接入网节点根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识，包括：
    所述接入网节点根据所述缺省的切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。
  7. 如权利要求1-6任一所述的方法，其特征在于，所述配置信息是由各个移动管理设备发送给所述接入网节点，或由网络管理设备为所述接入网节点配置的。
  8. 如权利要求1-7任一所述的方法，其特征在于，所述接入网节点根据所述至少一个移动管理设备的组标识确定目标移动管理设备的设备标识，包括：
    所述接入网节点从所述至少一个移动管理设备组中选取出目标移动管理设备组；
    所述接入网节点对目标移动管理设备组中的各个移动管理设备执行NAS节点选择功能确定目标移动管理设备的设备标识。
  9. 如权利要求8所述的方法，其特征在于，所述配置信息还包括每个移动管理设备组对应于移动管理设备类型的权重信息；
    所述接入网节点从所述至少一个移动管理设备组中选取出目标移动管理设备组，包括：
    所述接入网节点根据所述至少一个移动管理设备组中每个移动管理设备组对应于移动管理设备类型的权重信息，从所述至少一个移动管理设备组中选取出目标移动管理设备组。
  10. 如权利要求8所述的方法，其特征在于，所述配置信息还包括每个移动管理设备 组对应于切片类型的权重信息；所述至少一个切片类型包括一个缺省的切片类型，所述缺省的切片类型由所述终端指定或由网络配置设定；
    所述接入网节点从所述至少一个移动管理设备组中选取出目标移动管理设备组，包括：
    所述接入网节点根据所述至少一个移动管理设备组中每个移动管理设备组对应于所述缺省的切片类型的权重信息，从所述至少一个移动管理设备组中选取出目标移动管理设备组。
  11. 一种选择核心网设备的装置，其特征在于，包括：
    接收单元，用于接收终端发送的无线资源控制接入层消息，所述接入层消息包括非接入层NAS请求消息和网络选择辅助参数；
    处理单元，用于根据所述网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识，所述配置信息包括网络选择辅助参数与移动管理设备组的组标识的对应关系；以及根据所述至少一个移动管理设备组的组标识确定目标移动管理设备的设备标识；
    发送单元，用于向所述目标移动管理设备的设备标识指示的移动管理设备发送所述NAS请求消息。
  12. 如权利要求11所述的装置，其特征在于，所述网络选择辅助参数包括移动管理设备的类型，所述配置信息包括移动管理设备的类型与移动管理设备组的组标识的对应关系；
    根据所述网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识时，所述处理单元，具体用于：
    根据所述移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。
  13. 如权利要求11所述的装置，其特征在于，所述网络选择辅助参数包括至少一个切片类型，所述配置信息包括切片类型与移动管理设备组的组标识的对应关系；
    根据所述网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识时，所述处理单元，具体用于：
    根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。
  14. 如权利要求11所述的装置，其特征在于，所述网络选择辅助参数包括移动管理设备的类型和至少一个切片类型；所述配置信息包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系；所述配置信息还包括指示信息，所述指示信息指示所述接入网节点根据所述网络选择辅助参数选择移动管理设备组；
    根据所述网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识时，所述处理单元，具体用于：
    当所述指示信息指示所述接入网节点根据所述网络选择辅助参数中的移动管理设备的类型选择移动管理设备组时，根据所述移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识；
    或者，当所述指示信息指示所述接入网节点根据所述网络选择辅助参数中的至少一个切片类型选择移动管理设备组时，根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识；
    或者，当所述指示信息指示所述接入网节点根据所述网络选择辅助参数中的移动管理设备的类型和至少一个切片类型选择移动管理设备组时，根据所述移动管理设备的类型查 询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组；根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第二组标识组；根据所述第一组标识组与所述第二组标识组的交集确定至少一个移动管理设备组的组标识。
  15. 如权利要求11所述的装置，其特征在于，所述网络选择辅助参数包括移动管理设备的类型和至少一个切片类型；所述配置信息包括移动管理设备的类型、切片类型和移动管理设备组的组标识的对应关系；
    根据所述网络选择辅助参数查询配置信息，确定至少一个移动管理设备组的组标识时，所述处理单元，具体用于：
    根据所述移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组；根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第二组标识组；根据所述第一组标识组与所述第二组标识组的交集或并集确定至少一个移动管理设备组的组标识；
    或者，根据所述移动管理设备的类型查询移动管理设备的类型与移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识作为第一组标识组时，不再根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，将所述第一组标识组中包括的至少一个移动管理设备组的组标识作为最终确定的至少一个移动管理设备组的组标识。
  16. 如权利要求13-15所述的装置，其特征在于，所述至少一个切片类型包括一个缺省的切片类型，所述缺省的切片类型由所述终端指定或由网络配置设定；
    根据所述至少一个切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识时，所述处理单元，具体用于：
    根据所述缺省的切片类型查询切片类型和移动管理设备组的组标识的对应关系，确定至少一个移动管理设备组的组标识。
  17. 如权利要求11-16任一所述的装置，其特征在于，所述配置信息是由各个移动管理设备发送给所述装置，或由网络管理设备为所述装置配置的。
  18. 如权利要求11-17任一所述的装置，其特征在于，根据所述至少一个移动管理设备的组标识确定目标移动管理设备的设备标识时，所述处理单元，具体用于：
    从所述至少一个移动管理设备组中选取出目标移动管理设备组；
    对目标移动管理设备组中的各个移动管理设备执行NAS节点选择功能确定目标移动管理设备的设备标识。
  19. 如权利要求18所述的装置，其特征在于，所述配置信息还包括每个移动管理设备组对应于移动管理设备类型的权重信息；
    从所述至少一个移动管理设备组中选取出目标移动管理设备组时，所述处理单元，具体用于：
    根据所述至少一个移动管理设备组中每个移动管理设备组对应于移动管理设备类型的权重信息，从所述至少一个移动管理设备组中选取出目标移动管理设备组。
  20. 如权利要求18所述的装置，其特征在于，所述配置信息还包括每个移动管理设备组对应于切片类型的权重信息；所述至少一个切片类型包括一个缺省的切片类型，所述缺 省的切片类型由所述终端指定或由网络配置设定；
    从所述至少一个移动管理设备组中选取出目标移动管理设备组时，所述处理单元，具体用于：
    根据所述至少一个移动管理设备组中每个移动管理设备组对应于所述缺省的切片类型的权重信息，从所述至少一个移动管理设备组中选取出目标移动管理设备组。
PCT/CN2017/077586 2017-03-21 2017-03-21 一种选择核心网设备的方法及装置 WO2018170748A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2017/077586 WO2018170748A1 (zh) 2017-03-21 2017-03-21 一种选择核心网设备的方法及装置
CN201780088461.0A CN110431865B (zh) 2017-03-21 2017-03-21 一种选择核心网设备的方法及装置
EP17901991.4A EP3592016B1 (en) 2017-03-21 2017-03-21 Method and apparatus for selecting core network device
US16/577,878 US11129211B2 (en) 2017-03-21 2019-09-20 Core network device selection method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/077586 WO2018170748A1 (zh) 2017-03-21 2017-03-21 一种选择核心网设备的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/577,878 Continuation US11129211B2 (en) 2017-03-21 2019-09-20 Core network device selection method and apparatus

Publications (1)

Publication Number Publication Date
WO2018170748A1 true WO2018170748A1 (zh) 2018-09-27

Family

ID=63586245

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/077586 WO2018170748A1 (zh) 2017-03-21 2017-03-21 一种选择核心网设备的方法及装置

Country Status (4)

Country Link
US (1) US11129211B2 (zh)
EP (1) EP3592016B1 (zh)
CN (1) CN110431865B (zh)
WO (1) WO2018170748A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110994565A (zh) * 2019-12-02 2020-04-10 中国联合网络通信集团有限公司 一种继电保护方法及装置
CN112333058B (zh) * 2020-09-15 2023-06-30 深圳Tcl新技术有限公司 设备监控方法、装置、系统与计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100323695A1 (en) * 2009-06-18 2010-12-23 Nokia Siemens Networks Oy Mobile management entity operating in communications network and selection method therefor
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器
CN106375987A (zh) * 2015-07-22 2017-02-01 中兴通讯股份有限公司 一种网络切片的选择方法及系统
CN106412905A (zh) * 2016-12-12 2017-02-15 中国联合网络通信集团有限公司 网络切片选择方法、ue、mme和系统

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8331224B2 (en) * 2009-11-23 2012-12-11 Telefonaktiebolaget L M Ericsson (Publ) Self-management of mobility management entity (MME) pools
JP5421419B2 (ja) * 2012-03-28 2014-02-19 株式会社Ｎｔｔドコモ 基地局測位要求先決定装置
US9565572B2 (en) * 2012-07-23 2017-02-07 Lg Electronics Inc. Method for operating serving cell in wireless communication system to which carrier aggregation scheme is applied and device for same
WO2014052750A2 (en) * 2012-09-27 2014-04-03 Interdigital Patent Holdings, Inc. End-to-end architecture, api framework, discovery, and access in a virtualized network
KR101886748B1 (ko) * 2014-06-17 2018-08-08 후아웨이 테크놀러지 컴퍼니 리미티드 Mme 재선택 방법 및 mme
US10631356B2 (en) * 2015-01-13 2020-04-21 Nec Corporation Communication apparatus, core network node, system, computer program and methods for rerouting NAS-messages
US10327277B2 (en) * 2015-07-24 2019-06-18 Lg Electronics Inc. PDN connection establishment method and user equipment
US10425830B2 (en) * 2015-09-07 2019-09-24 Electronics And Telecommunications Research Institute Mobile communication network system and method for composing network component configurations
US10129108B2 (en) * 2015-11-13 2018-11-13 Huawei Technologies Co., Ltd. System and methods for network management and orchestration for network slicing
EP3446515B1 (en) * 2016-04-20 2020-12-02 Convida Wireless, LLC System information provisioning
US10447824B2 (en) * 2016-06-29 2019-10-15 Cisco Technology, Inc. Information centric networking for long term evolution
US10609635B2 (en) * 2017-03-10 2020-03-31 Hughes Network Systems, Llc Network sharing by multiple service providers in a 3GPP framework using single core network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100323695A1 (en) * 2009-06-18 2010-12-23 Nokia Siemens Networks Oy Mobile management entity operating in communications network and selection method therefor
CN106375987A (zh) * 2015-07-22 2017-02-01 中兴通讯股份有限公司 一种网络切片的选择方法及系统
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器
CN106412905A (zh) * 2016-12-12 2017-02-15 中国联合网络通信集团有限公司 网络切片选择方法、ue、mme和系统

Also Published As

Publication number Publication date
US11129211B2 (en) 2021-09-21
EP3592016B1 (en) 2021-09-22
US20200015290A1 (en) 2020-01-09
EP3592016A4 (en) 2020-02-19
CN110431865A (zh) 2019-11-08
EP3592016A1 (en) 2020-01-08
CN110431865B (zh) 2022-02-01

Similar Documents

Publication Publication Date Title
JP6988004B2 (ja) 集中型ユニットと分散型ユニットのアーキテクチャにおける通信方法および通信デバイス
EP3528519B1 (en) Network slice selection method and device
KR102397166B1 (ko) 시간 영역 리소스 할당 표들의 선택
CN112153098B (zh) 一种应用迁移方法及装置
WO2019007345A1 (zh) 网络切片的选择方法、装置及系统、存储介质
JP7184922B2 (ja) Ｕｅのためにポリシーを構成するための方法、装置、及びシステム
WO2020135850A1 (zh) 通信方法和装置
EP3955521A1 (en) Group management method, device and system
AU2019249939B2 (en) UE controlled handling of the security policy for user plane protection in 5G systems
WO2020238771A1 (zh) 无线接入能力信息处理方法及相关设备
WO2019037500A1 (zh) 一种选择无线接入网设备的方法及装置
WO2019051766A1 (zh) 一种调度请求的配置方法、网络设备及终端设备
JP2019501604A (ja) キャリアアグリケーション方法、ネットワーク側機器とコンピュータ記憶媒体
CN111263404B (zh) 一种负载管控的方法、装置及系统
WO2018170748A1 (zh) 一种选择核心网设备的方法及装置
CN110913437B (zh) 通信方法和网元
KR20200003184A (ko) 정보 전송 방법 및 장치
US11811856B2 (en) Determining a common application context relocation method for edge computing
JP2022510626A (ja) 下位レイヤスプリットにおける参照シンボルおよびユーザデータを分離するための方法
KR20230125844A (ko) Msg3 메시지를 송신 또는 수신하는 것을 포함하는 랜덤액세스
US11606672B2 (en) Information transmission method, network element selector, and controller
US20240114444A1 (en) Network slice isolation via network slice lists
CN114189920B (zh) 网络切片的载波隔离方法、装置、设备和介质
WO2018201305A1 (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: 17901991

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

Country of ref document: EP

Effective date: 20191001