[go: up one dir, main page]

WO2018014172A1 - Procédé de traitement d'activité et dispositif de réseau dans un réseau central - Google Patents

Procédé de traitement d'activité et dispositif de réseau dans un réseau central 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
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2016/090406
Other languages
English (en)
Chinese (zh)
Inventor
乔晓强
李岩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2016/090406 priority Critical patent/WO2018014172A1/fr
Publication of WO2018014172A1 publication Critical patent/WO2018014172A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un mode de réalisation de la présente invention concerne un procédé de traitement d'activité et un dispositif de réseau dans un réseau central. Le réseau central comprend un premier coordinateur et au moins une fonction réseau (NF). Dans le procédé selon l'invention : le premier coordinateur reçoit un message de demande envoyé par un premier élément de réseau, le message de demande étant utilisé pour demander le traitement de l'activité d'un UE ; et le premier coordinateur traite l'activité d'après le message de demande et une procédure d'activité correspondant au message de demande, ladite procédure étant utilisée pour invoquer la ou les NF qui doivent être utilisées pour traiter l'activité. Selon le mode de réalisation de la présente invention, un déploiement d'activité est transformé en déploiement logiciel. Différentes NF peuvent ainsi être sélectionnées et invoquées pour différents scénarios d'activité, et un réseautage élastique à la demande peut être exécuté de sorte que le réseau présente une capacité d'expansion, d'ouverture et d'évolution flexible.
PCT/CN2016/090406 2016-07-19 2016-07-19 Procédé de traitement d'activité et dispositif de réseau dans un réseau central Ceased WO2018014172A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/090406 WO2018014172A1 (fr) 2016-07-19 2016-07-19 Procédé de traitement d'activité et dispositif de réseau dans un réseau central

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/090406 WO2018014172A1 (fr) 2016-07-19 2016-07-19 Procédé de traitement d'activité et dispositif de réseau dans un réseau central

Publications (1)

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

Family

ID=60991691

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/090406 Ceased WO2018014172A1 (fr) 2016-07-19 2016-07-19 Procédé de traitement d'activité et dispositif de réseau dans un réseau central

Country Status (1)

Country Link
WO (1) WO2018014172A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119815408A (zh) * 2024-12-23 2025-04-11 中移(苏州)软件技术有限公司 业务处理方法、装置、系统、设备、存储介质和程序产品

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101895963A (zh) * 2010-07-16 2010-11-24 华为技术有限公司 一种无线传感器网络中设备入网方法及装置
WO2014198310A1 (fr) * 2013-06-12 2014-12-18 Nokia Solutions And Networks Oy Procédé de coordination d'un réseau de communication
CN104243301A (zh) * 2013-06-08 2014-12-24 华为技术有限公司 一种生成业务路径的方法、设备及系统
CN105577499A (zh) * 2014-10-10 2016-05-11 华为技术有限公司 决策协调方法、执行装置和决策协调器

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101895963A (zh) * 2010-07-16 2010-11-24 华为技术有限公司 一种无线传感器网络中设备入网方法及装置
CN104243301A (zh) * 2013-06-08 2014-12-24 华为技术有限公司 一种生成业务路径的方法、设备及系统
WO2014198310A1 (fr) * 2013-06-12 2014-12-18 Nokia Solutions And Networks Oy Procédé de coordination d'un réseau de communication
CN105577499A (zh) * 2014-10-10 2016-05-11 华为技术有限公司 决策协调方法、执行装置和决策协调器

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119815408A (zh) * 2024-12-23 2025-04-11 中移(苏州)软件技术有限公司 业务处理方法、装置、系统、设备、存储介质和程序产品

Similar Documents

Publication Publication Date Title
US10873886B2 (en) Mobile edge platform switching method, apparatus, and system
US20220191765A1 (en) Communication method, apparatus, and system
CN110049070B (zh) 事件通知方法及相关设备
CN113507730B (zh) 会话管理的方法、装置、设备及系统
US12225615B2 (en) Signaling handovers of terminals between user plane function network elements
KR102013232B1 (ko) 게이트웨이 구성 방법 및 게이트웨이 디바이스
CN114450982A (zh) 促进信令业务的机制
WO2019071643A1 (fr) Procédé de retour après une commutation de réseau, dispositif de réseau d'accès et dispositif de réseau central
EP3949270A1 (fr) Commande de fonction de plan utilisateur locale
WO2019196811A1 (fr) Procédé de communication, et appareil associé
CN108738086A (zh) 一种用户面重选的方法及装置
WO2019134181A1 (fr) Procédé et dispositif de communication radio
CN115442792B (zh) 接入业务的方法、装置和系统
WO2019024650A1 (fr) Procédé et dispositif de configuration de ressource
CN114071649B (zh) 访问本地网络的方法和装置
CN109196893A (zh) 一种网络连接配置方法及装置
WO2023087965A1 (fr) Procédé et appareil de communication
US11974355B2 (en) Indication information sending method, apparatus and system, and storage medium
WO2022057724A1 (fr) Procédé et dispositif de délestage de données
WO2018188186A1 (fr) Procédé et dispositif de transfert intercellulaire
CN114449585A (zh) 应用接入网络的方法、装置及系统
CN104272860B (zh) 用于通信网络中的有效信令消息处理的方法和设备
EP4262244A1 (fr) Procédé et dispositif de détermination de point d'accès mec
WO2025026191A1 (fr) Procédé et appareil d'établissement de connexion de service ia, terminal et dispositif côté réseau
WO2021047443A1 (fr) Procédé et appareil de transfert de paquet de données de service

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