CN101977220B - Method and device for matching functional modules with different versions among function subsystems - Google Patents
Method and device for matching functional modules with different versions among function subsystems Download PDFInfo
- Publication number
- CN101977220B CN101977220B CN201010517890.5A CN201010517890A CN101977220B CN 101977220 B CN101977220 B CN 101977220B CN 201010517890 A CN201010517890 A CN 201010517890A CN 101977220 B CN101977220 B CN 101977220B
- Authority
- CN
- China
- Prior art keywords
- version information
- functional
- service request
- function
- module
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 73
- 238000012545 processing Methods 0.000 claims abstract description 67
- 230000004044 response Effects 0.000 claims abstract description 43
- 230000008569 process Effects 0.000 claims abstract description 29
- 230000003993 interaction Effects 0.000 claims abstract description 9
- 230000000977 initiatory effect Effects 0.000 claims description 21
- 238000010295 mobile communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 230000006872 improvement Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a method and a device for matching functional modules with different versions among function subsystems. The method is characterized in that the functional modules in the function subsystem of a distributed system acquire version information of the other functional modules in the function subsystem and/or version information of the functional modules in the other function subsystems in the distributed system; and when the functional modules in different function subsystems are subject to service interaction, a service request is sent to the functional modules matched with the version information of the service request for processing according to the version information of the initiated or received service request. In the invention, when the functional modules in different function subsystems in the distributed system have inconsistent versions, the information can be automatically sent to the functional modules which can process the version information instead of neglecting unsupported services in the information so as to ensure success rate, or the versions do not support response information is returned, thus ensuring service processing completeness.
Description
Technical Field
The present invention relates to the field of mobile communications technologies, and in particular, to a method and an apparatus for matching different versions of function modules between function subsystems.
Background
With the rapid development of mobile communication networks, the number of mobile communication subscribers is also increasing rapidly, and the development of the HLR (Home Location Register) system in the mobile communication network towards a large-capacity and distributed direction has become a development trend of the future mobile communication networks.
Since the distributed HLR system has much higher requirements in terms of user quantity and processing capacity than the conventional HLR system, in the distributed HLR system, the functional subsystem with the same function usually includes a plurality of processing modules, and these processing modules are usually physically separated and geographically distributed at different sites of the distributed HLR, so as to meet the requirements of high performance and high reliability of the distributed HLR. The functional subsystems in the HLR mainly include FE (front end), BE (back end) and Provisioning (acceptance) subsystems. Hereinafter, FE, BE, and Provisioning subsystems are abstractly described as functional subsystems. A plurality of processing modules with the same function included in the same functional subsystem are abstractly described as functional modules.
However, since the different sites of the distributed HLR are geographically relatively independent, the distributed HLR is usually upgraded site by site at different time stages. As shown in fig. 1, the functional module 1 of the functional subsystem 1 and the functional module 1 of the functional subsystem 2 under the site 2 are upgraded to the version 2, while the functional module 1 of the functional subsystem 1 under the site 1 and the functional module 1 of the functional subsystem 2 are not upgraded and are still the version 1, before the functional subsystems of all sites of the distributed HLR are upgraded to the consistent version, there is a case that the functional modules of different functional subsystems have mutual access, in fig. 1, the access numbered 1 belongs to the access between the functional modules of the same version, and the access numbered 2 belongs to the access between the functional modules of different versions, and such mutual access between different versions includes the access of the functional module of the lower version to the functional module of the higher version (the functional module 1 of the version 1 of the functional subsystem 2 under the site 1 in fig. 1 accesses the functional module 1 of the version 2 of the functional subsystem 1 under the site 2), and the high-version function module accesses the low-version function module (the function module 1 of version 2 of the function subsystem 2 under the site 2 in fig. 1 accesses the function module 1 of version 1 of the function subsystem 1 under the site 1). For this situation, a common implementation manner considers compatibility processing for each version of each functional subsystem, but the compatibility processing is usually expressed as high-version compatible low-version, and low-version compatible high-version is difficult to implement (either modifying codes of the low-version or adding special processing when the high-version accesses the low-version), which often results in sacrificing some incompatible services for ensuring success rate when functional modules of different versions access each other, or sacrificing some success rate when incompatible for ensuring service integrity.
Disclosure of Invention
The technical problem to be solved by the invention is to provide a method and a device for matching different versions of function modules among function subsystems, which can ensure the integrity of system service processing to the maximum extent when the subsystems of different versions interact.
In order to solve the above technical problem, the present invention provides a method for matching different versions of function modules between function subsystems,
the method comprises the steps that a functional module in a functional subsystem of a distributed system obtains version information of other functional modules in the functional subsystem and/or version information of the functional modules in other functional subsystems in the distributed system;
when service interaction is carried out among the functional modules of different functional subsystems, the service request is sent to the functional module matched with the version information of the service request for processing according to the version information of the initiated or received service request.
Further, the method specifically comprises:
the method comprises the steps that a functional module in a functional subsystem of the distributed system obtains version information of each functional module in other functional subsystems of the distributed system;
when a functional module in the functional subsystem initiates a service request to other functional subsystems, the service request is sent to the functional module matched with the version information of the service request in the other functional subsystems for processing according to the acquired version information of each functional module in the other functional subsystems.
Further, the method further comprises:
the method comprises the steps that a functional module in a functional subsystem of the distributed system obtains version information of other functional modules in the functional subsystem;
after the service request is initiated, if the version information of the target function module of the service request is changed in the sending process of the service request, and the changed version information is lower than the version information of the service request, the target function module of the service request forwards the service request to other function modules matched with the version information of the service request in the function subsystem for processing according to the acquired version information of other function modules in the function subsystem.
Further, the method specifically comprises:
the method comprises the steps that a functional module in a functional subsystem of the distributed system obtains version information of other functional modules in the functional subsystem;
when a functional module in the functional subsystem receives a service request, if the version information of the functional module is lower than the version information of the service request, the service request is forwarded to other functional modules matched with the version information of the service request in the functional subsystem for processing according to the acquired version information of other functional modules in the functional subsystem.
Further, the functional module matched with the version information of the service request refers to:
and the version information is consistent with or higher than that of the service request.
Further, the function module acquires the version information by:
the network management centrally configures the version information of each functional module in each functional subsystem, and the functional module acquires the version information through the network management; or,
the functional module acquires the version information from other functional modules regularly through internal information, and broadcasts and notifies other functional modules when the version information of each functional module changes; or,
the functional modules of each functional subsystem report the version information of the functional module to the monitoring center at regular time, and when the version information of the functional module changes, the version information is actively reported to the monitoring center, and the monitoring center broadcasts the version information to inform all the functional modules.
Further, the method further comprises:
when the initiating function module and the forwarding function module of the service request initiate the service request or forward the received service request, the self address information is superposed in the initiated or forwarded service request;
after the functional module matched with the version information of the service request receives and processes the service request, a response message containing the superposed address information is returned to the last forwarding functional module according to the superposed address information in the service request; and each forwarding functional module removes the address information of the forwarding functional module according to the received response message, and then returns the response message to the previous forwarding functional module until the response message is forwarded to the service request initiating functional module.
Further, the method further comprises:
when the initiating function module and the forwarding function module of the service request initiate the service request or forward the received service request, the initiated or forwarded service request contains the address information of the initiating function module of the service request;
and after the functional module matched with the version information of the service request receives and processes the service request, returning a response message to the initiating functional module according to the address information of the initiating functional module contained in the service request.
The invention also provides a matching device of different versions of function modules among function subsystems, which is applied to the function modules in the function subsystems of a distributed system, and the device comprises:
the version information acquisition unit is used for acquiring the version information of other functional modules in the functional subsystem and/or the version information of the functional modules in other functional subsystems in the distributed system;
and the version information matching unit is used for sending the service request to the functional module matched with the version information of the service request for processing according to the version information of the initiated or received service request when service interaction is carried out between the functional module and the functional modules of other functional subsystems.
In addition, the version information acquiring unit is further configured to acquire version information of each functional module in other functional subsystems of the distributed system;
the version information matching unit is further used for sending the service request to the functional module matched with the version information of the service request in other functional subsystems for processing according to the acquired version information of each functional module in the other functional subsystems when the service request is sent to the other functional subsystems;
the functional module matched with the version information of the service request refers to a functional module of which the version information is consistent with or higher than the version information of the service request.
In addition, the version information acquiring unit is further configured to acquire version information of each other functional module in the functional subsystem;
the version information matching unit is further configured to, when a service request is received, if the version information of the current functional module is lower than the version information of the service request, forward the service request to other functional modules in the current functional subsystem, which are matched with the version information of the service request, for processing according to the acquired version information of each other functional module in the current functional subsystem.
Furthermore, the version information acquisition unit is further configured to acquire the version information by:
the network management centrally configures the version information of each functional module in each functional subsystem, and the version information acquisition unit acquires the version information through the network management; or,
the version information acquisition unit acquires the version information from other functional modules periodically through internal information, and broadcasts and notifies other functional modules when the version information of each functional module changes; or,
the version information acquisition unit reports the version information of the function module to the monitoring center at regular time, and actively reports the version information to the monitoring center when the version information of the function module changes, and the monitoring center broadcasts the version information to inform all the function modules.
Further, the apparatus further comprises a response message forwarding unit,
the version information matching unit is also used for superposing the address information of the version information matching unit in the initiated or forwarded service request when the service request is initiated or the received service request is forwarded;
the response message forwarding unit is used for returning or forwarding the response message of the service request according to the superposed address information, and removing the address information of the superposed address information in the returned or forwarded response message.
Further, the apparatus further comprises a response message forwarding unit,
the version information matching unit is also used for including the address information of the service module initiating the service request in the initiated or forwarded service request when the service request is initiated or the received service request is forwarded;
the response message forwarding unit is used for returning a response message to the initiating function module initiating the service request according to the address information contained in the service request.
Compared with the prior art, the invention has at least the following beneficial effects:
1. the invention can make the message automatically send to the function module which can process the version message to process when the versions of the function modules of different function subsystems in the distributed HLR are not consistent, instead of neglecting the unsupported service in the message to ensure the success rate or returning the version unsupported response to ensure the integrity of the service processing;
2. by adopting the technical scheme of the invention, the design of compatibility among different versions during system design can be simplified, particularly the design when a functional module of a low version processes messages of a high version;
3. in addition, by adopting the technical scheme of the invention, the version information of each functional module in the system can be managed in a centralized manner, and the maintainability of the system is improved.
Drawings
FIG. 1 is a problem of interaction of different versions of functional modules faced by functional modules of various functional subsystems in the prior art;
FIG. 2 is a schematic diagram of a first embodiment of a method according to the present invention;
FIG. 3 is a schematic diagram of a second embodiment of a method according to the present invention;
FIG. 4 is a schematic view of a third embodiment of the method according to the invention;
FIG. 5 is a diagram of a fourth embodiment of a method according to the present invention;
FIG. 6 is a schematic diagram of a fifth embodiment of the method according to the present invention.
Detailed Description
In the distributed HLR system, a plurality of functional subsystems need to generate information interaction. Due to the distributed nature, when upgrading the distributed HLR, it is usually upgraded in stages, so that there are several function modules with different versions in each function subsystem, and these function modules have similar functions but different service support capabilities. In this way, before all the functional modules of the functional subsystems of the distributed HLR are upgraded to the latest version, mutual access between the sub-modules of the subsystems of different versions is inevitable, and in this case, it is likely that the processing of the system fails due to insufficient processing capability of the modules of the high version accessing the modules of the low version.
In view of the foregoing problems in the prior art, an object of the present invention is to provide a method for compatible processing of different versions of function modules between function subsystems, the core idea of the method is that, according to the obtained version information of each function module in the local function subsystem and/or other function subsystems in a distributed network, when a service request is initiated to a function module of another function subsystem or a service request is received, the service request is sent to a function module with a version capability matched with that of the function module, so as to process the service request, thereby ensuring the integrity of the system service processing to the maximum extent when the function subsystems of different versions interact.
Based on the core thought, the invention provides a method for matching different versions of function modules among function subsystems, which specifically adopts the following technical scheme:
the method comprises the steps that a functional module in a functional subsystem of a distributed system obtains version information of other functional modules in the functional subsystem and/or version information of the functional modules in other functional subsystems in the distributed system;
when service interaction is carried out among the functional modules of different functional subsystems, the service request is sent to the functional module matched with the version information of the service request for processing according to the version information of the initiated or received service request.
Further, the method specifically comprises:
the method comprises the steps that a functional module in a functional subsystem of the distributed system obtains version information of each functional module in other functional subsystems of the distributed system;
when a functional module in the functional subsystem initiates a service request to other functional subsystems, the service request is sent to the functional module matched with the version information of the service request in the other functional subsystems for processing according to the acquired version information of each functional module in the other functional subsystems.
Further, the method further comprises:
the method comprises the steps that a functional module in a functional subsystem of the distributed system obtains version information of other functional modules in the functional subsystem;
and if the version information of the functional module in the other functional subsystems is changed after the functional module in the functional subsystem initiates the service request, and the changed version information is lower than the version information of the service request, forwarding the service request to other functional modules matched with the version information of the service request in the functional subsystem for processing according to the acquired version information of other functional modules in the functional subsystem.
Further, the method specifically comprises:
the method comprises the steps that a functional module in a functional subsystem of the distributed system obtains version information of other functional modules in the functional subsystem;
when a functional module in the functional subsystem receives a service request, if the version information is lower than that of the service request, the service request is forwarded to other functional modules matched with the version information of the service request in the functional subsystem for processing according to the acquired version information of other functional modules in the functional subsystem.
Further, the functional module matched with the version information of the service request refers to:
and the version information is consistent with or higher than that of the service request.
Further, the functional module of the functional subsystem obtains version information of each other functional module in the functional subsystem and/or version information of each functional module in each other functional subsystem in the distributed system by the following method:
1) configuring version information of each functional module in a network management set, wherein each functional module acquires the version information through the network management;
2) the functional modules inside the functional subsystems and among the functional subsystems regularly acquire the version information of other functional modules (specifically, the version information of other functional modules can be acquired through internally defined messages), and when the version information of a certain functional module changes, the other functional modules are notified in a broadcast manner;
the information of all other modules is not necessarily acquired first, and the two modes can be mutually supplemented, so that when the information is acquired at regular time, the time length setting of the timer may not be timely, and the point can be well compensated by the mode of broadcasting the notification after the change, so that the state switching is more timely.
3) And setting a centralized monitoring center, reporting the version information of the functional module to the monitoring center at regular time by the functional modules of the functional subsystems, actively reporting the version information to the monitoring center when the version information of a certain functional module is changed, and broadcasting and informing all the functional modules of the reported and changed version information by the monitoring center.
Further, the above-mentioned type 3 can be realized by the following two methods: firstly, each functional module is acquired from a monitoring center at regular time, and the monitoring center broadcasts a notice to all the functional modules when receiving the version information of a certain functional module; secondly, the monitoring center broadcasts the version information of each functional module to all the functional modules at regular time, and when the version information of a certain functional module changes, the monitoring center broadcasts a notice to all the functional modules.
When the above-mentioned manner 3 is adopted, for a plurality of sites of the distributed HLR, one monitoring center may be deployed at each site, and the monitoring center of each site is responsible for monitoring the version information of the function module of each function subsystem of the site, exchanging the version information with the monitoring centers of other sites, and actively broadcasting the version information to notify the other monitoring centers of the change of the version information of the function module of the site.
For the convenience of describing the present invention, the following detailed description will be made with reference to the accompanying drawings and specific embodiments.
Example one
In this embodiment, each functional module of each functional subsystem does not care about the version information of the functional module in other functional subsystems, but only care about the version information of other functional modules in the same functional subsystem, and the processing of the functional module of each functional subsystem when interacting with the functional module of other functional subsystems is specifically: when a certain function module a2 of the function subsystem a sends a message to a certain function module B1 of the function subsystem B, and B1 cannot process the request due to the lower version, B1 forwards the request to a function module B2 in the same function subsystem that has the capability of processing the request, after function module B2 processes the request, the processing result is returned to B1, and B1 returns the processing result to a 2.
Referring to fig. 2, the processing flow of the embodiment is specifically described as follows:
step 201, the function module a2 of version 2 sends a request to the function module B1 of version 1;
in step 202, function module B1 finds that its version is insufficient to handle the request from function module a2, function module B1 forwards the request to function module B2, which is capable of handling the request;
step 203, the function module B2 finds itself capable of processing the received request, processes the request, and returns the processing result to the function module B1;
in step 204, function Block B1 returns the results of the processing to function Block A2
In order to ensure that the function module B2 can return the response message to the function module a2 in the original route, the function module a2 adds information capable of identifying the address of the function module a2 to the request sent to the function module B1, and the function module B1 superimposes information capable of identifying the address of the function module a2 on the request forwarded to the function module B2 (superimposes the information on the address information of the function module a2 already existing in the message), that is, when each function module sends the request message to the next function module, the identifier capable of identifying the address information of the function module B is superimposed on the address information already in the message, so that the route information of all the function modules forwarding messages before is stored in the request message received by the last function module B2. Similarly, B2 returns a response message to B1 according to the address of the last function module in the routing information, where the message carries the routing information carried in the request message, B1 knows from the routing information that the response message should be returned to a2, B1 removes the address information of B1 in the routing information and then forwards the response message to a2, that is, each function module deletes the identifier capable of identifying its own address information from the routing information when sending the response message to the next function module. The request message and the response message can be distinguished by the event number or the identifier in the message body, so that each functional module can know whether the address information of the functional module needs to be added into the routing information or deleted.
Example two
In this embodiment, each functional module of each functional subsystem does not care about the version information of the functional module in other functional subsystems, but only care about the version information of other functional modules in the same functional subsystem, and the processing of the functional module of each functional subsystem when interacting with the functional module of other functional subsystems is specifically: when a certain function module a2 of the function subsystem a sends a message to a certain function module B1 of the function subsystem B, and B1 cannot process the request due to the lower version, B1 forwards the request to a function module B2 in the same function subsystem that has the capability of processing the request, and after the function module B2 processes the request, the processing result is directly returned to a 2.
Referring to fig. 3, the processing flow of the embodiment is specifically described as follows:
step 301, the function module a2 of version 2 sends a request to the function module B1 of version 1;
in step 302, function module B1 finds that its version is insufficient to handle the request from function module a2, function module B1 forwards the request to function module B2, which is capable of handling the request;
in step 303, the function block B2 finds itself capable of processing the received request, processes the request, and returns the processing result directly to the function block a 2.
The main difference between this embodiment and the first embodiment is a path for returning a response message, in order to ensure that the function module B2 can return the response message to the function module a2, the function module a2 may add information capable of identifying the address of the function module a2 in the request sent to the function module B1, and the function module B1 also carries information capable of identifying the address of the function module a2 in the request forwarded to the function module B2, that is, each function module transfers the address information of the sender of the request message to the next recipient, so that the last function module (B2) receives the request message and stores the address information of the message sender a2, and thus directly returns the response message to the function module a2 according to the address information.
EXAMPLE III
In this embodiment, each functional module of each functional subsystem does not care about the version information of other functional modules in the functional system, but only care about the version information of the functional modules in other functional subsystems. The processing of the functional module of each functional subsystem when interacting with the functional modules of other functional subsystems is specifically as follows: when a certain function module a2 of the function subsystem a sends a message to the function subsystem B, the function module a2 selects a function module B2 capable of processing the request, based on the grasped version information of each function module in the function subsystem B.
Referring to fig. 4, the processing flow of the embodiment is specifically described as follows:
step 401, the function module a2 in version 2 sends a request to the function subsystem B, a2 determines that the function module B2 of the function subsystem B can process the request, and sends the request to the function module B2;
in step 402, function block B2 processes the received request and returns the processing result to function block a 2.
Example four
This embodiment is a comprehensive improvement of the first embodiment and the second embodiment, and the main purpose of this improvement is to prevent the target system from being unable to process the received request due to the change of the version information of the target function module after the message is sent out. The main characteristics are that: besides the version information of other functional modules in the functional subsystem, each functional module of each functional subsystem needs to care about the version information of the functional modules in the other functional subsystems. Wherein, the processing of the functional module of each functional subsystem when interacting with the functional modules of other functional subsystems is specifically as follows: when a certain function module A3 of the function subsystem a sends a message to the function subsystem B, the function module A3 selects a function module B2 capable of processing the request according to the grasped version information of each function module in the function subsystem B, and the version of the function module B2 changes after the message is sent by A3, and the message sent by the function module A3 cannot be processed, the function module B2 forwards the request to the function module B3 capable of processing the request in the same function subsystem, and after the function module B3 finishes processing the request, the processing result is returned to B2, and the processing result is returned to A3 by B2.
Referring to fig. 5, the processing flow of the embodiment is specifically described as follows:
step 501, the function module A3 in version 3 sends a request to the function subsystem B, A3 determines that the function module B2 of the function subsystem B can process the request, and sends the request to the function module B2;
in step 502, when receiving the request, the function module B2 finds that it is unable to process the request of the version (the function module B2 switches to version 2 before receiving the request of the function module A3), determines that the function module B3 of version 3 is able to process the request, and forwards the request to the function module B3;
step 503, function module B3 processes the request and returns the request result to function module B2;
at step 504, function module B2 returns the request result to function module A3.
EXAMPLE five
The main difference between this embodiment and the fourth embodiment is the path of the response message. In this embodiment, the processing of the functional module of each functional subsystem when interacting with the functional modules of other functional subsystems is specifically as follows: when a certain function module A3 of the function subsystem a sends a message to the function subsystem B, the function module A3 selects a function module B2 capable of processing the request according to the grasped version information of each function module in the function subsystem B, and the version of the function module B2 changes after the message is sent by A3, and cannot process the message sent by the function module A3, the function module B2 forwards the request to the function module B3 capable of processing the request in the same function subsystem, and the function module B3 directly returns the processing result to A3 after processing the request.
Referring to fig. 6, the processing flow of the embodiment is specifically described as follows:
step 601, the function module A3 in version 3 sends a request to the function subsystem B, A3 determines that the function module B2 of the function subsystem B can process the request, and sends the request to the function module B2;
in step 602, when receiving the request, the function module B2 finds that it is unable to process the request of the version (the function module B2 switches to version 2 before receiving the request of the function module A3), determines that the function module B3 of version 3 is able to process the request, and forwards the request to the function module B3;
at step 603, function block B3 processes the request and returns the request results directly to function block A3.
In addition, the embodiment of the present invention further provides a matching device for different versions of function modules between function subsystems, and the present invention also provides a matching device for different versions of function modules between function subsystems, which is applied to function modules in function subsystems of a distributed system, and the device mainly includes a version information obtaining unit and a version information matching unit, wherein:
the version information acquisition unit is used for acquiring the version information of other functional modules in the functional subsystem and/or the version information of functional modules in other functional subsystems in the distributed system;
and the version information matching unit is used for sending the service request to the functional module matched with the version information of the service request for processing according to the version information of the initiated or received service request when service interaction is carried out between the functional module and the functional modules of other functional subsystems.
In addition, the version information acquiring unit is further configured to acquire version information of each functional module in other functional subsystems of the distributed system;
the version information matching unit is further used for sending the service request to the functional module matched with the version information of the service request in other functional subsystems for processing according to the acquired version information of each functional module in the other functional subsystems when the service request is sent to the other functional subsystems;
the functional module matched with the version information of the service request refers to a functional module of which the version information is consistent with or higher than the version information of the service request.
In addition, the version information acquiring unit is further configured to acquire version information of each other functional module in the functional subsystem;
the version information matching unit is further configured to, when a service request is received, if the version information of the current functional module is lower than the version information of the service request, forward the service request to other functional modules in the current functional subsystem, which are matched with the version information of the service request, for processing according to the acquired version information of each other functional module in the current functional subsystem.
Furthermore, the version information acquisition unit is further configured to acquire the version information by:
the network management centrally configures the version information of each functional module in each functional subsystem, and the version information acquisition unit acquires the version information through the network management; or,
the version information acquisition unit acquires the version information from other functional modules periodically through internal information, and broadcasts and notifies other functional modules when the version information of each functional module changes; or,
the version information acquisition unit reports the version information of the function module to the monitoring center at regular time, and actively reports the version information to the monitoring center when the version information of the function module changes, and the monitoring center broadcasts the version information to inform all the function modules.
Further, the apparatus further comprises a response message forwarding unit,
the version information matching unit is also used for superposing the address information of the version information matching unit in the initiated or forwarded service request when the service request is initiated or the received service request is forwarded;
the response message forwarding unit is used for returning or forwarding the response message of the service request according to the superposed address information, and removing the address information of the superposed address information in the returned or forwarded response message.
Further, the apparatus further comprises a response message forwarding unit,
the version information matching unit is also used for including the address information of the service module initiating the service request in the initiated or forwarded service request when the service request is initiated or the received service request is forwarded;
the response message forwarding unit is used for returning a response message to the initiating function module initiating the service request according to the address information contained in the service request.
While the invention has been described with reference to specific embodiments, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
It will be apparent to those skilled in the art that the functional blocks or steps of the present invention described above may be implemented by a general purpose computing device, centralized on a single computing device or distributed across a network of computing devices, or alternatively implemented by program code executable by a computing device, such that the steps shown and described may be executed by a computing device stored in a memory device and, in some cases, executed out of order, or fabricated separately as individual integrated circuit functional blocks, or fabricated as a single integrated circuit functional block. Thus, the present invention is not limited to any specific combination of hardware and software.
Claims (10)
1. A method for matching different versions of function modules between function subsystems is characterized in that,
the method comprises the steps that a functional module in a functional subsystem of a distributed system obtains version information of other functional modules in the functional subsystem and version information of the functional modules in the other functional subsystems in the distributed system;
when service interaction is performed among functional modules of different functional subsystems, according to version information of a service request which is initiated or received, the service request is sent to the functional module matched with the version information of the service request for processing, and the method specifically comprises the following steps:
when a functional module in the functional subsystem initiates a service request to other functional subsystems, sending the service request to a functional module matched with the version information of the service request in the other functional subsystems for processing according to the acquired version information of each functional module in the other functional subsystems;
after the service request is initiated, if the version information of the target function module of the service request is changed in the sending process of the service request, and the changed version information is lower than the version information of the service request, the target function module of the service request forwards the service request to other function modules matched with the version information of the service request in the function subsystem for processing according to the acquired version information of other function modules in the function subsystem.
2. The method according to claim 1, characterized in that it comprises in particular:
the method comprises the steps that a functional module in a functional subsystem of the distributed system obtains version information of other functional modules in the functional subsystem;
when a functional module in the functional subsystem receives a service request, if the version information of the functional module is lower than the version information of the service request, the service request is forwarded to other functional modules matched with the version information of the service request in the functional subsystem for processing according to the acquired version information of other functional modules in the functional subsystem.
3. The method according to claim 1 or 2, wherein the functional module matched with the version information of the service request is:
and the version information is consistent with or higher than that of the service request.
4. The method of claim 1 or 2, wherein the functional module obtains the version information by:
the network management centrally configures the version information of each functional module in each functional subsystem, and the functional module acquires the version information through the network management; or,
the functional module acquires the version information from other functional modules regularly through internal information, and broadcasts and notifies other functional modules when the version information of each functional module changes; or,
the functional modules of each functional subsystem report the version information of the functional module to the monitoring center at regular time, and when the version information of the functional module changes, the version information is actively reported to the monitoring center, and the monitoring center broadcasts the version information to inform all the functional modules.
5. The method of claim 1 or 2, wherein the method further comprises:
when the initiating function module and the forwarding function module of the service request initiate the service request or forward the received service request, the self address information is superposed in the initiated or forwarded service request;
after the functional module matched with the version information of the service request receives and processes the service request, a response message containing the superposed address information is returned to the last forwarding functional module according to the superposed address information in the service request; and each forwarding functional module removes the address information of the forwarding functional module according to the received response message, and then returns the response message to the previous forwarding functional module until the response message is forwarded to the service request initiating functional module.
6. The method of claim 1 or 2, wherein the method further comprises:
when the initiating function module and the forwarding function module of the service request initiate the service request or forward the received service request, the initiated or forwarded service request contains the address information of the initiating function module of the service request;
and after the functional module matched with the version information of the service request receives and processes the service request, returning a response message to the initiating functional module according to the address information of the initiating functional module contained in the service request.
7. An apparatus for matching different versions of function modules between function subsystems, the apparatus being applied to function modules in function subsystems of a distributed system, the apparatus comprising:
the version information acquisition unit is used for acquiring the version information of other functional modules in the functional subsystem and the version information of functional modules in other functional subsystems in the distributed system;
the version information matching unit is used for sending the service request to the functional module matched with the version information of the service request for processing according to the version information of the initiated or received service request when service interaction is carried out between the functional module and the functional module of other functional subsystems, and specifically comprises the following steps:
when the version information matching unit initiates a service request to other functional subsystems, the version information matching unit sends the service request to the functional module matched with the version information of the service request in the other functional subsystems for processing according to the acquired version information of each functional module in the other functional subsystems;
when the version information matching unit receives a service request, if the version information of the function module is lower than the version information of the service request, the service request is forwarded to other function modules matched with the version information of the service request in the function subsystem for processing according to the acquired version information of other function modules in the function subsystem;
the functional module matched with the version information of the service request refers to a functional module of which the version information is consistent with or higher than the version information of the service request.
8. The apparatus of claim 7,
the version information obtaining unit is further configured to obtain the version information by:
the network management centrally configures the version information of each functional module in each functional subsystem, and the version information acquisition unit acquires the version information through the network management; or,
the version information acquisition unit acquires the version information from other functional modules periodically through internal information, and broadcasts and notifies other functional modules when the version information of each functional module changes; or,
the version information acquisition unit reports the version information of the function module to the monitoring center at regular time, and actively reports the version information to the monitoring center when the version information of the function module changes, and the monitoring center broadcasts the version information to inform all the function modules.
9. The apparatus of claim 7, wherein the apparatus further comprises a response message forwarding unit,
the version information matching unit is also used for superposing the address information of the version information matching unit in the initiated or forwarded service request when the service request is initiated or the received service request is forwarded;
the response message forwarding unit is used for returning or forwarding the response message of the service request according to the superposed address information, and removing the address information of the superposed address information in the returned or forwarded response message.
10. The apparatus of claim 7, wherein the apparatus further comprises a response message forwarding unit,
the version information matching unit is also used for including the address information of the service module initiating the service request in the initiated or forwarded service request when the service request is initiated or the received service request is forwarded;
the response message forwarding unit is used for returning a response message to the initiating function module initiating the service request according to the address information contained in the service request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010517890.5A CN101977220B (en) | 2010-10-14 | 2010-10-14 | Method and device for matching functional modules with different versions among function subsystems |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010517890.5A CN101977220B (en) | 2010-10-14 | 2010-10-14 | Method and device for matching functional modules with different versions among function subsystems |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101977220A CN101977220A (en) | 2011-02-16 |
| CN101977220B true CN101977220B (en) | 2015-06-03 |
Family
ID=43577065
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010517890.5A Active CN101977220B (en) | 2010-10-14 | 2010-10-14 | Method and device for matching functional modules with different versions among function subsystems |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101977220B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10291486B2 (en) * | 2012-06-13 | 2019-05-14 | Oracle International Corporation | System and method for supporting implicit versioning in a transactional middleware machine environment |
| CN111914194B (en) * | 2020-07-02 | 2021-09-17 | 网联清算有限公司 | Business system changing method and device, electronic equipment and storage medium |
| CN112698885B (en) * | 2021-01-04 | 2023-07-21 | 联想(北京)有限公司 | Method and device for operating |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1483286A (en) * | 2000-11-01 | 2004-03-17 | 松下电器产业株式会社 | Data transmitting apparatus and data receiving apparatus |
| CN1956394A (en) * | 2006-11-13 | 2007-05-02 | 杭州华为三康技术有限公司 | Method and device for service configuration of network equipment |
| CN101594355A (en) * | 2009-06-17 | 2009-12-02 | 华为技术有限公司 | A kind of method and device of realizing cross-version software interaction |
-
2010
- 2010-10-14 CN CN201010517890.5A patent/CN101977220B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1483286A (en) * | 2000-11-01 | 2004-03-17 | 松下电器产业株式会社 | Data transmitting apparatus and data receiving apparatus |
| CN1956394A (en) * | 2006-11-13 | 2007-05-02 | 杭州华为三康技术有限公司 | Method and device for service configuration of network equipment |
| CN101594355A (en) * | 2009-06-17 | 2009-12-02 | 华为技术有限公司 | A kind of method and device of realizing cross-version software interaction |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101977220A (en) | 2011-02-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3751886A1 (en) | Communication method and device under centralized unit-distributed unit architecture | |
| KR102590338B1 (en) | Short message service ability updating method, device and apparatus | |
| CA2780505C (en) | Method, system and equipment for implementing ussd service in cdma network | |
| KR102589728B1 (en) | Communication methods, related devices and devices | |
| KR102392120B1 (en) | Processing method, device and system for nf component abnormality | |
| JP2016541200A (en) | Management method, related device and system for embedded universal integrated circuit card | |
| EP2811766B1 (en) | Method and system for sending short message | |
| CN111031517A (en) | Message notification method, device, network element, system and storage medium | |
| CN112600693B (en) | Service request processing method, system, electronic equipment and computer storage medium | |
| CN110831044B (en) | Processing method, device and equipment of routing strategy | |
| WO2022089163A1 (en) | Method and apparatus for managing network slice data | |
| JP2023515393A (en) | Mode switching method and equipment | |
| CN111491036A (en) | Internet of things equipment and communication method thereof | |
| CN112218342A (en) | Method, device and system for realizing core network sub-slice disaster tolerance | |
| JP2023518344A (en) | Exposure and Discovery of Distributed Network Functions Serving User Equipment or PPDU Sessions | |
| CN101977220B (en) | Method and device for matching functional modules with different versions among function subsystems | |
| EP3188418A1 (en) | Near field discovery method, user equipment, and storage medium | |
| CN110519712B (en) | Information processing method and device, network element and storage medium | |
| CN113596792A (en) | Binding method and device of electronic equipment, storage medium and electronic device | |
| KR102316348B1 (en) | Communication method, network device and terminal device | |
| EP2582199A1 (en) | M2m system and method for processing services thereof | |
| CN102647691A (en) | Short message sending method, device and system | |
| CN102404697B (en) | Multi-media message service system, method and device | |
| CN103067563B (en) | Method, system and device for managing and discovering terminal capability information | |
| CN109788520A (en) | Method for switching network, AMF and RAN node |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |