WO2017161484A1 - 一种消息交互的方法、设备和系统 - Google Patents

一种消息交互的方法、设备和系统 Download PDF

Info

Publication number
WO2017161484A1
WO2017161484A1 PCT/CN2016/076927 CN2016076927W WO2017161484A1 WO 2017161484 A1 WO2017161484 A1 WO 2017161484A1 CN 2016076927 W CN2016076927 W CN 2016076927W WO 2017161484 A1 WO2017161484 A1 WO 2017161484A1
Authority
WO
WIPO (PCT)
Prior art keywords
identifier
message
network
service
service rule
Prior art date
Application number
PCT/CN2016/076927
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 CN201680083551.6A priority Critical patent/CN108886678B/zh
Priority to PCT/CN2016/076927 priority patent/WO2017161484A1/zh
Publication of WO2017161484A1 publication Critical patent/WO2017161484A1/zh
Priority to US16/137,773 priority patent/US20190029075A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H04W88/184—Messaging devices, e.g. message centre
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30—Security of mobile devices; Security of mobile applications
    • H04W12/37—Managing security policies for mobile devices or for controlling mobile applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/72—Subscriber identity
    • 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
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/17—Selecting a data network PoA [Point of Attachment]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, device, and system for message interaction.
  • EPC Evolved Packet Core
  • NE Evolved Packet Core
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P- GW Packet Data Network Gateway
  • the network function of the current EPC is implemented by the service characteristics and processing logic that are solidified in the network element and the flow messages between the network elements, such as mobility management, bearer management, location management, and the like.
  • the access service of the user needs the MME, the S-GW, the P-GW, and other network elements in the network, such as a Policy and Charging Rules Function (PCRF) and a Home Subscriber Server (Home Subscriber Server). , HSS), etc. work together and are done through standardized business process logic. Therefore, the characteristics of the network functions that the current EPC can provide are solidified.
  • PCRF Policy and Charging Rules Function
  • HSS Home Subscriber Server
  • the network functions provided by the EPC network are solidified and distributed among the various network elements. Therefore, if new network functions need to be introduced to support the user's needs, the EPC network needs to redefine and design the processing logic and process interaction of the network element. Such redesign means that the equipment manufacturer has a long development cycle and high cost. For the network operator, it means that the new network function cannot be released in time, and new services are provided to the user.
  • the HSS pre-sets a usage type for the UE according to the type and capability of the UE, and the network sets a corresponding core network according to each usage type.
  • the specific forwarding process is, first, received by the network. After the request to the UE is sent to the default MME in the network, the default MME first obtains the core network corresponding to the UE from the HSS, and then redirects the request to the corresponding core network by the forwarding unit in the EPC network. MME, complete the network selection.
  • the traditional EPC network element architecture needs to be supported by the HSS to complete the network selection.
  • the embodiment of the invention provides a method, a device and a system for message interaction.
  • the network function is dynamically adjusted, the message interaction between the network function module and other network entities is implemented.
  • the first aspect of the embodiments of the present invention provides a method for message interaction, which may include:
  • the core network device first receives a message, and the message may carry a message identifier; then the core network device obtains a service rule set, and the service rule in the service rule set includes a message identifier and a network function module corresponding to the message identifier. After determining the service rule set, the core network device determines the target network function module identifier corresponding to the message identifier from the service rule set; the network function module identifies and finally sends the message to the network function identified by the corresponding target network function module. .
  • the core network device obtains the service rule set by first receiving the message with the message identifier. Since the service rule set has the correspondence between the message identifier and the network function module identifier, the core network device will receive the service rule.
  • the network function module identifier corresponding to the message identifier is determined centrally, and then the corresponding network function is found through the network function module identifier, and the message is sent to the network function, and the HSS intervention is not required during the entire network function selection, only through the service.
  • the pre-stored correspondence in the rule set can quickly locate the message, and there is no special requirement for the message. It can be an internal message or an external message. As long as the message carries the message identifier, the corresponding message can be correctly selected. Network function.
  • the message is a message sent by a device within the service system in which the core network device is located or a message sent by a device outside the service system. It can be understood that the message generation path can be actually divided into two types, one is a message sent by a device in the service system, and the other is an external message request message sent by a device outside the service system, and both messages can trigger the selection. The process of network functions.
  • the message identification includes at least one of a timer timeout identifier, a message type identifier, and a function type identifier. It can be understood that the message identifier can be different according to the message, and can correspond to the message corresponding to the type.
  • the acquiring, by the core network device, the service rule set includes: the core network device acquiring the service rule set from the storage device; or the core network device locally reading the service rule from the core network device set.
  • the manner in which the core network device obtains the service rule set may be multiple, for example, may be acquired in a storage device, and the service rule set may be preset and stored in the storage device; for example, the core network device may be localized from the core network device.
  • Read, that is, the configured service rule set is placed locally on the core network device, such as the storage medium in the core network device, and can be directly read from the storage medium when the core network device obtains the service rule set.
  • the external message may be a request message, and the message type identifier may be carried in the request message.
  • the non-access stratum NAS message header of the request message includes the message type identifier, the method further comprising: the core network device determining the message type identifier according to a NAS message header of the request message .
  • the request message carries the message type identifier.
  • the message type identifier may be in the NAS message header of the request message, and the determination of the message type identifier may be extracted from the NAS message header of the request message.
  • the message includes a trigger message and/or a request message, where the trigger message carries the timer timeout identifier, and the request message carries the message type identifier.
  • the internal messages can be divided into trigger messages and request messages according to different types. The two types of messages carry different identifiers.
  • the request message is a message type identifier
  • the trigger message is a timer timeout identifier.
  • determining, by the core network device, the target network function module identifier corresponding to the message identifier in the service rule set includes: the core network device in the service rule set And determining, according to at least one of a timer timeout identifier, a message type identifier, and a function type identifier carried in the message, a corresponding target network function module identifier.
  • the message is a trigger message
  • the determining, by the core network device, the target network function module identifier corresponding to the message identifier in the service rule set includes: the core network device in the service rule set Determining a corresponding target network function module identifier according to the timer timeout identifier carried in the trigger message. If the message is a trigger message type, the trigger message may carry a timer timeout identifier, so that the corresponding target network function module identifier can be determined according to the timer timeout identifier, which can enhance the implementability of the method of the present invention.
  • the message is a request message
  • the core network device is in the service rule
  • Determining the target network function module identifier corresponding to the message identifier in a centralized manner includes: determining, by the core network device, the corresponding target network function module identifier according to the message type identifier carried in the request message in the service rule set. For the request message and the request message, since the message type identifier is carried in the two request messages, the target network function module identifier can be determined from the service rule set by the message type identifier.
  • the service rule in the service rule set further includes a network slice identifier, and the network slice identifier, the message identifier, and the network function module identifier in the service rule are corresponding
  • the method further includes: the core network device according to the Determining, by the core network device, the network function module identifier corresponding to the message identifier in the service rule set, where the core network device is in the service rule set according to the The message identifier and the network slice identifier of the message determine the network function module identifier. It can be seen that in some cases, for example, in an application scenario of a network slice, a plurality of network slices are likely to have the same message identifier.
  • the corresponding network function module identifier cannot be found through the message identifier, and the message must be first passed.
  • the corresponding network function module identifier is determined by using the message identifier in the service rule set corresponding to the network slice.
  • the message further carries a UE identifier
  • the service rule in the service rule set further includes a network slice identifier
  • the network slice identifier corresponds to a network slice
  • the core network device is in the service rule set. Determining the target network function module identifier corresponding to the message identifier, the core network device determining a network slice identifier according to the UE identifier, and determining, by the core network device, a service rule group according to the network slice identifier, the service rule The group consists of service rules with the same network slice identifier; the core network device determines the target network function module identifier corresponding to the message identifier from the service rule group according to the message identifier of the message.
  • the message when applied to the network slicing service, the message also carries the UE identifier, and the UE identifier uniquely corresponds to one network slice, that is, the required network functions of the UE are provided by the network slice, and each network slice is provided.
  • the network slice identifier is included in each service rule in the service rule set. Therefore, the entire service rule set can be divided into several service rule groups, and each service rule group is responsible for serving one network slice. .
  • the message further carries a UE identifier, each network slice corresponds to a service rule set, and the service rule set further includes a network slice identifier, and the network slice identifier pair Determining, by the network network device, the target network function module identifier corresponding to the message identifier in the service rule set, the core network device determining a network slice identifier according to the UE identifier, and the core network device Determining, according to the network slice identifier, a target service rule set; the core network device determining, according to the message identifier of the message, the target network function module identifier corresponding to the message identifier from the target service rule set.
  • the message when applied to the network slicing service, the message also carries the UE identifier, and the UE identifier uniquely corresponds to one network slice, that is, the required network functions of the UE are provided by the network slice, and each network slice is provided.
  • the network slice identifier is included in each service rule in the service rule set. Therefore, multiple service rule sets can be set, and each service rule set is responsible for serving one network slice, and each service rule set Set the network slice ID.
  • the determining, by the core network device, the network slice identifier of the message according to the message includes: when the message carries a UE identifier, the core network device determines the message according to the UE identifier. The network slice identifier is obtained; or the core network device obtains the network slice identifier carried in the message. It can be seen that there are two ways to determine the network slice identifier of the message by using a message, one of which is that the message carries the UE identifier, and the UE identifier can correspond to the network slice identifier, and second, the network slice identifier is directly carried in the message. in.
  • the network slice identifier may be determined in two manners.
  • the core network device determines, according to the UE identifier, the network slice identifier of the message, where the core network includes: The device queries and determines the network slice identifier of the message according to the UE identifier, and the corresponding relationship between the network slice identifier of the message and the UE identifier is stored in the subscription data center; or the core network device
  • the network slice identifier of the message is determined by parsing the identifier of the UE, where the network identifier carries a network slice identifier.
  • the core network device obtains the network slice identifier according to the UE identifier.
  • the network slice identifier may be obtained directly from the subscription data center.
  • the UE identifier carries the network slice identifier.
  • the network slice identifier can be obtained by parsing the UE identifier.
  • the determining, by the core network device, the target network function module identifier corresponding to the message identifier in the service rule set further comprising: the core network device according to the timer timeout identifier in the trigger message Determining a corresponding UE identifier, and generating a timer of the timer timeout identifier corresponds to the UE identifier.
  • the message is a trigger message
  • the UE identity generally does not It is directly included in the trigger message, but in the UE context database, because the maintenance of the timer corresponds to the UE, the UE corresponding to the UE is identified by the timer timeout, and the UE identifier is determined in the context database of the UE.
  • the second aspect of the present invention further provides a core network device, which may include:
  • a receiving module configured to receive a message, where the message carries a message identifier
  • a processing module configured to obtain a service rule set, where the service rule in the service rule set includes a message identifier and a network function module identifier corresponding to the message identifier; and determining, in the service rule set, a target corresponding to the message identifier Network function module identification;
  • a sending module configured to send the message to the network function identified by the corresponding target network function module.
  • the message is a request message sent by a device in a service system in which the core network device is located or an external message sent by a device outside the service system.
  • the message identifier includes at least one of a timer timeout identifier, a message type identifier, and a function type identifier.
  • the processing module is specifically configured to:
  • Reading the set of service rules locally from the core network device or,
  • the set of service rules is obtained from a storage device.
  • the request message carries the message type identifier.
  • the non-access stratum NAS message header of the request message includes the message type identifier, and the processing module is further configured to:
  • the message includes a trigger message and/or a request message, where the trigger message carries the timer timeout identifier, and the request message carries the message type identifier.
  • the processing module is specifically configured to:
  • the service rule in the service rule set further includes a network slice identifier, and the network slice identifier, the message identifier, and the network function module identifier in the service rule are corresponding, and the processing module is further configured to The message determines a network slice identifier of the message;
  • the determining, by the processing module, the network function module identifier corresponding to the message identifier in the service rule set includes:
  • the processing module determines, in the service rule set, the network function module identifier according to the message identifier and a network slice identifier of the message.
  • the message further carries a UE identifier
  • the service rule in the service rule set further includes a network slice identifier, where the network slice identifier corresponds to a network slice
  • the processing module is specifically configured to:
  • the message further carries a UE identifier, each network slice corresponds to a service rule set, and the service rule set further includes a network slice identifier, where the network slice identifier corresponds to a network slice, and the service rule The set also includes a network slice identifier, and the processing module is specifically configured to:
  • the processing module when the message carries the UE identifier, is specifically configured to:
  • the processing module queries and determines the network slice identifier of the message in the subscription data center according to the UE identifier, and the corresponding relationship between the network slice identifier of the message and the UE identifier is stored in the subscription data center; or
  • the processing module determines a network slice identifier of the message by parsing the UE identifier, where the UE identifier carries a network slice identifier.
  • the processing module is further configured to:
  • a third aspect of the present invention provides a network system, which may include:
  • a core network device configured to receive a message, where the message includes a message identifier, and a service rule set, where the service rule in the service rule set includes the message identifier and a network function module identifier corresponding to the message identifier; the service Determining, by the rule set, a target network function module identifier corresponding to the message identifier; and sending the message to a network function module corresponding to the target network function module identifier;
  • the network function module is configured to receive the message sent by the core network device, and provide a network function service.
  • the message identifier includes at least one of a timer timeout identifier, a message type identifier, and a function type identifier.
  • the message is a message sent by the device in the service system where the core network device is located to the core network device or a message sent by the device outside the service system to the core network device.
  • the core network device is specifically configured to locally read the service rule set from a core network device;
  • the system further includes a storage device, configured to store the service rule set, and the core network device is specifically configured to acquire the service rule set from the storage device.
  • the service rule in the service rule set further includes a network slice identifier, and when the network slice identifier, the message identifier, and the network function module identifier in the service rule correspond, the core network device is further used according to The message determines a network slice identifier of the message;
  • the core network device is specifically configured to determine, according to the message identifier and the network slice identifier of the message, the network function module identifier in the service rule set.
  • the core network device is specifically configured to:
  • the core network device when the message carries the UE identifier, is specifically configured to:
  • the network slice identifier of the message is determined by parsing the identifier of the UE, where the network identifier carries a network slice identifier.
  • the fourth aspect of the present invention further provides a network system, which may include:
  • a network function module configured to define a service rule, and provide a network function corresponding to the service rule, where the service rule includes a message identifier and a network function module identifier corresponding to the message identifier;
  • a service management framework module configured to register the service rule and a network function module corresponding to the service rule; and configured to store the service rule set formed by the service rule in the network system;
  • Process coordination module for:
  • the message is sent to a network function corresponding to the target network function module identifier.
  • the process coordination module is further specifically configured to:
  • the service management framework module is also used to:
  • the network address is sent to the process coordination module.
  • the process coordination module is further configured to:
  • the service management framework module is further configured to:
  • the process coordination module is specifically configured to:
  • the network system further includes a subscription data center, configured to pre-define and store a correspondence between the network slice identifier and the UE identifier, where the network slice identifier corresponds to a network slice;
  • the process coordination module is specifically configured to:
  • the network system further includes a network function component module for calling by one or more of the network function modules, and including at least one of the following modules: user data management Module, security module, bearer management module, policy management module.
  • the service management framework module is further for adding, deleting, and updating at least one of the network function modules.
  • the embodiment of the present invention has the following advantages: the core network device obtains the service rule set, determines the target network function module identifier according to the message identifier and the service rule set carried in the received message, and obtains the The received message is sent to the network function module corresponding to the identifier of the target network function module. Since the service rule centralized service rule can be modified, when a new functional service is deployed in the network or an existing service is updated (that is, in a case where the network function is dynamically adjusted), one corresponding to the network function in the service rule set is adjusted or A plurality of service rules can be implemented according to the method embodiment of the present invention to implement a subsequent message interaction process, thereby improving network execution efficiency.
  • 1 is a schematic structural diagram of an existing EPC network
  • FIG. 2 is a schematic structural diagram of a system according to an embodiment of the present invention.
  • FIG. 3 is a diagram of an embodiment of a message interaction method according to an embodiment of the present invention.
  • FIG. 4 is a diagram of another embodiment of a message interaction method according to an embodiment of the present invention.
  • FIG. 5 is a diagram of another embodiment of a message interaction method according to an embodiment of the present invention.
  • FIG. 6 is a diagram of an embodiment of a core network device according to an embodiment of the present invention.
  • FIG. 7 is a diagram showing an embodiment of a network system according to an embodiment of the present invention.
  • FIG. 8 is a diagram showing an embodiment of a network system according to an embodiment of the present invention.
  • FIG. 9 is a diagram of an embodiment of a core network device according to an embodiment of the present invention.
  • Figure 10 is a diagram showing an embodiment of a network system in accordance with an embodiment of the present invention.
  • the embodiment of the invention provides a method, a device and a system for message interaction, which are used to modify a service rule in a service rule set to implement subsequent message interaction when a new function service is deployed in the network or an existing service is updated. Process to improve the efficiency of network execution.
  • FIG. 1 is a schematic structural diagram of an existing EPC network, where a user equipment (User Equipment, UE) is used in the EPC network architecture.
  • UE User Equipment
  • FIG. 1 is a schematic structural diagram of an existing EPC network, where a user equipment (User Equipment, UE) is used in the EPC network architecture.
  • UE User Equipment
  • MBB Mobile Broad Band
  • MTC Machine Type Communication
  • V2V Vehicle to Vehicle
  • the UE can be connected to the core network through the access network, and the core network provides the corresponding service for the user equipment, wherein the control plane of the core network provides the UE with the registration access, location update, location switching, bearer establishment, etc. of the UE. Control surface service inside.
  • the core network here can also be called Non-access network, where the non-access network refers to a network different from the access network and providing at least one or more of the following functional combinations, which may include: Non-Access Stratum (NAS) letter Processing, NAS security, authentication, access control, authorization, bearer management or session management, mobility management, location management, lawful interception, roaming Wait.
  • NAS Non-Access Stratum
  • FIG. 2 is a schematic diagram of a system architecture according to an embodiment of the present invention.
  • the core network control plane function is implemented by using a “network function + service architecture”.
  • the architecture of the present invention cancels the Mobility Management Entity (MME), the Serving Gateway (S-GW), and the Packet Data Network Gateway (Packet) included in the EPC architecture.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • Packet Packet Data Network Gateway
  • P-GW Data Network Gateway
  • the network function refers to one or more relatively independent and complete logic functions, which can process similar types of service requests from the UE or other entities in the network, and is responsible for executing the corresponding processing flow, thereby completing the corresponding network functions. For example, the UE's registered access service, the UE's location update service, and the like.
  • the architecture shown in FIG. 2 mainly includes an external interface function module (EIF), a process coordinator (PC), a network function module, a network function component module, and a service management framework module.
  • EIF external interface function module
  • PC process coordinator
  • network function module a network function component module
  • service management framework module a service management framework module
  • EIF is the external interface function of the entire serviced control plane architecture, which handles message interaction with other network elements.
  • the EIF is responsible for implementing the interface functions between the functional modules (including PCs, network function modules, network function component modules, etc.) and entities in the control plane architecture, including establishment of communication channels, maintenance of connection contexts, protocol encapsulation and decapsulation of messages. , message forwarding and receiving, etc.
  • the PC is a unified network function coordination module of the entire serviced control plane architecture. It is responsible for transmitting messages based on functional modules from the serving control plane or other network entities other than the serving control plane (eg UE, RAN Node, user plane). The message sent by the entity, or the network entity of another network, selects a network function module capable of processing the above message, and sends the above message to the selected network function module.
  • the PC can also be responsible for detecting and processing service request conflicts (for example, When a new service request conflicts with the current service process, it determines the priority execution, suspension, or rejection of the service request.
  • this unified device can perform EIF and PC functions at the same time.
  • this unified deployment device can be a Control Plane Interaction Manager Function (CPIMF).
  • CIMF Control Plane Interaction Manager Function
  • the network function module is the basic component of the network function implemented by the entire service control plane architecture, and can also be called the network function unit.
  • a network function module is a relatively independent and complete logical function entity that can receive a certain type or types of messages, process messages and perform corresponding network functions.
  • the network function module can complete the registration access service of the UE, the location update service of the UE, the handover service of the UE, and the like.
  • the network function module may also be one or more network function component modules that are combined according to the service execution order.
  • the network function component module is a general-purpose network function unit abstracted and independent in the entire service control plane architecture, and can also be called a network function component unit.
  • the network function component module is generally available for one or more network function modules to be used to perform the specific general network functions required in the network function implemented by the network function module.
  • the security verification service, the bearer setup service may be completed by the network function component module, and may be invoked by the UE registration access service and the handover service of the UE or the like.
  • the network function component module can also be embedded in the network function module.
  • the Service Management Framework module is the unit that performs the service management functions in the entire serviced control plane architecture.
  • Network function units in the network such as network function modules and network function component modules, can save related information (such as service rule sets) of network function units to the service management framework module through function registration.
  • Other entities in the network can obtain related information of the network function unit through the service management framework module, so as to realize the discovery and invocation of the network function unit.
  • the serviced control plane architecture is different from the decentralized and repetitive storage of user data by traditional network elements, but decouples the business processing logic of the network function from the user data to be processed.
  • the user context, security context and bearer context stored in the network element, and network policies are placed in a unified database for storage, and the generalized data service provides access to the database.
  • the EPC network proposes to support different service requirements of multiple users.
  • Dedicated Core (DECOR) technology which uses a functionally customized set of network elements to build a regional private network, and uses dedicated core network selection technology to select the appropriate user equipment for certain service needs.
  • a private network ensures that the user can access the private network and select the corresponding network function.
  • the UE sends a request message to the radio access network node
  • the radio access network node cannot know the DECOR corresponding to the UE. Therefore, the radio access network node arbitrarily selects a Mobility Management Entity (MME) as the default for the UE to ensure load balancing. The MME then sends the received UE's request message to the default MME;
  • MME Mobility Management Entity
  • the default MME processes the request message of the UE, and obtains the subscription information of the UE, and then determines the DECOR MME corresponding to the UE according to the subscription information of the UE. If the DECOR MME corresponding to the UE is inconsistent with the default MME, then the default MME will connect to the wireless device.
  • the ingress node sends a redirect message;
  • the radio access network node After receiving the redirect message, the radio access network node resends the request message of the UE to the DECOR MME corresponding to the UE.
  • the above method generally requires a redirection process when selecting a network corresponding to the UE. Therefore, the application of the network selection technology to the 5G network architecture has the following problem: since the network slice is generally a network optimized for a certain type of UE and provides a customized service, different network slices have certain authentication methods for the UE.
  • the arbitrarily selected network slice may not be able to obtain the subscription data of the UE because the UE cannot be authenticated, so that the network slice corresponding to the UE cannot be determined, and the corresponding network function cannot be selected for the UE;
  • the network access node may perform a redirection process when selecting a network slice for the UE, and in the process of redirection, the radio access network node needs to cache the UE's request message, and needs to repeatedly send the request message, which greatly increases the number of times. The burden of the wireless access network node.
  • the method and apparatus for selecting a network function in the embodiment of the present invention are not limited to the network architecture shown in FIG. 1 and FIG. 2, and the embodiment of the present invention may also be applied to other networks similar to network function modularization or service. In the architecture.
  • an embodiment of the present invention provides a method for message interaction.
  • FIG. 3 is a schematic diagram of an embodiment of a method for message interaction according to an embodiment of the present invention. As shown in 3, the method can include the following:
  • the core network device receives the message.
  • the message includes a message sent by the device in the service system where the core network device is located or a request message sent by the device outside the service system, and the message identifier is carried in both the message in the service system and the external message.
  • the service system in the embodiment of the present invention refers to a control plane in a communication network, and may be, for example, the foregoing serviced control plane architecture.
  • the network system in the embodiment of the present invention refers to a communication network, and may include a service system.
  • the message identifier includes at least one of a timer timeout identifier, a message type identifier, and a function type identifier.
  • the core network device may be a PC or EIF or a two-in-one deployment device with a CPIMF as shown in FIG. 2, and the core network device has a network element selection function.
  • the core network device is a PC
  • the UE The request message can be forwarded to the EIF through an access network element, such as a wireless base station, and then forwarded to the core network device by the EIF, and if the core network device is an EIF, the core network device can directly access the network element such as wireless.
  • the base station or the like forwards the request message of the UE.
  • the message includes two types, one is a message sent by a device inside the service system where the core network device is located, and the message may be further divided into a request message and a trigger message; and another device is a device outside the service system where the core network device is located.
  • the sent messages can be divided into the request message and the trigger message.
  • the request message and the trigger message are generated differently.
  • the trigger message can be triggered by the internal or external maintenance timer of the service system where the core network device is located.
  • the generated message, the request message is a message sent by these devices with the requested service.
  • the message identifiers included in the message may include three types, one is a message type identifier, one is a timer timeout identifier, and the other is a function type identifier.
  • the message type identifier may be a type identifier carried in the message header, indicating the type of the message, for example, a message type field included in a message header of a non-access stratum NAS message; the timer timeout identifier may be after the timer expires
  • the identifier carried in the triggered message may indicate which type of timer of the UE has timed out;
  • the function type identifier may be a function type identifier carried in the message or the message header, which is used to indicate the specific request of the message.
  • Various types of network functions such as in the Protocol descriptor field of a message, indicate the mobile management function or session management function requested by the message.
  • the message type identifier and/or the function type identifier are generally carried, and for the trigger message, it may be a timer timeout identifier.
  • an event timer can be maintained in a database in or outside the service system where the core network device is located.
  • a trigger message is sent, and the core network device can receive the trigger message. Determining the timer timeout identifier carried in the trigger message. For example, when the core network device receives the request message from the service system or the request message from the outside, the corresponding message type identifier and/or may be determined. A function type message for subsequent processing.
  • the core network device obtains a service rule set.
  • step 302 There is no order between step 302 and step 301.
  • the service rule in the service rule set includes a message identifier and a network function module identifier corresponding to the message identifier. That is, when the message identifier is the message type identifier, the message type identifier corresponds to the network function module identifier; when the message identifier is the timer timeout identifier, the timer timeout identifier corresponds to the network function module identifier; when the message identifier is the function type identifier , the function type identifier corresponding to the network function module identifier.
  • the core network device obtains the service rule set from other storage devices; second, the core network device from the core The network device reads the set of service rules locally.
  • the network function module can provide the service rule set to the service management framework module by means of function registration, and the service management framework module uniformly saves and manages all the network function modules.
  • the core network device can obtain the service rule set of the required network function module from the service management framework module and save it locally.
  • the service rule set is a set of pre-set service rules
  • the service rule set can be stored in the storage device after being generated, and when the core network device starts working, the device will read the storage device from the storage device.
  • the service rule set is sent to the core network device; in another mode, the service rule set is directly stored in the local device of the core network device after the generation is completed, for example, configured as a configuration file on the core network device, and the message identification message network function module identifier message is generated.
  • the network function module identifier corresponds to a network function for serving the UE.
  • the core network device determines the corresponding message identifier, it can be identified by the message. As a basis, the network function module identifier is determined.
  • the service rules are described below in Table 1-1:
  • the Event ID indicates the event identifier
  • the Message Type ID indicates the message type identifier
  • the Timer Trigger ID indicates the timer timeout identifier
  • the Function Type ID indicates the function type identifier
  • the NF ID indicates the network function module identifier. It can be seen that a service rule contains five items, and an Event ID can be uniquely determined by a Message Type ID or a Timer Trigger ID or a Function ID, and an NF ID can be determined by an Event ID to determine the corresponding Network function module.
  • the network function module identifier may be identifier information corresponding to the network function, or may be an access address corresponding to the network function or other information capable of uniquely identifying the network function.
  • the service rules may also be as shown in the following Table 1-2:
  • the message identifier may be a message type identifier, a Message Type ID, a timer timeout identifier, a Timer Trigger ID, or a function type identifier, a Function Type ID. That is, a NF ID can be uniquely determined by the Message Type ID or the Timer Trigger ID or the Function ID, thereby determining the corresponding network function module.
  • the NF_A ID, the NF_B ID is the identifier of the network function module, and the Message Type indicates the message type identifier. It can be seen that the network function NF_A can process the message with the Message Type being 1, 2, 3, and the network function NF_B can process the Message Type to 4. 5,6 news. Therefore, according to the message type of the message, the corresponding network function module identifier capable of processing the message can be determined.
  • Table 1-1 Table 1-1
  • Table 1-2 Table 1-3
  • Table 1-3 The above specific use of Table 1-1, Table 1-2 or Table 1-3 can be determined according to the actual situation, specifically not Limited.
  • the specific generation of Table 1-1, Table 1-2, and Table 1-3 can be defined by the network function module.
  • the network function module can generate the above service rule set according to a message that can be processed by itself.
  • the message that can be processed by the network function module includes a message sent by a device inside the service system where the core network device is located and a message sent by a device external to the service system where the core network device is located.
  • the network function module generates a specific form of the foregoing service rule set according to the message identifier that can be processed by itself and the network function module identifier of the network function module.
  • the service rule set can be dynamically updated when the network function module is actually running. Specifically, the network function module determines, according to the updated service, the message identifier that can be processed by itself, and the network function module identifier of the network to regenerate the specific form of the service rule set.
  • the network function module may provide the service rule set to the service management framework module by means of function registration, and the service management framework module uniformly saves and manages the service rule set generated by all the network function modules.
  • the core network device can obtain the service rule set of the required network function module from the service management framework module and save it locally.
  • the message type identifier After the network function module serving one or some messages is generated, the network defines and allocates the network function module.
  • the network function uniquely corresponds to the network function module identifier.
  • the network function module identifier defines a message identifier according to a message that can be processed by itself, and the message identifier is used to indicate that the network function module can be invoked to process the message when the message corresponding to the message identifier arrives.
  • the network function module defines a message correspondence table for the message identifier, that is, at least one of a message type identifier, a timer timeout identifier, and a function type identifier is configured for each message identifier, indicating that any one carries a message type identifier.
  • the network function module may be invoked to process the message when the timer timeout identifier and at least one of the function type identifiers arrive at the message.
  • the message identifier Message ID itself may be a message type identifier, a Message Type ID, a timer timeout identifier, a Timer Trigger ID, or a function type identifier, a Function Type ID. That is, a NF ID can be uniquely determined by the Message Type ID or the Timer Trigger ID or the Function ID, thereby determining the corresponding network function module.
  • the generation of the service rules in Table 1-2 is similar to the generation of Table 1-1, except that the message identifier is no longer defined. Instead, the message correspondence table is directly defined, that is, at least one of a message type identifier, a timer timeout identifier, and a function type identifier is configured for each message identifier, indicating that any one carries a message type identifier, a timer timeout identifier, and a function type.
  • the network function module can be invoked to process the message.
  • Table 1-3 generates the service rules and types of Table 1-2, and details are not described here.
  • the core network device may be an EIF or a PC or a CPIMF in which the core network device is a CPIMF.
  • the timer timeout identifier indicates that a timeout message is sent to the CPIMF when the timer inside or outside the service system times out.
  • the CPIMF receives the timer timeout identifier, it indicates that the message indicated by the corresponding message identifier is triggered; and the message type identifier or the function type identifier is from the request message, and the message type identifier is usually in the protocol header of the request message, CPIMF After receiving the request message, the request message is parsed and the message type identifier or function type identifier is obtained according to the protocol header.
  • the Detach event is triggered corresponding to the Detach event, and the Detach message is triggered, thereby passing the Detach message.
  • the identifier identifies the corresponding network function module.
  • the corresponding target network function module identifier may be determined in the service rule set according to the message identifier.
  • the service rule in the service rule set further includes a network slice identifier, and the network slice identifier, the message identifier, and the network function module identifier have a corresponding relationship.
  • the core network device determines and describes the service rule set.
  • the target network function module identifier corresponding to the message identifier may include:
  • the core network device determines, according to the message, a network slice identifier of the message
  • the message carries a network slice identifier of the message.
  • the message carries a UE identifier, where the UE identifier may be an IMEI, an IMSI, or other identifier that can uniquely identify the UE, and the core network device determines the network slice identifier according to the UE identifier.
  • the UE identifier may be an IMEI, an IMSI, or other identifier that can uniquely identify the UE
  • the core network device determines the network slice identifier according to the UE identifier.
  • the core network device determines a service rule group according to the network slice identifier of the message. Can reason The solution is that the network function module applied to the network slice can add a network slice identifier to the service rule in each service rule set, that is, each service rule corresponds to a network slice identifier, and the service rule of the same network slice identifier is composed.
  • a service rule group that provides various functions of network slicing. It can be understood that after the network network device determines the network slice identifier, the service rule group is further determined. Since the service rule group is composed of service rules identified by the same network slice and corresponds to one network slice, the core network device only needs to The network slice identifier of the message can be used to determine the same service rule group as the network slice identifier of the message. When searching for the network function module corresponding to the matching message, only the service rule group needs to be searched. Reduce the scope of the search match and improve the search efficiency.
  • multiple service rule sets may be directly set.
  • multiple service rule sets and one service rule set are stored in the core network device or the storage device.
  • the service rule in the same has the same network slice identifier, and one service rule set corresponds to one network slice.
  • the Ba step is the same as the foregoing Aa step;
  • Step Bb may specifically be that the core network device determines a service rule set according to the network slice identifier.
  • the service rule set corresponding to the network slice identifier of the message may be determined from multiple service rule sets.
  • the core network device determines, according to the message identifier of the message, the target network function module identifier corresponding to the message identifier from the service rule set.
  • the core network device may determine the network slice identifier according to the UE identifier in multiple manners, and two of the following manners are given.
  • the UE identifier and the network slice identifier are predefined by the subscription data center.
  • the core network device determines the network slice identifier according to the UE identifier, where the core network device queries and determines the network slice identifier according to the UE identifier subscription data center.
  • the correspondence between the network slice identifier and the UE identity is predefined by the subscription data center and stored in the subscription data center.
  • the UE identifier includes not only the UE identification information but also the network slice identifier corresponding to the UE identifier.
  • the determining, by the core network device, the network slice identifier according to the UE identifier includes:
  • the core network device determines the network slice identifier by parsing the UE identifier, and the UE identifier is a UE identifier that is pre-allocated by the subscription data center and carries the network slice identifier.
  • the core network device can directly from the subscription data.
  • the core network device can directly parse the enhanced UE identifier, and obtain the network slice identifier from the network identifier, which can be selected according to actual conditions, which is not limited herein.
  • the above is the configuration and selection process of the network slice for the UE's request message.
  • the following describes the configuration and selection process of the network slice of the message.
  • the message is a message in the service system where the core network device is located, and the core network device determines the target service rule in the service rule set according to the message, including:
  • the CA and the core network device determine the service rule group from the service rule set according to the timer timeout identifier in the message.
  • the service rule group is configured from the service rule set by the network function module in the service system where the core network device is located according to the service requirement of the UE;
  • the service rule set is grouped, and each group corresponds to the requirements of one type of UE. .
  • the Cb and the core network device determine the target service rule from the service rule set according to the timer timeout identifier.
  • the corresponding message identifier can be determined, and the service rule with the message identifier can be determined in the service rule group, because the service rule group generally does not appear to be targeted.
  • the service rule in the service rule set further includes a network slice identifier
  • the core network device determines, according to the timer timeout identifier in the internal message, the service rule group from the service rule set includes:
  • the core network device determines the network slice identifier according to the timer timeout identifier
  • the network slice identifier can be obtained through the service rule where the message identifier is located.
  • the Cc and the core network device determine the service rule group according to the network slice identifier.
  • the service rule group includes a service rule having the same network slice identifier configured by the subscription data center from the service rule set according to the service requirement of the UE.
  • the service rule with the same network slice identifier can be determined.
  • the determining, by the core network device, the target service rule from the service rule group according to the timer timeout identifier includes:
  • the core network device determines a corresponding message identifier according to the timer timeout identifier
  • timer timeout identifier has a corresponding relationship with the message identifier, it is only necessary to query the corresponding relationship by determining the corresponding message identifier by using the timer timeout identifier.
  • the Cd and the core network device determine the target service rule from the service rule group according to the message identifier.
  • the core network device is selected from the service rule set in step 302, but is selected in the service rule with the same network slice identifier. Because the selection range is smaller, the selection speed will be more rapid, bringing direct The effect is a reduction in response time.
  • the core network device may determine the corresponding network function module identifier, and send the message to the corresponding network function module.
  • the network function module identifier determined by the core network device is only the identifier information of the network function module, and the core network device requests the access address of the corresponding network function module from the service management framework module according to the identifier of the network function module.
  • the service management framework module returns an access address of the corresponding network function module, and the core network device sends the message to the network function module using the access address.
  • the core network device in the embodiment of the present invention first receives the message, and then obtains the service rule set, and determines the target network function module identifier in the service rule set by using the message identifier carried in the message message, where the service rule includes the message identifier and The network function module identifier corresponding to the message identifier can find a network function message message request message request message corresponding to the target service rule by finding the target network function module identifier.
  • the service rule centralized service rule can be modified in the embodiment of the present invention. Therefore, when a new functional service is deployed or an existing service is updated in the network (that is, when the network function is dynamically adjusted), the service rule set is adjusted.
  • the one or more service rules corresponding to the network function may be executed according to the method embodiment of the present invention to implement a subsequent message interaction process, thereby improving network execution efficiency.
  • the following takes the process of the Attach network service as an example to illustrate the configuration process of the Attach network service and the role that the service configuration plays when the EIF selects the network slice service for the UE's Attach request.
  • the service will be Configure the unique network function module identifier, that is, the Attach NF ID, and define a message identifier, which indicates the event that triggers the Attach NF ID.
  • the message identifier is the Attach Message ID, and the Attach Message ID and the Attach NF ID are used as an Attach network. Service rules are saved.
  • the event correspondence table of the Attach Message ID is defined, that is, the Attach request sent by the UE corresponding to the Attach Message ID, that is, the condition triggered by the Attach request as the Attach Message ID. Since there is no Attack event triggered internally by the network, the Timer Trigger ID Set to N/A, that is, the final Attach Message ID corresponds to the Attach Message Type ID, and the Timer Trigger ID is set to N/A and Attach Message Type ID to join the Attach Network Service Rule.
  • the configured Attach network service rule is added to the core network device, for example, in the configuration file of the network slice A.
  • the EIF uses the service rule set of the Attach network service to select the corresponding network function for the Attach request of the UE.
  • the subscription data center pre-defines a network slice, for example, the network slice A configured as described above.
  • the subscription data center there are two types of the subscription data center that associate the UE with the network slice A. And generating a correspondence relationship between the UE identifier of the UE and the network slice A. If the UE identifier is an identifier that uniquely identifies the UE, for example, IMSI, IMEI, etc., the correspondence between the unique identifier and the Slice ID_A is saved in the policy database; The second is to assign the UE an enhanced unique identifier containing the Slice ID_A ID of Network Slice A.
  • FIG. 4 is another embodiment of a method for message interaction according to an embodiment of the present invention.
  • the method includes a UE, an EIF, a policy database, and an Attach network service instance.
  • the execution process of the Attach request may include:
  • the policy database stores a correspondence between the unique identifier of the UE and the slice ID_A.
  • the step is a pre-requisite step of the actual implementation step, and may be performed directly in the configuration process, and is not necessarily configured during use.
  • the unique identifier may be an identifier that uniquely identifies the UE, such as IMSI or IMEI.
  • the UE sends an Attach request message to the EIF.
  • the step is that during the actual UE service processing, the UE sends an Attach request message to the core network device, so that the core network device identifies the request message.
  • the EIF queries the policy database for the slice ID_A corresponding to the unique identifier according to the unique identifier in the Attach request message.
  • the policy database returns the Slice ID_A corresponding to the unique identifier
  • Step 403 and step 404 are only one case of querying the slice ID, and another case may be that all the unique identifiers and the corresponding slice ID_A are stored in the EIF in advance, and the EIF only needs to query the local identifier according to the unique identifier. You can determine the Slice ID_A.
  • the EIF determines a corresponding service rule group according to the slice ID_A.
  • the EIF determines an Attach Message Type ID according to the NAS message header of the Attach request message.
  • this step 406 is not a necessary step.
  • the EIF may directly parse the Attach Message Type ID when the address is resolved from the Attach request message in step 403. Only the Attach Message Type ID is included in the NAS message header. The above step 406 is required.
  • the EIF obtains the corresponding Attach Message ID according to the Attach Message Type ID.
  • the Attach Message Type ID is obtained, and the corresponding Attach Message ID is determined according to the corresponding storage table.
  • the EIF determines the Attach NF ID in the Attach network service rule in the service rule group by using the Attach Message ID as the search condition. 409. The EIF forwards the Attach request message to the Attach network service instance corresponding to the Attach NF ID.
  • steps 407 and 408 are also not necessary steps, and steps 407 and 408 are also necessary. It can also be directly included in step 409.
  • the Attach NF ID can be directly located in the service rule group according to the Attach Message Type ID.
  • FIG. 5 is another embodiment of a method for message interaction according to an embodiment of the present invention.
  • the method includes a UE, an EIF, a policy database, and an Attach network service instance, where the UE identifier is an enhanced IMSI.
  • the steps 504 to 508 are similar to the steps 405 to 409, and the execution process of the Attach request may further include:
  • the enhanced IMSI including the slice ID_A allocated to the UE is stored in the policy database.
  • the UE sends an Attach request message to the EIF.
  • the EIF parses the enhanced IMSI in the Attach request message to determine Slice ID_A.
  • FIG. 6 is a schematic diagram of an embodiment of a core network device according to an embodiment of the present invention, which may include :
  • the receiving module 601 is configured to receive a message, where the message carries a message identifier.
  • the receiving module 601 is used to implement the step 301 in the embodiment shown in FIG. 3.
  • the description of the related function of the receiving module 601 is similar to the description of step 301 in the embodiment shown in FIG. 3, and details are not described herein again.
  • the message is a message sent by a device in a service system where the core network device is located or a message sent by a device outside the service system. Both of these messages have a message identifier, which can also be received by the receiving module 601.
  • the message identifier includes at least one of a timer timeout identifier, a message type identifier, and a function type identifier; and the message may be classified according to its function, in addition to being divided into internal and external.
  • the request message and the trigger message may carry different types of identifiers respectively.
  • the request message may carry a message type identifier
  • the trigger message may carry a timer timeout identifier.
  • the two types of identifiers refer to the description of step 301 in the embodiment shown in FIG. 3, and details are not described herein again.
  • the processing module 602 is configured to obtain a service rule set, where the service rule in the service rule set includes a message identifier and a network function module identifier corresponding to the message identifier.
  • the receiving module 602 is used to implement the step 302 in the embodiment shown in FIG. 3.
  • the description of the related function of the receiving module 602 is similar to the description of step 302 in the embodiment shown in FIG. 3, and details are not described herein again.
  • a service rule set there are multiple ways to obtain a service rule set, and optionally, from the storage device. Obtaining the set of service rules; or reading the set of service rules locally from a core network device. In this way, the service rule set can be obtained.
  • the service rule set In view of the storage form of the service rule set, it can be a configuration file, so it can be directly configured on the local storage of the core network device, or can be stored in the storage device, so There are two situations in which the storage device can be obtained. One is that the service network rule set is not stored on the core network device. The other is that if there is a configuration file, it needs to be updated. In this case, the storage device can be directly obtained. For the description of step 302 in the embodiment shown in FIG. 3, details are not described herein again.
  • the processing module 603 is configured to determine, in the service rule set, a target network function module identifier corresponding to the message identifier.
  • the receiving module 603 is used to implement the step 303 in the embodiment shown in FIG. 3.
  • the description of the related function of the receiving module 603 is similar to the description of step 303 in the embodiment shown in FIG. 3, and details are not described herein again.
  • the processing module is configured to determine, according to the timer timeout identifier and/or the message type identifier carried in the message, the corresponding target network function module identifier in the service rule set.
  • the message may be a timer timeout identifier, it may also be a message type identifier. Of course, it may also be a timer timeout identifier plus a message type identifier.
  • the message further carries a UE identifier
  • the service rule in the service rule set further includes a network slice identifier, where the network slice identifier corresponds to a network slice
  • the processing module The 603 is specifically configured to: determine, according to the identifier of the network, a network slice identifier; determine, according to the network slice identifier, a service rule group, where the service rule group is composed of service rules having the same network slice identifier; and according to the message identifier of the message, Determining, in the service rule group, a target network function module identifier corresponding to the message identifier.
  • the message when applied to the network slicing service, the message also carries the UE identifier, and the UE identifier uniquely corresponds to one network slice, that is, the required network functions of the UE are provided by the network slice, and each network slice is provided.
  • the network slice identifier is included in each service rule in the service rule set. Therefore, the entire service rule set can be divided into several service rule groups, and each service rule group is responsible for serving one network slice. .
  • the message further includes a UE identifier, where each network slice corresponds to a service rule set, and the service rule set further includes a network slice identifier, where the network slice identifier corresponds to a network slice, and the processing module 603 is specifically used. Determining, according to the identifier of the UE, a network slice identifier, determining a target service rule set according to the network slice identifier, and determining, according to the message identifier of the message, a target network function module corresponding to the message identifier from the target service rule set Logo.
  • the message when applied to the network slicing service, the message also carries the UE identifier, and the UE identifier uniquely corresponds to one network slice, that is, the required network functions of the UE are provided by the network slice, and each network slice is provided.
  • the network slice identifier is included in each service rule in the service rule set. Therefore, multiple service rule sets can be set, and each service rule set is responsible for serving one network slice, and each service rule set Set the network slice ID.
  • the determining of the network slice identifier may also be performed in two manners.
  • the processing module 603 is configured to query, according to the UE identifier, the network slice identifier, the network slice identifier, and the UE identifier. The corresponding relationship is stored in the subscription data center; or the core network device determines the network slice identifier by parsing the UE identifier, where the UE identifier carries a network slice identifier pre-allocated by the subscription data center.
  • the manner in which the core network device obtains the network slice identifier according to the UE identifier is actually multiple.
  • the network slice identifier can be directly obtained from the subscription data center; for example, carried in the UE identifier.
  • There is a network slice identifier and the network slice identifier can be obtained by parsing the UE identifier.
  • the processing module 603 is further configured to determine, according to the timer timeout identifier in the message, a corresponding UE identifier, where the timer that generates the timer timeout identifier corresponds to the UE identifier.
  • the UE identifier is generally not directly included in the trigger message, but in the UE context database, since the maintenance of the timer corresponds to the UE, the timer timeout identifier may be used.
  • the sending module 604 is configured to send the message to the network function identified by the corresponding target network function module.
  • the receiving module 604 is used to implement the step 304 in the embodiment shown in FIG. 3.
  • the description of the related function of the receiving module 604 is similar to the description of step 304 in the embodiment shown in FIG. 3, and details are not described herein again.
  • FIG. 7 is An embodiment of the network system of the embodiment of the present invention, wherein the core network device is a process coordination module, and the network system may include:
  • the core network device 701 is configured to receive a message, where the message includes a message identifier, and obtain a service rule set, where the service rule in the service rule set includes the message identifier and a network function module identifier corresponding to the message identifier;
  • the service rule set determines the target network function module identifier corresponding to the message identifier; and sends the message to the network function module 702 corresponding to the target network function module identifier;
  • the core network device 701 is the core network device in the embodiment shown in FIG. 6.
  • the core network device 703 can implement the steps 301 to 304 in the embodiment shown in FIG.
  • the description of steps 301 to 304 in the embodiment shown in FIG. 3 is similar, and details are not described herein again.
  • the network function module 702 is configured to receive the message sent by the core network device 701, and provide a network function service.
  • the network function module 702 is mainly configured to receive a message sent by the core network device 701 and provide a network function service corresponding to the message, and the network function module 702 can customize the service rule and the service rule set, and can also The service rules or service rule sets are stored on the network function module 702, and may of course be registered on the service management framework module.
  • the message identifier includes at least one of a timer timeout identifier, a message type identifier, and a function type identifier.
  • a timer timeout identifier identifier for the functions of the three types of identifiers and the corresponding manners.
  • the message is sent by the device in the service system where the core network device 701 is located to the core network device 701 or sent by the device outside the service system to the core network device 701.
  • Message may be of two types, in the service system and outside the service system.
  • the processing of the two types of messages refer to the description of step 302 in the embodiment shown in FIG. .
  • the core network device 701 is specifically configured to locally read the service rule set from the core network device 701.
  • the system further includes a storage device, where the service rule set is stored, where the core is The network device 701 is specifically configured to acquire the service rule set from the storage device.
  • the service rule set is obtained from a storage device.
  • the service rule set is locally read from the core network device 701.
  • the service rule set can be obtained by the two methods.
  • the storage rule set can be a configuration file, so it can be directly configured on the local storage of the core network device 701, or can be stored in the storage device.
  • the service rule in the service rule set further includes a network slice identifier, and when the network slice identifier, the message identifier, and the network function module identifier in the service rule correspond,
  • the core network device 701 is further configured to determine, according to the message, a network slice identifier of the message, where the core network device 701 is specifically configured to determine, according to the message identifier and the network slice identifier of the message, in the service rule set.
  • the network function module identifier is further configured to determine, according to the message, a network slice identifier of the message, where the core network device 701 is specifically configured to determine, according to the message identifier and the network slice identifier of the message, in the service rule set.
  • a plurality of network slices are likely to have the same message identifier.
  • the corresponding network function module identifier cannot be found through the message identifier, and the message must be first passed.
  • the corresponding network function module identifier is determined by using the message identifier in the service rule set corresponding to the network slice.
  • the network slice identifier of the message is determined according to the UE identifier, or the network slice identifier carried in the message is obtained. It can be understood that, in addition to the above, the network identifier is associated with the network function module identifier, and the network function module identifier is determined by the two identifiers.
  • the message carries the UE identifier
  • Directly determining the network slice identifier of the message by using the UE identifier Directly determining the network slice identifier of the message by using the UE identifier, The service rule in the service rule set corresponding to the network slice identifier is determined by the message identifier in the message, thereby determining the network function module identifier.
  • step 303 in the embodiment shown in FIG. 3, and details are not described herein again.
  • the core network device 701 may determine that the network slice identifier is determined according to the UE identifier, and the method is to query and determine the location in the subscription data center according to the UE identifier.
  • the network slice identifier of the message, the corresponding relationship between the network slice identifier of the message and the UE identifier is stored in the subscription data center; and the other is, determining the network slice identifier of the message by parsing the UE identifier,
  • the network identifier is carried in the UE identifier.
  • the corresponding network slice identifier can be obtained by using the UE identifier.
  • FIG. 8 is a diagram of an embodiment of a network system according to an embodiment of the present invention, where the core network device is a process coordination module, and the network system may include:
  • the network function module 801 is configured to define a service rule, and provide a network function service corresponding to the service rule, where the service rule includes a message identifier and a service identifier corresponding to the message identifier, where the service identifier corresponds to the network function service.
  • the service management framework module 802 is configured to register the service rule and a network function module corresponding to the service rule, and is further configured to store and store the service rule set formed by the service rule in the network system.
  • the functions of the network function module 801 and the service management framework module 802 cooperate to enable the generation of service rules and the registration of service rules and service rule sets. After the registration is completed, other devices can find correspondings according to the service rules.
  • the network function service enables fast and fast positioning of network function services to achieve the effect of quick selection of network functions.
  • the process coordination module 803 is configured to receive a message, where the message includes a message identifier, obtain a service rule set, determine, in the service rule set, a target network function module identifier corresponding to the message identifier, and correspond to the target network function module.
  • the identified network function service sends the message.
  • the process tuning module 803 is mainly configured to receive a message, and determine a corresponding service rule according to the message, and finally forward to the corresponding network function service according to the service rule; the process tuning module 803 and the figure
  • the function of the core network device in the embodiment shown in FIG. 3 is the same. For details, refer to the core network device in the embodiment shown in FIG. 3 and its description, and details are not described herein again.
  • the process coordination module 803 is further configured to: send the network function module to the service management framework module 802. Identification
  • the service management framework module 802 is further configured to: receive and determine, according to the network function module identifier, a network address of a network function module corresponding to the network function module identifier; and send the network address to the process coordination module 803.
  • the process coordination module 803 first determines the message identifier of the received message, and then queries the corresponding network function module identifier through the service rule set, and sends the network function module identifier to the service management framework module 802, due to the service. All the network function modules 801 and the network function service are registered on the management framework module 802. Therefore, the service management framework module 802 determines the network address of the corresponding network function module 801 according to the network function module identifier, and returns the network address to the network address. The process coordination module 803, after obtaining the network address, optionally, the process coordination module 803 forwards the message to the network function module 801 corresponding to the network address according to the network address.
  • the message type identifier and the timer timeout identifier respectively correspond to the message identifier, and the message identifier also corresponds to the network function module.
  • the message type identifier and/or the timer timeout identifier are first received, and then the message identifier is determined according to at least one of the two identifiers, and the corresponding target is determined by the message identifier.
  • the network function module identifier if it is in the form of Table 1-2 or Table 1-3, the corresponding network function module identifier may be directly determined by the message type identifier and/or the timer timeout identifier.
  • the service management framework module 802 since the service management framework module 802 registers all service rules, network function modules, and corresponding network function services, the service management framework module 802 can actively update the service rule set when determining that the service rules change;
  • the service management framework module is further configured to: determine that a service rule of the registered network function module is changed; and update a service rule set stored in the network system according to the changed service rule set.
  • the network system further includes a subscription data center 804. And configured to pre-define and store a correspondence between the network slice identifier and the UE identifier, where the network slice identifier corresponds to a network slice.
  • the process coordination module 803 determines that the specific process of the target network function module identifier is:
  • the subscription data center 804 is mainly used to provide a correspondence between the network slice identifier and the UE identifier, and the network slice identifier can be determined by the corresponding relationship if the UE identifier is used. Then, the process coordination module 803 finds the corresponding service rule group according to the network slice identifier, and determines the service rule in the service rule group according to the message identifier, thereby finding the corresponding target network function module identifier.
  • this situation corresponds to a service rule set corresponding to multiple service rule groups, and in the case of multiple service rule sets, a service rule set is determined according to the network slice identifier.
  • the network system may further include: a network function service component module, configured to be invoked by one or more of the network function modules, where the network function service component module includes the following modules At least one of: a user data management module, a security module, a bearer management module, and a policy management module.
  • a network function service component module configured to be invoked by one or more of the network function modules, where the network function service component module includes the following modules At least one of: a user data management module, a security module, a bearer management module, and a policy management module.
  • the network function service component module is mainly used for calling one or more of the network function modules, and the components may be at least one of a user data management module, a security module, a bearer management module, and a policy management module. To enhance the functionality of the network system.
  • FIG. 9 is an embodiment of a core network device according to an embodiment of the present invention.
  • the core network device 9 may include at least one processor 901, at least one receiver 902, at least one transmitter 903, and a memory 904 each connected to a bus.
  • the memory 904 includes a memory and an external memory, and the memory is used for storing the memory.
  • the processor 901 stores the related data of the computer instruction to be executed, and stores the configuration file and other files of the core network device, and the processor 901
  • the running computer in the memory executes the instructions to perform the steps 301 to 304 in the embodiment shown in FIG.
  • the core network device according to the embodiment of the present invention may have more or less components than those shown in FIG. Two or more components may be combined, or may have different component configurations or arrangements, which may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.
  • the processor 901 can implement the function of the processing module 602 in the embodiment shown in FIG. 6, and the receiver 902 can implement the receiving module in the embodiment shown in FIG. 601.
  • the transmitter 903 can implement the sending module 603 in the embodiment shown in FIG. 6.
  • FIG. 10 is a diagram of an embodiment of a network system according to an embodiment of the present invention.
  • the network system 10 may include at least one processor 1001, at least one receiver 1002, at least one transmitter 1003, and a memory 1004 each connected to a bus.
  • the memory 1004 includes a memory and an external memory, and the memory is used to store the storage processor 1001.
  • the executed computer instructions and related data are stored for storing the policy data and other data of the network system, and the processor 1001 runs the computer executed instructions in the memory;
  • the core network device according to the embodiment of the present invention may have a ratio of FIG. More or fewer components are shown, two or more components may be combined, or may have different component configurations or arrangements, each component may include one or more signal processing and/or application specific integrated circuits. Hardware, software, or a combination of hardware and software.
  • the processor 1001 can implement the functions of the network function module 801, the service management framework module 802, and the process coordination module 803 in the embodiment shown in FIG.
  • the function of the subscription data center 804 in the embodiment shown in FIG. 8 can be implemented in conjunction with the memory 1004 for receiving and transmitting messages internal or external to the service system.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or Some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Power Engineering (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明涉及通信领域，尤其涉及的是一种消息交互的方法、设备和系统。该方法可包括：核心网设备接收消息，消息中携带有消息标识；核心网设备获取服务规则集，服务规则集中的服务规则包括消息标识和对应的网络功能模块标识；核心网设备在服务规则集中确定对应的目标网络功能模块标识；向对应目标网络功能模块标识的网络功能发送所述消息。由于服务规则集中服务规则可进行修改，因此在网络中部署了新的功能业务或者更新已有的业务时（即网络功能动态调整的情况下），调整服务规则集中的该网络功能对应的一条或者多条服务规则，再按照本发明方法实施例执行即可实现后续的消息交互过程，从而提高网络的执行效率。

Description

一种消息交互的方法、设备和系统 技术领域
本发明涉及通信领域，尤其涉及的是一种消息交互的方法、设备和系统。
背景技术
随着移动通信技术的高速发展，网络架构变得越来越复杂，演变出了许多不同的网络类型，如演进分组核心网络(Evolved Packet Core，EPC)，在EPC中采用了网元(Network Element，NE)的架构方式，该架构包含的典型网元如移动性管理实体(Mobility Management Entity，MME)，服务网关(Serving Gateway，S-GW)，分组数据网络网关(Packet Data Network Gateway，P-GW)等。当前EPC的网络功能是通过网元中固化的服务特性和处理逻辑以及网元之间的流程消息来实现的，例如实现移动性管理，承载管理、位置管理等。举例来说，用户的接入服务需要MME、S-GW、P-GW以及网络中其他网元如策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)、归属用户服务器(Home Subscriber Server，HSS)等共同协作并且通过标准化定义的业务流程逻辑来完成的。因此当前EPC所能提供的网络功能的特性是固化的。
而随着商业模式的不断拓展以及技术的不断发展，用户的业务需求也会随之发生变化。用户业务会需求更多的服务模式和更优的服务特性，例如超低时延通信的需求，高可靠性通信的需求等等，并由此带来对新的网络功能的需求。而EPC网络所提供的网络功能是固化并分散在各个网元中的，因此如果需要引入新的网络功能来支持用户的需求，则EPC网络需要重新定义和设计网元的处理逻辑和流程交互。这样的重新设计对于设备商来说意味着开发周期长，成本高，对于网络运营商来说意味着不能及时发布新的网络功能，提供新业务给用户。传统的EPC网络中，HSS会根据UE的类型和能力为UE预先设定一个使用类型，并且网络为根据每一种使用类型设定一个对应的核心网，具体的转发过程为，首先由网络接收到UE的请求后，会发送至网络中默认的MME，而后该默认的MME会首先向HSS获取该UE对应的核心网，然后由EPC网络中的转发单元将该请求重定向到对应核心网的MME，完成网络的选择。
因此，传统EPC的网元架构在需要在HSS的支持下，才能完成网络选择 的过程，并且由于是根据使用类型配置对应的核心网，会使得功能网络内部的定时器触发的请求事件无法调用网络中的服务来处理，而必须通过网络内部的其他方式实现，另外，当网络中部署了新的功能业务或者更新已有的业务时，需要UE和HSS均修改使用类型来选择到新的网络，可扩展性差。
发明内容
本发明实施例提供了一种消息交互的方法、设备和系统，在网络功能动态调整的情况下，实现该网络功能模块与其他网络实体的消息交互。
有鉴于此，本发明实施例第一方面提供一种消息交互的方法，可包括：
核心网设备首先会接收消息，该消息中可携带消息标识；而后会由该核心网设备获取服务规则集，且该服务规则集中的服务规则包括消息标识和与所述消息标识对应的网络功能模块标识；在确定服务规则集之后，核心网设备会从该服务规则集中确定出与消息标识对应的目标网络功能模块标识；网络功能模块标识并最终向对应目标网络功能模块标识的网络功能发送该消息。
可以看出，核心网设备通过先接收带有消息标识的消息，一并还会获取服务规则集，由于服务规则集中具有消息标识与网络功能模块标识的对应关系，因此核心网设备会从服务规则集中确定出对应消息标识的网络功能模块标识，而后就可通过网络功能模块标识找到对应的网络功能，并将消息发送至该网络功能，整个网络功能选择期间并不需要HSS的介入，仅通过服务规则集中预先存储的对应关系即可为消息快速定位，并且对于消息并没有特别的要求，可以是内部的消息，也可以是外部的消息，只要该消息中携带有消息标识即可正确选择出对应的网络功能。
在一些实施例中，消息为所述核心网设备所在服务系统内的设备发送的消息或者由服务系统外的设备发送的消息。可以理解的是，消息的产生途径实际可以分为两种，一种所在服务系统内的设备发送的消息，一种是服务系统外的设备发送的外部消息请求消息，两种消息均可触发选择网络功能的过程。
在一些实施例中，消息标识包括定时器超时标识、消息类型标识和功能类型标识之中的至少一种。可以理解的是，消息标识可以根据消息的不同而不同，能够对应反应对应类型的消息。
在一些实施例中，所述核心网设备获取服务规则集包括：所述核心网设备从存储设备获取所述服务规则集；或者，所述核心网设备从核心网设备本地读取所述服务规则集。核心网设备获取服务规则集的方式，实际有多种，例如可以是存储设备中获取，服务规则集可以预先设定并存储在存储设备中；再例如，可以是核心网设备从核心网设备本地读取，即该配置好的服务规则集会放在核心网设备的本地，如核心网设备内的存储介质中，在核心网设备获取该服务规则集时，能够从存储介质中直接读取。
在一些实施例中，外部的消息一般可为请求消息，该请求消息中可携带有所述消息类型标识。
在一些实施例中，该请求消息的非接入层NAS消息头包含所述消息类型标识，所述方法还包括：所述核心网设备根据所述请求消息的NAS消息头确定所述消息类型标识。其中，请求消息中携带消息类型标识，具体的，该消息类型标识可以是在请求消息的NAS消息头中，该消息类型标识的确定可以从请求消息的NAS消息头中提取。
在一些实施例中，消息包括触发消息和/或请求消息，触发消息中携带有所述定时器超时标识，所述请求消息中携带有所述消息类型标识。内部消息根据类型不同可分为触发消息以及请求消息，两种消息分别携带有不同的标识，请求消息的为消息类型标识，触发消息的为定时器超时标识。
在一些实施例中，由于消息标识可包括三种情况，因此，核心网设备在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识包括：核心网设备在所述服务规则集中根据消息中携带的定时器超时标识、消息类型标识和功能类型标识之中的至少一个确定对应的目标网络功能模块标识。
在一些实施例中，所述消息为触发消息，所述核心网设备在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识包括：所述核心网设备在所述服务规则集中根据所述触发消息中携带的定时器超时标识确定对应的目标网络功能模块标识。消息为触发消息类型的情况下，由于触发消息中会携带有定时器超时标识，从而能够根据该定时器超时标识确定出对应的目标网络功能模块标识，能增强本发明方法的可实现性。
在一些实施例中，所述消息为请求消息，所述核心网设备在所述服务规则 集中确定与所述消息标识对应的目标网络功能模块标识包括：所述核心网设备在所述服务规则集中根据所述请求消息中携带的消息类型标识确定对应的目标网络功能模块标识。对于请求消息以及请求消息来说，由于这两种请求消息中都会携带有消息类型标识，因此可通过消息类型标识从服务规则集中确定出目标网络功能模块标识。
在一些实施例中，服务规则集中的服务规则还包含网络切片标识，且所述服务规则中的网络切片标识，消息标识和网络功能模块标识对应，所述方法还包括：所述核心网设备根据所述消息确定所述消息的网络切片标识；此时，核心网设备在所述服务规则集中确定与所述消息标识对应的网络功能模块标识包括：核心网设备在所述服务规则集中根据所述消息标识和所述消息的网络切片标识确定所述网络功能模块标识。可以看出，在一些情况中，例如网络切片的应用场景中，多个网络切片内很可能具有相同的消息标识，此时仅通过消息标识是无法找到对应的网络功能模块标识，必须先通过消息标识关联网络切片标识从而确定出网络切片后，再通过此消息标识在网络切片对应的服务规则集中确定对应的网络功能模块标识。
在一些实施例中，所述消息中还携带有UE标识，所述服务规则集中的服务规则还包含网络切片标识，所述网络切片标识对应网络切片，所述核心网设备在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识包括：所述核心网设备根据所述UE标识确定网络切片标识；所述核心网设备根据所述网络切片标识确定服务规则组，所述服务规则组由具有相同网络切片标识的服务规则组成；所述核心网设备根据所述消息的消息标识从所述服务规则组中确定与所述消息标识对应的目标网络功能模块标识。可以看出，在应用于网络切片服务时，消息中还会携带UE标识，该UE标识会唯一对应一个网络切片，即该UE的所需的网络功能都由该网络切片提供，每个网络切片对应一个网络切片标识，该网络切片标识会被包含在服务规则集中的每条服务规则中，因此，可将整个服务规则集分为几个服务规则组，每个服务规则组负责服务一个网络切片。
在一些实施例中，所述消息中还携带有UE标识，每个网络切片对应一个服务规则集，所述服务规则集中还包含网络切片标识，所述网络切片标识对 应网络切片，所述核心网设备在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识包括：所述核心网设备根据所述UE标识确定网络切片标识；所述核心网设备根据所述网络切片标识确定目标服务规则集；所述核心网设备根据所述消息的消息标识从所述目标服务规则集中确定与所述消息标识对应的目标网络功能模块标识。可以看出，在应用于网络切片服务时，消息中还会携带UE标识，该UE标识会唯一对应一个网络切片，即该UE的所需的网络功能都由该网络切片提供，每个网络切片对应一个网络切片标识，该网络切片标识会被包含在服务规则集中的每条服务规则中，因此，可设置多个服务规则集，每个服务规则集负责服务一个网络切片，每个服务规则集中设置网络切片标识。
在一些实施例中，所述核心网设备根据所述消息确定所述消息的网络切片标识包括：当所述消息中携带有UE标识时，所述核心网设备根据所述UE标识确定所述消息的网络切片标识；或者，所述核心网设备获取所述消息中携带的网络切片标识。可以看出，通过消息确定消息的网络切片标识的方式有两种，其一是该消息中携带有UE标识，而UE标识能够对应网络切片标识，其二，该网络切片标识被直接携带在消息中。
在一些实施例中，网络切片标识的确定可以有两种方式，在消息中携带有UE标识时，所述核心网设备根据所述UE标识确定所述消息的网络切片标识包括：所述核心网设备根据所述UE标识在签约数据中心查询并确定所述消息的网络切片标识，所述消息的网络切片标识与UE标识的对应关系存储在所述签约数据中心内；或者，所述核心网设备通过解析所述UE标识确定所述消息的网络切片标识，所述UE标识内携带有网络切片标识。核心网设备根据UE标识获取网络切片标识的方式实际有多种，例如，在具有UE标识的情况下，可以直接从签约数据中心获取网络切片标识；又例如，再UE标识中携带有网络切片标识，通过解析UE标识即可获取网络切片标识。
在一些实施例中，所述核心网设备在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识之前还包括：所述核心网设备根据所述触发消息中的定时器超时标识确定对应的UE标识，产生所述定时器超时标识的定时器与UE标识相对应。在消息为触发消息的情况下，UE标识一般来说并不会 直接被包含在触发消息中，而是在UE上下文数据库中，由于定时器的维护与UE对应，因此通过定时器超时标识可对应的UE，进而在UE的上下文数据库中确定出UE标识。
本发明第二方面还提供一种核心网设备，可包括：
接收模块，用于接收消息，所述消息中携带有消息标识；
处理模块，用于获取服务规则集，所述服务规则集中的服务规则包括消息标识和与所述消息标识对应的网络功能模块标识；并在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识；
发送模块，用于向所述对应目标网络功能模块标识的网络功能发送所述消息。
在一些实施例中，所述消息为所述核心网设备所在服务系统中内的设备发送的请求消息或者由服务系统外的设备发送的外部消息。
在一些实施例中，所述消息标识包括定时器超时标识，消息类型标识和功能类型标识中的至少一种。
在一些实施例中，所述处理模块具体用于：
从核心网设备本地读取所述服务规则集；或者，
从存储设备获取所述服务规则集。
在一些实施例中，所述请求消息中携带有所述消息类型标识。
在一些实施例中，所述请求消息的非接入层NAS消息头包含所述消息类型标识，所述处理模块还用于，
根据所述请求消息的NAS消息头确定所述消息类型标识。
在一些实施例中，所述消息包括触发消息和/或请求消息，所述触发消息中携带有所述定时器超时标识，所述请求消息中携带有所述消息类型标识。
在一些实施例中，所述处理模块具体用于，
在所述服务规则集中根据消息中携带的定时器超时标识、消息类型标识和功能类型标识之中至少一种确定对应的目标网络功能模块标识。
在一些实施例中，所述服务规则集中的服务规则还包含网络切片标识，且所述服务规则中的网络切片标识，消息标识和网络功能模块标识对应，所述处理模块还用于根据所述消息确定所述消息的网络切片标识；
则处理模块在所述服务规则集中确定与所述消息标识对应的网络功能模块标识包括：
所述处理模块在所述服务规则集中根据所述消息标识和所述消息的网络切片标识确定所述网络功能模块标识。
在一些实施例中，所述消息中还携带有UE标识，所述服务规则集中的服务规则还包含网络切片标识，所述网络切片标识对应网络切片，所述处理模块具体用于，
根据所述UE标识确定网络切片标识；
根据所述网络切片标识确定服务规则组，所述服务规则组由具有相同网络切片标识的服务规则组成；
根据所述消息的消息标识从所述服务规则组中确定与所述消息标识对应的目标网络功能模块标识。
在一些实施例中，所述消息中还携带有UE标识，每个网络切片对应一个服务规则集，所述服务规则集中还包含网络切片标识，所述网络切片标识对应网络切片，所述服务规则集中还包含网络切片标识，所述处理模块具体用于，
根据所述UE标识确定网络切片标识；
根据所述网络切片标识确定服务规则集，所述服务规则组由具有相同网络切片标识的服务规则组成；
根据所述消息的消息标识从所述服务规则组中确定与所述消息标识对应的目标网络功能模块标识。
在一些实施例中，当所述消息中携带有UE标识时，所述处理模块具体用于，
所述处理模块根据所述UE标识在签约数据中心查询并确定所述消息的网络切片标识，所述消息的网络切片标识与UE标识的对应关系存储在所述签约数据中心内；或者，
所述处理模块通过解析所述UE标识确定所述消息的网络切片标识，所述UE标识内携带有网络切片标识。
在一些实施例中，所述处理模块还用于，
根据所述触发消息中的定时器超时标识确定对应的UE标识，产生所述定 时器超时标识的定时器与UE标识相对应。
本发明第三方面还提供一种网络系统，可包括：
核心网设备，用于接收消息，所述消息包括消息标识；获取服务规则集，所述服务规则集中的服务规则包括所述消息标识和与所述消息标识对应的网络功能模块标识；所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识；向对应所述目标网络功能模块标识的网络功能模块发送所述消息；
所述网络功能模块，用于接收所述核心网设备发送的所述消息，并提供网络功能服务。
在一些实施例中，所述消息标识包括定时器超时标识，消息类型标识和功能类型标识中的至少一种。
在一些实施例中，所述消息为所述核心网设备所在服务系统内的设备发送给所述核心网设备的消息或者由所述服务系统外的设备发送给所述核心网设备的消息。
在一些实施例中，所述核心网设备具体用于从核心网设备本地读取所述服务规则集；或者，
所述系统还包括存储设备，用于存储所述服务规则集，则所述核心网设备具体用于从所述存储设备获取所述服务规则集。
在一些实施例中，所述服务规则集中的服务规则还包含网络切片标识，且所述服务规则中的网络切片标识，消息标识和网络功能模块标识对应时，所述核心网设备还用于根据所述消息确定所述消息的网络切片标识；
所述核心网设备具体用于在所述服务规则集中根据所述消息标识和所述消息的网络切片标识确定所述网络功能模块标识。
在一些实施例中，所述核心网设备具体用于：
当所述消息中携带有UE标识时，根据所述UE标识确定所述消息的网络切片标识；或者，
获取所述消息中携带的网络切片标识。
在一些实施例中，当所述消息中携带有UE标识时，所述核心网设备具体用于：
根据所述UE标识在签约数据中心查询并确定所述消息的网络切片标识， 所述消息的网络切片标识与UE标识的对应关系存储在所述签约数据中心内；或者，
通过解析所述UE标识确定所述消息的网络切片标识，所述UE标识内携带有网络切片标识。
本发明第四方面另外还提供一种网络系统，可包括：
网络功能模块，用于定义服务规则，并提供所述服务规则对应的网络功能，所述服务规则包括消息标识和与所述消息标识对应的网络功能模块标识；
服务管理框架模块，用于注册所述服务规则和与所述服务规则对应的网络功能模块；还用于将所述服务规则组成的服务规则集并存储在所述网络系统内；
过程协调模块，用于：
接收消息，所述消息包括消息标识；
获取服务规则集；
在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识；网络功能模块标识网络功能模块标识
向对应所述目标网络功能模块标识的网络功能发送所述消息。
在一些实施例中，所述过程协调模块还具体用于：
向所述服务管理框架模块发送所述网络功能模块标识；
所述服务管理框架模块还用于：
接收并根据所述网络功能模块标识确定对应所述网络功能模块标识的网络功能模块的网络地址；
将所述网络地址发送至所述过程协调模块。
在一些实施例中，所述过程协调模块还用于：
根据所述网络地址将所述消息转发至所述网络地址对应的网络功能模块。
在一些实施例中，所述服务管理框架模块还用于：
确定已注册的网络功能模块的服务规则发生改变；
根据改变后的服务规则集更新存储在所述网络系统内的服务规则集。
在一些实施例中，所述过程协调模块具体用于：
从服务规则集中确定与所述消息类型标识和/或定时器超时标识对应的目 标网络功能模块标识。
在一些实施例中，所述网络系统还包括签约数据中心，用于预定义并存储所述网络切片标识与UE标识的对应关系，所述网络切片标识对应网络切片；
所述过程协调模块具体用于：
根据所述UE标识确定网络切片标识，所述服务规则集中的服务规则还包含所述网络切片标识；
根据所述网络切片标识确定服务规则组，所述服务规则组由具有相同网络切片标识的服务规则组成；
根据所述消息标识从所述服务规则组中确定与所述消息标识对应的目标网络功能模块标识。
在一些实施例中，所述网络系统还包括网络功能组件模块，所述网络功能组件模块用于供一个或多个所述网络功能模块调用，并包括以下模块中的至少一种：用户数据管理模块，安全模块，承载管理模块，策略管理模块。
在一些实施例中，所述服务管理框架模块还用于增加、删除和更新所述网络功能模块之中的至少一种。
从以上技术方案可以看出，本发明实施例具有以下优点：核心网设备获取服务规则集，根据收到的消息中携带的消息标识及服务规则集确定出目标网络功能模块标识，并将该收到的消息发送给对应所述目标网络功能模块标识的网络功能模块。由于服务规则集中服务规则可进行修改，因此在网络中部署了新的功能业务或者更新已有的业务时(即网络功能动态调整的情况下)，调整服务规则集中的该网络功能对应的一条或者多条服务规则，再按照本发明方法实施例执行即可实现后续的消息交互过程，从而提高网络的执行效率。
附图说明
图1是现有EPC网络的结构示意图；
图2是本发明实施例的系统架构示意图；
图3本发明实施例的消息交互方法的一个实施例图；
图4是本发明实施例的消息交互方法的另一个实施例图；
图5是本发明实施例的消息交互方法的另一个实施例图；
图6是本发明实施例的核心网设备的一个实施例图；
图7是本发明实施例的网络系统的一个实施例图；
图8是本发明实施例的网络系统的一个实施例图；
图9是本发明实施例的核心网设备的一个实施例图；
图10是本发明实施例的网络系统的一个实施例图。
具体实施方式
本发明实施例提供了一种消息交互的方法、设备和系统，用于在网络中部署了新的功能业务或者更新已有的业务时，修改服务规则集中的服务规则即可实现后续的消息交互过程，提高网络的执行效率。为了使本技术领域的人员更好地理解本发明方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分的实施例，而不是全部的实施例。
以下分别进行详细说明。
本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或模块的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或模块，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或模块。
为了便于理解，先给出本发明实施例应用场景的一个具体的例子，如图1所示，图1是现有EPC网络的结构示意图，在该EPC网络架构中用户设备(User Equipment，UE)是指在该通信系统中获得服务的终端，它包括但不限于移动宽带(Mobile Broad Band，MBB)类型终端、机器类通信(Machine Type Communication，MTC)类型终端、车辆间通信(Vehicle to Vehicle,V2V)类型终端等。UE通过接入网可以接到核心网中，并由核心网为用户设备提供相应的业务，其中核心网的控制面为UE提供包括UE的注册接入、位置更新、位置切换、承载建立等在内的控制面服务。应理解，这里的核心网也可以称作 非接入网络，这里的非接入网络是指不同于接入网络并提供以下至少一种或者多种功能组合的网络，这些功能可以包括：非接入层(Non-Access Stratum，NAS)信令处理，NAS安全，鉴权(authentication)，接入控制(access control)，授权(authorization)，承载管理(bearer management)或者会话管理(session management)，移动性管理,位置管理，合法监听，漫游等。
图2是本发明实施例的系统架构示意图，在图2所示的架构下，核心网控制面功能采用“网络功能+服务化架构”的方式来实现。相对于传统的核心网架构如EPC架构，本发明架构取消了EPC架构中包含的移动性管理实体(Mobility Management Entity，MME)，服务网关(Serving Gateway，S-GW)，分组数据网络网关(Packet Data Network Gateway，P-GW)等在内的传统网元的设置，并将原本分散在各个网元的网络功能串联起来，融合重构为以网络功能为基本单元的服务化控制面架构。其中网络功能是指一个或多个相对独立和完整的逻辑功能，能够处理来自UE或网络中其他实体的相似类型的服务请求，并负责执行相应的处理流程，从而完成相应的网络功能。例如UE的注册接入服务，UE的位置更新服务等。
具体来说，图2所示的架构主要包括外部接口功能模块(External Interface Function，EIF)，过程协调模块(Process Coordinator，PC)，网络功能模块，网络功能组件模块以及服务管理框架模块。下面分别说明各组成部分的功能。应理解，此处所述的组成部分的名称并不唯一，为描述方便，以下行文以上述名称对各个组成部分进行描述。
EIF是整个服务化控制面架构的外部接口功能，它处理与其他网元的消息交互。EIF负责实现该控制面架构中的功能模块(包括PC，网络功能模块，网络功能组件模块等)与实体之间的接口功能，包括通信信道的建立，连接上下文的维护，消息的协议封装和解封装，消息的转发和接收等。
PC是整个服务化控制面架构的统一网络功能协调模块，它负责根据来自服务化控制面中的功能模块发送的消息或者服务化控制面之外的其他网络实体(例如UE、RAN Node、用户面实体、或其他网络的网络实体)发送的消息，选择能够处理上述消息的网络功能模块，并将上述消息发送到所选的网络功能模块。在此过程中，PC还可以负责完成服务请求冲突的检测和处理(例如， 当新服务请求与当前服务流程冲突时，决定服务请求的优先执行、挂起或拒绝)。
需要说明的是，视实际部署情况而定，EIF和PC可以分开部署，也可以合一部署。合一部署时，这个合一部署的设备可以同时完成EIF和PC的功能。举例来说，这种合一部署的设备可以是控制面交互管理功能(Control Plane Interaction ManagerFunction，CPIMF)。
网络功能模块是整个服务化控制面架构所实现的网络功能的基本组成单元，也可称为网络功能单元。网络功能模块是一个相对独立和完整的逻辑功能实体，它能够接收某一类型或某些类型的消息，处理消息并完成相应的网络功能。例如，网络功能模块可以完成UE的注册接入服务，UE的位置更新服务，UE的切换服务等。此外，网络功能模块还可以是一个或者多个按照业务执行顺序组合得到的网络功能组件模块。
网络功能组件模块是整个服务化控制面架构中所抽象和独立出的通用网络功能单元，也可称为网络功能组件单元。网络功能组件模块一般可供一个或多个网络功能模块调用，用来完成网络功能模块实现的网络功能中所需的特定的通用网络功能。举例来说，安全验证服务，承载建立服务可以由网络功能组件模块来完成，并且可被UE注册接入服务以及UE的切换服务等调用。此外，网络功能组件模块还可以嵌入在网络功能模块中。
服务管理框架模块是整个服务化控制面架构中执行服务管理功能的单元。网络中的网络功能单元，如网络功能模块和网络功能组件模块，可以通过功能注册的方式，将网络功能单元的相关信息(如服务规则集)保存到服务管理框架模块中。网络中其他实体可以通过服务管理框架模块获取网络功能单元的相关信息，以实现网络功能单元的发现和调用。
此外还需说明的一点是，该服务化控制面架构不同于传统网元对用户数据的分散式和重复式存储，而是将网络功能的业务处理逻辑和所要处理的用户数据解耦，将传统网元中存储的用户上下文，安全上下文和承载上下文，以及网络策略等放置到统一的数据库中存储，并由通用化数据服务提供对数据库的访问。
此外，在现有技术中，EPC网络为支持多种用户不同的服务需求，提出了 专用核心网(Dedicated Core，DECOR)技术，即利用功能定制化的网元集合来构建一个区域性的专用网络，并采用专用核心网络选择技术来为某些有特定服务需求的用户设备选择相应的专用网络，从而保证该部分用户能够接入到专用网络并选择到对应的网络功能。该网络选择技术的具体步骤如下：
(1)UE向无线接入网节点发送请求消息；
(2)无线接入网节点由于无法获知UE对应的DECOR，因此，无线接入网节点在保证负载均衡的情况下会为UE任意选择一个移动性管理网元(Mobility Management Entity，MME)作为默认MME，然后将接收到的UE的请求消息发送给该默认MME；
(3)默认MME处理UE的请求消息，并获取UE的签约信息，然后根据UE的签约信息确定UE对应的DECOR MME，如果UE对应的DECOR MME与默认MME不一致的话，那么默认MME将向无线接入网节点发送重定向消息；
(4)无线接入网节点接收到重定向消息后，将UE的请求消息重新发送给UE对应的DECOR MME。
由此可见，上述方法在选择UE对应的网络时，一般都需要一个重定向的过程。因此将该网络选择技术应用到5G网络架构中存在以下问题：由于网络切片一般是针对某一类型的UE进行优化配置并提供定制化服务的网络，不同的网络切片对UE的验证方式存在一定的差异，因此，任意选择的网络切片可能因为无法对UE进行身份验证而不能获取UE的签约数据，从而无法确定UE真正对应的网络切片，也就无法为UE选择对应的网络功能；另外，无线接入网节点在为UE选择网络切片时可能要进行重定向的过程，而在重定向的过程中，无线接入网节点要缓存UE的请求消息，并且需要重复发送请求消息，这样就大大增加了无线接入网节点的负担。
应理解，本发明实施例的选择网络功能的方法和装置并不限于如图1和图2所示的网络架构，本发明实施例还可以应用到其他与网络功能模块化或服务化类似的网络架构中。
为了解决上述问题，本发明实施例提供了一种消息交互的方法，
请参阅图3，图3本发明实施例的消息交互的方法的一个实施例图，如图 3所示，该方法可包括以下内容：
301、核心网设备接收消息。
其中，消息包括核心网设备所在服务系统内的设备发送的消息或服务系统外的设备发送的请求消息，不论是服务系统内的消息还是外部消息中均携带有消息标识。
需要说明的是，本发明实施例中的服务系统是指通信网络中的控制面，例如可以是上述服务化控制面架构。
本发明实施例中的网络系统是指通信网络，可以包含服务系统。
需要说明的是，消息标识包括定时器超时标识，消息类型标识和功能类型标识中的至少一种。
需要说明的是，该核心网设备可以是图2所示的PC或者EIF或者二合一部署的具有CPIMF的设备，且该核心网设备具备网元选择功能，当核心网设备为PC时，UE的请求消息可以通过接入网元如无线基站等转发到达EIF，再由EIF处理后转发到核心网设备，而如果核心网设备为EIF的话，那么核心网设备可以直接通过接入网元如无线基站等的转发获取UE的请求消息。
可选的，消息包括两种，一种是核心网设备所在服务系统内部的设备发送的消息，消息又可分为请求消息和触发消息；另外还有一种是核心网设备所在服务系统外的设备发送的消息，这些消息均可分为请求消息和触发消息，请求消息和触发消息的产生方式是不相同的，触发消息可以由核心网设备所在服务系统的内部或者外部的维护的定时器触发而产生的消息，请求消息是这些设备发出的带有请求服务的消息。
可选的，对于消息中包含的消息标识，可包括三种，一种是消息类型标识，一种是定时器超时标识，还有一种是功能类型标识。具体的，消息类型标识可以是消息头中携带的类型标识，指示该消息的类型，例如非接入层NAS消息的消息头中所包含的消息类型字段；定时器超时标识可以是定时器超时后发出的触发消息中携带的标识，可以指示是哪一个UE的哪一种类型的定时器发生了超时；功能类型标识可以是消息或消息头中携带的功能类型标识，用来指示消息具体请求哪种类型的网络功能，例如在消息的协议描述(Protocol descriptor)字段指示消息所请求的移动管理功能或会话管理功能。
对于请求消息来说，一般携带的是消息类型标识和/或功能类型标识，而对于触发消息来说，其携带的可以是定时器超时标识。
举例来说，可以在核心网设备所在的服务系统内或者外的数据库内维护一个事件定时器，当定时器发生超时时，就会发出一个触发消息，核心网设备在接收到这个触发消息后可确定出该触发消息携带的定时器超时标识，又举例来说，当核心网设备接收到来自服务系统内部的请求消息或者来自外部的请求消息时，即可确定出对应的消息类型标识和/或功能类型的消息，以便进行后续的处理。
302、核心网设备获取服务规则集。
步骤302和步骤301之间没有先后顺序。
其中，所述服务规则集中的服务规则包括消息标识和与所述消息标识对应的网络功能模块标识。即当消息标识是消息类型标识，则为消息类型标识对应网络功能模块标识；当消息标识是定时器超时标识时，则为定时器超时标识对应网络功能模块标识；当消息标识是功能类型标识时，则为功能类型标识对应网络功能模块标识。
需要说明的是，对于服务规则集的获取可以有多种方式，可选的，第一种，核心网设备从其他存储设备获取所述服务规则集；第二种，所述核心网设备从核心网设备本地读取所述服务规则集。对于第一种方式来说，存储设备上述服务规则集生成后，网络功能模块可以通过功能注册的方式将服务规则集提供给服务管理框架模块，由服务管理框架模块统一保存和管理所有网络功能模块所生成的服务规则集。核心网设备可从服务管理框架模块获取所需网络功能模块的服务规则集并在本地保存。
由于服务规则集是由预先设定好的服务规则构成的集合，因此该服务规则集在生成后可以存放在存储设备内，在核心网设备开始工作时，就会从该存储设备内读取该服务规则集到核心网设备；另外一种方式中，服务规则集在生成完成后会直接存储在核心网设备的本地，例如作为配置文件配置在核心网设备上，消息标识消息网络功能模块标识消息其中网络功能模块标识与用于服务UE的网络功能相对应。
可以理解的是，核心网设备在确定出对应的消息标识后，可以由消息标识 作为基础，确定出网络功能模块标识。下面以表1-1对服务规则进行说明：
表1-1
Figure PCTCN2016076927-appb-000001
其中，Event ID表示事件标识，Message Type ID表示消息类型标识，Timer Trigger ID表示定时器超时标识，Function Type ID表示功能类型标识，NF ID表示网络功能模块标识。可以看出，一个服务规则包含五项内容，可以通过Message Type ID或Timer Trigger ID或Function ID均可唯一确定出一个Event ID，而通过一个Event ID又可确定出一个NF ID，从而确定对应的网络功能模块。网络功能模块标识可以是网络功能对应的标识信息，也可以是网络功能对应的访问地址或其他能够唯一标识该网络功能的信息。
可选的，服务规则除表1-1所示情形之外，还可以如下表1-2所示的服务规则：
Figure PCTCN2016076927-appb-000002
消息标识可以是消息类型标识Message Type ID,也可以是定时器超时标识Timer Trigger ID，还可以是功能类型标识Function Type ID。即可以通过Message Type ID或Timer Trigger ID或Function ID均可唯一确定出一个NF ID，从而确定对应的网络功能模块。
可选的,在仅具有消息类型标识时,还可采用如下表1-3所示的服务规则:
表1-3
NF_A ID Message Type 1 Message Type 2 Message Type 3
NF_B ID Message Type 4 Message Type 5 Message Type 6
其中，NF_A ID，NF_B ID是网络功能模块标识，Message Type表示消息类型标识，可以看出，网络功能NF_A可以处理Message Type为1，2，3的消息，网络功能NF_B可以处理Message Type为4，5，6的消息。从而根据消息的消息类型就可以确定出对应的能够处理该消息的网络功能模块标识。
上述具体的采用表1-1、表1-2还是表1-3可根据实际情况决定，具体不 作限定。
表1-1、表1-2和表1-3的具体生成可以由网络功能模块来定义。网络功能模块可以根据自身能够处理的消息来生成上述服务规则集。具体来说，网络功能模块能够处理的消息包括核心网设备所在服务系统内部的设备发送的消息和核心网设备所在服务系统外部的设备发送的消息。网络功能模块根据自身能够处理的消息标识和自身的网络功能模块标识来生成上述服务规则集的具体形式。
可选的，当网络功能模块在实际运行的过程中，可以动态地更新服务规则集。具体来说，网络功能模块根据更新后的服务决定自身能够处理的消息标识，以及自身的网络功能模块标识重新生成上述服务规则集的具体形式。
上述服务规则集生成后，网络功能模块可以通过功能注册的方式将服务规则集提供给服务管理框架模块，由服务管理框架模块统一保存和管理所有网络功能模块所生成的服务规则集。核心网设备可从服务管理框架模块获取所需网络功能模块的服务规则集并在本地保存。
下面结合表1-1的服务规则的生成进行具体说明，首先是消息类型标识，在服务于某个或某些消息的网络功能模块在生成后，网络会为该网络功能模块定义和分配与该网络功能唯一对应的网络功能模块标识。该网络功能模块标识根据自身能够处理的消息定义消息标识，消息标识用于表示在消息标识所对应的消息到达时，可以调用该网络功能模块来处理该消息。进一步地，网络功能模块会为该消息标识定义消息对应表，即为每一个消息标识配置消息类型标识，定时器超时标识，和功能类型标识中的至少一个，表示任何一个携带有消息类型标识，定时器超时标识，和功能类型标识中的至少一个标识的消息到达时，可以调用该网络功能模块来处理该消息。或者，消息标识Message ID本身就可以是消息类型标识Message Type ID,也可以是定时器超时标识Timer Trigger ID，还可以是功能类型标识Function Type ID。即可以通过Message Type ID或Timer Trigger ID或Function ID均可唯一确定出一个NF ID，从而确定对应的网络功能模块。
表1-2的服务规则的生成与表1-1的生成类似，只是不再定义消息标识， 而是直接定义消息对应表，即为每一个消息标识配置消息类型标识，定时器超时标识，和功能类型标识中的至少一个，表示任何一个携带有消息类型标识，定时器超时标识，和功能类型标识中的至少一个标识的消息到达时，可以调用该网络功能模块来处理该消息。
表1-3的服务规则的生成与表1-2类型，这里不再赘述。
举例来说，核心网设备可以是EIF或者PC或者两者合一的CPIMF，以核心网设备是CPIMF为例，定时器超时标识指服务系统内或者外的定时器超时时向CPIMF发送超时消息，CPIMF在接收到该定时器超时标识则表示对应的消息标识所指的消息被触发；而消息类型标识或功能类型标识则是来自请求消息，消息类型标识通常在请求消息的协议头之中，CPIMF在接收到该请求消息后，解析该请求消息并根据协议头获得消息类型标识或功能类型标识。
举例来说，以Detach请求为例，当UE发起Detach请求到达CPIMF，或网络数据库中维护的Detach定时器发生超时通知CPIMF，则对应此时Detach事件发生，会触发Detach消息标识，从而通过Detach消息标识确定出对应的网络功能模块。
303、在服务规则集中确定与消息标识对应的目标网络功能模块标识。
其中，在确定出了服务规则集后，就可以根据消息标识在服务规则集中确定对应的目标网络功能模块标识。
可选的，服务规则集中的服务规则还包含网络切片标识，且所述网络切片标识，消息标识和网络功能模块标识存在对应关系，此时，核心网设备在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识可包括：
Aa、核心网设备根据所述消息确定所述消息的网络切片标识；
其中，所述消息中携带有所述消息的网络切片标识。
可选的，所述消息中携带有UE标识，该UE标识可以是IMEI、IMSI，或者是其他可以唯一标识UE的标识，核心网设备根据所述UE标识确定网络切片标识。
Ab、核心网设备在所述服务规则集中根据所述消息标识和所述消息的网络切片标识确定所述网络功能模块标识。
其中，核心网设备根据所述消息的网络切片标识确定服务规则组。可以理 解的是，应用于网络切片的网络功能模块可在每一个服务规则集中的服务规则上加上网络切片标识，即每一服务规则均会对应一个网络切片标识，同一网络切片标识的服务规则组成服务规则组，该服务规则组能提供网络切片的各种功能。可以理解的是，在核心网设备确定出了网络切片标识后，会进一步确定服务规则组，由于服务规则组由同一网络切片标识的服务规则组成，并对应一个网络切片，因此核心网设备仅需要通过所述消息的网络切片标识即可确定出与所述消息的网络切片标识相同的服务规则组，在查找匹配消息对应的网络功能模块时，仅需要从该服务规则组中查找即可，能够减小查找匹配的范围，提高查找效率。
可选的，除了从服务规则集中划分出多个服务规则组的方式，还可直接设置多个服务规则集，此时核心网设备或者存储设备内会存储多个服务规则集，一个服务规则集内的服务规则具有相同的网络切片标识，一个服务规则集对应一个网络切片，本方式中，Ba步骤与前述Aa步骤相同；
步骤Bb具体可为，核心网设备根据所述网络切片标识确定服务规则集。
其中，在Ba步骤确定出了所述消息的网络切片标识后，即可从多个服务规则集中确定与所述消息的网络切片标识对应的服务规则集。核心网设备根据所述消息的消息标识从所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识。
需要说明的是，核心网设备根据UE标识确定网络切片标识可采用多种方式，以下给出其中两种方式，
其一、UE标识与网络切片标识由签约数据中心预定义对应关系，可选的，核心网设备根据UE标识确定网络切片标识包括：核心网设备根据UE标识签约数据中心查询并确定网络切片标识，网络切片标识与UE标识的对应关系由签约数据中心预定义并存储在签约数据中心内。
其二、UE标识不仅包含UE标识信息，还包括UE标识对应的网络切片标识。可选的，核心网设备根据UE标识确定网络切片标识包括：
核心网设备通过解析UE标识确定网络切片标识，UE标识为由签约数据中心预分配的携带有网络切片标识的UE标识。
可以理解的是，在采用方式一的情形下，核心网设备可直接从签约数据中 心查询到UE标识对应的网络切片标识；在采用方式二的情形下，核心网设备可直接解析该增强型UE标识，从中获得网络切片标识，具体的可根据实际进行选择，此处不作限定。
上面是针对UE的请求消息的网络切片的配置及选择过程，下面针对消息的网络切片的配置及选择过程进行说明。
作为可选的，消息为核心网设备所在服务系统内的消息，核心网设备根据消息在服务规则集中确定目标服务规则包括：
Ca、核心网设备根据该消息中的定时器超时标识从服务规则集中确定服务规则组。
其中，服务规则组由核心网设备所在的服务系统中的网络功能模块根据UE的服务需求从服务规则集中配置；
可以理解的是，针对一类UE一般具有固定属于该UE的服务规则，而服务规则集中则并不区分是哪些UE的服务规则，因此可服务规则集进行分组，每组对应一类UE的需求。
Cb、核心网设备根据定时器超时标识从服务规则集中确定目标服务规则。
可以理解的是，在确定出定时器超时标识后，即可确定出对应的消息标识，进而能够在服务规则组中确定出具有该消息标识的服务规则，由于服务规则组中一般不会出现针对同一事件的两种不同的服务规则，而是事件与服务规则一对一的关系。
作为可选的，服务规则集中的服务规则中还包括网络切片标识，核心网设备根据内部消息中的定时器超时标识从服务规则集中确定服务规则组包括：
核心网设备根据所定时器超时标识确定网络切片标识；
可以理解的是，由于在定义事件的过程已将将定时超时标识对应了消息标识，通过消息标识所在的服务规则即可获知网络切片标识。
Cc、核心网设备根据网络切片标识确定服务规则组。
其中，服务规则组包括由签约数据中心根据UE的服务需求从服务规则集中配置的具有相同网络切片标识的服务规则。
可以理解的是，在确定出网络切片标识后，即可确定出具有相同网络切片标识的服务规则。
作为可选的，核心网设备根据定时器超时标识从服务规则组中确定目标服务规则包括：
核心网设备根据所定时器超时标识确定对应的消息标识；
可以理解的是，由于定时器超时标识与消息标识具有对应关系，因此通过定时器超时标识确定对应的消息标识仅需要查询对应关系即可。
Cd、核心网设备根据消息标识从服务规则组中确定目标服务规则。
可以理解的是，核心网设备区别于302步骤中从服务规则集中选取，而是在具有相同网络切片标识的服务规则中选取，由于选择范围更小，选择速度将会更加迅速，带来的直接效果是响应时间的缩短。
304、向网络功能模块发送所述消息。
其中，核心网设备在确定目标服务规则中的消息标识后，即可确定出对应的网络功能模块标识，从而向对应的网络功能模块发送所述消息。
可选的，核心网设备确定的网络功能模块标识仅为网络功能模块的标识信息，则核心网设备根据网络功能模块的标识向服务管理框架模块请求对应的网络功能模块的访问地址。服务管理框架模块返回对应的网络功能模块的访问地址，核心网设备使用访问地址向所述网络功能模块发送所述消息。
可以看出，本发明实施例中的核心网设备首先接收消息，而后获取服务规则集，并通过消息消息中携带的消息标识在服务规则集中确定出目标网络功能模块标识，服务规则包括消息标识和与所述消息标识对应的网络功能模块标识，找到目标网络功能模块标识就能够找到对应该目标服务规则的网络功能消息消息请求消息请求消息。可以看出，本发明实施例由于服务规则集中服务规则可进行修改，因此在网络中部署了新的功能业务或者更新已有的业务时(即网络功能动态调整的情况下)，调整服务规则集中的该网络功能对应的一条或者多条服务规则，再按照本发明方法实施例执行即可实现后续的消息交互过程，从而提高网络的执行效率。下面以Attach网络服务的流程为例，说明Attach网络服务的配置过程及该服务配置在EIF为UE的Attach请求选择网络切片服务时所发挥的作用。
Attach网络服务的配置过程：
首先，在对应UE的Attach请求的Attach网络服务生成后，会为该服务 配置唯一的网络功能模块标识，即Attach NF ID，同时会定义一个消息标识，该标识表示触发Attach NF ID的事件，该消息标识即Attach Message ID，将Attach Message ID与Attach NF ID作为一个Attach网络服务规则保存。
其次，定义Attach Message ID的事件对应表，即Attach Message ID所对应的由UE发送的Attach请求，即由Attach请求作为Attach Message ID触发的条件，由于没有网络内部触发的Attach事件，所以Timer Trigger ID设置为N/A，即最终的Attach Message ID对应Attach Message Type ID，将Timer Trigger ID设置为N/A和Attach Message Type ID加入Attach网络服务规则。
接着，确定Attach网络服务所在的服务规则组，并在该Attach网络服务规则加上该服务规则组中统一的网络切片标识，即Slice ID，最终生成的Attach网络服务规则如下表2所示：
表2
Figure PCTCN2016076927-appb-000003
接着，将配置好的Attach网络服务规则加入核心网设备，例如是网络切片A的配置文件内。
最后，当运营商决定部署该网络切片A时，将网络切片A实例化时，即提供网络切片A实际的运营环境以及所需的软硬件资源，将网络切片A中保存或存储在策略数据库的所有服务规则组成的服务规则组配置到EIF上，完成整个配置过程。
二、EIF使用Attach网络服务的服务规则集为UE的Attach请求选择对应的网络功能的过程。
首先，在UE向网络签约注册时，签约数据中心会预定义一个网络切片，例如是上述配置的网络切片A，此时，签约数据中心有两种将UE与网络切片A联系起来，情形一是，生成UE的UE标识和网络切片A的对应关系表，若UE标识为唯一标识UE的标识，例如IMSI、IMEI等，则为唯一标识与Slice ID_A的对应关系,并保存在策略数据库中；情形二是为UE分配一个包含了网络切片A的Slice ID_A ID的增强型的唯一标识。
下面以情形一进行说明：
结合图3的实施例，请参阅图4，图4是本发明实施例的消息交互的方法的另一个实施例图，如图4所示，包括UE、EIF、策略数据库和Attach网络服务实例，该Attach请求的执行过程可包括：
401、策略数据库存储UE的唯一标识与Slice ID_A的对应关系；
其中，该步骤是实际执行步骤的先决步骤，实际可直接在配置过程中完成，而不一定在使用过程中进行配置，该唯一标识可以是IMSI或者IMEI等唯一识别UE的标识。
402、UE向EIF发送Attach请求消息；
其中，该步骤是实际UE服务处理过程中，UE会向核心网设备发送Attach请求消息，以便于核心网设备对该请求消息进行识别。
403、EIF根据Attach请求消息中的唯一标识从策略数据库中查询该唯一标识对应的Slice ID_A；
404、策略数据库返回该唯一标识对应的Slice ID_A；
其中，步骤403和步骤404仅是查询切片ID的一种情况，另外还有一种情况可以是预先将所有唯一标识与对应的Slice ID_A均存储在EIF上，此时EIF仅需根据唯一标识查询本地即可确定出Slice ID_A。
405、EIF根据Slice ID_A确定对应的服务规则组；
406、EIF根据Attach请求消息的NAS消息头中确定Attach Message Type ID；
需要说明的是，此步骤406并非必须步骤，EIF也可能直在步骤403中从Attach请求消息解析唯一标识时，直接解析出该Attach Message Type ID，只有在Attach Message Type ID被包含在NAS消息头中才需要上述步骤406。
407、EIF根据Attach Message Type ID获得对应的Attach Message ID；
其中，在获取了Attach Message Type ID即可根据对应的存储表确定对应的Attach Message ID。
408、EIF以Attach Message ID作为检索条件在服务规则组中确定出Attach网络服务规则中的Attach NF ID；409、EIF将该Attach请求消息转发至该Attach NF ID对应的Attach网络服务实例。
需要说明的是，步骤407和步骤408也并非必须步骤，该步骤407及408 也可以直接被包含在步骤409之中进行，在发送Attach请求消息时，直接根据Attach Message Type ID在服务规则组中定位Attach NF ID即可。
下面进行情形二的说明：
请参阅图5，图5是本发明实施例的消息交互的方法的另一个实施例图，如图5所示，包括UE、EIF、策略数据库和Attach网络服务实例，UE标识为增强型IMSI，其中步骤504至步骤508与步骤405至步骤409类似，不再赘述，该Attach请求的执行过程还可包括：
501、策略数据库中存储为UE分配的包含Slice ID_A的增强型IMSI；
502、UE向EIF发送Attach请求消息；
503、EIF解析Attach请求消息中的增强型IMSI确定Slice ID_A。
上面对本发明实施例的消息交互的方法进行了介绍，下面对本发明实施例的核心网设备进行介绍，请参阅图6，图6是本发明实施例的核心网设备的一个实施例图，可包括：
接收模块601，用于接收消息，所述消息中携带有消息标识。
其中，该接收模块601用于实现图3所示实施例中步骤301，该接收模块601的相关功能说明与图3所示实施例中步骤301的说明类似，此处不再赘述。
可选的，该消息为所述核心网设备所在服务系统中内的设备发送的消息或者由服务系统外的设备发送的消息。这两种消息中均带有消息标识，也均可被该接收模块601接收。此外，可选的，消息标识包括定时器超时标识、消息类型标识和功能类型标识之中的至少一种；由于消息除了分为内部的和外部的两种之外，还可根据其功能分为请求消息和触发消息，两种消息可分别携带不同类型的标识，例如请求消息可携带消息类型标识，触发消息可携带定时器超时标识。具体的关于两种标识的说明请参阅图3所示实施例针对步骤301的说明，此处不再赘述。
处理模块602，用于获取服务规则集，所述服务规则集中的服务规则包括消息标识和与所述消息标识对应的网络功能模块标识。
其中，该接收模块602用于实现图3所示实施例中步骤302，该接收模块602的相关功能说明与图3所示实施例中步骤302的说明类似，此处不再赘述。
需要说明的是，获取服务规则集的方式有多种，可选的，从所述存储设备 获取所述服务规则集；或者，从核心网设备本地读取所述服务规则集。此两种方式均可获取到服务规则集，鉴于服务规则集的存储形式，可以是一配置文件，因此可以直接配置在核心网设备的本地存储上，或者也可以存储在存储设备中，因此从存储设备获取的方式有两种情形，一种是核心网设备上未存储服务规则集的情况，一种是虽然有配置文件，但是需要更新的情况，此时可直接从存储设备获取，具体的可参阅图3所示实施例中针对步骤302的说明，此处不再赘述。
处理模块603，用于在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识。
其中，该接收模块603用于实现图3所示实施例中步骤303，该接收模块603的相关功能说明与图3所示实施例中步骤303的说明类似，此处不再赘述。
可选的，所述处理模块具体用于，在所述服务规则集中根据消息中携带的定时器超时标识和/或消息类型标识确定对应的目标网络功能模块标识。可以理解的是，由于消息中携带的可能是定时器超时标识，也可能是消息类型标识，当然，还可能是定时器超时标识加消息类型标识的情况，这三种情形由于有表1-1、表1-2或是表1-3的存储结构，因此均能够顺利的找到对应的目标网络功能模块标识，具体的可参见图3所示实施例中步骤303的说明类似，此处不再赘述。
此外，对于网络切片的应用场景，可选的，所述消息中还携带有UE标识，所述服务规则集中的服务规则还包含网络切片标识，所述网络切片标识对应网络切片，所述处理模块603具体用于，根据所述UE标识确定网络切片标识；根据所述网络切片标识确定服务规则组，所述服务规则组由具有相同网络切片标识的服务规则组成；根据所述消息的消息标识从所述服务规则组中确定与所述消息标识对应的目标网络功能模块标识。
可以看出，在应用于网络切片服务时，消息中还会携带UE标识，该UE标识会唯一对应一个网络切片，即该UE的所需的网络功能都由该网络切片提供，每个网络切片对应一个网络切片标识，该网络切片标识会被包含在服务规则集中的每条服务规则中，因此，可将整个服务规则集分为几个服务规则组，每个服务规则组负责服务一个网络切片。
当然，网络切片情况下，除了从一个服务规则集中配置多个服务规则组的情形，还可直接配置多个服务规则集，每个服务规则集对应一个网络切片。
可选的，所述消息中还携带有UE标识，每个网络切片对应一个服务规则集，所述服务规则集中还包含网络切片标识，所述网络切片标识对应网络切片，该处理模块603具体用于：根据所述UE标识确定网络切片标识；根据所述网络切片标识确定目标服务规则集；根据所述消息的消息标识从所述目标服务规则集中确定与所述消息标识对应的目标网络功能模块标识。
可以看出，在应用于网络切片服务时，消息中还会携带UE标识，该UE标识会唯一对应一个网络切片，即该UE的所需的网络功能都由该网络切片提供，每个网络切片对应一个网络切片标识，该网络切片标识会被包含在服务规则集中的每条服务规则中，因此，可设置多个服务规则集，每个服务规则集负责服务一个网络切片，每个服务规则集中设置网络切片标识。
以上两种情形均可用于网络切片应用场景，具体的可参见图3所示实施例中针对步骤303的说明，此处不再赘述。
此外，网络切片标识的确定也可以有两种方式，可选的，该处理模块603具体用于，根据所述UE标识在签约数据中心查询并确定网络切片标识，所述网络切片标识与UE标识的对应关系存储在所述签约数据中心内；或者，所述核心网设备通过解析所述UE标识确定网络切片标识，所述UE标识内携带有由所述签约数据中心预分配的网络切片标识。
可以看出，核心网设备根据UE标识获取网络切片标识的方式实际有多种，例如，在具有UE标识的情况下，可以直接从签约数据中心获取网络切片标识；又例如，在UE标识中携带有网络切片标识，通过解析UE标识即可获取网络切片标识。具体的可参见图3所示实施例中针对步骤303的说明，此处不再赘述。
处理模块603还用于根据所述消息中的定时器超时标识确定对应的UE标识，产生所述定时器超时标识的定时器与UE标识相对应。
可以理解的是，对于触发消息来说，UE标识一般来说并不会直接被包含在触发消息中，而是UE上下文数据库中，由于定时器的维护与UE对应，因此通过定时器超时标识可对应的UE，进而在UE的上下文数据库中确定出UE 标识。具体的可参见图3所示实施例中针对步骤303的说明，此处不再赘述。
发送模块604，用于向所述对应目标网络功能模块标识的网络功能发送所述消息。
其中，该接收模块604用于实现图3所示实施例中步骤304，该接收模块604的相关功能说明与图3所示实施例中步骤304的说明类似，此处不再赘述。
上面对本发明实施例的核心网设备进行了介绍，下面对有上述核心网设备的本发明实施例的网络系统进行介绍，可运行于通用架构的服务器上，请参阅图7，图7是本发明实施例的网络系统的一个实施例图，其中核心网设备为过程协调模块，该网络系统可包括：
核心网设备701，用于接收消息，所述消息包括消息标识；获取服务规则集，所述服务规则集中的服务规则包括所述消息标识和与所述消息标识对应的网络功能模块标识；所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识；向对应所述目标网络功能模块标识的网络功能模块702发送所述消息；
其中，该核心网设备701为图6所示实施例中的核心网设备，该核心网设备703能够实现图3所示实施例中步骤301至步骤304，该核心网设备703的相关功能说明与图3所示实施例中步骤301至步骤304的说明类似，此处不再赘述。
网络功能模块702，用于接收所述核心网设备701发送的所述消息，并提供网络功能服务。
可以看出，网络功能模块702，主要用于接收核心网设备701发送的消息，并提供对应该消息的网络功能服务，网络功能模块702能够自定义服务规则和服务规则集，并且还可将该服务规则或者服务规则集存储在网络功能模块702上，当然也可以注册在服务管理框架模块上。
可选的，所述消息标识包括定时器超时标识，消息类型标识和功能类型标识中的至少一种。三种标识的功能以及各自对应方式请参阅图3所示实施例针对步骤302的说明，此处不再赘述。
可选的，消息为所述核心网设备701所在服务系统内的设备发送给所述核心网设备701的消息或者由所述服务系统外的设备发送给所述核心网设备701 的消息。可以理解的是，该消息的来源可以有两种，服务系统内的和服务系统外的，对于两种消息的处理方式请参阅图3所示实施例针对步骤302的说明，此处不再赘述。
可选的，所述核心网设备701具体用于从核心网设备701本地读取所述服务规则集；或者，所述系统还包括存储设备，用于存储所述服务规则集，则所述核心网设备701具体用于从所述存储设备获取所述服务规则集。
需要说明的是，获取服务规则集的方式有多种，可选的，从存储设备获取所述服务规则集；或者，从核心网设备701本地读取所述服务规则集。此两种方式均可获取到服务规则集，鉴于服务规则集的存储形式，可以是一配置文件，因此可以直接配置在核心网设备701的本地存储上，或者也可以存储在存储设备中，因此从存储设备获取的方式有两种情形，一种是核心网设备701上未存储服务规则集的情况，一种是虽然有配置文件，但是需要更新的情况，此时可直接从存储设备获取，具体的可参阅图3所示实施例中针对步骤302的说明，此处不再赘述。
此外，在网络切片应用场景中，可选的，所述服务规则集中的服务规则还包含网络切片标识，且所述服务规则中的网络切片标识，消息标识和网络功能模块标识对应时，所述核心网设备701还用于根据所述消息确定所述消息的网络切片标识；则所述核心网设备701具体用于在所述服务规则集中根据所述消息标识和所述消息的网络切片标识确定所述网络功能模块标识。
可以看出，在一些情况中，例如网络切片的应用场景中，多个网络切片内很可能具有相同的消息标识，此时仅通过消息标识是无法找到对应的网络功能模块标识，必须先通过消息标识关联网络切片标识从而确定出网络切片后，再通过此消息标识在网络切片对应的服务规则集中确定对应的网络功能模块标识。具体的可参阅图3所示实施例中针对步骤303的说明，此处不再赘述。
此外，可选的，当所述消息中携带有UE标识时，根据所述UE标识确定所述消息的网络切片标识；或者，获取所述消息中携带的网络切片标识。可以理解的是，网络切片标识除了通过上述方式，将消息标识和网络切片标识均关联至网络功能模块标识上，从而通过两种标识确定网络功能模块标识；在消息中携带有UE标识时，可以直接通过UE标识确定消息的网络切片标识，进行 通过消息内的消息标识确定出对应网络切片标识的服务规则集中的服务规则，从而确定出网络功能模块标识。具体的可参阅图3所示实施例中针对步骤303的说明，此处不再赘述。
可选的，当所述消息中携带有UE标识时，所述核心网设备701具体根据UE标识确定网络切片标识可以有两种，一种是根据所述UE标识在签约数据中心查询并确定所述消息的网络切片标识，所述消息的网络切片标识与UE标识的对应关系存储在所述签约数据中心内；另一种是，通过解析所述UE标识确定所述消息的网络切片标识，所述UE标识内携带有网络切片标识。两种方式均可通过UE标识准确获得对应网络切片标识，具体的可参阅图3所示实施例中针对步骤303的说明，此处不再赘述。
上面对本发明实施例的核心网设备进行了介绍，下面对具有上述核心网设备的本发明实施例的网络系统进行介绍。该网络系统可运行于通用架构的服务器上，请参阅图8，图8是本发明实施例的网络系统的一个实施例图，其中核心网设备为过程协调模块，该网络系统可包括：
网络功能模块801，用于定义服务规则，并提供所述服务规则对应的网络功能服务，所述服务规则包括消息标识和与所述消息标识对应的服务标识，所述服务标识对应所述网络功能服务。
服务管理框架模块802，用于注册所述服务规则和与所述服务规则对应的网络功能模块；还用于将所述服务规则组成的服务规则集并存储在所述网络系统内。
可以看出，网络功能模块801和服务管理框架模块802的功能相配合，能够实现服务规则的生成以及服务规则和服务规则集的注册，在完成注册后，使得其他设备能够按照该服务规则找到对应的网络功能服务，从而实现快速快速定位网络功能服务，以实现网络功能快速选择的效果。
过程协调模块803，用于接收消息，所述消息包括消息标识；获取服务规则集；在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识；向对应所述目标网络功能模块标识的网络功能服务发送所述消息。需要说明的是，该过程调模块803主要用于接收消息，并根据消息确定对应的服务规则，最后根据该服务规则转发至对应的网络功能服务；该过程调模块803与图 3所示实施例中的核心网设备的功能相同，具体可参见图3所示实施例中的核心网设备及其说明，此处不再赘述。
可选的，根据服务规则定位网络功能服务的具体过程有多种方式，下面以一种情形为例，过程协调模块803还具体用于：向所述服务管理框架模块802发送所述网络功能模块标识；
服务管理框架模块802还用于：接收并根据所述网络功能模块标识确定对应所述网络功能模块标识的网络功能模块的网络地址；将所述网络地址发送至所述过程协调模块803。
可以看出，首先由过程协调模块803确定出接收的消息的消息标识，进而通过服务规则集查询到对应的网络功能模块标识，并将该网络功能模块标识发送至服务管理框架模块802，由于服务管理框架模块802上注册有所有的网络功能模块801和网络功能服务，因此服务管理框架模块802会根据此网络功能模块标识确定出对应的网络功能模块801的网络地址，并将该网络地址返回给过程协调模块803，在获知网络地址后，可选的，该过程协调模块803会根据所述网络地址将所述消息转发至所述网络地址对应的网络功能模块801。
需要说明的是，在确定消息标识时，若服务规则集采用表1-1的格式，为两层对应关系，消息类型标识和定时器超时标识分别对应消息标识，而消息标识还对应网络功能模块标识，实际接收消息过程中，首先接收到的为消息类型标识和/或定时器超时标识，而后根据这两种标识之中的至少一种确定出消息标识，再通过消息标识确定出对应的目标网络功能模块标识；而若是表1-2或者表1-3的形式，则直接由消息类型标识和/或定时器超时标识确定对应的网络功能模块标识即可。
此外，服务管理框架模块802由于注册了所有的服务规则、网络功能模块和对应的网络功能服务，因此该服务管理框架模块802能够在确定服务规则发生改变时，主动更新服务规则集；可选的，服务管理框架模块还用于：确定已注册的网络功能模块的服务规则发生改变；根据改变后的服务规则集更新存储在所述网络系统内的服务规则集。
需要说明的是，除了更新服务规则，还可以增加或者删除服务规则。
可选的，在切片网络的应用场景下，网络系统还包括签约数据中心804， 用于预定义并存储所述网络切片标识与UE标识的对应关系，所述网络切片标识对应网络切片。
此时，过程协调模块803确定目标网络功能模块标识的具体过程为：
根据所述UE标识确定网络切片标识，所述服务规则集中的服务规则还包含所述网络切片标识；
根据所述网络切片标识确定服务规则组，所述服务规则组由具有相同网络切片标识的服务规则组成；
根据所述消息标识从所述服务规则组中确定与所述消息标识对应的目标网络功能模块标识。
可以看出，该签约数据中心804主要用于提供网络切片标识与UE标识的对应关系，通过该对应关系，在具有UE标识的情况下能够确定出网络切片标识。而后，过程协调模块803会据此网络切片标识找出对应的服务规则组，并根据消息标识确定服务规则组中的服务规则，从而找到对应的目标网络功能模块标识。
需要说明的是，此情形对应于一个服务规则集对应多个服务规则组，而若是多个服务规则集的情形，则根据网络切片标识确定出的是一个服务规则集。
需要说明的是，网络系统还可包括：网络功能服务组件模块，所述网络功能服务组件模块用于供一个或多个所述网络功能模块调用，所述网络功能服务组件模块包括以下模块中的至少一种：用户数据管理模块，安全模块，承载管理模块，策略管理模块。
可以看出，网络功能服务组件模块主要用于供一个或多个所述网络功能模块调用，这些组件可以是用户数据管理模块，安全模块，承载管理模块，策略管理模块之中的至少一种，以增强网络系统的功能。
下面对本发明实施例中核心网设备的结构进行描述，本发明实施例中的核心网设备可以是通用处理机结构，请参阅图9，图9是本发明实施例的核心网设备的一个实施例图，其中，核心网设备9可包括均与总线相连接的至少一个处理器901、至少一个接收器902、至少一个发送器903和存储器904，存储器904包括内存和外存，内存用于存储存储处理器901将要执行的计算机指令的和相关数据，外存用于存储核心网设备的配置文件及其他文件，处理器901 运行内存中的计算机执行指令以执行上述图3所示实施例中步骤301至步骤304；本发明实施例涉及的核心网设备可以具有比图9所示出的更多或更少的部件，可以组合两个或更多个部件，或者可以具有不同的部件配置或设置，各个部件可以在包括一个或多个信号处理和/或专用集成电路在内的硬件、软件或硬件和软件的组合实现。
具体的，对于图6所示的实施例来说，该处理器901能实现图6所示实施例中的处理模块602的功能，该接收器902能实现图6所示实施例中的接收模块601，该发送器903能实现图6所示实施例中的发送模块603。
下面对本发明实施例中核心网设备的结构进行描述，本发明实施例中的网络系统可以是通用服务器架构，请参阅图10，图10是本发明实施例的网络系统的一个实施例图，其中，网络系统10可包括均与总线相连接的至少一个处理器1001、至少一个接收器1002、至少一个发送器1003和存储器1004，存储器1004包括内存和外存，内存用于存储存储处理器1001将要执行的计算机指令的和相关数据，外存用于存储网络系统的策略数据和其他各项数据，处理器1001运行内存中的计算机执行指令；本发明实施例涉及的核心网设备可以具有比图10所示出的更多或更少的部件，可以组合两个或更多个部件，或者可以具有不同的部件配置或设置，各个部件可以在包括一个或多个信号处理和/或专用集成电路在内的硬件、软件或硬件和软件的组合实现。
具体的，对于图8所示的实施例来说，该处理器1001能实现图8所示实施例中的网络功能模块801、服务管理框架模块802和过程协调模块803的功能，该处理器1001结合存储器1004能实现图8所示实施例中的签约数据中心804的功能，该接收器1002和发送器1003用于接收和发送服务系统内部或外部的消息。所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或 一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims (24)

  1. 一种消息交互的方法，其特征在于，包括：
    核心网设备接收消息，所述消息中携带有消息标识；
    所述核心网设备获取服务规则集，所述服务规则集中的服务规则包括所述消息标识和与所述消息标识对应的网络功能模块标识；
    所述核心网设备在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识；
    向对应所述目标网络功能模块标识的网络功能模块发送所述消息。
  2. 根据权利要求1所述的消息交互的方法，其特征在于：所述消息为所述核心网设备所在服务系统内的设备发送的消息或者由服务系统外的设备发送的消息。
  3. 根据权利要求1或2所述的消息交互的方法，其特征在于：所述消息标识包括定时器超时标识，消息类型标识和功能类型标识中的至少一种。
  4. 根据权利要求1至3中任一项所述的消息交互的方法，其特征在于，所述核心网设备获取服务规则集包括：所述核心网设备从核心网设备本地读取所述服务规则集；或者，
    所述核心网设备从存储设备中获取所述服务规则集。
  5. 根据权利要求1至4中任一项所述的消息交互的方法，其特征在于，所述服务规则集中的服务规则还包含网络切片标识，且所述服务规则中的网络切片标识，消息标识和网络功能模块标识对应，所述方法还包括：
    所述核心网设备根据所述消息确定所述消息的网络切片标识；
    则所述核心网设备在所述服务规则集中确定与所述消息标识对应的网络功能模块标识包括：
    所述核心网设备在所述服务规则集中根据所述消息标识和所述消息的网络切片标识确定所述网络功能模块标识。
  6. 根据权利要求5中所述的消息交互的方法，其特征在于，所述核心网设备根据所述消息确定所述消息的网络切片标识包括：
    当所述消息中携带有UE标识时，所述核心网设备根据所述UE标识确定所述消息的网络切片标识；或者，
    所述核心网设备获取所述消息中携带的网络切片标识。
  7. 根据权利要求6所述的消息交互的方法，其特征在于，当所述消息中携带有UE标识时，所述核心网设备根据所述UE标识确定所述消息的网络切片标识包括：
    所述核心网设备根据所述UE标识在签约数据中心查询并确定所述消息的网络切片标识，所述消息的网络切片标识与UE标识的对应关系存储在所述签约数据中心内；或者，
    所述核心网设备通过解析所述UE标识确定所述消息的网络切片标识，所述UE标识内携带有网络切片标识。
  8. 根据权利要求1至7中任一项所述的消息交互的方法，其特征在于，所述核心网设备为过程协调模块PC，外部接口功能模块EIF或者控制面交互管理功能CPIMF。
  9. 一种核心网设备，其特征在于，包括：
    接收模块，用于接收消息，所述消息中携带有消息标识；
    处理模块，用于获取服务规则集，所述服务规则集中的服务规则包括消息标识和与所述消息标识对应的网络功能模块标识；并在所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识；
    发送模块，用于向所述对应目标网络功能模块标识的网络功能发送所述消息。
  10. 根据权利要求9所述的核心网设备，其特征在于，所述消息为所述核心网设备所在服务系统中内的设备发送的请求消息或者由服务系统外的设备发送的外部消息。
  11. 根据权利要求9或10所述的核心网设备，其特征在于，所述消息标识包括定时器超时标识，消息类型标识和功能类型标识中的至少一种。
  12. 根据权利要求9至11中任一项所述的核心网设备，其特征在于，所述处理模块具体用于：
    所述处理模块用于从核心网设备本地读取所述服务规则集；或者，
    从存储设备获取所述服务规则集。
  13. 根据权利要求9至12中任一项所述的核心网设备，其特征在于，其 特征在于，所述服务规则集中的服务规则还包含网络切片标识，且所述服务规则中的网络切片标识，消息标识和网络功能模块标识对应，所述处理模块还用于根据所述消息确定所述消息的网络切片标识；
    则所述处理模块具体用于：
    所述处理模块在所述服务规则集中根据所述消息标识和所述消息的网络切片标识确定所述网络功能模块标识。
  14. 根据权利要求13所述的核心网设备，其特征在于，所述处理模块具体用于：
    当所述消息中携带有UE标识时，所述处理模块根据所述UE标识确定所述消息的网络切片标识；或者，
    所述处理模块获取所述消息中携带的网络切片标识。
  15. 根据权利要求14所述的核心网设备，其特征在于，当所述消息中携带有UE标识时，所述处理模块还具体用于：
    所述处理模块根据所述UE标识在签约数据中心查询并确定所述消息的网络切片标识，所述消息的网络切片标识与UE标识的对应关系存储在所述签约数据中心内；或者，
    所述处理模块通过解析所述UE标识确定所述消息的网络切片标识，所述UE标识内携带有网络切片标识。
  16. 根据权利要求9至15中任一项所述的核心网设备，其特征在于，所述核心网设备为过程协调模块PC，外部接口功能模块EIF或者控制面交互管理功能CPIMF。
  17. 一种网络系统，其特征在于，包括：
    核心网设备，用于接收消息，所述消息包括消息标识；获取服务规则集，所述服务规则集中的服务规则包括所述消息标识和与所述消息标识对应的网络功能模块标识；所述服务规则集中确定与所述消息标识对应的目标网络功能模块标识；向对应所述目标网络功能模块标识的网络功能模块发送所述消息；
    所述网络功能模块，用于接收所述核心网设备发送的所述消息，并提供网络功能服务。
  18. 根据权利要求17所述的网络系统，其特征在于：所述消息标识包括 定时器超时标识，消息类型标识和功能类型标识中的至少一种。
  19. 根据权利要求17或18所述的网络系统，其特征在于：所述消息为所述核心网设备所在服务系统内的设备发送给所述核心网设备的消息或者由所述服务系统外的设备发送给所述核心网设备的消息。
  20. 根据权利要求17至19中任一项所述的网络系统，其特征在于，
    所述核心网设备具体用于从核心网设备本地读取所述服务规则集；或者，
    所述系统还包括存储设备，用于存储所述服务规则集，则所述核心网设备具体用于从所述存储设备获取所述服务规则集。
  21. 根据权利要求17至20中任一项所述的网络系统，其特征在于，所述服务规则集中的服务规则还包含网络切片标识，且所述服务规则中的网络切片标识，消息标识和网络功能模块标识对应时，所述核心网设备还用于根据所述消息确定所述消息的网络切片标识；
    则所述核心网设备具体用于在所述服务规则集中根据所述消息标识和所述消息的网络切片标识确定所述网络功能模块标识。
  22. 根据权利要求21中所述的网络系统，其特征在于，所述核心网设备还具体用于：
    当所述消息中携带有UE标识时，根据所述UE标识确定所述消息的网络切片标识；或者，
    获取所述消息中携带的网络切片标识。
  23. 根据权利要求22所述的网络系统，其特征在于，当所述消息中携带有UE标识时，所述核心网设备还具体用于：
    根据所述UE标识在签约数据中心查询并确定所述消息的网络切片标识，所述消息的网络切片标识与UE标识的对应关系存储在所述签约数据中心内；或者，
    通过解析所述UE标识确定所述消息的网络切片标识，所述UE标识内携带有网络切片标识。
  24. 根据权利要求17至23中任一项所述的网络系统，其特征在于，所述核心网设备为过程协调模块PC，外部接口功能模块EIF或者控制面交互管理功能CPIMF。
PCT/CN2016/076927 2016-03-21 2016-03-21 一种消息交互的方法、设备和系统 WO2017161484A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201680083551.6A CN108886678B (zh) 2016-03-21 2016-03-21 一种消息交互的方法、设备和系统
PCT/CN2016/076927 WO2017161484A1 (zh) 2016-03-21 2016-03-21 一种消息交互的方法、设备和系统
US16/137,773 US20190029075A1 (en) 2016-03-21 2018-09-21 Message exchange method, device, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/076927 WO2017161484A1 (zh) 2016-03-21 2016-03-21 一种消息交互的方法、设备和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/137,773 Continuation US20190029075A1 (en) 2016-03-21 2018-09-21 Message exchange method, device, and system

Publications (1)

Publication Number Publication Date
WO2017161484A1 true WO2017161484A1 (zh) 2017-09-28

Family

ID=59900906

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/076927 WO2017161484A1 (zh) 2016-03-21 2016-03-21 一种消息交互的方法、设备和系统

Country Status (3)

Country Link
US (1) US20190029075A1 (zh)
CN (1) CN108886678B (zh)
WO (1) WO2017161484A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3462691A4 (en) * 2016-06-03 2019-04-10 Huawei Technologies Co., Ltd. METHOD, DEVICE, AND SYSTEM FOR DETERMINING NETWORK WAFER

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6806137B2 (ja) * 2016-03-23 2021-01-06 日本電気株式会社 基地局及び方法
EP3432652B1 (en) * 2016-04-05 2023-01-11 LG Electronics Inc. Method for processing access request from ue, and network node
JP6773116B2 (ja) * 2016-07-15 2020-10-21 日本電気株式会社 通信方法
US11019528B2 (en) * 2018-10-29 2021-05-25 Verizon Patent And Licensing Inc. Method and system for admission control with network slice capability
WO2020093247A1 (en) * 2018-11-06 2020-05-14 Zte Corporation A method and apparatus for attaching user equipment to a network slice
CN111506340B (zh) * 2019-01-31 2023-07-04 阿里巴巴集团控股有限公司 业务规则信息处理方法、装置及系统
CN114531385B (zh) * 2020-10-31 2022-12-27 华为技术有限公司 发送报文的方法、装置及系统
US20240107317A1 (en) * 2020-12-28 2024-03-28 Telefonaktiebolaget Lm Ericsson (Publ) Subscription Identifier for a Communication Network
EP4277438A4 (en) * 2021-01-15 2024-02-28 Guangdong Oppo Mobile Telecommunications Corp Ltd COMMUNICATION METHOD AND APPARATUS, DEVICE, AND STORAGE MEDIUM
CN115209564B (zh) * 2021-04-12 2024-04-30 成都鼎桥通信技术有限公司 网络切片匹配方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621435A (zh) * 2008-07-04 2010-01-06 华为技术有限公司 一种通用业务架构下业务调用的方法、装置与系统
WO2012178055A1 (en) * 2011-06-23 2012-12-27 Interdigital Patent Holdings, Inc. Mobile network virtualization
WO2016014728A1 (en) * 2014-07-22 2016-01-28 Parallel Wireless, Inc. Signaling storm reduction from radio networks
CN105338511A (zh) * 2014-06-25 2016-02-17 华为技术有限公司 网络拓扑隐藏方法和设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101019441B (zh) * 2004-06-22 2011-03-23 株式会社Ntt都科摩 用电模式认知数据包通信方法和装置
US20060282886A1 (en) * 2005-06-09 2006-12-14 Lockheed Martin Corporation Service oriented security device management network
US8365189B2 (en) * 2007-02-28 2013-01-29 International Business Machines Corporation Method and apparatus for a service control layer
CN102089775B (zh) * 2008-04-29 2016-06-08 泰必高软件公司 具有用于缓解和自动防护的责任约束服务等级协议及模式的服务性能管理器
US8140615B2 (en) * 2008-05-07 2012-03-20 International Business Machines Corporation Consolidated business service for integrating service oriented architecture services with customer resources
WO2017124003A1 (en) * 2016-01-15 2017-07-20 Idac Holdings, Inc. Mobility management for next generation mobile network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621435A (zh) * 2008-07-04 2010-01-06 华为技术有限公司 一种通用业务架构下业务调用的方法、装置与系统
WO2012178055A1 (en) * 2011-06-23 2012-12-27 Interdigital Patent Holdings, Inc. Mobile network virtualization
CN105338511A (zh) * 2014-06-25 2016-02-17 华为技术有限公司 网络拓扑隐藏方法和设备
WO2016014728A1 (en) * 2014-07-22 2016-01-28 Parallel Wireless, Inc. Signaling storm reduction from radio networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ETSI: "LTE; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access", ETSI TS 123 401 V8.18.0, 30 April 2013 (2013-04-30), pages 25 - 28, XP055425047 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3462691A4 (en) * 2016-06-03 2019-04-10 Huawei Technologies Co., Ltd. METHOD, DEVICE, AND SYSTEM FOR DETERMINING NETWORK WAFER
US10798646B2 (en) 2016-06-03 2020-10-06 Huawei Technologies Co., Ltd. Network slice determining method and system, and apparatus

Also Published As

Publication number Publication date
US20190029075A1 (en) 2019-01-24
CN108886678A (zh) 2018-11-23
CN108886678B (zh) 2020-03-10

Similar Documents

Publication Publication Date Title
WO2017161484A1 (zh) 一种消息交互的方法、设备和系统
CN109842906B (zh) 一种通信的方法、装置及系统
CN110603851B (zh) 一种基于切片的通信方法和设备
KR102442911B1 (ko) 네트워크 슬라이스 식별자의 선택
JP6995189B2 (ja) データ伝送方法、デバイス、およびシステム
US10389848B2 (en) Message transmission method and core network interface device
US11363447B2 (en) Method and device for managing and allocating binding service in a wireless network
WO2017075757A1 (zh) 选择网络功能服务的方法、装置和系统
JP2020504566A (ja) 移動通信システムでアクセス及び移動性管理機能を選択するための方法及び装置
US11729137B2 (en) Method and device for edge application server discovery
CN114175600B (zh) 一种获取信息的方法及装置
US20220103990A1 (en) Communication Method, Apparatus, and System
CN114223262A (zh) 用于网络功能服务发现的方法和装置
WO2019024650A1 (zh) 一种资源配置方法和装置
CN114365518A (zh) 一种通过服务应用影响核心网络中数据业务路由的方法
US11863519B2 (en) Communication method and apparatus for handling DNS messages
WO2014005551A1 (zh) 用于接近感知的ue配置方法、网络侧设备及系统
CN117177266A (zh) 一种地址获取方法及装置
WO2014177019A1 (zh) 一种接入制式的配置方法、设备及系统
CN106341851B (zh) 一种用于为指定终端建立专有承载的方法
EP3897013B1 (en) Method for accessing local network, and related device
WO2018053749A1 (zh) 一种呼叫方法、装置、终端及核心网系统
US20220330140A1 (en) Edge computing
WO2023070643A1 (en) Method, device, and system for core network node re-allocation in wireless network
WO2022022392A1 (zh) 一种终端设备的数据关联方法及装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16894843

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16894843

Country of ref document: EP

Kind code of ref document: A1