WO2017165999A1 - 网络服务实现方法、服务控制器及通信*** - Google Patents
网络服务实现方法、服务控制器及通信*** Download PDFInfo
- Publication number
- WO2017165999A1 WO2017165999A1 PCT/CN2016/077465 CN2016077465W WO2017165999A1 WO 2017165999 A1 WO2017165999 A1 WO 2017165999A1 CN 2016077465 W CN2016077465 W CN 2016077465W WO 2017165999 A1 WO2017165999 A1 WO 2017165999A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- instance
- target
- request message
- message
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5058—Service discovery by the service manager
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a network service implementation method, a service controller, and a communication system.
- network services may include mobility management, bearer management, location management, and the like.
- a plurality of network elements are disposed in the communication system, where the network element may include: a Mobility Management Entity (MME), a Serving Gateway (S-GW), and a packet. Data Network Gateway (P-GW), etc.
- MME Mobility Management Entity
- S-GW Serving Gateway
- P-GW Data Network Gateway
- the processing logic of multiple network elements is generally required according to the characteristics of the network service to be implemented.
- the interaction process between the network elements is set, and the multiple network elements jointly implement a network service.
- the user sends a corresponding service request message to the network side of the communication system.
- the network side determines the multiple network elements corresponding to the service request message.
- the service request message is delivered between the plurality of network elements, and the service request message is processed by the plurality of network elements in sequence to complete the network service requested by the user.
- Embodiments of the present invention provide a network service implementation method, a service controller, and a communication system, which are used to improve the efficiency of providing network services.
- an embodiment of the present invention provides a network service implementation method.
- the execution body of the method is a service controller, wherein the method includes: the service controller receives the service including the message identifier Requesting a message, and determining, according to the received service request message, a target service component corresponding to the message identifier in the service request message, since each service component includes at least one service instance, after the service controller determines that the target service component is obtained, the service control
- the target service instance is determined in at least one service instance of the target service component, and a service request message is sent to the target service instance to cause the target service instance to process the service request message.
- a service instance can provide a network service to the user, and does not require cooperation between multiple network elements to provide a service to the user, which reduces the number of message interactions and shortens the network service provided to the user. Time, which in turn increases the efficiency of the communication system providing network services to users.
- the service controller may determine the target in at least one service instance of the service component by the following feasible implementation manner.
- Service instance specific:
- a feasible implementation manner the service controller determines any one of the at least one service instance as the target service instance; in the feasible implementation manner, randomly determining a service instance as the target service in the at least one service instance An instance can improve the speed at which the service controller determines the target service instance.
- Another feasible implementation manner is: the service controller obtains the idle rate of each service instance in the at least one service instance, and determines the service instance with the largest idle rate as the target service instance; in the feasible implementation manner, the idle rate is adopted.
- the largest service instance is determined to be the target service instance, and the resources of each service instance can be utilized more effectively.
- the service request message may further include a terminal identifier, and after the service controller sends the service request message to the target service instance, the service controller may further determine and store the terminal identifier, the target service component, and the target service instance. The first correspondence between them.
- the process message is a message sent by the user after sending the trigger message for acquiring the network service
- the service request message further includes the terminal identifier
- the service The controller may determine the target service instance in the at least one service instance of the service component by using a feasible implementation manner. Specifically, the service controller acquires a second correspondence between the terminal identifier, the service component, and the service instance; the service controller is configured according to The second correspondence, the terminal identifier in the service request message, and the target service component determine the target service instance.
- the service controller may further determine whether the network service is over; if the judgment result is yes, the service In the second correspondence, the controller clears the correspondence between the terminal identifier, the target service component, and the target service instance in the service request message.
- the service controller may send a service request message to the target service instance by using a feasible implementation manner, where the service controller obtains the network address of the target service instance, and according to the network address, the target The service instance sends a service request message.
- the network address may include at least one of an Internet Protocol (IP) address, a Media Access Control (MAC) address, and a port number.
- IP Internet Protocol
- MAC Media Access Control
- an embodiment of the present invention provides a service controller, where the service controller may include a receiving module, a determining module, and a sending module, where the receiving module is configured to receive a service request message, where the service request message includes a message identifier; The module is configured to determine, according to the service request message, a target service component corresponding to the message identifier, and determine a target service instance in the at least one service instance of the target service component; the sending module is configured to send a service request message to the target service instance to enable the target service The instance processes the service request message.
- the determining module is specifically configured to: determine any one of the at least one service instance as the target service instance; or obtain the at least one service instance.
- the idle rate of each service instance determines the service instance with the largest idle rate as the target service instance.
- the service controller further includes a storage module, wherein the determining module is further configured to: after the sending module sends the service request message to the target service instance, determine the terminal identifier, the target service component, and the target service instance. The first correspondence between the two, wherein the service request message further includes a terminal identifier, and the storage module is configured to store the first correspondence between the terminal identifier, the target service component, and the target service instance.
- the determining module is further configured to: obtain a second correspondence between the terminal identifier, the service component, and the service instance; according to the second correspondence, The terminal identifier in the service request message and the target service component determine the target service instance.
- the service controller may further include a determining module and a clearing module, wherein the determining module is configured to determine whether the network service ends after the sending module sends the service request message to the target service instance; the clearing module is configured to: When the judging module judges that the network service ends, in the second correspondence, the terminal identifier, the target service component, and the target in the service request message are cleared. The correspondence between service instances.
- the sending module is specifically configured to obtain a network address of the target service instance, and send a service request message to the target service instance according to the network address.
- the network address includes an IP address, At least one of a MAC address and a port number.
- service controller in any one of the possible designs of the second aspect may perform any one of the possible technical solutions in the first aspect, and the implementation principle and the beneficial effects are similar, and details are not described herein.
- an embodiment of the present invention provides a communication system, where the communication system includes a service controller and at least one service component, and a service component corresponds to a network service, each service component includes at least one service instance, and the service controller is configured to: Receiving a service request message including a message identifier, determining a target service component corresponding to the message identifier, determining a target service instance in at least one service instance of the target service component, and sending a service request message to the target service instance; the service instance is configured to receive the service The service request message sent by the controller and processing the service request message.
- a network service can be provided to a user through a service instance, and collaboration between multiple network elements is not required to provide a service to the user, which reduces the number of message interactions and shortens the network service provided to the user. Time, which in turn increases the efficiency of the communication system providing network services to users. Further, when it is required to make changes to the network service in the communication system (for example, upgrading an existing network service or adding a new network service to the communication system), only the service component corresponding to the network service needs to be performed. The change can be performed without changing the processing logic of multiple network elements in the communication system and the interaction process between multiple network elements. The process is simple and convenient, and the cost of maintaining the network service is reduced.
- the system further includes a service deployment center and a service registration center, wherein the service deployment center is configured to determine a correspondence between the service component and the message identifier in the communication system, and send a correspondence to the service registration center;
- the center is configured to receive and store the corresponding relationship sent by the service deployment center.
- the service controller is configured to receive the service request message including the message identifier, obtain the correspondence in the service registration center, and determine the corresponding message identifier according to the corresponding relationship.
- the target service component determines a target service instance in at least one service instance of the target service component and sends a service request message to the target service instance.
- the service deployment center is further configured to acquire a service requirement corresponding to each service component in the communication system, and deploy at least one service instance for each service component in the communication system according to the service requirement corresponding to each service component. And sending, to the service registry, a service instance included in each service component, and attribute information of each service instance, where the attribute information includes a network address of the service instance; the service registration center is further configured to receive and store each service component sent by the service deployment center.
- the target service component obtains at least one service instance included in the target service component in the service registry, determines the target service instance in the at least one service instance, and sends a service request message to the target service instance.
- the communication system further includes a monitoring module, configured to acquire an operating state of the service instance in the communication system, and generate a failure notification message when the working state of the service instance is an abnormal state.
- the monitoring module monitors the working status of the service instance in the communication system in real time, and timely reports the fault, which effectively improves the reliability of the communication system.
- an embodiment of the present invention provides a service controller, where the service controller includes a processor, a receiving port, a sending port, a communication bus, and a memory.
- the communication bus is used to implement a communication connection between components, and various programs can be stored in the memory.
- the processor performs various processing functions and implements the method steps of the embodiment by executing a program stored in the memory.
- Receiving, by the receiving port, the service request message, the service request message includes a message identifier, and determining, according to the service request message, the target service component corresponding to the message identifier, and determining the target service instance in the at least one service instance of the target service component;
- the service request message is sent to the target service instance through the sending port, so that the target service instance processes the service request message.
- the processor may determine the target service instance in the at least one service instance by using the following feasible implementation manner, specifically:
- the processor further determines the first pair between the terminal identifier, the target service component, and the target service instance. Should be related, wherein the service request message further includes a terminal identifier,
- the processor stores the first correspondence stored between the terminal identifier, the target service component, and the target service instance in a memory.
- the processor may determine the target service instance in the at least one service instance by using the following feasible implementation manner, specifically:
- the target service instance is determined according to the second correspondence, the terminal identifier in the service request message, and the target service component.
- the processor sends the service request message to the target service instance through the sending port, it is further determined whether the network service ends;
- the processor determines that the network service ends, in the second correspondence, the correspondence between the terminal identifier, the target service component, and the target service instance in the service request message is cleared.
- the processor may send a service request message to the target service instance by using a feasible implementation manner. Specifically, the processor obtains a network address of the target service instance, and sends a service request message to the target service instance according to the network address.
- the network address includes at least one of an IP address, a MAC address, and a port number.
- the network service implementation method, the service controller, and the communication system provided by the embodiment of the present invention after the service controller receives the service request message including the message identifier, the service controller determines the target service component corresponding to the message identifier according to the service request message.
- a target service instance is determined in at least one service instance of the target service component, and a service request message is sent to the target service instance to cause the target service instance to process the service request message.
- a service instance can provide a network service to the user, and does not require cooperation between multiple network elements to provide a service to the user, which reduces the number of message interactions and shortens the network service provided to the user. Time, which in turn increases the efficiency of the communication system providing network services to users.
- FIG. 1 is a network architecture diagram of a communication system provided by the present invention.
- FIG. 2 is a schematic structural diagram 1 of a communication system provided by the present invention.
- FIG. 3 is a schematic structural diagram 2 of a communication system provided by the present invention.
- FIG. 4 is a flowchart of a method for implementing a network service according to the present invention.
- FIG. 5 is a schematic structural diagram 1 of a service controller provided by the present invention.
- FIG. 6 is a schematic structural diagram 2 of a service controller provided by the present invention.
- FIG. 7 is a schematic structural diagram of hardware of a service controller according to an embodiment of the present invention.
- the communication system includes a service controller 101 and M service components (102-1 to 102-M), and each service component corresponds to a network service.
- a service component includes at least one service instance; wherein a service instance of the service component can be obtained by deploying a service component in the communication system, and the service instance provides a corresponding network service to the user, and multiple services of the same service component The instance provides the same network service to the user. Multiple service instances of the same service component can be deployed in the same hardware device or in different hardware devices.
- the service request is sent to the service controller, and the service controller forwards the service request to the corresponding service instance according to the type of the network service corresponding to the service request, and the service request is forwarded to the corresponding service instance.
- the service instance processes the service request to provide the corresponding network service to the client.
- the communication system includes a service controller 201 and at least one service component (202-1 to 202-M), each service component including at least one service instance. ,among them,
- the service controller is configured to receive a service request message including a message identifier, determine a target service component corresponding to the message identifier, determine a target service instance in the at least one service instance of the target service component, and send a service request message to the target service instance; the service instance For receiving service controller The service request message is sent and the service request message is processed.
- a service component corresponds to a network service
- each service component can be implemented by software, or each service component can also be implemented by software and hardware.
- Rate for each service component, multiple service instances can be deployed in the communication system, and the multiple service instances provide network services to the users respectively.
- the service component 1 corresponds to the bearer management service
- the service instances of the three service components 1 can be deployed in the communication system, respectively, as the service instance 1 - the service instance 3, and the three service instances provide the bearer management service to the user,
- the communication system can provide a bearer management service to 1000 users, and the bearer management service can be provided by the service instance 1 to the user 1 - the user 300, and the bearer management service is provided by the service instance 2 to the user 301 - the user 750, by the service instance 3 User 751 - User 1000 provides a bearer management service.
- the message identifier in the network service request may indicate the type of the request message.
- the message identifier may be represented by a preset code identifier (for example, a protocol identification identifier), where a network service corresponds to A service component, a network service corresponding to one or more message identifiers.
- the message that the user interacts with the service control center may include a network attach request message and a network detach request message, where the message identifier message is included in the network attach request message.
- the message included in the network detach request message is identified as message -002
- the service component corresponding to the network service is service component 1
- the correspondence between the location management service, the message identifier, and the service component may be as shown in Table 1.
- the network service, the message identifier, and the service component may also have a one-to-one correspondence, for example, the bearer management service, the message identifier, and the correspondence between the service components shown in Table 1. .
- the user When the user needs to obtain the network service in the communication system, the user sends a service request message including the message identifier to the service controller, and when the service controller receives the service request message, determines the target service component corresponding to the message identifier.
- the service controller determines that the target service component is obtained, the at least one service instance corresponding to the target service component is obtained, and the target service instance is determined in the at least one service instance, specifically: if the target service component corresponds to only one service instance, the service The controller directly determines the one service instance as the target service instance; if the target service component corresponds to multiple (more than one) service instances, the service controller selects one service instance as the target service instance among the multiple service instances, Alternatively, the service controller may randomly select one service instance as the target service instance among the multiple service instances, or determine the service instance with the largest idle rate as the target service instance according to the idle rate of each service instance. It should be noted that, in the actual application process, when the target service component corresponds to multiple (more than one) service instances, the target service instance may also be selected among the multiple service instances according to other methods, and the present invention does not specifically limited.
- the service controller determines that the target service instance is obtained in the at least one service instance corresponding to the target service component, the received service request message is forwarded to the target service instance.
- the target service instance receives the service request message sent by the service controller, the target service instance processes the service request message to provide a corresponding service to the user who sends the service request message.
- the communication system provided by the embodiment of the present invention includes multiple service components, each service component includes at least one service instance, and the service instance provides a network service to the user.
- a network service can be provided to a user through a service instance, and collaboration between multiple network elements is not required to provide a service to the user, which reduces the number of message interactions and shortens the network service provided to the user. Time, which in turn increases the efficiency of the communication system providing network services to users.
- it is required to make changes to the network service in the communication system for example, upgrading an existing network service or adding a new network service to the communication system
- only the service component corresponding to the network service needs to be performed. The change can be performed without changing the processing logic of multiple network elements in the communication system and the interaction process between multiple network elements. The process is simple and convenient, and the cost of maintaining the network service is reduced.
- service deployment information and a service registration center may be added to the communication system.
- the communication system is further implemented by the embodiment shown in FIG. Description.
- FIG. 3 is a schematic structural diagram of a communication system provided by the present invention.
- the communication system further includes a service deployment center 203 and a service registration center 204, where
- the service deployment center is configured to determine a correspondence between the service component and the message identifier in the communication system, and send a correspondence to the service registration center; correspondingly, the service registration center is configured to receive and store the corresponding relationship sent by the service deployment center;
- the service deployment center is further configured to acquire a service requirement corresponding to each service component in the communication system, deploy at least one service instance for each service component in the communication system according to the service requirement corresponding to each service component, and send each service to the service registration center.
- the service instance included in the component, and the attribute information of each service instance; correspondingly, the service registration center is configured to receive and store the service instance included in each service component sent by the service deployment center, and attribute information of each service instance, where the attribute The information includes the network address of the service instance.
- the network service corresponding service component that needs to be added is obtained, the correspondence between the service component and the message identifier of the network service is determined, and the correspondence is sent to the service registration center.
- the service registry receives the correspondence, the corresponding relationship is saved.
- the service deployment center After the service deployment center determines that the service component is obtained, the service deployment center acquires the network requirement of the network service in the communication system, and determines the number of service instances that need to be deployed in the communication system according to the network requirement, in the hardware device in the communication system. Deploy a corresponding number of service instances, determine attribute information of each service instance, such as the network address of the service instance, and send the service instance included in each service component and the attribute information of each service instance to the service registration center. After receiving the service instance included in each service component and the attribute information of each service instance, the service instance included in each service component and the attribute information of each service instance are saved.
- the service component 1 that can implement the location management service, and the message identifier of the location management service are determined, and the service component 1 and the network are determined.
- the corresponding relationship of the service 1 is sent to the service registration center, and the corresponding relationship is saved by the service registration center.
- the service deployment center can deploy the service service component 1 on the hardware device 1, obtain the service instance 1 and the service instance 2, deploy the service component 1 on the hardware device 2, obtain the service instance 3 and the service instance 4, and obtain the service instance 1
- the attribute information of the service instance 4, such as the service instance 1 - the network address of the service instance 4, for example, the network address of the service instance 1 may be the IP address of the hardware device 1, and the port number of the service instance 1 on the hardware device 1.
- the service controller is specifically configured to: after the service controller receives the service request message including the message identifier, the service controller obtains the message identifier and the service component in the service registry. Corresponding relationship, and determining a target service component corresponding to the message identifier according to the correspondence relationship and the message identifier in the service request message; then, the service controller acquires at least one service instance included in the target service component in the service registry, A target service instance is determined in the at least one service instance and a service request message is sent to the target service instance.
- the service deployment center may also add a service instance or delete the service instance for the service component existing in the communication system, and the service deployment center may also change the attribute information of the existing service instance, for example, the service instance.
- the network address is changed.
- the service deployment center changes the service instance of the service component or the attribute information of the service instance
- the service deployment center sends a change notification to the service registration center, so that the service registration center provides the service instance of the service component or the attribute information of the service instance. Make changes.
- the monitoring module 205 can also be set in the communication system, and the monitoring module 205 can be used to obtain the working state of the service instance in the communication system, and in the working state of the service instance. A fault notification message is generated when it is in an abnormal state. Further, the monitoring module may also collect parameters such as the number of running times and the running time of each service instance to evaluate the performance of the communication system.
- FIG. 4 is a flowchart of a method for implementing a network service according to the present invention.
- the method may include:
- the service controller receives a service request message, where the service request message includes a message identifier.
- the service controller determines, according to the service request message, a target service component corresponding to the message identifier.
- the service controller determines a target service instance in at least one service instance of the target service component, and sends a service request message to the target service instance, so that the target service instance processes the service request message.
- the network service, the message identifier, and the service component have a corresponding relationship, and the corresponding relationship is described in detail in the embodiment shown in FIG. 2, and details are not described herein again.
- the user When the user needs to obtain the network service in the communication system, the user sends a service request message including the message identifier to the service controller, and the service controller determines, according to the correspondence between the message identifier and the service component, and the message identifier included in the service request message.
- the target service component that corresponds to the message ID.
- the service controller After the service controller determines that the target service component is obtained, acquiring at least one service instance corresponding to the target service component, determining a target service instance in the at least one service instance, and forwarding the received service request message to the target service instance,
- the service controller may obtain a network address of the target service instance, and send a service request message to the target service instance according to the network address, where the network address includes an Internet Protocol IP address, a media access control MAC address, and a port number. At least one.
- the target service instance After the target service instance receives the service request message sent by the service controller, the target service instance processes the service request message to provide a corresponding service to the user who sends the service request message.
- the network service implementation method provided by the embodiment of the present invention after the service controller receives the service request message including the message identifier, the service controller determines, according to the service request message, the target service component corresponding to the message identifier, at least one of the target service components.
- the target service instance is determined in the service instance, and a service request message is sent to the target service instance to cause the target service instance to process the service request message.
- a service instance can provide a network service to the user, and does not require cooperation between multiple network elements to provide a service to the user, which reduces the number of message interactions and shortens the network service provided to the user. Time, which in turn increases the efficiency of the communication system providing network services to users.
- the user may need to perform multiple message interactions with a service instance to obtain a corresponding network service.
- the trigger message of the service request message sent by the user to the service instance for the first time the service request message sent to the service instance any time before the first time is a process message.
- the user needs to perform 8 times of message interaction with the service instance 1 to obtain the network service 1.
- the user sends the service instance 1 to the service instance 1.
- the first message sent is a trigger message
- the second to eighth messages sent by the user to the service instance 1 are process messages.
- the process of determining the target service instance by the service controller in at least one service instance of the target service component is different, specifically, the following two Possible implementations:
- the type of the service request message is a trigger message:
- the service controller determines any one of the at least one service instance as the target service instance; or the service controller acquires the idle rate of each service instance in the at least one service instance, The service instance with the highest idle rate is determined as the target service instance.
- the idleness of the service instance is a ratio of the remaining service capability of the service instance to the total service capability of the service instance.
- the service instance may provide network services to 100 users, if the service instance is currently going to 70 If the user provides network services, the service instance can also provide network services to 30 users. At this time, the service instance has an idle rate of 30%.
- the service request message may further include a terminal identifier, where the service controller determines and stores the terminal identifier, the target service component, and the target service instance after the service controller determines that the target service instance is obtained.
- the service controller determines and stores the terminal identifier, the target service component, and the target service instance after the service controller determines that the target service instance is obtained.
- the target service component corresponding to the message identifier included in the acquisition service request message 1 is the service component 1, and the service component 1 includes three services.
- the examples are respectively recorded as service instance 1 - service instance 3.
- the service controller may further acquire the terminal identifier (terminal 1) included in the service request message 1, and determine a first correspondence between the terminal 1, the service component 1, and the service instance 2, and store the corresponding relationship.
- the type of service request message is a process message:
- the service request message further includes a terminal identifier
- the service controller acquires a second correspondence between the terminal identifier, the service component, and the service instance, and according to the second correspondence, the service request message The terminal identifier, and the target service component, determine the target service instance.
- the service controller determines whether the network service is ended. If the determination result is yes, the service controller is In the second correspondence, the correspondence between the terminal identifier, the target service component, and the target service instance in the service request message is cleared.
- whether the network service ends is determined by the service controller: determining, by the service controller, whether the terminal identifier and the message identifier with the same message identifier are received within the preset duration, and if yes, determining that the network service ends. For example, suppose that in order to obtain the network service 1, the terminal identifier included in the service request message sent to the service controller is the terminal 1, the message identifier is the network service 1, and the service controller sends a network service message to the target service instance. Thereafter, if the service request message including the terminal 1 and the network service 1 is not received within a preset time period (for example, 5 minutes), it is determined that the network service 1 ends.
- a preset time period for example, 5 minutes
- the type of the service request message may be included in the service request message.
- the user interacts with any message performed by the service instance, and the service instance generates data of the user in the current network service, and may be used in subsequent message interaction.
- the data generated in the previous message interaction in this network service For example, in the process that the service instance 1 provides the network service 1 to the user 1, the service instance 1 needs to perform 5 times of information interaction with the user 1 to complete the network service 1, and the service instance 1 interacts with each information performed by the user 1
- the service instance 1 may use the data generated when the service instance 1 interacts with the user 1 for the first time when performing the second information interaction with the user 1.
- the service controller determines the target service instance in at least one service instance of the target service component in a different manner, so that in the process of one network service, the same A service instance provides network services to the same user, avoiding multiple service instances providing network services to the same user in a network service process.
- the user 1 sends a service request message 1 to the service controller through the terminal 1, and the service request message 1 includes a message identifier (network service 1) and a terminal identifier (terminal 1).
- the service controller After receiving the service request message 1, the service controller determines that the service request message 1 is a trigger message according to the message type in the service request message 1, and the service controller according to the correspondence between the message identifier and the service component, and the network service 1, Determining that the target service component corresponding to the network service 1 is the service component 1, and acquiring the three service instances of the service component 1, respectively, as the service instance 1 - the service instance 3, and obtaining the idle rate of the service instance 1 - service instance 3, assuming The service instance 1 has an idle rate of 50%, the service instance 2 has an idle rate of 30%, and the service instance 3 has an idle rate of 60%. The service controller determines the service instance 3 with the highest idle rate as the target service instance.
- the service controller determines that the target service instance (service instance 3) is obtained, the service request message 1 is sent to the service instance 3, and the service request message 1 is processed by the service instance 3.
- the service controller records and stores the first correspondence between the terminal 1, the network service 1, and the service instance 3.
- the user 1 sends a service request message 2 to the service controller through the terminal 1, and the service request message 2 includes a message identifier (network service 1), a terminal identifier (terminal 1), and a message type ( Process message).
- the service request message 2 includes a message identifier (network service 1), a terminal identifier (terminal 1), and a message type ( Process message).
- the service controller After receiving the service request message 2, the service controller determines that the service request message 2 is a process message according to the message type in the service request message 2, and the service controller is based on the saved terminal 1, the network service 1, and the service instance 3.
- the first correspondence between the two, the terminal 1 and the target service instance corresponding to the network service 1 (service instance 3) are acquired, and the service request message 2 is sent to the service instance 3, and the service request message 2 is processed by the service instance 3.
- the service controller determines that the network service 1 has not ended, and does not delete the first correspondence.
- third to fifth information interaction process is similar to the second information interaction process, and details are not described herein.
- the service controller determines that the network service 1 is over, then Delete the first correspondence.
- FIG. 5 is a schematic structural diagram 1 of a service controller according to the present invention.
- the service controller is applied to a communication system, where the communication system includes the service controller and at least one service component, and one service component corresponds to a network service, and each service component includes For at least one service instance, please refer to FIG. 5, the service controller includes:
- the receiving module 501 is configured to receive a service request message, where the service request message includes a message identifier.
- the determining module 502 is configured to determine, according to the service request message, a target service component corresponding to the message identifier, and determine the target service instance in the at least one service instance of the target service component;
- the trigger message is a message that triggers the network service
- the determining module 502 may specifically be used to:
- the determining module 502 is further configured to: after the sending module 503 sends the service request message to the target service instance, determine a first correspondence between the terminal identifier, the target service component, and the target service instance, where the service request message further includes the terminal identifier ,
- the storage module 504 is configured to store a first correspondence between the terminal identifier, the target service component, and the target service instance.
- the process message is a message that is sent by the user after the trigger message is sent, and the service request message further includes the terminal identifier, and the determining module 502 specifically Can be used for:
- the target service instance is determined according to the second correspondence, the terminal identifier in the service request message, and the target service component.
- the service controller may further include a determining module 505 and a clearing module 506, where
- the determining module 505 is configured to: after the sending module sends a service request message to the target service instance, Determine whether the network service is over;
- the clearing module 506 is configured to, when the determining module determines that the network service ends, clear the correspondence between the terminal identifier, the target service component, and the target service instance in the service request message in the second correspondence.
- the sending module 503 is specifically configured to:
- a service request message is sent to the target service instance based on the network address.
- the service controller of the embodiment of the present invention may perform the technical solution shown in the foregoing method embodiment, and the implementation principle and the beneficial effects are similar, and details are not described herein.
- FIG. 7 is a schematic diagram of a hardware structure of a service controller according to an embodiment of the present invention.
- the service controller includes a processor 701, a receiving port 702, a sending port 703, a communication bus 704, and a memory 705.
- the communication bus 704 is used to implement communication connection between components, and various programs can be stored in the memory 705.
- the processor 701 performs various processing functions and implements the method steps of the embodiment by executing a program stored in the memory 705. specific:
- the processor 701 receives a service request message through the receiving port 702, where the service request message includes a message identifier;
- the processor 701 determines, according to the service request message, a target service component corresponding to the message identifier, and determines a target service instance in the at least one service instance of the target service component;
- the processor 701 sends a service request message to the target service instance through the send port 703 to cause the target service instance to process the service request message.
- the processor 701 may determine the target service instance in the at least one service instance by using the following feasible implementation manner, specifically:
- the processor 701 further determines a first correspondence between the terminal identifier, the target service component, and the target service instance, where the service request message is further Including the terminal identification,
- the processor 701 stores the first correspondence between the storage terminal identifier, the target service component, and the target service instance in the memory 705.
- the processor 701 may determine the target service instance in the at least one service instance by using the following feasible implementation manner, specifically:
- the target service instance is determined according to the second correspondence, the terminal identifier in the service request message, and the target service component.
- processor 701 sends the service request message to the target service instance through the sending port 703, it also determines whether the network service ends.
- the processor 701 determines that the network service ends, in the second correspondence, the correspondence between the terminal identifier, the target service component, and the target service instance in the service request message is cleared.
- the processor 701 may send a service request message to the target service instance by using a feasible implementation manner. Specifically, the processor 701 obtains a network address of the target service instance, and sends a service request to the target service instance according to the network address. The message, wherein the network address comprises at least one of an internet protocol IP address, a media access control MAC address, and a port number.
- the service controller of the embodiment of the present invention may perform the technical solution shown in the foregoing method embodiment, and the implementation principle and the beneficial effects are similar, and details are not described herein.
- the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
- the foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明提供一种网络服务实现方法、服务控制器及通信***,该方法包括:接收包括消息标识的服务请求消息,根据服务请求消息,确定消息标识对应的目标服务组件,在目标服务组件的至少一个服务实例中确定目标服务实例,并向目标服务实例发送服务请求消息,以使目标服务实例对服务请求消息进行处理。用于提高提供网络服务的效率。
Description
本发明涉及通信技术领域,尤其涉及一种网络服务实现方法、服务控制器及通信***。
随着网络技术的不断发展,通信***向用户提供的网络服务的种类越来越多,例如,网络服务可以包括移动性管理、承载管理、位置管理等。
在现有技术中,在通信***中设置有多个网元,其中,网元可以包括:移动性管理实体(Mobility Management Entity,简称MME),服务网关(Serving Gateway,简称S-GW),分组数据网络网关(Packet Data Network Gateway,简称P-GW)等,当需要在通信***中实现一种网络服务时,一般根据需要实现的网络服务的特性,对多个网元的处理逻辑、以及多个网元之间的交互流程进行设置,由该多个网元共同实现一个网络服务。当用户需要获取一种网络服务时,用户向通信***的网络侧发送相应的服务请求消息,在网络侧接收到用户发送的服务请求消息后,网络侧确定该服务请求消息对应的多个网元,并将该服务请求消息在该多个网元之间进行传递,由该多个网元依次对该服务请求消息进行处理,以完成用户请求的网络服务。
然而,在上述过程中,由于一个网络服务需要多个网元的协作才能完成,使得在用户通过服务请求消息请求获取网络服务时,需要将服务请求消息在多个网元之间进行传递,由多个网元进行处理,过程复杂,消耗较多时长,导致通信***向用户提供网络服务的效率低下。
发明内容
本发明实施例提供一种网络服务实现方法、服务控制器及通信***,用于提高提供网络服务的效率。
第一方面,本发明实施例提供一种网络服务实现方法。该方法的执行主体为服务控制器,其中,该方法包括:服务控制器接收包括消息标识的服务
请求消息,并根据接收到的服务请求消息,确定服务请求消息中的消息标识对应的目标服务组件,由于每一个服务组件包括至少一个服务实例,在服务控制器确定得到目标服务组件后,服务控制器在目标服务组件的至少一个服务实例中确定目标服务实例,并向目标服务实例发送服务请求消息,以使目标服务实例对服务请求消息进行处理。在该过程中,通过一个服务实例即可向用户提供一种网络服务,不需要多个网元之间的协作向用户提供一种服务,减少了消息交互次数,缩短了向用户提供网络服务的时间,进而提高通信***向用户提供网络服务的效率。
在一种可能的设计中,当服务请求消息的类型为触发消息时,该触发消息为触发网络服务的消息,服务控制器可以通过如下可行的实现方式在服务组件的至少一个服务实例中确定目标服务实例,具体的:
一种可行的实现方式:服务控制器将至少一个服务实例中的任意一个服务实例确定为目标服务实例;在该种可行的实现方式中,在至少一个服务实例中随机确定一个服务实例为目标服务实例,可以提高服务控制器确定目标服务实例的速度。
另一种可行的实现方式:服务控制器获取至少一个服务实例中各服务实例的空闲率,将空闲率最大的服务实例确定为目标服务实例;在该种可行的实现方式中,通过将空闲率最大的服务实例确定为目标服务实例,可以更加有效的利用各服务实例的资源。
在又一种可能的设计中,服务请求消息还可以包括终端标识,在服务控制器向目标服务实例发送服务请求消息之后,服务控制器还可以确定并存储终端标识、目标服务组件和目标服务实例之间的第一对应关系。
在另一种可能的设计中,当服务请求消息的类型为过程消息时,该过程消息为用户在发送触发消息之后发送的、用于获取网络服务的消息,服务请求消息还包括终端标识,服务控制器可以通过如下可行的实现方式在服务组件的至少一个服务实例中确定目标服务实例,具体的:服务控制器获取终端标识、服务组件和服务实例之间的第二对应关系;服务控制器根据第二对应关系、服务请求消息中的终端标识、以及目标服务组件,确定目标服务实例。
在再一种可能的设计中,在服务控制器向目标服务实例发送服务请求消息之后,服务控制器还可以判断网络服务是否结束;若判断结果为是,服务
控制器在第二对应关系中,清除服务请求消息中的终端标识、目标服务组件、以及目标服务实例之间的对应关系。
在上述任意一种可能的设计中,服务控制器可以通过如下可行的实现方式向目标服务实例发送服务请求消息,具体的:服务控制器获取目标服务实例的网络地址,并根据网络地址,向目标服务实例发送服务请求消息,可选的,网络地址可以包括互联网协议(Internet Protocol,简称IP)地址、媒体访问控制(Media Access Control,简称MAC)地址以及端口号中的至少一种。
第二方面,本发明实施例提供一种服务控制器,该服务控制器可以包括接收模块、确定模块、以及发送模块,其中,接收模块用于接收服务请求消息,服务请求消息包括消息标识;确定模块用于根据服务请求消息,确定消息标识对应的目标服务组件,并在目标服务组件的至少一个服务实例中确定目标服务实例;发送模块用于向目标服务实例发送服务请求消息,以使目标服务实例对服务请求消息进行处理。
在一种可能的设计中,当服务请求消息的类型为触发消息时,确定模块具体用于:将至少一个服务实例中的任意一个服务实例确定为目标服务实例;或者,获取至少一个服务实例中各服务实例的空闲率,将空闲率最大的服务实例确定为目标服务实例。
在又一种可能的设计中,服务控制器还包括存储模块,其中,确定模块还用于,在发送模块向目标服务实例发送服务请求消息之后,确定终端标识、目标服务组件和目标服务实例之间的第一对应关系,其中,服务请求消息还包括终端标识,存储模块用于,存储终端标识、目标服务组件和目标服务实例之间的第一对应关系。
在另一种可能的设计中,当服务请求消息的类型为过程消息时,确定模块具体还用于:获取终端标识、服务组件和服务实例之间的第二对应关系;根据第二对应关系、服务请求消息中的终端标识、以及目标服务组件,确定目标服务实例。
在又一种可能的设计中,服务控制器还可以包括判断模块和清除模块,其中,判断模块用于在发送模块向目标服务实例发送服务请求消息之后,判断网络服务是否结束;清除模块用于在判断模块判断网络服务结束时,在第二对应关系中,清除服务请求消息中的终端标识、目标服务组件、以及目标
服务实例之间的对应关系。
在第二方面的任意一种可能的设计中,发送模块具体用于获取目标服务实例的网络地址,并根据网络地址,向目标服务实例发送服务请求消息,可选的,网络地址包括IP地址、MAC地址以及端口号中的至少一种。
需要说明的是,第二方面的任意一种可能的设计中的服务控制器均可以执行第一方面任意一种可能的技术方案,其实现原理以及有益效果类似,此处不再进行赘述。
第三方面,本发明实施例提供一种通信***,该通信***包括服务控制器和至少一个服务组件,一个服务组件对应一种网络服务,各服务组件包括至少一个服务实例,服务控制器用于,接收包括消息标识的服务请求消息,确定消息标识对应的目标服务组件,在目标服务组件的至少一个服务实例中确定目标服务实例,并向目标服务实例发送服务请求消息;服务实例用于,接收服务控制器发送的服务请求消息,并对服务请求消息进行处理。在该***中,通过一个服务实例即可向用户提供一种网络服务,不需要多个网元之间的协作向用户提供一种服务,减少了消息交互次数,缩短了向用户提供网络服务的时间,进而提高通信***向用户提供网络服务的效率。进一步的,当需要对通信***中网络服务进行更改时(例如,对已有的一个网络服务进行升级,或者在通信***中增加新的网络服务),只需要对该网络服务对应的服务组件进行更改即可,无需对通信***中的多个网元的处理逻辑、以及多个网元之间的交互流程进行改变,该过程简单方便,降低了对网络服务进行维护的成本。
一种可能的设计中,***还包括服务部署中心和服务注册中心,其中,服务部署中心用于,确定通信***中服务组件与消息标识的对应关系,并向服务注册中心发送对应关系;服务注册中心用于,接收并存储服务部署中心发送的对应关系;相应的,服务控制器用于,接收包括消息标识的服务请求消息,在服务注册中心中获取对应关系,并根据对应关系确定消息标识对应的目标服务组件,在目标服务组件的至少一个服务实例中确定目标服务实例,并向目标服务实例发送服务请求消息。通过在通信***中设置服务部署中心和服务注册中心,由服务部署中心和服务注册中心执行不同的任务,更加有利于对通信***的维护。
在另一种可能的设计中,服务部署中心还用于,获取通信***中各服务组件对应的服务需求,根据各服务组件对应的服务需求,在通信***中为各服务组件部署至少一个服务实例,并向服务注册中心发送各服务组件包括的服务实例、及各服务实例的属性信息,属性信息包括服务实例的网络地址;服务注册中心还用于,接收并存储服务部署中心发送的各服务组件包括的服务实例、及各服务实例的属性信息;相应的,服务控制器还用于,接收包括消息标识的服务请求消息,在服务注册中心中获取对应关系,并根据对应关系确定消息标识对应的目标服务组件,在服务注册中心中获取目标服务组件包括的至少一个服务实例,在至少一个服务实例中确定目标服务实例,并向目标服务实例发送服务请求消息。
在又一种可能的设计中,该通信***还包括监控模块,监控模块用于,获取通信***中的服务实例的工作状态,并在服务实例的工作状态为异常状态时,生成故障通知消息。通过监控模块对通信***中的服务实例的工作状态进行实时监控,并及时反馈故障,有效提高了通信***的可靠性
第四方面,本发明实施例提供一种服务控制器,其中该服务控制器包括处理器、接收端口、发送端口、通信总线以及存储器。其中,通信总线用于实现元件之间的通信连接,存储器中可以存储各种程序,处理器通过执行存储器中存储的程序,完成各种处理功能以及实现本实施例的方法步骤,具体的:
处理器通过接收端口接收服务请求消息,服务请求消息包括消息标识;并根据服务请求消息,确定消息标识对应的目标服务组件,并在目标服务组件的至少一个服务实例中确定目标服务实例;处理器通过发送端口向目标服务实例发送服务请求消息,以使目标服务实例对服务请求消息进行处理。
在实际应用过程中,当服务请求消息的类型为触发消息时,处理器可以通过如下可行的实现方式在至少一个服务实例中确定目标服务实例,具体的:
将至少一个服务实例中的任意一个服务实例确定为目标服务实例;或者,
获取至少一个服务实例中各服务实例的空闲率,将空闲率最大的服务实例确定为目标服务实例。
在实际应用过程中,处理器在通过发送端口向目标服务实例发送服务请求消息之后,还确定终端标识、目标服务组件和目标服务实例之间的第一对
应关系,其中,服务请求消息还包括终端标识,
处理器将存储终端标识、目标服务组件和目标服务实例之间的第一对应关系存储中存储器中。
在实际应用过程中,当服务请求消息的类型为过程消息时,处理器可以通过如下可行的实现方式在至少一个服务实例中确定目标服务实例,具体的:
获取终端标识、服务组件和服务实例之间的第二对应关系;
根据第二对应关系、服务请求消息中的终端标识、以及目标服务组件,确定目标服务实例。
进一步的,在处理器通过发送端口向目标服务实例发送服务请求消息之后,还判断网络服务是否结束;
当处理器判断网络服务结束时,在第二对应关系中,清除服务请求消息中的终端标识、目标服务组件、以及目标服务实例之间的对应关系。
可选的,处理器可以通过如下可行的实现方式,向目标服务实例发送服务请求消息,具体的:处理器获取目标服务实例的网络地址,并根据网络地址,向目标服务实例发送服务请求消息,其中,网络地址包括IP地址、MAC地址以及端口号中的至少一种。
本发明实施例提供的网络服务实现方法、服务控制器及通信***,在服务控制器接收到包括消息标识的服务请求消息后,服务控制器根据服务请求消息,确定消息标识对应的目标服务组件,在目标服务组件的至少一个服务实例中确定目标服务实例,并向目标服务实例发送服务请求消息,以使目标服务实例对服务请求消息进行处理。在该过程中,通过一个服务实例即可向用户提供一种网络服务,不需要多个网元之间的协作向用户提供一种服务,减少了消息交互次数,缩短了向用户提供网络服务的时间,进而提高通信***向用户提供网络服务的效率。
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍,显而易见地,下面描述中的附图是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为本发明提供的通信***的网络架构图;
图2为本发明提供的通信***的结构示意图一;
图3为本发明提供的通信***的结构示意图二;
图4为本发明提供的网络服务实现方法的流程图;
图5为本发明提供的服务控制器的结构示意图一;
图6为本发明提供的服务控制器的结构示意图二;
图7为本发明实施例提供的服务控制器的硬件结构示意图。
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
图1为本发明提供的通信***的网络架构图,请参照图1,通信***包括服务控制器101和M个服务组件(102-1至102-M),每一个服务组件对应一种网络服务,一个服务组件包括至少一个服务实例;其中,可以通过在通信***中部署服务组件,得到该服务组件的一个服务实例,由服务实例向用户提供相应的网络服务,同一个服务组件的多个服务实例向用户提供给的网络服务相同,同一服务组件的多个服务实例可以部署在同一硬件设备中,也可以部署在不同的硬件设备中。在实际应用过程中,当用户需要从网络侧获取网络服务时,向服务控制器发送服务请求,服务控制器根据服务请求对应的网络服务的类型,将服务请求转发至相应的服务实例,由该服务实例对服务请求进行处理,以向客户端提供相应的网络服务。下面,通过具体实施例对本发明提供的通信***、网络服务实现方法及装置进行详细说明。
图2为本发明提供的通信***的结构示意图一,请参照图2,该通信***包括服务控制器201和至少一个服务组件(202-1至202-M),各服务组件包括至少一个服务实例,其中,
服务控制器用于,接收包括消息标识的服务请求消息,确定消息标识对应的目标服务组件,在目标服务组件的至少一个服务实例中确定目标服务实例,并向目标服务实例发送服务请求消息;服务实例用于,接收服务控制器
发送的服务请求消息,并对服务请求消息进行处理。
在本发明实施例中,一个服务组件对应一种网络服务,各服务组件可以通过软件实现,或者,各服务组件也可以通过软件和硬件实现,在实际应用过程中,为了提高向用户提供服务的速率,针对每一个服务组件,可以在通信***中部署多个服务实例,由该多个服务实例分别向用户提供网络服务。例如,服务组件1对应承载管理服务,可以在通信***中部署3个服务组件1的服务实例,分别记为服务实例1-服务实例3,由该3个服务实例向用户提供承载管理服务,假设该通信***可以向1000个用户提供承载管理服务,则可以由服务实例1向用户1-用户300提供承载管理服务,由服务实例2向用户301-用户750提供承载管理服务,由服务实例3向用户751-用户1000提供承载管理服务。
在本发明实施例中,网络服务请求中的消息标识可以表示该请求消息的类型,可选的,消息标识可以通过预设代码标识(例如,协议识别标识)表示,其中,一种网络服务对应一种服务组件,一种网络服务对应一种或多种消息标识。
示例性的,在服务控制中心向用户提供位置管理服务的过程中,用户与服务控制中心交互的消息可以包括网络附着请求消息和网络去附着请求消息,在网络附着请求消息中包括消息标识为消息-001,在网络去附着请求消息中包括的消息标识为消息-002,再假设网络服务对应的服务组件为服务组件1,则位置管理服务、消息标识、以及服务组件的对应关系可以如表1所示。当然,在实际应用过程中,网络服务、消息标识、以及服务组件之间也可以具有一一对应关系,例如,表1中所示的承载管理服务、消息标识、以及服务组件之间的对应关系。
表1
网络服务 | 消息标识 | 服务组件 |
位置管理服务 | 消息-001 | 服务组件1 |
位置管理服务 | 消息-002 | 服务组件1 |
承载管理服务 | 消息-003 | 服务组件2 |
…… | …… | …… |
下面,对图1实施例所示的通信***的工作过程进行详细说明。
当用户需要在通信***中获取网络服务时,用户向服务控制器发送包括消息标识的服务请求消息,当服务控制器接收到服务请求消息后,确定与该消息标识对应的目标服务组件。
在服务控制器确定得到目标服务组件后,获取目标服务组件对应的至少一个服务实例,并在该至少一个服务实例中确定目标服务实例,具体的:若目标服务组件仅对应一个服务实例,则服务控制器直接将该一个服务实例确定为目标服务实例;若目标服务组件对应多个(大于1个)服务实例,则服务控制器在该多个服务实例中选择一个服务实例作为目标服务实例,可选的,服务控制器可以在该多个服务实例中随机选择一个服务实例作为目标服务实例,也可以根据各服务实例的空闲率,将空闲率最大的服务实例确定为目标服务实例。需要说明的是,在实际应用过程中,当目标服务组件对应多个(大于1个)服务实例时,还可以根据其他方法在该多个服务实例中选择目标服务实例,本发明对此不作具体限定。
在服务控制器在目标服务组件对应的至少一个服务实例中确定得到目标服务实例后,将接收到的服务请求消息转发给该目标服务实例。在目标服务实例接收到服务控制器发送的服务请求消息后,目标服务实例对该服务请求消息进行处理,以向发送该服务请求消息的用户提供相应的服务。
本发明实施例提供的通信***中包括多个服务组件,各服务组件包括至少一个服务实例,并由服务实例向用户提供一种网络服务。在该***中,通过一个服务实例即可向用户提供一种网络服务,不需要多个网元之间的协作向用户提供一种服务,减少了消息交互次数,缩短了向用户提供网络服务的时间,进而提高通信***向用户提供网络服务的效率。进一步的,当需要对通信***中网络服务进行更改时(例如,对已有的一个网络服务进行升级,或者在通信***中增加新的网络服务),只需要对该网络服务对应的服务组件进行更改即可,无需对通信***中的多个网元的处理逻辑、以及多个网元之间的交互流程进行改变,该过程简单方便,降低了对网络服务进行维护的成本。
在图2所示实施例的基础上,为了便于对通信***的维护,可以在该通信***中增设服务部署信息以及服务注册中心,下面,通过图3所示实施例对该通信***进行进一步的说明。
图3为本发明提供的通信***的结构示意图二,在图2所示实施例的基础上,请参照图3,通信***还包括服务部署中心203和服务注册中心204,其中,
服务部署中心用于,确定通信***中服务组件与消息标识的对应关系,并向服务注册中心发送对应关系;相应的,服务注册中心用于,接收并存储服务部署中心发送的对应关系;
服务部署中心还用于,获取通信***中各服务组件对应的服务需求,根据各服务组件对应的服务需求,在通信***中为各服务组件部署至少一个服务实例,并向服务注册中心发送各服务组件包括的服务实例、及各服务实例的属性信息;相应的,服务注册中心用于,接收并存储服务部署中心发送的各服务组件包括的服务实例、及各服务实例的属性信息,其中,属性信息包括服务实例的网络地址。
下面,对服务部署中心和服务注册中心的工作过程进行详细说明。
当需要在通信***中增设一个新的网络服务时,获取需要增设的网络服务对应服务组件,确定该服务组件与该网络服务的消息标识的对应关系,并向服务注册中心发送该对应关系,当服务注册中心收到该对应关系时,对该对应关系进行保存。
在服务部署中心确定得到服务组件后,服务部署中心获取通信***中对该网络服务的网络需求,根据网络需求确定需要在通信***中部署的服务实例的个数,在通信***中的硬件设备中部署相应个数的服务实例,确定各服务实例的属性信息,如服务实例的网络地址等,并向服务注册中心发送各服务组件包括的服务实例、及各服务实例的属性信息,当服务注册中心收到各服务组件包括的服务实例、及各服务实例的属性信息后,对各服务组件包括的服务实例、及各服务实例的属性信息进行保存。
示例性的,当需要在通信***中增设网络服务(位置管理服务)时,获取可以实现位置管理服务的服务组件1、以及位置管理服务的消息标识(网络服务1),确定服务组件1和网络服务1的对应关系,并向服务注册中心发送该对应关系,由服务注册中心对该对应关系进行保存。
假设服务组件1的一个服务实例可以向300个用户提供位置管理服务,且通信***具有1000个用户,则可以在通信***中部署4个服务实例,则服
务部署中心可以在硬件设备1上部署服务服务组件1,得到服务实例1和服务实例2,在硬件设备2上部署服务组件1,得到服务实例3和服务实例4,并分别获取服务实例1-服务实例4的属性信息,如服务实例1-服务实例4的网络地址,例如,服务实例1的网络地址可以为硬件设备1的IP地址、以及服务实例1在硬件设备1上的端口号。在服务部署中心完成对服务组件1的部署后,向服务注册中心发送服务组件1包括的服务实例1-服务实例4、及服务实例1-服务实例4的属性信息,由服务注册中心对该信息进行保存。
在通信***中增设服务部署中心和服务注册中心之后,服务控制器具体用于:当服务控制器接收到包括消息标识的服务请求消息后,服务控制器在服务注册中心中获取消息标识和服务组件之间的对应关系,并根据该对应关系以及服务请求消息中的消息标识确定消息标识对应的目标服务组件;然后,服务控制器在服务注册中心中获取该目标服务组件包括的至少一个服务实例,在该至少一个服务实例中确定目标服务实例,并向目标服务实例发送服务请求消息。
在实际应用过程中,服务部署中心还可以为通信***中已有的服务组件增设服务实例、或者删除服务实例,服务部署中心还可以对已有服务实例的属性信息进行变更,例如,对服务实例的网络地址进行变更。当服务部署中心对服务组件的服务实例、或者服务实例的属性信息进行变更后,服务部署中心向服务注册中心发送变更通知,以使得服务注册中心对服务组件的服务实例、或者服务实例的属性信息进行变更。
在实际应用过程中,为了提高通信***的可靠性,还可以在通信***中设置监控模块205,监控模块205可以用于,获取通信***中的服务实例的工作状态,并在服务实例的工作状态为异常状态时,生成故障通知消息。进一步的,监控模块还可以统计各服务实例的运行次数、运行时长等参数,以对通信***的性能进行评估。
图4为本发明提供的网络服务实现方法的流程图,请参照图4,该方法可以包括:
S401、服务控制器接收服务请求消息,服务请求消息包括消息标识;
S402、服务控制器根据服务请求消息,确定消息标识对应的目标服务组件;
S403、服务控制器在目标服务组件的至少一个服务实例中确定目标服务实例,并向目标服务实例发送服务请求消息,以使目标服务实例对服务请求消息进行处理。
在本发明实施例中,网络服务、消息标识、以及服务组件之间具有对应关系,该对应关系在图2所示实施例中进行了详细说明,此处不再进行赘述。
当用户需要在通信***中获取网络服务时,用户向服务控制器发送包括消息标识的服务请求消息,服务控制器根据消息标识和服务组件的对应关系、以及服务请求消息中包括的消息标识,确定与该消息标识对应的目标服务组件。在服务控制器确定得到目标服务组件后,获取目标服务组件对应的至少一个服务实例,并在该至少一个服务实例中确定目标服务实例,并将接收到的服务请求消息转发给该目标服务实例,可选的,服务控制器可以获取目标服务实例的网络地址,并根据网络地址,向目标服务实例发送服务请求消息,其中,网络地址包括互联网协议IP地址、媒体访问控制MAC地址以及端口号中的至少一种。在目标服务实例接收到服务控制器发送的服务请求消息后,目标服务实例对该服务请求消息进行处理,以向发送该服务请求消息的用户提供相应的服务。
本发明实施例提供的网络服务实现方法,在服务控制器接收到包括消息标识的服务请求消息后,服务控制器根据服务请求消息,确定消息标识对应的目标服务组件,在目标服务组件的至少一个服务实例中确定目标服务实例,并向目标服务实例发送服务请求消息,以使目标服务实例对服务请求消息进行处理。在该过程中,通过一个服务实例即可向用户提供一种网络服务,不需要多个网元之间的协作向用户提供一种服务,减少了消息交互次数,缩短了向用户提供网络服务的时间,进而提高通信***向用户提供网络服务的效率。
在图4所示实施例的基础上,当用户需要获取网络服务时,用户可能需要与一个服务实例进行多次消息交互才能获取得到相应的网络服务。在用户获取一个网络服务的过程中,用户第一次向服务实例发送的服务请求消息的触发消息,在第一次之外的任意次向服务实例发送的服务请求消息为过程消息。例如,用户需要与服务实例1进行8次消息交互才能获取得到网络服务1,则用户在通过服务实例1获取网络服务1的过程中,用户向服务实例1发
送的第一次消息为触发消息,用户向服务实例1发送的第二次至第8次消息均为过程消息。
在实际应用过程中,根据服务请求消息类型的不同(触发消息或过程消息),服务控制器在目标服务组件的至少一个服务实例中确定目标服务实例的过程也不相同,具体的,包括以下两种可行的实现方式:
一种可行的实现方式:服务请求消息的类型为触发消息:
当服务请求消息的类型为触发消息时,服务控制器将至少一个服务实例中的任意一个服务实例确定为目标服务实例;或者,服务控制器获取至少一个服务实例中各服务实例的空闲率,将空闲率最大的服务实例确定为目标服务实例。
在该种可行的实现方式中,服务实例的空闲率为服务实例剩余服务能力与服务实例的总服务能力之比,例如,服务实例可以向100个用户提供网络服务,若服务实例当前正在向70个用户提供网络服务,则该服务实例还可以向30个用户提供网络服务,此时,该服务实例的空闲率为30%。
在该种可行的实现方式中,服务请求消息中还可以包括终端标识,在服务控制器确定得到目标服务实例后,服务控制器确定并存储终端标识、目标服务组件和目标服务实例之间的第一对应关系。
示例性的,在服务控制器接收到服务类型为触发消息的服务请求消息1后,获取服务请求消息1中包括的消息标识对应的目标服务组件为服务组件1,服务组件1的包括3个服务实例,分别记为服务实例1-服务实例3,假设服务实例1的当前空闲率为40%,服务实例2的当前空闲率为60%,服务实例3的当前空闲率为45%,则服务控制器将空闲率最大的服务实例2确定为目标服务实例。进一步的,服务控制器还可以获取服务请求消息1中包括的终端标识(终端1),并确定终端1、服务组件1、以及服务实例2之间的第一对应关系,并存储该对应关系。
另一种可行的实现方式:服务请求消息的类型为过程消息:
当服务请求消息的类型为过程消息时,服务请求消息还包括终端标识,服务控制器获取终端标识、服务组件和服务实例之间的第二对应关系,并根据第二对应关系、服务请求消息中的终端标识、以及目标服务组件,确定目标服务实例。
在该种可行的实现方式中,在服务控制器确定得到目标服务实例,并向目标服务实例发送了服务请求消息后,服务控制器判断网络服务是否结束,若判断结果为是,服务控制器在第二对应关系中,清除服务请求消息中的终端标识、目标服务组件、以及目标服务实例之间的对应关系。
可选的,可以通过如下方式判断网络服务是否结束:服务控制器判断在预设时长内是否接收到终端标识以及消息标识相同的过程消息,若是,则判断该网络服务结束。例如,假设用户为了获取网络服务1,向服务控制器发送的服务请求消息中包括的终端标识为终端1、消息标识为网络服务1,若服务控制器在向目标服务实例发送了一个网络服务消息后,在预设时长内(例如5分钟)未接收到包括终端1和网络服务1的服务请求消息,则确定该网络服务1结束。
示例性的,在服务控制器接收到服务类型为过程消息的服务请求消息2后,获取服务请求消息2中包括的消息标识对应的目标服务组件为服务组件1,再假设服务请求消息2中包括的终端标识为终端2;服务控制器获取其内部存储的终端标识、服务组件和服务实例之间的第二对应关系,并根据终端标识(终端2)和服务组件(服务组件1),在第二对应关系中确定与终端2和服务组件1对应的服务实例为目标服务实例。
在上述两种可行的实现方式中,可选的,为了便于服务控制器对服务请求消息类型的识别,可以在服务请求消息中包括服务请求消息的类型。
在本发明实施例中,在一次网络服务中,用户在与服务实例进行的任意一次消息交互,服务实例均会产生用户在本次网络服务中的数据,且后续的消息交互中可能会使用到本次网络服务中前边消息交互中产生的数据。例如,在服务实例1向用户1提供网络服务1的过程中,服务实例1需要与用户1进行5次信息交互才能完成网络服务1,服务实例1在与用户1进行的每一次信息交互均会产生数据,服务实例1在与用户1进行第二次信息交互时,可能会使用到服务实例1与用户1进行第一次信息交互时产生的数据。
在本实施例中,根据服务请求消息类型的不同,服务控制器采用不同的方式,在目标服务组件的至少一个服务实例中确定目标服务实例,这样可以保证在一次网络服务的过程中,由同一个服务实例向同一用户提供网络服务,避免了在一次网络服务过程中,多个服务实例向同一用户提供网络服务,由
于数据丢失而导致无法向用户提供正确的网络服务的问题。
下面,通过具体示例,对本发明实施例所示的网络服务实现方法进行详细说明。
示例性的,假设用户需要从通信***中获取网络服务1,其中,用户需要与网络服务1对应的服务组件进行5次信息交互才能获取得到网络服务1。
在第一次信息交互过程中,用户1通过终端1向服务控制器发送服务请求消息1,该服务请求消息1中包括消息标识(网络服务1)、终端标识(终端1)。
当服务控制器接收到服务请求消息1后,根据服务请求消息1中的消息类型,确定该服务请求消息1为触发消息,服务控制器根据消息标识与服务组件的对应关系、以及网络服务1,确定网络服务1对应的目标服务组件为服务组件1,并获取服务组件1的3个服务实例,分别记为服务实例1-服务实例3,并获取服务实例1-服务实例3的空闲率,假设服务实例1的空闲率为50%,服务实例2的空闲率为30%,服务实例3的空闲率为60%,则服务控制器将空闲率最高的服务实例3确定为目标服务实例。
在服务控制器确定得到目标服务实例(服务实例3)后,向服务实例3发送服务请求消息1,由服务实例3对服务请求消息1进行处理。服务控制器记录并保存终端1、网络服务1、以及服务实例3之间的第一对应关系。
在第二次信息交互过程中,用户1通过终端1向服务控制器发送服务请求消息2,该服务请求消息2中包括消息标识(网络服务1)、终端标识(终端1)、以及消息类型(过程消息)。
当服务控制器接收到服务请求消息2后,根据服务请求消息2中的消息类型,确定该服务请求消息2为过程消息,服务控制器根据保存的终端1、网络服务1、以及服务实例3之间的第一对应关系,获取终端1和网络服务1对应的目标服务实例(服务实例3),并向服务实例3发送服务请求消息2,由服务实例3对服务请求消息2进行处理。服务控制器判断网络服务1没有结束,则不对第一对应关系进行删除。
需要说明的是,第三次至第五次信息交互过程中与第二次信息交互过程类似,此处不再进行赘述。
在执行完第五次信息交互过程后,服务控制器判断网络服务1结束,则
删除第一对应关系。
图5为本发明提供的服务控制器的结构示意图一,该服务控制器应用于通信***,通信***包括该服务控制器和至少一个服务组件,一个服务组件对应一种网络服务,各服务组件包括至少一个服务实例,请参照图5,该服务控制器包括:
接收模块501,用于接收服务请求消息,服务请求消息包括消息标识;
确定模块502,用于根据服务请求消息,确定消息标识对应的目标服务组件,并在目标服务组件的至少一个服务实例中确定目标服务实例;
发送模块503,用于向目标服务实例发送服务请求消息,以使目标服务实例对服务请求消息进行处理。
在实际应用过程中,当服务请求消息的类型为触发消息时,触发消息为触发网络服务的消息,确定模块502具体可以用于:
将至少一个服务实例中的任意一个服务实例确定为目标服务实例;或者,
获取至少一个服务实例中各服务实例的空闲率,将空闲率最大的服务实例确定为目标服务实例。
图6为本发明提供的服务控制器的结构示意图二,在图5所示实施例的基础上,请参照图6,服务控制器还可以包括存储模块504,其中,
确定模块502还可以用于,在发送模块503向目标服务实例发送服务请求消息之后,确定终端标识、目标服务组件和目标服务实例之间的第一对应关系,其中,服务请求消息还包括终端标识,
存储模块504用于,存储终端标识、目标服务组件和目标服务实例之间的第一对应关系。
在实际应用过程中,当服务请求消息的类型为过程消息时,过程消息为用户在发送触发消息之后发送的、用于获取网络服务的消息,服务请求消息还包括终端标识,确定模块502具体还可以用于:
获取终端标识、服务组件和服务实例之间的第二对应关系;
根据第二对应关系、服务请求消息中的终端标识、以及目标服务组件,确定目标服务实例。
进一步的,服务控制器还可以包括判断模块505和清除模块506,其中,
判断模块505用于,在发送模块向目标服务实例发送服务请求消息之后,
判断网络服务是否结束;
清除模块506用于,在判断模块判断网络服务结束时,在第二对应关系中,清除服务请求消息中的终端标识、目标服务组件、以及目标服务实例之间的对应关系。
可选的,发送模块503具体可以用于:
获取目标服务实例的网络地址,网络地址包括互联网协议IP地址、媒体访问控制MAC地址以及端口号中的至少一种;
根据网络地址,向目标服务实例发送服务请求消息。
本发明实施例所述的服务控制器可以执行上述方法实施例所示的技术方案,其实现原理以及有益效果类似,此处不再进行赘述。
图7为本发明实施例提供的服务控制器的硬件结构示意图,请参见图7,该服务控制器包括处理器701、接收端口702、发送端口703、通信总线704以及存储器705。其中,通信总线704用于实现元件之间的通信连接,存储器705中可以存储各种程序,处理器701通过执行存储器705中存储的程序,完成各种处理功能以及实现本实施例的方法步骤,具体的:
处理器701通过接收端口702接收服务请求消息,服务请求消息包括消息标识;
处理器701根据服务请求消息,确定消息标识对应的目标服务组件,并在目标服务组件的至少一个服务实例中确定目标服务实例;
处理器701通过发送端口703向目标服务实例发送服务请求消息,以使目标服务实例对服务请求消息进行处理。
在实际应用过程中,当服务请求消息的类型为触发消息时,处理器701可以通过如下可行的实现方式在至少一个服务实例中确定目标服务实例,具体的:
将至少一个服务实例中的任意一个服务实例确定为目标服务实例;或者,
获取至少一个服务实例中各服务实例的空闲率,将空闲率最大的服务实例确定为目标服务实例。
在实际应用过程中,处理器701在通过发送端口703向目标服务实例发送服务请求消息之后,还确定终端标识、目标服务组件和目标服务实例之间的第一对应关系,其中,服务请求消息还包括终端标识,
处理器701将存储终端标识、目标服务组件和目标服务实例之间的第一对应关系存储中存储器705中。
在实际应用过程中,当服务请求消息的类型为过程消息时,处理器701可以通过如下可行的实现方式在至少一个服务实例中确定目标服务实例,具体的:
获取终端标识、服务组件和服务实例之间的第二对应关系;
根据第二对应关系、服务请求消息中的终端标识、以及目标服务组件,确定目标服务实例。
进一步的,在处理器701通过发送端口703向目标服务实例发送服务请求消息之后,还判断网络服务是否结束;
当处理器701判断网络服务结束时,在第二对应关系中,清除服务请求消息中的终端标识、目标服务组件、以及目标服务实例之间的对应关系。
可选的,处理器701可以通过如下可行的实现方式,向目标服务实例发送服务请求消息,具体的:处理器701获取目标服务实例的网络地址,并根据网络地址,向目标服务实例发送服务请求消息,其中,网络地址包括互联网协议IP地址、媒体访问控制MAC地址以及端口号中的至少一种。
本发明实施例所述的服务控制器可以执行上述方法实施例所示的技术方案,其实现原理以及有益效果类似,此处不再进行赘述。
本领域普通技术人员可以理解:实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成,前述的程序可以存储于一计算机可读取存储介质中,该程序在执行时,执行包括上述方法实施例的步骤;而前述的存储介质包括:ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是:以上各实施例仅用以说明本发明的技术方案,而非对其限制;尽管参照前述各实施例对本发明进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分或者全部技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。
Claims (22)
- 一种网络服务实现方法,其特征在于,应用于通信***,所述通信***包括服务控制器和至少一个服务组件,一个所述服务组件对应一种网络服务,各所述服务组件包括至少一个服务实例,所述方法包括:所述服务控制器接收服务请求消息,所述服务请求消息包括消息标识;所述服务控制器根据所述服务请求消息,确定所述消息标识对应的目标服务组件;所述服务控制器在所述目标服务组件的至少一个服务实例中确定目标服务实例,并向所述目标服务实例发送所述服务请求消息,以使所述目标服务实例对所述服务请求消息进行处理。
- 根据权利要求1所述的方法,其特征在于,所述服务请求消息的类型为触发消息,所述触发消息为触发所述网络服务的消息;所述服务控制器在所述服务组件的至少一个服务实例中确定目标服务实例,包括:所述服务控制器将所述至少一个服务实例中的任意一个服务实例确定为所述目标服务实例;或者,所述服务控制器获取所述至少一个服务实例中各所述服务实例的空闲率,将空闲率最大的服务实例确定为所述目标服务实例。
- 根据权利要求2所述的方法,其特征在于,所述服务请求消息还包括终端标识,所述服务控制器向所述目标服务实例发送所述服务请求消息之后,还包括:所述服务控制器确定并存储所述终端标识、所述目标服务组件和所述目标服务实例之间的第一对应关系。
- 根据权利要求1所述的方法,其特征在于,所述服务请求消息的类型为过程消息,所述过程消息为用户在发送触发消息之后发送的、用于获取网络服务的消息,所述服务请求消息还包括终端标识,所述服务控制器在所述服务组件的至少一个服务实例中确定目标服务实例,包括:所述服务控制器获取终端标识、服务组件和服务实例之间的第二对应关系;所述服务控制器根据所述第二对应关系、所述服务请求消息中的终端标识、以及所述目标服务组件,确定目标服务实例。
- 根据权利要求4所述的方法,其特征在于,所述服务控制器向所述目标服务实例发送所述服务请求消息之后,还包括:所述服务控制器判断所述网络服务是否结束;若判断结果为是,所述服务控制器在所述第二对应关系中,清除所述服务请求消息中的终端标识、所述目标服务组件、以及所述目标服务实例之间的对应关系。
- 根据权利要求1-5任一项所述的方法,其特征在于,所述服务控制器向所述目标服务实例发送所述服务请求消息,包括:所述服务控制器获取所述目标服务实例的网络地址,所述网络地址包括互联网协议IP地址、媒体访问控制MAC地址以及端口号中的至少一种;所述服务控制器根据所述网络地址,向所述目标服务实例发送所述服务请求消息。
- 一种服务控制器,其特征在于,所述服务控制器包括:接收模块,用于接收服务请求消息,所述服务请求消息包括消息标识;确定模块,用于根据所述服务请求消息,确定所述消息标识对应的目标服务组件,并在所述目标服务组件的至少一个服务实例中确定目标服务实例;发送模块,用于向所述目标服务实例发送所述服务请求消息,以使所述目标服务实例对所述服务请求消息进行处理。
- 根据权利要求7所述的服务控制器,其特征在于,所述服务请求消息的类型为触发消息,所述触发消息为触发所述网络服务的消息;所述确定模块具体用于:将所述至少一个服务实例中的任意一个服务实例确定为所述目标服务实例;或者,获取所述至少一个服务实例中各所述服务实例的空闲率,将空闲率最大的服务实例确定为所述目标服务实例。
- 根据权利要求7所述的服务控制器,其特征在于,所述服务控制器还包括存储模块,其中,所述确定模块还用于,在所述发送模块向所述目标服务实例发送所述服务请求消息之后,确定所述终端标识、所述目标服务组件和所述目标服务实例之间的第一对应关系,其中,所述服务请求消息还包括终端标识,所述存储模块用于,存储所述终端标识、所述目标服务组件和所述目标服务实例之间的第一对应关系。
- 根据权利要求7所述的服务控制器,其特征在于,所述服务请求消息的类型为过程消息,所述过程消息为用户在发送触发消息之后发送的、用于获取网络服务的消息,所述服务请求消息还包括终端标识,所述确定模块具体还用于:获取终端标识、服务组件和服务实例之间的第二对应关系;根据所述第二对应关系、所述服务请求消息中的终端标识、以及所述目标服务组件,确定目标服务实例。
- 根据权利要求10所述的服务控制器,其特征在于,所述服务控制器还包括判断模块和清除模块,其中,所述判断模块用于,在所述发送模块向所述目标服务实例发送所述服务请求消息之后,判断所述网络服务是否结束;所述清除模块用于,在所述判断模块判断所述网络服务结束时,在所述第二对应关系中,清除所述服务请求消息中的终端标识、所述目标服务组件、以及所述目标服务实例之间的对应关系。
- 根据权利要求7-11任一项所述的服务控制器,其特征在于,所述发送模块具体用于:获取所述目标服务实例的网络地址,所述网络地址包括互联网协议IP地址、媒体访问控制MAC地址以及端口号中的至少一种;根据所述网络地址,向所述目标服务实例发送所述服务请求消息。
- 一种服务控制器,其特征在于,所述服务控制器包括处理器、发送端口以及接收端口,其中,所述处理器用于,通过所述接收端口接收服务请求消息,所述服务请求消息包括消息标识;所述处理器还用于,根据所述服务请求消息,确定所述消息标识对应的目标服务组件,并在所述目标服务组件的至少一个服务实例中确定目标服务实例;所述处理器还用于,通过所述发送端口向所述目标服务实例发送所述服务请求消息,以使所述目标服务实例对所述服务请求消息进行处理。
- 根据权利要求13所述的服务控制器,其特征在于,所述服务请求消息的类型为触发消息,所述触发消息为触发所述网络服务的消息;所述处理器具体还用于:将所述至少一个服务实例中的任意一个服务实例确定为所述目标服务实例;或者,获取所述至少一个服务实例中各所述服务实例的空闲率,将空闲率最大的服务实例确定为所述目标服务实例。
- 根据权利要求13所述的服务控制器,其特征在于,所述处理器还用于,在通过所述发送端口向所述目标服务实例发送所述服务请求消息之后,确定所述终端标识、所述目标服务组件和所述目标服务实例之间的第一对应关系,其中,所述服务请求消息还包括终端标识,所述处理器还用于,存储所述终端标识、所述目标服务组件和所述目标服务实例之间的第一对应关系。
- 根据权利要求13所述的服务控制器,其特征在于,所述服务请求消息的类型为过程消息,所述过程消息为用户在发送触发消息之后发送的、用于获取网络服务的消息,所述服务请求消息还包括终端标识,所述处理器还用于:获取终端标识、服务组件和服务实例之间的第二对应关系;根据所述第二对应关系、所述服务请求消息中的终端标识、以及所述目标服务组件,确定目标服务实例。
- 根据权利要求16所述的服务控制器,其特征在于,所述处理器还用于,在所述处理器通过所述发送端口向所述目标服务实例发送所述服务请求消息之后,判断所述网络服务是否结束;所述处理器还用于,在所述处理器判断所述网络服务结束时,在所述第二对应关系中,清除所述服务请求消息中的终端标识、所述目标服务组件、以及所述目标服务实例之间的对应关系。
- 根据权利要求13-17任一项所述的服务控制器,其特征在于,所述处理器具体还用于:获取所述目标服务实例的网络地址,所述网络地址包括互联网协议IP地址、媒体访问控制MAC地址以及端口号中的至少一种;根据所述网络地址,通过所述发送端口向所述目标服务实例发送所述服务请求消息。
- 一种通信***,其特征在于,包括服务控制器和至少一个服务组件,一个所述服务组件对应一种网络服务,各所述服务组件包括至少一个服务实例,其中,所述服务控制器用于,接收包括消息标识的服务请求消息,确定所述消息标识对应的目标服务组件,在所述目标服务组件的至少一个服务实例中确定目标服务实例,并向所述目标服务实例发送所述服务请求消息;所述服务实例用于,接收所述服务控制器发送的服务请求消息,并对所述服务请求消息进行处理。
- 根据权利要求19所述的***,其特征在于,所述***还包括服务部署中心和服务注册中心,其中,所述服务部署中心用于,确定所述通信***中服务组件与消息标识的对应关系,并向所述服务注册中心发送所述对应关系;所述服务注册中心用于,接收并存储所述服务部署中心发送的所述对应关系;相应的,所述服务控制器用于,接收包括消息标识的服务请求消息,在所述服务注册中心中获取所述对应关系,并根据所述对应关系确定所述消息标识对应的目标服务组件,在所述目标服务组件的至少一个服务实例中确定目标服务实例,并向所述目标服务实例发送所述服务请求消息。
- 根据权利要求20所述的***,其特征在于,所述服务部署中心还用于,获取所述通信***中各服务组件对应的服务需求,根据各所述服务组件对应的服务需求,在所述通信***中为各所述服务组件部署至少一个服务实例,并向所述服务注册中心发送各所述服务组件包括的服务实例、及各所述服务实例的属性信息,所述属性信息包括所述服务实例的网络地址;所述服务注册中心还用于,接收并存储所述服务部署中心发送的各所述服务组件包括的服务实例、及各所述服务实例的属性信息;相应的,所述服务控制器还用于,接收包括消息标识的服务请求消息,在所述服务注册中心中获取所述对应关系,并根据所述对应关系确定所述消 息标识对应的目标服务组件,在所述服务注册中心中获取所述目标服务组件包括的至少一个服务实例,在所述至少一个服务实例中确定目标服务实例,并向所述目标服务实例发送所述服务请求消息。
- 根据权利要求19-21任一项所述的***,其特征在于,所述***还包括监控模块,其中,所述监控模块用于,获取所述通信***中的服务实例的工作状态,并在所述服务实例的工作状态为异常状态时,生成故障通知消息。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP16895780.1A EP3435615B1 (en) | 2016-03-28 | 2016-03-28 | Network service implementation method, service controller, and communication system |
PCT/CN2016/077465 WO2017165999A1 (zh) | 2016-03-28 | 2016-03-28 | 网络服务实现方法、服务控制器及通信*** |
CN201680083657.6A CN108781215B (zh) | 2016-03-28 | 2016-03-28 | 网络服务实现方法、服务控制器及通信*** |
US16/144,730 US20190036793A1 (en) | 2016-03-28 | 2018-09-27 | Network service implementation method, service controller, and communications system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2016/077465 WO2017165999A1 (zh) | 2016-03-28 | 2016-03-28 | 网络服务实现方法、服务控制器及通信*** |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/144,730 Continuation US20190036793A1 (en) | 2016-03-28 | 2018-09-27 | Network service implementation method, service controller, and communications system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017165999A1 true WO2017165999A1 (zh) | 2017-10-05 |
Family
ID=59963251
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2016/077465 WO2017165999A1 (zh) | 2016-03-28 | 2016-03-28 | 网络服务实现方法、服务控制器及通信*** |
Country Status (4)
Country | Link |
---|---|
US (1) | US20190036793A1 (zh) |
EP (1) | EP3435615B1 (zh) |
CN (1) | CN108781215B (zh) |
WO (1) | WO2017165999A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117041980A (zh) * | 2023-10-09 | 2023-11-10 | 之江实验室 | 一种网元管理方法、装置、存储介质及电子设备 |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111124661B (zh) * | 2019-10-11 | 2024-04-09 | 合肥非度信息技术有限公司 | 基于java线程池主动释放资源的短信发送方法及*** |
CN115248730A (zh) * | 2021-04-27 | 2022-10-28 | 华为云计算技术有限公司 | 提供服务的方法及装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1537392A (zh) * | 2001-05-24 | 2004-10-13 | �Ҵ���˾ | 用于集成网络服务提供者的服务应用程序构架 |
CN101359999A (zh) * | 2007-07-30 | 2009-02-04 | 中兴通讯股份有限公司 | 一种网元数据同步的方法及装置 |
CN102037702A (zh) * | 2008-05-20 | 2011-04-27 | 艾利森电话股份有限公司 | 电信网络内的组合服务提供 |
CN105306418A (zh) * | 2014-06-24 | 2016-02-03 | 博雅网络游戏开发(深圳)有限公司 | 多应用程序共享通信连接的方法和*** |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8868779B2 (en) * | 2004-06-15 | 2014-10-21 | Accenture Global Services Limited | Method and apparatus to accomplish peer-to-peer application data routing between service consumers and service providers within a service oriented architecture |
BRPI0517521B1 (pt) * | 2004-10-26 | 2019-04-09 | Telecom Italia S.P.A. | Método e sistema para autenticar um assinante de uma primeira rede para acessar um serviço de aplicação através de uma segunda rede |
US8239536B2 (en) * | 2007-03-30 | 2012-08-07 | Platform Computing Corporation | System for generic service management in a distributed and dynamic resource environment, providing constant service access to users |
US8260940B1 (en) * | 2007-06-29 | 2012-09-04 | Amazon Technologies, Inc. | Service request management |
US8825876B2 (en) * | 2008-07-17 | 2014-09-02 | Qualcomm Incorporated | Apparatus and method for mobile virtual network operator (MVNO) hosting and pricing |
CN101771563B (zh) * | 2008-12-30 | 2012-07-25 | 北大方正集团有限公司 | 网络服务程序的监控方法 |
TWI604745B (zh) * | 2012-02-29 | 2017-11-01 | 內數位專利控股公司 | 透過虛擬網路無縫傳遞服務方法及裝置 |
TW201807961A (zh) * | 2012-09-27 | 2018-03-01 | 內數位專利控股公司 | 在噓擬網路中端對端架構、api框架、發現及存取 |
US9398100B2 (en) * | 2012-12-29 | 2016-07-19 | Ricoh Company, Ltd. | Managing access of network services |
US9134962B1 (en) * | 2013-03-15 | 2015-09-15 | Sanctum Solutions, Inc. | Interactive content development |
EP2782316A1 (en) * | 2013-03-18 | 2014-09-24 | Koninklijke KPN N.V. | Localizing and placement of network node functions in a network |
EP2782317A1 (en) * | 2013-03-18 | 2014-09-24 | Koninklijke KPN N.V. | Redirecting a client device from a first gateway to a second gateway for accessing a network node function |
TWI516151B (zh) * | 2013-04-26 | 2016-01-01 | 緯創資通股份有限公司 | 通訊方法與通訊系統 |
US10114680B2 (en) * | 2013-05-08 | 2018-10-30 | Convida Wireless, Llc | Method and apparatus for the virtualization of resources using a virtualization broker and context information |
CN104602245B (zh) * | 2013-10-31 | 2019-10-22 | 索尼公司 | 增强邻近服务设备到设备发现资源分配的方法和网络设备 |
CN105379218B (zh) * | 2014-06-17 | 2018-09-07 | 华为技术有限公司 | 业务流的处理方法、装置及设备 |
CN105282195A (zh) * | 2014-06-27 | 2016-01-27 | 中兴通讯股份有限公司 | 网络服务提供、策略规则评估、服务组件选择方法及装置 |
US9763060B2 (en) * | 2014-11-11 | 2017-09-12 | Alcatel Lucent | Streaming unicast services to multiple user equipment |
EP3266151A4 (en) * | 2015-03-03 | 2018-10-31 | Calgary Scientific Inc. | Methods and systems for requesting access to limited service instances |
US10277687B2 (en) * | 2015-11-16 | 2019-04-30 | At&T Intellectual Property I, L.P. | Master service orchestration of virtual networking functions |
-
2016
- 2016-03-28 EP EP16895780.1A patent/EP3435615B1/en active Active
- 2016-03-28 WO PCT/CN2016/077465 patent/WO2017165999A1/zh active Application Filing
- 2016-03-28 CN CN201680083657.6A patent/CN108781215B/zh active Active
-
2018
- 2018-09-27 US US16/144,730 patent/US20190036793A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1537392A (zh) * | 2001-05-24 | 2004-10-13 | �Ҵ���˾ | 用于集成网络服务提供者的服务应用程序构架 |
CN101359999A (zh) * | 2007-07-30 | 2009-02-04 | 中兴通讯股份有限公司 | 一种网元数据同步的方法及装置 |
CN102037702A (zh) * | 2008-05-20 | 2011-04-27 | 艾利森电话股份有限公司 | 电信网络内的组合服务提供 |
CN105306418A (zh) * | 2014-06-24 | 2016-02-03 | 博雅网络游戏开发(深圳)有限公司 | 多应用程序共享通信连接的方法和*** |
Non-Patent Citations (1)
Title |
---|
See also references of EP3435615A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117041980A (zh) * | 2023-10-09 | 2023-11-10 | 之江实验室 | 一种网元管理方法、装置、存储介质及电子设备 |
CN117041980B (zh) * | 2023-10-09 | 2024-01-09 | 之江实验室 | 一种网元管理方法、装置、存储介质及电子设备 |
Also Published As
Publication number | Publication date |
---|---|
US20190036793A1 (en) | 2019-01-31 |
EP3435615A4 (en) | 2019-03-20 |
EP3435615B1 (en) | 2021-04-14 |
EP3435615A1 (en) | 2019-01-30 |
CN108781215B (zh) | 2021-02-12 |
CN108781215A (zh) | 2018-11-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11251981B2 (en) | Communication method and apparatus | |
CN105991412B (zh) | 消息推送方法及装置 | |
US20150382132A1 (en) | Method and Device for Monitoring | |
US11233694B2 (en) | Method and device for processing communication path | |
CN108712485A (zh) | 一种物联网设备的资源订阅方法和装置 | |
CN106330742B (zh) | 一种流量控制的方法及网络控制器 | |
CN109983736A (zh) | 一种nf组件异常的处理方法、设备及*** | |
KR20140052397A (ko) | 이동 통신 시스템에서 가상 머신 관리 장치 및 방법 | |
CN109769029B (zh) | 基于用电信息采集***的通信连接方法及终端设备 | |
WO2020034827A1 (zh) | 网络切片创建方法、装置、设备及存储介质 | |
WO2017165999A1 (zh) | 网络服务实现方法、服务控制器及通信*** | |
CN108055156B (zh) | Ap管理方法及装置 | |
WO2010017659A1 (zh) | 一种在通信网络中实现心跳机制的方法和装置 | |
JP2010251838A (ja) | アクセスゲートウェイ装置及びアクセスゲートウェイ装置におけるセッション情報複製方法 | |
WO2017000625A1 (zh) | 动态主机配置协议dhcp服务器管理方法及装置 | |
US20210328887A1 (en) | Method for performing task processing on common service entity, common service entity, apparatus and medium for task processing | |
JP5679616B2 (ja) | 報告を関連付けるための方法および装置 | |
CN108391325B (zh) | 管理无线连接的方法、装置及终端 | |
WO2013159492A1 (zh) | 信息上报与下载的方法及*** | |
US20180081746A1 (en) | Application message processing system, method, and application device | |
CN110597631B (zh) | 资源管理方法、监控服务器、代理服务器以及存储介质 | |
WO2017101028A1 (zh) | 数据传输方法、m2m服务器、pgw、sgw及服务网络节点 | |
CN114489730A (zh) | 一种远程升级方法及其终端设备、计算机可读存储介质 | |
EP2282448A1 (en) | Technique for controlling device management response messages | |
EP3038290A1 (en) | Method and device for application management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2016895780 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2016895780 Country of ref document: EP Effective date: 20181023 |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16895780 Country of ref document: EP Kind code of ref document: A1 |