WO2018014172A1 - Business processing method and network equipment in core network - Google Patents

Business processing method and network equipment in core network Download PDF

Info

Publication number
WO2018014172A1
WO2018014172A1 PCT/CN2016/090406 CN2016090406W WO2018014172A1 WO 2018014172 A1 WO2018014172 A1 WO 2018014172A1 CN 2016090406 W CN2016090406 W CN 2016090406W WO 2018014172 A1 WO2018014172 A1 WO 2018014172A1
Authority
WO
WIPO (PCT)
Prior art keywords
coordinator
service
network
manager
message
Prior art date
Application number
PCT/CN2016/090406
Other languages
French (fr)
Chinese (zh)
Inventor
乔晓强
李岩
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2016/090406 priority Critical patent/WO2018014172A1/en
Publication of WO2018014172A1 publication Critical patent/WO2018014172A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Definitions

  • the present invention relates to the field of communications, and more particularly to a method and network device for service processing in a core network in the field of communications.
  • SAE System Architecture Evolution
  • 3GPP 3rd Generation Partnership Project
  • HSS Home Subscriber Server
  • S-GW Service Gateway
  • PDN GW Packet Data Network Gateway
  • Each network element in the core network is connected to each other through standard interfaces to meet the interworking between different device vendors.
  • the peer-to-peer network element interaction model is used to implement mutual communication and remote calling between different subsystems.
  • the network element and all existing network elements need to be defined.
  • Interactive interface, and interface development and testing involve all network elements, and the flexibility is relatively poor.
  • the manner in which the interactive interface is defined point-to-point enables tight coupling between the interacting network elements and reduces the reusability of the network element.
  • the embodiments of the present invention provide a method and a network device for processing a service in a core network, and can select and invoke different network functions for different service scenarios to implement an on-demand elastic networking.
  • an embodiment of the present invention provides a method for service processing in a core network, where the core network includes a first coordinator and at least one network function NF, and the method includes: the first coordinator receives the first a request message sent by the network element, where the request message is used to request processing of the service of the UE; the first coordinator processes the service according to the service flow corresponding to the request message and the request message, The business process is used to invoke the at least one NF that is required to process the service.
  • the embodiment of the invention can call the network in the core network according to the service flow corresponding to the request message.
  • the function is to process the service of the UE, and the network function includes the function of the virtualized network element in the core network.
  • the embodiment of the present invention converts the service deployment into a software deployment, and can select and invoke different network functions for different service scenarios to implement an on-demand elastic networking, so that the network has flexible scalability, openness, and evolution capability.
  • the at least one NF includes at least two NFs, and the business process is used to invoke the at least two NFs in a logical order.
  • the coordinator can first call NF 1 according to the business process, then call NF 2 and NF 3 at the same time, then call NF 4 , and finally call NF 5 .
  • the number of NFs to be called is at least two, an input message of the NF that is called later may be constructed according to the output message returned by the previously invoked NF.
  • the first coordinator processes the service according to the request message and the service flow corresponding to the service, including: the first coordinator according to the request message and the service process, Generating an input message for each of the at least one NF; the first coordinator processes the service according to the input message of each of the NFs.
  • the first coordinator processes the service according to the input message of each NF, including: the first coordinator acquires an output message of each NF, where each NF The output message is that each NF is generated according to the input message of each NF; the first coordinator determines a processing result for the service according to the output message of each NF.
  • the NF may generate an output message based on the input message and return the output message to the first coordinator.
  • the NF input message is only used to notify the NF in one direction, and the NF may not need to generate an output message.
  • the first coordinator updates the context of the UE according to the output message of each NF.
  • the context of the UE may be updated according to the output message returned by the previously invoked NF, and then the input message of the NF that is called later is constructed according to the context of the UE.
  • the first coordinator may further generate an input of each NF in the at least one NF according to the request message and the service flow.
  • the first coordinator generates an input message of each NF in the at least one NF according to the request message and the service flow, including: the first coordinator according to the context and location of the UE
  • the business process generates an input message for each of the at least one NF.
  • the second network element includes a user subscription information storage unit, a radio access network RAN node, or a second coordinator, where the second coordinator is disposed in the core network.
  • the NF can be implemented as a stateless service, that is, the state of the UE, the context information of the UE, or the interaction information between the UE and each network element may not be saved in the NF. Since the NF in the embodiment of the present invention is a stateless service, the call of the NF is more flexible, thereby improving the reusability of the NF, thereby making the deployment of the network more flexible.
  • the core network further includes a coordinator manager
  • the method further includes: the first coordinator receiving the service flow sent by the coordinator manager.
  • the method further includes: the first coordinator sending a return message to the first network element according to a processing result of the service, so that the first network element can determine, by the core network, the request message. process result.
  • an embodiment of the present invention provides a method for service processing in a core network, where the core network includes a coordinator manager, a network function NF, and a coordinator, and the method includes: the coordinator manager determines to process the a flow of a service for indicating at least one network function NF required to process the service; the coordinator manager determining information of the at least one NF according to the flow; the coordinator manager is based on Generating, by the process and the information of the at least one NF, a business process for processing the service, where the business process is used to invoke at least one NF required to process the service; the coordinator manager to the first coordination And sending the service process, so that the first coordinator processes the service according to the service process.
  • the embodiment of the present invention can process the service of the UE according to the network function in the core network according to the service process, and the network function includes the function of the virtualized network element in the core network.
  • the embodiment of the present invention converts the service deployment into a software deployment, and can select and invoke different network functions for different service scenarios to implement an on-demand elastic networking, so that the network has flexible scalability, openness, and evolution capability.
  • the at least one NF includes at least two NFs, and the process is further used to indicate a logical sequence of the at least two NFs that are required to be used, where the service flow is used to invoke the according to the logical sequence. At least two NFs.
  • the coordinator can first call NF 1 according to the business process, then call NF 2 and NF 3 at the same time, then call NF 4 , and finally call NF 5 .
  • the core network further includes an NF manager, where the coordinator manager determines the information of the at least one NF according to the process, including: the coordinator manager determines a requirement in the at least one NF The created NF; the coordinator manager sends the type of the NF that needs to be created to the NF manager, so that the NF manager creates the NF that needs to be created according to the type of the NF; the coordinator management The device receives information of the NF created by the NF manager sent by the NF manager.
  • the coordinator manager determines the information of the at least one NF according to the process, including: the coordinator manager determines a requirement in the at least one NF The created NF; the coordinator manager sends the type of the NF that needs to be created to the NF manager, so that the NF manager creates the NF that needs to be created according to the type of the NF; the coordinator management The device receives information of the NF created by the NF manager sent by the NF manager.
  • the coordinator manager determines that the existing NF can be shared, the coordinator can directly determine the information of the existing NF, and generate a service flow according to the information of the existing NF.
  • the coordinator manager can send the type of the NF that needs to be created to the NF manager.
  • the information about the NF includes an interface parameter of the NF and an address of the NF.
  • the embodiment of the present invention provides a network device, where the method of the foregoing first aspect or any possible implementation of the first aspect is implemented, where the network device includes Or a module of the method in any of the possible implementations of the first aspect.
  • the embodiment of the present invention provides a network device, where the method of any of the foregoing second aspect or the second aspect is implemented, where the network device includes Or a module of the method in any of the possible implementations of the second aspect.
  • an embodiment of the present invention provides a network device, where the network device includes: a memory, a processor, a transceiver, and a bus system. Wherein the memory and the processor are coupled by the bus system for storing instructions for executing instructions stored by the memory, and when the processor executes the instructions stored by the memory, the performing causes the processing The method of the first aspect or any possible implementation of the first aspect is performed.
  • an embodiment of the present invention provides a network device, where the network device includes: a memory, a processor, a transceiver, and a bus system. Wherein the memory and the processor are coupled by the bus system for storing instructions for executing instructions stored by the memory, and when the processor executes the instructions stored by the memory, the performing causes the processing The method of the second aspect or any of the possible implementations of the second aspect is performed.
  • a seventh aspect of the present invention provides a computer readable medium for storing a computer program, the computer program comprising any possible implementation party for performing the first aspect or the first aspect The instruction of the method in the formula.
  • an embodiment of the present invention provides a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the second aspect or any possible implementation of the second aspect.
  • FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a core network according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a deployment service process according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for service processing in a core network according to an embodiment of the present invention.
  • FIG. 5 is a schematic interaction flowchart of a method for service processing in a core network according to an embodiment of the present invention.
  • FIG. 6 is a schematic interaction flowchart of a method for service processing in a core network according to another embodiment of the present invention.
  • FIG. 7 is a schematic interaction flowchart of a method for service processing in a core network according to another embodiment of the present invention.
  • FIG. 8 is a schematic interaction flowchart of a method for service processing in a core network according to another embodiment of the present invention.
  • FIG. 9 is a schematic block diagram of a network device in accordance with an embodiment of the present invention.
  • FIG. 10 is a schematic block diagram of a network device according to another embodiment of the present invention.
  • FIG. 11 is a schematic block diagram of a network device according to another embodiment of the present invention.
  • FIG. 12 is a schematic block diagram of a network device according to another embodiment of the present invention.
  • the access network may be a radio access network (RAN), and specifically, may be a base station.
  • the base station may be a Global System for Mobile communication (GSM) system or a Base Transceiver Station (BTS) in a Code Division Multiple Access (CDMA) system, or may be a wideband code division multiple access ( A base station (NodeB) in a Wideband Code Division Multiple Access (WCDMA) system, which may also be an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a base station device, a small base station device, etc. in a future 5G network.
  • GSM Global System for Mobile communication
  • BTS Base Transceiver Station
  • CDMA Code Division Multiple Access
  • a base station (NodeB) in a Wideband Code Division Multiple Access (WCDMA) system which may also be an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a base station device, a small
  • the user equipment can communicate with one or more core networks via a radio access network, and the UE can be called an access terminal, a terminal device, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, and a remote terminal.
  • the UE may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), or a wireless communication function.
  • FIG. 1 shows the architecture of the SAE.
  • the SAE architecture is composed of an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) and an evolved EPC.
  • the node of the access network may be a base station (for example, an eNodeB).
  • the EPC includes the MME, the HSS, the S-GW, and the PDN-GW, and further includes a Policy Control and Charging Rules Function (PCRF) and a General Packet Radio Service (GPRS) support node. (Serving GPRS Support Node, SGSN).
  • PCRF Policy Control and Charging Rules Function
  • GPRS General Packet Radio Service
  • the MME is responsible for the mobility management of the control plane, including user context and mobility state management.
  • the HSS stores user subscription information.
  • the S-GW is a user plane anchor between 3GPP access networks and is an interface of E-UTRAN.
  • the PDN GW is a user plane anchor between the 3GPP access network and the non-3GPP access network, and is an interface of the external PDN network.
  • the logical network element S-GW and the PDN GW are all deployed in one (except for individual cases, such as roaming), and are generally referred to as gateways.
  • the embodiment of the present invention provides a core network as shown in FIG. 2, where the core network includes a coordinator 131, a network function (NF) 132, and a coordinator tube.
  • the core network can be connected to the access network, and the UE communicates with the core network through the access network.
  • the coordinator 131, the NF 132, the coordinator manager 133, and the NF manager 134 may be deployed on one or more virtual machines.
  • the core network may be deployed in one or more Composed of multiple components on a virtual machine.
  • the coordinator 131 is an external interface of the core network element, and is responsible for receiving and returning the UE interaction signaling, for example, receiving the service request of the UE, and returning the execution result of the service request to the UE.
  • the coordinator 131 can call the NF 132.
  • the NF includes virtualized network element functions in the core network.
  • the function of the network node level can be divided into several functional blocks by using virtualization technology, and each functional block can be implemented as a corresponding NF in a software manner, so that the core network will no longer be used.
  • the functions of the MME may be divided into two functional modules: Mobility Management (MM) and Session Management (SM), which are respectively implemented in software as corresponding MM modules and SM modules.
  • the NF may include a function module such as an MM, an SM, and a Policy and Charging Control (PCC).
  • PCC Policy and Charging Control
  • the NF may be described as an example of the foregoing functional module, and the NF may also be a module for implementing other network element functions of the core network (for example, S-GW or PDN GW, etc.), and The embodiment of the invention does not limit the implementation granularity of the NF.
  • the coordinator manager 133 can perform management functions of various coordinators, such as instantiation, update, or termination of the coordinator.
  • the coordinator manager 133 can deploy the business process definition to the coordinator 131, which in accordance with the business process definition invokes at least one network function NF that is required to process the service.
  • the business process definition can be regarded as a business process as a whole, and one business process can have different business process branches, and different business process branches can process different requests of the UE.
  • a business process may be defined as a business process.
  • the business process may be in the form of a script, which is not limited by the embodiment of the present invention.
  • the NFs that need to be invoked in the business process may be NF 1 , NF 2 , NF 3 , NF 4 , and NF 5 in FIG. 2, and the direction of the dotted line in FIG. 2 indicates the order in which the respective NFs are called.
  • the coordinator 131 first calls NF 1 according to the business process, then calls NF 2 and NF 3 at the same time, then calls NF 4 , and finally calls NF 5 .
  • the NF manager 134 can perform various NF management functions, such as instantiation, update, or termination of the NF.
  • the NF manager can create NFs according to the instructions of the coordinator manager 133, and the core The NF in the network is managed.
  • FIG. 3 is a schematic flowchart of a method for deploying a service flow according to an embodiment of the present invention. It should be understood that FIG. 3 illustrates steps or operations of a method of deploying a business process, but these steps or operations are merely examples, and embodiments of the present invention may perform other operations or variations of the various operations in FIG. Moreover, the various steps in FIG. 3 may be performed in a different order than that presented in FIG. 3, and it is possible that not all operations in FIG. 3 are to be performed.
  • the same reference numerals in FIG. 3 as those in FIG. 2 denote the same or similar meanings, and are not described herein again for the sake of brevity.
  • the coordinator manager 133 creates a coordinator instance.
  • the coordinator instance is the coordinator described above.
  • the coordinator instance is used to process service requests from multiple UEs.
  • the coordinator instance load in the core network is relatively large, for example, when the number of UEs served by one coordinator exceeds the load, a new coordinator instance needs to be created to implement load balancing of the coordinator instance in the core network.
  • the coordinator manager 133 when creating the coordinator instance, needs to determine the flow of processing the UE's traffic, such as determining the network element function needed to process the UE's traffic.
  • the coordinator manager when at least two network element functions need to be used, it is also necessary to determine the order of at least two network element functions used. That is to say, when the coordinator manager creates the coordinator instance, it needs to determine the NF that needs to be called when the service is processed, and the order of the NFs that need to be called.
  • the coordinator manager 133 sends an instantiation NF request to the NF manager 134.
  • the coordinator manager 133 can determine the NF that needs to be invoked to process the service according to the foregoing process.
  • the NF can be referred to as an NF instance.
  • one or more NF instances that need to be called in the coordinator instance may exist in the NF instance that has been established in the NF 132.
  • the coordinator manager 133 can determine the NF instance that can be called in the NF 132 according to the associated isolation policy, at which point it is not necessary to re-establish the NF instance.
  • a NF instance instance coordinator 202 is included in NF n. If the coordinator manager 133 determines that the NF n already present in the NF 132 can be shared, then the NF n may not be created. If the coordinator manager 133 determines that there are NF n, can not be shared or existing NF n, you need to create the NF n.
  • an instantiation NF request is sent to the NF manager 134 to cause the NF to create the NF instance that needs to be created based on the instantiated NF request.
  • the NF request may carry the type of the NF instance, for example, the NF created by the request carried in the NF request is MM.
  • the NF manager 134 sends an instantiation NF response to the coordinator manager 133.
  • the NF manager 134 creates an NF instance that needs to be created in the instantiated NF request according to a related isolation policy, such as other NF shared physical machines or physical isolation.
  • a related isolation policy such as other NF shared physical machines or physical isolation.
  • the NF manager sends an instantiated NF response to the coordinator manager 133, instantiating information of the created NF instance in the NF response.
  • the information may include the NF instance address and the NF interface parameter, and may also include information such as the NF instance identifier, which is not limited by the embodiment of the present invention.
  • the coordinator manager 133 deploys the business process.
  • the business process is used to invoke at least one NF instance that needs to be used to process the above services.
  • the template or the business process model may be used to implement the business process, which is not limited by the present invention.
  • the coordinator 131 stores the business process and returns a response message to the coordinator manager 133.
  • the coordinator manager 133 when the coordinator manager 133 updates the service process, it is necessary to determine whether the NF instance needs to be updated. When the coordinator manager 133 determines that an NF instance needs to be updated, the updated NF instance needs to be created. At this time, it is necessary to perform the corresponding steps in the above 204 to 210 to implement the update of the business process. Specifically, when the coordinator 131 implements the update of the business process according to the relevant policy, the existing process can continue to be executed according to the original definition, and the newly created process can be executed according to the new definition, or the existing processes of all UEs are suspended, and unified. Execute according to the new business process, or select part of the UE according to the status of the UE, and switch its business process to the new business process.
  • FIG. 4 is a schematic flowchart of a method for service processing in a core network according to an embodiment of the present invention. The method is performed by the core network described above. The method in Figure 4 includes:
  • the first coordinator receives a request message sent by the first network element, where the request message is used to request processing of the service of the UE.
  • the first coordinator is a coordinator serving the UE, and the first coordinator includes a service flow.
  • the first network element can be a UE or a RAN node (e.g., a base station).
  • the request message is a request message of the service of the UE, for example, a Tracking Area Update (TAU) request, a service request, or a handover request.
  • the service may include an attach service of the UE, a Tracking Area Update (TAU) service of the UE, a service service of the UE, or a handover service of the UE.
  • the request message may be another request message of the UE, which is not limited in this embodiment of the present invention. A detailed description will be given below with specific examples, which will not be described in detail herein.
  • the first coordinator processes the service according to the service flow corresponding to the request message and the request message.
  • the business process is used to invoke the processing required to process the service At least one network function NF.
  • the business process corresponding to the service may be a branch in the business process.
  • the first coordinator determines a service flow corresponding to the request message according to the request message in 310, and processes the requested service according to the service flow.
  • the NF and the business process can be referred to the descriptions in FIG. 2 and FIG. 3 above, and in order to avoid repetition, details are not described herein again.
  • the calling of the at least two NFs may be implemented based on a concurrent or sequential architecture.
  • the business process is for calling the at least two NFs in a logical order.
  • an input message of each NF of the at least one NF may be generated according to the request message and the service flow, and an input message of each NF is used to invoke the NF.
  • the NF may generate an output message based on the input message and return the output message to the first coordinator.
  • the NF input message is only used to notify the NF in one direction, and the NF may not need to generate an output message.
  • an input message of the NF that is called later may be constructed based on the output message returned by the previously invoked NF.
  • the first coordinator may determine a processing result of the service according to the output message of the NF.
  • the first coordinator may send a return message to the first network element according to the processing result of the service.
  • the first coordinator 131 first generates an input message of NF 1 according to the request message and the business flow shown in FIG. 2, and then calls NF 1 .
  • After 2 and NF NF 3 to be output message is returned, in accordance with the output message NF NF 2 and 3, the configuration of the input message 4 NF, NF 4 call, obtain an output message 4 NF.
  • the message is then output NF 4, the configuration of the input message. 5 NF, NF call. 5, NF. 5 finally obtain the output message.
  • a return message can be sent to the first network element according to the output message of NF 5 .
  • the data information of the UE may be acquired from the second network element, and the UE is created according to the data information. Context.
  • the service may be processed according to the context, the request message, and the business process.
  • the second network element may include user subscription information storage.
  • the unit, the RAN node or the second coordinator, the user subscription information storage unit may be, for example, an HSS.
  • the second coordinator is another coordinator in the core network that is different from the first coordinator.
  • the first coordinator and the second coordinator are respectively located in two data centers, and the UE performs handover across the data center, the first coordinator and the second coordinator may interact to implement transmission of status and context data of the UE.
  • the NF can be implemented as a stateless service, that is, the state of the UE, the context information of the UE, or the interaction information between the UE and each network element may not be saved in the NF. Since the NF in the embodiment of the present invention is a stateless service, the call of the NF is more flexible, thereby improving the reusability of the NF, thereby making the deployment of the network more flexible.
  • the first coordinator may send a request to the other network element (for example, the second network element) to obtain data information of the UE, where the data information may be the UE. At least one of a temporary identifier, an S1 Application Protocol (S1AP) identifier, a mobility management state, or partial subscription data of the UE.
  • the first coordinator can establish a context of the UE according to the data information.
  • the coordinator can implement a call to the NF according to the context of the UE.
  • the coordinator can interact with different network elements to obtain data information according to request messages of different services. And after obtaining the return message of the above NF, the coordinator can update the context of the UE.
  • the context may also be stored in the NF.
  • the context of the UE may not be stored in the coordinator, and the coordinator may not include the context-related data of the UE in the input message constructed when the NF is invoked. This embodiment of the present invention does not limit this.
  • the embodiment of the present invention can process the service of the UE according to the network function in the core network according to the service flow corresponding to the request message, and the network function includes the function of the virtualized network element in the core network.
  • the embodiment of the present invention converts the service deployment into a software deployment, and can select and invoke different network functions for different service scenarios to implement an on-demand elastic networking, so that the network has flexible scalability, openness, and evolution capability.
  • FIG. 5 is a schematic flowchart of a method for processing a service in a core network according to an embodiment of the present invention.
  • the MM 150, SM 160, and PCC 170 in Figure 5 are the network functions that need to be invoked in this embodiment.
  • FIG. 5 illustrates steps or operations of the method of service processing in the core network, but these steps or operations are merely examples, and other operations may be performed in the embodiment of the present invention or in FIG. 5 Deformation of each operation.
  • the various steps in FIG. 5 may be performed in a different order than that presented in FIG. 5, and it is possible that not all operations in FIG. 5 are to be performed.
  • the UE 110 sends an attach request to the coordinator 131.
  • the attach request is one of the request messages in FIG. After the coordinator receives the attach request sent by the UE, the attach request of the UE may be processed according to a pre-stored service flow corresponding to the attach request.
  • the coordinator 131 sends a user authentication authorization request to the HSS 140.
  • the HSS 140 sends a user authentication authorization response to the coordinator 131.
  • the coordinator needs to interact with the HSS to perform authentication and authorization to obtain data information of the UE.
  • the data information refer to the description of FIG. 4 above.
  • the coordinator 131 sends an update location request to the HSS 140.
  • the HSS 140 sends an update location response to the coordinator 131.
  • the coordinator interacts with the HSS to obtain related subscription data of the UE.
  • the coordinator can create a context of the UE based on the acquired data information and associated subscription data.
  • the coordinator 131 sends a mobility management request to the MM 150.
  • the MM 150 is a functional module in the coordinator, and the mobility management request is an input message of the MM module constructed by the coordinator according to the service flow and the context of the UE.
  • the MM 150 performs mobility management calculation according to the mobility management request.
  • the MM 150 returns a mobility management response to the coordinator 131 according to the result of the mobility management calculation.
  • the coordinator 131 calls the MM 150. Specifically, after acquiring the subscription information of the UE and creating the context of the UE, the coordinator sends the UE related information to the MM module, and the MM module performs corresponding calculation, including operations such as a Tracking Area List (TA list). The calculation result is returned to the coordinator, which updates the context of the UE.
  • TA list Tracking Area List
  • the coordinator 131 sends a session management request to the SM 160.
  • the SM 160 is a network function in the coordinator that is an input message of the SM module constructed by the coordinator according to the business process and the context of the UE.
  • the SM 160 performs session management calculation according to the session management request.
  • the SM 160 returns a session management response to the coordinator 131 according to the result of the session management calculation. should.
  • the coordinator 131 calls the SM 160. Specifically, the coordinator sends the UE related information to the SM module, and the SM management module performs corresponding calculations, including operations such as assigning an Internet Protocol (IP) address, selecting a service gateway, and the like, and returning the calculation result to the coordinator, the coordinator Update the UE context.
  • IP Internet Protocol
  • the coordinator 131 sends an IP-Connectivity Access Network (IP-CAN) session establishment indication to the PCC 170.
  • IP-CAN IP-Connectivity Access Network
  • the PCC 170 returns an IP-CAN session establishment response to the coordinator 131.
  • the coordinator 131 calls the PCC 170. Specifically, the coordinator sends the UE related information to the PCC module, and the PCC module calculates a related charging and quality of service (QoS) control policy of the UE, and returns related content to the coordinator, and the coordinator updates the UE context.
  • QoS quality of service
  • the coordinator 131 sends a create session request to the SM 160.
  • the SM 160 interacts with the serving gateway according to the create session request, and configures to establish a data path.
  • the SM 160 returns a create session response to the coordinator 131.
  • the coordinator 131 calls the SM 160 again. Specifically, the coordinator interacts with the SM management module to complete the process of creating a session.
  • the coordinator 131 returns an attach reception message to the UE 110.
  • the coordinator constructs a response message to the attach request based on the return message of the MM module, the SM module, and the PCC module, and sends a response message to the UE.
  • the UE 110 sends an attach complete message to the coordinator 131.
  • the coordinator 131 sends a modify bearer request to the PCC 170.
  • the PCC 170 interacts with the serving gateway according to the modified bearer request, and configures the modified data path.
  • the PCC 170 returns a modified bearer response to the coordinator 131.
  • the coordinator 131 calls the PCC 170 again. Specifically, the coordinator interacts with the PCC management module to complete the modification of the bearer process.
  • the coordinator 131 sends a notification request to the HSS 140.
  • the HSS 140 returns a notification response to the coordinator 131.
  • the coordinator interacts with the HSS to update the relevant data of the UE, and completes the attachment. The process.
  • the core network implements the attach procedure of the UE according to the service request corresponding to the attach request according to the attach request of the UE, and the coordinator acts as an external interaction interface, and implements external signaling reception and transmission and NF (for example, The MM, SM, and PCC) are invoked, and the state and context data of the UE are updated, thereby completing the attachment process of the UE.
  • NF for example, The MM, SM, and PCC
  • FIG. 6 is a schematic flowchart of a method for service processing in a core network according to another embodiment of the present invention.
  • the MM 150, SM 160, and PCC 170 in FIG. 6 are respectively network functions that the first coordinator 1311 needs to invoke.
  • the first coordinator 1311 and the second coordinator 1312 in FIG. 6 may each be the coordinator in FIG. 2 described above.
  • FIG. 6 illustrates steps or operations of the method of service processing in the core network, but these steps or operations are merely examples, and embodiments of the present invention may perform other operations or variations of the operations in FIG. Moreover, the various steps in FIG. 6 may be performed in a different order than that presented in FIG. 6, and it is possible that not all operations in FIG. 6 are to be performed.
  • the UE 110 sends a TAU request to the first coordinator 1311.
  • the TAU request is one of the service request messages in FIG.
  • the first coordinator may process the TAU request of the UE according to a pre-stored service flow corresponding to the TAU request.
  • the first coordinator 1311 sends a UE context request to the second coordinator 1312.
  • the second coordinator 1312 sends a UE context response to the first coordinator 1312.
  • the first coordinator 1311 sends a UE context response to the second coordinator 1312.
  • the first coordinator first selects the second coordinator according to the related information, for example, according to the ID of the second coordinator in the TAU request, and interacts with the second coordinator to acquire the subscription and context data of the UE, and saves the subscription information of the UE. And context data.
  • the two coordinators when two coordinators are respectively located in two data centers, and the UE performs handover across the data center, the two coordinators can interact to implement the state of the UE and the transmission of the context data.
  • the first coordinator 1312 sends a mobility management request to the MM 150.
  • the MM150 performs mobility management calculation according to the mobility management request.
  • the MM 150 sends a mobility management response to the first coordinator 1311.
  • the first coordinator 1311 calls the MM 150. Specifically, the first coordinator sends the UE related information to the MM module, and the MM management module performs corresponding calculation, including, for example, Re-allocating operations such as TA List, returning the calculation result to the first coordinator, and the first coordinator updates the UE context.
  • the MM management module performs corresponding calculation, including, for example, Re-allocating operations such as TA List, returning the calculation result to the first coordinator, and the first coordinator updates the UE context.
  • the first coordinator 1311 sends a session management request to the SM160.
  • the SM 160 performs session management calculation according to the session management request.
  • the SM 160 sends a serving gateway response to the first coordinator 1311.
  • the first coordinator 1311 calls the SM 160.
  • the first coordinator sends the UE related information to the SM module, and the SM management module performs corresponding calculations, including operations such as whether to reselect the serving gateway (GW-U), and returns the calculation result to the first coordinator, and the first coordinator updates.
  • GW-U serving gateway
  • the first coordinator 1311 sends an IP-CAN session modification indication to the PCC 170.
  • the PCC 170 sends an IP-CAN session modification response to the first coordinator 1311.
  • the first coordinator 1311 calls the PCC 170. Specifically, the first coordinator sends the UE related information to the PCC module, and the PCC module recalculates the related charging and quality of service (QoS) control policy of the UE, and returns related content to the first coordinator, A coordinator updates the UE context.
  • QoS quality of service
  • the first coordinator 1311 sends a modify bearer request to the SM 160.
  • the SM 160 interacts with the service gateway and configures a modified data path.
  • the SM 160 sends a modify bearer response to the first coordinator 1311.
  • the first coordinator 1311 calls the SM 160 again.
  • the first coordinator interacts with the SM management module to complete the modification of the bearer process.
  • the first coordinator 1311 sends an update location request to the HSS 140.
  • the HSS 140 sends an update location response to the first coordinator.
  • the first coordinator interacts with the HSS to update the relevant data of the UE.
  • the first coordinator 1311 sends a TAU Receive message to the UE 110.
  • the first coordinator constructs a response message to the TAU request based on the return message of the MM module, the SM module, and the PCC module, and sends a response message to the UE, for example, a TAU receiving message.
  • the UE 110 sends a TAU Complete message to the first coordinator.
  • the core network implements the TAU process of the UE according to the TAU request of the UE and according to the service flow corresponding to the TAU request.
  • the first coordinator acts as an interface for external interaction, implements interaction with the second coordinator, and completes transmission of the state and context of the UE, and implements an external letter.
  • the reception and transmission of the command and the invocation of the NF (eg, MM, SM, and PCC), and the status and context data of the UE are updated, thereby completing the TAU procedure of the UE.
  • the NF eg, MM, SM, and PCC
  • FIG. 7 is a schematic flowchart of a method for service processing in a core network according to another embodiment of the present invention.
  • the SM 160 and the PCC 170 in FIG. 7 are respectively network functions that the coordinator 131 needs to invoke.
  • FIG. 7 illustrates steps or operations of the method of service processing in the core network, but these steps or operations are merely examples, and embodiments of the present invention may perform other operations or variations of the operations in FIG. Moreover, the various steps in FIG. 7 may be performed in a different order than that presented in FIG. 7, and it is possible that not all operations in FIG. 7 are to be performed.
  • the UE 110 sends a service request to the coordinator 131.
  • the service request is one of the service request messages in FIG. After the coordinator receives the service request sent by the UE, the service request of the UE may be processed according to a pre-stored service flow corresponding to the service request.
  • the coordinator 131 sends an initial context setup request to the RAN 120.
  • the RAN 120 sends an initial context setup complete response to the coordinator 131.
  • the coordinator interacts with the RAN side node to establish a UE initial context.
  • the coordinator 131 sends an IP-CAN session modification indication to the PCC 170.
  • the PCC 170 sends an IP-CAN session modification response to the coordinator 131.
  • the coordinator 131 calls the PCC 170. Specifically, the coordinator sends the UE related information to the PCC module, and the PCC module recalculates the related charging and QoS control policies of the UE, and returns related content to the coordinator, and the coordinator updates the UE context.
  • the coordinator 131 sends a modify bearer request to the SM 160.
  • the SM 160 interacts with the service gateway to configure a modified data path.
  • the SM 160 sends a modify bearer response to the coordinator 131.
  • the coordinator 131 calls the SM 160.
  • the coordinator interacts with the SM management module to complete the modification of the bearer process.
  • the core network implements the service request process of the UE according to the service request of the UE and according to the service flow corresponding to the service request.
  • the coordinator implements the establishment of the initial context of the RAN side, the reception and transmission of external signaling, and the invocation of NF (for example, SM and PCC), and updates the status and context data of the UE, thereby completing the UE's service request process.
  • NF for example, SM and PCC
  • FIG. 8 is a schematic flowchart of a method for service processing in a core network according to another embodiment of the present invention.
  • the source RAN 1201 and the destination RAN in FIG. 8 may be the access network node in FIG. 1 above, and the source coordinator 1313 and the destination coordinator 1314 may be the coordinator in FIG. 2 above, and the source SM 1601 is the NF invoked by the source coordinator 1313.
  • the destination SM1602 is the NF called by the destination coordinator 1314.
  • FIG. 8 illustrates steps or operations of the method of service processing in the core network, but these steps or operations are merely examples, and embodiments of the present invention may perform other operations or variations of the operations in FIG. Moreover, the various steps in FIG. 8 may be performed in a different order than that presented in FIG. 8, and it is possible that not all operations in FIG. 8 are to be performed.
  • the source RAN 1201 sends a handover request to the source coordinator 1313.
  • the handover request is one of the service request messages in FIG.
  • the first coordinator may process the handover request of the UE according to the pre-stored service flow corresponding to the handover request.
  • the source coordinator 1313 sends a destination coordinator selection request to the source SM 1601.
  • the source SM 1601 calculates and selects a destination coordinator.
  • the source SM 1601 sends a destination coordinator selection response to the source coordinator 1313.
  • source coordinator 1313 invokes source SM 1601. Specifically, the source coordinator requests the source SM module to calculate and select a destination coordinator, for example, selecting a destination coordinator according to the location information of the UE.
  • the source coordinator 1313 sends a relocation request to the destination coordinator 1314.
  • the destination coordinator 1314 sends a session management request to the destination SM 1602.
  • the destination SM 1602 performs session management calculation.
  • the destination SM 1602 sends a session management response to the destination coordinator 1314.
  • the destination coordinator 1314 invokes the target SM 1602. Specifically, the destination coordinator sends the UE related information to the destination SM module, and the destination SM management module performs corresponding calculations, including operations such as reselecting the serving gateway, and returns the calculation result to the destination coordinator, and the destination coordinator updates the UE context.
  • the destination coordinator 1314 sends a create session request to the destination SM 1602.
  • the destination SM1602 interacts with the service gateway to configure a data path.
  • the destination SM 1602 sends a create session response to the destination coordinator 1314.
  • the destination coordinator 1314 invokes the destination SM 1602. Specifically, the destination coordinator interacts with the destination SM management module according to the calculation result to complete the session creation process.
  • the destination coordinator 1314 sends a handover request to the destination RAN 1202.
  • the destination RAN 1202 sends a handover response to the destination coordinator 1314.
  • the destination coordinator 1314 sends an indirect forwarding tunnel establishment request to the destination SM1602.
  • the destination SM 1602 sends an indirect forwarding tunnel response to the destination coordinator 1314.
  • the destination coordinator 1314 invokes the destination SM 1602 again.
  • the destination coordinator interacts with the destination SM management module to complete the establishment process of the destination side indirect forwarding tunnel.
  • the destination coordinator 1314 sends a relocation response to the source coordinator 1313.
  • the source coordinator 1313 sends an indirect forwarding tunnel establishment request to the source SM1601.
  • the source SM1601 sends an indirect forwarding tunnel response to the source coordinator 1313.
  • the source coordinator 1313 calls the source SM 1601 again.
  • the source coordinator interacts with the source SM management module to complete the source side indirect forwarding tunnel establishment process.
  • the source coordinator 1313 sends a handover command to the UE.
  • the source RAN node or the source coordinator interacts with the destination RAN or the destination coordinator to complete transmission of the access context/coordinator state, and the UE switches to the destination RAN.
  • the two coordinators when two coordinators are respectively located in two data centers, and the UE performs handover across the data center, the two coordinators can interact to implement the state of the UE and the transmission of the context data.
  • the UE 110 sends a handover confirmation to the destination RAN 1202.
  • the destination RAN 1202 sends a handover notification to the destination coordinator 1314.
  • the destination coordinator 1314 sends a relocation complete notification to the source coordinator 1313.
  • the source coordinator 1313 sends a relocation complete response to the destination coordinator 1314.
  • the destination coordinator 1314 sends a modify bearer request to the destination SM 1602.
  • the destination SM1602 interacts with the service gateway to configure a modified data path.
  • the destination SM 1602 sends a modify bearer response to the destination coordinator 1314.
  • the destination coordinator 1314 invokes the destination SM 1602 again.
  • the destination coordinator interacts with the SM management module to complete the modification of the bearer process.
  • TAU and other handover operations for example, deleting the source session, removing the indirect forwarding tunnel light, and completing the handover process.
  • the core network implements the handover process of the UE according to the handover request of the UE according to the service flow corresponding to the handover request.
  • the source coordinator and the destination coordinator act as interfaces for external interaction, implement interaction between the source coordinator and the destination coordinator, transmit UE status and context data, implement external signaling reception and transmission, and NF (eg, MM, SM and PCC) And the status and context data of the UE are updated, thereby completing the handover process of the UE.
  • NF eg, MM, SM and PCC
  • FIG. 9 is a schematic block diagram of a network device according to an embodiment of the present invention.
  • the network device 400 shown in FIG. 9 is applied to a core network, and the network device 400 may be the above-described coordinator or a device having various functional modules of the above-described coordinator.
  • the network function NF is also included in the core network, and the network device 400 includes:
  • the receiving unit 410 is configured to receive a request message sent by the first network element, where the request message is used to request processing of the service of the UE;
  • the processing unit 420 is configured to process the service according to the request message and the service flow corresponding to the request message, where the service process is used to invoke at least one NF required to process the service.
  • the embodiment of the present invention can process the service of the UE according to the network function in the core network according to the service flow corresponding to the request message, and the network function includes the function of the virtualized network element in the core network.
  • the embodiment of the present invention converts the service deployment into a software deployment, and can select and invoke different network functions for different service scenarios to implement an on-demand elastic networking, so that the network has flexible scalability, openness, and evolution capability.
  • the at least one NF includes at least two NFs, and the business process is used to invoke the at least two NFs in a logical order.
  • processing unit 420 is specifically configured to:
  • the service is processed according to the input message of each NF.
  • processing unit 420 is specifically configured to:
  • the output message of each NF is generated by each NF according to an input message of each NF;
  • the processing result for the service is determined according to the output message of each NF.
  • processing unit 420 is further configured to:
  • the network device 400 further includes:
  • An acquiring unit configured to acquire, according to the request message, data information of the UE sent by a second network element, where the data information includes information required to create a context of the UE;
  • a establishing unit configured to create a context of the UE according to the data information of the UE
  • the processing unit 420 is specifically configured to:
  • the first coordinator generates an input message for each NF of the at least one NF according to the context of the UE and the service flow.
  • the second network element includes a user subscription information storage unit, a radio access network RAN node, or a first network device, where the first network device is disposed in the core network.
  • the first network device may be a network device having the same functional module as the network device 400.
  • the core network further includes a coordinator manager, where the receiving unit is further configured to receive the service process sent by the coordinator manager.
  • the network device further includes a sending unit, configured to send a return message to the first network element according to the processing result of the service.
  • the receiving unit 410 may be implemented by a transceiver
  • the processing unit 420 may be implemented by a processor.
  • network device 500 can include a processor 510, a memory 520, a transceiver 530, and a bus system 540.
  • the memory 520 can be used to store code and the like executed by the processor 510.
  • bus system 540 which in addition to the data bus includes a power bus, a control bus, and a status signal bus.
  • bus system 540 various buses are labeled as bus system 540 in the figure.
  • each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 410 or an instruction in a form of software.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 520, and the processor 510 reads the information in the memory 520 and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the network device 400 shown in FIG. 9 or the network device 500 shown in FIG. 10 can implement the processes corresponding to the foregoing method embodiments shown in FIG. 3 to FIG. 8. Specifically, the network device 400 or the network device 500 can refer to the foregoing. The descriptions in FIGS. 3 to 8 are not repeated here to avoid repetition.
  • FIG. 11 is a schematic block diagram of a network device according to an embodiment of the present invention.
  • the network device 600 shown in FIG. 10 is applied to a core network, and the network device 600 may be the above-described coordinator manager or a device having various functional modules of the coordinator manager described above.
  • the core network also includes the network function NF
  • the network device 600 includes:
  • a determining unit 610 configured to determine a process for processing the service, where the process is used to indicate at least one network function NF required to process the service;
  • the determining unit 610 is further configured to determine information about the at least one NF according to the process;
  • the generating unit 620 is configured to generate, according to the process and the information of the at least one NF, a service process for processing the service, where the service process is used to invoke at least one NF required to process the service;
  • the sending unit 630 is configured to send the service flow to the coordinator, so that the coordinator processes the service according to the service process.
  • the embodiment of the present invention can call the network function in the core network according to the service process, process the service of the UE, convert the service deployment into a software deployment, and select and invoke different network functions for different service scenarios to implement the on-demand elastic group.
  • the network enables the network to be flexible, scalable, and evolving.
  • the at least one NF includes at least two NFs, and the process is further used to indicate a logical sequence of the at least two NFs that are required to be used, where the service flow is used to invoke the according to the logical sequence. At least two NFs.
  • the core network further includes an NF manager, and the determining unit 610 is specifically configured to:
  • the information about the NF includes an interface parameter of the NF and an address of the NF.
  • network device 700 can include a processor 710, a memory 720, a transceiver 730, and a bus system 740.
  • the memory 720 can be used to store code and the like executed by the processor 710.
  • bus system 740 which in addition to the data bus includes a power bus, a control bus, and a status signal bus.
  • bus system 740 various buses are labeled as bus system 740 in the figure.
  • each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 710 or an instruction in a form of software.
  • the steps of the method disclosed in connection with the embodiments of the present invention can be directly implemented as a hardware processor or completed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in memory 720, and processor 710 reads the information in memory 720 and, in conjunction with its hardware, performs the steps of the above method. To avoid repetition, it will not be described in detail here.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods 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 functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used 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. .

Abstract

Provided in an embodiment of the present invention are a business processing method and network equipment in a core network. The core network comprises a first coordinator and at least one network function (NF). The method comprises: receiving, by the first coordinator, a request message sent by a first network element, the request message being used for requesting to process the business of a UE; and processing the business by the first coordinator according to the request message and a business procedure corresponding to the request message, the business procedure being used for invoking the at least one NF that is needed to be used for processing the business. According to the embodiment of the present invention, business deployment is transformed into software deployment; therefore different NFs can be selected and invoked for different business scenarios and an on-demand elastic networking is achieved so that the network has flexible expandability, openness and evolution capability.

Description

核心网中业务处理的方法和网络设备Method and network device for business processing in core network 技术领域Technical field
本发明涉及通信领域，更具体的，涉及通信领域中的核心网中业务处理的方法和网络设备。The present invention relates to the field of communications, and more particularly to a method and network device for service processing in a core network in the field of communications.
背景技术Background technique
***架构演进(System Architecture Evolution，SAE)是第三代合作伙伴项目(the 3rd Generation Partnership Project，3GPP)对于长期演进***(Long Term Evolution，LTE)无线通信标准的核心网络架构的升级计划。SAE体系结构的主要组成部分是演进的分组核心网(Evolved Packet Core，EPC)，EPC包含了移动性管理组件(Mobility Management Entity，MME)，归属用户服务器(Home Subscriber Server，HSS)，服务网关(Serving Gateway，S-GW)和分组数据网网关(Packet Data Network Gateway，PDN GW)等。System Architecture Evolution (SAE) is the 3rd Generation Partnership Project (3GPP) upgrade plan for the core network architecture of the Long Term Evolution (LTE) wireless communication standard. The main component of the SAE architecture is the Evolved Packet Core (EPC). The EPC includes Mobility Management Entity (MME), Home Subscriber Server (HSS), and Service Gateway ( Serving Gateway, S-GW) and Packet Data Network Gateway (PDN GW).
核心网中每个网元都通过标准接口相互连接，以满足不同设备商产品之间的互通。但是，现有技术中是通过点对点的网元交互模型实现不同子***之间的相互通信和远程调用，每次部署一个新的功能网元时，需要定义该网元与所有已有网元的交互接口，而且接口开发和测试都要涉及所有网元，灵活性比较差。并且，点对点定义交互接口的方式，使交互网元之间紧密耦合，降低了网元的可重用性。Each network element in the core network is connected to each other through standard interfaces to meet the interworking between different device vendors. However, in the prior art, the peer-to-peer network element interaction model is used to implement mutual communication and remote calling between different subsystems. Each time a new functional network element is deployed, the network element and all existing network elements need to be defined. Interactive interface, and interface development and testing involve all network elements, and the flexibility is relatively poor. Moreover, the manner in which the interactive interface is defined point-to-point enables tight coupling between the interacting network elements and reduces the reusability of the network element.
发明内容Summary of the invention
本发明实施例提供了核心网中业务处理的方法和网络设备，能够针对不同的业务场景选择和调用不同的网络功能，实现按需弹性组网。The embodiments of the present invention provide a method and a network device for processing a service in a core network, and can select and invoke different network functions for different service scenarios to implement an on-demand elastic networking.
第一方面，本发明实施例提供了一种核心网中业务处理的方法，所述核心网包括第一协调器和至少一个网络功能NF，所述方法包括：所述第一协调器接收第一网元发送的请求消息，所述请求消息用于请求对UE的业务进行处理；所述第一协调器根据所述请求消息和所述请求消息对应的业务流程，对所述业务进行处理，所述业务流程用于调用处理所述业务所需要使用的所述至少一个NF。In a first aspect, an embodiment of the present invention provides a method for service processing in a core network, where the core network includes a first coordinator and at least one network function NF, and the method includes: the first coordinator receives the first a request message sent by the network element, where the request message is used to request processing of the service of the UE; the first coordinator processes the service according to the service flow corresponding to the request message and the request message, The business process is used to invoke the at least one NF that is required to process the service.
本发明实施例能够根据请求消息对应的业务流程调用核心网中的网络 功能，对UE的业务进行处理，该网络功能包括核心网中虚拟化的网元功能。本发明实施例将业务部署转化为软件部署，能够针对不同的业务场景选择和调用不同的网络功能，实现按需弹性组网，使得网络具有灵活的可扩展性、开放性和演进能力。The embodiment of the invention can call the network in the core network according to the service flow corresponding to the request message. The function is to process the service of the UE, and the network function includes the function of the virtualized network element in the core network. The embodiment of the present invention converts the service deployment into a software deployment, and can select and invoke different network functions for different service scenarios to implement an on-demand elastic networking, so that the network has flexible scalability, openness, and evolution capability.
可选的，所述至少一个NF包括至少两个NF，所述业务流程用于按照逻辑顺序调用所述至少两个NF。Optionally, the at least one NF includes at least two NFs, and the business process is used to invoke the at least two NFs in a logical order.
例如，协调器可以根据该业务流程，首先调用NF1，之后同时调用NF2和NF3，然后调用NF4，最后调用NF5。当需要调用的NF的数量为至少两个时，可以根据在先调用的NF返回的输出消息，构造在后调用的NF的输入消息。For example, the coordinator can first call NF 1 according to the business process, then call NF 2 and NF 3 at the same time, then call NF 4 , and finally call NF 5 . When the number of NFs to be called is at least two, an input message of the NF that is called later may be constructed according to the output message returned by the previously invoked NF.
可选的，所述第一协调器根据所述请求消息和所述业务对应的业务流程，对所述业务进行处理，包括：所述第一协调器根据所述请求消息和所述业务流程，生成所述至少一个NF中的每个NF的输入消息；所述第一协调器根据所述每个NF的输入消息，对所述业务进行处理。Optionally, the first coordinator processes the service according to the request message and the service flow corresponding to the service, including: the first coordinator according to the request message and the service process, Generating an input message for each of the at least one NF; the first coordinator processes the service according to the input message of each of the NFs.
可选的，所述第一协调器根据所述每个NF的输入消息，对所述业务进行处理，包括：所述第一协调器获取所述每个NF的输出消息，所述每个NF的输出消息是所述每个NF根据所述每个NF的输入消息生成的；所述第一协调器根据所述每个NF的输出消息，确定对所述业务的处理结果。Optionally, the first coordinator processes the service according to the input message of each NF, including: the first coordinator acquires an output message of each NF, where each NF The output message is that each NF is generated according to the input message of each NF; the first coordinator determines a processing result for the service according to the output message of each NF.
应理解，当第一协调器根据输入消息调用NF时，NF可以根据输入消息生成输出消息，并将该输出消息返回给第一协调器。而在特定情况下，NF的输入消息仅用于单向通知该NF，此时该NF可以不需要生成输出消息。It should be understood that when the first coordinator invokes the NF based on the input message, the NF may generate an output message based on the input message and return the output message to the first coordinator. In a specific case, the NF input message is only used to notify the NF in one direction, and the NF may not need to generate an output message.
可选的，所述第一协调器获取所述每个NF的输出消息之后，所述第一协调器根据所述每个NF的输出消息，更新所述UE的上下文。当需要调用的NF的数量为至少两个时，可以根据在先调用的NF返回的输出消息，更新UE的上下文，然后根据UE的上下文构造在后调用的NF的输入消息。Optionally, after the first coordinator obtains the output message of each NF, the first coordinator updates the context of the UE according to the output message of each NF. When the number of NFs to be called is at least two, the context of the UE may be updated according to the output message returned by the previously invoked NF, and then the input message of the NF that is called later is constructed according to the context of the UE.
可选的，当第一协调器中没有存储UE的上下文时，所述第一协调器还可以在根据所述请求消息和所述业务流程，生成所述至少一个NF中的每个NF的输入消息之前，根据所述请求消息，获取第二网元发送的所述UE的数据信息，所述数据信息包括创建所述UE的上下文所需的信息；所述第一协调器根据所述UE的数据信息，创建所述UE的上下文；该数据信息可以为UE的临时标识、S1AP标识、移动性管理状态或者UE的部分签约数据中 的至少一种。Optionally, when the context of the UE is not stored in the first coordinator, the first coordinator may further generate an input of each NF in the at least one NF according to the request message and the service flow. Obtaining, according to the request message, data information of the UE sent by the second network element, where the data information includes information required to create a context of the UE, where the first coordinator is configured according to the UE Data information, creating a context of the UE; the data information may be a temporary identifier of the UE, an S1AP identifier, a mobility management state, or part of the subscription data of the UE. At least one of them.
其中，所述第一协调器根据所述请求消息和所述业务流程，生成所述至少一个NF中的每个NF的输入消息，包括：所述第一协调器根据所述UE的上下文和所述业务流程，生成所述至少一个NF中的每个NF的输入消息。The first coordinator generates an input message of each NF in the at least one NF according to the request message and the service flow, including: the first coordinator according to the context and location of the UE The business process generates an input message for each of the at least one NF.
可选的，所述第二网元包括用户签约信息存储单元、无线接入网RAN节点或第二协调器，所述第二协调器设置于所述核心网中。Optionally, the second network element includes a user subscription information storage unit, a radio access network RAN node, or a second coordinator, where the second coordinator is disposed in the core network.
这样，NF可以实现为无状态服务，即NF中可以不保存UE的状态、UE的上下文信息或者UE与各网元的交互信息。由于本发明实施例中的NF为无状态服务，NF的调用更加灵活，因而能够提高NF的可重用性，进而使网络的部署更加灵活。In this way, the NF can be implemented as a stateless service, that is, the state of the UE, the context information of the UE, or the interaction information between the UE and each network element may not be saved in the NF. Since the NF in the embodiment of the present invention is a stateless service, the call of the NF is more flexible, thereby improving the reusability of the NF, thereby making the deployment of the network more flexible.
可选的，所述核心网还包括协调器管理器，所述方法还包括：所述第一协调器接收协调器管理器发送的所述业务流程。Optionally, the core network further includes a coordinator manager, the method further includes: the first coordinator receiving the service flow sent by the coordinator manager.
可选的，所述方法还包括：所述第一协调器根据对所述业务的处理结果，向所述第一网元发送返回消息，使得第一网元能够确定核心网对该请求消息的处理结果。Optionally, the method further includes: the first coordinator sending a return message to the first network element according to a processing result of the service, so that the first network element can determine, by the core network, the request message. process result.
第二方面，本发明实施例提供了一种核心网中业务处理的方法，所述核心网包括协调器管理器、网络功能NF和协调器，所述方法包括：协调器管理器确定处理所述业务的流程，所述流程用于指示处理所述业务所需要使用的至少一个网络功能NF；所述协调器管理器根据所述流程确定所述至少一个NF的信息；所述协调器管理器根据所述流程和所述至少一个NF的信息，生成处理所述业务的业务流程，所述业务流程用于调用处理所述业务所需要使用的至少一个NF；所述协调器管理器向第一协调器发送所述业务流程，使得所述第一协调器根据所述业务流程，对所述业务进行处理。In a second aspect, an embodiment of the present invention provides a method for service processing in a core network, where the core network includes a coordinator manager, a network function NF, and a coordinator, and the method includes: the coordinator manager determines to process the a flow of a service for indicating at least one network function NF required to process the service; the coordinator manager determining information of the at least one NF according to the flow; the coordinator manager is based on Generating, by the process and the information of the at least one NF, a business process for processing the service, where the business process is used to invoke at least one NF required to process the service; the coordinator manager to the first coordination And sending the service process, so that the first coordinator processes the service according to the service process.
本发明实施例能够根据业务流程调用核心网中的网络功能，对UE的业务进行处理，该网络功能包括核心网中虚拟化的网元功能。本发明实施例将业务部署转化为软件部署，能够针对不同的业务场景选择和调用不同的网络功能，实现按需弹性组网，使得网络具有灵活的可扩展性、开放性和演进能力。The embodiment of the present invention can process the service of the UE according to the network function in the core network according to the service process, and the network function includes the function of the virtualized network element in the core network. The embodiment of the present invention converts the service deployment into a software deployment, and can select and invoke different network functions for different service scenarios to implement an on-demand elastic networking, so that the network has flexible scalability, openness, and evolution capability.
可选的，所述至少一个NF包括至少两个NF，所述流程还用于指示所需要使用的所述至少两个NF的逻辑顺序，所述业务流程用于按照所述逻辑顺序调用所述至少两个NF。 Optionally, the at least one NF includes at least two NFs, and the process is further used to indicate a logical sequence of the at least two NFs that are required to be used, where the service flow is used to invoke the according to the logical sequence. At least two NFs.
例如，协调器可以根据该业务流程，首先调用NF1，之后同时调用NF2和NF3，然后调用NF4，最后调用NF5。For example, the coordinator can first call NF 1 according to the business process, then call NF 2 and NF 3 at the same time, then call NF 4 , and finally call NF 5 .
可选的，所述核心网还包括NF管理器，所述协调器管理器根据所述流程确定所述至少一个NF的信息，包括：所述协调器管理器在所述至少一个NF中确定需要创建的NF；所述协调器管理器向NF管理器发送所述需要创建的NF的类型，以使得所述NF管理器根据所述NF的类型创建所述需要创建的NF；所述协调器管理器接收所述NF管理器发送的所述NF管理器创建的NF的信息。Optionally, the core network further includes an NF manager, where the coordinator manager determines the information of the at least one NF according to the process, including: the coordinator manager determines a requirement in the at least one NF The created NF; the coordinator manager sends the type of the NF that needs to be created to the NF manager, so that the NF manager creates the NF that needs to be created according to the type of the NF; the coordinator management The device receives information of the NF created by the NF manager sent by the NF manager.
可理解，当协调器管理器确定可以共享已有的NF时，协调器可以直接确定该已有的NF的信息，根据该已有的NF的信息，生成业务流程。当协调器确定不能够共享已有的NF或者协调器确定不存在需要使用的NF时，协调器管理器可以向NF管理器发送所述需要创建的NF的类型。It can be understood that when the coordinator manager determines that the existing NF can be shared, the coordinator can directly determine the information of the existing NF, and generate a service flow according to the information of the existing NF. When the coordinator determines that the existing NF cannot be shared or the coordinator determines that there is no NF to use, the coordinator manager can send the type of the NF that needs to be created to the NF manager.
可选的，所述NF的信息包括所述NF的接口参数和所述NF的地址。Optionally, the information about the NF includes an interface parameter of the NF and an address of the NF.
第三方面，本发明实施例提供了一种网络设备，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法，具体的，该网络设备包括用于执行上述第一方面或第一方面任意可能的实现方式中的方法的模块。In a third aspect, the embodiment of the present invention provides a network device, where the method of the foregoing first aspect or any possible implementation of the first aspect is implemented, where the network device includes Or a module of the method in any of the possible implementations of the first aspect.
第四方面，本发明实施例提供了一种网络设备，用于执行上述第二方面或第二方面的任意可能的实现方式中的方法，具体的，该网络设备包括用于执行上述第二方面或第二方面任意可能的实现方式中的方法的模块。In a fourth aspect, the embodiment of the present invention provides a network device, where the method of any of the foregoing second aspect or the second aspect is implemented, where the network device includes Or a module of the method in any of the possible implementations of the second aspect.
第五方面，本发明实施例提供了一种网络设备，该网络设备包括：存储器、处理器、收发器和总线***。其中，该存储器和该处理器通过该总线***相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。In a fifth aspect, an embodiment of the present invention provides a network device, where the network device includes: a memory, a processor, a transceiver, and a bus system. Wherein the memory and the processor are coupled by the bus system for storing instructions for executing instructions stored by the memory, and when the processor executes the instructions stored by the memory, the performing causes the processing The method of the first aspect or any possible implementation of the first aspect is performed.
第六方面，本发明实施例提供了一种网络设备，该网络设备包括：存储器、处理器、收发器和总线***。其中，该存储器和该处理器通过该总线***相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。In a sixth aspect, an embodiment of the present invention provides a network device, where the network device includes: a memory, a processor, a transceiver, and a bus system. Wherein the memory and the processor are coupled by the bus system for storing instructions for executing instructions stored by the memory, and when the processor executes the instructions stored by the memory, the performing causes the processing The method of the second aspect or any of the possible implementations of the second aspect is performed.
第七方面，本发明实施例提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方 式中的方法的指令。A seventh aspect of the present invention provides a computer readable medium for storing a computer program, the computer program comprising any possible implementation party for performing the first aspect or the first aspect The instruction of the method in the formula.
第八方面，本发明实施例提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。In an eighth aspect, an embodiment of the present invention provides a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the second aspect or any possible implementation of the second aspect.
附图说明DRAWINGS
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the embodiments of the present invention will be briefly described below. It is obvious that the drawings described below are only some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.
图1是本发明实施例的应用场景示意图。FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present invention.
图2是本发明实施例的一个核心网的示意性结构图。2 is a schematic structural diagram of a core network according to an embodiment of the present invention.
图3是本发明实施例的部署业务流程的示意性流程图。FIG. 3 is a schematic flowchart of a deployment service process according to an embodiment of the present invention.
图4是本发明一个实施例的核心网中业务处理的方法的示意性流程图。FIG. 4 is a schematic flowchart of a method for service processing in a core network according to an embodiment of the present invention.
图5是本发明一个具体实施例的核心网中业务处理的方法的示意***互流程图。FIG. 5 is a schematic interaction flowchart of a method for service processing in a core network according to an embodiment of the present invention.
图6是本发明另一个具体实施例的核心网中业务处理的方法的示意***互流程图。FIG. 6 is a schematic interaction flowchart of a method for service processing in a core network according to another embodiment of the present invention.
图7是本发明另一个具体实施例的核心网中业务处理的方法的示意***互流程图。FIG. 7 is a schematic interaction flowchart of a method for service processing in a core network according to another embodiment of the present invention.
图8是本发明另一个具体实施例的核心网中业务处理的方法的示意***互流程图。FIG. 8 is a schematic interaction flowchart of a method for service processing in a core network according to another embodiment of the present invention.
图9是本发明一个实施例的网络设备的示意性框图。9 is a schematic block diagram of a network device in accordance with an embodiment of the present invention.
图10是本发明另一个实施例的网络设备的示意性框图。FIG. 10 is a schematic block diagram of a network device according to another embodiment of the present invention.
图11是本发明另一个实施例的网络设备的示意性框图。11 is a schematic block diagram of a network device according to another embodiment of the present invention.
图12是本发明另一个实施例的网络设备的示意性框图。FIG. 12 is a schematic block diagram of a network device according to another embodiment of the present invention.
具体实施方式detailed description
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明的一部分实施例，而不是全部实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创 造性劳动的前提下所获得的所有其他实施例，都应属于本发明保护的范围。The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, those of ordinary skill in the art are not making innovations. All other embodiments obtained under the premise of causative labor are within the scope of protection of the present invention.
本发明实施例中，接入网可以为无线接入网(Radio Access Network，RAN)，具体的，可以为基站。基站可以是全球移动通信(Global System for Mobile communication，GSM)***或码分多址(Code Division Multiple Access，CDMA)***中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)***中的基站(NodeB)，还可以是LTE***中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是未来5G网络中的基站设备、小基站设备等，本发明对此并不限定。In the embodiment of the present invention, the access network may be a radio access network (RAN), and specifically, may be a base station. The base station may be a Global System for Mobile communication (GSM) system or a Base Transceiver Station (BTS) in a Code Division Multiple Access (CDMA) system, or may be a wideband code division multiple access ( A base station (NodeB) in a Wideband Code Division Multiple Access (WCDMA) system, which may also be an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a base station device, a small base station device, etc. in a future 5G network. The invention is not limited thereto.
用户设备可以经无线接入网与一个或多个核心网(Core Network)进行通信，UE可称为接入终端、终端设备、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。UE可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及未来5G网络中的终端设备等。The user equipment can communicate with one or more core networks via a radio access network, and the UE can be called an access terminal, a terminal device, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, and a remote terminal. , mobile device, user terminal, terminal, wireless communication device, user agent or user device. The UE may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), or a wireless communication function. Handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, and terminal devices in future 5G networks.
图1示出了SAE的架构图。SAE体系结构由演进的接入网(Evolved UMTS Terrestrial Radio Access Network，E-UTRAN)和演进的EPC组成，接入网的节点可以为基站(例如为eNodeB)。EPC中包含了MME、HSS、S-GW、PDN-GW，还包含策略控制和计费功能(Policy Control and Charging Rules Function，PCRF)和服务通用分组无线服务(General Packet Radio Service，GPRS)支持节点(Serving GPRS Support Node，SGSN)。Figure 1 shows the architecture of the SAE. The SAE architecture is composed of an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) and an evolved EPC. The node of the access network may be a base station (for example, an eNodeB). The EPC includes the MME, the HSS, the S-GW, and the PDN-GW, and further includes a Policy Control and Charging Rules Function (PCRF) and a General Packet Radio Service (GPRS) support node. (Serving GPRS Support Node, SGSN).
在图1所示的架构中，MME负责控制面的移动性管理，包括用户上下文和移动状态管理。HSS存储用户签约信息。S-GW是3GPP接入网络间的用户面锚点，是E-UTRAN的接口。PDN GW是3GPP接入网络和非3GPP接入网络之间的用户面锚点，是外部PDN网络的接口。在实际的网络部署中，逻辑网元S-GW和PDN GW都是合一部署的(除个别情况，如漫游)，一般统称为网关。In the architecture shown in Figure 1, the MME is responsible for the mobility management of the control plane, including user context and mobility state management. The HSS stores user subscription information. The S-GW is a user plane anchor between 3GPP access networks and is an interface of E-UTRAN. The PDN GW is a user plane anchor between the 3GPP access network and the non-3GPP access network, and is an interface of the external PDN network. In an actual network deployment, the logical network element S-GW and the PDN GW are all deployed in one (except for individual cases, such as roaming), and are generally referred to as gateways.
基于图1中的***架构，本发明实施例提供了如图2所示的核心网，该核心网包括协调器131、网络功能(Network Function，NF)132、协调器管 理器133和NF管理器134。该核心网可以与接入网连接，UE通过接入网与核心网进行通信。本发明实施例中，协调器131、NF132、协调器管理器133和NF管理器134可以部署在一个或者多个虚拟机上，即本发明实施例中，核心网可以由部署在一个或多个虚拟机上的多个组件组成。Based on the system architecture in FIG. 1, the embodiment of the present invention provides a core network as shown in FIG. 2, where the core network includes a coordinator 131, a network function (NF) 132, and a coordinator tube. The processor 133 and the NF manager 134. The core network can be connected to the access network, and the UE communicates with the core network through the access network. In the embodiment of the present invention, the coordinator 131, the NF 132, the coordinator manager 133, and the NF manager 134 may be deployed on one or more virtual machines. In the embodiment of the present invention, the core network may be deployed in one or more Composed of multiple components on a virtual machine.
其中，协调器131为核心网网元的外部接口，负责接收和返回UE交互信令，例如可以接收UE的业务请求，并向UE返回对该业务请求的执行结果。协调器131可以调用NF132。The coordinator 131 is an external interface of the core network element, and is responsible for receiving and returning the UE interaction signaling, for example, receiving the service request of the UE, and returning the execution result of the service request to the UE. The coordinator 131 can call the NF 132.
NF包括核心网中虚拟化的网元功能。本发明实施例中，利用虚拟化技术，可以将网络节点级别的功能分割为几个功能区块，每个功能区块可以分别以软件的方式实现为相应的NF，这样，核心网将不再局限于图1中的网络架构。例如，可以将MME的功能分割为移动性管理(Mobility Management，MM)和会话管理(Session Management，SM)两个功能模块，分别以软件的方式实现为相应的MM模块和SM模块。本发明实施例中，NF可以包括MM、SM和策略和计费控制(Policy and Charging Control，PCC)等功能模块。应理解，本发明实施例中，仅仅以该NF可以为上述功能模块为例进行描述，该NF也可以为实现核心网其他网元功能(例如S-GW或PDN GW等)的模块，并且本发明实施例并不限定NF的实现粒度。The NF includes virtualized network element functions in the core network. In the embodiment of the present invention, the function of the network node level can be divided into several functional blocks by using virtualization technology, and each functional block can be implemented as a corresponding NF in a software manner, so that the core network will no longer be used. Limited to the network architecture in Figure 1. For example, the functions of the MME may be divided into two functional modules: Mobility Management (MM) and Session Management (SM), which are respectively implemented in software as corresponding MM modules and SM modules. In the embodiment of the present invention, the NF may include a function module such as an MM, an SM, and a Policy and Charging Control (PCC). It should be understood that, in the embodiment of the present invention, the NF may be described as an example of the foregoing functional module, and the NF may also be a module for implementing other network element functions of the core network (for example, S-GW or PDN GW, etc.), and The embodiment of the invention does not limit the implementation granularity of the NF.
协调器管理器133可以执行各种协调器的管理功能，如协调器的实例化、更新或终止等。在协调器管理器133实例化协调器131时，协调器管理器133可以将业务流程定义部署到协调器131上，协调器131根据业务流程定义调用处理业务所需要使用的至少一个网络功能NF。本发明实施例中，该业务流程定义整体上可以看做一个业务流程，一个业务流程可以具有不同的业务流程分支，不同的业务流程分支可以处理UE的不同请求。本发明实施例中可以称业务流程定义为业务流程。具体的，业务流程可以表现为脚本的形式，本发明实施例对此不作限定。The coordinator manager 133 can perform management functions of various coordinators, such as instantiation, update, or termination of the coordinator. When the coordinator manager 133 instantiates the coordinator 131, the coordinator manager 133 can deploy the business process definition to the coordinator 131, which in accordance with the business process definition invokes at least one network function NF that is required to process the service. In the embodiment of the present invention, the business process definition can be regarded as a business process as a whole, and one business process can have different business process branches, and different business process branches can process different requests of the UE. In the embodiment of the present invention, a business process may be defined as a business process. Specifically, the business process may be in the form of a script, which is not limited by the embodiment of the present invention.
作为一例，业务流程中需要调用的NF可以为图2中的NF1、NF2、NF3、NF4和NF5，并且图2中的虚线的方向表示调用各个NF的顺序。具体的，协调器131根据该业务流程，首先调用NF1，之后同时调用NF2和NF3，然后调用NF4，最后调用NF5。As an example, the NFs that need to be invoked in the business process may be NF 1 , NF 2 , NF 3 , NF 4 , and NF 5 in FIG. 2, and the direction of the dotted line in FIG. 2 indicates the order in which the respective NFs are called. Specifically, the coordinator 131 first calls NF 1 according to the business process, then calls NF 2 and NF 3 at the same time, then calls NF 4 , and finally calls NF 5 .
NF管理器134可以执行各种NF的管理功能，如NF的实例化、更新或终止等。NF管理器可以根据协调器管理器133的指示，创建NF，并对核心 网中的NF进行管理。The NF manager 134 can perform various NF management functions, such as instantiation, update, or termination of the NF. The NF manager can create NFs according to the instructions of the coordinator manager 133, and the core The NF in the network is managed.
图3为本发明一个实施例的部署业务流程的方法的示意性流程图。应理解，图3示出了部署业务流程的方法的步骤或操作，但这些步骤或操作仅是示例，本发明实施例还可以执行其他操作或者图3中的各个操作的变形。此外，图3中的各个步骤可以按照与图3呈现的不同的顺序来执行，并且有可能并非要执行图3中的全部操作。图3中与图2中相同的附图标记表示相同或相似的含义，为了简洁，此处不再赘述。FIG. 3 is a schematic flowchart of a method for deploying a service flow according to an embodiment of the present invention. It should be understood that FIG. 3 illustrates steps or operations of a method of deploying a business process, but these steps or operations are merely examples, and embodiments of the present invention may perform other operations or variations of the various operations in FIG. Moreover, the various steps in FIG. 3 may be performed in a different order than that presented in FIG. 3, and it is possible that not all operations in FIG. 3 are to be performed. The same reference numerals in FIG. 3 as those in FIG. 2 denote the same or similar meanings, and are not described herein again for the sake of brevity.
202，协调器管理器133创建协调器实例。202, the coordinator manager 133 creates a coordinator instance.
本发明实施例中，协调器实例即上文中所述的协调器。协调器实例用于处理多个UE的业务请求。当核心网中的协调器实例负载比较大，例如一个协调器同时服务的UE的数量超过负荷时，需要创建新的协调器实例，实现核心网中协调器实例的负载均衡。In the embodiment of the present invention, the coordinator instance is the coordinator described above. The coordinator instance is used to process service requests from multiple UEs. When the coordinator instance load in the core network is relatively large, for example, when the number of UEs served by one coordinator exceeds the load, a new coordinator instance needs to be created to implement load balancing of the coordinator instance in the core network.
在202中，协调器管理器133在创建协调器实例时，需要确定处理UE的业务的流程，例如确定处理UE的业务需要使用的网元功能。当需要使用至少两个网元功能时，还需要确定使用的至少两个网元功能的顺序。也就是说，协调器管理器在创建协调器实例时，需要确定处理该业务时需要调用的NF，以及所需要调用的各个NF的先后顺序。In 202, the coordinator manager 133, when creating the coordinator instance, needs to determine the flow of processing the UE's traffic, such as determining the network element function needed to process the UE's traffic. When at least two network element functions need to be used, it is also necessary to determine the order of at least two network element functions used. That is to say, when the coordinator manager creates the coordinator instance, it needs to determine the NF that needs to be called when the service is processed, and the order of the NFs that need to be called.
204，协调器管理器133向NF管理器134发送实例化NF请求。204, the coordinator manager 133 sends an instantiation NF request to the NF manager 134.
协调器管理器133根据处理上述流程，可以确定处理该业务所需要调用的NF，本发明实施例中，可以称NF为NF实例。The coordinator manager 133 can determine the NF that needs to be invoked to process the service according to the foregoing process. In the embodiment of the present invention, the NF can be referred to as an NF instance.
本发明实施例中，NF132中已经建立的NF实例中可能会存在协调器实例中需要调用的一个或多个NF实例。协调器管理器133根据相关的隔离策略可以确定在NF132中可以调用的NF实例，这时不需要重新建立该NF实例。例如，202中的协调器实例中包括的一个NF实例为NFn。如果协调器管理器133确定可以共享NF132中已经存在的NFn，则可以不创建该NFn。如果协调器管理器133确定不存在NFn，或者不能共享已经存在的NFn，则需要创建该NFn。In the embodiment of the present invention, one or more NF instances that need to be called in the coordinator instance may exist in the NF instance that has been established in the NF 132. The coordinator manager 133 can determine the NF instance that can be called in the NF 132 according to the associated isolation policy, at which point it is not necessary to re-establish the NF instance. For example, a NF instance instance coordinator 202 is included in NF n. If the coordinator manager 133 determines that the NF n already present in the NF 132 can be shared, then the NF n may not be created. If the coordinator manager 133 determines that there are NF n, can not be shared or existing NF n, you need to create the NF n.
在协调器管理器133确定需要创建的NF实例之后，向NF管理器134发送实例化NF请求，以使得NF根据该实例化NF请求来创建所需要创建的NF实例。该实例化NF请求中可以携带NF实例的类型，例如NF请求中携带的请求创建的NF为MM。 After the coordinator manager 133 determines the NF instance that needs to be created, an instantiation NF request is sent to the NF manager 134 to cause the NF to create the NF instance that needs to be created based on the instantiated NF request. The NF request may carry the type of the NF instance, for example, the NF created by the request carried in the NF request is MM.
206，NF管理器134向协调器管理器133发送实例化NF应答。206, the NF manager 134 sends an instantiation NF response to the coordinator manager 133.
具体的，NF管理器134根据相关隔离策略，例如其他NF共享物理机或需要物理隔离等，创建实例化NF请求中需要创建的NF实例。NF管理器在创建NF模块之后，向协调器管理器133发送实例化NF应答，实例化NF应答中包括创建的NF实例的信息。该信息可以包括NF实例地址和NF接口参数，还可以包括NF实例标识等信息，本发明实施例对此不作限定。Specifically, the NF manager 134 creates an NF instance that needs to be created in the instantiated NF request according to a related isolation policy, such as other NF shared physical machines or physical isolation. After creating the NF module, the NF manager sends an instantiated NF response to the coordinator manager 133, instantiating information of the created NF instance in the NF response. The information may include the NF instance address and the NF interface parameter, and may also include information such as the NF instance identifier, which is not limited by the embodiment of the present invention.
208，协调器管理器133部署业务流程。该业务流程用于调用处理上述业务需要使用的至少一个NF实例。具体的，可以采用模板或者业务流程模型来实现业务流程，本发明对此不作限定。208, the coordinator manager 133 deploys the business process. The business process is used to invoke at least one NF instance that needs to be used to process the above services. Specifically, the template or the business process model may be used to implement the business process, which is not limited by the present invention.
210，协调器131存储业务流程，并向协调器管理器133返回应答消息。210, the coordinator 131 stores the business process and returns a response message to the coordinator manager 133.
本发明实施例中，当协调器管理器133更新业务流程时，需要判断是否需要更新NF实例。当协调器管理器133确定需要更新NF实例时，需要创建该更新的NF实例。这时，需要执行上述204至210中对应的各个步骤，来实现业务流程的更新。具体的，在协调器131依据相关策略，实现业务流程的更新时，已有的流程可以继续按照原有定义执行，新建的流程可以按照新的定义执行，或者暂停所有UE的现有流程，统一按照新的业务流程执行，或者依据UE的状态选择部分UE，将其业务流程切换到新的业务流程上。In the embodiment of the present invention, when the coordinator manager 133 updates the service process, it is necessary to determine whether the NF instance needs to be updated. When the coordinator manager 133 determines that an NF instance needs to be updated, the updated NF instance needs to be created. At this time, it is necessary to perform the corresponding steps in the above 204 to 210 to implement the update of the business process. Specifically, when the coordinator 131 implements the update of the business process according to the relevant policy, the existing process can continue to be executed according to the original definition, and the newly created process can be executed according to the new definition, or the existing processes of all UEs are suspended, and unified. Execute according to the new business process, or select part of the UE according to the status of the UE, and switch its business process to the new business process.
图4示出了本发明一个实施例的核心网中业务处理的方法的示意性流程图。该方法由上述核心网执行。图4中的方法包括：FIG. 4 is a schematic flowchart of a method for service processing in a core network according to an embodiment of the present invention. The method is performed by the core network described above. The method in Figure 4 includes:
310，第一协调器接收第一网元发送的请求消息，所述请求消息用于请求对UE的业务进行处理。310. The first coordinator receives a request message sent by the first network element, where the request message is used to request processing of the service of the UE.
在具体的实施例中，该第一协调器为为所述UE服务的协调器，该第一协调器中包括业务流程。该第一网元可以为UE或RAN节点(例如基站)。该请求消息为所述UE的业务的请求消息，例如为附着请求、(Tracking Area Update，TAU)请求、服务请求或切换(handover)请求。相应的，该业务可以包括UE的附着业务、UE的跟踪区更新(Tracking Area Update，TAU)业务、UE的服务业务或UE的切换(handover)业务等。本发明实施例中，该请求消息可以为UE的其他请求消息，本发明实施例对此不作限定。下文会结合具体的例子进行详细描述，此处不再详述。In a specific embodiment, the first coordinator is a coordinator serving the UE, and the first coordinator includes a service flow. The first network element can be a UE or a RAN node (e.g., a base station). The request message is a request message of the service of the UE, for example, a Tracking Area Update (TAU) request, a service request, or a handover request. Correspondingly, the service may include an attach service of the UE, a Tracking Area Update (TAU) service of the UE, a service service of the UE, or a handover service of the UE. In the embodiment of the present invention, the request message may be another request message of the UE, which is not limited in this embodiment of the present invention. A detailed description will be given below with specific examples, which will not be described in detail herein.
320，所述第一协调器根据所述请求消息和所述请求消息对应的业务流程，对所述业务进行处理。所述业务流程用于调用处理所述业务所需要使用 的至少一个网络功能NF。320. The first coordinator processes the service according to the service flow corresponding to the request message and the request message. The business process is used to invoke the processing required to process the service At least one network function NF.
具体的，所述业务对应的业务流程可以为业务流程中的一个分支。第一协调器根据310中的请求消息，确定与该请求消息对应的业务流程，并根据该业务流程，对请求的业务进行处理。这里，NF和业务流程可以参见上述图2和图3中的描述，为避免重复，这里不再赘述。Specifically, the business process corresponding to the service may be a branch in the business process. The first coordinator determines a service flow corresponding to the request message according to the request message in 310, and processes the requested service according to the service flow. Here, the NF and the business process can be referred to the descriptions in FIG. 2 and FIG. 3 above, and in order to avoid repetition, details are not described herein again.
可选的，本发明实施例中，当业务流程用于调用的NF的数量为至少两个时，可以基于并发或者顺序的架构，实现对该至少两个NF的调用。这样，所述业务流程用于按照逻辑顺序调用所述至少两个NF。Optionally, in the embodiment of the present invention, when the number of NFs used by the service process for calling is at least two, the calling of the at least two NFs may be implemented based on a concurrent or sequential architecture. Thus, the business process is for calling the at least two NFs in a logical order.
可选的，本发明实施例中，可以根据所述请求消息和所述业务流程，生成所述至少一个NF中的每个NF的输入消息，每个NF的输入消息用于调用该NF。Optionally, in the embodiment of the present invention, an input message of each NF of the at least one NF may be generated according to the request message and the service flow, and an input message of each NF is used to invoke the NF.
应理解，当第一协调器根据输入消息调用NF时，NF可以根据输入消息生成输出消息，并将该输出消息返回给第一协调器。而在特定情况下，NF的输入消息仅用于单向通知该NF，此时该NF可以不需要生成输出消息。It should be understood that when the first coordinator invokes the NF based on the input message, the NF may generate an output message based on the input message and return the output message to the first coordinator. In a specific case, the NF input message is only used to notify the NF in one direction, and the NF may not need to generate an output message.
还应理解，当需要调用的NF的数量为至少两个时，可以根据在先调用的NF返回的输出消息，构造在后调用的NF的输入消息。It should also be understood that when the number of NFs to be called is at least two, an input message of the NF that is called later may be constructed based on the output message returned by the previously invoked NF.
可选的，本发明实施例中，当NF向第一协调器返回输出消息时，第一协调器可以根据所述NF的输出消息，确定对所述业务的处理结果。Optionally, in the embodiment of the present invention, when the NF returns an output message to the first coordinator, the first coordinator may determine a processing result of the service according to the output message of the NF.
可选的，第一协调器可以根据对业务的处理结果，向第一网元发送返回消息。Optionally, the first coordinator may send a return message to the first network element according to the processing result of the service.
作为一个具体的实施例，第一协调器131根据请求消息和图2中所示的该业务流程，首先生成NF1的输入消息，然后调用NF1。获得NF1的输出消息之后，根据NF1的输出消息，构造NF2和NF3的输入消息，并同时调用NF2和NF3。待NF2和NF3返回输出消息之后，根据NF2和NF3的输出消息，构造NF4的输入消息，调用NF4，获取NF4的输出消息。然后根据NF4的输出消息，构造NF5的输入消息，调用NF5，最后获取NF5的输出消息。之后，可以根据NF5的输出消息，向第一网元发送返回消息。As a specific embodiment, the first coordinator 131 first generates an input message of NF 1 according to the request message and the business flow shown in FIG. 2, and then calls NF 1 . After obtaining the output message NF 1, according to the NF output messages 1, 2 and NF NF input configuration message 3, and also calling NF 2 and NF 3. After 2 and NF NF 3 to be output message is returned, in accordance with the output message NF NF 2 and 3, the configuration of the input message 4 NF, NF 4 call, obtain an output message 4 NF. The message is then output NF 4, the configuration of the input message. 5 NF, NF call. 5, NF. 5 finally obtain the output message. Thereafter, a return message can be sent to the first network element according to the output message of NF 5 .
可选的，本发明实施例中，在320之前，当第一协调器中不存在UE的上下文时，可以从第二网元获取UE的数据信息，并根据所述数据信息，创建所述UE的上下文。这时，可以根据所述上下文、所述请求消息和所述业务流程，对所述业务进行处理。这里，第二网元可以包括用户签约信息存储 单元、RAN节点或第二协调器，该用户签约信息存储单元例如可以为HSS。Optionally, in the embodiment of the present invention, before the 320, when the context of the UE does not exist in the first coordinator, the data information of the UE may be acquired from the second network element, and the UE is created according to the data information. Context. At this time, the service may be processed according to the context, the request message, and the business process. Here, the second network element may include user subscription information storage. The unit, the RAN node or the second coordinator, the user subscription information storage unit may be, for example, an HSS.
这里，该第二协调器为核心网中不同于第一协调器的另一个协调器。当第一协调器和第二协调器分别位于两个数据中心，并且UE发生跨数据中心的切换时，第一协调器和第二协调器可以进行交互，实现UE的状态和上下文数据的传输。下文会结合具体的例子进行详细描述，此处不再详述。Here, the second coordinator is another coordinator in the core network that is different from the first coordinator. When the first coordinator and the second coordinator are respectively located in two data centers, and the UE performs handover across the data center, the first coordinator and the second coordinator may interact to implement transmission of status and context data of the UE. A detailed description will be given below with specific examples, which will not be described in detail herein.
这样，NF可以实现为无状态服务，即NF中可以不保存UE的状态、UE的上下文信息或者UE与各网元的交互信息。由于本发明实施例中的NF为无状态服务，NF的调用更加灵活，因而能够提高NF的可重用性，进而使网络的部署更加灵活。In this way, the NF can be implemented as a stateless service, that is, the state of the UE, the context information of the UE, or the interaction information between the UE and each network element may not be saved in the NF. Since the NF in the embodiment of the present invention is a stateless service, the call of the NF is more flexible, thereby improving the reusability of the NF, thereby making the deployment of the network more flexible.
具体的，当第一协调器中不存在UE的上下文时，第一协调器可以向其他网元(例如上述第二网元)发送请求，以获取UE的数据信息，该数据信息可以为UE的临时标识、S1应用协议(S1 Application Protocol，S1AP)标识、移动性管理状态或者UE的部分签约数据中的至少一种。第一协调器可以根据该数据信息，建立UE的上下文。在调用NF时，协调器可以根据UE的上下文，实现对NF的调用。本发明实施例中，根据不同的业务的请求消息，协调器可以与不同的网元进行交互，获取数据信息。并且在获取了上述NF的返回消息之后，协调器可以更新UE的上下文。下文会结合具体的例子进行详细描述，此处不再详述。Specifically, when the context of the UE does not exist in the first coordinator, the first coordinator may send a request to the other network element (for example, the second network element) to obtain data information of the UE, where the data information may be the UE. At least one of a temporary identifier, an S1 Application Protocol (S1AP) identifier, a mobility management state, or partial subscription data of the UE. The first coordinator can establish a context of the UE according to the data information. When the NF is invoked, the coordinator can implement a call to the NF according to the context of the UE. In the embodiment of the present invention, the coordinator can interact with different network elements to obtain data information according to request messages of different services. And after obtaining the return message of the above NF, the coordinator can update the context of the UE. A detailed description will be given below with specific examples, which will not be described in detail herein.
应注意，本发明实施例中，上下文也可以存储在NF中，这时，协调器中可以不存储UE的上下文，协调器在调用NF时构造的输入消息中可以不包含UE的上下文相关的数据，本发明实施例对此不作限定。It should be noted that, in the embodiment of the present invention, the context may also be stored in the NF. In this case, the context of the UE may not be stored in the coordinator, and the coordinator may not include the context-related data of the UE in the input message constructed when the NF is invoked. This embodiment of the present invention does not limit this.
本发明实施例能够根据请求消息对应的业务流程调用核心网中的网络功能，对UE的业务进行处理，该网络功能包括核心网中虚拟化的网元功能。本发明实施例将业务部署转化为软件部署，能够针对不同的业务场景选择和调用不同的网络功能，实现按需弹性组网，使得网络具有灵活的可扩展性、开放性和演进能力。The embodiment of the present invention can process the service of the UE according to the network function in the core network according to the service flow corresponding to the request message, and the network function includes the function of the virtualized network element in the core network. The embodiment of the present invention converts the service deployment into a software deployment, and can select and invoke different network functions for different service scenarios to implement an on-demand elastic networking, so that the network has flexible scalability, openness, and evolution capability.
下文将结合具体的例子对核心网中业务处理的方法进行详细描述。The method of service processing in the core network will be described in detail below with reference to specific examples.
图5为本发明应用于一个实施例的核心网中业务处理的方法的示意性流程图。图5中的MM 150、SM 160和PCC 170为该实施例中所需要调用的网络功能。应理解，图5示出了核心网中业务处理的方法的步骤或操作，但这些步骤或操作仅是示例，本发明实施例还可以执行其他操作或者图5中的 各个操作的变形。此外，图5中的各个步骤可以按照与图5呈现的不同的顺序来执行，并且有可能并非要执行图5中的全部操作。FIG. 5 is a schematic flowchart of a method for processing a service in a core network according to an embodiment of the present invention. The MM 150, SM 160, and PCC 170 in Figure 5 are the network functions that need to be invoked in this embodiment. It should be understood that FIG. 5 illustrates steps or operations of the method of service processing in the core network, but these steps or operations are merely examples, and other operations may be performed in the embodiment of the present invention or in FIG. 5 Deformation of each operation. Moreover, the various steps in FIG. 5 may be performed in a different order than that presented in FIG. 5, and it is possible that not all operations in FIG. 5 are to be performed.
402，UE 110向协调器131发送附着请求。402. The UE 110 sends an attach request to the coordinator 131.
该附着请求为图4中的请求消息的一种。当协调器接收到UE发送的附着请求之后，可以根据预先存储的对应于附着请求的业务流程对UE的附着请求进行处理。The attach request is one of the request messages in FIG. After the coordinator receives the attach request sent by the UE, the attach request of the UE may be processed according to a pre-stored service flow corresponding to the attach request.
404，协调器131向HSS 140发送用户认证授权请求。404. The coordinator 131 sends a user authentication authorization request to the HSS 140.
406，HSS 140向协调器131发送用户认证授权响应。406. The HSS 140 sends a user authentication authorization response to the coordinator 131.
可理解，如果协调器本地不存在UE的上下文，协调器则需要与HSS交互，进行认证和授权，以获取UE的数据信息，该数据信息可以参见上述图4的描述。It can be understood that if the coordinator does not have the context of the UE locally, the coordinator needs to interact with the HSS to perform authentication and authorization to obtain data information of the UE. For the data information, refer to the description of FIG. 4 above.
408，协调器131向HSS 140发送更新位置请求。408, the coordinator 131 sends an update location request to the HSS 140.
410，HSS 140向协调器131发送更新位置响应。410. The HSS 140 sends an update location response to the coordinator 131.
408和410步骤中，协调器与HSS交互，获取UE的相关签约数据。在404至410之后，协调器可以根据获取的数据信息和相关签约数据，创建UE的上下文。In steps 408 and 410, the coordinator interacts with the HSS to obtain related subscription data of the UE. After 404 to 410, the coordinator can create a context of the UE based on the acquired data information and associated subscription data.
412，协调器131向MM 150发送移动管理请求。MM150为协调器中的一个功能模块，该移动管理请求为协调器根据业务流程和UE的上下文，构造的MM模块的输入消息。412, the coordinator 131 sends a mobility management request to the MM 150. The MM 150 is a functional module in the coordinator, and the mobility management request is an input message of the MM module constructed by the coordinator according to the service flow and the context of the UE.
414，MM 150根据移动管理请求，进行移动管理计算。414. The MM 150 performs mobility management calculation according to the mobility management request.
416，MM 150根据移动管理计算的结果，向协调器131返回移动管理响应。416. The MM 150 returns a mobility management response to the coordinator 131 according to the result of the mobility management calculation.
412至416步骤中，协调器131调用MM 150。具体的，协调器获取UE的签约信息并创建UE的上下文后，将UE相关信息发送给MM模块，MM模块进行相应的计算，包括诸如分配跟踪区列表(Tracking Area list，TA list)等操作，将计算结果返回给协调器，协调器更新UE的上下文。In steps 412 to 416, the coordinator 131 calls the MM 150. Specifically, after acquiring the subscription information of the UE and creating the context of the UE, the coordinator sends the UE related information to the MM module, and the MM module performs corresponding calculation, including operations such as a Tracking Area List (TA list). The calculation result is returned to the coordinator, which updates the context of the UE.
418，协调器131向SM 160发送会话管理请求。SM 160为协调器中的网络功能，该会话管理请求为协调器根据业务流程和UE的上下文，构造的SM模块的输入消息。418, the coordinator 131 sends a session management request to the SM 160. The SM 160 is a network function in the coordinator that is an input message of the SM module constructed by the coordinator according to the business process and the context of the UE.
420，SM 160根据会话管理请求，进行会话管理计算。420. The SM 160 performs session management calculation according to the session management request.
422，SM 160根据会话管理计算的结果，向协调器131返回会话管理响 应。422. The SM 160 returns a session management response to the coordinator 131 according to the result of the session management calculation. should.
418至422步骤中，协调器131调用SM 160。具体的，协调器将UE相关信息发送给SM模块，SM管理模块进行相应计算，包括诸如分配互联网协议(Internet Protocol，IP)地址、选择服务网关等操作，将计算结果返回给协调器，协调器更新UE上下文。In steps 418 to 422, the coordinator 131 calls the SM 160. Specifically, the coordinator sends the UE related information to the SM module, and the SM management module performs corresponding calculations, including operations such as assigning an Internet Protocol (IP) address, selecting a service gateway, and the like, and returning the calculation result to the coordinator, the coordinator Update the UE context.
424，协调器131向PCC 170发送IP联通接入网络(IP-Connectivity Access Network，IP-CAN)会话建立指示。424. The coordinator 131 sends an IP-Connectivity Access Network (IP-CAN) session establishment indication to the PCC 170.
426，PCC 170向协调器131返回IP-CAN会话建立应答。426, the PCC 170 returns an IP-CAN session establishment response to the coordinator 131.
424至426步骤中，协调器131调用PCC 170。具体的，协调器将UE相关信息发送给PCC模块，PCC模块计算UE的相关计费与服务质量(Quality of Service，QoS)控制策略，并将相关内容返回给协调器，协调器更新UE上下文。In steps 424 to 426, the coordinator 131 calls the PCC 170. Specifically, the coordinator sends the UE related information to the PCC module, and the PCC module calculates a related charging and quality of service (QoS) control policy of the UE, and returns related content to the coordinator, and the coordinator updates the UE context.
428，协调器131向SM 160发送创建会话请求。428, the coordinator 131 sends a create session request to the SM 160.
430，SM 160根据创建会话请求，与服务网关进行交互，并配置建立数据路径。430. The SM 160 interacts with the serving gateway according to the create session request, and configures to establish a data path.
432，SM 160向协调器131返回创建会话响应。432. The SM 160 returns a create session response to the coordinator 131.
428至432步骤中，协调器131再一次调用SM 160。具体的，协调器与SM管理模块交互，完成创建会话流程。In steps 428 to 432, the coordinator 131 calls the SM 160 again. Specifically, the coordinator interacts with the SM management module to complete the process of creating a session.
434，协调器131将附着接收消息返回给UE 110。434, the coordinator 131 returns an attach reception message to the UE 110.
协调器基于MM模块、SM模块和PCC模块的返回消息，构造对附着请求的应答消息，并将应答消息发送给UE。The coordinator constructs a response message to the attach request based on the return message of the MM module, the SM module, and the PCC module, and sends a response message to the UE.
436，UE 110发送附着完成消息给协调器131。436. The UE 110 sends an attach complete message to the coordinator 131.
438，协调器131向PCC 170发送修改承载请求。438. The coordinator 131 sends a modify bearer request to the PCC 170.
440，PCC 170根据修改承载请求，与服务网关进行交互，配置修改数据路径。440. The PCC 170 interacts with the serving gateway according to the modified bearer request, and configures the modified data path.
442，PCC 170向协调器131返回修改承载响应。442. The PCC 170 returns a modified bearer response to the coordinator 131.
438至442步骤中，协调器131再一次调用PCC 170。具体的，协调器与PCC管理模块交互，完成修改承载流程。In steps 438 through 442, the coordinator 131 calls the PCC 170 again. Specifically, the coordinator interacts with the PCC management module to complete the modification of the bearer process.
444，协调器131向HSS 140发送通知请求。444, the coordinator 131 sends a notification request to the HSS 140.
446，HSS 140向协调器131返回通知响应。446. The HSS 140 returns a notification response to the coordinator 131.
444和446步骤中，协调器与HSS交互，更新UE的相关数据，完成附 着流程。In steps 444 and 446, the coordinator interacts with the HSS to update the relevant data of the UE, and completes the attachment. The process.
本发明实施例中，核心网根据UE的附着请求，根据附着请求对应的业务流程，实现了UE的附着流程，协调器作为对外交互的接口，实现了外部信令的接收和发送以及NF(例如MM、SM和PCC)的调用，并且对UE的状态和上下文数据进行了更新，从而完成了UE的附着过程。In the embodiment of the present invention, the core network implements the attach procedure of the UE according to the service request corresponding to the attach request according to the attach request of the UE, and the coordinator acts as an external interaction interface, and implements external signaling reception and transmission and NF (for example, The MM, SM, and PCC) are invoked, and the state and context data of the UE are updated, thereby completing the attachment process of the UE.
图6为本发明的另一个实施例的核心网中业务处理的方法的示意性流程图。图6中的MM 150、SM 160和PCC 170分别为第一协调器1311需要调用的网络功能。图6中的第一协调器1311和第二协调器1312均可以为上述图2中的协调器。FIG. 6 is a schematic flowchart of a method for service processing in a core network according to another embodiment of the present invention. The MM 150, SM 160, and PCC 170 in FIG. 6 are respectively network functions that the first coordinator 1311 needs to invoke. The first coordinator 1311 and the second coordinator 1312 in FIG. 6 may each be the coordinator in FIG. 2 described above.
应理解，图6示出了核心网中业务处理的方法的步骤或操作，但这些步骤或操作仅是示例，本发明实施例还可以执行其他操作或者图6中的各个操作的变形。此外，图6中的各个步骤可以按照与图6呈现的不同的顺序来执行，并且有可能并非要执行图6中的全部操作。It should be understood that FIG. 6 illustrates steps or operations of the method of service processing in the core network, but these steps or operations are merely examples, and embodiments of the present invention may perform other operations or variations of the operations in FIG. Moreover, the various steps in FIG. 6 may be performed in a different order than that presented in FIG. 6, and it is possible that not all operations in FIG. 6 are to be performed.
502，UE 110向第一协调器1311发送TAU请求。502. The UE 110 sends a TAU request to the first coordinator 1311.
该TAU请求为图4中的业务请求消息的一种。当第一协调器接收到UE发送的TAU请求之后，可以根据预先存储的对应于TAU请求的业务流程对UE的TAU请求进行处理。The TAU request is one of the service request messages in FIG. After receiving the TAU request sent by the UE, the first coordinator may process the TAU request of the UE according to a pre-stored service flow corresponding to the TAU request.
504，第一协调器1311向第二协调器1312发送UE上下文请求。504. The first coordinator 1311 sends a UE context request to the second coordinator 1312.
506，第二协调器1312向第一协调器1312发送UE上下文响应。506. The second coordinator 1312 sends a UE context response to the first coordinator 1312.
508，第一协调器1311向第二协调器1312发送UE上下文应答。508. The first coordinator 1311 sends a UE context response to the second coordinator 1312.
第一协调器首先按照相关信息选择第二协调器，例如根据TAU请求中的第二协调器的ID，并和第二协调器交互，以获取UE的签约及上下文数据，并保存UE的签约信息和上下文数据。The first coordinator first selects the second coordinator according to the related information, for example, according to the ID of the second coordinator in the TAU request, and interacts with the second coordinator to acquire the subscription and context data of the UE, and saves the subscription information of the UE. And context data.
本发明实施例中，当两个协调器分别位于两个数据中心，并且UE发生跨数据中心的切换时，两个协调器可以进行交互，实现UE的状态和上下文数据的传输。In the embodiment of the present invention, when two coordinators are respectively located in two data centers, and the UE performs handover across the data center, the two coordinators can interact to implement the state of the UE and the transmission of the context data.
510，第一协调器1312向MM 150发送移动管理请求。510. The first coordinator 1312 sends a mobility management request to the MM 150.
512，MM150根据该移动管理请求，进行移动管理计算。512. The MM150 performs mobility management calculation according to the mobility management request.
514，MM150向第一协调器1311发送移动管理响应。514. The MM 150 sends a mobility management response to the first coordinator 1311.
510至514步骤中，第一协调器1311调用MM150。具体的，第一协调器将UE相关信息发送给MM模块，MM管理模块进行相应计算，包括诸如 重新分配TA List等操作，将计算结果返回给第一协调器，第一协调器更新UE上下文。In steps 510 to 514, the first coordinator 1311 calls the MM 150. Specifically, the first coordinator sends the UE related information to the MM module, and the MM management module performs corresponding calculation, including, for example, Re-allocating operations such as TA List, returning the calculation result to the first coordinator, and the first coordinator updates the UE context.
516，第一协调器1311向SM160发送会话管理请求。516. The first coordinator 1311 sends a session management request to the SM160.
518，SM 160根据会话管理请求，进行会话管理计算。518. The SM 160 performs session management calculation according to the session management request.
520，SM 160向第一协调器1311发送服务网关响应。520. The SM 160 sends a serving gateway response to the first coordinator 1311.
516至520步骤中，第一协调器1311调用SM160。第一协调器将UE相关信息发送给SM模块，SM管理模块进行相应计算，包括诸如是否重新选择服务网关(GW-U)等操作，将计算结果返回给第一协调器，第一协调器更新UE上下文。In steps 516 to 520, the first coordinator 1311 calls the SM 160. The first coordinator sends the UE related information to the SM module, and the SM management module performs corresponding calculations, including operations such as whether to reselect the serving gateway (GW-U), and returns the calculation result to the first coordinator, and the first coordinator updates. UE context.
522，第一协调器1311向PCC 170发送IP-CAN会话修改指示。522. The first coordinator 1311 sends an IP-CAN session modification indication to the PCC 170.
524，PCC170向第一协调器1311发送IP-CAN会话修改应答。524. The PCC 170 sends an IP-CAN session modification response to the first coordinator 1311.
522至524步骤中，第一协调器1311调用PCC 170。具体的，第一协调器将UE相关信息发送给PCC模块，PCC模块重新计算UE的相关计费与服务质量(Quality of Service，QoS)控制策略，并将相关内容返回给第一协调器，第一协调器更新UE上下文。In steps 522 to 524, the first coordinator 1311 calls the PCC 170. Specifically, the first coordinator sends the UE related information to the PCC module, and the PCC module recalculates the related charging and quality of service (QoS) control policy of the UE, and returns related content to the first coordinator, A coordinator updates the UE context.
526，第一协调器1311向SM 160发送修改承载请求。526. The first coordinator 1311 sends a modify bearer request to the SM 160.
528，SM 160与服务网关交互，配置修改数据路径。528. The SM 160 interacts with the service gateway and configures a modified data path.
530，SM160向第一协调器1311发送修改承载响应。530. The SM 160 sends a modify bearer response to the first coordinator 1311.
526至530步骤中，第一协调器1311再一次调用SM 160。第一协调器与SM管理模块交互，完成修改承载流程。In steps 526 to 530, the first coordinator 1311 calls the SM 160 again. The first coordinator interacts with the SM management module to complete the modification of the bearer process.
532，第一协调器1311向HSS140发送更新位置请求。532. The first coordinator 1311 sends an update location request to the HSS 140.
534，HSS 140向第一协调器发送更新位置响应。534. The HSS 140 sends an update location response to the first coordinator.
532和534的步骤中，第一协调器与HSS交互，更新UE的相关数据。In the steps of 532 and 534, the first coordinator interacts with the HSS to update the relevant data of the UE.
536，第一协调器1311向UE110发送TAU接收消息。536. The first coordinator 1311 sends a TAU Receive message to the UE 110.
第一协调器基于MM模块、SM模块和PCC模块的返回消息，构造对TAU请求的应答消息，并将应答消息发送给UE，该应答消息例如为TAU接收消息。The first coordinator constructs a response message to the TAU request based on the return message of the MM module, the SM module, and the PCC module, and sends a response message to the UE, for example, a TAU receiving message.
538，UE110向第一协调器发送TAU完成消息。538. The UE 110 sends a TAU Complete message to the first coordinator.
本发明实施例中，核心网根据UE的TAU请求，根据TAU请求对应的业务流程，实现了UE的TAU流程。第一协调器作为对外交互的接口，实现了与第二协调器的交互并完成了UE的状态及上下文的传输，实现外部信 令的接收和发送以及NF(例如MM、SM和PCC)的调用，并且对UE的状态和上下文数据进行了更新，从而完成了UE的TAU过程。In the embodiment of the present invention, the core network implements the TAU process of the UE according to the TAU request of the UE and according to the service flow corresponding to the TAU request. The first coordinator acts as an interface for external interaction, implements interaction with the second coordinator, and completes transmission of the state and context of the UE, and implements an external letter. The reception and transmission of the command and the invocation of the NF (eg, MM, SM, and PCC), and the status and context data of the UE are updated, thereby completing the TAU procedure of the UE.
图7为本发明应的另一个实施例的核心网中业务处理的方法的示意性流程图。图7中的SM160和PCC 170分别为协调器131需要调用的网络功能。FIG. 7 is a schematic flowchart of a method for service processing in a core network according to another embodiment of the present invention. The SM 160 and the PCC 170 in FIG. 7 are respectively network functions that the coordinator 131 needs to invoke.
应理解，图7示出了核心网中业务处理的方法的步骤或操作，但这些步骤或操作仅是示例，本发明实施例还可以执行其他操作或者图7中的各个操作的变形。此外，图7中的各个步骤可以按照与图7呈现的不同的顺序来执行，并且有可能并非要执行图7中的全部操作。It should be understood that FIG. 7 illustrates steps or operations of the method of service processing in the core network, but these steps or operations are merely examples, and embodiments of the present invention may perform other operations or variations of the operations in FIG. Moreover, the various steps in FIG. 7 may be performed in a different order than that presented in FIG. 7, and it is possible that not all operations in FIG. 7 are to be performed.
602，UE 110向协调器131发送服务请求。602. The UE 110 sends a service request to the coordinator 131.
该服务请求为图4中的业务请求消息的一种。当协调器接收到UE发送的服务请求之后，可以根据预先存储的对应于服务请求的业务流程对UE的服务请求进行处理。The service request is one of the service request messages in FIG. After the coordinator receives the service request sent by the UE, the service request of the UE may be processed according to a pre-stored service flow corresponding to the service request.
604，协调器131向RAN 120发送初始上下文建立请求。604, the coordinator 131 sends an initial context setup request to the RAN 120.
606，RAN 120向协调器131发送初始上下文建立完成应答。606. The RAN 120 sends an initial context setup complete response to the coordinator 131.
604和606步骤中，协调器和RAN侧节点交互，建立UE初始上下文。In steps 604 and 606, the coordinator interacts with the RAN side node to establish a UE initial context.
608，协调器131向PCC 170发送IP-CAN会话修改指示。608, the coordinator 131 sends an IP-CAN session modification indication to the PCC 170.
610，PCC170向协调器131发送IP-CAN会话修改应答。610. The PCC 170 sends an IP-CAN session modification response to the coordinator 131.
608和610步骤中，协调器131调用PCC170。具体的，协调器将UE相关信息发送给PCC模块，PCC模块重新计算UE的相关计费与QoS控制策略，并将相关内容返回给协调器，协调器更新UE上下文。In steps 608 and 610, the coordinator 131 calls the PCC 170. Specifically, the coordinator sends the UE related information to the PCC module, and the PCC module recalculates the related charging and QoS control policies of the UE, and returns related content to the coordinator, and the coordinator updates the UE context.
612，协调器131向SM 160发送修改承载请求。612. The coordinator 131 sends a modify bearer request to the SM 160.
614，SM 160与服务网关交互，配置修改数据路径。614. The SM 160 interacts with the service gateway to configure a modified data path.
616，SM160向协调器131发送修改承载响应。616. The SM 160 sends a modify bearer response to the coordinator 131.
612至616步骤中，协调器131调用SM160。协调器与SM管理模块交互，完成修改承载流程。In steps 612 to 616, the coordinator 131 calls the SM 160. The coordinator interacts with the SM management module to complete the modification of the bearer process.
本发明实施例中，核心网根据UE的服务请求，根据服务请求对应的业务流程，实现了UE的服务请求流程。协调器作为对外交互的接口，实现了RAN侧初始上下文的建立，外部信令的接收和发送以及NF(例如SM和PCC)的调用，并且对UE的状态和上下文数据进行了更新，从而完成了UE的服务请求过程。In the embodiment of the present invention, the core network implements the service request process of the UE according to the service request of the UE and according to the service flow corresponding to the service request. As an external interaction interface, the coordinator implements the establishment of the initial context of the RAN side, the reception and transmission of external signaling, and the invocation of NF (for example, SM and PCC), and updates the status and context data of the UE, thereby completing the UE's service request process.
图8为本发明另一个实施例的核心网中业务处理的方法的示意性流程 图。图8中的源RAN1201和目的RAN可以为上述图1中的接入网节点，源协调器1313和目的协调器1314可以为上述图2中的协调器，源SM1601为源协调器1313调用的NF，目的SM1602为目的协调器1314调用的NF。FIG. 8 is a schematic flowchart of a method for service processing in a core network according to another embodiment of the present invention; Figure. The source RAN 1201 and the destination RAN in FIG. 8 may be the access network node in FIG. 1 above, and the source coordinator 1313 and the destination coordinator 1314 may be the coordinator in FIG. 2 above, and the source SM 1601 is the NF invoked by the source coordinator 1313. The destination SM1602 is the NF called by the destination coordinator 1314.
应理解，图8示出了核心网中业务处理的方法的步骤或操作，但这些步骤或操作仅是示例，本发明实施例还可以执行其他操作或者图8中的各个操作的变形。此外，图8中的各个步骤可以按照与图8呈现的不同的顺序来执行，并且有可能并非要执行图8中的全部操作。It should be understood that FIG. 8 illustrates steps or operations of the method of service processing in the core network, but these steps or operations are merely examples, and embodiments of the present invention may perform other operations or variations of the operations in FIG. Moreover, the various steps in FIG. 8 may be performed in a different order than that presented in FIG. 8, and it is possible that not all operations in FIG. 8 are to be performed.
702，源RAN1201向源协调器1313发送切换请求。702. The source RAN 1201 sends a handover request to the source coordinator 1313.
该切换请求为图4中的业务请求消息的一种。当第一协调器接收到UE发送的切换请求之后，可以根据预先存储的对应于切换请求的业务流程对UE的切换请求进行处理。The handover request is one of the service request messages in FIG. After receiving the handover request sent by the UE, the first coordinator may process the handover request of the UE according to the pre-stored service flow corresponding to the handover request.
704，源协调器1313向源SM 1601发送目的协调器选择请求。704. The source coordinator 1313 sends a destination coordinator selection request to the source SM 1601.
706，源SM 1601计算并选择目的协调器。706. The source SM 1601 calculates and selects a destination coordinator.
708，源SM 1601向源协调器1313发送目的协调器选择响应。708. The source SM 1601 sends a destination coordinator selection response to the source coordinator 1313.
704至708步骤中，源协调器1313调用源SM 1601。具体的，源协调器请求源SM模块，以计算并选择目的协调器，例如根据UE的位置信息选择目的协调器。In steps 704 through 708, source coordinator 1313 invokes source SM 1601. Specifically, the source coordinator requests the source SM module to calculate and select a destination coordinator, for example, selecting a destination coordinator according to the location information of the UE.
710，源协调器1313向目的协调器1314发送重定位请求。710. The source coordinator 1313 sends a relocation request to the destination coordinator 1314.
712，目的协调器1314向目的SM 1602发送会话管理请求。712. The destination coordinator 1314 sends a session management request to the destination SM 1602.
714，目的SM 1602进行会话管理计算。714. The destination SM 1602 performs session management calculation.
716，目的SM 1602向目的协调器1314发送会话管理响应。716. The destination SM 1602 sends a session management response to the destination coordinator 1314.
712至716步骤中，目的协调器1314调用目标SM 1602。具体的，目的协调器将UE相关信息发送给目的SM模块，目的SM管理模块进行相应计算，包括诸如是否重新选择服务网关等操作，将计算结果返回给目的协调器，目的协调器更新UE上下文。In the steps 712 to 716, the destination coordinator 1314 invokes the target SM 1602. Specifically, the destination coordinator sends the UE related information to the destination SM module, and the destination SM management module performs corresponding calculations, including operations such as reselecting the serving gateway, and returns the calculation result to the destination coordinator, and the destination coordinator updates the UE context.
718，目的协调器1314向目的SM 1602发送创建会话请求。718, the destination coordinator 1314 sends a create session request to the destination SM 1602.
720，目的SM1602与服务网关交互，配置建立数据路径。720. The destination SM1602 interacts with the service gateway to configure a data path.
722，目的SM1602向目的协调器1314发送创建会话响应。722. The destination SM 1602 sends a create session response to the destination coordinator 1314.
718至722中，目的协调器1314调用目的SM 1602。具体的，目的协调器根据计算结果，与目的SM管理模块交互，完成创建会话流程。In 718 to 722, the destination coordinator 1314 invokes the destination SM 1602. Specifically, the destination coordinator interacts with the destination SM management module according to the calculation result to complete the session creation process.
724，目的协调器1314向目的RAN1202发送切换请求。 724. The destination coordinator 1314 sends a handover request to the destination RAN 1202.
726，目的RAN 1202向目的协调器1314发送切换应答。726. The destination RAN 1202 sends a handover response to the destination coordinator 1314.
728，目的协调器1314向目的SM1602发送间接转发隧道建立请求。728. The destination coordinator 1314 sends an indirect forwarding tunnel establishment request to the destination SM1602.
730，目的SM1602向目的协调器1314发送间接转发隧道响应。730. The destination SM 1602 sends an indirect forwarding tunnel response to the destination coordinator 1314.
728和730步骤中，目的协调器1314再次调用目的SM 1602。目的协调器与目的SM管理模块交互，完成目的侧间接转发隧道建立流程。In steps 728 and 730, the destination coordinator 1314 invokes the destination SM 1602 again. The destination coordinator interacts with the destination SM management module to complete the establishment process of the destination side indirect forwarding tunnel.
732，目的协调器1314向源协调器1313发送重定位响应。732, the destination coordinator 1314 sends a relocation response to the source coordinator 1313.
734，源协调器1313向源SM1601发送间接转发隧道建立请求。734. The source coordinator 1313 sends an indirect forwarding tunnel establishment request to the source SM1601.
736，源SM1601向源协调器1313发送间接转发隧道响应。736. The source SM1601 sends an indirect forwarding tunnel response to the source coordinator 1313.
734和736步骤中，源协调器1313再次调用源SM 1601。源协调器与源SM管理模块交互，完成源侧间接转发隧道建立流程In steps 734 and 736, the source coordinator 1313 calls the source SM 1601 again. The source coordinator interacts with the source SM management module to complete the source side indirect forwarding tunnel establishment process.
738，源协调器1313向UE发送切换命令。738. The source coordinator 1313 sends a handover command to the UE.
740，源RAN节点或源协调器，与目的RAN或目的协调器交互，完成接入上下文/协调器状态的传输，同时UE切换到目的RAN。740. The source RAN node or the source coordinator interacts with the destination RAN or the destination coordinator to complete transmission of the access context/coordinator state, and the UE switches to the destination RAN.
本发明实施例中，当两个协调器分别位于两个数据中心，并且UE发生跨数据中心的切换时，两个协调器可以进行交互，实现UE的状态和上下文数据的传输。In the embodiment of the present invention, when two coordinators are respectively located in two data centers, and the UE performs handover across the data center, the two coordinators can interact to implement the state of the UE and the transmission of the context data.
742，UE110向目的RAN 1202发送切换确认。742. The UE 110 sends a handover confirmation to the destination RAN 1202.
744，目的RAN1202向目的协调器1314发送切换通知。744. The destination RAN 1202 sends a handover notification to the destination coordinator 1314.
746，目的协调器1314向源协调器1313发送重定位完成通知。746. The destination coordinator 1314 sends a relocation complete notification to the source coordinator 1313.
748，源协调器1313向目的协调器1314发送重定位完成应答。748. The source coordinator 1313 sends a relocation complete response to the destination coordinator 1314.
750，目的协调器1314向目的SM1602发送修改承载请求。750. The destination coordinator 1314 sends a modify bearer request to the destination SM 1602.
752，目的SM1602与服务网关交互，配置修改数据路径。752. The destination SM1602 interacts with the service gateway to configure a modified data path.
754，目的SM1602向目的协调器1314发送修改承载响应。754. The destination SM 1602 sends a modify bearer response to the destination coordinator 1314.
750至754步骤中，目的协调器1314再次调用目的SM 1602。目的协调器与SM管理模块交互，完成修改承载流程。In steps 750 to 754, the destination coordinator 1314 invokes the destination SM 1602 again. The destination coordinator interacts with the SM management module to complete the modification of the bearer process.
756，进行TAU以及其他handover操作，例如删除源会话即拆除间接转发隧道灯，完成handover流程。756, performing TAU and other handover operations, for example, deleting the source session, removing the indirect forwarding tunnel light, and completing the handover process.
本发明实施例中，核心网根据UE的切换请求，根据切换请求对应的业务流程，实现了UE的切换流程。源协调器和目的协调器作为对外交互的接口，实现了源协调器与目的协调器之间的交互，UE的状态和上下文数据的传输，实现外部信令的接收和发送以及NF(例如MM、SM和PCC)的调 用，并且对UE的状态和上下文数据进行了更新，从而完成了UE的切换过程。In the embodiment of the present invention, the core network implements the handover process of the UE according to the handover request of the UE according to the service flow corresponding to the handover request. The source coordinator and the destination coordinator act as interfaces for external interaction, implement interaction between the source coordinator and the destination coordinator, transmit UE status and context data, implement external signaling reception and transmission, and NF (eg, MM, SM and PCC) And the status and context data of the UE are updated, thereby completing the handover process of the UE.
图9为本发明实施例的网络设备的一个示意性框图。图9所示的网络设备400应用于核心网中，该网络设备400可以为上述协调器，或具有上述协调器的各个功能模块的设备。核心网中还包括网络功能NF，所述网络设备400包括：FIG. 9 is a schematic block diagram of a network device according to an embodiment of the present invention. The network device 400 shown in FIG. 9 is applied to a core network, and the network device 400 may be the above-described coordinator or a device having various functional modules of the above-described coordinator. The network function NF is also included in the core network, and the network device 400 includes:
接收单元410，用于接收第一网元发送的请求消息，所述请求消息用于请求对UE的业务进行处理；The receiving unit 410 is configured to receive a request message sent by the first network element, where the request message is used to request processing of the service of the UE;
处理单元420，用于根据所述请求消息和所述请求消息对应的业务流程，对所述业务进行处理，所述业务流程用于调用处理所述业务所需要使用的至少一个NF。The processing unit 420 is configured to process the service according to the request message and the service flow corresponding to the request message, where the service process is used to invoke at least one NF required to process the service.
本发明实施例能够根据请求消息对应的业务流程调用核心网中的网络功能，对UE的业务进行处理，该网络功能包括核心网中虚拟化的网元功能。本发明实施例将业务部署转化为软件部署，能够针对不同的业务场景选择和调用不同的网络功能，实现按需弹性组网，使得网络具有灵活的可扩展性、开放性和演进能力。The embodiment of the present invention can process the service of the UE according to the network function in the core network according to the service flow corresponding to the request message, and the network function includes the function of the virtualized network element in the core network. The embodiment of the present invention converts the service deployment into a software deployment, and can select and invoke different network functions for different service scenarios to implement an on-demand elastic networking, so that the network has flexible scalability, openness, and evolution capability.
可选的，所述至少一个NF包括至少两个NF，所述业务流程用于按照逻辑顺序调用所述至少两个NF。Optionally, the at least one NF includes at least two NFs, and the business process is used to invoke the at least two NFs in a logical order.
可选的，所述处理单元420具体用于：Optionally, the processing unit 420 is specifically configured to:
根据所述请求消息和所述业务流程，生成所述至少一个NF中的每个NF的输入消息；Generating an input message for each NF of the at least one NF according to the request message and the service flow;
根据所述每个NF的输入消息，对所述业务进行处理。The service is processed according to the input message of each NF.
可选的，所述处理单元420具体用于：Optionally, the processing unit 420 is specifically configured to:
获取所述每个NF的输出消息，所述每个NF的输出消息是所述每个NF根据所述每个NF的输入消息生成的；Obtaining an output message of each NF, the output message of each NF is generated by each NF according to an input message of each NF;
根据所述每个NF的输出消息，确定对所述业务的处理结果。The processing result for the service is determined according to the output message of each NF.
可选的，所述处理单元420具体还用于：Optionally, the processing unit 420 is further configured to:
根据所述每个NF的输出消息，更新所述UE的上下文。Updating the context of the UE according to the output message of each NF.
可选的，其特征在于，所述网络设备400还包括：Optionally, the network device 400 further includes:
获取单元，用于根据所述请求消息，获取第二网元发送的所述UE的数据信息，所述数据信息包括创建所述UE的上下文所需的信息； An acquiring unit, configured to acquire, according to the request message, data information of the UE sent by a second network element, where the data information includes information required to create a context of the UE;
建立单元，用于根据所述UE的数据信息，创建所述UE的上下文；a establishing unit, configured to create a context of the UE according to the data information of the UE;
其中，所述处理单元420具体用于：The processing unit 420 is specifically configured to:
所述第一协调器根据所述UE的上下文和所述业务流程，生成所述至少一个NF中的每个NF的输入消息。The first coordinator generates an input message for each NF of the at least one NF according to the context of the UE and the service flow.
可选的，所述第二网元包括用户签约信息存储单元、无线接入网RAN节点或第一网络设备，所述第一网络设备设置于所述核心网中。这里，该第一网络设备可以为与该网络设备400具有相同功能模块的网络设备。Optionally, the second network element includes a user subscription information storage unit, a radio access network RAN node, or a first network device, where the first network device is disposed in the core network. Here, the first network device may be a network device having the same functional module as the network device 400.
可选的，所述核心网还包括协调器管理器，所述接收单元还用于接收所述协调器管理器发送的所述业务流程。Optionally, the core network further includes a coordinator manager, where the receiving unit is further configured to receive the service process sent by the coordinator manager.
可选的，所述网络设备还包括发送单元，用于根据对所述业务的处理结果，向所述第一网元发送返回消息。Optionally, the network device further includes a sending unit, configured to send a return message to the first network element according to the processing result of the service.
应注意，本发明实施例中，接收单元410可以由收发器实现，处理单元420可以由处理器实现。如图10所示，网络设备500可以包括处理器510、存储器520、收发器530和总线***540。其中，存储器520可以用于存储处理器510执行的代码等。It should be noted that, in the embodiment of the present invention, the receiving unit 410 may be implemented by a transceiver, and the processing unit 420 may be implemented by a processor. As shown in FIG. 10, network device 500 can include a processor 510, a memory 520, a transceiver 530, and a bus system 540. The memory 520 can be used to store code and the like executed by the processor 510.
网络设备500中的各个组件通过总线***540耦合在一起，其中总线***540除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图中将各种总线都标为总线***540。The various components in network device 500 are coupled together by a bus system 540, which in addition to the data bus includes a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 540 in the figure.
在实现过程中，上述方法的各步骤可以通过处理器410中的硬件的集成逻辑电路或者软件形式的指令完成。结合本发明实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器520，处理器510读取存储器520中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 410 or an instruction in a form of software. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 520, and the processor 510 reads the information in the memory 520 and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
图9所示的网络设备400或图10所示的网络设备500能够实现前述图3至图8所示的方法实施例对应的各个过程，具体的，该网络设备400或网络设备500可以参见上述图3至图8中的描述，为避免重复，这里不再赘述。The network device 400 shown in FIG. 9 or the network device 500 shown in FIG. 10 can implement the processes corresponding to the foregoing method embodiments shown in FIG. 3 to FIG. 8. Specifically, the network device 400 or the network device 500 can refer to the foregoing. The descriptions in FIGS. 3 to 8 are not repeated here to avoid repetition.
图11为本发明实施例的网络设备的一个示意性框图。图10所示的网络设备600应用于核心网中，该网络设备600可以为上述协调器管理器，或者具有上述协调器管理器的各个功能模块的设备。核心网还包括网络功能NF 和协调器，该网络设备600包括：FIG. 11 is a schematic block diagram of a network device according to an embodiment of the present invention. The network device 600 shown in FIG. 10 is applied to a core network, and the network device 600 may be the above-described coordinator manager or a device having various functional modules of the coordinator manager described above. The core network also includes the network function NF And the coordinator, the network device 600 includes:
确定单元610，用于确定处理所述业务的流程，所述流程用于指示处理所述业务所需要使用的至少一个网络功能NF；a determining unit 610, configured to determine a process for processing the service, where the process is used to indicate at least one network function NF required to process the service;
所述确定单元610还用于根据所述流程确定所述至少一个NF的信息；The determining unit 610 is further configured to determine information about the at least one NF according to the process;
生成单元620，用于根据所述流程和所述至少一个NF的信息，生成处理所述业务的业务流程，所述业务流程用于调用处理所述业务所需要使用的至少一个NF；The generating unit 620 is configured to generate, according to the process and the information of the at least one NF, a service process for processing the service, where the service process is used to invoke at least one NF required to process the service;
发送单元630，用于向所述协调器发送所述业务流程，使得所述协调器根据所述业务流程，对所述业务进行处理。The sending unit 630 is configured to send the service flow to the coordinator, so that the coordinator processes the service according to the service process.
本发明实施例能够根据业务流程调用核心网中的网络功能，对UE的业务进行处理，将业务部署转化为软件部署，能够针对不同的业务场景选择和调用不同的网络功能，实现按需弹性组网，使得网络具有灵活的可扩展性、开放性和演进能力。The embodiment of the present invention can call the network function in the core network according to the service process, process the service of the UE, convert the service deployment into a software deployment, and select and invoke different network functions for different service scenarios to implement the on-demand elastic group. The network enables the network to be flexible, scalable, and evolving.
可选的，所述至少一个NF包括至少两个NF，所述流程还用于指示所需要使用的所述至少两个NF的逻辑顺序，所述业务流程用于按照所述逻辑顺序调用所述至少两个NF。Optionally, the at least one NF includes at least two NFs, and the process is further used to indicate a logical sequence of the at least two NFs that are required to be used, where the service flow is used to invoke the according to the logical sequence. At least two NFs.
可选的，所述核心网还包括NF管理器，所述确定单元610具体用于：Optionally, the core network further includes an NF manager, and the determining unit 610 is specifically configured to:
在所述至少一个NF中确定需要创建的NF；Determining an NF to be created in the at least one NF;
向所述NF管理器发送所述需要创建的NF的类型，以使得所述NF管理器根据所述NF的类型创建所述需要创建的NF；Sending, to the NF manager, the type of the NF that needs to be created, so that the NF manager creates the NF that needs to be created according to the type of the NF;
接收所述NF管理器发送的所述NF管理器创建的NF的信息。Receiving information of the NF created by the NF manager sent by the NF manager.
可选的，所述NF的信息包括所述NF的接口参数和所述NF的地址。Optionally, the information about the NF includes an interface parameter of the NF and an address of the NF.
应注意，本发明实施例中，确定单元610和生成单元420可以由处理器实现，发送单元630可以由收发器实现。如图12所示，网络设备700可以包括处理器710、存储器720、收发器730和总线***740。其中，存储器720可以用于存储处理器710执行的代码等。It should be noted that in the embodiment of the present invention, the determining unit 610 and the generating unit 420 may be implemented by a processor, and the sending unit 630 may be implemented by a transceiver. As shown in FIG. 12, network device 700 can include a processor 710, a memory 720, a transceiver 730, and a bus system 740. The memory 720 can be used to store code and the like executed by the processor 710.
网络设备700中的各个组件通过总线***740耦合在一起，其中总线***740除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图中将各种总线都标为总线***740。The various components in network device 700 are coupled together by a bus system 740, which in addition to the data bus includes a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 740 in the figure.
在实现过程中，上述方法的各步骤可以通过处理器710中的硬件的集成逻辑电路或者软件形式的指令完成。结合本发明实施例所公开的方法的步骤 可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器720，处理器710读取存储器720中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 710 or an instruction in a form of software. The steps of the method disclosed in connection with the embodiments of the present invention It can be directly implemented as a hardware processor or completed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in memory 720, and processor 710 reads the information in memory 720 and, in conjunction with its hardware, performs the steps of the above method. To avoid repetition, it will not be described in detail here.
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。It should be understood that the term "and/or" herein is merely an association relationship describing an associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and A and B exist simultaneously. There are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.
应理解，在本发明的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention. The implementation process constitutes any limitation.
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, 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. In addition, 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.
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。In addition, 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.
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used 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. .
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应所述以权利要求的保护范围为准。 The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims (26)

  1. 一种核心网中业务处理的方法，其特征在于，所述核心网包括第一协调器和至少一个网络功能NF，所述方法包括：A method for service processing in a core network, characterized in that the core network comprises a first coordinator and at least one network function NF, the method comprising:
    所述第一协调器接收第一网元发送的请求消息，所述请求消息用于请求对UE的业务进行处理；The first coordinator receives a request message sent by the first network element, where the request message is used to request processing of the service of the UE;
    所述第一协调器根据所述请求消息和所述请求消息对应的业务流程，对所述业务进行处理，所述业务流程用于调用处理所述业务所需要使用的所述至少一个NF。The first coordinator processes the service according to the request message and the service flow corresponding to the request message, where the service process is used to invoke the at least one NF that is required to process the service.
  2. 根据权利要求1所述的方法，其特征在于，所述至少一个NF包括至少两个NF，所述业务流程用于按照逻辑顺序调用所述至少两个NF。The method of claim 1 wherein said at least one NF comprises at least two NFs, said business process for calling said at least two NFs in a logical order.
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一协调器根据所述请求消息和所述请求消息对应的业务流程，对所述业务进行处理，包括：The method according to claim 1 or 2, wherein the first coordinator processes the service according to the request message and the service flow corresponding to the request message, including:
    所述第一协调器根据所述请求消息和所述业务流程，生成所述至少一个NF中的每个NF的输入消息；The first coordinator generates an input message of each NF of the at least one NF according to the request message and the service flow;
    所述第一协调器根据所述每个NF的输入消息，对所述业务进行处理。The first coordinator processes the service according to the input message of each NF.
  4. 根据权利要求3所述的方法，其特征在于，所述第一协调器根据所述每个NF的输入消息，对所述业务进行处理，包括：The method according to claim 3, wherein the first coordinator processes the service according to the input message of each NF, including:
    所述第一协调器获取所述每个NF的输出消息，所述每个NF的输出消息是所述每个NF根据所述每个NF的输入消息生成的；The first coordinator acquires an output message of each NF, and the output message of each NF is generated by each NF according to an input message of each NF;
    所述第一协调器根据所述每个NF的输出消息，确定对所述业务的处理结果。The first coordinator determines a processing result for the service according to the output message of each NF.
  5. 根据权利要求4所述的方法，其特征在于，所述第一协调器获取所述每个NF的输出消息之后，还包括：The method according to claim 4, wherein after the first coordinator obtains the output message of each NF, the method further includes:
    所述第一协调器根据所述每个NF的输出消息，更新所述UE的上下文。The first coordinator updates the context of the UE according to the output message of each NF.
  6. 根据权利要求3-5任一项所述的方法，其特征在于，所述第一协调器根据所述请求消息和所述业务流程，生成所述至少一个NF中的每个NF的输入消息之前，还包括：The method according to any one of claims 3-5, wherein the first coordinator generates an input message for each NF of the at least one NF according to the request message and the service flow. ,Also includes:
    所述第一协调器根据所述请求消息，获取第二网元发送的所述UE的数据信息，所述数据信息包括创建所述UE的上下文所需的信息；Obtaining, by the first coordinator, the data information of the UE that is sent by the second network element according to the request message, where the data information includes information required to create a context of the UE;
    所述第一协调器根据所述UE的数据信息，创建所述UE的上下文； The first coordinator creates a context of the UE according to the data information of the UE;
    其中，所述第一协调器根据所述请求消息和所述业务流程，生成所述至少一个NF中的每个NF的输入消息，包括：The first coordinator generates an input message of each NF in the at least one NF according to the request message and the service flow, including:
    所述第一协调器根据所述UE的上下文和所述业务流程，生成所述至少一个NF中的每个NF的输入消息。The first coordinator generates an input message for each NF of the at least one NF according to the context of the UE and the service flow.
  7. 根据权利要求6所述的方法，其特征在于，所述第二网元包括用户签约信息存储单元、无线接入网RAN节点或第二协调器，所述第二协调器设置于所述核心网中。The method according to claim 6, wherein the second network element comprises a user subscription information storage unit, a radio access network RAN node or a second coordinator, and the second coordinator is disposed on the core network. in.
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述核心网还包括协调器管理器，所述方法还包括：The method according to any one of claims 1 to 7, wherein the core network further comprises a coordinator manager, the method further comprising:
    所述第一协调器接收所述协调器管理器发送的所述业务流程。The first coordinator receives the service flow sent by the coordinator manager.
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述方法还包括：The method of any of claims 1-8, wherein the method further comprises:
    所述第一协调器根据对所述业务的处理结果，向所述第一网元发送返回消息。The first coordinator sends a return message to the first network element according to the processing result of the service.
  10. 一种核心网中业务处理的方法，其特征在于，所述核心网包括协调器管理器、网络功能NF和协调器，所述方法包括：A method for processing a service in a core network, the core network comprising a coordinator manager, a network function NF, and a coordinator, the method comprising:
    所述协调器管理器确定处理所述业务的流程，所述流程用于指示处理所述业务所需要使用的至少一个网络功能NF；The coordinator manager determines a process for processing the service, the process being used to indicate at least one network function NF required to process the service;
    所述协调器管理器根据所述流程确定所述至少一个NF的信息；Determining, by the coordinator manager, information of the at least one NF according to the process;
    所述协调器管理器根据所述流程和所述至少一个NF的信息，生成处理所述业务的业务流程，所述业务流程用于调用处理所述业务所需要使用的至少一个NF；The coordinator manager generates, according to the process and the information of the at least one NF, a service process for processing the service, where the service process is used to invoke at least one NF required to process the service;
    所述协调器管理器向所述协调器发送所述业务流程，使得所述协调器根据所述业务流程，对所述业务进行处理。The coordinator manager sends the business process to the coordinator, so that the coordinator processes the service according to the business process.
  11. 根据权利要求10所述的方法，其特征在于，所述至少一个NF包括至少两个NF，所述流程还用于指示所需要使用的所述至少两个NF的逻辑顺序，所述业务流程用于按照所述逻辑顺序调用所述至少两个NF。The method according to claim 10, wherein said at least one NF comprises at least two NFs, and said flow is further for indicating a logical sequence of said at least two NFs to be used, said business process The at least two NFs are invoked in the logical order.
  12. 根据权利要求10或11所述的方法，其特征在于，所述核心网还包括NF管理器，所述协调器管理器根据所述流程确定所述至少一个NF的信息，包括：The method according to claim 10 or 11, wherein the core network further comprises an NF manager, and the coordinator manager determines the information of the at least one NF according to the process, including:
    所述协调器管理器在所述至少一个NF中确定需要创建的NF； The coordinator manager determines, in the at least one NF, an NF that needs to be created;
    所述协调器管理器向所述NF管理器发送所述需要创建的NF的类型，以使得所述NF管理器根据所述NF的类型创建所述需要创建的NF；The coordinator manager sends the type of the NF that needs to be created to the NF manager, so that the NF manager creates the NF that needs to be created according to the type of the NF;
    所述协调器管理器接收所述NF管理器发送的所述NF管理器创建的NF的信息。The coordinator manager receives information of the NF created by the NF manager sent by the NF manager.
  13. 根据权利要求10-12任一项所述的方法，其特征在于，所述NF的信息包括所述NF的接口参数和所述NF的地址。The method according to any one of claims 10 to 12, wherein the information of the NF comprises an interface parameter of the NF and an address of the NF.
  14. 一种网络设备，其特征在于，所述网络设备应用于核心网中，所述核心网包括网络功能NF，所述网络设备包括：A network device, wherein the network device is applied to a core network, where the core network includes a network function NF, and the network device includes:
    接收单元，用于接收第一网元发送的请求消息，所述请求消息用于请求对UE的业务进行处理；a receiving unit, configured to receive a request message sent by the first network element, where the request message is used to request processing of a service of the UE;
    处理单元，用于根据所述请求消息和所述请求消息对应的业务流程，对所述业务进行处理，所述业务流程用于调用处理所述业务所需要使用的至少一个NF。The processing unit is configured to process the service according to the request message and the service flow corresponding to the request message, where the service process is used to invoke at least one NF required to process the service.
  15. 根据权利要求14所述的网络设备，其特征在于，所述至少一个NF包括至少两个NF，所述业务流程用于按照逻辑顺序调用所述至少两个NF。The network device of claim 14, wherein the at least one NF comprises at least two NFs, the business process for calling the at least two NFs in a logical order.
  16. 根据权利要求14或15所述的网络设备，其特征在于，所述处理单元具体用于：The network device according to claim 14 or 15, wherein the processing unit is specifically configured to:
    根据所述请求消息和所述业务流程，生成所述至少一个NF中的每个NF的输入消息；Generating an input message for each NF of the at least one NF according to the request message and the service flow;
    根据所述每个NF的输入消息，对所述业务进行处理。The service is processed according to the input message of each NF.
  17. 根据权利要求16所述的网络设备，其特征在于，所述处理单元具体用于：The network device according to claim 16, wherein the processing unit is specifically configured to:
    获取所述每个NF的输出消息，所述每个NF的输出消息是所述每个NF根据所述每个NF的输入消息生成的；Obtaining an output message of each NF, the output message of each NF is generated by each NF according to an input message of each NF;
    根据所述每个NF的输出消息，确定对所述业务的处理结果。The processing result for the service is determined according to the output message of each NF.
  18. 根据权利要求17所述的网络设备，其特征在于，所述处理单元具体还用于：The network device according to claim 17, wherein the processing unit is further configured to:
    根据所述每个NF的输出消息，更新所述UE的上下文。Updating the context of the UE according to the output message of each NF.
  19. 根据权利要求16-18任一项所述的网络设备，其特征在于，所述网络设备还包括：The network device according to any one of claims 16 to 18, wherein the network device further comprises:
    获取单元，用于根据所述请求消息，获取第二网元发送的所述UE的数 据信息，所述数据信息包括创建所述UE的上下文所需的信息；An acquiring unit, configured to acquire, according to the request message, the number of the UEs sent by the second network element According to the information, the data information includes information required to create a context of the UE;
    建立单元，用于根据所述UE的数据信息，创建所述UE的上下文；a establishing unit, configured to create a context of the UE according to the data information of the UE;
    其中，所述处理单元具体用于：The processing unit is specifically configured to:
    所述第一协调器根据所述UE的上下文和所述业务流程，生成所述至少一个NF中的每个NF的输入消息。The first coordinator generates an input message for each NF of the at least one NF according to the context of the UE and the service flow.
  20. 根据权利要求19所述的网络设备，其特征在于，所述第二网元包括用户签约信息存储单元、无线接入网RAN节点或第一网络设备，所述第一网络设备设置于所述核心网中。The network device according to claim 19, wherein the second network element comprises a user subscription information storage unit, a radio access network RAN node or a first network device, and the first network device is disposed in the core In the net.
  21. 根据权利要求14-20任一项所述的网络设备，其特征在于，所述核心网还包括协调器管理器，The network device according to any one of claims 14 to 20, wherein the core network further comprises a coordinator manager,
    所述接收单元还用于接收所述协调器管理器发送的所述业务流程。The receiving unit is further configured to receive the service flow sent by the coordinator manager.
  22. 根据权利要求14-21任一项所述的网络设备，其特征在于，所述网络设备还包括发送单元，用于根据对所述业务的处理结果，向所述第一网元发送返回消息。The network device according to any one of claims 14 to 21, wherein the network device further comprises a sending unit, configured to send a return message to the first network element according to a processing result of the service.
  23. 一种网络设备，其特征在于，所述网络设备应用于核心网中，所述核心网包括网络功能NF和协调器，所述网络设备包括：A network device, wherein the network device is applied to a core network, where the core network includes a network function NF and a coordinator, and the network device includes:
    确定单元，用于确定处理所述业务的流程，所述流程用于指示处理所述业务所需要使用的至少一个网络功能NF；a determining unit, configured to determine a process for processing the service, where the process is used to indicate at least one network function NF required to process the service;
    所述确定单元还用于根据所述流程确定所述至少一个NF的信息；The determining unit is further configured to determine information of the at least one NF according to the process;
    生成单元，用于根据所述流程和所述至少一个NF的信息，生成处理所述业务的业务流程，所述业务流程用于调用处理所述业务所需要使用的至少一个NF；a generating unit, configured to generate, according to the process and the information of the at least one NF, a service process for processing the service, where the service process is used to invoke at least one NF required to process the service;
    发送单元，用于向所述协调器发送所述业务流程，使得所述协调器根据所述业务流程，对所述业务进行处理。And a sending unit, configured to send the service process to the coordinator, so that the coordinator processes the service according to the service process.
  24. 根据权利要求23所述的网络设备，其特征在于，所述至少一个NF包括至少两个NF，所述流程还用于指示所需要使用的所述至少两个NF的逻辑顺序，所述业务流程用于按照所述逻辑顺序调用所述至少两个NF。The network device according to claim 23, wherein said at least one NF comprises at least two NFs, and said flow is further for indicating a logical sequence of said at least two NFs to be used, said business process The at least two NFs are invoked in the logical order.
  25. 根据权利要求23或24所述的网络设备，其特征在于，所述核心网还包括NF管理器，所述确定单元具体用于：The network device according to claim 23 or 24, wherein the core network further includes an NF manager, and the determining unit is specifically configured to:
    在所述至少一个NF中确定需要创建的NF；Determining an NF to be created in the at least one NF;
    向所述NF管理器发送所述需要创建的NF的类型，以使得所述NF管 理器根据所述NF的类型创建所述需要创建的NF；Transmitting, to the NF manager, the type of the NF that needs to be created, so that the NF tube The processor creates the NF that needs to be created according to the type of the NF;
    接收所述NF管理器发送的所述NF管理器创建的NF的信息。Receiving information of the NF created by the NF manager sent by the NF manager.
  26. 根据权利要求23-25任一项所述的网络设备，其特征在于，所述NF的信息包括所述NF的接口参数和所述NF的地址。 The network device according to any one of claims 23-25, wherein the information of the NF comprises an interface parameter of the NF and an address of the NF.
PCT/CN2016/090406 2016-07-19 2016-07-19 Business processing method and network equipment in core network WO2018014172A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/090406 WO2018014172A1 (en) 2016-07-19 2016-07-19 Business processing method and network equipment in core network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/090406 WO2018014172A1 (en) 2016-07-19 2016-07-19 Business processing method and network equipment in core network

Publications (1)

Publication Number Publication Date
WO2018014172A1 true WO2018014172A1 (en) 2018-01-25

Family

ID=60991691

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/090406 WO2018014172A1 (en) 2016-07-19 2016-07-19 Business processing method and network equipment in core network

Country Status (1)

Country Link
WO (1) WO2018014172A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101895963A (en) * 2010-07-16 2010-11-24 华为技术有限公司 Method and device for network access of equipment in wireless sensor network
WO2014198310A1 (en) * 2013-06-12 2014-12-18 Nokia Solutions And Networks Oy Method of coordinating a communication network
CN104243301A (en) * 2013-06-08 2014-12-24 华为技术有限公司 Method, device and system for generating service path
CN105577499A (en) * 2014-10-10 2016-05-11 华为技术有限公司 Decision coordination method, execution device, and decision coordinator

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101895963A (en) * 2010-07-16 2010-11-24 华为技术有限公司 Method and device for network access of equipment in wireless sensor network
CN104243301A (en) * 2013-06-08 2014-12-24 华为技术有限公司 Method, device and system for generating service path
WO2014198310A1 (en) * 2013-06-12 2014-12-18 Nokia Solutions And Networks Oy Method of coordinating a communication network
CN105577499A (en) * 2014-10-10 2016-05-11 华为技术有限公司 Decision coordination method, execution device, and decision coordinator

Similar Documents

Publication Publication Date Title
US10873886B2 (en) Mobile edge platform switching method, apparatus, and system
CN110049070B (en) Event notification method and related equipment
US20230093339A1 (en) Session Management Method, Apparatus, and System
US11765686B2 (en) Packet transmission method and apparatus for communicating between terminals of a same 5G LAN group
KR102013232B1 (en) Gateway Configuration Methods and Gateway Devices
US20200383035A1 (en) Communications method and apparatus
WO2019196811A1 (en) Communication method and related apparatus
US11902389B2 (en) Mechanism to facilitate signaling traffic
US20210120620A1 (en) Communication Method and Apparatus
EP4024956A1 (en) Communication method, apparatus, and system
CN113906717B (en) Local user plane function control
CN110268751A (en) Method and system for selection access and mobile management function to ps domain in access net environment
WO2019134181A1 (en) Method and device for radio communication
US20200252839A1 (en) Method for returning after network handover, access network device and core network device
JP7135122B2 (en) Redirection method, communication system and communication device
WO2019024650A1 (en) Resource configuration method and device
WO2020001402A1 (en) Method and device for managing monitoring event
CN111567082A (en) Traffic steering between LTE and NR
CN109196893A (en) A kind of network connection configuration method and device
WO2019096306A1 (en) Request processing method, and corresponding entity
CN108235376B (en) User plane anchor point selection method and device
WO2021136287A1 (en) Communication method and apparatus
CN110140416A (en) Customer equipment context management method, device and equipment
WO2018127224A1 (en) Method and apparatus for establishing connection
WO2022057724A1 (en) Data offloading method and device

Legal Events

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

Ref document number: 16909103

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16909103

Country of ref document: EP

Kind code of ref document: A1